diff --git a/.devcontainer/devcontainer.json b/.devcontainer/devcontainer.json
deleted file mode 100644
index 8c5fea882..000000000
--- a/.devcontainer/devcontainer.json
+++ /dev/null
@@ -1,48 +0,0 @@
-// For format details, see https://aka.ms/devcontainer.json. For config options, see the
-// README at: https://github.com/devcontainers/templates/tree/main/src/typescript-node
-{
-  "name": "Stellar Docs - Docusaurus/pnpm",
-  "image": "mcr.microsoft.com/devcontainers/typescript-node:1-24",
-  "hostRequirements": {
-    "cpus": 2
-  },
-  "forwardPorts": [3000],
-  "portsAttributes": {
-    "3000": {
-      "elevateIfNeeded": true,
-      "onAutoForward": "openBrowser",
-      "label": "docusaurus",
-      "requireLocalPort": true
-    }
-  },
-  "customizations": {
-    "codespaces": {
-      "openFiles": ["README.md"]
-    },
-    "vscode": {
-      "settings": {
-        "[typescript]": {
-          "editor.defaultFormatter": "esbenp.prettier-vscode",
-          "editor.formatOnSave": true
-        },
-        "[json]": {
-          "editor.defaultFormatter": "esbenp.prettier-vscode",
-          "editor.formatOnSave": true
-        },
-        "[jsonc]": {
-          "editor.defaultFormatter": "esbenp.prettier-vscode",
-          "editor.formatOnSave": true
-        }
-      },
-      "extensions": [
-        "dbaeumer.vscode-eslint",
-        "esbenp.prettier-vscode",
-        "streetsidesoftware.code-spell-checker"
-      ]
-    }
-  },
-  "postCreateCommand": "pnpm install --frozen-lockfile",
-  "waitFor": "postCreateCommand",
-  "postStartCommand": "chmod +x ./.devcontainer/post_attach_start.sh",
-  "postAttachCommand": "./.devcontainer/post_attach_start.sh && tail -f docs.log"
-}
diff --git a/.devcontainer/post_attach_start.sh b/.devcontainer/post_attach_start.sh
deleted file mode 100755
index 59b145803..000000000
--- a/.devcontainer/post_attach_start.sh
+++ /dev/null
@@ -1,14 +0,0 @@
-#!/bin/bash
-set -e
-
-touch docs.log
-chmod 775 docs.log
-nohup pnpm start --port 3000 > docs.log 2>&1 & echo $! > run.pid
-
-echo "Docusaurus running on process: $(cat run.pid)"
-echo "Docusaurus running on port 3000"
-echo ""
-echo "View logs:  tail -f docs.log"
-echo "Restart docusaurus:  ./.devcontainer/restart.sh"
-echo "Stop docusaurus:  kill -9 '$(lsof -t -i:3000)'"
-echo "Developing in a devcontainer: https://docs.github.com/en/codespaces/developing-in-a-codespace/developing-in-a-codespace#working-in-a-codespace-in-the-browser"
diff --git a/.devcontainer/restart.sh b/.devcontainer/restart.sh
deleted file mode 100755
index d27525d7a..000000000
--- a/.devcontainer/restart.sh
+++ /dev/null
@@ -1,5 +0,0 @@
-#!/bin/bash
-set -e
-
-kill -9 $(lsof -t -i:3000)
-./post_attach_start.sh
diff --git a/.github/dependabot.yml b/.github/dependabot.yml
index d1619e92b..c730811e2 100644
--- a/.github/dependabot.yml
+++ b/.github/dependabot.yml
@@ -32,16 +32,3 @@ updates:
       all-actions:
         applies-to: version-updates
         patterns: [ "*" ]
-  - package-ecosystem: "docker"
-    directory: "/"
-    schedule:
-      interval: "weekly"
-      day: "sunday"
-      time: "02:00"
-    cooldown:
-      default-days: 3
-    open-pull-requests-limit: 2
-    groups:
-      all-docker:
-        applies-to: version-updates
-        patterns: [ "*" ]
diff --git a/.github/workflows/build-and-push.yml b/.github/workflows/build-and-push.yml
deleted file mode 100644
index f6139e443..000000000
--- a/.github/workflows/build-and-push.yml
+++ /dev/null
@@ -1,79 +0,0 @@
-name: Build and push stellar-docs
-
-# Deployed to: https://github.com/stellar/stellar-docs
-#
-# Converted from the Jenkins pipeline (Jenkinsfile-stellar-docs). On every push
-# to main (or manual dispatch) builds the stellar-docs docker image (with
-# translations), pushes it to the prd ECR repo (prd/stellar-docs:<sha>), and
-# also pushes it as dev/stellar-docs:latest for PR previews.
-
-on:
-  push:
-    branches:
-      - main
-  workflow_dispatch:
-
-permissions:
-  id-token: write
-  contents: read
-
-env:
-  SLACK_CHANNEL: docs-builds
-
-jobs:
-  build-and-push:
-    if: github.ref == 'refs/heads/main'
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v7.0.1
-        with:
-          # Docusaurus uses Git history for last-update author and time.
-          fetch-depth: 0
-
-      - name: Determine image label
-        id: vars
-        run: echo "label=$(git rev-parse --short HEAD)" >> "$GITHUB_OUTPUT"
-
-      - name: ECR login
-        id: ecr-login
-        uses: stellar/actions/sdf-ecr-login@main
-
-      - name: Build and push docker image
-        env:
-          ECR_REGISTRY: ${{ steps.ecr-login.outputs.ecr-registry }}
-          LABEL: ${{ steps.vars.outputs.label }}
-        run: |
-          set -eu
-          export TAG="${ECR_REGISTRY}/prd/stellar-docs:${LABEL}"
-          make docker-build
-          ecr-push "${TAG}"
-
-          # Push image with latest tag to dev registry for the PR previews.
-          DEV_TAG="${ECR_REGISTRY}/dev/stellar-docs:latest"
-          docker tag "${TAG}" "${DEV_TAG}"
-          ecr-push "${DEV_TAG}"
-
-      - name: Slack notification — success
-        if: success()
-        uses: slackapi/slack-github-action@dcb1066f776dd043e64d0e8ba94ca15cc7e1875d # v4.0.0
-        with:
-          method: chat.postMessage
-          token: ${{ secrets.SLACK_BOT_TOKEN }}
-          payload: |
-            {
-              "channel": "${{ env.SLACK_CHANNEL }}",
-              "text": "Docs build complete for <${{ github.server_url }}/${{ github.repository }}/commit/${{ github.sha }}|${{ github.sha }}>."
-            }
-
-      - name: Slack notification — failure
-        if: failure()
-        uses: slackapi/slack-github-action@dcb1066f776dd043e64d0e8ba94ca15cc7e1875d # v4.0.0
-        with:
-          method: chat.postMessage
-          token: ${{ secrets.SLACK_BOT_TOKEN }}
-          payload: |
-            {
-              "channel": "${{ env.SLACK_CHANNEL }}",
-              "text": "Docs build failed for <${{ github.server_url }}/${{ github.repository }}/commit/${{ github.sha }}|${{ github.sha }}>."
-            }
diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
deleted file mode 100644
index d398cb4f2..000000000
--- a/.github/workflows/build.yml
+++ /dev/null
@@ -1,55 +0,0 @@
-name: Build docs
-
-on:
-  workflow_call:
-    inputs:
-      stellar-cli-ref:
-        required: false
-        default: 'main'
-        type: string
-        description: "Stellar-cli ref to build against. If empty, will use latest cli version"
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout App Repo
-        uses: actions/checkout@v7.0.1
-        with:
-          repository: "stellar/stellar-docs"
-
-      - name: Install pnpm
-        uses: pnpm/action-setup@v6
-
-      - name: Setup Node
-        uses: actions/setup-node@v7.0.0
-        with:
-          node-version: '24'
-          cache: 'pnpm'
-          cache-dependency-path: '**/pnpm-lock.yaml'
-
-      - name: Enable Corepack
-        run: corepack enable
-
-      - name: Install App Dependencies
-        run: pnpm install --prefer-offline --frozen-lockfile
-        shell: bash
-
-      - name: Copy Files From Stellar CLI
-        run: pnpm stellar-cli:build -- --cli-ref='${{ inputs.stellar-cli-ref }}'
-        shell: bash
-
-      - name: (temp) Fix CLI links
-        run: pnpm stellar-cli:fix-links
-        shell: bash
-
-      - name: Build app
-        run: pnpm build
-        shell: bash
-
-      - name: Check if routes.txt file needs updating
-        run: |
-          if ! git diff --exit-code -- routes.txt; then
-            echo 'The `routes.txt` file has changed. Please update the routes.txt file locally by running `pnpm build` and push that change.'
-            exit 1
-          fi
diff --git a/.github/workflows/check-routes-removal.yml b/.github/workflows/check-routes-removal.yml
deleted file mode 100644
index 7c81f7d46..000000000
--- a/.github/workflows/check-routes-removal.yml
+++ /dev/null
@@ -1,59 +0,0 @@
-name: Check Routes Removal
-
-on:
-  pull_request:
-    paths:
-      - 'routes.txt'
-
-jobs:
-  check-routes-removal:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v7.0.1
-        with:
-          fetch-depth: 0
-
-      - name: Check for routes removal
-        id: check-removal
-        run: |
-          # Get the list of removed lines in routes.txt
-          ROUTES_DIFF=$(git diff origin/${{ github.base_ref }} ${{ github.sha }} -- routes.txt)
-          
-          # Count removed lines (excluding diff metadata)
-          REMOVED_COUNT=$(echo "$ROUTES_DIFF" | { grep -E '^\-[^-]' || true; } | wc -l)
-          
-          if [ $REMOVED_COUNT -gt 0 ]; then
-            echo "routes_removed=true" >> $GITHUB_OUTPUT
-            echo "$ROUTES_DIFF" >> routes.diff
-          else
-            echo "routes_removed=false" >> $GITHUB_OUTPUT
-          fi
-
-      - name: Comment on PR (if routes were removed)
-        if: steps.check-removal.outputs.routes_removed == 'true'
-        uses: actions/github-script@v9
-        with:
-          github-token: ${{ secrets.GITHUB_TOKEN }}
-          script: |
-            const fs = require('fs')
-            const diffContent = fs.readFileSync('routes.diff', 'utf8');
-            
-            // Convert escaped newlines back for display
-            const formattedDiff = diffContent.replace(/%0A/g, '\n').replace(/%0D/g, '\r').replace(/%25/g, '%');
-            
-            const comment = `> [!WARNING]  
-            > This change removes routes. The diff of routes is below. Please verify that these changes to the routes are intentional and that redirects are in place if needed. Redirects can be added to \`nginx/includes/redirects.conf\`.
-            
-            \`\`\`diff
-            ${formattedDiff}
-            \`\`\`
-            
-            `;
-            
-            github.rest.issues.createComment({
-              issue_number: context.issue.number,
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              body: comment
-            });
diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
deleted file mode 100644
index cb2d039a3..000000000
--- a/.github/workflows/main.yml
+++ /dev/null
@@ -1,66 +0,0 @@
-name: Build, format MDX and Lint
-
-on:
-  pull_request:
-    branches:
-      - main
-
-  workflow_dispatch:
-
-jobs:
-  complete:
-    if: always()
-    needs: [ mdx-format, build ]
-    runs-on: ubuntu-latest
-    steps:
-      - if: contains(needs.*.result, 'failure') || contains(needs.*.result, 'cancelled')
-        run: exit 1
-
-  mdx-format:
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Checkout App Repo
-        uses: actions/checkout@v7.0.1
-        with:
-          # Full history so we can diff the PR against its base branch and only
-          # flag links introduced by this PR, not pre-existing repo content.
-          fetch-depth: 0
-
-      - name: Install pnpm
-        uses: pnpm/action-setup@v6
-
-      - name: Setup Node
-        uses: actions/setup-node@v7.0.0
-        with:
-          node-version: '24'
-          cache: 'pnpm'
-          cache-dependency-path: '**/pnpm-lock.yaml'
-
-      - name: Enable Corepack
-        run: corepack enable
-
-      - name: Install App Dependencies
-        run: pnpm install --prefer-offline --frozen-lockfile
-
-      - name: Check MDX
-        run:  git update-index -g && pnpm ci:mdx
-
-      - name: Show Diff if Prettier Fails
-        if: ${{ failure() }}
-        run: pnpm diff:mdx && echo "::error::Prettier static analysis failed"
-
-      - name: No new absolute internal /docs links
-        # Canonical rule lives in scripts/check-relative-links.sh (shared with
-        # the pre-commit hook). Only flags absolute /docs links introduced by
-        # this PR's diff, not pre-existing content in untouched lines.
-        run: |
-          base="${{ github.base_ref }}"
-          scripts/check-relative-links.sh --range "origin/${base:-main}...HEAD" \
-            || { echo "::error::New absolute /docs link(s) found above."; exit 1; }
-
-
-
-  build:
-    uses: ./.github/workflows/build.yml
-
diff --git a/.github/workflows/mintlify-checks.yml b/.github/workflows/mintlify-checks.yml
new file mode 100644
index 000000000..9461347f1
--- /dev/null
+++ b/.github/workflows/mintlify-checks.yml
@@ -0,0 +1,65 @@
+name: Format MDX and validate the Mintlify build
+
+on:
+  pull_request:
+    branches:
+      - main
+      - mintlify-migration
+
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  complete:
+    if: always()
+    needs: [ checks ]
+    runs-on: ubuntu-latest
+    steps:
+      - if: contains(needs.*.result, 'failure') || contains(needs.*.result, 'cancelled')
+        run: exit 1
+
+  checks:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout App Repo
+        uses: actions/checkout@v7.0.1
+        with:
+          persist-credentials: false
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v6
+
+      - name: Setup Node
+        uses: actions/setup-node@v7.0.0
+        with:
+          node-version: '24'
+          cache: 'pnpm'
+          cache-dependency-path: '**/pnpm-lock.yaml'
+
+      - name: Enable Corepack
+        run: corepack enable
+
+      - name: Install App Dependencies
+        run: pnpm install --prefer-offline --frozen-lockfile
+
+      - name: Check MDX formatting
+        run: git update-index -g && pnpm ci:mdx
+
+      - name: Show Diff if Prettier Fails
+        if: ${{ failure() }}
+        run: pnpm diff:mdx && echo "::error::Prettier static analysis failed"
+
+      - name: Check blank lines around component tags
+        run: pnpm check:pad
+
+      - name: Validate the Mintlify build
+        run: pnpm validate
+
+      - name: Check links
+        # Known broken links remain (see mintlify-fast-follow.md), so this
+        # reports without failing the job until they're fixed.
+        continue-on-error: true
+        run: pnpm check:links
diff --git a/.github/workflows/pr-preview.yml b/.github/workflows/pr-preview.yml
deleted file mode 100644
index 51be1b9aa..000000000
--- a/.github/workflows/pr-preview.yml
+++ /dev/null
@@ -1,76 +0,0 @@
-# PR preview environments, replacing the Jenkins preview pipeline
-# (Jenkinsfile-stellar-docs-preview). CI only builds the image and signals with the
-# `preview` label; ArgoCD's preview-developers ApplicationSet
-# (stellar/kube) does the deploying.
-# See https://github.com/stellar/actions/tree/main/sdf-pr-preview
-
-name: pr-preview
-
-on:
-  pull_request_target:
-    types: [opened, synchronize, reopened, closed, labeled]
-
-# pull_request_target runs in base-repo context, so these are real write
-# permissions even for fork PRs. On `pull_request`, fork runs get no OIDC
-# token and a read-only token.
-permissions:
-  contents: read
-  id-token: write
-  pull-requests: write
-
-concurrency:
-  group: pr-preview-${{ github.event.pull_request.number }}
-  cancel-in-progress: true
-
-env:
-  ECR_REPOSITORY: dev/stellar-docs
-  PREVIEW_HOST: developers-pr-${{ github.event.pull_request.number }}.previews.kube001.services.stellar-ops.com
-
-jobs:
-  preview:
-    # `labeled` is only for maintainer approval of PRs whose author is not an
-    # org member (the stellar-triage-bot App). Any other label must not rerun
-    # the gate: it withdraws the `preview` label and would take a live
-    # preview down.
-    if: github.event.action != 'labeled' || github.event.label.name == 'preview-approved'
-    runs-on: ubuntu-latest
-    steps:
-      # Nothing that touches PR code may run before the gate, and every step
-      # after it must be guarded by `member == 'true'`.
-      - id: gate
-        uses: stellar/actions/sdf-pr-preview/gate@main
-        with:
-          app-id: ${{ vars.PREVIEW_BOT_APP_ID }}
-          private-key: ${{ secrets.PREVIEW_BOT_PRIVATE_KEY }}
-          # An org member applies this to approve one preview build of the
-          # current head; a later push needs a fresh approval.
-          approval-label: preview-approved
-
-      # PR head SHA, not the default base ref - must match the
-      # ApplicationSet's {{ .head_sha }}.
-      - uses: actions/checkout@v6
-        if: steps.gate.outputs.member == 'true'
-        with:
-          ref: ${{ github.event.pull_request.head.sha }}
-          persist-credentials: false
-          allow-unsafe-pr-checkout: true
-
-      - id: ecr-login
-        if: steps.gate.outputs.member == 'true'
-        uses: stellar/actions/sdf-ecr-login@main
-
-      - name: Build and push preview image
-        if: steps.gate.outputs.member == 'true'
-        env:
-          TAG: ${{ steps.ecr-login.outputs.ecr-registry }}/${{ env.ECR_REPOSITORY }}:${{ steps.gate.outputs.image-tag }}
-        run: |
-          set -eu
-          make docker-build
-          make docker-push
-          echo "IMAGE=${TAG}" >> "$GITHUB_ENV"
-
-      - uses: stellar/actions/sdf-pr-preview/publish@main
-        if: steps.gate.outputs.member == 'true'
-        with:
-          images: ${{ env.IMAGE }}
-          preview-host: ${{ env.PREVIEW_HOST }}
diff --git a/.gitignore b/.gitignore
index 6208c37c4..cf856e7d5 100644
--- a/.gitignore
+++ b/.gitignore
@@ -35,3 +35,7 @@ stellar-cli-repo
 
 docs.log
 run.pid
+
+# Mintlify
+tools/sds/node_modules/
+tools/redirects/
diff --git a/.husky/pre-commit b/.husky/pre-commit
index 0d418d1aa..4ce5ccf5c 100755
--- a/.husky/pre-commit
+++ b/.husky/pre-commit
@@ -51,6 +51,9 @@ fi
 corepack pnpm check:mdx
 CHECK_STATUS=$?
 
+corepack pnpm -s check:pad ||
+  fail "✖ MDX components need blank lines around their tags. Run \`pnpm format:mdx\`."
+
 if [ "$CHECK_STATUS" -eq 1 ]; then
   printf '%s\n' 'ℹ Run `pnpm format:mdx` to fix the formatting.'
   printf '%s\n' '  If that also fails, your dependencies may be out of sync: `corepack pnpm install`'
@@ -63,9 +66,3 @@ The project dependencies may be incomplete or corrupted. Run:
   corepack pnpm install
 Setup instructions: ${SETUP_URL}"
 fi
-
-# No new absolute internal /docs links in staged docs. Canonical rule lives in
-# scripts/check-relative-links.sh (shared with CI) — only flags links introduced
-# in staged changes, never pre-existing content in untouched lines.
-scripts/check-relative-links.sh --staged ||
-  fail "✖ Absolute /docs link check failed. Use a relative ../path/file.mdx link with the .mdx extension instead."
diff --git a/.mintignore b/.mintignore
new file mode 100644
index 000000000..3326283dd
--- /dev/null
+++ b/.mintignore
@@ -0,0 +1,39 @@
+/tools/
+
+# Pages marked draft: true in the Docusaurus source (not published on developers.stellar.org)
+/docs/build/guides/conventions/work-contractspec-js.mdx
+/docs/build/guides/conversions/address-to-bytesn.mdx
+/docs/build/guides/conversions/address-to-id.mdx
+/docs/build/guides/conversions/id-to-address.mdx
+/docs/build/guides/dapps/docker.mdx
+/docs/build/guides/dapps/react.mdx
+/docs/build/guides/fees/cost-analysis.mdx
+/docs/build/guides/rpc/self-deploy-rpc.mdx
+/docs/build/guides/rpc/use-public-rpc.mdx
+/docs/build/guides/storage/choose-type.mdx
+/docs/build/smart-contracts/example-contracts/TEMPLATE.mdx
+/docs/learn/fundamentals/contract-development/transaction-lifecycle.mdx
+/docs/learn/migrate/cosmos.mdx
+/docs/learn/migrate/near.mdx
+/docs/learn/migrate/solana.mdx
+/docs/tools/developer-tools/IDEs.mdx
+/docs/build/apps/wallet/contributing.mdx
+
+# Repo tooling and sources (not site content)
+/CONTRIBUTING.md
+/docs/**/CONTRIBUTING.md
+/openrpc/
+/openapi/horizon/main.yml
+/openapi/horizon/components/
+/openapi/horizon/README.md
+/openapi/anchor-platform/main-*.yaml
+/openapi/anchor-platform/examples.yaml
+/openapi/anchor-platform/schemas.yaml
+/openapi/stellar-disbursement-platform/main.yaml
+/scripts/
+/redocly.yaml
+/.prettierrc.js
+/.github/
+/.claude/
+/.husky/
+/scratchpad/
diff --git a/.mintlify/skills/agentic-payments/SKILL.md b/.mintlify/skills/agentic-payments/SKILL.md
new file mode 100644
index 000000000..9515de3da
--- /dev/null
+++ b/.mintlify/skills/agentic-payments/SKILL.md
@@ -0,0 +1,626 @@
+---
+name: agentic-payments
+description: Agentic and machine-to-machine payments on Stellar. Covers x402 (HTTP 402 paid APIs via OZ Channels facilitator, fee-sponsored clients) and MPP (Machine Payments Protocol) in both Charge mode (per-request SAC) and Channel mode (off-chain commits, high-frequency). Defaults to USDC (SEP-41 SAC) on `stellar:testnet`/`stellar:pubnet` (CAIP-2). Use when selling a paid API to AI agents, building an x402 client, or designing a payment-channel architecture for high-frequency agent traffic.
+user-invocable: true
+argument-hint: "[payment task]"
+---
+
+# Agentic Payments: x402 + MPP
+
+Two complementary protocols for AI-agent and machine-to-machine payments on Stellar. Pick based on who depends on whom and how often the agent pays.
+
+## Quick decision
+
+| | x402 | MPP Charge | MPP Channel |
+|--|------|------------|-------------|
+| Per-request on-chain tx? | Yes (via facilitator) | Yes (SAC) | No (off-chain commits) |
+| Needs facilitator? | Yes (OZ Channels) | No | No |
+| Client needs XLM? | No (fees sponsored) | Optional (`feePayer`) | Yes |
+| Setup complexity | Low | Low | Medium (deploy contract first) |
+| Best for | Quickest setup, fee-free clients | No third-party dep | High-frequency agents |
+
+- Selling an API, want zero-XLM clients → see **x402 Seller** below
+- Calling an x402 API from an agent → see **x402 Buyer** below
+- Selling an API, no facilitator dependency → see **MPP Charge** below
+- Agent making many requests per session → see **MPP Channel** below
+- Unsure → x402 (lowest friction to get started)
+
+All protocols use USDC (SEP-41 SAC) by default; `stellar:testnet` / `stellar:pubnet` CAIP-2 network IDs.
+
+## Related skills
+- The SACs the protocols call → `/.well-known/agent-skills/smart-contracts/skill.md`
+- USDC and other classic assets → `/.well-known/agent-skills/assets/skill.md`
+- Wallets and signing in the buyer client → `/.well-known/agent-skills/dapp/skill.md`
+- RPC simulation / submission patterns → `/.well-known/agent-skills/data/skill.md`
+- SEP-41 (token interface) and related standards → `/.well-known/agent-skills/standards/skill.md`
+
+---
+
+# Part 1: x402 — Paid APIs + Agent Buyer Clients
+
+
+## When to use x402
+x402 is the right choice when:
+- You want the fastest path to a paid API — minimal code, no contract deployment
+- You want clients (including AI agents) to pay with **zero XLM** — the OZ Channels facilitator sponsors all network fees
+- You're building on top of an existing x402 ecosystem (Coinbase, other chains)
+
+Trade-off: you depend on OZ Channels (or a self-hosted relayer) for verification and settlement. If you need zero third-party dependency, use MPP Charge (Part 2 below) instead.
+
+## How x402 works on Stellar
+
+```
+Client → GET /resource                               → Server
+Client ← 402 Payment Required (payment requirements) ← Server
+Client builds SAC USDC transfer
+Client signs auth entries only (not the full tx envelope)
+Client → GET /resource + X-PAYMENT header           → Server
+Server → OZ Channels /verify + /settle              → Stellar (~5s)
+Client ← 200 OK + resource
+```
+
+The key Stellar difference: clients sign **auth entries**, not full transaction envelopes. The facilitator assembles the transaction, pays fees, and submits. Clients need zero XLM.
+
+## Seller: monetize an Express API
+
+```bash
+npm install @x402/express @x402/core @x402/stellar express dotenv
+npm pkg set type=module
+```
+
+```js
+// server.js
+import "dotenv/config";
+import express from "express";
+import { paymentMiddleware, x402ResourceServer } from "@x402/express";
+import { HTTPFacilitatorClient } from "@x402/core/server";
+import { ExactStellarScheme } from "@x402/stellar/exact/server";
+
+// Drive the CAIP-2 network ID from one place. Switching to mainnet means
+// flipping STELLAR_NETWORK and FACILITATOR_URL in .env, nothing in code.
+const NETWORK = process.env.STELLAR_NETWORK || "stellar:testnet";
+
+if (!process.env.OZ_API_KEY) {
+  throw new Error(
+    "OZ_API_KEY is required. Generate one at https://channels.openzeppelin.com/testnet/gen (testnet) or https://channels.openzeppelin.com/gen (mainnet)."
+  );
+}
+
+const facilitator = new HTTPFacilitatorClient({
+  url: process.env.FACILITATOR_URL ?? "https://channels.openzeppelin.com/x402/testnet",
+  // OZ Channels requires Bearer auth on both testnet and mainnet
+  createAuthHeaders: async () => {
+    const h = { Authorization: `Bearer ${process.env.OZ_API_KEY}` };
+    return { verify: h, settle: h, supported: h };
+  },
+});
+
+const resourceServer = new x402ResourceServer(facilitator)
+  .register(NETWORK, new ExactStellarScheme());
+
+const app = express();
+
+app.use(
+  paymentMiddleware(
+    {
+      "GET /weather": {
+        accepts: {
+          scheme: "exact",
+          price: "$0.001", // human-readable, auto-converts to 7-decimal USDC units
+          network: NETWORK,
+          payTo: process.env.STELLAR_RECIPIENT, // recipient G... account
+        },
+        description: "Current weather data",
+      },
+    },
+    resourceServer
+  )
+);
+
+app.get("/weather", (_req, res) => {
+  res.json({ city: "San Francisco", temp: 18, conditions: "Foggy" });
+});
+
+app.listen(3001, () => console.log(`x402 server on http://localhost:3001 (${NETWORK})`));
+```
+
+**Env vars:**
+- `STELLAR_NETWORK` — CAIP-2 network ID; defaults to `stellar:testnet`. Set to `stellar:pubnet` for mainnet.
+- `STELLAR_RECIPIENT` — your G... address (receives USDC, needs a USDC trustline)
+- `OZ_API_KEY` — OZ Channels API key (**required on both testnet and mainnet**; generate at the link in the runbook below)
+- `FACILITATOR_URL` — defaults to testnet URL above; set to `https://channels.openzeppelin.com/x402` for mainnet
+
+**Price format options:**
+- `"$0.001"` — human-readable, auto-converts to 7-decimal USDC units
+- `{ amount: "1000", asset: "ASSET_SAC_CONTRACT_ID" }` — explicit base units for non-USDC assets
+
+**`payTo` is the recipient's classic Stellar account (`G...`), not the USDC SAC contract address.** Sending USDC lands in the classic balance of the `payTo` account, which is why that account also needs a USDC trustline. The SAC contract address is what the protocol invokes `transfer` on; see "Two USDC addresses" below.
+
+## Buyer: agent client
+
+```bash
+npm install @x402/fetch @x402/stellar dotenv
+npm pkg set type=module
+```
+
+```js
+// client.js
+import "dotenv/config";
+import { wrapFetchWithPaymentFromConfig } from "@x402/fetch";
+import { createEd25519Signer } from "@x402/stellar";
+import { ExactStellarScheme } from "@x402/stellar/exact/client";
+
+const NETWORK = process.env.STELLAR_NETWORK || "stellar:testnet";
+
+// createEd25519Signer takes the raw S... secret string and the CAIP-2 network ID.
+// Do NOT pre-wrap with Keypair.fromSecret or call getNetworkPassphrase yourself —
+// the signer does both internally.
+const signer = createEd25519Signer(process.env.STELLAR_SECRET_KEY, NETWORK);
+
+// wrapFetchWithPaymentFromConfig returns a fetch that handles 402 negotiation
+// and auth-entry signing transparently.
+const fetchWithPayment = wrapFetchWithPaymentFromConfig(fetch, {
+  schemes: [{ network: NETWORK, client: new ExactStellarScheme(signer) }],
+});
+
+const res = await fetchWithPayment("http://localhost:3001/weather");
+console.log(await res.json());
+// Paid automatically: 402 negotiation + auth-entry signing under the hood
+```
+
+**Env vars:**
+- `STELLAR_NETWORK` — CAIP-2 network ID; defaults to `stellar:testnet`. Must match the server's network.
+- `STELLAR_SECRET_KEY` — your S... secret key (needs USDC trustline + balance)
+
+**Browser frontends:** this client uses Node `fetch` and `createEd25519Signer`, both of which run in Node. A vanilla browser cannot sign contract auth entries through a typical wallet extension without additional glue. For a browser payer, run the x402 client server-side and expose a thin proxy endpoint to the page, or wire up Wallets-Kit / Freighter with custom auth-entry signing.
+
+## Testnet runbook
+
+You need two Stellar testnet accounts: a **client/payer** (signs and pays from a USDC balance) and a **server/recipient** (the `payTo` in your route config). Both need a USDC trustline.
+
+Two steps are web-only (Captcha or auth form) and cannot be scripted: the Circle USDC faucet and the OZ Channels key generator. Everything else can be automated. A complete `setup.js` sketch lives at the end of this section.
+
+1. **Generate two keypairs**
+   ```bash
+   node -e "const { Keypair } = require('@stellar/stellar-sdk'); for (const n of ['RECIPIENT','PAYER']) { const k = Keypair.random(); console.log(n, k.publicKey(), k.secret()); }"
+   ```
+
+2. **Fund both with testnet XLM (friendbot)**
+   ```bash
+   curl "https://friendbot.stellar.org?addr=RECIPIENT_G..."
+   curl "https://friendbot.stellar.org?addr=PAYER_G..."
+   ```
+
+3. **Add a USDC trustline to BOTH accounts** — open [Stellar Lab](https://lab.stellar.org/account/fund?network=test) and add a USDC trustline to each `G...`, or run via SDK for each keypair:
+   ```js
+   import * as StellarSdk from "@stellar/stellar-sdk";
+
+   const horizon = new StellarSdk.Horizon.Server("https://horizon-testnet.stellar.org");
+   // Circle's classic USDC issuer on Stellar testnet
+   const USDC_ISSUER = "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5";
+
+   async function addTrustline(secret) {
+     const kp = StellarSdk.Keypair.fromSecret(secret);
+     const acc = await horizon.loadAccount(kp.publicKey());
+     const tx = new StellarSdk.TransactionBuilder(acc, {
+       fee: StellarSdk.BASE_FEE,
+       networkPassphrase: StellarSdk.Networks.TESTNET,
+     })
+       .addOperation(StellarSdk.Operation.changeTrust({
+         asset: new StellarSdk.Asset("USDC", USDC_ISSUER),
+       }))
+       .setTimeout(60)
+       .build();
+     tx.sign(kp);
+     return horizon.submitTransaction(tx);
+   }
+
+   // Repeat for both the recipient secret and the payer secret.
+   await addTrustline(process.env.RECIPIENT_SECRET);
+   await addTrustline(process.env.PAYER_SECRET);
+   ```
+
+   Without a trustline on the recipient, the SAC `transfer` settles into nothing and the request fails with `op_no_trust`.
+
+4. **Fund the PAYER with testnet USDC** — open the [Circle testnet faucet](https://faucet.circle.com/), select **Stellar testnet**, paste the payer's `G...`. Web Captcha; no API.
+
+5. **Generate an OZ Channels testnet API key** ([channels.openzeppelin.com/testnet/gen](https://channels.openzeppelin.com/testnet/gen)). **Required, not optional.** Without it the server crashes at startup with `Failed to initialize: no supported payment kinds loaded from any facilitator`.
+
+6. **Fill in `.env`**
+   ```
+   STELLAR_NETWORK=stellar:testnet
+   STELLAR_RECIPIENT=G... (recipient public key)
+   STELLAR_SECRET_KEY=S... (payer secret key)
+   OZ_API_KEY=...
+   ```
+
+7. **Run it**
+   ```bash
+   node server.js
+   # in another terminal
+   node client.js
+   ```
+
+### Optional: setup.js to automate steps 1–3
+
+Drop this in your project and run once. It generates keys, friendbots, and adds USDC trustlines, then writes a starter `.env` so you only need to do the two manual web steps afterward.
+
+```js
+// setup.js
+import fs from "fs/promises";
+import {
+  Keypair, Horizon, Networks, TransactionBuilder, Operation, Asset, BASE_FEE,
+} from "@stellar/stellar-sdk";
+
+const USDC_ISSUER = "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5";
+const horizon = new Horizon.Server("https://horizon-testnet.stellar.org");
+
+const friendbot = (addr) => fetch(`https://friendbot.stellar.org?addr=${addr}`);
+
+async function addTrustline(kp) {
+  const acc = await horizon.loadAccount(kp.publicKey());
+  const tx = new TransactionBuilder(acc, { fee: BASE_FEE, networkPassphrase: Networks.TESTNET })
+    .addOperation(Operation.changeTrust({ asset: new Asset("USDC", USDC_ISSUER) }))
+    .setTimeout(60).build();
+  tx.sign(kp);
+  return horizon.submitTransaction(tx);
+}
+
+const recipient = Keypair.random();
+const payer = Keypair.random();
+await Promise.all([friendbot(recipient.publicKey()), friendbot(payer.publicKey())]);
+await new Promise(r => setTimeout(r, 2000));
+await Promise.all([addTrustline(recipient), addTrustline(payer)]);
+
+await fs.writeFile(".env", `STELLAR_RECIPIENT=${recipient.publicKey()}
+STELLAR_SECRET_KEY=${payer.secret()}
+OZ_API_KEY=
+`);
+
+console.log(`Fund payer with USDC: https://faucet.circle.com  →  ${payer.publicKey()}`);
+console.log(`Get OZ key:          https://channels.openzeppelin.com/testnet/gen  →  paste into OZ_API_KEY`);
+```
+
+## Two USDC addresses (don't confuse them)
+
+USDC on Stellar has two addresses, used in different places. Mixing them up is a common stumble.
+
+| Address | Format | Used for |
+|---------|--------|----------|
+| Classic asset issuer | `G...` (32-byte ed25519 public key) | The `issuer` of the classic USDC asset; used when adding a trustline (`new Asset("USDC", G...)`) |
+| SAC (Stellar Asset Contract) | `C...` (32-byte contract address) | The contract the protocol invokes `transfer` on; used in payment requirements |
+
+Use the exported constants instead of hard-coding when possible:
+
+```js
+import { USDC_TESTNET_ADDRESS, USDC_PUBNET_ADDRESS } from "@x402/stellar";
+// USDC_TESTNET_ADDRESS = "CBIELTK6YBZJU5UP2WWQEUCYKLPU6AUNZ2BQ4WWFEIE3USCIHMXQDAMA"
+// USDC_PUBNET_ADDRESS  = "CCW67TSZV3SSS2HXMBQ5JFGCKJNXKZM7UQUWUZPUTHXSTZLEO7SJMI75"
+```
+
+`payTo` in your route config is always a classic recipient account (`G...`). The SAC address only appears if you set a custom `asset` in the price config for a non-USDC token.
+
+## Mainnet checklist
+
+| Config | Value |
+|--------|-------|
+| Network ID | `stellar:pubnet` |
+| RPC URL | Provider-specific endpoint (see [Stellar RPC providers directory](https://developers.stellar.org/docs/data/apis/rpc/providers)) |
+| Facilitator URL | `https://channels.openzeppelin.com/x402` |
+| USDC SAC | `USDC_PUBNET_ADDRESS` from `@x402/stellar` (currently `CCW67TSZV3SSS2HXMBQ5JFGCKJNXKZM7UQUWUZPUTHXSTZLEO7SJMI75`) |
+| OZ Channels API key | Required ([channels.openzeppelin.com/gen](https://channels.openzeppelin.com/gen)) |
+| Funding | Real USDC on mainnet (CEX, DEX, or bridge) |
+
+Always test on testnet first. To switch a working setup to mainnet, change only the `.env` (`STELLAR_NETWORK=stellar:pubnet`, `FACILITATOR_URL=https://channels.openzeppelin.com/x402`, mainnet `OZ_API_KEY`, and a mainnet `STELLAR_RECIPIENT`); the samples derive their network from `STELLAR_NETWORK`, so no code changes are needed. Both networks require an OZ Channels API key in the `Authorization: Bearer` header.
+
+## Key concepts
+
+**Auth entry signing** — On Stellar, x402 clients sign contract authorization entries, not full transaction envelopes. The facilitator assembles the complete transaction. This is lighter than EVM/Solana signing, and means clients never need to manage sequence numbers or pay fees.
+
+**Fee sponsorship** — OZ Channels pays all Stellar network fees (~$0.00001/tx). Clients need a funded wallet with USDC but zero XLM.
+
+**`exact-v2` scheme** — The Stellar x402 scheme version. Server advertises `scheme: "exact"` + `x402Version: 2`. Don't mix v1 and v2 packages.
+
+**SAC (Stellar Asset Contract)** — USDC on Stellar is a classic asset wrapped in a smart contract. x402 payments invoke `transfer` on the SAC. Any SEP-41 token works; USDC is the default.
+
+**Ledger expiration** — Auth entries include a `max_ledger` bound. Use `latestLedger + 12` (~1 minute at 5s/ledger). Expired entries fail at settlement.
+
+**CAIP-2 network IDs** — `stellar:testnet` and `stellar:pubnet`. These are the exact strings the protocol expects.
+
+## Common pitfalls
+
+**Auth entry expired on settle**
+- Symptom: facilitator returns `isValid: false`, error mentions ledger expiration
+- Fix: ensure client uses `latestLedger + 12` (or higher) as expiration; don't cache auth entries across requests
+
+**Wrong USDC decimal precision**
+- Symptom: payment amount off by 10x or 100x
+- Fix: Stellar USDC uses **7 decimal places** (not 6 like EVM USDC). `$0.001` = `10000` in base units.
+
+**V1/V2 package mismatch**
+- Symptom: TypeScript errors or silent payment failures
+- Fix: use all `@x402/*` packages at the same major version. V2 is multi-chain; don't import V1 `@x402/core` alongside V2 `@x402/stellar`.
+
+**Missing USDC trustline**
+- Symptom: `op_no_trust` error during settlement
+- Fix: add a USDC `changeTrust` operation before attempting any x402 payment (see testnet runbook above)
+
+**OZ Channels 401 on testnet or mainnet**
+- Symptom: facilitator rejects with 401, server logs `Failed to initialize: no supported payment kinds loaded from any facilitator`
+- Fix: an API key is required on **both** networks (this is a recent change). Generate one at [channels.openzeppelin.com/testnet/gen](https://channels.openzeppelin.com/testnet/gen) (testnet) or [channels.openzeppelin.com/gen](https://channels.openzeppelin.com/gen) (mainnet), then set `OZ_API_KEY` and pass it via `createAuthHeaders` (see the Seller example).
+
+**Trustline missing on the recipient**
+- Symptom: `op_no_trust` during settlement, even though the client has USDC
+- Fix: the `payTo` account needs a USDC trustline too. The SAC `transfer` settles the underlying classic asset, which the recipient cannot hold without a trustline. Add `changeTrust` to both accounts during setup.
+
+**Trying to sign auth entries from a browser**
+- Symptom: bundling errors, or a browser wallet that has no API to sign contract auth entries
+- Fix: run the x402 client server-side (e.g. an Express route the browser calls), or use Wallets-Kit / Freighter with custom auth-entry signing. `@x402/fetch` + `createEd25519Signer` target Node and assume a raw secret key.
+
+**Passing a `Keypair` (or a network passphrase) to `createEd25519Signer`**
+- Symptom: `TypeError: encoded argument must be of type String`, or `Error: Unknown Stellar network: Test SDF Network ; September 2015`
+- Fix: the signer takes the raw `S...` secret string and a CAIP-2 network ID. Do **not** wrap with `Keypair.fromSecret` first, and do **not** pre-convert with `getNetworkPassphrase` — both are done internally.
+  ```js
+  // wrong
+  const signer = createEd25519Signer(Keypair.fromSecret(s), getNetworkPassphrase("stellar:testnet"));
+  // right
+  const signer = createEd25519Signer(s, "stellar:testnet");
+  ```
+
+---
+
+# Part 2: MPP — Machine Payments Protocol (Charge + Channel)
+
+
+## When to use MPP
+MPP is the right choice when:
+- You want **no facilitator dependency** — payments settle directly on Stellar via SAC transfers
+- Your AI agent makes **many requests per session** — use channel mode to pay off-chain and settle once
+- You're building a Stellar-native payment stack without relying on third-party infrastructure
+
+Two modes:
+
+| Mode | On-chain txs | Best for |
+|------|-------------|----------|
+| **Charge** | One per request | Per-request payments, no pre-funding required |
+| **Channel** | One deposit + one close | High-frequency agents (100s of requests/session) |
+
+If you need zero-XLM clients or the simplest possible setup, use x402 (Part 1 above) instead.
+
+## Charge mode: per-request payments
+
+Each request triggers a SAC token transfer settled on-chain. No facilitator. Server can optionally sponsor fees so clients don't need XLM.
+
+```bash
+npm install express @stellar/mpp mppx @stellar/stellar-sdk dotenv
+npm pkg set type=module
+```
+
+**Server:**
+
+```js
+// charge-server.js
+import express from "express";
+import { Mppx } from "mppx";
+import * as stellar from "@stellar/mpp/charge/server";
+import * as StellarSdk from "@stellar/stellar-sdk";
+
+const USDC_SAC_TESTNET = "CBIELTK6YBZJU5UP2WWQEUCYKLPU6AUNZ2BQ4WWFEIE3USCIHMXQDAMA";
+const RECIPIENT = process.env.STELLAR_RECIPIENT; // G... address
+
+const mppx = Mppx.create({
+  secretKey: process.env.MPP_SECRET_KEY, // shared secret for credential verification
+  methods: [
+    stellar.charge({
+      recipient: RECIPIENT,
+      currency: USDC_SAC_TESTNET,
+      network: "stellar:testnet",
+      // optional: server pays network fees so clients don't need XLM
+      feePayer: process.env.FEE_PAYER_SECRET
+        ? { envelopeSigner: StellarSdk.Keypair.fromSecret(process.env.FEE_PAYER_SECRET) }
+        : undefined,
+    }),
+  ],
+});
+
+const app = express();
+app.use(express.json());
+
+// mppx middleware: returns 402 with challenge, then validates payment on retry
+app.use(mppx.middleware());
+
+app.get("/data", (req, res) => {
+  res.json({ result: "paid content", price: "$0.001 USDC" });
+});
+
+app.listen(3002, () => console.log("MPP charge server on http://localhost:3002"));
+```
+
+**Client:**
+
+```js
+// charge-client.js
+import { Mppx } from "mppx";
+import * as stellar from "@stellar/mpp/charge/client";
+import * as StellarSdk from "@stellar/stellar-sdk";
+
+const keypair = StellarSdk.Keypair.fromSecret(process.env.STELLAR_SECRET_KEY);
+
+const mppx = Mppx.create({
+  methods: [
+    stellar.charge({
+      keypair,
+      mode: "pull", // server assembles and broadcasts the transaction
+      onProgress(event) {
+        // event.type: "challenge" | "signed" | "settled"
+        if (event.type === "settled") console.log("Settled:", event.txHash);
+      },
+    }),
+  ],
+});
+
+// mppx wraps fetch — 402 handling is transparent
+const res = await mppx.fetch("http://localhost:3002/data");
+console.log(await res.json());
+```
+
+**Env vars (server):** `STELLAR_RECIPIENT`, `MPP_SECRET_KEY`, `FEE_PAYER_SECRET` (optional)
+**Env vars (client):** `STELLAR_SECRET_KEY`
+
+**`mode: "pull"` vs `"push"`:**
+- `"pull"` — client signs auth entries, server assembles + broadcasts (default; use with `feePayer`)
+- `"push"` — client builds and broadcasts the transaction directly (client must have XLM for fees)
+
+## Channel mode: high-frequency off-chain payments
+
+The client deploys a one-way payment channel contract, deposits USDC once, then signs **cumulative commitments** off-chain for each request. No transaction per request — only two on-chain txs total (deposit + close). Ideal for AI agents making hundreds of calls in a session.
+
+### Channel lifecycle
+
+```
+1. Deploy channel contract (one-time)   → C... contract address
+2. Client deposits USDC into channel    → on-chain tx
+3. Per request: client signs commitment → off-chain (just a signature)
+   Amount is cumulative: each sig covers all previous payments + this one
+4. Server closes channel when done      → on-chain tx, settles total
+```
+
+### Prerequisites
+
+- Deploy a one-way-channel smart contract to get a `C...` contract address
+- Generate an ed25519 keypair for commitment signing (see [stellar-mpp SDK](https://github.com/stellar/stellar-mpp-sdk))
+- Fund the channel with USDC before making requests
+
+### Server:
+
+```js
+// channel-server.js
+import express from "express";
+import { Mppx, Store } from "mppx";
+import * as stellar from "@stellar/mpp/channel/server";
+
+const mppx = Mppx.create({
+  secretKey: process.env.MPP_SECRET_KEY,
+  methods: [
+    stellar.channel({
+      channel: process.env.CHANNEL_CONTRACT,       // C... contract address
+      commitmentKey: process.env.COMMITMENT_PUBKEY, // 64-char hex ed25519 public key
+      store: Store.memory(), // dev only — use persistent store in production
+      network: "stellar:testnet",
+    }),
+  ],
+});
+
+const app = express();
+app.use(express.json());
+app.use(mppx.middleware());
+
+app.get("/data", (req, res) => {
+  res.json({ result: "paid content" });
+});
+
+app.listen(3003);
+```
+
+### Client:
+
+```js
+// channel-client.js
+import { Mppx } from "mppx";
+import * as stellar from "@stellar/mpp/channel/client";
+import * as StellarSdk from "@stellar/stellar-sdk";
+
+// commitment key must be a raw ed25519 seed — NOT a standard Stellar secret key
+const commitmentKey = StellarSdk.Keypair.fromRawEd25519Seed(
+  Buffer.from(process.env.COMMITMENT_SECRET, "hex") // 64-char hex secret
+);
+
+const mppx = Mppx.create({
+  methods: [
+    stellar.channel({
+      commitmentKey,
+      onProgress(event) {
+        // event.type: "challenge" | "signed"
+      },
+    }),
+  ],
+});
+
+// Make many requests — each signs a cumulative off-chain commitment
+for (let i = 0; i < 100; i++) {
+  const res = await mppx.fetch("http://localhost:3003/data");
+  console.log(i, await res.json());
+}
+```
+
+### Closing the channel (server-initiated):
+
+```js
+import { close } from "@stellar/mpp/channel/server";
+import * as StellarSdk from "@stellar/stellar-sdk";
+
+const txHash = await close({
+  channel: process.env.CHANNEL_CONTRACT,
+  amount: lastCumulativeAmount, // bigint, total USDC owed in base units
+  signature: lastCommitmentSignature, // hex string from final commitment
+  feePayer: { envelopeSigner: StellarSdk.Keypair.fromSecret(process.env.FEE_PAYER_SECRET) },
+  network: "stellar:testnet",
+});
+// Single on-chain transaction settles the full session
+console.log("Channel closed:", txHash);
+```
+
+**Env vars (server):** `CHANNEL_CONTRACT`, `COMMITMENT_PUBKEY`, `MPP_SECRET_KEY`, `FEE_PAYER_SECRET`
+**Env vars (client):** `COMMITMENT_SECRET`
+
+## Packages and subpath imports
+
+```bash
+npm install @stellar/mpp mppx @stellar/stellar-sdk
+```
+
+| Import path | Recommended import pattern |
+|-------------|----------------------------|
+| `@stellar/mpp/charge/server` | `import * as stellar from "@stellar/mpp/charge/server"` — use `stellar.charge(...)` |
+| `@stellar/mpp/charge/client` | `import * as stellar from "@stellar/mpp/charge/client"` — use `stellar.charge(...)` |
+| `@stellar/mpp/channel/server` | `import * as stellar from "@stellar/mpp/channel/server"` — use `stellar.channel(...)`, `stellar.close(...)`, `stellar.getChannelState(...)`, `stellar.watchChannel(...)` |
+| `@stellar/mpp/channel/client` | `import * as stellar from "@stellar/mpp/channel/client"` — use `stellar.channel(...)` |
+| `@stellar/mpp/channel` | Zod schema definitions for channel types |
+| `mppx` | `import { Mppx, Store } from "mppx"` |
+
+## Testnet runbook
+
+**Steps shared with all protocols:**
+1. Generate keypair + fund with Friendbot (see x402 testnet runbook in Part 1 above)
+2. Add USDC trustline
+3. Get testnet USDC from [Circle faucet](https://faucet.circle.com/)
+
+**Channel mode only:**
+4. Deploy the one-way-channel contract (see [stellar-mpp-sdk](https://github.com/stellar/stellar-mpp-sdk) for deploy script)
+5. Generate a 64-char hex ed25519 seed for the commitment key:
+   ```bash
+   node -e "console.log(require('crypto').randomBytes(32).toString('hex'))"
+   ```
+6. Derive the public key and fund the channel with USDC before making requests
+
+## Common pitfalls
+
+**Channel: wrong commitment key format**
+- Symptom: `Keypair.fromRawEd25519Seed` throws or signatures fail to verify
+- Fix: the commitment key is a raw ed25519 seed as a 64-char hex string — not a Stellar `S...` secret key. Generate with `crypto.randomBytes(32).toString('hex')`.
+
+**Channel: non-cumulative amounts**
+- Symptom: server rejects commitments after the first request
+- Fix: each commitment's `amount` must be the **running total** of all payments so far, not just the price of the current request. The server tracks the highest-seen commitment.
+
+**Channel: deposit TTL expired**
+- Symptom: `close()` fails or channel appears drained
+- Fix: Contract storage has a TTL. Close the channel before it expires, or extend storage TTL via `bumpContractInstance`. Don't leave channels open indefinitely.
+
+**Charge: client has no XLM for fees**
+- Symptom: `op_insufficient_balance` or fee errors on client-submitted transactions
+- Fix: set `mode: "pull"` on the client and configure `feePayer` on the server so the server pays fees. The client only signs auth entries.
+
+**`Store.memory()` in production**
+- Symptom: server loses track of channel state on restart, enables double-spend
+- Fix: replace `Store.memory()` with a persistent store (database-backed) before going to production.
diff --git a/.mintlify/skills/assets/SKILL.md b/.mintlify/skills/assets/SKILL.md
new file mode 100644
index 000000000..3ec534894
--- /dev/null
+++ b/.mintlify/skills/assets/SKILL.md
@@ -0,0 +1,452 @@
+---
+name: assets
+description: Stellar Assets (classic) + trustlines + Stellar Asset Contract (SAC) bridge to smart contracts. Covers asset issuance, distribution, authorization flags, clawback, regulated assets, trustline management, and the SAC interop layer that exposes classic assets as SEP-41 contract tokens. Use when tokenizing real-world assets, issuing stablecoins, managing trustlines, or bridging classic assets to smart contracts.
+user-invocable: true
+argument-hint: "[asset task]"
+---
+
+# Stellar Assets, Trustlines, and SAC
+
+Stellar's native token mechanism: classic asset issuance, trustlines, and the Stellar Asset Contract (SAC) bridge that makes classic assets usable from smart contracts. Default to classic assets over custom contract tokens unless you need custom logic.
+
+## When to use this skill
+- Issuing a new asset (stablecoin, security token, utility token)
+- Setting up trustlines from a client or contract
+- Managing issuer flags (auth required, auth revocable, clawback)
+- Bridging a classic asset into a smart contract via SAC
+- Building regulated-asset flows (compliance, KYC, freeze)
+
+## Related skills
+- Custom token contracts (when classic isn't enough) → `/.well-known/agent-skills/smart-contracts/skill.md`
+- UI flows for trustline creation and asset display → `/.well-known/agent-skills/dapp/skill.md`
+- Looking up balances and trustline state → `/.well-known/agent-skills/data/skill.md`
+- Token-related SEPs (SEP-41, SEP-7, etc.) → `/.well-known/agent-skills/standards/skill.md`
+
+---
+
+
+## Overview
+
+Stellar has two token mechanisms:
+
+1. **Stellar Assets (Classic)**: Built-in, highly efficient, full ecosystem support
+2. **Contract tokens (SEP-41)**: Custom contracts with flexible logic
+
+**Recommendation**: Prefer Stellar Assets unless you need custom token logic.
+
+## Stellar Assets (Classic)
+
+### Asset Types
+
+| Type | Description |
+|------|-------------|
+| Native (XLM) | Stellar's native currency, no trustline needed |
+| Credit | Issued by an account, requires trustline |
+| Liquidity Pool Shares | Represent LP positions |
+
+### Asset Identifiers
+
+```typescript
+import * as StellarSdk from "@stellar/stellar-sdk";
+
+// Native XLM
+const xlm = StellarSdk.Asset.native();
+
+// Credit asset (code + issuer)
+const usdc = new StellarSdk.Asset(
+  "USDC",
+  "GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN"
+);
+
+// Asset code rules:
+// - 1-4 chars: alphanumeric (credit_alphanum4)
+// - 5-12 chars: alphanumeric (credit_alphanum12)
+```
+
+## Issuing Assets
+
+### Create Issuing Account
+
+```typescript
+import * as StellarSdk from "@stellar/stellar-sdk";
+
+const server = new StellarSdk.Horizon.Server("https://horizon-testnet.stellar.org");
+
+// 1. Create issuing account (should be separate from distribution)
+const issuerKeypair = StellarSdk.Keypair.random();
+const distributorKeypair = StellarSdk.Keypair.random();
+
+// 2. Fund accounts (testnet)
+await fetch(`https://friendbot.stellar.org?addr=${issuerKeypair.publicKey()}`);
+await fetch(`https://friendbot.stellar.org?addr=${distributorKeypair.publicKey()}`);
+```
+
+### Issue Asset
+
+```typescript
+const asset = new StellarSdk.Asset("MYTOKEN", issuerKeypair.publicKey());
+
+// 1. Distributor creates trustline to issuer
+const distributorAccount = await server.loadAccount(distributorKeypair.publicKey());
+
+const trustlineTx = new StellarSdk.TransactionBuilder(distributorAccount, {
+  fee: StellarSdk.BASE_FEE,
+  networkPassphrase: StellarSdk.Networks.TESTNET,
+})
+  .addOperation(
+    StellarSdk.Operation.changeTrust({
+      asset: asset,
+      limit: "1000000", // Max amount to hold
+    })
+  )
+  .setTimeout(180)
+  .build();
+
+trustlineTx.sign(distributorKeypair);
+await server.submitTransaction(trustlineTx);
+
+// 2. Issuer sends tokens to distributor
+const issuerAccount = await server.loadAccount(issuerKeypair.publicKey());
+
+const issueTx = new StellarSdk.TransactionBuilder(issuerAccount, {
+  fee: StellarSdk.BASE_FEE,
+  networkPassphrase: StellarSdk.Networks.TESTNET,
+})
+  .addOperation(
+    StellarSdk.Operation.payment({
+      destination: distributorKeypair.publicKey(),
+      asset: asset,
+      amount: "1000000",
+    })
+  )
+  .setTimeout(180)
+  .build();
+
+issueTx.sign(issuerKeypair);
+await server.submitTransaction(issueTx);
+```
+
+### Lock Issuing Account
+
+For fixed-supply tokens, lock the issuer:
+
+```typescript
+const lockTx = new StellarSdk.TransactionBuilder(issuerAccount, {
+  fee: StellarSdk.BASE_FEE,
+  networkPassphrase: StellarSdk.Networks.TESTNET,
+})
+  .addOperation(
+    StellarSdk.Operation.setOptions({
+      masterWeight: 0, // Disable master key
+    })
+  )
+  .setTimeout(180)
+  .build();
+
+lockTx.sign(issuerKeypair);
+await server.submitTransaction(lockTx);
+// Issuer can never issue more tokens
+```
+
+## Asset Flags
+
+Configure issuer account flags for compliance:
+
+```typescript
+const setFlagsTx = new StellarSdk.TransactionBuilder(issuerAccount, {
+  fee: StellarSdk.BASE_FEE,
+  networkPassphrase: StellarSdk.Networks.TESTNET,
+})
+  .addOperation(
+    StellarSdk.Operation.setOptions({
+      setFlags:
+        StellarSdk.AuthRequiredFlag |    // Trustlines require approval
+        StellarSdk.AuthRevocableFlag |   // Can freeze trustlines
+        StellarSdk.AuthClawbackEnabledFlag, // Can clawback tokens
+    })
+  )
+  .setTimeout(180)
+  .build();
+```
+
+### Flag Descriptions
+
+| Flag | Effect |
+|------|--------|
+| `AUTH_REQUIRED` | Users must get approval before receiving tokens |
+| `AUTH_REVOCABLE` | Issuer can freeze user balances |
+| `AUTH_IMMUTABLE` | Flags cannot be changed (permanent) |
+| `AUTH_CLAWBACK_ENABLED` | Issuer can clawback tokens from accounts |
+
+### Authorize Trustline
+
+```typescript
+// When AUTH_REQUIRED is set, approve trustlines:
+const authorizeTx = new StellarSdk.TransactionBuilder(issuerAccount, {
+  fee: StellarSdk.BASE_FEE,
+  networkPassphrase: StellarSdk.Networks.TESTNET,
+})
+  .addOperation(
+    StellarSdk.Operation.setTrustLineFlags({
+      trustor: userPublicKey,
+      asset: asset,
+      flags: {
+        authorized: true,
+        // authorizedToMaintainLiabilities: true, // Partial auth
+      },
+    })
+  )
+  .setTimeout(180)
+  .build();
+```
+
+### Clawback Tokens
+
+```typescript
+// Requires AUTH_CLAWBACK_ENABLED flag
+const clawbackTx = new StellarSdk.TransactionBuilder(issuerAccount, {
+  fee: StellarSdk.BASE_FEE,
+  networkPassphrase: StellarSdk.Networks.TESTNET,
+})
+  .addOperation(
+    StellarSdk.Operation.clawback({
+      asset: asset,
+      from: targetAccountId,
+      amount: "100",
+    })
+  )
+  .setTimeout(180)
+  .build();
+```
+
+## Trustlines
+
+### Create Trustline
+
+```typescript
+const changeTrustTx = new StellarSdk.TransactionBuilder(userAccount, {
+  fee: StellarSdk.BASE_FEE,
+  networkPassphrase: StellarSdk.Networks.TESTNET,
+})
+  .addOperation(
+    StellarSdk.Operation.changeTrust({
+      asset: asset,
+      limit: "10000", // 0 to remove trustline
+    })
+  )
+  .setTimeout(180)
+  .build();
+```
+
+### Check Trustline Status
+
+```typescript
+const account = await server.loadAccount(userPublicKey);
+const trustline = account.balances.find(
+  (b) =>
+    b.asset_type !== "native" &&
+    b.asset_code === "USDC" &&
+    b.asset_issuer === usdcIssuer
+);
+
+if (trustline) {
+  console.log("Balance:", trustline.balance);
+  console.log("Limit:", trustline.limit);
+  console.log("Authorized:", trustline.is_authorized);
+}
+```
+
+## Stellar Asset Contract (SAC)
+
+SAC provides a smart-contract interface for Stellar Assets, enabling smart contract interactions.
+
+### Deploy SAC for Existing Asset
+
+```bash
+# Get the SAC address for an asset
+stellar contract asset deploy \
+  --asset USDC:GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN \
+  --source alice \
+  --network testnet
+```
+
+### SAC Address Derivation
+
+```typescript
+import * as StellarSdk from "@stellar/stellar-sdk";
+
+const asset = new StellarSdk.Asset("USDC", issuerPublicKey);
+const contractId = asset.contractId(StellarSdk.Networks.TESTNET);
+// Returns the deterministic SAC contract address
+```
+
+### Using SAC in Smart Contracts
+
+```rust
+use soroban_sdk::{token::Client as TokenClient, Address, Env};
+
+pub fn transfer_asset(
+    env: Env,
+    from: Address,
+    to: Address,
+    asset_contract: Address,
+    amount: i128,
+) {
+    from.require_auth();
+
+    // Use standard token interface
+    let token = TokenClient::new(&env, &asset_contract);
+    token.transfer(&from, &to, &amount);
+}
+```
+
+### SAC vs Custom Token Interface
+
+SAC implements the standard SEP-41 token interface:
+- `balance(id: Address) -> i128`
+- `transfer(from: Address, to: Address, amount: i128)`
+- `approve(from: Address, spender: Address, amount: i128, expiration_ledger: u32)`
+- `allowance(from: Address, spender: Address) -> i128`
+- `decimals() -> u32`
+- `name() -> String`
+- `symbol() -> Symbol`
+
+## When to Use What
+
+### Use Stellar Assets When:
+- Standard fungible token (currency, stablecoin)
+- Need full ecosystem support (wallets, exchanges)
+- Regulatory compliance features (freeze, clawback)
+- Performance critical (classic operations are cheaper)
+- DEX integration via order book
+
+### Use Custom Contract Tokens When:
+- Complex transfer logic (royalties, fees, restrictions)
+- Custom authorization schemes
+- Non-standard token behaviors
+- Integration with custom DeFi contracts
+- NFTs or semi-fungible tokens
+
+> Reach for a fully custom token as a last resort. Many of the cases above
+> (royalties, fees, transfer restrictions) can be built with a regular
+> issued Stellar asset plus a thin "SAC admin" contract that drives the
+> SAC's `mint`, `burn`, and `clawback` functions. That keeps the ecosystem
+> compatibility of a normal asset (DEX, anchors, wallets, trustlines) while
+> still layering on custom logic. Prefer a custom contract token only when
+> you need token behavior the SAC genuinely cannot express.
+
+### Use SAC When:
+- Need a Stellar asset inside a smart contract
+- Building DeFi protocols with existing assets
+- Bridge between classic and smart contract operations
+
+## Querying Assets
+
+### Get Account Balances
+
+```typescript
+const account = await server.loadAccount(publicKey);
+
+for (const balance of account.balances) {
+  if (balance.asset_type === "native") {
+    console.log("XLM:", balance.balance);
+  } else {
+    console.log(`${balance.asset_code}:`, balance.balance);
+  }
+}
+```
+
+### Find Assets
+
+```typescript
+// Search for assets by code
+const assets = await server
+  .assets()
+  .forCode("USDC")
+  .call();
+
+// Get specific asset details
+const assetDetails = await server
+  .assets()
+  .forCode("USDC")
+  .forIssuer(issuerPublicKey)
+  .call();
+```
+
+### Get Asset Statistics
+
+```typescript
+const stats = await server
+  .assets()
+  .forCode("USDC")
+  .forIssuer(issuerPublicKey)
+  .call();
+
+// stats includes:
+// - amount: total issued
+// - num_accounts: trustline count
+// - flags: issuer flags
+```
+
+## SEP Standards for Assets
+
+### SEP-0001 (stellar.toml)
+
+Publish asset metadata in your domain's `/.well-known/stellar.toml`:
+
+```toml
+[[CURRENCIES]]
+code = "MYTOKEN"
+issuer = "GABC..."
+display_decimals = 2
+name = "My Token"
+desc = "A description of my token"
+image = "https://example.com/token-logo.png"
+```
+
+### SEP-0010 (Web Authentication)
+
+Authenticate users with their Stellar accounts:
+
+```typescript
+// Server generates challenge
+// Client signs with wallet
+// Server verifies signature
+```
+
+### SEP-0024 (Hosted Deposit/Withdrawal)
+
+For fiat on/off ramps:
+
+```typescript
+// Interactive flow for deposits/withdrawals
+// Anchor handles KYC and fiat transfer
+```
+
+### SEP-0045 (Web Auth for Contract Accounts)
+
+Extends SEP-10 to support contract accounts (`C...` addresses) for web authentication. Required for smart wallet / passkey-based anchor integrations. See [SEP-0045](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0045.md).
+
+### SEP-0050 (Non-Fungible Tokens)
+
+Standard contract interface for NFTs on Stellar. Reference implementations available in [OpenZeppelin Stellar Contracts](https://github.com/OpenZeppelin/stellar-contracts) with Base, Consecutive, and Enumerable variants. See [SEP-0050](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0050.md).
+
+## Best Practices
+
+### Asset Issuance
+- Use separate issuing and distribution accounts
+- Lock issuer after initial distribution for fixed supply
+- Publish stellar.toml with asset metadata
+- Consider multisig for issuer account
+
+### Trustline Management
+- Check trustline exists before sending payments
+- Handle trustline creation in onboarding flow
+- Respect trustline limits
+- Monitor for frozen/deauthorized status
+
+### Security
+- Validate asset issuer, not just code
+- Be cautious of assets with clawback enabled
+- Verify stellar.toml from authoritative source
+- Use well-known asset lists for common tokens
diff --git a/.mintlify/skills/dapp/SKILL.md b/.mintlify/skills/dapp/SKILL.md
new file mode 100644
index 000000000..c5e6a729e
--- /dev/null
+++ b/.mintlify/skills/dapp/SKILL.md
@@ -0,0 +1,684 @@
+---
+name: dapp
+description: Stellar dApp / frontend development. Covers the JavaScript stellar-sdk (browser + Node.js), Freighter wallet, Stellar Wallets Kit (multi-wallet), Wallet Standard, smart accounts with passkeys, transaction building / signing / submission, smart contract invocation from the client, simulation, and error handling. Use when building a React/Next.js/Node.js app that talks to Stellar — classic operations or smart contracts.
+user-invocable: true
+argument-hint: "[dapp task]"
+---
+
+# Stellar dApp / Frontend
+
+Client-side development with `@stellar/stellar-sdk`, wallet connection, signing, and submitting transactions. Covers both classic Stellar operations and smart contract invocation from the browser or Node.js.
+
+## When to use this skill
+- Connecting Freighter or other wallets via Stellar Wallets Kit
+- Building, simulating, signing, and submitting transactions
+- Invoking Stellar smart contracts from a frontend
+- Implementing smart accounts with passkeys
+- Handling network passphrases (Mainnet / Testnet / local)
+
+## Related skills
+- Writing the contract being invoked → `/.well-known/agent-skills/smart-contracts/skill.md`
+- Issuing assets and managing trustlines → `/.well-known/agent-skills/assets/skill.md`
+- Querying chain state via RPC / Horizon → `/.well-known/agent-skills/data/skill.md`
+- Building paid APIs or agent payment clients → `/.well-known/agent-skills/agentic-payments/skill.md`
+- SEPs the wallet/anchor flows depend on → `/.well-known/agent-skills/standards/skill.md`
+
+---
+
+
+## Goals
+- Single SDK instance for the app (RPC/Horizon + transaction building)
+- Freighter wallet integration (or multi-wallet via Stellar Wallets Kit)
+- Clean separation of client/server in Next.js
+- Transaction sending with proper confirmation handling
+
+## Quick Navigation
+- SDK setup and env config: [SDK Initialization](#sdk-initialization)
+- Wallet integrations: [Wallet Integration](#wallet-integration)
+- Tx build/send patterns: [Transaction Building](#transaction-building), [Transaction Submission](#transaction-submission)
+- React + Next.js patterns: [React Components](#react-components), [Next.js App Router Setup](#nextjs-app-router-setup)
+- Smart wallets/passkeys: [Smart Accounts (Passkey Wallets)](#smart-accounts-passkey-wallets)
+- Production UX checklist: [Transaction UX Checklist](#transaction-ux-checklist)
+
+## Recommended Dependencies
+
+> **Requires Node.js 20+** — the Stellar SDK dropped Node 18 support.
+
+```bash
+npm install @stellar/stellar-sdk @stellar/freighter-api
+# Or for multi-wallet support:
+npm install @stellar/stellar-sdk @creit.tech/stellar-wallets-kit
+```
+
+## SDK Initialization
+
+> For the full API reference (RPC methods, Horizon endpoints, migration guide), see [api-rpc-horizon.md](/.well-known/agent-skills/data/skill.md).
+
+### Basic Setup
+```typescript
+import * as StellarSdk from "@stellar/stellar-sdk";
+
+// For Testnet
+const testnetServer = new StellarSdk.Horizon.Server("https://horizon-testnet.stellar.org");
+const testnetRpc = new StellarSdk.rpc.Server("https://soroban-testnet.stellar.org");
+const testnetNetworkPassphrase = StellarSdk.Networks.TESTNET;
+
+// For Mainnet
+const mainnetServer = new StellarSdk.Horizon.Server("https://horizon.stellar.org");
+const mainnetRpcUrl = process.env.NEXT_PUBLIC_STELLAR_MAINNET_RPC_URL;
+if (!mainnetRpcUrl) throw new Error("Missing NEXT_PUBLIC_STELLAR_MAINNET_RPC_URL");
+const mainnetRpc = new StellarSdk.rpc.Server(mainnetRpcUrl); // set from your chosen RPC provider
+const mainnetNetworkPassphrase = StellarSdk.Networks.PUBLIC;
+```
+
+### Environment Configuration
+> Use a provider-specific mainnet RPC URL (see: https://developers.stellar.org/docs/data/apis/rpc/providers).
+
+```typescript
+// lib/stellar.ts
+import * as StellarSdk from "@stellar/stellar-sdk";
+
+const NETWORK = process.env.NEXT_PUBLIC_STELLAR_NETWORK || "testnet";
+
+const requireEnv = (name: string): string => {
+  const value = process.env[name];
+  if (!value) throw new Error(`Missing required env var: ${name}`);
+  return value;
+};
+
+export const config = {
+  testnet: {
+    horizonUrl: "https://horizon-testnet.stellar.org",
+    rpcUrl: "https://soroban-testnet.stellar.org",
+    networkPassphrase: StellarSdk.Networks.TESTNET,
+    friendbotUrl: "https://friendbot.stellar.org",
+  },
+  mainnet: {
+    horizonUrl: "https://horizon.stellar.org",
+    rpcUrl: requireEnv("NEXT_PUBLIC_STELLAR_MAINNET_RPC_URL"),
+    networkPassphrase: StellarSdk.Networks.PUBLIC,
+    friendbotUrl: null,
+  },
+}[NETWORK]!;
+
+export const horizon = new StellarSdk.Horizon.Server(config.horizonUrl);
+export const rpc = new StellarSdk.rpc.Server(config.rpcUrl);
+```
+
+## Wallet Integration
+
+### Freighter (Primary Browser Wallet)
+```typescript
+// hooks/useFreighter.ts
+import { useState, useEffect, useCallback } from "react";
+import {
+  isConnected,
+  getAddress,
+  requestAccess,
+  signTransaction,
+  getNetwork,
+} from "@stellar/freighter-api";
+
+export function useFreighter() {
+  const [connected, setConnected] = useState(false);
+  const [address, setAddress] = useState<string | null>(null);
+  const [network, setNetwork] = useState<string | null>(null);
+
+  useEffect(() => {
+    checkConnection();
+  }, []);
+
+  const checkConnection = async () => {
+    const { isConnected: installed, error } = await isConnected();
+    if (error || !installed) return;
+
+    // getAddress returns address: "" until the app has been granted access,
+    // so a non-empty address means we're already authorized.
+    const { address: addr, error: addressError } = await getAddress();
+    if (addressError || !addr) return;
+
+    const { network: net, error: networkError } = await getNetwork();
+    if (networkError) return;
+    setConnected(true);
+    setAddress(addr);
+    setNetwork(net);
+  };
+
+  const connect = useCallback(async () => {
+    const { isConnected: installed, error } = await isConnected();
+    if (error || !installed) {
+      throw new Error("Freighter extension not installed");
+    }
+
+    // requestAccess prompts the user and returns the granted address.
+    const { address: addr, error: accessError } = await requestAccess();
+    if (accessError) throw new Error(accessError.message);
+
+    const { network: net, error: networkError } = await getNetwork();
+    if (networkError) throw new Error(networkError.message);
+    setConnected(true);
+    setAddress(addr);
+    setNetwork(net);
+
+    return addr;
+  }, []);
+
+  const disconnect = useCallback(() => {
+    setConnected(false);
+    setAddress(null);
+    setNetwork(null);
+  }, []);
+
+  const sign = useCallback(
+    async (xdr: string, networkPassphrase: string) => {
+      if (!connected) throw new Error("Wallet not connected");
+      const { signedTxXdr, error } = await signTransaction(xdr, {
+        networkPassphrase,
+      });
+      if (error) throw new Error(error.message);
+      return signedTxXdr;
+    },
+    [connected]
+  );
+
+  return { connected, address, network, connect, disconnect, sign };
+}
+```
+
+### Stellar Wallets Kit (Multi-Wallet)
+```typescript
+// hooks/useStellarWallet.ts
+import { useState, useCallback } from "react";
+import {
+  StellarWalletsKit,
+  WalletNetwork,
+  allowAllModules,
+  FREIGHTER_ID,
+  LOBSTR_ID,
+  XBULL_ID,
+} from "@creit.tech/stellar-wallets-kit";
+
+const kit = new StellarWalletsKit({
+  network: WalletNetwork.TESTNET,
+  selectedWalletId: FREIGHTER_ID,
+  modules: allowAllModules(),
+});
+
+export function useStellarWallet() {
+  const [address, setAddress] = useState<string | null>(null);
+
+  const connect = useCallback(async () => {
+    await kit.openModal({
+      onWalletSelected: async (option) => {
+        kit.setWallet(option.id);
+        const { address } = await kit.getAddress();
+        setAddress(address);
+      },
+    });
+  }, []);
+
+  const disconnect = useCallback(() => {
+    setAddress(null);
+  }, []);
+
+  const sign = useCallback(async (xdr: string) => {
+    const { signedTxXdr } = await kit.signTransaction(xdr);
+    return signedTxXdr;
+  }, []);
+
+  return { address, connect, disconnect, sign, kit };
+}
+```
+
+## Transaction Building
+
+### Basic Payment
+```typescript
+import * as StellarSdk from "@stellar/stellar-sdk";
+import { horizon, config } from "@/lib/stellar";
+
+export async function buildPaymentTx(
+  sourceAddress: string,
+  destinationAddress: string,
+  amount: string,
+  asset: StellarSdk.Asset = StellarSdk.Asset.native()
+) {
+  const account = await horizon.loadAccount(sourceAddress);
+
+  const transaction = new StellarSdk.TransactionBuilder(account, {
+    fee: StellarSdk.BASE_FEE,
+    networkPassphrase: config.networkPassphrase,
+  })
+    .addOperation(
+      StellarSdk.Operation.payment({
+        destination: destinationAddress,
+        asset: asset,
+        amount: amount,
+      })
+    )
+    .setTimeout(180)
+    .build();
+
+  return transaction.toXDR();
+}
+```
+
+### Smart Contract Invocation
+```typescript
+import * as StellarSdk from "@stellar/stellar-sdk";
+import { rpc, config } from "@/lib/stellar";
+
+export async function invokeContract(
+  sourceAddress: string,
+  contractId: string,
+  method: string,
+  args: StellarSdk.xdr.ScVal[]
+) {
+  const account = await rpc.getAccount(sourceAddress);
+
+  const contract = new StellarSdk.Contract(contractId);
+
+  let transaction = new StellarSdk.TransactionBuilder(account, {
+    fee: StellarSdk.BASE_FEE,
+    networkPassphrase: config.networkPassphrase,
+  })
+    .addOperation(contract.call(method, ...args))
+    .setTimeout(180)
+    .build();
+
+  // Simulate to get resource estimates
+  const simulation = await rpc.simulateTransaction(transaction);
+
+  if (StellarSdk.rpc.Api.isSimulationError(simulation)) {
+    throw new Error(`Simulation failed: ${simulation.error}`);
+  }
+
+  // Assemble with proper resources
+  transaction = StellarSdk.rpc.assembleTransaction(
+    transaction,
+    simulation
+  ).build();
+
+  return transaction.toXDR();
+}
+```
+
+### Building ScVal Arguments
+```typescript
+import * as StellarSdk from "@stellar/stellar-sdk";
+
+// Common conversions
+const addressVal = StellarSdk.Address.fromString(address).toScVal();
+const i128Val = StellarSdk.nativeToScVal(BigInt(amount), { type: "i128" });
+const u32Val = StellarSdk.nativeToScVal(42, { type: "u32" });
+const stringVal = StellarSdk.nativeToScVal("hello", { type: "string" });
+const symbolVal = StellarSdk.nativeToScVal("transfer", { type: "symbol" });
+
+// Struct
+const structVal = StellarSdk.nativeToScVal(
+  { name: "Token", decimals: 7 },
+  {
+    type: {
+      name: ["symbol", null],
+      decimals: ["u32", null],
+    },
+  }
+);
+
+// Vec
+const vecVal = StellarSdk.nativeToScVal([1, 2, 3], { type: "i128" });
+```
+
+## Transaction Submission
+
+### Submit and Wait for Confirmation
+```typescript
+import * as StellarSdk from "@stellar/stellar-sdk";
+import { rpc, horizon, config } from "@/lib/stellar";
+
+export async function submitTransaction(signedXdr: string) {
+  const transaction = StellarSdk.TransactionBuilder.fromXDR(
+    signedXdr,
+    config.networkPassphrase
+  );
+
+  // For smart contract transactions, use RPC
+  if (transaction.operations.some(op => op.type === "invokeHostFunction")) {
+    return submitSorobanTransaction(signedXdr);
+  }
+
+  // For classic transactions, use Horizon
+  return submitClassicTransaction(signedXdr);
+}
+
+async function submitSorobanTransaction(signedXdr: string) {
+  const transaction = StellarSdk.TransactionBuilder.fromXDR(
+    signedXdr,
+    config.networkPassphrase
+  ) as StellarSdk.Transaction;
+
+  const response = await rpc.sendTransaction(transaction);
+
+  if (response.status === "ERROR") {
+    throw new Error(`Transaction failed: ${response.errorResult}`);
+  }
+
+  // Poll for completion
+  let getResponse = await rpc.getTransaction(response.hash);
+  while (getResponse.status === "NOT_FOUND") {
+    await new Promise((resolve) => setTimeout(resolve, 1000));
+    getResponse = await rpc.getTransaction(response.hash);
+  }
+
+  if (getResponse.status === "SUCCESS") {
+    return {
+      hash: response.hash,
+      result: getResponse.returnValue,
+    };
+  }
+
+  throw new Error(`Transaction failed: ${getResponse.status}`);
+}
+
+async function submitClassicTransaction(signedXdr: string) {
+  const transaction = StellarSdk.TransactionBuilder.fromXDR(
+    signedXdr,
+    config.networkPassphrase
+  ) as StellarSdk.Transaction;
+
+  const response = await horizon.submitTransaction(transaction);
+  return {
+    hash: response.hash,
+    ledger: response.ledger,
+  };
+}
+```
+
+## React Components
+
+### Connect Wallet Button
+```tsx
+// components/ConnectButton.tsx
+"use client";
+
+import { useFreighter } from "@/hooks/useFreighter";
+
+export function ConnectButton() {
+  const { connected, address, connect, disconnect } = useFreighter();
+
+  if (connected && address) {
+    return (
+      <div className="flex items-center gap-2">
+        <span className="text-sm">
+          {address.slice(0, 4)}...{address.slice(-4)}
+        </span>
+        <button
+          onClick={disconnect}
+          className="px-4 py-2 bg-red-500 text-white rounded"
+        >
+          Disconnect
+        </button>
+      </div>
+    );
+  }
+
+  return (
+    <button
+      onClick={connect}
+      className="px-4 py-2 bg-blue-500 text-white rounded"
+    >
+      Connect Wallet
+    </button>
+  );
+}
+```
+
+### Send Payment Form
+```tsx
+// components/SendPayment.tsx
+"use client";
+
+import { useState } from "react";
+import { useFreighter } from "@/hooks/useFreighter";
+import { buildPaymentTx, submitTransaction } from "@/lib/transactions";
+
+export function SendPayment() {
+  const { address, sign } = useFreighter();
+  const [destination, setDestination] = useState("");
+  const [amount, setAmount] = useState("");
+  const [status, setStatus] = useState<string | null>(null);
+  const [loading, setLoading] = useState(false);
+
+  const handleSubmit = async (e: React.FormEvent) => {
+    e.preventDefault();
+    if (!address) return;
+
+    setLoading(true);
+    setStatus("Building transaction...");
+
+    try {
+      const xdr = await buildPaymentTx(address, destination, amount);
+
+      setStatus("Please sign in your wallet...");
+      const signedXdr = await sign(xdr, config.networkPassphrase);
+
+      setStatus("Submitting transaction...");
+      const result = await submitTransaction(signedXdr);
+
+      setStatus(`Success! Hash: ${result.hash}`);
+    } catch (error) {
+      setStatus(`Error: ${error.message}`);
+    } finally {
+      setLoading(false);
+    }
+  };
+
+  return (
+    <form onSubmit={handleSubmit} className="space-y-4">
+      <input
+        type="text"
+        placeholder="Destination Address"
+        value={destination}
+        onChange={(e) => setDestination(e.target.value)}
+        className="w-full p-2 border rounded"
+      />
+      <input
+        type="text"
+        placeholder="Amount (XLM)"
+        value={amount}
+        onChange={(e) => setAmount(e.target.value)}
+        className="w-full p-2 border rounded"
+      />
+      <button
+        type="submit"
+        disabled={loading || !address}
+        className="w-full p-2 bg-blue-500 text-white rounded disabled:opacity-50"
+      >
+        {loading ? "Processing..." : "Send"}
+      </button>
+      {status && <p className="text-sm">{status}</p>}
+    </form>
+  );
+}
+```
+
+## Next.js App Router Setup
+
+### Provider Component
+```tsx
+// app/providers.tsx
+"use client";
+
+import { ReactNode } from "react";
+
+// Add any context providers here
+export function Providers({ children }: { children: ReactNode }) {
+  return <>{children}</>;
+}
+```
+
+### Layout
+```tsx
+// app/layout.tsx
+import { Providers } from "./providers";
+
+export default function RootLayout({
+  children,
+}: {
+  children: React.ReactNode;
+}) {
+  return (
+    <html lang="en">
+      <body>
+        <Providers>{children}</Providers>
+      </body>
+    </html>
+  );
+}
+```
+
+## Data Fetching
+
+### Account Balance
+```typescript
+import { horizon } from "@/lib/stellar";
+
+export async function getBalance(address: string) {
+  try {
+    const account = await horizon.loadAccount(address);
+    const nativeBalance = account.balances.find(
+      (b) => b.asset_type === "native"
+    );
+    return nativeBalance?.balance || "0";
+  } catch (error) {
+    if (error.response?.status === 404) {
+      return "0"; // Account not funded
+    }
+    throw error;
+  }
+}
+```
+
+### Contract State
+```typescript
+import * as StellarSdk from "@stellar/stellar-sdk";
+import { rpc } from "@/lib/stellar";
+
+export async function getContractData(
+  contractId: string,
+  key: StellarSdk.xdr.ScVal
+) {
+  const ledgerKey = StellarSdk.xdr.LedgerKey.contractData(
+    new StellarSdk.xdr.LedgerKeyContractData({
+      contract: new StellarSdk.Address(contractId).toScAddress(),
+      key: key,
+      durability: StellarSdk.xdr.ContractDataDurability.persistent(),
+    })
+  );
+
+  const entries = await rpc.getLedgerEntries(ledgerKey);
+
+  if (entries.entries.length === 0) {
+    return null;
+  }
+
+  return StellarSdk.scValToNative(
+    entries.entries[0].val.contractData().val()
+  );
+}
+```
+
+## Smart Accounts (Passkey Wallets)
+
+For passwordless authentication using WebAuthn passkeys, use Smart Account Kit.
+
+### Installation
+```bash
+npm install smart-account-kit
+```
+
+### Quick Start
+```typescript
+import { SmartAccountKit, IndexedDBStorage } from 'smart-account-kit';
+
+const kit = new SmartAccountKit({
+  rpcUrl: 'https://soroban-testnet.stellar.org',
+  networkPassphrase: 'Test SDF Network ; September 2015',
+  accountWasmHash: 'YOUR_ACCOUNT_WASM_HASH',
+  webauthnVerifierAddress: 'CWEBAUTHN_VERIFIER_ADDRESS',
+  storage: new IndexedDBStorage(),
+});
+
+// On page load - silent restore from stored session
+const result = await kit.connectWallet();
+if (!result) {
+  showConnectButton(); // No stored session
+}
+
+// Create new wallet with passkey
+const { contractId, credentialId } = await kit.createWallet(
+  'My App',
+  'user@example.com',
+  { autoSubmit: true }
+);
+
+// Connect to existing wallet (prompts for passkey)
+await kit.connectWallet({ prompt: true });
+
+// Sign and submit transactions
+const result = await kit.signAndSubmit(transaction);
+
+// Transfer tokens
+await kit.transfer(tokenContract, recipient, amount);
+```
+
+### Key Features
+- **Session Management**: Automatic credential persistence and silent reconnection
+- **Multiple Signer Types**: Passkeys (secp256r1), Ed25519 keys, policies
+- **Context Rules**: Fine-grained authorization for different operations
+- **Policy Support**: Threshold multisig, spending limits, custom policies
+- **External Wallet Support**: Connect Freighter, LOBSTR via adapters
+- **Gasless Transactions**: Optional relayer integration for fee sponsoring
+
+### Fee Sponsorship with OpenZeppelin Relayer
+
+The [OpenZeppelin Relayer](https://docs.openzeppelin.com/relayer/stellar) (also called Stellar Channels Service) handles gasless transaction submission. It replaces the deprecated Launchtube service and uses Stellar's native fee bump mechanism so users don't need XLM for fees.
+
+```typescript
+import * as RPChannels from "@openzeppelin/relayer-plugin-channels";
+
+const client = new RPChannels.ChannelsClient({
+  baseUrl: "https://channels.openzeppelin.com/testnet",
+  apiKey: "your-api-key",
+});
+
+// Submit a smart contract call with fee sponsorship
+const response = await client.submitSorobanTransaction({
+  func: contractFunc,
+  auth: contractAuth,
+});
+```
+
+- **Testnet hosted instance**: `https://channels.openzeppelin.com/testnet` (API keys at `/gen`)
+- **Production**: Self-host via Docker ([GitHub](https://github.com/OpenZeppelin/openzeppelin-relayer))
+- **Stellar docs**: https://developers.stellar.org/docs/tools/openzeppelin-relayer
+
+### Resources
+- **GitHub**: https://github.com/kalepail/smart-account-kit
+- **OpenZeppelin Contracts**: https://github.com/OpenZeppelin/stellar-contracts
+- **Legacy SDK**: https://github.com/kalepail/passkey-kit (for simpler use cases)
+
+## Transaction UX Checklist
+
+- [ ] Show loading state during wallet signing
+- [ ] Display transaction hash immediately after submission
+- [ ] Track confirmation status (pending → success/failed)
+- [ ] Handle common errors with clear messages:
+  - Wallet not connected
+  - User rejected signing
+  - Insufficient XLM for fees
+  - Account not funded
+  - Network mismatch (wallet on wrong network)
+  - Transaction timeout/expired
+- [ ] Prevent double-submission while processing
+- [ ] Show destination and amount before signing
diff --git a/.mintlify/skills/data/SKILL.md b/.mintlify/skills/data/SKILL.md
new file mode 100644
index 000000000..84850ac49
--- /dev/null
+++ b/.mintlify/skills/data/SKILL.md
@@ -0,0 +1,546 @@
+---
+name: data
+description: Querying Stellar chain data via Stellar RPC (preferred) and Horizon (legacy). Covers RPC JSON-RPC methods, Horizon REST endpoints, streaming, pagination, historical queries, Hubble/Galexie for deep history, and the RPC/Horizon migration story. Use when reading balances, transactions, operations, ledgers, contract events, or building any indexer/analytics workflow.
+user-invocable: true
+argument-hint: "[data task]"
+---
+
+# Stellar Data: RPC + Horizon
+
+API access for reading chain state. Stellar RPC is the preferred entry point for new projects; Horizon remains for legacy and historical-query workflows. For deeper history beyond RPC's 7-day window, use Hubble/Galexie.
+
+## When to use this skill
+- Calling Stellar RPC methods (`getLatestLedger`, `getLedgerEntries`, `getEvents`, `simulateTransaction`, `sendTransaction`)
+- Querying Horizon endpoints (accounts, transactions, operations, effects, ledgers)
+- Streaming live events or operations
+- Pulling historical data beyond RPC's 7-day window (Hubble, Galexie)
+- Choosing between RPC and Horizon for a given workflow
+
+## Related skills
+- Building transactions to send → `/.well-known/agent-skills/dapp/skill.md`
+- Smart contract simulation and event emission → `/.well-known/agent-skills/smart-contracts/skill.md`
+- Asset balance and trustline lookups → `/.well-known/agent-skills/assets/skill.md`
+- Standards (SEP-7 deeplinks, SEP-10 auth) → `/.well-known/agent-skills/standards/skill.md`
+
+---
+
+
+## Overview
+
+Stellar provides two API paradigms:
+
+| API | Status | Use Case |
+|-----|--------|----------|
+| **Stellar RPC** | Preferred | Smart contracts, real-time state, new projects |
+| **Horizon** | Legacy-focused | Historical data, legacy applications |
+
+**Recommendation**: Use Stellar RPC for all new projects. Use Horizon mainly for historical queries and legacy compatibility paths.
+
+## Quick Navigation
+- RPC methods and usage: [Stellar RPC](#stellar-rpc)
+- Horizon endpoints and streaming: [Horizon API (Legacy)](#horizon-api-legacy)
+- Migration strategy: [Migration: Horizon to RPC](#migration-horizon-to-rpc)
+- Data history/indexing options: [Historical Data Access](#historical-data-access)
+- Environment setup and endpoints: [Network Configuration](#network-configuration)
+
+## Stellar RPC
+
+### Endpoints
+
+> Note: SDF directly provides Futurenet public RPC. For Mainnet RPC, select a provider from the [RPC providers directory](https://developers.stellar.org/docs/data/apis/rpc/providers).
+
+| Network | RPC URL |
+|---------|---------|
+| Mainnet | Provider-specific endpoint (see [RPC providers directory](https://developers.stellar.org/docs/data/apis/rpc/providers)) |
+| Testnet | `https://soroban-testnet.stellar.org` |
+| Futurenet | `https://rpc-futurenet.stellar.org` |
+| Local | `http://localhost:8000/soroban/rpc` |
+
+### Setup
+
+```typescript
+import * as StellarSdk from "@stellar/stellar-sdk";
+
+const rpc = new StellarSdk.rpc.Server("https://soroban-testnet.stellar.org");
+```
+
+### Key Methods
+
+#### Get Account
+
+```typescript
+const account = await rpc.getAccount(publicKey);
+// Returns account with sequence number for transaction building
+```
+
+#### Get Health
+
+```typescript
+const health = await rpc.getHealth();
+// { status: "healthy" }
+```
+
+#### Get Latest Ledger
+
+```typescript
+const ledger = await rpc.getLatestLedger();
+// { id: "...", sequence: 123456, protocolVersion: 25 }
+```
+
+#### Get Ledger Entries
+
+```typescript
+// Read contract storage
+const key = StellarSdk.xdr.LedgerKey.contractData(
+  new StellarSdk.xdr.LedgerKeyContractData({
+    contract: new StellarSdk.Address(contractId).toScAddress(),
+    key: StellarSdk.xdr.ScVal.scvSymbol("Counter"),
+    durability: StellarSdk.xdr.ContractDataDurability.persistent(),
+  })
+);
+
+const entries = await rpc.getLedgerEntries(key);
+if (entries.entries.length > 0) {
+  const value = StellarSdk.scValToNative(
+    entries.entries[0].val.contractData().val()
+  );
+}
+```
+
+#### Simulate Transaction
+
+```typescript
+const simulation = await rpc.simulateTransaction(transaction);
+
+if (StellarSdk.rpc.Api.isSimulationError(simulation)) {
+  console.error("Simulation failed:", simulation.error);
+} else if (StellarSdk.rpc.Api.isSimulationSuccess(simulation)) {
+  console.log("Cost:", simulation.cost);
+  console.log("Result:", simulation.result);
+}
+```
+
+#### Send Transaction
+
+```typescript
+const response = await rpc.sendTransaction(signedTransaction);
+
+if (response.status === "PENDING") {
+  // Poll for result
+  let result = await rpc.getTransaction(response.hash);
+  while (result.status === "NOT_FOUND") {
+    await new Promise(r => setTimeout(r, 1000));
+    result = await rpc.getTransaction(response.hash);
+  }
+
+  if (result.status === "SUCCESS") {
+    console.log("Success:", result.returnValue);
+  } else {
+    console.error("Failed:", result.status);
+  }
+}
+```
+
+#### Get Transaction
+
+```typescript
+const tx = await rpc.getTransaction(txHash);
+// status: "SUCCESS" | "FAILED" | "NOT_FOUND"
+// returnValue: ScVal (for contract calls)
+// ledger: number
+```
+
+#### Get Events
+
+```typescript
+const events = await rpc.getEvents({
+  startLedger: 1000000,
+  filters: [
+    {
+      type: "contract",
+      contractIds: [contractId],
+      topics: [
+        ["*", StellarSdk.xdr.ScVal.scvSymbol("transfer").toXDR("base64")],
+      ],
+    },
+  ],
+});
+
+for (const event of events.events) {
+  console.log("Event:", event.topic, event.value);
+}
+```
+
+### RPC Limitations
+
+- **7-day history for most methods**: `getTransaction`, `getEvents`, etc. only cover recent data
+- **`getLedgers` exception**: "Infinite Scroll" feature queries any ledger back to genesis via the data lake
+- **No streaming**: Poll for updates (no WebSocket)
+- **Contract-focused**: Limited classic Stellar data
+
+## Horizon API (Legacy)
+
+### Endpoints
+
+| Network | Horizon URL |
+|---------|-------------|
+| Mainnet | `https://horizon.stellar.org` |
+| Testnet | `https://horizon-testnet.stellar.org` |
+| Local | `http://localhost:8000` |
+
+### Setup
+
+```typescript
+import * as StellarSdk from "@stellar/stellar-sdk";
+
+const server = new StellarSdk.Horizon.Server("https://horizon-testnet.stellar.org");
+```
+
+### Common Operations
+
+#### Load Account
+
+```typescript
+const account = await server.loadAccount(publicKey);
+// Full account details including balances, signers, data
+```
+
+#### Get Account Balances
+
+```typescript
+const account = await server.loadAccount(publicKey);
+for (const balance of account.balances) {
+  if (balance.asset_type === "native") {
+    console.log("XLM:", balance.balance);
+  } else {
+    console.log(`${balance.asset_code}:`, balance.balance);
+  }
+}
+```
+
+#### Get Transactions
+
+```typescript
+// Account transactions
+const transactions = await server
+  .transactions()
+  .forAccount(publicKey)
+  .order("desc")
+  .limit(10)
+  .call();
+
+// Specific transaction
+const tx = await server
+  .transactions()
+  .transaction(txHash)
+  .call();
+```
+
+#### Get Operations
+
+```typescript
+const operations = await server
+  .operations()
+  .forAccount(publicKey)
+  .order("desc")
+  .limit(20)
+  .call();
+
+for (const op of operations.records) {
+  console.log(op.type, op.created_at);
+}
+```
+
+#### Get Payments
+
+```typescript
+const payments = await server
+  .payments()
+  .forAccount(publicKey)
+  .order("desc")
+  .call();
+
+for (const payment of payments.records) {
+  if (payment.type === "payment") {
+    console.log(
+      `${payment.from} -> ${payment.to}: ${payment.amount} ${payment.asset_code || "XLM"}`
+    );
+  }
+}
+```
+
+#### Get Effects
+
+```typescript
+const effects = await server
+  .effects()
+  .forAccount(publicKey)
+  .limit(50)
+  .call();
+```
+
+#### Streaming (Server-Sent Events)
+
+```typescript
+// Stream transactions
+const closeHandler = server
+  .transactions()
+  .forAccount(publicKey)
+  .cursor("now")
+  .stream({
+    onmessage: (tx) => {
+      console.log("New transaction:", tx.hash);
+    },
+    onerror: (error) => {
+      console.error("Stream error:", error);
+    },
+  });
+
+// Close stream when done
+closeHandler();
+```
+
+#### Submit Transaction
+
+```typescript
+try {
+  const result = await server.submitTransaction(signedTransaction);
+  console.log("Success:", result.hash);
+} catch (error) {
+  if (error.response?.data?.extras?.result_codes) {
+    console.error("Error codes:", error.response.data.extras.result_codes);
+  }
+}
+```
+
+### Pagination
+
+```typescript
+// First page
+let page = await server.transactions().forAccount(publicKey).limit(10).call();
+
+// Next page
+if (page.records.length > 0) {
+  page = await page.next();
+}
+
+// Previous page
+page = await page.prev();
+```
+
+## Migration: Horizon to RPC
+
+### Account Loading
+
+```typescript
+// Horizon (old)
+const account = await horizonServer.loadAccount(publicKey);
+
+// RPC (new)
+const account = await rpc.getAccount(publicKey);
+// Note: RPC returns less data, just what's needed for transactions
+```
+
+### Transaction Submission
+
+```typescript
+// Horizon (for classic transactions)
+const result = await horizonServer.submitTransaction(tx);
+
+// RPC (for smart contract transactions)
+const response = await rpc.sendTransaction(tx);
+const result = await pollForResult(response.hash);
+```
+
+### Historical Data
+
+```typescript
+// Horizon - full history
+const allTxs = await horizonServer
+  .transactions()
+  .forAccount(publicKey)
+  .call();
+
+// RPC - most methods limited to 7 days
+// Exception: getLedgers can query back to genesis (Infinite Scroll)
+// For full historical data, use:
+// 1. Hubble (SDF's BigQuery dataset)
+// 2. Galexie (data pipeline)
+// 3. Your own indexer
+```
+
+### Streaming Replacement
+
+```typescript
+// Horizon - native streaming
+server.payments().stream({ onmessage: handlePayment });
+
+// RPC - polling (no native streaming)
+async function pollForUpdates() {
+  const lastLedger = await rpc.getLatestLedger();
+  // Check for new events/transactions
+  // Repeat on interval
+}
+setInterval(pollForUpdates, 5000);
+```
+
+## Historical Data Access
+
+For data older than 7 days (not available via most RPC methods; `getLedgers` can reach genesis via Infinite Scroll):
+
+### Hubble (BigQuery)
+
+```sql
+-- Query Stellar data in BigQuery
+SELECT *
+FROM `crypto-stellar.crypto_stellar.history_transactions`
+WHERE source_account = 'G...'
+ORDER BY created_at DESC
+LIMIT 100
+```
+
+### Galexie
+
+Self-hosted data pipeline for processing Stellar ledger data:
+- https://github.com/stellar/galexie
+
+### Data Lake
+
+RPC "Infinite Scroll" is powered by the Stellar data lake — a cloud-based object store (SEP-0054 format):
+- **Public access**: `s3://aws-public-blockchain/v1.1/stellar/ledgers/pubnet` (AWS Open Data)
+- **Self-host**: Use Galexie to export to AWS S3 or Google Cloud Storage
+- **Hosted**: [Quasar (Lightsail Network)](https://quasar.lightsail.network) provides hosted Galexie Data Lake + Archive RPC endpoints
+- **Size**: ~3.8TB, growing ~0.5TB/year
+- **Cost**: ~$160/month self-hosted ($60 compute + $100 storage)
+- **Docs**: https://developers.stellar.org/docs/data/apis/rpc/admin-guide/data-lake-integration
+
+### Third-Party Indexers
+
+For complex queries, event streaming, or custom data pipelines beyond what RPC/Horizon provide:
+
+- **Mercury** — Stellar-native indexer with Retroshades, GraphQL API (https://mercurydata.app)
+- **SubQuery** — Multi-chain indexer with Stellar support, event handlers (https://subquery.network)
+- **Goldsky** — Real-time data replication pipelines and subgraphs (https://goldsky.com)
+- **StellarExpert API** — Free, no-auth REST API for assets, accounts, ledger resolution (https://stellar.expert/openapi.html)
+
+See the full indexer directory: https://developers.stellar.org/docs/data/indexers
+
+## Network Configuration
+
+> For a React/Next.js-specific setup, see [frontend-stellar-sdk.md](/.well-known/agent-skills/dapp/skill.md).
+> For mainnet RPC, set `STELLAR_MAINNET_RPC_URL` from a provider in the [RPC providers directory](https://developers.stellar.org/docs/data/apis/rpc/providers).
+
+### Environment-Based Setup
+
+```typescript
+// lib/stellar-config.ts
+import * as StellarSdk from "@stellar/stellar-sdk";
+
+type NetworkConfig = {
+  rpcUrl: string;
+  horizonUrl: string;
+  networkPassphrase: string;
+  friendbotUrl: string | null;
+};
+
+const requireEnv = (name: string): string => {
+  const value = process.env[name];
+  if (!value) throw new Error(`Missing required env var: ${name}`);
+  return value;
+};
+
+const configs: Record<string, NetworkConfig> = {
+  mainnet: {
+    rpcUrl: requireEnv("STELLAR_MAINNET_RPC_URL"),
+    horizonUrl: "https://horizon.stellar.org",
+    networkPassphrase: StellarSdk.Networks.PUBLIC,
+    friendbotUrl: null,
+  },
+  testnet: {
+    rpcUrl: "https://soroban-testnet.stellar.org",
+    horizonUrl: "https://horizon-testnet.stellar.org",
+    networkPassphrase: StellarSdk.Networks.TESTNET,
+    friendbotUrl: "https://friendbot.stellar.org",
+  },
+  local: {
+    rpcUrl: "http://localhost:8000/soroban/rpc",
+    horizonUrl: "http://localhost:8000",
+    networkPassphrase: "Standalone Network ; February 2017",
+    friendbotUrl: "http://localhost:8000/friendbot",
+  },
+};
+
+const network = process.env.STELLAR_NETWORK || "testnet";
+export const config = configs[network];
+
+export const rpc = new StellarSdk.rpc.Server(config.rpcUrl);
+export const horizon = new StellarSdk.Horizon.Server(config.horizonUrl);
+```
+
+## Best Practices
+
+### Use RPC for:
+- New application development
+- Smart contract interactions
+- Transaction simulation and submission
+- Real-time account state
+
+### Use Horizon for:
+- Historical transaction queries
+- Payment streaming
+- Legacy application maintenance
+- Rich account metadata
+
+### Error Handling
+
+```typescript
+// RPC errors
+try {
+  const result = await rpc.sendTransaction(tx);
+} catch (error) {
+  if (error.code === 400) {
+    // Invalid transaction
+  } else if (error.code === 503) {
+    // Service unavailable
+  }
+}
+
+// Horizon errors
+try {
+  const result = await horizon.submitTransaction(tx);
+} catch (error) {
+  const extras = error.response?.data?.extras;
+  if (extras?.result_codes) {
+    // Detailed error codes
+    console.log("Transaction:", extras.result_codes.transaction);
+    console.log("Operations:", extras.result_codes.operations);
+  }
+}
+```
+
+### Rate Limiting
+
+Both RPC and Horizon have rate limits:
+- Use exponential backoff for retries
+- Cache responses where appropriate
+- Consider running your own nodes for high-volume applications
+
+```typescript
+async function withRetry<T>(fn: () => Promise<T>, maxRetries = 3): Promise<T> {
+  let lastError: Error;
+  for (let i = 0; i < maxRetries; i++) {
+    try {
+      return await fn();
+    } catch (error) {
+      lastError = error;
+      if (error.response?.status === 429) {
+        // Rate limited - exponential backoff
+        await new Promise(r => setTimeout(r, Math.pow(2, i) * 1000));
+      } else {
+        throw error;
+      }
+    }
+  }
+  throw lastError;
+}
+```
diff --git a/.mintlify/skills/smart-contracts/SKILL.md b/.mintlify/skills/smart-contracts/SKILL.md
new file mode 100644
index 000000000..d0d135abe
--- /dev/null
+++ b/.mintlify/skills/smart-contracts/SKILL.md
@@ -0,0 +1,901 @@
+---
+name: smart-contracts
+description: Stellar smart contract development (Rust, soroban-sdk). Entry point with project setup, contract anatomy, and build/deploy workflow, routing to three companion files in this directory — development.md (storage, auth, cross-contract calls, events, errors, upgrades, factories, troubleshooting), testing.md (unit, fuzz, property, fork, mutation, integration), and security.md (vulnerability classes, checklists, tooling, audits). Use when writing, testing, securing, or shipping Stellar smart contracts (formerly branded Soroban).
+user-invocable: true
+argument-hint: "[contract task]"
+---
+
+# Stellar Smart Contracts
+
+Guide for building Stellar smart contracts in Rust. Smart contracts on Stellar were formerly branded "Soroban" — the platform name is retired, but the Rust SDK (`soroban-sdk`) and several tool names keep the prefix.
+
+This file covers setup and the core workflow. The deep dives are included below — **jump to the section that matches the task**:
+
+| Task | Section |
+|------|------|
+| Storage, auth, cross-contract calls, events, errors, upgrades, factories, troubleshooting | [Development Patterns](#development-patterns) |
+| Unit, integration, fuzz, property, fork, and mutation testing | [Testing](#testing) |
+| Security review, vulnerability classes, checklists, audit prep, tooling | [Security](#security) |
+
+## When to use this skill
+- Writing a Stellar smart contract in Rust
+- Setting up contract tests (any layer)
+- Reviewing a contract for security issues
+- Architecting upgradeable contracts, factories, governance, or DeFi primitives
+- Debugging a contract-specific error (auth, storage, archival, resource limits)
+
+## Related skills
+- Assets, trustlines, and SAC bridge → `/.well-known/agent-skills/assets/skill.md`
+- Frontend/wallets that call your contract → `/.well-known/agent-skills/dapp/skill.md`
+- Chain data queries (RPC/Horizon) → `/.well-known/agent-skills/data/skill.md`
+- ZK verification (BLS12-381, Groth16, Circom/Noir/RISC Zero) → `/.well-known/agent-skills/zk-proofs/skill.md`
+- SEP/CAP standards and ecosystem links → `/.well-known/agent-skills/standards/skill.md`
+
+## Platform constraints
+
+Contracts are Rust compiled to WebAssembly, run in a sandboxed host:
+
+- `#![no_std]` required — use `soroban_sdk` types (`String`, `Vec`, `Map`, `Symbol`), not the Rust standard library
+- 64KB compiled contract size limit — use the release profile below
+- `Symbol` is limited to 32 characters; `symbol_short!()` covers up to 9
+- Storage is rented: every entry has a TTL and can be archived — see [development.md](#storage)
+- No `delegatecall`, no classical cross-contract reentrancy — see [security.md](#security)
+
+## Project setup
+
+```bash
+stellar contract init my-contract   # scaffolds a Cargo workspace with contracts/
+cd my-contract
+```
+
+`Cargo.toml` essentials:
+
+```toml
+[lib]
+crate-type = ["cdylib"]
+
+[dependencies]
+soroban-sdk = "25.0.1"  # check https://crates.io/crates/soroban-sdk for latest
+
+[dev-dependencies]
+soroban-sdk = { version = "25.0.1", features = ["testutils"] }  # match above
+
+[profile.release]
+opt-level = "z"
+overflow-checks = true
+debug = 0
+strip = "symbols"
+debug-assertions = false
+panic = "abort"
+codegen-units = 1
+lto = true
+```
+
+## Contract anatomy
+
+One compact example showing state, constructor, auth, TTL, and a typed error:
+
+```rust
+#![no_std]
+use soroban_sdk::{contract, contracterror, contractimpl, contracttype, Address, Env};
+
+#[contracttype]
+#[derive(Clone)]
+pub enum DataKey {
+    Admin,
+    Counter,
+}
+
+#[contracterror]
+#[derive(Copy, Clone, Debug, Eq, PartialEq)]
+#[repr(u32)]
+pub enum Error {
+    NotInitialized = 1,
+}
+
+#[contract]
+pub struct CounterContract;
+
+#[contractimpl]
+impl CounterContract {
+    // Runs once, atomically, at deploy time (Protocol 22+). Must be named
+    // `__constructor` and return (). Does not run again on upgrade.
+    pub fn __constructor(env: Env, admin: Address) {
+        env.storage().instance().set(&DataKey::Admin, &admin);
+        env.storage().instance().set(&DataKey::Counter, &0u32);
+    }
+
+    pub fn increment(env: Env) -> Result<u32, Error> {
+        let admin: Address = env
+            .storage()
+            .instance()
+            .get(&DataKey::Admin)
+            .ok_or(Error::NotInitialized)?;
+        admin.require_auth();
+
+        let count: u32 = env.storage().instance().get(&DataKey::Counter).unwrap_or(0);
+        let count = count + 1;
+        env.storage().instance().set(&DataKey::Counter, &count);
+
+        // Extend TTL so contract state is not archived (threshold, extend-to)
+        env.storage().instance().extend_ttl(100, 518400);
+
+        Ok(count)
+    }
+
+    pub fn get_count(env: Env) -> u32 {
+        env.storage().instance().get(&DataKey::Counter).unwrap_or(0)
+    }
+}
+```
+
+Full patterns (three storage types, auth variants, cross-contract calls, events, custom types): [development.md](#development-patterns).
+
+## Build, deploy, invoke
+
+```bash
+# Build optimized WASM → target/wasm32-unknown-unknown/release/*.wasm
+stellar contract build
+
+# Create and fund an identity (testnet)
+stellar keys generate --global alice --network testnet --fund
+
+# Deploy (constructor args go after the `--`)
+stellar contract deploy \
+  --wasm target/wasm32-unknown-unknown/release/my_contract.wasm \
+  --source alice \
+  --network testnet \
+  -- \
+  --admin alice
+
+# Invoke
+stellar contract invoke \
+  --id CONTRACT_ID \
+  --source alice \
+  --network testnet \
+  -- \
+  increment
+```
+
+To upload WASM without instantiating (e.g. for factories or upgrades), use `stellar contract upload` (the older `stellar contract install` is a deprecated alias).
+
+## Minimal test
+
+```rust
+#![cfg(test)]
+use super::*;
+use soroban_sdk::{testutils::Address as _, Address, Env};
+
+#[test]
+fn test_increment() {
+    let env = Env::default();
+    env.mock_all_auths();
+    let admin = Address::generate(&env);
+    let contract_id = env.register(CounterContract, (admin.clone(),));
+    let client = CounterContractClient::new(&env, &contract_id);
+
+    assert_eq!(client.increment(), 1);
+    assert_eq!(client.get_count(), 1);
+}
+```
+
+Auth mocking, fuzzing, fork tests, and CI setup: [testing.md](#testing).
+
+## Before mainnet
+
+Work through the checklists in [security.md](#security) — authorization, reinitialization, arithmetic, storage TTLs, and cross-contract validation are the recurring failure modes.
+
+## Documentation
+
+- [Smart contract docs](https://developers.stellar.org/docs/build/smart-contracts)
+- [Example contracts](https://github.com/stellar/soroban-examples)
+- [soroban-sdk API reference](https://docs.rs/soroban-sdk)
+- [Stellar CLI manual](https://developers.stellar.org/docs/tools/cli/stellar-cli)
+
+
+---
+
+# Development Patterns
+
+Core and advanced patterns for Stellar smart contracts. For setup and the basic workflow, start at [SKILL.md](#stellar-smart-contracts); for tests see [testing.md](#testing); for security review see [security.md](#security).
+
+## Architecture
+
+Contracts run as WebAssembly guests in a sandboxed host. The host provides storage, crypto, and cross-contract calls; guest code references host objects via handles, not direct memory. Practical consequences:
+
+- `#![no_std]` — use `soroban_sdk` collections and strings
+- 64KB compiled size limit (see [Contract size](#contract-size) below)
+- Rust is the supported language. Community alternatives (AssemblyScript, Solidity via Solang) exist but are not production-ready — see [migration docs](https://developers.stellar.org/docs/learn/migrate).
+
+## Storage
+
+Three storage types with different costs and lifetimes. Choosing wrong is a top source of bugs and fee waste:
+
+| Type | Lifetime | Use for |
+|------|----------|---------|
+| `instance()` | Tied to the contract instance, shared TTL | Admin address, global config, small global state |
+| `persistent()` | Per-key TTL, archived when expired but **restorable** | User balances, anything that must survive |
+| `temporary()` | Per-key TTL, deleted when expired, **not restorable** | Caches, session data, short-lived flags |
+
+```rust
+env.storage().instance().set(&DataKey::Admin, &admin);
+env.storage().persistent().set(&DataKey::Balance(user), &balance);
+env.storage().temporary().set(&DataKey::Cache(key), &value);
+```
+
+### TTL management
+
+Every entry has a TTL (in ledgers, ~5s each) and is archived when it expires. Extend proactively in functions that touch the data:
+
+```rust
+const MIN_TTL: u32 = 17280;     // ~1 day
+const EXTEND_TO: u32 = 518400;  // ~30 days
+
+// extend_ttl(threshold, extend_to): only extends if TTL < threshold
+env.storage().instance().extend_ttl(MIN_TTL, EXTEND_TO);
+env.storage().persistent().extend_ttl(&DataKey::Balance(user), MIN_TTL, EXTEND_TO);
+```
+
+Archived persistent entries can be restored with a `RestoreFootprint` operation, but that costs an extra transaction — design TTL extension into hot paths instead. Details: [state archival docs](https://developers.stellar.org/docs/learn/fundamentals/contract-development/storage/state-archival).
+
+### Typed storage keys
+
+Always use a `#[contracttype]` enum for keys — ad-hoc symbols invite collisions:
+
+```rust
+#[contracttype]
+#[derive(Clone)]
+pub enum DataKey {
+    Admin,
+    Balance(Address),
+    Allowance(Address, Address), // (owner, spender)
+}
+```
+
+## Data types
+
+```rust
+use soroban_sdk::{Address, Bytes, BytesN, Map, String, Symbol, Vec};
+
+let addr: Address = env.current_contract_address();
+let sym: Symbol = symbol_short!("transfer");        // ≤9 chars; Symbol max is 32
+let s: String = String::from_str(&env, "hello");
+let hash: BytesN<32> = env.crypto().sha256(&bytes).into();
+let v: Vec<u32> = vec![&env, 1, 2, 3];
+let m: Map<Symbol, u32> = Map::new(&env);
+```
+
+Custom types derive `#[contracttype]`:
+
+```rust
+#[contracttype]
+#[derive(Clone, Debug, Eq, PartialEq)]
+pub struct TokenMetadata {
+    pub name: String,
+    pub symbol: Symbol,
+    pub decimals: u32,
+}
+```
+
+## Authorization
+
+Authorization is opt-in and explicit. Call `require_auth()` on every address whose consent the operation needs:
+
+```rust
+pub fn transfer(env: Env, from: Address, to: Address, amount: i128) {
+    from.require_auth();
+    // or bind the auth to specific arguments:
+    // from.require_auth_for_args((&to, amount).into_val(&env));
+    // ...
+}
+```
+
+Admin pattern:
+
+```rust
+fn require_admin(env: &Env) {
+    let admin: Address = env.storage().instance().get(&DataKey::Admin).unwrap();
+    admin.require_auth();
+}
+```
+
+Authorization semantics (sub-invocations, custom accounts): [auth docs](https://developers.stellar.org/docs/learn/fundamentals/contract-development/authorization).
+
+## Constructors
+
+`__constructor` runs once, atomically, at deploy time (Protocol 22+). Prefer it over a separate `initialize` function — it removes the front-running window between deploy and init:
+
+```rust
+pub fn __constructor(env: Env, admin: Address, initial_value: u32) {
+    env.storage().instance().set(&DataKey::Admin, &admin);
+    env.storage().instance().set(&DataKey::Value, &initial_value);
+}
+```
+
+Rules: exact name `__constructor`, returns `()`, runs only at creation (not on upgrade), failure aborts the deployment atomically. Pass args at deploy time after the `--` separator (see [SKILL.md](#build-deploy-invoke)).
+
+If you must support a guarded `initialize` instead (pre-Protocol-22 targets), check-and-set an `Initialized` flag — see [security.md](#2-reinitialization-attacks).
+
+## Cross-contract calls
+
+Import another contract's WASM to get a typed client:
+
+```rust
+mod token_contract {
+    soroban_sdk::contractimport!(
+        file = "../token/target/wasm32-unknown-unknown/release/token.wasm"
+    );
+}
+
+pub fn deposit(env: Env, user: Address, token: Address, amount: i128) {
+    user.require_auth();
+    let token_client = token_contract::Client::new(&env, &token);
+    token_client.transfer(&user, &env.current_contract_address(), &amount);
+}
+```
+
+For Stellar assets, use the built-in SAC client — every asset has a Stellar Asset Contract:
+
+```rust
+use soroban_sdk::token::Client as TokenClient;
+
+let token = TokenClient::new(&env, &asset_contract_id);
+token.transfer(&from, &to, &amount);
+```
+
+SAC details and asset interop: `/.well-known/agent-skills/assets/skill.md`. Validate addresses you call — see [security.md](#3-arbitrary-contract-calls).
+
+## Events
+
+```rust
+use soroban_sdk::contractevent;
+
+#[contractevent(topics = ["transfer"])]
+pub struct TransferEvent {
+    pub from: Address,
+    pub to: Address,
+    pub amount: i128,
+}
+
+// in a contract function:
+TransferEvent { from, to, amount }.publish(&env);
+```
+
+Emit events for every state change you'll want to index or audit — events are much cheaper than storing queryable state.
+
+## Error handling
+
+```rust
+#[contracterror]
+#[derive(Copy, Clone, Debug, Eq, PartialEq)]
+#[repr(u32)]
+pub enum ContractError {
+    NotInitialized = 1,
+    InsufficientBalance = 2,
+    InvalidAmount = 3,
+}
+
+pub fn transfer(env: Env, from: Address, to: Address, amount: i128) -> Result<(), ContractError> {
+    if amount <= 0 {
+        return Err(ContractError::InvalidAmount);
+    }
+    // ...
+    Ok(())
+}
+```
+
+Returning `Result` gives callers (and clients generated for tests) typed errors via `try_` methods. Panics abort with less information — reserve them for invariant violations.
+
+## Upgradeability
+
+Decide early whether the contract is mutable. If yes, gate the upgrade behind admin/governance auth and track versions:
+
+```rust
+contractmeta!(key = "binver", val = "1.0.0");
+
+pub fn upgrade(env: Env, new_wasm_hash: BytesN<32>) {
+    let admin: Address = env.storage().instance().get(&DataKey::Admin).unwrap();
+    admin.require_auth();
+    env.deployer().update_current_contract_wasm(new_wasm_hash);
+}
+```
+
+- Upload the new WASM first (`stellar contract upload`), pass its hash here.
+- Add a dedicated `migrate` entrypoint for storage migrations; make it idempotent and monotonic (`new_version > current_version`).
+- `__constructor` does not re-run on upgrade.
+- SEP-0049 standardizes upgradeable-contract interfaces; OpenZeppelin's [stellar-contracts](https://github.com/OpenZeppelin/stellar-contracts) ships an audited implementation.
+
+## Factories
+
+```rust
+#[contractimpl]
+impl Factory {
+    pub fn deploy(
+        env: Env,
+        owner: Address,
+        wasm_hash: BytesN<32>,
+        salt: BytesN<32>,
+        constructor_args: Vec<Val>,
+    ) -> Address {
+        owner.require_auth();
+        env.deployer()
+            .with_address(env.current_contract_address(), salt)
+            .deploy_v2(wasm_hash, constructor_args)
+    }
+}
+```
+
+- Addresses are deterministic per (deployer, salt) — derive salts intentionally.
+- Authorize who may deploy; emit an event per deployment so instances are indexable.
+- Keep factory logic separate from instance business logic.
+
+## Governance
+
+For sensitive actions (upgrades, config changes), prefer a timelock: `propose_*` stores the pending action plus an execute-after ledger, `execute_*` enforces the delay, `cancel_*` lets governance abort. For multisig, separate proposer/approver/executor roles, store proposal state in persistent storage, and prevent replay (unique proposal IDs, expiry semantics, explicit events).
+
+## DeFi and compliance patterns
+
+Condensed design rules — the details are application-specific:
+
+- **Vaults**: track `total_assets`/`total_shares`, round conservatively on mint/redeem, include pause controls.
+- **Pools/AMMs**: define the invariant and fee accounting precisely; slippage-check every user-facing swap.
+- **Oracles**: enforce freshness bounds, prefer multi-source/median feeds, add circuit breakers.
+- **Regulated tokens**: isolate allowlist/denylist and freeze/forced-transfer logic in dedicated entrypoints with strong auth, emit policy-decision events, never store PII on-chain.
+
+Worked examples: [soroban-examples](https://github.com/stellar/soroban-examples) (liquidity pool, atomic swap, timelock, single-offer) and the [DeFi tutorials](https://developers.stellar.org/docs/build/apps/guestbook).
+
+## Contract size
+
+The 64KB limit is real and the release profile in [SKILL.md](#project-setup) is mandatory. If you still exceed it:
+
+```bash
+ls -la target/wasm32-unknown-unknown/release/*.wasm   # check size
+cargo install cargo-bloat
+cargo bloat --release --target wasm32-unknown-unknown # find heavy deps
+```
+
+Then: split the contract, drop heavy dependencies, prefer `symbol_short!`, avoid large static data.
+
+## Resource optimization
+
+Fees are multidimensional (CPU instructions, ledger reads/writes, bytes, events, rent):
+
+- Minimize storage reads/writes; batch where possible
+- Avoid unbounded loops over user-controlled collections
+- Reduce cross-contract calls in hot paths
+- Use events instead of storage for data that only needs off-chain visibility
+- Profile with `stellar contract invoke ... --send=no` before optimizing blind
+
+## Troubleshooting
+
+| Symptom | Cause | Fix |
+|---------|-------|-----|
+| `contract exceeds maximum size` | WASM > 64KB | See [Contract size](#contract-size) |
+| `cannot find macro println` / `std` errors | Missing `#![no_std]` | Add as first line of `lib.rs`; use SDK types |
+| Calls fail after inactivity, data "missing" | Storage TTL expired → archived | Extend TTLs proactively; restore archived entries |
+| Temporary data vanished | Wrong storage type | Use `persistent()` for data that must survive |
+| `Error: identity "alice" not found` | CLI identity missing | `stellar keys generate --global alice --network testnet --fund` |
+| `invalid argument format` on invoke | Wrong CLI arg syntax | Plain strings for addresses; JSON for complex types |
+| `transaction simulation failed` | Soroban tx not simulated/assembled | Simulate, then `assembleTransaction` before signing |
+| `tx_bad_auth` | Wrong network passphrase or signer | Match passphrase to network; check signing identity |
+| `tx_bad_seq` | Stale sequence number | Reload the account before building the tx |
+
+Client-side issues (wallet detection, trustlines, transaction building from JS) are covered in `/.well-known/agent-skills/dapp/skill.md` and `/.well-known/agent-skills/data/skill.md`.
+
+
+---
+
+# Testing
+
+Testing strategy for Stellar smart contracts, from fast native unit tests to mainnet-fork tests. Companion to [SKILL.md](#stellar-smart-contracts), [development.md](#development-patterns), and [security.md](#security).
+
+Layers, fastest first:
+
+1. **Unit tests** — native Rust with `soroban-sdk` testutils (not WASM, full debugger support)
+2. **Local integration** — Stellar Quickstart container
+3. **Testnet** — public network rehearsal
+4. **Fork tests** — replay against real ledger state
+
+## Unit testing
+
+```rust
+#![cfg(test)]
+use soroban_sdk::{
+    testutils::{Address as _, MockAuth, MockAuthInvoke},
+    Address, Env,
+};
+use crate::{Contract, ContractClient};
+
+#[test]
+fn test_basic() {
+    let env = Env::default();
+    let contract_id = env.register(Contract, ());      // () = no constructor args
+    let client = ContractClient::new(&env, &contract_id);
+    let user = Address::generate(&env);
+
+    client.initialize(&user);
+    assert_eq!(client.get_value(), 0);
+}
+```
+
+`env.register` takes constructor args as its second parameter — `env.register(Contract, (admin.clone(),))` for a contract with `__constructor(env, admin)`.
+
+### Authorization
+
+`mock_all_auths()` approves everything — convenient, but it can hide missing `require_auth` calls. Always pair it with `env.auths()` assertions, or mock specific auths:
+
+```rust
+#[test]
+fn test_auth() {
+    let env = Env::default();
+    let contract_id = env.register(Contract, ());
+    let client = ContractClient::new(&env, &contract_id);
+    let user = Address::generate(&env);
+    let other = Address::generate(&env);
+    // Approve only this specific invocation
+    env.mock_auths(&[MockAuth {
+        address: &user,
+        invoke: &MockAuthInvoke {
+            contract: &contract_id,
+            fn_name: "transfer",
+            args: (&user, &other, &100i128).into_val(&env),
+            sub_invokes: &[],
+        },
+    }]);
+
+    client.transfer(&user, &other, &100);
+    assert!(!env.auths().is_empty());  // verify auth was actually required
+}
+```
+
+### Time and ledger state
+
+```rust
+env.ledger().set_timestamp(1000);          // for vesting/timelock logic
+env.ledger().set_sequence_number(1000);
+// ... act, then advance:
+env.ledger().set_timestamp(2500);
+```
+
+### Events
+
+```rust
+let events = env.events().all();
+assert_eq!(events.len(), 1);
+// each event = (contract_id, topics: Vec<Val>, data: Val)
+```
+
+### Storage TTL
+
+```rust
+let ttl = env.as_contract(&contract_id, || {
+    env.storage().persistent().get_ttl(&DataKey::MyData)
+});
+assert!(ttl > 0);
+```
+
+### Cross-contract
+
+Register a real dependency from its WASM and test the interaction:
+
+```rust
+mod token { soroban_sdk::contractimport!(file = "token.wasm"); }
+
+let token_id = env.register(token::WASM, ());
+let vault_id = env.register(VaultContract, ());
+// drive both through their typed clients
+```
+
+## Local network
+
+```bash
+stellar container start local     # or: docker run --rm -it -p 8000:8000 stellar/quickstart:latest --local
+stellar keys generate --global test-account --network local --fund
+stellar contract deploy --wasm target/wasm32-unknown-unknown/release/contract.wasm \
+  --source test-account --network local
+```
+
+Endpoints: RPC `http://localhost:8000/soroban/rpc`, Horizon `http://localhost:8000`, passphrase `"Standalone Network ; February 2017"`.
+
+## Testnet
+
+```bash
+stellar keys generate --global my-key --network testnet --fund
+stellar contract deploy --wasm ... --source my-key --network testnet
+```
+
+- RPC: `https://soroban-testnet.stellar.org` · Horizon: `https://horizon-testnet.stellar.org`
+- Passphrase: `"Test SDF Network ; September 2015"` · Friendbot: `https://friendbot.stellar.org`
+- **Testnet resets quarterly** — everything is deleted. Script your deployments; never treat testnet state as durable.
+
+## Integration tests
+
+TypeScript, against local or testnet (the same flow a frontend uses — simulate, assemble, sign, send):
+
+```typescript
+import * as StellarSdk from "@stellar/stellar-sdk";
+
+const rpc = new StellarSdk.rpc.Server(process.env.RPC_URL!);
+const account = await rpc.getAccount(keypair.publicKey());
+const contract = new StellarSdk.Contract(contractId);
+
+const tx = new StellarSdk.TransactionBuilder(account, { fee: "100", networkPassphrase })
+  .addOperation(contract.call("initialize", StellarSdk.Address.fromString(keypair.publicKey()).toScVal()))
+  .setTimeout(30)
+  .build();
+
+const sim = await rpc.simulateTransaction(tx);
+const prepared = StellarSdk.rpc.assembleTransaction(tx, sim).build();
+prepared.sign(keypair);
+const result = await rpc.sendTransaction(prepared);
+```
+
+In Rust, gate network-dependent tests behind `#[ignore]` and run them with `cargo test -- --ignored` in environments where the network is up.
+
+## Fuzz testing
+
+All `#[contracttype]` types implement `SorobanArbitrary` under the `testutils` feature, so fuzzing works out of the box with `cargo-fuzz`:
+
+```bash
+rustup install nightly
+cargo install --locked cargo-fuzz
+cargo fuzz init
+```
+
+`Cargo.toml` needs `crate-type = ["lib", "cdylib"]`; add `soroban-sdk = { version = "...", features = ["testutils"] }` to `fuzz/Cargo.toml`.
+
+```rust
+// fuzz/fuzz_targets/fuzz_deposit.rs
+#![no_main]
+use libfuzzer_sys::fuzz_target;
+use soroban_sdk::{testutils::Address as _, Address, Env};
+use my_contract::{Contract, ContractClient};
+
+fuzz_target!(|amount: i128| {
+    let env = Env::default();
+    env.mock_all_auths();
+    let contract_id = env.register(Contract, ());
+    let client = ContractClient::new(&env, &contract_id);
+    let user = Address::generate(&env);
+
+    client.initialize(&user);
+    let _ = client.try_deposit(&user, &amount);  // must never panic unexpectedly
+});
+```
+
+Run with `cargo +nightly fuzz run fuzz_deposit`. For token contracts there's a reusable harness: [soroban-token-fuzzer](https://github.com/brson/soroban-token-fuzzer). Docs: [fuzzing guide](https://developers.stellar.org/docs/build/guides/testing/fuzzing).
+
+## Property-based testing
+
+`proptest` + `SorobanArbitrary` runs in plain `cargo test` — use it to lock in invariants found by fuzzing:
+
+```rust
+proptest! {
+    #[test]
+    fn deposit_then_withdraw_preserves_balance(amount in 1i128..=i128::MAX) {
+        // setup as usual...
+        client.deposit(&user, &amount);
+        client.withdraw(&user, &amount);
+        prop_assert_eq!(client.balance(&user), 0);
+    }
+}
+```
+
+Workflow: fuzz interactively to find deep bugs → convert findings to proptest regressions for CI.
+
+## Snapshots, fork tests, mutation tests
+
+Three techniques worth knowing; each is one command plus a doc link:
+
+- **Test snapshots**: every test writes a JSON snapshot of events + final ledger state to `test_snapshots/`. Commit them — diffs expose unintended behavioral changes. [Docs](https://developers.stellar.org/docs/build/guides/testing/differential-tests-with-test-snapshots)
+- **Fork testing**: `stellar snapshot create --address C... --output json --out snapshot.json`, then `Env::from_ledger_snapshot_file("snapshot.json")` to test against real network state. Also useful for upgrade rehearsals: `stellar contract fetch --id C... --out-file deployed.wasm`, register both old and new versions, compare behavior. [Docs](https://developers.stellar.org/docs/build/guides/testing/fork-testing)
+- **Mutation testing**: `cargo install --locked cargo-mutants && cargo mutants` — mutates your source and reports `MISSED` where tests didn't notice. [Docs](https://developers.stellar.org/docs/build/guides/testing/mutation-testing)
+
+## Resource profiling
+
+```bash
+stellar contract invoke --id CONTRACT_ID --source alice --network testnet \
+  --send=no -- function_name --arg value
+```
+
+Simulation reports CPU instructions, ledger reads/writes, and fees without submitting.
+
+## CI
+
+```yaml
+name: Test contracts
+on: [push, pull_request]
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: dtolnay/rust-toolchain@stable
+      - run: rustup target add wasm32-unknown-unknown
+      - run: cargo test
+      - run: cargo build --release --target wasm32-unknown-unknown
+```
+
+For integration jobs, run `stellar/quickstart` as a service container and deploy with the CLI (`cargo install stellar-cli --locked`).
+
+## Checklist
+
+- [ ] Unit tests cover all public functions, including error paths
+- [ ] Edge cases: zero amounts, max values, empty state
+- [ ] Authorization verified with `env.auths()` or specific `mock_auths`
+- [ ] Events asserted
+- [ ] Storage TTL behavior validated
+- [ ] Cross-contract interactions tested against real WASM
+- [ ] Fuzz targets for value-moving paths (deposit, withdraw, swap)
+- [ ] Property tests for invariants
+- [ ] Test snapshots committed
+- [ ] Integration test against local network in CI
+- [ ] Testnet rehearsal before mainnet
+
+
+---
+
+# Security
+
+Security review guide for Stellar smart contracts. Companion to [SKILL.md](#stellar-smart-contracts), [development.md](#development-patterns), and [testing.md](#testing).
+
+## Threat model
+
+Assume the attacker controls:
+
+- All arguments passed to contract functions
+- Transaction ordering and timing
+- All accounts except those requiring signatures
+- The ability to deploy contracts that mimic your interface
+
+## What the platform rules out
+
+- **No `delegatecall`** — contracts cannot execute foreign bytecode in their own context; proxy-style hijacks don't exist.
+- **No classical reentrancy** — execution is synchronous; the Ethereum-style cross-contract reentrancy class is absent (self-reentrancy is possible but rarely exploitable).
+- **Explicit authorization** — `require_auth()` is opt-in, which means *forgetting it* is the failure mode to hunt for.
+
+## Vulnerability classes
+
+### 1. Missing authorization
+
+```rust
+// BAD: anyone can drain
+pub fn withdraw(env: Env, to: Address, amount: i128) {
+    transfer_tokens(&env, &to, amount);
+}
+
+// GOOD
+pub fn withdraw(env: Env, to: Address, amount: i128) {
+    let admin: Address = env.storage().instance().get(&DataKey::Admin).unwrap();
+    admin.require_auth();
+    transfer_tokens(&env, &to, amount);
+}
+```
+
+Every privileged path needs `require_auth()` on the right address. Auth variants: [development.md](#authorization).
+
+### 2. Reinitialization attacks
+
+Only relevant if you use a guarded `initialize` instead of a `__constructor` (which can't re-run):
+
+```rust
+// GOOD: refuses second call
+pub fn initialize(env: Env, admin: Address) {
+    if env.storage().instance().has(&DataKey::Admin) {
+        panic!("already initialized");
+    }
+    env.storage().instance().set(&DataKey::Admin, &admin);
+}
+```
+
+### 3. Arbitrary contract calls
+
+Calling whatever address a user passes lets an attacker substitute a contract that mimics the interface:
+
+```rust
+// GOOD: allowlist external contracts
+pub fn swap(env: Env, token: Address, amount: i128) {
+    let allowed: Vec<Address> = env.storage().instance().get(&DataKey::AllowedTokens).unwrap();
+    if !allowed.contains(&token) {
+        panic!("token not allowed");
+    }
+    let client = token::Client::new(&env, &token);
+    // ...
+}
+```
+
+### 4. Integer overflow/underflow
+
+`overflow-checks = true` in the release profile catches overflows at runtime (panic), but explicit checked math fails cleaner and survives profile mistakes:
+
+```rust
+let new_balance = balance.checked_add(amount).expect("overflow");
+```
+
+Also validate sign and range on inputs (`amount <= 0` checks) — `i128` amounts can be negative.
+
+### 5. Storage key collisions
+
+Untyped keys can silently overwrite unrelated data. Always use a `#[contracttype]` key enum — see [development.md](#typed-storage-keys).
+
+### 6. Check-then-act races
+
+State can change between transactions. Do checks and state changes atomically within one invocation, and take slippage bounds (`min_out`) from the caller:
+
+```rust
+pub fn swap(env: Env, user: Address, amount_in: i128, min_out: i128) {
+    user.require_auth();
+    let amount_out = calculate_output(amount_in);
+    if amount_out < min_out {
+        panic!("slippage exceeded");
+    }
+    // update all state in this same invocation
+}
+```
+
+### 7. TTL/archival failures
+
+If critical state expires, the contract breaks (or worse, behaves as if state never existed). Extend TTLs in hot paths and monitor entry TTLs in production — see [development.md](#ttl-management).
+
+### 8. Trusting cross-contract return values
+
+Validate data from external contracts — allowlist oracles, sanity-check magnitudes, enforce freshness:
+
+```rust
+let price: i128 = oracle_client.get_price(&asset);
+if price <= 0 || price > MAX_REASONABLE_PRICE {
+    panic!("invalid price");
+}
+```
+
+## Classic-side risks (for contracts touching assets)
+
+- **Trustline spoofing**: display and verify full asset code + issuer; honor curated lists (`stellar.toml`).
+- **Clawback**: assets with `auth_clawback_enabled` can be seized by the issuer — check issuer flags before treating balances as final.
+- Asset semantics live in `/.well-known/agent-skills/assets/skill.md`.
+
+## Checklists
+
+### Contract
+
+- [ ] All privileged functions require appropriate authorization
+- [ ] Initialization can only happen once (or uses `__constructor`)
+- [ ] External contract calls validated/allowlisted
+- [ ] Arithmetic checked; input signs and ranges validated
+- [ ] Storage keys typed and collision-free
+- [ ] Critical TTLs extended proactively; archival behavior considered
+- [ ] Events emitted for auditable state changes
+- [ ] Upgrade path gated, tested (happy + failure), and replay-safe
+- [ ] Emergency controls (pause) and incident runbook defined for value-bearing contracts
+
+### Client-side
+
+- [ ] Network passphrase validated before signing
+- [ ] Transactions simulated before submission
+- [ ] Operation details displayed clearly; confirmation for high-value actions
+- [ ] Contract addresses verified against known deployments
+- [ ] Trustline status checked before transfers
+
+## Tooling
+
+**Static analysis**
+
+- [Scout](https://github.com/CoinFabrik/scout-soroban) (CoinFabrik): `cargo install cargo-scout-audit && cargo scout-audit` — 20+ detectors (missing overflow checks, unprotected WASM update, unrestricted transfers, unsafe unwrap, DoS-unbounded ops). SARIF output for CI; VSCode extension available.
+- [Security Detectors SDK](https://github.com/OpenZeppelin/soroban-security-detectors-sdk) (OpenZeppelin): pre-built detectors (`auth_missing`, `unchecked_ft_transfer`, improper TTL extension) plus a framework for writing custom ones.
+
+**Formal verification**
+
+- [Certora Sunbeam](https://docs.certora.com/en/latest/docs/sunbeam/index.html): specs as Rust macros (`cvlr_assert!`), operates on WASM bytecode.
+- [Komet](https://docs.runtimeverification.com/komet) (Runtime Verification): property tests + formal verification via KWasm semantics.
+
+**Monitoring**: [OpenZeppelin Monitor](https://www.openzeppelin.com/news/monitor-and-relayers-are-now-open-source) — self-hosted contract monitoring with Stellar support.
+
+**Knowledge base**: [sorobansecurity.com](https://sorobansecurity.com) — searchable audit reports and vulnerability database.
+
+## Audits and bounties
+
+- **[Audit Bank](https://stellar.org/grants-and-funding/soroban-audit-bank)** — SDF-subsidized audits for SCF-funded protocols ($3M+ across 43+ audits to date). Partner firms include OtterSec, Veridise, Runtime Verification, CoinFabrik, Certora, Zellic, Code4rena. Follow-up audits trigger at TVL milestones.
+- **[Immunefi — Stellar](https://immunefi.com/bug-bounty/stellar/)** — up to $250K for core/SDK/CLI vulnerabilities (PoC required, local forks only).
+- **[Immunefi — OpenZeppelin on Stellar](https://immunefi.com/bug-bounty/openzeppelin-stellar/)** — up to $25K for the audited contracts library.
+
+Before requesting an audit: run the static analyzers, complete the checklists above, document your threat model and trust assumptions, and have the test suite from [testing.md](#testing) green — auditors' time is better spent on logic than on lint.
diff --git a/.mintlify/skills/standards/SKILL.md b/.mintlify/skills/standards/SKILL.md
new file mode 100644
index 000000000..390d893e5
--- /dev/null
+++ b/.mintlify/skills/standards/SKILL.md
@@ -0,0 +1,864 @@
+---
+name: standards
+description: Stellar standards, ecosystem, and reference. Covers SEPs (Stellar Ecosystem Proposals), CAPs (Core Advancement Proposals), and a quick map for picking the right standard for wallets, anchors, payments, deposits/withdrawals, federation, deep links, and KYC. Also bundles ecosystem references (DeFi protocols, dev tools, wallets, infra, community projects) and curated documentation links. Use when you need to know which SEP applies, or want a starting point for ecosystem integrations and official docs.
+user-invocable: true
+argument-hint: "[standards or ecosystem lookup]"
+---
+
+# Standards, Ecosystem, and Resources
+
+Three things bundled because they're all reference material you reach for in the same moment: "which standard handles X?", "is there an existing project doing Y?", and "where's the canonical doc for Z?".
+
+## When to use this skill
+- Picking the right SEP for an integration (anchors, deposits, federation, deep links, KYC, paths)
+- Checking CAP status for a protocol feature you want to rely on
+- Finding existing DeFi protocols, wallets, or infrastructure to integrate with rather than rebuild
+- Locating official docs, SDKs, or community resources
+
+## Related skills
+- Implementing a SEP-41 token interface → `/.well-known/agent-skills/assets/skill.md`, `/.well-known/agent-skills/smart-contracts/skill.md`
+- Frontend SEP-7 / SEP-10 flows → `/.well-known/agent-skills/dapp/skill.md`
+- CAPs for cryptography (BLS, BN254, Poseidon) → `/.well-known/agent-skills/zk-proofs/skill.md`
+- x402/MPP protocol context → `/.well-known/agent-skills/agentic-payments/skill.md`
+
+---
+
+# Part 1: SEP / CAP Standards Reference
+
+
+## When to use this guide
+Use this when you need:
+- The right SEP/CAP for a feature or integration
+- Interoperability guidance for wallets, anchors, and contracts
+- A fast map from use case to official standards docs
+
+## Maintenance note
+Standards status can change quickly.
+Before implementation, verify current status in:
+- SEPs: [stellar-protocol/ecosystem](https://github.com/stellar/stellar-protocol/tree/master/ecosystem)
+- CAPs: [stellar-protocol/core](https://github.com/stellar/stellar-protocol/tree/master/core)
+
+Treat this file as a routing map, not a source of final governance/status truth.
+
+## High-value SEPs for app developers
+
+### Contracts and token interfaces
+- [SEP-0041](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0041.md): Soroban token interface
+- [SEP-0046](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0046.md): Contract metadata in Wasm
+- [SEP-0048](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0048.md): Contract interface specification
+- [SEP-0049](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0049.md): Upgradeable-contract guidance
+- [SEP-0050](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0050.md): NFT standard work
+- [SEP-0055](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0055.md): Contract build verification
+- [SEP-0056](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0056.md): Vault-style tokenized products
+- [SEP-0057](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0057.md): Regulated token patterns (T-REX)
+
+### Auth, identity, and metadata
+- [SEP-0010](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md): Web authentication
+- [SEP-0023](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0023.md): StrKey encoding
+- [SEP-0001](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md): `stellar.toml`
+
+### Anchor and fiat integration
+- [SEP-0006](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md): Programmatic deposit/withdrawal API
+- [SEP-0024](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md): Hosted interactive anchor flow
+- [SEP-0031](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md): Cross-border payment flow
+- [SEP-0012](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md): KYC data exchange
+
+## High-value CAPs for smart contract developers
+
+### Smart contract foundations
+- [CAP-0046](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0046.md): Soroban overview
+- CAP-0046 subdocuments (`cap-0046-*.md`): runtime, lifecycle, host functions, storage, auth, metering
+
+### Frequently used contract capabilities
+- [CAP-0051](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0051.md): secp256r1 verification (passkey-related cryptography)
+- [CAP-0053](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0053.md): TTL extension behavior
+- [CAP-0058](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0058.md): constructors (`__constructor`)
+- [CAP-0059](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0059.md): BLS12-381 primitives
+- [CAP-0067](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md): protocol/runtime improvements including asset/event model changes
+
+### Newer and draft crypto/features
+- [CAP-0074](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0074.md): BN254 host functions proposal
+- [CAP-0075](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0075.md): Poseidon/Poseidon2 proposal
+- [CAP-0079](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0079.md): muxed-address strkey conversion proposal
+
+Use the CAP preamble status fields as the source of truth for implementation readiness.
+
+## Quick mapping by use case
+
+### I am building a fungible token
+1. Start with SEP-0041 interface expectations.
+2. Prefer Stellar Assets + SAC interop unless custom logic is required.
+3. If regulated, review SEP-0057 patterns.
+
+### I need upgrade-safe contracts
+1. Read SEP-0049 guidance for upgrade process design.
+2. Use CAP-0058 constructors for atomic initialization where protocol support exists.
+3. Add migration/versioning strategy before deploying upgradeable contracts.
+
+### I am building a smart-wallet flow
+1. Use SEP-0010 for web authentication flows.
+2. Review CAP-0051 for passkey-related cryptographic primitives.
+3. Align wallet UX and signing payloads with current SDK guidance.
+
+### I need anchor integration for fiat rails
+1. SEP-0006 for API-first flows.
+2. SEP-0024 for hosted interactive rails.
+3. SEP-0031 when supporting payment corridors.
+4. SEP-0012 for KYC data requirements.
+
+## Practical workflow for AI agents
+- Step 1: Identify feature category (token, wallet auth, anchor, upgradeability).
+- Step 2: Link user to the 1-3 primary SEP/CAP docs.
+- Step 3: Check status/acceptance in the source repo before asserting support.
+- Step 4: Implement only what is active on the target network/protocol.
+- Step 5: Document dependencies on draft standards explicitly.
+
+## Related docs
+- Contract implementation details: [`/.well-known/agent-skills/smart-contracts/skill.md`](/.well-known/agent-skills/smart-contracts/skill.md)
+- Advanced architecture guidance: [`/.well-known/agent-skills/smart-contracts/skill.md#development-patterns`](/.well-known/agent-skills/smart-contracts/skill.md#development-patterns)
+- RPC and data access: [`/.well-known/agent-skills/data/skill.md`](/.well-known/agent-skills/data/skill.md)
+- Security considerations: [`/.well-known/agent-skills/smart-contracts/skill.md#security`](/.well-known/agent-skills/smart-contracts/skill.md#security)
+
+---
+
+# Part 2: Stellar Ecosystem
+
+
+This guide catalogs the major projects, protocols, and tools in the Stellar ecosystem. Use this as a reference when building on Stellar to find relevant integrations, examples, and community projects.
+
+> **Canonical directories** — For the most up-to-date project lists, check:
+> - [Stellar Ecosystem](https://stellar.org/ecosystem) — Official directory (searchable by country, asset, category)
+> - [SCF Projects](https://communityfund.stellar.org/projects) — Funded projects with status tracking
+> - [Stellar on DefiLlama](https://defillama.com/chain/stellar) — Live DeFi TVL data
+>
+> Treat project metrics/status as volatile. Validate latest activity and production readiness before taking dependencies.
+
+## DeFi Protocols
+
+### Lending & Borrowing
+
+#### Blend Protocol
+Universal liquidity protocol enabling permissionless lending pools.
+- **Use Case**: Lending, borrowing, yield generation
+- **GitHub**: https://github.com/blend-capital/blend-contracts
+- **GitHub (v2)**: https://github.com/blend-capital/blend-contracts-v2
+- **Integrations**: Meru, Airtm, Lobstr, DeFindex, Beans
+
+#### Slender
+First non-custodial lending protocol on Stellar with flash loan support.
+- **Use Case**: Lending, borrowing, flash loans
+- **Features**: Pool-based strategy, sTokens, dTokens, utilization caps
+- **Oracle**: SEP-40 compatible (Reflector)
+
+### DEXs & AMMs
+
+#### Soroswap
+First DEX and aggregator on Stellar.
+- **Use Case**: Token swaps, liquidity provision, aggregation
+- **Website**: https://soroswap.finance
+- **GitHub (Core)**: https://github.com/soroswap/core
+- **GitHub (Frontend)**: https://github.com/soroswap/frontend
+- **GitHub (Aggregator)**: https://github.com/soroswap/aggregator
+- **Docs**: https://docs.soroswap.finance
+- **Features**: AMM + DEX aggregator across Aqua, Phoenix, Stellar Classic DEX
+
+#### Aquarius / AQUA Network
+Governance-driven liquidity layer with AMM functionality.
+- **Use Case**: Liquidity incentives, AMM, governance
+- **Website**: https://aqua.network
+- **GitHub**: https://github.com/AquaToken/soroban-amm
+- **GitHub (Org)**: https://github.com/AquaToken
+- **Token**: AQUA (governance + rewards)
+- **Docs**: https://docs.aqua.network
+
+#### Phoenix Protocol
+AMM protocol on Stellar.
+- **GitHub**: https://github.com/Phoenix-Protocol-Group
+- **Use Case**: Token swaps, liquidity pools
+
+### Yield & Vaults
+
+#### DeFindex
+Yield aggregation and vault infrastructure by PaltaLabs.
+- **Use Case**: Tokenized vaults, yield strategies, DeFi abstraction
+- **Docs**: https://docs.defindex.io
+- **Features**: Automated rebalancing, vault management, Blend integration
+
+### Stablecoins & CDPs
+
+#### Orbit CDP Protocol
+Collateralized stablecoin issuance (USD, EUR, MXN).
+- **Use Case**: Mint stablecoins against XLM/bond collateral
+- **Docs**: https://docs.orbitcdp.finance
+- **Features**: Multi-currency stablecoins, Pegkeeper automation, Blend integration
+
+## Wallets
+
+### Browser Extensions
+
+#### Freighter
+SDF's flagship non-custodial browser wallet.
+- **Website**: https://freighter.app
+- **Docs**: https://docs.freighter.app
+- **GitHub**: https://github.com/stellar/freighter
+- **GitHub (Mobile)**: https://github.com/stellar/freighter-mobile
+- **API**: https://github.com/stellar/freighter/tree/master/library/freighter-api
+- **Features**: Smart contract support, mobile apps (iOS/Android), Discover browser
+
+#### xBull
+Feature-rich browser wallet with advanced capabilities.
+- **Website**: https://xbull.app
+- **Features**: Multi-account, hardware wallet support
+
+#### Albedo
+Lightweight web-based wallet and signing provider.
+- **Website**: https://albedo.link
+- **Use Case**: Web authentication, transaction signing
+
+#### Rabet
+Browser extension wallet for Stellar.
+- **Website**: https://rabet.io
+
+#### Hana Wallet
+Modern Stellar wallet with DeFi features.
+- **Website**: https://hana.network
+
+### Mobile Wallets
+
+#### LOBSTR
+Most popular Stellar mobile wallet.
+- **Website**: https://lobstr.co
+- **Platforms**: iOS, Android, Web
+- **Features**: DEX trading, multisig, 2FA, asset discovery
+
+#### Beans
+Payments platform with yield features.
+- **Use Case**: Payments, earning (via DeFindex/Blend)
+- **Features**: Non-custodial yield generation
+
+### Multi-Wallet Integration
+
+#### Stellar Wallets Kit
+SDK for integrating multiple Stellar wallets.
+- **GitHub**: https://github.com/Creit-Tech/Stellar-Wallets-Kit
+- **Supports**: Freighter, LOBSTR, xBull, Albedo, Rabet, Hana, Ledger, Trezor, WalletConnect
+
+## Developer Tools
+
+### Smart Account & Authentication
+
+#### Smart Account Kit (Recommended)
+Comprehensive TypeScript SDK for OpenZeppelin Smart Accounts on Stellar.
+- **GitHub**: https://github.com/kalepail/smart-account-kit
+- **Use Case**: Production smart wallets with passkeys
+- **Built On**: [OpenZeppelin stellar-contracts](https://github.com/OpenZeppelin/stellar-contracts)
+- **Features**:
+  - Context rules with fine-grained authorization scopes
+  - Policy support (threshold multisig, spending limits, custom policies)
+  - Session management with automatic credential persistence
+  - External wallet adapter support (Freighter, LOBSTR, etc.)
+  - Built-in indexer for contract discovery
+  - Multiple signer types (passkeys, Ed25519, policies)
+
+#### Passkey Kit (Legacy)
+Original TypeScript SDK for passkey-based smart wallets.
+- **GitHub**: https://github.com/kalepail/passkey-kit
+- **Status**: Legacy - use Smart Account Kit for new projects
+- **Use Case**: Simple passkey wallet integration
+- **Integration**: OpenZeppelin Relayer (gasless tx), Mercury (indexing)
+- **Demo**: [passkey-kit-demo.pages.dev](https://passkey-kit-demo.pages.dev)
+- **Example**: [Super Peach](https://github.com/kalepail/superpeach)
+
+#### OpenZeppelin Relayer
+Service for fee-sponsored transaction submission.
+- **Docs**: https://docs.openzeppelin.com/relayer
+- **Use Case**: Gasless transactions, fee sponsoring
+
+### Data Indexing
+
+For a full directory of indexing options, see [Stellar Indexer Docs](https://developers.stellar.org/docs/data/indexers).
+
+#### Mercury
+Stellar-native data indexing platform with Retroshades technology.
+- **Website**: https://mercurydata.app
+- **Docs**: https://docs.mercurydata.app
+- **Use Case**: Event indexing, data queries, automation
+- **Features**: Zephyr VM (serverless Rust execution at ledger close), GraphQL API
+
+#### SubQuery
+Multi-chain indexer supporting Stellar.
+- **Website**: https://subquery.network
+- **Quick Start**: https://subquery.network/doc/indexer/quickstart/quickstart_chains/stellar.html
+- **Features**: Block/transaction/operation/event handlers, multi-threading, 300+ chains
+
+#### Goldsky
+Real-time data replication and subgraph platform.
+- **Website**: https://goldsky.com
+- **Docs**: https://docs.goldsky.com/chains/stellar
+- **Features**: Mirror (real-time pipelines), subgraphs, on-chain + off-chain data
+
+#### Zephyr VM
+Cloud execution environment for blockchain data processing.
+- **GitHub**: https://github.com/xycloo/zephyr-vm
+- **Use Case**: Indexing, monitoring, automation
+- **Features**: Self-hostable, ledger-close execution
+
+### Contract Libraries
+
+#### OpenZeppelin Stellar Contracts
+Audited smart contract library for Stellar (track latest release tags before pinning versions).
+- **GitHub**: https://github.com/OpenZeppelin/stellar-contracts
+- **Docs**: https://developers.stellar.org/docs/tools/openzeppelin-contracts
+- **Contract Wizard**: https://wizard.openzeppelin.com/stellar
+- **Includes**: Tokens (fungible/NFT), governance (timelock), vaults (SEP-56), access control, fee forwarder
+- **Crates**: `stellar-tokens`, `stellar-access`, `stellar-contract-utils`
+
+### Security Tools
+
+#### Scout Soroban (CoinFabrik)
+Open-source vulnerability detector with 23 detectors for Stellar smart contracts.
+- **GitHub**: https://github.com/CoinFabrik/scout-soroban
+- **Install**: `cargo install cargo-scout-audit`
+- **Features**: CLI tool, VSCode extension, SARIF output for CI/CD
+- **Examples**: https://github.com/CoinFabrik/scout-soroban-examples
+
+#### OpenZeppelin Security Detectors SDK
+Framework for building custom security detectors for Stellar contracts.
+- **GitHub**: https://github.com/OpenZeppelin/soroban-security-detectors-sdk
+- **Detectors**: `auth_missing`, `unchecked_ft_transfer`, improper TTL, contract panics
+- **Extensible**: Load external detector libraries, CI/CD ready
+
+#### Certora Sunbeam Prover
+Formal verification for Stellar smart contracts — first WASM platform supported by Certora.
+- **Docs**: https://docs.certora.com/en/latest/docs/sunbeam/index.html
+- **Spec Language**: CVLR (Rust macros) — https://github.com/Certora/cvlr
+- **Reports**: [Blend V1 verification](https://www.certora.com/reports/blend-smart-contract-verification-report)
+- **Verifies at**: WASM bytecode level, eliminating compiler trust assumptions
+
+#### Runtime Verification — Komet
+Formal verification and testing tool designed for Stellar smart contracts (SCF-funded).
+- **Docs**: https://docs.runtimeverification.com/komet
+- **Repo**: https://github.com/runtimeverification/komet
+- **Spec Language**: Rust — property-based tests written in the same language as the contracts
+- **Operates at**: WASM bytecode level via [KWasm semantics](https://github.com/runtimeverification/wasm-semantics) (eliminates compiler trust assumptions)
+- **Features**: Fuzzing, testing, formal verification
+- **Reports**: https://github.com/runtimeverification/publications
+- **Example**: [TokenOps audit and verification report](https://github.com/runtimeverification/publications/blob/main/reports/smart-contracts/TokenOps.pdf)
+- **Blog**: [Introducing Komet](https://runtimeverification.com/blog/introducing-komet-smart-contract-testing-and-verification-tool-for-soroban-created-by-runtime-verification)
+
+#### Soroban Security Portal (Inferara)
+Community security knowledge base (SCF-funded).
+- **Website**: https://sorobansecurity.com
+- **Features**: Searchable audit reports, vulnerability database, best practices
+
+### CLI & SDKs
+
+#### Stellar CLI
+Official command-line interface for Stellar.
+- **Docs**: https://developers.stellar.org/docs/tools/stellar-cli
+- **Features**: Contract build, deploy, invoke, bindings generation
+
+#### Stellar SDK (JavaScript)
+Official JavaScript/TypeScript SDK.
+- **GitHub**: https://github.com/stellar/js-stellar-sdk
+- **npm**: `@stellar/stellar-sdk`
+
+#### Soroban Rust SDK
+Rust SDK for smart contract development.
+- **GitHub**: https://github.com/stellar/rs-soroban-sdk
+- **Crate**: `soroban-sdk`
+
+## Oracles
+
+#### Reflector Network
+Community-powered price oracle for Stellar.
+- **Website**: https://reflector.network
+- **Docs**: https://developers.stellar.org/docs/data/oracles/oracle-providers
+- **Features**: SEP-40 compatible, on-chain/off-chain prices, webhooks
+- **Integrations**: Blend, OrbitCDP, DeFindex, EquitX, Slender
+
+#### DIA Oracle
+Cross-chain oracle with 20,000+ asset support.
+- **Website**: https://diadata.org
+- **Blog**: https://www.diadata.org/blog/post/soroban-stellar-oracle-dia/
+- **Features**: VWAPIR methodology, custom feeds
+
+#### Band Protocol
+Cross-chain data oracle on BandChain.
+- **Website**: https://bandprotocol.com
+- **Architecture**: Cosmos SDK-based, cross-chain
+
+## Gaming & NFTs
+
+#### Litemint
+NFT marketplace and gaming platform.
+- **GitHub**: https://github.com/litemint/litemint-soroban-contracts
+- **Contracts**: Timed auctions, royalty payments
+- **Features**: Open/sealed bids, ascending/descending price, buy-now
+
+## Infrastructure
+
+### Anchors & On/Off Ramps
+
+#### Stellar Ramps
+Suite of open standards for fiat-crypto bridges.
+- **Docs**: https://stellar.org/use-cases/ramps
+- **SEPs**: SEP-6, SEP-24, SEP-31 (deposits/withdrawals/cross-border)
+
+#### Anchor Platform
+SDF-maintained platform for building SEP-compliant anchors.
+- **Docs**: https://developers.stellar.org/docs/learn/fundamentals/anchors
+- **GitHub**: https://github.com/stellar/java-stellar-anchor-sdk
+
+### Block Explorers
+
+#### StellarExpert
+Comprehensive network explorer with analytics.
+- **Website**: https://stellar.expert
+- **Features**: Transactions, accounts, assets, contracts
+
+#### Stellar Lab
+Developer tools and transaction builder.
+- **Website**: https://lab.stellar.org
+
+#### StellarChain
+Alternative explorer with contract support.
+- **Website**: https://stellarchain.io
+
+### Disbursements
+
+#### Stellar Disbursement Platform (SDP)
+Bulk payment infrastructure for enterprises.
+- **Docs**: https://developers.stellar.org/docs/category/use-the-stellar-disbursement-platform
+- **GitHub**: https://github.com/stellar/stellar-disbursement-platform
+- **Use Case**: Mass payments, aid distribution, payroll
+
+## Example Repositories
+
+### Official Examples
+
+#### Soroban Examples
+Official educational smart contract examples.
+- **GitHub**: https://github.com/stellar/soroban-examples
+- **Includes**: Tokens, atomic swaps, auth, events, liquidity pools, timelock, deployer, merkle distribution
+
+#### Soroban Example dApp
+Crowdfunding dApp with Next.js frontend.
+- **GitHub**: https://github.com/stellar/soroban-example-dapp
+- **Learning**: Full-stack contract development, Freighter integration
+
+### Community Examples
+
+#### Soroban Guide (Xycloo)
+Learning resources and example contracts.
+- **GitHub**: https://github.com/xycloo/soroban-guide
+- **Includes**: Events, rock-paper-scissors, vaults, Dutch auctions
+
+#### Soroban Contracts (icolomina)
+Governance and investment contract examples.
+- **GitHub**: https://github.com/icolomina/soroban-contracts
+- **Includes**: Ballot voting, investment contracts, multisig
+
+#### Oracle Example
+Publisher-subscriber oracle pattern.
+- **GitHub**: https://github.com/FredericRezeau/soroban-oracle-example
+- **Uses**: soroban-kit oracle module
+
+#### OZ Stellar NFT
+Simple NFT using OpenZeppelin.
+- **GitHub**: https://github.com/jamesbachini/OZ-Stellar-NFT
+
+## Cross-Chain
+
+#### Axelar
+Cross-chain gateway and Interchain Token Service for Stellar.
+- **GitHub**: https://github.com/axelarnetwork/axelar-amplifier-stellar
+- **Use Case**: Cross-chain messaging, token bridging, interoperability
+- **Status**: Active development (verify latest activity before integrating)
+
+#### Allbridge Core
+Cross-chain stable swap bridge (Stellar is 10th supported chain).
+- **Use Case**: Cross-chain stablecoin transfers (USDC between Stellar, Base, Arbitrum, etc.)
+- **Features**: Automatic Stellar account activation, liquidity pools
+
+#### LayerZero
+Omnichain interoperability protocol with Stellar support.
+- **Use Case**: Cross-chain messaging, token bridging (OFT/ONFT), dApp interoperability
+- **Features**: OApp standard, Omni-Chain Fungible Tokens, native issuer minting/burning control
+
+## Builder Teams & Companies
+
+Notable teams shipping production-level code on Stellar. For a broader directory, see [Stellar Ecosystem](https://stellar.org/ecosystem).
+
+| Team | Website | GitHub | X/Twitter | Notable Projects |
+|------|---------|--------|-----------|-----------------|
+| **Lightsail Network** | [lightsail.network](https://lightsail.network) | [lightsail-network](https://github.com/lightsail-network) | [@overcat_me](https://x.com/overcat_me) | Quasar RPC, Java/Python SDKs, Ledger app, validators |
+| **PaltaLabs** | [paltalabs.io](https://paltalabs.io) | [paltalabs](https://github.com/paltalabs) | [@PaltaLabs](https://x.com/PaltaLabs) | Soroswap, DeFindex |
+| **Aha Labs** | [ahalabs.dev](https://ahalabs.dev) | [AhaLabs](https://github.com/AhaLabs) | [@AhaLabsDev](https://x.com/AhaLabsDev) | Scaffold Stellar, Soroban CLI contributions |
+| **OpenZeppelin** | [openzeppelin.com](https://www.openzeppelin.com/networks/stellar) | [OpenZeppelin](https://github.com/OpenZeppelin/stellar-contracts) | [@OpenZeppelin](https://x.com/OpenZeppelin) | Contracts library, Relayer, Monitor, Security Detectors SDK |
+| **Cheesecake Labs** | [cheesecakelabs.com](https://cheesecakelabs.com) | [CheesecakeLabs](https://github.com/CheesecakeLabs) | [@CheesecakeLabs](https://x.com/CheesecakeLabs) | Stellar Plus library |
+| **Script3 / Blend Capital** | [script3.io](https://script3.io) | [script3](https://github.com/script3), [blend-capital](https://github.com/blend-capital) | [@script3official](https://x.com/script3official) | Blend Protocol |
+| **Xycloo Labs** | [xycloo.com](https://xycloo.com) | [Xycloo](https://github.com/Xycloo) | [@heytdep](https://x.com/heytdep) | Mercury indexer, Zephyr VM |
+| **CoinFabrik** | [coinfabrik.com](https://www.coinfabrik.com) | [CoinFabrik](https://github.com/CoinFabrik) | [@coinfabrik](https://x.com/coinfabrik) | Scout Soroban (static analysis) |
+| **Creit Tech** | [creit.tech](https://creit.tech) | [Creit-Tech](https://github.com/Creit-Tech) | [@CreitTech_](https://x.com/CreitTech_) | Stellar Wallets Kit, xBull, SorobanHub |
+| **Ultra Stellar** | [ultrastellar.com](https://ultrastellar.com) | [lobstrco](https://github.com/lobstrco) | [@Lobstrco](https://x.com/Lobstrco) | LOBSTR wallet, StellarExpert |
+
+## Project Directories
+
+### Official Directories
+
+#### Stellar Ecosystem Directory
+The canonical, up-to-date project directory maintained by SDF.
+- **Website**: https://stellar.org/ecosystem
+- **Features**: Search by country, asset, category
+- **Includes**: DeFi, wallets, anchors, on/off ramps, exchanges, infrastructure
+
+#### SCF Project Tracker
+All Stellar Community Fund–funded projects with status and milestones.
+- **Website**: https://communityfund.stellar.org/projects
+
+### Funding Programs
+
+#### Stellar Community Fund (SCF)
+Grants up to $150K per funding round.
+- **Website**: https://communityfund.stellar.org
+- **Funded**: 100+ projects across DeFi, NFT, GameFi, Web3
+
+#### Soroban Audit Bank
+Security audit funding for SCF projects.
+- **Website**: https://stellar.org/grants-and-funding/soroban-audit-bank
+- **Features**: Pre-negotiated audit rates, readiness checklist
+
+## Real-World Assets
+
+### Major Issuers on Stellar
+- **Franklin Templeton**: Regulated fund tokens
+- **Ondo**: Tokenized real estate
+- **RedSwan**: $100M commercial real estate
+- **Centrifuge**: Yield-generating tokens
+- **WisdomTree**: Asset-backed tokens
+
+### Stablecoins
+- **USDC** (Circle): Primary USD stablecoin
+- **EURC** (Circle): EUR stablecoin
+- **PYUSD** (PayPal): Verify current issuance and distribution details before launch planning
+
+## Enterprise Integrations
+
+Major companies building on Stellar:
+- **PayPal**: PYUSD stablecoin
+- **Visa**: Settlement infrastructure
+- **Mastercard**: Payment rails
+- **Wirex**: USDC/EURC settlement
+- **U.S. Bank**: Custom stablecoin testing
+- **PwC**: Stablecoin exploration
+
+---
+
+# Part 3: Curated Resources
+
+
+## Official Documentation
+
+### Stellar Developer Docs
+- [Stellar Documentation](https://developers.stellar.org/docs) - Primary documentation
+- [Build Smart Contracts](https://developers.stellar.org/docs/build/smart-contracts) - smart contract guides
+- [Build Apps](https://developers.stellar.org/docs/build/apps) - Client application guides
+- [Tools & SDKs](https://developers.stellar.org/docs/tools) - Available tooling
+- [Networks](https://developers.stellar.org/docs/networks) - Network configuration
+- [Learn Fundamentals](https://developers.stellar.org/docs/learn/fundamentals) - Core concepts
+- [Security Best Practices](https://developers.stellar.org/docs/build/security-docs)
+
+### API References
+- [Stellar RPC Methods](https://developers.stellar.org/docs/data/apis/rpc/api-reference/methods) - RPC API
+- [Horizon API](https://developers.stellar.org/docs/data/apis/horizon/api-reference) - REST API (legacy-focused)
+- [Oracle Providers](https://developers.stellar.org/docs/data/oracles/oracle-providers)
+
+## SDKs
+
+### Client SDKs (Application Development)
+- [JavaScript SDK](https://github.com/stellar/js-stellar-sdk) - `@stellar/stellar-sdk`
+- [Python SDK](https://github.com/StellarCN/py-stellar-base) - `stellar-sdk`
+- [Java SDK](https://github.com/lightsail-network/java-stellar-sdk) - `network.lightsail:stellar-sdk` (Lightsail Network)
+- [Go SDK](https://github.com/stellar/go-stellar-sdk) - `txnbuild`, Horizon & RPC clients
+- [Rust SDK (RPC Client)](https://github.com/stellar/rs-stellar-rpc-client)
+- [SDK Documentation](https://developers.stellar.org/docs/tools/sdks/client-sdks)
+
+### Contract SDK (Rust)
+- [Soroban Rust SDK](https://github.com/stellar/rs-soroban-sdk) - `soroban-sdk`
+- [Soroban SDK Docs](https://docs.rs/soroban-sdk/latest/soroban_sdk/) - Rust docs
+
+## CLI Tools
+
+### Stellar CLI
+- [Stellar CLI Repository](https://github.com/stellar/stellar-cli)
+- [CLI Installation](https://developers.stellar.org/docs/tools/stellar-cli)
+- [CLI Commands Reference](https://developers.stellar.org/docs/tools/stellar-cli/stellar-cli-commands)
+
+### Scaffold Stellar
+- [Scaffold Stellar](https://scaffoldstellar.org) - Full-stack dApp scaffolding (contracts + React/Vite/TS frontend)
+- [Scaffold Docs](https://developers.stellar.org/docs/tools/scaffold-stellar) - Official documentation
+- [GitHub](https://github.com/theahaco/scaffold-stellar) - Open source (Apache 2.0)
+
+### Quickstart (Local Development)
+- [Quickstart Docker](https://github.com/stellar/quickstart)
+- [Quickstart Guide](https://developers.stellar.org/docs/tools/quickstart)
+
+## Contract Libraries & Tools
+
+### OpenZeppelin Stellar Contracts
+- [OpenZeppelin Contracts](https://github.com/OpenZeppelin/stellar-contracts)
+- [Documentation](https://developers.stellar.org/docs/tools/openzeppelin-contracts)
+- [Contract Wizard](https://wizard.openzeppelin.com/stellar) - Generate contracts
+
+### Smart Account SDKs
+- [Smart Account Kit](https://github.com/kalepail/smart-account-kit) - Production smart wallet SDK (recommended)
+- [Passkey Kit](https://github.com/kalepail/passkey-kit) - Legacy passkey wallet SDK
+- [Super Peach](https://github.com/kalepail/superpeach) - Smart wallet implementation example
+
+### Developer Tools
+- [Stellar Wallets Kit](https://github.com/Creit-Tech/Stellar-Wallets-Kit) - Multi-wallet integration
+- [OpenZeppelin Relayer](https://docs.openzeppelin.com/relayer) - Fee-sponsored transactions
+
+## Example Repositories
+
+### Official Examples
+- [Soroban Examples](https://github.com/stellar/soroban-examples) - Core contract patterns
+- [Soroban Example dApp](https://github.com/stellar/soroban-example-dapp) - Crowdfunding Next.js app
+- [Stellar Repositories](https://github.com/orgs/stellar/repositories)
+
+### Community Examples
+- [Scout Soroban Examples](https://github.com/CoinFabrik/scout-soroban-examples) - Security-audited examples
+- [Soroban Guide (Xycloo)](https://github.com/xycloo/soroban-guide) - Learning resources
+- [Soroban Contracts (icolomina)](https://github.com/icolomina/soroban-contracts) - Governance examples
+- [Oracle Example](https://github.com/FredericRezeau/soroban-oracle-example) - Pub-sub oracle pattern
+- [OZ Stellar NFT](https://github.com/jamesbachini/OZ-Stellar-NFT) - Simple NFT with OpenZeppelin
+
+## Ecosystem Projects
+
+For DeFi protocols, wallets, oracles, gaming/NFTs, cross-chain bridges, and builder teams, see Part 2: Stellar Ecosystem below.
+
+## Security
+
+For vulnerability patterns, checklists, and detailed tooling guides, see [the smart contract security guide](/.well-known/agent-skills/smart-contracts/skill.md#security).
+
+### Bug Bounty Programs
+- [Stellar Bug Bounty (Immunefi)](https://immunefi.com/bug-bounty/stellar/) - Up to $250K, covers core + smart contract stack
+- [OpenZeppelin Stellar Bounty (Immunefi)](https://immunefi.com/bug-bounty/openzeppelin-stellar/) - Up to $25K
+- [HackerOne VDP](https://stellar.org/grants-and-funding/bug-bounty) - Web application vulnerabilities
+
+### Audit Bank & Audit Firms
+- [Soroban Audit Bank](https://stellar.org/grants-and-funding/soroban-audit-bank) - $3M+ deployed, 43+ audits
+- [Audited Projects List](https://stellar.org/audit-bank/projects) - Public audit registry
+- Partners: OtterSec, Veridise, Runtime Verification, CoinFabrik, QuarksLab, Coinspect, Certora, Halborn, Zellic, Code4rena
+
+### Static Analysis
+- [Scout Soroban](https://github.com/CoinFabrik/scout-soroban) - 23 vulnerability detectors, VSCode extension
+- [OZ Security Detectors SDK](https://github.com/OpenZeppelin/soroban-security-detectors-sdk) - Custom detector framework
+
+### Formal Verification
+- [Certora Sunbeam Prover](https://docs.certora.com/en/latest/docs/sunbeam/index.html) - WASM-level formal verification
+- [CVLR Spec Language](https://github.com/Certora/cvlr) - Certora Verification Language for Rust
+- [Runtime Verification Komet](https://runtimeverification.com/blog/introducing-komet-smart-contract-testing-and-verification-tool-for-soroban-created-by-runtime-verification) - contract verification tool
+
+### Security Resources
+- [Veridise Security Checklist](https://veridise.com/blog/audit-insights/building-on-stellar-soroban-grab-this-security-checklist-to-avoid-vulnerabilities/) - smart-contract security checklist
+- [Soroban Security Portal](https://sorobansecurity.com) - Community vulnerability database
+- [CoinFabrik Audit Reports](https://www.coinfabrik.com/smart-contract-audit-reports/)
+- [Certora Security Reports](https://github.com/Certora/SecurityReports) - Includes Stellar verifications
+
+## Zero-Knowledge Proofs (Status-Sensitive)
+
+For comprehensive ZK development guidance, see [zk-proofs.md](/.well-known/agent-skills/zk-proofs/skill.md).
+
+Always verify CAP status and network support before treating any ZK primitive as production-available.
+
+### Protocol & Specifications
+- [Protocol upgrades](https://stellar.org/protocol-upgrades) - Upgrade timeline and network context
+- [CAP-0074](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0074.md) - BN254 host functions proposal
+- [CAP-0075](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0075.md) - Poseidon/Poseidon2 host functions proposal
+
+### SDK Documentation
+- [Soroban SDK BN254 module](https://docs.rs/soroban-sdk/latest/soroban_sdk/crypto/bn254/) - Verify availability in your pinned SDK version
+- [Soroban SDK Crypto](https://docs.rs/soroban-sdk/latest/soroban_sdk/crypto/) - Full crypto module reference
+
+### Proving Systems & Tooling
+- [Noir Documentation](https://noir-lang.org/docs/) - Aztec's ZK domain-specific language
+- [RISC Zero](https://dev.risczero.com/) - General-purpose zkVM for Rust programs
+
+### Example Contracts
+- [Soroban Examples](https://github.com/stellar/soroban-examples) - Official examples (includes `groth16_verifier`, `privacy-pools`, `import_ark_bn254`)
+
+## Testing
+
+### Testing Guides
+- [Definitive Guide to Testing Smart Contracts](https://stellar.org/blog/developers/the-definitive-guide-to-testing-smart-contracts-on-stellar) - Comprehensive overview
+- [Fuzzing Guide](https://developers.stellar.org/docs/build/guides/testing/fuzzing) - cargo-fuzz + SorobanArbitrary
+- [Fuzzing Example Contract](https://developers.stellar.org/docs/build/smart-contracts/example-contracts/fuzzing)
+- [Differential Testing](https://developers.stellar.org/docs/build/guides/testing/differential-tests-with-test-snapshots) - Automatic test snapshots
+- [Fork Testing](https://developers.stellar.org/docs/build/guides/testing/fork-testing) - Test against production state
+- [Mutation Testing](https://developers.stellar.org/docs/build/guides/testing/mutation-testing) - cargo-mutants
+
+### Local Development
+- [Stellar Quickstart](https://github.com/stellar/quickstart)
+- [Docker Setup](https://developers.stellar.org/docs/tools/quickstart)
+
+### Test Networks
+- [Testnet Info](https://developers.stellar.org/docs/networks/testnet)
+- [Friendbot](https://friendbot.stellar.org) - Testnet faucet
+
+## Data & Analytics
+
+### Data Documentation Hub
+- [Stellar Data Overview](https://developers.stellar.org/docs/data) - Choose the right tool (APIs, indexers, analytics, oracles)
+- [Indexer Directory](https://developers.stellar.org/docs/data/indexers) - All supported indexers
+- [RPC Provider Directory](https://developers.stellar.org/docs/data/apis/rpc/providers) - All RPC infrastructure providers
+
+### Block Explorers
+- [StellarExpert](https://stellar.expert) - Network explorer & analytics
+- [StellarExpert API](https://stellar.expert/openapi.html) - Free REST API (no auth, CORS-enabled)
+- [Stellar Lab](https://lab.stellar.org) - Developer tools
+- [StellarChain](https://stellarchain.io) - Alternative explorer
+
+### Data Indexers
+- [Mercury](https://mercurydata.app) - Stellar-native indexer with Retroshades + GraphQL ([docs](https://docs.mercurydata.app))
+- [SubQuery](https://subquery.network) - Multi-chain indexer with Stellar support ([quick start](https://subquery.network/doc/indexer/quickstart/quickstart_chains/stellar.html))
+- [Goldsky](https://goldsky.com) - Real-time data replication pipelines + subgraphs ([Stellar docs](https://docs.goldsky.com/chains/stellar))
+- [Zephyr VM](https://github.com/xycloo/zephyr-vm) - Serverless Rust execution at ledger close
+
+### Historical Data & Analytics
+- [Hubble](https://developers.stellar.org/docs/data/analytics/hubble) - BigQuery dataset (updated every 30 min)
+- [Galexie](https://developers.stellar.org/docs/data/indexers/build-your-own/galexie) - Data pipeline for building data lakes
+- [Data Lake](https://developers.stellar.org/docs/data/apis/rpc/admin-guide/data-lake-integration) - Powers RPC Infinite Scroll (public via AWS Open Data)
+
+## Infrastructure
+
+### Anchors & On/Off Ramps
+- [Anchor Platform](https://github.com/stellar/java-stellar-anchor-sdk)
+- [Anchor Docs](https://developers.stellar.org/docs/category/anchor-platform)
+- [Anchor Fundamentals](https://developers.stellar.org/docs/learn/fundamentals/anchors)
+- [Stellar Ramps](https://stellar.org/use-cases/ramps)
+
+### Disbursements
+- [Stellar Disbursement Platform](https://github.com/stellar/stellar-disbursement-platform)
+- [SDP Documentation](https://developers.stellar.org/docs/category/use-the-stellar-disbursement-platform)
+
+### RPC Providers
+- [RPC Provider Directory](https://developers.stellar.org/docs/data/apis/rpc/providers) - Full list of providers
+- [Quasar (Lightsail Network)](https://quasar.lightsail.network) - Stellar-native RPC, Archive RPC, hosted Galexie Data Lake
+- [Blockdaemon](https://www.blockdaemon.com/soroban) - Enterprise RPC
+- [Validation Cloud](https://www.validationcloud.io) - Testnet & Mainnet
+- [QuickNode](https://www.quicknode.com) - Testnet, Mainnet & Dedicated
+- [Ankr](https://www.ankr.com) - Testnet & Mainnet
+- [NOWNodes](https://nownodes.io) - All networks incl. Futurenet
+- [GetBlock](https://getblock.io) - Testnet & Mainnet
+
+## Protocol & Governance
+
+### Stellar Protocol
+- [Stellar Protocol Repo](https://github.com/stellar/stellar-protocol)
+- [CAPs](https://github.com/stellar/stellar-protocol/tree/master/core) - Core Advancement Proposals
+- [SEPs](https://github.com/stellar/stellar-protocol/tree/master/ecosystem) - Stellar Ecosystem Proposals
+
+### Key SEP Standards
+- [SEP-0001](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md) - stellar.toml
+- [SEP-0010](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md) - Web Authentication
+- [SEP-0024](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md) - Hosted Deposit/Withdrawal
+- [SEP-0030](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0030.md) - Account Recovery
+- [SEP-0031](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md) - Cross-Border Payments
+- [SEP-0041](https://developers.stellar.org/docs/tokens/token-interface) - Token Interface
+- [SEP-0045](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0045.md) - Web Auth for Contract Accounts (Draft)
+- [SEP-0046](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0046.md) - Contract Meta (Active)
+- [SEP-0048](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0048.md) - Contract Interface Specification (Active)
+- [SEP-0050](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0050.md) - Non-Fungible Tokens (Draft)
+- [SEP-0056](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0056.md) - Tokenized Vault Standard (Draft, ERC-4626 equivalent)
+
+### Network Upgrades
+- [Protocol Upgrades](https://stellar.org/protocol-upgrades)
+- [SDF Blog](https://stellar.org/blog)
+
+## Project Directories & Funding
+
+### Ecosystem Discovery
+- [Stellar Ecosystem](https://stellar.org/ecosystem) - Official project directory
+- [Stellar Community Fund Projects](https://communityfund.stellar.org/projects)
+
+### Funding Programs
+- [Stellar Community Fund](https://communityfund.stellar.org) - Grants up to $150K
+- [Soroban Audit Bank](https://stellar.org/grants-and-funding/soroban-audit-bank)
+- [$100M Soroban Adoption Fund](https://stellar.org/soroban)
+
+## Learning Resources
+
+### Official Tutorials
+- [Getting Started](https://developers.stellar.org/docs/build/smart-contracts/getting-started)
+- [Hello World Contract](https://developers.stellar.org/docs/build/smart-contracts/getting-started/hello-world)
+- [Deploy to Testnet](https://developers.stellar.org/docs/build/smart-contracts/getting-started/deploy-to-testnet)
+- [TypeScript Bindings](https://developers.stellar.org/docs/build/apps/guestbook/bindings)
+- [Passkey Prerequisites](https://developers.stellar.org/docs/build/apps/guestbook/passkeys-prerequisites)
+
+### Video Content
+- [Stellar YouTube](https://www.youtube.com/@StellarDevelopmentFoundation)
+- [Learn Rust for Smart Contracts (DAO Series)](https://www.youtube.com/watch?v=VeQM5N-0DrI)
+- [Call Option Contract Walkthrough](https://www.youtube.com/watch?v=Z8FHVllP_D0)
+- [Blend Protocol Tutorial](https://www.youtube.com/watch?v=58j0QkXKiDU)
+
+### Developer Tools
+- [Stella AI Bot](https://developers.stellar.org/docs/tools/developer-tools) - AI assistant for Stellar developer questions
+- [Soroban Playground](https://soropg.com) - Browser-based smart contract IDE ([GitHub](https://github.com/jamesbachini/Soroban-Playground))
+
+### Blog Posts & Guides
+- [Composability on Stellar](https://stellar.org/blog/developers/composability-on-stellar-from-concept-to-reality)
+- [Testing Smart Contracts Guide](https://stellar.org/blog/developers/the-definitive-guide-to-testing-smart-contracts-on-stellar)
+- [Sorobounty Spectacular Tutorials](https://stellar.org/blog/developers/sorobounty-spectacular-dapp-tutorials)
+- [Learn Soroban 1-2-3 (Community Tools)](https://stellar.org/blog/developers/learn-soroban-as-easy-as-1-2-3-with-community-made-tooling)
+- [SCF Infrastructure Recap](https://stellar.org/blog/ecosystem/stellar-community-fund-recap-soroban-infrastructure)
+- [Native vs Soroban Tokens](https://cheesecakelabs.com/blog/native-tokens-vs-soroban-tokens/)
+- [57Blocks Integration Testing](https://57blocks.com/blog/soroban-integration-testing-best-practices)
+
+## Stablecoins on Stellar
+
+### Major Stablecoins
+- [USDC on Stellar](https://www.circle.com/usdc/stellar) - Circle
+- [EURC on Stellar](https://www.circle.com/en/eurc) - Circle
+- PYUSD (PayPal) - Verify current issuer/distribution details before integration
+
+### Asset Discovery
+- [StellarExpert Asset Directory](https://stellar.expert/explorer/public/asset)
+
+## Community
+
+### Developer Resources
+- [Stellar Developers Discord](https://discord.gg/stellar)
+- [Stellar Stack Exchange](https://stellar.stackexchange.com)
+- [GitHub Discussions](https://github.com/stellar/stellar-protocol/discussions)
+
+### Key People to Follow
+
+Builders and contributors actively shaping the Stellar ecosystem:
+
+| Name | GitHub | X/Twitter | Focus |
+|------|--------|-----------|-------|
+| Tyler van der Hoeven | [kalepail](https://github.com/kalepail) | [@kalepail](https://x.com/kalepail) | SDF DevRel, Smart Account Kit, Passkey Kit, Launchtube |
+| Leigh McCulloch | [leighmcculloch](https://github.com/leighmcculloch) | [@___leigh___](https://x.com/___leigh___) | SDF core engineer, Stellar CLI, Soroban SDK |
+| James Bachini | [jamesbachini](https://github.com/jamesbachini) | [@james_bachini](https://x.com/james_bachini) | SDF Dev in Residence, Soroban Playground, tutorials |
+| Elliot Voris | [ElliotFriend](https://github.com/ElliotFriend) | [@ElliotFriend](https://x.com/ElliotFriend) | SDF DevRel, community education |
+| Carsten Jacobsen | [carstenjacobsen](https://github.com/carstenjacobsen) | — | SDF, weekly dev meetings, Soroban examples |
+| Esteban Iglesias | [esteblock](https://github.com/esteblock) | [@esteblock_dev](https://x.com/esteblock_dev) | PaltaLabs, Soroswap, DeFindex |
+| Markus Paulson-Luna | [markuspluna](https://github.com/markuspluna) | [@script3official](https://x.com/script3official) | Script3, Blend Protocol |
+| Alexander Mootz | [mootz12](https://github.com/mootz12) | — | Script3, Blend contracts |
+| Tommaso | [heytdep](https://github.com/heytdep) | [@heytdep](https://x.com/heytdep) | Xycloo Labs, Mercury indexer, ZephyrVM |
+| OrbitLens | [orbitlens](https://github.com/orbitlens) | [@orbitlens](https://x.com/orbitlens) | Reflector oracle, StellarExpert, Albedo |
+| Frederic Rezeau | [FredericRezeau](https://github.com/FredericRezeau) | [@FredericRezeau](https://x.com/FredericRezeau) | Litemint, soroban-kit, gaming |
+| Jun Luo (Overcat) | [overcat](https://github.com/overcat) | [@overcat_me](https://x.com/overcat_me) | Lightsail Network, Quasar RPC, Java/Python SDKs, Ledger app |
+| Jay Geng | [jayz22](https://github.com/jayz22) | — | SDF, Soroban SDK, confidential tokens |
+| Chad Ostrowski | [chadoh](https://github.com/chadoh) | [@chadoh](https://x.com/chadoh) | Aha Labs CEO, Scaffold Stellar, Soroban CLI |
+| Willem Wyndham | [willemneal](https://github.com/willemneal) | [@willemneal](https://x.com/willemneal) | Aha Labs co-founder, Scaffold Stellar, JS contract client |
+
+### Builder Teams & Companies
+See Part 2: Stellar Ecosystem above for a table of teams shipping production code on Stellar, with GitHub orgs, websites, and Twitter handles.
+
+### Foundation
+- [Stellar Development Foundation](https://stellar.org/foundation)
+- [Foundation Roadmap](https://stellar.org/foundation/roadmap)
+- [Ecosystem Blog](https://stellar.org/blog/ecosystem)
diff --git a/.mintlify/skills/zk-proofs/SKILL.md b/.mintlify/skills/zk-proofs/SKILL.md
new file mode 100644
index 000000000..f9aa5dbee
--- /dev/null
+++ b/.mintlify/skills/zk-proofs/SKILL.md
@@ -0,0 +1,234 @@
+---
+name: zk-proofs
+description: Zero-knowledge proofs and privacy patterns on Stellar. Covers Groth16 verification in smart contracts via BLS12-381 host functions (CAP-0059, available), the BN254 + Poseidon proposals (CAP-0074/0075, status-sensitive), and concrete toolchain walkthroughs for Circom (on-chain verifiable today), Noir, and RISC Zero (attestation pattern until BN254 lands). Use when building privacy-preserving applications, ZK-verifier contracts, or wiring a proving toolchain to Stellar.
+user-invocable: true
+argument-hint: "[zk task]"
+---
+
+# Zero-Knowledge Proofs & Privacy
+
+ZK verification on Stellar. Capability is protocol- and SDK-version dependent — always verify CAP status, network version, and `soroban-sdk` host-function support before relying on a primitive.
+
+## When to use this skill
+- Implementing a Groth16 (or other SNARK) verifier as a Stellar smart contract
+- Wiring Circom, Noir, or RISC Zero output to on-chain verification
+- Building privacy pools, confidential tokens, or Merkle-tree-backed commitments
+- Planning for BN254 / Poseidon availability
+
+## Related skills
+- Contract patterns and deployment → `/.well-known/agent-skills/smart-contracts/skill.md#development-patterns`
+- Verifier security review → `/.well-known/agent-skills/smart-contracts/skill.md#security`
+- CAPs referenced here → `/.well-known/agent-skills/standards/skill.md`
+
+## What's available — verify before building
+
+| Primitive | CAP | Status |
+|-----------|-----|--------|
+| BLS12-381 ops (G1/G2 add, mul, MSM, pairing check, hash-to-curve, Fr arithmetic) | [CAP-0059](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0059.md) | **Available** (Protocol 22+) |
+| BN254 host functions | [CAP-0074](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0074.md) | Proposed — check current status |
+| Poseidon/Poseidon2 hash | [CAP-0075](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0075.md) | Proposed — check current status |
+
+Before implementation, always confirm:
+1. CAP status in the preamble (`Accepted`/`Implemented` vs draft)
+2. Target network protocol version ([software versions](https://developers.stellar.org/docs/networks/software-versions))
+3. `soroban-sdk` release support for the host functions you need
+
+**The curve decides everything.** BLS12-381 proofs verify natively on-chain today; BN254 proofs (Circom's default, Barretenberg, RISC Zero's Groth16 wrapper) are gated on CAP-0074.
+
+| Toolchain | Proof system | Curve | On-chain on Stellar |
+|-----------|--------------|-------|---------------------|
+| Circom + snarkjs (`-p bls12381`) | Groth16 | BLS12-381 | ✅ Today, via CAP-0059 |
+| Circom + snarkjs (default) | Groth16 | BN254 | Gated on CAP-0074 |
+| Noir + Barretenberg | UltraHonk | BN254 | Not yet — attest off-chain verification |
+| RISC Zero (STARK → Groth16 wrap) | Groth16 | BN254 | Gated on CAP-0074 — attest meanwhile |
+
+## The on-chain verifier (Groth16 over BLS12-381)
+
+The official [groth16_verifier example](https://github.com/stellar/soroban-examples/tree/main/groth16_verifier) is the canonical implementation — the full contract:
+
+```rust
+#![no_std]
+use soroban_sdk::{
+    contract, contracterror, contractimpl, contracttype,
+    crypto::bls12_381::{Fr, G1Affine, G2Affine},
+    vec, Env, Vec,
+};
+
+#[contracterror]
+#[derive(Copy, Clone, Debug, Eq, PartialEq, PartialOrd, Ord)]
+#[repr(u32)]
+pub enum Groth16Error {
+    MalformedVerifyingKey = 0,
+}
+
+#[derive(Clone)]
+#[contracttype]
+pub struct VerificationKey {
+    pub alpha: G1Affine,
+    pub beta: G2Affine,
+    pub gamma: G2Affine,
+    pub delta: G2Affine,
+    pub ic: Vec<G1Affine>,
+}
+
+#[derive(Clone)]
+#[contracttype]
+pub struct Proof {
+    pub a: G1Affine,
+    pub b: G2Affine,
+    pub c: G1Affine,
+}
+
+#[contract]
+pub struct Groth16Verifier;
+
+#[contractimpl]
+impl Groth16Verifier {
+    pub fn verify_proof(
+        env: Env,
+        vk: VerificationKey,
+        proof: Proof,
+        pub_signals: Vec<Fr>,
+    ) -> Result<bool, Groth16Error> {
+        let bls = env.crypto().bls12_381();
+
+        // vk_x = ic[0] + sum(pub_signals[i] * ic[i+1])
+        if pub_signals.len() + 1 != vk.ic.len() {
+            return Err(Groth16Error::MalformedVerifyingKey);
+        }
+        let mut vk_x = vk.ic.get(0).unwrap();
+        for (s, v) in pub_signals.iter().zip(vk.ic.iter().skip(1)) {
+            let prod = bls.g1_mul(&v, &s);
+            vk_x = bls.g1_add(&vk_x, &prod);
+        }
+
+        // e(-A, B) * e(alpha, beta) * e(vk_x, gamma) * e(C, delta) == 1
+        let neg_a = -proof.a;
+        let vp1 = vec![&env, neg_a, vk.alpha, vk_x, proof.c];
+        let vp2 = vec![&env, proof.b, vk.beta, vk.gamma, vk.delta];
+
+        Ok(bls.pairing_check(vp1, vp2))
+    }
+}
+```
+
+Point encodings are uncompressed big-endian: `G1Affine` wraps 96 bytes, `G2Affine` 192 bytes, `Fr` 32 bytes. The example's test suite shows the exact conversion from arkworks types (`ark-bls12-381` + `ark-serialize`) — reuse it when building fixtures from your proving toolchain's JSON output.
+
+In production, wrap this verifier with application logic: fix the `VerificationKey` at deploy time (constructor) instead of taking it as a call argument, and bind proofs to context (see [Pitfalls](#pitfalls)).
+
+## Walkthrough: Circom → on-chain verification (works today)
+
+Circom supports BLS12-381 as a target field — this makes it the toolchain that verifies natively on Stellar right now.
+
+```bash
+# 1. Circuit
+cat > multiplier.circom <<'EOF'
+pragma circom 2.1.6;
+template Multiplier() {
+    signal input a;
+    signal input b;
+    signal output c;
+    c <== a * b;
+}
+component main = Multiplier();
+EOF
+
+# 2. Compile for BLS12-381 (NOT the default bn128 — that's gated on CAP-0074)
+circom multiplier.circom --r1cs --wasm -p bls12381
+
+# 3. Trusted setup (powers of tau on bls12-381, then circuit-specific phase 2)
+snarkjs powersoftau new bls12-381 12 pot12_0000.ptau
+snarkjs powersoftau contribute pot12_0000.ptau pot12_0001.ptau --name="contrib" -e="random"
+snarkjs powersoftau prepare phase2 pot12_0001.ptau pot12_final.ptau
+snarkjs groth16 setup multiplier.r1cs pot12_final.ptau multiplier.zkey
+snarkjs zkey export verificationkey multiplier.zkey verification_key.json
+
+# 4. Witness + proof
+echo '{"a": 3, "b": 11}' > input.json
+node multiplier_js/generate_witness.js multiplier_js/multiplier.wasm input.json witness.wtns
+snarkjs groth16 prove multiplier.zkey witness.wtns proof.json public.json
+
+# 5. Sanity-check off-chain before going on-chain
+snarkjs groth16 verify verification_key.json public.json proof.json
+```
+
+Then convert `proof.json` / `verification_key.json` (decimal-string coordinates) into the contract's types — serialize each point uncompressed big-endian into the 96/192-byte layouts, e.g. via arkworks as in the example's tests — and invoke `verify_proof`. Public signals (`public.json`) become the `Vec<Fr>` argument; the contract must also validate what those signals *mean* (see [Pitfalls](#pitfalls)).
+
+For real applications the per-proof flow is: client proves locally (WASM prover or native), submits `(proof, public_signals)` in a contract invocation, contract verifies + applies policy + updates state.
+
+## Walkthrough: Noir (off-chain verify + attestation, for now)
+
+Noir's standard backend (Barretenberg) produces UltraHonk proofs over BN254 — neither the proof system nor the curve is on-chain verifiable on Stellar today.
+
+```bash
+# Local proving workflow
+nargo new age_check && cd age_check
+cat > src/main.nr <<'EOF'
+fn main(age: u64, threshold: pub u64) {
+    assert(age >= threshold);
+}
+EOF
+nargo check
+nargo execute witness          # writes the witness from Prover.toml inputs
+bb prove -b target/age_check.json -w target/witness.gz -o target/proof
+bb verify -k target/vk -p target/proof   # off-chain verification
+```
+
+On Stellar, two patterns until the curve/system gap closes:
+
+1. **Attestation oracle**: a verifier service runs `bb verify` (or the Noir JS verifier) off-chain and submits a signed attestation; the contract `require_auth()`s the attester address and applies policy. The trust assumption (the attester) must be explicit and documented — this is *not* trustless ZK, it's a verifiable-computation oracle.
+2. **Switch the proving stack for on-chain parts**: express the on-chain-critical statement as a Circom/Groth16-BLS12-381 circuit (walkthrough above) and keep Noir for off-chain components.
+
+Track CAP-0074 (BN254): when implemented, BN254 Groth16 verification becomes possible — but UltraHonk would additionally need a verifier implementation in-contract, so Groth16-based paths will land first.
+
+## Walkthrough: RISC Zero (same gate, clear path)
+
+RISC Zero proves arbitrary Rust execution (zkVM) and can wrap its STARK receipts into a Groth16 proof over BN254 ("stark-to-snark") — small enough for on-chain verification where BN254 is supported.
+
+```rust
+// Guest (runs inside the zkVM): the computation being proven
+use risc0_zkvm::guest::env;
+
+fn main() {
+    let input: u64 = env::read();
+    let result = expensive_check(input);
+    env::commit(&result);          // becomes part of the public journal
+}
+```
+
+```rust
+// Host: produce and verify a receipt locally
+let receipt = prover.prove(env, ELF)?.receipt;
+receipt.verify(IMAGE_ID)?;         // off-chain verification
+```
+
+On Stellar today, use the **attestation pattern** (as with Noir): verify the receipt off-chain — locally or via a proving service — and have an authorized attester submit the journal + attestation to your contract. Once CAP-0074 (BN254) is implemented, the Groth16-wrapped receipt becomes verifiable natively with a BN254 verifier contract mirroring the BLS12-381 one above; the `IMAGE_ID` (which program ran) and journal digest become public inputs. See the [RISC Zero docs](https://dev.risczero.com/api) for the wrapping workflow.
+
+## Architecture patterns
+
+- **Verification gateway**: isolate cryptographic checks in a dedicated verifier contract/module — normalize inputs, verify, emit explicit success/failure events. Smaller audit surface, cleaner upgrades.
+- **Policy-and-proof split**: `Verifier` (cryptographic validity) → `Policy` (business/compliance rules) → `Application` (state transition). Each independently testable and upgradeable.
+- **Capability gating**: enable ZK flows only where required primitives are confirmed available; keep deterministic fallbacks and document the supported network/protocol matrix.
+
+For Merkle-tree commitments (privacy pools, allowlists): until Poseidon (CAP-0075) lands, in-circuit-friendly hashing on-chain is expensive — design trees so the contract only needs root comparisons and membership proofs verified inside the SNARK.
+
+## Pitfalls
+
+- **Verifying the proof but not the statement.** A valid proof only shows *some* witness satisfies the circuit. The contract must validate the public inputs' semantics: who is this proof for, which Merkle root, which action, which amount.
+- **Missing anti-replay binding.** Valid proofs can be replayed. Bind a nonce/session/action into the public inputs and persist a replay guard (nullifier set) on-chain.
+- **Curve mismatch.** Circom defaults to bn128; on Stellar compile with `-p bls12381` or your proof will be unverifiable on-chain.
+- **Trusted-setup hygiene.** Groth16 needs a circuit-specific phase-2 setup; for production use a real multi-party ceremony, not a single-contributor dev setup.
+- **Hardcoded protocol assumptions.** Capability-gate; don't assume draft CAPs are live on the target network.
+
+## Testing
+
+- Unit: input domain validation, replay protection, event correctness, malformed/tampered proof rejection (negative paths are the important ones)
+- Integration: full prove → submit → verify → state-transition flow against a local network
+- Operational: resource costs for realistic proof sizes via simulation (`--send=no`) — pairing checks are expensive; budget before committing to per-transaction verification
+
+## References
+
+- [groth16_verifier example](https://github.com/stellar/soroban-examples/tree/main/groth16_verifier) — canonical verifier + arkworks test fixtures
+- [soroban-examples](https://github.com/stellar/soroban-examples)
+- [BLS12-381 SDK docs](https://docs.rs/soroban-sdk/latest/soroban_sdk/crypto/bls12_381/index.html)
+- [Circom docs](https://docs.circom.io) · [snarkjs](https://github.com/iden3/snarkjs) · [Noir docs](https://noir-lang.org/docs) · [RISC Zero docs](https://dev.risczero.com)
diff --git a/Dockerfile b/Dockerfile
deleted file mode 100644
index f6b3a08b3..000000000
--- a/Dockerfile
+++ /dev/null
@@ -1,32 +0,0 @@
-FROM ubuntu:26.04 AS build
-
-LABEL maintainer="SDF Ops Team <ops@stellar.org>"
-
-WORKDIR /app
-
-ENV DEBIAN_FRONTEND=noninteractive
-ENV INLINE_RUNTIME_CHUNK=false
-RUN apt-get update && apt-get install --no-install-recommends -y gpg curl git make ca-certificates apt-transport-https && \
-    curl -sSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key|gpg --dearmor >/etc/apt/trusted.gpg.d/nodesource-key.gpg && \
-    echo "deb https://deb.nodesource.com/node_24.x nodistro main" | tee /etc/apt/sources.list.d/nodesource.list && \
-    apt-get update && apt-get install -y nodejs libatomic1 && apt-get clean
-
-ENV PNPM_HOME="/pnpm"
-ENV PATH="$PNPM_HOME/bin:$PATH"
-RUN corepack enable
-
-COPY . /app/
-
-RUN pnpm ci
-RUN du -sh /app/*
-RUN pnpm rpcspec:build --no-minify
-RUN pnpm stellar-cli:build --no-minify --cli-ref=main
-RUN pnpm stellar-cli:fix-links
-
-ENV NODE_OPTIONS="--max-old-space-size=4096"
-RUN pnpm build --no-minify
-
-FROM nginx:1.31
-
-COPY --from=build /app/build/ /usr/share/nginx/html/
-COPY nginx /etc/nginx/
diff --git a/Makefile b/Makefile
deleted file mode 100644
index 564a4a97d..000000000
--- a/Makefile
+++ /dev/null
@@ -1,16 +0,0 @@
-###
-# Check if we need to prepend docker commands with sudo
-SUDO := $(shell docker version >/dev/null 2>&1 || echo "sudo")
-
-# If LABEL is not provided set default value
-LABEL ?= $(shell git rev-parse --short HEAD)$(and $(shell git status -s),-dirty-$(shell id -u -n))
-# If TAG is not provided set default value
-TAG ?= stellar/stellar-docs:$(LABEL)
-# https://github.com/opencontainers/image-spec/blob/master/annotations.md
-BUILD_DATE := $(shell date -u +%FT%TZ)
-# the app label is used by the pipelines to prune docker dangling images on the jenkins build hosts
-docker-build:
-	$(SUDO) docker build -m 8g --no-cache --pull --label app="stellar-docs" --label org.opencontainers.image.created="$(BUILD_DATE)" -t $(TAG) .
-
-docker-push:
-	$(SUDO) docker push $(TAG)
diff --git a/static/assets/SDP/SDP1.png b/assets/SDP/SDP1.png
similarity index 100%
rename from static/assets/SDP/SDP1.png
rename to assets/SDP/SDP1.png
diff --git a/static/assets/SDP/SDP19.png b/assets/SDP/SDP19.png
similarity index 100%
rename from static/assets/SDP/SDP19.png
rename to assets/SDP/SDP19.png
diff --git a/static/assets/SDP/SDP2-2.png b/assets/SDP/SDP2-2.png
similarity index 100%
rename from static/assets/SDP/SDP2-2.png
rename to assets/SDP/SDP2-2.png
diff --git a/static/assets/SDP/SDP20.png b/assets/SDP/SDP20.png
similarity index 100%
rename from static/assets/SDP/SDP20.png
rename to assets/SDP/SDP20.png
diff --git a/static/assets/SDP/SDP20x.png b/assets/SDP/SDP20x.png
similarity index 100%
rename from static/assets/SDP/SDP20x.png
rename to assets/SDP/SDP20x.png
diff --git a/static/assets/SDP/SDP22.png b/assets/SDP/SDP22.png
similarity index 100%
rename from static/assets/SDP/SDP22.png
rename to assets/SDP/SDP22.png
diff --git a/static/assets/SDP/SDP23.png b/assets/SDP/SDP23.png
similarity index 100%
rename from static/assets/SDP/SDP23.png
rename to assets/SDP/SDP23.png
diff --git a/static/assets/SDP/SDP24.png b/assets/SDP/SDP24.png
similarity index 100%
rename from static/assets/SDP/SDP24.png
rename to assets/SDP/SDP24.png
diff --git a/static/assets/SDP/SDP25.png b/assets/SDP/SDP25.png
similarity index 100%
rename from static/assets/SDP/SDP25.png
rename to assets/SDP/SDP25.png
diff --git a/static/assets/SDP/SDP30.png b/assets/SDP/SDP30.png
similarity index 100%
rename from static/assets/SDP/SDP30.png
rename to assets/SDP/SDP30.png
diff --git a/static/assets/SDP/SDP31.png b/assets/SDP/SDP31.png
similarity index 100%
rename from static/assets/SDP/SDP31.png
rename to assets/SDP/SDP31.png
diff --git a/static/assets/SDP/SDP32.png b/assets/SDP/SDP32.png
similarity index 100%
rename from static/assets/SDP/SDP32.png
rename to assets/SDP/SDP32.png
diff --git a/static/assets/SDP/SDP33.png b/assets/SDP/SDP33.png
similarity index 100%
rename from static/assets/SDP/SDP33.png
rename to assets/SDP/SDP33.png
diff --git a/static/assets/SDP/SDP34.png b/assets/SDP/SDP34.png
similarity index 100%
rename from static/assets/SDP/SDP34.png
rename to assets/SDP/SDP34.png
diff --git a/static/assets/SDP/SDP35.png b/assets/SDP/SDP35.png
similarity index 100%
rename from static/assets/SDP/SDP35.png
rename to assets/SDP/SDP35.png
diff --git a/static/assets/SDP/SDP36.png b/assets/SDP/SDP36.png
similarity index 100%
rename from static/assets/SDP/SDP36.png
rename to assets/SDP/SDP36.png
diff --git a/static/assets/SDP/SDP37.png b/assets/SDP/SDP37.png
similarity index 100%
rename from static/assets/SDP/SDP37.png
rename to assets/SDP/SDP37.png
diff --git a/static/assets/SDP/SDP38.png b/assets/SDP/SDP38.png
similarity index 100%
rename from static/assets/SDP/SDP38.png
rename to assets/SDP/SDP38.png
diff --git a/static/assets/SDP/SDP39.png b/assets/SDP/SDP39.png
similarity index 100%
rename from static/assets/SDP/SDP39.png
rename to assets/SDP/SDP39.png
diff --git a/static/assets/SDP/SDP40.png b/assets/SDP/SDP40.png
similarity index 100%
rename from static/assets/SDP/SDP40.png
rename to assets/SDP/SDP40.png
diff --git a/static/assets/SDP/SDP41.png b/assets/SDP/SDP41.png
similarity index 100%
rename from static/assets/SDP/SDP41.png
rename to assets/SDP/SDP41.png
diff --git a/static/assets/SDP/SDP42.png b/assets/SDP/SDP42.png
similarity index 100%
rename from static/assets/SDP/SDP42.png
rename to assets/SDP/SDP42.png
diff --git a/static/assets/SDP/SDP43.png b/assets/SDP/SDP43.png
similarity index 100%
rename from static/assets/SDP/SDP43.png
rename to assets/SDP/SDP43.png
diff --git a/static/assets/SDP/SDP44.png b/assets/SDP/SDP44.png
similarity index 100%
rename from static/assets/SDP/SDP44.png
rename to assets/SDP/SDP44.png
diff --git a/static/assets/SDP/SDP45.png b/assets/SDP/SDP45.png
similarity index 100%
rename from static/assets/SDP/SDP45.png
rename to assets/SDP/SDP45.png
diff --git a/static/assets/SDP/SDP46.png b/assets/SDP/SDP46.png
similarity index 100%
rename from static/assets/SDP/SDP46.png
rename to assets/SDP/SDP46.png
diff --git a/static/assets/SDP/SDP47.png b/assets/SDP/SDP47.png
similarity index 100%
rename from static/assets/SDP/SDP47.png
rename to assets/SDP/SDP47.png
diff --git a/static/assets/SDP/SDP48.png b/assets/SDP/SDP48.png
similarity index 100%
rename from static/assets/SDP/SDP48.png
rename to assets/SDP/SDP48.png
diff --git a/static/assets/SDP/SDP49.png b/assets/SDP/SDP49.png
similarity index 100%
rename from static/assets/SDP/SDP49.png
rename to assets/SDP/SDP49.png
diff --git a/static/assets/SDP/SDP50.png b/assets/SDP/SDP50.png
similarity index 100%
rename from static/assets/SDP/SDP50.png
rename to assets/SDP/SDP50.png
diff --git a/static/assets/ap/anchor-platform-architecture-1.png b/assets/ap/anchor-platform-architecture-1.png
similarity index 100%
rename from static/assets/ap/anchor-platform-architecture-1.png
rename to assets/ap/anchor-platform-architecture-1.png
diff --git a/static/assets/ap/anchor-platform-architecture-2.png b/assets/ap/anchor-platform-architecture-2.png
similarity index 100%
rename from static/assets/ap/anchor-platform-architecture-2.png
rename to assets/ap/anchor-platform-architecture-2.png
diff --git a/static/assets/ap/anchor-platform-sep24-demo-wallet-widget.png b/assets/ap/anchor-platform-sep24-demo-wallet-widget.png
similarity index 100%
rename from static/assets/ap/anchor-platform-sep24-demo-wallet-widget.png
rename to assets/ap/anchor-platform-sep24-demo-wallet-widget.png
diff --git a/static/assets/ap/anchor-platform-sep24-demo-wallet.png b/assets/ap/anchor-platform-sep24-demo-wallet.png
similarity index 100%
rename from static/assets/ap/anchor-platform-sep24-demo-wallet.png
rename to assets/ap/anchor-platform-sep24-demo-wallet.png
diff --git a/static/assets/ap/anchor-platform-sep31-demo-wallet-widget.png b/assets/ap/anchor-platform-sep31-demo-wallet-widget.png
similarity index 100%
rename from static/assets/ap/anchor-platform-sep31-demo-wallet-widget.png
rename to assets/ap/anchor-platform-sep31-demo-wallet-widget.png
diff --git a/static/assets/ap/sep24-deposit-flow-diagram.png b/assets/ap/sep24-deposit-flow-diagram.png
similarity index 100%
rename from static/assets/ap/sep24-deposit-flow-diagram.png
rename to assets/ap/sep24-deposit-flow-diagram.png
diff --git a/static/assets/ap/sep24-withdrawal-flow-diagram.png b/assets/ap/sep24-withdrawal-flow-diagram.png
similarity index 100%
rename from static/assets/ap/sep24-withdrawal-flow-diagram.png
rename to assets/ap/sep24-withdrawal-flow-diagram.png
diff --git a/static/assets/ap/sep31-transition-diagram.png b/assets/ap/sep31-transition-diagram.png
similarity index 100%
rename from static/assets/ap/sep31-transition-diagram.png
rename to assets/ap/sep31-transition-diagram.png
diff --git a/static/assets/ap/sep6-deposit-flow-diagram.png b/assets/ap/sep6-deposit-flow-diagram.png
similarity index 100%
rename from static/assets/ap/sep6-deposit-flow-diagram.png
rename to assets/ap/sep6-deposit-flow-diagram.png
diff --git a/static/assets/ap/sep6-withdrawal-flow-diagram.png b/assets/ap/sep6-withdrawal-flow-diagram.png
similarity index 100%
rename from static/assets/ap/sep6-withdrawal-flow-diagram.png
rename to assets/ap/sep6-withdrawal-flow-diagram.png
diff --git a/static/assets/api/rpc/getevents.jpg b/assets/api/rpc/getevents.jpg
similarity index 100%
rename from static/assets/api/rpc/getevents.jpg
rename to assets/api/rpc/getevents.jpg
diff --git a/static/assets/api/rpc/getfeestats.png b/assets/api/rpc/getfeestats.png
similarity index 100%
rename from static/assets/api/rpc/getfeestats.png
rename to assets/api/rpc/getfeestats.png
diff --git a/static/assets/api/rpc/gethealth.png b/assets/api/rpc/gethealth.png
similarity index 100%
rename from static/assets/api/rpc/gethealth.png
rename to assets/api/rpc/gethealth.png
diff --git a/static/assets/api/rpc/getlatestledger.png b/assets/api/rpc/getlatestledger.png
similarity index 100%
rename from static/assets/api/rpc/getlatestledger.png
rename to assets/api/rpc/getlatestledger.png
diff --git a/static/assets/api/rpc/getledgerentries-01.gif b/assets/api/rpc/getledgerentries-01.gif
similarity index 100%
rename from static/assets/api/rpc/getledgerentries-01.gif
rename to assets/api/rpc/getledgerentries-01.gif
diff --git a/static/assets/api/rpc/getledgerentries-02.gif b/assets/api/rpc/getledgerentries-02.gif
similarity index 100%
rename from static/assets/api/rpc/getledgerentries-02.gif
rename to assets/api/rpc/getledgerentries-02.gif
diff --git a/static/assets/api/rpc/getledgers.gif b/assets/api/rpc/getledgers.gif
similarity index 100%
rename from static/assets/api/rpc/getledgers.gif
rename to assets/api/rpc/getledgers.gif
diff --git a/static/assets/api/rpc/getnetwork.png b/assets/api/rpc/getnetwork.png
similarity index 100%
rename from static/assets/api/rpc/getnetwork.png
rename to assets/api/rpc/getnetwork.png
diff --git a/static/assets/api/rpc/gettransaction.gif b/assets/api/rpc/gettransaction.gif
similarity index 100%
rename from static/assets/api/rpc/gettransaction.gif
rename to assets/api/rpc/gettransaction.gif
diff --git a/static/assets/api/rpc/gettransactions.png b/assets/api/rpc/gettransactions.png
similarity index 100%
rename from static/assets/api/rpc/gettransactions.png
rename to assets/api/rpc/gettransactions.png
diff --git a/static/assets/api/rpc/getversioninfo.png b/assets/api/rpc/getversioninfo.png
similarity index 100%
rename from static/assets/api/rpc/getversioninfo.png
rename to assets/api/rpc/getversioninfo.png
diff --git a/static/assets/api/rpc/sendtransaction.gif b/assets/api/rpc/sendtransaction.gif
similarity index 100%
rename from static/assets/api/rpc/sendtransaction.gif
rename to assets/api/rpc/sendtransaction.gif
diff --git a/static/assets/api/rpc/simulatetransaction.gif b/assets/api/rpc/simulatetransaction.gif
similarity index 100%
rename from static/assets/api/rpc/simulatetransaction.gif
rename to assets/api/rpc/simulatetransaction.gif
diff --git a/static/assets/audits/2024-01-03 - Veridise - stellar-core v20.0.0 - soroban.pdf b/assets/audits/2024-01-03 - Veridise - stellar-core v20.0.0 - soroban.pdf
similarity index 100%
rename from static/assets/audits/2024-01-03 - Veridise - stellar-core v20.0.0 - soroban.pdf
rename to assets/audits/2024-01-03 - Veridise - stellar-core v20.0.0 - soroban.pdf
diff --git a/assets/audits/2024-01-03-veridise-stellar-core-v20.0.0-soroban.pdf b/assets/audits/2024-01-03-veridise-stellar-core-v20.0.0-soroban.pdf
new file mode 100644
index 000000000..ba6ac4791
Binary files /dev/null and b/assets/audits/2024-01-03-veridise-stellar-core-v20.0.0-soroban.pdf differ
diff --git a/static/assets/audits/2024-12-20 - OtterSec - stellar-rpc commit a60044e.pdf b/assets/audits/2024-12-20 - OtterSec - stellar-rpc commit a60044e.pdf
similarity index 100%
rename from static/assets/audits/2024-12-20 - OtterSec - stellar-rpc commit a60044e.pdf
rename to assets/audits/2024-12-20 - OtterSec - stellar-rpc commit a60044e.pdf
diff --git a/assets/audits/2024-12-20-ottersec-stellar-rpc-commit-a60044e.pdf b/assets/audits/2024-12-20-ottersec-stellar-rpc-commit-a60044e.pdf
new file mode 100644
index 000000000..f4462c394
Binary files /dev/null and b/assets/audits/2024-12-20-ottersec-stellar-rpc-commit-a60044e.pdf differ
diff --git a/static/assets/audits/2025-10-17 - Oak - stellar-core v23.0.0 - protocol 23 changes.pdf b/assets/audits/2025-10-17 - Oak - stellar-core v23.0.0 - protocol 23 changes.pdf
similarity index 100%
rename from static/assets/audits/2025-10-17 - Oak - stellar-core v23.0.0 - protocol 23 changes.pdf
rename to assets/audits/2025-10-17 - Oak - stellar-core v23.0.0 - protocol 23 changes.pdf
diff --git a/assets/audits/2025-10-17-oak-stellar-core-v23.0.0-protocol-23-changes.pdf b/assets/audits/2025-10-17-oak-stellar-core-v23.0.0-protocol-23-changes.pdf
new file mode 100644
index 000000000..3c27c5a65
Binary files /dev/null and b/assets/audits/2025-10-17-oak-stellar-core-v23.0.0-protocol-23-changes.pdf differ
diff --git a/static/assets/audits/2025-11-13 - Oak - stellar-core v24.0.0 - protocol 24 changes.pdf b/assets/audits/2025-11-13 - Oak - stellar-core v24.0.0 - protocol 24 changes.pdf
similarity index 100%
rename from static/assets/audits/2025-11-13 - Oak - stellar-core v24.0.0 - protocol 24 changes.pdf
rename to assets/audits/2025-11-13 - Oak - stellar-core v24.0.0 - protocol 24 changes.pdf
diff --git a/assets/audits/2025-11-13-oak-stellar-core-v24.0.0-protocol-24-changes.pdf b/assets/audits/2025-11-13-oak-stellar-core-v24.0.0-protocol-24-changes.pdf
new file mode 100644
index 000000000..cb6becc31
Binary files /dev/null and b/assets/audits/2025-11-13-oak-stellar-core-v24.0.0-protocol-24-changes.pdf differ
diff --git a/static/assets/audits/2026-02-06 - Runtime Verification - stellar-core v25.0.0 - soroban environment.pdf b/assets/audits/2026-02-06 - Runtime Verification - stellar-core v25.0.0 - soroban environment.pdf
similarity index 100%
rename from static/assets/audits/2026-02-06 - Runtime Verification - stellar-core v25.0.0 - soroban environment.pdf
rename to assets/audits/2026-02-06 - Runtime Verification - stellar-core v25.0.0 - soroban environment.pdf
diff --git a/assets/audits/2026-02-06-runtime-verification-stellar-core-v25.0.0-soroban-environment.pdf b/assets/audits/2026-02-06-runtime-verification-stellar-core-v25.0.0-soroban-environment.pdf
new file mode 100644
index 000000000..b359faed0
Binary files /dev/null and b/assets/audits/2026-02-06-runtime-verification-stellar-core-v25.0.0-soroban-environment.pdf differ
diff --git a/static/assets/audits/2027-03-07 - Halborn - bytes-lit v0.0.5.pdf b/assets/audits/2027-03-07 - Halborn - bytes-lit v0.0.5.pdf
similarity index 100%
rename from static/assets/audits/2027-03-07 - Halborn - bytes-lit v0.0.5.pdf
rename to assets/audits/2027-03-07 - Halborn - bytes-lit v0.0.5.pdf
diff --git a/static/assets/audits/2027-03-07 - Halborn - crates-git-revision v0.0.6.pdf b/assets/audits/2027-03-07 - Halborn - crates-git-revision v0.0.6.pdf
similarity index 100%
rename from static/assets/audits/2027-03-07 - Halborn - crates-git-revision v0.0.6.pdf
rename to assets/audits/2027-03-07 - Halborn - crates-git-revision v0.0.6.pdf
diff --git a/static/assets/audits/2027-03-07 - Halborn - soroban-poseidon v25.0.0.pdf b/assets/audits/2027-03-07 - Halborn - soroban-poseidon v25.0.0.pdf
similarity index 100%
rename from static/assets/audits/2027-03-07 - Halborn - soroban-poseidon v25.0.0.pdf
rename to assets/audits/2027-03-07 - Halborn - soroban-poseidon v25.0.0.pdf
diff --git a/static/assets/audits/2027-03-07 - Halborn - soroban-sdk v25.1.0.pdf b/assets/audits/2027-03-07 - Halborn - soroban-sdk v25.1.0.pdf
similarity index 100%
rename from static/assets/audits/2027-03-07 - Halborn - soroban-sdk v25.1.0.pdf
rename to assets/audits/2027-03-07 - Halborn - soroban-sdk v25.1.0.pdf
diff --git a/static/assets/audits/2027-03-07 - Halborn - stellar-strkey v0.0.13 v0.0.16.pdf b/assets/audits/2027-03-07 - Halborn - stellar-strkey v0.0.13 v0.0.16.pdf
similarity index 100%
rename from static/assets/audits/2027-03-07 - Halborn - stellar-strkey v0.0.13 v0.0.16.pdf
rename to assets/audits/2027-03-07 - Halborn - stellar-strkey v0.0.13 v0.0.16.pdf
diff --git a/assets/audits/2027-03-07-halborn-bytes-lit-v0.0.5.pdf b/assets/audits/2027-03-07-halborn-bytes-lit-v0.0.5.pdf
new file mode 100644
index 000000000..fb8bd86d5
Binary files /dev/null and b/assets/audits/2027-03-07-halborn-bytes-lit-v0.0.5.pdf differ
diff --git a/assets/audits/2027-03-07-halborn-crates-git-revision-v0.0.6.pdf b/assets/audits/2027-03-07-halborn-crates-git-revision-v0.0.6.pdf
new file mode 100644
index 000000000..09fae38a1
Binary files /dev/null and b/assets/audits/2027-03-07-halborn-crates-git-revision-v0.0.6.pdf differ
diff --git a/assets/audits/2027-03-07-halborn-soroban-poseidon-v25.0.0.pdf b/assets/audits/2027-03-07-halborn-soroban-poseidon-v25.0.0.pdf
new file mode 100644
index 000000000..2bb9af566
Binary files /dev/null and b/assets/audits/2027-03-07-halborn-soroban-poseidon-v25.0.0.pdf differ
diff --git a/assets/audits/2027-03-07-halborn-soroban-sdk-v25.1.0.pdf b/assets/audits/2027-03-07-halborn-soroban-sdk-v25.1.0.pdf
new file mode 100644
index 000000000..31e480bac
Binary files /dev/null and b/assets/audits/2027-03-07-halborn-soroban-sdk-v25.1.0.pdf differ
diff --git a/assets/audits/2027-03-07-halborn-stellar-strkey-v0.0.13-v0.0.16.pdf b/assets/audits/2027-03-07-halborn-stellar-strkey-v0.0.13-v0.0.16.pdf
new file mode 100644
index 000000000..ba71038d7
Binary files /dev/null and b/assets/audits/2027-03-07-halborn-stellar-strkey-v0.0.13-v0.0.16.pdf differ
diff --git a/static/assets/basic-pay/add-assets.png b/assets/basic-pay/add-assets.png
similarity index 100%
rename from static/assets/basic-pay/add-assets.png
rename to assets/basic-pay/add-assets.png
diff --git a/static/assets/basic-pay/add-contact.png b/assets/basic-pay/add-contact.png
similarity index 100%
rename from static/assets/basic-pay/add-contact.png
rename to assets/basic-pay/add-contact.png
diff --git a/static/assets/basic-pay/auth_valid.png b/assets/basic-pay/auth_valid.png
similarity index 100%
rename from static/assets/basic-pay/auth_valid.png
rename to assets/basic-pay/auth_valid.png
diff --git a/static/assets/basic-pay/authenticate.png b/assets/basic-pay/authenticate.png
similarity index 100%
rename from static/assets/basic-pay/authenticate.png
rename to assets/basic-pay/authenticate.png
diff --git a/static/assets/basic-pay/confirm-pincode.png b/assets/basic-pay/confirm-pincode.png
similarity index 100%
rename from static/assets/basic-pay/confirm-pincode.png
rename to assets/basic-pay/confirm-pincode.png
diff --git a/static/assets/basic-pay/display-assets.png b/assets/basic-pay/display-assets.png
similarity index 100%
rename from static/assets/basic-pay/display-assets.png
rename to assets/basic-pay/display-assets.png
diff --git a/static/assets/basic-pay/fees.png b/assets/basic-pay/fees.png
similarity index 100%
rename from static/assets/basic-pay/fees.png
rename to assets/basic-pay/fees.png
diff --git a/static/assets/basic-pay/funded-account.png b/assets/basic-pay/funded-account.png
similarity index 100%
rename from static/assets/basic-pay/funded-account.png
rename to assets/basic-pay/funded-account.png
diff --git a/static/assets/basic-pay/kyc_accepted.png b/assets/basic-pay/kyc_accepted.png
similarity index 100%
rename from static/assets/basic-pay/kyc_accepted.png
rename to assets/basic-pay/kyc_accepted.png
diff --git a/static/assets/basic-pay/path-payment.png b/assets/basic-pay/path-payment.png
similarity index 100%
rename from static/assets/basic-pay/path-payment.png
rename to assets/basic-pay/path-payment.png
diff --git a/static/assets/basic-pay/payment.png b/assets/basic-pay/payment.png
similarity index 100%
rename from static/assets/basic-pay/payment.png
rename to assets/basic-pay/payment.png
diff --git a/static/assets/basic-pay/public-and-private-keys.png b/assets/basic-pay/public-and-private-keys.png
similarity index 100%
rename from static/assets/basic-pay/public-and-private-keys.png
rename to assets/basic-pay/public-and-private-keys.png
diff --git a/static/assets/basic-pay/sep24_transfers.png b/assets/basic-pay/sep24_transfers.png
similarity index 100%
rename from static/assets/basic-pay/sep24_transfers.png
rename to assets/basic-pay/sep24_transfers.png
diff --git a/static/assets/basic-pay/sep6_deposit_withdraw.png b/assets/basic-pay/sep6_deposit_withdraw.png
similarity index 100%
rename from static/assets/basic-pay/sep6_deposit_withdraw.png
rename to assets/basic-pay/sep6_deposit_withdraw.png
diff --git a/static/assets/basic-pay/sep6_kyc.png b/assets/basic-pay/sep6_kyc.png
similarity index 100%
rename from static/assets/basic-pay/sep6_kyc.png
rename to assets/basic-pay/sep6_kyc.png
diff --git a/static/assets/basic-pay/sep6_transfer_details.png b/assets/basic-pay/sep6_transfer_details.png
similarity index 100%
rename from static/assets/basic-pay/sep6_transfer_details.png
rename to assets/basic-pay/sep6_transfer_details.png
diff --git a/static/assets/clawback/example1.png b/assets/clawback/example1.png
similarity index 100%
rename from static/assets/clawback/example1.png
rename to assets/clawback/example1.png
diff --git a/static/assets/contract/contract-info-meta.png b/assets/contract/contract-info-meta.png
similarity index 100%
rename from static/assets/contract/contract-info-meta.png
rename to assets/contract/contract-info-meta.png
diff --git a/static/assets/contract/contract-info-spec.png b/assets/contract/contract-info-spec.png
similarity index 100%
rename from static/assets/contract/contract-info-spec.png
rename to assets/contract/contract-info-spec.png
diff --git a/static/assets/dev-tools/blux_demo.gif b/assets/dev-tools/blux_demo.gif
similarity index 100%
rename from static/assets/dev-tools/blux_demo.gif
rename to assets/dev-tools/blux_demo.gif
diff --git a/static/assets/dev-tools/jupyter-notebooks.png b/assets/dev-tools/jupyter-notebooks.png
similarity index 100%
rename from static/assets/dev-tools/jupyter-notebooks.png
rename to assets/dev-tools/jupyter-notebooks.png
diff --git a/static/assets/dev-tools/stellar-wallet-kit.gif b/assets/dev-tools/stellar-wallet-kit.gif
similarity index 100%
rename from static/assets/dev-tools/stellar-wallet-kit.gif
rename to assets/dev-tools/stellar-wallet-kit.gif
diff --git a/static/assets/diagrams/environment-concepts.png b/assets/diagrams/environment-concepts.png
similarity index 100%
rename from static/assets/diagrams/environment-concepts.png
rename to assets/diagrams/environment-concepts.png
diff --git a/static/assets/diagrams/soroban_fees.png b/assets/diagrams/soroban_fees.png
similarity index 100%
rename from static/assets/diagrams/soroban_fees.png
rename to assets/diagrams/soroban_fees.png
diff --git a/static/assets/diagrams/stellar-tech-stack.png b/assets/diagrams/stellar-tech-stack.png
similarity index 100%
rename from static/assets/diagrams/stellar-tech-stack.png
rename to assets/diagrams/stellar-tech-stack.png
diff --git a/static/assets/diagrams/validator_complete.png b/assets/diagrams/validator_complete.png
similarity index 100%
rename from static/assets/diagrams/validator_complete.png
rename to assets/diagrams/validator_complete.png
diff --git a/static/assets/galexie/galexie-architecture.png b/assets/galexie/galexie-architecture.png
similarity index 100%
rename from static/assets/galexie/galexie-architecture.png
rename to assets/galexie/galexie-architecture.png
diff --git a/static/assets/guestbook/frontend.png b/assets/guestbook/frontend.png
similarity index 100%
rename from static/assets/guestbook/frontend.png
rename to assets/guestbook/frontend.png
diff --git a/static/assets/guestbook/github_template.png b/assets/guestbook/github_template.png
similarity index 100%
rename from static/assets/guestbook/github_template.png
rename to assets/guestbook/github_template.png
diff --git a/static/assets/guides/fee-bump-transaction.png b/assets/guides/fee-bump-transaction.png
similarity index 100%
rename from static/assets/guides/fee-bump-transaction.png
rename to assets/guides/fee-bump-transaction.png
diff --git a/static/assets/guides/x402-demo.png b/assets/guides/x402-demo.png
similarity index 100%
rename from static/assets/guides/x402-demo.png
rename to assets/guides/x402-demo.png
diff --git a/static/assets/horizon-scaling/Topology-ingestion-isolation.png b/assets/horizon-scaling/Topology-ingestion-isolation.png
old mode 100755
new mode 100644
similarity index 100%
rename from static/assets/horizon-scaling/Topology-ingestion-isolation.png
rename to assets/horizon-scaling/Topology-ingestion-isolation.png
diff --git a/static/assets/horizon-scaling/Topology-multiple.png b/assets/horizon-scaling/Topology-multiple.png
old mode 100755
new mode 100644
similarity index 100%
rename from static/assets/horizon-scaling/Topology-multiple.png
rename to assets/horizon-scaling/Topology-multiple.png
diff --git a/static/assets/horizon-scaling/Topology-single.png b/assets/horizon-scaling/Topology-single.png
old mode 100755
new mode 100644
similarity index 100%
rename from static/assets/horizon-scaling/Topology-single.png
rename to assets/horizon-scaling/Topology-single.png
diff --git a/static/assets/horizon-scaling/Topology-txsub.png b/assets/horizon-scaling/Topology-txsub.png
old mode 100755
new mode 100644
similarity index 100%
rename from static/assets/horizon-scaling/Topology-txsub.png
rename to assets/horizon-scaling/Topology-txsub.png
diff --git a/static/assets/ingest-sdk/architecture.png b/assets/ingest-sdk/architecture.png
similarity index 100%
rename from static/assets/ingest-sdk/architecture.png
rename to assets/ingest-sdk/architecture.png
diff --git a/static/assets/ingest-sdk/bufferedstoragebackend_architecture.png b/assets/ingest-sdk/bufferedstoragebackend_architecture.png
similarity index 100%
rename from static/assets/ingest-sdk/bufferedstoragebackend_architecture.png
rename to assets/ingest-sdk/bufferedstoragebackend_architecture.png
diff --git a/static/assets/ingest-sdk/cdp_pipelines.png b/assets/ingest-sdk/cdp_pipelines.png
similarity index 100%
rename from static/assets/ingest-sdk/cdp_pipelines.png
rename to assets/ingest-sdk/cdp_pipelines.png
diff --git a/static/assets/lab/ab-tx-dashboard-01232026.png b/assets/lab/ab-tx-dashboard-01232026.png
similarity index 100%
rename from static/assets/lab/ab-tx-dashboard-01232026.png
rename to assets/lab/ab-tx-dashboard-01232026.png
diff --git a/static/assets/lab/horizon-assets-usdc-response.png b/assets/lab/horizon-assets-usdc-response.png
similarity index 100%
rename from static/assets/lab/horizon-assets-usdc-response.png
rename to assets/lab/horizon-assets-usdc-response.png
diff --git a/static/assets/lab/horizon-assets-usdc.png b/assets/lab/horizon-assets-usdc.png
similarity index 100%
rename from static/assets/lab/horizon-assets-usdc.png
rename to assets/lab/horizon-assets-usdc.png
diff --git a/static/assets/lab/horizon-assets.png b/assets/lab/horizon-assets.png
similarity index 100%
rename from static/assets/lab/horizon-assets.png
rename to assets/lab/horizon-assets.png
diff --git a/static/assets/lab/horizon-endpoints.png b/assets/lab/horizon-endpoints.png
similarity index 100%
rename from static/assets/lab/horizon-endpoints.png
rename to assets/lab/horizon-endpoints.png
diff --git a/static/assets/lab/horizon-payments-response.png b/assets/lab/horizon-payments-response.png
similarity index 100%
rename from static/assets/lab/horizon-payments-response.png
rename to assets/lab/horizon-payments-response.png
diff --git a/static/assets/lab/horizon-payments.png b/assets/lab/horizon-payments.png
similarity index 100%
rename from static/assets/lab/horizon-payments.png
rename to assets/lab/horizon-payments.png
diff --git a/static/assets/lab/horizon-save-modal.png b/assets/lab/horizon-save-modal.png
similarity index 100%
rename from static/assets/lab/horizon-save-modal.png
rename to assets/lab/horizon-save-modal.png
diff --git a/static/assets/lab/horizon-save.png b/assets/lab/horizon-save.png
similarity index 100%
rename from static/assets/lab/horizon-save.png
rename to assets/lab/horizon-save.png
diff --git a/static/assets/lab/horizon-share.png b/assets/lab/horizon-share.png
similarity index 100%
rename from static/assets/lab/horizon-share.png
rename to assets/lab/horizon-share.png
diff --git a/static/assets/lab/lab-01232026.png b/assets/lab/lab-01232026.png
similarity index 100%
rename from static/assets/lab/lab-01232026.png
rename to assets/lab/lab-01232026.png
diff --git a/static/assets/lab/lab-account-saved-manual.png b/assets/lab/lab-account-saved-manual.png
similarity index 100%
rename from static/assets/lab/lab-account-saved-manual.png
rename to assets/lab/lab-account-saved-manual.png
diff --git a/static/assets/lab/lab-account-saved-usage-public.png b/assets/lab/lab-account-saved-usage-public.png
similarity index 100%
rename from static/assets/lab/lab-account-saved-usage-public.png
rename to assets/lab/lab-account-saved-usage-public.png
diff --git a/static/assets/lab/lab-account-saved-usage-secret.png b/assets/lab/lab-account-saved-usage-secret.png
similarity index 100%
rename from static/assets/lab/lab-account-saved-usage-secret.png
rename to assets/lab/lab-account-saved-usage-secret.png
diff --git a/static/assets/lab/lab-account-saved.png b/assets/lab/lab-account-saved.png
similarity index 100%
rename from static/assets/lab/lab-account-saved.png
rename to assets/lab/lab-account-saved.png
diff --git a/static/assets/lab/lab-already-uploaded.gif b/assets/lab/lab-already-uploaded.gif
similarity index 100%
rename from static/assets/lab/lab-already-uploaded.gif
rename to assets/lab/lab-already-uploaded.gif
diff --git a/static/assets/lab/lab-contract-explorer-build.png b/assets/lab/lab-contract-explorer-build.png
similarity index 100%
rename from static/assets/lab/lab-contract-explorer-build.png
rename to assets/lab/lab-contract-explorer-build.png
diff --git a/static/assets/lab/lab-contract-explorer-info.png b/assets/lab/lab-contract-explorer-info.png
similarity index 100%
rename from static/assets/lab/lab-contract-explorer-info.png
rename to assets/lab/lab-contract-explorer-info.png
diff --git a/static/assets/lab/lab-contract-explorer-invoke.gif b/assets/lab/lab-contract-explorer-invoke.gif
similarity index 100%
rename from static/assets/lab/lab-contract-explorer-invoke.gif
rename to assets/lab/lab-contract-explorer-invoke.gif
diff --git a/static/assets/lab/lab-contract-explorer-source.png b/assets/lab/lab-contract-explorer-source.png
similarity index 100%
rename from static/assets/lab/lab-contract-explorer-source.png
rename to assets/lab/lab-contract-explorer-source.png
diff --git a/static/assets/lab/lab-contract-explorer-spec.png b/assets/lab/lab-contract-explorer-spec.png
similarity index 100%
rename from static/assets/lab/lab-contract-explorer-spec.png
rename to assets/lab/lab-contract-explorer-spec.png
diff --git a/static/assets/lab/lab-contract-explorer-storage.png b/assets/lab/lab-contract-explorer-storage.png
similarity index 100%
rename from static/assets/lab/lab-contract-explorer-storage.png
rename to assets/lab/lab-contract-explorer-storage.png
diff --git a/static/assets/lab/lab-contract-explorer-version.png b/assets/lab/lab-contract-explorer-version.png
similarity index 100%
rename from static/assets/lab/lab-contract-explorer-version.png
rename to assets/lab/lab-contract-explorer-version.png
diff --git a/static/assets/lab/lab-contract-explorer.png b/assets/lab/lab-contract-explorer.png
similarity index 100%
rename from static/assets/lab/lab-contract-explorer.png
rename to assets/lab/lab-contract-explorer.png
diff --git a/static/assets/lab/lab-custom-network.png b/assets/lab/lab-custom-network.png
similarity index 100%
rename from static/assets/lab/lab-custom-network.png
rename to assets/lab/lab-custom-network.png
diff --git a/static/assets/lab/lab-deploy-contract.gif b/assets/lab/lab-deploy-contract.gif
similarity index 100%
rename from static/assets/lab/lab-deploy-contract.gif
rename to assets/lab/lab-deploy-contract.gif
diff --git a/static/assets/lab/lab-events.png b/assets/lab/lab-events.png
similarity index 100%
rename from static/assets/lab/lab-events.png
rename to assets/lab/lab-events.png
diff --git a/static/assets/lab/lab-fee.png b/assets/lab/lab-fee.png
similarity index 100%
rename from static/assets/lab/lab-fee.png
rename to assets/lab/lab-fee.png
diff --git a/static/assets/lab/lab-fund-01232026.png b/assets/lab/lab-fund-01232026.png
similarity index 100%
rename from static/assets/lab/lab-fund-01232026.png
rename to assets/lab/lab-fund-01232026.png
diff --git a/static/assets/lab/lab-horizon-saved-requests.png b/assets/lab/lab-horizon-saved-requests.png
similarity index 100%
rename from static/assets/lab/lab-horizon-saved-requests.png
rename to assets/lab/lab-horizon-saved-requests.png
diff --git a/static/assets/lab/lab-horizon-view-docs.png b/assets/lab/lab-horizon-view-docs.png
similarity index 100%
rename from static/assets/lab/lab-horizon-view-docs.png
rename to assets/lab/lab-horizon-view-docs.png
diff --git a/static/assets/lab/lab-keypair-01232026.png b/assets/lab/lab-keypair-01232026.png
similarity index 100%
rename from static/assets/lab/lab-keypair-01232026.png
rename to assets/lab/lab-keypair-01232026.png
diff --git a/static/assets/lab/lab-resource-profiler.png b/assets/lab/lab-resource-profiler.png
similarity index 100%
rename from static/assets/lab/lab-resource-profiler.png
rename to assets/lab/lab-resource-profiler.png
diff --git a/static/assets/lab/lab-rpc-methods-saved.png b/assets/lab/lab-rpc-methods-saved.png
similarity index 100%
rename from static/assets/lab/lab-rpc-methods-saved.png
rename to assets/lab/lab-rpc-methods-saved.png
diff --git a/static/assets/lab/lab-signatures.png b/assets/lab/lab-signatures.png
similarity index 100%
rename from static/assets/lab/lab-signatures.png
rename to assets/lab/lab-signatures.png
diff --git a/static/assets/lab/lab-single-account-response.png b/assets/lab/lab-single-account-response.png
similarity index 100%
rename from static/assets/lab/lab-single-account-response.png
rename to assets/lab/lab-single-account-response.png
diff --git a/static/assets/lab/lab-single-account.png b/assets/lab/lab-single-account.png
similarity index 100%
rename from static/assets/lab/lab-single-account.png
rename to assets/lab/lab-single-account.png
diff --git a/static/assets/lab/lab-state-change.png b/assets/lab/lab-state-change.png
similarity index 100%
rename from static/assets/lab/lab-state-change.png
rename to assets/lab/lab-state-change.png
diff --git a/static/assets/lab/lab-token-contracts.png b/assets/lab/lab-token-contracts.png
similarity index 100%
rename from static/assets/lab/lab-token-contracts.png
rename to assets/lab/lab-token-contracts.png
diff --git a/static/assets/lab/lab-token-summary.png b/assets/lab/lab-token-summary.png
similarity index 100%
rename from static/assets/lab/lab-token-summary.png
rename to assets/lab/lab-token-summary.png
diff --git a/static/assets/lab/lab-transactions-build.png b/assets/lab/lab-transactions-build.png
similarity index 100%
rename from static/assets/lab/lab-transactions-build.png
rename to assets/lab/lab-transactions-build.png
diff --git a/static/assets/lab/lab-transactions-ops.png b/assets/lab/lab-transactions-ops.png
similarity index 100%
rename from static/assets/lab/lab-transactions-ops.png
rename to assets/lab/lab-transactions-ops.png
diff --git a/static/assets/lab/lab-transactions-response-error.png b/assets/lab/lab-transactions-response-error.png
similarity index 100%
rename from static/assets/lab/lab-transactions-response-error.png
rename to assets/lab/lab-transactions-response-error.png
diff --git a/static/assets/lab/lab-transactions-response-success.png b/assets/lab/lab-transactions-response-success.png
similarity index 100%
rename from static/assets/lab/lab-transactions-response-success.png
rename to assets/lab/lab-transactions-response-success.png
diff --git a/static/assets/lab/lab-transactions-saved.png b/assets/lab/lab-transactions-saved.png
similarity index 100%
rename from static/assets/lab/lab-transactions-saved.png
rename to assets/lab/lab-transactions-saved.png
diff --git a/static/assets/lab/lab-tx-details.png b/assets/lab/lab-tx-details.png
similarity index 100%
rename from static/assets/lab/lab-tx-details.png
rename to assets/lab/lab-tx-details.png
diff --git a/static/assets/lab/lab-upload-contract.gif b/assets/lab/lab-upload-contract.gif
similarity index 100%
rename from static/assets/lab/lab-upload-contract.gif
rename to assets/lab/lab-upload-contract.gif
diff --git a/static/assets/lab/lab-upload-deploy-page.png b/assets/lab/lab-upload-deploy-page.png
similarity index 100%
rename from static/assets/lab/lab-upload-deploy-page.png
rename to assets/lab/lab-upload-deploy-page.png
diff --git a/static/assets/lab/lab-xdr-diff-dropdown.png b/assets/lab/lab-xdr-diff-dropdown.png
similarity index 100%
rename from static/assets/lab/lab-xdr-diff-dropdown.png
rename to assets/lab/lab-xdr-diff-dropdown.png
diff --git a/static/assets/lab/lab-xdr-diff-filled.png b/assets/lab/lab-xdr-diff-filled.png
similarity index 100%
rename from static/assets/lab/lab-xdr-diff-filled.png
rename to assets/lab/lab-xdr-diff-filled.png
diff --git a/static/assets/lab/lab-xdr-diff.png b/assets/lab/lab-xdr-diff.png
similarity index 100%
rename from static/assets/lab/lab-xdr-diff.png
rename to assets/lab/lab-xdr-diff.png
diff --git a/static/assets/lab/lab-xdr-from-json-dropdown.png b/assets/lab/lab-xdr-from-json-dropdown.png
similarity index 100%
rename from static/assets/lab/lab-xdr-from-json-dropdown.png
rename to assets/lab/lab-xdr-from-json-dropdown.png
diff --git a/static/assets/lab/lab-xdr-from-json-filled.png b/assets/lab/lab-xdr-from-json-filled.png
similarity index 100%
rename from static/assets/lab/lab-xdr-from-json-filled.png
rename to assets/lab/lab-xdr-from-json-filled.png
diff --git a/static/assets/lab/lab-xdr-from-json.png b/assets/lab/lab-xdr-from-json.png
similarity index 100%
rename from static/assets/lab/lab-xdr-from-json.png
rename to assets/lab/lab-xdr-from-json.png
diff --git a/static/assets/lab/lab-xdr-to-json-dropdown.png b/assets/lab/lab-xdr-to-json-dropdown.png
similarity index 100%
rename from static/assets/lab/lab-xdr-to-json-dropdown.png
rename to assets/lab/lab-xdr-to-json-dropdown.png
diff --git a/static/assets/lab/lab-xdr-to-json-filled.png b/assets/lab/lab-xdr-to-json-filled.png
similarity index 100%
rename from static/assets/lab/lab-xdr-to-json-filled.png
rename to assets/lab/lab-xdr-to-json-filled.png
diff --git a/static/assets/lab/lab-xdr-to-json.png b/assets/lab/lab-xdr-to-json.png
similarity index 100%
rename from static/assets/lab/lab-xdr-to-json.png
rename to assets/lab/lab-xdr-to-json.png
diff --git a/static/assets/lab/restore-footprint.gif b/assets/lab/restore-footprint.gif
similarity index 100%
rename from static/assets/lab/restore-footprint.gif
rename to assets/lab/restore-footprint.gif
diff --git a/static/assets/lab/rpc-methods-item.png b/assets/lab/rpc-methods-item.png
similarity index 100%
rename from static/assets/lab/rpc-methods-item.png
rename to assets/lab/rpc-methods-item.png
diff --git a/static/assets/lab/smart-contract-list-01232026.png b/assets/lab/smart-contract-list-01232026.png
similarity index 100%
rename from static/assets/lab/smart-contract-list-01232026.png
rename to assets/lab/smart-contract-list-01232026.png
diff --git a/static/assets/lab/stellar-lab-restore.png b/assets/lab/stellar-lab-restore.png
similarity index 100%
rename from static/assets/lab/stellar-lab-restore.png
rename to assets/lab/stellar-lab-restore.png
diff --git a/static/assets/lab/tx-dashboard-classic.png b/assets/lab/tx-dashboard-classic.png
similarity index 100%
rename from static/assets/lab/tx-dashboard-classic.png
rename to assets/lab/tx-dashboard-classic.png
diff --git a/static/assets/lab/tx-dashboard-ops.png b/assets/lab/tx-dashboard-ops.png
similarity index 100%
rename from static/assets/lab/tx-dashboard-ops.png
rename to assets/lab/tx-dashboard-ops.png
diff --git a/static/assets/quickstart/stellar_lab_screenshot.png b/assets/quickstart/stellar_lab_screenshot.png
similarity index 100%
rename from static/assets/quickstart/stellar_lab_screenshot.png
rename to assets/quickstart/stellar_lab_screenshot.png
diff --git a/static/assets/security/threat-modeling.png b/assets/security/threat-modeling.png
similarity index 100%
rename from static/assets/security/threat-modeling.png
rename to assets/security/threat-modeling.png
diff --git a/config/anchorPlatform.sidebar.ts b/config/anchorPlatform.sidebar.ts
deleted file mode 100644
index 36b7329bf..000000000
--- a/config/anchorPlatform.sidebar.ts
+++ /dev/null
@@ -1,22 +0,0 @@
-import type { SidebarsConfig } from '@docusaurus/plugin-content-docs';
-
-const sidebars: SidebarsConfig = {
-    anchor_platform: [
-        {
-            type: 'category',
-            label: 'Anchor Platform',
-            link: {
-                type: 'doc',
-                id: 'platforms/anchor-platform/README',
-            },
-            items: [
-                {
-                    type: 'autogenerated',
-                    dirName: 'platforms/anchor-platform',
-                }
-            ],
-        },
-    ],
-}
-
-export default sidebars;
diff --git a/config/constants.ts b/config/constants.ts
deleted file mode 100644
index 36488fdf6..000000000
--- a/config/constants.ts
+++ /dev/null
@@ -1,33 +0,0 @@
-export const CODE_LANGS = {
-  bash: 'bash',
-  cpp: 'C++',
-  css: 'CSS',
-  curl: 'cURL',
-  dart: 'Flutter',
-  flutter: 'Flutter',
-  swift: 'Swift',
-  docker: 'Dockerfile',
-  go: 'Go',
-  html: 'HTML',
-  kotlin: 'Kotlin',
-  kt: 'Kotlin',
-  java: 'Java',
-  javascript: 'JavaScript',
-  js: 'JavaScript',
-  jsx: 'JSX',
-  json: 'JSON',
-  json5: 'JSON5',
-  python: 'Python',
-  scss: 'SCSS',
-  sql: 'SQL',
-  rust: 'Rust',
-  php: 'PHP',
-  toml: 'TOML',
-  ts: 'TypeScript',
-  tsx: 'TSX',
-  typescript: 'TypeScript',
-  yaml: 'YAML',
-};
-
-const GOOGLE_TRANSLATE_LANGUAGES: string = "af,sq,am,en,fa,ar,ps,ja,zh-CN,hy,az,eu,be,bn,bs,bg,ca,ceb,ny,zh-TW,co,hr,cs,da,nl,eo,et,tl,fi,fr,fy,gl,ka,de,el,gu,ht,ha,haw,iw,hi,hmn,hu,is,ig,id,ga,it,jw,kn,kk,km,rw,ko,ku,ky,lo,la,lv,lt,lb,mk,mg,ms,ml,mt,mi,mr,mn,my,ne,no,pl,pt,pa,ro,ru,sm,gd,sr,st,sn,sd,si,sk,sl,so,es,su,sw,sv,tg,ta,te,th,tr,uk,ur,uz,vi,cy,xh,yi,yo,zu";
-export const GOOGLE_TRANSLATE_ELEMENT: string = `<a href="#" class="my-google-translate-button" onclick="new google.translate.TranslateElement({pageLanguage: 'en', includedLanguages: '${GOOGLE_TRANSLATE_LANGUAGES}'}, 'google_translate_element'); return false;"></a>`;
diff --git a/config/disbursementPlatform.sidebar.ts b/config/disbursementPlatform.sidebar.ts
deleted file mode 100644
index b8f256a0e..000000000
--- a/config/disbursementPlatform.sidebar.ts
+++ /dev/null
@@ -1,45 +0,0 @@
-import type { SidebarsConfig } from "@docusaurus/plugin-content-docs";
-
-import sdpSidebar from "../docs/platforms/stellar-disbursement-platform/api-reference/sidebar";
-
-const sidebars: SidebarsConfig = {
-  stellar_disbursement_platform: [
-    {
-      type: "category",
-      label: "Stellar Disbursement Platform",
-      link: {
-        type: "doc",
-        id: "platforms/stellar-disbursement-platform/README",
-      },
-      items: [
-        "platforms/stellar-disbursement-platform/README",
-        {
-          type: "category",
-          label: "Admin Guide",
-          collapsed: false,
-          link: {
-            description:
-              "All you need to know about setting up, running, and using the Stellar Disbursement Platform.",
-            type: "generated-index",
-            slug: "platforms/stellar-disbursement-platform/admin-guide",
-          },
-          items: [{ type: "autogenerated", dirName: "platforms/stellar-disbursement-platform/admin-guide" }],
-        },
-        {
-          type: "category",
-          label: "API Reference",
-          collapsed: true,
-          link: {
-            description:
-              "View all Stellar Disbursement Platform API information.",
-            type: "generated-index",
-            slug: "platforms/stellar-disbursement-platform/api-reference",
-          },
-          items: [...sdpSidebar.filter((item) => item.type === "category")],
-        },
-      ],
-    },
-  ],
-};
-
-export default sidebars;
diff --git a/config/sidebars.ts b/config/sidebars.ts
deleted file mode 100644
index 39948aa72..000000000
--- a/config/sidebars.ts
+++ /dev/null
@@ -1,55 +0,0 @@
-import { SidebarsConfig } from "@docusaurus/plugin-content-docs";
-import ap_sidebars from "./anchorPlatform.sidebar";
-import sdp_sidebars from "./disbursementPlatform.sidebar"
-
-const sidebars: SidebarsConfig = {
-  build: [
-    {
-      type: 'autogenerated',
-      dirName: 'build',
-    },
-  ],
-  learn: [
-    {
-      type: 'autogenerated',
-      dirName: 'learn',
-    },
-  ],
-  tokens: [
-    {
-      type: 'autogenerated',
-      dirName: 'tokens',
-    },
-  ],
-  data: [
-    {
-      type: 'autogenerated',
-      dirName: 'data',
-    },
-  ],
-  tools: [
-    {
-      type: 'autogenerated',
-      dirName: 'tools',
-    },
-    { type: 'html', value: '<small>SDF Platforms</small>', defaultStyle: true, className: 'networkMenuHtmlItem'},
-    { type: 'link', href: '/docs/platforms/anchor-platform', label: 'Anchor Platform'},
-    { type: 'link', href: '/docs/platforms/stellar-disbursement-platform', label: 'Stellar Disbursement Platform'},
-  ],
-  networks: [
-    {
-      type: 'autogenerated',
-      dirName: 'networks',
-    },
-  ],
-  validators: [
-    {
-      type: 'autogenerated',
-      dirName: 'validators',
-    },
-  ],
-  anchor_platform: ap_sidebars.anchor_platform,
-  stellar_disbursement_platform: sdp_sidebars.stellar_disbursement_platform,
-};
-
-export default sidebars;
diff --git a/config/theme/footer.ts b/config/theme/footer.ts
deleted file mode 100644
index a56d6cb38..000000000
--- a/config/theme/footer.ts
+++ /dev/null
@@ -1,115 +0,0 @@
-import type { FooterLinkItem } from "@docusaurus/theme-common";
-
-const resources = {
-  title: "Resources",
-  items: [
-    {
-      label: "Developer Blog",
-      href: "https://stellar.org/developers-blog",
-    },
-    {
-      label: "Stellar Quest",
-      href: "https://quest.stellar.org/",
-    },
-    {
-      label: "Soroban Quest",
-      href: "https://fastcheapandoutofcontrol.com/tutorial",
-    },
-    {
-      label: "YouTube",
-      href: "https://www.youtube.com/@StellarDevelopmentFoundation",
-    },
-    {
-      label: "Twitch",
-      href: "https://m.twitch.tv/stellarorg/home",
-    },
-    {
-      html: '<a class="footer__link-item" href="/llms.txt">llms.txt</a>'
-    },
-  ] satisfies FooterLinkItem[],
-};
-
-const tools = {
-  title: "Tools",
-  items: [
-    {
-      label: "Explorer",
-      href: "https://stellar.expert",
-    },
-    {
-      label: "Lab",
-      href: "https://lab.stellar.org",
-    },
-    {
-      label: "Status",
-      href: "https://status.stellar.org/",
-    },
-    {
-      label: "Dashboard",
-      href: "https://dashboard.stellar.org/",
-    },
-    {
-      label: "All Tools",
-      to: "/docs/tools",
-    },
-  ] satisfies FooterLinkItem[],
-};
-
-const community = {
-  title: "Community",
-  items: [
-    {
-      label: "Contribute to Docs",
-      href: "https://github.com/stellar/stellar-docs?tab=readme-ov-file#contributing",
-    },
-    {
-      label: "Developer Discord",
-      href: "https://discord.gg/stellardev",
-    },
-    {
-      label: "Developer Meetings",
-      to: "/meetings",
-    },
-    {
-      label: "Developer Google Group",
-      href: "https://groups.google.com/g/stellar-dev",
-    },
-    {
-      label: "Stack Exchange",
-      href: "https://stellar.stackexchange.com/",
-    },
-    {
-      label: "Stellar Community Fund",
-      href: "https://communityfund.stellar.org/",
-    },
-  ] satisfies FooterLinkItem[],
-};
-
-const about = {
-  title: "About",
-  items: [
-    {
-      label: "About SDF",
-      href: "https://stellar.org/foundation",
-    },
-    {
-      label: "Careers",
-      href: "https://stellar.org/foundation/careers",
-    },
-    {
-      label: "Events",
-      href: "https://stellar.org/events",
-    },
-    {
-      label: "Grants & Funding",
-      href: "https://stellar.org/foundation/grants-and-funding",
-    },
-  ] satisfies FooterLinkItem[],
-};
-
-export default {
-  resources,
-  tools,
-  community,
-  about,
-};
diff --git a/config/theme/headTags.ts b/config/theme/headTags.ts
deleted file mode 100644
index eb539dfd5..000000000
--- a/config/theme/headTags.ts
+++ /dev/null
@@ -1,26 +0,0 @@
-import type { HtmlTagObject } from '@docusaurus/types/src/plugin';
-
-export const headTags: HtmlTagObject[] = [
-  {
-    tagName: 'link',
-    attributes: {
-      rel: 'preconnect',
-      href: 'https://dev.visualwebsiteoptimizer.com',
-    },
-  },
-  {
-    tagName: 'script',
-    attributes: {
-      id: 'vwoCode',
-    },
-    innerHTML: `
-      window._vwo_code || (function() {
-      var account_id=814004,
-      version=2.1,
-      settings_tolerance=2000,
-      hide_element='body',
-      hide_element_style='opacity:0 !important;filter:alpha(opacity=0) !important;background:none !important;transition:none !important;',
-      f=false,w=window,d=document,v=d.querySelector('#vwoCode'),cK='_vwo_'+account_id+'_settings',cc={};try{var c=JSON.parse(localStorage.getItem('_vwo_'+account_id+'_config'));cc=c&&typeof c==='object'?c:{}}catch(e){}var stT=cc.stT==='session'?w.sessionStorage:w.localStorage;code={nonce:v&&v.nonce,use_existing_jquery:function(){return typeof use_existing_jquery!=='undefined'?use_existing_jquery:undefined},library_tolerance:function(){return typeof library_tolerance!=='undefined'?library_tolerance:undefined},settings_tolerance:function(){return cc.sT||settings_tolerance},hide_element_style:function(){return'{'+(cc.hES||hide_element_style)+'}'},hide_element:function(){if(performance.getEntriesByName('first-contentful-paint')[0]){return''}return typeof cc.hE==='string'?cc.hE:hide_element},getVersion:function(){return version},finish:function(e){if(!f){f=true;var t=d.getElementById('_vis_opt_path_hides');if(t)t.parentNode.removeChild(t);if(e)(new Image).src='https://dev.visualwebsiteoptimizer.com/ee.gif?a='+account_id+e}},finished:function(){return f},addScript:function(e){var t=d.createElement('script');t.type='text/javascript';if(e.src){t.src=e.src}else{t.text=e.text}v&&t.setAttribute('nonce',v.nonce);d.getElementsByTagName('head')[0].appendChild(t)},load:function(e,t){var n=this.getSettings(),i=d.createElement('script'),r=this;t=t||{};if(n){i.textContent=n;d.getElementsByTagName('head')[0].appendChild(i);if(!w.VWO||VWO.caE){stT.removeItem(cK);r.load(e)}}else{var o=new XMLHttpRequest;o.open('GET',e,true);o.withCredentials=!t.dSC;o.responseType=t.responseType||'text';o.onload=function(){if(t.onloadCb){return t.onloadCb(o,e)}if(o.status===200||o.status===304){_vwo_code.addScript({text:o.responseText})}else{_vwo_code.finish('&e=loading_failure:'+e)}};o.onerror=function(){if(t.onerrorCb){return t.onerrorCb(e)}_vwo_code.finish('&e=loading_failure:'+e)};o.send()}},getSettings:function(){try{var e=stT.getItem(cK);if(!e){return}e=JSON.parse(e);if(Date.now()>e.e){stT.removeItem(cK);return}return e.s}catch(e){return}},init:function(){if(d.URL.indexOf('__vwo_disable__')>-1)return;var e=this.settings_tolerance();w._vwo_settings_timer=setTimeout(function(){_vwo_code.finish();stT.removeItem(cK)},e);var t;if(this.hide_element()!=='body'){t=d.createElement('style');var n=this.hide_element(),i=n?n+this.hide_element_style():'',r=d.getElementsByTagName('head')[0];t.setAttribute('id','_vis_opt_path_hides');v&&t.setAttribute('nonce',v.nonce);t.setAttribute('type','text/css');if(t.styleSheet)t.styleSheet.cssText=i;else t.appendChild(d.createTextNode(i));r.appendChild(t)}else{t=d.getElementsByTagName('head')[0];var i=d.createElement('div');i.style.cssText='z-index: 2147483647 !important;position: fixed !important;left: 0 !important;top: 0 !important;width: 100% !important;height: 100% !important;background: white !important;display: block !important;';i.setAttribute('id','_vis_opt_path_hides');i.classList.add('_vis_hide_layer');t.parentNode.insertBefore(i,t.nextSibling)}var o=window._vis_opt_url||d.URL,s='https://dev.visualwebsiteoptimizer.com/j.php?a='+account_id+'&u='+encodeURIComponent(o)+'&vn='+version;if(w.location.search.indexOf('_vwo_xhr')!==-1){this.addScript({src:s})}else{this.load(s+'&x=true')}}};w._vwo_code=code;code.init();})();
-    `,
-  },
-]
diff --git a/config/theme/navbar.ts b/config/theme/navbar.ts
deleted file mode 100644
index 616b889df..000000000
--- a/config/theme/navbar.ts
+++ /dev/null
@@ -1,588 +0,0 @@
-import type { NavbarItem } from '@docusaurus/theme-common';
-import { GOOGLE_TRANSLATE_ELEMENT } from '../constants';
-
-const build: NavbarItem = {
-  type: 'dropdown',
-  label: 'Build',
-  position: 'left',
-  to: '/docs/build',
-  items: [
-    {
-      to: '/docs/build',
-      label: 'Overview',
-      activeBasePath: 'docs/build',
-    },
-    {
-      to: '/docs/build/building-with-ai',
-      label: 'Building with AI',
-      activeBasePath: 'docs/build/building-with-ai',
-    },
-    {
-      type: 'html',
-      value: '<hr><a href="/docs/build/smart-contracts" class="subtitle"><small>Build Smart Contracts</small></a>',
-      className: 'subtitle',
-    },
-    {
-      to: '/docs/build/smart-contracts/overview',
-      label: 'Introduction',
-      activeBasePath: 'docs/build/smart-contracts/overview',
-    },
-    {
-      to: '/docs/build/smart-contracts/getting-started',
-      label: 'Getting Started',
-      activeBasePath: 'docs/build/smart-contracts/getting-started',
-      className: 'has-nested-items',
-    },
-    {
-      to: '/docs/build/smart-contracts/example-contracts',
-      label: 'Example Contracts',
-      activeBasePath: 'docs/build/smart-contracts/example-contracts',
-      className: 'has-nested-items',
-    },
-    {
-      type: 'html',
-      value: '<hr><a href="/docs/build/apps" class="subtitle"><small>Build Applications</small></a>',
-      className: 'subtitle',
-    },
-    {
-      to: '/docs/build/apps/overview',
-      label: 'Introduction',
-      activeBasePath: 'docs/build/apps/overview',
-    },
-    {
-      to: '/docs/build/apps/application-design-considerations',
-      label: 'Application Design Considerations',
-      activeBasePath: 'docs/build/apps/application-design-considerations',
-    },
-    {
-      to: '/docs/build/apps/wallet/overview',
-      label: 'Tutorial: Wallet SDK',
-      activeBasePath: 'docs/build/apps/wallet/overview',
-    },
-    {
-      to: '/docs/build/apps/example-application-tutorial/overview',
-      label: 'Tutorial: Payment Application, JavaScript',
-      activeBasePath: 'docs/build/apps/example-application-tutorial/overview',
-    },
-    {
-      to: '/docs/build/apps/swift-payment-app',
-      label: 'Tutorial: Payment Application, Swift',
-      activeBasePath: 'docs/build/apps/swift-payment-app',
-    },
-    {
-      to: '/docs/build/apps/ingest-sdk/overview',
-      label: 'Tutorial: Network Ingestion Pipeline',
-      activeBasePath: 'docs/build/apps/ingest-sdk/overview',
-    },
-    {
-      to: '/docs/build/apps/guestbook/overview',
-      label: 'Tutorial: Passkey Dapp',
-      activeBasePath: 'docs/build/apps/guestbook/overview',
-    },
-    {
-      to: '/docs/build/apps/dapp-frontend',
-      label: 'Tutorial: Dapp Frontend',
-      activeBasePath: 'docs/build/apps/dapp-frontend',
-    },
-    {
-      to: '/docs/build/apps/privacy',
-      label: 'Privacy on Stellar',
-      activeBasePath: 'docs/build/apps/privacy',
-    },
-    {
-      to: '/docs/build/apps/zk',
-      label: 'ZK Proofs on Stellar',
-      activeBasePath: 'docs/build/apps/zk',
-    },
-    {
-      type: 'html',
-      value: '<hr><a href="/docs/build/agentic-payments" class="subtitle"><small>Agentic Payments</small></a>',
-      className: 'subtitle',
-    },
-    {
-      to: '/docs/build/agentic-payments/x402',
-      label: 'x402 on Stellar',
-      activeBasePath: 'docs/build/agentic-payments/x402',
-    },
-    {
-      to: '/docs/build/agentic-payments/mpp',
-      label: 'MPP on Stellar',
-      activeBasePath: 'docs/build/agentic-payments/mpp',
-    },
-    {
-      type: 'html',
-      value: '<hr><a href="/docs/build/guides" class="subtitle"><small>How-To Guides</small></a>',
-      className: 'subtitle',
-    },
-    {
-      to: '/docs/build/guides/auth',
-      label: 'Contract Authorization',
-      activeBasePath: 'docs/build/guides/auth',
-    },
-    {
-      to: '/docs/build/guides/contract-accounts',
-      label: 'Contract Accounts',
-      activeBasePath: 'docs/build/guides/contract-accounts',
-    },
-    {
-      to: '/docs/build/guides/conventions',
-      label: 'Contract Conventions',
-      activeBasePath: 'docs/build/guides/conventions',
-    },
-    {
-      to: '/docs/build/guides/events',
-      label: 'Contract Events',
-      activeBasePath: 'docs/build/guides/events',
-    },
-    {
-      to: '/docs/build/guides/storage',
-      label: 'Contract Storage',
-      activeBasePath: 'docs/build/guides/storage',
-    },
-    {
-      to: '/docs/build/guides/testing',
-      label: 'Contract Testing',
-      activeBasePath: 'docs/build/guides/testing',
-    },
-    {
-      to: '/docs/build/guides/dapps',
-      label: 'Dapp Development',
-      activeBasePath: 'docs/build/guides/dapps',
-    },
-    {
-      to: '/docs/build/guides/fees',
-      label: 'Fees & Metering',
-      activeBasePath: 'docs/build/guides/fees',
-    },
-    {
-      to: '/docs/build/guides/freighter',
-      label: 'Freighter Wallet',
-      activeBasePath: 'docs/build/guides/freighter',
-    },
-    {
-      to: '/docs/build/guides/basics',
-      label: 'Stellar Basics',
-      activeBasePath: 'docs/build/guides/basics',
-    },
-    {
-      to: '/docs/build/guides/rpc',
-      label: 'RPC',
-      activeBasePath: 'docs/build/guides/rpc',
-    },
-    {
-      to: '/docs/build/guides/archival',
-      label: 'State Archival',
-      activeBasePath: 'docs/build/guides/archival',
-    },
-    {
-      to: '/docs/build/guides/tokens',
-      label: 'Stellar Asset Contract Tokens',
-      activeBasePath: 'docs/build/guides/tokens',
-    },
-    {
-      to: '/docs/build/guides/transactions',
-      label: 'Transactions',
-      activeBasePath: 'docs/build/guides/transactions',
-    },
-    {
-      to: '/docs/build/guides/conversions',
-      label: 'Type Conversions',
-      activeBasePath: 'docs/build/guides/conversions',
-    },
-    {
-      type: 'html',
-      value: '<hr><a href="/docs/build/security-docs" class="dropdown__link has-nested-items">Security Best Practices</a>',
-    },
-  ],
-}
-
-const learn: NavbarItem = {
-  type: 'dropdown',
-  label: 'Learn',
-  position: 'left',
-  to: '/docs/learn/fundamentals',
-  items: [
-    {
-      type: 'html',
-      value: '<hr><a href="/docs/learn/fundamentals" class="subtitle"><small>Core Concepts</small></a>',
-      className: 'subtitle',
-    },
-    {
-      to: '/docs/learn/fundamentals/stellar-stack',
-      label: 'Stellar Stack',
-      activeBasePath: 'docs/learn/fundamentals/stellar-stack',
-    },
-    {
-      to: '/docs/learn/fundamentals/lumens',
-      label: 'Lumens (XLM)',
-      activeBasePath: 'docs/learn/fundamentals/lumens',
-    },
-    {
-      to: '/docs/learn/fundamentals/stellar-consensus-protocol',
-      label: 'Stellar Consensus Protocol (SCP)',
-      activeBasePath: 'docs/learn/fundamentals/stellar-consensus-protocol',
-    },
-    {
-      to: '/docs/learn/fundamentals/stellar-data-structures',
-      label: 'Data Structures',
-      activeBasePath: 'docs/learn/fundamentals/stellar-data-structures',
-      className: 'has-nested-items',
-    },
-    {
-      to: '/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools',
-      label: 'Stellar Decentralized Exchange (SDEX)',
-      activeBasePath: 'docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools',
-    },
-    {
-      to: '/docs/learn/fundamentals/transactions',
-      label: 'Operations & Transactions',
-      activeBasePath: 'docs/learn/fundamentals/transactions',
-      className: 'has-nested-items',
-    },
-    {
-      to: '/docs/learn/fundamentals/fees-resource-limits-metering',
-      label: 'Fees & Metering',
-      activeBasePath: 'docs/learn/fundamentals/fees-resource-limits-metering',
-    },
-    {
-      to: '/docs/learn/fundamentals/stellar-ecosystem-proposals',
-      label: 'Stellar Ecosystem Proposals (SEPs)',
-      activeBasePath: 'docs/learn/fundamentals/stellar-ecosystem-proposals',
-    },
-    {
-      to: '/docs/learn/fundamentals/contract-development',
-      label: 'Smart Contracts',
-      activeBasePath: 'docs/learn/fundamentals/contract-development',
-      className: 'has-nested-items',
-    },
-    {
-      to: '/docs/learn/fundamentals/data-format',
-      label: 'Data Format',
-      activeBasePath: 'docs/learn/fundamentals/data-format',
-      className: 'has-nested-items',
-    },
-    {
-      to: '/docs/learn/fundamentals/anchors',
-      label: 'Ramps (anchors)',
-      activeBasePath: 'docs/learn/fundamentals/anchors',
-    },
-    {
-      type: 'html',
-      value: '<hr><a href="/docs/learn/glossary" class="dropdown__link">Glossary</a>',
-    },
-    {
-      to: 'docs/learn/migrate',
-      label: 'Migrate from Another Chain',
-    },
-    {
-      to: 'docs/learn/interactive',
-      label: 'Interactive Learning',
-    },
-  ],
-}
-
-const tokens: NavbarItem = {
-  type: 'dropdown',
-  label: 'Tokens',
-  position: 'left',
-  to: '/docs/tokens',
-  exact: true,
-  items: [
-    {
-      to: '/docs/tokens',
-      label: 'Stellar Assets & Contract Tokens',
-      exact: true,
-    },
-    {
-      to: 'docs/tokens/anatomy-of-an-asset',
-      label: 'Assets Overview',
-    },
-    {
-      to: '/docs/tokens/quickstart',
-      label: 'Quickstart Guide',
-    },
-    {
-      to: '/docs/tokens/control-asset-access',
-      label: 'Asset Design Considerations',
-    },
-    {
-      to: '/docs/tokens/stellar-asset-contract',
-      label: 'Stellar Asset Contract',
-    },
-    {
-      to: '/docs/tokens/token-interface',
-      label: 'Token Interface',
-    },
-    {
-      to: '/docs/tokens/how-to-issue-an-asset',
-      label: 'Tutorial: Issue an Asset',
-    },
-    {
-      to: '/docs/tokens/publishing-asset-info',
-      label: 'Publish Asset Information',
-    },
-    {
-      to: '/docs/tokens/cross-chain-transfers',
-      label: 'CCTP',
-    },
-    {
-      to: '/docs/tokens/usdt0-layerzero',
-      label: 'USDT0',
-    },
-  ],
-}
-
-const data: NavbarItem = {
-  type: "dropdown",
-  label: "Data",
-  position: "left",
-  to: '/docs/data',
-  items: [
-    {
-      type: 'doc',
-      docId: "data/README",
-      label: "Overview",
-    },
-    {
-      type: 'html',
-      value: '<hr><a href="/docs/data/analytics" class="subtitle"><small>Analytics</small></a>',
-      className:'subtitle'
-    },
-    {
-      to: '/docs/data/analytics/hubble',
-      label: 'Hubble',
-      activeBasePath: 'docs/data/analytics/hubble'
-    },
-    {
-      to: '/docs/data/analytics/public-dashboards',
-      label: 'Dashboards',
-      activeBasePath: 'docs/data/analytics/public-dashboards'
-    },
-    {
-      to: '/docs/data/analytics/analytics-providers',
-      label: 'Providers',
-      activeBasePath: 'docs/data/analytics/analytics-providers'
-    },
-    {
-      type: 'html',
-      value: '<hr><a href="/docs/data/apis" class="subtitle"><small>API</small></a>',
-      className:'subtitle'
-    },
-    {
-      to: '/docs/data/apis/rpc',
-      label: 'RPC',
-      activeBasePath: 'docs/data/apis/rpc'
-    },
-    {
-      to: '/docs/data/apis/rpc/providers',
-      label: 'RPC Providers',
-      activeBasePath: 'docs/data/apis/rpc/providers'
-    },
-    {
-      to: '/docs/data/apis/horizon',
-      label: 'Horizon',
-      activeBasePath: 'docs/data/apis/horizon'
-    },
-    {
-      to: '/docs/data/apis/horizon/providers',
-      label: 'Horizon Providers',
-      activeBasePath: 'docs/data/apis/horizon/providers'
-    },
-    {
-      to: '/docs/data/apis/migrate-from-horizon-to-rpc',
-      label: 'Migrate Horizon to RPC',
-      activeBasePath: 'docs/data/apis/migrate-from-horizon-to-rpc'
-    },
-    {
-      type: 'html',
-      value: '<hr><a href="/docs/data/indexers" class="subtitle"><small>Indexers</small></a>',
-      className:'subtitle'
-    },
-    {
-      to: '/docs/data/indexers/build-your-own',
-      label: 'Build Your Own',
-      activeBasePath: 'docs/data/indexers/build-your-own'
-    },
-    {
-      type: 'html',
-      value: '<hr><a href="/docs/data/oracles" class="subtitle"><small>Oracles</small></a>',
-      className:'subtitle'
-    },
-    {
-      to: '/docs/data/oracles',
-      label: 'Providers',
-      activeBasePath: 'docs/data/oracles'
-    },
-  ]
-}
-
-const tools: NavbarItem = {
-  type: 'dropdown',
-  label: 'Tools',
-  position: 'left',
-  to: '/docs/tools',
-  activeBaseRegex: `(docs/tools|platforms)`,
-  items: [
-    {
-      type: 'html',
-      value: '<hr><small>Developer Tools</small>',
-      className: 'subtitle',
-    },
-    {
-      to: '/docs/tools/sdks',
-      label: 'SDKs',
-      activeBasePath: 'docs/tools/sdks'
-    },
-    {
-      to: '/docs/tools/cli',
-      label: 'Stellar CLI',
-      activeBasePath: 'docs/tools/cli'
-    },
-    {
-      to: '/docs/tools/cli/agent-cli',
-      label: 'Stellar CLI for Agents',
-      activeBasePath: 'docs/tools/cli/agent-cli'
-    },
-    {
-      to: '/docs/tools/lab',
-      label: 'Lab',
-      activeBasePath: 'docs/tools/lab'
-    },
-    {
-      to: '/docs/tools/quickstart',
-      label: 'Quickstart',
-      activeBasePath: 'docs/tools/quickstart'
-    },
-    {
-      to: '/docs/tools/openzeppelin-relayer',
-      label: 'OpenZeppelin Relayer',
-      activeBasePath: 'docs/tools/openzeppelin-relayer'
-    },
-    {
-      to: '/docs/tools/openzeppelin-contracts',
-      label: 'OpenZeppelin Contracts',
-      activeBasePath: 'docs/tools/openzeppelin-contracts'
-    },
-    {
-      to: '/docs/tools/scaffold-stellar',
-      label: 'Scaffold Stellar',
-      activeBasePath: 'docs/tools/scaffold-stellar'
-    },
-    {
-      to: '/docs/tools/developer-tools',
-      label: 'More Developer Tools',
-      className: 'has-nested-items',
-    },
-    {
-      type: 'html',
-      value: '<hr><small>Ramps</small>',
-      className: 'subtitle',
-    },
-    {
-      to: '/docs/tools/ramps/moneygram',
-      label: 'MoneyGram Ramps',
-      activeBasePath: '/docs/tools/ramps/moneygram'
-    },
-    {
-      type: 'html',
-      value: '<hr><small>Infra Tools</small>',
-      className: 'subtitle',
-    },
-    {
-      to: '/docs/tools/infra-tools/cross-chain',
-      label: 'Cross-Chain',
-      activeBasePath: 'docs/tools/infra-tools/cross-chain'
-    },
-    {
-      type: 'html',
-      value: '<hr><small>SDF Platforms</small>',
-      className: 'subtitle',
-    },
-    {
-      type: 'docSidebar',
-      // docId: "docs/platforms/anchor-platform/README",
-      sidebarId: 'anchor_platform',
-      label: "Anchor Platform",
-    },
-    {
-      type: 'docSidebar',
-      // docId: "docs/platforms/stellar-disbursement-platform/README",
-      sidebarId: 'stellar_disbursement_platform',
-      label: "Stellar Disbursement Platform",
-    },
-  ]
-}
-
-const networks: NavbarItem = {
-  type: 'dropdown',
-  label: 'Networks',
-  position: 'left',
-  to: '/docs/networks',
-  exact: true,
-  items: [
-    {
-      to: '/docs/networks',
-      label: 'Networks Overview',
-      exact: true,
-    },
-    {
-      to: '/docs/networks/software-versions',
-      label: 'Software Versions',
-    },
-    {
-      to: '/docs/networks/resource-limits-fees',
-      label: 'Resource Limits & Fees',
-    },
-    {
-      to: '/docs/networks/audits',
-      label: 'Audits',
-    }
-  ]
-}
-
-const validators: NavbarItem = {
-  type: 'dropdown',
-  label: 'Validators',
-  position: 'left',
-  to: '/docs/validators',
-  exact: true,
-  items: [
-    {
-      to: 'docs/validators',
-      label: 'Validators Introduction',
-      exact: true,
-    },
-    {
-      to: 'docs/validators/admin-guide',
-      label: 'Admin Guide',
-    },
-    {
-      to: 'docs/validators/tier-1-orgs',
-      label: 'Tier 1 Organizations',
-    }
-  ]
-}
-
-const translation: NavbarItem[] = [
-  {
-    type: 'html',
-    position: 'right',
-    value: '<div id="google_translate_element"></div>',
-  },
-  {
-    type: 'html',
-    position: 'right',
-    value: GOOGLE_TRANSLATE_ELEMENT,
-  },
-]
-
-export default {
-  build,
-  learn,
-  tokens,
-  data,
-  tools,
-  networks,
-  validators,
-  translation,
-}
diff --git a/docs.json b/docs.json
new file mode 100644
index 000000000..7d11d858f
--- /dev/null
+++ b/docs.json
@@ -0,0 +1,1982 @@
+{
+  "$schema": "https://mintlify.com/docs.json",
+  "theme": "sequoia",
+  "name": "Stellar Developer Docs",
+  "colors": {
+    "primary": "#6E56CF",
+    "light": "#9E8CFC",
+    "dark": "#5746AF"
+  },
+  "fonts": {
+    "family": "Inter"
+  },
+  "background": {
+    "color": {
+      "light": "#fcfcfc",
+      "dark": "#161616"
+    }
+  },
+  "styling": {
+    "codeblocks": {
+      "theme": {
+        "light": "github-light",
+        "dark": "github-dark"
+      }
+    }
+  },
+  "favicon": "/favicon.png",
+  "appearance": {
+    "default": "light"
+  },
+  "seo": {
+    "metatags": {
+      "canonical": "https://developers.stellar.org"
+    }
+  },
+  "navigation": {
+    "tabs": [
+      {
+        "tab": "Build",
+        "pages": [
+          {
+            "group": " ",
+            "pages": [
+              "docs/build/index",
+              "docs/build/building-with-ai",
+              {
+                "group": "Build Smart Contracts",
+                "root": "docs/build/smart-contracts/index",
+                "pages": [
+                  "docs/build/smart-contracts/overview",
+                  {
+                    "group": "Getting Started",
+                    "root": "docs/build/smart-contracts/getting-started/index",
+                    "expanded": true,
+                    "pages": [
+                      "docs/build/smart-contracts/getting-started/setup",
+                      "docs/build/smart-contracts/getting-started/hello-world",
+                      "docs/build/smart-contracts/getting-started/deploy-to-testnet",
+                      "docs/build/smart-contracts/getting-started/storing-data",
+                      "docs/build/smart-contracts/getting-started/deploy-increment-contract",
+                      "docs/build/smart-contracts/getting-started/hello-world-frontend"
+                    ]
+                  },
+                  {
+                    "group": "Example Contracts",
+                    "root": "docs/build/smart-contracts/example-contracts/index",
+                    "pages": [
+                      "docs/build/smart-contracts/example-contracts/storage",
+                      "docs/build/smart-contracts/example-contracts/events",
+                      "docs/build/smart-contracts/example-contracts/simple-account",
+                      "docs/build/smart-contracts/example-contracts/complex-account",
+                      "docs/build/smart-contracts/example-contracts/bls-signature",
+                      "docs/build/smart-contracts/example-contracts/delegate-auth",
+                      "docs/build/smart-contracts/example-contracts/custom-types",
+                      "docs/build/smart-contracts/example-contracts/errors",
+                      "docs/build/smart-contracts/example-contracts/logging",
+                      "docs/build/smart-contracts/example-contracts/auth",
+                      "docs/build/smart-contracts/example-contracts/cross-contract-call",
+                      "docs/build/smart-contracts/example-contracts/deployer",
+                      "docs/build/smart-contracts/example-contracts/alloc",
+                      "docs/build/smart-contracts/example-contracts/atomic-swap",
+                      "docs/build/smart-contracts/example-contracts/atomic-multi-swap",
+                      "docs/build/smart-contracts/example-contracts/mint-lock",
+                      "docs/build/smart-contracts/example-contracts/timelock",
+                      "docs/build/smart-contracts/example-contracts/single-offer-sale",
+                      "docs/build/smart-contracts/example-contracts/upgradeable-contract",
+                      "docs/build/smart-contracts/example-contracts/liquidity-pool",
+                      "docs/build/smart-contracts/example-contracts/tokens",
+                      "docs/build/smart-contracts/example-contracts/fuzzing",
+                      "docs/build/smart-contracts/example-contracts/workspace"
+                    ]
+                  }
+                ],
+                "expanded": true
+              },
+              {
+                "group": "Build Applications",
+                "root": "docs/build/apps/index",
+                "pages": [
+                  "docs/build/apps/overview",
+                  "docs/build/apps/application-design-considerations",
+                  {
+                    "group": "Build a Wallet with the Wallet SDK",
+                    "root": "docs/build/apps/wallet/index",
+                    "pages": [
+                      "docs/build/apps/wallet/overview",
+                      "docs/build/apps/wallet/intro",
+                      "docs/build/apps/wallet/stellar",
+                      "docs/build/apps/wallet/sep10",
+                      "docs/build/apps/wallet/sep24",
+                      "docs/build/apps/wallet/sep30",
+                      "docs/build/apps/wallet/sep6",
+                      "docs/build/apps/wallet/sep38",
+                      "docs/build/apps/wallet/sep7"
+                    ]
+                  },
+                  {
+                    "group": "Build a Payment App with the JS SDK",
+                    "root": "docs/build/apps/example-application-tutorial/index",
+                    "pages": [
+                      "docs/build/apps/example-application-tutorial/overview",
+                      "docs/build/apps/example-application-tutorial/account-creation",
+                      "docs/build/apps/example-application-tutorial/confirmation-modal",
+                      "docs/build/apps/example-application-tutorial/contacts-list",
+                      "docs/build/apps/example-application-tutorial/manage-trust",
+                      "docs/build/apps/example-application-tutorial/payment",
+                      "docs/build/apps/example-application-tutorial/path-payment",
+                      {
+                        "group": "Anchor Integration",
+                        "root": "docs/build/apps/example-application-tutorial/anchor-integration/index",
+                        "pages": [
+                          "docs/build/apps/example-application-tutorial/anchor-integration/setup",
+                          "docs/build/apps/example-application-tutorial/anchor-integration/sep1",
+                          "docs/build/apps/example-application-tutorial/anchor-integration/sep10",
+                          "docs/build/apps/example-application-tutorial/anchor-integration/sep6",
+                          "docs/build/apps/example-application-tutorial/anchor-integration/sep24"
+                        ]
+                      },
+                      "docs/build/apps/example-application-tutorial/querying-data"
+                    ]
+                  },
+                  "docs/build/apps/swift-payment-app",
+                  {
+                    "group": "Build Custom Network Ingestion Pipeline",
+                    "root": "docs/build/apps/ingest-sdk/index",
+                    "pages": [
+                      "docs/build/apps/ingest-sdk/overview",
+                      "docs/build/apps/ingest-sdk/ingestion-pipeline-code"
+                    ]
+                  },
+                  {
+                    "group": "Build a Passkey Powered Guestbook Dapp",
+                    "root": "docs/build/apps/guestbook/index",
+                    "pages": [
+                      "docs/build/apps/guestbook/overview",
+                      "docs/build/apps/guestbook/smart-contract",
+                      "docs/build/apps/guestbook/bindings",
+                      "docs/build/apps/guestbook/passkeys-prerequisites",
+                      "docs/build/apps/guestbook/setup-passkeys",
+                      "docs/build/apps/guestbook/frontend"
+                    ]
+                  },
+                  "docs/build/apps/dapp-frontend",
+                  "docs/build/apps/privacy",
+                  "docs/build/apps/zk"
+                ]
+              },
+              {
+                "group": "Agentic Payments",
+                "root": "docs/build/agentic-payments/index",
+                "pages": [
+                  {
+                    "group": "x402 on Stellar",
+                    "root": "docs/build/agentic-payments/x402/index",
+                    "expanded": true,
+                    "pages": [
+                      "docs/build/agentic-payments/x402/built-on-stellar",
+                      "docs/build/agentic-payments/x402/quickstart-guide"
+                    ]
+                  },
+                  {
+                    "group": "MPP on Stellar",
+                    "root": "docs/build/agentic-payments/mpp/index",
+                    "expanded": true,
+                    "pages": [
+                      "docs/build/agentic-payments/mpp/charge-guide",
+                      "docs/build/agentic-payments/mpp/channel-guide"
+                    ]
+                  }
+                ],
+                "expanded": true
+              },
+              {
+                "group": "How-To Guides",
+                "root": "docs/build/guides/index",
+                "pages": [
+                  {
+                    "group": "Contract Authorization",
+                    "root": "docs/build/guides/auth/index",
+                    "pages": [
+                      "docs/build/guides/auth/check-auth-tutorials",
+                      "docs/build/guides/auth/contract-authorization"
+                    ]
+                  },
+                  {
+                    "group": "Contract Accounts",
+                    "root": "docs/build/guides/contract-accounts/index",
+                    "pages": [
+                      "docs/build/guides/contract-accounts/smart-wallets",
+                      "docs/build/guides/contract-accounts/advanced-patterns",
+                      "docs/build/guides/contract-accounts/examples"
+                    ]
+                  },
+                  {
+                    "group": "Contract Conventions",
+                    "root": "docs/build/guides/conventions/index",
+                    "pages": [
+                      "docs/build/guides/conventions/cross-contract",
+                      "docs/build/guides/conventions/deploy-contract",
+                      "docs/build/guides/conventions/deploy-sac-with-code",
+                      "docs/build/guides/conventions/error-enum",
+                      "docs/build/guides/conventions/extending-wasm-ttl",
+                      "docs/build/guides/conventions/upgrading-contracts",
+                      "docs/build/guides/conventions/wasm-metadata",
+                      "docs/build/guides/conventions/workspace"
+                    ]
+                  },
+                  {
+                    "group": "Contract Events",
+                    "root": "docs/build/guides/events/index",
+                    "pages": [
+                      "docs/build/guides/events/consume",
+                      "docs/build/guides/events/ingest",
+                      "docs/build/guides/events/publish",
+                      "docs/build/guides/events/replay-ledger-close-meta"
+                    ]
+                  },
+                  {
+                    "group": "Contract Storage",
+                    "root": "docs/build/guides/storage/index",
+                    "pages": [
+                      "docs/build/guides/storage/choosing-the-right-storage",
+                      "docs/build/guides/storage/migrate-contract-storage",
+                      "docs/build/guides/storage/storage-strategies",
+                      "docs/build/guides/storage/use-instance",
+                      "docs/build/guides/storage/use-persistent",
+                      "docs/build/guides/storage/use-temporary"
+                    ]
+                  },
+                  {
+                    "group": "Contract Testing",
+                    "root": "docs/build/guides/testing/index",
+                    "pages": [
+                      "docs/build/guides/testing/unit-tests",
+                      "docs/build/guides/testing/mocking",
+                      "docs/build/guides/testing/test-contract-auth",
+                      "docs/build/guides/testing/test-contract-events",
+                      "docs/build/guides/testing/integration-tests",
+                      "docs/build/guides/testing/fork-testing",
+                      "docs/build/guides/testing/fuzzing",
+                      "docs/build/guides/testing/differential-tests",
+                      "docs/build/guides/testing/differential-tests-with-test-snapshots",
+                      "docs/build/guides/testing/mutation-testing",
+                      "docs/build/guides/testing/code-coverage",
+                      "docs/build/guides/testing/ledger-snapshot-testing"
+                    ]
+                  },
+                  {
+                    "group": "Dapp Development",
+                    "root": "docs/build/guides/dapps/index",
+                    "pages": [
+                      "docs/build/guides/dapps/frontend-guide",
+                      "docs/build/guides/dapps/initialization",
+                      "docs/build/guides/dapps/soroban-contract-init-template",
+                      "docs/build/guides/dapps/state-archival",
+                      "docs/build/guides/dapps/working-with-contract-specs"
+                    ]
+                  },
+                  {
+                    "group": "Fees & Metering",
+                    "root": "docs/build/guides/fees/index",
+                    "pages": [
+                      "docs/build/guides/fees/analyzing-smart-contract-cost"
+                    ]
+                  },
+                  {
+                    "group": "Freighter Wallet",
+                    "root": "docs/build/guides/freighter/index",
+                    "pages": [
+                      "docs/build/guides/freighter/connect-testnet",
+                      "docs/build/guides/freighter/enable-soroban-tokens",
+                      "docs/build/guides/freighter/integrate-freighter-react",
+                      "docs/build/guides/freighter/prompt-to-sign-tx",
+                      "docs/build/guides/freighter/send-token-payments",
+                      "docs/build/guides/freighter/sign-auth-entries",
+                      "docs/build/guides/freighter/sign-soroban-xdrs"
+                    ]
+                  },
+                  {
+                    "group": "RPC",
+                    "root": "docs/build/guides/rpc/index",
+                    "pages": [
+                      "docs/build/guides/rpc/generate-ledger-keys-python",
+                      "docs/build/guides/rpc/retrieve-contract-code-js",
+                      "docs/build/guides/rpc/retrieve-contract-code-python"
+                    ]
+                  },
+                  {
+                    "group": "Stellar Asset Contract (SAC) Tokens",
+                    "root": "docs/build/guides/tokens/index",
+                    "pages": [
+                      "docs/build/guides/tokens/custom-sac-admin",
+                      "docs/build/guides/tokens/deploying-a-sac",
+                      "docs/build/guides/tokens/stellar-asset-contract"
+                    ]
+                  },
+                  {
+                    "group": "State Archival",
+                    "root": "docs/build/guides/archival/index",
+                    "pages": [
+                      "docs/build/guides/archival/create-restoration-footprint-js",
+                      "docs/build/guides/archival/extend-persistent-entry-js",
+                      "docs/build/guides/archival/restore-contract-js",
+                      "docs/build/guides/archival/restore-data-js",
+                      "docs/build/guides/archival/test-ttl-extension"
+                    ]
+                  },
+                  {
+                    "group": "Stellar Basics",
+                    "root": "docs/build/guides/basics/index",
+                    "pages": [
+                      "docs/build/guides/basics/verify-trustlines",
+                      "docs/build/guides/basics/classic-transition",
+                      "docs/build/guides/basics/automate-reset-data"
+                    ]
+                  },
+                  {
+                    "group": "Transactions",
+                    "root": "docs/build/guides/transactions/index",
+                    "pages": [
+                      "docs/build/guides/transactions/create-account",
+                      "docs/build/guides/transactions/send-and-receive-c-accounts",
+                      "docs/build/guides/transactions/send-and-receive-payments",
+                      "docs/build/guides/transactions/channel-accounts",
+                      "docs/build/guides/transactions/signing-soroban-invocations",
+                      "docs/build/guides/transactions/claimable-balances",
+                      "docs/build/guides/transactions/clawbacks",
+                      "docs/build/guides/transactions/fee-sponsorship",
+                      "docs/build/guides/transactions/fee-bump-transactions",
+                      "docs/build/guides/transactions/sponsored-reserves",
+                      "docs/build/guides/transactions/path-payments",
+                      "docs/build/guides/transactions/pooled-accounts-muxed-accounts-memos",
+                      "docs/build/guides/transactions/install-deploy-contract-with-code",
+                      "docs/build/guides/transactions/invoke-contract-tx-sdk",
+                      "docs/build/guides/transactions/simulateTransaction-Deep-Dive",
+                      "docs/build/guides/transactions/submit-transaction-wait-js",
+                      "docs/build/guides/transactions/upload-wasm-bytecode"
+                    ]
+                  },
+                  {
+                    "group": "Type Conversions",
+                    "root": "docs/build/guides/conversions/index",
+                    "pages": [
+                      "docs/build/guides/conversions/address-conversions",
+                      "docs/build/guides/conversions/bytes-conversions",
+                      "docs/build/guides/conversions/scval-conversions",
+                      "docs/build/guides/conversions/string-conversions"
+                    ]
+                  }
+                ]
+              },
+              {
+                "group": "Security Best Practices",
+                "root": "docs/build/security-docs/index",
+                "pages": [
+                  {
+                    "group": "Threat Modeling",
+                    "root": "docs/build/security-docs/threat-modeling/index",
+                    "pages": [
+                      "docs/build/security-docs/threat-modeling/threat-modeling-description",
+                      "docs/build/security-docs/threat-modeling/threat-modeling-how-to",
+                      "docs/build/security-docs/threat-modeling/STRIDE-template",
+                      "docs/build/security-docs/threat-modeling/pizza-restaurant-example"
+                    ]
+                  },
+                  {
+                    "group": "Onchain Monitoring",
+                    "root": "docs/build/security-docs/monitoring/index",
+                    "pages": [
+                      "docs/build/security-docs/monitoring/monitoring-template-builders",
+                      "docs/build/security-docs/monitoring/monitoring-template-users"
+                    ]
+                  },
+                  "docs/build/security-docs/securing-web-based-projects"
+                ]
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "tab": "Learn",
+        "pages": [
+          {
+            "group": " ",
+            "pages": [
+              {
+                "group": "Core Concepts",
+                "root": "docs/learn/fundamentals/index",
+                "pages": [
+                  "docs/learn/fundamentals/stellar-stack",
+                  "docs/learn/fundamentals/lumens",
+                  "docs/learn/fundamentals/stellar-consensus-protocol",
+                  {
+                    "group": "Stellar Data Structures",
+                    "root": "docs/learn/fundamentals/stellar-data-structures/index",
+                    "pages": [
+                      "docs/learn/fundamentals/stellar-data-structures/ledgers",
+                      "docs/learn/fundamentals/stellar-data-structures/events",
+                      "docs/learn/fundamentals/stellar-data-structures/accounts",
+                      "docs/learn/fundamentals/stellar-data-structures/assets",
+                      "docs/learn/fundamentals/stellar-data-structures/contracts"
+                    ]
+                  },
+                  "docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools",
+                  {
+                    "group": "Operations & Transactions",
+                    "root": "docs/learn/fundamentals/transactions/index",
+                    "pages": [
+                      "docs/learn/fundamentals/transactions/operations-and-transactions",
+                      "docs/learn/fundamentals/transactions/list-of-operations",
+                      "docs/learn/fundamentals/transactions/signatures-multisig",
+                      "docs/learn/fundamentals/transactions/transaction-lifecycle"
+                    ]
+                  },
+                  "docs/learn/fundamentals/fees-resource-limits-metering",
+                  "docs/learn/fundamentals/stellar-ecosystem-proposals",
+                  {
+                    "group": "Smart Contracts",
+                    "root": "docs/learn/fundamentals/contract-development/index",
+                    "pages": [
+                      "docs/learn/fundamentals/contract-development/overview",
+                      "docs/learn/fundamentals/contract-development/rust-dialect",
+                      "docs/learn/fundamentals/contract-development/environment-concepts",
+                      {
+                        "group": "Contract Interactions",
+                        "root": "docs/learn/fundamentals/contract-development/contract-interactions/index",
+                        "pages": [
+                          "docs/learn/fundamentals/contract-development/contract-interactions/overview",
+                          "docs/learn/fundamentals/contract-development/contract-interactions/cross-contract",
+                          "docs/learn/fundamentals/contract-development/contract-interactions/tests",
+                          "docs/learn/fundamentals/contract-development/contract-interactions/stellar-transaction",
+                          "docs/learn/fundamentals/contract-development/contract-interactions/transaction-simulation"
+                        ]
+                      },
+                      {
+                        "group": "Types",
+                        "root": "docs/learn/fundamentals/contract-development/types/index",
+                        "pages": [
+                          "docs/learn/fundamentals/contract-development/types/built-in-types",
+                          "docs/learn/fundamentals/contract-development/types/custom-types",
+                          "docs/learn/fundamentals/contract-development/types/fully-typed-contracts"
+                        ]
+                      },
+                      {
+                        "group": "Storage",
+                        "root": "docs/learn/fundamentals/contract-development/storage/index",
+                        "pages": [
+                          "docs/learn/fundamentals/contract-development/storage/persisting-data",
+                          "docs/learn/fundamentals/contract-development/storage/state-archival"
+                        ]
+                      },
+                      "docs/learn/fundamentals/contract-development/authorization",
+                      {
+                        "group": "Errors and Debugging",
+                        "root": "docs/learn/fundamentals/contract-development/errors-and-debugging/index",
+                        "pages": [
+                          "docs/learn/fundamentals/contract-development/errors-and-debugging/errors",
+                          "docs/learn/fundamentals/contract-development/errors-and-debugging/debugging",
+                          "docs/learn/fundamentals/contract-development/errors-and-debugging/debugging-errors"
+                        ]
+                      },
+                      "docs/learn/fundamentals/contract-development/contract-lifecycle"
+                    ]
+                  },
+                  {
+                    "group": "Data Format",
+                    "root": "docs/learn/fundamentals/data-format/index",
+                    "pages": [
+                      "docs/learn/fundamentals/data-format/xdr",
+                      "docs/learn/fundamentals/data-format/xdr-json"
+                    ]
+                  },
+                  "docs/learn/fundamentals/anchors"
+                ]
+              },
+              "docs/learn/glossary",
+              {
+                "group": "Migrate from Another Chain",
+                "root": "docs/learn/migrate/index",
+                "pages": [
+                  {
+                    "group": "EVM Networks",
+                    "root": "docs/learn/migrate/evm/index",
+                    "pages": [
+                      "docs/learn/migrate/evm/introduction-to-solidity-and-rust",
+                      "docs/learn/migrate/evm/solidity-and-rust-basics",
+                      "docs/learn/migrate/evm/solidity-and-rust-advanced-concepts",
+                      "docs/learn/migrate/evm/smart-contract-deployment",
+                      "docs/learn/migrate/evm/solidity-support-via-solang"
+                    ]
+                  }
+                ]
+              },
+              {
+                "group": "Interactive Learning",
+                "root": "docs/learn/interactive/index",
+                "pages": [
+                  "docs/learn/interactive/quest",
+                  "docs/learn/interactive/fca00c",
+                  "docs/learn/interactive/dapp-world"
+                ]
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "tab": "Tokens",
+        "pages": [
+          {
+            "group": " ",
+            "pages": [
+              "docs/tokens/index",
+              "docs/tokens/anatomy-of-an-asset",
+              "docs/tokens/quickstart",
+              "docs/tokens/control-asset-access",
+              "docs/tokens/stellar-asset-contract",
+              "docs/tokens/token-interface",
+              "docs/tokens/how-to-issue-an-asset",
+              "docs/tokens/publishing-asset-info",
+              "docs/tokens/cross-chain-transfers",
+              "docs/tokens/usdt0-layerzero"
+            ]
+          }
+        ]
+      },
+      {
+        "tab": "Data",
+        "pages": [
+          {
+            "group": " ",
+            "pages": [
+              "docs/data/index",
+              {
+                "group": "Analytics Overview",
+                "root": "docs/data/analytics/index",
+                "pages": [
+                  {
+                    "group": "Hubble",
+                    "root": "docs/data/analytics/hubble/index",
+                    "pages": [
+                      {
+                        "group": "Analyst Guide",
+                        "root": "docs/data/analytics/hubble/analyst-guide/index",
+                        "pages": [
+                          "docs/data/analytics/hubble/analyst-guide/connecting",
+                          "docs/data/analytics/hubble/analyst-guide/viewing-metadata",
+                          "docs/data/analytics/hubble/analyst-guide/optimizing-queries",
+                          "docs/data/analytics/hubble/analyst-guide/creating-visualizations",
+                          "docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data",
+                          "docs/data/analytics/hubble/analyst-guide/history-vs-state-tables"
+                        ]
+                      },
+                      {
+                        "group": "Developer Guide",
+                        "root": "docs/data/analytics/hubble/developer-guide/index",
+                        "pages": [
+                          {
+                            "group": "Backfill",
+                            "root": "docs/data/analytics/hubble/developer-guide/backfill/index",
+                            "pages": [
+                              "docs/data/analytics/hubble/developer-guide/backfill/JS-UDF",
+                              "docs/data/analytics/hubble/developer-guide/backfill/data-import"
+                            ]
+                          },
+                          "docs/data/analytics/hubble/developer-guide/connecting-to-bigquery/index",
+                          {
+                            "group": "Source System Ingestion",
+                            "root": "docs/data/analytics/hubble/developer-guide/source-system-ingestion/index",
+                            "pages": [
+                              "docs/data/analytics/hubble/developer-guide/source-system-ingestion/overview",
+                              "docs/data/analytics/hubble/developer-guide/source-system-ingestion/architecture",
+                              "docs/data/analytics/hubble/developer-guide/source-system-ingestion/getting-started"
+                            ]
+                          },
+                          {
+                            "group": "Data Curation",
+                            "root": "docs/data/analytics/hubble/developer-guide/data-curation/index",
+                            "pages": [
+                              "docs/data/analytics/hubble/developer-guide/data-curation/overview",
+                              "docs/data/analytics/hubble/developer-guide/data-curation/architecture",
+                              "docs/data/analytics/hubble/developer-guide/data-curation/getting-started"
+                            ]
+                          },
+                          {
+                            "group": "Visualization",
+                            "root": "docs/data/analytics/hubble/developer-guide/visualization/index",
+                            "pages": [
+                              "docs/data/analytics/hubble/developer-guide/visualization/overview",
+                              "docs/data/analytics/hubble/developer-guide/visualization/getting-started"
+                            ]
+                          },
+                          {
+                            "group": "Scheduling and Orchestration",
+                            "root": "docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/index",
+                            "pages": [
+                              "docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/overview",
+                              "docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/architecture",
+                              "docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/getting-started"
+                            ]
+                          }
+                        ]
+                      },
+                      {
+                        "group": "Data Catalog",
+                        "root": "docs/data/analytics/hubble/data-catalog/index",
+                        "pages": [
+                          "docs/data/analytics/hubble/data-catalog/data-model-diagram",
+                          {
+                            "group": "Data Dictionary",
+                            "root": "docs/data/analytics/hubble/data-catalog/data-dictionary/index",
+                            "pages": [
+                              {
+                                "group": "Bronze 🥉",
+                                "root": "docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/index",
+                                "pages": [
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/accounts",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/account-signers",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/claimable-balances",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-code",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/config-settings",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-data",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/liquidity-pools",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/offers",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/restored-key",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/trustlines",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/evicted-keys",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/ttl",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-assets",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-contract-events",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-effects",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-ledgers",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-operations",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-trades",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-transactions"
+                                ]
+                              },
+                              {
+                                "group": "Silver 🥈",
+                                "root": "docs/data/analytics/hubble/data-catalog/data-dictionary/silver/index",
+                                "pages": [
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/silver/account-signers-current",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-current",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-snapshot",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/silver/claimable-balances-current",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/silver/config-settings-current",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/silver/config-settings-snapshot",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-code-current",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-current",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-snapshot",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/silver/evicted-keys-snapshot",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-current",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-snapshot",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/silver/offers-current",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-cex-snapshot",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-fex-snapshot",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-sdex-snapshot",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-current",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-snapshot",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/silver/ttl-current",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations-soroban",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/silver/token-transfers-raw"
+                                ]
+                              },
+                              {
+                                "group": "Gold 🥇",
+                                "root": "docs/data/analytics/hubble/data-catalog/data-dictionary/gold/index",
+                                "pages": [
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/gold/asset-balances-daily-agg",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/gold/trade-agg",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/gold/tvl-agg",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/gold/ledger-fee-stats-agg",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/gold/daily-fee-stats-agg",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/gold/hourly-soroban-fee-agg-contract",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/gold/hourly-fee-agg-account",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/gold/account-balances-daily-agg",
+                                  "docs/data/analytics/hubble/data-catalog/data-dictionary/gold/soroban-core-metrics"
+                                ]
+                              }
+                            ]
+                          },
+                          "docs/data/analytics/hubble/data-catalog/data-lineage"
+                        ]
+                      }
+                    ]
+                  },
+                  "docs/data/analytics/public-dashboards",
+                  "docs/data/analytics/analytics-providers/index"
+                ]
+              },
+              {
+                "group": "APIs Overview",
+                "root": "docs/data/apis/index",
+                "pages": [
+                  {
+                    "group": "RPC",
+                    "root": "docs/data/apis/rpc/index",
+                    "pages": [
+                      {
+                        "group": "Admin Guide",
+                        "root": "docs/data/apis/rpc/admin-guide/index",
+                        "pages": [
+                          "docs/data/apis/rpc/admin-guide/prerequisites",
+                          "docs/data/apis/rpc/admin-guide/installing",
+                          "docs/data/apis/rpc/admin-guide/configuring",
+                          "docs/data/apis/rpc/admin-guide/running",
+                          "docs/data/apis/rpc/admin-guide/development",
+                          "docs/data/apis/rpc/admin-guide/monitoring",
+                          "docs/data/apis/rpc/admin-guide/data-lake-integration"
+                        ]
+                      },
+                      {
+                        "group": "API Reference",
+                        "root": "docs/data/apis/rpc/api-reference/index",
+                        "pages": [
+                          {
+                            "group": "Methods",
+                            "root": "docs/data/apis/rpc/api-reference/methods/index",
+                            "pages": [
+                              "docs/data/apis/rpc/api-reference/methods/getEvents",
+                              "docs/data/apis/rpc/api-reference/methods/getFeeStats",
+                              "docs/data/apis/rpc/api-reference/methods/getHealth",
+                              "docs/data/apis/rpc/api-reference/methods/getLatestLedger",
+                              "docs/data/apis/rpc/api-reference/methods/getLedgerEntries",
+                              "docs/data/apis/rpc/api-reference/methods/getLedgers",
+                              "docs/data/apis/rpc/api-reference/methods/getNetwork",
+                              "docs/data/apis/rpc/api-reference/methods/getTransaction",
+                              "docs/data/apis/rpc/api-reference/methods/getTransactions",
+                              "docs/data/apis/rpc/api-reference/methods/getVersionInfo",
+                              "docs/data/apis/rpc/api-reference/methods/queryEvents",
+                              "docs/data/apis/rpc/api-reference/methods/sendTransaction",
+                              "docs/data/apis/rpc/api-reference/methods/simulateTransaction"
+                            ]
+                          },
+                          {
+                            "group": "Structure",
+                            "root": "docs/data/apis/rpc/api-reference/structure/index",
+                            "pages": [
+                              "docs/data/apis/rpc/api-reference/structure/json-rpc",
+                              "docs/data/apis/rpc/api-reference/structure/pagination",
+                              "docs/data/apis/rpc/api-reference/structure/data-format"
+                            ]
+                          }
+                        ]
+                      },
+                      "docs/data/apis/rpc/providers"
+                    ]
+                  },
+                  {
+                    "group": "Horizon",
+                    "root": "docs/data/apis/horizon/index",
+                    "pages": [
+                      {
+                        "group": "Admin Guide",
+                        "root": "docs/data/apis/horizon/admin-guide/index",
+                        "pages": [
+                          "docs/data/apis/horizon/admin-guide/overview",
+                          "docs/data/apis/horizon/admin-guide/prerequisites",
+                          "docs/data/apis/horizon/admin-guide/installing",
+                          "docs/data/apis/horizon/admin-guide/configuring",
+                          "docs/data/apis/horizon/admin-guide/running",
+                          "docs/data/apis/horizon/admin-guide/ingestion",
+                          "docs/data/apis/horizon/admin-guide/monitoring",
+                          "docs/data/apis/horizon/admin-guide/scaling",
+                          "docs/data/apis/horizon/admin-guide/upgrading",
+                          "docs/data/apis/horizon/admin-guide/ingestion-filtering"
+                        ]
+                      },
+                      {
+                        "group": "API Reference",
+                        "root": "docs/data/apis/horizon/api-reference/index",
+                        "pages": [
+                          {
+                            "group": "Resources",
+                            "root": "docs/data/apis/horizon/api-reference/resources/index",
+                            "pages": [
+                              {
+                                "group": "Accounts",
+                                "root": "docs/data/apis/horizon/api-reference/resources/accounts/index",
+                                "pages": [
+                                  "docs/data/apis/horizon/api-reference/resources/accounts/object",
+                                  "docs/data/apis/horizon/api-reference/list-all-accounts",
+                                  "docs/data/apis/horizon/api-reference/retrieve-an-account",
+                                  "docs/data/apis/horizon/api-reference/get-transactions-by-account-id",
+                                  "docs/data/apis/horizon/api-reference/get-operations-by-account-id",
+                                  "docs/data/apis/horizon/api-reference/get-payments-by-account-id",
+                                  "docs/data/apis/horizon/api-reference/get-effects-by-account-id",
+                                  "docs/data/apis/horizon/api-reference/get-offers-by-account-id",
+                                  "docs/data/apis/horizon/api-reference/get-trades-by-account-id",
+                                  "docs/data/apis/horizon/api-reference/get-data-by-account-id"
+                                ]
+                              },
+                              {
+                                "group": "Assets",
+                                "root": "docs/data/apis/horizon/api-reference/resources/assets/index",
+                                "pages": [
+                                  "docs/data/apis/horizon/api-reference/resources/assets/object",
+                                  "docs/data/apis/horizon/api-reference/list-all-assets"
+                                ]
+                              },
+                              {
+                                "group": "Claimable Balances",
+                                "root": "docs/data/apis/horizon/api-reference/resources/claimablebalances/index",
+                                "pages": [
+                                  "docs/data/apis/horizon/api-reference/resources/claimablebalances/object",
+                                  "docs/data/apis/horizon/api-reference/list-all-claimable-balances",
+                                  "docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance",
+                                  "docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions",
+                                  "docs/data/apis/horizon/api-reference/cb-retrieve-related-operations"
+                                ]
+                              },
+                              {
+                                "group": "Effects",
+                                "root": "docs/data/apis/horizon/api-reference/resources/effects/index",
+                                "pages": [
+                                  "docs/data/apis/horizon/api-reference/resources/effects/types",
+                                  "docs/data/apis/horizon/api-reference/list-all-effects"
+                                ]
+                              },
+                              {
+                                "group": "Ledgers",
+                                "root": "docs/data/apis/horizon/api-reference/resources/ledgers/index",
+                                "pages": [
+                                  "docs/data/apis/horizon/api-reference/resources/ledgers/object",
+                                  "docs/data/apis/horizon/api-reference/retrieve-a-ledger",
+                                  "docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions",
+                                  "docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments",
+                                  "docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations",
+                                  "docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects",
+                                  "docs/data/apis/horizon/api-reference/list-all-ledgers"
+                                ]
+                              },
+                              {
+                                "group": "Liquidity Pools",
+                                "root": "docs/data/apis/horizon/api-reference/resources/liquiditypools/index",
+                                "pages": [
+                                  "docs/data/apis/horizon/api-reference/list-liquidity-pools",
+                                  "docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool",
+                                  "docs/data/apis/horizon/api-reference/retrieve-related-effects",
+                                  "docs/data/apis/horizon/api-reference/retrieve-related-trades",
+                                  "docs/data/apis/horizon/api-reference/lp-retrieve-related-transactions",
+                                  "docs/data/apis/horizon/api-reference/lp-retrieve-related-operations"
+                                ]
+                              },
+                              {
+                                "group": "Offers",
+                                "root": "docs/data/apis/horizon/api-reference/resources/offers/index",
+                                "pages": [
+                                  "docs/data/apis/horizon/api-reference/resources/offers/object",
+                                  "docs/data/apis/horizon/api-reference/get-all-offers",
+                                  "docs/data/apis/horizon/api-reference/get-offer-by-offer-id",
+                                  "docs/data/apis/horizon/api-reference/get-trades-by-offer-id"
+                                ]
+                              },
+                              {
+                                "group": "Operations",
+                                "root": "docs/data/apis/horizon/api-reference/resources/operations/index",
+                                "pages": [
+                                  {
+                                    "group": "The Operation Object",
+                                    "root": "docs/data/apis/horizon/api-reference/resources/operations/object/index",
+                                    "pages": [
+                                      "docs/data/apis/horizon/api-reference/resources/operations/object/account-merge",
+                                      "docs/data/apis/horizon/api-reference/resources/operations/object/allow-trust",
+                                      "docs/data/apis/horizon/api-reference/resources/operations/object/begin-sponsoring-future-reserves",
+                                      "docs/data/apis/horizon/api-reference/resources/operations/object/bump-sequence",
+                                      "docs/data/apis/horizon/api-reference/resources/operations/object/buy-offer",
+                                      "docs/data/apis/horizon/api-reference/resources/operations/object/change-trust",
+                                      "docs/data/apis/horizon/api-reference/resources/operations/object/claim-claimable-balance",
+                                      "docs/data/apis/horizon/api-reference/resources/operations/object/create-account",
+                                      "docs/data/apis/horizon/api-reference/resources/operations/object/create-claimable-balance",
+                                      "docs/data/apis/horizon/api-reference/resources/operations/object/end-sponsoring-future-reserves",
+                                      "docs/data/apis/horizon/api-reference/resources/operations/object/extend-footprint-ttl",
+                                      "docs/data/apis/horizon/api-reference/resources/operations/object/invoke-host-function",
+                                      "docs/data/apis/horizon/api-reference/resources/operations/object/liquidity-pool-deposit",
+                                      "docs/data/apis/horizon/api-reference/resources/operations/object/liquidity-pool-withdraw",
+                                      "docs/data/apis/horizon/api-reference/resources/operations/object/manage-data",
+                                      "docs/data/apis/horizon/api-reference/resources/operations/object/passive-sell-offer",
+                                      "docs/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-receive",
+                                      "docs/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-send",
+                                      "docs/data/apis/horizon/api-reference/resources/operations/object/restore-footprint",
+                                      "docs/data/apis/horizon/api-reference/resources/operations/object/revoke-sponsorship",
+                                      "docs/data/apis/horizon/api-reference/resources/operations/object/sell-offer",
+                                      "docs/data/apis/horizon/api-reference/resources/operations/object/set-options"
+                                    ]
+                                  },
+                                  "docs/data/apis/horizon/api-reference/retrieve-an-operation",
+                                  "docs/data/apis/horizon/api-reference/retrieve-an-operations-effects",
+                                  "docs/data/apis/horizon/api-reference/list-all-operations"
+                                ]
+                              },
+                              {
+                                "group": "Payments",
+                                "root": "docs/data/apis/horizon/api-reference/resources/payments/index",
+                                "pages": [
+                                  "docs/data/apis/horizon/api-reference/resources/payments/object",
+                                  "docs/data/apis/horizon/api-reference/list-all-payments",
+                                  "docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments"
+                                ]
+                              },
+                              {
+                                "group": "Trades",
+                                "root": "docs/data/apis/horizon/api-reference/resources/trades/index",
+                                "pages": [
+                                  "docs/data/apis/horizon/api-reference/resources/trades/object",
+                                  "docs/data/apis/horizon/api-reference/get-all-trades"
+                                ]
+                              },
+                              {
+                                "group": "Transactions",
+                                "root": "docs/data/apis/horizon/api-reference/resources/transactions/index",
+                                "pages": [
+                                  "docs/data/apis/horizon/api-reference/resources/transactions/object",
+                                  "docs/data/apis/horizon/api-reference/retrieve-a-transaction",
+                                  "docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations",
+                                  "docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects",
+                                  "docs/data/apis/horizon/api-reference/list-all-transactions",
+                                  "docs/data/apis/horizon/api-reference/submit-a-transaction",
+                                  "docs/data/apis/horizon/api-reference/submit-async-transaction"
+                                ]
+                              }
+                            ]
+                          },
+                          {
+                            "group": "Structure",
+                            "root": "docs/data/apis/horizon/api-reference/structure/index",
+                            "pages": [
+                              "docs/data/apis/horizon/api-reference/structure/response-format",
+                              "docs/data/apis/horizon/api-reference/structure/streaming",
+                              "docs/data/apis/horizon/api-reference/structure/rate-limiting",
+                              "docs/data/apis/horizon/api-reference/structure/xdr",
+                              "docs/data/apis/horizon/api-reference/structure/consistency",
+                              {
+                                "group": "Pagination",
+                                "root": "docs/data/apis/horizon/api-reference/structure/pagination/index",
+                                "pages": [
+                                  "docs/data/apis/horizon/api-reference/structure/pagination/page-arguments"
+                                ]
+                              }
+                            ]
+                          },
+                          {
+                            "group": "Aggregations",
+                            "root": "docs/data/apis/horizon/api-reference/aggregations/index",
+                            "pages": [
+                              {
+                                "group": "Order Books",
+                                "root": "docs/data/apis/horizon/api-reference/aggregations/order-books/index",
+                                "pages": [
+                                  "docs/data/apis/horizon/api-reference/aggregations/order-books/object",
+                                  "docs/data/apis/horizon/api-reference/retrieve-an-order-book"
+                                ]
+                              },
+                              {
+                                "group": "Paths",
+                                "root": "docs/data/apis/horizon/api-reference/aggregations/paths/index",
+                                "pages": [
+                                  "docs/data/apis/horizon/api-reference/aggregations/paths/object",
+                                  "docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths",
+                                  "docs/data/apis/horizon/api-reference/list-strict-send-payment-paths"
+                                ]
+                              },
+                              {
+                                "group": "Trade Aggregations",
+                                "root": "docs/data/apis/horizon/api-reference/aggregations/trade-aggregations/index",
+                                "pages": [
+                                  "docs/data/apis/horizon/api-reference/aggregations/trade-aggregations/object",
+                                  "docs/data/apis/horizon/api-reference/list-trade-aggregations"
+                                ]
+                              },
+                              {
+                                "group": "Fee Stats",
+                                "root": "docs/data/apis/horizon/api-reference/aggregations/fee-stats/index",
+                                "pages": [
+                                  "docs/data/apis/horizon/api-reference/aggregations/fee-stats/object",
+                                  "docs/data/apis/horizon/api-reference/retrieve-fee-stats"
+                                ]
+                              }
+                            ]
+                          },
+                          {
+                            "group": "Errors",
+                            "root": "docs/data/apis/horizon/api-reference/errors/index",
+                            "pages": [
+                              "docs/data/apis/horizon/api-reference/errors/response",
+                              "docs/data/apis/horizon/api-reference/errors/error-handling",
+                              {
+                                "group": "HTTP Status Codes",
+                                "root": "docs/data/apis/horizon/api-reference/errors/http-status-codes/index",
+                                "pages": [
+                                  "docs/data/apis/horizon/api-reference/errors/http-status-codes/standard",
+                                  {
+                                    "group": "Horizon-Specific Status Codes",
+                                    "root": "docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/index",
+                                    "pages": [
+                                      "docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-failed",
+                                      "docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-malformed",
+                                      "docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/before-history",
+                                      "docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/stale-history",
+                                      "docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/timeout"
+                                    ]
+                                  }
+                                ]
+                              },
+                              {
+                                "group": "Result Codes",
+                                "root": "docs/data/apis/horizon/api-reference/errors/result-codes/index",
+                                "pages": [
+                                  "docs/data/apis/horizon/api-reference/errors/result-codes/transactions",
+                                  "docs/data/apis/horizon/api-reference/errors/result-codes/operations",
+                                  {
+                                    "group": "Operation-Specific Result Codes",
+                                    "root": "docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/index",
+                                    "pages": [
+                                      "docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-account",
+                                      "docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/payment",
+                                      "docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-receive",
+                                      "docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-send",
+                                      "docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-sell-offer",
+                                      "docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-buy-offer",
+                                      "docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-passive-sell-offer",
+                                      "docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/set-options",
+                                      "docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/change-trust",
+                                      "docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/allow-trust",
+                                      "docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/account-merge",
+                                      "docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-data",
+                                      "docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/bump-sequence"
+                                    ]
+                                  }
+                                ]
+                              }
+                            ]
+                          }
+                        ]
+                      },
+                      "docs/data/apis/horizon/providers"
+                    ]
+                  },
+                  "docs/data/apis/migrate-from-horizon-to-rpc"
+                ]
+              },
+              {
+                "group": "Indexers",
+                "root": "docs/data/indexers/index",
+                "pages": [
+                  {
+                    "group": "Build Your Own",
+                    "root": "docs/data/indexers/build-your-own/index",
+                    "pages": [
+                      {
+                        "group": "Galexie",
+                        "root": "docs/data/indexers/build-your-own/galexie/index",
+                        "pages": [
+                          "docs/data/indexers/build-your-own/galexie/data-lake-format",
+                          {
+                            "group": "Admin Guide",
+                            "root": "docs/data/indexers/build-your-own/galexie/admin_guide/index",
+                            "pages": [
+                              "docs/data/indexers/build-your-own/galexie/admin_guide/prerequisites",
+                              "docs/data/indexers/build-your-own/galexie/admin_guide/setup",
+                              "docs/data/indexers/build-your-own/galexie/admin_guide/configuring",
+                              "docs/data/indexers/build-your-own/galexie/admin_guide/installing",
+                              "docs/data/indexers/build-your-own/galexie/admin_guide/running",
+                              "docs/data/indexers/build-your-own/galexie/admin_guide/monitoring",
+                              "docs/data/indexers/build-your-own/galexie/admin_guide/full-history-exporting"
+                            ]
+                          },
+                          {
+                            "group": "Example Usages",
+                            "root": "docs/data/indexers/build-your-own/galexie/examples/index",
+                            "pages": [
+                              "docs/data/indexers/build-your-own/galexie/examples/gcs-export"
+                            ]
+                          },
+                          "docs/data/indexers/build-your-own/galexie/providers"
+                        ]
+                      },
+                      {
+                        "group": "Ingest SDK",
+                        "root": "docs/data/indexers/build-your-own/ingest-sdk/index",
+                        "pages": [
+                          {
+                            "group": "Developer Guide",
+                            "root": "docs/data/indexers/build-your-own/ingest-sdk/developer_guide/index",
+                            "pages": [
+                              "docs/data/indexers/build-your-own/ingest-sdk/developer_guide/architecture",
+                              "docs/data/indexers/build-your-own/ingest-sdk/developer_guide/prerequisites",
+                              {
+                                "group": "Ledger Backends",
+                                "root": "docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/index",
+                                "pages": [
+                                  "docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/captivecore",
+                                  "docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/bufferedstoragebackend",
+                                  "docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/rpcledgerbackend"
+                                ]
+                              },
+                              "docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerreaders"
+                            ]
+                          },
+                          {
+                            "group": "Example Usages",
+                            "root": "docs/data/indexers/build-your-own/ingest-sdk/examples/index",
+                            "pages": [
+                              "docs/data/indexers/build-your-own/ingest-sdk/examples/transaction_statistics",
+                              "docs/data/indexers/build-your-own/ingest-sdk/examples/ledger_entry_statistics",
+                              "docs/data/indexers/build-your-own/ingest-sdk/examples/changes"
+                            ]
+                          }
+                        ]
+                      },
+                      {
+                        "group": "Processors",
+                        "root": "docs/data/indexers/build-your-own/processors/index",
+                        "pages": [
+                          {
+                            "group": "Token Transfer Processor",
+                            "root": "docs/data/indexers/build-your-own/processors/token-transfer-processor/index",
+                            "pages": [
+                              {
+                                "group": "Example Usages",
+                                "root": "docs/data/indexers/build-your-own/processors/token-transfer-processor/examples/index",
+                                "pages": [
+                                  "docs/data/indexers/build-your-own/processors/token-transfer-processor/examples/event_stats",
+                                  "docs/data/indexers/build-your-own/processors/token-transfer-processor/examples/filter_events"
+                                ]
+                              }
+                            ]
+                          }
+                        ]
+                      }
+                    ]
+                  }
+                ]
+              },
+              {
+                "group": "Oracles",
+                "root": "docs/data/oracles/index",
+                "pages": ["docs/data/oracles/oracle-providers"]
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "tab": "Tools",
+        "pages": [
+          {
+            "group": " ",
+            "pages": [
+              "docs/tools/index",
+              {
+                "group": "SDKs",
+                "root": "docs/tools/sdks/index",
+                "pages": [
+                  "docs/tools/sdks/contract-sdks",
+                  "docs/tools/sdks/client-sdks",
+                  "docs/tools/sdks/build-your-own"
+                ],
+                "expanded": true
+              },
+              {
+                "group": "Stellar CLI",
+                "root": "docs/tools/cli/index",
+                "pages": [
+                  "docs/tools/cli/install-cli",
+                  "docs/tools/cli/stellar-cli",
+                  {
+                    "group": "Stellar CLI for Agents",
+                    "root": "docs/tools/cli/agent-cli/index",
+                    "pages": [
+                      "docs/tools/cli/agent-cli/quickstart",
+                      "docs/tools/cli/agent-cli/skills",
+                      {
+                        "group": "Agent Cookbook",
+                        "pages": [
+                          "docs/tools/cli/agent-cli/guides/send-tokens",
+                          "docs/tools/cli/agent-cli/guides/check-balances-and-metadata",
+                          "docs/tools/cli/agent-cli/guides/delegate-spending",
+                          "docs/tools/cli/agent-cli/guides/sign-messages",
+                          "docs/tools/cli/agent-cli/guides/build-and-submit-transactions",
+                          "docs/tools/cli/agent-cli/guides/pay-for-apis-x402",
+                          "docs/tools/cli/agent-cli/guides/usdt0-on-mainnet",
+                          "docs/tools/cli/agent-cli/guides/build-and-deploy-contracts"
+                        ]
+                      },
+                      {
+                        "group": "Reference",
+                        "pages": [
+                          "docs/tools/cli/agent-cli/reference/architecture",
+                          "docs/tools/cli/agent-cli/reference/authority-model",
+                          "docs/tools/cli/agent-cli/reference/output-and-errors",
+                          "docs/tools/cli/agent-cli/reference/troubleshooting"
+                        ]
+                      }
+                    ]
+                  },
+                  "docs/tools/cli/plugins",
+                  "docs/tools/cli/plugins-list",
+                  {
+                    "group": "Cookbook",
+                    "root": "docs/tools/cli/cookbook/index",
+                    "expanded": true,
+                    "pages": [
+                      "docs/tools/cli/cookbook/asset-management",
+                      "docs/tools/cli/cookbook/contract-build-meta",
+                      "docs/tools/cli/cookbook/contract-invoke-arguments",
+                      "docs/tools/cli/cookbook/contract-lifecycle",
+                      "docs/tools/cli/cookbook/deploy-contract",
+                      "docs/tools/cli/cookbook/deploy-stellar-asset-contract",
+                      "docs/tools/cli/cookbook/extend-contract-instance",
+                      "docs/tools/cli/cookbook/extend-contract-storage",
+                      "docs/tools/cli/cookbook/extend-contract-wasm",
+                      "docs/tools/cli/cookbook/payments-and-assets",
+                      "docs/tools/cli/cookbook/restore-contract-instance",
+                      "docs/tools/cli/cookbook/restore-contract-storage",
+                      "docs/tools/cli/cookbook/stellar-keys",
+                      "docs/tools/cli/cookbook/tx-new-create-claimable-balance",
+                      "docs/tools/cli/cookbook/tx-new",
+                      "docs/tools/cli/cookbook/tx-op-add",
+                      "docs/tools/cli/cookbook/tx-sign",
+                      "docs/tools/cli/cookbook/upload-deploy",
+                      "docs/tools/cli/cookbook/upload-wasm"
+                    ]
+                  }
+                ],
+                "expanded": true
+              },
+              {
+                "group": "Lab",
+                "root": "docs/tools/lab/index",
+                "pages": [
+                  {
+                    "group": "View XDR",
+                    "root": "docs/tools/lab/view-xdr/index",
+                    "pages": [
+                      "docs/tools/lab/view-xdr/xdr-to-json",
+                      "docs/tools/lab/view-xdr/json-to-xdr",
+                      "docs/tools/lab/view-xdr/diff-xdr"
+                    ]
+                  },
+                  "docs/tools/lab/account",
+                  {
+                    "group": "Saved",
+                    "root": "docs/tools/lab/saved/index",
+                    "pages": [
+                      "docs/tools/lab/saved/keypairs",
+                      "docs/tools/lab/saved/requests",
+                      "docs/tools/lab/saved/transactions"
+                    ]
+                  },
+                  "docs/tools/lab/transactions",
+                  {
+                    "group": "API Explorer",
+                    "root": "docs/tools/lab/api-explorer/index",
+                    "pages": [
+                      "docs/tools/lab/api-explorer/horizon-endpoint",
+                      "docs/tools/lab/api-explorer/rpc-methods"
+                    ]
+                  },
+                  {
+                    "group": "Smart Contracts",
+                    "root": "docs/tools/lab/smart-contracts/index",
+                    "pages": [
+                      "docs/tools/lab/smart-contracts/contract-explorer",
+                      "docs/tools/lab/smart-contracts/smart-contract-list",
+                      "docs/tools/lab/smart-contracts/upload-deploy-contract"
+                    ]
+                  },
+                  "docs/tools/lab/transaction-dashboard",
+                  "docs/tools/lab/quickstart-with-lab"
+                ],
+                "expanded": true
+              },
+              {
+                "group": "Quickstart",
+                "root": "docs/tools/quickstart/index",
+                "pages": [
+                  {
+                    "group": "Getting Started",
+                    "root": "docs/tools/quickstart/getting-started/index",
+                    "pages": [
+                      "docs/tools/quickstart/getting-started/connect-stellar-lab",
+                      "docs/tools/quickstart/getting-started/deploy-smart-contract"
+                    ]
+                  },
+                  "docs/tools/quickstart/explorer",
+                  "docs/tools/quickstart/network-modes",
+                  "docs/tools/quickstart/faucet",
+                  {
+                    "group": "Debugging",
+                    "root": "docs/tools/quickstart/debugging/index",
+                    "pages": [
+                      "docs/tools/quickstart/debugging/diagnostic-events",
+                      "docs/tools/quickstart/debugging/viewing-logs"
+                    ]
+                  },
+                  {
+                    "group": "Cloud Deployment",
+                    "root": "docs/tools/quickstart/cloud/index",
+                    "pages": [
+                      "docs/tools/quickstart/cloud/digitalocean",
+                      "docs/tools/quickstart/cloud/fly.io"
+                    ]
+                  },
+                  {
+                    "group": "Advanced Usage",
+                    "root": "docs/tools/quickstart/advanced-usage/index",
+                    "pages": [
+                      "docs/tools/quickstart/advanced-usage/container",
+                      "docs/tools/quickstart/advanced-usage/service-options",
+                      "docs/tools/quickstart/advanced-usage/operation-modes",
+                      "docs/tools/quickstart/advanced-usage/ports",
+                      "docs/tools/quickstart/advanced-usage/run-command-examples"
+                    ]
+                  }
+                ]
+              },
+              "docs/tools/openzeppelin-relayer",
+              "docs/tools/openzeppelin-contracts",
+              "docs/tools/scaffold-stellar",
+              {
+                "group": "More Developer Tools",
+                "root": "docs/tools/developer-tools/index",
+                "pages": [
+                  "docs/tools/developer-tools/analytics-platforms",
+                  "docs/tools/developer-tools/anchor-tools",
+                  "docs/tools/developer-tools/asset-tools",
+                  "docs/tools/developer-tools/block-explorers",
+                  "docs/tools/developer-tools/jupyter-notebooks",
+                  "docs/tools/developer-tools/online-ide",
+                  "docs/tools/developer-tools/network-insights",
+                  "docs/tools/developer-tools/network-status",
+                  "docs/tools/developer-tools/node-operator-tools",
+                  "docs/tools/developer-tools/security-tools",
+                  "docs/tools/developer-tools/wallets"
+                ]
+              },
+              {
+                "group": "Ramps",
+                "root": "docs/tools/ramps/index",
+                "pages": ["docs/tools/ramps/moneygram"]
+              },
+              {
+                "group": "Infrastructure Tools",
+                "root": "docs/tools/infra-tools/index",
+                "pages": ["docs/tools/infra-tools/cross-chain"]
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "tab": "Networks",
+        "pages": [
+          {
+            "group": " ",
+            "pages": [
+              "docs/networks/index",
+              "docs/networks/software-versions",
+              "docs/networks/resource-limits-fees",
+              {
+                "group": "Audits",
+                "root": "docs/networks/audits/index",
+                "pages": [
+                  "docs/networks/audits/stellar-core",
+                  "docs/networks/audits/stellar-rpc",
+                  "docs/networks/audits/soroban-sdk",
+                  "docs/networks/audits/soroban-poseidon"
+                ]
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "tab": "Validators",
+        "pages": [
+          {
+            "group": " ",
+            "pages": [
+              "docs/validators/index",
+              {
+                "group": "Admin Guide",
+                "root": "docs/validators/admin-guide/index",
+                "pages": [
+                  "docs/validators/admin-guide/prerequisites",
+                  "docs/validators/admin-guide/installation",
+                  "docs/validators/admin-guide/configuring",
+                  "docs/validators/admin-guide/environment-preparation",
+                  "docs/validators/admin-guide/publishing-history-archives",
+                  "docs/validators/admin-guide/running-node",
+                  "docs/validators/admin-guide/logging",
+                  "docs/validators/admin-guide/monitoring",
+                  "docs/validators/admin-guide/maintenance",
+                  "docs/validators/admin-guide/network-upgrades",
+                  "docs/validators/admin-guide/soroban-settings",
+                  "docs/validators/admin-guide/commands",
+                  "docs/validators/admin-guide/advanced"
+                ],
+                "expanded": true
+              },
+              "docs/validators/tier-1-orgs"
+            ]
+          }
+        ]
+      },
+      {
+        "tab": "Platforms",
+        "pages": [
+          {
+            "group": " ",
+            "pages": [
+              "docs/platforms/index",
+              {
+                "group": "Anchor Platform",
+                "pages": [
+                  "docs/platforms/anchor-platform/index",
+                  {
+                    "group": "Admin Guide",
+                    "root": "docs/platforms/anchor-platform/admin-guide/index",
+                    "expanded": true,
+                    "pages": [
+                      "docs/platforms/anchor-platform/admin-guide/architecture",
+                      "docs/platforms/anchor-platform/admin-guide/getting-started",
+                      "docs/platforms/anchor-platform/admin-guide/assets-and-client-wallets",
+                      {
+                        "group": "Event Handling",
+                        "root": "docs/platforms/anchor-platform/admin-guide/events/index",
+                        "pages": [
+                          "docs/platforms/anchor-platform/admin-guide/events/getting-started",
+                          "docs/platforms/anchor-platform/admin-guide/events/integration",
+                          "docs/platforms/anchor-platform/admin-guide/events/delivery"
+                        ]
+                      }
+                    ]
+                  },
+                  {
+                    "group": "API Reference",
+                    "root": "docs/platforms/anchor-platform/api-reference/index",
+                    "expanded": true,
+                    "pages": [
+                      {
+                        "group": "Platform Server",
+                        "root": "docs/platforms/anchor-platform/api-reference/platform/index",
+                        "pages": [
+                          {
+                            "group": "Transactions",
+                            "root": "docs/platforms/anchor-platform/api-reference/platform/transactions/index",
+                            "pages": [
+                              "docs/platforms/anchor-platform/api-reference/platform/transactions/get-transaction",
+                              "docs/platforms/anchor-platform/api-reference/platform/transactions/get-transactions"
+                            ]
+                          },
+                          {
+                            "group": "JSON-RPC API",
+                            "root": "docs/platforms/anchor-platform/api-reference/platform/rpc/index",
+                            "pages": [
+                              "docs/platforms/anchor-platform/api-reference/platform/rpc/overview",
+                              {
+                                "group": "Methods",
+                                "root": "docs/platforms/anchor-platform/api-reference/platform/rpc/methods/index",
+                                "pages": [
+                                  "docs/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_payment",
+                                  "docs/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_refund",
+                                  "docs/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transaction",
+                                  "docs/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transactions",
+                                  "docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_amounts_updated",
+                                  "docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_customer_info_updated",
+                                  "docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_interactive_flow_completed",
+                                  "docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_available",
+                                  "docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_pending",
+                                  "docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_received",
+                                  "docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_sent",
+                                  "docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_received",
+                                  "docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_sent",
+                                  "docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_pending",
+                                  "docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_sent",
+                                  "docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_error",
+                                  "docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_expired",
+                                  "docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_on_hold",
+                                  "docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_recovery",
+                                  "docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_trust_set",
+                                  "docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_offchain_funds",
+                                  "docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_onchain_funds",
+                                  "docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_trust"
+                                ]
+                              }
+                            ]
+                          }
+                        ]
+                      },
+                      {
+                        "group": "Callbacks Server",
+                        "root": "docs/platforms/anchor-platform/api-reference/callbacks/index",
+                        "pages": [
+                          "docs/platforms/anchor-platform/api-reference/callbacks/del-customer",
+                          "docs/platforms/anchor-platform/api-reference/callbacks/get-customer",
+                          "docs/platforms/anchor-platform/api-reference/callbacks/get-rates",
+                          "docs/platforms/anchor-platform/api-reference/callbacks/post-event",
+                          "docs/platforms/anchor-platform/api-reference/callbacks/put-customer"
+                        ]
+                      }
+                    ]
+                  },
+                  {
+                    "group": "SEP Guides",
+                    "root": "docs/platforms/anchor-platform/sep-guide/index",
+                    "expanded": true,
+                    "pages": [
+                      "docs/platforms/anchor-platform/sep-guide/sep1/index",
+                      "docs/platforms/anchor-platform/sep-guide/sep10/index",
+                      "docs/platforms/anchor-platform/sep-guide/sep45/index",
+                      {
+                        "group": "Programmatic Deposits and Withdrawals (SEP-6)",
+                        "root": "docs/platforms/anchor-platform/sep-guide/sep6/index",
+                        "pages": [
+                          "docs/platforms/anchor-platform/sep-guide/sep6/getting-started",
+                          "docs/platforms/anchor-platform/sep-guide/sep6/configuration",
+                          "docs/platforms/anchor-platform/sep-guide/sep6/integration"
+                        ]
+                      },
+                      {
+                        "group": "Hosted Deposits and Withdrawals (SEP-24)",
+                        "root": "docs/platforms/anchor-platform/sep-guide/sep24/index",
+                        "pages": [
+                          "docs/platforms/anchor-platform/sep-guide/sep24/getting-started",
+                          "docs/platforms/anchor-platform/sep-guide/sep24/configuration",
+                          "docs/platforms/anchor-platform/sep-guide/sep24/integration",
+                          "docs/platforms/anchor-platform/sep-guide/sep24/example",
+                          "docs/platforms/anchor-platform/sep-guide/sep24/faq",
+                          "docs/platforms/anchor-platform/sep-guide/sep24/setting-up-production-server"
+                        ]
+                      },
+                      {
+                        "group": "Cross-Border Payments (SEP-31)",
+                        "root": "docs/platforms/anchor-platform/sep-guide/sep31/index",
+                        "pages": [
+                          "docs/platforms/anchor-platform/sep-guide/sep31/getting-started",
+                          "docs/platforms/anchor-platform/sep-guide/sep31/configuration",
+                          "docs/platforms/anchor-platform/sep-guide/sep31/integration"
+                        ]
+                      }
+                    ]
+                  }
+                ]
+              },
+              {
+                "group": "Stellar Disbursement Platform",
+                "pages": [
+                  "docs/platforms/stellar-disbursement-platform/index",
+                  {
+                    "group": "Admin Guide",
+                    "expanded": true,
+                    "pages": [
+                      "docs/platforms/stellar-disbursement-platform/admin-guide/overview",
+                      "docs/platforms/stellar-disbursement-platform/admin-guide/getting-started",
+                      "docs/platforms/stellar-disbursement-platform/admin-guide/design-and-architecture",
+                      "docs/platforms/stellar-disbursement-platform/admin-guide/deploy-the-sdp",
+                      "docs/platforms/stellar-disbursement-platform/admin-guide/configuring-sdp",
+                      "docs/platforms/stellar-disbursement-platform/admin-guide/advanced-configuration",
+                      "docs/platforms/stellar-disbursement-platform/admin-guide/cli-manual",
+                      "docs/platforms/stellar-disbursement-platform/admin-guide/embedded-wallets",
+                      "docs/platforms/stellar-disbursement-platform/admin-guide/security",
+                      "docs/platforms/stellar-disbursement-platform/admin-guide/monitoring",
+                      "docs/platforms/stellar-disbursement-platform/admin-guide/making-your-wallet-sdp-ready",
+                      "docs/platforms/stellar-disbursement-platform/admin-guide/troubleshooting",
+                      {
+                        "group": "User Interface",
+                        "root": "docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/index",
+                        "pages": [
+                          "docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/dashboard-home",
+                          "docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/disbursements",
+                          "docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/receivers",
+                          "docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/payments",
+                          "docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/distribution-accounts",
+                          "docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/analytics",
+                          "docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/account-picker",
+                          "docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/circle-configuration"
+                        ]
+                      }
+                    ],
+                    "root": "docs/platforms/stellar-disbursement-platform/admin-guide/index",
+                    "directory": "card"
+                  },
+                  {
+                    "group": "API Reference",
+                    "pages": [
+                      {
+                        "group": "Admin (Tenant Management)",
+                        "root": "docs/platforms/stellar-disbursement-platform/api-reference/admin",
+                        "pages": [
+                          "docs/platforms/stellar-disbursement-platform/api-reference/get-all-tenants",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/create-tenant",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/update-a-tenant",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/default-tenant"
+                        ]
+                      },
+                      {
+                        "group": "Authentication",
+                        "root": "docs/platforms/stellar-disbursement-platform/api-reference/authentication",
+                        "pages": [
+                          "docs/platforms/stellar-disbursement-platform/api-reference/log-in",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/refresh-token",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/authenticate-mfa",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/forgot-password",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/reset-password"
+                        ]
+                      },
+                      {
+                        "group": "API Keys",
+                        "root": "docs/platforms/stellar-disbursement-platform/api-reference/api-keys",
+                        "pages": [
+                          "docs/platforms/stellar-disbursement-platform/api-reference/list-api-keys",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/create-api-key",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/get-api-key",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/update-api-key",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/delete-api-key"
+                        ]
+                      },
+                      {
+                        "group": "Balances",
+                        "root": "docs/platforms/stellar-disbursement-platform/api-reference/balances",
+                        "pages": [
+                          "docs/platforms/stellar-disbursement-platform/api-reference/get-organization-circle-balances"
+                        ]
+                      },
+                      {
+                        "group": "Bridge Integration",
+                        "root": "docs/platforms/stellar-disbursement-platform/api-reference/bridge-integration",
+                        "pages": [
+                          "docs/platforms/stellar-disbursement-platform/api-reference/get-bridge-integration",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/update-bridge-integration"
+                        ]
+                      },
+                      {
+                        "group": "Disbursements",
+                        "root": "docs/platforms/stellar-disbursement-platform/api-reference/disbursements",
+                        "pages": [
+                          "docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursements",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/create-disbursement",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/list-registration-contact-types"
+                        ]
+                      },
+                      {
+                        "group": "Distribution Wallets",
+                        "root": "docs/platforms/stellar-disbursement-platform/api-reference/distribution-wallets",
+                        "pages": [
+                          "docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallets",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/create-distribution-wallet",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallets-total-balance",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-balance",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-capabilities",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallet-memberships",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/grant-distribution-wallet-membership",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/revoke-distribution-wallet-membership",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-audit",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/archive-distribution-wallet",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/promote-distribution-wallet-to-default"
+                        ]
+                      },
+                      {
+                        "group": "Organization",
+                        "root": "docs/platforms/stellar-disbursement-platform/api-reference/organization",
+                        "pages": [
+                          "docs/platforms/stellar-disbursement-platform/api-reference/get-organization-info",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/update-organization-profile",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/get-organization-logo",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/patch-organization-circle",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/get-all-assets",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/create-asset",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/delete-asset"
+                        ]
+                      },
+                      {
+                        "group": "Payments",
+                        "root": "docs/platforms/stellar-disbursement-platform/api-reference/payments",
+                        "pages": [
+                          "docs/platforms/stellar-disbursement-platform/api-reference/list-all-payments",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/create-direct-payment",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/retry-payments",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/update-payment-status"
+                        ]
+                      },
+                      {
+                        "group": "Profile",
+                        "root": "docs/platforms/stellar-disbursement-platform/api-reference/profile",
+                        "pages": [
+                          "docs/platforms/stellar-disbursement-platform/api-reference/get-profile",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/update-user-profile",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/reset-user-password"
+                        ]
+                      },
+                      {
+                        "group": "Receivers",
+                        "root": "docs/platforms/stellar-disbursement-platform/api-reference/receivers",
+                        "pages": [
+                          "docs/platforms/stellar-disbursement-platform/api-reference/list-receiver-verification-types",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/list-all-receivers",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/create-receiver",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/update-receiver",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet-status"
+                        ]
+                      },
+                      {
+                        "group": "Registration",
+                        "root": "docs/platforms/stellar-disbursement-platform/api-reference/registration",
+                        "pages": [
+                          "docs/platforms/stellar-disbursement-platform/api-reference/get-receiver-registration-info",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/send-one-time-passcode",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/verify-receiver-registration",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/start-wallet-registration",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/retrieve-stellar-info-file",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/provide-signed-challenge-transaction",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/get-sep-24-info",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/request-registration-url"
+                        ]
+                      },
+                      {
+                        "group": "Statistics",
+                        "root": "docs/platforms/stellar-disbursement-platform/api-reference/statistics",
+                        "pages": [
+                          "docs/platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics"
+                        ]
+                      },
+                      {
+                        "group": "Users",
+                        "root": "docs/platforms/stellar-disbursement-platform/api-reference/users",
+                        "pages": [
+                          "docs/platforms/stellar-disbursement-platform/api-reference/get-all-users",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/create-user",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/update-user-activation-status",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/get-all-roles",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/update-user-role"
+                        ]
+                      },
+                      {
+                        "group": "Exports",
+                        "pages": [
+                          "docs/platforms/stellar-disbursement-platform/api-reference/export-disbursements",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/export-payments-csv",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/export-receivers-csv"
+                        ]
+                      },
+                      {
+                        "group": "Wallets",
+                        "pages": [
+                          "docs/platforms/stellar-disbursement-platform/api-reference/get-all-wallets",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/create-wallet",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/update-wallet",
+                          "docs/platforms/stellar-disbursement-platform/api-reference/delete-wallet"
+                        ]
+                      }
+                    ],
+                    "root": "docs/platforms/stellar-disbursement-platform/api-reference/index",
+                    "directory": "card"
+                  }
+                ]
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "tab": "Meeting Notes",
+        "pages": [
+          {
+            "group": " ",
+            "pages": [
+              "meetings/index",
+              {
+                "group": "2026",
+                "pages": [
+                  "meetings/2026/10/08",
+                  "meetings/2026/10/01",
+                  "meetings/2026/09/24",
+                  "meetings/2026/09/17/protocol",
+                  "meetings/2026/09/17",
+                  "meetings/2026/09/10",
+                  "meetings/2026/09/03",
+                  "meetings/2026/08/27",
+                  "meetings/2026/08/20",
+                  "meetings/2026/08/13",
+                  "meetings/2026/08/06",
+                  "meetings/2026/07/30",
+                  "meetings/2026/07/23",
+                  "meetings/2026/07/16/protocol",
+                  "meetings/2026/07/16",
+                  "meetings/2026/07/09",
+                  "meetings/2026/07/02",
+                  "meetings/2026/06/25",
+                  "meetings/2026/06/18",
+                  "meetings/2026/06/11",
+                  "meetings/2026/05/21",
+                  "meetings/2026/05/14",
+                  "meetings/2026/05/07",
+                  "meetings/2026/04/30",
+                  "meetings/2026/04/23",
+                  "meetings/2026/04/16",
+                  "meetings/2026/02/26",
+                  "meetings/2026/01/29",
+                  "meetings/2026/01/22"
+                ]
+              },
+              {
+                "group": "2025",
+                "pages": [
+                  "meetings/2025/11/06",
+                  "meetings/2025/10/30",
+                  "meetings/2025/10/23",
+                  "meetings/2025/10/16",
+                  "meetings/2025/10/09",
+                  "meetings/2025/10/02",
+                  "meetings/2025/09/25",
+                  "meetings/2025/08/07",
+                  "meetings/2025/07/24",
+                  "meetings/2025/07/17",
+                  "meetings/2025/07/10",
+                  "meetings/2025/05/22",
+                  "meetings/2025/05/01",
+                  "meetings/2025/04/17",
+                  "meetings/2025/04/10",
+                  "meetings/2025/04/03",
+                  "meetings/2025/03/27",
+                  "meetings/2025/03/06",
+                  "meetings/2025/02/27",
+                  "meetings/2025/02/20",
+                  "meetings/2025/02/13",
+                  "meetings/2025/02/06",
+                  "meetings/2025/01/30",
+                  "meetings/2025/01/23",
+                  "meetings/2025/01/16"
+                ]
+              },
+              {
+                "group": "2024",
+                "pages": [
+                  "meetings/2024/12/19",
+                  "meetings/2024/12/12",
+                  "meetings/2024/12/05",
+                  "meetings/2024/11/14",
+                  "meetings/2024/10/24",
+                  "meetings/2024/09/26",
+                  "meetings/2024/09/19",
+                  "meetings/2024/09/12",
+                  "meetings/2024/09/05",
+                  "meetings/2024/08/29",
+                  "meetings/2024/08/22",
+                  "meetings/2024/08/15",
+                  "meetings/2024/08/08",
+                  "meetings/2024/08/01",
+                  "meetings/2024/07/25",
+                  "meetings/2024/07/18",
+                  "meetings/2024/07/11",
+                  "meetings/2024/06/27",
+                  "meetings/2024/06/20",
+                  "meetings/2024/06/13",
+                  "meetings/2024/05/09",
+                  "meetings/2024/05/02",
+                  "meetings/2024/04/25",
+                  "meetings/2024/04/18",
+                  "meetings/2024/04/11",
+                  "meetings/2024/04/04",
+                  "meetings/2024/03/28",
+                  "meetings/2024/03/21",
+                  "meetings/2024/03/14",
+                  "meetings/2024/03/07",
+                  "meetings/2024/02/29",
+                  "meetings/2024/02/22",
+                  "meetings/2024/02/15",
+                  "meetings/2024/02/08",
+                  "meetings/2024/02/01",
+                  "meetings/2024/01/26",
+                  "meetings/2024/01/18"
+                ]
+              }
+            ]
+          }
+        ]
+      }
+    ],
+    "global": {
+      "anchors": [
+        {
+          "anchor": "Community",
+          "href": "https://stellar.org/community",
+          "icon": "users"
+        },
+        {
+          "anchor": "Blog",
+          "href": "https://stellar.org/blog",
+          "icon": "newspaper"
+        },
+        {
+          "anchor": "Discord",
+          "href": "https://discord.com/invite/zVYdY3ktTn",
+          "icon": "discord"
+        },
+        {
+          "anchor": "X",
+          "href": "https://twitter.com/StellarOrg",
+          "icon": "x-twitter"
+        },
+        {
+          "anchor": "YouTube",
+          "href": "https://www.youtube.com/@StellarDevelopmentFoundation",
+          "icon": "youtube"
+        }
+      ]
+    }
+  },
+  "logo": {
+    "light": "/logo/light.svg",
+    "dark": "/logo/dark.svg",
+    "href": "https://developers.stellar.org"
+  },
+  "navbar": {
+    "primary": {
+      "type": "button",
+      "label": "For agents",
+      "href": "#for-agents"
+    }
+  },
+  "contextual": {
+    "options": [
+      "copy",
+      "view",
+      "assistant",
+      "chatgpt",
+      "claude",
+      "perplexity",
+      "grok",
+      "aistudio",
+      "devin",
+      "windsurf",
+      "mcp",
+      "cursor",
+      "vscode",
+      "devin-mcp",
+      "download-spec"
+    ]
+  },
+  "integrations": {
+    "gtm": { "tagId": "GTM-M2JLH37" }
+  },
+  "redirects": { "$ref": "redirects.json" }
+}
diff --git a/docs/README.mdx b/docs/README.mdx
deleted file mode 100644
index 62af02b8d..000000000
--- a/docs/README.mdx
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Stellar Developer Docs
-displayed_sidebar: build
-hide_table_of_contents: true
-hide_sidebar: true
----
-
-## Navigating the docs
-
-### [Build](./build/README.mdx)
-
-Contains tutorials and how-to guides for writing smart contracts, building applications, interacting with the network, and more.
-
-### [Learn](./learn/fundamentals/README.mdx)
-
-Find all informational and conceptual content here. Learn about Stellar fundamentals like how accounts and transactions function, dive deeper into the functionality of each operation, discover how fees work, and more.
-
-### [Tokens](./tokens/README.mdx)
-
-Information on how to issue assets on the Stellar network and create contract tokens.
-
-### [Data](./data/README.mdx)
-
-Discover various data availability options: RPC, Hubble, Galexie, the Ingest SDK, and Horizon (nearing end-of-life).
-
-### [Tools](./tools/README.mdx)
-
-Learn about all the available tools at your disposal for building on, interacting with, or just watching the Stellar network. Also, find information on how to use the Anchor Platform or Stellar Disbursement Platform.
-
-### [Networks](./networks/README.mdx)
-
-Information about deployed networks (Mainnet, Testnet, and Futurenet), current software versions, and resource limitations and fees.
-
-### [Validators](./validators/README.mdx)
-
-Everything you'll need to know if you want to run, operate, and maintain a core validator node on the Stellar network.
diff --git a/docs/build/README.mdx b/docs/build/README.mdx
deleted file mode 100644
index 9a30445bb..000000000
--- a/docs/build/README.mdx
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: "Get Started with Blockchain Development; Guides, Tutorials & Tools"
-sidebar_label: Introduction
-icon: "house"
-sidebar_position: 0
-hide_table_of_contents: false
-description: "Get started with developing on the Stellar with guides, tutorials, tools, and resources. Learn how to write smart contracts, build applications, and more."
----
-
-# Introduction
-
-The Build section is split into three parts:
-
-1. [Smart contracts](./smart-contracts/README.mdx)
-2. [Applications](./apps/README.mdx)
-3. [How-to guides](./guides/README.mdx)
-
-Explanations for each section are stated below:
-
-## Smart contracts
-
-Smart contracts are self-executing programs with the terms of an agreement written directly into the code. They automatically enforce and execute the terms of the contract when predefined conditions are met. Once written and tested, smart contracts are deployed to the blockchain, where they become immutable and publicly accessible.
-
-:::tip
-
-While defining the rules and logic of the contract, developers must be security conscious to avoid vulnerabilities such as integer overflows, access control flaws, and other exploits that could compromise the integrity and functionality of the smart contract.
-
-:::
-
-This section will walk you through how to write and deploy smart contracts on Stellar, including the installation process, an introduction to testing, storing data, and more. It also provides a variety of example contracts for reference and use.
-
-## Applications
-
-Applications interact with the blockchain and can use smart contracts as the backend.
-
-They:
-
-- Provide user interfaces (UI);
-- Manage user interactions;
-- Integrate with smart contracts to operate.
-
-Writing **smart contracts** focuses on the backend logic and rules enforced on the blockchain, while **building applications** involves creating the frontend and integrating it with these smart contracts to provide a complete user experience.
-
-:::note
-
-You can create applications on Stellar without using smart contracts, as demonstrated in the [Wallet SDK tutorial](./apps/wallet/overview.mdx) or the [JS SDK Payment Application tutorial](./apps/example-application-tutorial/overview.mdx).
-
-:::
-
-This section walks you through design considerations for applications and tutorials for building applications with or without smart contracts.
-
-## How-to guides
-
-This section provides step-by-step instructions to help users complete specific tasks associated with building on Stellar. These tasks can include instructions for aspects of writing contracts, interacting with contracts, building applications, using Stellar operations, setting up infrastructure, and more.
-
-:::note
-
-How-to guides assume that the user has some experience and knowledge with building on Stellar and are not typically for beginners.
-
-:::
diff --git a/docs/build/agentic-payments/README.mdx b/docs/build/agentic-payments/README.mdx
deleted file mode 100644
index 673771682..000000000
--- a/docs/build/agentic-payments/README.mdx
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: "Agentic Payments: HTTP-Native Payment Protocols for AI Agents and APIs"
-sidebar_label: Agentic Payments
-description: "Build payment-enabled APIs and AI agents on Stellar using HTTP-native payment protocols like x402 and MPP."
-sidebar_position: 0
-keywords:
-  [
-    agentic payments,
-    AI payments,
-    AI agents,
-    x402,
-    MPP,
-    machine payments,
-    HTTP payments,
-    402,
-  ]
----
-
-# Agentic Payments
-
-import DocCardList from "@theme/DocCardList";
-
-Agentic payments enable programmatic, per-request payments over HTTP — designed for AI agents, APIs, and machine-to-machine interactions. These protocols extend the `402 Payment Required` HTTP status code into a machine-readable payment negotiation layer, allowing clients to pay for API requests natively on Stellar.
-
-- **[x402 on Stellar](./x402/README.mdx)** — An open protocol from the Coinbase Developer Platform for per-request payments using Soroban authorization entries, with facilitator-based verification and settlement.
-- **[MPP on Stellar](./mpp/README.mdx)** — The Machine Payments Protocol for direct on-chain settlement via Soroban SAC transfers, with support for both one-time charge payments and high-frequency off-chain payment channels.
-
-<DocCardList />
diff --git a/docs/build/agentic-payments/_category_.json b/docs/build/agentic-payments/_category_.json
deleted file mode 100644
index 9bff4e22c..000000000
--- a/docs/build/agentic-payments/_category_.json
+++ /dev/null
@@ -1,9 +0,0 @@
-{
-  "label": "Agentic Payments",
-  "collapsed": false,
-  "position": 35,
-  "link": {
-    "type": "doc",
-    "id": "build/agentic-payments/README"
-  }
-}
diff --git a/docs/build/agentic-payments/index.mdx b/docs/build/agentic-payments/index.mdx
new file mode 100644
index 000000000..7e556597b
--- /dev/null
+++ b/docs/build/agentic-payments/index.mdx
@@ -0,0 +1,34 @@
+---
+title: Agentic Payments
+"og:title": "Agentic Payments: HTTP-Native Payment Protocols for AI Agents and APIs"
+description: "Build payment-enabled APIs and AI agents on Stellar using HTTP-native payment protocols like x402 and MPP."
+keywords:
+  [
+    agentic payments,
+    AI payments,
+    AI agents,
+    x402,
+    MPP,
+    machine payments,
+    HTTP payments,
+    402,
+  ]
+---
+
+Agentic payments enable programmatic, per-request payments over HTTP — designed for AI agents, APIs, and machine-to-machine interactions. These protocols extend the `402 Payment Required` HTTP status code into a machine-readable payment negotiation layer, allowing clients to pay for API requests natively on Stellar.
+
+- **[x402 on Stellar](/docs/build/agentic-payments/x402)** — An open protocol from the Coinbase Developer Platform for per-request payments using Soroban authorization entries, with facilitator-based verification and settlement.
+- **[MPP on Stellar](/docs/build/agentic-payments/mpp)** — The Machine Payments Protocol for direct on-chain settlement via Soroban SAC transfers, with support for both one-time charge payments and high-frequency off-chain payment channels.
+
+<CardGroup cols={2}>
+  <Card title="x402 on Stellar" icon="box-archive" href="/docs/build/agentic-payments/x402">
+
+    2 items
+
+  </Card>
+  <Card title="MPP on Stellar" icon="box-archive" href="/docs/build/agentic-payments/mpp">
+
+    2 items
+
+  </Card>
+</CardGroup>
diff --git a/docs/build/agentic-payments/mpp/README.mdx b/docs/build/agentic-payments/mpp/README.mdx
deleted file mode 100644
index 388766887..000000000
--- a/docs/build/agentic-payments/mpp/README.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-title: MPP on Stellar
-sidebar_position: 0
-sidebar_label: MPP on Stellar
-description: "Use the Machine Payments Protocol (MPP) for per-request HTTP payments on Stellar, with support for AI agents, APIs, and off-chain payment channels."
-keywords:
-  [
-    MPP,
-    machine payments protocol,
-    machine payments,
-    mppx,
-    stellar mpp,
-    "@stellar/mpp",
-    payment channels,
-    AI agents,
-    402,
-    HTTP payments,
-  ]
----
-
-## What is MPP?
-
-The [Machine Payments Protocol (MPP)](https://mpp.dev) is an open protocol that enables programmatic, per-request payments over HTTP, designed especially for AI agents and APIs. It extends the `402 Payment Required` HTTP status code into a machine-readable payment negotiation layer for both humans and autonomous agents.
-
-On Stellar, MPP works with Soroban SAC (Stellar Asset Contract) token transfers so that clients can pay for API requests natively, without an external facilitator. This makes it ideal for micropayments, AI agent-driven APIs, and payment-enabled applications.
-
-## Supported MPP Intents
-
-The `@stellar/mpp` SDK supports two payment intents:
-
-### [Charge](https://mpp.dev/intents/charge)
-
-Immediate one-time payments. Each request triggers a Soroban SAC `transfer` settled on-chain individually. This is the simplest intent — no channel setup or pre-funding required.
-
-Two credential modes are available:
-
-- **Pull** (default) — The client prepares and signs the Soroban authorization entries; the server broadcasts the transaction. Supports an optional sponsored path where the server rebuilds the transaction with its own account as source, so the client never pays network fees.
-- **Push** — The client broadcasts the transaction itself and sends a `signedHash` credential for server verification — the transaction hash plus a signature proving the client controls the paying (`from`) account.
-
-See the [MPP Charge Guide](./charge-guide.mdx) to get started.
-
-### Session
-
-The session intent enables high-frequency, pay-as-you-go payments over unidirectional [payment channels](https://github.com/stellar-experimental/one-way-channel). The funder deposits tokens into the channel once, then makes many off-chain payments by signing cumulative commitments — no per-payment on-chain transactions, ideal for AI agent interactions. The server settles by closing the channel when convenient.
-
-See the [MPP Session Guide](./channel-guide.mdx) to get started.
-
-## Demo
-
-Try the live demo at [mpp.stellar.buzz](https://mpp.stellar.buzz), or run the [MPP Demo](https://github.com/stellar/stellar-mpp-sdk/tree/main/demo) locally. It runs a Node.js server that charges 0.01 USDC per request and a minimal browser UI for testing end-to-end payment flows on Stellar Testnet.
-
-To build an MPP-enabled service or integrate payments into your app, see [Build Applications](../../apps/README.mdx) and the resources below.
-
-## Install
-
-```bash
-npm install @stellar/mpp mppx @stellar/stellar-sdk
-```
-
-## Examples
-
-- **@stellar/mpp (GitHub)** — SDK source code, examples, and integration tests. [View on GitHub](https://github.com/stellar/stellar-mpp-sdk)
-- **Server example** — A minimal Node.js HTTP server charging 0.01 USDC per request using `@stellar/mpp/charge/server`. [View on GitHub](https://github.com/stellar/stellar-mpp-sdk/blob/main/examples/charge-server.ts)
-- **Client example** — A Node.js client that automatically handles 402 responses using `@stellar/mpp/charge/client`. [View on GitHub](https://github.com/stellar/stellar-mpp-sdk/blob/main/examples/charge-client.ts)
-
-## Learn more
-
-- [MPP Specification](https://mpp.dev) — Official MPP protocol specification
-- [@stellar/mpp (npm)](https://www.npmjs.com/package/@stellar/mpp) — npm package for MPP on Stellar
-- [mppx (npm)](https://www.npmjs.com/package/mppx) — Core MPP framework library
-- [one-way-channel contract](https://github.com/stellar-experimental/one-way-channel) — Soroban contract powering channel mode
-- [Signing Soroban invocations](../../guides/transactions/signing-soroban-invocations.mdx) — Auth-entry signing and transaction signing on Stellar
diff --git a/docs/build/agentic-payments/mpp/_category_.json b/docs/build/agentic-payments/mpp/_category_.json
deleted file mode 100644
index 5b7ae0833..000000000
--- a/docs/build/agentic-payments/mpp/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
-  "collapsed": false,
-  "position": 20
-}
diff --git a/docs/build/agentic-payments/mpp/channel-guide.mdx b/docs/build/agentic-payments/mpp/channel-guide.mdx
index 1f4e0631b..d7cd74f51 100644
--- a/docs/build/agentic-payments/mpp/channel-guide.mdx
+++ b/docs/build/agentic-payments/mpp/channel-guide.mdx
@@ -1,7 +1,6 @@
 ---
 title: MPP Session Guide
 description: Set up session-based off-chain payments for high-frequency use on Stellar using the Machine Payments Protocol (MPP).
-sidebar_position: 30
 ---
 
 This guide explains how to use the MPP **session** intent with `@stellar/mpp`. The session intent is implemented using a [one-way payment channel](https://github.com/stellar-experimental/one-way-channel) Soroban contract — the funder deposits tokens once, then makes many off-chain payments by signing cumulative commitments. No on-chain transaction is needed per payment, making this ideal for high-frequency AI agent interactions.
@@ -315,5 +314,5 @@ Channel mode uses separate subpath exports to avoid bundling unused code:
 
 - [one-way-channel contract](https://github.com/stellar-experimental/one-way-channel) — Soroban contract, deployment scripts, and parameters
 - [@stellar/mpp on GitHub](https://github.com/stellar/stellar-mpp-sdk) — Full API reference and integration tests
-- [MPP Charge Guide](./charge-guide.mdx) — Charge mode (per-request on-chain settlement)
+- [MPP Charge Guide](./charge-guide) — Charge mode (per-request on-chain settlement)
 - [MPP Specification](https://mpp.dev) — Protocol specification
diff --git a/docs/build/agentic-payments/mpp/charge-guide.mdx b/docs/build/agentic-payments/mpp/charge-guide.mdx
index 38d0376f6..4a6e974cf 100644
--- a/docs/build/agentic-payments/mpp/charge-guide.mdx
+++ b/docs/build/agentic-payments/mpp/charge-guide.mdx
@@ -1,7 +1,6 @@
 ---
 title: MPP Charge Guide
 description: Build a paid API with Node.js and Stellar settlement using the Machine Payments Protocol (MPP).
-sidebar_position: 10
 ---
 
 The [**charge** intent](https://mpp.dev/intents/charge) is for immediate, one-time payments. Each API request triggers a Soroban SAC `transfer` that settles on-chain individually — no channel setup, no pre-funding, and no external facilitator required. This is the simplest way to get started with MPP on Stellar.
@@ -70,7 +69,7 @@ Install the npm packages used by the server and client:
 npm install express @stellar/mpp mppx @stellar/stellar-sdk
 ```
 
-## Create `server.js`
+## Create `server.js` {#create-serverjs}
 
 Create a file named `server.js` and paste in the following code:
 
@@ -164,7 +163,7 @@ STELLAR_RECIPIENT=GYOUR_PUBLIC_KEY MPP_SECRET_KEY=replace-me node server.js
 
 When a client requests your endpoint, the server responds with `402 Payment Required`, including headers that describe the payment requirements. A compliant client builds a signed Soroban SAC transfer and retries the request — no external facilitator needed. The server verifies and broadcasts the transaction directly.
 
-## Create `client.js`
+## Create `client.js` {#create-clientjs}
 
 ### Setting up a testnet wallet
 
@@ -181,11 +180,11 @@ Create a `.env` file and add your testnet secret key:
 STELLAR_SECRET=S...
 ```
 
-:::caution
+<Warning>
 
 Secret keys provide full access to any digital assets held in the wallet. Use `.env` files only for hot wallets in testnet deployments.
 
-:::
+</Warning>
 
 ### Client code
 
@@ -438,11 +437,13 @@ Set `FEE_PAYER_SECRET` before running the server if you use sponsored fees.
 
 When `feePayer` is configured, the server automatically signals fee sponsorship to the client via the challenge. The client then signs only the Soroban auth entries (not the full transaction envelope). The server rebuilds the transaction with the `envelopeSigner`'s account as source and broadcasts it. Optionally, add `feeBumpSigner` inside `feePayer` to wrap the transaction in a fee bump.
 
-:::info[Channel open removal]
+<Info>
 
-The channel `open` MPP action was removed in v0.7 as it was dead code — the Soroban contract has no on-chain open entrypoint. Channels are created on-chain directly by signing and broadcasting a deploy transaction. See the [MPP Session Guide](./channel-guide.mdx) for channel setup details.
+**Channel open removal**
 
-:::
+The channel `open` MPP action was removed in v0.7 as it was dead code — the Soroban contract has no on-chain open entrypoint. Channels are created on-chain directly by signing and broadcasting a deploy transaction. See the [MPP Session Guide](./channel-guide) for channel setup details.
+
+</Info>
 
 ## Learn more
 
@@ -450,6 +451,6 @@ The channel `open` MPP action was removed in v0.7 as it was dead code — the So
 - [@stellar/mpp (npm)](https://www.npmjs.com/package/@stellar/mpp) — npm package for MPP on Stellar
 - [MPP Specification](https://mpp.dev) — Official MPP protocol specification and whitepaper
 - [mppx (npm)](https://www.npmjs.com/package/mppx) — Core MPP framework library used by both server and client
-- [Signing Soroban invocations](../../guides/transactions/signing-soroban-invocations.mdx) — Auth-entry signing on Stellar
+- [Signing Soroban invocations](../../guides/transactions/signing-soroban-invocations) — Auth-entry signing on Stellar
 - [one-way-channel contract](https://github.com/stellar-experimental/one-way-channel) — Soroban contract powering the channel payment mode
-- [MPP Session Guide](./channel-guide.mdx) — Set up off-chain payment channels for high-frequency payments
+- [MPP Session Guide](./channel-guide) — Set up off-chain payment channels for high-frequency payments
diff --git a/docs/build/agentic-payments/mpp/index.mdx b/docs/build/agentic-payments/mpp/index.mdx
new file mode 100644
index 000000000..11f8fc855
--- /dev/null
+++ b/docs/build/agentic-payments/mpp/index.mdx
@@ -0,0 +1,70 @@
+---
+title: MPP on Stellar
+description: "Use the Machine Payments Protocol (MPP) for per-request HTTP payments on Stellar, with support for AI agents, APIs, and off-chain payment channels."
+keywords:
+  [
+    MPP,
+    machine payments protocol,
+    machine payments,
+    mppx,
+    stellar mpp,
+    "@stellar/mpp",
+    payment channels,
+    AI agents,
+    402,
+    HTTP payments,
+  ]
+---
+
+## What is MPP?
+
+The [Machine Payments Protocol (MPP)](https://mpp.dev) is an open protocol that enables programmatic, per-request payments over HTTP, designed especially for AI agents and APIs. It extends the `402 Payment Required` HTTP status code into a machine-readable payment negotiation layer for both humans and autonomous agents.
+
+On Stellar, MPP works with Soroban SAC (Stellar Asset Contract) token transfers so that clients can pay for API requests natively, without an external facilitator. This makes it ideal for micropayments, AI agent-driven APIs, and payment-enabled applications.
+
+## Supported MPP Intents
+
+The `@stellar/mpp` SDK supports two payment intents:
+
+### [Charge](https://mpp.dev/intents/charge)
+
+Immediate one-time payments. Each request triggers a Soroban SAC `transfer` settled on-chain individually. This is the simplest intent — no channel setup or pre-funding required.
+
+Two credential modes are available:
+
+- **Pull** (default) — The client prepares and signs the Soroban authorization entries; the server broadcasts the transaction. Supports an optional sponsored path where the server rebuilds the transaction with its own account as source, so the client never pays network fees.
+- **Push** — The client broadcasts the transaction itself and sends a `signedHash` credential for server verification — the transaction hash plus a signature proving the client controls the paying (`from`) account.
+
+See the [MPP Charge Guide](/docs/build/agentic-payments/mpp/charge-guide) to get started.
+
+### Session
+
+The session intent enables high-frequency, pay-as-you-go payments over unidirectional [payment channels](https://github.com/stellar-experimental/one-way-channel). The funder deposits tokens into the channel once, then makes many off-chain payments by signing cumulative commitments — no per-payment on-chain transactions, ideal for AI agent interactions. The server settles by closing the channel when convenient.
+
+See the [MPP Session Guide](/docs/build/agentic-payments/mpp/channel-guide) to get started.
+
+## Demo
+
+Try the live demo at [mpp.stellar.buzz](https://mpp.stellar.buzz), or run the [MPP Demo](https://github.com/stellar/stellar-mpp-sdk/tree/main/demo) locally. It runs a Node.js server that charges 0.01 USDC per request and a minimal browser UI for testing end-to-end payment flows on Stellar Testnet.
+
+To build an MPP-enabled service or integrate payments into your app, see [Build Applications](/docs/build/apps) and the resources below.
+
+## Install
+
+```bash
+npm install @stellar/mpp mppx @stellar/stellar-sdk
+```
+
+## Examples
+
+- **@stellar/mpp (GitHub)** — SDK source code, examples, and integration tests. [View on GitHub](https://github.com/stellar/stellar-mpp-sdk)
+- **Server example** — A minimal Node.js HTTP server charging 0.01 USDC per request using `@stellar/mpp/charge/server`. [View on GitHub](https://github.com/stellar/stellar-mpp-sdk/blob/main/examples/charge-server.ts)
+- **Client example** — A Node.js client that automatically handles 402 responses using `@stellar/mpp/charge/client`. [View on GitHub](https://github.com/stellar/stellar-mpp-sdk/blob/main/examples/charge-client.ts)
+
+## Learn more
+
+- [MPP Specification](https://mpp.dev) — Official MPP protocol specification
+- [@stellar/mpp (npm)](https://www.npmjs.com/package/@stellar/mpp) — npm package for MPP on Stellar
+- [mppx (npm)](https://www.npmjs.com/package/mppx) — Core MPP framework library
+- [one-way-channel contract](https://github.com/stellar-experimental/one-way-channel) — Soroban contract powering channel mode
+- [Signing Soroban invocations](/docs/build/guides/transactions/signing-soroban-invocations) — Auth-entry signing and transaction signing on Stellar
diff --git a/docs/build/agentic-payments/x402/README.mdx b/docs/build/agentic-payments/x402/README.mdx
deleted file mode 100644
index 5be143dd6..000000000
--- a/docs/build/agentic-payments/x402/README.mdx
+++ /dev/null
@@ -1,138 +0,0 @@
----
-title: x402 on Stellar
-sidebar_position: 0
-sidebar_label: x402 on Stellar
-description: "Use the x402 protocol for per-request HTTP payments on Stellar, with support for AI agents and APIs."
-keywords:
-  [x402, HTTP payments, 402, AI agents, agentic payments, machine payments]
----
-
-## What is x402?
-
-x402 is an open protocol from the Coinbase Developer Platform that enables programmatic, per request payments over HTTP, designed especially for AI agents and APIs. It effectively turns the old “402 Payment Required” HTTP status code into something usable, for both humans and AI agents.
-
-On Stellar, x402 works with Soroban authorization so that clients can pay for API requests via signed auth entries, ideal for micropayments and payment enabled apps. To build an x402-enabled service or integrate payments into your app, see [Build Applications](../../apps/README.mdx) and the resources below.
-
-## Demo
-
-Try the [x402 Demo](https://stellar.org/x402-demo). Send an x402 payment on Stellar Testnet or Mainnet and see the x402 payment flow in action. ([source code](https://github.com/stellar/x402-stellar))
-
-[![Screenshot of the x402 payment flow demo on Stellar](/assets/guides/x402-demo.png)](https://stellar.org/x402-demo)
-
-## x402 Compatible Wallets
-
-To support x402 on Stellar, a wallet must support [auth-entry signing](../../guides/transactions/signing-soroban-invocations.mdx#method-2-auth-entry-signing) (Soroban authorization entry signing). The following wallets support auth-entry signing:
-
-- Freighter Browser Extension
-- Albedo
-- Hana
-- HOT
-- Klever
-- OneKey
-- Scopuly
-
-:::note
-
-Freighter Mobile does not currently support x402; use the Freighter browser extension. Mobile support is planned for a future release.
-
-:::
-
-## Supported Assets
-
-x402 on Stellar supports any [SEP-41](https://stellar.org/protocol/sep-41) compliant token. The default is USDC.
-
-### Testnet USDC
-
-| Property        | Value                                                      |
-| --------------- | ---------------------------------------------------------- |
-| Asset Code      | `USDC`                                                     |
-| Issuer          | `GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5` |
-| SEP-41 Contract | `CBIELTK6YBZJU5UP2WWQEUCYKLPU6AUNZ2BQ4WWFEIE3USCIHMXQDAMA` |
-
-### Mainnet USDC
-
-| Property        | Value                                                      |
-| --------------- | ---------------------------------------------------------- |
-| Asset Code      | `USDC`                                                     |
-| Issuer          | `GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN` |
-| SEP-41 Contract | `CCW67TSZV3SSS2HXMBQ5JFGCKJNXKZM7UQUWUZPUTHXSTZLEO7SJMI75` |
-
-## x402 Facilitators
-
-You can use a facilitator to verify and settle x402 payments. The following options are available for Stellar:
-
-### Coinbase x402 Facilitator
-
-Coinbase’s x402 facilitator supports Stellar on **Testnet** with sponsored fees. Check which networks and options are supported:
-
-- **[x402 Facilitator Supported Networks](https://www.x402.org/facilitator/supported)** — Lists supported networks (including `stellar:testnet`) and facilitator configuration.
-
-### Build on Stellar Relayer (with OpenZeppelin x402 Plugin)
-
-The [Relayer Plugin for x402](https://github.com/OpenZeppelin/relayer-plugin-x402-facilitator) implements the x402 Facilitator API so you can serve x402 payments directly from a Relayer instance. The x402 Facilitator leverages the OpenZeppelin Relayer Framework. It works with the [Coinbase x402](https://github.com/coinbase/x402) ecosystem and exposes the expected `/verify`, `/settle`, and `/supported` endpoints under the Relayer plugin router.
-
-#### How to Use
-
-This x402 facilitator service is available on Testnet and Mainnet. Under the hood, the plugin leverages OpenZeppelin Channels to submit transactions onchain via a managed Relayer and Facilitator setup.
-
-#### Testnet
-
-To use the facilitator on testnet, you will need:
-
-- An API Key (Relayer Service). Generate your testnet API key here: https://channels.openzeppelin.com/testnet/gen
-- Facilitator URL. Use the following facilitator endpoint in your configuration: `https://channels.openzeppelin.com/x402/testnet`
-
-#### Mainnet
-
-To use the Facilitator on mainnet, you will need:
-
-- An API Key (Relayer Service). Generate your mainnet API key here: https://channels.openzeppelin.com/gen
-- Facilitator URL. Use the following facilitator endpoint in your configuration: `https://channels.openzeppelin.com/x402`
-
-:::note
-
-This version supports x402 v2 specification. For x402 v1 support, please use a previous version of this plugin (check git history for v1 compatible releases).
-
-:::
-
-### Community Facilitators
-
-The following facilitators are built and operated by the community. They are not maintained by SDF and are at varying stages of readiness, so check each project's current status before depending on it.
-
-#### Vellar Facilitator
-
-[Vellar](https://github.com/Vellar-Wallet/vellar-facilitator) serves the standard `/verify`, `/settle`, and `/supported` endpoints, and adds an optional Bazaar discovery layer: when a payment settles and carries Vellar's discovery extension, the facilitator may also add that resource to a searchable catalog, so sellers are listed without registering separately. Cataloging is best-effort and never blocks settlement, and payments without the extension settle as normal. The catalog can also be queried by AI agents through an [MCP](https://modelcontextprotocol.io) discovery server, which you run yourself and point at a facilitator. Vellar sponsors the settlement transaction fee, though classic accounts still fund their own base and trustline reserves.
-
-- **Source**: https://github.com/Vellar-Wallet/vellar-facilitator
-- **Docs**: https://docs.vellar.xyz
-
-:::note
-
-Testnet only, and not independently audited. See [Vellar's security notes](https://docs.vellar.xyz) for more information. The hosted instance runs on a free tier, so the first request after an idle period can take up to a minute.
-
-:::
-
-## Examples
-
-- **x402 on Stellar (Stellar repo)** — Tools, examples, and references for the x402 protocol on Stellar. Use this as the canonical source for Stellar-specific x402 demos and tooling. [View on GitHub](https://github.com/stellar/x402-stellar)
-- **x402 Starter Template** — A starter template for building payment-enabled applications with x402. Simplified scaffolding demonstrating x402 payment protocol integration with browser wallet support; use it as a foundation for micropayment-enabled services, SaaS applications, or any project that needs frictionless web payments. [View on GitHub](https://github.com/ElliotFriend/x402/tree/stellar-browser-wallet-example/examples/typescript/fullstack/browser-wallet-example)
-- **Economic Load Balancer** — An intelligent multi-chain payment router that automatically selects the most cost-efficient network for high-frequency AI agent micropayments. [View on GitHub](https://github.com/marcelosalloum/x402/tree/x402-hackathon)
-- **1-shot Stellar x402 app** — Example x402 app with a video paywall and guide for building payment-enabled apps on Stellar. [View on GitHub](https://github.com/oceans404/1-shot-stellar/tree/main/x402-app)
-
-## Additional Documentation
-
-- [OpenZeppelin x402 Facilitator Plugin Source Code](https://github.com/OpenZeppelin/relayer-plugin-x402-facilitator)
-- [OpenZeppelin x402 Facilitator Docs](https://docs.openzeppelin.com/relayer/1.4.x/guides/stellar-x402-facilitator-guide)
-- [OpenZeppelin Stellar Relayer SDK](https://github.com/OpenZeppelin/openzeppelin-relayer-sdk)
-- [OpenZeppelin Stellar Relayer Docs](https://docs.openzeppelin.com/relayer/1.4.x)
-- [OpenZeppelin Smart Account](https://docs.openzeppelin.com/stellar-contracts/accounts/smart-account)
-
-## Learn more
-
-- [x402 on Stellar (Landing page)](https://stellar.org/x402) — Stellar x402 overview and resources
-- [x402 on Stellar (Blog)](https://stellar.org/blog/foundation-news/x402-on-stellar) — Foundation news and announcement
-- [x402 protocol (Coinbase Developer Platform)](https://docs.cdp.coinbase.com/x402) — Official x402 protocol overview and spec
-- [x402 protocol specification](https://www.x402.org) — x402 Specification and Whitepaper
-- [Coinbase x402 GitHub](https://github.com/coinbase/x402) — Official x402 Protocol GitHub Repo
-- [x402-stellar (npm)](https://www.npmjs.com/package/x402-stellar) — npm package for x402 on Stellar
-- [Signing Soroban invocations](../../guides/transactions/signing-soroban-invocations.mdx) — Auth-entry signing and transaction signing on Stellar
diff --git a/docs/build/agentic-payments/x402/_category_.json b/docs/build/agentic-payments/x402/_category_.json
deleted file mode 100644
index 2d0269b1e..000000000
--- a/docs/build/agentic-payments/x402/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
-  "collapsed": false,
-  "position": 10
-}
diff --git a/docs/build/agentic-payments/x402/built-on-stellar.mdx b/docs/build/agentic-payments/x402/built-on-stellar.mdx
index 21acb6b4d..b5a2bc24b 100644
--- a/docs/build/agentic-payments/x402/built-on-stellar.mdx
+++ b/docs/build/agentic-payments/x402/built-on-stellar.mdx
@@ -1,7 +1,6 @@
 ---
 title: Built on Stellar x402 Facilitator
-sidebar_position: 10
-sidebar_label: Built on Stellar Facilitator
+sidebarTitle: Built on Stellar Facilitator
 description: "Free, public x402 facilitator for Stellar with ~5-second finality and sponsored fees. Full verification and settlement flow powered by the OpenZeppelin Relayer."
 keywords:
   [
@@ -15,7 +14,7 @@ keywords:
   ]
 ---
 
-The **Built on Stellar** x402 Facilitator is a production-ready payment facilitator for the [x402 protocol](./README.mdx) on Stellar. It handles payment verification and settlement so that sellers can accept per-request payments without running their own blockchain infrastructure.
+The **Built on Stellar** x402 Facilitator is a production-ready payment facilitator for the [x402 protocol](/docs/build/agentic-payments/x402) on Stellar. It handles payment verification and settlement so that sellers can accept per-request payments without running their own blockchain infrastructure.
 
 Built with the [OpenZeppelin Relayer][oz-relayer] and the [x402 Facilitator Plugin][oz-plugin], it exposes the standard x402 `/verify`, `/settle`, and `/supported` endpoints and is fully compatible with the [Coinbase x402 ecosystem][x402-ecosystem].
 
@@ -172,7 +171,7 @@ This approach provides several benefits:
 - **x402 scheme**: `exact-v2`
 - **Endpoints**: `/verify`, `/settle`, `/supported`
 - **Settlement**: Managed on-chain submission via [OpenZeppelin Relayer][oz-relayer]
-- **Compatibility**: Works with all [x402 ecosystem packages][x402-ecosystem] and [Stellar x402-compatible wallets](./README.mdx#x402-compatible-wallets)
+- **Compatibility**: Works with all [x402 ecosystem packages][x402-ecosystem] and [Stellar x402-compatible wallets](/docs/build/agentic-payments/x402#x402-compatible-wallets)
 
 ## Self-hosting
 
@@ -182,7 +181,7 @@ If you want to run your own instance of the facilitator instead of using the hos
 
 - [@x402/stellar (npm)](https://www.npmjs.com/package/@x402/stellar) — npm package for x402 on Stellar
 - [x402-stellar (repo)](https://github.com/stellar/x402-stellar) — Tools, examples, and references for x402 on Stellar
-- [x402 on Stellar](./README.mdx) — Overview of the x402 protocol on Stellar
+- [x402 on Stellar](/docs/build/agentic-payments/x402) — Overview of the x402 protocol on Stellar
 - [x402 protocol specification](https://www.x402.org) — x402 specification and whitepaper
 - [OpenZeppelin x402 Facilitator Plugin][oz-plugin] — Source code
 - [OpenZeppelin x402 Facilitator Docs][oz-facilitator-guide] — Full configuration and setup guide
diff --git a/docs/build/agentic-payments/x402/index.mdx b/docs/build/agentic-payments/x402/index.mdx
new file mode 100644
index 000000000..508b7e999
--- /dev/null
+++ b/docs/build/agentic-payments/x402/index.mdx
@@ -0,0 +1,136 @@
+---
+title: x402 on Stellar
+description: "Use the x402 protocol for per-request HTTP payments on Stellar, with support for AI agents and APIs."
+keywords:
+  [x402, HTTP payments, 402, AI agents, agentic payments, machine payments]
+---
+
+## What is x402?
+
+x402 is an open protocol from the Coinbase Developer Platform that enables programmatic, per request payments over HTTP, designed especially for AI agents and APIs. It effectively turns the old “402 Payment Required” HTTP status code into something usable, for both humans and AI agents.
+
+On Stellar, x402 works with Soroban authorization so that clients can pay for API requests via signed auth entries, ideal for micropayments and payment enabled apps. To build an x402-enabled service or integrate payments into your app, see [Build Applications](/docs/build/apps) and the resources below.
+
+## Demo
+
+Try the [x402 Demo](https://stellar.org/x402-demo). Send an x402 payment on Stellar Testnet or Mainnet and see the x402 payment flow in action. ([source code](https://github.com/stellar/x402-stellar))
+
+[![Screenshot of the x402 payment flow demo on Stellar](/assets/guides/x402-demo.png)](https://stellar.org/x402-demo)
+
+## x402 Compatible Wallets
+
+To support x402 on Stellar, a wallet must support [auth-entry signing](/docs/build/guides/transactions/signing-soroban-invocations#method-2-auth-entry-signing) (Soroban authorization entry signing). The following wallets support auth-entry signing:
+
+- Freighter Browser Extension
+- Albedo
+- Hana
+- HOT
+- Klever
+- OneKey
+- Scopuly
+
+<Note>
+
+Freighter Mobile does not currently support x402; use the Freighter browser extension. Mobile support is planned for a future release.
+
+</Note>
+
+## Supported Assets
+
+x402 on Stellar supports any [SEP-41](https://stellar.org/protocol/sep-41) compliant token. The default is USDC.
+
+### Testnet USDC
+
+| Property        | Value                                                      |
+| --------------- | ---------------------------------------------------------- |
+| Asset Code      | `USDC`                                                     |
+| Issuer          | `GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5` |
+| SEP-41 Contract | `CBIELTK6YBZJU5UP2WWQEUCYKLPU6AUNZ2BQ4WWFEIE3USCIHMXQDAMA` |
+
+### Mainnet USDC
+
+| Property        | Value                                                      |
+| --------------- | ---------------------------------------------------------- |
+| Asset Code      | `USDC`                                                     |
+| Issuer          | `GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN` |
+| SEP-41 Contract | `CCW67TSZV3SSS2HXMBQ5JFGCKJNXKZM7UQUWUZPUTHXSTZLEO7SJMI75` |
+
+## x402 Facilitators
+
+You can use a facilitator to verify and settle x402 payments. Two options are available for Stellar:
+
+### Coinbase x402 Facilitator
+
+Coinbase’s x402 facilitator supports Stellar on **Testnet** with sponsored fees. Check which networks and options are supported:
+
+- **[x402 Facilitator Supported Networks](https://www.x402.org/facilitator/supported)** — Lists supported networks (including `stellar:testnet`) and facilitator configuration.
+
+### Build on Stellar Relayer (with OpenZeppelin x402 Plugin)
+
+The [Relayer Plugin for x402](https://github.com/OpenZeppelin/relayer-plugin-x402-facilitator) implements the x402 Facilitator API so you can serve x402 payments directly from a Relayer instance. The x402 Facilitator leverages the OpenZeppelin Relayer Framework. It works with the [Coinbase x402](https://github.com/coinbase/x402) ecosystem and exposes the expected `/verify`, `/settle`, and `/supported` endpoints under the Relayer plugin router.
+
+#### How to Use
+
+This x402 facilitator service is available on Testnet and Mainnet. Under the hood, the plugin leverages OpenZeppelin Channels to submit transactions onchain via a managed Relayer and Facilitator setup.
+
+#### Testnet
+
+To use the facilitator on testnet, you will need:
+
+- An API Key (Relayer Service). Generate your testnet API key here: https://channels.openzeppelin.com/testnet/gen
+- Facilitator URL. Use the following facilitator endpoint in your configuration: `https://channels.openzeppelin.com/x402/testnet`
+
+#### Mainnet
+
+To use the Facilitator on mainnet, you will need:
+
+- An API Key (Relayer Service). Generate your mainnet API key here: https://channels.openzeppelin.com/gen
+- Facilitator URL. Use the following facilitator endpoint in your configuration: `https://channels.openzeppelin.com/x402`
+
+<Note>
+
+This version supports x402 v2 specification. For x402 v1 support, please use a previous version of this plugin (check git history for v1 compatible releases).
+
+</Note>
+
+### Community Facilitators
+
+The following facilitators are built and operated by the community. They are not maintained by SDF and are at varying stages of readiness, so check each project's current status before depending on it.
+
+#### Vellar Facilitator
+
+[Vellar](https://github.com/Vellar-Wallet/vellar-facilitator) serves the standard `/verify`, `/settle`, and `/supported` endpoints, and adds an optional Bazaar discovery layer: when a payment settles and carries Vellar's discovery extension, the facilitator may also add that resource to a searchable catalog, so sellers are listed without registering separately. Cataloging is best-effort and never blocks settlement, and payments without the extension settle as normal. The catalog can also be queried by AI agents through an [MCP](https://modelcontextprotocol.io) discovery server, which you run yourself and point at a facilitator. Vellar sponsors the settlement transaction fee, though classic accounts still fund their own base and trustline reserves.
+
+- **Source**: https://github.com/Vellar-Wallet/vellar-facilitator
+- **Docs**: https://docs.vellar.xyz
+
+<Note>
+
+Testnet only, and not independently audited. See [Vellar's security notes](https://docs.vellar.xyz) for more information. The hosted instance runs on a free tier, so the first request after an idle period can take up to a minute.
+
+</Note>
+
+## Examples
+
+- **x402 on Stellar (Stellar repo)** — Tools, examples, and references for the x402 protocol on Stellar. Use this as the canonical source for Stellar-specific x402 demos and tooling. [View on GitHub](https://github.com/stellar/x402-stellar)
+- **x402 Starter Template** — A starter template for building payment-enabled applications with x402. Simplified scaffolding demonstrating x402 payment protocol integration with browser wallet support; use it as a foundation for micropayment-enabled services, SaaS applications, or any project that needs frictionless web payments. [View on GitHub](https://github.com/ElliotFriend/x402/tree/stellar-browser-wallet-example/examples/typescript/fullstack/browser-wallet-example)
+- **Economic Load Balancer** — An intelligent multi-chain payment router that automatically selects the most cost-efficient network for high-frequency AI agent micropayments. [View on GitHub](https://github.com/marcelosalloum/x402/tree/x402-hackathon)
+- **1-shot Stellar x402 app** — Example x402 app with a video paywall and guide for building payment-enabled apps on Stellar. [View on GitHub](https://github.com/oceans404/1-shot-stellar/tree/main/x402-app)
+
+## Additional Documentation
+
+- [OpenZeppelin x402 Facilitator Plugin Source Code](https://github.com/OpenZeppelin/relayer-plugin-x402-facilitator)
+- [OpenZeppelin x402 Facilitator Docs](https://docs.openzeppelin.com/relayer/1.4.x/guides/stellar-x402-facilitator-guide)
+- [OpenZeppelin Stellar Relayer SDK](https://github.com/OpenZeppelin/openzeppelin-relayer-sdk)
+- [OpenZeppelin Stellar Relayer Docs](https://docs.openzeppelin.com/relayer/1.4.x)
+- [OpenZeppelin Smart Account](https://docs.openzeppelin.com/stellar-contracts/accounts/smart-account)
+
+## Learn more
+
+- [x402 on Stellar (Landing page)](https://stellar.org/x402) — Stellar x402 overview and resources
+- [x402 on Stellar (Blog)](https://stellar.org/blog/foundation-news/x402-on-stellar) — Foundation news and announcement
+- [x402 protocol (Coinbase Developer Platform)](https://docs.cdp.coinbase.com/x402) — Official x402 protocol overview and spec
+- [x402 protocol specification](https://www.x402.org) — x402 Specification and Whitepaper
+- [Coinbase x402 GitHub](https://github.com/coinbase/x402) — Official x402 Protocol GitHub Repo
+- [x402-stellar (npm)](https://www.npmjs.com/package/x402-stellar) — npm package for x402 on Stellar
+- [Signing Soroban invocations](/docs/build/guides/transactions/signing-soroban-invocations) — Auth-entry signing and transaction signing on Stellar
diff --git a/docs/build/agentic-payments/x402/quickstart-guide.mdx b/docs/build/agentic-payments/x402/quickstart-guide.mdx
index 62557a82f..af8b842b1 100644
--- a/docs/build/agentic-payments/x402/quickstart-guide.mdx
+++ b/docs/build/agentic-payments/x402/quickstart-guide.mdx
@@ -1,7 +1,6 @@
 ---
 title: x402 Quickstart Guide
 description: Build a paid x402 API with Node.js, Express, and Stellar settlement.
-sidebar_position: 20
 keywords: [x402, x402 quickstart, x402 tutorial, 402]
 ---
 
@@ -30,7 +29,7 @@ npm install express dotenv @stellar/stellar-sdk @x402/core @x402/express @x402/f
 
 This installs everything needed for both `server.js` and `client.js`.
 
-## Create `server.js`
+## Create `server.js` {#create-serverjs}
 
 Create a file named `server.js` and paste in the following code:
 
@@ -100,7 +99,7 @@ The client generates a signed payment payload that authorizes a stablecoin trans
 
 The funds settle directly to the wallet address in `PAY_TO`.
 
-## Create `client.js`
+## Create `client.js` {#create-clientjs}
 
 With your Express server running, create a file named `client.js` and paste in the following code:
 
@@ -235,13 +234,13 @@ STELLAR_PRIVATE_KEY=S...
 
 Edit `.env` and replace `S...` with the secret key for the account that will sign transactions and pay for the resource.
 
-:::caution
+<Warning>
 
 Secret keys provide full access to any digital assets held within the wallet. Use `.env` files only for hot wallets in testnet deployments.
 
-:::
+</Warning>
 
-### Step 3 (expanded): Establish USDC trustline
+### Step 3 (expanded): Establish USDC trustline {#step-3-expanded-establish-usdc-trustline}
 
 A trustline tells Stellar your account accepts USDC. Without it, you cannot receive payments.
 
@@ -321,4 +320,4 @@ The server is set up as an MVP for machine-to-machine payments. If you want to e
 - [x402 GitHub](https://github.com/x402-foundation/x402) - Official x402 Protocol GitHub Repo
 - [@x402/stellar (npm)](https://www.npmjs.com/package/@x402/stellar) - npm package for x402 on Stellar
 - [x402-stellar (repo)](https://github.com/stellar/x402-stellar) - Tools, examples, and references for x402 on Stellar
-- [Signing Soroban invocations](../../guides/transactions/signing-soroban-invocations.mdx) - Auth-entry signing and transaction signing on Stellar
+- [Signing Soroban invocations](../../guides/transactions/signing-soroban-invocations) - Auth-entry signing and transaction signing on Stellar
diff --git a/docs/build/apps/README.mdx b/docs/build/apps/README.mdx
deleted file mode 100644
index 3029e18b1..000000000
--- a/docs/build/apps/README.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: "Build Blockchain Apps: Guides, Tools, and Best Practices for Development"
-sidebar_label: Build Applications
-description: "Learn how to build blockchain apps with guides, tools, and best practices. Explore key concepts, integration tips, and resources for development on Stellar."
-sidebar_position: 30
----
-
-# Build Applications
-
-import DocCardList from "@theme/DocCardList";
-
-This section walks you through design considerations for applications and tutorials for building applications with or without smart contracts.
-
-<DocCardList />
diff --git a/docs/build/apps/application-design-considerations.mdx b/docs/build/apps/application-design-considerations.mdx
index 4ac2ed7b1..aa5ee7f7c 100644
--- a/docs/build/apps/application-design-considerations.mdx
+++ b/docs/build/apps/application-design-considerations.mdx
@@ -1,6 +1,6 @@
 ---
 title: Application Design Considerations
-sidebar_position: 10
+description: "When building an application, one of the first things you have to decide is how your users’ secret keys will be secured and stored."
 ---
 
 ## Custody models
@@ -11,7 +11,7 @@ There are four custody options to consider:
 
 - Non-custodial service - the user of the application stores their own secret key
 - Custodial service - the service provider (application) stores the users’ secret keys
-- Mixture of both - with the use of [multisig](../../learn/fundamentals/transactions/signatures-multisig.mdx), this option is useful for maintaining non-custodial status while still allowing for account recovery
+- Mixture of both - with the use of [multisig](../../learn/fundamentals/transactions/signatures-multisig), this option is useful for maintaining non-custodial status while still allowing for account recovery
 - Third-party key management services - integrate a third-party custodial service into your application that can store your users’ secret keys
 
 ### Non-custodial service
@@ -24,13 +24,13 @@ Typically, non-custodial applications create or import a pre-existing Stellar ac
 
 With a custodial service, the service provider (an application such as a centralized exchange) stores the users’ secret keys and delegates usage rights to the user.
 
-Many custodial services choose to use a single pooled Stellar account (called shared, omnibus, or [pooled accounts](../guides/transactions/pooled-accounts-muxed-accounts-memos.mdx)) to handle transactions on behalf of their users instead of creating a new Stellar account for each user. To distinguish between individual users in a pooled account, we encourage the implementation of [muxed accounts](../guides/transactions/pooled-accounts-muxed-accounts-memos.mdx).
+Many custodial services choose to use a single pooled Stellar account (called shared, omnibus, or [pooled accounts](../guides/transactions/pooled-accounts-muxed-accounts-memos)) to handle transactions on behalf of their users instead of creating a new Stellar account for each user. To distinguish between individual users in a pooled account, we encourage the implementation of [muxed accounts](../guides/transactions/pooled-accounts-muxed-accounts-memos).
 
 ### A mixture of non-custodial and custodial
 
-Building an application with [multi-signature](../../learn/fundamentals/transactions/signatures-multisig.mdx) capabilities allows you to have a non-custodial service with account recovery. If the user loses their secret key, they can still sign transactions with other authorized signatures, granted the signature threshold is high enough.
+Building an application with [multi-signature](../../learn/fundamentals/transactions/signatures-multisig) capabilities allows you to have a non-custodial service with account recovery. If the user loses their secret key, they can still sign transactions with other authorized signatures, granted the signature threshold is high enough.
 
-### Third-party key management services​
+### Third-party key management services​ {#third-party-key-management-services}
 
 There are several apps and services that specialize in adding additional security layers to users' accounts. Check them out if you're interested in integrating a third-party key management service:
 
@@ -58,7 +58,7 @@ In this section, we will go over the new user account creation flow between non-
 
 When a new customer downloads the wallet application and goes through the deposit flow for the first time, their Stellar account can be created by either the user’s wallet application or the anchor facilitating the first deposit. This section describes each of these strategies.
 
-### Option 1: The anchor creates and funds the Stellar account​
+### Option 1: The anchor creates and funds the Stellar account​ {#option-1-the-anchor-creates-and-funds-the-stellar-account}
 
 For this option, the wallet needs to allow users to initiate their first deposit without having to add an asset/establish a trustline. The wallet then prompts the user to add the trustline once funds are received by the anchor. The flow looks like this:
 
@@ -71,11 +71,11 @@ For this option, the wallet needs to allow users to initiate their first deposit
 7. The wallet prompts the user to add the asset/create the trustline.
 8. Finally, the anchor sends the deposit funds to the user’s Stellar account.
 
-:::info
+<Info>
 
 An anchor should always maintain a healthy amount of XLM in its distribution account to support new account creations. If doing so becomes unsustainable, it’s recommended that the anchor collaborates with wallets to determine a strategy based on the number of account creation requests. The recommended amount is 2XLM per user account creation (1XLM to meet the minimum balance requirement, and 1XLM for establishing trustlines and covering transaction fees).
 
-:::
+</Info>
 
 With the flow described above, the wallet and the anchor have to facilitate listening for and responding to the trustline status, which can create user experience frictions when waiting for the trustline to be established. To address this issue, Protocol 15 introduced claimable balances, which enhance the flow by allowing users to start using the wallet without having to secure XLM. Both the wallet and the anchor have to implement claimable balance support in order to make this flow work.
 
@@ -89,9 +89,9 @@ The flow with Claimable Balances looks like this:
 6. The anchor creates a Claimable Balance.
 7. The wallet detects the Claimable Balance for the account, claims the funds, and posts it in the wallet.
 
-### Option 2: the wallet creates and funds the Stellar account upon user sign-up​
+### Option 2: the wallet creates and funds the Stellar account upon user sign-up​ {#option-2-the-wallet-creates-and-funds-the-stellar-account-upon-user-sign-up}
 
-For this option, the wallet creates and funds the Stellar account upon every new user sign-up with the minimum requirement of 1XLM, plus the .5XLM reserve for establishing the first trustline, plus a bit more to cover transaction fees. For more information on minimum balances, check out the [Lumens section](../../learn/fundamentals/lumens.mdx#minimum-balance).
+For this option, the wallet creates and funds the Stellar account upon every new user sign-up with the minimum requirement of 1XLM, plus the .5XLM reserve for establishing the first trustline, plus a bit more to cover transaction fees. For more information on minimum balances, check out the [Lumens section](../../learn/fundamentals/lumens#minimum-balance).
 
 The flow looks like this:
 
@@ -102,8 +102,8 @@ The flow looks like this:
 5. The anchor receives the funds, then sends them to the user’s Stellar account.
 6. The wallet detects that funds were sent and notifies the user.
 
-:::note
+<Note>
 
 In the examples above, we suggest having the anchor or wallet cover minimum balance and trustline XLM requirements by depositing funds directly into a user's account. We made that suggestion for the sake of simplicity, but in all cases, the anchor or wallet could instead use sponsored reserves to ensure that when a user closes a trustline or merges their account, the reserve reverts to the sponsoring account rather than to the user's account.
 
-:::
+</Note>
diff --git a/docs/build/apps/dapp-frontend.mdx b/docs/build/apps/dapp-frontend.mdx
index 1c737ff57..10d7ccab2 100644
--- a/docs/build/apps/dapp-frontend.mdx
+++ b/docs/build/apps/dapp-frontend.mdx
@@ -1,13 +1,10 @@
 ---
-sidebar_position: 70
-sidebar_label: Develop a Contract with Frontend Templates
-title: "Build a dapp Frontend: Connect Wallets, Handle Transactions & More"
+title: Develop a Contract with Frontend Templates
+"og:title": "Build a dapp Frontend: Connect Wallets, Handle Transactions & More"
 description: "Learn how to build a dapp frontend that connects to smart contracts. Explore best practices for integrating wallets, handling transactions, and interacting with the Stellar network."
 ---
 
-# Develop a Contract with Frontend Templates
-
-This guide picks up where [Getting Started tutorial](../smart-contracts/getting-started/README.mdx) left off. From there, we'll build our own simple frontend template.
+This guide picks up where [Getting Started tutorial](/docs/build/smart-contracts/getting-started) left off. From there, we'll build our own simple frontend template.
 
 Building our own template will be a great way to learn how they work. They're not that complicated!
 
@@ -84,7 +81,7 @@ PUBLIC_STELLAR_CONTRACT_PATH="../hello-world"
 
 The variables used here are for deploying the contract to testnet and creating the contract bindings for testnet. The user name can be any name, but let’s say you use alice, and have previously created the user `alice` with the Stellar CLI, creating a new account named `alice` will fail.
 
-### 3. initialize.js
+### 3. initialize.js {#3-initializejs}
 
 The goal is to have a script that will handle everything smart contract-related, from creating a user account to deploying the smart contract and providing a TypeScript binding for easy smart contract calls from frontend code. The file `initialize.js` contains that script, and the functionality of it will be broken down in the following sections.
 
@@ -198,7 +195,7 @@ The `deploy()` function will get the contract ID from the CLI call, and add the
 
 In this example, we only use one smart contract, but it’s not uncommon to use multiple smart contracts in a dapp, so the template supports the use of multiple contracts.
 
-##### Create bindings
+#### Create bindings {#create-bindings}
 
 The Stellar CLI has a convenient command to create an NPM package that makes it easy to call smart contract functions from a JavaScript/TypeScript-based frontend. We call the package “bindings” because that’s what it does: it binds the contract and the frontend together.
 
@@ -280,7 +277,7 @@ main().catch((e) => {
 });
 ```
 
-#### Complete initialize.js file
+#### Complete initialize.js file {#complete-initializejs-file}
 
 This is the complete file. Place it in the SolidJS root:
 
diff --git a/docs/build/apps/example-application-tutorial/README.mdx b/docs/build/apps/example-application-tutorial/README.mdx
deleted file mode 100644
index 3869655b2..000000000
--- a/docs/build/apps/example-application-tutorial/README.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-sidebar_position: 40
----
-
-import DocCardList from "@theme/DocCardList";
-
-# Build a Payment App with the JS SDK
-
-Create a basic payment application to transfer tokens between accounts on the Stellar Testnet.
-
-<DocCardList />
diff --git a/docs/build/apps/example-application-tutorial/account-creation.mdx b/docs/build/apps/example-application-tutorial/account-creation.mdx
index 924d4aa1d..80d95ae37 100644
--- a/docs/build/apps/example-application-tutorial/account-creation.mdx
+++ b/docs/build/apps/example-application-tutorial/account-creation.mdx
@@ -1,6 +1,6 @@
 ---
 title: Account Creation
-sidebar_position: 20
+description: "Accounts are the central data structure in Stellar and can only exist with a valid keypair (a public and secret key) and the required minimum balance of XLM."
 ---
 
 Accounts are the central data structure in Stellar and can only exist with a valid keypair (a public and secret key) and the required minimum balance of XLM. Read more in the [Accounts section].
@@ -9,11 +9,11 @@ Accounts are the central data structure in Stellar and can only exist with a val
 
 To start, we'll have our user create an account. In BasicPay, the signup page will display a randomized public and secret keypair that the user can select with the option to choose a new set if preferred.
 
-:::info
+<Info>
 
 Since we are building a [non-custodial application], the encrypted secret key will only ever live in the browser. It will never be shared with a server or anybody else.
 
-:::
+</Info>
 
 ![public and private keys](/assets/basic-pay/public-and-private-keys.png)
 
@@ -189,8 +189,8 @@ Source: https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/h
 
 Our `walletStore` is used in a ton of places in our application, especially in the confirmation modal when asking a user to input their pincode. Read on to see how we've done that.
 
-[accounts section]: ../../../learn/fundamentals/stellar-data-structures/accounts.mdx
-[non-custodial application]: ../application-design-considerations.mdx#non-custodial-service
+[accounts section]: ../../../learn/fundamentals/stellar-data-structures/accounts
+[non-custodial application]: ../application-design-considerations#non-custodial-service
 [`@stellar/typescript-wallet-sdk-km`]: https://www.npmjs.com/package/@stellar/typescript-wallet-sdk-km
-[sponsored reserves]: ../../guides/transactions/sponsored-reserves.mdx
+[sponsored reserves]: ../../guides/transactions/sponsored-reserves
 [contacts list]: ./contacts-list
diff --git a/docs/build/apps/example-application-tutorial/anchor-integration/README.mdx b/docs/build/apps/example-application-tutorial/anchor-integration/README.mdx
deleted file mode 100644
index 9f94cf8a4..000000000
--- a/docs/build/apps/example-application-tutorial/anchor-integration/README.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-sidebar_position: 60
----
-
-import DocCardList from "@theme/DocCardList";
-
-# Anchor Integration
-
-Interact with non-Lumen assets in your application. Use anchors for deposits and withdrawals to get tokens on or off the network.
-
-<DocCardList />
diff --git a/docs/build/apps/example-application-tutorial/anchor-integration/index.mdx b/docs/build/apps/example-application-tutorial/anchor-integration/index.mdx
new file mode 100644
index 000000000..dd8ff500f
--- /dev/null
+++ b/docs/build/apps/example-application-tutorial/anchor-integration/index.mdx
@@ -0,0 +1,32 @@
+---
+title: Anchor Integration
+description: "Interact with non-Lumen assets in your application. Use anchors for deposits and withdrawals to get tokens on or off the network."
+---
+
+<CardGroup cols={2}>
+  <Card title="Setup for Anchored Assets" icon="file-lines" href="/docs/build/apps/example-application-tutorial/anchor-integration/setup">
+
+    An anchor is a Stellar-specific term for the on and off-ramps that connect the Stellar network to traditional financial rails, such as financial...
+
+  </Card>
+  <Card title="SEP-1: Stellar TOML" icon="file-lines" href="/docs/build/apps/example-application-tutorial/anchor-integration/sep1">
+
+    The stellar.toml file is a common place where the Internet can find information about an organization’s Stellar integration.
+
+  </Card>
+  <Card title="SEP-10: Stellar Web Authentication" icon="file-lines" href="/docs/build/apps/example-application-tutorial/anchor-integration/sep10">
+
+    Similar to the SEP-1 information, both SEP-6 and SEP-24 protocols make use of SEP-10 for authentication with the user.
+
+  </Card>
+  <Card title="SEP-6: Deposit and Withdrawal API" icon="file-lines" href="/docs/build/apps/example-application-tutorial/anchor-integration/sep6">
+
+    SEP-6 allows wallets and other clients to interact with anchors directly without the user needing to leave the wallet to go to the anchor’s site.
+
+  </Card>
+  <Card title="SEP-24: Hosted Deposit and Withdrawal" icon="file-lines" href="/docs/build/apps/example-application-tutorial/anchor-integration/sep24">
+
+    SEP-24 provides a standard way for wallets and anchors to interact by having the user open a webview hosted by an anchor to collect and handle KYC information.
+
+  </Card>
+</CardGroup>
diff --git a/docs/build/apps/example-application-tutorial/anchor-integration/sep1.mdx b/docs/build/apps/example-application-tutorial/anchor-integration/sep1.mdx
index 92b3eca5a..4a78d62b6 100644
--- a/docs/build/apps/example-application-tutorial/anchor-integration/sep1.mdx
+++ b/docs/build/apps/example-application-tutorial/anchor-integration/sep1.mdx
@@ -1,9 +1,9 @@
 ---
 title: "SEP-1: Stellar TOML"
-sidebar_position: 20
+description: "The stellar.toml file is a common place where the Internet can find information about an organization’s Stellar integration. Regardless of which type of transfer we want to use (SEP-6 or SEP-24), we'll need to start with SEP-1."
 ---
 
-The [`stellar.toml` file](../../../../tokens/publishing-asset-info.mdx#completing-your-stellartoml) is a common place where the Internet can find information about an organization’s Stellar integration. Regardless of which type of transfer we want to use (SEP-6 or SEP-24), we'll need to start with SEP-1.
+The [`stellar.toml` file](../../../../tokens/publishing-asset-info#completing-your-stellartoml) is a common place where the Internet can find information about an organization’s Stellar integration. Regardless of which type of transfer we want to use (SEP-6 or SEP-24), we'll need to start with SEP-1.
 
 For anchors, we’re interested in the `CURRENCIES` they issue, the `TRANSFER_SERVER` and/or `TRANSFER_SERVER_SEP0024` keywords that indicate if the anchor supports SEP-6, SEP-24, or both, and the `WEB_AUTH_ENDPOINT` which allows a wallet to set up an authenticated user session.
 
diff --git a/docs/build/apps/example-application-tutorial/anchor-integration/sep10.mdx b/docs/build/apps/example-application-tutorial/anchor-integration/sep10.mdx
index 33b9d14d2..81cb57655 100644
--- a/docs/build/apps/example-application-tutorial/anchor-integration/sep10.mdx
+++ b/docs/build/apps/example-application-tutorial/anchor-integration/sep10.mdx
@@ -1,6 +1,6 @@
 ---
 title: "SEP-10: Stellar Web Authentication"
-sidebar_position: 20
+description: "Similar to the SEP-1 information, both SEP-6 and SEP-24 protocols make use of SEP-10 for authentication with the user."
 ---
 
 Similar to the SEP-1 information, both SEP-6 and SEP-24 protocols make use of SEP-10 for authentication with the user. The user must prove they own the account before they can withdraw or deposit any assets as part of SEP-10: Stellar Web Authentication.
@@ -9,11 +9,11 @@ Since we have the `stellar.toml` file information already, we can use that to di
 
 ## Prompt for authentication
 
-:::note
+<Note>
 
 The `/src/routes/dashboard/transfers/+page.svelte` is doing **a lot** of work throughout these sections, and we are chopping it up in various ways for display as part of this tutorial. For a full picture of this file, please remember to check the source code.
 
-:::
+</Note>
 
 ```html title=/src/routes/dashboard/transfers/+page.svelte
 <script>
@@ -194,7 +194,7 @@ function validateChallengeTransaction({
 
 In response, the user signs the transaction. You may have noticed we present this challenge transaction to the user with our regular confirmation modal. Once they've signed the transaction, the application sends it back to the anchor with a `POST` request. If the signature checks out, the success response will contain a [JSON Web Token (JWT)](https://jwt.io), which BasicPay stores in the `webAuthStore` store to use for future interactions with the anchor.
 
-```html title=/src/routes/dashboard/transfers/+page.svelte
+```html title=/src/routes/dashboard/transfers/+page.svelte highlight={10-13}
 <script>
   /* ... */
 
@@ -204,12 +204,10 @@ In response, the user signs the transaction. You may have noticed we present thi
   import { webAuthStore } from "$lib/stores/webAuthStore";
 
   // We import some of our `$lib` functions
-  // highlight-start
   import {
     getChallengeTransaction,
     submitChallengeTransaction,
   } from "$lib/stellar/sep10";
-  // highlight-end
 
   // Takes an action after the pincode has been confirmed by the user on a SEP-10 challenge transaction.
   const onAuthConfirm = async (pincode) => {
diff --git a/docs/build/apps/example-application-tutorial/anchor-integration/sep24.mdx b/docs/build/apps/example-application-tutorial/anchor-integration/sep24.mdx
index 16709ee3f..c73eb2840 100644
--- a/docs/build/apps/example-application-tutorial/anchor-integration/sep24.mdx
+++ b/docs/build/apps/example-application-tutorial/anchor-integration/sep24.mdx
@@ -1,17 +1,17 @@
 ---
 title: "SEP-24: Hosted Deposit and Withdrawal"
-sidebar_position: 40
+description: "SEP-24 provides a standard way for wallets and anchors to interact by having the user open a webview hosted by an anchor to collect and handle KYC information."
 ---
 
 SEP-24 provides a standard way for wallets and anchors to interact by having the user open a webview hosted by an anchor to collect and handle KYC information. In this integration, a user's KYC information is gathered and handled entirely by the anchor. For the most part, after the anchor's webview has opened, BasicPay will have little knowledge about what's going on.
 
-:::info
+<Info>
 
 Remember, SEP-24 depends on [SEP-10 authentication]. Everything below assumes the user has successfully authenticated with the anchor server, and BasicPay has access to an unexpired authentication token to send with its requests.
 
-:::
+</Info>
 
-## Find the anchor's `TRANSFER_SERVER_SEP0024`
+## Find the anchor's `TRANSFER_SERVER_SEP0024` {#find-the-anchors-transfer_server_sep0024}
 
 Before we can ask anything about _how_ to make a SEP-24 transfer, we have to figure out _where_ to discover that information. Fortunately, the SEP-1 protocol describes standardized fields to find out what we need.
 
@@ -25,7 +25,7 @@ export async function getTransferServerSep24(domain) {
 
 **Source:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/sep1.js
 
-## Get `/info`
+## Get `/info` {#get-info}
 
 Our application will request the `/info` endpoint from the anchor's transfer server to understand the supported transfer methods (deposit, withdraw) and available endpoints, as well as additional features that may be available during transfers.
 
@@ -55,15 +55,15 @@ export async function getSep24Info(domain) {
 
 **Source:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/sep24.js
 
-## The user clicks "deposit" or "withdraw"
+## The user clicks "deposit" or "withdraw" {#the-user-clicks-deposit-or-withdraw}
 
 Now that we have all the SEP-24 information the anchor has made available to us, it's up to the user to actually begin the initiation process. In BasicPay, they do that by simply clicking a button that will then trigger the `launchTransferWindowSep24` function.
 
-:::note
+<Note>
 
 This file was pretty heavily covered in the [SEP-6 section]. We'll be presenting here the additions we make to this file, though we won't repeat things we've already covered. Remember to check the source files for the full picture.
 
-:::
+</Note>
 
 ```html title=/src/routes/dashboard/transfers/+page.svelte
 <script>
@@ -141,11 +141,11 @@ export async function initiateTransfer24({
 
 BasicPay doesn't really need (or want) to know everything that's happening between the user and the anchor during a SEP-24 transfer. However, we _do_ want to know when the interaction is over, since we may need to take some action at that point. So, we add a callback to the interactive URL and open the popup window.
 
-:::caution
+<Warning>
 
 Since BasicPay is an entirely client-side application, we can't provide a callback as a URL. So, we are using a `postMessage` callback. For more information on the details of these callback options, check out [this section of the SEP-24 specification].
 
-:::
+</Warning>
 
 ```html title=/src/routes/dashboard/transfers/+page.svelte
 <script>
@@ -276,6 +276,6 @@ In a withdrawal transaction, BasicPay will also build and present to the user a
 
 **Source:** https://github.com/stellar/basic-payment-app/blob/main/src/routes/dashboard/transfers/+page.svelte
 
-[sep-10 authentication]: ./sep10.mdx
-[sep-6 section]: ./sep6.mdx
+[sep-10 authentication]: ./sep10
+[sep-6 section]: ./sep6
 [this section of the sep-24 specification]: https://stellar.org/protocol/sep-24#adding-parameters-to-the-url
diff --git a/docs/build/apps/example-application-tutorial/anchor-integration/sep6.mdx b/docs/build/apps/example-application-tutorial/anchor-integration/sep6.mdx
index 0086efee3..44fae6106 100644
--- a/docs/build/apps/example-application-tutorial/anchor-integration/sep6.mdx
+++ b/docs/build/apps/example-application-tutorial/anchor-integration/sep6.mdx
@@ -1,11 +1,11 @@
 ---
 title: "SEP-6: Deposit and Withdrawal API"
-sidebar_position: 30
+description: "SEP-6 allows wallets and other clients to interact with anchors directly without the user needing to leave the wallet to go to the anchor’s site."
 ---
 
 SEP-6 allows wallets and other clients to interact with anchors directly without the user needing to leave the wallet to go to the anchor’s site. In this integration, a user’s KYC information is gathered and handled by the wallet and submitted to the anchor _on behalf of_ the user.
 
-## Find the anchor's `TRANSFER_SERVER`
+## Find the anchor's `TRANSFER_SERVER` {#find-the-anchors-transfer_server}
 
 Before we can ask anything about _how_ to make a SEP-6 transfer, we have to figure out _where_ to discover that information. Fortunately, the SEP-1 protocol describes standardized fields to find out what we need.
 
@@ -19,15 +19,15 @@ export async function getTransferServerSep6(domain) {
 
 **Source:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/sep1.js
 
-## Get `/info`
+## Get `/info` {#get-info}
 
 Now that we know where the transfer server is located, BasicPay needs to fetch the `/info` endpoint from the anchor's transfer server to understand the supported transfer methods ([deposit, withdraw, deposit-exchange, and withdraw-exchange](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md#info)) and available endpoints, as well as additional features that may be available during transfers.
 
-:::note
+<Note>
 
 At this time, BasicPay only supports the `deposit` and `withdraw` transfer methods. A future version of this tutorial will incorporate the `*-exchange` transfer methods.
 
-:::
+</Note>
 
 ```js title=/src/lib/stellar/sep6.js
 import { getTransferServerSep6 } from "$lib/stellar/sep1";
@@ -45,7 +45,7 @@ export async function getSep6Info(domain) {
 
 ## Display interactive elements
 
-Since many of the SEP-6 (and SEP-24) endpoints require authentication, we wait until our user is [authenticated with SEP-10](./sep10.mdx) before we display what kinds of transfers are available. When they have a valid authentication token, we can display some buttons the user can use to begin a transfer.
+Since many of the SEP-6 (and SEP-24) endpoints require authentication, we wait until our user is [authenticated with SEP-10](./sep10) before we display what kinds of transfers are available. When they have a valid authentication token, we can display some buttons the user can use to begin a transfer.
 
 The user can then initiate one of the transfer methods (in BasicPay, only deposits and withdraws are supported) by clicking the “Deposit” or “Withdraw” button underneath a supported asset.
 
@@ -75,7 +75,7 @@ The user can then initiate one of the transfer methods (in BasicPay, only deposi
 
 ## A special SEP-6 modal component
 
-If you recall back to our [confirmation modal section](../confirmation-modal.mdx), we designed our modal component to be useful for anything we might require. Well, that's _almost_ true. The fact is that SEP-6 interactions are just plain complex. To facilitate that complexity, we've created a purpose-built SEP-6 transfer modal. There is **so much** to it, that we couldn't possibly cover everything it does here. However, we'll cover the main bits and link to the relevant source files.
+If you recall back to our [confirmation modal section](../confirmation-modal), we designed our modal component to be useful for anything we might require. Well, that's _almost_ true. The fact is that SEP-6 interactions are just plain complex. To facilitate that complexity, we've created a purpose-built SEP-6 transfer modal. There is **so much** to it, that we couldn't possibly cover everything it does here. However, we'll cover the main bits and link to the relevant source files.
 
 The modal component itself has been broken into several smaller Svelte components. Check out this source file to start looking through how we've put it together: https://github.com/stellar/basic-payment-app/blob/main/src/routes/dashboard/transfers/components/TransferModalSep6.svelte
 
@@ -253,11 +253,11 @@ export async function initiateTransfer6({
 
 We then store the details of the transfer in the `transfersStore` store and display the transfer server's response to the user. We then wait for them to close the modal.
 
-:::note
+<Note>
 
 The only reason we're storing anything about the transfer in BasicPay is to help us keep track of which anchors the user has initiated transfers with. Otherwise, we wouldn't be able query for a transfer history (like on the `/dashboard` page).
 
-:::
+</Note>
 
 ### (Sometimes) Modal step 5: Send a Stellar payment
 
diff --git a/docs/build/apps/example-application-tutorial/anchor-integration/setup.mdx b/docs/build/apps/example-application-tutorial/anchor-integration/setup.mdx
index 0890e73a5..eb197ec89 100644
--- a/docs/build/apps/example-application-tutorial/anchor-integration/setup.mdx
+++ b/docs/build/apps/example-application-tutorial/anchor-integration/setup.mdx
@@ -1,19 +1,19 @@
 ---
 title: "Setup for Anchored Assets"
-sidebar_position: 10
+description: "An anchor is a Stellar-specific term for the on and off-ramps that connect the Stellar network to traditional financial rails, such as financial..."
 ---
 
-An anchor is a Stellar-specific term for the on and off-ramps that connect the Stellar network to traditional financial rails, such as financial institutions or fintech companies. When a user deposits with an anchor, that anchor will credit their Stellar account with the equivalent amount of digital tokens. The user can then hold, transfer, or trade those tokens just like any other Stellar asset. When a user withdraws those tokens, the anchor redeems them for cash in hand or money in the bank. Read more about anchors in this [anchor section](../../../../learn/fundamentals/anchors.mdx).
+An anchor is a Stellar-specific term for the on and off-ramps that connect the Stellar network to traditional financial rails, such as financial institutions or fintech companies. When a user deposits with an anchor, that anchor will credit their Stellar account with the equivalent amount of digital tokens. The user can then hold, transfer, or trade those tokens just like any other Stellar asset. When a user withdraws those tokens, the anchor redeems them for cash in hand or money in the bank. Read more about anchors in this [anchor section](../../../../learn/fundamentals/anchors).
 
-When a customer downloads a wallet application that is connected to an anchor service, their Stellar account can either be created by the wallet application or the anchor service. In this example, the account has been created by the wallet application, BasicPay. Account creation strategies are described more in-depth [here](../../application-design-considerations.mdx#account-creation-strategies).
+When a customer downloads a wallet application that is connected to an anchor service, their Stellar account can either be created by the wallet application or the anchor service. In this example, the account has been created by the wallet application, BasicPay. Account creation strategies are described more in-depth [here](../../application-design-considerations#account-creation-strategies).
 
 In this example, we’ll use an anchor on Stellar’s Testnet to simulate a bank transfer into and out of the user’s wallet using [SEP-6: Deposit and Withdrawal API](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md) and/or [SEP-24: Hosted Deposit and Withdrawal](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md).
 
-:::info
+<Info>
 
-SEPs define community-decided standards for interoperability on Stellar. Read more in our [SEPs section](../../../../learn/fundamentals/stellar-ecosystem-proposals.mdx).
+SEPs define community-decided standards for interoperability on Stellar. Read more in our [SEPs section](../../../../learn/fundamentals/stellar-ecosystem-proposals).
 
-:::
+</Info>
 
 Our integrations will also use the following SEPs:
 
diff --git a/docs/build/apps/example-application-tutorial/confirmation-modal.mdx b/docs/build/apps/example-application-tutorial/confirmation-modal.mdx
index 8baa20359..42054488c 100644
--- a/docs/build/apps/example-application-tutorial/confirmation-modal.mdx
+++ b/docs/build/apps/example-application-tutorial/confirmation-modal.mdx
@@ -1,6 +1,6 @@
 ---
 title: Confirmation Modal
-sidebar_position: 22
+description: "Since the user's keypair is encrypted with a pincode and stored in their browser, we will occasionally need to prompt them for that pincode to sign a..."
 ---
 
 Since the user's keypair is encrypted with a pincode and stored in their browser, we will occasionally need to prompt them for that pincode to sign a transaction or otherwise prove that they should be permitted to perform some action or view some data.
@@ -17,38 +17,49 @@ The modal window we've implemented facilitates this confirmation flow whenever w
 
 Our modal function uses the `svelte-simple-modal` package to give us a versatile starting point. If you need to, install it now.
 
-```bash npm2yarn
+<CodeGroup>
+
+```bash npm
 npm install --save-dev svelte-simple-modal
 ```
 
+```bash Yarn
+yarn add --dev svelte-simple-modal
+```
+
+```bash pnpm
+pnpm add --save-dev svelte-simple-modal
+```
+
+```bash Bun
+bun add --dev svelte-simple-modal
+```
+
+</CodeGroup>
+
 ### Wrapping the rest of our app in the modal
 
 On the Svelte side, this modal component will be a "wrapper" around the rest of our application, which allows us to trigger the modal from anywhere we need, and it should behave similarly no matter what.
 
-```html title="/src/routes/+layout.svelte"
+```html title="/src/routes/+layout.svelte" highlight={5,8-10,13,19}
 <script>
   import "../app.postcss";
 
   // We will use a `writable` Svelte store to trigger our modal
-  // highlight-next-line
   import { writable } from "svelte/store";
 
   // We have a custom close button for consistent styling, but this is NOT a requirement.
-  // highlight-start
   import ModalCloseButton from "$lib/components/ModalCloseButton.svelte";
   import Modal from "svelte-simple-modal";
   const modal = writable(null);
-  // highlight-end
 </script>
 
-// highlight-next-line
 <Modal
   show="{$modal}"
   closeButton="{ModalCloseButton}"
   classContent="rounded bg-base-100"
 >
   <slot />
-  // highlight-next-line
 </Modal>
 ```
 
@@ -58,11 +69,11 @@ On the Svelte side, this modal component will be a "wrapper" around the rest of
 
 To avoid reinventing the wheel every time we need a modal, we will create a reusable component that can accomodate most of our needs. Then, when we need the confirmation modal, we can pass an object of props to customize the modal's behavior.
 
-:::note
+<Note>
 
 In our `*.svelte` component files, we will **not** dive into the HTML markup outside of the `<script>` tags. The Svelte syntax used in HTML is primarily used for iterating and is quite understandable to read.
 
-:::
+</Note>
 
 The basic parts of this component look like this:
 
@@ -207,11 +218,10 @@ First, in our modal component, we declare a dummy function to act as a prop, as
 
 Now that our modal component is setup to make use of a prop function for confirmation and rejection, we can declare what those functions should do inside the page that spawns the modal.
 
-```html title="/src/routes/signup/+page.svelte"
+```html title="/src/routes/signup/+page.svelte" highlight={4-19,27}
 <script>
   /* ... */
 
-  // highlight-start
   const onConfirm = async (pincode) => {
     // Register the encrypted keypair in the user's browser
     await walletStore.register({
@@ -228,7 +238,6 @@ Now that our modal component is setup to make use of a prop function for confirm
       goto("/dashboard");
     }
   };
-  // highlight-end
 
   const signup = () => {
     open(ConfirmationModal, {
@@ -236,7 +245,6 @@ Now that our modal component is setup to make use of a prop function for confirm
       title: "Confirm Pincode",
       body: "Please re-type your 6-digit pincode to encrypt the secret key.",
       rejectButton: "Cancel",
-      // highlight-next-line
       onConfirm: onConfirm,
     });
   };
diff --git a/docs/build/apps/example-application-tutorial/contacts-list.mdx b/docs/build/apps/example-application-tutorial/contacts-list.mdx
index 944b4d6b5..765279fd9 100644
--- a/docs/build/apps/example-application-tutorial/contacts-list.mdx
+++ b/docs/build/apps/example-application-tutorial/contacts-list.mdx
@@ -1,6 +1,6 @@
 ---
 title: Contacts List
-sidebar_position: 25
+description: "One central feature of BasicPay is a list of contacts containing a user's name and associated Stellar addresses."
 ---
 
 One central feature of BasicPay is a list of contacts containing a user's name and associated Stellar addresses.
@@ -21,11 +21,11 @@ We will create a Svelte `store` to keep track of a user's contact list.
 
 As with the rest of our user-data, the contacts list will live in the browser's `localStorage`. We are using the [`svelt-local-storage-store` package] to facilitate this. We create a Svelte `store` to hold the data, and add a few custom functions to manage the list: `empty`, `remove`, `add`, `favorite`, and `lookup`.
 
-:::note
+<Note>
 
 This tutorial code is simplified for display here. The code is fully typed, documented, and commented in the [source code repository].
 
-:::
+</Note>
 
 ```js title="/src/lib/stores/contactsStore.js"
 import { v4 as uuidv4 } from "uuid";
@@ -92,11 +92,11 @@ export const contacts = createContactsStore();
 
 ### Using the `contacts` store
 
-#### On the `/dashboard/contacts` page
+#### On the `/dashboard/contacts` page {#on-the-dashboardcontacts-page}
 
 We also have a page dedicated to managing contacts. The `/dashboard/contacts` page will allow the user to collect and manage a list of contact entries that stores the contact's name and Stellar address. The contact can also be flagged or unflagged as a "favorite" contact to be displayed on the main `/dashboard` page.
 
-```html title="/src/routes/dashboard/contacts/+page.svelte"
+```html title="/src/routes/dashboard/contacts/+page.svelte" highlight={9}
 <script>
   // We import things from external packages that will be needed
   import { Trash2Icon, UserPlusIcon } from "svelte-feather-icons";
@@ -105,7 +105,6 @@ We also have a page dedicated to managing contacts. The `/dashboard/contacts` pa
   import TruncatedKey from "$lib/components/TruncatedKey.svelte";
 
   // We import any stores we will need to read and/or write
-  // highlight-next-line
   import { contacts } from "$lib/stores/contactsStore";
 
   // We declare a _reactive_ component variable that will hold information for
@@ -123,21 +122,19 @@ We also have a page dedicated to managing contacts. The `/dashboard/contacts` pa
 
 **Source:** https://github.com/stellar/basic-payment-app/blob/main/src/routes/dashboard/contacts/+page.svelte
 
-#### On the `/dashboard` page
+#### On the `/dashboard` page {#on-the-dashboard-page}
 
 The `contacts` store is now exported from this file and can be accessed and used inside a Svelte page or component. Here is how we've implemented a "favorite contacts" component for display on the main BasicPay dashboard.
 
-```html title="/src/routes/dashboard/components/FavoriteContacts.svelte"
+```html title="/src/routes/dashboard/components/FavoriteContacts.svelte" highlight={3,9}
 <script>
   // We import the `contacts` store into our Svelte component
-  // highlight-next-line
   import { contacts } from "$lib/stores/contactsStore";
   import TruncatedKey from "$lib/components/TruncatedKey.svelte";
 
   // `$:` makes a Svelte variable reactive, so it will be re-computed any time
   // the `$contacts` store is modified. We access a Svelte store by adding `$`
   // to the beginning of the variable name.
-  // highlight-next-line
   $: favoriteContacts = $contacts?.filter((contact) => contact.favorite);
 </script>
 
diff --git a/docs/build/apps/example-application-tutorial/index.mdx b/docs/build/apps/example-application-tutorial/index.mdx
new file mode 100644
index 000000000..5c90d15e0
--- /dev/null
+++ b/docs/build/apps/example-application-tutorial/index.mdx
@@ -0,0 +1,52 @@
+---
+title: Build a Payment App with the JS SDK
+description: "Create a basic payment application to transfer tokens between accounts on the Stellar Testnet."
+---
+
+<CardGroup cols={2}>
+  <Card title="Overview" icon="file-lines" href="/docs/build/apps/example-application-tutorial/overview">
+
+    This tutorial walks through how to build an application with the @stellar/stellar-sdk.
+
+  </Card>
+  <Card title="Account Creation" icon="file-lines" href="/docs/build/apps/example-application-tutorial/account-creation">
+
+    Accounts are the central data structure in Stellar and can only exist with a valid keypair (a public and secret key) and the required minimum balance of XLM.
+
+  </Card>
+  <Card title="Confirmation Modal" icon="file-lines" href="/docs/build/apps/example-application-tutorial/confirmation-modal">
+
+    Since the user's keypair is encrypted with a pincode and stored in their browser, we will occasionally need to prompt them for that pincode to sign a...
+
+  </Card>
+  <Card title="Contacts List" icon="file-lines" href="/docs/build/apps/example-application-tutorial/contacts-list">
+
+    One central feature of BasicPay is a list of contacts containing a user's name and associated Stellar addresses.
+
+  </Card>
+  <Card title="Manage Trust" icon="file-lines" href="/docs/build/apps/example-application-tutorial/manage-trust">
+
+    For an account to hold and trade assets other than XLM, it must establish a trustline with the issuing account of that particular asset.
+
+  </Card>
+  <Card title="Payment" icon="file-lines" href="/docs/build/apps/example-application-tutorial/payment">
+
+    A payment operation sends an amount in a specific asset (XLM or non-XLM) to a destination account.
+
+  </Card>
+  <Card title="Path Payment" icon="file-lines" href="/docs/build/apps/example-application-tutorial/path-payment">
+
+    A path payment is where the asset sent can be different from the asset received.
+
+  </Card>
+  <Card title="Anchor Integration" icon="box-archive" href="/docs/build/apps/example-application-tutorial/anchor-integration">
+
+    5 items
+
+  </Card>
+  <Card title="Querying Data" icon="file-lines" href="/docs/build/apps/example-application-tutorial/querying-data">
+
+    Your application will be querying data from Horizon (one of Stellar's APIs) throughout its functionality.
+
+  </Card>
+</CardGroup>
diff --git a/docs/build/apps/example-application-tutorial/manage-trust.mdx b/docs/build/apps/example-application-tutorial/manage-trust.mdx
index 1fe78737a..673049ff9 100644
--- a/docs/build/apps/example-application-tutorial/manage-trust.mdx
+++ b/docs/build/apps/example-application-tutorial/manage-trust.mdx
@@ -1,19 +1,19 @@
 ---
 title: Manage Trust
-sidebar_position: 30
+description: "For an account to hold and trade assets other than XLM, it must establish a trustline with the issuing account of that particular asset. Each trustline increases the account’s base reserve by 0.5 XLM, which means the account will have to hold more XLM in its minimum balance."
 ---
 
-For an account to hold and trade assets other than XLM, it must establish a [trustline](../../../learn/fundamentals/stellar-data-structures/accounts.mdx#trustlines) with the issuing account of that particular asset. Each trustline increases the account’s [base reserve](../../../learn/fundamentals/stellar-data-structures/accounts.mdx#base-reserves-and-subentries) by 0.5 XLM, which means the account will have to hold more XLM in its minimum balance.
+For an account to hold and trade assets other than XLM, it must establish a [trustline](../../../learn/fundamentals/stellar-data-structures/accounts#trustlines) with the issuing account of that particular asset. Each trustline increases the account’s [base reserve](../../../learn/fundamentals/stellar-data-structures/accounts#base-reserves-and-subentries) by 0.5 XLM, which means the account will have to hold more XLM in its minimum balance.
 
 ## User experience
 
 First, we’ll have the user create a trustline for an asset by navigating to the Assets page, selecting an asset, and clicking the “Add Asset” button.
 
-:::info
+<Info>
 
-An asset is displayed as an asset code and issuer address. Learn more in our [Assets section](../../../learn/fundamentals/stellar-data-structures/assets.mdx).
+An asset is displayed as an asset code and issuer address. Learn more in our [Assets section](../../../learn/fundamentals/stellar-data-structures/assets).
 
-:::
+</Info>
 
 ![add-assets](/assets/basic-pay/add-assets.png)
 
@@ -21,11 +21,11 @@ This triggers a modal form for the user to confirm the transaction with their pi
 
 The `changeTrust` operation can also be used to modify or remove trustlines.
 
-:::info
+<Info>
 
 Every transaction must contain a sequence number that is used to identify and verify the order of transactions with the account. A transaction’s sequence number must always increase by one. In BasicPay, fetching and incrementing the sequence number is handled automatically by the transaction builder.
 
-:::
+</Info>
 
 Trustlines hold the balances for all of their associated assets (except XLM, which are held at the account level), and you can display the user’s various balances in your application.
 
@@ -37,7 +37,7 @@ See it in action here: https://basicpay.pages.dev/dashboard/assets
 
 The trustlines an account holds will be necessary to view in several parts of the BasicPay application. First, we'll discuss how we manage different trustlines for the account.
 
-### The `/dashboard/assets` page
+### The `/dashboard/assets` page {#the-dashboardassets-page}
 
 The `/dashboard/assets` page allows the user to manage the Stellar assets their account carries trustlines to. On this page, they can select from several pre-suggested or highly ranked assets, or they could specify their own asset to trust using an asset code and issuer public key. They can also remove trustlines that already exist on their account.
 
@@ -252,4 +252,4 @@ export async function createChangeTrustTransaction({ source, asset, limit }) {
 }
 ```
 
-[this querying data section]: ./querying-data.mdx#fetchaccountbalances
+[this querying data section]: ./querying-data#fetchaccountbalances
diff --git a/docs/build/apps/example-application-tutorial/overview.mdx b/docs/build/apps/example-application-tutorial/overview.mdx
index 709e6b4c2..c6b8974e9 100644
--- a/docs/build/apps/example-application-tutorial/overview.mdx
+++ b/docs/build/apps/example-application-tutorial/overview.mdx
@@ -1,23 +1,23 @@
 ---
 title: Overview
-sidebar_position: 10
+description: "This tutorial walks through how to build an application with the [@stellar/stellar-sdk]."
 ---
 
-:::note
+<Note>
 
-This tutorial walks through how to build an application with the [`@stellar/stellar-sdk`]. To build with the Wallet SDK, please follow the [Build a Wallet tutorial](../wallet/overview.mdx). To build with smart contracts, navigate to the [Smart Contracts section](../../../build/smart-contracts/getting-started/setup.mdx).
+This tutorial walks through how to build an application with the [`@stellar/stellar-sdk`]. To build with the Wallet SDK, please follow the [Build a Wallet tutorial](../wallet/overview). To build with smart contracts, navigate to the [Smart Contracts section](../../../build/smart-contracts/getting-started/setup).
 
-:::
+</Note>
 
 In this tutorial, we'll walk through the steps needed to build a basic payment application on Stellar's Testnet. After this tutorial, you should have a good understanding of the fundamental Stellar concepts and a solid base for iterative development.
 
 For this tutorial, we'll walk through the steps as we build a sample application we've called [BasicPay], which will be used to showcase various features.
 
-:::caution
+<Warning>
 
 Although BasicPay is a full-fledged application on Stellar's Testnet, it has been built solely to showcase Stellar functionality for the educational purposes of this tutorial, not to be copied, pasted, and used on Mainnet.
 
-:::
+</Warning>
 
 ## Project Setup
 
@@ -30,11 +30,11 @@ To build a basic Stellar application, you'll need:
 - A way to interact with the Stellar network: we're using the [`@stellar/stellar-sdk`], but you could use traditional fetch requests. The [`@stellar/stellar-sdk`] is also used for building transactions to submit to the Stellar network.
 - A way to interact with the user's keypair: we're using [`@stellar/typescript-wallet-sdk-km`], but you can opt to use an existing wallet.
 
-:::note
+<Note>
 
 While we are using the above components to construct our application, we have done our best to write this tutorial in such a way that dependency on any one of these things is minimized. Ideally, you should be able to use the JavaScript code we've written and plug it into any other framework you'd like with minimal effort.
 
-:::
+</Note>
 
 We've made the following choices during the development of BasicPay that you may also need to consider as you follow along:
 
@@ -46,11 +46,11 @@ We've made the following choices during the development of BasicPay that you may
 - We do _some_ error handling, but not nearly as much as you would want for a real-world application. If something seems like it's not working, and you're not seeing an error, open your developer console, and you might be able to figure out what has gone wrong.
 - We have not implemented _any_ automated testing. You'll probably want some for your application.
 
-:::note
+<Note>
 
 This tutorial is probably best viewed as "_nearly_ comprehensive." We aren't going to walk you through each and every file in our codebase, and the files we do use to illustrate concepts in the tutorial may not be _entirely_ present or explained. However, we will cover the basics, and point you to more complete examples in the codebase when applicable.
 
-:::
+</Note>
 
 ### Dev Helpers
 
@@ -63,11 +63,11 @@ This tutorial is probably best viewed as "_nearly_ comprehensive." We aren't goi
 
 Here are the steps we've taken to start building BasicPay. Feel free to be inspired and customize these directions as you see fit. The entire [BasicPay codebase] is freely open and available on GitHub for reference.
 
-:::note
+<Note>
 
 This part of the tutorial will need a large helping of "your mileage may vary." We will outline what steps we've taken for our deployment situation, but you will want to review what options are needed for your environment(s).
 
-:::
+</Note>
 
 ### Install Frameworks
 
@@ -85,13 +85,38 @@ This will walk you through the SvelteKit creation process, asking you about the
 
 After this process, the scaffolding for your application will live inside the `my-basic-payment-app` directory. You can `cd` into that directory and add some UI dependencies.
 
-```bash npm2yarn
+<CodeGroup>
+
+```bash npm
 cd my-basic-payment-app
 npm install --save-dev svelte-preprocess tailwindcss@^3.4.13 autoprefixer postcss @sveltejs/adapter-static \
     @tailwindcss/typography \
     daisyui svelte-feather-icons
 ```
 
+```bash Yarn
+cd my-basic-payment-app
+yarn add --dev svelte-preprocess tailwindcss@^3.4.13 autoprefixer postcss @sveltejs/adapter-static \
+    @tailwindcss/typography \
+    daisyui svelte-feather-icons
+```
+
+```bash pnpm
+cd my-basic-payment-app
+pnpm add --save-dev svelte-preprocess tailwindcss@^3.4.13 autoprefixer postcss @sveltejs/adapter-static \
+    @tailwindcss/typography \
+    daisyui svelte-feather-icons
+```
+
+```bash Bun
+cd my-basic-payment-app
+bun add --dev svelte-preprocess tailwindcss@^3.4.13 autoprefixer postcss @sveltejs/adapter-static \
+    @tailwindcss/typography \
+    daisyui svelte-feather-icons
+```
+
+</CodeGroup>
+
 Before we configure anything, we'll need to generate our `tailwind.config.js` and `postcss.config.js` files.
 
 ```bash
@@ -100,30 +125,24 @@ npx tailwindcss init -p
 
 Now, we will require a bit of configuration to make all those components work together. First, modify your `svelte.config.js` file:
 
-```js title="/svelte.config.js"
-// highlight-start
+```js title="/svelte.config.js" highlight={1-2,9-11,13-17}
 import preprocess from "svelte-preprocess";
 import adapter from "@sveltejs/adapter-static";
-// highlight-end
 
 /** @type {import('@sveltejs/kit').Config} */
 const config = {
   kit: {
     // Note: Your `adapter` configuration may need customizations depending
     // on how you are building and deploying your application.
-    // highlight-start
     adapter: adapter({
       fallback: "index.html",
     }),
-    // highlight-end
   },
-  // highlight-start
   preprocess: [
     preprocess({
       postcss: true,
     }),
   ],
-  // highlight-end
 };
 
 export default config;
@@ -135,22 +154,17 @@ Next, you can configure the `tailwind.config.js` file.
 2. Configure our content paths (you may need to modify these values depending on your project structure)
 3. Add the `daisyui` plugin **after** any officialy `@tailwindcss` plugins (only `typography` in our example)
 
-```js title="/tailwind.config.js"
-// highlight-start
+```js title="/tailwind.config.js" highlight={1-2,7-9,11}
 const daisyui = require("daisyui");
 const typography = require("@tailwindcss/typography");
-// highlight-end
 
 /** @type {import('tailwindcss').Config} */
 export default {
   content: [
-    // highlight-start
     "./src/routes/**/*.{html,js,svelte,ts}",
     "./src/routes/**/**/*.{html,js,svelte,ts}",
     "./src/lib/components/**/*.{html,js,svelte,ts}",
-    // highlight-end
   ],
-  // highlight-next-line
   plugins: [typography, daisyui],
 };
 ```
@@ -184,15 +198,33 @@ export const ssr = false;
 
 Your SvelteKit project is now configured and ready to run!
 
-```bash npm2yarn
+<CodeGroup>
+
+```bash npm
 npm run dev
 ```
 
+```bash Yarn
+yarn dev
+```
+
+```bash pnpm
+pnpm run dev
+```
+
+```bash Bun
+bun run dev
+```
+
+</CodeGroup>
+
 ### Stellar dependencies
 
 To work with the Stellar network, datastructures, and locally stored keypairs, we're going to install and configure a few more dependencies.
 
-```bash npm2yarn
+<CodeGroup>
+
+```bash npm
 # Stellar SDKs
 npm install @stellar/stellar-sdk @stellar/typescript-wallet-sdk-km
 # Wallet integration packages (required for vite.config.js SSR bundling)
@@ -202,11 +234,45 @@ npm install --save-dev @esbuild-plugins/node-globals-polyfill @esbuild-plugins/n
     path @rollup/plugin-inject buffer svelte-local-storage-store uuid
 ```
 
-:::info[Stellar Wallets Kit v1]
+```bash Yarn
+# Stellar SDKs
+yarn add @stellar/stellar-sdk @stellar/typescript-wallet-sdk-km
+# Wallet integration packages (required for vite.config.js SSR bundling)
+yarn add @creit.tech/stellar-wallets-kit@^1 @stellar/freighter-api @lobstrco/signer-extension-api
+# We will need some polyfills to make things available client-side
+yarn add --dev @esbuild-plugins/node-globals-polyfill @esbuild-plugins/node-modules-polyfill \
+    path @rollup/plugin-inject buffer svelte-local-storage-store uuid
+```
+
+```bash pnpm
+# Stellar SDKs
+pnpm add @stellar/stellar-sdk @stellar/typescript-wallet-sdk-km
+# Wallet integration packages (required for vite.config.js SSR bundling)
+pnpm add @creit.tech/stellar-wallets-kit@^1 @stellar/freighter-api @lobstrco/signer-extension-api
+# We will need some polyfills to make things available client-side
+pnpm add --save-dev @esbuild-plugins/node-globals-polyfill @esbuild-plugins/node-modules-polyfill \
+    path @rollup/plugin-inject buffer svelte-local-storage-store uuid
+```
+
+```bash Bun
+# Stellar SDKs
+bun add @stellar/stellar-sdk @stellar/typescript-wallet-sdk-km
+# Wallet integration packages (required for vite.config.js SSR bundling)
+bun add @creit.tech/stellar-wallets-kit@^1 @stellar/freighter-api @lobstrco/signer-extension-api
+# We will need some polyfills to make things available client-side
+bun add --dev @esbuild-plugins/node-globals-polyfill @esbuild-plugins/node-modules-polyfill \
+    path @rollup/plugin-inject buffer svelte-local-storage-store uuid
+```
+
+</CodeGroup>
+
+<Info>
+
+**Stellar Wallets Kit v1**
 
 The Stellar Wallets Kit dependency is pinned to `@^1` on purpose. This tutorial and its companion [`stellar/basic-payment-app`](https://github.com/stellar/basic-payment-app) are written against the Kit v1 API (`new StellarWalletsKit(...)`). Installing the package unpinned now resolves to v2.x, whose initialization API is incompatible. This pin keeps the tutorial working until it and BasicPay are migrated to v2 together.
 
-:::
+</Info>
 
 We will use a `window.js` file to inject Buffer into our client-side code, since that's required by some parts of the `@stellar/stellar-sdk`.
 
diff --git a/docs/build/apps/example-application-tutorial/path-payment.mdx b/docs/build/apps/example-application-tutorial/path-payment.mdx
index 02437b083..81705f5d2 100644
--- a/docs/build/apps/example-application-tutorial/path-payment.mdx
+++ b/docs/build/apps/example-application-tutorial/path-payment.mdx
@@ -1,9 +1,9 @@
 ---
 title: Path Payment
-sidebar_position: 50
+description: "A path payment is where the asset sent can be different from the asset received."
 ---
 
-A path payment is where the asset sent can be different from the asset received. There are two possible path payment operations: 1) `path_payment_strict_send`, which allows the user to specify the amount of the asset to send, and 2) `path_payment_strict_receive`, which allows the user to specify the amount of the asset received. Read more in the [Path Payments Guide](../../../build/guides/transactions/path-payments.mdx).
+A path payment is where the asset sent can be different from the asset received. There are two possible path payment operations: 1) `path_payment_strict_send`, which allows the user to specify the amount of the asset to send, and 2) `path_payment_strict_receive`, which allows the user to specify the amount of the asset received. Read more in the [Path Payments Guide](../../../build/guides/transactions/path-payments).
 
 ## User experience
 
@@ -15,28 +15,24 @@ The user will then preview the transaction, input their pincode, and select the
 
 ## Code implementation
 
-### The `/dashboard/send` page
+### The `/dashboard/send` page {#the-dashboardsend-page}
 
-Most of this page has been discussed in the [Payment section](./payment.mdx#the-dashboardsend-page). Below, we're highlighting the unique pieces that are added to BasicPay to allow for the path payment feature.
+Most of this page has been discussed in the [Payment section](./payment#the-dashboardsend-page). Below, we're highlighting the unique pieces that are added to BasicPay to allow for the path payment feature.
 
-```html title="/src/routes/dashboard/send/+page.svelte"
+```html title="/src/routes/dashboard/send/+page.svelte" highlight={7-8,12-13,29-31,94-113}
 <script>
   // We import some of our `$lib` functions
   import {
     fetchAccount,
     submit,
     fetchAccountBalances,
-    // highlight-start
     findStrictSendPaths,
     findStrictReceivePaths,
-    // highlight-end
   } from "$lib/stellar/horizonQueries";
   import {
     createCreateAccountTransaction,
-    // highlight-start
     createPathPaymentStrictReceiveTransaction,
     createPathPaymentStrictSendTransaction,
-    // highlight-end
     createPaymentTransaction,
   } from "$lib/stellar/transactions";
 
@@ -52,11 +48,9 @@ Most of this page has been discussed in the [Payment section](./payment.mdx#the-
   let receiveAmount = "";
   let memo = "";
   let createAccount = null;
-  // highlight-start
   let pathPayment = false;
   let availablePaths = [];
   let strictReceive = false;
-  // highlight-end
   let paymentXDR = "";
   let paymentNetwork = "";
 
@@ -119,7 +113,6 @@ Most of this page has been discussed in the [Payment section](./payment.mdx#the-
       { transaction, network_passphrase } = await createCreateAccountTransaction({
         /* ... */
       })
-    // highlight-start
     } else if (pathPayment && strictReceive) {
       { transaction, network_passphrase } = await createPathPaymentStrictReceiveTransaction({
         source: data.publicKey,
@@ -140,7 +133,6 @@ Most of this page has been discussed in the [Payment section](./payment.mdx#the-
         destinationAmount: receiveAmount,
         memo: memo,
       })
-    // highlight-end
     } else {
       { transaction, network_passphrase } = await createPaymentTransaction({
         /* ... */
diff --git a/docs/build/apps/example-application-tutorial/payment.mdx b/docs/build/apps/example-application-tutorial/payment.mdx
index 3b097d9e4..f4e947786 100644
--- a/docs/build/apps/example-application-tutorial/payment.mdx
+++ b/docs/build/apps/example-application-tutorial/payment.mdx
@@ -1,6 +1,6 @@
 ---
 title: Payment
-sidebar_position: 40
+description: "A payment operation sends an amount in a specific asset (XLM or non-XLM) to a destination account."
 ---
 
 A payment operation sends an amount in a specific asset (XLM or non-XLM) to a destination account. With a basic payment operation, the asset sent is the same as the asset received. BasicPay also allows for path payments (where the asset sent is different than the asset received), which we’ll talk about in the next section.
@@ -13,9 +13,9 @@ In our BasicPay application, the user will navigate to the Payments page where c
 
 The user clicks the "Confirm Transaction" button. If the destination account exists and is properly funded with XLM, this will trigger a Transaction Preview where they can view the transaction details.
 
-All Stellar transactions require a small fee to make it to the ledger. Read more in our [Fees section](../../../learn/fundamentals/fees-resource-limits-metering.mdx).
+All Stellar transactions require a small fee to make it to the ledger. Read more in our [Fees section](../../../learn/fundamentals/fees-resource-limits-metering).
 
-In BasicPay, we’ve set it up so that the user always pays a static fee of 100,000 [stroops](../../../learn/fundamentals/stellar-data-structures/assets.mdx#amount-precision) (one stroop equals 0.0000001 XLM) per operation. Alternatively, you can add a feature to your application that allows the user to set their own fee.
+In BasicPay, we’ve set it up so that the user always pays a static fee of 100,000 [stroops](../../../learn/fundamentals/stellar-data-structures/assets#amount-precision) (one stroop equals 0.0000001 XLM) per operation. Alternatively, you can add a feature to your application that allows the user to set their own fee.
 
 ![payment](/assets/basic-pay/fees.png)
 
@@ -23,7 +23,7 @@ The user then inputs their pincode and clicks the "Confirm" button, which signs
 
 ## Code implementation
 
-### The `/dashboard/send` page
+### The `/dashboard/send` page {#the-dashboardsend-page}
 
 The `/dashboard/send` page allows the user to send payments to other Stellar addresses. They can select from a dropdown containing their contact list names, or they can enter their own "Other..." public key.
 
@@ -37,7 +37,7 @@ The following additional features have been implemented:
   4. The amount entered for the send/receive value.
 - An optional memo field is available for text-only memos.
 
-For now, we'll focus on regular payments, and we'll dig into the path payments in a [later section](./path-payment.mdx).
+For now, we'll focus on regular payments, and we'll dig into the path payments in a [later section](./path-payment).
 
 ```html title="/src/routes/dashboard/send/+page.svelte"
 <script>
diff --git a/docs/build/apps/example-application-tutorial/querying-data.mdx b/docs/build/apps/example-application-tutorial/querying-data.mdx
index 06ece535e..1d1d648a8 100644
--- a/docs/build/apps/example-application-tutorial/querying-data.mdx
+++ b/docs/build/apps/example-application-tutorial/querying-data.mdx
@@ -1,17 +1,17 @@
 ---
 title: Querying Data
-sidebar_position: 70
+description: "Your application will be querying data from Horizon (one of Stellar's APIs) throughout its functionality."
 ---
 
 Your application will be querying data from Horizon (one of Stellar's APIs) throughout its functionality. Information such as account balances, transaction history, sequence numbers for transactions, asset availability, and more are stored in Horizon’s database.
 
 Here is a list of some common queries that you'll make.
 
-:::note
+<Note>
 
 In other places in this tutorial, we have omitted the JSDoc descriptions and typing for the sake of clean presentation. Here, we're including those to make these functions more copy/paste-able.
 
-:::
+</Note>
 
 ## Imports and types
 
@@ -288,11 +288,11 @@ export async function findStrictReceivePaths({
 
 Stellar Expert is a third-party block explorer that is indispensable as a tool for understanding what is happening on the Stellar network. On our `/dashboard/assets` page, we're pre-populating a list of asset trustlines a user might choose to add to their Stellar account. We get this list of assets from the Stellar Expert API.
 
-:::note
+<Note>
 
 Stellar Expert employs their own algorithm to determine the quality of an asset. This algorithm considers things like the number of payments made using an asset, the number of accounts holding that asset, how much of the asset is available on the DEX or in liquidity pools, and so on. These rankings aren't a "final determination" of an asset's quality by any means, and are more like an observation of which Stellar assets see the most use and activity on the network.
 
-:::
+</Note>
 
 We've created our own `RankedAsset` type so BasicPay knows how to interact with these objects. And we are then retrieving the ten most highly-rated assets from the Stellar Expert API.
 
diff --git a/docs/build/apps/guestbook/README.mdx b/docs/build/apps/guestbook/README.mdx
deleted file mode 100644
index c41048304..000000000
--- a/docs/build/apps/guestbook/README.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: Build a Passkey Powered Guestbook Dapp
-sidebar_position: 57
----
-
-import DocCardList from "@theme/DocCardList";
-
-This section walks you through designing and building a decentralized application (dapp) that interacts with a smart contract guestbook, allowing users to read and write public messages. The tutorial also implements a passkey-powered smart wallet for user authentication.
-
-That smart wallet is built with [Smart Account Kit](https://github.com/stellar/smart-account-kit) and the [OpenZeppelin Smart Account](https://docs.openzeppelin.com/stellar-contracts/accounts/smart-account) contracts, and its transactions are submitted by the [OpenZeppelin Relayer](https://docs.openzeppelin.com/relayer/guides/stellar-channels-guide) running the Stellar Channels plugin.
-
-<DocCardList />
diff --git a/docs/build/apps/guestbook/bindings.mdx b/docs/build/apps/guestbook/bindings.mdx
index 4d824087c..e247722d6 100644
--- a/docs/build/apps/guestbook/bindings.mdx
+++ b/docs/build/apps/guestbook/bindings.mdx
@@ -1,17 +1,17 @@
 ---
 title: Generate Bindings
-sidebar_position: 30
+description: "Let's turn our attention to how we'll interact with the deployed smart contract."
 ---
 
 Let's turn our attention to how we'll interact with the deployed smart contract. This is where the TypeScript bindings come in! But, I hear you ask: What are TypeScript bindings?
 
 These bindings are a feature of the Stellar CLI that will generate and produce a fully typed NPM package ready for integration into your frontend. This means you can import and invoke a smart contract as if it were any other nodejs package! You get typed functions for each of your contract's functions, and those will result in a built, simulated, signable, and submittable assembled transaction!
 
-:::tip
+<Tip>
 
 This can be done with ANY contract that's live on the network! Or, you can use it on contracts you've only compiled locally, too.
 
-:::
+</Tip>
 
 We'll be generating our contract bindings, and keeping them in the same repository as our frontend code. However, you could do this in a lot of different ways:
 
@@ -75,11 +75,13 @@ rm -f packages/ye_olde_guestbook/pnpm-lock.yaml
 pnpm --filter ye_olde_guestbook pkg set scripts.prepare=tsc
 ```
 
-:::tip[Customize your bindings]
+<Tip>
+
+**Customize your bindings**
 
 You could take this opportunity to customize your generated bindings _before_ you build them. By default, generated bindings will re-export the entirety of `@stellar/stellar-sdk` for your frontend application. If this behavior isn't desired, you can remove it. These packages are your own to modify as you see fit.
 
-:::
+</Tip>
 
 ### Import the bindings package as a project dependency
 
@@ -93,7 +95,7 @@ That records `"ye_olde_guestbook": "workspace:*"` in your root `package.json`, a
 
 This is also the moment the bindings actually get compiled. Adding the dependency runs an install, the install runs the `prepare` script we just added, and `prepare` runs `tsc`. You'll see pnpm report it as it goes.
 
-:::caution
+<Warning>
 
 Don't lean on `prepare` any harder than that, because pnpm only runs lifecycle scripts when it has installing to do. Against an already up-to-date workspace it prints "Already up to date" and skips them entirely, so a `dist/` that was never built (or that you cleaned) stays missing. Locally that's a puzzling import error. On a deploy it's worse: a warm build cache means the install has nothing to do, `prepare` never fires, and the build fails to resolve `ye_olde_guestbook` on a commit that worked perfectly well yesterday.
 
@@ -112,15 +114,15 @@ The fix is to compile the workspace packages explicitly, as a step the other scr
 
 Now `pnpm dev` and `pnpm build` always have bindings to import, whatever pnpm decided to do about the install.
 
-:::
+</Warning>
 
 ### Import the bindings client into the SvelteKit project
 
-:::info
+<Info>
 
 We're straying just a _bit_ into the Svelte-ish side of things here. The main goal of this step is to get the contract client (which is the "bindings package" we've just generated) into our frontend in a way that makes it usable anywhere we need it. In SvelteKit, we're putting it into `src/lib/contracts` because that means we can easily access the client by importing from `#lib/contracts/ye_olde_guestbook.js` whenever and wherever we need it.
 
-:::
+</Info>
 
 Now, we'll define the contract client in a way we can easily access it through the rest of our app.
 
@@ -140,7 +142,7 @@ export default new Client({
 
 That was a lot of steps and a lot of work wasn't it!?
 
-The good news is that our starter template (remember [that](./overview.mdx#start-from-the-stellar-template-repository)?) comes with an `initialize.js` script that will perform all of those actions for you! This script will go through all the following steps for you:
+The good news is that our starter template (remember [that](/docs/build/apps/guestbook/overview#start-from-the-stellar-template-repository)?) comes with an `initialize.js` script that will perform all of those actions for you! This script will go through all the following steps for you:
 
 - Create and fund a keypair in the CLI
 - Compile, install, and deploy **all contracts** in the `/contracts` directory
@@ -155,11 +157,11 @@ Run the initialization script like so:
 node initialize.js
 ```
 
-:::info
+<Info>
 
-For a more comprehensive overview of the process of creating, customizing, and using initialization scripts like this, check out the [frontend template guide](../../guides/dapps/soroban-contract-init-template.mdx).
+For a more comprehensive overview of the process of creating, customizing, and using initialization scripts like this, check out the [frontend template guide](/docs/build/guides/dapps/soroban-contract-init-template).
 
-:::
+</Info>
 
 We've also added a command to the `package.json` scripts, so you can run this initialize script simply by running (from your project's root directory):
 
diff --git a/docs/build/apps/guestbook/frontend.mdx b/docs/build/apps/guestbook/frontend.mdx
index c30213bd4..d6f6c1f86 100644
--- a/docs/build/apps/guestbook/frontend.mdx
+++ b/docs/build/apps/guestbook/frontend.mdx
@@ -1,6 +1,6 @@
 ---
 title: Dapp Frontend Walkthrough
-sidebar_position: 60
+description: "So, we now have all the pieces in place, and we're ready to connect the dots."
 ---
 
 So, we now have all the pieces in place, and we're ready to connect the dots.
@@ -9,11 +9,11 @@ So, we now have all the pieces in place, and we're ready to connect the dots.
 
 Since we've just gone through the smart account setup, let's begin there. We'll create the functions for signup, login, and the "profile menu" that drops down when a user is logged in (with buttons for viewing the wallet on a block explorer, sending a donation, requesting more Testnet funds, etc.).
 
-:::info
+<Info>
 
-We're using [Svelte state](https://svelte.dev/docs/svelte/$state) to keep track of the user's smart account address, in the `wallet` object we built on the [previous page](./setup-passkeys.mdx#tracking-the-connected-wallet). Your implementation may differ depending on your frontend, state management, and project design. Draw inspiration from the pattern rather than the exact code.
+We're using [Svelte state](https://svelte.dev/docs/svelte/$state) to keep track of the user's smart account address, in the `wallet` object we built on the [previous page](/docs/build/apps/guestbook/setup-passkeys#tracking-the-connected-wallet). Your implementation may differ depending on your frontend, state management, and project design. Draw inspiration from the pattern rather than the exact code.
 
-:::
+</Info>
 
 ### Connect Buttons setup
 
@@ -157,9 +157,9 @@ For returning users, `account.connectWallet({ prompt: true })` asks the browser'
 <button class="btn preset-tonal-primary" onclick={login}>Login</button>
 ```
 
-There's more happening in that one call than it lets on. The credential-to-contract lookup has to take place somewhere, and the kit handles it: it checks its local IndexedDB index first, then falls back to a hosted indexer. Have a look back at the [prerequisites](./passkeys-prerequisites.mdx) if you skipped that part, because it's the one place where "I didn't configure it" is easy to mistake for "it isn't happening."
+There's more happening in that one call than it lets on. The credential-to-contract lookup has to take place somewhere, and the kit handles it: it checks its local IndexedDB index first, then falls back to a hosted indexer. Have a look back at the [prerequisites](/docs/build/apps/guestbook/passkeys-prerequisites) if you skipped that part, because it's the one place where "I didn't configure it" is easy to mistake for "it isn't happening."
 
-The lookup is only half of it, though. Before the kit connects, it also verifies how that smart account was created, what contract code it's running now, and that the passkey the user just presented is a live signer on it. A failed check means no connection at all, which is why the `catch` block runs the error past `describeConnectionError` from the [setup page](./setup-passkeys.mdx#a-few-helpers) before falling back to a generic message. "Something went wrong, please try again later" is actively misleading for a passkey that is never going to work on this account.
+The lookup is only half of it, though. Before the kit connects, it also verifies how that smart account was created, what contract code it's running now, and that the passkey the user just presented is a live signer on it. A failed check means no connection at all, which is why the `catch` block runs the error past `describeConnectionError` from the [setup page](/docs/build/apps/guestbook/setup-passkeys#a-few-helpers) before falling back to a generic message. "Something went wrong, please try again later" is actively misleading for a passkey that is never going to work on this account.
 
 #### User logout
 
@@ -178,13 +178,13 @@ async function logout() {
 
 With those three flows our dapp is ready to onboard users.
 
-### The "profile menu"
+### The "profile menu" {#the-profile-menu}
 
 When a user is logged in, the Settings popover shows their balance, their contract address, and buttons for funding, donating, and logging out. Three of those are worth a look: reading a balance (no signing at all), topping the wallet up, and sending a donation (the first user-signed transaction in the tutorial).
 
 #### Reading the balance
 
-This one's already done. We wrote `getNativeBalance` back on the [setup page](./setup-passkeys.mdx#a-few-helpers), and it simulates a `balance` call against the native Stellar Asset Contract. Simulation costs nothing and needs no signature, so reading a balance is about as cheap as an interaction gets.
+This one's already done. We wrote `getNativeBalance` back on the [setup page](/docs/build/apps/guestbook/setup-passkeys#a-few-helpers), and it simulates a `balance` call against the native Stellar Asset Contract. Simulation costs nothing and needs no signature, so reading a balance is about as cheap as an interaction gets.
 
 ```ts title="src/lib/components/ConnectButtons/Settings.svelte"
 let balance: string = $state("0");
@@ -221,11 +221,11 @@ async function fundWallet() {
 
 That comment is doing more work than it looks like. Smart Account Kit reports _expected_ failures (the relayer refused, the transaction failed on-chain) in a `{ success, error }` result rather than by throwing, which is generally very pleasant. But `toaster.promise` wants a rejected promise to show its error state. So we translate between the two conventions, and this little `if (!result.success) throw result.error` shim shows up in a few places in the codebase for exactly that reason.
 
-:::note
+<Note>
 
 This is worth internalizing before you go hunting for a bug that isn't there: with the kit's submission methods, a `try`/`catch` alone will _not_ catch a failed transaction. You have to check `result.success`. The `catch` block is for the unexpected stuff (a dismissed passkey, a network blip, a programming error).
 
-:::
+</Note>
 
 #### Sending a donation
 
@@ -318,13 +318,13 @@ async function signGuestbook() {
 
 The `write_message` function comes from our generated contract bindings, so invoking a Soroban function looks like any other typed TypeScript call. `account.signAndSubmit()` then does the passkey ceremony, the re-simulation, and the submission.
 
-:::caution
+<Warning>
 
 Here's a gotcha that will bite you the first time, so let's be explicit about it. Our contract's `write_message` function returns the new message's ID, and you might reasonably expect to find it on the assembled transaction after submitting. You won't. When a transaction goes out through a relayer, what comes back is a **transaction hash**, not the invocation's return value, because the relayer submitted it from a channel account and we only ever saw the receipt.
 
 So to get the message ID, we take the hash, poll the network for that transaction with `rpc.pollTransaction()`, and pull the `returnValue` off the result. It's an extra round trip, and it's the price of not making your users think about fees.
 
-:::
+</Warning>
 
 With the ID in hand, we redirect the user to the page for their shiny new entry.
 
diff --git a/docs/build/apps/guestbook/index.mdx b/docs/build/apps/guestbook/index.mdx
new file mode 100644
index 000000000..9b740f62a
--- /dev/null
+++ b/docs/build/apps/guestbook/index.mdx
@@ -0,0 +1,39 @@
+---
+title: Build a Passkey Powered Guestbook Dapp
+description: "This section walks you through designing and building a decentralized application (dapp) that interacts with a smart contract guestbook, allowing users to read and write public messages. The tutorial also implements a passkey-powered smart wallet for user authentication."
+---
+
+That smart wallet is built with [Smart Account Kit](https://github.com/stellar/smart-account-kit) and the [OpenZeppelin Smart Account](https://docs.openzeppelin.com/stellar-contracts/accounts/smart-account) contracts, and its transactions are submitted by the [OpenZeppelin Relayer](https://docs.openzeppelin.com/relayer/guides/stellar-channels-guide) running the Stellar Channels plugin.
+
+<CardGroup cols={2}>
+  <Card title="Overview" icon="file-lines" href="/docs/build/apps/guestbook/overview">
+
+    In this tutorial, we'll walk you through building an old-timey internet guestbook.
+
+  </Card>
+  <Card title="The Guestbook Contract" icon="file-lines" href="/docs/build/apps/guestbook/smart-contract">
+
+    The heart of this project starts with our smart contract.
+
+  </Card>
+  <Card title="Generate Bindings" icon="file-lines" href="/docs/build/apps/guestbook/bindings">
+
+    Let's turn our attention to how we'll interact with the deployed smart contract.
+
+  </Card>
+  <Card title="Passkeys Prerequisites" icon="file-lines" href="/docs/build/apps/guestbook/passkeys-prerequisites">
+
+    Passkeys are a great way to connect users with your dapp without the friction of seed phrases or browser extensions.
+
+  </Card>
+  <Card title="Setup Passkeys" icon="file-lines" href="/docs/build/apps/guestbook/setup-passkeys">
+
+    With the relayer key in place, we're ready to put Smart Account Kit to work and get our users connected.
+
+  </Card>
+  <Card title="Dapp Frontend Walkthrough" icon="file-lines" href="/docs/build/apps/guestbook/frontend">
+
+    So, we now have all the pieces in place, and we're ready to connect the dots.
+
+  </Card>
+</CardGroup>
diff --git a/docs/build/apps/guestbook/overview.mdx b/docs/build/apps/guestbook/overview.mdx
index d2feb3535..45468a5c2 100644
--- a/docs/build/apps/guestbook/overview.mdx
+++ b/docs/build/apps/guestbook/overview.mdx
@@ -1,17 +1,17 @@
 ---
 title: Overview
-sidebar_position: 10
+description: "In this tutorial, we'll walk you through building an old-timey internet guestbook."
 ---
 
 In this tutorial, we'll walk you through building an old-timey [internet guestbook](https://en.wikipedia.org/wiki/Guestbook). (Trust me, they were all the rage back in the day.) We'll examine how the project is constructed, starting with the smart contract, then turn that deployed contract into a "bindings package" we can integrate into our frontend. To authenticate users we'll use Stellar's passkey support via [Smart Account Kit](https://github.com/stellar/smart-account-kit), giving each user their very own [OpenZeppelin Smart Account](https://docs.openzeppelin.com/stellar-contracts/accounts/smart-account). After this tutorial, you'll have a solid understanding of how smart contracts and web applications can work together, plus practical examples for integrating passkey-powered smart wallets into your own projects.
 
 For this tutorial, we'll walk through the steps as we build a sample application we've called [Ye Olde Guestbook](https://ye-olde-guestbook.vercel.app)[^1], which will be used to showcase various features.
 
-:::caution
+<Warning>
 
 Although Ye Olde Guestbook is a full-fledged application on Stellar's Testnet, it has been built solely to showcase Stellar functionality for the educational benefit of the Stellar community. It should not be deployed and used on Stellar Mainnet.
 
-:::
+</Warning>
 
 ![Ye Olde Guestbook Dapp](/assets/guestbook/frontend.png)
 
@@ -24,14 +24,14 @@ To build this guestbook application, we'll need a few pieces.
 - **Application framework:** we're using SvelteKit with TypeScript. SvelteKit (and Svelte on its own) is quite a capable framework, and we'll be using some of its features in this project. The source code is freely open and available with informational comments throughout if you'd like to peruse it.
 - **Frontend framework:** [Skeleton](https://www.skeleton.dev/) simplifies working with [Tailwind CSS](https://tailwindcss.com/).
 - **A way to interact with the network:** this is a TypeScript application, so we're using `@stellar/stellar-sdk` to build transactions and work with keypairs.
-- **A way to interact with a user's account:** we're foregoing traditional wallets here, and using [Smart Account Kit](https://github.com/stellar/smart-account-kit) to give each user a smart account they unlock with a passkey (Touch ID, Face ID, a hardware key, etc.). Smart Account Kit targets the [OpenZeppelin Smart Account](https://docs.openzeppelin.com/stellar-contracts/accounts/smart-account) contracts and integrates natively with the OpenZeppelin Relayer for fee sponsorship. (You may also run into `passkey-kit`, a sibling SDK built around a different wallet contract. The [smart wallets guide](../../guides/contract-accounts/smart-wallets.mdx#client-sdks) covers how the two differ.)
+- **A way to interact with a user's account:** we're foregoing traditional wallets here, and using [Smart Account Kit](https://github.com/stellar/smart-account-kit) to give each user a smart account they unlock with a passkey (Touch ID, Face ID, a hardware key, etc.). Smart Account Kit targets the [OpenZeppelin Smart Account](https://docs.openzeppelin.com/stellar-contracts/accounts/smart-account) contracts and integrates natively with the OpenZeppelin Relayer for fee sponsorship. (You may also run into `passkey-kit`, a sibling SDK built around a different wallet contract. The [smart wallets guide](/docs/build/guides/contract-accounts/smart-wallets#client-sdks) covers how the two differ.)
 - **A relayer for fee sponsorship:** the [OpenZeppelin Relayer](https://docs.openzeppelin.com/relayer/guides/stellar-channels-guide) (Stellar Channels plugin) submits our users' transactions on-chain without exposing them to fees or sequence-number management.
 
-:::note
+<Note>
 
 While we use the above components to construct our application, we've worked to minimize dependency on any one of them. Ideally you should be able to lift most of the TypeScript code we've written into another framework with minimal effort.
 
-:::
+</Note>
 
 Some choices we've made during the course of development:
 
@@ -44,11 +44,11 @@ Some choices we've made during the course of development:
 - We do _some_ error handling, but not nearly as much as a production app would need. If something seems off, open your browser's dev console, which is usually where the answer lives.
 - The smart contract has a proper test suite, which you can read in `contracts/ye_olde_guestbook/src/test.rs`. The frontend has **no** automated testing at all. You'll want some for your own application.
 
-:::note
+<Note>
 
 This tutorial is "_nearly_ comprehensive." We won't walk you through every file, and the files we do cover may not be entirely present or explained. We'll cover the basics and point to the codebase for the full picture.
 
-:::
+</Note>
 
 ### Dev Helpers
 
@@ -63,7 +63,7 @@ Here are the steps we've taken to start building Ye Olde Guestbook. Feel free to
 
 ### Start from the `stellar-template` repository
 
-With the move to smart contract development, a newly emerging utility in the Stellar ecosystem is the "[Stellar template](../../guides/dapps/soroban-contract-init-template.mdx)." These templates can help alleviate the burden of writing boilerplate code, and can help adapt typical Stellar development workflows into framework-specific reference templates. We've created [just such a template](https://github.com/ElliotFriend/stellar-template-sveltekit-passkeys) that can help you get started developing with SvelteKit and passkeys from the very beginning. You can either use the template on the GitHub website:
+With the move to smart contract development, a newly emerging utility in the Stellar ecosystem is the "[Stellar template](/docs/build/guides/dapps/soroban-contract-init-template)." These templates can help alleviate the burden of writing boilerplate code, and can help adapt typical Stellar development workflows into framework-specific reference templates. We've created [just such a template](https://github.com/ElliotFriend/stellar-template-sveltekit-passkeys) that can help you get started developing with SvelteKit and passkeys from the very beginning. You can either use the template on the GitHub website:
 
 ![Github Template Project](/assets/guestbook/github_template.png)
 
@@ -86,7 +86,7 @@ This template will give you a few things to help you hit the ground running:
 
 What more could you want!?
 
-:::info
+<Info>
 
 Prefer to read the finished thing rather than build up to it? The [guestbook repository](https://github.com/ElliotFriend/ye-olde-guestbook) is the same app at the end of this tutorial, so you can clone that instead and follow along in the source:
 
@@ -95,7 +95,7 @@ git clone https://github.com/ElliotFriend/ye-olde-guestbook
 cd ye-olde-guestbook
 ```
 
-:::
+</Info>
 
 ### Set up the `.env` file
 
@@ -127,11 +127,11 @@ The Smart Account Wasm hash and WebAuthn verifier address come pre-filled with t
 pnpm install
 ```
 
-:::note
+<Note>
 
 We're using `pnpm` in this tutorial because it handles SvelteKit + Stellar projects reliably, but the commands translate straightforwardly to `npm` or `yarn` if you prefer.
 
-:::
+</Note>
 
 Next up, let's look at the smart contract at the heart of the project.
 
diff --git a/docs/build/apps/guestbook/passkeys-prerequisites.mdx b/docs/build/apps/guestbook/passkeys-prerequisites.mdx
index 619479ec8..a04a640f6 100644
--- a/docs/build/apps/guestbook/passkeys-prerequisites.mdx
+++ b/docs/build/apps/guestbook/passkeys-prerequisites.mdx
@@ -1,9 +1,9 @@
 ---
 title: Passkeys Prerequisites
-sidebar_position: 40
+description: "Passkeys are a great way to connect users with your dapp without the friction of seed phrases or browser extensions."
 ---
 
-Passkeys are a great way to connect users with your dapp without the friction of seed phrases or browser extensions. Learn more on the [smart wallets guide](../../guides/contract-accounts/smart-wallets.mdx).
+Passkeys are a great way to connect users with your dapp without the friction of seed phrases or browser extensions. Learn more on the [smart wallets guide](/docs/build/guides/contract-accounts/smart-wallets).
 
 For this tutorial we'll be using [Smart Account Kit](https://github.com/stellar/smart-account-kit), which handles the WebAuthn ceremony and deploys an [OpenZeppelin Smart Account](https://docs.openzeppelin.com/stellar-contracts/accounts/smart-account) for each of your users.
 
@@ -25,37 +25,39 @@ We'll use the hosted Testnet relayer at `https://channels.openzeppelin.com/testn
 
 That's the whole prerequisite. Short and sweet!
 
-:::info
+<Info>
 
 SvelteKit doesn't decide what's private by looking at a variable's name. Every variable the app uses is declared in `src/env.ts` (the template ships with this file already filled in), and anything declared there is private unless it's marked `public: true`. Private variables like these two are only importable by server-side code via [`$app/env/private`](https://svelte.dev/docs/kit/environment-variables), so the relayer key never ships to the browser. The `PUBLIC_*` variables from `.env.example` are the ones marked `public: true`, which makes them importable from `$app/env/public`. The `PRIVATE_` and `PUBLIC_` prefixes are just our naming convention, to make each one's audience obvious at a glance.
 
-:::
+</Info>
 
-:::warning[Never expose the relayer key client-side]
+<Warning>
 
-Calls to the Channels relayer authenticate with the API key in an `Authorization: Bearer` header. Put that call in the browser and you've handed the key to anyone who opens their network tab, and they can then spend your credits on whatever they like. This tutorial keeps the key server-side by routing every submission through a same-origin `/api/send` route, which we'll build on the [next page](./setup-passkeys.mdx).
+**Never expose the relayer key client-side**
 
-:::
+Calls to the Channels relayer authenticate with the API key in an `Authorization: Bearer` header. Put that call in the browser and you've handed the key to anyone who opens their network tab, and they can then spend your credits on whatever they like. This tutorial keeps the key server-side by routing every submission through a same-origin `/api/send` route, which we'll build on the [next page](/docs/build/apps/guestbook/setup-passkeys).
 
-## What's handled for you
+</Warning>
+
+## What's handled for you {#whats-handled-for-you}
 
 A couple of jobs that a passkey dapp genuinely needs are taken care of without any setup on your part. It's worth knowing _who_ is doing that work, though, because "I don't configure it" is not the same as "it isn't happening."
 
 ### Funding new wallets
 
-[Friendbot](../../../networks/README.mdx#friendbot) only funds classic `G...` accounts, so it can't top up a `C...` contract address directly. Smart Account Kit does that dance for you: ask it to fund a wallet and it creates a temporary account, funds _that_ from Friendbot, and transfers the XLM on to your user's contract address. There's no funder keypair to generate and no secret key in your `.env`. We'll see the two places this shows up (at signup, and behind a "Fund Wallet" button) on the [frontend page](./frontend.mdx).
+[Friendbot](/docs/networks#friendbot) only funds classic `G...` accounts, so it can't top up a `C...` contract address directly. Smart Account Kit does that dance for you: ask it to fund a wallet and it creates a temporary account, funds _that_ from Friendbot, and transfers the XLM on to your user's contract address. There's no funder keypair to generate and no secret key in your `.env`. We'll see the two places this shows up (at signup, and behind a "Fund Wallet" button) on the [frontend page](/docs/build/apps/guestbook/frontend).
 
-### Finding a returning user's wallet
+### Finding a returning user's wallet {#finding-a-returning-users-wallet}
 
 When a returning user taps their passkey, your dapp gets a credential ID back from the authenticator. Before it can do anything useful with that, it has to turn the credential ID into the smart account contract address the credential was added to, and that reverse lookup requires indexed network data.
 
 Smart Account Kit ships an indexer client for exactly this, defaulting to Mercury's hosted `smart-account-indexer` on Testnet and Mainnet. Its read endpoints are public, so there's no account to create, no JWT to fetch, and no indexing program of your own to write and deploy. You can point `indexerUrl` at any wire-compatible provider, or pass `indexerUrl: false` to switch discovery off entirely.
 
-:::note
+<Note>
 
 The indexer is easy to overlook precisely _because_ you never configure it, so it's worth being explicit about the division of labor. The relayer handles **submission and fee sponsorship**. The indexer handles the **credential-to-address lookup** that lets a returning user log in. They're separate pieces doing separate jobs, and an app that turns discovery off will fail to log users in on any device that hasn't seen that passkey before.
 
-:::
+</Note>
 
 The other half of this story is local: we'll configure the kit with `IndexedDBStorage` so a connected session survives a page reload. That's a per-browser cache sitting in front of the indexer, not a substitute for it.
 
diff --git a/docs/build/apps/guestbook/setup-passkeys.mdx b/docs/build/apps/guestbook/setup-passkeys.mdx
index 83fe18b4d..e98729e68 100644
--- a/docs/build/apps/guestbook/setup-passkeys.mdx
+++ b/docs/build/apps/guestbook/setup-passkeys.mdx
@@ -1,6 +1,6 @@
 ---
 title: Setup Passkeys
-sidebar_position: 50
+description: "With the relayer key in place, we're ready to put Smart Account Kit to work and get our users connected."
 ---
 
 With the relayer key in place, we're ready to put Smart Account Kit to work and get our users connected. This takes two files:
@@ -77,14 +77,14 @@ Worth calling out a few of those options:
 - **`accountWasmHash`** is the Wasm hash of the [OpenZeppelin Smart Account](https://docs.openzeppelin.com/stellar-contracts/accounts/smart-account) contract code. Every user's wallet is a fresh instance deployed from this executable. The hash is just the Sha256 of the compiled contract file, and it's returned when that contract is installed on the network. The shared Testnet value comes pre-filled in `.env.example`, so there's nothing for you to compile or deploy here.
 - **`webauthnVerifierAddress`** is the contract address of the shared verifier that checks `secp256r1` signatures on-chain. Also pre-filled.
 - **`relayerUrl`** points at our _own_ `/api/send` route rather than at OpenZeppelin directly. That's the whole trick for keeping the API key server-side, and we'll build that route below.
-- **`storage`** decides where a connected session lives. `IndexedDBStorage` means a session survives a page reload. As noted in the [prerequisites](./passkeys-prerequisites.mdx), this is a per-browser cache sitting in front of the indexer, not a replacement for it.
+- **`storage`** decides where a connected session lives. `IndexedDBStorage` means a session survives a page reload. As noted in the [prerequisites](/docs/build/apps/guestbook/passkeys-prerequisites), this is a per-browser cache sitting in front of the indexer, not a replacement for it.
 - **`rpName`** is the "relying party" name, which is the label your users will see in their authenticator's prompt. Make it something they'll recognize.
 
-:::note
+<Note>
 
 If you're server-rendering any part of your app, note the `browser` guard on `storage`. IndexedDB is a browser API, so handing the kit an `IndexedDBStorage` during SSR will fall over. Ye Olde Guestbook sets `export const ssr = false` in `src/routes/+layout.ts` and renders entirely on the client, but the guard costs nothing and saves a confusing error later.
 
-:::
+</Note>
 
 ### A few helpers
 
@@ -226,11 +226,11 @@ Each of those maps to a check the kit runs on your behalf:
 
 Returning `null` for anything else matters as much as the four branches do. This helper only claims the errors it recognizes, and everything it doesn't recognize falls through to the caller's own generic message.
 
-:::note
+<Note>
 
 These checks are why a passkey that works perfectly well in one app can still be refused by another. The kit is deliberately fail-closed here, so it would rather decline to connect than hand your app a smart account it couldn't fully vouch for.
 
-:::
+</Note>
 
 ## Tracking the connected wallet
 
@@ -347,15 +347,15 @@ export const POST: RequestHandler = async ({ url, request, fetch }) => {
 A few things this route is doing on purpose:
 
 - **The `origin` check** is a first, cheap line of defense. Without it, anyone who finds `yourdomain.com/api/send` can submit their own transactions while _you_ pick up the tab for the fees.
-- **The `params` wrapper** is what the Channels endpoint expects on the wire: `{ "params": { ... } }`, rather than the bare payload the kit sent us. You won't see it in the [OpenZeppelin Relayer guide](../../../tools/openzeppelin-relayer.mdx), because those examples go through the relayer SDK, which adds the wrapper for you. We're talking to the endpoint directly, so we add it ourselves.
+- **The `params` wrapper** is what the Channels endpoint expects on the wire: `{ "params": { ... } }`, rather than the bare payload the kit sent us. You won't see it in the [OpenZeppelin Relayer guide](/docs/tools/openzeppelin-relayer), because those examples go through the relayer SDK, which adds the wrapper for you. We're talking to the endpoint directly, so we add it ourselves.
 - **Passing the relayer's response through untouched** keeps the route dumb, which is a feature. The kit treats a submission as successful only when the response status is ok _and_ the body carries a top-level `success: true`, which is exactly the `{ success, data }` envelope Channels already returns. Re-shaping the response here would only give us a new way to accidentally report a successful transaction as a failed one.
 
-:::warning
+<Warning>
 
 An origin header is trivially forged by anything that isn't a browser, so please don't mistake the check above for real authorization. Before you put something like this on Mainnet you'll want actual rate limiting, a way to bound _which_ transactions you're willing to sponsor, and some monitoring on your relayer credits. Otherwise a bad actor can happily drain them.
 
 Implementing all of that is outside the scope of this tutorial, but it's very much inside the scope of shipping to real users.
 
-:::
+</Warning>
 
 Still with us?! Incredible! You're a rock star! And, you're ready to get into the interactions with the smart contract! See you on the next page!
diff --git a/docs/build/apps/guestbook/smart-contract.mdx b/docs/build/apps/guestbook/smart-contract.mdx
index 97b9333ce..6e71fbe9a 100644
--- a/docs/build/apps/guestbook/smart-contract.mdx
+++ b/docs/build/apps/guestbook/smart-contract.mdx
@@ -1,6 +1,6 @@
 ---
 title: The Guestbook Contract
-sidebar_position: 20
+description: "The heart of this project starts with our smart contract."
 ---
 
 The heart of this project starts with our smart contract. This smart contract will, in essence, act as a database for our guestbook messages. Users will be able to write messages, read them, and edit their own previously submitted message(s). Additionally, the contract will be upgradeable, and it will require initialization.
@@ -15,11 +15,11 @@ All the following "business logic" will be handled by our smart contract:
 - **A means of retrieving donations and transferring them to the `Admin` address.** The hubris associated with requesting donations on a site like this speaks volumes of the maintainer's sense of self. However, providing this functionality is an excellent exercise in asset interactions within the smart contract.
 - We'll also need some utility functions that the contract will use internally, as well as a `__constructor` and an `upgrade` function, in case we need to upgrade our smart contract in the future.
 
-:::note
+<Note>
 
 We'll be diving into each of the main functions below, but if you want to see the whole smart contract uninterrupted, it can be found [on GitHub](https://github.com/ElliotFriend/ye-olde-guestbook/blob/main/contracts/ye_olde_guestbook/src/lib.rs).
 
-:::
+</Note>
 
 ## How it works
 
@@ -216,11 +216,11 @@ pub fn read_latest(env: Env) -> Result<Message, Error> {
 
 #### `claim_donations`
 
-:::info
+<Info>
 
 We'll set aside whether or not the maintainer of the guestbook _should_ be soliciting donations, and we'll just assume that they _want to_. It's a great way to think about asset interoperability in your smart contracts, so let's go for it!
 
-:::
+</Info>
 
 The `claim_donations` function will allow the invoker of the function to send a balance of any token to the admin of the guestbook contract. We'll direct your attention to two aspects of this function, in particular.
 
@@ -364,7 +364,7 @@ pub enum DataKey {
 
 #### `Error`
 
-We're holding to the typical [contract conventions](../../guides/conventions/error-enum.mdx), and creating an `enum` to keep track of our errors.
+We're holding to the typical [contract conventions](/docs/build/guides/conventions/error-enum), and creating an `enum` to keep track of our errors.
 
 ```rust
 #[contracterror]
diff --git a/docs/build/apps/index.mdx b/docs/build/apps/index.mdx
new file mode 100644
index 000000000..fc7b0192e
--- /dev/null
+++ b/docs/build/apps/index.mdx
@@ -0,0 +1,60 @@
+---
+title: Build Applications
+"og:title": "Build Blockchain Apps: Guides, Tools, and Best Practices for Development"
+description: "Learn how to build blockchain apps with guides, tools, and best practices. Explore key concepts, integration tips, and resources for development on Stellar."
+---
+
+This section walks you through design considerations for applications and tutorials for building applications with or without smart contracts.
+
+<CardGroup cols={2}>
+  <Card title="Introduction" icon="file-lines" href="/docs/build/apps/overview">
+
+    Build a wallet application on Stellar with the Wallet SDK using Typescript, Flutter, Kotlin or Swift. Explore key features, setup steps, and best practices.
+
+  </Card>
+  <Card title="Application Design Considerations" icon="file-lines" href="/docs/build/apps/application-design-considerations">
+
+    When building an application, one of the first things you have to decide is how your users’ secret keys will be secured and stored.
+
+  </Card>
+  <Card title="Build a Wallet with the Wallet SDK" icon="box-archive" href="/docs/build/apps/wallet">
+
+    9 items
+
+  </Card>
+  <Card title="Build a Payment App with the JS SDK" icon="box-archive" href="/docs/build/apps/example-application-tutorial">
+
+    9 items
+
+  </Card>
+  <Card title="Build a Payment App with Swift" icon="file-lines" href="/docs/build/apps/swift-payment-app">
+
+    SwiftBasicPay is an open-source example iOS payment application that showcases how to integrate Stellar's powerful payment infrastructure into native Swift...
+
+  </Card>
+  <Card title="Build Custom Network Ingestion Pipeline" icon="box-archive" href="/docs/build/apps/ingest-sdk">
+
+    2 items
+
+  </Card>
+  <Card title="Build a Passkey Powered Guestbook Dapp" icon="box-archive" href="/docs/build/apps/guestbook">
+
+    6 items
+
+  </Card>
+  <Card title="Develop a Contract with Frontend Templates" icon="file-lines" href="/docs/build/apps/dapp-frontend">
+
+    Learn how to build a dapp frontend that connects to smart contracts. Explore best practices for integrating wallets, handling transactions, and interacting with the Stellar network.
+
+  </Card>
+  <Card title="Privacy on Stellar" icon="file-lines" href="/docs/build/apps/privacy">
+
+    Stellar is a public blockchain: every transaction is recorded onchain and visible to anyone.
+
+  </Card>
+  <Card title="ZK Proofs on Stellar" icon="file-lines" href="/docs/build/apps/zk">
+
+    X-Ray (Protocol 25) introduced native host functions for zero-knowledge-friendly primitives (BN254 and Poseidon/Poseidon2), marking an important milestone...
+
+  </Card>
+</CardGroup>
diff --git a/docs/build/apps/ingest-sdk/README.mdx b/docs/build/apps/ingest-sdk/README.mdx
deleted file mode 100644
index 8dc6a3b4d..000000000
--- a/docs/build/apps/ingest-sdk/README.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-sidebar_position: 55
----
-
-import DocCardList from "@theme/DocCardList";
-
-# Build Custom Network Ingestion Pipeline
-
-With Stellar's [Composable Data Platform](https://stellar.org/blog/developers/composable-data-platform) you can build fast, lightweight data pipelines for ledger data.
-
-<DocCardList />
diff --git a/docs/build/apps/ingest-sdk/index.mdx b/docs/build/apps/ingest-sdk/index.mdx
new file mode 100644
index 000000000..e69f791af
--- /dev/null
+++ b/docs/build/apps/ingest-sdk/index.mdx
@@ -0,0 +1,17 @@
+---
+title: Build Custom Network Ingestion Pipeline
+description: "With Stellar's Composable Data Platform you can build fast, lightweight data pipelines for ledger data."
+---
+
+<CardGroup cols={2}>
+  <Card title="Overview" icon="file-lines" href="/docs/build/apps/ingest-sdk/overview">
+
+    This tutorial walks through how an application can leverage CDP architecture to create fast, lightweight Stellar Ledger Metada data pipelines using a few...
+
+  </Card>
+  <Card title="CDP Consumer Pipeline Sample Code" icon="file-lines" href="/docs/build/apps/ingest-sdk/ingestion-pipeline-code">
+
+    Complete code for a small sample of a consumer pipeline of Stellar network ledger metadata using the Stellar Go Ingest SDK to demonstrate data pipeline from...
+
+  </Card>
+</CardGroup>
diff --git a/docs/build/apps/ingest-sdk/ingestion-pipeline-code.mdx b/docs/build/apps/ingest-sdk/ingestion-pipeline-code.mdx
index c37b0c9d6..daeb09b4d 100644
--- a/docs/build/apps/ingest-sdk/ingestion-pipeline-code.mdx
+++ b/docs/build/apps/ingest-sdk/ingestion-pipeline-code.mdx
@@ -1,28 +1,30 @@
 ---
 title: CDP Consumer Pipeline Sample Code
-sidebar_position: 30
+description: "Complete code for a small sample of a consumer pipeline of Stellar network ledger metadata using the Stellar Go Ingest SDK to demonstrate data pipeline from ledger metadata to derived data model with event-driven, distributed processing to sample microservice (Python script) as subscriber."
 ---
 
-Complete code for a small sample of a consumer pipeline of Stellar network ledger metadata using the Stellar Go [Ingest SDK](overview.mdx#the-ingestion-sdk-packages) to demonstrate data pipeline from ledger metadata to derived data model with event-driven, distributed processing to sample microservice (Python script) as subscriber.
+Complete code for a small sample of a consumer pipeline of Stellar network ledger metadata using the Stellar Go [Ingest SDK](/docs/build/apps/ingest-sdk/overview#the-ingestion-sdk-packages) to demonstrate data pipeline from ledger metadata to derived data model with event-driven, distributed processing to sample microservice (Python script) as subscriber.
 
 This example uses the ZeroMQ [goczmq](https://github.com/zeromq/goczmq) Go wrapper SDK, which requires a few o/s [dependent libraries to also be installed on the host machine](https://github.com/zeromq/goczmq?tab=readme-ov-file#dependencies).
 
 This example requires having access to a public ledger metadata lake that is actively populated with latest ledgers from Stellar mainnet. For purposes of the example it uses a reference data lake hosted on [AWS Open Data S3](../../../data/apis/rpc/admin-guide/data-lake-integration#1-accessing-a-data-lake)
 
-### Step# 1 - Create example directory and copy following files to your workstation.
+### Step# 1 - Create example directory and copy following files to your workstation. {#step-1---create-example-directory-and-copy-following-files-to-your-workstation}
 
-<CodeExample>
-```bash
+<CodeGroup>
+
+```bash bash
 mkdir pipeline-example; cd pipeline-example
 
-````
-</CodeExample>
+```
+
+</CodeGroup>
 
-### `main.go`
+### `main.go` {#maingo}
 
-<CodeExample>
+<CodeGroup>
 
-```go
+```go Go
 
 package main
 
@@ -226,17 +228,17 @@ func main() {
   log.Infof("Payment ingestion pipeline ended %v\n", ledgerMetadataInboundAdapter.Run(ctx))
 }
 
-````
+```
 
-</CodeExample>
+</CodeGroup>
 
-### `config.toml`
+### `config.toml` {#configtoml}
 
 The CDP configuration settings, this file defines the data storage which contains the pre-generated Ledger Metadata files. The [S3 Public Blockchain](https://registry.opendata.aws/aws-public-blockchain) bucket for [Stellar Pubnet](https://aws-public-blockchain.s3.us-east-2.amazonaws.com/index.html#v1.1/stellar/ledgers/pubnet) is used in this example.
 
-<CodeExample>
+<CodeGroup>
 
-```
+```text Example
 type = "S3"
 
 [params]
@@ -250,15 +252,15 @@ files_per_partition = 64000
 
 ```
 
-</CodeExample>
+</CodeGroup>
 
-### `distributed_payment_subsciber.py`
+### `distributed_payment_subsciber.py` {#distributed_payment_subsciberpy}
 
 A Python script demonstrating how we now have distributed processing and event driven architecture by leveraging the MQ Broker to push derived application payment data model out to other microservices. Make sure to `pip install pyzmq`
 
-<CodeExample>
+<CodeGroup>
 
-```python
+```python Python
 import sys
 import zmq
 import json
@@ -280,22 +282,27 @@ while True:
 
 ```
 
-</CodeExample>
+</CodeGroup>
 
-### Step# 2 - Compile and run the ingestion pipeline example.
+### Step# 2 - Compile and run the ingestion pipeline example. {#step-2---compile-and-run-the-ingestion-pipeline-example}
 
-<CodeExample>
-```bash 
+<CodeGroup>
+
+```bash bash
 go mod init example/pipeline
 go get github.com/stellar/go-stellar-sdk@latest github.com/zeromq/goczmq@v4.1.0
-go mod tidy 
-go build -o pipeline ./. 
+go mod tidy
+go build -o pipeline ./.
 AWS_SHARED_CREDENTIALS_FILE=/dev/null ./pipeline
 
 ```
-</CodeExample>
 
-### Step# 3 - Run the distributed pipeline consumer
+</CodeGroup>
+
+### Step# 3 - Run the distributed pipeline consumer {#step-3---run-the-distributed-pipeline-consumer}
 
 In separate terminal, run `python distributed_payment_subsciber.py`, this will perform distributed pipeline topology, as it receives messages with payment info from the pipeline process and does additional processing(printing it to console).
+
+```
+
 ```
diff --git a/docs/build/apps/ingest-sdk/overview.mdx b/docs/build/apps/ingest-sdk/overview.mdx
index 80385c561..23ecc0bc8 100644
--- a/docs/build/apps/ingest-sdk/overview.mdx
+++ b/docs/build/apps/ingest-sdk/overview.mdx
@@ -1,6 +1,6 @@
 ---
 title: Overview
-sidebar_position: 10
+description: "This tutorial walks through how an application can leverage CDP architecture to create fast, lightweight Stellar Ledger Metada data pipelines using a few select packages from the Stellar Go Repo github.com/stellar/go-stellar-sdk collectively known as the 'Ingestion' SDK:"
 ---
 
 This tutorial walks through how an application can leverage [CDP architecture](https://stellar.org/blog/developers/composable-data-platform) to create fast, lightweight Stellar Ledger Metada data pipelines using a few select packages from the Stellar Go Repo [github.com/stellar/go-stellar-sdk](https://github.com/stellar/go-stellar-sdk) collectively known as the 'Ingestion' SDK:
@@ -22,17 +22,17 @@ To use this example CDP pipeline for live Stellar network transaction data, you'
 - A developer workstation with [Go](https://go.dev/learn) programming language runtime installed
 - An IDE to edit Go code, [VSCode](https://code.visualstudio.com/download) is good if one is needed
 - A newly initialized, empty Go project folder. `mkdir pipeline; cd pipeline; go mod init example/pipeline`
-- Some familiarity to the [Stellar Ledger Metadata model](../../../learn/fundamentals/stellar-data-structures/README.mdx). It is defined in an IDL format expressed in [XDR encoding](https://github.com/stellar/stellar-xdr).
+- Some familiarity to the [Stellar Ledger Metadata model](/docs/learn/fundamentals/stellar-data-structures). It is defined in an IDL format expressed in [XDR encoding](https://github.com/stellar/stellar-xdr).
 - Docker
 - Google Cloud Platform account:
   - a bucket created in Google Cloud Storage(GCS)
-  - GCP [credentials in workstation environment](../../../data/indexers/build-your-own/galexie/admin_guide/setup.mdx#google-cloud-platform-gcp-credentials)
+  - GCP [credentials in workstation environment](../../../data/indexers/build-your-own/galexie/admin_guide/setup#google-cloud-platform-gcp-credentials)
 
 Our example application is only interested in a small subset of the overall network data model related to asset transfers triggered by Payment operation and defines its own derived data model as the goal of exercise:
 
-<CodeExample>
+<CodeGroup>
 
-```
+```text Example
 ::AppPayment
    Timestamp: uint
    BuyerAccountId: string
@@ -42,7 +42,7 @@ Our example application is only interested in a small subset of the overall netw
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
 The example application will perform both of CDP pipelines. A minimum of two pipelines are required for a complete end to end CDP architecture.
 
@@ -62,9 +62,9 @@ There will be open source contributions for implementations on other storage lay
 
 Use Galexie, a new CDP command line program for exporting network metadata to datastores.
 
-- Follow the Galexie setup steps in [Galexie User Guide](../../../data/indexers/build-your-own/galexie/admin_guide/setup.mdx), to configure specifics of GCS bucket and target network.
+- Follow the Galexie setup steps in [Galexie User Guide](../../../data/indexers/build-your-own/galexie/admin_guide/setup), to configure specifics of GCS bucket and target network.
 
-- Follow the [Galexie docker runtime instructions](../../../data/indexers/build-your-own/galexie/admin_guide/running.mdx) to start the export.
+- Follow the [Galexie docker runtime instructions](../../../data/indexers/build-your-own/galexie/admin_guide/running) to start the export.
   - For one time export of historical bounded range of ledgers, use `append --start <from_ledger> --end <to_ledger>`
   - For a continuous export of prior ledgers and all new ledgers generated on network, use `append --start <from_ledger>`.
 
@@ -88,4 +88,4 @@ Acts as the termination of the pipeline, it subscribes to receive `ApplicationPa
 
 ### Summary
 
-Refer to [Ingestion Pipeline Sample Application](./ingestion-pipeline-code.mdx) for complete consumer code example, demonstrating a live, streaming pipeline against the Stellar network, processing each new ledger's metadata as it is closed on the network.
+Refer to [Ingestion Pipeline Sample Application](./ingestion-pipeline-code) for complete consumer code example, demonstrating a live, streaming pipeline against the Stellar network, processing each new ledger's metadata as it is closed on the network.
diff --git a/docs/build/apps/overview.mdx b/docs/build/apps/overview.mdx
index 4e15f56c9..f69116588 100644
--- a/docs/build/apps/overview.mdx
+++ b/docs/build/apps/overview.mdx
@@ -1,25 +1,23 @@
 ---
-title: "Build Wallet Applications on Stellar with the Wallet SDK in four languages"
-sidebar_position: 0
-sidebar_label: Introduction
+title: Overview
+sidebarTitle: Introduction
+"og:title": Build Wallet Applications on Stellar with the Wallet SDK in four languages
 description: "Build a wallet application on Stellar with the Wallet SDK using Typescript, Flutter, Kotlin or Swift. Explore key features, setup steps, and best practices."
 ---
 
-# Overview
-
 Stellar is an open-source distributed ledger that you can use as a backend to power various applications and services, such as wallets, payment apps, currency exchanges, micropayment services, platforms for in-game purchases, and more — check out projects being built on Stellar: [Stellar Ecosystem Projects](https://stellar.org/ecosystem/projects#Projects).
 
 Stellar has built-in logic for key storage, creating accounts, signing transactions, tracking balances, and queries to the Stellar database, and anyone can use the network to issue, store, transfer, and trade assets.
 
-This documentation includes sections on how to build applications without smart contracts with the [Wallet SDK](./wallet/overview.mdx) or the [JS SDK](./example-application-tutorial/overview.mdx), building with smart contracts with the [dapp frontend tutorial](./dapp-frontend.mdx), and all information regarding experimentation with [passkey / contract account wallets](../guides/contract-accounts/smart-wallets.mdx).
+This documentation includes sections on how to build applications without smart contracts with the [Wallet SDK](./wallet/overview) or the [JS SDK](./example-application-tutorial/overview), building with smart contracts with the [dapp frontend tutorial](./dapp-frontend), and all information regarding experimentation with [passkey / contract account wallets](../guides/contract-accounts/smart-wallets).
 
 ## Anchors
 
 Many Stellar assets connect to real-world currencies, and Stellar has open protocols for integrating deposits and withdrawals of these assets via the [anchor network](https://stellar.org/learn/anchor-basics). Because of this, a Stellar-based application can take advantage of real banking rails and connect to real money.
 
-Read more about anchors in our [Anchors section](../../learn/fundamentals/anchors.mdx).
+Read more about anchors in our [Anchors section](../../learn/fundamentals/anchors).
 
-Set up an anchor using the [Anchor Platform](../../platforms/anchor-platform/README.mdx).
+Set up an anchor using the [Anchor Platform](/docs/platforms/anchor-platform).
 
 Integrate MoneyGram Ramps into an existing application with the [Integrate with MoneyGram Ramps tutorial](https://developer.moneygram.com/moneygram-developer/docs/integrate-moneygram-ramps).
 
diff --git a/docs/build/apps/privacy.mdx b/docs/build/apps/privacy.mdx
index 161064365..4ec600153 100644
--- a/docs/build/apps/privacy.mdx
+++ b/docs/build/apps/privacy.mdx
@@ -1,10 +1,8 @@
 ---
 title: Privacy on Stellar
-sidebar_position: 74
+description: "Stellar is a public blockchain: every transaction is recorded onchain and visible to anyone."
 ---
 
-# Privacy on Stellar
-
 Stellar is a public blockchain: every transaction is recorded onchain and visible to anyone. This transparency enables permissionless validation, but many real-world use cases — payroll, institutional settlement, everyday payments — require transaction privacy.
 
 To support use cases like these, the Stellar community is building configurable, compliance-ready privacy tools. From low-level cryptographic host functions to managed private payment systems, these solutions help developers protect sensitive financial information while supporting regulatory compliance and enterprise requirements.
@@ -21,11 +19,11 @@ Privacy Pools include built-in features that allow operators to implement compli
 
 Nethermind has built Stellar Private Payments (SPP), a Privacy Pools implementation for Stellar using Circom circuits, Groth16 proofs, and Stellar smart contracts. SPP gives payments counterparty-level privacy: users hold a private balance in a shared shielded pool and pay each other inside it, while the public ledger records only that the pool was used — never who paid whom or how much.
 
-:::caution
+<Warning>
 
 Stellar Private Payments is a developer preview. The contracts, SDKs, and demo linked below are unaudited — testnet only, not intended for production use or real assets.
 
-:::
+</Warning>
 
 | Component | Description |
 | --- | --- |
@@ -53,11 +51,11 @@ This makes confidential tokens well-suited for payments where parties need confi
 
 The [Confidential Token Association](https://www.confidentialtoken.org) — whose members include the Stellar Development Foundation, Nethermind, OpenZeppelin, and Zama — is developing an open standard for encryption-based onchain confidentiality compatible with existing token interfaces. OpenZeppelin's implementation for Stellar is available in the [`stellar-contracts`](https://github.com/OpenZeppelin/stellar-contracts) library as of `v0.8.0`.
 
-:::caution
+<Warning>
 
 OpenZeppelin's [v0.8.0 audit](https://github.com/OpenZeppelin/stellar-contracts/blob/v0.8.0/audits/Stellar%20Contracts%20Library%20v0.8.0%20Audit.pdf) covers the confidential token contracts and circuits. The current verifier accepts only non-zero-knowledge UltraHonk proofs, so OpenZeppelin does not guarantee that proofs keep balances and amounts private. Zero-knowledge verification is in progress. Read the [zero-knowledge setting](https://github.com/OpenZeppelin/stellar-contracts/blob/v0.8.0/packages/confidential/README.md#zero-knowledge-setting) notes before you use confidential tokens with real assets. The demo linked below targets the earlier developer preview and runs on Testnet only.
 
-:::
+</Warning>
 
 Learn more about our work with OpenZeppelin in the post [Developer Preview: Confidential Tokens on Stellar](https://stellar.org/blog/developers/developer-preview-confidential-tokens-on-stellar), published on June 29, 2026 during the Testnet preview, and watch the [Developer Preview stream with OpenZeppelin](https://youtu.be/nfbr3KuYqPE?si=n5jX6g3-azW4Lp1B) that explains more about the architecture and design choices.
 
@@ -98,4 +96,4 @@ Stellar's Protocol [22](https://stellar.org/blog/developers/announcing-protocol-
 
 **Poseidon / Poseidon2** ([CAP-75](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0075.md)) — permutation primitives for building hash functions designed for ZK circuits. Far more efficient inside proofs than SHA-256, used for commitments, Merkle trees, and nullifiers. Available as host functions (`poseidon_permutation` and `poseidon2_permutation`) from which developers construct the hash function their application needs, keeping hashing logic consistent between off-chain circuits and onchain contracts.
 
-Navigate to [this page](../apps/zk.mdx) For full details and code examples.
+Navigate to [this page](../apps/zk) For full details and code examples.
diff --git a/docs/build/apps/swift-payment-app.mdx b/docs/build/apps/swift-payment-app.mdx
index fe5483a16..8901d869b 100644
--- a/docs/build/apps/swift-payment-app.mdx
+++ b/docs/build/apps/swift-payment-app.mdx
@@ -1,6 +1,6 @@
 ---
 title: Build a Payment App with Swift
-sidebar_position: 41
+description: "SwiftBasicPay is an open-source example iOS payment application that showcases how to integrate Stellar's powerful payment infrastructure into native Swift..."
 ---
 
 ## SwiftBasicPay
@@ -55,7 +55,7 @@ The tutorial covers secure data storage, authentication, account creation, asset
 - [SwiftBasicPay Tutorial](https://github.com/Soneso/SwiftBasicPay/tree/main/tutorial)
 - [Stellar Wallet SDK for Swift](https://github.com/Soneso/stellar-swift-wallet-sdk)
 - [Stellar iOS SDK](https://github.com/Soneso/stellar-ios-mac-sdk)
-- [Stellar Wallet SDK Documentation](../apps/wallet/README.mdx)
+- [Stellar Wallet SDK Documentation](/docs/build/apps/wallet)
 
 ## Contributing
 
diff --git a/docs/build/apps/wallet/CONTRIBUTING.md b/docs/build/apps/wallet/CONTRIBUTING.md
deleted file mode 100644
index b3251d3d4..000000000
--- a/docs/build/apps/wallet/CONTRIBUTING.md
+++ /dev/null
@@ -1,96 +0,0 @@
-# Contributing guide
-
-Thank you for contributing to the Stellar Wallet documentation! To get started,
-please first read [main README](../../../README.md) guide.
-
-This documentation is mainly for the Wallet SDK and it's usages to integrate
-with various SEPs.
-
-The document is structured to be language-agnostic, but with the components
-listed below we can add language-specific logic into the document.
-
-Generally, text should be applicable to all of supported programming languages,
-but for differences special `<LanguageSpecific/>` component can be used (read
-more below)
-
-## Wallet guide components
-
-### Header
-
-Header is a special .mdx file that should be included on all pages. It contains:
-
-- Language buttons
-- A general guide on using this buttons
-- Optional warning for languages in progress
-
-On all new pages, Header should be the first element. Optionally, provide list
-of languages that are work in progress:
-
-```mdxjs
-<Header WIPLangs={["ts", "dart"]}/>
-```
-
-### LanguageButtons
-
-This component is a part of the header. It allows to switch between programming
-languages. Current language is stored as a cookie.
-
-### WalletGuideWarn
-
-This component puts a warning if language is in progress for this section.
-Please use `WIPLangs` property to enable it for a language for the page.
-
-### WalletCodeExample
-
-This is improved `CodeExample` component. It currently supports dynamic
-switching between TypeScript, Kotlin, Flutter and Swift code snippets (depending
-on the user selected language). It will also generate placeholder if code
-snippet is missing. Here's an example on how to use it:
-
-````mdxjs
-<CodeExample>
-
-​```kotlin
-// Kotlin example here
-​```
-
-
-​```ts
-// TypeScript example here
-​```
-
-// Flutter example is replaced with an auto-generated notice
-
-</CodeExample>
-````
-
-For a regular code examples (non Wallet SDK) please use vanilla `CodeExample`
-component.
-
-### LanguageSpecific
-
-This component allows to render parts of documentation based on selected code.
-To get started, crete 2 files in `component` directory:
-
-```md
-// ./component/kt/hello.mdx Hello, Kotlin!
-```
-
-```md
-// ./component/ts/hello.mdx Hello, TypeScript!
-```
-
-Then, in the main document import both files and LanguageSpecific component:
-
-```mdxjs
-// main.mdx
-import {LanguageSpecific} from "@site/src/components/LanguageSpecific";
-import KtHello from "./component/kt/hello.mdx";
-import TsHello from "./component/ts/hello.mdx";
-
-<LanguageSpecific kt={<KtHello/>} ts={<TsHello/>} /
-```
-
-When user selects Kotlin, "Hello, Kotlin!" is going to be rendered, when
-TypeScript is selected — "Hello, TypeScript!". Finally, for Flutter and Swift,
-nothing would be rendered.
diff --git a/docs/build/apps/wallet/README.mdx b/docs/build/apps/wallet/README.mdx
deleted file mode 100644
index 005a5509a..000000000
--- a/docs/build/apps/wallet/README.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-sidebar_position: 30
----
-
-import DocCardList from "@theme/DocCardList";
-
-# Build a Wallet with the Wallet SDK
-
-Use the Wallet SDK to integrate with the Stellar blockchain and connect to anchors using your preferred programming language.
-
-<DocCardList />
diff --git a/docs/build/apps/wallet/component/dart/configClient.mdx b/docs/build/apps/wallet/component/dart/configClient.mdx
deleted file mode 100644
index 87e9157a9..000000000
--- a/docs/build/apps/wallet/component/dart/configClient.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
-### Configuring the Client
-
-The Flutter Wallet SDK uses the standard Client from the [http package](https://pub.dev/packages/http) for all network requests (excluding Horizon, where the Flutter Stellar SDK's HTTP client is used).
-
-Optionally, you can set your own client from [http package](https://pub.dev/packages/http) to be used across the app.
-
-The client can be globally configured:
-
-```dart
-import 'package:http/http.dart';
-// ...
-
-// init and configure your HTTP client
-// var myClient = ...
-
-// set as default HTTP client
-var appConfig = ApplicationConfiguration(defaultClient: myClient);
-var walletCustomClient = Wallet(StellarConfiguration.testNet, applicationConfiguration: appConfig);
-```
-
-Some [test cases](https://github.com/Soneso/stellar_wallet_flutter_sdk/tree/main/test) of this SDK use for example the `MockClient`.
diff --git a/docs/build/apps/wallet/component/header.mdx b/docs/build/apps/wallet/component/header.mdx
deleted file mode 100644
index 1864d3d4f..000000000
--- a/docs/build/apps/wallet/component/header.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
-import { LanguageButtons } from "@site/src/components/LanguageButtons";
-import { WalletGuideWarn } from "@site/src/components/WalletGuideWarn";
-
-<LanguageButtons />
-
-:::info
-
-This guide is available on four different programming languages: Typescript, Kotlin, Flutter (Dart) and Swift. You can change the shown version on each page via the buttons above.
-
-:::
-
-<WalletGuideWarn WIPLangs={props.WIPLangs} />
diff --git a/docs/build/apps/wallet/component/kt/configClient.mdx b/docs/build/apps/wallet/component/kt/configClient.mdx
deleted file mode 100644
index b7a087f07..000000000
--- a/docs/build/apps/wallet/component/kt/configClient.mdx
+++ /dev/null
@@ -1,42 +0,0 @@
-### Configuring the Client
-
-The Kotlin wallet SDK uses the [ktor client](https://ktor.io/docs/getting-started-ktor-client.html) for all network requests (excluding Horizon, where the Stellar SDK's HTTP client is used). Currently, the okhttp engine is configured to be used with the client. You can read more about how to configure the ktor client [here](https://ktor.io/docs/create-client.html#configure-client).
-
-For example, the client can be globally configured:
-
-```kotlin
-val walletCustomClient =
-  Wallet(
-    StellarConfiguration.Testnet,
-    ApplicationConfiguration(
-      defaultClientConfig = {
-        engine { this.config { this.connectTimeout(Duration.ofSeconds(10)) } }
-        install(HttpRequestRetry) {
-          retryOnServerErrors(maxRetries = 5)
-          exponentialDelay()
-        }
-      }
-    )
-  )
-```
-
-This Kotlin code will set the connect timeout to ten seconds via the [okhttp configuration](https://ktor.io/docs/http-client-engines.html#okhttp) and also installs the [retry plugin](https://ktor.io/docs/client-retry.html). You can also specify client configuration for specific wallet SDK classes.
-
-For example, to change connect timeout when connecting to some anchor server:
-
-```kotlin
-val anchorCustomClient =
-  walletCustomClient.anchor("example.com") {
-    engine { this.config { this.connectTimeout(Duration.ofSeconds(30)) } }
-  }
-```
-
-### Closing Resources
-
-After the wallet class is no longer used, it's necessary to close all clients used by it. While in some applications it may not be required (e.g. the wallet lives for the whole lifetime of the application), in other cases it can be required. If your wallet class is short-lived, it's recommended to close client resources using a close function:
-
-```kotlin
-fun closeWallet() {
-  wallet.close()
-}
-```
diff --git a/docs/build/apps/wallet/component/ts/configClient.mdx b/docs/build/apps/wallet/component/ts/configClient.mdx
deleted file mode 100644
index 25526e8c0..000000000
--- a/docs/build/apps/wallet/component/ts/configClient.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
-### Configuring the Client
-
-The Typescript wallet SDK uses the [axios client](https://axios-http.com/docs/intro) for all network requests. You can read more about how to configure the axios client [here](https://axios-http.com/docs/instance).
-
-For example, we can configure our axios client to be globally configured with a timeout:
-
-```typescript
-const customClient: AxiosInstance = axios.create({
-  timeout: 1000,
-});
-let appConfig = new ApplicationConfiguration(DefaultSigner, customClient);
-let wal = new Wallet({
-  stellarConfiguration: StellarConfiguration.TestNet(),
-  applicationConfiguration: appConfig,
-});
-```
-
-You can find more [configure options here.](https://axios-http.com/docs/req_config)
diff --git a/docs/build/apps/wallet/contributing.mdx b/docs/build/apps/wallet/contributing.mdx
new file mode 100644
index 000000000..166325a70
--- /dev/null
+++ b/docs/build/apps/wallet/contributing.mdx
@@ -0,0 +1,78 @@
+---
+title: "Contribution Guide"
+description: "Thank you for contributing to the Stellar Wallet documentation! To get started, please first read [main README](/docs) guide."
+---
+
+This documentation is mainly for the Wallet SDK and it's usages to integrate with various SEPs.
+
+The document is structured to be language-agnostic, but with the components listed below we can add language-specific logic into the document.
+
+Generally, text should be applicable to all of supported programming languages, but for differences special `` component can be used (read more below)
+
+## Wallet guide components
+
+### Header
+
+Header is a special .mdx file that should be included on all pages. It contains:
+
+- Language buttons
+- A general guide on using this buttons
+- Optional warning for languages in progress
+
+On all new pages, Header should be the first element. Optionally, provide list of languages that are work in progress:
+
+```mdxjs
+<Header WIPLangs={["ts", "dart"]}/>
+```
+
+### LanguageButtons
+
+This component is a part of the header. It allows to switch between programming languages. Current language is stored as a cookie.
+
+### WalletGuideWarn
+
+This component puts a warning if language is in progress for this section. Please use `WIPLangs` property to enable it for a language for the page.
+
+### WalletCodeExample
+
+This is improved `CodeExample` component. It currently supports dynamic switching between TypeScript, Kotlin, Flutter and Swift code snippets (depending on the user selected language). It will also generate placeholder if code snippet is missing. Here's an example on how to use it:
+
+````mdxjs
+<CodeGroup>
+
+​```kotlin
+// Kotlin example here
+​```
+
+
+​```ts
+// TypeScript example here
+​```
+
+// Flutter example is replaced with an auto-generated notice
+
+</CodeGroup>
+````
+
+For a regular code examples (non Wallet SDK) please use vanilla `CodeExample` component.
+
+### LanguageSpecific
+
+This component allows to render parts of documentation based on selected code. To get started, crete 2 files in `component` directory:
+
+```md
+// ./component/kt/hello.mdx Hello, Kotlin!
+```
+
+```md
+// ./component/ts/hello.mdx Hello, TypeScript!
+```
+
+Then, in the main document import both files and LanguageSpecific component:
+
+```mdxjs
+// main.mdx
+} ts={<TsHello/>} /
+```
+
+When user selects Kotlin, "Hello, Kotlin!" is going to be rendered, when TypeScript is selected — "Hello, TypeScript!". Finally, for Flutter and Swift, nothing would be rendered.
diff --git a/docs/build/apps/wallet/index.mdx b/docs/build/apps/wallet/index.mdx
new file mode 100644
index 000000000..00beb4cb9
--- /dev/null
+++ b/docs/build/apps/wallet/index.mdx
@@ -0,0 +1,52 @@
+---
+title: Build a Wallet with the Wallet SDK
+description: "Use the Wallet SDK to integrate with the Stellar blockchain and connect to anchors using your preferred programming language."
+---
+
+<CardGroup cols={2}>
+  <Card title="Overview" icon="file-lines" href="/docs/build/apps/wallet/overview">
+
+    In this guide we will use the Wallet SDK to integrate with the Stellar blockchain and connect to anchors.
+
+  </Card>
+  <Card title="Getting Started" icon="file-lines" href="/docs/build/apps/wallet/intro">
+
+    Learn how to build a wallet application on the Stellar network with the Wallet SDK. Explore key features, setup steps, Stellar fundamentals, and anchor basics.
+
+  </Card>
+  <Card title="Stellar Network" icon="file-lines" href="/docs/build/apps/wallet/stellar">
+
+    In the previous section we learned how to create a wallet and a Stellar object that provides a connection to Horizon.
+
+  </Card>
+  <Card title="Stellar Authentication" icon="file-lines" href="/docs/build/apps/wallet/sep10">
+
+    Wallets connect to anchors using a standard way of authentication via the Stellar network defined by the SEP-10 standard.
+
+  </Card>
+  <Card title="Hosted Deposit and Withdrawal" icon="file-lines" href="/docs/build/apps/wallet/sep24">
+
+    The SEP-24 standard defines the standard way for anchors and wallets to interact on behalf of users.
+
+  </Card>
+  <Card title="Recovery" icon="file-lines" href="/docs/build/apps/wallet/sep30">
+
+    The Sep-30 standard defines the standard way for an individual (e.g., a user or wallet) to regain access to their Stellar account after losing its private...
+
+  </Card>
+  <Card title="Programmatic Deposit and Withdrawal" icon="file-lines" href="/docs/build/apps/wallet/sep6">
+
+    The SEP-6 standard defines a way for anchors and wallets to interact on behalf of users.
+
+  </Card>
+  <Card title="Quote" icon="file-lines" href="/docs/build/apps/wallet/sep38">
+
+    The SEP-38 standard defines a way for anchors to provide quotes for the exchange of an off-chain asset and a different on-chain asset, and vice versa.
+
+  </Card>
+  <Card title="URI Scheme to facilitate delegated signing" icon="file-lines" href="/docs/build/apps/wallet/sep7">
+
+    The Sep-7 standard defines a way for a non-wallet application to construct a URI scheme that represents a specific transaction for an account to sign.
+
+  </Card>
+</CardGroup>
diff --git a/docs/build/apps/wallet/intro.mdx b/docs/build/apps/wallet/intro.mdx
index e44777c6c..0727f52ea 100644
--- a/docs/build/apps/wallet/intro.mdx
+++ b/docs/build/apps/wallet/intro.mdx
@@ -1,24 +1,19 @@
 ---
-title: "The First Step to Building a Wallet App on Stellar with the Wallet SDK"
-sidebar_position: 20
-sidebar_label: Getting Started
+title: Getting Started
+"og:title": The First Step to Building a Wallet App on Stellar with the Wallet SDK
 description: "Learn how to build a wallet application on the Stellar network with the Wallet SDK. Explore key features, setup steps, Stellar fundamentals, and anchor basics."
 ---
 
-# Getting Started
-
-import { LanguageSpecific } from "@site/src/components/LanguageSpecific";
-import { WalletCodeExample } from "@site/src/components/WalletCodeExample";
-import Header from "./component/header.mdx";
-import KtInstall from "./component/kt/install.mdx";
-import TsInstall from "./component/ts/install.mdx";
-import DartInstall from "./component/dart/install.mdx";
-import SwiftInstall from "./component/swift/install.mdx";
-import KtHttpConfig from "./component/kt/httpConfig.mdx";
-import KtConfigClient from "./component/kt/configClient.mdx";
-import TsConfigClient from "./component/ts/configClient.mdx";
-import DartConfigClient from "./component/dart/configClient.mdx";
-import AllowHttpInfo from "./component/ts/allowHttpInfo.mdx";
+import Header from "/snippets/wallet/header.mdx";
+import TsInstall from "/snippets/wallet/ts/install.mdx";
+import KtInstall from "/snippets/wallet/kt/install.mdx";
+import DartInstall from "/snippets/wallet/dart/install.mdx";
+import SwiftInstall from "/snippets/wallet/swift/install.mdx";
+import KtHttpConfig from "/snippets/wallet/kt/httpConfig.mdx";
+import KtConfigClient from "/snippets/wallet/kt/configClient.mdx";
+import TsConfigClient from "/snippets/wallet/ts/configClient.mdx";
+import DartConfigClient from "/snippets/wallet/dart/configClient.mdx";
+import AllowHttpInfo from "/snippets/wallet/ts/allowHttpInfo.mdx";
 
 <Header />
 
@@ -26,68 +21,120 @@ import AllowHttpInfo from "./component/ts/allowHttpInfo.mdx";
 
 First, you need to add the SDK dependency to your project.
 
-<LanguageSpecific
-  kt={<KtInstall />}
-  ts={<TsInstall />}
-  flutter={<DartInstall />}
-  swift={<SwiftInstall />}
-/>
+<Tabs>
+<Tab title="TypeScript">
+
+<TsInstall />
+
+</Tab>
+<Tab title="Kotlin">
+
+<KtInstall />
+
+</Tab>
+<Tab title="Flutter">
+
+<DartInstall />
+
+</Tab>
+<Tab title="Swift">
+
+<SwiftInstall />
+
+</Tab>
+</Tabs>
 
 ## Working with the SDK
 
 Let's start with the main class that provides all SDK functionality. It's advised to have a singleton wallet object shared across the application. Creating a wallet with a default configuration connected to Stellar's Testnet is simple:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kotlin
 val wallet = Wallet(StellarConfiguration.Testnet)
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```ts
 let wallet = walletSdk.Wallet.TestNet();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var wallet = Wallet.testNet;
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let wallet = Wallet.testNet
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 The wallet instance can be further configured. For example, to connect to the public network:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kotlin
 val walletTestnet = Wallet(StellarConfiguration(Network.TESTNET, "https://horizon-testnet.stellar.org"))
 ```
 
+<KtHttpConfig />
+
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 let wallet = new Wallet({
   stellarConfiguration: StellarConfiguration.MainNet(),
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var wallet = Wallet(StellarConfiguration.publicNet);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let wallet = Wallet(stellarConfig: StellarConfig.publicNet)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
+
+### Configuring the Client
 
-<LanguageSpecific kt={<KtHttpConfig />} />
+<Tabs>
+<Tab title="Kotlin">
 
-<LanguageSpecific
-  kt={<KtConfigClient />}
-  ts={<TsConfigClient />}
-  flutter={<DartConfigClient />}
-/>
+<KtConfigClient />
+
+</Tab>
+<Tab title="TypeScript">
+
+<TsConfigClient />
+
+</Tab>
+<Tab title="Flutter">
+
+<DartConfigClient />
+
+</Tab>
+</Tabs>
 
 ## Stellar Basics
 
@@ -95,65 +142,94 @@ The wallet SDK provides some extra functionality on top of the existing [Horizon
 
 To interact with the Horizon instance configured in the previous steps, simply do:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kotlin
 val stellar = wallet.stellar()
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const stellar = wallet.stellar();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var stellar = wallet.stellar();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let stellar = wallet.stellar
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 This example will create a Stellar class that manages the connection to Horizon service.
 
-:::note
+<Note>
 
 Default configuration connects to the public Stellar Horizon instance. You can change this behavior as described [above](#working-with-the-sdk).
 
-:::
+</Note>
 
-You can read more about working with the Stellar network in the [respective section](./stellar.mdx).
+You can read more about working with the Stellar network in the [respective section](./stellar).
 
 ## Anchor Basics
 
 Primary use of the SDK is to provide an easy way to connect to anchors via sets of protocols known as SEPs. Let's look into connecting to the Stellar test anchor:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kotlin
 val anchor = wallet.anchor("https://testanchor.stellar.org")
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 let anchor = wallet.anchor({ homeDomain: "testanchor.stellar.org" });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var anchor = wallet.anchor("testanchor.stellar.org")
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let anchor = wallet.anchor(homeDomain: "testanchor.stellar.org")
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
+
+<Tabs>
+<Tab title="TypeScript">
 
-<LanguageSpecific ts={<AllowHttpInfo />} />
+<AllowHttpInfo />
+
+</Tab>
+</Tabs>
 
 And the most basic interaction of fetching a [SEP-1]: Stellar Info File:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kotlin
 suspend fun anchorToml(): TomlInfo {
@@ -161,19 +237,29 @@ suspend fun anchorToml(): TomlInfo {
 }
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 let resp = await anchor.sep1();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var resp = await anchor.sep1();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let resp = try await anchor.sep1
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Below you can find all the SEPs the anchor class currently supports:
 
diff --git a/docs/build/apps/wallet/overview.mdx b/docs/build/apps/wallet/overview.mdx
index c88c719f2..aca28e2b3 100644
--- a/docs/build/apps/wallet/overview.mdx
+++ b/docs/build/apps/wallet/overview.mdx
@@ -1,16 +1,16 @@
 ---
 title: Overview
-sidebar_position: 10
+description: "In this guide we will use the Wallet SDK to integrate with the Stellar blockchain and connect to anchors."
 ---
 
-import Header from "./component/header.mdx";
+import Header from "/snippets/wallet/header.mdx";
 
 <Header />
 
 In this guide we will use the Wallet SDK to integrate with the Stellar blockchain and connect to anchors.
 
-:::note
+<Note>
 
-This documentation walks you through how to build a wallet without using smart contracts. To build with smart contracts, navigate to the [Smart Contracts section](../../smart-contracts/overview.mdx).
+This documentation walks you through how to build a wallet without using smart contracts. To build with smart contracts, navigate to the [Smart Contracts section](../../smart-contracts/overview).
 
-:::
+</Note>
diff --git a/docs/build/apps/wallet/sep10.mdx b/docs/build/apps/wallet/sep10.mdx
index 45e2ebf0f..6f4095ce8 100644
--- a/docs/build/apps/wallet/sep10.mdx
+++ b/docs/build/apps/wallet/sep10.mdx
@@ -1,14 +1,12 @@
 ---
 title: Stellar Authentication
-sidebar_position: 40
+description: "Wallets connect to anchors using a standard way of authentication via the Stellar network defined by the [SEP-10] standard."
 ---
 
-import { LanguageSpecific } from "@site/src/components/LanguageSpecific";
-import { WalletCodeExample } from "@site/src/components/WalletCodeExample";
-import Header from "./component/header.mdx";
-import GlobalClientSignerKt from "./component/kt/globalSigner.mdx";
-import GlobalClientSignerTs from "./component/ts/globalSigner.mdx";
-import GlobalClientSignerSwift from "./component/swift/globalSigner.mdx";
+import Header from "/snippets/wallet/header.mdx";
+import GlobalClientSignerKt from "/snippets/wallet/kt/globalSigner.mdx";
+import GlobalClientSignerTs from "/snippets/wallet/ts/globalSigner.mdx";
+import GlobalClientSignerSwift from "/snippets/wallet/swift/globalSigner.mdx";
 
 <Header />
 
@@ -18,9 +16,11 @@ This guide will cover all ways to use SEP-10 to authenticate with an anchor.
 
 ## Creating Authentication Key
 
-:::info[Custodial wallets only]
+<Info>
 
-:::
+**Custodial wallets only**
+
+</Info>
 
 First, let's create an authentication key. While you can use the same key for authentication and sending funds, it's recommended to split the responsibilities. In your application, you will have one or more fund keypairs (keypairs for the accounts that hold funds and initiate and receive transactions) and one authentication key.
 
@@ -34,29 +34,41 @@ Let's do a basic authentication. In this example, we will use wallet SDK to crea
 
 First, let's create an `anchor` object to work with the anchor you are integrating with. In this example, we will be using a reference anchor implementation with the home domain `testanchor.stellar.org`
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kotlin
 val anchor = wallet.anchor("https://testanchor.stellar.org")
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const anchor = wallet.anchor({ homeDomain: "https://testanchor.stellar.org" });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final anchor = wallet.anchor("testanchor.stellar.org");
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let anchor = wallet.anchor(homeDomain: "testanchor.stellar.org")
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Next, authenticate with the `authKey` created earlier:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kotlin
 val authKey = SigningKeyPair.fromSecret("my secret key")
@@ -66,6 +78,9 @@ suspend fun getAuthToken(): AuthToken {
 }
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const authKey = SigningKeypair.fromSecret("my secret key");
 const sep10 = await anchor.sep10();
@@ -73,6 +88,9 @@ const sep10 = await anchor.sep10();
 const authToken = await sep10.authenticate({ accountKp: authKey });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final authKey = SigningKeyPair.fromSecret("my secret key");
 final sep10 = await anchor.sep10();
@@ -80,6 +98,9 @@ final sep10 = await anchor.sep10();
 final authToken = await sep10.authenticate(authKey);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let authKey = try SigningKeyPair(secretKey: "my secret key")
 let sep10 = try await anchor.sep10
@@ -87,7 +108,8 @@ let sep10 = try await anchor.sep10
 let authToken = try await sep10.authenticate(userKeyPair: authKey)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 For non-custodial wallets, you want to use the user's private key as an `authKey`.
 
@@ -97,15 +119,17 @@ The home domain is the optional parameter for SEP-10 authentication, when a sing
 
 ## Client Domain (Optional)
 
-:::info[Non-custodial wallets only]
+<Info>
+
+**Non-custodial wallets only**
 
-:::
+</Info>
 
-:::caution
+<Warning>
 
 Some anchors may require the `client_domain` to always be present as part of the request, even for non-custodial wallets.
 
-:::
+</Warning>
 
 Client domain is used by anchors to verify the origin of user's request (which wallet this user is using?). This is particularly useful for anchors for integrating with non-custodial wallets.
 
@@ -115,7 +139,8 @@ Supporting `client_domain` comes in two parts, the wallet's client and the walle
 
 First, let's implement the client side. In this example we will connect to a remote signer that signs transactions on the endpoint `https://demo-wallet-server.stellar.org/sign` for the client domain `demo-wallet-server.stellar.org`.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kotlin
 val signer = WalletSigner.DomainSigner("https://demo-wallet-server.stellar.org/sign") {}
@@ -127,6 +152,9 @@ suspend fun getAuthToken(): AuthToken {
 }
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const signer = new DomainSigner(
   "https://demo-wallet-server.stellar.org/sign",
@@ -142,6 +170,9 @@ const getAuthToken = async () => {
 };
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final signer = DomainSigner("https://demo-wallet-server.stellar.org/sign");
 final sep10 = await anchor.sep10();
@@ -150,6 +181,9 @@ final authToken = await sep10.authenticate(userKeyPair,
   clientDomainSigner: signer, clientDomain: "demo-wallet-server.stellar.org");
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let signer = try DomainSigner(url: "https://demo-wallet-server.stellar.org/sign")
 let sep10 = try await anchor.sep10
@@ -159,28 +193,36 @@ let authToken = try await sep10.authenticate(userKeyPair: authKey,
                                              clientDomainSigner: signer)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
-:::danger
+<Danger>
 
 The demo-wallet signing endpoint is not protected for anybody to use. Your production URL must be protected, otherwise anybody could impersonate your wallet's user.
 
-:::
+</Danger>
 
 Let's add authentication with a bearer token. Simply update the request transformer:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kotlin
 val signer = WalletSigner.DomainSigner("https://demo-wallet-server.stellar.org/sign") { bearerAuth("authToken") }
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const signer = new DomainSigner("https://demo-wallet-server.stellar.org/sign", {
   Authorization: `Bearer ${authToken}`,
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 Map<String, String> requestHeaders = {
   "Authorization": "Bearer $authToken",
@@ -191,6 +233,9 @@ var signer = DomainSigner("https://demo-wallet-server.stellar.org/sign",
   requestHeaders: requestHeaders);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let requestHeaders = ["Authorization" : "Bearer \(authToken)"]
 
@@ -198,13 +243,26 @@ let signer = try DomainSigner(url: "https://demo-wallet-server.stellar.org/sign"
                               requestHeaders: requestHeaders)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
+
+<Tabs>
+<Tab title="TypeScript">
+
+<GlobalClientSignerTs />
+
+</Tab>
+<Tab title="Kotlin">
+
+<GlobalClientSignerKt />
+
+</Tab>
+<Tab title="Swift">
+
+<GlobalClientSignerSwift />
 
-<LanguageSpecific
-  kt={<GlobalClientSignerKt />}
-  ts={<GlobalClientSignerTs />}
-  swift={<GlobalClientSignerSwift />}
-/>
+</Tab>
+</Tabs>
 
 ### Server Side
 
diff --git a/docs/build/apps/wallet/sep24.mdx b/docs/build/apps/wallet/sep24.mdx
index 34744bfe3..c68e172e7 100644
--- a/docs/build/apps/wallet/sep24.mdx
+++ b/docs/build/apps/wallet/sep24.mdx
@@ -1,13 +1,10 @@
 ---
 title: Hosted Deposit and Withdrawal
-sidebar_position: 50
+description: "The [SEP-24] standard defines the standard way for anchors and wallets to interact on behalf of users."
 ---
 
-import { LanguageSpecific } from "@site/src/components/LanguageSpecific";
-import KtWatcher from "./component/kt/watcher.mdx";
-
-import { WalletCodeExample } from "@site/src/components/WalletCodeExample";
-import Header from "./component/header.mdx";
+import Header from "/snippets/wallet/header.mdx";
+import KtWatcher from "/snippets/wallet/kt/watcher.mdx";
 
 <Header />
 
@@ -19,29 +16,41 @@ During the flow, a wallet makes several requests to the anchor, and finally rece
 
 Let's start with getting an instance of `Sep24` class, responsible for all SEP-24 interactions:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kotlin
 val sep24 = anchor.sep24()
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const sep24 = await anchor.sep24();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final sep24 = await anchor.sep24();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let sep24 = anchor.sep24
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 First, let's get the information about the anchor's support for [SEP-24]. This request doesn't require authentication, and will return generic info, such as supported currencies, and features supported by the anchor. You can get a full list of returned fields in the [SEP-24 specification](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md#info).
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 suspend fun getAnchorServices(): AnchorServiceInfo {
@@ -49,21 +58,31 @@ suspend fun getAnchorServices(): AnchorServiceInfo {
 }
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const getAnchorServices = async (): Promise<AnchorServiceInfo> => {
   return await anchor.getServicesInfo();
 };
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final servicesInfo = await sep24.getServiceInfo();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let servicesInfo = try await sep24.info
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 ## Interactive Flows
 
@@ -71,12 +90,16 @@ Before getting started, make sure you have connected to the anchor and received
 
 To initiate an operation, we need to know an asset. You may want to hard-code it, or get it dynamically from the anchor's info file, like shown below (for USDC):
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 val asset = info.currencies.first { it.code == "USDC" }.assetId
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 import { IssuedAssetId } from "@stellar/typescript-wallet-sdk";
 
@@ -95,33 +118,44 @@ if (!currency?.code || !currency?.issuer) {
 const asset = new IssuedAssetId(currency.code, currency.issuer);
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final asset = info.currencies.firstWhere((it)=>it.code=='USDC').assetId;
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let info = try await anchor.info
 let asset = try info.currencies?.first(where: {$0.code == "USDC"})?.assetId
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
-:::info
+<Info>
 
-Before starting with the deposit flow, make sure that the user account has [established a trustline](./stellar.mdx#modify-assets-trustlines) for the asset you are working with.
+Before starting with the deposit flow, make sure that the user account has [established a trustline](./stellar#modify-assets-trustlines) for the asset you are working with.
 
-:::
+</Info>
 
 ### Basic Flow
 
 Let's start with a basic deposit:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 val deposit = sep24.deposit(asset, authToken)
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const deposit = await sep24.deposit({
   assetCode: asset.code,
@@ -129,47 +163,66 @@ const deposit = await sep24.deposit({
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final deposit = await sep24.deposit(asset, authToken);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let deposit = try await sep24.deposit(assetId: asset, authToken: authToken)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 As a result, you will get an [interactive response](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md#deposit-and-withdraw-shared-responses) from the anchor.
 
 Open the received URL in an iframe and save the transaction ID for future reference:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 val url = deposit.url
 val id = deposit.id
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const url = deposit.url;
 const id = deposit.id;
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final url = deposit.url;
 final id = deposit.id;
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let url = deposit.url
 let id = deposit.id
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Similarly to the deposit flow, a basic withdrawal flow has the same method signature and response type:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 val withdrawal = sep24.withdraw(asset, authToken)
@@ -177,6 +230,9 @@ val url = withdrawal.url
 val id = withdrawal.id
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const withdrawal = await sep24.withdraw({
   assetCode: asset.code,
@@ -186,37 +242,43 @@ const url = withdrawal.url;
 const id = withdrawal.id;
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final withdrawal = await sep24.withdraw(asset, authToken);
 final url = withdrawal.url;
 final id = withdrawal.id;
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let withdrawal = try await sep24.withdraw(assetId: asset, authToken: authToken)
 let url = withdrawal.url
 let id = withdrawal.id
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 ### Providing KYC Info
 
 To improve the user experience, the [SEP-24] standard supports passing user KYC to the anchor via [SEP-9]. In turn, the anchor will pre-fill this information in the interactive popup.
 
-:::info
+<Info>
 
 While [SEP-9] supports passing binary data, the current version of the SDK doesn't offer such functionality.
 
-:::
-
-:::note
+</Info>
+<Note>
 
 At the time, accepted [SEP-9] is not strictly typed yet. Improved typing will be offered in future versions.
 
-:::
-
-<WalletCodeExample>
+</Note>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 val sep9 = mapOf("email_address" to "mail@example.com")
@@ -224,6 +286,9 @@ val sep9 = mapOf("email_address" to "mail@example.com")
 val deposit = sep24.deposit(asset, authToken, sep9)
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const deposit = await sep24.deposit({
   assetCode: asset.code,
@@ -232,18 +297,25 @@ const deposit = await sep24.deposit({
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final deposit = await sep24.deposit(asset, authToken,
   extraFields: {"email_address": "mail@example.com"});
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let deposit = try await sep24.deposit(assetId: asset,
                                       authToken: authToken,
                                       extraFields: ["email_address" : "mail@example.com"])
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 ### Changing Stellar Transfer Account
 
@@ -251,7 +323,8 @@ By default, the Stellar transfer will be sent to the authenticated account (with
 
 While in most cases it's acceptable, some wallets may split their accounts. To do so, pass additional account (and optionally a memo):
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 suspend fun depositDifferentAccount(): InteractiveFlowResponse {
@@ -261,6 +334,9 @@ suspend fun depositDifferentAccount(): InteractiveFlowResponse {
 }
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 import { Memo, MemoText } from "@stellar/stellar-sdk";
 
@@ -275,12 +351,18 @@ const depositDifferentAccount = async (): Promise<InteractiveFlowResponse> => {
 };
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final recipientAccount = "G...";
 final deposit = await sep24.deposit(asset, authToken, destinationAccount: recipientAccount,
   destinationMemo: "my memo", destinationMemoType: MemoType.text);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let recipientAccount = "G..."
 let deposit = try await sep24.deposit(assetId: asset,
@@ -290,17 +372,22 @@ let deposit = try await sep24.deposit(assetId: asset,
                                       destinationMemoType: MemoType.text)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Similarly, for a withdrawal, the origin account of the Stellar transaction could be changed:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 val originAccount = "G..."
 val withdrawal = sep24.withdraw(asset, authToken, withdrawalAccount = originAccount)
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const originAccount = "G...";
 const withdrawal = await sep24.withdraw({
@@ -310,11 +397,17 @@ const withdrawal = await sep24.withdraw({
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final originAccount = "G...";
 final withdrawal = await sep24.withdraw(asset, authToken, withdrawalAccount: originAccount);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let originAccount = "G..."
 let withdrawal = try await sep24.withdraw(assetId: asset,
@@ -322,7 +415,8 @@ let withdrawal = try await sep24.withdraw(assetId: asset,
                                           withdrawalAccount: originAccount)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 ## Getting Transaction Info
 
@@ -334,13 +428,17 @@ Alternatively, some anchors support webhooks for notifications. Note that this f
 
 Let's look into how to use the wallet SDK to track transaction status changes. We will use `Watcher` class for this purpose. First, let's initialize watcher and start tracking a transaction.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 val watcher = sep24.watcher()
 val result = watcher.watchOneTransaction(authToken, "transaction id")
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const watcher = sep24.watcher();
 
@@ -354,28 +452,41 @@ const { stop, refresh } = watcher.watchOneTransaction({
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final watcher = sep24.watcher();
 final result = watcher.watchOneTransaction(authToken, "transaction id");
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let watcher = sep24.watcher()
 let result = watcher.watchOneTransaction(authToken: authToken,
                                          id: "transaction id")
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Alternatively, we can track multiple transactions for the same asset.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 val watcher = sep24.watcher()
 val result = watcher.watchAsset(getAuthToken(), asset)
 ```
 
+<KtWatcher />
+
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const watcher = sep24.watcher();
 
@@ -387,25 +498,31 @@ const { stop, refresh } = watcher.watchAllTransactions({
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final watcher = sep24.watcher();
 final result = watcher.watchAsset(authToken, asset);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let watcher = sep24.watcher()
 let result = watcher.watchAsset(authToken: authToken, asset: asset)
 ```
 
-</WalletCodeExample>
-
-<LanguageSpecific kt={<KtWatcher />} />
+</Tab>
+</Tabs>
 
 ### Fetching Transaction
 
 While `Watcher` class offers powerful tracking capabilities, sometimes it's required to just fetch a transaction (or transactions) once. The `Anchor` class allows you to fetch a transaction by ID, Stellar transaction ID, or external transaction ID:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 // "id" is the actual Anchor transaction id, all transactions should have it.
@@ -429,6 +546,9 @@ val transaction = sep24.getTransactionBy(authToken, stellarTransactionId = "tran
 val transaction = sep24.getTransactionBy(authToken, externalTransactionId = "transaction id")
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const transaction = await sep24.getTransactionBy({
   authToken,
@@ -465,10 +585,16 @@ const transaction = await anchor.sep24().getTransactionBy({
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final transaction = await sep24.getTransaction("transaction id", authToken);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 // "transactionId" is the actual Anchor transaction id, all transactions should have it.
 let transaction = try await anchor.sep24.getTransactionBy(authToken: authToken,
@@ -494,16 +620,21 @@ let transaction = try await anchor.sep24.getTransactionBy(authToken: authToken,
                                                           externalTransactionId: "external transaction id")
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 It's also possible to fetch transaction by the asset
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 val transactions = sep24.getTransactionsForAsset(asset, authToken)
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const transactions = await sep24.getTransactionsForAsset({
   authToken,
@@ -511,15 +642,22 @@ const transactions = await sep24.getTransactionsForAsset({
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final transactions = await sep24.getTransactionsForAsset(asset, authToken);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let transactions = try await sep24.getTransactionsForAsset(authToken: authToken, asset: asset)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 ## Submitting Withdrawal Transfer
 
@@ -527,12 +665,16 @@ Previously, we took a look at starting the withdrawal flow. Now, let's take a lo
 
 First, start the withdrawal:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 val withdrawal = sep24.withdraw(asset, authToken)
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const withdrawal = await sep24.withdraw({
   assetCode: asset.code,
@@ -540,45 +682,64 @@ const withdrawal = await sep24.withdraw({
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final withdrawal = await sep24.withdraw(asset, authToken);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let withdrawal = try await sep24.withdraw(assetId: asset, authToken: authToken)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Next, open an interactive url :
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 val url = withdrawal.url
 // open the url
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const url = withdrawal.url;
 // open the url
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final url = withdrawal.url
 // open the url
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let url = withdrawal.url
 // open the url
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 After that we need to wait until the anchor is ready to receive funds. To do so, we will be waiting until transaction reaches `pending_user_transfer_start` status. This code uses a simple watching (polling) mechanism with no bail-out condition. The application’s code should be more robust.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 val withdrawalWatcher = sep24.watcher().watchOneTransaction(authToken, withdrawal.id)
@@ -593,6 +754,9 @@ do {
 )
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const watcher = sep24.watcher();
 
@@ -630,6 +794,9 @@ const { refresh, stop } = watcher.watchAllTransactions({
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final withdrawalWatcher = sep24.watcher().watchOneTransaction(authToken, withdrawal.id);
 withdrawalWatcher.controller.stream.listen(
@@ -644,6 +811,9 @@ withdrawalWatcher.controller.stream.listen(
 );
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let watcher = anchor.sep24.watcher()
 let result = watcher.watchOneTransaction(authToken: authToken,
@@ -669,11 +839,13 @@ NotificationCenter.default.addObserver(self,
 }
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Next, sign and submit the Stellar transfer:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 val anchorTransaction = (statusChange.transaction as WithdrawalTransaction)
@@ -684,6 +856,9 @@ transfer.sign(keypair)
 stellar.submitTransaction(transfer)
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 // Import Horizon to get the result codes for error handling
 import { Horizon } from "@stellar/stellar-sdk";
@@ -796,6 +971,9 @@ onMessage: (transaction) => {
 };
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final tx = event.transaction as WithdrawalTransaction;
 
@@ -825,6 +1003,9 @@ final transaction = transactionBuilder.build()..sign(kp, network);
 final paymentResult = await sdk.submitTransaction(transaction);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 if let tx = statusChange.transaction as? WithdrawalTransaction {
     let paymentOperation = try PaymentOperation(sourceAccountId: sourceAccountId,
@@ -849,7 +1030,8 @@ if let tx = statusChange.transaction as? WithdrawalTransaction {
 }
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Where `keypair` is the SEP-10 authenticated account. If you want to transfer funds from a different address, refer to [Changing Stellar Transfer Account](#changing-stellar-transfer-account) section.
 
@@ -861,7 +1043,8 @@ Code for submitting transactions to Stellar should be developed thoughtfully. Th
 
 Finally, let's track transaction status updates. In this example we simply check if the transaction has been completed:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 var terminalStatus: TransactionStatus? = null
@@ -886,6 +1069,9 @@ if (terminalStatus != TransactionStatus.COMPLETED) {
 }
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const watcher = sep24.watcher();
 
@@ -909,6 +1095,9 @@ const { refresh, stop } = watcher.watchOneTransaction({
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final watcher = sep24.watcher().watchOneTransaction(authToken, withdrawal.id);
 watcher.controller.stream.listen(
@@ -931,6 +1120,9 @@ watcher.controller.stream.listen(
 );
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let watcher = anchor.sep24.watcher()
 let result = watcher.watchOneTransaction(authToken: authToken,
@@ -957,10 +1149,11 @@ NotificationCenter.default.addObserver(self,
 }
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 [sep-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
 [sep-10]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md
 [sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[stellar authentication]: ./sep10.mdx
-[submitting transactions and handling errors gracefully]: ../../../data/apis/horizon/api-reference/errors/error-handling.mdx
+[stellar authentication]: ./sep10
+[submitting transactions and handling errors gracefully]: ../../../data/apis/horizon/api-reference/errors/error-handling
diff --git a/docs/build/apps/wallet/sep30.mdx b/docs/build/apps/wallet/sep30.mdx
index 5fe5593e0..9b1c120f6 100644
--- a/docs/build/apps/wallet/sep30.mdx
+++ b/docs/build/apps/wallet/sep30.mdx
@@ -1,10 +1,9 @@
 ---
 title: Recovery
-sidebar_position: 60
+description: "The [Sep-30] standard defines the standard way for an individual (e.g., a user or wallet) to regain access to their Stellar account after losing its private..."
 ---
 
-import Header from "./component/header.mdx";
-import { WalletCodeExample } from "@site/src/components/WalletCodeExample";
+import Header from "/snippets/wallet/header.mdx";
 
 <Header />
 
@@ -14,7 +13,8 @@ The [Sep-30] standard defines the standard way for an individual (e.g., a user o
 
 First, let's create an account key, a device key, and a recovery key that will be attached to the account.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const accountKp = wallet.stellar().account().createKeypair();
@@ -22,31 +22,42 @@ const deviceKp = wallet.stellar().account().createKeypair();
 const recoveryKp = wallet.stellar().account().createKeypair();
 ```
 
+</Tab>
+<Tab title="Kotlin">
+
 ```kotlin
   val accountKp = wallet.stellar().account().createKeyPair()
   val deviceKp = wallet.stellar().account().createKeyPair()
   val recoveryKp = wallet.stellar().account().createKeyPair()
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var accountKp = wallet.stellar().account().createKeyPair();
 var deviceKp = wallet.stellar().account().createKeyPair();
 var recoveryKp = wallet.stellar().account().createKeyPair();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let accountKp = wallet.stellar.account.createKeyPair()
 let deviceKp = wallet.stellar.account.createKeyPair()
 let recoveryKp = wallet.stellar.account.createKeyPair()
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 The `accountKp` is the wallet's main account. The `deviceKp` we will be adding to the wallet as a signer so a device (eg. a mobile device a wallet is hosted on) can take control of the account. And the `recoveryKp` will be used to identify the key with the recovery servers.
 
 Next, let's identify the recovery servers and create our recovery object:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const server1Key = "server1";
@@ -68,6 +79,9 @@ const recovery = wallet.recovery({
 });
 ```
 
+</Tab>
+<Tab title="Kotlin">
+
 ```kotlin
 val first = RecoveryServerKey("first")
 val second = RecoveryServerKey("second")
@@ -77,6 +91,9 @@ val servers = mapOf(first to firstServer, second to secondServer)
 val recovery = wallet.recovery(servers)
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var first = RecoveryServerKey("first");
 var second = RecoveryServerKey("second");
@@ -86,6 +103,9 @@ var servers = {first:firstServer, second:secondServer};
 var recovery = wallet.recovery(servers);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let first = RecoveryServerKey(name: "first")
 let second = RecoveryServerKey(name: "second")
@@ -103,11 +123,13 @@ let servers = [first: firstServer, second:secondServer]
 let recovery = wallet.recovery(servers: servers)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Next, we need to define SEP-30 identities. In this example we are going to create an identity for both servers. Registering an identity tells the recovery server what identities are allowed to access the account.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const identity1 = {
@@ -131,6 +153,9 @@ const identity2 = {
 };
 ```
 
+</Tab>
+<Tab title="Kotlin">
+
 ```kotlin
   val identity1 = listOf(RecoveryAccountIdentity(
         RecoveryRole.OWNER,
@@ -145,6 +170,9 @@ const identity2 = {
     )
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var identity1 = [
   RecoveryAccountIdentity(RecoveryRole.owner, [
@@ -158,6 +186,9 @@ var identity2 = [
 ];
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let identity1 = [
     RecoveryAccountIdentity(role:RecoveryRole.owner,
@@ -172,7 +203,8 @@ let identity2 = [
 ]
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Here, stellar key and email are used as recovery methods. Other recovery servers may support phone as a recovery method as well.
 
@@ -180,7 +212,8 @@ You can read more about SEP-30 identities [here](https://github.com/stellar/stel
 
 Next, let's create a recoverable account:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const config = {
@@ -193,6 +226,9 @@ const config = {
 const recoverableWallet = await recovery.createRecoverableWallet(config);
 ```
 
+</Tab>
+<Tab title="Kotlin">
+
 ```kotlin
   val recoverableWallet =
     recovery.createRecoverableWallet(
@@ -206,6 +242,9 @@ const recoverableWallet = await recovery.createRecoverableWallet(config);
     )
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var recoverableWallet = await recovery.createRecoverableWallet(
     RecoverableWalletConfig(
@@ -218,6 +257,9 @@ var recoverableWallet = await recovery.createRecoverableWallet(
 );
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let config = RecoverableWalletConfig(accountAddress: accountKp,
                                     deviceAddress: deviceKp,
@@ -228,18 +270,20 @@ let config = RecoverableWalletConfig(accountAddress: accountKp,
 let recoverableWallet = try await recovery.createRecoverableWallet(config: config)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 With the given parameters, this function will create a transaction that will:
 
 1. Set `deviceKp` as the primary account key. Please note that the master key belonging to `accountKp` will be locked. `deviceKp` should be used as a primary signer instead.
-2. Set all operation thresholds to 10. You can read more about threshold in the [documentation](../../../learn/fundamentals/transactions/signatures-multisig.mdx#thresholds)
+2. Set all operation thresholds to 10. You can read more about threshold in the [documentation](../../../learn/fundamentals/transactions/signatures-multisig#thresholds)
 3. Use identities that were defined earlier on both servers. (That means, both server will accept SEP-10 authentication via `recoveryKp` as an auth method)
 4. Set device key weight to 10, and recovery server weight to 5. Given these account thresholds, both servers must be used to recover the account, as transaction signed by one will only have weight of 5, which is not sufficient to change account key.
 
 Finally, sign and submit transaction to the network:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 recoverableWallet.transaction.sign(accountKp.keypair);
@@ -247,31 +291,42 @@ recoverableWallet.transaction.sign(accountKp.keypair);
 await stellar.submitTransaction(recoverableWallet.transaction);
 ```
 
+</Tab>
+<Tab title="Kotlin">
+
 ```kotlin
   val tx = recoverableWallet.transaction.sign(accountKp)
 
   wallet.stellar().submitTransaction(tx)
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var transaction = recoverableWallet.transaction;
 transaction.sign(accountKp.keyPair, flutter_sdk.Network.TESTNET);
 await wallet.stellar().submitTransaction(transaction);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let transaction = recoverableWallet.transaction
 try transaction.sign(keyPair: accountKp.keyPair, network: Network.testnet)
 try await wallet.stellar.submitTransaction(signedTransaction: transaction)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 ## Get Account Info
 
 You can fetch account info from one or more servers. To do so, first we need to authenticate with a recovery server using the SEP-10 authentication method:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const authToken = await recovery
@@ -279,25 +334,36 @@ const authToken = await recovery
   .authenticate({ accountKp: recoveryKp });
 ```
 
+</Tab>
+<Tab title="Kotlin">
+
 ```kotlin
   val auth1 = recovery.sep10Auth(first).authenticate(recoveryKp)
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var sep10 = await recovery.sep10Auth(first);
 var authToken = await sep10.authenticate(recoveryKp);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let sep10 = try await recovery.sep10Auth(key: first)
 let authToken = try await sep10.authenticate(userKeyPair: recoveryKp)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Next, get account info using auth tokens:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const accountResp = await recovery.getAccountInfo(accountKp, {
@@ -305,28 +371,39 @@ const accountResp = await recovery.getAccountInfo(accountKp, {
 });
 ```
 
+</Tab>
+<Tab title="Kotlin">
+
 ```kotlin
   val accountInfo = recovery.getAccountInfo(account, mapOf(first to auth1))
 
   println("Recoverable info: $accountInfo")
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var accountInfo = await recovery.getAccountInfo(accountKp, {first: authToken.jwt});
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let accountInfo = try await recovery.getAccountInfo(accountAddress: accountKp,
                                                     auth: [first:auth1Token.jwt])
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Our second identity uses an email as an auth method. For that we can't use a [SEP-10] auth token for that server. Instead we need to use a token that ties the email to the user. For example, Firebase tokens are a good use case for this. To use this, the recovery signer server needs to be prepared to handle these kinds of tokens.
 
 Getting account info using these tokens is the same as before.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 // get token from firebase
@@ -337,6 +414,9 @@ const accountResp = await recovery.getAccountInfo(accountKp, {
 });
 ```
 
+</Tab>
+<Tab title="Kotlin">
+
 ```kotlin
   // get token from firebase
   val firebaseToken = AuthToken.from(<firebase token string>)
@@ -346,16 +426,23 @@ const accountResp = await recovery.getAccountInfo(accountKp, {
   println("Recoverable info: $accountInfo")
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var accountInfo = await recovery.getAccountInfo(accountKp, {second: <other token string>});
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let accountInfo = try await recovery.getAccountInfo(accountAddress: accountKp,
                                                     auth: [second:<other token string>])
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 ## Recover Wallet
 
@@ -363,7 +450,8 @@ Let's say we've lost our device key and need to recover our wallet.
 
 First, we need to authenticate with both recovery servers:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const authToken1 = await recovery
@@ -374,6 +462,9 @@ const authToken1 = await recovery
 const firebaseToken = AuthToken.from(<firebase token string>)
 ```
 
+</Tab>
+<Tab title="Kotlin">
+
 ```kotlin
   val auth1 = recovery.sep10Auth(first).authenticate(recoveryKp)
 
@@ -381,6 +472,9 @@ const firebaseToken = AuthToken.from(<firebase token string>)
   val firebaseToken = AuthToken.from(<firebase token string>)
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var sep10 = await recovery.sep10Auth(first);
 var authToken = await sep10.authenticate(recoveryKp);
@@ -389,6 +483,9 @@ var auth1 = authToken.jwt;
 var auth2 = "..."; // get other token e.g. firebase token
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let sep10 = try await recovery.sep10Auth(key: first)
 let authToken = try await sep10.authenticate(userKeyPair: recoveryKp)
@@ -397,34 +494,47 @@ let auth1 = authToken.jwt
 let auth2 = "..."; // get other token e.g. firebase token
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 We need to know the recovery signer addresses that will be used to sign the transaction. You can get them from either the recoverable wallet object we created earlier (`recoverableWallet.signers`), or via fetching account info from recovery servers.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const recoverySignerAddress1 = recoverableWallet.signers[0];
 const recoverySignerAddress2 = recoverableWallet.signers[1];
 ```
 
+</Tab>
+<Tab title="Kotlin">
+
 ```kotlin
   val recoverySigners = recoverableWallet.signers
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var recoverySigners = recoverableWallet.signers;
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let recoverySigners = recoverableWallet.signers
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Next, create a new device key and retrieve a signed transaction that replaces the device key:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const newDeviceKp = accountService.createKeypair();
@@ -447,6 +557,9 @@ const recoverTxn = await recovery.replaceDeviceKey(
 );
 ```
 
+</Tab>
+<Tab title="Kotlin">
+
 ```kotlin
   val newKey = wallet.stellar().account().createKeyPair()
 
@@ -463,6 +576,9 @@ const recoverTxn = await recovery.replaceDeviceKey(
     )
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var newKey = wallet.stellar().account().createKeyPair();
 var serverAuth = {
@@ -473,6 +589,9 @@ var serverAuth = {
 var signedReplaceKeyTx = await recovery.replaceDeviceKey(accountKp, newKey, serverAuth);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let newKey = wallet.stellar.account.createKeyPair()
 let serverAuth = [
@@ -485,7 +604,8 @@ let signedReplaceKeyTx = try await recovery.replaceDeviceKey(account: accountKp,
                                                              serverAuth: serverAuth)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Calling this function will create a transaction that locks the previous device key and replaces it with your new key (having the same weight as the old one). Both recovery signers will have signed the transaction.
 
@@ -494,34 +614,45 @@ The lost device key is deduced automatically if not given. A signer will be cons
 1. It's the only signer that's not in `serverAuth`.
 2. All signers in `serverAuth` have the same weight, and the potential signer is the only one with a different weight.
 
-:::note
+<Note>
 
 The account created above will match the first criteria. If a 2-3 schema were used, then the second criteria would match. (In a 2-3 schema, 3 servers are used and 2 of them are enough to recover the key. This is a recommended approach.)
 
 You can also use more low-level `signWithRecoveryServers` functions to sign arbitrary transactions.
 
-:::
+</Note>
 
 Finally, it's time to submit the transaction:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 await stellar.submitTransaction(recoverTxn);
 ```
 
+</Tab>
+<Tab title="Kotlin">
+
 ```kotlin
   wallet.stellar().submitTransaction(signedReplaceKeyTransaction)
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 await wallet.stellar().submitTransaction(signedReplaceKeyTx);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 try await wallet.stellar.submitTransaction(signedTransaction: signedReplaceKeyTx)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 [sep-30]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0030.md
diff --git a/docs/build/apps/wallet/sep38.mdx b/docs/build/apps/wallet/sep38.mdx
index 258737f15..c8b4ca46c 100644
--- a/docs/build/apps/wallet/sep38.mdx
+++ b/docs/build/apps/wallet/sep38.mdx
@@ -1,14 +1,19 @@
 ---
 title: Quote
-sidebar_position: 70
+description: "The [SEP-38] standard defines a way for anchors to provide quotes for the exchange of an off-chain asset and a different on-chain asset, and vice versa."
 ---
 
-import { LanguageSpecific } from "@site/src/components/LanguageSpecific";
+import Header from "/snippets/wallet/header.mdx";
 
-import { WalletCodeExample } from "@site/src/components/WalletCodeExample";
-import Header from "./component/header.mdx";
+<Header />
 
-<Header WIPLangs={["kotlin"]} />
+<Warning>
+
+**Important**
+
+Documentation for Kotlin is currently work in progress. Some of information may not be applicable for Kotlin, or missing. Code samples may be incomplete.
+
+</Warning>
 
 The [SEP-38] standard defines a way for anchors to provide quotes for the exchange of an off-chain asset and a different on-chain asset, and vice versa. Quotes may be [indicative](https://www.investopedia.com/terms/i/indicativequote.asp) or [firm](https://www.investopedia.com/terms/f/firmquote.asp) ones. When either is used is explained in the sections below.
 
@@ -18,7 +23,8 @@ Let's start with creating a sep38 object, which we'll use for all SEP-38 interac
 
 Authentication is done using [Sep-10], and we add the authentication token to the sep38 object.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const accountKp = ... // our account keypair
@@ -28,6 +34,9 @@ const authToken = await auth.authenticate({ accountKp });
 const sep38 = anchor.sep38(authToken);
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var accountKp = ... // our account keypair
 
@@ -36,6 +45,9 @@ var authToken = await auth.authenticate(accountKp);
 var sep38 = anchor.sep38(authToken: authToken);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let accountKp = ... // our account keypair
 
@@ -44,27 +56,36 @@ let authToken = try await sep10.authenticate(userKeyPair: accountKp)
 let sep38 = try await anchor.sep38(authToken: authToken)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 ## Get Anchor Information
 
 First, let's get information about the anchor's support for [SEP-38]. The response gives what stellar on-chain assets and off-chain assets are available for trading.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const resp = await sep38.info();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var resp = await sep38.info();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let resp = try await sep38.info
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 For example a response will look like this. The asset identifiers are described below in [Asset Identification Format](#asset-identification-format).
 
@@ -114,7 +135,8 @@ Now let's get [indicative](https://www.investopedia.com/terms/i/indicativequote.
 
 In our example we're getting prices for selling 5 fiat USD.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const resp = await sep38.prices({
@@ -123,6 +145,9 @@ const resp = await sep38.prices({
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var resp = await sep38.prices(
   sellAsset: "iso4217:USD",
@@ -130,12 +155,16 @@ var resp = await sep38.prices(
 );
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let response = try await sep38.prices(sellAsset: "iso4217:USD",
                                       sellAmount: "5")
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 The response gives the asset prices for exchanging the requested sell asset. For example, a response look like this:
 
@@ -159,7 +188,8 @@ Once again this is an indicative value. The actual price will be calculated at c
 
 Either a `sellAmount` or `buyAmount` value must be given, but not both. And `context` refers to what Stellar SEP context this will be used for (ie. `sep6`, `sep24`, or `sep31`).
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const resp = await sep38.price({
@@ -171,6 +201,9 @@ const resp = await sep38.price({
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var resp = await sep38.price(
   sellAsset: "iso4217:USD",
@@ -181,6 +214,9 @@ var resp = await sep38.price(
 );
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let resp = try await sep38.price(
     context: "sep6",
@@ -189,7 +225,8 @@ let resp = try await sep38.price(
     sellAmount: "5")
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 The response gives information for exchanging these assets. For example, a response will look like this:
 
@@ -203,7 +240,8 @@ Now let's get a [firm](https://www.investopedia.com/terms/f/firmquote.asp) quote
 
 The request body is similar to the `.price()` call we made earlier.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const requestResp = await sep38.requestQuote({
@@ -215,6 +253,9 @@ const requestResp = await sep38.requestQuote({
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var requestResp = await sep38.requestQuote(
   sellAsset: "iso4217:USD",
@@ -225,6 +266,9 @@ var requestResp = await sep38.requestQuote(
 );
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let resp = try await sep38.requestQuote(
     context: "sep6",
@@ -233,7 +277,8 @@ let resp = try await sep38.requestQuote(
     sellAmount: "5")
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 However now the response gives an `id` that we can use to identify the quote. The `expires_at` field tells us how long the anchor will wait to receive funds for this quote.
 
@@ -255,24 +300,32 @@ An example response looks like this:
 
 Now let's get the previously requested quote. To do that we use the `id` from the `.requestQuote()` response.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const quoteId = requestResp.id;
 const getResp = await sep38.getQuote(quoteId);
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var quoteId = requestResp.id;
 var getResp = await sep38.getQuote(quoteId);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let quoteId = requestResp.id
 let getResp = try await sep38.getQuote(quoteId: quoteId)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 The response should match the one given from `.requestQuote()` we made earlier.
 
diff --git a/docs/build/apps/wallet/sep6.mdx b/docs/build/apps/wallet/sep6.mdx
index 88d596564..189e3b9cd 100644
--- a/docs/build/apps/wallet/sep6.mdx
+++ b/docs/build/apps/wallet/sep6.mdx
@@ -1,56 +1,77 @@
 ---
 title: Programmatic Deposit and Withdrawal
-sidebar_position: 60
+description: "The [SEP-6] standard defines a way for anchors and wallets to interact on behalf of users."
 ---
 
-import { LanguageSpecific } from "@site/src/components/LanguageSpecific";
+import Header from "/snippets/wallet/header.mdx";
 
-import { WalletCodeExample } from "@site/src/components/WalletCodeExample";
-import Header from "./component/header.mdx";
+<Header />
 
-<Header WIPLangs={["kotlin"]} />
+<Warning>
+
+**Important**
+
+Documentation for Kotlin is currently work in progress. Some of information may not be applicable for Kotlin, or missing. Code samples may be incomplete.
+
+</Warning>
 
 The [SEP-6] standard defines a way for anchors and wallets to interact on behalf of users. Wallets use this standard to facilitate exchanges between on-chain assets (such as stablecoins) and off-chain assets (such as fiat, or other network assets such as BTC).
 
-Please note, this is for _programmatic_ deposits and withdrawals. For hosted deposits and withdrawals, where the anchor interacts with wallets interactively using a popup, please see [Hosted Deposit and Withdrawal](./sep24.mdx).
+Please note, this is for _programmatic_ deposits and withdrawals. For hosted deposits and withdrawals, where the anchor interacts with wallets interactively using a popup, please see [Hosted Deposit and Withdrawal](./sep24).
 
 ## Get Anchor Information
 
 Let's start with creating a sep6 object, which we'll use for all SEP-6 interactions:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const sep6 = anchor.sep6();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var sep6 = anchor.sep6();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let sep6 = anchor.sep6
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 First, let's get information about the anchor's support for [SEP-6]. This request doesn't require authentication, and will return generic info, such as supported currencies, and features supported by the anchor. You can get a full list of returned fields in the [SEP-6 specification](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md#info).
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const info = await sep6.info();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var info = await sep6.info();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let info = try await sep6.info()
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 ## Start a deposit
 
@@ -58,15 +79,16 @@ Before getting started, make sure you have connected to the anchor and received
 
 To initiate an operation, we need to know an asset. You can hardcode this. Ensure it is one that is included in the info response above.
 
-:::info
+<Info>
 
-Before starting with the deposit flow, make sure that the user account has [established a trustline](./stellar.mdx#modify-assets-trustlines) for the asset you are working with.
+Before starting with the deposit flow, make sure that the user account has [established a trustline](./stellar#modify-assets-trustlines) for the asset you are working with.
 
-:::
+</Info>
 
 Let's start with a basic deposit. We will use `account` to represent our account's public key.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const deposit = await sep6.deposit({
@@ -78,6 +100,9 @@ const deposit = await sep6.deposit({
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var deposit = await anchor.sep6().deposit(
   Sep6DepositParams(assetCode: assetCode, account: accountId),
@@ -85,6 +110,9 @@ var deposit = await anchor.sep6().deposit(
 );
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let params = Sep6DepositParams(assetCode: assetCode, account: account)
 let depositResponse = try await anchor.sep6.deposit(params: params, authToken: authToken)
@@ -95,7 +123,8 @@ case .depositSuccess(let how, let id, let eta, let minAmount, let maxAmount, let
 }
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 There are several kinds of responses, depending on if the anchor needs more information. All deposits and withdrawals will have these same response types:
 
@@ -132,7 +161,8 @@ An example response:
 
 Let's show how a wallet can handle this situation. First, we get the deposit response object. If the response includes this error, then we can see which missing fields the anchor is requiring.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 if (deposit.type === "non_interactive_customer_info_needed") {
@@ -141,12 +171,18 @@ if (deposit.type === "non_interactive_customer_info_needed") {
 }
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 if (deposit is Sep6MissingKYC) {
   print(deposit.fields);
 }
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 switch depositResponse {
 case .missingKYC(let fields):
@@ -154,11 +190,13 @@ case .missingKYC(let fields):
 }
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 The wallet will need to handle displaying to the user which fields are missing. And then to add those fields, we can use the sep12 class like so.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const sep12 = await anchor.sep12(authToken);
@@ -174,6 +212,9 @@ await sep12.add({
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var sep12 = await anchor.sep12(authToken);
 
@@ -188,6 +229,9 @@ var sep9Info = {
 var addResponse = await sep12.add(sep9Info);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let sep12 = try await anchor.sep12(authToken: authToken)
 
@@ -202,7 +246,8 @@ let sep9Info = [
 let addResponse = try await sep12.add(sep9Info: sep9Info)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Then, we can re-call the deposit method like before and it should be successful.
 
@@ -214,7 +259,8 @@ An anchor may respond to a deposit or withdrawal request saying they need additi
 
 Let's add some KYC info for our account using sample data. Binary data (eg. image data), needs to be sent in a separate field. The fields allowed to send to the anchor are described in [SEP-9].
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const sep12 = await anchor.sep12(authToken);
@@ -234,6 +280,9 @@ await sep12.add({
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var sep12 = await anchor.sep12(authToken);
 
@@ -256,6 +305,9 @@ var sep9Files = {
 await sep12.add(sep9Info, sep9Files: sep9Files);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let sep12 = try await anchor.sep12(authToken: authToken)
 
@@ -278,13 +330,15 @@ let sep9Files = [
 let addResponse = try await sep12.add(sep9Info: sep9Info, sep9Files: sep9Files)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 ## Start a withdrawal
 
 Starting a withdrawal is similar to deposit, and has the same response types as described earlier.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const resp = await sep6.withdraw({
@@ -299,6 +353,9 @@ const resp = await sep6.withdraw({
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var params = Sep6WithdrawParams(
     assetCode: 'SRT',
@@ -311,6 +368,9 @@ var params = Sep6WithdrawParams(
 var resp = await anchor.sep6().withdraw(params, authToken);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let params = Sep6WithdrawParams(
   assetCode: "SRT",
@@ -323,7 +383,8 @@ let resp = try await anchor.sep6.withdraw(params: withdrawParams,
                                           authToken: authToken)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 ## Get exchange info
 
@@ -333,7 +394,8 @@ The sep6 exchange functions allow a user to start an exchange deposit or withdra
 
 First, let's start a deposit exchange with sample data. Assets are described using the [SEP-38] scheme.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const resp = await sep6.depositExchange({
@@ -347,6 +409,9 @@ const resp = await sep6.depositExchange({
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var params = Sep6DepositExchangeParams(
     destinationAssetCode: 'SRT',
@@ -357,6 +422,9 @@ var params = Sep6DepositExchangeParams(
 var resp = await anchor.sep6().depositExchange(params, authToken);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let params = Sep6DepositExchangeParams(
   destinationAssetCode: "SRT",
@@ -367,13 +435,15 @@ let resp = try await anchor.sep6.depositExchange(params: params,
                                                  authToken: authToken)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 The response follows the same types as all the deposits and withdrawals for SEP-6.
 
 Now let's create a withdrawal exchange, which follows the same format as the deposit exchange. We also specify it's a bank account withdrawal using the `type` field.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const resp = await sep6.withdrawExchange({
@@ -388,6 +458,9 @@ const resp = await sep6.withdrawExchange({
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var params = Sep6WithdrawExchangeParams(
     sourceAssetCode: 'SRT',
@@ -399,6 +472,9 @@ var params = Sep6WithdrawExchangeParams(
 var resp = await anchor.sep6().withdrawExchange(params, authToken);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let params = Sep6WithdrawExchangeParams(
   sourceAssetCode: "SRT",
@@ -410,7 +486,8 @@ let resp = try await anchor.sep6.withdrawExchange(params: params,
                                                   authToken: authToken)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 The response follows the same types as all the deposits and withdrawals for SEP-6.
 
@@ -422,7 +499,8 @@ On the typical flow, the wallet would get transaction data to notify users about
 
 Let's look into how to use the sdk to track transaction status changes. We will use the `Watcher` class for this purpose. First, let's initialize it and start tracking a transaction.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const watcher = anchor.sep6().watcher();
@@ -437,6 +515,9 @@ const { stop, refresh } = watcher.watchOneTransaction({
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var watcher = anchor.sep6.watcher();
 var result = watcher.watchOneTransaction(authToken, 'transaction id');
@@ -454,6 +535,9 @@ result.controller.stream.listen(
 );
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let watcher = anchor.sep6.watcher()
 let result = watcher.watchOneTransaction(authToken: token,
@@ -476,11 +560,13 @@ NotificationCenter.default.addObserver(self,
 }
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Alternatively, we can track multiple transactions for the same asset.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const watcher = anchor.sep6().watcher();
@@ -493,6 +579,9 @@ const { stop, refresh } = watcher.watchAllTransactions({
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var watcher = anchor.sep6.watcher();
 var result = watcher.watchAsset(authToken, asset);
@@ -510,6 +599,9 @@ result.controller.stream.listen(
 );
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let watcher = anchor.sep6.watcher()
 let result = watcher.watchAsset(authToken: token,
@@ -532,13 +624,15 @@ NotificationCenter.default.addObserver(self,
 }
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 ### Fetching Transaction
 
 While `Watcher` class offers powerful tracking capabilities, sometimes it's required to just fetch a transaction (or transactions) once. The `Anchor` class allows you to fetch a transaction by ID, Stellar transaction ID, or external transaction ID:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const transaction = await anchor
@@ -546,6 +640,9 @@ const transaction = await anchor
   .getTransactionBy({ authToken, id: transactionId });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var transaction = await anchor.sep6().getTransactionBy(
     authToken: authToken,
@@ -553,17 +650,22 @@ var transaction = await anchor.sep6().getTransactionBy(
 );
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let transaction = try await anchor.sep6.getTransactionBy(
   authToken: authToken,
   transactionId:transactionId)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 It's also possible to fetch transactions by the asset.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const transactions = await anchor.sep6().getTransactionsForAsset({
@@ -572,6 +674,9 @@ const transactions = await anchor.sep6().getTransactionsForAsset({
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var transactions = await anchor.sep6().getTransactionsForAsset(
   authToken: authToken,
@@ -579,6 +684,9 @@ var transactions = await anchor.sep6().getTransactionsForAsset(
 );
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let transactions = try await anchor.sep6.getTransactionsForAsset(
   authToken: authToken,
@@ -586,11 +694,12 @@ let transactions = try await anchor.sep6.getTransactionsForAsset(
 
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 [sep-6]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md
 [sep-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
 [sep-10]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md
 [sep-12]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md
 [sep-38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
-[stellar authentication]: ./sep10.mdx
+[stellar authentication]: ./sep10
diff --git a/docs/build/apps/wallet/sep7.mdx b/docs/build/apps/wallet/sep7.mdx
index 5e1bfb6e0..932124cc8 100644
--- a/docs/build/apps/wallet/sep7.mdx
+++ b/docs/build/apps/wallet/sep7.mdx
@@ -1,10 +1,9 @@
 ---
 title: URI Scheme to facilitate delegated signing
-sidebar_position: 80
+description: "The [Sep-7] standard defines a way for a non-wallet application to construct a URI scheme that represents a specific transaction for an account to sign."
 ---
 
-import Header from "./component/header.mdx";
-import { WalletCodeExample } from "@site/src/components/WalletCodeExample";
+import Header from "/snippets/wallet/header.mdx";
 
 <Header />
 
@@ -14,7 +13,8 @@ The [Sep-7] standard defines a way for a non-wallet application to construct a U
 
 The tx operation represents a request to sign a specific transaction envelope, with [some configurable parameters].
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const sourceAccountKeyPair = "G...";
@@ -30,6 +30,9 @@ const uri = wallet.parseSep7Uri(txUri);
 // uri can be parsed and transaction can be signed/submitted by an application that implements Sep-7
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final sourceAccountKeyPair = PublicKeyPair.fromAccountId('G...');
 final destinationAccountKeyPair = PublicKeyPair.fromAccountId('G...');
@@ -42,6 +45,9 @@ final uri = wallet.parseSep7Uri(txUri);
 // uri can be parsed and transaction can be signed/submitted by an application that implements Sep-7
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let sourceAccountKeyPair = try PublicKeyPair(accountId: "G...")
 let destinationAccountKeyPair = try PublicKeyPair(accountId: "G...")
@@ -54,11 +60,13 @@ let uri = try wallet.parseSep7Uri(uri: txUri)
 // uri can be parsed and transaction can be signed/submitted by an application that implements Sep-7
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 You can set replacements to be made in the xdr for specific fields by the application, these will be added in the [Sep-11 transaction representation format] to the URI.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const uri = new Sep7Tx(txUri);
@@ -69,6 +77,9 @@ uri.addReplacement({
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final uri = wallet.parseSep7Uri(txUri);
 
@@ -80,6 +91,9 @@ if (uri is Sep7Tx) {
 }
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let uri = try wallet.parseSep7Uri(uri: txUri)
 
@@ -92,11 +106,13 @@ if let uri = uri as? Sep7Tx {
 }
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 You can assign parameters after creating the initial instance using the appropriate setter for the parameter.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const sourceAccountKeyPair = "G...";
@@ -111,6 +127,9 @@ uri.msg = "here goes a message";
 uri.toString(); // encodes everything and converts to a uri string
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final sourceAccountKeyPair = PublicKeyPair.fromAccountId('G...');
 final destinationAccountKeyPair = PublicKeyPair.fromAccountId('G...');
@@ -123,6 +142,9 @@ uri.setMsg('here goes a message');
 uri.toString(); // encodes everything and converts to a uri string
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let sourceAccountKeyPair = try PublicKeyPair(accountId: "G...")
 let destinationAccountKeyPair = try PublicKeyPair(accountId: "G...")
@@ -135,13 +157,15 @@ try uri.setMsg(msg: "here goes a message")
 let uriStr = uri.toString() // encodes everything and converts to a uri string
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 ## Pay Operation
 
 The pay operation represents a request to pay a specific address with a specific asset, regardless of the source asset used by the payer. You can [configure parameters] to build the payment operation.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const destination = "G...";
@@ -156,6 +180,9 @@ const uri = parseSep7Uri(payUri);
 // uri can be parsed and transaction can be built/signed/submitted by an application that implements Sep-7
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 const destination = 'G...';
 const assetIssuer = 'G...';
@@ -169,6 +196,9 @@ final uri = Sep7.parseSep7Uri(payUri);
 // uri can be parsed and transaction can be built/signed/submitted by an application that implements Sep-7
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let destination = "G..."
 let assetIssuer = "G..."
@@ -182,11 +212,13 @@ uri = try Sep7.parseSep7Uri(uri: payUri)
 // uri can be parsed and transaction can be built/signed/submitted by an application that implements Sep-7
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 You can assign parameters after creating the initial instance using the appropriate setter for the parameter.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const uri = wallet.Sep7Pay.forDestination("G...");
@@ -198,6 +230,9 @@ uri.amount = "10";
 uri.toString(); // encodes everything and converts to a uri string
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final uri = Sep7Pay.forDestination('G...');
 uri.setCallback('https://example.com/callback');
@@ -208,6 +243,9 @@ uri.setAmount('10');
 uri.toString(); // encodes everything and converts to a uri string
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let uri = Sep7Pay(destination: "G...")
 uri.setCallback(callback: "https://example.com/callback")
@@ -218,11 +256,13 @@ uri.setAmount(amount: "10")
 uri.toString() // encodes everything and converts to a uri string
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 The last step after building a `Sep7Tx` or `Sep7Pay` is to add a signature to your uri. This will create a payload out of the transaction and sign it with the provided keypair.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const uri = wallet.Sep7Pay.forDestination("G...");
@@ -232,6 +272,9 @@ uri.addSignature(Keypair.fromSecret(keypair.secretKey));
 console.log(uri.signature); // signed uri payload
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final uri = Sep7Pay.forDestination('G...');
 uri.setOriginDomain('example.com');
@@ -240,6 +283,9 @@ uri.addSignature(keypair);
 print(uri.getSignature()); // signed uri payload
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 uri = Sep7Pay(destination: "G..")
 uri.setOriginDomain(originDomain: "example.com")
@@ -248,28 +294,37 @@ try uri.addSignature(keyPair: keyPair)
 print(uri.getSignature()) // signed uri payload
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 The signature can then be verified by fetching the [Stellar toml file] from the origin domain in the uri, and using the included signing key to verify the uri signature. This is all done as part of the `verifySignature` method.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const passesVerification = await uri.verifySignature(); // true or false
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 final passesVerification = await uri.verifySignature(); // true or false
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let passesVerification = await uri.verifySignature() // true or false
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 [Sep-7]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0007.md
 [Sep-11 transaction representation format]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0011.md
 [some configurable parameters]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0007.md#operation-tx
 [configure parameters]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0007.md#operation-pay
-[Stellar toml file]: ../../apps/example-application-tutorial/anchor-integration/sep1.mdx
+[Stellar toml file]: ../../apps/example-application-tutorial/anchor-integration/sep1
diff --git a/docs/build/apps/wallet/stellar.mdx b/docs/build/apps/wallet/stellar.mdx
index 27ad679e9..45563fa12 100644
--- a/docs/build/apps/wallet/stellar.mdx
+++ b/docs/build/apps/wallet/stellar.mdx
@@ -1,12 +1,10 @@
 ---
 title: Stellar Network
-sidebar_position: 30
+description: "In the previous section we learned how to create a wallet and a Stellar object that provides a connection to Horizon."
 ---
 
-import { LanguageSpecific } from "@site/src/components/LanguageSpecific";
-import { WalletCodeExample } from "@site/src/components/WalletCodeExample";
-import Header from "./component/header.mdx";
-import CreateKeyPairInfo from "./component/ts/createKeypairInfo.mdx";
+import Header from "/snippets/wallet/header.mdx";
+import CreateKeyPairInfo from "/snippets/wallet/ts/createKeypairInfo.mdx";
 
 <Header />
 
@@ -16,49 +14,71 @@ In the previous section we learned how to create a wallet and a `Stellar` object
 
 The most basic entity on the Stellar network is an account. Let's look into AccountService that provides the capability to work with accounts:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 val account = wallet.stellar().account()
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 let account = wal.stellar().account();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var account = wallet.stellar().account();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let account = wallet.stellar.account
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Now we can create a keypair:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 val accountKeyPair = account.createKeyPair()
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 let accountKeyPair = account.createKeypair();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var accountKeyPair = account.createKeyPair();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let accountKeyPair = account.createKeyPair()
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
-<LanguageSpecific ts={<CreateKeyPairInfo />} />
+<CreateKeyPairInfo />
 
 ## Build Transaction
 
@@ -72,7 +92,8 @@ First, let's look into building basic transactions.
 
 The create account transaction activates/creates an account with a starting balance of XLM (1 XLM by default).
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kotlin
 suspend fun createAccount(): Transaction {
@@ -80,6 +101,9 @@ suspend fun createAccount(): Transaction {
 }
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const txBuilder = await stellar.transaction({
   sourceAddress: sourceAccountKeyPair,
@@ -87,23 +111,31 @@ const txBuilder = await stellar.transaction({
 const tx = txBuilder.createAccount(destinationAccountKeyPair).build();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var txBuilder = await stellar.transaction(sourceAccountKeyPair);
 var tx = txBuilder.createAccount(destinationAccountKeyPair).build();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let txBuilder = try await stellar.transaction(sourceAddress: sourceAccountKeyPair)
 let tx = try txBuilder.createAccount(newAccount: destinationAccountKeyPair).build()
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 #### Modify Account
 
 You can lock the master key of the account by setting its weight to 0. Use caution when locking the account's master key. Make sure you have set the correct signers and weights. Otherwise, you will lock the account irreversibly.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kotlin
 suspend fun lockMasterKey(): Transaction {
@@ -111,6 +143,9 @@ suspend fun lockMasterKey(): Transaction {
 }
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const txBuilder = await stellar.transaction({
   sourceAddress: sourceAccountKeyPair,
@@ -119,21 +154,29 @@ const txBuilder = await stellar.transaction({
 const tx = txBuilder.lockAccountMasterKey().build();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var txBuilder = await stellar.transaction(sourceAccountKeyPair);
 var tx = txBuilder.lockAccountMasterKey().build();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let txBuilder = try await stellar.transaction(sourceAddress: sourceAccountKeyPair)
 let tx = try txBuilder.lockAccountMasterKey().build()
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Add a new signer to the account. Use caution when adding new signers and make sure you set the correct signer weight. Otherwise, you will lock the account irreversibly.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kotlin
 val newSignerKeyPair = account.createKeyPair()
@@ -143,12 +186,18 @@ suspend fun addSigner(): Transaction {
 }
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const newSignerKeyPair = account.createKeypair();
 
 const tx = txBuilder.addAccountSigner(newSignerKeyPair, 10).build();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var newSignerKeyPair = account.createKeyPair();
 
@@ -156,6 +205,9 @@ var txBuilder = await stellar.transaction(sourceAccountKeyPair);
 var tx = txBuilder.addAccountSigner(newSignerKeyPair, 10).build();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let newSignerKeyPair = account.createKeyPair()
 
@@ -163,11 +215,13 @@ let txBuilder = try await stellar.transaction(sourceAddress: sourceAccountKeyPai
 let tx = try txBuilder.addAccountSigner(signerAddress: newSignerKeyPair, signerWeight: 10).build()
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Remove a signer from the account.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kotlin
 suspend fun removeSigner(): Transaction {
@@ -175,25 +229,36 @@ suspend fun removeSigner(): Transaction {
 }
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const tx = txBuilder.removeAccountSigner(newSignerKeyPair).build();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var txBuilder = await stellar.transaction(sourceAccountKeyPair);
 var tx = txBuilder.removeAccountSigner(newSignerKeyPair).build();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let txBuilder = try await stellar.transaction(sourceAddress: sourceAccountKeyPair)
 let tx = try txBuilder.removeAccountSigner(signerAddress: newSignerKeyPair).build()
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Modify account thresholds (useful when multiple signers are assigned to the account). This allows you to restrict access to certain operations when the limit is not reached.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kotlin
 suspend fun setThreshold(): Transaction {
@@ -201,27 +266,38 @@ suspend fun setThreshold(): Transaction {
 }
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const tx = txBuilder.setThreshold({ low: 1, medium: 10, high: 30 }).build();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var txBuilder = await stellar.transaction(sourceAccountKeyPair);
 var tx = txBuilder.setThreshold(low: 1, medium: 10, high: 20).build();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let txBuilder = try await stellar.transaction(sourceAddress: sourceAccountKeyPair)
 let tx = try txBuilder.setThreshold(low: 1, medium: 10, high: 20).build()
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 #### Modify Assets (Trustlines)
 
 Add an asset (trustline) to the account. This allows the account to receive transfers of the asset.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kotlin
 val asset = IssuedAssetId("USDC", "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5")
@@ -231,6 +307,9 @@ suspend fun addAsset(): Transaction {
 }
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const asset = new IssuedAssetId(
   "USDC",
@@ -240,6 +319,9 @@ const asset = new IssuedAssetId(
 const tx = txBuilder.addAssetSupport(asset).build();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var asset = IssuedAssetId(
         code: "USDC",
@@ -249,6 +331,9 @@ var txBuilder = await stellar.transaction(sourceAccountKeyPair);
 var tx = txBuilder.addAssetSupport(asset).build();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let asset = try IssuedAssetId(
     code: "USDC",
@@ -258,11 +343,13 @@ let txBuilder = try await stellar.transaction(sourceAddress: sourceAccountKeyPai
 let tx = try txBuilder.addAssetSupport(asset: asset).build()
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Remove an asset from the account (the asset's balance must be 0).
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kotlin
 suspend fun removeAsset(): Transaction {
@@ -270,21 +357,31 @@ suspend fun removeAsset(): Transaction {
 }
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const tx = txBuilder.removeAssetSupport(asset).build();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var txBuilder = await stellar.transaction(sourceAccountKeyPair);
 var tx = txBuilder.removeAssetSupport(asset).build();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let txBuilder = try await stellar.transaction(sourceAddress: sourceAccountKeyPair)
 let tx = try txBuilder.removeAssetSupport(asset: asset).build()
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 #### Swap
 
@@ -292,7 +389,8 @@ Exchange an account's asset for a different asset. The account must have a trust
 
 A swap is filled at whatever rate the network can find when the transaction is applied, which may differ from the rate you quoted to the user. The minimum destination amount (`destMin`) is the slippage limit that protects against that: it is the least amount of the destination asset the account is willing to receive for the amount it sends. If the swap cannot deliver at least that much, the transaction fails instead of executing at a worse rate. Derive it from a current quote minus the slippage tolerance you are willing to accept.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const txBuilder = await stellar.transaction({
@@ -308,6 +406,9 @@ const txn = txBuilder
   .build();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var txBuilder = await stellar.transaction(sourceKp);
 
@@ -325,6 +426,9 @@ var txn = txBuilder.swap(
   ).build();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let txBuilder = try await stellar.transaction(sourceAddress: sourceKp)
 
@@ -339,7 +443,8 @@ let txn = try txBuilder.swap(fromAsset: NativeAssetId(),
                              destMin: 0.025).build()
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 #### Path Pay
 
@@ -352,7 +457,8 @@ Like a swap, a path payment is filled at the rate available when the transaction
 
 If the network cannot fill the payment within that limit, the transaction fails instead of executing at a worse rate. Derive the limit from a current quote plus or minus the slippage tolerance you are willing to accept.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const txBuilder = await stellar.transaction({
@@ -374,6 +480,9 @@ const txn = txBuilder
   .build();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var txBuilder = await stellar.transaction(sourceKp);
 
@@ -392,6 +501,9 @@ var txn = txBuilder.pathPay(
   ).build();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let txBuilder = try await stellar.transaction(sourceAddress: sourceKp)
 
@@ -407,11 +519,13 @@ let txn = try txBuilder.pathPay(destinationAddress: receivingKp.address,
                                 destMin: 1.25).build()
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 To deliver an exact amount of the destination asset instead, pass `destAmount` together with `sendMax`:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 // Deliver exactly 5 USDC; spend no more than 21 XLM to do it
@@ -426,6 +540,9 @@ const txn = txBuilder
   .build();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 // Deliver exactly 5 USDC; spend no more than 21 XLM to do it
 var txn = txBuilder.pathPay(
@@ -437,6 +554,9 @@ var txn = txBuilder.pathPay(
   ).build();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 // Deliver exactly 5 USDC; spend no more than 21 XLM to do it
 let txn = try txBuilder.pathPay(destinationAddress: receivingKp.address,
@@ -446,13 +566,15 @@ let txn = try txBuilder.pathPay(destinationAddress: receivingKp.address,
                                 sendMax: 21).build()
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 #### Set Memo
 
 Set a memo on the transaction. The memo object can be imported from ["@stellar/stellar-sdk"](https://www.npmjs.com/package/@stellar/stellar-sdk).
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 import { Memo } from "@stellar/stellar-sdk";
@@ -460,6 +582,9 @@ import { Memo } from "@stellar/stellar-sdk";
 const tx = txBuilder.setMemo(new Memo("text", "Memo string")).build();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 import 'package:stellar_flutter_sdk/stellar_flutter_sdk.dart' as flutter_sdk;
 
@@ -467,6 +592,9 @@ var memo = flutter_sdk.MemoText("Memo string");
 var tx = txBuilder.setMemo(memo).build();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 import stellarsdk
 
@@ -474,13 +602,15 @@ let memo = Memo.text("Memo string")
 let tx = try txBuilder.setMemo(memo: memo).build()
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 #### Account Merge
 
 Merges account into a destination account.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 const txBuilder = await stellar.transaction({
@@ -492,6 +622,9 @@ const mergeTxn = txBuilder
   .build();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var txBuilder = await stellar.transaction(accountKp, baseFee: 1000);
 
@@ -501,6 +634,9 @@ var mergeTxn = txBuilder.accountMerge(
   ).build();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let txBuilder = try await stellar.transaction(sourceAddress: accountKp,
                                               baseFee: 1000)
@@ -509,33 +645,43 @@ let mergeTxn = try txBuilder.accountMerge(destinationAddress: accountKp.address,
                                           sourceAddress: sourceKp.address).build()
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 #### Fund Testnet Account
 
 Fund an account on the Stellar test network
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 wallet.stellar().fundTestnetAccount(accountKp.publicKey);
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 await wallet.stellar().fundTestNetAccount(accountKp.address);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 try await wallet.stellar.fundTestNetAccount(address: accountKp.address)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 ### Building Advanced Transactions
 
 In some cases a private key may not be known prior to forming a transaction. For example, a new account must be funded to exist and the wallet may not have the key for the account so may request the create account transaction to be sponsored by a third party.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 // Third-party key that will sponsor creating new account
@@ -543,29 +689,40 @@ val externalKeyPair = "MySponsorAddress".toPublicKeyPair()
 val newKeyPair = account.createKeyPair()
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 // Third-party key that will sponsor creating new account
 const externalKeyPair = new PublicKeypair.fromPublicKey("GC5GD...");
 const newKeyPair = account.createKeypair();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 // Third-party key that will sponsor creating new account
 var externalKeyPair = PublicKeyPair.fromAccountId("GC5GD...");
 var newKeyPair = account.createKeyPair();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 // Third-party key that will sponsor creating new account
 let externalKeyPair = try PublicKeyPair(accountId: "GC5GD...")
 let newKeyPair = account.createKeyPair()
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 First, the account must be created.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kotlin
 suspend fun makeCreateTx(): Transaction {
@@ -573,25 +730,36 @@ suspend fun makeCreateTx(): Transaction {
 }
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const createTxn = txBuilder.createAccount(newKeyPair).build();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var txBuilder = await stellar.transaction(externalKeyPair);
 var createTxn = txBuilder.createAccount(newKeyPair).build();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let txBuilder = try await stellar.transaction(sourceAddress: externalKeyPair)
 let createTxn = try txBuilder.createAccount(newAccount: newKeyPair).build()
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 This transaction must be sent to external signer (holder of `externalKeyPair`) to be signed.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 suspend fun remoteSignTransaction(transaction: Transaction) {
@@ -604,6 +772,9 @@ suspend fun remoteSignTransaction(transaction: Transaction) {
 }
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const xdrString = createTxn.toXDR();
 // Send xdr encoded transaction to your backend server to sign
@@ -613,6 +784,9 @@ const xdrStringFromBackend = await sendTransactionToBackend(xdrString);
 const signedTransaction = stellar.decodeTransaction(xdrStringFromBackend);
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var xdrString = createTxn.toEnvelopeXdrBase64();
 
@@ -623,6 +797,9 @@ var xdrStringFromBackend = await sendTransactionToBackend(xdrString);
 var signedTransaction = stellar.decodeTransaction(xdrStringFromBackend);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let xdrString = createTxn.toEnvelopeXdrBase64()
 
@@ -633,17 +810,19 @@ let xdrStringFromBackend = await sendTransactionToBackend(xdrString)
 let signedTransaction = stellar.decodeTransaction(xdr: xdrStringFromBackend)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
-:::note
+<Note>
 
 You can read more about passing XDR transaction to the server in the [chapter below](#using-xdr-to-send-transaction-data).
 
-:::
+</Note>
 
 Signed transaction can be submitted by the wallet.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 suspend fun submitCreateTx(signedCreateTx: Transaction) {
@@ -652,23 +831,34 @@ suspend fun submitCreateTx(signedCreateTx: Transaction) {
 
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 await wallet.stellar().submitTransaction(signedTransaction);
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 bool success = await stellar.submitTransaction(signedTransaction);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 try await stellar.submitTransaction(signedTransaction: signedTransaction)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Now, after the account is created, it can perform operations. For example, we can disable the master keypair and replace it with a new one (let's call it the device keypair) atomically in one transaction:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kotlin
 suspend fun addDeviceKeyPair() {
@@ -689,6 +879,9 @@ suspend fun addDeviceKeyPair() {
 }
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const deviceKeyPair = account.createKeypair();
 
@@ -702,6 +895,9 @@ newKeyPair.sign(modifyAccountTransaction);
 await wallet.stellar().submitTransaction(modifyAccountTransaction);
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var deviceKeyPair = account.createKeyPair();
 
@@ -716,6 +912,9 @@ stellar.sign(modifyAccountTransaction, newKeyPair);
 bool success = await stellar.submitTransaction(modifyAccountTransaction);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let deviceKeyPair = account.createKeyPair()
 
@@ -732,13 +931,15 @@ stellar.sign(tx: modifyAccountTransaction,
 try await stellar.submitTransaction(signedTransaction: modifyAccountTransaction)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 #### Adding an Operation
 
 Add a custom Operation to a transaction. This can be any [Operation](../../../learn/fundamentals/transactions/list-of-operations) supported by the Stellar network. The Operation object can be imported from ["@stellar/stellar-sdk"](https://www.npmjs.com/package/@stellar/stellar-sdk).
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="TypeScript">
 
 ```typescript
 import { Operation } from "@stellar/stellar-sdk";
@@ -755,6 +956,9 @@ const tx = txBuilder.addOperation(
 );
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 import 'package:stellar_flutter_sdk/stellar_flutter_sdk.dart' as flutter_sdk;
 
@@ -774,6 +978,9 @@ var tx = txBuilder.addOperation(
   ).build();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 import stellarsdk
 
@@ -787,15 +994,17 @@ let manageDataOperation = ManageDataOperation(sourceAccountId: sourceAccountKeyP
 let tx = try txBuilder.addOperation(operation: manageDataOperation).build()
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 ### Sponsoring Transactions
 
 #### Sponsor Operations
 
-Some operations, that modify account reserves can be [sponsored](../../guides/transactions/sponsored-reserves.mdx). For sponsored operations, the sponsoring account will be paying for the reserves instead of the account that being sponsored. This allows you to do some operations, even if account doesn't have enough funds to perform such operations. To sponsor a transaction, <LanguageSpecific kt={<span>simply start a <code>sponsoring</code> block:</span>} ts={<span>simply create a building function (describing which operations are to be sponsored) and pass it to the <code>sponsoring</code> method:</span>}/>
+Some operations, that modify account reserves can be [sponsored](../../guides/transactions/sponsored-reserves). For sponsored operations, the sponsoring account will be paying for the reserves instead of the account that being sponsored. This allows you to do some operations, even if account doesn't have enough funds to perform such operations. To sponsor a transaction, simply start a `sponsoring` block (Kotlin), or simply create a building function (describing which operations are to be sponsored) and pass it to the `sponsoring` method (TypeScript):
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kotlin
 suspend fun sponsorOperation() {
@@ -809,6 +1018,9 @@ suspend fun sponsorOperation() {
 }
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const txBuilder = await stellar.transaction({
   sourceAddress: sponsoredKeyPair,
@@ -823,6 +1035,9 @@ sponsoredKeyPair.sign(transaction);
 sponsorKeyPair.sign(transaction);
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var txBuilder = await stellar.transaction(sponsoredKeyPair);
 var transaction = txBuilder
@@ -833,6 +1048,9 @@ stellar.sign(transaction, sponsorKeyPair);
 stellar.sign(transaction, sponsoredKeyPair);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let txBuilder = try await stellar.transaction(sourceAddress: sponsoredKeyPair)
 let transaction = try txBuilder.sponsoring(
@@ -843,19 +1061,21 @@ stellar.sign(tx: transaction, keyPair: sponsorKeyPair)
 stellar.sign(tx: transaction, keyPair: sponsoredKeyPair)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
-:::info
+<Info>
 
-Only some operations can be sponsored, and a sponsoring <LanguageSpecific kt={<span>block</span>} ts={<span>builder</span>} /> has a slightly different set of functions available compared to the regular `TransactionBuilder`. Note, that a transaction must be signed by both the sponsor account (`sponsoringKeyPair`) and the account being sponsored (`sponsoredKeyPair`).
+Only some operations can be sponsored, and a sponsoring block (Kotlin) / builder (TypeScript) has a slightly different set of functions available compared to the regular `TransactionBuilder`. Note, that a transaction must be signed by both the sponsor account (`sponsoringKeyPair`) and the account being sponsored (`sponsoredKeyPair`).
 
-:::
+</Info>
 
 #### Sponsoring Account Creation
 
 One of the things that can be done via sponsoring is to create an account with a 0 starting balance. This account creation can be created by simply writing:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 suspend fun sponsorAccountCreation() {
@@ -871,6 +1091,9 @@ suspend fun sponsorAccountCreation() {
 }
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const txBuilder = await stellar.transaction({ sourceAddress: sponsorKeyPair });
 
@@ -885,6 +1108,9 @@ newKeyPair.sign(transaction);
 sponsorKeyPair.sign(transaction);
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var newKeyPair = account.createKeyPair();
 
@@ -898,6 +1124,9 @@ stellar.sign(transaction, sponsorKeyPair);
 stellar.sign(transaction, newKeyPair);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let newKeyPair = account.createKeyPair()
 
@@ -911,17 +1140,19 @@ stellar.sign(tx: transaction, keyPair: sponsorKeyPair)
 stellar.sign(tx: transaction, keyPair: newKeyPair)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
-Note how in the first example the transaction source account is set to `sponsoredKeyPair`. Due to this, we did not need to pass a sponsored account value to the `sponsoring` <LanguageSpecific kt={<span>block</span>} ts={<span>method</span>} />. Since when ommitted, the sponsored account defaults to the transaction source account (`sponsoredKeyPair`).
+Note how in the first example the transaction source account is set to `sponsoredKeyPair`. Due to this, we did not need to pass a sponsored account value to the `sponsoring` block (Kotlin) / method (TypeScript). Since when ommitted, the sponsored account defaults to the transaction source account (`sponsoredKeyPair`).
 
 However, this time, the sponsored account (freshly created `newKeyPair`) is different from the transaction source account. Therefore, it's necessary to specify it. Otherwise, the transaction will contain a malformed operation. As before, the transaction must be signed by both keys.
 
 #### Sponsoring Account Creation and Modification
 
-If you want to create an account and modify it in one transaction, it's possible to do so with passing a `sponsoredAccount` optional argument to the <LanguageSpecific kt={<span> sponsored block</span>} ts={<span>sponsoring method</span>} /> (`newKeyPair` below). If this argument is present, all operations inside the sponsored block will be sourced by this `sponsoredAccount`. (Except account creation, which is always sourced by the sponsor).
+If you want to create an account and modify it in one transaction, it's possible to do so with passing a `sponsoredAccount` optional argument to the sponsored block (Kotlin) / sponsoring method (TypeScript) (`newKeyPair` below). If this argument is present, all operations inside the sponsored block will be sourced by this `sponsoredAccount`. (Except account creation, which is always sourced by the sponsor).
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kotlin
 suspend fun sponsorAccountCreationAndModification() {
@@ -943,6 +1174,9 @@ suspend fun sponsorAccountCreationAndModification() {
 }
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const txBuilder = await stellar.transaction({ sourceAddress: sponsorKeyPair });
 
@@ -964,6 +1198,9 @@ newKeyPair.sign(transaction);
 sponsorKeyPair.sign(transaction);
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var newKeyPair = account.createKeyPair();
 var replaceWith = account.createKeyPair();
@@ -983,6 +1220,9 @@ stellar.sign(transaction, sponsorKeyPair);
 stellar.sign(transaction, newKeyPair);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let newKeyPair = account.createKeyPair()
 let replaceWith = account.createKeyPair()
@@ -1001,15 +1241,17 @@ stellar.sign(tx: transaction, keyPair: sponsorKeyPair)
 stellar.sign(tx: transaction, keyPair: newKeyPair)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 ### Fee-Bump Transaction
 
-If you wish to modify a newly created account with a 0 balance, it's also possible to do so via `FeeBump`. It can be combined with a sponsoring <LanguageSpecific kt={<span>block</span>} ts={<span>method</span>} /> to achieve the same result as in the example above. However, with `FeeBump` it's also possible to add more operations (that don't require sponsoring), such as a transfer.
+If you wish to modify a newly created account with a 0 balance, it's also possible to do so via `FeeBump`. It can be combined with a sponsoring block (Kotlin) / method (TypeScript) to achieve the same result as in the example above. However, with `FeeBump` it's also possible to add more operations (that don't require sponsoring), such as a transfer.
 
 First, let's create a transaction that will replace the master key of an account with a new keypair.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 val replaceWith = account.createKeyPair()
@@ -1025,6 +1267,9 @@ val transaction =
 
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const txBuilder = await stellar.transaction({
   sourceAddress: sponsoredKeyPair,
@@ -1039,6 +1284,9 @@ const transaction = txBuilder
   .build();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var replaceWith = account.createKeyPair();
 
@@ -1049,6 +1297,9 @@ var transaction = txBuilder
     .build();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let replaceWith = account.createKeyPair()
 
@@ -1061,42 +1312,58 @@ let transaction = try txBuilder.sponsoring(
     }).build()
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Second, sign transaction with both keys.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 transaction.sign(sponsoredKeyPair).sign(sponsorKeyPair)
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 sponsorKeyPair.sign(transaction);
 sponsoredKeyPair.sign(transaction);
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 stellar.sign(transaction, sponsorKeyPair);
 stellar.sign(transaction, sponsoredKeyPair);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 stellar.sign(tx: transaction, keyPair: sponsorKeyPair)
 stellar.sign(tx: transaction, keyPair: sponsoredKeyPair)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Next, create a fee bump, targeting the transaction.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 val feeBump = stellar.makeFeeBump(sponsorKeyPair, transaction)
 feeBump.sign(sponsorKeyPair)
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const feeBump = stellar.makeFeeBump({
   feeAddress: sponsorKeyPair,
@@ -1105,68 +1372,98 @@ const feeBump = stellar.makeFeeBump({
 sponsorKeyPair.sign(feeBump);
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var feeBump = stellar.makeFeeBump(sponsorKeyPair, transaction);
 stellar.sign(feeBump, sponsorKeyPair);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let feeBump = try stellar.makeFeeBump(feeAddress: sponsorKeyPair,
                                       transaction: transaction)
 stellar.sign(tx: transaction, keyPair: sponsorKeyPair)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Finally, submit a fee-bump transaction. Executing this transaction will be fully covered by the `sponsorKeyPair` and `sponsoredKeyPair` and may not even have any XLM funds on its account.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 wallet.stellar().submitTransaction(feeBump)
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 await wallet.stellar().submitTransaction(feeBump);
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 bool success = await stellar.submitTransaction(feeBump);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 try await stellar.submitTransaction(signedFeeBumpTransaction: feeBump)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 ### Using XDR to Send Transaction Data
 
 Note, that a wallet may not have a signing key for `sponsorKeyPair`. In that case, it's necessary to convert the transaction to XDR, send it to the server, containing `sponsorKey` and return the signed transaction back to the wallet. Let's use the previous example of sponsoring account creation, but this time with the sponsor key being unknown to the wallet. The first step is to define the public key of the sponsor keypair:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 val sponsorKeyPair = "SponsorAddress".toPublicKeyPair()
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const sponsorKeyPair = new PublicKeypair.fromPublicKey("GC5GD...");
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var sponsorKeyPair = PublicKeyPair.fromAccountId("GC5GD...");
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let sponsorKeyPair = try PublicKeyPair(accountId: "GC5GD...")
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 Next, create an account in the same manner as before and sign it with `newKeyPair`. This time, convert the transaction to XDR:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 suspend fun sponsorAccountCreation(): String {
@@ -1182,6 +1479,9 @@ suspend fun sponsorAccountCreation(): String {
 
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const txBuilder = await stellar.transaction({ sourceAddress: sponsorKeyPair });
 
@@ -1193,6 +1493,9 @@ const transaction = txBuilder
 const xdrString = newKeyPair.sign(transaction).toXDR();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var newKeyPair = account.createKeyPair();
 
@@ -1208,6 +1511,9 @@ stellar.sign(transaction, newKeyPair);
 var xdrString = transaction.toEnvelopeXdrBase64();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let newKeyPair = account.createKeyPair()
 
@@ -1222,11 +1528,13 @@ stellar.sign(tx: transaction, keyPair: newKeyPair)
 let xdrString = transaction.toEnvelopeXdrBase64()
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 It can now be sent to the server. On the server, sign it with a private key for the sponsor address:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 // On the server
@@ -1239,6 +1547,9 @@ fun signTransaction(xdrString: String): String {
 }
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 // On the server
 const sponsorPrivateKey = SigningKeyPair.fromSecret("SD3LH4...");
@@ -1250,6 +1561,9 @@ const signedTransaction = sponsorPrivateKey.sign(
 return signedTransaction.toXDR();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 String signTransaction(String xdrString) {
   var sponsorPrivateKey = SigningKeyPair.fromSecret("SD3LH4...");
@@ -1261,6 +1575,9 @@ String signTransaction(String xdrString) {
 }
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 internal func signTransaction(xdr:String) throws -> String {
     let sponsorPrivateKey = try SigningKeyPair(secretKey: "SD3LH4...")
@@ -1279,11 +1596,13 @@ internal func signTransaction(xdr:String) throws -> String {
 }
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 When the client receives the fully signed transaction, it can be decoded and sent to the Stellar network:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 suspend fun recoverSigned(xdrString: String) {
@@ -1294,18 +1613,27 @@ suspend fun recoverSigned(xdrString: String) {
 
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const signedTransaction = stellar.decodeTransaction(xdrString);
 
 await wallet.stellar().submitTransaction(signedTransaction);
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var signedTransaction = stellar.decodeTransaction(xdrStringFromBackend);
 
 bool success = await stellar.submitTransaction(signedTransaction);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let signedTransactionEnum = stellar.decodeTransaction(xdr: xdrStringFromBackend)
 
@@ -1319,21 +1647,23 @@ case .invalidXdrErr:
 }
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 ## Submit Transaction
 
-:::info
+<Info>
 
 It's strongly recommended to use the wallet SDK transaction submission functions instead of Horizon alternatives. The wallet SDK gracefully handles timeout and out-of-fee exceptions.
 
-:::
+</Info>
 
 Finally, let's submit a signed transaction to the Stellar network. Note that a sponsored transaction must be signed by both the account and the sponsor.
 
 The transaction is automatically re-submitted on the Horizon 504 error (timeout), which indicates a sudden network activity increase.
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kotlin
 suspend fun signAndSubmit() {
@@ -1342,28 +1672,39 @@ suspend fun signAndSubmit() {
 }
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const signedTxn = transaction.sign(sourceAccountKeyPair);
 await wallet.stellar().submitTransaction(signedTxn);
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 stellar.sign(transaction, sourceAccountKeyPair);
 bool success = await stellar.submitTransaction(transaction);
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 stellar.sign(tx: transaction, keyPair: sourceAccountKeyPair)
 try await stellar.submitTransaction(signedTransaction: transaction)
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 However, the method above doesn't handle fee surge pricing in the network gracefully. If the required fee for a transaction to be included in the ledger becomes too high and transaction expires before making it into the ledger, this method will throw an exception.
 
 So, instead, the alternative approach is to:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kotlin
 suspend fun submitWithFeeIncrease() {
@@ -1373,6 +1714,9 @@ suspend fun submitWithFeeIncrease() {
 }
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const buildingFunction = (builder) =>
   builder.transfer(kp.publicKey, new NativeAssetId(), "2");
@@ -1385,6 +1729,9 @@ await stellar.submitWithFeeIncrease({
 });
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 bool success = await stellar.submitWithFeeIncrease(
     sourceAddress: sourceAccountKeyPair,
@@ -1395,6 +1742,9 @@ bool success = await stellar.submitWithFeeIncrease(
     builder.transfer(destinationAccountKeyPair.address, NativeAssetId(), "10.0"));
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 try await stellar.submitWithFeeIncrease(
   sourceAddress: sourceAccountKeyPair,
@@ -1409,7 +1759,8 @@ try await stellar.submitWithFeeIncrease(
   })
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 This will create and sign the transaction that originated from the `sourceAccountKeyPair`. Every 30 seconds this function will re-construct this transaction with a new fee (increased by 100 stroops), repeating signing and submitting. Once the transaction is successful, the function will return the transaction body. Note, that any other error will terminate the retry cycle and an exception will be thrown.
 
@@ -1417,34 +1768,49 @@ This will create and sign the transaction that originated from the `sourceAccoun
 
 It's very simple to use the Horizon SDK connecting to the same Horizon instance as a `Wallet` class. To do so, simply call:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kotlin
 val server = wallet.stellar().server
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const server = wallet.stellar().server;
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var server = wallet.stellar().server;
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let server = wallet.stellar.server
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
 
 And you can work with Horizon Server instance:
 
-<WalletCodeExample>
+<Tabs>
+<Tab title="Kotlin">
 
 ```kt
 val stellarTransaction = server.transactions().transaction("transaction_id")
 ```
 
+</Tab>
+<Tab title="TypeScript">
+
 ```typescript
 const stellarTransaction = server
   .transactions()
@@ -1452,10 +1818,16 @@ const stellarTransaction = server
   .call();
 ```
 
+</Tab>
+<Tab title="Flutter">
+
 ```dart
 var transactions = await server.transactions.forAccount("accountId").execute();
 ```
 
+</Tab>
+<Tab title="Swift">
+
 ```swift
 let transactionsEnum = await server.transactions.getTransactions(forAccount: "accountId")
 switch transactionsEnum {
@@ -1466,4 +1838,5 @@ case .failure(let error):
 }
 ```
 
-</WalletCodeExample>
+</Tab>
+</Tabs>
diff --git a/docs/build/apps/zk.mdx b/docs/build/apps/zk.mdx
index cbbbcd09f..d0282fd33 100644
--- a/docs/build/apps/zk.mdx
+++ b/docs/build/apps/zk.mdx
@@ -1,6 +1,6 @@
 ---
 title: ZK Proofs on Stellar
-sidebar_position: 75
+description: "X-Ray (Protocol 25) introduced native host functions for zero-knowledge-friendly primitives (BN254 and Poseidon/Poseidon2), marking an important milestone..."
 ---
 
 X-Ray (Protocol 25) introduced native host functions for zero-knowledge-friendly primitives (BN254 and Poseidon/Poseidon2), marking an important milestone in a long-term strategy to equip developers with the execution-environment infrastructure needed to build compliance-forward, privacy-preserving applications using zero-knowledge cryptography. These primitives are foundational building blocks and do not, on their own, provide end-to-end private payments without additional higher-level protocol or application logic.
@@ -41,14 +41,14 @@ In the Rust `soroban-sdk`, these functions are exposed through the `CryptoHazmat
 - `poseidon_permutation` - performs the Poseidon permutation on an input vector of field elements
 - `poseidon2_permutation` - performs the Poseidon2 permutation on an input vector of field elements
 
-### Resources
+### Resources {#resources-1}
 
 - [P25 Preview examples](https://github.com/jayz22/soroban-examples/tree/p25-preview/p25-preview)
 - [Soroban SDK Poseidon documentation](https://docs.rs/soroban-sdk/latest/soroban_sdk/_migrating/v25_poseidon/index.html)
 - [CAP-75 proposal](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0075.md)
 
-:::note
+<Note>
 
 Ready-made Poseidon hash functions (built on top of these permutation primitives) live in a separate Rust SDK: [rs-soroban-poseidon](https://github.com/stellar/rs-soroban-poseidon).
 
-:::
+</Note>
diff --git a/docs/build/building-with-ai.mdx b/docs/build/building-with-ai.mdx
index 9a0c9d7a9..b2e2280ee 100644
--- a/docs/build/building-with-ai.mdx
+++ b/docs/build/building-with-ai.mdx
@@ -1,17 +1,8 @@
 ---
 title: Building with AI
 description: Use Stellar documentation with AI assistants and Large Language Models
-sidebar_label: Building with AI
-sidebar_position: 1
 ---
 
-import {
-  RavenConnectTabs,
-  SkillsInstallTabs,
-} from "@site/src/components/AgentSetup";
-
-# Building with AI
-
 Stellar provides resources to help AI assistants and Large Language Models (LLMs) understand our documentation, making it easier for you to get accurate answers about Stellar development.
 
 ## Raven (MCP server)
@@ -27,19 +18,89 @@ Under the hood it wraps Stellar Docs (via Algolia), Lumenloop, Stellar Light, an
 
 Unlike the static [`llms.txt`](#using-llmstxt) file and the installable [Stellar Skills](#stellar-skills) below, Raven is a live, hosted server your agent talks to. All three are useful, and they work well together.
 
-:::tip[Try it in your browser]
+<Tip>
+
+**Try it in your browser**
 
 [raven.stellar.buzz/playground](https://raven.stellar.buzz/playground) is a hosted chat UI where you can ask Raven questions directly in the browser, no agent setup required (sign-in required).
 
-:::
+</Tip>
 
 ### Connect your agent
 
 Add the server, then sign in. Sign-in happens inside your own client (Raven uses OAuth), so the first request opens your browser to authorize. For full setup details see [raven.stellar.buzz](https://raven.stellar.buzz).
 
-{/* Rendered from src/data/agentTools.ts, shared with the "For agents" panel. */}
+<Tabs>
+<Tab title="Claude Code">
+
+```bash
+claude mcp add --transport http stellar-raven "https://raven.stellar.buzz/mcp"
+# then run /mcp -> Authenticate -> sign in in your browser
+```
+
+</Tab>
+<Tab title="Codex">
+
+```bash
+codex mcp add stellar-raven --url "https://raven.stellar.buzz/mcp"
+codex mcp login stellar-raven  # opens your browser
+```
+
+</Tab>
+<Tab title="VS Code">
+
+```bash
+code --add-mcp '{"name":"stellar-raven","type":"http","url":"https://raven.stellar.buzz/mcp"}'
+```
+
+</Tab>
+<Tab title="Cursor">
 
-<RavenConnectTabs />
+Add to ~/.cursor/mcp.json (or .cursor/mcp.json per project). Cursor runs the OAuth sign-in on first use.
+
+```json
+{
+  "mcpServers": {
+    "stellar-raven": { "url": "https://raven.stellar.buzz/mcp" }
+  }
+}
+```
+
+</Tab>
+<Tab title="Claude desktop">
+
+Go to Settings -> Connectors -> Add custom connector, paste the endpoint, and approve the browser sign-in.
+
+```text
+https://raven.stellar.buzz/mcp
+```
+
+</Tab>
+<Tab title="Other clients">
+
+For clients without native remote or OAuth support, bridge with mcp-remote.
+
+```json
+{
+  "mcpServers": {
+    "stellar-raven": {
+      "command": "npx",
+      "args": [
+        "-y",
+        "mcp-remote@latest",
+        "https://raven.stellar.buzz/mcp",
+        "--transport",
+        "http-only"
+      ]
+    }
+  }
+}
+```
+
+[mcp-remote](https://github.com/geelen/mcp-remote)
+
+</Tab>
+</Tabs>
 
 ## Stellar Skills
 
@@ -83,9 +144,66 @@ Skills can be installed on any AI coding tool that supports the [Agent Skills](h
 | [OpenCode](https://opencode.ai) | `~/.config/opencode/skills/` |
 | [OpenAI Codex](https://openai.com/index/openai-codex) | `~/.codex/skills/` |
 
-{/* Rendered from src/data/agentTools.ts, shared with the "For agents" panel. */}
+<Tabs>
+<Tab title="Claude Code">
+
+Adds the skill to your tool permanently.
+
+```bash
+/plugin marketplace add stellar/stellar-dev-skill
+```
+
+```bash
+/plugin install stellar-dev@stellar-dev
+```
+
+</Tab>
+<Tab title="Codex">
+
+Codex reads skills from ~/.codex/skills/.
+
+```bash
+git clone https://github.com/stellar/stellar-dev-skill ~/.codex/skills/stellar-dev-skill
+```
+
+</Tab>
+<Tab title="VS Code">
+
+Works with any tool that supports the Agent Skills standard.
+
+```bash
+npx skills add https://github.com/stellar/stellar-dev-skill
+```
+
+</Tab>
+<Tab title="Cursor">
+
+Works with any tool that supports the Agent Skills standard.
+
+```bash
+npx skills add https://github.com/stellar/stellar-dev-skill
+```
+
+</Tab>
+<Tab title="Claude desktop">
+
+Works with any tool that supports the Agent Skills standard.
+
+```bash
+npx skills add https://github.com/stellar/stellar-dev-skill
+```
+
+</Tab>
+<Tab title="Other clients">
+
+Works with any tool that supports the Agent Skills standard.
+
+```bash
+npx skills add https://github.com/stellar/stellar-dev-skill
+```
 
-<SkillsInstallTabs />
+</Tab>
+</Tabs>
 
 #### Manual installation
 
@@ -95,7 +213,7 @@ Once installed, your AI coding assistant will automatically have access to up-to
 
 For other AI coding tools like Cursor, Windsurf, or Aider, you can consider the community-maintained [OpenSkills](https://github.com/numman-ali/openskills) CLI, which aims to bring the Agent Skills system to a wide range of AI coding agents. OpenSkills is a third-party project and not an official Stellar offering, so be sure to review the repository and its documentation to verify that it meets your security and maintenance requirements before using it.
 
-## Using llms.txt
+## Using llms.txt {#using-llmstxt}
 
 [`llms.txt`](https://developers.stellar.org/llms.txt) is a standardized way to provide documentation context to AI systems. This file contains a structured overview of Stellar's developer documentation optimized for LLM consumption.
 
diff --git a/docs/build/guides/README.mdx b/docs/build/guides/README.mdx
deleted file mode 100644
index b3589206e..000000000
--- a/docs/build/guides/README.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: How-To Guides
-description: Here you will find really useful guides
-sidebar_position: 40
-hide_table_of_contents: true
----
-
-This section provides step-by-step instructions to help users complete specific tasks associated with developing on Stellar. These tasks can include instructions for goals related to writing contracts, interacting with contracts, building applications, using Stellar operations, setting up infrastructure, and more.
diff --git a/docs/build/guides/archival/README.mdx b/docs/build/guides/archival/README.mdx
deleted file mode 100644
index 262b3078e..000000000
--- a/docs/build/guides/archival/README.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: State Archival
-hide_table_of_contents: true
-sidebar_position: 77
----
-
-Soroban's novel strategy to combat state bloat can present a learning curve for developers. Here are some quick guides that will help you through the process. Read more in the [State Archival section](../../../learn/fundamentals/contract-development/storage/state-archival.mdx).
diff --git a/docs/build/guides/archival/create-restoration-footprint-js.mdx b/docs/build/guides/archival/create-restoration-footprint-js.mdx
index 035a7ac01..cf20355f3 100644
--- a/docs/build/guides/archival/create-restoration-footprint-js.mdx
+++ b/docs/build/guides/archival/create-restoration-footprint-js.mdx
@@ -1,14 +1,13 @@
 ---
 title: Create a restoration footprint manually to restore archived data using the JavaScript SDK
-hide_table_of_contents: true
 description: Manually set up a restoration footprint with JavaScript SDK
 ---
 
-:::info
+<Info>
 
-The manual operation (`RestoreFootprintOp`) is, for the most part, no longer needed starting in Protocol 23, as archived entries included in a transaction's restore list (usually populated during transaction simulation) are [automatically restored](../../../learn/fundamentals/contract-development/storage/state-archival.mdx#contract-data-automatic-restoration) when the `InvokeHostFunctionOp` executes. `RestoreFootprintOp` can be used in rare use cases [described in this section](../../../learn/fundamentals/contract-development/storage/state-archival.mdx#restorefootprintop).
+The manual operation (`RestoreFootprintOp`) is, for the most part, no longer needed starting in Protocol 23, as archived entries included in a transaction's restore list (usually populated during transaction simulation) are [automatically restored](../../../learn/fundamentals/contract-development/storage/state-archival#contract-data-automatic-restoration) when the `InvokeHostFunctionOp` executes. `RestoreFootprintOp` can be used in rare use cases [described in this section](../../../learn/fundamentals/contract-development/storage/state-archival#restorefootprintop).
 
-:::
+</Info>
 
 In this guide, we'll create a utility method named `createRestorationFootprint` used for manually creating a restoration footprint and restore archived data in a contract.
 
@@ -25,7 +24,7 @@ As seen above, all contract data is automatically archived when TTL reaches `0`,
 
 Both types `Instance` and `Persistent` are suitable for storing data that cannot be easily recreated, with the nuance that `Instance` shares the same TTL as the contract instance while `Persistent` does not and, if the contract instance is not archived, `Persistent` data may be archived and need to be restored before invoking the contract.
 
-For a detailed explanation of contract data archival, check out the [State Archival section](./../../../learn/fundamentals/contract-development/storage/state-archival.mdx).
+For a detailed explanation of contract data archival, check out the [State Archival section](./../../../learn/fundamentals/contract-development/storage/state-archival).
 
 ```typescript
 import {
@@ -113,10 +112,10 @@ Next up we are preparing the (Soroban) transaction data with:
 
 Note that for restoration footprints we only need to fill in `readWrite`.
 
-:::caution
+<Warning>
 
-The `diskReadBytes`, `writeBytes`, and `resourceFee` values above are zeroed **placeholders** to keep the example focused on footprint construction. A real restoration will not succeed with these left at `0` — Core compares the restored entry's serialized size against the declared resources and rejects the operation (`RESTORE_FOOTPRINT_RESOURCE_LIMIT_EXCEEDED`) when they are too low. Before signing, populate valid resource values by running the transaction through [simulation](../../../learn/fundamentals/contract-development/contract-interactions/transaction-simulation.mdx) (for example with `server.prepareTransaction`), which fills in the required resources and fee for you.
+The `diskReadBytes`, `writeBytes`, and `resourceFee` values above are zeroed **placeholders** to keep the example focused on footprint construction. A real restoration will not succeed with these left at `0` — Core compares the restored entry's serialized size against the declared resources and rejects the operation (`RESTORE_FOOTPRINT_RESOURCE_LIMIT_EXCEEDED`) when they are too low. Before signing, populate valid resource values by running the transaction through [simulation](../../../learn/fundamentals/contract-development/contract-interactions/transaction-simulation) (for example with `server.prepareTransaction`), which fills in the required resources and fee for you.
 
-:::
+</Warning>
 
 The transaction can now be submitted to the Stellar (test) network & signed to restore the specified contract’s data.
diff --git a/docs/build/guides/archival/extend-persistent-entry-js.mdx b/docs/build/guides/archival/extend-persistent-entry-js.mdx
index d84f69767..fe12543c5 100644
--- a/docs/build/guides/archival/extend-persistent-entry-js.mdx
+++ b/docs/build/guides/archival/extend-persistent-entry-js.mdx
@@ -9,9 +9,9 @@ Every persistent entry on the ledger is a key-value pair made up of:
 
 - a key (the identifier for the data),
 - a value (the data itself), and
-- a [Time To Live](../../../learn/fundamentals/contract-development/storage/state-archival.mdx#ttl) (TTL), which is how many ledgers remain until the entry is no longer live. (The absolute cutoff is stored on the entry itself as its [`liveUntilLedger`](../../../learn/fundamentals/contract-development/storage/state-archival.mdx#live-until-ledger).)
+- a [Time To Live](../../../learn/fundamentals/contract-development/storage/state-archival#ttl) (TTL), which is how many ledgers remain until the entry is no longer live. (The absolute cutoff is stored on the entry itself as its [`liveUntilLedger`](../../../learn/fundamentals/contract-development/storage/state-archival#live-until-ledger).)
 
-Once an entry's TTL runs out, the network archives it. Archived persistent data isn't lost (it can be [restored](./restore-data-js.mdx)), but nothing can read it until that happens. Keeping the TTL topped up before it expires is the cheaper, less exciting path, and that's what we'll walk through here.
+Once an entry's TTL runs out, the network archives it. Archived persistent data isn't lost (it can be [restored](./restore-data-js)), but nothing can read it until that happens. Keeping the TTL topped up before it expires is the cheaper, less exciting path, and that's what we'll walk through here.
 
 By the end of this guide you'll have four helper functions you can drop into a project: one that extends a single persistent entry, one for a contract's instance, one for the Wasm code that instance points to, and one that extends all three together in a single operation.
 
@@ -21,13 +21,13 @@ By the end of this guide you'll have four helper functions you can drop into a p
 2. Build a transaction containing an `extendFootprintTtl` operation with your target TTL, and attach the Soroban transaction data.
 3. Prepare the transaction (this runs simulation to fill in the resources and fee for you), sign it with your secret key, and submit it to the network.
 
-:::note
+<Note>
 
-`extendFootprintTtl` sets a _floor_, not an exact value. Per the [`ExtendFootprintTTLOp` semantics](../../../learn/fundamentals/contract-development/storage/state-archival.mdx#extendfootprintttlop), the operation guarantees each entry in the read-only footprint lives for _at least_ `extendTo` ledgers from now. Entries that already live longer than your target are left alone, so a repeated extension is harmless.
+`extendFootprintTtl` sets a _floor_, not an exact value. Per the [`ExtendFootprintTTLOp` semantics](../../../learn/fundamentals/contract-development/storage/state-archival#extendfootprintttlop), the operation guarantees each entry in the read-only footprint lives for _at least_ `extendTo` ledgers from now. Entries that already live longer than your target are left alone, so a repeated extension is harmless.
 
-There's also a ceiling: an entry can only be extended up to the network's [maximum TTL](../../../learn/fundamentals/contract-development/storage/state-archival.mdx#maximum-ttl), which is a network parameter (check the [network limits](https://lab.stellar.org/network-limits) in the Stellar Lab for the current value).
+There's also a ceiling: an entry can only be extended up to the network's [maximum TTL](../../../learn/fundamentals/contract-development/storage/state-archival#maximum-ttl), which is a network parameter (check the [network limits](https://lab.stellar.org/network-limits) in the Stellar Lab for the current value).
 
-:::
+</Note>
 
 ## Extending a persistent entry
 
@@ -86,13 +86,13 @@ async function extendPersistentEntryTTL(
 
 `Contract.getFootprint()` hands you the ledger key for the deployed contract instance, so you don't have to assemble that one by hand.
 
-:::note
+<Note>
 
 This extends the contract _instance_ only. The Wasm code the instance points to is a separate ledger entry with its own TTL, and an `extendFootprintTtl` operation only touches the keys you actually put in the read-only footprint. A live instance backed by archived code still leaves your contract unusable, so the next section covers the code entry too.
 
 If you're coming from the Rust side, this is a real difference worth internalizing: inside a contract, `env.storage().instance().extend_ttl()` extends the instance and the code together. The operation used here does not.
 
-:::
+</Note>
 
 ```typescript
 import * as StellarSdk from "@stellar/stellar-sdk";
@@ -202,11 +202,11 @@ async function extendContractCodeTTL(
 }
 ```
 
-:::caution
+<Warning>
 
-`getWasmHash` assumes the contract runs an executable that _was deployed_. A [Stellar Asset Contract](../../../tokens/stellar-asset-contract.mdx) instance has a built-in executable instead of a Wasm hash, so `executable().wasmHash()` will throw for one of those. Check `instance.executable().switch()` first if your code has to handle both.
+`getWasmHash` assumes the contract runs an executable that _was deployed_. A [Stellar Asset Contract](../../../tokens/stellar-asset-contract) instance has a built-in executable instead of a Wasm hash, so `executable().wasmHash()` will throw for one of those. Check `instance.executable().switch()` first if your code has to handle both.
 
-:::
+</Warning>
 
 ## Extending all three together
 
@@ -271,11 +271,11 @@ async function extendContractAndPersistentEntry(
 
 That shared `extendTo` is the one real constraint. Entries that need _different_ target TTLs can't share an operation, so extend each one in its own transaction. That's exactly what the `extendPersistentEntryTTL`, `extendContractInstanceTTL`, and `extendContractCodeTTL` helpers above do: each builds its own operation, so each can carry its own `extendTo` target.
 
-:::note
+<Note>
 
 Batching keys into one footprint grows the transaction's resource usage, since `diskReadBytes` has to cover the serialized size of every entry in the read-only set. `server.prepareTransaction` works that out for you, but a large enough batch can bump into the network's transaction limits. If that happens, split the batch across a few transactions.
 
-:::
+</Note>
 
 Putting one of these to work looks like this:
 
diff --git a/docs/build/guides/archival/index.mdx b/docs/build/guides/archival/index.mdx
new file mode 100644
index 000000000..3e2da7ced
--- /dev/null
+++ b/docs/build/guides/archival/index.mdx
@@ -0,0 +1,6 @@
+---
+title: State Archival
+description: "Soroban's novel strategy to combat state bloat can present a learning curve for developers. Here are some quick guides that will help you through the process."
+---
+
+Read more in the [State Archival section](/docs/learn/fundamentals/contract-development/storage/state-archival).
diff --git a/docs/build/guides/archival/restore-contract-js.mdx b/docs/build/guides/archival/restore-contract-js.mdx
index 79a36c31a..6fdb10e3f 100644
--- a/docs/build/guides/archival/restore-contract-js.mdx
+++ b/docs/build/guides/archival/restore-contract-js.mdx
@@ -1,6 +1,5 @@
 ---
 title: Restore a contract using the JavaScript SDK
-hide_table_of_contents: true
 description: Restore archived contract instance or contract code using the JavaScript SDK
 ---
 
@@ -17,11 +16,11 @@ Let's work through how these can be recovered. The recovery process is slightly
 
 Unfortunately, we still need simulation to figure out the _fees_ for our restoration. This, however, can be easily covered by the SDK's [`Server.prepareTransaction()`](https://stellar.github.io/js-soroban-client/Server.html#prepareTransaction) helper, which will do simulation and assembly for us.
 
-:::info
+<Info>
 
-This guide makes use of the (aptly named) `submitTx` function we created in [another guide](../transactions/submit-transaction-wait-js.mdx).
+This guide makes use of the (aptly named) `submitTx` function we created in [another guide](../transactions/submit-transaction-wait-js).
 
-:::
+</Info>
 
 ```typescript
 import {
diff --git a/docs/build/guides/archival/restore-data-js.mdx b/docs/build/guides/archival/restore-data-js.mdx
index f9eb75e12..a5d753ca4 100644
--- a/docs/build/guides/archival/restore-data-js.mdx
+++ b/docs/build/guides/archival/restore-data-js.mdx
@@ -1,14 +1,13 @@
 ---
 title: Restore archived contract data using the JavaScript SDK
-hide_table_of_contents: true
 description: Restore archived persistent contract data using the JavaScript SDK
 ---
 
-:::info
+<Info>
 
-The manual operation (`RestoreFootprintOp`) is, for the most part, no longer needed starting in Protocol 23, as archived entries are automatically restored when they appear in a footprint during `InvokeHostFunctionOp`. `RestoreFootprintOp` can be used in rare use cases [described in this section](../../../learn/fundamentals/contract-development/storage/state-archival.mdx#contract-data-automatic-restoration).
+The manual operation (`RestoreFootprintOp`) is, for the most part, no longer needed starting in Protocol 23, as archived entries are automatically restored when they appear in a footprint during `InvokeHostFunctionOp`. `RestoreFootprintOp` can be used in rare use cases [described in this section](../../../learn/fundamentals/contract-development/storage/state-archival#contract-data-automatic-restoration).
 
-:::
+</Info>
 
 This is a pretty likely occurrence: my piece of persistent data is archived because I haven't interacted with my contract in a while. How do I make it accessible again?
 
@@ -25,11 +24,11 @@ The restoration process we'll use involves three discrete steps:
 
 Here's a function called `submitOrRestoreAndRetry()` that will take care of all those steps for us:
 
-:::info
+<Info>
 
-This guide makes use of the (aptly named) `submitTx` function we created in [another guide](../transactions/submit-transaction-wait-js.mdx).
+This guide makes use of the (aptly named) `submitTx` function we created in [another guide](../transactions/submit-transaction-wait-js).
 
-:::
+</Info>
 
 ```typescript
 import {
diff --git a/docs/build/guides/archival/test-ttl-extension.mdx b/docs/build/guides/archival/test-ttl-extension.mdx
index f74747c63..e70e10b4d 100644
--- a/docs/build/guides/archival/test-ttl-extension.mdx
+++ b/docs/build/guides/archival/test-ttl-extension.mdx
@@ -1,10 +1,9 @@
 ---
 title: Test TTL extension logic in smart contracts
-hide_table_of_contents: true
 description: Test contracts that extend contract data time to live (TTL)
 ---
 
-In order to test contracts that extend the contract data [TTL](../../../learn/fundamentals/contract-development/storage/state-archival.mdx#ttl) via `extend_ttl` storage operations, you can use the TTL getter operation (`get_ttl`) in combination with manipulating the ledger sequence number. Note, that `get_ttl` function is only available for tests and only in Soroban SDK v21+.
+In order to test contracts that extend the contract data [TTL](../../../learn/fundamentals/contract-development/storage/state-archival#ttl) via `extend_ttl` storage operations, you can use the TTL getter operation (`get_ttl`) in combination with manipulating the ledger sequence number. Note, that `get_ttl` function is only available for tests and only in Soroban SDK v21+.
 
 ## Example
 
diff --git a/docs/build/guides/auth/README.mdx b/docs/build/guides/auth/README.mdx
deleted file mode 100644
index 2148ec832..000000000
--- a/docs/build/guides/auth/README.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: Contract Authorization
-hide_table_of_contents: true
-sidebar_position: 1
----
-
-Learn about smart contract authorization on Stellar.
diff --git a/docs/build/guides/auth/check-auth-tutorials.mdx b/docs/build/guides/auth/check-auth-tutorials.mdx
index 51336ef83..132fad837 100644
--- a/docs/build/guides/auth/check-auth-tutorials.mdx
+++ b/docs/build/guides/auth/check-auth-tutorials.mdx
@@ -1,18 +1,10 @@
 ---
 title: Using __check_auth in interesting ways
+og:title: "Using __check_auth in interesting ways"
+og:description: "This guide will walk you through interesting ways you can use __check_auth in your Soroban applications"
 description: Two guides that walk through using __check_auth
 ---
 
-<head>
-  <title>Using __check_auth in interesting ways</title>
-  <meta charSet="utf-8" />
-  <meta property="og:title" content="Using __check_auth in interesting ways" />
-  <meta
-    property="og:description"
-    content="This guide will walk you through interesting ways you can use __check_auth in your Soroban applications"
-  />
-</head>
-
 ## Tutorial 1: time based restriction on token transfers
 
 Imagine a multi-sig account contract where certain actions, like transferring tokens, need to be controlled by the time elapsed between consecutive transfers. For example, a token transfer should only be allowed if a certain period of time has passed since the last transfer. This can be useful in scenarios where you want to limit the frequency of transactions to prevent misuse or to implement rate limiting.
@@ -601,7 +593,7 @@ fn test_token_auth() {
 
 Imagine a world where traditional passwords are obsolete. In this world, WebAuthn (Web Authentication) has become the standard for secure online interactions. Alice, a blockchain enthusiast, wants to create a wallet that leverages WebAuthn technology for enhanced security. She decides to implement a WebAuthn wallet on Stellar, allowing users to manage their digital assets using their device's biometric features or security keys (e.g., YubiKey, Google Titan Security Key, etc.).
 
-### Base concepts
+### Base concepts {#base-concepts-1}
 
 WebAuthn is a web standard for passwordless authentication. It allows users to authenticate using biometrics (like fingerprints or facial recognition).
 
@@ -612,15 +604,15 @@ The WebAuthn wallet implemented in this tutorial will be able to:
 3. Differentiate between admin and regular users
 4. Allow contract updates for future improvements
 
-:::info
+<Info>
 
 This tutorial's code credit goes to [@kalepail's](https://github.com/kalepail) work on passkeys, which you can explore more [here](https://github.com/kalepail/passkey-kit).
 
-:::
+</Info>
 
-### Code walkthrough
+### Code walkthrough {#code-walkthrough-1}
 
-#### Contract structure and imports
+#### Contract structure and imports {#contract-structure-and-imports-1}
 
 This section sets up the contract structure and imports necessary components from the Soroban SDK.
 
@@ -1071,11 +1063,11 @@ mod test {
 }
 ```
 
-#### Summary
+#### Summary {#summary-1}
 
 This WebAuthn wallet implementation provides a secure and user-friendly way to manage digital assets on Stellar. It leverages the security benefits of WebAuthn while maintaining the flexibility needed for blockchain interactions.
 
-#### Complete code
+#### Complete code {#complete-code-1}
 
 Here are all the snippets stacked together in a single file for convenience:
 
diff --git a/docs/build/guides/auth/contract-authorization.mdx b/docs/build/guides/auth/contract-authorization.mdx
index 261b7ee56..8e6464330 100644
--- a/docs/build/guides/auth/contract-authorization.mdx
+++ b/docs/build/guides/auth/contract-authorization.mdx
@@ -1,6 +1,5 @@
 ---
 title: Smart contract authorization starter guide
-hide_table_of_contents: true
 description: Learn about smart contract auth on Stellar
 ---
 
@@ -8,7 +7,7 @@ description: Learn about smart contract auth on Stellar
 
 Smart contracts can be invoked without any caller authorization by default. The functionality of the smart contract can either justify, or even require, authorization. Let’s say we want to read or write sensitive information: then access to the contract should be restricted through authorization. Authorization is required if the contract signs transactions.
 
-For a deeper understanding of how authorization works, see the [Security](../../../learn/fundamentals/contract-development/authorization.mdx) section.
+For a deeper understanding of how authorization works, see the [Security](../../../learn/fundamentals/contract-development/authorization) section.
 
 ### Address-based authorization
 
@@ -177,7 +176,7 @@ The following output should appear:
 
 If the authorization doesn’t pass, the function will not reach the return line of the code.
 
-#### Test
+#### Test {#test-1}
 
 Contract functions using `require_auth_for_args()` for authorization can be tested with `cargo test` by mocking the authorization. The test is very similar to the test used in the `require_auth()` section, where the testing is done in two parts.
 
@@ -246,7 +245,7 @@ test test::test ... ok
 
 Smart contracts can invoke functions in other contracts (called cross-contract calls). These direct calls are implicitly authorized by the invoker and do not need to be authorized. However, the contract function being invoked may require authorization from a user other than the contract itself. An example could be a transfer function, where an external user may have to authorize the transfer to the current contract.
 
-To illustrate how to add authorization to a simple cross-contract invocation, we use the [Cross Contract Calls example contract](../../smart-contracts/example-contracts/cross-contract-call.mdx), which consists of two separate contracts, one that has a simple addition contract function, and another contract to invoke the first one.
+To illustrate how to add authorization to a simple cross-contract invocation, we use the [Cross Contract Calls example contract](../../smart-contracts/example-contracts/cross-contract-call), which consists of two separate contracts, one that has a simple addition contract function, and another contract to invoke the first one.
 
 ### Invoking contract
 
@@ -312,7 +311,7 @@ The function `__check_auth()` may be invoked for a given contract if two conditi
 
 #### How it works
 
-`__check_auth()` verifies the credentials and policy for an account address whenever another contract calls `require_auth`. A minimal implementation, shown below and documented end-to-end in the [Simple Account example](../../smart-contracts/example-contracts/simple-account.mdx), loads a stored Ed25519 key and verifies the signature payload against it:
+`__check_auth()` verifies the credentials and policy for an account address whenever another contract calls `require_auth`. A minimal implementation, shown below and documented end-to-end in the [Simple Account example](../../smart-contracts/example-contracts/simple-account), loads a stored Ed25519 key and verifies the signature payload against it:
 
 ```rust
    pub fn __check_auth(
@@ -331,7 +330,7 @@ The function `__check_auth()` may be invoked for a given contract if two conditi
    }
 ```
 
-More advanced accounts build on the same structure: the [Complex Account example](../../smart-contracts/example-contracts/complex-account.mdx) adds multiple signers, signature weights, and spend limits enforced via `auth_context` traversal.
+More advanced accounts build on the same structure: the [Complex Account example](../../smart-contracts/example-contracts/complex-account) adds multiple signers, signature weights, and spend limits enforced via `auth_context` traversal.
 
 #### Authorization logic
 
@@ -364,15 +363,15 @@ fn test_account() {
 }
 ```
 
-That snippet highlights the key inputs: contract address, payload, signature, and authorization tree. For the full tests, see the [Simple Account example](../../smart-contracts/example-contracts/simple-account.mdx); the Complex Account doc includes multisig and policy coverage.
+That snippet highlights the key inputs: contract address, payload, signature, and authorization tree. For the full tests, see the [Simple Account example](../../smart-contracts/example-contracts/simple-account); the Complex Account doc includes multisig and policy coverage.
 
 #### `set_auths()`
 
-:::note
+<Note>
 
 `set_auths()` may not be relevant for most developers.
 
-:::
+</Note>
 
 Another method is to use `set_auths()`, which will `call __check_auth()` when the contract function is called, similar to how the host will `call __check_auth()` on Testnet or Mainnet. This method is more complex, and provides a lower-level control over the authorization process in tests.
 
@@ -447,6 +446,6 @@ Similar to how the host executes authorization on Testnet and Mainnet, `set_auth
 
 A `SorobanAuthorizationEntry` contains authorization credentials and contract invocation details. The credentials part specifies the contract address of `the __check_auth()` function, and relevant authorization data. The root invocation part specifies the contract ID, the name of the function being tested, and the function’s arguments.
 
-For more information about authorization details provided in `set_auths()`, see the [Stellar Transactions](../../../learn/fundamentals/contract-development/contract-interactions/stellar-transaction.mdx) documentation.
+For more information about authorization details provided in `set_auths()`, see the [Stellar Transactions](../../../learn/fundamentals/contract-development/contract-interactions/stellar-transaction) documentation.
 
 Testing using `set_auths()` is more complex than testing using `try_invoke_contract_check_auth`, but in return, it allows for more advanced testing scenarios. If more advanced testing, e.g., testing specific authorization edge cases, is required, `set_auths()` might be a good choice. Otherwise, `try_invoke_contract_check_auth` generally is the recommended method for testing.
diff --git a/docs/build/guides/auth/index.mdx b/docs/build/guides/auth/index.mdx
new file mode 100644
index 000000000..004769424
--- /dev/null
+++ b/docs/build/guides/auth/index.mdx
@@ -0,0 +1,4 @@
+---
+title: Contract Authorization
+description: "Learn about smart contract authorization on Stellar."
+---
diff --git a/docs/build/guides/basics/README.mdx b/docs/build/guides/basics/README.mdx
deleted file mode 100644
index 40ac7c7c7..000000000
--- a/docs/build/guides/basics/README.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: Stellar Basics
-hide_table_of_contents: true
-sidebar_position: 80
----
-
-Learn how to perform basic actions on the Stellar network.
diff --git a/docs/build/guides/basics/automate-reset-data.mdx b/docs/build/guides/basics/automate-reset-data.mdx
index 64c13d154..a0fb5f180 100644
--- a/docs/build/guides/basics/automate-reset-data.mdx
+++ b/docs/build/guides/basics/automate-reset-data.mdx
@@ -1,30 +1,19 @@
 ---
 title: Automating Testnet and Futurenet reset data
+og:title: "Automating Testnet and Futurenet Reset Data in Stellar"
+og:description: "Automating Testnet and Futurenet Reset Data in Stellar"
 description: Learn how to automate Testnet and Futurenet reset data on Stellar
 ---
 
-<head>
-  <title>{`Automating Testnet and Futurenet Reset Data in Stellar`}</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Automating Testnet and Futurenet Reset Data in Stellar"
-  />
-  <meta
-    property="og:description"
-    content="Automating Testnet and Futurenet Reset Data in Stellar"
-  />
-</head>
-
 ## Overview
 
-Stellar operates two primary testing environments: the [Testnet and the Futurenet](../../../networks/README.mdx). These networks allow developers to experiment with Stellar features without risking real assets. Periodically, these networks are reset to ensure they remain clean and manageable.
+Stellar operates two primary testing environments: the [Testnet and the Futurenet](/docs/networks). These networks allow developers to experiment with Stellar features without risking real assets. Periodically, these networks are reset to ensure they remain clean and manageable.
 
 ## What is the Testnet and Futurenet reset?
 
 Testnet and Futurenet are reset periodically to the genesis ledger to declutter the network, remove spam, reduce the time needed to catch up on the latest ledger, and help maintain the system. These resets take place approximately quarterly. Resets clear all ledger entries (accounts, trustlines, offers, smart contract data, etc.), transactions, and historical data from Stellar Core, Horizon, and the Stellar RPC, which is why developers should not rely on the persistence of accounts or the state of any balances when using Testnet or Futurenet.
 
-You can check current reset dates [here](../../../networks/README.mdx#testnet-and-futurenet-data-reset).
+You can check current reset dates [here](/docs/networks#testnet-and-futurenet-data-reset).
 
 ## Why resets are important
 
@@ -43,7 +32,7 @@ Automating blockchain state on Stellar's Testnet and Futurenet can streamline de
 
 - [Node.js](https://nodejs.org/en) and `npm` installed.
 - Stellar SDK for [JavaScript](https://www.npmjs.com/package/@stellar/stellar-sdk) and `fs` installed
-- An understanding of the rudimentary, retry-enabled transaction polling function `submitTx` which we outlined in [another guide](../transactions/submit-transaction-wait-js.mdx)
+- An understanding of the rudimentary, retry-enabled transaction polling function `submitTx` which we outlined in [another guide](../transactions/submit-transaction-wait-js)
 
 ### Code
 
@@ -366,7 +355,7 @@ Initializes the Stellar server connection, Creates two accounts, Issues a custom
 
 `sleep(ms)`: A utility function to introduce delays in asynchronous operations.
 
-`submitTx(tx)`: a retry-enabled transaction submission function `submitTx` outlined in [another guide](../transactions/submit-transaction-wait-js.mdx)
+`submitTx(tx)`: a retry-enabled transaction submission function `submitTx` outlined in [another guide](../transactions/submit-transaction-wait-js)
 
 ### Conclusion
 
diff --git a/docs/build/guides/basics/classic-transition.mdx b/docs/build/guides/basics/classic-transition.mdx
index b59141760..4fc2c3a71 100644
--- a/docs/build/guides/basics/classic-transition.mdx
+++ b/docs/build/guides/basics/classic-transition.mdx
@@ -1,6 +1,5 @@
 ---
 title: Add support for smart contracts
-sidebar_position: 50
 description: Considerations for integrating with Stellar’s smart contracts specifically for wallets and exchanges
 ---
 
@@ -20,28 +19,28 @@ You can set up an RPC environment by hosting your own node or using a third-part
 
 ### Ingesting Smart Contract Events
 
-Horizon offers an effects endpoint that describes state changes executed by classic operations. Similarly, contracts emit [events](../../../learn/fundamentals/stellar-data-structures/events.mdx) that describe changes to their state, which can be fetched via RPC's API. Off-chain solutions can [monitor and ingest these events](../../../build/guides/events/ingest.mdx) (for token transfers or protocol updates) and remain in sync with on-chain data. Each event is defined by the contract and is subject to standards applied to the implementation. Depending on the requirements for retention, a solution might have to handle ingestion directly or use a [third-party service](../../../data/indexers/README.mdx) for a longer-term history.
+Horizon offers an effects endpoint that describes state changes executed by classic operations. Similarly, contracts emit [events](../../../learn/fundamentals/stellar-data-structures/events) that describe changes to their state, which can be fetched via RPC's API. Off-chain solutions can [monitor and ingest these events](../../../build/guides/events/ingest) (for token transfers or protocol updates) and remain in sync with on-chain data. Each event is defined by the contract and is subject to standards applied to the implementation. Depending on the requirements for retention, a solution might have to handle ingestion directly or use a [third-party service](/docs/data/indexers) for a longer-term history.
 
 ### Simulating Transaction
 
-While events should be used to monitor changes to a contract’s state, clients may also need to determine the current state of a contract. [Simulation](../../../build/guides/transactions/simulateTransaction-Deep-Dive.mdx) allows clients to execute contract invocations with incurring fees or finalizing changes, making it an ideal approach for fetching contracts’ current state. For example, clients can call the balance function on a [SEP-41](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0041.md)-compliant token contract to fetch a user’s current balance.
+While events should be used to monitor changes to a contract’s state, clients may also need to determine the current state of a contract. [Simulation](../../../build/guides/transactions/simulateTransaction-Deep-Dive) allows clients to execute contract invocations with incurring fees or finalizing changes, making it an ideal approach for fetching contracts’ current state. For example, clients can call the balance function on a [SEP-41](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0041.md)-compliant token contract to fetch a user’s current balance.
 
 ## 3. Transaction Workflow Changes
 
 ### Building Transactions
 
-Transaction construction involves specifying a call to a contract function rather than any of the built-in operations Stellar offers. When building these contract calls, it is necessary to specify the relevant contract ID and function arguments according to the contract interface. See more at [Documentation for Contract Interaction - Stellar Transaction](../../../learn/fundamentals/contract-development/contract-interactions/stellar-transaction.mdx).
+Transaction construction involves specifying a call to a contract function rather than any of the built-in operations Stellar offers. When building these contract calls, it is necessary to specify the relevant contract ID and function arguments according to the contract interface. See more at [Documentation for Contract Interaction - Stellar Transaction](../../../learn/fundamentals/contract-development/contract-interactions/stellar-transaction).
 
-You can still use the libraries or tools you’re already familiar with to assemble these transactions, [but keep in mind the extra steps required for contract invocation](../../../build/guides/transactions/invoke-contract-tx-sdk.mdx).
+You can still use the libraries or tools you’re already familiar with to assemble these transactions, [but keep in mind the extra steps required for contract invocation](../../../build/guides/transactions/invoke-contract-tx-sdk).
 
-### Simulating Transaction
+### Simulating Transaction {#simulating-transaction-1}
 
-Transactions that execute smart contracts must be [simulated](../../../build/guides/transactions/simulateTransaction-Deep-Dive.mdx) before sending. That is because simulation doesn’t just provide the results of executing transactions; it also provides essential information such as the transaction’s read/write [footprint](../../../learn/fundamentals/contract-development/contract-interactions/transaction-simulation.mdx#footprint) and [authorizations](../../../learn/fundamentals/contract-development/contract-interactions/transaction-simulation.mdx#authorization) needed, and clients must add this information to the transaction before sending it to the network for execution.
+Transactions that execute smart contracts must be [simulated](../../../build/guides/transactions/simulateTransaction-Deep-Dive) before sending. That is because simulation doesn’t just provide the results of executing transactions; it also provides essential information such as the transaction’s read/write [footprint](../../../learn/fundamentals/contract-development/contract-interactions/transaction-simulation#footprint) and [authorizations](../../../learn/fundamentals/contract-development/contract-interactions/transaction-simulation#authorization) needed, and clients must add this information to the transaction before sending it to the network for execution.
 
-### Signing & Auth Entries
+### Signing & Auth Entries {#signing--auth-entries}
 
-Smart contracts can define their own [custom authorization logic](../../../learn/fundamentals/contract-development/authorization.mdx), meaning you might need [additional signatures for specific authorization data](../../../learn/fundamentals/contract-development/contract-interactions/stellar-transaction.mdx#authorization-data) to prove permission for certain contract calls. Each contract can have its own requirements, so a good practice is to [leverage transaction simulations to identify specific authorization requirements for a transaction](../../../learn/fundamentals/contract-development/contract-interactions/transaction-simulation.mdx#authorization).
+Smart contracts can define their own [custom authorization logic](../../../learn/fundamentals/contract-development/authorization), meaning you might need [additional signatures for specific authorization data](../../../learn/fundamentals/contract-development/contract-interactions/stellar-transaction#authorization-data) to prove permission for certain contract calls. Each contract can have its own requirements, so a good practice is to [leverage transaction simulations to identify specific authorization requirements for a transaction](../../../learn/fundamentals/contract-development/contract-interactions/transaction-simulation#authorization).
 
 ### Asynchronous Transaction Submission
 
-Unlike Horizon, [RPC only queues transactions for inclusion rather than waiting for final confirmation](../../../data/apis/rpc/api-reference/methods/sendTransaction). Therefore, it is necessary to [poll the transaction’s status](../../../data/apis/rpc/api-reference/methods/getTransaction) to determine if a transaction eventually succeeds or fails. This asynchronous model, as well as other common challenges, can be seen at the [Documentation for Dapp Development - Common Pitfalls](../../../build/guides/dapps/frontend-guide.mdx#7-common-pitfalls).
+Unlike Horizon, [RPC only queues transactions for inclusion rather than waiting for final confirmation](../../../data/apis/rpc/api-reference/methods/sendTransaction). Therefore, it is necessary to [poll the transaction’s status](../../../data/apis/rpc/api-reference/methods/getTransaction) to determine if a transaction eventually succeeds or fails. This asynchronous model, as well as other common challenges, can be seen at the [Documentation for Dapp Development - Common Pitfalls](../../../build/guides/dapps/frontend-guide#7-common-pitfalls).
diff --git a/docs/build/guides/basics/index.mdx b/docs/build/guides/basics/index.mdx
new file mode 100644
index 000000000..38d8ccd19
--- /dev/null
+++ b/docs/build/guides/basics/index.mdx
@@ -0,0 +1,4 @@
+---
+title: Stellar Basics
+description: "Learn how to perform basic actions on the Stellar network."
+---
diff --git a/docs/build/guides/basics/verify-trustlines.mdx b/docs/build/guides/basics/verify-trustlines.mdx
index 6077683ec..4059f3e3a 100644
--- a/docs/build/guides/basics/verify-trustlines.mdx
+++ b/docs/build/guides/basics/verify-trustlines.mdx
@@ -1,22 +1,21 @@
 ---
 title: Verify Trustlines
-sidebar_position: 40
 description: Learn to verify trustlines before sending transactions to Stellar.
 ---
 
-When performing payments on Stellar for [Stellar Assets](../../../tokens/README.mdx) other than XLM, it is important to ensure that the receiving account has a trustline established for the asset being sent. This one-pager provides a quick overview of how to verify trustlines before sending transactions, ensuring that payments are processed smoothly and allowing for application to appropriately handle cases where trustlines are not established or invalid.
+When performing payments on Stellar for [Stellar Assets](/docs/tokens) other than XLM, it is important to ensure that the receiving account has a trustline established for the asset being sent. This one-pager provides a quick overview of how to verify trustlines before sending transactions, ensuring that payments are processed smoothly and allowing for application to appropriately handle cases where trustlines are not established or invalid.
 
 ## Why Verify Trustlines?
 
-In Stellar, trustlines are used to establish a relationship between an account and a Stellar Asset. They are created with the [change trust](../../../learn/fundamentals/transactions/list-of-operations.mdx#change-trust) operation, and indicate that the account is willing to hold and transact with that asset. If a trustline is not established for an asset, the account cannot receive payments in that asset, leading to transaction failures.
+In Stellar, trustlines are used to establish a relationship between an account and a Stellar Asset. They are created with the [change trust](../../../learn/fundamentals/transactions/list-of-operations#change-trust) operation, and indicate that the account is willing to hold and transact with that asset. If a trustline is not established for an asset, the account cannot receive payments in that asset, leading to transaction failures.
 
-Furthermore, asset issuers may enforce specific requirements through trustlines, such as maximum balances an account can hold or granular authorization to receive/send the asset or to maintain liabilities. See the [Asset Design Considerations](../../../tokens/control-asset-access.mdx) for more details on how control flags and trustlines can be used to customize these behaviors.
+Furthermore, asset issuers may enforce specific requirements through trustlines, such as maximum balances an account can hold or granular authorization to receive/send the asset or to maintain liabilities. See the [Asset Design Considerations](../../../tokens/control-asset-access) for more details on how control flags and trustlines can be used to customize these behaviors.
 
 Verifying trustlines before sending transactions helps ensure that the receiving account meets the requirements and can successfully receive the asset. This allows for the application to handle cases where trustlines are not established or invalid, providing clear feedback and a smooth user experience while preventing failed transactions.
 
 ## Checking a Trustline through the Stellar RPC
 
-Unlike Horizon, [Stellar RPC does not return an account's trustlines alongside the account itself](../../../data/apis/migrate-from-horizon-to-rpc.mdx) — a trustline is its own ledger entry, so you look it up directly. The JavaScript SDK gives you two ways to do that:
+Unlike Horizon, [Stellar RPC does not return an account's trustlines alongside the account itself](../../../data/apis/migrate-from-horizon-to-rpc) — a trustline is its own ledger entry, so you look it up directly. The JavaScript SDK gives you two ways to do that:
 
 - `getAssetBalance` is the quick path. One call tells you whether the trustline exists at all, whether it is authorized, and how much of the asset the account currently holds.
 - `getLedgerEntries` gives you the raw trustline entry, which you need when you also care about the trustline's **limit** — the maximum balance the account is willing to hold.
@@ -27,9 +26,9 @@ Most applications only need the first. Reach for the second when a large payment
 
 The following snippet checks that the destination account exists, that it trusts the asset, and that the trustline is authorized to receive it:
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 import { Asset } from "@stellar/stellar-sdk";
 import { Server } from "@stellar/stellar-sdk/rpc";
 
@@ -91,19 +90,18 @@ console.log(
 // Proceed with sending the payment...
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::tip
+<Tip>
 
-`getAssetBalance` also accepts a contract address, so the same call verifies a Soroban contract's balance of the asset through its [Stellar Asset Contract](../../../tokens/stellar-asset-contract.mdx).
+`getAssetBalance` also accepts a contract address, so the same call verifies a Soroban contract's balance of the asset through its [Stellar Asset Contract](../../../tokens/stellar-asset-contract).
 
-:::
-
-:::warning
+</Tip>
+<Warning>
 
 `getAssetBalance` raises the same `Trustline for CODE:ISSUER not found for ACCOUNT` error whether the trustline is genuinely absent or the lookup simply failed — a timeout or an unreachable RPC endpoint surfaces as "not found" too. If your application needs to tell those cases apart, use `getLedgerEntries` instead: it returns an empty `entries` array for a missing trustline and only rejects on a transport error.
 
-:::
+</Warning>
 
 ### Checking the trustline limit
 
@@ -111,11 +109,11 @@ A trustline also carries a `limit`: the maximum balance of the asset the account
 
 `getAssetBalance` does not surface the limit, so we fetch the raw trustline ledger entry with `getLedgerEntries`.
 
-Amounts are stored on the ledger as int64 stroops, and the largest representable amount — 922,337,203,685.4775807 — exceeds what a JavaScript `Number` can hold exactly. Trustline limits routinely sit at that maximum, so this example keeps the arithmetic in `BigInt` stroops; converting to `Number` first can silently misjudge whether a payment fits. See [Amount precision](../../../learn/fundamentals/stellar-data-structures/assets.mdx#amount-precision) for the full picture.
+Amounts are stored on the ledger as int64 stroops, and the largest representable amount — 922,337,203,685.4775807 — exceeds what a JavaScript `Number` can hold exactly. Trustline limits routinely sit at that maximum, so this example keeps the arithmetic in `BigInt` stroops; converting to `Number` first can silently misjudge whether a payment fits. See [Amount precision](../../../learn/fundamentals/stellar-data-structures/assets#amount-precision) for the full picture.
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 import { Asset, Keypair, xdr } from "@stellar/stellar-sdk";
 import { Server } from "@stellar/stellar-sdk/rpc";
 
@@ -198,7 +196,7 @@ console.log(
 // Proceed with sending the payment...
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## Checking a Trustline through the Stellar Asset Contract (SAC)
 
@@ -210,9 +208,9 @@ This function can be accessed directly in a smart contract invocation as the exa
 
 Note that `authorized` only reports the trustline's authorization state. If the account has no trustline for the asset at all, the invocation does not return `false` — the simulation fails with `Error(Contract, #13)` (`trustline entry is missing for account`), so the two cases are handled in different branches below. If you also need to check the trustline's limit, use the `getLedgerEntries` approach shown above.
 
-:::info
+<Info>
 
-To use the RPC example below you should first generate the contract bindings so the client can be used accordingly. This can be achieved through the [Stellar CLI](../../../tools/cli/README.mdx).
+To use the RPC example below you should first generate the contract bindings so the client can be used accordingly. This can be achieved through the [Stellar CLI](/docs/tools/cli).
 
 E.g.: Generating the typescript bindings for the SAC of a given asset. The generated package takes its name from the output directory, so `--output-dir=./sac` is what makes `import ... from "sac"` below resolve:
 
@@ -220,13 +218,13 @@ E.g.: Generating the typescript bindings for the SAC of a given asset. The gener
 stellar contract bindings typescript --network=testnet --contract-id=CBIELTK6YBZJU5UP2WWQEUCYKLPU6AUNZ2BQ4WWFEIE3USCIHMXQDAMA --output-dir=./sac
 ```
 
-:::
+</Info>
 
 Given a receiver address, the following code snippet demonstrates how to simulate a transaction to check if a trustline exists for a specific asset:
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 import { Asset, Networks } from "@stellar/stellar-sdk";
 import { Client } from "sac";
 import { Server } from "@stellar/stellar-sdk/rpc";
@@ -302,4 +300,4 @@ try {
 // If the trustline is authorized, we can proceed with sending the payment...
 ```
 
-</CodeExample>
+</CodeGroup>
diff --git a/docs/build/guides/contract-accounts/README.mdx b/docs/build/guides/contract-accounts/README.mdx
deleted file mode 100644
index 75f9d5cd0..000000000
--- a/docs/build/guides/contract-accounts/README.mdx
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: Contract Accounts
-hide_table_of_contents: true
-sidebar_position: 5
-description: Build, evaluate, and extend contract accounts on Stellar.
----
-
-Contract accounts are smart contracts that act like accounts. They hold balances and use `__check_auth` to decide who can act and under what conditions.
-
-Use a contract account when:
-
-- You need custom authentication in the contract (passkeys/WebAuthn, hardware keys, or other signer checks).
-- You need on chain rules such as spend caps, allow lists, or timelocks.
-
-Stay with a classic account when:
-
-- You want the simplest path: one private key, fund the account, no extra contract code or infrastructure.
-- You must interoperate with systems/tools that expect memos (for example, some exchanges require payments with memos from a G-address; contract account payments go through the Stellar Asset Contract as muxed transfers, so transfers from contracts are not supported by exchanges today).
-
-Quick links:
-
-- [Simple Account example](../../smart-contracts/example-contracts/simple-account.mdx)
-- [Complex Account example](../../smart-contracts/example-contracts/complex-account.mdx)
-- [Contract authorization starter guide](../auth/contract-authorization.mdx) and [Authorization fundamentals](../../../learn/fundamentals/contract-development/authorization.mdx)
-- [Choose a fee sponsorship approach](../transactions/fee-sponsorship.mdx): contract accounts can't pay their own transaction fees
diff --git a/docs/build/guides/contract-accounts/advanced-patterns.mdx b/docs/build/guides/contract-accounts/advanced-patterns.mdx
index eec438032..33389bf0b 100644
--- a/docs/build/guides/contract-accounts/advanced-patterns.mdx
+++ b/docs/build/guides/contract-accounts/advanced-patterns.mdx
@@ -1,7 +1,6 @@
 ---
 title: Advanced contract account patterns
 description: Layer spend limits, allow lists, time rules, and other guardrails onto contract accounts.
-sidebar_position: 40
 ---
 
 Use these patterns to extend a basic contract account with guardrails. Put the logic in `__check_auth` or a helper it calls, and test both the allow and deny paths. Treat signer rules as “who can act” and policy rules as “under what conditions.”
@@ -12,7 +11,7 @@ Use these patterns to extend a basic contract account with guardrails. Put the l
 - Derive a window key from the ledger timestamp (for example, `day = timestamp / 86_400`) and reset the total when the window changes.
 - On each request, check the remaining allowance; if the amount would exceed it, reject and emit an event with the attempted amount and remaining allowance.
 
-See the [Complex Account example](../../smart-contracts/example-contracts/complex-account.mdx) for a reference implementation with weighted signers and limits.
+See the [Complex Account example](../../smart-contracts/example-contracts/complex-account) for a reference implementation with weighted signers and limits.
 
 ## Allow lists
 
@@ -43,7 +42,7 @@ See the [Complex Account example](../../smart-contracts/example-contracts/comple
 
 ## Where to go next
 
-- See these patterns applied in the [contract account examples](./examples.mdx).
+- See these patterns applied in the [contract account examples](./examples).
 - Explore reference implementations and libraries:
   - [OpenZeppelin Smart Account](https://docs.openzeppelin.com/stellar-contracts/accounts/smart-account): modular signer/policy framework in [OpenZeppelin Stellar contracts](https://github.com/OpenZeppelin/stellar-contracts)
   - [Smart Account Kit](https://github.com/stellar/smart-account-kit): TypeScript SDK for deploying and signing with smart accounts
diff --git a/docs/build/guides/contract-accounts/examples.mdx b/docs/build/guides/contract-accounts/examples.mdx
index 3da9a45dc..8f977dad0 100644
--- a/docs/build/guides/contract-accounts/examples.mdx
+++ b/docs/build/guides/contract-accounts/examples.mdx
@@ -1,7 +1,6 @@
 ---
 title: Contract account examples
 description: Real projects that showcase policy signers, passkeys, and contract-account UX on Stellar.
-sidebar_position: 50
 ---
 
 Use these projects as references or starting points. They are community-built; review and test before reusing in production.
@@ -27,7 +26,7 @@ An app that uses passkeys to sign Stellar smart contract transactions.
 - View the [demo](https://passkey.sorobanbyexample.org)
 - View the [code](https://github.com/kalepail/soroban-passkey)
 - Watch the [demo video](https://www.youtube.com/watch?v=y38_O4oIvbY)
-- Watch the [discussion](/meetings/2024/05/09)
+- Watch the [discussion](https://developers.stellar.org/meetings/2024/05/09)
 - Read the [blog](https://kalepail.com/blockchain/the-passkey-powered-future-of-web3)
 
 ### Super Peach
@@ -44,4 +43,4 @@ A passkey-powered internet guestbook from yesteryear built with smart contracts
 
 - View the [demo](https://ye-olde-guestbook.vercel.app)
 - View the [code](https://github.com/ElliotFriend/ye-olde-guestbook)
-- Read the [tutorial](../../apps/guestbook/README.mdx)
+- Read the [tutorial](/docs/build/apps/guestbook)
diff --git a/docs/build/guides/contract-accounts/index.mdx b/docs/build/guides/contract-accounts/index.mdx
new file mode 100644
index 000000000..30dd175b9
--- /dev/null
+++ b/docs/build/guides/contract-accounts/index.mdx
@@ -0,0 +1,23 @@
+---
+title: Contract Accounts
+description: Build, evaluate, and extend contract accounts on Stellar.
+---
+
+Contract accounts are smart contracts that act like accounts. They hold balances and use `__check_auth` to decide who can act and under what conditions.
+
+Use a contract account when:
+
+- You need custom authentication in the contract (passkeys/WebAuthn, hardware keys, or other signer checks).
+- You need on chain rules such as spend caps, allow lists, or timelocks.
+
+Stay with a classic account when:
+
+- You want the simplest path: one private key, fund the account, no extra contract code or infrastructure.
+- You must interoperate with systems/tools that expect memos (for example, some exchanges require payments with memos from a G-address; contract account payments go through the Stellar Asset Contract as muxed transfers, so transfers from contracts are not supported by exchanges today).
+
+Quick links:
+
+- [Simple Account example](/docs/build/smart-contracts/example-contracts/simple-account)
+- [Complex Account example](/docs/build/smart-contracts/example-contracts/complex-account)
+- [Contract authorization starter guide](/docs/build/guides/auth/contract-authorization) and [Authorization fundamentals](/docs/learn/fundamentals/contract-development/authorization)
+- [Choose a fee sponsorship approach](/docs/build/guides/transactions/fee-sponsorship): contract accounts can't pay their own transaction fees
diff --git a/docs/build/guides/contract-accounts/smart-wallets.mdx b/docs/build/guides/contract-accounts/smart-wallets.mdx
index 816b79ba1..7a79aaca7 100644
--- a/docs/build/guides/contract-accounts/smart-wallets.mdx
+++ b/docs/build/guides/contract-accounts/smart-wallets.mdx
@@ -1,6 +1,6 @@
 ---
 title: Smart wallets
-sidebar_position: 10
+description: "Smart wallets are contract accounts that act as user wallets."
 ---
 
 Smart wallets are contract accounts that act as user wallets. They hold assets and enforce authorization in `__check_auth` instead of a single secret key. Passkeys (WebAuthn) are common, but you can also use Ed25519 keys, policy signers, session keys or anything the contract can verify.
@@ -30,7 +30,7 @@ Benefits:
 - WebAuthn is the browser standard for passwordless auth.
 - secp256r1 is the curve most authenticators use; Stellar verifies it on-chain.
 - Passkeys are the platform or hardware-backed credentials that implement WebAuthn.
-- See [examples](./examples.mdx) for real projects.
+- See [examples](./examples) for real projects.
 
 ## Passkeys in practice
 
@@ -44,7 +44,7 @@ Benefits:
 
 There are two TypeScript SDKs for building passkey smart wallets. They're siblings rather than old and new versions of the same thing: each one targets a different wallet contract with a different on-chain authorization model, so they aren't drop-in compatible. Pick the one whose model fits your app.
 
-- **Smart Account Kit**: deploys and drives [OpenZeppelin Smart Account](#accounts-and-relayers) contracts, where authorization runs through context rules, signers, and policies. Reach for it when you want thresholds, spending limits, or other policy-driven rules. Supports passkey (WebAuthn), Ed25519, and policy signers. The [guestbook tutorial](../../apps/guestbook/README.mdx) is built with it.
+- **Smart Account Kit**: deploys and drives [OpenZeppelin Smart Account](#accounts-and-relayers) contracts, where authorization runs through context rules, signers, and policies. Reach for it when you want thresholds, spending limits, or other policy-driven rules. Supports passkey (WebAuthn), Ed25519, and policy signers. The [guestbook tutorial](/docs/build/apps/guestbook) is built with it.
   - Code: [github.com/stellar/smart-account-kit](https://github.com/stellar/smart-account-kit)
 - **Passkey Kit**: ships its own smart wallet contract, which authorizes with a flat map of signatures from passkey (secp256r1), Ed25519, or policy signers. Its repository states that the wallet contract and SDKs have not been independently audited, so review them yourself before they guard real value.
   - Code: [github.com/stellar/passkey-kit](https://github.com/stellar/passkey-kit)
diff --git a/docs/build/guides/conventions/README.mdx b/docs/build/guides/conventions/README.mdx
deleted file mode 100644
index f68ebb8a2..000000000
--- a/docs/build/guides/conventions/README.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: Contract Conventions
-hide_table_of_contents: true
-sidebar_position: 10
----
-
-These guides describe the "typical" way something might be accomplished in a Rust contract. These guides aren't meant to be quite as _prescriptive_ as some others; instead, they serve to highlight some of the norms we've seen when crop up in contract development.
diff --git a/docs/build/guides/conventions/cross-contract.mdx b/docs/build/guides/conventions/cross-contract.mdx
index 94b56cefc..a009c77e2 100644
--- a/docs/build/guides/conventions/cross-contract.mdx
+++ b/docs/build/guides/conventions/cross-contract.mdx
@@ -7,20 +7,22 @@ As with developing software in any language, developing a Stellar smart contract
 
 There are two kinds of dependencies that can be introduced in a Stellar smart contract:
 
-1. Other Rust crates can be used (provided that they are compatible with Soroban's [Rust dialect](../../../learn/fundamentals/contract-development/rust-dialect.mdx));
-2. Other smart contract can be used. This is referred to as a [cross-contract call](../../../learn/fundamentals/contract-development/contract-interactions/cross-contract.mdx).
+1. Other Rust crates can be used (provided that they are compatible with Soroban's [Rust dialect](../../../learn/fundamentals/contract-development/rust-dialect));
+2. Other smart contract can be used. This is referred to as a [cross-contract call](../../../learn/fundamentals/contract-development/contract-interactions/cross-contract).
 
 In the following, we will see how contracts can be leveraged from within another contract.
 
 ## Contract as a dependency
 
-While finding a contract is out of scope for this guide, there are a few places to be on the lookout. Most projects and dApps publicly disclose the address of their Stellar smart contract on their website. With this information, a [block explorer](../../../tools/developer-tools/block-explorers.mdx) is a powerful tool to understand how a contract is being used. Some explorers also allow you to download the compiled contract as a Wasm file. There are also projects that provide a link to access the code itself.
+While finding a contract is out of scope for this guide, there are a few places to be on the lookout. Most projects and dApps publicly disclose the address of their Stellar smart contract on their website. With this information, a [block explorer](../../../tools/developer-tools/block-explorers) is a powerful tool to understand how a contract is being used. Some explorers also allow you to download the compiled contract as a Wasm file. There are also projects that provide a link to access the code itself.
 
-:::info[Contract address]
+<Info>
+
+**Contract address**
 
 To depend on a project, we need to know the contract address of the contract to depend on.
 
-:::
+</Info>
 
 ## Public API
 
@@ -73,7 +75,9 @@ impl ContractB {
 
 Although we have access to the Wasm, we still need a contract address because there could be multiple contracts deployed on-chain that use the same underlying code. This can be of importance if, for instance, the function that you need requires access to stored values from other users.
 
-:::tip[Address and Wasm]
+<Tip>
+
+**Address and Wasm**
 
 Thanks to the Rust bindings of the external contract, we can also use any public enum of the contract as if we would have defined them within our own contract.
 
@@ -81,7 +85,7 @@ Thanks to the Rust bindings of the external contract, we can also use any public
 client::ContractAEnum::SomeField
 ```
 
-:::
+</Tip>
 
 ## Handling responses
 
@@ -107,11 +111,13 @@ match client.try_add(&x, &y) {
 }
 ```
 
-:::caution[Some errors cannot be caught]
+<Warning>
 
-`try_` does not catch every error. A resource limit error, a footprint violation, or an internal host error still traps the contract, and the transaction fails. See [Recoverable and Non-Recoverable Errors](../../../learn/fundamentals/contract-development/contract-interactions/overview.mdx#recoverable-and-non-recoverable-errors).
+**Some errors cannot be caught**
 
-:::
+`try_` does not catch every error. A resource limit error, a footprint violation, or an internal host error still traps the contract, and the transaction fails. See [Recoverable and Non-Recoverable Errors](../../../learn/fundamentals/contract-development/contract-interactions/overview#recoverable-and-non-recoverable-errors).
+
+</Warning>
 
 ## Depending on another contract
 
@@ -119,15 +125,17 @@ Congratulations, now you can effectively leverage the whole Soroban ecosystem an
 
 As with calling any smart contract, depending on an external smart contract should be done with care. It is advisable to do your own research and analysis on the contract you want to use. As contracts can be updated without their address changing, it is important to pay close attention to any changes in the underlying code.
 
-:::tip[Contract Wasm]
+<Tip>
+
+**Contract Wasm**
 
-The Wasm can be fetched by using the [Stellar CLI](../../../tools/cli/README.mdx). This can serve as a quick way to (for example) automate a hash check in a continuous integration system. However, such a check would not provide strong on-chain guarantees, but one could build a contract for that!
+The Wasm can be fetched by using the [Stellar CLI](/docs/tools/cli). This can serve as a quick way to (for example) automate a hash check in a continuous integration system. However, such a check would not provide strong on-chain guarantees, but one could build a contract for that!
 
 ```bash
 stellar contract fetch --id C... --network ... > contract.wasm
 ```
 
-:::
+</Tip>
 
 Besides this security consideration, upgrading a contract is an integral part of a contract's lifecycle. New features are added, bugs are fixed, and public API changes are made. Here as well, it is important to observe any development on these contracts to ensure the continuous operation of your own contract.
 
@@ -135,4 +143,4 @@ Besides this security consideration, upgrading a contract is an integral part of
 
 See the following full example with tests:
 
-- [Cross-contract calls](../../smart-contracts/example-contracts/cross-contract-call.mdx) shows how to create two contracts, deploy them, and then how to call one from the other.
+- [Cross-contract calls](../../smart-contracts/example-contracts/cross-contract-call) shows how to create two contracts, deploy them, and then how to call one from the other.
diff --git a/docs/build/guides/conventions/deploy-contract.mdx b/docs/build/guides/conventions/deploy-contract.mdx
index f5ae2a18c..80a2f537e 100644
--- a/docs/build/guides/conventions/deploy-contract.mdx
+++ b/docs/build/guides/conventions/deploy-contract.mdx
@@ -1,23 +1,10 @@
 ---
 title: Deploy a contract from installed Wasm bytecode using a deployer contract
+og:title: "Deploy a contract from installed Wasm bytecode using a deployer contract"
+og:description: "Deploy a contract from installed Wasm bytecode using a deployer contract"
 description: Deploy a contract from installed Wasm bytecode using a deployer contract
 ---
 
-<head>
-  <title>
-    {`Deploy a contract from installed Wasm bytecode using a deployer contract`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Deploy a contract from installed Wasm bytecode using a deployer contract"
-  />
-  <meta
-    property="og:description"
-    content="Deploy a contract from installed Wasm bytecode using a deployer contract"
-  />
-</head>
-
 ## Overview
 
 This guide walks through the process of deploying a smart contract from installed Wasm bytecode using a deployer contract. We will cover setting up your environment, uploading Wasm bytecode, and deploying and initializing a contract atomically.
@@ -25,8 +12,8 @@ This guide walks through the process of deploying a smart contract from installe
 ### Prerequisites:
 
 - Basic understanding of [Rust programming language](https://www.rust-lang.org). To brush up on Rust, check out [Rustlings](https://github.com/rust-lang/rustlings) or [The Rust book](https://doc.rust-lang.org/book).
-- Familiarity with [Stellar smart contracts](../../smart-contracts/getting-started/hello-world.mdx)
-- Installed Cargo, [Stellar CLI](../../smart-contracts/getting-started/setup.mdx#install-the-stellar-cli) and Soroban SDK
+- Familiarity with [Stellar smart contracts](../../smart-contracts/getting-started/hello-world)
+- Installed Cargo, [Stellar CLI](../../smart-contracts/getting-started/setup#install-the-stellar-cli) and Soroban SDK
 
 ### Setup environment
 
@@ -44,11 +31,11 @@ git clone -b main https://github.com/stellar/soroban-examples
 cd soroban-examples/deployer/deployer
 ```
 
-:::note
+<Note>
 
 For this example to work, you should navigate to `deployer/contract` and `deployer/deployer` and run the command `stellar contract build` in each directory to generate the target files.
 
-:::
+</Note>
 
 3. Run tests:
 
@@ -178,7 +165,7 @@ stellar contract upload \
 
 When deploying a smart contract to the network, you must specify an identity that will be used to sign the transactions. Change the `alice` [identity] to your own.
 
-[identity]: ../../smart-contracts/getting-started/setup.mdx#configure-an-identity
+[identity]: ../../smart-contracts/getting-started/setup#configure-an-identity
 
 The command prints out the hash as hex. It will look something like `6bc6d975ef99c057231481c40f69f4c2a8a89ac56e8826ef0378f8e5c6abc4be`.
 
diff --git a/docs/build/guides/conventions/deploy-sac-with-code.mdx b/docs/build/guides/conventions/deploy-sac-with-code.mdx
index c3d58f3fa..5130adc58 100644
--- a/docs/build/guides/conventions/deploy-sac-with-code.mdx
+++ b/docs/build/guides/conventions/deploy-sac-with-code.mdx
@@ -1,33 +1,20 @@
 ---
 title: Deploy a SAC for a Stellar asset using code
+og:title: "Deploy a Stellar Asset Contract (SAC) for a Stellar asset using code"
+og:description: "This is a step-by-step guide to help you deploy a SAC for a Stellar asset using the Stellar SDK."
 description: Deploy a SAC for a Stellar asset using Javascript SDK
 ---
 
-<head>
-  <title>
-    {`Deploy a Stellar Asset Contract (SAC) for a Stellar asset using code`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Deploy a Stellar Asset Contract (SAC) for a Stellar asset using code"
-  />
-  <meta
-    property="og:description"
-    content="This is a step-by-step guide to help you deploy a SAC for a Stellar asset using the Stellar SDK."
-  />
-</head>
-
 ## Overview
 
-In this guide, you'll learn how to deploy a [Stellar Asset Contract (SAC)](../../../tokens/stellar-asset-contract.mdx) for a Stellar asset using the [Stellar SDK](../../../tools/sdks/client-sdks.mdx#javascript-sdk). The Stellar SDK is a set of tools and libraries designed to help developers build applications that interact with the Stellar blockchain network.
+In this guide, you'll learn how to deploy a [Stellar Asset Contract (SAC)](../../../tokens/stellar-asset-contract) for a Stellar asset using the [Stellar SDK](../../../tools/sdks/client-sdks#javascript-sdk). The Stellar SDK is a set of tools and libraries designed to help developers build applications that interact with the Stellar blockchain network.
 
 ### Prerequisites:
 
 - [Node.js ](https://nodejs.org/en) and npm installed.
 - Stellar SDK for [JavaScript](https://www.npmjs.com/package/@stellar/stellar-sdk) installed
-- [Knowledge about Issuing an Asset on Stellar](../../../tokens/how-to-issue-an-asset.mdx)
-- An understanding of the rudimentary, retry-enabled transaction polling function `submitTx` which we outlined in [another guide](../transactions/submit-transaction-wait-js.mdx)
+- [Knowledge about Issuing an Asset on Stellar](../../../tokens/how-to-issue-an-asset)
+- An understanding of the rudimentary, retry-enabled transaction polling function `submitTx` which we outlined in [another guide](../transactions/submit-transaction-wait-js)
 
 ## Code overview
 
diff --git a/docs/build/guides/conventions/error-enum.mdx b/docs/build/guides/conventions/error-enum.mdx
index e93d4784e..75811f993 100644
--- a/docs/build/guides/conventions/error-enum.mdx
+++ b/docs/build/guides/conventions/error-enum.mdx
@@ -1,6 +1,5 @@
 ---
 title: Organize contract errors with an error enum type
-hide_table_of_contents: true
 description: Manage and communicate contract errors using an enum struct
 ---
 
diff --git a/docs/build/guides/conventions/extending-wasm-ttl.mdx b/docs/build/guides/conventions/extending-wasm-ttl.mdx
index 63a69554d..0f5ec1134 100644
--- a/docs/build/guides/conventions/extending-wasm-ttl.mdx
+++ b/docs/build/guides/conventions/extending-wasm-ttl.mdx
@@ -1,14 +1,11 @@
 ---
-title: Extend a deployed contract's TTL with code
+title: "Extending a deployed contract's TTL using code"
+sidebarTitle: "Extend a deployed contract's TTL with code"
+"og:title": "Extend a deployed contract's TTL with code"
 description: How to extend the TTL of a deployed contract's Wasm code
 ---
 
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-# Extending a deployed contract's TTL using code
-
-When a smart contract is deployed on the Stellar network, two ledger entries are created. A contract instance ledger entry is created that defines the contract address, which WebAssembly (WASM) code it uses, and any additional storage the contract utilizes. The WebAssembly (WASM) code also has its own ledger entry that can be shared by multiple contract instances. Each ledger entry has a [Time To Live (TTL)](../../../learn/fundamentals/contract-development/storage/state-archival.mdx#ttl) that determines how long it remains accessible.
+When a smart contract is deployed on the Stellar network, two ledger entries are created. A contract instance ledger entry is created that defines the contract address, which WebAssembly (WASM) code it uses, and any additional storage the contract utilizes. The WebAssembly (WASM) code also has its own ledger entry that can be shared by multiple contract instances. Each ledger entry has a [Time To Live (TTL)](../../../learn/fundamentals/contract-development/storage/state-archival#ttl) that determines how long it remains accessible.
 
 The TTL is the number of ledgers between the current ledger and the final ledger for which the data can still be accessed. If the TTL expires, the data becomes archived and inaccessible. To prevent this, you need to periodically extend the TTL of the contract's Wasm code and instance entry.
 
@@ -25,8 +22,8 @@ Before we demonstrate the TTL extension methods, you should note that in Soroban
 ## Prerequisites
 
 - Stellar SDK: `npm install @stellar/stellar-sdk` for Javascript
-- Install the [Stellar CLI](../../../tools/cli/install-cli.mdx)
-- A [Stellar RPC](../../../data/apis/rpc/README.mdx) endpoint (e.g., `https://soroban-testnet.stellar.org`)
+- Install the [Stellar CLI](../../../tools/cli/install-cli)
+- A [Stellar RPC](/docs/data/apis/rpc) endpoint (e.g., `https://soroban-testnet.stellar.org`)
 - Basic knowledge of the SDK in use
 
 ## Extending Contract Code and Instance TTL with a Contract
@@ -82,14 +79,13 @@ impl ExtendTTLContract {
   - Simulate to determine the resource fee needed to extend the TTL
   - Sign and submit the transaction
 
-:::note
+<Note>
 
 A resource fee and inclusion fee are both charged in this transaction.
 
-:::
-
-<Tabs groupId="language" defaultValue="CLI">
-<TabItem value="CLI" label="CLI">
+</Note>
+<Tabs>
+<Tab title="CLI">
 
 The CLI has separate commands to extend contract code and contract instance ledger entries. The `--ledgers-to-extend` argument is the new entries TTL value.
 
@@ -113,10 +109,10 @@ stellar contract extend \
   --id CC77VMQFKNXIKZQ6LMX56FTH2S2NLAF2FDZIHITSM3UKW24Z75UZ4YW2
 ```
 
-</TabItem>
-<TabItem value="js" label="JS">
+</Tab>
+<Tab title="JS">
 
-The code below uses Nodejs environment but same concept can also be applied in the browser using Freighter wallet or using any other [Stellar SDK](../../../tools/sdks/client-sdks.mdx).
+The code below uses Nodejs environment but same concept can also be applied in the browser using Freighter wallet or using any other [Stellar SDK](../../../tools/sdks/client-sdks).
 
 ```javascript
 import * as StellarSdk from "@stellar/stellar-sdk";
@@ -203,9 +199,9 @@ Why `setReadOnly()`? A few reasons:
 
 This is super important for contracts that need to stick around for a while. Without extending the TTL, the contract's data could expire and disappear from the ledger.
 
-</TabItem>
+</Tab>
 </Tabs>
 
-Learn how to test the TTL extension in this [guide](../archival/test-ttl-extension.mdx).
+Learn how to test the TTL extension in this [guide](../archival/test-ttl-extension).
 
-Want to dive deeper? Check out the docs on the [Extend Footprint TTL operation](../../../learn/fundamentals/contract-development/storage/state-archival.mdx#extendfootprintttlop).
+Want to dive deeper? Check out the docs on the [Extend Footprint TTL operation](../../../learn/fundamentals/contract-development/storage/state-archival#extendfootprintttlop).
diff --git a/docs/build/guides/conventions/index.mdx b/docs/build/guides/conventions/index.mdx
new file mode 100644
index 000000000..33b57c3bb
--- /dev/null
+++ b/docs/build/guides/conventions/index.mdx
@@ -0,0 +1,4 @@
+---
+title: Contract Conventions
+description: 'These guides describe the "typical" way something might be accomplished in a Rust contract. These guides aren''t meant to be quite as prescriptive as some others; instead, they serve to highlight some of the norms we''ve seen when crop up in contract development.'
+---
diff --git a/docs/build/guides/conventions/upgrading-contracts.mdx b/docs/build/guides/conventions/upgrading-contracts.mdx
index 49060d0a2..fb5b6fb76 100644
--- a/docs/build/guides/conventions/upgrading-contracts.mdx
+++ b/docs/build/guides/conventions/upgrading-contracts.mdx
@@ -1,21 +1,10 @@
 ---
 title: Upgrading Wasm bytecode for a deployed contract
+og:title: "Upgrading Wasm Bytecode for a Deployed Contract"
+og:description: "Upgrading Wasm Bytecode for a Deployed Contract"
 description: Upgrade Wasm bytecode for a deployed contract
 ---
 
-<head>
-  <title>Upgrading Wasm Bytecode for a Deployed Contract</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Upgrading Wasm Bytecode for a Deployed Contract"
-  />
-  <meta
-    property="og:description"
-    content="Upgrading Wasm Bytecode for a Deployed Contract"
-  />
-</head>
-
 ## Introduction
 
 Upgrading a smart contract allows you to improve or modify your contract without changing its address. This guide will walk you through the process of upgrading a WebAssembly (Wasm) bytecode contract using the Soroban SDK.
@@ -23,8 +12,8 @@ Upgrading a smart contract allows you to improve or modify your contract without
 ### Prerequisites:
 
 - Basic understanding of the [Rust programming language]. To brush up on Rust, check out [Rustlings](https://github.com/rust-lang/rustlings) or [The Rust book](https://doc.rust-lang.org/book).
-- Familiarity with [Stellar smart contracts](../../smart-contracts/getting-started/hello-world.mdx)
-- Installed [Stellar CLI](../../smart-contracts/getting-started/setup.mdx#install-the-stellar-cli) and Soroban SDK
+- Familiarity with [Stellar smart contracts](../../smart-contracts/getting-started/hello-world)
+- Installed [Stellar CLI](../../smart-contracts/getting-started/setup#install-the-stellar-cli) and Soroban SDK
 
 ### Download the upgradeable contract example
 
@@ -110,7 +99,7 @@ When upgrading a contract, the key function used is `env.deployer().update_curre
 
 5. `update_current_contract` will also emit a `SYSTEM` contract [event] that contains the old and new `ContractExecutable`, allowing downstream users to be notified when a contract they use is updated. The event structure will have `topics = ["executable_update", old_executable: ContractExecutable, new_executable: ContractExecutable]` and `data = []`.
 
-[event]: ../../../learn/fundamentals/stellar-data-structures/events.mdx#event-types
+[event]: ../../../learn/fundamentals/stellar-data-structures/events#event-types
 
 ## Tests
 
@@ -301,5 +290,5 @@ stellar contract invoke \
 
 Hooray, our contract has been upgraded!
 
-[`stellar-cli`]: ../../smart-contracts/getting-started/setup.mdx#install-the-stellar-cli
-[identities]: ../../smart-contracts/getting-started/setup.mdx#configure-an-identity
+[`stellar-cli`]: ../../smart-contracts/getting-started/setup#install-the-stellar-cli
+[identities]: ../../smart-contracts/getting-started/setup#configure-an-identity
diff --git a/docs/build/guides/conventions/wasm-metadata.mdx b/docs/build/guides/conventions/wasm-metadata.mdx
index 43d84c0f5..a35314d03 100644
--- a/docs/build/guides/conventions/wasm-metadata.mdx
+++ b/docs/build/guides/conventions/wasm-metadata.mdx
@@ -1,19 +1,10 @@
 ---
 title: Write metadata for your contract
-hide_table_of_contents: true
+og:title: "Write metadata for your contract."
+og:description: "Use a macro provided in the Rust SDK to write structured metadata and use the tools available to read and display this information to users."
 description: Use the contractmeta! macro in Rust SDK to write metadata in Wasm contracts
 ---
 
-<head>
-  <title>Write structured metadata.</title>
-  <meta charSet="utf-8" />
-  <meta property="og:title" content="Write metadata for your contract." />
-  <meta
-    property="og:description"
-    content="Use a macro provided in the Rust SDK to write structured metadata and use the tools available to read and display this information to users."
-  />
-</head>
-
 The [`contractmeta!`] macro provided in the Rust SDK allows users to write two strings - a `key` and a `val` - within a serialized `SCMetaEntry::SCMetaV0` XDR object to the custom section of Wasm contracts. The section name for this metadata is `contractmetav0`. Developers can utilize this macro to write metadata, and tools can then read and display this information to users.
 
 The [liquidity pool example] provides a clear demonstration of how to use the `contractmeta!` macro:
diff --git a/docs/build/guides/conventions/work-contractspec-js.mdx b/docs/build/guides/conventions/work-contractspec-js.mdx
index 0a2059a43..8fd66b062 100644
--- a/docs/build/guides/conventions/work-contractspec-js.mdx
+++ b/docs/build/guides/conventions/work-contractspec-js.mdx
@@ -1,6 +1,6 @@
 ---
 title: Work with ContractSpecs in JavaScript
-hide_table_of_contents: true
+description: "You do something."
 draft: true
 ---
 
diff --git a/docs/build/guides/conventions/workspace.mdx b/docs/build/guides/conventions/workspace.mdx
index aa08d49fd..d42cb9ed0 100644
--- a/docs/build/guides/conventions/workspace.mdx
+++ b/docs/build/guides/conventions/workspace.mdx
@@ -1,11 +1,10 @@
 ---
-title: Workspaces
-hide_table_of_contents: true
+title: Workspace
+sidebarTitle: Workspaces
+"og:title": Workspaces
 description: Organize contracts using Cargo workspaces
 ---
 
-# Workspace
-
 Using Cargo's workspace [feature](https://doc.rust-lang.org/book/ch14-03-cargo-workspaces.html) makes it very convenient to organize your smart contracts in subdirectories of your project's root.
 
 It's very simple to get started using the cli:
@@ -73,11 +72,11 @@ impl ContractAdd {
 }
 ```
 
-:::tip
+<Tip>
 
-In this tutorial we use workspaces to import contract client. However, it's also possible to use contract's compiled code instead (for example, if you don't have a source code for it). See [making cross-contract calls](./cross-contract.mdx) guide for more info
+In this tutorial we use workspaces to import contract client. However, it's also possible to use contract's compiled code instead (for example, if you don't have a source code for it). See [making cross-contract calls](./cross-contract) guide for more info
 
-:::
+</Tip>
 
 Next, in order to call `ContractAdd` from another contract, it's necessary to add a workspace dependency:
 
diff --git a/docs/build/guides/conversions/README.mdx b/docs/build/guides/conversions/README.mdx
deleted file mode 100644
index af2a8b76f..000000000
--- a/docs/build/guides/conversions/README.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: Type Conversions
-hide_table_of_contents: true
-sidebar_position: 130
----
-
-A collection of guides for converting from one data type to another in a variety of SDK languages.
diff --git a/docs/build/guides/conversions/address-conversions.mdx b/docs/build/guides/conversions/address-conversions.mdx
index 479f1a8b3..d626519be 100644
--- a/docs/build/guides/conversions/address-conversions.mdx
+++ b/docs/build/guides/conversions/address-conversions.mdx
@@ -1,10 +1,9 @@
 ---
 title: Convert an address to other types
-hide_table_of_contents: true
 description: Convert an address to other types
 ---
 
-The `Address` is an opaque type that represents either a 'default' externally owned account on the Stellar network, or a contract (that may also provide logic for custom externally owned accounts, see [authorization docs](../../../learn/fundamentals/contract-development/authorization.mdx#account-abstraction) for details). For the smart contracts it normally doesn't matter which kind of `Address` is used. However, in some contexts it's useful to convert `Address` to/from different data types, such as string or XDR. The conversions have distinctly different purpose depending on whether they happen in the smart contract itself, or in the client code.
+The `Address` is an opaque type that represents either a 'default' externally owned account on the Stellar network, or a contract (that may also provide logic for custom externally owned accounts, see [authorization docs](../../../learn/fundamentals/contract-development/authorization#account-abstraction) for details). For the smart contracts it normally doesn't matter which kind of `Address` is used. However, in some contexts it's useful to convert `Address` to/from different data types, such as string or XDR. The conversions have distinctly different purpose depending on whether they happen in the smart contract itself, or in the client code.
 
 ## String conversions
 
@@ -14,9 +13,9 @@ The default string format for `Address` is a so called 'string key' (or 'strkey'
 
 Outside of the smart contracts, it is convenient to represent `Address` as string most of the time. It can be stored in string serialization formats such as JSON and XML. Storing addresses as strings in databases can simplify database schema design and queries. Strings are easier to manipulate and are more compatible with user interfaces and APIs. Thus
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 const StellarSdk = require("@stellar/stellar-sdk");
 
 // Example Stellar address
@@ -28,7 +27,7 @@ const address = new StellarSdk.Address(stellarAddress);
 const addressToString = address.toString();
 ```
 
-```python
+```python Python
 from stellar_sdk import Address
 
 # Example Stellar address
@@ -39,7 +38,7 @@ address = Address(stellar_address)
 address_to_string = address.address
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### String Conversions in Smart Contracts
 
@@ -74,9 +73,9 @@ XDR is schema-based binary serialization format used by the Stellar network. It
 
 On the client side XDR conversions are useful to build the transactions and process the transaction results.
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 // Example Stellar address
 const stellarAddress =
   "GCM5WPR4DDR24FSAX5LIEM4J7AI3KOWJYANSXEPKYXCSZOTAYXE75AFN";
@@ -90,7 +89,7 @@ const scValBuffer = scVal.toXDR("raw");
 const scAddress = address.toScAddress();
 ```
 
-```python
+```python Python
 from stellar_sdk import Address
 
 # Example Stellar address
@@ -101,7 +100,7 @@ address = Address(stellar_address)
 sc_address_xdr = address.to_xdr_sc_address()
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### XDR Conversions in Smart Contracts
 
diff --git a/docs/build/guides/conversions/address-to-bytesn.mdx b/docs/build/guides/conversions/address-to-bytesn.mdx
index f47528cbd..79a570154 100644
--- a/docs/build/guides/conversions/address-to-bytesn.mdx
+++ b/docs/build/guides/conversions/address-to-bytesn.mdx
@@ -1,6 +1,5 @@
 ---
 title: Convert an address to BytesN using the Rust SDK
-hide_table_of_contents: true
 description: Convert an address to BytesN using the Rust SDK
 draft: true
 ---
diff --git a/docs/build/guides/conversions/address-to-id.mdx b/docs/build/guides/conversions/address-to-id.mdx
index 8fa983277..d276151e4 100644
--- a/docs/build/guides/conversions/address-to-id.mdx
+++ b/docs/build/guides/conversions/address-to-id.mdx
@@ -1,6 +1,6 @@
 ---
 title: Convert a contract address to a contract ID in Rust
-hide_table_of_contents: true
+description: "C..."
 draft: true
 ---
 
diff --git a/docs/build/guides/conversions/bytes-conversions.mdx b/docs/build/guides/conversions/bytes-conversions.mdx
index b23cf3918..276bf1012 100644
--- a/docs/build/guides/conversions/bytes-conversions.mdx
+++ b/docs/build/guides/conversions/bytes-conversions.mdx
@@ -1,6 +1,5 @@
 ---
 title: Convert from bytes to other types
-hide_table_of_contents: true
 description: Convert from bytes to other types
 ---
 
@@ -10,9 +9,9 @@ Bytes is a contiguous growable array type containing u8s. They may represent var
 
 When retrieving data stored on the blockchain, addresses might be stored in byte representation for compactness and efficiency. Off-chain systems, such as APIs, databases, or user interfaces, usually expect addresses in a human-readable format. In such cases, you need to convert the bytes to an address format to ensure compatibility.
 
-<CodeExample>
+<CodeGroup>
 
-```rust
+```rust Rust
 use soroban_sdk::{Address, Bytes};
 
 pub fn bytes_to_address(bytes: Bytes) -> Address {
@@ -20,7 +19,7 @@ pub fn bytes_to_address(bytes: Bytes) -> Address {
 }
 ```
 
-```js
+```js JavaScript
 const StellarSdk = require("@stellar/stellar-sdk");
 
 // Example bytes value
@@ -36,7 +35,7 @@ const addressFromBytes = StellarSdk.Address.contract(rawBytes);
 addressFromBytes.toString();
 ```
 
-```python
+```python Python
 from stellar_sdk.address import Address
 
 # Example bytes value
@@ -44,15 +43,15 @@ raw_bytes = bytes.fromhex("99db3e3c18e3ae1640bf56823389f811b53ac9c01b2b91eac5c52
 bytes_to_address = Address.from_raw_account(raw_bytes)
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## Bytes to String
 
 When dealing with binary data, you may need to convert certain portions of the data to a human-readable format like strings for logging, debugging, processing or display.
 
-<CodeExample>
+<CodeGroup>
 
-```rust
+```rust Rust
 use soroban_sdk::{String, Bytes};
 
 pub fn bytes_to_string(bytes: Bytes) -> String {
@@ -60,7 +59,7 @@ pub fn bytes_to_string(bytes: Bytes) -> String {
 }
 ```
 
-```js
+```js JavaScript
 // Example bytes value
 const rawBytes = Buffer.from(
   "99db3e3c18e3ae1640bf56823389f811b53ac9c01b2b91eac5c52cba60c5c9fe",
@@ -70,22 +69,22 @@ const rawBytes = Buffer.from(
 const bytesToString = rawBytes.toString("hex");
 ```
 
-```python
+```python Python
 # Example bytes value
 raw_bytes = bytes.fromhex("99db3e3c18e3ae1640bf56823389f811b53ac9c01b2b91eac5c52cba60c5c9fe")
 # Convert bytes to string
 bytes_to_string = raw_bytes.hex()
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## Bytes to ScVal
 
 In a Soroban smart contract that interacts with an external oracle service to provide price data in raw byte format, you would need to convert the bytes to ScVal to process and manipulate the data within your contract.
 
-<CodeExample>
+<CodeGroup>
 
-```rust
+```rust Rust
 use soroban_sdk::{Bytes, Val};
 
 pub fn bytes_to_val(bytes: Bytes) -> Val {
@@ -93,7 +92,7 @@ pub fn bytes_to_val(bytes: Bytes) -> Val {
 }
 ```
 
-```js
+```js JavaScript
 // Example bytes value
 const rawBytes = Buffer.from(
   "99db3e3c18e3ae1640bf56823389f811b53ac9c01b2b91eac5c52cba60c5c9fe",
@@ -103,22 +102,22 @@ const rawBytes = Buffer.from(
 const bytesToScVal = StellarSdk.nativeToScVal(rawBytes);
 ```
 
-```python
+```python Python
 # Example bytes value
 raw_bytes = bytes.fromhex("99db3e3c18e3ae1640bf56823389f811b53ac9c01b2b91eac5c52cba60c5c9fe")
 # Convert bytes to ScVal
 sc_val = stellar_sdk.scval.to_bytes(raw_bytes)
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## BytesN to Fixed-Size Array
 
 `BytesN<N>` is a fixed-length byte buffer used for values like hashes and public keys. It can be converted to a native Rust `[u8; N]` array using the `to_array()` method or the standard `Into` trait.
 
-<CodeExample>
+<CodeGroup>
 
-```rust
+```rust Rust
 use soroban_sdk::BytesN;
 
 // Convert by value using to_array()
@@ -137,4 +136,4 @@ pub fn bytesn_ref_to_array(b: &BytesN<32>) -> [u8; 32] {
 }
 ```
 
-</CodeExample>
+</CodeGroup>
diff --git a/docs/build/guides/conversions/id-to-address.mdx b/docs/build/guides/conversions/id-to-address.mdx
index a8b9734d2..af4e0f513 100644
--- a/docs/build/guides/conversions/id-to-address.mdx
+++ b/docs/build/guides/conversions/id-to-address.mdx
@@ -1,6 +1,5 @@
 ---
 title: Convert a contract ID to a contract address
-hide_table_of_contents: true
 description: Convert a contract ID to a contract address
 draft: true
 ---
diff --git a/docs/build/guides/conversions/index.mdx b/docs/build/guides/conversions/index.mdx
new file mode 100644
index 000000000..179fe59df
--- /dev/null
+++ b/docs/build/guides/conversions/index.mdx
@@ -0,0 +1,4 @@
+---
+title: Type Conversions
+description: "A collection of guides for converting from one data type to another in a variety of SDK languages."
+---
diff --git a/docs/build/guides/conversions/scval-conversions.mdx b/docs/build/guides/conversions/scval-conversions.mdx
index 5212df1ba..d2c75cf9f 100644
--- a/docs/build/guides/conversions/scval-conversions.mdx
+++ b/docs/build/guides/conversions/scval-conversions.mdx
@@ -1,6 +1,5 @@
 ---
 title: Convert a ScVal to other type
-hide_table_of_contents: true
 description: Convert a ScVal to other type
 ---
 
@@ -8,27 +7,27 @@ Soroban Contract Value (`ScVal`) is a custom type defined within the Soroban run
 
 ## ScVal to bytes
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 // An ScVal bytes value
 const myScVal = StellarSdk.xdr.ScVal.fromXDR("AAAADQAAAARQ/8AB", "base64");
 // Convert the ScVal to a Buffer
 const bytesFromScVal = StellarSdk.scValToNative(myScVal);
 ```
 
-```python
+```python Python
 # Convert the ScVal to bytes
 bytes_from_sc_val = stellar_sdk.scval.from_bytes("AAAADQAAAARQ/8AB")
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## ScVal to address
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 // An ScVal Address value
 const myScVal = StellarSdk.xdr.ScVal.fromXDR(
   "AAAAEgAAAAAAAAAAmds+PBjjrhZAv1aCM4n4EbU6ycAbK5HqxcUsumDFyf4=",
@@ -38,18 +37,18 @@ const myScVal = StellarSdk.xdr.ScVal.fromXDR(
 const addressFromScVal = StellarSdk.Address.fromScVal(myScVal);
 ```
 
-```python
+```python Python
 # Convert the ScVal to address
 address_from_sc_val = stellar_sdk.scval.from_address("AAAAEgAAAAAAAAAAmds+PBjjrhZAv1aCM4n4EbU6ycAbK5HqxcUsumDFyf4=")
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## ScVal to String
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 // An ScVal string value
 const myScVal = StellarSdk.xdr.ScVal.fromXDR(
   "AAAADgAAAA9IZWxsbywgU3RlbGxhciEA",
@@ -59,9 +58,9 @@ const myScVal = StellarSdk.xdr.ScVal.fromXDR(
 const stringFromScVal = StellarSdk.scValToNative(myScVal);
 ```
 
-```python
+```python Python
 # Convert the ScVal to a string
 string_from_sc_val = stellar_sdk.scval.from_string("AAAADgAAAA9IZWxsbywgU3RlbGxhciEA").decode()
 ```
 
-</CodeExample>
+</CodeGroup>
diff --git a/docs/build/guides/conversions/string-conversions.mdx b/docs/build/guides/conversions/string-conversions.mdx
index 45f00e2fe..a14cd05aa 100644
--- a/docs/build/guides/conversions/string-conversions.mdx
+++ b/docs/build/guides/conversions/string-conversions.mdx
@@ -1,6 +1,5 @@
 ---
 title: Convert a string to other types
-hide_table_of_contents: true
 description: Convert a string to other types
 ---
 
@@ -10,9 +9,9 @@ Strings are a sequence of characters used to represent readable text. They are u
 
 Some systems use binary formats where data needs to be represented as a fixed-length byte array for storage or processing. For example, fixed-length hashes or identifiers. Converting strings to a fixed byte size ensures that the data fits the required size constraints.
 
-<CodeExample>
+<CodeGroup>
 
-```rust
+```rust Rust
 use soroban_sdk::{Bytes, String};
 
 pub fn string_to_bytes(string: String) -> Bytes {
@@ -20,29 +19,29 @@ pub fn string_to_bytes(string: String) -> Bytes {
 }
 ```
 
-```js
+```js JavaScript
 // Example string
 const stringValue = "Hello, Stellar!";
 // Convert the string to bytes format
 const byteValue = Buffer.from(stringValue, "utf-8");
 ```
 
-```python
+```python Python
 # Example string
 string_value = "Hello, Stellar!"
 # Convert the string to bytes format
 string_value.encode()
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## String to address
 
 An address received in a user input may be of string type and you would need to convert it to an address type to perform validations, transactions, or other operations within your smart contract.
 
-<CodeExample>
+<CodeGroup>
 
-```rust
+```rust Rust
 use soroban_sdk::{Address, Env, String};
 
 pub fn string_to_address(string: String) -> Address {
@@ -50,7 +49,7 @@ pub fn string_to_address(string: String) -> Address {
 }
 ```
 
-```js
+```js JavaScript
 const StellarSdk = require("@stellar/stellar-sdk");
 
 // Example Stellar address
@@ -62,7 +61,7 @@ const address = new StellarSdk.Address(stellarAddress);
 const addressToString = address.toString();
 ```
 
-```python
+```python Python
 from stellar_sdk import Address
 
 # Example Stellar address
@@ -73,15 +72,15 @@ address = Address(stellar_address)
 address_to_string = address.address
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## String to ScVal
 
 When calling functions or methods that expect ScVal types, you need to convert your string data to ScVal to make the call successful. For example, if your smart contract needs to store or manipulate a user input string within its state or use it as part of its logic, you would convert the string to an ScVal type to integrate it with the contract's operations.
 
-<CodeExample>
+<CodeGroup>
 
-```rust
+```rust Rust
 use soroban_sdk::{String, Val};
 
 pub fn string_to_val(string: String) -> Val {
@@ -89,7 +88,7 @@ pub fn string_to_val(string: String) -> Val {
 }
 ```
 
-```js
+```js JavaScript
 import * as StellarSdk from "@stellar/stellar-sdk";
 
 // Example string value
@@ -98,7 +97,7 @@ const stringValue = "Hello, Stellar!";
 const stringToScVal = StellarSdk.xdr.ScVal.scvString(stringValue);
 ```
 
-```python
+```python Python
 import stellar_sdk
 
 # Example string value
@@ -107,4 +106,4 @@ string_value = "Hello, Stellar!"
 string_to_sc_val = stellar_sdk.scval.to_string(string_value)
 ```
 
-</CodeExample>
+</CodeGroup>
diff --git a/docs/build/guides/dapps/README.mdx b/docs/build/guides/dapps/README.mdx
deleted file mode 100644
index 50544b62b..000000000
--- a/docs/build/guides/dapps/README.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: Dapp Development
-hide_table_of_contents: true
-sidebar_position: 50
----
-
-We've written some helpful guides on some of the most useful tools available to you, the dapp developer.
diff --git a/docs/build/guides/dapps/frontend-guide.mdx b/docs/build/guides/dapps/frontend-guide.mdx
index db6e25f01..a72dc65dc 100644
--- a/docs/build/guides/dapps/frontend-guide.mdx
+++ b/docs/build/guides/dapps/frontend-guide.mdx
@@ -42,7 +42,7 @@ By focusing on these aspects, you can create Stellar dapps that are not only fun
 
 Before we start building our Stellar dapp, we need to set up our development environment. We'll be using React with Next.js for our frontend framework, Tailwind CSS for styling, and the Stellar SDK for interacting with the Stellar network.
 
-### Installing Node.js and npm
+### Installing Node.js and npm {#installing-nodejs-and-npm}
 
 First, make sure you have Node.js and npm (Node Package Manager) installed on your system. You can download and install them from the official Node.js website: https://nodejs.org/
 
@@ -55,7 +55,7 @@ npm --version
 
 Both commands should return version numbers if the installation was successful.
 
-### Setting up a Next.js project
+### Setting up a Next.js project {#setting-up-a-nextjs-project}
 
 Next.js is a React framework that provides features such as server-side rendering and routing out of the box. To create a new Next.js project, run the following commands in your terminal:
 
@@ -345,11 +345,11 @@ This setup provides a solid foundation for building the user interface of our St
 
 Before we start integrating smart contract functionality into our Stellar dapp, let's understand the basic concepts of Soroban contracts.
 
-Soroban is a smart contract platform built on the Stellar network. It allows developers to write and deploy smart contracts that run on the Stellar blockchain. Soroban contracts are written in Rust and compiled to [XDR (External Data Representation)](../../../learn/fundamentals/data-format/xdr.mdx) for execution on the Stellar network.
+Soroban is a smart contract platform built on the Stellar network. It allows developers to write and deploy smart contracts that run on the Stellar blockchain. Soroban contracts are written in Rust and compiled to [XDR (External Data Representation)](../../../learn/fundamentals/data-format/xdr) for execution on the Stellar network.
 
 ### Data Types
 
-Stellar supports a few data types that can be used in Soroban contracts and we need to do conversions from time to time between those types and the types we have in Javascript. The full list of primitive data types are explained [here](../../../learn/fundamentals/contract-development/types/built-in-types.mdx).
+Stellar supports a few data types that can be used in Soroban contracts and we need to do conversions from time to time between those types and the types we have in Javascript. The full list of primitive data types are explained [here](../../../learn/fundamentals/contract-development/types/built-in-types).
 
 ### XDR
 
@@ -365,7 +365,7 @@ Calculating these fees can be cumbersome but the Stellar SDK provides a way to c
 
 The ABI or spec is a json file that contains the contract's interface. It defines the functions that can be called on the contract, their parameters, and return types. The ABI is used by clients to interact with the contract and execute its functions. The ABI is generated from the contract's source code and is used to compile the contract into XDR for execution on the Stellar network.
 
-ABI can be genrated for a contract using the [`stellar contract bindings`](../../../tools/cli/stellar-cli.mdx#stellar-contract-bindings-json) command and can be used to interact with the contract.
+ABI can be genrated for a contract using the [`stellar contract bindings`](../../../tools/cli/stellar-cli#stellar-contract-bindings-json) command and can be used to interact with the contract.
 
 This ABI can also be generated as a typescript library to ease development in your DApp and we'll be looking it later in this guide
 
@@ -377,7 +377,7 @@ Now that we have our basic UI components in place, let's integrate them with the
 - Test network: This is a test environment for developers to test their applications without using real lumens.
 - Futurenet network: This is a network for testing new features before they are deployed to the public network.
 
-For this guide, we'll be using the Test network to avoid using real lumens during development. Read more about the [Stellar networks here](../../../networks/README.mdx).
+For this guide, we'll be using the Test network to avoid using real lumens during development. Read more about the [Stellar networks here](/docs/networks).
 
 ### Setting up the Stellar SDK
 
@@ -522,11 +522,11 @@ The `handleSendPayment` function now interacts with the Stellar network to send
 
 Notice how we imported the `isConnected`, `setAllowed`, `getAddress`, and `signTransaction` functions from the `@stellar/freighter-api` library. These functions are used to interact with the Freighter wallet extension and sign transactions securely.
 
-:::tip
+<Tip>
 
 Hurray! You have successfully integrated your Stellar dapp with the Stellar network. You can now send payments using the Freighter wallet extension on the Stellar Testnet.
 
-:::
+</Tip>
 
 ### Interacting with smart contracts
 
@@ -726,13 +726,13 @@ Notice how we used a different operation `contract.call("increment")` to interac
 
 After calling the transaction to increment successfully, we need to poll and then call another method `server.getTransaction` to get the transaction result. The transaction result contains the new counter value which we extract and display to the user.
 
-The value gotten from the transaction result is stored in a form called `scval` due to the limited [number of types](../../../learn/fundamentals/contract-development/types/built-in-types.mdx) that exist in soroban today. This value is transmitted about in the form of `xdr` which can be converted to an `scVal` using the sdk. The value is then parsed as `u32` which is a 32-bit unsigned integer. We will learn more about converting these types [in this collection of guides](../conversions/README.mdx).
+The value gotten from the transaction result is stored in a form called `scval` due to the limited [number of types](../../../learn/fundamentals/contract-development/types/built-in-types) that exist in soroban today. This value is transmitted about in the form of `xdr` which can be converted to an `scVal` using the sdk. The value is then parsed as `u32` which is a 32-bit unsigned integer. We will learn more about converting these types [in this collection of guides](/docs/build/guides/conversions).
 
-:::tip
+<Tip>
 
 Congratulations! You have successfully interacted with a smart contract on the Stellar network using your dapp.
 
-:::
+</Tip>
 
 ### Reading events from the Stellar network
 
@@ -744,7 +744,7 @@ This is made possible by using the `server.getEvents` method which allows you to
 
 We will be editing the `CounterPage` component to read events from the counter smart contract immediately the page loads to get the initial counter value and update instead of using "Unknown". Before we continue, please take a look at the [contract code](https://github.com/stellar/soroban-examples/blob/main/events/src/lib.rs). In the contract code, an event named `increment` is emitted whenever the `increment` function is called. It is published over 2 topics, `increment` and `COUNTER` and we need to listen to these topics to get the events.
 
-The topics are stored in a data type called `symbol` and we will need to convert both `increment` and `COUNTER` to `symbol` before we can use them in the [`server.getEvents`](../../../data/apis/rpc/api-reference/methods/getEvents.mdx) method. At maximum, stellar RPCs keep track of events for 7 days and you can query events that happened within the last 7 days, so if you need to store events for longer, you may need to make use of an [indexer](../../../data/indexers/README.mdx).
+The topics are stored in a data type called `symbol` and we will need to convert both `increment` and `COUNTER` to `symbol` before we can use them in the [`server.getEvents`](../../../data/apis/rpc/api-reference/methods/getEvents) method. At maximum, stellar RPCs keep track of events for 7 days and you can query events that happened within the last 7 days, so if you need to store events for longer, you may need to make use of an [indexer](/docs/data/indexers).
 
 To use events,we edit our counter page and add the following code:
 
@@ -803,21 +803,21 @@ The library generated contains helper methods for calling each contract and also
 
 To achieve this, you need to
 
-- Have the [Stellar CLI](../../../tools/cli/install-cli.mdx) installed.
+- Have the [Stellar CLI](../../../tools/cli/install-cli) installed.
 - Have either source code or deployed contract ID of the contract.
 - Know the network it was deployed to.
 
 #### Scenario 1: I have the Contract ID but no code
 
-In this scenario, we need to use the command [`stellar contract fetch`](../../../tools/cli/stellar-cli.mdx#stellar-contract-fetch) to fetch the wasm code of the contract
+In this scenario, we need to use the command [`stellar contract fetch`](../../../tools/cli/stellar-cli#stellar-contract-fetch) to fetch the wasm code of the contract
 
 #### Scenario 2: I have the code
 
-The next step here is to build it to a wasm file using the [`stellar contract build`](../../../tools/cli/stellar-cli.mdx#stellar-contract-build) command.
+The next step here is to build it to a wasm file using the [`stellar contract build`](../../../tools/cli/stellar-cli#stellar-contract-build) command.
 
 ### Generating the Library
 
-After getting the wasm, we can now run [`stellar contract bindings typescript`](../../../tools/cli/stellar-cli.mdx#stellar-contract-bindings-typescript) to generate the library which is ready to be published to NPM. The library generated is suited for working with complex contracts.
+After getting the wasm, we can now run [`stellar contract bindings typescript`](../../../tools/cli/stellar-cli#stellar-contract-bindings-typescript) to generate the library which is ready to be published to NPM. The library generated is suited for working with complex contracts.
 
 ## 7. Common Pitfalls
 
@@ -827,17 +827,17 @@ Below are a few common pitfalls that soroban DApp developers might run into
 
 The data types in Javascript are different from the data types in soroban. When working with soroban contracts, you need to be aware of the data types and how to convert them to the types you are familiar with in Javascript. The Stellar SDK provides helper methods for converting between XDR and Javascript types in the `xdr` namespace.
 
-### Fees
+### Fees {#fees-1}
 
-Calculating fees for transactions can be tricky. The Stellar SDK provides a way to calculate fees using the `server.prepareTransaction` method, which simulates the transaction and returns the appropriate fees. Fees are calculated in [stroops](../../../learn/glossary.mdx#stroop)
+Calculating fees for transactions can be tricky. The Stellar SDK provides a way to calculate fees using the `server.prepareTransaction` method, which simulates the transaction and returns the appropriate fees. Fees are calculated in [stroops](../../../learn/glossary#stroop)
 
 ### SendTransaction and GetTransaction
 
-Results from a smart contract execution or any of the [valid transactions](../../../learn/fundamentals/transactions/list-of-operations.mdx#extend-footprint-ttl) on soroban are not immediate. They are kept in a `PENDING` state until they are confirmed. You need to poll the `getTransaction` method to get the final result of the transaction.
+Results from a smart contract execution or any of the [valid transactions](../../../learn/fundamentals/transactions/list-of-operations#extend-footprint-ttl) on soroban are not immediate. They are kept in a `PENDING` state until they are confirmed. You need to poll the `getTransaction` method to get the final result of the transaction.
 
 ### State Archival
 
-State Archival is a characteristic of soroban contracts where some data stored on the ledger about the contract might be archived. These [guides](../archival/README.mdx) helps to understand how to work with state archival in DApps.
+State Archival is a characteristic of soroban contracts where some data stored on the ledger about the contract might be archived. These [guides](/docs/build/guides/archival) helps to understand how to work with state archival in DApps.
 
 ### Data Retention
 
diff --git a/docs/build/guides/dapps/index.mdx b/docs/build/guides/dapps/index.mdx
new file mode 100644
index 000000000..bca990c54
--- /dev/null
+++ b/docs/build/guides/dapps/index.mdx
@@ -0,0 +1,4 @@
+---
+title: Dapp Development
+description: "We've written some helpful guides on some of the most useful tools available to you, the dapp developer."
+---
diff --git a/docs/build/guides/dapps/react.mdx b/docs/build/guides/dapps/react.mdx
index 0b40c7aa5..553cc4c45 100644
--- a/docs/build/guides/dapps/react.mdx
+++ b/docs/build/guides/dapps/react.mdx
@@ -6,11 +6,11 @@ draft: true
 
 This section elaborates on how the frontends from your dapp can interact with the example contracts and access chain data, and connect to a freighter wallet. This will be illustrated by utilizing libraries provided by [`@soroban-react`](https://soroban-react.gitbook.io/index), a simple, powerful framework for building modern Dapps using React. `@soroban-react` was created and is maintained by an amazing member of the community!
 
-:::info
+<Info>
 
 This guide will demonstrate how an [example crowdfund dapp] frontend was developed with React. While much of the code is specific to this project, the principles demonstrated should be educational enough to get you started.
 
-:::
+</Info>
 
 Below is a list of the libraries used throughout the frontend code and their respective imports:
 
diff --git a/docs/build/guides/dapps/soroban-contract-init-template.mdx b/docs/build/guides/dapps/soroban-contract-init-template.mdx
index 4209076f2..8d50b8b85 100644
--- a/docs/build/guides/dapps/soroban-contract-init-template.mdx
+++ b/docs/build/guides/dapps/soroban-contract-init-template.mdx
@@ -1,22 +1,11 @@
 ---
 title: Develop contract with frontend templates
+og:title: "Develop contract with frontend templates"
+og:description: "Understand, find, and create your own frontend templates for use with Stellar CLI's `stellar contract init` command"
 description: Understand, find, and create your own frontend templates for use with Stellar CLI's `stellar contract init` command
 ---
 
-<head>
-  <title>Develop contract with frontend templates</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Develop contract with frontend templates"
-  />
-  <meta
-    property="og:description"
-    content="Understand, find, and create your own frontend templates for use with Stellar CLI's `stellar contract init` command"
-  />
-</head>
-
-This guide picks up where [Build a Dapp Frontend](../../apps/dapp-frontend.mdx) left off. From there, we'll:
+This guide picks up where [Build a Dapp Frontend](../../apps/dapp-frontend) left off. From there, we'll:
 
 1. Search GitHub for other Soroban templates
 1. Build our own simple template
@@ -25,7 +14,7 @@ Building our own template will be a great way to learn how they work. They're no
 
 ## Search GitHub for other Soroban templates
 
-The official template maintained by Stellar Development Foundation (SDF), as used in [Build a Dapp Frontend](../../apps/dapp-frontend.mdx), lives on GitHub at [stellar/soroban-template-astro](https://github.com/stellar/soroban-astro-template). It uses the [Astro](https://astro.build) web framework. While Astro works with React, Vue, Svelte, and any other UI library, the template opts not to use them, preferring Astro's own templating language, which uses vanilla JavaScript with no UI library.
+The official template maintained by Stellar Development Foundation (SDF), as used in [Build a Dapp Frontend](../../apps/dapp-frontend), lives on GitHub at [stellar/soroban-template-astro](https://github.com/stellar/soroban-astro-template). It uses the [Astro](https://astro.build) web framework. While Astro works with React, Vue, Svelte, and any other UI library, the template opts not to use them, preferring Astro's own templating language, which uses vanilla JavaScript with no UI library.
 
 (You may wonder why it makes this unpopular choice. A fair question! The team wanted to balance actual utility with broad approachability. Not everyone learning Stellar and Soroban is familiar with React, or any other UI library. It also demonstrates that core Soroban libraries all work with any JavaScript project.)
 
@@ -83,7 +72,7 @@ git add .
 git commit -m "init from solid ts template"
 ```
 
-### 3. Copy in the `initialize.js` script
+### 3. Copy in the `initialize.js` script {#3-copy-in-the-initializejs-script}
 
 The SDF-maintained `soroban-template-astro` has [an `initialize.js` script](https://github.com/stellar/soroban-astro-template/blob/main/initialize.js) in its project root. Copy-paste it into your project.
 
@@ -140,7 +129,7 @@ src/contracts/*
 !src/contracts/util.ts
 ```
 
-#### C. `package.json`
+#### C. `package.json` {#c-packagejson}
 
 Make sure users of your template don't forget to run the `initialize.js` script. Modify the `scripts` section as follows:
 
@@ -181,7 +170,7 @@ Also make sure that this project is set up to allow the `import` statements in t
 
 While you're here, you can also update the `name` (maybe `"soroban-template-solid"`) and `description`.
 
-#### E. `src/contracts/util.ts`
+#### E. `src/contracts/util.ts` {#e-srccontractsutilts}
 
 In the `.gitignore` above, you may have noticed that this file is explicitly included. Copy it in from [the official template](https://github.com/stellar/soroban-astro-template/blob/main/src/contracts/util.ts). You'll need to create the `src/contracts` folder.
 
@@ -291,5 +280,5 @@ Some things we did in this section:
 
 After you're done building your own frontend template, what's next? You choose! You can:
 
-- See more complex example contracts in the [Example Contracts](../../smart-contracts/example-contracts/README.mdx) section.
-- Learn more about the [internal architecture and design](../../../learn/fundamentals/contract-development/README.mdx) of Soroban.
+- See more complex example contracts in the [Example Contracts](/docs/build/smart-contracts/example-contracts) section.
+- Learn more about the [internal architecture and design](/docs/learn/fundamentals/contract-development) of Soroban.
diff --git a/docs/build/guides/dapps/state-archival.mdx b/docs/build/guides/dapps/state-archival.mdx
index 13ed583d7..8ad7b8de0 100644
--- a/docs/build/guides/dapps/state-archival.mdx
+++ b/docs/build/guides/dapps/state-archival.mdx
@@ -5,7 +5,7 @@ description: Learn how to implement state archival in your dapp
 
 When developing decentralized applications on Stellar, state archival is part of what we need to consider due to how data is stored on the network. This guide will help you understand how to work with state archival in your dapp.
 
-Some state archival terminology we will be using in this guide are described in the [state archival section](../../../learn/fundamentals/contract-development/storage/state-archival.mdx#terms-and-semantics).
+Some state archival terminology we will be using in this guide are described in the [state archival section](../../../learn/fundamentals/contract-development/storage/state-archival#terms-and-semantics).
 
 ## Why managing state archival is important for applications
 
@@ -81,11 +81,11 @@ impl TtlContract {
 mod test;
 ```
 
-:::info
+<Info>
 
 The above contract shows how to extend the TTL of a `Persistent`, `Instance`, and `Temporary` data entry. The `extend_ttl()` method is used to extend the TTL of the data entry to a new ledger height.
 
-:::
+</Info>
 
 #### Using the Extend TTL method in your Contract
 
@@ -261,7 +261,7 @@ async function performContractAction(contractId, method, ...args) {
 
 For restoring an entire contract instance, you might need a separate function:
 
-Here we will be using the [`getLedgerEntries` method](../../../data/apis/rpc/api-reference/methods/getLedgerEntries.mdx#2-request-the-contractcode-using-the-retrieved-ledgerkey) to get the WASM code of the contract and also the [`restoreFootprint` operation](../../../learn/fundamentals/transactions/list-of-operations.mdx#restore-footprint) to restore the contract instance.
+Here we will be using the [`getLedgerEntries` method](../../../data/apis/rpc/api-reference/methods/getLedgerEntries#2-request-the-contractcode-using-the-retrieved-ledgerkey) to get the WASM code of the contract and also the [`restoreFootprint` operation](../../../learn/fundamentals/transactions/list-of-operations#restore-footprint) to restore the contract instance.
 
 ```javascript
 async function restoreContractInstance(contractId) {
@@ -333,11 +333,11 @@ function getWasmLedgerKey(entry) {
 }
 ```
 
-:::info
+<Info>
 
 This function specifically restores a contract instance and its associated Wasm code. It retrieves the contract's footprint and Wasm entry, creates a restoration transaction, which is then signed using Freighter and submitted to the network.
 
-:::
+</Info>
 
 ## When to use these functions
 
diff --git a/docs/build/guides/dapps/working-with-contract-specs.mdx b/docs/build/guides/dapps/working-with-contract-specs.mdx
index beec3d85d..7c3d96101 100644
--- a/docs/build/guides/dapps/working-with-contract-specs.mdx
+++ b/docs/build/guides/dapps/working-with-contract-specs.mdx
@@ -19,11 +19,11 @@ These details guide how you interact with the contract, regardless of the progra
 
 Before diving into contract interactions, ensure you have the following:
 
-- Stellar CLI ([`stellar`](../../smart-contracts/getting-started/setup.mdx#install-the-stellar-cli)) installed
-- A Soroban-compatible SDK for your programming language. View the [list of available SDKs](../../../tools/sdks/README.mdx) to find one that suits your needs
-- Access to a Stellar [RPC server](../../..//README.mdx) (local or on a test network)
+- Stellar CLI ([`stellar`](../../smart-contracts/getting-started/setup#install-the-stellar-cli)) installed
+- A Soroban-compatible SDK for your programming language. View the [list of available SDKs](/docs/tools/sdks) to find one that suits your needs
+- Access to a Stellar [RPC server](/docs) (local or on a test network)
 
-For this guide, we will focus on the [Java](../../../tools/sdks/client-sdks.mdx#java-sdk), [Python](../../../tools/sdks/client-sdks.mdx#python-sdk), and [PHP](../../../tools/sdks/client-sdks.mdx#php-sdk) SDKs for reference, but the concepts can also be applied to other languages.
+For this guide, we will focus on the [Java](../../../tools/sdks/client-sdks#java-sdk), [Python](../../../tools/sdks/client-sdks#python-sdk), and [PHP](../../../tools/sdks/client-sdks#php-sdk) SDKs for reference, but the concepts can also be applied to other languages.
 
 ## What are contract specs?
 
@@ -31,7 +31,7 @@ A contract spec is just like an ABI (Application Binary Interface) in Ethereum.
 
 This specification serves as a crucial bridge between the smart contract and client applications, enabling them to interact without needing to know the contract's internal implementation details.
 
-# Stellar Contract Spec
+## Stellar Contract Spec
 
 When you compile a smart contract using the Rust SDK, the resulting Wasm file includes a special section containing a complete description of your contract's interface types. This is often referred to as the contract's `spec` or `contract spec`. Stellar smart contract specification, known as the `contract spec`, is a foundational element for interacting with contracts and for building dApps on the Stellar network. The contract Spec provides a robust and fully typed definitions for interacting with smart contracts, offering functionality equivalent to Ethereum's ABI while addressing its limitations.
 
@@ -68,9 +68,9 @@ Stellar’s Contract Spec shares many similarities with Ethereum’s ABI but als
 
 [The Stellar CLI](https://github.com/stellar/stellar-cli) provides a command to generate a contract spec from a contract's source code. This process is easy but requires you to have the Wasm binary of the contract.
 
-Sometimes, you may not have access to the contract's source code or the ability to compile it. In such cases, you must use the [`stellar contract fetch`](../../../tools/cli/stellar-cli.mdx#stellar-contract-fetch) command to download the contract's Wasm binary and generate the spec.
+Sometimes, you may not have access to the contract's source code or the ability to compile it. In such cases, you must use the [`stellar contract fetch`](../../../tools/cli/stellar-cli#stellar-contract-fetch) command to download the contract's Wasm binary and generate the spec.
 
-Finally, we use the [`stellar bindings`](../../../tools/cli/stellar-cli.mdx#stellar-contract-bindings-json) command to generate the contract spec from the Wasm binary.
+Finally, we use the [`stellar bindings`](../../../tools/cli/stellar-cli#stellar-contract-bindings-json) command to generate the contract spec from the Wasm binary.
 
 The Stellar Lab has a [Contract Explorer](https://lab.stellar.org/smart-contracts/contract-explorer) also provides the ability to view and to download a contract's contract spec.
 
@@ -239,7 +239,7 @@ These specifications are crucial for encoding and decoding data when interacting
 
 ## Soroban types
 
-Before we dive into interacting with Stellar smart contracts, it is important to note that Soroban has its own set of types that are used to interact with the contracts as described in [this guide](../../../learn/fundamentals/contract-development/types/built-in-types.mdx). Here are some of the common types:
+Before we dive into interacting with Stellar smart contracts, it is important to note that Soroban has its own set of types that are used to interact with the contracts as described in [this guide](../../../learn/fundamentals/contract-development/types/built-in-types). Here are some of the common types:
 
 - `u32`: Unsigned 32-bit integer
 - `u64`: Unsigned 64-bit integer
@@ -264,11 +264,11 @@ One of the most common tasks when working with Stellar smart contracts is conver
 
 In most SDKs, the `ScVal` class or function is used to convert between Soroban types and native types.
 
-:::note
+<Note>
 
 The JSON code block shows the contract spec, while RUST code blocks show the contract for each example.
 
-:::
+</Note>
 
 ### 1. Invoking a contract function with no parameters
 
@@ -276,9 +276,9 @@ We will be using the `increment` function of the sample [increment contract](htt
 
 In this scenario, there is no need for conversions and passing the value `null` as contract arguments is sufficient in most SDKs.
 
-<CodeExample>
+<CodeGroup>
 
-```rust
+```rust Rust
 #[contractimpl]
 impl IncrementContract {
     /// Increment increments an internal counter, and returns the value.
@@ -299,7 +299,7 @@ impl IncrementContract {
 }
 ```
 
-```json
+```json JSON
 [
   {
     "type": "function",
@@ -315,7 +315,7 @@ impl IncrementContract {
 ]
 ```
 
-```python
+```python Python
 # pip install --upgrade stellar-sdk
 from stellar_sdk import SorobanServer, soroban_rpc, Account, Asset, Keypair, Network, TransactionBuilder
 
@@ -355,7 +355,7 @@ print("status:", response.status)
 print("errorResultXdr:", response.error_result_xdr)
 ```
 
-```java
+```java Java
 // implementation 'network.lightsail:stellar-sdk:3.1.0'
 import org.stellar.sdk.KeyPair;
 import org.stellar.sdk.Network;
@@ -431,7 +431,7 @@ public class SendTransactionExample {
 
 ```
 
-```php
+```php PHP
 <?php
 
 namespace App\Models;
@@ -476,13 +476,13 @@ class Invoker
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::info
+<Info>
 
 Subsequent examples will show code blocks for using the contract spec only to reduce redundancy.
 
-:::
+</Info>
 
 ### 2. Invoking a contract function with one or more parameters
 
@@ -494,9 +494,9 @@ We know from the spec that the `hello` function takes a string parameter and ret
 
 This process is convenient using the `ScVal` class or function in most SDKs.
 
-<CodeExample>
+<CodeGroup>
 
-```rust
+```rust Rust
 #[contract]
 pub struct HelloContract;
 
@@ -508,7 +508,7 @@ impl HelloContract {
 }
 ```
 
-```json
+```json JSON
 [
   {
     "type": "function",
@@ -535,7 +535,7 @@ impl HelloContract {
 ]
 ```
 
-```python
+```python Python
 from stellar_sdk import Keypair, Network, SorobanServer, TransactionBuilder, scval
 .....
 tx = (
@@ -550,7 +550,7 @@ tx = (
 ).build())
 ```
 
-```java
+```java Java
 import org.stellar.sdk.scval.Scv;
 import org.stellar.sdk.xdr.SCVal;
 // .....
@@ -562,7 +562,7 @@ TransactionBuilder transaction = new TransactionBuilder(source, Network.TESTNET)
 Transaction tx = transaction.addOperation(operation).build();
 ```
 
-```php
+```php PHP
 $arg = \Soneso\StellarSDK\Xdr\XdrSCVal::forString("John");
 $invokeContractHostFunction = new InvokeContractHostFunction($contractId, "hello", [$arg]);
 $builder = new InvokeHostFunctionOperationBuilder($invokeContractHostFunction);
@@ -572,7 +572,7 @@ $transaction = (new TransactionBuilder($accountA))
     ->addOperation($op)->build();
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### 3. Getting responses from contracts
 
@@ -590,11 +590,11 @@ Steps:
 
 This process is convenient using the `ScVal` class or function in most SDKs.
 
-Ideally, to retrieve this value, we need to use the [`getTransaction`](../../../data/apis/rpc/api-reference/methods/getTransaction.mdx) RPC method using the response hash of the transaction that invoked the contract function.
+Ideally, to retrieve this value, we need to use the [`getTransaction`](../../../data/apis/rpc/api-reference/methods/getTransaction) RPC method using the response hash of the transaction that invoked the contract function.
 
-<CodeExample>
+<CodeGroup>
 
-```rust
+```rust Rust
 #[contract]
 pub struct HelloContract;
 
@@ -606,7 +606,7 @@ impl HelloContract {
 }
 ```
 
-```json
+```json JSON
 [
   {
     "type": "function",
@@ -633,7 +633,7 @@ impl HelloContract {
 ]
 ```
 
-```python
+```python Python
 from stellar_sdk import SorobanServer, soroban_rpc
 from stellar_sdk import xdr as stellar_xdr
 from stellar_sdk.soroban_rpc import GetTransactionStatus
@@ -659,7 +659,7 @@ else:
     print(f"Transaction failed: {get_transaction_data.result_xdr}")
 ```
 
-```java
+```java Java
 import org.stellar.sdk.responses.sorobanrpc.GetTransactionResponse;
 import org.stellar.sdk.xdr.SCVal;
 import org.stellar.sdk.xdr.TransactionMeta;
@@ -696,7 +696,7 @@ public static void main(String[] args) {
 }
 ```
 
-```php
+```php PHP
 <?php
 use Soneso\StellarSDK\Soroban\Responses\GetTransactionResponse;
 use Soneso\StellarSDK\Soroban\SorobanServer;
@@ -725,11 +725,11 @@ class Test {
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## Working with complex data types
 
-As described in [this guide](../../../learn/fundamentals/contract-development/types/custom-types.mdx), there are some other variants of data structure supported by Soroban. They are
+As described in [this guide](../../../learn/fundamentals/contract-development/types/custom-types), there are some other variants of data structure supported by Soroban. They are
 
 - `Struct` with named fields
 - `Struct` with unnamed fields
@@ -742,9 +742,9 @@ We would be looking at how these variants translate to the spec and how to const
 
 Structs with named values when converted to ABI or spec are represented as a `ScMap` where each value has the key in `ScSymbol` and the value in the underlying type.
 
-<CodeExample>
+<CodeGroup>
 
-```rust
+```rust Rust
 #[contracttype]
 #[derive(Clone, Debug, Eq, PartialEq)]
 pub struct State {
@@ -753,7 +753,7 @@ pub struct State {
 }
 ```
 
-```json
+```json JSON
 [
   {
     "type": "struct",
@@ -779,7 +779,7 @@ pub struct State {
 ]
 ```
 
-```python
+```python Python
 from stellar_sdk import scval
 scval.to_map(
     {
@@ -789,7 +789,7 @@ scval.to_map(
 )
 ```
 
-```java
+```java Java
 import org.stellar.sdk.xdr.SCVal;
 import org.stellar.sdk.scval.Scv;
 import java.util.LinkedHashMap;
@@ -800,7 +800,7 @@ map.put(Scv.toSymbol("last_incr"), Scv.toUint32(0));
 SCVal val = Scv.toMap(map);
 ```
 
-```php
+```php PHP
 <?php
 use Soneso\StellarSDK\Xdr\XdrSCVal;
 
@@ -812,21 +812,21 @@ XdrSCVal::forMap(
 );
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Struct with unnamed fields
 
 Structs with unnamed values when converted to ABI or spec are represented as a `ScVal` where each value has the underlying type.
 
-<CodeExample>
+<CodeGroup>
 
-```rust
+```rust Rust
 #[contracttype]
 #[derive(Clone, Debug, Eq, PartialEq)]
 pub struct State(pub u32, pub u32);
 ```
 
-```json
+```json JSON
 [
   {
     "type": "struct",
@@ -850,7 +850,7 @@ pub struct State(pub u32, pub u32);
 ]
 ```
 
-```python
+```python Python
 from stellar_sdk import scval
 scval.to_vec(
     [
@@ -860,7 +860,7 @@ scval.to_vec(
 )
 ```
 
-```java
+```java Java
 import org.stellar.sdk.xdr.SCVal;
 import org.stellar.sdk.scval.Scv;
 import java.util.LinkedHashMap;
@@ -871,7 +871,7 @@ vec.add(Scv.toUint32(0));
 SCVal val = Scv.toVec(vec);
 ```
 
-```php
+```php PHP
 <?php
 use Soneso\StellarSDK\Xdr\XdrSCVal;
 
@@ -883,15 +883,15 @@ XdrSCVal::forVec(
 );
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Enum (unit and tuple variants)
 
 Enums are generally represented with `ScVec`, their unit types are represented as `ScSymbol` and their tuple variants are represented as the underlying types.
 
-<CodeExample>
+<CodeGroup>
 
-```rust
+```rust Rust
 #[contracttype]
 #[derive(Clone, Debug, Eq, PartialEq)]
 pub enum Enum {
@@ -900,7 +900,7 @@ pub enum Enum {
 }
 ```
 
-```json
+```json JSON
 [
   {
     "type": "union",
@@ -926,7 +926,7 @@ pub enum Enum {
 ]
 ```
 
-```python
+```python Python
 from stellar_sdk import scval
 scval.to_vec(
     [
@@ -940,7 +940,7 @@ scval.to_vec(
 )
 ```
 
-```java
+```java Java
 import org.stellar.sdk.xdr.SCVal;
 import org.stellar.sdk.scval.Scv;
 import java.util.LinkedHashMap;
@@ -953,7 +953,7 @@ vec.add(Scv.toMap(map));
 SCVal val = Scv.toVec(vec);
 ```
 
-```php
+```php PHP
 <?php
 use Soneso\StellarSDK\Xdr\XdrSCVal;
 
@@ -969,15 +969,15 @@ XdrSCVal::forVec(
 );
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Enum (integer variants)
 
 Enums are generally represented with `ScVec`, the integer variant has no keys so it's just a `ScVec` of the underlying type.
 
-<CodeExample>
+<CodeGroup>
 
-```rust
+```rust Rust
 #[contracttype]
 #[derive(Copy, Clone, Debug, Eq, PartialEq)]
 #[repr(u32)]
@@ -987,7 +987,7 @@ pub enum Enum {
 }
 ```
 
-```json
+```json JSON
 [
   {
     "type": "struct",
@@ -1009,7 +1009,7 @@ pub enum Enum {
 ]
 ```
 
-```python
+```python Python
 from stellar_sdk import scval
 scval.to_vec(
     [
@@ -1019,7 +1019,7 @@ scval.to_vec(
 )
 ```
 
-```java
+```java Java
 import org.stellar.sdk.xdr.SCVal;
 import org.stellar.sdk.scval.Scv;
 import java.util.LinkedHashMap;
@@ -1030,7 +1030,7 @@ vec.add(Scv.toUint32(0));
 SCVal val = Scv.toVec(vec);
 ```
 
-```php
+```php PHP
 <?php
 use Soneso\StellarSDK\Xdr\XdrSCVal;
 
@@ -1042,7 +1042,7 @@ XdrSCVal::forVec(
 );
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### A complex example
 
@@ -1050,9 +1050,9 @@ Let's use the [timelock contract](https://github.com/stellar/soroban-examples/bl
 
 This example uses a `TimeBound` struct that has a `TimeBoundKind` enum as one of its fields, which are parameters to the `deposit` function. This example combines most of the concepts we have discussed so far.
 
-<CodeExample>
+<CodeGroup>
 
-```rust
+```rust Rust
 #[derive(Clone)]
 #[contracttype]
 pub enum TimeBoundKind {
@@ -1081,7 +1081,7 @@ impl ClaimableBalanceContract {
 }
 ```
 
-```json
+```json JSON
 [
   {
     "type": "union",
@@ -1172,7 +1172,7 @@ impl ClaimableBalanceContract {
 ]
 ```
 
-```python
+```python Python
 from stellar_sdk import scval, SorobanServer, Keypair, Network, TransactionBuilder
 
 secret = "SXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
@@ -1217,11 +1217,11 @@ tx = (
 )
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## Reading contract events
 
-Reading contract events is similar to reading transaction results. You can use the [`getEvents`](../../../data/apis/rpc/api-reference/methods/getEvents.mdx) RPC method to get the list of events associated with a contract.
+Reading contract events is similar to reading transaction results. You can use the [`getEvents`](../../../data/apis/rpc/api-reference/methods/getEvents) RPC method to get the list of events associated with a contract.
 
 One common convention is that small strings like function names, enum keys, and event topics are represented as `ScSymbol` in the contract spec.
 
@@ -1229,9 +1229,9 @@ However, event topics can be any `scval` type depending on the contract implemen
 
 In the example below, we will be encoding the mint to `ScSymbol` before querying it, and also encoding the addresses to `ScAddress`. Even after getting the event, we will need to parse the topics and value to get the actual values again from xdr base 64 to their corresponding types before then converting it to native types.
 
-<CodeExample>
+<CodeGroup>
 
-```rust
+```rust Rust
 let address_1: &Address = "GXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX".into();
 let address_2: &Address = "GXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX".into();
 let count: i128 = 1;
@@ -1239,7 +1239,7 @@ env.events()
     .publish((symbol_short!("mint"), address_1, address_2), count);
 ```
 
-```python
+```python Python
 from stellar_sdk import SorobanServer, scval, xdr as stellar_xdr
 from stellar_sdk.exceptions import NotFoundError, BadResponseError
 from stellar_sdk.soroban_server import EventFilter, EventFilterType
@@ -1294,7 +1294,7 @@ def get_events():
         print(f"Error occurred: {str(e)}")
 ```
 
-```bash
+```bash bash
 curl -X POST \
   -H 'Content-Type: application/json' \
   -d '{
@@ -1326,7 +1326,7 @@ curl -X POST \
   https://soroban-testnet.stellar.org
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## Wrapping Up
 
diff --git a/docs/build/guides/events/README.mdx b/docs/build/guides/events/README.mdx
deleted file mode 100644
index c5785b5bd..000000000
--- a/docs/build/guides/events/README.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: Contract Events
-hide_table_of_contents: true
-sidebar_position: 20
----
-
-Learn how to emit, ingest, and use events published from a Stellar smart contract.
diff --git a/docs/build/guides/events/consume.mdx b/docs/build/guides/events/consume.mdx
index d011b3c51..cbb2ec9de 100644
--- a/docs/build/guides/events/consume.mdx
+++ b/docs/build/guides/events/consume.mdx
@@ -79,11 +79,11 @@ INFO sqlalchemy.engine.Engine [...] ('CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2
 INFO sqlalchemy.engine.Engine COMMIT
 ```
 
-:::info
+<Info>
 
 Here, we are storing XDR encoded values. We could have instead decided to store decoded values in the database. XDR being a compressed format, choosing when to decode the value is a tradeoff between CPU usage and memory consumption.
 
-:::
+</Info>
 
 ## Consuming events
 
@@ -112,11 +112,11 @@ INFO sqlalchemy.engine.Engine [...] ()
 INFO sqlalchemy.engine.Engine ROLLBACK
 ```
 
-:::note
+<Note>
 
 Notice previous events being present and having a slightly different formatting. While we are using a schema, it is still easy to corrupt a database. This is only shown for demonstration purposes.
 
-:::
+</Note>
 
 SQLAlchemy allows to make advanced queries. For example, we could filter a single event based on some specific fields.
 
@@ -206,5 +206,5 @@ There is a large body of technical literature around this topic and there is no
 
 While researching this topic, you could search for _message brokers_ like RabbitMQ of Kafka---to cite widely used solutions.
 
-[ingest guide]: ingest.mdx
+[ingest guide]: ingest
 [stellar-sdk]: https://stellar-sdk.readthedocs.io/
diff --git a/docs/build/guides/events/index.mdx b/docs/build/guides/events/index.mdx
new file mode 100644
index 000000000..cf044fd1a
--- /dev/null
+++ b/docs/build/guides/events/index.mdx
@@ -0,0 +1,4 @@
+---
+title: Contract Events
+description: "Learn how to emit, ingest, and use events published from a Stellar smart contract."
+---
diff --git a/docs/build/guides/events/ingest.mdx b/docs/build/guides/events/ingest.mdx
index 6ba2a04a4..216b09268 100644
--- a/docs/build/guides/events/ingest.mdx
+++ b/docs/build/guides/events/ingest.mdx
@@ -3,19 +3,16 @@ title: Ingest events published from a contract
 description: Use Stellar RPC's getEvents method for querying events, with a 7 day retention window
 ---
 
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
 Stellar RPC provides a [`getEvents` method] which allows you to query events from a smart contract. However, the data retention window for these events is 7 days at most. If you need access to a longer-lived record of these events you'll want to "ingest" the events as they are published, maintaining your own record or database as events are ingested.
 
-There are many strategies you can use to ingest and keep the events published by a smart contract. Among the simplest might be using a community-developed tool such as [Mercury](https://mercurydata.app) which will take all the infrastructure work off your plate for a low subscription fee. Or, [indexers](../../../data/indexers/README.mdx) can provide ingested event data for affordable prices.
+There are many strategies you can use to ingest and keep the events published by a smart contract. Among the simplest might be using a community-developed tool such as [Mercury](https://mercurydata.app) which will take all the infrastructure work off your plate for a low subscription fee. Or, [indexers](/docs/data/indexers) can provide ingested event data for affordable prices.
 
 Another approach we'll explore here is using a cron job to query Stellar RPC periodically and store the relevant events in a locally stored SQLite database. We are going to use an Object Relational Mapper (ORM), allowing us to write database query directly in Python or JavaScript.
 
 ## Setup
 
-<Tabs groupId="language" defaultValue="python">
-<TabItem value="python" label="Python">
+<Tabs>
+<Tab title="Python">
 
 In a [virtual environment](https://docs.python.org/3/tutorial/venv.html), install the Python dependencies:
 
@@ -23,13 +20,13 @@ In a [virtual environment](https://docs.python.org/3/tutorial/venv.html), instal
 pip install sqlalchemy stellar-sdk
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 ## Setup the Database Client
 
-<Tabs groupId="language" defaultValue="python">
-<TabItem value="python" label="Python">
+<Tabs>
+<Tab title="Python">
 
 To access the database, we will use [SQLAlchemy](https://www.sqlalchemy.org), which is a frequently used Python library to query database.
 
@@ -67,11 +64,11 @@ engine = create_engine("sqlite://", echo=True)
 Base.metadata.create_all(engine)
 ```
 
-:::tip
+<Tip>
 
 By setting `echo=True` we can understand what is happening on the database. Creating the database table leads to the following logs:
 
-:::
+</Tip>
 
 ```text
 BEGIN (implicit)
@@ -91,8 +88,8 @@ CREATE TABLE StellarEvent (
 COMMIT
 ```
 
-</TabItem>
-<TabItem value="js" label="JavaScript">
+</Tab>
+<Tab title="JavaScript">
 
 The finer details of choosing a Prisma configuration are beyond the scope of this document. You can get a lot more information in the [Prisma quickstart](https://www.prisma.io/docs/getting-started/quickstart). Here is our Prisma schema's model:
 
@@ -110,14 +107,14 @@ model StellarEvent {
 }
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
-:::info
+<Info>
 
 Using a database model is very convenient as it allows us to control the database schema programmatically. If we need to change the schema, by adding a new columns for instance, then using an ORM allows us to use very powerful migration tools.
 
-:::
+</Info>
 
 We'll use this model to create and query for the events stored in our database.
 
@@ -125,14 +122,13 @@ We'll use this model to create and query for the events stored in our database.
 
 First, we'll need to query the events from Stellar RPC. This simple example makes an RPC request using the [`getEvents` method], filtering for all `transfer` events that are emitted by the native XLM contract.
 
-:::note
+<Note>
 
 We are making some assumptions here. We'll assume that your contract sees enough activity, and that you are querying for events frequently enough that you aren't in danger of needing to figure out the oldest ledger Stellar RPC is aware of. The approach we're taking is to find the largest (most recent) ledger sequence number in the database and query for events starting there. Your use-case may require some logic to determine what the latest ledger is, and what the oldest ledger available is, etc.
 
-:::
-
-<Tabs groupId="language" defaultValue="python">
-<TabItem value="python" label="Python">
+</Note>
+<Tabs>
+<Tab title="Python">
 
 If we start from scratch, there is no known ledger so we can try to ingest roughly the last 7 days assuming a ledger closes every 6s.
 
@@ -176,8 +172,8 @@ res = soroban_server.get_events(
 events = res.events
 ```
 
-</TabItem>
-<TabItem value="js" label="JavaScript">
+</Tab>
+<Tab title="JavaScript">
 
 We use the `@stellar/stellar-sdk` library:
 
@@ -208,21 +204,21 @@ let { events } = await server.getEvents({
 });
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 ## Store Events in the Database
 
 Now, we'll check if the `events` object contains any new events we should store, and we do exactly that. We're storing the event's topics and values as base64-encoded strings here, but you could decode the necessary topics and values into the appropriate data types for your use-case.
 
-<Tabs groupId="language" defaultValue="python">
-<TabItem value="python" label="Python">
+<Tabs>
+<Tab title="Python">
 
-:::tip
+<Tip>
 
 Make your life easier with a SQLAlchemy [`sessionmaker`](https://docs.sqlalchemy.org/en/20/orm/session_basics.html#using-a-sessionmaker) when making transactions (e.g. add more than one record in a single database call.)
 
-:::
+</Tip>
 
 ```python
 import sqlalchemy
@@ -249,8 +245,8 @@ INFO sqlalchemy.engine.Engine [...] ('CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2
 COMMIT
 ```
 
-</TabItem>
-<TabItem value="js" label="JavaScript">
+</Tab>
+<Tab title="JavaScript">
 
 ```javascript
 if (events?.length) {
@@ -272,47 +268,47 @@ if (events?.length) {
 }
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 ## Run the Script with Cron
 
 A cron entry is an excellent way to automate this script to gather and ingest events every so often. You could configure this script to run as (in)frequently as you want or need. This example would run the script every 24 hours at 1:14 pm:
 
-<Tabs groupId="language" defaultValue="python">
-<TabItem value="python" label="Python">
+<Tabs>
+<Tab title="Python">
 
 ```sh
 14 13 * * * python /absolute/path/to/script.py
 ```
 
-</TabItem>
-<TabItem value="js" label="JavaScript">
+</Tab>
+<Tab title="JavaScript">
 
 ```sh
 14 13 * * * node /absolute/path/to/script.js
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 Here's another example that will run the script every 30 minutes:
 
-<Tabs groupId="language" defaultValue="python">
-<TabItem value="python" label="Python">
+<Tabs>
+<Tab title="Python">
 
 ```sh
 30 * * * * python /absolute/path/to/script.py
 ```
 
-</TabItem>
-<TabItem value="js" label="JavaScript">
+</Tab>
+<Tab title="JavaScript">
 
 ```sh
 30 * * * * node /absolute/path/to/script.js
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
-[`getEvents` method]: ../../../data/apis/rpc/api-reference/methods/getEvents.mdx
+[`getEvents` method]: ../../../data/apis/rpc/api-reference/methods/getEvents
diff --git a/docs/build/guides/events/publish.mdx b/docs/build/guides/events/publish.mdx
index 0d4d3e36a..0bac83829 100644
--- a/docs/build/guides/events/publish.mdx
+++ b/docs/build/guides/events/publish.mdx
@@ -1,16 +1,17 @@
 ---
 title: Publish events from a Rust contract
-hide_table_of_contents: true
 description: Publish events from a Rust contract
 ---
 
 An event can contain topics, alongside the data it is publishing. The topics data can be any value or type you want.
 
-:::info[Whisk Changes]
+<Info>
+
+**Whisk Changes**
 
 With the release of Whisk, Protocol 23, the syntax for publishing smart contract events has changed. In order to provide the most up-to-date information, this guide has been updated to include the new patterns. Find more detailed information in the [Rust SDK documentation].
 
-:::
+</Info>
 
 The strategy here is to first create some `struct`s that will define how our events are shaped. Then, within the contract's function, we can create and publish those structs.
 
@@ -83,5 +84,5 @@ pub fn transfer(env: Env, from: Address, to: Address, amount: i128) {
 }
 ```
 
-[token interface]: ../../../tokens/token-interface.mdx
+[token interface]: ../../../tokens/token-interface
 [Rust SDK documentation]: https://docs.rs/soroban-sdk/latest/soroban_sdk/_migrating/v23_contractevent/index.html
diff --git a/docs/build/guides/events/replay-ledger-close-meta.mdx b/docs/build/guides/events/replay-ledger-close-meta.mdx
index ff849f1ff..157b46fba 100644
--- a/docs/build/guides/events/replay-ledger-close-meta.mdx
+++ b/docs/build/guides/events/replay-ledger-close-meta.mdx
@@ -3,13 +3,13 @@ title: Replay a ledger to collect its LedgerCloseMeta
 description: Use Stellar Core to replay a single ledger from the history archives and collect its LedgerCloseMeta, including the diagnostic events.
 ---
 
-:::caution
+<Warning>
 
-Replaying a ledger is a complex and advanced process, and it isn't suitable for most application integrations, which are better served by [Stellar RPC](../../../data/apis/rpc/README.mdx) or an [indexer](../../../data/indexers/README.mdx). It's helpful when a transaction's diagnostic events are needed and aren't accessible any other way.
+Replaying a ledger is a complex and advanced process, and it isn't suitable for most application integrations, which are better served by [Stellar RPC](/docs/data/apis/rpc) or an [indexer](/docs/data/indexers). It's helpful when a transaction's diagnostic events are needed and aren't accessible any other way.
 
-:::
+</Warning>
 
-:::tip
+<Tip>
 
 An AI coding agent can do all of this for you. Give it a prompt that links to this guide, like:
 
@@ -18,9 +18,9 @@ Collect the LedgerCloseMeta for transaction ____ from ledger ____ and analyse fr
 https://developers.stellar.org/docs/build/guides/events/replay-ledger-close-meta.md
 ```
 
-:::
+</Tip>
 
-When Stellar Core closes a ledger it can emit a `LedgerCloseMeta`, the complete record of what closing the ledger did: the transactions applied, their results, every ledger entry they created, updated, or deleted, and the events they emitted. Stellar RPC, Horizon, and Galexie are all built on it, and Stellar RPC's [`getLedgers`](../../../data/apis/rpc/api-reference/methods/getLedgers.mdx) method serves it.
+When Stellar Core closes a ledger it can emit a `LedgerCloseMeta`, the complete record of what closing the ledger did: the transactions applied, their results, every ledger entry they created, updated, or deleted, and the events they emitted. Stellar RPC, Horizon, and Galexie are all built on it, and Stellar RPC's [`getLedgers`](/docs/data/apis/rpc/api-reference/methods/getLedgers) method serves it.
 
 The meta a Stellar RPC serves is produced by a Stellar Core, and contains only what that Stellar Core was configured to produce. Diagnostic events are a common gap because of their size and the performance cost to generate and store them. Stellar Core leaves them off by default, but they are the part of the meta that explains why a contract failed and the only way to collect a trace of what contracts were called.
 
@@ -36,7 +36,7 @@ On macOS:
 brew install stellar-core stellar-xdr jq
 ```
 
-On Linux, install `stellar-core` from [SDF's apt repository](../../../validators/admin-guide/installation.mdx#configure-sdf-apt-repository-on-the-system), and `stellar-xdr` with cargo:
+On Linux, install `stellar-core` from [SDF's apt repository](/docs/validators/admin-guide/installation#configure-sdf-apt-repository-on-the-system), and `stellar-xdr` with cargo:
 
 ```sh
 sudo apt install stellar-core jq
@@ -87,7 +87,7 @@ To replay a Testnet ledger instead, use the network passphrase and validators in
 
 ### Diagnostic events
 
-`ENABLE_SOROBAN_DIAGNOSTIC_EVENTS=true` is the line that adds [diagnostic events](../../../learn/fundamentals/stellar-data-structures/events.mdx) to the meta. With it, the Soroban host records events while it applies each Soroban transaction: a `fn_call` and `fn_return` for every contract function called, errors raised by the host, and logs. Contract events are included in the same list, so everything appears in the order it happened.
+`ENABLE_SOROBAN_DIAGNOSTIC_EVENTS=true` is the line that adds [diagnostic events](/docs/learn/fundamentals/stellar-data-structures/events) to the meta. With it, the Soroban host records events while it applies each Soroban transaction: a `fn_call` and `fn_return` for every contract function called, errors raised by the host, and logs. Contract events are included in the same list, so everything appears in the order it happened.
 
 **Diagnostic events are not part of the protocol.** They're written to a part of the meta that isn't hashed into the ledger, so turning them on doesn't change the result of the replay. The ledger comes out identical. The meta just says more about how it got there. The setting is off by default, and can't be turned on for a validator.
 
@@ -105,7 +105,7 @@ Then catch up to the ledger, streaming its meta to a file. The ledger used here
 stellar-core --conf mainnet.cfg catchup 64681481/1 --metadata-output-stream meta.xdr
 ```
 
-[`catchup`](../../../validators/admin-guide/commands.mdx#catchup) takes a destination ledger and a count, as `DESTINATION/COUNT`. It stops at the destination, after replaying at least that many ledgers. `64681481/1` replays at least one ledger, 64681481 itself.
+[`catchup`](/docs/validators/admin-guide/commands#catchup) takes a destination ledger and a count, as `DESTINATION/COUNT`. It stops at the destination, after replaying at least that many ledgers. `64681481/1` replays at least one ledger, 64681481 itself.
 
 Progress is written to a `stellar-core-*.log` file in the directory rather than to the terminal, so catchup can look idle for minutes at a time. Add `--console` to see the log as it runs.
 
diff --git a/docs/build/guides/fees/README.mdx b/docs/build/guides/fees/README.mdx
deleted file mode 100644
index 8ec6383d9..000000000
--- a/docs/build/guides/fees/README.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: Fees & Metering
-hide_table_of_contents: true
-sidebar_position: 60
----
-
-Fees and metering in Soroban smart contracts work differently than the fees for "regular" Stellar transactions. The Stellar network still provides cheap, accessible transaction and that now includes smart contract metering!
diff --git a/docs/build/guides/fees/analyzing-smart-contract-cost.mdx b/docs/build/guides/fees/analyzing-smart-contract-cost.mdx
index 761520cce..e457aad4e 100644
--- a/docs/build/guides/fees/analyzing-smart-contract-cost.mdx
+++ b/docs/build/guides/fees/analyzing-smart-contract-cost.mdx
@@ -1,6 +1,5 @@
 ---
 title: Analyzing smart contract cost and efficiency
-hide_table_of_contents: false
 description: Create efficient and cost-effective contracts
 ---
 
@@ -38,13 +37,13 @@ impl ExampleContract {
 
 ```
 
-:::danger
+<Danger>
 
 **Problem**: Each iteration of the loop performs a separate read and write operation to update total_count in storage.
 
 **Inefficient**: This results in multiple expensive storage operations (read and write) within the loop, increasing gas costs significantly as the array size (values.len()) grows.
 
-:::
+</Danger>
 
 #### Optimal Contract ✅
 
@@ -73,17 +72,17 @@ impl ExampleContract {
 
 ```
 
-:::tip
+<Tip>
 
 In this optimized approach, we'll accumulate the changes outside the loop and perform a single storage update and also a single read operation. This reduces the number of storage operations and the overall gas cost of the contract.
 
-:::
+</Tip>
 
 ### 2. Proper use of batch operations
 
 From the first example, we can see that batch operations are more efficient than individual operations. This is because batch operations reduce the number of external calls to the blockchain, which can be costly. However, there are some scenarios where the use of batch operations can be further optimized. Examples are shown below.
 
-#### Not Optimal Contract ❎
+#### Not Optimal Contract ❎ {#not-optimal-contract--1}
 
 ```rust
 #![no_std]
@@ -112,13 +111,13 @@ impl TokenTransferContract {
 }
 ```
 
-:::danger
+<Danger>
 
 This function performs individual transfers for each recipient. While straightforward, it's inefficient because each transfer is a separate subcontract call, potentially leading to higher gas costs and slower execution.
 
-:::
+</Danger>
 
-#### Optimal Contract ✅
+#### Optimal Contract ✅ {#optimal-contract--1}
 
 ```rust
 #![no_std]
@@ -156,7 +155,7 @@ impl TokenTransferContract {
 }
 ```
 
-:::tip
+<Tip>
 
 This function optimizes the process by:
 
@@ -165,7 +164,7 @@ This function optimizes the process by:
 
 Internal distributions are cheaper due to the reduction in the number of costly external blockchain transactions. By transferring the total amount to the contract and then distributing it internally, the contract minimizes the number of external calls, reducing gas costs and improving efficiency.
 
-:::
+</Tip>
 
 ### 3. Use of events over storage
 
@@ -217,11 +216,11 @@ impl GameContract {
 }
 ```
 
-:::danger
+<Danger>
 
 We cannot store everything in storage like we would do in a traditional database. This approach is not cost-effective as it involves multiple storage operations for each player move and saves each achievement to the storage
 
-:::
+</Danger>
 
 #### Optimized Using Events
 
@@ -250,17 +249,17 @@ impl GameContract {
 }
 ```
 
-:::tip
+<Tip>
 
 In this optimized approach, we use events to store data that doesn't need to be accessed frequently. This reduces the number of storage operations and the overall gas cost of the contract.
 
-:::
+</Tip>
 
 #### Trade-offs:
 
 The current approach using events is indeed optimized for gas efficiency, but it comes with its own set of trade-offs. Let's see different approaches and their implications:
 
-##### Current Approach (Using Events)
+#### Current Approach (Using Events) {#current-approach-using-events}
 
 - Pros:
   - Extremely gas-efficient as it minimizes storage operations
@@ -272,7 +271,7 @@ The current approach using events is indeed optimized for gas efficiency, but it
   - Relies on external systems to capture and process the event data
   - Not suitable if you need to query or validate past moves within the contract
 
-##### Storing Latest Move in Persistent Storage and History in Temporary Storage
+#### Storing Latest Move in Persistent Storage and History in Temporary Storage {#storing-latest-move-in-persistent-storage-and-history-in-temporary-storage}
 
 This approach offers a balance between accessibility and efficiency.
 
@@ -289,13 +288,13 @@ This approach offers a balance between accessibility and efficiency.
 
 Heap allocated arrays are slow and costly. Prefer fixed-sized arrays or `soroban_sdk::vec!`. This is crucial for large arrays, as exceeding the current linear memory size (a multiple of 64KB) triggers `wasm32::memory_grow`, which is highly computationally intensive.
 
-##### Example (Heap Allocated Array) ❎
+#### Example (Heap Allocated Array) ❎ {#example-heap-allocated-array-}
 
 ```rust
 let mut v1 = alloc::vec![];
 ```
 
-##### Example (Fixed-Sized Array) ✅
+#### Example (Fixed-Sized Array) ✅ {#example-fixed-sized-array-}
 
 ```rust
 let mut v2 = [0; 100];
@@ -303,7 +302,7 @@ let mut v2 = [0; 100];
 
 Storing many items in a `Vec` can be inefficient due to the linear time complexity of membership checks. However, there are some alternatives to having a cumbersome `Vec`:
 
-##### Example (Inefficient Data Storage) ❎
+#### Example (Inefficient Data Storage) ❎ {#example-inefficient-data-storage-}
 
 ```rust
 #![no_std]
@@ -401,7 +400,9 @@ impl NonOptimalGameContract {
 }
 ```
 
-:::danger[This non-optimal version has several inefficiencies:]
+<Danger>
+
+**This non-optimal version has several inefficiencies:**
 
 - Single Vec for All Data:
 
@@ -431,9 +432,9 @@ impl NonOptimalGameContract {
 
   Moves and achievements are not clearly separated in the storage structure, making it harder to manage and potentially leading to confusion in more complex scenarios.
 
-:::
+</Danger>
 
-##### Alternative: using keyed vecs ✅
+#### Alternative: using keyed vecs ✅ {#alternative-using-keyed-vecs-}
 
 ```rust
 #![no_std]
@@ -497,7 +498,7 @@ impl GameContract {
 }
 ```
 
-:::tip
+<Tip>
 
 Here's a breakdown of the optimizations and benefits:
 
@@ -525,13 +526,13 @@ Here's a breakdown of the optimizations and benefits:
 
   If you need to add new types of data associated with players, you can easily extend the DataKey enum without changing the existing structure.
 
-:::
+</Tip>
 
-### 5. Use of appropriate `env.storage` mechanisms
+### 5. Use of appropriate `env.storage` mechanisms {#5-use-of-appropriate-envstorage-mechanisms}
 
 There are three types of storage mechanisms in Stellar:
 
-#### [`env.storage().persistent()`](https://docs.rs/soroban-sdk/latest/soroban_sdk/storage/struct.Storage.html#method.persistent)
+#### [`env.storage().persistent()`](https://docs.rs/soroban-sdk/latest/soroban_sdk/storage/struct.Storage.html#method.persistent) {#envstoragepersistent}
 
 Persistent storage is used to store data that needs to be retained across contract invocations. Data stored in persistent storage is maintained between contract invocations and is accessible to all contract functions. Storage for data here is intended to stay in the ledger indefinitely until explicitly deleted. Expired entries can be restored but cannot be recreated.
 
@@ -549,25 +550,25 @@ Persistent storage is used to store data that needs to be retained across contra
 
 - Data behaves as if it were stored forever but can expire and be restored.
 
-#### [`env.storage().temporary()`](https://docs.rs/soroban-sdk/latest/soroban_sdk/storage/struct.Storage.html#method.temporary)
+#### [`env.storage().temporary()`](https://docs.rs/soroban-sdk/latest/soroban_sdk/storage/struct.Storage.html#method.temporary) {#envstoragetemporary}
 
 Temporary storage is used for data that only needs to exist for a limited period of time. Entries stay in the ledger until their TTL expires: they are not cleared at the end of the contract invocation, and any function of the same contract can read them while they are live. (Contracts still cannot read data stored by other contracts.) Expired temporary entries are removed permanently and cannot be restored, but they can be recreated, potentially with different values. The shortest lifetime temporary entries can be given is itself a network setting, so check the current value rather than assuming a fixed duration.
 
-#### Use cases
+#### Use cases {#use-cases-1}
 
 - Data that only needs to exist temporarily, such as oracle data, claimable balances, and offers.
 - When data only needs to exist for a limited time and can be recreated if needed.
 - Examples: Oracle data, claimable balances, offers.
 
-#### Cost
+#### Cost {#cost-1}
 
 - Cheaper than persistent storage due to the limited lifespan of data. (Cheapest cost).
 
-#### Lifetime
+#### Lifetime {#lifetime-1}
 
 - Data exists for a predefined period and is then removed.
 
-#### [`env.storage().instance()`](https://docs.rs/soroban-sdk/latest/soroban_sdk/storage/struct.Storage.html#method.instance)
+#### [`env.storage().instance()`](https://docs.rs/soroban-sdk/latest/soroban_sdk/storage/struct.Storage.html#method.instance) {#envstorageinstance}
 
 Storage here is done for a small amount of persistent data tightly coupled with the contract instance. Data is loaded from the ledger every time the contract instance is loaded and it is limited by the ledger entry size, which is a network setting that can change; see the current value [on the Stellar Lab](https://lab.stellar.org/network-limits).
 
@@ -598,7 +599,7 @@ To optimize the size of your `wasm` binary, you can:
 
 ### 1. Use of built-in tools
 
-One way to control the size of your `wasm` binary is the `--optimize` flag of the [Stellar CLI](../../../tools/cli/stellar-cli.mdx). It rewrites the binary to remove unnecessary code and reduce its size.
+One way to control the size of your `wasm` binary is the `--optimize` flag of the [Stellar CLI](/docs/tools/cli/stellar-cli). It rewrites the binary to remove unnecessary code and reduce its size.
 
 Recent versions of the CLI run this optimization on every build, so `stellar contract build` already produces the optimized binary and no extra flag is needed. To keep the unoptimized output, for example when comparing instruction counts, pass the flag with an explicit `false`:
 
@@ -628,7 +629,7 @@ stellar contract invoke \
 
 `--cost` reports the fee the network actually charged, so it only produces output when a transaction is sent. Combining it with `--send=no` simulates the call and prints the result with no cost breakdown.
 
-Reference: [Stellar CLI Guides](../../../tools/cli/cookbook/README.mdx).
+Reference: [Stellar CLI Guides](/docs/tools/cli/cookbook).
 
 ### 2. Manual code review
 
@@ -638,7 +639,7 @@ Perform a manual code review of your smart contract to identify areas where you
 
 Use unit tests to measure the gas cost of your smart contract functions. This will help you identify functions that are consuming a lot of gas and optimize them accordingly.
 
-Also, using [simulateTransaction](../../../data/apis/rpc/api-reference/methods/simulateTransaction.mdx) rpc helper method can give you an insight of the gas cost of your contract functions.
+Also, using [simulateTransaction](../../../data/apis/rpc/api-reference/methods/simulateTransaction) rpc helper method can give you an insight of the gas cost of your contract functions.
 
 ### 4. Static analysis tools
 
diff --git a/docs/build/guides/fees/cost-analysis.mdx b/docs/build/guides/fees/cost-analysis.mdx
index b82e36590..79e59a230 100644
--- a/docs/build/guides/fees/cost-analysis.mdx
+++ b/docs/build/guides/fees/cost-analysis.mdx
@@ -1,6 +1,6 @@
 ---
 title: Analyze contract cost and efficiency
-hide_table_of_contents: true
+description: "See issue #552 for more context."
 draft: true
 ---
 
diff --git a/docs/build/guides/fees/index.mdx b/docs/build/guides/fees/index.mdx
new file mode 100644
index 000000000..bc207da00
--- /dev/null
+++ b/docs/build/guides/fees/index.mdx
@@ -0,0 +1,4 @@
+---
+title: Fees & Metering
+description: 'Fees and metering in Soroban smart contracts work differently than the fees for "regular" Stellar transactions. The Stellar network still provides cheap, accessible transaction and that now includes smart contract metering!'
+---
diff --git a/docs/build/guides/freighter/README.mdx b/docs/build/guides/freighter/README.mdx
deleted file mode 100644
index bf9a834ec..000000000
--- a/docs/build/guides/freighter/README.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: Freighter Wallet
-hide_table_of_contents: true
-sidebar_position: 70
----
-
-[Freighter](https://www.freighter.app) is a browser extension wallet provided by the Stellar Development Foundation. It provides users a way to interact with Soroban tokens directly from the web browser.
diff --git a/docs/build/guides/freighter/connect-testnet.mdx b/docs/build/guides/freighter/connect-testnet.mdx
index b24a203fc..fc00e486d 100644
--- a/docs/build/guides/freighter/connect-testnet.mdx
+++ b/docs/build/guides/freighter/connect-testnet.mdx
@@ -1,6 +1,5 @@
 ---
 title: Connect to the Testnet
-hide_table_of_contents: true
 description: Create a Stellar account on Testnet with Freighter
 ---
 
diff --git a/docs/build/guides/freighter/enable-soroban-tokens.mdx b/docs/build/guides/freighter/enable-soroban-tokens.mdx
index f78392024..b55b2e71d 100644
--- a/docs/build/guides/freighter/enable-soroban-tokens.mdx
+++ b/docs/build/guides/freighter/enable-soroban-tokens.mdx
@@ -1,6 +1,5 @@
 ---
 title: Enable Soroban tokens
-hide_table_of_contents: true
 description: Add smart contract tokens to your Freighter wallet
 ---
 
diff --git a/docs/build/guides/freighter/index.mdx b/docs/build/guides/freighter/index.mdx
new file mode 100644
index 000000000..e8e0be0e1
--- /dev/null
+++ b/docs/build/guides/freighter/index.mdx
@@ -0,0 +1,4 @@
+---
+title: Freighter Wallet
+description: "Freighter is a browser extension wallet provided by the Stellar Development Foundation. It provides users a way to interact with Soroban tokens directly from the web browser."
+---
diff --git a/docs/build/guides/freighter/prompt-to-sign-tx.mdx b/docs/build/guides/freighter/prompt-to-sign-tx.mdx
index 9675e1edd..c5f05989c 100644
--- a/docs/build/guides/freighter/prompt-to-sign-tx.mdx
+++ b/docs/build/guides/freighter/prompt-to-sign-tx.mdx
@@ -1,12 +1,11 @@
 ---
 title: Prompt Freighter to sign transactions as a JS dapp developer
-hide_table_of_contents: true
 description: Sign smart contract transactions using the Freighter browser extension
 ---
 
 If you're building a JS dapp, easily sign Soroban transactions using the [Freighter browser extension](https://www.freighter.app) and its corresponding client library [@stellar/freighter-api](https://www.npmjs.com/package/@stellar/freighter-api):
 
-1. Follow the setup instructions to [connect to the Testnet](./connect-testnet.mdx), if required during development.
+1. Follow the setup instructions to [connect to the Testnet](./connect-testnet), if required during development.
 
 2. Now, you can use the `signTransaction` [method](https://docs.freighter.app/docs/guide/usingFreighterWebApp) from `@stellar/freighter-api` in your dapp to sign Soroban XDRs using the account in Freighter.
 
diff --git a/docs/build/guides/freighter/send-token-payments.mdx b/docs/build/guides/freighter/send-token-payments.mdx
index 00d21158c..a4e2ebae7 100644
--- a/docs/build/guides/freighter/send-token-payments.mdx
+++ b/docs/build/guides/freighter/send-token-payments.mdx
@@ -1,6 +1,5 @@
 ---
 title: Send Soroban token payments
-hide_table_of_contents: true
 description: Send a smart contract token payment directly from Freighter
 ---
 
diff --git a/docs/build/guides/freighter/sign-auth-entries.mdx b/docs/build/guides/freighter/sign-auth-entries.mdx
index e7f204170..3988f1cc8 100644
--- a/docs/build/guides/freighter/sign-auth-entries.mdx
+++ b/docs/build/guides/freighter/sign-auth-entries.mdx
@@ -1,9 +1,8 @@
 ---
 title: Sign authorization entries
-hide_table_of_contents: true
 description: Use Freighter's API to sign an authorization entry
 ---
 
-In order to take advantage of [contract authorization](../../../learn/fundamentals/contract-development/authorization.mdx), you can use Freighter's API to sign an authorization entry. A good example of how signing an authorization entry works can be found in the [`authorizeEntry` helper of `stellar-sdk`](https://github.com/stellar/js-stellar-base/blob/e3d6fc3351e7d242b374c7c6057668366364a279/src/auth.js#L97).
+In order to take advantage of [contract authorization](../../../learn/fundamentals/contract-development/authorization), you can use Freighter's API to sign an authorization entry. A good example of how signing an authorization entry works can be found in the [`authorizeEntry` helper of `stellar-sdk`](https://github.com/stellar/js-stellar-base/blob/e3d6fc3351e7d242b374c7c6057668366364a279/src/auth.js#L97).
 
 Like in the helper, you can construct a [`HashIdPreimageSorobanAuthorization`](https://github.com/stellar/js-stellar-base/blob/a9567e5843760bfb6a8b786592046aee4c9d38b2/types/next.d.ts#L6895) and use the xdr representation of that structure to call `await freighterApi.signAuthEntry(preimageXdr)`. This call will return a `Buffer` of the signed hash of the `HashIdPreimageSorobanAuthorization` passed in, which can then be used to submit to the network during a contract authorization workflow.
diff --git a/docs/build/guides/freighter/sign-soroban-xdrs.mdx b/docs/build/guides/freighter/sign-soroban-xdrs.mdx
index d4dfcd5e1..c6b7d00d8 100644
--- a/docs/build/guides/freighter/sign-soroban-xdrs.mdx
+++ b/docs/build/guides/freighter/sign-soroban-xdrs.mdx
@@ -1,6 +1,5 @@
 ---
 title: Sign Soroban XDRs
-hide_table_of_contents: true
 description: Sign smart contract XDRs using dapps integrated with Freighter
 ---
 
diff --git a/docs/build/guides/index.mdx b/docs/build/guides/index.mdx
new file mode 100644
index 000000000..612ff516e
--- /dev/null
+++ b/docs/build/guides/index.mdx
@@ -0,0 +1,6 @@
+---
+title: How-To Guides
+description: Here you will find really useful guides
+---
+
+This section provides step-by-step instructions to help users complete specific tasks associated with developing on Stellar. These tasks can include instructions for goals related to writing contracts, interacting with contracts, building applications, using Stellar operations, setting up infrastructure, and more.
diff --git a/docs/build/guides/rpc/README.mdx b/docs/build/guides/rpc/README.mdx
deleted file mode 100644
index 621fad9f3..000000000
--- a/docs/build/guides/rpc/README.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: RPC
-hide_table_of_contents: true
-sidebar_position: 75
----
-
-Using and interacting with the Stellar RPC is an important part of the smart contract development lifecycle. Read more about the RPC in our [RPC documentation](../../../data/apis/rpc/README.mdx).
diff --git a/docs/build/guides/rpc/generate-ledger-keys-python.mdx b/docs/build/guides/rpc/generate-ledger-keys-python.mdx
index 1250ec110..2413c4cd1 100644
--- a/docs/build/guides/rpc/generate-ledger-keys-python.mdx
+++ b/docs/build/guides/rpc/generate-ledger-keys-python.mdx
@@ -1,6 +1,5 @@
 ---
 title: Generate ledger key parameters with a symbol key using the Python SDK
-hide_table_of_contents: true
 description: Generate ledger key parameters with a symbol key using the Python SDK
 ---
 
@@ -28,4 +27,4 @@ print(
 )
 ```
 
-[`increment` example contract]: ../../smart-contracts/getting-started/storing-data.mdx
+[`increment` example contract]: ../../smart-contracts/getting-started/storing-data
diff --git a/docs/build/guides/rpc/index.mdx b/docs/build/guides/rpc/index.mdx
new file mode 100644
index 000000000..6a4536d7f
--- /dev/null
+++ b/docs/build/guides/rpc/index.mdx
@@ -0,0 +1,6 @@
+---
+title: RPC
+description: "Using and interacting with the Stellar RPC is an important part of the smart contract development lifecycle."
+---
+
+Read more about the RPC in our [RPC documentation](/docs/data/apis/rpc).
diff --git a/docs/build/guides/rpc/retrieve-contract-code-js.mdx b/docs/build/guides/rpc/retrieve-contract-code-js.mdx
index 1fff632ca..6af92be26 100644
--- a/docs/build/guides/rpc/retrieve-contract-code-js.mdx
+++ b/docs/build/guides/rpc/retrieve-contract-code-js.mdx
@@ -1,6 +1,5 @@
 ---
 title: Retrieve a contract code ledger entry using the JavaScript SDK
-hide_table_of_contents: true
 description: Retrieve a contract code ledger entry using the JavaScript SDK
 ---
 
diff --git a/docs/build/guides/rpc/retrieve-contract-code-python.mdx b/docs/build/guides/rpc/retrieve-contract-code-python.mdx
index 48a463d54..1d84078d4 100644
--- a/docs/build/guides/rpc/retrieve-contract-code-python.mdx
+++ b/docs/build/guides/rpc/retrieve-contract-code-python.mdx
@@ -1,6 +1,5 @@
 ---
 title: Retrieve a contract code ledger entry using the Python SDK
-hide_table_of_contents: true
 description: Retrieve a contract code ledger entry using the Python SDK
 ---
 
diff --git a/docs/build/guides/rpc/self-deploy-rpc.mdx b/docs/build/guides/rpc/self-deploy-rpc.mdx
index f97c84c98..3b3e45107 100644
--- a/docs/build/guides/rpc/self-deploy-rpc.mdx
+++ b/docs/build/guides/rpc/self-deploy-rpc.mdx
@@ -1,6 +1,6 @@
 ---
 title: Self-deploy and use your own RPC instance
-hide_table_of_contents: true
+description: "Placeholder text goes here."
 draft: true
 ---
 
diff --git a/docs/build/guides/rpc/use-public-rpc.mdx b/docs/build/guides/rpc/use-public-rpc.mdx
index 70069fb34..674912515 100644
--- a/docs/build/guides/rpc/use-public-rpc.mdx
+++ b/docs/build/guides/rpc/use-public-rpc.mdx
@@ -1,6 +1,6 @@
 ---
 title: Make use of a public RPC instance
-hide_table_of_contents: true
+description: "Placeholder text goes here."
 draft: true
 ---
 
diff --git a/docs/build/guides/storage/README.mdx b/docs/build/guides/storage/README.mdx
deleted file mode 100644
index 53df01613..000000000
--- a/docs/build/guides/storage/README.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: Contract Storage
-hide_table_of_contents: true
-sidebar_position: 30
----
-
-Smart contract storage is available to affordably accommodate a wide range of uses. Learn more in the [state archival section](../../../learn/fundamentals/contract-development/storage/state-archival.mdx).
diff --git a/docs/build/guides/storage/choose-type.mdx b/docs/build/guides/storage/choose-type.mdx
index dcb41ff15..249ae8b2f 100644
--- a/docs/build/guides/storage/choose-type.mdx
+++ b/docs/build/guides/storage/choose-type.mdx
@@ -1,6 +1,6 @@
 ---
 title: Choose the right storage type for your use-case
-hide_table_of_contents: true
+description: "Placeholder text goes here."
 draft: true
 ---
 
diff --git a/docs/build/guides/storage/choosing-the-right-storage.mdx b/docs/build/guides/storage/choosing-the-right-storage.mdx
index 2cf7a4882..929f135ba 100644
--- a/docs/build/guides/storage/choosing-the-right-storage.mdx
+++ b/docs/build/guides/storage/choosing-the-right-storage.mdx
@@ -1,6 +1,5 @@
 ---
 title: How to choose the right storage type for your use case
-hide_table_of_contents: true
 description: This guide walks you through choosing the most suitable storage type for your use case and how to implement it
 ---
 
@@ -28,13 +27,13 @@ State archival is a special mechanism defined by the Stellar protocol that ensur
 
 TTL also may be extended however many times are necessary, for a fee.
 
-Read more about state archival [here](../../../learn/fundamentals/contract-development/storage/state-archival.mdx).
+Read more about state archival [here](../../../learn/fundamentals/contract-development/storage/state-archival).
 
 ## Persistent storage
 
 This storage type is used for storing data on the network over an indefinitely long time period.
 
-For persistent storage, when the TTL reaches zero, the entry is moved to the archival storage. It can then be restored when needed — usually [automatically](../../../learn/fundamentals/contract-development/storage/state-archival.mdx#contract-data-automatic-restoration), by including the entry in a transaction's restore list (which transaction simulation typically populates for you), or manually using the `RestoreFootprintOp` operation.
+For persistent storage, when the TTL reaches zero, the entry is moved to the archival storage. It can then be restored when needed — usually [automatically](../../../learn/fundamentals/contract-development/storage/state-archival#contract-data-automatic-restoration), by including the entry in a transaction's restore list (which transaction simulation typically populates for you), or manually using the `RestoreFootprintOp` operation.
 
 Persistent storage is the default storage type use-case-wise. Instance and temporary storage are only useful for the specific use cases described in the respective sections. Stellar protocol also uses persistent storage to store the contracts and their Wasm executables, so that they always can be accessed or restored.
 
@@ -138,19 +137,18 @@ The benefit of temporary storage is the smaller cost and the ability to set a ve
 
 Temporary storage is suitable for data that is only necessary for a relatively short and well-defined time period. 'Well-defined' here means that when creating an entry, the contract should be able to define its maximum necessary TTL.
 
-:::caution
+<Warning>
 
 While TTL for the temporary data can be extended, it is unsafe to rely on the extensions to preserve data. There is always a risk of losing temporary data. Only the TTL extension made when the entry is created is guaranteed to happen.
 
-:::
-
-:::caution
+</Warning>
+<Warning>
 
 It is also unsafe to rely on an entry expiring as it can be extended by anyone. When a time bound has to be enforced, always include it in the data as well.
 
 **Temporary storage is a cost optimization, it's not a mechanism of enforcing any time-based invariants.**
 
-:::
+</Warning>
 
 Temporary storage is best suited for easily replaceable data, or data that is only relevant within a certain time period. For example, oracle price feed data that is only relevant for a few minutes, or limited time authorizations such as token allowances, session tokens, auctions, timelocks, etc. Nonces for the Soroban signatures are also stored in the temporary storage, at least until the signature itself expires.
 
@@ -179,14 +177,7 @@ pub struct AuctionContract;
 #[contractimpl]
 impl AuctionContract {
     // This function lets a user place a bid that lives only until the auction ends.
-    pub fn place_bid(env: Env, user: Address, bid: i128, bid_expiration_ledger_seq: u32) {
-        user.require_auth();
-        let bid_key = DataKey::Bid(user.clone());
-
-        // Store the bid in the temporary storage.
-        env.storage().temporary().set(&bid_key, &Bid {
-            value: bid,
-            expiration_ledger_seq: bid_expiration_ledger_seq,
+@@ -185,29 +190,28 @@ impl AuctionContract {
         });
         // Compute the TTL that the bid requires.
         let bid_ttl = bid_expiration_ledger_seq
@@ -212,6 +203,7 @@ impl AuctionContract {
                 // order to trick our contract, so return 0.
                 0
             }
+
         } else {
             // There is no bid for the user - it either hasn't existed at all,
             // or has been removed from the temporary storage. In either case,
diff --git a/docs/build/guides/storage/index.mdx b/docs/build/guides/storage/index.mdx
new file mode 100644
index 000000000..cc96726dd
--- /dev/null
+++ b/docs/build/guides/storage/index.mdx
@@ -0,0 +1,6 @@
+---
+title: Contract Storage
+description: "Smart contract storage is available to affordably accommodate a wide range of uses."
+---
+
+Learn more in the [state archival section](/docs/learn/fundamentals/contract-development/storage/state-archival).
diff --git a/docs/build/guides/storage/migrate-contract-storage.mdx b/docs/build/guides/storage/migrate-contract-storage.mdx
index de752982a..ecee10d10 100644
--- a/docs/build/guides/storage/migrate-contract-storage.mdx
+++ b/docs/build/guides/storage/migrate-contract-storage.mdx
@@ -1,6 +1,5 @@
 ---
 title: Migrate contract storage data when upgrading data structures
-hide_table_of_contents: true
 description: Use the version marker pattern to safely read and migrate stored data when a contract upgrade changes a data structure
 ---
 
@@ -142,7 +141,7 @@ pub enum DataKey {
 
 Each logical record occupies two storage slots. Because the version is stored per-record rather than globally, each entry is independently versioned. There is no all-or-nothing upgrade requirement.
 
-### Reading with version awareness
+### Reading with version awareness {#reading-with-version-awareness-1}
 
 Before decoding a storage entry, read its version marker. Use `unwrap_or(1)` to handle entries that were written before versioning was introduced. The absence of a version key is itself a signal that the entry is version 1:
 
@@ -162,7 +161,7 @@ fn read_data(env: &Env, id: u32) -> DataV2 {
 }
 ```
 
-### Writing always uses the current version
+### Writing always uses the current version {#writing-always-uses-the-current-version-1}
 
 Every write stamps the entry with the current version number. An entry that was originally `DataV1` will carry a `DataVersion` marker of `2` the next time it is written back:
 
@@ -211,13 +210,13 @@ Eager migration is rarely practical for large datasets on Soroban. Each rewrite
 
 Eager migration is occasionally appropriate when the total number of records is small and known in advance (for example, a fixed registry of a few dozen entries), or when you need to permanently drop old version branches from the read path.
 
-:::caution
+<Warning>
 
 Never remove a version branch from `read_data` while old entries of that version can still exist on the ledger. Doing so will cause any remaining old entries to trap when accessed.
 
-:::
+</Warning>
 
-### Testing migrations
+### Testing migrations {#testing-migrations-1}
 
 Testing data migration requires simulating state written by an old contract version and verifying that the new contract reads it correctly.
 
@@ -311,11 +310,11 @@ The three test cases cover the three states a record can be in after an upgrade:
 
 The techniques presented here may not immediately seem necessary. The "apparent" obvious solutions may be to programmatically handle the discrepancies in data types, rather than modify any of the underlying data structures, or adjust how the storage entries are read or written.
 
-:::warning
+<Warning>
 
 We've outlined a couple of the more "obvious" approaches to this problem, to illustrate _why_ these anti-patterns are not ideal. Please do not use the following code snippets as examples to be emulated. Rather, read the context of them, and learn why to avoid them.
 
-:::
+</Warning>
 
 ### Approach 1: Read old entries directly with the new type
 
diff --git a/docs/build/guides/storage/storage-strategies.mdx b/docs/build/guides/storage/storage-strategies.mdx
index 3893d518f..221cf2440 100644
--- a/docs/build/guides/storage/storage-strategies.mdx
+++ b/docs/build/guides/storage/storage-strategies.mdx
@@ -1,20 +1,22 @@
 ---
 title: Storage strategies in production contracts
-sidebar_label: Storage strategies
+sidebarTitle: Storage strategies
 description: Twelve storage layout strategies for Soroban contracts, with diagrams, a decision path, and a cheatsheet
 ---
 
-import StorageDiagram from "@site/src/components/StorageStrategies";
+import { StorageDiagram } from "/snippets/storage-diagram.jsx";
 
 How experienced teams lay out contract state on Stellar — from a first counter to protocol-scale data layouts. The strategies below are ordered from simplest to most complex and grounded in current production contracts and official examples. They are not mutually exclusive: each one applies to a _piece_ of state, not to a whole contract, and production contracts routinely compose several — a single lending pool keeps its config in instance storage (Strategy 1), one entry per user position (Strategy 2), and a bounded reserve list (Strategy 6). Use the [decision path](#decision-path-composing-strategies) to pick a strategy per piece of state.
 
-:::info[Protocol and limits snapshot]
+<Info>
+
+**Protocol and limits snapshot**
 
 **Checked:** July 20, 2026. **Protocol:** Stellar Protocol 27.
 
 Mainnet resource limits are network settings that validators can change, and the strategy list itself can grow with the ecosystem. Verify any limit quoted here — such as the 200 disk-read-entry and 200 write-entry caps per transaction — with `stellar network settings --network mainnet` or on [Stellar Laboratory](https://lab.stellar.org/network-limits). The current values are tabulated in the [appendix](#appendix-mainnet-limits).
 
-:::
+</Info>
 
 ## Why storage is the hard part
 
@@ -109,7 +111,7 @@ pub fn deposit(e: Env, from: Address, amount: i128) {
 - [`blend-capital/blend-contracts-v2`](https://github.com/blend-capital/blend-contracts-v2) — [`pool/src/storage.rs`](https://github.com/blend-capital/blend-contracts-v2/blob/ba22b487b2c5057a4ecc28b05b5193c28e4bd117/pool/src/storage.rs#L208-L223): admin, backstop, config under `Symbol` keys.
 - [`OpenZeppelin/stellar-contracts`](https://github.com/OpenZeppelin/stellar-contracts) — fungible-token metadata in [`packages/tokens/src/fungible/storage.rs`](https://github.com/OpenZeppelin/stellar-contracts/blob/34fd71403d59dfc0947fcede227313f37dd23635/packages/tokens/src/fungible/storage.rs#L33-L126) and the ownable `Owner` key in [`packages/access/src/ownable/storage.rs`](https://github.com/OpenZeppelin/stellar-contracts/blob/34fd71403d59dfc0947fcede227313f37dd23635/packages/access/src/ownable/storage.rs#L13-L51) use instance storage.
 
-## Strategy 2: One entry per entity — keyed by a `DataKey` enum
+## Strategy 2: One entry per entity — keyed by a `DataKey` enum {#strategy-2-one-entry-per-entity--keyed-by-a-datakey-enum}
 
 _persistent · O(1) lookup · independently addressed entries · no enumeration_
 
@@ -152,7 +154,7 @@ Note the two idioms: **absent-means-default** (don't create entries to store zer
 - [`OpenZeppelin/stellar-contracts`](https://github.com/OpenZeppelin/stellar-contracts) — fungible [`Balance(Address)`](https://github.com/OpenZeppelin/stellar-contracts/blob/34fd71403d59dfc0947fcede227313f37dd23635/packages/tokens/src/fungible/storage.rs#L34-L60) entries are persistent and extended explicitly; the smart account keeps [one persistent entry per signer](https://github.com/OpenZeppelin/stellar-contracts/blob/34fd71403d59dfc0947fcede227313f37dd23635/packages/accounts/src/smart_account/storage.rs#L36-L41) (`SignerData(u32)`, deduplicated through a `SignerLookup` hash entry) and [extends the TTL on every read](https://github.com/OpenZeppelin/stellar-contracts/blob/34fd71403d59dfc0947fcede227313f37dd23635/packages/accounts/src/smart_account/storage.rs#L1421-L1432).
 - [`blend-capital/blend-contracts-v2`](https://github.com/blend-capital/blend-contracts-v2) — one persistent [`Positions(Address)`](https://github.com/blend-capital/blend-contracts-v2/blob/ba22b487b2c5057a4ecc28b05b5193c28e4bd117/pool/src/storage.rs#L176-L196) entry per user and separate [`ResConfig(Address)`](https://github.com/blend-capital/blend-contracts-v2/blob/ba22b487b2c5057a4ecc28b05b5193c28e4bd117/pool/src/storage.rs#L338-L370) and [`ResData(Address)`](https://github.com/blend-capital/blend-contracts-v2/blob/ba22b487b2c5057a4ecc28b05b5193c28e4bd117/pool/src/storage.rs#L432-L456) entries per reserve.
 
-## Strategy 3: Composite keys — multi-dimensional lookups
+## Strategy 3: Composite keys — multi-dimensional lookups {#strategy-3-composite-keys--multi-dimensional-lookups}
 
 _persistent · temporary · O(1) · serialized ledger key ≤ 250 B_
 
@@ -246,7 +248,7 @@ The TTL alone is not the whole guarantee, for two reasons: the network enforces
 - [`blend-capital/blend-contracts-v2`](https://github.com/blend-capital/blend-contracts-v2) — [auctions](https://github.com/blend-capital/blend-contracts-v2/blob/ba22b487b2c5057a4ecc28b05b5193c28e4bd117/pool/src/storage.rs#L637-L647), [queued reserve configs](https://github.com/blend-capital/blend-contracts-v2/blob/ba22b487b2c5057a4ecc28b05b5193c28e4bd117/pool/src/storage.rs#L401-L408), and `ProposedAdmin` use temporary storage; [`ProposedAdmin` is initialized with a 10-day TTL](https://github.com/blend-capital/blend-contracts-v2/blob/ba22b487b2c5057a4ecc28b05b5193c28e4bd117/pool/src/storage.rs#L239-L247).
 - [`OpenZeppelin/stellar-contracts`](https://github.com/OpenZeppelin/stellar-contracts) — [fungible allowances](https://github.com/OpenZeppelin/stellar-contracts/blob/34fd71403d59dfc0947fcede227313f37dd23635/packages/tokens/src/fungible/storage.rs#L18-L20) and pending role or ownership transfers use temporary storage and enforce a [stored `live_until_ledger`](https://github.com/OpenZeppelin/stellar-contracts/blob/34fd71403d59dfc0947fcede227313f37dd23635/packages/access/src/role_transfer/storage.rs#L132-L134).
 
-## Strategy 5: TTL management — bump-on-access
+## Strategy 5: TTL management — bump-on-access {#strategy-5-ttl-management--bump-on-access}
 
 _persistent · instance · rent tracks usage_
 
@@ -299,7 +301,7 @@ The same threshold → bump call exists on temporary storage and suits regenerab
 - [`blend-capital/blend-contracts-v2`](https://github.com/blend-capital/blend-contracts-v2) — [`get_persistent_default()`](https://github.com/blend-capital/blend-contracts-v2/blob/ba22b487b2c5057a4ecc28b05b5193c28e4bd117/backstop/src/storage.rs#L97-L112) combines reads with explicit extensions.
 - [`soroswap/core`](https://github.com/soroswap/core) — [`get_persistent_extend_or_error()`](https://github.com/soroswap/core/blob/bb90a65556d8eee0dc698ac75de0f280e547fedc/contracts/factory/src/storage.rs#L36-L49) reads and extends in one helper.
 
-## Strategy 6: Bounded collections — a capped Vec or Map in one entry
+## Strategy 6: Bounded collections — a capped Vec or Map in one entry {#strategy-6-bounded-collections--a-capped-vec-or-map-in-one-entry}
 
 _persistent · 1 read to iterate · hard cap in code_
 
@@ -340,7 +342,7 @@ The list entry stores only _identifiers_; per-item detail lives in its own entry
 
 - [`blend-capital/blend-contracts-v2`](https://github.com/blend-capital/blend-contracts-v2) — the pool stores reserve identifiers in one persistent [`ResList`](https://github.com/blend-capital/blend-contracts-v2/blob/ba22b487b2c5057a4ecc28b05b5193c28e4bd117/pool/src/storage.rs#L480-L495) entry and [rejects additions beyond 30 reserves](https://github.com/blend-capital/blend-contracts-v2/blob/ba22b487b2c5057a4ecc28b05b5193c28e4bd117/pool/src/constants.rs#L16). Reserve details remain in per-asset entries.
 
-## Strategy 7: Pack vs. split — group state by access pattern
+## Strategy 7: Pack vs. split — group state by access pattern {#strategy-7-pack-vs-split--group-state-by-access-pattern}
 
 _persistent · size the entry to the transaction · split hot from cold_
 
@@ -385,7 +387,7 @@ Blend's reserves show the split side of the same trade-off: each asset's state i
 - Packed: Blend stores a user's liabilities, collateral, and supply maps in one [`Positions(Address)`](https://github.com/blend-capital/blend-contracts-v2/blob/ba22b487b2c5057a4ecc28b05b5193c28e4bd117/pool/src/pool/user.rs#L11-L14) entry; backstop shares and queued withdrawals share one [`UserBalance`](https://github.com/blend-capital/blend-contracts-v2/blob/ba22b487b2c5057a4ecc28b05b5193c28e4bd117/backstop/src/backstop/user.rs#L19-L21) entry; OZ's smart account packs a rule's metadata, signer IDs, and policy IDs into one [`ContextRuleEntry`](https://github.com/OpenZeppelin/stellar-contracts/blob/34fd71403d59dfc0947fcede227313f37dd23635/packages/accounts/src/smart_account/storage.rs#L56-L71), cutting auth-check reads from three to one.
 - Split: Blend [`ResConfig`/`ResData`](https://github.com/blend-capital/blend-contracts-v2/blob/ba22b487b2c5057a4ecc28b05b5193c28e4bd117/pool/src/storage.rs#L126-L139) pairs; OZ fungible [`Balance` vs `Allowance` vs `Meta`](https://github.com/OpenZeppelin/stellar-contracts/blob/34fd71403d59dfc0947fcede227313f37dd23635/packages/tokens/src/fungible/storage.rs#L33-L37); every token's balance-per-entry layout.
 
-## Strategy 8: Enumeration — build the index yourself
+## Strategy 8: Enumeration — build the index yourself {#strategy-8-enumeration--build-the-index-yourself}
 
 _persistent · O(1) maintain · pageable reads_
 
@@ -438,7 +440,7 @@ O(1) counts steps, not ledger I/O: the swap-and-pop above writes four entries fo
 - (a) [`soroswap/core`](https://github.com/soroswap/core) — [`contracts/factory/src/storage.rs`](https://github.com/soroswap/core/blob/bb90a65556d8eee0dc698ac75de0f280e547fedc/contracts/factory/src/storage.rs#L11-L19), the dual-index registry.
 - (b) [`OpenZeppelin/stellar-contracts`](https://github.com/OpenZeppelin/stellar-contracts) — [access-control role enumeration](https://github.com/OpenZeppelin/stellar-contracts/blob/34fd71403d59dfc0947fcede227313f37dd23635/packages/access/src/access_control/storage.rs#L21-L29) and [`packages/tokens/src/non_fungible/extensions/enumerable/storage.rs`](https://github.com/OpenZeppelin/stellar-contracts/blob/34fd71403d59dfc0947fcede227313f37dd23635/packages/tokens/src/non_fungible/extensions/enumerable/storage.rs#L39-L45) use forward and reverse indexes and move the last item into a removed slot.
 
-## Strategy 9: Pull, don't push — lazy settlement for unbounded holders
+## Strategy 9: Pull, don't push — lazy settlement for unbounded holders {#strategy-9-pull-dont-push--lazy-settlement-for-unbounded-holders}
 
 _persistent · O(1) per user · cumulative index_
 
@@ -483,7 +485,7 @@ The global `index` answers one question — how much has a single share earned s
 
 - [`blend-capital/blend-contracts-v2`](https://github.com/blend-capital/blend-contracts-v2) — [pool](https://github.com/blend-capital/blend-contracts-v2/blob/ba22b487b2c5057a4ecc28b05b5193c28e4bd117/pool/src/storage.rs#L84-L98) and [backstop](https://github.com/blend-capital/blend-contracts-v2/blob/ba22b487b2c5057a4ecc28b05b5193c28e4bd117/backstop/src/storage.rs#L33-L51) emissions each keep shared emission data and separate per-user emission data; the settlement delta is computed in [`distributor.rs`](https://github.com/blend-capital/blend-contracts-v2/blob/ba22b487b2c5057a4ecc28b05b5193c28e4bd117/pool/src/emissions/distributor.rs#L200-L207).
 
-## Strategy 10: Checkpoints — read state as of a past ledger
+## Strategy 10: Checkpoints — read state as of a past ledger {#strategy-10-checkpoints--read-state-as-of-a-past-ledger}
 
 _persistent · O(1) append · O(log n) historical read_
 
@@ -523,7 +525,7 @@ Checkpoints before the tail are never rewritten — that is what makes binary se
 - [`OpenZeppelin/stellar-contracts`](https://github.com/OpenZeppelin/stellar-contracts) — the votes module keeps [per-delegate and total-supply checkpoint series](https://github.com/OpenZeppelin/stellar-contracts/blob/34fd71403d59dfc0947fcede227313f37dd23635/packages/governance/src/votes/storage.rs#L25-L66), [collapses same-ledger writes into the tail](https://github.com/OpenZeppelin/stellar-contracts/blob/34fd71403d59dfc0947fcede227313f37dd23635/packages/governance/src/votes/storage.rs#L444-L489), and answers past-power queries with a [binary search](https://github.com/OpenZeppelin/stellar-contracts/blob/34fd71403d59dfc0947fcede227313f37dd23635/packages/governance/src/votes/storage.rs#L367-L400). The Governor applies the same shape to [quorum changes](https://github.com/OpenZeppelin/stellar-contracts/blob/34fd71403d59dfc0947fcede227313f37dd23635/packages/governance/src/governor/storage.rs#L1088-L1113), so raising the quorum today does not retroactively affect proposals voted under the old one.
 - [`Phoenix-Protocol-Group/phoenix-contracts`](https://github.com/Phoenix-Protocol-Group/phoenix-contracts) — the stake contract stores each reward token's [distribution history as one persistent `Map<u64, u128>` keyed by day](https://github.com/Phoenix-Protocol-Group/phoenix-contracts/blob/aa9bfc000166e3ccdc30281b5181bbd8046fd35d/contracts/stake/src/distribution.rs#L11-L41) — the single-entry variant: simpler while the history is short, but every update rewrites the whole map, which grows for as long as rewards run.
 
-## Strategy 11: Merkle roots and derived state — replace storage with verification
+## Strategy 11: Merkle roots and derived state — replace storage with verification {#strategy-11-merkle-roots-and-derived-state--replace-storage-with-verification}
 
 _one 32-byte root · derived IDs · sentinel values_
 
@@ -563,7 +565,7 @@ What must stay on-chain can still shrink to a **sentinel**. The Governor's compa
 - [`stellar/soroban-examples`](https://github.com/stellar/soroban-examples) — [`merkle_distribution/src/lib.rs`](https://github.com/stellar/soroban-examples/blob/14c069cccf85e552d4d80c8122e00a61a5723aae/merkle_distribution/src/lib.rs#L19-L20) stores the root and `Claimed(index)` flags in instance storage; its claim count is bounded by the instance-entry size.
 - [`OpenZeppelin/stellar-contracts`](https://github.com/OpenZeppelin/stellar-contracts) — its reusable [`merkle_distributor`](https://github.com/OpenZeppelin/stellar-contracts/blob/34fd71403d59dfc0947fcede227313f37dd23635/packages/contract-utils/src/merkle_distributor/storage.rs#L13-L18) module is the unbounded-distribution variant: one persistent [`Claimed(u32)`](https://github.com/OpenZeppelin/stellar-contracts/blob/34fd71403d59dfc0947fcede227313f37dd23635/packages/contract-utils/src/merkle_distributor/storage.rs#L18) entry per claimed index. [Governor proposal IDs](https://github.com/OpenZeppelin/stellar-contracts/blob/34fd71403d59dfc0947fcede227313f37dd23635/packages/governance/src/governor/storage.rs#L771-L783) and [Timelock operation IDs](https://github.com/OpenZeppelin/stellar-contracts/blob/34fd71403d59dfc0947fcede227313f37dd23635/packages/governance/src/timelock/storage.rs#L403-L413) are derived from caller-supplied inputs; the Timelock stores [one ledger-number sentinel per operation](https://github.com/OpenZeppelin/stellar-contracts/blob/34fd71403d59dfc0947fcede227313f37dd23635/packages/governance/src/timelock/mod.rs#L353-L357).
 
-## Strategy 12: Scale out — contract-per-entity via factory
+## Strategy 12: Scale out — contract-per-entity via factory {#strategy-12-scale-out--contract-per-entity-via-factory}
 
 _one contract per entity · own instance & TTLs · factory registry_
 
@@ -637,7 +639,7 @@ For each piece of state, answer every question in order — steps 1–3 pick the
 | Oracle prices / regenerable caches | temporary | loss is cheap, freshness is the point |
 | Anything derivable (states, IDs, tallies pre-first-vote) | _none_ | recompute; hash-commit; lazy-create |
 
-### Pattern → complexity
+### Pattern → complexity {#pattern--complexity}
 
 Every pattern in this guide, costed per operation — use it to compare finalists once the [decision path](#decision-path-composing-strategies) has produced a shortlist. Complexity counts steps inside the contract, not ledger I/O: an O(1) swap-and-pop still writes up to four entries, and every entry touched counts toward the per-transaction read and write caps. **Ledger entries per item** is the rent side — how many entries the pattern keeps alive for each item it stores. An "n/a" cell means the pattern has no such operation.
 
@@ -701,11 +703,11 @@ Every pattern in this guide, costed per operation — use it to compare finalist
 | Min TTL: persistent/instance create or restore | 2,073,600 ledgers ≈ 120 d |
 | Min TTL: temporary create                      |      17,280 ledgers ≈ 1 d |
 
-:::info
+<Info>
 
 Two numbers to remember: **`17,280` ledgers is about one day at today's ~5-second target close time**, and **64 KiB is the whole contract-data entry limit**. Close time is a network setting, so day-based TTL constants are approximations, not wall-clock guarantees. Many codebases define `DAY_IN_LEDGERS` for readability. Keep entries well below the size limit because large values increase read, write, and rent costs.
 
-:::
+</Info>
 
 ## Repositories reviewed
 
@@ -722,4 +724,4 @@ Two numbers to remember: **`17,280` ledgers is about one day at today's ~5-secon
 | [CometDEX/comet-contracts-v1](https://github.com/CometDEX/comet-contracts-v1) | Weighted AMM | Persistent LP-token balances, temporary composite-key allowances, and a factory pool registry |
 | [FredericRezeau/soroban-kit](https://github.com/FredericRezeau/soroban-kit) | Macro library | Type-safe storage macros that select instance, persistent, or temporary storage and bind key/value types |
 
-**Methodology.** Network values were read with `stellar network settings --network mainnet` and cross-checked against the Mainnet constants rendered by [Stellar Laboratory](https://lab.stellar.org/network-limits) on 2026-07-20. Repository claims above were checked against each repository's current default branch. Further reading: [state archival](../../../learn/fundamentals/contract-development/storage/state-archival.mdx) · [persisting data](../../../learn/fundamentals/contract-development/storage/persisting-data.mdx).
+**Methodology.** Network values were read with `stellar network settings --network mainnet` and cross-checked against the Mainnet constants rendered by [Stellar Laboratory](https://lab.stellar.org/network-limits) on 2026-07-20. Repository claims above were checked against each repository's current default branch. Further reading: [state archival](../../../learn/fundamentals/contract-development/storage/state-archival) · [persisting data](../../../learn/fundamentals/contract-development/storage/persisting-data).
diff --git a/docs/build/guides/storage/use-instance.mdx b/docs/build/guides/storage/use-instance.mdx
index 9ef5f28d0..1ed08e62b 100644
--- a/docs/build/guides/storage/use-instance.mdx
+++ b/docs/build/guides/storage/use-instance.mdx
@@ -1,18 +1,17 @@
 ---
 title: Use instance storage in a contract
-hide_table_of_contents: true
 description: Instance storage has an archival TTL that is tied to the contract instance itself
 ---
 
 Under the hood, instance storage is exactly like persistent storage. The only difference is that anything stored in instance storage has an archival TTL that is tied to the contract instance itself. So, if a contract is live and available, the instance storage is guaranteed to be so, too.
 
-Instance storage is really useful for global contract data that is shared among all users of the contract (token administrator, for example). From the [token example contract](../../smart-contracts/example-contracts/tokens.mdx), the helper functions to set and retrieve the admininistrator address are basically just wrappers surrounding the one Admin ledger entry.
+Instance storage is really useful for global contract data that is shared among all users of the contract (token administrator, for example). From the [token example contract](../../smart-contracts/example-contracts/tokens), the helper functions to set and retrieve the admininistrator address are basically just wrappers surrounding the one Admin ledger entry.
 
-:::caution
+<Warning>
 
 It should be noted that _every_ piece of data stored in `instance()` storage is retrieved from the ledger _every_ time the contract is invoked. Even if the invoked function does not interact with any ledger data at all. This can lead to more expensive (computationally and financially) function invocations if the stored data grows over time. Choose judiciously which bits of data actually belong in the instance storage, and which should be kept in persistent storage.
 
-:::
+</Warning>
 
 ```rust
 pub fn has_administrator(e: &Env) -> bool {
diff --git a/docs/build/guides/storage/use-persistent.mdx b/docs/build/guides/storage/use-persistent.mdx
index 595fb2f16..ae908964a 100644
--- a/docs/build/guides/storage/use-persistent.mdx
+++ b/docs/build/guides/storage/use-persistent.mdx
@@ -1,6 +1,5 @@
 ---
 title: Use persistent storage in a contract
-hide_table_of_contents: true
 description: Persistent storage can be useful for ledger entrys that are not common across every user of the contract instance
 ---
 
diff --git a/docs/build/guides/storage/use-temporary.mdx b/docs/build/guides/storage/use-temporary.mdx
index f27dbbc77..cfc0205a0 100644
--- a/docs/build/guides/storage/use-temporary.mdx
+++ b/docs/build/guides/storage/use-temporary.mdx
@@ -1,6 +1,5 @@
 ---
 title: Use temporary storage in a contract
-hide_table_of_contents: true
 description: Temporary storage is useful for a contract to store data that can quickly become irrelevant or out-dated
 ---
 
diff --git a/docs/build/guides/testing/README.mdx b/docs/build/guides/testing/README.mdx
deleted file mode 100644
index f80b60aaa..000000000
--- a/docs/build/guides/testing/README.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Contract Testing
-description: Testing Stellar Smart Contracts
-hide_table_of_contents: true
-sidebar_position: 40
----
-
-Testing is vital to ensure that smart contracts are safe, resilient, and accurate.
diff --git a/docs/build/guides/testing/code-coverage.mdx b/docs/build/guides/testing/code-coverage.mdx
index 6986014d1..7c069642f 100644
--- a/docs/build/guides/testing/code-coverage.mdx
+++ b/docs/build/guides/testing/code-coverage.mdx
@@ -1,17 +1,15 @@
 ---
 title: Code Coverage
-hide_table_of_contents: true
 description: Code coverage tools find code not tested.
-sidebar_position: 11
 ---
 
 Measuring code coverage uses tools to identify lines of code that are and aren't executed by tests. Code coverage stats can give us an idea of how much of a contract is actually tested by its tests.
 
-:::tip
+<Tip>
 
 Mutation testing is another form of coverage testing. See [Mutation Testing].
 
-:::
+</Tip>
 
 In rust projects the `cargo-llvm-cov` tool can be used to generate coverage stats, HTML reports, and lcov files that IDEs will load to display the coverage in the code editor.
 
@@ -49,12 +47,12 @@ cargo llvm-cov test --lcov --output-path=lcov.info
 
 Load the `lcov.info` file into your IDE using its coverage feature. In VSCode this can be done by installing the [Coverage Gutters] extension and executing the `Coverage Gutters: Watch` command.
 
-:::info
+<Info>
 
 Measuring code coverage in fuzz tests requires different tooling. See [Fuzzing].
 
-:::
+</Info>
 
 [Coverage Gutters]: https://marketplace.visualstudio.com/items?itemName=ryanluker.vscode-coverage-gutters
-[Mutation Testing]: mutation-testing.mdx
-[Fuzzing]: fuzzing.mdx
+[Mutation Testing]: mutation-testing
+[Fuzzing]: fuzzing
diff --git a/docs/build/guides/testing/differential-tests-with-test-snapshots.mdx b/docs/build/guides/testing/differential-tests-with-test-snapshots.mdx
index 8877adf34..bcd8db616 100644
--- a/docs/build/guides/testing/differential-tests-with-test-snapshots.mdx
+++ b/docs/build/guides/testing/differential-tests-with-test-snapshots.mdx
@@ -1,19 +1,17 @@
 ---
 title: Differential Tests with Test Snapshots
-hide_table_of_contents: true
 description: Differential testing using automatic test snapshots.
-sidebar_position: 9
 ---
 
 Tests are written to ensure that contracts behave today as expected, and in the future as well. Over time a contract may change and in all software development there remains the possibility of changes causing side-effects that are unexpected. Testing is one of the ways that we identify unexpected changes.
 
 However tests are limited, as they only show changes to values that the tests assert on.
 
-:::tip
+<Tip>
 
 Test snapshots are one tool for performing differential testing. See [Differential Testing] for other ways.
 
-:::
+</Tip>
 
 ### Test Snapshots
 
@@ -25,7 +23,7 @@ Most tests have a single `Env` and will result in a single test snapshot. Tests
 
 1. Write tests using the default `Env`. For example:
 
-   ```rust
+   ```rust highlight={14-15}
    #![cfg(test)]
    use soroban_sdk::Env;
 
@@ -39,10 +37,8 @@ Most tests have a single `Env` and will result in a single test snapshot. Tests
 
        assert_eq!(client.increment(), 1);
 
-       // highlight-start
        // At the end of the test the Env will automatically write a test snapshot
        // to the following directory: test_snapshots/test_abc.1.json
-       // highlight-end
    }
    ```
 
@@ -54,14 +50,14 @@ Most tests have a single `Env` and will result in a single test snapshot. Tests
 
 5. Diff test snapshots as needed to look for hints to why an unexpected change has occurred.
 
-:::info
+<Info>
 
 Test snapshots files are verbose. Test snapshots are most useful when changes appear and can be diffed, such as a new event being published, or storage changing.
 
-:::
+</Info>
 
 To give this a go, check out the [Getting Started] contract or any of the [examples], run the tests, and look for the test snapshots on disk.
 
-[Differential Testing]: ./differential-tests.mdx
-[Getting Started]: ../../smart-contracts/getting-started/README.mdx
-[examples]: ../../smart-contracts/example-contracts/README.mdx
+[Differential Testing]: ./differential-tests
+[Getting Started]: /docs/build/smart-contracts/getting-started
+[examples]: /docs/build/smart-contracts/example-contracts
diff --git a/docs/build/guides/testing/differential-tests.mdx b/docs/build/guides/testing/differential-tests.mdx
index 5f5bd7ece..07cabb5b8 100644
--- a/docs/build/guides/testing/differential-tests.mdx
+++ b/docs/build/guides/testing/differential-tests.mdx
@@ -1,8 +1,6 @@
 ---
 title: Differential Tests
-hide_table_of_contents: true
 description: Differential testing detects unintended changes.
-sidebar_position: 8
 ---
 
 Differential testing is the testing of two things to discover differences in their behavior.
@@ -13,11 +11,11 @@ This strategy is effective when building something new that should behave like s
 
 This strategy can be used in the context of unit and integration tests, or in the context of fuzz tests as well.
 
-:::tip
+<Tip>
 
 All contracts built with the Rust Soroban SDK have a form of differential testing built-in and enabled by default. See [Differential Testing with Test Snapshots].
 
-:::
+</Tip>
 
 ## How to Write Differential Tests
 
@@ -99,16 +97,16 @@ This test uses the same patterns used in [unit tests] and [integration tests]:
 4. Invoke functions using a client.
 5. Assert equality.
 
-:::tip
+<Tip>
 
 Differential tests work best when less assumptions are made. Rather than asserting only on specific return values or on implementation details like specific state, asserting on all observable outcomes and including things like events published or return values of other read-only contract functions will help to discover unexpected changes.
 
-:::
+</Tip>
 
 [Getting Started]: ../../smart-contracts/getting-started
 [increment example]: https://github.com/stellar/soroban-examples/blob/main/increment/src/lib.rs
-[Differential Testing with Test Snapshots]: ./differential-tests-with-test-snapshots.mdx
-[stellar contract fetch]: ../../../tools/cli/stellar-cli.mdx#stellar-contract-fetch
-[integration tests]: ./integration-tests.mdx
-[unit tests]: ./unit-tests.mdx
+[Differential Testing with Test Snapshots]: ./differential-tests-with-test-snapshots
+[stellar contract fetch]: ../../../tools/cli/stellar-cli#stellar-contract-fetch
+[integration tests]: ./integration-tests
+[unit tests]: ./unit-tests
 [stellar/rs-soroban-sdk#1360]: https://github.com/stellar/rs-soroban-sdk/issues/1360
diff --git a/docs/build/guides/testing/fork-testing.mdx b/docs/build/guides/testing/fork-testing.mdx
index a4ca1db92..acaeb99b7 100644
--- a/docs/build/guides/testing/fork-testing.mdx
+++ b/docs/build/guides/testing/fork-testing.mdx
@@ -1,8 +1,6 @@
 ---
 title: Fork Testing
-hide_table_of_contents: true
 description: Integration testing using mainnet data.
-sidebar_position: 6
 ---
 
 Fork testing is another form of [integration test], where not only mainnet contracts can be used, but also their data on mainnet. A snapshot of the ledger is taken and used to create an environment for testing. The test operates as a fork of that initial state.
@@ -25,11 +23,11 @@ The following tests set up the `increment-with-pause` contract, using a ledger s
    stellar snapshot create --address C... --output json --out snapshot.json
    ```
 
-   :::info
+   <Info>
 
    The `--ledger <ledger-seq>` option can be added to specify a ledger to snapshot. When not specified the latest ledger that's been pushed to archives is snapshot, that is usually less than 5 minutes old.
 
-   :::
+   </Info>
 
 2. Use `Env::from_ledger_snapshot_file(...)` to load the snapshot into an `Env` in the test.
 
@@ -39,12 +37,10 @@ The following tests set up the `increment-with-pause` contract, using a ledger s
 
 3. Write a test similar to the following that uses the `Env` preloaded with the contracts and contract data in `snapshot.json`. The test makes assertions about the behavior of the main contract in the context of the real dependencies and data that the dependencies have on the network.
 
-   ```rust
+   ```rust highlight={3}
    #[test]
    fn test() {
-       // highlight-start
        let env = Env::from_ledger_snapshot_file("snapshot.json");
-       // highlight-end
 
        let contract_id = env.register(
            IncrementContract,
@@ -63,21 +59,20 @@ Most tests, whether they're unit, mocks, or integration tests, will look very si
 3. Invoke functions using the generated client.
 4. Assert the outcome.
 
-:::tip
+<Tip>
 
 Snapshots created from testnet or mainnet can also be a way to test and debug incidents with a contract on network. A snapshot can be created at a specific ledger and tests written using that snapshot to better understand why or how a series of events occurred.
 
-:::
-
-:::tip
+</Tip>
+<Tip>
 
 A snapshot can be created of any contract deployed to mainnet or testnet using the `stellar snapshot create` command. It can be a fun way to experiment with and learn about deployed contracts by loading a snapshot into a test and invoking the contract. Fuzzing can even be performed on contracts using this tooling.
 
-:::
+</Tip>
 
 [increment-with-pause contract]: https://github.com/stellar/soroban-examples/blob/main/increment_with_pause/src/lib.rs
 [pause contract]: https://github.com/stellar/soroban-examples/blob/main/pause/src/lib.rs
-[integration test]: ./integration-tests.mdx
-[Making Cross-Contract Calls]: ../conventions/cross-contract.mdx
-[Soroban Rust SDK]: ../../../tools/sdks/contract-sdks.mdx#soroban-rust-sdk
-[Stellar CLI]: ../../../tools/cli/README.mdx
+[integration test]: ./integration-tests
+[Making Cross-Contract Calls]: ../conventions/cross-contract
+[Soroban Rust SDK]: ../../../tools/sdks/contract-sdks#soroban-rust-sdk
+[Stellar CLI]: /docs/tools/cli
diff --git a/docs/build/guides/testing/fuzzing.mdx b/docs/build/guides/testing/fuzzing.mdx
index 9eb8c0e8b..35cbb13b3 100644
--- a/docs/build/guides/testing/fuzzing.mdx
+++ b/docs/build/guides/testing/fuzzing.mdx
@@ -1,8 +1,6 @@
 ---
 title: Fuzzing
-hide_table_of_contents: true
 description: Fuzzing and property testing to find unexpected behavior.
-sidebar_position: 7
 ---
 
 Fuzzing is the process of providing random data to programs to identify unexpected behavior, such as crashes and panics.
@@ -11,11 +9,11 @@ Fuzz tests can also be written as property tests that instead of seeking to iden
 
 The following steps can be used in any Stellar contract workspace. If experimenting, try them in the [increment example]. The contract has an `increment` function that increases a counter value by one on every invocation.
 
-:::tip
+<Tip>
 
 See the [Rust Fuzz Book] for a general tutorial on using both `cargo-fuzz` and `cargo-afl`.
 
-:::
+</Tip>
 
 ## How to Write Fuzz Tests with `cargo-fuzz`
 
@@ -103,11 +101,11 @@ See the [Rust Fuzz Book] for a general tutorial on using both `cargo-fuzz` and `
    cargo +nightly fuzz run --sanitizer=thread fuzz_target_1
    ```
 
-   :::info
+   <Info>
 
    If you're developing on MacOS you need to add the `--sanitizer=thread` flag in order to work around a [known issue](https://github.com/stellar/rs-soroban-sdk/issues/1056).
 
-   :::
+   </Info>
 
 This test uses the same patterns used in [unit tests] and [integration tests]:
 
@@ -116,11 +114,11 @@ This test uses the same patterns used in [unit tests] and [integration tests]:
 3. Invoke functions using a client.
 4. Assert expectations.
 
-:::tip
+<Tip>
 
 For a full detailed example, see the [fuzzing example].
 
-:::
+</Tip>
 
 ## How to Write Fuzz Tests with `cargo-afl`
 
@@ -259,21 +257,21 @@ Getting code coverage data for fuzz tests requires some different tooling than w
 
    Load the `lcov.info` file into your IDE using its coverage feature. In VSCode this can be done by installing the [Coverage Gutters] extension and executing the `Coverage Gutters: Watch` command.
 
-:::tip
+<Tip>
 
 To measure code coverage of regular Rust tests, see [Code Coverage].
 
-:::
+</Tip>
 
 [increment example]: https://github.com/stellar/soroban-examples/blob/main/increment/src/lib.rs
-[Differential Testing with Test Snapshots]: ./differential-tests-with-test-snapshots.mdx
-[stellar contract fetch]: ../../../tools/cli/stellar-cli.mdx#stellar-contract-fetch
-[integration tests]: ./integration-tests.mdx
-[unit tests]: ./unit-tests.mdx
+[Differential Testing with Test Snapshots]: ./differential-tests-with-test-snapshots
+[stellar contract fetch]: ../../../tools/cli/stellar-cli#stellar-contract-fetch
+[integration tests]: ./integration-tests
+[unit tests]: ./unit-tests
 [stellar/rs-soroban-sdk#1360]: https://github.com/stellar/rs-soroban-sdk/issues/1360
-[fuzzing example]: ../../smart-contracts/example-contracts/fuzzing.mdx
+[fuzzing example]: ../../smart-contracts/example-contracts/fuzzing
 [Rust Fuzz Book]: https://rust-fuzz.github.io/book
-[Code Coverage]: code-coverage.mdx
+[Code Coverage]: code-coverage
 [Coverage Gutters]: https://marketplace.visualstudio.com/items?itemName=ryanluker.vscode-coverage-gutters
 [`cargo-afl`]: https://github.com/rust-fuzz/afl.rs
 [AFL++]: https://aflplus.plus
diff --git a/docs/build/guides/testing/index.mdx b/docs/build/guides/testing/index.mdx
new file mode 100644
index 000000000..2321cf261
--- /dev/null
+++ b/docs/build/guides/testing/index.mdx
@@ -0,0 +1,6 @@
+---
+title: Contract Testing
+description: Testing Stellar Smart Contracts
+---
+
+Testing is vital to ensure that smart contracts are safe, resilient, and accurate.
diff --git a/docs/build/guides/testing/integration-tests.mdx b/docs/build/guides/testing/integration-tests.mdx
index 8a412bd98..45d57e2b7 100644
--- a/docs/build/guides/testing/integration-tests.mdx
+++ b/docs/build/guides/testing/integration-tests.mdx
@@ -1,8 +1,6 @@
 ---
 title: Integration Tests
-hide_table_of_contents: true
 description: Integration testing uses dependency contracts instead of mocks.
-sidebar_position: 5
 ---
 
 Integration tests are tests that include the integration between components, and so test a larger scope such as other contracts.
@@ -31,15 +29,13 @@ The following tests set up the `increment-with-pause` contract, as well as impor
 
 3. Write a test similar to the following that registers not only the increment-with-pause contract, but also the pause contract that was imported. The test checks that when the pause contract is not paused that the increment contract operates as expected. When it is paused, the increment function errors. Once it's unpaused the function operates as expected.
 
-   ```rust
+   ```rust highlight={5-6}
    #[test]
    fn test() {
        let env = Env::default();
 
-       // highlight-start
        let pause_id = env.register(pause::WASM, ());
        let pause_client = pause::Client::new(&env, &pause_id);
-       // highlight-end
 
        let contract_id = env.register(
            IncrementContract,
@@ -67,6 +63,6 @@ Most tests, whether they're unit, mocks, or integration tests, will look very si
 
 [increment-with-pause contract]: https://github.com/stellar/soroban-examples/blob/main/increment_with_pause/src/lib.rs
 [pause contract]: https://github.com/stellar/soroban-examples/blob/main/pause/src/lib.rs
-[Integration Tests]: ./integration-tests.mdx
-[Making Cross-Contract Calls]: ../conventions/cross-contract.mdx
-[Soroban Rust SDK]: ../../../tools/sdks/contract-sdks.mdx#soroban-rust-sdk
+[Integration Tests]: ./integration-tests
+[Making Cross-Contract Calls]: ../conventions/cross-contract
+[Soroban Rust SDK]: ../../../tools/sdks/contract-sdks#soroban-rust-sdk
diff --git a/docs/build/guides/testing/ledger-snapshot-testing.mdx b/docs/build/guides/testing/ledger-snapshot-testing.mdx
index 92f41f53b..b80bef4d2 100644
--- a/docs/build/guides/testing/ledger-snapshot-testing.mdx
+++ b/docs/build/guides/testing/ledger-snapshot-testing.mdx
@@ -1,8 +1,6 @@
 ---
 title: Testing with Ledger Snapshot
-hide_table_of_contents: true
 description: Use ledger snapshots to test contracts with ledger data
-sidebar_position: 12
 ---
 
 Ledger snapshots can be used to test smart contracts with a local copy of the ledger’s entries. Learn how to create a ledger snapshot and use it for smart contract testing in a few simple steps. The examples here will cover the following use cases:
@@ -46,7 +44,7 @@ Since we want to write a test that reads data stored on the ledger, or more prec
 
 #### Build contract
 
-Use the [Stellar CLI](../../../tools/cli/stellar-cli.mdx) to build the contract:
+Use the [Stellar CLI](../../../tools/cli/stellar-cli) to build the contract:
 
 ```bash
 stellar contract build
@@ -83,7 +81,7 @@ Now we have a working, deployed smart contract function that has stored a value
 
 ## 2. Create a ledger snapshot
 
-A snapshot of the ledger can be created using the Stellar CLI. The CLI command allows you to customize and limit the scope of the snapshot, since it’s most likely not necessary for you to create a snapshot of all ledger entries. See the [documentation](../../../tools/cli/stellar-cli.mdx#stellar-snapshot-create) for full details about how to limit the snapshot.
+A snapshot of the ledger can be created using the Stellar CLI. The CLI command allows you to customize and limit the scope of the snapshot, since it’s most likely not necessary for you to create a snapshot of all ledger entries. See the [documentation](../../../tools/cli/stellar-cli#stellar-snapshot-create) for full details about how to limit the snapshot.
 
 For the examples used here, we want to limit the ledger snapshot to include entries related to:
 
@@ -244,13 +242,13 @@ This example shows there are only minor differences between testing contract fun
 
 In this last example, we want to read the balance of an account. It can be the balance of a user account or of a smart contract - any account that can hold a balance. In this example, we check the balance of the user account `alice`.
 
-In this example, we assume that `alice` already has a balance in XLM, and since the examples are based on Testnet, the `alice` account was funded by FriendBot if this [guide](../../../tools/cli/cookbook/stellar-keys.mdx) was followed while creating the account. The address of `alice` can be looked up by running this command:
+In this example, we assume that `alice` already has a balance in XLM, and since the examples are based on Testnet, the `alice` account was funded by FriendBot if this [guide](../../../tools/cli/cookbook/stellar-keys) was followed while creating the account. The address of `alice` can be looked up by running this command:
 
 ```bash
 stellar keys address alice
 ```
 
-Tokens, such as XLM, are wrapped in a contract interface called the [Stellar Asset Contract (SAC)](../../../tokens/stellar-asset-contract.mdx). This interface provides a convenient way to query an account’s balance. The first step of getting the account balance is to create a contract client for XLM tokens.
+Tokens, such as XLM, are wrapped in a contract interface called the [Stellar Asset Contract (SAC)](../../../tokens/stellar-asset-contract). This interface provides a convenient way to query an account’s balance. The first step of getting the account balance is to create a contract client for XLM tokens.
 
 The SAC address for XLM is a reserved address and will be the same for all projects. USDC and other assets will have another SAC address, but they do not change. We use the SAC address to define a client using `TokenClient`.
 
diff --git a/docs/build/guides/testing/mocking.mdx b/docs/build/guides/testing/mocking.mdx
index e37eb717c..ef346bb13 100644
--- a/docs/build/guides/testing/mocking.mdx
+++ b/docs/build/guides/testing/mocking.mdx
@@ -1,17 +1,15 @@
 ---
 title: Mocking
-hide_table_of_contents: true
 description: Mocking dependency contracts in tests.
-sidebar_position: 2
 ---
 
 Mocks are used in tests to exclude functionality that a test doesn't want to test. Mocks are used when it's difficult to test against an external component.
 
-:::tip
+<Tip>
 
 The [Soroban Rust SDK] makes it just as easy to test against a real contract as it does to test against a mock of a contract. In some ecosystems integration tests are avoided. Not in the Stellar ecosystem. See [Integration Tests].
 
-:::
+</Tip>
 
 ## How to Write Tests with Mocks
 
@@ -21,14 +19,13 @@ The following tests set up the `increment-with-pause` contract, as well as a moc
 
 The following test checks that when the pause contract is not paused, the increment contract functions.
 
-```rust
+```rust highlight={7-14,20}
 #![cfg(test)]
 use crate::{Error, IncrementContract, IncrementContractArgs, IncrementContractClient, Pause};
 use soroban_sdk::{contract, contractimpl, Env};
 
 mod notpaused {
     use super::*;
-    // highlight-start
     #[contract]
     pub struct Mock;
     #[contractimpl]
@@ -37,15 +34,12 @@ mod notpaused {
             false
         }
     }
-    // highlight-end
 }
 
 #[test]
 fn test_notpaused() {
     let env = Env::default();
-    // highlight-start
     let pause_id = env.register(notpaused::Mock, ());
-    // highlight-end
     let contract_id = env.register(
         IncrementContract,
         IncrementContractArgs::__constructor(&pause_id),
@@ -60,14 +54,13 @@ fn test_notpaused() {
 
 The following test checks that when the pause contract is paused, the increment contract function rejects attempts to increment.
 
-```rust
+```rust highlight={7-14,20}
 #![cfg(test)]
 use crate::{Error, IncrementContract, IncrementContractArgs, IncrementContractClient, Pause};
 use soroban_sdk::{contract, contractimpl, Env};
 
 mod paused {
     use super::*;
-    // highlight-start
     #[contract]
     pub struct Mock;
     #[contractimpl]
@@ -76,15 +69,12 @@ mod paused {
             true
         }
     }
-    // highlight-end
 }
 
 #[test]
 fn test_paused() {
     let env = Env::default();
-    // highlight-start
     let pause_id = env.register(paused::Mock, ());
-    // highlight-end
     let contract_id = env.register(
         IncrementContract,
         IncrementContractArgs::__constructor(&pause_id),
@@ -102,7 +92,7 @@ Most tests, whether you're writing unit, mocks, or integration tests, will look
 3. Invoke functions using the generated client.
 4. Assert the outcome.
 
-:::warning
+<Warning>
 
 Mocking introduces assumptions about the behavior of another contract. Even if the contract publishes an interface that says it'll return a bool (true/false), contracts can return any type.
 
@@ -118,9 +108,9 @@ See [Integration Tests] for how to test with real dependencies.
 
 The [Soroban Rust SDK] handles contract calls defensively so that any unexpected error or unexpected type returned from the called contract will cause execution to stop. The SDK also provides methods to make these calls and to intercept error situations. See [Making Cross-Contract Calls] for more details.
 
-:::
+</Warning>
 
 [increment-with-pause contract]: https://github.com/stellar/soroban-examples/blob/main/increment_with_pause/src/lib.rs
-[Integration Tests]: ./integration-tests.mdx
-[Making Cross-Contract Calls]: ../conventions/cross-contract.mdx
-[Soroban Rust SDK]: ../../../tools/sdks/contract-sdks.mdx#soroban-rust-sdk
+[Integration Tests]: ./integration-tests
+[Making Cross-Contract Calls]: ../conventions/cross-contract
+[Soroban Rust SDK]: ../../../tools/sdks/contract-sdks#soroban-rust-sdk
diff --git a/docs/build/guides/testing/mutation-testing.mdx b/docs/build/guides/testing/mutation-testing.mdx
index 4cf4954ac..1b24c19cf 100644
--- a/docs/build/guides/testing/mutation-testing.mdx
+++ b/docs/build/guides/testing/mutation-testing.mdx
@@ -1,8 +1,6 @@
 ---
 title: Mutation Testing
-hide_table_of_contents: true
 description: Mutation testing finds code not tested.
-sidebar_position: 10
 ---
 
 Mutation testing is making changes to a program, either manually or automatically, to identify changes that can be made that don't get caught by tests.
@@ -34,4 +32,4 @@ The `cargo-mutants` tool can be used to automatically and iteratively modify the
 
    Diffs of each change that was attempted can be found in the `mutants.out/diff` directory.
 
-[code coverage]: code-coverage.mdx
+[code coverage]: code-coverage
diff --git a/docs/build/guides/testing/test-contract-auth.mdx b/docs/build/guides/testing/test-contract-auth.mdx
index 17f8cec91..cf5bcba4a 100644
--- a/docs/build/guides/testing/test-contract-auth.mdx
+++ b/docs/build/guides/testing/test-contract-auth.mdx
@@ -1,15 +1,13 @@
 ---
 title: Test Authorization
-hide_table_of_contents: true
 description: Write tests that test contract authorization.
-sidebar_position: 3
 ---
 
 Tests can assert on the auths that are expected to occur.
 
 The following example sets up a test environment, registers an increment contract, and checks after the increment invocation what auths were required.
 
-```rust
+```rust highlight={12-38}
 #[test]
 fn test() {
     let env = Env::default();
@@ -21,7 +19,6 @@ fn test() {
 
     assert_eq!(client.increment(&user_1, &5), 5);
 
-    // highlight-start
     // Verify that the user indeed had to authorize a call of `increment` with
     // the expected arguments:
     assert_eq!(
@@ -49,15 +46,14 @@ fn test() {
             }
         )]
     );
-    // highlight-end
 }
 ```
 
-:::tip
+<Tip>
 
-For the full example the above snippet is extracted from, see the [auth example contract](../../smart-contracts/example-contracts/auth.mdx).
+For the full example the above snippet is extracted from, see the [auth example contract](../../smart-contracts/example-contracts/auth).
 
-:::
+</Tip>
 
 ## Authorization in constructors
 
@@ -65,8 +61,8 @@ If a contract's constructor calls `require_auth()` (or `require_auth_for_args()`
 
 To have auth in a constructor execute as it will in production the contract must be deployed in the test using the standard deployment functions after being built to Wasm.
 
-:::caution
+<Warning>
 
 This behaviour was not consistent in some versions of the `soroban-sdk` due to an issue, but is consistent as of v27.0.2.
 
-:::
+</Warning>
diff --git a/docs/build/guides/testing/test-contract-events.mdx b/docs/build/guides/testing/test-contract-events.mdx
index d9882fcf7..f146acb46 100644
--- a/docs/build/guides/testing/test-contract-events.mdx
+++ b/docs/build/guides/testing/test-contract-events.mdx
@@ -1,15 +1,13 @@
 ---
 title: Test Events
-hide_table_of_contents: true
 description: Write tests that test contract events.
-sidebar_position: 4
 ---
 
 Tests can assert on events that are expected to be published.
 
 The following example sets up a test environment, registers an increment contract, and checks after the increment invocations which events were published.
 
-```rust
+```rust highlight={11-33}
 #[test]
 fn test() {
     let env = Env::default();
@@ -20,7 +18,6 @@ fn test() {
     assert_eq!(client.increment(), 2);
     assert_eq!(client.increment(), 3);
 
-    // highlight-start
     assert_eq!(
         // Get all events published since the Env was created.
         env.events().all(),
@@ -44,12 +41,11 @@ fn test() {
             ),
         ]
     );
-    // highlight-end
 }
 ```
 
-:::tip
+<Tip>
 
-For the full example the above snippet is extracted from, see the [events example contract](../../smart-contracts/example-contracts/events.mdx).
+For the full example the above snippet is extracted from, see the [events example contract](../../smart-contracts/example-contracts/events).
 
-:::
+</Tip>
diff --git a/docs/build/guides/testing/unit-tests.mdx b/docs/build/guides/testing/unit-tests.mdx
index 44d9efd6f..0a54f186e 100644
--- a/docs/build/guides/testing/unit-tests.mdx
+++ b/docs/build/guides/testing/unit-tests.mdx
@@ -1,8 +1,6 @@
 ---
 title: Unit Tests
-hide_table_of_contents: true
 description: Unit tests are small tests that test smart contracts.
-sidebar_position: 1
 ---
 
 Unit tests are small tests that test one piece of functionality within a contract.
@@ -59,17 +57,16 @@ Most tests, even integration tests and fuzz tests, will look very similar to thi
    assert_eq!(client.increment(), 1);
    ```
 
-:::tip
+<Tip>
 
 Tests are written in Rust, alongside the contract. Same tools. Same APIs. Same SDK. No context switching! Use your favorite Rust tools and libraries that you'd use for any Rust test.
 
-:::
-
-:::info
+</Tip>
+<Info>
 
 The `Env` created at the beginning of the test is not a simulation of the Soroban Environment. It's the same Soroban Environment that mainnet uses to execute contracts. There are only some minor differences: test utilities are enabled, and the storage backend is different.
 
-:::
+</Info>
 
 It's a simple test, but it's a complete test. There's a full environment setup, used, and torn down in the test, and it happens fast. The Rust test harness runs all the tests for a contract in parallel and each will have its own isolated contract environment.
 
diff --git a/docs/build/guides/tokens/README.mdx b/docs/build/guides/tokens/README.mdx
deleted file mode 100644
index 707b0bf40..000000000
--- a/docs/build/guides/tokens/README.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Stellar Asset Contract (SAC) Tokens
-description: Tokens and Stellar Asset Contract (SAC)
-hide_table_of_contents: true
-sidebar_position: 76
----
-
-The Stellar Asset Contract (SAC) is a standard introduced on the Stellar blockchain to streamline and enhance token issuance and management. Learn about using tokens on Stellar.
diff --git a/docs/build/guides/tokens/custom-sac-admin.mdx b/docs/build/guides/tokens/custom-sac-admin.mdx
index 5afcdb35d..cf953d0e8 100644
--- a/docs/build/guides/tokens/custom-sac-admin.mdx
+++ b/docs/build/guides/tokens/custom-sac-admin.mdx
@@ -1,18 +1,17 @@
 ---
 title: Set a custom admin account for a Stellar Asset Contract (SAC)
-hide_table_of_contents: true
 description: Set a custom administrator account on a deployed SAC
 ---
 
-The [Stellar Asset Contract (SAC)](../../../tokens/stellar-asset-contract.mdx) includes functionality to set a custom administration account on the contract itself. This can allow for flexible arrangements of asset administration, which can be configured to suit many distinct use-cases.
+The [Stellar Asset Contract (SAC)](../../../tokens/stellar-asset-contract) includes functionality to set a custom administration account on the contract itself. This can allow for flexible arrangements of asset administration, which can be configured to suit many distinct use-cases.
 
 For example, you can set a custom SAC admin, and then lock the issuer account, allowing for token administration to be _exclusively_ performed through the SAC contract. Or, you could set a custom SAC admin and still keep the issuer account unlocked, allowing for a hybrid approach to token administration.
 
-:::info
+<Info>
 
 It should be understood that an asset's issuer account can have a distinct set of signatures and weights, and these are unrelated to the SAC admin address.
 
-:::
+</Info>
 
 ## Considerations
 
@@ -22,26 +21,26 @@ To effectively utilize the SAC admin functionality, you should be aware of a few
 - A SAC `Admin` address can be either a regular Stellar account (`G...`), or it can be a smart contract (`C...`) address. The use-cases requiring a smart contract to act as a SAC `Admin` tend to be more common. This opens up the possibility of programmatically minting and taking other administrative actions for an asset by way of a smart contract invocation.
 - Changing a SAC `Admin` address requires authorization from the asset's _current_ `Admin` address, which will be the issuer account the first time the action is performed.
 
-Depending on the use-case, it can be beneficial for asset issuers to mint an entire supply of tokens up front, and then lock down the issuer account. This would keep the total token supply capped forever. You can learn more about this practice on the [asset design considerations](../../../tokens/control-asset-access.mdx#limiting-the-supply-of-an-asset) page. However, since the issuer account and a SAC `Admin` address act independently, there are some interesting points to make that might seem counterintuitive at first glance.
+Depending on the use-case, it can be beneficial for asset issuers to mint an entire supply of tokens up front, and then lock down the issuer account. This would keep the total token supply capped forever. You can learn more about this practice on the [asset design considerations](../../../tokens/control-asset-access#limiting-the-supply-of-an-asset) page. However, since the issuer account and a SAC `Admin` address act independently, there are some interesting points to make that might seem counterintuitive at first glance.
 
 - If an asset's issuer account is locked while the SAC `Admin` address has not been changed, it will _never_ be possible to change the SAC `Admin` address. This is because the issuer account can no longer authorize the first `set_admin` invocation.
 - If an asset's issuer account is locked after the SAC `Admin` address has been changed, tokens will still be mint-able and/or clawback-able (if enabled) from the SAC as long as it's authorized by the _current_ `Admin` address.
 
-:::danger
+<Danger>
 
 When changing a SAC `Admin` address, the new admin address provided is not validated at that time. This means you can lock down administration from the SAC **forever**. Consider your choice of SAC `Admin` address carefully and thoroughly.
 
-:::
+</Danger>
 
 ## Example
 
 The following example will create a new Stellar asset, `STAR:GCS5NEHKJALCSVJAKIORXXVS554QQV5FNDLBK33CCAH6UIRYPXYZFC34`. Then, we will create a simple contract to regulate a hypothetical airdrop for the token. This contract will be configured as the SAC `Admin` address for the `STAR` asset, and it will be able to perform any administrative functions we want.
 
-:::note
+<Note>
 
-We will not demonstrate setting a new `G...` account as a SAC admin in this guide. Any use-case that needs asset administration delegated to another `G...` account will likely be better served by taking advantage of the existing [multisig capabilities](../../../learn/fundamentals/transactions/signatures-multisig.mdx) of Stellar accounts.
+We will not demonstrate setting a new `G...` account as a SAC admin in this guide. Any use-case that needs asset administration delegated to another `G...` account will likely be better served by taking advantage of the existing [multisig capabilities](../../../learn/fundamentals/transactions/signatures-multisig) of Stellar accounts.
 
-:::
+</Note>
 
 ### Enable the built-in SAC contract
 
@@ -56,11 +55,11 @@ stellar contract asset deploy \
 
 This gives us the SAC address of `CBVYF2KJ72BRPLVPCUL3PGWDO5RK2XP4AJDHKX7GDDBJW42L2C6VT3SF`.
 
-:::note
+<Note>
 
 We're using the asset's issuer account here to enable the SAC on the Testnet network, but this action can be performed using _any_ account.
 
-:::
+</Note>
 
 ### Check the initial `Admin` address
 
@@ -105,7 +104,7 @@ impl StarDropContract {
 }
 ```
 
-Notice the contract calls the SAC's [`trust` function](../../../tokens/stellar-asset-contract.mdx#creating-trustlines-from-a-contract) before minting. As of Yardstick, Protocol 26 ([CAP-73](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0073.md)), this creates the receiver's `STAR` trustline as part of the same invocation, so a `G...` receiver doesn't need to set up a trustline in a separate transaction beforehand. The call is a no-op if the receiver is a contract address or already has the trustline, and it requires the receiver's authorization (which they're already providing by invoking `claim_airdrop`).
+Notice the contract calls the SAC's [`trust` function](../../../tokens/stellar-asset-contract#creating-trustlines-from-a-contract) before minting. As of Yardstick, Protocol 26 ([CAP-73](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0073.md)), this creates the receiver's `STAR` trustline as part of the same invocation, so a `G...` receiver doesn't need to set up a trustline in a separate transaction beforehand. The call is a no-op if the receiver is a contract address or already has the trustline, and it requires the receiver's authorization (which they're already providing by invoking `claim_airdrop`).
 
 This contract gets deployed, and the address might be (for example) `CDF4VYXJE2KPLIZHQAX4XQRZ3QAMVQJRTOCS3B3GEKONHMYSYK6QID7B`. We can now set the SAC `Admin` address to this contract:
 
@@ -128,7 +127,7 @@ stellar contract invoke \
 # CDF4VYXJE2KPLIZHQAX4XQRZ3QAMVQJRTOCS3B3GEKONHMYSYK6QID7B
 ```
 
-Now, since the airdrop contract is the administrator of the SAC, we can invoke its `claim_airdrop` function from any account we like. The contract's `trust` call takes care of creating the asset's trustline for the receiving account, so the receiver only needs enough XLM to cover the new trustline's [base reserve](../../../learn/fundamentals/lumens.mdx#base-reserves).
+Now, since the airdrop contract is the administrator of the SAC, we can invoke its `claim_airdrop` function from any account we like. The contract's `trust` call takes care of creating the asset's trustline for the receiving account, so the receiver only needs enough XLM to cover the new trustline's [base reserve](../../../learn/fundamentals/lumens#base-reserves).
 
 ```sh
 stellar contract invoke \
diff --git a/docs/build/guides/tokens/deploying-a-sac.mdx b/docs/build/guides/tokens/deploying-a-sac.mdx
index 8496bce1d..9121d298a 100644
--- a/docs/build/guides/tokens/deploying-a-sac.mdx
+++ b/docs/build/guides/tokens/deploying-a-sac.mdx
@@ -1,34 +1,20 @@
 ---
 title: Deploy a Stellar Asset Contract (SAC) from within a contract
-hide_table_of_contents: true
+og:title: "Deploying a Stellar Asset Contract (SAC) from within a contract"
+og:description: "This is a step-by-step guide to help you deploy an SAC from within a smart contract on Stellar."
 description: Deploy a SAC from another smart contract using the Rust SDK
 ---
 
-<head>
-  <title>
-    {`Deploying a Stellar Asset Contract (SAC) from within a contract`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Deploying a Stellar Asset Contract (SAC) from within a contract"
-  />
-  <meta
-    property="og:description"
-    content="This is a step-by-step guide to help you deploy an SAC from within a smart contract on Stellar."
-  />
-</head>
-
 ## Overview
 
-In this guide, you'll learn how to deploy a [Stellar Asset Contract (SAC)](../../../tokens/stellar-asset-contract.mdx) from within another smart contract using the Soroban Rust SDK. The Soroban Rust SDK provides tools and utilities for working with Stellar smart contracts, allowing you to deploy and interact with SACs directly from your contract logic.
+In this guide, you'll learn how to deploy a [Stellar Asset Contract (SAC)](../../../tokens/stellar-asset-contract) from within another smart contract using the Soroban Rust SDK. The Soroban Rust SDK provides tools and utilities for working with Stellar smart contracts, allowing you to deploy and interact with SACs directly from your contract logic.
 
 ## Prerequisites:
 
 Before you begin, make sure you have the following:
 
 - Basic understanding of [Rust programming language](https://www.rust-lang.org). To brush up on Rust, check out [Rustlings](https://github.com/rust-lang/rustlings) or [The Rust book](https://doc.rust-lang.org/book).
-- [Soroban Rust SDK](../../../tools/sdks/contract-sdks.mdx#soroban-rust-sdk) installed and configured in your development environment.
+- [Soroban Rust SDK](../../../tools/sdks/contract-sdks#soroban-rust-sdk) installed and configured in your development environment.
 - Basic understanding of the Soroban Rust SDK and familiarity with Soroban's core concepts and Rust programming.
 
 ## 1. Define the SacDeployer contract
@@ -85,7 +71,7 @@ fn test() {
 }
 ```
 
-### Explanation
+### Explanation {#explanation-1}
 
 - `env.register(SacDeployer, ())`: registers the `SacDeployer` contract in the test environment and returns its contract ID.
 - `SacDeployerClient::new(&env, &contract_id)`: creates a client used to invoke the deployed `SacDeployer` contract's functions.
diff --git a/docs/build/guides/tokens/index.mdx b/docs/build/guides/tokens/index.mdx
new file mode 100644
index 000000000..19c1cbc75
--- /dev/null
+++ b/docs/build/guides/tokens/index.mdx
@@ -0,0 +1,6 @@
+---
+title: Stellar Asset Contract (SAC) Tokens
+description: Tokens and Stellar Asset Contract (SAC)
+---
+
+The Stellar Asset Contract (SAC) is a standard introduced on the Stellar blockchain to streamline and enhance token issuance and management. Learn about using tokens on Stellar.
diff --git a/docs/build/guides/tokens/stellar-asset-contract.mdx b/docs/build/guides/tokens/stellar-asset-contract.mdx
index 716eb856c..77b1813b7 100644
--- a/docs/build/guides/tokens/stellar-asset-contract.mdx
+++ b/docs/build/guides/tokens/stellar-asset-contract.mdx
@@ -1,10 +1,9 @@
 ---
 title: Integrate Stellar Assets Contracts
-hide_table_of_contents: true
 description: Test and use Stellar assets in a Stellar smart contract
 ---
 
-When interacting with assets in a smart contract, the [Stellar Asset Contract](../../../tokens/stellar-asset-contract.mdx) is not different from any other token that implements the Stellar [SEP-41 Token Interface].
+When interacting with assets in a smart contract, the [Stellar Asset Contract](../../../tokens/stellar-asset-contract) is not different from any other token that implements the Stellar [SEP-41 Token Interface].
 
 ## Contract Code
 
@@ -40,9 +39,11 @@ stellar contract id asset \
 
 E.g. for USDC, it would be `--asset USDC:G...` For the native asset, XLM, `--asset native`. See the [deploy SAC] guide for more details.
 
-[deploy SAC]: ../../../tools/cli/cookbook/deploy-stellar-asset-contract.mdx
+[deploy SAC]: ../../../tools/cli/cookbook/deploy-stellar-asset-contract
 
-:::info[Clients]
+<Info>
+
+**Clients**
 
 A client created by [`token::TokenClient`] implements the functions defined by any contract that implements the [SEP-41 Token Interface]. But with [CAP-46-6 smart contract standardized asset], the Stellar Asset Contract exposes additional functions such as `mint`. To access the additional functions, another client needs to be used: [`token::StellarAssetClient`]. This client only implements the functions from CAP-46-6, which are not part of the SEP-41 interface.
 
@@ -53,11 +54,11 @@ let client = token::StellarAssetClient::new(&env, &id);
 client.mint(...);
 ```
 
-:::
+</Info>
 
 ## Testing
 
-Soroban Rust SDK provides an easy way to instantiate a Stellar Asset Contract tokens using `register_stellar_asset_contract_v2`. This function can be seen as the deployment of a generic token. It also allows you to manipulate flags on the issuer account like `AUTH_REVOCABLE` and `AUTH_REQUIRED`. In the following example, we are following the best practices outlined in the [Issuing and Distribution Accounts section](../../../tokens/control-asset-access.mdx#issuing-and-distribution-accounts):
+Soroban Rust SDK provides an easy way to instantiate a Stellar Asset Contract tokens using `register_stellar_asset_contract_v2`. This function can be seen as the deployment of a generic token. It also allows you to manipulate flags on the issuer account like `AUTH_REVOCABLE` and `AUTH_REQUIRED`. In the following example, we are following the best practices outlined in the [Issuing and Distribution Accounts section](../../../tokens/control-asset-access#issuing-and-distribution-accounts):
 
 ```rust
 #![cfg(test)]
@@ -101,10 +102,10 @@ fn test() {
 
 See the full examples that utilize the token contract in various ways for more details:
 
-- [Timelock](../../smart-contracts/example-contracts/timelock.mdx) and [single offer](../../smart-contracts/example-contracts/single-offer-sale.mdx) move token via `transfer` to and from the contract
-- [Atomic swap](../../smart-contracts/example-contracts/atomic-swap.mdx) uses `transfer` to transfer token on behalf of the user
+- [Timelock](../../smart-contracts/example-contracts/timelock) and [single offer](../../smart-contracts/example-contracts/single-offer-sale) move token via `transfer` to and from the contract
+- [Atomic swap](../../smart-contracts/example-contracts/atomic-swap) uses `transfer` to transfer token on behalf of the user
 
-[sep-41 token interface]: ../../../tokens/token-interface.mdx
+[sep-41 token interface]: ../../../tokens/token-interface
 [cap-46-6 smart contract standardized asset]: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0046-06.md
 [`token::tokenclient`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/token/struct.TokenClient.html
 [`token::stellarassetclient`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/token/struct.StellarAssetClient.html
diff --git a/docs/build/guides/transactions/README.mdx b/docs/build/guides/transactions/README.mdx
deleted file mode 100644
index 366b6c587..000000000
--- a/docs/build/guides/transactions/README.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: Transactions
-hide_table_of_contents: true
-sidebar_position: 120
----
-
-Stellar transactions are comprised of operations. These guides will walk you through various Stellar operations, non-contract transactions, and smart contract transactions. Read more about operations and transactions in the [Operations and Transactions section](../../../learn/fundamentals/transactions/README.mdx).
diff --git a/docs/build/guides/transactions/channel-accounts.mdx b/docs/build/guides/transactions/channel-accounts.mdx
index cb981e0d5..cbc53e3bf 100644
--- a/docs/build/guides/transactions/channel-accounts.mdx
+++ b/docs/build/guides/transactions/channel-accounts.mdx
@@ -1,7 +1,6 @@
 ---
 title: Channel accounts
 description: Create channel accounts to submit transactions to the network at a high rate.
-sidebar_position: 10
 ---
 
 Channel accounts provide a method for submitting transactions to the network at a high rate.
@@ -16,9 +15,9 @@ You will, of course, have to sign the transaction with both the base account key
 
 For example:
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 // channelAccounts[] is an array of accountIDs, one for each channel
 // channelKeys[] is an array of secret keys, one for each channel
 // channelIndex is the channel you want to send this transaction over
@@ -47,7 +46,7 @@ transaction.sign(baseAccountKey); // base account must sign to approve the payme
 transaction.sign(channelKeys[channelIndex]); // channel must sign to approve it being the source of the transaction
 ```
 
-```python
+```python Python
 # channelAccounts[] is an array of accountIDs, one for each channel
 # channelKeys[] is an array of secret keys, one for each channel
 # channelIndex is the channel you want to send this transaction over
@@ -72,4 +71,4 @@ transaction.sign(baseAccountKey) # base account must sign to approve the payment
 transaction.sign(channelKeys[channelIndex]) # channel must sign to approve it being the source of the transaction
 ```
 
-</CodeExample>
+</CodeGroup>
diff --git a/docs/build/guides/transactions/claimable-balances.mdx b/docs/build/guides/transactions/claimable-balances.mdx
index f3623127c..22a4308dc 100644
--- a/docs/build/guides/transactions/claimable-balances.mdx
+++ b/docs/build/guides/transactions/claimable-balances.mdx
@@ -1,11 +1,8 @@
 ---
 title: Claimable balances
 description: Split a payment into two parts by creating a claimable balance.
-sidebar_position: 20
 ---
 
-import Details from "@theme/Details";
-
 Claimable balances were introduced in [CAP-23](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0023.md) and are used to split a payment into two parts.
 
 - Part 1: sending account creates a payment, or ClaimableBalanceEntry, using the Create Claimable Balance operation
@@ -23,7 +20,7 @@ Once a ClaimableBalanceEntry has been claimed, it is deleted.
 
 ### Create Claimable Balance
 
-For basic parameters, see the Create Claimable Balance entry in our [List of Operations section](../../../learn/fundamentals/transactions/list-of-operations.mdx#create-claimable-balance).
+For basic parameters, see the Create Claimable Balance entry in our [List of Operations section](../../../learn/fundamentals/transactions/list-of-operations#create-claimable-balance).
 
 #### Additional parameters
 
@@ -55,7 +52,7 @@ This operation claws back a claimable balance, returning the asset to the issuer
 
 Clawback claimable balances require the claimable balance ID.
 
-Learn more about clawbacks in our [Clawback Guide](./clawbacks.mdx).
+Learn more about clawbacks in our [Clawback Guide](./clawbacks).
 
 ## Example
 
@@ -65,11 +62,11 @@ Each of these accounts can only claim the balance under unique conditions. Accou
 
 **Note:** there is no recovery mechanism for a claimable balance in general — if none of the predicates can be fulfilled, the balance cannot be recovered. The reclaim example below acts as a safety net for this situation.
 
-<Details summary="Click here to see helper functions">
+<Accordion title="Click here to see helper functions">
 
-<CodeExample>
+<CodeGroup>
 
-```go
+```go Go
 func fundAccount(rpcClient *client.Client, address string) error {
 	ctx := context.Background()
 
@@ -103,13 +100,13 @@ func panicIf(err error) {
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
-</Details>
+</Accordion>
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 import * as StellarSdk from "@stellar/stellar-sdk";
 
 /**
@@ -215,7 +212,7 @@ async function createClaimableBalance() {
 createClaimableBalance();
 ```
 
-```go
+```go Go
 package main
 
 import (
@@ -364,13 +361,13 @@ func extractBalanceID(resp *protocol.GetTransactionResponse) (string, error) {
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
-At this point, the `ClaimableBalanceEntry` exists in the ledger, but we’ll need its Balance ID to claim it. You can call the RPC's [`getLedgerEntries`](../../../data/apis/rpc/api-reference/methods/getLedgerEntries.mdx) endpoint to do this.
+At this point, the `ClaimableBalanceEntry` exists in the ledger, but we’ll need its Balance ID to claim it. You can call the RPC's [`getLedgerEntries`](../../../data/apis/rpc/api-reference/methods/getLedgerEntries) endpoint to do this.
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 import * as StellarSdk from "@stellar/stellar-sdk";
 
 // Replace with your actual Claimable Balance ID
@@ -436,7 +433,7 @@ async function fetchClaimableBalance(balanceId) {
 fetchClaimableBalance(BALANCE_ID);
 ```
 
-```go
+```go Go
 package main
 
 import (
@@ -510,13 +507,13 @@ func main() {
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
 With the Claimable Balance ID acquired, either Account B or A can actually submit a claim, depending on which predicate is fulfilled. We’ll assume here that a minute has passed, so Account A just reclaims the balance entry.
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 import * as StellarSdk from "@stellar/stellar-sdk";
 
 // Replace with your claimable balance ID
@@ -586,7 +583,7 @@ async function claimClaimableBalance(balanceId, claimantSecret) {
 claimClaimableBalance(BALANCE_ID, CLAIMANT_SECRET);
 ```
 
-```go
+```go Go
 package main
 
 import (
@@ -697,6 +694,6 @@ func main() {
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
 And that’s it! Since we opted for the reclaim path, Account A should have the same balance as what it started with (minus fees), and Account B should be unchanged.
diff --git a/docs/build/guides/transactions/clawbacks.mdx b/docs/build/guides/transactions/clawbacks.mdx
index 389d32014..3bd3246c5 100644
--- a/docs/build/guides/transactions/clawbacks.mdx
+++ b/docs/build/guides/transactions/clawbacks.mdx
@@ -1,7 +1,6 @@
 ---
 title: Clawbacks
 description: Use clawbacks to burn a specific amount of a clawback-enabled asset from a trustline or claimable balance.
-sidebar_position: 30
 ---
 
 Clawbacks were introduced in [CAP-35: Asset Clawback](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0035.md) and allow an asset issuer to burn a specific amount of a clawback-enabled asset from a trustline or claimable balance, effectively destroying it and removing it from a recipient's balance.
@@ -24,15 +23,15 @@ If an issuing account wants to set the `AUTH_CLAWBACK_ENABLED_FLAG`, it must hav
 
 ### Clawback
 
-The issuing account uses this operation to claw back some or all of an asset. Once an account holds a particular asset for which clawbacks have been enabled, the issuing account can claw it back, burning it. You need to provide the asset, a quantity, and the account from which you're clawing back the asset. For more details, refer the [Clawback operation](../../../learn/fundamentals/transactions/list-of-operations.mdx#clawback).
+The issuing account uses this operation to claw back some or all of an asset. Once an account holds a particular asset for which clawbacks have been enabled, the issuing account can claw it back, burning it. You need to provide the asset, a quantity, and the account from which you're clawing back the asset. For more details, refer the [Clawback operation](../../../learn/fundamentals/transactions/list-of-operations#clawback).
 
 ### Clawback Claimable Balance
 
-This operation claws back a claimable balance, returning the asset to the issuer account, burning it. You must claw back the entire claimable balance, not just part of it. Once a claimable balance has been claimed, use the regular clawback operation to claw it back. Clawback claimable balances require the claimable balance ID. For more details, refer the [Clawback Claimable Balance operation](../../../learn/fundamentals/transactions/list-of-operations.mdx#clawback-claimable-balance).
+This operation claws back a claimable balance, returning the asset to the issuer account, burning it. You must claw back the entire claimable balance, not just part of it. Once a claimable balance has been claimed, use the regular clawback operation to claw it back. Clawback claimable balances require the claimable balance ID. For more details, refer the [Clawback Claimable Balance operation](../../../learn/fundamentals/transactions/list-of-operations#clawback-claimable-balance).
 
 ### Set Trust Line Flag
 
-The issuing account uses this operation to remove clawback capabilities on a specific trustline by removing the `TRUSTLINE_CLAWBACK_ENABLED_FLAG` via the [**SetTrustLineFlags**](../../../learn/fundamentals/transactions/list-of-operations.mdx#set-trustline-flags) operation.
+The issuing account uses this operation to remove clawback capabilities on a specific trustline by removing the `TRUSTLINE_CLAWBACK_ENABLED_FLAG` via the [**SetTrustLineFlags**](../../../learn/fundamentals/transactions/list-of-operations#set-trustline-flags) operation.
 
 You can only clear a flag, not set it. So clearing a clawback flag on a trustline is irreversible. This is done so that you don't retroactively change the rules on your asset holders. If you'd like to enable clawbacks again, holders must reissue their trustlines.
 
@@ -42,7 +41,7 @@ Here we'll cover the following approaches to clawing back an asset.
 
 **Example 1:** Issuing account (Account A) creates a clawback-enabled asset and sends it to Account B. Account B sends that asset to Account C. Account A will then clawback the asset from C. **Example 2:** Account B creates a claimable balance for Account C, and Account A claws back the claimable balance. **Example 3:** Account A issues a clawback-enabled asset to Account B. A claws back some of the asset from B, then removes the clawback enabled flag from the trustline and can no longer clawback the asset.
 
-### Preamble: Creating + Funding Accounts and Issuing a Clawback-able Asset
+### Preamble: Creating + Funding Accounts and Issuing a Clawback-able Asset {#preamble-creating--funding-accounts-and-issuing-a-clawback-able-asset}
 
 First, we'll set up an account to enable clawbacks and issue an asset accordingly.
 
@@ -52,9 +51,9 @@ Also, note that we first need to enable clawbacks and then establish trustlines
 
 The following code snippet contains helper functions that will be used in the following examples.
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 import * as sdk from "@stellar/stellar-sdk";
 
 let server = new sdk.rpc.Server("https://soroban-testnet.stellar.org");
@@ -396,7 +395,7 @@ function preamble() {
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Example 1: Payments
 
@@ -408,9 +407,9 @@ In this scenario:
 - Account B will then pay Account C 500 tokens in turn.
 - Finally, Account A will claw back half of Account C's balance, burning 250 CLAW tokens.
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 function examplePaymentAndThenClawback() {
   console.log("\n=== PAYMENT AND CLAWBACK EXAMPLE ===");
   return getAccounts()
@@ -467,7 +466,7 @@ function runExample1() {
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
 When you invoke `runExample1()`, you should see output similar to:
 
@@ -536,12 +535,11 @@ GDYIV7XB (Account A): 0 CLAW
 === CLAWBACK DEMO COMPLETED ===
 ```
 
-<details>
-  <summary>Clawback Flow Chart</summary>
+<Accordion title="Clawback Flow Chart">
 
 ![example1](/assets/clawback/example1.png)
 
-</details>
+</Accordion>
 
 Notice that Account A (the issuer) holds none of the asset despite clawing back 250 from Account C. This should drive home the fact that clawed-back assets are burned, not transferred.
 
@@ -558,9 +556,9 @@ In this scenario:
 - Account A then claws back the Claimable Balance from Account C.
 - The Claimable Balance entry is deleted and no longer queryable.
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 function exampleClaimableBalanceClawback() {
   console.log("\n=== CLAIMABLE BALANCE CLAWBACK EXAMPLE ===");
   let balanceId;
@@ -640,7 +638,7 @@ function runExample2() {
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
 When you invoke `runExample2()`, you should see output similar to:
 
@@ -741,9 +739,9 @@ In this scenario:
 
 _Please note that Account C is not relevant in this example._
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 function exampleSelectiveClawbackThenDisableClawback() {
   console.log("\n=== SELECTIVE CLAWBACK EXAMPLE ===");
   return getAccounts()
@@ -811,7 +809,7 @@ function runExample3() {
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
 When you invoke `runExample3()`, you should see output similar to:
 
diff --git a/docs/build/guides/transactions/create-account.mdx b/docs/build/guides/transactions/create-account.mdx
index 69bbbff45..bab0f877f 100644
--- a/docs/build/guides/transactions/create-account.mdx
+++ b/docs/build/guides/transactions/create-account.mdx
@@ -1,14 +1,12 @@
 ---
-title: Create an account
-sidebar_position: 5
+title: Create an Account
+sidebarTitle: Create an account
 description: Learn about creating Stellar accounts, keypairs, funding, and account basics.
 ---
 
-# Create an Account
-
 _Before we get started with working with Stellar in code, consider going through the following examples using the [Stellar Lab](https://lab.stellar.org). The lab allows you to create accounts, fund accounts on the Stellar test network, build transactions, run any operation, and inspect responses from Horizon via the Endpoint Explorer._
 
-[Accounts](../../../learn/fundamentals/stellar-data-structures/accounts.mdx) are a fundamental building block of Stellar: they hold all your balances, allow you to send and receive payments, and let you place offers to buy and sell assets. Since pretty much everything on Stellar is in some way tied to an account, the first thing you generally need to do when you start developing is create one. This beginner-level tutorial walks through the three building blocks you'll need: [generating keys](#create-a-keypair), [funding an account](#create-an-account), and [fetching balances](#fetch-balances).
+[Accounts](../../../learn/fundamentals/stellar-data-structures/accounts) are a fundamental building block of Stellar: they hold all your balances, allow you to send and receive payments, and let you place offers to buy and sell assets. Since pretty much everything on Stellar is in some way tied to an account, the first thing you generally need to do when you start developing is create one. This beginner-level tutorial walks through the three building blocks you'll need: [generating keys](#create-a-keypair), [funding an account](#create-an-account), and [fetching balances](#fetch-balances).
 
 ## Create a Keypair
 
@@ -16,15 +14,15 @@ Stellar uses public key cryptography to secure every transaction: each Stellar a
 
 Before creating an account, you need to generate your own keypair; we'll learn how in the [full example](#full-example), below.
 
-## Create an Account
+## Create an Account {#create-an-account-1}
 
-A valid keypair alone does not make an account. To prevent unused entries from bloating the ledger, Stellar requires every account to hold a [minimum balance](../../../learn/fundamentals/lumens.mdx#minimum-balance) of two base reserves before it actually exists (at the current base reserve of 0.5 XLM that works out to 1 XLM, but validators can change the base reserve — see the linked section for the current value). This is the ordinary, self-funded path shown throughout this tutorial.
+A valid keypair alone does not make an account. To prevent unused entries from bloating the ledger, Stellar requires every account to hold a [minimum balance](../../../learn/fundamentals/lumens#minimum-balance) of two base reserves before it actually exists (at the current base reserve of 0.5 XLM that works out to 1 XLM, but validators can change the base reserve — see the linked section for the current value). This is the ordinary, self-funded path shown throughout this tutorial.
 
-Alternatively, an account can be created with a `startingBalance` of `0` when another account sponsors its reserves ([CAP-33](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0033.md) sponsored reserves): the sponsor carries the two base reserves on the new account's behalf, so the account exists without holding the minimum balance itself. See the [Sponsored Reserves guide](sponsored-reserves.mdx) for how to set this up.
+Alternatively, an account can be created with a `startingBalance` of `0` when another account sponsors its reserves ([CAP-33](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0033.md) sponsored reserves): the sponsor carries the two base reserves on the new account's behalf, so the account exists without holding the minimum balance itself. See the [Sponsored Reserves guide](/docs/build/guides/transactions/sponsored-reserves) for how to set this up.
 
 On the test network you can ask Friendbot — a friendly funding service — to create and fund the account for you. In the SDK examples, below, you'll see that we "discover" the Friendbot endpoint via the RPC's `getNetwork` call, then issue a funding request.
 
-On the public network, things are a little different. You'd acquire lumens from an exchange or have someone create or sponsor an account on your behalf. This is the purpose of the [`CreateAccount` operation](../../../learn/fundamentals/transactions/list-of-operations.mdx#create-account). We'll see in the examples, later, that given a funded account, you can then create a child account on the network with a starting balance.
+On the public network, things are a little different. You'd acquire lumens from an exchange or have someone create or sponsor an account on your behalf. This is the purpose of the [`CreateAccount` operation](../../../learn/fundamentals/transactions/list-of-operations#create-account). We'll see in the examples, later, that given a funded account, you can then create a child account on the network with a starting balance.
 
 ## Fetch Balances
 
@@ -40,11 +38,11 @@ You'll learn about these in later tutorials.
 
 Let's combine these four concepts into a single cohesive example. Keep in mind that you will always see your USDC balance as zero, since we did not actually receive any of it, but it will be useful in the future when you hold more than just the native token.
 
-For each of these, be sure to follow the installation and setup instructions corresponding to each SDK from their [documentation](../../../tools/sdks/client-sdks.mdx).
+For each of these, be sure to follow the installation and setup instructions corresponding to each SDK from their [documentation](../../../tools/sdks/client-sdks).
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 import {
   Keypair,
   BASE_FEE,
@@ -134,7 +132,7 @@ async function main() {
 main().catch((err) => console.error(err));
 ```
 
-```python
+```python Python
 import requests
 from stellar_sdk import *
 from stellar_sdk.soroban_rpc import GetTransactionStatus, SendTransactionStatus
@@ -265,7 +263,7 @@ if __name__ == "__main__":
     main()
 ```
 
-```go
+```go Go
 package main
 
 import (
@@ -480,7 +478,7 @@ func check(err error) {
 }
 ```
 
-```java
+```java Java
 // File: main.java
 // Dependencies (Maven coordinates):
 //   network.lightsail:stellar-sdk:3.1.0
@@ -625,7 +623,7 @@ public final class main {
 }
 ```
 
-```rust
+```rust Rust
 use std::{cell::RefCell, rc::Rc, time::Duration};
 
 use soroban_client::{
@@ -715,6 +713,6 @@ pub async fn main() -> Result<(), Box<dyn std::error::Error>> {
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
-Now that you’ve got an account and check its asset balances, you can [start sending and receiving payments](send-and-receive-payments.mdx), or, if you're ready to hunker down, you can skip ahead and [build a wallet](../../apps/wallet/overview.mdx) or [issue a Stellar asset](../../../tokens/anatomy-of-an-asset.mdx).
+Now that you’ve got an account and check its asset balances, you can [start sending and receiving payments](/docs/build/guides/transactions/send-and-receive-payments), or, if you're ready to hunker down, you can skip ahead and [build a wallet](../../apps/wallet/overview) or [issue a Stellar asset](../../../tokens/anatomy-of-an-asset).
diff --git a/docs/build/guides/transactions/fee-bump-transactions.mdx b/docs/build/guides/transactions/fee-bump-transactions.mdx
index e8bed2615..99157f915 100644
--- a/docs/build/guides/transactions/fee-bump-transactions.mdx
+++ b/docs/build/guides/transactions/fee-bump-transactions.mdx
@@ -1,7 +1,6 @@
 ---
 title: Fee-bump transactions
 description: Use fee-bump transactions to pay for transaction fees on behalf of another account without re-signing the transaction.
-sidebar_position: 40
 ---
 
 Fee-bump transactions were introduced in [CAP-15](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) and enable an account to pay the transaction fees for an existing transaction without having to re-sign the transaction or manage sequence numbers.
@@ -21,11 +20,11 @@ You may want to consider using fee bumps when:
 - You want to increase the fee on an existing transaction so it has a better chance of making it to the ledger during surge pricing
 - You need to adjust the fee on a pre-authorized transaction so it can make it to the ledger if minimum network fees have increased
 
-:::note
+<Note>
 
-Use the [Stellar Wallet Sponsorship Calculator](../../../tools/developer-tools/wallets.mdx#stellar-wallet-sponsorship-calculator) to estimate the XLM requirements for wallets looking to use sponsored reserves and fee-bump transactions to cover account creation, transaction fees, trustlines, and more.
+Use the [Stellar Wallet Sponsorship Calculator](../../../tools/developer-tools/wallets#stellar-wallet-sponsorship-calculator) to estimate the XLM requirements for wallets looking to use sponsored reserves and fee-bump transactions to cover account creation, transaction fees, trustlines, and more.
 
-:::
+</Note>
 
 ## Attributes
 
@@ -41,7 +40,7 @@ The account that will pay the fee for the fee-bump transaction. This account wil
 
 The maximum per-operation fee you’re willing to pay for the fee-bump transaction. The fee-bump transaction is one operation. Therefore, the total number of operations is equal to the number of operations in the inner transaction plus one.
 
-Read more about transaction fees in our [Fees section](../../../learn/fundamentals/fees-resource-limits-metering.mdx).
+Read more about transaction fees in our [Fees section](../../../learn/fundamentals/fees-resource-limits-metering).
 
 ### Replace-by-fee
 
@@ -62,7 +61,7 @@ A fee-bump transaction goes through a series of checks in its lifecycle to deter
   - If the fee-bump transaction is taking advantage of the replace-by-fee, the fee must be 10x higher than the first transaction
 - **Fee account signature** — the fee-bump transaction envelope must contain a valid signature for the fee account. Additionally, the weight of that signature must meet the low threshold for the fee account, and the appropriate network passphrase must be part of the transaction hash signed by the fee account.
 - **Fee account balance** — the fee account must have a sufficient XLM balance to cover the fee
-- **Inner transaction** — the inner transaction must be valid, which means it must meet the requirements described in the [Validity of a Transaction section](../../../learn/fundamentals/transactions/operations-and-transactions.mdx#transaction-and-operation-validity). If validation of the inner transaction is successful, then the result is `FEE_BUMP_INNER_SUCCESS`, and the validation results from the validation of the inner transaction appear in the inner result. If the inner transaction is invalid, the result is `FEE_BUMP_INNER_FAILED`, and the fee-bump transaction is invalid because the inner transaction is invalid.
+- **Inner transaction** — the inner transaction must be valid, which means it must meet the requirements described in the [Validity of a Transaction section](../../../learn/fundamentals/transactions/operations-and-transactions#transaction-and-operation-validity). If validation of the inner transaction is successful, then the result is `FEE_BUMP_INNER_SUCCESS`, and the validation results from the validation of the inner transaction appear in the inner result. If the inner transaction is invalid, the result is `FEE_BUMP_INNER_FAILED`, and the fee-bump transaction is invalid because the inner transaction is invalid.
 
 ## Application
 
@@ -74,9 +73,9 @@ Every fee-bump transaction result contains a complete inner transaction result.
 
 This example shows how to create and submit a fee-bump transaction on the Stellar network. Replace secret key values, `SECREY_KEY_1` and `SECREY_KEY_2` of keypairs of your choosing. This is not a production example, and you should take care to never expose your secret keys on the web.
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 import * as StellarSdk from "@stellar/stellar-sdk";
 
 // Define the network passphrase (use 'Testnet' for testing and 'Public Global Stellar Network ; September 2015' for production)
@@ -141,4 +140,4 @@ server
   });
 ```
 
-</CodeExample>
+</CodeGroup>
diff --git a/docs/build/guides/transactions/fee-sponsorship.mdx b/docs/build/guides/transactions/fee-sponsorship.mdx
index 2f4b4ceb3..9c5398205 100644
--- a/docs/build/guides/transactions/fee-sponsorship.mdx
+++ b/docs/build/guides/transactions/fee-sponsorship.mdx
@@ -1,7 +1,6 @@
 ---
 title: Choose a fee sponsorship approach
 description: Compare fee-bump transactions, sponsored reserves, and relayers for paying a user's fees and reserves on the Stellar network.
-sidebar_position: 35
 ---
 
 A new user often has no XLM to pay transaction fees or base reserves. If the user has a contract account, such as a passkey smart wallet, it can't pay its own fees at all: contract accounts can't sign transaction envelopes, so a separate G-account must act as the transaction source.
@@ -24,7 +23,7 @@ Use a fee-bump transaction when the user signs their own transaction from a G-ac
 
 The fee account pays the fee instead of the inner transaction's source account, but the inner transaction still consumes the source account's sequence number. A contract account can't sign the inner transaction, so a fee-bump on its own doesn't cover a contract account's fees.
 
-Learn more in the [Fee-bump transactions](./fee-bump-transactions.mdx) guide.
+Learn more in the [Fee-bump transactions](/docs/build/guides/transactions/fee-bump-transactions) guide.
 
 ### Sponsored reserves
 
@@ -34,7 +33,7 @@ Both accounts sign the sponsorship transaction, so the user agrees to it. While
 
 Smart contract data doesn't require base reserves; it pays rent instead. A contract account is a smart contract, so sponsored reserves don't cover its storage.
 
-Learn more in the [Sponsored reserves](./sponsored-reserves.mdx) guide.
+Learn more in the [Sponsored reserves](/docs/build/guides/transactions/sponsored-reserves) guide.
 
 ### Relayers
 
@@ -42,17 +41,19 @@ Use a relayer when the user has a contract account, or when the user holds no XL
 
 You can run a relayer yourself, in which case you control its signer and fund the accounts that pay the fees, or you can use a managed relayer service.
 
-Learn more about the signing flow in [Signing Soroban contract invocations](./signing-soroban-invocations.mdx#method-2-auth-entry-signing).
+Learn more about the signing flow in [Signing Soroban contract invocations](/docs/build/guides/transactions/signing-soroban-invocations#method-2-auth-entry-signing).
 
-:::info[Current recommendation (as of October 2026)]
+<Info>
 
-For managed fee sponsorship, see the [OpenZeppelin Relayer](../../../tools/openzeppelin-relayer.mdx) page. This recommendation changes over time; the page linked here stays current.
+**Current recommendation (as of October 2026)**
 
-:::
+For managed fee sponsorship, see the [OpenZeppelin Relayer](/docs/tools/openzeppelin-relayer) page. This recommendation changes over time; the page linked here stays current.
+
+</Info>
 
 ## Combining approaches
 
 These approaches can work together:
 
-- **Sponsored reserves and fee-bumps:** a wallet that onboards G-accounts can sponsor each account's reserves and fee-bump its transactions. To estimate the XLM you need for account creation, transaction fees, and trustlines, use the [Stellar Wallet Sponsorship Calculator](../../../tools/developer-tools/wallets.mdx#stellar-wallet-sponsorship-calculator).
-- **Relayers and fee-bumps:** a relayer can wrap the transactions it submits in fee-bump transactions, which separates the account that spends the sequence number from the account that pays the fees. A relayer can also use [channel accounts](./channel-accounts.mdx) to submit transactions in parallel.
+- **Sponsored reserves and fee-bumps:** a wallet that onboards G-accounts can sponsor each account's reserves and fee-bump its transactions. To estimate the XLM you need for account creation, transaction fees, and trustlines, use the [Stellar Wallet Sponsorship Calculator](/docs/tools/developer-tools/wallets#stellar-wallet-sponsorship-calculator).
+- **Relayers and fee-bumps:** a relayer can wrap the transactions it submits in fee-bump transactions, which separates the account that spends the sequence number from the account that pays the fees. A relayer can also use [channel accounts](/docs/build/guides/transactions/channel-accounts) to submit transactions in parallel.
diff --git a/docs/build/guides/transactions/index.mdx b/docs/build/guides/transactions/index.mdx
new file mode 100644
index 000000000..c62c0bb43
--- /dev/null
+++ b/docs/build/guides/transactions/index.mdx
@@ -0,0 +1,6 @@
+---
+title: Transactions
+description: "Stellar transactions are comprised of operations. These guides will walk you through various Stellar operations, non-contract transactions, and smart contract transactions."
+---
+
+Read more about operations and transactions in the [Operations and Transactions section](/docs/learn/fundamentals/transactions).
diff --git a/docs/build/guides/transactions/install-deploy-contract-with-code.mdx b/docs/build/guides/transactions/install-deploy-contract-with-code.mdx
index 5ae5d69a8..8fd08fbf6 100644
--- a/docs/build/guides/transactions/install-deploy-contract-with-code.mdx
+++ b/docs/build/guides/transactions/install-deploy-contract-with-code.mdx
@@ -1,21 +1,10 @@
 ---
 title: Install and deploy a smart contract with code
+og:title: "Install and deploy a smart contract with code"
+og:description: "This guide will walk you through the process of installing and deploying a smart contract using js-stellar-sdk. We will cover the setup of a sample Rust contract, creating a Node.js project to manage the deployment, and finally, installing the Wasm of the contract and deploying it to the network"
 description: Install and deploy a smart contract with code.
 ---
 
-<head>
-  <title>Install and deploy a smart contract with code</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Install and deploy a smart contract with code"
-  />
-  <meta
-    property="og:description"
-    content="This guide will walk you through the process of installing and deploying a smart contract using js-stellar-sdk. We will cover the setup of a sample Rust contract, creating a Node.js project to manage the deployment, and finally, installing the Wasm of the contract and deploying it to the network"
-  />
-</head>
-
 This guide will walk you through the process of installing and deploying a smart contract using [js-stellar-sdk](https://github.com/stellar/js-stellar-sdk). We will cover the setup of a sample Rust contract, creating a Node.js project to manage the deployment, and finally, installing the Wasm of the contract and deploying it to the network
 
 ## Prerequisites
@@ -24,7 +13,7 @@ Before you begin, ensure you have the following installed:
 
 1. [Rust](https://www.rust-lang.org) and Cargo (for compiling smart contracts)
 2. [Node.js](https://nodejs.org/en) and npm (for running JavaScript deployment scripts)
-3. [Stellar CLI](../../smart-contracts/getting-started/setup.mdx#install-the-stellar-cli)
+3. [Stellar CLI](../../smart-contracts/getting-started/setup#install-the-stellar-cli)
 
 ## Initialize a sample Rust Contract
 
diff --git a/docs/build/guides/transactions/invoke-contract-tx-sdk.mdx b/docs/build/guides/transactions/invoke-contract-tx-sdk.mdx
index 3cb55e56b..acbb2b484 100644
--- a/docs/build/guides/transactions/invoke-contract-tx-sdk.mdx
+++ b/docs/build/guides/transactions/invoke-contract-tx-sdk.mdx
@@ -1,24 +1,20 @@
 ---
 title: Invoke a contract function in a transaction using SDKs
-hide_table_of_contents: true
 description: Use the Stellar SDK to create, simulate, and assemble a transaction.
 ---
 
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-This is a simple example using the Stellar SDK to create, simulate, and then assemble a Stellar transaction which invokes an `increment` function of the [auth example contract](../../smart-contracts/example-contracts/auth.mdx).
+This is a simple example using the Stellar SDK to create, simulate, and then assemble a Stellar transaction which invokes an `increment` function of the [auth example contract](../../smart-contracts/example-contracts/auth).
 
 <Tabs>
-<TabItem value="js" label="JavaScript">
+<Tab title="JavaScript">
 
-:::tip
+<Tip>
 
 Please go to [the project homepage](https://github.com/stellar/js-stellar-sdk) of JavaScript SDK to learn how to install it.
 
-:::
+</Tip>
 
-First, upload the bytes of [the example contract](../../smart-contracts/example-contracts/auth.mdx) onto the blockchain using [Stellar CLI](../../../tools/cli/stellar-cli.mdx). This is called "install" because, from the perspective of the blockchain itself, this contract has been installed.
+First, upload the bytes of [the example contract](../../smart-contracts/example-contracts/auth) onto the blockchain using [Stellar CLI](../../../tools/cli/stellar-cli). This is called "install" because, from the perspective of the blockchain itself, this contract has been installed.
 
 ```bash
 stellar contract build
@@ -83,7 +79,9 @@ async function generateFundedKeypair() {
   ...
 ```
 
-:::tip[Client from existing Contract]
+<Tip>
+
+**Client from existing Contract**
 
 If you don't need to deploy a contract, and instead already know a deployed contract's ID, you can instantiate a Client for it directly. This uses similar arguments to the ones to `Client.deploy` above, with the addition of `contractId`:
 
@@ -101,7 +99,7 @@ If you don't need to deploy a contract, and instead already know a deployed cont
  })
 ```
 
-:::
+</Tip>
 
 Now that we instantiated a `client`, we can use it to call methods on the contract. Picking up where we left off:
 
@@ -126,17 +124,17 @@ Now that we instantiated a `client`, we can use it to call methods on the contra
 })();
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="py" label="Python">
+<Tab title="Python">
 
-:::tip
+<Tip>
 
 Please go to [the project homepage](https://github.com/StellarCN/py-stellar-base) of Python SDK to learn how to install it.
 
 In addition, Python provides a lot of example code, which you can find [here](https://github.com/StellarCN/py-stellar-base/tree/main/examples).
 
-:::
+</Tip>
 
 ```py
 import time
@@ -225,15 +223,15 @@ else:
     raise Exception("Transaction failed")
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="java" label="Java">
+<Tab title="Java">
 
-:::tip
+<Tip>
 
 Please go to [the project homepage](https://github.com/lightsail-network/java-stellar-sdk) of Java SDK to learn how to install it.
 
-:::
+</Tip>
 
 ```java
 import org.stellar.sdk.KeyPair;
@@ -345,18 +343,18 @@ public class Example {
 }
 ```
 
-</TabItem>
-<TabItem value="rust" label="Rust">
+</Tab>
+<Tab title="Rust">
 
-:::tip
+<Tip>
 
 Please go to [the project homepage](https://github.com/rahul-soshte/rs-soroban-client) of Rust Soroban Client Library to learn how to install it.
 
 Other examples can be found in the [`examples/`](https://github.com/rahul-soshte/rs-soroban-client/tree/main/examples) folder of the repository.
 
-:::
+</Tip>
 
-First, deploy [the example contract](../../smart-contracts/example-contracts/auth.mdx) onto the blockchain using [Stellar CLI](../../../tools/cli/stellar-cli.mdx).
+First, deploy [the example contract](../../smart-contracts/example-contracts/auth) onto the blockchain using [Stellar CLI](../../../tools/cli/stellar-cli).
 
 ```bash
 stellar contract build
@@ -445,5 +443,5 @@ pub async fn main() -> Result<(), Box<dyn std::error::Error>> {
 }
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
diff --git a/docs/build/guides/transactions/path-payments.mdx b/docs/build/guides/transactions/path-payments.mdx
index 5983d2c63..8feea0cf9 100644
--- a/docs/build/guides/transactions/path-payments.mdx
+++ b/docs/build/guides/transactions/path-payments.mdx
@@ -1,6 +1,5 @@
 ---
 title: Path payments
-sidebar_position: 60
 description: Send a payment where the asset received differs from the asset sent.
 ---
 
@@ -12,7 +11,7 @@ Account A sells XLM → [buy XLM / sell ETH → buy ETH / sell BTC → buy BTC /
 
 It is possible for path payments to fail if there are no viable exchange paths.
 
-For more information on the Stellar Decentralized Exchange and Liquidity Pools, see the [Liquidity on Stellar section](../../../learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx).
+For more information on the Stellar Decentralized Exchange and Liquidity Pools, see the [Liquidity on Stellar section](../../../learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools).
 
 ## Operations
 
@@ -26,7 +25,7 @@ Allows a user to specify the amount of the asset to send. The amount received wi
 
 Allows a user to specify the amount of the asset received. The amount sent will vary based on the offers in the order books/liquidity pools.
 
-## Path payments - more info
+## Path payments - more info {#path-payments---more-info}
 
 - Path payments don’t allow intermediate offers to be from the source account as this would yield a worse exchange rate. You’ll need to either split the path payment into two smaller path payments or ensure that the source account’s offers are not at the top of the order book.
 - Balances are settled at the very end of the operation.
diff --git a/docs/build/guides/transactions/pooled-accounts-muxed-accounts-memos.mdx b/docs/build/guides/transactions/pooled-accounts-muxed-accounts-memos.mdx
index 812c82fbb..af7ecae32 100644
--- a/docs/build/guides/transactions/pooled-accounts-muxed-accounts-memos.mdx
+++ b/docs/build/guides/transactions/pooled-accounts-muxed-accounts-memos.mdx
@@ -1,18 +1,17 @@
 ---
 title: "Pooled accounts: muxed accounts and memos"
 description: Use muxed accounts to differentiate between individual accounts in a pooled account.
-sidebar_position: 60
 ---
 
 When building an application or service on Stellar, one of the first things you have to decide is how to handle user accounts.
 
 You can create a Stellar account for each user, but most custodial services, including cryptocurrency exchanges, choose to use a single pooled Stellar account to handle transactions on behalf of their users. In these cases, an internal customer database maps transactions to individual accounts, using either the muxed account feature or transaction memos.
 
-:::note
+<Note>
 
 Transaction memos were traditionally used for this purpose, and many services still rely on them. Muxed accounts are better in the long term, but they aren't yet supported by all wallets, exchanges, and anchors, so you may want to support both memos and muxed accounts, at least for a while. This guide covers both approaches.
 
-:::
+</Note>
 
 ## Pooled accounts
 
@@ -68,17 +67,17 @@ Muxed accounts (M...) are a client-side abstraction that don't actually exist on
 
 **Transaction Fees:** All transactions incur a fee (typically 100 stroops or 0.0000100 XLM). Since the custodian account is the source of all transactions in these examples, fees are always debited from the custodian's balance. You'll see this reflected in the before/after balance comparisons, where the custodian account decreases by both the payment amount and the transaction fee.
 
-### Example 1 - Basic Payment (G → G)
+### Example 1 - Basic Payment (G → G) {#example-1---basic-payment-g--g}
 
 This example establishes baseline behavior with a standard payment between two regular Stellar accounts. Both accounts exist directly on the ledger, demonstrating traditional Stellar payment flow without muxed account abstractions. The custodian account balance decreases by 10 XLM plus transaction fees, while the outsider account increases by exactly 10 XLM.
 
-### Example 2 - Muxed to Unmuxed Payment (M → G)
+### Example 2 - Muxed to Unmuxed Payment (M → G) {#example-2---muxed-to-unmuxed-payment-m--g}
 
 This demonstrates a payment from a muxed account (representing a custodial customer) to a regular Stellar account. The underlying custodian account executes the payment, but the transaction includes the muxed address to identify which customer initiated it.
 
 The transaction is signed with custodian keys since muxed accounts have no secret keys. The custodian account balance decreases by 10 XLM plus fees.
 
-### Example 3 - Muxed to Muxed Payment (M → M)
+### Example 3 - Muxed to Muxed Payment (M → M) {#example-3---muxed-to-muxed-payment-m--m}
 
 When two muxed accounts share the same underlying account, payments between them are essentially the account sending to itself. The payment amount (+10 XLM and -10 XLM) cancels out, but transaction fees are still charged since the operation is recorded on the ledger.
 
@@ -90,9 +89,9 @@ The account balance decreases only by the transaction fee. You may want to detec
 
 _The following code demonstrates all three examples using Stellar RPC. You can run all examples sequentially with `runAllMuxedExamples()` or execute individual examples using their respective functions._
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 import * as sdk from "@stellar/stellar-sdk";
 
 const server = new sdk.rpc.Server("https://soroban-testnet.stellar.org");
@@ -350,7 +349,7 @@ async function makePayment(source, dest, description = "Payment") {
 runAllMuxedExamples();
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Running the Examples
 
@@ -408,9 +407,9 @@ Only certain operations allow muxed accounts, as described above. Passing a muxe
 
 For example, when using the JavaScript SDK incorrectly:
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 const mAddress =
   "MA7QYNF7SOWQ3GLR2BGMZEHXAVIRZA4KVWLTJJFC7MGXUA74P7UJUAAAAAAAAAABUTGI4";
 transactionBuilder.addOperation(
@@ -422,7 +421,7 @@ transactionBuilder.addOperation(
 );
 ```
 
-</CodeExample>
+</CodeGroup>
 
 The runtime result would be:
 
@@ -443,11 +442,11 @@ namespace StrKey {
 
 There are also abstractions for constructing and managing both muxed and regular accounts; consult your SDK documentation for details.
 
-## Memo - differentiated accounts
+## Memo - differentiated accounts {#memo---differentiated-accounts}
 
 Prior to the introduction of muxed accounts, products and services that relied on pooled accounts often used transaction memos to differentiate between users. Supporting muxed accounts is better in the long term, but for now you may want to support both memos and muxed accounts as all exchanges, anchors, and wallets may not support muxed accounts.
 
-To learn about what other purposes memos can be used for, see our [Memos section](../../../learn/fundamentals/transactions/operations-and-transactions.mdx#memo).
+To learn about what other purposes memos can be used for, see our [Memos section](../../../learn/fundamentals/transactions/operations-and-transactions#memo).
 
 ## Why are muxed accounts better in the long term?
 
diff --git a/docs/build/guides/transactions/send-and-receive-c-accounts.mdx b/docs/build/guides/transactions/send-and-receive-c-accounts.mdx
index 611713391..485d0c5dc 100644
--- a/docs/build/guides/transactions/send-and-receive-c-accounts.mdx
+++ b/docs/build/guides/transactions/send-and-receive-c-accounts.mdx
@@ -1,16 +1,13 @@
 ---
 title: "Send to and receive payments from Contract Accounts"
 description: "Learn to send payments to and receive payments from Contract Accounts on the Stellar network."
-sidebar_position: 7
 ---
 
-import Details from "@theme/Details";
-
 Payments between Contract Accounts (C addresses) and Classic Accounts (G addresses) are supported on a protocol level, but there are differences in the implementations that are required to support them. This guide will cover implementations for applications that use classic G accounts and want to support transacting with Contract Accounts.
 
 ## Receiving payments from Contract Accounts (C to G)
 
-If a sender is using a Contract Account, and sending an [SAC token](../../../tokens/stellar-asset-contract.mdx) (such as XLM, USDC, etc.), the transaction will be received by the G account normally since it is supported on a protocol level.
+If a sender is using a Contract Account, and sending an [SAC token](../../../tokens/stellar-asset-contract) (such as XLM, USDC, etc.), the transaction will be received by the G account normally since it is supported on a protocol level.
 
 ### Receiving payments from Contract Accounts requiring a memo
 
@@ -29,7 +26,7 @@ That's the main difference between receiving from customers using G or Contract
 
 **Receiving from a G address**
 
-The memo field will be present in the response of Horizon's [accounts/:account_id/transactions](../../../data/apis/horizon/api-reference/get-transactions-by-account-id.api.mdx) endpoint
+The memo field will be present in the response of Horizon's [accounts/:account_id/transactions](/docs/data/apis/horizon/api-reference/get-transactions-by-account-id) endpoint
 
 **Example response from a G address:**
 
@@ -74,9 +71,9 @@ The memo field will be present in the response of Horizon's [accounts/:account_i
 
 **Receiving from a Contract Account**
 
-The payment details will be present in Horizon's [accounts/:account_id/payments](../../../data/apis/horizon/api-reference/get-payments-by-account-id.api.mdx) endpoint, under 'asset_balance_changes', which will present the encoded ID and the underlying G address separately.
+The payment details will be present in Horizon's [accounts/:account_id/payments](/docs/data/apis/horizon/api-reference/get-payments-by-account-id) endpoint, under 'asset_balance_changes', which will present the encoded ID and the underlying G address separately.
 
-It is important to note the 'asset_balance_changes' section only supports Stellar assets and transactions that make use of the `transfer` function in the [Stellar Asset Contract (SAC)](../../../tokens/stellar-asset-contract.mdx).
+It is important to note the 'asset_balance_changes' section only supports Stellar assets and transactions that make use of the `transfer` function in the [Stellar Asset Contract (SAC)](../../../tokens/stellar-asset-contract).
 
 **Example response from a Contract Account:**
 
@@ -141,7 +138,7 @@ For a detailed code example, see the section 'Monitoring Payments -> Using the H
 
 Since the release of the Unified Asset Events ([CAP-67](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md)) on Protocol 23, a number of transactions involving Stellar assets now emit standardized events that can be ingested by both the Horizon API and the Stellar RPC. If funds are sent through a 'payment' operation or by invoking the 'transfer' function of the asset contract, the same kind of event is emitted for both cases.
 
-To monitor these payments, the method '[getEvents](../../../data/apis/rpc/api-reference/methods/getEvents.mdx)' of the Stellar RPC is used to stream events emitted by the Stellar Asset Contract. A filter can be used to specify the target asset (SAC contract ID) and accounts.
+To monitor these payments, the method '[getEvents](../../../data/apis/rpc/api-reference/methods/getEvents)' of the Stellar RPC is used to stream events emitted by the Stellar Asset Contract. A filter can be used to specify the target asset (SAC contract ID) and accounts.
 
 **From a G address**
 
@@ -218,13 +215,13 @@ For a detailed code example, see the section ‘_Monitoring Payments \-\> Using
 
 ### Sending payments from Contract Accounts to a recipient that requires a memo
 
-If a sender is using a Contract Account, and sending an [SAC token](../../../tokens/stellar-asset-contract.mdx) (such as XLM, USDC, etc.) to a recipient that requires a memo, (an exchange, for example) it should create a muxed address that includes the receiving account (GBLVHX…) and provided memo id in the muxed id field (123456789). In the user inteface, the resulting memo address doesn't need to be surfaced to the user, it should be used directly in the transaction.
+If a sender is using a Contract Account, and sending an [SAC token](../../../tokens/stellar-asset-contract) (such as XLM, USDC, etc.) to a recipient that requires a memo, (an exchange, for example) it should create a muxed address that includes the receiving account (GBLVHX…) and provided memo id in the muxed id field (123456789). In the user inteface, the resulting memo address doesn't need to be surfaced to the user, it should be used directly in the transaction.
 
 If the receiving party already provides an M address, it should be used directly, without requiring a memo field. Since this is the value provided by the user, it should be used in the transaction and displayed to the user.
 
 ## Sending payments to Contract Accounts (G to C)
 
-### Sending a ‘transfer’ via Stellar RPC
+### Sending a ‘transfer’ via Stellar RPC {#sending-a-transfer-via-stellar-rpc}
 
 This approach is simpler but requires the use of an RPC and involves a slightly different transaction workflow than a traditional native operation. For a detailed code example, see the section ‘_Sending Payments through the SAC \-\> Using the Stellar RPC_’ of [this repository's examples](https://github.com/fazzatti/c-address-payment-examples#sending-payments-through-the-sac).
 
@@ -246,13 +243,13 @@ This process is fully handled by the SDK in a very simple step by using the ‘_
 
 When the same account is used as the ‘sender’ of the funds and also the ‘source’ of the transaction, the signing step will be exactly the same. Once the updated transaction object is returned from the previous step, you just sign it with the source/sender account and it will be ready.
 
-When the ‘source’ account of the transaction differs from the ‘sender’ account, an additional signed entry will be necessary to authorize the ‘transfer’ invocation explicitly. Refer to the [Soroban Authorization Framework documentation](../../../learn/fundamentals/contract-development/authorization.mdx#soroban-authorization-framework) for further details.
+When the ‘source’ account of the transaction differs from the ‘sender’ account, an additional signed entry will be necessary to authorize the ‘transfer’ invocation explicitly. Refer to the [Soroban Authorization Framework documentation](../../../learn/fundamentals/contract-development/authorization#soroban-authorization-framework) for further details.
 
 **Sending the Transaction for processing**
 
 When a transaction is submitted for processing through the Stellar RPC, differently from the Horizon API, it will resolve immediately confirming its submission but not the processing. It is necessary to poll the transaction status for the next moment until you get a confirmation that it was successfully processed or a status update on a potential failure.
 
-### Sending a ‘transfer’ via Horizon API
+### Sending a ‘transfer’ via Horizon API {#sending-a-transfer-via-horizon-api}
 
 When sending a ‘transfer’ via the Horizon API, this approach introduces a few extra steps when compared to the use of an RPC. For a detailed code example, see the section ‘_Sending Payments through the SAC \-\> Using the Horizon API_’ of [this repository's examples](https://github.com/fazzatti/c-address-payment-examples#using-the-horizon-api-1).
 
diff --git a/docs/build/guides/transactions/send-and-receive-payments.mdx b/docs/build/guides/transactions/send-and-receive-payments.mdx
index 62e591811..2406eb667 100644
--- a/docs/build/guides/transactions/send-and-receive-payments.mdx
+++ b/docs/build/guides/transactions/send-and-receive-payments.mdx
@@ -1,37 +1,34 @@
 ---
 title: "Send and receive payments"
 description: "Learn to send payments and watch for received payments on the Stellar network."
-sidebar_position: 7
 ---
 
-import Details from "@theme/Details";
-
 ## Payments Overview
 
-A payment constitutes the transfer of a token from one account to another. On Stellar network a token can be either a Stellar asset or a custom contract token which follows the [SEP-41 token standard](../../../tokens/stellar-asset-contract.mdx#overview).
+A payment constitutes the transfer of a token from one account to another. On Stellar network a token can be either a Stellar asset or a custom contract token which follows the [SEP-41 token standard](../../../tokens/stellar-asset-contract#overview).
 
 There are two primary ways payments are transacted on Stellar:
 
-- Using Stellar's payment-related [operations](../../../learn/fundamentals/transactions/list-of-operations.mdx)
-- [Invoking a function](../../../learn/fundamentals/contract-development/contract-interactions/overview.mdx) on a token contract.
+- Using Stellar's payment-related [operations](../../../learn/fundamentals/transactions/list-of-operations)
+- [Invoking a function](../../../learn/fundamentals/contract-development/contract-interactions/overview) on a token contract.
 
 The approach you should take depends on the use case:
 
-- If you want to make a payment of a Stellar asset between two Stellar accounts, use the payment operations. Transaction fees are cheaper when using them compared to the fees for invoking the asset's token contract directly which is referred to as the [Stellar Asset Contract](../../../tokens/stellar-asset-contract.mdx#overview).
+- If you want to make a payment of a Stellar asset between two Stellar accounts, use the payment operations. Transaction fees are cheaper when using them compared to the fees for invoking the asset's token contract directly which is referred to as the [Stellar Asset Contract](../../../tokens/stellar-asset-contract#overview).
 - If you want to make a payment of a Stellar asset between a Stellar account and a contract address, or between two contract addresses, then the asset's contract must be used. Stellar's payment-related operations cannot have contract addresses as their source or destination.
-- If you want to make a payment of a custom contract token which is not a Stellar asset but follows the [SEP-41 token standard](../../../tokens/stellar-asset-contract.mdx#overview), you must use the token's contract. Stellar's payment operations can only be used to transfer Stellar assets.
+- If you want to make a payment of a custom contract token which is not a Stellar asset but follows the [SEP-41 token standard](../../../tokens/stellar-asset-contract#overview), you must use the token's contract. Stellar's payment operations can only be used to transfer Stellar assets.
 
-To learn more about the differences between Stellar assets and contract tokens, see the [Tokens](../../../tokens/README.mdx) overview.
+To learn more about the differences between Stellar assets and contract tokens, see the [Tokens](/docs/tokens) overview.
 
-:::info
+<Info>
 
 In the following code samples, proper error checking is omitted for brevity. However, you should _always_ validate your results, as there are many ways that requests can fail.
 
-:::
+</Info>
 
 ## Using Payments Example
 
-This example highlights the approach mentioned for transacting payments using operations and assets and using the [Stellar RPC](../../../data/apis/rpc/README.mdx) with [Stellar Client SDKs](../../../tools/sdks/client-sdks.mdx#overview) to perform all actions needed.
+This example highlights the approach mentioned for transacting payments using operations and assets and using the [Stellar RPC](/docs/data/apis/rpc) with [Stellar Client SDKs](../../../tools/sdks/client-sdks#overview) to perform all actions needed.
 
 ### Send a Payment
 
@@ -44,10 +41,10 @@ Lets demonstrate a payment of an asset on Stellar. We will build a transaction w
   - The transaction in serialized XDR format is idempotent meaning if the transaction has already been successfully applied to the ledger, RPC will simply return the saved result and not attempt to submit the transaction again.
   - Only in cases where a transaction's status is unknown (and thus will have a chance of being included into a ledger) will a resubmission to the network occur.
 
-<Details summary="Click to view payment sending code">
-<CodeExample>
+<Accordion title="Click to view payment sending code">
+<CodeGroup>
 
-```js
+```js JavaScript
 // send_payment.js
 // follow the https://github.com/stellar/js-stellar-sdk?tab=readme-ov-file#installation
 
@@ -182,7 +179,7 @@ sendPayments().catch((error) => {
 });
 ```
 
-```java
+```java Java
 // SendPaymentExample.java
 // Java 17, Stellar Java SDK (lightsail-network/java-stellar-sdk)
 
@@ -296,7 +293,7 @@ public class SendPaymentJavaExample {
 
 ```
 
-```go
+```go Go
 // sender.go
 package main
 
@@ -485,8 +482,8 @@ func main() {
 }
 ```
 
-</CodeExample>
-</Details>
+</CodeGroup>
+</Accordion>
 
 ### Monitoring Payments as event stream
 
@@ -501,10 +498,10 @@ The RPC approach offers several advantages:
 
 Demonstrate near real-time monitoring of transactions from the Stellar network by establishing an asynchronous listener to consume events from RPC and filter them by topic for just our example payments generated by our previous payments script.
 
-<Details summary="Click to view payment monitoring code">
-<CodeExample>
+<Accordion title="Click to view payment monitoring code">
+<CodeGroup>
 
-```js
+```js JavaScript
 // monitor_payment.js
 // follow the https://github.com/stellar/js-stellar-sdk?tab=readme-ov-file#installation
 
@@ -610,7 +607,7 @@ monitorPayments().catch((error) => {
 });
 ```
 
-```java
+```java Java
 // MonitorPaymentExample.java
 // Java 17, Stellar Java SDK (lightsail-network/java-stellar-sdk)
 
@@ -723,7 +720,7 @@ public class MonitorPaymentsJavaExample {
 }
 ```
 
-```go
+```go Go
 // monitor.go
 package main
 
@@ -1055,17 +1052,17 @@ func decodeAssetFromXDR(base64XDR string) (string, error) {
 }
 ```
 
-</CodeExample>
-</Details>
+</CodeGroup>
+</Accordion>
 
 ### Running Your Payment Pipeline with RPC
 
 1. **Run the payment submission script** in one terminal. Leave it running, it will submit a payment once every 30 seconds.
 
-<Details summary="Click for command to run the payments">
-<CodeExample>
+<Accordion title="Click for command to run the payments">
+<CodeGroup>
 
-```bash
+```bash bash
 # js
 node send_payment.js
 
@@ -1090,15 +1087,15 @@ go build -o sender sender/sender.go
 ./sender
 ```
 
-</CodeExample>
-</Details>
+</CodeGroup>
+</Accordion>
 
 2. **Run the payment monitor script** in a separate terminal.
 
-<Details summary="Click for command to run the payments monitor">
-<CodeExample>
+<Accordion title="Click for command to run the payments monitor">
+<CodeGroup>
 
-```bash
+```bash bash
 # js
 node monitor_payments.js
 
@@ -1113,8 +1110,8 @@ go build -o monitor monitor/monitor.go
 ./monitor
 ```
 
-</CodeExample>
-</Details>
+</CodeGroup>
+</Accordion>
 
 3. **Observe the payment events** as they're detected and displayed on console.
 
diff --git a/docs/build/guides/transactions/signing-soroban-invocations.mdx b/docs/build/guides/transactions/signing-soroban-invocations.mdx
index 498a8e2b5..429915f06 100644
--- a/docs/build/guides/transactions/signing-soroban-invocations.mdx
+++ b/docs/build/guides/transactions/signing-soroban-invocations.mdx
@@ -1,7 +1,6 @@
 ---
 title: "Signing Soroban contract invocations"
 description: "Learn two methods to sign Soroban smart contract invocations: full transaction signing for G-accounts and auth-entry signing for G or C-accounts with sponsored fees."
-sidebar_position: 15
 ---
 
 When invoking Soroban smart contracts that require authorization, there are two distinct signing approaches. Understanding when to use each method is essential for building powerful applications that interact with smart contracts.
@@ -90,11 +89,13 @@ async function invokeWithFullSigning(
 }
 ```
 
-:::note[Source account authorization]
+<Note>
+
+**Source account authorization**
 
 For transaction signing, `prepareTransaction` handles simulation internally. Since the source account's signature on the transaction envelope implicitly authorizes the invocation, no separate auth entry signing is needed—and therefore no second simulation is required.
 
-:::
+</Note>
 
 ### Key characteristics
 
@@ -107,7 +108,7 @@ For transaction signing, `prepareTransaction` handles simulation internally. Sin
 
 Auth-entry signing decouples authorization from transaction submission. The authorizer signs only the specific contract invocation (an "auth entry"), while a **separate account** acts as the transaction source, paying fees and consuming its own sequence number. This method works for either G-account or C-account clients.
 
-### When to use
+### When to use {#when-to-use-1}
 
 - The end-user has a C-account (commonly a smart wallet) — Method 2 is the **only** option for C-accounts, as they cannot sign transaction envelopes. G-accounts can also use this method.
 - The end-user doesn't (need to) have XLM to pay for fees
@@ -115,7 +116,7 @@ Auth-entry signing decouples authorization from transaction submission. The auth
 - Building smart contract protocols where the end-user doesn't submit the transaction
 - Building payment protocols where the transaction source account will be defined at a later point in time
 
-### How it works
+### How it works {#how-it-works-1}
 
 1. **Client** builds the transaction using `AssembledTransaction`
 2. **Client** simulates (Recording Mode) to get the authorization tree
@@ -136,7 +137,9 @@ Transaction simulation has two modes that are critical to understand:
 | **Recording Mode** | First simulation, before signing | Returns the auth entries that need signatures. Skips `require_auth` validation. |
 | **Enforcing Mode** | Second simulation, after signing | Validates signatures and executes `__check_auth`. Returns accurate resource estimates. |
 
-:::warning[Enforcing Mode simulation is required for submission]
+<Warning>
+
+**Enforcing Mode simulation is required for submission**
 
 The first simulation (Recording Mode) **does not execute** the `require_auth` checks — it only records which auth entries are needed. This means the resource estimates from the first simulation are **incomplete**.
 
@@ -152,9 +155,9 @@ Running Enforcing Mode simulation provides two critical benefits:
 - **Validates signatures and execution** — Catches auth errors and contract failures before submission. Failed simulations cost nothing; failed submissions cost real fees.
 - **Returns accurate resource estimates** — Recording Mode underestimates fees because it skips auth validation.
 
-See [Transaction Simulation - Authorization](../../../learn/fundamentals/contract-development/contract-interactions/transaction-simulation.mdx#authorization) for more details.
+See [Transaction Simulation - Authorization](../../../learn/fundamentals/contract-development/contract-interactions/transaction-simulation#authorization) for more details.
 
-:::
+</Warning>
 
 ### Auth entry structure
 
@@ -165,13 +168,15 @@ An auth entry signature authorizes a specific invocation tree and includes:
 - **Nonce**: A unique value for replay protection
 - **Signature**: Signs the SHA-256 hash of the `ENVELOPE_TYPE_SOROBAN_AUTHORIZATION` preimage
 
-:::note[Signature expiration]
+<Note>
+
+**Signature expiration**
 
 Auth entry signatures expire based on ledger numbers, not timestamps. A typical offset is between 12 and 60 ledgers (approximately 1-5 minutes). The signature is valid until and including the `signatureExpirationLedger`, but invalid at `signatureExpirationLedger + 1`.
 
 Keep expiration windows as small as viable – shorter windows are safer and result in lower transaction costs.
 
-:::
+</Note>
 
 ### Code example: Using `AssembledTransaction`
 
@@ -314,7 +319,7 @@ async function submitWithSignedAuth(
 }
 ```
 
-### Key characteristics
+### Key characteristics {#key-characteristics-1}
 
 - **Sequence number**: Consumed from the fee-payer account
 - **Fees**: Paid by the fee-payer account (in XLM)
@@ -357,7 +362,7 @@ const signedTransaction = await signer.signTransaction(transactionXDR);
 
 **Using Freighter for C-accounts (browser/wallet)**
 
-Wallet interfaces like [Freighter](../freighter/sign-auth-entries.mdx) provide `signAuthEntry` for C-accounts (smart wallets) where the signing logic is defined by the contract.
+Wallet interfaces like [Freighter](../freighter/sign-auth-entries) provide `signAuthEntry` for C-accounts (smart wallets) where the signing logic is defined by the contract.
 
 ```typescript
 import freighterApi from "@stellar/freighter-api";
@@ -366,7 +371,9 @@ import freighterApi from "@stellar/freighter-api";
 const signedAuthEntry = await freighterApi.signAuthEntry(preimageXdr);
 ```
 
-:::caution[C-account limitations]
+<Warning>
+
+**C-account limitations**
 
 C-accounts:
 
@@ -375,7 +382,7 @@ C-accounts:
 - Must rely on a G-account to pay fees and submit transactions
 - Require their auth entries to be signed according to their contract logic
 
-:::
+</Warning>
 
 ## Comparison summary
 
@@ -440,11 +447,11 @@ This allows the fee-payer to sponsor fees while the client retains exclusive con
 
 Regardless of the method, the user can still use fee bump transactions as an additional layer in order to separate the account spending their sequence number from the account paying the fees.
 
-More info on fee bump transactions can be found in the [Fee-bump transactions](./fee-bump-transactions.mdx) guide.
+More info on fee bump transactions can be found in the [Fee-bump transactions](./fee-bump-transactions) guide.
 
 ## Common pitfalls and gotchas
 
-- **Using Horizon URLs**: Soroban signing requires Soroban RPC, not Horizon. Refer to [Soroban RPC Providers](../../../data/apis/rpc/providers.mdx) for the correct URL to use.
+- **Using Horizon URLs**: Soroban signing requires Soroban RPC, not Horizon. Refer to [Soroban RPC Providers](../../../data/apis/rpc/providers) for the correct URL to use.
 - **Forgetting to assemble**: Fee-payer flows must `assembleTransaction` after simulation to apply footprint + resource fees.
 - **Missing auth on rebuilt ops**: When rebuilding, include `sorobanData` in the `invokeHostFunction` operation.
 - **Wrong signer**: C-accounts cannot sign envelopes, only auth entries.
@@ -452,11 +459,11 @@ More info on fee bump transactions can be found in the [Fee-bump transactions](.
 
 ## Further reading
 
-- [Transaction simulation](../../../learn/fundamentals/contract-development/contract-interactions/transaction-simulation.mdx) — Details on simulation and authorization modes
-- [Multi-party auth example](../../../learn/fundamentals/contract-development/contract-interactions/transaction-simulation.mdx#example-2-multi-party-authentication) — Walkthrough of multi-party signing in simulation using full transaction signing
-- [Contract authorization](../auth/contract-authorization.mdx) — How `require_auth` works in contracts
-- [Sign authorization entries with Freighter](../freighter/sign-auth-entries.mdx) — Wallet integration for auth entry signing
-- [Send to and receive from C-accounts](./send-and-receive-c-accounts.mdx) — Working with contract accounts
-- [Fee-bump transactions](./fee-bump-transactions.mdx) — Using fee bump transactions to pay for transaction fees on behalf of another account without re-signing the transaction
+- [Transaction simulation](../../../learn/fundamentals/contract-development/contract-interactions/transaction-simulation) — Details on simulation and authorization modes
+- [Multi-party auth example](../../../learn/fundamentals/contract-development/contract-interactions/transaction-simulation#example-2-multi-party-authentication) — Walkthrough of multi-party signing in simulation using full transaction signing
+- [Contract authorization](../auth/contract-authorization) — How `require_auth` works in contracts
+- [Sign authorization entries with Freighter](../freighter/sign-auth-entries) — Wallet integration for auth entry signing
+- [Send to and receive from C-accounts](./send-and-receive-c-accounts) — Working with contract accounts
+- [Fee-bump transactions](./fee-bump-transactions) — Using fee bump transactions to pay for transaction fees on behalf of another account without re-signing the transaction
 - [Stellar auth example (community)](https://github.com/fazzatti/stellar-auth-example) — End-to-end auth-entry signing walkthrough
-- [Stellar Asset Contract (SAC)](../tokens/stellar-asset-contract.mdx) — Background on the SAC `transfer`, used in the code examples above
+- [Stellar Asset Contract (SAC)](../tokens/stellar-asset-contract) — Background on the SAC `transfer`, used in the code examples above
diff --git a/docs/build/guides/transactions/simulateTransaction-Deep-Dive.mdx b/docs/build/guides/transactions/simulateTransaction-Deep-Dive.mdx
index e842fad21..c46087e90 100644
--- a/docs/build/guides/transactions/simulateTransaction-Deep-Dive.mdx
+++ b/docs/build/guides/transactions/simulateTransaction-Deep-Dive.mdx
@@ -13,7 +13,7 @@ Here we will look at the objects involved and their definitions.
 
 ## RPC Services
 
-Stellar Development Foundation provides a testnet RPC service at `http://soroban-testnet.stellar.org`. For public network providers please refer to the [Ecosystem RPC Providers](../../../data/apis/rpc/providers.mdx) list.
+Stellar Development Foundation provides a testnet RPC service at `http://soroban-testnet.stellar.org`. For public network providers please refer to the [Ecosystem RPC Providers](../../../data/apis/rpc/providers) list.
 
 ### Testnet Endpoint:
 
@@ -30,7 +30,7 @@ interface SimulateTransactionParams {
 }
 ```
 
-**SimulateTransactionResult** is the return result from the call. It includes [many useful things](../../../data/apis/rpc/api-reference/methods/simulateTransaction.mdx)!
+**SimulateTransactionResult** is the return result from the call. It includes [many useful things](../../../data/apis/rpc/api-reference/methods/simulateTransaction)!
 
 ## Things `simulateTransaction` is used for:
 
@@ -373,11 +373,11 @@ Soroban smart contracts on Stellar use a multidimensional resource fee model, ch
 5. **Events & Return Value Size**: Size of the events produced by the contract and the return value of the top-level contract function.
 6. **Ledger Space Rent**: Payment for ledger entry TTL extensions and rent payments for increasing ledger entry size.
 
-Fees are calculated based on the resource consumption declared in the transaction. Refundable fees are charged before execution and refunded based on actual usage, while non-refundable fees are calculated from CPU instructions, read bytes, write bytes, and transaction size. [Check out this document for a more in depth understanding of fees and metering.](../../../learn/fundamentals/fees-resource-limits-metering.mdx)
+Fees are calculated based on the resource consumption declared in the transaction. Refundable fees are charged before execution and refunded based on actual usage, while non-refundable fees are calculated from CPU instructions, read bytes, write bytes, and transaction size. [Check out this document for a more in depth understanding of fees and metering.](../../../learn/fundamentals/fees-resource-limits-metering)
 
 ## Error Handling
 
-The transaction simulation mechanism provides an estimation of CPU and memory consumption of a contract invocation during a transaction. It also highlights [potential errors and resource limitations](../../../learn/fundamentals/contract-development/errors-and-debugging/debugging-errors.mdx#1-transaction-simulation) of the invocation before actual submission.
+The transaction simulation mechanism provides an estimation of CPU and memory consumption of a contract invocation during a transaction. It also highlights [potential errors and resource limitations](../../../learn/fundamentals/contract-development/errors-and-debugging/debugging-errors#1-transaction-simulation) of the invocation before actual submission.
 
 ## Backend Code and Workflow
 
@@ -405,7 +405,7 @@ These functions are defined in the [`rs-soroban-env`](https://github.com/stellar
 
 For more information and examples, check out the code and other documentation:
 
-- [openRpc Documentation](../../../data/apis/rpc/api-reference/methods/simulateTransaction.mdx)
+- [openRpc Documentation](../../../data/apis/rpc/api-reference/methods/simulateTransaction)
 - [openRpc json Specification](https://github.com/stellar/stellar-docs/tree/main/openrpc)
 - [preflight.go](https://github.com/stellar/stellar-rpc/blob/release/v22.1.2/cmd/stellar-rpc/internal/preflight/preflight.go)
 - [Soroban Example Code](https://github.com/stellar/soroban-examples)
diff --git a/docs/build/guides/transactions/sponsored-reserves.mdx b/docs/build/guides/transactions/sponsored-reserves.mdx
index 88c483bfc..b9517aa7f 100644
--- a/docs/build/guides/transactions/sponsored-reserves.mdx
+++ b/docs/build/guides/transactions/sponsored-reserves.mdx
@@ -1,24 +1,21 @@
 ---
 title: Sponsored reserves
 description: Use sponsored reserves to pay for base reserves on behalf of another account.
-sidebar_position: 50
 ---
 
-import Details from "@theme/Details";
-
 Sponsored reserves were introduced in [CAP-33](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0033.md) and allow an account (sponsoring account) to pay the base reserves for another account (sponsored account). While this relationship exists, base reserve requirements that would normally accumulate on the sponsored account now accumulate on the sponsoring account.
 
 Both the Begin Sponsoring Future Reserves and the End Sponsoring Future Reserves operations must appear in the sponsorship transaction, guaranteeing that both accounts agree to the sponsorship.
 
 Anything that increases the minimum balance can be sponsored (account creation, offers, trustlines, data entries, signers, claimable balances).
 
-To learn about base reserves, see our section on [Lumens](../../../learn/fundamentals/lumens.mdx#base-reserves).
+To learn about base reserves, see our section on [Lumens](../../../learn/fundamentals/lumens#base-reserves).
 
-:::note
+<Note>
 
-Use the [Stellar Wallet Sponsorship Calculator](../../../tools/developer-tools/wallets.mdx#stellar-wallet-sponsorship-calculator) to estimate the XLM requirements for wallets looking to use sponsored reserves and fee-bump transactions to cover account creation, transaction fees, trustlines, and more.
+Use the [Stellar Wallet Sponsorship Calculator](../../../tools/developer-tools/wallets#stellar-wallet-sponsorship-calculator) to estimate the XLM requirements for wallets looking to use sponsored reserves and fee-bump transactions to cover account creation, transaction fees, trustlines, and more.
 
-:::
+</Note>
 
 ## Sponsored reserves operations
 
@@ -36,7 +33,7 @@ End Sponsoring Future Reserves ends the current is-sponsoring-future-reserves-fo
 
 At the end of any transaction, there must be no ongoing is-sponsoring-future-reserves-for relationships, which is why these two operations must be used together in a single transaction.
 
-View operation details in our [List of Operations section](../../../learn/fundamentals/transactions/list-of-operations.mdx).
+View operation details in our [List of Operations section](../../../learn/fundamentals/transactions/list-of-operations).
 
 ### Revoke sponsorship
 
@@ -55,7 +52,7 @@ Operation logic
   - Source account is not the beneficiary of a is-sponsoring-future-reserves-for relationship
     - No-Op
 
-View operation details in our [List of Operations section](../../../learn/fundamentals/transactions/list-of-operations.mdx#begin-sponsoring-future-reserves).
+View operation details in our [List of Operations section](../../../learn/fundamentals/transactions/list-of-operations#begin-sponsoring-future-reserves).
 
 ## Effect on minimum balance
 
@@ -69,13 +66,13 @@ When a sponsored entry or subentry is removed, `numSponsoring` is decreased on t
 
 Because sponsorship can cover an account's own base reserves as well as its subentries, a brand-new account can be created with a `startingBalance` of `0`: wrap the `CreateAccount` operation in a `BeginSponsoringFutureReserves`/`EndSponsoringFutureReserves` sandwich (as in the examples below) and the sponsor carries the two base reserves so the account never has to hold the minimum balance itself.
 
-To learn more about minimum balance requirements, see our section on [Lumens](../../../learn/fundamentals/lumens.mdx#minimum-balance).
+To learn more about minimum balance requirements, see our section on [Lumens](../../../learn/fundamentals/lumens#minimum-balance).
 
 ## Effect on claimable balances
 
 All claimable balances are sponsored through built-in logic in the claimable balance operations. The account that creates the claimable balance pays the base reserve to get the claimable balance on the ledger. When the claimable balance is claimed by the claimant(s), the claimable balance is removed from the ledger, and the account that created it gets the base reserve back.
 
-Read more about claimable balances in our [Claimable Balances guide](./claimable-balances.mdx).
+Read more about claimable balances in our [Claimable Balances guide](./claimable-balances).
 
 ## Examples
 
@@ -91,9 +88,9 @@ For brevity in the Golang examples, we’ll assume the existence of a `SignAndSe
 
 We’ll start by including the boilerplate of account and asset creation.
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 import {
   Keypair,
   Asset,
@@ -130,7 +127,7 @@ async function main() {
   // ...
 ```
 
-```go
+```go Go
 package main
 
 import (
@@ -180,16 +177,17 @@ func main() {
   // ...
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### 1. Sponsoring trustlines
 
 Now, let’s sponsor trustlines for Account A. Notice how the `CHANGE_TRUST` operation is sandwiched between the begin and end sponsoring operations and that all relevant accounts need to sign the transaction.
 
-<Details summary="Sponsoring a single trustline">
-<CodeExample>
+<AccordionGroup>
+<Accordion title="Sponsoring a single trustline">
+<CodeGroup>
 
-```js
+```js JavaScript
 //
 // 1. S1 will sponsor a trustline for Account A.
 //
@@ -227,7 +225,7 @@ if (!txResponse) {
 console.log("Sponsored a trustline of", A.publicKey());
 ```
 
-```go
+```go Go
   //
   // 1. S1 will sponsor a trustline for Account A.
   //
@@ -248,13 +246,13 @@ console.log("Sponsored a trustline of", A.publicKey());
   fmt.Println("Sponsored a trustline of", A.Address())
 ```
 
-</CodeExample>
-</Details>
+</CodeGroup>
+</Accordion>
 
-<Details summary="Two accounts sponsoring different assets for a single account">
-<CodeExample>
+<Accordion title="Two accounts sponsoring different assets for a single account">
+<CodeGroup>
 
-```js
+```js JavaScript
 //
 // 2. Both S1 and S2 sponsor trustlines for Account A for different assets.
 //
@@ -300,7 +298,7 @@ if (!txResponse) {
 console.log("Sponsored two trustlines of", A.publicKey());
 ```
 
-```go
+```go Go
   //
   // 2. Both S1 and S2 sponsor trustlines for Account A for different assets.
   //
@@ -331,8 +329,9 @@ console.log("Sponsored two trustlines of", A.publicKey());
   fmt.Println("Sponsored two trustlines of", A.Address())
 ```
 
-</CodeExample>
-</Details>
+</CodeGroup>
+</Accordion>
+</AccordionGroup>
 
 ### 2. Transferring sponsorship
 
@@ -340,9 +339,9 @@ Suppose that now Signer 1 wants to transfer the responsibility of sponsoring res
 
 An intuitive way to think of a sponsorship transfer is that the very act of sponsorship is being sponsored by a new account. That is, the new sponsor takes over the responsibilities of the old sponsor by sponsoring a revocation.
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 //
 // 3. Transfer sponsorship of B's second trustline from S1 to S2.
 //
@@ -375,7 +374,7 @@ if (!txResponse) {
 console.log("Transferred sponsorship for", A.publicKey());
 ```
 
-```go
+```go Go
   //
   // 3. Transfer sponsorship of B's second trustline from S1 to S2.
   //
@@ -401,7 +400,7 @@ console.log("Transferred sponsorship for", A.publicKey());
   fmt.Println("Transferred sponsorship for", A.Address())
 ```
 
-</CodeExample>
+</CodeGroup>
 
 At this point, Signer 1 is only sponsoring the first asset (arbitrarily coded as ABCD), while Signer 2 is sponsoring the other two assets. (Recall that initially Signer 1 was also sponsoring EFGH.)
 
@@ -409,9 +408,9 @@ At this point, Signer 1 is only sponsoring the first asset (arbitrarily coded as
 
 Finally, we can demonstrate complete revocation of sponsorships. Below, Signer 2 removes themselves from all responsibility over the two asset trustlines. Notice that Account A is not involved at all, since revocation should be performable purely at the sponsor’s discretion.
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
   //
   // 4. S2 revokes sponsorship of B's trustlines entirely.
   //
@@ -443,7 +442,7 @@ Finally, we can demonstrate complete revocation of sponsorships. Below, Signer 2
 } // ends main()
 ```
 
-```go
+```go Go
   //
   // 4. S2 revokes sponsorship of B's trustlines entirely.
   //
@@ -471,7 +470,7 @@ Finally, we can demonstrate complete revocation of sponsorships. Below, Signer 2
 } // ends main()
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Sponsorship Source Accounts
 
@@ -483,9 +482,9 @@ Since the source account defaults to the transaction submitter when omitted, thi
 
 For example, the following is an identical expression of the earlier Golang example of sponsoring a trustline, just submitted by the sponsor (Sponsor 1) rather than the sponsored account (Account A). Notice the differences in where `SourceAccount` is set:
 
-<CodeExample>
+<CodeGroup>
 
-```go
+```go Go
     sponsorTrustline := []txnbuild.Operation{
         &txnbuild.BeginSponsoringFutureReserves{
             SponsoredID: addressA,
@@ -505,7 +504,7 @@ For example, the following is an identical expression of the earlier Golang exam
     SignAndSend(client, s1Account.AccountID, []*keypair.Full{S1, A}, sponsorTrustline...)
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Other examples
 
@@ -515,9 +514,9 @@ If you’d like other examples or want to view a more-generic pseudo-code breakd
 
 For the above examples, an implementation of `SignAndSend` (Golang) and some (very) rudimentary error checking code (all languages) might look something like this:
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 async function sendTransaction(tx) {
   const sendResp = await server.sendTransaction(tx);
   if (sendResp.status !== "PENDING") throw sendResp;
@@ -533,7 +532,7 @@ function accountFail(err) {
 }
 ```
 
-```go
+```go Go
 
 // Builds a transaction containing `operations...`, signed (by `signers`), and
 // submitted using the given `client` on behalf of `account`.
@@ -597,4 +596,4 @@ func check(err error) {
 }
 ```
 
-</CodeExample>
+</CodeGroup>
diff --git a/docs/build/guides/transactions/submit-transaction-wait-js.mdx b/docs/build/guides/transactions/submit-transaction-wait-js.mdx
index 20c8a6eab..4a728758a 100644
--- a/docs/build/guides/transactions/submit-transaction-wait-js.mdx
+++ b/docs/build/guides/transactions/submit-transaction-wait-js.mdx
@@ -1,6 +1,5 @@
 ---
 title: Submit a transaction to Stellar RPC using the JavaScript SDK
-hide_table_of_contents: true
 description: Use a looping mechanism to submit a transaction to the RPC.
 ---
 
@@ -41,8 +40,8 @@ async function submitTx(
 }
 ```
 
-:::caution
+<Warning>
 
 Remember: You should always handle errors gracefully! This is a fail-hard and fail-fast approach that should only be used in these examples.
 
-:::
+</Warning>
diff --git a/docs/build/guides/transactions/upload-wasm-bytecode.mdx b/docs/build/guides/transactions/upload-wasm-bytecode.mdx
index a6be82a5c..ca7133142 100644
--- a/docs/build/guides/transactions/upload-wasm-bytecode.mdx
+++ b/docs/build/guides/transactions/upload-wasm-bytecode.mdx
@@ -1,27 +1,13 @@
 ---
 title: Upload WebAssembly (Wasm) bytecode using code
+og:title: "Install WebAssembly (Wasm) bytecode using code"
+og:description: "This guide will walk you through installing the wasm of the contract using js-stellar-sdk."
 description: Upload the Wasm of the contract using js-stellar-sdk.
 ---
 
-<head>
-  <title>Install WebAssembly (Wasm) bytecode using code</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Install WebAssembly (Wasm) bytecode using code"
-  />
-  <meta
-    property="og:description"
-    content="This guide will walk you through installing the wasm of the contract using js-stellar-sdk."
-  />
-</head>
+## Install WebAssembly (Wasm) bytecode using code
 
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-# Install WebAssembly (Wasm) bytecode using code
-
-This process uploads the contract code to the Stellar Testnet in a transaction, the uploaded Wasm blob is a [contract source](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0046-02.md#contract-source), which can be thought of as a 'class' of a contract. Multiple [instances of a contract can be deployed](../conventions/deploy-contract.mdx) which share the same source, but have their own state.
+This process uploads the contract code to the Stellar Testnet in a transaction, the uploaded Wasm blob is a [contract source](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0046-02.md#contract-source), which can be thought of as a 'class' of a contract. Multiple [instances of a contract can be deployed](../conventions/deploy-contract) which share the same source, but have their own state.
 
 ## Prerequisites
 
@@ -47,7 +33,7 @@ After building the contract for release, the generated .wasm file is at the path
 
 ## Upload Wasm to the Stellar blockchain
 
-We can use one of the [client SDKs](../../../tools/sdks/client-sdks.mdx), install necessary dependencies for your chosen programming language:
+We can use one of the [client SDKs](../../../tools/sdks/client-sdks), install necessary dependencies for your chosen programming language:
 
 - JavaScript SDK: [Node.js](https://nodejs.org/en) and npm
 - Python SDK: [pip](https://pip.pypa.io/en/stable/installation)
@@ -65,7 +51,8 @@ Different programming languages can be used to upload the `.wasm` file, its SHA2
 
 <Tabs>
 
-<TabItem value="js" label="JavaScript">
+<Tab title="JavaScript">
+
 This guide will walk you through installing the Wasm of the contract using the JavaScript SDK: [js-stellar-sdk](https://github.com/stellar/js-stellar-sdk).
 
 Create a new Node.js project with a JavaScript file, and install necessary dependencies:
@@ -150,8 +137,9 @@ try {
 }
 ```
 
-</TabItem>
-<TabItem value="py" label="Python">
+</Tab>
+<Tab title="Python">
+
 This guide will walk you through installing the Wasm of the contract using the Python SDK: [py-stellar-base](https://stellar-sdk.readthedocs.io/en/soroban).
 
 Create a new Python script, and install the necessary dependencies:
@@ -258,8 +246,8 @@ async def main():
 asyncio.run(main())
 ```
 
-</TabItem>
-<TabItem value="rust" label="Rust">
+</Tab>
+<Tab title="Rust">
 
 This guide will walk you through uploading the Wasm of the contract using the Rust SDK: [rs-soroban-client](https://github.com/rahul-soshte/rs-soroban-client).
 
@@ -349,7 +337,7 @@ pub async fn main() -> Result<(), Box<dyn std::error::Error>> {
 }
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 Replace `"Your_Secret_Key"` with your actual secret key.
@@ -361,11 +349,11 @@ stellar keys show hello
 
 The Stellar CLI can be used to generate identities, e.g. `hello`, and show its secret key.
 
-:::tip
+<Tip>
 
 Ensure that you handle secret and private keys securely in production environments and never expose them in your code repositories.
 
-:::
+</Tip>
 
 ```bash
 Submitting transaction...
diff --git a/docs/build/index.mdx b/docs/build/index.mdx
new file mode 100644
index 000000000..3823a248e
--- /dev/null
+++ b/docs/build/index.mdx
@@ -0,0 +1,56 @@
+---
+title: Introduction
+"og:title": "Get Started with Blockchain Development; Guides, Tutorials & Tools"
+icon: "house"
+description: "Get started with developing on the Stellar with guides, tutorials, tools, and resources. Learn how to write smart contracts, build applications, and more."
+---
+
+The Build section is split into three parts:
+
+1. [Smart contracts](/docs/build/smart-contracts)
+2. [Applications](/docs/build/apps)
+3. [How-to guides](/docs/build/guides)
+
+Explanations for each section are stated below:
+
+## Smart contracts
+
+Smart contracts are self-executing programs with the terms of an agreement written directly into the code. They automatically enforce and execute the terms of the contract when predefined conditions are met. Once written and tested, smart contracts are deployed to the blockchain, where they become immutable and publicly accessible.
+
+<Tip>
+
+While defining the rules and logic of the contract, developers must be security conscious to avoid vulnerabilities such as integer overflows, access control flaws, and other exploits that could compromise the integrity and functionality of the smart contract.
+
+</Tip>
+
+This section will walk you through how to write and deploy smart contracts on Stellar, including the installation process, an introduction to testing, storing data, and more. It also provides a variety of example contracts for reference and use.
+
+## Applications
+
+Applications interact with the blockchain and can use smart contracts as the backend.
+
+They:
+
+- Provide user interfaces (UI);
+- Manage user interactions;
+- Integrate with smart contracts to operate.
+
+Writing **smart contracts** focuses on the backend logic and rules enforced on the blockchain, while **building applications** involves creating the frontend and integrating it with these smart contracts to provide a complete user experience.
+
+<Note>
+
+You can create applications on Stellar without using smart contracts, as demonstrated in the [Wallet SDK tutorial](/docs/build/apps/wallet/overview) or the [JS SDK Payment Application tutorial](/docs/build/apps/example-application-tutorial/overview).
+
+</Note>
+
+This section walks you through design considerations for applications and tutorials for building applications with or without smart contracts.
+
+## How-to guides
+
+This section provides step-by-step instructions to help users complete specific tasks associated with building on Stellar. These tasks can include instructions for aspects of writing contracts, interacting with contracts, building applications, using Stellar operations, setting up infrastructure, and more.
+
+<Note>
+
+How-to guides assume that the user has some experience and knowledge with building on Stellar and are not typically for beginners.
+
+</Note>
diff --git a/docs/build/security-docs/README.mdx b/docs/build/security-docs/README.mdx
deleted file mode 100644
index 5cf691f62..000000000
--- a/docs/build/security-docs/README.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: Security Best Practices
-sidebar_position: 60
-sidebar_label: Security Best Practices
----
-
-import DocCardList from "@theme/DocCardList";
-
-A series of guides and documentation to help developers build safe and secure products on Stellar.
-
-<DocCardList />
diff --git a/docs/build/security-docs/index.mdx b/docs/build/security-docs/index.mdx
new file mode 100644
index 000000000..902526d9b
--- /dev/null
+++ b/docs/build/security-docs/index.mdx
@@ -0,0 +1,22 @@
+---
+title: Security Best Practices
+description: "A series of guides and documentation to help developers build safe and secure products on Stellar."
+---
+
+<CardGroup cols={2}>
+  <Card title="Threat Modeling" icon="box-archive" href="/docs/build/security-docs/threat-modeling">
+
+    4 items
+
+  </Card>
+  <Card title="Onchain Monitoring" icon="box-archive" href="/docs/build/security-docs/monitoring">
+
+    2 items
+
+  </Card>
+  <Card title="Securing Web-Based Projects" icon="file-lines" href="/docs/build/security-docs/securing-web-based-projects">
+
+    Any application managing cryptocurrency is a frequent target of malicious actors and needs to follow security best practices.
+
+  </Card>
+</CardGroup>
diff --git a/docs/build/security-docs/monitoring/README.mdx b/docs/build/security-docs/monitoring/README.mdx
deleted file mode 100644
index a70214c69..000000000
--- a/docs/build/security-docs/monitoring/README.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: Onchain Monitoring Templates
-sidebar_label: Onchain Monitoring
-sidebar_position: 20
----
-
-import DocCardList from "@theme/DocCardList";
-
-Learn how to monitor your important positions and protocols on Stellar.
-
-<DocCardList />
diff --git a/docs/build/security-docs/monitoring/index.mdx b/docs/build/security-docs/monitoring/index.mdx
new file mode 100644
index 000000000..585422f2a
--- /dev/null
+++ b/docs/build/security-docs/monitoring/index.mdx
@@ -0,0 +1,18 @@
+---
+title: Onchain Monitoring Templates
+sidebarTitle: Onchain Monitoring
+description: "Learn how to monitor your important positions and protocols on Stellar."
+---
+
+<CardGroup cols={2}>
+  <Card title="On-Chain Monitoring Plan Template (Builders)" icon="file-lines" href="/docs/build/security-docs/monitoring/monitoring-template-builders">
+
+    For Builders - turn your threat model into a monitoring plan
+
+  </Card>
+  <Card title="Position Monitoring Plan Template (Users)" icon="file-lines" href="/docs/build/security-docs/monitoring/monitoring-template-users">
+
+    For Users - Monitor your important positions on Stellar
+
+  </Card>
+</CardGroup>
diff --git a/docs/build/security-docs/monitoring/monitoring-template-builders.mdx b/docs/build/security-docs/monitoring/monitoring-template-builders.mdx
index f60c3771a..204134133 100644
--- a/docs/build/security-docs/monitoring/monitoring-template-builders.mdx
+++ b/docs/build/security-docs/monitoring/monitoring-template-builders.mdx
@@ -1,10 +1,9 @@
 ---
 title: On-Chain Monitoring Plan Template (Builders)
 description: For Builders - turn your threat model into a monitoring plan
-sidebar_position: 10
 ---
 
-This template turns a completed [threat model](../threat-modeling/README.mdx) into an operational monitoring plan for a protocol or set of smart contracts on Stellar. Where the threat model asks _what could go wrong and how will we design against it_, this plan asks _how will we watch for it in production_. Each threat identified in the threat model becomes one or more observable on-chain effects, and each effect becomes a rule that the monitoring solution watches while the contracts are live.
+This template turns a completed [threat model](/docs/build/security-docs/threat-modeling) into an operational monitoring plan for a protocol or set of smart contracts on Stellar. Where the threat model asks _what could go wrong and how will we design against it_, this plan asks _how will we watch for it in production_. Each threat identified in the threat model becomes one or more observable on-chain effects, and each effect becomes a rule that the monitoring solution watches while the contracts are live.
 
 **Directions**: Fill out each section below to the best of your ability. Carry the threat identifiers over from the STRIDE threat model so the two documents stay linked. Work through the sections in order; every threat should leave the exercise with at least one monitor and a defined response.
 
@@ -21,11 +20,11 @@ _Input text: high-level description of the protocol, the value it holds, and the
 | _e.g. Lending pool core_ | _C..._ | _Holds pooled collateral and debt_ |
 |  |  |  |
 
-:::note
+<Note>
 
 Keep this inventory current. Addresses can change with new versions, and an out-of-date address list is the most common reason a monitor silently stops working. If it's discovered later that scope has changed, update this section with the latest information.
 
-:::
+</Note>
 
 ## What could go wrong?
 
@@ -56,11 +55,11 @@ Keep this inventory current. Addresses can change with new versions, and an out-
 | _e.g. Elevation.1_ | _A leaked admin key reassigns ownership, then raises borrow caps and drains reserves._ | _`set_admin` / ownership-transfer event; privileged parameter change from a non-allowlisted caller_ |
 |  |  |  |
 
-:::note
+<Note>
 
 If a threat has no observable on-chain effect (for example, a compromised frontend or an oracle's upstream data source), record it here and plan to monitor it off-chain. Don't drop it just because it isn't visible on-chain.
 
-:::
+</Note>
 
 ## What will we monitor for?
 
diff --git a/docs/build/security-docs/monitoring/monitoring-template-users.mdx b/docs/build/security-docs/monitoring/monitoring-template-users.mdx
index 5a3d09c10..943c68adf 100644
--- a/docs/build/security-docs/monitoring/monitoring-template-users.mdx
+++ b/docs/build/security-docs/monitoring/monitoring-template-users.mdx
@@ -1,7 +1,6 @@
 ---
 title: Position Monitoring Plan Template (Users)
 description: For Users - Monitor your important positions on Stellar
-sidebar_position: 20
 ---
 
 This template helps you, as someone holding positions on Stellar, set up monitoring for what you own, without needing a formal threat model. Fill in one row per position or wallet you care about: what could go wrong, when you want to be alerted, and what you'll do about it.
@@ -46,11 +45,11 @@ _Input text: a short description of each position and where it lives._
 | _e.g. XLM collateral..._ | _Health factor drops below 1.5; any admin change on the market; pool liquidity falls more than 30% in an hour._ | _Push + Telegram_ |
 |  |  |  |
 
-:::note
+<Note>
 
 Don't assume the protocol is watching your specific position. Its monitoring is tuned to the health of the whole system; yours should be tuned to your concerns.
 
-:::
+</Note>
 
 ## What will I do?
 
diff --git a/docs/build/security-docs/securing-web-based-projects.mdx b/docs/build/security-docs/securing-web-based-projects.mdx
index f03f9288d..1b5fdc2a5 100644
--- a/docs/build/security-docs/securing-web-based-projects.mdx
+++ b/docs/build/security-docs/securing-web-based-projects.mdx
@@ -1,11 +1,11 @@
 ---
 title: Securing Web-Based Projects
-sidebar_position: 30
+description: "Any application managing cryptocurrency is a frequent target of malicious actors and needs to follow security best practices."
 ---
 
 Any application managing cryptocurrency is a frequent target of malicious actors and needs to follow security best practices. The below checklist offers guidance on the most common vulnerabilities. However, even if you follow every piece of advice, security is not guaranteed. Web security and malicious actors are constantly evolving, so it’s good to maintain a healthy amount of paranoia.
 
-## SSL/TLS
+## SSL/TLS {#ssltls}
 
 Ensure that TLS is enabled. Redirect HTTP to HTTPS where necessary to ensure that Man in the Middle attacks can’t occur and sensitive data is securely transferred between the client and browser. Enable TLS and get an SSL certificate for free at [LetsEncrypt](https://letsencrypt.org/getting-started).
 
@@ -65,6 +65,6 @@ Phishing attacks will thwart any well-formed security infrastructure. Have clear
 
 Use a tool like [Snyk](https://snyk.io) to scan your third-party client libraries for vulnerabilities. Make sure to keep your third-party libraries up to date. Often, upgrades are triggered by security exploits. You can use [Mozilla Observatory](https://observatory.mozilla.org) to check your HTTP security as well.
 
-## Cross-Site Request Forgery Protection (CSRF), SQL injections
+## Cross-Site Request Forgery Protection (CSRF), SQL injections {#cross-site-request-forgery-protection-csrf-sql-injections}
 
 Most modern web and mobile frameworks handle both CSRF protection and SQL injections. Ensure CSRF protection is enabled and that you are using a database ORM instead of running raw SQL based on user input. For example, see what [Ruby on Rails documentation](http://guides.rubyonrails.org/security.html#sql-injection) says about SQL injections.
diff --git a/docs/build/security-docs/threat-modeling/README.mdx b/docs/build/security-docs/threat-modeling/README.mdx
deleted file mode 100644
index 1951f290d..000000000
--- a/docs/build/security-docs/threat-modeling/README.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: Threat Modeling Readiness How-To Guide
-sidebar_label: Threat Modeling
-sidebar_position: 10
----
-
-import DocCardList from "@theme/DocCardList";
-
-This Threat Modeling How-To Guide is intended for Stellar ecosystem partners to fund an audit through the Audit Bank. This document is aimed at developers who are ready to audit their application.
-
-<DocCardList />
diff --git a/docs/build/security-docs/threat-modeling/STRIDE-template.mdx b/docs/build/security-docs/threat-modeling/STRIDE-template.mdx
index 8f5379db2..2608c5c58 100644
--- a/docs/build/security-docs/threat-modeling/STRIDE-template.mdx
+++ b/docs/build/security-docs/threat-modeling/STRIDE-template.mdx
@@ -1,5 +1,4 @@
 ---
-sidebar_position: 30
 title: STRIDE Threat Model Template
 description: Use this template to create a STRIDE threat model for your project.
 ---
@@ -12,11 +11,11 @@ _**Input text**: high level description of the project and what is being designe
 
 _Add at least one visual dataflow diagram that shows process flows between different entities in the system_
 
-:::note
+<Note>
 
 If additional information is needed to understand the flow, include additional diagrams or information here. The goal of this section is to capture the documentation needed to accomplish building a successful threat model. If it is discovered later that additional information is required, ensure the “What are we working on?” section is updated with the latest information.
 
-:::
+</Note>
 
 ## What can go wrong?
 
diff --git a/docs/build/security-docs/threat-modeling/index.mdx b/docs/build/security-docs/threat-modeling/index.mdx
new file mode 100644
index 000000000..3bb276fc2
--- /dev/null
+++ b/docs/build/security-docs/threat-modeling/index.mdx
@@ -0,0 +1,28 @@
+---
+title: Threat Modeling Readiness How-To Guide
+sidebarTitle: Threat Modeling
+description: "This Threat Modeling How-To Guide is intended for Stellar ecosystem partners to fund an audit through the Audit Bank. This document is aimed at developers who are ready to audit their application."
+---
+
+<CardGroup cols={2}>
+  <Card title="What is Threat Modeling?" icon="file-lines" href="/docs/build/security-docs/threat-modeling/threat-modeling-description">
+
+    Threat modeling is a process of identifying potential security threats to a system or application, analyzing those threats, and then developing strategies to mitigate or prevent them.
+
+  </Card>
+  <Card title="How-To Guide" icon="file-lines" href="/docs/build/security-docs/threat-modeling/threat-modeling-how-to">
+
+    How to conduct a threat modeling exercise for your project.
+
+  </Card>
+  <Card title="STRIDE Threat Model Template" icon="file-lines" href="/docs/build/security-docs/threat-modeling/STRIDE-template">
+
+    Use this template to create a STRIDE threat model for your project.
+
+  </Card>
+  <Card title="Example STRIDE Threat Model" icon="file-lines" href="/docs/build/security-docs/threat-modeling/pizza-restaurant-example">
+
+    Example STRIDE threat model to help you understand the process.
+
+  </Card>
+</CardGroup>
diff --git a/docs/build/security-docs/threat-modeling/pizza-restaurant-example.mdx b/docs/build/security-docs/threat-modeling/pizza-restaurant-example.mdx
index f8ec857cb..0e13758f2 100644
--- a/docs/build/security-docs/threat-modeling/pizza-restaurant-example.mdx
+++ b/docs/build/security-docs/threat-modeling/pizza-restaurant-example.mdx
@@ -1,7 +1,6 @@
 ---
-sidebar_position: 40
-sidebar_label: Example STRIDE Threat Model
 title: Pizza Restaurant Example STRIDE Threat Model
+sidebarTitle: Example STRIDE Threat Model
 description: Example STRIDE threat model to help you understand the process.
 ---
 
diff --git a/docs/build/security-docs/threat-modeling/threat-modeling-description.mdx b/docs/build/security-docs/threat-modeling/threat-modeling-description.mdx
index cd889c73b..aad0bbf06 100644
--- a/docs/build/security-docs/threat-modeling/threat-modeling-description.mdx
+++ b/docs/build/security-docs/threat-modeling/threat-modeling-description.mdx
@@ -1,7 +1,6 @@
 ---
-sidebar_position: 10
-sidebar_label: What is Threat Modeling?
 title: Threat Modeling Readiness
+sidebarTitle: What is Threat Modeling?
 description: Threat modeling is a process of identifying potential security threats to a system or application, analyzing those threats, and then developing strategies to mitigate or prevent them.
 ---
 
diff --git a/docs/build/security-docs/threat-modeling/threat-modeling-how-to.mdx b/docs/build/security-docs/threat-modeling/threat-modeling-how-to.mdx
index 6fb1d601a..35f20298f 100644
--- a/docs/build/security-docs/threat-modeling/threat-modeling-how-to.mdx
+++ b/docs/build/security-docs/threat-modeling/threat-modeling-how-to.mdx
@@ -1,7 +1,6 @@
 ---
-sidebar_position: 20
-sidebar_label: How-To Guide
 title: Threat Modeling How-To Guide
+sidebarTitle: How-To Guide
 description: How to conduct a threat modeling exercise for your project.
 ---
 
@@ -14,7 +13,7 @@ Threat modeling, at its heart, is really about asking four simple questions:
 3. What are we going to do about it?
 4. Did we do a good job?
 
-### How to answer: “What are we working on?”
+### How to answer: “What are we working on?” {#how-to-answer-what-are-we-working-on}
 
 The crux of this question is documentation. More specifically, this question is guiding the development team to start thinking about (and documenting) the core processes being developed in terms of processes, data flows, data storage, areas of control, and identifying places where trust assumptions are being made between and among systems and processes. The answer to “What are we working on?” should include a verbal description of the use case for the application and a data-flow diagram showing:
 
@@ -29,7 +28,7 @@ The crux of this question is documentation. More specifically, this question is
 - Trust boundaries
   - Outline and group together areas where interactions between systems make or include trust assumptions. For example, in a dataflow where a user submits data on a webpage and it gets processed on the backend, a trust boundary should enclose the backend process, since data can be submitted to the backend outside any filtering controls on the front-end.
 
-### How to answer: “What can go wrong?”
+### How to answer: “What can go wrong?” {#how-to-answer-what-can-go-wrong}
 
 Understanding the use case and the data flow from “What are we working on?” can greatly inform thinking around what can go wrong. However, to ensure consistency and thoroughness for the review, it is useful to follow a framework that helps guide the thinking around threats and what can go wrong. Stellar Development Foundation (SDF) follows the STRIDE model. Described below, the STRIDE model helps to provide the consistent framework to ensure high-quality threat models.
 
@@ -44,11 +43,11 @@ For each of the S, T, R, I, D, and E acronyms in the table below, ensure, at a m
 | **D**enial of Service | Denial of Service is the ability for an attacker to negatively affect the availability of a system. | Is there a part of the application that is susceptible to being overwhelmed or made entirely unavailable due to overwhelming demand? | Pizza company has a single phone line that only returns busy when called while in use. |
 | **E**levation of Privilege | Elevation of Privilege refers to the ability for an attacker to gain additional privileges and roles beyond what they initially were granted, either through legitimate or illegitimate means. | Can someone gain additional privileges without proper authentication and authorization? | Pizza maker signs into the computer with his manager’s keycard and deletes the order so he doesn’t have to make the pizza. |
 
-### How to answer: “What are we going to do about it?”
+### How to answer: “What are we going to do about it?” {#how-to-answer-what-are-we-going-to-do-about-it}
 
 For each issue identified in the STRIDE model, think through the ways that issue can happen and identify a “treatment” or way of addressing the issue. Answers here should be detailed in how the issue will address the threat identified. This could include code blocks detailing changes or verbal descriptions of how the issue will be addressed.
 
-### How to answer: “Did we do a good job?”
+### How to answer: “Did we do a good job?” {#how-to-answer-did-we-do-a-good-job}
 
 The point of this section is to understand if the analysis done during the other sections was sufficiently deep and broad as to provide value. Some questions to ask and answer here might include:
 
diff --git a/docs/build/smart-contracts/README.mdx b/docs/build/smart-contracts/README.mdx
deleted file mode 100644
index 63dceefb4..000000000
--- a/docs/build/smart-contracts/README.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: "Build, Test, and Deploy Smart Contracts on Stellar: Tools & Best Practices"
-sidebar_position: 20
-sidebar_label: Build Smart Contracts
-description: "Learn how to build, test, deploy, and manage smart contracts on the Stellar network. Explore best practices, tools, guides, and example contracts for development."
----
-
-# Write Smart Contracts
-
-import DocCardList from "@theme/DocCardList";
-
-This section will walk you through how to get set up to write smart contracts on Stellar, plus an introduction to testing, storing data, and deploying your contracts. It also provides an array of example contracts for use.
-
-<DocCardList />
diff --git a/docs/build/smart-contracts/_category_.json b/docs/build/smart-contracts/_category_.json
deleted file mode 100644
index 0d4475828..000000000
--- a/docs/build/smart-contracts/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": false
-}
diff --git a/docs/build/smart-contracts/example-contracts/README.mdx b/docs/build/smart-contracts/example-contracts/README.mdx
deleted file mode 100644
index 82e3536ff..000000000
--- a/docs/build/smart-contracts/example-contracts/README.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: "Example Smart Contracts: Learn, Build, Test & Deploy on the Network"
-sidebar_label: Example Contracts
-description: "Explore example smart contracts to learn key concepts, from basic functions to advanced use cases. Build, test, and deploy contracts on the Stellar network."
-sidebar_position: 30
-hide_table_of_contents: true
----
-
-# Example Contracts
-
-import DocCardList from "@theme/DocCardList";
-
-The Stellar team has put together a large collection of [example contracts] to demonstrate use of smart contracts on Stellar. For many of these example contracts, we've written an accompanying tutorial that will walk you through the example contract and describe a bit more about its design.
-
-The examples listed below are provided in a sequential manner. The first listed example contracts create a solid foundation of concepts that will be required during the later examples. While you are absolutely free to choose, read, and use any of the example contracts you like, please keep in mind that the order you see is intentional.
-
-<DocCardList />
-
-[example contracts]: https://github.com/stellar/soroban-examples
diff --git a/docs/build/smart-contracts/example-contracts/TEMPLATE.mdx b/docs/build/smart-contracts/example-contracts/TEMPLATE.mdx
index a506c0cb6..fd6b4f30c 100644
--- a/docs/build/smart-contracts/example-contracts/TEMPLATE.mdx
+++ b/docs/build/smart-contracts/example-contracts/TEMPLATE.mdx
@@ -2,29 +2,24 @@
 title: Tutorial Template
 description: A description of the tutorial that is being written.
 draft: true
-sidebar_position: 1000
 ---
 
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
 Quick note about what this [example demonstrates]. Maybe it's also based on some [other example].
 
 [![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
 
 [![Open in Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
 
-:::tip
+<Tip>
 
 Place each link definition at the bottom of the section it first is used in.
 
-:::
+</Tip>
 
 [open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
 [open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
 [example demonstrates]: https://github.com/stellar/soroban-examples/tree/main/hello_world
-[other example]: ../getting-started/setup.mdx
+[other example]: ../getting-started/setup
 
 ## Run the Example
 
@@ -50,7 +45,7 @@ running 1 test
 test test::test ... ok
 ```
 
-[setup]: ../getting-started/setup.mdx
+[setup]: ../getting-started/setup
 
 ## Code
 
@@ -152,8 +147,8 @@ If you have [`stellar-cli`] installed, you can deploy the contract and invoke it
 
 ### Deploy
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract deploy \
@@ -163,8 +158,8 @@ stellar contract deploy \
     --network testnet
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract deploy `
@@ -174,13 +169,13 @@ stellar contract deploy `
     --network testnet
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 ### Invoke
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract invoke \
@@ -192,8 +187,8 @@ stellar contract invoke \
     --to Soroban
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract invoke `
@@ -205,10 +200,10 @@ stellar contract invoke `
     --to Soroban
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
-[`stellar-cli`]: ../getting-started/setup.mdx#install-the-stellar-cli
+[`stellar-cli`]: ../getting-started/setup#install-the-stellar-cli
 
 ## Further Reading
 
diff --git a/docs/build/smart-contracts/example-contracts/alloc.mdx b/docs/build/smart-contracts/example-contracts/alloc.mdx
index 6f5ca2af4..9b67ae837 100644
--- a/docs/build/smart-contracts/example-contracts/alloc.mdx
+++ b/docs/build/smart-contracts/example-contracts/alloc.mdx
@@ -1,24 +1,10 @@
 ---
 title: Allocator
+og:title: "Use the allocator feature to emulate heap memory in a smart contract."
+og:description: "Use the allocator feature in the SDK. The lightweight bump-pointer allocator can be used to emulate heap memory allocation in a Wasm smart contract."
 description: Use the allocator feature to emulate heap memory in a smart contract.
-sidebar_position: 80
 ---
 
-<head>
-  <title>
-    {`Use the allocator feature to emulate heap memory in a smart contract.`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Use the allocator feature to emulate heap memory in a smart contract."
-  />
-  <meta
-    property="og:description"
-    content="Use the allocator feature in the SDK. The lightweight bump-pointer allocator can be used to emulate heap memory allocation in a Wasm smart contract."
-  />
-</head>
-
 The [allocator example] demonstrates how to utilize the allocator feature when writing a contract.
 
 [![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
@@ -35,7 +21,7 @@ The `soroban-sdk` crate provides a lightweight bump-pointer allocator which can
 
 First go through the [Setup] process to get your development environment configured, then clone the `v23.0.0` tag of `soroban-examples` repository:
 
-[setup]: ../getting-started/setup.mdx
+[setup]: ../getting-started/setup
 
 ```sh
 git clone -b v23.0.0 https://github.com/stellar/soroban-examples
@@ -107,7 +93,7 @@ extern crate alloc;
 
 Imports the `alloc` crate, which is required in order to support allocation under `no_std`. See [Contract Rust dialect] for more info about `no_std`.
 
-[contract rust dialect]: ../../../learn/fundamentals/contract-development/rust-dialect.mdx
+[contract rust dialect]: ../../../learn/fundamentals/contract-development/rust-dialect
 
 ```rust
 let mut v1 = alloc::vec![];
@@ -115,18 +101,17 @@ let mut v1 = alloc::vec![];
 
 Creates a contiguous growable array `v1` with contents allocated on the heap memory.
 
-:::info
+<Info>
 
 The heap memory in the context of a smart contract actually refers to the Wasm linear memory. The `alloc` will use the global allocator provided by the soroban sdk to interact with the linear memory.
 
-:::
-
-:::caution
+</Info>
+<Warning>
 
 Using heap allocated array is typically slow and computationally expensive. Try to avoid it and instead use a fixed-sized array or `soroban_sdk::vec!` whenever possible.
 
 This is especially the case for a large-size array. Whenever the array size grows beyond the current linear memory size, which is multiple of the page size (64KB), the [`wasm32::memory_grow`](https://doc.rust-lang.org/core/arch/wasm32/fn.memory_grow.html) is invoked to grow the linear memory by more pages as necessary, which is very computationally expensive.
 
-:::
+</Warning>
 
 The remaining code pushes values `(0..count)` to `v1`, then computes and returns their sum. This is the simplest example to illustrate how to use the allocator.
diff --git a/docs/build/smart-contracts/example-contracts/atomic-multi-swap.mdx b/docs/build/smart-contracts/example-contracts/atomic-multi-swap.mdx
index e96bafd66..b0b5b3f99 100644
--- a/docs/build/smart-contracts/example-contracts/atomic-multi-swap.mdx
+++ b/docs/build/smart-contracts/example-contracts/atomic-multi-swap.mdx
@@ -1,22 +1,10 @@
 ---
 title: Batched Atomic Swaps
+og:title: "Swap a token pair among groups of authorized users."
+og:description: "Swap a pair of tokens between two groups of users that authorized the swap operation."
 description: Swap a token pair among groups of authorized users.
-sidebar_position: 100
 ---
 
-<head>
-  <title>Swap a token pair among groups of authorized users.</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Swap a token pair among groups of authorized users."
-  />
-  <meta
-    property="og:description"
-    content="Swap a pair of tokens between two groups of users that authorized the swap operation."
-  />
-</head>
-
 The [atomic swap batching example] swaps a pair of tokens between the two groups of users that authorized the `swap` operation from the [Atomic Swap] example.
 
 This contract basically batches the multiple swaps while following some simple rules to match the swap participants.
@@ -25,7 +13,7 @@ Follow the comments in the code for more information.
 
 [open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
 [open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-[atomic swap]: atomic-swap.mdx
+[atomic swap]: atomic-swap
 [atomic swap batching example]: https://github.com/stellar/soroban-examples/tree/v23.0.0/atomic_multiswap
 
 [![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
diff --git a/docs/build/smart-contracts/example-contracts/atomic-swap.mdx b/docs/build/smart-contracts/example-contracts/atomic-swap.mdx
index 34079d2b8..d42540154 100644
--- a/docs/build/smart-contracts/example-contracts/atomic-swap.mdx
+++ b/docs/build/smart-contracts/example-contracts/atomic-swap.mdx
@@ -1,25 +1,13 @@
 ---
 title: Atomic Swap
+og:title: "Swap tokens atomically between authorized users."
+og:description: "Swap two tokens between two authorized parties atomically using the auth framework; the requested minimum price must be respected for both parties."
 description: Swap tokens atomically between authorized users.
-sidebar_position: 90
 ---
 
-<head>
-  <title>Swap tokens atomically between authorized users.</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Swap tokens atomically between authorized users."
-  />
-  <meta
-    property="og:description"
-    content="Swap two tokens between two authorized parties atomically using the auth framework; the requested minimum price must be respected for both parties."
-  />
-</head>
-
 The [atomic swap example] swaps two tokens between two authorized parties atomically while following the limits they set.
 
-This is example demonstrates advanced usage of Soroban auth framework and assumes the reader is familiar with the [auth example](../example-contracts/auth.mdx) and with Soroban token usage.
+This is example demonstrates advanced usage of Soroban auth framework and assumes the reader is familiar with the [auth example](../example-contracts/auth) and with Soroban token usage.
 
 [![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
 
@@ -33,7 +21,7 @@ This is example demonstrates advanced usage of Soroban auth framework and assume
 
 First go through the [Setup] process to get your development environment configured, then clone the `v23.0.0` tag of `soroban-examples` repository:
 
-[setup]: ../getting-started/setup.mdx
+[setup]: ../getting-started/setup
 
 ```sh
 git clone -b v23.0.0 https://github.com/stellar/soroban-examples
diff --git a/docs/build/smart-contracts/example-contracts/auth.mdx b/docs/build/smart-contracts/example-contracts/auth.mdx
index 754c151b8..36faea100 100644
--- a/docs/build/smart-contracts/example-contracts/auth.mdx
+++ b/docs/build/smart-contracts/example-contracts/auth.mdx
@@ -1,26 +1,10 @@
 ---
 title: Auth
+og:title: "Implement authentication and authorization."
+og:description: "Implement authentication and authorization into your smart contract using the Soroban Host-managed auth framework."
 description: Implement authentication and authorization.
-sidebar_position: 50
 ---
 
-<head>
-  <title>Implement authentication and authorization.</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Implement authentication and authorization."
-  />
-  <meta
-    property="og:description"
-    content="Implement authentication and authorization into your smart contract using the Soroban Host-managed auth framework."
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
 The [auth example] demonstrates how to implement authentication and authorization using the Soroban Host-managed auth framework.
 
 This example is an extension of the [storing data example].
@@ -31,14 +15,14 @@ This example is an extension of the [storing data example].
 
 [open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
 [open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-[storing data example]: ../getting-started/storing-data.mdx
+[storing data example]: ../getting-started/storing-data
 [auth example]: https://github.com/stellar/soroban-examples/tree/v23.0.0/auth
 
 ## Run the Example
 
 First go through the [Setup] process to get your development environment configured, then clone the `v23.0.0` tag of `soroban-examples` repository:
 
-[setup]: ../getting-started/setup.mdx
+[setup]: ../getting-started/setup
 
 ```
 git clone -b v23.0.0 https://github.com/stellar/soroban-examples
@@ -132,13 +116,15 @@ pub enum DataKey {
 
 `Address` is a universal Soroban identifier that may represent a Stellar account, a contract, or a contract account (a contract that defines a custom authentication scheme and authorization policies). Contracts don't need to distinguish between these internal representations though. `Address` can be used any time some network identity needs to be represented, like to distinguish between counters for different users in this example.
 
-:::tip[Enum keys like `DataKey` are useful for organizing contract storage.]
+<Tip>
+
+**Enum keys like `DataKey` are useful for organizing contract storage.**
 
 Different enum values create different key 'namespaces'.
 
 In the example the counter for each address is stored against `DataKey::Counter(Address)`. If the contract needs to start storing other types of data, it can do so by adding additional variants to the enum.
 
-:::
+</Tip>
 
 ### `require_auth`
 
@@ -323,8 +309,8 @@ GAJGHZ44IJXYFNOVRZGBCVKC2V62DB2KHZB7BEMYOWOLFQH4XP2TAM6B
 
 ### Deploy
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract deploy \
@@ -334,8 +320,8 @@ stellar contract deploy \
     --network testnet
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract deploy `
@@ -345,15 +331,15 @@ stellar contract deploy `
     --network testnet
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 ### Invoke
 
 Now the contract itself can be invoked. Notice the `--source-account` must be the identity name matching the address passed to the `--user` argument. This allows `Stellar CLI` to automatically sign the necessary payload for the invocation.
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract invoke \
@@ -366,8 +352,8 @@ stellar contract invoke \
     --value 2
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract invoke `
@@ -380,13 +366,13 @@ stellar contract invoke `
     --value 2
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 Run a few more increments for both accounts.
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract invoke \
@@ -421,8 +407,8 @@ stellar contract invoke \
     --value 10
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract invoke `
@@ -457,7 +443,7 @@ stellar contract invoke `
     --value 10
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 View the data that has been stored against each user with `stellar contract read`.
@@ -473,8 +459,8 @@ stellar contract read --id auth_example --network testnet
 
 It is also possible to preview the authorization payload that is being signed by providing `--auth` flag to the invocation:
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract invoke \
@@ -488,8 +474,8 @@ stellar contract invoke \
     --value 123
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract invoke `
@@ -503,21 +489,21 @@ stellar contract invoke `
     --value 123
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 ```json
 Contract auth: [{"address_with_nonce":null,"root_invocation":{"contract_id":"0000000000000000000000000000000000000000000000000000000000000001","function_name":"increment","args":[{"object":{"address":{"account":{"public_key_type_ed25519":"c7bab0288753d58d3e21cc3fa68cd2546b5f78ae6635a6f1b3fe07e03ee846e9"}}}},{"u32":123}],"sub_invocations":[]},"signature_args":[]}]
 ```
 
-[`stellar-cli`]: ../getting-started/setup.mdx#install-the-stellar-cli
+[`stellar-cli`]: ../getting-started/setup#install-the-stellar-cli
 
 ## Further reading
 
-[Authorization documentation](../../../learn/fundamentals/contract-development/authorization.mdx) provides more details on how Soroban auth framework works.
+[Authorization documentation](../../../learn/fundamentals/contract-development/authorization) provides more details on how Soroban auth framework works.
 
-[Timelock](../example-contracts/timelock.mdx) and [Single Offer](../example-contracts/single-offer-sale.mdx) examples demonstrate authorizing token operations on behalf of the user, which can be extended to any nested contract invocations.
+[Timelock](../example-contracts/timelock) and [Single Offer](../example-contracts/single-offer-sale) examples demonstrate authorizing token operations on behalf of the user, which can be extended to any nested contract invocations.
 
-[Atomic Swap](../example-contracts/atomic-swap.mdx) example demonstrates multi-party authorization where multiple users sign their parts of the contract invocation.
+[Atomic Swap](../example-contracts/atomic-swap) example demonstrates multi-party authorization where multiple users sign their parts of the contract invocation.
 
-[Simple Account](../example-contracts/simple-account.mdx) example demonstrates a minimal contract account implementation and how `__check_auth` works end-to-end.
+[Simple Account](../example-contracts/simple-account) example demonstrates a minimal contract account implementation and how `__check_auth` works end-to-end.
diff --git a/docs/build/smart-contracts/example-contracts/bls-signature.mdx b/docs/build/smart-contracts/example-contracts/bls-signature.mdx
index eeb74c5b4..2e19d93c3 100644
--- a/docs/build/smart-contracts/example-contracts/bls-signature.mdx
+++ b/docs/build/smart-contracts/example-contracts/bls-signature.mdx
@@ -1,26 +1,10 @@
 ---
 title: BLS Signature
+og:title: "A contract account with BLS signature verification."
+og:description: "A basic contract account implementing the `FastAggregateVerify` function in [BLS Signatures](https://www.ietf.org/archive/id/draft-irtf-cfrg-bls-signature-05.html#name-fastaggregateverify) draft."
 description: A contract account with BLS signature verification.
-sidebar_position: 17
 ---
 
-<head>
-  <title>BLS Signature</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="A contract account with BLS signature verification."
-  />
-  <meta
-    property="og:description"
-    content="A basic contract account implementing the `FastAggregateVerify` function in [BLS Signatures](https://www.ietf.org/archive/id/draft-irtf-cfrg-bls-signature-05.html#name-fastaggregateverify) draft."
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
 The [BLS signature example] illustrates how to implement BLS signature verification inside a contract account.
 
 This example is based off of the [Complex Account example]. Although the main goal is to illustrate the practical use of the BLS12-381 functionalities in a relevant setting.
@@ -34,8 +18,8 @@ It is good to have an understanding of how a contract account works, so walk thr
 [open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
 [open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
 [BLS signature example]: https://github.com/stellar/soroban-examples/tree/main/bls_signature
-[Complex Account example]: ./complex-account.mdx
-[Simple Account example]: ./simple-account.mdx
+[Complex Account example]: ./complex-account
+[Simple Account example]: ./simple-account
 
 ## Background on BLS Signature
 
@@ -59,19 +43,18 @@ e(pk_{agg}, H(m)) = e(g1, \sigma_{agg})
 
 with a single pairing on chain, you can verify N signatures on the same message in constant time. In general, `n` unique messages takes `n + 1` pairing operations to verify all signatures.
 
-### Hash of message `H(m)`
+### Hash of message `H(m)` {#hash-of-message-hm}
 
 The message will need to be hashed on the curve `H(m)` for pairing operation to be applied. We follow the approach outlined in [RFC 9380 - Hashing to Elliptic Curves](https://datatracker.ietf.org/doc/rfc9380).
 
 The hashing method requires a unique domain separation tag (DST), it is highly advisable that your application choose a unique DST. For the requirements of DST, refer to section 3.1 of the RFC,
 
-:::tip
+<Tip>
 
 For digital signatures, the G1 and G2 groups can be used interchangeably. Public keys can be chosen as elements of G1 with signatures in G2, or the other way around. The choice involves trade-offs between execution speed and storage size. G1 offers smaller points and faster operations, whereas G2 has larger points and slower performance.
 
-:::
-
-:::caution
+</Tip>
+<Warning>
 
 The example presented below is intended for demonstration purpose only
 
@@ -80,13 +63,13 @@ The example presented below is intended for demonstration purpose only
 
 Implementing a production-safe signature scheme requires deep understanding of the underlying cryptography and security considerations. **Use this at your own risk**.
 
-:::
+</Warning>
 
 ## Run the Example
 
 First go through the [Setup] process to get your development environment configured, then clone the `main` branch of `soroban-examples` repository:
 
-[setup]: ../getting-started/setup.mdx
+[setup]: ../getting-started/setup
 
 ```
 git clone -b main https://github.com/stellar/soroban-examples
diff --git a/docs/build/smart-contracts/example-contracts/complex-account.mdx b/docs/build/smart-contracts/example-contracts/complex-account.mdx
index 4030ca01c..1cea628d3 100644
--- a/docs/build/smart-contracts/example-contracts/complex-account.mdx
+++ b/docs/build/smart-contracts/example-contracts/complex-account.mdx
@@ -1,39 +1,24 @@
 ---
 title: Complex Account
+og:title: "Implement a contract account with multisig and custom authorization policies."
+og:description: "Build on the Simple Account example to add multisig rules and policy logic that run whenever this account authorizes a call."
 description: Implement a contract account with multisig and custom authorization policies.
-sidebar_position: 16
 ---
 
-<head>
-  <title>
-    {`Implement a contract account with multisig and custom authorization policies.`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Implement a contract account with multisig and custom authorization policies."
-  />
-  <meta
-    property="og:description"
-    content="Build on the Simple Account example to add multisig rules and policy logic that run whenever this account authorizes a call."
-  />
-</head>
-
-Start with the [Simple Account example](./simple-account.mdx) to learn the single-signer basics. This Complex Account extends that baseline with multisig and customizable authorization policies. Any time an `Address` pointing at this contract instance is used, the logic defined here runs through the Soroban auth framework.
+Start with the [Simple Account example](./simple-account) to learn the single-signer basics. This Complex Account extends that baseline with multisig and customizable authorization policies. Any time an `Address` pointing at this contract instance is used, the logic defined here runs through the Soroban auth framework.
 
 Contract accounts are exclusive to Soroban and can't be used to perform other Stellar operations.
 
-:::danger
+<Danger>
 
 Implementing a contract account requires a very good understanding of authentication and authorization and requires rigorous testing and review. The example here is _not_ a full-fledged account contract - use it as an API reference only.
 
-:::
-
-:::caution
+</Danger>
+<Warning>
 
 While contract accounts are supported by the Stellar protocol and Soroban SDK, the full client support (such as transaction simulation) is still under development.
 
-:::
+</Warning>
 
 [![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
 
@@ -47,7 +32,7 @@ While contract accounts are supported by the Stellar protocol and Soroban SDK, t
 
 First go through the [Setup] process to get your development environment configured, then clone the `v23.0.0` tag of `soroban-examples` repository:
 
-[setup]: ../getting-started/setup.mdx
+[setup]: ../getting-started/setup
 
 ```sh
 git clone -b v23.0.0 https://github.com/stellar/soroban-examples
@@ -456,4 +441,4 @@ assert_eq!(
 
 ## Further Reading
 
-- [Delegate Auth example](./delegate-auth.mdx) — extends this example with CAP-71 auth delegation to registered delegate signers.
+- [Delegate Auth example](./delegate-auth) — extends this example with CAP-71 auth delegation to registered delegate signers.
diff --git a/docs/build/smart-contracts/example-contracts/cross-contract-call.mdx b/docs/build/smart-contracts/example-contracts/cross-contract-call.mdx
index 8e0a52cb8..85e14b385 100644
--- a/docs/build/smart-contracts/example-contracts/cross-contract-call.mdx
+++ b/docs/build/smart-contracts/example-contracts/cross-contract-call.mdx
@@ -1,37 +1,21 @@
 ---
 title: Cross Contract Calls
+og:title: "Call a smart contract from another smart contract."
+og:description: "Perform a cross contract call by invoking another contract using its contract ID."
 description: Call a smart contract from another smart contract.
-sidebar_position: 60
 ---
 
-<head>
-  <title>Call a smart contract from another smart contract.</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Call a smart contract from another smart contract."
-  />
-  <meta
-    property="og:description"
-    content="Perform a cross contract call by invoking another contract using its contract ID."
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
 The [cross contract call example] demonstrates how to call a contract from another contract.
 
 [![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
 
 [![Open in Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
 
-:::info
+<Info>
 
 In this example there are two contracts that are compiled separately, deployed separately, and then tested together. There are a variety of ways to develop and test contracts with dependencies on other contracts, and the Soroban SDK and tooling is still building out the tools to support these workflows. Feedback appreciated [here](https://github.com/stellar/rs-soroban-sdk/issues/new/choose).
 
-:::
+</Info>
 
 [open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
 [open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
@@ -41,7 +25,7 @@ In this example there are two contracts that are compiled separately, deployed s
 
 First go through the [Setup] process to get your development environment configured, then clone the `v23.0.0` tag of `soroban-examples` repository:
 
-[setup]: ../getting-started/setup.mdx
+[setup]: ../getting-started/setup
 
 ```sh
 git clone -b v23.0.0 https://github.com/stellar/soroban-examples
@@ -114,11 +98,11 @@ Contracts to invoke can be imported into your contract with the use of `contract
 - A `ContractClient` type that can be used to invoke functions on the contract.
 - Any types in the contract that were annotated with `#[contracttype]`.
 
-:::tip
+<Tip>
 
 The `contractimport!` macro will generate the types in the module it is used, so it's a good idea to use the macro inside a `mod { ... }` block, or inside its own file, so that the names of generated types don't collide with names of types in your own contract.
 
-:::
+</Tip>
 
 Open the files above to follow along.
 
@@ -138,11 +122,11 @@ impl ContractA {
 }
 ```
 
-:::tip
+<Tip>
 
 The contract uses the `checked_add` method to ensure that there is no overflow, and if there is overflow, panics rather than returning an overflowed value. Rust's primitive integer types all have checked operations available as functions with the prefix `checked_`.
 
-:::
+</Tip>
 
 ### Contract B: The Contract doing the Calling
 
@@ -255,8 +239,8 @@ target/wasm32v1-none/release/soroban_cross_contract_b_contract.wasm
 
 If you have [`stellar-cli`] installed, you can invoke contract functions. Both contracts must be deployed.
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract deploy \
@@ -274,8 +258,8 @@ stellar contract deploy \
     --network testnet
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract deploy `
@@ -293,13 +277,13 @@ stellar contract deploy `
     --network testnet
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 Invoke Contract B's `add_with` function, passing in values for `x` and `y` (e.g. as `5` and `7`), and then pass in the contract ID or alias of Contract A.
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract invoke \
@@ -313,8 +297,8 @@ stellar contract invoke \
     --y 7
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract invoke `
@@ -328,7 +312,7 @@ stellar contract invoke `
     --y 7
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 The following output should occur using the code above.
@@ -339,4 +323,4 @@ The following output should occur using the code above.
 
 Contract B's `add_with` function invoked Contract A's `add` function to do the addition.
 
-[`stellar-cli`]: ../getting-started/setup.mdx#install-the-stellar-cli
+[`stellar-cli`]: ../getting-started/setup#install-the-stellar-cli
diff --git a/docs/build/smart-contracts/example-contracts/custom-types.mdx b/docs/build/smart-contracts/example-contracts/custom-types.mdx
index ed1e80442..a60e3e008 100644
--- a/docs/build/smart-contracts/example-contracts/custom-types.mdx
+++ b/docs/build/smart-contracts/example-contracts/custom-types.mdx
@@ -1,26 +1,10 @@
 ---
 title: Custom Types
+og:title: "Define your own data structures in a smart contract."
+og:description: "Define the data structures that can be stored on the ledger or used as inputs and outputs to contract invocations. They can be either structs or enums."
 description: Define your own data structures in a smart contract.
-sidebar_position: 20
 ---
 
-<head>
-  <title>Define your own data structures in a smart contract.</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Define your own data structures in a smart contract."
-  />
-  <meta
-    property="og:description"
-    content="Define the data structures that can be stored on the ledger or used as inputs and outputs to contract invocations. They can be either structs or enums."
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
 The [custom types example] demonstrates how to define your own data structures that can be stored on the ledger, or used as inputs and outputs to contract invocations. This example is an extension of the [storing data example].
 
 [![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
@@ -30,13 +14,13 @@ The [custom types example] demonstrates how to define your own data structures t
 [open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
 [open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
 [custom types example]: https://github.com/stellar/soroban-examples/tree/v23.0.0/custom_types
-[storing data example]: ../getting-started/storing-data.mdx
+[storing data example]: ../getting-started/storing-data
 
 ## Run the Example
 
 First go through the [Setup] process to get your development environment configured, then clone the `v23.0.0` tag of `soroban-examples` repository:
 
-[setup]: ../getting-started/setup.mdx
+[setup]: ../getting-started/setup
 
 ```sh
 git clone -b v23.0.0 https://github.com/stellar/soroban-examples
@@ -262,8 +246,8 @@ target/wasm32v1-none/release/soroban_custom_types_contract.wasm
 
 If you have [`stellar-cli`] installed, you can [deploy] and invoke contract function.
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract invoke \
@@ -275,8 +259,8 @@ stellar contract invoke \
     --incr 5
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract invoke `
@@ -288,7 +272,7 @@ stellar contract invoke `
     --incr 5
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 The following output should occur using the code above.
@@ -309,5 +293,5 @@ stellar contract read --id 1 --key STATE
 STATE,"{""count"":25,""last_incr"":15}"
 ```
 
-[`stellar-cli`]: ../getting-started/setup.mdx#install-the-stellar-cli
+[`stellar-cli`]: ../getting-started/setup#install-the-stellar-cli
 [deploy]: ../getting-started/deploy-to-testnet
diff --git a/docs/build/smart-contracts/example-contracts/delegate-auth.mdx b/docs/build/smart-contracts/example-contracts/delegate-auth.mdx
index 0a46108de..bc44b1812 100644
--- a/docs/build/smart-contracts/example-contracts/delegate-auth.mdx
+++ b/docs/build/smart-contracts/example-contracts/delegate-auth.mdx
@@ -1,38 +1,24 @@
 ---
 title: Delegate Auth
-sidebar_label: Delegate Auth
+og:title: "A custom account contract that delegates __check_auth to registered signer contracts."
+og:description: "Learn how to implement modular account auth delegation using CAP-71: get_delegated_signers and delegate_auth in soroban-sdk v27."
 description: A custom account contract that uses CAP-71 auth delegation to forward __check_auth to registered delegate signers.
-sidebar_position: 18
 ---
 
-<head>
-  <title>Delegate Auth</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="A custom account contract that delegates __check_auth to registered signer contracts."
-  />
-  <meta
-    property="og:description"
-    content="Learn how to implement modular account auth delegation using CAP-71: get_delegated_signers and delegate_auth in soroban-sdk v27."
-  />
-</head>
-
 This example shows **auth delegation**: a `ModularAccount` contract performs no signature verification itself. Instead, it stores a set of registered signer addresses and, when `__check_auth` is called, forwards the authorization context to whichever of those signers the user attached to the transaction. Each delegate runs its own `__check_auth` independently.
 
-Auth delegation was introduced in soroban-sdk v27 via [CAP-71](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0071.md). For a single-key account see the [Simple Account example](./simple-account.mdx), and for a multi-sig account with spend-limit policies see the [Complex Account example](./complex-account.mdx).
+Auth delegation was introduced in soroban-sdk v27 via [CAP-71](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0071.md). For a single-key account see the [Simple Account example](./simple-account), and for a multi-sig account with spend-limit policies see the [Complex Account example](./complex-account).
 
-:::danger
+<Danger>
 
 Implementing a contract account requires a very good understanding of authentication and authorization and requires rigorous testing and review. The example here is _not_ a full-fledged account contract — use it as an API reference only.
 
-:::
-
-:::caution
+</Danger>
+<Warning>
 
 While contract accounts are supported by the Stellar protocol and Soroban SDK, the full client support (such as transaction simulation) is still under development.
 
-:::
+</Warning>
 
 [![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
 
@@ -68,7 +54,7 @@ test test::test ... ok
 test result: ok. 3 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
 ```
 
-[setup]: ../getting-started/setup.mdx
+[setup]: ../getting-started/setup
 
 ## Code
 
@@ -179,7 +165,7 @@ pub fn __constructor(env: Env, signers: Vec<Address>) {
 
 Each allowed delegate address is persisted individually at deployment. A production account would also expose an admin function to add or remove signers after deployment.
 
-### `type Signature = ()`
+### `type Signature = ()` {#type-signature--}
 
 ```rust
 type Signature = ();
@@ -187,7 +173,7 @@ type Signature = ();
 
 `ModularAccount` verifies no signature of its own — it relies entirely on its delegates. Setting `Signature = ()` tells the Soroban host that no signature data needs to be passed to `__check_auth`. The user's wallet still builds a full `SorobanAddressCredentialsWithDelegates` auth entry (see the test), but the account-level signature field is empty.
 
-### `__check_auth`: get → verify → forward
+### `__check_auth`: get → verify → forward {#\_\_check_auth-get--verify--forward}
 
 ```rust
 let delegates = env.custom_account().get_delegated_signers();
@@ -258,11 +244,11 @@ After the call, the test asserts two things:
 
 Two further tests cover the rejection paths: `test_unknown_delegate_is_rejected` attaches a delegate the account never registered, and `test_empty_delegates_is_rejected` attaches none at all. In both, `Protected::protected` fails. The caller only sees a generic `Error(Auth, InvalidAction)`, because the host escalates any failed `__check_auth` to that — the account's own error code does not propagate to the return value. To assert the account rejected the call for its own reason, the tests read the host's diagnostic events with `env.host().get_diagnostic_events()` and match the recorded `Error(Contract, #n)` — `UnknownDelegate` and `InsufficientDelegates` respectively.
 
-:::note
+<Note>
 
 Testing delegated auth via `env.try_invoke_contract_check_auth` is not supported. Use `env.set_auths` with `SorobanAddressCredentialsWithDelegates` and a wrapper contract call instead, as shown in the test.
 
-:::
+</Note>
 
 ## Build the Contract
 
@@ -278,7 +264,7 @@ target/wasm32v1-none/release/soroban_modular_account_contract.wasm
 
 ## Further Reading
 
-- [Simple Account example](./simple-account.mdx) — the minimal single-key baseline.
-- [Complex Account example](./complex-account.mdx) — multisig and spend-limit policies.
+- [Simple Account example](./simple-account) — the minimal single-key baseline.
+- [Complex Account example](./complex-account) — multisig and spend-limit policies.
 - [CAP-71 specification](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0071.md) — the protocol change that introduced auth delegation.
 - [`CustomAccount` API docs](https://docs.rs/soroban-sdk/latest/soroban_sdk/custom_account/struct.CustomAccount.html) — reference for `get_delegated_signers` and `delegate_auth`.
diff --git a/docs/build/smart-contracts/example-contracts/deployer.mdx b/docs/build/smart-contracts/example-contracts/deployer.mdx
index 7c36ec711..793fe0661 100644
--- a/docs/build/smart-contracts/example-contracts/deployer.mdx
+++ b/docs/build/smart-contracts/example-contracts/deployer.mdx
@@ -1,37 +1,19 @@
 ---
 title: Deployer
+og:title: "Deploy and initialize a smart contract using another smart contract."
+og:description: "Deploy a smart contract on behalf of any other address using the SDK `deployer()` and initialize it atomically."
 description: Deploy and initialize a smart contract using another smart contract.
-sidebar_position: 70
 ---
 
-<head>
-  <title>
-    {`Deploy and initialize a smart contract using another smart contract.`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Deploy and initialize a smart contract using another smart contract."
-  />
-  <meta
-    property="og:description"
-    content="Deploy a smart contract on behalf of any other address using the SDK `deployer()` and initialize it atomically."
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
 The [deployer example] demonstrates how to deploy contracts using a contract.
 
 Here we deploy a contract on behalf of any address and initialize it atomically.
 
-:::info
+<Info>
 
 In this example there are two contracts that are compiled separately, and the tests deploy one with the other.
 
-:::
+</Info>
 
 [![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
 
@@ -45,7 +27,7 @@ In this example there are two contracts that are compiled separately, and the te
 
 First go through the [Setup] process to get your development environment configured, then clone the `main` branch of `soroban-examples` repository:
 
-[setup]: ../getting-started/setup.mdx
+[setup]: ../getting-started/setup
 
 ```sh
 git clone -b main https://github.com/stellar/soroban-examples
@@ -125,15 +107,15 @@ Open the `deployer/deployer/src/lib.rs` file to follow along.
 
 Before deploying the new contract instances, the Wasm code needs to be uploaded on-chain. Then it can be used to deploy an arbitrary number of contract instances. The upload should typically happen outside of the deployer contract, as it needs to happen just once. However, it is possible to use `env.deployer().upload_contract_wasm()` function to upload Wasm from a contract as well.
 
-See the [tests](#tests) for an example of uploading the contract code programmatically. For the actual on-chain installation see the general deployment [tutorial](../../smart-contracts/getting-started/deploy-to-testnet.mdx).
+See the [tests](#tests) for an example of uploading the contract code programmatically. For the actual on-chain installation see the general deployment [tutorial](../../smart-contracts/getting-started/deploy-to-testnet).
 
 ### Authorization
 
-:::info
+<Info>
 
-For introduction to Soroban authorization see the [auth tutorial](./auth.mdx).
+For introduction to Soroban authorization see the [auth tutorial](./auth).
 
-:::
+</Info>
 
 We start with verifying authorization of the deployer contract's admin. Without that anyone would be able to call the `deploy` function with any arguments, which may not always be desirable (however, there are contracts where it's perfectly fine to have permissionless deployments).
 
@@ -146,7 +128,7 @@ admin.require_auth();
 
 See more details on the actual authorization payloads in [tests](#tests).
 
-### `env.deployer()`
+### `env.deployer()` {#envdeployer}
 
 The `env.deployer()` SDK function comes with a few deployment-related utilities. Here we use the most generic deployer kind, `with_address(env.current_contract_address(), salt)`.
 
@@ -159,19 +141,19 @@ let deployed_address = env
 
 `with_address()` accepts the `deployer` address and `salt`. Both are used to derive the address of the deployed contract deterministically. It is not possible to re-deploy an already existing contract.
 
-:::tip
+<Tip>
 
 The `env.deployer().with_address(env.current_contract_address(), salt)` call may be replaced with the `env.deployer().with_current_contract(salt)` function for brevity.
 
-:::
+</Tip>
 
 The `deploy_contract()` function performs the actual deployment using the provided executable, here `ContractExecutable::Wasm(wasm_hash)`. The implementation of the new contract is defined by the Wasm file uploaded under `wasm_hash`. `constructor_args` are the arguments that will be passed to the constructor of the contract that is being deployed. If the deployed contract has no constructor, empty argument vector should be passed.
 
-:::tip
+<Tip>
 
 Only the `wasm_hash` itself is stored per contract ID thus saving the ledger space and fees.
 
-:::
+</Tip>
 
 ### Tests
 
@@ -355,8 +337,8 @@ This will return the deployer address: `CAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
 
 Then the deployer contract may be invoked with the Wasm hash value above.
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract invoke --id 1 -- deploy \
@@ -366,8 +348,8 @@ stellar contract invoke --id 1 -- deploy \
     --constructor_args '[{"u32":5}]'
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract invoke --id 1 -- deploy `
@@ -377,13 +359,13 @@ stellar contract invoke --id 1 -- deploy `
     --constructor_args '[{"u32":5}]'
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 And then invoke the deployed test contract using the identifier returned from the previous command.
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract invoke \
@@ -392,8 +374,8 @@ stellar contract invoke \
     value
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract invoke `
@@ -402,7 +384,7 @@ stellar contract invoke `
     value
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 The following output should occur using the code above.
@@ -411,4 +393,4 @@ The following output should occur using the code above.
 5
 ```
 
-[`stellar-cli`]: ../getting-started/setup.mdx#install-the-stellar-cli
+[`stellar-cli`]: ../getting-started/setup#install-the-stellar-cli
diff --git a/docs/build/smart-contracts/example-contracts/errors.mdx b/docs/build/smart-contracts/example-contracts/errors.mdx
index 1cc046581..c4f30561b 100644
--- a/docs/build/smart-contracts/example-contracts/errors.mdx
+++ b/docs/build/smart-contracts/example-contracts/errors.mdx
@@ -1,26 +1,10 @@
 ---
 title: Errors
+og:title: "Define and generate errors in a smart contract."
+og:description: "Define and generate errors in a smart contract that invokers of the contract can understand and handle."
 description: Define and generate errors in a smart contract.
-sidebar_position: 30
 ---
 
-<head>
-  <title>Define and generate errors in a smart contract.</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Define and generate errors in a smart contract."
-  />
-  <meta
-    property="og:description"
-    content="Define and generate errors in a smart contract that invokers of the contract can understand and handle."
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
 The [errors example] demonstrates how to define and generate errors in a contract that invokers of the contract can understand and handle. This example is an extension of the [storing data example].
 
 [![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
@@ -30,13 +14,13 @@ The [errors example] demonstrates how to define and generate errors in a contrac
 [open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
 [open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
 [errors example]: https://github.com/stellar/soroban-examples/tree/v23.0.0/errors
-[storing data example]: ../getting-started/storing-data.mdx
+[storing data example]: ../getting-started/storing-data
 
 ## Run the Example
 
 First go through the [Setup] process to get your development environment configured, then clone the `v23.0.0` tag of `soroban-examples` repository:
 
-[setup]: ../getting-started/setup.mdx
+[setup]: ../getting-started/setup
 
 ```sh
 git clone -b v23.0.0 https://github.com/stellar/soroban-examples
@@ -154,11 +138,11 @@ pub enum Error {
 
 Contract errors cannot be stored as contract data, and therefore cannot be used as types on fields of contract types.
 
-:::tip
+<Tip>
 
 If an error is returned from a function anything the function has done is rolled back. If ledger entries have been altered, or contract data stored, all those changes are reverted and will not be persisted.
 
-:::
+</Tip>
 
 ### Returning an Error
 
@@ -198,11 +182,11 @@ pub fn increment(env: Env) -> u32 {
 }
 ```
 
-:::caution
+<Warning>
 
 Functions that do not return a `Result<_, E>` type do not include in their specification what the possible error values are. This makes it more difficult for other contracts and clients to integrate with the contract. However, this might be ideal if the errors are diagnostic and debugging, and not intended to be handled.
 
-:::
+</Warning>
 
 ## Tests
 
@@ -306,8 +290,8 @@ target/wasm32v1-none/release/soroban_errors_contract.wasm
 
 Let's deploy the contract to Testnet so we can run it. The value provided as `--source-account` was set up in our Getting Started guide; please change accordingly if you created a different identity.
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract deploy \
@@ -316,8 +300,8 @@ stellar contract deploy \
   --network testnet
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract deploy `
@@ -326,15 +310,15 @@ stellar contract deploy `
   --network testnet
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 The command above will output the contract id, which in our case is `CA4KWO3HL6M5F5MZ5ITVFLCQ6ZM2GDSP2NOTNXOT4GIRECQOVX3I6CXL`.
 
 Now that we've deployed the contract, we can invoke it.
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract invoke \
@@ -345,8 +329,8 @@ stellar contract invoke \
     increment
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract invoke `
@@ -357,7 +341,7 @@ stellar contract invoke `
     increment
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 Run the command a few times and on the 6th invocation you should see an error like this:
@@ -372,8 +356,8 @@ Event log (newest first):
 
 To retrieve the current counter value, use the command `stellar contract read`.
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract read \
@@ -384,8 +368,8 @@ stellar contract read \
   --output json
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract read `
@@ -396,7 +380,7 @@ stellar contract read `
   --output json
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
-[`stellar-cli`]: ../getting-started/setup.mdx#install-the-stellar-cli
+[`stellar-cli`]: ../getting-started/setup#install-the-stellar-cli
diff --git a/docs/build/smart-contracts/example-contracts/events.mdx b/docs/build/smart-contracts/example-contracts/events.mdx
index 7ea6b1f3b..e9a60fedb 100644
--- a/docs/build/smart-contracts/example-contracts/events.mdx
+++ b/docs/build/smart-contracts/example-contracts/events.mdx
@@ -1,30 +1,19 @@
 ---
 title: Events
+og:title: "Publish events from a smart contract."
+og:description: "Publish events from a smart contract. Contract events let contracts emit information about what the contract is doing using the environment events publish function."
 description: Publish events from a smart contract.
-sidebar_position: 10
 ---
 
-<head>
-  <title>Publish events from a smart contract.</title>
-  <meta charSet="utf-8" />
-  <meta property="og:title" content="Publish events from a smart contract." />
-  <meta
-    property="og:description"
-    content="Publish events from a smart contract. Contract events let contracts emit information about what the contract is doing using the environment events publish function."
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
 The [events example] demonstrates how to publish events from a contract. This example is an extension of the [storing data example].
 
-:::tip[Whisk Changes]
+<Tip>
+
+**Whisk Changes**
 
 With the release of Whisk, Protocol 23, the syntax for publishing smart contract events has changed. In order to provide the most up-to-date information, this example has been updated to include the new patterns. Find more detailed information in the [Rust SDK documentation].
 
-:::
+</Tip>
 
 [![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
 
@@ -33,14 +22,14 @@ With the release of Whisk, Protocol 23, the syntax for publishing smart contract
 [open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
 [open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
 [events example]: https://github.com/stellar/soroban-examples/tree/main/events
-[storing data example]: ../getting-started/storing-data.mdx
+[storing data example]: ../getting-started/storing-data
 [Rust SDK documentation]: https://docs.rs/soroban-sdk/latest/soroban_sdk/_migrating/v23_contractevent/index.html
 
 ## Run the Example
 
 First go through the [Setup] process to get your development environment configured, then clone the `main` branch of the `soroban-examples` repository:
 
-[setup]: ../getting-started/setup.mdx
+[setup]: ../getting-started/setup
 
 ```sh
 git clone -b main https://github.com/stellar/soroban-examples
@@ -133,11 +122,11 @@ Topics can be defined either statically or dynamically. In the sample code two s
 #[contractevent(topics = ["COUNTER", "increment"], ...)]
 ```
 
-:::tip
+<Tip>
 
 The topics don't have to be made of the same type.
 
-:::
+</Tip>
 
 Topics can also be defined dynamically, inside the struct. In this case, the struct's `snake_case` name will be the first topic. For example, the following event will have two topics: the `Symbol` "increment", followed by an `Address`.
 
@@ -168,11 +157,11 @@ Publishing an event is done by calling the `publish` function on the created eve
 IncrementEvent { count }.publish(&env);
 ```
 
-:::caution
+<Warning>
 
 Published events are discarded if a contract invocation fails due to a panic, budget exhaustion, or when the contract returns an error.
 
-:::
+</Warning>
 
 ## Tests
 
@@ -303,8 +292,8 @@ If you have [`stellar-cli`] installed, you can deploy the contract and invoke it
 
 ### Deploy
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract deploy \
@@ -314,8 +303,8 @@ stellar contract deploy \
     --network testnet
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract deploy `
@@ -325,13 +314,13 @@ stellar contract deploy `
     --network testnet
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 ### Invoke
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract invoke \
@@ -342,8 +331,8 @@ stellar contract invoke \
     increment
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract invoke `
@@ -354,7 +343,7 @@ stellar contract invoke `
     increment
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 The following output should occur using the code above.
@@ -366,4 +355,4 @@ The following output should occur using the code above.
 
 A single event is outputted, which is the contract event the contract published. The event contains the two topics, each a `Symbol`, and the data object containing the `u32`.
 
-[`stellar-cli`]: ../getting-started/setup.mdx#install-the-stellar-cli
+[`stellar-cli`]: ../getting-started/setup#install-the-stellar-cli
diff --git a/docs/build/smart-contracts/example-contracts/fuzzing.mdx b/docs/build/smart-contracts/example-contracts/fuzzing.mdx
index 1abf224df..27db70363 100644
--- a/docs/build/smart-contracts/example-contracts/fuzzing.mdx
+++ b/docs/build/smart-contracts/example-contracts/fuzzing.mdx
@@ -1,24 +1,10 @@
 ---
 title: Fuzz Testing
+og:title: "Increase confidence in a contract's correctness with fuzz testing."
+og:description: "Fuzz test smart contracts with cargo-fuzz and customize the input to fuzz tests with arbitrary crate; demonstrate how to adapt fuzz tests to reusable property tests."
 description: Increase confidence in a contract's correctness with fuzz testing.
-sidebar_position: 160
 ---
 
-<head>
-  <title>
-    {`Increase confidence in a contract's correctness with fuzz testing.`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Increase confidence in a contract's correctness with fuzz testing."
-  />
-  <meta
-    property="og:description"
-    content="Fuzz test smart contracts with cargo-fuzz and customize the input to fuzz tests with arbitrary crate; demonstrate how to adapt fuzz tests to reusable property tests."
-  />
-</head>
-
 The [fuzzing example] demonstrates how to fuzz test Soroban contracts with [`cargo-fuzz`] and customize the input to fuzz tests with the [`arbitrary`] crate. It also demonstrates how to adapt fuzz tests into reusable property tests with the [`proptest`] and [`proptest-arbitrary-interop`] crates. It builds on the [timelock example].
 
 [![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
@@ -38,7 +24,7 @@ The [fuzzing example] demonstrates how to fuzz test Soroban contracts with [`car
 
 First go through the [setup] process to get your development environment configured, then clone the `v23.0.0` tag of `soroban-examples` repository:
 
-[setup]: ../../smart-contracts/getting-started/setup.mdx
+[setup]: ../../smart-contracts/getting-started/setup
 
 ```sh
 git clone -b v23.0.0 https://github.com/stellar/soroban-examples
@@ -58,11 +44,11 @@ cd fuzzing
 cargo +nightly fuzz run fuzz_target_1
 ```
 
-:::info
+<Info>
 
 If you're developing on MacOS you may need to add the `--sanitizer=thread` flag in order to fix some [known linking errors](https://github.com/stellar/rs-soroban-sdk/issues/1056).
 
-:::
+</Info>
 
 You should see output that begins like this:
 
@@ -206,11 +192,11 @@ testutils = []
 
 In most examples, a Soroban contract will only be a "cdylib", a Rust crate that is compiled to a dynamically loadable Wasm module. For fuzzing though, the fuzzing crate needs to be able to link to the contract crate as a Rust library, an "rlib".
 
-:::note
+<Note>
 
 Note that cargo has a [feature/bug that inhibits LTO][lto] of cdylibs when a crate is both a "cdylib" and "rlib". This can be worked around by building the contract with either `soroban contract build` or `cargo rustc --crate-type cdylib` instead of the typical `cargo build`.
 
-:::
+</Note>
 
 [lto]: https://github.com/stellar/soroban-docs/pull/476
 
diff --git a/docs/build/smart-contracts/example-contracts/index.mdx b/docs/build/smart-contracts/example-contracts/index.mdx
new file mode 100644
index 000000000..d6c8844a3
--- /dev/null
+++ b/docs/build/smart-contracts/example-contracts/index.mdx
@@ -0,0 +1,129 @@
+---
+title: Example Contracts
+"og:title": "Example Smart Contracts: Learn, Build, Test & Deploy on the Network"
+description: "Explore example smart contracts to learn key concepts, from basic functions to advanced use cases. Build, test, and deploy contracts on the Stellar network."
+---
+
+The Stellar team has put together a large collection of [example contracts] to demonstrate use of smart contracts on Stellar. For many of these example contracts, we've written an accompanying tutorial that will walk you through the example contract and describe a bit more about its design.
+
+The examples listed below are provided in a sequential manner. The first listed example contracts create a solid foundation of concepts that will be required during the later examples. While you are absolutely free to choose, read, and use any of the example contracts you like, please keep in mind that the order you see is intentional.
+
+<CardGroup cols={2}>
+  <Card title="Storage" icon="file-lines" href="/docs/build/smart-contracts/example-contracts/storage">
+
+    Increment a counter and store the incremented value
+
+  </Card>
+  <Card title="Events" icon="file-lines" href="/docs/build/smart-contracts/example-contracts/events">
+
+    Publish events from a smart contract.
+
+  </Card>
+  <Card title="Simple Account" icon="file-lines" href="/docs/build/smart-contracts/example-contracts/simple-account">
+
+    A minimal contract account secured by a single ed25519 public key.
+
+  </Card>
+  <Card title="Complex Account" icon="file-lines" href="/docs/build/smart-contracts/example-contracts/complex-account">
+
+    Implement a contract account with multisig and custom authorization policies.
+
+  </Card>
+  <Card title="BLS Signature" icon="file-lines" href="/docs/build/smart-contracts/example-contracts/bls-signature">
+
+    A contract account with BLS signature verification.
+
+  </Card>
+  <Card title="Delegate Auth" icon="file-lines" href="/docs/build/smart-contracts/example-contracts/delegate-auth">
+
+    A custom account contract that uses CAP-71 auth delegation to forward __check_auth to registered delegate signers.
+
+  </Card>
+  <Card title="Custom Types" icon="file-lines" href="/docs/build/smart-contracts/example-contracts/custom-types">
+
+    Define your own data structures in a smart contract.
+
+  </Card>
+  <Card title="Errors" icon="file-lines" href="/docs/build/smart-contracts/example-contracts/errors">
+
+    Define and generate errors in a smart contract.
+
+  </Card>
+  <Card title="Logging" icon="file-lines" href="/docs/build/smart-contracts/example-contracts/logging">
+
+    Debug a smart contract with logs.
+
+  </Card>
+  <Card title="Auth" icon="file-lines" href="/docs/build/smart-contracts/example-contracts/auth">
+
+    Implement authentication and authorization.
+
+  </Card>
+  <Card title="Cross Contract Calls" icon="file-lines" href="/docs/build/smart-contracts/example-contracts/cross-contract-call">
+
+    Call a smart contract from another smart contract.
+
+  </Card>
+  <Card title="Deployer" icon="file-lines" href="/docs/build/smart-contracts/example-contracts/deployer">
+
+    Deploy and initialize a smart contract using another smart contract.
+
+  </Card>
+  <Card title="Allocator" icon="file-lines" href="/docs/build/smart-contracts/example-contracts/alloc">
+
+    Use the allocator feature to emulate heap memory in a smart contract.
+
+  </Card>
+  <Card title="Atomic Swap" icon="file-lines" href="/docs/build/smart-contracts/example-contracts/atomic-swap">
+
+    Swap tokens atomically between authorized users.
+
+  </Card>
+  <Card title="Batched Atomic Swaps" icon="file-lines" href="/docs/build/smart-contracts/example-contracts/atomic-multi-swap">
+
+    Swap a token pair among groups of authorized users.
+
+  </Card>
+  <Card title="Mint Lock" icon="file-lines" href="/docs/build/smart-contracts/example-contracts/mint-lock">
+
+    Implement a contract that can delegate minting with limits.
+
+  </Card>
+  <Card title="Timelock" icon="file-lines" href="/docs/build/smart-contracts/example-contracts/timelock">
+
+    Lockup some token to be claimed by another user under set conditions.
+
+  </Card>
+  <Card title="Single Offer Sale" icon="file-lines" href="/docs/build/smart-contracts/example-contracts/single-offer-sale">
+
+    Make a standing offer to sell a token in exchange for another token.
+
+  </Card>
+  <Card title="Upgradeable Contract" icon="file-lines" href="/docs/build/smart-contracts/example-contracts/upgradeable-contract">
+
+    Upgrading Wasm Bytecode for a Deployed Contract.
+
+  </Card>
+  <Card title="Liquidity Pool" icon="file-lines" href="/docs/build/smart-contracts/example-contracts/liquidity-pool">
+
+    Write a constant-product liquidity pool contract.
+
+  </Card>
+  <Card title="Tokens" icon="file-lines" href="/docs/build/smart-contracts/example-contracts/tokens">
+
+    Write a CAP-46-6 compliant token contract.
+
+  </Card>
+  <Card title="Fuzz Testing" icon="file-lines" href="/docs/build/smart-contracts/example-contracts/fuzzing">
+
+    Increase confidence in a contract's correctness with fuzz testing.
+
+  </Card>
+  <Card title="Workspace" icon="file-lines" href="/docs/build/smart-contracts/example-contracts/workspace">
+
+    Develop multiple contracts side-by-side.
+
+  </Card>
+</CardGroup>
+
+[example contracts]: https://github.com/stellar/soroban-examples
diff --git a/docs/build/smart-contracts/example-contracts/liquidity-pool.mdx b/docs/build/smart-contracts/example-contracts/liquidity-pool.mdx
index a262894da..a466cfda3 100644
--- a/docs/build/smart-contracts/example-contracts/liquidity-pool.mdx
+++ b/docs/build/smart-contracts/example-contracts/liquidity-pool.mdx
@@ -1,37 +1,21 @@
 ---
 title: Liquidity Pool
+og:title: "Write a constant-product liquidity pool contract."
+og:description: "Write a constant-product liquidity pool smart contract."
 description: Write a constant-product liquidity pool contract.
-sidebar_position: 130
 ---
 
-<head>
-  <title>Write a constant-product liquidity pool contract.</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Write a constant-product liquidity pool contract."
-  />
-  <meta
-    property="og:description"
-    content="Write a constant-product liquidity pool smart contract."
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
 The [liquidity pool example] demonstrates how to write a constant product liquidity pool contract. A liquidity pool is an automated way to add liquidity for a set of tokens that will facilitate asset conversion between them. Users can deposit some amount of each token into the pool, receiving a proportional number of "token shares." The user will then receive a portion of the accrued conversion fees when they ultimately "trade in" their token shares to receive their original tokens back.
 
 Soroban liquidity pools are exclusive to Soroban and cannot interact with built-in Stellar AMM liquidity pools.
 
-:::caution
+<Warning>
 
 Implementing a liquidity pool contract should be done cautiously. User funds are involved, so great care should be taken to ensure safety and transparency. The example here should _not_ be considered a ready-to-go contract. Please use it as a reference only.
 
-The Stellar network already has liquidity pool functionality built right in to the core protocol. [Learn more here](../../../learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx).
+The Stellar network already has liquidity pool functionality built right in to the core protocol. [Learn more here](../../../learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools).
 
-:::
+</Warning>
 
 [![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
 
@@ -68,7 +52,7 @@ test test::swap_reserve_one_nonzero_other_zero - should panic ... ok
 test test::test ... ok
 ```
 
-[setup]: ../getting-started/setup.mdx
+[setup]: ../getting-started/setup
 
 ## Code
 
@@ -413,7 +397,7 @@ Ref: https://github.com/stellar/soroban-examples/tree/v23.0.0/liquidity_pool
 
 ## How it Works
 
-Every asset created on Stellar starts with zero liquidity. The same is true of tokens created on Soroban (unless a Stellar asset with existing liquidity token has its [Stellar Asset Contract (SAC)](../../../tokens/stellar-asset-contract.mdx) deployed for use in Soroban). In simple terms, "liquidity" means how much of an asset in a market is available to be bough or sold. In the "old days," you could generate liquidity in a market by creating buy/sell orders on an order book.
+Every asset created on Stellar starts with zero liquidity. The same is true of tokens created on Soroban (unless a Stellar asset with existing liquidity token has its [Stellar Asset Contract (SAC)](../../../tokens/stellar-asset-contract) deployed for use in Soroban). In simple terms, "liquidity" means how much of an asset in a market is available to be bough or sold. In the "old days," you could generate liquidity in a market by creating buy/sell orders on an order book.
 
 Liquidity pools automate this process by substituting the orders with math. Depositors into the liquidity pool earn fees from `swap` transactions. No orders required!
 
@@ -444,9 +428,9 @@ pub fn __constructor(e: Env, token_a: Address, token_b: Address) {
 
 [creating its own `pool` token]: #minting-and-burning-lp-shares
 [interacting with contracts for `token_a` and `token_b`]: #token-transfers-tofrom-the-lp-contract
-[lexicographical order]: ../../../learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx#liquidity-pool-participation
+[lexicographical order]: ../../../learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools#liquidity-pool-participation
 
-### A "Constant Product" Liquidity Pool
+### A "Constant Product" Liquidity Pool {#a-constant-product-liquidity-pool}
 
 The _type_ of liquidity pool this example contract implements is called a "constant product" liquidity pool. While this isn't the only type of liquidity pool out there, it is the most common variety. These liquidity pools are designed to keep the _total_ value of each asset in _relative_ equilibrium. The "product" in the constant product (also called an "invariant") will change every time the liquidity pool is interacted with (deposit, withdraw, or token swaps). However, the invariant **must** only increase with every interaction.
 
@@ -477,7 +461,7 @@ This liquidity pool contract will operate with a total of three different Soroba
 - **Pool Shares:** This example uses a very simple share token given to asset depositors in exchange for their deposit. These tokens are "traded in" by the user when they withdraw some amount of their original deposit (plus any earned swap fees). In this simplified system, shares are just added/subtracted whenever a user deposits or withdraws the underlying assets. No distinct _token contract_ will be used for these shares.
 - **`token_a`** and **`token_b`**: Will be the two "reserve tokens" that users will deposit into the pool. These could be "wrapped" tokens from pre-existing Stellar assets, or they could be Soroban-native tokens. This contract doesn't really care, as long as the functions it needs from the common [Token Interface] are available in the token contract.
 
-[token interface]: ../../../tokens/token-interface.mdx
+[token interface]: ../../../tokens/token-interface
 
 #### Minting and Burning LP Shares
 
@@ -522,7 +506,7 @@ fn deposit(e: Env, to: Address, desired_a: i128, min_a: i128, desired_b: i128, m
 }
 ```
 
-#### Token Transfers to/from the LP Contract
+#### Token Transfers to/from the LP Contract {#token-transfers-tofrom-the-lp-contract}
 
 As we've already discussed, the liquidity pool contract will make use of the [Token Interface] available in the token contracts that were supplied as `token_a` and `token_b` arguments at the time of initialization. Throughout the rest of the contract, the liquidity pool will make use of that interface to make transfers of those tokens to/from itself.
 
@@ -846,8 +830,8 @@ If you have [`stellar-cli`] installed, you can deploy the contract and invoke it
 
 ### Deploy
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract deploy \
@@ -857,8 +841,8 @@ stellar contract deploy \
     --network testnet
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract deploy `
@@ -868,13 +852,13 @@ stellar contract deploy `
     --network testnet
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 ### Invoke
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract invoke \
@@ -890,8 +874,8 @@ stellar contract invoke \
     --min_b 196
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract invoke `
@@ -907,7 +891,7 @@ stellar contract invoke `
     --min_b 196
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
-[`stellar-cli`]: ../../../tools/cli/stellar-cli.mdx
+[`stellar-cli`]: ../../../tools/cli/stellar-cli
diff --git a/docs/build/smart-contracts/example-contracts/logging.mdx b/docs/build/smart-contracts/example-contracts/logging.mdx
index 101c779fe..34e472d4e 100644
--- a/docs/build/smart-contracts/example-contracts/logging.mdx
+++ b/docs/build/smart-contracts/example-contracts/logging.mdx
@@ -1,23 +1,10 @@
 ---
 title: Logging
+og:title: "Debug a smart contract with logs."
+og:description: "Employ logging to debug your smart contracts."
 description: Debug a smart contract with logs.
-sidebar_position: 40
 ---
 
-<head>
-  <title>Debug a smart contract with logs.</title>
-  <meta charSet="utf-8" />
-  <meta property="og:title" content="Debug a smart contract with logs." />
-  <meta
-    property="og:description"
-    content="Employ logging to debug your smart contracts."
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
 The [logging example] demonstrates how to log for the purpose of debugging.
 
 [![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
@@ -30,26 +17,25 @@ Logs in contracts are only visible in tests, or when executing contracts using [
 [open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
 [logging example]: https://github.com/stellar/soroban-examples/tree/v23.0.0/hello_world
 
-:::tip
+<Tip>
 
 Logs are not a substitute for step-through debugging. Rust tests for Soroban can be step-through debugged in your Rust-enabled IDE. See [testing] for more details.
 
-:::
-
-:::caution
+</Tip>
+<Warning>
 
 Logs are not accessible by dapps and other applications. See the [events example] for how to produce structured events.
 
-:::
+</Warning>
 
-[testing]: ../getting-started/hello-world.mdx#run-the-tests
-[events example]: ./events.mdx
+[testing]: ../getting-started/hello-world#run-the-tests
+[events example]: ./events
 
 ## Run the Example
 
 First go through the [Setup] process to get your development environment configured, then clone the `v23.0.0` tag of `soroban-examples` repository:
 
-[setup]: ../getting-started/setup.mdx
+[setup]: ../getting-started/setup
 
 ```sh
 git clone -b v23.0.0 https://github.com/stellar/soroban-examples
@@ -109,7 +95,7 @@ Logs are only recorded in Soroban environments that have logging enabled. The on
 
 Open the files above to follow along.
 
-### `Cargo.toml` Profile
+### `Cargo.toml` Profile {#cargotoml-profile}
 
 Logs are only outputted if the contract is built with the `debug-assertions` compiler option enabled.
 
@@ -141,11 +127,11 @@ The above log will render as follows if `value` is a `Symbol` containing `"Dev"`
 Hello Symbol(Dev)
 ```
 
-:::caution
+<Warning>
 
 The values outputted are currently relatively limited. While primitive values like `u32`, `u64`, `bool`, and `Symbol`s will render clearly in the log output, `Bytes`, `Vec`, `Map`, and custom types will render only their handle number. Logging capabilities are in early development.
 
-:::
+</Warning>
 
 ## Tests
 
@@ -258,8 +244,8 @@ If you have [`stellar-cli`] installed, you can deploy the contract and invoke it
 
 ### Deploy
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract deploy \
@@ -269,8 +255,8 @@ stellar contract deploy \
     --network testnet
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract deploy `
@@ -280,13 +266,13 @@ stellar contract deploy `
     --network testnet
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 ### Invoke
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar -v contract invoke \
@@ -298,8 +284,8 @@ stellar -v contract invoke \
     --value friend
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar -v contract invoke `
@@ -311,7 +297,7 @@ stellar -v contract invoke `
     --value friend
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 The output should include the following line.
@@ -321,4 +307,4 @@ The output should include the following line.
 ```
 
 [`log!`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/macro.log.html
-[`stellar-cli`]: ../getting-started/setup.mdx#install-the-stellar-cli
+[`stellar-cli`]: ../getting-started/setup#install-the-stellar-cli
diff --git a/docs/build/smart-contracts/example-contracts/mint-lock.mdx b/docs/build/smart-contracts/example-contracts/mint-lock.mdx
index 0e74463ae..e1001abf7 100644
--- a/docs/build/smart-contracts/example-contracts/mint-lock.mdx
+++ b/docs/build/smart-contracts/example-contracts/mint-lock.mdx
@@ -1,22 +1,10 @@
 ---
 title: Mint Lock
+og:title: "Implement a contract that can delegate minting with limits."
+og:description: "Implement a contract that can delegate minting with limits."
 description: Implement a contract that can delegate minting with limits.
-sidebar_position: 110
 ---
 
-<head>
-  <title>{`Implement contract that can delegate minting with limits.`}</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Implement a contract that can delegate minting with limits."
-  />
-  <meta
-    property="og:description"
-    content="Implement a contract that can delegate minting with limits."
-  />
-</head>
-
 The [mint-lock example] demonstrates how to write a contract that can delegate minting tokens from another address with limits on how much those addresses can mint across a specified time period.
 
 The admin of the token contracts used must be the mint-lock contract.
diff --git a/docs/build/smart-contracts/example-contracts/simple-account.mdx b/docs/build/smart-contracts/example-contracts/simple-account.mdx
index 4e410b459..777a69767 100644
--- a/docs/build/smart-contracts/example-contracts/simple-account.mdx
+++ b/docs/build/smart-contracts/example-contracts/simple-account.mdx
@@ -1,36 +1,22 @@
 ---
 title: Simple Account
-sidebar_label: Simple Account
+og:title: "Minimal contract account secured by a single ed25519 public key."
+og:description: "Walk through the simple Soroban account example to see how __check_auth can be implemented with one key."
 description: A minimal contract account secured by a single ed25519 public key.
-sidebar_position: 15
 ---
 
-<head>
-  <title>Simple Account</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Minimal contract account secured by a single ed25519 public key."
-  />
-  <meta
-    property="og:description"
-    content="Walk through the simple Soroban account example to see how __check_auth can be implemented with one key."
-  />
-</head>
+This example implements the smallest possible [contract account](../../../learn/glossary#contract-account): each `require_auth` call delegates to one ed25519 public key. It shows how to store that key, run `__check_auth`, and surface authorization failures. Use this as the baseline before moving to the [Complex Account example](./complex-account) for multisig or policy enforcement.
 
-This example implements the smallest possible [contract account](../../../learn/glossary.mdx#contract-account): each `require_auth` call delegates to one ed25519 public key. It shows how to store that key, run `__check_auth`, and surface authorization failures. Use this as the baseline before moving to the [Complex Account example](./complex-account.mdx) for multisig or policy enforcement.
-
-:::danger
+<Danger>
 
 Implementing a contract account requires a very good understanding of authentication and authorization and requires rigorous testing and review. The example here is _not_ a full-fledged account contract - use it as an API reference only.
 
-:::
-
-:::caution
+</Danger>
+<Warning>
 
 While contract accounts are supported by the Stellar protocol and Soroban SDK, the full client support (such as transaction simulation) is still under development.
 
-:::
+</Warning>
 
 [![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
 
@@ -64,7 +50,7 @@ running 1 test
 test test::test_account ... ok
 ```
 
-[setup]: ../getting-started/setup.mdx
+[setup]: ../getting-started/setup
 
 ## How it Works
 
@@ -170,7 +156,7 @@ The compiled file appears at `target/wasm32v1-none/release/simple_account.wasm`
 ## Further Reading
 
 - [Complex account example] – adds multisig support and spend limits.
-- [BLS signature contract](./bls-signature.mdx) – demonstrates custom signature schemes inside `__check_auth`.
+- [BLS signature contract](./bls-signature) – demonstrates custom signature schemes inside `__check_auth`.
 
-[Complex account example]: ./complex-account.mdx
+[Complex account example]: ./complex-account
 [simple account example]: https://github.com/stellar/soroban-examples/tree/main/simple_account
diff --git a/docs/build/smart-contracts/example-contracts/single-offer-sale.mdx b/docs/build/smart-contracts/example-contracts/single-offer-sale.mdx
index 2418c12ce..d440787e1 100644
--- a/docs/build/smart-contracts/example-contracts/single-offer-sale.mdx
+++ b/docs/build/smart-contracts/example-contracts/single-offer-sale.mdx
@@ -1,24 +1,10 @@
 ---
 title: Single Offer Sale
+og:title: "Make a standing offer to sell a token in exchange for another token."
+og:description: "Write a smart contract that allows a seller to set up an offer to sell one token for another token to multiple buyers."
 description: Make a standing offer to sell a token in exchange for another token.
-sidebar_position: 120
 ---
 
-<head>
-  <title>
-    {`Make a standing offer to sell a token in exchange for another token.`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Make a standing offer to sell a token in exchange for another token."
-  />
-  <meta
-    property="og:description"
-    content="Write a smart contract that allows a seller to set up an offer to sell one token for another token to multiple buyers."
-  />
-</head>
-
 The [single offer sale example] demonstrates how to write a contract that allows a seller to set up an offer to sell token A for token B to multiple buyers. The comments in the [source code] explain how the contract should be used.
 
 [![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
diff --git a/docs/build/smart-contracts/example-contracts/storage.mdx b/docs/build/smart-contracts/example-contracts/storage.mdx
index 588aa3fd0..5f216b7d7 100644
--- a/docs/build/smart-contracts/example-contracts/storage.mdx
+++ b/docs/build/smart-contracts/example-contracts/storage.mdx
@@ -1,26 +1,10 @@
 ---
 title: Storage
+og:title: "Increment a counter and store the incremented value."
+og:description: "Use storage to retain the value of a counter in an incrementer smart contract"
 description: Increment a counter and store the incremented value
-sidebar_position: 9
 ---
 
-<head>
-  <title>Increment a counter and store the incremented value.</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Increment a counter and store the incremented value."
-  />
-  <meta
-    property="og:description"
-    content="Use storage to retain the value of a counter in an incrementer smart contract"
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
 The [increment example] demonstrates how to call a contract from another contract.
 
 [![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
@@ -35,7 +19,7 @@ The [increment example] demonstrates how to call a contract from another contrac
 
 First go through the [Setup] process to get your development environment configured, then clone the `v23.0.0` tag of `soroban-examples` repository:
 
-[setup]: ../getting-started/setup.mdx
+[setup]: ../getting-started/setup
 
 ```sh
 git clone -b v23.0.0 https://github.com/stellar/soroban-examples
@@ -118,7 +102,7 @@ If no value is currently stored, the value given to `unwrap_or(...)` is returned
 
 Values stored as contract data and retrieved are transmitted from [the environment] and expanded into the type specified. In this case a `u32`. If the value can be expanded, the type returned will be a `u32`. Otherwise, if a developer cast it to be some other type, a panic would occur at the unwrap.
 
-[the environment]: ../../../learn/fundamentals/contract-development/environment-concepts.mdx
+[the environment]: ../../../learn/fundamentals/contract-development/environment-concepts
 
 ```rust
 env.storage()
@@ -134,9 +118,9 @@ The `set()` function stores the new count value against the key, replacing the e
 env.storage().instance().extend_ttl(50, 100);
 ```
 
-All contract data has a Time To Live (TTL), measured in ledgers, that must be periodically extended. If an entry's TTL is not periodically extended, the entry will eventually become "archived." You can learn more about this in the [State Archival](../../../learn/fundamentals/contract-development/storage/state-archival.mdx) document.
+All contract data has a Time To Live (TTL), measured in ledgers, that must be periodically extended. If an entry's TTL is not periodically extended, the entry will eventually become "archived." You can learn more about this in the [State Archival](../../../learn/fundamentals/contract-development/storage/state-archival) document.
 
-For now, it's worth knowing that there are three kinds of storage: `Persistent`, `Temporary`, and `Instance`. This contract only uses `Instance` storage: `env.storage().instance()`. Every time the counter is incremented, this storage's TTL gets extended by 100 [ledgers](../../../learn/fundamentals/stellar-data-structures/ledgers.mdx), or about 500 seconds.
+For now, it's worth knowing that there are three kinds of storage: `Persistent`, `Temporary`, and `Instance`. This contract only uses `Instance` storage: `env.storage().instance()`. Every time the counter is incremented, this storage's TTL gets extended by 100 [ledgers](../../../learn/fundamentals/stellar-data-structures/ledgers), or about 500 seconds.
 
 ## Tests
 
@@ -201,8 +185,8 @@ If you have [`stellar-cli`] installed, you can deploy the contract, and invoke t
 
 ### Deploy
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract deploy \
@@ -212,8 +196,8 @@ stellar contract deploy \
     --network testnet
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract deploy `
@@ -223,13 +207,13 @@ stellar contract deploy `
     --network testnet
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 ### Invoke
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract invoke \
@@ -240,8 +224,8 @@ stellar contract invoke \
     increment
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract invoke `
@@ -252,7 +236,7 @@ stellar contract invoke `
     increment
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 ### Result
@@ -265,4 +249,4 @@ The following output should occur the first time the code above is used.
 
 The value will be incremented every time the contract function is invoked.
 
-[`stellar-cli`]: ../getting-started/setup.mdx#install-the-stellar-cli
+[`stellar-cli`]: ../getting-started/setup#install-the-stellar-cli
diff --git a/docs/build/smart-contracts/example-contracts/timelock.mdx b/docs/build/smart-contracts/example-contracts/timelock.mdx
index cef4bd2e0..b9f3f4190 100644
--- a/docs/build/smart-contracts/example-contracts/timelock.mdx
+++ b/docs/build/smart-contracts/example-contracts/timelock.mdx
@@ -1,24 +1,10 @@
 ---
 title: Timelock
+og:title: "Write a timelock implementing a claimable balance."
+og:description: "Write a timelock that implements a simplified claimable balance feature that accepts a deposit of an amount of a token and allows other users to claim it."
 description: Lockup some token to be claimed by another user under set conditions.
-sidebar_position: 110
 ---
 
-<head>
-  <title>
-    {`Lockup some token to be claimed by another user under set conditions`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Write a timelock implementing a claimable balance."
-  />
-  <meta
-    property="og:description"
-    content="Write a timelock that implements a simplified claimable balance feature that accepts a deposit of an amount of a token and allows other users to claim it."
-  />
-</head>
-
 The [timelock example] demonstrates how to write a timelock and implements a greatly simplified claimable balance similar to the [claimable balance] feature available on Stellar.
 
 [![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
@@ -30,4 +16,4 @@ The contract accepts deposits of an amount of a token, and allows other users to
 [open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
 [open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
 [timelock example]: https://github.com/stellar/soroban-examples/tree/v23.0.0/timelock
-[claimable balance]: ../../guides/transactions/claimable-balances.mdx
+[claimable balance]: ../../guides/transactions/claimable-balances
diff --git a/docs/build/smart-contracts/example-contracts/tokens.mdx b/docs/build/smart-contracts/example-contracts/tokens.mdx
index b4de7b530..3507d3d6a 100644
--- a/docs/build/smart-contracts/example-contracts/tokens.mdx
+++ b/docs/build/smart-contracts/example-contracts/tokens.mdx
@@ -1,33 +1,17 @@
 ---
 title: Tokens
+og:title: "Write a CAP-46-6 compliant token contract"
+og:description: "Use the Token Interface to construct a smart contract token that has a uniform and predictable interface for payments, balance transfers, balance inquiries, and more."
 description: Write a CAP-46-6 compliant token contract.
-sidebar_position: 140
 ---
 
-<head>
-  <title>Write a CAP-46-6 compliant token contract</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Write a CAP-46-6 compliant token contract"
-  />
-  <meta
-    property="og:description"
-    content="Use the Token Interface to construct a smart contract token that has a uniform and predictable interface for payments, balance transfers, balance inquiries, and more."
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
 The [token example] demonstrates how to write a token contract that implements the [Token Interface].
 
-:::tip
+<Tip>
 
-This example shows how to build a token from scratch using only the `soroban-sdk`. For many use cases, issuing a Stellar asset and using its built-in [Stellar Asset Contract (SAC)](../../../tokens/stellar-asset-contract.mdx) is all you need. If you want a custom token contract, the fastest path is the audited [OpenZeppelin Stellar Contracts](https://github.com/OpenZeppelin/stellar-contracts) library, which has easy-to-follow examples in its docs for [fungible tokens](https://docs.openzeppelin.com/stellar-contracts/tokens/fungible/fungible) and [non-fungible tokens (NFTs)](https://docs.openzeppelin.com/stellar-contracts/tokens/non-fungible/non-fungible).
+This example shows how to build a token from scratch using only the `soroban-sdk`. For many use cases, issuing a Stellar asset and using its built-in [Stellar Asset Contract (SAC)](../../../tokens/stellar-asset-contract) is all you need. If you want a custom token contract, the fastest path is the audited [OpenZeppelin Stellar Contracts](https://github.com/OpenZeppelin/stellar-contracts) library, which has easy-to-follow examples in its docs for [fungible tokens](https://docs.openzeppelin.com/stellar-contracts/tokens/fungible/fungible) and [non-fungible tokens (NFTs)](https://docs.openzeppelin.com/stellar-contracts/tokens/non-fungible/non-fungible).
 
-:::
+</Tip>
 
 [![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
 
@@ -36,13 +20,15 @@ This example shows how to build a token from scratch using only the `soroban-sdk
 [open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
 [open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
 [token example]: https://github.com/stellar/soroban-examples/tree/main/token
-[token interface]: ../../../tokens/token-interface.mdx
+[token interface]: ../../../tokens/token-interface
+
+<Info>
 
-:::info[Whisk Changes]
+**Whisk Changes**
 
 With the release of Whisk, Protocol 23, the [token interface] has seen some changes to incorporate the `MuxedAddress` type into the `transfer` function. Please see the [Rust SDK documentation](https://docs.rs/soroban-token-sdk/latest/soroban_token_sdk/_migrating/v23_token_transfer/index.html) for more details.
 
-:::
+</Info>
 
 ## Run the Example
 
@@ -73,18 +59,17 @@ test test::test_burn ... ok
 test test::test ... ok
 ```
 
-[setup]: ../getting-started/setup.mdx
+[setup]: ../getting-started/setup
 
 ## Code
 
-:::note
+<Note>
 
 The source code for this [token example] is broken into several smaller modules. This is a common design pattern for more complex smart contracts.
 
-:::
-
+</Note>
 <Tabs>
-<TabItem value="lib" default>
+<Tab title="lib">
 
 ```rust title="token/src/lib.rs"
 #![no_std]
@@ -100,8 +85,8 @@ mod test;
 pub use crate::contract::TokenClient;
 ```
 
-</TabItem>
-<TabItem value="admin">
+</Tab>
+<Tab title="admin">
 
 ```rust title="token/src/admin.rs"
 use soroban_sdk::{Address, Env};
@@ -119,8 +104,8 @@ pub fn write_administrator(e: &Env, id: &Address) {
 }
 ```
 
-</TabItem>
-<TabItem value="allowance">
+</Tab>
+<Tab title="allowance">
 
 ```rust title="token/src/allowance.rs"
 use crate::storage_types::{AllowanceDataKey, AllowanceValue, DataKey};
@@ -190,8 +175,8 @@ pub fn spend_allowance(e: &Env, from: Address, spender: Address, amount: i128) {
 }
 ```
 
-</TabItem>
-<TabItem value="balance">
+</Tab>
+<Tab title="balance">
 
 ```rust title="token/src/balance.rs"
 use crate::storage_types::{DataKey, BALANCE_BUMP_AMOUNT, BALANCE_LIFETIME_THRESHOLD};
@@ -231,8 +216,8 @@ pub fn spend_balance(e: &Env, addr: Address, amount: i128) {
 }
 ```
 
-</TabItem>
-<TabItem value="contract">
+</Tab>
+<Tab title="contract">
 
 ```rust title="token/src/contract.rs"
 //! This contract demonstrates a sample implementation of the Soroban token
@@ -438,8 +423,8 @@ impl TokenInterface for Token {
 }
 ```
 
-</TabItem>
-<TabItem value="metadata">
+</Tab>
+<Tab title="metadata">
 
 ```rust title="token/src/metadata.rs"
 use soroban_sdk::{Env, String};
@@ -466,8 +451,8 @@ pub fn write_metadata(e: &Env, metadata: TokenMetadata) {
 }
 ```
 
-</TabItem>
-<TabItem value="storage_types">
+</Tab>
+<Tab title="storage_types">
 
 ```rust title="token/src/storage_types.rs"
 use soroban_sdk::{contracttype, Address};
@@ -502,7 +487,7 @@ pub enum DataKey {
 }
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 Ref: https://github.com/stellar/soroban-examples/tree/main/token
@@ -515,7 +500,7 @@ Creating a Soroban token compatible contract from an existing Stellar asset is v
 
 This example contract, however, demonstrates how a smart contract token might be constructed that doesn't take advantage of the Stellar Asset Contract, but does still satisfy the commonly used Token Interface to maximize interoperability.
 
-[stellar asset contract]: ../../../tokens/stellar-asset-contract.mdx
+[stellar asset contract]: ../../../tokens/stellar-asset-contract
 
 ### Separation of Functionality
 
@@ -531,7 +516,7 @@ events::MintWithAmountOnly { to, amount }.publish(&e);
 
 Admittedly, this is a simple example, but constructing the contract this way makes it very clear to the developer what is happening and where. This function is then used by the `contract.rs` module whenever the `mint` function is invoked:
 
-```rust
+```rust highlight={14}
 // earlier in `contract.rs`
 use soroban_token_sdk::events;
 
@@ -545,7 +530,6 @@ pub fn mint(e: Env, to: Address, amount: i128) {
         .extend_ttl(INSTANCE_LIFETIME_THRESHOLD, INSTANCE_BUMP_AMOUNT);
 
     receive_balance(&e, to.clone(), amount);
-    // highlight-next-line
     events::MintWithAmountOnly { to, amount }.publish(&e);
 }
 ```
@@ -558,7 +542,7 @@ This example contract follows the standardized [Token Interface], implementing a
 
 By way of example, perhaps you have an NFT project, and the artist wants to have a small royalty paid every time their token transfers hands:
 
-```rust
+```rust highlight={9-17}
 // This is mainly the `transfer` function from `token/src/contract.rs`
 fn transfer(e: Env, from: Address, to_muxed: MuxedAddress, amount: i128) {
     from.require_auth();
@@ -567,7 +551,6 @@ fn transfer(e: Env, from: Address, to_muxed: MuxedAddress, amount: i128) {
     spend_balance(&e, from.clone(), amount);
     let to: Address = to_muxed.address();
 
-    // highlight-start
     // We calculate some new amounts for payment and royalty
     let payment = (amount * 997) / 1000;
     let royalty = amount - payment
@@ -577,7 +560,6 @@ fn transfer(e: Env, from: Address, to_muxed: MuxedAddress, amount: i128) {
         to: artist.clone(),
         amount: royalty,
     }.publish(&e);
-    // highlight-end
     receive_balance(&e, to.clone(), payment);
     events::Transfer {
         from,
@@ -591,11 +573,11 @@ fn transfer(e: Env, from: Address, to_muxed: MuxedAddress, amount: i128) {
 
 The `transfer` interface is still in use, and is still the same as other tokens, but we've customized the behavior to address a specific need. Another use-case might be a tightly controlled token that requires authentication from an admin before any `transfer`, `allowance`, etc. function could be invoked.
 
-:::tip
+<Tip>
 
 Of course, you will want your token to behave in an _intuitive_ and _transparent_ manner. If a user is invoking a `transfer`, they will expect tokens to move. If an asset issuer needs to invoke a `clawback` they will likely _require_ the right kind of behavior to take place.
 
-:::
+</Tip>
 
 ## Tests
 
@@ -941,8 +923,8 @@ If you have [`stellar-cli`] installed, you can deploy the contract and invoke it
 
 ### Deploy
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract deploy \
@@ -952,8 +934,8 @@ stellar contract deploy \
     --network testnet
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract deploy `
@@ -963,13 +945,13 @@ stellar contract deploy `
     --network testnet
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 ### Invoke
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract invoke \
@@ -981,8 +963,8 @@ stellar contract invoke \
     --id GBZV3NONYSUDVTEHATQO4BCJVFXJO3XQU5K32X3XREVZKSMMOZFO4ZXR
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract invoke `
@@ -994,7 +976,7 @@ stellar contract invoke `
     --id GBZV3NONYSUDVTEHATQO4BCJVFXJO3XQU5K32X3XREVZKSMMOZFO4ZXR
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
-[`stellar-cli`]: ../../../tools/cli/stellar-cli.mdx
+[`stellar-cli`]: ../../../tools/cli/stellar-cli
diff --git a/docs/build/smart-contracts/example-contracts/upgradeable-contract.mdx b/docs/build/smart-contracts/example-contracts/upgradeable-contract.mdx
index a2eaf732a..62f4254da 100644
--- a/docs/build/smart-contracts/example-contracts/upgradeable-contract.mdx
+++ b/docs/build/smart-contracts/example-contracts/upgradeable-contract.mdx
@@ -1,20 +1,8 @@
 ---
 title: Upgradeable Contract
+og:title: "Upgrading Wasm Bytecode for a Deployed Contract."
+og:description: "Upgrading Wasm Bytecode for a Deployed Contract."
 description: Upgrading Wasm Bytecode for a Deployed Contract.
-sidebar_position: 120
 ---
 
-<head>
-  <title>Upgrading Wasm Bytecode for a Deployed Contract</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Upgrading Wasm Bytecode for a Deployed Contract."
-  />
-  <meta
-    property="og:description"
-    content="Upgrading Wasm Bytecode for a Deployed Contract."
-  />
-</head>
-
-The [upgrading contracts](../../guides/conventions/upgrading-contracts.mdx) page demonstrates how to upgrade the Wasm bytecode using example contracts.
+The [upgrading contracts](../../guides/conventions/upgrading-contracts) page demonstrates how to upgrade the Wasm bytecode using example contracts.
diff --git a/docs/build/smart-contracts/example-contracts/workspace.mdx b/docs/build/smart-contracts/example-contracts/workspace.mdx
index be7c97910..d25db7dec 100644
--- a/docs/build/smart-contracts/example-contracts/workspace.mdx
+++ b/docs/build/smart-contracts/example-contracts/workspace.mdx
@@ -1,13 +1,8 @@
 ---
 title: Workspace
 description: Develop multiple contracts side-by-side.
-sidebar_position: 170
 ---
 
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
 The [workspace example] demonstrates how multiple smart contracts can be developed, tested, and built side-by-side in the same Rust workspace.
 
 [![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
@@ -22,7 +17,7 @@ The [workspace example] demonstrates how multiple smart contracts can be develop
 
 First go through the [Setup] process to get your development environment configured, then clone the `v23.0.0` tag of `soroban-examples` repository:
 
-[Setup]: ../getting-started/setup.mdx
+[Setup]: ../getting-started/setup
 
 ```sh
 git clone https://github.com/stellar/soroban-examples
@@ -47,7 +42,7 @@ test test::test ... ok
 ## Code
 
 <Tabs>
-<TabItem value="Contract A Interface" default>
+<Tab title="Contract A Interface">
 
 ```rust title="workspace/contract_a_interface/src/lib.rs"
 #![no_std]
@@ -60,8 +55,8 @@ pub trait ContractAInterface {
 }
 ```
 
-</TabItem>
-<TabItem value="Contract A">
+</Tab>
+<Tab title="Contract A">
 
 ```rust title="workspace/contract_a/src/lib.rs"
 #![no_std]
@@ -80,8 +75,8 @@ impl ContractAInterface for ContractA {
 }
 ```
 
-</TabItem>
-<TabItem value="Contract B">
+</Tab>
+<Tab title="Contract B">
 
 ```rust title="workspace/contract_b/src/lib.rs"
 #![no_std]
@@ -103,8 +98,8 @@ impl ContractB {
 mod test;
 ```
 
-</TabItem>
-<TabItem value="Contract B Test">
+</Tab>
+<Tab title="Contract B Test">
 
 ```rust title="workspace/src/contract_b/src/test.rs"
 #![cfg(test)]
@@ -134,7 +129,7 @@ fn test() {
 }
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 Ref: https://github.com/stellar/soroban-examples/tree/v23.0.0/workspace
@@ -163,11 +158,11 @@ The `contract_a` crate contains the implementation for Contract A, defining for
 
 The implementation takes the value of `x`, along with the value of `y`, and performs a `checked_add`, returning the sum of both numbers (while avoiding an overflow error).
 
-:::info
+<Info>
 
 The `add` function doesn't require an `Env` argument. That's totally fine! `Env` has many useful features that are available to your smart contracts, if you need them. But, you're not at all required to use it, if you don't.
 
-:::
+</Info>
 
 All that is required to make use of the previously defined `ContractAInterface` is to `use` the interface, define a `ContractA` struct, and `impl` the interface for that struct.
 
@@ -179,11 +174,11 @@ Now that we've created a trait in `contract_a_interface`, and implemented it in
 
 We're creating and implementing an entirely new contract, `ContractB`. We're skipping the trait, and getting right to the contract itself.
 
-:::info
+<Info>
 
 Defining the contract interface with a `trait` separately is optional. It's a great way to share the interface of a contract, and a contract client, with multiple contracts in a multi-contract workspace.
 
-:::
+</Info>
 
 `ContractB` has one function, `add_with`, that requires three arguments:
 
@@ -220,8 +215,8 @@ The [`stellar-cli`] knows the `contract_a_interface` is not intended to be compi
 
 If you have [`stellar-cli`] installed, you can invoke contract the functions. Both contracts must be deployed.
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract deploy \
@@ -233,8 +228,8 @@ stellar contract deploy \
     --wasm target/wasm32v1-none/release/soroban_workspace_contract_b.wasm
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract deploy `
@@ -246,13 +241,13 @@ stellar contract deploy `
     --wasm target/wasm32v1-none/release/soroban_workspace_contract_b.wasm
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 Invoke `ContractB`'s `add_with` function, passing in `ContractA`'s address for `contract`, and integer values for `x` and `y` (e.g. as `5` and `7`).
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract invoke \
@@ -264,8 +259,8 @@ stellar contract invoke \
     --y 7
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract invoke `
@@ -277,7 +272,7 @@ stellar contract invoke `
     --y 7
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
-[`stellar-cli`]: ../getting-started/setup.mdx#install-the-stellar-cli
+[`stellar-cli`]: ../getting-started/setup#install-the-stellar-cli
diff --git a/docs/build/smart-contracts/getting-started/README.mdx b/docs/build/smart-contracts/getting-started/README.mdx
deleted file mode 100644
index b8967e41c..000000000
--- a/docs/build/smart-contracts/getting-started/README.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: "Get Started with Smart Contracts: Setup, Write in Rust & Deploy"
-sidebar_label: Getting Started
-description: "Get started with smart contracts by setting up your environment, writing code in Rust, and deploying contracts using CLI tools on the Stellar network."
-sidebar_position: 20
----
-
-# Getting Started
-
-:::tip
-
-Start with [Scaffold Stellar](https://scaffoldstellar.org/docs/quick-start) for the fastest path to a working dApp on Stellar. Scaffold Stellar is a toolkit that bundles a CLI, contract templates, a smart contract registry, and a modern frontend for building full-stack dApps.
-
-_Use this getting started guide for a lower-level tour of Stellar smart contract development from the main Stellar CLI._
-
-:::
-
-import DocCardList from "@theme/DocCardList";
-
-Dive into smart contract development with this Getting Started tutorial.
-
-<DocCardList />
diff --git a/docs/build/smart-contracts/getting-started/_category_.json b/docs/build/smart-contracts/getting-started/_category_.json
deleted file mode 100644
index 0d4475828..000000000
--- a/docs/build/smart-contracts/getting-started/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": false
-}
diff --git a/docs/build/smart-contracts/getting-started/deploy-increment-contract.mdx b/docs/build/smart-contracts/getting-started/deploy-increment-contract.mdx
index be983fae9..a98f86b92 100644
--- a/docs/build/smart-contracts/getting-started/deploy-increment-contract.mdx
+++ b/docs/build/smart-contracts/getting-started/deploy-increment-contract.mdx
@@ -1,16 +1,9 @@
 ---
-sidebar_position: 40
-title: "Deploy the Increment Smart Contract on Testnet Using the CLI: A Guide"
-sidebar_label: 4. Deploy the Increment Contract
+title: 4. Deploy the Increment Contract
+"og:title": "Deploy the Increment Smart Contract on Testnet Using the CLI: A Guide"
 description: "Follow this step-by-step guide in the final section of Getting Started to learn how to deploy the increment smart contract on Testnet using the Stellar CLI."
 ---
 
-# 4. Deploy the Increment Contract
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
 ## Two-step deployment
 
 It's worth knowing that `deploy` is actually a two-step process.
@@ -21,15 +14,14 @@ It's worth knowing that `deploy` is actually a two-step process.
 
 You can run these two steps separately. Let's try it with the Increment contract:
 
-:::info
+<Info>
 
 If the contract has not been build yet, run the build command `stellar contract build` from the contract's root directory.
 
-:::
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
+</Info>
+<Tabs>
 
-<TabItem value="unix" label="macOS/Linux">
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract upload \
@@ -38,9 +30,9 @@ stellar contract upload \
   --wasm target/wasm32v1-none/release/increment.wasm
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="windows" label="Windows (PowerShell)">
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract upload `
@@ -49,15 +41,15 @@ stellar contract upload `
   --wasm target/wasm32v1-none/release/increment.wasm
 ```
 
-</TabItem>
+</Tab>
 
 </Tabs>
 
 This returns the hash of the Wasm bytes, like `6ddb28e0980f643bb97350f7e3bacb0ff1fe74d846c6d4f2c625e766210fbb5b`. Now you can use `--wasm-hash` with `deploy` rather than `--wasm. Make sure to replace the example wasm hash with your own.
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
+<Tabs>
 
-<TabItem value="unix" label="macOS/Linux">
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract deploy \
@@ -67,9 +59,9 @@ stellar contract deploy \
   --alias increment
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="windows" label="Windows (PowerShell)">
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract deploy `
@@ -79,15 +71,15 @@ stellar contract deploy `
   --alias increment
 ```
 
-</TabItem>
+</Tab>
 
 </Tabs>
 
 This command will return the contract id (e.g. `CACDYF3CYMJEJTIVFESQYZTN67GO2R5D5IUABTCUG3HXQSRXCSOROBAN`), and you can use it to invoke the contract like we did in previous examples.
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
+<Tabs>
 
-<TabItem value="unix" label="macOS/Linux">
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract invoke \
@@ -98,9 +90,9 @@ stellar contract invoke \
   increment
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="windows" label="Windows (PowerShell)">
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract invoke `
@@ -111,7 +103,7 @@ stellar contract invoke `
   increment
 ```
 
-</TabItem>
+</Tab>
 
 </Tabs>
 
@@ -123,15 +115,15 @@ You should see the following output:
 
 Run it a few more times to watch the count change.
 
-## Run your own network/node
+## Run your own network/node {#run-your-own-networknode}
 
 Sometimes you'll need to run your own node:
 
-- Production apps! Stellar maintains public test RPC nodes for Testnet and Futurenet, but not for Mainnet. Instead, you will need to run your own node, and point your app at that. If you want to use a software-as-a-service platform for this, [various providers](../../../data/apis/rpc/providers.mdx) are available.
+- Production apps! Stellar maintains public test RPC nodes for Testnet and Futurenet, but not for Mainnet. Instead, you will need to run your own node, and point your app at that. If you want to use a software-as-a-service platform for this, [various providers](../../../data/apis/rpc/providers) are available.
 - When you need a network that differs from the version deployed to Testnet.
 
-The RPC team maintains Docker containers that make this as straightforward as possible. See the [RPC](../../../data/apis/rpc/admin-guide/README.mdx) reference for details.
+The RPC team maintains Docker containers that make this as straightforward as possible. See the [RPC](/docs/data/apis/rpc/admin-guide) reference for details.
 
 ## Up next
 
-Ready to turn these deployed contracts into a simple web application? Head over to the [Build a Dapp Frontend section](../../apps/dapp-frontend.mdx).
+Ready to turn these deployed contracts into a simple web application? Head over to the [Build a Dapp Frontend section](../../apps/dapp-frontend).
diff --git a/docs/build/smart-contracts/getting-started/deploy-to-testnet.mdx b/docs/build/smart-contracts/getting-started/deploy-to-testnet.mdx
index ceefd4997..7da0ed4ac 100644
--- a/docs/build/smart-contracts/getting-started/deploy-to-testnet.mdx
+++ b/docs/build/smart-contracts/getting-started/deploy-to-testnet.mdx
@@ -1,17 +1,10 @@
 ---
-sidebar_position: 20
-title: "Deploy and Debug Smart Contracts on Testnet & Interact with Other Contracts"
-sidebar_label: 2. Deploy to Testnet
+title: 2. Deploy to Testnet
+"og:title": "Deploy and Debug Smart Contracts on Testnet & Interact with Other Contracts"
 description: "Deploy Stellar smart contracts to Testnet using the CLI, interact with other contracts, test functionality, debug issues, and prepare for Mainnet deployment."
 ---
 
-# 2. Deploy to Testnet
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
-To recap what we've done so far, in [Setup](setup.mdx):
+To recap what we've done so far, in [Setup](/docs/build/smart-contracts/getting-started/setup):
 
 - we set up our local environment to write Rust smart contracts
 - installed the stellar-cli
@@ -23,7 +16,7 @@ In this guide, we’ll generate a Testnet-funded identity, deploy the contract t
 
 When you deploy a smart contract to a network, you need to specify a source account's keypair that will be used to sign the transactions.
 
-Let's generate a keypair called `alice`. You can use any name you want, but it might be nice to have some named keys that you can use for testing, such as [`alice`, `bob`, and `carol`](https://en.wikipedia.org/wiki/Alice_and_Bob). Notice that the keypair's account will be funded using [Friendbot](../../../networks/README.mdx#friendbot).
+Let's generate a keypair called `alice`. You can use any name you want, but it might be nice to have some named keys that you can use for testing, such as [`alice`, `bob`, and `carol`](https://en.wikipedia.org/wiki/Alice_and_Bob). Notice that the keypair's account will be funded using [Friendbot](/docs/networks#friendbot).
 
 ```sh
 stellar keys generate alice --network testnet --fund
@@ -45,9 +38,9 @@ stellar keys ls -l
 
 To deploy your HelloWorld contract, run the following command:
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
+<Tabs>
 
-<TabItem value="unix" label="macOS/Linux">
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract deploy \
@@ -57,9 +50,9 @@ stellar contract deploy \
   --alias hello_world
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="windows" label="Windows (PowerShell)">
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract deploy `
@@ -69,31 +62,30 @@ stellar contract deploy `
   --alias hello_world
 ```
 
-</TabItem>
+</Tab>
 
 </Tabs>
 
 This returns the contract's id, starting with a `C`. In this example, we're going to use `CACDYF3CYMJEJTIVFESQYZTN67GO2R5D5IUABTCUG3HXQSRXCSOROBAN`, so replace it with your actual contract id.
 
-:::tip
+<Tip>
 
 We used the `--alias` flag in this deploy command which will create a `~/.config/stellar/contract-ids/hello_world.json` file that maps the alias `hello_world` to the contract id and network. This allows us to refer to this contract as its alias instead the contract id.
 
-:::
+</Tip>
 
 ## Interact
 
-Using the code we wrote in [Write a Contract](./hello-world.mdx#contract-source-code) and the resulting `.wasm` file we built in [Build](hello-world.mdx#build-the-contract), run the following command to invoke the `hello` function.
+Using the code we wrote in [Write a Contract](./hello-world#contract-source-code) and the resulting `.wasm` file we built in [Build](/docs/build/smart-contracts/getting-started/hello-world#build-the-contract), run the following command to invoke the `hello` function.
 
-:::info
+<Info>
 
-In the background, the CLI is making RPC calls. For information on that checkout out the [RPC](../../../data/apis/rpc/admin-guide/README.mdx) reference page.
+In the background, the CLI is making RPC calls. For information on that checkout out the [RPC](/docs/data/apis/rpc/admin-guide) reference page.
 
-:::
+</Info>
+<Tabs>
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-
-<TabItem value="unix" label="macOS/Linux">
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract invoke \
@@ -105,9 +97,9 @@ stellar contract invoke \
   --to RPC
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="windows" label="Windows (PowerShell)">
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract invoke `
@@ -119,7 +111,7 @@ stellar contract invoke `
   --to RPC
 ```
 
-</TabItem>
+</Tab>
 
 </Tabs>
 
@@ -129,7 +121,7 @@ The following output should appear.
 ["Hello", "RPC"]
 ```
 
-:::note
+<Note>
 
 You may also see a message like:
 
@@ -145,9 +137,8 @@ This is expected! The `hello` function is **read-only**—it doesn't modify any
 
 The `--send=yes` flag is only needed for **state-changing functions**—those that write to contract storage. For those, the CLI first simulates the transaction (to estimate fees and check for errors), then you use `--send=yes` to actually submit and persist changes on-chain.
 
-:::
-
-:::info
+</Note>
+<Info>
 
 The `--` double-dash is required!
 
@@ -163,7 +154,7 @@ and
 stellar contract invoke ... -- hello --help
 ```
 
-:::
+</Info>
 
 ## Summary
 
diff --git a/docs/build/smart-contracts/getting-started/hello-world-frontend.mdx b/docs/build/smart-contracts/getting-started/hello-world-frontend.mdx
index 8dfdc9a63..43765d613 100644
--- a/docs/build/smart-contracts/getting-started/hello-world-frontend.mdx
+++ b/docs/build/smart-contracts/getting-started/hello-world-frontend.mdx
@@ -1,20 +1,16 @@
 ---
-sidebar_position: 50
-sidebar_label: "5. Build a Hello World Frontend"
-title: "Build a frontend for the Hello World contract"
+title: 5. Build a Hello World Frontend
+"og:title": Build a frontend for the Hello World contract
 description: "Build a frontend for the Hello World contract by using Stellar CLI to generate TypeScript bindings."
-pagination_next: build/apps/dapp-frontend
 ---
 
-# 5. Build a Hello World Frontend
-
 In the previous examples, we invoked the contracts using the Stellar CLI, and in this last part of the guide we'll create a web app that interacts with the Hello World contract through TypeScript bindings.
 
-:::info
+<Info>
 
-This example shows one way of creating a binding between a contract and a frontend. For a more comprehensive guide to Dapp frontends, see the [Build a Dapp Frontend](../../apps/dapp-frontend.mdx) documentation. For tooling that helps you start with smart contracts integrated with a working frontend environment quickly, jump to learn more about [Scaffold Stellar](#using-scaffold-stellar-to-rapidly-develop-dapps).
+This example shows one way of creating a binding between a contract and a frontend. For a more comprehensive guide to Dapp frontends, see the [Build a Dapp Frontend](../../apps/dapp-frontend) documentation. For tooling that helps you start with smart contracts integrated with a working frontend environment quickly, jump to learn more about [Scaffold Stellar](#using-scaffold-stellar-to-rapidly-develop-dapps).
 
-:::
+</Info>
 
 ## Initialize a frontend toolchain from scratch
 
@@ -57,7 +53,7 @@ extra-escape
 
 ## Generate an NPM package for the Hello World contract
 
-Before we open the new frontend files, let's generate an NPM package for the Hello World contract. This is our suggested way to interact with contracts from frontends. These generated libraries work with any JavaScript project (not a specific UI like React), and make it easy to work with some of the trickiest bits of smart contracts on Stellar, like encoding [XDR](../../../learn/fundamentals/contract-development/types/fully-typed-contracts.mdx).
+Before we open the new frontend files, let's generate an NPM package for the Hello World contract. This is our suggested way to interact with contracts from frontends. These generated libraries work with any JavaScript project (not a specific UI like React), and make it easy to work with some of the trickiest bits of smart contracts on Stellar, like encoding [XDR](../../../learn/fundamentals/contract-development/types/fully-typed-contracts).
 
 This is going to use the CLI command `stellar contract bindings typescript`:
 
@@ -68,11 +64,11 @@ stellar contract bindings typescript \
   --output-dir packages/hello_world
 ```
 
-:::tip
+<Tip>
 
 Notice that we were able to use the contract alias, `hello_world`, in place of the contract id!
 
-:::
+</Tip>
 
 The binding will be created in as a NPM package in the directory `packages/hello_world` as specified in the CLI command. We'll need to build the bindings package, since (in its initial state) the package is mostly TypeScript types and stubs for the various contract functions.
 
@@ -121,15 +117,15 @@ And open [localhost:4321](http://localhost:4321) in your browser. You should see
 
 You can try updating the argument to `{ to: 'Stellar' }`. When you save the file, the page will automatically update.
 
-:::info
+<Info>
 
 When you start up the dev server with `npm run dev`, you will see similar output in your terminal as when you ran `npm run init`. This is because the `dev` script in package.json is set up to run `npm run init` and `astro dev`, so that you can ensure that your deployed contract and your generated NPM package are always in sync. If you want to just start the dev server without the initialize.js script, you can run `npm run astro dev`.
 
-:::
+</Info>
 
 ## Using Scaffold Stellar to rapidly develop dapps
 
-[Scaffold Stellar](../../../tools/scaffold-stellar.mdx) is a developer toolkit for building decentralized applications and smart contracts on the Stellar blockchain, integrated with a frontend application.
+[Scaffold Stellar](../../../tools/scaffold-stellar) is a developer toolkit for building decentralized applications and smart contracts on the Stellar blockchain, integrated with a frontend application.
 
 Getting a running set of smart contracts and a frontend can be done in just a few short steps with Scaffold Stellar. This tutorial will show you how to make a new Scaffold Stellar project.
 
@@ -175,4 +171,4 @@ The second task it runs is `vite`, a popular JavaScript build tool to compile an
 
 After a little compiling time, you'll be able to see your running app at [localhost:5173](http://localhost:5173)!
 
-Learn more about [Scaffold Stellar](../../../tools/scaffold-stellar.mdx).
+Learn more about [Scaffold Stellar](../../../tools/scaffold-stellar).
diff --git a/docs/build/smart-contracts/getting-started/hello-world.mdx b/docs/build/smart-contracts/getting-started/hello-world.mdx
index 76a73b599..8362a263c 100644
--- a/docs/build/smart-contracts/getting-started/hello-world.mdx
+++ b/docs/build/smart-contracts/getting-started/hello-world.mdx
@@ -1,16 +1,11 @@
 ---
-sidebar_position: 10
-sidebar_label: 1. Hello World
-title: "Write, Test, and Deploy a Rust Smart Contract"
+title: Hello World
+sidebarTitle: 1. Hello World
+"og:title": "Write, Test, and Deploy a Rust Smart Contract"
 description: "Create your first smart contract on Stellar with this Hello World guide. Learn how to write, deploy, and test your contract using Rust and the Stellar CLI."
 ---
 
-# Hello World
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-Once you've [set up](./setup.mdx) your development environment, you're ready to create your first smart contract.
+Once you've [set up](./setup) your development environment, you're ready to create your first smart contract.
 
 ## Create a New Project
 
@@ -36,7 +31,7 @@ The `init` command will create a Rust workspace project, using the recommended s
     │   │   └── test.rs
 ```
 
-### Cargo.toml
+### Cargo.toml {#cargotoml}
 
 The `Cargo.toml` file at the root of the project is set up as Rust Workspace, which allows us to include multiple smart contracts in one project.
 
@@ -55,11 +50,11 @@ members = [
 soroban-sdk = "28"
 ```
 
-:::info
+<Info>
 
 The `testutils` are automatically enabled inside [Rust unit tests] inside the same crate as your contract. If you write tests from another crate, you'll need to require the `testutils` feature for those tests and enable the `testutils` feature when running your tests with `cargo test --features testutils` to be able to use those test utilities.
 
-:::
+</Info>
 
 #### `release` Profile
 
@@ -91,13 +86,13 @@ debug-assertions = true
 
 See the [logging example] for more information about how to log.
 
-[logging example]: ../example-contracts/logging.mdx
+[logging example]: ../example-contracts/logging
 
 ### Contracts Directory
 
 The `contracts` directory is where Soroban contracts will live, each in their own directory. There is already a `hello-world` contract in there to get you started.
 
-#### Contract-specific Cargo.toml file
+#### Contract-specific Cargo.toml file {#contract-specific-cargotoml-file}
 
 Each contract should have its own `Cargo.toml` file, which relies on the top-level `Cargo.toml` that we just discussed.
 
@@ -111,7 +106,7 @@ edition = "2021"
 publish = false
 ```
 
-The `crate-type` includes `cdylib`, which is required for building contracts. It also includes `lib`, so other crates, such as a [fuzz target](../../guides/testing/fuzzing.mdx), can import the contract as a Rust library.
+The `crate-type` includes `cdylib`, which is required for building contracts. It also includes `lib`, so other crates, such as a [fuzz target](/docs/build/guides/testing/fuzzing), can import the contract as a Rust library.
 
 ```toml
 [lib]
@@ -145,7 +140,7 @@ The contract imports the types and macros that it needs from the `soroban-sdk` c
 use soroban_sdk::{contract, contractimpl, vec, Env, String, Vec};
 ```
 
-Many of the types available in typical Rust programs, such as `std::vec::Vec`, are not available, as there is no allocator and no heap memory in Soroban contracts by default (the SDK does provide an opt-in allocator through its `alloc` feature — see the [alloc example](../example-contracts/alloc.mdx)). The `soroban-sdk` provides a variety of types like `Vec`, `Map`, `Bytes`, `BytesN`, `Symbol`, that all utilize the Soroban environment's memory and native capabilities. Primitive values like `u128`, `i128`, `u64`, `i64`, `u32`, `i32`, and `bool` can also be used. Floats and floating point math are not supported.
+Many of the types available in typical Rust programs, such as `std::vec::Vec`, are not available, as there is no allocator and no heap memory in Soroban contracts by default (the SDK does provide an opt-in allocator through its `alloc` feature — see the [alloc example](../example-contracts/alloc)). The `soroban-sdk` provides a variety of types like `Vec`, `Map`, `Bytes`, `BytesN`, `Symbol`, that all utilize the Soroban environment's memory and native capabilities. Primitive values like `u128`, `i128`, `u64`, `i64`, `u32`, `i32`, and `bool` can also be used. Floats and floating point math are not supported.
 
 Contract inputs must not be references.
 
@@ -195,7 +190,7 @@ Writing tests for Soroban contracts involves writing Rust code using the test fa
 Given our `Contract`, a simple test will look like this.
 
 <Tabs>
-<TabItem value="lib.rs" label="contracts/hello-world/src/lib.rs">
+<Tab title="contracts/hello-world/src/lib.rs">
 
 ```rust
 #![no_std]
@@ -214,8 +209,8 @@ impl Contract {
 mod test;
 ```
 
-</TabItem>
-<TabItem value="test.rs" label="contracts/hello-world/src/test.rs" default>
+</Tab>
+<Tab title="contracts/hello-world/src/test.rs">
 
 ```rust
 #![cfg(test)]
@@ -241,7 +236,7 @@ fn test() {
 }
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 In any test the first thing that is always required is an `Env`, which is the Soroban environment that the contract will run inside of.
@@ -291,11 +286,11 @@ test test::test ... ok
 
 Try changing the values in the test to see how it works.
 
-:::note
+<Note>
 
 The first time you run the tests you may see output in the terminal of cargo compiling all the dependencies before running the tests.
 
-:::
+</Note>
 
 ## Build the contract
 
@@ -305,11 +300,11 @@ To build a smart contract to deploy or run, use the `stellar contract build` com
 stellar contract build
 ```
 
-:::tip
+<Tip>
 
-If you get an error like `can't find crate for 'core'`, it means you didn't install the wasm32 target during the [setup step](./setup.mdx#install-the-target). You can do so by running `rustup target add wasm32v1-none` (reminder, this requires Rust `v1.84.0` or higher).
+If you get an error like `can't find crate for 'core'`, it means you didn't install the wasm32 target during the [setup step](./setup#install-the-target). You can do so by running `rustup target add wasm32v1-none` (reminder, this requires Rust `v1.84.0` or higher).
 
-:::
+</Tip>
 
 This is a small wrapper around `cargo build` that sets the target to `wasm32v1-none` and the profile to `release` (it also [optimizes](#optimizing-builds) the resulting `.wasm` file by default). You can think of it as a shortcut for the following command:
 
@@ -319,7 +314,7 @@ cargo build --target wasm32v1-none --release
 
 A `.wasm` file will be outputted in the `target` directory, at `target/wasm32v1-none/release/hello_world.wasm`. The `.wasm` file is the built contract.
 
-The `.wasm` file contains the logic of the contract, as well as the contract's [specification / interface types](../../../learn/fundamentals/contract-development/types/fully-typed-contracts.mdx), which can be imported into other contracts who wish to call it. This is the only artifact needed to deploy the contract, share the interface with others, or integration test against the contract.
+The `.wasm` file contains the logic of the contract, as well as the contract's [specification / interface types](../../../learn/fundamentals/contract-development/types/fully-typed-contracts), which can be imported into other contracts who wish to call it. This is the only artifact needed to deploy the contract, share the interface with others, or integration test against the contract.
 
 ## Optimizing Builds
 
@@ -329,17 +324,16 @@ The `stellar contract build` command optimizes the generated `.wasm` by default,
 stellar contract build --optimize=false
 ```
 
-:::tip
+<Tip>
 
 Optimized contract builds are only necessary when deploying to a network with fees or when analyzing and profiling a contract to get it as small as possible. If you're just starting out writing a contract, un-optimized builds will work just fine.
 
-:::
-
-:::note
+</Tip>
+<Note>
 
 Older versions of the Stellar CLI provided a standalone `stellar contract optimize` command. That command is now deprecated in favor of the (default) `--optimize` flag on `stellar contract build`.
 
-:::
+</Note>
 
 ## Summary
 
@@ -348,4 +342,4 @@ In this section, we wrote a simple contract that can be deployed to a Soroban ne
 Next we'll learn to deploy the HelloWorld contract to Stellar's Testnet network and interact with it over RPC using the CLI.
 
 [rust unit tests]: https://doc.rust-lang.org/rust-by-example/testing/unit_testing.html
-[`stellar-cli`]: setup.mdx#install-the-stellar-cli
+[`stellar-cli`]: setup#install-the-stellar-cli
diff --git a/docs/build/smart-contracts/getting-started/index.mdx b/docs/build/smart-contracts/getting-started/index.mdx
new file mode 100644
index 000000000..d737defe2
--- /dev/null
+++ b/docs/build/smart-contracts/getting-started/index.mdx
@@ -0,0 +1,48 @@
+---
+title: Getting Started
+"og:title": "Get Started with Smart Contracts: Setup, Write in Rust & Deploy"
+description: "Get started with smart contracts by setting up your environment, writing code in Rust, and deploying contracts using CLI tools on the Stellar network."
+---
+
+<Tip>
+
+Start with [Scaffold Stellar](https://scaffoldstellar.org/docs/quick-start) for the fastest path to a working dApp on Stellar. Scaffold Stellar is a toolkit that bundles a CLI, contract templates, a smart contract registry, and a modern frontend for building full-stack dApps.
+
+_Use this getting started guide for a lower-level tour of Stellar smart contract development from the main Stellar CLI._
+
+</Tip>
+
+Dive into smart contract development with this Getting Started tutorial.
+
+<CardGroup cols={2}>
+  <Card title="Setup" icon="file-lines" href="/docs/build/smart-contracts/getting-started/setup">
+
+    Learn how to set up Stellar smart contract development by installing Rust, configuring your editor, and setting up the Stellar CLI with this step-by-step guide.
+
+  </Card>
+  <Card title="1. Hello World" icon="file-lines" href="/docs/build/smart-contracts/getting-started/hello-world">
+
+    Create your first smart contract on Stellar with this Hello World guide. Learn how to write, deploy, and test your contract using Rust and the Stellar CLI.
+
+  </Card>
+  <Card title="2. Deploy to Testnet" icon="file-lines" href="/docs/build/smart-contracts/getting-started/deploy-to-testnet">
+
+    Deploy Stellar smart contracts to Testnet using the CLI, interact with other contracts, test functionality, debug issues, and prepare for Mainnet deployment.
+
+  </Card>
+  <Card title="3. Storing Data" icon="file-lines" href="/docs/build/smart-contracts/getting-started/storing-data">
+
+    Follow along with the increment example to write a simple contract that stores and retrieves data on the Stellar network. Learn about storage and TTL.
+
+  </Card>
+  <Card title="4. Deploy the Increment Contract" icon="file-lines" href="/docs/build/smart-contracts/getting-started/deploy-increment-contract">
+
+    Follow this step-by-step guide in the final section of Getting Started to learn how to deploy the increment smart contract on Testnet using the Stellar CLI.
+
+  </Card>
+  <Card title="5. Build a Hello World Frontend" icon="file-lines" href="/docs/build/smart-contracts/getting-started/hello-world-frontend">
+
+    Build a frontend for the Hello World contract by using Stellar CLI to generate TypeScript bindings.
+
+  </Card>
+</CardGroup>
diff --git a/docs/build/smart-contracts/getting-started/setup.mdx b/docs/build/smart-contracts/getting-started/setup.mdx
index 23bd01338..c5c8a4ae8 100644
--- a/docs/build/smart-contracts/getting-started/setup.mdx
+++ b/docs/build/smart-contracts/getting-started/setup.mdx
@@ -1,21 +1,9 @@
 ---
-title: "Set Up and Configure Your Environment for Writing Smart Contracts"
-sidebar_label: Setup
+title: Setup
+"og:title": Set Up and Configure Your Environment for Writing Smart Contracts
 description: "Learn how to set up Stellar smart contract development by installing Rust, configuring your editor, and setting up the Stellar CLI with this step-by-step guide."
-sidebar_position: 0
 ---
 
-# Setup
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-import { getShell } from "@site/src/helpers/getShell";
-import { latestVersion } from "@site/src/helpers/stellarCli";
-import { getStellarCliLatestReleaseUrl } from "@site/src/helpers/getStellarCliLatestReleaseUrl";
-import { StellarCliVersion } from "@site/src/components/StellarCliVersion";
-import { StellarCliWingetVersion } from "@site/src/components/StellarCliWingetVersion";
-
 Stellar smart contracts are small programs written in the [Rust] programming language.
 
 To build and develop contracts you need the following prerequisites:
@@ -26,8 +14,8 @@ To build and develop contracts you need the following prerequisites:
 
 ## Install Rust
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 If you use macOS, Linux, or another Unix-like OS, the simplest method to install a Rust toolchain is to install `rustup`. Install `rustup` with the following command.
 
@@ -37,25 +25,25 @@ curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
 
 Then restart the terminal.
 
-</TabItem>
-<TabItem value="windows" label="Windows">
+</Tab>
+<Tab title="Windows">
 
 On Windows, download and run [rustup-init.exe](https://static.rust-lang.org/rustup/dist/i686-pc-windows-gnu/rustup-init.exe). You can continue with the default settings by pressing Enter.
 
-:::tip
+<Tip>
 
 The Stellar CLI uses emojis in its output. To properly render them on Windows, it is recommended to use the [Windows Terminal](https://learn.microsoft.com/en-us/windows/terminal). See [how to install Windows Terminal](https://learn.microsoft.com/en-us/windows/terminal/install) on Microsoft Learn. If the CLI is used in the built in Windows Command Prompt or Windows PowerShell the CLI will function as expected but the emojis will appear as question marks.
 
-:::
+</Tip>
 
 If you're already using [WSL](https://learn.microsoft.com/en-us/windows/wsl/install), you can also follow the instructions for Linux.
 
-</TabItem>
-<TabItem value="other" label="Other">
+</Tab>
+<Tab title="Other">
 
 For other methods of installing [Rust], see: https://www.rust-lang.org/tools/install
 
-</TabItem>
+</Tab>
 </Tabs>
 
 Stellar smart contracts require **Rust toolchain `v1.84.0` or higher**, as the `wasm32v1-none` target is only available in recent versions.
@@ -80,13 +68,13 @@ You'll need a "target" for which your smart contract will be compiled. Install t
 rustup target add wasm32v1-none
 ```
 
-:::note
+<Note>
 
 When you install Rust, the WebAssembly target is installed per-toolchain. If you update your Rust version, you'll need to reinstall the `wasm32v1-none` target for the new toolchain.
 
-:::
+</Note>
 
-You can learn more about the finer points of what this target brings to the table, in our page all about the [Stellar Rust dialect](../../../learn/fundamentals/contract-development/rust-dialect.mdx#limited-webassembly-features). This page describes the subset of Rust functionality that is available to you within Stellar smart contract environment.
+You can learn more about the finer points of what this target brings to the table, in our page all about the [Stellar Rust dialect](../../../learn/fundamentals/contract-development/rust-dialect#limited-webassembly-features). This page describes the subset of Rust functionality that is available to you within Stellar smart contract environment.
 
 ## Configure an editor
 
@@ -102,18 +90,18 @@ Here are the tools to you need to configure your editor:
 
 The [Stellar CLI](https://github.com/stellar/stellar-cli) can execute smart contracts on futurenet, testnet, mainnet, as well as in a local sandbox.
 
-:::info
+<Info>
 
-The latest stable release is [v{latestVersion}](https://github.com/stellar/stellar-cli/releases/latest).
+The latest stable release is available on the [Stellar CLI releases page](https://github.com/stellar/stellar-cli/releases/latest).
 
-:::
+</Info>
 
 ### Install
 
 There are a few ways to install the [latest release](https://github.com/stellar/stellar-cli/releases) of Stellar CLI.
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS">
+<Tabs>
+<Tab title="macOS">
 
 Install using script (macOS, Linux):
 
@@ -129,10 +117,12 @@ brew install stellar-cli
 
 Install with cargo from source:
 
-<StellarCliVersion />
+```sh
+cargo install --locked stellar-cli
+```
 
-</TabItem>
-<TabItem value="linux" label="Linux">
+</Tab>
+<Tab title="Linux">
 
 Install using script (macOS, Linux):
 
@@ -148,9 +138,11 @@ brew install stellar-cli
 
 Install with cargo from source:
 
-<StellarCliVersion />
+```sh
+cargo install --locked stellar-cli
+```
 
-:::note
+<Note>
 
 Installing from source requires a C build system. To install a C build system on Debian/Ubuntu, use:
 
@@ -158,45 +150,48 @@ Installing from source requires a C build system. To install a C build system on
 sudo apt update && sudo apt install -y build-essential
 ```
 
-:::
-
-</TabItem>
-<TabItem value="windows" label="Windows">
+</Note>
+</Tab>
+<Tab title="Windows">
 
 Using the installer:
 
-1. Download the installer from the <a href={getStellarCliLatestReleaseUrl()}>latest release</a>.
+1. Download the installer from the [latest release](https://github.com/stellar/stellar-cli/releases/latest).
 2. Go to your Downloads folder, double click the installer and follow the wizard instructions.
 3. Restart your terminal to use the `stellar` command.
 
 Using [winget](https://learn.microsoft.com/en-us/windows/package-manager/winget):
 
-<StellarCliWingetVersion />
+```powershell
+winget install --id Stellar.StellarCLI
+```
 
 Install with cargo from source:
 
-<StellarCliVersion />
+```powershell
+cargo install --locked stellar-cli
+```
 
-</TabItem>
+</Tab>
 </Tabs>
 
-:::info
+<Info>
 
 Report issues and share feedback about the Stellar CLI [here](https://github.com/stellar/stellar-cli/issues/new/choose).
 
-:::
+</Info>
 
 ### Documentation
 
-The auto-generated comprehensive reference documentation is available [here](../../../tools/cli/stellar-cli.mdx).
+The auto-generated comprehensive reference documentation is available [here](../../../tools/cli/stellar-cli).
 
 ### Autocompletion
 
 You can use `stellar completion` to generate shell completion for different shells. You should absolutely try it out. It will feel like a super power!
 
-<Tabs id="shell" defaultValue={getShell()}>
+<Tabs>
 
-<TabItem value="bash" label="Bash">
+<Tab title="Bash">
 
 To enable autocomplete on the current shell session:
 
@@ -210,9 +205,9 @@ To enable autocomplete permanently, run the following command, then restart your
 echo "source <(stellar completion --shell bash)" >> ~/.bashrc
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="zsh" label="ZSH">
+<Tab title="ZSH">
 
 To enable autocomplete on the current shell session:
 
@@ -226,9 +221,9 @@ To enable autocomplete permanently, run the following commands, then restart you
 echo "source <(stellar completion --shell zsh)" >> ~/.zshrc
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="fish" label="fish">
+<Tab title="fish">
 
 To enable autocomplete on the current shell session:
 
@@ -242,9 +237,9 @@ To enable autocomplete permanently, run the following command, then restart your
 echo "stellar completion --shell fish | source" >> ~/.config/fish/config.fish
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="powershell" label="PowerShell">
+<Tab title="PowerShell">
 
 To enable autocomplete on the current shell session:
 
@@ -261,15 +256,14 @@ Add-Content $PROFILE 'Set-PSReadlineKeyHandler -Key Tab -Function MenuComplete'
 Add-Content $PROFILE 'stellar completion --shell powershell | Out-String | Invoke-Expression'
 ```
 
-:::tip
+<Tip>
 
 If you get an error like `cannot be loaded because running scripts is disabled on this system`, you may need to change your [Execution Policy](https://go.microsoft.com/fwlink/?LinkID=135170) with `Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope CurrentUser`. **Before running this command, be sure you understand the implications of doing so.**
 
-:::
-
-</TabItem>
+</Tip>
+</Tab>
 
-<TabItem value="elvish" label="Elvish">
+<Tab title="Elvish">
 
 To enable autocomplete on the current shell session:
 
@@ -283,7 +277,7 @@ To enable autocomplete permanently, run the following commands, then restart you
 echo "source (stellar completion --shell elvish)" >> ~/.elvish/rc.elv
 ```
 
-</TabItem>
+</Tab>
 
 </Tabs>
 
diff --git a/docs/build/smart-contracts/getting-started/storing-data.mdx b/docs/build/smart-contracts/getting-started/storing-data.mdx
index 84ec5f9fc..023572e9f 100644
--- a/docs/build/smart-contracts/getting-started/storing-data.mdx
+++ b/docs/build/smart-contracts/getting-started/storing-data.mdx
@@ -1,20 +1,14 @@
 ---
-sidebar_position: 30
-title: "Write a Smart Contract to Store & Retrieve Data with Increment Example"
-sidebar_label: 3. Storing Data
+title: 3. Storing Data
+"og:title": "Write a Smart Contract to Store & Retrieve Data with Increment Example"
 description: "Follow along with the increment example to write a simple contract that stores and retrieves data on the Stellar network. Learn about storage and TTL."
 ---
 
-# 3. Storing Data
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
 Now that we've built a basic Hello World example contract, we'll write a simple contract that stores and retrieves data. This will help you see the basics of Soroban's storage system.
 
 This is going to follow along with the [increment example](https://github.com/stellar/soroban-examples/tree/v22.0.1/increment), which has a single function that increments an internal counter and returns the value. If you want to see a working example, [try it in Devcontainers](https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web).
 
-This tutorial assumes that you've already completed the previous steps in Getting Started: [Setup](./setup.mdx), [Hello World](./hello-world.mdx), and [Deploy to Testnet](./deploy-to-testnet.mdx).
+This tutorial assumes that you've already completed the previous steps in Getting Started: [Setup](./setup), [Hello World](./hello-world), and [Deploy to Testnet](./deploy-to-testnet).
 
 ## Adding the increment contract
 
@@ -104,7 +98,7 @@ The `get()` function gets the current value associated with the counter key.
 
 If no value is currently stored, the value given to `unwrap_or(...)` is returned instead.
 
-Values stored as contract data and retrieved are transmitted from [the environment](../../../learn/fundamentals/contract-development/environment-concepts.mdx) and expanded into the type specified. In this case a `u32`. If the value can be expanded, the type returned will be a `u32`. Otherwise, if a developer cast it to be some other type, a panic would occur at the unwrap.
+Values stored as contract data and retrieved are transmitted from [the environment](../../../learn/fundamentals/contract-development/environment-concepts) and expanded into the type specified. In this case a `u32`. If the value can be expanded, the type returned will be a `u32`. Otherwise, if a developer cast it to be some other type, a panic would occur at the unwrap.
 
 ```rust
 env.storage()
@@ -120,9 +114,9 @@ The `set()` function stores the new count value against the key, replacing the e
 env.storage().instance().extend_ttl(100, 100);
 ```
 
-All contract data has a Time To Live (TTL), measured in ledgers, that must be periodically extended. If an entry's TTL is not periodically extended, the entry will eventually become "archived." You can learn more about this in the [State Archival](../../../learn/fundamentals/contract-development/storage/state-archival.mdx) document.
+All contract data has a Time To Live (TTL), measured in ledgers, that must be periodically extended. If an entry's TTL is not periodically extended, the entry will eventually become "archived." You can learn more about this in the [State Archival](../../../learn/fundamentals/contract-development/storage/state-archival) document.
 
-For now, it's worth knowing that there are three kinds of storage: `Persistent`, `Temporary`, and `Instance`. This contract only uses `Instance` storage: `env.storage().instance()`. Every time the counter is incremented, this storage's TTL gets extended by 100 [ledgers](../../../learn/fundamentals/stellar-data-structures/ledgers.mdx), or about 500 seconds.
+For now, it's worth knowing that there are three kinds of storage: `Persistent`, `Temporary`, and `Instance`. This contract only uses `Instance` storage: `env.storage().instance()`. Every time the counter is incremented, this storage's TTL gets extended by 100 [ledgers](../../../learn/fundamentals/stellar-data-structures/ledgers), or about 500 seconds.
 
 ### Build the contract
 
diff --git a/docs/build/smart-contracts/index.mdx b/docs/build/smart-contracts/index.mdx
new file mode 100644
index 000000000..8afcbb3cd
--- /dev/null
+++ b/docs/build/smart-contracts/index.mdx
@@ -0,0 +1,26 @@
+---
+title: Write Smart Contracts
+sidebarTitle: Build Smart Contracts
+"og:title": "Build, Test, and Deploy Smart Contracts on Stellar: Tools & Best Practices"
+description: "Learn how to build, test, deploy, and manage smart contracts on the Stellar network. Explore best practices, tools, guides, and example contracts for development."
+---
+
+This section will walk you through how to get set up to write smart contracts on Stellar, plus an introduction to testing, storing data, and deploying your contracts. It also provides an array of example contracts for use.
+
+<CardGroup cols={2}>
+  <Card title="Introduction" icon="file-lines" href="/docs/build/smart-contracts/overview">
+
+    An overview of Stellar smart contracts, including information about the Soroban Rust SDK, host environment, and answers to general, commonly asked questions.
+
+  </Card>
+  <Card title="Getting Started" icon="box-archive" href="/docs/build/smart-contracts/getting-started">
+
+    6 items
+
+  </Card>
+  <Card title="Example Contracts" icon="box-archive" href="/docs/build/smart-contracts/example-contracts">
+
+    23 items
+
+  </Card>
+</CardGroup>
diff --git a/docs/build/smart-contracts/overview.mdx b/docs/build/smart-contracts/overview.mdx
index 09608f940..015592377 100644
--- a/docs/build/smart-contracts/overview.mdx
+++ b/docs/build/smart-contracts/overview.mdx
@@ -1,39 +1,37 @@
 ---
-sidebar_position: 10
-title: "An Overview of Smart Contracts on Stellar, Including the Rust SDK and FAQs"
-sidebar_label: Introduction
+title: Overview
+sidebarTitle: Introduction
+"og:title": "An Overview of Smart Contracts on Stellar, Including the Rust SDK and FAQs"
 description: "An overview of Stellar smart contracts, including information about the Soroban Rust SDK, host environment, and answers to general, commonly asked questions."
 ---
 
-# Overview
-
 Soroban is the smart contracts platform on the Stellar network. These contracts are small programs written in the [Rust language](https://www.rust-lang.org) and compiled as [WebAssembly](https://webassembly.org) (Wasm) for deployment.
 
-:::note
+<Note>
 
-For a comprehensive introduction to Stellar smart contracts, view the [Smart Contract Learn Section](../../learn/fundamentals/contract-development/overview.mdx).
+For a comprehensive introduction to Stellar smart contracts, view the [Smart Contract Learn Section](../../learn/fundamentals/contract-development/overview).
 
-:::
+</Note>
 
-Write your first smart contract on Stellar using the [Getting Started Guide](./getting-started/setup.mdx).
+Write your first smart contract on Stellar using the [Getting Started Guide](./getting-started/setup).
 
 ## Developing Smart Contracts
 
 Stellar smart contracts have several characteristics (such as resource limits, security considerations, and more) that force contracts to use only a narrow subset of the full Rust language and must use specialized libraries for most tasks.
 
-Learn more in the [Contract Rust Dialect section](../../learn/fundamentals/contract-development/rust-dialect.mdx).
+Learn more in the [Contract Rust Dialect section](../../learn/fundamentals/contract-development/rust-dialect).
 
 In particular, the Rust standard library and most third-party libraries (called [crates](../../learn/migrate/evm/solidity-and-rust-advanced-concepts#crates)) will not be available for direct off-the-shelf use in contracts due to the abovementioned constraints. Some crates can be adapted for use in contracts, and others may be incorporated into the host environment as host objects or functions.
 
-:::note
+<Note>
 
 Other languages may be supported in the future, but at this time, only Rust is supported.
 
-:::
+</Note>
 
 ## Soroban Rust SDK
 
-Contracts are developed using a software development kit (SDK). The [Soroban Rust SDK](../../tools/sdks/contract-sdks.mdx#soroban-rust-sdk) consists of a Rust crate and a command-line (CLI) tool.
+Contracts are developed using a software development kit (SDK). The [Soroban Rust SDK](../../tools/sdks/contract-sdks#soroban-rust-sdk) consists of a Rust crate and a command-line (CLI) tool.
 
 The SDK crate acts as a substitute for the Rust standard library — providing data structures and utility functions for contracts — as well as providing access to smart-contract-specific functionality from the contract environment, like cryptographic hashing and signature verification, access to on-chain persistent storage, and location and invocation of secondary contracts via stable identifiers.
 
@@ -45,7 +43,7 @@ The Soroban SDK CLI tool provides a developer-focused front-end for:
 - Versioning
 - Deploying
 
-It also includes a complete implementation of the contract host environment that is identical to the one that runs on-chain, called [local testing mode](../../learn/fundamentals/contract-development/errors-and-debugging/debugging.mdx#local-testing-mode). With this capability, contracts can be run locally on a developer's workstation and can be tested and debugged directly with a local debugger within a standard IDE, as well as a native test harness for fast-feedback unit testing and high-speed fuzzing or property testing.
+It also includes a complete implementation of the contract host environment that is identical to the one that runs on-chain, called [local testing mode](../../learn/fundamentals/contract-development/errors-and-debugging/debugging#local-testing-mode). With this capability, contracts can be run locally on a developer's workstation and can be tested and debugged directly with a local debugger within a standard IDE, as well as a native test harness for fast-feedback unit testing and high-speed fuzzing or property testing.
 
 ## Host environment
 
@@ -53,87 +51,54 @@ The host environment is a set of Rust crates compiled into the SDK CLI tool and
 
 Most contract developers will not frequently need to interact with the host environment directly — SDK functions wrap most of its facilities and provide richer and more ergonomic types and functions — but it is helpful to understand its structure to understand the conceptual model the SDK is presenting. Some parts of the host environment will likely be visible when testing or debugging contracts compiled natively on a local workstation.
 
-Learn more in the [Environment Concepts section](../../learn/fundamentals/contract-development/environment-concepts.mdx).
+Learn more in the [Environment Concepts section](../../learn/fundamentals/contract-development/environment-concepts).
 
 ## Stellar smart contract FAQs
 
-{/* prettier-ignore-start */}
-
-<details>
-  <summary>**What is Soroban to Stellar? Is it a new blockchain?**</summary>
+<AccordionGroup>
+<Accordion title="**What is Soroban to Stellar? Is it a new blockchain?**">
 
-  Soroban is not a new blockchain. Soroban is a smart contract platform
-  integrated into the existing Stellar blockchain. It is an additive feature
-  that lives alongside and doesn't replace the existing set of Stellar
-  operations.
-</details>
+Soroban is not a new blockchain. Soroban is a smart contract platform integrated into the existing Stellar blockchain. It is an additive feature that lives alongside and doesn't replace the existing set of Stellar operations.
 
-<details>
-  <summary>**How do I invoke a Soroban contract on Stellar?**</summary>
+</Accordion>
+<Accordion title="**How do I invoke a Soroban contract on Stellar?**">
 
-  Invoke a Soroban contract by submitting a transaction that contains the new
-  operation:
-  [`InvokeHostFunctionOp`](../../learn/fundamentals/transactions/list-of-operations.mdx#invoke-host-function).
-</details>
+Invoke a Soroban contract by submitting a transaction that contains the new operation: [`InvokeHostFunctionOp`](../../learn/fundamentals/transactions/list-of-operations#invoke-host-function).
 
-<details>
-  <summary>**Can Soroban contracts use Stellar accounts for authentication?**</summary>
+</Accordion>
+<Accordion title="**Can Soroban contracts use Stellar accounts for authentication?**">
 
-  Yes. Stellar accounts are shared with Soroban. Smart contacts have access to
-  Stellar account signer configuration and know the source account that directly
-  invoked them in a transaction. Check out the [Authorization
-  section](../../learn/fundamentals/contract-development/authorization.mdx) for
-  more information.
-</details>
+Yes. Stellar accounts are shared with Soroban. Smart contacts have access to Stellar account signer configuration and know the source account that directly invoked them in a transaction. Check out the [Authorization section](../../learn/fundamentals/contract-development/authorization) for more information.
 
-<details>
-  <summary>**Can Soroban contracts interact with Stellar assets?**</summary>
+</Accordion>
+<Accordion title="**Can Soroban contracts interact with Stellar assets?**">
 
-  Yes. Soroban contains a built-in [Stellar Asset
-  Contract](../../tokens/stellar-asset-contract.mdx) that can interact with
-  classic trustlines.
-</details>
+Yes. Soroban contains a built-in [Stellar Asset Contract](../../tokens/stellar-asset-contract) that can interact with classic trustlines.
 
-<details>
-  <summary>**Do issuers of Stellar assets maintain authorization over an asset sent to a non-account identifier in Soroban (`AUTH_REQUIRED`, `AUTH_REVOCABLE`, `AUTH_CLAWBACK`)?**</summary>
+</Accordion>
+<Accordion title="**Do issuers of Stellar assets maintain authorization over an asset sent to a non-account identifier in Soroban (`AUTH_REQUIRED`, `AUTH_REVOCABLE`, `AUTH_CLAWBACK`)?**">
 
-  Yes. Issuers retain the same level of control on Soroban as they have
-  regularly. This functionality is accessible through a set of admin functions
-  (clawback, set_auth) on the built-in Stellar Asset Contract.
-</details>
+Yes. Issuers retain the same level of control on Soroban as they have regularly. This functionality is accessible through a set of admin functions (clawback, set_auth) on the built-in Stellar Asset Contract.
 
-<details>
-  <summary>**Can Soroban contracts interact with any other Stellar operations?**</summary>
+</Accordion>
+<Accordion title="**Can Soroban contracts interact with any other Stellar operations?**">
 
-  No. Aside from the interactions with accounts and assets mentioned above. This
-  means that Soroban contracts cannot interact with the SDEX, claimable
-  balances, or sponsorships.
-</details>
+No. Aside from the interactions with accounts and assets mentioned above. This means that Soroban contracts cannot interact with the SDEX, claimable balances, or sponsorships.
 
-<details>
-  <summary>**Does the Stellar base reserve apply to Soroban contracts?**</summary>
+</Accordion>
+<Accordion title="**Does the Stellar base reserve apply to Soroban contracts?**">
 
-  No. Soroban has a different [fee
-  structure](../../learn/fundamentals/fees-resource-limits-metering.mdx), and
-  ledger entries that are allocated by Soroban contracts do not add to an
-  account's required minimal balance.
-</details>
+No. Soroban has a different [fee structure](../../learn/fundamentals/fees-resource-limits-metering), and ledger entries that are allocated by Soroban contracts do not add to an account's required minimal balance.
 
-<details>
-  <summary>**Need help finding what you're looking for?**</summary>
+</Accordion>
+<Accordion title="**Need help finding what you're looking for?**">
 
-  Ask in the Developer channels in the [Stellar Developer
-  Discord](https://discord.gg/stellardev).
-</details>
+Ask in the Developer channels in the [Stellar Developer Discord](https://discord.gg/stellardev).
 
-<details>
-  <summary>**Should I issue my token as a Stellar asset or a Soroban contract token?**</summary>
+</Accordion>
+<Accordion title="**Should I issue my token as a Stellar asset or a Soroban contract token?**">
 
-  To the greatest extent possible, we recommend issuing tokens as Stellar
-  assets. These tokens will benefit from being interoperable with the existing
-  tools available in the Stellar ecosystem and are more performant because the
-  Stellar Asset Contract is built into the host. Read more in the [Tokens
-  Overview](../../tokens/README.mdx).
-</details>
+To the greatest extent possible, we recommend issuing tokens as Stellar assets. These tokens will benefit from being interoperable with the existing tools available in the Stellar ecosystem and are more performant because the Stellar Asset Contract is built into the host. Read more in the [Tokens Overview](/docs/tokens).
 
-{/* prettier-ignore-end */}
+</Accordion>
+</AccordionGroup>
diff --git a/docs/data/README.mdx b/docs/data/README.mdx
deleted file mode 100644
index ee2152d43..000000000
--- a/docs/data/README.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: Data Overview
-sidebar_position: 0
----
-
-There are several products to choose from when interacting with the Stellar Network, and each one is optimized for different access patterns, so it's important to choose the right tool based on your specific use-case. These tools allow users to query network data, submit transactions, and interact with smart contracts without needing to understand the low-level details of Stellar Core.
-
-Use the summaries below to determine which types of data tools are right for your use case.
-
-## Compare Data Products
-
-SDF maintains four data products. Two are APIs and two are for bulk historical data, so start by picking the row that matches how you want to consume the data.
-
-|  | [RPC](./apis/rpc/README.mdx) | [Horizon](./apis/horizon/README.mdx) | [Hubble](./analytics/hubble/README.mdx) | [Galexie](./indexers/build-your-own/galexie/README.mdx) |
-| --- | --- | --- | --- | --- |
-| Type | API | API | Data warehouse | Ledger export tool |
-| Interface | JSON-RPC | REST | SQL (BigQuery) | XDR files in your data lake |
-| Real-time data | ✅ | ✅ | ❌ | ❌ |
-| Historical data | About 7 days | 1 year\* | Full | Full |
-| Smart contract data | ✅ | ❌ | ✅ | ✅ |
-| Transaction submission | ✅ | ✅ | ❌ | ❌ |
-| Transaction simulation | ✅ | ❌ | ❌ | ❌ |
-| Curated and parsed data | ❌ | ✅ | ✅ | ❌ |
-| Hosted by SDF | Testnet and futurenet | Mainnet, testnet, and futurenet\* | Public BigQuery dataset | None\*\* |
-
-\*_The SDF-hosted Horizon keeps one year of history and is nearing end-of-life in favor of RPC. A self-hosted Horizon can serve full history, but Hubble or Galexie are the recommended tools for that._
-
-\*\*_SDF does not host a Galexie data lake, but [several providers](./indexers/build-your-own/galexie/providers.mdx) make public ones available._
-
-The [Ingest SDK](./indexers/build-your-own/ingest-sdk/README.mdx) and [Processors](./indexers/build-your-own/processors/README.mdx) are libraries for building on top of these products rather than data products themselves. Third-party APIs, indexers, and analytics platforms are listed on their own pages in each section below.
-
-## [Analytics](./analytics/README.mdx)
-
-Explore and analyze Stellar network data to uncover trends, track activity, and generate insights for decision-making and reporting.
-
-**Why Use It:**
-
-- You want historical insights and visualizations for network activity and ecosystem health
-- You don't need to submit transactions to the network
-- You don't need real-time data
-
-## [APIs](./apis/README.mdx)
-
-Connect to the Stellar network in real-time, enabling seamless data retrieval, transaction submission, and application integration.
-
-**Why Use It:**
-
-- You want to develop applications that interact with Stellar
-- You want real-time data access and transaction submission and processing
-
-## [Indexers](./indexers/README.mdx)
-
-Organize and optimize Stellar blockchain data for efficient querying, deeper analysis, and enhanced accessibility.
-
-**Why Use It:**
-
-- You want structured and scalable access to historical and real-time blockchain data
-- You want easy access to processed and transformed raw ledger data for querying
-
-## [Oracles](./oracles/README.mdx)
-
-Integrate off-chain data with the Stellar network, enabling smart contracts and decentralized applications to interact with external information sources.
-
-**Why Use It:**
-
-- You want to use off-chain data in conjunction with Stellar smart contracts for expanded functionality and automation
diff --git a/docs/data/analytics/README.mdx b/docs/data/analytics/README.mdx
deleted file mode 100644
index 6ea95c271..000000000
--- a/docs/data/analytics/README.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: Analytics Overview
-sidebar_position: 0
----
-
-Learn about analytics and analytics providers on the Stellar network
-
-## [Hubble](./hubble/README.mdx)
-
-Hubble is an open-source, read-only BigQuery data warehouse maintained by SDF that provides a complete historical record of the Stellar network, ideal for large-scale analysis of transactions, fees, and network trends. It is not suitable for real-time data needs or simple lookups, and its documentation focuses on exploratory analysis, connection methods, and query optimization. By offering a structured and query-ready dataset, Hubble enables users to explore Stellar network data without managing raw data pipelines.
-
-Within Hubble, the stellar-etl product powers the extraction and transformation of Stellar network data into BigQuery. This open-source pipeline allows developers to extend or customize data ingestion workflows based on their analytical needs. Stellar-etl provides flexibility in how data is processed, enabling users to extract specific ledger entries, operations, or event logs based on their requirements.
-
-## [Public Dashboards](./public-dashboards.mdx)
-
-Public Dashboards is a directory of free, browser-based dashboards that track Stellar network activity, real-world assets, stablecoins, and DeFi. Most are maintained by ecosystem analytics platforms rather than SDF. Start here if you want to look at Stellar metrics without writing a query.
-
-## [Data Analytics Providers](./analytics-providers/analytics-providers.mdx)
-
-Data Analytics Providers provide a complete historical record of Pubnet Stellar network data for analysis and insights. These platforms enable users to explore network trends but are not designed for real-time data access or transaction execution. The key difference is that these ecosystem platforms operate independently of SDF and provide metrics and dashboards about the Stellar network.
diff --git a/docs/data/analytics/analytics-providers/analytics-providers.mdx b/docs/data/analytics/analytics-providers/analytics-providers.mdx
deleted file mode 100644
index df4469d5e..000000000
--- a/docs/data/analytics/analytics-providers/analytics-providers.mdx
+++ /dev/null
@@ -1,31 +0,0 @@
----
-sidebar_position: 1000
-title: Data Analytics Providers
----
-
-The following is a list of data analytics platforms that make a complete historical record of Pubnet Stellar network data available.
-
-For curated dashboards you can browse without writing queries, see the [Public Dashboards](../public-dashboards.mdx) page.
-
-| Platform | Description | Home page and Signup | Pricing | Data Access | Dashboard access |
-| --- | --- | --- | --- | --- | --- |
-| Hubble | SDF provides a publicly available raw dataset with a complete historical record of Stellar network data, updated every 15 minutes. | [Hubble](https://console.cloud.google.com/bigquery?project=crypto-stellar&ws=!1m4!1m3!3m2!1scrypto-stellar!2scrypto_stellar) <br></br> [Signup](https://cloud.google.com/?hl=en) | End users incur the cost to execute queries. Visit the [BigQuery Pricing](https://cloud.google.com/bigquery/pricing#analysis_pricing_models) page to learn more. | Please see the [Analyst Guide](./hubble/analyst-guide) for more information. | N/A |
-| Dune | Raw dataset for the Stellar network available in the Dune portal. Updated every hour. You can compare different chains on the platform. | [Dune](https://dune.com) <br></br>[Signup](https://dune.com/auth/register) | Free for simpler queries. Need to pay for complex queries. | To access datasets, click [here](https://dune.com/queries?category=canonical&namespace=stellar). | Explore community dashboards, network overview, and datasets [here](https://dune.com/blockchains/stellar). |
-| Artemis | Aggregated dataset for the Stellar network available in BigQuery as well as the Artemis portal. Provides dashboards to compare Stellar chain activity with ecosystem chains. | [Artemis](https://www.artemis.xyz) <br></br>[Signup](https://app.artemisanalytics.com/artemis-terminal-auth?flow=SIGN_UP) | Free dashboards. Need to pay for accessing the raw dataset. | For accessing Artemis-transformed Stellar dataset, upgrade to the enterprise plan and then star [this dataset](https://console.cloud.google.com/bigquery?ws=!1m4!1m3!3m2!1sartemis-bigquery-share!2sshared_us). | Explore [chain compare](https://app.artemisanalytics.com/chains?selectedChains=stellar) and [application activity](https://app.artemis.xyz/application-activity/stellar) dashboards. |
-| Nansen | Aggregated dataset for the Stellar network available in the Nansen portal. Provides dashboards to compare Stellar chain activity with ecosystem chains. | [Nansen](https://app.nansen.ai) <br></br>[Signup](https://app.nansen.ai/auth/signup) | Free dashboards. Need to pay for accessing the raw dataset. | For accessing Nansen-transformed Stellar dataset, upgrade to the Pioneer plan and then star [this dataset](https://console.cloud.google.com/bigquery?project=nansen-query). | Explore [chain activity, entity, and ecosystem](https://app.nansen.ai/macro/blockchains?chain=stellar&tab=overview). |
-| Ortege | Ortege hosts data services to make blockchain data more accessible through real time APIs and a managed [Lakehouse](https://docs.ortege.ai/en/ortege-products/ortege-lakehouse) for analytics exploration. The lakehouse follows a standardize schema across blockchains, making it easy to plug-and-play across L1s. | [Ortege](https://www.ortege.ai) <br></br>[Signup](https://app.ortege.ai/register/form) | Free for simpler queries, for larger workloads, user must purchase credits in the warehouse | Here is a [link](https://docs.ortege.ai/en/ortege-products/ortege-lakehouse/data-catalog/in-house-datasets) to their data catalog for data access. | Explore curated dashboards [here](https://app.ortege.ai/dashboard/list), or build your own |
-| Flipside | Raw dataset access to run queries, create dashboards and gain actionable intelligence on various crypto ecosystems. Flipside sponsors analytics bounties to encourage open source sharing of insights as well as developer quests. | [Flipside](https://flipsidecrypto.xyz/home) <br></br>[Signup](https://flipsidecrypto.xyz/home/sign-up) | Entire data access (raw, dashboards) is free. | To access the dataset, sign up on Flipside and find the "Stellar" database in [Flipside studio](https://flipsidecrypto.xyz/studio). | Explore [community dashboards](https://flipsidecrypto.xyz/insights/dashboards?search=stellar). |
-| DefiLlama | TVL aggregator for DeFi (Decentralized Finance). | [DefiLlama](https://defillama.com) | Free(open source) access to TVL dashboard | For data access, checkout [API Docs](https://defillama.com/docs/api) | Explore the [TVL Dashboard](https://defillama.com/chain/Stellar). |
-| Messari | Messari serves as a central hub for research and data related to the cryptoeconomy. With customizable and user-friendly features. | [Messari](https://messari.io) | Free access to dashboards and data ([subscription](https://messari.io/account/plan) for more advanced access) | For data access, checkout [API Docs](https://docs.messari.io/reference/introduction) | Explore the [Stellar Portal](https://stellar.messari.io). |
-| rwa.xyz | Aggregated information about tokenized real-world assets. | [rwa.xyz](https://www.rwa.xyz) | Free access to dashboards and general rwa information | For data access, checkout [Data & API Platform](https://app.rwa.xyz/platform-overview) | Explore the [Stellar Dashboard](https://app.rwa.xyz/networks/stellar). |
-| Token Terminal | Token Terminal is a full stack onchain data platform focused on standardizing financial and alternative data for the most widely used blockchains and decentralized applications. | [Token Terminal](https://tokenterminal.com) | Free access to dashboards. Paid [API access](https://tokenterminal.com/explorer/account/api) | For data access, checkout [API Docs](https://tokenterminal.com/docs/api-reference/introduction) | Explore the [Stellar Dashboard](https://tokenterminal.com/explorer/projects/stellar). |
-| SonarX | SonarX provides a one-stop-shop for indexed Stellar data. | [SonarX](https://www.sonarx.com) | Paid access to raw and curated datasets. | There are two products for data access, [Real-Time Data](https://www.sonarx.com/product/realtime) and [Historical Streaming](https://www.sonarx.com/product/historical) | N/A |
-| Range | The blockchain security and intelligence platform; helping the best teams build and use DeFi protocols, blockchains, rollups, and cross-chain bridges with peace of mind. | [Range](https://www.range.org) | Free access to analytics. Paid access to APIs and Security Products | Stellar has their own [Home Page](https://stellar.range.org) and we are featured on their [Stable Coin](https://stable.range.org) explorer as well. | Explore the [Stellar Dashboard](https://stellar.range.org). |
-
-{/* Allium login not working as of the writing of this doc */}
-
-{/* | Allium | Raw dataset access to the Stellar network. | [Allium](https://www.allium.so) | Free data access and queries | For data access, checkout [Allium Docs](https://docs.allium.so/) | N/A | */}
-
-## Run Your Own Hubble
-
-If you are interested in running your own Hubble, please checkout the [Developer Guide](../hubble/developer-guide/README.mdx).
diff --git a/docs/data/analytics/analytics-providers/index.mdx b/docs/data/analytics/analytics-providers/index.mdx
new file mode 100644
index 000000000..5aace0f67
--- /dev/null
+++ b/docs/data/analytics/analytics-providers/index.mdx
@@ -0,0 +1,29 @@
+---
+title: Data Analytics Providers
+description: "The following is a list of data analytics platforms that make a complete historical record of Pubnet Stellar network data available."
+---
+
+For curated dashboards you can browse without writing queries, see the [Public Dashboards](../public-dashboards) page.
+
+| Platform | Description | Home page and Signup | Pricing | Data Access | Dashboard access |
+| --- | --- | --- | --- | --- | --- |
+| Hubble | SDF provides a publicly available raw dataset with a complete historical record of Stellar network data, updated every 15 minutes. | [Hubble](https://console.cloud.google.com/bigquery?project=crypto-stellar&ws=!1m4!1m3!3m2!1scrypto-stellar!2scrypto_stellar) <br></br> [Signup](https://cloud.google.com/?hl=en) | End users incur the cost to execute queries. Visit the [BigQuery Pricing](https://cloud.google.com/bigquery/pricing#analysis_pricing_models) page to learn more. | Please see the [Analyst Guide](/docs/data/analytics/hubble/analyst-guide) for more information. | N/A |
+| Dune | Raw dataset for the Stellar network available in the Dune portal. Updated every hour. You can compare different chains on the platform. | [Dune](https://dune.com) <br></br>[Signup](https://dune.com/auth/register) | Free for simpler queries. Need to pay for complex queries. | To access datasets, click [here](https://dune.com/queries?category=canonical&namespace=stellar). | Explore community dashboards, network overview, and datasets [here](https://dune.com/blockchains/stellar). |
+| Artemis | Aggregated dataset for the Stellar network available in BigQuery as well as the Artemis portal. Provides dashboards to compare Stellar chain activity with ecosystem chains. | [Artemis](https://www.artemis.xyz) <br></br>[Signup](https://app.artemisanalytics.com/artemis-terminal-auth?flow=SIGN_UP) | Free dashboards. Need to pay for accessing the raw dataset. | For accessing Artemis-transformed Stellar dataset, upgrade to the enterprise plan and then star [this dataset](https://console.cloud.google.com/bigquery?ws=!1m4!1m3!3m2!1sartemis-bigquery-share!2sshared_us). | Explore [chain compare](https://app.artemisanalytics.com/chains?selectedChains=stellar) and [application activity](https://app.artemis.xyz/application-activity/stellar) dashboards. |
+| Nansen | Aggregated dataset for the Stellar network available in the Nansen portal. Provides dashboards to compare Stellar chain activity with ecosystem chains. | [Nansen](https://app.nansen.ai) <br></br>[Signup](https://app.nansen.ai/auth/signup) | Free dashboards. Need to pay for accessing the raw dataset. | For accessing Nansen-transformed Stellar dataset, upgrade to the Pioneer plan and then star [this dataset](https://console.cloud.google.com/bigquery?project=nansen-query). | Explore [chain activity, entity, and ecosystem](https://app.nansen.ai/macro/blockchains?chain=stellar&tab=overview). |
+| Ortege | Ortege hosts data services to make blockchain data more accessible through real time APIs and a managed [Lakehouse](https://docs.ortege.ai/en/ortege-products/ortege-lakehouse) for analytics exploration. The lakehouse follows a standardize schema across blockchains, making it easy to plug-and-play across L1s. | [Ortege](https://www.ortege.ai) <br></br>[Signup](https://app.ortege.ai/register/form) | Free for simpler queries, for larger workloads, user must purchase credits in the warehouse | Here is a [link](https://docs.ortege.ai/en/ortege-products/ortege-lakehouse/data-catalog/in-house-datasets) to their data catalog for data access. | Explore curated dashboards [here](https://app.ortege.ai/dashboard/list), or build your own |
+| Flipside | Raw dataset access to run queries, create dashboards and gain actionable intelligence on various crypto ecosystems. Flipside sponsors analytics bounties to encourage open source sharing of insights as well as developer quests. | [Flipside](https://flipsidecrypto.xyz/home) <br></br>[Signup](https://flipsidecrypto.xyz/home/sign-up) | Entire data access (raw, dashboards) is free. | To access the dataset, sign up on Flipside and find the "Stellar" database in [Flipside studio](https://flipsidecrypto.xyz/studio). | Explore [community dashboards](https://flipsidecrypto.xyz/insights/dashboards?search=stellar). |
+| DefiLlama | TVL aggregator for DeFi (Decentralized Finance). | [DefiLlama](https://defillama.com) | Free(open source) access to TVL dashboard | For data access, checkout [API Docs](https://defillama.com/docs/api) | Explore the [TVL Dashboard](https://defillama.com/chain/Stellar). |
+| Messari | Messari serves as a central hub for research and data related to the cryptoeconomy. With customizable and user-friendly features. | [Messari](https://messari.io) | Free access to dashboards and data ([subscription](https://messari.io/account/plan) for more advanced access) | For data access, checkout [API Docs](https://docs.messari.io/reference/introduction) | Explore the [Stellar Portal](https://stellar.messari.io). |
+| rwa.xyz | Aggregated information about tokenized real-world assets. | [rwa.xyz](https://www.rwa.xyz) | Free access to dashboards and general rwa information | For data access, checkout [Data & API Platform](https://app.rwa.xyz/platform-overview) | Explore the [Stellar Dashboard](https://app.rwa.xyz/networks/stellar). |
+| Token Terminal | Token Terminal is a full stack onchain data platform focused on standardizing financial and alternative data for the most widely used blockchains and decentralized applications. | [Token Terminal](https://tokenterminal.com) | Free access to dashboards. Paid [API access](https://tokenterminal.com/explorer/account/api) | For data access, checkout [API Docs](https://tokenterminal.com/docs/api-reference/introduction) | Explore the [Stellar Dashboard](https://tokenterminal.com/explorer/projects/stellar). |
+| SonarX | SonarX provides a one-stop-shop for indexed Stellar data. | [SonarX](https://www.sonarx.com) | Paid access to raw and curated datasets. | There are two products for data access, [Real-Time Data](https://www.sonarx.com/product/realtime) and [Historical Streaming](https://www.sonarx.com/product/historical) | N/A |
+| Range | The blockchain security and intelligence platform; helping the best teams build and use DeFi protocols, blockchains, rollups, and cross-chain bridges with peace of mind. | [Range](https://www.range.org) | Free access to analytics. Paid access to APIs and Security Products | Stellar has their own [Home Page](https://stellar.range.org) and we are featured on their [Stable Coin](https://stable.range.org) explorer as well. | Explore the [Stellar Dashboard](https://stellar.range.org). |
+
+{/* Allium login not working as of the writing of this doc */}
+
+{/* | Allium | Raw dataset access to the Stellar network. | [Allium](https://www.allium.so) | Free data access and queries | For data access, checkout [Allium Docs](https://docs.allium.so/) | N/A | */}
+
+## Run Your Own Hubble
+
+If you are interested in running your own Hubble, please checkout the [Developer Guide](/docs/data/analytics/hubble/developer-guide).
diff --git a/docs/data/analytics/hubble/README.mdx b/docs/data/analytics/hubble/README.mdx
deleted file mode 100644
index 575856930..000000000
--- a/docs/data/analytics/hubble/README.mdx
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: Hubble
-sidebar_position: 0
----
-
-## What is Hubble?
-
-Hubble is an open-source, publicly available dataset that provides a complete historical record of the Stellar network. It ingests and presents the data produced by the Stellar network in a format that is easier to consume than the performance-oriented data representations used by Stellar Core. The dataset is hosted on BigQuery–meaning it is suitable for large, analytic workloads, historical data retrieval and complex data aggregation. **Hubble should not be used for real-time data retrieval and cannot submit transactions to the network.** For real time use cases, we recommend [running an API server](../../apis/rpc/admin-guide/README.mdx).
-
-This guide describes when to use Hubble and how to connect. To view the underlying data structures, queries and examples, use the [Viewing Metadata](./analyst-guide/viewing-metadata.mdx) and [Optimizing Queries](./analyst-guide/optimizing-queries.mdx) tutorials.
-
-## Why Use Hubble?
-
-Some questions are hard to answer with the RPC API as its API is quite minimal. This is because its infrastructure is optimized for quick reads and writes so that it can process online transactions.
-
-This is where Hubble comes in. It is optimized to execute complex queries and scan large amounts of data. Hubble can store orders of magnitude more data than RPC and will not run into storage constraints. Queries that require pagination in RPC or timeout can be returned in a single query. Hubble empowers users to explore, analyze, and derive meaningful conclusions from the data without the burden of maintaining a database.
-
-Users should be aware of the following limitations:
-
-- Hubble is read-only; it cannot interact with the Stellar Network.
-- The database is updated in intraday batches. There is no guarantee for same-day data availability.
-- The SDF hosts a public instance of Hubble, and end users incur the cost to execute queries. Visit the [BigQuery Pricing Page](https://cloud.google.com/bigquery/pricing#analysis_pricing_models) to learn more.
-
-## Why We Chose BigQuery
-
-BigQuery is Google Cloud’s data warehouse that comes with some key features that fulfill Stellar’s analytic needs.
-
-First, BigQuery allows anyone to make a dataset publicly available. This means that the SDF can contribute open source repositories to build and maintain a data warehouse and also host a public instance.
-
-BigQuery also separates storage from compute, which makes it sustainable to host a public instance. The maintainer only has to pay the cost of storage without incurring the cost of the analytics running on the dataset.
-
-Most importantly, BigQuery is the de facto platform for blockchain datasets. By selecting BigQuery, Stellar Network data is located with other blockchain data, which allows for cross-chain analytics.
diff --git a/docs/data/analytics/hubble/analyst-guide/README.mdx b/docs/data/analytics/hubble/analyst-guide/README.mdx
deleted file mode 100644
index be6450ba0..000000000
--- a/docs/data/analytics/hubble/analyst-guide/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Analyst Guide
-sidebar_position: 15
----
-
-import DocCardList from "@theme/DocCardList";
-
-All you need to know to use Hubble data for analysis.
-
-<DocCardList />
diff --git a/docs/data/analytics/hubble/analyst-guide/_category_.json b/docs/data/analytics/hubble/analyst-guide/_category_.json
deleted file mode 100644
index 9e3a55f45..000000000
--- a/docs/data/analytics/hubble/analyst-guide/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": true
-}
diff --git a/docs/data/analytics/hubble/analyst-guide/connecting.mdx b/docs/data/analytics/hubble/analyst-guide/connecting.mdx
index a1e79f9f5..593598509 100644
--- a/docs/data/analytics/hubble/analyst-guide/connecting.mdx
+++ b/docs/data/analytics/hubble/analyst-guide/connecting.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Connecting"
-sidebar_position: 10
+description: "BigQuery offers multiple connection methods to Hubble."
 ---
 
 BigQuery offers multiple connection methods to Hubble. This guide details three common methods:
@@ -21,17 +21,17 @@ Google does provide a BigQuery Sandbox for free that allows users to explore dat
 2. This will open the public dataset `crypto_stellar`, where you can browse its contents in the **Explorer** pane.
 3. Click the **star** icon in the Explorer pane. This will favorite the dataset for you. More detailed information about starring resources can be found [here](https://cloud.google.com/bigquery/docs/bigquery-web-ui#star_resources).
 
-:::note
+<Note>
 
 Hubble cannot be found from the Explorer pane! You cannot search for the dataset. To view the dataset, you **must** use the [dataset link](https://console.cloud.google.com/bigquery?ws=!1m4!1m3!3m2!1scrypto-stellar!2scrypto_stellar).
 
-:::
+</Note>
 
 Copy and paste the following example query in the Editor:
 
-<CodeExample>
+<CodeGroup>
 
-```sql
+```sql SQL
 select
   account_id,
   balance
@@ -39,7 +39,7 @@ from `crypto-stellar.crypto_stellar.accounts_current`
 order by balance desc;
 ```
 
-</CodeExample>
+</CodeGroup>
 
 This query will return the XLM balances for all Stellar wallet addresses, ordered from largest to smallest amounts.
 
@@ -51,9 +51,9 @@ The following example uses Python to access the Hubble dataset. Use [this guide]
 
 Install the client library locally, and configure your environment to use your Google Cloud Project:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 # verify python version
 python3 --version
 # if you do not have pip, install it
@@ -64,13 +64,13 @@ pip install --upgrade google-cloud-bigquery
 gcloud config set project PROJECT_ID
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Use the Python Interpreter to run the example below to list the tables available in Hubble:
 
-<CodeExample>
+<CodeGroup>
 
-```python
+```python Python
 from google.cloud import bigquery
 
 # Construct a BigQuery client object.
@@ -87,13 +87,13 @@ for table in tables:
     print(f'{table.project}.{table.dataset_id}.{table.table_id}')
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Run the example below to run a query and print the results:
 
-<CodeExample>
+<CodeGroup>
 
-```python
+```python Python
 from google.cloud import bigquery
 
 # Construct a BigQuery client object.
@@ -117,7 +117,7 @@ for row in query_job:
     print(f'account_id={row[0]}, balance={row["balance"]}')
 ```
 
-</CodeExample>
+</CodeGroup>
 
 There are various ways to extract and load data using BigQuery. See the [BigQuery Client Documentation](https://cloud.google.com/python/docs/reference/bigquery/latest/google.cloud.bigquery.client.Client) for more information.
 
diff --git a/docs/data/analytics/hubble/analyst-guide/creating-visualizations.mdx b/docs/data/analytics/hubble/analyst-guide/creating-visualizations.mdx
index a50046ffb..9ef0683b8 100644
--- a/docs/data/analytics/hubble/analyst-guide/creating-visualizations.mdx
+++ b/docs/data/analytics/hubble/analyst-guide/creating-visualizations.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Creating Visualizations"
-sidebar_position: 40
+description: "This page will show how you can create visualizations with Hubble and Google Looker Studio."
 ---
 
 This page will show how you can create visualizations with Hubble and [Google Looker Studio](https://cloud.google.com/looker-studio?hl=en).
@@ -9,13 +9,13 @@ By the end of the tutorial you will have created two graphs that will help visua
 
 <img src="/img/hubble/hubble_visualization_demo.gif" width="1000" alt="Demo" />
 
-As you can see, persistent contract data entries account for roughly 25% of all contract data entries with the rest being temporary. There are also a lot more expired temporary contract data entries. This is expected because temporay entries cannot be bumped whereas persistent entries can be bumped/restored. For more information, you can read about [State Archival and the Contract Data Lifecycle](../../../../learn/fundamentals/contract-development/storage/state-archival.mdx#contract-data-type-descriptions).
+As you can see, persistent contract data entries account for roughly 25% of all contract data entries with the rest being temporary. There are also a lot more expired temporary contract data entries. This is expected because temporay entries cannot be bumped whereas persistent entries can be bumped/restored. For more information, you can read about [State Archival and the Contract Data Lifecycle](../../../../learn/fundamentals/contract-development/storage/state-archival#contract-data-type-descriptions).
 
 ## Prerequisites
 
-1. Make sure you have connected to Hubble by following the instructions in the [Connecting](../developer-guide/connecting-to-bigquery/README.mdx) page
+1. Make sure you have connected to Hubble by following the instructions in the [Connecting](/docs/data/analytics/hubble/developer-guide/connecting-to-bigquery) page
 2. You have access to [Google Looker Studio](https://cloud.google.com/looker-studio?hl=en)
-3. You have read and understand the general [Best Practices](./optimizing-queries.mdx#best-practices) for querying BigQuery data
+3. You have read and understand the general [Best Practices](./optimizing-queries#best-practices) for querying BigQuery data
 
 ## Create a Report in Looker Studio
 
diff --git a/docs/data/analytics/hubble/analyst-guide/history-vs-state-tables.mdx b/docs/data/analytics/hubble/analyst-guide/history-vs-state-tables.mdx
index 07bb810d4..a0949db09 100644
--- a/docs/data/analytics/hubble/analyst-guide/history-vs-state-tables.mdx
+++ b/docs/data/analytics/hubble/analyst-guide/history-vs-state-tables.mdx
@@ -1,6 +1,6 @@
 ---
 title: "History VS State Tables"
-sidebar_position: 60
+description: "This page describes the differences between History and State tables within Hubble."
 ---
 
 This page describes the differences between History and State tables within Hubble.
@@ -29,14 +29,14 @@ As seen in the table, each row shows the `balance` of `DUMMYACCOUNT` at a sepeci
 
 ### List of state tables
 
-- [Accounts](../data-catalog/data-dictionary/bronze/accounts.mdx)
-- [Claimable Balances](../data-catalog/data-dictionary/bronze/claimable-balances.mdx)
-- [Contract Code](../data-catalog/data-dictionary/bronze/contract-code.mdx)
-- [Contract Data](../data-catalog/data-dictionary/bronze/contract-data.mdx)
-- [Liquidity Pools](../data-catalog/data-dictionary/bronze/liquidity-pools.mdx)
-- [Offers](../data-catalog/data-dictionary/bronze/offers.mdx)
-- [Trustlines](../data-catalog/data-dictionary/bronze/trustlines.mdx)
-- [TTL](../data-catalog/data-dictionary/bronze/ttl.mdx)
+- [Accounts](../data-catalog/data-dictionary/bronze/accounts)
+- [Claimable Balances](../data-catalog/data-dictionary/bronze/claimable-balances)
+- [Contract Code](../data-catalog/data-dictionary/bronze/contract-code)
+- [Contract Data](../data-catalog/data-dictionary/bronze/contract-data)
+- [Liquidity Pools](../data-catalog/data-dictionary/bronze/liquidity-pools)
+- [Offers](../data-catalog/data-dictionary/bronze/offers)
+- [Trustlines](../data-catalog/data-dictionary/bronze/trustlines)
+- [TTL](../data-catalog/data-dictionary/bronze/ttl)
 
 ## What are history tables?
 
@@ -59,11 +59,11 @@ As seen in the table, each row shows the distinct operation with its unique `id`
 
 ### List of history tables
 
-- [History Assets](../data-catalog/data-dictionary/bronze/history-assets.mdx)
-- [History Contract Events](../data-catalog/data-dictionary/bronze/history-contract-events.mdx)
-- [History Effects](../data-catalog/data-dictionary/bronze/history-effects.mdx)
-- [History Ledgers](../data-catalog/data-dictionary/bronze/history-ledgers.mdx)
-- [History Operations](../data-catalog/data-dictionary/bronze/history-operations.mdx)
-- [History Trades](../data-catalog/data-dictionary/bronze/history-trades.mdx)
-- [History Transactions](../data-catalog/data-dictionary/bronze/history-transactions.mdx)
-- [Enriched History Operations](../data-catalog/data-dictionary/silver/enriched-history-operations.mdx)
+- [History Assets](../data-catalog/data-dictionary/bronze/history-assets)
+- [History Contract Events](../data-catalog/data-dictionary/bronze/history-contract-events)
+- [History Effects](../data-catalog/data-dictionary/bronze/history-effects)
+- [History Ledgers](../data-catalog/data-dictionary/bronze/history-ledgers)
+- [History Operations](../data-catalog/data-dictionary/bronze/history-operations)
+- [History Trades](../data-catalog/data-dictionary/bronze/history-trades)
+- [History Transactions](../data-catalog/data-dictionary/bronze/history-transactions)
+- [Enriched History Operations](../data-catalog/data-dictionary/silver/enriched-history-operations)
diff --git a/docs/data/analytics/hubble/analyst-guide/index.mdx b/docs/data/analytics/hubble/analyst-guide/index.mdx
new file mode 100644
index 000000000..f3bc53b6e
--- /dev/null
+++ b/docs/data/analytics/hubble/analyst-guide/index.mdx
@@ -0,0 +1,37 @@
+---
+title: Analyst Guide
+description: "All you need to know to use Hubble data for analysis."
+---
+
+<CardGroup cols={2}>
+  <Card title="Connecting" icon="file-lines" href="/docs/data/analytics/hubble/analyst-guide/connecting">
+
+    BigQuery offers multiple connection methods to Hubble.
+
+  </Card>
+  <Card title="Viewing Metadata" icon="file-lines" href="/docs/data/analytics/hubble/analyst-guide/viewing-metadata">
+
+    Hubble publishes metadata which can help users determine which tables to query, how frequently the dataset updates, and general information about the dataset.
+
+  </Card>
+  <Card title="Optimizing Queries" icon="file-lines" href="/docs/data/analytics/hubble/analyst-guide/optimizing-queries">
+
+    Hubble has terabytes of data to explore&mdash;that’s a lot of data!
+
+  </Card>
+  <Card title="Creating Visualizations" icon="file-lines" href="/docs/data/analytics/hubble/analyst-guide/creating-visualizations">
+
+    This page will show how you can create visualizations with Hubble and Google Looker Studio.
+
+  </Card>
+  <Card title="Queries for Horizon/RPC-like Data" icon="file-lines" href="/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data">
+
+    Horizon and RPC both provide API endpoints to retrieve data from the Stellar network.
+
+  </Card>
+  <Card title="History VS State Tables" icon="file-lines" href="/docs/data/analytics/hubble/analyst-guide/history-vs-state-tables">
+
+    This page describes the differences between History and State tables within Hubble.
+
+  </Card>
+</CardGroup>
diff --git a/docs/data/analytics/hubble/analyst-guide/optimizing-queries.mdx b/docs/data/analytics/hubble/analyst-guide/optimizing-queries.mdx
index 5f73d739e..34b170f27 100644
--- a/docs/data/analytics/hubble/analyst-guide/optimizing-queries.mdx
+++ b/docs/data/analytics/hubble/analyst-guide/optimizing-queries.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Optimizing Queries"
-sidebar_position: 30
+description: "Hubble has terabytes of data to explore&mdash;that’s a lot of data!"
 ---
 
 Hubble has terabytes of data to explore&mdash;that’s a lot of data! With access to so much data at your fingertips, it is crucial to performance-tune your queries.
@@ -15,15 +15,15 @@ Large tables are partitioned and clustered according to common access patterns.
 
 Joining tables on strings is expensive. Refrain from joining on string keys if you can utilize integer keys instead.
 
-Read the docs on [Viewing Metadata](./viewing-metadata.mdx) to learn more about table metadata.
+Read the docs on [Viewing Metadata](./viewing-metadata) to learn more about table metadata.
 
-#### Example - Profiling Operation Types
+#### Example - Profiling Operation Types {#example---profiling-operation-types}
 
-Let’s say you wanted to profile the [types of operations](../../../../learn/fundamentals/transactions/list-of-operations.mdx) submitted to the Stellar Network monthly. ======== Let’s say you wanted to profile the [types of operations](../../../../learn/fundamentals/transactions/list-of-operations.mdx) submitted to the Stellar Network monthly.
+Let’s say you wanted to profile the [types of operations](../../../../learn/fundamentals/transactions/list-of-operations) submitted to the Stellar Network monthly. ======== Let’s say you wanted to profile the [types of operations](../../../../learn/fundamentals/transactions/list-of-operations) submitted to the Stellar Network monthly.
 
-<CodeExample>
+<CodeGroup>
 
-```sql
+```sql SQL
 # Inefficient query
 select datetime_trunc(batch_run_date, month) as `month`,
   type_string,
@@ -34,13 +34,13 @@ group by `month`,
 order by `month`
 ```
 
-</CodeExample>
+</CodeGroup>
 
 The `history_operations` table is partitioned by `batch_run_date` and clustered by `transaction_id`, `source_account` and `type`. Query costs are greatly reduced by pruning unused partitions. In this case, you could filter out operations submitted before 2023. This reduces the query cost by 4x.
 
-<CodeExample>
+<CodeGroup>
 
-```sql
+```sql SQL
 # Prune out partitions you do not need
 select datetime_trunc(batch_run_date, month) as `month`,
   type_string,
@@ -53,13 +53,13 @@ group by `month`,
 order by `month`
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Switching the aggregation field to `type`, which is a clustered field, will cut costs by a third:
 
-<CodeExample>
+<CodeGroup>
 
-```sql
+```sql SQL
 # Prune out partitions you do not need
 # Aggregate by clustered field, `type`
 select datetime_trunc(batch_run_date, month) as `month`,
@@ -72,7 +72,7 @@ group by `month`,
 order by `month`
 ```
 
-</CodeExample>
+</CodeGroup>
 
 **Performance Summary**
 
@@ -88,13 +88,13 @@ By pruning partitions and aggregating on a clustered field, the query processing
 
 Do not write `SELECT *` statements unless you need every column returned in the query response. Since BigQuery is a columnar database, it can skip reading data entirely if the columns are not included in the select statement. The wider the table is, the more crucial it is to select _only_ what you need.
 
-#### Example - Transaction Fees
+#### Example - Transaction Fees {#example---transaction-fees}
 
 Let’s say you needed to view the fees for all transactions submitted in May 2023. What happens if you write a `SELECT *`?
 
-<CodeExample>
+<CodeGroup>
 
-```sql
+```sql SQL
 # Inefficient query
 select *
 from `crypto-stellar.crypto_stellar.history_transactions`
@@ -102,15 +102,15 @@ where batch_run_date >= '2023-05-01'
   and batch_run_date < '2023-06-01'
 ```
 
-</CodeExample>
+</CodeGroup>
 
 This query is estimated to cost almost $4!
 
 If you only need fee information, you can filter down the data, reducing the query costs by a factor of 50x:
 
-<CodeExample>
+<CodeGroup>
 
-```sql
+```sql SQL
 # Select only the columns you need
 select id,
   transaction_hash,
@@ -125,7 +125,7 @@ where batch_run_date >= '2023-05-01'
   and batch_run_date < '2023-06-01'
 ```
 
-</CodeExample>
+</CodeGroup>
 
 **Performance Summary**
 
@@ -136,21 +136,21 @@ Hubble stores wide tables. Query performance is greatly improved by selecting on
 | Original Query | 769.45 GB       | $3.847 |
 | Improved Query | 16.6 GB         | $0.083 |
 
-:::tip
+<Tip>
 
 The BigQuery console lets you preview table data for free, which is the equivalent of writing a `SELECT *`. Click on the table name, and pull up the preview pane.
 
-:::
+</Tip>
 
 ### Filter early.
 
 When writing complex queries, filter the data as early as possible. Push `WHERE` and `GROUP BY` clauses up in the query to reduce the amount of data scanned.
 
-:::caution
+<Warning>
 
 `LIMIT` clauses speed up performance, but **do not** reduce the amount of data scanned. Only the _final_ results returned to the user are limited. Use with caution.
 
-:::
+</Warning>
 
 Push transformations and mathematical functions to the end of the query when possible. Functions like `TRIM()`, `CAST()`, `SUM()`, and `REGEXP_*` are resource intensive and should only be applied to final table results.
 
@@ -168,9 +168,9 @@ To calculate the query cost, convert the number of bytes processed into terabyte
 
 Paste the following query into the Editor to view the estimated bytes processed.
 
-<CodeExample>
+<CodeGroup>
 
-```sql
+```sql SQL
 select timestamp_trunc(closed_at, month) as month,
   sum(tx_set_operation_count) as total_operations
 from `crypto-stellar.crypto_stellar.history_ledgers`
@@ -181,7 +181,7 @@ where batch_run_date >= '2023-01-01T00:00:00'
 group by month
 ```
 
-</CodeExample>
+</CodeGroup>
 
 The validator estimates that 51.95MB of data will be read.
 
@@ -191,9 +191,9 @@ The validator estimates that 51.95MB of data will be read.
 
 If you are submitting a query through a [BigQuery client library](https://cloud.google.com/bigquery/docs/reference/libraries), you can perform a dry run to estimate the total bytes processed before submitting the query job.
 
-<CodeExample>
+<CodeGroup>
 
-```python
+```python Python
 from google.cloud import bigquery
 
 # Construct a BigQuery client object
@@ -224,7 +224,7 @@ print(f'This query will process {query_job.total_bytes_processed} bytes')
 print(f'This query will cost approximately ${cost}')
 ```
 
-</CodeExample>
+</CodeGroup>
 
 There are also [IDE plugins](https://plugins.jetbrains.com/plugin/15884-bigquery-query-size-estimator) that can approximate cost.
 
diff --git a/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx b/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx
index ab1db0071..0314f336c 100644
--- a/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx
+++ b/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx
@@ -1,17 +1,17 @@
 ---
 title: "Queries for Horizon/RPC-like Data"
-sidebar_position: 50
+description: "Horizon and RPC both provide API endpoints to retrieve data from the Stellar network. The following example queries retrieve the same data by using Hubble with the added benefit of being able to return historical data."
 ---
 
-[Horizon](../../../apis/horizon/README.mdx) and [RPC](../../../apis/rpc/README.mdx) both provide API endpoints to retrieve data from the Stellar network. The following example queries retrieve the same data by using Hubble with the added benefit of being able to return historical data.
+[Horizon](/docs/data/apis/horizon) and [RPC](/docs/data/apis/rpc) both provide API endpoints to retrieve data from the Stellar network. The following example queries retrieve the same data by using Hubble with the added benefit of being able to return historical data.
 
 ## Accounts
 
-[horizon/accounts](../../../apis/horizon/api-reference/resources/accounts/README.mdx)
+[horizon/accounts](/docs/data/apis/horizon/api-reference/resources/accounts)
 
 Users interact with the Stellar network through accounts. Everything else in the ledger—assets, offers, trustlines, etc.—are owned by accounts, and accounts must authorize all changes to the ledger through signed transactions.
 
-Learn more about [accounts](../../../../learn/glossary.mdx#account).
+Learn more about [accounts](../../../../learn/glossary#account).
 
 ### General account information and XLM balance
 
@@ -81,7 +81,7 @@ where true
 limit 1000
 ```
 
-### Retrieve an Account’s Transactions
+### Retrieve an Account’s Transactions {#retrieve-an-accounts-transactions}
 
 ```sql
 select
@@ -101,7 +101,7 @@ where true
 limit 1000
 ```
 
-### Retrieve an Account’s Operations
+### Retrieve an Account’s Operations {#retrieve-an-accounts-operations}
 
 ```sql
 select
@@ -120,7 +120,7 @@ where true
 limit 1000
 ```
 
-### Retrieve an Account’s Payments
+### Retrieve an Account’s Payments {#retrieve-an-accounts-payments}
 
 ```sql
 select
@@ -147,7 +147,7 @@ where true
 limit 1000
 ```
 
-### Retrieve an Account’s Effects
+### Retrieve an Account’s Effects {#retrieve-an-accounts-effects}
 
 ```sql
 select
@@ -172,7 +172,7 @@ where true
 limit 1000
 ```
 
-### Retrieve an Account’s Offers
+### Retrieve an Account’s Offers {#retrieve-an-accounts-offers}
 
 ```sql
 select
@@ -188,7 +188,7 @@ where true
   and seller_id=<account_id>
 ```
 
-### Retrieve an Account’s Trades
+### Retrieve an Account’s Trades {#retrieve-an-accounts-trades}
 
 ```sql
 with selling_side as (
@@ -244,11 +244,11 @@ select * from union_data
 
 ## Assets
 
-[horizon/assets](../../../apis/horizon/api-reference/resources/assets/README.mdx)
+[horizon/assets](/docs/data/apis/horizon/api-reference/resources/assets)
 
 Assets are representations of value issued on the Stellar network. An asset consists of a type, code, and issuer.
 
-Learn more about [assets](../../../../learn/glossary.mdx#asset).
+Learn more about [assets](../../../../learn/glossary#asset).
 
 ### List all Assets
 
@@ -334,7 +334,7 @@ where true
 
 ## Claimable Balances
 
-[horizon/claimable_balances](../../../apis/horizon/api-reference/resources/claimablebalances/README.mdx)
+[horizon/claimable_balances](/docs/data/apis/horizon/api-reference/resources/claimablebalances)
 
 A Claimable Balance represents the transfer of ownership of some amount of an asset. Claimable balances provide a mechanism for setting up a payment which can be claimed in the future. This allows you to make payments to accounts which are currently not able to accept them.
 
@@ -427,7 +427,7 @@ where true
 
 ## Effects
 
-[horizon/effects](../../../apis/horizon/api-reference/resources/effects/README.mdx)
+[horizon/effects](/docs/data/apis/horizon/api-reference/resources/effects)
 
 Effects represent specific changes that occur in the ledger as a result of successful operations, but are not necessarily directly reflected in the ledger or history, as transactions and operations are.
 
@@ -450,11 +450,11 @@ where true
 
 ## Ledgers
 
-[horizon/ledgers](../../../apis/horizon/api-reference/resources/ledgers/README.mdx)
+[horizon/ledgers](/docs/data/apis/horizon/api-reference/resources/ledgers)
 
 Each ledger stores the state of the network at a point in time and contains all the changes - transactions, operations, effects, etc. - to that state.
 
-Learn more about [ledgers](../../../../learn/glossary.mdx#ledger).
+Learn more about [ledgers](../../../../learn/glossary#ledger).
 
 ### List All Ledgers
 
@@ -468,7 +468,7 @@ where true
   and closed_at between <start> and <end>
 ```
 
-### Retrieve a Ledger’s Transactions and Operations
+### Retrieve a Ledger’s Transactions and Operations {#retrieve-a-ledgers-transactions-and-operations}
 
 ```sql
 select
@@ -481,7 +481,7 @@ where true
   and closed_at between <start> and <end>
 ```
 
-### Retrieve a Ledger’s Payments
+### Retrieve a Ledger’s Payments {#retrieve-a-ledgers-payments}
 
 ```sql
 select
@@ -497,7 +497,7 @@ where true
 
 ## Liquidity Pools
 
-[horizon/liquidity_pools](../../../apis/horizon/api-reference/resources/liquiditypools/README.mdx)
+[horizon/liquidity_pools](/docs/data/apis/horizon/api-reference/resources/liquiditypools)
 
 Liquidity Pools provide a simple, non-interactive way to trade large amounts of capital and enable high volumes of trading.
 
@@ -532,7 +532,7 @@ where true
   and liquidity_pool_id = <liquidity_pool_id>
 ```
 
-### Retrieve a Liquidity Pool’s Transactions and Operations
+### Retrieve a Liquidity Pool’s Transactions and Operations {#retrieve-a-liquidity-pools-transactions-and-operations}
 
 ```sql
 select
@@ -544,7 +544,7 @@ where true
   and liquidity_pool_id = <liquidity_pool_id>
 ```
 
-### Retrieve a Liquidity Pool’s Related Trades
+### Retrieve a Liquidity Pool’s Related Trades {#retrieve-a-liquidity-pools-related-trades}
 
 ```sql
 select
@@ -559,11 +559,11 @@ where true
 
 ## Offers
 
-[horizon/offers](../../../apis/horizon/api-reference/resources/offers/README.mdx)
+[horizon/offers](/docs/data/apis/horizon/api-reference/resources/offers)
 
 Offers are statements about how much of an asset an account wants to buy or sell.
 
-Learn more about [offers](../../../../learn/glossary.mdx#decentralized-exchange).
+Learn more about [offers](../../../../learn/glossary#decentralized-exchange).
 
 ### List All Offers
 
@@ -598,7 +598,7 @@ where true
   and closed_at between <start> and <end>
 ```
 
-### Retrieve an Offer’s Trades
+### Retrieve an Offer’s Trades {#retrieve-an-offers-trades}
 
 ```sql
 select
@@ -614,7 +614,7 @@ where true
 
 ## Operations
 
-[horizon/operations](../../../apis/horizon/api-reference/resources/operations/README.mdx)
+[horizon/operations](/docs/data/apis/horizon/api-reference/resources/operations)
 
 Operations are objects that represent a desired change to the ledger: payments, offers to exchange currency, changes made to account options, etc. Operations are submitted to the Stellar network grouped in a Transaction.
 
@@ -670,7 +670,7 @@ where true
   and closed_at between <start> and <end>
 ```
 
-### Retrieve an Operation’s Effects
+### Retrieve an Operation’s Effects {#retrieve-an-operations-effects}
 
 ```sql
 select
@@ -685,13 +685,13 @@ where true
 
 ## Trades
 
-[horizon/trades](../../../apis/horizon/api-reference/resources/trades/README.mdx)
+[horizon/trades](/docs/data/apis/horizon/api-reference/resources/trades)
 
 When an offer is fully or partially fulfilled, a trade happens. Trades can also be caused by successful path payments, because path payments involve fulfilling offers.
 
 A trade occurs between two parties—`base` and `counter`. Which is which is either arbitrary or determined by the calling query.
 
-Learn more about [trades](../../../../learn/glossary.mdx#decentralized-exchange).
+Learn more about [trades](../../../../learn/glossary#decentralized-exchange).
 
 ### List All Trades
 
@@ -721,11 +721,11 @@ where true
 
 ## Transactions
 
-[horizon/transactions](../../../apis/horizon/api-reference/resources/transactions/README.mdx)
+[horizon/transactions](/docs/data/apis/horizon/api-reference/resources/transactions)
 
 Transactions are commands that modify the ledger state and consist of one or more operations.
 
-Learn more about [transactions](../../../../learn/glossary.mdx#transaction).
+Learn more about [transactions](../../../../learn/glossary#transaction).
 
 ### List All Transactions
 
@@ -761,7 +761,7 @@ where true
   and closed_at between <start> and <end>
 ```
 
-### Retrieve a Transaction’s Operations
+### Retrieve a Transaction’s Operations {#retrieve-a-transactions-operations}
 
 ```sql
 select
@@ -781,7 +781,7 @@ where true
 
 ## Trade Aggregations
 
-[horizon/trade_aggregations](../../../apis/horizon/api-reference/aggregations/trade-aggregations/README.mdx)
+[horizon/trade_aggregations](/docs/data/apis/horizon/api-reference/aggregations/trade-aggregations)
 
 A trade aggregation represents aggregated statistics on an asset pair (base and counter) for a specific time period. Trade aggregations are useful to developers of trading clients and provide historical trade data.
 
@@ -809,7 +809,7 @@ group by 1,2,3,4,5
 
 ## Fee Stats
 
-[horizon/fee-stats](../../../apis/horizon/api-reference/aggregations/fee-stats/README.mdx)
+[horizon/fee-stats](/docs/data/apis/horizon/api-reference/aggregations/fee-stats)
 
 Fee stats are used to predict what fee to set for a transaction before submitting it to the network. Two models are available: `ledger_fee_stats_agg` (ledger-grain) and `daily_fee_stats_agg` (daily-grain). Both provide separate Classic and Soroban fee breakdowns, inclusion fee metrics, and surge pricing statistics.
 
@@ -865,7 +865,7 @@ where true
 
 ## getEvents
 
-[rpc/getEvents](../../../apis/rpc/api-reference/methods/getEvents.mdx)
+[rpc/getEvents](../../../apis/rpc/api-reference/methods/getEvents)
 
 Contract events and diagnostic events are used for supplemental information related to a contract invocation
 
@@ -883,7 +883,7 @@ where true
 
 ## getLedgerEntries
 
-[rpc/getLedgerEntries](../../../apis/rpc/api-reference/methods/getLedgerEntries.mdx)
+[rpc/getLedgerEntries](../../../apis/rpc/api-reference/methods/getLedgerEntries)
 
 Enables the retrieval of various ledger states, such as accounts, trustlines, offers, data, claimable balances, and liquidity pools. It also provides direct access to inspect a contract's current state, its code, or any other ledger entry
 
@@ -913,11 +913,11 @@ where true
 
 ## getTransaction
 
-[rpc/getTransaction](../../../apis/rpc/api-reference/methods/getTransaction.mdx)
+[rpc/getTransaction](../../../apis/rpc/api-reference/methods/getTransaction)
 
 Transactions are commands that modify the ledger state and consist of one or more operations.
 
-Learn more about [transactions](../../../../learn/glossary.mdx#transaction).
+Learn more about [transactions](../../../../learn/glossary#transaction).
 
 ```sql
 select
diff --git a/docs/data/analytics/hubble/analyst-guide/viewing-metadata.mdx b/docs/data/analytics/hubble/analyst-guide/viewing-metadata.mdx
index bbd3717b9..6e62f99d5 100644
--- a/docs/data/analytics/hubble/analyst-guide/viewing-metadata.mdx
+++ b/docs/data/analytics/hubble/analyst-guide/viewing-metadata.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Viewing Metadata"
-sidebar_position: 20
+description: "Hubble publishes metadata which can help users determine which tables to query, how frequently the dataset updates, and general information about the dataset."
 ---
 
 Hubble publishes metadata which can help users determine which tables to query, how frequently the dataset updates, and general information about the dataset.
@@ -21,30 +21,30 @@ Use the Toggle to view the contents of the Dataset. Clicking a table name will l
 
 BigQuery supports read-only, system-defined views that provide metadata information about BigQuery objects. The views can be queried via SQL from the BigQuery UI or Client Libraries.
 
-:::note
+<Note>
 
 Queries executed against the `INFORMATION_SCHEMA` cannot be cached and **will** incur data processing charges for each run.
 
-:::
+</Note>
 
 From the BigQuery Editor, the following query will list all tables in Hubble:
 
-<CodeExample>
+<CodeGroup>
 
-```sql
+```sql SQL
 # List all tables in Hubble
 #standardSQL
 select *
 from `crypto-stellar.crypto_stellar`.INFORMATION_SCHEMA.TABLES;
 ```
 
-</CodeExample>
+</CodeGroup>
 
 If you want details on a particular table, you can return the table schema:
 
-<CodeExample>
+<CodeGroup>
 
-```sql
+```sql SQL
 # List all columns for the accounts table
 select table_name,
   column_name,
@@ -55,6 +55,6 @@ from `crypto-stellar.crypto_stellar`.INFORMATION_SCHEMA.COLUMNS
 where table_name = "accounts";
 ```
 
-</CodeExample>
+</CodeGroup>
 
 More on the `INFORMATION_SCHEMA` can be found [here](https://cloud.google.com/bigquery/docs/information-schema-intro).
diff --git a/docs/data/analytics/hubble/data-catalog/README.mdx b/docs/data/analytics/hubble/data-catalog/README.mdx
deleted file mode 100644
index f5ae1c9b9..000000000
--- a/docs/data/analytics/hubble/data-catalog/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Data Catalog
-sidebar_position: 200
----
-
-import DocCardList from "@theme/DocCardList";
-
-View all Hubble data catalog information.
-
-<DocCardList />
diff --git a/docs/data/analytics/hubble/data-catalog/_category_.json b/docs/data/analytics/hubble/data-catalog/_category_.json
deleted file mode 100644
index 9e3a55f45..000000000
--- a/docs/data/analytics/hubble/data-catalog/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": true
-}
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/README.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/README.mdx
deleted file mode 100644
index d512223f9..000000000
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/README.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Data Dictionary
-sidebar_position: 20
----
-
-import DocCardList from "@theme/DocCardList";
-
-<DocCardList />
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/README.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/README.mdx
deleted file mode 100644
index 5fc6656fb..000000000
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/README.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: Bronze 🥉
-sidebar_position: 10
----
-
-import DocCardList from "@theme/DocCardList";
-
-Raw, untransformed data from the Stellar network. These tables break down and organize Ledger Metadata into a series of useful tables such as breaking down Ledger Metadata into history_ledgers, history_transactions, and history operations tables.
-
-## When to use
-
-These tables are best used for deep diving into raw Stellar data where specific custom filtering is needed.
-
-One example is retrieving and analyzing a specific contract's data entries using the `contract_data` table.
-
-Please check if any of the silver and gold tables work for your use case before using the bronze tables as they may incur higher BigQuery costs due to their size.
-
-<DocCardList />
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/account-signers.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/account-signers.mdx
index 7f542a137..01a66e324 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/account-signers.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/account-signers.mdx
@@ -1,7 +1,6 @@
 ---
 title: Account Signers
-sidebar_position: 110
-description: ""
+description: "Reference documentation for the Account Signers table in Hubble's Bronze data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/accounts.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/accounts.mdx
index 8158c2c01..a87ae3634 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/accounts.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/accounts.mdx
@@ -1,7 +1,6 @@
 ---
 title: Accounts
-sidebar_position: 100
-description: ""
+description: "Reference documentation for the Accounts table in Hubble's Bronze data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
@@ -24,7 +23,7 @@ description: ""
 | buying_liabilities | The sum of all buy offers owned by this account for XLM only | float |  | Yes | The `accounts` table only reports monetary balances for XLM. Any other asset class is reported in the `trust_lines` table. For buy offers, the account must hold the amount of asset to complete the transaction |
 | selling_liabilities | The sum of all sell offers owned by this account for XLM only | float |  | Yes | The `accounts` table only reports monetary balances for XLM. Any other asset class is reported in the `trust_lines` table. |
 | sequence_number | The account's current sequence number. The sequence number controls operations applied to an account. Operations must submit a unique sequence number that is incremented by 1 in order to apply the operation to the account so that account changes will not collide within a ledger | integer |  | Yes |  |
-| num_subentries | The account's subentry count, a weighted total rather than a row count. Subentries are the account's trustlines, offers, signers, and data entries (claimable balances are counted under sponsoring entries, not subentries). Each offer, signer, data entry, or ordinary trustline adds 1. A pool share trustline adds 2 and therefore requires two base reserves (see [CAP-38](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0038.md)). | integer |  | Yes | Each entry on a ledger takes up space, which is expensive to store on the blockchain. For each entry, an account is required to hold a [minimum XLM balance](../../../../../../learn/glossary.mdx#minimum-balance). The reserve is calculated by (2 + num_subentries + num_sponsoring - num_sponsored) \* base_reserve, currently 0.5 XLM |
+| num_subentries | The account's subentry count, a weighted total rather than a row count. Subentries are the account's trustlines, offers, signers, and data entries (claimable balances are counted under sponsoring entries, not subentries). Each offer, signer, data entry, or ordinary trustline adds 1. A pool share trustline adds 2 and therefore requires two base reserves (see [CAP-38](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0038.md)). | integer |  | Yes | Each entry on a ledger takes up space, which is expensive to store on the blockchain. For each entry, an account is required to hold a [minimum XLM balance](../../../../../../learn/glossary#minimum-balance). The reserve is calculated by (2 + num_subentries + num_sponsoring - num_sponsored) \* base_reserve, currently 0.5 XLM |
 | inflation_destination | Deprecated: The account address to receive an inflation payment when they are disbursed on the network. | string |  | Yes | Inflation was discontinued in 2019 by validator vote. |
 | flags | Denotes the enabling and disabling of certain asset issuer privileges | integer | <ul><li>0 - None, Default</li><li>1 - Auth Required (all trustlines by default are untrusted and require manual trust established)</li><li>2 - Auth Revocable (allows trustlines to be revoked if account no longer trusts asset)</li><li>4 - Auth Immutable (all auth flags are read only when set)</li><li>8 - Auth Clawback Enabled (asset can be clawed back from the user)</li></ul> | Yes | Flags are set on the issuer accounts for an asset. When user accounts trust an asset, the flags applied to the asset originate from this account |
 | home_domain | The domain that hosts this account's stellar.toml file | string |  | Yes | Only applies to asset issuer accounts. The stellar.toml file contains metadata about the asset issuer which helps identify who the issuer is and instills trust in the asset |
@@ -41,8 +40,8 @@ description: ""
 | batch_run_date | The start date for the batch interval. When taken with the date in the batch_id, the date represents the interval of ledgers processed. The batch run date can be seen as a proxy of closed_at for a ledger. | datetime |  | Yes | The table is partitioned on batch_run_date. It is recommended to always include the batch_run_date in the filter if possible to help reduce query cost. |
 | batch_insert_ts | The timestamp in UTC when a batch of records was inserted into the database. This field can help identify if a batch executed in real time or as part of a backfill | timestamp |  | Yes |  |
 | sponsor | The account address of the sponsor who is paying the reserves for this account. | string |  | No |  |
-| num_sponsored | The number of reserves sponsored for this account (meaning another account is paying for the minimum balance). Sponsored entries do not incur any reserve requirement on the account that owns the entry. | integer |  | No | Defaults to 0 Accounts, offers, trustlines, data and signers can be optionally sponsored. Claimable Balances must be sponsored. See more information on sponsorship [here](../../../../../../build/guides/transactions/sponsored-reserves.mdx). |
-| num_sponsoring | The number of reserves sponsored by this account. Entries sponsored by this account incur a reserve requirement | integer |  | No | Defaults to 0 Accounts, offers, trustlines, data and signers can be optionally sponsored. Claimable Balances must be sponsored. See more information on sponsorship [here](../../../../../../build/guides/transactions/sponsored-reserves.mdx). |
+| num_sponsored | The number of reserves sponsored for this account (meaning another account is paying for the minimum balance). Sponsored entries do not incur any reserve requirement on the account that owns the entry. | integer |  | No | Defaults to 0 Accounts, offers, trustlines, data and signers can be optionally sponsored. Claimable Balances must be sponsored. See more information on sponsorship [here](../../../../../../build/guides/transactions/sponsored-reserves). |
+| num_sponsoring | The number of reserves sponsored by this account. Entries sponsored by this account incur a reserve requirement | integer |  | No | Defaults to 0 Accounts, offers, trustlines, data and signers can be optionally sponsored. Claimable Balances must be sponsored. See more information on sponsorship [here](../../../../../../build/guides/transactions/sponsored-reserves). |
 | sequence_ledger | The unsigned 32-bit ledger number of the sequence number's age | integer |  | No | Reflects the last time an account touched its sequence number. Note that even if the Bump Sequence operation has no effect, eg it does not increase the sequence number, it still counts as a "touch" |
 | sequence_time | The UNIX timestamp of the sequence number's age | timestamp |  | No | Reflects the last time an account touched its sequence number. Note that even if the Bump Sequence operation has no effect, eg it does not increase the sequence number, it still counts as a "touch" |
 
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/claimable-balances.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/claimable-balances.mdx
index 601f994f9..0e2c40a57 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/claimable-balances.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/claimable-balances.mdx
@@ -1,7 +1,6 @@
 ---
 title: Claimable Balances
-sidebar_position: 120
-description: ""
+description: "Reference documentation for the Claimable Balances table in Hubble's Bronze data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/config-settings.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/config-settings.mdx
index 62374bf17..0ff342182 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/config-settings.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/config-settings.mdx
@@ -1,7 +1,6 @@
 ---
 title: Config Settings
-sidebar_position: 140
-description: ""
+description: "Reference documentation for the Config Settings table in Hubble's Bronze data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-code.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-code.mdx
index bfea66e49..6e30a3f66 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-code.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-code.mdx
@@ -1,7 +1,6 @@
 ---
 title: Contract Code
-sidebar_position: 130
-description: ""
+description: "Reference documentation for the Contract Code table in Hubble's Bronze data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-data.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-data.mdx
index 7bd9966b3..b0907e2b3 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-data.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-data.mdx
@@ -1,7 +1,6 @@
 ---
 title: Contract Data
-sidebar_position: 150
-description: ""
+description: "Reference documentation for the Contract Data table in Hubble's Bronze data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/evicted-keys.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/evicted-keys.mdx
index 76182f86e..90c09913e 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/evicted-keys.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/evicted-keys.mdx
@@ -1,7 +1,6 @@
 ---
 title: Evicted Keys
-sidebar_position: 200
-description: ""
+description: "Reference documentation for the Evicted Keys table in Hubble's Bronze data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-assets.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-assets.mdx
index 1fb71de3c..67fa6b9e9 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-assets.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-assets.mdx
@@ -1,7 +1,6 @@
 ---
 title: History Assets
-sidebar_position: 220
-description: ""
+description: "Reference documentation for the History Assets table in Hubble's Bronze data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-contract-events.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-contract-events.mdx
index 8af341b13..0e483a8ea 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-contract-events.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-contract-events.mdx
@@ -1,7 +1,6 @@
 ---
 title: History Contract Events
-sidebar_position: 230
-description: ""
+description: "Reference documentation for the History Contract Events table in Hubble's Bronze data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-effects.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-effects.mdx
index 81c7a7a05..ddc5857fd 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-effects.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-effects.mdx
@@ -1,7 +1,6 @@
 ---
 title: History Effects
-sidebar_position: 240
-description: ""
+description: "Reference documentation for the History Effects table in Hubble's Bronze data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-ledgers.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-ledgers.mdx
index 42408fb83..b6b2a06f9 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-ledgers.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-ledgers.mdx
@@ -1,7 +1,6 @@
 ---
 title: History Ledgers
-sidebar_position: 250
-description: ""
+description: "Reference documentation for the History Ledgers table in Hubble's Bronze data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-operations.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-operations.mdx
index c0e8595cc..638f6bd61 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-operations.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-operations.mdx
@@ -1,7 +1,6 @@
 ---
 title: History Operations
-sidebar_position: 260
-description: ""
+description: "Reference documentation for the History Operations table in Hubble's Bronze data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-trades.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-trades.mdx
index 56feb3d20..f52962cc9 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-trades.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-trades.mdx
@@ -1,7 +1,6 @@
 ---
 title: History Trades
-sidebar_position: 270
-description: ""
+description: "Reference documentation for the History Trades table in Hubble's Bronze data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-transactions.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-transactions.mdx
index 83bdb4ce4..bb458c69d 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-transactions.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-transactions.mdx
@@ -1,7 +1,6 @@
 ---
 title: History Transactions
-sidebar_position: 280
-description: ""
+description: "Reference documentation for the History Transactions table in Hubble's Bronze data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/index.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/index.mdx
new file mode 100644
index 000000000..2eaf300ad
--- /dev/null
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/index.mdx
@@ -0,0 +1,110 @@
+---
+title: Bronze 🥉
+description: "Raw, untransformed data from the Stellar network. These tables break down and organize Ledger Metadata into a series of useful tables such as breaking down Ledger Metadata into history_ledgers, history_transactions, and history operations tables."
+---
+
+## When to use
+
+These tables are best used for deep diving into raw Stellar data where specific custom filtering is needed.
+
+One example is retrieving and analyzing a specific contract's data entries using the `contract_data` table.
+
+Please check if any of the silver and gold tables work for your use case before using the bronze tables as they may incur higher BigQuery costs due to their size.
+
+<CardGroup cols={2}>
+  <Card title="Accounts" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/accounts">
+
+    Reference documentation for the Accounts table in Hubble's Bronze data dictionary.
+
+  </Card>
+  <Card title="Account Signers" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/account-signers">
+
+    Reference documentation for the Account Signers table in Hubble's Bronze data dictionary.
+
+  </Card>
+  <Card title="Claimable Balances" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/claimable-balances">
+
+    Reference documentation for the Claimable Balances table in Hubble's Bronze data dictionary.
+
+  </Card>
+  <Card title="Contract Code" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-code">
+
+    Reference documentation for the Contract Code table in Hubble's Bronze data dictionary.
+
+  </Card>
+  <Card title="Config Settings" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/config-settings">
+
+    Reference documentation for the Config Settings table in Hubble's Bronze data dictionary.
+
+  </Card>
+  <Card title="Contract Data" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-data">
+
+    Reference documentation for the Contract Data table in Hubble's Bronze data dictionary.
+
+  </Card>
+  <Card title="Liquidity Pools" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/liquidity-pools">
+
+    Reference documentation for the Liquidity Pools table in Hubble's Bronze data dictionary.
+
+  </Card>
+  <Card title="Offers" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/offers">
+
+    Reference documentation for the Offers table in Hubble's Bronze data dictionary.
+
+  </Card>
+  <Card title="Restored Key" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/restored-key">
+
+    Reference documentation for the Restored Key table in Hubble's Bronze data dictionary.
+
+  </Card>
+  <Card title="Trustlines" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/trustlines">
+
+    Reference documentation for the Trustlines table in Hubble's Bronze data dictionary.
+
+  </Card>
+  <Card title="Evicted Keys" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/evicted-keys">
+
+    Reference documentation for the Evicted Keys table in Hubble's Bronze data dictionary.
+
+  </Card>
+  <Card title="TTL" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/ttl">
+
+    Reference documentation for the Ttl table in Hubble's Bronze data dictionary.
+
+  </Card>
+  <Card title="History Assets" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-assets">
+
+    Reference documentation for the History Assets table in Hubble's Bronze data dictionary.
+
+  </Card>
+  <Card title="History Contract Events" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-contract-events">
+
+    Reference documentation for the History Contract Events table in Hubble's Bronze data dictionary.
+
+  </Card>
+  <Card title="History Effects" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-effects">
+
+    Reference documentation for the History Effects table in Hubble's Bronze data dictionary.
+
+  </Card>
+  <Card title="History Ledgers" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-ledgers">
+
+    Reference documentation for the History Ledgers table in Hubble's Bronze data dictionary.
+
+  </Card>
+  <Card title="History Operations" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-operations">
+
+    Reference documentation for the History Operations table in Hubble's Bronze data dictionary.
+
+  </Card>
+  <Card title="History Trades" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-trades">
+
+    Reference documentation for the History Trades table in Hubble's Bronze data dictionary.
+
+  </Card>
+  <Card title="History Transactions" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-transactions">
+
+    Reference documentation for the History Transactions table in Hubble's Bronze data dictionary.
+
+  </Card>
+</CardGroup>
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/liquidity-pools.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/liquidity-pools.mdx
index 5e7bdb49e..8976647f3 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/liquidity-pools.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/liquidity-pools.mdx
@@ -1,7 +1,6 @@
 ---
 title: Liquidity Pools
-sidebar_position: 160
-description: ""
+description: "Reference documentation for the Liquidity Pools table in Hubble's Bronze data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
@@ -19,7 +18,7 @@ description: ""
 
 | Name | Description | Data Type | Domain Values | Required? | Notes |
 | --- | --- | --- | --- | --- | --- |
-| liquidity_pool_id | Unique identifier for a liquidity pool. There cannot be duplicate pools for the same asset pair. Once a pool has been created for the asset pair, another cannot be created. | string |  | Yes | There is a good primer on AMMs [here](../../../../../../learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx#liquidity-pools) |
+| liquidity_pool_id | Unique identifier for a liquidity pool. There cannot be duplicate pools for the same asset pair. Once a pool has been created for the asset pair, another cannot be created. | string |  | Yes | There is a good primer on AMMs [here](../../../../../../learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools#liquidity-pools) |
 | type | The mechanism that calculates pricing and division of shares for the pool. With the initial AMM rollout, the only type of liquidity pool allowed to be created is a constant product pool | string | constant_product | Yes | For more information regarding pricing and deposit calculations, read [CAP-38](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0038.md). |
 | fee | The number of basis points charged as a percentage of the trade in order to complete the transaction. The fees earned on all trades are divided amongst pool shareholders and distributed as an incentive to keep money in the pools | integer | 30 | Yes | Fees are distributed immediately to accounts as the transaction completes. There is no schedule for fee distribution |
 | trustline_count | Total number of accounts with trustlines authorized to the pool. To create a trustline, an account must trust both base assets before trusting a pool with the asset pair | integer |  | Yes | If the issuer of A or B revokes authorization on the trustline, the account will automatically withdraw from every liquidity pool containing that asset and those pool trustlines will be deleted. |
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/offers.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/offers.mdx
index 5a27c17d6..37af49788 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/offers.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/offers.mdx
@@ -1,7 +1,6 @@
 ---
 title: Offers
-sidebar_position: 170
-description: ""
+description: "Reference documentation for the Offers table in Hubble's Bronze data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/restored-key.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/restored-key.mdx
index 355633f18..24d0aa48e 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/restored-key.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/restored-key.mdx
@@ -1,7 +1,6 @@
 ---
 title: Restored Key
-sidebar_position: 180
-description: ""
+description: "Reference documentation for the Restored Key table in Hubble's Bronze data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/trustlines.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/trustlines.mdx
index 406c88a57..f3b147c7c 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/trustlines.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/trustlines.mdx
@@ -1,7 +1,6 @@
 ---
 title: Trustlines
-sidebar_position: 190
-description: ""
+description: "Reference documentation for the Trustlines table in Hubble's Bronze data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/ttl.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/ttl.mdx
index 8e309adb7..544bd3920 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/ttl.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/ttl.mdx
@@ -1,7 +1,6 @@
 ---
 title: TTL
-sidebar_position: 210
-description: ""
+description: "Reference documentation for the Ttl table in Hubble's Bronze data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/README.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/README.mdx
deleted file mode 100644
index 1c1bc6c76..000000000
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/README.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: Gold 🥇
-sidebar_position: 30
----
-
-import DocCardList from "@theme/DocCardList";
-
-Curated analytics with friendly aggregate tables. These tables are made up of various aggregations of Stellar data such as total network TVL.
-
-## When to use
-
-These tables are best used for getting pre-aggregated metrics and insights for the Stellar network.
-
-One example is the `tvl_agg` table that contains the daily TVL for the Stellar network instead of needing to aggregate TVL from each individual account, trade, liquiditiy pool, etc...
-
-<DocCardList />
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/account-balances-daily-agg.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/account-balances-daily-agg.mdx
index 785cc7c44..889f79aa8 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/account-balances-daily-agg.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/account-balances-daily-agg.mdx
@@ -1,7 +1,6 @@
 ---
 title: Account Balances Daily Agg
-sidebar_position: 170
-description: ""
+description: "Reference documentation for the Account Balances Daily Agg table in Hubble's Gold data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/asset-balances-daily-agg.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/asset-balances-daily-agg.mdx
index 8d80d1cae..bf2aa1a36 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/asset-balances-daily-agg.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/asset-balances-daily-agg.mdx
@@ -1,7 +1,6 @@
 ---
 title: Asset Balances Daily Agg
-sidebar_position: 100
-description: ""
+description: "Reference documentation for the Asset Balances Daily Agg table in Hubble's Gold data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/daily-fee-stats-agg.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/daily-fee-stats-agg.mdx
index 1d1dddb9b..aab345cc5 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/daily-fee-stats-agg.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/daily-fee-stats-agg.mdx
@@ -1,7 +1,6 @@
 ---
 title: Daily Fee Stats Agg
-sidebar_position: 140
-description: ""
+description: "Reference documentation for the Daily Fee Stats Agg table in Hubble's Gold data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/hourly-fee-agg-account.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/hourly-fee-agg-account.mdx
index b3e3dd93c..73e4bf450 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/hourly-fee-agg-account.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/hourly-fee-agg-account.mdx
@@ -1,7 +1,6 @@
 ---
 title: Hourly Fee Agg Account
-sidebar_position: 160
-description: ""
+description: "Reference documentation for the Hourly Fee Agg Account table in Hubble's Gold data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/hourly-soroban-fee-agg-contract.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/hourly-soroban-fee-agg-contract.mdx
index 86424b2bd..04aad93f9 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/hourly-soroban-fee-agg-contract.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/hourly-soroban-fee-agg-contract.mdx
@@ -1,6 +1,5 @@
 ---
 title: Hourly Soroban Fee Agg Contract
-sidebar_position: 150
 description: "Hourly Soroban fee aggregation by contract. Strictly per-contract — operations whose footprint resolves to no contract address are excluded (`upload_wasm`, plus `extend_footprint_ttl` and `restore_footprint` operations whose footprint contains only `ContractCode` entries with no `ContractData`). Totals here therefore do not represent total network-wide Soroban fees."
 ---
 
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/index.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/index.mdx
new file mode 100644
index 000000000..9ade5a291
--- /dev/null
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/index.mdx
@@ -0,0 +1,58 @@
+---
+title: Gold 🥇
+description: "Curated analytics with friendly aggregate tables. These tables are made up of various aggregations of Stellar data such as total network TVL."
+---
+
+## When to use
+
+These tables are best used for getting pre-aggregated metrics and insights for the Stellar network.
+
+One example is the `tvl_agg` table that contains the daily TVL for the Stellar network instead of needing to aggregate TVL from each individual account, trade, liquiditiy pool, etc...
+
+<CardGroup cols={2}>
+  <Card title="Asset Balances Daily Agg" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/asset-balances-daily-agg">
+
+    Reference documentation for the Asset Balances Daily Agg table in Hubble's Gold data dictionary.
+
+  </Card>
+  <Card title="Trade Agg" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/trade-agg">
+
+    Reference documentation for the Trade Agg table in Hubble's Gold data dictionary.
+
+  </Card>
+  <Card title="TVL Agg" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/tvl-agg">
+
+    Reference documentation for the Tvl Agg table in Hubble's Gold data dictionary.
+
+  </Card>
+  <Card title="Ledger Fee Stats Agg" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/ledger-fee-stats-agg">
+
+    Reference documentation for the Ledger Fee Stats Agg table in Hubble's Gold data dictionary.
+
+  </Card>
+  <Card title="Daily Fee Stats Agg" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/daily-fee-stats-agg">
+
+    Reference documentation for the Daily Fee Stats Agg table in Hubble's Gold data dictionary.
+
+  </Card>
+  <Card title="Hourly Soroban Fee Agg Contract" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/hourly-soroban-fee-agg-contract">
+
+    Hourly Soroban fee aggregation by contract. Strictly per-contract — operations whose footprint resolves to no contract address are excluded (`upload_wasm`, plus `extend_footprint_ttl` and `restore_footprint` operations whose footprint contains only `ContractCode` entries with no `ContractData`). Totals here therefore do not represent total network-wide Soroban fees.
+
+  </Card>
+  <Card title="Hourly Fee Agg Account" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/hourly-fee-agg-account">
+
+    Reference documentation for the Hourly Fee Agg Account table in Hubble's Gold data dictionary.
+
+  </Card>
+  <Card title="Account Balances Daily Agg" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/account-balances-daily-agg">
+
+    Reference documentation for the Account Balances Daily Agg table in Hubble's Gold data dictionary.
+
+  </Card>
+  <Card title="Soroban Core Metrics" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/soroban-core-metrics">
+
+    Reference documentation for the Soroban Core Metrics table in Hubble's Gold data dictionary.
+
+  </Card>
+</CardGroup>
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/ledger-fee-stats-agg.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/ledger-fee-stats-agg.mdx
index 34936cb6e..acadc07e2 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/ledger-fee-stats-agg.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/ledger-fee-stats-agg.mdx
@@ -1,7 +1,6 @@
 ---
 title: Ledger Fee Stats Agg
-sidebar_position: 130
-description: ""
+description: "Reference documentation for the Ledger Fee Stats Agg table in Hubble's Gold data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/soroban-core-metrics.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/soroban-core-metrics.mdx
index 11f8cc136..0a2a96bde 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/soroban-core-metrics.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/soroban-core-metrics.mdx
@@ -1,7 +1,6 @@
 ---
 title: Soroban Core Metrics
-sidebar_position: 180
-description: ""
+description: "Reference documentation for the Soroban Core Metrics table in Hubble's Gold data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/trade-agg.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/trade-agg.mdx
index d23dcdf24..a4d56e7cd 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/trade-agg.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/trade-agg.mdx
@@ -1,7 +1,6 @@
 ---
 title: Trade Agg
-sidebar_position: 110
-description: ""
+description: "Reference documentation for the Trade Agg table in Hubble's Gold data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/tvl-agg.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/tvl-agg.mdx
index b921a06f9..ffbf9929b 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/tvl-agg.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/tvl-agg.mdx
@@ -1,7 +1,6 @@
 ---
 title: TVL Agg
-sidebar_position: 120
-description: ""
+description: "Reference documentation for the Tvl Agg table in Hubble's Gold data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/index.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/index.mdx
new file mode 100644
index 000000000..e3e2dbb9f
--- /dev/null
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/index.mdx
@@ -0,0 +1,22 @@
+---
+title: Data Dictionary
+description: "Hubble data is organized into bronze, silver, and gold sections."
+---
+
+<CardGroup cols={2}>
+  <Card title="Bronze 🥉" icon="box-archive" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze">
+
+    19 items
+
+  </Card>
+  <Card title="Silver 🥈" icon="box-archive" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/silver">
+
+    22 items
+
+  </Card>
+  <Card title="Gold 🥇" icon="box-archive" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/gold">
+
+    9 items
+
+  </Card>
+</CardGroup>
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/README.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/README.mdx
deleted file mode 100644
index d28a530ad..000000000
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/README.mdx
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: Silver 🥈
-sidebar_position: 20
----
-
-import DocCardList from "@theme/DocCardList";
-
-Decoded, transformed, and filtered data. These tables transform the bronze tables into easier to use tables by joining and flattening tables and filtering out information for specific use cases.
-
-## When to use
-
-These tables are best used for a more curated experience while still needing to search and filter for specific use cases such as information on a specific contract.
-
-One example is getting relevant Stellar events to calculate circulating supply by using the `token_transfers_raw` table. In theory you can get the same information from the bronze `history_contract_events` table but the `token_transfers_raw` table has already processed, filtered, and flattened the events relevant to SEP-41 events and classic operations.
-
-## Slowly Changing Dimensions (SCD Type 2)
-
-Some silver tables are modeled as [SCD Type 2](https://github.com/stellar/stellar-dbt-public/blob/master/docs/snapshot.md) tables. This means they track the full history of changes to a record over time by keeping multiple versions with `valid_from` / `valid_to` ranges.
-
-These tables are especially useful for answering historical questions such as:
-
-- What was the state of a contract at a given point in time?
-- How did an account, trustline, or balance evolve across different periods?
-- Which liquidity pools were active at a given date, and how did their properties change over time?
-
-:::note[Daily Snapshot Frequency]
-
-Snapshots run on a daily basis, meaning they capture inter-day changes, but not multiple changes that occur within the same day.
-
-:::
-
-<DocCardList />
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/account-signers-current.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/account-signers-current.mdx
index 39a3945d6..ba808d462 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/account-signers-current.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/account-signers-current.mdx
@@ -1,7 +1,6 @@
 ---
 title: Account Signers Current
-sidebar_position: 100
-description: ""
+description: "Column details are equivalent to the bronze Account Signers table."
 ---
 
 <div className="scoped-data-dictionary-table">
@@ -17,6 +16,6 @@ description: ""
 
 ## Column Details
 
-Column details are equivalent to the bronze [Account Signers](../bronze/account-signers.mdx) table. Filters down to only latest state information.
+Column details are equivalent to the bronze [Account Signers](../bronze/account-signers) table. Filters down to only latest state information.
 
 </div>
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-current.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-current.mdx
index ecaf70b43..12dc923b8 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-current.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-current.mdx
@@ -1,7 +1,6 @@
 ---
 title: Accounts Current
-sidebar_position: 110
-description: ""
+description: "Column details are equivalent to the bronze Accounts table."
 ---
 
 <div className="scoped-data-dictionary-table">
@@ -17,6 +16,6 @@ description: ""
 
 ## Column Details
 
-Column details are equivalent to the bronze [Accounts](../bronze/accounts.mdx) table. Filters down to only latest state information.
+Column details are equivalent to the bronze [Accounts](../bronze/accounts) table. Filters down to only latest state information.
 
 </div>
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-snapshot.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-snapshot.mdx
index 5680b11fc..9629e22bd 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-snapshot.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-snapshot.mdx
@@ -1,7 +1,6 @@
 ---
 title: Accounts Snapshot
-sidebar_position: 120
-description: ""
+description: "Reference documentation for the Accounts Snapshot table in Hubble's Silver data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/claimable-balances-current.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/claimable-balances-current.mdx
index 4ad9b5b2e..4e742145e 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/claimable-balances-current.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/claimable-balances-current.mdx
@@ -1,14 +1,15 @@
 ---
 title: Claimable Balances Current
-sidebar_position: 130
-description: ""
+description: "Column details are equivalent to the bronze Claimable Balances table."
 ---
 
-:::caution[Table is not being updated]
+<Warning>
+
+**Table is not being updated**
 
 The `claimable_balances_current` model is disabled in `stellar-dbt-public` (`+enabled: false` in `dbt_project.yml`), so this table is no longer refreshed and its contents are frozen.
 
-To derive current state yourself, read the bronze [Claimable Balances](../bronze/claimable-balances.mdx) table and take the latest row per balance. That table is append-only and holds many historical rows per `balance_id`, so selecting from it without deduplicating will return stale rows:
+To derive current state yourself, read the bronze [Claimable Balances](../bronze/claimable-balances) table and take the latest row per balance. That table is append-only and holds many historical rows per `balance_id`, so selecting from it without deduplicating will return stale rows:
 
 ```sql
 select * except (row_num)
@@ -23,7 +24,7 @@ where row_num = 1
 
 This scans the full history of the bronze table (on the order of 1 TB), so materialize the result or restrict `batch_run_date` if you only need balances touched in a given window.
 
-:::
+</Warning>
 
 <div className="scoped-data-dictionary-table">
 
@@ -38,6 +39,6 @@ This scans the full history of the bronze table (on the order of 1 TB), so mater
 
 ## Column Details
 
-Column details are equivalent to the bronze [Claimable Balances](../bronze/claimable-balances.mdx) table. Filters down to only latest state information.
+Column details are equivalent to the bronze [Claimable Balances](../bronze/claimable-balances) table. Filters down to only latest state information.
 
 </div>
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/config-settings-current.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/config-settings-current.mdx
index f889d52f3..107eabeba 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/config-settings-current.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/config-settings-current.mdx
@@ -1,7 +1,6 @@
 ---
 title: Config Settings Current
-sidebar_position: 140
-description: ""
+description: "Column details are equivalent to the bronze Config Settings table."
 ---
 
 <div className="scoped-data-dictionary-table">
@@ -17,6 +16,6 @@ description: ""
 
 ## Column Details
 
-Column details are equivalent to the bronze [Config Settings](../bronze/config-settings.mdx) table. Filters down to only latest state information.
+Column details are equivalent to the bronze [Config Settings](../bronze/config-settings) table. Filters down to only latest state information.
 
 </div>
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/config-settings-snapshot.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/config-settings-snapshot.mdx
index 7a5587c29..84a0aff65 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/config-settings-snapshot.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/config-settings-snapshot.mdx
@@ -1,7 +1,6 @@
 ---
 title: Config Settings Snapshot
-sidebar_position: 150
-description: ""
+description: "Reference documentation for the Config Settings Snapshot table in Hubble's Silver data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
@@ -23,7 +22,7 @@ Each row represents a specific setting related to transaction limits, ledger con
 
 | Name | Description | Data Type | Domain Values | Required? | Notes |
 | --- | --- | --- | --- | --- | --- |
-| config_setting_name | The name of the configuration setting (metric) extracted from the source table. Each row represents a different setting tracked over time. | STRING |  | Yes | Natural Key. Corresponds to a column name on the bronze [Config Settings](../bronze/config-settings.mdx) table. |
+| config_setting_name | The name of the configuration setting (metric) extracted from the source table. Each row represents a different setting tracked over time. | STRING |  | Yes | Natural Key. Corresponds to a column name on the bronze [Config Settings](../bronze/config-settings) table. |
 | setting_value | The numeric value associated with the configuration setting. This value represents the active limit, fee, or constraint set by the network. | INTEGER |  | Yes |  |
 | valid_from | The timestamp when this snapshot row was first inserted and became effective. This helps in tracking changes over time. | TIMESTAMP |  | Yes | Natural Key. |
 | valid_to | The timestamp when this row is no longer valid. If `null`, the setting is currently active. | TIMESTAMP |  | No |  |
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-code-current.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-code-current.mdx
index 0e3e8877d..534e6ab1b 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-code-current.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-code-current.mdx
@@ -1,7 +1,6 @@
 ---
 title: Contract Code Current
-sidebar_position: 160
-description: ""
+description: "Column details are equivalent to the bronze Contract Code table."
 ---
 
 <div className="scoped-data-dictionary-table">
@@ -17,6 +16,6 @@ description: ""
 
 ## Column Details
 
-Column details are equivalent to the bronze [Contract Code](../bronze/contract-code.mdx) table. Filters down to only latest state information.
+Column details are equivalent to the bronze [Contract Code](../bronze/contract-code) table. Filters down to only latest state information.
 
 </div>
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-current.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-current.mdx
index 418f60915..66e2e1646 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-current.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-current.mdx
@@ -1,7 +1,6 @@
 ---
 title: Contract Data Current
-sidebar_position: 170
-description: ""
+description: "Column details are equivalent to the bronze Contract Data table."
 ---
 
 <div className="scoped-data-dictionary-table">
@@ -17,6 +16,6 @@ description: ""
 
 ## Column Details
 
-Column details are equivalent to the bronze [Contract Data](../bronze/contract-data.mdx) table. Filters down to only latest state information.
+Column details are equivalent to the bronze [Contract Data](../bronze/contract-data) table. Filters down to only latest state information.
 
 </div>
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-snapshot.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-snapshot.mdx
index f8a50b287..8fcb059da 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-snapshot.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-snapshot.mdx
@@ -1,7 +1,6 @@
 ---
 title: Contract Data Snapshot
-sidebar_position: 180
-description: ""
+description: "Reference documentation for the Contract Data Snapshot table in Hubble's Silver data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations-soroban.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations-soroban.mdx
index 8c677e456..f1a3dc238 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations-soroban.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations-soroban.mdx
@@ -1,7 +1,6 @@
 ---
 title: Enriched History Operations Soroban
-sidebar_position: 300
-description: ""
+description: "Column details are equivalent to the silver Enriched History Operations table."
 ---
 
 <div className="scoped-data-dictionary-table">
@@ -17,7 +16,7 @@ description: ""
 
 ## Column Details
 
-Column details are equivalent to the silver [Enriched History Operations](./enriched-history-operations.mdx) table. Filters down to only operation types 24, 25, and 26.
+Column details are equivalent to the silver [Enriched History Operations](./enriched-history-operations) table. Filters down to only operation types 24, 25, and 26.
 
 One column is renamed: this model selects `enriched.type as op_type`, so the operation type code is named `op_type` here and `type` on the Enriched History Operations page.
 
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations.mdx
index 1c13545e4..fe91015fc 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations.mdx
@@ -1,7 +1,6 @@
 ---
 title: Enriched History Operations
-sidebar_position: 290
-description: ""
+description: "Reference documentation for the Enriched History Operations table in Hubble's Silver data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
@@ -137,14 +136,16 @@ description: ""
 | operation_result_code | The result code returned when an operation is applied. This code is helpful for understanding failed operations | string |  |  | history_operations |  |
 | operation_trace_code | The trace code returned when an operation is applied to the Stellar Network. This code is helpful for understanding failure types | string |  |  | history_operations |  |
 
-:::note[Transaction and ledger columns]
+<Note>
 
-This table also carries transaction-level columns from [History Transactions](../bronze/history-transactions.mdx) (`closed_at`, `ledger_sequence`, `transaction_hash`, `txn_account`, `txn_created_at`, `txn_operation_count`, `account_sequence`, `account_muxed`, `max_fee`, `new_max_fee`, `memo`, `memo_type`, `time_bounds`, `ledger_bounds`, `successful`, `transaction_result_code`, `fee_account`, `fee_account_muxed`, `fee_charged`, `extra_signers`, `tx_signers`, `min_account_sequence`, `min_account_sequence_age`, `min_account_sequence_ledger_gap`, `resource_fee`, `resource_fee_refund`, `refundable_fee`, `non_refundable_resource_fee_charged`, `refundable_resource_fee_charged`, `rent_fee_charged`, `inclusion_fee_bid`, `inclusion_fee_charged`, `soroban_resources_instructions`, `soroban_resources_read_bytes` and `soroban_resources_write_bytes`) and ledger-level columns from [History Ledgers](../bronze/history-ledgers.mdx) (`ledger_hash`, `previous_ledger_hash`, `ledger_id`, `ledger_operation_count`, `transaction_count`, `successful_transaction_count`, `failed_transaction_count`, `total_coins`, `fee_pool`, `base_fee`, `base_reserve`, `max_tx_set_size`, `protocol_version`, `node_id`, `signature`, `soroban_fee_write_1kb` and `total_byte_size_of_bucket_list`), plus the batch metadata columns `batch_id`, `batch_run_date` and `airflow_start_ts` and the raw `details_json` record.
+**Transaction and ledger columns**
+
+This table also carries transaction-level columns from [History Transactions](../bronze/history-transactions) (`closed_at`, `ledger_sequence`, `transaction_hash`, `txn_account`, `txn_created_at`, `txn_operation_count`, `account_sequence`, `account_muxed`, `max_fee`, `new_max_fee`, `memo`, `memo_type`, `time_bounds`, `ledger_bounds`, `successful`, `transaction_result_code`, `fee_account`, `fee_account_muxed`, `fee_charged`, `extra_signers`, `tx_signers`, `min_account_sequence`, `min_account_sequence_age`, `min_account_sequence_ledger_gap`, `resource_fee`, `resource_fee_refund`, `refundable_fee`, `non_refundable_resource_fee_charged`, `refundable_resource_fee_charged`, `rent_fee_charged`, `inclusion_fee_bid`, `inclusion_fee_charged`, `soroban_resources_instructions`, `soroban_resources_read_bytes` and `soroban_resources_write_bytes`) and ledger-level columns from [History Ledgers](../bronze/history-ledgers) (`ledger_hash`, `previous_ledger_hash`, `ledger_id`, `ledger_operation_count`, `transaction_count`, `successful_transaction_count`, `failed_transaction_count`, `total_coins`, `fee_pool`, `base_fee`, `base_reserve`, `max_tx_set_size`, `protocol_version`, `node_id`, `signature`, `soroban_fee_write_1kb` and `total_byte_size_of_bucket_list`), plus the batch metadata columns `batch_id`, `batch_run_date` and `airflow_start_ts` and the raw `details_json` record.
 
 Those columns carry the same meaning here as they do in their source tables and are not repeated above.
 
 Not every column of the source tables is carried over. In particular the Protocol 23 additions `soroban_resources_disk_read_bytes` and `soroban_resources_archived_entries` (History Transactions) and `total_byte_size_of_live_soroban_state` (History Ledgers) are **not** selected by this model; query the bronze tables directly for those.
 
-:::
+</Note>
 
 </div>
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/evicted-keys-snapshot.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/evicted-keys-snapshot.mdx
index 6a96c2a45..8faf6370a 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/evicted-keys-snapshot.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/evicted-keys-snapshot.mdx
@@ -1,7 +1,6 @@
 ---
 title: Evicted Keys Snapshot
-sidebar_position: 190
-description: ""
+description: "Reference documentation for the Evicted Keys Snapshot table in Hubble's Silver data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/index.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/index.mdx
new file mode 100644
index 000000000..0d5b6ecb0
--- /dev/null
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/index.mdx
@@ -0,0 +1,140 @@
+---
+title: Silver 🥈
+description: "Decoded, transformed, and filtered data. These tables transform the bronze tables into easier to use tables by joining and flattening tables and filtering out information for specific use cases."
+---
+
+## When to use
+
+These tables are best used for a more curated experience while still needing to search and filter for specific use cases such as information on a specific contract.
+
+One example is getting relevant Stellar events to calculate circulating supply by using the `token_transfers_raw` table. In theory you can get the same information from the bronze `history_contract_events` table but the `token_transfers_raw` table has already processed, filtered, and flattened the events relevant to SEP-41 events and classic operations.
+
+## Slowly Changing Dimensions (SCD Type 2)
+
+Some silver tables are modeled as [SCD Type 2](https://github.com/stellar/stellar-dbt-public/blob/master/docs/snapshot.md) tables. This means they track the full history of changes to a record over time by keeping multiple versions with `valid_from` / `valid_to` ranges.
+
+These tables are especially useful for answering historical questions such as:
+
+- What was the state of a contract at a given point in time?
+- How did an account, trustline, or balance evolve across different periods?
+- Which liquidity pools were active at a given date, and how did their properties change over time?
+
+<Note>
+
+**Daily Snapshot Frequency**
+
+Snapshots run on a daily basis, meaning they capture inter-day changes, but not multiple changes that occur within the same day.
+
+</Note>
+<CardGroup cols={2}>
+  <Card title="Account Signers Current" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/account-signers-current">
+
+    Column details are equivalent to the bronze Account Signers table.
+
+  </Card>
+  <Card title="Accounts Current" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-current">
+
+    Column details are equivalent to the bronze Accounts table.
+
+  </Card>
+  <Card title="Accounts Snapshot" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-snapshot">
+
+    Reference documentation for the Accounts Snapshot table in Hubble's Silver data dictionary.
+
+  </Card>
+  <Card title="Claimable Balances Current" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/claimable-balances-current">
+
+    Column details are equivalent to the bronze Claimable Balances table.
+
+  </Card>
+  <Card title="Config Settings Current" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/config-settings-current">
+
+    Column details are equivalent to the bronze Config Settings table.
+
+  </Card>
+  <Card title="Config Settings Snapshot" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/config-settings-snapshot">
+
+    Reference documentation for the Config Settings Snapshot table in Hubble's Silver data dictionary.
+
+  </Card>
+  <Card title="Contract Code Current" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-code-current">
+
+    Column details are equivalent to the bronze Contract Code table.
+
+  </Card>
+  <Card title="Contract Data Current" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-current">
+
+    Column details are equivalent to the bronze Contract Data table.
+
+  </Card>
+  <Card title="Contract Data Snapshot" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-snapshot">
+
+    Reference documentation for the Contract Data Snapshot table in Hubble's Silver data dictionary.
+
+  </Card>
+  <Card title="Evicted Keys Snapshot" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/evicted-keys-snapshot">
+
+    Reference documentation for the Evicted Keys Snapshot table in Hubble's Silver data dictionary.
+
+  </Card>
+  <Card title="Liquidity Pools Current" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-current">
+
+    Column details are equivalent to the bronze Liquidity Pools table.
+
+  </Card>
+  <Card title="Liquidity Pools Snapshot" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-snapshot">
+
+    Reference documentation for the Liquidity Pools Snapshot table in Hubble's Silver data dictionary.
+
+  </Card>
+  <Card title="Offers Current" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/offers-current">
+
+    Column details are equivalent to the bronze Offers table.
+
+  </Card>
+  <Card title="Reflector Prices Data CEX Snapshot" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-cex-snapshot">
+
+    Reference documentation for the Reflector Prices Data CEX Snapshot table in Hubble's Silver data dictionary.
+
+  </Card>
+  <Card title="Reflector Prices Data FEX Snapshot" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-fex-snapshot">
+
+    Reference documentation for the Reflector Prices Data FEX Snapshot table in Hubble's Silver data dictionary.
+
+  </Card>
+  <Card title="Reflector Prices Data SDEX Snapshot" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-sdex-snapshot">
+
+    Reference documentation for the Reflector Prices Data SDEX Snapshot table in Hubble's Silver data dictionary.
+
+  </Card>
+  <Card title="Trustlines Current" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-current">
+
+    Column details are equivalent to the bronze Trustlines table.
+
+  </Card>
+  <Card title="Trustlines Snapshot" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-snapshot">
+
+    Reference documentation for the Trustlines Snapshot table in Hubble's Silver data dictionary.
+
+  </Card>
+  <Card title="TTL Current" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/ttl-current">
+
+    Column details are equivalent to the bronze TTL table.
+
+  </Card>
+  <Card title="Enriched History Operations" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations">
+
+    Reference documentation for the Enriched History Operations table in Hubble's Silver data dictionary.
+
+  </Card>
+  <Card title="Enriched History Operations Soroban" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations-soroban">
+
+    Column details are equivalent to the silver Enriched History Operations table.
+
+  </Card>
+  <Card title="Token Transfers" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/token-transfers-raw">
+
+    Reference documentation for the Token Transfers Raw table in Hubble's Silver data dictionary.
+
+  </Card>
+</CardGroup>
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-current.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-current.mdx
index 605acb7df..2a2c516c2 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-current.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-current.mdx
@@ -1,7 +1,6 @@
 ---
 title: Liquidity Pools Current
-sidebar_position: 200
-description: ""
+description: "Column details are equivalent to the bronze Liquidity Pools table."
 ---
 
 <div className="scoped-data-dictionary-table">
@@ -17,6 +16,6 @@ description: ""
 
 ## Column Details
 
-Column details are equivalent to the bronze [Liquidity Pools](../bronze/liquidity-pools.mdx) table. Filters down to only latest state information.
+Column details are equivalent to the bronze [Liquidity Pools](../bronze/liquidity-pools) table. Filters down to only latest state information.
 
 </div>
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-snapshot.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-snapshot.mdx
index bc37b34f6..f433d1c6e 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-snapshot.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-snapshot.mdx
@@ -1,7 +1,6 @@
 ---
 title: Liquidity Pools Snapshot
-sidebar_position: 210
-description: ""
+description: "Reference documentation for the Liquidity Pools Snapshot table in Hubble's Silver data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/offers-current.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/offers-current.mdx
index 64ea5aaba..acda621c2 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/offers-current.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/offers-current.mdx
@@ -1,7 +1,6 @@
 ---
 title: Offers Current
-sidebar_position: 220
-description: ""
+description: "Column details are equivalent to the bronze Offers table."
 ---
 
 <div className="scoped-data-dictionary-table">
@@ -17,6 +16,6 @@ description: ""
 
 ## Column Details
 
-Column details are equivalent to the bronze [Offers](../bronze/offers.mdx) table. Filters down to only latest state information.
+Column details are equivalent to the bronze [Offers](../bronze/offers) table. Filters down to only latest state information.
 
 </div>
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-cex-snapshot.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-cex-snapshot.mdx
index 08b4a9bfb..3ab915d2d 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-cex-snapshot.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-cex-snapshot.mdx
@@ -1,7 +1,6 @@
 ---
 title: Reflector Prices Data CEX Snapshot
-sidebar_position: 230
-description: ""
+description: "Reference documentation for the Reflector Prices Data CEX Snapshot table in Hubble's Silver data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-fex-snapshot.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-fex-snapshot.mdx
index 17f83c00b..232e5b917 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-fex-snapshot.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-fex-snapshot.mdx
@@ -1,7 +1,6 @@
 ---
 title: Reflector Prices Data FEX Snapshot
-sidebar_position: 240
-description: ""
+description: "Reference documentation for the Reflector Prices Data FEX Snapshot table in Hubble's Silver data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-sdex-snapshot.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-sdex-snapshot.mdx
index b473548e6..f4cf71699 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-sdex-snapshot.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-sdex-snapshot.mdx
@@ -1,7 +1,6 @@
 ---
 title: Reflector Prices Data SDEX Snapshot
-sidebar_position: 250
-description: ""
+description: "Reference documentation for the Reflector Prices Data SDEX Snapshot table in Hubble's Silver data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/token-transfers-raw.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/token-transfers-raw.mdx
index c14f4e5ed..6afff12cf 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/token-transfers-raw.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/token-transfers-raw.mdx
@@ -1,7 +1,6 @@
 ---
 title: Token Transfers
-sidebar_position: 310
-description: ""
+description: "Reference documentation for the Token Transfers Raw table in Hubble's Silver data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-current.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-current.mdx
index f9ae63316..89ccc0def 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-current.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-current.mdx
@@ -1,7 +1,6 @@
 ---
 title: Trustlines Current
-sidebar_position: 260
-description: ""
+description: "Column details are equivalent to the bronze Trustlines table."
 ---
 
 <div className="scoped-data-dictionary-table">
@@ -17,6 +16,6 @@ description: ""
 
 ## Column Details
 
-Column details are equivalent to the bronze [Trustlines](../bronze/trustlines.mdx) table. Filters down to only latest state information.
+Column details are equivalent to the bronze [Trustlines](../bronze/trustlines) table. Filters down to only latest state information.
 
 </div>
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-snapshot.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-snapshot.mdx
index 9a11f8985..fd3837320 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-snapshot.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-snapshot.mdx
@@ -1,7 +1,6 @@
 ---
 title: Trustlines Snapshot
-sidebar_position: 270
-description: ""
+description: "Reference documentation for the Trustlines Snapshot table in Hubble's Silver data dictionary."
 ---
 
 <div className="scoped-data-dictionary-table">
diff --git a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/ttl-current.mdx b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/ttl-current.mdx
index 29f1eb457..31774fed6 100644
--- a/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/ttl-current.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/ttl-current.mdx
@@ -1,7 +1,6 @@
 ---
 title: TTL Current
-sidebar_position: 280
-description: ""
+description: "Column details are equivalent to the bronze TTL table."
 ---
 
 <div className="scoped-data-dictionary-table">
@@ -17,6 +16,6 @@ description: ""
 
 ## Column Details
 
-Column details are equivalent to the bronze [TTL](../bronze/ttl.mdx) table. Filters down to only latest state information.
+Column details are equivalent to the bronze [TTL](../bronze/ttl) table. Filters down to only latest state information.
 
 </div>
diff --git a/docs/data/analytics/hubble/data-catalog/data-lineage.mdx b/docs/data/analytics/hubble/data-catalog/data-lineage.mdx
index 45f51b7b2..5548c80be 100644
--- a/docs/data/analytics/hubble/data-catalog/data-lineage.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-lineage.mdx
@@ -1,7 +1,5 @@
 ---
+url: "http://www.stellar-dbt-docs.com/#!/overview"
 title: Data Lineage
+description: "Overview of Data Lineage."
 ---
-
-import RedirectPage from "@site/src/components/RedirectPage";
-
-<RedirectPage to="http://www.stellar-dbt-docs.com/#!/overview" />
diff --git a/docs/data/analytics/hubble/data-catalog/data-model-diagram.mdx b/docs/data/analytics/hubble/data-catalog/data-model-diagram.mdx
index 1e50681c6..8c5c06549 100644
--- a/docs/data/analytics/hubble/data-catalog/data-model-diagram.mdx
+++ b/docs/data/analytics/hubble/data-catalog/data-model-diagram.mdx
@@ -1,13 +1,13 @@
 ---
 title: Data Model Diagram
-sidebar_position: 0
+description: "For more detailed information see the Full Hubble Data Model Diagram or the Compressed Hubble Data Model Diagram."
 ---
 
-:::info
+<Info>
 
 For more detailed information see the [Full Hubble Data Model Diagram](https://dbdiagram.io/d/Hubble-Public-Data-Model-66671e056bc9d447b1501801) or the [Compressed Hubble Data Model Diagram](https://dbdiagram.io/d/Hubble-Public-Data-Model-Compressed-666730996bc9d447b151a181).
 
-:::
+</Info>
 
 The following diagram shows the relationships between the history and state tables within Hubble.
 
diff --git a/docs/data/analytics/hubble/data-catalog/index.mdx b/docs/data/analytics/hubble/data-catalog/index.mdx
new file mode 100644
index 000000000..f15e09d27
--- /dev/null
+++ b/docs/data/analytics/hubble/data-catalog/index.mdx
@@ -0,0 +1,22 @@
+---
+title: Data Catalog
+description: "View all Hubble data catalog information."
+---
+
+<CardGroup cols={2}>
+  <Card title="Data Model Diagram" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-model-diagram">
+
+    For more detailed information see the Full Hubble Data Model Diagram or the Compressed Hubble Data Model Diagram.
+
+  </Card>
+  <Card title="Data Dictionary" icon="box-archive" href="/docs/data/analytics/hubble/data-catalog/data-dictionary">
+
+    3 items
+
+  </Card>
+  <Card title="Data Lineage" icon="file-lines" href="/docs/data/analytics/hubble/data-catalog/data-lineage">
+
+    Overview of Data Lineage.
+
+  </Card>
+</CardGroup>
diff --git a/docs/data/analytics/hubble/developer-guide/README.mdx b/docs/data/analytics/hubble/developer-guide/README.mdx
deleted file mode 100644
index 2454be0cc..000000000
--- a/docs/data/analytics/hubble/developer-guide/README.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: Developer Guide
-sidebar_position: 15
-sidebar_key: hubble-developer-guide
----
-
-import DocCardList from "@theme/DocCardList";
-
-All you need to know about running a Hubble analytics platform.
-
-<DocCardList />
diff --git a/docs/data/analytics/hubble/developer-guide/backfill/JS-UDF.mdx b/docs/data/analytics/hubble/developer-guide/backfill/JS-UDF.mdx
index 85296bd0e..2b20167b5 100644
--- a/docs/data/analytics/hubble/developer-guide/backfill/JS-UDF.mdx
+++ b/docs/data/analytics/hubble/developer-guide/backfill/JS-UDF.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Backfill using JS UDF"
-sidebar_position: 0
+description: "This document outlines methods to extract required fields from the XDR of raw data."
 ---
 
 This document outlines methods to extract required fields from the XDR of raw data.
@@ -11,7 +11,7 @@ Use Cases:
 - Backfix for a new column added
 - Temporary extraction of fields not parsed by stellar-etl
 
-We'll take the example of extracting the `fee_account_muxed` field from a transaction envelope (`tx_meta` XDR). However, this method can be adapted to other fields as well. It is worth noting that most users will not need to standup and run their own Hubble. The Stellar Development Foundation provides public access to the data through the public datasets and tables in GCP BigQuery. Instructions on how to access this data can be found in the [Connecting](../../developer-guide/connecting-to-bigquery/README.mdx) section.
+We'll take the example of extracting the `fee_account_muxed` field from a transaction envelope (`tx_meta` XDR). However, this method can be adapted to other fields as well. It is worth noting that most users will not need to standup and run their own Hubble. The Stellar Development Foundation provides public access to the data through the public datasets and tables in GCP BigQuery. Instructions on how to access this data can be found in the [Connecting](/docs/data/analytics/hubble/developer-guide/connecting-to-bigquery) section.
 
 We will use the [js-stellar-base](https://github.com/stellar/js-stellar-base) library to parse the XDR and employ JavaScript UDFs (User Defined Functions) in BigQuery to apply the transformation to the dataset.
 
diff --git a/docs/data/analytics/hubble/developer-guide/backfill/README.mdx b/docs/data/analytics/hubble/developer-guide/backfill/README.mdx
deleted file mode 100644
index 73eea5561..000000000
--- a/docs/data/analytics/hubble/developer-guide/backfill/README.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: "Backfill"
-sidebar_position: 10
----
-
-import DocCardList from "@theme/DocCardList";
-
-Once your scheduling and orchestration are set up, you might encounter the following scenarios:
-
-| Use Case | Description | Solution |
-| --- | --- | --- |
-| Initial Backfill | You have just setup hubble and would like to ingest historical data | - Option 1. [Data Import](../../developer-guide/backfill/data-import.mdx) <br></br> **Pros:** Cheap and fast <br></br>- Option 2: Re-trigger DAGs for past dates <br></br> **Cons:** Slow and expensive |
-| Bug Fix | You resolved a bug and need to re-ingest a specific data column/s or back fix a data column | - Option 1. [JS UDF](../../developer-guide/backfill/JS-UDF.mdx) <br></br> **Pros:** Cheap and fast <br></br> **Cons:** May need optimized query writing and running in batches <br></br> - Option 2: Re-trigger DAGs for past dates <br></br> **Cons:** Slow and expensive |
-| New data column extraction | You added a new data column/s as part of a feature request and need to backfill data for the newly added column/s | - Option 1. [JS UDF](../../developer-guide/backfill/JS-UDF.mdx) <br></br> **Pros:** Cheap and fast <br></br> **Cons:** May need optimized query writing and running in batches <br></br> - Option 2: Re-trigger DAGs for past dates <br></br> **Cons:** Slow and expensive |
-
-<DocCardList />
diff --git a/docs/data/analytics/hubble/developer-guide/backfill/data-import.mdx b/docs/data/analytics/hubble/developer-guide/backfill/data-import.mdx
index 79a96fec7..57817d7ec 100644
--- a/docs/data/analytics/hubble/developer-guide/backfill/data-import.mdx
+++ b/docs/data/analytics/hubble/developer-guide/backfill/data-import.mdx
@@ -1,11 +1,11 @@
 ---
 title: "Data Import"
-sidebar_position: 0
+description: "This document outlines methods to perform inital backfill when setting up hubble."
 ---
 
 This document outlines methods to perform inital backfill when setting up hubble.
 
-# Use SDF ETL Data as a Source
+## Use SDF ETL Data as a Source
 
 ## 1. Export Data to Cloud Storage and Load Data into BigQuery
 
@@ -29,9 +29,9 @@ LOAD DATA INTO mydataset.transactions
   WITH PARTITION COLUMNS;
 ```
 
-## 2. Use BigQuery API / Console to Mirror SDF's Dataset
+## 2. Use BigQuery API / Console to Mirror SDF's Dataset {#2-use-bigquery-api--console-to-mirror-sdfs-dataset}
 
-The Stellar Development Foundation provides public access to fully transformed Stellar network data through the public datasets and tables in GCP BigQuery. Instructions on how to access this data can be found in the [Connecting](../../developer-guide/connecting-to-bigquery/README.mdx) section.
+The Stellar Development Foundation provides public access to fully transformed Stellar network data through the public datasets and tables in GCP BigQuery. Instructions on how to access this data can be found in the [Connecting](/docs/data/analytics/hubble/developer-guide/connecting-to-bigquery) section.
 
 Use the [Create Table Copy statement](https://cloud.google.com/bigquery/docs/reference/standard-sql/data-definition-language#create_table_copy) to copy data across datasets.
 
@@ -42,12 +42,12 @@ COPY source_table_name
 [OPTIONS(table_option_list)]
 ```
 
-# Use Galexie as a Source
+## Use Galexie as a Source
 
-[Galexie](../../../../indexers/build-your-own/galexie/README.mdx) is a tool for extracting, processing, and exporting Stellar ledger metadata to external storage, creating a data lake of pre-processed ledger metadata. This is an upstream data source to Hubble, useful when you have a custom Stellar-ETL pipeline.
+[Galexie](/docs/data/indexers/build-your-own/galexie) is a tool for extracting, processing, and exporting Stellar ledger metadata to external storage, creating a data lake of pre-processed ledger metadata. This is an upstream data source to Hubble, useful when you have a custom Stellar-ETL pipeline.
 
 **Steps**
 
 1. Ensure you provide the correct value for datastore-path in Stellar-ETL [command flags](https://github.com/stellar/stellar-etl/tree/master?tab=readme-ov-file#common-flags). This represents the name of the bucket where your Galexie instance outputs ledger close metadata.
-2. Set up an [orchestration system like Airflow](../../developer-guide/scheduling-and-orchestration/getting-started.mdx).
+2. Set up an [orchestration system like Airflow](../../developer-guide/scheduling-and-orchestration/getting-started).
 3. In your Airflow instance, trigger the history_table_export DAG for older dates.
diff --git a/docs/data/analytics/hubble/developer-guide/backfill/index.mdx b/docs/data/analytics/hubble/developer-guide/backfill/index.mdx
new file mode 100644
index 000000000..09a4d5480
--- /dev/null
+++ b/docs/data/analytics/hubble/developer-guide/backfill/index.mdx
@@ -0,0 +1,25 @@
+---
+title: "Backfill"
+description: "Once your scheduling and orchestration are set up, you might encounter the following scenarios."
+---
+
+Once your scheduling and orchestration are set up, you might encounter the following scenarios:
+
+| Use Case | Description | Solution |
+| --- | --- | --- |
+| Initial Backfill | You have just setup hubble and would like to ingest historical data | - Option 1. [Data Import](/docs/data/analytics/hubble/developer-guide/backfill/data-import) <br></br> **Pros:** Cheap and fast <br></br>- Option 2: Re-trigger DAGs for past dates <br></br> **Cons:** Slow and expensive |
+| Bug Fix | You resolved a bug and need to re-ingest a specific data column/s or back fix a data column | - Option 1. [JS UDF](/docs/data/analytics/hubble/developer-guide/backfill/JS-UDF) <br></br> **Pros:** Cheap and fast <br></br> **Cons:** May need optimized query writing and running in batches <br></br> - Option 2: Re-trigger DAGs for past dates <br></br> **Cons:** Slow and expensive |
+| New data column extraction | You added a new data column/s as part of a feature request and need to backfill data for the newly added column/s | - Option 1. [JS UDF](/docs/data/analytics/hubble/developer-guide/backfill/JS-UDF) <br></br> **Pros:** Cheap and fast <br></br> **Cons:** May need optimized query writing and running in batches <br></br> - Option 2: Re-trigger DAGs for past dates <br></br> **Cons:** Slow and expensive |
+
+<CardGroup cols={2}>
+  <Card title="Backfill using JS UDF" icon="file-lines" href="/docs/data/analytics/hubble/developer-guide/backfill/JS-UDF">
+
+    This document outlines methods to extract required fields from the XDR of raw data.
+
+  </Card>
+  <Card title="Data Import" icon="file-lines" href="/docs/data/analytics/hubble/developer-guide/backfill/data-import">
+
+    This document outlines methods to perform inital backfill when setting up hubble.
+
+  </Card>
+</CardGroup>
diff --git a/docs/data/analytics/hubble/developer-guide/connecting-to-bigquery/README.mdx b/docs/data/analytics/hubble/developer-guide/connecting-to-bigquery/README.mdx
deleted file mode 100644
index a1e79f9f5..000000000
--- a/docs/data/analytics/hubble/developer-guide/connecting-to-bigquery/README.mdx
+++ /dev/null
@@ -1,144 +0,0 @@
----
-title: "Connecting"
-sidebar_position: 10
----
-
-BigQuery offers multiple connection methods to Hubble. This guide details three common methods:
-
-- [BigQuery UI](#bigquery-ui) - analysts that need to perform ad hoc analysis using SQL
-- [BigQuery SDK](#bigquery-sdk) - developers that need to integrate data into applications
-- [Looker Studio](#looker-studio) - business people that need to visualize data
-
-## Prerequisites
-
-To access Hubble, you will need a Google Cloud Project with billing and the BigQuery API enabled. For more information, please follow the instructions provided by [Google Cloud](https://cloud.google.com/bigquery/docs/quickstarts/query-public-dataset-console).
-
-Google does provide a BigQuery Sandbox for free that allows users to explore datasets in a limited capacity.
-
-## BigQuery UI
-
-1. From a browser, open the [crypto-stellar.crypto_stellar](http://console.cloud.google.com/bigquery?ws=!1m4!1m3!3m2!1scrypto-stellar!2scrypto_stellar) dataset.
-2. This will open the public dataset `crypto_stellar`, where you can browse its contents in the **Explorer** pane.
-3. Click the **star** icon in the Explorer pane. This will favorite the dataset for you. More detailed information about starring resources can be found [here](https://cloud.google.com/bigquery/docs/bigquery-web-ui#star_resources).
-
-:::note
-
-Hubble cannot be found from the Explorer pane! You cannot search for the dataset. To view the dataset, you **must** use the [dataset link](https://console.cloud.google.com/bigquery?ws=!1m4!1m3!3m2!1scrypto-stellar!2scrypto_stellar).
-
-:::
-
-Copy and paste the following example query in the Editor:
-
-<CodeExample>
-
-```sql
-select
-  account_id,
-  balance
-from `crypto-stellar.crypto_stellar.accounts_current`
-order by balance desc;
-```
-
-</CodeExample>
-
-This query will return the XLM balances for all Stellar wallet addresses, ordered from largest to smallest amounts.
-
-## BigQuery SDK
-
-There are multiple [BigQuery API Client Libraries](https://cloud.google.com/bigquery/docs/reference/libraries) available.
-
-The following example uses Python to access the Hubble dataset. Use [this guide](https://cloud.google.com/python/docs/setup) for help setting up a python development environment.
-
-Install the client library locally, and configure your environment to use your Google Cloud Project:
-
-<CodeExample>
-
-```bash
-# verify python version
-python3 --version
-# if you do not have pip, install it
-python -m pip install --upgrade pip
-
-# install bigquery client library
-pip install --upgrade google-cloud-bigquery
-gcloud config set project PROJECT_ID
-```
-
-</CodeExample>
-
-Use the Python Interpreter to run the example below to list the tables available in Hubble:
-
-<CodeExample>
-
-```python
-from google.cloud import bigquery
-
-# Construct a BigQuery client object.
-client = bigquery.Client()
-
-dataset_id = 'crypto-stellar.crypto_stellar'
-
-# Make an API request
-tables = client.list_tables(dataset_id)
-
-# List the tables found in Hubble
-print(f'Tables contained in {dataset_id}':)
-for table in tables:
-    print(f'{table.project}.{table.dataset_id}.{table.table_id}')
-```
-
-</CodeExample>
-
-Run the example below to run a query and print the results:
-
-<CodeExample>
-
-```python
-from google.cloud import bigquery
-
-# Construct a BigQuery client object.
-client = bigquery.Client()
-
-query = """
-SELECT
- account_id,
- balance,
-FROM `crypto-stellar.crypto_stellar.accounts_current`
-ORDER BY balance DESC
-LIMIT 10;
-"""
-
-# Make an API request
-query_job = client.query(query)
-
-print("The query data:")
-for row in query_job:
-    # Row values can be accessed by field name or index.
-    print(f'account_id={row[0]}, balance={row["balance"]}')
-```
-
-</CodeExample>
-
-There are various ways to extract and load data using BigQuery. See the [BigQuery Client Documentation](https://cloud.google.com/python/docs/reference/bigquery/latest/google.cloud.bigquery.client.Client) for more information.
-
-## Looker Studio
-
-[Looker Studio](https://cloud.google.com/looker-studio) is a business intelligence tool that can be used to connect to and visualize data from the Hubble dataset.
-
-To connect Hubble as a data source:
-
-1. Open [Looker Studio](https://lookerstudio.google.com)
-2. Click on **Create** > **Data Source**
-3. Search for the BigQuery connector
-4. _(Optional)_ Change the name of the data source at the top of the webpage
-5. Click _Shared Projects_ > Select your Google Cloud Project
-6. Enter `crypto-stellar` as the Shared Project name
-7. Click on the Dataset `crypto_stellar`
-8. Select the desired table to connect
-9. Click `CONNECT` on the top right of the webpage.
-
-And you're connected!
-
-General information about Looker Studio can be found [here](https://support.google.com/looker-studio).
-
-General information about connecting data sources can be found [here](https://support.google.com/looker-studio/topic/6370331?hl=en&ref_topic=7441382&sjid=14945902445646860578-NA).
diff --git a/docs/data/analytics/hubble/developer-guide/connecting-to-bigquery/index.mdx b/docs/data/analytics/hubble/developer-guide/connecting-to-bigquery/index.mdx
new file mode 100644
index 000000000..593598509
--- /dev/null
+++ b/docs/data/analytics/hubble/developer-guide/connecting-to-bigquery/index.mdx
@@ -0,0 +1,144 @@
+---
+title: "Connecting"
+description: "BigQuery offers multiple connection methods to Hubble."
+---
+
+BigQuery offers multiple connection methods to Hubble. This guide details three common methods:
+
+- [BigQuery UI](#bigquery-ui) - analysts that need to perform ad hoc analysis using SQL
+- [BigQuery SDK](#bigquery-sdk) - developers that need to integrate data into applications
+- [Looker Studio](#looker-studio) - business people that need to visualize data
+
+## Prerequisites
+
+To access Hubble, you will need a Google Cloud Project with billing and the BigQuery API enabled. For more information, please follow the instructions provided by [Google Cloud](https://cloud.google.com/bigquery/docs/quickstarts/query-public-dataset-console).
+
+Google does provide a BigQuery Sandbox for free that allows users to explore datasets in a limited capacity.
+
+## BigQuery UI
+
+1. From a browser, open the [crypto-stellar.crypto_stellar](http://console.cloud.google.com/bigquery?ws=!1m4!1m3!3m2!1scrypto-stellar!2scrypto_stellar) dataset.
+2. This will open the public dataset `crypto_stellar`, where you can browse its contents in the **Explorer** pane.
+3. Click the **star** icon in the Explorer pane. This will favorite the dataset for you. More detailed information about starring resources can be found [here](https://cloud.google.com/bigquery/docs/bigquery-web-ui#star_resources).
+
+<Note>
+
+Hubble cannot be found from the Explorer pane! You cannot search for the dataset. To view the dataset, you **must** use the [dataset link](https://console.cloud.google.com/bigquery?ws=!1m4!1m3!3m2!1scrypto-stellar!2scrypto_stellar).
+
+</Note>
+
+Copy and paste the following example query in the Editor:
+
+<CodeGroup>
+
+```sql SQL
+select
+  account_id,
+  balance
+from `crypto-stellar.crypto_stellar.accounts_current`
+order by balance desc;
+```
+
+</CodeGroup>
+
+This query will return the XLM balances for all Stellar wallet addresses, ordered from largest to smallest amounts.
+
+## BigQuery SDK
+
+There are multiple [BigQuery API Client Libraries](https://cloud.google.com/bigquery/docs/reference/libraries) available.
+
+The following example uses Python to access the Hubble dataset. Use [this guide](https://cloud.google.com/python/docs/setup) for help setting up a python development environment.
+
+Install the client library locally, and configure your environment to use your Google Cloud Project:
+
+<CodeGroup>
+
+```bash bash
+# verify python version
+python3 --version
+# if you do not have pip, install it
+python -m pip install --upgrade pip
+
+# install bigquery client library
+pip install --upgrade google-cloud-bigquery
+gcloud config set project PROJECT_ID
+```
+
+</CodeGroup>
+
+Use the Python Interpreter to run the example below to list the tables available in Hubble:
+
+<CodeGroup>
+
+```python Python
+from google.cloud import bigquery
+
+# Construct a BigQuery client object.
+client = bigquery.Client()
+
+dataset_id = 'crypto-stellar.crypto_stellar'
+
+# Make an API request
+tables = client.list_tables(dataset_id)
+
+# List the tables found in Hubble
+print(f'Tables contained in {dataset_id}':)
+for table in tables:
+    print(f'{table.project}.{table.dataset_id}.{table.table_id}')
+```
+
+</CodeGroup>
+
+Run the example below to run a query and print the results:
+
+<CodeGroup>
+
+```python Python
+from google.cloud import bigquery
+
+# Construct a BigQuery client object.
+client = bigquery.Client()
+
+query = """
+SELECT
+ account_id,
+ balance,
+FROM `crypto-stellar.crypto_stellar.accounts_current`
+ORDER BY balance DESC
+LIMIT 10;
+"""
+
+# Make an API request
+query_job = client.query(query)
+
+print("The query data:")
+for row in query_job:
+    # Row values can be accessed by field name or index.
+    print(f'account_id={row[0]}, balance={row["balance"]}')
+```
+
+</CodeGroup>
+
+There are various ways to extract and load data using BigQuery. See the [BigQuery Client Documentation](https://cloud.google.com/python/docs/reference/bigquery/latest/google.cloud.bigquery.client.Client) for more information.
+
+## Looker Studio
+
+[Looker Studio](https://cloud.google.com/looker-studio) is a business intelligence tool that can be used to connect to and visualize data from the Hubble dataset.
+
+To connect Hubble as a data source:
+
+1. Open [Looker Studio](https://lookerstudio.google.com)
+2. Click on **Create** > **Data Source**
+3. Search for the BigQuery connector
+4. _(Optional)_ Change the name of the data source at the top of the webpage
+5. Click _Shared Projects_ > Select your Google Cloud Project
+6. Enter `crypto-stellar` as the Shared Project name
+7. Click on the Dataset `crypto_stellar`
+8. Select the desired table to connect
+9. Click `CONNECT` on the top right of the webpage.
+
+And you're connected!
+
+General information about Looker Studio can be found [here](https://support.google.com/looker-studio).
+
+General information about connecting data sources can be found [here](https://support.google.com/looker-studio/topic/6370331?hl=en&ref_topic=7441382&sjid=14945902445646860578-NA).
diff --git a/docs/data/analytics/hubble/developer-guide/data-curation/README.mdx b/docs/data/analytics/hubble/developer-guide/data-curation/README.mdx
deleted file mode 100644
index 9cf6c8b76..000000000
--- a/docs/data/analytics/hubble/developer-guide/data-curation/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Data Curation
-sidebar_position: 20
----
-
-import DocCardList from "@theme/DocCardList";
-
-Running stellar-dbt-public to transform raw Stellar network data into something better.
-
-<DocCardList />
diff --git a/docs/data/analytics/hubble/developer-guide/data-curation/architecture.mdx b/docs/data/analytics/hubble/developer-guide/data-curation/architecture.mdx
index 001650067..e9e6e187b 100644
--- a/docs/data/analytics/hubble/developer-guide/data-curation/architecture.mdx
+++ b/docs/data/analytics/hubble/developer-guide/data-curation/architecture.mdx
@@ -1,13 +1,11 @@
 ---
 title: Architecture
-sidebar_position: 10
+description: "In general stellar-dbt-public runs by."
 ---
 
-import stellar_dbt_arch from "/img/hubble/stellar_dbt_architecture.png";
-
 ## Architecture Overview
 
-<img src={stellar_dbt_arch} width="300" />
+<img src="/img/hubble/stellar_dbt_architecture.png" width="300" />
 
 In general stellar-dbt-public runs by:
 
diff --git a/docs/data/analytics/hubble/developer-guide/data-curation/getting-started.mdx b/docs/data/analytics/hubble/developer-guide/data-curation/getting-started.mdx
index d7d625ec9..3d4091885 100644
--- a/docs/data/analytics/hubble/developer-guide/data-curation/getting-started.mdx
+++ b/docs/data/analytics/hubble/developer-guide/data-curation/getting-started.mdx
@@ -1,6 +1,6 @@
 ---
 title: Getting Started
-sidebar_position: 20
+description: "stellar-dbt-public GitHub repository."
 ---
 
 [stellar-dbt-public GitHub repository](https://github.com/stellar/stellar-dbt-public/tree/master)
diff --git a/docs/data/analytics/hubble/developer-guide/data-curation/index.mdx b/docs/data/analytics/hubble/developer-guide/data-curation/index.mdx
new file mode 100644
index 000000000..6632c8db0
--- /dev/null
+++ b/docs/data/analytics/hubble/developer-guide/data-curation/index.mdx
@@ -0,0 +1,22 @@
+---
+title: Data Curation
+description: "Running stellar-dbt-public to transform raw Stellar network data into something better."
+---
+
+<CardGroup cols={2}>
+  <Card title="Overview" icon="file-lines" href="/docs/data/analytics/hubble/developer-guide/data-curation/overview">
+
+    Data curation in Hubble is done through stellar-dbt-public.
+
+  </Card>
+  <Card title="Architecture" icon="file-lines" href="/docs/data/analytics/hubble/developer-guide/data-curation/architecture">
+
+    In general stellar-dbt-public runs by.
+
+  </Card>
+  <Card title="Getting Started" icon="file-lines" href="/docs/data/analytics/hubble/developer-guide/data-curation/getting-started">
+
+    stellar-dbt-public GitHub repository.
+
+  </Card>
+</CardGroup>
diff --git a/docs/data/analytics/hubble/developer-guide/data-curation/overview.mdx b/docs/data/analytics/hubble/developer-guide/data-curation/overview.mdx
index 9dd9ba30a..ab934ae76 100644
--- a/docs/data/analytics/hubble/developer-guide/data-curation/overview.mdx
+++ b/docs/data/analytics/hubble/developer-guide/data-curation/overview.mdx
@@ -1,11 +1,11 @@
 ---
 title: "Overview"
-sidebar_position: 0
+description: "Data curation in Hubble is done through stellar-dbt-public."
 ---
 
 Data curation in Hubble is done through [stellar-dbt-public](https://github.com/stellar/stellar-dbt-public). stellar-dbt-public transforms raw Stellar network data from BigQuery datasets and tables into aggregates for more user friendly analytics.
 
-It is worth noting that most users will not need to standup and run their own stellar-dbt-public instance. The Stellar Development Foundation provides public access to fully transformed Stellar network data through the public datasets and tables in GCP BigQuery. Instructions on how to access this data can be found in the [Connecting](../../developer-guide/connecting-to-bigquery/README.mdx) section.
+It is worth noting that most users will not need to standup and run their own stellar-dbt-public instance. The Stellar Development Foundation provides public access to fully transformed Stellar network data through the public datasets and tables in GCP BigQuery. Instructions on how to access this data can be found in the [Connecting](/docs/data/analytics/hubble/developer-guide/connecting-to-bigquery) section.
 
 ## Why Run stellar-dbt-public?
 
diff --git a/docs/data/analytics/hubble/developer-guide/index.mdx b/docs/data/analytics/hubble/developer-guide/index.mdx
new file mode 100644
index 000000000..4ff8e1925
--- /dev/null
+++ b/docs/data/analytics/hubble/developer-guide/index.mdx
@@ -0,0 +1,38 @@
+---
+title: Developer Guide
+description: "All you need to know about running a Hubble analytics platform."
+sidebar_key: hubble-developer-guide
+---
+
+<CardGroup cols={2}>
+  <Card title="Backfill" icon="box-archive" href="/docs/data/analytics/hubble/developer-guide/backfill">
+
+    2 items
+
+  </Card>
+  <Card title="Connecting" icon="file-lines" href="/docs/data/analytics/hubble/developer-guide/connecting-to-bigquery">
+
+    BigQuery offers multiple connection methods to Hubble.
+
+  </Card>
+  <Card title="Source System Ingestion" icon="box-archive" href="/docs/data/analytics/hubble/developer-guide/source-system-ingestion">
+
+    3 items
+
+  </Card>
+  <Card title="Data Curation" icon="box-archive" href="/docs/data/analytics/hubble/developer-guide/data-curation">
+
+    3 items
+
+  </Card>
+  <Card title="Visualization" icon="box-archive" href="/docs/data/analytics/hubble/developer-guide/visualization">
+
+    2 items
+
+  </Card>
+  <Card title="Scheduling and Orchestration" icon="box-archive" href="/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration">
+
+    3 items
+
+  </Card>
+</CardGroup>
diff --git a/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/README.mdx b/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/README.mdx
deleted file mode 100644
index 66ede6b7b..000000000
--- a/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Scheduling and Orchestration
-sidebar_position: 100
----
-
-import DocCardList from "@theme/DocCardList";
-
-Stitching all the components together.
-
-<DocCardList />
diff --git a/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/architecture.mdx b/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/architecture.mdx
index 21be8c3df..ec9c69f47 100644
--- a/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/architecture.mdx
+++ b/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/architecture.mdx
@@ -1,13 +1,11 @@
 ---
 title: Architecture
-sidebar_position: 10
+description: "In general stellar-etl-airflow runs by."
 ---
 
-import stellar_etl_airflow_arch from "/img/hubble/stellar_etl_airflow_architecture.png";
-
 ## Architecture Overview
 
-<img src={stellar_etl_airflow_arch} width="300" />
+<img src="/img/hubble/stellar_etl_airflow_architecture.png" width="300" />
 
 In general stellar-etl-airflow runs by:
 
diff --git a/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/getting-started.mdx b/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/getting-started.mdx
index 5eb25a067..2617c2201 100644
--- a/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/getting-started.mdx
+++ b/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/getting-started.mdx
@@ -1,33 +1,29 @@
 ---
 title: Getting Started
-sidebar_position: 20
+description: "stellar-etl-airflow GitHub repository."
 ---
 
-import history_table_export from "/img/hubble/history_table_export.png";
-import state_table_export from "/img/hubble/state_table_export.png";
-import dbt_enriched_base_tables from "/img/hubble/dbt_enriched_base_tables.png";
-
 [stellar-etl-airflow GitHub repository](https://github.com/stellar/stellar-etl-airflow/tree/master)
 
 ## GCP Account Setup
 
-[The SDF](../../../../../learn/glossary.mdx#stellar-development-foundation-sdf) runs Hubble in GCP using Composer and BigQuery. To follow the same deployment you will need to have access to a GCP project. Instructions can be found in the [Get Started](https://cloud.google.com/docs/get-started) documentation from Google.
+[The SDF](../../../../../learn/glossary#stellar-development-foundation-sdf) runs Hubble in GCP using Composer and BigQuery. To follow the same deployment you will need to have access to a GCP project. Instructions can be found in the [Get Started](https://cloud.google.com/docs/get-started) documentation from Google.
 
-:::note
+<Note>
 
 BigQuery and Composer should be available by default. If they are not you can find instructions for enabling them in the [BigQuery](https://cloud.google.com/bigquery?hl=en) or [Composer](https://cloud.google.com/composer?hl=en) Google documentation.
 
-:::
+</Note>
 
 ## Create GCP Composer Instance to Run Airflow
 
 Instructions on bringing up a GCP Composer instance to run Hubble can be found in the [Installation and Setup](https://github.com/stellar/stellar-etl-airflow?tab=readme-ov-file#installation-and-setup) section in the [stellar-etl-airflow](https://github.com/stellar/stellar-etl-airflow) repository.
 
-:::note
+<Note>
 
 Hardware requirements can be very different depending on the Stellar network data you require. The default GCP settings may be higher/lower than actually required.
 
-:::
+</Note>
 
 ## Configuring GCP Composer Airflow
 
@@ -68,7 +64,7 @@ More information can be found [here](https://github.com/stellar/stellar-etl-airf
   - Optionally this can ingest data using captive-core but that is not ideal nor recommended for usage with Airflow
 - Inserts into BigQuery
 
-<img src={history_table_export} width="300" />
+<img src="/img/hubble/history_table_export.png" width="300" />
 
 ### State Table Export DAG
 
@@ -77,7 +73,7 @@ More information can be found [here](https://github.com/stellar/stellar-etl-airf
 - Exports accounts, account_signers, offers, claimable_balances, liquidity pools, trustlines, contract_data, contract_code, config_settings and ttl.
 - Inserts into BigQuery
 
-<img src={state_table_export} width="300" />
+<img src="/img/hubble/state_table_export.png" width="300" />
 
 ### DBT Enriched Base Tables DAG
 
@@ -88,4 +84,4 @@ More information can be found [here](https://github.com/stellar/stellar-etl-airf
 - Updates the current state tables
 - (Optional) warnings and errors are sent to slack.
 
-<img src={dbt_enriched_base_tables} width="300" />
+<img src="/img/hubble/dbt_enriched_base_tables.png" width="300" />
diff --git a/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/index.mdx b/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/index.mdx
new file mode 100644
index 000000000..27065e189
--- /dev/null
+++ b/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/index.mdx
@@ -0,0 +1,22 @@
+---
+title: Scheduling and Orchestration
+description: "Stitching all the components together."
+---
+
+<CardGroup cols={2}>
+  <Card title="Overview" icon="file-lines" href="/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/overview">
+
+    Hubble uses stellar-etl-airflow to schedule and orchestrate all its workflows.
+
+  </Card>
+  <Card title="Architecture" icon="file-lines" href="/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/architecture">
+
+    In general stellar-etl-airflow runs by.
+
+  </Card>
+  <Card title="Getting Started" icon="file-lines" href="/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/getting-started">
+
+    stellar-etl-airflow GitHub repository.
+
+  </Card>
+</CardGroup>
diff --git a/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/overview.mdx b/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/overview.mdx
index b8b0a9522..e1c503889 100644
--- a/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/overview.mdx
+++ b/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/overview.mdx
@@ -1,11 +1,11 @@
 ---
 title: "Overview"
-sidebar_position: 0
+description: "Hubble uses stellar-etl-airflow to schedule and orchestrate all its workflows. This includes the scheduling and running of stellar-etl and stellar-dbt."
 ---
 
 Hubble uses [stellar-etl-airflow](https://github.com/stellar/stellar-etl-airflow) to schedule and orchestrate all its workflows. This includes the scheduling and running of stellar-etl and stellar-dbt.
 
-It is worth noting that most users will not need to standup and run their own Hubble. The Stellar Development Foundation provides public access to the data through the public datasets and tables in GCP BigQuery. Instructions on how to access this data can be found in the [Connecting](../../developer-guide/connecting-to-bigquery/README.mdx) section.
+It is worth noting that most users will not need to standup and run their own Hubble. The Stellar Development Foundation provides public access to the data through the public datasets and tables in GCP BigQuery. Instructions on how to access this data can be found in the [Connecting](/docs/data/analytics/hubble/developer-guide/connecting-to-bigquery) section.
 
 ## Why Run stellar-etl-ariflow?
 
diff --git a/docs/data/analytics/hubble/developer-guide/source-system-ingestion/README.mdx b/docs/data/analytics/hubble/developer-guide/source-system-ingestion/README.mdx
deleted file mode 100644
index e62bbd323..000000000
--- a/docs/data/analytics/hubble/developer-guide/source-system-ingestion/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Source System Ingestion
-sidebar_position: 10
----
-
-import DocCardList from "@theme/DocCardList";
-
-Running stellar-etl for Stellar network data ingestion.
-
-<DocCardList />
diff --git a/docs/data/analytics/hubble/developer-guide/source-system-ingestion/architecture.mdx b/docs/data/analytics/hubble/developer-guide/source-system-ingestion/architecture.mdx
index 36abdd1aa..6e1a73b2e 100644
--- a/docs/data/analytics/hubble/developer-guide/source-system-ingestion/architecture.mdx
+++ b/docs/data/analytics/hubble/developer-guide/source-system-ingestion/architecture.mdx
@@ -1,16 +1,13 @@
 ---
 title: Architecture
-sidebar_position: 10
+description: "In general stellar-etl runs by."
 ---
 
-import stellar_arch from "/img/hubble/stellar_overall_architecture.png";
-import stellar_etl_arch from "/img/hubble/stellar_etl_architecture.png";
-
 ## Architecture Overview
 
-<img src={stellar_arch} width="600" />
+<img src="/img/hubble/stellar_overall_architecture.png" width="600" />
 
-<img src={stellar_etl_arch} width="300" />
+<img src="/img/hubble/stellar_etl_architecture.png" width="300" />
 
 In general stellar-etl runs by:
 
diff --git a/docs/data/analytics/hubble/developer-guide/source-system-ingestion/getting-started.mdx b/docs/data/analytics/hubble/developer-guide/source-system-ingestion/getting-started.mdx
index 8b09a67a7..becb6e445 100644
--- a/docs/data/analytics/hubble/developer-guide/source-system-ingestion/getting-started.mdx
+++ b/docs/data/analytics/hubble/developer-guide/source-system-ingestion/getting-started.mdx
@@ -1,6 +1,6 @@
 ---
 title: Getting Started
-sidebar_position: 20
+description: "stellar-etl GitHub repository."
 ---
 
 [stellar-etl GitHub repository](https://github.com/stellar/stellar-etl/tree/master)
diff --git a/docs/data/analytics/hubble/developer-guide/source-system-ingestion/index.mdx b/docs/data/analytics/hubble/developer-guide/source-system-ingestion/index.mdx
new file mode 100644
index 000000000..12d6de336
--- /dev/null
+++ b/docs/data/analytics/hubble/developer-guide/source-system-ingestion/index.mdx
@@ -0,0 +1,22 @@
+---
+title: Source System Ingestion
+description: "Running stellar-etl for Stellar network data ingestion."
+---
+
+<CardGroup cols={2}>
+  <Card title="Overview" icon="file-lines" href="/docs/data/analytics/hubble/developer-guide/source-system-ingestion/overview">
+
+    Stellar network data ingestion in Hubble is done through stellar-etl.
+
+  </Card>
+  <Card title="Architecture" icon="file-lines" href="/docs/data/analytics/hubble/developer-guide/source-system-ingestion/architecture">
+
+    In general stellar-etl runs by.
+
+  </Card>
+  <Card title="Getting Started" icon="file-lines" href="/docs/data/analytics/hubble/developer-guide/source-system-ingestion/getting-started">
+
+    stellar-etl GitHub repository.
+
+  </Card>
+</CardGroup>
diff --git a/docs/data/analytics/hubble/developer-guide/source-system-ingestion/overview.mdx b/docs/data/analytics/hubble/developer-guide/source-system-ingestion/overview.mdx
index beabcd5f9..b70a7371d 100644
--- a/docs/data/analytics/hubble/developer-guide/source-system-ingestion/overview.mdx
+++ b/docs/data/analytics/hubble/developer-guide/source-system-ingestion/overview.mdx
@@ -1,12 +1,12 @@
 ---
 title: "Overview"
-sidebar_position: 0
+description: "Stellar network data ingestion in Hubble is done through stellar-etl."
 ---
 
 Stellar network data ingestion in Hubble is done through [stellar-etl](https://github.com/stellar/stellar-etl/tree/master). stellar-etl reads and transforms Stellar network data into OLAP friendly JSON files.
 
 | Use Case | Recommended Solution | Reason |
 | --- | --- | --- |
-| Need commonly required data fields and do not want to take burden of setting up entire pipeline | Use output from SDF's stellar-etl instance i.e. [Connect to Bigquery and access hubble](../../developer-guide/connecting-to-bigquery/README.mdx) | It is worth noting that most users will not need to standup and run their own stellar-etl instance. The Stellar Development Foundation provides public access to fully transformed Stellar network data through the public datasets and tables in GCP BigQuery. |
-| Need custom data but do not want to take burden of setting up entire pipeline | Use [JS-UDF](../../developer-guide/backfill/JS-UDF.mdx) | Stellar-ETL does not parse every single field available in raw XDR, but it does save the raw transaction meta. JS-UDF helps to extract a field directly from XDR |
+| Need commonly required data fields and do not want to take burden of setting up entire pipeline | Use output from SDF's stellar-etl instance i.e. [Connect to Bigquery and access hubble](/docs/data/analytics/hubble/developer-guide/connecting-to-bigquery) | It is worth noting that most users will not need to standup and run their own stellar-etl instance. The Stellar Development Foundation provides public access to fully transformed Stellar network data through the public datasets and tables in GCP BigQuery. |
+| Need custom data but do not want to take burden of setting up entire pipeline | Use [JS-UDF](../../developer-guide/backfill/JS-UDF) | Stellar-ETL does not parse every single field available in raw XDR, but it does save the raw transaction meta. JS-UDF helps to extract a field directly from XDR |
 | Need custom and operationally independent data | Run [stellar-etl](https://github.com/stellar/stellar-etl/tree/master) | Running stellar-etl within your own infrastructure provides a number of benefits. You can: <br></br> - Have full operational control without dependency on the Stellar Development Foundation for network data <br></br> - Run modified ETL/ELT pipelines that fit your individual business needs |
diff --git a/docs/data/analytics/hubble/developer-guide/visualization/README.mdx b/docs/data/analytics/hubble/developer-guide/visualization/README.mdx
deleted file mode 100644
index 5719c6668..000000000
--- a/docs/data/analytics/hubble/developer-guide/visualization/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Visualization
-sidebar_position: 30
----
-
-import DocCardList from "@theme/DocCardList";
-
-Visualizing Stellar network data.
-
-<DocCardList />
diff --git a/docs/data/analytics/hubble/developer-guide/visualization/getting-started.mdx b/docs/data/analytics/hubble/developer-guide/visualization/getting-started.mdx
index 8600d0495..130800c77 100644
--- a/docs/data/analytics/hubble/developer-guide/visualization/getting-started.mdx
+++ b/docs/data/analytics/hubble/developer-guide/visualization/getting-started.mdx
@@ -1,6 +1,6 @@
 ---
 title: Getting Started
-sidebar_position: 20
+description: "This sections goes through using Google's Looker Studio as a free and easy to use visualization tool that you can hook up your BigQuery Stellar network data to."
 ---
 
 This sections goes through using [Google's Looker Studio](https://lookerstudio.google.com/u/0/navigation/reporting) as a free and easy to use visualization tool that you can hook up your BigQuery Stellar network data to.
diff --git a/docs/data/analytics/hubble/developer-guide/visualization/index.mdx b/docs/data/analytics/hubble/developer-guide/visualization/index.mdx
new file mode 100644
index 000000000..e521b38d5
--- /dev/null
+++ b/docs/data/analytics/hubble/developer-guide/visualization/index.mdx
@@ -0,0 +1,17 @@
+---
+title: Visualization
+description: "Visualizing Stellar network data."
+---
+
+<CardGroup cols={2}>
+  <Card title="Overview" icon="file-lines" href="/docs/data/analytics/hubble/developer-guide/visualization/overview">
+
+    There are various ways to visualize data from Hubble.
+
+  </Card>
+  <Card title="Getting Started" icon="file-lines" href="/docs/data/analytics/hubble/developer-guide/visualization/getting-started">
+
+    This sections goes through using Google's Looker Studio as a free and easy to use visualization tool that you can hook up your BigQuery Stellar network data to.
+
+  </Card>
+</CardGroup>
diff --git a/docs/data/analytics/hubble/developer-guide/visualization/overview.mdx b/docs/data/analytics/hubble/developer-guide/visualization/overview.mdx
index 3f94c2c76..b4aa31216 100644
--- a/docs/data/analytics/hubble/developer-guide/visualization/overview.mdx
+++ b/docs/data/analytics/hubble/developer-guide/visualization/overview.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Overview"
-sidebar_position: 0
+description: "There are various ways to visualize data from Hubble. This section explains how to use Google's Looker Studio to visualize Stellar network data."
 ---
 
 There are various ways to visualize data from Hubble. This section explains how to use [Google's Looker Studio](https://cloud.google.com/looker-studio?hl=en) to visualize Stellar network data.
diff --git a/docs/data/analytics/hubble/index.mdx b/docs/data/analytics/hubble/index.mdx
new file mode 100644
index 000000000..d15a19537
--- /dev/null
+++ b/docs/data/analytics/hubble/index.mdx
@@ -0,0 +1,32 @@
+---
+title: Hubble
+description: "Hubble is an open-source, publicly available dataset that provides a complete historical record of the Stellar network."
+---
+
+## What is Hubble?
+
+Hubble is an open-source, publicly available dataset that provides a complete historical record of the Stellar network. It ingests and presents the data produced by the Stellar network in a format that is easier to consume than the performance-oriented data representations used by Stellar Core. The dataset is hosted on BigQuery–meaning it is suitable for large, analytic workloads, historical data retrieval and complex data aggregation. **Hubble should not be used for real-time data retrieval and cannot submit transactions to the network.** For real time use cases, we recommend [running an API server](/docs/data/apis/rpc/admin-guide).
+
+This guide describes when to use Hubble and how to connect. To view the underlying data structures, queries and examples, use the [Viewing Metadata](/docs/data/analytics/hubble/analyst-guide/viewing-metadata) and [Optimizing Queries](/docs/data/analytics/hubble/analyst-guide/optimizing-queries) tutorials.
+
+## Why Use Hubble?
+
+Some questions are hard to answer with the RPC API as its API is quite minimal. This is because its infrastructure is optimized for quick reads and writes so that it can process online transactions.
+
+This is where Hubble comes in. It is optimized to execute complex queries and scan large amounts of data. Hubble can store orders of magnitude more data than RPC and will not run into storage constraints. Queries that require pagination in RPC or timeout can be returned in a single query. Hubble empowers users to explore, analyze, and derive meaningful conclusions from the data without the burden of maintaining a database.
+
+Users should be aware of the following limitations:
+
+- Hubble is read-only; it cannot interact with the Stellar Network.
+- The database is updated in intraday batches. There is no guarantee for same-day data availability.
+- The SDF hosts a public instance of Hubble, and end users incur the cost to execute queries. Visit the [BigQuery Pricing Page](https://cloud.google.com/bigquery/pricing#analysis_pricing_models) to learn more.
+
+## Why We Chose BigQuery
+
+BigQuery is Google Cloud’s data warehouse that comes with some key features that fulfill Stellar’s analytic needs.
+
+First, BigQuery allows anyone to make a dataset publicly available. This means that the SDF can contribute open source repositories to build and maintain a data warehouse and also host a public instance.
+
+BigQuery also separates storage from compute, which makes it sustainable to host a public instance. The maintainer only has to pay the cost of storage without incurring the cost of the analytics running on the dataset.
+
+Most importantly, BigQuery is the de facto platform for blockchain datasets. By selecting BigQuery, Stellar Network data is located with other blockchain data, which allows for cross-chain analytics.
diff --git a/docs/data/analytics/index.mdx b/docs/data/analytics/index.mdx
new file mode 100644
index 000000000..f507f4a36
--- /dev/null
+++ b/docs/data/analytics/index.mdx
@@ -0,0 +1,18 @@
+---
+title: Analytics Overview
+description: "Learn about analytics and analytics providers on the Stellar network."
+---
+
+## [Hubble](/docs/data/analytics/hubble)
+
+Hubble is an open-source, read-only BigQuery data warehouse maintained by SDF that provides a complete historical record of the Stellar network, ideal for large-scale analysis of transactions, fees, and network trends. It is not suitable for real-time data needs or simple lookups, and its documentation focuses on exploratory analysis, connection methods, and query optimization. By offering a structured and query-ready dataset, Hubble enables users to explore Stellar network data without managing raw data pipelines.
+
+Within Hubble, the stellar-etl product powers the extraction and transformation of Stellar network data into BigQuery. This open-source pipeline allows developers to extend or customize data ingestion workflows based on their analytical needs. Stellar-etl provides flexibility in how data is processed, enabling users to extract specific ledger entries, operations, or event logs based on their requirements.
+
+## [Public Dashboards](/docs/data/analytics/public-dashboards)
+
+Public Dashboards is a directory of free, browser-based dashboards that track Stellar network activity, real-world assets, stablecoins, and DeFi. Most are maintained by ecosystem analytics platforms rather than SDF. Start here if you want to look at Stellar metrics without writing a query.
+
+## [Data Analytics Providers](/docs/data/analytics/analytics-providers/analytics-providers)
+
+Data Analytics Providers provide a complete historical record of Pubnet Stellar network data for analysis and insights. These platforms enable users to explore network trends but are not designed for real-time data access or transaction execution. The key difference is that these ecosystem platforms operate independently of SDF and provide metrics and dashboards about the Stellar network.
diff --git a/docs/data/analytics/public-dashboards.mdx b/docs/data/analytics/public-dashboards.mdx
index 584cd86f1..908f3beeb 100644
--- a/docs/data/analytics/public-dashboards.mdx
+++ b/docs/data/analytics/public-dashboards.mdx
@@ -1,12 +1,11 @@
 ---
 title: Public Dashboards
 description: A directory of free, public dashboards that track Stellar network activity, real-world assets, stablecoins, and DeFi.
-sidebar_position: 500
 ---
 
 This page lists public dashboards that show what is happening on the Stellar network. Every dashboard here can be opened in a browser without an account, though some platforms offer extra views to signed-in users. Most are built and maintained by third parties, not SDF, so refresh cadence and methodology vary by platform.
 
-If you want to run your own queries against the underlying data instead, see [Hubble](./hubble/README.mdx) or the [Data Analytics Providers](./analytics-providers/analytics-providers.mdx) page. For looking up a specific transaction, account, or contract, use a [block explorer](../../tools/developer-tools/block-explorers.mdx).
+If you want to run your own queries against the underlying data instead, see [Hubble](/docs/data/analytics/hubble) or the [Data Analytics Providers](./analytics-providers/analytics-providers) page. For looking up a specific transaction, account, or contract, use a [block explorer](../../tools/developer-tools/block-explorers).
 
 ## Network Overview
 
diff --git a/docs/data/apis/README.mdx b/docs/data/apis/README.mdx
deleted file mode 100644
index e84a6cd70..000000000
--- a/docs/data/apis/README.mdx
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: APIs Overview
-sidebar_position: 0
----
-
-Learn about the services that provide access to real-time Stellar network data
-
-| Features                | RPC | Horizon |
-| ----------------------- | --- | ------- |
-| Real-time Data          | ✅  | ✅      |
-| Historical Data         | ❌  | ❌\*    |
-| Smart Contracts         | ✅  | ❌      |
-| Transaction Simulation  | ✅  | ❌      |
-| Curated and Parsed Data | ❌  | ✅      |
-
-\*_Horizon can provide full historical data if you run your own instance, but it is not the recommended tool for that. Use [Hubble](../analytics/hubble/README.mdx) or [Galexie](../indexers/build-your-own/galexie/README.mdx) instead. For a side-by-side comparison of all four SDF data products, see [Compare Data Products](../README.mdx#compare-data-products)._
-
-## [RPC](./rpc/README.mdx)
-
-The RPC provides real-time access to the current state of the Stellar network, including account balances, smart contract states, and recent transaction queries (within a seven-day retention window), while also allowing transaction submission. It is designed to be simple, minimal, and scalable, making it ideal for applications and wallets that require live data availability.
-
-:::note
-
-RPC is the recommended API for accessing and interacting with Stellar network data in real-time.
-
-:::
-
-## [Horizon](./horizon/README.mdx)
-
-:::warning
-
-Horizon is nearing end-of-life and will eventually be deprecated in favor of Stellar RPC and [Portfolio APIs](../indexers/README.mdx#portfolio-apis). While it will continue to receive updates to maintain compatibility with upcoming protocol releases, it won't receive new feature development.
-
-If your application already uses Horizon, see [Migrate from Horizon to RPC](./migrate-from-horizon-to-rpc.mdx).
-
-:::
-
-Horizon is an API for accessing and interacting with Stellar network data.
diff --git a/docs/data/apis/horizon/README.mdx b/docs/data/apis/horizon/README.mdx
deleted file mode 100644
index cac632bfd..000000000
--- a/docs/data/apis/horizon/README.mdx
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: "Access Blockchain Data with Horizon API: Query Transactions, Accounts & More"
-sidebar_label: Horizon
-sidebar_position: 10
-description: "Learn how Horizon, the API for the Stellar network, enables access to blockchain data. Discover endpoints for querying transactions, accounts, and more."
----
-
-# Horizon Introduction
-
-:::info
-
-On August 1, 2024, the publicly accessible SDF-hosted Horizon had its historical data truncated to one year. That update optimized the performance of the publicly accessible Horizon and ensured a streamlined experience for all users. Consider third-party ecosystem providers of Horizon, which may provide a longer history retention window as well as other features.
-
-:::
-
-Horizon provides an HTTP API to data in the Stellar network. It ingests and re-serves the data produced by the Stellar network in a form that is easier to consume by the average application relative to the performance-oriented data representations used by Stellar Core. This API serves the bridge between apps and [Stellar Core](../../../validators/README.mdx). Projects like wallets, decentralized exchanges, and asset issuers use Horizon to submit transactions, query an account balance, or stream events like transactions to an account.
-
-Horizon can be accessed via cURL, a browser, or one of the [Stellar SDKs](../../../tools/sdks/README.mdx). To reduce the complexity of your project, we recommend you use an SDK instead of making direct API calls.
-
-This guide describes how to administer a production Horizon instance (refer to the [Developers' Blog](https://stellar.org/blog/developers/a-new-sun-on-the-horizon) for some background on the performance and architectural improvements of this major version bump). For information about developing on the Horizon codebase, check out the [Development Guide](https://github.com/stellar/stellar-horizon/blob/main/DEVELOPING.md).
-
-Before we begin, it's worth reiterating the sentiment echoed in the [Core Node](../../../validators/README.mdx) documentation: **we do not endorse running Horizon backed by a standalone Stellar Core instance**, and especially not by a _validating_ Stellar Core. These are two separate concerns, and decoupling them is important for both reliability and performance. Horizon instead manages its own, pared-down version of Stellar Core optimized for its own subset of needs (we'll refer to this as a "Captive Core" instance).
-
-## Why Run Horizon?
-
-Running Horizon within your own infrastructure provides a number of benefits. You can:
-
-- Have full operational control without dependency on the Stellar Development Foundation for network data and transaction submission to networks;
-- Run multiple instances for redundancy and scalability.
-
-The Stellar Development Foundation (SDF) runs two instances of Horizon:
-
-- [horizon-testnet.stellar.org](https://horizon-testnet.stellar.org) for interacting with the [testnet](../../../networks/README.mdx)
-- [horizon-futurenet.stellar.org](https://horizon-futurenet.stellar.org) for interacting with the [futurenet](../../..//README.mdx)
-
-## In These Docs
-
-- [Admin Guide](./admin-guide/README.mdx): how to set up your own Horizon instance.
-- [Structure](./api-reference/structure/README.mdx): how Horizon is structured.
-- [Resources](./api-reference/resources/README.mdx): descriptions of resources and their endpoints.
-- [Aggregations](./api-reference/aggregations/README.mdx): descriptions of specialized endpoints.
-- [Errors](./api-reference/errors/README.mdx): potential errors and what they mean.
diff --git a/docs/data/apis/horizon/admin-guide/README.mdx b/docs/data/apis/horizon/admin-guide/README.mdx
deleted file mode 100644
index f991dd872..000000000
--- a/docs/data/apis/horizon/admin-guide/README.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: Admin Guide
-sidebar_position: 15
-sidebar_key: horizon-admin-guide
----
-
-import DocCardList from "@theme/DocCardList";
-
-All you need to know about setting up, running, and using Horizon.
-
-<DocCardList />
diff --git a/docs/data/apis/horizon/admin-guide/configuring.mdx b/docs/data/apis/horizon/admin-guide/configuring.mdx
index 7b3adcb63..ccfaa06ba 100644
--- a/docs/data/apis/horizon/admin-guide/configuring.mdx
+++ b/docs/data/apis/horizon/admin-guide/configuring.mdx
@@ -1,14 +1,14 @@
 ---
 title: Configuring
-sidebar_position: 30
+description: "You are now ready to identify the configuration parameters needed to perform three important roles."
 ---
 
 ## Prerequisites
 
-- You have identified the [installation](./installing.mdx) method for the host system:
+- You have identified the [installation](./installing) method for the host system:
   - For bare-metal, you have two executables installed on the host operation system path: `stellar-horizon` and `stellar-core`.
   - For running Horizon image with Docker daemon, you will use the [stellar/stellar-horizon](https://hub.docker.com/r/stellar/stellar-horizon) hosted on Docker Hub. You have already pulled the stellar/stellar-horizon image via `docker pull stellar/stellar-horizon:<tag_version>` onto host. This image contains the `stellar-horizon` and `stellar-core` within.
-  - For Kubernetes with [Horizon Helm Chart](https://github.com/stellar/helm-charts/tree/main/charts/horizon), you have followed the [Install Horizon with Helm Chart](./installing.mdx#helm-chart-installation).
+  - For Kubernetes with [Horizon Helm Chart](https://github.com/stellar/helm-charts/tree/main/charts/horizon), you have followed the [Install Horizon with Helm Chart](./installing#helm-chart-installation).
 
 - [Initialize database](#initialize-horizon-database)
 
@@ -73,13 +73,13 @@ If setting `INGEST=false`, then **must** define the `STELLAR_CORE_URL` variable
 
 ### Ingestion
 
-If you have configured your deployment to perform the ingestion role, then it is **strongly** recommended to review [Ingestion](./ingestion.mdx) first and [Filtering](./ingestion-filtering.mdx) second and factor that into configuration parameters to achieve best performance related to your application requirements before proceeding further.
+If you have configured your deployment to perform the ingestion role, then it is **strongly** recommended to review [Ingestion](./ingestion) first and [Filtering](./ingestion-filtering) second and factor that into configuration parameters to achieve best performance related to your application requirements before proceeding further.
 
-- Horizon will create a sub-directory under the current working directory of the o/s process to store captive core runtime data files. Refer to [Prerequisites](./prerequisites.mdx) for the type and amount of storage recommended. You can override this location with the optional `CAPTIVE_CORE_STORAGE_PATH` environment variable, set to a directory on the file system where captive core will store the runtime files.
+- Horizon will create a sub-directory under the current working directory of the o/s process to store captive core runtime data files. Refer to [Prerequisites](./prerequisites) for the type and amount of storage recommended. You can override this location with the optional `CAPTIVE_CORE_STORAGE_PATH` environment variable, set to a directory on the file system where captive core will store the runtime files.
 
 ### `DISABLE_TX_SUB`
 
-This config parameter is optional, set as FALSE by default. Controls whether Horizon will accept HTTP requests to the `/tx` API endpoint and forward to the network. Refer to [Channel Accounts](../../../../build/guides/transactions/channel-accounts.mdx) for some recommendations on optional client transaction submission optimizations.
+This config parameter is optional, set as FALSE by default. Controls whether Horizon will accept HTTP requests to the `/tx` API endpoint and forward to the network. Refer to [Channel Accounts](../../../../build/guides/transactions/channel-accounts) for some recommendations on optional client transaction submission optimizations.
 
 - When set to FALSE, it requires **live** ingestion process to be running on the same database because Horizon depends on new ledgers from the network to confirm a transaction submission status, Horizon will report a startup error if it detects no **live** ingestion. Requires `INGEST=true` or `STELLAR_CORE_URL` to be defined for access to a Core instance.
 - When transaction submission is disabled by setting it to TRUE, Horizon will return 405 on POSTs to /tx.
@@ -100,7 +100,7 @@ This config parameter is optional, can be one of 'info', 'error', 'debug'.
 
 ### `HISTORY_RETENTION_COUNT`
 
-This config parameter is optional, it determines the maximum sliding window of historical network data to retain on the database from ingestion. The value is expressed as absolute ledger count, which is an indirect way to define a duration of time, each ledger being approximately 5 seconds. It is defaulted to 0, which means it will not purge any history from the database. To enact the recommended sliding window of one month, set this to 518400, which is the approximate number of ledgers in 30 days. Refer to [Compute Resources](./prerequisites.mdx) for how database storage space is closely related to this setting.
+This config parameter is optional, it determines the maximum sliding window of historical network data to retain on the database from ingestion. The value is expressed as absolute ledger count, which is an indirect way to define a duration of time, each ledger being approximately 5 seconds. It is defaulted to 0, which means it will not purge any history from the database. To enact the recommended sliding window of one month, set this to 518400, which is the approximate number of ledgers in 30 days. Refer to [Compute Resources](./prerequisites) for how database storage space is closely related to this setting.
 
 ## Passing Configurations to Horizon
 
@@ -109,13 +109,13 @@ The `stellar-horizon` binary searches process environment variables for configur
 ### Bare-metal
 
 - Non-package manager: use O/S environment variables to pass configurations. There are many tools you can use to manage them, such as [direnv](http://direnv.net) or [dotenv](https://github.com/bkeepers/dotenv).
-- [Package manager](./installing.mdx#package-manager): the provided `stellar-horizon-cmd` wrapper will start a new process and create environment variables in the process from `/etc/default/stellar-horizon` and then launch the 'stellar-horizon'. To set configurations, edit the file at `/etc/default/stellar-horizon`.
+- [Package manager](./installing#package-manager): the provided `stellar-horizon-cmd` wrapper will start a new process and create environment variables in the process from `/etc/default/stellar-horizon` and then launch the 'stellar-horizon'. To set configurations, edit the file at `/etc/default/stellar-horizon`.
 
-  :::info
+  <Info>
 
   This script invokes Horizon with the `stellar` user, so make sure that permissions for the user are set up accordingly. The current working directory should be writable for this user and the user should be able to execute the `stellar-horizon` and `stellar-core` binaries; etc.
 
-  :::
+  </Info>
 
 ### Containerized
 
@@ -167,4 +167,4 @@ With the config above, if there are no queries from a given client for 10 second
 
 ## Next Step
 
-After configuration is complete, you are now ready to proceed to [Running Horizon](./running.mdx)!
+After configuration is complete, you are now ready to proceed to [Running Horizon](./running)!
diff --git a/docs/data/apis/horizon/admin-guide/index.mdx b/docs/data/apis/horizon/admin-guide/index.mdx
new file mode 100644
index 000000000..e746fff34
--- /dev/null
+++ b/docs/data/apis/horizon/admin-guide/index.mdx
@@ -0,0 +1,58 @@
+---
+title: Admin Guide
+description: "All you need to know about setting up, running, and using Horizon."
+sidebar_key: horizon-admin-guide
+---
+
+<CardGroup cols={2}>
+  <Card title="Overview" icon="file-lines" href="/docs/data/apis/horizon/admin-guide/overview">
+
+    Horizon is a central component of the Stellar platform: it provides an HTTP API to data in the Stellar network.
+
+  </Card>
+  <Card title="Prerequisites" icon="file-lines" href="/docs/data/apis/horizon/admin-guide/prerequisites">
+
+    The Horizon service is responsible for synchronizing with the Stellar network and processing ledger data.
+
+  </Card>
+  <Card title="Installing" icon="file-lines" href="/docs/data/apis/horizon/admin-guide/installing">
+
+    To install Horizon in production or non-development environments, we recommend the following based on target infrastructure.
+
+  </Card>
+  <Card title="Configuring" icon="file-lines" href="/docs/data/apis/horizon/admin-guide/configuring">
+
+    You are now ready to identify the configuration parameters needed to perform three important roles.
+
+  </Card>
+  <Card title="Running" icon="file-lines" href="/docs/data/apis/horizon/admin-guide/running">
+
+    Once you have established the Horizon database and have identified the Horizon runtime config per host, you're ready to run Horizon.
+
+  </Card>
+  <Card title="Ingestion" icon="file-lines" href="/docs/data/apis/horizon/admin-guide/ingestion">
+
+    Horizon API provides most of its utility through ingested data, and your Horizon server can be configured to listen for and ingest transaction results from...
+
+  </Card>
+  <Card title="Monitoring" icon="file-lines" href="/docs/data/apis/horizon/admin-guide/monitoring">
+
+    Metrics are emitted from Horizon over HTTP in the de facto text-based exposition format.
+
+  </Card>
+  <Card title="Scaling" icon="file-lines" href="/docs/data/apis/horizon/admin-guide/scaling">
+
+    Horizon enables different logical tiers that can be scaled independently for increasing throughput, isolation, and availability.
+
+  </Card>
+  <Card title="Upgrading" icon="file-lines" href="/docs/data/apis/horizon/admin-guide/upgrading">
+
+    Here we'll describe the recommended steps for upgrading a Horizon 2.x installation.
+
+  </Card>
+  <Card title="Ingestion Filtering" icon="file-lines" href="/docs/data/apis/horizon/admin-guide/ingestion-filtering">
+
+    Ingestion Filtering enables Horizon operators to drastically reduce the storage footprint of the historical data in the Horizon database by white-listing...
+
+  </Card>
+</CardGroup>
diff --git a/docs/data/apis/horizon/admin-guide/ingestion-filtering.mdx b/docs/data/apis/horizon/admin-guide/ingestion-filtering.mdx
index 5db636acf..bfd9a9861 100644
--- a/docs/data/apis/horizon/admin-guide/ingestion-filtering.mdx
+++ b/docs/data/apis/horizon/admin-guide/ingestion-filtering.mdx
@@ -1,5 +1,6 @@
 ---
 title: Ingestion Filtering
+description: "Ingestion Filtering enables Horizon operators to drastically reduce the storage footprint of the historical data in the Horizon database by white-listing..."
 order: 46
 ---
 
@@ -23,7 +24,7 @@ Some key aspects to note about filtering behavior:
 - Filtering applies only to ingestion of historical data in the database, it does not affect how ingestion process maintains current state data stored in database, which is the last known ledger entry for each unique entity within accounts, trustlines, liquidity pools, offers. However, current state data consumes a relatively small amount of the overall storage capacity.
 - When filter rules are changed, they only apply to existing, running ingestion processes(**live** and **historical range**). They don't trigger any retro-active filtering or back-filling of existing historical data on the database.
   - When the filter rules are updated to include additional accounts or assets in the white-list, the related transactions from **live** ingestion will only appear in the historical database data once the filter rules have been updated using the Admin API. The same applies to **historical range** ingestion, where the new filter rules will only affect the data from the current ledger within its configured range at the time of the update.
-  - Updating the filter rules to include additional accounts or assets does not trigger automatic back-filling related to new entites in the historical database. To include prior history of newly white-listed entites in the database you can manually run a new [Historical Ingestion Range](./ingestion.mdx#ingesting-historical-data) after updating the filter rules.
+  - Updating the filter rules to include additional accounts or assets does not trigger automatic back-filling related to new entites in the historical database. To include prior history of newly white-listed entites in the database you can manually run a new [Historical Ingestion Range](./ingestion#ingesting-historical-data) after updating the filter rules.
   - When the filter rules are updated to remove accounts or assets previously defined on white-list, the historical data in the database will not be retroactively purged or filtered based on the updated rules. The data is stored in the history tables for the lifetime of the database or until the `HISTORY_RETENTION_COUNT` is exceeded. Once the retention limit is reached, Horizon will purge all historical data related to older ledgers, regardless of any filtering rules.
 - Filtering will not affect the performance or throughput rate of an ingestion process, it will remain consistent whether filter rules are present or not.
 
@@ -94,4 +95,4 @@ curl -X 'PUT' \
 
 2. Since this is new horizon database, and first filter rules, there is nothing more to do, and effectively stop here.
 
-3. However, for sake of exercise, suppose you already had Horizon running for a while and the database populated based on some filter rules, and these new rules were additional white-listings you just added. In this case, you choose whether you want to retro-actively back fill historical data on horizon database for these new white-listed entites from a prior time up to the present time, because they were originally dropped at prior ingestion time and not included on the database. If you decide you want to back fill, then you run a separate Horizon **historical range** ingestion process, refer to [Historical Ingestion Range](./ingestion.mdx#ingesting-historical-data) for steps:
+3. However, for sake of exercise, suppose you already had Horizon running for a while and the database populated based on some filter rules, and these new rules were additional white-listings you just added. In this case, you choose whether you want to retro-actively back fill historical data on horizon database for these new white-listed entites from a prior time up to the present time, because they were originally dropped at prior ingestion time and not included on the database. If you decide you want to back fill, then you run a separate Horizon **historical range** ingestion process, refer to [Historical Ingestion Range](./ingestion#ingesting-historical-data) for steps:
diff --git a/docs/data/apis/horizon/admin-guide/ingestion.mdx b/docs/data/apis/horizon/admin-guide/ingestion.mdx
index 2a004ae84..79e40c74b 100644
--- a/docs/data/apis/horizon/admin-guide/ingestion.mdx
+++ b/docs/data/apis/horizon/admin-guide/ingestion.mdx
@@ -1,6 +1,6 @@
 ---
 title: Ingestion
-sidebar_position: 45
+description: "Horizon API provides most of its utility through ingested data, and your Horizon server can be configured to listen for and ingest transaction results from..."
 ---
 
 Horizon API provides most of its utility through ingested data, and your Horizon server can be configured to listen for and ingest transaction results from the Stellar network. Ingestion enables API access to both current state (e.g. someone's balance) and historical state (e.g. someone's transaction history).
@@ -20,26 +20,26 @@ To keep your storage footprint small, we recommend the following:
 
 - Use **live** ingestion, use **historical** ingestion only in limited exceptional cases.
 - If your application requires access to all network data, no filtering can be done, we recommend limiting historical retention of ingested data to a sliding window of 1 month (`HISTORY_RETENTION_COUNT=518400`). Note that you must set this explicitly: Horizon's default is `HISTORY_RETENTION_COUNT=0`, which retains all history and never purges ingested data.
-- If your application can work on a [filtered network dataset](./ingestion-filtering.mdx) based on specific accounts and assets, then we recommend applying ingestion filter rules. When using filter rules, it provides benefit of choice in longer historical retention timeframe since the filtering is reducing the overall database size to such a degree, historical retention(`HISTORY_RETENTION_COUNT`) can be set in terms of years rather than months or even disabled(`HISTORY_RETENTION_COUNT=0`).
-- If you cannot limit your history retention window to 30 days and cannot use filter rules, we recommend considering [Stellar Hubble Data Warehouse](../../../analytics/hubble/README.mdx) for any historical data.
+- If your application can work on a [filtered network dataset](./ingestion-filtering) based on specific accounts and assets, then we recommend applying ingestion filter rules. When using filter rules, it provides benefit of choice in longer historical retention timeframe since the filtering is reducing the overall database size to such a degree, historical retention(`HISTORY_RETENTION_COUNT`) can be set in terms of years rather than months or even disabled(`HISTORY_RETENTION_COUNT=0`).
+- If you cannot limit your history retention window to 30 days and cannot use filter rules, we recommend considering [Stellar Hubble Data Warehouse](/docs/data/analytics/hubble) for any historical data.
 
 ### Ingesting Live Data
 
-This option is enabled by default and is the recommended mode of ingestion to run. It is controlled with environment configuration flag `INGEST`. Refer to [Configuration](./configuring.mdx) for how an instance of Horizon performs the ingestion role.
+This option is enabled by default and is the recommended mode of ingestion to run. It is controlled with environment configuration flag `INGEST`. Refer to [Configuration](./configuring) for how an instance of Horizon performs the ingestion role.
 
-For high availability requirements, **we recommend deploying more than one live ingesting instance**, as this makes it easier to avoid downtime during upgrades and adds resilience, ensuring you always have the latest network data (refer to [Ingestion Role Instance](./configuring.mdx#multiple-instance-deployment)).
+For high availability requirements, **we recommend deploying more than one live ingesting instance**, as this makes it easier to avoid downtime during upgrades and adds resilience, ensuring you always have the latest network data (refer to [Ingestion Role Instance](./configuring#multiple-instance-deployment)).
 
 ### Ingesting Historical Data
 
 Import network data from a past date range into the database:
 
-<CodeExample>
+<CodeGroup>
 
-```
+```text Example
 stellar-horizon db reingest range <start> <end>
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Running any historical range of ingestion requires coordination with the data retention configuration chosen. When setting a temporal limit on history with `HISTORY_RETENTION_COUNT=<LEDGER_COUNT>`, the temporal limit takes precedence, and any data ingested beyond that limit will be automatically purged.
 
@@ -51,9 +51,9 @@ You can run historical ingestion in parallel in background while your main Horiz
 
 You can parallelize the ingestion of target historical ledger range by dividing it into sequential slices of smaller ranges and run the db reingest range command for each sub-range in parallel as a separate process on the same or a different machine. The shorthand rule for best performance is to identify the number of CPU cores available per target machine, if multi-core, then add `--parallel-workers <num of cores>` to the command, this will enable the command to further parallelize internally within a single process using multiple threads and sub-divided smaller ranges.
 
-<CodeExample>
+<CodeGroup>
 
-```
+```text Example
 # target range 1 30000, on single machine with 1 CPU core
 horizon1> stellar-horizon db reingest range 1 30000
 
@@ -65,7 +65,7 @@ horizon1> stellar-horizon db reingest range 1 15000 --parallel-workers 2
 horizon2> stellar-horizon db reingest range 15001 30000 --parallel-workers 2
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Notes
 
@@ -75,7 +75,7 @@ horizon2> stellar-horizon db reingest range 15001 30000 --parallel-workers 2
 
 #### If more than five minutes has elapsed with no new ingested data:
 
-- Verify the host machine meets recommended [Prerequisites](./prerequisites.mdx).
+- Verify the host machine meets recommended [Prerequisites](./prerequisites).
 
 - Check Horizon log output.
   - If there are many `level=error` messages, it may point to an environmental issue, inability to access the database.
@@ -84,12 +84,12 @@ horizon2> stellar-horizon db reingest range 15001 30000 --parallel-workers 2
     tail -f horizon.log | | grep -E 'Processed ledger|Closed ledger'
     ```
     If you don't see output from this pipeline every couple of seconds for a new ledger then ingestion is not proceeding, look at full logs and see if any alternative messages are printing reasons to the contrary. May see lines mentioning 'catching up' When connecting to pubnet, as it can take up to 5 minutes for the captive core process started by Horizon to catch up to pubnet network.
-  - Check RAM usage on the machine, it's possible that system ran low on RAM and is using swap memory which will result in slow performance. Verify host machine meets minimum RAM [prerequisites](./prerequisites.mdx).
-  - Verify the read/write throughput speeds on the volume that current working directory for horizon process is using. Based on [prerequisites](./prerequisites.mdx), volume should have at least 10mb/s, one way to roughly verify this on host machine(linux/mac) command line:
+  - Check RAM usage on the machine, it's possible that system ran low on RAM and is using swap memory which will result in slow performance. Verify host machine meets minimum RAM [prerequisites](./prerequisites).
+  - Verify the read/write throughput speeds on the volume that current working directory for horizon process is using. Based on [prerequisites](./prerequisites), volume should have at least 10mb/s, one way to roughly verify this on host machine(linux/mac) command line:
     ```
     sudo dd if=/dev/zero of=/tmp/test_speed.img bs=1G count=1
     ```
 
 #### Monitoring Ingestion Process
 
-For high-availability deployments, it is recommended to implement monitoring of ingestion process for visibility on performance/health. Refer to [Monitoring](./monitoring.mdx) for accessing logs and metrics from Horizon. Stellar publishes the example [Horizon Grafana Dashboard](https://grafana.com/grafana/dashboards/13793-stellar-horizon), which demonstrates queries against key horizon ingestion metrics, specifically look at the `Local Ingestion Delay [Ledgers]` and `Last ledger age` in the `Health Summary` panel.
+For high-availability deployments, it is recommended to implement monitoring of ingestion process for visibility on performance/health. Refer to [Monitoring](./monitoring) for accessing logs and metrics from Horizon. Stellar publishes the example [Horizon Grafana Dashboard](https://grafana.com/grafana/dashboards/13793-stellar-horizon), which demonstrates queries against key horizon ingestion metrics, specifically look at the `Local Ingestion Delay [Ledgers]` and `Last ledger age` in the `Health Summary` panel.
diff --git a/docs/data/apis/horizon/admin-guide/installing.mdx b/docs/data/apis/horizon/admin-guide/installing.mdx
index b3627efc7..b137a5efe 100644
--- a/docs/data/apis/horizon/admin-guide/installing.mdx
+++ b/docs/data/apis/horizon/admin-guide/installing.mdx
@@ -1,6 +1,6 @@
 ---
 title: Installing
-sidebar_position: 20
+description: "To install Horizon in production or non-development environments, we recommend the following based on target infrastructure."
 ---
 
 To install Horizon in production or non-development environments, we recommend the following based on target infrastructure:
@@ -25,14 +25,14 @@ SDF publishes new releases to its custom Ubuntu repositories. Follow [this guide
 
 To proceed with installation:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 sudo apt update
 sudo apt install stellar-horizon stellar-core
 ```
 
-</CodeExample>
+</CodeGroup>
 
 #### Prebuilt Releases
 
@@ -48,29 +48,29 @@ Some shells (such as [zsh](https://www.zsh.org)) cache PATH lookups. You may nee
 
 If the deployment can be done on Kubernetes, there is a [Horizon Helm Chart](https://github.com/stellar/helm-charts/blob/main/charts/horizon) available. Install the [Helm CLI tool](https://helm.sh/docs/intro/install), if you haven't already on your workstation, minimum of version 3. Next, add the Stellar repo to the helm client's list of repos and confirm that you can view the list of available chart versions for the repo:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 helm repo add stellar https://helm.stellar.org/charts
 helm repo update stellar
 helm search repo stellar/horizon --versions --devel
 ```
 
-</CodeExample>
+</CodeGroup>
 
-Wait to install the Horizon Helm Chart, it will be done after [Configuring](./configuring.mdx) is completed and in [Running](./running.mdx).
+Wait to install the Horizon Helm Chart, it will be done after [Configuring](./configuring) is completed and in [Running](./running).
 
 If Kubernetes is not an option, the helm charts may still be good reference for showing how to configure and run the Horizon Docker container. Just run the helm command with `template` to display the generated Kubeneretes manifests, which demonstrate all the container configurations needed:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 git clone https://github.com/stellar/helm-charts; cd helm-charts
 helm template -f charts/horizon/values.yaml charts/horizon/
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## Next Step
 
-After installation is complete, you are now ready to proceed to [Configuring Horizon](./configuring.mdx)!
+After installation is complete, you are now ready to proceed to [Configuring Horizon](./configuring)!
diff --git a/docs/data/apis/horizon/admin-guide/monitoring.mdx b/docs/data/apis/horizon/admin-guide/monitoring.mdx
index 3a330117a..189c63453 100644
--- a/docs/data/apis/horizon/admin-guide/monitoring.mdx
+++ b/docs/data/apis/horizon/admin-guide/monitoring.mdx
@@ -1,6 +1,6 @@
 ---
 title: Monitoring
-sidebar_position: 60
+description: "Metrics are emitted from Horizon over HTTP in the de facto text-based exposition format."
 ---
 
 ## Metrics
@@ -111,6 +111,6 @@ Entering interactive mode (type "help" for commands, "o" for options)
 (pprof) web
 ```
 
-## I'm Stuck! Help!
+## I'm Stuck! Help! {#im-stuck-help}
 
 If any of the above steps don't work or you are otherwise prevented from correctly setting up Horizon, please join our community and let us know. Either post a question at [our Stack Exchange](https://stellar.stackexchange.com) or chat with us on [Horizon Discord](https://discord.com/channels/897514728459468821/912466080960766012) to ask for help.
diff --git a/docs/data/apis/horizon/admin-guide/overview.mdx b/docs/data/apis/horizon/admin-guide/overview.mdx
index 6f334b765..5dda3eebc 100644
--- a/docs/data/apis/horizon/admin-guide/overview.mdx
+++ b/docs/data/apis/horizon/admin-guide/overview.mdx
@@ -1,13 +1,13 @@
 ---
 title: "Overview"
-sidebar_position: 0
+description: "Horizon is a central component of the Stellar platform: it provides an HTTP API to data in the Stellar network."
 ---
 
 Horizon is a central component of the Stellar platform: it provides an HTTP API to data in the Stellar network. It ingests and re-serves the data produced by the Stellar network in a form that is easier to consume by the average application relative to the performance-oriented data representations used by Stellar Core.
 
 This guide describes how to administer a production Horizon instance (refer to the [Developers' Blog](https://stellar.org/blog/developers/a-new-sun-on-the-horizon) for some background on the performance and architectural improvements of this major version bump). For information about developing on the Horizon codebase, check out the [Development Guide](https://github.com/stellar/stellar-horizon/blob/main/internal/docs/DEVELOPING.md).
 
-Before we begin, it's worth reiterating the sentiment echoed in the [Run a Core Node](../../../../validators/README.mdx) guide: **we do not endorse running Horizon backed by a standalone Stellar Core instance**, and especially not by a _validating_ Stellar Core. These are two separate concerns, and decoupling them is important for both reliability and performance. Horizon instead manages its own, pared-down version of Stellar Core optimized for its own subset of needs (we'll refer to this as a "Captive Core" instance).
+Before we begin, it's worth reiterating the sentiment echoed in the [Run a Core Node](/docs/validators) guide: **we do not endorse running Horizon backed by a standalone Stellar Core instance**, and especially not by a _validating_ Stellar Core. These are two separate concerns, and decoupling them is important for both reliability and performance. Horizon instead manages its own, pared-down version of Stellar Core optimized for its own subset of needs (we'll refer to this as a "Captive Core" instance).
 
 ## Why Run Horizon?
 
diff --git a/docs/data/apis/horizon/admin-guide/prerequisites.mdx b/docs/data/apis/horizon/admin-guide/prerequisites.mdx
index acc086440..a1266121b 100644
--- a/docs/data/apis/horizon/admin-guide/prerequisites.mdx
+++ b/docs/data/apis/horizon/admin-guide/prerequisites.mdx
@@ -1,15 +1,15 @@
 ---
 title: Prerequisites
-sidebar_position: 10
+description: "The Horizon service is responsible for synchronizing with the Stellar network and processing ledger data."
 ---
 
-The Horizon service is responsible for synchronizing with the Stellar network and processing ledger data. To understand the scope of Horizon's services, please read the [configuring](./configuring.mdx) section before you move on to the prerequisites for computation.
+The Horizon service is responsible for synchronizing with the Stellar network and processing ledger data. To understand the scope of Horizon's services, please read the [configuring](./configuring) section before you move on to the prerequisites for computation.
 
-The Horizon service can be [installed](./installing.mdx) on bare metal or a virtual machine. It is natively supported on both Linux and Windows operating systems.
+The Horizon service can be [installed](./installing) on bare metal or a virtual machine. It is natively supported on both Linux and Windows operating systems.
 
 ## Single Instance Deployment Model
 
-For a basic setup using the [Single Instance Deployment model](./configuring.mdx#single-instance-deployment), you will need a sum of two distinct compute profiles:
+For a basic setup using the [Single Instance Deployment model](./configuring#single-instance-deployment), you will need a sum of two distinct compute profiles:
 
 - One for hosting the Horizon service
 - Another for hosting the PostgreSQL server
@@ -36,23 +36,23 @@ _\* Assuming a 30-day retention window for data storage._
 
 Please note that a minimum of PostgreSQL version 12 is required.
 
-These specifications assume a 30-day retention window for data storage. For a longer retention window, the system requirements will be higher. For more information about data ingestion, history retention, and managing storage, check the [ingestion](./ingestion.mdx) section.
+These specifications assume a 30-day retention window for data storage. For a longer retention window, the system requirements will be higher. For more information about data ingestion, history retention, and managing storage, check the [ingestion](./ingestion) section.
 
 ## Multiple Instance Deployment
 
-To achieve high availability, redundancy, and high throughput, refer to the [scaling](./scaling.mdx) documentation. It provides a detailed overview of several different deployment strategies you can employ, depending on the SLA you need your Horizon instance to achieve.
+To achieve high availability, redundancy, and high throughput, refer to the [scaling](./scaling) documentation. It provides a detailed overview of several different deployment strategies you can employ, depending on the SLA you need your Horizon instance to achieve.
 
 ## Network Access
 
 - Ensure that the Horizon instance can establish a connection with the PostgreSQL database instance. The default port for PostgreSQL is 5432.
 
-- A stable and fast network connection with the Internet is required for any Horizon instance running the ingestion role. This is to ensure it has efficient outbound connectivity to remote hosts in the [quorum set](../../../../validators/admin-guide/configuring.mdx#choosing-your-quorum-set) and [archive urls](../../../../validators/admin-guide/environment-preparation.mdx#history-archives) for the chosen Stellar network. During ingestion, the Horizon instance communicates with these hosts, receiving network transaction data through its local captive core sub-process.
+- A stable and fast network connection with the Internet is required for any Horizon instance running the ingestion role. This is to ensure it has efficient outbound connectivity to remote hosts in the [quorum set](../../../../validators/admin-guide/configuring#choosing-your-quorum-set) and [archive urls](../../../../validators/admin-guide/environment-preparation#history-archives) for the chosen Stellar network. During ingestion, the Horizon instance communicates with these hosts, receiving network transaction data through its local captive core sub-process.
 
-:::note
+<Note>
 
 Hardware requirements may increase as the Stellar network grows and/or if you're sharing resources or using custom configs.
 
-:::
+</Note>
 
 [c5d.2xlarge]: https://aws.amazon.com/ec2/instance-types/c5/
 [n4-standard-4]: https://cloud.google.com/compute/docs/general-purpose-machines#n4-standard
diff --git a/docs/data/apis/horizon/admin-guide/running.mdx b/docs/data/apis/horizon/admin-guide/running.mdx
index e205298f8..724ad0b5c 100644
--- a/docs/data/apis/horizon/admin-guide/running.mdx
+++ b/docs/data/apis/horizon/admin-guide/running.mdx
@@ -1,13 +1,13 @@
 ---
 title: Running
-sidebar_position: 40
+description: "Once you have established the Horizon database and have identified the Horizon runtime config per host, you're ready to run Horizon."
 ---
 
-Once you have [established the Horizon database](./configuring.mdx#initialize-horizon-database) and have [identified the Horizon runtime config per host](./configuring.mdx#prerequisites), you're ready to run Horizon.
+Once you have [established the Horizon database](./configuring#initialize-horizon-database) and have [identified the Horizon runtime config per host](./configuring#prerequisites), you're ready to run Horizon.
 
 ## Bare-metal installation
 
-Run the `stellar-horizon` binary with the [appropriate environment parameters](./configuring.mdx#passing-configurations-to-horizon) set (or `stellar-horizon-cmd serve` if you [installed via the package manager](./installing.mdx#package-manager), which will automatically import your configuration from `/etc/default/stellar-horizon`).
+Run the `stellar-horizon` binary with the [appropriate environment parameters](./configuring#passing-configurations-to-horizon) set (or `stellar-horizon-cmd serve` if you [installed via the package manager](./installing#package-manager), which will automatically import your configuration from `/etc/default/stellar-horizon`).
 
 ## Containerized installation
 
@@ -15,17 +15,17 @@ You don't execute the Horizon binary directly, instead the [stellar/stellar-hori
 
 ### Docker daemon
 
-Use `docker run stellar/stellar-horizon:<tag_version> --env-file <env_filename>`, and specify each Horizon configuration flag identified during [Configuring](./configuring.mdx) as a separate line in `<env_filename>` of `HORIZON_CONFIG_PARAM=value`.
+Use `docker run stellar/stellar-horizon:<tag_version> --env-file <env_filename>`, and specify each Horizon configuration flag identified during [Configuring](./configuring) as a separate line in `<env_filename>` of `HORIZON_CONFIG_PARAM=value`.
 
 ### Kubernetes using Helm Chart
 
-Ensure you have followed the [pre-requisite](./installing.mdx#helm-chart-installation) of installing the Helm CLI tool and added the Stellar chart repo to Helm client.
+Ensure you have followed the [pre-requisite](./installing#helm-chart-installation) of installing the Helm CLI tool and added the Stellar chart repo to Helm client.
 
-The Horizon process [requires access to a Postgres 12 database](./prerequisites.mdx#postgresql-database-server-compute-instance). First use the common Kubernetes CLI tool `kubectl` from your workstation to create a Kubernetes secret on the intended namespace of the Kubernetes cluster which will hold the Horizon database URL.
+The Horizon process [requires access to a Postgres 12 database](./prerequisites#postgresql-database-server-compute-instance). First use the common Kubernetes CLI tool `kubectl` from your workstation to create a Kubernetes secret on the intended namespace of the Kubernetes cluster which will hold the Horizon database URL.
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 # copy your horizon DATABASE_URL into a secure file, no line breaks.
 echo -n 'database_url_here' > my_creds.txt
 
@@ -36,13 +36,13 @@ my-db-secret \
 --from-file=DATABASE_URL=my_creds.txt
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Now deploy Horizon onto the cluster using the Helm Chart:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 helm install my-horizon stellar/horizon \
 --namespace my-horizon-namespace-on-cluster \
 --set ingest.persistence.enabled=true \
@@ -59,24 +59,24 @@ helm install my-horizon stellar/horizon \
 --set ingest.resources.limits.memory=6Gi
 ```
 
-</CodeExample>
+</CodeGroup>
 
 This example of Helm Chart usage highlights some key aspects:
 
-- Uses the `global.network=[testnet|pubnet]` parameter, this automates generation of all the Horizon configuration parameters specific to the network such as archive urls, captive core config, and other parameters mentioned in [Configuring](./configuring.mdx).
+- Uses the `global.network=[testnet|pubnet]` parameter, this automates generation of all the Horizon configuration parameters specific to the network such as archive urls, captive core config, and other parameters mentioned in [Configuring](./configuring).
 - `global.image.horizon.tag` should be set to one of the Docker Hub tags published on [stellar/stellar-horizon](https://hub.docker.com/r/stellar/stellar-horizon)
 - Enables all roles on the deployment instance: ingesting and web API (includes transaction submission). If you choose to have a multi-instance deployment with each instance performing a single role of just web API or ingestion, then you will do two Helm installations, one for each role: `my-horizon-ingestion-installation` and `my-horizon-api-installation`. Each of these Helm installations will set `ingest.enabled`, `web.enabled`, `ingest.replicaCount`, `web.replicaCount` respectively for the role they are performing.
 - To customize further, the best approach is to download the [Horizon Helm Chart values.yaml](https://github.com/stellar/helm-charts/blob/main/charts/horizon/values.yaml), update the settings in your local copy of values.yaml, and pass to Helm install, rather than have many individual `--set` on Helm install:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 helm install myhorizon stellar/horizon \
 --namespace my-horizon-namespace-on-cluster \
 --values values.yaml
 ```
 
-</CodeExample>
+</CodeGroup>
 
 - Customizing network configuration parameters, If you want to connect to a network other than presets of `testnet` or `pubnet`, then you won't use `global.network`, instead, use local copy of [values.yaml](https://github.com/stellar/helm-charts/blob/main/charts/horizon/values.yaml) and set `ingest.coreConfig`, and refer to [\_core-config.tpl](https://github.com/stellar/helm-charts/blob/main/charts/horizon/templates/_core-config.tpl) for example of all the key/value pairs to include.
 
@@ -86,21 +86,21 @@ helm install myhorizon stellar/horizon \
 
 Once the Horizon process starts, it will emit logging to standard out. When run, you should see output similar to:
 
-<CodeExample>
+<CodeGroup>
 
-```
+```text Example
 INFO[...] Starting horizon on :8000                     pid=29013
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Note that the numbers may naturally be different for your installation. The log line above announces that Horizon is ready to serve client requests.
 
 Next, you can confirm that Horizon is responding correctly by loading the root resource. In the example above, that URL would be http://127.0.0.1:8000/, and simply running `curl http://127.0.0.1:8000/` would show you that the root resource loads correctly:
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 {
   "_links": {
     "account": {
@@ -116,6 +116,6 @@ Next, you can confirm that Horizon is responding correctly by loading the root r
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
-Refer to [Monitoring](./monitoring.mdx) for more details on Horizon runtime logging and metrics available.
+Refer to [Monitoring](./monitoring) for more details on Horizon runtime logging and metrics available.
diff --git a/docs/data/apis/horizon/admin-guide/scaling.mdx b/docs/data/apis/horizon/admin-guide/scaling.mdx
index 35dd65050..578077d71 100644
--- a/docs/data/apis/horizon/admin-guide/scaling.mdx
+++ b/docs/data/apis/horizon/admin-guide/scaling.mdx
@@ -1,6 +1,6 @@
 ---
 title: Scaling
-sidebar_position: 70
+description: "Horizon enables different logical tiers that can be scaled independently for increasing throughput, isolation, and availability."
 ---
 
 Horizon enables different logical tiers that can be scaled independently for increasing throughput, isolation, and availability. The following components can be independently scaled:
@@ -11,11 +11,11 @@ Horizon enables different logical tiers that can be scaled independently for inc
 
 ## Single Instance Deployment
 
-It is recommend to start with a [single instance deployment](./prerequisites.mdx), and scale up based on the needs of your particular use-case.
+It is recommend to start with a [single instance deployment](./prerequisites), and scale up based on the needs of your particular use-case.
 
-This [deployment](./configuring.mdx#single-instance-deployment) is intended for use with minimal history retention (\<= 30 days) and minimal request volume.
+This [deployment](./configuring#single-instance-deployment) is intended for use with minimal history retention (\<= 30 days) and minimal request volume.
 
-In this setup, a single instance of Horizon performs all three [roles](./configuring.mdx#multiple-instance-deployment); ingestion, transaction submission, and end-user API requests.
+In this setup, a single instance of Horizon performs all three [roles](./configuring#multiple-instance-deployment); ingestion, transaction submission, and end-user API requests.
 
 ![](/assets/horizon-scaling/Topology-single.png)
 
@@ -29,7 +29,7 @@ There are a few reasons you may choose to scale to multiple instances of Horizon
 
 Multiple instances of Horizon can be configured to point to the same database, and the ingestion process will not perform redundant work in these cases.
 
-When scaling Horizon, it is worth it to note that Horizon's [rate limiting](../api-reference/structure/rate-limiting.mdx) should be disabled and rate limiting should be managed external to Horizon within infrastructure. Horizon's rate limiting implementation is managed in-memory, so does not work with multiple instances.
+When scaling Horizon, it is worth it to note that Horizon's [rate limiting](../api-reference/structure/rate-limiting) should be disabled and rate limiting should be managed external to Horizon within infrastructure. Horizon's rate limiting implementation is managed in-memory, so does not work with multiple instances.
 
 ![](/assets/horizon-scaling/Topology-multiple.png)
 
@@ -37,7 +37,7 @@ When scaling Horizon, it is worth it to note that Horizon's [rate limiting](../a
 
 Ingestion is the process by which new ledgers are propagated into Horizon's database. It's health is critical, as degredations in performance can result in falling behind the last closed ledger, leaving your end-users unaware of the current state of the network, and unable to successfully submit new transactions. Any lag in ingestion would likely be considered downtime for your service
 
-Horizon allows you to independently configure the different [roles](./configuring.mdx#multiple-instance-deployment) that it performs, including ingestion. The below diagram illustrates how you could logically separate the instances serving API requests from the instances performing ingestion, and introduce a read-only replica database in order to further isolate these components. This setup has quite a few advantages:
+Horizon allows you to independently configure the different [roles](./configuring#multiple-instance-deployment) that it performs, including ingestion. The below diagram illustrates how you could logically separate the instances serving API requests from the instances performing ingestion, and introduce a read-only replica database in order to further isolate these components. This setup has quite a few advantages:
 
 - Each "role" Horizon plays can be independently scaled
 - API instances are significantly ligher weight from a hardware requirements perspective, since they do not need to run captive core
diff --git a/docs/data/apis/horizon/admin-guide/upgrading.mdx b/docs/data/apis/horizon/admin-guide/upgrading.mdx
index 33d48c40d..dd4e885ed 100644
--- a/docs/data/apis/horizon/admin-guide/upgrading.mdx
+++ b/docs/data/apis/horizon/admin-guide/upgrading.mdx
@@ -1,6 +1,6 @@
 ---
 title: Upgrading
-sidebar_position: 80
+description: "Here we'll describe the recommended steps for upgrading a Horizon 2.x installation."
 ---
 
 Here we'll describe the recommended steps for upgrading a Horizon 2.x installation.
@@ -9,9 +9,9 @@ Here we'll describe the recommended steps for upgrading a Horizon 2.x installati
 
 - An existing Horizon deployment consisting of one or more instances of Horizon.
 - All instances are on same 2.x version to begin.
-- If [bare-metal](./installing.mdx#bare-metal) install, you have shell, or command line access to each host having a Horizon installation.
-- If [deployed direct on Docker daemon](./installing.mdx#containerized), you have command line access to the host that is running the Docker daemon.
-- If [deployed on Kubernetes with Helm chart](./installing.mdx#helm-chart-installation), you have kubectl and helm command line tools on your workstation and a user login with appropriate access levels to change resources in target namespace of Horizon deployment on the cluster.
+- If [bare-metal](./installing#bare-metal) install, you have shell, or command line access to each host having a Horizon installation.
+- If [deployed direct on Docker daemon](./installing#containerized), you have command line access to the host that is running the Docker daemon.
+- If [deployed on Kubernetes with Helm chart](./installing#helm-chart-installation), you have kubectl and helm command line tools on your workstation and a user login with appropriate access levels to change resources in target namespace of Horizon deployment on the cluster.
 
 ### Assess current installation
 
@@ -20,13 +20,13 @@ Here we'll describe the recommended steps for upgrading a Horizon 2.x installati
   - Docker daemon deployments: the list of hosts and running containers is managed by you.
   - Kubernetes deployments: get the list of pods that are deployed from your prior Helm installation, they will have an annotation for `release=your_helm_horizon_installation_name`:
 
-    <CodeExample>
+    <CodeGroup>
 
-    ```bash
+    ```bash bash
     kubectl get pods -l release=your_helm_horizon_installation_name -n <your_horizon_namespace>
     ```
 
-    </CodeExample>
+    </CodeGroup>
 
 - Identify your current Horizon software version:
   - Obtain command line access to the operating system of each Horizon instance:
@@ -45,42 +45,42 @@ Now that you know your current Horizon version, visit [Horizon Releases](https:/
 
 Now that you have indentified the new version and are aware of the potential impacts from upgrading to new version based on release notes, such as state rebuilds and db migrations, you are informed and ready to proceed with upgrade.
 
-Upgrading production deployents should leverage a secondary, hot-backup deployment, also known as a [blue/green model](./scaling.mdx#scaling-to-multiple-instances) and perform the upgrade on the inactive deployment first. This will avoid downtime of system to your external users, as the upgrade takes place on the inactive deployment.
+Upgrading production deployents should leverage a secondary, hot-backup deployment, also known as a [blue/green model](./scaling#scaling-to-multiple-instances) and perform the upgrade on the inactive deployment first. This will avoid downtime of system to your external users, as the upgrade takes place on the inactive deployment.
 
 A good strategy for upgrading Horizon and applicable to single or multi-instance deployments - shut all instances down, install new Horizon version on one of the ingesting instances first. The reason being Horizon software will only initate `State Rebuild` and `DB Schema Migration` actions related to an upgrade on an instance that it detects ingestion has been enabled with configuration parameter, `INGEST=true`. This lowers complexity for you during the upgrade as you only need to focus on one instance and it avoids potential concurrent Horizon ingestion processes attempting the same upgrade on the database.
 
 - Bare-metal installations, stop the Horizon process on all instances first, then shell into one instance that is configured for ingestion, and use apt package manager on linux.
 
-  <CodeExample>
+  <CodeGroup>
 
-  ```bash
+  ```bash bash
   sudo apt update
   sudo apt install stellar-horizon=new_horizon_debian_pkg_version
   ```
 
-  </CodeExample>
+  </CodeGroup>
 
   Restart Horizon using the configuration already in place, but include `APPLY_MIGRATIONS=true` environment variable, this will trigger Horizon to automatically run any db migrations that it detects are needed.
 
 - Docker daemon deployments, stop all docker containers first, then choose one container that has ingestion enabled, set the new tag for the image based on release published on dockerhub - [stellar/stellar-horizon](https://hub.docker.com/r/stellar/stellar-horizon/tags), and restart the container in docker daemon, include `APPLY_MIGRATIONS=true` environment variable to the container envrionment, this will trigger Horizon to automatically run any db migrations that it detects are needed.
-- For Helm installations on Kubernetes, first use your helm cli tool to stop all Horizon instances by scaling all your Horizon installations(for ingest and web) down to 0 replicas, which you've created prior on [run steps](./running.mdx).
+- For Helm installations on Kubernetes, first use your helm cli tool to stop all Horizon instances by scaling all your Horizon installations(for ingest and web) down to 0 replicas, which you've created prior on [run steps](./running).
 
-  <CodeExample>
+  <CodeGroup>
 
-  ```bash
+  ```bash bash
   helm upgrade all-my-horizon-installations \
   --namespace my-horizon-namespace-on-cluster \
   --set ingest.replicaCount=0 \
   --set web.replicaCount=0
   ```
 
-  </CodeExample>
+  </CodeGroup>
 
   Now, use helm to start just a single Horizon instance from a helm installation that has ingestion enabled on Kubernetes cluster, you will set the `global.image.horizon.tag` to the release tag published on [stellar/stellar-horizon](https://hub.docker.com/r/stellar/stellar-horizon/tags)
 
-  <CodeExample>
+  <CodeGroup>
 
-  ```bash
+  ```bash bash
   helm upgrade my-horizon \
   --namespace my-horizon-namespace-on-cluster  \
   --set global.image.horizon.tag=new_horizon_release_number \
@@ -88,23 +88,23 @@ A good strategy for upgrading Horizon and applicable to single or multi-instance
   --set ingest.replicaCount=1
   ```
 
-  </CodeExample>
+  </CodeGroup>
 
 ### Confirming the upgrade on single ingestion instance first
 
-If you have [monitoring](./monitoring.mdx) infrastructure in place, then you have two options for assessing the upgrade status:
+If you have [monitoring](./monitoring) infrastructure in place, then you have two options for assessing the upgrade status:
 
-- View metrics outputs using grafana dashboards that leverage queries on the [Horizon metrics data model](./monitoring.mdx#data-model) to check key stats like ingestion and network ledgers are advancing and in step.
+- View metrics outputs using grafana dashboards that leverage queries on the [Horizon metrics data model](./monitoring#data-model) to check key stats like ingestion and network ledgers are advancing and in step.
 
 - View the Horizon web server 'status' url path on the upgraded instance:
 
-  <CodeExample>
+  <CodeGroup>
 
-  ```bash
+  ```bash bash
   curl http://localhost:8000/
   ```
 
-  </CodeExample>
+  </CodeGroup>
 
   The response will be HTTP status code 200 and body of response will be a text based json data structure with diagnostic info on current Horizon software version, and ledger numbers for ingestion and network, refresh the url every 5 seconds or so, and should see the ingestion and network ledger numbers advancing and in step, indicating good connection to the network and ingestion.
 
@@ -121,9 +121,9 @@ If metrics and/or the Horizon 'status' url respones don't indicate healthy statu
 
 At this point, you have upgraded one ingesting instance to the new Horizon version, it has automatically updated the database if required and the instance is running with healthy status. Now, install the same Horizon software version on the remainder of instances, restarting each after the upgrade. For bare-metal and docker daemon installations that will likely be self explanatory on how to accomplish that for remainder of instances, on helm chart installations, run the helm upgrade again, setting the image tag and also restoring original `replicaCount`s:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 helm upgrade all-my-horizon-installations \
 --namespace my-horizon-namespace-on-cluster \
 --set ingest.replicaCount=1 \
@@ -132,6 +132,6 @@ helm upgrade all-my-horizon-installations \
 --set ingest.horizonConfig.applyMigrations=False
 ```
 
-</CodeExample>
+</CodeGroup>
 
 For production deployments following the hot backup or blue/green model, this is the opportunity to confirm the inactive deployment has taken the upgrade correctly and stable, at which point, switch the load balancers now to forward traffic to the inactive deployment, making it the active deployment. Now, can take time to perform same upgrade on the other deployment which is now inactive.
diff --git a/docs/data/apis/horizon/api-reference/README.mdx b/docs/data/apis/horizon/api-reference/README.mdx
deleted file mode 100644
index 6c6402542..000000000
--- a/docs/data/apis/horizon/api-reference/README.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: API Reference
-sidebar_position: 20
-sidebar_key: horizon-api-reference
----
-
-import DocCardList from "@theme/DocCardList";
-
-View all Horizon API information.
-
-<DocCardList />
diff --git a/docs/data/apis/horizon/api-reference/aggregations/README.mdx b/docs/data/apis/horizon/api-reference/aggregations/README.mdx
deleted file mode 100644
index 4fee24b56..000000000
--- a/docs/data/apis/horizon/api-reference/aggregations/README.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: Aggregations
-sidebar_position: 30
----
-
-import { MethodTable } from "@site/src/components/MethodTable";
-
-Endpoints that aggregate data about the ledger.
-
-<MethodTable title="Resource Types">
-
-|                                                       |     |
-| ----------------------------------------------------- | --- |
-| [Order Books](./order-books/README.mdx)               |     |
-| [Paths](./paths/README.mdx)                           |     |
-| [Trade Aggregations](./trade-aggregations/README.mdx) |     |
-| [Fee Stats](./fee-stats/README.mdx)                   |     |
-
-</MethodTable>
diff --git a/docs/data/apis/horizon/api-reference/aggregations/fee-stats/README.mdx b/docs/data/apis/horizon/api-reference/aggregations/fee-stats/README.mdx
deleted file mode 100644
index 9a1aef5d8..000000000
--- a/docs/data/apis/horizon/api-reference/aggregations/fee-stats/README.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Fee Stats
-sidebar_position: 50
----
-
-Fee stats are used to predict what fee to set for a transaction before submitting it to the network.
-
-<EndpointsTable title="Endpoints">
-
-|     |                                                |
-| --- | ---------------------------------------------- |
-| GET | [/fee-stats](../../retrieve-fee-stats.api.mdx) |
-
-</EndpointsTable>
diff --git a/docs/data/apis/horizon/api-reference/aggregations/fee-stats/index.mdx b/docs/data/apis/horizon/api-reference/aggregations/fee-stats/index.mdx
new file mode 100644
index 000000000..9525477e4
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/aggregations/fee-stats/index.mdx
@@ -0,0 +1,8 @@
+---
+title: Fee Stats
+description: "Fee stats are used to predict what fee to set for a transaction before submitting it to the network."
+---
+
+| Endpoints |  |
+| --- | --- |
+| GET | [/fee-stats](/docs/data/apis/horizon/api-reference/retrieve-fee-stats) |
diff --git a/docs/data/apis/horizon/api-reference/aggregations/fee-stats/object.mdx b/docs/data/apis/horizon/api-reference/aggregations/fee-stats/object.mdx
index a46394f84..33f60c0f7 100644
--- a/docs/data/apis/horizon/api-reference/aggregations/fee-stats/object.mdx
+++ b/docs/data/apis/horizon/api-reference/aggregations/fee-stats/object.mdx
@@ -1,120 +1,207 @@
 ---
 title: The Fee Stats Object
-sidebar_position: 20
+description: "When Horizon returns fee stats, it uses the format below."
 ---
 
 When Horizon returns fee stats, it uses the format below.
 
-:::note
+<Note>
 
 The `fee_charged` represents the actual fee paid for the transaction, while `max_fee` represents the maximum bid the transaction creator was willing to pay for the transaction.
 
-:::
-
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- last_ledger
-  - string
-  - The last ledger's sequence number.
-- last_ledger_base_fee
-  - string
-  - The base fee as defined in the last ledger.
-- ledger_capacity_usage
-  - string
-  - The average capacity usage over the last 5 ledgers (0 is no usage, 1.0 is completely full ledgers).
-- fee_charged
-  - object
-  - Information about the fee charged for transactions in the last 5 ledgers.
-    - min
-      - string
-      - Minimum fee charged over the last 5 ledgers.
-    - mode
-      - string
-      - Mode fee charged over the last 5 ledgers.
-    - p10
-      - string
-      - 10th percentile fee charged over the last 5 ledgers.
-    - p20
-      - string
-      - 20th percentile fee charged over the last 5 ledgers.
-    - p30
-      - string
-      - 30th percentile fee charged over the last 5 ledgers.
-    - p40
-      - string
-      - 40th percentile fee charged over the last 5 ledgers.
-    - p50
-      - string
-      - 50th percentile fee charged over the last 5 ledgers.
-    - p60
-      - string
-      - 60th percentile fee charged over the last 5 ledgers.
-    - p70
-      - string
-      - 70th percentile fee charged over the last 5 ledgers.
-    - p80
-      - string
-      - 80th percentile fee charged over the last 5 ledgers.
-    - p90
-      - string
-      - 90th percentile fee charged over the last 5 ledgers.
-    - p95
-      - string
-      - 95th percentile fee charged over the last 5 ledgers.
-    - p99
-      - string
-      - 99th percentile fee charged over the last 5 ledgers.
-- max_fee
-  - object
-  - Information about max fee bid for transactions over the last 5 ledgers.
-    - min
-      - string
-      - Minimum (lowest) value of the maximum fee bid over the last 5 ledgers.
-    - mode
-      - string
-      - Mode max fee over the last 5 ledgers.
-    - p10
-      - string
-      - 10th percentile max fee charged over the last 5 ledgers.
-    - p20
-      - string
-      - 20th percentile max fee charged over the last 5 ledgers.
-    - p30
-      - string
-      - 30th percentile max fee charged over the last 5 ledgers.
-    - p40
-      - string
-      - 40th percentile max fee charged over the last 5 ledgers.
-    - p50
-      - string
-      - 50th percentile max fee charged over the last 5 ledgers.
-    - p60
-      - string
-      - 60th percentile max fee charged over the last 5 ledgers.
-    - p70
-      - string
-      - 70th percentile max fee charged over the last 5 ledgers.
-    - p80
-      - string
-      - 80th percentile max fee charged over the last 5 ledgers.
-    - p90
-      - string
-      - 90th percentile max fee charged over the last 5 ledgers.
-    - p95
-      - string
-      - 95th percentile max fee charged over the last 5 ledgers.
-    - p99
-      - string
-      - 99th percentile max fee charged over the last 5 ledgers.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
+</Note>
+
+<ResponseField name="last_ledger" type="string">
+
+The last ledger's sequence number.
+
+</ResponseField>
+
+<ResponseField name="last_ledger_base_fee" type="string">
+
+The base fee as defined in the last ledger.
+
+</ResponseField>
+
+<ResponseField name="ledger_capacity_usage" type="string">
+
+The average capacity usage over the last 5 ledgers (0 is no usage, 1.0 is completely full ledgers).
+
+</ResponseField>
+
+<ResponseField name="fee_charged" type="object">
+
+Information about the fee charged for transactions in the last 5 ledgers.
+
+  <Expandable title="fee_charged properties">
+    <ResponseField name="min" type="string">
+
+      Minimum fee charged over the last 5 ledgers.
+
+    </ResponseField>
+
+    <ResponseField name="mode" type="string">
+
+      Mode fee charged over the last 5 ledgers.
+
+    </ResponseField>
+
+    <ResponseField name="p10" type="string">
+
+      10th percentile fee charged over the last 5 ledgers.
+
+    </ResponseField>
+
+    <ResponseField name="p20" type="string">
+
+      20th percentile fee charged over the last 5 ledgers.
+
+    </ResponseField>
+
+    <ResponseField name="p30" type="string">
+
+      30th percentile fee charged over the last 5 ledgers.
+
+    </ResponseField>
+
+    <ResponseField name="p40" type="string">
+
+      40th percentile fee charged over the last 5 ledgers.
+
+    </ResponseField>
+
+    <ResponseField name="p50" type="string">
+
+      50th percentile fee charged over the last 5 ledgers.
+
+    </ResponseField>
+
+    <ResponseField name="p60" type="string">
+
+      60th percentile fee charged over the last 5 ledgers.
+
+    </ResponseField>
+
+    <ResponseField name="p70" type="string">
+
+      70th percentile fee charged over the last 5 ledgers.
+
+    </ResponseField>
+
+    <ResponseField name="p80" type="string">
+
+      80th percentile fee charged over the last 5 ledgers.
+
+    </ResponseField>
+
+    <ResponseField name="p90" type="string">
+
+      90th percentile fee charged over the last 5 ledgers.
+
+    </ResponseField>
+
+    <ResponseField name="p95" type="string">
+
+      95th percentile fee charged over the last 5 ledgers.
+
+    </ResponseField>
+
+    <ResponseField name="p99" type="string">
+
+      99th percentile fee charged over the last 5 ledgers.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="max_fee" type="object">
+
+Information about max fee bid for transactions over the last 5 ledgers.
+
+  <Expandable title="max_fee properties">
+    <ResponseField name="min" type="string">
+
+      Minimum (lowest) value of the maximum fee bid over the last 5 ledgers.
+
+    </ResponseField>
+
+    <ResponseField name="mode" type="string">
+
+      Mode max fee over the last 5 ledgers.
+
+    </ResponseField>
+
+    <ResponseField name="p10" type="string">
+
+      10th percentile max fee charged over the last 5 ledgers.
+
+    </ResponseField>
+
+    <ResponseField name="p20" type="string">
+
+      20th percentile max fee charged over the last 5 ledgers.
+
+    </ResponseField>
+
+    <ResponseField name="p30" type="string">
+
+      30th percentile max fee charged over the last 5 ledgers.
+
+    </ResponseField>
+
+    <ResponseField name="p40" type="string">
+
+      40th percentile max fee charged over the last 5 ledgers.
+
+    </ResponseField>
+
+    <ResponseField name="p50" type="string">
+
+      50th percentile max fee charged over the last 5 ledgers.
+
+    </ResponseField>
+
+    <ResponseField name="p60" type="string">
+
+      60th percentile max fee charged over the last 5 ledgers.
+
+    </ResponseField>
+
+    <ResponseField name="p70" type="string">
+
+      70th percentile max fee charged over the last 5 ledgers.
+
+    </ResponseField>
+
+    <ResponseField name="p80" type="string">
+
+      80th percentile max fee charged over the last 5 ledgers.
+
+    </ResponseField>
+
+    <ResponseField name="p90" type="string">
+
+      90th percentile max fee charged over the last 5 ledgers.
+
+    </ResponseField>
+
+    <ResponseField name="p95" type="string">
+
+      95th percentile max fee charged over the last 5 ledgers.
+
+    </ResponseField>
+
+    <ResponseField name="p99" type="string">
+
+      99th percentile max fee charged over the last 5 ledgers.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+```json Example
 {
   "last_ledger": "28444678",
   "last_ledger_base_fee": "100",
@@ -166,5 +253,3 @@ The `fee_charged` represents the actual fee paid for the transaction, while `max
   }
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/aggregations/index.mdx b/docs/data/apis/horizon/api-reference/aggregations/index.mdx
new file mode 100644
index 000000000..00689e00f
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/aggregations/index.mdx
@@ -0,0 +1,11 @@
+---
+title: Aggregations
+description: "Endpoints that aggregate data about the ledger."
+---
+
+| Resource Types |  |
+| --- | --- |
+| [Order Books](/docs/data/apis/horizon/api-reference/aggregations/order-books) |  |
+| [Paths](/docs/data/apis/horizon/api-reference/aggregations/paths) |  |
+| [Trade Aggregations](/docs/data/apis/horizon/api-reference/aggregations/trade-aggregations) |  |
+| [Fee Stats](/docs/data/apis/horizon/api-reference/aggregations/fee-stats) |  |
diff --git a/docs/data/apis/horizon/api-reference/aggregations/order-books/README.mdx b/docs/data/apis/horizon/api-reference/aggregations/order-books/README.mdx
deleted file mode 100644
index 96653d4e9..000000000
--- a/docs/data/apis/horizon/api-reference/aggregations/order-books/README.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: Order Books
-sidebar_position: 10
----
-
-An order book is a collection of offers for a specific pair of assets.
-
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
-
-Learn more about [order books](../../../../../../learn/glossary.mdx#decentralized-exchange).
-
-<EndpointsTable title="Endpoints">
-
-|     |                                                     |
-| --- | --------------------------------------------------- |
-| GET | [/order_book](../../retrieve-an-order-book.api.mdx) |
-
-</EndpointsTable>
diff --git a/docs/data/apis/horizon/api-reference/aggregations/order-books/index.mdx b/docs/data/apis/horizon/api-reference/aggregations/order-books/index.mdx
new file mode 100644
index 000000000..edfdc6a92
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/aggregations/order-books/index.mdx
@@ -0,0 +1,12 @@
+---
+title: Order Books
+description: "An order book is a collection of offers for a specific pair of assets."
+---
+
+The [latest ledger](/docs/data/apis/horizon/api-reference/structure/consistency) known to Horizon is included as an HTTP header in the response.
+
+Learn more about [order books](/docs/learn/glossary#decentralized-exchange).
+
+| Endpoints |  |
+| --- | --- |
+| GET | [/order_book](/docs/data/apis/horizon/api-reference/retrieve-an-order-book) |
diff --git a/docs/data/apis/horizon/api-reference/aggregations/order-books/object.mdx b/docs/data/apis/horizon/api-reference/aggregations/order-books/object.mdx
index 188c9a93b..730194afd 100644
--- a/docs/data/apis/horizon/api-reference/aggregations/order-books/object.mdx
+++ b/docs/data/apis/horizon/api-reference/aggregations/order-books/object.mdx
@@ -1,83 +1,143 @@
 ---
 title: The Order Book Object
-sidebar_position: 10
+description: "When Horizon returns information about an order book, it uses the following format."
 ---
 
 When Horizon returns information about an order book, it uses the following format:
 
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- bids
-  - object
-  - The prices and amounts for the buyside of the asset pair.
-    - price_r
-      - object
-      - A precise representation of the bid price of the asset pair.
-        - n
-          - number
-          - The numerator.
-        - d
-          - number
-          - The denominator.
-    - price
-      - string
-      - The bid price of the base asset denominated in the counter asset. A number representing the decimal form of `price_r`.
-    - amount
-      - string
-      - The amount of counter asset that the account making this offer is willing to buy at this price.
-- asks
-  - object
-  - The prices and amounts for the sellside of the asset pair.
-    - price_r
-      - object
-      - A precise representation of the ask price of the asset pair.
-        - n
-          - number
-          - The numerator.
-        - d
-          - number
-          - The denominator.
-    - price
-      - string
-      - The ask price of the base asset denominated in the counter asset. A number representing the decimal form of `price_r`.
-    - amount
-      - string
-      - The amount of counter asset that the account making this offer is willing to sell at this price.
-- base
-  - object
-  - Details about the base asset.
-    - asset_type
-      - string
-      - The type for the base asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
-    - asset_code
-      - string
-      - The code for the base asset.
-    - asset_issuer
-      - string
-      - The Stellar address of the base asset’s issuer.
-- counter
-  - object
-  - Details about the counter asset.
-    - asset_type
-      - string
-      - The type for the counter asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
-    - asset_code
-      - string
-      - The code for the counter asset.
-    - asset_issuer
-      - string
-      - The Stellar address of the counter asset’s issuer.
-
-</AttributeTable>
-
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
-
-<ExampleResponse>
-
-```json
+<ResponseField name="bids" type="object">
+
+The prices and amounts for the buyside of the asset pair.
+
+  <Expandable title="bids properties">
+    <ResponseField name="price_r" type="object">
+
+      A precise representation of the bid price of the asset pair.
+
+      <Expandable title="price_r properties">
+        <ResponseField name="n" type="number">
+
+          The numerator.
+
+        </ResponseField>
+
+        <ResponseField name="d" type="number">
+
+          The denominator.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+    <ResponseField name="price" type="string">
+
+      The bid price of the base asset denominated in the counter asset. A number representing the decimal form of `price_r`.
+
+    </ResponseField>
+
+    <ResponseField name="amount" type="string">
+
+      The amount of counter asset that the account making this offer is willing to buy at this price.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="asks" type="object">
+
+The prices and amounts for the sellside of the asset pair.
+
+  <Expandable title="asks properties">
+    <ResponseField name="price_r" type="object">
+
+      A precise representation of the ask price of the asset pair.
+
+      <Expandable title="price_r properties">
+        <ResponseField name="n" type="number">
+
+          The numerator.
+
+        </ResponseField>
+
+        <ResponseField name="d" type="number">
+
+          The denominator.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+    <ResponseField name="price" type="string">
+
+      The ask price of the base asset denominated in the counter asset. A number representing the decimal form of `price_r`.
+
+    </ResponseField>
+
+    <ResponseField name="amount" type="string">
+
+      The amount of counter asset that the account making this offer is willing to sell at this price.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="base" type="object">
+
+Details about the base asset.
+
+  <Expandable title="base properties">
+    <ResponseField name="asset_type" type="string">
+
+      The type for the base asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
+
+    </ResponseField>
+
+    <ResponseField name="asset_code" type="string">
+
+      The code for the base asset.
+
+    </ResponseField>
+
+    <ResponseField name="asset_issuer" type="string">
+
+      The Stellar address of the base asset’s issuer.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="counter" type="object">
+
+Details about the counter asset.
+
+  <Expandable title="counter properties">
+    <ResponseField name="asset_type" type="string">
+
+      The type for the counter asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
+
+    </ResponseField>
+
+    <ResponseField name="asset_code" type="string">
+
+      The code for the counter asset.
+
+    </ResponseField>
+
+    <ResponseField name="asset_issuer" type="string">
+
+      The Stellar address of the counter asset’s issuer.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+The [latest ledger](../../structure/consistency) known to Horizon is included as an HTTP header in the response.
+
+```json Example
 {
   "bids": [
     {
@@ -125,5 +185,3 @@ The [latest ledger](../../structure/consistency.mdx) known to Horizon is include
   }
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/aggregations/paths/README.mdx b/docs/data/apis/horizon/api-reference/aggregations/paths/README.mdx
deleted file mode 100644
index b7fe0ce32..000000000
--- a/docs/data/apis/horizon/api-reference/aggregations/paths/README.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: Paths
-sidebar_position: 20
----
-
-Paths provide information about potential path payments. A path can be used to populate the necessary fields for a path payment operation.
-
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
-
-Learn more about the two types of path payment: [`path payment strict send`](../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#path-payment-strict-send) and [`path payment strict receive`](../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#path-payment-strict-receive)
-
-<EndpointsTable title="Endpoints">
-
-|  |  |
-| --- | --- |
-| GET | [/paths/strict-receive](../../list-strict-receive-payment-paths.api.mdx) |
-| GET | [/paths/strict-send](../../list-strict-send-payment-paths.api.mdx) |
-
-</EndpointsTable>
diff --git a/docs/data/apis/horizon/api-reference/aggregations/paths/index.mdx b/docs/data/apis/horizon/api-reference/aggregations/paths/index.mdx
new file mode 100644
index 000000000..80feb7e99
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/aggregations/paths/index.mdx
@@ -0,0 +1,13 @@
+---
+title: Paths
+description: "Paths provide information about potential path payments. A path can be used to populate the necessary fields for a path payment operation."
+---
+
+The [latest ledger](/docs/data/apis/horizon/api-reference/structure/consistency) known to Horizon is included as an HTTP header in the response.
+
+Learn more about the two types of path payment: [`path payment strict send`](/docs/learn/fundamentals/transactions/list-of-operations#path-payment-strict-send) and [`path payment strict receive`](/docs/learn/fundamentals/transactions/list-of-operations#path-payment-strict-receive)
+
+| Endpoints |  |
+| --- | --- |
+| GET | [/paths/strict-receive](/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths) |
+| GET | [/paths/strict-send](/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths) |
diff --git a/docs/data/apis/horizon/api-reference/aggregations/paths/object.mdx b/docs/data/apis/horizon/api-reference/aggregations/paths/object.mdx
index 8e1f467a8..e4e3045c9 100644
--- a/docs/data/apis/horizon/api-reference/aggregations/paths/object.mdx
+++ b/docs/data/apis/horizon/api-reference/aggregations/paths/object.mdx
@@ -1,59 +1,87 @@
 ---
 title: The Path Object
-sidebar_position: 10
+description: "When Horizon returns information about a path, it uses the following format."
 ---
 
 When Horizon returns information about a path, it uses the following format:
 
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- source_asset_type
-  - string
-  - The type for the source asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
-- source_asset_code
-  - string
-  - The code for the source asset.
-- source_asset_issuer
-  - string
-  - The Stellar address of the source asset’s issuer.
-- source_amount
-  - string
-  - An estimated cost for making a payment of destination_amount on this path. Suitable for use in the `sendMax` field of a path payment operation.
-- destination_asset_type
-  - string
-  - The type for the destination asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
-- destination_asset_code
-  - string
-  - The code for the destination asset.
-- destination_asset_issuer
-  - string
-  - The Stellar address of the destination asset’s issuer.
-- destination_amount
-  - string
-  - The destination amount specified in the search that found this path.
-- path
-  - array of objects
-  - The intermediary assets that this path hops through.
-    - asset_code
-      - string
-      - The code for this intermediary asset.
-    - asset_issuer
-      - string
-      - The Stellar address of the intermediary asset’s issuer.
-    - asset_type
-      - string
-      - The type for the intermediary asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
-
-</AttributeTable>
-
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
-
-<ExampleResponse>
-
-```json
+<ResponseField name="source_asset_type" type="string">
+
+The type for the source asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
+
+</ResponseField>
+
+<ResponseField name="source_asset_code" type="string">
+
+The code for the source asset.
+
+</ResponseField>
+
+<ResponseField name="source_asset_issuer" type="string">
+
+The Stellar address of the source asset’s issuer.
+
+</ResponseField>
+
+<ResponseField name="source_amount" type="string">
+
+An estimated cost for making a payment of destination_amount on this path. Suitable for use in the `sendMax` field of a path payment operation.
+
+</ResponseField>
+
+<ResponseField name="destination_asset_type" type="string">
+
+The type for the destination asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
+
+</ResponseField>
+
+<ResponseField name="destination_asset_code" type="string">
+
+The code for the destination asset.
+
+</ResponseField>
+
+<ResponseField name="destination_asset_issuer" type="string">
+
+The Stellar address of the destination asset’s issuer.
+
+</ResponseField>
+
+<ResponseField name="destination_amount" type="string">
+
+The destination amount specified in the search that found this path.
+
+</ResponseField>
+
+<ResponseField name="path" type="array of objects">
+
+The intermediary assets that this path hops through.
+
+  <Expandable title="path properties">
+    <ResponseField name="asset_code" type="string">
+
+      The code for this intermediary asset.
+
+    </ResponseField>
+
+    <ResponseField name="asset_issuer" type="string">
+
+      The Stellar address of the intermediary asset’s issuer.
+
+    </ResponseField>
+
+    <ResponseField name="asset_type" type="string">
+
+      The type for the intermediary asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+The [latest ledger](../../structure/consistency) known to Horizon is included as an HTTP header in the response.
+
+```json Example
 {
   "_embedded": {
     "records": [
@@ -131,5 +159,3 @@ The [latest ledger](../../structure/consistency.mdx) known to Horizon is include
   }
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/aggregations/trade-aggregations/README.mdx b/docs/data/apis/horizon/api-reference/aggregations/trade-aggregations/README.mdx
deleted file mode 100644
index 15152e546..000000000
--- a/docs/data/apis/horizon/api-reference/aggregations/trade-aggregations/README.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Trade Aggregations
-sidebar_position: 40
----
-
-A trade aggregation represents aggregated statistics on an asset pair (base and counter) for a specific time period. Trade aggregations are useful to developers of trading clients and provide historical trade data.
-
-<EndpointsTable title="Endpoints">
-
-|     |                                                              |
-| --- | ------------------------------------------------------------ |
-| GET | [/trade_aggregations](../../list-trade-aggregations.api.mdx) |
-
-</EndpointsTable>
diff --git a/docs/data/apis/horizon/api-reference/aggregations/trade-aggregations/index.mdx b/docs/data/apis/horizon/api-reference/aggregations/trade-aggregations/index.mdx
new file mode 100644
index 000000000..ea5117fa0
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/aggregations/trade-aggregations/index.mdx
@@ -0,0 +1,8 @@
+---
+title: Trade Aggregations
+description: "A trade aggregation represents aggregated statistics on an asset pair (base and counter) for a specific time period. Trade aggregations are useful to developers of trading clients and provide historical trade data."
+---
+
+| Endpoints |  |
+| --- | --- |
+| GET | [/trade_aggregations](/docs/data/apis/horizon/api-reference/list-trade-aggregations) |
diff --git a/docs/data/apis/horizon/api-reference/aggregations/trade-aggregations/object.mdx b/docs/data/apis/horizon/api-reference/aggregations/trade-aggregations/object.mdx
index a643e9a74..c8b6024ac 100644
--- a/docs/data/apis/horizon/api-reference/aggregations/trade-aggregations/object.mdx
+++ b/docs/data/apis/horizon/api-reference/aggregations/trade-aggregations/object.mdx
@@ -1,84 +1,145 @@
 ---
 title: The Trade Aggregation Object
-sidebar_position: 10
+description: "When Horizon returns information about a trade aggregation, it uses the following format."
 ---
 
 When Horizon returns information about a trade aggregation, it uses the following format:
 
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- timestamp
-  - string
-  - Start time for this trade aggregation. Represented as milliseconds since epoch.
-- trade_count
-  - integer
-  - Total number of trades aggregated.
-- base_volume
-  - string
-  - Total volume of base asset.
-- counter_volume
-  - string
-  - Total volume of counter asset.
-- avg
-  - string
-  - Weighted average price of counter asset in terms of base asset.
-- high
-  - string
-  - The highest price for this time period.
-- high_r
-  - object
-  - The highest price for this time period as a rational number.
-    - n
-      - number
-      - The numerator.
-    - d
-      - number
-      - The denominator.
-- low
-  - string
-  - The lowest price for this time period.
-- low_r
-  - object
-  - The lowest price for this time period as a rational number.
-    - n
-      - number
-      - The numerator.
-    - p
-      - number
-      - The denominator.
-- open
-  - string
-  - The price as seen on first trade aggregated.
-- open_r
-  - object
-  - The price as seen on first trade aggregated as a rational number.
-    - n
-      - number
-      - The numerator.
-    - p
-      - number
-      - The denominator.
-- close
-  - string
-  - The price as seen on last trade aggregated.
-- close_r
-  - object
-  - The price as seen on last trade aggregated as a rational number.
-    - n
-      - number
-      - The numerator.
-    - p
-      - number
-      - The denominator.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
+<ResponseField name="timestamp" type="string">
+
+Start time for this trade aggregation. Represented as milliseconds since epoch.
+
+</ResponseField>
+
+<ResponseField name="trade_count" type="integer">
+
+Total number of trades aggregated.
+
+</ResponseField>
+
+<ResponseField name="base_volume" type="string">
+
+Total volume of base asset.
+
+</ResponseField>
+
+<ResponseField name="counter_volume" type="string">
+
+Total volume of counter asset.
+
+</ResponseField>
+
+<ResponseField name="avg" type="string">
+
+Weighted average price of counter asset in terms of base asset.
+
+</ResponseField>
+
+<ResponseField name="high" type="string">
+
+The highest price for this time period.
+
+</ResponseField>
+
+<ResponseField name="high_r" type="object">
+
+The highest price for this time period as a rational number.
+
+  <Expandable title="high_r properties">
+    <ResponseField name="n" type="number">
+
+      The numerator.
+
+    </ResponseField>
+
+    <ResponseField name="d" type="number">
+
+      The denominator.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="low" type="string">
+
+The lowest price for this time period.
+
+</ResponseField>
+
+<ResponseField name="low_r" type="object">
+
+The lowest price for this time period as a rational number.
+
+  <Expandable title="low_r properties">
+    <ResponseField name="n" type="number">
+
+      The numerator.
+
+    </ResponseField>
+
+    <ResponseField name="p" type="number">
+
+      The denominator.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="open" type="string">
+
+The price as seen on first trade aggregated.
+
+</ResponseField>
+
+<ResponseField name="open_r" type="object">
+
+The price as seen on first trade aggregated as a rational number.
+
+  <Expandable title="open_r properties">
+    <ResponseField name="n" type="number">
+
+      The numerator.
+
+    </ResponseField>
+
+    <ResponseField name="p" type="number">
+
+      The denominator.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="close" type="string">
+
+The price as seen on last trade aggregated.
+
+</ResponseField>
+
+<ResponseField name="close_r" type="object">
+
+The price as seen on last trade aggregated as a rational number.
+
+  <Expandable title="close_r properties">
+    <ResponseField name="n" type="number">
+
+      The numerator.
+
+    </ResponseField>
+
+    <ResponseField name="p" type="number">
+
+      The denominator.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+```json Example
 {
   "_links": {
     "self": {
@@ -232,5 +293,3 @@ When Horizon returns information about a trade aggregation, it uses the followin
   }
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/cb-retrieve-related-operations.ParamsDetails.json b/docs/data/apis/horizon/api-reference/cb-retrieve-related-operations.ParamsDetails.json
deleted file mode 100644
index f0ef75bae..000000000
--- a/docs/data/apis/horizon/api-reference/cb-retrieve-related-operations.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"claimable_balance_id","in":"path","required":true,"description":"A unique identifier for this claimable balance.","schema":{"type":"string"}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}},{"name":"join","in":"query","required":false,"description":"Set to transactions to include the transactions which created each of the operations in the response."}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/cb-retrieve-related-operations.RequestSchema.json b/docs/data/apis/horizon/api-reference/cb-retrieve-related-operations.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/cb-retrieve-related-operations.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/cb-retrieve-related-operations.StatusCodes.json b/docs/data/apis/horizon/api-reference/cb-retrieve-related-operations.StatusCodes.json
deleted file mode 100644
index c0da2d20c..000000000
--- a/docs/data/apis/horizon/api-reference/cb-retrieve-related-operations.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"oneOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"create_account"},"type_i":{"type":"number","example":0},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"starting_balance":{"type":"string"},"funder":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","starting_balance","funder","account"],"title":"CreateAccount"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"payment"},"type_i":{"type":"string"},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string"},"asset_code":{"enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","asset_type","from","to","amount"]}}}}},"title":"Payment"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"path_payment_strict_receive"},"type_i":{"type":"number","example":2},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"},"path":{"type":"array","items":{"type":"object","properties":{"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}}}},"source_amount":{"type":"string"},"destination_min":{"type":"string"},"source_asset_type":{"type":"string"},"source_asset_code":{"type":"string"},"source_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","from","to","amount","path","source_amount","destination_min"],"title":"PathPaymentStrictReceive"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"path_payment_strict_send"},"type_i":{"type":"number","example":13},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"},"path":{"type":"array","items":{"type":"object","properties":{"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}}}},"source_amount":{"type":"string"},"source_max":{"type":"string"},"source_asset_type":{"type":"string"},"source_asset_code":{"type":"string"},"source_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","from","to","amount","path","source_amount","source_asset_type"],"title":"PathPaymentStrictSend"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"account_merge"},"type_i":{"type":"number","example":8},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"into":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","account","into"],"title":"AccountMerge"}]}]},"examples":{"CBRetrieveRelatedOperations":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000178826fbfe339e1f5c53417c6fedfe2c05e8bec14303143ec46b38981b09c3f9/operations?cursor=&limit=3&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000178826fbfe339e1f5c53417c6fedfe2c05e8bec14303143ec46b38981b09c3f9/operations?cursor=140648659841806337&limit=3&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000178826fbfe339e1f5c53417c6fedfe2c05e8bec14303143ec46b38981b09c3f9/operations?cursor=140648659841806337&limit=3&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/140648659841806337"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/fc5a98fc3869df408ebd4ac1c2e3fefec8b0a858e82ff1d14e362676708b91e8"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/140648659841806337/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=140648659841806337"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=140648659841806337"}},"id":"140648659841806337","paging_token":"140648659841806337","transaction_successful":true,"source_account":"GDCJIHD3623OCYNH65UUQC3NLG2D6YCNCDPZULRLCLOA76TBQRL6A3TF","type":"create_claimable_balance","type_i":14,"created_at":"2020-11-23T16:02:38Z","transaction_hash":"fc5a98fc3869df408ebd4ac1c2e3fefec8b0a858e82ff1d14e362676708b91e8","sponsor":"GDCJIHD3623OCYNH65UUQC3NLG2D6YCNCDPZULRLCLOA76TBQRL6A3TF","asset":"BODHI:GDCJIHD3623OCYNH65UUQC3NLG2D6YCNCDPZULRLCLOA76TBQRL6A3TF","amount":"0.1000000","claimants":[{"destination":"GBEUDKANIFPTFHPWJ5T3R6RIO36RQBFGHYPAQ6STH7KMNDHAT36LHOLD","predicate":{"unconditional":true}}]}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/cb-retrieve-related-operations.api.mdx b/docs/data/apis/horizon/api-reference/cb-retrieve-related-operations.api.mdx
deleted file mode 100644
index 6f9f47485..000000000
--- a/docs/data/apis/horizon/api-reference/cb-retrieve-related-operations.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: cb-retrieve-related-operations
-title: "Retrieve Related Operations"
-description: "This endpoint represents successful operations referencing a given claimable balance and can be used in streaming mode. Streaming mode allows you to listen for new operations referencing this claimable balance as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known operation unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream operations created since your request time."
-sidebar_label: "Retrieve Related Operations"
-hide_title: true
-hide_table_of_contents: true
-api: eJztXOtSGzkWfhVV/5hJUu07GOOqqVkuSWCGAQJkt2YI5cjSabdCt9QjqTEM5ap9jX29fZKto764DQ0hIZkkG/PHhVs6Ovdz1Nana8/SifGGp95WREVMxxGQTRpRycB4Z77HwTAtEiuU9IbeSSgMAckTJaQlGhINBqQ1xKSMgTFBGhGVgKY43hANAWiQTMgJoWQiLkASVi4zzpYhVHLCqCRjIKkBToQkxmqgMU6LFYcmOV74n9AoUlNDrlRKrCKRMBYkCZQmEqZ3rW+R9ZrFDbEhXBGqgVDOgSNFGwI5thBFVJMI+AR0k+wGhNEoquPPJztKi7+UJFMRRcRYqi2h1pEBqiMBxpJzqaZyzhxJZQTGEEpYqo3SRBhiwPpIfRoKFhJGDRBhqzQDrWJiQ2rzSU2yeYWzbCYgFLQuaJQCCiLV1HdqQv1mTFf1wzRQC5wYgaq4UqkmGv5MkV0rYmh6vleO3uXe0NvaPAKrBVzAEUQ49aAk5vleQjWNwYJGf7r2JI3BG3qlzke5zkeCe74n0J8SakPP93BRoYF7Q6tTuOl0GySV4s8UiOAgrQgEaGfseosi04aFEFNveO3ZqwR5MFYLOfFmM3/OllNVwcifKeirBU4CGpkaVmQaj0FnRnBRYFDPlJgEmAgEI5FimYGFROOqKALm/lcB0WASJQ0Y5/PCkCR1HpXbFUhCJ0JORladg8ytqAJCiQamNK8VTUgLE0BB4JLGSQTesN9v9/udtZW1wfrqeqe9WhVbaQ4fLjUHIyaSFnIgq47Q3FszDg0xoUojTmiSANVNcpBkniYki1IO5C017C15Qg0DyYWcPCVKk7e43FvyBD/yr128OQNTPUljkJYII//77//YPEos4RDQNMr078jeZ3nfA5nGmOaoYV4moHdWVUwkYmE/UDEnIZCYXoo4jQvHcFbOVKHBploCbxIc5+i7ONRUTiCzeQeZ77bbpEGoJGmSgM4HOgcThoRUc6Z4lnaKNIPen4AOlI5dEtNAjZLmHqUVBgR+S3ed9kP9qtOuKiw36SigIgL+gZo7BusSrc7yVOEeGa1qihISowZ5ve1MbjZGkluiVoqxUhFQObe/SzBu/IL13ykhP1YEKg1lGWcVUTBGFp7lWT1PuUBZWIbSgrj4TZEomt7szPcuGyZNEqWtaZSFp0iVZUpBobvtNn7c4DMrzZ7vMSUtSItDaJJEIktUrXcGx11XlEej6CBwOTxXoxq/A4bRkWhk1opsvVEk5LmpqPuOcQai4P2jQg1BXeQ6N7cuROW5N/M9C3Hiqk+NoWezquFOM6JnvmeFjaBCQ8Kl/cpYSjRcfFUszXBY8dWeMzWGjJLw/+4dlcD9yjiDIABmH6DVv5Ur1/4D/9rYSjQw4PB1sXVjkPP+RY+bW7mi2Yo0ZzPfE7yO3WIlwZ34lW6yphleWHQ038HVSeZ7RqWawYgyplJp6xZPqLWgseS8PN1o/NFurJ9dr67OKmxRzjWWIlzaTa5p04pmw8sqZblgPmckKrOynqs6qz3z84l8RGu4vCF0SE1YO8jtt1B5+a6idlCQSmymH6uKT6PSG27l9lgLDnCnuW/ZNrdOqfAFldYosEZdpXLm4lUCYcuR2ygt+95KAvEYcHP+/kDOm+/KQKo1xXZOWIgfkAmWVWtZtZZVa1m1PrJqJfQKN9615WouwqcoUdQYsKN6jsrH+OoAHxdvP/AdzgVkGZ0LO6JRElKZxiu3v+p0nckyOsKY9BOUOnzp8XgjqMeX3LjeHb5sFa1YNFeVE7Zk92y2uCU7LH1tWdSWRW1Z1JZF7bMVNRuO8so2wufMjlADWEoeti/r/g1Fz390lSuq5R3Lfi9F0M9+l/voLdS3byRXZoswu1tNHIwV2c9io1jUB3ZB5f5ubWHUnRIujPo0gn7JfqemxfGLn4QXlX9b1WfVNsiGeSt07HLTUZmaln3Rsi9a9kXLvuhv7IsMSP7ApqjTW3ZFy67o2zHSA7uifERML5cN0edriG6r8b6W6DjLSst+aNkPLfuhZT/0mfqhfKVRDHry0DdDg0/VA30iKYV8dBPxZX9EKGc6SSq+nP/e/ltmnLMZ+mRuBhdQ9x3uHl577jjyYpEoykAWil5obWKGrVaYHVNtWDBWgm2a7Ch9U+lJ69ZpcNNq53+dtcGg2w/GAfR669AJVtlqb6WzxvoB8AC6rL0KgzGwzkqv3eus9ICt9Me9wfqgM26vs16w3pqfo/w5O9390w/uMO1PvR/caeWf8Oxv5ezfV8t2Z6XdXxn0V9cHK51Bu9/rrdULUpwY/HYFceewMWAWjniUhzhOH+ltc45at1mp6Ro+gHT1bG8rYKt0fRCw3qC/zoOV9gDGfIWyDutCL4AA2GDcpoPVAQy6QdDhnRXo9bv9tf5aezBe78DgRpvwqSRsFTRv1PsPoJ9T+Hlurh/utO3N+v3Ry9D7V8lrqVfz7GYFrR9zVxHNjlTfLJvey+2tX3Z3tnv9bu9g6/f9nf7q69evtnr7ey+72/3ft/a3tg//eL13tLe1d7Cx1j/ZfHW019/onbwosnd5lu1W8M0T+7CzslgHvW672250Oo1u76TTH7a7w97gj7qUP/Qe7X2+5w6RK/04Yd1exBt6mwfbO7vDxxDKN5deu9nJchMWPqc8abO0UHkfjExvPn+9/evG/u6Lw5MXO4f/+mX1pHfUP9o96PWPXm2+eLnz++HGq/7xyc7ar7/tb+9snPT6ezsHe9tZi8bxJLwrbalkSnKBVGnuDzNXKfM/LJgWpMlq4um1dw5X3rD+gL5fVExH5cz3YrChQr+dQLmvG3p1Gfm6DjM1q8Q6Wgz0RYG0SnX0sDjz6hAsJ9k4sg92qvS52ybWUwxSm2p4CM0XxUgiC6pn2JEEWW+VdyQ5ngVVBdpks9vNdrPjuug4pvpqPookWl0I7sBTZOfk5JBsHO4i4oJTSwvgRIHay1dtkl1LhJyAsRnmSkPDKc6h/rKZiVY8ZcDJ+KqORIbjwk1FickBahCDZhVhSpo0hmIqvQBNJ0Aq6AqisZcSF1DgCiu4nYbSAiSiQRwjJZwyx4I4MOT4qmRoS2lALJEwTvKKHGMt+ATIGOwUQOLymbSLMw+1wo2UIZE4BzJFMKM1PuHAQFpNI/EX4lIuWYj4JOM7Ci6kSfZmxXFUYpCsIiYdO6hSpRL6xKFn0ER5/ixweT4ivXIIIlw40Kjj4yZ+Zj6zecuzvndPOK0a9OxJEZ4cLiDC5GAWamrOdospDQ2pODz9rrznjXwji+VyeDF1pR44uRCUsNdHez6hZKzV1IB2KygJBSir1PXx9q/mvbrmipmWVSoyLcPPDWpaEQ3oThkwV+E261LYK6TvkLZJplCfTMFBBuMYJHdgXVQUlbgwEdJYoBwnxfQcYb5caGDW2RDxyMbJ6cw6SQUHkkXMGAwJ1dSphMdCIkRak8LFnTsWusElHIrwiYNLF955ul1K+iPZjNRkroPpdLoofDmyMY7UpEUbEqYNk8oGVqEQGnn9eOqAi0ZhmFB2PtEqlZwoeTMaMt/RLBQWmE01jYiIMeYhdpZXOcoxpu8Q7JyVDjJO4+Rpk7xALLXMXgLh13SsUgQ8OhZRgfl6pWsoDmNqwCcsBHZOcHRVfgejfImqnStgImyYjptMxa1cD8VnIWprHKlxK6ZCtraf//P53sHh7v7LZsyfOnNtQqA0oOHHMBESIZk/GjJV2iKQVlhX5nNIN6YB4ZgAFqoMB+r4w7Ak+4p/TCIgXDEHEHU6GpJnz6ZAOOLFLcL7lTZAdColMlEoCk2WpSGKcHTJaYThUs0SpS89e5YlAHCwaBpFV460mzu6oJHgTsDRrdoG6PoaiJ0qYgAB5RaDRzLQMk8qHJhKkyjXT4xpWMTYfFFpnYONlVNjJOhYRBhxOKviXs0F18foiqmkEzBEoHNNpU8SqoE3OCL2C/dSwaKoKrEidkkP18xnYlLDlKcCInGzRZ5M4ccoIpXIQnQuwv7feFs0ceUAyb3xSt2hi2CfDzo2B8Ex6AuB+JOyGVvYhOKghgpcKRNuP4EgT8rc+40c21qwXXXoFxh6NH91udjsLbZ2EFPhnkIUqX9Un818LxIMpIHKWhsJZSGQbhM79jlev3zSyJ7MV8zTCXVPnUw5UdPa2916vn/8HKc0QxtHbuOXKGNjKitLFi+tSP7WiizcSbDQQFzPIbDLqyy+u6ss8r24hUvbSiIq3Dty54nX+Wbs9PZlFehDwzuusKjsx858L1TGIonraywnr3U0m+HXGZrcbVmFQRp34Mmrvvnlr5mo1VW22S0vzsi3t57bMH6IcN/MbRL3aKG4R+MjlfB/dHPEPUoq7tT4SCV9pksi7mH41p0Wi5y/l9HPehXEvZznF1jM+T3Df7RAVX9g9nlylP949ZR8+NU7tSwWB2bkVZXFMqHUZVf361QI1AFsyxdtG4xBUvWoW/dYLLxoe/n8xJvN/getnecW
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Related Operations"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/claimable_balances/{claimable_balance_id}/operations"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents successful operations referencing a given claimable balance and can be used in streaming mode. Streaming mode allows you to listen for new operations referencing this claimable balance as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known operation unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream operations created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./cb-retrieve-related-operations.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./cb-retrieve-related-operations.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./cb-retrieve-related-operations.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/cb-retrieve-related-operations.mdx b/docs/data/apis/horizon/api-reference/cb-retrieve-related-operations.mdx
new file mode 100644
index 000000000..280fbcf67
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/cb-retrieve-related-operations.mdx
@@ -0,0 +1,12 @@
+---
+title: Retrieve Related Operations
+openapi: "openapi/horizon/bundled.yml GET /claimable_balances/{claimable_balance_id}/operations"
+---
+
+<Tip>
+
+**Supports Streaming**
+
+This endpoint supports streaming. To read more about this, visit the [streaming section](/docs/data/apis/horizon/api-reference/structure/streaming).
+
+</Tip>
diff --git a/docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions.ParamsDetails.json b/docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions.ParamsDetails.json
deleted file mode 100644
index ba591a56d..000000000
--- a/docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"claimable_balance_id","in":"path","required":true,"description":"A unique identifier for this claimable balance.","schema":{"type":"string"}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions.RequestSchema.json b/docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions.StatusCodes.json b/docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions.StatusCodes.json
deleted file mode 100644
index 3d1e41770..000000000
--- a/docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"memo":{"type":"string"},"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"account":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"ledger":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","account","ledger","operations","effects","precedes","succeeds","transaction"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"successful":{"type":"boolean"},"hash":{"type":"string"},"ledger":{"type":"integer","format":"int32"},"created_at":{"type":"string"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"account_muxed":{"type":"string"},"account_muxed_id":{"type":"string"},"source_account_sequence":{"type":"string"},"fee_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed_id":{"type":"string"},"fee_charged":{"type":"string"},"max_fee":{"type":"string"},"operation_count":{"type":"integer","format":"int32"},"envelope_xdr":{"type":"string"},"result_xdr":{"type":"string"},"result_meta_xdr":{"type":"string"},"fee_meta_xdr":{"type":"string"},"memo_type":{"type":"string"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"},"preconditions":{"type":"object","properties":{"timebounds":{"type":"object","properties":{"min_time":{"type":"string"},"max_time":{"type":"string"}},"title":"TransactionPreconditionsTimebounds"},"ledgerbounds":{"type":"object","properties":{"min_ledger":{"type":"string"},"max_ledger":{"type":"string"}},"title":"TransactionPreconditionsLedgerbounds"},"min_account_sequence":{"type":"string"},"min_account_sequence_age":{"type":"string"},"min_account_sequence_ledger_gap":{"type":"integer","format":"uint32"},"extra_signers":{"type":"array","items":{"type":"string"}}},"title":"TransactionPreconditions"},"fee_bump_transaction":{"type":"object","properties":{"hash":{"type":"string","title":"hash"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"}},"title":"FeeBumpTransaction"},"inner_transaction":{"type":"object","properties":{"hash":{"type":"string","title":"hash"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"},"max_fee":{"type":"string"}},"title":"InnerTransaction"}},"required":["id","paging_token","successful","hash","ledger","created_at","source_account","source_account_sequence","fee_account","fee_charged","max_fee","operation_count","envelope_xdr","result_xdr","result_meta_xdr","memo_type","signatures"]}}}}},"title":"Transaction"}]},"examples":{"CBRetrieveRelatedTransactions":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000178826fbfe339e1f5c53417c6fedfe2c05e8bec14303143ec46b38981b09c3f9/transactions?cursor=&limit=2&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000178826fbfe339e1f5c53417c6fedfe2c05e8bec14303143ec46b38981b09c3f9/transactions?cursor=140648659841806336&limit=2&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000178826fbfe339e1f5c53417c6fedfe2c05e8bec14303143ec46b38981b09c3f9/transactions?cursor=140648659841806336&limit=2&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/fc5a98fc3869df408ebd4ac1c2e3fefec8b0a858e82ff1d14e362676708b91e8"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GDCJIHD3623OCYNH65UUQC3NLG2D6YCNCDPZULRLCLOA76TBQRL6A3TF"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/32747318"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/fc5a98fc3869df408ebd4ac1c2e3fefec8b0a858e82ff1d14e362676708b91e8/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/fc5a98fc3869df408ebd4ac1c2e3fefec8b0a858e82ff1d14e362676708b91e8/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=140648659841806336"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=140648659841806336"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/fc5a98fc3869df408ebd4ac1c2e3fefec8b0a858e82ff1d14e362676708b91e8"}},"id":"fc5a98fc3869df408ebd4ac1c2e3fefec8b0a858e82ff1d14e362676708b91e8","paging_token":"140648659841806336","successful":true,"hash":"fc5a98fc3869df408ebd4ac1c2e3fefec8b0a858e82ff1d14e362676708b91e8","ledger":32747318,"created_at":"2020-11-23T16:02:38Z","source_account":"GDCJIHD3623OCYNH65UUQC3NLG2D6YCNCDPZULRLCLOA76TBQRL6A3TF","source_account_sequence":"140646847365513218","fee_account":"GDCJIHD3623OCYNH65UUQC3NLG2D6YCNCDPZULRLCLOA76TBQRL6A3TF","fee_charged":"100","max_fee":"100","operation_count":1,"envelope_xdr":"AAAAAgAAAADElBx79rbhYaf3aUgLbVm0P2BNEN+aLisS3A/6YYRX4AAAAGQB862QAAAAAgAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAADgAAAAJCT0RISQAAAAAAAAAAAAAAxJQce/a24WGn92lIC21ZtD9gTRDfmi4rEtwP+mGEV+AAAAAAAA9CQAAAAAEAAAAAAAAAAElBqA1BXzKd9k9nuPoodv0YBKY+Hgh6Uz/UxozgnvyzAAAAAAAAAAAAAAABYYRX4AAAAEDf41ykW+eq8IVpJNOc4iDaht5Beil8NpQB8WMHkOxW3rocUBF3EHKqUXDIsD9CzzY7Xr1PbzVk5FZ4iBKNF4MM","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAAOAAAAAAAAAAAXiCb7/jOeH1xTQXxv7f4sBei+wUMDFD7EaziYGwnD+QAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAfOvNgAAAAAAAAAAxJQce/a24WGn92lIC21ZtD9gTRDfmi4rEtwP+mGEV+AAAAAAAcnCVAHzrZAAAAABAAAAAAAAAAAAAAAAAAAAD2dpdmluZ2JvZGhpLm9yZwABAAAAAAAAAAAAAAAAAAAAAAAAAQHzrzYAAAAAAAAAAMSUHHv2tuFhp/dpSAttWbQ/YE0Q35ouKxLcD/phhFfgAAAAAAHJwlQB862QAAAAAgAAAAAAAAAAAAAAAAAAAA9naXZpbmdib2RoaS5vcmcAAQAAAAAAAAAAAAAAAAAAAAAAAAEAAAADAAAAAwHzrzYAAAAAAAAAAMSUHHv2tuFhp/dpSAttWbQ/YE0Q35ouKxLcD/phhFfgAAAAAAHJwlQB862QAAAAAgAAAAAAAAAAAAAAAAAAAA9naXZpbmdib2RoaS5vcmcAAQAAAAAAAAAAAAAAAAAAAAAAAAEB8682AAAAAAAAAADElBx79rbhYaf3aUgLbVm0P2BNEN+aLisS3A/6YYRX4AAAAAABycJUAfOtkAAAAAIAAAAAAAAAAAAAAAAAAAAPZ2l2aW5nYm9kaGkub3JnAAEAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAfOvNgAAAAQAAAAAF4gm+/4znh9cU0F8b+3+LAXovsFDAxQ+xGs4mBsJw/kAAAABAAAAAAAAAABJQagNQV8ynfZPZ7j6KHb9GASmPh4IelM/1MaM4J78swAAAAAAAAACQk9ESEkAAAAAAAAAAAAAAMSUHHv2tuFhp/dpSAttWbQ/YE0Q35ouKxLcD/phhFfgAAAAAAAPQkAAAAAAAAAAAQAAAAEAAAAAxJQce/a24WGn92lIC21ZtD9gTRDfmi4rEtwP+mGEV+AAAAAAAAAAAA==","fee_meta_xdr":"AAAAAgAAAAMB866UAAAAAAAAAADElBx79rbhYaf3aUgLbVm0P2BNEN+aLisS3A/6YYRX4AAAAAABycK4AfOtkAAAAAEAAAAAAAAAAAAAAAAAAAAPZ2l2aW5nYm9kaGkub3JnAAEAAAAAAAAAAAAAAAAAAAAAAAABAfOvNgAAAAAAAAAAxJQce/a24WGn92lIC21ZtD9gTRDfmi4rEtwP+mGEV+AAAAAAAcnCVAHzrZAAAAABAAAAAAAAAAAAAAAAAAAAD2dpdmluZ2JvZGhpLm9yZwABAAAAAAAAAAAAAAAAAAAA","memo_type":"none","signatures":["3+NcpFvnqvCFaSTTnOIg2obeQXopfDaUAfFjB5DsVt66HFARdxByqlFwyLA/Qs82O169T281ZORWeIgSjReDDA=="],"preconditions":{"timebounds":{"min_time":"0"}}}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions.api.mdx b/docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions.api.mdx
deleted file mode 100644
index 433015be7..000000000
--- a/docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: cb-retrieve-related-transactions
-title: "Retrieve Related Transactions"
-description: "This endpoint represents successful transactions referencing a given claimable balance and can be used in streaming mode. Streaming mode allows you to listen for new transactions referencing this claimable balance as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time."
-sidebar_label: "Retrieve Related Transactions"
-hide_title: true
-hide_table_of_contents: true
-api: eJztW+ly27iWfhUUf3QnbdlaLUuuSt0rWV7jeHcSO+1Sg+ShhIgEGADUYpeq7mvM682T3DogKVES7djJnWn39PBHHIlYvrMCOPrwYGnaU9b2F2vHpyygtg+kTX3KHVDWXcFyQTmShZoJbm1bV32mCHA3FIxrIiGUoIBrRVTkOKCUF/lES8oVdbCHIhI8kMAdxnuEkh4bAifObCI7nohQ7hKHcmIDiRS4hHGitAQaYLdAuLBBLhc+E+r7YqTIREREC+IzpYETT0jCYfQ4Ao3wc6ZXRPdhQqgEQl0XXBxT94FcavB9KokPbg/kBjn0iEN9Pw9hgRwIye4FJyPm+0RpKjWh2gwDVPoMlCYDLkY8C49E3AelCCVOJJWQhCmiQBdw/FGfOX3iUAWE6eyonhQB0X2qk04bpD3BXjoWEdKxhtSPAEXhYlQwqkIdx7AXdeRIoBpcohiqYyIiSSR8ixCyZgFsWAVLhCAptj50rW1rp30BWjIYwgX42PUqM5xVsEIqaQAaJHrWg8VpANa2NdN8N9F8l7lWwWLoWSHVfatg4bRMgmttaxnBsvu1SMTZtwgIc4Fr5jGQxuj5dkXYyulDQK3tB0tPQsSgtGS8Z02nhTkso64UyLcI5GQBiUd9lQOFR4ENMjaEiQeFuqZEheAwjznEF47RGBqTEkf4PsRGFx6RoELBFSjj+0yRMDJ+ldgWSEh7jPe6WgyAJ5YUHqFEgiOkmysa4xp6gILAmAahD9Z2vV6q18tbta1Gc7NZLm1mxRbShZdL7YJiPU5TORCqGWjusTFCRVRfRL5LaBgClRvkNIx9jXHHj1wgf1Dl/EHeUOUAdxnvvSVCkj9wuj/IG/yTfG2izhiYyl4UANeEKf7f//ovnUSKJi54NPJj/Zthn7J8wQIeBZjwqHKsWEDrLqsYnwVMv1AxV30gAR2zIApSxzBWjlUhQUeSg7tBsJ0Z38SipLwHsc3LCL5SKpF1QjmJwhBk0tA4GFOkT6XrCDdOPmmyQe8PQXpCBiaVSaBKcPWE0lIDgruiu3LpuX5VLmUVlpi061Hmg/tCzV2CNulWxrkqdY94LDJLO+g4GDWIddWZTG+MJDNFrhS2ED5QPre/STCm/d10elewxusqCkMhtVqfpfY0Dc3CFQeslEr4Z0mMeAG0CpYjuAausQkNQ5/FSaD4VWG7hwww6vunnsmPCURhfwUHPS+UKLdm8Xxdn/GByojySDsFvvf9Vn0JXl5UGBfSxv35wJoWLA1BaHJ7jhKn06xdv8SD3hUszbQPmTE4jPUrgxRKGL4qSFNsln51bEyNsfUdn4DABtyqfF+UJAllGlIpKUYm0xA8w68CCETOClr4KzsmdRwR8dfmm/E+85WBmqfgVwYMPA8c/dpQhRIccOG1wTIHNHBfG6zMMeRVIVtqZDLYPGvMInUhOuYemfGCjOYXpb2bFizm5omTImGu8afMQSA3C8+P3nnSFqw+Vf3cjivZZr7Rm2mUcV2tYOPkiNilOh+EiKQD3dW0OpMqpFqDxK3S/pfW+m1pvXn3sLk5zchLXVfiFmqenrtBNIYcHS236OYpcgVVV+GZljuQ29aD/xz8zFiPifCzIz4mMjZ0+lT2HtFbQMddD/JVMPPl7rIanvIM4EPwRQjdsStzh4137d97HYCmj7ZBqZ5sgHuUbvxtnh+YE08k4Tm7oO8aKLNdywycpH7BXfbMxRJLK7aI+HOScsB4F9s/atNHXmawZko0Z1mgV3MYs6TwElgraWQR2KOvnwHtOAsGx2P8ecGc17BLey9oHMPu9mj4dBhE8zgYa0m76BGm7PVcP5s+RxFpDNhREHZftmbmZv/5jOb9/1aIZL7eA2hHQZgRGDsxzkH+hQV8Kr9muhyimAuiL+03TF10YeVfWOeTRT2zDckszyuL8ePr4OKqt7h4zEVZXRiWkv5Cil9N6NnsvGCHu+n0Me+3pnfTWb3JWObpkvP2g2WKpIv1kvTgGW8crb7WodouFvtx8Wxdg9Ic9IaKy/wbQvaKKzVqVSwlT3mr0ajUPduDarUJZW/T2azWyltO3QPXg4pT2oSGDU65Vi1Vy7UqOLW6XW00G2W71HSqXrOYrbn/I646v/vFFPneVX4xVdR3WJPM1E1eMfByrVSvNeqbzUat3CjVq9V6vihpveWvLIqpEaOnLpRdZoWVLz/pc1lMRc/ZpM2G51Qb9abr1UoNsN0adcpOBaoeeOA07BJtbDagUfG8sluuQbVeqW/Vt0oNu1mGxlJ14wUwkl6quN/ZOTo86FTrlerpzs3JQX3z+vp8p3pyvF/p1G92TnY6Z7fXxxfHO8enra36Vfv84rjeql7tLR4qXjBz3EkVq5Wt2la13FgtO/xZ2izOYTwk7lIwvlEwnmF26/PDJhaLFwsTfxruBMPzQWfrFj+I+h+zwP/l0charkX83FQYmE/PtbSX+POiMjnuWz890nJJwMoRfLEqEP+GEW+U/hPzpzGehutidcCqlCql9XJ5vVK9Kte3S5XtauN2dVeybf1wmnniYB8ro96obVXrm5vlaqXcWNrl/NS8C6drq1wqZbZJ6eeVU3R5+YxstfDp4T+dXb893mpKu39DvSq97h3bH4PSWaV9snuyRo+Zuqy2ivWbm4vPNWy+f95u1Cvn8/67raef+fuOaX+0c1W6OLw8X2w1Pjp3oEgrtU/7vFnxD3cq5VvdafauLjpewGpyV4/O1oL93Y9raY/mzvnS+K1dv/2tVW5/vn/vNgdNHp0J4Q5LN+33N2sHvX79+r54PRb3PT6c3C+BbM/k2+14tfJk8GkNvjUOP4ZHJ6dOjXVoX2+2gfmNk/C83fj04WBwOv5UlcK5bu9Vdw/ef7v+3DlUnebO/f3N1mdZPrPvPw42925rrP3+ZK/24cPiDjXRf6zPOYr5f08z2D6zHXur+PUUDsrjq/PP4+GWV1NtYGuj6w+dvc7WLr1nN/sj3lmL+7/L2QBnDX5obNHyTocnvZ8wgMN3PrYO7uVtrMA803cqbugGfnRbORre7vfD46A5uR3lt40VcHAv72/mnz9cXh8cDCs62uuHRTe8bGn9yT4v3uyWzqubIno/PnY6xbDf3/MSSQ6ORv6ygy4/TU4/34Z24DK7ciHo5ebQCZys8pee3Vhf+IxeJb52o96ozD+/MKBbrfbEObpuead6YD4e5k1ydlvxK/TTJr8JmgO6P4js6hFfCf5HMbZ2lvS5+sz8MR5kr9YL1oq1e95vOtelvYa9Vl07bn0WQ7XXaY3P18b7qha01dGoaFBnfKp9dE57J+cfGxPu3Z7dbn2tvz+wm/uty+CsXzsE/0Ox/IF+qB1tNdRoju980Ny93B0sYnqxfVtn59khzufyvjzB4fPunbVcesxE8od2o16/nrf+Ecu/r80tn2uZ51k+o/7XllkWTv/bFhd8qQiw/cWqrp044d6Qfxvu7NHLqyt+etirCBvOP4vQ69Drlrf3tb3ZUR91vX6w17pwx+3JN39vNDluFc9Vo3JarjevKo3y7enFJzjsXX69gE4HrXeXV5NdqLrO66pWCUtxcUnCVCVgrIGruNuXB2sAE2s7nyRSSGsPZit9hxLrvsAdQg90XETCnVfeufYhjxM3Xdh7orpADlMuXST9521grTyO0lXcjpyAHgk5MEyD/BG9CO3znDH30paEp6PeYSnPi1kDSXEnYSyhskCquHdpo7RRNpvVIKByMm9FQimGzDX0OHJwdXVGWmeHSA9yqabIBMqyM5NZN8ihJoz3QOmYVSdh3SjOsDvjnqEUbuSAS+xJ3hAxUw9ruzPWFVCFLEMtiCO4igJIu9IhSNoDkuH4EImVKTaElD+aYWatC8mAI8nSAJlRZxNyk6G92pMZoB0hAdliTBnJM3LYkrk9IDboEQDH6WNpF3ueSYHVUkV8NgAyQtKqVgXiggNcS+qze3AJjJ0+MtBUwYxAlQKUWUUgDaIZy0wLoiLbkNEyjlkghuKFJko21ynzsoBcvoRoCkNDEDY4FkinSJac9dxY8ay/uyd8yRr07k0ani7EJwmpFg6rCeyiIySsc+HC27+V9/zOf+fpdAmRnJrzL7hkyChxri+OC4QSW4qRAmlmEBxSButM15ed9+q7unaFo4paCF8VlTtQqGlBJKA7xfRrgUXrMdMTHN+wqcNYoQUyAkMKDQLgrqFko6Iox4kJ40oDdbFTQAdI5naZBEcbGyLvXBk5jVl7EXOBxBFjgyJ9MTIqcQPGkQwvSerixh1T3eAUhif6xtDiU+/80plJ+itp+6I318FoNFoUftZy3fZFr0jXOYzWVcTXcRXqw3qyfrw11FQlMEyoM+hJXHKJ4MvREPuOdPpMg6MjSX3CAox5CIzlRcJjDehXpLTHSwfB38HebpA9ZMzz+Lc4/JraIkJKq4GICkzmm7mGcMGmCgrE6YMzINg6K78hyu6jaucK6DHdj+wNRwTFRA/p31TUou0LuxhQxoud3Y+7x6dnhyf7G4H71pirDZ6QgIa3occ4km5/VWQkpEaqNNOmWJAQ9zENMAMCnL6Imb4GH4YlORHujyQC4grHUICNjrbJb7+NgLh4K0DjVQ4hFRAZcY4gUkWhyeI0RPHSAXepj+GSzRIzX/rttzgBgCG+U9+fmKFN3+6Q+sw1AnZX1jZA15dA9EgQBXhlQGPwcAckT5KKC46IQj/RT4BpmAW4/aJcGwezhVGjz6jNfIw47JVxr40F18foCiinPVCEoXONeIGEVIK77uLNjNS9hLcoqgg1C0zSwzmTnpjUMOUJj3CsZpI3I/jV90kmspB/jZc7frd2aGiWAxzud2umO3QRU42VgTr1LkEOmalipUZeqEdio3XhmaWMmV/vkGpMHVPnT6jYKeysQ+9h6BnjW4Wlzd7i1g4Cysxb8H3xz+w7LOwzB7iCzFytkDp9IJUNrHrNb2TM3qzHb+YzJumEmrdx4T8eVBWPD3d2Ty53sctGXwe+qZeGQumA8syU6U+AJPkNkCzdO1nYQjzMqdj/f3Hpb3txKTl4ahjrYuhTZngGxicfkoPZl9WLSehL249cV1o4m90VrL5QGgd5eMCl5Vr60yl+HV9/wBObyxSO8sgFiKyX/vmXinK1FR99Z9ekksOuZQ6PLxHuL3N36AktpLemflAJ/4fuCT2hpPQG1Q8q6X/oStATgFduMM2R3+EHyRD6C6P5zUXC6HlLXn5xMRdsylrikyzEWYDm5SvDo+kDRa+dl7FajgNh1kIrN5UWylj7u1fWdPpvprSVeQ==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Related Transactions"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/claimable_balances/{claimable_balance_id}/transactions"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents successful transactions referencing a given claimable balance and can be used in streaming mode. Streaming mode allows you to listen for new transactions referencing this claimable balance as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./cb-retrieve-related-transactions.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./cb-retrieve-related-transactions.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./cb-retrieve-related-transactions.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions.mdx b/docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions.mdx
new file mode 100644
index 000000000..3eb9b148a
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions.mdx
@@ -0,0 +1,12 @@
+---
+title: Retrieve Related Transactions
+openapi: "openapi/horizon/bundled.yml GET /claimable_balances/{claimable_balance_id}/transactions"
+---
+
+<Tip>
+
+**Supports Streaming**
+
+This endpoint supports streaming. To read more about this, visit the [streaming section](/docs/data/apis/horizon/api-reference/structure/streaming).
+
+</Tip>
diff --git a/docs/data/apis/horizon/api-reference/errors/README.mdx b/docs/data/apis/horizon/api-reference/errors/README.mdx
deleted file mode 100644
index 09000ae37..000000000
--- a/docs/data/apis/horizon/api-reference/errors/README.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: Errors
-sidebar_position: 40
----
-
-import { MethodTable } from "@site/src/components/MethodTable";
-
-After processing a request, Horizon returns a success or error response to the client. A success response will return a Status Code of 200, and an error response will return a Status Code in the range of 4XX - 5XX along with additional information about why the request could not complete successfully.
-
-There are two categories of errors:
-
-<MethodTable title="Error Categories">
-
-|  |  |
-| --- | --- |
-| [HTTP Status Codes](./http-status-codes/README.mdx) | Errors that occur at the Horizon Server level. |
-| [Result Codes](./result-codes/README.mdx) | Errors that occur at the Stellar Core level. |
-
-</MethodTable>
-
-Result Codes only follow a Transaction Failed (400) HTTP Status Code.
diff --git a/docs/data/apis/horizon/api-reference/errors/error-handling.mdx b/docs/data/apis/horizon/api-reference/errors/error-handling.mdx
index 90a226f7d..4541f334a 100644
--- a/docs/data/apis/horizon/api-reference/errors/error-handling.mdx
+++ b/docs/data/apis/horizon/api-reference/errors/error-handling.mdx
@@ -1,5 +1,6 @@
 ---
 title: Error Handling
+description: "It’s important to anticipate errors your users may encounter as you develop on Stellar."
 ---
 
 It’s important to anticipate errors your users may encounter as you develop on Stellar. In many tutorials throughout our developer documentation, we leave out error handling code to focus on the example. In this section, we will do the opposite and talk specifically about the errors. By the end of this section, you should be able to categorize errors and understand the best way to handle them in your application.
@@ -18,9 +19,9 @@ There are many possible error codes when executing these actions, and you can ty
 
 Many `GET` requests have specific parameter requirements, and while the SDKs can help enforce them, you can still pass invalid arguments (for example, an asset string that isn’t [SEP-11](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0011.md#asset-trustlineasset) compatible) that error out every time. In this scenario, there’s nothing you can do aside from following the API specification. The `extras` field of the error response will often clue you in on where to look and what to look for.
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 curl -s https://horizon-testnet.stellar.org/claimable_balances/0000 | jq '.extras'
 {
     "invalid_field": "id",
@@ -28,7 +29,7 @@ curl -s https://horizon-testnet.stellar.org/claimable_balances/0000 | jq '.extra
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Note that the SDKs make it a point to distinguish an invalid request (as above) versus a missing resource (a `404 Not Found`) (for example, the generic `NetworkError` versus a `NotFoundError` in the JavaScript SDK), where the latter might not be considered an error depending on your situation.
 
@@ -48,7 +49,7 @@ There are some resolution strategies that are common between the 2 endpoints whi
 Certain transaction submission failures also need adjustments to succeed.
 
 - If the XDR is malformed, or the transaction is otherwise invalid, you’ll encounter a `400 Bad Request` (for example, an invalid source account). Both transactions and their operations can be easily malformed or invalid: look at the `extras.result_codes` field for details and cross-reference them with the appropriate result codes documentation to determine specifics.
-- Transaction fees are also a safe adjustment by modifying the fees via a [fee-bump transaction](../../../../../build/guides/transactions/fee-bump-transactions.mdx) if you get a `tx_insufficient_fee` error. Refer to the [Insufficient Fees and Surge Pricing](#insufficient-fees-and-surge-pricing) section later in this document for more information on managing fees and strategies around it.
+- Transaction fees are also a safe adjustment by modifying the fees via a [fee-bump transaction](../../../../../build/guides/transactions/fee-bump-transactions) if you get a `tx_insufficient_fee` error. Refer to the [Insufficient Fees and Surge Pricing](#insufficient-fees-and-surge-pricing) section later in this document for more information on managing fees and strategies around it.
 
 ### Polling and Retrying Transactions
 
@@ -56,16 +57,16 @@ Certain transaction submission failures also need adjustments to succeed.
 
 Submissions using the `/transactions_async` endpoint return an immediate response back from Stellar-Core. There are different actions that clients can take based on the specific `tx_status` returned:
 
-1. `PENDING`: The submission is successful but the transaction is still waiting to be included in a ledger. You should use the [GET /transactions/:transaction_hash](../retrieve-a-transaction.api.mdx) endpoint to poll for the submitted transaction and check if it makes into a ledger. Note that even though the submission was successful, it can still fail to get included in the ledger.
+1. `PENDING`: The submission is successful but the transaction is still waiting to be included in a ledger. You should use the [GET /transactions/:transaction_hash](/docs/data/apis/horizon/api-reference/retrieve-a-transaction) endpoint to poll for the submitted transaction and check if it makes into a ledger. Note that even though the submission was successful, it can still fail to get included in the ledger.
 2. `DUPLICATE`: The submission was a duplicate of a previously submitted transaction. This could happen if the client resubmitted the same transaction multiple times.
 3. `ERROR`: The submission did not go through due to an error in Stellar-Core. Take a look at the attached error message for more details, modify your transaction if necessary, and resubmit.
 4. `TRY_AGAIN_LATER`: This indicates that the Stellar-Core instance is currently unable to process submission of this particular transaction. Clients should wait for sometime before resubmitting the transaction. This could happen due to different reasons:
    - There is another transaction from same source account in memory
    - It has been rejected due to too low inclusion fee and has been resubmitted too soon
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 let server = sdk.Server("https://horizon-testnet.stellar.org");
 let contractId = "CA3D5KRYM6CB7OWQ6TWYRR3Z4T7GNZLKERYNZGGA5SOAOPIFY6YQGAXE";
 let contract = new StellarSdk.Contract(contractId);
@@ -104,7 +105,7 @@ server
   });
 ```
 
-</CodeExample>
+</CodeGroup>
 
 #### Synchronous Transaction Submission
 
@@ -113,14 +114,14 @@ Due to the blocking nature of this endpoint, things are a little different compa
 1. The submission is successful and Horizon returns the transaction response back. This is the happy path and clients do not need to do anything but wait for Horizon's response.
 2. Stellar-Core sends back an `ERROR` response from the submission. Clients should consult the attached error message and retry the submission again.
 3. Timeouts: Horizon may respond with a `504` HTTP code. This response is not an error but a warning that your transaction hasn't been accepted by the network yet. There could be many possible reasons for the timeout, the most common of which is network congestion, but it could also be due to other transient issues.
-   1. **Polling the transaction hash**: Use the transaction hash in the timeout response and poll the [GET /transactions/:transaction_hash](../retrieve-a-transaction.api.mdx) endpoint to see if it successfully makes it into a ledger.
+   1. **Polling the transaction hash**: Use the transaction hash in the timeout response and poll the [GET /transactions/:transaction_hash](/docs/data/apis/horizon/api-reference/retrieve-a-transaction) endpoint to see if it successfully makes it into a ledger.
    2. **Resubmitting the transaction**: Before attempting any resubmissions, you need to make sure your transaction has timed out based on the time bounds you specified. After your transaction has expired, you can confirm it by polling the transaction again and getting a `tx_too_late` response from Horizon. Rebuild the transaction by updating the timebounds and resubmit the transaction.
 
-:::caution
+<Warning>
 
-Do note that resubmitting a transaction is only safe when it is unchanged - same operations, signatures, sequence number, etc... Be careful when working around an error that does require changes to the transaction. It can cause duplicate transactions, which can cause problems - double payments, incorrect trustlines, and more. If you continue to face timeouts on retries, consider using a fee-bump transaction to get into the ledger (after the initial transaction's timebound expires) or increasing the maximum fee you’re willing to pay. Read up on [Surge Pricing and Fee Strategies](../../../../../learn/fundamentals/fees-resource-limits-metering.mdx) for more details.
+Do note that resubmitting a transaction is only safe when it is unchanged - same operations, signatures, sequence number, etc... Be careful when working around an error that does require changes to the transaction. It can cause duplicate transactions, which can cause problems - double payments, incorrect trustlines, and more. If you continue to face timeouts on retries, consider using a fee-bump transaction to get into the ledger (after the initial transaction's timebound expires) or increasing the maximum fee you’re willing to pay. Read up on [Surge Pricing and Fee Strategies](../../../../../learn/fundamentals/fees-resource-limits-metering) for more details.
 
-:::
+</Warning>
 
 ### Example: Using Time Bounds
 
@@ -130,9 +131,9 @@ There are only two possible results to this scenario: either the transaction mak
 
 Example implementation:
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 import { Horizon } from "@stellar/stellar-sdk";
 
 let server = Horizon.Server("https://horizon-testnet.stellar.org");
@@ -162,7 +163,7 @@ function submitTransaction(tx, timeout) {
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
 We assume the existence of a sleep implementation similar to the one [here](https://stackoverflow.com/a/39914235). Be sure to integrate backoff into your retry mechanism. In our example error-handling code above, we implement a simple linear backoff, but there are [plenty of recommendations](https://backoff-utils.readthedocs.io/en/latest/strategies.html#why-are-backoff-strategies-useful) for various other strategies. Backoff is important both for maintaining performance and avoiding rate-limiting issues.
 
@@ -170,9 +171,9 @@ We assume the existence of a sleep implementation similar to the one [here](http
 
 These errors typically occur when you have an outdated view of an account. This could be because multiple devices are using this account, you have concurrent submissions happening, or other reasons. The solution is relatively simple: retrieve the account details and try again with an updated sequence number.
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 // suppose `account` is an outdated `AccountResponse` object
 let tx = sdk.TransactionBuilder(account, ...)/* etc */.build();
 server.submitTransaction(tx).catch(function (error) {
@@ -188,7 +189,7 @@ server.submitTransaction(tx).catch(function (error) {
 })
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Despite the solution’s simplicity, things can go wrong fast if you don’t understand why the error occurred.
 
@@ -200,15 +201,15 @@ Here, we will cover specific errors commonly encountered during transaction subm
 
 | Result | Code | Description |
 | --- | --- | --- |
-| `FAILED` | -1 | One of the operations failed (see [List of Operations](../../../../../learn/fundamentals/transactions/list-of-operations.mdx) for errors) |
+| `FAILED` | -1 | One of the operations failed (see [List of Operations](../../../../../learn/fundamentals/transactions/list-of-operations) for errors) |
 | `TOO_EARLY` | -2 | Ledger `closeTime` before `minTime` value in the transaction |
 | `TOO_LATE` | -3 | Ledger `closeTime` after `maxTime` value in the transaction |
 | `MISSING_OPERATION` | -4 | No operation was specified |
 | `BAD_SEQ` | -5 | Sequence number does not match source account |
 | `BAD_AUTH` | -6 | Too few valid signatures / wrong network |
-| `INSUFFICIENT_BALANCE` | -7 | Fee would bring account below minimum balance; see our section on [Lumens](../../../../../learn/fundamentals/lumens.mdx#minimum-balance) for more info |
+| `INSUFFICIENT_BALANCE` | -7 | Fee would bring account below minimum balance; see our section on [Lumens](../../../../../learn/fundamentals/lumens#minimum-balance) for more info |
 | `NO_ACCOUNT` | -8 | Source account not found |
-| `INSUFFICIENT_FEE` | -9 | Fee is too small; see our section on [Fees](../../../../../learn/fundamentals/fees-resource-limits-metering.mdx) for more info |
+| `INSUFFICIENT_FEE` | -9 | Fee is too small; see our section on [Fees](../../../../../learn/fundamentals/fees-resource-limits-metering) for more info |
 | `BAD_AUTH_EXTRA` | -10 | Unused signatures attached to transaction |
 | `INTERNAL_ERROR` | -11 | An unknown error occurred |
 | `NOT_SUPPORTED` | -12 | The transaction type is not supported |
@@ -217,7 +218,7 @@ Here, we will cover specific errors commonly encountered during transaction subm
 
 ### Insufficient fees and surge pricing
 
-See the [Fees section](../../../../../learn/fundamentals/fees-resource-limits-metering.mdx)
+See the [Fees section](../../../../../learn/fundamentals/fees-resource-limits-metering)
 
 ### Rate limiting
 
@@ -227,4 +228,4 @@ Horizon may rate limit requests and return `429 Too Many Requests` error when ex
 
 Any transaction that would reduce an account’s balance to less than the minimum will be rejected with an `INSUFFICIENT_BALANCE` error. Likewise, lumen selling liabilities that would reduce an account’s balance to less than the minimum plus lumen selling liabilities will be rejected with an `INSUFFICIENT_BALANCE` error.
 
-For more on minimum balances, see our [Lumens section](../../../../../learn/fundamentals/lumens.mdx#minimum-balance).
+For more on minimum balances, see our [Lumens section](../../../../../learn/fundamentals/lumens#minimum-balance).
diff --git a/docs/data/apis/horizon/api-reference/errors/http-status-codes/README.mdx b/docs/data/apis/horizon/api-reference/errors/http-status-codes/README.mdx
deleted file mode 100644
index 758ce5b77..000000000
--- a/docs/data/apis/horizon/api-reference/errors/http-status-codes/README.mdx
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: HTTP Status Codes
-order: 30
----
-
-import { MethodTable } from "@site/src/components/MethodTable";
-
-Some errors only occur at the Horizon level and are not thrown in Stellar Core. These are usually issues with how the transaction was formed or a conflict between the transaction’s composition and how the Horizon server is setup.
-
-Stellar uses conventional HTTP response codes to indicate the success or failure of an API request. In general:
-
-- Codes in the 2xx range indicate success.
-- Codes in the 4xx range indicate an error that failed given the information provided
-- Codes in the 5xx range indicate an error with the Horizon server.
-
-There are two types of Status Codes:
-
-<MethodTable title="HTTP Status Code Types">
-
-|  |  |
-| --- | --- |
-| [Standard Status Codes](./standard.mdx) | Generic HTTP responses. |
-| [Horizon-Specific Status Codes](./horizon-specific/README.mdx) | Errors that are unique to Horizon. |
-
-</MethodTable>
diff --git a/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/README.mdx b/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/README.mdx
deleted file mode 100644
index b0cf17fcf..000000000
--- a/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/README.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: Horizon-Specific Status Codes
-sidebar_position: 20
----
-
-import { MethodTable } from "@site/src/components/MethodTable";
-
-These responses are specific to how a Horizon server is set up and how transactions should be formed.
-
-<MethodTable title="Horizon-Specific Status Codes">
-
-|                                                      |     |
-| ---------------------------------------------------- | --- |
-| [Transaction Failed](./transaction-failed.mdx)       |     |
-| [Transaction Malformed](./transaction-malformed.mdx) |     |
-| [Before History](./before-history.mdx)               |     |
-| [Stale History](./stale-history.mdx)                 |     |
-| [Timeout](./timeout.mdx)                             |     |
-
-</MethodTable>
diff --git a/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/before-history.mdx b/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/before-history.mdx
index ac31fc9ed..8c73053cc 100644
--- a/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/before-history.mdx
+++ b/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/before-history.mdx
@@ -1,15 +1,13 @@
 ---
 title: Before History
-sidebar_position: 30
+description: "A Horizon server may be configured to only keep a portion of the stellar network’s history stored within its database."
 ---
 
 A Horizon server may be configured to only keep a portion of the stellar network’s history stored within its database.
 
 The `before_history` error returns a [`410` error code](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/410) and occurs a client requests a piece of information (such as a page of transactions or a single operation) that the server can positively identify as falling outside the range of recorded history.
 
-<ExampleResponse title="Example Response for a 'Before History' Status Code">
-
-```json
+```json Example Response for a 'Before History' Status Code
 {
   "type": "https://stellar.org/horizon-errors/before_history",
   "title": "Data Requested Is Before Recorded History",
@@ -17,5 +15,3 @@ The `before_history` error returns a [`410` error code](https://developer.mozill
   "detail": "This horizon instance is configured to only track a portion of the Stellar network's latest history. This request is asking for results prior to the recorded history known to this horizon instance."
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/index.mdx b/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/index.mdx
new file mode 100644
index 000000000..6c0e8efb0
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/index.mdx
@@ -0,0 +1,12 @@
+---
+title: Horizon-Specific Status Codes
+description: "These responses are specific to how a Horizon server is set up and how transactions should be formed."
+---
+
+| Horizon-Specific Status Codes |  |
+| --- | --- |
+| [Transaction Failed](/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-failed) |  |
+| [Transaction Malformed](/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-malformed) |  |
+| [Before History](/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/before-history) |  |
+| [Stale History](/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/stale-history) |  |
+| [Timeout](/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/timeout) |  |
diff --git a/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/stale-history.mdx b/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/stale-history.mdx
index f97205e96..329657cc7 100644
--- a/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/stale-history.mdx
+++ b/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/stale-history.mdx
@@ -1,15 +1,13 @@
 ---
 title: Stale History
-sidebar_position: 40
+description: "A Horizon server may be configured to reject historical requests when the history is known to be further out of date than the configured threshold."
 ---
 
 A Horizon server may be configured to reject historical requests when the history is known to be further out of date than the configured threshold.
 
 In such cases, the `stale_history` error occurs and returns a [`503` error code](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/503). To resolve this error (provided you are the Horizon instance’s operator), please ensure that the ingestion system is running correctly and importing new ledgers.
 
-<ExampleResponse title="Example Response for a 'Stale History' Status Code">
-
-```json
+```json Example Response for a 'Stale History' Status Code
 {
   "type": "https://stellar.org/horizon-errors/stale_history",
   "title": "Historical DB Is Too Stale",
@@ -17,5 +15,3 @@ In such cases, the `stale_history` error occurs and returns a [`503` error code]
   "detail": "This horizon instance is configured to reject client requests when it can determine that the history database is lagging too far behind the connected instance of stellar-core.  If you operate this server, please ensure that the ingestion system is properly running."
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/timeout.mdx b/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/timeout.mdx
index da2f5873e..abead58a6 100644
--- a/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/timeout.mdx
+++ b/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/timeout.mdx
@@ -1,6 +1,6 @@
 ---
 title: Timeout
-sidebar_position: 50
+description: "The timeout error returns a 504 error code and occurs when either:"
 ---
 
 The `timeout` error returns a [`504` error code](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/504) and occurs when either:
@@ -13,9 +13,7 @@ The former case may happen because there was no room for your transaction for 3
 - Keep resubmitting the same transaction (with the same sequence number) and wait until it finally is added to a new ledger, or
 - Increase the fee in order to prioritize the transaction.
 
-<ExampleResponse title="Example Response for a 'Timeout' Status Code">
-
-```json
+```json Example Response for a 'Timeout' Status Code
 {
   "type": "https://stellar.org/horizon-errors/timeout",
   "title": "Timeout",
@@ -23,5 +21,3 @@ The former case may happen because there was no room for your transaction for 3
   "detail": "Your request timed out before completing.  Please try your request again. If you are submitting a transaction make sure you are sending exactly the same transaction (with the same sequence number)."
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-failed.mdx b/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-failed.mdx
index 0064c131a..0e39ad59c 100644
--- a/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-failed.mdx
+++ b/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-failed.mdx
@@ -1,6 +1,6 @@
 ---
 title: Transaction Failed
-sidebar_position: 10
+description: "The transaction_failed error returns a 400 error code and occurs when a client submits a transaction that was well-formed but was not included in the ledger due to some other failure."
 ---
 
 The `transaction_failed` error returns a [`400` error code](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400) and occurs when a client submits a transaction that was well-formed but was not included in the ledger due to some other failure.
@@ -13,9 +13,7 @@ For example, a transaction may fail if:
 
 In almost every case, this error indicates that the transaction submitted in the initial request will never succeed. There is one exception: a transaction that fails with the `tx_bad_seq` result code (as expressed in the `result_code` field of the error) may become valid in the future if the sequence number it used was too high.
 
-<ExampleResponse title="Example Response for a 'Transaction Failed' Status Code">
-
-```json
+```json Example Response for a 'Transaction Failed' Status Code
 {
   "type": "https://stellar.org/horizon-errors/transaction_failed",
   "title": "Transaction Failed",
@@ -30,5 +28,3 @@ In almost every case, this error indicates that the transaction submitted in the
   }
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-malformed.mdx b/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-malformed.mdx
index 002b6f428..dd85e9146 100644
--- a/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-malformed.mdx
+++ b/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-malformed.mdx
@@ -1,6 +1,6 @@
 ---
 title: Transaction Malformed
-sidebar_position: 20
+description: "The transaction_malformed error returns a 400 error code and occurs when a client submits a malformed transaction."
 ---
 
 The `transaction_malformed` error returns a [`400` error code](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400) and occurs when a client submits a malformed transaction.
@@ -9,12 +9,10 @@ There are many ways in which a transaction could be malformed, including:
 
 1. You submitted an empty string.
 2. Your base64-encoded string is invalid.
-3. Your [XDR](../../../structure/xdr.mdx) structure is invalid.
-4. You have leftover bytes in your [XDR](../../../structure/xdr.mdx) structure.
+3. Your [XDR](../../../structure/xdr) structure is invalid.
+4. You have leftover bytes in your [XDR](../../../structure/xdr) structure.
 
-<ExampleResponse title="Example Response for a 'Transaction Malformed' Status Code">
-
-```json
+```json Example Response for a 'Transaction Malformed' Status Code
 {
   "type": "https://stellar.org/horizon-errors/transaction_malformed",
   "title": "Transaction Malformed",
@@ -25,5 +23,3 @@ There are many ways in which a transaction could be malformed, including:
   }
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/errors/http-status-codes/index.mdx b/docs/data/apis/horizon/api-reference/errors/http-status-codes/index.mdx
new file mode 100644
index 000000000..c6fcf9127
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/errors/http-status-codes/index.mdx
@@ -0,0 +1,18 @@
+---
+title: HTTP Status Codes
+description: "Some errors only occur at the Horizon level and are not thrown in Stellar Core. These are usually issues with how the transaction was formed or a conflict between the transaction’s composition and how the Horizon server is setup."
+order: 30
+---
+
+Stellar uses conventional HTTP response codes to indicate the success or failure of an API request. In general:
+
+- Codes in the 2xx range indicate success.
+- Codes in the 4xx range indicate an error that failed given the information provided
+- Codes in the 5xx range indicate an error with the Horizon server.
+
+There are two types of Status Codes:
+
+| HTTP Status Code Types |  |
+| --- | --- |
+| [Standard Status Codes](/docs/data/apis/horizon/api-reference/errors/http-status-codes/standard) | Generic HTTP responses. |
+| [Horizon-Specific Status Codes](/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific) | Errors that are unique to Horizon. |
diff --git a/docs/data/apis/horizon/api-reference/errors/http-status-codes/standard.mdx b/docs/data/apis/horizon/api-reference/errors/http-status-codes/standard.mdx
index 2818e17b2..eb5788bdc 100644
--- a/docs/data/apis/horizon/api-reference/errors/http-status-codes/standard.mdx
+++ b/docs/data/apis/horizon/api-reference/errors/http-status-codes/standard.mdx
@@ -1,39 +1,47 @@
 ---
 title: Standard Status Codes
-sidebar_position: 10
+description: "These responses are Internet protocol codes that describe basic issues with a submitted transaction."
 ---
 
 These responses are Internet protocol codes that describe basic issues with a submitted transaction.
 
-<AttributeTable>
-
-- STATUS CODE
-  - VALUE
-  - DESCRIPTION
-- OK
-  - 200
-  - The request has succeeded.
-- Bad Request
-  - 400
-  - The request as invalid in some way.
-- Not Found
-  - 404
-  - The requested resource does not exist.
-- Not Implemented
-  - 404
-  - The request does not have an acceptable response content-type.
-- Not Acceptable
-  - 406
-  - The request does not have an acceptable response content-type.
-- Internal Server Error
-  - 500
-  - Something went wrong on the Horizon server’s end.
-
-</AttributeTable>
-
-<ExampleResponse title="Example Response for a Bad Request Status Code">
-
-```json
+<ResponseField name="OK" type="200">
+
+The request has succeeded.
+
+</ResponseField>
+
+<ResponseField name="Bad Request" type="400">
+
+The request as invalid in some way.
+
+</ResponseField>
+
+<ResponseField name="Not Found" type="404">
+
+The requested resource does not exist.
+
+</ResponseField>
+
+<ResponseField name="Not Implemented" type="404">
+
+The request does not have an acceptable response content-type.
+
+</ResponseField>
+
+<ResponseField name="Not Acceptable" type="406">
+
+The request does not have an acceptable response content-type.
+
+</ResponseField>
+
+<ResponseField name="Internal Server Error" type="500">
+
+Something went wrong on the Horizon server’s end.
+
+</ResponseField>
+
+```json Example Response for a Bad Request Status Code
 {
   "type": "https://stellar.org/horizon-errors/bad_request",
   "title": "Bad Request",
@@ -45,5 +53,3 @@ These responses are Internet protocol codes that describe basic issues with a su
   }
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/errors/index.mdx b/docs/data/apis/horizon/api-reference/errors/index.mdx
new file mode 100644
index 000000000..7fa0f4d58
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/errors/index.mdx
@@ -0,0 +1,13 @@
+---
+title: Errors
+description: "After processing a request, Horizon returns a success or error response to the client. A success response will return a Status Code of 200, and an error response will return a Status Code in the range of 4XX - 5XX along with additional information about why the request could not complete successfully."
+---
+
+There are two categories of errors:
+
+| Error Categories |  |
+| --- | --- |
+| [HTTP Status Codes](/docs/data/apis/horizon/api-reference/errors/http-status-codes) | Errors that occur at the Horizon Server level. |
+| [Result Codes](/docs/data/apis/horizon/api-reference/errors/result-codes) | Errors that occur at the Stellar Core level. |
+
+Result Codes only follow a Transaction Failed (400) HTTP Status Code.
diff --git a/docs/data/apis/horizon/api-reference/errors/response.mdx b/docs/data/apis/horizon/api-reference/errors/response.mdx
index 3dc655813..33504df0e 100644
--- a/docs/data/apis/horizon/api-reference/errors/response.mdx
+++ b/docs/data/apis/horizon/api-reference/errors/response.mdx
@@ -1,48 +1,67 @@
 ---
 title: Error Response
-sidebar_position: 10
+description: "When any error occurs, Horizon responds with a JSON document with the below attributes."
 ---
 
 When any error occurs, Horizon responds with a JSON document with the below attributes.
 
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- type
-  - URL
-  - The type of Status Code returned.
-- title
-  - string
-  - A short title describing the Status Code, which can be used to look up more information about a error.
-- status
-  - number
-  - A short title describing the Status Code, which can be used to look up more information about a error.
-- detail
-  - string
-  - A short title describing the Status Code, which can be used to look up more information about a error.
-- extras
-  - map
-  - If the Status Code is `Transaction Failed`, this extras field displays the Result Code returned by Stellar Core describing why the transaction failed.
-    - envelope_xdr
-      - string
-      - A base64-encoded representation of the TransactionEnvelope XDR whose failure triggered this response.
-    - result_xdr
-      - string
-      - A base64-encoded representation of the TransactionResult XDR returned by stellar-core when submitting this transaction.
-    - result_codes.transaction
-      - string
-      - The transaction Result Code returned by Stellar Core, which can be used to look up more information about an error in the docs.
-    - result_codes.operations
-      - array
-      - An array of operation Result Codes returned by Stellar Core, which can be used to look up more information about an error in the docs.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
+<ResponseField name="type" type="URL">
+
+The type of Status Code returned.
+
+</ResponseField>
+
+<ResponseField name="title" type="string">
+
+A short title describing the Status Code, which can be used to look up more information about a error.
+
+</ResponseField>
+
+<ResponseField name="status" type="number">
+
+A short title describing the Status Code, which can be used to look up more information about a error.
+
+</ResponseField>
+
+<ResponseField name="detail" type="string">
+
+A short title describing the Status Code, which can be used to look up more information about a error.
+
+</ResponseField>
+
+<ResponseField name="extras" type="map">
+
+If the Status Code is `Transaction Failed`, this extras field displays the Result Code returned by Stellar Core describing why the transaction failed.
+
+  <Expandable title="extras properties">
+    <ResponseField name="envelope_xdr" type="string">
+
+      A base64-encoded representation of the TransactionEnvelope XDR whose failure triggered this response.
+
+    </ResponseField>
+
+    <ResponseField name="result_xdr" type="string">
+
+      A base64-encoded representation of the TransactionResult XDR returned by stellar-core when submitting this transaction.
+
+    </ResponseField>
+
+    <ResponseField name="result_codes.transaction" type="string">
+
+      The transaction Result Code returned by Stellar Core, which can be used to look up more information about an error in the docs.
+
+    </ResponseField>
+
+    <ResponseField name="result_codes.operations" type="array">
+
+      An array of operation Result Codes returned by Stellar Core, which can be used to look up more information about an error in the docs.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+```json Example
 {
   "type": "https://stellar.org/horizon-errors/transaction_failed",
   "title": "Transaction Failed",
@@ -58,5 +77,3 @@ When any error occurs, Horizon responds with a JSON document with the below attr
   }
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/errors/result-codes/README.mdx b/docs/data/apis/horizon/api-reference/errors/result-codes/README.mdx
deleted file mode 100644
index f5e87eaa7..000000000
--- a/docs/data/apis/horizon/api-reference/errors/result-codes/README.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Result Codes
-order: 40
----
-
-import { MethodTable } from "@site/src/components/MethodTable";
-
-Result Codes describe why a transaction or operation failed in Stellar Core and are communicated in the “extras” field of a Horizon response when the “Transaction Failed” Status Code is returned.
-
-In the “extras” field, the errors returned are referred to as “Result Codes” and are Horizon’s abstraction of “Stellar Protocol Codes”, which are more specific codes available in the XDR. Result Codes are Horizon’s way of normalizing Stellar Protocol Codes.
-
-There are three types of Result Codes:
-
-<MethodTable title="Result Code Types">
-
-|  |  |
-| --- | --- |
-| [Transaction Result Codes](./transactions.mdx) | Generic errors about transaction failures. |
-| [Operation Result Codes](./operations.mdx) | Generic errors about operation failures. |
-| [Operation-Specific Result Codes](./operation-specific/README.mdx) | Errors specific to each operation type. |
-
-</MethodTable>
diff --git a/docs/data/apis/horizon/api-reference/errors/result-codes/index.mdx b/docs/data/apis/horizon/api-reference/errors/result-codes/index.mdx
new file mode 100644
index 000000000..ca757b421
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/errors/result-codes/index.mdx
@@ -0,0 +1,15 @@
+---
+title: Result Codes
+description: "Result Codes describe why a transaction or operation failed in Stellar Core and are communicated in the “extras” field of a Horizon response when the “Transaction Failed” Status Code is returned."
+order: 40
+---
+
+In the “extras” field, the errors returned are referred to as “Result Codes” and are Horizon’s abstraction of “Stellar Protocol Codes”, which are more specific codes available in the XDR. Result Codes are Horizon’s way of normalizing Stellar Protocol Codes.
+
+There are three types of Result Codes:
+
+| Result Code Types |  |
+| --- | --- |
+| [Transaction Result Codes](/docs/data/apis/horizon/api-reference/errors/result-codes/transactions) | Generic errors about transaction failures. |
+| [Operation Result Codes](/docs/data/apis/horizon/api-reference/errors/result-codes/operations) | Generic errors about operation failures. |
+| [Operation-Specific Result Codes](/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific) | Errors specific to each operation type. |
diff --git a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/README.mdx b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/README.mdx
deleted file mode 100644
index d79d35dc6..000000000
--- a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/README.mdx
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: Operation-Specific Result Codes
-order: 30
----
-
-import { MethodTable } from "@site/src/components/MethodTable";
-
-These are Result Codes that communicate success (200) or failure (400) responses that are specific to each operation type.
-
-Each of Stellar's operations have unique causes of failure, and these result codes will help you diagnose and address the origins of issues.
-
-<MethodTable title="Operation-Specific Result Code Types">
-
-|                                                                  |     |
-| ---------------------------------------------------------------- | --- |
-| [Create Account](./create-account.mdx)                           |     |
-| [Payment](./payment.mdx)                                         |     |
-| [Path Payment Strict Receive](./path-payment-strict-receive.mdx) |     |
-| [Path Payment Strict Send](./path-payment-strict-send.mdx)       |     |
-| [Manage Sell Offer](./manage-sell-offer.mdx)                     |     |
-| [Manage Buy Offer](./manage-buy-offer.mdx)                       |     |
-| [Create Passive Sell Offer](./create-passive-sell-offer.mdx)     |     |
-| [Set Options](./set-options.mdx)                                 |     |
-| [Change Trust](./change-trust.mdx)                               |     |
-| [Allow Trust](./allow-trust.mdx)                                 |     |
-| [Account Merge](./account-merge.mdx)                             |     |
-| [Manage Data](./manage-data.mdx)                                 |     |
-| [Bump Sequence](./bump-sequence.mdx)                             |     |
-
-</MethodTable>
-
-For operations that aren't in this list, you can usually refer to their corresponding entries in the [List of Operations](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx) which will enumerate the failure cases and corresponding result codes.
diff --git a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/account-merge.mdx b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/account-merge.mdx
index f4eb19853..95f6364c5 100644
--- a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/account-merge.mdx
+++ b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/account-merge.mdx
@@ -1,37 +1,56 @@
 ---
 title: Account Merge Result Codes
-sidebar_position: 110
+description: "These are result codes that communicate success (200) or failure (400) specific to the Account Merge operation."
 ---
 
 These are result codes that communicate success (200) or failure (400) specific to the `Account Merge` operation.
 
-Learn more about the [`Account Merge` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#account-merge).
-
-<AttributeTable>
-
-- OpSuccess
-  - ACCOUNT_MERGE_SUCCESS
-  - Account succesfully merged.
-- OpMalformed
-  - ACCOUNT_MERGE_MALFORMED
-  - The operation is malformed because the source account cannot merge with itself. The destination must be a different account.
-- op_no_account
-  - ACCOUNT_MERGE_NO_ACCOUNT
-  - The destination account does not exist.
-- op_immutable_set
-  - ACCOUNT_MERGE_IMMUTABLE_SET
-  - The source account has AUTH_IMMUTABLE flag set.
-- op_has_sub_entries
-  - ACCOUNT_MERGE_HAS_SUB_ENTRIES
-  - The source account still has non-signer subentries (trustlines, offers, or data entries). Signers are not a blocker — they are removed automatically as part of the merge.
-- op_seq_num_too_far
-  - ACCOUNT_MERGE_SEQNUM_TOO_FAR
-  - Source account sequence number is too high.
-- op_dest_full
-  - ACCOUNT_MERGE_DEST_FULL
-  - The destination account cannot receive the balance of the source account and still satisfy its lumen buying liabilities.
-- op_is_sponsor
-  - ACCOUNT_MERGE_IS_SPONSOR
-  - The source account cannot be merged because it is sponsoring reserves. This covers two cases: it is already sponsoring reserves for other accounts (`numSponsoring > 0`), which must be revoked first; or it has an open is-sponsoring-future-reserves relationship earlier in the same transaction, which must be ended with `EndSponsoringFutureReserves` (there may be no created reserve to revoke in this case). Merely being sponsored by another account is not a blocker.
-
-</AttributeTable>
+Learn more about the [`Account Merge` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations#account-merge).
+
+<ResponseField name="OpSuccess" type="ACCOUNT_MERGE_SUCCESS">
+
+Account succesfully merged.
+
+</ResponseField>
+
+<ResponseField name="OpMalformed" type="ACCOUNT_MERGE_MALFORMED">
+
+The operation is malformed because the source account cannot merge with itself. The destination must be a different account.
+
+</ResponseField>
+
+<ResponseField name="op_no_account" type="ACCOUNT_MERGE_NO_ACCOUNT">
+
+The destination account does not exist.
+
+</ResponseField>
+
+<ResponseField name="op_immutable_set" type="ACCOUNT_MERGE_IMMUTABLE_SET">
+
+The source account has AUTH_IMMUTABLE flag set.
+
+</ResponseField>
+
+<ResponseField name="op_has_sub_entries" type="ACCOUNT_MERGE_HAS_SUB_ENTRIES">
+
+The source account still has non-signer subentries (trustlines, offers, or data entries). Signers are not a blocker — they are removed automatically as part of the merge.
+
+</ResponseField>
+
+<ResponseField name="op_seq_num_too_far" type="ACCOUNT_MERGE_SEQNUM_TOO_FAR">
+
+Source account sequence number is too high.
+
+</ResponseField>
+
+<ResponseField name="op_dest_full" type="ACCOUNT_MERGE_DEST_FULL">
+
+The destination account cannot receive the balance of the source account and still satisfy its lumen buying liabilities.
+
+</ResponseField>
+
+<ResponseField name="op_is_sponsor" type="ACCOUNT_MERGE_IS_SPONSOR">
+
+The source account cannot be merged because it is sponsoring reserves. This covers two cases: it is already sponsoring reserves for other accounts (`numSponsoring > 0`), which must be revoked first; or it has an open is-sponsoring-future-reserves relationship earlier in the same transaction, which must be ended with `EndSponsoringFutureReserves` (there may be no created reserve to revoke in this case). Merely being sponsored by another account is not a blocker.
+
+</ResponseField>
diff --git a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/allow-trust.mdx b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/allow-trust.mdx
index 7463c2098..e0fb68495 100644
--- a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/allow-trust.mdx
+++ b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/allow-trust.mdx
@@ -1,34 +1,50 @@
 ---
 title: Allow Trust Result Codes
-sidebar_position: 100
+description: "These are result codes that communicate success (200) or failure (400) specific to the Allow Trust operation."
 ---
 
 These are result codes that communicate success (200) or failure (400) specific to the `Allow Trust` operation.
 
-Learn more about the [`Allow Trust` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#allow-trust).
-
-<AttributeTable>
-
-- OpSuccess
-  - ALLOW_TRUST_SUCCESS
-  - Trust trust operation was successful.
-- OpMalformed
-  - ALLOW_TRUST_MALFORMED
-  - The asset specified in type is invalid. In addition, this error happens when the native asset is specified.
-- op_no_trustline
-  - ALLOW_TRUST_NO_TRUST_LINE
-  - The trustor does not have a trustline with the issuer performing this operation.
-- op_not_required
-  - ALLOW_TRUST_TRUST_NOT_REQUIRED
-  - The source account (issuer performing this operation) does not require trust. In other words, it does not have to have the flag AUTH_REQUIRED_FLAG set.
-- op_cant_revoke
-  - ALLOW_TRUST_CANT_REVOKE
-  - The source account is trying to revoke the trustline of the trustor, but it cannot do so.
-- op_self_not_allowed
-  - ALLOW_TRUST_SELF_NOT_ALLOWED
-  - The source account attempted to allow a trustline for itself, which is not allowed because an account cannot create a trustline with itself.
-- op_low_reserve
-  - ALLOW_TRUST_LOW_RESERVE
-  - Claimable balances can't be created on revoke due to low reserves
-
-</AttributeTable>
+Learn more about the [`Allow Trust` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations#allow-trust).
+
+<ResponseField name="OpSuccess" type="ALLOW_TRUST_SUCCESS">
+
+Trust trust operation was successful.
+
+</ResponseField>
+
+<ResponseField name="OpMalformed" type="ALLOW_TRUST_MALFORMED">
+
+The asset specified in type is invalid. In addition, this error happens when the native asset is specified.
+
+</ResponseField>
+
+<ResponseField name="op_no_trustline" type="ALLOW_TRUST_NO_TRUST_LINE">
+
+The trustor does not have a trustline with the issuer performing this operation.
+
+</ResponseField>
+
+<ResponseField name="op_not_required" type="ALLOW_TRUST_TRUST_NOT_REQUIRED">
+
+The source account (issuer performing this operation) does not require trust. In other words, it does not have to have the flag AUTH_REQUIRED_FLAG set.
+
+</ResponseField>
+
+<ResponseField name="op_cant_revoke" type="ALLOW_TRUST_CANT_REVOKE">
+
+The source account is trying to revoke the trustline of the trustor, but it cannot do so.
+
+</ResponseField>
+
+<ResponseField name="op_self_not_allowed" type="ALLOW_TRUST_SELF_NOT_ALLOWED">
+
+The source account attempted to allow a trustline for itself, which is not allowed because an account cannot create a trustline with itself.
+
+</ResponseField>
+
+<ResponseField name="op_low_reserve" type="ALLOW_TRUST_LOW_RESERVE">
+
+Claimable balances can't be created on revoke due to low reserves
+
+</ResponseField>
diff --git a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/bump-sequence.mdx b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/bump-sequence.mdx
index 077858c67..9daf5c4aa 100644
--- a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/bump-sequence.mdx
+++ b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/bump-sequence.mdx
@@ -1,19 +1,20 @@
 ---
 title: Bump Sequence Result Codes
-sidebar_position: 130
+description: "These are result codes that communicate success (200) or failure (400) specific to the Bump Sequence operation."
 ---
 
 These are result codes that communicate success (200) or failure (400) specific to the `Bump Sequence` operation.
 
-Learn more about the [`Bump Sequence` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#bump-sequence).
+Learn more about the [`Bump Sequence` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations#bump-sequence).
 
-<AttributeTable>
+<ResponseField name="OpSuccess" type="BUMP_SEQUENCE_SUCCESS">
 
-- OpSuccess
-  - BUMP_SEQUENCE_SUCCESS
-  - Sequence number has been bumped.
-- op_bad_seq
-  - BUMP_SEQUENCE_BAD_SEQ
-  - The specified bumpTo sequence number is not a valid sequence number. It must be between 0 and INT64_MAX (9223372036854775807 or 0x7fffffffffffffff).
+Sequence number has been bumped.
 
-</AttributeTable>
+</ResponseField>
+
+<ResponseField name="op_bad_seq" type="BUMP_SEQUENCE_BAD_SEQ">
+
+The specified bumpTo sequence number is not a valid sequence number. It must be between 0 and INT64_MAX (9223372036854775807 or 0x7fffffffffffffff).
+
+</ResponseField>
diff --git a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/change-trust.mdx b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/change-trust.mdx
index e95f5f05e..b24b1b618 100644
--- a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/change-trust.mdx
+++ b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/change-trust.mdx
@@ -1,31 +1,44 @@
 ---
 title: Change Trust Result Codes
-sidebar_position: 90
+description: "These are result codes that communicate success (200) or failure (400) specific to the Change Trust operation."
 ---
 
 These are result codes that communicate success (200) or failure (400) specific to the `Change Trust` operation.
 
-Learn more about the [`Change Trust` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#change-trust)
-
-<AttributeTable>
-
-- OpSuccess
-  - CHANGE_TRUST_SUCCESS
-  - Trust was successfully changed
-- OpMalformed
-  - CHANGE_TRUST_MALFORMED
-  - The input to this operation is invalid.
-- OpNoIssuer
-  - CHANGE_TRUST_NO_ISSUER
-  - The issuer of the asset cannot be found.
-- op_invalid_limit
-  - CHANGE_TRUST_INVALID_LIMIT
-  - The limit is not sufficient to hold the current balance of the trustline and still satisfy its buying liabilities.
-- OpLowReserve
-  - CHANGE_TRUST_LOW_RESERVE
-  - This account does not have enough XLM to satisfy the minimum XLM reserve increase caused by adding a subentry and still satisfy its XLM selling liabilities. For every new trustline added to an account, the minimum reserve of XLM that account must hold increases.
-- op_self_not_allowed
-  - CHANGE_TRUST_SELF_NOT_ALLOWED
-  - The source account attempted to create a trustline for itself, which is not allowed.
-
-</AttributeTable>
+Learn more about the [`Change Trust` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations#change-trust)
+
+<ResponseField name="OpSuccess" type="CHANGE_TRUST_SUCCESS">
+
+Trust was successfully changed
+
+</ResponseField>
+
+<ResponseField name="OpMalformed" type="CHANGE_TRUST_MALFORMED">
+
+The input to this operation is invalid.
+
+</ResponseField>
+
+<ResponseField name="OpNoIssuer" type="CHANGE_TRUST_NO_ISSUER">
+
+The issuer of the asset cannot be found.
+
+</ResponseField>
+
+<ResponseField name="op_invalid_limit" type="CHANGE_TRUST_INVALID_LIMIT">
+
+The limit is not sufficient to hold the current balance of the trustline and still satisfy its buying liabilities.
+
+</ResponseField>
+
+<ResponseField name="OpLowReserve" type="CHANGE_TRUST_LOW_RESERVE">
+
+This account does not have enough XLM to satisfy the minimum XLM reserve increase caused by adding a subentry and still satisfy its XLM selling liabilities. For every new trustline added to an account, the minimum reserve of XLM that account must hold increases.
+
+</ResponseField>
+
+<ResponseField name="op_self_not_allowed" type="CHANGE_TRUST_SELF_NOT_ALLOWED">
+
+The source account attempted to create a trustline for itself, which is not allowed.
+
+</ResponseField>
diff --git a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-account.mdx b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-account.mdx
index bf56d07af..b9940cf67 100644
--- a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-account.mdx
+++ b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-account.mdx
@@ -1,31 +1,38 @@
 ---
 title: Create Account Result Codes
-sidebar_position: 10
+description: "These are result codes that communicate success (200) or failure (400) specific to the Create Account operation, which often fails because the new account..."
 ---
 
 These are result codes that communicate success (200) or failure (400) specific to the `Create Account` operation, which often fails because the new account does not meet the minimum reserve.
 
-Learn more about the [`Create Account` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#create-account).
-
-<AttributeTable>
-
-- RESULT CODE
-  - STELLAR PROTOCOL CODE
-  - DESCRIPTION
-- OpSuccess
-  - CREATE_ACCOUNT_SUCCESS
-  - The inner object result is valid, the operation was a success, and an acount was created.
-- OpMalformed
-  - CREATE_ACCOUNT_MALFORMED
-  - The destination was invalid.
-- OpUnderfunded
-  - CREATE_ACCOUNT_UNDERFUNDED
-  - The source account performing the command does not have enough funds to give the destination account the necessary mininum reserve and still maintain its own minimum reserve.
-- OpLowReserve
-  - CREATE_ACCOUNT_LOW_RESERVE
-  - The operation would create an account below the minimum reserve.
-- OpAlreadyExists
-  - CREATE_ACCOUNT_ALREADY_EXIST
-  - The destination account already exists.
-
-</AttributeTable>
+Learn more about the [`Create Account` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations#create-account).
+
+<ResponseField name="OpSuccess" type="CREATE_ACCOUNT_SUCCESS">
+
+The inner object result is valid, the operation was a success, and an acount was created.
+
+</ResponseField>
+
+<ResponseField name="OpMalformed" type="CREATE_ACCOUNT_MALFORMED">
+
+The destination was invalid.
+
+</ResponseField>
+
+<ResponseField name="OpUnderfunded" type="CREATE_ACCOUNT_UNDERFUNDED">
+
+The source account performing the command does not have enough funds to give the destination account the necessary mininum reserve and still maintain its own minimum reserve.
+
+</ResponseField>
+
+<ResponseField name="OpLowReserve" type="CREATE_ACCOUNT_LOW_RESERVE">
+
+The operation would create an account below the minimum reserve.
+
+</ResponseField>
+
+<ResponseField name="OpAlreadyExists" type="CREATE_ACCOUNT_ALREADY_EXIST">
+
+The destination account already exists.
+
+</ResponseField>
diff --git a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-passive-sell-offer.mdx b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-passive-sell-offer.mdx
index c1c7b24dd..8705f4f37 100644
--- a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-passive-sell-offer.mdx
+++ b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-passive-sell-offer.mdx
@@ -1,52 +1,86 @@
 ---
 title: Create Passive Sell Offer Result Codes
-sidebar_position: 70
+description: "These are result codes that communicate success (200) or failure (400) specific to the Create Passive Sell Offer operation."
 ---
 
 These are result codes that communicate success (200) or failure (400) specific to the `Create Passive Sell Offer` operation.
 
-Learn more about the [`Create Passive Sell Offer` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#create-passive-sell-offer).
-
-<AttributeTable>
-
-- OpSuccess
-  - CREATE_PASSIVE_SELL_OFFER_SUCCESS
-  - The passive sell offer was successfully placed.
-- OpMalformed
-  - MANAGE_SELL_OFFER_MALFORMED
-  - The input is incorrect and would result in an invalid offer.
-- op_sell_no_trust
-  - MANAGE_SELL_OFFER_SELL_NO_TRUST
-  - The account creating the offer does not have a trustline for the asset it is selling.
-- op_buy_no_trust
-  - MANAGE_SELL_OFFER_BUY_NO_TRUST
-  - The account creating the offer does not have a trustline for the asset it is buying.
-- sell_not_authorized
-  - MANAGE_SELL_OFFER_SELL_NOT_AUTHORIZED
-  - The account creating the offer is not authorized to sell this asset.
-- buy_not_authorized
-  - MANAGE_SELL_OFFER_BUY_NOT_AUTHORIZED
-  - The account creating the offer is not authorized to buy this asset.
-- OpLineFull
-  - MANAGE_SELL_OFFER_LINE_FULL
-  - The account creating the offer does not have sufficient limits to receive buying and still satisfy its buying liabilities.
-- OpUnderfunded
-  - MANAGE_SELL_OFFER_UNDERFUNDED
-  - The account creating the offer does not have sufficient limits to send selling and still satisfy its selling liabilities. Note that if selling XLM then the account must additionally maintain its minimum XLM reserve, which is calculated assuming this offer will not completely execute immediately.
-- op_cross_self
-  - MANAGE_SELL_OFFER_CROSS_SELF
-  - The account has opposite offer of equal or lesser price active, so the account creating this offer would immediately cross itself.
-- op_sell_no_issuer
-  - MANAGE_SELL_OFFER_SELL_NO_ISSUER
-  - The issuer of selling asset does not exist.
-- buy_no_issuer
-  - MANAGE_SELL_OFFER_BUY_NO_ISSUER
-  - The issuer of buying asset does not exist.
-- op_offer_not_found
-  - MANAGE_SELL_OFFER_NOT_FOUND
-  - An offer with that offerID cannot be found.
-- OpLowReserve
-  - MANAGE_SELL_OFFER_LOW_RESERVE
-  - The account creating this offer does not have enough XLM to satisfy the minimum XLM reserve increase caused by adding a subentry and still satisfy its XLM selling liabilities. For every offer an account creates, the minimum amount of XLM that account must hold will increase.
-
-</AttributeTable>
+Learn more about the [`Create Passive Sell Offer` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations#create-passive-sell-offer).
+
+<ResponseField name="OpSuccess" type="CREATE_PASSIVE_SELL_OFFER_SUCCESS">
+
+The passive sell offer was successfully placed.
+
+</ResponseField>
+
+<ResponseField name="OpMalformed" type="MANAGE_SELL_OFFER_MALFORMED">
+
+The input is incorrect and would result in an invalid offer.
+
+</ResponseField>
+
+<ResponseField name="op_sell_no_trust" type="MANAGE_SELL_OFFER_SELL_NO_TRUST">
+
+The account creating the offer does not have a trustline for the asset it is selling.
+
+</ResponseField>
+
+<ResponseField name="op_buy_no_trust" type="MANAGE_SELL_OFFER_BUY_NO_TRUST">
+
+The account creating the offer does not have a trustline for the asset it is buying.
+
+</ResponseField>
+
+<ResponseField name="sell_not_authorized" type="MANAGE_SELL_OFFER_SELL_NOT_AUTHORIZED">
+
+The account creating the offer is not authorized to sell this asset.
+
+</ResponseField>
+
+<ResponseField name="buy_not_authorized" type="MANAGE_SELL_OFFER_BUY_NOT_AUTHORIZED">
+
+The account creating the offer is not authorized to buy this asset.
+
+</ResponseField>
+
+<ResponseField name="OpLineFull" type="MANAGE_SELL_OFFER_LINE_FULL">
+
+The account creating the offer does not have sufficient limits to receive buying and still satisfy its buying liabilities.
+
+</ResponseField>
+
+<ResponseField name="OpUnderfunded" type="MANAGE_SELL_OFFER_UNDERFUNDED">
+
+The account creating the offer does not have sufficient limits to send selling and still satisfy its selling liabilities. Note that if selling XLM then the account must additionally maintain its minimum XLM reserve, which is calculated assuming this offer will not completely execute immediately.
+
+</ResponseField>
+
+<ResponseField name="op_cross_self" type="MANAGE_SELL_OFFER_CROSS_SELF">
+
+The account has opposite offer of equal or lesser price active, so the account creating this offer would immediately cross itself.
+
+</ResponseField>
+
+<ResponseField name="op_sell_no_issuer" type="MANAGE_SELL_OFFER_SELL_NO_ISSUER">
+
+The issuer of selling asset does not exist.
+
+</ResponseField>
+
+<ResponseField name="buy_no_issuer" type="MANAGE_SELL_OFFER_BUY_NO_ISSUER">
+
+The issuer of buying asset does not exist.
+
+</ResponseField>
+
+<ResponseField name="op_offer_not_found" type="MANAGE_SELL_OFFER_NOT_FOUND">
+
+An offer with that offerID cannot be found.
+
+</ResponseField>
+
+<ResponseField name="OpLowReserve" type="MANAGE_SELL_OFFER_LOW_RESERVE">
+
+The account creating this offer does not have enough XLM to satisfy the minimum XLM reserve increase caused by adding a subentry and still satisfy its XLM selling liabilities. For every offer an account creates, the minimum amount of XLM that account must hold will increase.
+
+</ResponseField>
diff --git a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/index.mdx b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/index.mdx
new file mode 100644
index 000000000..5c4495e8e
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/index.mdx
@@ -0,0 +1,25 @@
+---
+title: Operation-Specific Result Codes
+description: "These are Result Codes that communicate success (200) or failure (400) responses that are specific to each operation type."
+order: 30
+---
+
+Each of Stellar's operations have unique causes of failure, and these result codes will help you diagnose and address the origins of issues.
+
+| Operation-Specific Result Code Types |  |
+| --- | --- |
+| [Create Account](/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-account) |  |
+| [Payment](/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/payment) |  |
+| [Path Payment Strict Receive](/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-receive) |  |
+| [Path Payment Strict Send](/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-send) |  |
+| [Manage Sell Offer](/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-sell-offer) |  |
+| [Manage Buy Offer](/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-buy-offer) |  |
+| [Create Passive Sell Offer](/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-passive-sell-offer) |  |
+| [Set Options](/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/set-options) |  |
+| [Change Trust](/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/change-trust) |  |
+| [Allow Trust](/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/allow-trust) |  |
+| [Account Merge](/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/account-merge) |  |
+| [Manage Data](/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-data) |  |
+| [Bump Sequence](/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/bump-sequence) |  |
+
+For operations that aren't in this list, you can usually refer to their corresponding entries in the [List of Operations](/docs/learn/fundamentals/transactions/list-of-operations) which will enumerate the failure cases and corresponding result codes.
diff --git a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-buy-offer.mdx b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-buy-offer.mdx
index c4635616a..f7f73d846 100644
--- a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-buy-offer.mdx
+++ b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-buy-offer.mdx
@@ -1,52 +1,86 @@
 ---
 title: Manage Buy Offer Result Codes
-sidebar_position: 60
+description: "These are result codes that communicate success (200) or failure (400) specific to the Manage Buy Offer operation."
 ---
 
 These are result codes that communicate success (200) or failure (400) specific to the `Manage Buy Offer` operation.
 
-Learn more about the [`Manage Buy Offer` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#manage-buy-offer).
-
-<AttributeTable>
-
-- OpSuccess
-  - MANAGE_BUY_OFFER_SUCCESS
-  - The offer was successfully placed.
-- OpMalformed
-  - MANAGE_BUY_OFFER_MALFORMED
-  - The input is incorrect and would result in an invalid offer.
-- op_sell_no_trust
-  - MANAGE_BUY_OFFER_SELL_NO_TRUST
-  - The account creating the offer does not have a trustline for the asset it is selling.
-- op_buy_no_trust
-  - MANAGE_BUY_OFFER_BUY_NO_TRUST
-  - The account creating the offer does not have a trustline for the asset it is buying.
-- sell_not_authorized
-  - MANAGE_BUY_OFFER_SELL_NOT_AUTHORIZED
-  - The account creating the offer is not authorized to sell this asset.
-- buy_not_authorized
-  - MANAGE_BUY_OFFER_BUY_NOT_AUTHORIZED
-  - The account creating the offer is not authorized to buy this asset.
-- OpLineFull
-  - MANAGE_BUY_OFFER_LINE_FULL
-  - The account creating the offer does not have sufficient limits to receive buying and still satisfy its buying liabilities.
-- OpUnderfunded
-  - MANAGE_BUY_OFFER_UNDERFUNDED
-  - The account creating the offer does not have sufficient limits to send selling and still satisfy its selling liabilities. Note that if selling XLM then the account must additionally maintain its minimum XLM reserve, which is calculated assuming this offer will not completely execute immediately.
-- op_cross_self
-  - MANAGE_BUY_OFFER_CROSS_SELF
-  - The account has opposite offer of equal or lesser price active, so the account creating this offer would immediately cross itself.
-- op_sell_no_issuer
-  - MANAGE_BUY_OFFER_SELL_NO_ISSUER
-  - The issuer of selling asset does not exist.
-- buy_no_issuer
-  - MANAGE_BUY_OFFER_BUY_NO_ISSUER
-  - The issuer of buying asset does not exist.
-- op_offer_not_found
-  - MANAGE_BUY_OFFER_NOT_FOUND
-  - An offer with that offerID cannot be found.
-- OpLowReserve
-  - MANAGE_BUY_OFFER_LOW_RESERVE
-  - The account creating this offer does not have enough XLM to satisfy the minimum XLM reserve increase caused by adding a subentry and still satisfy its XLM selling liabilities. For every offer an account creates, the minimum amount of XLM that account must hold will increase.
-
-</AttributeTable>
+Learn more about the [`Manage Buy Offer` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations#manage-buy-offer).
+
+<ResponseField name="OpSuccess" type="MANAGE_BUY_OFFER_SUCCESS">
+
+The offer was successfully placed.
+
+</ResponseField>
+
+<ResponseField name="OpMalformed" type="MANAGE_BUY_OFFER_MALFORMED">
+
+The input is incorrect and would result in an invalid offer.
+
+</ResponseField>
+
+<ResponseField name="op_sell_no_trust" type="MANAGE_BUY_OFFER_SELL_NO_TRUST">
+
+The account creating the offer does not have a trustline for the asset it is selling.
+
+</ResponseField>
+
+<ResponseField name="op_buy_no_trust" type="MANAGE_BUY_OFFER_BUY_NO_TRUST">
+
+The account creating the offer does not have a trustline for the asset it is buying.
+
+</ResponseField>
+
+<ResponseField name="sell_not_authorized" type="MANAGE_BUY_OFFER_SELL_NOT_AUTHORIZED">
+
+The account creating the offer is not authorized to sell this asset.
+
+</ResponseField>
+
+<ResponseField name="buy_not_authorized" type="MANAGE_BUY_OFFER_BUY_NOT_AUTHORIZED">
+
+The account creating the offer is not authorized to buy this asset.
+
+</ResponseField>
+
+<ResponseField name="OpLineFull" type="MANAGE_BUY_OFFER_LINE_FULL">
+
+The account creating the offer does not have sufficient limits to receive buying and still satisfy its buying liabilities.
+
+</ResponseField>
+
+<ResponseField name="OpUnderfunded" type="MANAGE_BUY_OFFER_UNDERFUNDED">
+
+The account creating the offer does not have sufficient limits to send selling and still satisfy its selling liabilities. Note that if selling XLM then the account must additionally maintain its minimum XLM reserve, which is calculated assuming this offer will not completely execute immediately.
+
+</ResponseField>
+
+<ResponseField name="op_cross_self" type="MANAGE_BUY_OFFER_CROSS_SELF">
+
+The account has opposite offer of equal or lesser price active, so the account creating this offer would immediately cross itself.
+
+</ResponseField>
+
+<ResponseField name="op_sell_no_issuer" type="MANAGE_BUY_OFFER_SELL_NO_ISSUER">
+
+The issuer of selling asset does not exist.
+
+</ResponseField>
+
+<ResponseField name="buy_no_issuer" type="MANAGE_BUY_OFFER_BUY_NO_ISSUER">
+
+The issuer of buying asset does not exist.
+
+</ResponseField>
+
+<ResponseField name="op_offer_not_found" type="MANAGE_BUY_OFFER_NOT_FOUND">
+
+An offer with that offerID cannot be found.
+
+</ResponseField>
+
+<ResponseField name="OpLowReserve" type="MANAGE_BUY_OFFER_LOW_RESERVE">
+
+The account creating this offer does not have enough XLM to satisfy the minimum XLM reserve increase caused by adding a subentry and still satisfy its XLM selling liabilities. For every offer an account creates, the minimum amount of XLM that account must hold will increase.
+
+</ResponseField>
diff --git a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-data.mdx b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-data.mdx
index 236c7a2fe..bb556bb98 100644
--- a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-data.mdx
+++ b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-data.mdx
@@ -1,28 +1,38 @@
 ---
 title: Manage Data Result Codes
-sidebar_position: 120
+description: "These are result codes that communicate success (200) or failure (400) specific to the Manage Data operation."
 ---
 
 These are result codes that communicate success (200) or failure (400) specific to the `Manage Data` operation.
 
-Learn more about the [`Manage Data` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#manage-data).
-
-<AttributeTable>
-
-- OpSuccess
-  - MANAGE_DATA_SUCCESS
-  - Manage data operation has executed successfully.
-- op_not_supported_yet
-  - MANAGE_DATA_NOT_SUPPORTED_YET
-  - The network hasn’t moved to this protocol change yet. This failure means the network doesn’t support this feature yet.
-- op_data_name_not_found
-  - MANAGE_DATA_NAME_NOT_FOUND
-  - Trying to remove a Data Entry that isn’t there. This will happen if Name is set (and Value isn’t) but the Account doesn’t have a DataEntry with that Name.
-- op_low_reserve
-  - MANAGE_DATA_LOW_RESERVE
-  - This account does not have enough XLM to satisfy the minimum XLM reserve increase caused by adding a subentry and still satisfy its XLM selling liabilities. For every new DataEntry added to an account, the minimum reserve of XLM that account must hold increases.
-- op_data_invalid_name
-  - MANAGE_DATA_INVALID_NAME
-  - Name not a valid string.
-
-</AttributeTable>
+Learn more about the [`Manage Data` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations#manage-data).
+
+<ResponseField name="OpSuccess" type="MANAGE_DATA_SUCCESS">
+
+Manage data operation has executed successfully.
+
+</ResponseField>
+
+<ResponseField name="op_not_supported_yet" type="MANAGE_DATA_NOT_SUPPORTED_YET">
+
+The network hasn’t moved to this protocol change yet. This failure means the network doesn’t support this feature yet.
+
+</ResponseField>
+
+<ResponseField name="op_data_name_not_found" type="MANAGE_DATA_NAME_NOT_FOUND">
+
+Trying to remove a Data Entry that isn’t there. This will happen if Name is set (and Value isn’t) but the Account doesn’t have a DataEntry with that Name.
+
+</ResponseField>
+
+<ResponseField name="op_low_reserve" type="MANAGE_DATA_LOW_RESERVE">
+
+This account does not have enough XLM to satisfy the minimum XLM reserve increase caused by adding a subentry and still satisfy its XLM selling liabilities. For every new DataEntry added to an account, the minimum reserve of XLM that account must hold increases.
+
+</ResponseField>
+
+<ResponseField name="op_data_invalid_name" type="MANAGE_DATA_INVALID_NAME">
+
+Name not a valid string.
+
+</ResponseField>
diff --git a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-sell-offer.mdx b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-sell-offer.mdx
index 9128331d5..6042ae658 100644
--- a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-sell-offer.mdx
+++ b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-sell-offer.mdx
@@ -1,52 +1,86 @@
 ---
 title: Manage Sell Offer Result Codes
-sidebar_position: 50
+description: "These are result codes that communicate success (200) or failure (400) specific to the Manage Sell Offer operation."
 ---
 
 These are result codes that communicate success (200) or failure (400) specific to the `Manage Sell Offer` operation.
 
-Learn more about the [`Manage Sell Offer` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#manage-sell-offer).
-
-<AttributeTable>
-
-- OpSuccess
-  - MANAGE_SELL_OFFER_SUCCESS
-  - The offer was successfully placed.
-- OpMalformed
-  - MANAGE_SELL_OFFER_MALFORMED
-  - The input is incorrect and would result in an invalid offer.
-- op_sell_no_trust
-  - MANAGE_SELL_OFFER_SELL_NO_TRUST
-  - The account creating the offer does not have a trustline for the asset it is selling.
-- op_buy_no_trust
-  - MANAGE_SELL_OFFER_BUY_NO_TRUST
-  - The account creating the offer does not have a trustline for the asset it is buying.
-- sell_not_authorized
-  - MANAGE_SELL_OFFER_SELL_NOT_AUTHORIZED
-  - The account creating the offer is not authorized to sell this asset.
-- buy_not_authorized
-  - MANAGE_SELL_OFFER_BUY_NOT_AUTHORIZED
-  - The account creating the offer is not authorized to buy this asset.
-- OpLineFull
-  - MANAGE_SELL_OFFER_LINE_FULL
-  - The account creating the offer does not have sufficient limits to receive buying and still satisfy its buying liabilities.
-- OpUnderfunded
-  - MANAGE_SELL_OFFER_UNDERFUNDED
-  - The account creating the offer does not have sufficient limits to send selling and still satisfy its selling liabilities. Note that if selling XLM then the account must additionally maintain its minimum XLM reserve, which is calculated assuming this offer will not completely execute immediately.
-- op_cross_self
-  - MANAGE_SELL_OFFER_CROSS_SELF
-  - The account has opposite offer of equal or lesser price active, so the account creating this offer would immediately cross itself.
-- op_sell_no_issuer
-  - MANAGE_SELL_OFFER_SELL_NO_ISSUER
-  - The issuer of selling asset does not exist.
-- buy_no_issuer
-  - MANAGE_SELL_OFFER_BUY_NO_ISSUER
-  - The issuer of buying asset does not exist.
-- op_offer_not_found
-  - MANAGE_SELL_OFFER_NOT_FOUND
-  - An offer with that offerID cannot be found.
-- OpLowReserve
-  - MANAGE_SELL_OFFER_LOW_RESERVE
-  - The account creating this offer does not have enough XLM to satisfy the minimum XLM reserve increase caused by adding a subentry and still satisfy its XLM selling liabilities. For every offer an account creates, the minimum amount of XLM that account must hold will increase.
-
-</AttributeTable>
+Learn more about the [`Manage Sell Offer` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations#manage-sell-offer).
+
+<ResponseField name="OpSuccess" type="MANAGE_SELL_OFFER_SUCCESS">
+
+The offer was successfully placed.
+
+</ResponseField>
+
+<ResponseField name="OpMalformed" type="MANAGE_SELL_OFFER_MALFORMED">
+
+The input is incorrect and would result in an invalid offer.
+
+</ResponseField>
+
+<ResponseField name="op_sell_no_trust" type="MANAGE_SELL_OFFER_SELL_NO_TRUST">
+
+The account creating the offer does not have a trustline for the asset it is selling.
+
+</ResponseField>
+
+<ResponseField name="op_buy_no_trust" type="MANAGE_SELL_OFFER_BUY_NO_TRUST">
+
+The account creating the offer does not have a trustline for the asset it is buying.
+
+</ResponseField>
+
+<ResponseField name="sell_not_authorized" type="MANAGE_SELL_OFFER_SELL_NOT_AUTHORIZED">
+
+The account creating the offer is not authorized to sell this asset.
+
+</ResponseField>
+
+<ResponseField name="buy_not_authorized" type="MANAGE_SELL_OFFER_BUY_NOT_AUTHORIZED">
+
+The account creating the offer is not authorized to buy this asset.
+
+</ResponseField>
+
+<ResponseField name="OpLineFull" type="MANAGE_SELL_OFFER_LINE_FULL">
+
+The account creating the offer does not have sufficient limits to receive buying and still satisfy its buying liabilities.
+
+</ResponseField>
+
+<ResponseField name="OpUnderfunded" type="MANAGE_SELL_OFFER_UNDERFUNDED">
+
+The account creating the offer does not have sufficient limits to send selling and still satisfy its selling liabilities. Note that if selling XLM then the account must additionally maintain its minimum XLM reserve, which is calculated assuming this offer will not completely execute immediately.
+
+</ResponseField>
+
+<ResponseField name="op_cross_self" type="MANAGE_SELL_OFFER_CROSS_SELF">
+
+The account has opposite offer of equal or lesser price active, so the account creating this offer would immediately cross itself.
+
+</ResponseField>
+
+<ResponseField name="op_sell_no_issuer" type="MANAGE_SELL_OFFER_SELL_NO_ISSUER">
+
+The issuer of selling asset does not exist.
+
+</ResponseField>
+
+<ResponseField name="buy_no_issuer" type="MANAGE_SELL_OFFER_BUY_NO_ISSUER">
+
+The issuer of buying asset does not exist.
+
+</ResponseField>
+
+<ResponseField name="op_offer_not_found" type="MANAGE_SELL_OFFER_NOT_FOUND">
+
+An offer with that offerID cannot be found.
+
+</ResponseField>
+
+<ResponseField name="OpLowReserve" type="MANAGE_SELL_OFFER_LOW_RESERVE">
+
+The account creating this offer does not have enough XLM to satisfy the minimum XLM reserve increase caused by adding a subentry and still satisfy its XLM selling liabilities. For every offer an account creates, the minimum amount of XLM that account must hold will increase.
+
+</ResponseField>
diff --git a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-receive.mdx b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-receive.mdx
index 70ef3b519..ed4e25c7c 100644
--- a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-receive.mdx
+++ b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-receive.mdx
@@ -1,55 +1,86 @@
 ---
 title: Path Payment Strict Receive Result Codes
-sidebar_position: 30
+description: "These are result codes that communicate success (200) or failure (400) specific to the Path Payment Strict Receive operation."
 ---
 
 These are result codes that communicate success (200) or failure (400) specific to the `Path Payment Strict Receive` operation.
 
-Learn more about the [`Path Payment Strict Receive` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#path-payment-strict-receive).
-
-<AttributeTable>
-
-- RESULT CODE
-  - STELLAR PROTOCOL CODE
-  - DESCRIPTION
-- OpSuccess
-  - PATH_PAYMENT_STRICT_RECEIVE_SUCCESS
-  - The payment was successfully completed.
-- OpMalformed
-  - PATH_PAYMENT_STRICT_RECEIVE_MALFORMED
-  - The input for this path payment is invalid.
-- OpUnderfunded
-  - PATH_PAYMENT_STRICT_RECEIVE_UNDERFUNDED
-  - The source account (sender) does not have enough lumens to send the payment amount while maintaining its own minimum reserve.
-- OpSrcNoTrust
-  - PATH_PAYMENT_STRICT_RECEIVE_SRC_NO_TRUST
-  - The source account is missing the appropriate trustline.
-- OpSrcNotAuthorized
-  - PATH_PAYMENT_STRICT_RECEIVE_SRC_NOT_AUTHORIZED
-  - The source account is not authorized to send this asset.
-- OpNoDestination
-  - PATH_PAYMENT_STRICT_RECEIVE_NO_DESTINATION
-  - The destination account does not exist.
-- OpNoTrust
-  - PATH_PAYMENT_STRICT_RECEIVE_NO_TRUST
-  - The destination account does not have a trustline for the asset being sent.
-- OpNotAuthorized
-  - PATH_PAYMENT_STRICT_RECEIVE_NOT_AUTHORIZED
-  - The destination account is not authorized to hold this asset.
-- OpLineFull
-  - PATH_PAYMENT_STRICT_RECEIVE_LINE_FULL
-  - The destination account (receiver) does not have sufficient limits to receive amount and still satisfy its buying liabilities.
-- OpNoIssuer
-  - PATH_PAYMENT_STRICT_RECEIVE_NO_ISSUER
-  - The issuer of one of the assets is missing.
-- OpTooFewOffers
-  - PATH_PAYMENT_STRICT_RECEIVE_TOO_FEW_OFFERS
-  - There is no path of offers connecting the send asset and destination asset. Stellar only considers paths of length 5 or shorter.
-- OpCrossSelf
-  - PATH_PAYMENT_STRICT_RECEIVE_OFFER_CROSS_SELF
-  - This path payment would cross one of its own offers.
-- OpOverSourceMax
-  - PATH_PAYMENT_STRICT_RECEIVE_OVER_SENDMAX
-  - The paths that could send destination amount of destination asset would exceed send max.
-
-</AttributeTable>
+Learn more about the [`Path Payment Strict Receive` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations#path-payment-strict-receive).
+
+<ResponseField name="OpSuccess" type="PATH_PAYMENT_STRICT_RECEIVE_SUCCESS">
+
+The payment was successfully completed.
+
+</ResponseField>
+
+<ResponseField name="OpMalformed" type="PATH_PAYMENT_STRICT_RECEIVE_MALFORMED">
+
+The input for this path payment is invalid.
+
+</ResponseField>
+
+<ResponseField name="OpUnderfunded" type="PATH_PAYMENT_STRICT_RECEIVE_UNDERFUNDED">
+
+The source account (sender) does not have enough lumens to send the payment amount while maintaining its own minimum reserve.
+
+</ResponseField>
+
+<ResponseField name="OpSrcNoTrust" type="PATH_PAYMENT_STRICT_RECEIVE_SRC_NO_TRUST">
+
+The source account is missing the appropriate trustline.
+
+</ResponseField>
+
+<ResponseField name="OpSrcNotAuthorized" type="PATH_PAYMENT_STRICT_RECEIVE_SRC_NOT_AUTHORIZED">
+
+The source account is not authorized to send this asset.
+
+</ResponseField>
+
+<ResponseField name="OpNoDestination" type="PATH_PAYMENT_STRICT_RECEIVE_NO_DESTINATION">
+
+The destination account does not exist.
+
+</ResponseField>
+
+<ResponseField name="OpNoTrust" type="PATH_PAYMENT_STRICT_RECEIVE_NO_TRUST">
+
+The destination account does not have a trustline for the asset being sent.
+
+</ResponseField>
+
+<ResponseField name="OpNotAuthorized" type="PATH_PAYMENT_STRICT_RECEIVE_NOT_AUTHORIZED">
+
+The destination account is not authorized to hold this asset.
+
+</ResponseField>
+
+<ResponseField name="OpLineFull" type="PATH_PAYMENT_STRICT_RECEIVE_LINE_FULL">
+
+The destination account (receiver) does not have sufficient limits to receive amount and still satisfy its buying liabilities.
+
+</ResponseField>
+
+<ResponseField name="OpNoIssuer" type="PATH_PAYMENT_STRICT_RECEIVE_NO_ISSUER">
+
+The issuer of one of the assets is missing.
+
+</ResponseField>
+
+<ResponseField name="OpTooFewOffers" type="PATH_PAYMENT_STRICT_RECEIVE_TOO_FEW_OFFERS">
+
+There is no path of offers connecting the send asset and destination asset. Stellar only considers paths of length 5 or shorter.
+
+</ResponseField>
+
+<ResponseField name="OpCrossSelf" type="PATH_PAYMENT_STRICT_RECEIVE_OFFER_CROSS_SELF">
+
+This path payment would cross one of its own offers.
+
+</ResponseField>
+
+<ResponseField name="OpOverSourceMax" type="PATH_PAYMENT_STRICT_RECEIVE_OVER_SENDMAX">
+
+The paths that could send destination amount of destination asset would exceed send max.
+
+</ResponseField>
diff --git a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-send.mdx b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-send.mdx
index a3fef6bf7..0adbe29a1 100644
--- a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-send.mdx
+++ b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-send.mdx
@@ -1,55 +1,86 @@
 ---
 title: Path Payment Strict Send Result Codes
-sidebar_position: 40
+description: "These are result codes that communicate success (200) or failure (400) specific to the Path Payment Strict Send operation."
 ---
 
 These are result codes that communicate success (200) or failure (400) specific to the `Path Payment Strict Send` operation.
 
-Learn more about the [`Path Payment Strict Send` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#path-payment-strict-send).
-
-<AttributeTable>
-
-- RESULT CODE
-  - STELLAR PROTOCOL CODE
-  - DESCRIPTION
-- OpSuccess
-  - PATH_PAYMENT_STRICT_SEND_SUCCESS
-  - The payment was successfully completed.
-- OpMalformed
-  - PATH_PAYMENT_STRICT_SEND_MALFORMED
-  - The input for this path payment is invalid.
-- OpUnderfunded
-  - PATH_PAYMENT_STRICT_SEND_UNDERFUNDED
-  - The source account (sender) does not have enough lumens to send the payment amount while maintaining its own minimum reserve.
-- OpSrcNoTrust
-  - PATH_PAYMENT_STRICT_SEND_SRC_NO_TRUST
-  - The source account is missing the appropriate trustline.
-- OpSrcNotAuthorized
-  - PATH_PAYMENT_STRICT_SEND_SRC_NOT_AUTHORIZED
-  - The source account is not authorized to send this asset.
-- OpNoDestination
-  - PATH_PAYMENT_STRICT_SEND_NO_DESTINATION
-  - The destination account does not exist.
-- OpNoTrust
-  - PATH_PAYMENT_STRICT_SEND_NO_TRUST
-  - The destination account does not have a trustline for the asset being sent.
-- OpNotAuthorized
-  - PATH_PAYMENT_STRICT_SEND_NOT_AUTHORIZED
-  - The destination account is not authorized to hold this asset.
-- OpLineFull
-  - PATH_PAYMENT_STRICT_SEND_LINE_FULL
-  - The destination account (receiver) does not have sufficient limits to receive amount and still satisfy its buying liabilities.
-- OpNoIssuer
-  - PATH_PAYMENT_STRICT_SEND_NO_ISSUER
-  - The issuer of one of the assets is missing.
-- OpTooFewOffers
-  - PATH_PAYMENT_STRICT_SEND_TOO_FEW_OFFERS
-  - There is no path of offers connecting the send asset and destination asset. Stellar only considers paths of length 5 or shorter.
-- OpCrossSelf
-  - PATH_PAYMENT_STRICT_SEND_OFFER_CROSS_SELF
-  - This path payment would cross one of its own offers.
-- OpUnderDestMin
-  - PATH_PAYMENT_STRICT_SEND_UNDER_DESTMIN
-  - The paths that could send destination amount of destination asset would fall short of destination min.
-
-</AttributeTable>
+Learn more about the [`Path Payment Strict Send` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations#path-payment-strict-send).
+
+<ResponseField name="OpSuccess" type="PATH_PAYMENT_STRICT_SEND_SUCCESS">
+
+The payment was successfully completed.
+
+</ResponseField>
+
+<ResponseField name="OpMalformed" type="PATH_PAYMENT_STRICT_SEND_MALFORMED">
+
+The input for this path payment is invalid.
+
+</ResponseField>
+
+<ResponseField name="OpUnderfunded" type="PATH_PAYMENT_STRICT_SEND_UNDERFUNDED">
+
+The source account (sender) does not have enough lumens to send the payment amount while maintaining its own minimum reserve.
+
+</ResponseField>
+
+<ResponseField name="OpSrcNoTrust" type="PATH_PAYMENT_STRICT_SEND_SRC_NO_TRUST">
+
+The source account is missing the appropriate trustline.
+
+</ResponseField>
+
+<ResponseField name="OpSrcNotAuthorized" type="PATH_PAYMENT_STRICT_SEND_SRC_NOT_AUTHORIZED">
+
+The source account is not authorized to send this asset.
+
+</ResponseField>
+
+<ResponseField name="OpNoDestination" type="PATH_PAYMENT_STRICT_SEND_NO_DESTINATION">
+
+The destination account does not exist.
+
+</ResponseField>
+
+<ResponseField name="OpNoTrust" type="PATH_PAYMENT_STRICT_SEND_NO_TRUST">
+
+The destination account does not have a trustline for the asset being sent.
+
+</ResponseField>
+
+<ResponseField name="OpNotAuthorized" type="PATH_PAYMENT_STRICT_SEND_NOT_AUTHORIZED">
+
+The destination account is not authorized to hold this asset.
+
+</ResponseField>
+
+<ResponseField name="OpLineFull" type="PATH_PAYMENT_STRICT_SEND_LINE_FULL">
+
+The destination account (receiver) does not have sufficient limits to receive amount and still satisfy its buying liabilities.
+
+</ResponseField>
+
+<ResponseField name="OpNoIssuer" type="PATH_PAYMENT_STRICT_SEND_NO_ISSUER">
+
+The issuer of one of the assets is missing.
+
+</ResponseField>
+
+<ResponseField name="OpTooFewOffers" type="PATH_PAYMENT_STRICT_SEND_TOO_FEW_OFFERS">
+
+There is no path of offers connecting the send asset and destination asset. Stellar only considers paths of length 5 or shorter.
+
+</ResponseField>
+
+<ResponseField name="OpCrossSelf" type="PATH_PAYMENT_STRICT_SEND_OFFER_CROSS_SELF">
+
+This path payment would cross one of its own offers.
+
+</ResponseField>
+
+<ResponseField name="OpUnderDestMin" type="PATH_PAYMENT_STRICT_SEND_UNDER_DESTMIN">
+
+The paths that could send destination amount of destination asset would fall short of destination min.
+
+</ResponseField>
diff --git a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/payment.mdx b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/payment.mdx
index 0096dd8de..9dab95e08 100644
--- a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/payment.mdx
+++ b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/payment.mdx
@@ -1,46 +1,68 @@
 ---
 title: Payment Result Codes
-sidebar_position: 20
+description: "These are result codes that communicate success (200) or failure (400) specific to the Payment operation, which often fails because the receiving account..."
 ---
 
 These are result codes that communicate success (200) or failure (400) specific to the `Payment` operation, which often fails because the receiving account does not trust the issuer of the asset being sent.
 
-Learn more about the [`Payment` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#payment).
-
-<AttributeTable>
-
-- RESULT CODE
-  - STELLAR PROTOCOL CODE
-  - DESCRIPTION
-- OpSuccess
-  - PAYMENT_SUCCESS
-  - The payment was successfully completed.
-- OpMalformed
-  - PAYMENT_MALFORMED
-  - The input to the payment is invalid.
-- OpUnderfunded
-  - PAYMENT_UNDERFUNDED
-  - The source account (sender) does not have enough lumens to send the payment amount while maintaining its own minimum reserve.
-- OpSrcNoTrust
-  - PAYMENT_SRC_NO_TRUST
-  - The source account does not have a trustline for the asset it is tring to send.
-- OpSrcNotAuthorized
-  - PAYMENT_SRC_NOT_AUTHORIZED
-  - The source account is not authorized to send this asset.
-- OpNoDestination
-  - PAYMENT_NO_DESTINATION
-  - The destination account does not exist.
-- OpNoTrust
-  - PAYMENT_NO_TRUST
-  - The destination account does not have a trustline for the asset being sent.
-- OpNotAuthorized
-  - PAYMENT_NOT_AUTHORIZED
-  - The destination account is not authorized to hold this asset.
-- OpLineFull
-  - PAYMENT_LINE_FULL
-  - The destination account (receiver) does not have sufficient limits to receive amount and still satisfy its buying liabilities.
-- OpNoIssuer
-  - PAYMENT_NO_ISSUER
-  - The issuer of the asset does not exist.
-
-</AttributeTable>
+Learn more about the [`Payment` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations#payment).
+
+<ResponseField name="OpSuccess" type="PAYMENT_SUCCESS">
+
+The payment was successfully completed.
+
+</ResponseField>
+
+<ResponseField name="OpMalformed" type="PAYMENT_MALFORMED">
+
+The input to the payment is invalid.
+
+</ResponseField>
+
+<ResponseField name="OpUnderfunded" type="PAYMENT_UNDERFUNDED">
+
+The source account (sender) does not have enough lumens to send the payment amount while maintaining its own minimum reserve.
+
+</ResponseField>
+
+<ResponseField name="OpSrcNoTrust" type="PAYMENT_SRC_NO_TRUST">
+
+The source account does not have a trustline for the asset it is tring to send.
+
+</ResponseField>
+
+<ResponseField name="OpSrcNotAuthorized" type="PAYMENT_SRC_NOT_AUTHORIZED">
+
+The source account is not authorized to send this asset.
+
+</ResponseField>
+
+<ResponseField name="OpNoDestination" type="PAYMENT_NO_DESTINATION">
+
+The destination account does not exist.
+
+</ResponseField>
+
+<ResponseField name="OpNoTrust" type="PAYMENT_NO_TRUST">
+
+The destination account does not have a trustline for the asset being sent.
+
+</ResponseField>
+
+<ResponseField name="OpNotAuthorized" type="PAYMENT_NOT_AUTHORIZED">
+
+The destination account is not authorized to hold this asset.
+
+</ResponseField>
+
+<ResponseField name="OpLineFull" type="PAYMENT_LINE_FULL">
+
+The destination account (receiver) does not have sufficient limits to receive amount and still satisfy its buying liabilities.
+
+</ResponseField>
+
+<ResponseField name="OpNoIssuer" type="PAYMENT_NO_ISSUER">
+
+The issuer of the asset does not exist.
+
+</ResponseField>
diff --git a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/set-options.mdx b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/set-options.mdx
index d2a5e3c74..5b1018386 100644
--- a/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/set-options.mdx
+++ b/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/set-options.mdx
@@ -1,43 +1,68 @@
 ---
 title: Set Options Result Codes
-sidebar_position: 80
+description: "These are result codes that communicate success (200) or failure (400) specific to the Set Options operation."
 ---
 
 These are result codes that communicate success (200) or failure (400) specific to the `Set Options` operation.
 
-Learn more about the [`Set Options` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#set-options).
-
-<AttributeTable>
-
-- OpSuccess
-  - SET_OPTIONS_SUCCESS
-  - Options successfully set.
-- OpLowReserve
-  - SET_OPTIONS_LOW_RESERVE
-  - This account does not have enough XLM to satisfy the minimum XLM reserve increase caused by adding a subentry and still satisfy its XLM selling liabilities. For every new signer added to an account, the minimum reserve of XLM that account must hold increases.
-- op_too_many_signers
-  - SET_OPTIONS_TOO_MANY_SIGNERS
-  - 20 is the maximum number of signers an account can have, and adding another signer would exceed that.
-- op_bad_flags
-  - SET_OPTIONS_BAD_FLAGS
-  - The flags set and/or cleared are invalid by themselves or in combination.
-- op_invalid_inflation
-  - SET_OPTIONS_INVALID_INFLATION
-  - The destination account set in the inflation field does not exist.
-- op_cant_change
-  - SET_OPTIONS_CANT_CHANGE
-  - This account can no longer change the option it wants to change.
-- op_unknown_flag
-  - SET_OPTIONS_UNKNOWN_FLAG
-  - The account is trying to set a flag that is unknown.
-- op_threshold_out_of_range
-  - SET_OPTIONS_THRESHOLD_OUT_OF_RANGE
-  - The value for a key weight or threshold is invalid.
-- op_bad_signer
-  - SET_OPTIONS_BAD_SIGNER
-  - Any additional signers added to the account cannot be the master key.
-- op_invalid_home_domain
-  - SET_OPTIONS_INVALID_HOME_DOMAIN
-  - Home domain is malformed.
-
-</AttributeTable>
+Learn more about the [`Set Options` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations#set-options).
+
+<ResponseField name="OpSuccess" type="SET_OPTIONS_SUCCESS">
+
+Options successfully set.
+
+</ResponseField>
+
+<ResponseField name="OpLowReserve" type="SET_OPTIONS_LOW_RESERVE">
+
+This account does not have enough XLM to satisfy the minimum XLM reserve increase caused by adding a subentry and still satisfy its XLM selling liabilities. For every new signer added to an account, the minimum reserve of XLM that account must hold increases.
+
+</ResponseField>
+
+<ResponseField name="op_too_many_signers" type="SET_OPTIONS_TOO_MANY_SIGNERS">
+
+20 is the maximum number of signers an account can have, and adding another signer would exceed that.
+
+</ResponseField>
+
+<ResponseField name="op_bad_flags" type="SET_OPTIONS_BAD_FLAGS">
+
+The flags set and/or cleared are invalid by themselves or in combination.
+
+</ResponseField>
+
+<ResponseField name="op_invalid_inflation" type="SET_OPTIONS_INVALID_INFLATION">
+
+The destination account set in the inflation field does not exist.
+
+</ResponseField>
+
+<ResponseField name="op_cant_change" type="SET_OPTIONS_CANT_CHANGE">
+
+This account can no longer change the option it wants to change.
+
+</ResponseField>
+
+<ResponseField name="op_unknown_flag" type="SET_OPTIONS_UNKNOWN_FLAG">
+
+The account is trying to set a flag that is unknown.
+
+</ResponseField>
+
+<ResponseField name="op_threshold_out_of_range" type="SET_OPTIONS_THRESHOLD_OUT_OF_RANGE">
+
+The value for a key weight or threshold is invalid.
+
+</ResponseField>
+
+<ResponseField name="op_bad_signer" type="SET_OPTIONS_BAD_SIGNER">
+
+Any additional signers added to the account cannot be the master key.
+
+</ResponseField>
+
+<ResponseField name="op_invalid_home_domain" type="SET_OPTIONS_INVALID_HOME_DOMAIN">
+
+Home domain is malformed.
+
+</ResponseField>
diff --git a/docs/data/apis/horizon/api-reference/errors/result-codes/operations.mdx b/docs/data/apis/horizon/api-reference/errors/result-codes/operations.mdx
index 2c94bddf2..f5f6cbac8 100644
--- a/docs/data/apis/horizon/api-reference/errors/result-codes/operations.mdx
+++ b/docs/data/apis/horizon/api-reference/errors/result-codes/operations.mdx
@@ -1,39 +1,49 @@
 ---
 title: Operation Result Codes
-sidebar_position: 20
+description: "These are Result Codes that communicate success (200) or failure (400) at the operation level: no source account, too many subentries, etc."
 ---
 
 These are Result Codes that communicate success (200) or failure (400) at the operation level: no source account, too many subentries, etc.
 
-<AttributeTable>
-
-- RESULT CODE
-  - STELLAR PROTOCOL CODE
-  - DESCRIPTION
-- op_inner
-  - opINNER
-  - The inner object result is valid and the operation was a success.
-- op_bad_auth
-  - opBAD_AUTH
-  - There are too few valid signatures, or the transaction was submitted to the wrong network.
-- op_no_source_account
-  - opNO_ACCOUNT
-  - The source account was not found.
-- op_not_supported
-  - opNOT_SUPPORTED
-  - The operation is not supported at this time.
-- op_too_many_subentries
-  - opTOO_MANY_SUBENTRIES
-  - Max number of subentries (1000) already reached
-- op_exceeded_work_limit
-  - opEXCEEDED_WORK_LIMIT
-  - Operation did too much work
-
-</AttributeTable>
-
-<ExampleResponse title="Example Response for an 'op_no_source_account' Result Code">
-
-```json
+Each entry shows the Horizon result code, then the Stellar protocol code.
+
+<ResponseField name="op_inner" type="opINNER">
+
+The inner object result is valid and the operation was a success.
+
+</ResponseField>
+
+<ResponseField name="op_bad_auth" type="opBAD_AUTH">
+
+There are too few valid signatures, or the transaction was submitted to the wrong network.
+
+</ResponseField>
+
+<ResponseField name="op_no_source_account" type="opNO_ACCOUNT">
+
+The source account was not found.
+
+</ResponseField>
+
+<ResponseField name="op_not_supported" type="opNOT_SUPPORTED">
+
+The operation is not supported at this time.
+
+</ResponseField>
+
+<ResponseField name="op_too_many_subentries" type="opTOO_MANY_SUBENTRIES">
+
+Max number of subentries (1000) already reached
+
+</ResponseField>
+
+<ResponseField name="op_exceeded_work_limit" type="opEXCEEDED_WORK_LIMIT">
+
+Operation did too much work
+
+</ResponseField>
+
+```json Example Response for an 'op_no_source_account' Result Code
 {
   "type": "https://stellar.org/horizon-errors/transaction_failed",
   "title": "Transaction Failed",
@@ -49,5 +59,3 @@ These are Result Codes that communicate success (200) or failure (400) at the op
   }
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/errors/result-codes/transactions.mdx b/docs/data/apis/horizon/api-reference/errors/result-codes/transactions.mdx
index 1412581e5..1ec67145f 100644
--- a/docs/data/apis/horizon/api-reference/errors/result-codes/transactions.mdx
+++ b/docs/data/apis/horizon/api-reference/errors/result-codes/transactions.mdx
@@ -1,57 +1,85 @@
 ---
 title: Transaction Result Codes
-sidebar_position: 10
+description: "These are Result Codes that communicate success (200) or failure (400) at the transaction level: bad sequence numbers, insufficient balances, insufficient..."
 ---
 
 These are Result Codes that communicate success (200) or failure (400) at the transaction level: bad sequence numbers, insufficient balances, insufficient fees, etc.
 
-<AttributeTable>
-
-- RESULT CODE
-  - STELLAR PROTOCOL CODE
-  - DESCRIPTION
-- tx_success
-  - txSUCCESS
-  - The transaction succeeded.
-- tx_failed
-  - txFAILED
-  - One of the operations failed (none were applied).
-- tx_too_early
-  - txTOO_EARLY
-  - The ledger closeTime was before the minTime.
-- tx_too_late
-  - txTOO_LATE
-  - The ledger closeTime was after the maxTime.
-- tx_missing_operation
-  - txMISSING_OPERATION
-  - No operation was specified
-- tx_bad_seq
-  - txBAD_SEQ
-  - sequence number does not match source account
-- tx_bad_auth
-  - txBAD_AUTH
-  - too few valid signatures / wrong network
-- tx_insufficient_balance
-  - txINSUFFICIENT_BALANCE
-  - fee would bring account below reserve
-- tx_no_source_account
-  - txNO_ACCOUNT
-  - source account not found
-- tx_insufficient_fee
-  - txINSUFFICIENT_FEE
-  - fee is too small
-- tx_bad_auth_extra
-  - txBAD_AUTH_EXTRA
-  - unused signatures attached to transaction
-- tx_internal_error
-  - txINTERNAL_ERROR
-  - an unknown error occurred
-
-</AttributeTable>
-
-<ExampleResponse title="Example Response for a 'tx_bad_seq' Result Code">
-
-```json
+Each entry shows the Horizon result code, then the Stellar protocol code.
+
+<ResponseField name="tx_success" type="txSUCCESS">
+
+The transaction succeeded.
+
+</ResponseField>
+
+<ResponseField name="tx_failed" type="txFAILED">
+
+One of the operations failed (none were applied).
+
+</ResponseField>
+
+<ResponseField name="tx_too_early" type="txTOO_EARLY">
+
+The ledger closeTime was before the minTime.
+
+</ResponseField>
+
+<ResponseField name="tx_too_late" type="txTOO_LATE">
+
+The ledger closeTime was after the maxTime.
+
+</ResponseField>
+
+<ResponseField name="tx_missing_operation" type="txMISSING_OPERATION">
+
+No operation was specified
+
+</ResponseField>
+
+<ResponseField name="tx_bad_seq" type="txBAD_SEQ">
+
+sequence number does not match source account
+
+</ResponseField>
+
+<ResponseField name="tx_bad_auth" type="txBAD_AUTH">
+
+too few valid signatures / wrong network
+
+</ResponseField>
+
+<ResponseField name="tx_insufficient_balance" type="txINSUFFICIENT_BALANCE">
+
+fee would bring account below reserve
+
+</ResponseField>
+
+<ResponseField name="tx_no_source_account" type="txNO_ACCOUNT">
+
+source account not found
+
+</ResponseField>
+
+<ResponseField name="tx_insufficient_fee" type="txINSUFFICIENT_FEE">
+
+fee is too small
+
+</ResponseField>
+
+<ResponseField name="tx_bad_auth_extra" type="txBAD_AUTH_EXTRA">
+
+unused signatures attached to transaction
+
+</ResponseField>
+
+<ResponseField name="tx_internal_error" type="txINTERNAL_ERROR">
+
+an unknown error occurred
+
+</ResponseField>
+
+```json Example Response for a 'tx_bad_seq' Result Code
 {
   "type": "https://stellar.org/horizon-errors/transaction_failed",
   "title": "Transaction Failed",
@@ -66,5 +94,3 @@ These are Result Codes that communicate success (200) or failure (400) at the tr
   }
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/get-all-offers.ParamsDetails.json b/docs/data/apis/horizon/api-reference/get-all-offers.ParamsDetails.json
deleted file mode 100644
index 126cf742e..000000000
--- a/docs/data/apis/horizon/api-reference/get-all-offers.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"sponser","in":"query","required":false,"description":"Account ID of the sponsor. Every account in the response will either be sponsored by the given account ID or have a subentry (trustline, offer, or data entry) which is sponsored by the given account ID.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"seller","in":"query","required":false,"description":"The account ID of the offer creator."},{"name":"selling_asset_type","in":"query","required":false,"description":"The type for the selling asset. Either native, credit_alphanum4, or credit_alphanum12.","schema":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]}},{"name":"selling_asset_issuer","in":"query","required":false,"description":"The Stellar address of the issuer of the asset being sold (base asset). Required if the `selling_asset_type` is not `native`.","schema":{"type":"string","example":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}},{"name":"selling_asset_code","in":"query","required":false,"description":"The code for the asset being sold (base asset). Required if the `selling_asset_type` is not `native`.","schema":{"type":"string","example":"USD"}},{"name":"buying_asset_type","in":"query","required":false,"description":"The type for the asset being bought (counter asset). Either `native`, `credit_alphanum4`, or `credit_alphanum12`.","schema":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]}},{"name":"buying_asset_issuer","in":"query","required":false,"description":"The Stellar address of the issuer of the asset being bought (counter asset). Required if the `buying_asset_type` is not `native`.","schema":{"type":"string","example":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}},{"name":"buying_asset_code","in":"query","required":false,"description":"The code for the asset being bought (counter asset). Required if the `buying_asset_type` is not `native`.","schema":{"type":"string","example":"EUR"}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-all-offers.RequestSchema.json b/docs/data/apis/horizon/api-reference/get-all-offers.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/get-all-offers.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-all-offers.StatusCodes.json b/docs/data/apis/horizon/api-reference/get-all-offers.StatusCodes.json
deleted file mode 100644
index 683fe7d65..000000000
--- a/docs/data/apis/horizon/api-reference/get-all-offers.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"offer_maker":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","offer_maker"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"seller":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"selling":{"type":"object","properties":{"asset_type":{"type":"string"},"asset_code":{"type":"string"},"asset_issuer":{"type":"string"}},"required":["asset_type"],"title":"BaseAsset"},"buying":{"type":"object","properties":{"asset_type":{"type":"string"},"asset_code":{"type":"string"},"asset_issuer":{"type":"string"}},"required":["asset_type"],"title":"BaseAsset"},"amount":{"type":"string"},"price_r":{"type":"object","properties":{"n":{"type":"integer","format":"int32"},"d":{"type":"integer","format":"int32"}},"title":"Price"},"price":{"type":"string"},"last_modified_ledger":{"type":"integer","format":"uint32","title":"last_modified_ledger"},"last_modified_time":{"type":"string"},"sponser":{"type":"string"}},"required":["id","paging_token","seller","selling","buying","amount","price_r","price","last_modified_ledger","last_modified_time"]}}}}},"title":"Offer"}]},"examples":{"GetAllOffers":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/offers?cursor=&limit=3&order=asc&selling_asset_code=USD&selling_asset_issuer=GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX&selling_asset_type=credit_alphanum4"},"next":{"href":"https://horizon-testnet.stellar.org/offers?cursor=88345152&limit=3&order=asc&selling_asset_code=USD&selling_asset_issuer=GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX&selling_asset_type=credit_alphanum4"},"prev":{"href":"https://horizon-testnet.stellar.org/offers?cursor=71673427&limit=3&order=desc&selling_asset_code=USD&selling_asset_issuer=GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX&selling_asset_type=credit_alphanum4"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/offers/71673427"},"offer_maker":{"href":"https://horizon-testnet.stellar.org/accounts/GBJPWEIFX6KO4H52BF3QJDYRCLXB2P3Z3QTKWUGFOOFH5MSRZV4WLRZ7"}},"id":71673427,"paging_token":"71673427","seller":"GBJPWEIFX6KO4H52BF3QJDYRCLXB2P3Z3QTKWUGFOOFH5MSRZV4WLRZ7","selling":{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"},"buying":{"asset_type":"credit_alphanum4","asset_code":"BTC","asset_issuer":"GAUTUYY2THLF7SGITDFMXJVYH3LHDSMGEAKSBU267M2K7A3W543CKUEF"},"amount":"25.6545775","price_r":{"n":289696073,"d":25654776},"price":"11.2920913","last_modified_ledger":26981646,"last_modified_time":"2019-11-26T13:42:10Z"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/offers/88328208"},"offer_maker":{"href":"https://horizon-testnet.stellar.org/accounts/GBSYMLHG5TGQ4O3NSPIO4DSCS4AC6YRJOQWQC3EW7O257RAUHI5SA45R"}},"id":88328208,"paging_token":"88328208","seller":"GBSYMLHG5TGQ4O3NSPIO4DSCS4AC6YRJOQWQC3EW7O257RAUHI5SA45R","selling":{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"},"buying":{"asset_type":"credit_alphanum4","asset_code":"BTC","asset_issuer":"GBVOL67TMUQBGL4TZYNMY3ZQ5WGQYFPFD5VJRWXR72VA33VFNL225PL5"},"amount":"2.4664893","price_r":{"n":500,"d":1233},"price":"0.4055150","last_modified_ledger":23886660,"last_modified_time":"2019-05-17T00:33:16Z"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/offers/88345152"},"offer_maker":{"href":"https://horizon-testnet.stellar.org/accounts/GACTQP5TAWIXF2LV4GWGJWIUNHKDWZ2ITCFDP37FIGOFPR3ORMQRR63U"}},"id":88345152,"paging_token":"88345152","seller":"GACTQP5TAWIXF2LV4GWGJWIUNHKDWZ2ITCFDP37FIGOFPR3ORMQRR63U","selling":{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"},"buying":{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GBUYUAI75XXWDZEKLY66CFYKQPET5JR4EENXZBUZ3YXZ7DS56Z4OKOFU"},"amount":"10.0000000","price_r":{"n":11,"d":10},"price":"1.1000000","last_modified_ledger":23887778,"last_modified_time":"2019-05-17T02:19:19Z"}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-all-offers.api.mdx b/docs/data/apis/horizon/api-reference/get-all-offers.api.mdx
deleted file mode 100644
index 0acb9551e..000000000
--- a/docs/data/apis/horizon/api-reference/get-all-offers.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: get-all-offers
-title: "List All Offers"
-description: "This endpoint lists all currently open offers and can be used in streaming mode. Streaming mode allows you to listen for new offers as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known offer unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream offers created since your request time. When filtering by buying or selling arguments, you must use a combination of selling_asset_type, selling_asset_issuer, and selling_asset_code for the selling asset, or a combination of buying_asset_type, buying_asset_issuer, and buying_asset_code for the buying asset."
-sidebar_label: "List All Offers"
-hide_title: true
-hide_table_of_contents: true
-api: eJztW+tS28qyfpUp/chKVtnGd4OrUucYfMFgwPjCxVkUjKW2PQtpRntmhMOmqDqvcV7vPMmpHklGvgQIyV5J1t75A0ijvn7d09PTebA0nSqr+sk6mUxAKusqZTmgbMl8zQS3qtZgxhQB7viCcU1cprQi1HWJHUgJXLv3RPjAiTCfE8odYlNOxkACBQ5hnCgtgXqMT4knHMiQ/tLfSEvMFbkXAdHC0AdOJkISDvMFVUX0DO4JlUCo44CDS/UMSF+D61JJXHCmIDOkPSE2dd1NjFNkX0j2T8HJnLkuUZpKTag2ZIBKl4HS5JaLeaQLCbgLShGKmiohCVNEgU4h5fmM2TNiUwWE6SS9iRQe0TOqo48yZPcev9IoBXKKaN1RNwBUgot5yuiORgsFjpW2JVANDlGM24BrJJHwjwDF1MyDDDmfoaWYq0Ei+fE9GQf3+JuQRIHr4q9UTgMPuFYhFy9QGh2DWglvzDhFLxMxiT+4pkqBvtb3PqRWnjGlApAp4+LlNzb6EV2GGi44K2MtIdd5hWIusVp6lOS09GKJUaSseZOxUpbwQRoWbceqWi3QNdeNQJ2yfCqpBxr/qH56sDj1wKpayhdcgbRSFkOo/yMAeW+lLDQzk+BY1Ql1FaxGRM22RcA1addRGaMz0kFvN+5A3hMaLWDcvJUQ8gmBAkzPQGKARF+Bg67DhVN2B3zxNZKXZEbv0FsqGAPX8p681zJQ2mUcUiFQjIkdqikxCz5E4ES0vkQfrabsGXjUqj5Y6Ai0iUY0WSkLPlPPd/FRq350enp8cFQcdiqn7Vq53K308t3R/tFp+/h8tHtUqew2do/2O82LeumgMazttw4qveLByHp8TD3ZGlz3q009mMGSPUJzh/Fp4kPIjLXCZBlab2CIn22Gc4Y0Qu8hlu8ghTI4TF9T159RHnhF44yVh7n8C3bmgYcJOKRppaxVouuPcnnratW2q+HzBsXjbEodR2Lqi8wd0ov/MjzIGNAoSrgOeT/GPGgef8iQXsSGsHD5zbpLbhCcXGhyE6p883ocDg+PWsNWfXR6WL7cv6yVRuXaZb5VvKj3R93+qNA/Lw2PC7Xe2dFJ+bTfq593S5edxsUaDpczyhsstZSIfqBFhv36knJrmfVb4Z/UbSyC6UyT9yYcQS4UjGIilj1FblYRfGPiYvVxLv+Snt8eGRv2lb8iML5kqjUsrDnsxwbH2m77PWPjBxilMewt6ReWX1+73xMeeGOQYWFn6mCFtRslygebTZhNXGGH1Q3jptxxXbDjaife/sPimCniB6ZCjWpFID6dorpa3AKPKkMxIZRIsIV0NqrKuIapgfJC13I5Wy7nKsXK9k5pJ5ctJdUW0vn6Koc4oNj0qWozOy8SeqqAQwkVUTMRuA6hvg9UZsiJoaEI47YbOEBuqLJvyHuqbOAO49MPJhsguxvyHn9Ej039rvG8EZethCn+f//zvzqqvDVxYEIDN7S/Ifu6DEKVbYUKLqcHl3lMvwHjHv3MvMCLgWG8HJpCgg4kBydDcJ2hb2p7SfkUQp/nUPh8NkvShHIS+D7IaKEBGFNkRqWDYWSOMfGxBUPKBzkR0qN4IpBAleDqGaPFDgRnzXa57Gtxlcs+Pl6lrM9pFfi+kFqlF+cqq6plAGiwCOFIKZ/N4o9lm/UD2waFhbgtuAaucQn1fZeFcbP1p8J1DwmJKFbvpliPZBPjP8FGZ/kSS33NQn7XLuO3KqHDF9YpcCcvr5pJmGwCkrG6Nojht9ZjytLg+S6aNrF6LIQLlGPGSYDoU0j0KmVppl1I0ODwWf9kIvkS7n4qkR5xWfyoY1yN8fsCJsAbA/YJXlYlitvEQiolxTTANHivwNUvjD9zjrr26C3In0qylUXGcsvSXj2mLOZsEiemxBwD58TWur76MRWfSjcQ8qnWIDF5tT7V0qNseufqoVR6TLCIqsGYjEmIL1kxUZlvEidReH35dVTGri9YsVuCV8LEu1RBDd8gwbDS+uXEph6WkBt5+ZLZcP0KPCfx8LTtLdDMuC7kkaDzqnWJJNVFCRaibBTSpUpfe8JhEwbOddi8fJ5NEPJJRMomEmuksVG4GfdR5+tFbzDHWgmj1FMrJ4b9AkgL1zw5IrbDF7TeKPHV43LeN2086xGjPqpLjAuXenzVB8vUzss5Oc66YfayZlr7qrq1NQtrqrQGpTnojAoPeBkhp1th+/W/wqPCx3emMvtYeGdK349U2e/WOwgfh/36u01NmI9vPZW9W28SfFw7/SZKiDfrt71dKJZypfxPrmdcl7xZz0quXCkU85UVPbFM/YkUfUwt1y6L6uTTdwH1VmyFDbv/VxCLOrJqq7V70D1vtJsX5cOT4n4pv9ssnB7UL3t7nYvdfLcwKpwODs+HrebJSXO/dNTvjc6K553eqGIUxf07lmd1p7YWgj5t0dabuS3tz8mtbFNDKbmXmf7a6v71DZ2W5Ib7VXLsDvY2yFEbDoaXl/nBfqdZ6bfag3rz6OLg7HK/0Nmv949ajdphf3eYL1eO8oeVWuG8VCzsHQ4bzeQOauVLmXKpWKpUStbS5smtan57p7xTzlYKZhPMl8qlYqVSftrYrFwuk9/JZ3dyhS9l92q+vLOdKxfLmzcmK5/N7aRzuXS+PMgVqsV8NZcdmfr+e4B9e7uQ385nt78b2PuXR539VmnQOi2eFI773fZJsd7f6xdre+XL3sHJ6fnpXqFxXjnJlyq92nC/XerXiqXeAuyxPGtgXwi6BPY3cvu7gn337KRTrgyOhqe7rU5xMLo8ProsjE5L563Ty2a3WS+dHfTOL3qV/FmtUDhrHnfy+VK3U1oGe6ZYLhe3dwprWC9lswbluXyhkEB4NlPMlkq5UvbLAC9sb5fL5exzAM+W0rnKIJutFgrVXPm7Atzs3d8L4LW9wWm3NKidty+a+c5ZsXXeOjhvD4/3D+vno3x7sNesdwuVZrt10uz2Cie9o9Ner1wYJgFu5NkE8FDQJMDfyu3XB/hmOXaHl8Nau1K6uDivjxqHnctyea95eXjabQxKB71io3F8MdodjgqXF6NKvV8qj4onhyfN4RLAc9lMNvy3hvBcLgR4NpnAM7nF6i/Du1KpbL8C3vlqbqea2xlhnR79w3JdA1fYDTY1zC3cW9XNvcRUXL5jTxE7jh7omcCr/Cno8Dw+s6pWhH2DAnkX3+cH0n0d2q1N3dxBuI4cg54LeWviczPFSaADCa+h2YxXEh5TvcI+80SYM1d0sIl6u6g8SBV+nc1kMznUL/A8Ku+fVhFfijvmmIsEsj8YdEmt28Zmrrn9j4YN4quqiGuGtHEOYQpmbIc7RELaGM5M1IRf+lI4gf00JrBCIrzTwJPooj8NVDG8DxHEFlwFHsSf0juQdAok0dolElxzaRPP7CR62GkhGXAccjGCSPAlKOCahvcHZoJofL8QaE9IwL46U0bzhB5jyZwpkDHoOeCIg++H2i5/2ZUCWwGKuOwWyBwHhXAwxgEbRyeoy/4JDoHP9gx79SqcPwkvsMIoNRIt+vFa4FSGadtLyhU1Fz4qRcw1ArooHlwYUxeVNXeg0YgP3OFMTihH8mtzrbT4MrOGrH93JHxKOvTqfRyeDtyBi80dtbSzRWJv2UJCmgsHPvxboecP/geP2UUzedRcw4BD7hgl9rDXSRFKxlLMVTRIJDjEd30LW/frh+pFWzvCVltaCFdtKedWoaUFkYBwCgffBLZtPjN9j/TNNJsfGjRF5mCuzzwPuGPG1MyEGkfGhHGlgTr4kUdv8RrZYRJsbXyIs37K6GncOg2YAySMmDEoMhNzYxLHYxznCnEULYS4gWNsG2RhbtTeS5iEYDb61xea/kZ2XTF9ssF8Pl9WfrEyPXbFdIumOczTKuBp3IVmkI72jw/mEk8JDBNq306lCLhDBF+NhhA70p4xDbYOJHUJ8zDmwczyhR5iinj0TxwmDLcOMg48/0OGNHFWkYedQ3xMxyLAyz8johkPDPktoCEcwIGVFLFnYN8SXJ3U31wpttC0TwaYMj0LxhlbeFuRHeKfsapbY1eMtzzK+Fa9cdbonHTbx62M53ww7tqFiZCAjh/DlHG8nvxNkbmQGi+VmTaTfNHIJKYBZoQAeybCO1EjH4YlORbOWxIBcYRtLkuNjark99/nQBxhhgyAO0IqIDLgHIWIDYUuC9MQxXFP7lAXwyWZJRZY+v33MAGAGRGgrntvSJtvr++oyxyj4PXa3gYIfQlEzwVRgGOLGoOH2yB5lFQcsEXgu5F9PEzDzMNyinJtADYWxowuo2PmYsThVwl4ZZagj9HlUU6noAhDcM15ivhUgpN2cBo2hpeYLKsqfM08k/SQZ/QlJjVMeWJCOICjyPs5/Oa6JBFZzMzzUvKHtUd9sx0guT+she0QItjpBumpk0kf5F1YrcZOTnrWLEqLidnKwjYz3jBT23RFo1v+WOwkoJsYesb5Vmql2Fsu7cCjzLwF1xX/nXyH3XZmA1eQ4FXzqT0Dks9gTc0cxO6EmQI/fJMO3zxxjNIJNW+NThFRtdVp7zWO+w38JDPTnmsOWr5Q2qM8wbLDlCY11yWLadelouHh6c79P8Pc/xnm/jWGuaOTtIbPest3KeMYbSZoHqKT4CdLLP7HwkwojU8eHnAjG0r38REfhwM9eD50mKJj90sjPckI+VsNd2+0YngGfxp9j47dljn2PpM5XjGJ/TzH+NZwmeGrPfMvG81+Qea1gdpvkP9HTli/Ws3FmOw3KPpXDEi/WqFokPV74e4vmIl+RrVNI95/JSK/8xTvazX9l4LyB+n0bbj88WPJz+i5GLR+s3K/zPTxM1aI566/AbN/k0njZ4wUz2A/GekK/5AMrWRVP+HUzwwoWvLpCqFm2+Anv1obJl66Qmg1Btbj4/8DFCZr3g==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Offers"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/offers"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint lists all currently open offers and can be used in streaming mode. Streaming mode allows you to listen for new offers as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known offer unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream offers created since your request time. When filtering by buying or selling arguments, you must use a combination of selling_asset_type, selling_asset_issuer, and selling_asset_code for the selling asset, or a combination of buying_asset_type, buying_asset_issuer, and buying_asset_code for the buying asset.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./get-all-offers.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-all-offers.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-all-offers.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-all-offers.mdx b/docs/data/apis/horizon/api-reference/get-all-offers.mdx
new file mode 100644
index 000000000..f1360a90f
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/get-all-offers.mdx
@@ -0,0 +1,12 @@
+---
+title: List All Offers
+openapi: "openapi/horizon/bundled.yml GET /offers"
+---
+
+<Tip>
+
+**Supports Streaming**
+
+This endpoint supports streaming. To read more about this, visit the [streaming section](/docs/data/apis/horizon/api-reference/structure/streaming).
+
+</Tip>
diff --git a/docs/data/apis/horizon/api-reference/get-all-trades.ParamsDetails.json b/docs/data/apis/horizon/api-reference/get-all-trades.ParamsDetails.json
deleted file mode 100644
index 1cdc890a1..000000000
--- a/docs/data/apis/horizon/api-reference/get-all-trades.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"offer_id","in":"query","required":false,"description":"The offer ID. Used to filter for trades originating from a specific offer."},{"name":"base_asset_type","in":"query","required":false,"description":"The type for the base asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.","schema":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]}},{"name":"base_asset_issuer","in":"query","required":false,"description":"The Stellar address of the base asset’s issuer. Required if the `base_asset_type` is not `native`.","schema":{"type":"string","example":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}},{"name":"base_asset_code","in":"query","required":false,"description":"The code for the base asset. Required if the `base_asset_type` is not `native`.","schema":{"type":"string","example":"USD"}},{"name":"counter_asset_type","in":"query","required":false,"description":"The type for the counter asset. Either native, credit_alphanum4, or credit_alphanum12.","schema":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]}},{"name":"counter_asset_issuer","in":"query","required":false,"description":"The Stellar address of the counter asset’s issuer. Required if the `counter_asset_type` is not `native`.","schema":{"type":"string","example":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}},{"name":"counter_asset_code","in":"query","required":false,"description":"The code for the counter asset. Required if the `counter_asset_type` is not `native`.","schema":{"type":"string","example":"USD"}},{"name":"trade_type","in":"query","required":false,"description":"Can be set to all, orderbook, or liquidity_pools to filter only trades executed across a given mechanism.","schema":{"type":"string","enum":["all","orderbook","liquidity_pools"]}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-all-trades.RequestSchema.json b/docs/data/apis/horizon/api-reference/get-all-trades.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/get-all-trades.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-all-trades.StatusCodes.json b/docs/data/apis/horizon/api-reference/get-all-trades.StatusCodes.json
deleted file mode 100644
index 3899622d3..000000000
--- a/docs/data/apis/horizon/api-reference/get-all-trades.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"base":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"counter":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operation":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","base","counter","operation"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"ledger_close_time":{"type":"string"},"offer_id":{"type":"string"},"trade_type":{"type":"string"},"liquidity_pool_fee_bp":{"type":"number","format":"uint32"},"base_liquidity_pool_id":{"type":"string"},"base_offer_id":{"type":"string"},"base_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"base_amount":{"type":"string"},"base_asset_type":{"type":"string"},"base_asset_code":{"type":"string"},"base_asset_issuer":{"type":"string"},"counter_liquidity_pool_id":{"type":"string"},"counter_offer_id":{"type":"string"},"counter_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"counter_amount":{"type":"string"},"counter_asset_type":{"type":"string"},"counter_asset_code":{"type":"string"},"counter_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"base_is_seller":{"type":"boolean"},"price":{"required":["id","paging_token","ledger_close_time","trade_type","base_amount","base_asset_type","counter_amount","counter_asset_type","base_is_seller"],"type":"object","properties":{"n":{"type":"string"},"d":{"type":"string"}},"title":"tradePrice"}}}}}}},"title":"Trade"}]},"examples":{"GetAllTrades":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/trades?base_asset_code=USD&base_asset_issuer=GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX&base_asset_type=credit_alphanum4&counter_asset_type=native&cursor=&limit=3&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/trades?base_asset_code=USD&base_asset_issuer=GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX&base_asset_type=credit_alphanum4&counter_asset_type=native&cursor=83056000260648961-0&limit=3&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/trades?base_asset_code=USD&base_asset_issuer=GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX&base_asset_type=credit_alphanum4&counter_asset_type=native&cursor=82854686553571330-0&limit=3&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":""},"base":{"href":"https://horizon-testnet.stellar.org/accounts/GD47M25MLSCSYP4SIVNQXVQ4KWNLVGXS4S2AXPTYEJK6OY4VALJWK4BS"},"counter":{"href":"https://horizon-testnet.stellar.org/accounts/GBCHK52UXADCQCO7FBA5VBYPGCJFXHCNAVJTMUEKOCCNKJH5F35UZU5T"},"operation":{"href":"https://horizon-testnet.stellar.org/operations/82854686553571330"}},"id":"82854686553571330-0","paging_token":"82854686553571330-0","ledger_close_time":"2018-08-05T00:55:34Z","offer_id":"23074703","base_offer_id":"23074703","base_account":"GD47M25MLSCSYP4SIVNQXVQ4KWNLVGXS4S2AXPTYEJK6OY4VALJWK4BS","base_amount":"22.9174941","base_asset_type":"credit_alphanum4","base_asset_code":"USD","base_asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","counter_offer_id":"4694540704980959234","counter_account":"GBCHK52UXADCQCO7FBA5VBYPGCJFXHCNAVJTMUEKOCCNKJH5F35UZU5T","counter_amount":"97.9999800","counter_asset_type":"native","base_is_seller":true,"price":{"n":"106905209","d":"25000000"}},{"_links":{"self":{"href":""},"base":{"href":"https://horizon-testnet.stellar.org/accounts/GD47M25MLSCSYP4SIVNQXVQ4KWNLVGXS4S2AXPTYEJK6OY4VALJWK4BS"},"counter":{"href":"https://horizon-testnet.stellar.org/accounts/GDURV3I6U5OTUV75WWAG2HWZTQHNMCR3NR2P5GPKDCIS2AEWCFSOLVFU"},"operation":{"href":"https://horizon-testnet.stellar.org/operations/83005225157287937"}},"id":"83005225157287937-0","paging_token":"83005225157287937-0","ledger_close_time":"2018-08-07T02:01:53Z","offer_id":"23400441","base_offer_id":"23400441","base_account":"GD47M25MLSCSYP4SIVNQXVQ4KWNLVGXS4S2AXPTYEJK6OY4VALJWK4BS","base_amount":"1.0000000","base_asset_type":"credit_alphanum4","base_asset_code":"USD","base_asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","counter_offer_id":"4694691243584675841","counter_account":"GDURV3I6U5OTUV75WWAG2HWZTQHNMCR3NR2P5GPKDCIS2AEWCFSOLVFU","counter_amount":"4.3080953","counter_asset_type":"native","base_is_seller":true,"price":{"n":"430809521","d":"100000000"}},{"_links":{"self":{"href":""},"base":{"href":"https://horizon-testnet.stellar.org/accounts/GD47M25MLSCSYP4SIVNQXVQ4KWNLVGXS4S2AXPTYEJK6OY4VALJWK4BS"},"counter":{"href":"https://horizon-testnet.stellar.org/accounts/GBNDB4UHLDRBLR35JNU4ADYG3J5WA4LJZOPBXMNHZKTKSL37BDX4UBQY"},"operation":{"href":"https://horizon-testnet.stellar.org/operations/83056000260648961"}},"id":"83056000260648961-0","paging_token":"83056000260648961-0","ledger_close_time":"2018-08-07T18:27:33Z","offer_id":"23400441","base_offer_id":"23400441","base_account":"GD47M25MLSCSYP4SIVNQXVQ4KWNLVGXS4S2AXPTYEJK6OY4VALJWK4BS","base_amount":"1.0000000","base_asset_type":"credit_alphanum4","base_asset_code":"USD","base_asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","counter_offer_id":"4694742018688036865","counter_account":"GBNDB4UHLDRBLR35JNU4ADYG3J5WA4LJZOPBXMNHZKTKSL37BDX4UBQY","counter_amount":"4.3080953","counter_asset_type":"native","base_is_seller":true,"price":{"n":"430809521","d":"100000000"}}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-all-trades.api.mdx b/docs/data/apis/horizon/api-reference/get-all-trades.api.mdx
deleted file mode 100644
index 403dddee8..000000000
--- a/docs/data/apis/horizon/api-reference/get-all-trades.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: get-all-trades
-title: "List All Trades"
-description: "This endpoint lists all trades and can be used in streaming mode. Streaming mode allows you to listen for new trades as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known trade unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream trades created since your request time. When filtering for a specific orderbook, you must use use all six of these arguments: base_asset_type, base_asset_issuer, base_asset_code, counter_asset_type, counter_asset_issuer, and counter_asset_code. If the base or counter asset is XLM, you only need to indicate the asset type as native and do not need to designate the code or the issuer."
-sidebar_label: "List All Trades"
-hide_title: true
-hide_table_of_contents: true
-api: eJztW/1SGzkSfxXV/JFNtmwz/sauSt0ZTIBAgGDMV5YCeaZta5mRZiUNhqOoute417snuWppxozt4WMJuc1mN1Vb2XhaUvdPv5a6pdato+lIOe0vzoGkPijnrOD4oDzJIs0Ed9rOwZgpAtyPBOOaBExpRWgQEG3kCeU+8SgnAyCxAp8wTpSWQEPGRyQUPpRIb+bf2FhMFLkRMdHCdAicDIUkHCbTXhXRY7ghVAKhvg8+iuoxkJ6GIKCSBOCPQJbI5pB4NAjyBi6QDSHZvwQnExYERGkqNaHadANUBgyUJpdcTLgdlcQ8AKUIJV4slZCEKaJAF7DnyZh5Y+JRBYTpbH9DKUKix1QnjUpk5QZbadQCR0r6uqJBDGgEF5OCsR1BswqnRnsSqAafKMY9QBlJJPwWo5qahVAiR2NEigUaJHaPmFGiIvDYkHlESB/kQIhL238YK41TYv7DCVPsmoghKoU/yFEcAteqTQZUwTlVCvS5vomgkP2BKRWDnPnJM9B6IuYa5Ey72d/SpoYgM188w4pNo4rpmQiZihAjgtAfb3+yhgge3BAOlgOM+8yjGkxbK4uDI2E41ewKzHg+4qynjXxQbMTTVjg8joj/b5UsOQVHRCApUn7Td9rOOuhOECQuUXAiKmkIGiR6yq3DaQhO2xHDIchz5jsFh6Gn/BaDvHEKDk4ak+A77SENFCw6FBDTlGx2S6SvrI52Ws2cJnQQko0YGoVTjTTLzjW2Lzl3hakyc7P4Ap0MjsMEGDMtprsSWWN6DJJcWIAvCuTCk+AzfU6DaEx5HNYuCgjo/M/lygUiq7wxhNRp3zpGsbajNNLXKTjA4xCXHtuxU3Dm+138qVxxzu7yzbZz+QLD0zWF+r7EBUAM5yD477//o1KqkP2kQ8Ks2MUc8hdIXmRfitcTGFzTMArwp/Vuf+vTen+9e/p5q3GycdKpnzY6J5X12nG3d7rXO632jur9nWpn//DTbuNzb797tFc/2V47dh7AA3n+AjSMe+TR4JsZ3u91Z2xYXFu+ls0zi8uU0FbNAplnnSHzAu++OZXzls/XY/MMBI8TehH/P5bTi7vH19J6jg/fEoF5cpvF/SWkXrVBltnxBG7oheyOLyQJ2G8x85m+OY+ECFRmUzE7aLKrwDV4MUYZ1JPCRDsjdgWchOCNKWcqfB7PaRDgppkq4BScueHnuG2ioN9pcYfwOByAtPGViT+NVZl9MBCe2bQxRqPEE0EAnvm3GBIJKhJcJTEqUySKTaCYhGxAIjpifHSuxSXwJEATQ0KJBE9IPxcHxjWMjFtOZ7jRcBuNcrPWXG7VW2W3njXb4PO7rU7DlcQOVNV0dB+IWg0VUWMRBz6hUQRUlsiu6UMRxr0g9oFcUOVdkLdUecB9xkfvzC6Nw12Qt/hX8nMSjDE1DQsJU/y///6PTgJgTXwY0jiw+Jtun0kT5TnWwFk+BCxk+gVeHNJrFsZhSgwzyxYKCTqWHPwSQTnTvwmxJeUjsHNeRuUrrkuKhHISRxHIRNAQjCkyptLHhcJkE2n2gItGBHIoZEgxMJdAleDqEdCm8aa/gF3ZfS6vyu7d3VnBuS6qOIqE1Ko4TW+ctpYxIGAJw7GniuviX7OY9WLPA4UhrCe4Bq5RhEZRwKzfLP2qUO42oxENgt2hCXMT3cTgV/BwsiKJQbJmdrzzgPFLlbHhATkFwfBpqbGEYR6RDOraMIZfOncFR0MYBQhtRnogRACU4zqbIdEX2+lZwdFMB5Dpg8O1/s5UiiRcfVcq3aFY+tO2mWr03yc4AeEAMF1/2pTEbzOCVEqKywDTED6DV39i/mHg/J2plEQ835lW06T8u9JrTsgQLJnUeyCzyp/dFRzm52mXdsx8swhkApLHpGfk7gqOPQw79wKh4ByPihYbI5jpcUXex0xYmvd5Nrg7HwKcD6KMpN2Ps3DHjOtqJWX7+VwHD2hhRB/V0+acnkE5D6KIag0St771L53iqVtsnd3W63cZ8JK86L6zML+v6ff7LPQJGZOZPCGTpHV5UmnS8TyoUulH0ZrmMa8E2LS/hzHLSd6fFnsQudyc+FWmnalzBUEw0910GcDFhXlg96l7TzdHfTPOl+d7hdkcL0uyRUotYJqL4ILOuCY9uhzmrB93BSePJZlt3ui9Zyy/s3/uv5mzUOcOl7IkRDXjzByUtm8dk0bNbs/pBmxXaGesdaTaS0tjG14XNSjNQZeUPbcoCTlasrnqP+Z8632/132z4EvvX3rG8GZuLt7PH9m8WZyJ9zb7f2Pz2fdvTPrwvvrG5GfvMdvJhJc/oMHLVbfecF230nAbteVWo1x08zFI49kfEYPKcr3WWG7U69V6s1ytugsYmHwXnWcmHp5GvF8e8Y5sePg7sEsWeLW03q01P1Xqn7Z7q72TvVpv83Dn8/Hh59rW0c724fpxr9ardI73Dk7WPm41dk9qh53tj0dbtZXeXAz4oqFXVje26pX+cae7+nl1t/lhpVM/XDnZW1/9+OF4Y3Wnc/jx4FN/bWt3dXVn6+NG/UO13j/t1w8WAr3fMfi0nVpamBYzA7gxOjkzNr+QPySUE1o5Fbe8XHSXi279wHXb9Xq7Wjt1svGVU6m6zVrTrToLIc3Cp+nW7Lx46uYCGadSKbXKzVqrVs7ZcNp5J9MLQYw5tswNXF5+pJsXszi1RqtWr7lNt9Zadlv1VqVac3LiFufF5FoMWpxWs9RqtVrLrpu/27bvT/HnQwV77jINDpA3ZbfRcusVt+WY/dWp1F3zx576/pCO3u3vH1Y3G/367kH/sFk/OuqsVzaOTg8+b+x8Wt2v7uxX9urre1vd1c1epbN2tPqht7t9+KH/Wo5edd16pVIv15uV5War2sw4+vynXEfPFXrU0ZsHbqXtltv16oKj11y3du9oj3z6Bo5eLrkJ1/4Uft5olSu1an251mjWlw0wOX7+Um7l+HmtVHVxUam+hpvXbF+VcuLmZdf94f18Zae7UutvbHf3V7b3q/WPO/1ap3uyXv1YP+rUtj+e7u6tHH/a2TjdOtjqbVebK93jWn/l88nr+flsrDnj5/NhaK6f5wg94efl5Xal2a7+7edf4efNGgLaWF52qxhPPbCfv5Bbf6Sfn91N02K41sAV8tTE85dw47Tz72oKaU6Mg+GNTgh6LLDrEWh7dDF22k6S/uDlEMirtNIolsHzHMfJuy07sHJkB/REyEtzgJ/f4zDWsYTn9PkhlSQ87fUM7/GGwpwtJKcFyd0ZGg9S2dZuyS0hqioOQypv7qVIJMUVs8WEZOPgYI909jZN3RbVFG/isoV/yaglsqkJ4yMw5YjcJxKKBjhTOGhbRlL4sQc+GdzkdWHvjPHAcnr/B1QxvG8WxBNcxSGkTekVSDoCkrk6IxICW3GWlCZm7giLQjLgeMtuFJEQSVDAtV3ZbKHk4Gaq0KqQgPeWTBnLM3YMJPNHQAagJwAch7fWzrbckwIPgRQJ2CWQCdZDalUgPnjAtaQB+xf4BK7xgn8EypbkpXV2uAoYjab3nVoQFQ/MtaikXFFzoa4KxFzT4hQlXkwGNEBjTfFBUskIV1hTaPXItjbX9tOWpQVm/dWZ8CU7oWdvU/f04QoC3BLVzCaZqL3kCQlFLnx495dizy/8F54Ol5QeU3PNDT65YpR4/f3tAqFkIMVEYQmqwBIYSGspplj3ulvqSax94akljRUtS8q/VIi0IBKQTkkpEZ6FXjN9g/2bot3IAlogEzDlCWEI3DelrKYUl+PAhHGlgfrYKKSXWOPpMwmeNnOIJc3K2GmmdRQzH4j1mAEoMhYTA4kfMo7l01gGbClu6Jhig0OYioW3EoaWzMb+7tTSn8hKIEb3GEwmk1njp5LFQSBGS7TIYVJUMS/iLjSGYrJ/vDNFEkqgm1DvciRFzH0i+Lw3WO5Ib8w0eDqWNCAsRJ8HU4tsZ4gpEtJfsWbabh1kEIfRuxL5gCXZ3F4w4c90IGIsrjAqIoDJeFNqCB9wwy8QbwzeJUHprP2mZGMdob0HYMT0OB6UPBEuJTikf6emLg0CMVgKKeNL3bXDte3dvc2d9VLovzPTtQJDIQEnfgAjxrH84ydFJkJqLNph2gS3SWU4LgPMKAHeWNiaE6MfuiXZEf5LFgLiC88UoxiM2uTnnyeQlkMD94VUQGTMOSqRAoVTZpchilXt3KcBukt2lZhy6eef7QIApgSLBliaLbRte35FA+YbA88X9jZbdA5ETwRRgAXVGp2HeyB5sqj44Ik4ChJ8QlyGWYjhFOXaEGwgDIwBowMWoMdhqwy9SjPUR+8KKacjUIQhuSa8QCIqwS/6WPSf0ksMZ00VkWahWfRwzKQlLmq45ImhqSpX5O0EfgoCkvEsZp4tUPKLs0ojsx1gd784U+yQIng7BDJUu8MeyCsTd06DsZnDcBQqiqHZylDMVvBQz9wsJFVUqdpZQn9A17OZV2Eu2JsN7SCkzHyFIBD/zH4z970ecJu0JmN1IuqNgVRKmIQwH7k7ZCaBsF+K9sv9iMlyQs1XY1PSqVra3lxd2+mtYZPSWIeBSewioXRIeWbIbaY06QQBmdbhzwQNt/c1TX8/Uvn7kcpf4ZFKks9quNZLUUCZuao2Lneb5JFfHD19xzUWSuMvt7eof18Gd3f4sy23xOzyEXd6tScqDyhtE+bMC5okSXZMkuozRQfBQ5Wg85p+q4crjyi+eI3/Ffr/H96fPM+U6ZuDrzDmdZ+PPE/v5EnAa1HotV6LPKJ8bo3H61Po9R99PNumV+fSK73ZeLYBX0eq/+drjUdMmqlEeqEpf/wzjMfmLH1Y8mLj/jSvLR7bR5N3Jl/haz/Iy4pHQErfnNyDdIb/kAxRctpfsLRtDBSRvD/S73geRNlWC48nZo7019cOnLu7/wHXctaW
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Trades"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/trades"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint lists all trades and can be used in streaming mode. Streaming mode allows you to listen for new trades as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known trade unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream trades created since your request time. When filtering for a specific orderbook, you must use use all six of these arguments: base_asset_type, base_asset_issuer, base_asset_code, counter_asset_type, counter_asset_issuer, and counter_asset_code. If the base or counter asset is XLM, you only need to indicate the asset type as native and do not need to designate the code or the issuer.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./get-all-trades.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-all-trades.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-all-trades.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-all-trades.mdx b/docs/data/apis/horizon/api-reference/get-all-trades.mdx
new file mode 100644
index 000000000..41f450793
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/get-all-trades.mdx
@@ -0,0 +1,12 @@
+---
+title: List All Trades
+openapi: "openapi/horizon/bundled.yml GET /trades"
+---
+
+<Tip>
+
+**Supports Streaming**
+
+This endpoint supports streaming. To read more about this, visit the [streaming section](/docs/data/apis/horizon/api-reference/structure/streaming).
+
+</Tip>
diff --git a/docs/data/apis/horizon/api-reference/get-data-by-account-id.ParamsDetails.json b/docs/data/apis/horizon/api-reference/get-data-by-account-id.ParamsDetails.json
deleted file mode 100644
index 0c821eaf3..000000000
--- a/docs/data/apis/horizon/api-reference/get-data-by-account-id.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"account_id","in":"path","required":true,"description":"This account’s public key encoded in a base32 string representation.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"key","in":"path","required":true,"description":"The key name for this data.","schema":{"type":"string","example":"config.memo_required"}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-data-by-account-id.RequestSchema.json b/docs/data/apis/horizon/api-reference/get-data-by-account-id.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/get-data-by-account-id.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-data-by-account-id.StatusCodes.json b/docs/data/apis/horizon/api-reference/get-data-by-account-id.StatusCodes.json
deleted file mode 100644
index 678369096..000000000
--- a/docs/data/apis/horizon/api-reference/get-data-by-account-id.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"value":{"type":"string"}}},"examples":{"RetrieveAnAccountsData":{"value":{"value":"MQ=="}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-data-by-account-id.api.mdx b/docs/data/apis/horizon/api-reference/get-data-by-account-id.api.mdx
deleted file mode 100644
index 9e9eb75e7..000000000
--- a/docs/data/apis/horizon/api-reference/get-data-by-account-id.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: get-data-by-account-id
-title: "Retrieve an Account's Data"
-description: "This endpoint represents a single data for a given account."
-sidebar_label: "Retrieve an Account's Data"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlV9tuGzkS/ZUCXxIHLbUnczEgIMDasWM7Y3t8y+4ijhFUkyU1IzbZIdlSFEHA/Mb83nzJotjdshQHu7OZeZsXSRCLdTl1qli1FBEnQYzuxL6UrrExiPtMKArS6zpqZ8VI3JY6AFlVO20jeKo9BbIxAELQdmIIFEaEsfOAMNEzsoCtsqHIhKvJI2s6VWIkjikeYsSDRWfuVIlM1OixokieHVkKixWJkeh0vNcsotmRGmMpMuHpY6M9KTGKvqGvetvd/f3X3wLUTWG0hCktgKx0ihRoCwgFBvr+OYTotZ08hJV8ZceDLKlCMVqKuKjZoVZSZII+YVUb/uv48Pzq6uL1+Q9vzvauTvd/+uly7/r55duT86vTi3+9PTjf2zs4Ojg/OXv178MfXx+92T85fr13/cPrt2K1ytaBTmnxf0ZIKRq+nlCPHDLn4I+6LZ0d68mwosq9X9tare7ZcqidDRRYwfPdXf7atn7TSEkhiIy1RLKRRbCujZYJuvxDYLnlY0dc8YFk5Hx7JkXUrZUZmoYe+7tardYuJ7lril7TjPZtT1Vm0paG7oc4v3rxghWskpKKYumYfBNK1hnjkcg7joR8+cC0Vc4w5sspLVaMJflZz8rGGzESZYx1GOV56bz+7OwgUoiW4jBEMgb90HlG+nG+bls5uKA4d34qOP1f1zhuYuPpj+h81UuC7bXeM4/GLqGpY8r1SatXZIJDaW/vDneH33F8TVWhXzxIQe3dTCsKgBZObm8vYf/yFKJrK1xbiCXBTetXb3UIpxG0nVDglmAVeBok4EKSTjdr71QjSUGx+JqKtiDHzlcQS4zA/QaDJs+mpbOhqai/ijPyOCHYoBx4Mhj1jFicZWryrAytpIHzmmwk1TqyXeYBmtA61Tv00nkaQuohHPlGHIXXakJQUJwTd7i6bqPdvnnpHZM8gNFTgjkaQzFkoEiSjR6N/kwK6JMskQHLkgYMgTjm0JBPHkGfjeggNEWlI0SPNqBMTmfwsSG/4BR1zIUCDQebgfPc0AgroFnq0cmPzdusFLc69Daz/u5MuNtM6P3TvjwVzchw2wqbdZl3bufSeRpYp2jnb8Wed/ad7c1JtFAQH1FgLGcaQb65Psv4rfVuHsgnC84SuHFCZY31zeHP4X9irZwMeXTOhDyoaWCkHXhiOiVt0vFb8UnHBetfuMYz2xjQDOYEnqSrKrKKjxJQaNkwaBsioeJLFU55GFDak4wphxKNCSnOlNZJoxVBWzEFBSjdPEGiKm11iMQjUEvxRMceGzbBEMNTT+OWzCn+w3WkT+DAuMkDBvP5fDv4teSgMG6S48DSfBAaO+BXqKRB937spIkgOC4TlNOJd41V4OyX1dByx8tSR5Kx8WhAV1zzVKXMpwzpABV+cB66pwOKpqp3hvDKeeB3xldt1WHhmgidiwxgZ29NDaeIx60MZElyCiy9GT+bhGOG9gGAiY5lUwylq/IOh/67DzUvjCvyCrXND4/+eXT2y+XpxfGwUjspXQc0dp448QVNtM1AxycB5s7HEjzpmKZSO0l+cBvQyQmSpWsHxOQflyVcOPUtjQCUk03VN5gRPHs2J1AOrIs8TTsfCHxjLTvRA8Upa9sQAjNGoeFy2ewSay49e9Y2AAo1SY3GLJLqdPf9DI1WKcD3j942Yup7gjh3EIiH78jFYyV52zUVRdI1tenwqbgN66p2PqKNiWCFSzAajYU2XHF8a4Newy3qc3VVaHFCATSTa24zqNGTGig3t2t6ufF2qK6OukpNj212N7mpcctzY7BEKsDTOT0xBjYqizcAXk/eiZdYp+eA1b0Ta+yYIiITkXwVfhnfkJ9pSRvD2GZmk9DAjdNTxmLt5IsyTb7dDN+7vUnoV1x6Kfki+2LY2x7tqEKdTskY94/Ns1UmjJZkA23Y2q9RlgTPh7u8Nijm7liTX58M2pMHi107wXSaYuqUhvzs9OXRxc0RXxmWsTK8mIjahVih3TDZz97cMrvp+0mANH9/MT8sH9aCP7k4dutApE8xrw1qy2ikoJbdDH/X74i8jYy29kXVujbi3eo+E6ULkeWXS25Db7xZrfjv9BKK0d19JmboNRY8Md8thdKBfysxGqMJXy5gmyE+ve7Wpx34yxbPrwbe/YmWd8V+zxFZWh63dmXeLL7R//+2Vn6DU/y5ul9loiRUzM+7ZXeyLyXVcePOo/2RN5n13nZ8dCtWq/8Adyzq1g==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Account's Data"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/accounts/{account_id}/data/{key}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents a single data for a given account.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./get-data-by-account-id.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-data-by-account-id.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-data-by-account-id.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-data-by-account-id.mdx b/docs/data/apis/horizon/api-reference/get-data-by-account-id.mdx
new file mode 100644
index 000000000..f875ef6f5
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/get-data-by-account-id.mdx
@@ -0,0 +1,4 @@
+---
+title: "Retrieve an Account's Data"
+openapi: "openapi/horizon/bundled.yml GET /accounts/{account_id}/data/{key}"
+---
diff --git a/docs/data/apis/horizon/api-reference/get-effects-by-account-id.ParamsDetails.json b/docs/data/apis/horizon/api-reference/get-effects-by-account-id.ParamsDetails.json
deleted file mode 100644
index c8a2ddd7f..000000000
--- a/docs/data/apis/horizon/api-reference/get-effects-by-account-id.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"account_id","in":"path","required":true,"description":"This account’s public key encoded in a base32 string representation.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-effects-by-account-id.RequestSchema.json b/docs/data/apis/horizon/api-reference/get-effects-by-account-id.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/get-effects-by-account-id.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-effects-by-account-id.StatusCodes.json b/docs/data/apis/horizon/api-reference/get-effects-by-account-id.StatusCodes.json
deleted file mode 100644
index 874797c18..000000000
--- a/docs/data/apis/horizon/api-reference/get-effects-by-account-id.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"oneOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"create_account"},"type_i":{"type":"number","example":0},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"starting_balance":{"type":"string"},"funder":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","starting_balance","funder","account"],"title":"CreateAccount"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"payment"},"type_i":{"type":"string"},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string"},"asset_code":{"enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","asset_type","from","to","amount"]}}}}},"title":"Payment"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"path_payment_strict_receive"},"type_i":{"type":"number","example":2},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"},"path":{"type":"array","items":{"type":"object","properties":{"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}}}},"source_amount":{"type":"string"},"destination_min":{"type":"string"},"source_asset_type":{"type":"string"},"source_asset_code":{"type":"string"},"source_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","from","to","amount","path","source_amount","destination_min"],"title":"PathPaymentStrictReceive"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"path_payment_strict_send"},"type_i":{"type":"number","example":13},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"},"path":{"type":"array","items":{"type":"object","properties":{"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}}}},"source_amount":{"type":"string"},"source_max":{"type":"string"},"source_asset_type":{"type":"string"},"source_asset_code":{"type":"string"},"source_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","from","to","amount","path","source_amount","source_asset_type"],"title":"PathPaymentStrictSend"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"account_merge"},"type_i":{"type":"number","example":8},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"into":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","account","into"],"title":"AccountMerge"}]}]},"examples":{"RetrieveAnAccountsEffects":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/accounts/GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE/effects?cursor=&limit=10&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/accounts/GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE/effects?cursor=147350483860869151-1&limit=10&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/accounts/GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE/effects?cursor=110694007436259329-1&limit=10&order=desc"}},"_embedded":{"records":[{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/110694007436259329"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=110694007436259329-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=110694007436259329-1"}},"id":"0110694007436259329-0000000001","paging_token":"110694007436259329-1","account":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","type":"account_created","type_i":0,"created_at":"2019-09-11T13:16:44Z","starting_balance":"1.0000000"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/110694007436259329"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=110694007436259329-3"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=110694007436259329-3"}},"id":"0110694007436259329-0000000003","paging_token":"110694007436259329-3","account":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","type":"signer_created","type_i":10,"created_at":"2019-09-11T13:16:44Z","weight":1,"public_key":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","key":""},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/110694007436259330"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=110694007436259330-2"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=110694007436259330-2"}},"id":"0110694007436259330-0000000002","paging_token":"110694007436259330-2","account":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","type":"account_credited","type_i":2,"created_at":"2019-09-11T13:16:44Z","asset_type":"native","amount":"355.2904739"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/115354197276323841"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=115354197276323841-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=115354197276323841-1"}},"id":"0115354197276323841-0000000001","paging_token":"115354197276323841-1","account":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","type":"account_credited","type_i":2,"created_at":"2019-11-18T19:59:40Z","asset_type":"native","amount":"688.4065454"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/117356420835532801"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=117356420835532801-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=117356420835532801-1"}},"id":"0117356420835532801-0000000001","paging_token":"117356420835532801-1","account":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","type":"account_credited","type_i":2,"created_at":"2019-12-18T08:23:35Z","asset_type":"native","amount":"355.3887598"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/119399833130811393"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=119399833130811393-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=119399833130811393-1"}},"id":"0119399833130811393-0000000001","paging_token":"119399833130811393-1","account":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","type":"trustline_created","type_i":20,"created_at":"2020-01-17T20:13:22Z","asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","limit":"922337203685.4775000"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/119399833130811394"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=119399833130811394-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=119399833130811394-1"}},"id":"0119399833130811394-0000000001","paging_token":"119399833130811394-1","account":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","type":"trade","type_i":33,"created_at":"2020-01-17T20:13:22Z","seller":"GCM4PT6XDZBWOOENDS6FOU22GJQLJPV2GC7VRVII4TFGZBA3ZXNM55SV","offer_id":"147625249","sold_amount":"539.0320108","sold_asset_type":"native","bought_amount":"32.8490620","bought_asset_type":"credit_alphanum4","bought_asset_code":"USD","bought_asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/119399833130811394"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=119399833130811394-3"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=119399833130811394-3"}},"id":"0119399833130811394-0000000003","paging_token":"119399833130811394-3","account":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","type":"trade","type_i":33,"created_at":"2020-01-17T20:13:22Z","seller":"GBDVKE33GVVMBXX73OHIBRP6RAHKHHW2P4PQVV6UNOKQCOXU7GNUM4QI","offer_id":"147618811","sold_amount":"854.9537682","sold_asset_type":"native","bought_amount":"52.0920258","bought_asset_type":"credit_alphanum4","bought_asset_code":"USD","bought_asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/119400713599217665"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=119400713599217665-2"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=119400713599217665-2"}},"id":"0119400713599217665-0000000002","paging_token":"119400713599217665-2","account":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","type":"account_debited","type_i":3,"created_at":"2020-01-17T20:32:38Z","asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","amount":"84.9410878"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/147350483860869151"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=147350483860869151-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=147350483860869151-1"}},"id":"0147350483860869151-0000000001","paging_token":"147350483860869151-1","account":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","type":"account_credited","type_i":2,"created_at":"2021-03-06T19:27:33Z","asset_type":"native","amount":"0.0000001"}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-effects-by-account-id.api.mdx b/docs/data/apis/horizon/api-reference/get-effects-by-account-id.api.mdx
deleted file mode 100644
index bce86d780..000000000
--- a/docs/data/apis/horizon/api-reference/get-effects-by-account-id.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: get-effects-by-account-id
-title: "Retrieve an Account's Effects"
-description: "This endpoint returns the effects of a specific account and can be used in streaming mode. Streaming mode allows you to listen for new effects for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known effect unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream effects created since your request time."
-sidebar_label: "Retrieve an Account's Effects"
-hide_title: true
-hide_table_of_contents: true
-api: eJztXOly2zgSfhUUf8wkU5LMQ3fV1K4dO7IT31ccZ1weiGxJGJMAFwAte12u2tfY19sn2WqQlCiLcZxDcWZG/uOSiKO78fUBAvruLE2Hyup+sFZ9XyRcK+uiYgWgfMlizQS3utbxiCkCPIgF45pI0InkiugREBgMwNeKiAGhRMXgswHzCU1HIpQHxKec9IEkCgLCOFFaAo0YH5JIBFAjRzOfCQ1DMVbkViRECxIypYGTgZCEw3gyGX7WKNJkHiPMLaESCA0CCLAzinekIQypJCEEQ5A1sjUgPg3DMlEqZFNI9m/ByZiFIVGaSk2oTrWkMmSgNLniYswzOUjCQ1CKUOInUglJmCIKdAWHHo+YPyI+VUCYLg44kCIiekR11qlG1m6xl0YxcKpsrGsaJoBacDGuGHOgHVOJJ3bwJVANAVGM+4CNJJHwrwQF1SyCmlWxRAyS4ipuBVbX6oHeSPuu3WarvRVYFSumkkagQSIO7ixOI7C6VmbdS4ZNGOIgpnpkVSychEkIrK6WCZSCJev7v//8V5E46YfMJ1dwS4D7IkitT0mfKvBcVAqVlxBLUMC1ERdlV/4IImp17yx9G6NAaUurYsENjeIQv+qt7xwc7L7ZqZ9stw62VpvN/dahu3++uXOwtfvufG2n1VrbWNvZ3H59tt54s3Gyutl70zqsvzm37u8rE0VTm+dK/isBeTuj5YCGak7NVcKTqA8yXU3jGQoXrOAGofCNMqm6vghD8M1nMSASVCy4AmWchKGVDC4zgACJ6ZDx4aUWV8AzOBgnk+ALGZTah3ENQ5BFAzWbdrPptOqtdqfRcexGUW0hA/h8rQNQbMhprgeKagaawj6VUBE1EkkYEBrHQGWN7JkxFGHcD5MAyO9U+b+TF1T5wAPGhy+JkOR3nO538gL/ZV8br03dXQ6TCLgmTPH//ee/OnM3TQIY0CRM7W+G/QR8eBJhwKPKt1IFrYuiYUIWMf2ZhjkeAYnoDYuSKAeGWeXUFGnIhKBGsJ0Z3zi0pHwI6Zo7KLxr26RKKCdJHIPMGhqAMUVGVAYT98mDFcbCGORAyIhiFJBAleDqEaPlCwjBnO0c+6m4cuz7+4uKdVNVSRwLqVV1Ek3zqDBBOI7k2jb+m7XZUeL7oJRVsXzBNXCNTWgchyz1m5U/FLa7K0hEw3BvYIJUJpvo/wE+LlYsMdZpls53GTJ+pQo6fKSdgnDw6VYjCYMyIBmra4MYfmXdVywNURyiaQut+0KEQDlGnAKIPqSDXlQszXQIhTE43OgfTKRYwvUPJdI9Nsu/2jZLjf4rOPzV0aEl5Yr6qQf9UJJlVckPJpXCGAPBjyZWLMGHAH4ssR40MuifRdx0lQuWLWhzcV+xWFAmbj4TC4z6heJmvvUszC9VmiYGSVimWcVSIpE+XGYlZ9nkMdUaJKac3ofV6rld7VzcNRr3BbFoEEhMRTi16fxY0ZnW3ZMJsz6XrNArLQGKvez7StYxuKQlUj5QekTVqLSR2Ueg8fo0xIxf2miQcKztvtYU38akD2DF0h1HAQAfXe65tc1WZ2LwGZOWGLDEXBPjTNUrOMIrM9zqZGU/mUkg6gPuOD/tyFktWGhIpaRYWjIN0RMiwTJrLbPWMmsts9YXZq2Y3uI+sDRdTVX4FimKKgX6slyiyWPcyeLjfDOOrxSuIY3oAdOXNIxHlCdRff4rxzVLlo7DlEq+QarDPfjXL4L4+pQblcPhebNoYUUzUxllJ+Je3M9uyfYnWFsmtWVSWya1ZVJbWFLTo8sss13ic19fogUwlTxtX+Z+h6RX+eosl2fLj0z7d0mClfQI6ou3UH/+RTJpNnezj5spAKVZekpzGbFyx85Hebxam2n1UQ1nWn0bRZ+z3ikpcSr56ees8edNfVEsg/QoK4WOTGw6nISmZV20rIuWddGyLvqOdZECHjyxKHK8ZVW0rIr+PIv0xKooaxHRm2VBtLiCaN6Mj5VER2lUWtZDy3poWQ8t66EF1UP5XdYI5PCpb4ba36oG+kZaMv7VRcTzHiJMehpNCljOztt30sW5uEdMZstgHOoQtGRwDas8v6O+MY1c5m7sbIrIk0DqiNZI61h1V1ZG6Z3JqgalOeiaSm+H14QcrmTCqZXeq93tRmPrzfGmu3nmNje3d7d679fdN1sH28drqwfb3tHp/u75anP/7G1rd/V086Tueu/2jjdWMjf7R3qb+NefzOXNXx37J3M99le8bFq43fecojn1ltew622v3bTbzY7TcKrOR8TNb/49q7iO3ezUbbtV95puo+O5nXlxzSVehPfMhYzJlYsPRXRM7sR/pmKTfmplXqSHieszxs3VnWry0yOaP0xFXzwR/dQ8WWKw7JLHdv7nPIwgXat0tEIYtL4UGHnMmYbzLORMo1DXno3Zlms7nardqTrOseN1nWa3Xj8vuxbUtZxappKpRv8icPG+E1y8J8LFexJcvG8MF7zwDrIELc4T4TIGNhxpq+tUrPTXLJdXcPt1oqUDLB5rnv1dsObZVfd7YC2d56NY8+wp1txPY82MtrDQFLBZtLlPA1vx/cP0rUv+WsPyGo2a27HrLa+zCPQ0vEbd6bTcVtNzvXbdWRB6Hk6zqMRWNk8BPXOPH09sJaM9L3ocp+q0j51Ot9Hp1u0noKfZbtfqdrNRb9QXgZ6W12jWXbvtNRqe27YXhZ6H0ywKPWXzFNAz9/hx9JSM9szocRE9drvrel2v8cTY47XbrUanvQj0dLxOp+15jme3HcfreAtCz8NpFoWesnkK6Jl7/Dh6Skb7tujRMlE6ZBxKCiV3vlBy7SpCuHXs2l3H67ruHH5KDgqKb82tk6N16+ExgNVbP3m70zvprZ8fvG2+33y/2jhvrr53e/Wz9aPz/aNz7+hd42TXWz083dlrHhwdrr/bb7zf3jizKtnvNrtWx3U9r+XaXrPdqNVbrcaCivoHK1L/PnCtfye41h+Ha/3z4FpfAFxpUHj/1PW8p0FUQRimSHu1U98/bp6tn6+929vb2F0/ar7eO3Hd3puD7Tf7p27vVev08HRrq378une+tuqdn+3uNBpHp/iz+sEA5KWxjFNvNd2GW++YV2RhMDl/shpep2Z7ru3Y7cmz0vDaF8lwpKcdPbfWrnfspmsXHn7CsWaazfjXzJOvd7O/kB8taHNcNs+T/Kh0c1wy2o/mR2vrp283PK93erqzdnbW8vY2t9YO95uHq5tvNzffufv1/YPT0+bJ7t7bg1d7Zyet3u7JTv1ga96PnHbbceb8qN2o1zoNr9Vsu5/nRw23Zndc2220/yZ+hDtbx2t0Oq7TajYbi/KjB9MsauNfNk/Rjx4+fnzjXzLaYorvAPoPau/HHcpzu1772WunqbfVa526Y7dbi6jw5w4eFgPRkvONhUC0dJ4pROcfP1oylY32jPtD16naXtVu4tsFt9X1vCfsD+1art59+pMgczEHbjRwhQgwJzHpm89S6pBKfpqHFCJIMBKBHgm05hAmN0661vSM6W5KUnS/UjjoBnmdsxklMnzaQltlnC7HaTuyC3os5JXxifIRB4lOJDxlzNd5S8LzUS/wUHSQHu9mh6IZwwvaBKRKe9s1u2YSZBJFVN5OW5FYimsWGDohsnl8vE9W97eQ0iWgmiJfTJENK5u1RrY0YXwISqcsRBKqxnAptZfpGUsRJD4EpH9bNkTKbIT3GiYsNUAVQ1YkQXzBVRJB3pVeg6RDIAWCFyIhNBjK+boKTDZVIRlwpLcygszSQ6mUT6x/OxHolZCA7DpMGc0LevQlC4ZA+qDHABynT7Wd7bkvxR+GVCtkV0DGSBKmVYUE4APXkobs3xAQuPFHyNijKmYE4wwkjb5GogkrjxZEJX1D3jM9B1cVYsiEcIly5rLs+KmC3Ec5u9c18FyOYm9DLjXpWZtD1t8dCR+KC3rxInfPAK4hxBykZoJ6JvaKLyRUuQjg5d8KPb/x33g+XcbQR81dDwjINaPEPzncriBHmxRjBdLMIDjkjF8TWx+tv1WftHUgfLWihQjVigquFFpaEAkIp5TzTuBNjxumb3F8w2MXpwatkDEYEq0oAh4YHjw0FOU4MWFcaaABdoroFZLIBUwiMx+uIfL8KaOnWdZhwgIgqcf0QZGRGBuTBBHjyDIoSQ5xA8fcNjiF4dV6IWGQgtnovz7R9GeyForh1Abj8XhW+UnLaj8UwxVa5TCuqoRXMQuNoJrlj5eGyksJdBPqXw2lSHhABH/oDSl2pD9iGnydSBoSFqHPQ2RWXmS8XxH9A3kE09RB+kkUv6yR10hTyNN7aPg17YsEKcCMiGjAbL4JNEQASNNXIf4I/CuCrYv6G2KxHpp2aoAh06OkX/NFtJLZIf+fq7rSD0V/JaKMr6xvnG5s7+1v7fZqUfDSLNcaDIQEXPg+DBlHkrKfFRkLqZFajmlTTWZsiRgGmBEC/JFImdGMfOiWZFcEXxIISCB8Q5lmbNQlv/wyBhIgFaNGEkwhFRCZcI5C5IbCJUvDEEWmRx7QEN2lGCUmWPrllzQAgCEKpGF4a4Y2fS+vacgCo+DlXG4DhL4EoseCKEDSRo3Ow32QPAsqAfgiicPMPhGGYRZhlUW5NgDrC2PGkNE+C9HjsFcBXrUZ6KN3RZTTISjCEFxjXiExlRBUA2TCzOElBrOqilizyAQ9nDPriUENQ54YEI71Pnkxhp/DkBQ8C/nqkFHzN+sVjU06wOF+sya2Q4hg1QoyUnuDI5DXzFzeyBe5uLKmUVUMTCpjhvoFeeaoby5gZVx/udhFQL9G16PZ7cnZYm+2tIOIMvMUwlD8s/jsHt9G+8AVFOZajak/AuLW8L0eCxC7A2Y2bumTavpkOmMWTqh5anTKBlUr21uvNnaPNrBLbaSj0Ow7YqF0RHlhyvzmHIbM7O7cz4psTArlmRLibsrDt6R8/dNSvuav9eBGr8QhZebCrcHUXbZ/+pBvBBEB3Rma13wLdVGxRkJpbHt3hxngRIb39/h1yoeJG6uAKdoPP8aIWQTT83Ollhol3YhO2F+zrWd6J+dzlPvTUKI+YoWcDPYLjfAXoj99xEg5MezUSBf4QTK00mf6xIvD7CL2S/LNGJNLRc/f/fDbouS5SgXvN9euR0ANc9zkPc2q70NcVHqOoHXmPU1v49i6v/8/ZmcRyQ==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Account's Effects"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/accounts/{account_id}/effects"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint returns the effects of a specific account and can be used in streaming mode. Streaming mode allows you to listen for new effects for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known effect unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream effects created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./get-effects-by-account-id.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-effects-by-account-id.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-effects-by-account-id.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-effects-by-account-id.mdx b/docs/data/apis/horizon/api-reference/get-effects-by-account-id.mdx
new file mode 100644
index 000000000..f51e64d43
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/get-effects-by-account-id.mdx
@@ -0,0 +1,12 @@
+---
+title: "Retrieve an Account's Effects"
+openapi: "openapi/horizon/bundled.yml GET /accounts/{account_id}/effects"
+---
+
+<Tip>
+
+**Supports Streaming**
+
+This endpoint supports streaming. To read more about this, visit the [streaming section](/docs/data/apis/horizon/api-reference/structure/streaming).
+
+</Tip>
diff --git a/docs/data/apis/horizon/api-reference/get-offer-by-offer-id.ParamsDetails.json b/docs/data/apis/horizon/api-reference/get-offer-by-offer-id.ParamsDetails.json
deleted file mode 100644
index e48393632..000000000
--- a/docs/data/apis/horizon/api-reference/get-offer-by-offer-id.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"offer_id","in":"path","required":true,"description":"A unique identifier for this offer."}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-offer-by-offer-id.RequestSchema.json b/docs/data/apis/horizon/api-reference/get-offer-by-offer-id.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/get-offer-by-offer-id.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-offer-by-offer-id.StatusCodes.json b/docs/data/apis/horizon/api-reference/get-offer-by-offer-id.StatusCodes.json
deleted file mode 100644
index 1b02eaa06..000000000
--- a/docs/data/apis/horizon/api-reference/get-offer-by-offer-id.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"offer_maker":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","offer_maker"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"seller":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"selling":{"type":"object","properties":{"asset_type":{"type":"string"},"asset_code":{"type":"string"},"asset_issuer":{"type":"string"}},"required":["asset_type"],"title":"BaseAsset"},"buying":{"type":"object","properties":{"asset_type":{"type":"string"},"asset_code":{"type":"string"},"asset_issuer":{"type":"string"}},"required":["asset_type"],"title":"BaseAsset"},"amount":{"type":"string"},"price_r":{"type":"object","properties":{"n":{"type":"integer","format":"int32"},"d":{"type":"integer","format":"int32"}},"title":"Price"},"price":{"type":"string"},"last_modified_ledger":{"type":"integer","format":"uint32","title":"last_modified_ledger"},"last_modified_time":{"type":"string"},"sponser":{"type":"string"}},"required":["id","paging_token","seller","selling","buying","amount","price_r","price","last_modified_ledger","last_modified_time"]}}}}},"title":"Offer"}]},"examples":{"GetOfferByOfferId":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/offers/165563085"},"offer_maker":{"href":"https://horizon-testnet.stellar.org/accounts/GCM4PT6XDZBWOOENDS6FOU22GJQLJPV2GC7VRVII4TFGZBA3ZXNM55SV"}},"id":165563085,"paging_token":"165563085","seller":"GCM4PT6XDZBWOOENDS6FOU22GJQLJPV2GC7VRVII4TFGZBA3ZXNM55SV","selling":{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"},"buying":{"asset_type":"native"},"amount":"26.1075388","price_r":{"n":1449156725,"d":84642346},"price":"17.1209423","last_modified_ledger":28412042,"last_modified_time":null}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-offer-by-offer-id.api.mdx b/docs/data/apis/horizon/api-reference/get-offer-by-offer-id.api.mdx
deleted file mode 100644
index d6ad89f2d..000000000
--- a/docs/data/apis/horizon/api-reference/get-offer-by-offer-id.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: get-offer-by-offer-id
-title: "Retrieve an Offer"
-description: "The single offer endpoint provides information on a specific [offer](https://developers.stellar.org/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools#orders)."
-sidebar_label: "Retrieve an Offer"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlWW9TGkkT/ypdcy8SUwsogkl49Wg0xItRI2oSjWUNOw07cXZmMzMLchTf/ameZWFRcvHuVVL3Corp//3rnulmyjwfOta5ZieDAVrHbiIm0MVWZl4azTrsPEFwUg8VgiESQC0yI7WHzJqRFOhA6oGxKScGMBo4uAxjOZAxXAeWm+eJ95nrNBoCR6hMhtbVnUeluK0bO2wIE7uGQm51Y5BrwVPUnivXUPJ7LoX0k5rRtTlDzQm8ry1PMmOU+8NYgdZt1FnESHyw5VCwDuuiD57tTcLHoWARy7jlKXpyt3M9ZZqnyDosmHoriUCS4xn3CYuYxe+5tChYx9scH0ZnF3Itv+cIUqD2ciDRwsBY8Il0RbzqbHZDUlxmtEPHOlPW3Nykj1VJvTyO0TkWsdhoj9oTCc8yJePgTeObI7opc3GCKQ+nSp0Mggt+kgUX+t8w9uShpSh4Wei7VVLfhW9/T+dQDX5OlVisUjlvpR6yiBUYYB1G2tgsYh7TTHFPoVtQ941RyDWbzaqRvS6E3kTMS6+wIkPjvf/FTMosjn4pk2ZEVv50FFI9i36KCUz7KMSK2h+QWoyNFVX8cGv5hOrEY/oEXP3G+CuaQsrv0P5Slj0gCpFbtfZmFjEp1plTSpIiwJkPpR7eenOH+jH1LCLZasX7haCMe4+Wmlf3erd2tVl7fTNtt2cVFVwIS01tLobYfhpF7hz624JmjTnFcWzE3x1L5/J1Nj+MW0VXJcR73OEunZDAfj75Hc3mqcm1X6srszLG2yfguYoHqT0O0VbRLLXfbpJA8SS6SpM6JQsWpqw1UnHnb1Mj6EoVtwrFcCUwa9TkhZ5KpawT8Ui0l+l6C4oL+wnZkMWbolJGi6JZwn4BpEVqloko4/ADr9dafDNb7fvhdcNmVPV4z9NMFSl8/PzpTNmIqxxXG3PZeosWxsr3WmKs/MvomkfnNfqVR1toNq6xtdNu72xvvmqvaZf/QBqPY4qKa3TffGidnu983r/a+3RycnC839t5e3LRbHb//Hj05+lls/vm5eXZ5eFh6/xt92pvd/vq8/GHdrt3GdJCDW9h0MPexpamLrsa+9f6VlpatfpZbFFIf8tVlnCdpy22Wv7sorfPHpY86+5fvP/QvejuX318v/Pl3Zfd9tXO7pdmt/V5v3d12rva7n1qXxxv755dfjjZ+dg72/902v5ydPB5tUet2KG5lyOsdgPW3Klvbb5sb796xVYagWadrVbr9VZ752WzHSr6VWun1dxu7SyrlG29rG81N1+3mts/gmqn+aq11dxsNddXmc6Vms3myE3RJ4ae6EP0xWWSsA4rYTUtn+OzEGg7Kl/ruVVPgxRbN8mcF3RwjH5s7F14KK2XOMh9bvEpMt+WlKBLqTc0QwxM6B3zAn1XyGURI1cK7s36Zn2L/MvTlNvJkmo5W3EN787PT2H39BC8AcE9B6nBJwi9wq5Sax0OPUg9ROeJTYDFWgicC9SBM7NG5DEK6E/WiSDJnOaXFHzCPUgHyB3NNN5AbLTLUyxZ+QgtHyJURhSwqALkiJxoMrShPesYa8ZK1B5FYYjFzKKjMY8YHeSuMKo06I2xWIdzmqLI84offSvFEKGPfoyoSX3h7SrnqTV0pTlQ8g5hzJVC7yIQGKP2liv5FwrA+zjhFLAoSAi1A0VBBougzIY34PJ+Kj14y7XjcTA6gu852gmlaN69oM8VORuBseC8RZ4CjlCXdlS5SeiSs/4IWf91JFxXE/rTDcLc7EZsLNa0Ebjxn0LPV/1Vl+pirqGPdISOYjmSHOKLs6MIOPStGTu0QYPRtNEJUVnEurf/3j1tW+Np7dJw4s5RpA1YJDgFabGh58e99BOSPzG5JbRRQCMYI9A4maaoBR2FQHFNikFq55ELYkr5ndRDENJi7EMOY66UC36GtA5zKRCKiumjg8SMQ0hEKrV0Hi2UEA9wLGNDKijE8NzioABz8H9/4ekz2FNmuIzBeDxedX5BWesrM2zwmsZxzeWaVlQ+wdr8/tgIayBnqEx4fDe0JteCtmMPqqHAjo0T6TH2ueUKZEo1j2nIfMiQdJDyb8bC/OqAfp5mG3V4a+zK8o33Te5hbiIFcK5vAQ0jsM8dRhAnGN8BUVf9J5XQpdAuAzCUPsn79dikjXkcys/S1UZfmX4j5VI39g8uD45OTg+Pu/VUbIR07eHAWKTE93EodQTSP3MwNtYnYFH6sKzTw2AHtQEZjMA4MSjK/nZNZQnHRvybRgDCxHlaNpgOvHgxRhAGtPG0yzTWIdhcazKiDBSlrGhDHAgxgisql2qXWGDpxYuiAWDYenKlJkF04L0dcSVFcPD20d2GBH2L4McGHNJS0lPx6BitnjcVgbHJMzWPT0ptWKaZsZ5rHwDWNyGMSvK+VFRxxFWBV30F+lRdKdd8SEtbAtdYR5Bxi6ImzFgv4GUGq66azMs0ND3SOeekpkYtzwxAIwoHz8f4TCmoVJZ0wB1w+Mre8CxcByTuK1vEjiBCExva1J0MemhHxUuzTHI1s4GoZgbhKivGJdqU8jhMufMlbml2FdBvqfRC8ln04LG3+rTDlMtwikqZ/1XPaGqUMWqHFV27GY8ThGZ9k1Zhi/3v4qRWnCw1ztsJD6fBp7lQ1zg6fHNw3DsglnriUxWmmcw4n3JdUXmG3kochZZZTHwPng3T5fb499vcz8cWj/e+kSkuNcU9hG86Hw+uiwmTtuSdxb7+JmKJcZ5Op1NqbxdWzWb0c7hhWef6JmIjbiXv00v8esqEdPRdsM6AK/dwqV+N4fOz+aC/AU9Z9f/Ah3JtqmlpOp++GYvYHU6qfzyE6T1BLghE19P58W4cY+YrjI/+FKBxYzFNdQ/O2Wz2fy0uCgU=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Offer"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/offers/{offer_id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The single offer endpoint provides information on a specific [offer](https://developers.stellar.org/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools#orders).
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./get-offer-by-offer-id.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-offer-by-offer-id.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-offer-by-offer-id.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-offer-by-offer-id.mdx b/docs/data/apis/horizon/api-reference/get-offer-by-offer-id.mdx
new file mode 100644
index 000000000..6a5536a14
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/get-offer-by-offer-id.mdx
@@ -0,0 +1,4 @@
+---
+title: Retrieve an Offer
+openapi: "openapi/horizon/bundled.yml GET /offers/{offer_id}"
+---
diff --git a/docs/data/apis/horizon/api-reference/get-offers-by-account-id.ParamsDetails.json b/docs/data/apis/horizon/api-reference/get-offers-by-account-id.ParamsDetails.json
deleted file mode 100644
index c8a2ddd7f..000000000
--- a/docs/data/apis/horizon/api-reference/get-offers-by-account-id.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"account_id","in":"path","required":true,"description":"This account’s public key encoded in a base32 string representation.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-offers-by-account-id.RequestSchema.json b/docs/data/apis/horizon/api-reference/get-offers-by-account-id.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/get-offers-by-account-id.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-offers-by-account-id.StatusCodes.json b/docs/data/apis/horizon/api-reference/get-offers-by-account-id.StatusCodes.json
deleted file mode 100644
index 6356e0abe..000000000
--- a/docs/data/apis/horizon/api-reference/get-offers-by-account-id.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"offer_maker":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","offer_maker"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"seller":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"selling":{"type":"object","properties":{"asset_type":{"type":"string"},"asset_code":{"type":"string"},"asset_issuer":{"type":"string"}},"required":["asset_type"],"title":"BaseAsset"},"buying":{"type":"object","properties":{"asset_type":{"type":"string"},"asset_code":{"type":"string"},"asset_issuer":{"type":"string"}},"required":["asset_type"],"title":"BaseAsset"},"amount":{"type":"string"},"price_r":{"type":"object","properties":{"n":{"type":"integer","format":"int32"},"d":{"type":"integer","format":"int32"}},"title":"Price"},"price":{"type":"string"},"last_modified_ledger":{"type":"integer","format":"uint32","title":"last_modified_ledger"},"last_modified_time":{"type":"string"},"sponser":{"type":"string"}},"required":["id","paging_token","seller","selling","buying","amount","price_r","price","last_modified_ledger","last_modified_time"]}}}}},"title":"Offer"}]},"examples":{"RetrieveAnAccountsOffers":{"value":{"_links":{"self":{"href":"https://\thorizon-testnet.stellar.org/accounts/GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K/offers?cursor=&limit=10&order=asc"},"next":{"href":"https://\thorizon-testnet.stellar.org/accounts/GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K/offers?cursor=164943216&limit=10&order=asc"},"prev":{"href":"https://\thorizon-testnet.stellar.org/accounts/GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K/offers?cursor=164555927&limit=10&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://\thorizon-testnet.stellar.org/offers/164555927"},"offer_maker":{"href":"https://\thorizon-testnet.stellar.org/accounts/GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K"}},"id":164555927,"paging_token":"164555927","seller":"GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K","selling":{"asset_type":"native"},"buying":{"asset_type":"credit_alphanum4","asset_code":"BB1","asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN"},"amount":"214.9999939","price_r":{"n":10000000,"d":86000001},"price":"0.1162791","last_modified_ledger":28383147,"last_modified_time":"2020-02-24T22:58:38Z"},{"_links":{"self":{"href":"https://\thorizon-testnet.stellar.org/offers/164943216"},"offer_maker":{"href":"https://\thorizon-testnet.stellar.org/accounts/GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K"}},"id":164943216,"paging_token":"164943216","seller":"GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K","selling":{"asset_type":"credit_alphanum4","asset_code":"BB1","asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN"},"buying":{"asset_type":"native"},"amount":"24.9999990","price_r":{"n":32224991,"d":2500000},"price":"12.8899964","last_modified_ledger":28394149,"last_modified_time":"2020-02-25T15:49:57Z"}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-offers-by-account-id.api.mdx b/docs/data/apis/horizon/api-reference/get-offers-by-account-id.api.mdx
deleted file mode 100644
index e1288a8bf..000000000
--- a/docs/data/apis/horizon/api-reference/get-offers-by-account-id.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: get-offers-by-account-id
-title: "Retrieve an Account's Offers"
-description: "This endpoint represents all offers a given account has currently open and can be used in streaming mode. Streaming mode allows you to listen for new offers for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known offer unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream offers created since your request time."
-sidebar_label: "Retrieve an Account's Offers"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWulyGzcSfpWu+REfxVskJbIqtav7sCzJlnzJVsngoMlBhAEmAEYUo2JVXiOvlyfZaswMOZRo2c5mEydZ/aHIARrdja/vuQ0cG9mg/z5YD0OdKmeDi0rA0YZGJE5oFfSDs0hYQMUTLZQDg4lBi8pZYFKCHg7RWGAwEteogGVUIGIWwtQYVE5OQCf0SHEImYIBQmqRg1BgnUEWCzWCWHOswenCd6KvxxYmOgWnQQrrUMFQG1A4Lg6mr44YLE5mFlyEE2AGgXGOnPa6COHUoZTMgEQ+QlOD/SGETMplnFRgTxvxk1YwFlKCdcw4YM6TQWakQOvgSumxytiAVEm0pIUwNVYbEBYsugpRHkcijCBkFkG4Mr2h0TG4iLl8Uw02JrTLERd0Uk7rmskUSQilxxWvDNJixnChhdAgc8jBChUirTFg8MeU2HQixlpQCXSChtGN7vOgH+yiO/ZbNyb5xe/zoBIkzLAYHRqCxG2gWIxBP8hVeyloiSBIJMxFQSWgM4RBHvSdSXEpbvK9v/78i4UkHUgRwhVOAFWoeaZ6BgNmcaVFIpHoM4B5bol1G0YYs6B/G7hJQgxlK4NKgDcsTiT9tLv1/MWLo4Pn7VeHqy/217vdk9WXrZPzvecv9o/enG88X13d2N54vne483arc7D9an1v92D1ZfvgPJhOKzNBM40XQv6YopksSDlk0t4Tcx1UGg/QZHfpjcTSdTGwCYZiKEKQOvTCZOKGWkoM/Xc9BIM20cqi9QYiSEselDk8EBI2Emp06fQVqhwMeggMDIba8KX6EcrhCE1ZQd1uo9ttrrZX13qdXrPRKYutDcevl5qjFSPFCjmIVU9oDvqMQws20qnkwJIEmanBsadhQahQphzhI7PhR3jMbIiKCzV6AtrARzruIzymj/xnb7KZrZtRGqNyIKz69edfXG5sDjgOWSoz/Xuyn4GPSmPyfcyGQSZgcFFWjBSxcF+pmLMIIWY3Ik7jAhj+ljNVGHSpUchrQOs8fW/OhqkRZnfeJOZbjQZUgSlIkwRNvtADTFiImOEz8yk8FTnCBM1Qm5iREzDIrFb2AaUVF4j8nu6ajS/FVbMxnV5UgpuqTZNEG2erM1daeIUZwolSq9Ggj0WdnaZhiNYGlSDUyqFytIQliRSZ3dR/sLTutsQRk/J46J1Uzpse/IAhXVZiyNU5kZ13KYW6siUZPrHOohx+flVkcLgMSF7rziNGXQXTSuAwTiSptrR6oLVEpsjjlED0PiN6UQmccBJLNBTeuG+MpcTg9TfF0pSWFT8d+qsm+/0MJjAeIKUGnxclt9vSQmYMIzcgHMZfgKu/MP58bnEZsys03xRndxZ5zS1yezGtBIIvY6egJLiHcym03l89rRBtuSD9jFDCnENDzmv3/Xr1vFHtXdx2OtPSEYxzQ04tJ+Md4ue0yKxFd5mtWcJO9phc/wOPhbXpMp7v6q10VknFG8ziOj0hgoN08ldkm8WUci49KzEixMsvwHMZD/OwN0OzUG6lRQT5F60rOakT4mDGylImJbPuMtZcDAXyy6xeefiYNDunZCnLSNwjTbXBctz7gP0FtyGyqqFkRjOjmcN+BqTZ1cwvotDDJ6ReyvHFdNHv+0ommJLV53mJv8KX6IzAa1xXRW2blTz0zOfRi/658MCZJwsi5xLbr9c/uCjLsKoOrVPoajYrJGvajOp5eWPru1srmwfvXp2dr7/rHrzYaW9u73fPV1+/6Rx3Xx/tPjs/23j3anvz7PjgZHvrbGN1v7V3fnqy33pWzyq4f2Wlx/ff+Uzv+2bjO59Lf0+ZaSkV+FN5a3bbvfZKq9n9BJNFcvBnM9npdHqt1btM+uyeULMQ/Wfx/f1/DYWMj/qMgSUh9I/VjJeWwuCMpbsRL5gzO491wW8+byHQlWNCQGXiNS6GlIUFoUEu3CWTScRUGreDxagRbGw0g7uRItjd6hx09w53Ot1u9217/fzwbOfs7eG7dvegc/pmdfvty2cbh9vvTg5OVlZOV1aevz3ffd3dfLNzVI4RQavZrvXob6UXLMQHRcVN9ufd/FrX/9+cu+6gUWs2u63VXvNT7qvfWltZW2m2V5d73qDVaDWqjVa11T5rtfqdtf7K2rlPYH83LGYW+01hMWNpGRZzZv+3WPzDofYJyM9tYo7FHIq9xj0orrRarXav1/RQbHU8FEtIbLZqa2u9Xq/bfgiKvXaz3fscFDtnzU6/3et3Vs8ppuZ/FFodKkudG+8tr3AS9JfX/ZUivFL9T92BGF2kqe04QpflzlHQD+aoup13GKc5dv0FmuuiE5kaWQLrA1ANlvVjzrJ1cIRurM2Vt7DlFIepSw1+Cc2dYiWoguoFdYqG2mdNeWqSd2dIJWhstrtRa9QIYjaNY2Ym81WQGH0tuG8Fwt7Z2Qmsn+xTO4Yzx6jXU25j56fWYN+BUCO0LusgGqx6xfk2eLYzMZqnIXIYTJaRyLqSlEvOOkzIrKCOpoZQK5vGWGxl12jYCKHUnAGD0kO5aLSXulBVbQQq6kx7RhZbuzabAwwmM4Y2tUHqjAnrJS/JMTCCjxAG6MZIs4QkyaRd3HliNCXzFqS4QhhTd9/ZCnAMUTnDpPgJOeBNGFG3zVY8BW+TkBm652jWUXMabDrwjTfDlGW+ZWsr4BuBdEXFyGHAJAlbob5l3pfHaz8h8XyUd/vG8Gxn7R6y/ulIeF++0IvHhXlyvEZJ5ZldCEs52/VQG6wqzfHJPwo9H9QHVRyXT9aYb6Qih2vBIHz18rBC8xWjxxaNP0ErLLr1M12fbj2zn9U116GtO62lrVt+ZUnTGgwSnLJplabC60a4CdH3I6gkU2gFxugb4HGMivsJFimKKToYhLIOGadNMbuiARAXBkPn75AGdNbL6a91lAqOkFnMAC1EeuxVwmOhaDpooIC4h2OhGzrC98QfGxxmYPbyb80kfQQbUo/mOhiPx4vCz1ZWB1KP6qyqcFy1qapSFIqwmsePJ74NbzWZCQuvRkanioNWd60hw44JI+EwdKlhEkRMNo+xv3md9+xj9gNNALPQAYM0Tp7UYIcGjCqr/elnNtApte89i6TA/LwZNDRHGrFVIIwwvAJaXZbfDwV2SbVzBYyEi9JBLdRxPddD8VmIWh9IPajHTKj61vbr7cPjk/2j3VrMn/jr2sChNkgXP8CRUDRgeGRhrI2jsZBwfhaZzznJDQjPBIaRzqYanj8ySzjS/Lc4AuA69OMOr6M+PH06RuA0RHU0y9bGIphUKWKiUBRdWeaGGM1oFWeSzKXsJWZYevo0cwDoh3xMyokn7fdeXjMpuBfw8l5sQ4K+QXBjDRZp4OrIeFSIRuVOhWOo00Tm+onJDYuYkiymnAfYQHs1SsEGQpLF0a4SvGoL0CfripliI7QgCFxjVYGEGeRVTiPsAl56uCiqTpyIvdOjM/Od5NTI5ekhKERu4fEYH0kJJcuiWRPNwj8Emyzx4YDIfQhmuiOIUK8KTWyPh6dorrMktrjk8s36RVU99KEsaxTRjIiFvh+Sz+kKtsuA3iHT85cfVO4ke4upHcZM+Kcopf53+Rn1y0SIymLprPWEhRFCq0Y5uuCE3aHwNUL2pJo9mZ+YuxPmn3qZcqK2fri/uX10uk1bapGLpa+SEm1dzFTpyKKRRS4zb2U9snBc5MkLGcTtfIT2/xc3/hYvbuTlosMbV08kE4pw6eF1m1dS74s3NAgN/YW3NfJi6qISRNo6Wnp7S7HglZHTKf2cTbWpxOLCsoH81Fy7jKs//42HpTrJKtLZOxx5DRr4au9rhPvLvNjwgBaKVzp+oxL+Ri8xPKCk4vWOuZIu6IsRpKWvtInHL/OpyBP43d57Wsp6MYZWkzLnhUgl4/fzkAgZAWHesFkPQ0zKQt97zWKhYbO7fRZMp/8BUYvoIw==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Account's Offers"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/accounts/{account_id}/offers"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents all offers a given account has currently open and can be used in streaming mode. Streaming mode allows you to listen for new offers for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known offer unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream offers created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./get-offers-by-account-id.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-offers-by-account-id.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-offers-by-account-id.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-offers-by-account-id.mdx b/docs/data/apis/horizon/api-reference/get-offers-by-account-id.mdx
new file mode 100644
index 000000000..c769055e4
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/get-offers-by-account-id.mdx
@@ -0,0 +1,12 @@
+---
+title: "Retrieve an Account's Offers"
+openapi: "openapi/horizon/bundled.yml GET /accounts/{account_id}/offers"
+---
+
+<Tip>
+
+**Supports Streaming**
+
+This endpoint supports streaming. To read more about this, visit the [streaming section](/docs/data/apis/horizon/api-reference/structure/streaming).
+
+</Tip>
diff --git a/docs/data/apis/horizon/api-reference/get-operations-by-account-id.ParamsDetails.json b/docs/data/apis/horizon/api-reference/get-operations-by-account-id.ParamsDetails.json
deleted file mode 100644
index c5428eda0..000000000
--- a/docs/data/apis/horizon/api-reference/get-operations-by-account-id.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"account_id","in":"path","required":true,"description":"This account’s public key encoded in a base32 string representation.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}},{"name":"join","in":"query","required":false,"description":"Set to transactions to include the transactions which created each of the operations in the response."}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-operations-by-account-id.RequestSchema.json b/docs/data/apis/horizon/api-reference/get-operations-by-account-id.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/get-operations-by-account-id.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-operations-by-account-id.StatusCodes.json b/docs/data/apis/horizon/api-reference/get-operations-by-account-id.StatusCodes.json
deleted file mode 100644
index 183733a17..000000000
--- a/docs/data/apis/horizon/api-reference/get-operations-by-account-id.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"oneOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"create_account"},"type_i":{"type":"number","example":0},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"starting_balance":{"type":"string"},"funder":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","starting_balance","funder","account"],"title":"CreateAccount"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"payment"},"type_i":{"type":"string"},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string"},"asset_code":{"enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","asset_type","from","to","amount"]}}}}},"title":"Payment"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"path_payment_strict_receive"},"type_i":{"type":"number","example":2},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"},"path":{"type":"array","items":{"type":"object","properties":{"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}}}},"source_amount":{"type":"string"},"destination_min":{"type":"string"},"source_asset_type":{"type":"string"},"source_asset_code":{"type":"string"},"source_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","from","to","amount","path","source_amount","destination_min"],"title":"PathPaymentStrictReceive"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"path_payment_strict_send"},"type_i":{"type":"number","example":13},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"},"path":{"type":"array","items":{"type":"object","properties":{"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}}}},"source_amount":{"type":"string"},"source_max":{"type":"string"},"source_asset_type":{"type":"string"},"source_asset_code":{"type":"string"},"source_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","from","to","amount","path","source_amount","source_asset_type"],"title":"PathPaymentStrictSend"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"account_merge"},"type_i":{"type":"number","example":8},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"into":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","account","into"],"title":"AccountMerge"}]}]},"examples":{"RetrieveAnAccountsOperations":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/accounts/GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA/operations?cursor=&limit=10&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/accounts/GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA/operations?cursor=120194466505179137&limit=10&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/accounts/GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA/operations?cursor=120192344791343105&limit=10&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120192344791343105"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/ef0fe04ac3c7de7228ca2598886059868ad05c224a041e8b2d9ee2a8a9dd6894"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120192344791343105/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120192344791343105"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120192344791343105"}},"id":"120192344791343105","paging_token":"120192344791343105","transaction_successful":true,"source_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","type":"create_account","type_i":0,"created_at":"2020-01-29T19:43:59Z","transaction_hash":"ef0fe04ac3c7de7228ca2598886059868ad05c224a041e8b2d9ee2a8a9dd6894","starting_balance":"2.0000000","funder":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","account":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120192370561220609"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/c1cb850f413e4038c4120bd9badc07bb8ef85a46649a4d5c9c16e578a2d30589"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120192370561220609/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120192370561220609"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120192370561220609"}},"id":"120192370561220609","paging_token":"120192370561220609","transaction_successful":true,"source_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","type":"payment","type_i":1,"created_at":"2020-01-29T19:44:36Z","transaction_hash":"c1cb850f413e4038c4120bd9badc07bb8ef85a46649a4d5c9c16e578a2d30589","asset_type":"native","from":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","to":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA","amount":"200.0000000"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120192452165550081"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/0e6bc30f2b2f50ca0ecedef5a527309c74964e7daa6018976cd2c686c5df4be3"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120192452165550081/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120192452165550081"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120192452165550081"}},"id":"120192452165550081","paging_token":"120192452165550081","transaction_successful":true,"source_account":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA","type":"change_trust","type_i":6,"created_at":"2020-01-29T19:46:20Z","transaction_hash":"0e6bc30f2b2f50ca0ecedef5a527309c74964e7daa6018976cd2c686c5df4be3","asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","limit":"922337203685.4775807","trustee":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","trustor":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120192477935251457"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/ec4116595bdfa8c1039c40af425e497c91fcf387c2a2a0cfa1f3bf64733f1f23"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120192477935251457/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120192477935251457"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120192477935251457"}},"id":"120192477935251457","paging_token":"120192477935251457","transaction_successful":true,"source_account":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA","type":"change_trust","type_i":6,"created_at":"2020-01-29T19:46:55Z","transaction_hash":"ec4116595bdfa8c1039c40af425e497c91fcf387c2a2a0cfa1f3bf64733f1f23","asset_type":"credit_alphanum4","asset_code":"NGNT","asset_issuer":"GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD","limit":"922337203685.4775807","trustee":"GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD","trustor":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120192490820268033"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/81f2b857cb47d7c63ca12e2ec3466f6f17b4990bf492ef752c9c6d2035ca11ff"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120192490820268033/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120192490820268033"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120192490820268033"}},"id":"120192490820268033","paging_token":"120192490820268033","transaction_successful":true,"source_account":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA","type":"change_trust","type_i":6,"created_at":"2020-01-29T19:47:11Z","transaction_hash":"81f2b857cb47d7c63ca12e2ec3466f6f17b4990bf492ef752c9c6d2035ca11ff","asset_type":"credit_alphanum4","asset_code":"EURT","asset_issuer":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","limit":"922337203685.4775807","trustee":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","trustor":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120192499410071553"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/34b28df891c6a09968a2f0a6b410300b08b09c5f58cd12fe64fda59d29688f6e"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120192499410071553/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120192499410071553"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120192499410071553"}},"id":"120192499410071553","paging_token":"120192499410071553","transaction_successful":true,"source_account":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA","type":"change_trust","type_i":6,"created_at":"2020-01-29T19:47:22Z","transaction_hash":"34b28df891c6a09968a2f0a6b410300b08b09c5f58cd12fe64fda59d29688f6e","asset_type":"credit_alphanum4","asset_code":"BB1","asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","limit":"922337203685.4775807","trustee":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","trustor":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120192508000047105"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/12a8e8f11a697ee06a092eb0700c2b713fe07d29ffab190988d5bb248caf1917"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120192508000047105/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120192508000047105"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120192508000047105"}},"id":"120192508000047105","paging_token":"120192508000047105","transaction_successful":true,"source_account":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA","type":"change_trust","type_i":6,"created_at":"2020-01-29T19:47:33Z","transaction_hash":"12a8e8f11a697ee06a092eb0700c2b713fe07d29ffab190988d5bb248caf1917","asset_type":"credit_alphanum4","asset_code":"CNY","asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","limit":"922337203685.4775807","trustee":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","trustor":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120192542359883777"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/36b9c9aa3c4a22a1e8274f69b1bbfdd5764e55b80804a8d9c6b35c14e4147580"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120192542359883777/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120192542359883777"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120192542359883777"}},"id":"120192542359883777","paging_token":"120192542359883777","transaction_successful":true,"source_account":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA","type":"manage_buy_offer","type_i":12,"created_at":"2020-01-29T19:48:16Z","transaction_hash":"36b9c9aa3c4a22a1e8274f69b1bbfdd5764e55b80804a8d9c6b35c14e4147580","amount":"3.0000000","price":"18.1088911","price_r":{"n":181088911,"d":10000000},"buying_asset_type":"credit_alphanum4","buying_asset_code":"EURT","buying_asset_issuer":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","selling_asset_type":"native","offer_id":"0"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120192568129794049"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/f0362887d2b9b853e7b464b174adfceb4c73ffb6a45e10b7cb3bff9cfa808340"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120192568129794049/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120192568129794049"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120192568129794049"}},"id":"120192568129794049","paging_token":"120192568129794049","transaction_successful":true,"source_account":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA","type":"manage_buy_offer","type_i":12,"created_at":"2020-01-29T19:48:54Z","transaction_hash":"f0362887d2b9b853e7b464b174adfceb4c73ffb6a45e10b7cb3bff9cfa808340","amount":"200.0000000","price":"0.0459893","price_r":{"n":459893,"d":10000000},"buying_asset_type":"credit_alphanum4","buying_asset_code":"NGNT","buying_asset_issuer":"GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD","selling_asset_type":"native","offer_id":"0"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120194466505179137"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/a470f40ba0c1fd17cb957e0b438bd873b110ffb808b8133a5144cea3f5a66d0d"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120194466505179137/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120194466505179137"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120194466505179137"}},"id":"120194466505179137","paging_token":"120194466505179137","transaction_successful":true,"source_account":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA","type":"change_trust","type_i":6,"created_at":"2020-01-29T20:31:28Z","transaction_hash":"a470f40ba0c1fd17cb957e0b438bd873b110ffb808b8133a5144cea3f5a66d0d","asset_type":"credit_alphanum4","asset_code":"CNY","asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","limit":"0.0000000","trustee":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","trustor":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA"}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-operations-by-account-id.api.mdx b/docs/data/apis/horizon/api-reference/get-operations-by-account-id.api.mdx
deleted file mode 100644
index 36fe3e579..000000000
--- a/docs/data/apis/horizon/api-reference/get-operations-by-account-id.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: get-operations-by-account-id
-title: "Retrieve an Account's Operations"
-description: "This endpoint represents successful operations for a given account and can be used in streaming mode. Streaming mode allows you to listen for new operations for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known operation unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream operations created since your request time."
-sidebar_label: "Retrieve an Account's Operations"
-hide_title: true
-hide_table_of_contents: true
-api: eJztXfly2zjSfxUU/5hJpmSZ9+Gqqf0kH7IT+YjlO+PygEBT4piHFqDseFOu2tfY19sn+QogKZGy5MS27Dizzj+uCFd3o/vXDRLs/qpkuM+Vlc9Ki5B0lGRcOW8oFDhh4TAL00RZUQ4GIUeQ0GEaJhliMGTAIck44iNCgPNgFKF0CAyL/hwFKUMY9cMrSBDOJ0U4oYjgBPmARhwoChPEMwY4DpM+ilMKTdSr/R/hKEqvObpJRyhLURTyDBI5dQLX06tlgsDxUhxlA7hBmAHClAIV47MBoF4GUYQZioD2gTXRVoAIjqJZ1DTQZsrCf6UJug6jCPEMswzhTE4DmEUh8AxdJul1MiEFjZIIOEcYkRHjKUMhRxyyhpj9ehCSASKYAwqz6pwBS2OUDXBWDGqi9o0YlQlKxGrFXFc4GoFgJEmvG1IoQpo50VVpEAY4A4p4mBAQ/Rhi8M+RIDcLY2gqDWXce4sqK0oHst3x8PZNoQRbVGkoQ8xwDBkwoR5flQTHoKwohZgvQtElFOoxxNlAaShinZABVVYyNoKZOlSM/e+//8PRcORHIUGXcIMgISnNtwEjH3MwdMGaEMFY2SSBgnxOBhBjZeWrkt0MBUF5T6WhwBccDyPxU2dt+9OnnQ/b5mHX+bTVsu09Z1/fO9vc/rS1c3zW3nac9np7e7O7cbJmfVg/bG12Pjj75ocz5fa2MWY0l3zJ5D9HwG5qXAY44nfYbKFkFPvA8j2VBsPFtmHEh0DCICQoSkmuL5JdkkYREPn/NEAM+DBNOHBpMKGQklTQQk0ADXE/TPoXWXoJSaEUaYAwYkBSRmfKJ0wy6AOrCsi2VdvWHNNxPcvTVKvKdsooPJxrCjzsJ7jkQ5AqJ5oof04hR3yQjiKK8HAImDXR7jBX3DAh0YgC+hNz8id6hzmBhIZJ/z1KGfpTLPcneif+FD9L883tnvVHMSQZCnny33//JyuMLkMUAjyKcvnLab+hPskoFjiIOVFyBpXzqmCiMA6zBwrmYAAoxl/CeBSXiiF3ORcFg2zEEqBNJPrJ+aVZM5z0Id9zTRCvqypaQjhBo+EQWNFRKljI0QAzOjafErUEKA6BBSmLsQACBpinCb9HaOUGAr0jO039Xr3S1KrAii29CHAYAX2g5HqQSdxmOeyV6pHPVUW8MBFWI2i9q0xytLAkucRMLvw0jQAnk/2X4CX713b/rzRMHssCTjgmOWUVVoSN1NoKJ1EgOGAyGJtSjV3xSwkUTeX2vKF8WeKj4TBlGV8a+7EShseQIpjWVVX8maIz9+JKQyFpkkGSiS54OIzCHKiW/+Ki39eK8HAU7QbSKxRiTP2/gAjrGDJBbBbm611EYXLJK+Ke049DFHy714BBMMtypZpn0kSTS+W2oWQQDyMhxRkbfXtb3bjP+aTnDSULswgqcyTwJXtlJA0ZXL0qkm5Ft/KnrtxqYTJpAn937agY7iujDIIASPYdUn1RquRJAehrI2vIgACF10XWVCep/XWNm+xyRbIVbs5vG0pIZ5FbrhRSyX4lmrzbu67mF5PD3izOGgpPR4zARRHjz1p8iLMMmHA5nc+tpTN1yTv/alm3FbIwpUy4IrG0HHxflJ97yvGCxZiLsDIqj7mqo9TbRjGQXuAZVE4xPcB8MLOTPL4J4fk4EiHWzE7BKBHB9FNFsRiRTqlVmB/xKgowd7vv7G2xO2OB10Q6Q4AzxDUWzoS9iiGsyula4539pieB2Adx1v+2IRfBd6UjZgyLcC7MIP4OJHjzWm9e681rvXmtR3qtIb4RB++Z7mrCwiJcFOYcsovZFI2bxaMD0Vw+/RDPcK4gR3QaZhc4Gg5wMorNuz9putyyfJ6Q89ECXJ146PH0TUif7nLj2erwY71oZUcLUUlmx+Se39aPZHtjXXtzam9O7c2pvTm1Z3Nq2eCi8GwXop1kF0ICwpV837lMfwGn13iylyu95Zxl/1ecYCN/5/foI9TPv0nSzZZmNl9MFHgW5q/FLuJwtmGXs9wfrdV6zeWw1msxjP7IeGdGiNMoXzfXhX9X1OfVMCgbFKFQT2LT/hia3uKit7joLS56i4teMC7ikNDvDIo04y0qeouKfp5N+s6oqOgR4y9vAdHzBUR3xXhfSNTLUektHnqLh97iobd46JniofLycAys/71PhtxFxUAL4jJMnhxE/NiXCOORkpOKLhfv27fzzTm/FTpZbIM0qH3IWAhX0ErKbwUmV8dFu7yPXPcSpR/IbVEZZNmQrywvD/J7qksZ8CyBrMnzq/nNlPWXC/r4cqd1utvtdg+3ztbNtbPtdls/a3/stA/bZ92t3dND+2Sje2w4nfaefnS2ZrTaOyerx2b7qLU8uS75j/wS9++/yDuzv2vqL/JW8u/ijm/ljt8Ppk7TVc0zTdu2VEtzPM1w5tBbXgB8DfTqhmkKWk1DU61peuXtaaHmtYsZ46sXn5+oIhOSlu/SMsPXP2Dq6o3cZQjUAFQTE4M4FBxddwnWLc91XVu1PNd2MVUtousmVk0NXF+nHoCOXexRarueOeXcF8XhcjnnlJd+wPzFDP+YbNcvczd32us+ehl8/yqFB1RmtE37vdl95rm+/CL0tLNTOu2jjYOzrrW5tXdg7m18Ojo4O9o63necI6d7fLp6cmiudk+Pjzc3d9dP2rZ5stexumvbB4cl5t65gTZxZ2rdZSm6qqtLqrakeweat2IaK5Z3NgudV5Qnq9ysq2mK3lTzf5N7V0/ivyLER8KKPGssGAQc1bI1XVdt1VsgCBCN+K6lBqZmgKkaLjE1XfWp52NKVMf3XQhcC5u2bXrYpBbxiGaD5bhYp4Zqud4iQaDC4UuAwJRAnwkEaqtMgUC1bR4I1Pu8OAiUF3om1q/db/3mimHPsf4n61r9Ud/kYVH+8OxJ3KZPsfbJYzPxDcoYjRYPAqala7ZlWarqagsEARVsnxhqoPt6YKkEq9ISAgtbumOoHnFMzzbBoRjbquZ6jk2oTmzXJhYNTB+MBYJAlcMXAIFpgT4PCNRXqYNArW0OCEz1eSgIPF6ty0hgIL7Zu8jYiFeRwL4fCewVXZ2DBE9WuCkkmPG0uProVDnsrSnTz4KVztrhx+3OYWft7NNH+3TztGWd2a1TvWOerPXO9npnRu/YOtwxWvtH27v2p97+2vGeddpdP1EaxdeSK4qn64bh6Kphu1bTdBzLVR3J8YhnAE9bQ06SstcVhZiO4xmWbmmm5SzyKEJMTbMtz/JpgF2iqYZHTBUHpm6B6TnE0wISGK5DdKxjlQRYCww/sE3HMAIt0BcKQBUOXwKApgT6TABUW2UKgKpt8wCo3uenASDLmncQearCPRCAdjo7BzMQqHW8u9ba393+YBhH1unaxqmxs3d6sHl0+qnjbH84Ofqg76wZrd3O1ubp/vHWznrPbq2u7q09CIEev8brRCBPdXVVt13VMBaIQK4W6L5rOcQ3HeoQ2yBY00EHYpi2HdiB5vim56l+YHo6BI6lE4/YVFcNi2BNC4JFIlCFw5dAoCmBPhMC1VaZQqBq2zwEqvf5SRDIWdG0OQj0ZIV7IAKtH+7PRKA9q7t+sHtkn26t2/ppa9uyewdrrZ29/bVd52xjrd3p7Wx++LR12ul87G3vnrU2d3d7eu9hCPToNV4pAnmmpqqOZlmLRCDD9HWXBq6nERurnme7WA9UbPumphqq6quur3rECiyXUE0PwDYDii2P6p7tuoENC0WgCYcvgkB1gT4XAlVXmUagSttcBKr1+WkQSNfnINCTFe6BCNRua7MOYdYHe7O7Ydm2fWK2zroHGwcn3VPT/mD1jp31k/2P7e766d6HPcPoGcb2yVnnyF493th52CHs0Wu8SgCyVFc8XzKdxb4P0nTsghtoGrY9B0AVSqGDrzqqSnTf0YwAVIfqXhBgX/NUz3Wp5fu66RIcaJ7mLBCAqhy+AABNC/R5AKi+Sh2Aam1zAGiqz08DQIYxB4CerHAPBKDVndNZEdD++nr3sG0aW/ubx+ut3upGu/tx83B/tbO9uW5tbdgnvXVn/WSt21o93ezsb26bxv7G7sOeAj1+jdcJQKZuiLd2huMs8imQYfse8TA2iIl1HWvg6o4Z2J6v+X5AqeXYJliW76quamKXesT2DYtoJpiaKYS+SACqcPgSADQl0GcCoNoqUwBUbZsHQPU+Lw5AMU5wHy780c1FGgTyHtX4pZR+Pwq5K9q8t1JP1rrK2x+j8iZ6yEL5dlpzm5rqup6mlT9eyFu6ibKiuUVLQ6Eiv1z+77ah+KMbIf5voVutW/2cV2taxHGPQxTdoWn8Bk7ux4XUp+d472XZrqZ7jmeq5iJffgeqYeuu61Dd93zXMsDxTdv0NcfENCDgm8QxgsC3sWmBpvoO8Q0/CDwSYFd1DXOhgFPh8CUAZ0qgzwQ4tVWmAKfaNg9w6n1+LsCxzDmA82Stm/O6eQI5alM1Lc/1jDuIk/+8QLgpHmzPg5tHP3v+kXBTu6y4QLjBpqMGpupjlWgB1Rzie5YDqm8ark9dx/A1TQ0C4Wl8VzMMbGmmSQAbgYVtm6p0cXBT4/D54eaOQJ8FbqZWqcFNvW023Ez3+QkOWLq6YmgrujsHaZ6scK/kgFXFuFdzqsrT0ciPwuBLBgnPL4p//qpcwo2yMjttbaO8Ri6USCS3jSEbpEJN+zD+2mlFmVxs/jrJSH5bMWOJkOyqzF4+YtH3mZAyK4fzQd4P7UB2nbJLCaizZwxG2YjB98y5UfZESTnrubiTH+RfFxR38ouMzkIswHg+Wm2qTU1+RxLHmN1MeqEhS69CKtOHo82Dgz3U2tsSOYcpznCZOrhMg1+s2kRbGQqTPvAszzrOYEkKTqbRz0cOWUpHBCjyb2ZNkWcyF5/VjLNSA+ahyIKeIpImfBRDORRfAcN9QJX8wohBJN1Wmai/krl6KWUhJCIfsiSkng6e57UE/JsxQaspA5FNO+SS8wofPgtpH5AP2TWIugTDYc5tfeQeS8WnRBxF4SWga1EdIOMNRIFAkjEchf8SmZm/5DDEG3IGacwoN2ZJ0TgLd5YiPvJlsu6Kk2sgmT9abFFZsqC4qNsQuc6LnP5wJSssSDqmM0hPRjbvaNb/uiZ8rm7o+bvSPClcQSTAgdfcZUH2MkkZLCUphff/U9rzR/JHUi5XVOfA0osDRVchRuRwv9sQNRlYes2ByRXSBMq05GNZ99Y+8m/KmqaEL2dpGvFlTi+5kHSKGAh1yitdpOJDoy9hdiPml6UrhrlAG+gaZNL8OIaEyuoXQlA4EQujMOEZYCoGxfhSFI2gIQOSyT0UBT645FNua38UUkC5xfjA0SC9liKhcZiICiOicEmu4lIdS9mIJWQe/XcMglyZJf9rY05/Re0o7U9kcH19XWd+3HPJj9L+Ml5K4HqJj5Il4YUGsFT4j/cydT9PhZlgctln6SihKE2mrSHXHUYGYQYkGzEcoTAWNg+x3Pm0yPMf479E9ZDcdSB/FA/fN9GGKE6S5J9Bip+xn45Eyn9JohBgsd5YNVIKoixHA5EBkEskelf5l4UEOkK0EwH0w2ww8pskjZcLOZR/S1aX/Sj1l2McJstr60fr3d29rZ1OM6bv5Xa1IUgZiI33oR8moijBrxxdpywTpSTCTLr5okaKgIFQEgFkkOaVECR9wizRTkofAwSIpkSWSJAyWkG//XYNiIoCLJmohZMyDoiNkkQQUQpKbFkOQ1jUd0kojoS5VFFirEu//ZYDAMjCIDiKbuTUcuzFFY5CKhm8uOPbQKg+A5Rdp4iDKNKSCeNJCLCkABUKJB0No0I+sYDhMBaBFk4yqWB+KsUYhdgPI2FxYlRFvZo11RfWlR/0OQqFcl0nDTTEDOgSFSVwSvVKgzqr6TALYwl6Ys1ipAA1AXlpgBJxjkLvruHXKEIVyxL1KUQdnT+UVTyU7kBM94cylp1QERGjAov5btADdpWf6stNrp0vRaelNJCuLJSZh0WZA0zkl39FdYeS7KpCbwjTw8XHu/Vgrx7aQYxD2QpRlP5fte1WBOgEEg6VtVpDTAaA9KaI1UMqdDcI5Tkgb1nKWyYrFnCCZavkqZiUL3e3Vtd3eutiSHOQxZE80w1TnsU4qSxZfrgpILP4dPNXjnarsXItivg6qQTxVvzpb1X8qTimZvAlWx5GOJSfgUtV+1qcrD6XH3cJrVipVXuqHK7OG8og5Zno/vWr8A2HLLq9FT/nxVHEkYuGHPvRvPIoVR378VWTZsolP6WO60AV51JFnv4ewtxPUxzpHimUZaEeKYS/USGke4RUloh6pJCeqebRPQTfKdFUp/ybhD5rZaN7KS/qMU3oPRf/YaEQ9QPR591+kYvhPVpYlbqZlJdpoZKbKuUlRxWolZkXBoDld7rjx2UtQmBYVa87NZpqj8s66wfK7e3/A3JUIfs=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Account's Operations"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/accounts/{account_id}/operations"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents successful operations for a given account and can be used in streaming mode. Streaming mode allows you to listen for new operations for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known operation unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream operations created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./get-operations-by-account-id.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-operations-by-account-id.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-operations-by-account-id.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-operations-by-account-id.mdx b/docs/data/apis/horizon/api-reference/get-operations-by-account-id.mdx
new file mode 100644
index 000000000..3595059a3
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/get-operations-by-account-id.mdx
@@ -0,0 +1,12 @@
+---
+title: "Retrieve an Account's Operations"
+openapi: "openapi/horizon/bundled.yml GET /accounts/{account_id}/operations"
+---
+
+<Tip>
+
+**Supports Streaming**
+
+This endpoint supports streaming. To read more about this, visit the [streaming section](/docs/data/apis/horizon/api-reference/structure/streaming).
+
+</Tip>
diff --git a/docs/data/apis/horizon/api-reference/get-payments-by-account-id.ParamsDetails.json b/docs/data/apis/horizon/api-reference/get-payments-by-account-id.ParamsDetails.json
deleted file mode 100644
index c5428eda0..000000000
--- a/docs/data/apis/horizon/api-reference/get-payments-by-account-id.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"account_id","in":"path","required":true,"description":"This account’s public key encoded in a base32 string representation.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}},{"name":"join","in":"query","required":false,"description":"Set to transactions to include the transactions which created each of the operations in the response."}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-payments-by-account-id.RequestSchema.json b/docs/data/apis/horizon/api-reference/get-payments-by-account-id.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/get-payments-by-account-id.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-payments-by-account-id.StatusCodes.json b/docs/data/apis/horizon/api-reference/get-payments-by-account-id.StatusCodes.json
deleted file mode 100644
index e60aff153..000000000
--- a/docs/data/apis/horizon/api-reference/get-payments-by-account-id.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"payment"},"type_i":{"type":"string"},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string"},"asset_code":{"enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","asset_type","from","to","amount"]}}}}},"title":"Payment"}]},"examples":{"RetrieveAnAccountsPayments":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/accounts/GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE/payments?cursor=&limit=10&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/accounts/GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE/payments?cursor=148289273518190684&limit=10&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/accounts/GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE/payments?cursor=110694007436259329&limit=10&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/110694007436259329"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/26c996aa6afb299b6761f2335277196715160ade6aa001a755116448b145d3a7"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/110694007436259329/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=110694007436259329"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=110694007436259329"}},"id":"110694007436259329","paging_token":"110694007436259329","transaction_successful":true,"source_account":"GB44UMO65PK5NWMRP4S2OSZA5BD4ACOW5KQ6TWLLO2MP7S7N5MJ2MJVI","type":"create_account","type_i":0,"created_at":"2019-09-11T13:16:44Z","transaction_hash":"26c996aa6afb299b6761f2335277196715160ade6aa001a755116448b145d3a7","starting_balance":"1.0000000","funder":"GB44UMO65PK5NWMRP4S2OSZA5BD4ACOW5KQ6TWLLO2MP7S7N5MJ2MJVI","account":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/110694007436259330"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/26c996aa6afb299b6761f2335277196715160ade6aa001a755116448b145d3a7"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/110694007436259330/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=110694007436259330"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=110694007436259330"}},"id":"110694007436259330","paging_token":"110694007436259330","transaction_successful":true,"source_account":"GB44UMO65PK5NWMRP4S2OSZA5BD4ACOW5KQ6TWLLO2MP7S7N5MJ2MJVI","type":"account_merge","type_i":8,"created_at":"2019-09-11T13:16:44Z","transaction_hash":"26c996aa6afb299b6761f2335277196715160ade6aa001a755116448b145d3a7","account":"GB44UMO65PK5NWMRP4S2OSZA5BD4ACOW5KQ6TWLLO2MP7S7N5MJ2MJVI","into":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/115354197276323841"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/c09d4cee993d60d73c80f036666966738a26b8f3b25d7275b93fd995505b5e5b"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/115354197276323841/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=115354197276323841"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=115354197276323841"}},"id":"115354197276323841","paging_token":"115354197276323841","transaction_successful":true,"source_account":"GDV4KECLSZLKRVH4ZTWVAS4I3W2LPAPV66ADFFUZKGIVOTK6GMKGJT53","type":"payment","type_i":1,"created_at":"2019-11-18T19:59:40Z","transaction_hash":"c09d4cee993d60d73c80f036666966738a26b8f3b25d7275b93fd995505b5e5b","asset_type":"native","from":"GDV4KECLSZLKRVH4ZTWVAS4I3W2LPAPV66ADFFUZKGIVOTK6GMKGJT53","to":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","amount":"688.4065454"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/117356420835532801"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/c25dd84798076ee8ea126c78407d61c7e8f3efdf8739274f56b07a7029500b00"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/117356420835532801/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=117356420835532801"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=117356420835532801"}},"id":"117356420835532801","paging_token":"117356420835532801","transaction_successful":true,"source_account":"GDV4KECLSZLKRVH4ZTWVAS4I3W2LPAPV66ADFFUZKGIVOTK6GMKGJT53","type":"payment","type_i":1,"created_at":"2019-12-18T08:23:35Z","transaction_hash":"c25dd84798076ee8ea126c78407d61c7e8f3efdf8739274f56b07a7029500b00","asset_type":"native","from":"GDV4KECLSZLKRVH4ZTWVAS4I3W2LPAPV66ADFFUZKGIVOTK6GMKGJT53","to":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","amount":"355.3887598"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/119400713599217665"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/b9d7c534b5fa168570a5bffe0f2089de150d00bf8cbd19ec93e897c565958f3f"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/119400713599217665/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=119400713599217665"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=119400713599217665"}},"id":"119400713599217665","paging_token":"119400713599217665","transaction_successful":true,"source_account":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","type":"payment","type_i":1,"created_at":"2020-01-17T20:32:38Z","transaction_hash":"b9d7c534b5fa168570a5bffe0f2089de150d00bf8cbd19ec93e897c565958f3f","asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","from":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","to":"GASWJWFRYE55KC7MGANZMMRBK5NPXT3HMPDQ6SEXZN6ZPWYXVVYBFRTE","amount":"84.9410878"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/147350483860869151"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/b53cd1d3a95ad2fd7141b3b800e8cd3af1658d2d72b2274d1bd116cf0e58f193"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/147350483860869151/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=147350483860869151"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=147350483860869151"}},"id":"147350483860869151","paging_token":"147350483860869151","transaction_successful":true,"source_account":"GBDSJHAGNQDL2WZ5LBRSIVI6MUHJO6CLKF5XFVUK7GMPUQ4NBLSYVAHX","type":"payment","type_i":1,"created_at":"2021-03-06T19:27:33Z","transaction_hash":"b53cd1d3a95ad2fd7141b3b800e8cd3af1658d2d72b2274d1bd116cf0e58f193","asset_type":"native","from":"GBDSJHAGNQDL2WZ5LBRSIVI6MUHJO6CLKF5XFVUK7GMPUQ4NBLSYVAHX","to":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","amount":"0.0000001"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/147354181828010015"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/1be9f5f3dcd28c4fa70f5f5ed79d7332da14741e55a5abe4132d4c04da7b6f1e"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/147354181828010015/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=147354181828010015"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=147354181828010015"}},"id":"147354181828010015","paging_token":"147354181828010015","transaction_successful":true,"source_account":"GCVZ5PHDFGUV6YXN7I735RE5AJSFOOWPT4A2WHCGTGXOQ6KVWM3TYEQC","type":"payment","type_i":1,"created_at":"2021-03-06T20:49:34Z","transaction_hash":"1be9f5f3dcd28c4fa70f5f5ed79d7332da14741e55a5abe4132d4c04da7b6f1e","asset_type":"native","from":"GCVZ5PHDFGUV6YXN7I735RE5AJSFOOWPT4A2WHCGTGXOQ6KVWM3TYEQC","to":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","amount":"0.0000001"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/147355590577238047"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/ba6bca6dce0c01d9d9cebcc79466c986b18a8cb3b67030f6424b6563778ab947"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/147355590577238047/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=147355590577238047"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=147355590577238047"}},"id":"147355590577238047","paging_token":"147355590577238047","transaction_successful":true,"source_account":"GBDSJHAGNQDL2WZ5LBRSIVI6MUHJO6CLKF5XFVUK7GMPUQ4NBLSYVAHX","type":"payment","type_i":1,"created_at":"2021-03-06T21:19:49Z","transaction_hash":"ba6bca6dce0c01d9d9cebcc79466c986b18a8cb3b67030f6424b6563778ab947","asset_type":"native","from":"GBDSJHAGNQDL2WZ5LBRSIVI6MUHJO6CLKF5XFVUK7GMPUQ4NBLSYVAHX","to":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","amount":"0.0000001"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/148286782436462682"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/74afe177a6ecf466899bbdbd339a796e1995a3c8c4084c556849a702759bb7c1"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/148286782436462682/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=148286782436462682"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=148286782436462682"}},"id":"148286782436462682","paging_token":"148286782436462682","transaction_successful":true,"source_account":"GDAXCWDQAYP2VC2UR2KRLVD7JQYIYMQ7BGFY647BCG4CFANT7JYNSO4S","type":"payment","type_i":1,"created_at":"2021-03-20T12:48:24Z","transaction_hash":"74afe177a6ecf466899bbdbd339a796e1995a3c8c4084c556849a702759bb7c1","asset_type":"native","from":"GDAXCWDQAYP2VC2UR2KRLVD7JQYIYMQ7BGFY647BCG4CFANT7JYNSO4S","to":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","amount":"0.0000001"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/148289273518190684"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/de50646ece611a9fbd2b222b910f020f94e654064d64fd54f50358d3d13e7f49"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/148289273518190684/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=148289273518190684"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=148289273518190684"}},"id":"148289273518190684","paging_token":"148289273518190684","transaction_successful":true,"source_account":"GC2LS7Z564TGWRVCIHTSEIZBO5WUZSNR2MA544FE4JPXMAUMDQI2JR6N","type":"payment","type_i":1,"created_at":"2021-03-20T13:42:07Z","transaction_hash":"de50646ece611a9fbd2b222b910f020f94e654064d64fd54f50358d3d13e7f49","asset_type":"native","from":"GC2LS7Z564TGWRVCIHTSEIZBO5WUZSNR2MA544FE4JPXMAUMDQI2JR6N","to":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","amount":"0.0000001"}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-payments-by-account-id.api.mdx b/docs/data/apis/horizon/api-reference/get-payments-by-account-id.api.mdx
deleted file mode 100644
index 69ff08d0f..000000000
--- a/docs/data/apis/horizon/api-reference/get-payments-by-account-id.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: get-payments-by-account-id
-title: "Retrieve an Account's Payments"
-description: "This endpoint represents successful payments for a given account and can be used in streaming mode. Streaming mode allows you to listen for new payments for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known payment unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream payments created since your request time."
-sidebar_label: "Retrieve an Account's Payments"
-hide_title: true
-hide_table_of_contents: true
-api: eJztXOty2ziyfhUUf8wkU5LMG3hR1dQe+SbLtmTZkq8ZlwckmhLHFKkFKDvelKv2Nfb19km2AJK60vHYlmeSmZM/qQgg0N34+gMaQfcXJSUDrtQ/KQ3fTyZxypXrikKB+ywcp2ESK3WlPww5gpiOkzBOEYMxAw5xyhGf+D5wHkwiNCYPI/lbkDBE0CC8gxiRbEhEYop8EiMP0IQDRWGMeMqAjMJ4gEYJhRrqLfwbkShK7jl6SCYoTVAU8hRiOXQM94tzpUK46UQcpUN4QIQBIpQCFV+nQ0C9FKKIMBQBHQCroVaAfBJFZbJU0F7Cwn8lMboPowjxlLAUkVQOA4RFIfAU3cbJfVwIgiZxBJwjgvwJ4wlDIUcc0ooY+34Y+kPkEw4oTOdHDFgyQumQpPlHNbT5IL5KhRxirnysOxJNQKgRJ/cVaRBhyUzkmSV8BiQFingY+yB6McTgnxMhahqOoKZUlGQMjIgVbVGlrjQh7eYfbz7kS9+iSkUZE0ZGkAIToPiixGQESl3JDXwTii6hAMWYpEOloohZQgZUqadsAqXIyb/977//w9F44kWhj27hAUHsJzRbAII8wsHQhVpC/SnEpLxCeO4PYUSU+hclfRgLgbKeSkWBz2Q0jsRPze328XFnv22eHtrHrYZlde0TvXu11z5udc6vNtu2vbmz2d473L3Yxvs7p4295r59Yu5fKY+PlamimdULJf85AfawoGVAIr6iZgPFk5EHLFtP6SZcLBlBfAx+GIQ+ihJfKpOp6ydRBL78dxIgBnycxBy4dJRQWElCM4cIoDEZhPHgJk1uIc4BkQSIIAZ+wmipfcI4hQGweQNZlmpZmm3ajotdTcXzaieMwsu1psDDQUwKPYSocqAZ8DMJOeLDZBJRRMZjIKyGjuQYHIWxH00ooF8J939FHwj3IaZhPPiIEoZ+FdP9ij6Iv/KfpeNmHs8GE+l7IY//++//pLnDpYhCQCZRZn857DPwiScjwX6E+0qmoHI9b5goHIXpCw3THwIakc/haDIqgCFXOTMFg3TCYqA1JPrJ8aVLMxIPIFtzTQivqyqqIhKjyXgMLO8oARZyNCSMTt2n4CtBh2NgQcJGRNAAA8KTmH/FaMUCAl2xnab+Xlxp6rzB8iW9CUgYAX2h5XqQSsZmGeUV8MjGQlMGE8ARXiNkXQWT/Fp4kpyiVAsvSSIg8Wz9JXnJ/gur/1sSxq9VgcSc+Jlkc6oIH1loyzeInL+B+MOpKy2oK34piKKmPF5XlM9VPhmPE5by6nQHK2h4SilCaV1VxV9LcmZ7t1JR/CROIU5FFzIeR2FGVBu/cdHvy5zxSBQdBXJXyM2YeL+BL7xjzISwaZjNdxOF8S2fM/cT/ThEwfO9hgyCMs+VME+li8a3ymNFSWE0joQVSxb68XF+4T5lg15XlDRMI5gbI4bP6Tcm0pjB3Tcl0qPoVvx0KJdauMwzmICRB+JE9rwqOVHOdSSMEeF6YQqj34Gr7xh/c9TwjUkGQQB++jus+odKJSMQoN+aWGMGPlD4tsRa6iTRv4i42SrPWXZOm+vHihLSMnGLmUIq1Z87r672XoT5zSyILNOsovBkwny4yaOIssnHJE2BiU2t+alRvVKr7vUXjB/nxCKUMrHZianlx1+LI/Kgquh8E5aqkO/YN6REpCUNh4QPSzsRziG9KZdo2iyOeaK5OKmK8/YdKFICGqY3JBoPSTwZmas/abpcsmyckPMJsDfbTxxQ374IyZuHIKNyOCzDPMyC2jlAPgm/FazlaJniYGHVS9Z4YUVzU0llp+JePy5un90Ca2KdcghKXjiBlIVwB424uJcpwnXRKmPAxa2u2MwyQlGGaTrm9Y2NYRYbVFPgaQxpjWcXIbWEDTZyNflGc6tziHFrv7+n713o1t5hp9W83Nb3W8eH/c3G8aHRO+t2rhpW9+LA7jTO9k5N3Tg/6u9sFPcP/8jC5p9/kFHKz5r6g4wDfxZR1dyp6k+VTTMd3XF128Cao7mq5ZhPSFscuP5caTXVck1VtU3D0rFr6O6ytDJWFVhaOFpND0+f3giOWfSxsSpLyVHlBUPPxz8buuW7rkWIRQJPd13Psi0t0A0D67atuZatYc1SCQWLEFXViI2xplmm6XiaialB7KWzybo03CjGXDpkvGD8fIR/zJbrhycXd/nQ8OppyNdnyTdwpaRtedsu7/PUzp2Fnct7tdLcNM3T9pGFuwe4c94+6Zo9/ah31cCb22Zj6+gcHxxb/fPDwyO93bV7dge39/X2/lmroN56zrhLlCz2ZHVxD1Z0VXOrqlvVtL5m1DWrbppXZSRdV94MuYoi73CFsTwSibsWYa6amv0RzD+JxX3am/SfM+IrSUWGZe9FAob6VycBQ/1DSSAz6HuTgJjlKRIw1OdJQPb5w0mg+O+HEbDB3Hms7vyZHLAWBcNYnIW/FRfHBjY119Zty9ANx9TW6OK+6lLTB3Bdg1oqtQ3fUQPVsCzLci3LNhyiW54TGJ6Oqa3b2HONgLouxir2MGBvTS6+rOE7u3iZQdfv4quzzFx8pa3ExUv6vNTFt8/Mg52tw97V4cHJ2Z551T8/a/TMlnGuH3Yb3TPLamzv7p5eHTRbZ0f9A6vZPmju97Exc/Ei6p45t1bm3JpW1Zy+5taxWzfVJ5z7zVhbDM1nIXcW/L5J2zd5+yzsVSzHqZmqhU1srpkEbANbpq46BsaG7qhrJQEdU+qYtuuotgXgANF0y7cdU7Wppfk2OIEBAQ0c23B12wyw5ak2sVXdxarqqeqaSGBZw3cmgTKDrp8EVmeZkcBKWwkJlPT5ZklAFySgOnXdqBv4KRJ4K9a+AxIwMK4ZjmNj11kzCcgzn2Zg19U127LwGknAc6ntY8P0cEA0y8G2SrAXBKAGuuq4FDSsUlX1Asf3qOaC7xrguLaPLexiJzCCNZHAsobvTAJlBl0/CazOMiOBlbYSEijp81ISeD2sX0ACulpVtapm93W1buh1w3mCBN6MtSUSKLlzn7+lV05728ryhbvS3D49aDdPm9tXxwfW5d5lA19ZjUu9aV5s9666vSujd45PO0bj5Kx9ZB33TrbPu/jycOdijmveYFTJNY3e+f757snlDsYHW3a72ehctdsnmwe4073oG3vt7vax1du5uOpYV93zy4uzs8vN3ZNFrnHMmmtqqmOvmWpM28Cq6RiOpTqWq+F1njc8bPhUowZxMaF6QG3N1DzDc1QVHJ8aJNAs7FCd2rqn67ZJNY9qmuUHKmAn0FxjPVSzouH7Uk2pQddONSWzTKlmtW2Vasr6vPheYbu3v9dodo63D/XzK3y4edJrnbWs9une/pG1dXiwiy92z04P7Ga7e3psdjYPe5dnjb2LF1KNVlWNqmqJoEO364bxFNW8FWvPnTfeoO26zhtqfseprZ8CTM3RHHHuVFVtnacNzQM3wIFBfao7vhkQWw1wgIHaLrUNQ6dEM21TA4wJJh6YmqFT01dNSmzPCjRYHwUsaPj+FLBi0HehgKVZFihgsa2cApb7vPi0cXaFu3vbu83TM+vyomO3bAOf7ODGfm/36Oi82zcb+vneVrPfvDg6tg7OzttG/3LneOuVFKCrddOtG09dKr4Za89RwBu0/Q4oAGNXxbatG45q2us8BRDL84lFfVB9VaMudX3wfN92TcvyXcfyNIc4vmd4lq0aamCZuulZ2DJs2yGea67pfxdWNHx/Clgx6LtQwNIsCxSw2FZOAct9vu1TgK7VNbduuk+dAt6Ktb/xKcDRHct2dNOwTEu3HH2NFGCbJADNtokFfmBaluO6nkc9ahgusV0LNNfFxPAd31Qd08fYckxX3AXZ2PU829fWRAHLGr4zBZQZdP0UsDrLjAJW2koooKTPiy8eGxdb59vHjcuufraln57oByeHZ9v2/vFl67J9bG82dy8t097cappbu41O396/7PSOzN5rKEBX+5peN526/tQp4M1Ye/bi8fXafgcUsPBEa40UQAGrlmmBD5amETfwqAjEdM/V1EDV1cA1wcKmapnUMgOKzQCrBnaoQTUD7MB010cBCxq+PwWsGPRdKGBplgUKWGwrp4DlPi8OBPTDnn2FLbPfPD8522rt9Xs7ravNI3x+etXrnOjtBjbN3R1zv3vRbpy2t49b+v6J1XktBRh1U6+r9hMU8GasPRsIvF7bd6CA7FWrfNgKn1OIucC6fIJ4Cw9KvTxTqVK8YhUrKvKZRpAOE4GZAaTZa2Bhytnbyi+zJNTH6XtJ8RYL2F2Rrjph0e9Ds1KWtNfP+qEOpPcJu5XcVj5iMEknDH7PmLtFTxQXo16LZx9B9gQ6fwecp/AJowDj2ddqTa1p8iX+aETYw6wXGrPkLqQyXxTt9ftd1Oi2RJIZJSkpcsWKjOd81hpqpSiMB8DTLM2UQVUaTmZMZ1+OWUInPlDkPZQNkaWuisSEaRoiEB6KtNcE+UnMJyMoPiV3wMgA0FxCGWIQSRgXOdlzqYrVhIUQiwQ4Kchi/i/Pksa9h6lAWwkDkT4Zcqn5nB4eC+kAkAfpPYgE9PE403bxyy5LRDIGR1F4C+heJIKnvIIo+BCnjEThv0Qq3md/KFIyeUWOIP0RZXf6UqJp2mWaID7xZHbm3H5TQTJhUCxRkZ2evxWsiOTWPIEb7mT6tpRjOWVw9mVtBVl/dyR8ml/Q6w+Fe1K4g0hst3xh58rF3vATBtU4ofDxb4WeX+Jf4mK6vAwDkRsqUHQXEuSfnhxWRBI+S+45MDlDEkORhzq1dW/7gD9ra5r4fCNNkohvcHrLhaUTxEDAKStrkIgch89h+iDGl5UKxplBK+geZJb0aAQxlaUOhKFILCZGYcxTIFR8NCK3okoADRn4qVxDUcuBSz3lsg4mIQWUeYwHHA2Te2kSOgpjUUpCVKjIIC7hWNhGTCETpz8wCDIwS/23p5r+iDajZDCzwf39/aLy055VL0oGG6Qaw32VT+Kq2IWGUM33j48yV5snwk2IfztgySSmKImXvSHDDvOHYQp+OmEkQuFI+DxkZR+SPLF7RH4TpSKyrQN5k9H4Yw3tikoUcZZIJn4mXjIROd5SRGHAfL4pNBIKog5DBflD8G+R6D2vv8wcbwrTzgwwCNPhxKv5yWgjt0Pxd6Hqhhcl3saIhPHG9s7ZzuFRt9Vp1kb0o1yuTQgSBmLhPRiEschC/5Gj+4SlonZAmMqDc14QQ9BAKIUAf5hkqe9SPuGWqJPQ1xABookvc+Kljerop5/uAVFRbSMVJU8SxgGxSRwLIQpDiSXLaIiIYh4xJZFwl3mWmGLpp58yAgBZCYJE0YMcWn57c0eikEoFb1b2NhDQZ4DS+wRxEFU5UuE8sQ8szkmFgp9MxlFun5Gg4XAkjlkkTiXAvESaMQqJF0bC48RXc/CqLUBfeNeIxGQAHIUCXPdxBY0JA1qlotpJAa8kWFQ1GafhSJKemDP/UpCaoLwkQLEIadCHe/gxitCcZ4mCBKJoyi/KFhnL7UAM94sytZ2AiDixAhvxo6AH7C6UL+2LRV4I9USnahLIrUx0y/LaiS8Tj/J0/kLseUDvCtcjefrj4mFv8WgHIxLKVoii5P/m2x4rShT6EHOYm6sxJv4QkF4TD4lCKrAbhPI5QNZSzVpmM+Z0QmSr1CkflG8ctrZ2Or0d8UltmI4iGV6NE56OSDw3ZZEzJigzzxr7kaPu7KS8cIb4Mkv8//8KP3+JCj95sJjC53RjHJFQps9KgH3Jo6lPxaN1gYb6QlGfaUB1XVGGCU9F5y9fxH5wyqLHR/FzVgFDhFk05MSLnqqBMY+sP780TqlVsrh0Wuwnj0QVGfG9RLnvpgLOV6xQ1P55pRH+QtVuvmKkog7QK430ToVtviLwSh2eRcmfFfRdy9d8VfK86M5M3mvxDxYKU7+QfT6c5JngH9HaSpGVSl7kKcUP85IXGs0RrUz0HgKR6YHTC7KG78N4Hl4rhXgWLsiaO33l8fF/7r9tdw==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Account's Payments"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/accounts/{account_id}/payments"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents successful payments for a given account and can be used in streaming mode. Streaming mode allows you to listen for new payments for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known payment unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream payments created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./get-payments-by-account-id.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-payments-by-account-id.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-payments-by-account-id.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-payments-by-account-id.mdx b/docs/data/apis/horizon/api-reference/get-payments-by-account-id.mdx
new file mode 100644
index 000000000..b21ecdf3e
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/get-payments-by-account-id.mdx
@@ -0,0 +1,12 @@
+---
+title: "Retrieve an Account's Payments"
+openapi: "openapi/horizon/bundled.yml GET /accounts/{account_id}/payments"
+---
+
+<Tip>
+
+**Supports Streaming**
+
+This endpoint supports streaming. To read more about this, visit the [streaming section](/docs/data/apis/horizon/api-reference/structure/streaming).
+
+</Tip>
diff --git a/docs/data/apis/horizon/api-reference/get-trades-by-account-id.ParamsDetails.json b/docs/data/apis/horizon/api-reference/get-trades-by-account-id.ParamsDetails.json
deleted file mode 100644
index c8a2ddd7f..000000000
--- a/docs/data/apis/horizon/api-reference/get-trades-by-account-id.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"account_id","in":"path","required":true,"description":"This account’s public key encoded in a base32 string representation.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-trades-by-account-id.RequestSchema.json b/docs/data/apis/horizon/api-reference/get-trades-by-account-id.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/get-trades-by-account-id.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-trades-by-account-id.StatusCodes.json b/docs/data/apis/horizon/api-reference/get-trades-by-account-id.StatusCodes.json
deleted file mode 100644
index bd6a341f7..000000000
--- a/docs/data/apis/horizon/api-reference/get-trades-by-account-id.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"base":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"counter":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operation":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","base","counter","operation"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"ledger_close_time":{"type":"string"},"offer_id":{"type":"string"},"trade_type":{"type":"string"},"liquidity_pool_fee_bp":{"type":"number","format":"uint32"},"base_liquidity_pool_id":{"type":"string"},"base_offer_id":{"type":"string"},"base_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"base_amount":{"type":"string"},"base_asset_type":{"type":"string"},"base_asset_code":{"type":"string"},"base_asset_issuer":{"type":"string"},"counter_liquidity_pool_id":{"type":"string"},"counter_offer_id":{"type":"string"},"counter_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"counter_amount":{"type":"string"},"counter_asset_type":{"type":"string"},"counter_asset_code":{"type":"string"},"counter_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"base_is_seller":{"type":"boolean"},"price":{"required":["id","paging_token","ledger_close_time","trade_type","base_amount","base_asset_type","counter_amount","counter_asset_type","base_is_seller"],"type":"object","properties":{"n":{"type":"string"},"d":{"type":"string"}},"title":"tradePrice"}}}}}}},"title":"Trade"}]},"examples":{"RetrieveAnAccountsTrades":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/accounts/GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K/trades?cursor=&limit=3&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/accounts/GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K/trades?cursor=107449584845914113-0&limit=3&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/accounts/GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K/trades?cursor=107449468881756161-0&limit=3&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":""},"base":{"href":"https://horizon-testnet.stellar.org/accounts/GCO7OW5P2PP7WDN6YUDXUUOPAR4ZHJSDDCZTIAQRTRZHKQWV45WUPBWX"},"counter":{"href":"https://horizon-testnet.stellar.org/accounts/GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K"},"operation":{"href":"https://horizon-testnet.stellar.org/operations/107449468881756161"}},"id":"107449468881756161-0","paging_token":"107449468881756161-0","ledger_close_time":"2019-07-26T09:17:02Z","trade_type":"orderbook","base_offer_id":"104078276","base_account":"GCO7OW5P2PP7WDN6YUDXUUOPAR4ZHJSDDCZTIAQRTRZHKQWV45WUPBWX","base_amount":"4433.2000000","base_asset_type":"native","counter_offer_id":"4719135487309144065","counter_account":"GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K","counter_amount":"443.3200000","counter_asset_type":"credit_alphanum4","counter_asset_code":"BB1","counter_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","base_is_seller":true,"price":{"n":"1","d":"10"}},{"_links":{"self":{"href":""},"base":{"href":"https://horizon-testnet.stellar.org/accounts/GCQDOTIILRG634IRWAODTUS6H6Q7VUUNKZINBDJOXGJFR7YZ57FGYV7B"},"counter":{"href":"https://horizon-testnet.stellar.org/accounts/GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K"},"operation":{"href":"https://horizon-testnet.stellar.org/operations/107449486061649921"}},"id":"107449486061649921-0","paging_token":"107449486061649921-0","ledger_close_time":"2019-07-26T09:17:25Z","trade_type":"orderbook","base_offer_id":"104273938","base_account":"GCQDOTIILRG634IRWAODTUS6H6Q7VUUNKZINBDJOXGJFR7YZ57FGYV7B","base_amount":"10.0000000","base_asset_type":"native","counter_offer_id":"4719135504489037825","counter_account":"GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K","counter_amount":"1.0000000","counter_asset_type":"credit_alphanum4","counter_asset_code":"BB1","counter_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","base_is_seller":true,"price":{"n":"1","d":"10"}},{"_links":{"self":{"href":""},"base":{"href":"https://horizon-testnet.stellar.org/accounts/GAMU5TQFUMDGVKYQPPDCD2MKKUUWELSQAEKNNU4RFQCWFSRBPJA2MAGQ"},"counter":{"href":"https://horizon-testnet.stellar.org/accounts/GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K"},"operation":{"href":"https://horizon-testnet.stellar.org/operations/107449584845914113"}},"id":"107449584845914113-0","paging_token":"107449584845914113-0","ledger_close_time":"2019-07-26T09:19:30Z","trade_type":"orderbook","base_offer_id":"104299223","base_account":"GAMU5TQFUMDGVKYQPPDCD2MKKUUWELSQAEKNNU4RFQCWFSRBPJA2MAGQ","base_amount":"748.5338945","base_asset_type":"native","counter_offer_id":"104299548","counter_account":"GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K","counter_amount":"74.8533887","counter_asset_type":"credit_alphanum4","counter_asset_code":"BB1","counter_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","base_is_seller":true,"price":{"n":"10000000","d":"100000001"}}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-trades-by-account-id.api.mdx b/docs/data/apis/horizon/api-reference/get-trades-by-account-id.api.mdx
deleted file mode 100644
index a1f0990fe..000000000
--- a/docs/data/apis/horizon/api-reference/get-trades-by-account-id.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: get-trades-by-account-id
-title: "Retrieve an Account's Trades"
-description: "This endpoint represents all trades for a given account and can be used in streaming mode. Streaming mode allows you to listen for trades for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known trade unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream trades created since your request time."
-sidebar_label: "Retrieve an Account's Trades"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWuly4zYSfhUUf2SO0i3qclVqV7JsWT5lW/KhGZcHIlsSYhJgANCy41JVXiOvlyfZapCUKUv2zHiTzUyy/uMS2Wh0f32gwe4HS9OJsjY+WE3HESHXyrrKWC4oR7JAM8GtDas/ZYoAdwPBuCYSAgkKuFaEeh7RkrqgyFhIQsmE3QInNOJEKHeJQzkZAQkVuIRxorQE6jM+Ib5wIUdOl34jQzFT5F6ERAviMaWBG9apXTRKs9hCET2Fe0IlEOq64OI6PQVyqsHzqCQeuBOQOdIdE4d63jopMmRHSPaL4GTGPI8oTaUmVBs2QKXHQGlyw8WMR2KQkHugFKHECaUSkjBFFOgMcp5NmTMlDlVAmE7zG0vhEz2lOl6UI617XKVRCtwp5nVLvRBQCS5mGQMEIhgJnKDgSKAaXKIYdwBpJJHwc4hiauZDzspYIgBJ0Xxd19qwOqD7ZmnrPrZy17UyVkAl9UGDRPs/WJz6YG1YMbTXDEkY2j+gemplLNyDSXCtDS1DWOsk8drff/1NkSAcecwhN3BPgDvCjaCnZEQVlEuoEqq+8CYjLYqunCn41Np4sPR9gAJFlFbGgjvqBx4+6rQPjo8Pdw/swX7tuNusVnu1k1JvuHNw3D08H7YOarXWVutgZ3/7ol3Z3Ro0dzq7tRN7d2jN55mFohHiiZI/hyDvl7QcU0+tqNkkPPRHICNbmohQaC5KVAAOGzOHeMIxykTqOsLzwDG/xZhIUIHgCpQJDoYoGaeM3QNIQCeMT661uAEeO4MYE0okOEK6a/FhXMMEZBqgarVQrRZrdq3eqDSKhUpabSFd+HqtXVBswmmiB4pqGD06fSShImoqQs8lNAiAyhw5MjwUYdzxQhfIJ6qcT+QtVQ5wl/HJOyIk+YTbfSJv8V/82IRsFOtyEvrANWGK//7rbzoONk1cGNPQi/A3bD/jPjz0MdFR5ViRgtZVGhiP+Ux/JTD9KRCf3jE/9BPHMFaOoJCgQ8nBzRGkM/xNOEvKJxDZvIjClwoFkiWUkzAIQMaExsGYIlMq3UX4JJkKE2EAciykTzEJSKBKcPUCaIkBwV3Brlj4Ur8qFubzq4x1l1VhEAipVXaRSpOssPBw5FQqFPDfMmanoeOAUlbGcgTXwDWS0CDwWBQ3+Z8U0j2kJKKedzQ2SSqWTYx+AgeNFUhMdZpF+117jN+olA7P0Cnwxp+nmkoYr3Mkg7o2HsNvrHnG0uAHHkKboh4J4QHlmHFSTvQhYnqVsTTTHqR4cLjT35hIgYTbb0qkOZIlj/aNqTF+P+MT4I8AS4PPqxLHbYqQSkkxDTAN/hf41Xfsf3gsf2MimVoC5Dcm1aK0+qbkekJkHCw26iOQaeGv5hmLueukSxgz1ySBVEHyEvUS3TxjRYX3teMJBddYlq4uRjDHY5DX6+RAVLBmvY4er3ntsZ9D5jJ9fx0I4V2PAa5HQYoyOo/TcIeM63Ip8fbrJwyekcKQviinoYhL33UQBVRrkHj0dT40s8NCtnH1UKnMU+BR15V4JC6Y+et5Ld4rBfp5ZFI0WDl8joYpFS6F2SNV7DlfCFVC/SJaCdEfBdiC3/OYLUhehm2Z7FnklsmeA+81ZmfqWoHnLbFbpAFMLsyB6Jx6jHQW3eRSwbcu9paCadnJVl1qBdO1CK7IjDnpxXS4Jn/MM9Y6L0kd80buntF8Hv09vjOXWmuOqSwuUc0+J6Alg1to8uSbRnT7xXfmSrV8VCeHcZStranWgdrI56dRqZ3VoDQHnVPRF4WckJN87Lsq32mXN3cvB/1h87K6e7xtb251q8Pa2XnlqHp22Nkb9luXg63N/tFub6vdb9W6pZ3haa9b2stHV/l/RXfQH38wJf+P5R/MnepHvKGkSsK/ULBioWbbjUrdrtuVRtEuFsvZwnphk2LxLxfWrtbr9WKtUi1WiyvCmlsfutBSVbio+z684BfpIulVSm4e1Y7OK71Sr1c7bx9WLwfti8HgqNc8sYc7u6ft9uaw320en/RPhjt7x+dnduV80GudXzyphP6X+K6UO1+x+WKdyq/axZgAzwdrnc2eJrRnqdbUGFapUGxkC7VsqdovNDaKtY1Cabic/uJPICMhbqyV490qFuxCrV6qVa2nB7v1ags+OdUt2y6Xc6WC+VuTfzcs/NBym07EKQHtWrFRLFfseq1caBRtu1CtWGtOVevVRl89UlHgXLmUyLvuOLUcCS7T19QLppSHvr1CF52nVqtVXHmVnKFWp13Zre7sb1eq1eqF3Rzu97f7F/uXdnW3cnpe27o42Wvtb132dnvl8mm5fHAx7JxVN8+3D1cPo/hrxOLINF5kmdPGKhai74B/Yqgft4/63e7+Sadatrsn582jdn9wWt2pHtfOBoPDvWH3sNXePbro7G6f1C6Hldp25/Ks1vrbhHq9WqgWq3ajUVoN9dS7F0L9KdUXhXqp8rWhXqqVG+X6ulB/pQWfhnqxkCv8d4FeKdh2vVEo1+qlPz/Qiylp/x/mn4u15sGg0j/eHhy0O2d7l8e9XnuzXTrY2xsMzrf2T4+bW3uHhwP7ZPt483z79KTV222WDpqd479LmKfLwqdhvlwyPhfmK1RfEOaNjXLhq8O80SiVymvC/LUWfBrmNbueq5TL9YZd+eo4j+Sr2PU/Pbprdq6OUtZr33N4P2YoN/UTD5qr+eKKCHcauEJnNVX9DdxbG+v7FpnkToh7YXfDBz0VyHoCOrrGT60N6zH2Hh47pPP4BoLtE5C3SSc1lN6XxZS1rp/Uj+jIIeiZkDfmE/d6juNQhxK+hOd2Qkl4wvUKO11jYW7f8X067i4hJCBVtLqQK+TQ1ir0fSrvH6lIIMUtc00rk+z0+z3S7HWxneRSTbFXlW7Dx7vmSFcTxiegdNQBlZA1wJk2frQykMINHXDJ6H4di6irip/0Fh0yoIphR1YQR3AV+pAspbcg6QRIqrlEJHgmFpNBgVQXLSskA46ddSPIcmtaRTMMo/uFQJtCAnb2mDKap/QYSeZOgIxAzwDnIYIg0nZ5ZU8K/EyiiMdugMxwOkGrDHHBAa4l9dgv4BK4c6bYLVQZw8FEGokizUi06AhqQVQ4Mo1DSbmipuWsMsQ0MtFEycjEiHqobAb7rvFcAdyacQ4jR3q1aWwvVuZWPOuf7gkf0ga9epuEpwu34OFpqZbOz1jsvCMkZLlw4d0/yns+8o882S6eCqKmEQwuuWWUOIOT/QzOh0gxUyDNDoJDMm2wwPq0vac+i7UrHJXXQngqr9wbhUgLIgHdKZq2Efi18I7pe+RvRmiCCNAMmYFp4Ps+cNdM4CBQlOPGhHGlgbq4yKc3OMDiMgmONjbEASNl9DRmnYTMBRJFzAgUmYqZgcT1GcfJJhyYilzcuGOCDW5hevpvJYwjZzb6txeaviEtT0weMZjNZsvKLyizI09M8jTLYZZVIc/iKTSFbHx+vDNjBEpgmFDnZiJFyF0i+NNoiHxHOlOmwdGhpB5hPsY8+MbyIp458OlPOMEUHR1kFPrBuxzZxgEpHrVg8DEdiRDHD4yICGC838I1hAtYBWSIMwXnhiB1Wn8z1NBBaB8BmDA9DUc5R/j5GIfkf6JqfuSJUd6njOfbW2db+0e97mEn57vvjLlaMBYS0PAjmDCOAxJvFJkJqXGshWlT98ZzWpgGmBECnKmIpjKMfBiW5FC4r0kExBWOGdcwGG2Q9+9nQFwcAtM4eCekAiJDzlGIBCg0WZSGKM6YcZd6GC7pLLHwpffvowQAZkiJet69YW3WXt9Sj7lGweuVsw3Q9SUQPRNEAQ6MaQwe7oDkcVJxwRFh4MX4+JiGmY9FFuXaONhIGBg9RkfMw4jDVSn3yi25PkaXTzmdgCIMnWvGMySgEtysiyN4iXuJ8bKqItDMN0kP94xXYlLDlCfGhAO4irydwRvPI6nIwlkZnOX7aG3SwBwHyO6jtcAOXQSvGyB9dTQ+BXlritFFMZa2rCHKirE5ypAsmnGhjvmOH88ZJWKnHXobQy+6lGWeFHvLpR34lJm34Hni3+l3piPqAI/us/FezYA6UyClHJbLzEXfHTNTpEdvstGbxx3jdELNW6NTzFTl97ubW4enW7gkN9W+Z658gVDapzy1ZdJ9wZQZ91/eKNJP6uSlCuLhcQTo/1Om39+UaXxp1HCn84FHmelSGl96iK9NH5JxUjT9xtJoaXxzuspYU6E0kj48YOIfSG8+x8fRCB7ep1ym6Mh7bggv7UR//XjmWkyi6+di4DS+cFrmavc1yn03U5gvoJDMn74ShL/RxOULICWzqI8gXeEPyRClr4yJtyfxuMA78ocNaa8VPZmZ4/dpyROVUsFvOvZToOgIj19nmo4DQVrplZnQpa8zna2+NZ//BxaWqzY=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Account's Trades"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/accounts/{account_id}/trades"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents all trades for a given account and can be used in streaming mode. Streaming mode allows you to listen for trades for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known trade unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream trades created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./get-trades-by-account-id.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-trades-by-account-id.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-trades-by-account-id.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-trades-by-account-id.mdx b/docs/data/apis/horizon/api-reference/get-trades-by-account-id.mdx
new file mode 100644
index 000000000..c7b2f6b86
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/get-trades-by-account-id.mdx
@@ -0,0 +1,12 @@
+---
+title: "Retrieve an Account's Trades"
+openapi: "openapi/horizon/bundled.yml GET /accounts/{account_id}/trades"
+---
+
+<Tip>
+
+**Supports Streaming**
+
+This endpoint supports streaming. To read more about this, visit the [streaming section](/docs/data/apis/horizon/api-reference/structure/streaming).
+
+</Tip>
diff --git a/docs/data/apis/horizon/api-reference/get-trades-by-offer-id.ParamsDetails.json b/docs/data/apis/horizon/api-reference/get-trades-by-offer-id.ParamsDetails.json
deleted file mode 100644
index c3997c953..000000000
--- a/docs/data/apis/horizon/api-reference/get-trades-by-offer-id.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"offer_id","in":"path","required":true,"description":"A unique identifier for this offer."},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-trades-by-offer-id.RequestSchema.json b/docs/data/apis/horizon/api-reference/get-trades-by-offer-id.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/get-trades-by-offer-id.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-trades-by-offer-id.StatusCodes.json b/docs/data/apis/horizon/api-reference/get-trades-by-offer-id.StatusCodes.json
deleted file mode 100644
index 109dbfc3b..000000000
--- a/docs/data/apis/horizon/api-reference/get-trades-by-offer-id.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"base":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"counter":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operation":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","base","counter","operation"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"ledger_close_time":{"type":"string"},"offer_id":{"type":"string"},"trade_type":{"type":"string"},"liquidity_pool_fee_bp":{"type":"number","format":"uint32"},"base_liquidity_pool_id":{"type":"string"},"base_offer_id":{"type":"string"},"base_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"base_amount":{"type":"string"},"base_asset_type":{"type":"string"},"base_asset_code":{"type":"string"},"base_asset_issuer":{"type":"string"},"counter_liquidity_pool_id":{"type":"string"},"counter_offer_id":{"type":"string"},"counter_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"counter_amount":{"type":"string"},"counter_asset_type":{"type":"string"},"counter_asset_code":{"type":"string"},"counter_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"base_is_seller":{"type":"boolean"},"price":{"required":["id","paging_token","ledger_close_time","trade_type","base_amount","base_asset_type","counter_amount","counter_asset_type","base_is_seller"],"type":"object","properties":{"n":{"type":"string"},"d":{"type":"string"}},"title":"tradePrice"}}}}}}},"title":"Trade"}]},"examples":{"GetTradesByOfferId":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/offers/104078276/trades?cursor=&limit=3&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/offers/104078276/trades?cursor=107449584845914113-0&limit=3&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/offers/104078276/trades?cursor=107449468881756161-0&limit=3&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":""},"base":{"href":"https://horizon-testnet.stellar.org/accounts/GCO7OW5P2PP7WDN6YUDXUUOPAR4ZHJSDDCZTIAQRTRZHKQWV45WUPBWX"},"counter":{"href":"https://horizon-testnet.stellar.org/accounts/GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K"},"operation":{"href":"https://horizon-testnet.stellar.org/operations/107449468881756161"}},"id":"107449468881756161-0","paging_token":"107449468881756161-0","ledger_close_time":"2019-07-26T09:17:02Z","offer_id":"104078276","base_offer_id":"104078276","base_account":"GCO7OW5P2PP7WDN6YUDXUUOPAR4ZHJSDDCZTIAQRTRZHKQWV45WUPBWX","base_amount":"4433.2000000","base_asset_type":"native","counter_offer_id":"4719135487309144065","counter_account":"GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K","counter_amount":"443.3200000","counter_asset_type":"credit_alphanum4","counter_asset_code":"BB1","counter_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","base_is_seller":true,"price":{"n":1,"d":10}}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-trades-by-offer-id.api.mdx b/docs/data/apis/horizon/api-reference/get-trades-by-offer-id.api.mdx
deleted file mode 100644
index ff4c05b25..000000000
--- a/docs/data/apis/horizon/api-reference/get-trades-by-offer-id.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: get-trades-by-offer-id
-title: "Retrieve an Offer's Trades"
-description: "This endpoint represents all trades for a given offer and can be used in streaming mode. Streaming mode allows you to listen for trades for this offer as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known trade unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream trades created since your request time."
-sidebar_label: "Retrieve an Offer's Trades"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWuluGzkSfpUCf0wO6LR12AIGu77i2PHGnliOEyeGQzVLEmM22SHZlj2GgH2Nfb19kkWxu+WWJTsHBtjMzuqPIHWxWPzqZFXfMs9HjvU+sMPhEK1j5xUm0EVWJl4azXqsP5YOUIvESO3BYmLRofYOuFLgLRfoYGgscBjJK9RgiA9wLSDiGgYIqUMBUoPzFnks9QhiI7AGx3O/iZ2ZOLgxKXgDSjqPOjAu7eFJlnwDB36MN8AtAhcCBa3yY4Rjj0pxCwrFCG0N9oYQcaWWyVCBl8bK342GiVQKnOfWA/eBDXKrJDoPl9pMdCYEpFqhc8AhSq0zFqQDh75CnCdjGY0h4g5B+jK/oTUx+DH3+aIabN7QKk9S0E45ryuuUqRDaDOpBBgIv0zgAoPIIvcowEkdIdFYsPglJTG9jLHGKswkaDmpbk+wHttF3w9LN2+CfvcEq7CEWx6jJ233PtwyzWNkPRZgvZBEIEnvCfdjVmHEX1oUrOdtiveNYwNSLb+kCFKg9nIo0d5TVI1NK7M9sqMWO3xJ0d7MbTHkyi3ZQ6fxAG0GYjBDRzhxcAlGcigjUCYKZyZFcIiMUhiF32YIFl1itEMXbFI6SNJgDbleEBI+knp04c0l6lwLZggcLEbGCsLURWOMOevdMn+T0Dmk9jhCOghe8zhRyHqdTqPTaXZb3bX19nqz0Z6Wjm2swO8/tUAnR5oX5yBRA6M7a8skdODGJlUCeJIgtzU4DDwcSB2pVCB84i76BE+5i1ALqUfPwFj4RNt9gqf0lf8dfCVojttRGqP2IJ3+9z//5XMr9yBwyFOV4R/YLoXHeSv1iNDRaUyxhbuIZQdk52VglIyl/05g+mOEmF/LOI0LwwhazqCw6FOrUdSA6AL/4EeW6xFmOm+S8CuNBlSBa0iTBG1OGAxMOhhzKyIjspBRhAgy6wTt0NiYk/dZ5M5o9whohQJRLGDXbHyrXTUb0+l5hV1XXZokxnpXncWwwiVnFk6cVhoN+prH7DiNInSOVVhktEftiYQniZKZ39Q/O6K7LUnElTochviQy2YGnzEiZSWWYoyX2X4XSupLVzrDA3QO1fDrVGOLw2WGFFD3wWL0JZtWmMc4UQRtiXpgjEKu2XRaNqIPGdPzCvPSKyzx0HjtfzKREotXP5VIUyIr/joIqib//YpNYDxAyslfP0rutyVCbi2nMCA9xt9gV39i+xtwhz+ZSJFJtUf7k0k1q2l+KrnuEQUDy5V6B2RZ+PNphUmxTLqCsRQhCJQKkseo5+imFZZVvBeRMg4vqB5cXExgFnXesoehzrzI/l7yWMkvqRTS31wkxqiLIeLFIClRZvm4DHcqtV9dKaz94h6DB6QIpI/KGSh4FFBeBlHCvUdLqW/3w0b1rFFdP79tt6cl8LgQllLijFm8nNfsuXPoH0amREOVw9dopHPpnJvdUeWW841QFdSPolUQ/VGAzfg9jNmM5HHY5skeRG6e7CHwfkTt0l04VGqO3SwMUHCREWZ56s7TZXaJKjnfMt+bc6Z5I1s0qQVMlyK4IDPFpEfD4ZL4Ma2wZVZSSvNB7qNw8mn2uXsWbpNsSqEsL1HDPkvumb1bFi5T80m6SMNZnGZj7xPXq9fHWZFd9ei8Rl9z2SW+ZuyoHkzb1ZuNVqO7ttLt1LPL8N+yy+Svv4Ta/dfVX8Ll6Fe6apRquz9un2aj22qtt9daa632erPVbK5WG8v3Loq4P3rvVmdtba3ZbXeanebC3uFyRZqaK75m5dWHR5RQrkW+Q+Y8mrj67tZh9/C0fbRydNQ93X7deX+y/e7k5PBo403r7OX+8fb21ll/b+O3N/03Zy9f/Xb6ttU+PTnaPH13r+D4oa23V7f235/0zzbed/Z/e9Ha2tnrnHXfnrYPO29f774662++P9nZ6h/uH+1s9ze7eysvz46P9lZeLVQV36OrYh3p675eggooDLNlOrsfNx6kWpLK2UqjuV5tdKsrnX5jvdfs9horZ6ycz9nMfNhCDl18NksG7If1dy91slZrdbW20gifJUGux6ibcVWOdiUBW93menO13VrrrjbWm61Wo9NmS1IX+2GVL+YtEri2ulLIuyxnsciikP6Cq2TMdRq3FuiypMU2N5sLj4pExXa32/udlwcv2p1O511r4+yg/6L/7uB9q7PfPj7t7rx782rzYOf90f7R6urx6uo/3p3tvu1snb54vRjx8yv/LC9p1muGgB76BNNZvMZrj9qRkQbfv8Qb1lveRKgUYZo4U6shRj82pJER+iynjlmPFSHqtlDZNI9R1MdAe1V0E1Orvs2P2LLGTj+jg9foJ8Zehrvmco7D1KcWv4Xni4ISdMH1nFpOQxPSYJ7Y8jYPwYHWZasbtUaNtOrSOOb25o4KEmuupAg9RXjZ7x/BxtEe9XUE95yaRuVGdL5rDfY8SD1C57NWpMVqAC40srOViTUijVDA4GYZi6y9SbX1rFWF3FHP1RuIjHZpjMVSfoWWjxBKXR6wqIIDFq3yUjuraqxETb3lIMiszZ8FuqyHP7iZCbRlLFKLTbpw8tI5BlaKEcIA/QRR0/bZaedXHllD9YoDJS8RJtSf964CAiPU3nIlf0cBeB2NqW3nKoFD8CnIfCpINGvNeQMuHYQOnuXa8dD7dRUIHUVSUR49YMAVHbZCDdC8s45XYZgR5CivDh3m2cragmX91S3hQ1mh508L9xR4hYoypJvLmbnY9chYrGoj8Nlfyno+6o+62C6fivHQkUUBV5JDdPLmoAIcBtZMHNqwg9FYtP1nWB9vv3JfxVqYyNW9McrVnbh0hLQBi2RO2bzJUNl+Lf0N8Q9DpCQDtAITDJ30OEYtwgyKgOKaNgapnUcuaFHML2l6JaTFyAcd0ojNhXMGtY5SKRAyjxmgg7GZBEhELDVN9mhcmJl4MMcCG9oiNNefWhxmxhzOvz076RPYVGZ0h8FkMpk//IyyOlBmVOdVjZOqS3WVstAYq3n+eBb6+c6Qm/DocmRNqgUYfd8bMtux0Vh6jHxquQIZk89jHDRv8uZ/zD/TDC9LHTBI4+RZDV7QiFBnvRD6mw9MSnOAICIBmO83Mw0jkPJ9BaIxRpdA1OXzh+nCLkF7B8BI+nE6qEUmruc4FN/FUesDZQb1mEtd3955u3NweLT3ercWi2dBXZs4NBZJ8QMcSU2TiicOJsZ6mi9JH2rdfFJJYUAGITAam2w8EuQjt4TXRvxIIABhojA3CRj14PnzCYKgMainsbOxDsGmWpMQBVCksiwMcZqyasEVuUs5Ssxs6fnzLABgmBZypW4C67D24oorKcIBLxZyG5LpWwQ/MeCQhqaenEdHaHUeVARGJk1Ujk9MYVjGVGBx7YOBDUyAUUk+kIo8jlaVzKs2Z/rkXTHXfIQOJBnXRFcg4RZFVdAQujAvM5w/qkm8jEPQoz3zlRTUKOSZIWhE4eDpBJ8oBSXPoqEVTbM/si2ehHRA7D6yGXZkItTIQBu7w+Ex2qtQds6KsbJmA1HVDEMqI7Js2MSjcA/PB36F2GWDfkGul13EKveKvfnSDmMuw1NUyvy9/Cy0JiPU2R0232sj4dEYYaVGtf3dfHr2pJo9udsxDyc8PA1nypm6+sHe1s7r4x1aUhv7WIVrXmKcj7kubfkGvZV4FUJm6IM8cdAvquS5+uH2bhL3/zcs/lxvWOQXQ4/Xvp4oLkOjMFjRbX5Z+pBdyknpvdJrFfl96bzCxsZ5Iru9pXB/YtV0Sn9nE3C6RQnp+EA9NAMvG89//+2IpXhkF87Z+x75FZOFC933HO5P8xLEIygUr3/8IAj/Qy88PAJS8SrIHUjn9MNKQuk7feLpm7xb/wy+5QWlB+Qq5tH6pizWTKmFX4de+Bg56fiu1bIRRZiUz7PwtsVcq2V3p8+m0/8AzZ3E+Q==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Offer's Trades"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/offers/{offer_id}/trades"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents all trades for a given offer and can be used in streaming mode. Streaming mode allows you to listen for trades for this offer as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known trade unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream trades created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./get-trades-by-offer-id.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-trades-by-offer-id.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-trades-by-offer-id.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-trades-by-offer-id.mdx b/docs/data/apis/horizon/api-reference/get-trades-by-offer-id.mdx
new file mode 100644
index 000000000..51067d540
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/get-trades-by-offer-id.mdx
@@ -0,0 +1,12 @@
+---
+title: "Retrieve an Offer's Trades"
+openapi: "openapi/horizon/bundled.yml GET /offers/{offer_id}/trades"
+---
+
+<Tip>
+
+**Supports Streaming**
+
+This endpoint supports streaming. To read more about this, visit the [streaming section](/docs/data/apis/horizon/api-reference/structure/streaming).
+
+</Tip>
diff --git a/docs/data/apis/horizon/api-reference/get-transactions-by-account-id.ParamsDetails.json b/docs/data/apis/horizon/api-reference/get-transactions-by-account-id.ParamsDetails.json
deleted file mode 100644
index c7a943fc8..000000000
--- a/docs/data/apis/horizon/api-reference/get-transactions-by-account-id.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"account_id","in":"path","required":true,"description":"This account’s public key encoded in a base32 string representation.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-transactions-by-account-id.RequestSchema.json b/docs/data/apis/horizon/api-reference/get-transactions-by-account-id.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/get-transactions-by-account-id.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-transactions-by-account-id.StatusCodes.json b/docs/data/apis/horizon/api-reference/get-transactions-by-account-id.StatusCodes.json
deleted file mode 100644
index c44115e5f..000000000
--- a/docs/data/apis/horizon/api-reference/get-transactions-by-account-id.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"memo":{"type":"string"},"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"account":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"ledger":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","account","ledger","operations","effects","precedes","succeeds","transaction"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"successful":{"type":"boolean"},"hash":{"type":"string"},"ledger":{"type":"integer","format":"int32"},"created_at":{"type":"string"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"account_muxed":{"type":"string"},"account_muxed_id":{"type":"string"},"source_account_sequence":{"type":"string"},"fee_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed_id":{"type":"string"},"fee_charged":{"type":"string"},"max_fee":{"type":"string"},"operation_count":{"type":"integer","format":"int32"},"envelope_xdr":{"type":"string"},"result_xdr":{"type":"string"},"result_meta_xdr":{"type":"string"},"fee_meta_xdr":{"type":"string"},"memo_type":{"type":"string"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"},"preconditions":{"type":"object","properties":{"timebounds":{"type":"object","properties":{"min_time":{"type":"string"},"max_time":{"type":"string"}},"title":"TransactionPreconditionsTimebounds"},"ledgerbounds":{"type":"object","properties":{"min_ledger":{"type":"string"},"max_ledger":{"type":"string"}},"title":"TransactionPreconditionsLedgerbounds"},"min_account_sequence":{"type":"string"},"min_account_sequence_age":{"type":"string"},"min_account_sequence_ledger_gap":{"type":"integer","format":"uint32"},"extra_signers":{"type":"array","items":{"type":"string"}}},"title":"TransactionPreconditions"},"fee_bump_transaction":{"type":"object","properties":{"hash":{"type":"string","title":"hash"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"}},"title":"FeeBumpTransaction"},"inner_transaction":{"type":"object","properties":{"hash":{"type":"string","title":"hash"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"},"max_fee":{"type":"string"}},"title":"InnerTransaction"}},"required":["id","paging_token","successful","hash","ledger","created_at","source_account","source_account_sequence","fee_account","fee_charged","max_fee","operation_count","envelope_xdr","result_xdr","result_meta_xdr","memo_type","signatures"]}}}}},"title":"Transaction"}]},"examples":{"RetrieveAnAccountsTransactions":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/accounts/GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU/transactions?cursor=&limit=10&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/accounts/GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU/transactions?cursor=122152984477229056&limit=10&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/accounts/GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU/transactions?cursor=94658837230923776&limit=10&order=desc"}},"_embedded":{"records":[{"memo":"","memo_bytes":"","_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/4826a3d41a5a795bf795767d0fb5e39c4abbcf695cf888b3578aa126b5b257ee"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GBYSOAM7D42RMUN4LCKCFYNXZU3F7TJVKD2NMR672J4372BCH6DE4BKR"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/22039478"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/4826a3d41a5a795bf795767d0fb5e39c4abbcf695cf888b3578aa126b5b257ee/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/4826a3d41a5a795bf795767d0fb5e39c4abbcf695cf888b3578aa126b5b257ee/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=94658837230923776"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=94658837230923776"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/4826a3d41a5a795bf795767d0fb5e39c4abbcf695cf888b3578aa126b5b257ee"}},"id":"4826a3d41a5a795bf795767d0fb5e39c4abbcf695cf888b3578aa126b5b257ee","paging_token":"94658837230923776","successful":true,"hash":"4826a3d41a5a795bf795767d0fb5e39c4abbcf695cf888b3578aa126b5b257ee","ledger":22039478,"created_at":"2019-01-18T14:40:47Z","source_account":"GBYSOAM7D42RMUN4LCKCFYNXZU3F7TJVKD2NMR672J4372BCH6DE4BKR","source_account_sequence":"90296735301107721","fee_account":"GBYSOAM7D42RMUN4LCKCFYNXZU3F7TJVKD2NMR672J4372BCH6DE4BKR","fee_charged":"100","max_fee":"100","operation_count":1,"envelope_xdr":"AAAAAHEnAZ8fNRZRvFiUIuG3zTZfzTVQ9NZH39J5v+giP4ZOAAAAZAFAzGcAAAAJAAAAAQAAAAAAAAAAAAAAAFxB5cMAAAABAAAAAAAAAAEAAAAAAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAAC+vCAAAAAAAAAAAEiP4ZOAAAAQO421wcb/JYfBpnYEJzHpMyQnrM8rHd4PUoyHXpPlvQAUGzARqwbX8hcLSM4tlk51AwbuZOaZfWCaFQfzFZJuAA=","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAVBLtgAAAAAAAAAAcScBnx81FlG8WJQi4bfNNl/NNVD01kff0nm/6CI/hk4AAAAAI9MEZAFAzGcAAAAIAAAAAAAAAAEAAAAA7Nxp7lmV7taqQfqoSP+tlqjOHWeANaQYFqhDkCQERZQAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAVBLtgAAAAAAAAAAcScBnx81FlG8WJQi4bfNNl/NNVD01kff0nm/6CI/hk4AAAAAI9MEZAFAzGcAAAAJAAAAAAAAAAEAAAAA7Nxp7lmV7taqQfqoSP+tlqjOHWeANaQYFqhDkCQERZQAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAAAwAAAAMBUEu2AAAAAAAAAABxJwGfHzUWUbxYlCLht802X801UPTWR9/Seb/oIj+GTgAAAAAj0wRkAUDMZwAAAAkAAAAAAAAAAQAAAADs3GnuWZXu1qpB+qhI/62WqM4dZ4A1pBgWqEOQJARFlAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBUEu2AAAAAAAAAABxJwGfHzUWUbxYlCLht802X801UPTWR9/Seb/oIj+GTgAAAAAg2BPkAUDMZwAAAAkAAAAAAAAAAQAAAADs3GnuWZXu1qpB+qhI/62WqM4dZ4A1pBgWqEOQJARFlAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAABUEu2AAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAAC+vCAAVBLtgAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMBUCemAAAAAAAAAABxJwGfHzUWUbxYlCLht802X801UPTWR9/Seb/oIj+GTgAAAAAj0wTIAUDMZwAAAAgAAAAAAAAAAQAAAADs3GnuWZXu1qpB+qhI/62WqM4dZ4A1pBgWqEOQJARFlAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBUEu2AAAAAAAAAABxJwGfHzUWUbxYlCLht802X801UPTWR9/Seb/oIj+GTgAAAAAj0wRkAUDMZwAAAAgAAAAAAAAAAQAAAADs3GnuWZXu1qpB+qhI/62WqM4dZ4A1pBgWqEOQJARFlAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"text","signatures":["7jbXBxv8lh8GmdgQnMekzJCeszysd3g9SjIdek+W9ABQbMBGrBtfyFwtIzi2WTnUDBu5k5pl9YJoVB/MVkm4AA=="],"preconditions":{"timebounds":{"min_time":"0","max_time":"1547822531"}}},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/ec8d5d6e64dc4df1bc8d8c200e048d6740d1e9f680612baeda0f78678c9ca666"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GAL62GEDMQFWRQLZXJKT4WFRFTIKPPTC2ALSD45VMK7ZUUZVBXWWXUAX"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/23895910"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/ec8d5d6e64dc4df1bc8d8c200e048d6740d1e9f680612baeda0f78678c9ca666/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/ec8d5d6e64dc4df1bc8d8c200e048d6740d1e9f680612baeda0f78678c9ca666/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=102632151958179840"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=102632151958179840"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/ec8d5d6e64dc4df1bc8d8c200e048d6740d1e9f680612baeda0f78678c9ca666"}},"id":"ec8d5d6e64dc4df1bc8d8c200e048d6740d1e9f680612baeda0f78678c9ca666","paging_token":"102632151958179840","successful":true,"hash":"ec8d5d6e64dc4df1bc8d8c200e048d6740d1e9f680612baeda0f78678c9ca666","ledger":23895910,"created_at":"2019-05-17T14:43:53Z","source_account":"GAL62GEDMQFWRQLZXJKT4WFRFTIKPPTC2ALSD45VMK7ZUUZVBXWWXUAX","source_account_sequence":"93143259236270083","fee_account":"GAL62GEDMQFWRQLZXJKT4WFRFTIKPPTC2ALSD45VMK7ZUUZVBXWWXUAX","fee_charged":"100","max_fee":"100","operation_count":1,"envelope_xdr":"AAAAABftGINkC2jBebpVPlixLNCnvmLQFyHztWK/mlM1De1rAAAAZAFK6U0AAAADAAAAAQAAAAAAAAAAAAAAAFzeydEAAAAAAAAAAQAAAAAAAAABAAAAAGpZ5X06Hz48sKzzVFo//X67YFenBLxaxzuJcPuXebqxAAAAAAAAAALLQXgAAAAAAAAAAAE1De1rAAAAQLFFYK9rGA2Um2Vwguj4Ra3T6gaeturf4Qw/0LcG/qa/oXZeu6s7ZrB3wVVJu0m123Z7zirYoo576IS8agzLKQQ=","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAABAAAAAAAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAWyfZgAAAAAAAAAAF+0Yg2QLaMF5ulU+WLEs0Ke+YtAXIfO1Yr+aUzUN7WsAAAAC1fwL1AFK6U0AAAACAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAWyfZgAAAAAAAAAAF+0Yg2QLaMF5ulU+WLEs0Ke+YtAXIfO1Yr+aUzUN7WsAAAAC1fwL1AFK6U0AAAADAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAABAAAAAMBUEu2AAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAAC+vCAAVBLtgAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBbJ9mAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAALOPGiAAVBLtgAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAMBbJ9mAAAAAAAAAAAX7RiDZAtowXm6VT5YsSzQp75i0Bch87Viv5pTNQ3tawAAAALV/AvUAUrpTQAAAAMAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBbJ9mAAAAAAAAAAAX7RiDZAtowXm6VT5YsSzQp75i0Bch87Viv5pTNQ3tawAAAAAKupPUAUrpTQAAAAMAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMBS+8PAAAAAAAAAAAX7RiDZAtowXm6VT5YsSzQp75i0Bch87Viv5pTNQ3tawAAAALV/Aw4AUrpTQAAAAIAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBbJ9mAAAAAAAAAAAX7RiDZAtowXm6VT5YsSzQp75i0Bch87Viv5pTNQ3tawAAAALV/AvUAUrpTQAAAAIAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"none","signatures":["sUVgr2sYDZSbZXCC6PhFrdPqBp626t/hDD/Qtwb+pr+hdl67qztmsHfBVUm7SbXbdnvOKtiijnvohLxqDMspBA=="],"preconditions":{"timebounds":{"min_time":"0","max_time":"1558104529"}}},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/5427d2719db9ca33706e9c06c04f91bd353e0e6f5185c6f47b517b338b8d81b2"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/27114571"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/5427d2719db9ca33706e9c06c04f91bd353e0e6f5185c6f47b517b338b8d81b2/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/5427d2719db9ca33706e9c06c04f91bd353e0e6f5185c6f47b517b338b8d81b2/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=116456195690164224"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=116456195690164224"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/5427d2719db9ca33706e9c06c04f91bd353e0e6f5185c6f47b517b338b8d81b2"}},"id":"5427d2719db9ca33706e9c06c04f91bd353e0e6f5185c6f47b517b338b8d81b2","paging_token":"116456195690164224","successful":true,"hash":"5427d2719db9ca33706e9c06c04f91bd353e0e6f5185c6f47b517b338b8d81b2","ledger":27114571,"created_at":"2019-12-04T22:03:41Z","source_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","source_account_sequence":"94658837230911489","fee_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","fee_charged":"100","max_fee":"100","operation_count":1,"envelope_xdr":"AAAAAGpZ5X06Hz48sKzzVFo//X67YFenBLxaxzuJcPuXebqxAAAAZAFQS7YAAAABAAAAAQAAAAAAAAAAAAAAAF3oLZMAAAAAAAAAAQAAAAAAAAABAAAAAARD8QZr6wa97ii5JeeuMJEXycVsEO1dBekjRTcI9AadAAAAAAAAAAABMS0AAAAAAAAAAAGXebqxAAAAQND+muz3883MoHmTtuhsDb4awF1U3EDJ2FQn8Ia2C9L+Rz62Z9EvH8rl81d3oPxrjUnedZmjOnptn6Agm5alHwc=","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAABAAAAAAAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAZ28SwAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACzjxoHAFQS7YAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAZ28SwAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACzjxoHAFQS7YAAAABAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAABAAAAAMBnbwPAAAAAAAAAAAEQ/EGa+sGve4ouSXnrjCRF8nFbBDtXQXpI0U3CPQGnQAAAABxZQNiAZtraAAAABsAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBnbxLAAAAAAAAAAAEQ/EGa+sGve4ouSXnrjCRF8nFbBDtXQXpI0U3CPQGnQAAAAByljBiAZtraAAAABsAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAMBnbxLAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAALOPGgcAVBLtgAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBnbxLAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAALNCzscAVBLtgAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMBbJ9mAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAALOPGiAAVBLtgAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBnbxLAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAALOPGgcAVBLtgAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"none","signatures":["0P6a7PfzzcygeZO26GwNvhrAXVTcQMnYVCfwhrYL0v5HPrZn0S8fyuXzV3eg/GuNSd51maM6em2foCCblqUfBw=="],"preconditions":{"timebounds":{"min_time":"0","max_time":"1575497107"}}},{"memo":"hello universe","memo_bytes":"aGVsbG8gdW5pdmVyc2U=","_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/ef0fe04ac3c7de7228ca2598886059868ad05c224a041e8b2d9ee2a8a9dd6894"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/27984461"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/ef0fe04ac3c7de7228ca2598886059868ad05c224a041e8b2d9ee2a8a9dd6894/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/ef0fe04ac3c7de7228ca2598886059868ad05c224a041e8b2d9ee2a8a9dd6894/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=120192344791343104"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=120192344791343104"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/ef0fe04ac3c7de7228ca2598886059868ad05c224a041e8b2d9ee2a8a9dd6894"}},"id":"ef0fe04ac3c7de7228ca2598886059868ad05c224a041e8b2d9ee2a8a9dd6894","paging_token":"120192344791343104","successful":true,"hash":"ef0fe04ac3c7de7228ca2598886059868ad05c224a041e8b2d9ee2a8a9dd6894","ledger":27984461,"created_at":"2020-01-29T19:43:59Z","source_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","source_account_sequence":"94658837230911490","fee_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","fee_charged":"100","max_fee":"100","operation_count":1,"envelope_xdr":"AAAAAGpZ5X06Hz48sKzzVFo//X67YFenBLxaxzuJcPuXebqxAAAAZAFQS7YAAAACAAAAAQAAAAAAAAAAAAAAAF4x4NYAAAABAAAADmhlbGxvIHVuaXZlcnNlAAAAAAABAAAAAAAAAAAAAAAAMOWtdEZJweWBDrIVGDQOVodinrlXbfzBfquR7AFtxW4AAAAAATEtAAAAAAAAAAABl3m6sQAAAEDwdDlpQv5IfweTkLjytpWIa+bpQv7BAHRFpMCHscM3g+WBKjXPVEnSP1BghLuy3uhvgv4LnCkI+gFEDZxwV/YF","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAasCTQAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACzQs6uAFQS7YAAAABAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAasCTQAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACzQs6uAFQS7YAAAACAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAAAwAAAAMBqwJNAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAALNCzq4AVBLtgAAAAIAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBqwJNAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAALL2g24AVBLtgAAAAIAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAABqwJNAAAAAAAAAAAw5a10RknB5YEOshUYNA5Wh2KeuVdt/MF+q5HsAW3FbgAAAAABMS0AAasCTQAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMBnbxLAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAALNCzscAVBLtgAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBqwJNAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAALNCzq4AVBLtgAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"text","signatures":["8HQ5aUL+SH8Hk5C48raViGvm6UL+wQB0RaTAh7HDN4PlgSo1z1RJ0j9QYIS7st7ob4L+C5wpCPoBRA2ccFf2BQ=="],"preconditions":{"timebounds":{"min_time":"0","max_time":"1580327126"}}},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/c1cb850f413e4038c4120bd9badc07bb8ef85a46649a4d5c9c16e578a2d30589"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/27984467"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/c1cb850f413e4038c4120bd9badc07bb8ef85a46649a4d5c9c16e578a2d30589/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/c1cb850f413e4038c4120bd9badc07bb8ef85a46649a4d5c9c16e578a2d30589/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=120192370561220608"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=120192370561220608"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/c1cb850f413e4038c4120bd9badc07bb8ef85a46649a4d5c9c16e578a2d30589"}},"id":"c1cb850f413e4038c4120bd9badc07bb8ef85a46649a4d5c9c16e578a2d30589","paging_token":"120192370561220608","successful":true,"hash":"c1cb850f413e4038c4120bd9badc07bb8ef85a46649a4d5c9c16e578a2d30589","ledger":27984467,"created_at":"2020-01-29T19:44:36Z","source_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","source_account_sequence":"94658837230911491","fee_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","fee_charged":"100","max_fee":"100","operation_count":1,"envelope_xdr":"AAAAAGpZ5X06Hz48sKzzVFo//X67YFenBLxaxzuJcPuXebqxAAAAZAFQS7YAAAADAAAAAQAAAAAAAAAAAAAAAF4x4PoAAAAAAAAAAQAAAAAAAAABAAAAADDlrXRGScHlgQ6yFRg0DlaHYp65V238wX6rkewBbcVuAAAAAAAAAAB3NZQAAAAAAAAAAAGXebqxAAAAQMzdIubro9XQUTkhf0YbDBNM5tqC/zS7fGb0BLFq+QxXT7VAS7dDMno9A2f1df4nnyeHqVl+CuKcpwwwS04JSgE=","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAABAAAAAAAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAasCUwAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACy9oNVAFQS7YAAAACAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAasCUwAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACy9oNVAFQS7YAAAADAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAABAAAAAMBqwJNAAAAAAAAAAAw5a10RknB5YEOshUYNA5Wh2KeuVdt/MF+q5HsAW3FbgAAAAABMS0AAasCTQAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBqwJTAAAAAAAAAAAw5a10RknB5YEOshUYNA5Wh2KeuVdt/MF+q5HsAW3FbgAAAAB4ZsEAAasCTQAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAMBqwJTAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAALL2g1UAVBLtgAAAAMAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBqwJTAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAJUpHlUAVBLtgAAAAMAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMBqwJNAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAALL2g24AVBLtgAAAAIAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBqwJTAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAALL2g1UAVBLtgAAAAIAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"none","signatures":["zN0i5uuj1dBROSF/RhsME0zm2oL/NLt8ZvQEsWr5DFdPtUBLt0Myej0DZ/V1/iefJ4epWX4K4pynDDBLTglKAQ=="],"preconditions":{"timebounds":{"min_time":"0","max_time":"1580327162"}}},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/e0f3d6e327a6de01223a8f0e2b88e97abeaf1f514f95f8e7c55f18b951f09dbe"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/28000615"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/e0f3d6e327a6de01223a8f0e2b88e97abeaf1f514f95f8e7c55f18b951f09dbe/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/e0f3d6e327a6de01223a8f0e2b88e97abeaf1f514f95f8e7c55f18b951f09dbe/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=120261725693136896"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=120261725693136896"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/e0f3d6e327a6de01223a8f0e2b88e97abeaf1f514f95f8e7c55f18b951f09dbe"}},"id":"e0f3d6e327a6de01223a8f0e2b88e97abeaf1f514f95f8e7c55f18b951f09dbe","paging_token":"120261725693136896","successful":true,"hash":"e0f3d6e327a6de01223a8f0e2b88e97abeaf1f514f95f8e7c55f18b951f09dbe","ledger":28000615,"created_at":"2020-01-30T21:45:07Z","source_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","source_account_sequence":"94658837230911492","fee_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","fee_charged":"100","max_fee":"100","operation_count":1,"envelope_xdr":"AAAAAGpZ5X06Hz48sKzzVFo//X67YFenBLxaxzuJcPuXebqxAAAAZAFQS7YAAAAEAAAAAQAAAAAAAAAAAAAAAF4zTrgAAAAAAAAAAQAAAAAAAAABAAAAABhkaLZ/GHrh4vaarKkeK7PX2c581NvMfPvtTyATuVziAAAAAAAAAAAF9eEAAAAAAAAAAAGXebqxAAAAQB9XBu17Olvry7c8CqLJXqvK5csy2r3lGiP3HyR5JcryL8QQjSuwGr/LEFFKIS5Afo/jh9fCzGzJzZQ4DN1KPgs=","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAABAAAAAAAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAatBZwAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACVKR48AFQS7YAAAADAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAatBZwAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACVKR48AFQS7YAAAAEAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAABAAAAAMBq0EQAAAAAAAAAAAYZGi2fxh64eL2mqypHiuz19nOfNTbzHz77U8gE7lc4gAAAAACYljUAatBDAAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBq0FnAAAAAAAAAAAYZGi2fxh64eL2mqypHiuz19nOfNTbzHz77U8gE7lc4gAAAAAIWDnUAatBDAAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAMBq0FnAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAJUpHjwAVBLtgAAAAQAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBq0FnAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAJOrpfwAVBLtgAAAAQAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMBqwJTAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAJUpHlUAVBLtgAAAAMAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBq0FnAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAJUpHjwAVBLtgAAAAMAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"none","signatures":["H1cG7Xs6W+vLtzwKosleq8rlyzLaveUaI/cfJHklyvIvxBCNK7Aav8sQUUohLkB+j+OH18LMbMnNlDgM3Uo+Cw=="],"preconditions":{"timebounds":{"min_time":"0","max_time":"1580420792"}}},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/329ae48814ae29ed6d9c0bb6e398932e6a178cac21623b63fbf5d8245261c041"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/28000619"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/329ae48814ae29ed6d9c0bb6e398932e6a178cac21623b63fbf5d8245261c041/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/329ae48814ae29ed6d9c0bb6e398932e6a178cac21623b63fbf5d8245261c041/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=120261742872928256"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=120261742872928256"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/329ae48814ae29ed6d9c0bb6e398932e6a178cac21623b63fbf5d8245261c041"}},"id":"329ae48814ae29ed6d9c0bb6e398932e6a178cac21623b63fbf5d8245261c041","paging_token":"120261742872928256","successful":true,"hash":"329ae48814ae29ed6d9c0bb6e398932e6a178cac21623b63fbf5d8245261c041","ledger":28000619,"created_at":"2020-01-30T21:45:29Z","source_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","source_account_sequence":"94658837230911493","fee_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","fee_charged":"100","max_fee":"100","operation_count":1,"envelope_xdr":"AAAAAGpZ5X06Hz48sKzzVFo//X67YFenBLxaxzuJcPuXebqxAAAAZAFQS7YAAAAFAAAAAQAAAAAAAAAAAAAAAF4zTtEAAAAAAAAAAQAAAAAAAAABAAAAABhkaLZ/GHrh4vaarKkeK7PX2c581NvMfPvtTyATuVziAAAAAAAAAAAO5rKAAAAAAAAAAAGXebqxAAAAQFaUIoWWXLurZRFty6iBHmm65K2w5EZjldQcMsB/KeQl1Rh0UkZ7Q44JCDCvntnIhWfkl1Qipr6jZk/I4c+pjw8=","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAABAAAAAAAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAatBawAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACTq6XjAFQS7YAAAAEAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAatBawAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACTq6XjAFQS7YAAAAFAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAABAAAAAMBq0FnAAAAAAAAAAAYZGi2fxh64eL2mqypHiuz19nOfNTbzHz77U8gE7lc4gAAAAAIWDnUAatBDAAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBq0FrAAAAAAAAAAAYZGi2fxh64eL2mqypHiuz19nOfNTbzHz77U8gE7lc4gAAAAAXPuxUAatBDAAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAMBq0FrAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAJOrpeMAVBLtgAAAAUAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBq0FrAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAI/x+UMAVBLtgAAAAUAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMBq0FnAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAJOrpfwAVBLtgAAAAQAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBq0FrAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAJOrpeMAVBLtgAAAAQAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"none","signatures":["VpQihZZcu6tlEW3LqIEeabrkrbDkRmOV1BwywH8p5CXVGHRSRntDjgkIMK+e2ciFZ+SXVCKmvqNmT8jhz6mPDw=="],"preconditions":{"timebounds":{"min_time":"0","max_time":"1580420817"}}},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/2b8a77c7e42997280b8454e39bd7c681c58ab5b7cc288ff836c1c4b6152dccfe"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/28210091"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/2b8a77c7e42997280b8454e39bd7c681c58ab5b7cc288ff836c1c4b6152dccfe/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/2b8a77c7e42997280b8454e39bd7c681c58ab5b7cc288ff836c1c4b6152dccfe/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=121161418262413312"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=121161418262413312"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/2b8a77c7e42997280b8454e39bd7c681c58ab5b7cc288ff836c1c4b6152dccfe"}},"id":"2b8a77c7e42997280b8454e39bd7c681c58ab5b7cc288ff836c1c4b6152dccfe","paging_token":"121161418262413312","successful":true,"hash":"2b8a77c7e42997280b8454e39bd7c681c58ab5b7cc288ff836c1c4b6152dccfe","ledger":28210091,"created_at":"2020-02-13T18:54:50Z","source_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","source_account_sequence":"94658837230911494","fee_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","fee_charged":"100","max_fee":"100","operation_count":1,"envelope_xdr":"AAAAAGpZ5X06Hz48sKzzVFo//X67YFenBLxaxzuJcPuXebqxAAAAZAFQS7YAAAAGAAAAAQAAAAAAAAAAAAAAAF5Fm9EAAAAAAAAAAQAAAAAAAAAAAAAAADKjrtXFaprjtdoV8mYex4557fEGVYkp83K0vfUwEyVnAAAAAAvrwgAAAAAAAAAAAZd5urEAAABAKCO0IAmQ8hUJVMMfIxu1Q/DgZebmn09dROCFCKSEUZGYuzqlfJPYMrcOJRtf41wwMFK8Wj1g70EAw+ZDhKhJDA==","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAa5zqwAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACP8fkqAFQS7YAAAAFAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAa5zqwAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACP8fkqAFQS7YAAAAGAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAAAwAAAAMBrnOrAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAI/x+SoAVBLtgAAAAYAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBrnOrAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAIz3CKoAVBLtgAAAAYAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAABrnOrAAAAAAAAAAAyo67VxWqa47XaFfJmHseOee3xBlWJKfNytL31MBMlZwAAAAAL68IAAa5zqwAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMBq0FrAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAI/x+UMAVBLtgAAAAUAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBrnOrAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAI/x+SoAVBLtgAAAAUAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"none","signatures":["KCO0IAmQ8hUJVMMfIxu1Q/DgZebmn09dROCFCKSEUZGYuzqlfJPYMrcOJRtf41wwMFK8Wj1g70EAw+ZDhKhJDA=="],"preconditions":{"timebounds":{"min_time":"0","max_time":"1581620177"}}},{"memo":"hello world","memo_bytes":"aGVsbG8gd29ybGQ=","_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/729e441893075fe40b6a6db0acbe38dd39243417cc8717f968414934331a6260"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/28211677"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/729e441893075fe40b6a6db0acbe38dd39243417cc8717f968414934331a6260/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/729e441893075fe40b6a6db0acbe38dd39243417cc8717f968414934331a6260/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=121168230080335872"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=121168230080335872"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/729e441893075fe40b6a6db0acbe38dd39243417cc8717f968414934331a6260"}},"id":"729e441893075fe40b6a6db0acbe38dd39243417cc8717f968414934331a6260","paging_token":"121168230080335872","successful":true,"hash":"729e441893075fe40b6a6db0acbe38dd39243417cc8717f968414934331a6260","ledger":28211677,"created_at":"2020-02-13T21:21:01Z","source_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","source_account_sequence":"94658837230911495","fee_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","fee_charged":"100","max_fee":"100","operation_count":1,"envelope_xdr":"AAAAAGpZ5X06Hz48sKzzVFo//X67YFenBLxaxzuJcPuXebqxAAAAZAFQS7YAAAAHAAAAAQAAAAAAAAAAAAAAAF5Fvg4AAAABAAAAC2hlbGxvIHdvcmxkAAAAAAEAAAAAAAAAAAAAAAD7exWPWaCVKiygoj7vEoUox3IdGR0BGEwgrfvu7xj49gAAAAAL68IAAAAAAAAAAAGXebqxAAAAQPNJSRhqEmEaKqtigW3PTPmm0SPF2befw+hH+j7hhDW9L7xDA6FDZlEvFESKAQxWBMQeV9r3D/7Y8tx5uW2WwQk=","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAa553QAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACM9wiRAFQS7YAAAAGAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAa553QAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACM9wiRAFQS7YAAAAHAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAAAwAAAAMBrnndAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAIz3CJEAVBLtgAAAAcAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBrnndAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAIn8GBEAVBLtgAAAAcAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAABrnndAAAAAAAAAAD7exWPWaCVKiygoj7vEoUox3IdGR0BGEwgrfvu7xj49gAAAAAL68IAAa553QAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMBrnOrAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAIz3CKoAVBLtgAAAAYAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBrnndAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAIz3CJEAVBLtgAAAAYAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"text","signatures":["80lJGGoSYRoqq2KBbc9M+abRI8XZt5/D6Ef6PuGENb0vvEMDoUNmUS8URIoBDFYExB5X2vcP/tjy3Hm5bZbBCQ=="],"preconditions":{"timebounds":{"min_time":"0","max_time":"1581628942"}}},{"memo":"Airdrop invite✅xlmget.org","memo_bytes":"QWlyZHJvcCBpbnZpdGXinIV4bG1nZXQub3Jn","_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/849fc553ad0a55e75a27ad5a80047a45baa54c321043686cb7f55fa9ef3f7d59"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GBRW5XFS5PANVBWVOHXTR6D6KZN3CEKA2JIROR5NRYQMHT5K67B3SYU7"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/28440958"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/849fc553ad0a55e75a27ad5a80047a45baa54c321043686cb7f55fa9ef3f7d59/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/849fc553ad0a55e75a27ad5a80047a45baa54c321043686cb7f55fa9ef3f7d59/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=122152984477229056"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=122152984477229056"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/849fc553ad0a55e75a27ad5a80047a45baa54c321043686cb7f55fa9ef3f7d59"}},"id":"849fc553ad0a55e75a27ad5a80047a45baa54c321043686cb7f55fa9ef3f7d59","paging_token":"122152984477229056","successful":true,"hash":"849fc553ad0a55e75a27ad5a80047a45baa54c321043686cb7f55fa9ef3f7d59","ledger":28440958,"created_at":"2020-02-28T16:28:42Z","source_account":"GBRW5XFS5PANVBWVOHXTR6D6KZN3CEKA2JIROR5NRYQMHT5K67B3SYU7","source_account_sequence":"122138905574114388","fee_account":"GBRW5XFS5PANVBWVOHXTR6D6KZN3CEKA2JIROR5NRYQMHT5K67B3SYU7","fee_charged":"100","max_fee":"100","operation_count":1,"envelope_xdr":"AAAAAGNu3LLrwNqG1XHvOPh+VluxEUDSURdHrY4gw8+q98O5AAAAZAGx7LAAAARUAAAAAAAAAAEAAAAbQWlyZHJvcCBpbnZpdGXinIV4bG1nZXQub3JnAAAAAAEAAAAAAAAAAQAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAAAAAAAAAGGoAAAAAAAAAABqvfDuQAAAECzK8e8L+dHqGZWsoOwNLgTnFD+Omu3DcVJ4Gwb71ZKsokaH+2hPLf65I6GgIX4pcyz1SgRNuhi0Utg4tGkfGUA","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAABAAAAAAAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAbH5fgAAAAAAAAAAY27csuvA2obVce84+H5WW7ERQNJRF0etjiDDz6r3w7kAAAAAGGO7UAGx7LAAAARTAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAbH5fgAAAAAAAAAAY27csuvA2obVce84+H5WW7ERQNJRF0etjiDDz6r3w7kAAAAAGGO7UAGx7LAAAARUAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAABAAAAAMBrnndAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAIn8GBEAVBLtgAAAAcAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBsfl+AAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAIn8ebkAVBLtgAAAAcAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAMBsfl+AAAAAAAAAABjbtyy68DahtVx7zj4flZbsRFA0lEXR62OIMPPqvfDuQAAAAAYY7tQAbHssAAABFQAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBsfl+AAAAAAAAAABjbtyy68DahtVx7zj4flZbsRFA0lEXR62OIMPPqvfDuQAAAAAYYjSwAbHssAAABFQAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMBsfl8AAAAAAAAAABjbtyy68DahtVx7zj4flZbsRFA0lEXR62OIMPPqvfDuQAAAAAYY7u0AbHssAAABFMAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBsfl+AAAAAAAAAABjbtyy68DahtVx7zj4flZbsRFA0lEXR62OIMPPqvfDuQAAAAAYY7tQAbHssAAABFMAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"text","signatures":["syvHvC/nR6hmVrKDsDS4E5xQ/jprtw3FSeBsG+9WSrKJGh/toTy3+uSOhoCF+KXMs9UoETboYtFLYOLRpHxlAA=="]}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-transactions-by-account-id.api.mdx b/docs/data/apis/horizon/api-reference/get-transactions-by-account-id.api.mdx
deleted file mode 100644
index d6c6290a4..000000000
--- a/docs/data/apis/horizon/api-reference/get-transactions-by-account-id.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: get-transactions-by-account-id
-title: "Retrieve an Account's Transactions"
-description: "This endpoint represents successful transactions for a given account and can be used in streaming mode. Streaming mode allows you to listen for new transactions for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time."
-sidebar_label: "Retrieve an Account's Transactions"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlfdlu40jS7qskdDHTPbIt7ouBxn+077J2yeopVCfJpESJm5KktoKBuTkPMcB5unmSgyQli5Zll22q2tXz68JVkpL5RURGRMYXSdrfUj6ceqnb31NZVXUC2/dSX65SGvJUbLi+4dip21R/ZngA2ZrrGLYPMHIx8pDte8ALVBV5nh6YwMfQ9qBKrvCA7mAAwdRYIRvAaFoAbQ2o0AYKAoGHNGDYwPMxgpZhT4HlaOgG9J68B9A0nbUHtk4AfAeYhucjO5zaRuvneD4R8hHMA/4MbQHECEBNQxqZwZ8h0PORaUIMTKRNEb4BVR2o0DTPyXMFKg42do4N1oZpAs+H2AfQD6dBEJsG8nywsJ21HRcGBLaJPA9AoAbYczAwPOAh/4rMv54Z6gyo0EPA8OOz6tixgD+D/v6iG5Dbkqt8IgvB28+1gmaAiCq2s74KDUMsGon91CIqRtBHGvAMW0VkJAYYLQMism9Y6CZ1lXJchCEZXdVSt6ky8vuxCXLbvTtUtdRVyoUYWshHmDjKt5QNLZS6Te2N/dUgQwziKC70Z6mrFEEyMNJStz4O0Flv2l/7n3/92wNuoJiGChZoC5CtOlq0GBAo0EMsQ9QjZnh0u1BmooCnzpAFU7ffUv7WJQJFI1NXKbSBlmuSj8qFZqfTqjW5QUPsVLOC0Ba7THtSaXaqrdEk1xTFXDHXrDRK4wJfKw6ylXJN7HK1Serh4epR0cj6ByWXAcLbJ1rq0PSeqZkFdmApCEfrGoaOR5YOAs9FqqEbKjAdNVQmUld1TBNFPuToACPPdWwPeWHgGMRKoZvuXQUBF04Ne/rVdxbI3juGowMIMFIdrJ21j2H7aIpw3ECCQAkCLXKiJPMyTfFxtR2sofdrrSHPmNrwoAcRNZzoGACRhB7wZk5gagC6LoL4Bty5kesatmoGGgJ/QE/9A/wCPRXZmmFPfwUOBn8QuD/AL+Sf/cdhEEfRj6eBhWwfGJ79n3/9298Hng80pMPAjOwfTvsd97EDi2RE6KmpSMHUl7hhTMMy/Hcapj9DwIIbwwqsg2OEqxyZAiM/wDbSbgAZF84fhjaG9hRFa04T4RmKAtcA2iBwXYT3A0MHMzwwg1h7DJ9D7iKp0UVYd7AFSSrACHqO7b1itMMCIu2Z7WjqrX5FU3GD7Zf0qw4NE2nvtFwP+WH2xlHqO7hHNBd4zGLEcUjUEFmfO1N4NYmkEOKsForjmAjax/UPk1c4/svDw5er1ObaC1zXwb53/bhTHFLcY7iSCRmKIv+cqBHtlamrlOrYPrJ9MgS6rmlESSAz98i4bzHBoGne6WHG3YvoKHOkEs9zMdHbNyK8r6ZhL7yYKi+M85Cpf3/UDCP9XFSELuSH7m8vUg9XKR9Zrkn85IwRHx7i6/p7NOmXq5Rv+CaKzWGjjf+TieRitPqpRHogww4fNcKlJrH1HZ9AloJI5fN9VfZJKDYQYgxJZBo+st7gVxaynOe2eLj6KzvmvkD5yaSKytafTKhjCv7JBEO6jlT/Z5PKxUhFGvrZxAq5HNJ+NrFirOankuxkUJjBjlnjMVKfRMfRI2NeELP8U22/PFylDO2cOgdJDC30pxgROJuFjyz9nLZXqRn0ZmcvfJZtjoXeo0UN22cZMnjPOL9C/7wQToBV9PV5Wn3UyoW+jzAplcq/Z68n1LX85RvPP8T0hZqGSQl1TM9frWCDztjodMTXc4Z8JtVXj1BkW0Vnx+rocuLH5npJhaQzvqQyGajOIJ6+YDcLbr7q6LwJHn3566kZXvMMZK+Q6bjo60bDZ6eNqvbvfW0hH744hmj16gBSo3yNPj3nByHjCTB6SxX03QWKlWuxifep37E1442bJenUKE5gvyUpW4b9lYx/cU1f+DIma6z/044L2j+K8ZgU3iPWszTyVLAXv36DaI24MGQ+w35bMJ8b+BVO3zE4EvvrFLqvh0FwjIONj+FX4hFhI+2tfvbwFkMcYkAJLPfr+/bMs9n/iBh+/2eFSOzjEkK5wHJjCpOLDNtG+C+s4Gv5NXZJlaj5RPWTesOI2rKxnf/JPr/f1GNlSGx7frYZv7wPPt31nm4eR1WebwwnSf9Jin+e0OPZ+ck6fHl4eMn7Uw9fHh77TeHKdJGPDbRCWftwkhFvaJMRYZf0acPkwDyjyjE1833Xu81kZlH37NpHnm8j/8aLjg1uHDzN7K3hZcq5Yak/afCVarvPtUudYX8yrI66ojgUG6P7/HjA5Rv3o1Glclcc5wRu3C7zjUKzP8jEO/X/EzWXf/tb2Mv7jab+FnZLfyO9x1h/5NPloxmG5hlZ4jhRZBiZ4oUXJD60Tz5dYpkTeEliRYalZIYVxWcCh41d4l5PeiWP3ZDfD42N1MFBla1PXI28T+RBcWkznMQIkNU4GvJQlHlFF2VeFESN0hUesbLKQUVRdUHmVV2SJIXlRQlCmhEUXmF4EaGTZsXHzH7fu8s2xQLHdJuDFtfI1/Ol+9Z4MmBLYr82rBeYVrMriEyNY0Uml68IhSKXq3efcoR3IEcXeRmGoViZE6XnXYTPsmbmKMa3vSNdhW5zFfpMWHwfuSPp/T7tM3ya3HsZ3i50vA3xQan/5zHw//ZSzJ12FpIhkYh9FeqkMPi8mNxz91TimU75feq53k8ZfnQeERU9l4A/BPghVp8y/RRD0fI1RV/TUp/mbjnqlhMnzyuM29SHc8wrJD0lU4wsiCzPUjRNiSJDnxQsiWCfEOUUTVGxiufw/hkhpk/pbipLXpWinZ1Ieqs76a5KxqAalNldf6Lv+sOO3JpUWLnGr9JTo81N7sjwSbaU3ZVV8t9aeH0n+/RV2uR4tUn+lzt+WDwZlFuO0FC+m0npdiPvSXQXtjN0OmByY3fdk0aeKhrjgmiyluBF8+fTq3zs+uKjPJ07jqHXqpKp3es5174v1nYVt7nt2Lgp4YrGtQfOtjJ22+aqkx2Ud9nucq2MpZna6DU531zwdHatBJM7ONFHeVjq6LvSpBZks789LQz3tiKvckzhU92j129n6sj9BFPyo0p+FLLDXMOfHq9Se2rO3kh0ySxLo1rH4BS91TIzrdawQNELXadsKyPkq5nZggvHV+VmMbYY1VNji62NK5rWUPThsqMvnV477ZvL+V1lhLIt2LkvLWeFRb5T7E7iWpwu1HHFLixv7YfLS15r8qOZGxQDJvbVprYu65XdYDRQNvdmvjHzJYoZSxQ9aPdHXTnTQ0rGqc7T5X6k75xadxfZQaE5CedbHKcKRSl4bNkORpNxQC/dXHo5q2YEZrRsctqEy9JubjpaFu86tWy3ZMYlPO88RKek8k6ZXPtPlDd7Ku/HgvvEv569Xsb/LXXaZYtFWzM3yCMrgTXn1LpfPVozJuLPufon3voj5f3ttycE+TblE074tF/xe0qcK+PcZiWZM6lsadOO3USLXS2PvN3W09ip3JtXNbRIj+RsrqM0c2Wc8/Vtae1XdwYz6tuDQi7gF7xryvc1Z5jLNIcLiwuxv5xrWz5pTB5bj6nDHrl/S/OcKDEMz9JhFysh8X5SoiFV0nhNQAKnqZym04oqaZLKUBSiOEkTRI7SaCTrgkQJNKNApEFKFyVBlFRZhYIgXII2ZRsCUy4Wmp3SqNtpTMa1ep8blbqlfrXebvfzTLbRK3D8sFkXJ4PBZJgbj0bjQXacnDax0d1al6NNSa35WbQpsdw/B22iKUZgGZqnZV6iRVniqB/Hm85jXYg4JY/KA3FKPNMz4nRG8VeY0wXwH5nTPlzPMif+mhZD5sTe8ux55vTRNPMqc2JpjmV4mWEFRqQoiX3OnD4Oe0nmlNP9crW1yDPzHFLcYds0No1W3l5ZjU5pW9n5o3rGMpt0AdE4GzGnujCgwj347JZa2qGtFitoj99HxWzZnfBjSqjsOMmr73bDkpPJjAXxvoTsXGMDN7ugpraDMVKWm+MkjUZnHK+qio/ydBql0n1dxuUsM7CY4XoazLkuZPvCFJJbPnWus85QDbWcWcKMM56gQPDECc6x6+GwFlAWzbATcWfge8fhRaHak+B016h3Ou9lTjGW+FbmNNrqk5hOpTR1P2U6Ddgs8YE5SI8aRY+qo/S9nx1X9Tv6HqfhYDdoiSOPDM/T+rpBHxcjzivjhjr/MRH4sviFd+M/Wu0Zs/mTK+9iTqnJ8dr6nfiNu3bZSIDfPMHPjsWuUZhkfWc9toRhn7/3eruOK/IGlVNnkjg0Vrzbb3VYH4a1cWOYya4G2QF2+yFGM6H+78XP1gO3nQD/e8ynl5bayayz5o7SVc/L8MOsc7o678F/xkxsx0bPmIk3GE4x490XJj1lMs7nhfashLX2MucKjOBnZoVCpuOvlbSL0zPNFMTlzre8ip4bDiyxp4wVzV7d1X3DmNsrZ9bYLAtNz80lZya8RFMcz8gXZyY8x4gaI9KypsgqZFmREpCsUoJKcbpMKxrLs4hCgs7TEq8KOicqPC0qLCspkibRCnORA52PnaMlZyYiTXO8SF+OmSS15mcxk8Ry/yTMhBY4XqBlXpApWuAYhvuBzOQs1oWYSfKoPDCTxDM9ZybPFX+FmVwA/5GZ7MP1HDOhmWuK6zPMLcXecvQLZzofTDOvMpPY+RZNc5J85kznw7CXZCbvZAqTbKnTE++zj3XlM2bCOo1JrDh5Vr13C1JngoU1lEXD4GsIBc1acbxVh17xjtZyaDHv9tWqnIVabNZcs0fF3pYf5em0Cmkr2LGSxDaditX3g5lXUDi4LtEDtlioMaWOLVUhk5cb6e5OYCZycVWRsCnRGuu0N3g+sJE2seZ3tuvbQnZq8dCsrNU/gZlMGKm3Pl4FTdvU+47enm/XuN0ajOYZWcf+dCioxVUJV+44c53mNT7AYbWf3803TuW4GC+8XmEGl8XPnYd5GzOxlXW89ix2MsUyTHvlFeKcoDe28TzfLUl2SckV/HFn7FapAZtvd8p2uAC5zaTTMrITH8PwrXce8ZXa01Y2jQT4W3OeS4DfPMH/CDOaqkdm9ILN36z/u/Fb+Z2XAP97zORzeWNi65ysznvw38ZMqLYAxba+26nbKZrcMUJ53VrNcHY87Kudpn0/zOvrGb5vUCu+0sYTm+pJ+jYY74YsmmbKQaun8bQFmwKyGN3J5xVzOdBz68TMROQ5WaQpcc9M9jehzZBpOiCwjRXCHjq9JQ2Wh55SlqbaiHc1a7hVmcFvF71NDemUjigOqqwqakhkGEmFDC9LkiRQvCwJEtQoXmUYDlIcjSSF0WSEGChBWdMESeb+2qyG3PcoXJDVJLXmp523JJX7J2E1pMJlWI4TZZrlWJr6kazmLNalzlsSR+XjeUvSmZ6zmueKv3bekhz/yGqicH3GahiK3KnGyH1aDs9b5E9jNTL138dq8me34xK34VrHQrdgzUylvFlVK8MAjiemarcOd0A8K4SbdyNfK05qazTKFXB1WC507oaOZtjYHCv6Lqcvg66YLfmbUXTzU7Zf9GOX5x5LiWJhrRVMt7Piq/oa9ReN+dZ3R1WYVtzOSsxlK92S28xXPLXJTtOjXH0+bg+Ldq9N56azRrBlg9lquuIadn5RTU9LxcJksx5m7ks//u416OX7sQnezTQ6nhAkYRqXxX//GVD2eHfZcl1rxb76QKW95I615Pu77AnxG8yUSYCfPcHPrnlIU92FnePvi3febHDfyvKjGVNHwVDzM81SeslXvOyILSlR7Ry1AU7W8x3432Ean8uDEq/OiXe8B/9td2dJlQ4PB410ryJVFnyekzAcGuWVJQwa6XUnR3VhPzsTK4UW1zanPYfe0d0aNZc799We6Pmio3CNdJ5fu/m2k+tmGVUt6Uyuk5hpSBTLiDQjXPwMRKVVReIpnaNZxFGspHI0QymarEBNpURFkZAu8ZATBE6GnMarskoLiNx8zmgsxUvyfwFbEC/HFpJa87PYQmK5fyq2IFK8QDMMJVDSD2cLJ1gXYgvJo/LAFhLP9BJbiCv+Clu4AP4JWxBfZwvcLSt8Hls491zLX5wtvHB3Frfh2s65LTcqBgsFE4+75Z5aMacdYVvqTqmCCSv3rsAPGVZajwW8QOucog6DWDnAtp48zhA7A2nutGqgYEcedwb9xUyn7pVCrtXk/WU+s+uJelmhco3SMt3ZjPviMNsTtULTduQso9Oaztn2FlWWQzOdD+qqu16vexRX602Lf8IZCPTygwRnEFvZaQ2TVOaXxU90d9bnVsZh7dn/OH6Om3jFBPjNE/yPMBN6cKx93393VjL82sCtmAnwv8dMPpe3JbXO6epc/u6sXYsy+CCY01que9crZbozr1mkdhbjNDKthi9NVp2iN8J8oaS1/UGu4VPNLZpThUlmSGcMpNc45I7GXJ1zt3ahkGv0p2Y9eylmIjCXf26E0llNQCwjQkFDFM0wLJR0CjGKJCFZhAqCOq3zNKfLvC4hUeV5nZYUmad1StaUyzxu/1nMRKIoSqD5C55jJLTmp51jJJX7p2EmjECLDC/ILM0KkvwDn7c/j3Wpc4zEUfl4jpF0pnPM5FTx184xkuM/MpN9uL7ATFiqz9C3HH9LvfTE/Z/ATJj/PmZSPLullrhdH58+5hnt6dHP2QI2JplyBc+4FYS4vkB1sT1mVF6iW6um3l75/W22Hwx3RnxWGcWL3BgzycnjXECLd+YKb0VVyi8btfFyVedVb8tg1iwbbbay7fI1FW8bUqcz7wXrMs40iqVSvdrjs7qTmc9kPb8r72q7SYcrtOh6e+r9GczEz00SMINhvctJSZjBZfFfAHojM6GKcTe6n5QNRt/MBA41GGu5dStGsKNl+05v9ZVdZSeKA2laFE2Vi/wsf2/OB0SfwmuYr9WeVMlOgF8dFewE+M0T/I8wg/n6WPu+APRm/d+Nf4ddPQH+G5jJJ/KmxNY5WZ334L+NmVRotSyOPWGUXjX83brueCZaStjc7hpwhQawmlH1WmVhblfV1SaXb9XFLFxJXmcwcGaNRS49T99VaKnRVJp2yyxMm+zASeeT350lURxDifLlmQnLyBBxkkRzEDEy0gRNVilFERArSzLLIAHSoqRClaEFhlUEVld0XpMYjmcEWqU4+r+AmciXYyZJrflZzCSx3D8VM+EYSWRkRmL4H89MTrAuxEySR+WBmSSe6SVmElf8FWZyAfwTZiJ/j5kwn3iH1Zkn2v/qzKR0dkslzMR/5Yn2jzGTOx7XY29jzKQEB1VnNBo3AjzplvytYOQqliXwdWbNFydzU+uoTS+XqaOOSXdn1GAxETscV8sX8ivbt6uzkb4w6Y7hYmE+WWSqnJp252vpz2EmMAEz6C+F8TwJM7gsfund+E+YyWcyg7D2xAnwx+1gk5SZxPA/wgxQ81j7DhLq/178amaTHiTA/y4z+VTelNQ6p6vzHvy3MZOh2zFmk4kaCL5ZHLGNZbWIoIIXWCksutbdkM6tt+uK5PL58bBc6fa6tl+YTxfVZj2NGNUoTdK98TBft1bLltWX5rOdYLULF2ImEi1enJkwigRFURURx8iyyEiUInE8h1hZ0URVkGiVl6DCK6KqMpKk6xIrqLTKKQLNM5qq6n/xMxOGpij5gs9+JLXmZzGTxHL/LMyEpgWaoyVGYDiaZWnmRzKTc1gXYibJo/LATBLPdIaZPFP8FWZyAfwjM4nC9SwzYa5ptk9Ltzx3y1Ofx0y4/z5mUj67pZb4kiWfZSbRq1CfY39cgi6e+5ozlKx7tOF4XtSL5eH9wpXYOrXSB+vidrgvR1Z4HX8UdHIojnPZev6OqmatjjQb1IbNpl7dBHQnU5hOkGLZlKx17/KlfL1XHEzK98Fuaeq19n0Tq3e1rq9z9HrdLNWl0ZyeilQxu05PCrP6rFaIyoEf/YwHv1smYAVtSV8sk7CCy+KX342fPT7jge27hFVxzznWfS883f9K3ZkQf8fm6wnwsyf42a0jiMPNaAk5cQxLes2qeOgOIXaTM0e1ut7a+g2Wbuaa5v68qyFI1ezper4D//us4BM5S+LVOfGO9+C/jRX8sBSUkBXQAkPR4tmnydcONrUXHyVn5K1S7lz2MXKRkRHH0ZLMUiKvI45SBChoCgVVBbGSprEyw7EcLaqqJNKiLgsSR3p5HMvSUGAE6q9OJWhBvOCDIUmt+VlUIrHcPxGVkBiWoiSKZXlJ/NFU4hnWhahE8qg8UInEM52nEk8Vf4VKXAA/TiVIuL5MJRj6lqFvqc/75Vgy/99HJSpn9+ESX1pNw8e8w4oxzxweI9dWqrXZ//GF0yqzIKLNqD2C+WHd2E6dubgqOgNnw1a1cpfKlYvrKdZXgbiZc3JEK6IK6vEVO/Rot2q97mxZtIqwvvSN6Yht99uWRfXaJUZB+jo9q6Tn4mxWGMkNcVPICqXCxCyuSsVePdvZjHLNDhrKmC1kxHvJ3/DBiBmtO4s/hV7wbIJHuJvy2ugmKe8vi195N342Ti/s2G9G+0h5XyseC0j1POKrBWwifFsq5xLgZ0/wPxgcJ+v5Dvzv0IvPJV+JV+fEO96D/8ZHyCmzVi47vfuus1wy9Zyiys00VLpVaTzx+UxBKOpCOygXWwq1WhWbBWfQsgY9adCtOrlC6b64yfFjZqW2M/58y1YsXpkoufwFHtSgBUaSOeYpvcgaWMOOCwx7ZfjoP//v/25Ma4p8Unmc0o3OyNxOKrWVms+5ij1xtfLYsKtDTinT9mTcCRS2Zl+UgkicrKs8z0KNgjyPRB4yItR4KFEUJ0KOVyDkOZVlaIpjBUlQFVHneR3KSGd1UeMv82x6d8SPSz2+nW0Nc6PhXWXc7woFoT5psfliPcvUqt27Lt/q3nealT5fF8Qc27sfiBegIBxHyfwF/+BiUmt+FgVJLPfPQkFO/yzrj6Qg57AuREGSR+WBgiSe6QwFeab4KxTkAvhHChKF6wsUhJH6tHDLSLcc8wIF+WCaeY2CEGOwkkzxvMjRNMdK0hkO8mHci3KQVsA2GnjdWpbpcWV1156lh2awKQ4KvUFXq+B7brqW0ktZuuOzIQcpb8Twt9h0Y83BsLRU3rJJxcbHNvt3/7WI/atcjj0Gn1uu9EIQ/iqr/K4uIamR1irL8mTkOXfrVmPat0uF9J0VsAV1WOPKa0WkJ3XPWcBKmpm1G7rAV4XytDrmXHW7o3vTbiuYGdTAn3J+eaGXB9kff/OVUuH12NnNPSOqXrDKMo4yVJHEpSv8aCQWu51WrVuikD83CoWdgNm1uNib404cHBco/sB17PUKD7gs/gvd47fdfPW5PKCY83QznQgfKYuP4zdP8eeKv90KUgHO/OFG3M053ZwoXreUpcziuCswd9Vmu/0YANns/b3od7JKxSO/LjhXev/tRYnx5731x/G/x4M83ZSSWSegjtK9/7GQy65OosdCzvIgb7uqrPIZuyvMrCGuF7xCjyvym05m7mJ/zZZ6KOeV0/Koh+u18izjO/0tmw56dzMnX0rXx01PHjjFvuLc+6XG/V2j61Y2ZvSHDh++POxfVym08ZHtRcXx799SC7RN3aY2117gug72vWvPxwhahk3ozAqaAdqXeV+IBv7MIbvXFPlhLeGTquBY/H87bKqG9vCkBiKqIkx+vW+IGWDzbYVU6ipFyjRsuFERlurPEOhH40AL+WsHL1KEnJ2fUQ+Ibd8yZ+kwEtiHWb9cpQxbdyLO6Jtk1SrRvMQwCHvR1dQNdUOHRZNlQbw9jgIudlaGhjwAbVDp99sg264C3wEa9CEwbODPEOhFch1Qb0DVB4Y9RZ5PLtMARteh4bxwdHilix0tUJEGlO25KcjMEOgOtoA/gz4wPICgZyBMoFXH9gILHS6FK4ThFAHouqahhoUHwMiEvrFCZDgZ4yJMJoO2iq4dbCDbR1okCEYuRh6y/YjjgMCLhDoIlHcwugH9meGFmsf0ULChTRFQkL9GyCbwkbZPr2xjZ054CDCNBQJraJrI966AhlRk+xiaxg5pAG3UGSQGuwpngJ6HiM5egHAoETishu8AL1Aswwdxx7wCywDhLVmive8CBZpE2SvgYBDFAkArZB/kiF9NJj1eefPMs/63e8Lv8QX98sshPDUUVbTYe0Ka9mJnVAeja9vR0K//q7znn/Y/7QOcCm2gIPIV8ogtVwYE6qDbuAIQKNhZewiHCI6NgKOHVnm0da9Q975ra81RvYzvOKaX8bSFRyztAIyIO4WzqY7lmmhj+Fsy/9YJMPE2YtArsEaANNUsC9ka+So0FLQJMDBsz0dQIxdZcGHYU6AZGKl+uIYqNE0v1DNc1mlgaAhEEaMgD8ycdWgSzTJsw/MRBgcXD93xYBsCQUwMfsFIj5w51L/wqOnfQc50pkcbrNfrp8o/jrxWTGeagdc2Wl97gX1NdqEZut7vH7+S4AGeQ8IEqospJm1D4Nin0RD5DlZnho9UP8DQBIZFYh5Z4cqHK2R4wIJzB4P91gGUwHJ/vQElBwOyz2ArijqoOIEP9iISA+7xHl3D0ZACPXQF1BlSF4CMjutPIEGZmPZogKnhzwLlRnWszN4Oh38PqmYU01EyFjTsTKE4LDbu2tVW+cbSfg2XK4d0ByOy8AqaGvYVMPy/e+QWC38GMDL8kLTa01AOkgaMUAikzhykHfLb7yQsQcvRPpIIgOaogXVIMLfgH/9YI6A5wHZ8gGzNwR4COLBtIsTBUGTJojQEAfEYDZokXOJZ4tGX/vGPKAEgz0WqAU1zG04dXvt1BU1DCxX8+mxvQ8T1MQL+2gEeciGGPgkeW0XY3icVDalO4Jp7+1gkDRsWKbWg7YcOpjihGU0DKoZJIo5cFXOvmyeuT6LLgjacIg8YxLnW9hVwIUbateas7Uf3cvSnqjqub1hh0iOY+ytJUiMpz9GBTbpq4Jc1+rtpglhkGR6AHoDgn6k8dMPtgEz3z9Sj7YiLhF1BbHl3eg/hlRF2Uw6L/KQvRgZdO3q4lZFhVynVsX2ohv1mG4ad94PYcYcukdALFz91dVLsPS3tkAUN83AX0P+Jf0cazIaKbA/FsLIuVGcIMDek+2JoxHd1A+HHb66jb46I+3QCw2+jBnQ0qZdpVPPFVq9ILrmZ+ZYZ9u1cx/MtaMcgu8jHBlqFKTMb5f6/e6D/tFp+Ukd8C42EwgZUmDmRrbmOYfvHjdcDx6bd002GrDYEU2OFjpsUcbD9FhNu1YYNHqt+YDkaugG9J+8BNE1n7YXZ3neASdKzHU5to/VzvMhrDmDhrr0NwwRqGtIOGfuwzlFL8AZU9XCHOCfP1WMIrA3TJOGMfQCjxIcgNg3k+WBhE4+OCQMC20Qecd6ozUtCz0P+FZl/PTPUGVChh4Dhx2fVsbOvl6KLbkBuS656THD7uUJqRFSxnfVVaBhi0f2W/8Qi+wYn8AyyV4R7KSZNR88HJFOSsjHGCjOuCQ2beGvodN/2LOv3w8EM8Y7bI89KPWlTe+TIa+Z4Prng2zeyTwyw+fBAPg5LlZB+aYYHFZO0IXVoeugVb8sCO7AUkgqIQUKfi8oWECZK3VCB6ezLxbDaVB3TRJHxHR1g5LkOiY3Q4wwPuEG4vnsbIxDvRu8t6ugAhvUF1l60TMRZo4U4stRUyATfo5yGIgK+F5dIFJ4NHB0kEsQD3swJTI3UmgjiG3DnRktr2KoZaAj8AT31D/AL9FRka4Y9/ZUUZ38Q5D/AL+Sf/cehk0fRgafhhgYMz/7Pv/7t7x2T7Pw6DMzIzOG037FCKPDHjUDIrwU3hhVYh7UOFy5SG5O/5GwjLdzqQHgOFLo5JkVztIw0EZShKHBNElrgugjvBx5IxwxijVQtYVwf4pikiXgJhRH0HNt7xUCHxULaMzvR1HeMFAr0cSP1kB8mLRxF/GHVdWgQbz4e8xEFo4ax99xHwqtJHIRo3xF4f9HXCOKJ5F/IG2wQ0d8Zzb900TIwMNJ+jXjVPov851//JpGpmIYKFmgLkP24WhCQFMIyJK+R/PeU6L2ow/5DaG/jkh90iyWvhy8PV6kZgsSFj82orKoiN75cMVaamXuOnXrSjCoX+6mHh/8PrbU1ZA==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Account's Transactions"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/accounts/{account_id}/transactions"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents successful transactions for a given account and can be used in streaming mode. Streaming mode allows you to listen for new transactions for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./get-transactions-by-account-id.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-transactions-by-account-id.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-transactions-by-account-id.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/get-transactions-by-account-id.mdx b/docs/data/apis/horizon/api-reference/get-transactions-by-account-id.mdx
new file mode 100644
index 000000000..f1f750889
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/get-transactions-by-account-id.mdx
@@ -0,0 +1,12 @@
+---
+title: "Retrieve an Account's Transactions"
+openapi: "openapi/horizon/bundled.yml GET /accounts/{account_id}/transactions"
+---
+
+<Tip>
+
+**Supports Streaming**
+
+This endpoint supports streaming. To read more about this, visit the [streaming section](/docs/data/apis/horizon/api-reference/structure/streaming).
+
+</Tip>
diff --git a/docs/data/apis/horizon/api-reference/index.mdx b/docs/data/apis/horizon/api-reference/index.mdx
new file mode 100644
index 000000000..d7ddb1a60
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/index.mdx
@@ -0,0 +1,28 @@
+---
+title: API Reference
+description: "View all Horizon API information."
+sidebar_key: horizon-api-reference
+---
+
+<CardGroup cols={2}>
+  <Card title="Resources" icon="box-archive" href="/docs/data/apis/horizon/api-reference/resources">
+
+    11 items
+
+  </Card>
+  <Card title="Structure" icon="box-archive" href="/docs/data/apis/horizon/api-reference/structure">
+
+    6 items
+
+  </Card>
+  <Card title="Aggregations" icon="box-archive" href="/docs/data/apis/horizon/api-reference/aggregations">
+
+    4 items
+
+  </Card>
+  <Card title="Errors" icon="box-archive" href="/docs/data/apis/horizon/api-reference/errors">
+
+    4 items
+
+  </Card>
+</CardGroup>
diff --git a/docs/data/apis/horizon/api-reference/list-all-accounts.ParamsDetails.json b/docs/data/apis/horizon/api-reference/list-all-accounts.ParamsDetails.json
deleted file mode 100644
index 0da05271f..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-accounts.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"sponser","in":"query","required":false,"description":"Account ID of the sponsor. Every account in the response will either be sponsored by the given account ID or have a subentry (trustline, offer, or data entry) which is sponsored by the given account ID.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"asset","in":"query","required":false,"description":"An issued asset represented as “Code:IssuerAccountID”. Every account in the response will have a trustline for the given asset."},{"name":"signer","in":"query","required":false,"description":"Account ID of the signer. Every account in the response will have the given account ID as a signer.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"liqudity_pool","in":"query","required":false,"description":"With this parameter, the results will include only accounts which have trustlines to the specified liquidity pool."},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-accounts.RequestSchema.json b/docs/data/apis/horizon/api-reference/list-all-accounts.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-accounts.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-accounts.StatusCodes.json b/docs/data/apis/horizon/api-reference/list-all-accounts.StatusCodes.json
deleted file mode 100644
index b05c8fd34..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-accounts.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Returns accounts based on provided filter: signer , asset, sponser or liquidity pool","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transactions":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"payments":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"offers":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"trades":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"data":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transactions","operations","payments","effects","offers","trades","data"]},"id":{"type":"string","title":"id"},"account_id":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"sequence":{"type":"string","pattern":"[0-9]+","title":"sequence"},"sequence_ledger":{"type":"integer","format":"uint32","title":"sequence_ledger"},"sequence_time":{"type":"string"},"subentry_count":{"type":"integer","format":"int32","title":"subentry_count"},"inflation_destination":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"home_domain":{"type":"string"},"last_modified_ledger":{"type":"integer","format":"uint32","title":"last_modified_ledger"},"last_modified_time":{"type":"string"},"thresholds":{"type":"object","properties":{"low_threshold":{"type":"integer"},"med_threshold":{"type":"integer"},"high_threshold":{"type":"integer"}},"title":"thresholds"},"flags":{"type":"object","properties":{"auth_required":{"type":"boolean"},"auth_revocable":{"type":"boolean"},"auth_immutable":{"type":"boolean"},"auth_clawback_enabled":{"type":"boolean"}},"title":"flags"},"balances":{"type":"array","items":{"anyOf":[{"type":"object","properties":{"balance":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"liquidity_pool_id":{"type":"string"},"limit":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"buying_liabilites":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"selling_liabilites":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"sponser":{"type":"string"},"last_modified_ledger":{"type":"integer","format":"uint32","title":"last_modified_ledger"},"is_authorized":{"type":"boolean"},"is_authorized_to_maintain_liabilites":{"type":"boolean"},"is_clawback_enabled":{"type":"boolean"},"asset_type":{"type":"string","enum":["native"]}},"required":["balance","limit","asset_type","buying_liabilites","selling_liabilites","last_modified_ledger","is_authorized","is_authorized_to_maintain_liabilites","is_clawback_enabled"],"title":"BalanceLineNative"},{"type":"object","properties":{"balance":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"limit":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"buying_liabilites":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"selling_liabilites":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"sponser":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"last_modified_ledger":{"type":"integer","format":"uint32","title":"last_modified_ledger"},"is_authorized":{"type":"boolean"},"is_authorized_to_maintain_liabilites":{"type":"boolean"},"is_clawback_enabled":{"type":"boolean"},"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["balance","limit","asset_type","asset_code","asset_issuer","buying_liabilites","selling_liabilites","last_modified_ledger","is_authorized","is_authorized_to_maintain_liabilites","is_clawback_enabled"],"title":"BalanceLineAsset"},{"type":"object","properties":{"liquidity_pool_id":{"type":"string"},"asset_type":{"type":"string","enum":["liquidity_pool_shares"]},"balance":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"limit":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"last_modified_ledger":{"type":"integer","format":"uint32","title":"last_modified_ledger"},"sponser":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"is_authorized":{"type":"boolean"},"is_authorized_to_maintain_liabilites":{"type":"boolean"},"is_clawback_enabled":{"type":"boolean"}},"required":["liquidity_pool_id","balance","limit","asset_type","last_modified_ledger","is_authorized","is_authorized_to_maintain_liabilites","is_clawback_enabled"],"title":"BalanceLineLiquidityPool"}]}},"signers":{"type":"array","items":{"type":"object","properties":{"key":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"weight":{"type":"integer","format":"int32"},"type":{"type":"string","enum":["ed25519_public_key","sha256_hash","preauth_tx"]},"sponser":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["key","weight","type"],"title":"signers"}},"data":{"type":"object"},"num_sponsoring":{"type":"integer"},"num_sponsered":{"type":"integer"},"sponser":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"paging_token":{"type":"string"}},"required":["id","account_id","sequence","subentry_count","last_modified_ledger","last_modified_time","thresholds","flags","balances","signers","data","num_sponsoring","num_sponsered","paging_token"]}}}}},"title":"Account"}]},"examples":{"ListAllAccounts":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/accounts?cursor=&limit=10&order=asc&signer=GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U"},"next":{"href":"https://horizon-testnet.stellar.org/accounts?cursor=GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U&limit=10&order=asc&signer=GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U"},"prev":{"href":"https://horizon-testnet.stellar.org/accounts?cursor=GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U&limit=10&order=desc&signer=GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/accounts/GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U"},"transactions":{"href":"https://horizon-testnet.stellar.org/accounts/GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/accounts/GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U/operations{?cursor,limit,order}","templated":true},"payments":{"href":"https://horizon-testnet.stellar.org/accounts/GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U/payments{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/accounts/GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U/effects{?cursor,limit,order}","templated":true},"offers":{"href":"https://horizon-testnet.stellar.org/accounts/GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U/offers{?cursor,limit,order}","templated":true},"trades":{"href":"https://horizon-testnet.stellar.org/accounts/GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U/trades{?cursor,limit,order}","templated":true},"data":{"href":"https://horizon-testnet.stellar.org/accounts/GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U/data/{key}","templated":true}},"id":"GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U","account_id":"GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U","sequence":"24739097524306474","subentry_count":3,"inflation_destination":"GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U","home_domain":"tempo.eu.com","last_modified_ledger":40074676,"last_modified_time":"2022-03-17T23:13:54Z","thresholds":{"low_threshold":5,"med_threshold":0,"high_threshold":0},"flags":{"auth_required":false,"auth_revocable":true,"auth_immutable":false,"auth_clawback_enabled":false},"balances":[{"balance":"0.0000000","limit":"922337203685.4775807","buying_liabilities":"0.0000000","selling_liabilities":"0.0000000","last_modified_ledger":40074670,"is_authorized":true,"is_authorized_to_maintain_liabilities":true,"asset_type":"credit_alphanum4","asset_code":"EURT","asset_issuer":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"},{"balance":"0.0000000","limit":"922337203685.4775807","buying_liabilities":"0.0000000","selling_liabilities":"0.0000000","last_modified_ledger":20213845,"is_authorized":true,"is_authorized_to_maintain_liabilities":true,"asset_type":"credit_alphanum4","asset_code":"NGN","asset_issuer":"GCC4YLCR7DDWFCIPTROQM7EB2QMFD35XRWEQVIQYJQHVW6VE5MJZXIGW"},{"balance":"0.0000000","limit":"922337203685.4775807","buying_liabilities":"0.0000000","selling_liabilities":"0.0000000","last_modified_ledger":7877447,"is_authorized":false,"is_authorized_to_maintain_liabilities":false,"asset_type":"credit_alphanum4","asset_code":"PHP","asset_issuer":"GBUQWP3BOUZX34TOND2QV7QQ7K7VJTG6VSE7WMLBTMDJLLAW7YKGU6EP"},{"balance":"80.8944518","buying_liabilities":"0.0000000","selling_liabilities":"0.0000000","asset_type":"native"}],"signers":[{"weight":10,"key":"GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U","type":"ed25519_public_key"}],"data":{},"num_sponsoring":0,"num_sponsored":0,"paging_token":"GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U"}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-accounts.api.mdx b/docs/data/apis/horizon/api-reference/list-all-accounts.api.mdx
deleted file mode 100644
index 636ae0117..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-accounts.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: list-all-accounts
-title: "List all Accounts"
-description: "This endpoint lists accounts by one of four filters : signer, asset, liquidity pool  or sponsor."
-sidebar_label: "List all Accounts"
-hide_title: true
-hide_table_of_contents: true
-api: eJztW+lyG7eyfhXU/Ejs3CFFcbVZlbpXEmkt1r5YtmQVA840OYgwwATAiNJVsSqvcarOfbk8ya3GLBoukijLUZRzTv4oHgKN7q8XAN3oW8fQoXba586K58lYGO1cuI4P2lMsMkwKp+0cB0wTEH4kmTCEM200oelo0r8hUgCRAzKQsSIDxg0oTdpEs6EA5RKqNRiXcPZbzHxmbkgkJSdEKqIjKbRUZcd1ZASK4nKbvtN2tpk2K5znHLlORBUNASk77fNbR9AQnLZjCYByXIchn7/FoG4c11HwW8wU+E57QLmGaXFSsmSzg1ybAHJGSPcK1E0mG2HC/qogWYeMGOcEmAlAkX4+C3zEAAcO2RWIfDaSVySgV0Ao0XEfhFE35I1RsTacCXCJHAwQIKmITw0ldsBbMgqYFxCmH6ePwGkvgJA67VvH3EQWE6OYGDquA9c0jDh+Wu/sHBzsbu3UT7ZbB5srzeZ+67C6f7axc7C5e3q2utNqrXZXdza2P3zuNLa6Jysb61utw/rWmTMeuznWVo1PRVoQpnUMfmIEREGkQIMw9gv54/d/rkkf2ps4RqVq2ez88fv/LaSJFNocUDKQqogTLll2CiIkFvl8a7FkFmdxrmlQjVaRUHpJNaIbohf20AufCMUpMwExGAxyd3QzoWNudCIzEx6PfSBS8Ju7MJFYdYJHpjBNjEz9Dzw2YOBPRYkJ7Xmx0vLJ2iMiDvuAdkENsQHMrkqzNT3CpWcjD2qQEk9yDp79txzk2tSECh99Moo5B58MlAwt5xEdMjHsGXkJglxRHttISIkCTyp/rmaZMDC0ZpirttmsNJvLrXrr3fvG++VKo6gwqfyn2yzxAW2LZnIgq5YQCpmoIuFQEx3ImPuERhFQVSZ7lobOtfgL1d4v5A3VHgifieFbDFe/4HK/kDf4J/1cJpuDxDaoGsYhoEdo8cfv/zDEhn9miA8Das3EyITsI4Yv4hD3Jao9JxHQuZi05JA9NSAdB0BCes3COMwMw2o5gUKBiZUAv0xwnKVPPCqIomIIic6XkflqpUJKhAoSRxGodKA1MKZJQJXvSR98hHpDKva/UtjIFIEaSBVS4aHDUC2FfgC0TIHgz2C3XFnUrpYr4/GF61yXdBxFUhld0kYBDRHgtlExIGCphSOlaqWCfyYxO7SoFHd8qsEnUpBIySuGkiabfrblk3zPT/dnNJlJx3Zcx5PCgDC4Ho0izhInXPpV46K3BfEo53sDu+ungsr+r+Ch5iOFxwbDEuZ7nIlLXQDknnEa+ODxUYGCwTyrtCo01vzEpTN2HQNhxFFPhdF9KTlQgYG3YJHnCdEL1zHMcCjQEHBtXhlLkYKrV8XSGIdln7atqjEYPGITEPbB9yeWvWdoGgQKA6lSFGMKMxAuYFd/Y/szigpN7a63gAAvylp+MXhtjEX0BgP2a2MLBgPwXh1X9qbz2pgyivrw2pjCm+CrYmlqkI1eUxFjwksLnnFnjbkF5Kinkl6MXYf580TJuGA+ypEePnrzx0bUGFB4WFk/XymdVUrvL24bjXGBCvV9BRq3DEfDbzEIDx4mdI5E/qtAIZ9WINHj4OORa94hLFdFzISpVedQymYXCRoWzmEMR6QJhJ7F4eEVZxacnIuQiwG3+ur5oA1LLgrPRjaQIfR8GVI2h9bYdTjVphdK3171vg27uSRmSN+LogkU6EByfwG353LUy8fPYXPsOiGu9fCQgA2Dh8cUjjUF9sauM+A2M/cYnzQ2Qe/ORWfd3M2GXEmP9jk8MIaFYWweGeNxOupT77IHAkfeF1kymRIpxq7TpxzvPg+esKi4Weisn9JaxIW/fi3b/7ltFa3Wi5UC4d1Y28muJjYnMjfE2FF43fwuC/bjG0wacEb7jDMzAckzyGrg/E+hm2ZZX9ilme6hveEN+j67nhjSM7KHocdQJuZjMDlzETt2k7RnL/l+f44CA+gV2PzExG6Z2ambZysK9OYZwlwt3gPzNEQL4jFf+MK+v5owvc0E7CZyPX7R+s4O+R9Xe95O/B+3LLql63gKfGZ6lEcBFXFYn/20XLVn0YQu5u/mhrvkZ1vTeK6SnhYpCnxNcfE3iCIrtnT0eBBZbCNeTPVTtHRAFWir4tcaqv5En/1eYeU1+P6U38zajPuYL/1VbrCdsbqPGfCxPSwkGfNnZB0v4ebZah0BGwYL3SnxXP+I44FfbTSW3/eiuM+Z10P+XEcHtNpo9gKqAysB2JuEubYO+X2sc8ouknVTyVKuC2rJcB/fm3LBtHwc9tIivK2YzLvf5WNg8vZVGPK9vK9Ya5wTGacAsJ5QSJsUEh8z2YR7fWLOtXriEp1dUgu3uzubTpGdwXEatCnJLsaTuf60AI8Ok5e2rOlPvxJp3zq2AjuZjM/S7UnKzAmMiXR7aSlIKnMlA9oIMGVtgHOqylINl7JK138nJeeff7Bh5Oflyg+2hvoz1d4PiZA/r3c2W7XTrfrR59b23nrt81lna632ce1js9tpdhu7q18+VrdOVg+O9lfXdndPu+u1s93WcatxUqz6PIOzb13+T5IoKxq9Aomwhvl8kcbuZAkpLxKdfycTW3oO3NNlm5dcf6m4+G2qPdcqwbUasEHsLvuM1eaZcs6LMny39OLsFos8L8pstvDirBYKPy/KabruE0wgrwW9rPrtsouzeVcdemm38uEJbGaHlxdlEhddur2Em3k8pRUd55sj22S15zl07ko9TrXeqr2vvG81qvVapVlv1WdPQe3avYWR5zAxURWxaMkyxGVPhvedu9r1SqVVb7aa8+saTrVSrZYqtdJy67haay/X2o36mTNd3JgqXzRmqhWV2eJEpVh1mKorpO+ppksJySui6eJBcfDspc7+OlEROC9kEJ1KuZL8l1/g2s77arVWa1Urtea7RrneajXeVVqzqQ97J5qYP50HmR3xoAYqM3feRN7H74Z2oRScQsJiXiaqmHNyuieHx9MpnrazvrLf2O4e731qftnsNqtfVnYazaPjzsru/mFnr3X2obO6frS7sXWw+WV9/ePRzt7Zysbe3lH1yCZdXhey1Up1ufau3nhxZHfXd+cAu7ZW/7K9dtjqdE4/rG3uHx/uHey0uqvVg50PnVrj8+Fp9+DT5sGXrYONT6fNT93GztbZ583101cIbOtdq1Wvt2ZwTX1xQWAzz30Ksvsb+3OQXT05ON2vre6dnH2u1Y/3djvVg0+tg4PWx9anreP15qejbut0Z3v1eKeztb29ctr68nH9pNndn0L2XaX87n293lh+932wmxAszQ/jG8k8EXN+m+dDlitukl95TvhPl5qTFsFl0+17TrKhMvEJkoA9mQL4drbGySXb3rPh2oDQyZH8PE0ozX8y6mb3a7vPX+COYgKJe/TQtgZE1ARO28kPGFYh6iqDNVZ8sROKM+/Z7nEyjuyCGUl1ac1kPsVBbGIFi9D8kI0kIqN6Yc8A0uZX0gRE+ogXxQelk9mVcqW8bI8QYUjVzd2o7FEsvhgnG8fH+2RlfxNf7doWj7RJ4CjhK1u1TDaxf2AItrFG+ERByQKn7Wg7M1LSj727XpApEsnjdczW5Q+RgWqGD98l8aTQcQjZVHoFig6BFJ7dEgXc+kL2Ir/wWLkkFUtaNiwjeQ9HcpcisU6YyhhakwrwATXTVvKCHH3F/CGQPpgRYDNEFCXSTs7cVxLzb5pwdglkRDkHo13ig4dnNcoxfBG49gJ8lK1dSyHpLklCj+Uof3htJLbe2PfZhfuqS+x7cVRR1pKRRhzbjZNYPIErvIElfBRn2/6BfGZ5xrL+3S3hvKjQizeZe/pwBRwv4XriNpKyveRJBSUhfXj7b2U9X8VXkS2HvQZ9wJ9AI5ZXjBLv5HDbJZT0lRzptFss7bdDVHKsjzof9aNY+9LTS0ZKrpe0f6kRaUkUoDlZap7E5Oo1vtKXA3KD/XxRAqhLRmD7JMIQhI8/WaCowIUJE9oA9XFSSC+ZGBKfKfCM1aFHOddWTqvWYcx8IInH9EGTQI4sJH7IBNMGFMlM3Jpjhg0uYVsn3igYJMZs5e/kkv5IVrkc3mEwGo0mhc9HlvpcDpdoScCopGNRwl0ogFK6f7y13RpaoptQ73KoZCxsu8OUNyS2o7yAGfBMrCgnLESfB5u5STTENAnpr1KRdOsg/TiM3pbJB4mtOEl1BT/Tvoyxy8OyiACm6+WmIX3AvguXeAF4lwRHF+W3vSPrCO0dAENmgriPF82lFIfsbybqUp/L/hIeBJc63U/d7b39zd31cui/tepahYFUgIrvw5AJ7EP5UZORVAa7h5ix6TQxTDq4QODlVBgCXiCT5hfLH7ol2ZX+twQC4kvPdsVYjNrkp59GQHxJhDTYjiqVBqJiIZCJDChUWRKGKEGL8SlHdylGidyWfvopCQBge8Eo5zeWtJ3bu6Kc+VbA3szeBmj6CogZSaIBm+EMOo/wQIk0qPjgyTjiKT4hhmEW4oGKCmMNrC8tjNlJ9cbOKphXecL00btCKugQNGFoXCPhYhce+CVfjkRuXnIwKaqMDAtt0MM105kY1DDkyQERAL4mb0bwI+ek4FnYkoQdil+dNRrZ7QDJfXVy7NBEbPJHhXpvcATqitnzeqbkombtoJIc2K2M2QIUdv9Qz5Y/0naujO2iQX9A10tSMO7UYW/yaAchZfZX4Fz+T/E3W6P3QGgorLUSUS8AUi3jjYD5aLsDZm8tyS+l5Je7FdNwQu2vVqaUqF7a3lzr7h51cUo5MCG3RYNIahNSUVgSi1WEck4KTc0Tx4bbu46ol2i4Tq8lBq7NUsQxNzVOBb5Nz/HnTn6Ov8Asljb47fYWw9CJ4uMxfk767vB07zNdTO88IN2/VP/1XByTO9Rdd3p6bXLspeV+XF5Bt/SDAmUt4JPiPEfvf0In9UMKyfq/F9PHX9Du/CD7063b36qGv7wl+gEZ8ybvbxbub9P5/AAKWc/3N4LwL9Tl/KA7JG+77kC6wH8olpQgzvG5SAAUkbzLa614HkTFWTO9xxN5rfXusTMe/z9E4dKB
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List all Accounts"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/accounts"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint lists accounts by one of four filters : signer, asset, liquidity pool  or sponsor.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./list-all-accounts.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./list-all-accounts.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./list-all-accounts.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-accounts.mdx b/docs/data/apis/horizon/api-reference/list-all-accounts.mdx
new file mode 100644
index 000000000..5a3dbb441
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/list-all-accounts.mdx
@@ -0,0 +1,12 @@
+---
+title: List all Accounts
+openapi: "openapi/horizon/bundled.yml GET /accounts"
+---
+
+<Tip>
+
+**Supports Streaming**
+
+This endpoint supports streaming. To read more about this, visit the [streaming section](/docs/data/apis/horizon/api-reference/structure/streaming).
+
+</Tip>
diff --git a/docs/data/apis/horizon/api-reference/list-all-assets.ParamsDetails.json b/docs/data/apis/horizon/api-reference/list-all-assets.ParamsDetails.json
deleted file mode 100644
index 4942f8dc4..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-assets.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"asset_code","in":"query","required":false,"description":"The code of the asset you would like to filter by."},{"name":"asset_issuer","in":"query","required":false,"description":"The Stellar address of the issuer for the asset you would like to filter by."},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-assets.RequestSchema.json b/docs/data/apis/horizon/api-reference/list-all-assets.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-assets.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-assets.StatusCodes.json b/docs/data/apis/horizon/api-reference/list-all-assets.StatusCodes.json
deleted file mode 100644
index 77cc39bc1..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-assets.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"toml":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}},"asset_type":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"paging_token":{"type":"string"},"accounts":{"type":"object","properties":{"authorized":{"type":"integer"},"authorized_to_maintain_liabilities":{"type":"integer"},"unauthorized":{"type":"integer"}}},"num_claimable_balances":{"type":"integer"},"num_contracts":{"type":"integer"},"num_liquidity_pools":{"type":"integer"},"balances":{"type":"object","properties":{"authorized":{"type":"string"},"authorized_to_maintain_liabilities":{"type":"string"},"unauthorized":{"type":"string"}}},"claimable_balances_amount":{"type":"string"},"contracts_amount":{"type":"string"},"liquidity_pools_amount":{"type":"string"},"flags":{"type":"object","properties":{"auth_required":{"type":"boolean"},"auth_revocable":{"type":"boolean"},"auth_immutable":{"type":"boolean"}}}}}}}}},"title":"Asset"}]},"examples":{"ListAllAssets":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/assets?asset_code=CNY&cursor=&limit=3&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/assets?asset_code=CNY&cursor=CNY_GABGBJYLIC2OGATH3DVW22UEB66TFMWC3VKTAPFIOINVESRZLFKIHA4I_credit_alphanum4&limit=3&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/assets?asset_code=CNY&cursor=CNY_GA6VXTS64XUOCQZSBAYHD24ZYJYPNB3KJ2CVKSYIE43P2DQQIX74UT2A_credit_alphanum4&limit=3&order=desc"}},"_embedded":{"records":[{"_links":{"toml":{"href":"https://swisscustodys.org/.well-known/stellar.toml"}},"asset_type":"credit_alphanum4","asset_code":"CNY","asset_issuer":"GA6VXTS64XUOCQZSBAYHD24ZYJYPNB3KJ2CVKSYIE43P2DQQIX74UT2A","paging_token":"CNY_GA6VXTS64XUOCQZSBAYHD24ZYJYPNB3KJ2CVKSYIE43P2DQQIX74UT2A_credit_alphanum4","num_claimable_balances":0,"num_contracts":0,"num_liquidity_pools":0,"accounts":{"authorized":10,"authorized_to_maintain_liabilities":0,"unauthorized":0},"claimable_balances_amount":"0.0000000","contracts_amount":"0.0000000","liquidity_pools_amount":"0.0000000","balances":{"authorized":"899996000000.0000000","authorized_to_maintain_liabilities":"0.0000000","unauthorized":"0.0000000"},"flags":{"auth_required":false,"auth_revocable":false,"auth_immutable":false,"auth_clawback_enabled":false}},{"_links":{"toml":{"href":"https://StellarAssets.org/fx/.well-known/stellar.toml"}},"asset_type":"credit_alphanum4","asset_code":"CNY","asset_issuer":"GAASPHILC6DCBPP2P4T66QNSYF6C6OGN6DK36NY4G5SBR7AWH75TJG7N","paging_token":"CNY_GAASPHILC6DCBPP2P4T66QNSYF6C6OGN6DK36NY4G5SBR7AWH75TJG7N_credit_alphanum4","num_claimable_balances":0,"num_contracts":0,"num_liquidity_pools":0,"accounts":{"authorized":43,"authorized_to_maintain_liabilities":0,"unauthorized":0},"claimable_balances_amount":"0.0000000","contracts_amount":"0.0000000","liquidity_pools_amount":"0.0000000","balances":{"authorized":"1.0000000","authorized_to_maintain_liabilities":"0.0000000","unauthorized":"0.0000000"},"flags":{"auth_required":false,"auth_revocable":true,"auth_immutable":false,"auth_clawback_enabled":true}},{"_links":{"toml":{"href":"https://masterstellar.com/.well-known/stellar.toml"}},"asset_type":"credit_alphanum4","asset_code":"CNY","asset_issuer":"GABGBJYLIC2OGATH3DVW22UEB66TFMWC3VKTAPFIOINVESRZLFKIHA4I","paging_token":"CNY_GABGBJYLIC2OGATH3DVW22UEB66TFMWC3VKTAPFIOINVESRZLFKIHA4I_credit_alphanum4","num_claimable_balances":0,"num_contracts":0,"num_liquidity_pools":0,"accounts":{"authorized":1,"authorized_to_maintain_liabilities":0,"unauthorized":0},"claimable_balances_amount":"0.0000000","contracts_amount":"0.0000000","liquidity_pools_amount":"0.0000000","balances":{"authorized":"65000000000.0000000","authorized_to_maintain_liabilities":"0.0000000","unauthorized":"0.0000000"},"flags":{"auth_required":false,"auth_revocable":false,"auth_immutable":false,"auth_clawback_enabled":false}}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-assets.api.mdx b/docs/data/apis/horizon/api-reference/list-all-assets.api.mdx
deleted file mode 100644
index 7862e65d5..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-assets.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: list-all-assets
-title: "List all Assets"
-description: "This endpoint lists all [assets](https://developers.stellar.org/docs/learn/fundamentals/stellar-data-structures/assets)."
-sidebar_label: "List all Assets"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlWntzGzcO/yoY/tEmGb38UmrPZO7ktxLXdmonreN4FIqEJNZccktyLfs8mrmvcV/vPskNuLvSyq84vvSaXvWPx0sQBH4EQBDgNQt86NnaKet4j8GzsxqT6IVTaVDWsDV2PFIe0MjUKhNAKx88cK3hlMcJZ89GIaR+rdmUeIHapuh8wwfUmruGdcOmtMI3NXJnmoPMSJ6gCVz7ZkFTlzzwug8uEyFz6Js52+cNVmPEjJMYXcnW2J7yoaN1IWeNpdzxBAM6Ev+aGZ4gW2Nxek9YiazGFCnwW4buitWYw98y5VCytQHXHm/riUDTwA4gjBAiI7iyGYxtpiVodY4QLAyUDuigf9Vgk9qNZZX3GbonLHyUgwFcSofelzLk/GBg3RNEEpnz9kuF6YDJkj7SejxA3HNPS3DwKQo1UAK0FXFTQBngIKzWKOL/dgAOfWqNRw/cSFAe0kxrlDBwNokqpHyozLAX7DkauOA6i3hzcCisk7TpXoww4WztmoWrlPRQJuAwooqXPEk1srV2u9VuL7xcfvnD6srqQmtlUlHbOvnFW9ABiV4NDS/1IFEjI1JyPFJiVEjowY8i9jxNkbsGHEQeHpQROpMIn7gXn+AZ9wKNVGb4HKyDT7TcJ3hGf4rPDejSMsoDd8OMnAKUN//+578CeAw1UAEkDnimc/wj2zvh8cEpMyR0TJaQI3MvWK4gO6sCo1WiwhNsM+GXKsmS0jDiLudQOAyZMygbQHSRPwhuwHEzxHzPF0j4xVYL6sANZGmKriCMBqY8jLiT5HeSoN61Tv3DmmjxKbqBdQk3AsEh99b4B0ArNxDlLewWWo+1q4XWZHJWY5d1n6WpdcFTYEKeEMBrwWVIgBUWTpwWWy36M4/ZUSYEeopQwpqAJhAJT1Otcr9p/uqJ7roiEdf6YBCjWCGb7f+KgjYrdRQEg8rX62llzn1Fh3voPOrB56lGDgd3GVJEPUSLMedsUmMBk1QTtBXqvrUauWGTSdWITnOmZzUWVNBY4WHwMnxjIqUOL74pkSZEVn7ai1tN/vsZm8Ckj1LOLXsPaeG3FULuHKcwoAImj7Crx9pfsIn+xpCtFUd0Pv3motPh4gS/Q6qUh4COHHzntFP/0Kqvnl2vrEzYbKni8I6mVTnm7l5NCJuZ8AgseRZGFBXntC9jF3GajveC7SVcmcCV6WnF+0qr6Y7cmpeZhzkTZCZLekJzlfC+xl6fawrG9/CLtNYEx0V4gESr3zIlVbjqpdbqewjvWOlL0KnA/CXgzKbdg01JQNDchqXHE9rSOxlOgXmI6AY0D5EOdMzaH4NOb+Ydt52nVpJcWEHKPECjkiQL99GUv5kzxDSdTc4m0+M1SjSfxK9ds5gDzseW8vTK4wMr7xejPDeoB/TBYJi7ZOSXhr/Nkv9XG/sn3+UZ8KvvYsLxaum7mNG9ovyociB9rVU29k96O531nfXXJ3vdjcWDnc7x7tLm+58XF99trbfbx9s//ryx9P7Ncedwu3vQ3X+/dfTTh73tN93dznK3JxxKFXpcpyNusmT5bpHLA+vritx+/8vxUXv5l3cHG28/HK13TnY3F5c/nLw+OdxfX3rzenHj/Zujk+7W8tLh4ubbt91fXi6/O17sfE7kmH+SQcydT9MT6HTuMCmOixt6+bHyXmQ+WHnlozaNMWpdPzd2bMr7YyNOvhnf2U3pWK16M1xjG/sn7GbMZ0/Fgt0M+OyrIsvuD8StW3G3dU+Ybc2fOdX4ttB6XKBs3QyMrYfjIGs1WvmP3RUB54bvi31zRNVjoSoH+2F1dXW1ndNV6B+j1NwC8+pVhqoh90ZQLe5NN+No9XMldFY/C83HfS7Oe2hosOQV72yfdY6iYpAH0ugcg8vf3z86R4e73b2N9ubG+uHh4uHycbv9dv/oZLu90T7Y2W9vvllq758s76wcrf/0svPz7suV49c7L/fv84+ncfuf+8fy0p/dPxa+EafIr9Bf5hM053EukXBP1cDC7oVNfn9/eNpxf58/fKXk4Xc/L/7s7tBeaZW/b8Qx/pvT4myWfONlQOOpHhkzrHO8Ymt3V7NqZeId3eusxhIMI0tqDDHkt90RW2NF/kjlM3QXZak9c/px6Se7q554nNPBPoaxdeexxHE3x0FGLYHH8NwuKcGUXM+o0jmwMV4Ud5KiukjKo/P57Faj1Vgg/bIk4e5qRgWpsxdKxlI27B4fH0LnsEvlRGpYUK0yVOr2xaoN6AZQZoixSWIkOKxH4HykjjNTZ2UmUEL/6i4WeVWdSiDTCilyr6gib0FY47MEy6n8Ah0fIlSKi+BQ86AuYl8gFtxnVdS6dQpNQJkL4jB16Kkbk1ewM58LVQq0YR1SZVf5qHlFj75TcojQxzBGNLR8ru38zENn6VLq8zbFmGuNwddAokDybU1uA3gpRlQt9rXIIe9w5AE2SjStCAcLPuvHwrHjxvPYcvA1iIVs2qIiWkHh9TWqu+f2DniBppSjOjs2NqYzG7cs669uCafVDf1so68Quymsw7qxEp//pazno/loyuWoCdJHGkJPWF4oDuLdT3s14NB3duzRxRWsmbYbp1gfbb55ZFM10NHX9PLcE9IWHJI5RW7CUsXlUoUr4n9lM0fWRoDWYIyxgZMkaGRsJhJQ3NDCoIwPyCVNSvi5MkOQyqEIcQ8F19pHPeO2DjMlEXKP6aOHkR1HSGSijKJMDEoTj+ZYYkNLxJ7OM4eD3Jij/ptTTb+HdW2HMwzG4/G88lPKel/bYZPXDY7rPjN1OoVGWC/Oj+exjeQtuQkX50NnMyPBmpvekNuOEyMVkJrQXINKyOcxiTtvi55Twn+1DoqjA/pZkj5vwLalHmFesqbPvG8zaj9FEQnAYr2paViJfe6xBmKE4hyIuqp/bGrtELQzAIYqjLJ+zGgLHKbd80LVZl/bfpNylubm1vutvYPD7v5OI5HP43at48A6pI3v41AZapB972FsXaC2pgqxy26GUQ4KAyoKgWJk865clI/cEvatfEogAGlFbNdFjNbgxYsxgrRgbKCnBdZ5BJcZQ0KUQNGW5WGIA1mM5JrcpRolprb04kUeADA2qbnWV5F1nNu74FrJqGDv1tmGZPoOIYwteKQXBYGcxwh0pggqEoXNUl3gk1AYVgmlU9yEaGB9G2Es88SrOKtiXo050yfvSrjhQ/SgyLjGpgYpdyjr0o7N1LzsYF5VmwaVxKBHaxYzKahRyLMDMIjSw7Mxfq81VDyLeqUeOHxkGzyNxwGx+8im2JGJUBMDXeIPBkfoLpTAahWusrORqG4H8SgjsjxR5yJWUos+cyl21aC3yfXi5lPePJfszad2mHAVR1Fr+/fqWCyQCzQeK2t1Ui5GCIsNyseVJNsdqHg3y0fq+chsxSKc8DgadSqY+uZed2Nr/2iLpjRGobgkptaHhJvKklTBjg9gpg9R5pKG61nX9498OlNcawNehmaquYp1/AjDdZHbnzI+ffEzsj7Ql+trCk3vnJ5M6HP+SIAy/gdU/OJXM/cIl19W5p7vFFcUFq8ID4rw1d7PPEK46SOfefGUr17LHrCKP/6JzQMqTh8NPVm5P81LmgdQKN8QPRGE/6NXMw+AVL4nmoF0Rv84ldcuTqn1N0JOSM6KER0hMK3OuvUwZq4YsbN1zCaT/wAQjjl6
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List all Assets"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/assets"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint lists all [assets](https://developers.stellar.org/docs/learn/fundamentals/stellar-data-structures/assets).
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./list-all-assets.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./list-all-assets.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./list-all-assets.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-assets.mdx b/docs/data/apis/horizon/api-reference/list-all-assets.mdx
new file mode 100644
index 000000000..18501b4f5
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/list-all-assets.mdx
@@ -0,0 +1,12 @@
+---
+title: List all Assets
+openapi: "openapi/horizon/bundled.yml GET /assets"
+---
+
+<Tip>
+
+**Supports Streaming**
+
+This endpoint supports streaming. To read more about this, visit the [streaming section](/docs/data/apis/horizon/api-reference/structure/streaming).
+
+</Tip>
diff --git a/docs/data/apis/horizon/api-reference/list-all-claimable-balances.ParamsDetails.json b/docs/data/apis/horizon/api-reference/list-all-claimable-balances.ParamsDetails.json
deleted file mode 100644
index bfb7dcd0a..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-claimable-balances.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"sponser","in":"query","required":false,"description":"Account ID of the sponsor. Every account in the response will either be sponsored by the given account ID or have a subentry (trustline, offer, or data entry) which is sponsored by the given account ID.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"asset","in":"query","required":false,"description":"An issued asset represented as “Code:IssuerAccountID”. Every account in the response will have a trustline for the given asset."},{"name":"claimant","in":"query","required":false,"description":"Account ID of the destination address. Only include claimable balances which can be claimed by the given account ID."},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-claimable-balances.RequestSchema.json b/docs/data/apis/horizon/api-reference/list-all-claimable-balances.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-claimable-balances.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-claimable-balances.StatusCodes.json b/docs/data/apis/horizon/api-reference/list-all-claimable-balances.StatusCodes.json
deleted file mode 100644
index 3259d68fc..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-claimable-balances.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transactions":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","operations","transactions"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"asset":{"type":"string"},"amount":{"type":"string"},"sponsor":{"type":"string"},"last_modified_ledger":{"type":"string"},"last_modified_time":{"type":"string"},"claimants":{"type":"array","items":{"type":"object","properties":{"destination":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"predicate":{"type":"object","properties":{"and":{"type":"array","items":{"type":"object","properties":{"or":{"type":"array","items":{"type":"object","properties":{"relBefore":{"type":"string"},"absBefore":{"type":"string"},"absBeforeEpoch":{"type":"string"}}}},"not":{"type":"object","properties":{"unconditional":{"type":"boolean"},"relBefore":{"type":"string"},"absBefore":{"type":"string"},"absBeforeEpoch":{"type":"string"}}}}}}}}}}},"flags":{"type":"integer"}},"required":["id","paging_token","asset","amount","last_modified_ledger","last_modified_time"]}}}}},"title":"ClaimableBalances"}]},"examples":{"ListAllClaimableBalances":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances?asset=native&cursor=&limit=10&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/claimable_balances?asset=native&cursor=35938300-0000000017b9a95e25aa60200b52cc04f75c496dca76dc19fec21c942dfb35cce23c3eba&limit=10&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/claimable_balances?asset=native&cursor=33324106-00000000691787983bc3ea12361092fe49ae83cbbe37804ee1590fe2b9b3e3860fc8261f&limit=10&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000691787983bc3ea12361092fe49ae83cbbe37804ee1590fe2b9b3e3860fc8261f"},"transactions":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000691787983bc3ea12361092fe49ae83cbbe37804ee1590fe2b9b3e3860fc8261f/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000691787983bc3ea12361092fe49ae83cbbe37804ee1590fe2b9b3e3860fc8261f/operations{?cursor,limit,order}","templated":true}},"id":"00000000691787983bc3ea12361092fe49ae83cbbe37804ee1590fe2b9b3e3860fc8261f","asset":"native","amount":"0.1000000","sponsor":"GDOZMXWISPB57FITUQIGTFH2KNNW7QTFESXF5DZEAMZK6QHE3KVO5TRT","last_modified_ledger":33324106,"last_modified_time":"2020-12-30T23:02:56Z","claimants":[{"destination":"GCD3T6UIQLYZPGRCYVSE7LKQB5HYYNVT7ENY6RCSFRFQYR5JTBDCECO3","predicate":{"and":[{"abs_before":"2020-12-30T23:03:56Z","abs_before_epoch":"1609369436"},{"not":{"abs_before":"2020-12-30T23:05:56Z","abs_before_epoch":"1609369556"}}]}}],"flags":{"clawback_enabled":false},"paging_token":"33324106-00000000691787983bc3ea12361092fe49ae83cbbe37804ee1590fe2b9b3e3860fc8261f"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/000000003a9a08342ca45d96abc011278644d83d1718ab16e44209fa1952829b66017c28"},"transactions":{"href":"https://horizon-testnet.stellar.org/claimable_balances/000000003a9a08342ca45d96abc011278644d83d1718ab16e44209fa1952829b66017c28/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/claimable_balances/000000003a9a08342ca45d96abc011278644d83d1718ab16e44209fa1952829b66017c28/operations{?cursor,limit,order}","templated":true}},"id":"000000003a9a08342ca45d96abc011278644d83d1718ab16e44209fa1952829b66017c28","asset":"native","amount":"1.0000000","sponsor":"GA5ACYSBFH5AFWMZ5T34FLT5W3X6Z4FT4PMN3NUDT3G2JCYJXYGD72EF","last_modified_ledger":33505955,"last_modified_time":"2021-01-12T21:02:00Z","claimants":[{"destination":"GCXAULI3NAFEUKIXUQTD3HXGCTTLM6KVGKTUBZIHVUDP6WXEF7RWJV67","predicate":{"unconditional":true}}],"flags":{"clawback_enabled":false},"paging_token":"33505955-000000003a9a08342ca45d96abc011278644d83d1718ab16e44209fa1952829b66017c28"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/0000000063036dcfa438cb51180bea16e36850e3699efc934577b07322c818157e4d5411"},"transactions":{"href":"https://horizon-testnet.stellar.org/claimable_balances/0000000063036dcfa438cb51180bea16e36850e3699efc934577b07322c818157e4d5411/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/claimable_balances/0000000063036dcfa438cb51180bea16e36850e3699efc934577b07322c818157e4d5411/operations{?cursor,limit,order}","templated":true}},"id":"0000000063036dcfa438cb51180bea16e36850e3699efc934577b07322c818157e4d5411","asset":"native","amount":"0.0010000","sponsor":"GBIIQM26JJS774T7CSP3WBFVUXHUCTZCV5ZPGMKL57POWMFPMLYOKOZQ","last_modified_ledger":34254613,"last_modified_time":"2021-03-03T10:36:28Z","claimants":[{"destination":"GBIIQM26JJS774T7CSP3WBFVUXHUCTZCV5ZPGMKL57POWMFPMLYOKOZQ","predicate":{"unconditional":true}}],"flags":{"clawback_enabled":false},"paging_token":"34254613-0000000063036dcfa438cb51180bea16e36850e3699efc934577b07322c818157e4d5411"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000d076fe2df3e6cc5e5c28e7bf257c11eb209d703a681c58bb867b78b67235c694"},"transactions":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000d076fe2df3e6cc5e5c28e7bf257c11eb209d703a681c58bb867b78b67235c694/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000d076fe2df3e6cc5e5c28e7bf257c11eb209d703a681c58bb867b78b67235c694/operations{?cursor,limit,order}","templated":true}},"id":"00000000d076fe2df3e6cc5e5c28e7bf257c11eb209d703a681c58bb867b78b67235c694","asset":"native","amount":"0.0010000","sponsor":"GANVXZ2DQ2FFLVCBSVMBBNVWSXS6YVEDP247EN4C3CM3I32XR4U3OU2I","last_modified_ledger":34255259,"last_modified_time":"2021-03-03T11:35:31Z","claimants":[{"destination":"GANVXZ2DQ2FFLVCBSVMBBNVWSXS6YVEDP247EN4C3CM3I32XR4U3OU2I","predicate":{"unconditional":true}}],"flags":{"clawback_enabled":false},"paging_token":"34255259-00000000d076fe2df3e6cc5e5c28e7bf257c11eb209d703a681c58bb867b78b67235c694"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000da8ed8d0dccacce237c5395eb07bb845d2bb96425d18d168d535063316d99e7f"},"transactions":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000da8ed8d0dccacce237c5395eb07bb845d2bb96425d18d168d535063316d99e7f/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000da8ed8d0dccacce237c5395eb07bb845d2bb96425d18d168d535063316d99e7f/operations{?cursor,limit,order}","templated":true}},"id":"00000000da8ed8d0dccacce237c5395eb07bb845d2bb96425d18d168d535063316d99e7f","asset":"native","amount":"1.0000000","sponsor":"GB7OYQFQI7GH622CKCFWPH4WSZUGOXXNY2XWV5K27S3SW2JHOWCCWEJ4","last_modified_ledger":35023766,"last_modified_time":"2021-04-20T19:00:04Z","claimants":[{"destination":"GAV2USD4ELGLRWBT67V7N37QAJKOPLHUJL3AVFW5NHWDHVXL4EQPSWZ5","predicate":{"unconditional":true}}],"flags":{"clawback_enabled":false},"paging_token":"35023766-00000000da8ed8d0dccacce237c5395eb07bb845d2bb96425d18d168d535063316d99e7f"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000c551a949d0fb5199b05cb8220b4ba7dad4cd7968c849ab0fb51f744daab864fe"},"transactions":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000c551a949d0fb5199b05cb8220b4ba7dad4cd7968c849ab0fb51f744daab864fe/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000c551a949d0fb5199b05cb8220b4ba7dad4cd7968c849ab0fb51f744daab864fe/operations{?cursor,limit,order}","templated":true}},"id":"00000000c551a949d0fb5199b05cb8220b4ba7dad4cd7968c849ab0fb51f744daab864fe","asset":"native","amount":"0.2091529","sponsor":"GA5WWLUYCR4XJKS4ZYKWATKC7E3AVM3FZLWXWSKOBZWAGDROF5MUQXAT","last_modified_ledger":35530330,"last_modified_time":"2021-05-22T17:04:31Z","claimants":[{"destination":"GCSZDAUKEX3IZXXUEEMERIYTVKHDTVTWK7LHXHELZE5B472QMGGXQLHD","predicate":{"unconditional":true}},{"destination":"GA5WWLUYCR4XJKS4ZYKWATKC7E3AVM3FZLWXWSKOBZWAGDROF5MUQXAT","predicate":{"unconditional":true}}],"flags":{"clawback_enabled":false},"paging_token":"35530330-00000000c551a949d0fb5199b05cb8220b4ba7dad4cd7968c849ab0fb51f744daab864fe"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000d1f2ad9c1ff9124de62f9721ed5811f1f0d7705660c5a7daaa174ad5100c6b4d"},"transactions":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000d1f2ad9c1ff9124de62f9721ed5811f1f0d7705660c5a7daaa174ad5100c6b4d/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000d1f2ad9c1ff9124de62f9721ed5811f1f0d7705660c5a7daaa174ad5100c6b4d/operations{?cursor,limit,order}","templated":true}},"id":"00000000d1f2ad9c1ff9124de62f9721ed5811f1f0d7705660c5a7daaa174ad5100c6b4d","asset":"native","amount":"0.2091529","sponsor":"GA5WWLUYCR4XJKS4ZYKWATKC7E3AVM3FZLWXWSKOBZWAGDROF5MUQXAT","last_modified_ledger":35530330,"last_modified_time":"2021-05-22T17:04:31Z","claimants":[{"destination":"GBO4FL74OZTOCTABWFS2PH4LGI2CHFABDZ2LBPRH6UECXBAIU5LUIOF2","predicate":{"unconditional":true}},{"destination":"GA5WWLUYCR4XJKS4ZYKWATKC7E3AVM3FZLWXWSKOBZWAGDROF5MUQXAT","predicate":{"unconditional":true}}],"flags":{"clawback_enabled":false},"paging_token":"35530330-00000000d1f2ad9c1ff9124de62f9721ed5811f1f0d7705660c5a7daaa174ad5100c6b4d"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/000000001b53636a29ca25d28d1c5bb165f55280167d53cfefb0ce297d98032b32f772d0"},"transactions":{"href":"https://horizon-testnet.stellar.org/claimable_balances/000000001b53636a29ca25d28d1c5bb165f55280167d53cfefb0ce297d98032b32f772d0/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/claimable_balances/000000001b53636a29ca25d28d1c5bb165f55280167d53cfefb0ce297d98032b32f772d0/operations{?cursor,limit,order}","templated":true}},"id":"000000001b53636a29ca25d28d1c5bb165f55280167d53cfefb0ce297d98032b32f772d0","asset":"native","amount":"4.2696061","sponsor":"GA5WWLUYCR4XJKS4ZYKWATKC7E3AVM3FZLWXWSKOBZWAGDROF5MUQXAT","last_modified_ledger":35686528,"last_modified_time":"2021-06-01T13:29:59Z","claimants":[{"destination":"GD54EZPKQCBZKPI6F4KKYYLGLDWBOVKPXBL3BLFGYNCLTBFGFZZGVMRT","predicate":{"unconditional":true}},{"destination":"GA5WWLUYCR4XJKS4ZYKWATKC7E3AVM3FZLWXWSKOBZWAGDROF5MUQXAT","predicate":{"unconditional":true}}],"flags":{"clawback_enabled":false},"paging_token":"35686528-000000001b53636a29ca25d28d1c5bb165f55280167d53cfefb0ce297d98032b32f772d0"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000ff1bb4a01b1d4e62ba23bcfd4e2c2289c63fe5ae0368f85b79d74a2224f8ab6c"},"transactions":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000ff1bb4a01b1d4e62ba23bcfd4e2c2289c63fe5ae0368f85b79d74a2224f8ab6c/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000ff1bb4a01b1d4e62ba23bcfd4e2c2289c63fe5ae0368f85b79d74a2224f8ab6c/operations{?cursor,limit,order}","templated":true}},"id":"00000000ff1bb4a01b1d4e62ba23bcfd4e2c2289c63fe5ae0368f85b79d74a2224f8ab6c","asset":"native","amount":"29.8872425","sponsor":"GA5WWLUYCR4XJKS4ZYKWATKC7E3AVM3FZLWXWSKOBZWAGDROF5MUQXAT","last_modified_ledger":35686528,"last_modified_time":"2021-06-01T13:29:59Z","claimants":[{"destination":"GB2QQWOA32GRILAOZ57H5Z5MO52KNUO3WHJWVZZHWSN66LLDPXQMSILD","predicate":{"unconditional":true}},{"destination":"GA5WWLUYCR4XJKS4ZYKWATKC7E3AVM3FZLWXWSKOBZWAGDROF5MUQXAT","predicate":{"unconditional":true}}],"flags":{"clawback_enabled":false},"paging_token":"35686528-00000000ff1bb4a01b1d4e62ba23bcfd4e2c2289c63fe5ae0368f85b79d74a2224f8ab6c"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/0000000017b9a95e25aa60200b52cc04f75c496dca76dc19fec21c942dfb35cce23c3eba"},"transactions":{"href":"https://horizon-testnet.stellar.org/claimable_balances/0000000017b9a95e25aa60200b52cc04f75c496dca76dc19fec21c942dfb35cce23c3eba/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/claimable_balances/0000000017b9a95e25aa60200b52cc04f75c496dca76dc19fec21c942dfb35cce23c3eba/operations{?cursor,limit,order}","templated":true}},"id":"0000000017b9a95e25aa60200b52cc04f75c496dca76dc19fec21c942dfb35cce23c3eba","asset":"native","amount":"0.0000400","sponsor":"GB6DNEWWSSPQAX7SR5MCWUTRVQPJBAERJTUQAZOVXXJDU2E6PIMKGMO2","last_modified_ledger":35938300,"last_modified_time":"2021-06-17T10:37:03Z","claimants":[{"destination":"GC2CMMOQ2BUFI33PPOLNJKMQYJGAXUP2KMZXEXE6TGE37JSXQPHI4UAE","predicate":{"and":[{"abs_before":"2021-07-16T21:00:00Z","abs_before_epoch":"1626469200"},{"abs_before":"2021-08-16T21:00:00Z","abs_before_epoch":"1629147600"}]}}],"flags":{"clawback_enabled":false},"paging_token":"35938300-0000000017b9a95e25aa60200b52cc04f75c496dca76dc19fec21c942dfb35cce23c3eba"}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-claimable-balances.api.mdx b/docs/data/apis/horizon/api-reference/list-all-claimable-balances.api.mdx
deleted file mode 100644
index a357bb54f..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-claimable-balances.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: list-all-claimable-balances
-title: "List All Claimable Balances"
-description: "This endpoint lists all available [claimable balances](https://developers.stellar.org/docs/build/guides/transactions/claimable-balances)."
-sidebar_label: "List All Claimable Balances"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlXOtu28iSfpUGf8wkA8kmm3cBg7O6S9bdulqZINPsLkqcUKQOSdnJMQzMayyw+3LzJItuUrJ8ie2JrD2eOfljxKyuruvX1TSrrqWELGKp8EEq+8RbEccHVCI+CSjE0secxCCmkbdOvDCQCtJo6cUIArYOvSBBvhcnMSK+j8gl8Xyx9gPdsXEyNh/fLZNkHRdOTxlcgh+uIYpP4gR8n0QnYbQ4ZSGNT52N57PTxcZjEJ8mEQliQvmu8emOY37L8f2JlJM4H8IpmkwqSG0vToq+v1Nip0NOWpOIrCCBiKt5LQVkBVJBitdhEEMk5SSPa/bPDURfpZwUwT83XgRMKrjEj+G+AYqUhpsgQc0KCl2ULAEJPmF0gqqXEH1FJCPwAvE0gnQfdOX5PgIvWUKEnN0qYMj5KggX3iUEu9WcfYSW5BIQQfHGgSCJvqJ3SbSJE98LIIdC14Uox6kYSQgSBO/R1dKjS+TFz/PnFozpElZEKlxLyde1sEkSecFCyknwhazWPv9VvdIZDLpnHW3cNgfNomH0zXPcnzc6g2Z3Oi91TLNULXUa7dqsop9Vx8VG/cw8187m0s1NbmdrEseQ/FlLB8iL4w0wJFajCNYRxBAk4jfoj9//pxwyKDQ5TZS5pVn54/f/fZEnMtPuDIrcMNq3E9/yRNpTIQ3C4E9r8SBeGMSJF4jARYSxCOL4BPUC/yvyAupvGKCHGZT5lZKAx454/pRn98XeRHH4p4McBZuVA9wgJEEi12OUhDwU10A916PID2mqghcggmjo+yCylWu5tXSMSMB4MK43vg8MuVG4EhKvycILFp+S8DME6JL4G+DLCIqAhhF7NDK9IIGFyNZdaBqGbBiKqZmWrduKrO8HXBixP5/a3DXeInNN5i3BiCuZeiCVMEbxMtz4DJH1Gkh0gnqCR7zz4K8kpr+idySmEDAvWLznefor3+5X9I7/yH59gpp8Gy9GJFpsVsCjNQ7++P2/ExRDkkNeghi4ZOOn9hdsn0ncYLPiYE5iKqUKSh/3DeN7K+/PxvBoCWhFvnirzWobGMLLqSkiSDZRAOwEcTrBXwRqRIIFpD5XuPBYllEekQBt1muIMkIRYF6MliRiNGTAuKkbYeT9KwxESq4hcsNoxbMARUDiMIifMNrWgcAe2E6RXxpXinxz85EbJYtiTo1lmf+4a5fhhlKI+QlDwyCBIOEkZL32vTQ3Tn+LOd313q7E93uuOIWy/UPnN6DcIeuIn2eJl+73yfeCz/GenN+gi8F3n6daRuA+FizCsomIiuCzdJOTElitfW6+PWonDH0gAcfzvUD5kDL9mJMSL/Fhj0cAX5I3JtI6gss3JdINJ9v+qi1czXP0mZiAlQOM3dn2G6RZbu4RkigiPNW9BFYviKu/cPztysIXiP//Kth+TfumRLtHJHx6x473ZP94k5M89phwW74eE2m3d8w/pL7JZWXho09WvJh59FFW2T76zCdx8mkVMs/1gH3ygXFof54w8fjZ+AjZtug7IJP2yr3HLLYmSQIRP03qH4r5uZy3P17r+s2eLbMaMcMxxs8WeH5bErDvl/mOdf/k2gj8Erhh9LhBiRO/5Gl1HdLlIyQCN4PwBefLJqBhwDxuduI/lhm5o0ua/ctJri9u2A9qjvuJ5zHpXtLkdjenLCG+EeKPBvTHm7vnzMOr8Q3P5KzuEQJ+8xJduJZEnX73bNiif4pV0vaWv0zrt3wCcRJAcueqv7vbfNrebf4hVPyZp8gl/JDeV37+QZSHPyvyD6IA/5mXs3u1xetvqOq2aqmynJezf4rp2MTWAeuEGDKWZUfHlMqaa+pUsw1GiWkwqtguUKxQW8PMdVSdUsAqVcEh39BgW4ocQQNVxZoiGzsNDFsxLdO2VIeqQBSsGopsYxc0m4ClUscB1bRkDUDRbdkF7NiOCqplyC61sKG49zUQlwkeUHcKkV2p8eHVI+P0tTR57PR9G5LdedF1/Y/UlTlh+JywujgJbk/4JNrAgxrnjahyK9RLFcnqCOnV/LwrKaQ0N26BsyDJJ0q6i7RXQ0j1Sm/emU2bw35JN2vN0XjQrI9qDdzqdqfmYFSrDmc1vTKvFjvzljFoVNXWpKePzkffQuLCNg0frzEkLGM5r+C8Ko+wWpBxQTfm0p1C48O9mkGqlyvqyBg3B+2Leb9+Xr6YDKtmuzUo6Y2Li+5kZFa7F8Z5eVg7rw0uzvWzUalSrpZ7qnSvYBAlwYdrfnZ9crKj7b48aibPLc0nSE84STFkWzVsTTXS90vpKfwUM/1ZZrpuSDc3H8V9e3dKUp9cOYR+/gQBj9TtW4kHBaX06ognFDsWiKnEJrKlapgSTWe2QRwqKwo2LUPTmKUyxVQs4igGaBqWbZcoto4tbDuGISsmxdbxQOxQyd4QiB2syuEgdrCfnwIx5UR+DMSKerF8MSzVGnqxNu3M9ZGq1dojfarOjLlWG2n9TlftjisjtY7Pyhdns4t6xcTV2hMgpsu6revfBjElLyt5BY+wwkFMlp8HsVlx3G6q3WKtOm41Z+PBqKI2ZvXyaNTuGK1JvTUal+bNxmRc6RvTWbVmnk/PJoZ5H8Tu1fWpB74TPVId86+YoEcsgVRZNRh1iaZa1NEVxZIdIIoBqmHpMqiGbYNLbVXTTdORTRVjaimWopugMV1TlCOWQAdK9obQ42BVXqEEOtTPT5dAsqw8RI9SsznoYOPsbGia2sgsD/vqtFSbjGeNcXk0L0/0eb/eabV1s9+bdmr9Tvui1+rNB99GDw3rmqGoT6KHmpfVkSIXVKOArWfR4/tFPBZ6ZDrmXzFBj4ceTDYNFzBzVTAo1UGn2ALTcbFuUkUBB8s2M2WVGJZCdctxLMN0TMsxTKzq1LC146HHoZK9IfQ4WJXD0eNgP38HehS7k9kcVwa4VmtPyqXhpFMqdSfT4WxoXEyqlT7WzGpXK6vljtpU8excG6u9MW4+iR461u0XoIdSUPWCqjyLHt8v4hHRg+uYf8UEPSJ6EAuYxWRGKREvuEyqq7YOjmw6jqXpDDuObWhYZ4rFFMNiuqrLhqoqBrNtMI/4+uVQyd4Sehyqyiugx6F+/o6bS8nsXQxqg6ZZbxgYl1vl2rTf0KbD+bjem826F3g2negtbA7V4RSfNXrTcnlaPdO+jR66jFXTeOL1i5KXtTyWR4pdkOWCrD2PHhM8Hla0arvePp+WRoY5MbuqOSietXr9dmN81laLk9pU7zamlcZk1taqg/5wOtePiB6ZjvlXTNDjoQfVdYXYms1k19EV23ZknToWxrKjOcRkhGmUmbZhUUuziSOIXFPTGCGOZWguHA89DpXsDaHHwaocjh4H+/np2gPLtqJj+/57j+m0Pb4on2uzs9ZQm1+0psVRq2xW1eKko9bm7elsOmz1SvNpsV4579X0zngwKz7x8lbXVVlV5SfRQ89jPFLMgqy9pPYoD+eV4rhVnanN+Ww2rlY71fPmxWjSalRGk9G0ZbYbs0a1Pa/qJc3Eg069Phu0G5UXoUfuIVZ9t0GOhlWpRfOvCAdHrHQUFxNmU8V1bQVrDAzs2iZWgOmWoriKKzPTlHXDkKnOhSVEMTXCdEWWqeFo7IiVzoGSvSGsOliVV6h0DvXz3xOrSj2t1ja13nzUK4+KpWltiPsNrV1v4nKjVixV5rhd6p83jHG1PCsVm2O9PW72avhvi1WvAAfHwyrF0VVDNQi2KcE6wxZTqO44iqG7uo4tWTFMpqvUBdeRKWDbZLYlq9hRsWuamMnHw6pDJXtDWHWwKodj1cF+fgqrtBNs2IZsKMfGKsMydGw9iVVGXlZGilrAdkG3n8Wqiq5V5/3WoFyat/pNo6a1WhcX7Xq7Mi31Jq3+rNRWS+1a/aJbbo9KtXptPq9POucvQ4+/BFalFs2/IhwcD6tcV3EcjciKozANDOwQrDrUZRpgirFlU0N1QScgq4blWrpj2szUCMZYcy3iGPR4WHWoZG8Iqw5W5XCsOtjPT2EVtk8sy8Qa1v9yYFXCg8G0V1Rx/bzZLvbmutnQ53qnp+NWd9xTp42z6WQ+b0yHXcNotyv92aAzbLb/RpfAe2D1CnhwxMLqwC8/j1hYHSjZGwKrg1V5hcLqUD8/98cyWdYevO42Kt3qdDoc9gfFmTk81zvl6Xh0Phn0z0rF6vnZaDwoznuT2eysMsZVo9/stOqdHn4Cq9LPlp/BKsUUf2o3C7L6/AsrXO50egNcGteaqtrv99rds1ZncHFWL87GfdzqzGfVWdUY1auqeTacDfqNpjYuVl/6taGSl828YogPh+Tsw6FHPxDEhmbYvO+O5/ojXKyXcbEVzTQ4l+/+yvC1vwwXomx7A1aQLEMelQvxmf+aJFzuRzKHxxFEl9sm9k3kvywJpce6OUcpHepCchVGn4WJH+fobpJNBC/hWdtSomDL9SPvM3VD0fqQNSFkvZ1STuKqpKvlE/lEXEA2qxWJvt5SoXUUXvJ5ALxttDEa9VGx3+TNnKLlPevrHqZybXc9QU3e8r0AMZogYCiCvDBcnHZf85XrKGQbettBfY9F2tPMG612/alAYo/3Q4eIhkG8WcF2KbmEiCwA7bV9ogh8gQecXLQ73/aw5sPIS1vYhSC7nvYUydAmToXaClQOI+B9tV4sNN/Tw4k8tgDkQHIFvPt7vU61vbuyH4W8OyZGvvcZ0BXxfUjiHGJA+bwA4nv/AobgC13yXt04Jzik3fai9T4SEu36cZOQjyIQbbt750gOiTZi7qJtD3oWs2I6QZxEQFYILiHYyrG/WrSV71aePIis//RI+LDv0GcHaWRin9IwgnwQMnj/HxU9vwS/BNvtslkJRLRoA0OXHkF0fN7OIYKcKLyKs+kZYQDbXv+drYeV1guHliRh6MenMfscc0uHKAIeToIbDXlb1Rcv+cr5fw03EY82btAcugLRPr9aQcD4I2EoEvCNkRfECRDGF63IZy9YIOZFQBPhQ0p8PxZ6CreKaSkozRgHYrQMr4RJ2MoLvDiBCG1DXITj1jZ8C9FR/y4CNw1moX9lp+mPqOSHi1sbXF1d3VV+R5l3/HBxSvIBXOXjTZDnp9AS8tn58V408cchTxNCPy+icBMwFAb3syGNnYguvQRosomIj7wVz3lYCc+HWcf/ivwWRig7OpCzWa3fn6BayCc0pI2xYqqGE254878QkRsw228XGiEDh8SQQ3QJ9DPi1Pv6i5ECdW7aWwMsvGS5cU5ouDrN7LD9uVX11PFD53RFvOC0Up1U271+s1s/WbH3wl1ptyB3vAMLL+DjCX6M0VUYJXyohJeIYjZYpBNlIOD1W5AgoMswnYkg5ONpiboh+x4gQCykYliCsFEB/fTTFSAWoiBM+ECfMIoBRZsg4EJsDcVdlsIQQTxiGPF5uuyjxC6WfvopBQAQI0KI738VrMXaT5fE95hQ8NODsw146EeAkqsQxcBn9SQ8eQIKUZCBCgMabtZ+Zp8Vh2FvtQ6jhASJCDAnFGb0PeJ4Ps84vmovvE7uhD7PrhUJyAJi5PHgugpyaE0iYHkWXgW78Ardu6qG68RbCdDje2YrOahxyAtdFACwGL27gh99H+1lFp9UESOCfpHKZC2OA87uF2lnOx4i4sISreKeO4To0qOwV4zte1YQ5UNXHGWcLJ0+Qahox8mmfGzF3g/oGk+9tMrP3Sv27pZ2sCKeeAq+H/7X/jPeOO1RCGLY26u4JnQJCJ/wq47HeOy6Hr+bZE/y6ZPbHTM4IeKp0CljGp+2m+Vqd1jlS06WycoX7YbrME5WJNjbkrepoqLvo0dGVt0rIK5vZ3O8qeFVWStwAl+S07VPPNGRLGx0nV0CPkiPXAI+5qRlGCf86fU1x7Bx5N/c8F+ns1zEfc6L9280TxjkbzXM6lGLfoavd0Z9ZU3MkpS9NvuGXd7A6KknFdp2hb9QnX/HDKon5d8bpnVXhZeH7r99RNVT6m2Hbn23cn+ZSVRPWGE7g+s7jfA3mjr1hJG287hujfSR/yfyuJWkwgc+oWEJhFuSY3u6qEgprPdXPRg6xbnsXi3VqyPp5ub/ABLoIY8=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Claimable Balances"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/claimable_balances"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint lists all available [claimable balances](https://developers.stellar.org/docs/build/guides/transactions/claimable-balances).
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./list-all-claimable-balances.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./list-all-claimable-balances.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./list-all-claimable-balances.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-claimable-balances.mdx b/docs/data/apis/horizon/api-reference/list-all-claimable-balances.mdx
new file mode 100644
index 000000000..0d92c7d85
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/list-all-claimable-balances.mdx
@@ -0,0 +1,4 @@
+---
+title: List All Claimable Balances
+openapi: "openapi/horizon/bundled.yml GET /claimable_balances"
+---
diff --git a/docs/data/apis/horizon/api-reference/list-all-effects.ParamsDetails.json b/docs/data/apis/horizon/api-reference/list-all-effects.ParamsDetails.json
deleted file mode 100644
index cffcdc7ce..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-effects.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-effects.RequestSchema.json b/docs/data/apis/horizon/api-reference/list-all-effects.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-effects.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-effects.StatusCodes.json b/docs/data/apis/horizon/api-reference/list-all-effects.StatusCodes.json
deleted file mode 100644
index 14ff4b5ce..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-effects.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"operation":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","enum":["Account Created","Account Removed","Account Credited","Account Debited","Account Thresholds Updated","Account Home Domain Updated","Account Flags Updated","Account Inflation Destination Updated","Signer Created","Signer Removed","Signer Updated","Trustline Created","Trustline Removed","Trustline Updated","Trustline Authorized","Trustline Deauthorized","Offer Created","Offer Removed","Offer Updated","Trade","Data Created","Data Removed","Data Updated","Claimable Balance Created","Claimable Balance Claimant Created","Claimable Balance Claimed","Account Sponsorship Created","Account Sponsorship Updated","Account Sponsorship Removed","Trustline Sponsorship Created","Trustline Sponsorship Updated","Trustline Sponsorship Removed","Account Data Sponsorship Created","Account Data Sponsorship Updated","Account Data Sponsorship Removed","Claimable Balance Sponsorship Created","Claimable Balance Sponsorship Updated","Claimable Balance Sponsorship Removed","Account Signer Sponsorship Created","Account Signer Sponsorship Updated","Account Signer Sponsorship Removed","Liquidity Pool Created","Liquidity Pool Removed","Liquidity Pool Revoked","Liquidity Pool Deposited","Liquidity Pool Withdraw","Liquidity Pool Trade","Sequence Bumped"]},"type_i":{"type":"number","example":1},"created_at":{"type":"string"}}}}},"required":["id","paging_token","account","type","type_i","created_at"]}},"title":"Effect"}]},"examples":{"ListAllEffects":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/effects?cursor=&limit=10&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/effects?cursor=33676838572034-1&limit=10&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/effects?cursor=12884905985-1&limit=10&order=desc"}},"_embedded":{"records":[{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/12884905985"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905985-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905985-1"}},"id":"0000000012884905985-0000000001","paging_token":"12884905985-1","account":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB","type":"account_created","type_i":0,"created_at":"2015-09-30T17:15:54Z","starting_balance":"20.0000000"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/12884905985"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905985-2"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905985-2"}},"id":"0000000012884905985-0000000002","paging_token":"12884905985-2","account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"account_debited","type_i":3,"created_at":"2015-09-30T17:15:54Z","asset_type":"native","amount":"20.0000000"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/12884905985"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905985-3"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905985-3"}},"id":"0000000012884905985-0000000003","paging_token":"12884905985-3","account":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB","type":"signer_created","type_i":10,"created_at":"2015-09-30T17:15:54Z","weight":1,"public_key":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB","key":""},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/12884905986"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905986-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905986-1"}},"id":"0000000012884905986-0000000001","paging_token":"12884905986-1","account":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB","type":"account_credited","type_i":2,"created_at":"2015-09-30T17:15:54Z","asset_type":"native","amount":"99999999959.9999700"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/12884905986"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905986-2"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905986-2"}},"id":"0000000012884905986-0000000002","paging_token":"12884905986-2","account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"account_debited","type_i":3,"created_at":"2015-09-30T17:15:54Z","asset_type":"native","amount":"99999999959.9999700"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/12884905987"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905987-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905987-1"}},"id":"0000000012884905987-0000000001","paging_token":"12884905987-1","account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"signer_removed","type_i":11,"created_at":"2015-09-30T17:15:54Z","weight":0,"public_key":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","key":""},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/33676838572033"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=33676838572033-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=33676838572033-1"}},"id":"0000033676838572033-0000000001","paging_token":"33676838572033-1","account":"GAP2KHWUMOHY7IO37UJY7SEBIITJIDZS5DRIIQRPEUT4VUKHZQGIRWS4","type":"account_created","type_i":0,"created_at":"2015-10-01T04:15:01Z","starting_balance":"20.0000000"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/33676838572033"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=33676838572033-2"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=33676838572033-2"}},"id":"0000033676838572033-0000000002","paging_token":"33676838572033-2","account":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB","type":"account_debited","type_i":3,"created_at":"2015-10-01T04:15:01Z","asset_type":"native","amount":"20.0000000"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/33676838572033"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=33676838572033-3"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=33676838572033-3"}},"id":"0000033676838572033-0000000003","paging_token":"33676838572033-3","account":"GAP2KHWUMOHY7IO37UJY7SEBIITJIDZS5DRIIQRPEUT4VUKHZQGIRWS4","type":"signer_created","type_i":10,"created_at":"2015-10-01T04:15:01Z","weight":1,"public_key":"GAP2KHWUMOHY7IO37UJY7SEBIITJIDZS5DRIIQRPEUT4VUKHZQGIRWS4","key":""},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/33676838572034"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=33676838572034-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=33676838572034-1"}},"id":"0000033676838572034-0000000001","paging_token":"33676838572034-1","account":"GCZTBYH66ISTZKUPVJWTMHWBH4S4JIJ7WNLQJXCTQJKWY3FIT34BWZCJ","type":"account_created","type_i":0,"created_at":"2015-10-01T04:15:01Z","starting_balance":"20.0000000"}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-effects.api.mdx b/docs/data/apis/horizon/api-reference/list-all-effects.api.mdx
deleted file mode 100644
index b56bdeabf..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-effects.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: list-all-effects
-title: "List All Effects"
-description: "This endpoint lists all effects and can be used in streaming mode. Streaming mode allows you to listen for new effects as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known effect unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream effects created since your request time."
-sidebar_label: "List All Effects"
-hide_title: true
-hide_table_of_contents: true
-api: eJztW+tSGzkWfhVV/5hJpmxjY2MHV03tgiHBhgDBJgwkFJFbx24FtdQjqXFYylX7Gvt6+yRbR91tty8hDjPOZGaWP5R1OTd9Okfq/vrBs3RovOY7b38wAN8a77rgMTC+5pHlSnpNrxdwQ0CySHFpieDGGkKFIJBMIFQy4lNJ+kBiA4xwSYzVQEMuhyRUDEqkO/MbZ6uRIfcqJlY5iSDJQGkiYTQVa4gN4J5QDYQyBgzH2gBI14IQVBMBbAi6RNoD4lMhlmkukAOl+b+UJCMuBDGWakuodWKAasHBWHIr1UimakksBRhDKPFjbZQm3BADtoCiRwH3A+JTA4TbvMCBViGxAbXppBLZvcdZFs1AVamsOypiQC+kGhWc9xi2xOKJ274GaoERw6UPOEgTDb/GaKjlIZS8gqci0BQXp828pnfEjd0RIlu+ghdRTUOwoHFZHzxJQ/CaXmKDV/A4rumvMeh7r+ChaK6Bec0BFQbml36HyDjsg068cwAw6AAlJgKfD7hPhPKdLRghSnwlBPjutxoQDSZS0kCCEW5IFLt1SgMGJKJDLoc3Vt2CTMOjBoQSDb7SDH01fgAh9ZoPnr2P0A8uLQwBHYFPNIwEeM16vVyvVxq1xovtre1KeWs8LkzcVprB13vNwPChpJkfaKoTNIVBYqEhJlCxYIRGEVBdIidOhiFc+iJmQD5Q438gz6jxQTIuh8+J0uQDqvtAnuG/tNmh2OJGo3oYhyAt4Ub+99//sSn8LGEwoLFI4u/ELg2PsZrLIUZHxiFua2p8L3HQu84HRvCQ268MTC8AEtJPPIzDDBhulZNQaLCxlsBKBMc5+Q7gmsohJGteQeM3y2VSJFSSOIpApwMdwLghAdXMVyzZzNnmxdQQgR4oHVLcFRqoUdI8ErRsAYEtxK5SXhVXlfJ4fF3wPhVNHEVKW1OcZBevaXUMGLAU4Shps1zGf7Mx68a+Dwb3pa+kBWlxCI0iwZN9s/HR4LiHnEVUiJOB27upbar/EXxcrEjj3rc80XcjuLw1OR8+M86AGHx5VKBhsAxILurWIUbeeuOCZyGMBIY2N7qvlAAqvfE4D6J3idDrgme5FZCTIeGT/c5MijTcfVcmjXFY1nTklhr37xcwAWEfsFp+2ZV03+YGUq0ppgFuIVwBV6vib1KvvqvwFjyDWxPYCh58ayD6wOD7MgtHcbZMWTaOM2d8rqI/Nnpm3LjgUd9XsbTLpkTUWtCYS1+92ylelYvb1w9bW+OcMMqYxhyLnrrJny+HO4ke0kqOWV5h0nIGobqbaWlpYHx20B7051p6gQYTKMEMOY/YnMwDFQLZUyHlcknvS0GHy2a15UAkZ489MJan55DpuC4fStA5F9KGqQdpw3RKT8fGCi4hN2vaNp04bVs2dye2AZbkueY9oPmOk8Fgxrrk91RH8jsvnzLwCt4etTQ3zf2cznI/p5NagvKQ9gWQXSrcoWA6c0mfa5lZ9s8MmlmILtZ2pU3AoyWAyfcuLmK+d1l8l8te3r9sLZbLn+AUo/W4+QtDFn1YGDJVtBi+5doeH/fYej7uYIrwL6zQ4qAlC7U4aKruiP8ac8btPTlVSuRUzHV8dsYZ3KnbZR17ECnDlwq74DZgmo4We7Kt0sUbIQZpNw4jYN51mvlueC73JSf0mQPtuOCl98sbuiTXjpMzR74acObNJfVprk6z7UT1jPDr/OkluZx6Y7QztcYVsLm7a/PBc5fA2cNFdnxNqp0XWBuZ5sZGkFwOihaMlWBLJnksUFJ6uJFepv+RXHp//sHdMX6ulH9wt7if8U6UO4Q+XXC1Wm/UX1RfbDU2y9VasfIZRdnR8umKKpsvXtS2y1vbL7YWtbjLHYZ75vA3Od69ywdz5iz2FfZM5pmNnC3zp6gnODh14Ydlvs4fiJ6sgX5WQXqy8crpX767PGmc3wZNb1ZM7gjjvdo5Om21ro5rl7/sVC9fdw4Oj+qtt+391uHpUafT6r193T2+vNjtHXYuaodbB2+OLo/2Xl/1drMd1cxk3fiThJNt7/LsFvY2y5WtYnm7WC33Ko1mZau5VbvC+y0+mUJr+0k6dSNLqTPuHvGnxcTmujGxuSImNh/HxOYcJnau2rVe66zau9w66Ry0ep3W5k7tTfey3upcdA622jud3qvD9vHm/lnjaPf47eFJq3Vx3FjEBJucQTNMVFfDBDUG7E1WHajld5i8aZha+FfBR3Xd+KiuiI/q4/io/s45w7iDzJKUUVkxZ4yADwPrNSsFL4r7gvs3t3D/20xLBKwTT/U146m+7hpUf7wG1VesQfV11iA2l3A2f5eEs539bW2X8F9jvZln/UhZc2WqP16Z6itWpvqfrjJ9Y6A01gyUxrpTSuPxlNJYMaU0FlLKbwVKWqL05LY8KVGVrytR5YUS9WTT1lWiZu6G1bVAalbFelC1qGMGWHPdjwFrQdIstk43Dw8uzl+fHFw22ifVxnnnstHd3223e5323lV3a++s3X5zdrp/3qu9PT88uHrzqn120a09+cpUKRfLlV65htgqV/6AK9O3x8daytOijpXwsaRCLUhaz3FmxSK1iI8/8Pr07bGylkvUoo6VsLLkHrUg6ffNJV95lVrEyuevUk827ZvUqdr6sVX7BnWq9nidqq1ep2rzdap11du9PKjX293e1eH56dvORe/1wcXuQa1b67Q7jYvjozedX1q9N53Di8vqy3avWtu9uGp1vl2duh6nf/io3YI0uMruKXCCoKV0lkL24B1pLUh6CcEGCqM3BJu8gw28ppeFH60AfZdRzGItVls+bxmjqJeMI8dgR0rfOoQvlziIbaxhFZkvs5FEZlKvkes0UO6tR/paIuUXofegTTK7XCqXcMlNHIZU309HkUirO84cmY0c9HqnZOe0jYQihm/JuJzhJqZaS6RtCZdDMClPUkPRBc5xG5OZkVYs9oGR/v0yEQmvDt/oTzhSQA1HTp4ivpImDiGbSu9A0yGQHL2IaBCuVGXsyRyPqqg0B4lkQ2eIhkiDAWmTxJCQOfv3E4NaSgNyu7hxnuf86GvOhkD6YEcAEtUn3s7OPNXqo6M4Cn4LZISUTWsKhIEP0moq8PUxgU9+gHwxU3ASXM0l3JgYtLNowgmzipi476hjmkpDHenQFIijsuESpfuMpLukgMy7jGt5BzKzIz/bURsnM0sLyPq7I+FdfkGvn2Xbk8EdCKwoZiZVp2Zv+EpDUSoGz/9W6Hkv38tMXUqPpo4KCIzccUr887OjAqGkr9XIgHYalISMbzqJdXfv0Hwx1kz5ZsMqJcyGYbcGI62IBoRTwkBW+M71E75IVoOEVRwlAS2QETgKZxiCZI6VjIGiEhUTLo0FynBSSG+Rz8y4Rp40riGyro3z0y3rMOYMSLJj+mBIoEYuJCzkEinemmQQd3DMYoMq3Av/ZxoGCZid/3sTT38ku0INpzEYjUazzk9GFvtCDTdoUcKoaGJZxCoUQDGtH88dkdQgJ6dP/duhVrFkRMn53ZBgR/sBt+DbWFNBeIh7HkK38iplnYb0I7K6k9JB+nEYPS+Rl0galwkDC5tpX8VIQHUmYgBTfRNoKAZ9aqBA/AD8W4Kj8/47WusrDO00AENug7hf8lW4kcYh+5+5utEXqr+BvKONvf23+0cnp+3jV6WQPXfLtQsDpQEXvg9DLpEi+6MhI6UtEpu5dWfDlLuOaYA7I8APVMLLdfbhtiTHij0lERCmfEfYdTFqkp9+GgFhSIy3+KWB0gaIjqVEI7JA4ZIlaYgi714yKnC75LPEBEs//ZQkAHA0dSrEvRPt5t7cUcGZc/BmobYBQl8DsSNFDCCT3uLmkT5omSYVBr6KI5HGJ8Q0zEM8TyG/CAHWVy6MgtM+F7jjcFYOXqUZ6OPuCqmkQzCEI7hGskAiqoEVGX6XkMFLDWZdVZHloUt6qDOdiUkNU54aEIknePJsBD8KQXI7i7svKyh577Vo5MoBinvvTWKHEMFDKejQnAy6oO+4O2Nmi5xfWTeoqAaulOGwhOVMfcerSJnmmdl5QL/ErZdcXApzh73Zox2ElLteEEL9M983LniC+yAN5HTtRNQPgGyWykhjZYjdAQc96SkmPVONaTqhrtf5lAo1G0ft1v5xdx+nlAIbCnejiJSxIZU5lchhITtCkOkXGDOnhocp8fv/n9J8b5/SpHcyC5/sRiQod1xUh46H9M7zzsvuPNcFL1DGYtPDA6bscy3GY2xOPp/AmxDjBklsn/mAIg+FP/7TmqW+J3fEycdC6a0weezwNc79ab6geSQK2bdDTwzCX+hrmUeClH1HNA3SNf7QHKPkNd8h5S8AipGcPoPY8X2I8rMWPoiZeQbxar/njcf/AwOKIQM=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Effects"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/effects"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint lists all effects and can be used in streaming mode. Streaming mode allows you to listen for new effects as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known effect unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream effects created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./list-all-effects.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./list-all-effects.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./list-all-effects.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-effects.mdx b/docs/data/apis/horizon/api-reference/list-all-effects.mdx
new file mode 100644
index 000000000..f2ddbb694
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/list-all-effects.mdx
@@ -0,0 +1,12 @@
+---
+title: List All Effects
+openapi: "openapi/horizon/bundled.yml GET /effects"
+---
+
+<Tip>
+
+**Supports Streaming**
+
+This endpoint supports streaming. To read more about this, visit the [streaming section](/docs/data/apis/horizon/api-reference/structure/streaming).
+
+</Tip>
diff --git a/docs/data/apis/horizon/api-reference/list-all-ledgers.ParamsDetails.json b/docs/data/apis/horizon/api-reference/list-all-ledgers.ParamsDetails.json
deleted file mode 100644
index cffcdc7ce..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-ledgers.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-ledgers.RequestSchema.json b/docs/data/apis/horizon/api-reference/list-all-ledgers.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-ledgers.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-ledgers.StatusCodes.json b/docs/data/apis/horizon/api-reference/list-all-ledgers.StatusCodes.json
deleted file mode 100644
index 148b03a9b..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-ledgers.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transactions":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"payments":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transactions","operations","effects"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"hash":{"type":"string","title":"hash"},"pre_hash":{"type":"string","title":"hash"},"sequence":{"type":"integer","format":"int32"},"successful_transaction_count":{"type":"integer","format":"int32"},"failed_transaction_count":{"type":"integer","format":"int32"},"operation_count":{"type":"integer","format":"int32"},"tx_set_operation_count":{"type":"integer","format":"int32"},"closed_at":{"type":"string"},"total_coins":{"type":"string"},"fee_pool":{"type":"string"},"base_fee_in_stroops":{"type":"integer","format":"int32"},"base_reserve_in_stroops":{"type":"integer","format":"int32"},"max_tx_set_size":{"type":"integer","format":"int32"},"protocol_version":{"type":"integer","format":"int32"},"header_xdr":{"type":"string"}}}}},"required":["id","paging_token","hash","sequence","successful_transaction_count","failed_transaction_count","operation_count","tx_set_operation_count","closed_at","total_coins","fee_pool","base_fee_in_stroops","base_reserve_in_stroops","max_tx_set_size","protocol_version","header_xdr"]}},"title":"Ledger"},"examples":{"ListAllLedgers":{"value":{"_embedded":{"records":[{"_links":{"effects":{"href":"/ledgers/1/effects/{?cursor,limit,order}","templated":true},"operations":{"href":"/ledgers/1/operations/{?cursor,limit,order}","templated":true},"self":{"href":"/ledgers/1"},"transactions":{"href":"/ledgers/1/transactions/{?cursor,limit,order}","templated":true}},"id":"e8e10918f9c000c73119abe54cf089f59f9015cc93c49ccf00b5e8b9afb6e6b1","paging_token":"4294967296","hash":"e8e10918f9c000c73119abe54cf089f59f9015cc93c49ccf00b5e8b9afb6e6b1","sequence":1,"transaction_count":0,"successful_transaction_count":0,"failed_transaction_count":0,"operation_count":0,"tx_set_operation_count":0,"closed_at":"1970-01-01T00:00:00Z","total_coins":"100000000000.0000000","fee_pool":"0.0000000","base_fee_in_stroops":100,"base_reserve_in_stroops":100000000,"max_tx_set_size":50},{"_links":{"effects":{"href":"/ledgers/2/effects/{?cursor,limit,order}","templated":true},"operations":{"href":"/ledgers/2/operations/{?cursor,limit,order}","templated":true},"self":{"href":"/ledgers/2"},"transactions":{"href":"/ledgers/2/transactions/{?cursor,limit,order}","templated":true}},"id":"e12e5809ab8c59d8256e691cb48a024dd43960bc15902d9661cd627962b2bc71","paging_token":"8589934592","hash":"e12e5809ab8c59d8256e691cb48a024dd43960bc15902d9661cd627962b2bc71","prev_hash":"e8e10918f9c000c73119abe54cf089f59f9015cc93c49ccf00b5e8b9afb6e6b1","sequence":2,"transaction_count":0,"successful_transaction_count":0,"failed_transaction_count":0,"operation_count":0,"closed_at":"2015-07-16T23:49:00Z","total_coins":"100000000000.0000000","fee_pool":"0.0000000","base_fee_in_stroops":100,"base_reserve_in_stroops":100000000,"max_tx_set_size":100}]},"_links":{"next":{"href":"/ledgers?order=asc&limit=2&cursor=8589934592"},"prev":{"href":"/ledgers?order=desc&limit=2&cursor=4294967296"},"self":{"href":"/ledgers?order=asc&limit=2&cursor="}}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-ledgers.api.mdx b/docs/data/apis/horizon/api-reference/list-all-ledgers.api.mdx
deleted file mode 100644
index edafe7b3b..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-ledgers.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: list-all-ledgers
-title: "List All Ledgers"
-description: "This endpoint lists all ledgers and can be used in streaming mode. Streaming mode allows you to listen for new ledgers as they close. If called in streaming mode, Horizon will start at the earliest known ledger unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream ledgers since your request time."
-sidebar_label: "List All Ledgers"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWv1uGzcSf5UB/2iTYCWtFEu2BBS9tE3b4II0uLj3xzmGwiVnJdZccktyJbuGgHuNe717ksNwd6WVLTtOLtfLfRgGBGk5w/n6DYcze80CX3g2O2MvUS7QeXaeMIleOFUGZQ2bsdOl8oBGllaZAFr54IFrDbomAG4kCG4gQ6g8SlAGfHDIC2UWUFiJfXiz952o7drDla0g2MgRDeTWgcH1jq2HsMQrENp67MOLHATX+hD/BH60Tv1mDayV1uADdwF4IHJA7rRCH+DC2LVpmENlNHoPHETlvHWgPHgMCbFeL5VYguAeQYUuw9zZAsKSh4aoD99cEVUgMWirhteK6wpJL2PXSdSRjFNLvFXOKyOQHjpw+GtFAgZVYJ8lzJboOJn+hWQz9lL58Ezr1jkJK7njBQb6Mju7ZoYXyGas3pslTJHHfq3QXbGEEWvlULJZzrXHm459BqYqMnS1VtG9ngTn4EsUKlcCtBVRFrIMB2G1RhG/2xwc+tIaj3UEKA9lFf3TGAqh5AtlFvNgL9A0ZrE5cHAorJOkqxdLLDibXbNwVZIeygRcICmCl7woNbLZZJJOJsPjo+OT6Xg6TMebTbJV2zqJH661RK8Whrd6kKiR0c79tYQe/NJWWgIvS+SuDz9FHh6UEbqSCO+4F+/gEfcCjVRm8Risg3e03Tt4RB/NzzF6A8GIu0VVoAmgvPn7X/8WmrALIDHnla7tH9keNI8PTpkFWcdUBYGWe8FqBdl51zBaFSp8oGFOlwgFv1RFVbSBEb1cm8JhqJxB2QdaF/nHwHbcLLD2+ZCEH6Up9IAbqMoSXbMwBpjysOROCitrELegJeCX6HLrCk6ocMi9Nf4eo7UORHnLdsP0oXE1TDeb84Rd9nxVltYF39tmFTYLrkIyWBPhxGmUpvSxb7M3lRDoCZfCmoAm0BJellrVuBn84mnd9W2JbPYLCnJR6QjxQdW7zLHIUEpy0vuWNp7pLOTOcXK0Clj4B+yllbl4wDqPOn//qqXD/FCoRr+GGJPmgm0SFrAoNTmvszqzViM3bLPphulZzfQ8YUEFjV0ejhvPYyp6gAK/q2jb/P25CVbyK0LR5yYW5jmKz0yqG4siAG4E3Z6jd1qcbxKm5CEx2x2UrJ2xOxvvW723bpOwJffL+9bH58Tf4fyhaz1VIEbgwXy5ta4y4ekoLq9zXl7peccic2GrOv09gEXOlUb50eRby38QVbicewzzjyOOVaic83DboMTaBq7nwqo90O+e54jz0lp98GHGPc5phTJzH5y1pX+gUJHSoUe3+gjqgl/OG5t49dtDvV86G6ywer5C55U1DyRbIpfo5pfSHbAB/e0jTkl2AyNN6Hei9T2ReE+U3Y6gO6Oj6/l9P3e8etiHd/vntu0P2HXPZlTcbXFbXwZi7qyLmejxGzeF2TWLJfetomJbNpx1K4BOFq7zLBs0d5XBcNA8HFx/Xd8zkljVJbFo3rC9hEuF061D8DbH3fMPYNrWIbfYHaoIbu/ZXfHgXZt0zvAEh+l0eJJPRZqm4vjpcDjlGY6PRJ6eTPPxNJ+mw7EQ06fiaCpEnqbZGE+yKc+zCU6y4c1wnrGj0fRoOjkeTSdtbH+SXXbJfLhnlDbbpe9L4Ol96Tk9kHzTu1Nrupc42XB6nPbSYS8dnqbpLP7/5QaqZmyY7v76zWcXbDPW/flg8hym6T3JcbvBgRQ4TukS9SBYjD45LEafFhajh8Bi9E/CYjjC8Uk65dmJGE/lyWg8wcl0KLKjE56OjqQ8ejqdpJkYjqfpSE4nk6GQk9HxdDLKRpk4PgCLk/HJdPr0aDwddWDxCXZxuJr/K1A2+v1Q1oXSKB2Oe+lxbzg5HT2dHU0/PygN03RD1fAOTAYvw4EY/DpG2Vfciy9i1H01+qIOwq86sVCXtKu7yelefpO+k2Lvxsnd29eFSV2c4GVA42sUnV2zC7xis8O9g6Q9dyNQzhNWYFhaAssC46WGh2Vn+xhMbtX28ypHblmGUPrZYLCsWyS9gD4YDH0fUGvu+tYt2KH2zWm9Dl5hWFtHl6G7OOZVqBw+hOf37UowLddzaizlNlZyTU3SNHNI+7YupODqR7BURcHd1W4VlM6ulIydQ/jx9PQ1PHv9gro3kgdOrSFqyb2p5Wp37cOLAMosMLafjQSHvWi42CauKUtnZSVQQnZ1iEXdxKTadNuQQu4VNUAtCGt8VWBLylfo+AKh08sBh5oHtYrN3djf3DWtetYpNAFlLYjDkuBiQp3M6754drUV6FvrkBppykfNO3pkTskFQoZhjWho+1rbfcrXztIV2YNWFwhr6osHn4BEgSY4rtVvKAEvxZKacz6JHLj3SDr7ihrQlcdtAy5Y8FUW+3SdsyCB2DckF3ERkxBkXJOyCbU5m4Y2rqilUMvRpY595C1l/1Zk/a9HwlnXoeePWnhKXKGm3O+7uBw0Yg+EddgzVuLj/6noeWvemna7ZtLE4+GKElaKg/j5Ty8T4JA5u/bo4g7WYNvc39r6zXd/9O+1tbTCD4K12g+8vPBkaQsOKZzqMY+lK9elClfEP45wytqgCawx9suLAo2Mox8yFDe0MSjjA3JJRAW/oKGRVA5FiD6k0ZaPeka3LiolEWrEZOhhadfRJLJQhqZlDtoQj+HY2oa2iC30Rw7zOpij/t9tNf0SvtF2sbPBer3eV367spdpuxjwnsF1z1emR6fQEnvN+fE4du29JZhwcbFwtjISrLmJhjp2nFiqgCJUjmtQBWEeYyuy9pDyUPBfaHRWHx2QVUX5uA/f02TO1L0E+plntqJufxSRDNjstw0NK5FKlQTEEsUF0Oqu/nGG8AOZdmeAhQrLKusLWwwaO7SfraqDTNtsUHBlBt89//Pzlz+9fvHqh34hH0d3fYO5dUiOz3ChDM0jvvSwti7QFEmFWMU1A0JKAyoKgWJp6yFIlI9gCa+s/JhEANKKOB2JNprBkydrBEnTx0BDW+s8gquMISFaQ5HL6jTEabhpJNcEl26W2MbSkyd1AsA4E+RaX0XWkXa+4lrJqOD81tmGFPoOIawteKSxZSDwGIHONElForBVqRv7FJSGVUH1FDchBlhmoxm14pnShDii6oRXfy/0CV0FN3yBHhQF19okUHKHsidp+NuGl833VbVlUEVMerRnQ0lJjVKezcEgSg+P1vil1tBBlopDag5v2be8jMcBsXvLtrajEImXJ1f4n/I36FZKYKcY63o2LurZPB5lKra3aKTERSyZm7FeK3Y3oL8n6EXns+RGsbdf2mHBVXyKWts/dJ9tEqaVQOOxs9ezkoslwqhPdwMlKXZzhW77pFc/2e3YpBMen0adGqZ+8PLFt89fvXlOJP1lKHTssJfWh4KbzpbUwoJnWsNu3L1XNVzvpmz/fyvh930roenYBrwMg1JzFYcR0ffXzY3mjOndGyRL6wP9dH1NCflnpzcb+rmeRNM9RyrPM33XLLrr6H//WwoHda9vgNv3Lpo7H4tXrg9R7j/mZYR7rNC+hvGRRvgvevHgHiO1r2TsjHROX5wiK7HZ2fl2StLpMDwTAssu1a13C/Y6DD88P2WbzT8Ap74wZQ==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Ledgers"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/ledgers"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint lists all ledgers and can be used in streaming mode. Streaming mode allows you to listen for new ledgers as they close. If called in streaming mode, Horizon will start at the earliest known ledger unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream ledgers since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./list-all-ledgers.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./list-all-ledgers.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./list-all-ledgers.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-ledgers.mdx b/docs/data/apis/horizon/api-reference/list-all-ledgers.mdx
new file mode 100644
index 000000000..80e13ad76
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/list-all-ledgers.mdx
@@ -0,0 +1,12 @@
+---
+title: List All Ledgers
+openapi: "openapi/horizon/bundled.yml GET /ledgers"
+---
+
+<Tip>
+
+**Supports Streaming**
+
+This endpoint supports streaming. To read more about this, visit the [streaming section](/docs/data/apis/horizon/api-reference/structure/streaming).
+
+</Tip>
diff --git a/docs/data/apis/horizon/api-reference/list-all-operations.ParamsDetails.json b/docs/data/apis/horizon/api-reference/list-all-operations.ParamsDetails.json
deleted file mode 100644
index 42859558a..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-operations.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}},{"name":"join","in":"query","required":false,"description":"Set to transactions to include the transactions which created each of the operations in the response."}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-operations.RequestSchema.json b/docs/data/apis/horizon/api-reference/list-all-operations.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-operations.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-operations.StatusCodes.json b/docs/data/apis/horizon/api-reference/list-all-operations.StatusCodes.json
deleted file mode 100644
index d8d1139ec..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-operations.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_links":{"type":"object","properties":{"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"type_i":{"type":"number","example":0},"type":{"type":"string","example":"create_account"}},"title":"Operation"}]},"examples":{"ListAllOperations":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations?cursor=&limit=3&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/operations?cursor=12884905987&limit=3&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/operations?cursor=12884905985&limit=3&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/12884905985"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/12884905985/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905985"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905985"}},"id":"12884905985","paging_token":"12884905985","transaction_successful":true,"source_account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"create_account","type_i":0,"created_at":"2015-09-30T17:15:54Z","transaction_hash":"3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889","starting_balance":"20.0000000","funder":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","account":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/12884905986"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/12884905986/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905986"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905986"}},"id":"12884905986","paging_token":"12884905986","transaction_successful":true,"source_account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"payment","type_i":1,"created_at":"2015-09-30T17:15:54Z","transaction_hash":"3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889","asset_type":"native","from":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","to":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB","amount":"99999999959.9999700"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/12884905987"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/12884905987/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905987"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905987"}},"id":"12884905987","paging_token":"12884905987","transaction_successful":true,"source_account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"set_options","type_i":5,"created_at":"2015-09-30T17:15:54Z","transaction_hash":"3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889","master_key_weight":0}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-operations.api.mdx b/docs/data/apis/horizon/api-reference/list-all-operations.api.mdx
deleted file mode 100644
index d3a4ce44e..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-operations.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: list-all-operations
-title: "List All Operations"
-description: "This endpoint lists all Successful operations and can be used in streaming mode. Streaming mode allows you to listen for new operations as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known operation unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream operations created since your request time."
-sidebar_label: "List All Operations"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWntz2zYS/yo7/KNNMnralmRrptNzFDfxo3Zaq8nl4XEgYCkiBgEWAC27Hs3c17ivd5/kZkFSpmzVzbNJe6d/OCKBxe5vHwB29yrybOqi4avoKEPLvDTaRSeNSKDjVmb0PxpG40Q6QC0yI7UHJZ13wJSC45xzdC7OFZjFdGBaAGcaJgi5QwFSg/MWWSr1FFIjsAXHS/+Jlpk5uDQ5eBPoo4bYWNA4W6LswCd4CcwiMCFQ0HCfIBx7VIpZUCimaFuwGwNnSq1avAFPjJW/GQ0zqRQ4z6wH5gMZZFZJdB7OtJnp65Uh1wqdAwY8t85YkA4c+gZRnyWSJ8CZQ5C+TjO2JgWfMF9OasHDS5rliRNaraR1zlSOJIg2s0bAgMArmK4Lzy0yjwKc1BxpnAWLv+bErpcptqJGtBi9K6JhdCCd31aqpthGlDHLUvRoSedXkWYpRsOo4CRqRJK0/WuO9jJqRERdWhTRMGbK4U2j2AadpxO0hYzBNByJwcBlyGUsOSjDC/ykJuyMUsjDfxODRZcZ7bCwF+kgy4PCStgQMjaVenrqzRnqEiQTAwOL3FhB4jqeYMqi4VXkLzOSQ2qPUyRB8IKlmcJo2O93+v3uYGOwudXb6nZ683ljIbaxAt9faoFOTjWr5CBWA6FrYyg4dOASkysBLMuQ2RYcZYUipeYqFwhvmONv4B5zHLWQenofjIU3tNwbuEeP8nUwZ08uyOw0T1F7kE7/51//9qURehAYs1wV+AeyK+Fx3ko9JXR0npLPM8ejQsDopA6Mkqn07wnMOEFI2YVM87QyjKDlAgqLPrcaRQtoXKAfzNwyPcVC511ifq3TgSYwDXmWoS0HBgOTDhJmBTei8OrKiylMZGhjY1NGjmGROaPdHaBVCkRxC7tu513tqtupA1aq9DRmUqF4T+SO0Yc4ZoswUJlHQaseAaQmryFebxtTmE2eFJZYKcXEGIVMX+uf5jTC+CXtvzVSf6gITDvGC85qopCPLH0rg2YZ0ZDxZOFKS+LSmypQtKL5SSO6aLo8y4z1rrmI69EwSBItQgoJvdbp0OMGn8WGFTUibrRH7WkIyzIli0DVfuto3FUNPKbUURyCZQmjmbxFTt6RWWLWy2K9UyX1mavB/TvjHKr4j0clFuNVnhvM3AcX1WfRvBF5TDNFKK5Q9HxeV9yrguhJI/LSK6zR0HjhvzKWMovnXxVLcxpWvToIqiaX+TQ2gXGM3L/DwD9bBxwFfm1sfYUO5CisiK8NqFrE/ao4o1FSrFqsGidFsL/aAfCu0UvjiMPLDE9lbUZxHKnv3p1y2MrDUTUoKvanU8a5ybWP6hFgcaiO5ifzxZyA5O1j9/AqCufX5ZBQ2XGBfJR4n7lhu50U55qmR+c1+pYrrjYtY6ft683x++LI/t034YT03fo34Qj6HR3oagH9o0h31zY3N7Y6va3NwepVqhj9iVbp3VglHEsJ81NMJ0i3PVqsPFCGDfkTYdmu8bDCb96DZv2M015f39zCrbgTd1m/F3e3But9znjc29jga7i51lvvruPmxsYg7vW31tbXJ5NNMVnfYqzfGfDNzc0tYqW2MXy0aO2KWBWwyoj1HoRLCt9fK+ib22q8uXV8MH32O+TL8BHVX96MFjc+1hRz6hZJi+rc6Exu+bWfD6PH29svdzfGo5/Xxy96R3tPRuO90dr2xk/HL/qjved7T3q723vjx/u7h2s7Pw8OHh4+2z8ajZ4fDqIqqtwMHddBqdMov4nTEFbXOt1es7PVXO+Mu4Nhtzfsbby8wXDCXBINo4+2p0YUEhOE0oQpuiyF9Vud4kfBPtd0I/4oAOooHjwdjV4ebrz45/b6ix/3nuwf9EfPdndG+08P9vZG42c/Hh++eP5wvL/3fGO/9+SngxcHj358OX4YDlaf3rf7f1/f7v9Jvt3/vL7dX+Xb/bt8u/8lfDtjl5RPqDl190s6NXMO/Wl11GFeniO5sjXpR0prPsaHGxFLS8S3ql9vq0WPQafzmVx88Pd18cGf5OKDz+vig1UuPrjLxQdfwsXJo0xWJc0rN+99STdPmfNoT8/w8nSGcpp4usWczMsfXUE8alfcN15dRWd4GQ1XZ8sa1W2E4KOcWoo+MaSSKYaLIfPEc80O6eiA9ryqGuRWvZtFRKuSxONiHByinxl7FkLBaopx7nOL70Lzh2ok6IrqCWUwYxNueOWlrUwZEwBoXTG70+q0uiRfnqbMXl6PgsyacylCfQKejMdPYfvpLiU1BfOsyk1Wdady1RbsepB6iqFApgVYbAbgQt2qmJlZI3KOAiaXq0gUpRK6dS/S3sicpDKLAW60y1OsprJztGyKUEtggkUVtoCqMlZLjTeNlagp4RoYsZhZdKh9mW4NtbrJ5YKhkbFI6XrpguQ1OSZWiinCBP0MUdPyhbTLM59aQ5kGB0qeIcyoHOddAwRy1N4yJX+j1O8FT6gE4BqBQtjLQDqXow0cLdL83oDLJ6EaUIvSDQgJalJR6f5QHm0bVEwpi2h4jrri42aK+npm65Zl/a9bwqu6Qk/uVe4p8BwVBQe3FP1LttvcWGxqI/D+/5T1vNavdbVcWf1mYadCAeeSAf/l54MGMJhYM3NowwpGY1X3WGB9/Gjf/SHWwnDX9sYo13bizBHSBiySORWlZUPpqAvpL4l+qBVnBaANmGGoyqUpahHKzQQU07QwSO08MkGTUnZGhWohLXIfdEgVdRfkDGqd5lIgFB4zQQeJmQVIRCo1VfAtVCYezLHChpYIhbp7FuPCmIP8jxaSfgsPlZleYzCbzZaFX4xsTpSZtllT46zpct2kXSjBZrl/3A+1QWfITRg/m1qTawFG3/SGwnYsT6RH7nPLFMiUfB7ToHlTFhJT9pbK9cXWAZM8ze634AfqBtBFlpRes4nJqaYYWCQAy/UWpmEETpjDBvAE+RnQ6Lr8oVL5mKC9BmAqfZJPWtyk7RKH6lmJ2p4oM2mnTOr2o51nOwdHT3cPH7dScT+o6yHGxiIpfoJTqanq+a2DmbGeatXSh22+bEqgMCADE8gTU5RaA3/klnBoxIcEAhCGhxpswGgIDx7MEAR1PHhqKzHWIdhca2KiAopUVoQhRg0VWjBF7lKPEgtbevCgCAAYOg+YUpeBdJh7es6UFEHA01t7G5LpWwQ/M+CQmiM8OY/maHUZVARyk2eqxCelMCxTOlIx7YOBTUyAUUk2kYo8jmbVzKu1ZPrkXSnTbIoOJBnXTDcgYxZFU1DPSWVeJl4WlU6jaQh6tGY5k4IahTwTg6b7ANyb4bdKQc2zZOiaYfA6GrEsbAdE7nW0wI5MhA6taFN3FB+jPZchMVQpeemCRIOaJg5bGQ0r6qiMh2xzWT6u2K4b9A/kekW+vHHjsLd8tMOUyfAVlTL/qH+bNyIlOWqHtbW2M8YThLUWZa+kINuNZchgFV+axZfrFctwwsLXIFNJ1LUPdkc7h8c7NKWV+FSFm0pmnE+Zri1J6X3YVgqW+mqWDg5X19Xl/7dO/UVap8qLn8cL384Uk6GSFOzmqrwQvYrMUotcYpynt1dXFM9/sWo+p9dFxwRdk4R0bKJ+r2eibiRfvpVqpfjFHXLRHFbeGqNwY3sf4f4yHVN3oFD1in0gCH+j7qg7QKr6xj4QpM/UCHUHw7f6tpY5/0NGP2u7052cl01a1/ye0B8rCepo+IqK0gmyUM1ZZIO2Ocesrp9bnU9L2aDHO+NoPv8vvMc8sg==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Operations"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/operations"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint lists all Successful operations and can be used in streaming mode. Streaming mode allows you to listen for new operations as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known operation unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream operations created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./list-all-operations.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./list-all-operations.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./list-all-operations.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-operations.mdx b/docs/data/apis/horizon/api-reference/list-all-operations.mdx
new file mode 100644
index 000000000..079aefb0a
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/list-all-operations.mdx
@@ -0,0 +1,12 @@
+---
+title: List All Operations
+openapi: "openapi/horizon/bundled.yml GET /operations"
+---
+
+<Tip>
+
+**Supports Streaming**
+
+This endpoint supports streaming. To read more about this, visit the [streaming section](/docs/data/apis/horizon/api-reference/structure/streaming).
+
+</Tip>
diff --git a/docs/data/apis/horizon/api-reference/list-all-payments.ParamsDetails.json b/docs/data/apis/horizon/api-reference/list-all-payments.ParamsDetails.json
deleted file mode 100644
index 42859558a..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-payments.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}},{"name":"join","in":"query","required":false,"description":"Set to transactions to include the transactions which created each of the operations in the response."}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-payments.RequestSchema.json b/docs/data/apis/horizon/api-reference/list-all-payments.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-payments.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-payments.StatusCodes.json b/docs/data/apis/horizon/api-reference/list-all-payments.StatusCodes.json
deleted file mode 100644
index 1bc8c571d..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-payments.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"oneOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"create_account"},"type_i":{"type":"number","example":0},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"starting_balance":{"type":"string"},"funder":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","starting_balance","funder","account"],"title":"CreateAccount"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"payment"},"type_i":{"type":"string"},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string"},"asset_code":{"enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","asset_type","from","to","amount"]}}}}},"title":"Payment"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"path_payment_strict_receive"},"type_i":{"type":"number","example":2},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"},"path":{"type":"array","items":{"type":"object","properties":{"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}}}},"source_amount":{"type":"string"},"destination_min":{"type":"string"},"source_asset_type":{"type":"string"},"source_asset_code":{"type":"string"},"source_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","from","to","amount","path","source_amount","destination_min"],"title":"PathPaymentStrictReceive"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"path_payment_strict_send"},"type_i":{"type":"number","example":13},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"},"path":{"type":"array","items":{"type":"object","properties":{"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}}}},"source_amount":{"type":"string"},"source_max":{"type":"string"},"source_asset_type":{"type":"string"},"source_asset_code":{"type":"string"},"source_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","from","to","amount","path","source_amount","source_asset_type"],"title":"PathPaymentStrictSend"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"account_merge"},"type_i":{"type":"number","example":8},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"into":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","account","into"],"title":"AccountMerge"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"invoke_host_function"},"type_i":{"type":"number","example":0},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"function":{"type":"string"},"parameters":{"type":"array","items":{"type":"object","properties":{"value":{"type":"string"},"type":{"type":"string"}},"required":["value","type"],"title":"host_function_parameter"}},"address":{"type":"string"},"salt":{"type":"string"},"asset_balance_changes":{"type":"array","items":{"type":"object","properties":{"asset_type":{"type":"string"},"asset_code":{"enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","enum":["transfer","mint","clawback","burn"]},"from":{"type":"string"},"to":{"type":"string"},"amount":{"type":"string"}},"required":["asset_type","type","amount"],"title":"asset_balance_change"}}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","function"],"title":"InvokeHostFunction"}]}]},"examples":{"ListAllPayments":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/payments?cursor=&limit=3&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/payments?cursor=33676838572033&limit=3&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/payments?cursor=12884905985&limit=3&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/12884905985"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/12884905985/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905985"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905985"}},"id":"12884905985","paging_token":"12884905985","transaction_successful":true,"source_account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"create_account","type_i":0,"created_at":"2015-09-30T17:15:54Z","transaction_hash":"3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889","starting_balance":"20.0000000","funder":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","account":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/12884905986"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/12884905986/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905986"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905986"}},"id":"12884905986","paging_token":"12884905986","transaction_successful":true,"source_account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"payment","type_i":1,"created_at":"2015-09-30T17:15:54Z","transaction_hash":"3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889","asset_type":"native","from":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","to":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB","amount":"99999999959.9999700"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/33676838572033"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/2db4b22ca018119c5027a80578813ffcf582cda4aa9e31cd92b43cf1bda4fc5a"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/33676838572033/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=33676838572033"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=33676838572033"}},"id":"33676838572033","paging_token":"33676838572033","transaction_successful":true,"source_account":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB","type":"create_account","type_i":0,"created_at":"2015-10-01T04:15:01Z","transaction_hash":"2db4b22ca018119c5027a80578813ffcf582cda4aa9e31cd92b43cf1bda4fc5a","starting_balance":"20.0000000","funder":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB","account":"GAP2KHWUMOHY7IO37UJY7SEBIITJIDZS5DRIIQRPEUT4VUKHZQGIRWS4"}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-payments.api.mdx b/docs/data/apis/horizon/api-reference/list-all-payments.api.mdx
deleted file mode 100644
index 85561d328..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-payments.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: list-all-payments
-title: "List All Payments"
-description: "This endpoint lists all Successful payment-related operations and can be used in streaming mode. Streaming mode allows you to listen for new payments as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known payment unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream payments created since your request time. Operations that can be returned by this endpoint include: create_account, payment, path_payment_strict_recieve, path_payment_strict_send, and account_merge ."
-sidebar_label: "List All Payments"
-hide_title: true
-hide_table_of_contents: true
-api: eJztXOty27YSfhUMf7RJR/ebJc10ehzHjWU7jhsryUlSjwoBSwk1CbAAaMX1aOa8xnm98yRnFiQlSqYT33Jpq/xRTOKy++0udkES36Vn6cR4/ffeMb0IQVrjnZY8DoZpEVmhpNf3hlNhCEgeKSEtCYSxhtAgICcxY2CMHwckSjqXNQTUAicqAk2xuyFUcsKoJGMgsQFOhCTGaqChkBMSKg4VcrLyN46tZoZcqJhY5eYDSXyliYRZNpMh1BA7hQtCNRDKOXBsbKdATiwEAdUkAD4BXSEDnzAaBEVTl8ie0uJPJclMBAExlmpLqHXDANWBAGPJmVQzmc1LYhmAMYQSFmujNBGGGLAlHHs2FWxKGDVAhM2P6GsVEjulNu1UIU8usJdFOXCudKxzGsSAakg1Kzn9EbhE5KXiTIPD2AjJAFtpouGPGEW1IoQKebEEP5k0QV+DjbUETsYXxK6YVEgWxBz66dAjypiKpS1lc+J/7HSU/jUyVgtmRxqYgHMovmlA8pKzfTrYKAQ9AVLxSt7COQbc63uHwtjtIFi4X8mLqKYhWNDol5eepCF4fS/ByCt5An3yjxj0hVfyUHOhgXt9nwYG1l13m8g4HINOgHDaGgSYEhMBE75gJFDMCYMWpISpIADm/lY+0WAiJQ0kXiwMiWLnSKlBgUR0IuRkZNUZyNR8yieUaGBKc1TWsCmE1OtfevYiQj2EtDABVAQ+0DAKwOt3OrVOp77V2ur22r16rT2flxZqK83h9lpzMGIiaaYHiuoGWrppIqEhZqrigBMaRUA1+k7iOKlLkN+oYb+RR9QwkFzIyWOiNPkNp/uNPMKf9LILM+dVVE9iFynCyP/95782DQ9LOPg0DhL83bCF8KD/yAmiI+MQ1yVqmJco6J3mgQlEKOwtgRlOgYT0gwjjMHMMZ+UEiixAKgTbufFd7GgqJ5DYvI7CN2o1UiZUkjiKQKcNnYMJQ6ZUc6Z4stpkqwsuXhFoX+mQYtBqoEZJ8xHQMgMCv4JdvXZTv6rX8oClJh35VATAb4ncCVi3vupkgcrcIxkrv9wLiVGDsl51JtcbI8lNUajFWKkAqFzaH/uUXPsV6/+uhLyrClQaytL1cakKxsjKvXQ5T1dboGy6CKUVdfFKtlBUvPlpyftQNnEUKW1NeZFvvL7TxFssKah0o1bDnzU5k7TqlTympAVpsQmNokAkC1X1d4PtLnPg0SB44bvFMoVRjX8HhtERaRTWimS+USDkmcnBfU07A4H/6VZTDX5R5Do3ty5E5Zk3L3kWwsjVBQWGns/zhnufDHpa8qywAeTGkPDBfmMiRRrOvymR5tgsu3ToTI0hoyT83b0jF7jfmGTg+8DsDVD9olIZXGOAf2tiRRoYcPi2xFpr5Lx/1eOWVs4hm9PmdF7yBC8SN5tJcKd+rpq82nrVzUdmsfsq0qzkGRVrtqjliyaPqLWgMeU8e79dflcr904v2+15TizKucZUhFO7zgVlWlZseKubh6zPSOR6JTVXvldtXko78hEtkHJN6Sk108JGbqOF4I1pgCVWYSM/llhM3xeKh4F0za0E99Yc4FpzX7Ftap0F4CuQFgBYANcCnKV6uUDYccNtLyz7yUwC4RhwT/7pQE6L71xDqjXFck5YCG+wEmyy1iZrbbLWJmvdMWulz60K09VShYdIUdQYsKNiiRa38dEB3s6efuAznHNIVnQu7IgG0ZTKOGxdvVRvOJMl4whj4gdIdfjQ4/5GUPdPuWGxO3zdLJqzaAqVU3Yh7ul8dUt2vPC1TVLbJLVNUtsktc+W1Apf1wCmkpvtyxpfIOmV7p3lsmx5zbT/lCToxsnjf8st1F/fSC7NZmF2PUwcjBXJa7FRKIoDOxvl49XaSqtrNVxp9TCKfs16p6DESV1vHfyrUJ/myyA7TUuhE7c2vVwsTZu6aFMXbeqiTV30Besi/FLlhkVRvbmpijZV0V/HSDesitIWIf2wKYg+X0F0FcaPlUQnyaq0qYc29dCmHtrUQ5+pHlr5NveGRVD3oWqgB9JSyHsXEV/3JcKip9Mk58vp+/bnqXE2uWCTCza5YJMLPlMuEPJcncFoqowd+bFMoPmyH3Etpi3ezC1Phdx1S+dOaBTLV7yvWXOepH/aOudpK6CNFpK6/pkRCrdDNCiGK9klpB9njdgUTyDcQ++/4qcHn9p4O4/ynSOGwuVPFtDZmLIzr+SNYy2dSMVPKa558nCLDw1WXv2nP9lb/5w6BWb05l95z5oFWU7OgYv9PWXsz4vIP50jfmmMOy9aP6mVD6hl8ZGVF8kS702tjUy/Wp0mR2HKFoyVYCsmOaVXUXpSzY62/ZSc8frxO3ek5sfmd+7M0o94Aih3AuAeAzebna1Ot9ltbzVqzWbxNNlX/feYpt7odlu9WrvXba/N4Y4xof1XvpBcfAP5/p5ALg+mVHMyFFRYtxgzfyam2mx2e9Dza36ddtp+vbfV7DDK/HarxRrQbbSb9SZ0W60tv93pNZrN8bjLx80epZ3aFut2u721kureqlWzwdaKolsMnI7w09JA310143p1c+fx6TXDpyWGl7+4XlGs3byumkjOGa3XD96z7e13g9Zw52Vz+Lb9Yn9vZ7i/09hu/XLytrOz/2Z/rz3Y3h8+OxgcNXZfbh0+OXp98GJn583RVrbEXPnAe1ka1FbTv9eo1dvlWq/crA3rW/16u99uvStajPrevf2p6Mtvr1Gr1JJ/y++a7wVAHsXD452dd0ett//ebr59vr93cNjZeT3Y3Tk4Ptzf3xm+fn5y9PbNk+HB/pvWQXvvl8O3h0+fvxs+cfu3h4/tzt83tjtfKLY7nze2O0Wx3flYbHe+Rmxnn8Eug7r+NYM6X7AuC9GkmLuXtuo+MbwsD71e9q/dq+DPVq32oCG+Wqk8YJQ3+Lg1bjQYrdW79XqPtWuNLdqttbe63XrT95nf7jYYpy1Ke9CsM95rjFtN5tfHnLZ81qYPEuWr2n3WQL8K5EPH+voMWbivXb8S8Vfu3zro7+zGd0ro9Vq5Vh/WWhj7tfo1sX9v97pVQr97HOdQPG4c7L159fzF3tutwYvm1qv9t1snu08Gg+H+4Om7k/bTl4PBLy+Pd18NW69fHey9++XZ4OWbkxZukNJ/uEuyIA26tqvhz+DC6xefAi9lWyY0Kp4VD8FOFbrLBBYvD/veYkuBeIA+z7gwYh3czF29IuqDYdKOHIGdKX3mFqziEf3YxhpuMubPWUsis1FP8VG2n+yv0w1mSoSA6oM2Se9apVapu0duYUj1xbIVibQ6F9yxbpC94fCYbB8P8Kg+p5ZmJ+4zlpd01goZII/JBBw5jeREQ9kB51hikp6RVjxmGQHKlSESAhB8ArkgcwBqBJKHKMKUNHEIWVd6DppOgOSO5RPHfSPOIeOhyRE+lJUWIJFGwAmiIdJgQNqURMDx4owvFgLtKA1IQiGM0zynx1gLPgEyBjsDkDh9ou1qz2Ot8DGQIYE4AzJD8htrSoQDA2k1DcSfSGjwIX2slNK0YMYlybMbJ9GCvMIqYuKx47jIJZIScbQLaKI0mEgaryWkCElJa+DcUdY4OdaJF5Y9K1c865/uCe/zBj19lIUnh3MIMI+aldSUil1lSkNZKg6P/1He86v8VWbTpVxH1GVP4ORcUMJevTwsEUrGWs0MaDeDkpCxeSywPnl6YD6JNVfMVK1SgakafmYQaUU0oDslVE4Kn5d9EPYCx3fsTFECaInMwHHNhCFI7uidECgqcWIipLFAOXYK6RkSQ3GhgVlnQ+SvMk5PZ9ZJLDiQJGLGYMhUzRwkPBQS2bI0yVzcuWOGDU7h6GceafATZ3b6P11o+j15EqjJEoPZbLaq/KJleRyoSZWWJczKJpZlzEJTKKf547FjvDEKw4Sys4lWseREyfVoSHxHs6mwwGysaUBEiDEPCdWVSulxQvo70mMlqYOM4zB6XCE/I/uWTN4Y4WU6VjEy5TgREcB0voVrKA5jaqBE2BTYGcHWef0d/84zhHYJwETYaTyuMBVWUxyy30zV6jhQ42pIhaw+3X29e/jieHD0rBLyx85cT8BXGtDwY5gIiVw+3xsyU9oiA5OwriJOScBwGRBOCGBTlRAIOfkwLMmR4ndZCAhXzDELOYz65IcfZkA4MoxZ5P9S2gDRsZQoRAYUmixZhigSmElOAwyX/Cqx8KUffkgWAHB8WjQILtzQru/onAaCOwVHV3IboOtrIHamiAF8ZWIxeCQDLdNFhQNTcRSk+IS4DIsQCyoqrXOwsXIwBoKORYARh71y7lVZcX2MrpBKOgFDBDrXTCJ3mQZe5sjwlrmX8ldVVZEVoVv0cM60Jy5quOQpn0jcr5BHM/g+CEgusoTjqKPkV2+HRi4d4HC/egvs0EWwigYdmhf+Cehz4ardzMgrezhsVFa+S2XCHdhHdiDK3CPxlBQpEzvv0D9j6NH0Pedqsbda2kFIhbsLQaD+lb83L3mBYCAN5ObajiibAmlUsCQXHH3XF64sT+6UkzvLGdPlhLq7Tqd0UFM9HOzsHp3sYpfK1IaB20NFytiQytyU+P6BbAcByXHFrZQNl0vGpA1p4Ya08EFJC9Mts4UPthoFVLh34867L9NN23svylFo4ithvHZ5iTnnlQ7mc7yccJXhVo4LQ8fBdWxleVf++iSGhconu9wFLWO6r/XcrvI2yv1luAo/gkLG0nhHEP5GvIQfASljbLwjSJ+JgvAjAl9hTFyV/JOCflaiwY9KntIjLuU9xT+0QKi9/nt8sz8F6h6jLZ5XbTMGUd4+VzgHV55XPdsdevP5/wFhNGU6
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Payments"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/payments"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint lists all Successful payment-related operations and can be used in streaming mode. Streaming mode allows you to listen for new payments as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known payment unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream payments created since your request time. Operations that can be returned by this endpoint include: create_account, payment, path_payment_strict_recieve, path_payment_strict_send, and account_merge .
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./list-all-payments.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./list-all-payments.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./list-all-payments.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-payments.mdx b/docs/data/apis/horizon/api-reference/list-all-payments.mdx
new file mode 100644
index 000000000..b982d287d
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/list-all-payments.mdx
@@ -0,0 +1,12 @@
+---
+title: List All Payments
+openapi: "openapi/horizon/bundled.yml GET /payments"
+---
+
+<Tip>
+
+**Supports Streaming**
+
+This endpoint supports streaming. To read more about this, visit the [streaming section](/docs/data/apis/horizon/api-reference/structure/streaming).
+
+</Tip>
diff --git a/docs/data/apis/horizon/api-reference/list-all-transactions.ParamsDetails.json b/docs/data/apis/horizon/api-reference/list-all-transactions.ParamsDetails.json
deleted file mode 100644
index 24ec568a4..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-transactions.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-transactions.RequestSchema.json b/docs/data/apis/horizon/api-reference/list-all-transactions.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-transactions.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-transactions.StatusCodes.json b/docs/data/apis/horizon/api-reference/list-all-transactions.StatusCodes.json
deleted file mode 100644
index 77817ef59..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-transactions.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"memo":{"type":"string"},"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"account":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"ledger":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","account","ledger","operations","effects","precedes","succeeds","transaction"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"successful":{"type":"boolean"},"hash":{"type":"string"},"ledger":{"type":"integer","format":"int32"},"created_at":{"type":"string"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"account_muxed":{"type":"string"},"account_muxed_id":{"type":"string"},"source_account_sequence":{"type":"string"},"fee_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed_id":{"type":"string"},"fee_charged":{"type":"string"},"max_fee":{"type":"string"},"operation_count":{"type":"integer","format":"int32"},"envelope_xdr":{"type":"string"},"result_xdr":{"type":"string"},"result_meta_xdr":{"type":"string"},"fee_meta_xdr":{"type":"string"},"memo_type":{"type":"string"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"},"preconditions":{"type":"object","properties":{"timebounds":{"type":"object","properties":{"min_time":{"type":"string"},"max_time":{"type":"string"}},"title":"TransactionPreconditionsTimebounds"},"ledgerbounds":{"type":"object","properties":{"min_ledger":{"type":"string"},"max_ledger":{"type":"string"}},"title":"TransactionPreconditionsLedgerbounds"},"min_account_sequence":{"type":"string"},"min_account_sequence_age":{"type":"string"},"min_account_sequence_ledger_gap":{"type":"integer","format":"uint32"},"extra_signers":{"type":"array","items":{"type":"string"}}},"title":"TransactionPreconditions"},"fee_bump_transaction":{"type":"object","properties":{"hash":{"type":"string","title":"hash"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"}},"title":"FeeBumpTransaction"},"inner_transaction":{"type":"object","properties":{"hash":{"type":"string","title":"hash"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"},"max_fee":{"type":"string"}},"title":"InnerTransaction"}},"required":["id","paging_token","successful","hash","ledger","created_at","source_account","source_account_sequence","fee_account","fee_charged","max_fee","operation_count","envelope_xdr","result_xdr","result_meta_xdr","memo_type","signatures"]}}}}},"title":"Transaction"}]},"examples":{"ListAllTransactions":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions?cursor=&limit=3&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/transactions?cursor=33736968114176&limit=3&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/transactions?cursor=12884905984&limit=3&order=desc"}},"_embedded":{"records":[{"memo":"hello world","_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/3"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=12884905984"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=12884905984"}},"id":"3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889","paging_token":"12884905984","successful":true,"hash":"3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889","ledger":3,"created_at":"2015-09-30T17:15:54Z","source_account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","source_account_sequence":"1","fee_charged":300,"max_fee":300,"operation_count":3,"envelope_xdr":"AAAAAAGUcmKO5465JxTSLQOQljwk2SfqAJmZSG6JH6wtqpwhAAABLAAAAAAAAAABAAAAAAAAAAEAAAALaGVsbG8gd29ybGQAAAAAAwAAAAAAAAAAAAAAABbxCy3mLg3hiTqX4VUEEp60pFOrJNxYM1JtxXTwXhY2AAAAAAvrwgAAAAAAAAAAAQAAAAAW8Qst5i4N4Yk6l+FVBBKetKRTqyTcWDNSbcV08F4WNgAAAAAN4Lazj4x61AAAAAAAAAAFAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABLaqcIQAAAEBKwqWy3TaOxoGnfm9eUjfTRBvPf34dvDA0Nf+B8z4zBob90UXtuCqmQqwMCyH+okOI3c05br3khkH0yP4kCwcE","result_xdr":"AAAAAAAAASwAAAAAAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAAFAAAAAAAAAAA=","result_meta_xdr":"AAAAAAAAAAMAAAACAAAAAAAAAAMAAAAAAAAAABbxCy3mLg3hiTqX4VUEEp60pFOrJNxYM1JtxXTwXhY2AAAAAAvrwgAAAAADAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAMAAAAAAAAAAAGUcmKO5465JxTSLQOQljwk2SfqAJmZSG6JH6wtqpwhDeC2s5t4PNQAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAwAAAAEAAAADAAAAAAAAAAABlHJijueOuScU0i0DkJY8JNkn6gCZmUhuiR+sLaqcIQAAAAAL68IAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAMAAAADAAAAAAAAAAAW8Qst5i4N4Yk6l+FVBBKetKRTqyTcWDNSbcV08F4WNgAAAAAL68IAAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEAAAADAAAAAAAAAAAW8Qst5i4N4Yk6l+FVBBKetKRTqyTcWDNSbcV08F4WNg3gtrObeDzUAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEAAAABAAAAAwAAAAAAAAAAAZRyYo7njrknFNItA5CWPCTZJ+oAmZlIbokfrC2qnCEAAAAAC+vCAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMAAAABAAAAAAAAAAABlHJijueOuScU0i0DkJY8JNkn6gCZmUhuiR+sLaqcIQ3gtrOnZAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEAAAADAAAAAAAAAAABlHJijueOuScU0i0DkJY8JNkn6gCZmUhuiR+sLaqcIQ3gtrOnY/7UAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"text","signatures":["SsKlst02jsaBp35vXlI300Qbz39+HbwwNDX/gfM+MwaG/dFF7bgqpkKsDAsh/qJDiN3NOW695IZB9Mj+JAsHBA=="]},{"memo":"testpool,faucet,sdf","_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/2db4b22ca018119c5027a80578813ffcf582cda4aa9e31cd92b43cf1bda4fc5a"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/7841"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/2db4b22ca018119c5027a80578813ffcf582cda4aa9e31cd92b43cf1bda4fc5a/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/2db4b22ca018119c5027a80578813ffcf582cda4aa9e31cd92b43cf1bda4fc5a/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=33676838572032"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=33676838572032"}},"id":"2db4b22ca018119c5027a80578813ffcf582cda4aa9e31cd92b43cf1bda4fc5a","paging_token":"33676838572032","successful":true,"hash":"2db4b22ca018119c5027a80578813ffcf582cda4aa9e31cd92b43cf1bda4fc5a","ledger":7841,"created_at":"2015-10-01T04:15:01Z","source_account":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB","source_account_sequence":"12884901890","fee_charged":300,"max_fee":300,"operation_count":3,"envelope_xdr":"AAAAABbxCy3mLg3hiTqX4VUEEp60pFOrJNxYM1JtxXTwXhY2AAABLAAAAAMAAAACAAAAAAAAAAEAAAATdGVzdHBvb2wsZmF1Y2V0LHNkZgAAAAADAAAAAAAAAAAAAAAAH6Ue1GOPj6Hb/ROPyIFCJpQPMujihEIvJSfK0UfMDIgAAAAAC+vCAAAAAAAAAAAAAAAAALMw4P7yJTyqj6ptNh7BPyXEoT+zVwTcU4JVbGyonvgbAAAAAAvrwgAAAAAAAAAAAAAAAABJlwu05Op/5x1uyrweYsyR6pTTos33hRNZe5IF6blnzwAAAAAL68IAAAAAAAAAAAHwXhY2AAAAQDSBB5eNEKkWIoQbZ1YQabJuE5mW/AKhrHTxw9H3m/sai90YcaZlsAe3ueO9jExjSZF289ZcR4vc0wFw1p/WyAc=","result_xdr":"AAAAAAAAASwAAAAAAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=","result_meta_xdr":"AAAAAAAAAAMAAAACAAAAAAAAHqEAAAAAAAAAAB+lHtRjj4+h2/0Tj8iBQiaUDzLo4oRCLyUnytFHzAyIAAAAAAvrwgAAAB6hAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAQAAHqEAAAAAAAAAABbxCy3mLg3hiTqX4VUEEp60pFOrJNxYM1JtxXTwXhY2DeC2s4+MeHwAAAADAAAAAgAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAB6hAAAAAAAAAACzMOD+8iU8qo+qbTYewT8lxKE/s1cE3FOCVWxsqJ74GwAAAAAL68IAAAAeoQAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEAAB6hAAAAAAAAAAAW8Qst5i4N4Yk6l+FVBBKetKRTqyTcWDNSbcV08F4WNg3gtrODoLZ8AAAAAwAAAAIAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAeoQAAAAAAAAAASZcLtOTqf+cdbsq8HmLMkeqU06LN94UTWXuSBem5Z88AAAAAC+vCAAAAHqEAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAeoQAAAAAAAAAAFvELLeYuDeGJOpfhVQQSnrSkU6sk3FgzUm3FdPBeFjYN4Lazd7T0fAAAAAMAAAACAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMAAB55AAAAAAAAAAAW8Qst5i4N4Yk6l+FVBBKetKRTqyTcWDNSbcV08F4WNg3gtrObeDuoAAAAAwAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEAAB6hAAAAAAAAAAAW8Qst5i4N4Yk6l+FVBBKetKRTqyTcWDNSbcV08F4WNg3gtrObeDp8AAAAAwAAAAIAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"text","signatures":["NIEHl40QqRYihBtnVhBpsm4TmZb8AqGsdPHD0feb+xqL3RhxpmWwB7e5472MTGNJkXbz1lxHi9zTAXDWn9bIBw=="]},{"memo":"","_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/3ce2aca2fed36da2faea31352c76c5e412348887a4c119b1e90de8d1b937396a"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/7855"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/3ce2aca2fed36da2faea31352c76c5e412348887a4c119b1e90de8d1b937396a/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/3ce2aca2fed36da2faea31352c76c5e412348887a4c119b1e90de8d1b937396a/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=33736968114176"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=33736968114176"}},"id":"3ce2aca2fed36da2faea31352c76c5e412348887a4c119b1e90de8d1b937396a","paging_token":"33736968114176","successful":true,"hash":"3ce2aca2fed36da2faea31352c76c5e412348887a4c119b1e90de8d1b937396a","ledger":7855,"created_at":"2015-10-01T04:16:11Z","source_account":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB","source_account_sequence":"12884901891","fee_charged":100,"max_fee":100,"operation_count":1,"envelope_xdr":"AAAAABbxCy3mLg3hiTqX4VUEEp60pFOrJNxYM1JtxXTwXhY2AAAAZAAAAAMAAAADAAAAAAAAAAEAAAAAAAAAAQAAAAAAAAAFAAAAAQAAAAAfpR7UY4+Podv9E4/IgUImlA8y6OKEQi8lJ8rRR8wMiAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHwXhY2AAAAQNbDcWsR3s3z8Qzqatcdc/k2L4LXWJMA6eXac8dbXkAdc4ppH25isGC5OwvG06Vwvc3Ce3/r2rYcBP3vxhx18A8=","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAAFAAAAAAAAAAA=","result_meta_xdr":"AAAAAAAAAAEAAAABAAAAAQAAHq8AAAAAAAAAABbxCy3mLg3hiTqX4VUEEp60pFOrJNxYM1JtxXTwXhY2DeC2s3e09BgAAAADAAAAAwAAAAAAAAABAAAAAB+lHtRjj4+h2/0Tj8iBQiaUDzLo4oRCLyUnytFHzAyIAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAA","fee_meta_xdr":"AAAAAgAAAAMAAB6hAAAAAAAAAAAW8Qst5i4N4Yk6l+FVBBKetKRTqyTcWDNSbcV08F4WNg3gtrN3tPR8AAAAAwAAAAIAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEAAB6vAAAAAAAAAAAW8Qst5i4N4Yk6l+FVBBKetKRTqyTcWDNSbcV08F4WNg3gtrN3tPQYAAAAAwAAAAMAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"text","signatures":["1sNxaxHezfPxDOpq1x1z+TYvgtdYkwDp5dpzx1teQB1zimkfbmKwYLk7C8bTpXC9zcJ7f+vathwE/e/GHHXwDw=="]}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-transactions.api.mdx b/docs/data/apis/horizon/api-reference/list-all-transactions.api.mdx
deleted file mode 100644
index c83d94d1f..000000000
--- a/docs/data/apis/horizon/api-reference/list-all-transactions.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: list-all-transactions
-title: "List All Transactions"
-description: "This endpoint lists all Successful transactions and can be used in streaming mode. Streaming mode allows you to listen for new transactions as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time."
-sidebar_label: "List All Transactions"
-hide_title: true
-hide_table_of_contents: true
-api: eJztPOty4jqTr6Lyj3MLCTbmYlI1tcstAULIjVzInFSObLfBwbaMJGPIVKq+19jX2yfZkszFEJJJJnN25uy3/jEZbKlv6m51t936onA8YMr+Z6VHccCwxV0SMOUuo9jALOqG4reyr/SGLkMQ2CFxA448l3GGsOehi8iygDEn8hBPAUA4sJGFA2QCihjYyA0Q4xSw7wYD5BMb9tDF2m8BjcQMzUiEOJEYIEAOoSiAeAM2Q3wIM4QpIGzbYIsJfAjogoPnYYo8sAdA91DLQRb2vG3oM6hJqPtIAhS7nocYx5QjzCUYwNRzgXE0CkgcpHGjKPCAMYSRFVFGKHIZYsAzAn48dK0hsjAD5PI0VIcSH/Eh5vNJe6g6E7O4oEXgm8OaYC8CwUpA4oyUgxBgQva6ACwKmIONmBtYIEZSRGEcCZK568OeklFICBSL0S1b2Vc6LuMVz1tb4owSYop94EDF+n9RAuyDsq8k1CgZxRXrPo6AzpSMIuC7FGxl38Eeg031qKAg8k2gCZ9SSZhgBSMWguU6roU8YkmChKwwsojnQSJT4iAKLCQBg0RvXIbCSC7bXHSAQjxwg8E9JyMI5oIiDsKIgkWoLRhm1hB8rOx/UfgsFHy4AYcBCEZgiv3QA2W/WFSLRa2ULxnlQllTC09PmSXbhNrwfq5tYO4gwAs+BKkS0EohEgoZYkMSeTbCYQiY7qGTMFlKN7C8yAb0F2bWX+g3zCwIbDcY/I4IRX8JdH+h38Sf+W2p1FwYI6aDyIeAI5cF//2v/+JzReTIBgdHXiJ/CXareBinbjAQ0gkiX9g/ZpaSMKjcpQXjub7L3ymY3hCQj6euH/kLxZCrnIiCAo9oAPYeEuMkfKnqFAcDSNZcE8TnVBXtIhygKAyBzgdKBXMZGmJqW8RObHthy8JdhEAdQn0sTIMCZiRgrwhtsYBgP5Odpr5VrzQ1LbD5kt472PXAfqfkLoBLb0YTV7BQjwQWWlq1UBxhNYLW58okZwtLkii2cmES4gEOVusv5mTk+Lunp7uMMt1lURgSytnu0nMq+3KUsjRXATCnquLPBhvJtqBkFIsEHAIuhuAw9NzECWQfmBj3JUUY9rwTRzqiOYnEfABLaF5IBd/cTfDde24wYilWXhjHwHO+PmpIwdlmFVKFuFT/YKQ8ZRQOfugJPdkixKen9Lp+ToDeZRTucg9SMAKY8p+MpJDC5Kci6UkMW9zqyKUWtvUVnQDfBBEJfJ2VuRNKDcSUYmGZLgf/DXrlg0+ey+Ip809WTGxZJAp+Nt1MwrifjKiVC/7JCAPHAYv/bFSFFCyw4Wcji4n9CeyfjaxUlP9TUbYxSHqwlddYWuqadaw0MqUFKcmvc3v3lFFcexs7C0pcW+pTKhHY6oXZMiHdxm1GGWI23DrxmbdZBXpLiboB13Ni8DwDu8d8OxEkohbcP3erS65CzDlQESodfq7s3qq75bsvhcJTil9s21SEUCv3fO9HU9gio80R99sE+YyqeyZSxsCCrWMd+H7kp2C9xMJHIb7EshhoDTEdvCA3H0/vHdgugqUu32+K4TXNgGACHgnhfmrTrWCTqP1rj33g+MUxgqtXB4gY5T65u00PZMYTUXhLFPTVBUqFaynAc9dPAtt942YpKhcmiYK3OGXfDe7F+BfX9IWHKVpTtZDTNKG9FRlLp/Aesp65kXXCXnz8BtI6aWIEPDd4mzFvG3iPB+8YnJB9P8Dh62YQrexgyim+Fxoh60tv1bOntwhiYQNm5If379szt3r/FUb5/H/LRFK3DwCqkR+mGBaT3CAA+g9m8DX/mprSEmyusb4Rb7i2srHzr+3z8009FYaktudnm/HL++D6rre+eaxYeb4xbDj9NRf/3KGnvfPaOtw9Pb2k/crT3dOy3iRXZltFd/+LIkuj61WSRbqZhIvKkPOQ7Wezw6RktsuB8QD4Hktq53uEDrLpYvN/JPXgT7/I8tsn/RdZ3/wkqoWpisYHget6SS+Wi4am5bVScTuqRaXig6i0nGHky2qhbOQ38MjSp1iAtWrCsl7weZH6K0PwPIJiQj2hF99N0lldN8pQdlRHw8WCo5VLetHCllPI560cGLmCrulg5PMlp1As53TdNA3b1MsYF9WSZRhGeSOTfwcZ81kse1ip3Lbyvdq53usXTtrNWq9dy1XyZxf9Yq193W4WWpV27/Co1c01zkudavfq6KRWu+6W1gPod2BOJrGs/jy3/lFizK7I+DLXmozUlIzUExmSrjIqURFdz75/GN1zGt5OdDo5/1azWtroL88NbDPT/hgOYZ9bkcxTR+XD9rOZXippNOupZVIIT3bb74F4YTz6em6p5FStsKuWd3W1p5X2tcJ+IX/7fE/bV77ZcF9JCxVtYxPc11U1tafLX8+yJH0zB1Iq8jq8tPyjk0K+WGhPexeds5Mz7yEe5S6ccaXt314cFtvNYszHYTysVCrVTmV5VVf/bYh/OvjwipmHxsDOlWfm4VnyKK6sX1VzWpvpfmegD93e+CZ/ddlohEU1PDih7e60f6y1+fSmF98M+7lkwoTGg9T8BOy1ccZ4wc138/1R0ds5uKpWj4AfnffGs551Xe9emNaVahzkr7vJ3G6+gx8f8tOitoJ0UNl2nW29u+2qdvDYaonxjepRPL6e6T18MiWHgeOX4fLB6Z1XJ6eOnrcn9YradXaqxmP+sUrMsnp5w6Pa2D8bx8e1WXOHjE5auqUWTKqPhqOmOjvNj2qx1ViPWBbrValULlJC3ZRvir6N32l+P20JgFIIKsfin9rG7znYb17A+mvCfPHJ2Qb+dyhsHWo5VuD50+7ZBrx34JcCbmzSX/WabfchgpPowrpUXbU+aveNdncUFAe1W/9yGLnnO2ypIJVKp2i0UtMbr/C67TrexP9eA1jhf1lhXsH/jP934NcHnJ6YUH+8/CD+6rP5t+ezPikFD3QUHHRbvFKoXZ/WerftHVLxb72WSUYOreXGQS2Rd21nktLpV9b8+fVJ2SzvJNYipXu8Ce0d2iGlE9y+hYa3r8678fezpcsNeG/E/+nTWua0r3CReqwnsp+VC3bkMa7mHhiuhnphcuO1dFU9Mx/18k7TjONu/SY7cI53jmN8mLUPDkrmYByOjli9wobZcbvudvXuyXWxXGjdVsvHDzvtCmtWBe478RJyHv+LeCUkxMs4OLKAZ5jtfNc8IGebeTOXs7CqGZpWtgpqroQNtVAyDE13HMspGDnLxnmMy6Brll3OmXndcjTTxnnHKuDvkgd0Tmu1226+f1PR+8ft5lGnWLtqNWpHp512u9a7Or7o9q+rvaP2df6o0Dzr9Dv149te9cN5QMnIa98vFfioJH9UKvBhun+OVEDXi6WioRuFUk5NqoJ/TzawiWeREHzYkJ4lBBuYXskJvgPuhSEJm9iWFmjqrqr11LxIC1TthbTgG+341bQgyYo0o6x+xwThffHePEHYjB/ljtKzD68e7WZ1YuZidusfaP3cldppdke3L8SHzeIlaIcnpw/Fppk9PzmdtQ5q7fDs9Dh6cIeN1qR94Rypl85xvZUA2Njfk6tzHOdPS7N2bzZ+KIa8OyxVT2c3DdLbebyKe9Zlvn1lHs5IMBmYyYSNhCMRQtuLI7VwEmYLUy2a0Rj6bHZeDHs9wnR9eN69hULroGh6wWMSn2zEe81lPHxWv6hWC9BtHI2uW+TMvNX6Z9hsR42Cf52tHA1pszeNy03dzzLsltW+hW89VgE9gpPyQ2P6cHF7kDPKt9Z5fmKp8UGshdnrWcX69MFk4bXrfclCc5wKH6o7XpOfPzzkd4a5rNp7MNzqmYsv648dkifntc7sMpjxg+ZjZdZaE361OHyFoFeThXX8b1demSzkd46hKaWUKOMzRfgK/sX4Nfprj8cn9R3DvTTGZGds9voQ9wxvetTIMs1q6AcntavrKRu3S/nDdeUB8lo2+lo4uC6/9wbrddK5NeRMSU9rO5oX8S/Hr9F/cWt1+Elv7OxYtsnGRtPvHI9gfKkWO91y/rJ3fRNdVMEv3BoJ6oUxr63nNl63X9VN/AeTRqcD/agOh+2T0BlenZ1dBPRidFlkI/1g8Hjp6wf2aRUOHvqyWmCXeqojZ246s6/i/1qyUC0UUqO/IZWKiJwZv0jB36kdJtTDb9SOtyUL3Vaj6eXVs/F53x1WeXA1rIbMz/f8W9OojA+Zfdqsqw6YO9NxRz8fTkP/Oq6WoJAv5Y57h9326MZ81Lxp0y0/9io39eugbLaq8Uay8H3fEFiQwxbOOWDrRRvnHAxY1/RCzioVrQLktZyeNwyjhPOWppVNDcqqDYatmWW9pJeL//DMoFD4ji8JPijJH/aS4KN0/yyZQfqF39+ZGazjWb4q+KghbckM1jC99rbg47hXmUGh8HpmUNzXfkhm8OzVgbaWGWhbMwPte2QGlaTGtVnJTG1fqy3jIPXbCc9Ll/38zimxJ+VGPtsaXLZ8r2LMiidHjTPX8NoGPT834mP3pR3v1SsVmXfNunXNznWmPxpnj2PMLdvKjnKdfOfmun1cKcINtgzbvBlVbCsfhs1cwWWHtcJJPDlUi1fxxNJroGdpjvat6qk+mQ6nmlExXo7MD7dWpd9Tpk+VRWXka6wevTfy1UEtVwerxVmlCgn8d0fyqbkb19eio49EJ12dn55/IHaV0dHkY/jP+iv8x9vRfCA60lh3iqdNeHROp/WTcKxNtcedXn8y4HZ/FNfDgh0+TjUOZ1Xt0fVHjukfxf3OqFQzzF54Uys/Wu2SszPBfBg3spA9bDZv4noSHSVfusiPXWDKIWDJbv75izKCmbK/vfcos/i4Re5Ld4IDPiTCmQ+AJ98mCe+6tiMIpoBOFh2OEfXetq0o2xraesk41AUeEzqSbSnbITqRkOJbYB4sRqJgAfVOfPflJC0m8y+B5u1tQgRAWTJb3VP3NLnN+D6ms9UoFFIycW3ZS4mavd4pqpy2RC+ZjTkWbWPpTtk51j3U4sgNBiDbegMbUdiVgpOdtsnMkBI7ssBG5mwbiKStU3wIuGzRA8xc0RJKkEUCFvmwmIonQPEAUKohDFHwMHcnsOjlTbXx7RLqQiAaXiUhFEIKDAI+74ST/cXmbElQjVAQrYUuk5yn+DCpaw8AmcBjgECgT7hdn3lKifi0jiHPHQGKRQMxZxlkgwUBp9hzH8FGMLWGol2RZSQEzBgInlkEVFK0bEnkBLHIlJ2LKcXMINkPKJZovo0iE3uC2Yxo/Jw3/cIEggUdaw3AorN2OXPvmWb9u2vC5/SC3v22ME8bktiCsrUQck521iIUdgNiw+//VtrzZ/BnsEA379jHMnIFG01cjKzL804GYWRSEjOgEgMJYNHuvJT1Rf2IfVXWNrFYlhPisSyzR0xImiAKQp2SVngivnCcunwm4MvO9jARaAbFIDuIfR8CW7bHC0HhQCBGbsA4YFtM8vFINNbbLgWLyzUUZwAwyadc1kHk2oASizGBoSGJpUhs3w3EqQMULVRcquNCNgKFbCr+jYKTKLPkv77k9FdU9chgJYM4jteZX47cNT0yyOLdAOJdFgW7Yhcawu58//hd9jEzIswEW6MBFV98IxJsWkOiO9QauhwsHlHsIdcXNg++XHkyb3r28YM4XiDZOpD4aPr3PXQgTi8Ikg+3xW1skkj0P0sShQDn+JaqQWwwMYMMsoZgjZAYneZfdlUfCtGuBDBw+TAy9yziZ+dyWPxdsJo1PWJmfewG2XrjqtE5OW11D/d8+3e5XFVwCAWx8CYM3EB0aP/KxIeXXPTVu1ymD/NDFIQbcCURYA1J0hYu6RNmibrE/hZHgGxiyX5xKaN99McfMSBbnNDAxWEYhDJANAoCQcRCUGLJEjeExQEQgY09YS5pL7HUpT/+SBwAyFMSsOfNJGg5936CPdeWDN4/29tAqD4FxGOCGIiDHLgwnsACGsydig0WiUJvLh9fuGHXF0EVDrhUMJNIMXouNl1PWJyYlVKvvTXVF9bl4wAPgCFXKFccZFCIKdi7tjglY6FexFlnlYTc9aXTEzjnM4VTEy6POCgQST/6LYZfPQ+lLMuV53xg9KdSw6HcDgS4P5Wl7ISKyIIF9dmJcwF04socdLHIa1UCMWiXOHIrc+Wn3qIvHVuyDDbv21+QnVboA2F6cvGVzEawtx7agY9db/Ft8H+mn4m6l2tBwCCFqxJiawgotyfeoLm20F3HBbp8sps8WWGcuxMsnyZ1sQQoy3ZatUb3oiGm7A2578kqR0gY93GQQim+GEcVz0Mbp4CshQ5fVv36/3/kyz/syJdUMpcNPezKFhKpQV/mydFnZS05ussoQ8K4uP/li/Dtl9R7ehK3k8MqRMpkuwyb3kvHVaTV5ccfAbNVAElGuTzUZp5DKjJ7ew9z/5iTXl6RwuKMm28Uwv+hU11eEdLivJtvFNLfdIDLKwQ/O29mRfmd+EFdQbqy/1n0EA0BCx1Y1VoqlgVhmt9np7Ss1VoOGz3l6el/AHyseUw=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Transactions"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/transactions"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint lists all Successful transactions and can be used in streaming mode. Streaming mode allows you to listen for new transactions as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./list-all-transactions.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./list-all-transactions.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./list-all-transactions.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-all-transactions.mdx b/docs/data/apis/horizon/api-reference/list-all-transactions.mdx
new file mode 100644
index 000000000..aa3cc9bef
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/list-all-transactions.mdx
@@ -0,0 +1,12 @@
+---
+title: List All Transactions
+openapi: "openapi/horizon/bundled.yml GET /transactions"
+---
+
+<Tip>
+
+**Supports Streaming**
+
+This endpoint supports streaming. To read more about this, visit the [streaming section](/docs/data/apis/horizon/api-reference/structure/streaming).
+
+</Tip>
diff --git a/docs/data/apis/horizon/api-reference/list-liquidity-pools.ParamsDetails.json b/docs/data/apis/horizon/api-reference/list-liquidity-pools.ParamsDetails.json
deleted file mode 100644
index 45bb39cb7..000000000
--- a/docs/data/apis/horizon/api-reference/list-liquidity-pools.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"reserves","in":"query","required":false,"description":"Comma-separated list of assets in canonical form (Code:IssuerAccountID), to only include liquidity pools which have reserves matching all listed assets."},{"name":"account","in":"query","required":false,"description":"A Stellar account ID, to only include liquidity pools in which this account is participating in (i.e. holds pool shares to)."},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-liquidity-pools.RequestSchema.json b/docs/data/apis/horizon/api-reference/list-liquidity-pools.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/list-liquidity-pools.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-liquidity-pools.StatusCodes.json b/docs/data/apis/horizon/api-reference/list-liquidity-pools.StatusCodes.json
deleted file mode 100644
index af8bd0e7c..000000000
--- a/docs/data/apis/horizon/api-reference/list-liquidity-pools.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"fee_bp":{"type":"integer","format":"uint32"},"type":{"type":"string"},"total_trustlines":{"type":"string"},"total_shares":{"type":"string"},"reserves":{"type":"object","properties":{"asset":{"type":"string"},"amount":{"type":"string"}}},"last_modified_ledger":{"type":"string"},"last_modified_time":{"type":"string"}},"required":["id","paging_token","fee_bp","type","total_trustlines","total_shares","reserves","last_modified_ledger","last_modified_time"]}}}}},"title":"LiquidityPools"}]},"examples":{"ListLiquidityPools":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/liquidity_pools?cursor=&limit=10&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/liquidity_pools?cursor=66835-00000000c582697b67cbec7f9ce64f4dc67bfb2bfd26318bb9f964f4d70e3f41f650b1e6&limit=10&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/liquidity_pools?cursor=38888-00000000929b20b72e5890ab51c24f1cc46fa01c4f318d8d33367d24dd614cfdf5491072&limit=10&order=desc"}},"_embedded":{"records":[{"id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9","paging_token":"113725249324879873","fee_bp":30,"type":"constant_product","total_trustlines":"300","total_shares":"5000","reserves":[{"amount":"1000.0000005","asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"},{"amount":"2000.0000000","asset":"PHP:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"}]},{"id":"14be5a5b3d3f5e1e74380ab0a3bf9c172b7246fdf7753b172cbacd4d66143c08","paging_token":"113725249324879874","fee_bp":30,"type":"constant_product","total_trustlines":"200","total_shares":"3500","reserves":[{"amount":"1000.0000005","asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"},{"amount":"1200.0000000","asset":"USDC:GC5W3BH2MQRQK2H4A6LP3SXDSAAY2W2W64OWKKVNQIAOVWSAHFDEUSDC"}]}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-liquidity-pools.api.mdx b/docs/data/apis/horizon/api-reference/list-liquidity-pools.api.mdx
deleted file mode 100644
index 7616a5b0a..000000000
--- a/docs/data/apis/horizon/api-reference/list-liquidity-pools.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: list-liquidity-pools
-title: "List Liquidity Pools"
-description: "This endpoint lists all available liquidity pools."
-sidebar_label: "List Liquidity Pools"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlWdty2zgS/RUUH2bilCST1F1VU7uO7djeeGIndpLNOC4HBJoixiDAAUArHpeq9jf29/ZLthokZUmRc32Y2Z28uCI2+nL6gu7GXeDo1AaTi+BY/FYKLtwtOdVa2uCyFXCwzIjCCa2CSXCeCUtA8UIL5YgU1llCpST0hgpJEwlELlgUyKITtAJdgKHI4IgHk+BYWLeQU4lpBQU1NAcHBtW4CxTNIZgEBiyYG0ACgdJ/K8HcBq3AwG+lMMCDSUqlhXUld3We07YFZOqAezWJTgm1FpwlQhFGlVaCUUlSbXLyaFdzmBxZW4LZYUyXyh3tbbWI00QreUuEYrLkH9lGZplgGcnoDZBGVZJTxzKhph4WlAy8FtwJ5q2FabQS85WW7ZAzB1JSQ+rz5Gjv82oKVWvq0HvNSWFJQY0TTBTUocJCkUeiAx2SacmtP0tsRg1Y4vTWivasNFabr1ZelXkChriMOuIjCDkTSmwBTKSCEamZDxTUhRKmpQTm/69TRLjQyoIlVHGvfSklcJIanROXASnoVKjpldPXoMgNlSV4pxMDTBuOgWhZBjkNJneBuy3QDqEcTAENgQ80LyQEk8EgHAyiYW84GvfHUdifL5mtDYevt5qDFVNFGztQVc/o3i+VhpbYTJeSE1oUQE2HnHgeduHX99Sy9+QRtQwUF2q6RbQh71Hce/II/9Q/d8hRWvvaTMscvLPVf/71b0csuBYRjnBIaSkr/D3bjfBYZ4SaIjqqzLE+UMuCysDgchkYKXLxtbF8ngHJ6QeRl3kTGN7LFRQGXGkU8A5BOs8fs5YYqqZQ+TxC5eMwJG1CFSmLAkxN6ANMWJJRw5nmwBHqQ23E71phxpMCDCY+VQwzl1qt7CdAaxwI/CPsovBL4yoK5/NLBKWOYqSOwxD/rOJyVjIGFmse08qBckhCi0KKKje2f7VId7cklUp5kvrCWcvXya/A0CGFweLrRCXvSgp1bZf0fIDOgkw/T5UZSDcFi0fW+ahQ18G8FTjIC4nwLVEnWkugKpjPlwPlomJ62QqccBKWeCj44P5kKhUGbv5UKs2RrPnp2Lsac/QzMQF5ApyviH2AtM7NJUJqDMVUFw7yL4grwTch0WgsuEd1qYp/inqFbt4KUoCrpNiYgwuoS6FcN/Zge5p17vhBOyqvnCmtk0KB/QRRdTduJFg0Lp+FxLcGG3nQ3DcIH39CL0tq3VWuuUgF8CsJHC3dxGWV0Il8k9lr0SV4sOaHBbw1chtwWkOltdy8bdR2o26X8/UoXmkU55fzRUn18G1oJid3gb/8VwteU9KqdAwy5wo72d7Oqkuh7cA6Ba5jq/aqo810e9FGXfk26m9V0/PTD/6O+SkKf/C3+E94Jy4VqO8XMBiMuv12WP9j/VE8GA+TwZAlwIbpmMGgl/Y4GwyTNImTlMeDbjRKknE69h+GIXTTXpQO+mESweABdZvi9f3qdkej0Wih7jgeJ3GYDGPoj8YhTfoRi3tpxFhvkNIwYr20G434iHe73cGQxz3OB1GPpTzt98ZROIzX1fW9BkbESp1aVKKLqqgEg2E8CFmPRaNwmMSDOE1H/SgJaTeFqBdF4964O0iSMI76SZwOh73eMI14GkXj8QhokozXA34SRFF3GPfj3rgb90bD8WjYvc+CSTdsSghe0tZR5a4Ko3npM/zjGhJ0w3A9QyZBP/S/3heLi7tF1gdRGIadCtN+0GrqRLD/6uX55GDntH+8f37yevD2aH8Qv935uT84O9/beX76cu9k+MvTvScHZ88P//Hi6O3BwbOzn09+2Tk8OTmLz/x1sJAQ30sIlyScHp5+h4BLFOFdEvUS6NN+0uXdtA8RDHvdUUjRJ0k6ZtEwToZxb5DydDjsd5NoGLOEMt7jg0HU67Jw9AUu6X2PS+JNLun2/1CXRPFGl7w629udHOz233SfHMY/v3j54ll82NsZHJ92z/65d7az8zZ+E78Z9E7ePHv2+vmLo52T12/Odg6f7u3jQfRJVVZ9Zc3BZRr9MwV/G1GXBZNgPbmxqUUE6nm8NPLLikSwqcs/r+jIc3Azba69yZs5pqUrDXwJz6cNJVEN10ucP1Lt77f6+qh7/qAVoCnV6bATdiK0r8xzam7vqUhh9I3gfsAkh+fnp2Tn9AibfE4dxQkCJ7dm/q6ldsiRI0JNwS9CFCcG2vUiAKn9ySoKgZPkdhOLatb1e4hmbgFqBc7JmmAolzk0R+kNGDoFsjQOEAOSOnEDSO7H4PvZpq2NAIUbCK+IgQIDWzlazZWlrZRqFNrVBnDeEtZbvmRHYgSfAknAzQAUiq+sXT15ajT2OJZIcQ1kRqUEZ1uEAwPlDJXid+AEPrAMZzjb8hx8iBPhVy9eo8Wc5jSxZeLHOUOVpX4RYFvEj5foomaRkVCJxrZwGrbOAM0J3IBq9Fg+7dcNi5OdjyLrrx4JF8sOvXzUpCeHG5DYtdqVhqBWe5tpA22lOWz9paLnnXqnGnG4mkgAP4FFLG8EJezVy+MWoSQxembBeAlaQbMDWmB9tvfMfhZrrpnddliaty2/toi0JgYwnDw3prEn/oBLP52SW10ajDYEtEVm4NcqeQ6K4ycPFFUomAhlHVCOh3J6jWtALgww533IqJTW2+ndOi0FB1JlTAKWZHrmIeG5ULjoNKQJcR+ODTbC38YMyCMDaRXM3v69haU/kidST+8xmM1mq8YvKNuJ1NNt2lYwa9tStfEWyqBd3x9bfrljNaYJZddTo0vFiVbr2VDFjmGZcMBcaagkIsech9x7XteboJz+qg2prw6SlHmx1SFPNW7uqpkSf6aJLnEp5FVEAGt5i9DQHBJqoUVYBuyaIPWy/X7VdIDQ3gMwFS4rkw7T+XaNQ/O3MXU7kTrZzqlQ23v7r/ePT06Pnh90cr7l3fUEUm0AHZ/AVChcW/1oyUwbh8tG4fw+Xk29HlgGhFcCWKarXZnXD9OSPNf8WwoB4Zr5JZrHaEIeP54B4Zoo7fD5QBsLxJRKoRINUOiyqgxRghHDqcR0Wa4Si1h6/LgqAOBXx1TKW8/an726oVJwb+DVR3cbYOgbIG6mSfNCgLWVgVF1UeHAdFnIGp8cy7DIC22wpfQBlmgPoxQ0ERIzDk8thVdnJfQxu3Kq6BQsERhcM9XCzTvwNtcztQgvna6aqgsncl/0UGZ9EosaljydEgXALXk0gx+lJEuZhRtMSyh5F+zSwl8HyO5dsMAOQwQ7XzC5PUnPwNwIBkvN2LJnPVFbp/4qQ7JqK0mZn3Xr7W+j9nJAP8XU884PWmvN3mprBzkV/itIqf++/A23F4KBsrAka6egLAMSd7A/FhxjNxW4+6i/tKsv9xLrckL913qO9Uzt9vHR7v7zs3080slcLv2cWWjrcqqWROKOgay/jK11Dnf3y9pveyOrRxcHH9x2IanwOy1vxV3do18E6z36ZSvItHX46e4OS8wrI+dz/LlawWPn/qCWf9pHsgewuIbb1RfBeskT+HHiQTP/0BezT5py/wK4aomwGCMPvJqsmvZHv6d9wrrFC+E3G/c/82z2CRSaB8NvBOH/6InsEyA1j4f3IF3if4xAlILJBe58M6CIJFa06tAOY1Asn/rohQy5LJYdB/vnwXz+X8BtasU=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List Liquidity Pools"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/liquidity_pools"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint lists all available liquidity pools.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./list-liquidity-pools.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./list-liquidity-pools.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./list-liquidity-pools.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-liquidity-pools.mdx b/docs/data/apis/horizon/api-reference/list-liquidity-pools.mdx
new file mode 100644
index 000000000..7e4b3a184
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/list-liquidity-pools.mdx
@@ -0,0 +1,4 @@
+---
+title: List Liquidity Pools
+openapi: "openapi/horizon/bundled.yml GET /liquidity_pools"
+---
diff --git a/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths.ParamsDetails.json b/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths.ParamsDetails.json
deleted file mode 100644
index 4910abb0c..000000000
--- a/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"source_account","in":"query","required":false,"description":"The Stellar address of the sender. Any returned path must start with an asset that the sender holds. Using either `source_account` or `source_assets` as an argument is required for strict receive path payments.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"source_assets","in":"query","required":false,"description":"A comma-separated list of assets available to the sender. Any returned path must start with an asset in this list. Each asset is formatted as `CODE:ISSUER_ACCOUNT`. For example: `USD:GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX`. Using either `source_account` or `source_assets` as an argument is required for strict receive path payments.","schema":{"type":"string","example":"CNY:GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX"}},{"name":"destination_asset_type","in":"query","required":true,"description":"The type for the destination asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.","schema":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]}},{"name":"destination_asset_issuer","in":"query","required":false,"description":"The Stellar address of the issuer of the destination asset. Required if the `destination_asset_type` is not `native`.","schema":{"type":"string","example":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}},{"name":"destination_asset_code","in":"query","required":false,"description":"The code for the destination asset. Required if the `destination_asset_type` is not `native`.","schema":{"type":"string","example":"USD"}},{"name":"destination_amount","in":"query","required":true,"description":"The amount of the destination asset that should be received.","schema":{"type":"string","example":"5"}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths.RequestSchema.json b/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths.StatusCodes.json b/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths.StatusCodes.json
deleted file mode 100644
index a23df7188..000000000
--- a/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"source_asset_type":{"type":"string"},"source_asset_code":{"type":"string"},"source_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"source_amount":{"type":"string"},"destination_asset_type":{"type":"string"},"destination_asset_code":{"type":"string"},"destination_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"destination_amount":{"type":"string"},"path":{"type":"array","items":{"type":"object","properties":{"asset_type":{"type":"string"},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["asset_type"],"title":"Asset-2"}}}},"required":["source_asset_type","source_amount","destination_asset_type","destination_amount","path"]}}}},"title":"Path"},"examples":{"ListStrictRecievePaymentPaths":{"value":{"_embedded":{"records":[{"source_asset_type":"credit_alphanum4","source_asset_code":"CNY","source_asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","source_amount":"28.9871131","destination_asset_type":"credit_alphanum4","destination_asset_code":"BB1","destination_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","destination_amount":"5.0000000","path":[{"asset_type":"credit_alphanum4","asset_code":"XCN","asset_issuer":"GCNY5OXYSY4FKHOPT2SPOQZAOEIGXB5LBYW3HVU3OWSTQITS65M5RCNY"},{"asset_type":"native"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"CNY","source_asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","source_amount":"29.0722784","destination_asset_type":"credit_alphanum4","destination_asset_code":"BB1","destination_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","destination_amount":"5.0000000","path":[{"asset_type":"credit_alphanum4","asset_code":"ULT","asset_issuer":"GC76RMFNNXBFDSJRBXCABWLHXDK4ITVQSMI56DC2ZJVC3YOLLPCKKULT"},{"asset_type":"native"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"CNY","source_asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","source_amount":"29.4000002","destination_asset_type":"credit_alphanum4","destination_asset_code":"BB1","destination_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","destination_amount":"5.0000000","path":[{"asset_type":"native"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"CNY","source_asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","source_amount":"31.8955888","destination_asset_type":"credit_alphanum4","destination_asset_code":"BB1","destination_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","destination_amount":"5.0000000","path":[{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GBUYUAI75XXWDZEKLY66CFYKQPET5JR4EENXZBUZ3YXZ7DS56Z4OKOFU"},{"asset_type":"native"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"CNY","source_asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","source_amount":"34.7086084","destination_asset_type":"credit_alphanum4","destination_asset_code":"BB1","destination_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","destination_amount":"5.0000000","path":[{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"},{"asset_type":"native"}]}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths.api.mdx b/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths.api.mdx
deleted file mode 100644
index bbafb5144..000000000
--- a/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: list-strict-receive-payment-paths
-title: "List Strict Receive Payment Paths"
-description: "The [strict receive payment path](https://developers.stellar.org/docs/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-receive) endpoint lists the paths a payment can take based on the amount of an asset you want the recipient to receive. The destination asset amount stays constant, and the type and amount of an asset sent varies based on offers in the order books."
-sidebar_label: "List Strict Receive Payment Paths"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWm1X27gS/is6/nCX9OSFAglt9nDu5o3wEkJISElCOKDYk1iLLXklmZTl5L/fM7IdEhIKpbv33rbbLym2NDN65pmRrJkHS9OJsoqXVotqV1lXacsBZUsWaCa4VbTOXSCXSktmayLBBnYHJKD3PnBNAqrdqw1X60AVczkH7sATAUiVVRo8j8qskJOcI2yVc6imORowlXOFZH8Kjn9kJIxBArchJ0GJUNqgciiAom6VE6PfwdY51JKJVWYiSzKxJSkC3AkE45p4TGlFtAvGKkXo3EqbcqLpLZARVeAQwc0o6ouQayLGhHJClQJN7kVIppRr816CzQKG87VIFp4liIYDSjNubIwnxrKUpveK2IIrTblOE8odI0rfB2D+WKNToYY7KhmoR/vEeAxSERZZKqQDkoyEuFXZIR/yfSGJdpkiCqi03TQ5iCAlnqAOLhyhMEpQgyL0jjKPjjzAlaBABRwlbsz13UTgX1PbRgNviJCPz4yQm5RZgMNU4OEiDc5CKYZiI8DHUvjmucPGxq2aRCISO2LtK/BlySn37mMp2qWaKKqZGt+b4TcL468jAG8IleggHUoOTnbIrbQ1p82hYxWtBlO6Y5jSjjzXirgQcTxtBVRSHzRIZP6DxakPVtFaRsFKWwwD4I8Q5L2VtiT8ETIJjlUcU0/BujjpRLQn1HEkKIU+eMQ7S0r8fm61WS7xQ2VoIzWZMu0+0sLAsOArV3iOypKuYnxCgGkX5Gu8RqgyMuUkNKHAFEmWQcZCkpW41m4SNiprpS1lu+BTq/hgIYcRIi0Zn1hpCz5TP/DwUb16cnbWPDrZ6TZ2zw5LhUJrt73VGhycnB02Lwblk93dcq18ctDY71XzR7Vu6aB+tNveORpYs1l6BXpj9lciXyK28H2aUYBu1eC8MgC+yiEmFpkyorOkRm03eaEQSZ9qVEwVuamcVmvFw06nW2tflyqV027z/CZLMGhjzIrkptupFuvV7vFJvVuvDs6OC/2Dfik/KJT6W/WdXrUzaHUG252LfLe5XWp/OjktnHXa1YtWvt+o9W7+P2lQafaL9VK7Vmt0yzvbh+2Di1qpU9kvN44Puu1K/eSglj/cL/Q6td1ar9ooVfoH9fbByc52e/+0t0SFpXhH+6+N0mc5oWW4NhhN1h2bXLk26dRi+PDpHdykyY0twWH6mnqBS3no79ykDZZPHr/funkBEx76uKFGgq209VTu6qP3W9bVlzFgSoUg/7qcFMlL/loDTzshCBuvycNzv9wgmbjQcxxfnzbeRv8XuGIL5wtceRYlnPYlsvzdaHQ71ecX5n95O3ouAB5PG2sXFW+1rgg9h4wgiX7ntSbnrdnsKm19zqgwCITUCs9mQH0cF9skQQWCK1AoaWtzE3+W7eyEtg0KM74tuAaucQgNAo/ZxtTc7wrHPaxaFB0OcS+XuPdrFmm5Bn8EjoO4vDRUgi2koxYGUikpYss0+OplAYtJNkpSK4DN0sujDD1fHBUH+xr4A9xnJCJXvyxlBpuZj1cP+fzMSluaaeOWOM4XZUb8Waf1mVz7uqHPruXZ7PWtC1oTFev04/71dq++gMMLa/8L1ztbDPLLRbuuHkeX8Glmy5rNno5fZedTRjzr/7VIx7heRZoS/XiixnXHecEguHT6ZvDk9F18sO6oF8JKtM7j8XJtaK3bRtfEFh5Enr5J3GG9+YCyEkzW1ofsxw+7799vv38ex7U2PxdIVrm8XtSj9dX8UeGgsZ8vFAq9ndKgcb5/3mv0dwpH+c7Fbq3XPi43av3WUWt7u7O9fdIb1D8VKhf7zfX+LFr57Gb0L/EtIv+S+Usm9ypN6ynnrXql2c+f9vqd/s7+8cFp63yr0zo9G5ROa4f1XjnfKPcvtg8+dbdPLzrnZ4fnnUL+JN9Gr+H+t6Q+PkHNrvDNd0CJj9nN3a2t3Q/r3fxzUKLbOF9Hid1C+2S/2eyV96udo3a5VymVLxoHverxzuH5p7POyWG+UK1sDY4+Vbb7p41Gq3J8jJJ+AErsGDy3fmBKfGc+2X6f/fAxn//w4cMP7JMXw7RTXROm5W6/Wzrczfd6F9VB7bjRLxQq+/3js1btPH/U3qnVmr1BuTvY7vcGu9VOvjDYOT0+3e9+92G6vZPd3fxQ2Py5M/daSrz5M/15SpgjZHSM/JxB5Z3k7Hj5YHkUvx+tjgueN/cUWh9KjySlhriIkNGgNAe9VG8w98i55TrBv4fDIV+6E9v7lvuqf6G49TTZe4ryM2Nx2Xvl8vtnXkf4772VJKtSDU328kNuHBODfETvaMd8jVtpy6Mj8Kyi9VsMZi7+zSjndtERd1Qml0od55bsJVeJG0NrYcbQSv065DhWgbwDSfYIh+nCxGxctch2zPuNISdkaL3CwUMrPeQofMgj0Tgzq5Zv+7WrjERCLqMf8lS9+XDaSF6i7kqzb2Q/PnkrPxbEpOL/XcW/X7RiiGljYfLwzVliLiTRP7Ty8bOUwcumnrcR/Ve7wDfGIbfN3dAGXtqkyEM0DYtZwoOsJybRi1/x+SyRoW13YSZIuTIRpBTSvIln/rpMwda9dgVfoF/s6esnrDPVpYV3hPl46UQi9qSJATJhBNkjCatex6gUsim5rSJ7MWdjUl3HSeQ6WKBVZNje5SNdYlfGNPom9qSWObOSHvZWybtMnG+jzjJz1qQRQ6YhT81ZNOSBZFxvJBCm0MlXeCuggSss5prcfgv3VnH9jWE6uRTAm0Oc6oN2BdbyJjC/eyhaa7M78sQ4LNISSuTRK/xurbs1PY/GkSboqZC3hqvrJY5DHUp4jcz9ZCThidQrvM4dC3NFFF+lxAkRoQCpotmb2c0sHiRU6PtU3j+OIoEUd8wBU9g5OD9vkVLrEOtbWGlPKsfJ3X+sNUsOsZA1AayUYzlXQsYAF9VzzcxACie0wSGj+3UiUDI1Ba/o+pgpAlQxkKgaYz70IZlK70DSCZCF61wiwTPHgKQSF4A01TNuQ0ZILLeDExkiIZCA1fGoGYCEKjIqMagipKnHM2VWvrCOkWTOBMgI9BSAo/potcszW1Lg9R9W9G6BTKnngVZp4oANXEvqsT/BIfDZdikCFhXzk4of7s3GonnpXQuiwpHPNNGSckVNRlRpYm7rTe0tqs6REfVwsaayFLGfwB3W2SI7Fmej0MeZ2RVm/exMuFx06IttKLHZOVtIyHDhQOqnYg/m6EQdNsSMAF+BQizvGCV2t91IE0pGUkwVbqhCEsEhqR7Nse5Uj9XrWn60EJ7KKedWIdLYQ4N0MtJsgef9z0zfo/x7EUpkGwKaJlNTiRK+D9wxHTkIFOWomDCuNFAHJ/n0FmvgDpNga+ND3IuiBhnj1knIHFP1siUbgSKumBpIHJ9xpjRIklDc0DHBhpnmHRvwHDSOyGzWX52v9BdS9sTkEYPpdLq8+PnIzMgTkxzNcJhmVMgzuAu5kIn3j1RUehcYJtS+nUgR8nl30kI0RNyRtss02DqU1MOzjxR3YOrzkYeYIj79XUgSbx1kFPpBKmo7wH0GGxRM5W8kQk1iExHAWN+cGsIBbAtKE9sF+5bg6MX1m/aBOkL7CMCEaTccZW3h555+OiTNXiNPjHI+ZTxXrX2qNU5bh8161ndSxl1lGAsJ6PgRTBhPE6Z/UWQqpHaJBKZNYw+fJJ0bmhkjwHYF1mMj+y8xLElTOG9JBMQRtmmMMBgVybt3UyCOMIVc4I6QCogMOUcjEqDQZVEaotgvwh3qYbgsZok5l969ixIAqABsRj3v3og2c6/vqMccs8Drlb0NkPoSiJ4KknS3YG61QfI4qThgizDwYnx8TMPRyRj72JBgI2Fg9BgdMQ8jDmct0Cu7RH2MLp9yOgFFGJJrytMkoBKcjCOmfE4vMV5eqgg0803SQ53xTExqmPLEmHAAR5GNKfzieWQhspgyvSn49UUDsx2guKE1xy4VtXdpkL46HeOpnpnvgcTJi541gzJibLYyHBZVlaltyoRxZT0xe5HQ+xh6xvlW+slhb/loBz5l5i14nvht8d0sbXnMBq5gQVcpoLYLZCuLlzLMQe6OmblWid5kojePGuN0Qs1bs6ZYqMo1Diu1ZqeGU7Ku9j1THwyE0j7lCyqx9kai4huJv4ZJXH4jSffb0jHi4bHy/k+v5z+9nt9Dr2d8oajhs84FHmV4oRAF0UNy9Wl+ketPvhSv0pYrlMYRDw+ISVd6sxk+jvpq8PvRYQoRfKZd6Gm8/HA9n2vRjb7cVxpk4292y3wlvx63fzo2/w+cmLTavtGHG0lLXIr8F7otv7CeZ3tY3riw/1XT5Fctcd4O+g2L/Dt7Hr9qMXHP5l9DxG/oenyt0f5K9rvCPyRDi63i5dUsbblAHTzpzW89S7YNweKslS7HpVvPeu3cms3+A2EF7u4=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List Strict Receive Payment Paths"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/paths/strict-receive"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The [strict receive payment path](https://developers.stellar.org/docs/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-receive) endpoint lists the paths a payment can take based on the amount of an asset you want the recipient to receive. The destination asset amount stays constant, and the type and amount of an asset sent varies based on offers in the order books.
-
-For this search, Horizon loads a list of assets available to the sender (based on `source_account` or `source_assets`) and displays the possible paths from the different source assets to the destination asset. Only paths that satisfy the `destination_amount` are returned.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./list-strict-receive-payment-paths.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./list-strict-receive-payment-paths.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./list-strict-receive-payment-paths.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths.mdx b/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths.mdx
new file mode 100644
index 000000000..6ca3d8d44
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths.mdx
@@ -0,0 +1,12 @@
+---
+title: List Strict Receive Payment Paths
+openapi: "openapi/horizon/bundled.yml GET /paths/strict-receive"
+---
+
+<Tip>
+
+**Supports Streaming**
+
+This endpoint supports streaming. To read more about this, visit the [streaming section](/docs/data/apis/horizon/api-reference/structure/streaming).
+
+</Tip>
diff --git a/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths.ParamsDetails.json b/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths.ParamsDetails.json
deleted file mode 100644
index 9d9d8fae5..000000000
--- a/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"source_asset_type","in":"query","required":true,"description":"The type for the source asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.","schema":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]}},{"name":"source_asset_issuer","in":"query","required":false,"description":"The Stellar address of the issuer of the source asset. Required if the `source_asset_type` is not `native`.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"source_asset_code","in":"query","required":false,"description":"The code for the source asset. Required if the `source_asset_type` is not `native`.","schema":{"type":"string","example":"USD"}},{"name":"source_amount","in":"query","required":true,"description":"The amount of the source asset that should be sent.","schema":{"type":"string","example":"5"}},{"name":"destination_account","in":"query","required":false,"description":"The Stellar address of the receiver. Any returned path must end with an asset that the recipient can receive. Using either `source_account` or `source_assets` as an argument is required for strict send path payments.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"destination_assets","in":"query","required":false,"description":"A comma-separated list of assets that the recipient can receive. Any returned path must end with an asset in this list. Each asset is formatted as `CODE:ISSUER_ACCOUNT`. For example: `USD:GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX`. Using either `source_account` or `source_assets` as an argument is required for strict send path payments.","schema":{"type":"string","example":"CNY:GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX"}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths.RequestSchema.json b/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths.StatusCodes.json b/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths.StatusCodes.json
deleted file mode 100644
index 6f78d1d71..000000000
--- a/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"source_asset_type":{"type":"string"},"source_asset_code":{"type":"string"},"source_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"source_amount":{"type":"string"},"destination_asset_type":{"type":"string"},"destination_asset_code":{"type":"string"},"destination_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"destination_amount":{"type":"string"},"path":{"type":"array","items":{"type":"object","properties":{"asset_type":{"type":"string"},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["asset_type"],"title":"Asset-2"}}}},"required":["source_asset_type","source_amount","destination_asset_type","destination_amount","path"]}}}},"title":"Path"},"examples":{"ListStrictSendPaymentPaths":{"value":{"_embedded":{"records":[{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"BB1","destination_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","destination_amount":"87.6373649","path":[{"asset_type":"native"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"BB1","destination_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","destination_amount":"36.0841597","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"EURT","asset_issuer":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"BB1","destination_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","destination_amount":"16.2264000","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"BTC","asset_issuer":"GBVOL67TMUQBGL4TZYNMY3ZQ5WGQYFPFD5VJRWXR72VA33VFNL225PL5"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"BB1","destination_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","destination_amount":"13.9424750","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"CNY","destination_asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","destination_amount":"499.8384123","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"ULT","asset_issuer":"GC76RMFNNXBFDSJRBXCABWLHXDK4ITVQSMI56DC2ZJVC3YOLLPCKKULT"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"CNY","destination_asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","destination_amount":"498.1069097","path":[{"asset_type":"native"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"CNY","destination_asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","destination_amount":"494.5886542","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"XCN","asset_issuer":"GCNY5OXYSY4FKHOPT2SPOQZAOEIGXB5LBYW3HVU3OWSTQITS65M5RCNY"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"CNY","destination_asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","destination_amount":"490.0780598","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"CNY","destination_asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","destination_amount":"280.2909824","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GBUYUAI75XXWDZEKLY66CFYKQPET5JR4EENXZBUZ3YXZ7DS56Z4OKOFU"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"EURT","destination_asset_issuer":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","destination_amount":"63.1883029","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"EURT","destination_asset_issuer":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","destination_amount":"63.1472796","path":[{"asset_type":"native"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"EURT","destination_asset_issuer":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","destination_amount":"62.9386895","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"NGNT","asset_issuer":"GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"EURT","destination_asset_issuer":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","destination_amount":"6.7649849","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"WSD","asset_issuer":"GDSVWEA7XV6M5XNLODVTPCGMAJTNBLZBXOFNQD3BNPNYALEYBNT6CE2V"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"EURT","destination_asset_issuer":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","destination_amount":"0.0498106","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"CNY","asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"NGNT","destination_asset_issuer":"GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD","destination_amount":"25155.3452034","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"NGNT","destination_asset_issuer":"GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD","destination_amount":"25146.7108397","path":[{"asset_type":"native"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"NGNT","destination_asset_issuer":"GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD","destination_amount":"24986.8616583","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"BTC","asset_issuer":"GAUTUYY2THLF7SGITDFMXJVYH3LHDSMGEAKSBU267M2K7A3W543CKUEF"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"NGNT","destination_asset_issuer":"GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD","destination_amount":"24948.9784843","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"XCN","asset_issuer":"GCNY5OXYSY4FKHOPT2SPOQZAOEIGXB5LBYW3HVU3OWSTQITS65M5RCNY"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"NGNT","destination_asset_issuer":"GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD","destination_amount":"24930.7854717","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"EURT","asset_issuer":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"USD","destination_asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","destination_amount":"69.7123752","path":[{"asset_type":"native"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"USD","destination_asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","destination_amount":"68.9785993","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"EURT","asset_issuer":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"USD","destination_asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","destination_amount":"68.6731854","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"NGNT","asset_issuer":"GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"USD","destination_asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","destination_amount":"63.5394120","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GBUYUAI75XXWDZEKLY66CFYKQPET5JR4EENXZBUZ3YXZ7DS56Z4OKOFU"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"USD","destination_asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","destination_amount":"39.6691360","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"HEX","asset_issuer":"GCGBSZ3DSSH6PRHCOD4JXFNNZXCTKBDFRT4JR2HIAC6FQZU4YK7GPHEX"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"native","destination_amount":"1226.9231099","path":[]}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths.api.mdx b/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths.api.mdx
deleted file mode 100644
index 073d7a92c..000000000
--- a/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: list-strict-send-payment-paths
-title: "List Strict Send Payment Paths"
-description: "The [strict send payment path](https://developers.stellar.org/docs/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-send) endpoint lists the paths a payment can take based on the amount of an asset you want to send. The source asset amount stays constant, and the type and amount of an asset received varies based on offers in the order books."
-sidebar_label: "List Strict Send Payment Paths"
-hide_title: true
-hide_table_of_contents: true
-api: eJztXGtz4rqy/Ssqf7h7sgsMwQ8gu1L3YN5vgnkPqUTYSvCOsTmSSCYnlf9+q2WbQCCTTHZOauYO8yWDJbXU3atbsqDXg8TxNZNOvkodzOdMOo9JNmEWdZbc8T3pROrNCfrKOHUsjhjxbLTE9wvicbTEfH7+Zc75kp0kEja5Ja6/JJTJjBPXxVT26XXC9i2WsDHHCbx0WGLuU+c/vgcf4pRcEUo8iyQoYf6KWoQlQACGiVnCn/1NLJ6AWeLhlPFgGXFYxhEinr30HY8j12GcIT4nYkkM4fUSLewhjm8ImmFGbOR7ohde+CuPI/8KYQ9hxghH9/4K3WGPI+4LJWUEagerCruEoxjH9wxZvsc49ngMYc8WQvn9kogPe6RTYhHnltjoFlOHsKfV+FdXhDLkBOvyqU0omvn+DZOn3tQr+RTxucMQI5ha8xiqBNZDro9tUBMUFxPBLGABzIUgSixn6UQGCGdHX9bTXtqEcccThr7AlgULvkQ+fdYgpF4eCa1shy1d0FyY2WfMmbmRva+ovxDPbedKuJRvWY6BUUXzk/CgRUZtz70PpYjVM8wddnUvul8GQi4Cg14iTEEzvqIeseWpJ8WkNVqqtnQiNRzGTQEQk3h2J4BAAOqYtMQULwgnFKD+IHl4QaQTKZoBFnMBHpRikgOg//eK0HspJlHy75VDiS2dcLoi+0JD+P1KeGobMDIqOnxOKLoElW/JZQxdWpTYDr/A7nKOvdVCvYwJqz97fJy6lKWYxKw5WWDp5EESKzuRAP3etRSTiLdaQMQGgqWY9Fzu7qPjlHT++Bjbr7nD2IrQl3W/wi7bq7wZRDrCtk0JY4BFMEMgL/q0bZRuKBU5V9teXvvgEjkMeT5fG+4VY3zDi6ULj8qF5tlZq9ZU+430WTWn6510N9WZVJpn1dZwYjTTaaNoNCuN0qig1Yr9XKVcS3fV2kR60TCWb38HEi+aBYa9gIn/ovp9s7BXExE+Pw7spzz2XIswVOf+yrXRjEDC5G9dpLa1xD156ONQGOY9KqOcd7/OHCLboMWKcdhA0J3D50+J+vsZVEZ95njXiIRxHRl4M4FuupNdIsyEcHq9EvuRw1Ckj8DH9rbK59HGxT4V8rtJ/wedkEOWv1jgOCOQZjmxf2xn+gEHiZ3SYUK+jIrYmkcNDAy6wBxmxwxd5tuF4knVNPvF7kUun2/3W71LGcGWGlrvBF32zcJJudCvN8v9cmFyVtfHlXFOm+i5caqsjgrmpGNOFHOo9VtKrjtotvUzs1sYdrRxozi6/AnRkG+NT8q5brHY6BuqUu1WhsWcmS8ZjXql382Xm5WiVi3pI7OYLo4KjVx+XCl3K01V6ZbaI+nx8TwmfYuz1XLpU87grEXwAqYIUwQlbOl7jDBYRCqZhD/bODBXlkUYoMfyPU48Dl3wcuk6lkBX4m8G/R52lQkOe7BPU9jUuRPMckEWM2LbALzXulJi+dRmGx0xpRjA63CyYK8L2D0L7Nj6MbZne3i1V7i77vHcEuBKwXLlr7n4JBnPnj9o2qMUk7jDhUfDlLYpM0jn+2bdieOX1djt+qIuu10/SKEtwS9rBZHwfq++YodXdP9AfR83s+jXzXWdP/XOwdN4Snp8fN5/30n1+Qb/gv/3Wjq063kwUzQ/nJZB7zClCAt+51h98iDdYndFdkJ1HYxf98bVvvPqnsCSjG7jeUvkC6lcGNTHqXI/VeiOhj2jOK7VhmZpVC0bk4Gem7SMwcDsV4qdSVVTG1VTN3LpwmBgdnbsdiKpyaScDP69bMW9i34pjCTDON7bvLF8raZXGiVN1/WRmps0eqXeqDFW9ZpmDtPFUbduNIrjTq2jKKaiNEeT8kDPD0ut/d48kTJpWVfSiq5mI9eC7bfWH74tPJ7D1n/wymd4RdHlZEY91rLpV70Se/Z8j15buhT73Z70PENJ5VxHaxR77YE+rhb11DjX1HSzV8i1Ot1COz0pFYyy2arUzqrjcrluNtuTXKXdNlPmARWfiIpjXU6ldDVQ4WNRYfTye0BhDNoNPd1r9s+MckPtTcat5liZnGnD8tm41CkVtEGtOxx106lBTlEGpVYjldI6De0Ais8EhSJn1ZSa1j4eFHAxsAuKd773/M6gyLfGr4DivS9fL4BCzWbljJJRj1PKx6OisW//yKf1brPUao2MUsGsdY1RPmcMG5VRoa5We4Mzs1nV9EI+NakN8sq43Wh08vU6SDqg4jNRkZGPk3o2+YZjxcEtn+gWVdYyGV1TUx8erKN8a1+wtsZaezQ2x2qpXml3eimz0z6b5NrFanlkaA1jPFQqg77SHpq9s2rP1LWm1gWzHFDxmahIysl0JqllM4eN/YCKUIdUJimnsslsJqV+EiqM/rifq6a10WhYmBTrjbGu50vj+lmn2NNqXbVYbI0mRn+ijEeTdMHU9InarrdL/d8ZFeEr9ndh8c7X7RdgoSvycSajJFOv3+IccsVvhQo1nUpn9cNx72dyS0rOKhk9k9U+PFhb5dbey71hu5Drtps1RRlo40JprLQ6415lMD4rp5u10aCWahWUXLtcrYy7w2qraOq5fL5TOMDiU2Ehp3U1m3nDRfyPomK4P4Wbg2Exlx4N9KY2ajXahUGvky83c7Vey2hMjFG71DorKEar0xrnGsWx0erp+WJqcADFZ4IiKSfVbOY4+XoG/1FQBEfXjzqu/sagCHPud0Hxzvz70kuAdqxpsqJqqaTyWa8BhwPfrwEMVZfTx8mMcrji+7k8o2YzupzRj3Ut8/FX8vu/vcv1e/3xONWrNEpps1ztFUrNUW0wriiNSsFslou5umn0U3q6maqnc8pQU5V8vV8sHYDxycBQM3I2nVEz6scD43D9+ysDQ0nK6Yympo8PvwL5eZERHJe++4X/O49OL70nZuX0cUpJa69/W3Twyud5RSRxLZv9+CR+iNVfGRV6WjnOaB//mna46vt1UaHImpJVj1Of9ZOtw3d4Pz8olKys69ljRf94UFTErDtvAWXDnCgF06zonW4l3y6otVGp1ZqM8r26USh1e2qtm6pUc3m9dDbpq+N6utyp/P+70fGiWtj9v65MpXQ5m1KOk9mNe/nzR1H/ENRAfIuDXmZU+PD1QXIxFD9J5py47nphYJ8VdVFU9x5WtMc5YdwjfKv4XRQ2JzaK1v93Op16OyY/fW7w/9npBks7NbqN3ZbA5KfvNfiWQGGtUzWZFE/3FGeelnPwo79GvzopqoVJ0zBSE6NeNvrGpFFtj/v6qNQYKumy0UkNJgUlZ7RG+aFqDHJTT8A9tGgN32JT1I1JMcnFM+JKJ9K/Qsslwr9xZt9sWv0W06jS07Rv0GlUO/dlunfoVDr6a+rBIEboLaHoFHnkbkOCHFbTy6Zo/zL1EJpKb3DrVIpNPRA+9QLRMFJmGyUyfM6EOPR8SlHfEzbBbEa3IaRFn9/rxbWQo/DvFMJm/XQqvdtvgYgjoaKFXfdL8F8+J96Xq5VnATrQFygNPEIPwWzAjeC7RHb966DhL3j+GMng1nxjJKF0ZyCh1KeiJRz51zZ8Ovd87nsb0Amdc/EMMYKXYKMNOQsobUSBw2NIeCNyIjpFERDeBoIjAEBUE4lOQ5iFOLiAaL9YbiBhM2hPt3Gwi4R/hoVtKGwH9zYwNkL89J+AZOodrdEx9ZbU8fiXyDRH4LxzqCnjxGNA7SGS6w25l07215vGoqoyqDuFoQvC5z5QPFyTdeXaibSbXsH5wgvBFCsK4HiDM6V9VeW9oB9qEX7n0xsBwP0Sr1Z8RclbZJainsiLpJ5DqfWVL6oLwyq8MDGBHQhlweiknJShIoGtFgtM7596oSX1bx2biNLiSq/XQblOFRg3gHQlYhaJKuTDWWVUhVLqawK8KcDuQUlcGC6g9xAjl9S3Vxax0ex+nwiQjEXJdVDc7TBEMHMIhakhkFcLEg3Ft4Tia4I2KoERJa7YsCNukCWhon7bs0jcp1AhTuxgIZQsKQGKgYAXBq1YsKhoQXmfEqBrcZjQfEOPGXXsa4JmhN8R4sH0gbbbIzvUh8pRqCm/IegOuy7hLIZsYhGPU+w6/yE2It+sOQaDBYQvIopDmguxojU1C/DHrGYLhyNOscewSHMshkQlvaj+DnZSNMMuKCsIQALoI3ILxd7BOjZHg9CnkfIOsn53JHzddOirjEThshOWT0nc821y9FuhBxJ0NB1wMMwINBEGtrx1MLL63UYMYTSj/h2DXdKnyPdIRKqxtrVZqLO3sT9x33dZgtk3DCztI0oATkKa5cNp+5vD70H+vb+igDYwaAzdCbYIf7EAOgTgZwJDYQ8mRo7HOME2DFrgG2BhsB1KLC58CBtRQKAk3Hq9cmzBPWRRZ0YYmvt3wiT2wvEcxglFEcQFHCPbOILgySJwuLkKwCz0L6w1/QMZrn/9ZIO7u7tt5dc94zPXv07guEfu4mzlxWEXmpN4uH8cBeQPPoQJtm6uqb/y1lxVG9EQYIdac4cTi68oduFAQ/1bIkgiAg85DC3w3z5F4daBZqvF8iggvoB9BigyBP/SzF9xFC4RDBjOt4aGbxPgi4oha06sGwS9N/UXBBZlMO2TAa4dPl/NZMtfJJ4fyCPer5nrzxIL7HiJQnFQbLQ71VZZXthHwl0GufIpAcfPyLXjxZDD/2Dozqd8jihxuCB78q4DPhricUcsglhzH/h0gvV/hbBELd9+TyJAtm8Jag5hoxP05593BNm+YOMhnu1TRhBdeR4sIjIUuCxIQxi4wTwbuxAum1lijaU//wwSAGFLYjnYde+FaDH24ha7ji0UvNjZ2whAnxLE74CeLCBZgdxqEeqFScUmlr9auqF9FpCGg+MusJoBwGa+MKPr4JnjQsTBqA14yVvQh+haYA9fE4YcANedF0NLTIkdt/07bw0v/2pbVX/JnYVIejBnOBKSGqQ8/wp5hNgMfbkjf7gu2ogshwl2FDSV8ngptgMQN5XWtjsKKL84oQvWvoKjuiMO+ZGTNz0rOsX9K7GVQbeAkARbgmEiZL2Jlr0J6BKEnnC+FHt22Ns+2pEFdkQrcV3/X5ttjzHJdSziMbIxV26JrTlBKRmuMBwbsHvliIuSoCUetDzNGKYTLFqFTqFQlmhU88WWWYQh8pwvXEEtsfQZX2BvY0qgbUABbwOCt1IUMjegiBFt6wzx8MTYciD8OxD+/ayEf+FdHyffeGLpYgeuBYKoeYju9MRfwPfme+F5TJr7jEPzwwNYpU/dx0d4HDBcwdui7TA8c1/iuNoMkC8RidsR+u8yAO5VN3hx3scHE741S+JV9e3qfC6R31t1WnMS/gOtPp6H762rD4kD37n2ZwD7cSa+NywzogH6eND86rx73zHefr7Cd5rwwJr38/iShayHT648hw/UAV+Kb4pi0pxgG85s68vLnGWR5SYAdqjuti4vy8We9Pj4f6FfaAo=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List Strict Send Payment Paths"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/paths/strict-send"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The [strict send payment path](https://developers.stellar.org/docs/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-send) endpoint lists the paths a payment can take based on the amount of an asset you want to send. The source asset amount stays constant, and the type and amount of an asset received varies based on offers in the order books.
-
-For this search, Horizon loads a list of assets that the recipient can receive (based on `destination_account` or `destination_assets`) and displays the possible paths from the different source assets to the destination asset. Only paths that satisfy the `source_amount` are returned.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./list-strict-send-payment-paths.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./list-strict-send-payment-paths.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./list-strict-send-payment-paths.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths.mdx b/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths.mdx
new file mode 100644
index 000000000..cef405b22
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths.mdx
@@ -0,0 +1,12 @@
+---
+title: List Strict Send Payment Paths
+openapi: "openapi/horizon/bundled.yml GET /paths/strict-send"
+---
+
+<Tip>
+
+**Supports Streaming**
+
+This endpoint supports streaming. To read more about this, visit the [streaming section](/docs/data/apis/horizon/api-reference/structure/streaming).
+
+</Tip>
diff --git a/docs/data/apis/horizon/api-reference/list-trade-aggregations.ParamsDetails.json b/docs/data/apis/horizon/api-reference/list-trade-aggregations.ParamsDetails.json
deleted file mode 100644
index 22576af72..000000000
--- a/docs/data/apis/horizon/api-reference/list-trade-aggregations.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"start_time","in":"query","required":false,"description":"The lower time boundary represented as milliseconds since epoch.","schema":{"type":"integer","format":"long"}},{"name":"end_time","in":"query","required":false,"description":"The upper time boundary represented as milliseconds since epoch.","schema":{"type":"integer","format":"long"}},{"name":"resolution","in":"query","required":false,"description":"The segment duration represented as milliseconds. Supported values are 1 minute (60000), 5 minutes (300000), 15 minutes (900000), 1 hour (3600000), 1 day (86400000) and 1 week (604800000).","schema":{"type":"integer","format":"long","oneOf":[{"const":60000,"description":"1 minute"},{"const":300000,"description":"5 minutes"},{"const":900000,"description":"15 minutes"},{"const":3600000,"description":"1 hour"},{"const":86400000,"description":"1 day"},{"const":604800000,"description":"1 week"}]}},{"name":"offset","in":"query","required":false,"description":"Segments can be offset using this parameter. Expressed in milliseconds. Can only be used if the resolution is greater than 1 hour. Value must be in whole hours, less than the provided resolution, and less than 24 hours.","schema":{"type":"number","format":"long"}},{"name":"base_asset_type","in":"query","required":true,"description":"The type for the base asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.","schema":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]}},{"name":"base_asset_issuer","in":"query","required":false,"description":"The Stellar address of the base asset’s issuer. Required if the `base_asset_type` is not `native`.","schema":{"type":"string","example":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}},{"name":"base_asset_code","in":"query","required":false,"description":"The code for the base asset. Required if the `base_asset_type` is not `native`.","schema":{"type":"string","example":"USD"}},{"name":"counter_asset_type","in":"query","required":true,"description":"The type for the counter asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.","schema":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]}},{"name":"counter_asset_issuer","in":"query","required":false,"description":"The Stellar address of the counter asset’s issuer. Required if the `counter_asset_type` is not `native`.","schema":{"type":"string","example":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}},{"name":"counter_asset_code","in":"query","required":false,"description":"The code for the counter asset. Required if the `counter_asset_type` is not `native`.","schema":{"type":"string","example":"USD"}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-trade-aggregations.RequestSchema.json b/docs/data/apis/horizon/api-reference/list-trade-aggregations.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/list-trade-aggregations.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-trade-aggregations.StatusCodes.json b/docs/data/apis/horizon/api-reference/list-trade-aggregations.StatusCodes.json
deleted file mode 100644
index 87ba0896f..000000000
--- a/docs/data/apis/horizon/api-reference/list-trade-aggregations.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"timestamp":{"type":"string"},"trade_count":{"type":"string"},"base_volume":{"type":"string"},"counter_volume":{"type":"string"},"avg":{"type":"string"},"high":{"type":"string"},"high_r":{"type":"object","properties":{"n":{"type":"string"},"d":{"type":"string"}},"title":"tradePrice"},"low":{"type":"string"},"low_r":{"type":"object","properties":{"n":{"type":"string"},"d":{"type":"string"}},"title":"tradePrice"},"open":{"type":"string"},"open_r":{"type":"object","properties":{"n":{"type":"string"},"d":{"type":"string"}},"title":"tradePrice"},"close":{"type":"string"},"close_r":{"type":"object","properties":{"n":{"type":"string"},"d":{"type":"string"}},"title":"tradePrice"}}}}}}},"title":"TradeAggregation"},"examples":{"ListTradeAggregations":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/trade_aggregations?base_asset_type=native&counter_asset_code=EURT&counter_asset_issuer=GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S&counter_asset_type=credit_alphanum4&resolution=3600000&start_time=1582156800000&end_time=1582178400001"},"next":{"href":"https://horizon-testnet.stellar.org/trade_aggregations?base_asset_type=native&counter_asset_code=EURT&counter_asset_issuer=GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S&counter_asset_type=credit_alphanum4&end_time=1582178400001&resolution=3600000&start_time=1582171200000"},"prev":{"href":""}},"_embedded":{"records":[{"timestamp":1582164000000,"trade_count":3,"base_volume":"399.3873200","counter_volume":"25.5368082","avg":"0.0639400","high":"0.0652169","high_r":{"N":652169,"D":10000000},"low":"0.0638338","low_r":{"N":8107550,"D":127010393},"open":"0.0652169","open_r":{"N":652169,"D":10000000},"close":"0.0638338","close_r":{"N":8107550,"D":127010393}},{"timestamp":1582167600000,"trade_count":1,"base_volume":"149.8415320","counter_volume":"9.7149804","avg":"0.0648350","high":"0.0648350","high_r":{"N":5000000,"D":77118803},"low":"0.0648350","low_r":{"N":5000000,"D":77118803},"open":"0.0648350","open_r":{"N":5000000,"D":77118803},"close":"0.0648350","close_r":{"N":5000000,"D":77118803}}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-trade-aggregations.api.mdx b/docs/data/apis/horizon/api-reference/list-trade-aggregations.api.mdx
deleted file mode 100644
index 2e57f935f..000000000
--- a/docs/data/apis/horizon/api-reference/list-trade-aggregations.api.mdx
+++ /dev/null
@@ -1,76 +0,0 @@
----
-id: list-trade-aggregations
-title: "List Trade Aggregations"
-description: "This endpoint displays [trade](https://developers.stellar.org/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools#orders) data based on filters set in the arguments."
-sidebar_label: "List Trade Aggregations"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWntTHDcS/ypduioHUsM+eLMp6o4Egp04QLw4iW0o0M707ihopImkYdmjqLqvcV/vPslVSzO7sw8wtomvcon/wTuSWt0/dbfUj1vm+MCyzjt2aniCsDcYGBxwJ7Sy7DxiCdrYiJx+sw47TYUFVEmuhXKQCJtLPrLwztHa86XUudx2ms0Er1HqHI1tWIdSctPQZtBMdGybErlRzX6hEp6hclzaphS/FSIRbrSi1Uq5YMUmeLMyGcm1lvZv2iRo7DIk3HHocYsJaAV9IR0aCxYdCAUuReBmUBB52zhTZ8qzLSwkWiH0RpCIa5EINQAOA3GNCpzIEAxXAwShnAaLA78auEqAV5CoAVjHnbBOxDaCvjZjAtzS5jkXBpaIrwhiXSiHZhn0NRpAHqeg+8SbxTH5kjmEpDAe8nLKZH9hweYYi77ABIbCpX740qDVsqAVl5BzwzN0aBpApKzjxnm+USUVvZp83GDJc28El372qcjw0i+5RJWEXwZpXyeuUY4iGKYiTv3SnnYpGF2oBBNw2lNXyA1aB1khncgl0q5TLFqhYgTMdZyORRbKn0LBZQ1tg8Cl1cClGKhK4oqsfZAuvOjDSBcw5MoRY3HqxXV09J4cbRFNoxtzBT2ES93vW3SXhEhAe0RnTVPDSA3jM8UiRqrtz+tFwjrspbDOG8+U7URsvIjM65YpniHrMI/4BR0Ii5ggo/qtQDNiETP4WyEMJqzT59LivO0hSD1EE06zR2fAzQgM5gYtKocJcAuZkFJYjLVK7BRALGI2TjHjrHPL3CgnZoRyOEDDItbXJuOOdZjUasDu7qIxw6iSj2W3yPPPzu5EPz6C4VIzJvb4ALcN6BZ5rg0NXXNZYNDfNmRCFQ5habPVarWWI9gov1hYWmuV39q1jzvjj5DqwsDS2ubkS8JHsLS9uR6+eCNtwxDxiuivb4fPHwRWxLTC477XyVgr61jH7zeLRyUII3DLiYH/2ZljWepTdxZObS+cWwo8zwHhUZ9YATE/M+Gj+sQxNvMzCTx2d17XmWDlH6gv3RkvUrqKwgbfIWzdMx/ckB7RfSXUjBZ9wxVoJUdEo/Azgs+eKDLdAgOD3JExpVyVitKAn0jtICuso8VCwTDVEv2gjUCitWE+kcuNvhbktCd0I69Ok2mr62HpQnVSRdZ7j+nRxXfhb8ILv+hePJ0pFpofrfLXKjFM1MK92oAD4VI0cKk43UiXEVzGBhPhLrjMU66KbP0yAm3mPrdXLxcKY50R3hRQFRk9fgJhFrFZuvOf2qvs/B6phbWFx+hD/U43PHqAJwmpSXVtTyD4z7/+TY8BIt+AVyXBSlMuZ4C/JIVR2o3xeg8GNzzLJX063H/9/Q+Hrw/33/74/eab52/2Nt5u7r1ZPVz/Zb/79qT7dq3788bro7W9Vz/9cLz5Y/fV/s8nG29eHvxynxbEOvmYa4OWLVSD303w1939KRnKx9vTKXNJ8I+gz9OyP7VKTwHxsFbPH8L/VrGn+XkK3Z7Rit8TgVkN95HUB/K/BwlaMVBToYonFO4eihEMxtrQUy7VhUyA5zly04BjT8OCULEsEoRLbuNLWOI2RkWR2LLXdtruEpboT/nZP+vDG76M6EBY9Z9//dtRtBeBcJBgnxfSWXr0e7KPsxBuYxYEnFZ/KTLxoU8BOtiM34isyCDck4ROBYVBVxiFSYjPPH3/ZgjxWN/oDNrE/GqrBSvAVflsDhNdyklkSLlJSHf8A+K5NuKfFPhqAzkafyPTy9kgt1rZB0CrDhCTOezarfc8I8fK1G7d3Z0TKDbXyqKl2autFv2ZeSIVcYyWYqFYK4fK0RSe51LEXoeav1qadzu/q+79ijEdQ24o2HIi7HKBWQ+ThA7ifVNL9GsTuTGcDlM4zOz7CVDYYh3P8nktuouYz3hceANdOO5vpmstC1KqBeOVaT8whV8PFn5PxSC9d+DCvF8ytXB1suArCSqcdyBe4BMjYgoImNTDhUSkHn4mDnSOi6nQwGfiIZba3nO8NPJZuAj/JmOzmQgiV1qu33BxtqJzy3wM641MCnXlP1mUffqbGuyzDqvSe2lwPysOrVPopnJ8wS54jfbfZx5pu+HmejZ/ne4evH51+mzR+2P3cO9k4+XB6fFPm29eHGyuvtn7YWOze7q/d3Tyav946+23+18fdo+ef/fjizeHh993fzh+u/f8+Li72n02f4Xuzj6Jnk0iot0yEn02ydLstje2V9sbmyGcfFZlQ8LnrW0fj7YJZIU37k8A1mIAHoPhVnvVDxBYucHrGlheu6ec+9h9v5vyxJ5QmQRozXjhtRmvy9Z2dhpr21trdDfNe1y2utHYWNvcbm2vstLZslajtbm2s+7nBzfrP22stjd3WN3BHrFO+BqxfboQw7/KMQY622tr26zmEo9YZ7vd2trYaIVFq1utdmttZ23szKb2mrixe/cq3c/UbjXHc+9+9NqZw3RrcxGm7VlM2+s7je319sba6kJMdxpb7fWd7db6FKTr22sbM5DWP43Z3ajOdZ91trba7e3t1toUptWqOqb3LKpBWq2agvSeZXVMq3XTmC5cSPmkyhPfrJB9diuX++6WSa4Iim6KUtIbSxcm9hFFYSTMOIr3OYizszN1j5OgofscxfzYpzqLeYqLHQbNW+Ad6PO9XpYGFzqa1pnyab4S0e/4Ne/6BycpBe+hZB32jxLB5qSUdFVH/ZqbKjrtJlewC+Xrfuls4dIztvzVmaJFFg3VcnZB4bBGoVE+xxtdP750pgDOHuP/z1h0poh4IO8zHXPE93xsGE54qeKkChwXzy45oHP3W9CPjz3mMY8egKpaBLswdWDleFk9qkarMytHawnNXSjVoBwqc6e70PJoBKCJ8YabeapMV9eiCUtRtXs0leEMlJc9rZhLuRT+61JUS/1CxZ6dJQplluGWhgAohawlNqQehIGv6PtdRcPFaW0lGjO3EI3Rxo+UK78irT2PWIYu1VQyGvhsc84ducMFVk7q6jEI/qMw8nEvCrYoMj0N8+AI3VCbK28/iyn2C1cYfAzNb6uZoCqq5xQz93UIncJbtDQMFjESJaxuNVqNNslXZBk3o8msKkNNRVd4fnp6AnsnLygw9cXesq5bZZXKXRvwgkq+A7RlrdbgigfO+tl+ZW50UsSYUHVvAQmizCmSzsaxNnIrKNWu/YkWGVZL+TUaTjXUSQgLBqW3zaoYWovHV7QRoXTkGRnXksIZh2R/bzRm6BttkHIEwnrJa3L0jEgGCD10Q6Ric54HaadXnhhNIYYFKa4QhlxKdDaCBGNUznAp/okJ4E0ojNqQ/A9163AVeI7GuQWqghc9n4IwXFnu9d1G4FMidEQ89kYIPS5JWJ+vtM4gzwCvfWHE81FfTUQnKxtzmvVn14R39QN9bztFyXYz1gZXlE5w+U+lPXRRVNuVJTju001UjxUc4tevXkbAoWf00NJVoQ1Q/0eZtxxj3d3/3j6udcVRD0rTJleWkNZgkNSpzOTSa+9GuBHRH1EZNw+ARjBEnwrMMmrIoBYFAoor2hiEsg6579PI+BVVDhNhMHb+DOm+qjWwDAqRIASL6aGFVA89JEkmlLA+j1yquFfHChvawmcHlwz2gzJ7+ffHkn4BX0s9mGAwHA6nhR/PXOlJPWjyFYXDFVso6tdxKa6U98eyT0haTWbC46uBbxOhBp0Zawi6Y+JUOIxdYbgEkZHNYyio6jJ7mfFftYHy6oBekeXLDfhWU7Y5FCHpM+/pghKZnkUCsNxvrBo6wfLNkGJ8BTS7Lr9Pjx4StBMABsKlRa8R66w5+yAsRW32pO41My5Uc//gp4OXxycvjg4bWbLsj+tr7GuDdPA9HAhFqdYvLAy1od4ZFM53j5QdJuQGhGcC41SH/K7nj8wSjvQj+qrmHQEkOvaJX49RB778coiQaF85QJVoYxFMoRQxUQFFRxbcEKdXlUq4JHOpe4mxLn35ZXAAvklIcClHnrRfe3HNpUi8gBdzdxt1P1GXhBtSkxUVyB0Zj4rRqNKpJBjrIpclPhm5YZFRnwU19pCChRYklIL3hCSLo1U19WpMqT5ZV8YVH6AFQco1VBFV5jFZSfRQjdVL96dF1bkTmXd6tGe5kpwauTzdB4WYWFga4hdSQs2yKOtugcMZ+4bn/jogcmdsjN1y6CFyaDJ73KeYQfiwpDrkqfiPJq3ovr/KaFrIpPPYZ5rKikXFdl2hv/XtNmUXzPRjb/pphxkXfhSl1P+oj1HgLWJUIcNZ7rWX8zhFWG1QXCwS0t2+QDMeWQkjkx1Ld8L9qJepJGqbL198c3DUPaAljdRl0ieBcm1dxlVtS0pYwoLmxJnHw+2kxvBXm+JfbYp/tSlGVQHB4Y1r5pILXwvwpnlbxp7v2ILY8zxiqaYmqnfs9pa05LWRd3f0OZRDKSJNhOU9eV9BdNoWP7ltcaEcVzia7aYsKxjMR7gfxuEndio+wGGtffIT+PsDNyY+gM1Ur+ZHovP/3Yb3AHjjpsWPBG6pajdZht+z9+4BCeb7BT/BQj5DC93jRBl3TH2CME/bAfc4vsuGpt9Bm562+e0BaRa27T29Tj19D9ujZXpy5XqiFrRHC/BpWvYH6kB7yHOXvXefcIb/J91mD4BU9eFNQDqnH0YQSqzz7pwanpATkvQgDYv24hjz+qq5ZrOpMszhwSm7u/sv6AIPLg==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List Trade Aggregations"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/trade_aggregations"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint displays [trade](https://developers.stellar.org/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools#orders) data based on filters set in the arguments.
-
-This is done by dividing a given time range into segments and aggregating statistics, for a given asset pair (base, counter) over each of these segments.
-
-The duration of the segments is specified with the `resolution` parameter. The start and end of the time range are given by `startTime` and `endTime` respectively, which are both rounded to the nearest multiple of `resolution` since epoch.
-
-The individual segments are also aligned with multiples of `resolution` since epoch. If you want to change this alignment, the segments can be `offset` by specifying the offset parameter.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./list-trade-aggregations.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./list-trade-aggregations.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./list-trade-aggregations.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/list-trade-aggregations.mdx b/docs/data/apis/horizon/api-reference/list-trade-aggregations.mdx
new file mode 100644
index 000000000..888cb35be
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/list-trade-aggregations.mdx
@@ -0,0 +1,4 @@
+---
+title: List Trade Aggregations
+openapi: "openapi/horizon/bundled.yml GET /trade_aggregations"
+---
diff --git a/docs/data/apis/horizon/api-reference/lp-retrieve-related-operations.ParamsDetails.json b/docs/data/apis/horizon/api-reference/lp-retrieve-related-operations.ParamsDetails.json
deleted file mode 100644
index e5281cca8..000000000
--- a/docs/data/apis/horizon/api-reference/lp-retrieve-related-operations.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"liquidity_pool_id","in":"path","required":true,"description":"A unique identifier for this liquidity pool."},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}},{"name":"join","in":"query","required":false,"description":"Set to transactions to include the transactions which created each of the operations in the response."}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/lp-retrieve-related-operations.RequestSchema.json b/docs/data/apis/horizon/api-reference/lp-retrieve-related-operations.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/lp-retrieve-related-operations.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/lp-retrieve-related-operations.StatusCodes.json b/docs/data/apis/horizon/api-reference/lp-retrieve-related-operations.StatusCodes.json
deleted file mode 100644
index 5f58778ae..000000000
--- a/docs/data/apis/horizon/api-reference/lp-retrieve-related-operations.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_links":{"type":"object","properties":{"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"type_i":{"type":"number","example":0},"type":{"type":"string","example":"create_account"}},"title":"Operation"}]},"examples":{"LPRetrieveRelatedOperations":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9/operations?cursor=&limit=3&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9/operations?cursor=120192452165550081&limit=3&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9/operations?cursor=120192344791343105&limit=3&order=desc"}},"_embedded":{"records":[{"id":"3697472920621057","paging_token":"3697472920621057","transaction_successful":true,"source_account":"GBB4JST32UWKOLGYYSCEYBHBCOFL2TGBHDVOMZP462ET4ZRD4ULA7S2L","type":"liquidity_pool_withdraw","type_i":23,"created_at":"2021-11-18T03:47:47Z","transaction_hash":"43ed5ce19190822ec080b67c3ccbab36a56bc34102b1a21d3ee690ed3bc23378","liquidity_pool_id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9","reserves_min":[{"asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","min":"1000.0000005"},{"asset":"PHP:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","min":"3000.0000005"}],"shares":"200","reserves_received":[{"asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","amount":"993.0000005"},{"asset":"PHP:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","amount":"2478.0000005"}]},{"id":"157639717969326081","paging_token":"157639717969326081","transaction_successful":true,"source_account":"GBBWI7TEVQBPEUXKYNGI3GBAH7EHFEREONKK3UK56ZSLJIDIYHQJCVSG","type":"change_trust","type_i":6,"created_at":"2021-08-04T20:01:24Z","transaction_hash":"941f2fa2101d1265696a3c7d35e7688cd210324114e96b64a386ab55f65e488f","asset_type":"liquidity_pool_shares","liquidity_pool_id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9","limit":"1000","trustor":"GBBWI7TEVQBPEUXKYNGI3GBAH7EHFEREONKK3UK56ZSLJIDIYHQJCVSG"}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/lp-retrieve-related-operations.api.mdx b/docs/data/apis/horizon/api-reference/lp-retrieve-related-operations.api.mdx
deleted file mode 100644
index 8861d299f..000000000
--- a/docs/data/apis/horizon/api-reference/lp-retrieve-related-operations.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: lp-retrieve-related-operations
-title: "Retrieve Related Operations"
-description: "This endpoint represents successful operations referencing a given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new operations referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known operation unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream operations created since your request time."
-sidebar_label: "Retrieve Related Operations"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWv1y2zYSfxUM/2iTjiSTlER9zHTu7Nixnbi2azvpOYnHAYGlhJgEGAC04no0c69xr3dPcrMgKVG2kiZpc+e7nv/RWFosdn/7gcUubj1LJ8Ybv/YOxPtCcGFvyLFSqfEuWh4Hw7TIrVDSG3tnU2EISJ4rIS3RkGswIK0hpmAMjEmKlKgcNEV6QzQkoEEyISeEkom4BknSxR65UimhkhNGJYmBFAY4EZIYq4FmuCZTHDrkdOV/QtNUzQy5UQWxiqTCWJAkUZpImH1sc4ty393ZEDuFG0I1EMo5cGRnp0BOLaQp1SQFPgHdIfsJYTRN1wnXIntKi1+VJDORpsRYqi2h1rEBqlMBxpIrqWZyKRkpZArGEEpYoY3SRBhiwLaQ+2wq2JQwaoAI2+SZaJURO6W2WtQhWze4ypbaQc3rmqYFoCJSzVoOIwS3FLoJDtNALXBihGSAdJpoeF+guFZk0PFa3oJ6n3tj7+D4BKwWcA0nkOLSowUzr+XlVNMMLGh0o1tP0gy8sbcA/BIBvxTca3kC3Sinduq1PNxRaODe2OoC7vraJimkeF8AERykFYkA7cy8xpYdb95a7FoiUW/1vgB9s7JXQlOzZjNZZDHoEmPn3gZhpMTkwEQiGEkVK+0nJNpOpSkw979KiAaTK2nAOH8WhuSFc5jKbEByOhFycmnVFcjKSCohlGhgSnOE27ApZNQb33r2Jkc9hLQwAVQEPtAsT8EbR5EfRcGgNxiO+qPA788baivN4cu15mDERNJaDxTVMVo6YymhIWaqipQTmudAdYcc5aUjCcnSggN5Sw17Sx5Rw0ByISePidLkLW73ljzCj+prF07OhFRPigykJcLIf/79H7YKAks4JLRIS/wd27XwGKuFnCA6ssgweVHDvFJB76IJTCoyYb8QmLMpkIx+EFmR1Y7hrFxCocEWWgLvEKRz/F2YaSonUNo8QOFD3ydtQiUp8hx0RegcTBgypZozxcusUmcR9O8cdKJ0RjEwNVCjpPkEaLUBgd/DLvA/168CvwlYZdLLhIoU+BcidwrW5VFdpqHaPUpezQwkJEYNynrfmdxqjCS3xVotYqVSoHJpf5dCHP2K9d8pIb9WBSoNZaVkDVUwRlZ+q5J2lVGBsukilFbUxW/qRNHx5hct70PbFHmutDXtxblSJ8NFSkGlQ9/Hjztylmeu1/KYkhakRRKa56koE9XGO4N0tw3waJoeJS5FVzCq+B0wjI5co7BWlPtdpkJemQbcH6EzkCa/TTXVkKyLXOfm1oWovPLmLc9ClrvDZY2h5/Om4V6XTC9anhU2hQYPCR/sAxMp13D9oESaI1n91YEzNYbMH+MTkCTA7GcQ/rttwIDDQxPrAQaQK+X5QwOqkXEflGRIJfi6zWo6wZ3/NQrAT1Gv0KGENzlcisaKshxpnt5+Rba2OKqJvPJ8uqSMqUJar5kBFqW8N7+YL9Y4JD9V9o9vPVfJriaH2qNLG3hTa3Mz3tiYlhVO24KxEmzHlJesjtKTjdV7gtmIBmHksx4Lhv4gDqMwSYb9IPZpN4GgFwSj3qgbxbEfBv04TAaDXm+QBDwJgtFoCDSORxvLc/cv5W3gx+9c8fVj9ztX3f6ItWLjrHhYsgahH4zCXj8Mon6/7/vDYL309bHyEKXv9nqDUdDtdQO/f0d6V6Gj+11CFgNevFGJqrZ2tQnGk9eNRoPeIByFfhQGfn/g3Y2hdRSNLHG5bEnUJZVRhWbLEBh7u1tbvWenZ93wxS/Pjw52z89Pn+ycb+1tPTl6ehCe7W7tbb88+unVcS8Kd856r062ey8ONgen4YFXB9zdK+5M2CnXdOYtAzfstqrY45cu94R+GLSDoB0Mz/zuuDcY9wav7og+pWbqjb1eF3ifQTAKRv4wDIH5Qz+OBqzLWEzjbkT7Ucy6vcAP44CGAe8CRCMfeDdmYbc7GHqtNVfwsfd7je4qaAP6GsxlhoX161uPGgOo3M6Lk7Px7uZx/2Dn7OhldL6/E4Xnmz/1o9Oz7c3D45Pto8Grp9tbu6eHe89+3j/f3X1++tPRq829o6PT8NRreY6fF/i+3/HdX99VJjX7473j38+9u8L9ouWZKdWY7lyZ3VAOSwZx7bL/H6chzSrnG42630LHBf+wNxg21MQtnPmD/iDqjgbBYBSNumHkD4P7obWW5suD65f9wdnOy5+3jnde/O35+eHufnd3a3NvsLP3dOdk5+jw+fPui+f96NXpwbP97f3zvZ+fPXl5ursMLjbFC/Wl1YWxjYiK1gWUP2z7vbPQH/vBOOx9JKBGvSAJExoGfsCDMOpHo4h22YB3+zCIhkPGw8Dvhr0g6MEoiqMe7Q4jGvf7SdSH3nCYILxopcv10V/50TeLurKTUYaHU7AwVunfA/X8Yl794bFvQZryZH99613BjTdef0Nt1ec+Wh4DKAM7VajkBFwxhu29sXfvtLm9h8u8cYDgLR/jruohFjr9vEPNW9e8OSvpyCHYmdJXLsDWc0wKW2j4HJ5Pa0oia64X2FlIlKu8qmKqauUgSKBNudrv+B2MIFNkGdU3SyqSa3UtuOsbkr2zs2OyebyPzQZOLa17BnU/utq1Q/YtEXICxpbtRg3tMmE5arcy14oXDDiJb9axKFuYWA0v2lFADTZYrSJMSVNkUC+l16DpBEijsUA01oLiGuqOeaNl1VZagMRGiBNkMSKo2iCuxx/fLAR6ojRgG00Yp3lDj1gLPgESg50BSNy+1HZ15bFWeAPAhvAVkBm26a1pEQ4MpNU0Fb9iS+ZDmUlMy3FwIUyEMQVoJ9Gi/WYVMUXsunSNBk+LuMYRmqjKbiSmKSrbwiZn1VyHazcIcXLcbR0tV3buedaf3RNeNw168agOTw7XkGJyMCsFbCX2BlMa2lJxePyn8p438o2st6umZtQdxMDJtaCEvTg5aBFKYq1mBrTbQUmo+5ELrE+3n5vfxJorZjasy9yGXxlEWhEN6E7lyEnhNfEDDmFUUs6Q8hLQFpmB65ZnGUjuxlAIFJW4MRHSWKAcF2X0CgdYXGhg1tkQJ23G6enMOikEB1JGTAyGTNXMQcIzIXHyp0nt4s4da2xwC9dAf+SmgLV3vt5eaPo92UrVZInBbDZbVX5B2Y5TNdmgbQmztilkG0+hKbSr8+Ox69kbhWFC2dVEq0JyouTdaCh9R7OpsMBsoWlKRIYxD5mzvKoa/Bl9h2O88uggcZHljzvkKU4JZdm9wK9prArs9TsREcBqv4VrKA4xNdAibArsiiB1U383QdhFaJcATISdFnGHqWyjwqH+rFXdiFMVb2RUyI3tnZc7B0fH+4e7nYw/dubagkRpQMPHMBESpxHfGzJT2uIMSVh3zFfDSkwDwgkBbKrKEYiTD8OSHCr+NYmAcMXcbMRhNCY//DADwnESanFkrbQBogspUYgaKDRZmYYoDlolpymGSzNLLHzphx/KBABuIkjT9Maxdmsvr2kquFPw8t7ZBuj6GoidKWIAR6UWg0cy0LJKKhyYKvK0wifDNCwyLLuotM7BYuVgTAWNRYoRh6sa7tVZcX2MroxKOgFDBDrXTLZITjXwNsdZdO1eKllVVeVWZC7p4Z7VSkxqmPJUQiQAN+TRDL5PU9KILBxM4UD7jfeE5u44QHZvvAV26CJYsYLOzFFyCvpaMGgUY03LOqK2StxRhmTlfIMy16qpxjq12E2HfoqhV/axWneKvdXSDjIq3K+Qpuqvzd/mWGQzkAYae23mlE2BhB0supfD6MUv7fKX5Y5VOqHu16rv4piajYP9JzuHpzu4pDO1WeoaIbkyNqOysWXddCNV142sTNtXCojb5fTn/88z/kTPM6orqIUPdiNPqXDdYueDt9UF7PWdeyi6znjdm4zGHeyi5U2Vsbj49haPkBc6nc/x63J4ijczLgyN04+NT5v++J9/VbEWpfJqu3gnUl1mPXdJ/BLl/mseT3wChfrZyFeC8D/0UOITINVPSL4SpG/0JuITAt97wrEq+W8K+k1fPnxS8uq9xlLeC/xHC4T6C7PPo5NqeveYfNFbso/IV31J5U1TvqWL3M2rbpY2BYrxtWyobTIGedOX7j3YWGmo7e6cefP5vwCAGV4s
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Related Operations"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/liquidity_pools/{liquidity_pool_id}/operations"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents successful operations referencing a given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new operations referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known operation unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream operations created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./lp-retrieve-related-operations.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./lp-retrieve-related-operations.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./lp-retrieve-related-operations.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/lp-retrieve-related-operations.mdx b/docs/data/apis/horizon/api-reference/lp-retrieve-related-operations.mdx
new file mode 100644
index 000000000..1c38938ae
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/lp-retrieve-related-operations.mdx
@@ -0,0 +1,12 @@
+---
+title: Retrieve Related Operations
+openapi: "openapi/horizon/bundled.yml GET /liquidity_pools/{liquidity_pool_id}/operations"
+---
+
+<Tip>
+
+**Supports Streaming**
+
+This endpoint supports streaming. To read more about this, visit the [streaming section](/docs/data/apis/horizon/api-reference/structure/streaming).
+
+</Tip>
diff --git a/docs/data/apis/horizon/api-reference/lp-retrieve-related-transactions.ParamsDetails.json b/docs/data/apis/horizon/api-reference/lp-retrieve-related-transactions.ParamsDetails.json
deleted file mode 100644
index d2b9ed36b..000000000
--- a/docs/data/apis/horizon/api-reference/lp-retrieve-related-transactions.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"liquidity_pool_id","in":"path","required":true,"description":"A unique identifier for this liquidity pool."},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/lp-retrieve-related-transactions.RequestSchema.json b/docs/data/apis/horizon/api-reference/lp-retrieve-related-transactions.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/lp-retrieve-related-transactions.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/lp-retrieve-related-transactions.StatusCodes.json b/docs/data/apis/horizon/api-reference/lp-retrieve-related-transactions.StatusCodes.json
deleted file mode 100644
index 44932b5ce..000000000
--- a/docs/data/apis/horizon/api-reference/lp-retrieve-related-transactions.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"memo":{"type":"string"},"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"account":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"ledger":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","account","ledger","operations","effects","precedes","succeeds","transaction"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"successful":{"type":"boolean"},"hash":{"type":"string"},"ledger":{"type":"integer","format":"int32"},"created_at":{"type":"string"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"account_muxed":{"type":"string"},"account_muxed_id":{"type":"string"},"source_account_sequence":{"type":"string"},"fee_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed_id":{"type":"string"},"fee_charged":{"type":"string"},"max_fee":{"type":"string"},"operation_count":{"type":"integer","format":"int32"},"envelope_xdr":{"type":"string"},"result_xdr":{"type":"string"},"result_meta_xdr":{"type":"string"},"fee_meta_xdr":{"type":"string"},"memo_type":{"type":"string"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"},"preconditions":{"type":"object","properties":{"timebounds":{"type":"object","properties":{"min_time":{"type":"string"},"max_time":{"type":"string"}},"title":"TransactionPreconditionsTimebounds"},"ledgerbounds":{"type":"object","properties":{"min_ledger":{"type":"string"},"max_ledger":{"type":"string"}},"title":"TransactionPreconditionsLedgerbounds"},"min_account_sequence":{"type":"string"},"min_account_sequence_age":{"type":"string"},"min_account_sequence_ledger_gap":{"type":"integer","format":"uint32"},"extra_signers":{"type":"array","items":{"type":"string"}}},"title":"TransactionPreconditions"},"fee_bump_transaction":{"type":"object","properties":{"hash":{"type":"string","title":"hash"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"}},"title":"FeeBumpTransaction"},"inner_transaction":{"type":"object","properties":{"hash":{"type":"string","title":"hash"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"},"max_fee":{"type":"string"}},"title":"InnerTransaction"}},"required":["id","paging_token","successful","hash","ledger","created_at","source_account","source_account_sequence","fee_account","fee_charged","max_fee","operation_count","envelope_xdr","result_xdr","result_meta_xdr","memo_type","signatures"]}}}}},"title":"Transaction"}]},"examples":{"LPRetrieveRelatedTransactions":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/3b476aff8a406a6ec3b61d5c038009cef85f2ddfaf616822dc4fec92845149b4/transactions?cursor=&limit=2&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/3b476aff8a406a6ec3b61d5c038009cef85f2ddfaf616822dc4fec92845149b4/transactions?cursor=120192370561220608&limit=2&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/3b476aff8a406a6ec3b61d5c038009cef85f2ddfaf616822dc4fec92845149b4/transactions?cursor=120192344791343104&limit=2&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/2ff47e1bafe68639276b2a8df0a73597ee0c062fbcc72d121af314fe7851c908"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GAHQN6YNYD6ZT7TLAVE4R36MSZWQJZ22XB3WD4RLSHURMXHW4VHJIDF7"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/895788"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/2ff47e1bafe68639276b2a8df0a73597ee0c062fbcc72d121af314fe7851c908/operations","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/2ff47e1bafe68639276b2a8df0a73597ee0c062fbcc72d121af314fe7851c908/effects","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=3847380164161536"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=3847380164161536"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/2ff47e1bafe68639276b2a8df0a73597ee0c062fbcc72d121af314fe7851c908"}},"id":"2ff47e1bafe68639276b2a8df0a73597ee0c062fbcc72d121af314fe7851c908","paging_token":"3847380164161536","successful":true,"hash":"2ff47e1bafe68639276b2a8df0a73597ee0c062fbcc72d121af314fe7851c908","ledger":895788,"created_at":"2021-08-09T20:53:11Z","source_account":"GAHQN6YNYD6ZT7TLAVE4R36MSZWQJZ22XB3WD4RLSHURMXHW4VHJIDF7","source_account_sequence":"3847371574214658","fee_account":"GAHQN6YNYD6ZT7TLAVE4R36MSZWQJZ22XB3WD4RLSHURMXHW4VHJIDF7","fee_charged":"10000","max_fee":"10001","operation_count":1,"envelope_xdr":"AAAAAgAAAAAPBvsNwP2Z/msFScjvzJZtBOdauHdh8iuR6RZc9uVOlAAAJxEADasqAAAAAgAAAAAAAAAAAAAAAQAAAAEAAAAADwb7DcD9mf5rBUnI78yWbQTnWrh3YfIrkekWXPblTpQAAAAGAAAAAVNFQwAAAAAAm6XFaVsf8OSuS9C9gMplyTjagE9jAnnqwxSDJ6fin6IAsaK8LsUAAAAAAAAAAAAB9uVOlAAAAECXmRsoXmRiJjUrtbkDZYRnzac5s1CVV4g2RlIgBIuQty21npz3A1VhUcSmAx+GmsyGxVFvIrcdstTawJlmy9kF","result_xdr":"AAAAAAAAJxAAAAAAAAAAAQAAAAAAAAAGAAAAAAAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAA2rLAAAAAAAAAAADwb7DcD9mf5rBUnI78yWbQTnWrh3YfIrkekWXPblTpQAAAAAGtJNDAANqyoAAAABAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAA2rLAAAAAAAAAAADwb7DcD9mf5rBUnI78yWbQTnWrh3YfIrkekWXPblTpQAAAAAGtJNDAANqyoAAAACAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAAAwAAAAMADassAAAAAAAAAAAPBvsNwP2Z/msFScjvzJZtBOdauHdh8iuR6RZc9uVOlAAAAAAa0k0MAA2rKgAAAAIAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEADassAAAAAAAAAAAPBvsNwP2Z/msFScjvzJZtBOdauHdh8iuR6RZc9uVOlAAAAAAa0k0MAA2rKgAAAAIAAAABAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAADassAAAAAQAAAAAPBvsNwP2Z/msFScjvzJZtBOdauHdh8iuR6RZc9uVOlAAAAAFTRUMAAAAAAJulxWlbH/DkrkvQvYDKZck42oBPYwJ56sMUgyen4p+iAAAAAAAAAAAAsaK8LsUAAAAAAAEAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMADasrAAAAAAAAAAAPBvsNwP2Z/msFScjvzJZtBOdauHdh8iuR6RZc9uVOlAAAAAAa0nQcAA2rKgAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEADassAAAAAAAAAAAPBvsNwP2Z/msFScjvzJZtBOdauHdh8iuR6RZc9uVOlAAAAAAa0k0MAA2rKgAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"none","signatures":["l5kbKF5kYiY1K7W5A2WEZ82nObNQlVeINkZSIASLkLcttZ6c9wNVYVHEpgMfhprMhsVRbyK3HbLU2sCZZsvZBQ=="]}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/lp-retrieve-related-transactions.api.mdx b/docs/data/apis/horizon/api-reference/lp-retrieve-related-transactions.api.mdx
deleted file mode 100644
index aa55278be..000000000
--- a/docs/data/apis/horizon/api-reference/lp-retrieve-related-transactions.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: lp-retrieve-related-transactions
-title: "Retrieve Related Transactions"
-description: "This endpoint represents successful transactions referencing a given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new transactions referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time."
-sidebar_label: "Retrieve Related Transactions"
-hide_title: true
-hide_table_of_contents: true
-api: eJztW+ty27iSfhUUf8wkc3S/y1Wps3Jsx3Ycx/ckzrg0INiUEJEAA4CSNS5VndfY19sn2WqQkkhJduxkzhnPzvqHnZAA+t5ANz/cOYYOtLP12TniX2PucTMlJ1IG2rkpOB5opnhkuBTOlnMx5JqA8CLJhSEKIgUahNFEx4yB1n4cEKOo0JThDE0U+KBAMC4GhJIBH4MgwYJKJGVAqPAIo4K4QGINHuGCaKOAhjgnlB6UyHnu/4QGgZxoMpUxMZIEXBsQxJeKCJjcT94g76u0NTFDmBKqgFDPAw8XNEMg5waCgCoSgDcAVSIHPmE0CDaxVyD7UvHfpSATHgREG6oMocYuA1QFHLQhIyEnIssbiUUAWhNKWKy0VIRrosEUcP3JkLMhYVQD4Sa7qq9kSMyQmnRSiWxPcZZJ5IP5WmMaxICiCDkpWD2hghO28wpiCqgBj2guGOBIRRR8jZFlw0MoOQVHRqAojj7wnC3n6OQMjOIwhjMIcOpFZjmn4ERU0RAMKHSoO0fQEJwtZ6H2Pqq9zz2n4HB0qIiaoVNwkCZX4DlbRsWw6nU9Egv+NQbCPRCG+xyUNfcGi5acWWFBNdHGnNTXGNQ0R8ungd5ATMShCyrRs3V0jaqkREfAuM8ZCSSzCkFbUcJkEEBiU+kTBTqSQoO2fs01iWLrNqnpgER0wMWgb+QIRGoo6RNKFDCpPFS4ZkMIqbN155hphHJwYWAAKAjc0jAKwNlqtSqtVrXdaHe6zW610pxlxJbKg6dL7YHmA0HnciCrdqGlQyYcaqKHMg48QqMIqCqR91HiSlywIPaA/EY1+428oJqB8LgYvCRSkd+Q3G/kBf5JH9ugsiakahCHIAzhWvzPv/7bpIFgiAc+jYNE/3bZjerRRnExQO2IOMQ0RjVzEgGdm6xiAh5y80TFXAyBhPSWh3E4dwxr5UQVCkysBHglguPs+jbUFBUDSGxeReZrlQopEipIHEWg0oHWwbgmQ6o8Jr0kt8xzCfp3BMqXKqQYmgqolkI/oLS5AcFb01218li/qlayCktN2vcpD8B7oubOwdhsqpJUNHePZC2yyCroOBg1yOu6M9nZGEmWxEYpXCkDoGJpf5tC7Pib2eym4NwWdRxFUhldXGTueaJZhCsuWKtU8M+KGMnO5hQcJoUBYXAIjaKAJ0mg/EXjuLsMYzQI3vs2/aUsSvcLMPS8SKHchif0+gEXI50R5Z5xGgL/26OGCvxNUWFdyFj3FyNnVnAMhJFN3RuUOJtl7fo5WfSm4BhuAsisIeDWPDOWIgXjZ8XSDIfNHx1ZU2NsfcMnIHQBTyLfFiVNQpmBVCmKkckNhI/wqxBCua6LWeGv7JiUMRmL5+abyTHymTG1TMHPjDHwfWDmuXEVKWDgwXNjy1Ze4D03tjJVxrPibGWQzWDLrLGI1Fx0LD0y4wUZzeelvZkVHO5tEmfOCfesP2UKgY1ZeFlTb5K24AypHm6cuJZtlge9hUa5MPUaDk4rwD41m5mQsWLQX0+rC6kiagwoPCq9+dwrXleK3Zu7ZnOWkZd6nsIj1DI998P4FjboaHVEf5Mi17jqayxZBYONY33449jPrHWfCD+64n0i40A2pGpwj95Cetv3YbMKFr7cX1XDQ54BYgyBjKB/66mNyyan9m+9DsHQe8egVA8OwDNKP3m6yQ9sxRMreMwp6JsGyhzXMgunqV8Kjz9ys8TOiStj8ZikHHLRx/H32vSelxleMx2YkyyjF0s2FknhKWytpZE8Y/e+fgRrR1lmcD0uHhfMmwb26eAJgxO2+wMaPRwG8TIObo2iffQI29V6rJ/NHqOIeQy4cRj1n7Znbsz+S4r2/X8qRDKP9wC24zDKCIyTuBCg/sICPpRfM1MOUMyc6CvnDdv5zO38uX0+3dQzx5DM9ry2Gd+/D+Z3vfzmsRRlfWNYSfq5FL+e0LPZOWeHm9nsPu93ZjezRb/JWubhjvLWnWObpPl+ybzwTA6OztCYSG+Vy8OkeVY0oI0AU9JJF78k1aCcb0Hrct1ttFvU9zu0UWnRFrC626p6TVapdyqVLgO/0/RrnudTv1VtdWo1jzV8YN1ap9GsNrpuo5zto/8zaTW/+sl29l7VfrKt01fYiMw0S54bt9Vapdqt1duVZqtaq1Valc5m/uedlWfKf6PR7lbrjXq10ljh37aA0RFzXZVF3+TzD7pUlqdyzfcbbai61IdWp1Xv1tott0Y7nl+h7Xqz2waosEqr5ruMtWtetValfr3a8KHdaVZZt9JZaV48gY10li6/6e2fHrc+HX/aaV1ftC+Oele7jbN669359YfTw+ta7eN2/cNO4+zofP/y7N3H/Q+Nq/3Dg529dr5meIqV7SRd7nSb7U5nvafwZ+mynCveMkUjNn3zDYY/jcVlSbnOX7bV8J0M/nMRwT+l0VLvNNr1TqXaalRb1Wa9tdo8+DFCGGoPUVrZ+v+8KEurc+eHV1qt4J01sfMlfPLBITnV/BHU5xGbBF++kHdqlVq1WOkUK92LWmWrWd+qVq/XDxBbznenjAdq8EQR7Wqz3ahVG61mZ+U48kNUc2WwU61UKpXMiSZ5Ut1wstmqrha0Tg9/Bvb3yfZYH09OatflUO+dsy/j3w+vzfZ7j8b73rDD47PW2TXrxlfvg16vd3i729uh+mtm/vLnFH/t2n/uTNz2Dtvphn5TbV+Kg3Zn+sE9vRAf1LD+yT9QIxh9+HjiBheRnfTGTro63judJEuFrY979Er7nffn8Xn3dXfwLgqmF1/oYLf7pSfE18nt+c5hy+eiddDT9G3nSF9mOdme89vbff0xPNPyY3jGD79cKuOOdq4/nYnfKWvq6uurq8agdhYcDLYP4lMzrVVF9Hu9V70aXrLzsHf7jzehnr65vdobHyjmaXNBJ4dBOO2O9vLHw1SfVj+r+ugt5Ut+Xm04TWYNcmD11+vV1FFm1hMV2ntjDo93er3jr1NpFdLb+LO7+bEd/4fSf/10+r1ezzrDO3Q4nXn3JIft9Xq0Mqq8Q3neLvW7/nO6+THy+G+gv26Pe+n3lvRPv4f+3sXZ5btkocM4uP0QuPvlnZEajU/Hn3beXrNRoya3Tz5NDpst/e5yMAXRiP7Bs/TzAbZms1fOai8r483WeuqHtCdO2VJ793jMf8x6T6H/6lWuTNxyhBQr1eLWZydojty3e83RJ/6p+rb9odmrfdi97tTEe/f4NLiCg+PR9flB7/xodMSMuW6x7uT46tPV/m40eOcPI/VuqK/O3Onb+r57dFnTr6+v9fh6+/TVK+dmltSithyFWwNCJ4fTz3fOCKbO1mZ0QGFedNoD2Q1KYIYSd5wBmKR7gLv4WplztwZ0muXOLyg4qPEcHRWr4HGHIGcTLOUiGUeOwUykGtmPy5tX9GPU9GPW3JuPJGK+6g12b/zkQ3Faz6cgFVQTKJ3MrpQqpao98oQhVdPlKBIpOeaeRUSR/YuLE9I7OUBEiEcNRfBHFm+XUi2RA0O4GIA2CZBKQdEqzuL1kpmRkl7MwCPudNMSCTgL23kLoA1QjdAxIwmTQschzKfSMSg6AJKBdRCFzQg+hjkiMAPGKUrFQSBszjKygEGmeBaLYnSnC4ZeSwUIEOLaSp6Rw1XcGwBxwUwABJJPpM3PPFESG2QIdRsBmSAM0egC8YCBMIoG/HfwCNyyIYKOdMGuQLUGlFnHoCxHC2CRkUTHrsUfZRyzQCyqB02UHtOISwMUtoDwrRQ6CGML9rR85GCEiI9bzCytedbf3RM+Zw1682Ienh4k51GlcwVPynaZSQVFIT14+bfynl/Fr2JOLsUFU1tFgUfGnBJ2eXZUIJS4Sk40KEtBCpiDFhe6Pt95q7+pa08yXTY2d2tvpFHTkihAd0oAtRL7lLcIL5V+go+NEoUWyAQsDjAMQXgWZIuKogIJEy60AerhpJCOEJ7rcQXMWBsiklhbOa1ZBzH3gCQR44ImQzmxKvFCLhDbrMjcxa07znWDJCw08IVFOc+98/POQtKfyXYgB0sdTCaTvPCLkUU3kIMyLQqYFHUsirgLDaGY7h8vLRpRSwwTykYDhd9tiBSr0ZD4jmJDboCZWNGA8BBjHkJreZlCF0P6BUHKydZB8NPHyxLZQwy0SD6/4GPqyhhRjJZFVGBKb+Ea0gOXaigQNgQ2Ijg6K7/FRr5B1S4VMOBmGLslJsNyqof537moZTeQbjmkXJR3dq92j96fHBy/KYXeS2uubfClAjS8CwMuEGf5syYTqQyiY7mxJWcKxcY0wC0TwIYyAXda/jAsybH0vicREE8yi/q0Otoiv/wyAeIhztsgLF8qDUTFQiATc0WhyZI0RBFGLjwaYLhks8TCl375JUkAYLHONAimdmk7tz+mAfesgP21vQ3Q9RUQM5FEA4LADQaPYKBEmlQ8YDKOglQ/IaZhHuLBiwpjHcyVVo0Bpy4PMOJwVsa9SjnXx+gKqaAD0ISjc01EgURUgVf0EGs/dy/p50WVkeGhTXpIM52JSQ1TnvSJwH4YeTGBn4OAZCILIbcI1//VeU0jux3gcr86C92hi9hungr1e/8c1JjbbsjcyLmeFg4qSt9uZdx+sEF0KWW295uib+dsZx16D0PPGt8prBz28kc7CCm3byEI5H9l32GzlzMQGjK0ehFlQyC1EnZTljD7xZti8mZJMU0n1L5NW/52UV0+Oni9e3y+i1NKQxMGtucWSW1CKjIk5199SPrZh6zcJMgdIe6W6Nv/v4TyN7yEkhaPBm5NOQootx+VrTfepcXY55VLJuhCW5vuneTqsZuCM5Ta4PS7O9xOLlUwm+HjBOWOVZrHNXWD+3DuWc/88++ObNRTUugubsOkpa1jC8anCPeXuSLygBbml2O+Uwn/h66DPKCk+UWZ71TSv+nmxwMMr11UWXJ+g/9RHFl/YjS/OEuBGy/Jk26g3cPpHJkipln+lipfzVQWKDEEiv66bFf1GIMoa5u1qyi5dtWb3QtnNvtfnA7vGg==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Related Transactions"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/liquidity_pools/{liquidity_pool_id}/transactions"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents successful transactions referencing a given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new transactions referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./lp-retrieve-related-transactions.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./lp-retrieve-related-transactions.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./lp-retrieve-related-transactions.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/lp-retrieve-related-transactions.mdx b/docs/data/apis/horizon/api-reference/lp-retrieve-related-transactions.mdx
new file mode 100644
index 000000000..bf7dad82b
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/lp-retrieve-related-transactions.mdx
@@ -0,0 +1,12 @@
+---
+title: Retrieve Related Transactions
+openapi: "openapi/horizon/bundled.yml GET /liquidity_pools/{liquidity_pool_id}/transactions"
+---
+
+<Tip>
+
+**Supports Streaming**
+
+This endpoint supports streaming. To read more about this, visit the [streaming section](/docs/data/apis/horizon/api-reference/structure/streaming).
+
+</Tip>
diff --git a/docs/data/apis/horizon/api-reference/resources/README.mdx b/docs/data/apis/horizon/api-reference/resources/README.mdx
deleted file mode 100644
index 1d8b2668a..000000000
--- a/docs/data/apis/horizon/api-reference/resources/README.mdx
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: Resources
-sidebar_position: 20
----
-
-import { MethodTable } from "@site/src/components/MethodTable";
-
-Data on the Stellar ledger is organized according to resources. Each resource has several different endpoints.
-
-<MethodTable title="Resource Types">
-
-|                                                      |     |
-| ---------------------------------------------------- | --- |
-| [Ledgers](./ledgers/README.mdx)                      |     |
-| [Transactions](./transactions/README.mdx)            |     |
-| [Operations](./operations/README.mdx)                |     |
-| [Effects](./effects/README.mdx)                      |     |
-| [Accounts](./accounts/README.mdx)                    |     |
-| [Offers](./offers/README.mdx)                        |     |
-| [Claimable Balances](./claimablebalances/README.mdx) |     |
-| [Trades](./trades/README.mdx)                        |     |
-| [Assets](./assets/README.mdx)                        |     |
-| [Liquidity Pools](./liquiditypools/README.mdx)       |     |
-
-</MethodTable>
diff --git a/docs/data/apis/horizon/api-reference/resources/_category_.json b/docs/data/apis/horizon/api-reference/resources/_category_.json
deleted file mode 100644
index 9e3a55f45..000000000
--- a/docs/data/apis/horizon/api-reference/resources/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": true
-}
diff --git a/docs/data/apis/horizon/api-reference/resources/accounts/README.mdx b/docs/data/apis/horizon/api-reference/resources/accounts/README.mdx
deleted file mode 100644
index 58b9dec08..000000000
--- a/docs/data/apis/horizon/api-reference/resources/accounts/README.mdx
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: Accounts
-order: 0
----
-
-Users interact with the Stellar network through accounts. Everything else in the ledger—assets, offers, trustlines, etc.—are owned by accounts, and accounts must authorize all changes to the ledger through signed transactions.
-
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
-
-Learn more about [accounts](../../../../../../learn/glossary.mdx#account).
-
-<EndpointsTable title="Endpoints">
-
-|  |  |
-| --- | --- |
-| GET | [/accounts](../../list-all-accounts.api.mdx) |
-| GET | [/accounts/:account_id](../../retrieve-an-account.api.mdx) |
-| GET | [/accounts/:account_id/transactions](../../get-transactions-by-account-id.api.mdx) |
-| GET | [/accounts/:account_id/operations](../../get-operations-by-account-id.api.mdx) |
-| GET | [/accounts/:account_id/payments](../../get-payments-by-account-id.api.mdx) |
-| GET | [/accounts/:account_id/effects](../../get-effects-by-account-id.api.mdx) |
-| GET | [/accounts/:account_id/offers](../../get-offers-by-account-id.api.mdx) |
-| GET | [/accounts/:account_id/trades](../../get-trades-by-account-id.api.mdx) |
-| GET | [/accounts/:account_id/data](../../get-data-by-account-id.api.mdx) |
-
-</EndpointsTable>
diff --git a/docs/data/apis/horizon/api-reference/resources/accounts/index.mdx b/docs/data/apis/horizon/api-reference/resources/accounts/index.mdx
new file mode 100644
index 000000000..15b39ead1
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/resources/accounts/index.mdx
@@ -0,0 +1,21 @@
+---
+title: Accounts
+description: "Users interact with the Stellar network through accounts. Everything else in the ledger—assets, offers, trustlines, etc.—are owned by accounts, and accounts must authorize all changes to the ledger through signed transactions."
+order: 0
+---
+
+The [latest ledger](/docs/data/apis/horizon/api-reference/structure/consistency) known to Horizon is included as an HTTP header in the response.
+
+Learn more about [accounts](/docs/learn/glossary#account).
+
+| Endpoints |  |
+| --- | --- |
+| GET | [/accounts](/docs/data/apis/horizon/api-reference/list-all-accounts) |
+| GET | [/accounts/:account_id](/docs/data/apis/horizon/api-reference/retrieve-an-account) |
+| GET | [/accounts/:account_id/transactions](/docs/data/apis/horizon/api-reference/get-transactions-by-account-id) |
+| GET | [/accounts/:account_id/operations](/docs/data/apis/horizon/api-reference/get-operations-by-account-id) |
+| GET | [/accounts/:account_id/payments](/docs/data/apis/horizon/api-reference/get-payments-by-account-id) |
+| GET | [/accounts/:account_id/effects](/docs/data/apis/horizon/api-reference/get-effects-by-account-id) |
+| GET | [/accounts/:account_id/offers](/docs/data/apis/horizon/api-reference/get-offers-by-account-id) |
+| GET | [/accounts/:account_id/trades](/docs/data/apis/horizon/api-reference/get-trades-by-account-id) |
+| GET | [/accounts/:account_id/data](/docs/data/apis/horizon/api-reference/get-data-by-account-id) |
diff --git a/docs/data/apis/horizon/api-reference/resources/accounts/object.mdx b/docs/data/apis/horizon/api-reference/resources/accounts/object.mdx
index 0436efbb9..45c4f2dfb 100644
--- a/docs/data/apis/horizon/api-reference/resources/accounts/object.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/accounts/object.mdx
@@ -1,140 +1,257 @@
 ---
 title: The Account Object
+description: "When Horizon returns information about an account, it uses the following format."
 order: 10
 ---
 
 When Horizon returns information about an account, it uses the following format:
 
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- id
-  - string
-  - A unique identifier for this account.
-- account_id
-  - string
-  - This account's public key encoded in a base32 string representation.
-- sequence
-  - number
-  - This account's current sequence number. For use when submitting this account's next transaction.
-- sequence_ledger
-  - number
-  - The unsigned 32-bit ledger number of the sequence number's [age](../../../../../../learn/glossary.mdx#sequence-number).
-- sequence_time
-  - string
-  - The unsigned 64-bit UNIX timestamp of the sequence number's [age](../../../../../../learn/glossary.mdx#sequence-number).
-- subentry_count
-  - number
-  - The number of subentries on this account.
-- home_domain
-  - string
-  - The domain that hosts this account's `stellar.toml` file.
-- last_modified_ledger
-  - number
-  - The ID of the last ledger that included changes to this account.
-- num_sponsoring
-  - number
-  - The number of reserves sponsored by this account.
-- num_sponsored
-  - number
-  - The number of reserves sponsored for this account.
-- sponsor
-  - string (optional)
-  - The account ID of the sponsor who is paying the reserves for this account.
-- thresholds
-  - object
-  - Operations have varying levels of access. This field specifies thresholds for different access levels, as well as the weight of the master key.
-    - low_threshold
-      - number
-      - The weight required for a valid transaction including the Allow Trust and Bump Sequence operations.
-    - med_threshold
-      - number
-      - The weight required for a valid transaction including the Create Account, Payment, Path Payment, Manage Buy Offer, Manage Sell Offer, Create Passive Sell Offer, Change Trust, Inflation, and Manage Data operations.
-    - high_threshold
-      - number
-      - The weight required for a valid transaction including the Account Merge and Set Options operations.
-- flags
-  - object
-  - Flags denote the enabling/disabling of certain asset issuer privileges.
-    - auth_immutable
-      - boolean
-      - If set to `true`, none of the following flags can be changed.
-    - auth_required
-      - boolean
-      - If set to `true`, anyone who wants to hold an asset issued by this account must first be approved by this account.
-    - auth_revocable
-      - boolean
-      - If set to `true`, this account can freeze the balance of a holder of an asset issued by this account.
-    - auth_clawback_enabled
-      - boolean
-      - If set to `true`, trustlines created for assets issued by this account have [clawbacks](../../../../../../learn/glossary.mdx#clawback) enabled.
-- balances
-  - object
-  - The assets this account holds.
-    - balance
-      - string
-      - The number of units of an asset held by this account.
-    - buying_liabilities
-      - string (optional)
-      - The sum of all buy offers owned by this account for this asset.
-    - selling_liabilities
-      - string (optional)
-      - The sum of all sell offers owned by this account for this asset.
-    - limit
-      - number (optional)
-      - The maximum amount of this asset that this account is willing to accept. Specified when opening a trustline.
-    - asset_type
-      - string
-      - Either `native`, `credit_alphanum4`, `credit_alphanum12`, or `liquidity_pool_shares`.
-    - asset_code
-      - string (optional)
-      - The code for this asset.
-    - asset_issuer
-      - string (optional)
-      - The Stellar address of this asset's issuer.
-    - sponsor
-      - string (optional)
-      - The account ID of the sponsor who is paying the reserves for this trustline.
-- signers
-  - array of objects
-  - The public keys and associated weights that can be used to authorize transactions for this account. Used for multi-sig.
-    - public_key
-      - string
-      - **REMOVED in 0.17.0: USE `key` INSTEAD.**
-    - weight
-      - number
-      - The numerical weight of a signer. Used to determine if a transaction meets the `threshold` requirements.
-    - sponsor
-      - string (optional)
-      - The account ID of the sponsor who is paying the reserves for this signer.
-    - key
-      - string
-      - A hash of characters dependent on the signer type.
-    - type
-      - string
-      - The type of hash for this signer.
-        - ed25519_public_key
-          - skip
-          - A normal Stellar public key.
-        - sha256_hash
-          - skip
-          - The SHA256 hash of some arbitrary `x`. Adding a signature of this type allows anyone who knows x to sign a transaction from this account. _Note: Once this transaction is broadcast, x will be known publicly._
-        - preauth_tx
-          - skip
-          - The hash of a pre-authorized transaction. This signer is automatically removed from the account when a matching transaction is properly applied.
-- data
-  - object
-  - An array of account data fields.
-
-</AttributeTable>
-
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
-
-<ExampleResponse>
-
-```json
+<ResponseField name="id" type="string">
+
+A unique identifier for this account.
+
+</ResponseField>
+
+<ResponseField name="account_id" type="string">
+
+This account's public key encoded in a base32 string representation.
+
+</ResponseField>
+
+<ResponseField name="sequence" type="number">
+
+This account's current sequence number. For use when submitting this account's next transaction.
+
+</ResponseField>
+
+<ResponseField name="sequence_ledger" type="number">
+
+The unsigned 32-bit ledger number of the sequence number's [age](../../../../../../learn/glossary#sequence-number).
+
+</ResponseField>
+
+<ResponseField name="sequence_time" type="string">
+
+The unsigned 64-bit UNIX timestamp of the sequence number's [age](../../../../../../learn/glossary#sequence-number).
+
+</ResponseField>
+
+<ResponseField name="subentry_count" type="number">
+
+The number of subentries on this account.
+
+</ResponseField>
+
+<ResponseField name="home_domain" type="string">
+
+The domain that hosts this account's `stellar.toml` file.
+
+</ResponseField>
+
+<ResponseField name="last_modified_ledger" type="number">
+
+The ID of the last ledger that included changes to this account.
+
+</ResponseField>
+
+<ResponseField name="num_sponsoring" type="number">
+
+The number of reserves sponsored by this account.
+
+</ResponseField>
+
+<ResponseField name="num_sponsored" type="number">
+
+The number of reserves sponsored for this account.
+
+</ResponseField>
+
+<ResponseField name="sponsor" type="string (optional)">
+
+The account ID of the sponsor who is paying the reserves for this account.
+
+</ResponseField>
+
+<ResponseField name="thresholds" type="object">
+
+Operations have varying levels of access. This field specifies thresholds for different access levels, as well as the weight of the master key.
+
+  <Expandable title="thresholds properties">
+    <ResponseField name="low_threshold" type="number">
+
+      The weight required for a valid transaction including the Allow Trust and Bump Sequence operations.
+
+    </ResponseField>
+
+    <ResponseField name="med_threshold" type="number">
+
+      The weight required for a valid transaction including the Create Account, Payment, Path Payment, Manage Buy Offer, Manage Sell Offer, Create Passive Sell Offer, Change Trust, Inflation, and Manage Data operations.
+
+    </ResponseField>
+
+    <ResponseField name="high_threshold" type="number">
+
+      The weight required for a valid transaction including the Account Merge and Set Options operations.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="flags" type="object">
+
+Flags denote the enabling/disabling of certain asset issuer privileges.
+
+  <Expandable title="flags properties">
+    <ResponseField name="auth_immutable" type="boolean">
+
+      If set to `true`, none of the following flags can be changed.
+
+    </ResponseField>
+
+    <ResponseField name="auth_required" type="boolean">
+
+      If set to `true`, anyone who wants to hold an asset issued by this account must first be approved by this account.
+
+    </ResponseField>
+
+    <ResponseField name="auth_revocable" type="boolean">
+
+      If set to `true`, this account can freeze the balance of a holder of an asset issued by this account.
+
+    </ResponseField>
+
+    <ResponseField name="auth_clawback_enabled" type="boolean">
+
+      If set to `true`, trustlines created for assets issued by this account have [clawbacks](../../../../../../learn/glossary#clawback) enabled.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="balances" type="object">
+
+The assets this account holds.
+
+  <Expandable title="balances properties">
+    <ResponseField name="balance" type="string">
+
+      The number of units of an asset held by this account.
+
+    </ResponseField>
+
+    <ResponseField name="buying_liabilities" type="string (optional)">
+
+      The sum of all buy offers owned by this account for this asset.
+
+    </ResponseField>
+
+    <ResponseField name="selling_liabilities" type="string (optional)">
+
+      The sum of all sell offers owned by this account for this asset.
+
+    </ResponseField>
+
+    <ResponseField name="limit" type="number (optional)">
+
+      The maximum amount of this asset that this account is willing to accept. Specified when opening a trustline.
+
+    </ResponseField>
+
+    <ResponseField name="asset_type" type="string">
+
+      Either `native`, `credit_alphanum4`, `credit_alphanum12`, or `liquidity_pool_shares`.
+
+    </ResponseField>
+
+    <ResponseField name="asset_code" type="string (optional)">
+
+      The code for this asset.
+
+    </ResponseField>
+
+    <ResponseField name="asset_issuer" type="string (optional)">
+
+      The Stellar address of this asset's issuer.
+
+    </ResponseField>
+
+    <ResponseField name="sponsor" type="string (optional)">
+
+      The account ID of the sponsor who is paying the reserves for this trustline.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="signers" type="array of objects">
+
+The public keys and associated weights that can be used to authorize transactions for this account. Used for multi-sig.
+
+  <Expandable title="signers properties">
+    <ResponseField name="public_key" type="string">
+
+      **REMOVED in 0.17.0: USE `key` INSTEAD.**
+
+    </ResponseField>
+
+    <ResponseField name="weight" type="number">
+
+      The numerical weight of a signer. Used to determine if a transaction meets the `threshold` requirements.
+
+    </ResponseField>
+
+    <ResponseField name="sponsor" type="string (optional)">
+
+      The account ID of the sponsor who is paying the reserves for this signer.
+
+    </ResponseField>
+
+    <ResponseField name="key" type="string">
+
+      A hash of characters dependent on the signer type.
+
+    </ResponseField>
+
+    <ResponseField name="type" type="string">
+
+      The type of hash for this signer.
+
+      <Expandable title="type properties">
+        <ResponseField name="ed25519_public_key" type="skip">
+
+          A normal Stellar public key.
+
+        </ResponseField>
+
+        <ResponseField name="sha256_hash" type="skip">
+
+          The SHA256 hash of some arbitrary `x`. Adding a signature of this type allows anyone who knows x to sign a transaction from this account. _Note: Once this transaction is broadcast, x will be known publicly._
+
+        </ResponseField>
+
+        <ResponseField name="preauth_tx" type="skip">
+
+          The hash of a pre-authorized transaction. This signer is automatically removed from the account when a matching transaction is properly applied.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="data" type="object">
+
+An array of account data fields.
+
+</ResponseField>
+
+The [latest ledger](../../structure/consistency) known to Horizon is included as an HTTP header in the response.
+
+```json Example
 {
   "_links": {
     "self": {
@@ -244,5 +361,3 @@ The [latest ledger](../../structure/consistency.mdx) known to Horizon is include
   "paging_token": ""
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/assets/README.mdx b/docs/data/apis/horizon/api-reference/resources/assets/README.mdx
deleted file mode 100644
index 86392fe78..000000000
--- a/docs/data/apis/horizon/api-reference/resources/assets/README.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: Assets
-order: 0
----
-
-Assets are representations of value issued on the Stellar network. An asset consists of a type, code, and issuer.
-
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
-
-Learn more about [assets](../../../../../../learn/glossary.mdx#asset).
-
-<EndpointsTable title="Endpoints">
-
-|     |                                          |
-| --- | ---------------------------------------- |
-| GET | [/assets](../../list-all-assets.api.mdx) |
-
-</EndpointsTable>
diff --git a/docs/data/apis/horizon/api-reference/resources/assets/index.mdx b/docs/data/apis/horizon/api-reference/resources/assets/index.mdx
new file mode 100644
index 000000000..ca005e45e
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/resources/assets/index.mdx
@@ -0,0 +1,13 @@
+---
+title: Assets
+description: "Assets are representations of value issued on the Stellar network. An asset consists of a type, code, and issuer."
+order: 0
+---
+
+The [latest ledger](/docs/data/apis/horizon/api-reference/structure/consistency) known to Horizon is included as an HTTP header in the response.
+
+Learn more about [assets](/docs/learn/glossary#asset).
+
+| Endpoints |                                                                  |
+| --------- | ---------------------------------------------------------------- |
+| GET       | [/assets](/docs/data/apis/horizon/api-reference/list-all-assets) |
diff --git a/docs/data/apis/horizon/api-reference/resources/assets/object.mdx b/docs/data/apis/horizon/api-reference/resources/assets/object.mdx
index 08bbb0fcb..fd9538c0d 100644
--- a/docs/data/apis/horizon/api-reference/resources/assets/object.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/assets/object.mdx
@@ -1,71 +1,112 @@
 ---
 title: The Asset Object
+description: "When Horizon returns information about an asset, it uses the following format."
 order: 10
 ---
 
 When Horizon returns information about an asset, it uses the following format:
 
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- asset_type
-  - string
-  - This asset's type. Either `credit_alphanum4` or `credit_alphanum12`.
-- asset_code
-  - string
-  - This asset's code
-- asset_issuer
-  - string
-  - The Stellar address of this asset’s issuer.
-- accounts
-  - object
-  - The number of accounts grouped by each trustline flag state.
-- num_claimable_balances
-  - number
-  - The current number of claimable_balances for this asset.
-- num_contracts
-  - number
-  - The current number of Soroban contracts holding this asset.
-- num_liquidity_pools
-  - number
-  - The current number of liquidity pools holding this asset.
-- balances
-  - object
-  - The number of units issued for this asset grouped by each trustline flag state.
-- claimable_balances_amount
-  - string
-  - The number of units for this asset held by all claimable balances.
-- contracts_amount
-  - string
-  - The number of units for this asset held by all Soroban contracts.
-- liquidity_pools_amount
-  - string
-  - The number of units for this asset held by all liquidity pools.
-- flags
-  - object
-  - Flags denote the enabling/disabling of certain asset issuer privileges.
-    - auth_immutable
-      - boolean
-      - If set to `true`, none of the following flags can be changed.
-    - auth_required
-      - boolean
-      - If set to `true`, anyone who wants to hold an asset issued by this account must first be approved by this account.
-    - auth_revocable
-      - boolean
-      - If set to `true`, this account can freeze the balance of a holder of an asset issued by this account.
-- paging_token
-  - number
-  - A cursor value for use in [pagination](../../structure/pagination/README.mdx).
-
-</AttributeTable>
-
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
-
-<ExampleResponse>
-
-```json
+<ResponseField name="asset_type" type="string">
+
+This asset's type. Either `credit_alphanum4` or `credit_alphanum12`.
+
+</ResponseField>
+
+<ResponseField name="asset_code" type="string">
+
+This asset's code
+
+</ResponseField>
+
+<ResponseField name="asset_issuer" type="string">
+
+The Stellar address of this asset’s issuer.
+
+</ResponseField>
+
+<ResponseField name="accounts" type="object">
+
+The number of accounts grouped by each trustline flag state.
+
+</ResponseField>
+
+<ResponseField name="num_claimable_balances" type="number">
+
+The current number of claimable_balances for this asset.
+
+</ResponseField>
+
+<ResponseField name="num_contracts" type="number">
+
+The current number of Soroban contracts holding this asset.
+
+</ResponseField>
+
+<ResponseField name="num_liquidity_pools" type="number">
+
+The current number of liquidity pools holding this asset.
+
+</ResponseField>
+
+<ResponseField name="balances" type="object">
+
+The number of units issued for this asset grouped by each trustline flag state.
+
+</ResponseField>
+
+<ResponseField name="claimable_balances_amount" type="string">
+
+The number of units for this asset held by all claimable balances.
+
+</ResponseField>
+
+<ResponseField name="contracts_amount" type="string">
+
+The number of units for this asset held by all Soroban contracts.
+
+</ResponseField>
+
+<ResponseField name="liquidity_pools_amount" type="string">
+
+The number of units for this asset held by all liquidity pools.
+
+</ResponseField>
+
+<ResponseField name="flags" type="object">
+
+Flags denote the enabling/disabling of certain asset issuer privileges.
+
+  <Expandable title="flags properties">
+    <ResponseField name="auth_immutable" type="boolean">
+
+      If set to `true`, none of the following flags can be changed.
+
+    </ResponseField>
+
+    <ResponseField name="auth_required" type="boolean">
+
+      If set to `true`, anyone who wants to hold an asset issued by this account must first be approved by this account.
+
+    </ResponseField>
+
+    <ResponseField name="auth_revocable" type="boolean">
+
+      If set to `true`, this account can freeze the balance of a holder of an asset issued by this account.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="paging_token" type="number">
+
+A cursor value for use in [pagination](/docs/data/apis/horizon/api-reference/structure/pagination).
+
+</ResponseField>
+
+The [latest ledger](../../structure/consistency) known to Horizon is included as an HTTP header in the response.
+
+```json Example
 {
   "_links": {
     "self": {
@@ -112,5 +153,3 @@ The [latest ledger](../../structure/consistency.mdx) known to Horizon is include
   }
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/claimablebalances/README.mdx b/docs/data/apis/horizon/api-reference/resources/claimablebalances/README.mdx
deleted file mode 100644
index 786b83a6b..000000000
--- a/docs/data/apis/horizon/api-reference/resources/claimablebalances/README.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: Claimable Balances
-order: 0
----
-
-A Claimable Balance represents the transfer of ownership of some amount of an asset. Claimable balances provide a mechanism for setting up a payment which can be claimed in the future. This allows you to make payments to accounts which are currently not able to accept them.
-
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
-
-<EndpointsTable title="Endpoints">
-
-|  |  |
-| --- | --- |
-| GET | [/claimable_balances](../../list-all-claimable-balances.api.mdx) |
-| GET | [/claimable_balances/:claimable_balance_id](../../retrieve-a-claimable-balance.api.mdx) |
-| GET | [/claimable_balances/:claimable_balance_id/transactions](../../cb-retrieve-related-transactions.api.mdx) |
-| GET | [/claimable_balances/:claimable_balance_id/operations](../../cb-retrieve-related-operations.api.mdx) |
-
-</EndpointsTable>
diff --git a/docs/data/apis/horizon/api-reference/resources/claimablebalances/index.mdx b/docs/data/apis/horizon/api-reference/resources/claimablebalances/index.mdx
new file mode 100644
index 000000000..53dd93b39
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/resources/claimablebalances/index.mdx
@@ -0,0 +1,14 @@
+---
+title: Claimable Balances
+description: "A Claimable Balance represents the transfer of ownership of some amount of an asset. Claimable balances provide a mechanism for setting up a payment which can be claimed in the future. This allows you to make payments to accounts which are currently not able to accept them."
+order: 0
+---
+
+The [latest ledger](/docs/data/apis/horizon/api-reference/structure/consistency) known to Horizon is included as an HTTP header in the response.
+
+| Endpoints |  |
+| --- | --- |
+| GET | [/claimable_balances](/docs/data/apis/horizon/api-reference/list-all-claimable-balances) |
+| GET | [/claimable_balances/:claimable_balance_id](/docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance) |
+| GET | [/claimable_balances/:claimable_balance_id/transactions](/docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions) |
+| GET | [/claimable_balances/:claimable_balance_id/operations](/docs/data/apis/horizon/api-reference/cb-retrieve-related-operations) |
diff --git a/docs/data/apis/horizon/api-reference/resources/claimablebalances/object.mdx b/docs/data/apis/horizon/api-reference/resources/claimablebalances/object.mdx
index d1cb8685c..6a38af3b4 100644
--- a/docs/data/apis/horizon/api-reference/resources/claimablebalances/object.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/claimablebalances/object.mdx
@@ -1,74 +1,119 @@
 ---
 title: The Claimable Balance Object
+description: "When Horizon returns information about a claimable balance, it uses the following format."
 order: 10
 ---
 
 When Horizon returns information about a claimable balance, it uses the following format:
 
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- id
-  - string
-  - A unique identifier for this claimable balance.
-- paging_token
-  - number
-  - A cursor value for use in [pagination](../../structure/pagination/README.mdx).
-- asset
-  - string
-  - The asset available to be claimed in the [SEP-11 form](https://github.com/stellar/stellar-protocol/blob/0c675fb3a482183dcf0f5db79c12685acf82a95c/ecosystem/sep-0011.md#values) `asset_code:issuing_address` or `native` (for XLM)
-- amount
-  - string
-  - The amount of `asset` that can be claimed.
-- sponsor
-  - string (optional)
-  - The account id of the sponsor who is paying the reserves for this claimable balance.
-- last_modified_ledger
-  - integer
-  - The sequence number of the last ledger in which this claimable balance was modified.
-- last_modified_time
-  - string
-  - An ISO 8601 formatted string of last modification time.
-- claimants
-  - array of objects
-  - The list of entries which could claim the claimable balance.
-    - destination
-      - string
-      - The account ID who can claim the balance.
-    - predicate
-      - object
-      - The condition which must be satisfied so `destination` can claim the balance.
-        - unconditional
-          - boolean (optional)
-          - If true it means this clause of the condition is always satisfied.
-        - and
-          - array of objects (optional)
-          - The array will always contain two elements which also are predicates. This clause of the condition is satisfied if both of the two elements in the array are satisfied.
-        - or
-          - array of objects (optional)
-          - The array will always contain two elements which also are predicates. This clause of the condition is satisfied if at least one of the two elements in the array are satisfied.
-        - not
-          - object (optional)
-          - The value is also a predicate. This clause of the condition is satisfied if the value is _not_ satisfied.
-        - absBefore
-          - string (optional)
-          - A customized ISO 8601 formatted string representing a deadline for when the claimable balance can be claimed. If the balance is claimed before the date then this clause of the condition is satisfied. The format of this date string is a custom extension on top of ISO 8601 format. It allows for years to be outside the 0000-9999 range. The dates are derived from a unix epoch value in range of signed 64 bit integer. This means the date expresses a much larger calendar range of 292277026596 years into future and -292471206707 years back in past. This custom extension format will add a `'+'` prefix on values that go beyond year 9999 into the future and for years that are prior to year 0(B.C per Gregorian calendar) it will add prefix of `'-'`. Here are examples of date string values that are possible: `'2022-02-10T15:30:22Z'` `'+39121901036-03-29T15:30:22Z'` `'-7025-12-23T00:00:00Z'`
-        - absBeforeEpoch
-          - string (optional)
-          - A unix epoch value in seconds representing the same deadline date for when the claimable balance can be claimed. It is the same date/time value that absBefore represents, just expressed in integral unix epoch seconds within the range of a signed 64bit integer.
-        - relBefore
-          - string (optional)
-          - A relative deadline for when the claimable balance can be claimed. The value represents the number of seconds since the close time of the ledger which created the claimable balance.
-
-</AttributeTable>
-
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
-
-<ExampleResponse>
-
-```json
+<ResponseField name="id" type="string">
+
+A unique identifier for this claimable balance.
+
+</ResponseField>
+
+<ResponseField name="paging_token" type="number">
+
+A cursor value for use in [pagination](/docs/data/apis/horizon/api-reference/structure/pagination).
+
+</ResponseField>
+
+<ResponseField name="asset" type="string">
+
+The asset available to be claimed in the [SEP-11 form](https://github.com/stellar/stellar-protocol/blob/0c675fb3a482183dcf0f5db79c12685acf82a95c/ecosystem/sep-0011.md#values) `asset_code:issuing_address` or `native` (for XLM)
+
+</ResponseField>
+
+<ResponseField name="amount" type="string">
+
+The amount of `asset` that can be claimed.
+
+</ResponseField>
+
+<ResponseField name="sponsor" type="string (optional)">
+
+The account id of the sponsor who is paying the reserves for this claimable balance.
+
+</ResponseField>
+
+<ResponseField name="last_modified_ledger" type="integer">
+
+The sequence number of the last ledger in which this claimable balance was modified.
+
+</ResponseField>
+
+<ResponseField name="last_modified_time" type="string">
+
+An ISO 8601 formatted string of last modification time.
+
+</ResponseField>
+
+<ResponseField name="claimants" type="array of objects">
+
+The list of entries which could claim the claimable balance.
+
+  <Expandable title="claimant properties">
+    <ResponseField name="destination" type="string">
+
+      The account ID who can claim the balance.
+
+    </ResponseField>
+
+    <ResponseField name="predicate" type="object">
+
+      The condition which must be satisfied so `destination` can claim the balance.
+
+      <Expandable title="predicate properties">
+        <ResponseField name="unconditional" type="boolean (optional)">
+
+          If true it means this clause of the condition is always satisfied.
+
+        </ResponseField>
+
+        <ResponseField name="and" type="array of objects (optional)">
+
+          The array will always contain two elements which also are predicates. This clause of the condition is satisfied if both of the two elements in the array are satisfied.
+
+        </ResponseField>
+
+        <ResponseField name="or" type="array of objects (optional)">
+
+          The array will always contain two elements which also are predicates. This clause of the condition is satisfied if at least one of the two elements in the array are satisfied.
+
+        </ResponseField>
+
+        <ResponseField name="not" type="object (optional)">
+
+          The value is also a predicate. This clause of the condition is satisfied if the value is _not_ satisfied.
+
+        </ResponseField>
+
+        <ResponseField name="absBefore" type="string (optional)">
+
+          A customized ISO 8601 formatted string representing a deadline for when the claimable balance can be claimed. If the balance is claimed before the date then this clause of the condition is satisfied. The format of this date string is a custom extension on top of ISO 8601 format. It allows for years to be outside the 0000-9999 range. The dates are derived from a unix epoch value in range of signed 64 bit integer. This means the date expresses a much larger calendar range of 292277026596 years into future and -292471206707 years back in past. This custom extension format will add a `'+'` prefix on values that go beyond year 9999 into the future and for years that are prior to year 0(B.C per Gregorian calendar) it will add prefix of `'-'`. Here are examples of date string values that are possible: `'2022-02-10T15:30:22Z'` `'+39121901036-03-29T15:30:22Z'` `'-7025-12-23T00:00:00Z'`
+
+        </ResponseField>
+
+        <ResponseField name="absBeforeEpoch" type="string (optional)">
+
+          A unix epoch value in seconds representing the same deadline date for when the claimable balance can be claimed. It is the same date/time value that absBefore represents, just expressed in integral unix epoch seconds within the range of a signed 64bit integer.
+
+        </ResponseField>
+
+        <ResponseField name="relBefore" type="string (optional)">
+
+          A relative deadline for when the claimable balance can be claimed. The value represents the number of seconds since the close time of the ledger which created the claimable balance.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+The [latest ledger](../../structure/consistency) known to Horizon is included as an HTTP header in the response.
+
+```json Example
 {
   "_links": {
     "self": {
@@ -114,5 +159,3 @@ The [latest ledger](../../structure/consistency.mdx) known to Horizon is include
   "last_modified_time": "2020-02-26T19:29:16Z"
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/effects/README.mdx b/docs/data/apis/horizon/api-reference/resources/effects/README.mdx
deleted file mode 100644
index 6393bc07e..000000000
--- a/docs/data/apis/horizon/api-reference/resources/effects/README.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Effects
-order: 0
----
-
-Effects represent specific changes that occur in the ledger as a result of successful operations, but are not necessarily directly reflected in the ledger or history, as transactions and operations are.
-
-<EndpointsTable title="Endpoints">
-
-|     |                                            |
-| --- | ------------------------------------------ |
-| GET | [/effects](../../list-all-effects.api.mdx) |
-
-</EndpointsTable>
diff --git a/docs/data/apis/horizon/api-reference/resources/effects/index.mdx b/docs/data/apis/horizon/api-reference/resources/effects/index.mdx
new file mode 100644
index 000000000..3ffab2e1e
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/resources/effects/index.mdx
@@ -0,0 +1,9 @@
+---
+title: Effects
+description: "Effects represent specific changes that occur in the ledger as a result of successful operations, but are not necessarily directly reflected in the ledger or history, as transactions and operations are."
+order: 0
+---
+
+| Endpoints |  |
+| --- | --- |
+| GET | [/effects](/docs/data/apis/horizon/api-reference/list-all-effects) |
diff --git a/docs/data/apis/horizon/api-reference/resources/effects/types.mdx b/docs/data/apis/horizon/api-reference/resources/effects/types.mdx
index 54cef9708..c21238678 100644
--- a/docs/data/apis/horizon/api-reference/resources/effects/types.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/effects/types.mdx
@@ -1,5 +1,6 @@
 ---
 title: Effect Types
+description: "There are eight groups of effect types."
 order: 10
 ---
 
@@ -7,242 +8,316 @@ There are eight groups of effect types. Each effect type has its own set of attr
 
 ### Account Effects
 
-<AttributeTable>
-
-- TYPE
-  - skip
-  - OPERATION(S)
-- Account Created
-  - skip
-  - create_account
-- Account Removed
-  - skip
-  - merge_account
-- Account Credited
-  - skip
-  - create_account, payment, path_payment, merge_account
-- Account Debited
-  - skip
-  - create_account, payment, path_payment, merge_account
-- Account Thresholds Updated
-  - skip
-  - set_options
-- Account Home Domain Updated
-  - skip
-  - set_options
-- Account Flags Updated
-  - skip
-  - set_options
-- Account Inflation Destination Updated
-  - skip
-  - set_options
-
-</AttributeTable>
+<ResponseField name="Account Created">
+
+create_account
+
+</ResponseField>
+
+<ResponseField name="Account Removed">
+
+merge_account
+
+</ResponseField>
+
+<ResponseField name="Account Credited">
+
+create_account, payment, path_payment, merge_account
+
+</ResponseField>
+
+<ResponseField name="Account Debited">
+
+create_account, payment, path_payment, merge_account
+
+</ResponseField>
+
+<ResponseField name="Account Thresholds Updated">
+
+set_options
+
+</ResponseField>
+
+<ResponseField name="Account Home Domain Updated">
+
+set_options
+
+</ResponseField>
+
+<ResponseField name="Account Flags Updated">
+
+set_options
+
+</ResponseField>
+
+<ResponseField name="Account Inflation Destination Updated">
+
+set_options
+
+</ResponseField>
 
 ### Signer Effects
 
-<AttributeTable>
+<ResponseField name="Signer Created">
+
+set_options
 
-- TYPE
-  - skip
-  - OPERATION(S)
-- Signer Created
-  - skip
-  - set_options
-- Signer Removed
-  - skip
-  - set_options
-- Signer Updated
-  - skip
-  - set_options
+</ResponseField>
 
-</AttributeTable>
+<ResponseField name="Signer Removed">
+
+set_options
+
+</ResponseField>
+
+<ResponseField name="Signer Updated">
+
+set_options
+
+</ResponseField>
 
 ### Trustline Effects
 
-<AttributeTable>
-
-- TYPE
-  - skip
-  - OPERATION(S)
-- Trustline Created
-  - skip
-  - change_trust
-- Trustline Removed
-  - skip
-  - change_trust
-- Trustline Updated
-  - skip
-  - change_trust, allow_trust
-- Trustline Authorized
-  - skip
-  - allow_trust
-- Trustline Deauthorized
-  - skip
-  - allow_trust
-
-</AttributeTable>
+<ResponseField name="Trustline Created">
+
+change_trust
+
+</ResponseField>
+
+<ResponseField name="Trustline Removed">
+
+change_trust
+
+</ResponseField>
+
+<ResponseField name="Trustline Updated">
+
+change_trust, allow_trust
+
+</ResponseField>
+
+<ResponseField name="Trustline Authorized">
+
+allow_trust
+
+</ResponseField>
+
+<ResponseField name="Trustline Deauthorized">
+
+allow_trust
+
+</ResponseField>
 
 ### Trading Effects
 
-<AttributeTable>
+<ResponseField name="Offer Created">
+
+Unused; not emitted
+
+</ResponseField>
+
+<ResponseField name="Offer Removed">
+
+Unused; not emitted
+
+</ResponseField>
 
-- TYPE
-  - skip
-  - STATUS / OPERATION(S)
-- Offer Created
-  - skip
-  - Unused; not emitted
-- Offer Removed
-  - skip
-  - Unused; not emitted
-- Offer Updated
-  - skip
-  - Unused; not emitted
-- Trade
-  - skip
-  - manage_buy_offer, manage_sell_offer, create_passive_sell_offer, path_payment
+<ResponseField name="Offer Updated">
 
-</AttributeTable>
+Unused; not emitted
 
-:::note[Offer Lifecycle]
+</ResponseField>
 
-Although offer identifiers were [historically defined](https://github.com/stellar/stellar-horizon/blob/main/internal/db2/history/main.go#L114-L122), [manage_offer](../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#manage-sell-offer)'s effects don't have ingestion code. To view them, decode the transaction's [`result_xdr`](../../structure/xdr.mdx), which contains the `ManageOfferSuccessResult`.
+<ResponseField name="Trade">
 
-Use [List All Offers](../../get-all-offers.api.mdx) to inspect currently open offers and [Retrieve an Offer's Trades](../../get-trades-by-offer-id.api.mdx) for retained trade history associated with an offer.
+manage_buy_offer, manage_sell_offer, create_passive_sell_offer, path_payment
 
-:::
+</ResponseField>
+
+<Note>
+
+**Offer Lifecycle**
+
+Although offer identifiers were [historically defined](https://github.com/stellar/stellar-horizon/blob/main/internal/db2/history/main.go#L114-L122), [manage_offer](../../../../../../learn/fundamentals/transactions/list-of-operations#manage-sell-offer)'s effects don't have ingestion code. To view them, decode the transaction's [`result_xdr`](../../structure/xdr), which contains the `ManageOfferSuccessResult`.
+
+Use [List All Offers](/docs/data/apis/horizon/api-reference/get-all-offers) to inspect currently open offers and [Retrieve an Offer's Trades](/docs/data/apis/horizon/api-reference/get-trades-by-offer-id) for retained trade history associated with an offer.
+
+</Note>
 
 ### Data Effects
 
-<AttributeTable>
+<ResponseField name="Data Created">
+
+manage_data
+
+</ResponseField>
+
+<ResponseField name="Data Removed">
 
-- TYPE
-  - skip
-  - OPERATION(S)
-- Data Created
-  - skip
-  - manage_data
-- Data Removed
-  - skip
-  - manage_data
-- Data Updated
-  - skip
-  - manage_data
+manage_data
 
-</AttributeTable>
+</ResponseField>
+
+<ResponseField name="Data Updated">
+
+manage_data
+
+</ResponseField>
 
 ### Claimable Balance Effects
 
-<AttributeTable>
+<ResponseField name="Claimable Balance Created">
+
+create_claimable_balance
+
+</ResponseField>
+
+<ResponseField name="Claimable Balance Claimant Created">
+
+create_claimable_balance
 
-- TYPE
-  - skip
-  - OPERATION(S)
-- Claimable Balance Created
-  - skip
-  - create_claimable_balance
-- Claimable Balance Claimant Created
-  - skip
-  - create_claimable_balance
-- Claimable Balance Claimed
-  - skip
-  - claim_claimable_balance
+</ResponseField>
 
-</AttributeTable>
+<ResponseField name="Claimable Balance Claimed">
+
+claim_claimable_balance
+
+</ResponseField>
 
 ### Sponsorship Effects
 
-<AttributeTable>
-
-- TYPE
-  - skip
-  - OPERATION(S)
-- Account Sponsorship Created
-  - skip
-  - create_account
-- Account Sponsorship Updated
-  - skip
-  - revoke_sponsorship
-- Account Sponsorship Removed
-  - skip
-  - revoke_sponsorship
-- Trustline Sponsorship Created
-  - skip
-  - change_trust
-- Trustline Sponsorship Updated
-  - skip
-  - revoke_sponsorship
-- Trustline Sponsorship Removed
-  - skip
-  - revoke_sponsorship
-- Account Data Sponsorship Created
-  - skip
-  - manage_data
-- Account Data Sponsorship Updated
-  - skip
-  - revoke_sponsorship
-- Account Data Sponsorship Removed
-  - skip
-  - revoke_sponsorship
-- Claimable Balance Sponsorship Created
-  - skip
-  - create_claimable_balance
-- Claimable Balance Sponsorship Updated
-  - skip
-  - revoke_sponsorship
-- Claimable Balance Sponsorship Removed
-  - skip
-  - revoke_sponsorship
-- Account Signer Sponsorship Created
-  - skip
-  - set_options
-- Account Signer Sponsorship Updated
-  - skip
-  - revoke_sponsorship
-- Account Signer Sponsorship Removed
-  - skip
-  - revoke_sponsorship
-
-</AttributeTable>
+<ResponseField name="Account Sponsorship Created">
+
+create_account
+
+</ResponseField>
+
+<ResponseField name="Account Sponsorship Updated">
+
+revoke_sponsorship
+
+</ResponseField>
+
+<ResponseField name="Account Sponsorship Removed">
+
+revoke_sponsorship
+
+</ResponseField>
+
+<ResponseField name="Trustline Sponsorship Created">
+
+change_trust
+
+</ResponseField>
+
+<ResponseField name="Trustline Sponsorship Updated">
+
+revoke_sponsorship
+
+</ResponseField>
+
+<ResponseField name="Trustline Sponsorship Removed">
+
+revoke_sponsorship
+
+</ResponseField>
+
+<ResponseField name="Account Data Sponsorship Created">
+
+manage_data
+
+</ResponseField>
+
+<ResponseField name="Account Data Sponsorship Updated">
+
+revoke_sponsorship
+
+</ResponseField>
+
+<ResponseField name="Account Data Sponsorship Removed">
+
+revoke_sponsorship
+
+</ResponseField>
+
+<ResponseField name="Claimable Balance Sponsorship Created">
+
+create_claimable_balance
+
+</ResponseField>
+
+<ResponseField name="Claimable Balance Sponsorship Updated">
+
+revoke_sponsorship
+
+</ResponseField>
+
+<ResponseField name="Claimable Balance Sponsorship Removed">
+
+revoke_sponsorship
+
+</ResponseField>
+
+<ResponseField name="Account Signer Sponsorship Created">
+
+set_options
+
+</ResponseField>
+
+<ResponseField name="Account Signer Sponsorship Updated">
+
+revoke_sponsorship
+
+</ResponseField>
+
+<ResponseField name="Account Signer Sponsorship Removed">
+
+revoke_sponsorship
+
+</ResponseField>
 
 ### Liquidity Pool Effects
 
-<AttributeTable>
-
-- TYPE
-  - skip
-  - OPERATION(S)
-- Liquidity Pool Created
-  - skip
-  - change_trust
-- Liquidity Pool Removed
-  - skip
-  - change_trust
-- Liquidity Pool Revoked
-  - skip
-  - change_trust, allow_trust
-- Liquidity Pool Deposited
-  - skip
-  - liquidity_pool_deposit
-- Liquidity Pool Withdraw
-  - skip
-  - liquidity_pool_withdraw
-- Liquidity Pool Trade
-  - skip
-  - path_payment
-
-</AttributeTable>
+<ResponseField name="Liquidity Pool Created">
+
+change_trust
+
+</ResponseField>
+
+<ResponseField name="Liquidity Pool Removed">
+
+change_trust
+
+</ResponseField>
+
+<ResponseField name="Liquidity Pool Revoked">
+
+change_trust, allow_trust
+
+</ResponseField>
+
+<ResponseField name="Liquidity Pool Deposited">
+
+liquidity_pool_deposit
+
+</ResponseField>
+
+<ResponseField name="Liquidity Pool Withdraw">
+
+liquidity_pool_withdraw
+
+</ResponseField>
+
+<ResponseField name="Liquidity Pool Trade">
+
+path_payment
+
+</ResponseField>
 
 ### Miscellaneous Effects
 
-<AttributeTable>
+<ResponseField name="Sequence Bumped">
 
-- TYPE
-  - skip
-  - OPERATION(S)
-- Sequence Bumped
-  - skip
-  - bump_sequence
+bump_sequence
 
-</AttributeTable>
+</ResponseField>
diff --git a/docs/data/apis/horizon/api-reference/resources/index.mdx b/docs/data/apis/horizon/api-reference/resources/index.mdx
new file mode 100644
index 000000000..a0eebd3f1
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/resources/index.mdx
@@ -0,0 +1,17 @@
+---
+title: Resources
+description: "Data on the Stellar ledger is organized according to resources. Each resource has several different endpoints."
+---
+
+| Resource Types |  |
+| --- | --- |
+| [Ledgers](/docs/data/apis/horizon/api-reference/resources/ledgers) |  |
+| [Transactions](/docs/data/apis/horizon/api-reference/resources/transactions) |  |
+| [Operations](/docs/data/apis/horizon/api-reference/resources/operations) |  |
+| [Effects](/docs/data/apis/horizon/api-reference/resources/effects) |  |
+| [Accounts](/docs/data/apis/horizon/api-reference/resources/accounts) |  |
+| [Offers](/docs/data/apis/horizon/api-reference/resources/offers) |  |
+| [Claimable Balances](/docs/data/apis/horizon/api-reference/resources/claimablebalances) |  |
+| [Trades](/docs/data/apis/horizon/api-reference/resources/trades) |  |
+| [Assets](/docs/data/apis/horizon/api-reference/resources/assets) |  |
+| [Liquidity Pools](/docs/data/apis/horizon/api-reference/resources/liquiditypools) |  |
diff --git a/docs/data/apis/horizon/api-reference/resources/ledgers/README.mdx b/docs/data/apis/horizon/api-reference/resources/ledgers/README.mdx
deleted file mode 100644
index 9132280d7..000000000
--- a/docs/data/apis/horizon/api-reference/resources/ledgers/README.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: Ledgers
-order: 0
----
-
-Each ledger stores the state of the network at a point in time and contains all the changes - transactions, operations, effects, etc. - to that state.
-
-Learn more about [ledgers](../../../../../../learn/glossary.mdx#ledger).
-
-<EndpointsTable title="Endpoints">
-
-|  |  |
-| --- | --- |
-| GET | [/ledgers/:ledger_sequence](../../retrieve-a-ledger.api.mdx) |
-| GET | [/ledgers/:ledger_sequence/transactions](../../retrieve-a-ledgers-transactions.api.mdx) |
-| GET | [/ledgers/:ledger_sequence/operations](../../retrieve-a-ledgers-operations.api.mdx) |
-| GET | [/ledgers/:ledger_sequence/payments](../../retrieve-a-ledgers-payments.api.mdx) |
-| GET | [/ledgers/:ledger_sequence/effects](../../retrieve-a-ledgers-effects.api.mdx) |
-| GET | [/ledgers](../../list-all-ledgers.api.mdx) |
-
-</EndpointsTable>
diff --git a/docs/data/apis/horizon/api-reference/resources/ledgers/index.mdx b/docs/data/apis/horizon/api-reference/resources/ledgers/index.mdx
new file mode 100644
index 000000000..0d61162c6
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/resources/ledgers/index.mdx
@@ -0,0 +1,16 @@
+---
+title: Ledgers
+description: "Each ledger stores the state of the network at a point in time and contains all the changes - transactions, operations, effects, etc. - to that state."
+order: 0
+---
+
+Learn more about [ledgers](/docs/learn/glossary#ledger).
+
+| Endpoints |  |
+| --- | --- |
+| GET | [/ledgers/:ledger_sequence](/docs/data/apis/horizon/api-reference/retrieve-a-ledger) |
+| GET | [/ledgers/:ledger_sequence/transactions](/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions) |
+| GET | [/ledgers/:ledger_sequence/operations](/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations) |
+| GET | [/ledgers/:ledger_sequence/payments](/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments) |
+| GET | [/ledgers/:ledger_sequence/effects](/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects) |
+| GET | [/ledgers](/docs/data/apis/horizon/api-reference/list-all-ledgers) |
diff --git a/docs/data/apis/horizon/api-reference/resources/ledgers/object.mdx b/docs/data/apis/horizon/api-reference/resources/ledgers/object.mdx
index f12c00717..c7facb502 100644
--- a/docs/data/apis/horizon/api-reference/resources/ledgers/object.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/ledgers/object.mdx
@@ -1,72 +1,114 @@
 ---
 title: The Ledger Object
+description: "When Horizon returns information about a ledger, it uses the following format."
 order: 10
 ---
 
 When Horizon returns information about a ledger, it uses the following format:
 
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- id
-  - string
-  - A unique identifier for this ledger.
-- paging_token
-  - number
-  - A cursor value for use in [pagination](../../structure/pagination/README.mdx).
-- hash
-  - string
-  - A hex-encoded SHA-256 hash of this ledger’s [XDR](../../../../../../learn/fundamentals/data-format/xdr.mdx)-encoded form.
-- prev_hash
-  - string
-  - The hash of the ledger immediately preceding this ledger.
-- sequence
-  - number
-  - The sequence number of this ledger, and the parameter used in Horizon calls that require a ledger number.
-- successful_transaction_count
-  - number
-  - The number of successful transactions in this ledger.
-- failed_transaction_count
-  - number
-  - The number of failed transactions in this ledger.
-- operation_count
-  - number
-  - The number of operations applied in this ledger.
-- tx_set_operation_count
-  - number
-  - The number of total operations in the transaction set (including failed transactions).
-- closed_at
-  - string
-  - An [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) formatted string of when this ledger was closed.
-- total_coins
-  - string
-  - The total number of lumens in circulation.
-- fee_pool
-  - string
-  - The sum of all transaction fees.
-- base_fee_in_stroops
-  - number
-  - The fee the network charges per operation in a transaction.
-- base_reserve_in_stroops
-  - number
-  - The reserve the network uses when calculating an account’s minimum balance.
-- max_tx_set_size
-  - number
-  - The maximum number of operations validators have agreed to process in a given ledger. Since Protocol 11, ledger capacity has been measured in operations rather than transactions. For more info on that decision, see [CAP-5](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0005.md#repurposing-ledgerheadermaxtxsetsize).
-- protocol_version
-  - number
-  - The protocol version that the Stellar network was running when this ledger was committed.
-- header_xdr
-  - string
-  - A base64 encoded string of the raw `LedgerHeader` xdr struct for this ledger.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
+<ResponseField name="id" type="string">
+
+A unique identifier for this ledger.
+
+</ResponseField>
+
+<ResponseField name="paging_token" type="number">
+
+A cursor value for use in [pagination](/docs/data/apis/horizon/api-reference/structure/pagination).
+
+</ResponseField>
+
+<ResponseField name="hash" type="string">
+
+A hex-encoded SHA-256 hash of this ledger’s [XDR](../../../../../../learn/fundamentals/data-format/xdr)-encoded form.
+
+</ResponseField>
+
+<ResponseField name="prev_hash" type="string">
+
+The hash of the ledger immediately preceding this ledger.
+
+</ResponseField>
+
+<ResponseField name="sequence" type="number">
+
+The sequence number of this ledger, and the parameter used in Horizon calls that require a ledger number.
+
+</ResponseField>
+
+<ResponseField name="successful_transaction_count" type="number">
+
+The number of successful transactions in this ledger.
+
+</ResponseField>
+
+<ResponseField name="failed_transaction_count" type="number">
+
+The number of failed transactions in this ledger.
+
+</ResponseField>
+
+<ResponseField name="operation_count" type="number">
+
+The number of operations applied in this ledger.
+
+</ResponseField>
+
+<ResponseField name="tx_set_operation_count" type="number">
+
+The number of total operations in the transaction set (including failed transactions).
+
+</ResponseField>
+
+<ResponseField name="closed_at" type="string">
+
+An [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) formatted string of when this ledger was closed.
+
+</ResponseField>
+
+<ResponseField name="total_coins" type="string">
+
+The total number of lumens in circulation.
+
+</ResponseField>
+
+<ResponseField name="fee_pool" type="string">
+
+The sum of all transaction fees.
+
+</ResponseField>
+
+<ResponseField name="base_fee_in_stroops" type="number">
+
+The fee the network charges per operation in a transaction.
+
+</ResponseField>
+
+<ResponseField name="base_reserve_in_stroops" type="number">
+
+The reserve the network uses when calculating an account’s minimum balance.
+
+</ResponseField>
+
+<ResponseField name="max_tx_set_size" type="number">
+
+The maximum number of operations validators have agreed to process in a given ledger. Since Protocol 11, ledger capacity has been measured in operations rather than transactions. For more info on that decision, see [CAP-5](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0005.md#repurposing-ledgerheadermaxtxsetsize).
+
+</ResponseField>
+
+<ResponseField name="protocol_version" type="number">
+
+The protocol version that the Stellar network was running when this ledger was committed.
+
+</ResponseField>
+
+<ResponseField name="header_xdr" type="string">
+
+A base64 encoded string of the raw `LedgerHeader` xdr struct for this ledger.
+
+</ResponseField>
+
+```json Example
 {
   "_links": {
     "self": {
@@ -108,5 +150,3 @@ When Horizon returns information about a ledger, it uses the following format:
   "header_xdr": "AAAADERtbsqB3W222vUNk8qdKXvWCxIzuR3jdlzM31A8//ywoQieYsSc05/BpgEqnLR7fKXz7t0K42V7NOjbGZA/wTEAAAAAXdLwmQAAAAAAAAAAplf68mTg/Z/DDyEZeLCoNbJnMZm4SYsYWjUjuDOSfPeRNFE4n9Hm19yKutjwVurFjk72JKVHI8J+ELwLZgWsywGZ0KIOoh6z7HlbYQAAEG9XKhRBAAABFgAAAAAH9M6YAAAAZABMS0AAAAPop9+CeMs1/7BHgFltiQPH+VT+ACYb5P0lSXh7RpBLtd34kEpeL8qKJxYz4ufmkQ2lEv/HMR/i3bi1Rt0PYj185/0kAZ3ZRbmm2mVRMzmaCOak1rn2vejHXDh+MGlr6D6vI2tc/M6VIumTKUa7SgumWDyW0r5FcJTbu/FXDQ/6C4YAAAAA"
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/liquiditypools/README.mdx b/docs/data/apis/horizon/api-reference/resources/liquiditypools/README.mdx
deleted file mode 100644
index adb801aba..000000000
--- a/docs/data/apis/horizon/api-reference/resources/liquiditypools/README.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: Liquidity Pools
-order: 0
----
-
-Liquidity Pools provide a simple, non-interactive way to trade large amounts of capital and enable high volumes of trading.
-
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
-
-<EndpointsTable title="Endpoints">
-
-|  |  |
-| --- | --- |
-| GET | [/liquidity_pools](../../list-liquidity-pools.api.mdx) |
-| GET | [/liquidity_pools/:liquidity_pool_id](../../retrieve-a-liquidity-pool.api.mdx) |
-| GET | [/liquidity_pools/:liquidity_pool_id/effects](../../retrieve-related-effects.api.mdx) |
-| GET | [/liquidity_pools/:liquidity_pool_id/trades](../../retrieve-related-trades.api.mdx) |
-| GET | [/liquidity_pools/:liquidity_pool_id/transactions](../../lp-retrieve-related-transactions.api.mdx) |
-| GET | [/liquidity_pools/:liquidity_pool_id/operations](../../lp-retrieve-related-operations.api.mdx) |
-
-</EndpointsTable>
diff --git a/docs/data/apis/horizon/api-reference/resources/liquiditypools/index.mdx b/docs/data/apis/horizon/api-reference/resources/liquiditypools/index.mdx
new file mode 100644
index 000000000..1492a1977
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/resources/liquiditypools/index.mdx
@@ -0,0 +1,16 @@
+---
+title: Liquidity Pools
+description: "Liquidity Pools provide a simple, non-interactive way to trade large amounts of capital and enable high volumes of trading."
+order: 0
+---
+
+The [latest ledger](/docs/data/apis/horizon/api-reference/structure/consistency) known to Horizon is included as an HTTP header in the response.
+
+| Endpoints |  |
+| --- | --- |
+| GET | [/liquidity_pools](/docs/data/apis/horizon/api-reference/list-liquidity-pools) |
+| GET | [/liquidity_pools/:liquidity_pool_id](/docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool) |
+| GET | [/liquidity_pools/:liquidity_pool_id/effects](/docs/data/apis/horizon/api-reference/retrieve-related-effects) |
+| GET | [/liquidity_pools/:liquidity_pool_id/trades](/docs/data/apis/horizon/api-reference/retrieve-related-trades) |
+| GET | [/liquidity_pools/:liquidity_pool_id/transactions](/docs/data/apis/horizon/api-reference/lp-retrieve-related-transactions) |
+| GET | [/liquidity_pools/:liquidity_pool_id/operations](/docs/data/apis/horizon/api-reference/lp-retrieve-related-operations) |
diff --git a/docs/data/apis/horizon/api-reference/resources/offers/README.mdx b/docs/data/apis/horizon/api-reference/resources/offers/README.mdx
deleted file mode 100644
index d88cea336..000000000
--- a/docs/data/apis/horizon/api-reference/resources/offers/README.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: Offers
-order: 0
----
-
-Offers are statements about how much of an asset an account wants to buy or sell.
-
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
-
-Learn more about [offers](../../../../../../learn/glossary.mdx#decentralized-exchange).
-
-<EndpointsTable title="Endpoints">
-
-|     |                                                                  |
-| --- | ---------------------------------------------------------------- |
-| GET | [/offers](../../get-all-offers.api.mdx)                          |
-| GET | [/offers/:offer_id](../../get-offer-by-offer-id.api.mdx)         |
-| GET | [/offers/:offer_id/trades](../../get-trades-by-offer-id.api.mdx) |
-
-</EndpointsTable>
diff --git a/docs/data/apis/horizon/api-reference/resources/offers/index.mdx b/docs/data/apis/horizon/api-reference/resources/offers/index.mdx
new file mode 100644
index 000000000..75aab0467
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/resources/offers/index.mdx
@@ -0,0 +1,15 @@
+---
+title: Offers
+description: "Offers are statements about how much of an asset an account wants to buy or sell."
+order: 0
+---
+
+The [latest ledger](/docs/data/apis/horizon/api-reference/structure/consistency) known to Horizon is included as an HTTP header in the response.
+
+Learn more about [offers](/docs/learn/glossary#decentralized-exchange).
+
+| Endpoints |  |
+| --- | --- |
+| GET | [/offers](/docs/data/apis/horizon/api-reference/get-all-offers) |
+| GET | [/offers/:offer_id](/docs/data/apis/horizon/api-reference/get-offer-by-offer-id) |
+| GET | [/offers/:offer_id/trades](/docs/data/apis/horizon/api-reference/get-trades-by-offer-id) |
diff --git a/docs/data/apis/horizon/api-reference/resources/offers/object.mdx b/docs/data/apis/horizon/api-reference/resources/offers/object.mdx
index 78dd39d83..51cad1455 100644
--- a/docs/data/apis/horizon/api-reference/resources/offers/object.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/offers/object.mdx
@@ -1,62 +1,94 @@
 ---
 title: The Offer Object
+description: "When Horizon returns information about an offer, it uses the following format."
 order: 10
 ---
 
 When Horizon returns information about an offer, it uses the following format:
 
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- id
-  - string
-  - A unique identifier for this offer.
-- paging_token
-  - number
-  - A cursor value for use in [pagination](../../structure/pagination/README.mdx).
-- seller
-  - string
-  - The account ID of the account making this offer.
-- selling
-  - asset code
-  - The asset this offer wants to sell.
-- buying
-  - asset code
-  - The asset this offer wants to buy.
-- amount
-  - string
-  - The amount of `selling` that the account making this offer is willing to sell.
-- price_r
-  - object
-  - A precise representation of the buy and sell price of the assets on offer.
-    - n
-      - number
-      - The numerator.
-    - d
-      - number
-      - The denominator.
-- price
-  - string
-  - How many units of `buying` it takes to get 1 unit of `selling`. A number representing the decimal form of `price_r`.
-- last_modified_ledger
-  - integer
-  - The sequence number of the last ledger in which this offer was modified.
-- last_modified_time
-  - string
-  - An ISO 8601 formatted string of last modification time.
-- sponsor
-  - string (optional)
-  - The account id of the sponsor who is paying the reserves for this offer.
-
-</AttributeTable>
-
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
-
-<ExampleResponse>
-
-```json
+<ResponseField name="id" type="string">
+
+A unique identifier for this offer.
+
+</ResponseField>
+
+<ResponseField name="paging_token" type="number">
+
+A cursor value for use in [pagination](/docs/data/apis/horizon/api-reference/structure/pagination).
+
+</ResponseField>
+
+<ResponseField name="seller" type="string">
+
+The account ID of the account making this offer.
+
+</ResponseField>
+
+<ResponseField name="selling" type="asset code">
+
+The asset this offer wants to sell.
+
+</ResponseField>
+
+<ResponseField name="buying" type="asset code">
+
+The asset this offer wants to buy.
+
+</ResponseField>
+
+<ResponseField name="amount" type="string">
+
+The amount of `selling` that the account making this offer is willing to sell.
+
+</ResponseField>
+
+<ResponseField name="price_r" type="object">
+
+A precise representation of the buy and sell price of the assets on offer.
+
+  <Expandable title="price_r properties">
+    <ResponseField name="n" type="number">
+
+      The numerator.
+
+    </ResponseField>
+
+    <ResponseField name="d" type="number">
+
+      The denominator.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="price" type="string">
+
+How many units of `buying` it takes to get 1 unit of `selling`. A number representing the decimal form of `price_r`.
+
+</ResponseField>
+
+<ResponseField name="last_modified_ledger" type="integer">
+
+The sequence number of the last ledger in which this offer was modified.
+
+</ResponseField>
+
+<ResponseField name="last_modified_time" type="string">
+
+An ISO 8601 formatted string of last modification time.
+
+</ResponseField>
+
+<ResponseField name="sponsor" type="string (optional)">
+
+The account id of the sponsor who is paying the reserves for this offer.
+
+</ResponseField>
+
+The [latest ledger](../../structure/consistency) known to Horizon is included as an HTTP header in the response.
+
+```json Example
 {
   "_links": {
     "self": {
@@ -87,5 +119,3 @@ The [latest ledger](../../structure/consistency.mdx) known to Horizon is include
   "last_modified_time": "2020-02-26T19:29:16Z"
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/README.mdx b/docs/data/apis/horizon/api-reference/resources/operations/README.mdx
deleted file mode 100644
index 8b293fa6d..000000000
--- a/docs/data/apis/horizon/api-reference/resources/operations/README.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: Operations
-order: 0
----
-
-Operations are objects that represent a desired change to the ledger: payments, offers to exchange currency, changes made to account options, etc. Operations are submitted to the Stellar network grouped in a Transaction.
-
-Each of Stellar’s operations have a unique operation object.
-
-<EndpointsTable title="Endpoints">
-
-|  |  |
-| --- | --- |
-| GET | [/operations/:operation_id](../../retrieve-an-operation.api.mdx) |
-| GET | [/operations/:operation_id/effects](../../retrieve-an-operations-effects.api.mdx) |
-| GET | [/operations](../../list-all-operations.api.mdx) |
-| GET | [/payments](../../list-all-payments.api.mdx) |
-
-</EndpointsTable>
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/index.mdx b/docs/data/apis/horizon/api-reference/resources/operations/index.mdx
new file mode 100644
index 000000000..37e0d505c
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/resources/operations/index.mdx
@@ -0,0 +1,14 @@
+---
+title: Operations
+description: "Operations are objects that represent a desired change to the ledger: payments, offers to exchange currency, changes made to account options, etc. Operations are submitted to the Stellar network grouped in a Transaction."
+order: 0
+---
+
+Each of Stellar’s operations have a unique operation object.
+
+| Endpoints |  |
+| --- | --- |
+| GET | [/operations/:operation_id](/docs/data/apis/horizon/api-reference/retrieve-an-operation) |
+| GET | [/operations/:operation_id/effects](/docs/data/apis/horizon/api-reference/retrieve-an-operations-effects) |
+| GET | [/operations](/docs/data/apis/horizon/api-reference/list-all-operations) |
+| GET | [/payments](/docs/data/apis/horizon/api-reference/list-all-payments) |
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/object/README.mdx b/docs/data/apis/horizon/api-reference/resources/operations/object/README.mdx
deleted file mode 100644
index ecb440f36..000000000
--- a/docs/data/apis/horizon/api-reference/resources/operations/object/README.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: The Operation Object
-order: 0
----
-
-Each of Stellar’s operations have unique response shapes. Below are the attributes that are common across individual operation objects.
-
-See the [generic Operation errors](../../../errors/result-codes/operations.mdx).
-
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- id
-  - number
-  - The operation's ID number.
-- paging_token
-  - string
-  - A cursor value for use in [pagination](../../../structure/pagination/README.mdx).
-- type_i
-  - number
-  - A number indicating the operation type.
-- type
-  - string
-  - The name of the operation type.
-- transaction_hash
-  - string
-  - A unique identifier for the transaction this operation belongs to.
-- transaction_successful
-  - boolean
-  - Indicates if this operation was part of a successful transaction.
-- source_account
-  - string
-  - The account that originates the operation.
-- created_at
-  - string
-  - The date this operation was created.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "effects": {
-      "href": "/operations/402494270214144/effects/{?cursor,limit,order}",
-      "templated": true
-    },
-    "precedes": {
-      "href": "/operations?cursor=402494270214144&order=asc"
-    },
-    "self": {
-      "href": "/operations/402494270214144"
-    },
-    "succeeds": {
-      "href": "/operations?cursor=402494270214144&order=desc"
-    },
-    "transactions": {
-      "href": "/transactions/402494270214144"
-    }
-  },
-  "id": 402494270214144,
-  "paging_token": "402494270214144",
-  "type_i": 0,
-  "type": "create_account"
-}
-```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/object/account-merge.mdx b/docs/data/apis/horizon/api-reference/resources/operations/object/account-merge.mdx
index cae8a2880..376d451d2 100644
--- a/docs/data/apis/horizon/api-reference/resources/operations/object/account-merge.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/operations/object/account-merge.mdx
@@ -1,29 +1,26 @@
 ---
 title: Account Merge Object
+description: "Removes the source account from the Stellar and transfers the source account's lumens to another account."
 order: 110
 ---
 
 Removes the source account from the Stellar and transfers the source account's lumens to another account.
 
-See the [`Account Merge` errors](../../../errors/result-codes/operation-specific/account-merge.mdx).
+See the [`Account Merge` errors](../../../errors/result-codes/operation-specific/account-merge).
 
-<AttributeTable>
+<ResponseField name="account" type="string">
 
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- account
-  - string
-  - The Stellar address being removed.
-- into
-  - string
-  - The Stellar address receiving the deleted account's lumens.
+The Stellar address being removed.
 
-</AttributeTable>
+</ResponseField>
 
-<ExampleResponse>
+<ResponseField name="into" type="string">
 
-```json
+The Stellar address receiving the deleted account's lumens.
+
+</ResponseField>
+
+```json Example
 {
   "_links": {
     "self": {
@@ -54,5 +51,3 @@ See the [`Account Merge` errors](../../../errors/result-codes/operation-specific
   "into": "GATL3ETTZ3XDGFXX2ELPIKCZL7S5D2HY3VK4T7LRPD6DW5JOLAEZSZBA"
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/object/allow-trust.mdx b/docs/data/apis/horizon/api-reference/resources/operations/object/allow-trust.mdx
index 3f0cdf2a9..52fda08e7 100644
--- a/docs/data/apis/horizon/api-reference/resources/operations/object/allow-trust.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/operations/object/allow-trust.mdx
@@ -1,41 +1,50 @@
 ---
 title: Allow Trust Object
+description: "Updates the “authorized” flag of an existing trust line."
 order: 100
 ---
 
 Updates the “authorized” flag of an existing trust line. This must be called by the issuer of the asset.
 
-See the [`Allow Trust` errors](../../../errors/result-codes/operation-specific/allow-trust.mdx).
-
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- asset_type
-  - string
-  - The type of asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
-- asset_code
-  - string
-  - The Stellar address of the asset.
-- asset_issuer
-  - string
-  - The code for the asset.
-- authorize
-  - int
-  - Flag indicating whether the trustline is authorized. 0 if the account is not authorized to transact with the asset in any way. 1 if the account is authorized to transact with the asset. 2 if the account is authorized to maintain orders, but not to perform other transactions.
-- trustee
-  - string
-  - The issuing account, or source account in this instance.
-- trustor
-  - string
-  - The trusting account, or the account being authorized or unauthorized.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
+See the [`Allow Trust` errors](../../../errors/result-codes/operation-specific/allow-trust).
+
+<ResponseField name="asset_type" type="string">
+
+The type of asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
+
+</ResponseField>
+
+<ResponseField name="asset_code" type="string">
+
+The Stellar address of the asset.
+
+</ResponseField>
+
+<ResponseField name="asset_issuer" type="string">
+
+The code for the asset.
+
+</ResponseField>
+
+<ResponseField name="authorize" type="int">
+
+Flag indicating whether the trustline is authorized. 0 if the account is not authorized to transact with the asset in any way. 1 if the account is authorized to transact with the asset. 2 if the account is authorized to maintain orders, but not to perform other transactions.
+
+</ResponseField>
+
+<ResponseField name="trustee" type="string">
+
+The issuing account, or source account in this instance.
+
+</ResponseField>
+
+<ResponseField name="trustor" type="string">
+
+The trusting account, or the account being authorized or unauthorized.
+
+</ResponseField>
+
+```json Example
 {
   "_links": {
     "self": {
@@ -70,5 +79,3 @@ See the [`Allow Trust` errors](../../../errors/result-codes/operation-specific/a
   "authorize": true
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/object/begin-sponsoring-future-reserves.mdx b/docs/data/apis/horizon/api-reference/resources/operations/object/begin-sponsoring-future-reserves.mdx
index f9026568b..59bdef358 100644
--- a/docs/data/apis/horizon/api-reference/resources/operations/object/begin-sponsoring-future-reserves.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/operations/object/begin-sponsoring-future-reserves.mdx
@@ -1,24 +1,18 @@
 ---
 title: Begin Sponsoring Future Reserves
+description: "Initiate a sponsorship."
 order: 160
 ---
 
 Initiate a sponsorship.
 
-<AttributeTable>
+<ResponseField name="sponsored_id" type="string">
 
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- sponsored_id
-  - string
-  - The id of the account which will be sponsored.
+The id of the account which will be sponsored.
 
-</AttributeTable>
+</ResponseField>
 
-<ExampleResponse>
-
-```json
+```json Example
 {
   "_links": {
     "self": {
@@ -48,5 +42,3 @@ Initiate a sponsorship.
   "sponsored_id": "GC3C4AKRBQLHOJ45U4XG35ESVWRDECWO5XLDGYADO6DPR3L7KIDVUMML"
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/object/bump-sequence.mdx b/docs/data/apis/horizon/api-reference/resources/operations/object/bump-sequence.mdx
index 496e2f269..df2a296bd 100644
--- a/docs/data/apis/horizon/api-reference/resources/operations/object/bump-sequence.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/operations/object/bump-sequence.mdx
@@ -1,26 +1,20 @@
 ---
 title: Bump Sequence Object
+description: "Bumps forward the sequence number of the source account, allowing it to invalidate any transactions with a smaller sequence number."
 order: 130
 ---
 
 Bumps forward the sequence number of the source account, allowing it to invalidate any transactions with a smaller sequence number.
 
-See the [`Bump Sequence` errors](../../../errors/result-codes/operation-specific/bump-sequence.mdx).
+See the [`Bump Sequence` errors](../../../errors/result-codes/operation-specific/bump-sequence).
 
-<AttributeTable>
+<ResponseField name="bump_to" type="string">
 
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- bump_to
-  - string
-  - The new desired value for the source account's sequence number.
+The new desired value for the source account's sequence number.
 
-</AttributeTable>
+</ResponseField>
 
-<ExampleResponse>
-
-```json
+```json Example
 {
   "_links": {
     "self": {
@@ -50,5 +44,3 @@ See the [`Bump Sequence` errors](../../../errors/result-codes/operation-specific
   "bump_to": "120192344968520085"
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/object/buy-offer.mdx b/docs/data/apis/horizon/api-reference/resources/operations/object/buy-offer.mdx
index f38a78cd2..beba85f5d 100644
--- a/docs/data/apis/horizon/api-reference/resources/operations/object/buy-offer.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/operations/object/buy-offer.mdx
@@ -1,59 +1,88 @@
 ---
 title: Manage Buy Offer Object
+description: "Creates, updates, or deletes a buy offer to trade assets."
 order: 60
 ---
 
 Creates, updates, or deletes a buy offer to trade assets. A buy offer specifies a certain amount of the buying asset that should be sold in exchange for the minimum quantity of the selling asset.
 
-See the [`Manage Buy Offer` errors](../../../errors/result-codes/operation-specific/manage-buy-offer.mdx).
-
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- amount
-  - string
-  - The amount of `buying_asset` that the account making this offer is willing to buy.
-- price
-  - string
-  - How many units of `buying_asset` it takes to get 1 unit of `selling_asset`. A number representing the decimal form of `price_r`.
-- price_r
-  - object
-  - A precise representation of the buy and sell price of the assets on offer.
-    - n
-      - number
-      - The numerator.
-    - d
-      - number
-      - The denominator.
-- buying_asset_type
-  - string
-  - The type for the buying asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
-- buying_asset_issuer
-  - string
-  - The Stellar address of the buying asset’s issuer. Appears if the `buying_asset_type` is not `native`.
-- buying_asset_code
-  - string
-  - The code for the buying asset. Appears if the `buying_asset_type` is not `native`.
-- selling_asset_type
-  - string
-  - The type for the selling asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
-- selling_asset_issuer
-  - string
-  - The Stellar address of the selling asset’s issuer. Appears if the `selling_asset_type` is not `native`.
-- selling_asset_code
-  - string
-  - The code for the selling asset. Appears if the `selling_asset_type` is not `native`.
-- offer_id
-  - string
-  - A unique identifier for this offer.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
+See the [`Manage Buy Offer` errors](../../../errors/result-codes/operation-specific/manage-buy-offer).
+
+<ResponseField name="amount" type="string">
+
+The amount of `buying_asset` that the account making this offer is willing to buy.
+
+</ResponseField>
+
+<ResponseField name="price" type="string">
+
+How many units of `buying_asset` it takes to get 1 unit of `selling_asset`. A number representing the decimal form of `price_r`.
+
+</ResponseField>
+
+<ResponseField name="price_r" type="object">
+
+A precise representation of the buy and sell price of the assets on offer.
+
+  <Expandable title="price_r properties">
+    <ResponseField name="n" type="number">
+
+      The numerator.
+
+    </ResponseField>
+
+    <ResponseField name="d" type="number">
+
+      The denominator.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="buying_asset_type" type="string">
+
+The type for the buying asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
+
+</ResponseField>
+
+<ResponseField name="buying_asset_issuer" type="string">
+
+The Stellar address of the buying asset’s issuer. Appears if the `buying_asset_type` is not `native`.
+
+</ResponseField>
+
+<ResponseField name="buying_asset_code" type="string">
+
+The code for the buying asset. Appears if the `buying_asset_type` is not `native`.
+
+</ResponseField>
+
+<ResponseField name="selling_asset_type" type="string">
+
+The type for the selling asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
+
+</ResponseField>
+
+<ResponseField name="selling_asset_issuer" type="string">
+
+The Stellar address of the selling asset’s issuer. Appears if the `selling_asset_type` is not `native`.
+
+</ResponseField>
+
+<ResponseField name="selling_asset_code" type="string">
+
+The code for the selling asset. Appears if the `selling_asset_type` is not `native`.
+
+</ResponseField>
+
+<ResponseField name="offer_id" type="string">
+
+A unique identifier for this offer.
+
+</ResponseField>
+
+```json Example
 {
   "_links": {
     "self": {
@@ -93,5 +122,3 @@ See the [`Manage Buy Offer` errors](../../../errors/result-codes/operation-speci
   "offer_id": "0"
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/object/change-trust.mdx b/docs/data/apis/horizon/api-reference/resources/operations/object/change-trust.mdx
index 1832a97cf..bb5cd8c7b 100644
--- a/docs/data/apis/horizon/api-reference/resources/operations/object/change-trust.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/operations/object/change-trust.mdx
@@ -1,44 +1,56 @@
 ---
 title: Change Trust Object
+description: "Creates, updates, or deletes a trust line from the source account to another account's issued asset."
 order: 90
 ---
 
 Creates, updates, or deletes a trust line from the source account to another account's issued asset.
 
-See the [`Change Trust` errors](../../../errors/result-codes/operation-specific/change-trust.mdx).
-
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- asset_type
-  - string
-  - The type of asset being trusted, one of `native`, `credit_alphanum4`, `credit_alphanum12`, or `liquidity_pool_shares`.
-- asset_code
-  - string
-  - The Stellar address of the asset being trusted. (Only present for credit assets.)
-- asset_issuer
-  - string
-  - The code for the asset being trusted. (Only present for credit assets.)
-- limit
-  - string
-  - Limits the amount of an asset that the source account can hold.
-- trustee
-  - string
-  - The issuing account. (Only present for credit assets.)
-- trustor
-  - string
-  - The source account.
-- liquidity_pool_id
-  - string
-  - The liquidity pool whose trustline is being modified. (Only present for `asset_type == liquidity_pool_shares`.)
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
+See the [`Change Trust` errors](../../../errors/result-codes/operation-specific/change-trust).
+
+<ResponseField name="asset_type" type="string">
+
+The type of asset being trusted, one of `native`, `credit_alphanum4`, `credit_alphanum12`, or `liquidity_pool_shares`.
+
+</ResponseField>
+
+<ResponseField name="asset_code" type="string">
+
+The Stellar address of the asset being trusted. (Only present for credit assets.)
+
+</ResponseField>
+
+<ResponseField name="asset_issuer" type="string">
+
+The code for the asset being trusted. (Only present for credit assets.)
+
+</ResponseField>
+
+<ResponseField name="limit" type="string">
+
+Limits the amount of an asset that the source account can hold.
+
+</ResponseField>
+
+<ResponseField name="trustee" type="string">
+
+The issuing account. (Only present for credit assets.)
+
+</ResponseField>
+
+<ResponseField name="trustor" type="string">
+
+The source account.
+
+</ResponseField>
+
+<ResponseField name="liquidity_pool_id" type="string">
+
+The liquidity pool whose trustline is being modified. (Only present for `asset_type == liquidity_pool_shares`.)
+
+</ResponseField>
+
+```json Example
 {
   "_links": {
     "self": {
@@ -73,5 +85,3 @@ See the [`Change Trust` errors](../../../errors/result-codes/operation-specific/
   "trustor": "GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA"
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/object/claim-claimable-balance.mdx b/docs/data/apis/horizon/api-reference/resources/operations/object/claim-claimable-balance.mdx
index be77906df..c39db5cb4 100644
--- a/docs/data/apis/horizon/api-reference/resources/operations/object/claim-claimable-balance.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/operations/object/claim-claimable-balance.mdx
@@ -1,27 +1,24 @@
 ---
 title: Claim Claimable Balance
+description: "Claims a claimable balance."
 order: 150
 ---
 
 Claims a claimable balance.
 
-<AttributeTable>
+<ResponseField name="balance_id" type="string">
 
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- balance_id
-  - string
-  - The id of the claimable balance.
-- claimant
-  - string
-  - The id of the account which claimed the balance.
+The id of the claimable balance.
 
-</AttributeTable>
+</ResponseField>
 
-<ExampleResponse>
+<ResponseField name="claimant" type="string">
 
-```json
+The id of the account which claimed the balance.
+
+</ResponseField>
+
+```json Example
 {
   "_links": {
     "self": {
@@ -52,5 +49,3 @@ Claims a claimable balance.
   "claimant": "GC3C4AKRBQLHOJ45U4XG35ESVWRDECWO5XLDGYADO6DPR3L7KIDVUMML"
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/object/create-account.mdx b/docs/data/apis/horizon/api-reference/resources/operations/object/create-account.mdx
index 4ca9eb52c..7741ba495 100644
--- a/docs/data/apis/horizon/api-reference/resources/operations/object/create-account.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/operations/object/create-account.mdx
@@ -1,32 +1,32 @@
 ---
 title: Create Account Object
+description: "Creates and funds a new account with the specified starting balance."
 order: 10
 ---
 
 Creates and funds a new account with the specified starting balance.
 
-See the [`Create Account` errors](../../../errors/result-codes/operation-specific/create-account.mdx).
+See the [`Create Account` errors](../../../errors/result-codes/operation-specific/create-account).
 
-<AttributeTable>
+<ResponseField name="starting_balance" type="string">
 
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- starting_balance
-  - string
-  - The amount of XLM to send the newly created account.
-- funder
-  - string
-  - The account that funds the new account.
-- account
-  - string
-  - A new account that is funded.
+The amount of XLM to send the newly created account.
 
-</AttributeTable>
+</ResponseField>
 
-<ExampleResponse>
+<ResponseField name="funder" type="string">
 
-```json
+The account that funds the new account.
+
+</ResponseField>
+
+<ResponseField name="account" type="string">
+
+A new account that is funded.
+
+</ResponseField>
+
+```json Example
 {
   "_links": {
     "self": {
@@ -58,5 +58,3 @@ See the [`Create Account` errors](../../../errors/result-codes/operation-specifi
   "account": "GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA"
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/object/create-claimable-balance.mdx b/docs/data/apis/horizon/api-reference/resources/operations/object/create-claimable-balance.mdx
index 1284e01f6..00415a1bd 100644
--- a/docs/data/apis/horizon/api-reference/resources/operations/object/create-claimable-balance.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/operations/object/create-claimable-balance.mdx
@@ -1,61 +1,91 @@
 ---
 title: Create Claimable Balance
+description: "Creates a new claimable balance."
 order: 140
 ---
 
 Creates a new claimable balance.
 
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- asset
-  - string
-  - The asset available to be claimed in the [SEP-11 form](https://github.com/stellar/stellar-protocol/blob/0c675fb3a482183dcf0f5db79c12685acf82a95c/ecosystem/sep-0011.md#values) `asset_code:issuing_address` or `native` (for XLM)
-- amount
-  - string
-  - The amount available to be claimed.
-- claimants
-  - array of objects
-  - The list of entries which could claim the claimable balance.
-    - destination
-      - string
-      - The account ID who can claim the balance.
-    - predicate
-      - object
-      - The condition which must be satisfied so `destination` can claim the balance.
-        - unconditional
-          - boolean (optional)
-          - If true it means this clause of the condition is always satisfied.
-        - and
-          - array of objects (optional)
-          - The array will always contain two elements which also are predicates. This clause of the condition is satisfied if both of the two elements in the array are satisfied.
-        - or
-          - array of objects (optional)
-          - The array will always contain two elements which also are predicates. This clause of the condition is satisfied if at least one of the two elements in the array are satisfied.
-        - not
-          - object (optional)
-          - The value is also a predicate. This clause of the condition is satisfied if the value is _not_ satisfied.
-        - absBefore
-          - string (optional)
-          - A customized ISO 8601 formatted string representing a deadline for when the claimable balance can be claimed. If the balance is claimed before the date then this clause of the condition is satisfied. The format of this date string is a custom extension on top of ISO 8601 format. It allows for years to be outside the 0000-9999 range. The dates are derived from a unix epoch value in range of signed 64 bit integer. This means the date expresses a much larger calendar range of 292277026596 years into future and -292471206707 years back in past. This custom extension format will add a `'+'` prefix on values that go beyond year 9999 into the future and for years that are prior to year 0(B.C per Gregorian calendar) it will add prefix of `'-'`. \
-            Here are examples of date string values that are possible: \
-            `'2022-02-10T15:30:22Z'` \
-            `'+39121901036-03-29T15:30:22Z'` \
-            `'-7025-12-23T00:00:00Z'`
-        - absBeforeEpoch
-          - string (optional)
-          - A unix epoch value in seconds representing the same deadline date for when the claimable balance can be claimed. It is the same date/time value that absBefore represents, just expressed in integral unix epoch seconds within the range of a signed 64bit integer.
-        - relBefore
-          - string (optional)
-          - A relative deadline for when the claimable balance can be claimed. The value represents the number of seconds since the close time of the ledger which created the claimable balance.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
+<ResponseField name="asset" type="string">
+
+The asset available to be claimed in the [SEP-11 form](https://github.com/stellar/stellar-protocol/blob/0c675fb3a482183dcf0f5db79c12685acf82a95c/ecosystem/sep-0011.md#values) `asset_code:issuing_address` or `native` (for XLM)
+
+</ResponseField>
+
+<ResponseField name="amount" type="string">
+
+The amount available to be claimed.
+
+</ResponseField>
+
+<ResponseField name="claimants" type="array of objects">
+
+The list of entries which could claim the claimable balance.
+
+  <Expandable title="claimants properties">
+    <ResponseField name="destination" type="string">
+
+      The account ID who can claim the balance.
+
+    </ResponseField>
+
+    <ResponseField name="predicate" type="object">
+
+      The condition which must be satisfied so `destination` can claim the balance.
+
+      <Expandable title="predicate properties">
+        <ResponseField name="unconditional" type="boolean (optional)">
+
+          If true it means this clause of the condition is always satisfied.
+
+        </ResponseField>
+
+        <ResponseField name="and" type="array of objects (optional)">
+
+          The array will always contain two elements which also are predicates. This clause of the condition is satisfied if both of the two elements in the array are satisfied.
+
+        </ResponseField>
+
+        <ResponseField name="or" type="array of objects (optional)">
+
+          The array will always contain two elements which also are predicates. This clause of the condition is satisfied if at least one of the two elements in the array are satisfied.
+
+        </ResponseField>
+
+        <ResponseField name="not" type="object (optional)">
+
+          The value is also a predicate. This clause of the condition is satisfied if the value is _not_ satisfied.
+
+        </ResponseField>
+
+        <ResponseField name="absBefore" type="string (optional)">
+
+          A customized ISO 8601 formatted string representing a deadline for when the claimable balance can be claimed. If the balance is claimed before the date then this clause of the condition is satisfied. The format of this date string is a custom extension on top of ISO 8601 format. It allows for years to be outside the 0000-9999 range. The dates are derived from a unix epoch value in range of signed 64 bit integer. This means the date expresses a much larger calendar range of 292277026596 years into future and -292471206707 years back in past. This custom extension format will add a `'+'` prefix on values that go beyond year 9999 into the future and for years that are prior to year 0(B.C per Gregorian calendar) it will add prefix of `'-'`. \
+          Here are examples of date string values that are possible: \
+          `'2022-02-10T15:30:22Z'` \
+          `'+39121901036-03-29T15:30:22Z'` \
+          `'-7025-12-23T00:00:00Z'`
+
+        </ResponseField>
+
+        <ResponseField name="absBeforeEpoch" type="string (optional)">
+
+          A unix epoch value in seconds representing the same deadline date for when the claimable balance can be claimed. It is the same date/time value that absBefore represents, just expressed in integral unix epoch seconds within the range of a signed 64bit integer.
+
+        </ResponseField>
+
+        <ResponseField name="relBefore" type="string (optional)">
+
+          A relative deadline for when the claimable balance can be claimed. The value represents the number of seconds since the close time of the ledger which created the claimable balance.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+```json Example
 {
   "_links": {
     "self": {
@@ -109,5 +139,3 @@ Creates a new claimable balance.
   ]
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/object/end-sponsoring-future-reserves.mdx b/docs/data/apis/horizon/api-reference/resources/operations/object/end-sponsoring-future-reserves.mdx
index cd3fce27e..6bc3138f8 100644
--- a/docs/data/apis/horizon/api-reference/resources/operations/object/end-sponsoring-future-reserves.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/operations/object/end-sponsoring-future-reserves.mdx
@@ -1,24 +1,18 @@
 ---
 title: End Sponsoring Future Reserves
+description: "End a sponsorship."
 order: 170
 ---
 
 End a sponsorship.
 
-<AttributeTable>
+<ResponseField name="begin_sponsor" type="string">
 
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- begin_sponsor
-  - string
-  - The id of the account which initiated the sponsorship.
+The id of the account which initiated the sponsorship.
 
-</AttributeTable>
+</ResponseField>
 
-<ExampleResponse>
-
-```json
+```json Example
 {
   "_links": {
     "self": {
@@ -48,5 +42,3 @@ End a sponsorship.
   "begin_sponsor": "GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA"
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/object/extend-footprint-ttl.mdx b/docs/data/apis/horizon/api-reference/resources/operations/object/extend-footprint-ttl.mdx
index d5c2d3ada..488e74b4b 100644
--- a/docs/data/apis/horizon/api-reference/resources/operations/object/extend-footprint-ttl.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/operations/object/extend-footprint-ttl.mdx
@@ -1,24 +1,18 @@
 ---
 title: Extend Footprint TTL Object
+description: "Extends the TTL for a given set of ledger entries."
 order: 230
 ---
 
-[Extends](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#extend-footprint-ttl) the TTL for a given set of ledger entries.
+[Extends](../../../../../../../learn/fundamentals/transactions/list-of-operations#extend-footprint-ttl) the TTL for a given set of ledger entries.
 
-<AttributeTable>
+<ResponseField name="extend_to" type="number">
 
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- extend_to
-  - number
-  - The new live until ledger which will be applied to the ledger entries.
+The new live until ledger which will be applied to the ledger entries.
 
-</AttributeTable>
+</ResponseField>
 
-<ExampleResponse>
-
-```json
+```json Example
 {
   "id": "1109896858714113",
   "paging_token": "1109896858714113",
@@ -31,5 +25,3 @@ order: 230
   "extend_to": 100
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/object/index.mdx b/docs/data/apis/horizon/api-reference/resources/operations/object/index.mdx
new file mode 100644
index 000000000..21f3f9c3d
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/resources/operations/object/index.mdx
@@ -0,0 +1,82 @@
+---
+title: The Operation Object
+description: "Each of Stellar’s operations have unique response shapes. Below are the attributes that are common across individual operation objects."
+order: 0
+---
+
+See the [generic Operation errors](/docs/data/apis/horizon/api-reference/errors/result-codes/operations).
+
+<ResponseField name="id" type="number">
+
+The operation's ID number.
+
+</ResponseField>
+
+<ResponseField name="paging_token" type="string">
+
+A cursor value for use in [pagination](/docs/data/apis/horizon/api-reference/structure/pagination).
+
+</ResponseField>
+
+<ResponseField name="type_i" type="number">
+
+A number indicating the operation type.
+
+</ResponseField>
+
+<ResponseField name="type" type="string">
+
+The name of the operation type.
+
+</ResponseField>
+
+<ResponseField name="transaction_hash" type="string">
+
+A unique identifier for the transaction this operation belongs to.
+
+</ResponseField>
+
+<ResponseField name="transaction_successful" type="boolean">
+
+Indicates if this operation was part of a successful transaction.
+
+</ResponseField>
+
+<ResponseField name="source_account" type="string">
+
+The account that originates the operation.
+
+</ResponseField>
+
+<ResponseField name="created_at" type="string">
+
+The date this operation was created.
+
+</ResponseField>
+
+```json Example
+{
+  "_links": {
+    "effects": {
+      "href": "/operations/402494270214144/effects/{?cursor,limit,order}",
+      "templated": true
+    },
+    "precedes": {
+      "href": "/operations?cursor=402494270214144&order=asc"
+    },
+    "self": {
+      "href": "/operations/402494270214144"
+    },
+    "succeeds": {
+      "href": "/operations?cursor=402494270214144&order=desc"
+    },
+    "transactions": {
+      "href": "/transactions/402494270214144"
+    }
+  },
+  "id": 402494270214144,
+  "paging_token": "402494270214144",
+  "type_i": 0,
+  "type": "create_account"
+}
+```
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/object/invoke-host-function.mdx b/docs/data/apis/horizon/api-reference/resources/operations/object/invoke-host-function.mdx
index 1c0686632..7ee188fb9 100644
--- a/docs/data/apis/horizon/api-reference/resources/operations/object/invoke-host-function.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/operations/object/invoke-host-function.mdx
@@ -1,63 +1,100 @@
 ---
 title: Invoke Host Function Object
+description: "Invokes a Soroban smart contract function."
 order: 220
 ---
 
-[Invokes](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#invoke-host-function) a Soroban smart contract function.
-
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- function
-  - string
-  - The type of `InvokeHostFunctionOp` which can be one of `HostFunctionTypeHostFunctionTypeInvokeContract`, `HostFunctionTypeHostFunctionTypeCreateContract`, or `HostFunctionTypeHostFunctionTypeUploadContractWasm`.
-- parameters
-  - array
-  - An array of parameters passed into the Soroban smart contract function (only present when the type of `InvokeHostFunctionOp` is `HostFunctionTypeHostFunctionTypeInvokeContract`).
-    - type
-      - string
-      - The [type](../../../../../../../learn/fundamentals/contract-development/types/built-in-types.mdx) of the function parameter.
-    - value
-      - string
-      - The base64 encoding of the XDR value of the parameter.
-- address
-  - string
-  - The address of the newly created contract (only present when the type of `InvokeHostFunctionOp` is `HostFunctionTypeHostFunctionTypeCreateContract`).
-- salt
-  - string
-  - The salt used to create the contract (only present when the type of `InvokeHostFunctionOp` is `HostFunctionTypeHostFunctionTypeCreateContract`).
-- asset_balance_changes
-  - array
-  - An array of [Stellar Asset Contract](../../../../../../../tokens/stellar-asset-contract) balance update events that occurred as a side effect of the `InvokeHostFunctionOp` (only present when the type of `InvokeHostFunctionOp` is `HostFunctionTypeHostFunctionTypeInvokeContract` _and_ the invocation is on a Stellar Asset Contract).
-    - asset_type
-      - string
-      - The type of asset being sent. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
-    - code
-      - string
-      - The code for the asset being sent. Appears if the `asset_type` is not `native`.
-    - issuer
-      - string
-      - The Stellar address of the issuer of the asset being sent. Appears if the `asset_type` is not `native`.
-    - type
-      - string
-      - The type of the [Stellar Asset Contract event](../../../../../../../tokens/stellar-asset-contract). It can be one of `transfer`, `mint`, `clawback`, or `burn`.
-    - from
-      - string
-      - The Stellar address of the sender (can be a contract or a Stellar account). This field is not present when `type` is `mint`.
-    - to
-      - string
-      - The Stellar address of the recipient (can be a contract or a Stellar account). This field is only present when `type` is `transfer` or `mint`.
-    - amount
-      - string
-      - The amount sent.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
+[Invokes](../../../../../../../learn/fundamentals/transactions/list-of-operations#invoke-host-function) a Soroban smart contract function.
+
+<ResponseField name="function" type="string">
+
+The type of `InvokeHostFunctionOp` which can be one of `HostFunctionTypeHostFunctionTypeInvokeContract`, `HostFunctionTypeHostFunctionTypeCreateContract`, or `HostFunctionTypeHostFunctionTypeUploadContractWasm`.
+
+</ResponseField>
+
+<ResponseField name="parameters" type="array">
+
+An array of parameters passed into the Soroban smart contract function (only present when the type of `InvokeHostFunctionOp` is `HostFunctionTypeHostFunctionTypeInvokeContract`).
+
+  <Expandable title="parameters properties">
+    <ResponseField name="type" type="string">
+
+      The [type](../../../../../../../learn/fundamentals/contract-development/types/built-in-types) of the function parameter.
+
+    </ResponseField>
+
+    <ResponseField name="value" type="string">
+
+      The base64 encoding of the XDR value of the parameter.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="address" type="string">
+
+The address of the newly created contract (only present when the type of `InvokeHostFunctionOp` is `HostFunctionTypeHostFunctionTypeCreateContract`).
+
+</ResponseField>
+
+<ResponseField name="salt" type="string">
+
+The salt used to create the contract (only present when the type of `InvokeHostFunctionOp` is `HostFunctionTypeHostFunctionTypeCreateContract`).
+
+</ResponseField>
+
+<ResponseField name="asset_balance_changes" type="array">
+
+An array of [Stellar Asset Contract](../../../../../../../tokens/stellar-asset-contract) balance update events that occurred as a side effect of the `InvokeHostFunctionOp` (only present when the type of `InvokeHostFunctionOp` is `HostFunctionTypeHostFunctionTypeInvokeContract` _and_ the invocation is on a Stellar Asset Contract).
+
+  <Expandable title="asset_balance_changes properties">
+    <ResponseField name="asset_type" type="string">
+
+      The type of asset being sent. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
+
+    </ResponseField>
+
+    <ResponseField name="code" type="string">
+
+      The code for the asset being sent. Appears if the `asset_type` is not `native`.
+
+    </ResponseField>
+
+    <ResponseField name="issuer" type="string">
+
+      The Stellar address of the issuer of the asset being sent. Appears if the `asset_type` is not `native`.
+
+    </ResponseField>
+
+    <ResponseField name="type" type="string">
+
+      The type of the [Stellar Asset Contract event](../../../../../../../tokens/stellar-asset-contract). It can be one of `transfer`, `mint`, `clawback`, or `burn`.
+
+    </ResponseField>
+
+    <ResponseField name="from" type="string">
+
+      The Stellar address of the sender (can be a contract or a Stellar account). This field is not present when `type` is `mint`.
+
+    </ResponseField>
+
+    <ResponseField name="to" type="string">
+
+      The Stellar address of the recipient (can be a contract or a Stellar account). This field is only present when `type` is `transfer` or `mint`.
+
+    </ResponseField>
+
+    <ResponseField name="amount" type="string">
+
+      The amount sent.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+```json Example
 {
   "id": "1109896858714113",
   "paging_token": "1109896858714113",
@@ -91,5 +128,3 @@ order: 220
   "asset_balance_changes": []
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/object/liquidity-pool-deposit.mdx b/docs/data/apis/horizon/api-reference/resources/operations/object/liquidity-pool-deposit.mdx
index 586f11455..7f1c620df 100644
--- a/docs/data/apis/horizon/api-reference/resources/operations/object/liquidity-pool-deposit.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/operations/object/liquidity-pool-deposit.mdx
@@ -1,71 +1,118 @@
 ---
 title: Liquidity Pool Deposit Object
+description: "Deposit asset reserves into a liquidity pool."
 order: 200
 ---
 
 Deposit asset reserves into a liquidity pool.
 
-See the [`Liquidity Pool Deposit` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#liquidity-pool-deposit) for parameters, errors, etc.
-
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- liquidity_pool_id
-  - string
-  - The liquidity pool associated with this deposit
-- reserves_max
-  - array
-  - An array of objects corresponding to the maximum amount of each reserve that could've been deposited
-    - asset
-      - string
-      - The asset in canonical (`Code:Issuer`) form
-    - amount
-      - string
-      - A floating point value encoded as a string
-- min_price
-  - string
-  - A floating point value encoded as a string indicating the minimum exchange rate for this deposit operation
-- min_price_r
-  - object
-  - A precise (fractional) representation of the buy and sell price of the assets on offer.
-    - n
-      - number
-      - The numerator.
-    - d
-      - number
-      - The denominator.
-- max_price
-  - string
-  - A floating point value encoded as a string indicating the maximum exchange rate for this deposit operation
-- max_price_r
-  - object
-  - A precise (fractional) representation of the buy and sell price of the assets on offer.
-    - n
-      - number
-      - The numerator.
-    - d
-      - number
-      - The denominator.
-- reserves_deposited
-  - array
-  - An array of objects representing how much of each reserve ended up actually deposited into the pool
-    - asset
-      - string
-      - The asset in canonical (`Code:Issuer`) form
-    - amount
-      - string
-      - A floating point value encoded as a string
-- shares_received
-  - string
-  - A floating point value encoded as a string representing the number of pool shares received for this deposit
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
+See the [`Liquidity Pool Deposit` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations#liquidity-pool-deposit) for parameters, errors, etc.
+
+<ResponseField name="liquidity_pool_id" type="string">
+
+The liquidity pool associated with this deposit
+
+</ResponseField>
+
+<ResponseField name="reserves_max" type="array">
+
+An array of objects corresponding to the maximum amount of each reserve that could've been deposited
+
+  <Expandable title="reserves_max properties">
+    <ResponseField name="asset" type="string">
+
+      The asset in canonical (`Code:Issuer`) form
+
+    </ResponseField>
+
+    <ResponseField name="amount" type="string">
+
+      A floating point value encoded as a string
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="min_price" type="string">
+
+A floating point value encoded as a string indicating the minimum exchange rate for this deposit operation
+
+</ResponseField>
+
+<ResponseField name="min_price_r" type="object">
+
+A precise (fractional) representation of the buy and sell price of the assets on offer.
+
+  <Expandable title="min_price_r properties">
+    <ResponseField name="n" type="number">
+
+      The numerator.
+
+    </ResponseField>
+
+    <ResponseField name="d" type="number">
+
+      The denominator.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="max_price" type="string">
+
+A floating point value encoded as a string indicating the maximum exchange rate for this deposit operation
+
+</ResponseField>
+
+<ResponseField name="max_price_r" type="object">
+
+A precise (fractional) representation of the buy and sell price of the assets on offer.
+
+  <Expandable title="max_price_r properties">
+    <ResponseField name="n" type="number">
+
+      The numerator.
+
+    </ResponseField>
+
+    <ResponseField name="d" type="number">
+
+      The denominator.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="reserves_deposited" type="array">
+
+An array of objects representing how much of each reserve ended up actually deposited into the pool
+
+  <Expandable title="reserves_deposited properties">
+    <ResponseField name="asset" type="string">
+
+      The asset in canonical (`Code:Issuer`) form
+
+    </ResponseField>
+
+    <ResponseField name="amount" type="string">
+
+      A floating point value encoded as a string
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="shares_received" type="string">
+
+A floating point value encoded as a string representing the number of pool shares received for this deposit
+
+</ResponseField>
+
+```json Example
 {
   "id": "3697472920621057",
   "paging_token": "3697472920621057",
@@ -109,5 +156,3 @@ See the [`Liquidity Pool Deposit` operation](../../../../../../../learn/fundamen
   "shares_received": "1000"
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/object/liquidity-pool-withdraw.mdx b/docs/data/apis/horizon/api-reference/resources/operations/object/liquidity-pool-withdraw.mdx
index e6a637988..b4535272f 100644
--- a/docs/data/apis/horizon/api-reference/resources/operations/object/liquidity-pool-withdraw.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/operations/object/liquidity-pool-withdraw.mdx
@@ -1,47 +1,66 @@
 ---
 title: Liquidity Pool Withdraw Object
+description: "Withdraws asset reserves from a liquidity pool by redeeming pool shares."
 order: 210
 ---
 
 Withdraws asset reserves from a liquidity pool by redeeming pool shares.
 
-See the [`Liquidity Pool Withdraw` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#liquidity-pool-withdraw) for parameters, errors, etc.
-
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- liquidity_pool_id
-  - string
-  - The liquidity pool associated with this withdrawal
-- reserves_min
-  - array
-  - An array of objects corresponding to the minimum amount of each reserve that should've been withdrawn
-    - asset
-      - string
-      - The asset in canonical (`Code:Issuer`) form
-    - amount
-      - string
-      - A floating point value encoded as a string
-- shares
-  - string
-  - The number of shares that were redeemed for this withdrawal operation
-- reserves_received
-  - array
-  - An array of objects representing how much of each reserve ended up actually withdrawn from the pool
-    - asset
-      - string
-      - The asset in canonical (`Code:Issuer`) form
-    - amount
-      - string
-      - A floating point value encoded as a string
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
+See the [`Liquidity Pool Withdraw` operation](../../../../../../../learn/fundamentals/transactions/list-of-operations#liquidity-pool-withdraw) for parameters, errors, etc.
+
+<ResponseField name="liquidity_pool_id" type="string">
+
+The liquidity pool associated with this withdrawal
+
+</ResponseField>
+
+<ResponseField name="reserves_min" type="array">
+
+An array of objects corresponding to the minimum amount of each reserve that should've been withdrawn
+
+  <Expandable title="reserves_min properties">
+    <ResponseField name="asset" type="string">
+
+      The asset in canonical (`Code:Issuer`) form
+
+    </ResponseField>
+
+    <ResponseField name="amount" type="string">
+
+      A floating point value encoded as a string
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="shares" type="string">
+
+The number of shares that were redeemed for this withdrawal operation
+
+</ResponseField>
+
+<ResponseField name="reserves_received" type="array">
+
+An array of objects representing how much of each reserve ended up actually withdrawn from the pool
+
+  <Expandable title="reserves_received properties">
+    <ResponseField name="asset" type="string">
+
+      The asset in canonical (`Code:Issuer`) form
+
+    </ResponseField>
+
+    <ResponseField name="amount" type="string">
+
+      A floating point value encoded as a string
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+```json Example
 {
   "id": "3697472920621057",
   "paging_token": "3697472920621057",
@@ -85,5 +104,3 @@ See the [`Liquidity Pool Withdraw` operation](../../../../../../../learn/fundame
   "shares_received": "1000"
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/object/manage-data.mdx b/docs/data/apis/horizon/api-reference/resources/operations/object/manage-data.mdx
index 2425fea1a..03bd47a69 100644
--- a/docs/data/apis/horizon/api-reference/resources/operations/object/manage-data.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/operations/object/manage-data.mdx
@@ -1,29 +1,26 @@
 ---
 title: Manage Data Object
+description: "Set, modify, or delete a data entry (name/value pair) for an account."
 order: 120
 ---
 
 Set, modify, or delete a data entry (name/value pair) for an account.
 
-See the [`Manage Data` errors](../../../errors/result-codes/operation-specific/manage-data.mdx).
+See the [`Manage Data` errors](../../../errors/result-codes/operation-specific/manage-data).
 
-<AttributeTable>
+<ResponseField name="name" type="string">
 
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- name
-  - string
-  - The key for this data entry. It can be up to 64 bytes long. If this is a new `Name`, it will add the given name/value pair to the account. If this `Name` is already present, then the associated value will be modified.
-- value
-  - string
-  - If present, then this value will be set in the DataEntry. It can be up to 64 bytes long. If not present, then the existing `Name` will be deleted.
+The key for this data entry. It can be up to 64 bytes long. If this is a new `Name`, it will add the given name/value pair to the account. If this `Name` is already present, then the associated value will be modified.
 
-</AttributeTable>
+</ResponseField>
 
-<ExampleResponse>
+<ResponseField name="value" type="string">
 
-```json
+If present, then this value will be set in the DataEntry. It can be up to 64 bytes long. If not present, then the existing `Name` will be deleted.
+
+</ResponseField>
+
+```json Example
 {
   "_links": {
     "self": {
@@ -54,5 +51,3 @@ See the [`Manage Data` errors](../../../errors/result-codes/operation-specific/m
   "value": "MQ=="
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/object/passive-sell-offer.mdx b/docs/data/apis/horizon/api-reference/resources/operations/object/passive-sell-offer.mdx
index 28c46509a..2e680f066 100644
--- a/docs/data/apis/horizon/api-reference/resources/operations/object/passive-sell-offer.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/operations/object/passive-sell-offer.mdx
@@ -1,59 +1,88 @@
 ---
 title: Create Passive Sell Offer Object
+description: "Creates an offer that will not consume a counter offer that exactly matches this offer."
 order: 70
 ---
 
 Creates an offer that will not consume a counter offer that exactly matches this offer. This is useful for offers meant to be 1:1 exchanges for path payments. Use Manage Sell Offer to manage this offer after using this operation to create it.
 
-See the [`Create Passive Sell Offer` errors](../../../errors/result-codes/operation-specific/create-passive-sell-offer.mdx).
-
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- amount
-  - string
-  - The amount of `selling_asset` that the account making this offer is willing to sell.
-- price
-  - string
-  - How many units of `selling_asset` it takes to get 1 unit of `buying_asset`. A number representing the decimal form of `price_r`.
-- price_r
-  - object
-  - A precise representation of the buy and sell price of the assets on offer.
-    - n
-      - number
-      - The numerator.
-    - d
-      - number
-      - The denominator.
-- buying_asset_type
-  - string
-  - The type for the buying asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
-- buying_asset_issuer
-  - string
-  - The Stellar address of the buying asset’s issuer. Appears if the `buying_asset_type` is not `native`.
-- buying_asset_code
-  - string
-  - The code for the buying asset. Appears if the `buying_asset_type` is not `native`.
-- selling_asset_type
-  - string
-  - The type for the selling asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
-- selling_asset_issuer
-  - string
-  - The Stellar address of the selling asset’s issuer. Appears if the `selling_asset_type` is not `native`.
-- selling_asset_code
-  - string
-  - The code for the selling asset. Appears if the `selling_asset_type` is not `native`.
-- offer_id
-  - string
-  - A unique identifier for this offer.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
+See the [`Create Passive Sell Offer` errors](../../../errors/result-codes/operation-specific/create-passive-sell-offer).
+
+<ResponseField name="amount" type="string">
+
+The amount of `selling_asset` that the account making this offer is willing to sell.
+
+</ResponseField>
+
+<ResponseField name="price" type="string">
+
+How many units of `selling_asset` it takes to get 1 unit of `buying_asset`. A number representing the decimal form of `price_r`.
+
+</ResponseField>
+
+<ResponseField name="price_r" type="object">
+
+A precise representation of the buy and sell price of the assets on offer.
+
+  <Expandable title="price_r properties">
+    <ResponseField name="n" type="number">
+
+      The numerator.
+
+    </ResponseField>
+
+    <ResponseField name="d" type="number">
+
+      The denominator.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="buying_asset_type" type="string">
+
+The type for the buying asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
+
+</ResponseField>
+
+<ResponseField name="buying_asset_issuer" type="string">
+
+The Stellar address of the buying asset’s issuer. Appears if the `buying_asset_type` is not `native`.
+
+</ResponseField>
+
+<ResponseField name="buying_asset_code" type="string">
+
+The code for the buying asset. Appears if the `buying_asset_type` is not `native`.
+
+</ResponseField>
+
+<ResponseField name="selling_asset_type" type="string">
+
+The type for the selling asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
+
+</ResponseField>
+
+<ResponseField name="selling_asset_issuer" type="string">
+
+The Stellar address of the selling asset’s issuer. Appears if the `selling_asset_type` is not `native`.
+
+</ResponseField>
+
+<ResponseField name="selling_asset_code" type="string">
+
+The code for the selling asset. Appears if the `selling_asset_type` is not `native`.
+
+</ResponseField>
+
+<ResponseField name="offer_id" type="string">
+
+A unique identifier for this offer.
+
+</ResponseField>
+
+```json Example
 {
   "_links": {
     "self": {
@@ -94,5 +123,3 @@ See the [`Create Passive Sell Offer` errors](../../../errors/result-codes/operat
   "selling_asset_issuer": "GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-receive.mdx b/docs/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-receive.mdx
index fc37474ee..30de00d55 100644
--- a/docs/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-receive.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-receive.mdx
@@ -1,68 +1,106 @@
 ---
 title: Path Payment Strict Receive Object
+description: "Sends a payment from one account to another in a path through the order books, starting as one asset and ending as another."
 order: 30
 ---
 
 Sends a payment from one account to another in a path through the order books, starting as one asset and ending as another. Path payments that are `Strict Receive` designate the payment amount in the asset received.
 
-See the [`Path Payment Strict Receive` errors](../../../errors/result-codes/operation-specific/path-payment-strict-receive.mdx).
-
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- asset_type
-  - string
-  - The type of asset being received. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
-- asset_code
-  - string
-  - The code for the asset being received. Appears if the `asset_type` is not `native`.
-- asset_issuer
-  - string
-  - The Stellar address of the issuer of the asset being received. Appears if the `asset_type` is not `native`.
-- from
-  - string
-  - The payment sender’s public key.
-- to
-  - string
-  - The payment recipient’s public key.
-- amount
-  - string
-  - Amount received designated in the destination asset.
-- path
-  - array of objects
-  - The intermediary assets that this path hops through.
-    - asset_code
-      - string
-      - The code for this intermediary asset.
-    - asset_issuer
-      - string
-      - The Stellar address of the intermediary asset’s issuer.
-    - asset_type
-      - string
-      - The type for the intermediary asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
-- source_amount
-  - string
-  - Amount sent designated in the source asset.
-- source_max
-  - string
-  - The maximum amount to be sent designated in the source asset.
-- source_asset_type
-  - string
-  - The type for the source asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
-- source_asset_code
-  - string
-  - The code for the source asset.
-- source_asset_issuer
-  - string
-  - The Stellar address of the source asset’s issuer.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
+See the [`Path Payment Strict Receive` errors](../../../errors/result-codes/operation-specific/path-payment-strict-receive).
+
+<ResponseField name="asset_type" type="string">
+
+The type of asset being received. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
+
+</ResponseField>
+
+<ResponseField name="asset_code" type="string">
+
+The code for the asset being received. Appears if the `asset_type` is not `native`.
+
+</ResponseField>
+
+<ResponseField name="asset_issuer" type="string">
+
+The Stellar address of the issuer of the asset being received. Appears if the `asset_type` is not `native`.
+
+</ResponseField>
+
+<ResponseField name="from" type="string">
+
+The payment sender’s public key.
+
+</ResponseField>
+
+<ResponseField name="to" type="string">
+
+The payment recipient’s public key.
+
+</ResponseField>
+
+<ResponseField name="amount" type="string">
+
+Amount received designated in the destination asset.
+
+</ResponseField>
+
+<ResponseField name="path" type="array of objects">
+
+The intermediary assets that this path hops through.
+
+  <Expandable title="path properties">
+    <ResponseField name="asset_code" type="string">
+
+      The code for this intermediary asset.
+
+    </ResponseField>
+
+    <ResponseField name="asset_issuer" type="string">
+
+      The Stellar address of the intermediary asset’s issuer.
+
+    </ResponseField>
+
+    <ResponseField name="asset_type" type="string">
+
+      The type for the intermediary asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="source_amount" type="string">
+
+Amount sent designated in the source asset.
+
+</ResponseField>
+
+<ResponseField name="source_max" type="string">
+
+The maximum amount to be sent designated in the source asset.
+
+</ResponseField>
+
+<ResponseField name="source_asset_type" type="string">
+
+The type for the source asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
+
+</ResponseField>
+
+<ResponseField name="source_asset_code" type="string">
+
+The code for the source asset.
+
+</ResponseField>
+
+<ResponseField name="source_asset_issuer" type="string">
+
+The Stellar address of the source asset’s issuer.
+
+</ResponseField>
+
+```json Example
 {
   "_links": {
     "self": {
@@ -112,5 +150,3 @@ See the [`Path Payment Strict Receive` errors](../../../errors/result-codes/oper
   "source_asset_issuer": "GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-send.mdx b/docs/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-send.mdx
index a6d94dbac..8a9229601 100644
--- a/docs/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-send.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-send.mdx
@@ -1,68 +1,106 @@
 ---
 title: Path Payment Strict Send Object
+description: "Sends a payment from one account to another in a path through the order books, starting as one asset and ending as another."
 order: 40
 ---
 
 Sends a payment from one account to another in a path through the order books, starting as one asset and ending as another. Path payments that are `Strict Send` designate the payment amount in the asset sent.
 
-See the [`Path Payment Strict Send` errors](../../../errors/result-codes/operation-specific/path-payment-strict-send.mdx).
-
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- asset_type
-  - string
-  - The type of asset being received. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
-- asset_code
-  - string
-  - The code for the asset being received. Appears if the `asset_type` is not `native`.
-- asset_issuer
-  - string
-  - The Stellar address of the issuer of the asset being received. Appears if the `asset_type` is not `native`.
-- from
-  - string
-  - The payment sender’s public key.
-- to
-  - string
-  - The payment recipient’s public key.
-- amount
-  - string
-  - Amount received designated in the destination asset.
-- path
-  - array of objects
-  - The intermediary assets that this path hops through.
-    - asset_code
-      - string
-      - The code for this intermediary asset.
-    - asset_issuer
-      - string
-      - The Stellar address of the intermediary asset’s issuer.
-    - asset_type
-      - string
-      - The type for the intermediary asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
-- source_amount
-  - string
-  - Amount sent designated in the source asset.
-- destination_min
-  - string
-  - The minimum amount of destination asset expected to be received.
-- source_asset_type
-  - string
-  - The type for the source asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
-- source_asset_code
-  - string
-  - The code for the source asset. Appears if the `asset_type` is not `native`.
-- source_asset_issuer
-  - string
-  - The Stellar address of the source asset’s issuer. Appears if the `asset_type` is not `native`.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
+See the [`Path Payment Strict Send` errors](../../../errors/result-codes/operation-specific/path-payment-strict-send).
+
+<ResponseField name="asset_type" type="string">
+
+The type of asset being received. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
+
+</ResponseField>
+
+<ResponseField name="asset_code" type="string">
+
+The code for the asset being received. Appears if the `asset_type` is not `native`.
+
+</ResponseField>
+
+<ResponseField name="asset_issuer" type="string">
+
+The Stellar address of the issuer of the asset being received. Appears if the `asset_type` is not `native`.
+
+</ResponseField>
+
+<ResponseField name="from" type="string">
+
+The payment sender’s public key.
+
+</ResponseField>
+
+<ResponseField name="to" type="string">
+
+The payment recipient’s public key.
+
+</ResponseField>
+
+<ResponseField name="amount" type="string">
+
+Amount received designated in the destination asset.
+
+</ResponseField>
+
+<ResponseField name="path" type="array of objects">
+
+The intermediary assets that this path hops through.
+
+  <Expandable title="path properties">
+    <ResponseField name="asset_code" type="string">
+
+      The code for this intermediary asset.
+
+    </ResponseField>
+
+    <ResponseField name="asset_issuer" type="string">
+
+      The Stellar address of the intermediary asset’s issuer.
+
+    </ResponseField>
+
+    <ResponseField name="asset_type" type="string">
+
+      The type for the intermediary asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="source_amount" type="string">
+
+Amount sent designated in the source asset.
+
+</ResponseField>
+
+<ResponseField name="destination_min" type="string">
+
+The minimum amount of destination asset expected to be received.
+
+</ResponseField>
+
+<ResponseField name="source_asset_type" type="string">
+
+The type for the source asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
+
+</ResponseField>
+
+<ResponseField name="source_asset_code" type="string">
+
+The code for the source asset. Appears if the `asset_type` is not `native`.
+
+</ResponseField>
+
+<ResponseField name="source_asset_issuer" type="string">
+
+The Stellar address of the source asset’s issuer. Appears if the `asset_type` is not `native`.
+
+</ResponseField>
+
+```json Example
 {
   "_links": {
     "self": {
@@ -112,5 +150,3 @@ See the [`Path Payment Strict Send` errors](../../../errors/result-codes/operati
   "source_asset_issuer": "GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/object/restore-footprint.mdx b/docs/data/apis/horizon/api-reference/resources/operations/object/restore-footprint.mdx
index f1bb488bd..4707f3451 100644
--- a/docs/data/apis/horizon/api-reference/resources/operations/object/restore-footprint.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/operations/object/restore-footprint.mdx
@@ -1,13 +1,12 @@
 ---
 title: Restore Footprint Object
+description: "Restores archived entries and makes them accessible."
 order: 240
 ---
 
-[Restores](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#restore-footprint) archived entries and makes them accessible.
+[Restores](../../../../../../../learn/fundamentals/transactions/list-of-operations#restore-footprint) archived entries and makes them accessible.
 
-<ExampleResponse>
-
-```json
+```json Example
 {
   "id": "1109896858714113",
   "paging_token": "1109896858714113",
@@ -19,5 +18,3 @@ order: 240
   "transaction_hash": "1768d762bedf3129a00ec095d1aaed4c378dc3f55250758ed5008992b303303b"
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/object/revoke-sponsorship.mdx b/docs/data/apis/horizon/api-reference/resources/operations/object/revoke-sponsorship.mdx
index 59698d33b..08c7ad199 100644
--- a/docs/data/apis/horizon/api-reference/resources/operations/object/revoke-sponsorship.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/operations/object/revoke-sponsorship.mdx
@@ -1,48 +1,66 @@
 ---
 title: Revoke Sponsorship
+description: "Revoke sponsorship of a ledger entry."
 order: 190
 ---
 
 Revoke sponsorship of a ledger entry.
 
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- account_id
-  - string (optional)
-  - The id of the account which is no longer sponsored.
-- claimable_balance_id
-  - string (optional)
-  - The id of the claimable balance which is no longer sponsored.
-- data_account_id
-  - string (optional)
-  - The id of the account whose data entry is no longer sponsored.
-- data_name
-  - string (optional)
-  - The name of the data entry which is no longer sponsored.
-- offer_id
-  - string (optional)
-  - The id of the offer which is no longer sponsored.
-- trustline_account_id
-  - string (optional)
-  - The id of the account whose trustline is no longer sponsored.
-- trustline_asset
-  - string (optional)
-  - The asset of the trustline which is no longer sponsored.
-- signer_account_id
-  - string (optional)
-  - The account id of the signer which is no longer sponsored.
-- signer_key
-  - string (optional)
-  - The type of the signer which is no longer sponsored.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
+<ResponseField name="account_id" type="string (optional)">
+
+The id of the account which is no longer sponsored.
+
+</ResponseField>
+
+<ResponseField name="claimable_balance_id" type="string (optional)">
+
+The id of the claimable balance which is no longer sponsored.
+
+</ResponseField>
+
+<ResponseField name="data_account_id" type="string (optional)">
+
+The id of the account whose data entry is no longer sponsored.
+
+</ResponseField>
+
+<ResponseField name="data_name" type="string (optional)">
+
+The name of the data entry which is no longer sponsored.
+
+</ResponseField>
+
+<ResponseField name="offer_id" type="string (optional)">
+
+The id of the offer which is no longer sponsored.
+
+</ResponseField>
+
+<ResponseField name="trustline_account_id" type="string (optional)">
+
+The id of the account whose trustline is no longer sponsored.
+
+</ResponseField>
+
+<ResponseField name="trustline_asset" type="string (optional)">
+
+The asset of the trustline which is no longer sponsored.
+
+</ResponseField>
+
+<ResponseField name="signer_account_id" type="string (optional)">
+
+The account id of the signer which is no longer sponsored.
+
+</ResponseField>
+
+<ResponseField name="signer_key" type="string (optional)">
+
+The type of the signer which is no longer sponsored.
+
+</ResponseField>
+
+```json Example
 {
   "_links": {
     "self": {
@@ -72,5 +90,3 @@ Revoke sponsorship of a ledger entry.
   "account_id": "GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA"
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/object/sell-offer.mdx b/docs/data/apis/horizon/api-reference/resources/operations/object/sell-offer.mdx
index dae575f37..30c715757 100644
--- a/docs/data/apis/horizon/api-reference/resources/operations/object/sell-offer.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/operations/object/sell-offer.mdx
@@ -1,59 +1,88 @@
 ---
 title: Manage Sell Offer Object
+description: "Creates, updates, or deletes a sell offer to trade assets."
 order: 50
 ---
 
 Creates, updates, or deletes a sell offer to trade assets. A sell offer specifies a certain amount of the selling asset that should be sold in exchange for the maximum quantity of the buying asset.
 
-See the [`Manage Sell Offer` errors](../../../errors/result-codes/operation-specific/manage-sell-offer.mdx).
-
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- amount
-  - string
-  - The amount of `selling_asset` that the account making this offer is willing to sell.
-- price
-  - string
-  - How many units of `selling_asset` it takes to get 1 unit of `buying_asset`. A number representing the decimal form of `price_r`.
-- price_r
-  - object
-  - A precise representation of the buy and sell price of the assets on offer.
-    - n
-      - number
-      - The numerator.
-    - d
-      - number
-      - The denominator.
-- buying_asset_type
-  - string
-  - The type for the buying asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
-- buying_asset_issuer
-  - string
-  - The Stellar address of the buying asset’s issuer. Appears if the `buying_asset_type` is not `native`.
-- buying_asset_code
-  - string
-  - The code for the buying asset. Appears if the `buying_asset_type` is not `native`.
-- selling_asset_type
-  - string
-  - The type for the selling asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
-- selling_asset_issuer
-  - string
-  - The Stellar address of the selling asset’s issuer. Appears if the `selling_asset_type` is not `native`.
-- selling_asset_code
-  - string
-  - The code for the selling asset. Appears if the `selling_asset_type` is not `native`.
-- offer_id
-  - string
-  - A unique identifier for this offer.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
+See the [`Manage Sell Offer` errors](../../../errors/result-codes/operation-specific/manage-sell-offer).
+
+<ResponseField name="amount" type="string">
+
+The amount of `selling_asset` that the account making this offer is willing to sell.
+
+</ResponseField>
+
+<ResponseField name="price" type="string">
+
+How many units of `selling_asset` it takes to get 1 unit of `buying_asset`. A number representing the decimal form of `price_r`.
+
+</ResponseField>
+
+<ResponseField name="price_r" type="object">
+
+A precise representation of the buy and sell price of the assets on offer.
+
+  <Expandable title="price_r properties">
+    <ResponseField name="n" type="number">
+
+      The numerator.
+
+    </ResponseField>
+
+    <ResponseField name="d" type="number">
+
+      The denominator.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="buying_asset_type" type="string">
+
+The type for the buying asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
+
+</ResponseField>
+
+<ResponseField name="buying_asset_issuer" type="string">
+
+The Stellar address of the buying asset’s issuer. Appears if the `buying_asset_type` is not `native`.
+
+</ResponseField>
+
+<ResponseField name="buying_asset_code" type="string">
+
+The code for the buying asset. Appears if the `buying_asset_type` is not `native`.
+
+</ResponseField>
+
+<ResponseField name="selling_asset_type" type="string">
+
+The type for the selling asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
+
+</ResponseField>
+
+<ResponseField name="selling_asset_issuer" type="string">
+
+The Stellar address of the selling asset’s issuer. Appears if the `selling_asset_type` is not `native`.
+
+</ResponseField>
+
+<ResponseField name="selling_asset_code" type="string">
+
+The code for the selling asset. Appears if the `selling_asset_type` is not `native`.
+
+</ResponseField>
+
+<ResponseField name="offer_id" type="string">
+
+A unique identifier for this offer.
+
+</ResponseField>
+
+```json Example
 {
   "_links": {
     "self": {
@@ -93,5 +122,3 @@ See the [`Manage Sell Offer` errors](../../../errors/result-codes/operation-spec
   "offer_id": "0"
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/operations/object/set-options.mdx b/docs/data/apis/horizon/api-reference/resources/operations/object/set-options.mdx
index 27bc4c135..e3413e0c3 100644
--- a/docs/data/apis/horizon/api-reference/resources/operations/object/set-options.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/operations/object/set-options.mdx
@@ -1,56 +1,80 @@
 ---
 title: Set Options Object
+description: "Sets an account's flags, inflation destination, signers, and home domain."
 order: 80
 ---
 
 Sets an account's flags, inflation destination, signers, and home domain.
 
-See the [`Set Options` errors](../../../errors/result-codes/operation-specific/set-options.mdx).
-
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- signer_key
-  - string
-  - The public key of the new signer.
-- signer_weight
-  - number
-  - The weight of the new signer. Can range from `1` to `255`.
-- master_key_weight
-  - number
-  - The weight of the master key. Can range from `1` to `255`.
-- low_threshold
-  - number
-  - The sum weight for the low threshold.
-- med_threshold
-  - number
-  - The sum weight for the medium threshold.
-- high_threshold
-  - number
-  - The sum weight for the high threshold.
-- home_domain
-  - string
-  - The home domain used for stellar.toml file discovery.
-- set_flags
-  - array
-  - The array of numeric values of flags that has been set in this operation. Options include `1` for `AUTH_REQUIRED_FLAG`, `2` for `AUTH_REVOCABLE_FLAG`, and `4` for `AUTH_IMMUTABLE_FLAG`.
-- set_flags_s
-  - array
-  - The array of string values of flags that has been set in this operation. Options include `AUTH_REQUIRED_FLAG`, `AUTH_REVOCABLE_FLAG`, and `AUTH_IMMUTABLE_FLAG`.
-- clear_flags
-  - array
-  - The array of numeric values of flags that has been cleared in this operation. Options include `1` for `AUTH_REQUIRED_FLAG`, `2` for `AUTH_REVOCABLE_FLAG`, and `4` for `AUTH_IMMUTABLE_FLAG`.
-- clear_flags_s
-  - array
-  - The array of string values of flags that has been cleared in this operation. Options include `AUTH_REQUIRED_FLAG`, `AUTH_REVOCABLE_FLAG`, and `AUTH_IMMUTABLE_FLAG`.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
+See the [`Set Options` errors](../../../errors/result-codes/operation-specific/set-options).
+
+<ResponseField name="signer_key" type="string">
+
+The public key of the new signer.
+
+</ResponseField>
+
+<ResponseField name="signer_weight" type="number">
+
+The weight of the new signer. Can range from `1` to `255`.
+
+</ResponseField>
+
+<ResponseField name="master_key_weight" type="number">
+
+The weight of the master key. Can range from `1` to `255`.
+
+</ResponseField>
+
+<ResponseField name="low_threshold" type="number">
+
+The sum weight for the low threshold.
+
+</ResponseField>
+
+<ResponseField name="med_threshold" type="number">
+
+The sum weight for the medium threshold.
+
+</ResponseField>
+
+<ResponseField name="high_threshold" type="number">
+
+The sum weight for the high threshold.
+
+</ResponseField>
+
+<ResponseField name="home_domain" type="string">
+
+The home domain used for stellar.toml file discovery.
+
+</ResponseField>
+
+<ResponseField name="set_flags" type="array">
+
+The array of numeric values of flags that has been set in this operation. Options include `1` for `AUTH_REQUIRED_FLAG`, `2` for `AUTH_REVOCABLE_FLAG`, and `4` for `AUTH_IMMUTABLE_FLAG`.
+
+</ResponseField>
+
+<ResponseField name="set_flags_s" type="array">
+
+The array of string values of flags that has been set in this operation. Options include `AUTH_REQUIRED_FLAG`, `AUTH_REVOCABLE_FLAG`, and `AUTH_IMMUTABLE_FLAG`.
+
+</ResponseField>
+
+<ResponseField name="clear_flags" type="array">
+
+The array of numeric values of flags that has been cleared in this operation. Options include `1` for `AUTH_REQUIRED_FLAG`, `2` for `AUTH_REVOCABLE_FLAG`, and `4` for `AUTH_IMMUTABLE_FLAG`.
+
+</ResponseField>
+
+<ResponseField name="clear_flags_s" type="array">
+
+The array of string values of flags that has been cleared in this operation. Options include `AUTH_REQUIRED_FLAG`, `AUTH_REVOCABLE_FLAG`, and `AUTH_IMMUTABLE_FLAG`.
+
+</ResponseField>
+
+```json Example
 {
   "_links": {
     "self": {
@@ -80,5 +104,3 @@ See the [`Set Options` errors](../../../errors/result-codes/operation-specific/s
   "home_domain": "www.stellar.org"
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/payments/README.mdx b/docs/data/apis/horizon/api-reference/resources/payments/README.mdx
deleted file mode 100644
index bd22cb2e5..000000000
--- a/docs/data/apis/horizon/api-reference/resources/payments/README.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Payments
-order: 0
----
-
-Payments are objects that represent balance transfer from one address to another. Payments are submitted to the Stellar network grouped in a Transaction.
-
-<EndpointsTable title="Endpoints">
-
-|     |                                              |
-| --- | -------------------------------------------- |
-| GET | [/payments](../../list-all-payments.api.mdx) |
-
-</EndpointsTable>
diff --git a/docs/data/apis/horizon/api-reference/resources/payments/index.mdx b/docs/data/apis/horizon/api-reference/resources/payments/index.mdx
new file mode 100644
index 000000000..27c1a8a43
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/resources/payments/index.mdx
@@ -0,0 +1,9 @@
+---
+title: Payments
+description: "Payments are objects that represent balance transfer from one address to another. Payments are submitted to the Stellar network grouped in a Transaction."
+order: 0
+---
+
+| Endpoints |  |
+| --- | --- |
+| GET | [/payments](/docs/data/apis/horizon/api-reference/list-all-payments) |
diff --git a/docs/data/apis/horizon/api-reference/resources/payments/object.mdx b/docs/data/apis/horizon/api-reference/resources/payments/object.mdx
index 8d4ae6cb4..a511e9a5f 100644
--- a/docs/data/apis/horizon/api-reference/resources/payments/object.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/payments/object.mdx
@@ -1,41 +1,50 @@
 ---
 title: The Payment Object
+description: "Sends an amount in a specific asset to a destination account."
 order: 20
 ---
 
 Sends an amount in a specific asset to a destination account.
 
-See the [`Payment` errors](../../errors/result-codes/operation-specific/payment.mdx).
-
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- asset_type
-  - string
-  - The type of asset being sent. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
-- asset_code
-  - string
-  - The code for the asset being sent. Appears if the `asset_type` is not `native`.
-- asset_issuer
-  - string
-  - The Stellar address of the issuer of the asset being sent. Appears if the `asset_type` is not `native`.
-- from
-  - string
-  - The payment sender’s public key.
-- to
-  - string
-  - The payment recipient’s public key.
-- amount
-  - string
-  - Amount sent.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
+See the [`Payment` errors](../../errors/result-codes/operation-specific/payment).
+
+<ResponseField name="asset_type" type="string">
+
+The type of asset being sent. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
+
+</ResponseField>
+
+<ResponseField name="asset_code" type="string">
+
+The code for the asset being sent. Appears if the `asset_type` is not `native`.
+
+</ResponseField>
+
+<ResponseField name="asset_issuer" type="string">
+
+The Stellar address of the issuer of the asset being sent. Appears if the `asset_type` is not `native`.
+
+</ResponseField>
+
+<ResponseField name="from" type="string">
+
+The payment sender’s public key.
+
+</ResponseField>
+
+<ResponseField name="to" type="string">
+
+The payment recipient’s public key.
+
+</ResponseField>
+
+<ResponseField name="amount" type="string">
+
+Amount sent.
+
+</ResponseField>
+
+```json Example
 {
   "_links": {
     "self": {
@@ -70,5 +79,3 @@ See the [`Payment` errors](../../errors/result-codes/operation-specific/payment.
   "amount": "5.0000000"
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/trades/README.mdx b/docs/data/apis/horizon/api-reference/resources/trades/README.mdx
deleted file mode 100644
index e98a5b59a..000000000
--- a/docs/data/apis/horizon/api-reference/resources/trades/README.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: Trades
-order: 0
----
-
-When an offer is fully or partially fulfilled, a trade happens. Trades can also be caused by successful path payments, because path payments involve fulfilling offers.
-
-A trade occurs between two parties—`base` and `counter`. Which is which is either arbitrary or determined by the calling query.
-
-Learn more about [trades](../../../../../../learn/glossary.mdx#decentralized-exchange).
-
-<EndpointsTable title="Endpoints">
-
-|     |                                         |
-| --- | --------------------------------------- |
-| GET | [/trades](../../get-all-trades.api.mdx) |
-
-</EndpointsTable>
diff --git a/docs/data/apis/horizon/api-reference/resources/trades/index.mdx b/docs/data/apis/horizon/api-reference/resources/trades/index.mdx
new file mode 100644
index 000000000..bdb1d24cd
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/resources/trades/index.mdx
@@ -0,0 +1,13 @@
+---
+title: Trades
+description: "When an offer is fully or partially fulfilled, a trade happens. Trades can also be caused by successful path payments, because path payments involve fulfilling offers."
+order: 0
+---
+
+A trade occurs between two parties—`base` and `counter`. Which is which is either arbitrary or determined by the calling query.
+
+Learn more about [trades](/docs/learn/glossary#decentralized-exchange).
+
+| Endpoints |                                                                 |
+| --------- | --------------------------------------------------------------- |
+| GET       | [/trades](/docs/data/apis/horizon/api-reference/get-all-trades) |
diff --git a/docs/data/apis/horizon/api-reference/resources/trades/object.mdx b/docs/data/apis/horizon/api-reference/resources/trades/object.mdx
index cd494272a..6abf7bbae 100644
--- a/docs/data/apis/horizon/api-reference/resources/trades/object.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/trades/object.mdx
@@ -1,84 +1,140 @@
 ---
 title: The Trade Object
+description: "When Horizon returns information about a trade, it uses the following format."
 order: 10
 ---
 
 When Horizon returns information about a trade, it uses the following format:
 
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- id
-  - string
-  - A unique identifier for this trade.
-- paging_token
-  - number
-  - A cursor value for use in [pagination](../../structure/pagination/README.mdx).
-- ledger_close_time
-  - string
-  - An ISO 8601 formatted string of when the ledger with this trade was closed.
-- base_account
-  - string (optional)
-  - The account ID of the base party for this trade.
-- base_offer_id
-  - string (optional)
-  - The base offer ID. If this offer was immediately and fully consumed, this will be a synethic ID.
-- base_liquidity_pool_id
-  - string (optional)
-  - The base liquidity pool ID. If this trade was executed against a liquidity pool.
-- base_amount
-  - string
-  - The amount of the base asset that was moved from `base_account` to `counter_account`.
-- base_asset_type
-  - string
-  - The type for the base asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
-- base_asset_code
-  - string
-  - The code for the base asset.
-- base_asset_issuer
-  - string
-  - The Stellar address of the base asset’s issuer.
-- counter_account
-  - string (optional)
-  - The account ID of the base party for this trade.
-- counter_offer_id
-  - string (optional)
-  - The counter offer ID. If this offer was immediately and fully consumed, this will be a synethic ID.
-- counter_liquidity_pool_id
-  - string (optional)
-  - The counter liquidity pool ID. If this trade was executed against a liquidity pool.
-- counter_amount
-  - string
-  - The amount of the counter asset that was moved from `counter_account` to `base_account`.
-- counter_asset_type
-  - string
-  - The type for the counter asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
-- counter_asset_code
-  - string
-  - The code for the counter asset.
-- counter_asset_issuer
-  - string
-  - The Stellar address of the counter asset’s issuer.
-- price
-  - object
-  - An object of a number numerator and number denominator that represents the original offer price. To derive the price, divide `n` by `d`. `n` and `d` are represented as strings because they might be 64-bit integers.
-    - n
-      - string
-      - The numerator.
-    - d
-      - string
-      - The denominator.
-- base_is_seller
-  - boolean
-  - Indicates with party is the seller.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
+<ResponseField name="id" type="string">
+
+A unique identifier for this trade.
+
+</ResponseField>
+
+<ResponseField name="paging_token" type="number">
+
+A cursor value for use in [pagination](/docs/data/apis/horizon/api-reference/structure/pagination).
+
+</ResponseField>
+
+<ResponseField name="ledger_close_time" type="string">
+
+An ISO 8601 formatted string of when the ledger with this trade was closed.
+
+</ResponseField>
+
+<ResponseField name="base_account" type="string (optional)">
+
+The account ID of the base party for this trade.
+
+</ResponseField>
+
+<ResponseField name="base_offer_id" type="string (optional)">
+
+The base offer ID. If this offer was immediately and fully consumed, this will be a synethic ID.
+
+</ResponseField>
+
+<ResponseField name="base_liquidity_pool_id" type="string (optional)">
+
+The base liquidity pool ID. If this trade was executed against a liquidity pool.
+
+</ResponseField>
+
+<ResponseField name="base_amount" type="string">
+
+The amount of the base asset that was moved from `base_account` to `counter_account`.
+
+</ResponseField>
+
+<ResponseField name="base_asset_type" type="string">
+
+The type for the base asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
+
+</ResponseField>
+
+<ResponseField name="base_asset_code" type="string">
+
+The code for the base asset.
+
+</ResponseField>
+
+<ResponseField name="base_asset_issuer" type="string">
+
+The Stellar address of the base asset’s issuer.
+
+</ResponseField>
+
+<ResponseField name="counter_account" type="string (optional)">
+
+The account ID of the base party for this trade.
+
+</ResponseField>
+
+<ResponseField name="counter_offer_id" type="string (optional)">
+
+The counter offer ID. If this offer was immediately and fully consumed, this will be a synethic ID.
+
+</ResponseField>
+
+<ResponseField name="counter_liquidity_pool_id" type="string (optional)">
+
+The counter liquidity pool ID. If this trade was executed against a liquidity pool.
+
+</ResponseField>
+
+<ResponseField name="counter_amount" type="string">
+
+The amount of the counter asset that was moved from `counter_account` to `base_account`.
+
+</ResponseField>
+
+<ResponseField name="counter_asset_type" type="string">
+
+The type for the counter asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.
+
+</ResponseField>
+
+<ResponseField name="counter_asset_code" type="string">
+
+The code for the counter asset.
+
+</ResponseField>
+
+<ResponseField name="counter_asset_issuer" type="string">
+
+The Stellar address of the counter asset’s issuer.
+
+</ResponseField>
+
+<ResponseField name="price" type="object">
+
+An object of a number numerator and number denominator that represents the original offer price. To derive the price, divide `n` by `d`. `n` and `d` are represented as strings because they might be 64-bit integers.
+
+  <Expandable title="price properties">
+    <ResponseField name="n" type="string">
+
+      The numerator.
+
+    </ResponseField>
+
+    <ResponseField name="d" type="string">
+
+      The denominator.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="base_is_seller" type="boolean">
+
+Indicates with party is the seller.
+
+</ResponseField>
+
+```json Example
 {
   "_links": {
     "self": {
@@ -115,5 +171,3 @@ When Horizon returns information about a trade, it uses the following format:
   }
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/resources/transactions/README.mdx b/docs/data/apis/horizon/api-reference/resources/transactions/README.mdx
deleted file mode 100644
index 776de75a6..000000000
--- a/docs/data/apis/horizon/api-reference/resources/transactions/README.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: Transactions
-order: 0
----
-
-:::info
-
-Transaction meta `result_meta_xdr` will be removed from the SDF hosted Horizon API (`horizon.stellar.org`) in Q3 2024. Instead of using Horizon to access transaction metadata, developers could access it with the [`getTransactions`](../../../../rpc/api-reference/methods/getTransactions.mdx) endpoint in the Stellar RPC.
-
-:::
-
-Transactions are commands that modify the ledger state and consist of one or more operations.
-
-Learn more about [transactions](../../../../../../learn/glossary.mdx#transaction).
-
-<EndpointsTable title="Endpoints">
-
-|  |  |
-| --- | --- |
-| GET | [/transactions/:transaction_id](../../retrieve-a-transaction.api.mdx) |
-| GET | [/transactions/:transaction_id/operations](../../retrieve-a-transactions-operations.api.mdx) |
-| GET | [/transactions/:transaction_id/effects](../../retrieve-a-transactions-effects.api.mdx) |
-| GET | [/transactions](../../list-all-transactions.api.mdx) |
-| POST | [/transactions](../../submit-a-transaction.api.mdx) |
-| POST | [/transactions_async](../../submit-async-transaction.api.mdx) |
-
-</EndpointsTable>
diff --git a/docs/data/apis/horizon/api-reference/resources/transactions/index.mdx b/docs/data/apis/horizon/api-reference/resources/transactions/index.mdx
new file mode 100644
index 000000000..829f1e6c8
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/resources/transactions/index.mdx
@@ -0,0 +1,24 @@
+---
+title: Transactions
+description: "Transaction meta result_meta_xdr will be removed from the SDF hosted Horizon API (horizon.stellar.org) in Q3 2024."
+order: 0
+---
+
+<Info>
+
+Transaction meta `result_meta_xdr` will be removed from the SDF hosted Horizon API (`horizon.stellar.org`) in Q3 2024. Instead of using Horizon to access transaction metadata, developers could access it with the [`getTransactions`](/docs/data/apis/rpc/api-reference/methods/getTransactions) endpoint in the Stellar RPC.
+
+</Info>
+
+Transactions are commands that modify the ledger state and consist of one or more operations.
+
+Learn more about [transactions](/docs/learn/glossary#transaction).
+
+| Endpoints |  |
+| --- | --- |
+| GET | [/transactions/:transaction_id](/docs/data/apis/horizon/api-reference/retrieve-a-transaction) |
+| GET | [/transactions/:transaction_id/operations](/docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations) |
+| GET | [/transactions/:transaction_id/effects](/docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects) |
+| GET | [/transactions](/docs/data/apis/horizon/api-reference/list-all-transactions) |
+| POST | [/transactions](/docs/data/apis/horizon/api-reference/submit-a-transaction) |
+| POST | [/transactions_async](/docs/data/apis/horizon/api-reference/submit-async-transaction) |
diff --git a/docs/data/apis/horizon/api-reference/resources/transactions/object.mdx b/docs/data/apis/horizon/api-reference/resources/transactions/object.mdx
index 98dd3a0aa..87db1c118 100644
--- a/docs/data/apis/horizon/api-reference/resources/transactions/object.mdx
+++ b/docs/data/apis/horizon/api-reference/resources/transactions/object.mdx
@@ -1,114 +1,196 @@
 ---
 title: The Transaction Object
+description: "Transaction meta result_meta_xdr will be removed from the SDF hosted Horizon API (horizon.stellar.org) in Q3 2024."
 order: 10
 ---
 
-:::info
+<Info>
 
-Transaction meta `result_meta_xdr` will be removed from the SDF hosted Horizon API (`horizon.stellar.org`) in Q3 2024. Instead of using Horizon to access transaction metadata, developers could access it with the [`getTransactions`](../../../../rpc/api-reference/methods/getTransactions.mdx) endpoint in the Stellar RPC.
+Transaction meta `result_meta_xdr` will be removed from the SDF hosted Horizon API (`horizon.stellar.org`) in Q3 2024. Instead of using Horizon to access transaction metadata, developers could access it with the [`getTransactions`](../../../../rpc/api-reference/methods/getTransactions) endpoint in the Stellar RPC.
 
-:::
+</Info>
 
 When Horizon returns information about a transaction, it uses the following format:
 
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- id
-  - string
-  - A unique identifier for this transaction.
-- paging_token
-  - number
-  - A cursor value for use in [pagination](../../structure/pagination/README.mdx).
-- successful
-  - boolean
-  - Indicates if this transaction was successful or not.
-- hash
-  - string
-  - A hex-encoded SHA-256 hash of this transaction’s [XDR](../../../../../../learn/fundamentals/data-format/xdr.mdx)-encoded form.
-- ledger
-  - number
-  - The sequence number of the ledger that this transaction was included in.
-- created_at
-  - ISO8601 string
-  - The date this transaction was created.
-- source_account
-  - string
-  - The account that originates the transaction.
-- source_account_sequence
-  - string
-  - The source account's sequence number that this transaction consumed.
-- fee_charged
-  - number
-  - The fee (in [stroops](../../../../../../learn/fundamentals/lumens.mdx)) paid by the source account to apply this transaction to the ledger.
-- max_fee
-  - number
-  - The maximum fee (in [stroops](../../../../../../learn/fundamentals/lumens.mdx)) that the source account was willing to pay.
-- operation_count
-  - number
-  - The number of operations contained within this transaction.
-- envelope_xdr
-  - string
-  - A base64 encoded string of the raw `TransactionEnvelope` XDR struct for this transaction.
-- result_xdr
-  - string
-  - A base64 encoded string of the raw `TransactionResult` XDR struct for this transaction.
-- result_meta_xdr
-  - string
-  - **_[To be deprecated in Q3]_** A base64 encoded string of the raw `TransactionMeta` XDR struct for this transaction
-- fee_meta_xdr
-  - string
-  - A base64 encoded string of the raw `LedgerEntryChanges` XDR struct produced by taking fees for this transaction.
-- memo
-  - string
-  - The optional memo attached to a transaction.
-- memo_type
-  - string
-  - The type of memo. Potential values include `MEMO_TEXT`, `MEMO_ID`, `MEMO_HASH`, `MEMO_RETURN`.
-- signatures
-  - string
-  - An array of signatures used to sign this transaction.
-- preconditions
-  - object
-  - A set of transaction preconditions affecting its validity.
-    - time_bounds
-      - object
-      - The time range for which this transaction is valid, with bounds as unsigned 64-bit UNIX timestamps
-        - min_time
-          - string
-          - the lower bound
-        - max_time
-          - string
-          - the upper bound
-    - ledger_bounds
-      - object
-      - The ledger range for which this transaction is valid, as unsigned 32-bit integers.
-        - min_ledger
-          - number
-          - the lower bound
-        - max_ledger
-          - number
-          - the upper bound
-    - min_account_sequence
-      - string
-      - Containing a positive, signed 64-bit integer representing the lowest source account sequence number for which the transaction is valid.
-    - min_account_sequence_age
-      - number
-      - The minimum duration of time (in seconds as an unsigned 64-bit integer) that must have passed since the source account's sequence number changed for the transaction to be valid.
-    - min_account_sequence_ledger_gap
-      - number
-      - An unsigned 32-bit integer representing the minimum number of ledgers that must have closed since the source account's sequence number changed for the transaction to be valid.
-    - extra_signers
-      - array of strings
-      - The list of up to two additional signers that must have corresponding signatures for this transaction to be valid.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
+<ResponseField name="id" type="string">
+
+A unique identifier for this transaction.
+
+</ResponseField>
+
+<ResponseField name="paging_token" type="number">
+
+A cursor value for use in [pagination](/docs/data/apis/horizon/api-reference/structure/pagination).
+
+</ResponseField>
+
+<ResponseField name="successful" type="boolean">
+
+Indicates if this transaction was successful or not.
+
+</ResponseField>
+
+<ResponseField name="hash" type="string">
+
+A hex-encoded SHA-256 hash of this transaction’s [XDR](../../../../../../learn/fundamentals/data-format/xdr)-encoded form.
+
+</ResponseField>
+
+<ResponseField name="ledger" type="number">
+
+The sequence number of the ledger that this transaction was included in.
+
+</ResponseField>
+
+<ResponseField name="created_at" type="ISO8601 string">
+
+The date this transaction was created.
+
+</ResponseField>
+
+<ResponseField name="source_account" type="string">
+
+The account that originates the transaction.
+
+</ResponseField>
+
+<ResponseField name="source_account_sequence" type="string">
+
+The source account's sequence number that this transaction consumed.
+
+</ResponseField>
+
+<ResponseField name="fee_charged" type="number">
+
+The fee (in [stroops](../../../../../../learn/fundamentals/lumens)) paid by the source account to apply this transaction to the ledger.
+
+</ResponseField>
+
+<ResponseField name="max_fee" type="number">
+
+The maximum fee (in [stroops](../../../../../../learn/fundamentals/lumens)) that the source account was willing to pay.
+
+</ResponseField>
+
+<ResponseField name="operation_count" type="number">
+
+The number of operations contained within this transaction.
+
+</ResponseField>
+
+<ResponseField name="envelope_xdr" type="string">
+
+A base64 encoded string of the raw `TransactionEnvelope` XDR struct for this transaction.
+
+</ResponseField>
+
+<ResponseField name="result_xdr" type="string">
+
+A base64 encoded string of the raw `TransactionResult` XDR struct for this transaction.
+
+</ResponseField>
+
+<ResponseField name="result_meta_xdr" type="string">
+
+**_[To be deprecated in Q3]_** A base64 encoded string of the raw `TransactionMeta` XDR struct for this transaction
+
+</ResponseField>
+
+<ResponseField name="fee_meta_xdr" type="string">
+
+A base64 encoded string of the raw `LedgerEntryChanges` XDR struct produced by taking fees for this transaction.
+
+</ResponseField>
+
+<ResponseField name="memo" type="string">
+
+The optional memo attached to a transaction.
+
+</ResponseField>
+
+<ResponseField name="memo_type" type="string">
+
+The type of memo. Potential values include `MEMO_TEXT`, `MEMO_ID`, `MEMO_HASH`, `MEMO_RETURN`.
+
+</ResponseField>
+
+<ResponseField name="signatures" type="string">
+
+An array of signatures used to sign this transaction.
+
+</ResponseField>
+
+<ResponseField name="preconditions" type="object">
+
+A set of transaction preconditions affecting its validity.
+
+  <Expandable title="preconditions properties">
+    <ResponseField name="time_bounds" type="object">
+
+      The time range for which this transaction is valid, with bounds as unsigned 64-bit UNIX timestamps
+
+      <Expandable title="time_bounds properties">
+        <ResponseField name="min_time" type="string">
+
+          the lower bound
+
+        </ResponseField>
+
+        <ResponseField name="max_time" type="string">
+
+          the upper bound
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+    <ResponseField name="ledger_bounds" type="object">
+
+      The ledger range for which this transaction is valid, as unsigned 32-bit integers.
+
+      <Expandable title="ledger_bounds properties">
+        <ResponseField name="min_ledger" type="number">
+
+          the lower bound
+
+        </ResponseField>
+
+        <ResponseField name="max_ledger" type="number">
+
+          the upper bound
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+    <ResponseField name="min_account_sequence" type="string">
+
+      Containing a positive, signed 64-bit integer representing the lowest source account sequence number for which the transaction is valid.
+
+    </ResponseField>
+
+    <ResponseField name="min_account_sequence_age" type="number">
+
+      The minimum duration of time (in seconds as an unsigned 64-bit integer) that must have passed since the source account's sequence number changed for the transaction to be valid.
+
+    </ResponseField>
+
+    <ResponseField name="min_account_sequence_ledger_gap" type="number">
+
+      An unsigned 32-bit integer representing the minimum number of ledgers that must have closed since the source account's sequence number changed for the transaction to be valid.
+
+    </ResponseField>
+
+    <ResponseField name="extra_signers" type="array of strings">
+
+      The list of up to two additional signers that must have corresponding signatures for this transaction to be valid.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+```json Example
 {
   "memo": "298424",
   "_links": {
@@ -157,5 +239,3 @@ When Horizon returns information about a transaction, it uses the following form
   ]
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance.ParamsDetails.json b/docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance.ParamsDetails.json
deleted file mode 100644
index d1bb89c18..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"claimable_balance_id","in":"path","required":true,"description":"A unique identifier for this claimable balance.","schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance.RequestSchema.json b/docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance.StatusCodes.json b/docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance.StatusCodes.json
deleted file mode 100644
index 1f64c8457..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transactions":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","operations","transactions"]},"id":{"type":"string","title":"id"},"asset":{"type":"string"},"amount":{"type":"string"},"sponsor":{"type":"string"},"last_modified_ledger":{"type":"string"},"last_modified_time":{"type":"string"},"claimants":{"type":"array","items":{"type":"object","properties":{"destination":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"predicate":{"type":"object","properties":{"and":{"type":"array","items":{"type":"object","properties":{"or":{"type":"array","items":{"type":"object","properties":{"relBefore":{"type":"string"},"absBefore":{"type":"string"},"absBeforeEpoch":{"type":"string"}}}},"not":{"type":"object","properties":{"unconditional":{"type":"boolean"},"relBefore":{"type":"string"},"absBefore":{"type":"string"},"absBeforeEpoch":{"type":"string"}}}}}}}}}}},"flags":{"type":"integer"},"paging_token":{"type":"string"}},"required":["id","paging_token","asset","amount","last_modified_ledger","last_modified_time"],"title":"ClaimableBalance"},"examples":{"RetrieveAClaimableBalance":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/000000000102030000000000000000000000000000000000000000000000000000000000"},"operations":{"href":"https://horizon-testnet.stellar.org/claimable_balances/000000000102030000000000000000000000000000000000000000000000000000000000/operations{?cursor,limit,order}","templated":true},"transactions":{"href":"https://horizon-testnet.stellar.org/claimable_balances/000000000102030000000000000000000000000000000000000000000000000000000000/transactions{?cursor,limit,order}","templated":true}},"id":"000000000102030000000000000000000000000000000000000000000000000000000000","paging_token":"000000000102030000000000000000000000000000000000000000000000000000000000","asset":"native","amount":"10.0000000","claimants":[{"destination":"GC3C4AKRBQLHOJ45U4XG35ESVWRDECWO5XLDGYADO6DPR3L7KIDVUMML","predicate":{"and":[{"or":[{"relBefore":"12"},{"absBefore":"2020-08-26T11:15:39Z","absBeforeEpoch":"1598440539"}]},{"not":{"unconditional":true}}]}}],"last_modified_ledger":28411995,"last_modified_time":"2020-02-26T19:29:16Z"}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance.api.mdx b/docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance.api.mdx
deleted file mode 100644
index c61e078d6..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: retrieve-a-claimable-balance
-title: "Retrieve a Claimable Balance"
-description: "The single claimable balance endpoint provides information on a claimable balance."
-sidebar_label: "Retrieve a Claimable Balance"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlWVlvGzkS/isFvuRA6/KRjfWy69iO440nydpOZjaOYbDJkpoxm+yQbCkeQf99UexuqXUE8QQziwCjFxli3cdXZHnGAh97NrxmR5qrnKca4QXX3Aj07CZhEr1wqgjKGjZkVxmCV2asEcSCPK3IAY0srDIBCmcnSqIHZUbW5ZyYwRrgm0xdljBboIs0Z5IN2QUGp3CChwt7anNYwgrueI4BHRk8Y4bnyIZsIfS2FnqrJEuYIoMLHjKWMIdfSuVQsmFwJa57dQilUV9KBCXRBDVS6GBkHYRM+e0me5FhztlwxsJ9QTb44JQZs/n8hpT5whqPns53+n36WlV4WQqB3rOECWsCmkAkvCi0EjEQvc+e6Gabemz6GUWgUDgKW1CVllutzJ3/Pp1HPfo+VeZwtOlbwqpksiEjbWyesIB5oXmguC6oU2s1csPm83bYryuhNwkLKmhsyVhk/wHm/18NC44bz8XPZ9oaUczpShzXbL+ZJ0zJbcY1cpUky7j3GLbUdMJ4bkuz/SiWunVbzzT34Ta3kjpK3mqUY3wIYVDU1lvIqlY0oZ0O7hy/p24PmD8gTRJ9UIZXfbgZkIKHgI5a9PT6sPOx3zm4me3vz1uh4lI6at05SUZJDYvfV8uN/HGbV6L7B3kd6hc4sm57QHnqH3J6UliRbQM7KkVjw/fNKI2wRioKO9fbCj/5yy2tPwkb6TjwFjTKBKTCpIzysTLj22DvcEt5rDdenDIrLE0PLTrmGz2wteJbfb4x+uYJw688L3QVzm/PyOGMTbgucXUoNLBfgRTLQij8sNfLrFO/W9MJ6IPB0PUBteaua924tzFUfa/ffAb9nf5u/4c/m6j/c9jVWxo1+6conbcu0SpXIbFOoososARvukhsmRI/iSttsx7qTD0m2J9lxHp3/KmS62HFCMsnuOy4IRv0u0uy1si4XkN/dnq0e7R3+PrixX/OX739997++73fTnf3Ty4//HpxfHL069v9386PT/97ePz22fG7i93zf7w+O/7w/pdfztka9Edwv65w+noFctlgh82TWRu92E5/p9/pP+/sPLsaDIaD/eHuwUe2CWFssH/wfG+vv797wOY3JKQG2jUorTJ3Ey+e2+ftzvO9weDgYH/7mK3t2Yn2HAx3DoaDZx/ZAixzDJmlohhHWIvX6SHbVrqzbddwKjOPbtLc2EunH9YcbNvL46qigzcYptbdxdBulzgqQ+nwITJfNpRgGqk39HYY2TgAakB+VcllCSNXKu5+t98dkH9lnnN3v6Ravn+4gVdXV+/g8N0ZBAuSBw7KQMgQLiu7Gq1dOAugzBh9IDYJDjsxcD5SR87CWVkKlJDebxNBkjm9W3IIGQ+gPCD39JYJFoQ1vsyxYeUTdHyM0HpzgEMde4nIiaZAFy+vRmDHOoUmoKwMcVg49GhCBZZQ+sqoxqAj67ALV/R6Is9bfqROyTFCimGKaEh95e0q5ztn6RbhQas7hCnXGoNPQKJAExzX6neUgF9FxilgSZQQ8QCU9yW6aBE02QgWfJnmKkAbFBP4UqK7pxRxIQg6mvddAtaBDw55DjhB09jR5iahS87uRmX93Svhup3Qm8dNe0qcoKYp61cGYW12T1iHHWMlPvlbVc8n88k06gQ3kCIdoadYThQH8f7iPAEOqbNTjy5qsAbBjmJUFrG+PH7tvxtraYXvBWu173l55ynSFhxSOUVpwtIt86sK9yT/3paOqo0CmsAUwaGweY5G0lEMFDekGJTxAbkkppzfKTMGqRyKEHMouNY++hnTOi6VRKg6JkUPmZ3GkMhcGeUDOmhKPJZjExtSERdNjx2OqmKO/h8vPH0EL7QdL2MwnU5XnV9QdlJtxz3eMTjt+NJ0aApl2Knnx5O4/vGW2oSLu7GzpZG0wVrrhqp2nMhUQBFKxzWonHoe85j5mCHlIeefrYN6dEBa5sWTLry0bmVBxlNbBqhNpADW+halYSWm3GMCIkNxB0Td9p9UwimFdhmAsQpZmXaFzXt1HJrvxtVeqm3ay7kyveOTDyfnb9+dvTnt5vJJTFd1JaHEpzhWJgEVHnmYWhcycKhCvC+bcbSDYEBFI1BkFmWDb9fUlvDGyh8BApBWlHkDMEN4+nSKIC0YG2jfaJ1HcKUxZEQTKEpZBUMcqGIk19QubZRY1NLTpxUAoC9QKK71fRQdeW8nXCsZHbzdmG1Ipe8QwtSCR1pMBmoeI9CZGlQkClsWuo5PTjCs8sK6wE2IBZbaGEateKo0dRxxtcqru1L61F05N3xMi1UqrqlJoOAOZUfaqVmUlx2tumqLoPIIeqSz5iRQI8izIzCI0sPjKT7SGlqdpTxwDxw+sSNexHFA4j6xReyoROIzwuX+7egS3UTRC3RxGWtnNhJ17CiOMhWXubT65CLeaetFbmN2u6BfUutVN/Zk7bK3erXDnKt4ilrbf7XPaMGkBBqPLV2HBRcZwk6XXgnLve/ipFOdLDXWcMLjafSpFup752dHJ28uT4ilm4Vcx01BYX3IuWmpbF7twGFj175+g5gtN8N/zdK9Xm0E/Bp6heYq7mCit7P6ln+9uVin1eJw67r9JmGZ9YG4ZjNCqfdOz+f0cxyUbHh9k7AJd4oYq7eY8vS3ZMMR1359J9/2//FFvXR5An98U7/Vz2aXZmiTVu9LGEvYHd5/6/8J9AZjGXKJ1SuvIj0UAovQErKxxKfXxOIRdXpyxebz/wFYdr6f
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Claimable Balance"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/claimable_balances/{claimable_balance_id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The single claimable balance endpoint provides information on a claimable balance.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./retrieve-a-claimable-balance.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retrieve-a-claimable-balance.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retrieve-a-claimable-balance.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance.mdx b/docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance.mdx
new file mode 100644
index 000000000..5931d4081
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance.mdx
@@ -0,0 +1,4 @@
+---
+title: Retrieve a Claimable Balance
+openapi: "openapi/horizon/bundled.yml GET /claimable_balances/{claimable_balance_id}"
+---
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-ledger.ParamsDetails.json b/docs/data/apis/horizon/api-reference/retrieve-a-ledger.ParamsDetails.json
deleted file mode 100644
index 1aa38a599..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-ledger.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"sequence","in":"path","required":true,"description":"The sequence number of a specific ledger.","schema":{"type":"integer","example":0}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-ledger.RequestSchema.json b/docs/data/apis/horizon/api-reference/retrieve-a-ledger.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-ledger.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-ledger.StatusCodes.json b/docs/data/apis/horizon/api-reference/retrieve-a-ledger.StatusCodes.json
deleted file mode 100644
index 6e02dfb4c..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-ledger.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transactions":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"payments":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transactions","operations","effects"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"hash":{"type":"string","title":"hash"},"pre_hash":{"type":"string","title":"hash"},"sequence":{"type":"integer","format":"int32"},"successful_transaction_count":{"type":"integer","format":"int32"},"failed_transaction_count":{"type":"integer","format":"int32"},"operation_count":{"type":"integer","format":"int32"},"tx_set_operation_count":{"type":"integer","format":"int32"},"closed_at":{"type":"string"},"total_coins":{"type":"string"},"fee_pool":{"type":"string"},"base_fee_in_stroops":{"type":"integer","format":"int32"},"base_reserve_in_stroops":{"type":"integer","format":"int32"},"max_tx_set_size":{"type":"integer","format":"int32"},"protocol_version":{"type":"integer","format":"int32"},"header_xdr":{"type":"string"}}}}},"required":["id","paging_token","hash","sequence","successful_transaction_count","failed_transaction_count","operation_count","tx_set_operation_count","closed_at","total_coins","fee_pool","base_fee_in_stroops","base_reserve_in_stroops","max_tx_set_size","protocol_version","header_xdr"]}},"title":"Ledger"},"examples":{"RetrieveALedger":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/ledgers/27146933"},"transactions":{"href":"https://horizon-testnet.stellar.org/ledgers/27146933/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/ledgers/27146933/operations{?cursor,limit,order}","templated":true},"payments":{"href":"https://horizon-testnet.stellar.org/ledgers/27146933/payments{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/ledgers/27146933/effects{?cursor,limit,order}","templated":true}},"id":"e1218a337cecda05526fba902c61d3d7130baa58d8db41f544bf563f779b6329","paging_token":"116595189421703168","hash":"e1218a337cecda05526fba902c61d3d7130baa58d8db41f544bf563f779b6329","prev_hash":"9eac16fecd885147067b58b7684f60d216f931b813f651265bbc97de4cea313d","sequence":27146933,"successful_transaction_count":26,"failed_transaction_count":9,"operation_count":67,"closed_at":"2019-12-06T22:39:32Z","total_coins":"105443902087.3472865","fee_pool":"1807264.7509661","base_fee_in_stroops":100,"base_reserve_in_stroops":5000000,"max_tx_set_size":1000,"protocol_version":12,"header_xdr":"AAAADJ6sFv7NiFFHBntYt2hPYNIW+TG4E/ZRJlu8l95M6jE9bsvzId+Gtul2mNMW4UZQ+KqSb/nbN8F1CTxAfQsyUy8AAAAAXerYpAAAAAAAAAAAXQNpS8daKGZUeY5quYUcIiJZBMB7LiLsZJsEx9qw79fx99Bu/lk+sIePNUNcuOC2euthzfhLuWJ1nZBuoQFDjgGeOrUOoh6z7HlbYQAAEG/dvCadAAABFgAAAAAIOwAqAAAAZABMS0AAAAPooSNtHXJNJKKWlBtgkAM1LBxzlzYjIlS0xwpjP+uCi76fQj59wgTy0+xtx7O1qTb+W6zcI2zWZnrUU/8v8RZHFBfoo20QYKh95+wWr348yZAexZpdrjhyCxbChxlVTZOX6nZfIgcYBMnZRkOTCLdPO76yeqpDhqu9KrPe3YPTO3wAAAAA"}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-ledger.api.mdx b/docs/data/apis/horizon/api-reference/retrieve-a-ledger.api.mdx
deleted file mode 100644
index e2cb176cf..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-ledger.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: retrieve-a-ledger
-title: "Retrieve a Ledger"
-description: "The single ledger endpoint provides information on a specific [ledger](https://developers.stellar.org/docs/learn/fundamentals/stellar-data-structures/ledgers)."
-sidebar_label: "Retrieve a Ledger"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlGdlSGzv2V1R6uUloL+3dfpkxBAhLWAJcggnlUrdOuwVqqZHUXqD871NS26YNJOEmU1N36vrFLuvsu44esSEjjXvX+BDoCJTGNx6moEPFUsOkwD18HgPSTIw4IO5gEAiaSiYMSpUcMwoaMRFJlRCLgaRABOkUQhaxEF3nODfvYmNS3atUKIyByxSULmsDnBNVlmpUoTLUFQ5EiUqUCUoSEIZwXVnAlCgxpKSNykKTKbCgTtz3ZexhS83x3qO4h7+AUQzG0M81wh5OiSIJGKtd7/oRC5IA7mEN9xmIELCHmdUzJSbGHlZwnzEFFPeMyuBVYywQkciSABSSUVHhXDArlg5jSAjuPWIzSy1HJgzkEsGUJCkH3KvO5zeWp06l0KAtcK1atV/rfM+yMAStsYdDKQwIY0FImnIWOs0rt9rCPb5kKoNbCI21grJ2MiznMoQkAEqtnj8DVRBKRXUBkChFZtZuBhL9Bl6cibs3wGng0c+hYgVFKG0UEyPs4TwCcQ9bbnjuYQNJyolZUzGQkgMReD4vevo6J3rjYcOMdcsTDUWEJqE18RsU+J+Ktor6v5tgKZnZ7P27iQVRBOHfTKpnQC4BngXdmqOftLiZe5jR18RccmA0d8aIidHQyDsQP4Jeg5t7OCY6/hG8O7f0FQzfCruquK+VxJV1mTD1mgPPa16U8WHBIsNQZnn5ewOJiDAO9JfRV5b/S1hmOtRghr+GHHKpgQ6JeWlQS1oawoehZGtJ/3QeAQxTKfmrhwHRMLQQTAy1UVKm+o1COUwFGtT4F7ATMh0ubKLZw1u9nyppZCj5cAxKMyneiBYDoaCGU6pesYH9rGcco/hZjixC3yvOBz+MxB9E2csI+m50FD2/7ueCV1/34ff989L2r9h1zWY31kDLvF0MUPPVvOI8/ny+6j3iMeEZrHf6ZS/PiyleTn+xVOxBipIBbQSYtRFwMdJVam2/0erW66/1398gVynSevxXmCktlcdZwownFQU1x2sl3Y5/L9rs7/B/ovR27sVe+ju8l3TezrnQLn+H8YLMW/kuuhoGv+Z3SL3eDiGkpNps1lpRQLrVWtjyaZ22/Xo1IKTZoR0aNPyo2WgEUbNVj9rtbtCq17rPs7qHfb/V7Db9TrdR89vVut/qLFP9v8NNwXjRCHEXSOi3Ighpp9P0G+1qqx00O0G71WlErSqt+a2oW/eDjl+PWk2/1moGQdhtU2iEQOp+nRaLT29pyZ/1w1rrR+2u+0oza7XX2g2uVf1uya+Vqq3zWq1X7/bqtcGzWtTDfrXZaNS71Vq10y7XG+1ap9Uslqge9jvVdq3VKLeb1W6r5X+naPX8avUHjaVZdZ9Xmofv/n7ZHfzaevHH/X6//3G/pXfG7SO2s/NpU5grU4tPro72LjfOdxvblcGXfZ51eLf5uXW73Q30+GGPbuyajNeSo8+XjYvB6cbB/VlQEcFRZ8ffOp/2o1M9u5h1LOn+V1BXaf/p8/X0KD3rUHKwO7iAq+Z9dnUR7rH9webnzfYhO9SDfb097d5P2t1o2u1uZhV+t6H34OTo4ijMjrdqkJn4IYoPs8t9Xww2M3m68/F2tAvH6uJYxq2H9iceXJ32+9u7FTreIrTf72/ujBzrveNJ/97+GPQ3P59V7a8TKc+OzKev+0f7BweXfNOM7vqf/cPN6QN/uLrd42fV6SS9PdnItli7FZ3eNruT0fmsujE10/axf38ebFy2HsK92sPlQKiLi0pn3Pky+LSzGUlZq55eHcTd5sbkUtUbndmgD9NBStVtPNuaBlvxlP95Pjj+2hKDaG8UXm1+FoMvd8fnW4f05LjdmsF9+jG+z7oH6gTqVyfnx/WJUyJvz7YCJGBiaavACNx0bi/mPbyqLY/L5Ji7RFHj5cU+U/xtZQq/dq0/z+HQEZiJVHbA/x7FKLM7iLfQ3FlCIrGkemPXDZF008miz37K6WIPr6IZV8vVsu9GjyQhavYE9bR0IQJ9Oj8/Qf2TPWQkshsSxAQyMaCzXK4l1zLaM4iJEWhj0ShSUHKG0w7aYaZK0iwEioLZayQsZYLsvIVMTAxiGgHRDJRlHUqhswSWqGQMiowAFfYTSAEnho3BgluYFJQb3kQIJakYCAM0F0RBaiuCMHmvRJnOhVoKtCUVlNF5zLTTvKBHoBgdAQrATACEZZ9ru455oqS99mnE2R2gCeEcjPYQhRCEUYSzB6AIpmFMrME8R4FoDVZnnYFyEqGlN4xEOgsSZlBxvPDQfQZqZl1EQlduUUC4VdZDUiFtFJAEwdi25FyOIrYl+oRZfhFZ//RIuC469KebxYXYlVAqKAlJ4f0/Knq+iW9iyS4kAgVgj0BbW44ZQeHFl0MPERQoOdGgHAcpwG41rVVWtj77eKDftsU1UtrFLb3T1tISKbDh5KiF0l4jpszMLP2ZzJSNNmtQD00A2U1jkoCg9sgZigjLGDGhDRBqkRJyx8QIUaYgNM6HIeFcOz2dW0cZo4DyjAlAo1hOnElowgTTBhRahrgLx6VtLAtrYvROQZQHs9P/40rTP9Aml6MnG0wmk3XlV5ClgMtRhZQETEo6EyXbhWIoLfrHe5s8SEubJiS8GymZCWrX5s+yIY8dFcbMgN16E45YYnMe3Cife4hplJBbqdCidaAgS9L3ZbQj1dpWngQyM2ghojXggt8qNCQFO415KIwhvEMWuqi/ZYl2rWmfDDBiJs6CciiT5Zp+ta5fqFoJuAwqCWGi8nH7z+3D45O9o91yQt87d21CJBVYxwcwYsJDzPyh0UQqEyMFzLh5VYycHLYMMCcEhLEEuqxv1zYt0ZGkv1IIEJVhliwLTA99+DABRCUS0thHDqk0IJUJYYVYGsq6LC9DBNmIoYTbdClWiVUsffiQFwBwrwOE85kj7XCHY8IZdQoOX/Q2sKGvAJmJRBrs+4WxySNCUGJRVCiEMkv5wj6JLcMsSaUyRBgXYIF0ZuSMBIzbjLNYhfAqr4W+za6ECDKyrzk2uCbCQylRQEtUTsQqvGS0rqpMDUtc0bM8F5i2qNmSJyMkAKhG7ybwB+eokFlMI6IRQd/wFkldO7DkvuGV7WyIuAuiSvRxdAZqzEIoDGNFzzqgkoxcK2NuZWOfSUjotmiL956l2MWA3rGp55yPvWfD3vpoBwlh7hQ4l/8uns09zFkIQkOBVz8lYQyoVq7aVxJqYzdioFYnpfzkieOinBB3mt+kc6K6cri3tX10tm1RyrFJuNsap1KbhIgCy+VaBhG0evhaGxsen56O/g/e9BabOwNTU0k5YW4p7ez1uLgQXOMFPPZwb3VfvvFwLLWxx4+PtqBdKD6f279dT8W96xsPj4liJLCz9/Ujpkzb3xT3IsL18xe/otXefVlsDt+jv/IO+Koqy5c0Yd/RFvszjD18B7Pi2+T8ZrXTdMLmx/0whNQUEF+8BNprxuoatbt9jufz/wDNHnRS
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Ledger"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/ledgers/{sequence}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The single ledger endpoint provides information on a specific [ledger](https://developers.stellar.org/docs/learn/fundamentals/stellar-data-structures/ledgers).
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./retrieve-a-ledger.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retrieve-a-ledger.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retrieve-a-ledger.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-ledger.mdx b/docs/data/apis/horizon/api-reference/retrieve-a-ledger.mdx
new file mode 100644
index 000000000..521720fb9
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/retrieve-a-ledger.mdx
@@ -0,0 +1,4 @@
+---
+title: Retrieve a Ledger
+openapi: "openapi/horizon/bundled.yml GET /ledgers/{sequence}"
+---
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects.ParamsDetails.json b/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects.ParamsDetails.json
deleted file mode 100644
index 5ff40a72a..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"sequence","in":"path","required":true,"description":"The sequence number of a specific ledger.","schema":{"type":"integer","example":0}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects.RequestSchema.json b/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects.StatusCodes.json b/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects.StatusCodes.json
deleted file mode 100644
index f081b3c78..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"operation":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","enum":["Account Created","Account Removed","Account Credited","Account Debited","Account Thresholds Updated","Account Home Domain Updated","Account Flags Updated","Account Inflation Destination Updated","Signer Created","Signer Removed","Signer Updated","Trustline Created","Trustline Removed","Trustline Updated","Trustline Authorized","Trustline Deauthorized","Offer Created","Offer Removed","Offer Updated","Trade","Data Created","Data Removed","Data Updated","Claimable Balance Created","Claimable Balance Claimant Created","Claimable Balance Claimed","Account Sponsorship Created","Account Sponsorship Updated","Account Sponsorship Removed","Trustline Sponsorship Created","Trustline Sponsorship Updated","Trustline Sponsorship Removed","Account Data Sponsorship Created","Account Data Sponsorship Updated","Account Data Sponsorship Removed","Claimable Balance Sponsorship Created","Claimable Balance Sponsorship Updated","Claimable Balance Sponsorship Removed","Account Signer Sponsorship Created","Account Signer Sponsorship Updated","Account Signer Sponsorship Removed","Liquidity Pool Created","Liquidity Pool Removed","Liquidity Pool Revoked","Liquidity Pool Deposited","Liquidity Pool Withdraw","Liquidity Pool Trade","Sequence Bumped"]},"type_i":{"type":"number","example":1},"created_at":{"type":"string"}}}}},"required":["id","paging_token","account","type","type_i","created_at"]}},"title":"Effect"}]},"examples":{"RetrieveALedgersEffects":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/ledgers/0/effects?cursor=&limit=10&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/ledgers/0/effects?cursor=33676838572034-1&limit=10&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/ledgers/0/effects?cursor=12884905985-1&limit=10&order=desc"}},"_embedded":{"records":[{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/12884905985"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905985-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905985-1"}},"id":"0000000012884905985-0000000001","paging_token":"12884905985-1","account":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB","type":"account_created","type_i":0,"created_at":"2015-09-30T17:15:54Z","starting_balance":"20.0000000"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/12884905985"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905985-2"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905985-2"}},"id":"0000000012884905985-0000000002","paging_token":"12884905985-2","account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"account_debited","type_i":3,"created_at":"2015-09-30T17:15:54Z","asset_type":"native","amount":"20.0000000"}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects.api.mdx b/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects.api.mdx
deleted file mode 100644
index df1d3a4e4..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: retrieve-a-ledgers-effects
-title: "Retrieve a Ledgers's Effects"
-description: "This endpoint returns the effects of a specific ledger."
-sidebar_label: "Retrieve a Ledgers's Effects"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlGtlyG7nxV7rwsD5qeOi2WbWVyJRsXStpJa4dW1bJ4KDJgYUBxgBGtFbFqvxGfi9fkmrMDDkUKVnabBJvVi8qAn1faDTmhnk+dKxzxg5QDNE6dh4xgS62MvPSaNZhvUQ6QC0yI7UHiz632oFPEHAwwNg7MAPg4DKM5UDGoAKhJouYydByorIrWIedoLcSr3Cz5LRdYLOIZdzyFD1x75zdMM1TZB3m8EuOOkYWMUlyZNwnLGIWv+TSomAdb3OcFxahQgSdp320d4rn4gRTzjo3zF9nxFFqj0O0LGL4laeZQtZpj8fRRKI4t87YSp4vOdrrGYEGXLk5iTYrMXzCPQQjOvBmRiQTBzOB1MAhNkphHH6bAVh0mdEOHXAtQDrIcqVQwMCaNDgh40OphxfeXKKGK65yLBS2GBsrHqrn+np7fX1pY3Xjxcu1l0vttbraxgp8vNYCnRxqXulBogZCpOQokXFSSujAJSZXAniWIbdNOAo0HEgdq1wgfOIu/gRPuYtRC6mHz8BY+ETsPsFT+lcuN2GX2EgH3A7zFLUH6fQ///4PDw59BNKDwAHPVWH/QHaheZy3Ug/JOjpPKTW4i1mhIDuvG0bJVPpHGoYCNOVfZZqntfisTFFkF4omEFygDzHXYLkeYuHzJRJ+ud2GBnANeZahLQFDgEkHCbciNgIFmXrHWPmr0TAwFjK0A2NTTrlhkTuj3T1GqxyIYs52S+2HxtVSezw+J6OUUUzQy+02/Zu1y2kex+ioGsRGe9SeQHiWKVnkRuuzI7ibGleu1NEgVIySv+l/xpgcklkqPV4W/C6U1JeuJucdcA7V4NtQicXBomAJlvUhKvQlG0fMY5opMl8Num+MQq7ZeFwPlLOC6HnEvPQKazQ0fvXfmUiZxavvSqQxgVVLB8HVlKPfiAlM+yjEDNs7QMvcrAFyazmluvSYPiCuHhp/k+PyuzJvxBylJooHaPDfDsQYBX5fYhGUFIuYVXBSBOFrp/Z90DNw44jxODa59otQMu49Wqqlb842Gx/ajZfnN2tr4xoxLoSlGkuaBuS7j7zNgg90LQZ7RJOVE0zN1cxK16KQs0Bb2L+10kssusQo4eCXTNyiuWNShC2TcqkX7L5WfLgIa1cPVNFfbKHzsuw1pnCncqjR1lQoF6YalAtTlJ7NnVdSYw1rujZFnK4twt3MfULH7q3lLeT1jaPBYEa64veUR/G7Tp8Laoa3uOc1tPBzihV+TpG6isuU9xXCK67CwT/FXLAXVmbcfgfQjCNO6Ww31iUyWxAw9d15J9Z3F9l3Me3F+4t8sZj+JE7JWveLPwcyr8McyJTRvPkWc7sf7j5/3q9gGeHf8NA80AJHzQNN2R3IL7kU0l/DsTGqxuLWxp0YJ3hlLhdtbGFmnFxI7J30ibB8NL9TpcppdRN8lacZCnZeVr4LWat9RRc+07SOIxYXKlzwBbV2XPQc9dNACnarqE9rdVltJ6xniJ/Xu5fiSszGJGcpTTjA7ro6d25YuPHNdhlVH1sceyzxPnOdVispbgINj85r9E3nUSlum8YOW8Wl2LXarfJO/5firvvjD+Fq8eNS+4dwefuRrkK1vvT3YLGysr6x/mLlxdrGcntltbF0B8uq7/w9WC4tv3ix+rK99vLF2jy/cM8jr8z0iJMu8Kxu6pmW7RGSTfBcqybL7WbrEQQrBacq/LBI19t902/mwO9kUDZArF3+1bfbk8Xb2dJhs2RqnQ57s3lw3O1+OFx9/7fNlfc/7e3sH6x33+5ud/ePD/b2ur23P50evn/3qre/9251f23n54P3B1s/fei9qhKvU9G6iCd1qaoC7dlMZ8vtpbVG+2Vjpd1b2ugsrXXWVj/QVddz60naflF1A2SzVCZcN/6wMbH8n46J5QfGxPL9MbF8KyY2P+yu9ronK733a0d7O93eXnd5c/Xn0/fr3b13eztru5t7vTf7u4fL2ycbB68O3+4fdbvvDjfmY0JMWtUqJlYeFhPcOfQX1SHCvbyiGs/TUsJ6fJyPy7+IpegTQ7YYoi+a9oR12KRU3VTDy3FlXIo+tFfVcDS36mHOYYsmT70CDg7Rj4y9DJG7mOIg97nFh9B8XUGCrqie00xsYMLJWR5t5RyKRYxUKbDbzXaTUt3lacrt9RQKMmuupAhDT9jp9Y5h83iXBk+COi2pwzTxtJCr4tqEXQ9SD9H5YlZqsREMV8yqA2ZmjchjFNC/XkSimL/SrXAyS0PuJM1uDcRGuzzFCpVfoeVDhNqICiyqEAYEHkaz03lbw1iJ2qMoBLGYWXSofZHwkLtCqEqgrrFIM0DpguY1PfpWiiFCH/0IURP7QttZzGNrPofRvJKXCCOuFHoXgcAYtbdc0RUE8Guc0FzRRYFCiGeQzuVog0ST2aE34PJ+GDFarh0Pw2kXQRh5kovKXIKyOkY0oXXeIk8Br1BXctSxwwh8gtmci6w/eySc1R16/rRKT4FXqOikcDOFuBS7FRuLDW0EPvtTRc9H/VFX7Ghc3kfaQke2vJIc4l9ODiLg0Ldm5NAGDkZj9S4xsfXp1r77pq2FiV3LG6Ncy4lLR5Y2YJHCKVCLDfXtX+kyYgZwbXJL0UYGjWCEYdSfpqgFbQVDcU2MQWrnkQtCSvml1EMQ0mLsgw9jrpQLega3DnMpEIqM6aODxIyCSUQqtXQeLVQhHsKxsg2xCJfGpxYHRTAH/bcmmj6BV8oMpzYYjUazyk8gG31lhi3e0DhquFw36BRKsFGeH8/Cg4OjuU6fx5dDa3ItwOjb2VDEjo0T6TH2ueUKZEo5j2nwvClfJ1L+2Vgojw7o52n2rAmvDb0mFVM8WuZ9k9NDRRCRDFjym4SGEdjnDiOIE4wvgaDr+ofnjzdk2qkBhtIneb8Zm7RV2qH6X6na6ivTb9HsqrW1/Xb74Oh49/BNMxXPgrte4cBYJMf3cSg1PaU8cTAy1tMDmPSh59PDIAeVARmEwDgxxftNkI/SEg6N+C2FAISJw8NOsFEHnj8fIQgD2nh61TXWIdhcaxKiMhS5rChDHChiBFeULvUqMYml58+LAoDhOZMrdR1IB9yLK66kCApezJ1tSKFvEfzIgEN6A/aUPDpGq8uiIjA2eaZK+6RUhmWaGetpRkUB1jfBjEryvlSUcYRVC6/mTOhTdqVc8yE6kBRcIx1Bxi2KhjAjPQkvM5hV1WRepqHoEc8Sk4oalTwzAE3NOTwd4ROloJZZ9KrmgMNH1uVZOA6I3Ec2sR2FCDWeaFN3NDhFeyXD3aJyct2zAahhBuEok+FZnF7KeBwu4uWLZCV2PaBfU+oVF5LoVrM329phymXYRaXMX+t744gpGaN2WOO1mfE4QVhutukpRFDsDiTayU6j2JlyLMsJD7vFBb0g6loHu93tw9NtQmkmPlXhypAZ51OuayyrOQhwKCchTxxMvyOY6SBupg+J/8YnDGV77/Grb2WKyzCEDyrdlL37GSt7dxaxTu2bhap9P49YYpwnwJsbqj6/WDUe03LxYkxNvZCOZnp3vBnXNfnff02w0CKXeF3/PqIcSrFwv3iMcn+YjwbusUL1ucRvNML/0QcC9xip+nRiaqRz+mElWemROfH0pBzEPoPHfP6zULpqOKCv68JVUk/SO0xoE+TkaRK22N6MY8zqWs19v0BaTiYAb7Z7bDz+F8TxCs0=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Ledgers's Effects"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/ledgers/{sequence}/effects"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint returns the effects of a specific ledger.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./retrieve-a-ledgers-effects.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retrieve-a-ledgers-effects.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retrieve-a-ledgers-effects.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects.mdx b/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects.mdx
new file mode 100644
index 000000000..94a736f98
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects.mdx
@@ -0,0 +1,4 @@
+---
+title: "Retrieve a Ledgers's Effects"
+openapi: "openapi/horizon/bundled.yml GET /ledgers/{sequence}/effects"
+---
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations.ParamsDetails.json b/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations.ParamsDetails.json
deleted file mode 100644
index 6f27af90d..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"sequence","in":"path","required":true,"description":"The sequence number of a specific ledger.","schema":{"type":"integer","example":0}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}},{"name":"join","in":"query","required":false,"description":"Set to transactions to include the transactions which created each of the operations in the response."}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations.RequestSchema.json b/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations.StatusCodes.json b/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations.StatusCodes.json
deleted file mode 100644
index b198f05d2..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"_links":{"type":"object","properties":{"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"type_i":{"type":"number","example":0},"type":{"type":"string","example":"create_account"}},"title":"Operation"},"examples":{"RetrieveALedgersOperations":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/ledgers/27147222/operations?cursor=&limit=2&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/ledgers/27147222/operations?cursor=116596430667259905&limit=2&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/ledgers/27147222/operations?cursor=116596430667255809&limit=2&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/116596430667255809"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/3a644389bbec63dd2b107a03c16711563fc549daa7b7f56f951a2e470f81f2e0"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/116596430667255809/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=116596430667255809"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=116596430667255809"}},"id":"116596430667255809","paging_token":"116596430667255809","transaction_successful":true,"source_account":"GDQWI6FKB72DPOJE4CGYCFQZKRPQQIOYXRMZ5KEVGXMG6UUTGJMBCASH","type":"payment","type_i":1,"created_at":"2019-12-06T23:05:38Z","transaction_hash":"3a644389bbec63dd2b107a03c16711563fc549daa7b7f56f951a2e470f81f2e0","asset_type":"credit_alphanum4","asset_code":"NODL","asset_issuer":"GB2Y3AWXVROM2BHFQKQPTWKIOI3TZEBBD3LTKTVQTKEPXGOBE742NODL","from":"GDQWI6FKB72DPOJE4CGYCFQZKRPQQIOYXRMZ5KEVGXMG6UUTGJMBCASH","to":"GAD35Y7AEQYS4WNZND5OV7HQ6ALBDDNTNFO2TN2CM4ERE7ZV4FJBNXZ6","amount":"0.0000077"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/116596430667259905"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/83eabfa824b57436eda49bb9ac28675285f6d945325f69db41792078a83d3479"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/116596430667259905/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=116596430667259905"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=116596430667259905"}},"id":"116596430667259905","paging_token":"116596430667259905","transaction_successful":true,"source_account":"GBE63IHPHXHKQHIF7L5P5MGOV4MMDYE6RGZCJYWJPBRQZDJ5MOAPOX7A","type":"manage_offer","type_i":3,"created_at":"2019-12-06T23:05:38Z","transaction_hash":"83eabfa824b57436eda49bb9ac28675285f6d945325f69db41792078a83d3479","amount":"0.0000023","price":"0.0484621","price_r":{"n":484621,"d":10000000},"buying_asset_type":"native","selling_asset_type":"credit_alphanum4","selling_asset_code":"RMT","selling_asset_issuer":"GDEGOXPCHXWFYY234D2YZSPEJ24BX42ESJNVHY5H7TWWQSYRN5ZKZE3N","offer_id":0}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations.api.mdx b/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations.api.mdx
deleted file mode 100644
index 69e9514ef..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: retrieve-a-ledgers-operations
-title: "Retrieve a Ledger's Operations"
-description: "This endpoint returns successful operations in a specific ledger."
-sidebar_label: "Retrieve a Ledger's Operations"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlWuly2zgSfhUUfkySKVr3YalqataHfNvyFV+JywGJpoSYBDgAaMXjUtW+xr7ePslWg6QOW+PEOXazu/6jMtFA3x+a3Xyglg0M7b6je8AHoA299igHE2iRWKEk7dLToTAEJE+UkJZosKmWhpg0CMCYMI2ISkAzJDZESMKISSAQoQhI5I4sUY9OSLY57dJjsFrAHazkPPuTA6hHE6ZZDBZF6b57oJLFQLvUwB8pyACoRwUKlTA7pB7V8EcqNHDatTqFp5IDKTYSmcY+aKLCxRKaYAgxo90Hau8T5CikhQFo6lH4xOIkAtqtjMfeRKIg1UbpQp4/UtD3cwKFLDJPJFopxLBDZomzqCFWzYmkAmeLzJaBiiII3P8qJBpMoqQBQ5jkRBiSpFEEnIRaxcQOgSRsIOTgxqpbkOSORSlkCmsIlOZfqmerVWm1qu1Ge7nT7FQrzVm1lebwcq05GDGQrNADRXUHoZKjoQiGuYSGmKFKI05YkgDTJdJPisAKopQD+cBM8IG8ZiYAyYUcvCFKkw/I7gN5jT/54xLZRjbCEKYHaQzSEmHkP//+D0sMWI8ISziELI0y+7tjF5rHWC3kAK0j0xjzhJmAZgrS61nDRCIW9oWGwQCN2ScRp/FMfBamyFINeIkgnTufBEwSzeQAMp9XUfhapUKWCJMkTRLQOaELMGHIkGkeKA4cTb2ltPhTSRIqTRLQodIxw9zQwIyS5hmjFQ4E/sR21cqXxlV1LoFyl96ETETAX2i5E7DIG7Mef4vwyM56hEgaDMr6NJjcbswkx2KhFr5SETA59b/DGUc/5/2PSsivVYFJw4JMshlVMEfm1rI8CTSgFwiwYDhJpTl18UkBFCU6vkZBcthAxWqVCv48kiVDc+rRQEkL0iIJS5JIZGBU/miQ7uGpgZT/EQKM+0SjGFZkXG4iIW/N5+kgDCGwX0A41BAuSksXw9bln7ylY49aiJMITbTAi+PxrFfeZYdee9QKG8HMGYmGADj8bGIZiMKfTSQMHP6zGWomb34qyZBK8EXMCjrBXfzNXOPPUc/RoYT3CdyImR3ZpTJfw3j54oIrriCiGcrcsCBQqbROu4LnpFhDhvkOZ8dnqrruA3XFyDwyFOGcOYAOrU1Mt1weZpfUkgVjJdiSsRBFTJeUHpSzes2Ua+1qo12r1cpT6Ps9K8h++8Xdf7/VfnEFxm94XY89KuGT/f68qtVWs9Nq1CutVrvW7HQqzcXcEw13P5p7c7nSecTdFSnouxuIfeA8i9y8vHDV9Tc5YypR+akoC9LwBUfPXnzlOms1GvXlju9D0KpzXvOrlTar1INqq12tNlv1MGg2Opyxtt8Om62w06yyGjTalXC5Gtag4gJ1es98Lw3LxZkFDOY4+ILz8xN+n7rrl7/07eN76avZsOe55BBFF6w9BqbFNDO+u5m+JRZvaEalOpgiS5durh+db7c2dlfbtfXD/k6vsbZ5ubZxdLV7fHh0tN2/vDjev2ru9s42L/Y3W2/fnm7u7K+urZxs0QLHaMLusValU/yrejmC8RuH4LVKtbNUrS1VWqe1erfS7NaXrx5JOmRmSLv0m2PNo8wYsDe5bIEGLuwNi5Ihk2ncmKxjTU679KC/vjd5JoxJQaNNVmuX9ZXzi7Pj/n5tdWvjaPfo8PR8d7u/XT+96q2urtf3TndPz45Od3uHF5v91V67UctPwteCb7Sqwv0r6/XmZXuld3R50jg/uDpYb/bP2ltHrZW91fX1g9ODjX7t9KC2tt/oHffaV2eNjZ3Vg4urFuoS556tlCr4125TLJR/DNQg5n5HqFmuA/NDtlxr+M12o94Czhod3++woLbcajdry82wxTuNZr3WDFsd7jeq7U6t0l5my3Veb7Q7PwBqUMN/I9QUBv2xUJNxWQw1bu0zUJPTvBRqVnut+vbW4dbF1u7R1vZGe6952Nzf7J819vfXL3ut482rtZ3L853D1eOjq/Wd5n5/5bB/0V6ZQk3MJBvAjQpDV1UVeFP/arz55oB7mm+1uitxRQDZs8Zyo1WrFs9uNHpU0m722KMc38uzv7FH/fQerT6HYdi3ucPOm4EoerK6AOHm6XKkO94/fbI0Bbz13mb/4nBt6+J84/KyVm+s1y6vTg57O7XG6kWj1jvZOTjbumxutU/Pz49OLo8Pmle7V736AbYW0Rc3GEeV8fU4//NoDHaoMLgG4Ep+7Bd26aSseij6guOZzHPy6bui9Zjq6Muini7q65xmdOQA7EjpW4eBi08MU5tq+JIzNwpKIotTr7HpECpXzucVet7loR5FVbLdlVKlhDFg0jhm+n5KRRKt7gR3LUWydXp6SFYOt7EPwZllRTvhJJOr4Foi25YIOQBjs06khiVnOOOo3c5EK54GwIl/v+iIrLuJr1iTThUwI7AzqkigpEljKLayO9BsAGSmH0E0RC4qXQcFG5/TbtaS0gIk9kicIBoSDQakzTskqcmEKgRaUxqwwyaM03xGD18LPgDigx0BSGSfaTu/81ArfK00JBK3QEYsisAaj3AIQFrNIvEndms+BUPs2hnPneCin2TR7ySadOasIib1XQNv5l7yiOspoYtyNCM+i1BZD/ufxmpgMYE7kIUcj7tK052lJ5H1/x4J72Ydev26SE8OdxAhOJi5Gy4XuxwoDUtScXjzfxU97+V7WbDDZrQPuAQGbXknGAneHu95hBFfq5EB7TgoCUWrcmLrk/Vd81lbcxWYslUqMmXDbw1aWhENGE7utEBh9+GTsPd4/r1KNUYbGtQjI3CN9DgGyXHJGYpJZEyENBYYx00xuxVyQLjQEFjnw4BFkXF6OrcOUsGBZBnjgyFDNXIm4bGQwljQpAhxF46FbZCF662/1hBmwez0X59o+oqsRmowtcFoNJpXfkK55EdqUGZLEkZLJpVLeAsNYSm/P964dr5RmCYsuB1olUpOlHycDVns6GAoLAQ21SwiIsach9h5XuW9/5h9VJrkVwfx0zh5UyIbCmc1WUsMHzNfpTgGcCKiAXN+k9BQHHxmwCPBEIJbgtSz+rvhwiaadmqAgbDD1C8FKi7ndih+C1XLfqT8csyELK/3znp7/cPtg81SzN84d61CqDSg430YCImDileGjJS2OF4S1l3zcuDkQBgQTggIhiqbjjj5MC3JgeJfAwSEq8CNTZyNuuTXX0dAuCJSWRygKm2A6FRKFKIwFLosgyFGMGI4izBdZlFiEku//poBALhhIYuie3e023tzxyLBnYI3T+42wNDXQOxIEQM4YbWYPDIALXNQ4RCoNIly+8QIwyJOlLZMWhdgvnJmjATzRYQZh7tmwqs0F/qYXVmxbIjA4BpJjyRMA1/iaiQn4aXCeVVVYkXsQA955jsR1BDyVEgkvvqQ1yN4FUVkJrNwZmUII+/pGkvcdYDHvacT22GIYAkOOjb98AT0XVYgF06eeyVEoiUVuqtMuKEzjkVY4FqI+cSnEHs2oDcw9bLmqPeo2Jsv7SBmwq1CFKm/za6NPRqJAKSBGV4rCQuGQGol7C8IjrEbClc4ZytL2cqUYw4nzK1m/cTsUFPe217rHZz0cEtpaOPIvYYlytiYyRmWRTeXMJL1c18ZMjenn6shHqZzo+/yvUD+bmHhky0nEROu2ezUe8hL+Xc0L+WpR7szXwfMVPPXHh0qY5H24QHB6K2OxmN8nE3osMbnwjA/+qsZ3axa//nR/UKj3ML97McIeZuduteNlyj3XzOhf8YKxbcJX2mE/6Fp/DNGKr5T+Eoj/aDB+zMCP/lOYF7yzwr6Q8frz0qefxQwlfca/9ECTf1C9Hl9nA8X35CXfNW0ULj8IZP3s8IVQk+wdHw99ugQGOYUCpstrwQBJLPx8+QrAdRy0n3Z7J3S8fhfijA00Q==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Ledger's Operations"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/ledgers/{sequence}/operations"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint returns successful operations in a specific ledger.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./retrieve-a-ledgers-operations.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retrieve-a-ledgers-operations.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retrieve-a-ledgers-operations.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations.mdx b/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations.mdx
new file mode 100644
index 000000000..5f3205631
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations.mdx
@@ -0,0 +1,4 @@
+---
+title: "Retrieve a Ledger's Operations"
+openapi: "openapi/horizon/bundled.yml GET /ledgers/{sequence}/operations"
+---
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments.ParamsDetails.json b/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments.ParamsDetails.json
deleted file mode 100644
index 6f27af90d..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"sequence","in":"path","required":true,"description":"The sequence number of a specific ledger.","schema":{"type":"integer","example":0}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}},{"name":"join","in":"query","required":false,"description":"Set to transactions to include the transactions which created each of the operations in the response."}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments.RequestSchema.json b/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments.StatusCodes.json b/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments.StatusCodes.json
deleted file mode 100644
index ff89c06b6..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"payment"},"type_i":{"type":"string"},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string"},"asset_code":{"enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","asset_type","from","to","amount"]}}}}},"title":"Payment"}]},"examples":{"RetrieveALedgersPayments":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/ledgers/27521176/payments?cursor=&limit=1&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/ledgers/27521176/payments?cursor=118202550867476481&limit=1&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/ledgers/27521176/payments?cursor=118202550867476481&limit=1&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/118202550867476481"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/971454b84a82baa38afa975e9eb4ff2632821b5a3e7f7993a7e20bbd9d7633ea"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/118202550867476481/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=118202550867476481"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=118202550867476481"}},"id":"118202550867476481","paging_token":"118202550867476481","transaction_successful":true,"source_account":"GDQWI6FKB72DPOJE4CGYCFQZKRPQQIOYXRMZ5KEVGXMG6UUTGJMBCASH","type":"payment","type_i":1,"created_at":"2019-12-30T22:35:49Z","transaction_hash":"971454b84a82baa38afa975e9eb4ff2632821b5a3e7f7993a7e20bbd9d7633ea","asset_type":"credit_alphanum4","asset_code":"NODL","asset_issuer":"GB2Y3AWXVROM2BHFQKQPTWKIOI3TZEBBD3LTKTVQTKEPXGOBE742NODL","from":"GDQWI6FKB72DPOJE4CGYCFQZKRPQQIOYXRMZ5KEVGXMG6UUTGJMBCASH","to":"GDGJS7AXAUFDZARIRDVZ5V7CFW6XY47WSBE2OVLCCGCDWOE7INKYN3PS","amount":"0.0000017"}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments.api.mdx b/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments.api.mdx
deleted file mode 100644
index 1e4e341b5..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: retrieve-a-ledgers-payments
-title: "Retrieve a Ledger's Payments"
-description: "This endpoint returns all payment-related operations in a specific ledger. Operation types that can be returned by this endpoint include: create_account, payment, path_payment, and account_merge."
-sidebar_label: "Retrieve a Ledger's Payments"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlWutSG7kSfhWVfmwu5TsXg6u29nAPgXAPSSAU0Ug9toJGmpU0OCzlqvMa5/XOk5xqzYw9BpOEZHdPdpc/xh5J3f31191Sa26pZ31He+d0F0QfrKMXNSrAcStTL42mPXoykI6AFqmR2hMLPrPaEaYUSdlNAtrXLSjmQRCTgmU4yxGpCSMuBS5jyYkKazfIfjmA+JsUHPED5glnmkRQLAyCRDfET4mUmqtMQI9wC8zDJePcZNrXSvn4jx9cjr8xLUgx5jIB24cGrdGxbtuC9ugReCvhGlYKqw/yuY7WaMosS8AjFL3zW6pZArRHHfyageZAa1QiKCiR1qiFXzNpQdCetxncRw5IOZHoLInAEhPPAIbWqOMDSBjt3VKEhvao1B76YGmNwieWpAporzUa1cYa8cw6Y0t9fs3A3kwpFDPl7mm0UqoRkA/wOuLNlEqG5y4KLuRGKeDhu4mJBZca7cAFjKUjaaYUCBJbkxA/AJKyvtT9S2+uQJNrpjLIDbbAjRVfa+fiYmtxsd2d7y4tLyy3WwtVs40V8HirBTjZ16y0A1UNC6GRw4Hkg0JDR9zAZEoQlqbAAmNLPgcOkg/M8Q/kKXMctJC6/4wYSz6guA/kKX4UPzfIdpzTmNl+htwi0un//vs/njjwNSI9ERCzTOX4h2VnwuO8lbqP6OgswThljtPcQHpRBUbJRPpHAoMETdgnmWRJhZ8lFGVENgiOC+uHYLVM9yH3eRuV77RapE6YJlmagi0GBoJJRwbMCm4ECIT6hbHyN6NJbCxJwcbGJgxjwwJzRrvPgFY6EMQ97Nqtr+VVeyqACpdexkwqEI9E7hg8ysaox8+SHvladxKhBYe63idTmI2RFETMtCIyRgHTE/+HPBPGT3n/o5H6W01g2jGea1YxBWNk6lkeJ3kOFgQYH4xDacpc/KVMFA06ukBFirSBhnVaLfy4o0vGOThMv9xoD9rjEJamSubJqPnR4bjbCkBMqf04pOgCKhN9BI4RkFpUyMtc3qWS+spVIH1gnAMVf3nUwEI8KzoDlX0IQ31FRzXqIUlDVZzhzNGo6pzzfNGLGvXSK6isoeGT/8FUSi1c/1AqjXBY+dNucDWGxRc4AUkEQkyJfWBokQwrA5m1DMNLeki+gld/Yf5Vwv8H0wziGLj/ClT/VK0cZjEQP5paqQUOAn4ste4MCuyfZtzEyxVkK9ZcjGpUilnqlpKkCOZX9qT3R0/T/NLlhSjO1CzLatSZzPLxEWSW8JR5DxaL2tb5Sv2sVV++uF1YGFXUYkJYLHYoOkyesdkrtyy0ONWUgy/lTBOKqnzJZqh0x8IBc4OZg5hz4C9nazR+jFs5fFzuRnFPfY2nIm5BSH/JVDpgOkvm7//U7gSX5etI5zKw340fbkK/3wnmu5dgyWw63KW5FPQOIR+k3z2uFWwZ82DK6zN8POXRAqpg7Fjdi9F0+TwouYZ+KigY8sKDx+XeLQ2nvOlCV5ayPJ3Qgfep6zWbg3z3X/fgvAbfcB6UYrZhbL+ZH4Rds9Nd6LTb3cVmwXv3S37O/fmncKz4uf1TOLf9jKegyg7p95TUbi91Wp2FhdbSYne+uzi/1J4tu9wK/amyw7kPfTa1hRlvUs6/0w2TnXzzvioztgSPWLp6lmgud9vzC/PR0jxb6kSMzS2xmC13F2AZovk47izOdZY67WiBzUE37i4vz7EudFpRJJZFd3FuDtidPcDvZWGzXPNOMX/E+sUKv0zc9dODvr1bnL9ZDPu8lKJQ0hnP7pbH2WMeqpB50+tuTaRb64dvthc3d1a7nfWD/Zcb82tb79Y2D892jg4OD7f33709enW2sLNxuvX21dbi69cnWy9fra6tHL8oU9yk6k2KXnu6yNFOq71cb3fqc62TTqc3t9CbXz6blQV79Lu5Nl0aZ1W6am2ke/vru/RunaNbq513cytv3p4e7b/qrL7YPNw5PDh5s7O9vz13craxuro+t3uyc3J6eLKzcfB2a391ozvfKVbKi9x3oWrC/K2Xx92VtyuvN9fPVo62j9ZPzxZOu2ubbxbfvpvvvjle3ejsn+6urW2trb/Z3+hu7+2825s7OJ7Uix5tNVr41+5ijSj+ajQBPzBIsD74vHIi7uNsd1v2QEfjfIfVDex12WTNrPo63tNZHayTfBzZAz809iqc/2avGGc+s/A1a26WI4kuV73A9kqc7xWKgln0s2iNoin57Faj1WiHLWuSMHszGUVSa66lCM1T8uLk5ICsHGxjx0Uwz8rGyXGuVym1Qbax/90H5/Oeq4V6AM6F0WFmao3IeNk4v7dE3sfFHfy4JwfMSewBG8KNdlkC5VR2DZb1gVQ6LyQ09+V1aHOFFu+kb1c3VoLGblBQxEJqwYH2RS8oc7lSpUJrxgL2EqULllfsiKwUfSAR+CGARvG5tdMzD6zBU4sjSl4BGTKlwLsaEcBBe8uU/A37Up/4APuTrrgHwCgkeRQGjcY9SG+Iy6LQqqxUphoJ3TN0UZHPSMQUGlvDTq/zFlhC4BpJnOtxt382mdm4x6x/OhPOqw69eFqGp4BrUFiY3VSNK9RucmOhro2AZ/8o9rzX73UprrgjY6H0giDXkhH++mi3RhiJrBk6sEGC0VA2ZcdYH6/vuC9iLQx3TW+Mck0nrhwibYgFpFNYjRs8DHyS/gbXvzGZRbYhoDUyhHBlkCSgBT4KQDGNgonUzgMTOClhV1L3iZAWuA8+5EwpF+wMbu1nUgDJIyYCRwZmGCARidTSebCkpHigY4kNigi3CE8txDmZg/3rY0ufkFVl+hMMhsPhtPHjkfVImX6T1TUM6y7TdaxCA6gX9eNZuLhwBsOE8au+NZkWxOi70ZBzx/KB9MB9ZpkiMsGYh1D8cg9JRxL20VhSlA4SZUn6rEE2Dd5K5R0X/JlFJsMLj6AiAljIG1PDCIiYgxrhA+BXBEdX7Q/XKFsI7QSAvvSDLGpwkzQLHMrP0tRmpEzUTJjUzfWN043d/YPtva1GIp4Fd61CbCyg4yPoS41XMk8cGRrr8SJN+rDF1v2gB6YBGZQAPjD5PVDQD8OS7BnxLYmACMPDBVHAqEeePx8CEYZo4/He2FgHxGZaoxIlUOiyPA0xgowRTGG4VLPEmEvPn+cJAMK1KFPqJiwd5l5eMyVFMPDyXm0DpL4F4oeGOMC7ZI/BozlYXSQVAdxkqSrwSTANyyQ11jPtA8EiE2BUkkVSYcThrAq9GlPUx+hKmGZ9cEQiuYYaL8QtiLowQz2ml4mnTTWpl0lIeiizmIlJDVOeiYnGww95OoQnSpFKZOHtnCOMvKdrLA3lAJd7T8fYIUVwzwk2cfvxMdhryaGyGZs6FOKguolDKZPheh0vgBgPp/ribqtUu0roTQw9VvQJpzd701s7SJgMT0Ep86/qs1GNKslBO6jIWkkZHwDpNFrY4RfI3ViGDXz+pJ4/mUgs0gkLT/NDfr6oa+5ur23sHW/glMbAJyocxFLjfMJ0RWTZXCGM5O2VJ45U3keY2kHcTu7H/ibvZRSHKg+ffDNVTIYua4D3tjhInNPiIEFrtFd5D2N8lrio0YFxHkfe3mIqfG3VaIQ/5zeheMIQ0rFIPXQXWoX1//+KxExIruCm+tJH0XWj4bDzGOP+Mm9CfAaF8h2QbwThb/TWw2dAKt8H+UaQ/qAXHD6j8L33MaY1/6Kif+hrDJ/VvHj5YqLvBX6xEqF+ZPZ5elTcFjwjj3l7bKZy5X21vqkqVyo9zqSh2z8AhjGFyuaPVziHtMqfe29joJXjzs/Wxgkdjf4HxQwAJw==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Ledger's Payments"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/ledgers/{sequence}/payments"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint returns all payment-related operations in a specific ledger. Operation types that can be returned by this endpoint include: create_account, payment, path_payment, and account_merge.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./retrieve-a-ledgers-payments.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retrieve-a-ledgers-payments.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retrieve-a-ledgers-payments.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments.mdx b/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments.mdx
new file mode 100644
index 000000000..57b9ce849
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments.mdx
@@ -0,0 +1,4 @@
+---
+title: "Retrieve a Ledger's Payments"
+openapi: "openapi/horizon/bundled.yml GET /ledgers/{sequence}/payments"
+---
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions.ParamsDetails.json b/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions.ParamsDetails.json
deleted file mode 100644
index 70252112e..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"sequence","in":"path","required":true,"description":"The sequence number of a specific ledger.","schema":{"type":"integer","example":0}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions.RequestSchema.json b/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions.StatusCodes.json b/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions.StatusCodes.json
deleted file mode 100644
index 0dc3727ea..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"memo":{"type":"string"},"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"account":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"ledger":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","account","ledger","operations","effects","precedes","succeeds","transaction"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"successful":{"type":"boolean"},"hash":{"type":"string"},"ledger":{"type":"integer","format":"int32"},"created_at":{"type":"string"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"account_muxed":{"type":"string"},"account_muxed_id":{"type":"string"},"source_account_sequence":{"type":"string"},"fee_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed_id":{"type":"string"},"fee_charged":{"type":"string"},"max_fee":{"type":"string"},"operation_count":{"type":"integer","format":"int32"},"envelope_xdr":{"type":"string"},"result_xdr":{"type":"string"},"result_meta_xdr":{"type":"string"},"fee_meta_xdr":{"type":"string"},"memo_type":{"type":"string"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"},"preconditions":{"type":"object","properties":{"timebounds":{"type":"object","properties":{"min_time":{"type":"string"},"max_time":{"type":"string"}},"title":"TransactionPreconditionsTimebounds"},"ledgerbounds":{"type":"object","properties":{"min_ledger":{"type":"string"},"max_ledger":{"type":"string"}},"title":"TransactionPreconditionsLedgerbounds"},"min_account_sequence":{"type":"string"},"min_account_sequence_age":{"type":"string"},"min_account_sequence_ledger_gap":{"type":"integer","format":"uint32"},"extra_signers":{"type":"array","items":{"type":"string"}}},"title":"TransactionPreconditions"},"fee_bump_transaction":{"type":"object","properties":{"hash":{"type":"string","title":"hash"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"}},"title":"FeeBumpTransaction"},"inner_transaction":{"type":"object","properties":{"hash":{"type":"string","title":"hash"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"},"max_fee":{"type":"string"}},"title":"InnerTransaction"}},"required":["id","paging_token","successful","hash","ledger","created_at","source_account","source_account_sequence","fee_account","fee_charged","max_fee","operation_count","envelope_xdr","result_xdr","result_meta_xdr","memo_type","signatures"]}}}}},"title":"Transaction"}]},"examples":{"RetrieveALedgersTransactions":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/ledgers/27147222/transactions?cursor=&limit=2&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/ledgers/27147222/transactions?cursor=116596430667259904&limit=2&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/ledgers/27147222/transactions?cursor=116596430667255808&limit=2&order=desc"}},"_embedded":{"records":[{"memo":"FadBcV0owHrsLQif/V2TxZKGA2YiX+MoifI7oB/UjJM=","_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/3a644389bbec63dd2b107a03c16711563fc549daa7b7f56f951a2e470f81f2e0"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GBKTEASNXABG2NC4TY6N3IA5UFC6YW53Y4KTIKY3CUEKQ2W5EIYRMYVB"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/27147222"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/3a644389bbec63dd2b107a03c16711563fc549daa7b7f56f951a2e470f81f2e0/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/3a644389bbec63dd2b107a03c16711563fc549daa7b7f56f951a2e470f81f2e0/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=116596430667255808"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=116596430667255808"}},"id":"3a644389bbec63dd2b107a03c16711563fc549daa7b7f56f951a2e470f81f2e0","paging_token":"116596430667255808","successful":true,"hash":"3a644389bbec63dd2b107a03c16711563fc549daa7b7f56f951a2e470f81f2e0","ledger":27147222,"created_at":"2019-12-06T23:05:38Z","source_account":"GBKTEASNXABG2NC4TY6N3IA5UFC6YW53Y4KTIKY3CUEKQ2W5EIYRMYVB","source_account_sequence":"113943107245989112","fee_charged":100,"max_fee":100,"operation_count":1,"envelope_xdr":"AAAAAFUyAk24Am00XJ483aAdoUXsW7vHFTQrGxUIqGrdIjEWAAAAZAGUzqcAAFz4AAAAAQAAAAAAAAAAAAAAAAAAAAAAAAADFadBcV0owHrsLQif/V2TxZKGA2YiX+MoifI7oB/UjJMAAAABAAAAAQAAAADhZHiqD/Q3uSTgjYEWGVRfCCHYvFmeqJU12G9SkzJYEQAAAAEAAAAAB77j4CQxLlm5aPrq/PDwFhGNs2ldqbdCZwkSfzXhUhYAAAABTk9ETAAAAAB1jYLXrFzNBOWCoPnZSHI3PJAhHtc1TrCaiPuZwSf5pgAAAAAAAABNAAAAAAAAAALw9Tl2AAAAQLSLnL3XT3F6dq5m2WHZ7tH3HBrK/e+p2G7Hrl3WXQToUsgxKIRH6bhHT/mIWwnrfLZ9nlVjMCFoZPqVKrI2lgLdIjEWAAAAQCrZ9IbjDAB408VgQaqNpwX8hXr/OUsoEexkWGkN9PjcBG2nf4bKWdbjiaqHZ+LrvM+DdmhxtA3L9bzmCie8NgA=","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAABAAAAAAAAAAA=","result_meta_xdr":"AAAAAQAAAAIAAAADAZ471gAAAAAAAAAAVTICTbgCbTRcnjzdoB2hRexbu8cVNCsbFQioat0iMRYAAAAAB5tToAGUzqcAAFz3AAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAZ471gAAAAAAAAAAVTICTbgCbTRcnjzdoB2hRexbu8cVNCsbFQioat0iMRYAAAAAB5tToAGUzqcAAFz4AAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAABAAAAAMBnju+AAAAAQAAAAAHvuPgJDEuWblo+ur88PAWEY2zaV2pt0JnCRJ/NeFSFgAAAAFOT0RMAAAAAHWNgtesXM0E5YKg+dlIcjc8kCEe1zVOsJqI+5nBJ/mmAAAAAAAIP38ASptjhEiAAAAAAAEAAAAAAAAAAAAAAAEBnjvWAAAAAQAAAAAHvuPgJDEuWblo+ur88PAWEY2zaV2pt0JnCRJ/NeFSFgAAAAFOT0RMAAAAAHWNgtesXM0E5YKg+dlIcjc8kCEe1zVOsJqI+5nBJ/mmAAAAAAAIP8wASptjhEiAAAAAAAEAAAAAAAAAAAAAAAMBnjvVAAAAAQAAAADhZHiqD/Q3uSTgjYEWGVRfCCHYvFmeqJU12G9SkzJYEQAAAAFOT0RMAAAAAHWNgtesXM0E5YKg+dlIcjc8kCEe1zVOsJqI+5nBJ/mmAAAALEhqMpZ//////////wAAAAEAAAAAAAAAAAAAAAEBnjvWAAAAAQAAAADhZHiqD/Q3uSTgjYEWGVRfCCHYvFmeqJU12G9SkzJYEQAAAAFOT0RMAAAAAHWNgtesXM0E5YKg+dlIcjc8kCEe1zVOsJqI+5nBJ/mmAAAALEhqMkl//////////wAAAAEAAAAAAAAAAA==","fee_meta_xdr":"AAAAAgAAAAMBnjvKAAAAAAAAAABVMgJNuAJtNFyePN2gHaFF7Fu7xxU0KxsVCKhq3SIxFgAAAAAHm1QEAZTOpwAAXPcAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBnjvWAAAAAAAAAABVMgJNuAJtNFyePN2gHaFF7Fu7xxU0KxsVCKhq3SIxFgAAAAAHm1OgAZTOpwAAXPcAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"hash","signatures":["tIucvddPcXp2rmbZYdnu0fccGsr976nYbseuXdZdBOhSyDEohEfpuEdP+YhbCet8tn2eVWMwIWhk+pUqsjaWAg==","Ktn0huMMAHjTxWBBqo2nBfyFev85SygR7GRYaQ30+NwEbad/hspZ1uOJqodn4uu8z4N2aHG0Dcv1vOYKJ7w2AA=="]},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/83eabfa824b57436eda49bb9ac28675285f6d945325f69db41792078a83d3479"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GDUHYA43LEQWXLJ5GQGNDJHZY6TZN2OK3KA4YQXQ47BRMRDRIUUC4IU5"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/27147222"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/83eabfa824b57436eda49bb9ac28675285f6d945325f69db41792078a83d3479/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/83eabfa824b57436eda49bb9ac28675285f6d945325f69db41792078a83d3479/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=116596430667259904"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=116596430667259904"}},"id":"83eabfa824b57436eda49bb9ac28675285f6d945325f69db41792078a83d3479","paging_token":"116596430667259904","successful":true,"hash":"83eabfa824b57436eda49bb9ac28675285f6d945325f69db41792078a83d3479","ledger":27147222,"created_at":"2019-12-06T23:05:38Z","source_account":"GDUHYA43LEQWXLJ5GQGNDJHZY6TZN2OK3KA4YQXQ47BRMRDRIUUC4IU5","source_account_sequence":"113383696345604336","fee_charged":100,"max_fee":100,"operation_count":1,"envelope_xdr":"AAAAAOh8A5tZIWutPTQM0aT5x6eW6cragcxC8OfDFkRxRSguAAAAZAGS0d8AACDwAAAAAQAAAAAAAAAAAAAAAF3q3zYAAAAAAAAAAQAAAAEAAAAASe2g7z3OqB0F+vr+sM6vGMHgnomyJOLJeGMMjT1jgPcAAAADAAAAAVJNVAAAAAAAyGdd4j3sXGNb4PWMyeROuBvzRJJbU+On/O1oSxFvcqwAAAAAAAAAAAAAABcAB2UNAJiWgAAAAAAAAAAAAAAAAAAAAAJxRSguAAAAQG/ksOk2naI/PrA/6qes3c0IhoOpnBghd038S62rayiophPSs3HyUbgbOEpYQCkJezrf1bP+s2fFXVCEXbgveQk9Y4D3AAAAQAINPdxGV1VIeQ1OUDDlqtrSy8FrWQ/+CtRxqVHcHg98SYh5co/gd83R4IGDxukCByTbYapkrUOD0XDJKC/hcg4=","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAADAAAAAAAAAAAAAAACAAAAAA==","result_meta_xdr":"AAAAAQAAAAIAAAADAZ471gAAAAAAAAAA6HwDm1kha609NAzRpPnHp5bpytqBzELw58MWRHFFKC4AAAAAAKovMAGS0d8AACDvAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAZ471gAAAAAAAAAA6HwDm1kha609NAzRpPnHp5bpytqBzELw58MWRHFFKC4AAAAAAKovMAGS0d8AACDwAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAAAA==","fee_meta_xdr":"AAAAAgAAAAMBnjukAAAAAAAAAADofAObWSFrrT00DNGk+cenlunK2oHMQvDnwxZEcUUoLgAAAAAAqi+UAZLR3wAAIO8AAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBnjvWAAAAAAAAAADofAObWSFrrT00DNGk+cenlunK2oHMQvDnwxZEcUUoLgAAAAAAqi8wAZLR3wAAIO8AAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"none","signatures":["b+Sw6Tadoj8+sD/qp6zdzQiGg6mcGCF3TfxLratrKKimE9KzcfJRuBs4SlhAKQl7Ot/Vs/6zZ8VdUIRduC95CQ==","Ag093EZXVUh5DU5QMOWq2tLLwWtZD/4K1HGpUdweD3xJiHlyj+B3zdHggYPG6QIHJNthqmStQ4PRcMkoL+FyDg=="]}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions.api.mdx b/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions.api.mdx
deleted file mode 100644
index 7976412af..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: retrieve-a-ledgers-transactions
-title: "Retrieve a Ledger's Transactions"
-description: "This endpoint represents successful transactions in a given ledger."
-sidebar_label: "Retrieve a Ledger's Transactions"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlW+ty4rqyfhWVf+x1CQlgc03V1D7cr+FOCMxKZcm2sB1syUgykEyl6rzGeb3zJKckczEJySQzs9eafTZ/SLCk/rrV3epuq78oHFpMufystJFpIcqU25hiImZQx+cOwcqlMrIdBhA2feJgDijyKWIIcwZYYBiIsXngAk4hZtAQMxhwMIDAclYIA1cueqHEFOIjCsXzhqlcKgPEqYNWqLClOorMV2KKDyn0EBdwLj9/UTD0kHKpMLQMEDaQElMcAcyH3FZiCkXLwKHIVC45DdBL9AjsJgIceDqigMwBBMxHhjN3jAhGZtjIg8rlF4U/+IKigzmyEFViCtpAz3eRcpl4eortERkBZYTu8CwDRB+OAM2hy14gKuxgcBtyIKXKACdHkIghZRWK0iCui6RsBHKKmE8wQwxAbAKHAT9wXWSCOSUe4DYCPrQcbN1xskAYrKAboJBhigxCzffymckkMplkNpXN5dP5ZCIdZZtQE32caxMxx8Jwx4eAKhcSTK5tx7C3CBlgNglcE0DfR5BegK6/0yvDDUwE/oTM+BP8CpmBsOlg6zdAKPhTkPsT/Cq+tj9fgIYg4zAAqRV4CHPgMPy///0/HDDEY8DhwERzGLih/OWyJ8XDOHWwJaSDA0/YCmSGEjKo3EYF4zqewz8oGKGgHtw4XuBF9HMnCop4QDEyL4AYJ9cHBsSAQmyhcM+TAryaSIBzADEIfB/R7UCpYA4DNqSmQUxkClHXCXUeCQZzQoGP6JxQDwrboAgygtkbQtttIDJfyC6ZeK9eJY8MaLuld3PouMj8oOSGiAvawurF9049wrXA3uFIh0QRE1hfKpOcLSxJkjjJhU6IiyA+7L/0M3L87dPTrcC5NUkxSU0kxNczqKGrVGKKQTBHmIsh0PddJzT0+D0T475EiEPX7c6l+9vCIPo9MoR2+VTwxp2Q3p3r4AWLwH1lHEPu/OujbIrmpzRfqgmXKo4XylNM4cjzXaELJwT19BTdu8/horcxhTvcRZE1MNrwnwyST9Hqp4L0JIbtfmrLrRb28xWdQJ6OTPOI7CtDt44mMhBSCoX1ORx579ArD3nkpSyeYv/OigkNgwT4Z9PNMFD5yUAd3OxPBgzN58jgPxsqnyIDmehngyVDeWT+bLAiacVPhezZIOnBDl5jb6lH1nHQyIgWRCR/zO3tU0xxzFPs7JA4ptSnSLB/0gsfkrRT3MYUGzL75MQX3uYQzO0l6mCuqWKwQZEQ6B3kp0GQgBro7qVb3XPlQ84RFaFS7XPhfJY4z99+SaefIvxC06QihDq45zsv2KATMno+4u6UIF+gutunl6fGztGPgx9Z6zUWvnfF11gWAw0bUusVuXlwczdHp0Ww1+W752J4SzMQXiGX+OhuY9KTy4aR+dcee4jDV8cIrt4cIGKUu/DXU3ogs5qAovdEQV/doEi4Fll46/oJNp13Hpbc8ZBOAvwep+w5+E6Mf3VPX3kYwRqpwPSiQEcHGHun8BFYL9zIMbBXH78DWjsKRqzn4PcZ86mBd9D6wOAQ9p0F/bfNIDjYwYZTeCc0Qla13qtnT+8RxM4G9MDz7z52Zp70/geK8vlfZSKRn6sIFQPPjzAsJjkYI/pvzOBb/jUypSHYPGL9WbzhmMqzk//onN8e6pEwJHI8vziMXz8Hj0+948PjwMrLg+GZ0z9y8S8detQ7H+3D7dPTa9qvPN0+7WtKcmfeLChfflFkHfS4XLLLO8O4UbE599llPG6H9bFzjhjHiF8wjlwX0gtCrXgoUBZXs8lUVlXVeLTu/c+wGvzpH7L49kn9h6xufhK1wkit40dTSyYz6XwmpSUymayazucTqdP0d4WNfy39dC6Re0ZfVknFPh4VJfZlh8+7CoJShWbRuE6QdZ2ydt+Zx6/V0WbWqhXUqXNzdkWceSNLivHxffPqkxL7vo2MchLXYCaV0nJ5XUdGRjNNVU8msjChGclMNplMZ7S5kU7lTQizenaezszz6SRUUSqbmOeScxUlnlUMPgBjO4vFa8XWqFIYdm4KxZraKaVG00xHaxTS42opM52ktWmqNWq0plppXGn11Um60pgOrqbXxeNA/Tv29mUq/3dJM36A8WWrZDGpUTGpTzICPiRwohR7nOz/bbi3GN4POloL+EbU/9zb+D9etcfn+f33kRLm/Batbd6qfLdRPc9tlRPUjtPb8PVfeOL/CPo7w9rZyHGaq6iJZP48qZ4nMiNVu0ykL7Xc7OXxeql8s22/kaEqyaSWT2nJRFZNpfO5fDKpPjugL5OJRCTekP+9yOCSz/MzpSA+1fFDYaGmCl4icdNM5TRYMMn4hk2yq3p11Ke1zbixrFGzcV+ZiOGzQm38uDQKhepjSs7vF177lD/g5MX44mG9sj2rO8tyvK8Fw5F1P61MateDealUn66qHlo2x0m1lh8uHpvTihxfkVOL2ex9qtTftF0vDXt0Ge+V11W71mGqay51szRbL4bzxxt7bE/l8NEiXxmFM5P30/YNrT52it1JifTwbFhvaL1mwa5zIzmiJej0gtl6OE/71o69YufAanudH7mqhN8etnFbuxlp1Yy5THvqpD7L8rpWL9JWHJ35ai1bp642uemPyJhZm1ZjUM/odn0U9xqTNabz9iyP3ev7q1KVzHrL6xZtqK7V3su/X6KzfEO/LxeKqUTu2urDZcdf3+TsGxrvjhmpoM1iUlt08r17o1hT8Tyltyamfu/AZX121qarq7Oy6dkbXtDaef3RKzko17EKn44jt61uiE8tssGHP4uRff50ItDbLiAnNOSOFmapbNI6zLoeNUoj3Srpo4GB7x9NUlTtAdroQc647pSYXu07BPKEczWYhhTTfEQOyqed1rnKa8pY/MH0Ux+mv5faVRHfB2cRgdZXQc9qlivBRHfJWUBzuV5hUpmqj/Ba9XmiiUuDZryDqsOqxF/tjhKDq3DmpGNxxG6uEpX0tGWdmW7DuDdyi1IFJR+vu6y5bJylcbEZ97wtjkZPyxWGPr+3K84rmCtFfL+a/G34cuuv4BPyW10f8H3UWXw7vnbFXl75s/j+s36P/P5ifAv3DXyfPinPS2ihpVp7ybYiSnt9ZTU7QaHJO9UH1OuoVh1Wq9lqkN1sxonWhl2XWvZSGzY24c4X6l6yXynMRl1/XSjc9IzTtvDqkRGR3DfT71rfRl9KJlI73OXV0WLBZ4U3AmNlmj3jxlepp8+mJg4Sc8OoMZrPZvBUZyi4MWdmsWsPH8oVYlfmflAxe2dTWy8hnuNYRdeTq3VjYi/O/PGS3cNJwZK0Wxwn7ODqqlC/H20mxeKSqLg4f6iiVS49fLAG2dpgCvta4qyzrujQjNvMnyWDbnNJTJwKgtxjqqPCei1RNlbJVXfaambXqmTrVrxD/nEZVE5DUJ/DnJrS09mUlkEmTOV1PQ8NNZfJptVcep4x86m0pqbnmbypp5LZvJrI5mBOM7VUNv8jMqjyuD4tpLR2pT+5aTfTtX6tU27WZ9PMaNZRuy2tVUhN+zf9VLY4uBqUB43xuJRqjNM/YQb1vdL8uzKo78b9M2ZQoqLyV2VQIa1dBvXdRvWVDEpSeyOD+gH0f1QG9a22/ZUMSstpmXxGS6UziZSmZX5gBtW1c4U0nzUmAe+N+lcJOEpvMmiSMSi0jE0p152Xq4vBZjC0gkKYQQ0TZq5QKJXXJ4+jqrbUHqfPjqvwEB8i1co+at1lMVE9W9EzdpVZ1a7qFibeQ7PbbqLa1dX9KHlvhUdfWU66bnaut0s91Ewzda+xm1pHT/UmVw9o0A2Kq8dBs6mPz7o43k2S4aa6MpbrY0xFo1BUx51C05lYhVOf5p6/fi2+YN2FimEj3qOFeGaJmGYkGjbp+rho2WZCyw0zKoUPDvHt3pBp9Yexbundij/tlxZN9EjnSb13xtR59ea6VLnRrRXqL/LTVFkLxdHo9MxN7Tp53UD9ZHdcLrtLTocPuSqd9ONnJT7YLK/rRt3K54ZTO22QuGXmtEGqUStvgkWp+DDSp9Bf0HG3nLgpN1uluG1YqY9mQOVnAihFwoiPZ0OZ+rrsJRc2zCTyncLjwO/hup/W/Qe+LD5W2ut07moyqFerrdI28WiR1dVBkVYn9+QD2dB30l+fJvN2NvSeaDRYHCaVybzQ1SfDKqWjRKLcqS3ODITdALdUUr/qr8p4vZlVjPGYtLecLZ2zcWHWHmjrQqHRzZ3G8u5o9Fvo59bfRv9FNIoJRi+iUf1suM6MoEnuc2esHF/6mUfzse/UrIxn1EpVbTTftCnktNVyvEq+9WjMm4OgyFJD1y60+m62y+PXLJ55nOWuzXFjYAalfLrUl7QLViKvVWY312M7XR6n+1fdyVLl7fZ6wmfleKqVrNf8sblGZW3TdOruw/1ZUXs065Y17dUy/Ua92eH20hvyfqo3MK4WpH1WfShbMhoN3/XI1z0e4jYR55+FePiKTRxG+3Dry86FPx2drUIOiK52HQMBdd93QCunrmOPwnGgg/ia0IW8cHl6xXkgBP+eNau7kQDvVr0VbzTn4eXJ7Tuu7eVsJaYIVsLZiYvERVIe1J4H6cNhFPApWTmm7AQA9dGoBwq9hrgJbUIOxaVnccV+GOLaUb0ADQ4cbCHGwwYCis6l4JgcLWf6lJiBgUygP5xaImxKEK+49xfMEWSOaGggwCCYBR7aTYUrRKGFQOSqM6DIhdxZyTvbsl/hcAn9nFAHYY7MEMi+12R7jztgIagdoBKhSFyMd5jkPMKHTh3TQkBHfI0QFuRDbo9n9igRL40ZcJ0FAmvouoizGDCRgTCn0HUekQnQxrDFZXsWkytAxpDgmQWISkT7C/WcABbo8t59RDFjQN5mF1u0DUKADl3BbEy0LTBOEfQAWsmOGonjqJdG9IXsZ1680Kz/dE34HN3Q21935mmiMCSj7CgY38KOG4Sic0xM9Nt/lPb8gf/AO3Kih0RH4hFiQpYrBwJjPGjHAAQ6JWuGqKRAMNo16+xlPSy32FdlbRKDxTkhLoszc8GEpAmgSKiTXM0g4t39xuEPYv0HElChbUKgMbBGsv/F8xA2xSMpKIgFYeBgxhE0xSQPLhxsAdOhyOByDw3oukzyKbfVChwTgdBidMSATdZSJKbnYIdxRMFOxaU67mQjSMiWmF8pmofKLPkv7zn9BRRdYh1ksF6vj5nfjzzXXWLF4TlG63MW4HNxCtnofHt+/Ca7cBgRZgKNhUXFXSZA8HNrCHWHGrbDkcEDCl3geMLmkSd3nmxbdjx4TyjYHh1AXAf67QJUiWixCq8kiZ+hTgLRvSMhCgFu6e1Vg5hIhwzFgGEjYwHE6Cj/sieoJkR7EIDlcDvQLwzixbdy2H3vWI3rLtHjHnRwvFy5rrS7vUanduGZv8ntKqI5oUhsvI4sB4v+ol8YWBPKRVeYw2XWhS2JQ7gBR4JAhk3CpiaJT5gl6BDzWxwBMIkhu52kjC7B77+vETAJwISL3kdCGQI0wFiA2AlKbFnohiAQGmNCV5hL1Evsden330MHgGSPH3TdB7m0nHu3gq5jSgbvXpxtSKg+RYCvCWBINEZyYTzYQBRvnYqJDBL47lY+nnDDjucTyiHmUsF0IsXoOlB3XGFxYlZEvS6OVF9YlwcxtBADjlCuNY4BH1JknptkjffqRebHrBKfO550eoLmdqZwasLlkTnAonwCfl2jX1wXRCxLtJoxAMEfSgn68jgQy/2h7GUnVESWf6jHuvMhoitHZvC7TT6qt4hB52QujzJHXmISHVfQkIXFbdfZDnZUoavC9OTmK7Fnwd5xaIc86MinyHXJf0WfiUqiYyDMUIRWwYeGjYB6Id4oO6bQ3bmD6P7JefjkQHHrTqB8GlYaw0VZvN0oVTrDiphyYXPPlbUinzDuQRwhubsLBSAIb0P9wsCzBtujKOLLoSntBzX7bhMUjjY87rvQkbf3JItftgH9521tSIC5jNw4O4rpb2OKTRgXo798ES5pTN2nJ/Fz2CEoIn3TYVB3X+sRjLL29/fdnhTLAj1EO4m3F9UUmXR8hLl/m/baN6Swayz+RiH8P2qlfUNIuybjbxTSv6hr9g3AL5p8D8hvxT/UEdA/aM2/DrYXYn8DH2nxPwlzd90XP0TB7eDvvZO8dGojKHRUgA0fFwwD+dH9eNHWK7jcVzVqlZHy9PR/CqoRDg==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Ledger's Transactions"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/ledgers/{sequence}/transactions"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents successful transactions in a given ledger.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./retrieve-a-ledgers-transactions.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retrieve-a-ledgers-transactions.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retrieve-a-ledgers-transactions.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions.mdx b/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions.mdx
new file mode 100644
index 000000000..924d7c71c
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions.mdx
@@ -0,0 +1,4 @@
+---
+title: "Retrieve a Ledger's Transactions"
+openapi: "openapi/horizon/bundled.yml GET /ledgers/{sequence}/transactions"
+---
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool.ParamsDetails.json b/docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool.ParamsDetails.json
deleted file mode 100644
index 6b0280633..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"liquidity_pool_id","in":"path","required":true,"description":"A unique identifier for this liquidity pool."}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool.RequestSchema.json b/docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool.StatusCodes.json b/docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool.StatusCodes.json
deleted file mode 100644
index c94c4f1f8..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transactions":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","operations","transactions"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"fee_bp":{"type":"integer","format":"uint32"},"type":{"type":"string"},"total_trustlines":{"type":"string"},"total_shares":{"type":"string"},"reserves":{"type":"object","properties":{"asset":{"type":"string"},"amount":{"type":"string"}}},"last_modified_ledger":{"type":"string"},"last_modified_time":{"type":"string"}},"required":["id","paging_token","fee_bp","type","total_trustlines","total_shares","reserves","last_modified_ledger","last_modified_time"],"title":"LiquidityPool"},"examples":{"RetrieveALiquidityPool":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9"},"effects":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9/effects{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9/operations{?cursor,limit,order}","templated":true},"transactions":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9/transactions{?cursor,limit,order}","templated":true}},"id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9","paging_token":"113725249324879873","fee_bp":30,"type":"constant_product","total_trustlines":"300","total_shares":"5000","reserves":[{"amount":"1000.0000005","asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"},{"amount":"2000.0000000","asset":"PHP:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"}]}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool.api.mdx b/docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool.api.mdx
deleted file mode 100644
index d54ce0660..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: retrieve-a-liquidity-pool
-title: "Retrieve a Liquidity Pool"
-description: "The single liquidity pool endpoint provides information on a liquidity pool."
-sidebar_label: "Retrieve a Liquidity Pool"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlWG1v2zgS/isDfukL5Ne8Nf6ylzZpmttskm3SBbppYFDiyGJDkSpJ2c0a/u+HoSRbdtxt7vZwPWD9xYY5nJdnhg+HM2eeTxwb3bJz+aWUQvoHuDJGOXYXMYEusbLw0mg2YjcZgpN6ohDUUrYwRgFqURipPRTWTKVAB1KnxuacdoLRwDd2dFnETIE2CJwJNmLv0VuJUzxaukFesIgV3PIcPVpycs40z5GN2FLdmNSNpWARk+RkwX3GImbxSyktCjbytsTNSI6g1PJLiSAFai9TiRZSY8Fn0j3ydHFH6lxhtEPHRnM27Pfpa13ldZkk6ByLWGK0R+1JhBeFkkkIsvfZkdycuSTDnNMv/1BQKCb+jImnSC1B4mVlZaykvnffl3Oo0u9LZRbbUs5bqScsYlWWAqD6ni0i5jEvFPeE3FI6NkYh12yxaAN7Wym9i5iXXmFbh+Xa8YTCfkIA/1PXlkX3/+XYhlDI6ZqzG6DeLSImxTbnGr1SkGcFn0g9GXtzj/rPpNfkFhFLEcdx0dohtccJ2nb0pdR+ZxjiDzKb2mnBeK7G3pbOK6nR/YmQy7j9hoBFh3aKT8gYdw79Vh08N6XetkTQK+78ODeCiECMFQqKdJuWdUEv821hb+QyUNMavkt4a+S24LSBSguDb3i71bdWma2z6iJi+JXnhapg+wb3juZsylWJ62zU8E11OljmfeFGvV5mrPzD6I5H5zX6rvOoFLddYye9dbJ2vf2D4X4/2U0Gr/oH8XB/mKav9gZxn++kONgdDA53D3f247g/HOzFw/TgYHf3IB2IdDA4PHyFPI4Pg/9piol3P9iTXu3G/KektM7YSMlc+shYgXbB1piB7qFHBPQjXV958nTvN5n9R/rf9uWpEdS0yf5yBW5SKxsMdg6Ge8Pdw53h7quDw1cHO6tzPtrpNyRJ3YHzXPtxYY0oA4c9Zkm20+9vcsCI7fXDvys6vJ0veY0N+v1+tx8+eyxqmJCdfHh/Mzo9uto7P7m5/G3/49nJ/vDj0S97+9c3x0cXV++PLw9+f3v8+vT64t0/fz37eHr68/Uvl78fvbu8vB5es0XUsjBcWei3LFy9u/oLBu4W1SdiOfrMUG4mGIid+rgRe1Q280edH+U5IFJ3iKVVTytJtq3Bvank4AL9zNj7AMF2jWnpS4tP0fm2kQTdaL2jdjU14fqoKfpdpZdFjEKpdve7/e6A4ivznNuHldSq0+Ya3t3cXMHR1Rl4A4J7DlKDzxCuK78aq1048yD1BJ2nbQIsdqpSCtJhZ1WVKCB+2KaCNHNqlXPwGfcgHSB31D57A1TaZY7NVj5FyycIrSYYLCru5RRJnGQKtKGf0Al2jJWoPYrKEYsFFbr2FUVB6SqnGofeGItduKGGnSJvxRFbKSYIMfoZoibzVbTrO6+soRaC2v17hBlXCr2LQGCC2luu5B8oAL8mGSfAoqAhlDxI50q0wSNosuENuDLOpYc2K0XwpUT7QCniSULHCGKuKNgIjAXnLfIccIq68aO9m5SudnYfVdbfvRJu2wm9e94cT4FTVHS3ubXrp3a7lxiLHW0EvvhbVc8n/Uk35hKuIUZaQkdYTiWH5MP78wg4xNbMHNpgwWgEkwZUllhfH//svou1MInr+UDXTtw7QtqARSqnoC0x1Hp+pSe2SeHBlJaqjQCNYIZgMTF5jlrQUgCKazIMUjuPXNCmnN9LPQEhLSY+5DDhSrkQZ0jrpJQCoToxMTrIzCxAInKppfNooSnxUI4NNjLczgnCc4tpVcwh/uNlpM/gtTKTFQaz2Ww9+KVkJ1Zm0uMdjbOOK3WHbqEMO/X98SJMHJyhY8KT+4k1pRY0K9k4DVXt2CSTHhNfWq5A5nTmMQ+ZDxmSDnL+2Viorw6Iy7x40YW3xq6NYnhsSg+1iwRgbW9ZGkZgzB1GkGSY3ANJt+Mnk3BK0K4AmEiflXE3MXmvxqH5bkLtxcrEvZxL3Ts++e3k/PLq7OK0m4sXIV2vMTUWKfExTqSOQPpnDmbG+gwsSh+6VD0JfhANyOAEJplB0fDbLR1LuDDiPyECECYp84ZgRvDy5QxBGNDG02TLWIdgS63JiQYoSllFQxyoYgRXdFzaLLGspZcvKwJAV2AiuVIPQXXYO55yJUUIcPzobkMqfYvgZwYc0iDM0+HRCVpdk4rAxJSFqvHJiYZlXhhLLWYosNgEGJXksVR04mhXq7y6a6VPpyvnmk9ohEfFNdMRFNyi6Agz08vyMul6qKbwMg+kRzbrnURqRHkmBY0oHDyf4TOloHWypAPugMMn9oYX4TogdZ/YEjsqkdDH29xdptdopzLBVjPWzmwQ6pg0XGUkVs3ieBLe/fXgsHG7XdBv6eiF5LNoo9lbb+0w5zKsolLmH+01Gg7IBLXDlq2jgicZwrBL/fJq1Lhc6VQrK4s1nfCwWr+aglLXOz97c3JxfUJbupnPVZgzFMb5nOuWyeYpDxzW57mb7cN8Naf8bw9265eOx6++Vyguw0QpBDmv2/rbjfktjTVGj0e6dxHLjPMkP58TLX2warGgv8PNyEa3dxGbcit5TB307ZwJ6ei3YKOUK7c5923H/Px9PaN5Af/WNPgb4dV/cv1A/Xs1NWEsYvf4sHVavaAJXoZcUDnczmu5oyTBwrc0PBog08Nh+VI6Pblhi8W/ABXxTws=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Liquidity Pool"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/liquidity_pools/{liquidity_pool_id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The single liquidity pool endpoint provides information on a liquidity pool.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./retrieve-a-liquidity-pool.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retrieve-a-liquidity-pool.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retrieve-a-liquidity-pool.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool.mdx b/docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool.mdx
new file mode 100644
index 000000000..b8f4d3ab2
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool.mdx
@@ -0,0 +1,4 @@
+---
+title: Retrieve a Liquidity Pool
+openapi: "openapi/horizon/bundled.yml GET /liquidity_pools/{liquidity_pool_id}"
+---
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-transaction.ParamsDetails.json b/docs/data/apis/horizon/api-reference/retrieve-a-transaction.ParamsDetails.json
deleted file mode 100644
index f16a7a18e..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-transaction.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"transaction_hash","in":"path","required":true,"description":"Transactions are commands that modify the ledger state and consist of one or more operations.","schema":{"type":"string","example":"5ebd5c0af4385500b53dd63b0ef5f6e8feef1a7e1c86989be3cdcce825f3c0cc"}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-transaction.RequestSchema.json b/docs/data/apis/horizon/api-reference/retrieve-a-transaction.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-transaction.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-transaction.StatusCodes.json b/docs/data/apis/horizon/api-reference/retrieve-a-transaction.StatusCodes.json
deleted file mode 100644
index 06c95a51c..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-transaction.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"account":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"ledger":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","account","ledger","operations","effects","precedes","succeeds"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"successful":{"type":"boolean"},"hash":{"type":"string"},"ledger":{"type":"integer","format":"int32"},"created_at":{"type":"string"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"account_muxed":{"type":"string"},"account_muxed_id":{"type":"string"},"source_account_sequence":{"type":"string"},"fee_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed_id":{"type":"string"},"fee_charged":{"type":"string"},"max_fee":{"type":"string"},"operation_count":{"type":"integer","format":"int32"},"envelope_xdr":{"type":"string"},"result_xdr":{"type":"string"},"result_meta_xdr":{"type":"string"},"fee_meta_xdr":{"type":"string"},"memo_type":{"type":"string"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"}},"title":"Transaction-2"},"examples":{"RetrieveATransaction":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/5ebd5c0af4385500b53dd63b0ef5f6e8feef1a7e1c86989be3cdcce825f3c0cc"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GDI5EK4HNMBHJJQGP3GUXQJIIOHU2CJO3LABPWD6WYSPJZP5NP67TMNN"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/27963785"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/5ebd5c0af4385500b53dd63b0ef5f6e8feef1a7e1c86989be3cdcce825f3c0cc/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/5ebd5c0af4385500b53dd63b0ef5f6e8feef1a7e1c86989be3cdcce825f3c0cc/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=120103542047408128"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=120103542047408128"}},"id":"5ebd5c0af4385500b53dd63b0ef5f6e8feef1a7e1c86989be3cdcce825f3c0cc","paging_token":"120103542047408128","successful":true,"hash":"5ebd5c0af4385500b53dd63b0ef5f6e8feef1a7e1c86989be3cdcce825f3c0cc","ledger":27963785,"created_at":"2020-01-28T10:03:33Z","source_account":"GDI5EK4HNMBHJJQGP3GUXQJIIOHU2CJO3LABPWD6WYSPJZP5NP67TMNN","source_account_sequence":"65046128646685383","fee_charged":100,"max_fee":100,"operation_count":1,"envelope_xdr":"AAAAANHSK4drAnSmBn7NS8EoQ49NCS7awBfYfrYk9OX9a/35AAAAZADnFxwAAALHAAAAAAAAAAAAAAABAAAAAQAAAADR0iuHawJ0pgZ+zUvBKEOPTQku2sAX2H62JPTl/Wv9+QAAAAEAAAAA+qpaPAsU/CGcSeS4KnvqE9y+Bcjhyr1l6jiwixRsvu8AAAABTkdOVAAAAAAs4YIuYne69wMuNtfiZ64gb7E3qnTR7A4yD4jZDSS8AQAAAdGpSiAAAAAAAAAAAAH9a/35AAAAQM5LSBiFRQKtFYRPpNabwVuvIhZSVRDaajf0KzYaqJmgaXAlFaTOYyYc11YuxUM1Fzl1VT4UEbI22BvO/8HzUgQ=","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAABAAAAAAAAAAA=","result_meta_xdr":"AAAAAQAAAAIAAAADAaqxiQAAAAAAAAAA0dIrh2sCdKYGfs1LwShDj00JLtrAF9h+tiT05f1r/fkAAAAAAhWQlADnFxwAAALGAAAAAQAAAAEAAAAAhD8BLsZFQEF33rKS6YopQUT3b6iLBG4nspe68/DBNBYAAAAAAAAAAAEAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEBqrGJAAAAAAAAAADR0iuHawJ0pgZ+zUvBKEOPTQku2sAX2H62JPTl/Wv9+QAAAAACFZCUAOcXHAAAAscAAAABAAAAAQAAAACEPwEuxkVAQXfespLpiilBRPdvqIsEbieyl7rz8ME0FgAAAAAAAAAAAQAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAQAAAADAan62gAAAAEAAAAA+qpaPAsU/CGcSeS4KnvqE9y+Bcjhyr1l6jiwixRsvu8AAAABTkdOVAAAAAAs4YIuYne69wMuNtfiZ64gb7E3qnTR7A4yD4jZDSS8AQAAAAAAAAALf/////////8AAAABAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEBqrGJAAAAAQAAAAD6qlo8CxT8IZxJ5Lgqe+oT3L4FyOHKvWXqOLCLFGy+7wAAAAFOR05UAAAAACzhgi5id7r3Ay421+JnriBvsTeqdNHsDjIPiNkNJLwBAAAB0alKIAt//////////wAAAAEAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAwGp+6EAAAABAAAAANHSK4drAnSmBn7NS8EoQ49NCS7awBfYfrYk9OX9a/35AAAAAU5HTlQAAAAALOGCLmJ3uvcDLjbX4meuIG+xN6p00ewOMg+I2Q0kvAEAAAkQQwRXzX//////////AAAAAQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAaqxiQAAAAEAAAAA0dIrh2sCdKYGfs1LwShDj00JLtrAF9h+tiT05f1r/fkAAAABTkdOVAAAAAAs4YIuYne69wMuNtfiZ64gb7E3qnTR7A4yD4jZDSS8AQAABz6ZujfNf/////////8AAAABAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==","fee_meta_xdr":"AAAAAgAAAAMBqfuhAAAAAAAAAADR0iuHawJ0pgZ+zUvBKEOPTQku2sAX2H62JPTl/Wv9+QAAAAACFZD4AOcXHAAAAsYAAAABAAAAAQAAAACEPwEuxkVAQXfespLpiilBRPdvqIsEbieyl7rz8ME0FgAAAAAAAAAAAQAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQGqsYkAAAAAAAAAANHSK4drAnSmBn7NS8EoQ49NCS7awBfYfrYk9OX9a/35AAAAAAIVkJQA5xccAAACxgAAAAEAAAABAAAAAIQ/AS7GRUBBd96ykumKKUFE92+oiwRuJ7KXuvPwwTQWAAAAAAAAAAABAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=","memo_type":"none","signatures":["zktIGIVFAq0VhE+k1pvBW68iFlJVENpqN/QrNhqomaBpcCUVpM5jJhzXVi7FQzUXOXVVPhQRsjbYG87/wfNSBA=="]}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-transaction.api.mdx b/docs/data/apis/horizon/api-reference/retrieve-a-transaction.api.mdx
deleted file mode 100644
index c726021e4..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-transaction.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: retrieve-a-transaction
-title: "Retrieve a Transaction"
-description: "The single transaction endpoint provides information on a specific transaction."
-sidebar_label: "Retrieve a Transaction"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlWutz4riy/1dU/nB3ZwPBPENSNXWuSYBACIEAmTw2lRJ2GyvYkpFkDEnlf78lmYdJmJ3HnnN3qo4/JIBb3b9udbdaar0aEk+EcfJgDDmmAtuSMCqMx4zhgLA5CdV348QYeoAEoRMfkNwSIqBOyAiVKORsThwQiFCX8QDrt4wijEQINnGJnR53aGQMFgLXZC3HODGuQXICc7BSMIyMEWKOA5DAFcRXg+IAjBMjxenJw8IzMgZRIEMs1WcOs4hwcIwTySP4oElKT4Q5IJsFAaaOQNLDEgXMIe4SSQ+QD84EOBISS0CYOshmVBAhEXMRo4AYRwHjgDaaCKWXsD0IsHHyashlqNAKyQmdGBkDFjgIffVTGcZO2TaxWypWy2XTHJeLjlMpjk1wy24Fqi6Am8dHkLerlePq8RiKtmPbUC2U3aJt2rbx9vao9BQhowKEElYwTfVvV9dBZNsghJExbEYlUKlIcBj6xNaAc89C0b1+BM3Gz2BLNQNcqSdJIuXJJ3Qqvk0nwHe/TeVxcPcZKvEg48RQ0oy3jCEhCH0s1ZRuqMeM+YCp8faWnvGHhOljxpBEaluveWDbZlFigV8IVeJjvxiorUP/YsDAdcGWvxqqkIMNDvxqsIQKfnB+LVjviHSe2MbmJh52fHA77ylbp/R7fMsYxNmnwFo2cfQ84QmhkyfJpkA/Uq8tJoQb+fv0yxh6rdk38EMUEyoh0WNjQ0JlsaCIbQ7KhE9Y7gfBIm7D08d0tdEqxFICV/m9+WBl783s8eNrufyW0hc7Dld5f5v2noJoAXts9J7iaZ8hP6B6EjCLgNqwl9aFfx/8FK+vqfB3OX5NZUVoe5hPvmK3AC+eXNhvgo33Pr03w195BtA5+CyEp4XD97LlICJffut1ABJ/lUZp9ZcEAQTsKfl1nx+QCcUy4jvZDnOOl6oIkxCIH5mgt+0MpRi/pX5OVWvZxEZJEaXF7C0aT16NOfYj2C1X1gVJkuoMT8pQnORyHuPkhdGsBCEpyEMhwfcxP2R8kktVmSL39yu2nQrkB2CsRolc86xVrl+UzruXtfN2u9/sFZuj23671bo6HxVO21fFjlXrfTmrfLkb9Nr3vXK3VzkaXna7uwnqByQng0SucHRcKR5Vyx9Lg3/KmrktjNd/2REXjGd8EhCZYdwBriN/u1SpXcBu8fCP4V5h+H7Q6driJ1H/S7P/jIX9P4nUz/mCmTeL5VLBLB2VzGq+UH1fL/w9UWoT8leyVuv1398GvV/TjT3Sdpf1ZEeYLOT/DvnrwFrHyO7ybhTMgpk189lCdZg3T8ziSbF4b3xc442fju2/WJmNStksVfKFaqVUqVTLxWrReLeo5U0ztYzpbx8Wrvz7Zcmw1NM9H1yUHG7RQVCjR91Btc76pePu6eAIxzX3zuV30+Or22OcK5YV+b11RhuL2LKszrm1+9T03776c3Ztkugcx20znNwfvIzmtYv6VW/Yn0YFYd0WziuFdm/o577Mjw80fV0PPZiFuGeJUe60aQ9gULqg81n9eHlQs5+9Jc/7lWcSk8W1mEdVLW84da5uEtmidNeK7ihUjuPLqCtdcl8pTcZH9eKMDq+PrNLyrPR8fzYYVDU+pxkOSBr6+Ua//mW5M6iRxnX/QjburnthF4/jm2je8u4HN9dnGD+75sXLHZ61gwm+tfwGHl7dLe/sfP4uWowu840XP38zLI3q41ahUJtf5arnL6NJ/7Oxu+YbG9HN/hbG9mMtBS41drveG9sBLW1xC88WJMXLdFrcK4hT5+Ku6Yp8Jx54Z8+m2e5IbjWOvQNJhmbZzfOcO00GeF/6/nZym1v+yeR4Z9VaR9w3+vVGscgvBpU7FvZHw+K4Qjq1ZomKECrV3FmtW7tLYa/vukjf+o6nXpvxZnv7/UedyTpt3J+OrCv7VnuosK1d5zyt9+J6tJjeWP1bF0TYCQnxa9c9Zz5rifqYwNI/4i/Vy7rZmHwVe836nqe/+XNmYVopTKz/f2dPno6bWz/Vd/b4gflIVKnMfFY9XQyrrftFu9yZzOCADYudUmN5dX4x/3I7u+qcdhrN5cGRciWrcXVtlkfJzLx4E1ImzhEvWstSIX/QppzU5mIIM6d7Ls6eWz3SnXbbnVjhq5nYv2hZcoM8F2/s9332j5vhQSVF/4PJzhqVz4d+YqTOVfO0E7SL0dw+6zyPb0sBRK3mwaJbCU0T4qvLyUGr0Denc41v2u/H17cvt1voW/vVvwo39dS28ZzQ/2A8/7S/1F4q99Gz2/05f/n82Xi/M0kylfb8y9rMjbwt9c9E9llpG9l31j8X2c2ZuJtuv/+oZ1mtm2m7b5UXtkpPp4ttZkjkt/o5a3DUvB7Vas5xZTmNgouLUaN+XDhgJL6O2kcXt9G8F8fD/pevY/+mp6nZSm0TDcooGLt7wwfjZSpbzdZNw5qZN179YJoP57UvlSpp+O2bejecdXN93vVmLMC10D4d3YSX5ee293J7Q44a/ZfR7dXtzU3P61+L5/Fds3qUi93uoKY85fEteRQG6TFVSE5AJrtMVdXtluyv75sFqs4WwOfrnkLE/e+rdI19PZFhQoe6IGPG1SHZ1zi6kTLN9/BsrCkRXXN9VB0Ol+m99WpnfJ7wNTKGUiUZbR6ah3ld8QYB5sst1bY/gyk6Hw57yOq1kGTIwRIjQnW/Y5DgWks9RC2JCJ2AkEK3PzhkteGEptYjQ86cyAYHjZf7WCjOGKmDjqS5QgQCLAhwJVp1U6IA1kPxHDieAEq1JxAHH0syB0WuaELg+tSE2pBlnACV4CRAOIQcBFCZ7ApRJBJQa0CnjMMhGnpEaM1Teow5cSaAxiBjAKrEJ9rujuxxpo5OBfLJFFCMfR+kyCAHbKCSY5+8gINgYXtYGSyjOWAhQOksIuAaEVrPhmRIROOAyHRTTGTQLAK+VFO0qubRGPtK2YzqNQnJAQcI5kDXONKjFdPtyMMPnvXf7gkP6Ql9/H0dng4kmxsudna1K9g5m3HIUubAp/8q7/mT/knX4mxM0RjUKxDKlnOCkT267mQQRmPOYgFcS9AtUVdbZWPrwdmF+KatHWaLnGTMFznhTIWyNEMclDtpbjZTJ34LIpeK/5JFXHmbMmgGxYA4qA4uUEe90obCVAlGhAoJ2FGDAjwldIIcwsGWeg5t7PtC66mndRIRB1ASMWMQyGOxNokTEEqEBI7WLq7dcW0bJUKZGP3OwU2cWet/ttH0N1Tz2WRrgziOd5XfUGbHPpvkcJZCnBURzapVyIPsav34pIIHCabCBNvTCWcRdVSH/V00JL7DbY9IsGXEsY9IoGIeAj3zeoaIQAF+Zhytlg40joLw0yFqML7TwMdjFkm0gqgMuJK3cQ3mwBgLyCDbA3uKFHVafyUSNZVptwaYEOlF40ObBbmVHdb/16rmxj4b5wJMaO6sflPvXPVa3eZh4HzS01UDVzXdYxV0E0IziMjfBIoZlx7iQKQ+v6ATjUOlAaJBgO0xcNb57UGFJeoy52cSAXKYHQXrBHOC/vgjBuQwRJlU9yEYF4B4RKkCsTaUmrIkDWF1n4A62Ffhks4SG1/6448kAYC+OYF9f6lZ67FPc+wTRyv49GFtA+X6HJCMGRKgrk5IFTzUBk5XScUBm0Whv7JPoNIwCULGJaZSO9iYaTP6BI+JryJOjUq51+GO66voCjDFE3XxQzlXTDMoxBycrMNiunEv5u6qykJJAp30lMzVSJXUVMpjLqLqHBL9HsNvvo9SkUUEwgJh9KdxikO9HCh2fxob2ykX0eeoPBBX7gD4nOijsPUk7xxcKqIsc/VSpsiSWxLY1if0q6sma9hph26o0MOrGyq7xd5uaQcBJvot+D773/Q7dSRPbKACUrKsENseoMKhqXopjvJdlwDfvMkmb7YSV+kE67fJkX3CVOQ6rdN6d1BXQw49Gfj60DVkQgaYpkSuOygIo92LNzu1w+v2+sh/4CLQahMhYSFzoY+JbrVqJV9XJf1D+saPav2efLgB9JgxPCakon19VSlpxP23N/WzXhWNk4fHjDHHnOCxqp4fXg2HCPXZMU5c7Iv314TSKv9+vepYf0L/6ctDe22x7rJR1WNb9bYMI2NMYbnvMtSb6od7gB3lOg+vKzLLtiGUKQYfrgGpTcZmR9WsD423t/8DocHang==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Transaction"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/transactions/{transaction_hash}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The single transaction endpoint provides information on a specific transaction.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./retrieve-a-transaction.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retrieve-a-transaction.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retrieve-a-transaction.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-transaction.mdx b/docs/data/apis/horizon/api-reference/retrieve-a-transaction.mdx
new file mode 100644
index 000000000..bbe820304
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/retrieve-a-transaction.mdx
@@ -0,0 +1,4 @@
+---
+title: Retrieve a Transaction
+openapi: "openapi/horizon/bundled.yml GET /transactions/{transaction_hash}"
+---
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects.ParamsDetails.json b/docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects.ParamsDetails.json
deleted file mode 100644
index 10fbf466d..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"transaction_hash","in":"path","required":true,"description":"Transactions are commands that modify the ledger state and consist of one or more operations.","schema":{"type":"string","example":"5ebd5c0af4385500b53dd63b0ef5f6e8feef1a7e1c86989be3cdcce825f3c0cc"}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects.RequestSchema.json b/docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects.StatusCodes.json b/docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects.StatusCodes.json
deleted file mode 100644
index 2a8be7068..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"operation":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","enum":["Account Created","Account Removed","Account Credited","Account Debited","Account Thresholds Updated","Account Home Domain Updated","Account Flags Updated","Account Inflation Destination Updated","Signer Created","Signer Removed","Signer Updated","Trustline Created","Trustline Removed","Trustline Updated","Trustline Authorized","Trustline Deauthorized","Offer Created","Offer Removed","Offer Updated","Trade","Data Created","Data Removed","Data Updated","Claimable Balance Created","Claimable Balance Claimant Created","Claimable Balance Claimed","Account Sponsorship Created","Account Sponsorship Updated","Account Sponsorship Removed","Trustline Sponsorship Created","Trustline Sponsorship Updated","Trustline Sponsorship Removed","Account Data Sponsorship Created","Account Data Sponsorship Updated","Account Data Sponsorship Removed","Claimable Balance Sponsorship Created","Claimable Balance Sponsorship Updated","Claimable Balance Sponsorship Removed","Account Signer Sponsorship Created","Account Signer Sponsorship Updated","Account Signer Sponsorship Removed","Liquidity Pool Created","Liquidity Pool Removed","Liquidity Pool Revoked","Liquidity Pool Deposited","Liquidity Pool Withdraw","Liquidity Pool Trade","Sequence Bumped"]},"type_i":{"type":"number","example":1},"created_at":{"type":"string"}}}}},"required":["id","paging_token","account","type","type_i","created_at"]}},"title":"Effect"}]},"examples":{"RetrieveATransactionsEffects":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/512a9946bc7ff4a363299f14f79e0beb9b9cdbd0103e3a69a44446a0aa6471a8/effects?cursor=&limit=10&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/transactions/512a9946bc7ff4a363299f14f79e0beb9b9cdbd0103e3a69a44446a0aa6471a8/effects?cursor=121628667754319873-2&limit=10&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/transactions/512a9946bc7ff4a363299f14f79e0beb9b9cdbd0103e3a69a44446a0aa6471a8/effects?cursor=121628667754319873-1&limit=10&order=desc"}},"_embedded":{"records":[{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/121628667754319873"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=121628667754319873-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=121628667754319873-1"}},"id":"0121628667754319873-0000000001","paging_token":"121628667754319873-1","account":"GAHK7EEG2WWHVKDNT4CEQFZGKF2LGDSW2IVM4S5DP42RBW3K6BTODB4A","type":"account_credited","type_i":2,"created_at":"2020-02-20T21:18:33Z","asset_type":"native","amount":"1573.5112616"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/121628667754319873"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=121628667754319873-2"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=121628667754319873-2"}},"id":"0121628667754319873-0000000002","paging_token":"121628667754319873-2","account":"GA2XP4KMY4KWNPW4KUCUKYUF2J7Y6HO5HLPUEA3VPVSMYCM3TGNEZP5S","type":"account_debited","type_i":3,"created_at":"2020-02-20T21:18:33Z","asset_type":"native","amount":"1573.5112616"}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects.api.mdx b/docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects.api.mdx
deleted file mode 100644
index 7cdaf02db..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: retrieve-a-transactions-effects
-title: "Retrieve a Transaction's Effects"
-description: "This endpoint returns the effects of a specific transaction."
-sidebar_label: "Retrieve a Transaction's Effects"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlWulSHDkSfhVF/Rgf0fcFdMTELpeBAQNrwKwPAqukrC4ZlVSWVN1miY7Y19jX2yfZSFVVdzXdYDwbM+ud8R/cUiqPT6lUKrPuAkdHNhh+CM4NVZYyJ7SywVUt4GCZESn+DobBeSwsAcVTLZQjBlxmlCUuBgJRBMxZoiNCiU2BiUgw4ubcGkEt0CkYij8OeDAM3oAzAsawWZW5m/MJakFKDU3AgUG97gJFEwiGQYXjdUxtHNQCgZql1OH/DXzJhAEeDJ3JYEn9iiBCDRCmk4QqjiZQRxLNRXTrzZHAR2CIddQBoYoTppUV1qF9WgHRhiTaAJlZZNE+y2JIaDC8C9xtitpaZ4QaBbUAvtIklTjUh5D3WYtGve56v99qhf0u54Nu2IKoHw1gPQKI2nQN2mx9sLG+EUKXccZgvdOPuqzFWDCd1mZosMxYbUoMvmRgbhdAiKi0SyhsEpUlIZjcaL+Vljhd3TepmbeKCEUoYVpK8Kih+QZsqpUF63ERlqSZlMBJZHTisUvpSKjRtdM3oMiYygxyrzDAtOErcRLKwQhMFajBoDUYtNd6a+sb/Y12q181WxsO3281BytGipZ2oKqeERo5iQWLCw0tsbHOJCc0TYGaBjlJc48RismMA/lELftEnlPLQHGhRi/QHT6huE/kOf4phhvkAMUI9LVRloByRFj173/+yxELrkaEIxwimskcf8/2G26ksgRPKbUsyA0MrqrASJEI953AnMdAEvpVJFlSOobf5RyK/IwDbxCk8/wJo4oYqkaQ73kble+0WqROqCJZmoIpCL2DCUtiajjTHDhCva+N+IdWJNKGpGAibRKqGBAD1OI5ehi0cgOBL2HXbj3Vr9qt6fQKQSm8GKk7rRb+WcTlLGMMLEYippUD5ZCEpqkU+dlofrZId1eRSqU8iXy0KuTr8DMw3JDUYKRwIpd3LYW6sRU9H6CzIKNvU8UGolXO4pF13ivUTTCtBQ6SVCJ8FepQawlUYVSpOMqHnOlVLXDCSajwUPDV/WAqpQbGP5RKUyQrh478VuMZ/YZPQBIC5wtiHyAtzmaFkBpD8agLB8kT/Oqp/je73X4oeGuBxaMJ/AkW/N6OyIDDj6UWUgm+SlhJJ7hXvnJrP0a9QDetBZQxnSm3aklKnQODsXTvw2b9fau+cXXX708rzCjnBmMsWuoXP3zlbeZyyLYBj0dtNvIGEj1eGNk2wMUi0Q6E90bOYwM21pJbcpHyezz3dQJkRydUqBWzryQdrVp1oCKZ5xc7YJ0oco053ZkYKTAVE4qBuQXFwHzJucmsk0JBZdV8bL5wPrZq7WbmYrx27w3vAK1OnETRgnb577mM/HeVP+UQ1IId6mhlmf85X+V/zhdtSyoSGkogW1T6i3++csWcH1nY9geIFjbiDO92bWws0hUOU51d3sTq7Cp8V/NePb9qL1bzn/kpovW4+kskyzYskcwFLcO3WtrjdI/t5+MGFh7+jR1aJlqxUctEc3FH4ksmuHC35FRrWRFxb+LBFW9grG9WTexAqq1YyexSuJgbOlmeKY/KGXzJAEHaypIUeHBVRL5rUYl9eRa+kLROawHLTbimK2LtNM85qreB4MG9oD6P1UW0nYleYH5VzV7y53gwRT0LbfwF9ujbfXgX+GffYqpRJrP53RfEzqV22GzG+XOg7sA6Ba5hHUhJTUObUbPy2LfNfrtDNzZ6g5CtRVGPdgfdzsZG1O5FaxvQCiHcCDcYD3mr3epClw42aK/X6w1oi9JBb61N15tFieIv+aP555/8G+Xndusn/wr8Gd9UlQT3R1Gz3WkPOuuDwdpav9dtb6yvdeudB1QvE+EfWPX2fdX9GxY9biH/nWW4H6oetJCOfoeR8yJNc1ml+/nkd/AtzZ1b8tMjlt/PEH+1IPotOUXGF7RWTLfKf+374WEYrORWyfCCvc39w7Xd3b3O5eX+28Od4/Pe9u7fXr3fO3zVOdrbObvsHLx93Tvr75z2Om+2LruHg63zk52t3mYZcIYlr2s2z9DK8NdZDHFBp9Vp1Vudeqd13mkP2+vDbvc9amMtuOsyUlInxhjIaFKo2O6vdRv9drszaA/8q+sP4j6d38l9Ok90n86T3Kdzz306fz/tHb5+1zu8PD697B1ebF8cvrt41fll7d1g/6S/f3R6sbvZfXv69uz1u+3X3fO94933p/2zZffhs2y+9J7ub+A9V9PiXy1IwMUaQRmBy182cTAMFsPn3f3a9LREHktTYMZlKTsz8mk7F6yq1Z3ndOQY3ESbG+/kqzlGmcsMPIXnq5KSqJLrFVYRI+1zjSIZKCp3QS1AU/LVrUargUHCZklCze2ciqRGjwX3ZWKyf35+SjZPD7BUxzE3FcrXX89yvUqpDXLgiFAjsC6vLhuoe+DyHoNfmRrNMwachLerWOQVa3xHz6qPQK3Aarf2RfwsgXIpHYOhIyCVoh4xIL1XILkvZs8rlHVtBCgHPFfEQGrAgnJ5bCCZzZUqFdrWBrBqKqy3vGJHaAQfAQnBTQAUis+tXVx5avRn31KR4gbIhEoJztYIBwbKGSrx0UbgK4uxEmtrnoN3byKszcB4jWbVVqeJzUJflK34bI34IjFuUXG0SJhn8TWsaVtngCYExqBKPaqrfdNgtrKx5Fl/dk/4UN3Qq+fl8eQwBomXil2I0oXaTaYN1JXm8OJP5T0f1UdVisMGQwg4BRaxHAtK2MWboxqhJDR6YsF4Cb4Tl3dyZlif7Rzab2LNNbNNp7W0TctvLCKtiQF0J8+NaXzpfMXnm47Irc4MehsCWiMT8M2RJAHFccoDRRUKJkJZB5TjooTeCDUiXBhgzu8ho1Jab6ff1lEmOJD8xIRgSawnHhKeCCWsA0NKF/fuWGKDIvwz+7mBKHdmb//OzNJnZEvq0RyDyWSyaPyMsh5KPWrSuoJJ3WaqjrdQDPXi/njhWzQWK2EhZTcjozPFiVb3T0PuO4bFwgFzmaGSiATPPCR+53XRz0noZ21IcXWQMEvSFw3ySmP/La974jANdYatHa8iAljIm7mG5hBSCzXCYmA3BKmr9vuG0R5COwdgJFychQ2mk2aBQ/m3NLUZSh02sdrX3Nl9u3t0cnpwvNdI+Au/XVsQYa93goduJBQ2n55ZMtHGYctQOJ8eqpHXA8OA8EoAi3Xe8fL64bEkx5r/mkBAuGa+FeYxGpKXLydAuCZKO+zGa2OBmEwpVKIECrcsD0MU29iKU4nHpRolZr708mUeAMA3gKmUt561X3s9plJwb+D10t0G6PoGiJtoYgE79g4Pj2JgVBFUODCdpbLAJ8EwLJJUG4dVPXSwUHsYpaChkHjicFXFvRoLro+nK6GKjsASgc41UTWSUgO8zvVEzdxLR4um6tSJxAc9lFmsxKCGIU9HRGECT55P4JmUpHKysA9pCSUfg22a+usA2X0MZtihi2AeCiaxJ9EZmLFgUEnGFl7bSFTXkb/KkCzvLVLmKw5FD7dUu+rQr/Do5W+X2r1kbzG1g4QKPwtS6r9W56a1QAoGykJF1mZKWQyk02hh84ij70YCzGymns/MJRbhhPpZb1PB1DaPDrZ3j892cUkjdon0D4lUW5dQVRFZVo4IJZXa0TNL5l9+LGQRd/P263/7+UmR9jv46pqppML3L7xtd0VG/6H6fQmqMlzxvUmZ1F/Vglhbh6vu7jAmXRg5neJw3nnHVJ8Li7XRB3rvVdv+919lrITnBm6r35kUdb3Avzq+x7j/m48vHkGh/OzkV4LwB/rQ4hGQyk9Q5iBd4Q8jEKXvPBPP3xQF7Rfkt/50a6VFZdVB3VYNKi1dCg2+Sh4DRS9BQ3OyTcYgrSKy9A0JIjQrMOztngfT6X8Af+ewWg==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Transaction's Effects"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/transactions/{transaction_hash}/effects"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint returns the effects of a specific transaction.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./retrieve-a-transactions-effects.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retrieve-a-transactions-effects.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retrieve-a-transactions-effects.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects.mdx b/docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects.mdx
new file mode 100644
index 000000000..5a75db361
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects.mdx
@@ -0,0 +1,4 @@
+---
+title: "Retrieve a Transaction's Effects"
+openapi: "openapi/horizon/bundled.yml GET /transactions/{transaction_hash}/effects"
+---
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations.ParamsDetails.json b/docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations.ParamsDetails.json
deleted file mode 100644
index aba9b7ee8..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"transaction_hash","in":"path","required":true,"description":"Transactions are commands that modify the ledger state and consist of one or more operations.","schema":{"type":"string","example":"5ebd5c0af4385500b53dd63b0ef5f6e8feef1a7e1c86989be3cdcce825f3c0cc"}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}},{"name":"join","in":"query","required":false,"description":"Set to transactions to include the transactions which created each of the operations in the response."}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations.RequestSchema.json b/docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations.StatusCodes.json b/docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations.StatusCodes.json
deleted file mode 100644
index 470d7e620..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_links":{"type":"object","properties":{"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"type_i":{"type":"number","example":0},"type":{"type":"string","example":"create_account"}},"title":"Operation"}]},"examples":{"RetrieveATransactionsOperations":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/6b983a4e0dc3c04f4bd6b9037c55f70a09c434dfd01492be1077cf7ea68c2e4a/operations?cursor=&limit=10&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/transactions/6b983a4e0dc3c04f4bd6b9037c55f70a09c434dfd01492be1077cf7ea68c2e4a/operations?cursor=120133379185221636&limit=10&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/transactions/6b983a4e0dc3c04f4bd6b9037c55f70a09c434dfd01492be1077cf7ea68c2e4a/operations?cursor=120133379185221633&limit=10&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120133379185221633"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/6b983a4e0dc3c04f4bd6b9037c55f70a09c434dfd01492be1077cf7ea68c2e4a"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120133379185221633/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120133379185221633"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120133379185221633"}},"id":"120133379185221633","paging_token":"120133379185221633","transaction_successful":true,"source_account":"GDJX67SFY2N73H72TWMKKBQP5UPBNKBNUMNE2IGFKNES43S4327X6DHG","type":"manage_buy_offer","type_i":12,"created_at":"2020-01-28T21:14:59Z","transaction_hash":"6b983a4e0dc3c04f4bd6b9037c55f70a09c434dfd01492be1077cf7ea68c2e4a","amount":"0.0000000","price":"0.0001000","price_r":{"n":1,"d":10000},"buying_asset_type":"native","selling_asset_type":"credit_alphanum4","selling_asset_code":"ETH","selling_asset_issuer":"GBDEVU63Y6NTHJQQZIKVTC23NWLQVP3WJ2RI2OTSJTNYOIGICST6DUXR","offer_id":149983118},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120133379185221634"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/6b983a4e0dc3c04f4bd6b9037c55f70a09c434dfd01492be1077cf7ea68c2e4a"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120133379185221634/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120133379185221634"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120133379185221634"}},"id":"120133379185221634","paging_token":"120133379185221634","transaction_successful":true,"source_account":"GDJX67SFY2N73H72TWMKKBQP5UPBNKBNUMNE2IGFKNES43S4327X6DHG","type":"manage_buy_offer","type_i":12,"created_at":"2020-01-28T21:14:59Z","transaction_hash":"6b983a4e0dc3c04f4bd6b9037c55f70a09c434dfd01492be1077cf7ea68c2e4a","amount":"0.0000000","price":"0.0001000","price_r":{"n":1,"d":10000},"buying_asset_type":"native","selling_asset_type":"credit_alphanum4","selling_asset_code":"ETH","selling_asset_issuer":"GBDEVU63Y6NTHJQQZIKVTC23NWLQVP3WJ2RI2OTSJTNYOIGICST6DUXR","offer_id":149983119},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120133379185221635"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/6b983a4e0dc3c04f4bd6b9037c55f70a09c434dfd01492be1077cf7ea68c2e4a"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120133379185221635/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120133379185221635"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120133379185221635"}},"id":"120133379185221635","paging_token":"120133379185221635","transaction_successful":true,"source_account":"GDJX67SFY2N73H72TWMKKBQP5UPBNKBNUMNE2IGFKNES43S4327X6DHG","type":"manage_offer","type_i":3,"created_at":"2020-01-28T21:14:59Z","transaction_hash":"6b983a4e0dc3c04f4bd6b9037c55f70a09c434dfd01492be1077cf7ea68c2e4a","amount":"98.5005752","price":"0.0003494","price_r":{"n":17471,"d":50000000},"buying_asset_type":"credit_alphanum4","buying_asset_code":"ETH","buying_asset_issuer":"GBDEVU63Y6NTHJQQZIKVTC23NWLQVP3WJ2RI2OTSJTNYOIGICST6DUXR","selling_asset_type":"native","offer_id":0},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120133379185221636"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/6b983a4e0dc3c04f4bd6b9037c55f70a09c434dfd01492be1077cf7ea68c2e4a"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120133379185221636/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120133379185221636"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120133379185221636"}},"id":"120133379185221636","paging_token":"120133379185221636","transaction_successful":true,"source_account":"GDJX67SFY2N73H72TWMKKBQP5UPBNKBNUMNE2IGFKNES43S4327X6DHG","type":"manage_buy_offer","type_i":12,"created_at":"2020-01-28T21:14:59Z","transaction_hash":"6b983a4e0dc3c04f4bd6b9037c55f70a09c434dfd01492be1077cf7ea68c2e4a","amount":"291.8057980","price":"0.0002565","price_r":{"n":250039,"d":975000000},"buying_asset_type":"native","selling_asset_type":"credit_alphanum4","selling_asset_code":"ETH","selling_asset_issuer":"GBDEVU63Y6NTHJQQZIKVTC23NWLQVP3WJ2RI2OTSJTNYOIGICST6DUXR","offer_id":0}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations.api.mdx b/docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations.api.mdx
deleted file mode 100644
index b12e37dd7..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: retrieve-a-transactions-operations
-title: "Retrieve a Transaction's Operations"
-description: "This endpoint returns Successful operations for a specific transaction."
-sidebar_label: "Retrieve a Transaction's Operations"
-hide_title: true
-hide_table_of_contents: true
-api: eJztW+ly27YWfhUMfzTLaKH2ZabTm8VxnKTOYiVdEo8CAocSYhBgAdCK69FMX+O+3n2SOwckJcpSnKVJ6qb1H8fEAXDWD4fEl/PA0ZkNxi+DiaHKUuaEVjY4rgUcLDMixb+DcTCZC0tA8VQL5YgBlxllyVHGGFgbZ5LoFAz1k0msDaHEpsBELBhx64UbQS1YCR7wYBw8A2cEnMKt6vaPV2sFtSClhibgwKCW54GiCQTjoLLodE7tPKgFAvVMqcN/G/gtEwZ4MHYmgy1jKnsRaoAwnSRUcUvcnDqSaC7iM+LmQCTwGRhiHXVAqOKEaWWFdUTHRCsg2pBEG6hYjyZaNoeEBuPzwJ2lqK11RqhZUAvgLU1SiY96EPEeC2nc7Qx7vTCMeh3O+50ohLgX92EYA8QtOoAWG/ZHw1EEHcYZg2G7F3dYyFiwXNZW3mCZsdqUPvgtA3O24YSYSrvlhVtEZUkEJjfaB9YSp6uhk5p5q4hQhBKmpQTvNTTfgE21smC9X4QlaSYlcBIbnXjfpXQm1Gzq9AkockplBjiNEgNMG77TT0I5mIGpOqrfD/v91qA7GI56o1bYq5qtDYePt5qDFTNFSztQVb8QGrmYCzYvNLTEznUmOaFpCtQ0yOM0zxihmMw4kNfUstfkOrUMFBdqdgPT4TVu95pcx1/F4wY5wG0E5tosS0A5Iqz63x//dcSCqxHhCIeYZjL3v1/2PWmksgRrlloW5AYGx1XHSJEI95GOmcyBJPStSLKkTAwf5dwVecUDbxCU8+sTRhUxVM0gj3kLlW+HIakTqkiWpmAKQZ9gwpI5NZxpDhxdfV8b8btWHi1SMLE2CVUMiAFqsY7e7bQygMC3fNcKPzSvWmHVYUVIpzEVEvhHeu4IHO6NSIO/y/TI16oCo1BYNajrdjL52VhJfoudVkRaS6BqHX+PbV5+I/pvtFCfakIFGCumYI1sjOV1wgxgFAhQNl+V0oa5+KQEikawPEZFCthAw9phiL8u6JIfKkEtYFo5UA5FaJpKkYNR841FufOKg6iUj2N/PBSu0tEbYFgBqUGFnMj3m0qhTmzFpe+QsyDj90vNDcS7qtOnsvNlqE6CZS1wkKQSPbUjmMtlNTgv80WPa4ETTkJlDQVv3RVTKTVweqVUWqJY+eiRDzWWxefJCYhjYO4DBL92DBhwuGpqXcECsggr/Ko5qoKqV0ozlBJ812alnOA+/ypN3mXSG3Ko4VkKU1GZkbcc1RM6LMQu76PzM2hKGdOZckEVAVavEcHyeLma4z35vteO8XngO9ZNgCizOo9DMHcuteNmc553MnUH1ilwDetASmoa2sya1VOz2Y9Gww7tQshZh4XduBvxfjQKOwPW68WDkIYj1u10eczDVnfUjqAVDgYsHgDtD1kburS5Plx/yFv+77/zHdb3rfA738N+jx1h5bS4Qpq22mGr0+kMRq1hr91u9Tv9d+heHitXWffORd19D47JN4UkAs7z0iu6Z9+Z/Kk0WqvU3NZlB478Vb5DVSoH5eeysFmuWeJ4AeQfsX6xwg/rcH33zuBePFg/eRt6+S4FxgY7xi4i626Z6lcQu/oWU370sDozbA2N42D/7oOf+4Oje7+0Dwed+4P25KcfHz68/fRJ7/mT24cPbx8+//Fwr32wf+/h4d5Rt3PU7bQHP/fv3t8PSiAOEqroDKZRdjbVcezxukTyVrtWgDGf+sOoHbbDetiqt4eTdmvc6o57o18v6Oy/3IyDP511tYAmhY1hI8x//OkpGJTPWpVnU4NhVcG4VQs4vguGIZ42UXaGLqfWgpuW5xJ14hQC39LIrVFmgAs3pTKdU5Ul3S05fN0NxsHe5P7WkLA2A4NhuX1378XzfueX/uHk/oOnT389ePhicqfdOfzp0dMXTzo/PWg/O2g/nhw9mBz+8vhg/+DO0aR/9/nPz/BjGgZhiknU6o5Gw06rNcSO94thTfebx5ru18Wa7lfBmu4lWNP9AKzp/os1/2LNNtaMvijW9L55rOl9XazpfRWs6V2CNb0PwJreX4g1F3GmcyVgZjRs9MKwN+i1L+JMpzvqbuPMoDvIsaZXwNM74GYHoGyIbeDJxsjngJOdGLdCwDXYhF8UZPrfPMj0vy7I9L8KyPQvAZn+B4BM/9+GZhfStEetxjDsDUbDrZam3ev3tqCm3QvDzshjzWjQuxRs/i69Tbg8XhY/tSABN9eYZDPwX2ORXDAONqv+/GJMlpVy9Mqa05K8kBn5YaUQ7LqdneRy5BDcQpsTf7exe8U4c5mBD1nzXilJVLnqMV4dxtp/di2+pBZ3tUEtQFPy2WEjbLTQvixJqDlbS5HU6FPBPTGA3J9MnpBbTw7wNpFTR8tLwaNcr3LXBjlwRKgZWJfzCQzUveOsl/YzU6N5xoCT6GzXEjlHAT+Fr+6bgVqB/AbtaRtZAuVUegqGzoBUbhWJAelT1N+DIn1hfSdd10aAwptOr4iB1IAF5Yp7zszmSpUK3dEG8J5cWG95xY7ICD4DEoFbACjcPrd2c+YTo/HzvyVSnABZUCnB2RrhwEA5Q6X4He9c37I53r3bml/BlwLJS8FrtLpfd5rYLPLX8JW0rRF/M4whKiCORFSisTVkMVhngCYETkGVely8G17PbGxl1j89E15WA3p8vSxPDqcgERzsxrFXqN1k2kBdaQ43/lHZ80q9UuV2SCmJAIfAoi9PBSXs+bNHNUJJZPTCgvE7eO5VTjhY+fro7kP7Xl9zzWzTaS1t0/ITi57WxACmk1+NabwjeivcGa5/pjOD2YYOrZEFeDpMkoDiOOQdRRVuTISyDijHSQk9EWpGuDDAnI8ho1Jab6cP6ywTHEheMRFYMtcL7xKeCCWsA2TP5Snu07H0DW7hGTLXDcR5Mnv7764svUZuSz1b+2CxWGwav5KsR1LPmrSuYFG3marjKTSHenF+3PCkHKuxTCg7mRmdKU60ulgNee4YNhcOmMsMlUQkWPOQ+MjrgsGT0DfakOLoIFGWpDca5J5GxlV+dYmPaaQzJPN4FdGBxX6r1NAcImqhRtgc2AlB6ar9niK0j65dO2Am3DyLGkwnzcIP5e/S1GYkddRMqFDNu3sv9h49fnJwuN9I+A0frtsQI7tvgUU3EwrpRtcsWWjjkCQmnD/m1czrgTAgvBLA5jrnOHn9sCzJoeafAgSEa+bJT95HY3Lz5gII10Rph2xMbSwQkymFSpSOwpDlMESRuKg4lVguVZRY5dLNmzkAgKf8USnP/NJ+7vSUSsG9gdOtsw0w9Q0Qt9DEAnI0HRaPYmBUASocmM5SWfgnQRgWSaqNo8r5BIu0d6MUNBISKw5nVdKrsZH6WF15B22JwORaqBpJqQFe53qhVuml401TdepE4kEP9yxmIqgh5OmYKHwfItcXcE1KUqksZJ5ZQsmr4A5N/XGAy70KVr7DFMGWHExiH8dHYE7zdrkM8sZ7IgrVdeyPMhTLyU2U+VvagrdVql1N6HtYevkldu1Cs7fZ2kFChR8FKfV/qmPLWiAFA2WhstetlLI5kHYDG33BMXdj4bvofKSej6x3LOCE+lFvU7GobT46uLN3eLSHUxpzl0j/bpZq6xKqKluWd+6Eksqt+zVLNui+G43E+ZoC9hkZyMU7h4O3rplKKjwhwVt6XrT4L6svWqjVeAffuNLlH9eCubYOJ56fI0g9N3K5xMc5/w57fy4sjeS7GHhVS/96Yu5OD53AWZVqXPAjAv8a8jHG/W34t5d4oWQef6ITviGu7SVOKlnIn+ikL0SrvUThLRbwpubvVfSLkmcv1byg/K71PcY/jEBXfyT6XH9WkMNukC/9/yR2GlQ8pOqsalBp6BYOe2rXHCjWIxqai91iDNJq7m3xh9FDq887+3uTYLn8PwYNVHU=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Transaction's Operations"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/transactions/{transaction_hash}/operations"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint returns Successful operations for a specific transaction.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./retrieve-a-transactions-operations.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retrieve-a-transactions-operations.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retrieve-a-transactions-operations.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations.mdx b/docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations.mdx
new file mode 100644
index 000000000..4419c08fa
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations.mdx
@@ -0,0 +1,4 @@
+---
+title: "Retrieve a Transaction's Operations"
+openapi: "openapi/horizon/bundled.yml GET /transactions/{transaction_hash}/operations"
+---
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments.ParamsDetails.json b/docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments.ParamsDetails.json
deleted file mode 100644
index 10fbf466d..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"transaction_hash","in":"path","required":true,"description":"Transactions are commands that modify the ledger state and consist of one or more operations.","schema":{"type":"string","example":"5ebd5c0af4385500b53dd63b0ef5f6e8feef1a7e1c86989be3cdcce825f3c0cc"}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments.RequestSchema.json b/docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments.StatusCodes.json b/docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments.StatusCodes.json
deleted file mode 100644
index 624df53c6..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"payment"},"type_i":{"type":"string"},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string"},"asset_code":{"enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","asset_type","from","to","amount"]}}}}},"title":"Payment"}]},"examples":{"RetrieveATransactionsPayments":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/f8929884dfc56ff9d8bc220c7bfba9e58208943eba96f33e8a0787a5bb8a4629/payments?cursor=&limit=10&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/transactions/f8929884dfc56ff9d8bc220c7bfba9e58208943eba96f33e8a0787a5bb8a4629/payments?cursor=3382840796385281&limit=10&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/transactions/f8929884dfc56ff9d8bc220c7bfba9e58208943eba96f33e8a0787a5bb8a4629/payments?cursor=3382840796385281&limit=10&order=desc"}},"_embedded":{"records":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/3382840796385281"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/f8929884dfc56ff9d8bc220c7bfba9e58208943eba96f33e8a0787a5bb8a4629"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/3382840796385281/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=3382840796385281"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=3382840796385281"}},"id":"3382840796385281","paging_token":"3382840796385281","transaction_successful":true,"source_account":"GCNEGL4IYJ4XH2GV62QK4PQ5D4YWSYZPBC3NVF6VMNSFUMBFW3V3DKKY","type":"account_merge","type_i":8,"created_at":"2024-07-29T19:33:23Z","transaction_hash":"f8929884dfc56ff9d8bc220c7bfba9e58208943eba96f33e8a0787a5bb8a4629","account":"GCNEGL4IYJ4XH2GV62QK4PQ5D4YWSYZPBC3NVF6VMNSFUMBFW3V3DKKY","into":"GBFAIH5WKAJQ77NG6BZG7TGVGXHPX4SQLIJ7BENJMCVCZSUZPSISCLU5"}}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments.api.mdx b/docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments.api.mdx
deleted file mode 100644
index c35bee75e..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: retrieve-a-transactions-payments
-title: "Retrieve a Transaction's Payments"
-description: "This endpoint returns the payments of a specific transaction."
-sidebar_label: "Retrieve a Transaction's Payments"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlWuty27YSfpUd/mguo5slS5Y00+mxHcdx4jpO7bjNxeOAwFJCDAIsAFpxPZo5r3Fe7zzJmQVJmbLlXJqe0/T0l2xygd398GF3seBV5NnEReM30SG7TFF7F502IoGOW5l5aXQ0jo6n0gFqkRmpPVj0udUO/BQhK8eASYCBy5DLRHLwlmnHOA1vRY3IZGgZ/bMnonH0E3or8QI3j6+l3EJ5I8qYZSl6tGTVVaRZitE4qk15NmVuGjUiSbZlzNPfFn/NpUURjb3N8ZYDNU3ALAI3acq0ICeYh9QImVwGhxSKCVpwnnkEpgVwo510nhw0GsFYSI1FWLjkyEHHp5iyaHwV+cuMrHXeSj2JGhF+YGmm6FEfY9HnHZas94b9fqcT93tCDHpxB5N+MsBhgpissQ1c48PBaDiKsccF5zjs9pMe73AezeeNBRo8t87YCoNfc7SXSyAkTLlbKGyCztMYbeF0WEwH3tQXThkevAKpgQE3SmFAjdy36DKjHbqAi3SQ5UqhgMSatCTDROrJmTfnqOGCqRwLWljkxoqVOEntcYK2DtRg0BkM1jbWN4aj/mit06+7bazAL/daoJMTzSo/yNQwETk5m0o+LS104KYmVwJYliGzLXieFYyRmqtcILxjjr+D+8xx1ELqyQOiwztS9w7u00/5uAV7pEYS1yY58Rqk0//+5788OPQNkB4EJixXBf5h2k/QSOcp7VHmeFQ4GJ3WgVEylf4LgTmeIqTsg0zztCJGWOUCimKXo2gByYX5gTMNlukJFmu+RsZ3Ox1oAtOQZxnaUjAQTDqYMiu4ESgI6ifGyt+MhsRYyNAmxqZMcwSLzNE+uhu0agFR3MJurfO5vFrrzOenBErJYpLudjr0s4zLUc45OopE3GiP2pMIyzIli73Rfu9I7qqmlSn1PAnRqtRv4vfIaUEyS5HCy0LfmZL63NXsvEPOoUo+LTW1mKwiS0DWB1bo82jeiDymmSL4atKxMQqZpqhSI8qbYtLTRuSlV1ibQ+MH/42ZlFm8+KZMmpNY9Wg/LDXt0U9wAtMYhVhSe4douTdrgsxaRltdekw/g1d/Yf7V8v83ZhkmCXL/Gaj+T61yFMVQfGtmZRY5Cvy2zLohFNi/zLjrVa4hW/PmdN6IpFhlbqVJiuB+rUS6Lb1M8zNXJKIkV6s8a0TO5JbjGePc5NqvUp4x79FSUtt9s9l83WmOTq/6/XnNLCaEpWRHqsPgj5WwZbVfCZ/JlS5wi7QaZ2yFSTc8DIX8KiHmHPqz1RYtXlNlQa+r4ohKvAuMggVC+jOmsinTebp++9FaNyxZMY90Lkf71fhRTfT1i2C+egqWrqbDTZpLEd0g5J30u8W1ki0LHiyt+oo1XlrREqrg7MLc0/ly+jysuEbrVFIwxIWPHx/HV1E4eSxnuyqfFTElmnqfuXG7PS0q0qZH5zX6lvOoFLMtYyftmguunQxH3dFwuC4S3h8kyUgMY97tdvhGnMRshP1htzMcrfcwZqNB0uvhkHU2hhusH8dDtj7ojtrVOfmH4uD2/XehTv5+rfNdOIl8T3V9rcj6Zuzs9Ybd4XpnYzToDfvd4doddleV2F/G7nCCIrotVV+1+uqruHPdHGjfNGRFKfNngXajdvlj/GtXM94oQb5g9nKGH65X6rs7VvVmQfG7lbCP6ShTe3Trzc10vkrirnxedKluZvBod/tgZ3d/fe/V0/VfnnR3TwbdF8/WD1/0H62/+vno1evDre3ewcnjwcmPB0ePX/649fjn3knv0bNnr6qAPI7Kuc5StJNagB4PlxNz1O1015udjWZ3dLw2Gvd6427v9arIPY6+mmeN6A9xUGpKjtHu1uPNvSf9n59tPn2xsXGwO9h6vbtxvHuy+8uTw1/Wj17s7z3d2No5ePrj9sn266OXrw+P9o6291/2w/GsTDIp+qmhNZ2gL9IrObq8va5uQjFfRBnKh2gvqg5lbtXnsS5a1YI5LuTgAP3M2PNwYlw9Y5L73OLnzPm4kgRdzXpKACZFdVGm2LIhEzUicqUY3Wl1WmuhyE1TZi+vpSCz5kKK0P2DJ8fHh7B5uEcdGME8o/YOtdWOCrsqrS3Y8yD1BJ0vmoYWmwG4onkcRmbWiJyjgPhy1RRFI5Jq/kVTCZmT1MQ0oTebp1gNZRdo2QSh1qsBiypUhSQeepTXjaemsRK1R1EYYjGz6FD7IrJB7gqjKoO2jUVqhkkXPK/5EVspJggx+hmiJvWFt8sjD62hc44DJc8RZkwp9K4BAjlqb5mSv6EA/MCn1GBzjTBDKJqgqE+DRYsmmjfg8jj02mqkbUDo/dESlVsOYqbI2Qa1Kp23yFLAi9CyD3bUR4de8GJk6xaz/u5MeFNf0NP71fYUeIGKUqJbyjCl2W1uLDa1Efjgb8Wet/qtrtRR3zhGeoWOsLyQDPjLn/YbwCC2ZubQBg3hgqVo0C+wPnr0zH0Sa2G4a3tjlGs7ce4IaQMWiU5hNm7o+PBB+kua/9LklthGgDZghqHnnaaoBb0KQDFNikFq55EJGpSyc6knIKRF7sMacqaUC36GZZ3kUiAUOyZGB1MzC5CIVGrpPFqoKB7oWGFDKkIb/L7FpCBz8P/RwtN7sKXM5BqD2Wy27PxCshkrM2mzpsZZ0+W6SVlois0yfzwInXdnaJswfj6xJtcCjL65GwruWD6VHrnPLVMgU9rzuLjqC236lL03FsrUAXGeZg9a8NjQtUrRo6HHLDY5deyDiQRgqW9BDSMwZg4bwKfIz4Gk6/6He4BdgvYagIn00zxucZO2Sxyq38rVdqxM3E6Z1O1HOyc7+88P9w52W6l4EJZrCxO6wpvRpptITXcK9xzMjPV0EyR9KG71JNhBYUAGI5BPTXGREeyjbQkHRvyeQADC8HDDETAaw8OHMwRhQBtP16zGOgSba01GVEDRkhVhiNHtpBZM0XapR4kFlx4+LAIAhns9ptRlmDqMPbtgSorg4Nmt3IZEfYvgZwYc0kWsp82jOVpdBhWB3OSZKvFJKQzLNDPWM+0DwWITYFSSxVLRjqNRNXq1lqhPuytlmk3QgSRyzXQDMmZRNIWZ6QW9TLLsqsm8TEPQI53lSApqFPJMApoOHnB/hveUgtrOouslBwzeRtssC+mApnsbLbAjilAdjDZ1z5MjtBeSY60YWzqOkVDTJCGVkVhxZcR4OMSXV3OV2XVCP6atx8rO4nKxt1zaYcpkeItKmX/U380bkZIctcOars2M8SlCt9WhelkQdxNJra3yTbN4c62xDCcsvA0+lZO69v7e9s7B0Q4NaU19qsJBKDPOp0zXVFbtGGBQa8jcc1C70V8qI66ur9W++sOC8szj8YNvZ4rJ0BYN3l2VRf2b+omGbBmv6E1ltS8fpsZ5GnZ1RWHppVXzOT0u7lSp2hfSsVjddata9+7Pv29fic85Xta/ICjbZVE4eHyJc3+Za/WPoFB9UPA7Qfg/ukL/CEjVxwXXIJ3SP1YSSl+4J+7/VHagH8B/+6OclR5VXRJ9WXeo8vRWbAjd5ykyYgk5Wohtco5ZHZFbXwcQQosmw+7OcTSf/wc5T/gn
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Transaction's Payments"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/transactions/{transaction_hash}/payments"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint returns the payments of a specific transaction.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./retrieve-a-transactions-payments.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retrieve-a-transactions-payments.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retrieve-a-transactions-payments.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments.mdx b/docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments.mdx
new file mode 100644
index 000000000..fb98eea37
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments.mdx
@@ -0,0 +1,4 @@
+---
+title: "Retrieve a Transaction's Payments"
+openapi: "openapi/horizon/bundled.yml GET /transactions/{transaction_hash}/payments"
+---
diff --git a/docs/data/apis/horizon/api-reference/retrieve-an-account.ParamsDetails.json b/docs/data/apis/horizon/api-reference/retrieve-an-account.ParamsDetails.json
deleted file mode 100644
index 471489cae..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-an-account.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"account_id","in":"path","required":true,"description":"This account’s public key encoded in a base32 string representation.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-an-account.RequestSchema.json b/docs/data/apis/horizon/api-reference/retrieve-an-account.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-an-account.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-an-account.StatusCodes.json b/docs/data/apis/horizon/api-reference/retrieve-an-account.StatusCodes.json
deleted file mode 100644
index 6415f4482..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-an-account.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Returns details like balances, sponserships etc. about an account.","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transactions":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"payments":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"offers":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"trades":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"data":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transactions","operations","payments","effects","offers","trades","data"]},"id":{"type":"string","title":"id"},"account_id":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"sequence":{"type":"string","pattern":"[0-9]+","title":"sequence"},"sequence_ledger":{"type":"integer","format":"uint32","title":"sequence_ledger"},"sequence_time":{"type":"string"},"subentry_count":{"type":"integer","format":"int32","title":"subentry_count"},"inflation_destination":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"home_domain":{"type":"string"},"last_modified_ledger":{"type":"integer","format":"uint32","title":"last_modified_ledger"},"last_modified_time":{"type":"string"},"thresholds":{"type":"object","properties":{"low_threshold":{"type":"integer"},"med_threshold":{"type":"integer"},"high_threshold":{"type":"integer"}},"title":"thresholds"},"flags":{"type":"object","properties":{"auth_required":{"type":"boolean"},"auth_revocable":{"type":"boolean"},"auth_immutable":{"type":"boolean"},"auth_clawback_enabled":{"type":"boolean"}},"title":"flags"},"balances":{"type":"array","items":{"anyOf":[{"type":"object","properties":{"balance":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"liquidity_pool_id":{"type":"string"},"limit":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"buying_liabilites":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"selling_liabilites":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"sponser":{"type":"string"},"last_modified_ledger":{"type":"integer","format":"uint32","title":"last_modified_ledger"},"is_authorized":{"type":"boolean"},"is_authorized_to_maintain_liabilites":{"type":"boolean"},"is_clawback_enabled":{"type":"boolean"},"asset_type":{"type":"string","enum":["native"]}},"required":["balance","limit","asset_type","buying_liabilites","selling_liabilites","last_modified_ledger","is_authorized","is_authorized_to_maintain_liabilites","is_clawback_enabled"],"title":"BalanceLineNative"},{"type":"object","properties":{"balance":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"limit":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"buying_liabilites":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"selling_liabilites":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"sponser":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"last_modified_ledger":{"type":"integer","format":"uint32","title":"last_modified_ledger"},"is_authorized":{"type":"boolean"},"is_authorized_to_maintain_liabilites":{"type":"boolean"},"is_clawback_enabled":{"type":"boolean"},"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["balance","limit","asset_type","asset_code","asset_issuer","buying_liabilites","selling_liabilites","last_modified_ledger","is_authorized","is_authorized_to_maintain_liabilites","is_clawback_enabled"],"title":"BalanceLineAsset"},{"type":"object","properties":{"liquidity_pool_id":{"type":"string"},"asset_type":{"type":"string","enum":["liquidity_pool_shares"]},"balance":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"limit":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"last_modified_ledger":{"type":"integer","format":"uint32","title":"last_modified_ledger"},"sponser":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"is_authorized":{"type":"boolean"},"is_authorized_to_maintain_liabilites":{"type":"boolean"},"is_clawback_enabled":{"type":"boolean"}},"required":["liquidity_pool_id","balance","limit","asset_type","last_modified_ledger","is_authorized","is_authorized_to_maintain_liabilites","is_clawback_enabled"],"title":"BalanceLineLiquidityPool"}]}},"signers":{"type":"array","items":{"type":"object","properties":{"key":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"weight":{"type":"integer","format":"int32"},"type":{"type":"string","enum":["ed25519_public_key","sha256_hash","preauth_tx"]},"sponser":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["key","weight","type"],"title":"signers"}},"data":{"type":"object"},"num_sponsoring":{"type":"integer"},"num_sponsered":{"type":"integer"},"sponser":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"paging_token":{"type":"string"}},"required":["id","account_id","sequence","subentry_count","last_modified_ledger","last_modified_time","thresholds","flags","balances","signers","data","num_sponsoring","num_sponsered","paging_token"]}}}}},"title":"Account"}]},"examples":{"RetrieveAnAccount":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/accounts/GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA"},"transactions":{"href":"https://horizon-testnet.stellar.org/accounts/GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/accounts/GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA/operations{?cursor,limit,order}","templated":true},"payments":{"href":"https://horizon-testnet.stellar.org/accounts/GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA/payments{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/accounts/GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA/effects{?cursor,limit,order}","templated":true},"offers":{"href":"https://horizon-testnet.stellar.org/accounts/GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA/offers{?cursor,limit,order}","templated":true},"trades":{"href":"https://horizon-testnet.stellar.org/accounts/GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA/trades{?cursor,limit,order}","templated":true},"data":{"href":"https://horizon-testnet.stellar.org/accounts/GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA/data/{key}","templated":true}},"id":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA","account_id":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA","sequence":"120192344791187470","subentry_count":5,"last_modified_ledger":28105812,"num_sponsoring":0,"num_sponsored":0,"thresholds":{"low_threshold":0,"med_threshold":0,"high_threshold":0},"flags":{"auth_required":false,"auth_revocable":false,"auth_immutable":false,"auth_clawback_enabled":false},"balances":[{"balance":"3.0000000","limit":"922337203685.4775807","buying_liabilities":"0.0000000","selling_liabilities":"0.0000000","last_modified_ledger":27984507,"is_authorized":true,"is_clawback_enabled":false,"asset_type":"credit_alphanum4","asset_code":"EURT","asset_issuer":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"},{"balance":"4.0000000","limit":"922337203685.4775807","buying_liabilities":"0.0000000","selling_liabilities":"0.0000000","last_modified_ledger":27985131,"is_authorized":true,"is_clawback_enabled":true,"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"},{"balance":"72.8563792","buying_liabilities":"0.0000000","selling_liabilities":"0.0000000","asset_type":"native"}],"signers":[{"weight":1,"key":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA","type":"ed25519_public_key"}],"data":{},"paging_token":""}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-an-account.api.mdx b/docs/data/apis/horizon/api-reference/retrieve-an-account.api.mdx
deleted file mode 100644
index c244fe57b..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-an-account.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: retrieve-an-account
-title: "Retrieve an Account"
-description: "The single account endpoint provides information on a specific account. The balances section in the response will also list all the trustlines this account has established, including trustlines that haven’t been authorized yet."
-sidebar_label: "Retrieve an Account"
-hide_title: true
-hide_table_of_contents: true
-api: eJztW+tSG7kSfhWV/myyZ7CNwTjhzzkmECDhFi5JgFAuedT2aNFIE0mD4+Ny1b7Gvt4+yanWzNjjC8HZZDls7eYPqZlWXz51t9Q97SF1rGfp5jVthaFOlbP0JqAcbGhE4oRWdJOeR0CsUD0JhGVEBBRPtFCOJEbfCQ6WCNXVJma4hGhFGLEJhKIrwmJNhSCfDpNMhWCJhdDTCkVcBMSATbSyQPpCSsKk1UQK6wiT0r93JrVOCgWWuEjYsSIRswSsYx0pbAQ8IEKFMuVC9aaXMCS9A/X7r7850gFQhKUu0kb8FzgZgKvQgOoEjDdgn9NNegrOCLiDlsqRoQFNmGExODCI2JAqFgPdpLkubcFpQAUiljAX0YAa+JwKA5xuOpPCPKwTO37/9TdLkrQjRUhuYUBAhZoDR3QY6TALa3VinUGzDCQGLCjnVUW9bRhBzOjmkLpBggpllDSg8IXFicRHu9uH794dvTlcvzhovttvbWycNE/rJ1d7h+/2jz5cbR02m1s7W4d7B68/bjfe7Fy09nbfNE/X31zR0egGDcl2x6KQeq2Gf6aNOQWXGmUJB8eEtESK28lmByRbbmwkEkvAhRXCOjp1hKmxe9CAhlo5UA65sySRIvQmVn+xKGJYspNJedz1W5BbrDu/QOh3yOAuOpGp2pZC3doSMvfQWZDdh6kiA91FKGeOTzcpSqOjgDqIE8kcbvyYuqO1BKboaFT2i+uM6U1AnXB+owoeCr64J6ZSYuDuSak0QrLi0YHf6lHwoE9A3AHOp8TeQ2og1IaX/YcZwwYY5Q7iJfzqL+x/zjBlmc/RSxjwqKqN8/RTUyxhgxjwCH1aakG3C+GT00p3u/4cfVJKOcM4PDWlOHPsSak0Q+Sz10zGmIrSUmRMvHHsAWPUc0tvRgEVfJEphRaCox2la9cC2oQ5BwavJrvXrZWr2srLm2GjMSpxYZwbsHhkUAufU1AhfJ3RNTL5V4nDeFmJRVsC74EpcRLKAT4pbUUqlFurL+BUrC4zdCJeoBhSpB1Qzgza2fX0qxLnBE6vRchVV/r9anOwTiiW3ey+E9lIx9DmOmZiAa9RQCWzrh1rLroC+B/DbiGLOdb3ougiAzbSki8R9lL322P6BWqOAhqjrK+TRKIXfZ2mdK0pqTcKaFf6au0hPbG2aU9CdD7Mg4LkToesI+ErNCKOU/cATShZv8PC2zYopLwvsxQ2ZVaMAloUCF+7YTE1WOqun/NaJoQ/far4/wybZa8NU2NAhQPvO+JzKrhwg3aitVyYYjxVLNyPEdhJB0L12lKwjpDCTUHyHWwtSPmn8M3quccOaWHbk7J9sT9OkbSdbmPqcUyoxRhMr1zGjwPKrAXXzp4vqLlVGuOpiAn0DujN7GlZ+GnhPlP8FjnCwl28B+ZZiJbEY7HxpXN/K1P6QCg4yux6uND6wQH5T6h930n8T1iWwzKgoQEuXJvJJGIqjdfnH63W/V0044v9uIXpLnstrE2/e5O+LVOU9JrR4i+QRVqo7xJJZLmDeLmtn+FlI2bA+i1+qqnqT4zZH5VWnkLsz8TNvM8ED8XS/ysMDgpVT7SWdOQvC1b01HRn5Bu7jrcw+O5t7YPoRUvVlHivfyDwgNcbjdWX7ewDRxv1C6iNWL2x0Y6YjbwF4CsJ98UH5I/xzhm/yOTmluVal7alwH10b8sF2/Jp3PbKaa/OwvpuTAPT1VeJ5EdFX8J6mNKdvoVF9fUMAD4Spr5WjTsYc92Ee2NiQVk9VUQXRWqpupv4dI7sHI6zoM1YdjOa7vUXX+RG6Cv5Ry7v+vMf7TaH9I7JFKbb8UXDPWua0ci5xG5Wqz6ytVpxYJ0CV7EOpGSmok2vmuNmq7uty+ODg4OL/aud9e2rw62t+tXW292ti62rg/3jy4uNj68PPqw1d7dO6u+vttdaW0cfX31Y33rfWtRVf0z51bLw4b/D1FhtAp8OA204GO9jk+YgfrOc67Y/qsIT0curW+7BP6qyheDlVS315R9V01zuN7jAuFX/uNvvxS6v5qR5/9hhxeEb1CzOlkdVEoVWh7cwWKRT3nCnfzizTTfjv4fPpBNPV+u11Zf1tfX15svV1RfN9WZt/pTabNx3Sa6/WK01XqzW54/s2tQjBKE22wWe6fPW5tq6tfkubq3cnp1pwHaZtDDfcy0/LrVZy4/nr7/+7VTv9LrUa6FrlVr2b3zV3aQv6/W1tWa9trbxolFZbzYbL2rN+SLR3x5prbR+tmKcp7gH++bLF+uNWnOuOsjGYBbe6gujS5XcohK9XIzTnYvT89naF73vpHGwc378fuNyf2ejftk6bGycnW+3jk5Ot4+bV6+3t3bPjvbevNu/3N19e3Z4fNXaOz4+q5/5anQC5PoTAbKxurb6LUBmr74Jx4uz7QUwbl+8Pdy92N2+evd243LvstW42mhd1nfXP26fXZ2cXa2dfWhcHK21Tt8fHm+8Ozvd/nDSuDzY+TgDY7NeedHYWGu+rP8YoKYMy5s5OKI0rpquh+PiZTXIaqHvSUi5pAUlDErNc/ncTZz64RR/Z43BRRqzYg+yETIX0U06SenDSeoceQTMXWFHauRyBwRdNLJ3ntGRI3B9bW79vizm2E1damAZnq8LSqIKrjf+06H21Ud+Pd/L+NKAoinZ6lqlVln1CTyOmRlMqCYjhEyRvfPzE9I62SdOE8S2GA88y/QqpFbIviNC9cA6XMaJgRUPnPXUfmViNE9D4KQzWMQiG63DWjabDhSWALMCDIoOtbJpDMVSdgeG9YCUhtKIAemdD8mRJgHjC2MVwoo2ApQDnikyPbBnSWozpQqFXmkDOBwprLe8ZEfHCN4D0gHX9xOLSZJZO73yxGisTvOZuz6TEpwNCIcQT0om/YgjfAkjhoAFnoOPIpLFuteIFLvhNLFpJxaOlMuFgHxOwQxK83rFcF9AtMHRRGAxgTu8AGd6lFcj0+lJv2nP+rt7wnV5Q2+eFeHJ4Q4k1kB26jKYq10NtYEVpTk8/1t5zyf1SRXiQqZIx08lg0Us7wQj4cXpQYBTs0b3LRgvQSsguutRGWN9tv3WPog116GtOq2lrVp+axFpTQygO3luocbWwxfhBsh/oFOD3oaABqSPU82hjmNQHF95oJhCwUQo64BxXBSzWxzr5cJA6PwehkxK6+3029pLBQeSRUwHLIl030PCY6GEdWBI4eLeHQtsUARCTJ4Z6GbO7O3fHlv6E9mSujfBoN/vTxs/plzpSN2rshUF/RWbqhU8hSJYyc+P5xg8xGoMExbe9oxOFcch8JloyHzHhJFwELrUMElEjDEPvnDOdkhYErNftCH50UE6aZw8r5DX2kzNmGfzw7mKCGAub+wamgMOTgckjCC8JUhdth9Fkl2EdgJAT7go7VRCHVdzHIq/hanVjtSdKnZ9q9s773cOjk/2j3YrMX/ut2sLutoAbnwHekIFRLifLOlr4yJiQDjfzcDJdByoB4W9M5ylDyOdjXp7/TAsyZHmfyQREK7DNC4SzCb5+ec+EK6J0n5kXxsLxKRKoRIFULhlWRpiBD2GM4nhUs4SY1/6+ecsAYAf7mdSDjxrv7Z9x6Tg3sD23NkG6PoGiOtrYgHH6B0GjwrBqDypcAh1msgcnxjTsIgTbRxTzjtYR3sYi6vhwK8quVdlyvUxumKmWA9/m4DO1VcBSZgBvsJ1X43dS3enTdWJE7FPeigzX4lJDVOe7hIFwC151oefpCSlyMJZfksY+URfscQfB8juEx1jhy7ia28T2+PuGZg74S/IxSaXd9YTreiuP8qEb8/ibDwLfT8z/9lBoXbZoV9j6GWTW8HMZW/6agcxE/4tSKn/U37nv2CFoCyUZLUSFkZA6hW8gguOvtsVvkzI3qxkbyYS83TC/FtvU87UVg/2X+0cne3gkkrkYunb1Im2LmaqJLJo5WLKnPwCY+riMJz8YuBv8yOVvB5x8MVVE4ljdaMc92FeW1wXzRhst2+WGjM3OI5nHVIMh5gbL4wcjfCxP57p5vVNQO+YEVkb4npIubDT5fm98D87zZsdz8kP+13LQlOLT2IKv+XknX1Ki0KvZK3/NhAB4+im1/lXMfxyAIkrLZ37oQkWNOOabXfnnI5G/wP7rmkV
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Account"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/accounts/{account_id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The single account endpoint provides information on a specific account. The balances section in the response will also list all the trustlines this account has established, including trustlines that haven’t been authorized yet.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./retrieve-an-account.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retrieve-an-account.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retrieve-an-account.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-an-account.mdx b/docs/data/apis/horizon/api-reference/retrieve-an-account.mdx
new file mode 100644
index 000000000..90e5593a3
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/retrieve-an-account.mdx
@@ -0,0 +1,4 @@
+---
+title: Retrieve an Account
+openapi: "openapi/horizon/bundled.yml GET /accounts/{account_id}"
+---
diff --git a/docs/data/apis/horizon/api-reference/retrieve-an-operation.ParamsDetails.json b/docs/data/apis/horizon/api-reference/retrieve-an-operation.ParamsDetails.json
deleted file mode 100644
index 82b3e39ef..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-an-operation.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","required":true,"description":"The ID number for this operation.","schema":{"type":"string","example":121692259040116740}},{"name":"join","in":"query","required":false,"description":"Set to transactions to include the transactions which created each of the operations in the response."}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-an-operation.RequestSchema.json b/docs/data/apis/horizon/api-reference/retrieve-an-operation.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-an-operation.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-an-operation.StatusCodes.json b/docs/data/apis/horizon/api-reference/retrieve-an-operation.StatusCodes.json
deleted file mode 100644
index 2c91590de..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-an-operation.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_links":{"type":"object","properties":{"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"type_i":{"type":"number","example":0},"type":{"type":"string","example":"create_account"}},"title":"Operation"}]},"examples":{"RetrieveAnOperation":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/121692259040116737"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/f92a9648c1084d1de0fd786faac5d5e1637d4127c60841d2366c70d2e7f77b85"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/121692259040116737/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=121692259040116737"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=121692259040116737"}},"id":"121692259040116737","paging_token":"121692259040116737","transaction_successful":true,"source_account":"GBDVKE33GVVMBXX73OHIBRP6RAHKHHW2P4PQVV6UNOKQCOXU7GNUM4QI","type":"manage_offer","type_i":3,"created_at":"2020-02-21T20:10:21Z","transaction_hash":"f92a9648c1084d1de0fd786faac5d5e1637d4127c60841d2366c70d2e7f77b85","amount":"10000.0000000","price":"0.0704336","price_r":{"n":44021,"d":625000},"buying_asset_type":"credit_alphanum4","buying_asset_code":"USD","buying_asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","selling_asset_type":"native","offer_id":161536436}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-an-operation.api.mdx b/docs/data/apis/horizon/api-reference/retrieve-an-operation.api.mdx
deleted file mode 100644
index 0c210dfdd..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-an-operation.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: retrieve-an-operation
-title: "Retrieve an Operation"
-description: "The single operation endpoint provides information about a specific operation."
-sidebar_label: "Retrieve an Operation"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlGWtv27b2rxD8cPuAbMuP2K2BYTdt0iRIm6R59ZEGBkUeWWwkUiMpu1ng/z4cSrLl1O26rRgCLF8ciYfn/dYddWxq6fiKHudgmJNaWXodUAGWG5njMx3T8wSIlWqaAtE1GAElci2VI7nRMynAEqlibbLylEW6cIQRmwOXseSri20a0OXDgaBjegrOSJjBtloyQQOaM8MycGCQvTuqWAZ0TKWgAZXIVM5cQgNq4LdCGhB07EwBmzg/2CGqyCIwJNaGuETadWYsTyBjdHxH3W2ONKwzUk1pQOELy/IU6Ljb6w6f93pbz8NB2O0OR4NwsQiWPH3WUtVc/VaAuV1jK2ap/YqvM3DEaeIMU5Zxr3Z8loqnhQDiElg/myeSJ4QbYA4EAcYTomMPthQF9e/fGLC5VhbadHGNjJRPFgXshSH+3OOl4ByspQHlWjlQDkFYnqeSe8Sdzxbh7hqKYml6HHuzVCrT0WfgDq1mkCEnS3qTVKob21DtN+AspPGfQyUG4k1mKr2OjilSo4uAOsjyFDXVgI60ToEpulg0jXNVIr0OqJMOLb3EoeCLe2As5QZmD4qlBYLVr157U2NY/ByfgDgG7n4A8N+2AQcBD42tBxhAFtOKeGiKamTVB8UZQkmxiVgNJ4X3PzaVajpx+gbU96DX4JDD2xwmsnGjLInNIhdWYN+thLSsQRPGuS6Uo80MsKrei+vF8o7X5KYSP76jM5YWsJ4Uak8udU8T53I77nQSbeTvWrUcWKfAta2DNGWmrc20syqBnfuFuj/aYPS/gLpZhDvx8x57Phw8493w2UB0BYSxGD0bxozxLbEF3WF/JAbd3ogPw2eDruj1h0M+CkUPRvFoFD3bQlYaWe1nSdipcdZBV0XdX8BfYfhVGwHmF2wP/scLY7X5ZbNCm1nwb5Nh36dSBQTdcHY/DDbDNGw3sWWPExdp3SdaXRi+8uMx3Xuxc3m42+/vXV6+efH+/ah/vH/w4vRkeLq9f7i//653Mjh5e3k5vDg6Pnz78vj9xWjv6OLN4O0BraOGZkyxKUx0HPvAqkOuH1RBIyY+afTCXtgKe61e97wXjrvhuNf9eI/dhNmEjuk/driAsqwSrxuGYdgOyz+f6SRHpsN2OAoH/f6wfjcxaFVFx4NB2OsGVNDxsLcVhpgeouIW1c6sBTeppOYGhHQTluYJU0U2oPfAuBYIdnG2c/9EWluAQdXvXBy+2bvY2/n49nD4Yf/D9tbH4faH3t7g/c7Zx5Ozj/2zd1sXR/3t08s3x8O3Z6c77062PrzefU994Uu/YkkxJ2eAcwaaYoJu1B12t/rDQX+4KP8CmoFLNDrYFHzmx3FiTJuhdifFwpMws3oKKUz6Y75ON00i5yUcOQI31+bGN0ubMcaFKwz8CM5XNSRRNdZrnEVi7fN4lZr3S7w0oChKeTtsh+0uyldkGTO3K6jVRMcU2T8/PyHbJwc4ngjmWD1lnJV81VTb5MARqaZgHV4TxEDLK856aH8zN1oUHASJbjehQMwMZ7SMuIQ5Ii0BZiUYJM21skUG9VU2A8OmQBpjCjGQerv7wSoBkoPxhVpxaGkjQeHo5BkxkBuwoFw1OBW2ZKpm6KU20CbnOCmi5A05IiPFFEgEbg6gkHwp7frNE6Oxn7AklTdA5ixNwdmACOCgnGGp/B2HuC88YaiwwGPwDkzKkPAckdoaThNbRJl0ayNhQPyoiSaqchiJWIrCBkQbYp0BlhGYgar5uD9srm62v/Ks/7onXDUNev24Dk8BM0gxQ9i1ulax3eHaQEtpAU/+U97zSX1SNTnOFIkAj8CiLmeSEX5x+jogjERGzy0YT0ErqDcYS12f7RzaP9W10Nx2nNap7VhxY1HTmhhAd/LYuMam84t0t4j/VhcGvQ0VGpA5Lke4zjJQAo+8ophCwkQq64AJvJSxG6mmREgD3Hkbcpam1svpzTotpABSRkwEliR67lUiMqmkdWBI7eLeHWvdIAlUMXlsIC6d2cu/s5T0EXmR6ulKB/P5fF34JWQrSvW0w1oK5i1bqBZWoQRaVf144lddVmOYMH4zNbpQgmh1PxpK3zE8kQ64KwxLicww5iHzlvcWkpZk7LM2pCodJCqy/EmbvNJmw8qvYhEVWNFbuoYWEDELAeEJ8BuC0E35kSTZQ9WuFDCVLimiNtdZp9JD/VuL2olSHXUyJlVnZ/dy9/XxycHRXjsTT7y5XkCsDaDhI5hKFRDpHlky18YlxIB0vtarqecD04D0TABPNIg6v11hWJIjLf5OIiBC8yKrE8yYPH06ByI0UdrhBlUbC8QUSiETtaLQZGUaYgQ9RrAUw6WZJZa+9PRpmQDAL1pZmt561P7uZMZSKbyAk69qG6DrGyBurokFXLY6DB7FwagqqQjgusjTSj8ZpmGZ5do4ppx3sEh7NaaSRTLFiMNbDfdqr7k+RlfZIlsi0bnmKiA5MyBaQs/V0r10vC6qzp3MfNJDmtVNTGqY8nRMFA485PEcHqUpaUSWtIRZwsgn+pLlvhwguk90qTt0EWy8wWT2OD4DMytb4trIa4MgArV07EsZgpXbUsb9krBaBNdsNx36FYZevdNeb/bWWzvImPSnkKb6/82zRUBTyUFZaNDazhlPgPTa2MxLgb4bS99Nlyet8mRFsUonzJ96mSqktvP64OXu0dkuXmknLkv98JVr6zKmGiTrIR5TZnNTv9Y63K22yD//u0HV3zv44jp5yqRfbXgR76oG/mr1bQE32mMpcNeSaOvw7O4OE9CFSRcLfF0u67Gv/6YI/86i/huS3cDt6vNCtSuhvr+fMSNZhK09Mi8t/v+Nbw1NaR6fVouoJ+RHvoxsZKp6ydRtk6maWdxS4fInASbQG6/uqoNtziF3jStffWFAuZZD2d7uOV0s/gCjATkl
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Operation"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/operations/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The single operation endpoint provides information about a specific operation.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./retrieve-an-operation.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retrieve-an-operation.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retrieve-an-operation.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-an-operation.mdx b/docs/data/apis/horizon/api-reference/retrieve-an-operation.mdx
new file mode 100644
index 000000000..d7a7ad98c
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/retrieve-an-operation.mdx
@@ -0,0 +1,4 @@
+---
+title: Retrieve an Operation
+openapi: "openapi/horizon/bundled.yml GET /operations/{id}"
+---
diff --git a/docs/data/apis/horizon/api-reference/retrieve-an-operations-effects.ParamsDetails.json b/docs/data/apis/horizon/api-reference/retrieve-an-operations-effects.ParamsDetails.json
deleted file mode 100644
index 23757d9f8..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-an-operations-effects.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","required":true,"description":"The ID number for this operation.","schema":{"type":"string","example":121692259040116740}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-an-operations-effects.RequestSchema.json b/docs/data/apis/horizon/api-reference/retrieve-an-operations-effects.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-an-operations-effects.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-an-operations-effects.StatusCodes.json b/docs/data/apis/horizon/api-reference/retrieve-an-operations-effects.StatusCodes.json
deleted file mode 100644
index 1327e2c70..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-an-operations-effects.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"operation":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","enum":["Account Created","Account Removed","Account Credited","Account Debited","Account Thresholds Updated","Account Home Domain Updated","Account Flags Updated","Account Inflation Destination Updated","Signer Created","Signer Removed","Signer Updated","Trustline Created","Trustline Removed","Trustline Updated","Trustline Authorized","Trustline Deauthorized","Offer Created","Offer Removed","Offer Updated","Trade","Data Created","Data Removed","Data Updated","Claimable Balance Created","Claimable Balance Claimant Created","Claimable Balance Claimed","Account Sponsorship Created","Account Sponsorship Updated","Account Sponsorship Removed","Trustline Sponsorship Created","Trustline Sponsorship Updated","Trustline Sponsorship Removed","Account Data Sponsorship Created","Account Data Sponsorship Updated","Account Data Sponsorship Removed","Claimable Balance Sponsorship Created","Claimable Balance Sponsorship Updated","Claimable Balance Sponsorship Removed","Account Signer Sponsorship Created","Account Signer Sponsorship Updated","Account Signer Sponsorship Removed","Liquidity Pool Created","Liquidity Pool Removed","Liquidity Pool Revoked","Liquidity Pool Deposited","Liquidity Pool Withdraw","Liquidity Pool Trade","Sequence Bumped"]},"type_i":{"type":"number","example":1},"created_at":{"type":"string"}}}}},"required":["id","paging_token","account","type","type_i","created_at"]}},"title":"Effect"}]},"examples":{"RetrieveAnOperationsEffects":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/121693057904021505/effects?cursor=&limit=10&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/operations/121693057904021505/effects?cursor=121693057904021505-2&limit=10&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/operations/121693057904021505/effects?cursor=121693057904021505-1&limit=10&order=desc"}},"_embedded":{"records":[{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/121693057904021505"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=121693057904021505-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=121693057904021505-1"}},"id":"0121693057904021505-0000000001","paging_token":"121693057904021505-1","account":"GALSPNVKGNRJ3VIOQ26QKPZBDCTVJK7XPLSPF3UVZV3JJXCKVCHNSPCK","type":"account_credited","type_i":2,"created_at":"2020-02-21T20:27:30Z","asset_type":"credit_alphanum4","asset_code":"NODL","asset_issuer":"GB2Y3AWXVROM2BHFQKQPTWKIOI3TZEBBD3LTKTVQTKEPXGOBE742NODL","amount":"0.0000027"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/121693057904021505"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=121693057904021505-2"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=121693057904021505-2"}},"id":"0121693057904021505-0000000002","paging_token":"121693057904021505-2","account":"GDQWI6FKB72DPOJE4CGYCFQZKRPQQIOYXRMZ5KEVGXMG6UUTGJMBCASH","type":"account_debited","type_i":3,"created_at":"2020-02-21T20:27:30Z","asset_type":"credit_alphanum4","asset_code":"NODL","asset_issuer":"GB2Y3AWXVROM2BHFQKQPTWKIOI3TZEBBD3LTKTVQTKEPXGOBE742NODL","amount":"0.0000027"}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-an-operations-effects.api.mdx b/docs/data/apis/horizon/api-reference/retrieve-an-operations-effects.api.mdx
deleted file mode 100644
index c7632c70b..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-an-operations-effects.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: retrieve-an-operations-effects
-title: "Retrieve an Operation's Effects"
-description: "This endpoint returns the effects of a specific operation."
-sidebar_label: "Retrieve an Operation's Effects"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlGttSGzn2V1R6mFyqfSXAxlVTu4CBOBAw4JAMCUXk1mm3glrqSGo7LOWq/Y39vf2SraPuttvYEDK7O5uZ4YWydHTuOjqXvqWOjSztfKDHKRjmhFaWXgaUgw2NSPE37dBBLCwBxVMtlCMGXGaUJS4GAlEEobNER4QRm0IoIhESXeKq04DOfvQ47dBTcEbAGLbUnOBujoQGNGWGJeDAIEu3VLEEaIcKTgMqkJGUuZgG1MCXTBjgtONMBsvcAul1icqSIRgSaUMc8r/AlA1jSBjt3FJ3kyIN64xQIxpQ+MqSVALttNqtjZft9vrL5otmq7Wx+aI5nQYznsLMWG1Kvr5kYG4WGIuYtEucbZVMuZg54rVpidNV1UkdeiaJUISRUEsJof+tI2LAplpZsIQpToQlaSYlcBIZnXhrpGwk1OjK6WtQZMxkBrlhDITa8JVyC+VgBKYq+MZGc2Ojtfli8y8v11+2mutVsbXh8P1Sc7BipFgpB7LqEaGQk1iEccGhJTbWmeSEpSkwUyfHHoclQoUy40A+MRt+Ik+ZDUFxoUbPiDbkE5L7RJ7iv2K5TnpRbnVmRlkCyhFh1b/+8U9HLLiACEc4RCyTuf492m+4hcoSvCbMhjQXkF5WFSNFItx3KgYdNWFfRZIlpWN4K+eqyK8Z8DpBOI+fhEwRw9QIcpu3kPl2s0lqhCmSpSmYAtA7mLAkZoaHmgNHVb/SRvxdK38lUjCRNglTIRADzGplH1BaaUDgS7prNR/rV63mdHqJSim8GKHbzSb+W9TLWRaGYDEehFo5UA5BWJpKkd+NxmeLcLcVqkzK48jHjIK+Hn6GEA2SGrz4TuT0rqRQ17bC5z1wFmT0bajYQLTKWbxmnfcKdU2nAXWQpBLVV4Eeai2BKTqdVh3lQ470MqBOOAkVHAq+uh+MpdTA+IdiaYpg5dKhNzXe0W/4BCRD4HyB7D2gxd2sADJjGF514SB5hF891v9mj9UPpd6AWryawB8hwW/tiCFw+LHYQijBVxEr4QT3zFde7YegF+CmAWVhqDPlVh1JmXNgMJbuf9iqXTRrLy9v19enFWSMc4MxFiX1h+9/8rZyOmTHgNdHMFs5hUSPF1Z2DHCxCNSF4Z2VQWzAxlpyS96m/A7OVzoB0tUJE2rF7p5ko1WneiqSeX7RBetEkWvM4c7ESIGpiFAszCUoFuZHBiazTgoFlVPztfnB+dqqs1uZi/HZvbPcBVbdOI6iBe7y33Ma+e8qfsaBBrTLHKsc8z/np/zP+aEdyUTChhLINpP+4Z+fXLHnVxbMfg/QgiHO8G3XxsYiXeEw1d1lI1Z3V+l3Ne7V+6tssRr/zE9RWw+zvwSyLMMSyJzQsvpWU3sY7iF7Pixg4eHfsNAy0ApDLQPNyR2KL5ngwt2QvtayQuLOxr0nTmGsr1dtdCHVVqxE9k64mBs2Wd4pr8oZfMkAlbSdJSlwellEvitRiX15Fr6QtE4DGuYiXLEVsXaa5xzV18CXqwvBeh6ri2g7I72A/LKaveRFMZ0inwU3/gF7qIDu3FJf9S1mGmUumz99NHYutZ1GI86rgZoD6xS4unUgJTN1bUaNWfphG74MXmuub2Id3G6tN9cbRdH/17wG/vknX3L83Gr+5Iu6n7FEquSr/yuyyxC19j2slHnqb8hK6y4rvmREAy+km7OE8kPVYgvZ33+L6bvp23fgLcWdS/LTA5LfTch+NSH2LTpFgkWbK7ab5V/r7m3s0JXYKgkV3d86POsfnR/sH52+XjvvHZ+0N04O+hfb3Z3B+euDzff9w7P+3trb84vztdev3+8cnO+8Ojrr7xyU97tT4roK5wlRGW3aixGFtpvtZq3ZrrVbg3az097srDUvkBtrwV0V6HI0V0ymMVNZ8mK2j8U97dCj4+7hbE1Ym4FBMbbbv6xtvXt/fnr8pr39au/k4KQ/eHfQO+6tDS52t7e7a4eDg8H5yeBgt/9+/3h7d/NFu8SUFKpo1r0W25u+kvqD+Gj7N/LR9iN9tP0oH20v+mj35F1vY+9ge7Pd7R+/3n2xs//Lzt7JxcFp/+Skd/zL+9M3F+sHu+f779/sb7x9O9h//WZ7Z+vs1bKP8lmGXrro2u/VRS+nxV9AE3CxRs2PwOUlUUw7tOp/t4JPS3NiDwvMuOw8Z0Y+zh3oqqbeIIcjR+Am2lz7m7MaY5S5zMBjcO6VkESVWC+x3Rhpn5QUWUPR4qMBRVHy0816s47hzWZJwszNHIqkRo8F9/1k8mow6JOtfg97ehyTWKF8o/Ys56ukWic9R4QagXV5G9pAzSsunwf4k6nRPAuBk+HNKhR5axsL7lmbEpgV2BbXJNTKZgmUR9kYDBsBqXT/iAEs9caA4L7rPW9l1rQRoBzwnBEDqQELyuUGJ5nNmSoZ2tEGsL0qrJe8IsfQCD4CMgQ3AVBIPpd28WTf6M9+/CHFNZAJkxKcDQiHEJQzTGJ1R+BrGGPL1gYeg/d/kvu/52jWlnWa2Gzou7eGKct8398GxHeT0UTFfSXDPN0PsPltnQGWEBiDKvmonvbThdnJ+pJn/dk94UPVoJdPy+vJYQwSI4VdCP0F241QG6gpzeHZn8p7PqqPqiSHk4gh4BZY1OVYMBK+PT0MCCNDoycWjKegFZQjn5muz7oH9pu65jq0Dae1tA3Lry1qWhMD6E4eW6ixJPqKdZ6OyI3ODHobKjQgE/BTlCQBxXHLK4opJEyEsg4Yx0MJuxZqRLgwEDpvw5BJab2c3qyjTHAg+Y0ZgiWxnniV8EQoYR0YUrq4d8dSN0jC1+NPDUS5M3v5uzNJn5BtqUdzHUwmk0XhZ5C1odSjBqspmNRspmr4CsVQK96PZ36WY7FlNmTh9cjoTHGi1d3bkPuOCWPhIHSZYZKIBO88JN7yuhj8JOyzNqR4OsgwS9JndbKncVCXN0hxmQ11hjMgzyIqsKA3cw3NYcgsBCSMIbwmCF2V30+W9lG1cwWMhIuzYT3USaPQQ/m/FLUxlHrYwLZgo7t7vnt43O8d7dcT/sybaxsibQANP4SRUDilemLJRBuHs0Xh/JuvRp4PDAPCMwFhrPPRmOcPryU50vzXBALCdehnZl5HHfL8+QQI10Rph5NzbSwQkymFTJSKQpPlYYgR9BjOJF6XapSY+dLz53kAAD8pZlLeeNT+7NWYScG9gFdLbxug6xsgbqKJBRywO7w8KgSjiqDCIdRZKgv9JBiGRZJq47D9hw421F6NUrChkHjj8FTFveoLro+3K2GKjcASgc41UQFJmQFe43qiZu6lo0VRdepE4oMe0ixOYlDDkKcjorAqIE8n8ERKUrlZOLC0hJGPdIel/jlAdB/pTHfoIpjcgknscXQGZixCqCRjVct6oJqO/FOGYPkQkoW+l1EMe0u2qw69h1cvL4iCO8neYmoHCRN+F6TUf6vuTQMqRQjKQoXWVsrCGEi73sQpE0ffjYRPnfOdWr4zp1iEE+Z3vUwFUts47O3sHp3t4pF67BLpq5NUW5cwVSFZtpgwZM6aTE8smX+nsZBE3M7HtP/ZlyJFIeHgq2ukkgk/5fCC3Rbp+4d52YlsdHyrrczgLwMaa+sQ6vYWA9BbI6dTXM7n8ZjXc2GxY3rPRL4qyf//W42V6riGm+rXJ0W7j/oS43uE+918kvGAFsqPUX6lEv5An188oKTyw5S5ki7xhxGope+8E09Pizb3M/KYj6xWclX2HtRNlamSW5yIYsc7Boa2Rfbyja0whLQqx9L3ICjXrObf3x3Q6fTfGydo8g==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Operation's Effects"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/operations/{id}/effects"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint returns the effects of a specific operation.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./retrieve-an-operations-effects.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retrieve-an-operations-effects.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retrieve-an-operations-effects.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-an-operations-effects.mdx b/docs/data/apis/horizon/api-reference/retrieve-an-operations-effects.mdx
new file mode 100644
index 000000000..e71d9b4fd
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/retrieve-an-operations-effects.mdx
@@ -0,0 +1,4 @@
+---
+title: "Retrieve an Operation's Effects"
+openapi: "openapi/horizon/bundled.yml GET /operations/{id}/effects"
+---
diff --git a/docs/data/apis/horizon/api-reference/retrieve-an-order-book.ParamsDetails.json b/docs/data/apis/horizon/api-reference/retrieve-an-order-book.ParamsDetails.json
deleted file mode 100644
index e411bb455..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-an-order-book.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"selling_asset_type","in":"query","required":true,"description":"The type for the asset being sold (base asset). Either `native`, `credit_alphanum4`, or `credit_alphanum12`.","schema":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]}},{"name":"selling_asset_issuer","in":"query","required":false,"description":"The Stellar address of the issuer of the asset being sold (base asset). Required if the `selling_asset_type` is not `native`.","schema":{"type":"string","example":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}},{"name":"selling_asset_code","in":"query","required":false,"description":"The code for the asset being sold (base asset). Required if the `selling_asset_type` is not `native`.","schema":{"type":"string","example":"USD"}},{"name":"buying_asset_type","in":"query","required":false,"description":"The type for the asset being bought (counter asset). Either `native`, `credit_alphanum4`, or `credit_alphanum12`.","schema":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]}},{"name":"buying_asset_issuer","in":"query","required":false,"description":"The Stellar address of the issuer of the asset being bought (counter asset). Required if the `buying_asset_type` is not `native`.","schema":{"type":"string","example":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}},{"name":"buying_asset_code","in":"query","required":false,"description":"The code for the asset being bought (counter asset). Required if the `buying_asset_type` is not `native`.","schema":{"type":"string","example":"EUR"}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 — an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 20 for order books.","schema":{"type":"integer","example":20}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-an-order-book.RequestSchema.json b/docs/data/apis/horizon/api-reference/retrieve-an-order-book.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-an-order-book.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-an-order-book.StatusCodes.json b/docs/data/apis/horizon/api-reference/retrieve-an-order-book.StatusCodes.json
deleted file mode 100644
index 1010e05cf..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-an-order-book.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"bids":{"type":"array","items":{"type":"object","properties":{"price_r":{"type":"object","properties":{"n":{"type":"integer"},"d":{"type":"integer"}}},"price":{"type":"string"},"amount":{"type":"string"}}}},"asks":{"type":"array","items":{"type":"object","properties":{"price_r":{"type":"object","properties":{"n":{"type":"integer"},"d":{"type":"integer"}}},"price":{"type":"string"},"amount":{"type":"string"}}}},"base":{"type":"object","properties":{"asset_type":{"type":"string"}}},"counter":{"type":"object","properties":{"asset_type":{"type":"string"},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}}}},"title":"OrderBook"},"examples":{"RetrieveAnOrderBook":{"value":{"bids":[{"price_r":{"n":10000000,"d":139999999},"price":"0.0714286","amount":"24.9999990"},{"price_r":{"n":1,"d":14},"price":"0.0714286","amount":"188.0000000"},{"price_r":{"n":1,"d":15},"price":"0.0666667","amount":"230.3200000"},{"price_r":{"n":1,"d":16},"price":"0.0625000","amount":"50.0000000"}],"asks":[{"price_r":{"n":5000000,"d":62500001},"price":"0.0800000","amount":"4.9400001"},{"price_r":{"n":10000000,"d":125000001},"price":"0.0800000","amount":"2516.5154327"},{"price_r":{"n":2,"d":25},"price":"0.0800000","amount":"3125.0000000"},{"price_r":{"n":4,"d":49},"price":"0.0816327","amount":"4593.7500000"}],"base":{"asset_type":"native"},"counter":{"asset_type":"credit_alphanum4","asset_code":"BB1","asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN"}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-an-order-book.api.mdx b/docs/data/apis/horizon/api-reference/retrieve-an-order-book.api.mdx
deleted file mode 100644
index 74298c952..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-an-order-book.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: retrieve-an-order-book
-title: "Retrieve an Order Book"
-description: "The order book endpoint provides an order book's bids and asks and can be used in [streaming](https://developers.stellar.org/docs/data/apis/horizon/api-reference/structure/streaming) mode."
-sidebar_label: "Retrieve an Order Book"
-hide_title: true
-hide_table_of_contents: true
-api: eJztGe1SGznyVVT6cYHUeGz8QRJvpW4hEAIhCYshIWAqyKO2rTAjzUoaDEu5ah/i/tzr7ZNctTRjjz9YqGQ3udpdV1HYUnerP9Wt7ltq2cDQ9hl9pzlosqnUpaHnAeVgIi1SK5SkbXo0BKIcQE+pSwKSp0pIS1KtrgQHQ5gs7T8ypCc4LnLCzKX/EjFJekAyA5wISc6M1cASIQfnK0NrU9OuVjlcQaxS0CY0FuKY6VDpQZWryFQ5s6zKUmGqQ6XFL0rij4qGPmiQEVSN1VlkM+2+ecKrJFEcwq7syg9DkKQvYgtayAHpK00YMSlEoi+iEucBuVEZSTJjkVH3x+KYGHFNVJ/YIeCCHmQJSGva5KLHDHxixoD9ZG9SuAhmloQxGei5xUhxBxepTFrQc9izqxMCqMC5PUcnJLuOLYIHEKVJDkMcDBGGnOy/8UIpGd8QCcCJVURILiJmweF6WOSAMEMuJLPiCi7cmVwRqewEjYMRA1ngIQd4Jn73nIZdSQOKFmToOLuctukhWC3gCjak8zB0MBrQlGmWgAWNvndLJUuAtqmBOBZyUNIJDahAB/w5A31DA6rh50xo4LRtdQbL3NTJ0c/Z8qL1AI1uVMzJilOUW14NybawQ9ATkVH/Griwn1icDpnMkuZFgBLOL6/VL0IaUBMNIWG0fUsdq21qLLoXDSjILMGg8oRpQOfpLi6t1en5eBzcoQuv37u10WexWaqOjg8kwjjXYEzuxrm9il/3qOkwP4YID36xaKcL9DV0lUKX9+jnmiVpjEs7W8ev3+wc72yd/vR6/eOrjxut0/WNj/Wd5slW5/Sgc9rofGgdv21sHL5/8279p87h1oeD1sf97RN6t67QL79AU86dH+g4f6ZGjjtbM8L1spuHxsSdst0ZFD2VDYaWrMzcG//nkTGjkG8XGHepasEXFgz2fYNjhp0/Oja+g1K2jw9n5ItFIuwXyJSwa5FkCZFZ0vMW1xApzQ3RYDMtgYcE4Rx9V75oJgdA+lolZA3TYb1WI7/9+h8sfrI0BZ2D2iFzqXfINEfFuXrnla9anBJT0H2lEyYjIBqYUdLkiVyYSXlBhJG//fpfO026PCACf/ZZFlvjGXD0pvWLWapEIS0MXJBMtFivjcfnAb2umCxNlbamMimbitSqwaRKGjBIqV6r4b9ZLXayKAJjMGKVtCAtgrA0jbG2EEpWPxuEu13kSPU+Q4RGSzVWC1b4U7BqLEExrRkaU1hIzP3YqRYRfNL3A8oluhkHlC9bHo8DT3jRKccBZQn6/ZIth4e1719IHMyA93NTylPL6KCvuKviKykFtHSh3b2dp4clF0rKrAWNbrxztlE5rVWend+2WmMaUCusu2jyzJBLX6xOq9jxJJ4cu8sK3fYtvWJxBlPnPpsxrKTttZr/OIOtNZ75z9RMtBbWnqw160/X6dRAtN4MPWCN4lU4R9LTat5HZO3p0zA//W4qrVkq6/h5MsNKoxY26vdQWZ+jUm8heIlKqzZl5bwInQVltUq68jRqa7OUn3oaJcrN8FnTAS7jbkb5nuD9FOuttfWwtdZqNupPlhCtO2r11n1kGmv11u/ov+nINOdc4enaOp5alq/1rBE+aU11V8RpOX6Kems2/mYglhRi5RCjm5trdD6s6M5Wa2/91f7L1vr6+klz43T/6OXRyf7H5vpeq/PhyfbJ4evN/e2PB3sHjUan0Xhzcrrzfv3Fh5dvXVD5wLqu4AGdIpDObmnMMAvRzhDiGPOZyrQTP8p0TIpmQd4GqFgwVoKd6Ri4hPgJE+K/u92uXCzOn3t1/At3FyqT5/OaWARDjp8fd7ZeLG551Tzf2Widdrb3Pm42nuwdvmhtvH+xu9F68+6gefjq6E2j0Tqpv945aey+ere3cXDQOtxuNF83X5++f+sIujriebMrnVvk6thjV6zjsi8NaMx6ENM2/TEXu5r/rxh+WVbZFdNFpdvhl+Q5yQujle5S1C5d/aErEcmAvgJNnhMJoxKFMK9jwo7bX+lKQrr0ATbp0qArkTiaA1ERM3SGQjs5QmT+sA3UaOhttbIa3A2ToyMvm5tr7qzi95d66ISIP3fV8RuxOF7xX+0Q5Eo/kxFWOmQFq6VVcutRIiWNiiGM1cBv/IDr44KGjYYlTNB6ARG0Vtrt5Jg/oC+cY8KxII1Q0kfKJdzQ9vIqLigyD1ZziJqAHSrsyAzA+vw3pG1aihX0G2caTzvT6GAPMC1dVl0feTjyFuxI6UvnyMsp9jNs2z2E5ssCksiC6jnW/X3lEnyeoHMPRQWANh67FtZCvL1MliRM30yhZjqYr46ODsjGwa5rdTHLsG63padifmpIdi0RcgDG+tamhopTnHHQDjPVimcRcNK7WUYCKTOs3ZPJawGYEaDxaHSCLIEClV2BZgMgpcKaaIhdUCA4wpReFBWlBUgL3DOiIdVgQFqHaHz/tXczYeiF0oDvHGGc5CU5elrwAZAe2BGAxOO9tLOYB1ph8WZILC6BjFgcgzUB4RCBtJrF4hfgBK6jIb6dTJD3hH1zEi9Kx9HkdWQVMVnPPaI0k4a5EDEBcc86NBGLXPoiPRajsK4H4X2ewBU2ZT0fZWwkOsUMFzzr7+4JZ2WD3tuMz9muRkpDRSoOq38r78H8VRyXTzSYewQDJ1eCkej4cD8gjPS0GhnQ7gQloegnTXTd2XptHjb4sErFpmr4pUFNK6IB3SlvwGPNdC3sDdK/UZlGb0OFBmQErp2RJCC56/+7WYbEg4mQxgLjiJSwS2zjcKEhss6GmOKMk9OZdZAJDsRHTA8MGaqRUwlPhBTGtXxyF3fuWOgGj3D9jRU3oim882xrIukjshmr0vBnNBrNCj+BrPRiNaiyioRRxWSyglloCJU8f6y6FohRGCYsuhxolUlOlJyPBu87OhoKCzgoYjERCcY8uGGOt5AwJGGflSZ56iC9LElXQ/JSaYJ5Ric+6lhPZdiKcSyiAvPzJq6hOGAZHpBoCNElQeiy/K7Bs4OqnSpgIOww64WRSqrzlVkx8urFqldNmJDVre332/vvDnbf7oQJX3Xm2oS+0oCG78FASGwWPTJkpLQdEg3CuqGMHDg+8BoQjgmIhsp3qBx/GJbkreJfchEQriLXunI6apPHj0dQTJBAcqUNEJ1JiUwUikKT+WuIEfQYzmIMl/ItMfGlx4/9BQBucMdinGcp63E/XbFYcCfgp4Xc5qd2QOxIEQM4erIYPDICLfNLhUOksjTO9ZPgNSwSLKmYtM7BesqpMRasJ2KMOMQquVc44/oYXQmTbACGCHSukQxIyjTwClcjOXEv1Z8VVaVWJO7SwzNzTLzU8MpTfTeIM2RlBI/imJQiC/uGhjDSpS9Y6tIBkuvSie5W/WjOgk7Muz4W7/5FWRi5bFkHVFF9l8oQzPf3WOQ6Q3nXtWC77NAvMfSc8WkwV+zNlnaQMOF2IY7Vj+W9cUBjEYH0L9j8rI2URUMg9RCfz4Kj7/aFe376nYrfmZ6YXyfM7TqZcqKmur/7YvttZxtRwqFNYuo6YsrYhMnSkUUzB6/M6WR8vna4nTY+/xmR/zMif/iIPG+5WLi21TRmAh/63n9v84fZGS09zM4DOlTG4urtLcpxrOPxGJf9vAOfa1wY1ovvmniUPXWlGM6skm88MF8qtn/DLh395y9Y6l6PDxfwe8+9HyzmZHj5FYJ+i7H1gwXKx4tfIc63nlT/jmjLBu/f0iP/4NnqQyX9U53yO8n09X75l50W/44Ki8n6VG3n+EML1Bttn52PAzoExrEUmzQjN6II0jLWwkB4phm5s31Ex+P/AdHJGfg=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Order Book"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/order_book"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The order book endpoint provides an order book's bids and asks and can be used in [streaming](https://developers.stellar.org/docs/data/apis/horizon/api-reference/structure/streaming) mode.
-
-When filtering for a specific order book, you must use use all six of these arguments: `base_asset_type`, `base_asset_issuer`, `base_asset_code`, `counter_asset_type`, `counter_asset_issuer`, and `counter_asset_code`. If the base or counter asset is XLM, you only need to indicate the asset type as `native` and do not need to designate the code or the issuer.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./retrieve-an-order-book.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retrieve-an-order-book.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retrieve-an-order-book.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-an-order-book.mdx b/docs/data/apis/horizon/api-reference/retrieve-an-order-book.mdx
new file mode 100644
index 000000000..db0ed175c
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/retrieve-an-order-book.mdx
@@ -0,0 +1,12 @@
+---
+title: Retrieve an Order Book
+openapi: "openapi/horizon/bundled.yml GET /order_book"
+---
+
+<Tip>
+
+**Supports Streaming**
+
+This endpoint supports streaming. To read more about this, visit the [streaming section](/docs/data/apis/horizon/api-reference/structure/streaming).
+
+</Tip>
diff --git a/docs/data/apis/horizon/api-reference/retrieve-fee-stats.RequestSchema.json b/docs/data/apis/horizon/api-reference/retrieve-fee-stats.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-fee-stats.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-fee-stats.StatusCodes.json b/docs/data/apis/horizon/api-reference/retrieve-fee-stats.StatusCodes.json
deleted file mode 100644
index 805020a42..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-fee-stats.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"last_ledger":{"type":"string","description":"The last ledger's sequence number."},"last_ledger_base_fee":{"type":"string","description":"The base fee as defined in the last ledger."},"ledger_capacity_usage":{"type":"string","description":"The average capacity usage over the last 5 ledgers (0 is no usage, 1.0 is completely full ledgers)."},"fee_charged":{"allOf":[{"description":"Information about the fee charged for transactions in the last 5 ledgers."},{"allOf":[{"type":"object","properties":{"max":{"type":"string"},"min":{"type":"string"},"mode":{"type":"string"},"p10":{"type":"string"},"p20":{"type":"string"},"p30":{"type":"string"},"p40":{"type":"string"},"p50":{"type":"string"},"p60":{"type":"string"},"p70":{"type":"string"},"p80":{"type":"string"},"p90":{"type":"string"},"p95":{"type":"string"},"p99":{"type":"string"}},"title":"BaseFeeDistribution"},{"type":"object","properties":{"max":{"description":"Maximum (highest) fee charged over the last 5 ledgers."},"min":{"description":"Minimum (lowest) fee charged over the last 5 ledgers."},"mode":{"description":"Mode (middle) fee charged over the last 5 ledgers."},"p10":{"description":"10th percentile fee charged over the last 5 ledgers."},"p20":{"description":"20th percentile fee charged over the last 5 ledgers."},"p30":{"description":"30th percentile fee charged over the last 5 ledgers."},"p40":{"description":"40th percentile fee charged over the last 5 ledgers."},"p50":{"description":"50th percentile fee charged over the last 5 ledgers."},"p60":{"description":"60th percentile fee charged over the last 5 ledgers."},"p70":{"description":"70th percentile fee charged over the last 5 ledgers."},"p80":{"description":"80th percentile fee charged over the last 5 ledgers."},"p90":{"description":"90th percentile fee charged over the last 5 ledgers."},"p95":{"description":"95th percentile fee charged over the last 5 ledgers."},"p99":{"description":"99th percentile fee charged over the last 5 ledgers."}}}],"title":"ChargedFeeDistribution"}]},"max_fee":{"allOf":[{"description":"Information about max fee bid for transactions over the last 5 ledgers."},{"allOf":[{"type":"object","properties":{"max":{"type":"string"},"min":{"type":"string"},"mode":{"type":"string"},"p10":{"type":"string"},"p20":{"type":"string"},"p30":{"type":"string"},"p40":{"type":"string"},"p50":{"type":"string"},"p60":{"type":"string"},"p70":{"type":"string"},"p80":{"type":"string"},"p90":{"type":"string"},"p95":{"type":"string"},"p99":{"type":"string"}},"title":"BaseFeeDistribution"},{"type":"object","properties":{"max":{"description":"Maximum (highest) value of the maximum fee bid over the last 5 ledgers."},"min":{"description":"Minimum (lowest) value of the maximum fee bid over the last 5 ledgers."},"mode":{"description":"Mode (middle) value of the maximum fee bid over the last 5 ledgers."},"p10":{"description":"10th percentile value of the maximum fee bid over the last 5 ledgers."},"p20":{"description":"20th percentile value of the maximum fee bid over the last 5 ledgers."},"p30":{"description":"30th percentile value of the maximum fee bid over the last 5 ledgers."},"p40":{"description":"40th percentile value of the maximum fee bid over the last 5 ledgers."},"p50":{"description":"50th percentile value of the maximum fee bid over the last 5 ledgers."},"p60":{"description":"60th percentile value of the maximum fee bid over the last 5 ledgers."},"p70":{"description":"70th percentile value of the maximum fee bid over the last 5 ledgers."},"p80":{"description":"80th percentile value of the maximum fee bid over the last 5 ledgers."},"p90":{"description":"90th percentile value of the maximum fee bid over the last 5 ledgers."},"p95":{"description":"95th percentile value of the maximum fee bid over the last 5 ledgers."},"p99":{"description":"99th percentile value of the maximum fee bid over the last 5 ledgers."}}}],"title":"MaxFeeDistribution"}]}},"title":"FeeStats"},"examples":{"RetrieveFeeStats":{"value":{"last_ledger":"43277313","last_ledger_base_fee":"100","ledger_capacity_usage":"1","fee_charged":{"max":"5500","min":"5000","mode":"5000","p10":"5000","p20":"5000","p30":"5000","p40":"5000","p50":"5001","p60":"5001","p70":"5066","p80":"5066","p90":"5500","p95":"5500","p99":"5500"},"max_fee":{"max":"616065406","min":"5000","mode":"10003","p10":"10000","p20":"10003","p30":"10003","p40":"20005","p50":"20005","p60":"50020","p70":"50020","p80":"150000","p90":"500000","p95":"500000","p99":"1490000"}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-fee-stats.api.mdx b/docs/data/apis/horizon/api-reference/retrieve-fee-stats.api.mdx
deleted file mode 100644
index 8c5127500..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-fee-stats.api.mdx
+++ /dev/null
@@ -1,59 +0,0 @@
----
-id: retrieve-fee-stats
-title: "Retrieve Fee Stats"
-description: "The fee stats endpoint provides information about per-operation fee stats over the last 5 ledgers."
-sidebar_label: "Retrieve Fee Stats"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWVlvGzkS/isFvsQOWocP2bGCASaHk/FsJgnGnn2xDINNltSM2WSHZEv2GPrvi2J3Sy1bmtUqwD7srF9kklUf62IVi/3IAp94NrxmHxDhMvDg2U3CJHrhVBGUNWzIrjKEMSJ4WgY0srDKBCicnSqJHpQZW5dzogae2jJAga5jC3TV3JLXTtFByBA09wEGoFFO0PkuS9iC/EKyIfsdg1M4xQ+IlVAJc+gLazx6Nnxkh/0+/azKeVkKgZ5ohTUBTSASXhRaiYjc++aJ7pF5kWHO6b/wUCAbMpt+QxFYwgpHcgRV7UJS3lYytoh9cMpM2DorRbUqhhcePH4v0QgEU+Ypui6bJ23I25R7vB0jbodN1NGU3IPEsTIoQZmlNSvQapMKX/CCCxUebkvPJ1vuwqfo+ASh4YXIu8lxsNcH5cHYiiyBg26cEDYvNAbUDzAutW7I96N0Y8RbkXE3QRkdpPWXMRteP/XmxbOoCnUc1swwtg6C48ZzQVR+xRyt4Jon7V3+2uU5v39uqHnCcmXWz1u5xrLzhBUH/fXzhxvmjzbMH2+YH2yYP9kwf7ph/tWG+bNN84MN82dr5ucJCypomnrLPR3n94rW0jJ6mTyzlT9WQ+M3fq/yMoe9TE0y9GF/JSw2JpmlG5/AKVPBaTv7z9Bq5z+BsxJhL1dSatweq46XVaiDfsgomQo0QWncHuxwDdjhrmBHa8COdgU7XgN2vCvYYA3YYFewkzVgJ7uCna4BO90V7NUasFe7gp2tATvbGWywBmywK9jZGrCzXcDm85tl4nlXkT/LPTd0gvl9U4G3r0M5v49ypGpNDfoLDf9fhf7Hq9CU6xLBjqP/83q5iZQfL0u7w29Rp3YG36pw7Y6+TSXbHX2b0rY7+ja1bnf0bYrf7ujbVMPd0bcpj7ujb1Mvd0ffpoD+APoWFfUH0LcosTuir9Tc3/j9mnrbysOLxn6eMLzn1C7GTPus8R8+sijQs36cHR8dnp4eHRyxTV01O+j32cZumB2wZ71ozPNsMIh8MSmzQb8axBTajGLOWwwO24Oj9uC4PRjUA9o3Hq/F4LQanJywOngXg7P+Up4YGsvBWTNYvcZUKpwcnPRPBsf9kw16HPT7/aOFIjRaarJYO1oZRV0O+/3+YKHMYtRoc9hvqVOPoj4Hg2aLs8YkbZ2WQ9Lq4Pgsjuf1X8LuO8JKvGzC5JpCwUzYkP3Kp/wyxnKMghQ1G7KffUCtuevVvx0v71jCvC2dIOWn3MFltXQp7+AncPi9VA73RmtZR2z/9cgQk0dH4f8TGJy1ELq/WKf+tKZ7Gdf3RgZgxLIQCj/s9bJqsRPQB4OhWyN3rZuMWDIyBD4yFTRxdsd16O/tx2HI0OyNSxPvl7BHz2D78EhLAMIabzV2tZ1UC69pfl4xCh5E1uJE554xonPWxZWa8/WITmrCcgyZpZe4CcbrEA8ZG7IenRdfP8hVIlfuKB0ZfguV1z46XVV08BnDzLq7eCFbjzguQ+lwG8wPDSWYBvUmYfRUGS+IdRqqPccSRqpU3P1uv0vH0pd5zt3Dkmr54skN/HJ19RXefL2AYEHywJvHpzosml27cBFAmQn6QGwSHHai4XykjpyFs7IUKCF9WAdByJwajRxCxgO9ryH3ivKwjY4sc2xYm+e71qsnONQ8qCkSOdEU6GJHYwR2rFNoAspKEIeFQ48m8KqXKX0lVCPQO+uwC1eZ8lHzlh6pU3KCkGKYIRravtJ2lfOrs3S99qDVHcKMa43BJyCRSo/jWv2JEvBeZJwMlkQE7j2Szr6k98bSIzTeCBZ8meYqrDRgCXwv0T2Qi7gQtjQBUq5J2QSsAx8c8hxwiqaRY6V9C7bF2X0WWX/3SLhuO/RmrzmeEqeoqWHy7XPZq8XuCeuwY6zE/b9V9FBeb7YT3ECKtISebDlVHMQfv39KgEPq7MyjiztYs7h6LWx9+f4f/t/aWlrhe8Fa7Xte3nmytAWHFE4RrXqSv6cnfTuGB1s6ijYyaAIzBIfC5jkaSUvRUNzQxqCMD8glMeX8TpkJSOVQhOhDwbX2Uc/o1kmpJEJ1YlL0kNlZNInMlVE+oIMmxGM4NrahLcjEVNzGVTBH/d8vNH0Bb7WdLG0wm81WlV9QdlJtJz3eMTjr+NJ0qApl2Knrx358r/GWjgkXdxNnSyPBmqenoYodJzIVUITScQ0qpzOPefR89JDykPNv1kFdOiAt82K/Cx+sW/NJrBaRDFjvtwgNK5EurQmIDMUdNJ86Gv1pS/hIpl0aYKJCVqZdYfPe0xtLrWov1Tbt5VyZ3vvzf55/+vL14vPHbi73o7ve4tg6JMenOFEmARVeeJhZFzJwqEL8FmcmUQ5KAyoKgSKzy69O13Qs4bOVuyQCkFaUeZNghvDy5QxBWjA20BdG6zyCK40hIRpDkcuqNMTpe6KRXNNxaWeJRSy9fFklAPQFCsW1fojQkfd2yrWSUcHbZ7UNKfQdQphZ8FhwxwMdHiPQmTqpSBS2LHRtn5zSsMoL6wI3IQZYaqMZteKp0nTiiKsVXt2V0KfTlXPDJ/QplYJrZhIouEPZkXZmFuFlx6uq2iKoPCY92rPmpKRGKc+OwSBKD3szfKE1tE6W8vQJkcOIveNFLAcEN2IL21GIsIQFdLn/MqZLrYr35sbJbc9Goo4dx1JGZNXHVy7ix1fDc2JsxG4H9Ac6etH5LHly2Vu92mHOVVxFre3P7TX60qkEGo+tvd4UXGQIh13qJ5Sk2B2r2C9WK51qZbljnU54XI061aC+9+ni3fnny3Ni6WYh1/ElsbA+5Ny0tmx6Vlh+Q39yb3hcfpH+73xNr58zA96HXqG5okfOSufH+i5/zZZ3+ZuEZdYHmnx8pFT0h9PzOU3HasiG1zcJdU2Kp3RrvqaX8wy5JLNeP7I7pEvyGyEwtmF1u/78y/tKX/Hx/IrN5/8CO48iXw==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Fee Stats"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/fee_stats"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The fee stats endpoint provides information about per-operation fee stats over the last 5 ledgers.
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retrieve-fee-stats.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retrieve-fee-stats.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-fee-stats.mdx b/docs/data/apis/horizon/api-reference/retrieve-fee-stats.mdx
new file mode 100644
index 000000000..4e5130390
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/retrieve-fee-stats.mdx
@@ -0,0 +1,4 @@
+---
+title: Retrieve Fee Stats
+openapi: "openapi/horizon/bundled.yml GET /fee_stats"
+---
diff --git a/docs/data/apis/horizon/api-reference/retrieve-related-effects.ParamsDetails.json b/docs/data/apis/horizon/api-reference/retrieve-related-effects.ParamsDetails.json
deleted file mode 100644
index d3fefe55c..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-related-effects.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"liquidity_pool_id","in":"path","required":true,"description":"A unique identifier for this liquidity pool."},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-related-effects.RequestSchema.json b/docs/data/apis/horizon/api-reference/retrieve-related-effects.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-related-effects.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-related-effects.StatusCodes.json b/docs/data/apis/horizon/api-reference/retrieve-related-effects.StatusCodes.json
deleted file mode 100644
index a1a857f8c..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-related-effects.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"operation":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","enum":["Account Created","Account Removed","Account Credited","Account Debited","Account Thresholds Updated","Account Home Domain Updated","Account Flags Updated","Account Inflation Destination Updated","Signer Created","Signer Removed","Signer Updated","Trustline Created","Trustline Removed","Trustline Updated","Trustline Authorized","Trustline Deauthorized","Offer Created","Offer Removed","Offer Updated","Trade","Data Created","Data Removed","Data Updated","Claimable Balance Created","Claimable Balance Claimant Created","Claimable Balance Claimed","Account Sponsorship Created","Account Sponsorship Updated","Account Sponsorship Removed","Trustline Sponsorship Created","Trustline Sponsorship Updated","Trustline Sponsorship Removed","Account Data Sponsorship Created","Account Data Sponsorship Updated","Account Data Sponsorship Removed","Claimable Balance Sponsorship Created","Claimable Balance Sponsorship Updated","Claimable Balance Sponsorship Removed","Account Signer Sponsorship Created","Account Signer Sponsorship Updated","Account Signer Sponsorship Removed","Liquidity Pool Created","Liquidity Pool Removed","Liquidity Pool Revoked","Liquidity Pool Deposited","Liquidity Pool Withdraw","Liquidity Pool Trade","Sequence Bumped"]},"type_i":{"type":"number","example":1},"created_at":{"type":"string"}}}}},"required":["id","paging_token","account","type","type_i","created_at"]}},"title":"Effect"}]},"examples":{"RetrieveRelatedEffects":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9/effects?cursor=&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9/effects?cursor=120192370561220608&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9/effects?cursor=120192344791343104&order=desc"}},"_embedded":{"records":[{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/3849085266190337"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=3849085266190337-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=3849085266190337-1"}},"id":"0000000012884905986-0000000001","paging_token":"12884905986-2","account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"liquidity_pool_deposited","type_i":81,"created_at":"2021-11-18T03:15:54Z","liquidity_pool":{"id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9","fee_bp":30,"type":"constant_product","total_trustlines":"300","total_shares":"5000","reserves":[{"amount":"1000.0000005","asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"},{"amount":"2000.0000000","asset":"PHP:GBUQWP3BOUZX34TOND2QV7QQ7K7VJTG6VSE7WMLBTMDJLLAW7YKGU6EP"}]},"reserves_deposited":[{"asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","amount":"2378.0000005"},{"asset":"PHP:GBUQWP3BOUZX34TOND2QV7QQ7K7VJTG6VSE7WMLBTMDJLLAW7YKGU6EP","amount":"983.0000005"}],"shares_received":"1000"},{"id":"0000000012884905986-0000000002","paging_token":"12884905986-2","account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"liquidity_pool_withdrew","type_i":82,"created_at":"2021-11-18T03:15:54Z","liquidity_pool":{"id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9","fee_bp":30,"type":"constant_product","total_trustlines":"299","total_shares":"4000","reserves":[{"amount":"7.0000005","asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"},{"amount":"1.0000000","asset":"PHP:GBUQWP3BOUZX34TOND2QV7QQ7K7VJTG6VSE7WMLBTMDJLLAW7YKGU6EP"}]},"reserves_received":[{"asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","amount":"2478.0000005"},{"asset":"PHP:GBUQWP3BOUZX34TOND2QV7QQ7K7VJTG6VSE7WMLBTMDJLLAW7YKGU6EP","amount":"993.0000005"}],"shares_redeemed":"1000"},{"id":"0000000012884905986-0000000003","paging_token":"12884905986-2","account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"liquidity_pool_trade","type_i":83,"created_at":"2021-11-18T03:15:54Z","liquidity_pool":{"id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9","fee_bp":30,"type":"constant_product","total_trustlines":"300","total_shares":"5000","reserves":[{"amount":"1000.0000005","asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"},{"amount":"2000.0000000","asset":"PHP:GBUQWP3BOUZX34TOND2QV7QQ7K7VJTG6VSE7WMLBTMDJLLAW7YKGU6EP"}]},"sold":{"asset":"PHP:GBUQWP3BOUZX34TOND2QV7QQ7K7VJTG6VSE7WMLBTMDJLLAW7YKGU6EP","amount":"983.0000005"},"bought":{"asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","amount":"2378.0000005"}},{"id":"0000000012884905986-0000000004","paging_token":"12884905986-2","account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"liquidity_pool_created","type_i":84,"created_at":"2021-11-18T03:15:54Z","liquidity_pool":{"id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9","fee_bp":30,"type":"constant_product","total_trustlines":"1","total_shares":"0","reserves":[{"amount":"0","asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"},{"amount":"0","asset":"PHP:GBUQWP3BOUZX34TOND2QV7QQ7K7VJTG6VSE7WMLBTMDJLLAW7YKGU6EP"}]}},{"id":"0000000012884905986-0000000005","paging_token":"12884905986-2","account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"liquidity_pool_removed","type_i":85,"created_at":"2021-11-18T03:15:54Z","liquidity_pool_id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9"},{"id":"0000000012884905986-0000000006","paging_token":"12884905986-2","account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"liquidity_pool_revoked","type_i":86,"created_at":"2021-11-18T03:15:54Z","liquidity_pool":{"id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9","fee_bp":30,"type":"constant_product","total_trustlines":"299","total_shares":"4000","reserves":[{"amount":"7.0000005","asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"},{"amount":"1.0000000","asset":"PHP:GBUQWP3BOUZX34TOND2QV7QQ7K7VJTG6VSE7WMLBTMDJLLAW7YKGU6EP"}]},"reserves_revoked":[{"asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","amount":"2478.0000005","claimable_balance_id":"idcbd1234"},{"asset":"PHP:GBUQWP3BOUZX34TOND2QV7QQ7K7VJTG6VSE7WMLBTMDJLLAW7YKGU6EP","amount":"993.0000005","claimable_balance_id":"cbid1235"}],"shares_revoked":"1000"},{"id":"0000000012884905986-0000000007","paging_token":"157639717969326081-1","account":"GBBWI7TEVQBPEUXKYNGI3GBAH7EHFEREONKK3UK56ZSLJIDIYHQJCVSG","type":"trustline_created","type_i":20,"created_at":"2021-08-04T20:01:24Z","asset_type":"liquidity_pool_shares","liquidity_pool_id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9","limit":"1000"},{"id":"0000000012884905986-0000000008","paging_token":"157639717969326081-1","account":"GBBWI7TEVQBPEUXKYNGI3GBAH7EHFEREONKK3UK56ZSLJIDIYHQJCVSG","type":"trustline_updated","type_i":22,"created_at":"2021-08-04T20:01:24Z","asset_type":"liquidity_pool_shares","liquidity_pool_id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9","limit":"2000"},{"id":"0000000012884905986-0000000009","paging_token":"157639717969326081-1","account":"GBBWI7TEVQBPEUXKYNGI3GBAH7EHFEREONKK3UK56ZSLJIDIYHQJCVSG","type":"trustline_removed","type_i":21,"created_at":"2021-08-04T20:01:24Z","asset_type":"liquidity_pool_shares","liquidity_pool_id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9","limit":"0.0000000"}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-related-effects.api.mdx b/docs/data/apis/horizon/api-reference/retrieve-related-effects.api.mdx
deleted file mode 100644
index 756b0a637..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-related-effects.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: retrieve-related-effects
-title: "Retrieve Related Effects"
-description: "This endpoint represents effects referencing a given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new effects referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known effect unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream effects created since your request time."
-sidebar_label: "Retrieve Related Effects"
-hide_title: true
-hide_table_of_contents: true
-api: eJztW+ly2zi2fhUUf0wnXZJMarVUNTVXXuK1bceSk0nSLjdIHElokwAbAK34ulR1X2Neb55k6oCLKIt27L7tSTI9/uMSCODsBwfAhzvH0Kl2Bp+cY/5bwhk3t+RMylA7lzWHgQ4Ujw2Xwhk44xnXBASLJReGKIgVaBBGE5hMIDCaKJiAAhFwMSWUTPkNCBIWs8ZShoQKRgIqiA8k0cAIF0QbBTTCMZFk0CCjld+EhqGca3IrE2IkCbk2IMhEKiJgXknZIJv3yWpiZnBLqAJCGQOGc5kZkJGBMKSKhMCmoBrkYEICGoZVnNXIvlT8f6Ugcx6GRBuqDKHGTgNUhRy0IddCzkXGFklECFoTSoJEaakI10SDqeHU8xkPZiSgGgg35QknSkbEzKjJBjXI1i2OMqlokM91Q8MEUAoh5zWrHVRrynGhlkABNcCI5iIA7KSIgt8SZNTwCBpOzZExKIoGPmDOwDkHozjcwDmEOHA3ncepOTFVNAIDCl3lzhE0AmfgFFq+Qi1fcebUHI6uElMzc2oOEuMKmDMwKoH7/jQkieC/JUA4A2H4hIOyhq0wYMNZ1AqqqQZyUr8loG5XaE1oqCuIiSTyQaW6tS6sUX2U6BgCPuEBCWVgNYH2oSSQYQiB/S0nRIGOpdCgrQdzTeLEeklmLiAxnXIxvTLyGkRmHDkhlCgIpGKoaR3MIKLO4M4xtzHKwYWBKaAg8JlGcQjOoNt1u12v1+5t9jt9z+0sSmJLxeD5UjPQfCpoLgeyaidaOmHKoSZ6JpOQERrHQFWDnNo5NOEiCBMG5Beqg1/IK6oDEIyL6WsiFfkFyf1CXuG/rNnGkDUhVdMkAmEI1+Kf//cPkzm/IQwmNAlT/dtpK9WjjeJiitoRSYQJiurASQV0LsuKCXnEzTMVM54BiehnHiVR7hjWyqkqFJhECWANgv3s/Da8FBVTSG3uIfNN1yV1QgVJ4hhU1tE6GNdkRhULJEtTSZ460L9jUBOpIooxqYBqKfQjSssNCGxNd577VL/y3MXisuZ8ruskjqUyul7ktjw2Cw/HmZqui/9WdTZKggA0ZoNACgPCYBcaxyFP42bjV4397koc0TA8ndiMkfEm/V8hQGPFCjOP4Sm9q5CLa12S4YF+GsLJl3vNFEyqHMlq3ViPEdfOouYYiGKb6Eq9fSlDoMJZLMpO9Cmd9LLmGG5CKM0h4LP5xliKFdx8UywtsFvedGxNjfH7BZ+AyAdcq78sSha3pY5UKYppgBuInuBXT/W/YrX8ptRbczSGJrAnSPDvdsQAGHxbbGEvzqqI5f04s8yXVvTHeq/0W9QcGgQyEaZqSEyNAYW5dO/TsP7Rrfcv7zqdRWkyypjCHIuS2sEPL4fDlA7ZTos8p1a0nEMkb1ZathUwvtppB/x7LeOZAj2TIdPkImb35tyXEZAdGVEuKr6+Cem0atSBmIRp7bED2vCsDln2G/GpAFUSIWtYSpA1LIeMVaJNyAWURi3blgOXbVVjh4mZ4ZJ8r3kHaPnD6WSywl36e0kj/V2enzJwas4ONbQ0zP5cjrI/l4O2Q8oj6odAtmhoi4LlyIpvtmXF7A90WjHECNd2qfSMxxUOU/66bsTy1yr9Vs9d/b3KFtXzF36K2nqc/bUu6zKsdVkSWldfNbXH+z1mz8cFzDz8CxZa71RhqPVOS3Kr2/sSiXsfHhxxDjfyuurDDsRS88rJ3nMzY4rO17/koTLC/SgqaSuJYmDOZZb5rngp96UV+kpBu6g52e72ilbk2kVac5RXA7s7XUnWy1ydZduC9Mrkl+XqJd0SOwvkM+PGLmAP7JwHd47dDK4WGXkZm656zsyYWA82NmbpJqFuQBsBpqHTw4mGVNON1a223uj2ml03aAfeptvzm93mZLLZ8XyXtibgtT2v3+63ur7vNr2O35z0eu12b+Kxief1+5tAfb+/kZ0R/C3dTf/1L3ZX+FfcY5WK2m+IQa/pev1mq+d2ul6z6XbdzVWW86L322O53e71vVa75bntjGW7h0WvWqlxiyr2U9lXVkrOZwhXjNMbrc12393sNLtdr++2Wr37FeMzZs0lXMrxl0zY+0Tq3v0K8HeToY9Tyeo5x83+vOYm9ur0N7t1t2i8H/wDp9yvWUoGA2dvOPx40B5vn7fGHzqnh/vb48Pt5rD9dvShu334/nC/czA8HO8dHZw0d897x1sn745Ot7ffn/TyPLJ2MsZKKTLPbpveagpzmm7Tq3te3dscu62B1xl02h+d2r2pUJFW2v+vs2JxDXDlx86g5RZ8B1JoQ4W5ipVkiS3UjTQ0vDL5cq2dgdNy3eKDnlFlGzuubcVDYXUDqRvTKNOo57puI7VEB1WtNWDz7sX5eLA3POsc745P33U/HOx2mx+GP3W6o/HO8OTsfOe09/HNztbe6GT/8O3Bh729o9FPpx+H+6eno+bI7iELCs0lBbdE4Wz/bLC3dfH2/Vlr6/Ti499b7fHpyU7z7bve27e9o967w/Fe991ot/f+p+Ot8U87h8fHw/e9D0d7F93dszTL5wKVjGhF+0NEqJUEaPU2CxVZ0f4IEUoE+put5fyXNSe13BVGKMcVP7WSJf3leGp+1Xia27oC5uVwan634dTs99fDqf1YOPVeNpa8lw2kpce9SBy1XzqO+g/EEQOInhtHra8aRyarwosgan23QfSnWpO0DG3J+KJLRM3xZTKdmTKhF1rtnhYr7a8aK0GxYy6ipf3dRou3HisPB4r7MtHxR4bE0xyo81UdSBUnK4UDdX6PA139Md7zNJV1v7LK8jOnQmXd7zbm/nxlXmq8l6/yak6QH7pe+emhaxoknAU+85qt9osXgg+yEPgcObhXKmaaeU6l2KuIxE6v2+r3vF6/2281u+6mV/dWA3Jr6/1Bb7z77u3W2e7F348+nOwdtPa2hvu93f03u+e7pydHR62Lo0734+j48GDn4MP+28Ptd6O9ZUAWHlyx/jXdqlh0N+tue9x0B643aNpYtHq/qo7wLBBeKMfVMnDIsxS9+ZUVnRQH+4WiK/e236aim09XdP8rK3p9QW5Wnsl9m4pe7iyw/llkNx7w2YDQeOxr8+413DqDatxPLb+ZQPwPJqcIzEwik1Mw6WX1zBk4a6fkd2tyLfLzWkQjYe7PUIKJCp923utUwbPGaT9yAmYu1bX1qeoZJ4lJFDxlzjd5TyLyWS8RODaR9gopu+PJwFqoIVA6He023AZ6ok6iiKrbZS8SK3nDmUUGkv3x+IwMzw4QncXwypGLFZhpRrVBDgzhYgrapIBCBfV00bS97ci0lABG/NuqKVKQIsIjCsAZUI0QSiMJ1iNJBPlQegOKToGUsFpE4T0Vv4EcCFsCpdWl4iAQN2oZKYC+6W1Citv1bwuGtqUCBMpxbSUvyeErzqZAfDBzAIHkU2lXR54p+atFq4b8Gsgc0bdG1wiDAIRRNMS7eAKfgxmC73TNzmDjj3CtE1CWowJgZyTRiW9xeIoKTS2CU9eIxQWiibJUQrJFuoYwxhw2e2PhzJaP8miLEy1GNtY868/uCZ/KBr18lYcngxsI8RpKr9ztZGxvBFJBXUgGr/9U3vOz+Fnk5DIkPLW4SmDkhlMSXJwf1wglvpJzDcpSkAJy8G6h69HOkf6irpkM9IaxaVuza42alkQBulMKJpd4gf0Zb+XlJAWIx6lCa2QOFg8bRSCYBZijoqhAwoQLbYAyHBTRa4SmM64Q8o42RAC9tnJas04TzoCkEeODJjM5typhEReI5lckd3HrjrluuN1SBUBeWXB/7p2fdgpJfyBboZwudTCfz1eFL3rW/VBON2hdwLyuE1HHVWgG9Wz9eG1RuRoBTj4NrqdKJoIRKe5HQ+o7KphxA4FJFA0JjzDmIbKWlxmEN6K/IkA/XTqIn0Tx6wZ5g/h/kcLZsJn6MkE0r2URFZjRK1xDMvCphhoJZhBcE+xdlt9ihPdQtUsFTLmZJX4jkNFGpof8fy7qhh9KfwNBXBs7u+92j0/PDk72GhF7bc21BROpAA3vw5QLxBv/oMlcKoMocW7shXL2DAHTALdMQDCTKcjZ8odhSU4k+z2JgDAZWPSz1dGA/PjjHAjDNw4GH55IpYGoRAhkIlcUmixNQxSfUAhGQwyXcpYofOnHH9MEABbzT8Pw1k5tx17d0JAzK+DV2toG6PoKiJlLogEfQxgMHhGAEllSYRDIJA4z/USYhnmENReCtdDBfGnVGHLq8xAjDkeV3Kux4voYXREVdAqacHSuuaiRmCpgdYZPTHL3kpNVUWVseGSTHtLMRmJSw5QnJ0TgpT95NYcfwpCUIguh5/hU5Wdnm8Z2OcDpfnYK3aGLYKUMKtKnkxGoGx5AqRgrW9Z2qsuJXcqwWwoZp4E9S85g+znbZYd+g6GXoh1q94q91dIOIsrtVwhD+T/lbwuskAMQGkq0hjENZkCaDTzqWD43Kb7U0y9Lilk6ofZrBhaxk+qN44Pt3ZPRLg5pzEwUWgBCLLWJqCiRzAFBJEMEkeVjmpXq4W6Jpv/vC6v/xBdW+bYTPpuNOKTcgoStp91le6xP97aK6CODqrdV+TbrsubMpDY48u4OV4kLFS4W2Jw+f8HNF+MaD6MeeABT9rqv/zSqUkXp1rV47JVtVh27D3yOcN/NC6hHtJC//fqdSvgPeu30iJLyd2BLJV3iD8VRS8+MiVfnGXL0NXnWM8UHGMxfpYjbMn9Lxu+Huj1InwFFqy+PcYZBAHFZwrXHVyvHOHu7Y2ex+BcIssKd
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Related Effects"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/liquidity_pools/{liquidity_pool_id}/effects"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents effects referencing a given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new effects referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known effect unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream effects created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./retrieve-related-effects.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retrieve-related-effects.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retrieve-related-effects.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-related-effects.mdx b/docs/data/apis/horizon/api-reference/retrieve-related-effects.mdx
new file mode 100644
index 000000000..80aafdcb3
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/retrieve-related-effects.mdx
@@ -0,0 +1,12 @@
+---
+title: Retrieve Related Effects
+openapi: "openapi/horizon/bundled.yml GET /liquidity_pools/{liquidity_pool_id}/effects"
+---
+
+<Tip>
+
+**Supports Streaming**
+
+This endpoint supports streaming. To read more about this, visit the [streaming section](/docs/data/apis/horizon/api-reference/structure/streaming).
+
+</Tip>
diff --git a/docs/data/apis/horizon/api-reference/retrieve-related-trades.ParamsDetails.json b/docs/data/apis/horizon/api-reference/retrieve-related-trades.ParamsDetails.json
deleted file mode 100644
index d3fefe55c..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-related-trades.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"liquidity_pool_id","in":"path","required":true,"description":"A unique identifier for this liquidity pool."},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-related-trades.RequestSchema.json b/docs/data/apis/horizon/api-reference/retrieve-related-trades.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-related-trades.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-related-trades.StatusCodes.json b/docs/data/apis/horizon/api-reference/retrieve-related-trades.StatusCodes.json
deleted file mode 100644
index 573f65d5f..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-related-trades.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"base":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"counter":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operation":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","base","counter","operation"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"ledger_close_time":{"type":"string"},"offer_id":{"type":"string"},"trade_type":{"type":"string"},"liquidity_pool_fee_bp":{"type":"number","format":"uint32"},"base_liquidity_pool_id":{"type":"string"},"base_offer_id":{"type":"string"},"base_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"base_amount":{"type":"string"},"base_asset_type":{"type":"string"},"base_asset_code":{"type":"string"},"base_asset_issuer":{"type":"string"},"counter_liquidity_pool_id":{"type":"string"},"counter_offer_id":{"type":"string"},"counter_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"counter_amount":{"type":"string"},"counter_asset_type":{"type":"string"},"counter_asset_code":{"type":"string"},"counter_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"base_is_seller":{"type":"boolean"},"price":{"required":["id","paging_token","ledger_close_time","trade_type","base_amount","base_asset_type","counter_amount","counter_asset_type","base_is_seller"],"type":"object","properties":{"n":{"type":"string"},"d":{"type":"string"}},"title":"tradePrice"}}}}}}},"title":"Trade"}]},"examples":{"RetrieveRelatedTrades":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/3b476aff8a406a6ec3b61d5c038009cef85f2ddfaf616822dc4fec92845149b4/trades?cursor=&limit=2&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/3b476aff8a406a6ec3b61d5c038009cef85f2ddfaf616822dc4fec92845149b4/trades?cursor=120192370561220608&limit=2&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/3b476aff8a406a6ec3b61d5c038009cef85f2ddfaf616822dc4fec92845149b4/trades?cursor=120192344791343104&limit=2&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":""},"base":{"href":"https://horizon-testnet.stellar.org/accounts/GAVH5JM5OKXGMQDS7YPRJ4MQCPXJUGH26LYQPQJ4SOMOJ4SXY472ZM7G"},"counter":{"href":"https://horizon-testnet.stellar.org/accounts/GBB4JST32UWKOLGYYSCEYBHBCOFL2TGBHDVOMZP462ET4ZRD4ULA7S2L"},"operation":{"href":"https://horizon-testnet.stellar.org/operations/3697472920621057"}},"id":"3697472920621057-0","paging_token":"3697472920621057-0","ledger_close_time":"2015-11-18T03:47:47Z","offer_id":"9","base_offer_id":"9","base_account":"GAVH5JM5OKXGMQDS7YPRJ4MQCPXJUGH26LYQPQJ4SOMOJ4SXY472ZM7G","base_amount":"10.0000000","base_asset_type":"native","counter_liquidity_pool":"3b476aff8a406a6ec3b61d5c038009cef85f2ddfaf616822dc4fec92845149b4","liquidity_pool_fee_bp":"30","counter_amount":"2.6700000","counter_asset_type":"credit_alphanum4","counter_asset_code":"JPY","counter_asset_issuer":"GBVAOIACNSB7OVUXJYC5UE2D4YK2F7A24T7EE5YOMN4CE6GCHUTOUQXM","base_is_seller":true,"price":{"n":"267","d":"1000"},"trade_type":"liquidity_pool"}]}}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-related-trades.api.mdx b/docs/data/apis/horizon/api-reference/retrieve-related-trades.api.mdx
deleted file mode 100644
index ab45ace01..000000000
--- a/docs/data/apis/horizon/api-reference/retrieve-related-trades.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: retrieve-related-trades
-title: "Retrieve Related Trades"
-description: "This endpoint represents successful trades fulfilled by the given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new trades referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known trade unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream trade created since your request time."
-sidebar_label: "Retrieve Related Trades"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWntTGzkS/ypd+mM3SfmNscFVW3dACAmBQALkQhKKyKMeW8uMNJE0GJZy1X6N+3r3Sa5a8/D4AXncVV129/jHxUxL3f1Tv9Q9d8zxkWWDD+xAfk6lkO4WjrWOLLuoMYE2MDJxUis2YKdjaQGVSLRUDgwmBi0qZ8GmQYDWhmkEznCBFsI0CmUUoYDhLbgxwkheo4KoZJFoHQFXAgKuYIiQWhQgFVhnkMdSjSDWAhtwMvc/8CjSEwu3OgWnIZLWoYJQG1A4KXgbDNGgCmiRI5EXuVqS6Ba4QeBCoKCtSMYTh1HEDUQoRmga8CKEgHsllgSrwXNt5G9awURGEVjHjQPu/DbITSTROrhSeqIyqSBVEVoLHILUWG1AWrDoarTzZCyDMQTcIkhX3S80OgY35i5f1IDtW1rlMs2w2OuaRymSEkpPah4bAjUTOGcfGOQOBVipAiQSAwY/pySlkzE2gNWYTtBwOuoXgg3YG3RG4jW+wYhWnnpsWY0l3PAYHRqymTumeIxswEqILwniSylYjUmymYS7MasxYiYNCjZwJsVFw9qCVMnPKYIUqJwMJRp/qCtOr8GmtZJrpn/B6nOK5naOV8gju4KZSuMhmgxZb8uWwONgEwxkKAOIdOCBoNPhEOgowsD/r0MwaBOtLFpvvdJCknoTyQ8LIeEjqUaXTl+hyo9Gh8DBYKCNaLAas8EYY84Gd8zdJqSHVA5HSIrgDY+TCNmg12v1eu1+t7+xub7Zbq1PK2prI/DbtRZo5UjxQg8S1W80M8FMQgt2rNNIAE8S5KYBR34PC1IFUSoQPnEbfIJH3AaohFSjx6ANfCJ2n+AR/eSPvQP5I+RmlMaoHEir/vX7P11u+g4EhjyNMvz9tivhsc5INSJ0VBpTpOI2YJmC7KIKTCRj6b4RmNMxQsxvZJzGhWH4U86gMOhSo1A0gOj8/t65DFcjzM68TcJ3Wi2oA1eQJgmanNAbmLQw5kYEWmRxpIgbZN8JmlCbmJNPGuRWK/sAaMUBoljCrt36Wrtqt6bTixq7qds0SbRxtl4GtsI3SwunnTqtFv3MY3aSxXtWY4FWDpUjEp4kkcz8pvmrJbq7ikQ8io5CHzFy2fTwVwzosBJDgcfJjN9lJNWVrehwD53FKPwy1dhguMqQPOrOW4y6YtMacxgnPs5VqIdaR8gVm06rRvQh2/Sixpx0EVb2UHjjfjCREoPXP5RIUyIrHh34oyb//YJNYDxEStRfViX32wohN4ZTGJAO46+wqz+w/Q25xR9MpECnyqH5waQqC50fSq4FIm9g+aHOgKwKfzGtMSlWSVdsLIUPApWC5CHqObppjWVl8GUQaYuXVCUuLyYwwxDN5So5CBWqGi+zxyteL1SNIeLlMKlQZvm4CncqlVvrFNZ+uVx2rmLjSR+U01PwwKO8CqKEO4eGUt/eh636+1Z98+JufX1aAY8LYSgllpvFq/cq31uL7n5kKjRUOXyJRlqbzrnZjCq3nK+EqqB+EK2C6L8FWLnf/ZiVJA/DNk92L3LzZPeB9z3HLu2lxSia264MAxRcZIBZnpp5ur8szTnfKt+bc6Z5I1s2qSVMVyK4JDPFpAfD4Yr4Ma2xVVZSSfNe7mOv+TT7m73z10o2pVCWl6iez+rL5+CO+fvUfJ4uMnEWqtnYucQOms1xVmfXHVqn0DVsdrlvaDNqzvuCba4Nu/0eD8MN3m31eA+DtWGvLdaD1tpGq7UZYLixHnaECHnYa/c2Oh0RdEMMNjsb3fV2d3PYbWadh79l99FffvLl/y+dn/z96he6rVTKwx9Hznan1d7srPVb6712p9PqtTZWS15UkT+c5N1uf7O91l1rt7oLkvu7IRnaXO1YVocfHjCgain1DRrnwdA297bePl/fP1w/evlu7/D105P++fGb/e7h653jd/tne887vYPz18ev97snR4dH+92Td+fdfuf9YX9voV76Ltbb2939k9O1ztk/Xh4d7J2fn+zsnm8/3945enbQOd3bfv707dHh++Nur7N72n3/5mn37GCrf9I5WCqKvoF5uc4213qb/W6/s9lp9Trt1nrfHwDlELb4pt5aDHn30KyoQVin1V6vt9v19sZpa23Q7Q+6/fesWoiwTbaU9GfPyqzFvvukFnI8a7carexvRSweMGq6XFeD8rx3kO7/oXuwe2spttZazgYD1mn0+oXAq3IrCwwK6S55lIy5SuPuEl2WXNn+8fnSqyKhsr3tt1tHL7Z2Xp1s94/enr3bP99ZP9vtPO2ev+w86291uqf93d3186PDV92d3d7ezvOz06Oz1+8OlzNT3poo8ycZTKfXZz75sDYpslBuLgBCOabMPnjjUFmyWR8KrvCWDVa3RGpFxiH+1DiJ0Y018RyhyyqEMRuwpXh3t1RuTfMQRn0aNNdF/zQ10dc5GlvVuDrN6OAVuok2V/4uvXrHMHWpwa/Z81lBCarY9YJaaqH2aT5P3HkbiwBCY7PVrUar0Sb90jjm5nZGBYnR11L4nik8Pz09hq3jF9S3EtxxaopVu+851wa8cCDVCK3LWq0G6x44373PViZGizSYDRkWtsjat3R3KFtxyC01l52GQCubxlgs5ddo+Aih0sUCQ9WHvMZiPlBp19W1kaioo+4FKWchWSTMphnD21KgHW2QWojSes0regyNFCOEIboJoiL2mbbzK4+NpnqMmuFXCBMaSjhbA4EBKmd4JH9DAXgTjKktaWt+B++LkPmil6hsPToNNh36DqXhynLf27Y18B1TOqI8RMKQR6RsjRq8+TgBr/3Ex8tRXe076OXKxpJl/dUt4UP1QC8eFe4p8BojSqF2LqnmYjcDbbCutMDHfynr+ag+qoJdPh/kvuOMAq4lh+DszUENOAyNnlg0noNWWIw1SqxPnr60X8Ra6MA2nY/aVlxZQlqDQTKnbMim6VpyQwMoHWajsyQDtAYT9JOCOEYl/OCNgOKKGINU1iEXtCjmVzSyE9Jg4PwZ0lzRej39sY5SKRAyjxmihbGeeEhELBXNOA0UJu7NscCGWPjhwSM/8yys88PTUtOfYTvSoxkGk8lkXvmSsj6M9KjJ6wondZuqOmWhMdbz/PHYzyusJjfhwdXI6FQJ0GrRGzLbMcFYOgxcangEMiafx9ifvM6HGzH/lQaXWeqAYRonjxvwjOaiKuv10GM+1CnNObyIBGDOrzQNLZDqhBoEYwyugKir+vvpyR5BOwNgJN04HTYCHTdzHIrfQtXmMNLDZsylaj7dfbt7cHT84tVeIxaP/XFtY6gN0sEPcSQVTWJ+tjDRxtH8TDpfDOfjWQoD0guBwVhn4x8vH7klvNLiewIBCB34uZDHaABPnkwQBM1+Hc3mtbEIJlWKhCiAoiPLwhCn0bISPCJ3qUaJ0paePMkCAPppKI+iW7+1X3t5zSMpvIKXS7kNyfQNgptosEhjYkfOowI0Kg8qAgOdJlGOT0xhWMZUcnHlvIENtYcxknwoI/I4WlUxr8ac6ZN3xVzxEVqQZFwTVYOEGxR1QZP3wrx0OK+qTpyMfdAjnvlKCmoU8nQIClFYeDTBn6MIKp5FQzka4X9kOzzx6YC2+8hK7MhEqFGDJrZH4Qmaa1+ulsVY9WQ9UV2HPpURWTZM44FvEuQDzULsqkE/I9fLbmq1hWJvvrTDmEv/FqNI/736zrdeA1TZJTfntZXwYIzQadCdYDaIL9/Uszczjnk44f5tfuv3m9rmwYud3Vcnu7SkMXZx5G+CibYu5qrCsmjzQN7ngfIrg7ni4W42Zvz/Nyh/7m9Q8rubwxvXTCIufdfUm9xdftf6sHCxI2sZrPr8JL9uXdTYWFtHC+/uKFucmWg6pcfZBwJ0CRPS8mF03ycCVfP73388shKh7AZbfg6T31mZvw9+i3J/mG9EHkCh+DrmO0H4E30P8gBIxZcyM5Au6B8jCaVv9IlHb/JhxmP4pg+57hGwmNur26p8M8EXPd0PD8bI6dRn3ZytIMCkquHS5ylz3Zy93VM2nf4bBS5UEw==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Related Trades"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/liquidity_pools/{liquidity_pool_id}/trades"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents successful trades fulfilled by the given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new trades referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known trade unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream trade created since your request time. 
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./retrieve-related-trades.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retrieve-related-trades.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retrieve-related-trades.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/retrieve-related-trades.mdx b/docs/data/apis/horizon/api-reference/retrieve-related-trades.mdx
new file mode 100644
index 000000000..f92a0a749
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/retrieve-related-trades.mdx
@@ -0,0 +1,12 @@
+---
+title: Retrieve Related Trades
+openapi: "openapi/horizon/bundled.yml GET /liquidity_pools/{liquidity_pool_id}/trades"
+---
+
+<Tip>
+
+**Supports Streaming**
+
+This endpoint supports streaming. To read more about this, visit the [streaming section](/docs/data/apis/horizon/api-reference/structure/streaming).
+
+</Tip>
diff --git a/docs/data/apis/horizon/api-reference/sidebar.ts b/docs/data/apis/horizon/api-reference/sidebar.ts
deleted file mode 100644
index ca8646abb..000000000
--- a/docs/data/apis/horizon/api-reference/sidebar.ts
+++ /dev/null
@@ -1,458 +0,0 @@
-import type { SidebarsConfig } from "@docusaurus/plugin-content-docs";
-
-const sidebar: SidebarsConfig = {
-  apisidebar: [
-    {
-      type: "category",
-      label: "Resources",
-      collapsible: true,
-      collapsed: true,
-      items: [
-        {
-          type: "category",
-          label: "Accounts",
-          key: "resources-accounts",
-          items: [
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/list-all-accounts",
-              label: "List all Accounts",
-              className: "api-method get",
-              key: "resources-accounts-data-apis-horizon-api-reference-list-all-accounts",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/retrieve-an-account",
-              label: "Retrieve an Account",
-              className: "api-method get",
-              key: "resources-accounts-data-apis-horizon-api-reference-retrieve-an-account",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/get-transactions-by-account-id",
-              label: "Retrieve an Account's Transactions",
-              className: "api-method get",
-              key: "resources-accounts-data-apis-horizon-api-reference-get-transactions-by-account-id",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/get-operations-by-account-id",
-              label: "Retrieve an Account's Operations",
-              className: "api-method get",
-              key: "resources-accounts-data-apis-horizon-api-reference-get-operations-by-account-id",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/get-payments-by-account-id",
-              label: "Retrieve an Account's Payments",
-              className: "api-method get",
-              key: "resources-accounts-data-apis-horizon-api-reference-get-payments-by-account-id",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/get-effects-by-account-id",
-              label: "Retrieve an Account's Effects",
-              className: "api-method get",
-              key: "resources-accounts-data-apis-horizon-api-reference-get-effects-by-account-id",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/get-offers-by-account-id",
-              label: "Retrieve an Account's Offers",
-              className: "api-method get",
-              key: "resources-accounts-data-apis-horizon-api-reference-get-offers-by-account-id",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/get-trades-by-account-id",
-              label: "Retrieve an Account's Trades",
-              className: "api-method get",
-              key: "resources-accounts-data-apis-horizon-api-reference-get-trades-by-account-id",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/get-data-by-account-id",
-              label: "Retrieve an Account's Data",
-              className: "api-method get",
-              key: "resources-accounts-data-apis-horizon-api-reference-get-data-by-account-id",
-            },
-          ],
-        },
-        {
-          type: "category",
-          label: "Assets",
-          key: "resources-assets",
-          items: [
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/list-all-assets",
-              label: "List all Assets",
-              className: "api-method get",
-              key: "resources-assets-data-apis-horizon-api-reference-list-all-assets",
-            },
-          ],
-        },
-        {
-          type: "category",
-          label: "Claimable Balances",
-          key: "resources-claimable-balances",
-          items: [
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/list-all-claimable-balances",
-              label: "List All Claimable Balances",
-              className: "api-method get",
-              key: "resources-claimable-balances-data-apis-horizon-api-reference-list-all-claimable-balances",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/retrieve-a-claimable-balance",
-              label: "Retrieve a Claimable Balance",
-              className: "api-method get",
-              key: "resources-claimable-balances-data-apis-horizon-api-reference-retrieve-a-claimable-balance",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/cb-retrieve-related-transactions",
-              label: "Retrieve Related Transactions",
-              className: "api-method get",
-              key: "resources-claimable-balances-data-apis-horizon-api-reference-cb-retrieve-related-transactions",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/cb-retrieve-related-operations",
-              label: "Retrieve Related Operations",
-              className: "api-method get",
-              key: "resources-claimable-balances-data-apis-horizon-api-reference-cb-retrieve-related-operations",
-            },
-          ],
-        },
-        {
-          type: "category",
-          label: "Effects",
-          key: "resources-effects",
-          items: [
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/list-all-effects",
-              label: "List All Effects",
-              className: "api-method get",
-              key: "resources-effects-data-apis-horizon-api-reference-list-all-effects",
-            },
-          ],
-        },
-        {
-          type: "category",
-          label: "Liquidity Pools",
-          key: "resources-liquidity-pools",
-          items: [
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/list-liquidity-pools",
-              label: "List Liquidity Pools",
-              className: "api-method get",
-              key: "resources-liquidity-pools-data-apis-horizon-api-reference-list-liquidity-pools",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/retrieve-a-liquidity-pool",
-              label: "Retrieve a Liquidity Pool",
-              className: "api-method get",
-              key: "resources-liquidity-pools-data-apis-horizon-api-reference-retrieve-a-liquidity-pool",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/retrieve-related-effects",
-              label: "Retrieve Related Effects",
-              className: "api-method get",
-              key: "resources-liquidity-pools-data-apis-horizon-api-reference-retrieve-related-effects",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/retrieve-related-trades",
-              label: "Retrieve Related Trades",
-              className: "api-method get",
-              key: "resources-liquidity-pools-data-apis-horizon-api-reference-retrieve-related-trades",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/lp-retrieve-related-transactions",
-              label: "Retrieve Related Transactions",
-              className: "api-method get",
-              key: "resources-liquidity-pools-data-apis-horizon-api-reference-lp-retrieve-related-transactions",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/lp-retrieve-related-operations",
-              label: "Retrieve Related Operations",
-              className: "api-method get",
-              key: "resources-liquidity-pools-data-apis-horizon-api-reference-lp-retrieve-related-operations",
-            },
-          ],
-        },
-        {
-          type: "category",
-          label: "Ledgers",
-          key: "resources-ledgers",
-          items: [
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/retrieve-a-ledger",
-              label: "Retrieve a Ledger",
-              className: "api-method get",
-              key: "resources-ledgers-data-apis-horizon-api-reference-retrieve-a-ledger",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/retrieve-a-ledgers-transactions",
-              label: "Retrieve a Ledger's Transactions",
-              className: "api-method get",
-              key: "resources-ledgers-data-apis-horizon-api-reference-retrieve-a-ledgers-transactions",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/retrieve-a-ledgers-payments",
-              label: "Retrieve a Ledger's Payments",
-              className: "api-method get",
-              key: "resources-ledgers-data-apis-horizon-api-reference-retrieve-a-ledgers-payments",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/retrieve-a-ledgers-operations",
-              label: "Retrieve a Ledger's Operations",
-              className: "api-method get",
-              key: "resources-ledgers-data-apis-horizon-api-reference-retrieve-a-ledgers-operations",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/retrieve-a-ledgers-effects",
-              label: "Retrieve a Ledgers's Effects",
-              className: "api-method get",
-              key: "resources-ledgers-data-apis-horizon-api-reference-retrieve-a-ledgers-effects",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/list-all-ledgers",
-              label: "List All Ledgers",
-              className: "api-method get",
-              key: "resources-ledgers-data-apis-horizon-api-reference-list-all-ledgers",
-            },
-          ],
-        },
-        {
-          type: "category",
-          label: "Offers",
-          key: "resources-offers",
-          items: [
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/get-all-offers",
-              label: "List All Offers",
-              className: "api-method get",
-              key: "resources-offers-data-apis-horizon-api-reference-get-all-offers",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/get-offer-by-offer-id",
-              label: "Retrieve an Offer",
-              className: "api-method get",
-              key: "resources-offers-data-apis-horizon-api-reference-get-offer-by-offer-id",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/get-trades-by-offer-id",
-              label: "Retrieve an Offer's Trades",
-              className: "api-method get",
-              key: "resources-offers-data-apis-horizon-api-reference-get-trades-by-offer-id",
-            },
-          ],
-        },
-        {
-          type: "category",
-          label: "Operations",
-          key: "resources-operations",
-          items: [
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/retrieve-an-operation",
-              label: "Retrieve an Operation",
-              className: "api-method get",
-              key: "resources-operations-data-apis-horizon-api-reference-retrieve-an-operation",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/retrieve-an-operations-effects",
-              label: "Retrieve an Operation's Effects",
-              className: "api-method get",
-              key: "resources-operations-data-apis-horizon-api-reference-retrieve-an-operations-effects",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/list-all-operations",
-              label: "List All Operations",
-              className: "api-method get",
-              key: "resources-operations-data-apis-horizon-api-reference-list-all-operations",
-            },
-          ],
-        },
-        {
-          type: "category",
-          label: "Payments",
-          key: "resources-payments",
-          items: [
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/list-all-payments",
-              label: "List All Payments",
-              className: "api-method get",
-              key: "resources-payments-data-apis-horizon-api-reference-list-all-payments",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/retrieve-a-transactions-payments",
-              label: "Retrieve a Transaction's Payments",
-              className: "api-method get",
-              key: "resources-payments-data-apis-horizon-api-reference-retrieve-a-transactions-payments",
-            },
-          ],
-        },
-        {
-          type: "category",
-          label: "Trades",
-          key: "resources-trades",
-          items: [
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/get-all-trades",
-              label: "List All Trades",
-              className: "api-method get",
-              key: "resources-trades-data-apis-horizon-api-reference-get-all-trades",
-            },
-          ],
-        },
-        {
-          type: "category",
-          label: "Transactions",
-          key: "resources-transactions",
-          items: [
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/retrieve-a-transaction",
-              label: "Retrieve a Transaction",
-              className: "api-method get",
-              key: "resources-transactions-data-apis-horizon-api-reference-retrieve-a-transaction",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/retrieve-a-transactions-operations",
-              label: "Retrieve a Transaction's Operations",
-              className: "api-method get",
-              key: "resources-transactions-data-apis-horizon-api-reference-retrieve-a-transactions-operations",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/retrieve-a-transactions-effects",
-              label: "Retrieve a Transaction's Effects",
-              className: "api-method get",
-              key: "resources-transactions-data-apis-horizon-api-reference-retrieve-a-transactions-effects",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/list-all-transactions",
-              label: "List All Transactions",
-              className: "api-method get",
-              key: "resources-transactions-data-apis-horizon-api-reference-list-all-transactions",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/submit-a-transaction",
-              label: "Submit a Transaction",
-              className: "api-method post",
-              key: "resources-transactions-data-apis-horizon-api-reference-submit-a-transaction",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/submit-async-transaction",
-              label: "Submit a Transaction Asynchronously",
-              className: "api-method post",
-              key: "resources-transactions-data-apis-horizon-api-reference-submit-async-transaction",
-            },
-          ],
-        },
-      ],
-    },
-    {
-      type: "category",
-      label: "Aggregations",
-      collapsible: true,
-      collapsed: true,
-      items: [
-        {
-          type: "category",
-          label: "Fee Stats",
-          key: "aggregations-fee-stats",
-          items: [
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/retrieve-fee-stats",
-              label: "Retrieve Fee Stats",
-              className: "api-method get",
-              key: "aggregations-fee-stats-data-apis-horizon-api-reference-retrieve-fee-stats",
-            },
-          ],
-        },
-        {
-          type: "category",
-          label: "Order Books",
-          key: "aggregations-order-books",
-          items: [
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/retrieve-an-order-book",
-              label: "Retrieve an Order Book",
-              className: "api-method get",
-              key: "aggregations-order-books-data-apis-horizon-api-reference-retrieve-an-order-book",
-            },
-          ],
-        },
-        {
-          type: "category",
-          label: "Paths",
-          key: "aggregations-paths",
-          items: [
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/list-strict-receive-payment-paths",
-              label: "List Strict Receive Payment Paths",
-              className: "api-method get",
-              key: "aggregations-paths-data-apis-horizon-api-reference-list-strict-receive-payment-paths",
-            },
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/list-strict-send-payment-paths",
-              label: "List Strict Send Payment Paths",
-              className: "api-method get",
-              key: "aggregations-paths-data-apis-horizon-api-reference-list-strict-send-payment-paths",
-            },
-          ],
-        },
-        {
-          type: "category",
-          label: "Trade Aggregations",
-          key: "aggregations-trade-aggregations",
-          items: [
-            {
-              type: "doc",
-              id: "data/apis/horizon/api-reference/list-trade-aggregations",
-              label: "List Trade Aggregations",
-              className: "api-method get",
-              key: "aggregations-trade-aggregations-data-apis-horizon-api-reference-list-trade-aggregations",
-            },
-          ],
-        },
-      ],
-    },
-  ],
-};
-
-export default sidebar.apisidebar;
diff --git a/docs/data/apis/horizon/api-reference/structure/README.mdx b/docs/data/apis/horizon/api-reference/structure/README.mdx
deleted file mode 100644
index e300c71d9..000000000
--- a/docs/data/apis/horizon/api-reference/structure/README.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: Horizon API Reference
-sidebar_position: 20
-sidebar_label: Structure
-description: Horizon is an API for interacting with the Stellar network.
-sidebar_key: horizon-api-structure
----
-
-import DocCardList from "@theme/DocCardList";
-
-How Horizon is structured.
-
-<DocCardList />
diff --git a/docs/data/apis/horizon/api-reference/structure/consistency.mdx b/docs/data/apis/horizon/api-reference/structure/consistency.mdx
index de00eb39b..905c54bbe 100644
--- a/docs/data/apis/horizon/api-reference/structure/consistency.mdx
+++ b/docs/data/apis/horizon/api-reference/structure/consistency.mdx
@@ -1,6 +1,6 @@
 ---
 title: Consistency
-sidebar_position: 70
+description: "For endpoints which serve data which can change from ledger to ledger (for example an account balance), Horizon includes a Latest-Ledger HTTP header in its..."
 ---
 
 For endpoints which serve data which can change from ledger to ledger (for example an account balance), Horizon includes a `Latest-Ledger` HTTP header in its response. The value of the `Latest-Ledger` HTTP header is the sequence number of the latest ledger known to Horizon at the time the request was processed. Horizon will guarantee that all the data included in the response is consistent with that ledger. This mechanism prevents race conditions where a request is processed at the boundary of two ledgers and ensures that the response is consistent with the ledger included in the `Latest-Ledger` HTTP header.
diff --git a/docs/data/apis/horizon/api-reference/structure/index.mdx b/docs/data/apis/horizon/api-reference/structure/index.mdx
new file mode 100644
index 000000000..4e1911230
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/structure/index.mdx
@@ -0,0 +1,41 @@
+---
+title: Horizon API Reference
+sidebarTitle: Structure
+description: Horizon is an API for interacting with the Stellar network.
+sidebar_key: horizon-api-structure
+---
+
+How Horizon is structured.
+
+<CardGroup cols={2}>
+  <Card title="Response Format" icon="file-lines" href="/docs/data/apis/horizon/api-reference/structure/response-format">
+
+    Horizon delivers responses as JSON objects formatted according to HAL.
+
+  </Card>
+  <Card title="Streaming" icon="file-lines" href="/docs/data/apis/horizon/api-reference/structure/streaming">
+
+    Horizon provides a streaming mechanism for receiving events in near real time.
+
+  </Card>
+  <Card title="Rate Limiting" icon="file-lines" href="/docs/data/apis/horizon/api-reference/structure/rate-limiting">
+
+    Horizon rate limits on a per-IP-address basis.
+
+  </Card>
+  <Card title="XDR" icon="file-lines" href="/docs/data/apis/horizon/api-reference/structure/xdr">
+
+    In the Stellar network, transactions are encoded using a standardized protocol called External Data Representation (XDR).
+
+  </Card>
+  <Card title="Consistency" icon="file-lines" href="/docs/data/apis/horizon/api-reference/structure/consistency">
+
+    For endpoints which serve data which can change from ledger to ledger (for example an account balance), Horizon includes a Latest-Ledger HTTP header in its...
+
+  </Card>
+  <Card title="Pagination" icon="box-archive" href="/docs/data/apis/horizon/api-reference/structure/pagination">
+
+    1 items
+
+  </Card>
+</CardGroup>
diff --git a/docs/data/apis/horizon/api-reference/structure/pagination/README.mdx b/docs/data/apis/horizon/api-reference/structure/pagination/README.mdx
deleted file mode 100644
index e91d8de71..000000000
--- a/docs/data/apis/horizon/api-reference/structure/pagination/README.mdx
+++ /dev/null
@@ -1,271 +0,0 @@
----
-title: Pagination
-position: 60
----
-
-To make it possible to explore the millions of records for resources like transactions and operations, Horizon paginates the data it returns for collection-based endpoints.
-
-Each individual transaction, operation, ledger, etc. is returned as a record, and a group of records is called a collection. Records are returned as an array under the `_embedded` attribute.
-
-To move between pages of a collection of records, use the links in the `next` and `prev` attributes nested under the top-level `_links` attribute.
-
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- \_links
-  - array
-  - Provides links for navigating to other pages.
-    - \_links.self
-      - array
-      - An `href` key with a link to the response itself as the value.
-    - \_links.next
-      - array
-      - An `href` key with a link to the next page for this endpoint as the value.
-    - \_links.prev
-      - array
-      - An `href` key with a link to the next page for this endpoint as the value.
-- \_embedded
-  - array
-  - An `href` key with a link to the next page for this endpoint as the value.
-    - \_embedded.records
-      - array
-      - Returns an array of records.
-
-</AttributeTable>
-
-<CodeExample title="Example Request">
-
-```js
-var StellarSdk = require("@stellar/stellar-sdk");
-var server = new StellarSdk.Horizon.Server(
-  "https://horizon-testnet.stellar.org",
-);
-
-server
-  .transactions()
-  .call()
-  .then(function (resp) {
-    // page 1
-    console.log(resp);
-    return resp.next();
-  })
-  .then(function (resp) {
-    // page 2
-    console.log(resp);
-  })
-  .catch(function (err) {
-    console.error(err);
-  });
-```
-
-</CodeExample>
-
-<ExampleResponse title="Example Paginated Response">
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/transactions/2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906/operations?cursor=&limit=5&order=asc"
-    },
-    "next": {
-      "href": "https://horizon-testnet.stellar.org/transactions/2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906/operations?cursor=113928152169844741&limit=5&order=asc"
-    },
-    "prev": {
-      "href": "https://horizon-testnet.stellar.org/transactions/2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906/operations?cursor=113928152169844737&limit=5&order=desc"
-    }
-  },
-  "_embedded": {
-    "records": [
-      {
-        "_links": {
-          "self": {
-            "href": "https://horizon-testnet.stellar.org/operations/113928152169844737"
-          },
-          "transaction": {
-            "href": "https://horizon-testnet.stellar.org/transactions/2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906"
-          },
-          "effects": {
-            "href": "https://horizon-testnet.stellar.org/operations/113928152169844737/effects"
-          }
-        },
-        "id": "113928152169844737",
-        "paging_token": "113928152169844737",
-        "transaction_successful": true,
-        "source_account": "GDO2BIMNH7T6MOJVPKEJHWAGMYGOQU5QMK5BKT5XMVWPZKHAGA4JNAQZ",
-        "type": "manage_buy_offer",
-        "type_i": 12,
-        "created_at": "2019-10-28T19:44:09Z",
-        "transaction_hash": "2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906",
-        "amount": "0.0000000",
-        "price": "0.0001000",
-        "price_r": {
-          "n": 1,
-          "d": 10000
-        },
-        "buying_asset_type": "native",
-        "selling_asset_type": "credit_alphanum4",
-        "selling_asset_code": "SLT",
-        "selling_asset_issuer": "GCKA6K5PCQ6PNF5RQBF7PQDJWRHO6UOGFMRLK3DYHDOI244V47XKQ4GP",
-        "offer_id": 126229445
-      },
-      {
-        "_links": {
-          "self": {
-            "href": "https://horizon-testnet.stellar.org/operations/113928152169844738"
-          },
-          "transaction": {
-            "href": "https://horizon-testnet.stellar.org/transactions/2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906"
-          },
-          "effects": {
-            "href": "https://horizon-testnet.stellar.org/operations/113928152169844738/effects"
-          },
-          "succeeds": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=113928152169844738"
-          },
-          "precedes": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=113928152169844738"
-          }
-        },
-        "id": "113928152169844738",
-        "paging_token": "113928152169844738",
-        "transaction_successful": true,
-        "source_account": "GDO2BIMNH7T6MOJVPKEJHWAGMYGOQU5QMK5BKT5XMVWPZKHAGA4JNAQZ",
-        "type": "manage_buy_offer",
-        "type_i": 12,
-        "created_at": "2019-10-28T19:44:09Z",
-        "transaction_hash": "2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906",
-        "amount": "0.0000000",
-        "price": "0.0001000",
-        "price_r": {
-          "n": 1,
-          "d": 10000
-        },
-        "buying_asset_type": "native",
-        "selling_asset_type": "credit_alphanum4",
-        "selling_asset_code": "SLT",
-        "selling_asset_issuer": "GCKA6K5PCQ6PNF5RQBF7PQDJWRHO6UOGFMRLK3DYHDOI244V47XKQ4GP",
-        "offer_id": 126229446
-      },
-      {
-        "_links": {
-          "self": {
-            "href": "https://horizon-testnet.stellar.org/operations/113928152169844739"
-          },
-          "transaction": {
-            "href": "https://horizon-testnet.stellar.org/transactions/2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906"
-          },
-          "effects": {
-            "href": "https://horizon-testnet.stellar.org/operations/113928152169844739/effects"
-          },
-          "succeeds": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=113928152169844739"
-          },
-          "precedes": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=113928152169844739"
-          }
-        },
-        "id": "113928152169844739",
-        "paging_token": "113928152169844739",
-        "transaction_successful": true,
-        "source_account": "GDO2BIMNH7T6MOJVPKEJHWAGMYGOQU5QMK5BKT5XMVWPZKHAGA4JNAQZ",
-        "type": "manage_buy_offer",
-        "type_i": 12,
-        "created_at": "2019-10-28T19:44:09Z",
-        "transaction_hash": "2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906",
-        "amount": "0.0000000",
-        "price": "0.0001000",
-        "price_r": {
-          "n": 1,
-          "d": 10000
-        },
-        "buying_asset_type": "native",
-        "selling_asset_type": "credit_alphanum4",
-        "selling_asset_code": "SLT",
-        "selling_asset_issuer": "GCKA6K5PCQ6PNF5RQBF7PQDJWRHO6UOGFMRLK3DYHDOI244V47XKQ4GP",
-        "offer_id": 126229447
-      },
-      {
-        "_links": {
-          "self": {
-            "href": "https://horizon-testnet.stellar.org/operations/113928152169844740"
-          },
-          "transaction": {
-            "href": "https://horizon-testnet.stellar.org/transactions/2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906"
-          },
-          "effects": {
-            "href": "https://horizon-testnet.stellar.org/operations/113928152169844740/effects"
-          },
-          "succeeds": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=113928152169844740"
-          },
-          "precedes": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=113928152169844740"
-          }
-        },
-        "id": "113928152169844740",
-        "paging_token": "113928152169844740",
-        "transaction_successful": true,
-        "source_account": "GDO2BIMNH7T6MOJVPKEJHWAGMYGOQU5QMK5BKT5XMVWPZKHAGA4JNAQZ",
-        "type": "manage_buy_offer",
-        "type_i": 12,
-        "created_at": "2019-10-28T19:44:09Z",
-        "transaction_hash": "2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906",
-        "amount": "0.0000000",
-        "price": "0.0001000",
-        "price_r": {
-          "n": 1,
-          "d": 10000
-        },
-        "buying_asset_type": "native",
-        "selling_asset_type": "credit_alphanum4",
-        "selling_asset_code": "SLT",
-        "selling_asset_issuer": "GCKA6K5PCQ6PNF5RQBF7PQDJWRHO6UOGFMRLK3DYHDOI244V47XKQ4GP",
-        "offer_id": 126229448
-      },
-      {
-        "_links": {
-          "self": {
-            "href": "https://horizon-testnet.stellar.org/operations/113928152169844741"
-          },
-          "transaction": {
-            "href": "https://horizon-testnet.stellar.org/transactions/2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906"
-          },
-          "effects": {
-            "href": "https://horizon-testnet.stellar.org/operations/113928152169844741/effects"
-          },
-          "succeeds": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=113928152169844741"
-          },
-          "precedes": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=113928152169844741"
-          }
-        },
-        "id": "113928152169844741",
-        "paging_token": "113928152169844741",
-        "transaction_successful": true,
-        "source_account": "GDO2BIMNH7T6MOJVPKEJHWAGMYGOQU5QMK5BKT5XMVWPZKHAGA4JNAQZ",
-        "type": "manage_buy_offer",
-        "type_i": 12,
-        "created_at": "2019-10-28T19:44:09Z",
-        "transaction_hash": "2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906",
-        "amount": "0.0000000",
-        "price": "0.0001000",
-        "price_r": {
-          "n": 1,
-          "d": 10000
-        },
-        "buying_asset_type": "native",
-        "selling_asset_type": "credit_alphanum4",
-        "selling_asset_code": "SLT",
-        "selling_asset_issuer": "GCKA6K5PCQ6PNF5RQBF7PQDJWRHO6UOGFMRLK3DYHDOI244V47XKQ4GP",
-        "offer_id": 126229449
-      }
-    ]
-  }
-}
-```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/structure/pagination/index.mdx b/docs/data/apis/horizon/api-reference/structure/pagination/index.mdx
new file mode 100644
index 000000000..a7e628266
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/structure/pagination/index.mdx
@@ -0,0 +1,280 @@
+---
+title: Pagination
+description: "To make it possible to explore the millions of records for resources like transactions and operations, Horizon paginates the data it returns for collection-based endpoints."
+position: 60
+---
+
+Each individual transaction, operation, ledger, etc. is returned as a record, and a group of records is called a collection. Records are returned as an array under the `_embedded` attribute.
+
+To move between pages of a collection of records, use the links in the `next` and `prev` attributes nested under the top-level `_links` attribute.
+
+<ResponseField name="_links" type="array">
+
+Provides links for navigating to other pages.
+
+  <Expandable title="_links properties">
+    <ResponseField name="_links.self" type="array">
+
+      An `href` key with a link to the response itself as the value.
+
+    </ResponseField>
+
+    <ResponseField name="_links.next" type="array">
+
+      An `href` key with a link to the next page for this endpoint as the value.
+
+    </ResponseField>
+
+    <ResponseField name="_links.prev" type="array">
+
+      An `href` key with a link to the next page for this endpoint as the value.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="_embedded" type="array">
+
+An `href` key with a link to the next page for this endpoint as the value.
+
+  <Expandable title="_embedded properties">
+    <ResponseField name="_embedded.records" type="array">
+
+      Returns an array of records.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+### Example Request
+
+```js
+var StellarSdk = require("@stellar/stellar-sdk");
+var server = new StellarSdk.Horizon.Server(
+  "https://horizon-testnet.stellar.org",
+);
+
+server
+  .transactions()
+  .call()
+  .then(function (resp) {
+    // page 1
+    console.log(resp);
+    return resp.next();
+  })
+  .then(function (resp) {
+    // page 2
+    console.log(resp);
+  })
+  .catch(function (err) {
+    console.error(err);
+  });
+```
+
+### Example Response
+
+```json Example Paginated Response
+{
+  "_links": {
+    "self": {
+      "href": "https://horizon-testnet.stellar.org/transactions/2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906/operations?cursor=&limit=5&order=asc"
+    },
+    "next": {
+      "href": "https://horizon-testnet.stellar.org/transactions/2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906/operations?cursor=113928152169844741&limit=5&order=asc"
+    },
+    "prev": {
+      "href": "https://horizon-testnet.stellar.org/transactions/2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906/operations?cursor=113928152169844737&limit=5&order=desc"
+    }
+  },
+  "_embedded": {
+    "records": [
+      {
+        "_links": {
+          "self": {
+            "href": "https://horizon-testnet.stellar.org/operations/113928152169844737"
+          },
+          "transaction": {
+            "href": "https://horizon-testnet.stellar.org/transactions/2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906"
+          },
+          "effects": {
+            "href": "https://horizon-testnet.stellar.org/operations/113928152169844737/effects"
+          }
+        },
+        "id": "113928152169844737",
+        "paging_token": "113928152169844737",
+        "transaction_successful": true,
+        "source_account": "GDO2BIMNH7T6MOJVPKEJHWAGMYGOQU5QMK5BKT5XMVWPZKHAGA4JNAQZ",
+        "type": "manage_buy_offer",
+        "type_i": 12,
+        "created_at": "2019-10-28T19:44:09Z",
+        "transaction_hash": "2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906",
+        "amount": "0.0000000",
+        "price": "0.0001000",
+        "price_r": {
+          "n": 1,
+          "d": 10000
+        },
+        "buying_asset_type": "native",
+        "selling_asset_type": "credit_alphanum4",
+        "selling_asset_code": "SLT",
+        "selling_asset_issuer": "GCKA6K5PCQ6PNF5RQBF7PQDJWRHO6UOGFMRLK3DYHDOI244V47XKQ4GP",
+        "offer_id": 126229445
+      },
+      {
+        "_links": {
+          "self": {
+            "href": "https://horizon-testnet.stellar.org/operations/113928152169844738"
+          },
+          "transaction": {
+            "href": "https://horizon-testnet.stellar.org/transactions/2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906"
+          },
+          "effects": {
+            "href": "https://horizon-testnet.stellar.org/operations/113928152169844738/effects"
+          },
+          "succeeds": {
+            "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=113928152169844738"
+          },
+          "precedes": {
+            "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=113928152169844738"
+          }
+        },
+        "id": "113928152169844738",
+        "paging_token": "113928152169844738",
+        "transaction_successful": true,
+        "source_account": "GDO2BIMNH7T6MOJVPKEJHWAGMYGOQU5QMK5BKT5XMVWPZKHAGA4JNAQZ",
+        "type": "manage_buy_offer",
+        "type_i": 12,
+        "created_at": "2019-10-28T19:44:09Z",
+        "transaction_hash": "2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906",
+        "amount": "0.0000000",
+        "price": "0.0001000",
+        "price_r": {
+          "n": 1,
+          "d": 10000
+        },
+        "buying_asset_type": "native",
+        "selling_asset_type": "credit_alphanum4",
+        "selling_asset_code": "SLT",
+        "selling_asset_issuer": "GCKA6K5PCQ6PNF5RQBF7PQDJWRHO6UOGFMRLK3DYHDOI244V47XKQ4GP",
+        "offer_id": 126229446
+      },
+      {
+        "_links": {
+          "self": {
+            "href": "https://horizon-testnet.stellar.org/operations/113928152169844739"
+          },
+          "transaction": {
+            "href": "https://horizon-testnet.stellar.org/transactions/2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906"
+          },
+          "effects": {
+            "href": "https://horizon-testnet.stellar.org/operations/113928152169844739/effects"
+          },
+          "succeeds": {
+            "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=113928152169844739"
+          },
+          "precedes": {
+            "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=113928152169844739"
+          }
+        },
+        "id": "113928152169844739",
+        "paging_token": "113928152169844739",
+        "transaction_successful": true,
+        "source_account": "GDO2BIMNH7T6MOJVPKEJHWAGMYGOQU5QMK5BKT5XMVWPZKHAGA4JNAQZ",
+        "type": "manage_buy_offer",
+        "type_i": 12,
+        "created_at": "2019-10-28T19:44:09Z",
+        "transaction_hash": "2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906",
+        "amount": "0.0000000",
+        "price": "0.0001000",
+        "price_r": {
+          "n": 1,
+          "d": 10000
+        },
+        "buying_asset_type": "native",
+        "selling_asset_type": "credit_alphanum4",
+        "selling_asset_code": "SLT",
+        "selling_asset_issuer": "GCKA6K5PCQ6PNF5RQBF7PQDJWRHO6UOGFMRLK3DYHDOI244V47XKQ4GP",
+        "offer_id": 126229447
+      },
+      {
+        "_links": {
+          "self": {
+            "href": "https://horizon-testnet.stellar.org/operations/113928152169844740"
+          },
+          "transaction": {
+            "href": "https://horizon-testnet.stellar.org/transactions/2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906"
+          },
+          "effects": {
+            "href": "https://horizon-testnet.stellar.org/operations/113928152169844740/effects"
+          },
+          "succeeds": {
+            "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=113928152169844740"
+          },
+          "precedes": {
+            "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=113928152169844740"
+          }
+        },
+        "id": "113928152169844740",
+        "paging_token": "113928152169844740",
+        "transaction_successful": true,
+        "source_account": "GDO2BIMNH7T6MOJVPKEJHWAGMYGOQU5QMK5BKT5XMVWPZKHAGA4JNAQZ",
+        "type": "manage_buy_offer",
+        "type_i": 12,
+        "created_at": "2019-10-28T19:44:09Z",
+        "transaction_hash": "2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906",
+        "amount": "0.0000000",
+        "price": "0.0001000",
+        "price_r": {
+          "n": 1,
+          "d": 10000
+        },
+        "buying_asset_type": "native",
+        "selling_asset_type": "credit_alphanum4",
+        "selling_asset_code": "SLT",
+        "selling_asset_issuer": "GCKA6K5PCQ6PNF5RQBF7PQDJWRHO6UOGFMRLK3DYHDOI244V47XKQ4GP",
+        "offer_id": 126229448
+      },
+      {
+        "_links": {
+          "self": {
+            "href": "https://horizon-testnet.stellar.org/operations/113928152169844741"
+          },
+          "transaction": {
+            "href": "https://horizon-testnet.stellar.org/transactions/2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906"
+          },
+          "effects": {
+            "href": "https://horizon-testnet.stellar.org/operations/113928152169844741/effects"
+          },
+          "succeeds": {
+            "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=113928152169844741"
+          },
+          "precedes": {
+            "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=113928152169844741"
+          }
+        },
+        "id": "113928152169844741",
+        "paging_token": "113928152169844741",
+        "transaction_successful": true,
+        "source_account": "GDO2BIMNH7T6MOJVPKEJHWAGMYGOQU5QMK5BKT5XMVWPZKHAGA4JNAQZ",
+        "type": "manage_buy_offer",
+        "type_i": 12,
+        "created_at": "2019-10-28T19:44:09Z",
+        "transaction_hash": "2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906",
+        "amount": "0.0000000",
+        "price": "0.0001000",
+        "price_r": {
+          "n": 1,
+          "d": 10000
+        },
+        "buying_asset_type": "native",
+        "selling_asset_type": "credit_alphanum4",
+        "selling_asset_code": "SLT",
+        "selling_asset_issuer": "GCKA6K5PCQ6PNF5RQBF7PQDJWRHO6UOGFMRLK3DYHDOI244V47XKQ4GP",
+        "offer_id": 126229449
+      }
+    ]
+  }
+}
+```
diff --git a/docs/data/apis/horizon/api-reference/structure/pagination/page-arguments.mdx b/docs/data/apis/horizon/api-reference/structure/pagination/page-arguments.mdx
index 8eb3f19cb..97d6a0a4b 100644
--- a/docs/data/apis/horizon/api-reference/structure/pagination/page-arguments.mdx
+++ b/docs/data/apis/horizon/api-reference/structure/pagination/page-arguments.mdx
@@ -1,42 +1,39 @@
 ---
 title: Page Arguments
-sidebar_position: 20
+description: "|     |                                                                    |"
 ---
 
-import { MethodTable } from "@site/src/components/MethodTable";
-
-<MethodTable>
-
 |     |                                                                    |
 | --- | ------------------------------------------------------------------ |
 | GET | `/{endpoint}?cursor={paging_token}&order={asc,desc}&limit={1-200}` |
 
-</MethodTable>
+<ParamField query="cursor">
+
+A number that points to a specific location in a collection of responses and is pulled from the `paging_token` value of a record.
+
+</ParamField>
+
+<ParamField query="order">
 
-<AttributeTable>
+A designation of the order in which records should appear. Options include `asc`(ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.
 
-- ARGUMENT
-  - REQUIRED?
-  - DESCRIPTION
-- cursor
-  - optional
-  - A number that points to a specific location in a collection of responses and is pulled from the `paging_token` value of a record.
-- order
-  - optional
-  - A designation of the order in which records should appear. Options include `asc`(ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.
-- limit
-  - optional
-  - The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
+</ParamField>
 
-</AttributeTable>
+<ParamField query="limit">
 
-<CodeExample title="Example Request">
+The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
 
-```curl
+</ParamField>
+
+### Example Request
+
+<CodeGroup>
+
+```curl cURL
 curl "https://horizon-testnet.stellar.org/ledgers/26478723/operations?cursor=113725249324879872&limit=5&order=asc"
 ```
 
-```js
+```js JavaScript
 var StellarSdk = require("@stellar/stellar-sdk");
 var server = new StellarSdk.Horizon.Server(
   "https://horizon-testnet.stellar.org",
@@ -57,11 +54,11 @@ server
   });
 ```
 
-</CodeExample>
+</CodeGroup>
 
-<ExampleResponse title="Example Response">
+### Example Response
 
-```json
+```json Example Response
 {
   "_links": {
     "self": {
@@ -265,5 +262,3 @@ server
   }
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/structure/rate-limiting.mdx b/docs/data/apis/horizon/api-reference/structure/rate-limiting.mdx
index 539a8ae09..466044664 100644
--- a/docs/data/apis/horizon/api-reference/structure/rate-limiting.mdx
+++ b/docs/data/apis/horizon/api-reference/structure/rate-limiting.mdx
@@ -1,6 +1,6 @@
 ---
 title: Rate Limiting
-sidebar_position: 40
+description: "Horizon rate limits on a per-IP-address basis."
 ---
 
 Horizon rate limits on a per-IP-address basis. It can be configured via the option `PER_HOUR_RATE_LIMIT` and defaults to 3600 requests per hour. It is recommended that operators of Horizon tune this value based on their individual infrastructural capabilities and usage needs.
diff --git a/docs/data/apis/horizon/api-reference/structure/response-format.mdx b/docs/data/apis/horizon/api-reference/structure/response-format.mdx
index f53969c3e..597575a0e 100644
--- a/docs/data/apis/horizon/api-reference/structure/response-format.mdx
+++ b/docs/data/apis/horizon/api-reference/structure/response-format.mdx
@@ -1,6 +1,6 @@
 ---
 title: Response Format
-sidebar_position: 20
+description: "Horizon delivers responses as JSON objects formatted according to HAL."
 ---
 
 Horizon delivers responses as JSON objects formatted according to [HAL](https://en.wikipedia.org/wiki/Hypertext_Application_Language). The HAL format makes Horizon more explorable, paginates responses, and connects parent and child resources. Consuming this format is simple using one of the many [open source libraries available](https://github.com/mikekelly/hal_specification/wiki/Libraries) for most major programming languages.
@@ -12,25 +12,21 @@ HAL is just JSON with two reserved attribute names:
 
 If a response is a single record, the `_links` section will provide links to any parent or child records, and there will be no `_embedded` property.
 
-If a response is a collection, the `_links` section will provide [pagination](./pagination/README.mdx) links, and the response’s list of records will be nested underneath the `_embedded` property.
+If a response is a collection, the `_links` section will provide [pagination](/docs/data/apis/horizon/api-reference/structure/pagination) links, and the response’s list of records will be nested underneath the `_embedded` property.
 
-<AttributeTable>
+<ResponseField name="_links" type="array">
 
-- ATTRIBUTES
-  - DATA TYPE
-  - DESCRIPTION
-- \_links
-  - array
-  - Provides links for navigating to other pages or to parents and children.
-- \_embedded
-  - array
-  - Present when querying an endpoint that responds with a collection of records.
+Provides links for navigating to other pages or to parents and children.
 
-</AttributeTable>
+</ResponseField>
 
-<ExampleResponse title="Example Response">
+<ResponseField name="_embedded" type="array">
 
-```json
+Present when querying an endpoint that responds with a collection of records.
+
+</ResponseField>
+
+```json Example Response
 {
   "_links": {
     "self": {
@@ -207,5 +203,3 @@ If a response is a collection, the `_links` section will provide [pagination](./
   }
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/structure/streaming.mdx b/docs/data/apis/horizon/api-reference/structure/streaming.mdx
index ad13f8ca3..01246d9c0 100644
--- a/docs/data/apis/horizon/api-reference/structure/streaming.mdx
+++ b/docs/data/apis/horizon/api-reference/structure/streaming.mdx
@@ -1,27 +1,21 @@
 ---
 title: Streaming
-sidebar_position: 30
+description: "Horizon provides a streaming mechanism for receiving events in near real time."
 ---
 
-import { MethodTable } from "@site/src/components/MethodTable";
-
 Horizon provides a streaming mechanism for receiving events in near real time. Instead of repeatedly sending requests to Horizon for batch updates, a connection is established between a client and Horizon with updates to an endpoint response streaming as new ledgers close and updates occur.
 
 This reduces requests that return no data and allows near instantaneous updates client-side.
 
 All attributes for the endpoints that allow streaming are the same as regular responses. A caller can initiate streaming by setting ‘Accept: text/event-stream’ in the HTTP header when making the request.
 
-<MethodTable title="Endpoints with Streaming">
-
-|                                                       |
-| ----------------------------------------------------- |
-| [Ledgers](../resources/ledgers/README.mdx)            |
-| [Transactions](../resources/transactions/README.mdx)  |
-| [Operations](../resources/operations/README.mdx)      |
-| [Payments](../resources/payments/README.mdx)          |
-| [Effects](../resources/effects/README.mdx)            |
-| [Accounts](../resources/accounts/README.mdx)          |
-| [Trades](../resources/trades/README.mdx)              |
-| [Order Books](../aggregations/order-books/README.mdx) |
-
-</MethodTable>
+| Endpoints with Streaming |
+| --- |
+| [Ledgers](/docs/data/apis/horizon/api-reference/resources/ledgers) |
+| [Transactions](/docs/data/apis/horizon/api-reference/resources/transactions) |
+| [Operations](/docs/data/apis/horizon/api-reference/resources/operations) |
+| [Payments](/docs/data/apis/horizon/api-reference/resources/payments) |
+| [Effects](/docs/data/apis/horizon/api-reference/resources/effects) |
+| [Accounts](/docs/data/apis/horizon/api-reference/resources/accounts) |
+| [Trades](/docs/data/apis/horizon/api-reference/resources/trades) |
+| [Order Books](/docs/data/apis/horizon/api-reference/aggregations/order-books) |
diff --git a/docs/data/apis/horizon/api-reference/structure/xdr.mdx b/docs/data/apis/horizon/api-reference/structure/xdr.mdx
index 4e5484099..bdf21ecb9 100644
--- a/docs/data/apis/horizon/api-reference/structure/xdr.mdx
+++ b/docs/data/apis/horizon/api-reference/structure/xdr.mdx
@@ -1,11 +1,11 @@
 ---
 title: XDR
-sidebar_position: 50
+description: "In the Stellar network, transactions are encoded using a standardized protocol called External Data Representation (XDR)."
 ---
 
 In the Stellar network, transactions are encoded using a standardized protocol called [External Data Representation](https://en.wikipedia.org/wiki/External_Data_Representation) (XDR).
 
-In Horizon, you will only encounter XDR when [posting](../submit-a-transaction.api.mdx) and [getting](../retrieve-a-transaction.api.mdx) transactions and in the [ledger](../resources/ledgers/README.mdx) header.
+In Horizon, you will only encounter XDR when [posting](/docs/data/apis/horizon/api-reference/submit-a-transaction) and [getting](/docs/data/apis/horizon/api-reference/retrieve-a-transaction) transactions and in the [ledger](/docs/data/apis/horizon/api-reference/resources/ledgers) header.
 
 When you post a transaction, a client will encode the transaction as XDR before submitting it to Horizon.
 
@@ -13,29 +13,31 @@ When you request a transaction, Horizon returns some data about the transaction
 
 You can decode this XDR on the Stellar Lab’s [XDR page](https://lab.stellar.org/xdr/view?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;;).
 
-<AttributeTable>
-
-- ATTRIBUTE
-  - TYPE
-  - DESCRIPTION
-- envelope_xdr
-  - string
-  - The XDR encoded transaction as stellar-core sees it.
-- result_xdr
-  - string
-  - The effects of a transaction encoded in XDR.
-- result_meta_xdr
-  - string
-  - The details about the effects of a transaction encoded in XDR.
-- fee_meta_xdr
-  - string
-  - The fees associated with the transaction encoded in XDR.
-
-</AttributeTable>
-
-<ExampleResponse title="Example Transaction Response with XDR">
-
-```json
+<ResponseField name="envelope_xdr" type="string">
+
+The XDR encoded transaction as stellar-core sees it.
+
+</ResponseField>
+
+<ResponseField name="result_xdr" type="string">
+
+The effects of a transaction encoded in XDR.
+
+</ResponseField>
+
+<ResponseField name="result_meta_xdr" type="string">
+
+The details about the effects of a transaction encoded in XDR.
+
+</ResponseField>
+
+<ResponseField name="fee_meta_xdr" type="string">
+
+The fees associated with the transaction encoded in XDR.
+
+</ResponseField>
+
+```json Example Transaction Response with XDR
 {
   // Response truncated to highlight XDR-related attributes
   "envelope_xdr": "AAAAAPewD+/6X8o0bx3bp49Wf+mUhG3o+TUrcjcst717DWJVAAAAyAFvzscADTkNAAAAAAAAAAAAAAACAAAAAAAAAAYAAAACWE1BVEsAAAAAAAAAAAAAAAPvNOuztX4IjvV8pztsEc1/ZnTz0G3p5Cx4vcf04+xUAAONfqTGgAAAAAAAAAAABQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAAD2NyeXB0b21hcmluZS5ldQAAAAAAAAAAAAAAAAF7DWJVAAAAQK3vfUCZ8mbjW3ssMd0n1tJTF9Fv6EbuJ6cWKkYXBqG5itqanPbFzIQoZEHbPS8nr2vo4dROvKI0uQzNcfExKwM=",
@@ -45,5 +47,3 @@ You can decode this XDR on the Stellar Lab’s [XDR page](https://lab.stellar.or
   // Response truncated to highlight XDR-related attributes
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/horizon/api-reference/submit-a-transaction.ParamsDetails.json b/docs/data/apis/horizon/api-reference/submit-a-transaction.ParamsDetails.json
deleted file mode 100644
index f4ae53d07..000000000
--- a/docs/data/apis/horizon/api-reference/submit-a-transaction.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"in":"query","name":"tx","schema":{"type":"string","description":"The base64-encoded XDR of the transaction."},"required":true}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/submit-a-transaction.RequestSchema.json b/docs/data/apis/horizon/api-reference/submit-a-transaction.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/submit-a-transaction.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/submit-a-transaction.StatusCodes.json b/docs/data/apis/horizon/api-reference/submit-a-transaction.StatusCodes.json
deleted file mode 100644
index c977045db..000000000
--- a/docs/data/apis/horizon/api-reference/submit-a-transaction.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"memo":{"type":"string"},"memo_bytes":{"type":"string"},"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"account":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"ledger":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","account","ledger","operations","effects","precedes","succeeds","transaction"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"successful":{"type":"boolean"},"hash":{"type":"string"},"ledger":{"type":"integer","format":"int32"},"created_at":{"type":"string"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"account_muxed":{"type":"string"},"account_muxed_id":{"type":"string"},"source_account_sequence":{"type":"string"},"fee_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed_id":{"type":"string"},"fee_charged":{"type":"string"},"max_fee":{"type":"string"},"operation_count":{"type":"integer","format":"int32"},"envelope_xdr":{"type":"string"},"result_xdr":{"type":"string"},"result_meta_xdr":{"type":"string"},"fee_meta_xdr":{"type":"string"},"memo_type":{"type":"string"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"},"preconditions":{"type":"object","properties":{"timebounds":{"type":"object","properties":{"min_time":{"type":"string"},"max_time":{"type":"string"}},"title":"TransactionPreconditionsTimebounds"},"ledgerbounds":{"type":"object","properties":{"min_ledger":{"type":"string"},"max_ledger":{"type":"string"}},"title":"TransactionPreconditionsLedgerbounds"},"min_account_sequence":{"type":"string"},"min_account_sequence_age":{"type":"string"},"min_account_sequence_ledger_gap":{"type":"integer","format":"uint32"},"extra_signers":{"type":"array","items":{"type":"string"}}},"title":"TransactionPreconditions"},"fee_bump_transaction":{"type":"object","properties":{"hash":{"type":"string","title":"hash"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"}},"title":"FeeBumpTransaction"},"inner_transaction":{"type":"object","properties":{"hash":{"type":"string","title":"hash"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"},"max_fee":{"type":"string"}},"title":"InnerTransaction"}},"required":["id","paging_token","successful","hash","ledger","created_at","source_account","source_account_sequence","fee_account","fee_charged","max_fee","operation_count","envelope_xdr","result_xdr","result_meta_xdr","memo_type","signatures"]}}}}},"title":"SubmitTransaction"},"examples":{"SubmitaTransaction":{"value":{"memo":"Test Transaction","memo_bytes":"VGVzdCBUcmFuc2FjdGlvbg==","_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/8ef0c6d60357bf91b0b0d7800b747ff02bf73117d3e017690cbff641ca67f124"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GCIHAQVWZH2AB5BB5NP63FBSIREG77LQZZNUVKD2LN2IOCLOT6N72MJN"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/139575"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/8ef0c6d60357bf91b0b0d7800b747ff02bf73117d3e017690cbff641ca67f124/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/8ef0c6d60357bf91b0b0d7800b747ff02bf73117d3e017690cbff641ca67f124/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=599470060347392"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=599470060347392"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/8ef0c6d60357bf91b0b0d7800b747ff02bf73117d3e017690cbff641ca67f124"}},"id":"8ef0c6d60357bf91b0b0d7800b747ff02bf73117d3e017690cbff641ca67f124","paging_token":"599470060347392","successful":true,"hash":"8ef0c6d60357bf91b0b0d7800b747ff02bf73117d3e017690cbff641ca67f124","ledger":139575,"created_at":"2021-03-25T21:14:11Z","source_account":"GCIHAQVWZH2AB5BB5NP63FBSIREG77LQZZNUVKD2LN2IOCLOT6N72MJN","source_account_sequence":"599336916353025","fee_account":"GCIHAQVWZH2AB5BB5NP63FBSIREG77LQZZNUVKD2LN2IOCLOT6N72MJN","fee_charged":"100","max_fee":"100","operation_count":1,"envelope_xdr":"AAAAAgAAAACQcEK2yfQA9CHrX+2UMkRIb/1wzltKqHpbdIcJbp+b/QAAAGQAAiEYAAAAAQAAAAEAAAAAAAAAAAAAAABgXP3QAAAAAQAAABBUZXN0IFRyYW5zYWN0aW9uAAAAAQAAAAAAAAABAAAAAJBwQrbJ9AD0Ietf7ZQyREhv/XDOW0qoelt0hwlun5v9AAAAAAAAAAAF9eEAAAAAAAAAAAFun5v9AAAAQKdJnG8QRiv9xGp1Oq7ACv/xR2BnNqjfUHrGNua7m4tWbrun3+GmAj6ca3xz+4ZppWRTbvTUcCxvpbHERZ85QgY=","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAABAAAAAAAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAAIhNwAAAAAAAAAAkHBCtsn0APQh61/tlDJESG/9cM5bSqh6W3SHCW6fm/0AAAAXSHbnnAACIRgAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAIhNwAAAAAAAAAAkHBCtsn0APQh61/tlDJESG/9cM5bSqh6W3SHCW6fm/0AAAAXSHbnnAACIRgAAAABAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMAAiEYAAAAAAAAAACQcEK2yfQA9CHrX+2UMkRIb/1wzltKqHpbdIcJbp+b/QAAABdIdugAAAIhGAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEAAiE3AAAAAAAAAACQcEK2yfQA9CHrX+2UMkRIb/1wzltKqHpbdIcJbp+b/QAAABdIduecAAIhGAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"text","signatures":["p0mcbxBGK/3EanU6rsAK//FHYGc2qN9QesY25rubi1Zuu6ff4aYCPpxrfHP7hmmlZFNu9NRwLG+lscRFnzlCBg=="]}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/submit-a-transaction.api.mdx b/docs/data/apis/horizon/api-reference/submit-a-transaction.api.mdx
deleted file mode 100644
index fb5a48270..000000000
--- a/docs/data/apis/horizon/api-reference/submit-a-transaction.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: submit-a-transaction
-title: "Submit a Transaction"
-description: "This endpoint actually submits a transaction to the Stellar network. It only takes a single, required parameter: the signed transaction. Refer to the Transactions page for details on how to craft a proper one. If you submit a transaction that has already been included in a ledger, this endpoint will return the same response as would’ve been returned for the original transaction submission. This allows for safe resubmission of transactions in error scenarios, as highlighted in the error-handling guide."
-sidebar_label: "Submit a Transaction"
-hide_title: true
-hide_table_of_contents: true
-api: eJztGttu2zryVwg97OnFjm+JXQcoztq5OG5TN9emTRoYFDWy2EikQlJ20iDA/sb+3n7JYijLlmwnTduDc7o464cENodz5wyHM3eOoSPtbF44J4oKTZnhUmjnsuR4oJniMX53Np2TgGsCwoslF4ZQZhIahrdEJ27EjSaUmPl2YiQxAZBjA2FIFRFgJlJdrZG+IVKEt8TQK8A9motRCCWi4DrhCjwSU0UjMKA2LQLNRwK8POo1cgQ+qIxCnmcS0xEQXyrigaE81EQKEsgJwjJFfUMoiZWMQREpYI30fXIrk6kEiwIE1JCAakJDBdS7JS6AIFywMPHAI1wQSkLwRqBKxBQ0M+FhSBSYRIlUBBoBUaBjKTQQqslEJqH3n3/9ewwp0hQWPMs57pCKj7igYYEhy6XWVgPWFDQM5UTbTZr6lsQMhEg/v1kjv6AUgjIQVHGpS8hKwEdByEeBSUVC4hasHFDhhVyMyCjhHqw5JQfVRhFZ33M2nWOrs05O+07JmdkOvenO4eg11wmoW6fkCBqBs+mYG6fkaBZARJ3NO8fcxvirNoqLkbPscUBcqqG5XgbBJOr94/aRlS2Agk849yUncyFn06gE7i/xl1TpGknVq1X8V6RwnDAGWjslh0lhQBgEoXEccmZlrXzRCHe3zLJ0vwAzKLR1KMNTKkOIXPA85OJboAqYVJ7OAVKlKOqKG4j0txFEEMllJd6X7MLQvTWgVy4PQy6unoBfQ+h/GypQ4K8ypS9VRI2z6SA1JGsgikNqCqpxpQyBCue+YL+LFOllyTHchJDDQRmTSWqlX4irNA78YkzNzusTLP2nMga+D8z8alzFChh48KuxpTFAgfersZWLvb8UZwtANoLNo8bspBZOx9wjc16Q03xR2sv7ksO9VeJknHDP+hMdcTEaGnkFYhk6s6zWfhKukrbkBFQHKzcuRRsuDKRSzTTKhWnUEZgpQIUOqVnNhEwUg+FyWJ1JFVNjQGGu7F10yufVcvvybmPjPicv9TyFOXQenodRcgMrdLQIMVylyCWuhhquExAMVsL68Mexn8P1kAg/i/EhkRGQBVSNHtBbRG+GPqxWwcyXh4tqeMwzQIwhlDEMbzy1Ei3eJ0PzreUIDH0QBqV6FMDeVNJfV/kBHwlqEgVPuSR900D3cwvlEE9DvxQef2KyNDwCVybiKUE54mKI8A/a9IHFHK+5K/ZBntGTORuzoPA9bC2FkSJjDy4/gbX9PDOIj4unHeZVgEM6+g7glO3hiMaPH4Nkfg5ujKJDW2eq7/Cz+6coIjsDbhLFw+/LmSuj/5yiXf+zjkju512AbhLF+boPE6IQoP6HBXwsvua29FHMgugL9w3uOQuZv5Dnp0k9dw3JpeelZPxwHixmvWLymIuynBgWgn4hxC8H9Hx0Ltjh8v6+4P3pW8CCS8ANjeIwtVoKQE+K/jGmYQLzOtY5AW1I8UEhX8g6H3ofvnpb3VMW7SasvvvF64Vjd/T6tZOvaLOaNb1zOoExsd6sVAKp+Fcpyga0EWDWdPoutSbVqJJ/J6m8Ar/Kml6z2thouX675lbdqtd6Va26rfWW71frrt9q1GotrwHVWqvZrjLX95vrNUabLb9WX18oUr+DjekuXelt9fc6hx/Ozvfqne5Gt7sxOGg2drvH/aOdXqu1f3h+Pjj98Ha7vj+o999v7b8/aQ5a9XdvBsW74XdQTjfpSq3R3mhtLNeOf5UuK3M27n5nidJSlUIecVOSygNlr1zzisE++hSqy7+M7ykPT2c6X3z+INe/W/SvqWb/SKm+3mi311vVarPaWG812vXFavLn6OAz2iOEFlLBX3cap9Wa89OYFis6Z1HqYkWHhs1quD+CeHaw0zNarOucerVeK1cb5frGSb22WVvfrNXOl/PJpvPDkeWRkgz10Gg027VmY6NRrW8sJKefIlooipxatZrLbtn3peKntljaOB38jPDP1iHbeVu/9Q877a099fFl/fTd1VHfrdQmX0Pz9novdr0+e+PGL93KYafT6R12Onznk92P3zs7neKnO/p40DicrXe7p+cfB9X+7tHtp7ONr5/OBlV61k7m+9NN9u+b7uRQuW/ane1qH4zfOj+8PdoJxpWP2+/PqtcSQlMNJmEiNsbtHMHdNuR52J2tH7713ojeq8MjPm7f9OLa++tWZ2tcuTmqd8Xg+ot/uqd6g4S2onVz5qpENF72os6XJqONm68v18/j+OzoxB2fnLKtm3Hs7u0cnb/aOBx9el28JEx12ZnqJvssypZ+Xq+4U+SN0cc/251OPxhM5ruu9rpbRotq5+AwaNYqJtx+s3Pcq7TZuw33+DponjWO97bOmn5UqSL4x+M9V4hOZ6t/NOo8/Fk0XJ7hP5R+dzWZx+gXFFasmHPaejd3Rfv5Tlfuen0vQUT9oPeInnKmXJaA7zR+jj6wH6Nv73i5pwLHwI0p3kk3L5y4GjH3ptt7W2nsUHHaVLrztlLZ3fvUY/XrQfsQ9Kf6hkpcXjtPkqbvr9NPWwfxjfL3DlpBFIXnu4OkPTia7Pdehpod7Yqv4VYX75fpfffePleYQGIsiqU2aZmB8b2QtJAvUOOsCZao8GmZb2X36ySFI4O0f+rclx7C6CeoiKfg3M0gs66sg70yLvy0mTS91O+leJ2Sg6Kku6tr1bWaTXRRRNXtHAq7qmPuYUdXkL2TkwPSOehj19WjhmaNxVW9YC5GoLF5LDyioGwVpy203Rkr6SUMPOLerkKRdmGxpk/btdiFpZqnzWEmhU4iyLbSMSjsDueae0RBSA0fQ9ZLjkHZBwLBoCwVB4FtUcuIgliBBmHS6yhJdMpUxtCWVDBty6LkOTlcxb0RNnrNBHu9NI5TaYs7D5TEKlmTkF8BmdAwBKNLxAMGwiga8q/gEbhhAUWFlSwGqjWgzDoBZTkimTWMzHraeccsEduLRRNNszNxaYjClgg2ho0CGhEYg8j4KHSQjcztXFvyrL+7J1zkDXr5LDueHqRXEaULt9wp2xUmFZSF9OD538p7PovPIiPHqCAu4BJo1OWYU8JOj/ZLhBJXyYnGCQtpJzayzv9M18fbb/U3de1JpitGylBXtHelUdOSKEB3stiYxIeKG25uEf+tTBR6Gyq0RCY4VsFkFIHw7KwIKooKJEy40Aaoh5sieoWzEh5XwIy1IaNhqK2c1qx2ioKkJ8YFnQ2lUC/igmsDimQubt0x0w2SQBWTZyo/83KxPZP0N9IN5Wiug8lkUhR+Bll2Qzmq0LKASVknooxZKIDyNH88T+dIJB4Tyq5GCh9viRSLpyH1HcUCboCZRNGQ8AjPPETW8tZCXJOIfpGKTFMHwffP52tkVyqCeQbfYPFn6srEkCmLqMApvZlrSA9w/qNEWADsiiB0Xn4kSXqo2rkCRtwEibvGZFSZ6iH7n4lacUPpViLKRWV758PO/vuD/qC3FnnPrbm64EsFaHgXRlyUCDe/4ciOMgFRwI2tNsQonewBge/3whBggZyP0FzgsSQD6f1IICCeZEmUBZhN8uLFBIgniZAGZ4yk0kBUIgQykSkKTZaGIUrQYzwa4nHJR4mZL714kQYA0DEwbke4ELXdOxzTkHtWwOFSbgN0fQXETCTRgLM+Bg+PYKDENKh4wGQSh1P9RBiGeRRLZagw1sFcadUYcuryEE8c7sq511rB9fF0RVTQEWiCI2ZyIko4IAZe2ZMTMXMv6RdFlbHhkQ16SHO6E4MahjzpE4FvIOTZBH6zk1qzk4VDVTiU9tnZorFNB4juszPTHbqIfcBRkX7vH4Mac1sDZ0YuPGQgUFn6NpVx+2qLM0aU2YfB6ThUxnbeoXfx6NHpC2jxsle82kFEuV2FMJT/zK/hSyBnIDTkaHViygIg9TUsm7mHvutzULOVcroypzgNJ9Supi+FKVJd2e9v7QyOd3DLWmCi0D604KU4oiIvXjZZV3zWLdwc7uajV/8fMfx7jxjmqrtKHFJuGwnWH++mpdaFUyi1LktOgJXY5oVzd4eZ4lSF9/f4czp2iAWYxzV1Q3xB8mmo4RHve3Y09ZDn5CFmruA2G2Kcti8cWz2NqeJIxdm8wAGRAKiHJ+vibrqjwxjEJrdracYQsczKy4P3xyfO/f1/AeP8/bM=
-sidebar_class_name: "post api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Submit a Transaction"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/transactions"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint actually submits a transaction to the Stellar network. It only takes a single, required parameter: the signed transaction. Refer to the Transactions page for details on how to craft a proper one. If you submit a transaction that has already been included in a ledger, this endpoint will return the same response as would’ve been returned for the original transaction submission. This allows for safe resubmission of transactions in error scenarios, as highlighted in the error-handling guide.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./submit-a-transaction.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./submit-a-transaction.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./submit-a-transaction.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/submit-a-transaction.mdx b/docs/data/apis/horizon/api-reference/submit-a-transaction.mdx
new file mode 100644
index 000000000..eae6fdc96
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/submit-a-transaction.mdx
@@ -0,0 +1,4 @@
+---
+title: Submit a Transaction
+openapi: "openapi/horizon/bundled.yml POST /transactions"
+---
diff --git a/docs/data/apis/horizon/api-reference/submit-async-transaction.ParamsDetails.json b/docs/data/apis/horizon/api-reference/submit-async-transaction.ParamsDetails.json
deleted file mode 100644
index f4ae53d07..000000000
--- a/docs/data/apis/horizon/api-reference/submit-async-transaction.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"in":"query","name":"tx","schema":{"type":"string","description":"The base64-encoded XDR of the transaction."},"required":true}]}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/submit-async-transaction.RequestSchema.json b/docs/data/apis/horizon/api-reference/submit-async-transaction.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/data/apis/horizon/api-reference/submit-async-transaction.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/submit-async-transaction.StatusCodes.json b/docs/data/apis/horizon/api-reference/submit-async-transaction.StatusCodes.json
deleted file mode 100644
index 7af2074ff..000000000
--- a/docs/data/apis/horizon/api-reference/submit-async-transaction.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"201":{"description":"Transaction has been received by core and is in pending status.","content":{"application/json":{"schema":{"type":"object","properties":{"error_result_xdr":{"type":"string","nullable":true,"description":"TransactionResult XDR string which is present only if the submission status from core is an ERROR."},"tx_status":{"type":"string","enum":["ERROR","PENDING","DUPLICATE","TRY_AGAIN_LATER"],"description":"Status of the transaction submission."},"hash":{"type":"string","description":"Hash of the transaction."}},"title":"AsyncTransactionSubmissionResponse"},"examples":{"TransactionPending":{"summary":"Transaction Pending","value":{"tx_status":"PENDING","hash":"6cbb7f714bd08cea7c30cab7818a35c510cbbfc0a6aa06172a1e94146ecf0165"}}}}}},"400":{"description":"Transaction is malformed; ERROR status from core.","content":{"application/json":{"schema":{"oneOf":[{"type":"object","properties":{"error_result_xdr":{"type":"string","nullable":true,"description":"TransactionResult XDR string which is present only if the submission status from core is an ERROR."},"tx_status":{"type":"string","enum":["ERROR","PENDING","DUPLICATE","TRY_AGAIN_LATER"],"description":"Status of the transaction submission."},"hash":{"type":"string","description":"Hash of the transaction."}},"title":"AsyncTransactionSubmissionResponse"},{"type":"object","properties":{"type":{"type":"string","description":"Identifies the problem type."},"title":{"type":"string","description":"A short, human-readable summary of the problem type."},"status":{"type":"integer","description":"The HTTP status code for this occurrence of the problem."},"detail":{"type":"string","description":"A human-readable explanation specific to this occurrence of the problem."},"extras":{"type":"object","additionalProperties":true,"description":"Additional details that might help the client understand the error(s) that occurred."}},"title":"Problem"}]},"examples":{"TransactionMalformed":{"summary":"Transaction Malformed","value":{"type":"transaction_malformed","title":"Transaction Malformed","status":400,"detail":"Horizon could not decode the transaction envelope in this request. A transaction should be an XDR TransactionEnvelope struct encoded using base64. The envelope read from this request is echoed in the `extras.envelope_xdr` field of this response for your convenience.","extras":{"envelope_xdr":""}}},"TransactionError":{"summary":"ERROR Status from core","value":{"error_result_xdr":"AAAAAAAAAGT////7AAAAAA==","tx_status":"ERROR","hash":"6cbb7f714bd08cea7c30cab7818a35c510cbbfc0a6aa06172a1e94146ecf0165"}}}}}},"403":{"description":"Transaction submission has been disabled for Horizon.","content":{"application/json":{"schema":{"type":"object","properties":{"type":{"type":"string","description":"Identifies the problem type."},"title":{"type":"string","description":"A short, human-readable summary of the problem type."},"status":{"type":"integer","description":"The HTTP status code for this occurrence of the problem."},"detail":{"type":"string","description":"A human-readable explanation specific to this occurrence of the problem."},"extras":{"type":"object","additionalProperties":true,"description":"Additional details that might help the client understand the error(s) that occurred."}},"title":"Problem"},"examples":{"TransactionSubmissionDisabled":{"summary":"Transaction Submission Disabled","value":{"type":"transaction_submission_disabled","title":"Transaction Submission Disabled","status":403,"detail":"Transaction submission has been disabled for Horizon. To enable it again, remove env variable DISABLE_TX_SUB.","extras":{"envelope_xdr":""}}}}}}},"409":{"description":"Transaction is a duplicate of a previously submitted transaction.","content":{"application/json":{"schema":{"type":"object","properties":{"error_result_xdr":{"type":"string","nullable":true,"description":"TransactionResult XDR string which is present only if the submission status from core is an ERROR."},"tx_status":{"type":"string","enum":["ERROR","PENDING","DUPLICATE","TRY_AGAIN_LATER"],"description":"Status of the transaction submission."},"hash":{"type":"string","description":"Hash of the transaction."}},"title":"AsyncTransactionSubmissionResponse"},"examples":{"TransactionDuplicate":{"summary":"Transaction Duplicate","value":{"tx_status":"DUPLICATE","hash":"6cbb7f714bd08cea7c30cab7818a35c510cbbfc0a6aa06172a1e94146ecf0165"}}}}}},"500":{"description":"Transaction submission failure, exception or invalid status from core.","content":{"application/json":{"schema":{"type":"object","properties":{"type":{"type":"string","description":"Identifies the problem type."},"title":{"type":"string","description":"A short, human-readable summary of the problem type."},"status":{"type":"integer","description":"The HTTP status code for this occurrence of the problem."},"detail":{"type":"string","description":"A human-readable explanation specific to this occurrence of the problem."},"extras":{"type":"object","additionalProperties":true,"description":"Additional details that might help the client understand the error(s) that occurred."}},"title":"Problem"},"examples":{"TransactionFailed":{"summary":"Transaction Submission Failed","value":{"type":"transaction_submission_failed","title":"Transaction Submission Failed","status":500,"detail":"Could not submit transaction to stellar-core. The `extras.error` field on this response contains further details. Descriptions of each code can be found at: https://developers.stellar.org/api/errors/http-status-codes/horizon-specific/transaction-submission-async/transaction_submission_failed","extras":{"envelope_xdr":"","error":"Error details here"}}},"TransactionException":{"summary":"Transaction Submission Exception","value":{"type":"transaction_submission_exception","title":"Transaction Submission Exception","status":500,"detail":"Received exception from stellar-core. The `extras.error` field on this response contains further details. Descriptions of each code can be found at: https://developers.stellar.org/api/errors/http-status-codes/horizon-specific/transaction-submission-async/transaction_submission_exception","extras":{"envelope_xdr":"","error":"Exception details here"}}},"TransactionInvalidStatus":{"summary":"Transaction Submission Invalid Status","value":{"type":"transaction_submission_invalid_status","title":"Transaction Submission Invalid Status","status":500,"detail":"Received invalid status from stellar-core. The `extras.error` field on this response contains further details.  Descriptions of each code can be found at: https://developers.stellar.org/api/errors/http-status-codes/horizon-specific/transaction-submission-async/transaction_submission_invalid_status","extras":{"envelope_xdr":"","error":"Error details here"}}}}}}},"503":{"description":"History DB is stale; core is unavailable for transaction submission.","content":{"application/json":{"schema":{"oneOf":[{"type":"object","properties":{"error_result_xdr":{"type":"string","nullable":true,"description":"TransactionResult XDR string which is present only if the submission status from core is an ERROR."},"tx_status":{"type":"string","enum":["ERROR","PENDING","DUPLICATE","TRY_AGAIN_LATER"],"description":"Status of the transaction submission."},"hash":{"type":"string","description":"Hash of the transaction."}},"title":"AsyncTransactionSubmissionResponse"},{"type":"object","properties":{"type":{"type":"string","description":"Identifies the problem type."},"title":{"type":"string","description":"A short, human-readable summary of the problem type."},"status":{"type":"integer","description":"The HTTP status code for this occurrence of the problem."},"detail":{"type":"string","description":"A human-readable explanation specific to this occurrence of the problem."},"extras":{"type":"object","additionalProperties":true,"description":"Additional details that might help the client understand the error(s) that occurred."}},"title":"Problem"}]},"examples":{"HistoryDBStale":{"summary":"Historical DB Is Too Stale","value":{"type":"stale_history","title":"Historical DB Is Too Stale","status":503,"detail":"This horizon instance is configured to reject client requests when it can determine that the history database is lagging too far behind the connected instance of Stellar-Core or read replica. It's also possible that Stellar-Core is out of sync. Please try again later.","extras":{"envelope_xdr":""}}},"TransactionTryAgainLater":{"summary":"TRY_AGAIN_LATER Status from core","value":{"tx_status":"TRY_AGAIN_LATER","hash":"6cbb7f714bd08cea7c30cab7818a35c510cbbfc0a6aa06172a1e94146ecf0165"}}}}}}}}
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/submit-async-transaction.api.mdx b/docs/data/apis/horizon/api-reference/submit-async-transaction.api.mdx
deleted file mode 100644
index bff027d14..000000000
--- a/docs/data/apis/horizon/api-reference/submit-async-transaction.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: submit-async-transaction
-title: "Submit a Transaction Asynchronously"
-description: "This endpoint submits transactions to the Stellar network asynchronously. It is designed to allow users to submit transactions without blocking them while waiting for a response from Horizon. At the same time, it also provides clear response status codes from stellar-core to help understand the status of the submitted transaction. You can then use Horizon's [GET transaction endpoint](https://developers.stellar.org/docs/data/apis/horizon/api-reference/retrieve-a-transaction) to wait for the transaction to be included in a ledger and ingested by Horizon."
-sidebar_label: "Submit a Transaction Asynchronously"
-hide_title: true
-hide_table_of_contents: true
-api: eJztW1tvG7cS/isDviQOVpLd3FoXBY4SO4lxfBzDVg5aOIHL5Y60bLjkluRKdg3/94Mh96aLI7cnfShivwjWksOZ4TfXHd2wDJ2wsvTSaLbPJrl0gDorjdQeXJUW0jvwlmvHBa1x4A34HOHco1Lcgka/MPYzcHetRW6NNpVT10M48iAdZOjkTGNGu7hSZgGVQxuIROLLtBfS56bykCojPks9o5MKWORSISy49PTV1FjgYNGVRjuEqTUFvDNW/mH0EMY+MOd4geBlgQlID1w5A6U1c5mhA6GQ226/89xXDoShZ4GYi5INhLFIjOaoSqh0htZ5rrN4QNxlpvG/IIonMTtphvCLqUBwTUs0yd2w+cjBxdvDSX9xq/NPj3PvS7c/GmU4R2VKtG5YczQ0djbKjHCjjHs+4qV0ozySpH8GFqdoUQscWfRW4hwHfNA7ZIekITUGHRLjfQ68gRRBaqGqDDOQGjgozGZogaSWeoaOREyvW3WzhBGDnPYfZWyfnQdFjAkKk440S5jnM8f2L1jvW8c+Jazklhfo0dLTGyYJg79XaK9ZwjQvkO0zf8US5kSOBWf7N8xfl/St81bqGUvW8IuQcocvng1Q051m8PPBWXNP/dthtwmz+HslLWZs39sKbz/RNxEWjo76bnePPlZO6Kks5w5SRA0WBcp5VE6ATdCYIyWWqDOCbUQMqUwY7VF7Is3LUkkR9Df6zRH9m3VRTfobCs8SVlrStpeRO7TW2EuLrlL+8iqzm5SjK6V4qjAKuKasTpSzQCboKm4moxM5yVBadKg9GK2uQfYA7xzpoLaEYDlBdOmAazg8O3t/FpTsry7jmk0Moq4KwkVYzhJ2enhycHTyliXs4MPp8dHr8eSQJWxy9svl+O346OTyeDw5PCPgLEtyvmSOfVR3nAZmcu7y7Sh6x12+GTMkj/SkULaK8vP2pLMaRHQgXvGiVPHGeotPIyrCfVdFwe31CrSaBQmbc1Vh4LlTZE9PUSL2QqTpy+nLvWdptvu9QP5SPN0VPH35/d73/Olz8XxvV6TpVOzyF5zvvth7+R3fwx+e7T17gWK6u/fiObsNfwl7trv7ZdBLBwVXU2MLzH6M97wGgj8Fc6Px/TSY/wPg//GA33aJ8ek2fo4y1F5OJbrAUmlNqrAA2hRVHFnaRmYMLjfWJ5BXBdcDizwjcEBtco3Ea+TXrk9qjzO0G8PNu8nktJ9F1MFVOjBCVDYE5JWTwiEZei7VfYRY4R6vSsU1j7ddopBTKWJWtvVMvPKWu02xhWeZJIpcnfbua5MRjduVEEWgO+IeCjnLfUyW6FihJBnRSt4UbPix24lbamazZZydRobZ7ae7/ed/Gg90twftlvR9aBS7h/HLoreuYeEuOg0wnu3udhfI6nQIhKlUBtp4yDAgYdU2UceUjvKCcFuUgKDzQxgv23AeKKWURwQX1ePnsKHhvK2EhybNqRw5sZj7DIGA2Z5GyIn+qn8o+S0UuYm5HrH6a4THsNlITvZXmEpUWQRT2Nzk3cbCtaksCKPnqCVBjtx+B7E+GbbPWAgvfUkIC8v3F6PJ+YqH7V/gehBg4+bv7WQ0Go1exn9++oktueLW4379gPn0ywGzFzvahDGTjmw5C2rspdNfKTd88LIPXva+XvZOH9vF94MarXc7224ttIu/7HY7q7jMuh2bHPBm2p0rftpzxX/J7mBiAHW4deoWzLjUCVgszDw4UZhzK8PTg6Pz8avjw8vJz5fnH15t9XaNf/hha0LNIauitQdAccpB5zJ0Uu5oLjzUkd9UWn2XjR40sLnbNLsld9SSfQ197eD4fFs12UPAlEtVWUwArwSGtWAsSD3nSmb/X4n5EC0fouXfHC3fcHnfCFkvvXd8nDbrt0THlm6DledLZcrrtjxZb72Hhnyv7x0riLYgIA21lYBeqQTICrnUDqaV9Tna5gqGcNBdUnCqyEUe8Uht8ZRgWekMuN+HLV1vXspR4MKNaOUgSjgIXfumBz5ogDfqCTbo9DgIryhG25R8d0hPYqykWoI+W6jlaHG9ummc2L0g0a2+Nyqwt2ULMPrUN2PjrGlgd7537V3It4eJvorvBYtWeV+ExlEMaeetR98Kj3pHXRnfHyN18Gxi/VagrJ2zBS2bgvPXh8w/CjNrKv/r/qRJoTb0F95J5429hoNXlCc7zxX+2KbNleZzLkPCHgP/HXnsQ4/+2ywmHvLhh3z47+rR147p4NU5+aTl4BafScEV+a0jBxNjIK5bj2jBp13mkVwvcn2RSBeulppCpPTauYPUJKkILkEYPZWzysb5FIuk50YpdZfcwYKmN6QPoSajUYVCaoy6IW3VHAKNZFD3negqPpuF6RVjYMotpJjLWrnCaI3Ch9hZM2KmzTDN4DX5KmNjx95i8Mg0SvPI1UMsxjlJ+ArHL+0iXFWeiJELGMKpQuLG2+vY0QLFPdo/16Gf2Osx7T2mrSuJyrL3+2LPvt9sWPWaX7vlcJuwAn1uaBqlNC44N+7pgH7AdpchhhNi0M6b6ZPKElqaDKLJBjw6r9H304iNPmYS18FJHIgKfnYzxWnlK4v3ofmmWdmMWTEaUpF6aoJeG5OIdEnlaF3cvTvcHe6RfJ311QbQDkJxHf3i+PSI4E8Abt4ErQx3xWmuMADkwmiLxUFQXHT9YWdpTVaJOAKzaT4szBPRi7SIXXr5xJ1ES0cLo11VYLOVz9HyGUIvJQGLins5x2b8rERLxMiABsaSxWIWGbFYJwc85ouVi0w1DL2u81LpguQ9OVIrsxlCin5BvWJellHa5Z2n1pCfcKDkZ5pKUwq9S+iVH2pvuZJ/xDIq56SwJFDgziHJ7CoafuuNgt0xCJdAGIKiK+JCmEp7SLkiYRNyD85b5AXgHHXDx+qIXrdzuJ5JfONIuOhf6NaBu5rtEXm1gTYZ7nxT6PmoP+r2BXestrgQ6EiXc8lBfDg7ToBDas3CoQ0nGN1mNq2uzw/+7e433OiNUW7kss9uJ7yasUhwqqMnJRpX0oe8MLx+LqNCE1jQi25higJ1Ro+Corimg0OspZBqplDwMFiaSUvBnu5QcKVckDNc66ySGUK0mBQpcVgElWSF1NJ5GoesIR7g+G41r3gcxjAbdF4ctJI+glfKzDodLBaLZeHblYNUmdmIDzQuBq7SA4pCOQ7q+LETsldnyEy4+Dyzofg1etUaInasyKVH4SvLFciCbB6LcPPNK/2C/2Ys1KED0qood4bwJrTeA6kgJk8pu6hZJAXW53WzDxlS+pOAyFF8DrlIX346Et6SajsFzKTPq3QoTDGq9dB8NqKOUmXSUcGlHh0c/vfw+P3p0cnbYZHthOt6hVPKfBZkdDN6ZycpUVoY63OwKH2YTI1DxEBuQAYmlmceLkLydGKyv+IIIDOiKhoHsw9PniwQMhN6rKgzYx2CrbQmJhpF0ZVFN8Qh5Nxckbn0vUSLpSdPogPAUEJwpa4D6bD3MrQZgoCXa7ENCfo0vbww4JCGbH1IPQVaXTsVGlGhN0PNkDVNqxalsZ7rOB+cmqBGJXkqFVkc7erBa7gEfbKugms+Qwc0Mm4WOoGSW8wGmVnoFl5dshtFNaWXRXB6dGa9k5wauTwzBY2YOXi8wEdKQc+yqKCn96Yf2WtehnBA5D6yVncEESob0Bbu/fQc7VwK7CVj/ZsNiwZmGkIZLYudES5CZ6SeQ27Y7gP6DZkerzuEy8necmqHRSxFclTK/Kv/7DZhSgqkyrw7a1xykSN8N9xlCZNNoW3bJ4P4pDuxdic8PA0y1UTd6Pjo9eHJ+SFtGea+UKGOo9S44LovXowjvD9rBOOlof7VROKm6x89/HDg4YcDf+6HA03jGq/8qFRcarKEAOibumK7YBsqtk8Jy6ms279gNzcUcD5YdXtLX8efDVAd186T7E+5cqvNkT5qH5/VvwDYgbtY+ozXzY8Q6oKWhSKsGQph+xfUA8mRZ2SgFzf1jrGgdwG9XWsNVqLS1qqn788n7Pb2fz2rZSE=
-sidebar_class_name: "post api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Submit a Transaction Asynchronously"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/transactions_async"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint submits transactions to the Stellar network asynchronously. It is designed to allow users to submit transactions without blocking them while waiting for a response from Horizon. At the same time, it also provides clear response status codes from stellar-core to help understand the status of the submitted transaction. You can then use Horizon's [GET transaction endpoint](https://developers.stellar.org/docs/data/apis/horizon/api-reference/retrieve-a-transaction) to wait for the transaction to be included in a ledger and ingested by Horizon.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./submit-async-transaction.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./submit-async-transaction.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./submit-async-transaction.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/docs/data/apis/horizon/api-reference/submit-async-transaction.mdx b/docs/data/apis/horizon/api-reference/submit-async-transaction.mdx
new file mode 100644
index 000000000..9fcff5b04
--- /dev/null
+++ b/docs/data/apis/horizon/api-reference/submit-async-transaction.mdx
@@ -0,0 +1,4 @@
+---
+title: Submit a Transaction Asynchronously
+openapi: "openapi/horizon/bundled.yml POST /transactions_async"
+---
diff --git a/docs/data/apis/horizon/index.mdx b/docs/data/apis/horizon/index.mdx
new file mode 100644
index 000000000..b5b741277
--- /dev/null
+++ b/docs/data/apis/horizon/index.mdx
@@ -0,0 +1,40 @@
+---
+title: Horizon Introduction
+sidebarTitle: Horizon
+"og:title": "Access Blockchain Data with Horizon API: Query Transactions, Accounts & More"
+description: "Learn how Horizon, the API for the Stellar network, enables access to blockchain data. Discover endpoints for querying transactions, accounts, and more."
+---
+
+<Info>
+
+On August 1, 2024, the publicly accessible SDF-hosted Horizon had its historical data truncated to one year. That update optimized the performance of the publicly accessible Horizon and ensured a streamlined experience for all users. Consider third-party ecosystem providers of Horizon, which may provide a longer history retention window as well as other features.
+
+</Info>
+
+Horizon provides an HTTP API to data in the Stellar network. It ingests and re-serves the data produced by the Stellar network in a form that is easier to consume by the average application relative to the performance-oriented data representations used by Stellar Core. This API serves the bridge between apps and [Stellar Core](/docs/validators). Projects like wallets, decentralized exchanges, and asset issuers use Horizon to submit transactions, query an account balance, or stream events like transactions to an account.
+
+Horizon can be accessed via cURL, a browser, or one of the [Stellar SDKs](/docs/tools/sdks). To reduce the complexity of your project, we recommend you use an SDK instead of making direct API calls.
+
+This guide describes how to administer a production Horizon instance (refer to the [Developers' Blog](https://stellar.org/blog/developers/a-new-sun-on-the-horizon) for some background on the performance and architectural improvements of this major version bump). For information about developing on the Horizon codebase, check out the [Development Guide](https://github.com/stellar/stellar-horizon/blob/main/DEVELOPING.md).
+
+Before we begin, it's worth reiterating the sentiment echoed in the [Core Node](/docs/validators) documentation: **we do not endorse running Horizon backed by a standalone Stellar Core instance**, and especially not by a _validating_ Stellar Core. These are two separate concerns, and decoupling them is important for both reliability and performance. Horizon instead manages its own, pared-down version of Stellar Core optimized for its own subset of needs (we'll refer to this as a "Captive Core" instance).
+
+## Why Run Horizon?
+
+Running Horizon within your own infrastructure provides a number of benefits. You can:
+
+- Have full operational control without dependency on the Stellar Development Foundation for network data and transaction submission to networks;
+- Run multiple instances for redundancy and scalability.
+
+The Stellar Development Foundation (SDF) runs two instances of Horizon:
+
+- [horizon-testnet.stellar.org](https://horizon-testnet.stellar.org) for interacting with the [testnet](/docs/networks)
+- [horizon-futurenet.stellar.org](https://horizon-futurenet.stellar.org) for interacting with the [futurenet](/docs)
+
+## In These Docs
+
+- [Admin Guide](/docs/data/apis/horizon/admin-guide): how to set up your own Horizon instance.
+- [Structure](/docs/data/apis/horizon/api-reference/structure): how Horizon is structured.
+- [Resources](/docs/data/apis/horizon/api-reference/resources): descriptions of resources and their endpoints.
+- [Aggregations](/docs/data/apis/horizon/api-reference/aggregations): descriptions of specialized endpoints.
+- [Errors](/docs/data/apis/horizon/api-reference/errors): potential errors and what they mean.
diff --git a/docs/data/apis/horizon/providers.mdx b/docs/data/apis/horizon/providers.mdx
index 1ce491078..127f8e9ce 100644
--- a/docs/data/apis/horizon/providers.mdx
+++ b/docs/data/apis/horizon/providers.mdx
@@ -1,13 +1,13 @@
 ---
-sidebar_position: 60
 title: Providers
+description: "On August 1, 2024, the publicly accessible SDF-hosted Horizon had its historical data truncated to one year."
 ---
 
-:::info
+<Info>
 
 On August 1, 2024, the publicly accessible SDF-hosted Horizon had its historical data truncated to one year. That update optimized the performance of the publicly accessible Horizon and ensured a streamlined experience for all users. Consider third-party ecosystem providers of Horizon, which may provide a longer history retention window as well as other features.
 
-:::
+</Info>
 
 Multiple infrastructure providers have made Horizon services available, and offer plans ranging from free to dedicated instances. These providers can be used for development, testing, and production.
 
diff --git a/docs/data/apis/index.mdx b/docs/data/apis/index.mdx
new file mode 100644
index 000000000..3e08493f2
--- /dev/null
+++ b/docs/data/apis/index.mdx
@@ -0,0 +1,36 @@
+---
+title: APIs Overview
+description: "Learn about the services that provide access to real-time Stellar network data."
+---
+
+| Features                | RPC | Horizon |
+| ----------------------- | --- | ------- |
+| Real-time Data          | ✅  | ✅      |
+| Historical Data         | ❌  | ❌\*    |
+| Smart Contracts         | ✅  | ❌      |
+| Transaction Simulation  | ✅  | ❌      |
+| Curated and Parsed Data | ❌  | ✅      |
+
+\*_Horizon can provide full historical data if you run your own instance, but it is not the recommended tool for that. Use [Hubble](/docs/data/analytics/hubble) or [Galexie](/docs/data/indexers/build-your-own/galexie) instead. For a side-by-side comparison of all four SDF data products, see [Compare Data Products](/docs/data#compare-data-products)._
+
+## [RPC](/docs/data/apis/rpc)
+
+The RPC provides real-time access to the current state of the Stellar network, including account balances, smart contract states, and recent transaction queries (within a seven-day retention window), while also allowing transaction submission. It is designed to be simple, minimal, and scalable, making it ideal for applications and wallets that require live data availability.
+
+<Note>
+
+RPC is the recommended API for accessing and interacting with Stellar network data in real-time.
+
+</Note>
+
+## [Horizon](/docs/data/apis/horizon)
+
+<Warning>
+
+Horizon is nearing end-of-life and will eventually be deprecated in favor of Stellar RPC and [Portfolio APIs](/docs/data/indexers#portfolio-apis). While it will continue to receive updates to maintain compatibility with upcoming protocol releases, it won't receive new feature development.
+
+If your application already uses Horizon, see [Migrate from Horizon to RPC](/docs/data/apis/migrate-from-horizon-to-rpc).
+
+</Warning>
+
+Horizon is an API for accessing and interacting with Stellar network data.
diff --git a/docs/data/apis/migrate-from-horizon-to-rpc.mdx b/docs/data/apis/migrate-from-horizon-to-rpc.mdx
index 918adf229..dda08724e 100644
--- a/docs/data/apis/migrate-from-horizon-to-rpc.mdx
+++ b/docs/data/apis/migrate-from-horizon-to-rpc.mdx
@@ -1,12 +1,11 @@
 ---
 title: Migrate from Horizon to RPC
-sidebar_position: 100
-hide_table_of_contents: true
+description: "Applications using [Horizon's REST-like API] will need to be updated to use the [RPC JSON-RPC API] when migrating from [Horizon] to [RPC]."
 ---
 
 Applications using [Horizon's REST-like API] will need to be updated to use the [RPC JSON-RPC API] when migrating from [Horizon] to [RPC]. This guide provides an overview of the key differences between the two APIs and how to migrate your application.
 
-## Request / Response Format
+## Request / Response Format {#request--response-format}
 
 Horizon's REST-like API uses HTTP methods and status codes to communicate with clients. Responses are JSON in the HAL format. See [Horizon's Response Format].
 
@@ -24,60 +23,59 @@ Endpoints without mappings do not have a direct replacement in the RPC API. To b
 
 | Horizon Endpoint | Corresponding RPC Method(s) | Indexer Equivalent | Analytics Resources |
 | --- | --- | --- | --- |
-| [`GET /`] | [`getLatestLedger`] [`getVersionInfo`] [`getHealth`] [`getNetwork`] | Not applicable | [Analyst Guide](../analytics/hubble/analyst-guide/README.mdx) |
-| [`GET /ledgers`] | [`getLedgers`] | Create a [`getLedgers`] with full history, using [Galexie](../indexers/build-your-own/galexie/README.mdx), to build a historical ledger view. | [Ledgers](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#ledgers) |
-| [`GET /ledgers/{seq}`] | [`getLedgers`] (with filter for sequence) | Use a [`getLedgers`] view with full history, filtered by ledger sequence | [Ledgers](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#ledgers) |
-| [`GET /ledgers/{seq}/transactions`] | [`getTransactions`] (with filter for ledger sequence) | Use [`getTransactions`] with ledger sequence filtering to retrieve transactions for a specific ledger | [Transactions](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#transactions) |
-| [`GET /ledgers/{seq}/operations`] | [`getTransactions`] | Use [`getTransactions`] for the given ledger, then parse the transaction's XDR for individual operations. | [Operations](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#operations) |
-| [`GET /ledgers/{seq}/payments`] | [`getEvents`] [`getTransactions`] ⚠️ | Use [`getEvents`] (CAP-67 asset events, available since Protocol 23 on nodes that emit classic events) and parse [`getTransactions`] meta XDR to tie those events back to individual operations. | [Payments](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#payments) |
-| [`GET /ledgers/{seq}/effects`] | [`getEvents`] [`getTransactions`] ⚠️ | Use [`getEvents`] for the effects CAP-67 models (asset movement and trustline authorization), and parse [`getTransactions`] meta XDR for every other effect type. | [Effects](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#effects) |
+| [`GET /`] | [`getLatestLedger`] [`getVersionInfo`] [`getHealth`] [`getNetwork`] | Not applicable | [Analyst Guide](/docs/data/analytics/hubble/analyst-guide) |
+| [`GET /ledgers`] | [`getLedgers`] | Create a [`getLedgers`] with full history, using [Galexie](/docs/data/indexers/build-your-own/galexie), to build a historical ledger view. | [Ledgers](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#ledgers) |
+| [`GET /ledgers/{seq}`] | [`getLedgers`] (with filter for sequence) | Use a [`getLedgers`] view with full history, filtered by ledger sequence | [Ledgers](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#ledgers) |
+| [`GET /ledgers/{seq}/transactions`] | [`getTransactions`] (with filter for ledger sequence) | Use [`getTransactions`] with ledger sequence filtering to retrieve transactions for a specific ledger | [Transactions](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#transactions) |
+| [`GET /ledgers/{seq}/operations`] | [`getTransactions`] | Use [`getTransactions`] for the given ledger, then parse the transaction's XDR for individual operations. | [Operations](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#operations) |
+| [`GET /ledgers/{seq}/payments`] | [`getEvents`] [`getTransactions`] ⚠️ | Use [`getEvents`] (CAP-67 asset events, available since Protocol 23 on nodes that emit classic events) and parse [`getTransactions`] meta XDR to tie those events back to individual operations. | [Payments](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#payments) |
+| [`GET /ledgers/{seq}/effects`] | [`getEvents`] [`getTransactions`] ⚠️ | Use [`getEvents`] for the effects CAP-67 models (asset movement and trustline authorization), and parse [`getTransactions`] meta XDR for every other effect type. | [Effects](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#effects) |
 | [`POST /transactions`] | [`sendTransaction`] | Not applicable | Not applicable |
 | [`POST /transactions_async`] | [`sendTransaction`] | Not applicable | Not applicable |
-| [`GET /transactions`] | [`getTransactions`] | Use [`getTransactions`] to build a historical transaction list | [Transactions](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#transactions) |
-| [`GET /transactions/{hash}`] | [`getTransaction`] | Use getTransaction to retrieve a specific transaction by its hash | [Transactions](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#transactions) |
-| [`GET /transactions/{hash}/operations`] | [`getTransaction`] | Filter [`getTransaction`] by hash and then parse its XDR for operations | [Operations](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#operations) |
-| [`GET /transactions/{hash}/payments`] | No direct RPC equivalent; use [`getEvents`] or parse [`getTransactions`] | Filter [`getTransaction`] by hash and analyze its events and operation types to identify payments. | [Payments](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#payments) |
-| [`GET /transactions/{hash}/effects`] | No direct RPC equivalent; use [`getEvents`] or parse [`getTransactions`] | Filter [`getTransaction`] by hash and analyze its events and metadata for relevant data. | [Effects](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#effects) |
-| [`GET /operations`] | [`getTransactions`] | Ingest all historical ledgers/transactions and build and build a view of operations for filtering. | [Operations](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#operations) |
-| [`GET /operations/{id}`] | No direct RPC equivalent | Store Horizon's operation ID and map it back to the ledger sequence and transaction index to retrieve the relevant transaction via [`getTransactions`]. | [Operations](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#operations) |
-| [`GET /operations/{id}/effects`] | No direct RPC equivalent | Retrieve the operation by ID (as above) and then parse its associated transaction and events for effects. | [Effects](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#effects) |
-| [`GET /fee_stats`] | [`getFeeStats`] [`simulateTransaction`] | Indexed data not recommended. | [Fee Stats](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#fee-stats) |
-| [`GET /accounts`] | No direct RPC equivalent | Ingest all ledger history via [`getLedgers`] to build and maintain a complete list of accounts. | [Accounts](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#accounts) |
-| [`GET /accounts/{address}`] | [`getLedgerEntries`] | Use [`getLedgerEntries`] for a specific account address. Note: RPC will not provide trustline information associated with the account directly, as Horizon does. You will need to derive this from ledger entries. See [Example: Account Balances](#example-account-balances). | [Accounts](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#accounts) |
-| [`GET /claimable_balances`] | No direct RPC equivalent | Ingest all ledger history via [`getLedgers`] to build and maintain a complete list of claimable balances. | [Claimable Balances](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#claimable-balances) |
-| [`GET /claimable_balances/{id}`] | [`getLedgerEntries`] | Use [`getLedgerEntries`] to retrieve a specific claimable balance by ID. | [Claimable Balances](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#claimable-balances) |
-| [`GET /claimable_balances/{id}/transactions`] | No direct RPC equivalent | Trace transactions that interact with the specific claimable balance ID from their historical ledger data. | [Claimable Balances](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#claimable-balances) |
-| [`GET /claimable_balances/{id}/operations`] | No direct RPC equivalent | trace operations related to the specific claimable balance ID from your historical ledger data. | [Claimable Balances](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#claimable-balances) |
-| [`GET /liquidity_pools`] | No direct RPC equivalent | ingest all ledger history via [`getLedgers`] to build and maintain a complete list of liquidity pools. | [Liquiditity Pools](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#liquidity-pools) |
-| [`GET /liquidity_pools/{id}`] | [`getLedgerEntries`] | Use [`getLedgerEntries`] to retrieve a specific liquidity pool by ID. | [Liquiditity Pools](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#liquidity-pools) |
-| [`GET /liquidity_pools/{id}/transactions`] | No direct RPC equivalent | Trace transactions that interact with the specific liquidity pool ID from their historical ledger data. | [Liquiditity Pools](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#liquidity-pools) |
-| [`GET /liquidity_pools/{id}/operations`] | No direct RPC equivalent | Trace operations related to the specific liquidity pool ID from their historical ledger data. | [Liquiditity Pools](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#liquidity-pools) |
-| [`GET /liquidity_pools/{id}/effects`] | No direct RPC equivalent | Trace effects related to the specific liquidity pool ID from their historical ledger data. | [Liquiditity Pools](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#liquidity-pools) |
-| [`GET /liquidity_pools/{id}/trades`] | No direct RPC equivalent | Infer trades related to the specific liquidity pool ID from historical ledger data (e.g., from [`getEvents`] and [`getTransactions`] metadata). | [Liquiditity Pools](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#liquidity-pools) |
-| [`GET /offers`] | No direct RPC equivalent | Ingest all ledger history via [`getLedgers`] to build and maintain a complete list of offers. | [Offers](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#offers) |
-| [`GET /offers/{id}`] | [`getLedgerEntries`] | Use [`getLedgerEntries`] to retrieve a specific offer by ID. | [Offers](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#offers) |
-| [`GET /offers/{id}/trades`] | No direct RPC equivalent | Infer trades related to the specific offer ID from historical ledger data (e.g., from [`getEvents`] and [`getTransactions`] metadata). | [Offers](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#offers) |
-| [`GET /payments`] | [`getEvents`] [`getTransactions`] ⚠️ | Use [`getEvents`] (CAP-67 asset events) and process [`getTransactions`] metadata for payment-like operations across all history. | [Payments](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#payments) |
-| [`GET /effects`] | [`getEvents`] [`getTransactions`] ⚠️ | Use [`getEvents`] for the effects CAP-67 models, and process [`getTransactions`] metadata to derive the remaining effect types across all history. | [Effects](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#effects) |
-| [`GET /trades`] | [`getEvents`] [`getTransactions`] ⚠️ | Infer trades from [`getEvents`] and [`getTransactions`] metadata across all history, as there is no direct "trade event" in RPC. | [Trades](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#trades) |
-
-:::tip
+| [`GET /transactions`] | [`getTransactions`] | Use [`getTransactions`] to build a historical transaction list | [Transactions](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#transactions) |
+| [`GET /transactions/{hash}`] | [`getTransaction`] | Use getTransaction to retrieve a specific transaction by its hash | [Transactions](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#transactions) |
+| [`GET /transactions/{hash}/operations`] | [`getTransaction`] | Filter [`getTransaction`] by hash and then parse its XDR for operations | [Operations](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#operations) |
+| [`GET /transactions/{hash}/payments`] | No direct RPC equivalent; use [`getEvents`] or parse [`getTransactions`] | Filter [`getTransaction`] by hash and analyze its events and operation types to identify payments. | [Payments](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#payments) |
+| [`GET /transactions/{hash}/effects`] | No direct RPC equivalent; use [`getEvents`] or parse [`getTransactions`] | Filter [`getTransaction`] by hash and analyze its events and metadata for relevant data. | [Effects](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#effects) |
+| [`GET /operations`] | [`getTransactions`] | Ingest all historical ledgers/transactions and build and build a view of operations for filtering. | [Operations](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#operations) |
+| [`GET /operations/{id}`] | No direct RPC equivalent | Store Horizon's operation ID and map it back to the ledger sequence and transaction index to retrieve the relevant transaction via [`getTransactions`]. | [Operations](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#operations) |
+| [`GET /operations/{id}/effects`] | No direct RPC equivalent | Retrieve the operation by ID (as above) and then parse its associated transaction and events for effects. | [Effects](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#effects) |
+| [`GET /fee_stats`] | [`getFeeStats`] [`simulateTransaction`] | Indexed data not recommended. | [Fee Stats](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#fee-stats) |
+| [`GET /accounts`] | No direct RPC equivalent | Ingest all ledger history via [`getLedgers`] to build and maintain a complete list of accounts. | [Accounts](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#accounts) |
+| [`GET /accounts/{address}`] | [`getLedgerEntries`] | Use [`getLedgerEntries`] for a specific account address. Note: RPC will not provide trustline information associated with the account directly, as Horizon does. You will need to derive this from ledger entries. See [Example: Account Balances](#example-account-balances). | [Accounts](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#accounts) |
+| [`GET /claimable_balances`] | No direct RPC equivalent | Ingest all ledger history via [`getLedgers`] to build and maintain a complete list of claimable balances. | [Claimable Balances](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#claimable-balances) |
+| [`GET /claimable_balances/{id}`] | [`getLedgerEntries`] | Use [`getLedgerEntries`] to retrieve a specific claimable balance by ID. | [Claimable Balances](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#claimable-balances) |
+| [`GET /claimable_balances/{id}/transactions`] | No direct RPC equivalent | Trace transactions that interact with the specific claimable balance ID from their historical ledger data. | [Claimable Balances](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#claimable-balances) |
+| [`GET /claimable_balances/{id}/operations`] | No direct RPC equivalent | trace operations related to the specific claimable balance ID from your historical ledger data. | [Claimable Balances](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#claimable-balances) |
+| [`GET /liquidity_pools`] | No direct RPC equivalent | ingest all ledger history via [`getLedgers`] to build and maintain a complete list of liquidity pools. | [Liquiditity Pools](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#liquidity-pools) |
+| [`GET /liquidity_pools/{id}`] | [`getLedgerEntries`] | Use [`getLedgerEntries`] to retrieve a specific liquidity pool by ID. | [Liquiditity Pools](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#liquidity-pools) |
+| [`GET /liquidity_pools/{id}/transactions`] | No direct RPC equivalent | Trace transactions that interact with the specific liquidity pool ID from their historical ledger data. | [Liquiditity Pools](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#liquidity-pools) |
+| [`GET /liquidity_pools/{id}/operations`] | No direct RPC equivalent | Trace operations related to the specific liquidity pool ID from their historical ledger data. | [Liquiditity Pools](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#liquidity-pools) |
+| [`GET /liquidity_pools/{id}/effects`] | No direct RPC equivalent | Trace effects related to the specific liquidity pool ID from their historical ledger data. | [Liquiditity Pools](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#liquidity-pools) |
+| [`GET /liquidity_pools/{id}/trades`] | No direct RPC equivalent | Infer trades related to the specific liquidity pool ID from historical ledger data (e.g., from [`getEvents`] and [`getTransactions`] metadata). | [Liquiditity Pools](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#liquidity-pools) |
+| [`GET /offers`] | No direct RPC equivalent | Ingest all ledger history via [`getLedgers`] to build and maintain a complete list of offers. | [Offers](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#offers) |
+| [`GET /offers/{id}`] | [`getLedgerEntries`] | Use [`getLedgerEntries`] to retrieve a specific offer by ID. | [Offers](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#offers) |
+| [`GET /offers/{id}/trades`] | No direct RPC equivalent | Infer trades related to the specific offer ID from historical ledger data (e.g., from [`getEvents`] and [`getTransactions`] metadata). | [Offers](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#offers) |
+| [`GET /payments`] | [`getEvents`] [`getTransactions`] ⚠️ | Use [`getEvents`] (CAP-67 asset events) and process [`getTransactions`] metadata for payment-like operations across all history. | [Payments](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#payments) |
+| [`GET /effects`] | [`getEvents`] [`getTransactions`] ⚠️ | Use [`getEvents`] for the effects CAP-67 models, and process [`getTransactions`] metadata to derive the remaining effect types across all history. | [Effects](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#effects) |
+| [`GET /trades`] | [`getEvents`] [`getTransactions`] ⚠️ | Infer trades from [`getEvents`] and [`getTransactions`] metadata across all history, as there is no direct "trade event" in RPC. | [Trades](../analytics/hubble/analyst-guide/queries-for-horizon-like-data#trades) |
+
+<Tip>
 
 The [`getTransactions`] method can be used to retrieve events batched by transaction. The events are contained in the meta XDR of the transaction (field `resultMetaXdr`).
 
-:::
-
-:::warning
+</Tip>
+<Warning>
 
 The [`getEvents`] method is not a direct replacement for Horizon's endpoints.
 
 Since [CAP-67] shipped in Protocol 23, the method can return events from classic operations as well as from contracts. Those unified asset events are emitted as `transfer`, `mint`, `burn`, `clawback`, `fee`, and `set_authorized`, so a single stream can cover the movement of assets and changes to trustline authorization.
 
-Classic events are not on by default. They are only present if the Stellar Core instance backing the RPC runs with `EMIT_CLASSIC_EVENTS=true`. If you also need to cover ledgers from Protocol 22 and earlier, that additionally requires `BACKFILL_STELLAR_ASSET_EVENTS=true`. If you run your own RPC, set what your history range needs before relying on this mapping. If you use a provider, confirm with them. See [Events](../../learn/fundamentals/stellar-data-structures/events.mdx) for more detail.
+Classic events are not on by default. They are only present if the Stellar Core instance backing the RPC runs with `EMIT_CLASSIC_EVENTS=true`. If you also need to cover ledgers from Protocol 22 and earlier, that additionally requires `BACKFILL_STELLAR_ASSET_EVENTS=true`. If you run your own RPC, set what your history range needs before relying on this mapping. If you use a provider, confirm with them. See [Events](../../learn/fundamentals/stellar-data-structures/events) for more detail.
 
 That is still narrower than Horizon's effects. Anything CAP-67 does not model, such as signer updates, data entry changes, sequence number bumps, and offer management, has to come from the meta XDR of the transaction. The [`getTransactions`] method returns that meta XDR (field `resultMetaXdr`), which also contains events from contracts.
 
-:::
+</Warning>
 
 ## Response Differences
 
@@ -94,11 +92,11 @@ The [endpoint mapping](#endpoint-mapping) above pairs each Horizon endpoint with
 
 The RPC column describes the decoded ledger entry. A default response holds those fields inside the base64 XDR, so you see them only after you decode it, or after you ask for the JSON view with `xdrFormat`.
 
-### Example: Account Balances
+### Example: Account Balances {#example-account-balances}
 
 Horizon's [`GET /accounts/{address}`] response is an aggregation. It joins the account entry with the account's trustline entries. The [`AccountEntry`] structure holds no trustlines of its own. It holds only a count of the account's sub-entries. So, for balances, one Horizon call becomes a [`getLedgerEntries`] call with an account key plus one trustline key per non-native balance, including liquidity pool shares, and you must already know each asset. The XLM balance is in the account entry itself, so it needs no trustline key. Horizon's `data` map comes from separate data entries, so each account data key you need is one more key in the request. A call takes at most 200 keys, so an account with many trustlines or data entries needs more than one call.
 
-The example below uses a Testnet account. A [Testnet data reset](../../networks/README.mdx#testnet-and-futurenet-data-reset) clears it, so use your own account and asset to follow along. This Horizon request returns both balances at once:
+The example below uses a Testnet account. A [Testnet data reset](/docs/networks#testnet-and-futurenet-data-reset) clears it, so use your own account and asset to follow along. This Horizon request returns both balances at once:
 
 ```bash
 curl "https://horizon-testnet.stellar.org/accounts/GA2242THTLFWPCW2SF3TTLDWJ3C543UUNFTFIMDJUZYXNW2EMEAXZBRH"
@@ -144,7 +142,7 @@ Horizon answers with one resource. The response below is trimmed to the fields t
 }
 ```
 
-The same data over RPC takes two keys. The first key is the account, the second is the USDC trustline. See [Building ledger keys](./rpc/api-reference/methods/getLedgerEntries.mdx#types-of-ledgerkeys) for how to build each one.
+The same data over RPC takes two keys. The first key is the account, the second is the USDC trustline. See [Building ledger keys](/docs/data/apis/rpc/api-reference/methods/getLedgerEntries#types-of-ledgerkeys) for how to build each one.
 
 ```json
 {
@@ -218,15 +216,15 @@ Both responses describe the same account. Read them side by side:
 - The first byte, the master weight, appears in Horizon as the `weight` of the master key in the `signers` array. The raw account entry's `signers` list never includes the master key.
 - Horizon's `flags` booleans expand the entry's `flags` bitmask. The trustline's `flags` value of `1` is `AUTHORIZED_FLAG`, which Horizon reports as `is_authorized`.
 
-:::note
+<Note>
 
 Pass `"xdrFormat": "json"` to read an entry without an SDK, as the responses above do. Do not build an application on that JSON. The [`getLedgerEntries`] specification warns that its shape changes whenever the underlying XDR changes. Decode the default base64 XDR with one of the [SDKs] instead.
 
-:::
+</Note>
 
 ### Amounts Are Raw Integers
 
-Every classic amount on the ledger is a signed 64-bit integer of stroops. Horizon divides it by ten million and returns a string with seven decimal places. RPC returns the stroop count itself. It is a JSON string, not a JSON number, because a 64-bit integer does not fit a JSON number safely. Divide it in your own code, and use a big-number type so you do not lose precision. See [Amount precision](../../learn/fundamentals/stellar-data-structures/assets.mdx#amount-precision).
+Every classic amount on the ledger is a signed 64-bit integer of stroops. Horizon divides it by ten million and returns a string with seven decimal places. RPC returns the stroop count itself. It is a JSON string, not a JSON number, because a 64-bit integer does not fit a JSON number safely. Divide it in your own code, and use a big-number type so you do not lose precision. See [Amount precision](/docs/learn/fundamentals/stellar-data-structures/assets#amount-precision).
 
 ### A Missing Entry Is Not an Error
 
@@ -236,59 +234,59 @@ Match each returned entry back to its own key with the entry's `keyJson` field,
 
 [CAP-67]: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md
 [`AccountEntry`]: https://github.com/stellar/stellar-xdr/blob/v28.0/Stellar-ledger-entries.x#L190
-[Horizon]: ./horizon/README.mdx
-[RPC]: ./rpc/README.mdx
-[Horizon's REST-like API]: ./horizon/api-reference/README.mdx
-[Horizon's Response Format]: ./horizon/api-reference/structure/response-format.mdx
-[RPC JSON-RPC API]: ./rpc/api-reference/README.mdx
-[JSON-RPC]: ./rpc/api-reference/structure/json-rpc.mdx
-[Data]: ../analytics/README.mdx
-[SDKs]: ../../tools/sdks/README.mdx
-[`GET /`]: ./horizon/api-reference/README.mdx
-[`GET /ledgers`]: ./horizon/api-reference/list-all-ledgers.api.mdx
-[`GET /ledgers/{seq}`]: ./horizon/api-reference/retrieve-a-ledger.api.mdx
-[`GET /ledgers/{seq}/transactions`]: ./horizon/api-reference/retrieve-a-ledgers-transactions.api.mdx
-[`GET /ledgers/{seq}/operations`]: ./horizon/api-reference/retrieve-a-ledgers-operations.api.mdx
-[`GET /ledgers/{seq}/payments`]: ./horizon/api-reference/retrieve-a-ledgers-payments.api.mdx
-[`GET /ledgers/{seq}/effects`]: ./horizon/api-reference/retrieve-a-ledgers-effects.api.mdx
-[`POST /transactions`]: ./horizon/api-reference/submit-a-transaction.api.mdx
-[`POST /transactions_async`]: ./horizon/api-reference/submit-async-transaction.api.mdx
-[`GET /transactions`]: ./horizon/api-reference/list-all-transactions.api.mdx
-[`GET /transactions/{hash}`]: ./horizon/api-reference/retrieve-a-transaction.api.mdx
-[`GET /transactions/{hash}/operations`]: ./horizon/api-reference/retrieve-a-transactions-operations.api.mdx
-[`GET /transactions/{hash}/payments`]: ./horizon/api-reference/retrieve-a-transactions-payments.api.mdx
-[`GET /transactions/{hash}/effects`]: ./horizon/api-reference/retrieve-a-transactions-effects.api.mdx
-[`GET /operations`]: ./horizon/api-reference/list-all-operations.api.mdx
-[`GET /operations/{id}`]: ./horizon/api-reference/retrieve-an-operation.api.mdx
-[`GET /operations/{id}/effects`]: ./horizon/api-reference/retrieve-an-operations-effects.api.mdx
-[`GET /fee_stats`]: ./horizon/api-reference/README.mdx
-[`GET /accounts`]: ./horizon/api-reference/list-all-accounts.api.mdx
-[`GET /accounts/{address}`]: ./horizon/api-reference/retrieve-an-account.api.mdx
-[`GET /claimable_balances`]: ./horizon/api-reference/list-all-claimable-balances.api.mdx
-[`GET /claimable_balances/{id}`]: ./horizon/api-reference/retrieve-a-claimable-balance.api.mdx
-[`GET /claimable_balances/{id}/transactions`]: ./horizon/api-reference/cb-retrieve-related-transactions.api.mdx
-[`GET /claimable_balances/{id}/operations`]: ./horizon/api-reference/cb-retrieve-related-operations.api.mdx
-[`GET /liquidity_pools`]: ./horizon/api-reference/list-liquidity-pools.api.mdx
-[`GET /liquidity_pools/{id}`]: ./horizon/api-reference/retrieve-a-liquidity-pool.api.mdx
-[`GET /liquidity_pools/{id}/transactions`]: ./horizon/api-reference/lp-retrieve-related-transactions.api.mdx
-[`GET /liquidity_pools/{id}/operations`]: ./horizon/api-reference/lp-retrieve-related-operations.api.mdx
-[`GET /liquidity_pools/{id}/effects`]: ./horizon/api-reference/retrieve-related-effects.api.mdx
-[`GET /liquidity_pools/{id}/trades`]: ./horizon/api-reference/retrieve-related-trades.api.mdx
-[`GET /offers`]: ./horizon/api-reference/get-all-offers.api.mdx
-[`GET /offers/{id}`]: ./horizon/api-reference/get-offer-by-offer-id.api.mdx
-[`GET /offers/{id}/trades`]: ./horizon/api-reference/get-trades-by-offer-id.api.mdx
-[`GET /payments`]: ./horizon/api-reference/list-all-payments.api.mdx
-[`GET /effects`]: ./horizon/api-reference/list-all-effects.api.mdx
-[`GET /trades`]: ./horizon/api-reference/get-all-trades.api.mdx
-[`getLatestLedger`]: ./rpc/api-reference/methods/getLatestLedger.mdx
-[`getVersionInfo`]: ./rpc/api-reference/methods/getVersionInfo.mdx
-[`getHealth`]: ./rpc/api-reference/methods/getHealth.mdx
-[`getNetwork`]: ./rpc/api-reference/methods/getNetwork.mdx
-[`getLedgers`]: ./rpc/api-reference/methods/getLedgers.mdx
-[`getTransactions`]: ./rpc/api-reference/methods/getTransactions.mdx
-[`getTransaction`]: ./rpc/api-reference/methods/getTransaction.mdx
-[`getEvents`]: ./rpc/api-reference/methods/getEvents.mdx
-[`sendTransaction`]: ./rpc/api-reference/methods/sendTransaction.mdx
-[`getFeeStats`]: ./rpc/api-reference/methods/getFeeStats.mdx
-[`simulateTransaction`]: ./rpc/api-reference/methods/simulateTransaction.mdx
-[`getLedgerEntries`]: ./rpc/api-reference/methods/getLedgerEntries.mdx
+[Horizon]: /docs/data/apis/horizon
+[RPC]: /docs/data/apis/rpc
+[Horizon's REST-like API]: /docs/data/apis/horizon/api-reference
+[Horizon's Response Format]: ./horizon/api-reference/structure/response-format
+[RPC JSON-RPC API]: /docs/data/apis/rpc/api-reference
+[JSON-RPC]: ./rpc/api-reference/structure/json-rpc
+[Data]: /docs/data/analytics
+[SDKs]: /docs/tools/sdks
+[`GET /`]: /docs/data/apis/horizon/api-reference
+[`GET /ledgers`]: /docs/data/apis/horizon/api-reference/list-all-ledgers
+[`GET /ledgers/{seq}`]: /docs/data/apis/horizon/api-reference/retrieve-a-ledger
+[`GET /ledgers/{seq}/transactions`]: /docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions
+[`GET /ledgers/{seq}/operations`]: /docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations
+[`GET /ledgers/{seq}/payments`]: /docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments
+[`GET /ledgers/{seq}/effects`]: /docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects
+[`POST /transactions`]: /docs/data/apis/horizon/api-reference/submit-a-transaction
+[`POST /transactions_async`]: /docs/data/apis/horizon/api-reference/submit-async-transaction
+[`GET /transactions`]: /docs/data/apis/horizon/api-reference/list-all-transactions
+[`GET /transactions/{hash}`]: /docs/data/apis/horizon/api-reference/retrieve-a-transaction
+[`GET /transactions/{hash}/operations`]: /docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations
+[`GET /transactions/{hash}/payments`]: /docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments
+[`GET /transactions/{hash}/effects`]: /docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects
+[`GET /operations`]: /docs/data/apis/horizon/api-reference/list-all-operations
+[`GET /operations/{id}`]: /docs/data/apis/horizon/api-reference/retrieve-an-operation
+[`GET /operations/{id}/effects`]: /docs/data/apis/horizon/api-reference/retrieve-an-operations-effects
+[`GET /fee_stats`]: /docs/data/apis/horizon/api-reference
+[`GET /accounts`]: /docs/data/apis/horizon/api-reference/list-all-accounts
+[`GET /accounts/{address}`]: /docs/data/apis/horizon/api-reference/retrieve-an-account
+[`GET /claimable_balances`]: /docs/data/apis/horizon/api-reference/list-all-claimable-balances
+[`GET /claimable_balances/{id}`]: /docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance
+[`GET /claimable_balances/{id}/transactions`]: /docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions
+[`GET /claimable_balances/{id}/operations`]: /docs/data/apis/horizon/api-reference/cb-retrieve-related-operations
+[`GET /liquidity_pools`]: /docs/data/apis/horizon/api-reference/list-liquidity-pools
+[`GET /liquidity_pools/{id}`]: /docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool
+[`GET /liquidity_pools/{id}/transactions`]: /docs/data/apis/horizon/api-reference/lp-retrieve-related-transactions
+[`GET /liquidity_pools/{id}/operations`]: /docs/data/apis/horizon/api-reference/lp-retrieve-related-operations
+[`GET /liquidity_pools/{id}/effects`]: /docs/data/apis/horizon/api-reference/retrieve-related-effects
+[`GET /liquidity_pools/{id}/trades`]: /docs/data/apis/horizon/api-reference/retrieve-related-trades
+[`GET /offers`]: /docs/data/apis/horizon/api-reference/get-all-offers
+[`GET /offers/{id}`]: /docs/data/apis/horizon/api-reference/get-offer-by-offer-id
+[`GET /offers/{id}/trades`]: /docs/data/apis/horizon/api-reference/get-trades-by-offer-id
+[`GET /payments`]: /docs/data/apis/horizon/api-reference/list-all-payments
+[`GET /effects`]: /docs/data/apis/horizon/api-reference/list-all-effects
+[`GET /trades`]: /docs/data/apis/horizon/api-reference/get-all-trades
+[`getLatestLedger`]: ./rpc/api-reference/methods/getLatestLedger
+[`getVersionInfo`]: ./rpc/api-reference/methods/getVersionInfo
+[`getHealth`]: ./rpc/api-reference/methods/getHealth
+[`getNetwork`]: ./rpc/api-reference/methods/getNetwork
+[`getLedgers`]: ./rpc/api-reference/methods/getLedgers
+[`getTransactions`]: ./rpc/api-reference/methods/getTransactions
+[`getTransaction`]: ./rpc/api-reference/methods/getTransaction
+[`getEvents`]: ./rpc/api-reference/methods/getEvents
+[`sendTransaction`]: ./rpc/api-reference/methods/sendTransaction
+[`getFeeStats`]: ./rpc/api-reference/methods/getFeeStats
+[`simulateTransaction`]: ./rpc/api-reference/methods/simulateTransaction
+[`getLedgerEntries`]: ./rpc/api-reference/methods/getLedgerEntries
diff --git a/docs/data/apis/rpc/README.mdx b/docs/data/apis/rpc/README.mdx
deleted file mode 100644
index 51fd511ab..000000000
--- a/docs/data/apis/rpc/README.mdx
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: "Use the Stellar RPC to Access Blockchain Data, Query Transactions & More"
-sidebar_label: RPC
-description: "Learn how to use RPC methods to view current state, access blockchain data, interact with smart contracts, query transactions, and more on the Stellar network."
-sidebar_position: 5
----
-
-# RPC Introduction
-
-:::info
-
-Stellar-RPC was renamed from Soroban-RPC in Nov 2024. Additional context on this decision can be found on our [developer blog].
-
-:::
-
-Stellar RPC is a lightweight tool that provides real-time access to Stellar network data. Much like RPC nodes in other blockchain ecosystems, it allows developers to query the network efficiently. Whether you’re building a non-custodial wallet, issuing assets, or monitoring network activity, Stellar RPC is designed to provide trusted, stable infrastructure that anyone can run.
-
-For any new builders coming to Stellar, Stellar RPC should be your starting point—it’s built to align with the growing needs of the ecosystem. RPC can be accessed via cURL or one of the [Stellar SDKs](../../../tools/sdks/README.mdx).
-
-## Why Run RPC?
-
-Running RPC within your own infrastructure provides a number of benefits. You can:
-
-- Have full operational control without dependency on any third party provider for network data and transaction submission. The only way to harness the true power of a decentralized blockchain!
-- Avoid the added overhead of directly interacting with [Stellar Core], whose primary focus is performance and therefore provides a very limited API
-- Avoid the added overhead of storing way more data than your application actually needs, as would be the case when running [Horizon]
-
-What Stellar RPC is not:
-
-- An indexer for historical data. RPC retains only a bounded, recent window of history (about 7 days by default).
-- A primary backend service for your application. Use RPC as your gateway to the blockchain, but ingest and index only the data you care about.
-- A drop-in replacement for Horizon. Horizon provides several indexing features not commonly supported by RPC nodes. We believe these business opportunities should be passed back to third party applications (indexers, analytics providers, etc) and away from the SDF.
-
-## In These Docs
-
-- [Admin Guide](./admin-guide/README.mdx): how to set up and operate your own RPC instance.
-- [RPC Methods](./api-reference/methods/README.mdx): descriptions of RPC methods, including their expected inputs and outputs.
-- [Structure](./api-reference/structure/README.mdx): how the RPC API is structured.
-- [Ecosystem Providers](./providers.mdx): third party providers that provide RPC instances as a service.
-
-[quickstart]: https://github.com/stellar/quickstart
-[developer blog]: https://stellar.org/blog/foundation-news/stellar-rpc-has-arrived
-[Stellar Core]: ../../validators
-[Horizon]: ./horizon
diff --git a/docs/data/apis/rpc/admin-guide/README.mdx b/docs/data/apis/rpc/admin-guide/README.mdx
deleted file mode 100644
index 5c5b6de93..000000000
--- a/docs/data/apis/rpc/admin-guide/README.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: Admin Guide
-sidebar_position: 15
-sidebar_key: rpc-admin-guide
----
-
-import DocCardList from "@theme/DocCardList";
-
-All you need to know about setting up, running, and using Stellar RPC.
-
-<DocCardList />
diff --git a/docs/data/apis/rpc/admin-guide/configuring.mdx b/docs/data/apis/rpc/admin-guide/configuring.mdx
index 916249899..8f20a8faa 100644
--- a/docs/data/apis/rpc/admin-guide/configuring.mdx
+++ b/docs/data/apis/rpc/admin-guide/configuring.mdx
@@ -1,6 +1,6 @@
 ---
 title: Configuring
-sidebar_position: 25
+description: "For production, we recommend running Stellar RPC with a TOML configuration file rather than CLI flags. This is similar to creating a configuration file for Stellar-Core as we did previously. For example, using our docker image:"
 ---
 
 For production, we recommend running Stellar RPC with a [TOML](https://toml.io/en) configuration file rather than CLI flags. This is similar to creating a configuration file for Stellar-Core as we did previously. For example, using [our docker image](https://hub.docker.com/r/stellar/stellar-rpc):
@@ -254,11 +254,11 @@ STELLAR_CORE_TIMEOUT = "2s"
 # SERVE_LEDGERS_FROM_DATASTORE = false
 ```
 
-:::info
+<Info>
 
-Example datastore configurations can be found on the [data lake integration page](./data-lake-integration.mdx).
+Example datastore configurations can be found on the [data lake integration page](./data-lake-integration).
 
-:::
+</Info>
 
 Note that the above generated configuration contains the default values and you need to substitute them with proper values to run the image. For instance, when using a container, it is recommended to create a volume for the Captive Core and RPC persistent storage and point `CAPTIVE_CORE_STORAGE_PATH` and `DB_PATH` to it accordingly.
 
@@ -296,8 +296,8 @@ RPC treats this value as a target, not an exact count. Datastore coverage, ledge
 backfill requires serving ledgers from datastore to be enabled. See the `--serve-ledgers-from-datastore` flag
 ```
 
-To set up the datastore, see [Data Lake Integration](./data-lake-integration.mdx). That page also explains which requests the datastore serves directly.
+To set up the datastore, see [Data Lake Integration](./data-lake-integration). That page also explains which requests the datastore serves directly.
 
 ## Next Step
 
-After installation is complete, you are now ready to proceed to [Running RPC](./running.mdx)!
+After installation is complete, you are now ready to proceed to [Running RPC](./running)!
diff --git a/docs/data/apis/rpc/admin-guide/data-lake-integration.mdx b/docs/data/apis/rpc/admin-guide/data-lake-integration.mdx
index 2591dcc2a..9366a428f 100644
--- a/docs/data/apis/rpc/admin-guide/data-lake-integration.mdx
+++ b/docs/data/apis/rpc/admin-guide/data-lake-integration.mdx
@@ -1,6 +1,6 @@
 ---
 title: Data Lake Integration
-sidebar_position: 65
+description: "Expand your RPC node's capabilities by connecting it to a data lake for complete historical ledger access."
 ---
 
 Expand your RPC node's capabilities by connecting it to a data lake for complete historical ledger access.
@@ -11,20 +11,20 @@ RPC version 23.0 introduces data lake integration for the `getLedgers` endpoint,
 
 The process involves setting up a ledger data lake and then configuring your RPC node to use it.
 
-:::info
+<Info>
 
 The metadata of a ledger returned by `getLedgers` may vary depending on its source. When a ledger is retrieved from the RPC's local datastore, its metadata is subject to your RPC configuration. However, ledgers fetched from the data lake are typically stored with all metadata included.
 
-:::
+</Info>
 
 ### 1. Accessing a Data Lake
 
 You have two options for utilizing a data lake:
 
 - **Public Data Lake:** The simplest way is to use a publicly available data lake. For example, Stellar ledger data lake is available through the AWS Open Data program at `s3://aws-public-blockchain/v1.1/stellar/ledgers/pubnet`.
-- **Self-Hosted Data Lake:** This method lets you have more control over data integrity, availability and access, but requires you to create and manage your own data lake. The **Galexie** tool can help you deploy a data lake on either AWS S3 or Google Cloud Storage (GCS). For detailed instructions, refer to the [Galexie Admin Guide](../../../../data/indexers/build-your-own/galexie/README.mdx).
+- **Self-Hosted Data Lake:** This method lets you have more control over data integrity, availability and access, but requires you to create and manage your own data lake. The **Galexie** tool can help you deploy a data lake on either AWS S3 or Google Cloud Storage (GCS). For detailed instructions, refer to the [Galexie Admin Guide](/docs/data/indexers/build-your-own/galexie).
 
-RPC reads the data lake for you. If you also want to read the stored files directly, see [Data Lake Storage Format](../../../../data/indexers/build-your-own/galexie/data-lake-format.mdx).
+RPC reads the data lake for you. If you also want to read the stored files directly, see [Data Lake Storage Format](/docs/data/indexers/build-your-own/galexie/data-lake-format).
 
 ### 2. Configuring RPC for Data Lake Integration
 
@@ -38,7 +38,7 @@ Update your RPC node's configuration file with the following settings:
 
 1.  **Specify Storage Path:** Define the storage backend (`GCS` or `S3`) and provide the full path to the bucket (e.g., `my-bucket/path/to/data`).
 2.  **Enable the Feature Flag:** Set `SERVE_LEDGERS_FROM_DATASTORE` to `true`.
-3.  **Configure Ledger Backend:** Configure how data is read from the datastore through [BufferedStorageBackend](../../../../data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/bufferedstoragebackend.mdx).
+3.  **Configure Ledger Backend:** Configure how data is read from the datastore through [BufferedStorageBackend](../../../../data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/bufferedstoragebackend).
 
 #### Configuration Examples
 
diff --git a/docs/data/apis/rpc/admin-guide/development.mdx b/docs/data/apis/rpc/admin-guide/development.mdx
index 2bb1d7ad5..ddfebb963 100644
--- a/docs/data/apis/rpc/admin-guide/development.mdx
+++ b/docs/data/apis/rpc/admin-guide/development.mdx
@@ -1,15 +1,15 @@
 ---
 title: Development
-sidebar_position: 45
+description: "For local development, we recommend downloading and running a local instance via Docker Quickstart and running a local network or communicating with a live development [Testnet]."
 ---
 
 For local development, we recommend [downloading](https://hub.docker.com/r/stellar/quickstart) and running a local instance via [Docker Quickstart](https://github.com/stellar/quickstart) and running a local network or communicating with a live development [Testnet].
 
-:::caution
+<Warning>
 
-We don't recommend running the Quickstart image in production. See the [deploy your own RPC instance](./installing.mdx) section.
+We don't recommend running the Quickstart image in production. See the [deploy your own RPC instance](./installing) section.
 
-:::
+</Warning>
 
 ### Standalone
 
@@ -50,11 +50,13 @@ Then generate a unique identity (public/private keypair) and to fund it using:
 stellar keys generate alice
 ```
 
-:::tip[Test-only Identities]
+<Tip>
+
+**Test-only Identities**
 
 It's a good practice to never use the same keys for testing and development that you use for the public Stellar network. Generate new keys for testing and development and avoid using them for other purposes.
 
-:::
+</Tip>
 
 Now that you have a configured network and a funded identity, you can use these within other Stellar CLI commands. For example, deploying a contract:
 
@@ -79,4 +81,4 @@ stellar contract invoke \
 
 When you're done with your local node, you can close it with <kbd>ctrl</kbd><kbd>c</kbd> (not <kbd>cmd</kbd>). This will fully remove the container (that's what the `--rm` option to the `docker` command does), which means you will need to re-deploy your contract and re-fund your identity the next time you start it. If you work with local nodes often, you may want to create scripts to make these initialization steps easier. For example, see the [example dapp's `initialize.sh`](https://github.com/stellar/soroban-example-dapp/blob/abdac3afdb6c410cc426831ece93371c1a27347d/initialize.sh).
 
-[Testnet]: ../../../../networks/README.mdx
+[Testnet]: /docs/networks
diff --git a/docs/data/apis/rpc/admin-guide/index.mdx b/docs/data/apis/rpc/admin-guide/index.mdx
new file mode 100644
index 000000000..3126cdcfe
--- /dev/null
+++ b/docs/data/apis/rpc/admin-guide/index.mdx
@@ -0,0 +1,43 @@
+---
+title: Admin Guide
+description: "All you need to know about setting up, running, and using Stellar RPC."
+sidebar_key: rpc-admin-guide
+---
+
+<CardGroup cols={2}>
+  <Card title="Prerequisites" icon="file-lines" href="/docs/data/apis/rpc/admin-guide/prerequisites">
+
+    The RPC service can be installed on bare metal or a virtual machine.
+
+  </Card>
+  <Card title="Installing" icon="file-lines" href="/docs/data/apis/rpc/admin-guide/installing">
+
+    We offer three alternatives to deploy your own RPC instance.
+
+  </Card>
+  <Card title="Configuring" icon="file-lines" href="/docs/data/apis/rpc/admin-guide/configuring">
+
+    For production, we recommend running Stellar RPC with a TOML configuration file rather than CLI flags.
+
+  </Card>
+  <Card title="Running" icon="file-lines" href="/docs/data/apis/rpc/admin-guide/running">
+
+    You can run the stellar/stellar-rpc container with the following command.
+
+  </Card>
+  <Card title="Development" icon="file-lines" href="/docs/data/apis/rpc/admin-guide/development">
+
+    For local development, we recommend downloading and running a local instance via Docker Quickstart and running a local network or communicating with a live...
+
+  </Card>
+  <Card title="Monitoring" icon="file-lines" href="/docs/data/apis/rpc/admin-guide/monitoring">
+
+    If you run Stellar RPC with the --admin-endpoint configured and expose the port, you'll have access to the Prometheus metrics via the /metrics endpoint.
+
+  </Card>
+  <Card title="Data Lake Integration" icon="file-lines" href="/docs/data/apis/rpc/admin-guide/data-lake-integration">
+
+    Expand your RPC node's capabilities by connecting it to a data lake for complete historical ledger access.
+
+  </Card>
+</CardGroup>
diff --git a/docs/data/apis/rpc/admin-guide/installing.mdx b/docs/data/apis/rpc/admin-guide/installing.mdx
index 26f943ad4..18ca1d46a 100644
--- a/docs/data/apis/rpc/admin-guide/installing.mdx
+++ b/docs/data/apis/rpc/admin-guide/installing.mdx
@@ -1,6 +1,6 @@
 ---
 title: Installing
-sidebar_position: 20
+description: "We offer three alternatives to deploy your own RPC instance."
 ---
 
 We offer three alternatives to deploy your own RPC instance:
@@ -13,11 +13,11 @@ We offer three alternatives to deploy your own RPC instance:
 
 This is the preferred way to deploy your own RPC instance.
 
-:::caution
+<Warning>
 
 Although we have a [Quickstart Image](https://github.com/stellar/quickstart), it's for local development and testing only. It is not suitable for production-grade deployments.
 
-:::
+</Warning>
 
 Pull the image at the version you'd like to run from [the tags](https://hub.docker.com/r/stellar/stellar-rpc/tags):
 
@@ -44,4 +44,4 @@ Instructions for building Stellar RPC from source can be found [here](https://gi
 
 ## Next Step
 
-After installation is complete, you are now ready to proceed to [Configuring RPC](./configuring.mdx)!
+After installation is complete, you are now ready to proceed to [Configuring RPC](./configuring)!
diff --git a/docs/data/apis/rpc/admin-guide/monitoring.mdx b/docs/data/apis/rpc/admin-guide/monitoring.mdx
index 991276bbf..b1e5c1474 100644
--- a/docs/data/apis/rpc/admin-guide/monitoring.mdx
+++ b/docs/data/apis/rpc/admin-guide/monitoring.mdx
@@ -1,6 +1,6 @@
 ---
 title: Monitoring
-sidebar_position: 60
+description: "If you run Stellar RPC with the --admin-endpoint configured and expose the port, you'll have access to the Prometheus metrics via the /metrics endpoint. For example, if the admin endpoint is 0.0.0.0"
 ---
 
 If you run Stellar RPC with the `--admin-endpoint` configured and [expose the port](https://docs.docker.com/engine/reference/commandline/run/#publish), you'll have access to the [Prometheus](https://prometheus.io) metrics via the `/metrics` endpoint. For example, if the admin endpoint is `0.0.0.0:8001` and you're running the Stellar RPC Docker image:
diff --git a/docs/data/apis/rpc/admin-guide/prerequisites.mdx b/docs/data/apis/rpc/admin-guide/prerequisites.mdx
index ecb32a93f..aed4ef30c 100644
--- a/docs/data/apis/rpc/admin-guide/prerequisites.mdx
+++ b/docs/data/apis/rpc/admin-guide/prerequisites.mdx
@@ -1,6 +1,6 @@
 ---
 title: Prerequisites
-sidebar_position: 10
+description: "The RPC service can be installed on bare metal or a virtual machine."
 ---
 
 The RPC service can be installed on bare metal or a virtual machine. It is natively supported on both Linux and Windows operating systems.
diff --git a/docs/data/apis/rpc/admin-guide/running.mdx b/docs/data/apis/rpc/admin-guide/running.mdx
index d765e6fc6..cabbb1fb6 100644
--- a/docs/data/apis/rpc/admin-guide/running.mdx
+++ b/docs/data/apis/rpc/admin-guide/running.mdx
@@ -1,6 +1,6 @@
 ---
 title: Running
-sidebar_position: 40
+description: "You can run the stellar/stellar-rpc container with the following command."
 ---
 
 You can run the `stellar/stellar-rpc` container with the following command:
@@ -14,4 +14,4 @@ docker run -p 8001:8001 -p 8000:8000 \
 
 ## Next Step
 
-Refer to [Monitoring](./monitoring.mdx) for more details on RPC runtime logging and metrics available.
+Refer to [Monitoring](./monitoring) for more details on RPC runtime logging and metrics available.
diff --git a/docs/data/apis/rpc/api-reference/README.mdx b/docs/data/apis/rpc/api-reference/README.mdx
deleted file mode 100644
index de33850e6..000000000
--- a/docs/data/apis/rpc/api-reference/README.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: API Reference
-sidebar_position: 20
-sidebar_key: rpc-api-reference
----
-
-import DocCardList from "@theme/DocCardList";
-
-View all RPC API information.
-
-<DocCardList />
diff --git a/docs/data/apis/rpc/api-reference/_category_.json b/docs/data/apis/rpc/api-reference/_category_.json
deleted file mode 100644
index 9e3a55f45..000000000
--- a/docs/data/apis/rpc/api-reference/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": true
-}
diff --git a/docs/data/apis/rpc/api-reference/index.mdx b/docs/data/apis/rpc/api-reference/index.mdx
new file mode 100644
index 000000000..922163666
--- /dev/null
+++ b/docs/data/apis/rpc/api-reference/index.mdx
@@ -0,0 +1,18 @@
+---
+title: API Reference
+description: "View all RPC API information."
+sidebar_key: rpc-api-reference
+---
+
+<CardGroup cols={2}>
+  <Card title="Methods" icon="box-archive" href="/docs/data/apis/rpc/api-reference/methods">
+
+    12 items
+
+  </Card>
+  <Card title="Structure" icon="box-archive" href="/docs/data/apis/rpc/api-reference/structure">
+
+    3 items
+
+  </Card>
+</CardGroup>
diff --git a/docs/data/apis/rpc/api-reference/methods/README.mdx b/docs/data/apis/rpc/api-reference/methods/README.mdx
deleted file mode 100644
index 67057737a..000000000
--- a/docs/data/apis/rpc/api-reference/methods/README.mdx
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: Methods
-sidebar_position: 30
----
-
-import DocCardList from "@theme/DocCardList";
-
-All you need to know about available RPC methods, parameters and responses, and making RPC requests.
-
-<DocCardList />
-
-Don't know which endpoint you need to get what you want? A lot of the returned fields are deeply-nested [XDR structures](../../../../../learn/fundamentals/data-format/xdr.mdx#more-about-xdr), so it can be hard to figure out what kind of information is available in each of these. Here's a bit of a dive into what the "workhorse" endpoints provide, in decreasing order of granularity:
-
-- [`getLedgers`](./getLedgers.mdx) operates at the block level, providing you with the full, complete details of what occurred during application of that ledger (known as "ledger metadata", defined in the protocol by the [`LedgerCloseMeta`](https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-ledger.x#L539) union, specifically the `V1` iteration). Each of the subsequent endpoints is just a microscope into a subset of the data available provided by this endpoint. Metadata includes things like:
-  - Details for recreating the blockchain's state (see [Ledger Headers](../../../../../learn/fundamentals/stellar-data-structures/ledgers.mdx#ledger-headers) for more).
-  - The consensus information that led to the block closing (see [Stellar Consensus Protocol](../../../../../learn/fundamentals/stellar-consensus-protocol.mdx)).
-  - The set of transactions, their respective operations, and the results of applying those transactions in this block (see [Transactions](../../../../../learn/fundamentals/transactions/operations-and-transactions.mdx)).
-- [`getTransaction(s)`](./getTransactions.mdx) operates across a span of ledgers or on a single transaction hash depending on the variant. The structured data here includes details such as:
-  - The exact transaction structure ("envelope") that was submitted.
-  - Results for each of the operations within the transaction.
-  - All side-effects to ledger state that occurred as a result of this transaction.
-- [`getEvents`](./getEvents.mdx) lets you search for events that occurred over a ledger range. Events are emitted by the system and by smart contracts to communicate meaningful state changes to off chain indexers (see [Events](../../../../../learn/fundamentals/stellar-data-structures/events.mdx) for more). Each event is made up of topics (which you can filter on) and data which are `ScVal`s, Stellar's generic "value" type (see [Contract Development](../../../../../learn/fundamentals/contract-development/types/built-in-types.mdx) for more).
-- [`queryEvents`](./queryEvents.mdx) is the successor to `getEvents`. It adds descending order and stateless cursors. It is in beta and only runs on RPC nodes that enable it's new storage engine, so it lives in a separate beta spec and not in the main OpenRPC spec.
-- [`getLedgerEntries`](./getLedgerEntries.mdx), in contrast to the above endpoints, provides information about **live** on-chain state rather than historical actions. The [getLedgerEntries](./getLedgerEntries.mdx) page itself goes into detail on the different kinds of state stored on chain and how to fetch them.
-
-If you still aren't sure what you're looking for, remember that you can pass `xdrFormat: "json"` as a parameter to each of these endpoints to get a fully unpacked, human-readable JSON version of the XDR structures returned. You can look through these until you find what you need and go back to the Base64+unpack variation in your app. Equipped with an understanding of how to traverse XDR, the structure of the protocol, and your [favorite SDK](../../../../../tools/sdks/README.mdx), you should be able to find anything you want about the Stellar network with these endpoints.
diff --git a/docs/data/apis/rpc/api-reference/methods/_category_.json b/docs/data/apis/rpc/api-reference/methods/_category_.json
deleted file mode 100644
index 9e3a55f45..000000000
--- a/docs/data/apis/rpc/api-reference/methods/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": true
-}
diff --git a/docs/data/apis/rpc/api-reference/methods/getEvents.mdx b/docs/data/apis/rpc/api-reference/methods/getEvents.mdx
index ef55c92d7..39473e52f 100644
--- a/docs/data/apis/rpc/api-reference/methods/getEvents.mdx
+++ b/docs/data/apis/rpc/api-reference/methods/getEvents.mdx
@@ -1,14 +1,507 @@
 ---
-hide_title: true
+title: getEvents
 description: Returns contract events
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "getEvents")[0]}
-/>
+Clients can request a filtered list of events emitted by a given ledger range.
+
+Stellar-RPC retains a bounded, ledger-denominated history of recent transactions and events, configured by a single history-retention-window setting with a stock default of 120960 ledgers (about 7 days, depending on ledger cadence); requests are served from within that retained range. The effective window and the ledgers currently available can be inspected via the getHealth method (ledgerRetentionWindow, oldestLedger, latestLedger).
+
+Note, this could be used by the client to only prompt a refresh when there is a new ledger with relevant events. It should also be used by backend Dapp components to "ingest" events into their own database for querying and serving.
+
+If making multiple requests, clients should deduplicate any events received, based on the event's unique id field. This prevents double-processing in the case of duplicate events being received.
+
+## Params (5)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="startLedger" type="number">
+
+Ledger sequence number to start fetching responses from (inclusive). This method will return an error if `startLedger` is less than the oldest ledger stored in this node, or greater than the latest ledger seen by this node. If a cursor is included in the request, `startLedger` must be omitted.
+
+Sequence number of the ledger.
+
+</ParamField>
+
+<ParamField body="endLedger" type="number">
+
+Ledger sequence number represents the end of search window (exclusive). If a cursor is included in the request, `endLedger` must be omitted.
+
+Sequence number of the ledger.
+
+</ParamField>
+
+<ParamField body="filters" type="object[]">
+
+List of filters for the returned events. Events matching any of the filters are included. To match a filter, an event must match both a contractId and a topic. Maximum 5 filters are allowed per request.
+
+  <Expandable title="items">
+    <ParamField body="type" type="string">
+
+      Filter events by type. If omitted, all event types are included.
+
+      Available options: `system`, `contract`
+
+    </ParamField>
+    <ParamField body="contractIds" type="string[]">
+
+      List of contract IDs to query for events. If omitted, return events for all contracts. Maximum 5 contract IDs are allowed per request.
+
+    </ParamField>
+    <ParamField body="topics" type="string[][]">
+
+      A list of topic filters. Each filter is itself an array of one to four `SegmentMatcher` elements (see below). If omitted, query for all events. If multiple filters are specified, events will be included if they match any of the filters.
+
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+<ParamField body="pagination" type="object">
+
+Pagination in stellar-rpc is similar to pagination in Horizon. See [Pagination](https://developers.stellar.org/docs/data/rpc/api-reference/structure/pagination).
+
+  <Expandable title="properties">
+    <ParamField body="cursor" type="string">
+
+      An opaque string which acts as a paging token. To obtain the next page of results occurring after a given response set this value to the `cursor` field of the response.
+
+    </ParamField>
+    <ParamField body="limit" type="number">
+
+      The maximum number of records returned. The limit for getEvents can range from 1 to 10000 - an upper limit that is hardcoded in Stellar-RPC for performance reasons. If this argument isn't designated, it defaults to 100.
+
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+<ParamField body="xdrFormat" type="string">
+
+Lets the user choose the format in which the response should be returned - either as unpacked JSON or as base64-encoded XDR strings. Note that you should not rely on any schema for the JSON, as it will change when the underlying XDR changes.
+
+Specifies whether XDR should be encoded as Base64 (default or 'base64') or JSON ('json').
+
+</ParamField>
+
+## Result
+
+_(getEventsResult)_
+
+<ResponseField name="latestLedger" type="number">
+
+The sequence number of the latest ledger known to Stellar RPC at the time it handled the request.
+
+</ResponseField>
+
+<ResponseField name="oldestLedger" type="number">
+
+The sequence number of the oldest ledger ingested by Stellar RPC at the time it handled the request.
+
+</ResponseField>
+
+<ResponseField name="latestLedgerCloseTime" type="string">
+
+The unix timestamp (as a string) of the close time of the latest ledger known to Stellar RPC when it handled the request.
+
+</ResponseField>
+
+<ResponseField name="oldestLedgerCloseTime" type="string">
+
+The unix timestamp (as a string) of the close time of the oldest ledger kept in history by Stellar RPC when it handled the request.
+
+</ResponseField>
+
+<ResponseField name="events" type="object[]">
+  <Expandable title="items">
+    <ResponseField name="type" type="string">
+
+      The type of event emission.
+
+      Available options: `contract`, `system`
+
+    </ResponseField>
+    <ResponseField name="ledger" type="number">
+
+      Sequence number of the ledger in which this event was emitted.
+
+    </ResponseField>
+    <ResponseField name="ledgerClosedAt" type="string">
+
+      [ISO-8601](https://www.iso.org/iso-8601-date-and-time-format.html) timestamp of the ledger closing time
+
+    </ResponseField>
+    <ResponseField name="contractId" type="string">
+
+      StrKey representation of the contract address that emitted this event.
+
+    </ResponseField>
+    <ResponseField name="id" type="string">
+
+      Unique identifier for this event, based on the [TOID](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0035.md#specification) format. It combines a 19-character TOID and a 10-character, zero-padded event index, separated by a hyphen.
+
+      - For example: `0000000000000123456-0000000001`
+
+    </ResponseField>
+    <ResponseField name="transactionIndex" type="number">
+
+      The index of the transaction within the ledger this event occurred in.
+
+    </ResponseField>
+    <ResponseField name="operationIndex" type="number">
+
+      The index of the operation within the transaction this event occurred in.
+
+    </ResponseField>
+    <ResponseField name="topic" type="string[]">
+
+      The [ScVal](https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-contract.x#L214)s containing the topics this event was emitted with (as a base64 string).
+
+    </ResponseField>
+    <ResponseField name="value" type="string">
+
+      The data emitted by the event (an [ScVal](https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-contract.x#L214), serialized as a base64 string).
+
+    </ResponseField>
+    <ResponseField name="txHash" type="string">
+
+      The transaction which triggered this event.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="cursor" type="string">
+
+A token which can be included in a subsequent request to obtain the next page of results.
+
+</ResponseField>
+
+## Examples
+
+<Tabs>
+<Tab title="Native XLM Transfer Events">
+
+Example request to the `getEvents` method, filtering for `transfer` events for native Lumens and limiting the number of returned events to 2.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getEvents",
+  "params": {
+    "startLedger": 199616,
+    "filters": [
+      {
+        "type": "contract",
+        "contractIds": [
+          "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC"
+        ],
+        "topics": [
+          [
+            "AAAADwAAAAh0cmFuc2Zlcg==",
+            "*",
+            "*",
+            "**"
+          ]
+        ]
+      }
+    ],
+    "pagination": {
+      "limit": 2
+    }
+  }
+}' \
+https://soroban-testnet.stellar.org | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "getEvents",
+  params: {
+    startLedger: 199616,
+    filters: [
+      {
+        type: "contract",
+        contractIds: [
+          "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC",
+        ],
+        topics: [["AAAADwAAAAh0cmFuc2Zlcg==", "*", "*", "**"]],
+      },
+    ],
+    pagination: {
+      limit: 2,
+    },
+  },
+};
+let res = await fetch("https://soroban-testnet.stellar.org", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://soroban-testnet.stellar.org", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "getEvents",
+    "params": {
+        "startLedger": 199616,
+        "filters": [
+            {
+                "type": "contract",
+                "contractIds": [
+                    "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC"
+                ],
+                "topics": [
+                    [
+                        "AAAADwAAAAh0cmFuc2Zlcg==",
+                        "*",
+                        "*",
+                        "**"
+                    ]
+                ]
+            }
+        ],
+        "pagination": {
+            "limit": 2
+        }
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getEvents",
+  "params": {
+    "startLedger": 199616,
+    "filters": [
+      {
+        "type": "contract",
+        "contractIds": [
+          "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC"
+        ],
+        "topics": [["AAAADwAAAAh0cmFuc2Zlcg==", "*", "*", "**"]]
+      }
+    ],
+    "pagination": {
+      "limit": 2
+    }
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "events": [
+      {
+        "type": "contract",
+        "ledger": 3727845,
+        "ledgerClosedAt": "2026-07-21T18:01:10Z",
+        "contractId": "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC",
+        "id": "0016010972359577600-0000000001",
+        "transactionIndex": 5,
+        "operationIndex": 0,
+        "topic": [
+          "AAAADwAAAAh0cmFuc2Zlcg==",
+          "AAAAEgAAAAAAAAAAjnWZyariB+Ah9OPGy5WJe1t2Ks3gKsKGYsy7vmpJRIY=",
+          "AAAAEgAAAAGu/2GlTlA4D83fxvERV0mWvvsyBPo+xfk3Guav6IgNZQ==",
+          "AAAADgAAAAZuYXRpdmUAAA=="
+        ],
+        "value": "AAAACgAAAAAAAAAAAAAAALLQXgA=",
+        "txHash": "a5c9247b77eb04c0d857934a2e988c408167976c8acbdf3d8acf64c44deb3beb"
+      },
+      {
+        "type": "contract",
+        "ledger": 3727845,
+        "ledgerClosedAt": "2026-07-21T18:01:10Z",
+        "contractId": "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC",
+        "id": "0016010972359577600-0000000008",
+        "transactionIndex": 5,
+        "operationIndex": 0,
+        "topic": [
+          "AAAADwAAAAh0cmFuc2Zlcg==",
+          "AAAAEgAAAAFvWqehdOlYvvTHeLuVC7C5mabRfoyKnCxxAOeeSzHCbQ==",
+          "AAAAEgAAAAEX55xp/WiwvNIMhmNvj+HN+OoYTpPk1xsJ+iKUVLmQLg==",
+          "AAAADgAAAAZuYXRpdmUAAA=="
+        ],
+        "value": "AAAACgAAAAAAAAAAAAAAAAKJZY8=",
+        "txHash": "a5c9247b77eb04c0d857934a2e988c408167976c8acbdf3d8acf64c44deb3beb"
+      }
+    ],
+    "latestLedger": 3730843,
+    "oldestLedger": 3609884,
+    "latestLedgerCloseTime": "1784671886",
+    "oldestLedgerCloseTime": "1784066056",
+    "cursor": "0016010972359577600-0000000008"
+  }
+}
+```
+
+</Tab>
+<Tab title="All Events">
+
+Example request to the `getEvents` method, filtering for all events of all types for any and all contracts.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getEvents",
+  "params": {
+    "startLedger": 199616,
+    "pagination": {
+      "limit": 2
+    }
+  }
+}' \
+https://soroban-testnet.stellar.org | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "getEvents",
+  params: {
+    startLedger: 199616,
+    pagination: {
+      limit: 2,
+    },
+  },
+};
+let res = await fetch("https://soroban-testnet.stellar.org", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://soroban-testnet.stellar.org", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "getEvents",
+    "params": {
+        "startLedger": 199616,
+        "pagination": {
+            "limit": 2
+        }
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getEvents",
+  "params": {
+    "startLedger": 199616,
+    "pagination": {
+      "limit": 2
+    }
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "events": [
+      {
+        "type": "contract",
+        "ledger": 3729796,
+        "ledgerClosedAt": "2026-07-21T20:44:01Z",
+        "contractId": "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC",
+        "id": "0016019351840751616-0000000000",
+        "transactionIndex": 0,
+        "operationIndex": 0,
+        "topic": [
+          "AAAADwAAAANmZWUA",
+          "AAAAEgAAAAAAAAAAA+0oimKONzC713z+Cl8orRHR8/s0JY+JMothA0fY7bY="
+        ],
+        "value": "AAAACgAAAAAAAAAAAAAAAAAAAGQ=",
+        "txHash": "dd2f693c5d874ed09f2de0a4edbc453a0a74fe3e44a40e8a4017bd47a1708ffd"
+      },
+      {
+        "type": "contract",
+        "ledger": 3729796,
+        "ledgerClosedAt": "2026-07-21T20:44:01Z",
+        "contractId": "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC",
+        "id": "0016019351840751616-0000000001",
+        "transactionIndex": 0,
+        "operationIndex": 0,
+        "topic": [
+          "AAAADwAAAANmZWUA",
+          "AAAAEgAAAAAAAAAAHvWJXEUjo0G/RW4K3B2oCbR8OHbnLlCyfD3iKAnjKPY="
+        ],
+        "value": "AAAACgAAAAAAAAAAAAAAAAAAASw=",
+        "txHash": "3fcd635d285c5b3a4d9b65a10f6c70c11132d8fafd32e82fea79103eb1a05924"
+      }
+    ],
+    "latestLedger": 3730797,
+    "oldestLedger": 3609838,
+    "latestLedgerCloseTime": "1784671655",
+    "oldestLedgerCloseTime": "1784065826",
+    "cursor": "0016019351840751616-0000000001"
+  }
+}
+```
+
+</Tab>
+</Tabs>
+
+{/* /rpc-method */}
 
 ### Event ordering
 
@@ -33,13 +526,13 @@ Events in one ledger come back in this order:
 2. For each transaction, in transaction order: its operation events, then its post-transaction events.
 3. Every fee refund event.
 
-To reproduce this order from meta XDR, sort your own events by the same four values. The [`getTransaction`](./getTransaction.mdx) and [`getTransactions`](./getTransactions.mdx) methods return the two XDR fields separately, in their `events` object, as `events.transactionEventsXdr` and `events.contractEventsXdr`.
+To reproduce this order from meta XDR, sort your own events by the same four values. The [`getTransaction`](./getTransaction) and [`getTransactions`](./getTransactions) methods return the two XDR fields separately, in their `events` object, as `events.transactionEventsXdr` and `events.contractEventsXdr`.
 
-:::note
+<Note>
 
 `transactionIndex` and `operationIndex` come from the cursor. On a transaction-level event they hold the sort values in the table above, not a real position in the ledger. Read `txHash` to find the transaction that a fee event belongs to.
 
-:::
+</Note>
 
 Fee events are the only transaction-level events today. Stellar Core emits the fee charge at the `BEFORE_ALL_TXS` stage. It emits a Soroban fee refund at the `AFTER_ALL_TXS` stage. Both are `contract` events from the native asset contract, and their topics are the symbol `fee` and the fee source address. A refund carries a negative amount. Stellar Core emits no event when the amount is zero.
 
diff --git a/docs/data/apis/rpc/api-reference/methods/getFeeStats.mdx b/docs/data/apis/rpc/api-reference/methods/getFeeStats.mdx
index 26b6dcf1d..4a41d2255 100644
--- a/docs/data/apis/rpc/api-reference/methods/getFeeStats.mdx
+++ b/docs/data/apis/rpc/api-reference/methods/getFeeStats.mdx
@@ -1,14 +1,307 @@
 ---
-hide_title: true
+title: getFeeStats
 description: Returns statistics about charged inclusion fees for Soroban transactions and Stellar transactions
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "getFeeStats")[0]}
-/>
+Statistics for charged inclusion fees. The inclusion fee statistics are calculated from the inclusion fees that were paid for the transactions to be included onto the ledger. For Soroban transactions and Stellar transactions, they each have their own inclusion fees and own surge pricing. Inclusion fees are used to prevent spam and prioritize transactions during network traffic surge.
+
+## Params (0)
+
+## Result
+
+_(getFeeStatsResult)_
+
+<ResponseField name="sorobanInclusionFee" type="object">
+
+Inclusion fee distribution statistics for Soroban transactions
+
+  <Expandable title="properties">
+    <ResponseField name="max" type="string">
+
+      Maximum fee
+
+    </ResponseField>
+    <ResponseField name="min" type="string">
+
+      Minimum fee
+
+    </ResponseField>
+    <ResponseField name="mode" type="string">
+
+      Fee value which occurs the most often
+
+    </ResponseField>
+    <ResponseField name="p10" type="string">
+
+      10th nearest-rank fee percentile
+
+    </ResponseField>
+    <ResponseField name="p20" type="string">
+
+      20th nearest-rank fee percentile
+
+    </ResponseField>
+    <ResponseField name="p30" type="string">
+
+      30th nearest-rank fee percentile
+
+    </ResponseField>
+    <ResponseField name="p40" type="string">
+
+      40th nearest-rank fee percentile
+
+    </ResponseField>
+    <ResponseField name="p50" type="string">
+
+      50th nearest-rank fee percentile
+
+    </ResponseField>
+    <ResponseField name="p60" type="string">
+
+      60th nearest-rank fee percentile
+
+    </ResponseField>
+    <ResponseField name="p70" type="string">
+
+      70th nearest-rank fee percentile
+
+    </ResponseField>
+    <ResponseField name="p80" type="string">
+
+      80th nearest-rank fee percentile
+
+    </ResponseField>
+    <ResponseField name="p90" type="string">
+
+      90th nearest-rank fee percentile.
+
+    </ResponseField>
+    <ResponseField name="p95" type="string">
+
+      95th nearest-rank fee percentile.
+
+    </ResponseField>
+    <ResponseField name="p99" type="string">
+
+      99th nearest-rank fee percentile
+
+    </ResponseField>
+    <ResponseField name="transactionCount" type="string">
+
+      How many transactions are part of the distribution
+
+    </ResponseField>
+    <ResponseField name="ledgerCount" type="number">
+
+      How many consecutive ledgers form the distribution
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="inclusionFee" type="object">
+
+Fee distribution statistics for Stellar (i.e. non-Soroban) transactions. Statistics are normalized per operation.
+
+  <Expandable title="properties">
+    <ResponseField name="max" type="string">
+
+      Maximum fee
+
+    </ResponseField>
+    <ResponseField name="min" type="string">
+
+      Minimum fee
+
+    </ResponseField>
+    <ResponseField name="mode" type="string">
+
+      Fee value which occurs the most often
+
+    </ResponseField>
+    <ResponseField name="p10" type="string">
+
+      10th nearest-rank fee percentile
+
+    </ResponseField>
+    <ResponseField name="p20" type="string">
+
+      20th nearest-rank fee percentile
+
+    </ResponseField>
+    <ResponseField name="p30" type="string">
+
+      30th nearest-rank fee percentile
+
+    </ResponseField>
+    <ResponseField name="p40" type="string">
+
+      40th nearest-rank fee percentile
+
+    </ResponseField>
+    <ResponseField name="p50" type="string">
+
+      50th nearest-rank fee percentile
+
+    </ResponseField>
+    <ResponseField name="p60" type="string">
+
+      60th nearest-rank fee percentile
+
+    </ResponseField>
+    <ResponseField name="p70" type="string">
+
+      70th nearest-rank fee percentile
+
+    </ResponseField>
+    <ResponseField name="p80" type="string">
+
+      80th nearest-rank fee percentile
+
+    </ResponseField>
+    <ResponseField name="p90" type="string">
+
+      90th nearest-rank fee percentile.
+
+    </ResponseField>
+    <ResponseField name="p95" type="string">
+
+      95th nearest-rank fee percentile.
+
+    </ResponseField>
+    <ResponseField name="p99" type="string">
+
+      99th nearest-rank fee percentile
+
+    </ResponseField>
+    <ResponseField name="transactionCount" type="string">
+
+      How many transactions are part of the distribution
+
+    </ResponseField>
+    <ResponseField name="ledgerCount" type="number">
+
+      How many consecutive ledgers form the distribution
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="latestLedger" type="number">
+
+The sequence number of the latest ledger known to Stellar RPC at the time it handled the request.
+
+</ResponseField>
+
+## Example
+
+Example request to the `getFeeStats` method
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getFeeStats"
+}' \
+https://soroban-testnet.stellar.org | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "getFeeStats",
+};
+let res = await fetch("https://soroban-testnet.stellar.org", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://soroban-testnet.stellar.org", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "getFeeStats"
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getFeeStats"
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "sorobanInclusionFee": {
+      "max": "200",
+      "min": "100",
+      "mode": "100",
+      "p10": "100",
+      "p20": "100",
+      "p30": "100",
+      "p40": "100",
+      "p50": "100",
+      "p60": "100",
+      "p70": "100",
+      "p80": "100",
+      "p90": "200",
+      "p95": "200",
+      "p99": "200",
+      "transactionCount": "371",
+      "ledgerCount": 50
+    },
+    "inclusionFee": {
+      "max": "133",
+      "min": "100",
+      "mode": "100",
+      "p10": "100",
+      "p20": "100",
+      "p30": "100",
+      "p40": "100",
+      "p50": "100",
+      "p60": "100",
+      "p70": "100",
+      "p80": "100",
+      "p90": "100",
+      "p95": "100",
+      "p99": "133",
+      "transactionCount": "28",
+      "ledgerCount": 10
+    },
+    "latestLedger": 3730870
+  }
+}
+```
+
+{/* /rpc-method */}
 
 ### Using the Lab
 
diff --git a/docs/data/apis/rpc/api-reference/methods/getHealth.mdx b/docs/data/apis/rpc/api-reference/methods/getHealth.mdx
index a57c58296..8976a21fe 100644
--- a/docs/data/apis/rpc/api-reference/methods/getHealth.mdx
+++ b/docs/data/apis/rpc/api-reference/methods/getHealth.mdx
@@ -1,14 +1,128 @@
 ---
-hide_title: true
+title: getHealth
 description: Returns node health
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "getHealth")[0]}
-/>
+General node health check.
+
+## Params (0)
+
+## Result
+
+_(getHealthResult)_
+
+<ResponseField name="status" type="string">
+
+"healthy"
+
+</ResponseField>
+
+<ResponseField name="latestLedger" type="number">
+
+Most recent known ledger sequence
+
+</ResponseField>
+
+<ResponseField name="latestLedgerCloseTime" type="string">
+
+The unix timestamp (as a string) of the close time of the most recent known ledger
+
+</ResponseField>
+
+<ResponseField name="oldestLedger" type="number">
+
+Oldest ledger sequence kept in history
+
+</ResponseField>
+
+<ResponseField name="oldestLedgerCloseTime" type="string">
+
+The unix timestamp (as a string) of the close time of the oldest ledger kept in history
+
+</ResponseField>
+
+<ResponseField name="ledgerRetentionWindow" type="number">
+
+Maximum retention window configured. A full window state can be determined via: ledgerRetentionWindow = latestLedger - oldestLedger + 1
+
+</ResponseField>
+
+## Example
+
+Example request to the `getHealth` method
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getHealth"
+}' \
+https://soroban-testnet.stellar.org | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "getHealth",
+};
+let res = await fetch("https://soroban-testnet.stellar.org", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://soroban-testnet.stellar.org", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "getHealth"
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getHealth"
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "status": "healthy",
+    "latestLedger": 3730763,
+    "latestLedgerCloseTime": "1784671485",
+    "oldestLedger": 3609804,
+    "oldestLedgerCloseTime": "1784065656",
+    "ledgerRetentionWindow": 120960
+  }
+}
+```
+
+{/* /rpc-method */}
 
 ### Using the Lab
 
diff --git a/docs/data/apis/rpc/api-reference/methods/getLatestLedger.mdx b/docs/data/apis/rpc/api-reference/methods/getLatestLedger.mdx
index f68002218..26c0eea5f 100644
--- a/docs/data/apis/rpc/api-reference/methods/getLatestLedger.mdx
+++ b/docs/data/apis/rpc/api-reference/methods/getLatestLedger.mdx
@@ -1,14 +1,128 @@
 ---
-hide_title: true
+title: getLatestLedger
 description: Returns latest known ledger
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "getLatestLedger")[0]}
-/>
+For finding out the current latest known ledger of this node. This is a subset of the ledger info from Horizon.
+
+## Params (0)
+
+## Result
+
+_(getLatestLedgerResponse)_
+
+<ResponseField name="id" type="string">
+
+Hash identifier of the latest ledger (as a hex-encoded string) known to Stellar RPC at the time it handled the request.
+
+</ResponseField>
+
+<ResponseField name="protocolVersion" type="number">
+
+Stellar Core protocol version associated with the latest ledger.
+
+</ResponseField>
+
+<ResponseField name="sequence" type="number">
+
+The sequence number of the latest ledger known to Stellar RPC at the time it handled the request.
+
+</ResponseField>
+
+<ResponseField name="closeTime" type="string">
+
+The timestamp at which the latest ledger was closed.
+
+</ResponseField>
+
+<ResponseField name="headerXdr" type="string">
+
+The [LedgerHeader](https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-ledger.x#L74) structure for this ledger (base64-encoded string).
+
+</ResponseField>
+
+<ResponseField name="metadataXdr" type="string">
+
+The [LedgerCloseMeta](https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-ledger.x#L539) union for this ledger (base64-encoded string).
+
+</ResponseField>
+
+## Example
+
+Example request to the `getLatestLedger` method.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getLatestLedger"
+}' \
+https://soroban-testnet.stellar.org | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "getLatestLedger",
+};
+let res = await fetch("https://soroban-testnet.stellar.org", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://soroban-testnet.stellar.org", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "getLatestLedger"
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getLatestLedger"
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "id": "0a00a9cf845f7af7cff09c66f8ae6480e9971e6e2c7fa4afd8d6266ee13c987b",
+    "protocolVersion": 27,
+    "sequence": 3730795,
+    "closeTime": "1784671645",
+    "headerXdr": "CgCpz4RfevfP8Jxm+K5kgOmXHm4sf6Sv2NYmbuE8mHsAAAAbPDCnSG7CFV5/XNDJYU2mvuu7CWlGNETvjzmCB0C50X5Gm4bj+oLrMFjstd6bh+ahjUzOP//fanfkb6k4aruZ5AAAAABqX+2dAAAAAAAAAAEAAAAAtV0Qsrt9KE7VwDpHpeG1kMkPV4NVRxzEUHu+ggTSPIsAAABAcQoxoLTb8SJEAvsbXAetyT2GQeK8HMiN7z2TO4fX56R5roEd2xX5m2ii+FFlVQVErhT4KyxzN/hrbI+v2+9sCzMpCKVWHZKHWvI6d7MnLM0IZhhLZm9Cn43fPxlU5GgZVltQFYhVosSJDb2y8JpoHXePt07R4yONinsPVmZOHtwAOO1rDeC2s6dkAAAAAAO/vpEtPgAAAAAAAAAAAAX17QAAAGQATEtAAAAAyLgswiH76a8cJSTERunnOprBVOsw45eBswHJBh7QOH2GLf4GYAUflwJZdUz+pzyE1xTDFw9wViEEzJVHfgfPMfVBLqU1/WkTSpJrvCDw5YFOwWdTeyV4aQPW1Rg9Gm2gczzsqyuzzw6m/Ea/p4qmm6HSB3cImxjm7GK6fewJsfUzAAAAAAAAAAA=",
+    "metadataXdr": "AAAAAgAAAAAKAKnPhF9698/wnGb4rmSA6Zcebix/pK/Y1iZu4TyYewAAABs8MKdIbsIVXn9c0MlhTaa+67sJaUY0RO+POYIHQLnRfkabhuP6guswWOy13puH5qGNTM4//99qd+RvqThqu5nkAAAAAGpf7Z0AAAAAAAAAAQAAAAC1XRCyu30oTtXAOkel4bWQyQ9Xg1VHHMRQe76CBNI8iwAAAEBxCjGgtNvxIkQC+xtcB63JPYZB4rwcyI3vPZM7…(truncated for brevity; the full base64 LedgerCloseMeta is large)"
+  }
+}
+```
+
+{/* /rpc-method */}
 
 ### Using the Lab
 
diff --git a/docs/data/apis/rpc/api-reference/methods/getLedgerEntries.mdx b/docs/data/apis/rpc/api-reference/methods/getLedgerEntries.mdx
index a6a55b471..7de7987f0 100644
--- a/docs/data/apis/rpc/api-reference/methods/getLedgerEntries.mdx
+++ b/docs/data/apis/rpc/api-reference/methods/getLedgerEntries.mdx
@@ -1,16 +1,384 @@
 ---
-hide_title: true
+title: getLedgerEntries
 description: Returns ledger entries
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "getLedgerEntries")[0]}
-/>
+For reading the current value of ledger entries directly.
 
-# Building ledger keys
+This method enables querying live ledger state: accounts, trustlines, offers, data, claimable balances, and liquidity pools. It also provides direct access to inspect a contract's current state, its code, or any other ledger entry. This serves as a primary method to access your contract data which may not be available via events or `simulateTransaction`.
+
+To fetch contract wasm byte-code, use the ContractCode ledger entry key.
+
+## Params (2)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="keys" type="string[]" required>
+
+Array containing the keys of the ledger entries you wish to retrieve. (an array of serialized base64 strings)
+
+An array of LedgerKeys. The maximum number of ledger keys accepted is 200.
+
+</ParamField>
+
+<ParamField body="xdrFormat" type="string">
+
+Lets the user choose the format in which the response should be returned - either as unpacked JSON or as base64-encoded XDR strings. Note that you should not rely on any schema for the JSON, as it will change when the underlying XDR changes.
+
+Specifies whether XDR should be encoded as Base64 (default or 'base64') or JSON ('json').
+
+</ParamField>
+
+## Result
+
+_(getLedgerEntriesResult)_
+
+<ResponseField name="latestLedger" type="number" required>
+
+The sequence number of the latest ledger known to Stellar RPC at the time it handled the request.
+
+</ResponseField>
+
+<ResponseField name="entries" type="object[]">
+
+Array of objects containing all found ledger entries
+
+  <Expandable title="items">
+    <ResponseField name="key" type="string">
+
+      The [LedgerKey](https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-ledger-entries.x#L600) corresponding to the ledger entry (base64 string).
+
+    </ResponseField>
+    <ResponseField name="xdr" type="string">
+
+      The key's current [LedgerEntryData](https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-ledger-entries.x#L564) value (base64 string).
+
+    </ResponseField>
+    <ResponseField name="lastModifiedLedgerSeq" type="number">
+
+      The ledger sequence number of the last time this entry was updated.
+
+    </ResponseField>
+    <ResponseField name="liveUntilLedgerSeq" type="number">
+
+      The ledger sequence number of the ledger that the entry will be live until. May be zero if the entry is no longer live.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+## Examples
+
+<Tabs>
+<Tab title="Retrieve a Contract's Counter Entry for an Address">
+
+Example request to the `getNetwork` method for a `Counter(Address)` ledger entry.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getLedgerEntries",
+  "params": {
+    "keys": [
+      "AAAABgAAAAHMA/50/Q+w3Ni8UXWm/trxFBfAfl6De5kFttaMT0/ACwAAABAAAAABAAAAAgAAAA8AAAAHQ291bnRlcgAAAAASAAAAAAAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAAE="
+    ]
+  }
+}' \
+https://soroban-testnet.stellar.org | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "getLedgerEntries",
+  params: {
+    keys: [
+      "AAAABgAAAAHMA/50/Q+w3Ni8UXWm/trxFBfAfl6De5kFttaMT0/ACwAAABAAAAABAAAAAgAAAA8AAAAHQ291bnRlcgAAAAASAAAAAAAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAAE=",
+    ],
+  },
+};
+let res = await fetch("https://soroban-testnet.stellar.org", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://soroban-testnet.stellar.org", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "getLedgerEntries",
+    "params": {
+        "keys": [
+            "AAAABgAAAAHMA/50/Q+w3Ni8UXWm/trxFBfAfl6De5kFttaMT0/ACwAAABAAAAABAAAAAgAAAA8AAAAHQ291bnRlcgAAAAASAAAAAAAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAAE="
+        ]
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getLedgerEntries",
+  "params": {
+    "keys": [
+      "AAAABgAAAAHMA/50/Q+w3Ni8UXWm/trxFBfAfl6De5kFttaMT0/ACwAAABAAAAABAAAAAgAAAA8AAAAHQ291bnRlcgAAAAASAAAAAAAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAAE="
+    ]
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "entries": [
+      {
+        "key": "AAAAB+qfy4GuVKKfazvyk4R9P9fpo2n9HICsr+xqvVcTF+DC",
+        "xdr": "AAAABgAAAAAAAAABzAP+dP0PsNzYvFF1pv7a8RQXwH5eg3uZBbbWjE9PwAsAAAAQAAAAAQAAAAIAAAAPAAAAB0NvdW50ZXIAAAAAEgAAAAAAAAAAIOHWwMbBgBiAnwRt4k9nChmEOoSuLCVs2eqK9Qub+hgAAAABAAAAAwAAAAw=",
+        "lastModifiedLedgerSeq": 2552504
+      }
+    ],
+    "latestLedger": 2552990
+  }
+}
+```
+
+</Tab>
+<Tab title="Retrieve a Token's Balance Entry for Contract">
+
+Example request to the `getNetwork` method for a SAC balance ledger entry belonging to a contract.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getLedgerEntries",
+  "params": {
+    "keys": [
+      "AAAABgAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAABAAAAABAAAAAgAAAA8AAAAHQmFsYW5jZQAAAAASAAAAAcwD/nT9D7Dc2LxRdab+2vEUF8B+XoN7mQW21oxPT8ALAAAAAQ=="
+    ]
+  }
+}' \
+https://soroban-testnet.stellar.org | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "getLedgerEntries",
+  params: {
+    keys: [
+      "AAAABgAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAABAAAAABAAAAAgAAAA8AAAAHQmFsYW5jZQAAAAASAAAAAcwD/nT9D7Dc2LxRdab+2vEUF8B+XoN7mQW21oxPT8ALAAAAAQ==",
+    ],
+  },
+};
+let res = await fetch("https://soroban-testnet.stellar.org", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://soroban-testnet.stellar.org", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "getLedgerEntries",
+    "params": {
+        "keys": [
+            "AAAABgAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAABAAAAABAAAAAgAAAA8AAAAHQmFsYW5jZQAAAAASAAAAAcwD/nT9D7Dc2LxRdab+2vEUF8B+XoN7mQW21oxPT8ALAAAAAQ=="
+        ]
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getLedgerEntries",
+  "params": {
+    "keys": [
+      "AAAABgAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAABAAAAABAAAAAgAAAA8AAAAHQmFsYW5jZQAAAAASAAAAAcwD/nT9D7Dc2LxRdab+2vEUF8B+XoN7mQW21oxPT8ALAAAAAQ=="
+    ]
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "entries": [
+      {
+        "key": "AAAABgAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAABAAAAABAAAAAgAAAA8AAAAHQmFsYW5jZQAAAAASAAAAAcwD/nT9D7Dc2LxRdab+2vEUF8B+XoN7mQW21oxPT8ALAAAAAQ==",
+        "xdr": "AAAABgAAAAAAAAAB15KLcsJwPM/q9+uf9O9NUEpVqLl5/JtFDqLIQrTRzmEAAAAQAAAAAQAAAAIAAAAPAAAAB0JhbGFuY2UAAAAAEgAAAAHMA/50/Q+w3Ni8UXWm/trxFBfAfl6De5kFttaMT0/ACwAAAAEAAAARAAAAAQAAAAMAAAAPAAAABmFtb3VudAAAAAAACgAAAAAAAAAAAAAAAB3NZQAAAAAPAAAACmF1dGhvcml6ZWQAAAAAAAAAAAABAAAADwAAAAhjbGF3YmFjawAAAAAAAAAA",
+        "lastModifiedLedgerSeq": 2553612
+      }
+    ],
+    "latestLedger": 2553713
+  }
+}
+```
+
+</Tab>
+<Tab title="Retrieve Multiple Ledger Entries from Different Contracts.">
+
+Example request to the `getNetwork` method for a `Counter(Address)` ledger entry and a SAC balance ledger entry.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getLedgerEntries",
+  "params": {
+    "keys": [
+      "AAAABgAAAAHMA/50/Q+w3Ni8UXWm/trxFBfAfl6De5kFttaMT0/ACwAAABAAAAABAAAAAgAAAA8AAAAHQ291bnRlcgAAAAASAAAAAAAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAAE=",
+      "AAAABgAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAABAAAAABAAAAAgAAAA8AAAAHQmFsYW5jZQAAAAASAAAAAcwD/nT9D7Dc2LxRdab+2vEUF8B+XoN7mQW21oxPT8ALAAAAAQ=="
+    ]
+  }
+}' \
+https://soroban-testnet.stellar.org | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "getLedgerEntries",
+  params: {
+    keys: [
+      "AAAABgAAAAHMA/50/Q+w3Ni8UXWm/trxFBfAfl6De5kFttaMT0/ACwAAABAAAAABAAAAAgAAAA8AAAAHQ291bnRlcgAAAAASAAAAAAAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAAE=",
+      "AAAABgAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAABAAAAABAAAAAgAAAA8AAAAHQmFsYW5jZQAAAAASAAAAAcwD/nT9D7Dc2LxRdab+2vEUF8B+XoN7mQW21oxPT8ALAAAAAQ==",
+    ],
+  },
+};
+let res = await fetch("https://soroban-testnet.stellar.org", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://soroban-testnet.stellar.org", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "getLedgerEntries",
+    "params": {
+        "keys": [
+            "AAAABgAAAAHMA/50/Q+w3Ni8UXWm/trxFBfAfl6De5kFttaMT0/ACwAAABAAAAABAAAAAgAAAA8AAAAHQ291bnRlcgAAAAASAAAAAAAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAAE=",
+            "AAAABgAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAABAAAAABAAAAAgAAAA8AAAAHQmFsYW5jZQAAAAASAAAAAcwD/nT9D7Dc2LxRdab+2vEUF8B+XoN7mQW21oxPT8ALAAAAAQ=="
+        ]
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getLedgerEntries",
+  "params": {
+    "keys": [
+      "AAAABgAAAAHMA/50/Q+w3Ni8UXWm/trxFBfAfl6De5kFttaMT0/ACwAAABAAAAABAAAAAgAAAA8AAAAHQ291bnRlcgAAAAASAAAAAAAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAAE=",
+      "AAAABgAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAABAAAAABAAAAAgAAAA8AAAAHQmFsYW5jZQAAAAASAAAAAcwD/nT9D7Dc2LxRdab+2vEUF8B+XoN7mQW21oxPT8ALAAAAAQ=="
+    ]
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "entries": [
+      {
+        "key": "AAAABgAAAAHMA/50/Q+w3Ni8UXWm/trxFBfAfl6De5kFttaMT0/ACwAAABAAAAABAAAAAgAAAA8AAAAHQ291bnRlcgAAAAASAAAAAAAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAAE=",
+        "xdr": "AAAABgAAAAAAAAAB15KLcsJwPM/q9+uf9O9NUEpVqLl5/JtFDqLIQrTRzmEAAAAQAAAAAQAAAAIAAAAPAAAAB0JhbGFuY2UAAAAAEgAAAAHMA/50/Q+w3Ni8UXWm/trxFBfAfl6De5kFttaMT0/ACwAAAAEAAAARAAAAAQAAAAMAAAAPAAAABmFtb3VudAAAAAAACgAAAAAAAAAAAAAAAB3NZQAAAAAPAAAACmF1dGhvcml6ZWQAAAAAAAAAAAABAAAADwAAAAhjbGF3YmFjawAAAAAAAAAA",
+        "lastModifiedLedgerSeq": 2553612
+      },
+      {
+        "key": "AAAABgAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAABAAAAABAAAAAgAAAA8AAAAHQmFsYW5jZQAAAAASAAAAAcwD/nT9D7Dc2LxRdab+2vEUF8B+XoN7mQW21oxPT8ALAAAAAQ==",
+        "xdr": "AAAABgAAAAAAAAABzAP+dP0PsNzYvFF1pv7a8RQXwH5eg3uZBbbWjE9PwAsAAAAQAAAAAQAAAAIAAAAPAAAAB0NvdW50ZXIAAAAAEgAAAAAAAAAAIOHWwMbBgBiAnwRt4k9nChmEOoSuLCVs2eqK9Qub+hgAAAABAAAAAwAAAAw=",
+        "lastModifiedLedgerSeq": 2552504
+      }
+    ],
+    "latestLedger": 2553767
+  }
+}
+```
+
+</Tab>
+</Tabs>
+
+{/* /rpc-method */}
+
+## Building ledger keys
 
 The Stellar ledger is, on some level, essentially a key-value store. The keys are instances of [`LedgerKey`](https://github.com/stellar/stellar-xdr/blob/v25.0/Stellar-ledger-entries.x#L588) and the values are instances of [`LedgerEntry`](https://github.com/stellar/stellar-xdr/blob/v25.0/Stellar-ledger-entries.x#L548). An interesting product of the store's internal design is that the key is a _subset_ of the entry: we'll see more of this later.
 
@@ -20,12 +388,12 @@ The `getLedgerEntries` method returns the "values" (or "entries") for a given se
 
 The source of truth should always be the XDR defined in the protocol. `LedgerKey`s are a union type defined in [Stellar-ledger-entries.x](https://github.com/stellar/stellar-xdr/blob/v25.0/Stellar-ledger-entries.x#L588). There are 10 different forms a ledger key can take:
 
-1. **Account:** holistically defines a Stellar account, including its balance, signers, etc. (see [Accounts](../../../../../learn/fundamentals/stellar-data-structures/accounts.mdx))
-2. **Trustline:** defines a balance line to a non-native asset issued on the network (see [`changeTrustOp`](../../../../../learn/fundamentals/transactions/list-of-operations.mdx#change-trust))
-3. **Offer:** defines an offer made on the Stellar DEX (see [Liquidity on Stellar](../../../../../learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx))
-4. **Account Data:** defines key-value data entries attached to an account (see [`manageDataOp`](../../../../../learn/fundamentals/transactions/list-of-operations.mdx#manage-data))
-5. **Claimable Balance:** defines a balance that may or may not actively be claimable (see [Claimable Balances](../../../../../build/guides/transactions/claimable-balances.mdx))
-6. **Liquidity Pool:** defines the configuration of a native constant liquidity pool between two assets (see [Liquidity on Stellar](../../../../../learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx))
+1. **Account:** holistically defines a Stellar account, including its balance, signers, etc. (see [Accounts](../../../../../learn/fundamentals/stellar-data-structures/accounts))
+2. **Trustline:** defines a balance line to a non-native asset issued on the network (see [`changeTrustOp`](../../../../../learn/fundamentals/transactions/list-of-operations#change-trust))
+3. **Offer:** defines an offer made on the Stellar DEX (see [Liquidity on Stellar](../../../../../learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools))
+4. **Account Data:** defines key-value data entries attached to an account (see [`manageDataOp`](../../../../../learn/fundamentals/transactions/list-of-operations#manage-data))
+5. **Claimable Balance:** defines a balance that may or may not actively be claimable (see [Claimable Balances](../../../../../build/guides/transactions/claimable-balances))
+6. **Liquidity Pool:** defines the configuration of a native constant liquidity pool between two assets (see [Liquidity on Stellar](../../../../../learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools))
 7. **Contract Data:** defines a piece of data being stored in a contract under a key
 8. **Contract Code:** defines the Wasm bytecode of a contract
 9. **Config Setting:** defines the currently active network configuration
@@ -37,9 +405,9 @@ We're going to focus on a subset of these for maximum value, but once you unders
 
 To fetch an account, all you need is its public key:
 
-<CodeExample>
+<CodeGroup>
 
-```typescript
+```typescript TypeScript
 import { Keypair, xdr } from "@stellar/stellar-sdk";
 
 const publicKey = "GALAXYVOIDAOPZTDLHILAJQKCVVFMD4IKLXLSZV5YHO7VY74IWZILUTO";
@@ -51,7 +419,7 @@ const accountLedgerKey = xdr.LedgerKey.ledgerKeyAccount(
 console.log(accountLedgerKey.toXDR("base64"));
 ```
 
-```python
+```python Python
 from stellar_sdk import Keypair, xdr
 
 public_key = "GALAXYVOIDAOPZTDLHILAJQKCVVFMD4IKLXLSZV5YHO7VY74IWZILUTO"
@@ -64,31 +432,31 @@ account_ledger_key = xdr.LedgerKey(
 print(account_ledger_key.to_xdr())
 ```
 
-</CodeExample>
+</CodeGroup>
 
 This will give you the full account details.
 
-<CodeExample>
+<CodeGroup>
 
-```typescript
+```typescript TypeScript
 const accountEntryData = (
   await s.getLedgerEntries(accountLedgerKey)
 ).entries[0].account();
 ```
 
-```python
+```python Python
 account_entry_data = xdr.LedgerEntryData.from_xdr(
     server.get_ledger_entries([account_ledger_key]).entries[0].xdr
 ).account
 ```
 
-</CodeExample>
+</CodeGroup>
 
 If you just want to take a look at the structure, you can pass the raw base64 value we logged above to the [Laboratory](https://lab.stellar.org/endpoints/rpc/get-ledger-entries?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;&endpoints$params$xdrFormat=json;;) (or via `curl` if you pass `"xdrFormat": "json"` as an additional parameter to `getLedgerEntries`) and see all of the possible fields. You can also dig into them in code, of course:
 
-<CodeExample>
+<CodeGroup>
 
-```typescript
+```typescript TypeScript
 console.log(
   `Account ${publicKey} has ${accountEntryData
     .balance()
@@ -98,21 +466,21 @@ console.log(
 );
 ```
 
-```python
+```python Python
 print(
     f"Account {public_key} has {account_entry_data.balance.int64} stroops of XLM and is on sequence number {account_entry_data.seq_num.sequence_number.int64}"
 )
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Trustlines
 
 A trustline is a balance entry for any non-native asset (such as [Circle's USDC](https://stellar.expert/explorer/public/asset/USDC-GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN)). To fetch one, you need the trustline owner (a public key like for [Accounts](#accounts)) and the asset in question:
 
-<CodeExample>
+<CodeGroup>
 
-```typescript
+```typescript TypeScript
 const trustlineLedgerKey = xdr.LedgerKey.ledgerKeyTrustLine(
   new xdr.LedgerKeyTrustLine({
     accountId: Keypair.fromPublicKey(publicKey).xdrAccountId(),
@@ -124,7 +492,7 @@ const trustlineLedgerKey = xdr.LedgerKey.ledgerKeyTrustLine(
 );
 ```
 
-```python
+```python Python
 trustline_ledger_key = xdr.LedgerKey(
     type=xdr.LedgerEntryType.TRUSTLINE,
     trust_line=xdr.LedgerKeyTrustLine(
@@ -140,13 +508,13 @@ trustline_entry_data = xdr.LedgerEntryData.from_xdr(
 ).trust_line
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Much like an [account](#accounts), the resulting entry has a balance, but it also has a limit and flags to control how much of that asset can be held. The asset, however, can be either an issued asset or a liquidity pool:
 
-<CodeExample>
+<CodeGroup>
 
-```typescript
+```typescript TypeScript
 let asset: string;
 let rawAsset = trustlineEntryData.asset();
 
@@ -177,7 +545,7 @@ console.log(
 );
 ```
 
-```python
+```python Python
 raw_asset = trustline_entry_data.asset
 asset: str = ""
 
@@ -198,15 +566,15 @@ print(
 )
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Contract Data
 
 Suppose we've deployed the [`increment` example contract] and want to find out what value is stored in the `COUNTER` ledger key. To build the key:
 
-<CodeExample>
+<CodeGroup>
 
-```typescript
+```typescript TypeScript
 import { xdr, Address } from "@stellar/stellar-sdk";
 
 const getLedgerKeySymbol = (
@@ -231,7 +599,7 @@ const ledgerKey = getLedgerKeySymbol(
 );
 ```
 
-```python
+```python Python
 from stellar_sdk import xdr, scval, Address
 
 def get_ledger_key_symbol(contract_id: str, symbol_text: str) -> str:
@@ -253,7 +621,7 @@ print(
 )
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Contract Wasm Code
 
@@ -269,9 +637,9 @@ Thus, fetching the contract code is a two-step process:
 
 #### 1. Find the ledger key for the contract instance
 
-<CodeExample>
+<CodeGroup>
 
-```typescript
+```typescript TypeScript
 import { Contract } from "@stellar/stellar-sdk";
 
 function getLedgerKeyContractCode(contractId): xdr.LedgerKey {
@@ -285,7 +653,7 @@ console.log(
 );
 ```
 
-```python
+```python Python
 from stellar_sdk import xdr, Address
 
 def get_ledger_key_contract_code(contract_id: str) -> xdr.LedgerKey:
@@ -303,7 +671,7 @@ print(get_ledger_key_contract_code(
 ))
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Once we have the ledger entry (via `getLedgerEntries`, see [below](#actually-fetching-the-ledger-entry-data)), we can extract the Wasm hash:
 
@@ -311,9 +679,9 @@ Once we have the ledger entry (via `getLedgerEntries`, see [below](#actually-fet
 
 Now take the `xdr` field from the previous response's `result` object, and create a `LedgerKey` from the hash contained inside.
 
-<CodeExample>
+<CodeGroup>
 
-```typescript
+```typescript TypeScript
 import { xdr } from "@stellar/stellar-sdk";
 
 function getLedgerKeyWasmId(
@@ -329,7 +697,7 @@ function getLedgerKeyWasmId(
 }
 ```
 
-```python
+```python Python
 from stellar_sdk import xdr
 
 def get_ledger_key_wasm_id(
@@ -349,13 +717,13 @@ def get_ledger_key_wasm_id(
   return ledger_key
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Now, finally we have a `LedgerKey` that correspond to the Wasm byte-code that has been deployed under the `contractId` we started out with so very long ago. This `LedgerKey` can be used in a final request to `getLedgerEntries`. In that response we will get a `LedgerEntryData` corresponding to a `ContractCodeEntry` which will contain the actual, deployed, real-life contract byte-code:
 
-<CodeExample>
+<CodeGroup>
 
-```typescript
+```typescript TypeScript
 const theHashData: xdr.ContractDataEntry = await getLedgerEntries(
   getLedgerKeyContractCode("C..."),
 ).entries[0].contractData();
@@ -365,7 +733,7 @@ const theCode: Buffer = await getLedgerEntries(getLedgerKeyWasmId(theHashData))
   .code();
 ```
 
-```python
+```python Python
 the_hash_data = xdr.LedgerEntryData.from_xdr(
     server.get_ledger_entries([get_ledger_key_contract_code("C...")]).entries[0].xdr
 ).contract_data
@@ -375,15 +743,15 @@ the_code = xdr.LedgerEntryData.from_xdr(
 ).contract_code.code
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## Actually fetching the ledger entry data
 
 Once we've learned to _build_ and _parse_ these (which we've done above at length), the process for actually fetching them is always identical. If you know the type of key you fetched, you apply the accessor method accordingly once you've received them from the `getLedgerEntries` method:
 
-<CodeExample>
+<CodeGroup>
 
-```typescript
+```typescript TypeScript
 const s = new Server("https://soroban-testnet.stellar.org");
 
 // assume key1 is an account, key2 is a trustline, and key3 is contract data
@@ -394,7 +762,7 @@ const trustline = response.entries[1].trustline();
 const contractData = response.entries[2].contractData();
 ```
 
-```python
+```python Python
 server = SorobanServer("https://soroban-testnet.stellar.org")
 
 # assume key1 is an account, key2 is a trustline, and key3 is contract data
@@ -404,7 +772,7 @@ trustline = xdr.LedgerEntryData.from_xdr(response.entries[1].xdr).trust_line
 contract_data = xdr.LedgerEntryData.from_xdr(response.entries[2].xdr).contract_data
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Now, finally we have a `LedgerKey` that correspond to the Wasm byte-code that has been deployed under the `ContractId` we started out with so very long ago. This `LedgerKey` can be used in a final request to the Stellar-RPC endpoint.
 
@@ -427,7 +795,7 @@ Then you can inspect them accordingly. Each of the above entries follows the XDR
 
 ## Viewing and understanding XDR
 
-If you don't want to parse the XDR out programmatically, you can also leverage both the [Stellar CLI](../../../../../tools/cli/stellar-cli.mdx) and the [Stellar Lab](https://lab.stellar.org/xdr/view) to get a human-readable view of ledger keys and entries. For example,
+If you don't want to parse the XDR out programmatically, you can also leverage both the [Stellar CLI](../../../../../tools/cli/stellar-cli) and the [Stellar Lab](https://lab.stellar.org/xdr/view) to get a human-readable view of ledger keys and entries. For example,
 
 ```bash
 echo 'AAAAAAAAAAAL76GC5jcgEGfLG9+nptaB9m+R44oweeN3EcqhstdzhQ==' | stellar xdr decode --type LedgerKey --output json-formatted
diff --git a/docs/data/apis/rpc/api-reference/methods/getLedgers.mdx b/docs/data/apis/rpc/api-reference/methods/getLedgers.mdx
index 47d1696cc..6484ae541 100644
--- a/docs/data/apis/rpc/api-reference/methods/getLedgers.mdx
+++ b/docs/data/apis/rpc/api-reference/methods/getLedgers.mdx
@@ -1,14 +1,233 @@
 ---
-hide_title: true
+title: getLedgers
 description: Returns list of ledgers
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "getLedgers")[0]}
-/>
+The `getLedgers` method returns a detailed list of ledgers starting from the user specified starting point that you can paginate as long as the pages fall within the history retention of their corresponding RPC provider.
+
+## Params (3)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="startLedger" type="number">
+
+Ledger sequence number to start fetching responses from (inclusive). This method will return an error if `startLedger` is less than the oldest ledger stored in this node, or greater than the latest ledger seen by this node. If a cursor is included in the request, `startLedger` must be omitted.
+
+Sequence number of the ledger.
+
+</ParamField>
+
+<ParamField body="pagination" type="object">
+
+Pagination in stellar-rpc is similar to pagination in Horizon. See [Pagination](https://developers.stellar.org/docs/data/rpc/api-reference/structure/pagination).
+
+  <Expandable title="properties">
+    <ParamField body="cursor" type="string">
+
+      An opaque string which acts as a paging token. To obtain the next page of results occurring after a given response set this value to the `cursor` field of the response.
+
+    </ParamField>
+    <ParamField body="limit" type="number">
+
+      The maximum number of records returned. The limit for getLedgers can range from 1 to 200 - an upper limit that is hardcoded in Stellar-RPC for performance reasons. If this argument isn't designated, it defaults to 50.
+
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+<ParamField body="xdrFormat" type="string">
+
+Lets the user choose the format in which the response should be returned - either as unpacked JSON or as base64-encoded XDR strings. Note that you should not rely on any schema for the JSON, as it will change when the underlying XDR changes.
+
+Specifies whether XDR should be encoded as Base64 (default or 'base64') or JSON ('json').
+
+</ParamField>
+
+## Result
+
+_(getLedgersResult)_
+
+<ResponseField name="ledgers" type="object[]">
+  <Expandable title="items">
+    <ResponseField name="hash" type="string">
+
+      The hash of the ledger header which was included in the chain
+
+    </ResponseField>
+    <ResponseField name="sequence" type="number">
+
+      The sequence number of the ledger (sometimes called the 'block height').
+
+    </ResponseField>
+    <ResponseField name="ledgerCloseTime" type="string">
+
+      The unix timestamp (as a string) at which the ledger was closed.
+
+    </ResponseField>
+    <ResponseField name="headerXdr" type="string">
+
+      The [LedgerHeaderHistoryEntry](https://github.com/stellar/stellar-xdr/blob/v26.0/Stellar-ledger.x#L277) structure for this ledger (base64-encoded string).
+
+    </ResponseField>
+    <ResponseField name="metadataXdr" type="string">
+
+      The [LedgerCloseMeta](https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-ledger.x#L539) union for this ledger (base64-encoded string).
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="latestLedger" type="number">
+
+The sequence number of the latest ledger known to Stellar RPC at the time it handled the request.
+
+</ResponseField>
+
+<ResponseField name="latestLedgerCloseTime" type="number">
+
+The unix timestamp of the close time of the latest ledger known to Stellar RPC at the time it handled the request.
+
+</ResponseField>
+
+<ResponseField name="oldestLedger" type="number">
+
+The sequence number of the oldest ledger ingested by Stellar RPC at the time it handled the request.
+
+</ResponseField>
+
+<ResponseField name="oldestLedgerCloseTime" type="number">
+
+The unix timestamp of the close time of the oldest ledger ingested by Stellar RPC at the time it handled the request.
+
+</ResponseField>
+
+<ResponseField name="cursor" type="string">
+
+A token which can be included in a subsequent request to obtain the next page of results.
+
+</ResponseField>
+
+## Example
+
+Query a list of ledgers starting from the given startLedger.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getLedgers",
+  "params": {
+    "startLedger": 36233,
+    "pagination": {
+      "limit": 2
+    }
+  }
+}' \
+https://soroban-testnet.stellar.org | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "getLedgers",
+  params: {
+    startLedger: 36233,
+    pagination: {
+      limit: 2,
+    },
+  },
+};
+let res = await fetch("https://soroban-testnet.stellar.org", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://soroban-testnet.stellar.org", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "getLedgers",
+    "params": {
+        "startLedger": 36233,
+        "pagination": {
+            "limit": 2
+        }
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getLedgers",
+  "params": {
+    "startLedger": 36233,
+    "pagination": {
+      "limit": 2
+    }
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "ledgers": [
+      {
+        "hash": "434de11b427aa4b6f8cda259ac2111a6aa148d2ab6b4c7affe864e94a9f4bd80",
+        "sequence": 36233,
+        "ledgerCloseTime": "1734032457",
+        "headerXdr": "Q03hG0J6pLb4zaJZrCERpqoUjSq2tMev/oZOlKn0vYAAAAAWY6AkQmSfV+Rrnpq308LrTR1IZq7dUQr4HkNPlpDpw4/4WH/HGddpIrl1KZiCUKzFOi9sqkX+b56aTGNqhTRHtwAAAABnWzxJAAAAAAAAAAEAAAAAqCTNGLyddQZNKZpbW6ykO8OqLzJpOBU9jC+btctt8DMAAABAjksBzacOp2IR06utjCmZ0QR6kgidREHCceghZapmZdNrS1uBiBG8Zz5Eh7uxMga5IAHPVbkSgFgXzjwRk4i2At8/YZgEqS/bQFcZLcQ910jqd4rcUrxJjOgFJMAUuBEZkxHVMCvc1iIZj7nTD2d91KT24H9FpOIGJLSiTuwys+0AAI2JDeC2s6dkAAAAAAAIewDXaQAAAAAAAAAAAAAB3wAAAGQATEtAAAAAyESlcNBlpidDCvLHH8Nu1MWDHWwUXTfbvGKqvbvlzzrb2GJe+2UfU8rr8mWrJXRTcQhl5UYgKhOQUOWP1nWgbp4AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=",
+        "metadataXdr": "AAAAAQAAAABDTeEbQnqktvjNolmsIRGmqhSNKra0x6/+hk6UqfS9gAAAABZjoCRCZJ9X5GuemrfTwutNHUhmrt1RCvgeQ0+WkOnDj/hYf8cZ12kiuXUpmIJQrMU6L2yqRf5vnppMY2qFNEe3AAAAAGdbPEkAAAAAAAAAAQAAAACoJM0YvJ11Bk0pmltbrKQ7w6ovMmk4FT2ML5u1y23wMwAAAECOSwHNpw6nYhHTq62MKZnRBHqSCJ1EQcJx6CFlqmZl02tLW4GIEbxnPkSHu7EyBrkgAc9VuRKAWBfOPBGTiLYC3z9hmASpL9tAVxktxD3XSOp3itxSvEmM6AUkwBS4ERmTEdUwK9zWIhmPudMPZ33UpPbgf0Wk4gYktKJO7DKz7QAAjYkN4Lazp2QAAAAAAAh7ANdpAAAAAAAAAAAAAAHfAAAAZABMS0AAAADIRKVw0GWmJ0MK8scfw27UxYMdbBRdN9u8Yqq9u+XPOtvYYl77ZR9TyuvyZasldFNxCGXlRiAqE5BQ5Y/WdaBungAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAFjoCRCZJ9X5GuemrfTwutNHUhmrt1RCvgeQ0+WkOnDjwAAAAIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADVBewAAAAAAAAAAA=="
+      },
+      {
+        "hash": "201f38ca43cfad09d00287ee70d77edc8c88a61e018683fd466e71688222a217",
+        "sequence": 36234,
+        "ledgerCloseTime": "1734032462",
+        "headerXdr": "IB84ykPPrQnQAofucNd+3IyIph4BhoP9Rm5xaIIiohcAAAAWQ03hG0J6pLb4zaJZrCERpqoUjSq2tMev/oZOlKn0vYB8UE9ZJ4uLDnIu/g7+08D/eYnJjrJD07fGpWaVoLi29wAAAABnWzxOAAAAAAAAAAEAAAAAtV0Qsrt9KE7VwDpHpeG1kMkPV4NVRxzEUHu+ggTSPIsAAABAN6Cc3KxXPM2WmFDtY/yPZM0aha2yhnHFBDaliMqO6BzVQMb9Zlq5DoGrLr/xoFOp8YJ3RjLedF8w/KfN3ogPBuzRjPABveSt1CvvmDdnwUpSXyUsjdjECdbpjuKxaZZR+NeVPfeYT06qs2v4JwBff4WWpIGwEXPcxq3tZKuekH8AAI2KDeC2s6dkAAAAAAAIewDaiQAAAAAAAAAAAAAB3wAAAGQATEtAAAAAyESlcNBlpidDCvLHH8Nu1MWDHWwUXTfbvGKqvbvlzzrb2GJe+2UfU8rr8mWrJXRTcQhl5UYgKhOQUOWP1nWgbp4AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=",
+        "metadataXdr": "AAAAAQAAAAAgHzjKQ8+tCdACh+5w137cjIimHgGGg/1GbnFogiKiFwAAABZDTeEbQnqktvjNolmsIRGmqhSNKra0x6/+hk6UqfS9gHxQT1kni4sOci7+Dv7TwP95icmOskPTt8alZpWguLb3AAAAAGdbPE4AAAAAAAAAAQAAAAC1XRCyu30oTtXAOkel4bWQyQ9Xg1VHHMRQe76CBNI8iwAAAEA3oJzcrFc8zZaYUO1j/I9kzRqFrbKGccUENqWIyo7oHNVAxv1mWrkOgasuv/GgU6nxgndGMt50XzD8p83eiA8G7NGM8AG95K3UK++YN2fBSlJfJSyN2MQJ1umO4rFpllH415U995hPTqqza/gnAF9/hZakgbARc9zGre1kq56QfwAAjYoN4Lazp2QAAAAAAAh7ANqJAAAAAAAAAAAAAAHfAAAAZABMS0AAAADIRKVw0GWmJ0MK8scfw27UxYMdbBRdN9u8Yqq9u+XPOtvYYl77ZR9TyuvyZasldFNxCGXlRiAqE5BQ5Y/WdaBungAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAFDTeEbQnqktvjNolmsIRGmqhSNKra0x6/+hk6UqfS9gAAAAAIAAAAAAAAAAQAAAAAAAAABAAAAAAAAAGQAAAAEAAAAAgAAAAA1F1Ya+0O+eQhWGWasX1tP8XnT8KbByGO5FML7jU5klgAehIAAACHEAAAXJAAAAAEAAAAAAAAAAAAAAABnWzyHAAAAAQAAAAhwc3BiOjc3NAAAAAIAAAABAAAAAIqW61Q3kZPdQ6gTYFSQ20kTCiKkY6KcEWxC1eCkhkzFAAAAAQAAAADjfej7Kt6ZZTe3zxwql+kdH4kwVHjgkfOYEaeLqGoIRgAAAAJBVFVBSAAAAAAAAAAAAAAAZ8rWY3iaDnWNtfpvLpNaCEbKdDjrd2gQODOuKpmj1vMAAAAABo53gAAAAAEAAAAAipbrVDeRk91DqBNgVJDbSRMKIqRjopwRbELV4KSGTMUAAAABAAAAAON96Psq3pllN7fPHCqX6R0fiTBUeOCR85gRp4uoaghGAAAAAkFUVVNEAAAAAAAAAAAAAABnytZjeJoOdY21+m8uk1oIRsp0OOt3aBA4M64qmaPW8wAAAAAAOHUgAAAAAAAAAAKNTmSWAAAAQA8LFEGM2p68s9GHmYgL2JnpbAVCKHeOxtG/HkcxqacuNQqISa3Iq9piWDeY2ZRwLvRb5w3QU34rY0jVzALXNQekhkzFAAAAQGg6RE0OGGeH7F4ufEGlDq4vNvSrP+OsCEVA5HarIQmWECDYhw4gJttA7J3XqC7KFony4S1HxRyJVPj82+VErgcAAAACAAAAAI8ylQbZjflZClH425dyBEYnAc8VJv4R020WOQKf612dAB6EgAAAIksAABn5AAAAAQAAAAAAAAAAAAAAAGdbPIkAAAABAAAACXBzcGI6NTgxNgAAAAAAAAIAAAABAAAAALyBL9daiYtaADzcZA8i3U28u/d5KV2Cu3cJTM1hY1NAAAAAAQAAAAAoQ0HJTIQcw+IUqbqLK9ekDhTGjbbaKXXzFPSAIirHIAAAAAJBVFNCUElVU0QAAAAAAAAAvIEv11qJi1oAPNxkDyLdTby793kpXYK7dwlMzWFjU0AAAAAAAvfjQAAAAAEAAAAAvIEv11qJi1oAPNxkDyLdTby793kpXYK7dwlMzWFjU0AAAAABAAAAAFh1GtTOa90yTcX7I+Q6WWd9N1ZBXtyHPDTZaib7m3SbAAAAAkFUU0JQSVVTRAAAAAAAAAC8gS/XWomLWgA83GQPIt1NvLv3eSldgrt3CUzNYWNTQAAAAAAAAw1AAAAAAAAAAAKf612dAAAAQNSwd8tthlQCQ1doozKPn4Qgtv+kIuCrdwHGChRG4dR+wjQuDwcuyBVXFJzZrVThq9cu/arC/KzAimTxlZ8SXgxhY1NAAAAAQF4liVjujCjZjgin8A8S0eg9R15lgQbAbjpr6NgNiLfXb6hWH7yq+zvWTnyEP/+/Do2VlXHH3VS7dImzcK2BawEAAAACAAAAAEBQYAimx5waQHaAptKgy2a/IAHMSe96ETt5wiMOSpKXAB6EgAAAIdQAABcgAAAAAQAAAAAAAAAAAAAAAGdbPIcAAAABAAAACHBzcGI6NDc5AAAAAgAAAAEAAAAAipbrVDeRk91DqBNgVJDbSRMKIqRjopwRbELV4KSGTMUAAAABAAAAAON96Psq3pllN7fPHCqX6R0fiTBUeOCR85gRp4uoaghGAAAAAkFUVUFIAAAAAAAAAAAAAABnytZjeJoOdY21+m8uk1oIRsp0OOt3aBA4M64qmaPW8wAAAAAGjneAAAAAAQAAAACKlutUN5GT3UOoE2BUkNtJEwoipGOinBFsQtXgpIZMxQAAAAEAAAAA433o+yremWU3t88cKpfpHR+JMFR44JHzmBGni6hqCEYAAAACQVRVU0QAAAAAAAAAAAAAAGfK1mN4mg51jbX6by6TWghGynQ463doEDgzriqZo9bzAAAAAAA4dSAAAAAAAAAAAg5KkpcAAABAEkPvoJlXL/V+TiEP8eiBhIg7SqIN3Tg7GWHVrNPWdi+iPdWLiXtYdfeylyBiDS84qWyNeSk7oQs35lXIN6nxCKSGTMUAAABA5JlXPTUOGN9PIaM/2CzCQ5uv39K6rHCmnmaUDXWiibbsPSpVwQPoCSFjcfH/Gu9vzKdPM1Ia2/OEr14WSDBNDAAAAAIAAAAAF4G//fAShUcDgR3xGIa+nyNyQErjHHAiPpPDSm1Q8mgAHoSAAAAh1QAAFx8AAAABAAAAAAAAAAAAAAAAZ1s8iAAAAAEAAAAIcHNwYjo2NTcAAAACAAAAAQAAAACKlutUN5GT3UOoE2BUkNtJEwoipGOinBFsQtXgpIZMxQAAAAEAAAAA433o+yremWU3t88cKpfpHR+JMFR44JHzmBGni6hqCEYAAAACQVRVU0QAAAAAAAAAAAAAAGfK1mN4mg51jbX6by6TWghGynQ463doEDgzriqZo9bzAAAAAAA4dSAAAAABAAAAAIqW61Q3kZPdQ6gTYFSQ20kTCiKkY6KcEWxC1eCkhkzFAAAAAQAAAADjfej7Kt6ZZTe3zxwql+kdH4kwVHjgkfOYEaeLqGoIRgAAAAJBVFVBSAAAAAAAAAAAAAAAZ8rWY3iaDnWNtfpvLpNaCEbKdDjrd2gQODOuKpmj1vMAAAAABo53gAAAAAAAAAACbVDyaAAAAEB2pWOQ6oNzzFMA0ejSrpJr+Ltj7tTAz5p3j0DWktnsdi2hWMTwMZMSl+PTJrisS80wOhG3Kqe8dnNaIP6QJ9gHpIZMxQAAAEC8fqM6Vf/ZlzfecYiMsiFsk5T4xb9/Yg2Lpu9Kjo/aCvoxnTM9npu1S+NQONm+DVO/E+QCR+FoThukfzo7vSMFAAAAAAAAAAAAAAAETK9HXjqvIoZ83nB+r4yyVcLFoSyJQHGFzTddGlKGQC0AAAAAAAAAyP////8AAAACAAAAAAAAAAH////7AAAAAAAAAAH////7AAAAAAAAAAIAAAADAACNhgAAAAAAAAAAF4G//fAShUcDgR3xGIa+nyNyQErjHHAiPpPDSm1Q8mgAAAAXSGYyRAAAIdUAABceAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAwAAAAAAAI2GAAAAAGdbPDoAAAAAAAAAAQAAjYoAAAAAAAAAABeBv/3wEoVHA4Ed8RiGvp8jckBK4xxwIj6Tw0ptUPJoAAAAF0hmMXwAACHVAAAXHgAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAAAAAAMAAAAAAACNhgAAAABnWzw6AAAAAAAAAAMAAAAAAAAAAgAAAAMAAI2KAAAAAAAAAAAXgb/98BKFRwOBHfEYhr6fI3JASuMccCI+k8NKbVDyaAAAABdIZjF8AAAh1QAAFx4AAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAAAAAADAAAAAAAAjYYAAAAAZ1s8OgAAAAAAAAABAACNigAAAAAAAAAAF4G//fAShUcDgR3xGIa+nyNyQErjHHAiPpPDSm1Q8mgAAAAXSGYxfAAAIdUAABcfAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAwAAAAAAAI2KAAAAAGdbPE4AAAAAAAAAAAAAAAAAAAAAlHPkmVMd4KxXSFzK1ZnlVOu6ZVnmeoceJG8N8mqptnsAAAAAAAAAyP////8AAAACAAAAAAAAAAH////7AAAAAAAAAAH////7AAAAAAAAAAIAAAADAACNhgAAAAAAAAAAQFBgCKbHnBpAdoCm0qDLZr8gAcxJ73oRO3nCIw5KkpcAAAAXSGYx4AAAIdQAABcfAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAwAAAAAAAI2GAAAAAGdbPDoAAAAAAAAAAQAAjYoAAAAAAAAAAEBQYAimx5waQHaAptKgy2a/IAHMSe96ETt5wiMOSpKXAAAAF0hmMRgAACHUAAAXHwAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAAAAAAMAAAAAAACNhgAAAABnWzw6AAAAAAAAAAMAAAAAAAAAAgAAAAMAAI2KAAAAAAAAAABAUGAIpsecGkB2gKbSoMtmvyABzEnvehE7ecIjDkqSlwAAABdIZjEYAAAh1AAAFx8AAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAAAAAADAAAAAAAAjYYAAAAAZ1s8OgAAAAAAAAABAACNigAAAAAAAAAAQFBgCKbHnBpAdoCm0qDLZr8gAcxJ73oRO3nCIw5KkpcAAAAXSGYxGAAAIdQAABcgAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAwAAAAAAAI2KAAAAAGdbPE4AAAAAAAAAAAAAAAAAAAAAYSf/ygwR8YuXauwz38GEKXDIyITlfP88Z2wGEAWJqSgAAAAAAAAAyP////8AAAACAAAAAAAAAAEAAAAAAAAAAAAAAAH////6AAAAAAAAAAIAAAADAACNgAAAAAAAAAAAjzKVBtmN+VkKUfjbl3IERicBzxUm/hHTbRY5Ap/rXZ0AAAAXSGKhYAAAIksAABn4AAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAwAAAAAAAI2AAAAAAGdbPBwAAAAAAAAAAQAAjYoAAAAAAAAAAI8ylQbZjflZClH425dyBEYnAc8VJv4R020WOQKf612dAAAAF0hioJgAACJLAAAZ+AAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAAAAAAMAAAAAAACNgAAAAABnWzwcAAAAAAAAAAMAAAAAAAAAAgAAAAMAAI2KAAAAAAAAAACPMpUG2Y35WQpR+NuXcgRGJwHPFSb+EdNtFjkCn+tdnQAAABdIYqCYAAAiSwAAGfgAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAAAAAADAAAAAAAAjYAAAAAAZ1s8HAAAAAAAAAABAACNigAAAAAAAAAAjzKVBtmN+VkKUfjbl3IERicBzxUm/hHTbRY5Ap/rXZ0AAAAXSGKgmAAAIksAABn5AAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAwAAAAAAAI2KAAAAAGdbPE4AAAAAAAAAAAAAAAAAAAAAcERufoNgDSa7wFkwjPY0LJia0337ZTeNzXHyuOhXwIoAAAAAAAAAyP////8AAAACAAAAAAAAAAH////7AAAAAAAAAAH////7AAAAAAAAAAIAAAADAACNiAAAAAAAAAAANRdWGvtDvnkIVhlmrF9bT/F50/CmwchjuRTC+41OZJYAAAAXSGYyqAAAIcQAABcjAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAwAAAAAAAI2IAAAAAGdbPEQAAAAAAAAAAQAAjYoAAAAAAAAAADUXVhr7Q755CFYZZqxfW0/xedPwpsHIY7kUwvuNTmSWAAAAF0hmMeAAACHEAAAXIwAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAAAAAAMAAAAAAACNiAAAAABnWzxEAAAAAAAAAAMAAAAAAAAAAgAAAAMAAI2KAAAAAAAAAAA1F1Ya+0O+eQhWGWasX1tP8XnT8KbByGO5FML7jU5klgAAABdIZjHgAAAhxAAAFyMAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAAAAAADAAAAAAAAjYgAAAAAZ1s8RAAAAAAAAAABAACNigAAAAAAAAAANRdWGvtDvnkIVhlmrF9bT/F50/CmwchjuRTC+41OZJYAAAAXSGYx4AAAIcQAABckAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAwAAAAAAAI2KAAAAAGdbPE4AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAANUF7AAAAAAAAAAA"
+      }
+    ],
+    "latestLedger": 36379,
+    "latestLedgerCloseTime": 1734033188,
+    "oldestLedger": 29312,
+    "oldestLedgerCloseTime": 1733997822,
+    "cursor": "36234"
+  }
+}
+```
+
+{/* /rpc-method */}
 
 ### Using the Lab
 
diff --git a/docs/data/apis/rpc/api-reference/methods/getNetwork.mdx b/docs/data/apis/rpc/api-reference/methods/getNetwork.mdx
index 6809d381c..9e531f758 100644
--- a/docs/data/apis/rpc/api-reference/methods/getNetwork.mdx
+++ b/docs/data/apis/rpc/api-reference/methods/getNetwork.mdx
@@ -1,14 +1,184 @@
 ---
-hide_title: true
+title: getNetwork
 description: Returns network config
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "getNetwork")[0]}
-/>
+General information about the currently configured network. This response will contain all the information needed to successfully submit transactions to the network this node serves.
+
+## Params (0)
+
+## Result
+
+_(getNetworkResult)_
+
+<ResponseField name="passphrase" type="string" required>
+
+Network passphrase configured for this Stellar RPC node.
+
+</ResponseField>
+
+<ResponseField name="protocolVersion" type="number" required>
+
+Stellar Core protocol version associated with the latest ledger.
+
+</ResponseField>
+
+<ResponseField name="friendbotUrl" type="string">
+
+(optional) The URL of this network's "friendbot" faucet
+
+</ResponseField>
+
+## Examples
+
+<Tabs>
+<Tab title="Testnet Network Configuration">
+
+Example request to the `getNetwork` method for a node connected to the Stellar Testnet network.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getNetwork"
+}' \
+https://soroban-testnet.stellar.org | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "getNetwork",
+};
+let res = await fetch("https://soroban-testnet.stellar.org", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://soroban-testnet.stellar.org", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "getNetwork"
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getNetwork"
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "friendbotUrl": "https://friendbot-testnet.stellar.org/",
+    "passphrase": "Test SDF Network ; September 2015",
+    "protocolVersion": 20
+  }
+}
+```
+
+</Tab>
+<Tab title="Futurenet Network Configuration">
+
+Example request to the `getNetwork` method for a node connected to the Stellar Futurenet network.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getNetwork"
+}' \
+https://soroban-testnet.stellar.org | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "getNetwork",
+};
+let res = await fetch("https://soroban-testnet.stellar.org", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://soroban-testnet.stellar.org", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "getNetwork"
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getNetwork"
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "friendbotUrl": "https://friendbot-futurenet.stellar.org/",
+    "passphrase": "Test SDF Future Network ; October 2022",
+    "protocolVersion": 20
+  }
+}
+```
+
+</Tab>
+</Tabs>
+
+{/* /rpc-method */}
 
 ### Using the Lab
 
diff --git a/docs/data/apis/rpc/api-reference/methods/getTransaction.mdx b/docs/data/apis/rpc/api-reference/methods/getTransaction.mdx
index 4693822ea..4924d15d8 100644
--- a/docs/data/apis/rpc/api-reference/methods/getTransaction.mdx
+++ b/docs/data/apis/rpc/api-reference/methods/getTransaction.mdx
@@ -1,22 +1,473 @@
 ---
-hide_title: true
+title: getTransaction
 description: Returns transaction details
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "getTransaction")[0]}
-/>
+The getTransaction method provides details about the specified transaction. Clients are expected to periodically query this method to ascertain when a transaction has been successfully recorded on the blockchain. The stellar-rpc system maintains a bounded history of recently processed transactions and events, configured by a single history-retention-window setting expressed in ledgers, with a stock default of 120960 ledgers (about 7 days, depending on ledger cadence). Operators of private stellar-rpc instances can adjust this value. The effective time span and the range of ledgers currently available can be inspected via the getHealth method (ledgerRetentionWindow, oldestLedger, latestLedger). For debugging needs that extend beyond the retained window, it is advisable to index this data yourself, employ a third-party [indexer](https://developers.stellar.org/docs/tools/developer-tools/data-indexers), or query [Hubble](https://developers.stellar.org/docs/data/hubble) (our public BigQuery data set).
+
+## Params (2)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="hash" type="string" required>
+
+Transaction hash to query as a hex-encoded string. This transaction hash should correspond to transaction that has been previously submitted to the network.
+
+Transaction hash (as a hex-encoded string)
+
+</ParamField>
+
+<ParamField body="xdrFormat" type="string">
+
+Lets the user choose the format in which the response should be returned - either as unpacked JSON or as base64-encoded XDR strings. Note that you should not rely on any schema for the JSON, as it will change when the underlying XDR changes.
+
+Specifies whether XDR should be encoded as Base64 (default or 'base64') or JSON ('json').
+
+</ParamField>
+
+## Result
+
+_(getTransactionResult)_
+
+<ResponseField name="status" type="string" required>
+
+The current status of the transaction by hash
+
+Available options: `SUCCESS`, `NOT_FOUND`, `FAILED`
+
+</ResponseField>
+
+<ResponseField name="txHash" type="string" required>
+
+The hex-encoded hash of the transaction.
+
+</ResponseField>
+
+<ResponseField name="latestLedger" type="number" required>
+
+The sequence number of the latest ledger known to Stellar RPC at the time it handled the request.
+
+</ResponseField>
+
+<ResponseField name="latestLedgerCloseTime" type="string" required>
+
+The unix timestamp (as a string) of the close time of the latest ledger known to Stellar RPC when it handled the request.
+
+</ResponseField>
+
+<ResponseField name="oldestLedger" type="number" required>
+
+The sequence number of the oldest ledger ingested by Stellar RPC at the time it handled the request.
+
+</ResponseField>
+
+<ResponseField name="oldestLedgerCloseTime" type="string" required>
+
+The unix timestamp (as a string) of the close time of the oldest ledger kept in history by Stellar RPC when it handled the request.
+
+</ResponseField>
+
+<ResponseField name="ledger" type="number">
+
+(optional) The sequence number of the ledger which included the transaction. This field is only present if `status` is `SUCCESS` or `FAILED`.
+
+</ResponseField>
+
+<ResponseField name="createdAt" type="string">
+
+(optional) The unix timestamp (as a string) of when the transaction was included in the ledger. This field is only present if `status` is `SUCCESS` or `FAILED`.
+
+</ResponseField>
+
+<ResponseField name="applicationOrder" type="number">
+
+(optional) The index of the transaction among all transactions included in the ledger. This field is only present if `status` is `SUCCESS` or `FAILED`.
+
+</ResponseField>
+
+<ResponseField name="feeBump" type="boolean">
+
+(optional) Indicates whether the transaction was fee bumped. This field is only present if `status` is `SUCCESS` or `FAILED`.
+
+</ResponseField>
+
+<ResponseField name="envelopeXdr" type="string">
+
+(optional) A base64 encoded string of the raw TransactionEnvelope XDR struct for this transaction.
+
+</ResponseField>
+
+<ResponseField name="resultXdr" type="string">
+
+(optional) A base64 encoded string of the raw TransactionResult XDR struct for this transaction. This field is only present if `status` is `SUCCESS` or `FAILED`.
+
+</ResponseField>
+
+<ResponseField name="resultMetaXdr" type="string">
+
+(optional) A base64 encoded string of the raw TransactionMeta XDR struct for this transaction.
+
+</ResponseField>
+
+<ResponseField name="diagnosticEventsXdr" type="string[]">
+
+(optional) A base64 encoded slice of xdr.DiagnosticEvent. This is only present if the `ENABLE_SOROBAN_DIAGNOSTIC_EVENTS` has been enabled on the RPC server.
+
+</ResponseField>
+
+<ResponseField name="events" type="object">
+
+Contains all events emitted during transaction execution.
+
+_Note: Available only on RPC v23.x (currently testnet only)._
+
+  <Expandable title="properties">
+    <ResponseField name="transactionEventsXdr" type="string[]">
+
+      An array of base64-encoded [xdr.TransactionEvent](https://github.com/stellar/stellar-xdr/blob/v23.0/Stellar-ledger.x#L503-L506). These include events such as fees being charged or refunded.
+
+    </ResponseField>
+    <ResponseField name="contractEventsXdr" type="string[][]">
+
+      A nested array of base64-encoded [xdr.ContractEvent](https://github.com/stellar/stellar-xdr/blob/v23.0/Stellar-ledger.x#L371-L390). Each inner array represents the contract events emitted by a single operation within the transaction.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+## Examples
+
+<Tabs>
+<Tab title="Successful Transaction">
+
+Query for a transaction hash that returns `SUCCESS` from the RPC node.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getTransaction",
+  "params": {
+    "hash": "32f7e5c3afd281fcaa99c0e990adf62f33e3bb341b1641a5c8b0b4a4dc55c487"
+  }
+}' \
+https://soroban-testnet.stellar.org | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "getTransaction",
+  params: {
+    hash: "32f7e5c3afd281fcaa99c0e990adf62f33e3bb341b1641a5c8b0b4a4dc55c487",
+  },
+};
+let res = await fetch("https://soroban-testnet.stellar.org", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://soroban-testnet.stellar.org", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "getTransaction",
+    "params": {
+        "hash": "32f7e5c3afd281fcaa99c0e990adf62f33e3bb341b1641a5c8b0b4a4dc55c487"
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getTransaction",
+  "params": {
+    "hash": "32f7e5c3afd281fcaa99c0e990adf62f33e3bb341b1641a5c8b0b4a4dc55c487"
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "latestLedger": 490314,
+    "latestLedgerCloseTime": "1752722132",
+    "oldestLedger": 369355,
+    "oldestLedgerCloseTime": "1752115873",
+    "status": "SUCCESS",
+    "txHash": "32f7e5c3afd281fcaa99c0e990adf62f33e3bb341b1641a5c8b0b4a4dc55c487",
+    "applicationOrder": 3,
+    "feeBump": false,
+    "envelopeXdr": "AAAAAgAAAADuBg+afmvWN9+nlruudR93UO1rDpTe8i6yxgPgBKoBVwExLQAAAA2lAAAfvQAAAAEAAAAAAAAAAAAAAABoeGmwAAAAAAAAAAEAAAABAAAAAO4GD5p+a9Y336eWu651H3dQ7WsOlN7yLrLGA+AEqgFXAAAAGAAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAJc2V0X3ByaWNlAAAAAAAAAgAAABAAAAABAAAACQAAAAoAAAAAAAAAAAAAaahaRp+AAAAACgAAAAAAAAAAAAB5y+SQiwAAAAAKAAAAAAAAAAAAAHFdMEkwAAAAAAoAAAAAAAAAAAAAQkvPyHAAAAAACgAAAAAAAAAAAAAE2U+ba4AAAAAKAAAAAAAAAAAAAAASetIWgAAAAAoAAAAAAAAAAAAAEFgo8D+AAAAACgAAAAAAAAAAAAACzFTXmwAAAAAKAAAAAAAAAAAEoxZECi8uAAAAAAUAAAGYFlw7QAAAAAEAAAAAAAAAAAAAAAGlJx5hXtZLUEEJA9akotOUWIv8dYiEoyuKQmACnKsp1gAAAAlzZXRfcHJpY2UAAAAAAAACAAAAEAAAAAEAAAAJAAAACgAAAAAAAAAAAABpqFpGn4AAAAAKAAAAAAAAAAAAAHnL5JCLAAAAAAoAAAAAAAAAAAAAcV0wSTAAAAAACgAAAAAAAAAAAABCS8/IcAAAAAAKAAAAAAAAAAAAAATZT5trgAAAAAoAAAAAAAAAAAAAABJ60haAAAAACgAAAAAAAAAAAAAQWCjwP4AAAAAKAAAAAAAAAAAAAALMVNebAAAAAAoAAAAAAAAAAASjFkQKLy4AAAAABQAAAZgWXDtAAAAAAAAAAAEAAAAAAAAAAQAAAAfaZ5h4OOy0NoTgqFsSMHHBZ2BWo+ttPZwC2FftqORNwwAAAAoAAAAGAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAACQAAAZgWXDtAAAAAAAAAAAAAAAAAAAAABgAAAAGlJx5hXtZLUEEJA9akotOUWIv8dYiEoyuKQmACnKsp1gAAAAkAAAGYFlw7QAAAAAAAAAABAAAAAAAAAAYAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAJAAABmBZcO0AAAAAAAAAAAgAAAAAAAAAGAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAACQAAAZgWXDtAAAAAAAAAAAMAAAAAAAAABgAAAAGlJx5hXtZLUEEJA9akotOUWIv8dYiEoyuKQmACnKsp1gAAAAkAAAGYFlw7QAAAAAAAAAAEAAAAAAAAAAYAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAJAAABmBZcO0AAAAAAAAAABQAAAAAAAAAGAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAACQAAAZgWXDtAAAAAAAAAAAYAAAAAAAAABgAAAAGlJx5hXtZLUEEJA9akotOUWIv8dYiEoyuKQmACnKsp1gAAAAkAAAGYFlw7QAAAAAAAAAAHAAAAAAAAAAYAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAJAAABmBZcO0AAAAAAAAAACAAAAAAAAAAGAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAAFAAAAAEAmJaAAACcQAAAC7gAAAAAAJiWgAAAAAHMpdlgAAAAQI1Wv1nG8+GPa2KOs99Rc3DPDYwypIPeKBa9Po4AN/VLSkjpqhIf2Tvli73MZYQlVmxsF2dROm2LPlgFPep8ZA0=",
+    "resultXdr": "AAAAAAAHNm8AAAAAAAAAAQAAAAAAAAAYAAAAABAjuTEVbQCbk5bRhjZsSNvqYe1R+oSFTzqCtsrEM/Z/AAAAAA==",
+    "resultMetaXdr": "AAAABAAAAAAAAAACAAAAAwAHewwAAAAAAAAAAO4GD5p+a9Y336eWu651H3dQ7WsOlN7yLrLGA+AEqgFXAAAAFmQIoCkAAA2lAAAfvAAAAAEAAAAAAAAAAAAAAAAAAQEBAAAAAQAAAAChM5sgwhIdyIwqcgCD9fwQBNYj/ox4Aw054hQxzKXZYAAAAAEAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAEAAAAAAAAAAwAAAAAAB3rQAAAAAGh4aHEAAAAAAAAAAQAHewwAAAAAAAAAAO4GD5p+a9Y336eWu651H3dQ7WsOlN7yLrLGA+AEqgFXAAAAFmQIoCkAAA2lAAAfvQAAAAEAAAAAAAAAAAAAAAAAAQEBAAAAAQAAAAChM5sgwhIdyIwqcgCD9fwQBNYj/ox4Aw054hQxzKXZYAAAAAEAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAEAAAAAAAAAAwAAAAAAB3sMAAAAAGh4aZ0AAAAAAAAAAQAAAAAAAAAUAAAAAAAHewwAAAAGAAAAAAAAAAGlJx5hXtZLUEEJA9akotOUWIv8dYiEoyuKQmACnKsp1gAAAAkAAAGYFlw7QAAAAAAAAAAHAAAAAAAAAAoAAAAAAAAAAAAAAsxU15sAAAAAAAAAAAMAB3rQAAAABgAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAUAAAAAQAAABMAAAAA2meYeDjstDaE4KhbEjBxwWdgVqPrbT2cAthX7ajkTcMAAAABAAAAEQAAAA4AAAAFYWRtaW4AAAAAAAASAAAAAAAAAADuBg+afmvWN9+nlruudR93UO1rDpTe8i6yxgPgBKoBVwAAAA4AAAAKYXNzZXRfdHRscwAAAAAAEAAAAAEAAAAAAAAADgAAAAZhc3NldHMAAAAAABAAAAABAAAACQAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA0VVUgAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANHQlAAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQ0hGAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA0NBRAAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANNWE4AAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQVJTAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA0JSTAAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANUSEIAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADWEFVAAAAAA4AAAAKYmFzZV9hc3NldAAAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADVVNEAAAAAA4AAAAIZGVjaW1hbHMAAAADAAAADgAAAA4AAAAObGFzdF90aW1lc3RhbXAAAAAAAAUAAAGYFlenYAAAAA4AAAAGcGVyaW9kAAAAAAAFAAAAAAUmXAAAAAAOAAAACnJlc29sdXRpb24AAAAAAAMABJPgAAAADwAAAANBUlMAAAAAAwAAAAUAAAAPAAAAA0JSTAAAAAADAAAABgAAAA8AAAADQ0FEAAAAAAMAAAADAAAADwAAAANDSEYAAAAAAwAAAAIAAAAPAAAAA0VVUgAAAAADAAAAAAAAAA8AAAADR0JQAAAAAAMAAAABAAAADwAAAANNWE4AAAAAAwAAAAQAAAAPAAAAA1RIQgAAAAADAAAABwAAAA8AAAADWEFVAAAAAAMAAAAIAAAAAAAAAAEAB3sMAAAABgAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAUAAAAAQAAABMAAAAA2meYeDjstDaE4KhbEjBxwWdgVqPrbT2cAthX7ajkTcMAAAABAAAAEQAAAA4AAAAFYWRtaW4AAAAAAAASAAAAAAAAAADuBg+afmvWN9+nlruudR93UO1rDpTe8i6yxgPgBKoBVwAAAA4AAAAKYXNzZXRfdHRscwAAAAAAEAAAAAEAAAAAAAAADgAAAAZhc3NldHMAAAAAABAAAAABAAAACQAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA0VVUgAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANHQlAAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQ0hGAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA0NBRAAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANNWE4AAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQVJTAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA0JSTAAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANUSEIAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADWEFVAAAAAA4AAAAKYmFzZV9hc3NldAAAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADVVNEAAAAAA4AAAAIZGVjaW1hbHMAAAADAAAADgAAAA4AAAAObGFzdF90aW1lc3RhbXAAAAAAAAUAAAGYFlw7QAAAAA4AAAAGcGVyaW9kAAAAAAAFAAAAAAUmXAAAAAAOAAAACnJlc29sdXRpb24AAAAAAAMABJPgAAAADwAAAANBUlMAAAAAAwAAAAUAAAAPAAAAA0JSTAAAAAADAAAABgAAAA8AAAADQ0FEAAAAAAMAAAADAAAADwAAAANDSEYAAAAAAwAAAAIAAAAPAAAAA0VVUgAAAAADAAAAAAAAAA8AAAADR0JQAAAAAAMAAAABAAAADwAAAANNWE4AAAAAAwAAAAQAAAAPAAAAA1RIQgAAAAADAAAABwAAAA8AAAADWEFVAAAAAAMAAAAIAAAAAAAAAAAAB3sMAAAACWo/Q7+BqCohmd66fbeHqmOxwDrEajSJjntv7Y5sPFwKAAe+jQAAAAAAAAAAAAd7DAAAAAYAAAAAAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAACQAAAZgWXDtAAAAAAAAAAAYAAAAAAAAACgAAAAAAAAAAAAAQWCjwP4AAAAAAAAAAAAAHewwAAAAJDd+QVt7czhZ+1iOlJIEkfbQdjJY4vh2VW1NnYDEO0KIAB76NAAAAAAAAAAAAB3sMAAAABgAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAJAAABmBZcO0AAAAAAAAAAAwAAAAAAAAAKAAAAAAAAAAAAAEJLz8hwAAAAAAAAAAAAAAd7DAAAAAYAAAAAAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAACQAAAZgWXDtAAAAAAAAAAAgAAAAAAAAACgAAAAAAAAAABKMWRAovLgAAAAAAAAAAAAAHewwAAAAJYFSRWz1ud4KbBeH4wR+BTo2nujxr+OyRL34qDqLWGLgAB76NAAAAAAAAAAAAB3sMAAAACU9zyBAititNTWuzCCUxysgsXo1Y4uJR2bdxcEkKBfFXAAe+jQAAAAAAAAAAAAd7DAAAAAYAAAAAAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAACQAAAZgWXDtAAAAAAAAAAAIAAAAAAAAACgAAAAAAAAAAAABxXTBJMAAAAAAAAAAAAAAHewwAAAAJRwyMg2H3RfsefjQh4634iFhhyOEn/xxvjKDH2TMMscYAB76NAAAAAAAAAAAAB3sMAAAACSkT7lXMRBq1CY5zzXh7sK8kSPChtPHGlSwjz1Ukcv/pAAe+jQAAAAAAAAAAAAd7DAAAAAk8YixNDWhOoPg/9YvOd1q+OhmmPU206DKv5lP5MEuBlAAHvo0AAAAAAAAAAAAHewwAAAAGAAAAAAAAAAGlJx5hXtZLUEEJA9akotOUWIv8dYiEoyuKQmACnKsp1gAAAAkAAAGYFlw7QAAAAAAAAAAEAAAAAAAAAAoAAAAAAAAAAAAABNlPm2uAAAAAAAAAAAAAB3sMAAAACYx+BN6DguHmDcMmldaDVjShQeV0DhIVxf6o1Y+QlzQUAAe+jQAAAAAAAAAAAAd7DAAAAAYAAAAAAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAACQAAAZgWXDtAAAAAAAAAAAEAAAAAAAAACgAAAAAAAAAAAAB5y+SQiwAAAAAAAAAAAAAHewwAAAAGAAAAAAAAAAGlJx5hXtZLUEEJA9akotOUWIv8dYiEoyuKQmACnKsp1gAAAAkAAAGYFlw7QAAAAAAAAAAAAAAAAAAAAAoAAAAAAAAAAAAAaahaRp+AAAAAAAAAAAAAB3sMAAAABgAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAJAAABmBZcO0AAAAAAAAAABQAAAAAAAAAKAAAAAAAAAAAAAAASetIWgAAAAAAAAAAAAAd7DAAAAAkbTRN7zotklphc0r0JzXhgFTarHGmwoYH5aZVMPqWtlgAHvo0AAAAAAAAAAQAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAABAAAAAAAAAAMAAAAPAAAACXJlZmxlY3RvcgAAAAAAAA8AAAAGcHJpY2VzAAAAAAAPAAAABnVwZGF0ZQAAAAAAEAAAAAEAAAAJAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRVVSAAAAAAoAAAAAAAAAAAAAaahaRp+AAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADR0JQAAAAAAoAAAAAAAAAAAAAecvkkIsAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQ0hGAAAAAAoAAAAAAAAAAAAAcV0wSTAAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQ0FEAAAAAAoAAAAAAAAAAAAAQkvPyHAAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADTVhOAAAAAAoAAAAAAAAAAAAABNlPm2uAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQVJTAAAAAAoAAAAAAAAAAAAAABJ60haAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQlJMAAAAAAoAAAAAAAAAAAAAEFgo8D+AAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADVEhCAAAAAAoAAAAAAAAAAAAAAsxU15sAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADWEFVAAAAAAoAAAAAAAAAAASjFkQKLy4AAAAAAgAAAAMAB3sMAAAAAAAAAADuBg+afmvWN9+nlruudR93UO1rDpTe8i6yxgPgBKoBVwAAABZkCKApAAANpQAAH70AAAABAAAAAAAAAAAAAAAAAAEBAQAAAAEAAAAAoTObIMISHciMKnIAg/X8EATWI/6MeAMNOeIUMcyl2WAAAAABAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAAAAAABAAAAAAAAAAMAAAAAAAd7DAAAAABoeGmdAAAAAAAAAAEAB3sMAAAAAAAAAADuBg+afmvWN9+nlruudR93UO1rDpTe8i6yxgPgBKoBVwAAABZkmgCeAAANpQAAH70AAAABAAAAAAAAAAAAAAAAAAEBAQAAAAEAAAAAoTObIMISHciMKnIAg/X8EATWI/6MeAMNOeIUMcyl2WAAAAABAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAAAAAABAAAAAAAAAAMAAAAAAAd7DAAAAABoeGmdAAAAAAAAAAEAAAABAAAAAAAAAAAABQMAAAAAAAACMwsAAAAAAAIVvwAAAAEAAAABAAAAAgAAAAAAAAAAAAAAAdeSi3LCcDzP6vfrn/TvTVBKVai5efybRQ6iyEK00c5hAAAAAQAAAAAAAAACAAAADwAAAANmZWUAAAAAEgAAAAAAAAAA7gYPmn5r1jffp5a7rnUfd1Dtaw6U3vIussYD4ASqAVcAAAAKAAAAAAAAAAAAAAAAAJiW5AAAAAEAAAAAAAAAAdeSi3LCcDzP6vfrn/TvTVBKVai5efybRQ6iyEK00c5hAAAAAQAAAAAAAAACAAAADwAAAANmZWUAAAAAEgAAAAAAAAAA7gYPmn5r1jffp5a7rnUfd1Dtaw6U3vIussYD4ASqAVcAAAAK/////////////////26fiwAAABYAAAABAAAAAAAAAAAAAAACAAAAAAAAAAMAAAAPAAAAB2ZuX2NhbGwAAAAADQAAACClJx5hXtZLUEEJA9akotOUWIv8dYiEoyuKQmACnKsp1gAAAA8AAAAJc2V0X3ByaWNlAAAAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAAJAAAACgAAAAAAAAAAAABpqFpGn4AAAAAKAAAAAAAAAAAAAHnL5JCLAAAAAAoAAAAAAAAAAAAAcV0wSTAAAAAACgAAAAAAAAAAAABCS8/IcAAAAAAKAAAAAAAAAAAAAATZT5trgAAAAAoAAAAAAAAAAAAAABJ60haAAAAACgAAAAAAAAAAAAAQWCjwP4AAAAAKAAAAAAAAAAAAAALMVNebAAAAAAoAAAAAAAAAAASjFkQKLy4AAAAABQAAAZgWXDtAAAAAAQAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAABAAAAAAAAAAMAAAAPAAAACXJlZmxlY3RvcgAAAAAAAA8AAAAGcHJpY2VzAAAAAAAPAAAABnVwZGF0ZQAAAAAAEAAAAAEAAAAJAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRVVSAAAAAAoAAAAAAAAAAAAAaahaRp+AAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADR0JQAAAAAAoAAAAAAAAAAAAAecvkkIsAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQ0hGAAAAAAoAAAAAAAAAAAAAcV0wSTAAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQ0FEAAAAAAoAAAAAAAAAAAAAQkvPyHAAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADTVhOAAAAAAoAAAAAAAAAAAAABNlPm2uAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQVJTAAAAAAoAAAAAAAAAAAAAABJ60haAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQlJMAAAAAAoAAAAAAAAAAAAAEFgo8D+AAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADVEhCAAAAAAoAAAAAAAAAAAAAAsxU15sAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADWEFVAAAAAAoAAAAAAAAAAASjFkQKLy4AAAAAAQAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAACAAAAAAAAAAIAAAAPAAAACWZuX3JldHVybgAAAAAAAA8AAAAJc2V0X3ByaWNlAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAAApyZWFkX2VudHJ5AAAAAAAFAAAAAAAAAAsAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAALd3JpdGVfZW50cnkAAAAABQAAAAAAAAAKAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEGxlZGdlcl9yZWFkX2J5dGUAAAAFAAAAAAAAVzQAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAARbGVkZ2VyX3dyaXRlX2J5dGUAAAAAAAAFAAAAAAAABxAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAANcmVhZF9rZXlfYnl0ZQAAAAAAAAUAAAAAAAAClAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAAA53cml0ZV9rZXlfYnl0ZQAAAAAABQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADnJlYWRfZGF0YV9ieXRlAAAAAAAFAAAAAAAAA7AAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAPd3JpdGVfZGF0YV9ieXRlAAAAAAUAAAAAAAAHEAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAAA5yZWFkX2NvZGVfYnl0ZQAAAAAABQAAAAAAAFOEAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD3dyaXRlX2NvZGVfYnl0ZQAAAAAFAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAKZW1pdF9ldmVudAAAAAAABQAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD2VtaXRfZXZlbnRfYnl0ZQAAAAAFAAAAAAAAAvwAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAIY3B1X2luc24AAAAFAAAAAABImEoAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAIbWVtX2J5dGUAAAAFAAAAAAAhGTIAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAARaW52b2tlX3RpbWVfbnNlY3MAAAAAAAAFAAAAAAAW1jEAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAPbWF4X3J3X2tleV9ieXRlAAAAAAUAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAABBtYXhfcndfZGF0YV9ieXRlAAAABQAAAAAAAAOwAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEG1heF9yd19jb2RlX2J5dGUAAAAFAAAAAAAAU4QAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAATbWF4X2VtaXRfZXZlbnRfYnl0ZQAAAAAFAAAAAAAAAvw=",
+    "diagnosticEventsXdr": [
+      "AAAAAQAAAAAAAAAAAAAAAgAAAAAAAAADAAAADwAAAAdmbl9jYWxsAAAAAA0AAAAgpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAPAAAACXNldF9wcmljZQAAAAAAABAAAAABAAAAAgAAABAAAAABAAAACQAAAAoAAAAAAAAAAAAAaahaRp+AAAAACgAAAAAAAAAAAAB5y+SQiwAAAAAKAAAAAAAAAAAAAHFdMEkwAAAAAAoAAAAAAAAAAAAAQkvPyHAAAAAACgAAAAAAAAAAAAAE2U+ba4AAAAAKAAAAAAAAAAAAAAASetIWgAAAAAoAAAAAAAAAAAAAEFgo8D+AAAAACgAAAAAAAAAAAAACzFTXmwAAAAAKAAAAAAAAAAAEoxZECi8uAAAAAAUAAAGYFlw7QA==",
+      "AAAAAQAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAABAAAAAAAAAAMAAAAPAAAACXJlZmxlY3RvcgAAAAAAAA8AAAAGcHJpY2VzAAAAAAAPAAAABnVwZGF0ZQAAAAAAEAAAAAEAAAAJAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRVVSAAAAAAoAAAAAAAAAAAAAaahaRp+AAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADR0JQAAAAAAoAAAAAAAAAAAAAecvkkIsAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQ0hGAAAAAAoAAAAAAAAAAAAAcV0wSTAAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQ0FEAAAAAAoAAAAAAAAAAAAAQkvPyHAAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADTVhOAAAAAAoAAAAAAAAAAAAABNlPm2uAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQVJTAAAAAAoAAAAAAAAAAAAAABJ60haAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQlJMAAAAAAoAAAAAAAAAAAAAEFgo8D+AAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADVEhCAAAAAAoAAAAAAAAAAAAAAsxU15sAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADWEFVAAAAAAoAAAAAAAAAAASjFkQKLy4A",
+      "AAAAAQAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAACAAAAAAAAAAIAAAAPAAAACWZuX3JldHVybgAAAAAAAA8AAAAJc2V0X3ByaWNlAAAAAAAAAQ==",
+      "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACnJlYWRfZW50cnkAAAAAAAUAAAAAAAAACw==",
+      "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAC3dyaXRlX2VudHJ5AAAAAAUAAAAAAAAACg==",
+      "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEGxlZGdlcl9yZWFkX2J5dGUAAAAFAAAAAAAAVzQ=",
+      "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEWxlZGdlcl93cml0ZV9ieXRlAAAAAAAABQAAAAAAAAcQ",
+      "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADXJlYWRfa2V5X2J5dGUAAAAAAAAFAAAAAAAAApQ=",
+      "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADndyaXRlX2tleV9ieXRlAAAAAAAFAAAAAAAAAAA=",
+      "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADnJlYWRfZGF0YV9ieXRlAAAAAAAFAAAAAAAAA7A=",
+      "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD3dyaXRlX2RhdGFfYnl0ZQAAAAAFAAAAAAAABxA=",
+      "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADnJlYWRfY29kZV9ieXRlAAAAAAAFAAAAAAAAU4Q=",
+      "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD3dyaXRlX2NvZGVfYnl0ZQAAAAAFAAAAAAAAAAA=",
+      "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACmVtaXRfZXZlbnQAAAAAAAUAAAAAAAAAAQ==",
+      "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD2VtaXRfZXZlbnRfYnl0ZQAAAAAFAAAAAAAAAvw=",
+      "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACGNwdV9pbnNuAAAABQAAAAAASJhK",
+      "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACG1lbV9ieXRlAAAABQAAAAAAIRky",
+      "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEWludm9rZV90aW1lX25zZWNzAAAAAAAABQAAAAAAFtYx",
+      "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD21heF9yd19rZXlfYnl0ZQAAAAAFAAAAAAAAAEA=",
+      "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEG1heF9yd19kYXRhX2J5dGUAAAAFAAAAAAAAA7A=",
+      "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEG1heF9yd19jb2RlX2J5dGUAAAAFAAAAAAAAU4Q=",
+      "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAE21heF9lbWl0X2V2ZW50X2J5dGUAAAAABQAAAAAAAAL8"
+    ],
+    "events": {
+      "transactionEventsXdr": [
+        "AAAAAAAAAAAAAAAB15KLcsJwPM/q9+uf9O9NUEpVqLl5/JtFDqLIQrTRzmEAAAABAAAAAAAAAAIAAAAPAAAAA2ZlZQAAAAASAAAAAAAAAADuBg+afmvWN9+nlruudR93UO1rDpTe8i6yxgPgBKoBVwAAAAoAAAAAAAAAAAAAAAAAmJbk",
+        "AAAAAQAAAAAAAAAB15KLcsJwPM/q9+uf9O9NUEpVqLl5/JtFDqLIQrTRzmEAAAABAAAAAAAAAAIAAAAPAAAAA2ZlZQAAAAASAAAAAAAAAADuBg+afmvWN9+nlruudR93UO1rDpTe8i6yxgPgBKoBVwAAAAr/////////////////bp+L"
+      ],
+      "contractEventsXdr": [
+        [
+          "AAAAAAAAAAGlJx5hXtZLUEEJA9akotOUWIv8dYiEoyuKQmACnKsp1gAAAAEAAAAAAAAAAwAAAA8AAAAJcmVmbGVjdG9yAAAAAAAADwAAAAZwcmljZXMAAAAAAA8AAAAGdXBkYXRlAAAAAAAQAAAAAQAAAAkAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANFVVIAAAAACgAAAAAAAAAAAABpqFpGn4AAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANHQlAAAAAACgAAAAAAAAAAAAB5y+SQiwAAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANDSEYAAAAACgAAAAAAAAAAAABxXTBJMAAAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANDQUQAAAAACgAAAAAAAAAAAABCS8/IcAAAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANNWE4AAAAACgAAAAAAAAAAAAAE2U+ba4AAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANBUlMAAAAACgAAAAAAAAAAAAAAEnrSFoAAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANCUkwAAAAACgAAAAAAAAAAAAAQWCjwP4AAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANUSEIAAAAACgAAAAAAAAAAAAACzFTXmwAAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANYQVUAAAAACgAAAAAAAAAABKMWRAovLgA="
+        ]
+      ]
+    },
+    "ledger": 490252,
+    "createdAt": "1752721821"
+  }
+}
+```
+
+</Tab>
+<Tab title="Not Found Transaction">
+
+Query for a transaction hash that returns `NOT_FOUND` from the RPC node.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getTransaction",
+  "params": {
+    "hash": "85f7aa8bfda425b98c0e53ffe56796ffd8865ec2fcc3ad71abf120801e2a14e5"
+  }
+}' \
+https://soroban-testnet.stellar.org | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "getTransaction",
+  params: {
+    hash: "85f7aa8bfda425b98c0e53ffe56796ffd8865ec2fcc3ad71abf120801e2a14e5",
+  },
+};
+let res = await fetch("https://soroban-testnet.stellar.org", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://soroban-testnet.stellar.org", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "getTransaction",
+    "params": {
+        "hash": "85f7aa8bfda425b98c0e53ffe56796ffd8865ec2fcc3ad71abf120801e2a14e5"
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getTransaction",
+  "params": {
+    "hash": "85f7aa8bfda425b98c0e53ffe56796ffd8865ec2fcc3ad71abf120801e2a14e5"
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "status": "NOT_FOUND",
+    "txHash": "85f7aa8bfda425b98c0e53ffe56796ffd8865ec2fcc3ad71abf120801e2a14e5",
+    "latestLedger": 2540099,
+    "latestLedgerCloseTime": "1700086455",
+    "oldestLedger": 2538660,
+    "oldestLedgerCloseTime": "1700078913"
+  }
+}
+```
+
+</Tab>
+<Tab title="Failed Transaction">
+
+Query for a transaction hash that returns `FAILED` from the RPC node.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getTransaction",
+  "params": {
+    "hash": "109cf6170666e15470fb622df4965051ecfea2fee97d8165d072a769ba098b54"
+  }
+}' \
+https://soroban-testnet.stellar.org | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "getTransaction",
+  params: {
+    hash: "109cf6170666e15470fb622df4965051ecfea2fee97d8165d072a769ba098b54",
+  },
+};
+let res = await fetch("https://soroban-testnet.stellar.org", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://soroban-testnet.stellar.org", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "getTransaction",
+    "params": {
+        "hash": "109cf6170666e15470fb622df4965051ecfea2fee97d8165d072a769ba098b54"
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getTransaction",
+  "params": {
+    "hash": "109cf6170666e15470fb622df4965051ecfea2fee97d8165d072a769ba098b54"
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "latestLedger": 337311,
+    "latestLedgerCloseTime": "1751955519",
+    "oldestLedger": 337151,
+    "oldestLedgerCloseTime": "1751954719",
+    "status": "FAILED",
+    "txHash": "109cf6170666e15470fb622df4965051ecfea2fee97d8165d072a769ba098b54",
+    "applicationOrder": 1,
+    "feeBump": false,
+    "envelopeXdr": "AAAAAgAAAACPMpUG2Y35WQpR+NuXcgRGJwHPFSb+EdNtFjkCn+tdnQAAAGQAACVsAAAUvQAAAAEAAAAAAAAAAAAAAABobLYnAAAAAQAAAAdwc3A6MTIzAAAAAAEAAAABAAAAALyBL9daiYtaADzcZA8i3U28u/d5KV2Cu3cJTM1hY1NAAAAAAQAAAABiRvI6ZCsMe8e9H61jp3rdooHANhGow7zCN0hK0ncDTgAAAAJBVFVTRAAAAAAAAAAAAAAAZ8rWY3iaDnWNtfpvLpNaCEbKdDjrd2gQODOuKpmj1vMAAAAAALuu4AAAAAAAAAACn+tdnQAAAEDVTl0j8Hsq+XadkzDg6mu9mWjxorxcMThlsvwJTgNTTZmWhbZrUP3btXqQInLTsz39yTgXJRCudxh5c7K235IBYWNTQAAAAEAbI2IDD4atBlqwvn1fH5x3/agOr3ihF/VOSIdZJipgC+mXIYhD/mZxqlQk5QQC5jHAUYm0YWB7Z/sNuw71qVkC",
+    "resultXdr": "AAAAAAAAAGT/////AAAAAQAAAAAAAAAB////+wAAAAA=",
+    "resultMetaXdr": "AAAABAAAAAAAAAACAAAAAwAFJSgAAAAAAAAAAI8ylQbZjflZClH425dyBEYnAc8VJv4R020WOQKf612dAAAAF0Z0IZQAACVsAAAUvAAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAAAAAAMAAAAAAAUk7gAAAABobLTKAAAAAAAAAAEABSUoAAAAAAAAAACPMpUG2Y35WQpR+NuXcgRGJwHPFSb+EdNtFjkCn+tdnQAAABdGdCGUAAAlbAAAFL0AAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAAAAAADAAAAAAAFJSgAAAAAaGy17AAAAAAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAAB15KLcsJwPM/q9+uf9O9NUEpVqLl5/JtFDqLIQrTRzmEAAAABAAAAAAAAAAIAAAAPAAAAA2ZlZQAAAAASAAAAAAAAAACPMpUG2Y35WQpR+NuXcgRGJwHPFSb+EdNtFjkCn+tdnQAAAAoAAAAAAAAAAAAAAAAAAABkAAAAAA==",
+    "events": {
+      "transactionEventsXdr": [
+        "AAAAAAAAAAAAAAAB15KLcsJwPM/q9+uf9O9NUEpVqLl5/JtFDqLIQrTRzmEAAAABAAAAAAAAAAIAAAAPAAAAA2ZlZQAAAAASAAAAAAAAAACPMpUG2Y35WQpR+NuXcgRGJwHPFSb+EdNtFjkCn+tdnQAAAAoAAAAAAAAAAAAAAAAAAABk"
+      ]
+    },
+    "ledger": 337192,
+    "createdAt": "1751954924"
+  }
+}
+```
+
+</Tab>
+</Tabs>
+
+{/* /rpc-method */}
 
 ### SDK Guide
 
 The example above is querying details of a transaction using RPC methods directly. If you are using the Stellar SDK to build applications, you can use the native functions to get the same information.
 
-<CodeExample>
+<CodeGroup>
 
-```python
+```python Python
 # pip install --upgrade stellar-sdk
 from stellar_sdk import SorobanServer, soroban_rpc
 
@@ -31,7 +482,7 @@ tx = get_transaction("6bc97bddc21811c626839baf4ab574f4f9f7ddbebb44d286ae504396d4
 print("result", tx.status)
 ```
 
-```js
+```js JavaScript
 // yarn add @stellar/stellar-sdk
 import { Server } from "@stellar/stellar-sdk/rpc";
 
@@ -53,7 +504,7 @@ getTransactionDetails(
 );
 ```
 
-```java
+```java Java
 // implementation 'network.lightsail:stellar-sdk:3.1.0'
 
 import org.stellar.sdk.SorobanServer;
@@ -73,13 +524,13 @@ public class GetTransactionExample {
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Using the Lab
 
 You can use the `getTransaction` method in the [Stellar Laboratory](https://laboratory.stellar.org) to **retrieve details about a specific transaction**. This is especially useful for checking the status of a transaction to determine whether it has been successfully recorded on the blockchain.
 
-`stellar-rpc` retains a bounded, ledger-denominated history of recent transactions and events, configured by a single `history-retention-window` setting. The stock default is **120960 ledgers** (about **7 days**, depending on ledger cadence), and operators of private instances can adjust it. You can inspect the active window and the range of ledgers available on an instance with the [`getHealth`](./getHealth.mdx) method (`ledgerRetentionWindow`, `oldestLedger`, `latestLedger`). For transaction debugging beyond the retained window, consider indexing the data yourself, using a third-party indexer, or querying **Hubble**—Stellar’s public BigQuery dataset.
+`stellar-rpc` retains a bounded, ledger-denominated history of recent transactions and events, configured by a single `history-retention-window` setting. The stock default is **120960 ledgers** (about **7 days**, depending on ledger cadence), and operators of private instances can adjust it. You can inspect the active window and the range of ledgers available on an instance with the [`getHealth`](./getHealth) method (`ledgerRetentionWindow`, `oldestLedger`, `latestLedger`). For transaction debugging beyond the retained window, consider indexing the data yourself, using a third-party indexer, or querying **Hubble**—Stellar’s public BigQuery dataset.
 
 👉 [View getTransaction on the Lab](https://lab.stellar.org/endpoints/rpc/get-transaction?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;;)
 
diff --git a/docs/data/apis/rpc/api-reference/methods/getTransactions.mdx b/docs/data/apis/rpc/api-reference/methods/getTransactions.mdx
index 474e24716..cd5ef24b5 100644
--- a/docs/data/apis/rpc/api-reference/methods/getTransactions.mdx
+++ b/docs/data/apis/rpc/api-reference/methods/getTransactions.mdx
@@ -1,14 +1,718 @@
 ---
-hide_title: true
+title: getTransactions
 description: Returns list of transactions
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "getTransactions")[0]}
-/>
+The `getTransactions` method return a detailed list of transactions starting from the user specified starting point that you can paginate as long as the pages fall within the history retention of their corresponding RPC provider.
+
+## Params (3)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="startLedger" type="number">
+
+Ledger sequence number to start fetching responses from (inclusive). This method will return an error if `startLedger` is less than the oldest ledger stored in this node, or greater than the latest ledger seen by this node. If a cursor is included in the request, `startLedger` must be omitted.
+
+Sequence number of the ledger.
+
+</ParamField>
+
+<ParamField body="pagination" type="object">
+
+Pagination in stellar-rpc is similar to pagination in Horizon. See [Pagination](https://developers.stellar.org/docs/data/rpc/api-reference/structure/pagination).
+
+  <Expandable title="properties">
+    <ParamField body="cursor" type="string">
+
+      An opaque string which acts as a paging token. To obtain the next page of results occurring after a given response set this value to the `cursor` field of the response.
+
+    </ParamField>
+    <ParamField body="limit" type="number">
+
+      The maximum number of records returned. The limit for getTransactions can range from 1 to 200 - an upper limit that is hardcoded in Stellar-RPC for performance reasons. If this argument isn't designated, it defaults to 50.
+
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+<ParamField body="xdrFormat" type="string">
+
+Lets the user choose the format in which the response should be returned - either as unpacked JSON or as base64-encoded XDR strings. Note that you should not rely on any schema for the JSON, as it will change when the underlying XDR changes.
+
+Specifies whether XDR should be encoded as Base64 (default or 'base64') or JSON ('json').
+
+</ParamField>
+
+## Result
+
+_(getTransactionsResult)_
+
+<ResponseField name="transactions" type="object[]">
+  <Expandable title="items">
+    <ResponseField name="status" type="string">
+
+      Indicates whether the transaction was successful or not.
+
+    </ResponseField>
+    <ResponseField name="txHash" type="string">
+
+      The hex-encoded hash of the transaction.
+
+    </ResponseField>
+    <ResponseField name="applicationOrder" type="number">
+
+      The 1-based index of the transaction among all transactions included in the ledger.
+
+    </ResponseField>
+    <ResponseField name="feeBump" type="boolean">
+
+      Indicates whether the transaction was fee bumped.
+
+    </ResponseField>
+    <ResponseField name="envelopeXdr" type="string">
+
+      The [TransactionEnvelope](https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-transaction.x#L1009) structure for this transaction (base64-encoded string).
+
+    </ResponseField>
+    <ResponseField name="resultXdr" type="string">
+
+      The [TransactionResult](https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-transaction.x#L2088) structure for this transaction (base64-encoded string).
+
+    </ResponseField>
+    <ResponseField name="resultMetaXdr" type="string">
+
+      The [TransactionResultMeta](L446https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-ledger.x#L461) structure for this transaction (base64-encoded string).
+
+    </ResponseField>
+    <ResponseField name="diagnosticEventsXdr" type="string[]">
+
+      (optional) A base64 encoded slice of xdr.DiagnosticEvent. This is only present if the `ENABLE_SOROBAN_DIAGNOSTIC_EVENTS` has been enabled on the RPC server.
+
+    </ResponseField>
+    <ResponseField name="events" type="object">
+
+      Contains all events emitted during transaction execution.
+
+      _Note: Available only on RPC v23.x (currently testnet only)._
+
+      <Expandable title="properties">
+        <ResponseField name="transactionEventsXdr" type="string[]">
+
+          An array of base64-encoded [xdr.TransactionEvent](https://github.com/stellar/stellar-xdr/blob/v23.0/Stellar-ledger.x#L503-L506). These include events such as fees being charged or refunded.
+
+        </ResponseField>
+        <ResponseField name="contractEventsXdr" type="string[][]">
+
+          A nested array of base64-encoded [xdr.ContractEvent](https://github.com/stellar/stellar-xdr/blob/v23.0/Stellar-ledger.x#L371-L390). Each inner array represents the contract events emitted by a single operation within the transaction.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="ledger" type="number">
+
+      The sequence number of the ledger which included the transaction.
+
+    </ResponseField>
+    <ResponseField name="createdAt" type="number">
+
+      The unix timestamp of when the transaction was included in the ledger.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="latestLedger" type="number">
+
+The sequence number of the latest ledger known to Stellar RPC at the time it handled the request.
+
+</ResponseField>
+
+<ResponseField name="latestLedgerCloseTimestamp" type="number">
+
+The unix timestamp of the close time of the latest ledger known to Stellar RPC at the time it handled the request.
+
+</ResponseField>
+
+<ResponseField name="oldestLedger" type="number">
+
+The sequence number of the oldest ledger ingested by Stellar RPC at the time it handled the request.
+
+</ResponseField>
+
+<ResponseField name="oldestLedgerCloseTimestamp" type="number">
+
+The unix timestamp of the close time of the oldest ledger ingested by Stellar RPC at the time it handled the request.
+
+</ResponseField>
+
+<ResponseField name="cursor" type="string">
+
+A token which can be included in a subsequent request to obtain the next page of results.
+
+</ResponseField>
+
+## Examples
+
+<Tabs>
+<Tab title="Successful getTransactions Request">
+
+Query a list of transactions starting from the given startLedger.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getTransactions",
+  "params": {
+    "startLedger": 337272,
+    "pagination": {
+      "limit": 5
+    }
+  }
+}' \
+https://soroban-testnet.stellar.org | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "getTransactions",
+  params: {
+    startLedger: 337272,
+    pagination: {
+      limit: 5,
+    },
+  },
+};
+let res = await fetch("https://soroban-testnet.stellar.org", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://soroban-testnet.stellar.org", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "getTransactions",
+    "params": {
+        "startLedger": 337272,
+        "pagination": {
+            "limit": 5
+        }
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getTransactions",
+  "params": {
+    "startLedger": 337272,
+    "pagination": {
+      "limit": 5
+    }
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "transactions": [
+      {
+        "status": "FAILED",
+        "txHash": "173d6022f8db9654f31c5aa53785385b913ed32baf8ee72f984b97a97bb0909b",
+        "applicationOrder": 1,
+        "feeBump": true,
+        "envelopeXdr": "AAAABQAAAAADKm0xr8jnLz7gKYk/CQg7DF6nkVnJNErPGZcXNDs4RwAAAAAB2j5AAAAAAgAAAAC/JkamGjlv1kc1tD/C4dJaB6vxgIfnQRZNEIndZH9mjAAAAAAAAEXVAAACNgAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAYAAAABAAAAAAMqbTGvyOcvPuApiT8JCDsMXqeRWck0Ss8Zlxc0OzhHAAAAEAAAAACWzQF4RyG733Ul+cJlgJ6N6SBHVKLGfBpdDzTLMleEBQAAAAEAAAAAAyptMa/I5y8+4CmJPwkIOwxep5FZyTRKzxmXFzQ7OEcAAAAAAAAAAJbNAXhHIbvfdSX5wmWAno3pIEdUosZ8Gl0PNMsyV4QFAAAAAAAAAAAAAAABAAAAAJbNAXhHIbvfdSX5wmWAno3pIEdUosZ8Gl0PNMsyV4QFAAAABgAAAAFVU0RDAAAAAEI+fQXy7K+/7BkrIVo/G+lq7bjY5wJUq+NBPgIH3layf/////////8AAAABAAAAAJbNAXhHIbvfdSX5wmWAno3pIEdUosZ8Gl0PNMsyV4QFAAAAEQAAAAEAAAAAAyptMa/I5y8+4CmJPwkIOwxep5FZyTRKzxmXFzQ7OEcAAAABAAAAAJbNAXhHIbvfdSX5wmWAno3pIEdUosZ8Gl0PNMsyV4QFAAAAAVVTREMAAAAAQj59BfLsr7/sGSshWj8b6WrtuNjnAlSr40E+AgfeVrIAAAJMmJoCQAAAAAEAAAAAls0BeEchu991JfnCZYCejekgR1SixnwaXQ80yzJXhAUAAAABAAAAAAMqbTGvyOcvPuApiT8JCDsMXqeRWck0Ss8Zlxc0OzhHAAAAAVVTREMAAAAAQj59BfLsr7/sGSshWj8b6WrtuNjnAlSr40E+AgfeVrIAAAAAAJiWgAAAAAAAAAADNDs4RwAAAEBsY9JUoAwafnGojQcckXcOvght/skV5TLDkGYEZFgcoaofnRtEPJg1H9n6xI2rUPEldp6sTytYzSw+nAi/LbUMZH9mjAAAAEBVWIRriJF27OqY/hS5VOvO8Swbw4HjBiPzrffwZ5xq7RqYEpx4OOmbl94jj9Cdp93lyToIiH8jFJaSkQXPtGkPMleEBQAAAEB8ExSUA9xbTum5cKoarWfhgv3JX01GzddCsF/IhXgIb83AtTbIq6NrUjYHcgoID4JjiOMJcft0dUJa/EeEE7sEAAAAAAAAAAE0OzhHAAAAQPNXa7NgKAPG5/U0iJYvefDToAH9jgo8FYT7q3mYqAF0uZrlZaIYo/X18DSd36dHzRhvr1UuLYkstu2u9y3ScQY=",
+        "resultXdr": "AAAAAAAAArz////zu2AmCJI31SmmC6qXjcwfYgsaCyTb4enG267b6IADUC8AAAAAAAAAAP////8AAAAGAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAYAAAAAAAAAAAAAABEAAAAAAAAAAAAAAAH////+AAAAAAAAAAH////+AAAAAAAAAAA=",
+        "resultMetaXdr": "AAAABAAAAAAAAAAEAAAAAwAFJXgAAAAAAAAAAAMqbTGvyOcvPuApiT8JCDsMXqeRWck0Ss8Zlxc0OzhHAAAALpDfahAAAAktAAAAAQAAAAEAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAABHAAAAAAAAAAMAAAAAAAAJLgAAAABoUyJqAAAAAAAAAAEABSV4AAAAAAAAAAADKm0xr8jnLz7gKYk/CQg7DF6nkVnJNErPGZcXNDs4RwAAAC6Q32oQAAAJLQAAAAEAAAABAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAARwAAAAAAAAADAAAAAAAACS4AAAAAaFMiagAAAAAAAAADAAUivAAAAAAAAAAAvyZGpho5b9ZHNbQ/wuHSWger8YCH50EWTRCJ3WR/ZowAAAAXSHbnnAAARdUAAAI1AAAAAQAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAwAAAAAABSK8AAAAAGhsqc4AAAAAAAAAAQAFJXgAAAAAAAAAAL8mRqYaOW/WRzW0P8Lh0loHq/GAh+dBFk0Qid1kf2aMAAAAF0h255wAAEXVAAACNgAAAAEAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAAAAAAMAAAAAAAUleAAAAABobLd8AAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAAAEAAAAAAAAAAgAAAA8AAAADZmVlAAAAABIAAAAAAAAAAAMqbTGvyOcvPuApiT8JCDsMXqeRWck0Ss8Zlxc0OzhHAAAACgAAAAAAAAAAAAAAAAAAArwAAAAA",
+        "events": {
+          "transactionEventsXdr": [
+            "AAAAAAAAAAAAAAAB15KLcsJwPM/q9+uf9O9NUEpVqLl5/JtFDqLIQrTRzmEAAAABAAAAAAAAAAIAAAAPAAAAA2ZlZQAAAAASAAAAAAAAAAADKm0xr8jnLz7gKYk/CQg7DF6nkVnJNErPGZcXNDs4RwAAAAoAAAAAAAAAAAAAAAAAAAK8"
+          ]
+        },
+        "ledger": 337272,
+        "createdAt": 1751955324
+      },
+      {
+        "status": "SUCCESS",
+        "txHash": "973699dbd48afb3c81b796edce895aebe0023bbf250a6a2abd00086e5c94ab84",
+        "applicationOrder": 2,
+        "feeBump": false,
+        "envelopeXdr": "AAAAAgAAAACFivUlMyXwtcfYryl8RvpJ9Z5pRzP1+x7CbLyW3pnYDgAPQkAAAMdKAAABqAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAABAAAAABB90WssODNIgi6BHveqzxTRmIpvAFRyVNM+Hm2GVuCcAAAAAAAAAADtlCZZ5vMl+JUtJJAOPYwB9hb3stEZIjMkJ2yf2ghFPAAAABdIdugAAAAAAAAAAALemdgOAAAAQE5e8FMYtuh/E8YR+eMTlnsJ3oj9Fr9KvhZnRW/bFXIeQybZwxYoQoVLjMAwHvAFqCGE/yFJOipMyPBVDvDxpA+GVuCcAAAAQLjToPzfn0kYZaepMnJbaFbMcG2f8OrD8NxOTK0peGXaIeuLsPTxRms6NuKedhzKqgCnpyMOwxm4u838aw2vdww=",
+        "resultXdr": "AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAA=",
+        "resultMetaXdr": "AAAABAAAAAAAAAACAAAAAwAFJXgAAAAAAAAAAIWK9SUzJfC1x9ivKXxG+kn1nmlHM/X7HsJsvJbemdgOAAAAACyz13AAAMdKAAABpwAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAAAAAAMAAAAAAAUGFgAAAABobBpyAAAAAAAAAAEABSV4AAAAAAAAAACFivUlMyXwtcfYryl8RvpJ9Z5pRzP1+x7CbLyW3pnYDgAAAAAss9dwAADHSgAAAagAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAAAAAADAAAAAAAFJXgAAAAAaGy3fAAAAAAAAAABAAAAAAAAAAMAAAADAAUlbAAAAAAAAAAAEH3Rayw4M0iCLoEe96rPFNGYim8AVHJU0z4ebYZW4JwBol77S/sJ1AAAAF8AAADIAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAwAAAAAAAMdRAAAAAGhW2rkAAAAAAAAAAQAFJXgAAAAAAAAAABB90WssODNIgi6BHveqzxTRmIpvAFRyVNM+Hm2GVuCcAaJe5AOEIdQAAABfAAAAyAAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAAAAAAMAAAAAAADHUQAAAABoVtq5AAAAAAAAAAAABSV4AAAAAAAAAADtlCZZ5vMl+JUtJJAOPYwB9hb3stEZIjMkJ2yf2ghFPAAAABdIdugAAAUleAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAdeSi3LCcDzP6vfrn/TvTVBKVai5efybRQ6iyEK00c5hAAAAAQAAAAAAAAAEAAAADwAAAAh0cmFuc2ZlcgAAABIAAAAAAAAAABB90WssODNIgi6BHveqzxTRmIpvAFRyVNM+Hm2GVuCcAAAAEgAAAAAAAAAA7ZQmWebzJfiVLSSQDj2MAfYW97LRGSIzJCdsn9oIRTwAAAAOAAAABm5hdGl2ZQAAAAAACgAAAAAAAAAAAAAAF0h26AAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAAAEAAAAAAAAAAgAAAA8AAAADZmVlAAAAABIAAAAAAAAAAIWK9SUzJfC1x9ivKXxG+kn1nmlHM/X7HsJsvJbemdgOAAAACgAAAAAAAAAAAAAAAAAAAGQAAAAA",
+        "events": {
+          "transactionEventsXdr": [
+            "AAAAAAAAAAAAAAAB15KLcsJwPM/q9+uf9O9NUEpVqLl5/JtFDqLIQrTRzmEAAAABAAAAAAAAAAIAAAAPAAAAA2ZlZQAAAAASAAAAAAAAAACFivUlMyXwtcfYryl8RvpJ9Z5pRzP1+x7CbLyW3pnYDgAAAAoAAAAAAAAAAAAAAAAAAABk"
+          ],
+          "contractEventsXdr": [
+            [
+              "AAAAAAAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAAAEAAAAAAAAABAAAAA8AAAAIdHJhbnNmZXIAAAASAAAAAAAAAAAQfdFrLDgzSIIugR73qs8U0ZiKbwBUclTTPh5thlbgnAAAABIAAAAAAAAAAO2UJlnm8yX4lS0kkA49jAH2Fvey0RkiMyQnbJ/aCEU8AAAADgAAAAZuYXRpdmUAAAAAAAoAAAAAAAAAAAAAABdIdugA"
+            ]
+          ]
+        },
+        "ledger": 337272,
+        "createdAt": 1751955324
+      },
+      {
+        "status": "SUCCESS",
+        "txHash": "755b48791d7b1b7c4f68675e78ba5167162133b0873949235e81006a21dd52cd",
+        "applicationOrder": 3,
+        "feeBump": false,
+        "envelopeXdr": "AAAAAgAAAABpUTPXPvN3+8v2Cl+6qDXlDqQ6ktoudhowSiMNBqhZngExLQAAAA2hAAAVwgAAAAEAAAAAAAAAAAAAAABobLeMAAAAAAAAAAEAAAABAAAAAGlRM9c+83f7y/YKX7qoNeUOpDqS2i52GjBKIw0GqFmeAAAAGAAAAAAAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAJc2V0X3ByaWNlAAAAAAAAAgAAABAAAAABAAAAEAAAAAoAAAAAAAAAAJYxZhBWnlZ3AAAACgAAAAAAAAAAA4svb21d+NMAAAAKAAAAAAAAAAAAAFrzF8WOngAAAAoAAAAAAAAAAAAAzlZJvDSrAAAACgAAAAAAAAAAADUZdnd4hHsAAAAKAAAAAAAAAAAAAFryNi8g1QAAAAoAAAAAAAAAAAAANFak+TXaAAAACgAAAAAAAAAAAAZXAiMM0PQAAAAKAAAAAAAAAAAAATClyfjScwAAAAoAAAAAAAAAAAAAEPEKMAkQAAAACgAAAAAAAAAAAAS7lEpZRkoAAAAKAAAAAAAAAAAAAFrzEHpAAAAAAAoAAAAAAAAAAAABboY05/qTAAAACgAAAAAAAAAAAAAWjvy21H4AAAAKAAAAAAAAAAAAAqUWLpOXrgAAAAoAAAAAAAAAAAAAarh2TTl4AAAABQAAAZforF6gAAAAAQAAAAAAAAAAAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACXNldF9wcmljZQAAAAAAAAIAAAAQAAAAAQAAABAAAAAKAAAAAAAAAACWMWYQVp5WdwAAAAoAAAAAAAAAAAOLL29tXfjTAAAACgAAAAAAAAAAAABa8xfFjp4AAAAKAAAAAAAAAAAAAM5WSbw0qwAAAAoAAAAAAAAAAAA1GXZ3eIR7AAAACgAAAAAAAAAAAABa8jYvINUAAAAKAAAAAAAAAAAAADRWpPk12gAAAAoAAAAAAAAAAAAGVwIjDND0AAAACgAAAAAAAAAAAAEwpcn40nMAAAAKAAAAAAAAAAAAABDxCjAJEAAAAAoAAAAAAAAAAAAEu5RKWUZKAAAACgAAAAAAAAAAAABa8xB6QAAAAAAKAAAAAAAAAAAAAW6GNOf6kwAAAAoAAAAAAAAAAAAAFo78ttR+AAAACgAAAAAAAAAAAAKlFi6Tl64AAAAKAAAAAAAAAAAAAGq4dk05eAAAAAUAAAGX6KxeoAAAAAAAAAABAAAAAAAAAAEAAAAH2meYeDjstDaE4KhbEjBxwWdgVqPrbT2cAthX7ajkTcMAAAARAAAABgAAAAGw7KROebfFrhD7dcxcLPrX7UfuazOzetkAMPD12FOYmAAAAAkAAAGX6KxeoAAAAAAAAAAAAAAAAAAAAAYAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAJAAABl+isXqAAAAAAAAAAAQAAAAAAAAAGAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACQAAAZforF6gAAAAAAAAAAIAAAAAAAAABgAAAAGw7KROebfFrhD7dcxcLPrX7UfuazOzetkAMPD12FOYmAAAAAkAAAGX6KxeoAAAAAAAAAADAAAAAAAAAAYAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAJAAABl+isXqAAAAAAAAAABAAAAAAAAAAGAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACQAAAZforF6gAAAAAAAAAAUAAAAAAAAABgAAAAGw7KROebfFrhD7dcxcLPrX7UfuazOzetkAMPD12FOYmAAAAAkAAAGX6KxeoAAAAAAAAAAGAAAAAAAAAAYAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAJAAABl+isXqAAAAAAAAAABwAAAAAAAAAGAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACQAAAZforF6gAAAAAAAAAAgAAAAAAAAABgAAAAGw7KROebfFrhD7dcxcLPrX7UfuazOzetkAMPD12FOYmAAAAAkAAAGX6KxeoAAAAAAAAAAJAAAAAAAAAAYAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAJAAABl+isXqAAAAAAAAAACgAAAAAAAAAGAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACQAAAZforF6gAAAAAAAAAAsAAAAAAAAABgAAAAGw7KROebfFrhD7dcxcLPrX7UfuazOzetkAMPD12FOYmAAAAAkAAAGX6KxeoAAAAAAAAAAMAAAAAAAAAAYAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAJAAABl+isXqAAAAAAAAAADQAAAAAAAAAGAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACQAAAZforF6gAAAAAAAAAA4AAAAAAAAABgAAAAGw7KROebfFrhD7dcxcLPrX7UfuazOzetkAMPD12FOYmAAAAAkAAAGX6KxeoAAAAAAAAAAPAAAAAAAAAAYAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAUAAAAAQCn2MAAAJxAAAATiAAAAAAAmJaAAAAAAcyl2WAAAABAyIaUCPcC7eyzng1h8s/XLy+wLzmd2PzCj9lIRSesJVS/QlqhxdK6uiNtgP9nvcQ+D5jMAwCedquA5zDhQfOzDw==",
+        "resultXdr": "AAAAAAALMtUAAAAAAAAAAQAAAAAAAAAYAAAAANnVLpUIC01nXOWYpLQG/4W2uDzPwAmGLu9KQjrgOClAAAAAAA==",
+        "resultMetaXdr": "AAAABAAAAAAAAAACAAAAAwAFJXgAAAAAAAAAAGlRM9c+83f7y/YKX7qoNeUOpDqS2i52GjBKIw0GqFmeAAAAFlUyDQwAAA2hAAAVwQAAAAEAAAAAAAAAAAAAAAAAAQEBAAAAAQAAAAChM5sgwhIdyIwqcgCD9fwQBNYj/ox4Aw054hQxzKXZYAAAAAEAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAEAAAAAAAAAAwAAAAAABSU8AAAAAGhstlAAAAAAAAAAAQAFJXgAAAAAAAAAAGlRM9c+83f7y/YKX7qoNeUOpDqS2i52GjBKIw0GqFmeAAAAFlUyDQwAAA2hAAAVwgAAAAEAAAAAAAAAAAAAAAAAAQEBAAAAAQAAAAChM5sgwhIdyIwqcgCD9fwQBNYj/ox4Aw054hQxzKXZYAAAAAEAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAEAAAAAAAAAAwAAAAAABSV4AAAAAGhst3wAAAAAAAAAAQAAAAAAAAAiAAAAAwAFJTwAAAAGAAAAAAAAAAGw7KROebfFrhD7dcxcLPrX7UfuazOzetkAMPD12FOYmAAAABQAAAABAAAAEwAAAADaZ5h4OOy0NoTgqFsSMHHBZ2BWo+ttPZwC2FftqORNwwAAAAEAAAAYAAAADgAAAAVhZG1pbgAAAAAAABIAAAAAAAAAAGlRM9c+83f7y/YKX7qoNeUOpDqS2i52GjBKIw0GqFmeAAAADgAAAAphc3NldF90dGxzAAAAAAAQAAAAAQAAAAAAAAAOAAAABmFzc2V0cwAAAAAAEAAAAAEAAAAQAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQlRDAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA0VUSAAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAARVU0RUAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADWFJQAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA1NPTAAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAARVU0RDAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQURBAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABEFWQVgAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANET1QAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAFTUFUSUMAAAAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAARMSU5LAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADREFJAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABEFUT00AAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANYTE0AAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADVU5JAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABEVVUkMAAAAOAAAACmJhc2VfYXNzZXQAAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA1VTRAAAAAAOAAAACGRlY2ltYWxzAAAAAwAAAA4AAAAOAAAADmxhc3RfdGltZXN0YW1wAAAAAAAFAAABl+inysAAAAAOAAAABnBlcmlvZAAAAAAABQAAAAAFJlwAAAAADgAAAApyZXNvbHV0aW9uAAAAAAADAAST4AAAAA8AAAADQURBAAAAAAMAAAAGAAAADwAAAARBVE9NAAAAAwAAAAwAAAAPAAAABEFWQVgAAAADAAAABwAAAA8AAAADQlRDAAAAAAMAAAAAAAAADwAAAANEQUkAAAAAAwAAAAsAAAAPAAAAA0RPVAAAAAADAAAACAAAAA8AAAADRVRIAAAAAAMAAAABAAAADwAAAARFVVJDAAAAAwAAAA8AAAAPAAAABExJTksAAAADAAAACgAAAA8AAAAFTUFUSUMAAAAAAAADAAAACQAAAA8AAAADU09MAAAAAAMAAAAEAAAADwAAAANVTkkAAAAAAwAAAA4AAAAPAAAABFVTREMAAAADAAAABQAAAA8AAAAEVVNEVAAAAAMAAAACAAAADwAAAANYTE0AAAAAAwAAAA0AAAAPAAAAA1hSUAAAAAADAAAAAwAAAAAAAAABAAUleAAAAAYAAAAAAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAAFAAAAAEAAAATAAAAANpnmHg47LQ2hOCoWxIwccFnYFaj6209nALYV+2o5E3DAAAAAQAAABgAAAAOAAAABWFkbWluAAAAAAAAEgAAAAAAAAAAaVEz1z7zd/vL9gpfuqg15Q6kOpLaLnYaMEojDQaoWZ4AAAAOAAAACmFzc2V0X3R0bHMAAAAAABAAAAABAAAAAAAAAA4AAAAGYXNzZXRzAAAAAAAQAAAAAQAAABAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANCVEMAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRVRIAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABFVTRFQAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANYUlAAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADU09MAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABFVTREMAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANBREEAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAEQVZBWAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA0RPVAAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAAVNQVRJQwAAAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABExJTksAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANEQUkAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAEQVRPTQAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA1hMTQAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANVTkkAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAERVVSQwAAAA4AAAAKYmFzZV9hc3NldAAAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADVVNEAAAAAA4AAAAIZGVjaW1hbHMAAAADAAAADgAAAA4AAAAObGFzdF90aW1lc3RhbXAAAAAAAAUAAAGX6KxeoAAAAA4AAAAGcGVyaW9kAAAAAAAFAAAAAAUmXAAAAAAOAAAACnJlc29sdXRpb24AAAAAAAMABJPgAAAADwAAAANBREEAAAAAAwAAAAYAAAAPAAAABEFUT00AAAADAAAADAAAAA8AAAAEQVZBWAAAAAMAAAAHAAAADwAAAANCVEMAAAAAAwAAAAAAAAAPAAAAA0RBSQAAAAADAAAACwAAAA8AAAADRE9UAAAAAAMAAAAIAAAADwAAAANFVEgAAAAAAwAAAAEAAAAPAAAABEVVUkMAAAADAAAADwAAAA8AAAAETElOSwAAAAMAAAAKAAAADwAAAAVNQVRJQwAAAAAAAAMAAAAJAAAADwAAAANTT0wAAAAAAwAAAAQAAAAPAAAAA1VOSQAAAAADAAAADgAAAA8AAAAEVVNEQwAAAAMAAAAFAAAADwAAAARVU0RUAAAAAwAAAAIAAAAPAAAAA1hMTQAAAAADAAAADQAAAA8AAAADWFJQAAAAAAMAAAADAAAAAAAAAAAABSV4AAAACRtWwYKp8aF2qX+Jg4xRIWaw97oBDTKmDaMTGerc8aiVAAVo+QAAAAAAAAAAAAUleAAAAAmXaw4b0ehOqe/BC602CtDLHlLJmGqECWqW8osfIOsiFAAFaPkAAAAAAAAAAAAFJXgAAAAJ/Wpp20YmTDXBw16kOtl1jgGpveiIqSIxHJpVhi3SIEUABWj5AAAAAAAAAAAABSV4AAAABgAAAAAAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAJAAABl+isXqAAAAAAAAAADAAAAAAAAAAKAAAAAAAAAAAAAW6GNOf6kwAAAAAAAAAAAAUleAAAAAlOPfLSMl9xE2dQ06IxdD68yMhOeU3fKrkbPJ33VSBPRAAFaPkAAAAAAAAAAAAFJXgAAAAGAAAAAAAAAAGw7KROebfFrhD7dcxcLPrX7UfuazOzetkAMPD12FOYmAAAAAkAAAGX6KxeoAAAAAAAAAAOAAAAAAAAAAoAAAAAAAAAAAACpRYuk5euAAAAAAAAAAAABSV4AAAABgAAAAAAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAJAAABl+isXqAAAAAAAAAAAQAAAAAAAAAKAAAAAAAAAAADiy9vbV340wAAAAAAAAAAAAUleAAAAAmohgXFLMfosl9gbyvew1/Cx/XjW76VVXLo6LbDlL0kVAAFaPkAAAAAAAAAAAAFJXgAAAAJa84nEi9j/5CfMlG33MtaNS1H2L5iqbq1IUDD0gOsCyQABWj5AAAAAAAAAAAABSV4AAAABgAAAAAAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAJAAABl+isXqAAAAAAAAAADQAAAAAAAAAKAAAAAAAAAAAAABaO/LbUfgAAAAAAAAAAAAUleAAAAAYAAAAAAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACQAAAZforF6gAAAAAAAAAAgAAAAAAAAACgAAAAAAAAAAAAEwpcn40nMAAAAAAAAAAAAFJXgAAAAJrV+x0DJmHq+Ny9EKTJDwOe65HIxhA3fa9jbwrFUeJc8ABWj5AAAAAAAAAAAABSV4AAAACRTs0YFy1+M2aG76tT2eSadx45lSWuKqh00V8LjLDHhQAAVo+QAAAAAAAAAAAAUleAAAAAYAAAAAAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACQAAAZforF6gAAAAAAAAAAcAAAAAAAAACgAAAAAAAAAAAAZXAiMM0PQAAAAAAAAAAAAFJXgAAAAGAAAAAAAAAAGw7KROebfFrhD7dcxcLPrX7UfuazOzetkAMPD12FOYmAAAAAkAAAGX6KxeoAAAAAAAAAAEAAAAAAAAAAoAAAAAAAAAAAA1GXZ3eIR7AAAAAAAAAAAABSV4AAAABgAAAAAAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAJAAABl+isXqAAAAAAAAAADwAAAAAAAAAKAAAAAAAAAAAAAGq4dk05eAAAAAAAAAAAAAUleAAAAAmHGDZmgBRLxoX5oiXi09GSmdgRRxs9MMbbCzQytgNhkQAFaPkAAAAAAAAAAAAFJXgAAAAJaSfopin+fB6bsgXu4ZoSM78ihrZaD4QHL6nrUbS6NZMABWj5AAAAAAAAAAAABSV4AAAABgAAAAAAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAJAAABl+isXqAAAAAAAAAABgAAAAAAAAAKAAAAAAAAAAAAADRWpPk12gAAAAAAAAAAAAUleAAAAAYAAAAAAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACQAAAZforF6gAAAAAAAAAAUAAAAAAAAACgAAAAAAAAAAAABa8jYvINUAAAAAAAAAAAAFJXgAAAAGAAAAAAAAAAGw7KROebfFrhD7dcxcLPrX7UfuazOzetkAMPD12FOYmAAAAAkAAAGX6KxeoAAAAAAAAAALAAAAAAAAAAoAAAAAAAAAAAAAWvMQekAAAAAAAAAAAAAABSV4AAAABgAAAAAAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAJAAABl+isXqAAAAAAAAAACQAAAAAAAAAKAAAAAAAAAAAAABDxCjAJEAAAAAAAAAAAAAUleAAAAAYAAAAAAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACQAAAZforF6gAAAAAAAAAAMAAAAAAAAACgAAAAAAAAAAAADOVkm8NKsAAAAAAAAAAAAFJXgAAAAJ9RAqLANH4ius/Vq43FXikVlC8/aStdNH+0VPE+f/vrwABWj5AAAAAAAAAAAABSV4AAAACa+q8ZyOcbjQZOBzMuII58FgolfTj1g6nASeWehH/Y4yAAVo+QAAAAAAAAAAAAUleAAAAAYAAAAAAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACQAAAZforF6gAAAAAAAAAAoAAAAAAAAACgAAAAAAAAAAAAS7lEpZRkoAAAAAAAAAAAAFJXgAAAAJkaaYJYTilZxZ2YFR1/faqISLB6Gb7lWFvG3uRd20iZwABWj5AAAAAAAAAAAABSV4AAAACeiycPprqSDFiAUYAnjx/SjeVXwXe6Li76gXDPNDNc/7AAVo+QAAAAAAAAAAAAUleAAAAAYAAAAAAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACQAAAZforF6gAAAAAAAAAAIAAAAAAAAACgAAAAAAAAAAAABa8xfFjp4AAAAAAAAAAAAFJXgAAAAJCOYm2pVJLLGMpI0wbbfMeTDDUY0ZlkZTETzdKKsuCZYABWj5AAAAAAAAAAAABSV4AAAACR5Y6Ub0+8DldV2wrMOiPhNnqsMaYcpGUkKm4/40DqEHAAVo+QAAAAAAAAAAAAUleAAAAAYAAAAAAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACQAAAZforF6gAAAAAAAAAAAAAAAAAAAACgAAAAAAAAAAljFmEFaeVncAAAAAAAAAAQAAAAAAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAABAAAAAAAAAAMAAAAPAAAACXJlZmxlY3RvcgAAAAAAAA8AAAAGcHJpY2VzAAAAAAAPAAAABnVwZGF0ZQAAAAAAEAAAAAEAAAAQAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQlRDAAAAAAoAAAAAAAAAAJYxZhBWnlZ3AAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRVRIAAAAAAoAAAAAAAAAAAOLL29tXfjTAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAEVVNEVAAAAAoAAAAAAAAAAAAAWvMXxY6eAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADWFJQAAAAAAoAAAAAAAAAAAAAzlZJvDSrAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADU09MAAAAAAoAAAAAAAAAAAA1GXZ3eIR7AAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAEVVNEQwAAAAoAAAAAAAAAAAAAWvI2LyDVAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQURBAAAAAAoAAAAAAAAAAAAANFak+TXaAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAEQVZBWAAAAAoAAAAAAAAAAAAGVwIjDND0AAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRE9UAAAAAAoAAAAAAAAAAAABMKXJ+NJzAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAFTUFUSUMAAAAAAAAKAAAAAAAAAAAAABDxCjAJEAAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABExJTksAAAAKAAAAAAAAAAAABLuUSllGSgAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA0RBSQAAAAAKAAAAAAAAAAAAAFrzEHpAAAAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABEFUT00AAAAKAAAAAAAAAAAAAW6GNOf6kwAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA1hMTQAAAAAKAAAAAAAAAAAAABaO/LbUfgAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA1VOSQAAAAAKAAAAAAAAAAAAAqUWLpOXrgAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABEVVUkMAAAAKAAAAAAAAAAAAAGq4dk05eAAAAAIAAAADAAUleAAAAAAAAAAAaVEz1z7zd/vL9gpfuqg15Q6kOpLaLnYaMEojDQaoWZ4AAAAWVTINDAAADaEAABXCAAAAAQAAAAAAAAAAAAAAAAABAQEAAAABAAAAAKEzmyDCEh3IjCpyAIP1/BAE1iP+jHgDDTniFDHMpdlgAAAAAQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAQAAAAAAAAADAAAAAAAFJXgAAAAAaGy3fAAAAAAAAAABAAUleAAAAAAAAAAAaVEz1z7zd/vL9gpfuqg15Q6kOpLaLnYaMEojDQaoWZ4AAAAWVb9xGwAADaEAABXCAAAAAQAAAAAAAAAAAAAAAAABAQEAAAABAAAAAKEzmyDCEh3IjCpyAIP1/BAE1iP+jHgDDTniFDHMpdlgAAAAAQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAQAAAAAAAAADAAAAAAAFJXgAAAAAaGy3fAAAAAAAAAABAAAAAQAAAAAAAAAAAAdSWQAAAAAAA+AYAAAAAAADr2sAAAABAAAAAQAAAAIAAAAAAAAAAAAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAAAEAAAAAAAAAAgAAAA8AAAADZmVlAAAAABIAAAAAAAAAAGlRM9c+83f7y/YKX7qoNeUOpDqS2i52GjBKIw0GqFmeAAAACgAAAAAAAAAAAAAAAACYluQAAAABAAAAAAAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAAAEAAAAAAAAAAgAAAA8AAAADZmVlAAAAABIAAAAAAAAAAGlRM9c+83f7y/YKX7qoNeUOpDqS2i52GjBKIw0GqFmeAAAACv////////////////9ym/EAAAAWAAAAAQAAAAAAAAAAAAAAAgAAAAAAAAADAAAADwAAAAdmbl9jYWxsAAAAAA0AAAAgsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAPAAAACXNldF9wcmljZQAAAAAAABAAAAABAAAAAgAAABAAAAABAAAAEAAAAAoAAAAAAAAAAJYxZhBWnlZ3AAAACgAAAAAAAAAAA4svb21d+NMAAAAKAAAAAAAAAAAAAFrzF8WOngAAAAoAAAAAAAAAAAAAzlZJvDSrAAAACgAAAAAAAAAAADUZdnd4hHsAAAAKAAAAAAAAAAAAAFryNi8g1QAAAAoAAAAAAAAAAAAANFak+TXaAAAACgAAAAAAAAAAAAZXAiMM0PQAAAAKAAAAAAAAAAAAATClyfjScwAAAAoAAAAAAAAAAAAAEPEKMAkQAAAACgAAAAAAAAAAAAS7lEpZRkoAAAAKAAAAAAAAAAAAAFrzEHpAAAAAAAoAAAAAAAAAAAABboY05/qTAAAACgAAAAAAAAAAAAAWjvy21H4AAAAKAAAAAAAAAAAAAqUWLpOXrgAAAAoAAAAAAAAAAAAAarh2TTl4AAAABQAAAZforF6gAAAAAQAAAAAAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAABAAAAAAAAAAMAAAAPAAAACXJlZmxlY3RvcgAAAAAAAA8AAAAGcHJpY2VzAAAAAAAPAAAABnVwZGF0ZQAAAAAAEAAAAAEAAAAQAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQlRDAAAAAAoAAAAAAAAAAJYxZhBWnlZ3AAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRVRIAAAAAAoAAAAAAAAAAAOLL29tXfjTAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAEVVNEVAAAAAoAAAAAAAAAAAAAWvMXxY6eAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADWFJQAAAAAAoAAAAAAAAAAAAAzlZJvDSrAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADU09MAAAAAAoAAAAAAAAAAAA1GXZ3eIR7AAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAEVVNEQwAAAAoAAAAAAAAAAAAAWvI2LyDVAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQURBAAAAAAoAAAAAAAAAAAAANFak+TXaAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAEQVZBWAAAAAoAAAAAAAAAAAAGVwIjDND0AAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRE9UAAAAAAoAAAAAAAAAAAABMKXJ+NJzAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAFTUFUSUMAAAAAAAAKAAAAAAAAAAAAABDxCjAJEAAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABExJTksAAAAKAAAAAAAAAAAABLuUSllGSgAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA0RBSQAAAAAKAAAAAAAAAAAAAFrzEHpAAAAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABEFUT00AAAAKAAAAAAAAAAAAAW6GNOf6kwAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA1hMTQAAAAAKAAAAAAAAAAAAABaO/LbUfgAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA1VOSQAAAAAKAAAAAAAAAAAAAqUWLpOXrgAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABEVVUkMAAAAKAAAAAAAAAAAAAGq4dk05eAAAAAEAAAAAAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAAAgAAAAAAAAACAAAADwAAAAlmbl9yZXR1cm4AAAAAAAAPAAAACXNldF9wcmljZQAAAAAAAAEAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAKcmVhZF9lbnRyeQAAAAAABQAAAAAAAAASAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAC3dyaXRlX2VudHJ5AAAAAAUAAAAAAAAAEQAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAABBsZWRnZXJfcmVhZF9ieXRlAAAABQAAAAAAAFjgAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEWxlZGdlcl93cml0ZV9ieXRlAAAAAAAABQAAAAAAAAtcAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADXJlYWRfa2V5X2J5dGUAAAAAAAAFAAAAAAAABFQAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAOd3JpdGVfa2V5X2J5dGUAAAAAAAUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAAA5yZWFkX2RhdGFfYnl0ZQAAAAAABQAAAAAAAAVcAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD3dyaXRlX2RhdGFfYnl0ZQAAAAAFAAAAAAAAC1wAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAOcmVhZF9jb2RlX2J5dGUAAAAAAAUAAAAAAABThAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAAA93cml0ZV9jb2RlX2J5dGUAAAAABQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACmVtaXRfZXZlbnQAAAAAAAUAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAAA9lbWl0X2V2ZW50X2J5dGUAAAAABQAAAAAAAAT4AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACGNwdV9pbnNuAAAABQAAAAAAUVs1AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACG1lbV9ieXRlAAAABQAAAAAAI+WHAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEWludm9rZV90aW1lX25zZWNzAAAAAAAABQAAAAAAJjL5AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD21heF9yd19rZXlfYnl0ZQAAAAAFAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAQbWF4X3J3X2RhdGFfYnl0ZQAAAAUAAAAAAAAFXAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAABBtYXhfcndfY29kZV9ieXRlAAAABQAAAAAAAFOEAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAE21heF9lbWl0X2V2ZW50X2J5dGUAAAAABQAAAAAAAAT4",
+        "diagnosticEventsXdr": [
+          "AAAAAQAAAAAAAAAAAAAAAgAAAAAAAAADAAAADwAAAAdmbl9jYWxsAAAAAA0AAAAgsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAPAAAACXNldF9wcmljZQAAAAAAABAAAAABAAAAAgAAABAAAAABAAAAEAAAAAoAAAAAAAAAAJYxZhBWnlZ3AAAACgAAAAAAAAAAA4svb21d+NMAAAAKAAAAAAAAAAAAAFrzF8WOngAAAAoAAAAAAAAAAAAAzlZJvDSrAAAACgAAAAAAAAAAADUZdnd4hHsAAAAKAAAAAAAAAAAAAFryNi8g1QAAAAoAAAAAAAAAAAAANFak+TXaAAAACgAAAAAAAAAAAAZXAiMM0PQAAAAKAAAAAAAAAAAAATClyfjScwAAAAoAAAAAAAAAAAAAEPEKMAkQAAAACgAAAAAAAAAAAAS7lEpZRkoAAAAKAAAAAAAAAAAAAFrzEHpAAAAAAAoAAAAAAAAAAAABboY05/qTAAAACgAAAAAAAAAAAAAWjvy21H4AAAAKAAAAAAAAAAAAAqUWLpOXrgAAAAoAAAAAAAAAAAAAarh2TTl4AAAABQAAAZforF6g",
+          "AAAAAQAAAAAAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAABAAAAAAAAAAMAAAAPAAAACXJlZmxlY3RvcgAAAAAAAA8AAAAGcHJpY2VzAAAAAAAPAAAABnVwZGF0ZQAAAAAAEAAAAAEAAAAQAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQlRDAAAAAAoAAAAAAAAAAJYxZhBWnlZ3AAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRVRIAAAAAAoAAAAAAAAAAAOLL29tXfjTAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAEVVNEVAAAAAoAAAAAAAAAAAAAWvMXxY6eAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADWFJQAAAAAAoAAAAAAAAAAAAAzlZJvDSrAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADU09MAAAAAAoAAAAAAAAAAAA1GXZ3eIR7AAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAEVVNEQwAAAAoAAAAAAAAAAAAAWvI2LyDVAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQURBAAAAAAoAAAAAAAAAAAAANFak+TXaAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAEQVZBWAAAAAoAAAAAAAAAAAAGVwIjDND0AAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRE9UAAAAAAoAAAAAAAAAAAABMKXJ+NJzAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAFTUFUSUMAAAAAAAAKAAAAAAAAAAAAABDxCjAJEAAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABExJTksAAAAKAAAAAAAAAAAABLuUSllGSgAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA0RBSQAAAAAKAAAAAAAAAAAAAFrzEHpAAAAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABEFUT00AAAAKAAAAAAAAAAAAAW6GNOf6kwAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA1hMTQAAAAAKAAAAAAAAAAAAABaO/LbUfgAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA1VOSQAAAAAKAAAAAAAAAAAAAqUWLpOXrgAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABEVVUkMAAAAKAAAAAAAAAAAAAGq4dk05eA==",
+          "AAAAAQAAAAAAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAACAAAAAAAAAAIAAAAPAAAACWZuX3JldHVybgAAAAAAAA8AAAAJc2V0X3ByaWNlAAAAAAAAAQ==",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACnJlYWRfZW50cnkAAAAAAAUAAAAAAAAAEg==",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAC3dyaXRlX2VudHJ5AAAAAAUAAAAAAAAAEQ==",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEGxlZGdlcl9yZWFkX2J5dGUAAAAFAAAAAAAAWOA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEWxlZGdlcl93cml0ZV9ieXRlAAAAAAAABQAAAAAAAAtc",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADXJlYWRfa2V5X2J5dGUAAAAAAAAFAAAAAAAABFQ=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADndyaXRlX2tleV9ieXRlAAAAAAAFAAAAAAAAAAA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADnJlYWRfZGF0YV9ieXRlAAAAAAAFAAAAAAAABVw=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD3dyaXRlX2RhdGFfYnl0ZQAAAAAFAAAAAAAAC1w=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADnJlYWRfY29kZV9ieXRlAAAAAAAFAAAAAAAAU4Q=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD3dyaXRlX2NvZGVfYnl0ZQAAAAAFAAAAAAAAAAA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACmVtaXRfZXZlbnQAAAAAAAUAAAAAAAAAAQ==",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD2VtaXRfZXZlbnRfYnl0ZQAAAAAFAAAAAAAABPg=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACGNwdV9pbnNuAAAABQAAAAAAUVs1",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACG1lbV9ieXRlAAAABQAAAAAAI+WH",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEWludm9rZV90aW1lX25zZWNzAAAAAAAABQAAAAAAJjL5",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD21heF9yd19rZXlfYnl0ZQAAAAAFAAAAAAAAAEA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEG1heF9yd19kYXRhX2J5dGUAAAAFAAAAAAAABVw=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEG1heF9yd19jb2RlX2J5dGUAAAAFAAAAAAAAU4Q=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAE21heF9lbWl0X2V2ZW50X2J5dGUAAAAABQAAAAAAAAT4"
+        ],
+        "events": {
+          "transactionEventsXdr": [
+            "AAAAAAAAAAAAAAAB15KLcsJwPM/q9+uf9O9NUEpVqLl5/JtFDqLIQrTRzmEAAAABAAAAAAAAAAIAAAAPAAAAA2ZlZQAAAAASAAAAAAAAAABpUTPXPvN3+8v2Cl+6qDXlDqQ6ktoudhowSiMNBqhZngAAAAoAAAAAAAAAAAAAAAAAmJbk",
+            "AAAAAQAAAAAAAAAB15KLcsJwPM/q9+uf9O9NUEpVqLl5/JtFDqLIQrTRzmEAAAABAAAAAAAAAAIAAAAPAAAAA2ZlZQAAAAASAAAAAAAAAABpUTPXPvN3+8v2Cl+6qDXlDqQ6ktoudhowSiMNBqhZngAAAAr/////////////////cpvx"
+          ],
+          "contractEventsXdr": [
+            [
+              "AAAAAAAAAAGw7KROebfFrhD7dcxcLPrX7UfuazOzetkAMPD12FOYmAAAAAEAAAAAAAAAAwAAAA8AAAAJcmVmbGVjdG9yAAAAAAAADwAAAAZwcmljZXMAAAAAAA8AAAAGdXBkYXRlAAAAAAAQAAAAAQAAABAAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANCVEMAAAAACgAAAAAAAAAAljFmEFaeVncAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANFVEgAAAAACgAAAAAAAAAAA4svb21d+NMAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAARVU0RUAAAACgAAAAAAAAAAAABa8xfFjp4AAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANYUlAAAAAACgAAAAAAAAAAAADOVkm8NKsAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANTT0wAAAAACgAAAAAAAAAAADUZdnd4hHsAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAARVU0RDAAAACgAAAAAAAAAAAABa8jYvINUAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANBREEAAAAACgAAAAAAAAAAAAA0VqT5NdoAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAARBVkFYAAAACgAAAAAAAAAAAAZXAiMM0PQAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANET1QAAAAACgAAAAAAAAAAAAEwpcn40nMAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAAVNQVRJQwAAAAAAAAoAAAAAAAAAAAAAEPEKMAkQAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAETElOSwAAAAoAAAAAAAAAAAAEu5RKWUZKAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADREFJAAAAAAoAAAAAAAAAAAAAWvMQekAAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAEQVRPTQAAAAoAAAAAAAAAAAABboY05/qTAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADWExNAAAAAAoAAAAAAAAAAAAAFo78ttR+AAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADVU5JAAAAAAoAAAAAAAAAAAACpRYuk5euAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAERVVSQwAAAAoAAAAAAAAAAAAAarh2TTl4"
+            ]
+          ]
+        },
+        "ledger": 337272,
+        "createdAt": 1751955324
+      },
+      {
+        "status": "SUCCESS",
+        "txHash": "5686dc3df8ef0b7af08edcf9cc2eecca90fdbab99626117770e46e0042efddcb",
+        "applicationOrder": 4,
+        "feeBump": false,
+        "envelopeXdr": "AAAAAgAAAACWDRNrgN4HpWfA2B7H3QSMtt7GSK/J3/cH+i/Waf406QExLQAAAA1qAAAVxAAAAAEAAAAAAAAAAAAAAABobLeMAAAAAAAAAAEAAAABAAAAAJYNE2uA3gelZ8DYHsfdBIy23sZIr8nf9wf6L9Zp/jTpAAAAGAAAAAAAAAABKrf0Z9GS/LKu+hOOCq4fWWIWaS1ePWMaLC7oHiY6uD8AAAAJc2V0X3ByaWNlAAAAAAAAAgAAABAAAAABAAAABwAAAAoAAAAAAAAAAAAAAAAAAAAAAAAACgAAAAAAAAAAAAAAFAjvQXUAAAAKAAAAAAAAAAAAAFry4TaWFwAAAAoAAAAAAAAAAAAAABlwHrujAAAACgAAAAAAAAAAAAAACkGhPLUAAAAKAAAAAAAAAAAAAAASRzQWKwAAAAoAAAAAAAAAAAAAYLyUqAn+AAAABQAAAZforF6gAAAAAQAAAAAAAAAAAAAAASq39GfRkvyyrvoTjgquH1liFmktXj1jGiwu6B4mOrg/AAAACXNldF9wcmljZQAAAAAAAAIAAAAQAAAAAQAAAAcAAAAKAAAAAAAAAAAAAAAAAAAAAAAAAAoAAAAAAAAAAAAAABQI70F1AAAACgAAAAAAAAAAAABa8uE2lhcAAAAKAAAAAAAAAAAAAAAZcB67owAAAAoAAAAAAAAAAAAAAApBoTy1AAAACgAAAAAAAAAAAAAAEkc0FisAAAAKAAAAAAAAAAAAAGC8lKgJ/gAAAAUAAAGX6KxeoAAAAAAAAAABAAAAAAAAAAEAAAAH2meYeDjstDaE4KhbEjBxwWdgVqPrbT2cAthX7ajkTcMAAAAHAAAABgAAAAEqt/Rn0ZL8sq76E44Krh9ZYhZpLV49YxosLugeJjq4PwAAAAkAAAGX6KxeoAAAAAAAAAABAAAAAAAAAAYAAAABKrf0Z9GS/LKu+hOOCq4fWWIWaS1ePWMaLC7oHiY6uD8AAAAJAAABl+isXqAAAAAAAAAAAgAAAAAAAAAGAAAAASq39GfRkvyyrvoTjgquH1liFmktXj1jGiwu6B4mOrg/AAAACQAAAZforF6gAAAAAAAAAAMAAAAAAAAABgAAAAEqt/Rn0ZL8sq76E44Krh9ZYhZpLV49YxosLugeJjq4PwAAAAkAAAGX6KxeoAAAAAAAAAAEAAAAAAAAAAYAAAABKrf0Z9GS/LKu+hOOCq4fWWIWaS1ePWMaLC7oHiY6uD8AAAAJAAABl+isXqAAAAAAAAAABQAAAAAAAAAGAAAAASq39GfRkvyyrvoTjgquH1liFmktXj1jGiwu6B4mOrg/AAAACQAAAZforF6gAAAAAAAAAAYAAAAAAAAABgAAAAEqt/Rn0ZL8sq76E44Krh9ZYhZpLV49YxosLugeJjq4PwAAABQAAAABAIlUQAAAnEAAAAu4AAAAAACYloAAAAABzKXZYAAAAEAiyeOyFuBoelRjU2uOG6W0J9jAVHsbNazj9Mu4AVSVGIQQGG1UhoGHvx2vNk2J+MYaK51j/FKuFa8tUgxZ3TsD",
+        "resultXdr": "AAAAAAAFp24AAAAAAAAAAQAAAAAAAAAYAAAAABZiId17tj6HU0cnDSIf44RCQvx4Ze+9PZivYVpJrS/TAAAAAA==",
+        "resultMetaXdr": "AAAABAAAAAAAAAACAAAAAwAFJXgAAAAAAAAAAJYNE2uA3gelZ8DYHsfdBIy23sZIr8nf9wf6L9Zp/jTpAAAAFsrsGzEAAA1qAAAVwwAAAAEAAAAAAAAAAAAAAAAAAQEBAAAAAQAAAAChM5sgwhIdyIwqcgCD9fwQBNYj/ox4Aw054hQxzKXZYAAAAAEAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAEAAAAAAAAAAwAAAAAABSU8AAAAAGhstlAAAAAAAAAAAQAFJXgAAAAAAAAAAJYNE2uA3gelZ8DYHsfdBIy23sZIr8nf9wf6L9Zp/jTpAAAAFsrsGzEAAA1qAAAVxAAAAAEAAAAAAAAAAAAAAAAAAQEBAAAAAQAAAAChM5sgwhIdyIwqcgCD9fwQBNYj/ox4Aw054hQxzKXZYAAAAAEAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAEAAAAAAAAAAwAAAAAABSV4AAAAAGhst3wAAAAAAAAAAQAAAAAAAAAOAAAAAwAFJTwAAAAGAAAAAAAAAAEqt/Rn0ZL8sq76E44Krh9ZYhZpLV49YxosLugeJjq4PwAAABQAAAABAAAAEwAAAADaZ5h4OOy0NoTgqFsSMHHBZ2BWo+ttPZwC2FftqORNwwAAAAEAAAAPAAAADgAAAAVhZG1pbgAAAAAAABIAAAAAAAAAAJYNE2uA3gelZ8DYHsfdBIy23sZIr8nf9wf6L9Zp/jTpAAAADgAAAAphc3NldF90dGxzAAAAAAAQAAAAAQAAAAAAAAAOAAAABmFzc2V0cwAAAAAAEAAAAAEAAAAHAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABLH5dkYL+BORXImsTnZP2P5eUUBSUtBUr2CqINF2cq2UAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAHSXSYIa79oluHQAHW5pRvejjN21RnZnNCH0sSNBE4FwQAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAAQNsQWZ0O43FGKVwnNQb73Fb8k8DG+dEYKpzAL3nWeMVAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABpwrZOHKolMpzUngjpVN0fvP6eQACmnfUvchJrBqHThMAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAE4PCZRN876zenIEPbQW6JFAmed8Z68VxHSATEED5wr6gAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAAUERMTiMWywKwo7JTTyHAexwihJiFQRSQ7R2FXxBE/2tAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABgoavkxQqSDdQ0Z3vRlwVqAiggskSD6a4g7Zql4s3jpYAAAAOAAAACmJhc2VfYXNzZXQAAAAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAATRO7qcufYlaCCIeG6YGn6tt1Va2Xd726owvhPtmIFKTAAAADgAAAAhkZWNpbWFscwAAAAMAAAAOAAAADgAAAA5sYXN0X3RpbWVzdGFtcAAAAAAABQAAAZfop8rAAAAADgAAAAZwZXJpb2QAAAAAAAUAAAAABSZcAAAAAA4AAAAKcmVzb2x1dGlvbgAAAAAAAwAEk+AAAAASAAAAAQNsQWZ0O43FGKVwnNQb73Fb8k8DG+dEYKpzAL3nWeMVAAAAAwAAAAIAAAASAAAAASx+XZGC/gTkVyJrE52T9j+XlFAUlLQVK9gqiDRdnKtlAAAAAwAAAAAAAAASAAAAATg8JlE3zvrN6cgQ9tBbokUCZ53xnrxXEdIBMQQPnCvqAAAAAwAAAAQAAAASAAAAAUERMTiMWywKwo7JTTyHAexwihJiFQRSQ7R2FXxBE/2tAAAAAwAAAAUAAAASAAAAAYKGr5MUKkg3UNGd70ZcFagIoILJEg+muIO2apeLN46WAAAAAwAAAAYAAAASAAAAAacK2ThyqJTKc1J4I6VTdH7z+nkAApp31L3ISawah04TAAAAAwAAAAMAAAASAAAAAdJdJghrv2iW4dAAdbmlG96OM3bVGdmc0IfSxI0ETgXBAAAAAwAAAAEAAAAAAAAAAQAFJXgAAAAGAAAAAAAAAAEqt/Rn0ZL8sq76E44Krh9ZYhZpLV49YxosLugeJjq4PwAAABQAAAABAAAAEwAAAADaZ5h4OOy0NoTgqFsSMHHBZ2BWo+ttPZwC2FftqORNwwAAAAEAAAAPAAAADgAAAAVhZG1pbgAAAAAAABIAAAAAAAAAAJYNE2uA3gelZ8DYHsfdBIy23sZIr8nf9wf6L9Zp/jTpAAAADgAAAAphc3NldF90dGxzAAAAAAAQAAAAAQAAAAAAAAAOAAAABmFzc2V0cwAAAAAAEAAAAAEAAAAHAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABLH5dkYL+BORXImsTnZP2P5eUUBSUtBUr2CqINF2cq2UAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAHSXSYIa79oluHQAHW5pRvejjN21RnZnNCH0sSNBE4FwQAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAAQNsQWZ0O43FGKVwnNQb73Fb8k8DG+dEYKpzAL3nWeMVAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABpwrZOHKolMpzUngjpVN0fvP6eQACmnfUvchJrBqHThMAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAE4PCZRN876zenIEPbQW6JFAmed8Z68VxHSATEED5wr6gAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAAUERMTiMWywKwo7JTTyHAexwihJiFQRSQ7R2FXxBE/2tAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABgoavkxQqSDdQ0Z3vRlwVqAiggskSD6a4g7Zql4s3jpYAAAAOAAAACmJhc2VfYXNzZXQAAAAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAATRO7qcufYlaCCIeG6YGn6tt1Va2Xd726owvhPtmIFKTAAAADgAAAAhkZWNpbWFscwAAAAMAAAAOAAAADgAAAA5sYXN0X3RpbWVzdGFtcAAAAAAABQAAAZforF6gAAAADgAAAAZwZXJpb2QAAAAAAAUAAAAABSZcAAAAAA4AAAAKcmVzb2x1dGlvbgAAAAAAAwAEk+AAAAASAAAAAQNsQWZ0O43FGKVwnNQb73Fb8k8DG+dEYKpzAL3nWeMVAAAAAwAAAAIAAAASAAAAASx+XZGC/gTkVyJrE52T9j+XlFAUlLQVK9gqiDRdnKtlAAAAAwAAAAAAAAASAAAAATg8JlE3zvrN6cgQ9tBbokUCZ53xnrxXEdIBMQQPnCvqAAAAAwAAAAQAAAASAAAAAUERMTiMWywKwo7JTTyHAexwihJiFQRSQ7R2FXxBE/2tAAAAAwAAAAUAAAASAAAAAYKGr5MUKkg3UNGd70ZcFagIoILJEg+muIO2apeLN46WAAAAAwAAAAYAAAASAAAAAacK2ThyqJTKc1J4I6VTdH7z+nkAApp31L3ISawah04TAAAAAwAAAAMAAAASAAAAAdJdJghrv2iW4dAAdbmlG96OM3bVGdmc0IfSxI0ETgXBAAAAAwAAAAEAAAAAAAAAAAAFJXgAAAAJRB4HfTX+gh+4blV53fjKVsJ3af9ktmY+eVlEh/d6rJgABWj5AAAAAAAAAAAABSV4AAAABgAAAAAAAAABKrf0Z9GS/LKu+hOOCq4fWWIWaS1ePWMaLC7oHiY6uD8AAAAJAAABl+isXqAAAAAAAAAABAAAAAAAAAAKAAAAAAAAAAAAAAAKQaE8tQAAAAAAAAAAAAUleAAAAAlTk2Isx+HESCcyRfNCFOiK9B8bryCkXntYex9i2xerXAAFaPkAAAAAAAAAAAAFJXgAAAAGAAAAAAAAAAEqt/Rn0ZL8sq76E44Krh9ZYhZpLV49YxosLugeJjq4PwAAAAkAAAGX6KxeoAAAAAAAAAAGAAAAAAAAAAoAAAAAAAAAAAAAYLyUqAn+AAAAAAAAAAAABSV4AAAABgAAAAAAAAABKrf0Z9GS/LKu+hOOCq4fWWIWaS1ePWMaLC7oHiY6uD8AAAAJAAABl+isXqAAAAAAAAAABQAAAAAAAAAKAAAAAAAAAAAAAAASRzQWKwAAAAAAAAAAAAUleAAAAAYAAAAAAAAAASq39GfRkvyyrvoTjgquH1liFmktXj1jGiwu6B4mOrg/AAAACQAAAZforF6gAAAAAAAAAAMAAAAAAAAACgAAAAAAAAAAAAAAGXAeu6MAAAAAAAAAAAAFJXgAAAAJb10K4vAg2FMNYDYJPGj0A8Bq0N8tVLsivGFWnKWRlQ0ABWj5AAAAAAAAAAAABSV4AAAACRp0CfdyyxTguzTsyyDMIMf59bXkAsJ4BQHWh7aDOrEvAAVo+QAAAAAAAAAAAAUleAAAAAYAAAAAAAAAASq39GfRkvyyrvoTjgquH1liFmktXj1jGiwu6B4mOrg/AAAACQAAAZforF6gAAAAAAAAAAEAAAAAAAAACgAAAAAAAAAAAAAAFAjvQXUAAAAAAAAAAAAFJXgAAAAGAAAAAAAAAAEqt/Rn0ZL8sq76E44Krh9ZYhZpLV49YxosLugeJjq4PwAAAAkAAAGX6KxeoAAAAAAAAAACAAAAAAAAAAoAAAAAAAAAAAAAWvLhNpYXAAAAAAAAAAAABSV4AAAACXgGZlWaxEkY9Fou1Sux2Kr347xqlEECbgm/bYOHoMCyAAVo+QAAAAAAAAAAAAUleAAAAAmW36YQGgajHLVN9gVIWHPl+aLklfo7/rIc1HpxoPcZyQAFaPkAAAAAAAAAAQAAAAAAAAABKrf0Z9GS/LKu+hOOCq4fWWIWaS1ePWMaLC7oHiY6uD8AAAABAAAAAAAAAAMAAAAPAAAACXJlZmxlY3RvcgAAAAAAAA8AAAAGcHJpY2VzAAAAAAAPAAAABnVwZGF0ZQAAAAAAEAAAAAEAAAAHAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABLH5dkYL+BORXImsTnZP2P5eUUBSUtBUr2CqINF2cq2UAAAAKAAAAAAAAAAAAAAAAAAAAAAAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAAdJdJghrv2iW4dAAdbmlG96OM3bVGdmc0IfSxI0ETgXBAAAACgAAAAAAAAAAAAAAFAjvQXUAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAEDbEFmdDuNxRilcJzUG+9xW/JPAxvnRGCqcwC951njFQAAAAoAAAAAAAAAAAAAWvLhNpYXAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABpwrZOHKolMpzUngjpVN0fvP6eQACmnfUvchJrBqHThMAAAAKAAAAAAAAAAAAAAAZcB67owAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAATg8JlE3zvrN6cgQ9tBbokUCZ53xnrxXEdIBMQQPnCvqAAAACgAAAAAAAAAAAAAACkGhPLUAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAFBETE4jFssCsKOyU08hwHscIoSYhUEUkO0dhV8QRP9rQAAAAoAAAAAAAAAAAAAABJHNBYrAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABgoavkxQqSDdQ0Z3vRlwVqAiggskSD6a4g7Zql4s3jpYAAAAKAAAAAAAAAAAAAGC8lKgJ/gAAAAIAAAADAAUleAAAAAAAAAAAlg0Ta4DeB6VnwNgex90EjLbexkivyd/3B/ov1mn+NOkAAAAWyuwbMQAADWoAABXEAAAAAQAAAAAAAAAAAAAAAAABAQEAAAABAAAAAKEzmyDCEh3IjCpyAIP1/BAE1iP+jHgDDTniFDHMpdlgAAAAAQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAQAAAAAAAAADAAAAAAAFJXgAAAAAaGy3fAAAAAAAAAABAAUleAAAAAAAAAAAlg0Ta4DeB6VnwNgex90EjLbexkivyd/3B/ov1mn+NOkAAAAWy38KpwAADWoAABXEAAAAAQAAAAAAAAAAAAAAAAABAQEAAAABAAAAAKEzmyDCEh3IjCpyAIP1/BAE1iP+jHgDDTniFDHMpdlgAAAAAQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAQAAAAAAAAADAAAAAAAFJXgAAAAAaGy3fAAAAAAAAAABAAAAAQAAAAAAAAAAAAQl+gAAAAAAAYEQAAAAAAABYcgAAAABAAAAAQAAAAIAAAAAAAAAAAAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAAAEAAAAAAAAAAgAAAA8AAAADZmVlAAAAABIAAAAAAAAAAJYNE2uA3gelZ8DYHsfdBIy23sZIr8nf9wf6L9Zp/jTpAAAACgAAAAAAAAAAAAAAAACYluQAAAABAAAAAAAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAAAEAAAAAAAAAAgAAAA8AAAADZmVlAAAAABIAAAAAAAAAAJYNE2uA3gelZ8DYHsfdBIy23sZIr8nf9wf6L9Zp/jTpAAAACv////////////////9tEIoAAAAWAAAAAQAAAAAAAAAAAAAAAgAAAAAAAAADAAAADwAAAAdmbl9jYWxsAAAAAA0AAAAgKrf0Z9GS/LKu+hOOCq4fWWIWaS1ePWMaLC7oHiY6uD8AAAAPAAAACXNldF9wcmljZQAAAAAAABAAAAABAAAAAgAAABAAAAABAAAABwAAAAoAAAAAAAAAAAAAAAAAAAAAAAAACgAAAAAAAAAAAAAAFAjvQXUAAAAKAAAAAAAAAAAAAFry4TaWFwAAAAoAAAAAAAAAAAAAABlwHrujAAAACgAAAAAAAAAAAAAACkGhPLUAAAAKAAAAAAAAAAAAAAASRzQWKwAAAAoAAAAAAAAAAAAAYLyUqAn+AAAABQAAAZforF6gAAAAAQAAAAAAAAABKrf0Z9GS/LKu+hOOCq4fWWIWaS1ePWMaLC7oHiY6uD8AAAABAAAAAAAAAAMAAAAPAAAACXJlZmxlY3RvcgAAAAAAAA8AAAAGcHJpY2VzAAAAAAAPAAAABnVwZGF0ZQAAAAAAEAAAAAEAAAAHAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABLH5dkYL+BORXImsTnZP2P5eUUBSUtBUr2CqINF2cq2UAAAAKAAAAAAAAAAAAAAAAAAAAAAAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAAdJdJghrv2iW4dAAdbmlG96OM3bVGdmc0IfSxI0ETgXBAAAACgAAAAAAAAAAAAAAFAjvQXUAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAEDbEFmdDuNxRilcJzUG+9xW/JPAxvnRGCqcwC951njFQAAAAoAAAAAAAAAAAAAWvLhNpYXAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABpwrZOHKolMpzUngjpVN0fvP6eQACmnfUvchJrBqHThMAAAAKAAAAAAAAAAAAAAAZcB67owAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAATg8JlE3zvrN6cgQ9tBbokUCZ53xnrxXEdIBMQQPnCvqAAAACgAAAAAAAAAAAAAACkGhPLUAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAFBETE4jFssCsKOyU08hwHscIoSYhUEUkO0dhV8QRP9rQAAAAoAAAAAAAAAAAAAABJHNBYrAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABgoavkxQqSDdQ0Z3vRlwVqAiggskSD6a4g7Zql4s3jpYAAAAKAAAAAAAAAAAAAGC8lKgJ/gAAAAEAAAAAAAAAASq39GfRkvyyrvoTjgquH1liFmktXj1jGiwu6B4mOrg/AAAAAgAAAAAAAAACAAAADwAAAAlmbl9yZXR1cm4AAAAAAAAPAAAACXNldF9wcmljZQAAAAAAAAEAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAKcmVhZF9lbnRyeQAAAAAABQAAAAAAAAAIAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAC3dyaXRlX2VudHJ5AAAAAAUAAAAAAAAABwAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAABBsZWRnZXJfcmVhZF9ieXRlAAAABQAAAAAAAFhgAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEWxlZGdlcl93cml0ZV9ieXRlAAAAAAAABQAAAAAAAAccAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADXJlYWRfa2V5X2J5dGUAAAAAAAAFAAAAAAAAAdQAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAOd3JpdGVfa2V5X2J5dGUAAAAAAAUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAAA5yZWFkX2RhdGFfYnl0ZQAAAAAABQAAAAAAAATcAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD3dyaXRlX2RhdGFfYnl0ZQAAAAAFAAAAAAAABxwAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAOcmVhZF9jb2RlX2J5dGUAAAAAAAUAAAAAAABThAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAAA93cml0ZV9jb2RlX2J5dGUAAAAABQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACmVtaXRfZXZlbnQAAAAAAAUAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAAA9lbWl0X2V2ZW50X2J5dGUAAAAABQAAAAAAAAMwAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACGNwdV9pbnNuAAAABQAAAAAARc1cAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACG1lbV9ieXRlAAAABQAAAAAAIBuIAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEWludm9rZV90aW1lX25zZWNzAAAAAAAABQAAAAAAGWpZAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD21heF9yd19rZXlfYnl0ZQAAAAAFAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAQbWF4X3J3X2RhdGFfYnl0ZQAAAAUAAAAAAAAE3AAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAABBtYXhfcndfY29kZV9ieXRlAAAABQAAAAAAAFOEAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAE21heF9lbWl0X2V2ZW50X2J5dGUAAAAABQAAAAAAAAMw",
+        "diagnosticEventsXdr": [
+          "AAAAAQAAAAAAAAAAAAAAAgAAAAAAAAADAAAADwAAAAdmbl9jYWxsAAAAAA0AAAAgKrf0Z9GS/LKu+hOOCq4fWWIWaS1ePWMaLC7oHiY6uD8AAAAPAAAACXNldF9wcmljZQAAAAAAABAAAAABAAAAAgAAABAAAAABAAAABwAAAAoAAAAAAAAAAAAAAAAAAAAAAAAACgAAAAAAAAAAAAAAFAjvQXUAAAAKAAAAAAAAAAAAAFry4TaWFwAAAAoAAAAAAAAAAAAAABlwHrujAAAACgAAAAAAAAAAAAAACkGhPLUAAAAKAAAAAAAAAAAAAAASRzQWKwAAAAoAAAAAAAAAAAAAYLyUqAn+AAAABQAAAZforF6g",
+          "AAAAAQAAAAAAAAABKrf0Z9GS/LKu+hOOCq4fWWIWaS1ePWMaLC7oHiY6uD8AAAABAAAAAAAAAAMAAAAPAAAACXJlZmxlY3RvcgAAAAAAAA8AAAAGcHJpY2VzAAAAAAAPAAAABnVwZGF0ZQAAAAAAEAAAAAEAAAAHAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABLH5dkYL+BORXImsTnZP2P5eUUBSUtBUr2CqINF2cq2UAAAAKAAAAAAAAAAAAAAAAAAAAAAAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAAdJdJghrv2iW4dAAdbmlG96OM3bVGdmc0IfSxI0ETgXBAAAACgAAAAAAAAAAAAAAFAjvQXUAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAEDbEFmdDuNxRilcJzUG+9xW/JPAxvnRGCqcwC951njFQAAAAoAAAAAAAAAAAAAWvLhNpYXAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABpwrZOHKolMpzUngjpVN0fvP6eQACmnfUvchJrBqHThMAAAAKAAAAAAAAAAAAAAAZcB67owAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAATg8JlE3zvrN6cgQ9tBbokUCZ53xnrxXEdIBMQQPnCvqAAAACgAAAAAAAAAAAAAACkGhPLUAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAFBETE4jFssCsKOyU08hwHscIoSYhUEUkO0dhV8QRP9rQAAAAoAAAAAAAAAAAAAABJHNBYrAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABgoavkxQqSDdQ0Z3vRlwVqAiggskSD6a4g7Zql4s3jpYAAAAKAAAAAAAAAAAAAGC8lKgJ/g==",
+          "AAAAAQAAAAAAAAABKrf0Z9GS/LKu+hOOCq4fWWIWaS1ePWMaLC7oHiY6uD8AAAACAAAAAAAAAAIAAAAPAAAACWZuX3JldHVybgAAAAAAAA8AAAAJc2V0X3ByaWNlAAAAAAAAAQ==",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACnJlYWRfZW50cnkAAAAAAAUAAAAAAAAACA==",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAC3dyaXRlX2VudHJ5AAAAAAUAAAAAAAAABw==",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEGxlZGdlcl9yZWFkX2J5dGUAAAAFAAAAAAAAWGA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEWxlZGdlcl93cml0ZV9ieXRlAAAAAAAABQAAAAAAAAcc",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADXJlYWRfa2V5X2J5dGUAAAAAAAAFAAAAAAAAAdQ=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADndyaXRlX2tleV9ieXRlAAAAAAAFAAAAAAAAAAA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADnJlYWRfZGF0YV9ieXRlAAAAAAAFAAAAAAAABNw=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD3dyaXRlX2RhdGFfYnl0ZQAAAAAFAAAAAAAABxw=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADnJlYWRfY29kZV9ieXRlAAAAAAAFAAAAAAAAU4Q=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD3dyaXRlX2NvZGVfYnl0ZQAAAAAFAAAAAAAAAAA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACmVtaXRfZXZlbnQAAAAAAAUAAAAAAAAAAQ==",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD2VtaXRfZXZlbnRfYnl0ZQAAAAAFAAAAAAAAAzA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACGNwdV9pbnNuAAAABQAAAAAARc1c",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACG1lbV9ieXRlAAAABQAAAAAAIBuI",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEWludm9rZV90aW1lX25zZWNzAAAAAAAABQAAAAAAGWpZ",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD21heF9yd19rZXlfYnl0ZQAAAAAFAAAAAAAAAEA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEG1heF9yd19kYXRhX2J5dGUAAAAFAAAAAAAABNw=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEG1heF9yd19jb2RlX2J5dGUAAAAFAAAAAAAAU4Q=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAE21heF9lbWl0X2V2ZW50X2J5dGUAAAAABQAAAAAAAAMw"
+        ],
+        "events": {
+          "transactionEventsXdr": [
+            "AAAAAAAAAAAAAAAB15KLcsJwPM/q9+uf9O9NUEpVqLl5/JtFDqLIQrTRzmEAAAABAAAAAAAAAAIAAAAPAAAAA2ZlZQAAAAASAAAAAAAAAACWDRNrgN4HpWfA2B7H3QSMtt7GSK/J3/cH+i/Waf406QAAAAoAAAAAAAAAAAAAAAAAmJbk",
+            "AAAAAQAAAAAAAAAB15KLcsJwPM/q9+uf9O9NUEpVqLl5/JtFDqLIQrTRzmEAAAABAAAAAAAAAAIAAAAPAAAAA2ZlZQAAAAASAAAAAAAAAACWDRNrgN4HpWfA2B7H3QSMtt7GSK/J3/cH+i/Waf406QAAAAr/////////////////bRCK"
+          ],
+          "contractEventsXdr": [
+            [
+              "AAAAAAAAAAEqt/Rn0ZL8sq76E44Krh9ZYhZpLV49YxosLugeJjq4PwAAAAEAAAAAAAAAAwAAAA8AAAAJcmVmbGVjdG9yAAAAAAAADwAAAAZwcmljZXMAAAAAAA8AAAAGdXBkYXRlAAAAAAAQAAAAAQAAAAcAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAEsfl2Rgv4E5FciaxOdk/Y/l5RQFJS0FSvYKog0XZyrZQAAAAoAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAAB0l0mCGu/aJbh0AB1uaUb3o4zdtUZ2ZzQh9LEjQROBcEAAAAKAAAAAAAAAAAAAAAUCO9BdQAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAAQNsQWZ0O43FGKVwnNQb73Fb8k8DG+dEYKpzAL3nWeMVAAAACgAAAAAAAAAAAABa8uE2lhcAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAGnCtk4cqiUynNSeCOlU3R+8/p5AAKad9S9yEmsGodOEwAAAAoAAAAAAAAAAAAAABlwHrujAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABODwmUTfO+s3pyBD20FuiRQJnnfGevFcR0gExBA+cK+oAAAAKAAAAAAAAAAAAAAAKQaE8tQAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAAUERMTiMWywKwo7JTTyHAexwihJiFQRSQ7R2FXxBE/2tAAAACgAAAAAAAAAAAAAAEkc0FisAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAGChq+TFCpIN1DRne9GXBWoCKCCyRIPpriDtmqXizeOlgAAAAoAAAAAAAAAAAAAYLyUqAn+"
+            ]
+          ]
+        },
+        "ledger": 337272,
+        "createdAt": 1751955324
+      },
+      {
+        "status": "SUCCESS",
+        "txHash": "ad4e1293b32dfa1e9204892b64088d61465337abdf4c2eee2e9d0fa8095bf87a",
+        "applicationOrder": 5,
+        "feeBump": false,
+        "envelopeXdr": "AAAAAgAAAADuBg+afmvWN9+nlruudR93UO1rDpTe8i6yxgPgBKoBVwExLQAAAA2lAAAVwgAAAAEAAAAAAAAAAAAAAABobLeMAAAAAAAAAAEAAAABAAAAAO4GD5p+a9Y336eWu651H3dQ7WsOlN7yLrLGA+AEqgFXAAAAGAAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAJc2V0X3ByaWNlAAAAAAAAAgAAABAAAAABAAAACQAAAAoAAAAAAAAAAAAAar7vtc6AAAAACgAAAAAAAAAAAAB77nns4IAAAAAKAAAAAAAAAAAAAHIYVPMbgAAAAAoAAAAAAAAAAAAAQpzRyeGAAAAACgAAAAAAAAAAAAAE4WY2fkAAAAAKAAAAAAAAAAAAAAASduMCAAAAAAoAAAAAAAAAAAAAEKOEVuGAAAAACgAAAAAAAAAAAAACzMdm/4AAAAAKAAAAAAAAAAAEoCi1tZQ/gAAAAAUAAAGX6KxeoAAAAAEAAAAAAAAAAAAAAAGlJx5hXtZLUEEJA9akotOUWIv8dYiEoyuKQmACnKsp1gAAAAlzZXRfcHJpY2UAAAAAAAACAAAAEAAAAAEAAAAJAAAACgAAAAAAAAAAAABqvu+1zoAAAAAKAAAAAAAAAAAAAHvueezggAAAAAoAAAAAAAAAAAAAchhU8xuAAAAACgAAAAAAAAAAAABCnNHJ4YAAAAAKAAAAAAAAAAAAAAThZjZ+QAAAAAoAAAAAAAAAAAAAABJ24wIAAAAACgAAAAAAAAAAAAAQo4RW4YAAAAAKAAAAAAAAAAAAAALMx2b/gAAAAAoAAAAAAAAAAASgKLW1lD+AAAAABQAAAZforF6gAAAAAAAAAAEAAAAAAAAAAQAAAAfaZ5h4OOy0NoTgqFsSMHHBZ2BWo+ttPZwC2FftqORNwwAAAAoAAAAGAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAACQAAAZforF6gAAAAAAAAAAAAAAAAAAAABgAAAAGlJx5hXtZLUEEJA9akotOUWIv8dYiEoyuKQmACnKsp1gAAAAkAAAGX6KxeoAAAAAAAAAABAAAAAAAAAAYAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAJAAABl+isXqAAAAAAAAAAAgAAAAAAAAAGAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAACQAAAZforF6gAAAAAAAAAAMAAAAAAAAABgAAAAGlJx5hXtZLUEEJA9akotOUWIv8dYiEoyuKQmACnKsp1gAAAAkAAAGX6KxeoAAAAAAAAAAEAAAAAAAAAAYAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAJAAABl+isXqAAAAAAAAAABQAAAAAAAAAGAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAACQAAAZforF6gAAAAAAAAAAYAAAAAAAAABgAAAAGlJx5hXtZLUEEJA9akotOUWIv8dYiEoyuKQmACnKsp1gAAAAkAAAGX6KxeoAAAAAAAAAAHAAAAAAAAAAYAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAJAAABl+isXqAAAAAAAAAACAAAAAAAAAAGAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAAFAAAAAEAmJaAAACcQAAAC7gAAAAAAJiWgAAAAAHMpdlgAAAAQEgm+1bCDSJvdFDSnyeZmEPiZMhmwZmivK2nygo7vIaoIcb88CZBs6VAKQweX0EGp54vhFUUTIK6z0cTSJtZMwo=",
+        "resultXdr": "AAAAAAAHMRAAAAAAAAAAAQAAAAAAAAAYAAAAABEOa41BV0w6YargAzlyRUm7wx575S/rr4HPaL54Gz8aAAAAAA==",
+        "resultMetaXdr": "AAAABAAAAAAAAAACAAAAAwAFJXgAAAAAAAAAAO4GD5p+a9Y336eWu651H3dQ7WsOlN7yLrLGA+AEqgFXAAAAFqvoAosAAA2lAAAVwQAAAAEAAAAAAAAAAAAAAAAAAQEBAAAAAQAAAAChM5sgwhIdyIwqcgCD9fwQBNYj/ox4Aw054hQxzKXZYAAAAAEAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAEAAAAAAAAAAwAAAAAABSU8AAAAAGhstlAAAAAAAAAAAQAFJXgAAAAAAAAAAO4GD5p+a9Y336eWu651H3dQ7WsOlN7yLrLGA+AEqgFXAAAAFqvoAosAAA2lAAAVwgAAAAEAAAAAAAAAAAAAAAAAAQEBAAAAAQAAAAChM5sgwhIdyIwqcgCD9fwQBNYj/ox4Aw054hQxzKXZYAAAAAEAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAEAAAAAAAAAAwAAAAAABSV4AAAAAGhst3wAAAAAAAAAAQAAAAAAAAAUAAAAAAAFJXgAAAAJTFJ7hg0YekCP6O62XQDcF34hNHlC6Yogiee9kKZaq54ABWj5AAAAAAAAAAAABSV4AAAABgAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAJAAABl+isXqAAAAAAAAAABwAAAAAAAAAKAAAAAAAAAAAAAALMx2b/gAAAAAAAAAAAAAUleAAAAAYAAAAAAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAACQAAAZforF6gAAAAAAAAAAYAAAAAAAAACgAAAAAAAAAAAAAQo4RW4YAAAAAAAAAAAwAFJTwAAAAGAAAAAAAAAAGlJx5hXtZLUEEJA9akotOUWIv8dYiEoyuKQmACnKsp1gAAABQAAAABAAAAEwAAAADaZ5h4OOy0NoTgqFsSMHHBZ2BWo+ttPZwC2FftqORNwwAAAAEAAAARAAAADgAAAAVhZG1pbgAAAAAAABIAAAAAAAAAAO4GD5p+a9Y336eWu651H3dQ7WsOlN7yLrLGA+AEqgFXAAAADgAAAAphc3NldF90dGxzAAAAAAAQAAAAAQAAAAAAAAAOAAAABmFzc2V0cwAAAAAAEAAAAAEAAAAJAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRVVSAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA0dCUAAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANDSEYAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQ0FEAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA01YTgAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANBUlMAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQlJMAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA1RIQgAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANYQVUAAAAADgAAAApiYXNlX2Fzc2V0AAAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANVU0QAAAAADgAAAAhkZWNpbWFscwAAAAMAAAAOAAAADgAAAA5sYXN0X3RpbWVzdGFtcAAAAAAABQAAAZfop8rAAAAADgAAAAZwZXJpb2QAAAAAAAUAAAAABSZcAAAAAA4AAAAKcmVzb2x1dGlvbgAAAAAAAwAEk+AAAAAPAAAAA0FSUwAAAAADAAAABQAAAA8AAAADQlJMAAAAAAMAAAAGAAAADwAAAANDQUQAAAAAAwAAAAMAAAAPAAAAA0NIRgAAAAADAAAAAgAAAA8AAAADRVVSAAAAAAMAAAAAAAAADwAAAANHQlAAAAAAAwAAAAEAAAAPAAAAA01YTgAAAAADAAAABAAAAA8AAAADVEhCAAAAAAMAAAAHAAAADwAAAANYQVUAAAAAAwAAAAgAAAAAAAAAAQAFJXgAAAAGAAAAAAAAAAGlJx5hXtZLUEEJA9akotOUWIv8dYiEoyuKQmACnKsp1gAAABQAAAABAAAAEwAAAADaZ5h4OOy0NoTgqFsSMHHBZ2BWo+ttPZwC2FftqORNwwAAAAEAAAARAAAADgAAAAVhZG1pbgAAAAAAABIAAAAAAAAAAO4GD5p+a9Y336eWu651H3dQ7WsOlN7yLrLGA+AEqgFXAAAADgAAAAphc3NldF90dGxzAAAAAAAQAAAAAQAAAAAAAAAOAAAABmFzc2V0cwAAAAAAEAAAAAEAAAAJAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRVVSAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA0dCUAAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANDSEYAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQ0FEAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA01YTgAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANBUlMAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQlJMAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA1RIQgAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANYQVUAAAAADgAAAApiYXNlX2Fzc2V0AAAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANVU0QAAAAADgAAAAhkZWNpbWFscwAAAAMAAAAOAAAADgAAAA5sYXN0X3RpbWVzdGFtcAAAAAAABQAAAZforF6gAAAADgAAAAZwZXJpb2QAAAAAAAUAAAAABSZcAAAAAA4AAAAKcmVzb2x1dGlvbgAAAAAAAwAEk+AAAAAPAAAAA0FSUwAAAAADAAAABQAAAA8AAAADQlJMAAAAAAMAAAAGAAAADwAAAANDQUQAAAAAAwAAAAMAAAAPAAAAA0NIRgAAAAADAAAAAgAAAA8AAAADRVVSAAAAAAMAAAAAAAAADwAAAANHQlAAAAAAAwAAAAEAAAAPAAAAA01YTgAAAAADAAAABAAAAA8AAAADVEhCAAAAAAMAAAAHAAAADwAAAANYQVUAAAAAAwAAAAgAAAAAAAAAAAAFJXgAAAAJTBIOCKbv/+1/9CYra1RMqev8t31JP4xtN3HQcrApd+gABWj5AAAAAAAAAAAABSV4AAAABgAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAJAAABl+isXqAAAAAAAAAAAQAAAAAAAAAKAAAAAAAAAAAAAHvueezggAAAAAAAAAAAAAUleAAAAAYAAAAAAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAACQAAAZforF6gAAAAAAAAAAUAAAAAAAAACgAAAAAAAAAAAAAAEnbjAgAAAAAAAAAAAAAFJXgAAAAJrs0QqhKj1rGtzDDrF15UcZKQAMrbnL3cpKU2JJXi7f4ABWj5AAAAAAAAAAAABSV4AAAACbWHiKy0lbSAGDTH1wkwUqR3TQ/Fg1L2IaQ1dmFWkEh2AAVo+QAAAAAAAAAAAAUleAAAAAYAAAAAAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAACQAAAZforF6gAAAAAAAAAAQAAAAAAAAACgAAAAAAAAAAAAAE4WY2fkAAAAAAAAAAAAAFJXgAAAAJh003w9kt+aRpwy9fdIdAVbAqe351EmUps1Dn+AW9rl0ABWj5AAAAAAAAAAAABSV4AAAACRwH6p7HoKpXDI9DS/+TgFAaiv9Jq3RM0QEqG21MQUPOAAVo+QAAAAAAAAAAAAUleAAAAAYAAAAAAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAACQAAAZforF6gAAAAAAAAAAgAAAAAAAAACgAAAAAAAAAABKAotbWUP4AAAAAAAAAAAAAFJXgAAAAJypa225pMujmRlDXUPQYIw16s5NkjCTCg2v5MS7besVUABWj5AAAAAAAAAAAABSV4AAAABgAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAJAAABl+isXqAAAAAAAAAAAAAAAAAAAAAKAAAAAAAAAAAAAGq+77XOgAAAAAAAAAAAAAUleAAAAAYAAAAAAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAACQAAAZforF6gAAAAAAAAAAIAAAAAAAAACgAAAAAAAAAAAAByGFTzG4AAAAAAAAAAAAAFJXgAAAAJhyH7/lHoFoX7sLuNWBBBwviQCJidW44xkUo9hzgAVcYABWj5AAAAAAAAAAAABSV4AAAABgAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAJAAABl+isXqAAAAAAAAAAAwAAAAAAAAAKAAAAAAAAAAAAAEKc0cnhgAAAAAAAAAAAAAUleAAAAAkS+XxH4Tmpojq4OGNei7rBTadgDcosuDhnRMerOpeyfwAFaPkAAAAAAAAAAQAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAABAAAAAAAAAAMAAAAPAAAACXJlZmxlY3RvcgAAAAAAAA8AAAAGcHJpY2VzAAAAAAAPAAAABnVwZGF0ZQAAAAAAEAAAAAEAAAAJAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRVVSAAAAAAoAAAAAAAAAAAAAar7vtc6AAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADR0JQAAAAAAoAAAAAAAAAAAAAe+557OCAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQ0hGAAAAAAoAAAAAAAAAAAAAchhU8xuAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQ0FEAAAAAAoAAAAAAAAAAAAAQpzRyeGAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADTVhOAAAAAAoAAAAAAAAAAAAABOFmNn5AAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQVJTAAAAAAoAAAAAAAAAAAAAABJ24wIAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQlJMAAAAAAoAAAAAAAAAAAAAEKOEVuGAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADVEhCAAAAAAoAAAAAAAAAAAAAAszHZv+AAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADWEFVAAAAAAoAAAAAAAAAAASgKLW1lD+AAAAAAgAAAAMABSV4AAAAAAAAAADuBg+afmvWN9+nlruudR93UO1rDpTe8i6yxgPgBKoBVwAAABar6AKLAAANpQAAFcIAAAABAAAAAAAAAAAAAAAAAAEBAQAAAAEAAAAAoTObIMISHciMKnIAg/X8EATWI/6MeAMNOeIUMcyl2WAAAAABAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAAAAAABAAAAAAAAAAMAAAAAAAUleAAAAABobLd8AAAAAAAAAAEABSV4AAAAAAAAAADuBg+afmvWN9+nlruudR93UO1rDpTe8i6yxgPgBKoBVwAAABaseWhfAAANpQAAFcIAAAABAAAAAAAAAAAAAAAAAAEBAQAAAAEAAAAAoTObIMISHciMKnIAg/X8EATWI/6MeAMNOeIUMcyl2WAAAAABAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAAAAAABAAAAAAAAAAMAAAAAAAUleAAAAABobLd8AAAAAAAAAAEAAAABAAAAAAAAAAAABQC0AAAAAAACL/gAAAAAAAISrAAAAAEAAAABAAAAAgAAAAAAAAAAAAAAAdeSi3LCcDzP6vfrn/TvTVBKVai5efybRQ6iyEK00c5hAAAAAQAAAAAAAAACAAAADwAAAANmZWUAAAAAEgAAAAAAAAAA7gYPmn5r1jffp5a7rnUfd1Dtaw6U3vIussYD4ASqAVcAAAAKAAAAAAAAAAAAAAAAAJiW5AAAAAEAAAAAAAAAAdeSi3LCcDzP6vfrn/TvTVBKVai5efybRQ6iyEK00c5hAAAAAQAAAAAAAAACAAAADwAAAANmZWUAAAAAEgAAAAAAAAAA7gYPmn5r1jffp5a7rnUfd1Dtaw6U3vIussYD4ASqAVcAAAAK/////////////////26aLAAAABYAAAABAAAAAAAAAAAAAAACAAAAAAAAAAMAAAAPAAAAB2ZuX2NhbGwAAAAADQAAACClJx5hXtZLUEEJA9akotOUWIv8dYiEoyuKQmACnKsp1gAAAA8AAAAJc2V0X3ByaWNlAAAAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAAJAAAACgAAAAAAAAAAAABqvu+1zoAAAAAKAAAAAAAAAAAAAHvueezggAAAAAoAAAAAAAAAAAAAchhU8xuAAAAACgAAAAAAAAAAAABCnNHJ4YAAAAAKAAAAAAAAAAAAAAThZjZ+QAAAAAoAAAAAAAAAAAAAABJ24wIAAAAACgAAAAAAAAAAAAAQo4RW4YAAAAAKAAAAAAAAAAAAAALMx2b/gAAAAAoAAAAAAAAAAASgKLW1lD+AAAAABQAAAZforF6gAAAAAQAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAABAAAAAAAAAAMAAAAPAAAACXJlZmxlY3RvcgAAAAAAAA8AAAAGcHJpY2VzAAAAAAAPAAAABnVwZGF0ZQAAAAAAEAAAAAEAAAAJAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRVVSAAAAAAoAAAAAAAAAAAAAar7vtc6AAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADR0JQAAAAAAoAAAAAAAAAAAAAe+557OCAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQ0hGAAAAAAoAAAAAAAAAAAAAchhU8xuAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQ0FEAAAAAAoAAAAAAAAAAAAAQpzRyeGAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADTVhOAAAAAAoAAAAAAAAAAAAABOFmNn5AAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQVJTAAAAAAoAAAAAAAAAAAAAABJ24wIAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQlJMAAAAAAoAAAAAAAAAAAAAEKOEVuGAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADVEhCAAAAAAoAAAAAAAAAAAAAAszHZv+AAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADWEFVAAAAAAoAAAAAAAAAAASgKLW1lD+AAAAAAQAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAACAAAAAAAAAAIAAAAPAAAACWZuX3JldHVybgAAAAAAAA8AAAAJc2V0X3ByaWNlAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAAApyZWFkX2VudHJ5AAAAAAAFAAAAAAAAAAsAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAALd3JpdGVfZW50cnkAAAAABQAAAAAAAAAKAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEGxlZGdlcl9yZWFkX2J5dGUAAAAFAAAAAAAAVzQAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAARbGVkZ2VyX3dyaXRlX2J5dGUAAAAAAAAFAAAAAAAABxAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAANcmVhZF9rZXlfYnl0ZQAAAAAAAAUAAAAAAAAClAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAAA53cml0ZV9rZXlfYnl0ZQAAAAAABQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADnJlYWRfZGF0YV9ieXRlAAAAAAAFAAAAAAAAA7AAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAPd3JpdGVfZGF0YV9ieXRlAAAAAAUAAAAAAAAHEAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAAA5yZWFkX2NvZGVfYnl0ZQAAAAAABQAAAAAAAFOEAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD3dyaXRlX2NvZGVfYnl0ZQAAAAAFAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAKZW1pdF9ldmVudAAAAAAABQAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD2VtaXRfZXZlbnRfYnl0ZQAAAAAFAAAAAAAAAvwAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAIY3B1X2luc24AAAAFAAAAAABImEoAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAIbWVtX2J5dGUAAAAFAAAAAAAhGTIAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAARaW52b2tlX3RpbWVfbnNlY3MAAAAAAAAFAAAAAAAW5iQAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAPbWF4X3J3X2tleV9ieXRlAAAAAAUAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAABBtYXhfcndfZGF0YV9ieXRlAAAABQAAAAAAAAOwAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEG1heF9yd19jb2RlX2J5dGUAAAAFAAAAAAAAU4QAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAATbWF4X2VtaXRfZXZlbnRfYnl0ZQAAAAAFAAAAAAAAAvw=",
+        "diagnosticEventsXdr": [
+          "AAAAAQAAAAAAAAAAAAAAAgAAAAAAAAADAAAADwAAAAdmbl9jYWxsAAAAAA0AAAAgpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAPAAAACXNldF9wcmljZQAAAAAAABAAAAABAAAAAgAAABAAAAABAAAACQAAAAoAAAAAAAAAAAAAar7vtc6AAAAACgAAAAAAAAAAAAB77nns4IAAAAAKAAAAAAAAAAAAAHIYVPMbgAAAAAoAAAAAAAAAAAAAQpzRyeGAAAAACgAAAAAAAAAAAAAE4WY2fkAAAAAKAAAAAAAAAAAAAAASduMCAAAAAAoAAAAAAAAAAAAAEKOEVuGAAAAACgAAAAAAAAAAAAACzMdm/4AAAAAKAAAAAAAAAAAEoCi1tZQ/gAAAAAUAAAGX6KxeoA==",
+          "AAAAAQAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAABAAAAAAAAAAMAAAAPAAAACXJlZmxlY3RvcgAAAAAAAA8AAAAGcHJpY2VzAAAAAAAPAAAABnVwZGF0ZQAAAAAAEAAAAAEAAAAJAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRVVSAAAAAAoAAAAAAAAAAAAAar7vtc6AAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADR0JQAAAAAAoAAAAAAAAAAAAAe+557OCAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQ0hGAAAAAAoAAAAAAAAAAAAAchhU8xuAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQ0FEAAAAAAoAAAAAAAAAAAAAQpzRyeGAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADTVhOAAAAAAoAAAAAAAAAAAAABOFmNn5AAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQVJTAAAAAAoAAAAAAAAAAAAAABJ24wIAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQlJMAAAAAAoAAAAAAAAAAAAAEKOEVuGAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADVEhCAAAAAAoAAAAAAAAAAAAAAszHZv+AAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADWEFVAAAAAAoAAAAAAAAAAASgKLW1lD+A",
+          "AAAAAQAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAACAAAAAAAAAAIAAAAPAAAACWZuX3JldHVybgAAAAAAAA8AAAAJc2V0X3ByaWNlAAAAAAAAAQ==",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACnJlYWRfZW50cnkAAAAAAAUAAAAAAAAACw==",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAC3dyaXRlX2VudHJ5AAAAAAUAAAAAAAAACg==",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEGxlZGdlcl9yZWFkX2J5dGUAAAAFAAAAAAAAVzQ=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEWxlZGdlcl93cml0ZV9ieXRlAAAAAAAABQAAAAAAAAcQ",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADXJlYWRfa2V5X2J5dGUAAAAAAAAFAAAAAAAAApQ=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADndyaXRlX2tleV9ieXRlAAAAAAAFAAAAAAAAAAA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADnJlYWRfZGF0YV9ieXRlAAAAAAAFAAAAAAAAA7A=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD3dyaXRlX2RhdGFfYnl0ZQAAAAAFAAAAAAAABxA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADnJlYWRfY29kZV9ieXRlAAAAAAAFAAAAAAAAU4Q=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD3dyaXRlX2NvZGVfYnl0ZQAAAAAFAAAAAAAAAAA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACmVtaXRfZXZlbnQAAAAAAAUAAAAAAAAAAQ==",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD2VtaXRfZXZlbnRfYnl0ZQAAAAAFAAAAAAAAAvw=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACGNwdV9pbnNuAAAABQAAAAAASJhK",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACG1lbV9ieXRlAAAABQAAAAAAIRky",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEWludm9rZV90aW1lX25zZWNzAAAAAAAABQAAAAAAFuYk",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD21heF9yd19rZXlfYnl0ZQAAAAAFAAAAAAAAAEA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEG1heF9yd19kYXRhX2J5dGUAAAAFAAAAAAAAA7A=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEG1heF9yd19jb2RlX2J5dGUAAAAFAAAAAAAAU4Q=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAE21heF9lbWl0X2V2ZW50X2J5dGUAAAAABQAAAAAAAAL8"
+        ],
+        "events": {
+          "transactionEventsXdr": [
+            "AAAAAAAAAAAAAAAB15KLcsJwPM/q9+uf9O9NUEpVqLl5/JtFDqLIQrTRzmEAAAABAAAAAAAAAAIAAAAPAAAAA2ZlZQAAAAASAAAAAAAAAADuBg+afmvWN9+nlruudR93UO1rDpTe8i6yxgPgBKoBVwAAAAoAAAAAAAAAAAAAAAAAmJbk",
+            "AAAAAQAAAAAAAAAB15KLcsJwPM/q9+uf9O9NUEpVqLl5/JtFDqLIQrTRzmEAAAABAAAAAAAAAAIAAAAPAAAAA2ZlZQAAAAASAAAAAAAAAADuBg+afmvWN9+nlruudR93UO1rDpTe8i6yxgPgBKoBVwAAAAr/////////////////bpos"
+          ],
+          "contractEventsXdr": [
+            [
+              "AAAAAAAAAAGlJx5hXtZLUEEJA9akotOUWIv8dYiEoyuKQmACnKsp1gAAAAEAAAAAAAAAAwAAAA8AAAAJcmVmbGVjdG9yAAAAAAAADwAAAAZwcmljZXMAAAAAAA8AAAAGdXBkYXRlAAAAAAAQAAAAAQAAAAkAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANFVVIAAAAACgAAAAAAAAAAAABqvu+1zoAAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANHQlAAAAAACgAAAAAAAAAAAAB77nns4IAAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANDSEYAAAAACgAAAAAAAAAAAAByGFTzG4AAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANDQUQAAAAACgAAAAAAAAAAAABCnNHJ4YAAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANNWE4AAAAACgAAAAAAAAAAAAAE4WY2fkAAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANBUlMAAAAACgAAAAAAAAAAAAAAEnbjAgAAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANCUkwAAAAACgAAAAAAAAAAAAAQo4RW4YAAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANUSEIAAAAACgAAAAAAAAAAAAACzMdm/4AAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANYQVUAAAAACgAAAAAAAAAABKAotbWUP4A="
+            ]
+          ]
+        },
+        "ledger": 337272,
+        "createdAt": 1751955324
+      }
+    ],
+    "latestLedger": 353482,
+    "latestLedgerCloseTimestamp": 1752036440,
+    "oldestLedger": 337151,
+    "oldestLedgerCloseTimestamp": 1751954719,
+    "cursor": "1448572209876993"
+  }
+}
+```
+
+</Tab>
+<Tab title="Successful getTransactions Request Using Cursor">
+
+Query a list of transactions starting from the given cursor.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getTransactions",
+  "params": {
+    "pagination": {
+      "cursor": "1448572209676993",
+      "limit": 5
+    }
+  }
+}' \
+https://soroban-testnet.stellar.org | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "getTransactions",
+  params: {
+    pagination: {
+      cursor: "1448572209676993",
+      limit: 5,
+    },
+  },
+};
+let res = await fetch("https://soroban-testnet.stellar.org", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://soroban-testnet.stellar.org", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "getTransactions",
+    "params": {
+        "pagination": {
+            "cursor": "1448572209676993",
+            "limit": 5
+        }
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getTransactions",
+  "params": {
+    "pagination": {
+      "cursor": "1448572209676993",
+      "limit": 5
+    }
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "transactions": [
+      {
+        "status": "FAILED",
+        "txHash": "173d6022f8db9654f31c5aa53785385b913ed32baf8ee72f984b97a97bb0909b",
+        "applicationOrder": 1,
+        "feeBump": true,
+        "envelopeXdr": "AAAABQAAAAADKm0xr8jnLz7gKYk/CQg7DF6nkVnJNErPGZcXNDs4RwAAAAAB2j5AAAAAAgAAAAC/JkamGjlv1kc1tD/C4dJaB6vxgIfnQRZNEIndZH9mjAAAAAAAAEXVAAACNgAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAYAAAABAAAAAAMqbTGvyOcvPuApiT8JCDsMXqeRWck0Ss8Zlxc0OzhHAAAAEAAAAACWzQF4RyG733Ul+cJlgJ6N6SBHVKLGfBpdDzTLMleEBQAAAAEAAAAAAyptMa/I5y8+4CmJPwkIOwxep5FZyTRKzxmXFzQ7OEcAAAAAAAAAAJbNAXhHIbvfdSX5wmWAno3pIEdUosZ8Gl0PNMsyV4QFAAAAAAAAAAAAAAABAAAAAJbNAXhHIbvfdSX5wmWAno3pIEdUosZ8Gl0PNMsyV4QFAAAABgAAAAFVU0RDAAAAAEI+fQXy7K+/7BkrIVo/G+lq7bjY5wJUq+NBPgIH3layf/////////8AAAABAAAAAJbNAXhHIbvfdSX5wmWAno3pIEdUosZ8Gl0PNMsyV4QFAAAAEQAAAAEAAAAAAyptMa/I5y8+4CmJPwkIOwxep5FZyTRKzxmXFzQ7OEcAAAABAAAAAJbNAXhHIbvfdSX5wmWAno3pIEdUosZ8Gl0PNMsyV4QFAAAAAVVTREMAAAAAQj59BfLsr7/sGSshWj8b6WrtuNjnAlSr40E+AgfeVrIAAAJMmJoCQAAAAAEAAAAAls0BeEchu991JfnCZYCejekgR1SixnwaXQ80yzJXhAUAAAABAAAAAAMqbTGvyOcvPuApiT8JCDsMXqeRWck0Ss8Zlxc0OzhHAAAAAVVTREMAAAAAQj59BfLsr7/sGSshWj8b6WrtuNjnAlSr40E+AgfeVrIAAAAAAJiWgAAAAAAAAAADNDs4RwAAAEBsY9JUoAwafnGojQcckXcOvght/skV5TLDkGYEZFgcoaofnRtEPJg1H9n6xI2rUPEldp6sTytYzSw+nAi/LbUMZH9mjAAAAEBVWIRriJF27OqY/hS5VOvO8Swbw4HjBiPzrffwZ5xq7RqYEpx4OOmbl94jj9Cdp93lyToIiH8jFJaSkQXPtGkPMleEBQAAAEB8ExSUA9xbTum5cKoarWfhgv3JX01GzddCsF/IhXgIb83AtTbIq6NrUjYHcgoID4JjiOMJcft0dUJa/EeEE7sEAAAAAAAAAAE0OzhHAAAAQPNXa7NgKAPG5/U0iJYvefDToAH9jgo8FYT7q3mYqAF0uZrlZaIYo/X18DSd36dHzRhvr1UuLYkstu2u9y3ScQY=",
+        "resultXdr": "AAAAAAAAArz////zu2AmCJI31SmmC6qXjcwfYgsaCyTb4enG267b6IADUC8AAAAAAAAAAP////8AAAAGAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAYAAAAAAAAAAAAAABEAAAAAAAAAAAAAAAH////+AAAAAAAAAAH////+AAAAAAAAAAA=",
+        "resultMetaXdr": "AAAABAAAAAAAAAAEAAAAAwAFJXgAAAAAAAAAAAMqbTGvyOcvPuApiT8JCDsMXqeRWck0Ss8Zlxc0OzhHAAAALpDfahAAAAktAAAAAQAAAAEAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAABHAAAAAAAAAAMAAAAAAAAJLgAAAABoUyJqAAAAAAAAAAEABSV4AAAAAAAAAAADKm0xr8jnLz7gKYk/CQg7DF6nkVnJNErPGZcXNDs4RwAAAC6Q32oQAAAJLQAAAAEAAAABAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAARwAAAAAAAAADAAAAAAAACS4AAAAAaFMiagAAAAAAAAADAAUivAAAAAAAAAAAvyZGpho5b9ZHNbQ/wuHSWger8YCH50EWTRCJ3WR/ZowAAAAXSHbnnAAARdUAAAI1AAAAAQAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAwAAAAAABSK8AAAAAGhsqc4AAAAAAAAAAQAFJXgAAAAAAAAAAL8mRqYaOW/WRzW0P8Lh0loHq/GAh+dBFk0Qid1kf2aMAAAAF0h255wAAEXVAAACNgAAAAEAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAAAAAAMAAAAAAAUleAAAAABobLd8AAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAAAEAAAAAAAAAAgAAAA8AAAADZmVlAAAAABIAAAAAAAAAAAMqbTGvyOcvPuApiT8JCDsMXqeRWck0Ss8Zlxc0OzhHAAAACgAAAAAAAAAAAAAAAAAAArwAAAAA",
+        "events": {
+          "transactionEventsXdr": [
+            "AAAAAAAAAAAAAAAB15KLcsJwPM/q9+uf9O9NUEpVqLl5/JtFDqLIQrTRzmEAAAABAAAAAAAAAAIAAAAPAAAAA2ZlZQAAAAASAAAAAAAAAAADKm0xr8jnLz7gKYk/CQg7DF6nkVnJNErPGZcXNDs4RwAAAAoAAAAAAAAAAAAAAAAAAAK8"
+          ]
+        },
+        "ledger": 337272,
+        "createdAt": 1751955324
+      },
+      {
+        "status": "SUCCESS",
+        "txHash": "973699dbd48afb3c81b796edce895aebe0023bbf250a6a2abd00086e5c94ab84",
+        "applicationOrder": 2,
+        "feeBump": false,
+        "envelopeXdr": "AAAAAgAAAACFivUlMyXwtcfYryl8RvpJ9Z5pRzP1+x7CbLyW3pnYDgAPQkAAAMdKAAABqAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAABAAAAABB90WssODNIgi6BHveqzxTRmIpvAFRyVNM+Hm2GVuCcAAAAAAAAAADtlCZZ5vMl+JUtJJAOPYwB9hb3stEZIjMkJ2yf2ghFPAAAABdIdugAAAAAAAAAAALemdgOAAAAQE5e8FMYtuh/E8YR+eMTlnsJ3oj9Fr9KvhZnRW/bFXIeQybZwxYoQoVLjMAwHvAFqCGE/yFJOipMyPBVDvDxpA+GVuCcAAAAQLjToPzfn0kYZaepMnJbaFbMcG2f8OrD8NxOTK0peGXaIeuLsPTxRms6NuKedhzKqgCnpyMOwxm4u838aw2vdww=",
+        "resultXdr": "AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAA=",
+        "resultMetaXdr": "AAAABAAAAAAAAAACAAAAAwAFJXgAAAAAAAAAAIWK9SUzJfC1x9ivKXxG+kn1nmlHM/X7HsJsvJbemdgOAAAAACyz13AAAMdKAAABpwAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAAAAAAMAAAAAAAUGFgAAAABobBpyAAAAAAAAAAEABSV4AAAAAAAAAACFivUlMyXwtcfYryl8RvpJ9Z5pRzP1+x7CbLyW3pnYDgAAAAAss9dwAADHSgAAAagAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAAAAAADAAAAAAAFJXgAAAAAaGy3fAAAAAAAAAABAAAAAAAAAAMAAAADAAUlbAAAAAAAAAAAEH3Rayw4M0iCLoEe96rPFNGYim8AVHJU0z4ebYZW4JwBol77S/sJ1AAAAF8AAADIAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAwAAAAAAAMdRAAAAAGhW2rkAAAAAAAAAAQAFJXgAAAAAAAAAABB90WssODNIgi6BHveqzxTRmIpvAFRyVNM+Hm2GVuCcAaJe5AOEIdQAAABfAAAAyAAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAAAAAAMAAAAAAADHUQAAAABoVtq5AAAAAAAAAAAABSV4AAAAAAAAAADtlCZZ5vMl+JUtJJAOPYwB9hb3stEZIjMkJ2yf2ghFPAAAABdIdugAAAUleAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAdeSi3LCcDzP6vfrn/TvTVBKVai5efybRQ6iyEK00c5hAAAAAQAAAAAAAAAEAAAADwAAAAh0cmFuc2ZlcgAAABIAAAAAAAAAABB90WssODNIgi6BHveqzxTRmIpvAFRyVNM+Hm2GVuCcAAAAEgAAAAAAAAAA7ZQmWebzJfiVLSSQDj2MAfYW97LRGSIzJCdsn9oIRTwAAAAOAAAABm5hdGl2ZQAAAAAACgAAAAAAAAAAAAAAF0h26AAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAAAEAAAAAAAAAAgAAAA8AAAADZmVlAAAAABIAAAAAAAAAAIWK9SUzJfC1x9ivKXxG+kn1nmlHM/X7HsJsvJbemdgOAAAACgAAAAAAAAAAAAAAAAAAAGQAAAAA",
+        "events": {
+          "transactionEventsXdr": [
+            "AAAAAAAAAAAAAAAB15KLcsJwPM/q9+uf9O9NUEpVqLl5/JtFDqLIQrTRzmEAAAABAAAAAAAAAAIAAAAPAAAAA2ZlZQAAAAASAAAAAAAAAACFivUlMyXwtcfYryl8RvpJ9Z5pRzP1+x7CbLyW3pnYDgAAAAoAAAAAAAAAAAAAAAAAAABk"
+          ],
+          "contractEventsXdr": [
+            [
+              "AAAAAAAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAAAEAAAAAAAAABAAAAA8AAAAIdHJhbnNmZXIAAAASAAAAAAAAAAAQfdFrLDgzSIIugR73qs8U0ZiKbwBUclTTPh5thlbgnAAAABIAAAAAAAAAAO2UJlnm8yX4lS0kkA49jAH2Fvey0RkiMyQnbJ/aCEU8AAAADgAAAAZuYXRpdmUAAAAAAAoAAAAAAAAAAAAAABdIdugA"
+            ]
+          ]
+        },
+        "ledger": 337272,
+        "createdAt": 1751955324
+      },
+      {
+        "status": "SUCCESS",
+        "txHash": "755b48791d7b1b7c4f68675e78ba5167162133b0873949235e81006a21dd52cd",
+        "applicationOrder": 3,
+        "feeBump": false,
+        "envelopeXdr": "AAAAAgAAAABpUTPXPvN3+8v2Cl+6qDXlDqQ6ktoudhowSiMNBqhZngExLQAAAA2hAAAVwgAAAAEAAAAAAAAAAAAAAABobLeMAAAAAAAAAAEAAAABAAAAAGlRM9c+83f7y/YKX7qoNeUOpDqS2i52GjBKIw0GqFmeAAAAGAAAAAAAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAJc2V0X3ByaWNlAAAAAAAAAgAAABAAAAABAAAAEAAAAAoAAAAAAAAAAJYxZhBWnlZ3AAAACgAAAAAAAAAAA4svb21d+NMAAAAKAAAAAAAAAAAAAFrzF8WOngAAAAoAAAAAAAAAAAAAzlZJvDSrAAAACgAAAAAAAAAAADUZdnd4hHsAAAAKAAAAAAAAAAAAAFryNi8g1QAAAAoAAAAAAAAAAAAANFak+TXaAAAACgAAAAAAAAAAAAZXAiMM0PQAAAAKAAAAAAAAAAAAATClyfjScwAAAAoAAAAAAAAAAAAAEPEKMAkQAAAACgAAAAAAAAAAAAS7lEpZRkoAAAAKAAAAAAAAAAAAAFrzEHpAAAAAAAoAAAAAAAAAAAABboY05/qTAAAACgAAAAAAAAAAAAAWjvy21H4AAAAKAAAAAAAAAAAAAqUWLpOXrgAAAAoAAAAAAAAAAAAAarh2TTl4AAAABQAAAZforF6gAAAAAQAAAAAAAAAAAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACXNldF9wcmljZQAAAAAAAAIAAAAQAAAAAQAAABAAAAAKAAAAAAAAAACWMWYQVp5WdwAAAAoAAAAAAAAAAAOLL29tXfjTAAAACgAAAAAAAAAAAABa8xfFjp4AAAAKAAAAAAAAAAAAAM5WSbw0qwAAAAoAAAAAAAAAAAA1GXZ3eIR7AAAACgAAAAAAAAAAAABa8jYvINUAAAAKAAAAAAAAAAAAADRWpPk12gAAAAoAAAAAAAAAAAAGVwIjDND0AAAACgAAAAAAAAAAAAEwpcn40nMAAAAKAAAAAAAAAAAAABDxCjAJEAAAAAoAAAAAAAAAAAAEu5RKWUZKAAAACgAAAAAAAAAAAABa8xB6QAAAAAAKAAAAAAAAAAAAAW6GNOf6kwAAAAoAAAAAAAAAAAAAFo78ttR+AAAACgAAAAAAAAAAAAKlFi6Tl64AAAAKAAAAAAAAAAAAAGq4dk05eAAAAAUAAAGX6KxeoAAAAAAAAAABAAAAAAAAAAEAAAAH2meYeDjstDaE4KhbEjBxwWdgVqPrbT2cAthX7ajkTcMAAAARAAAABgAAAAGw7KROebfFrhD7dcxcLPrX7UfuazOzetkAMPD12FOYmAAAAAkAAAGX6KxeoAAAAAAAAAAAAAAAAAAAAAYAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAJAAABl+isXqAAAAAAAAAAAQAAAAAAAAAGAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACQAAAZforF6gAAAAAAAAAAIAAAAAAAAABgAAAAGw7KROebfFrhD7dcxcLPrX7UfuazOzetkAMPD12FOYmAAAAAkAAAGX6KxeoAAAAAAAAAADAAAAAAAAAAYAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAJAAABl+isXqAAAAAAAAAABAAAAAAAAAAGAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACQAAAZforF6gAAAAAAAAAAUAAAAAAAAABgAAAAGw7KROebfFrhD7dcxcLPrX7UfuazOzetkAMPD12FOYmAAAAAkAAAGX6KxeoAAAAAAAAAAGAAAAAAAAAAYAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAJAAABl+isXqAAAAAAAAAABwAAAAAAAAAGAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACQAAAZforF6gAAAAAAAAAAgAAAAAAAAABgAAAAGw7KROebfFrhD7dcxcLPrX7UfuazOzetkAMPD12FOYmAAAAAkAAAGX6KxeoAAAAAAAAAAJAAAAAAAAAAYAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAJAAABl+isXqAAAAAAAAAACgAAAAAAAAAGAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACQAAAZforF6gAAAAAAAAAAsAAAAAAAAABgAAAAGw7KROebfFrhD7dcxcLPrX7UfuazOzetkAMPD12FOYmAAAAAkAAAGX6KxeoAAAAAAAAAAMAAAAAAAAAAYAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAJAAABl+isXqAAAAAAAAAADQAAAAAAAAAGAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACQAAAZforF6gAAAAAAAAAA4AAAAAAAAABgAAAAGw7KROebfFrhD7dcxcLPrX7UfuazOzetkAMPD12FOYmAAAAAkAAAGX6KxeoAAAAAAAAAAPAAAAAAAAAAYAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAUAAAAAQCn2MAAAJxAAAATiAAAAAAAmJaAAAAAAcyl2WAAAABAyIaUCPcC7eyzng1h8s/XLy+wLzmd2PzCj9lIRSesJVS/QlqhxdK6uiNtgP9nvcQ+D5jMAwCedquA5zDhQfOzDw==",
+        "resultXdr": "AAAAAAALMtUAAAAAAAAAAQAAAAAAAAAYAAAAANnVLpUIC01nXOWYpLQG/4W2uDzPwAmGLu9KQjrgOClAAAAAAA==",
+        "resultMetaXdr": "AAAABAAAAAAAAAACAAAAAwAFJXgAAAAAAAAAAGlRM9c+83f7y/YKX7qoNeUOpDqS2i52GjBKIw0GqFmeAAAAFlUyDQwAAA2hAAAVwQAAAAEAAAAAAAAAAAAAAAAAAQEBAAAAAQAAAAChM5sgwhIdyIwqcgCD9fwQBNYj/ox4Aw054hQxzKXZYAAAAAEAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAEAAAAAAAAAAwAAAAAABSU8AAAAAGhstlAAAAAAAAAAAQAFJXgAAAAAAAAAAGlRM9c+83f7y/YKX7qoNeUOpDqS2i52GjBKIw0GqFmeAAAAFlUyDQwAAA2hAAAVwgAAAAEAAAAAAAAAAAAAAAAAAQEBAAAAAQAAAAChM5sgwhIdyIwqcgCD9fwQBNYj/ox4Aw054hQxzKXZYAAAAAEAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAEAAAAAAAAAAwAAAAAABSV4AAAAAGhst3wAAAAAAAAAAQAAAAAAAAAiAAAAAwAFJTwAAAAGAAAAAAAAAAGw7KROebfFrhD7dcxcLPrX7UfuazOzetkAMPD12FOYmAAAABQAAAABAAAAEwAAAADaZ5h4OOy0NoTgqFsSMHHBZ2BWo+ttPZwC2FftqORNwwAAAAEAAAAYAAAADgAAAAVhZG1pbgAAAAAAABIAAAAAAAAAAGlRM9c+83f7y/YKX7qoNeUOpDqS2i52GjBKIw0GqFmeAAAADgAAAAphc3NldF90dGxzAAAAAAAQAAAAAQAAAAAAAAAOAAAABmFzc2V0cwAAAAAAEAAAAAEAAAAQAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQlRDAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA0VUSAAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAARVU0RUAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADWFJQAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA1NPTAAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAARVU0RDAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQURBAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABEFWQVgAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANET1QAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAFTUFUSUMAAAAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAARMSU5LAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADREFJAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABEFUT00AAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANYTE0AAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADVU5JAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABEVVUkMAAAAOAAAACmJhc2VfYXNzZXQAAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA1VTRAAAAAAOAAAACGRlY2ltYWxzAAAAAwAAAA4AAAAOAAAADmxhc3RfdGltZXN0YW1wAAAAAAAFAAABl+inysAAAAAOAAAABnBlcmlvZAAAAAAABQAAAAAFJlwAAAAADgAAAApyZXNvbHV0aW9uAAAAAAADAAST4AAAAA8AAAADQURBAAAAAAMAAAAGAAAADwAAAARBVE9NAAAAAwAAAAwAAAAPAAAABEFWQVgAAAADAAAABwAAAA8AAAADQlRDAAAAAAMAAAAAAAAADwAAAANEQUkAAAAAAwAAAAsAAAAPAAAAA0RPVAAAAAADAAAACAAAAA8AAAADRVRIAAAAAAMAAAABAAAADwAAAARFVVJDAAAAAwAAAA8AAAAPAAAABExJTksAAAADAAAACgAAAA8AAAAFTUFUSUMAAAAAAAADAAAACQAAAA8AAAADU09MAAAAAAMAAAAEAAAADwAAAANVTkkAAAAAAwAAAA4AAAAPAAAABFVTREMAAAADAAAABQAAAA8AAAAEVVNEVAAAAAMAAAACAAAADwAAAANYTE0AAAAAAwAAAA0AAAAPAAAAA1hSUAAAAAADAAAAAwAAAAAAAAABAAUleAAAAAYAAAAAAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAAFAAAAAEAAAATAAAAANpnmHg47LQ2hOCoWxIwccFnYFaj6209nALYV+2o5E3DAAAAAQAAABgAAAAOAAAABWFkbWluAAAAAAAAEgAAAAAAAAAAaVEz1z7zd/vL9gpfuqg15Q6kOpLaLnYaMEojDQaoWZ4AAAAOAAAACmFzc2V0X3R0bHMAAAAAABAAAAABAAAAAAAAAA4AAAAGYXNzZXRzAAAAAAAQAAAAAQAAABAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANCVEMAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRVRIAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABFVTRFQAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANYUlAAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADU09MAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABFVTREMAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANBREEAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAEQVZBWAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA0RPVAAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAAVNQVRJQwAAAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABExJTksAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANEQUkAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAEQVRPTQAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA1hMTQAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANVTkkAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAERVVSQwAAAA4AAAAKYmFzZV9hc3NldAAAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADVVNEAAAAAA4AAAAIZGVjaW1hbHMAAAADAAAADgAAAA4AAAAObGFzdF90aW1lc3RhbXAAAAAAAAUAAAGX6KxeoAAAAA4AAAAGcGVyaW9kAAAAAAAFAAAAAAUmXAAAAAAOAAAACnJlc29sdXRpb24AAAAAAAMABJPgAAAADwAAAANBREEAAAAAAwAAAAYAAAAPAAAABEFUT00AAAADAAAADAAAAA8AAAAEQVZBWAAAAAMAAAAHAAAADwAAAANCVEMAAAAAAwAAAAAAAAAPAAAAA0RBSQAAAAADAAAACwAAAA8AAAADRE9UAAAAAAMAAAAIAAAADwAAAANFVEgAAAAAAwAAAAEAAAAPAAAABEVVUkMAAAADAAAADwAAAA8AAAAETElOSwAAAAMAAAAKAAAADwAAAAVNQVRJQwAAAAAAAAMAAAAJAAAADwAAAANTT0wAAAAAAwAAAAQAAAAPAAAAA1VOSQAAAAADAAAADgAAAA8AAAAEVVNEQwAAAAMAAAAFAAAADwAAAARVU0RUAAAAAwAAAAIAAAAPAAAAA1hMTQAAAAADAAAADQAAAA8AAAADWFJQAAAAAAMAAAADAAAAAAAAAAAABSV4AAAACRtWwYKp8aF2qX+Jg4xRIWaw97oBDTKmDaMTGerc8aiVAAVo+QAAAAAAAAAAAAUleAAAAAmXaw4b0ehOqe/BC602CtDLHlLJmGqECWqW8osfIOsiFAAFaPkAAAAAAAAAAAAFJXgAAAAJ/Wpp20YmTDXBw16kOtl1jgGpveiIqSIxHJpVhi3SIEUABWj5AAAAAAAAAAAABSV4AAAABgAAAAAAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAJAAABl+isXqAAAAAAAAAADAAAAAAAAAAKAAAAAAAAAAAAAW6GNOf6kwAAAAAAAAAAAAUleAAAAAlOPfLSMl9xE2dQ06IxdD68yMhOeU3fKrkbPJ33VSBPRAAFaPkAAAAAAAAAAAAFJXgAAAAGAAAAAAAAAAGw7KROebfFrhD7dcxcLPrX7UfuazOzetkAMPD12FOYmAAAAAkAAAGX6KxeoAAAAAAAAAAOAAAAAAAAAAoAAAAAAAAAAAACpRYuk5euAAAAAAAAAAAABSV4AAAABgAAAAAAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAJAAABl+isXqAAAAAAAAAAAQAAAAAAAAAKAAAAAAAAAAADiy9vbV340wAAAAAAAAAAAAUleAAAAAmohgXFLMfosl9gbyvew1/Cx/XjW76VVXLo6LbDlL0kVAAFaPkAAAAAAAAAAAAFJXgAAAAJa84nEi9j/5CfMlG33MtaNS1H2L5iqbq1IUDD0gOsCyQABWj5AAAAAAAAAAAABSV4AAAABgAAAAAAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAJAAABl+isXqAAAAAAAAAADQAAAAAAAAAKAAAAAAAAAAAAABaO/LbUfgAAAAAAAAAAAAUleAAAAAYAAAAAAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACQAAAZforF6gAAAAAAAAAAgAAAAAAAAACgAAAAAAAAAAAAEwpcn40nMAAAAAAAAAAAAFJXgAAAAJrV+x0DJmHq+Ny9EKTJDwOe65HIxhA3fa9jbwrFUeJc8ABWj5AAAAAAAAAAAABSV4AAAACRTs0YFy1+M2aG76tT2eSadx45lSWuKqh00V8LjLDHhQAAVo+QAAAAAAAAAAAAUleAAAAAYAAAAAAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACQAAAZforF6gAAAAAAAAAAcAAAAAAAAACgAAAAAAAAAAAAZXAiMM0PQAAAAAAAAAAAAFJXgAAAAGAAAAAAAAAAGw7KROebfFrhD7dcxcLPrX7UfuazOzetkAMPD12FOYmAAAAAkAAAGX6KxeoAAAAAAAAAAEAAAAAAAAAAoAAAAAAAAAAAA1GXZ3eIR7AAAAAAAAAAAABSV4AAAABgAAAAAAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAJAAABl+isXqAAAAAAAAAADwAAAAAAAAAKAAAAAAAAAAAAAGq4dk05eAAAAAAAAAAAAAUleAAAAAmHGDZmgBRLxoX5oiXi09GSmdgRRxs9MMbbCzQytgNhkQAFaPkAAAAAAAAAAAAFJXgAAAAJaSfopin+fB6bsgXu4ZoSM78ihrZaD4QHL6nrUbS6NZMABWj5AAAAAAAAAAAABSV4AAAABgAAAAAAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAJAAABl+isXqAAAAAAAAAABgAAAAAAAAAKAAAAAAAAAAAAADRWpPk12gAAAAAAAAAAAAUleAAAAAYAAAAAAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACQAAAZforF6gAAAAAAAAAAUAAAAAAAAACgAAAAAAAAAAAABa8jYvINUAAAAAAAAAAAAFJXgAAAAGAAAAAAAAAAGw7KROebfFrhD7dcxcLPrX7UfuazOzetkAMPD12FOYmAAAAAkAAAGX6KxeoAAAAAAAAAALAAAAAAAAAAoAAAAAAAAAAAAAWvMQekAAAAAAAAAAAAAABSV4AAAABgAAAAAAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAJAAABl+isXqAAAAAAAAAACQAAAAAAAAAKAAAAAAAAAAAAABDxCjAJEAAAAAAAAAAAAAUleAAAAAYAAAAAAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACQAAAZforF6gAAAAAAAAAAMAAAAAAAAACgAAAAAAAAAAAADOVkm8NKsAAAAAAAAAAAAFJXgAAAAJ9RAqLANH4ius/Vq43FXikVlC8/aStdNH+0VPE+f/vrwABWj5AAAAAAAAAAAABSV4AAAACa+q8ZyOcbjQZOBzMuII58FgolfTj1g6nASeWehH/Y4yAAVo+QAAAAAAAAAAAAUleAAAAAYAAAAAAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACQAAAZforF6gAAAAAAAAAAoAAAAAAAAACgAAAAAAAAAAAAS7lEpZRkoAAAAAAAAAAAAFJXgAAAAJkaaYJYTilZxZ2YFR1/faqISLB6Gb7lWFvG3uRd20iZwABWj5AAAAAAAAAAAABSV4AAAACeiycPprqSDFiAUYAnjx/SjeVXwXe6Li76gXDPNDNc/7AAVo+QAAAAAAAAAAAAUleAAAAAYAAAAAAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACQAAAZforF6gAAAAAAAAAAIAAAAAAAAACgAAAAAAAAAAAABa8xfFjp4AAAAAAAAAAAAFJXgAAAAJCOYm2pVJLLGMpI0wbbfMeTDDUY0ZlkZTETzdKKsuCZYABWj5AAAAAAAAAAAABSV4AAAACR5Y6Ub0+8DldV2wrMOiPhNnqsMaYcpGUkKm4/40DqEHAAVo+QAAAAAAAAAAAAUleAAAAAYAAAAAAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAACQAAAZforF6gAAAAAAAAAAAAAAAAAAAACgAAAAAAAAAAljFmEFaeVncAAAAAAAAAAQAAAAAAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAABAAAAAAAAAAMAAAAPAAAACXJlZmxlY3RvcgAAAAAAAA8AAAAGcHJpY2VzAAAAAAAPAAAABnVwZGF0ZQAAAAAAEAAAAAEAAAAQAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQlRDAAAAAAoAAAAAAAAAAJYxZhBWnlZ3AAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRVRIAAAAAAoAAAAAAAAAAAOLL29tXfjTAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAEVVNEVAAAAAoAAAAAAAAAAAAAWvMXxY6eAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADWFJQAAAAAAoAAAAAAAAAAAAAzlZJvDSrAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADU09MAAAAAAoAAAAAAAAAAAA1GXZ3eIR7AAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAEVVNEQwAAAAoAAAAAAAAAAAAAWvI2LyDVAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQURBAAAAAAoAAAAAAAAAAAAANFak+TXaAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAEQVZBWAAAAAoAAAAAAAAAAAAGVwIjDND0AAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRE9UAAAAAAoAAAAAAAAAAAABMKXJ+NJzAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAFTUFUSUMAAAAAAAAKAAAAAAAAAAAAABDxCjAJEAAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABExJTksAAAAKAAAAAAAAAAAABLuUSllGSgAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA0RBSQAAAAAKAAAAAAAAAAAAAFrzEHpAAAAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABEFUT00AAAAKAAAAAAAAAAAAAW6GNOf6kwAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA1hMTQAAAAAKAAAAAAAAAAAAABaO/LbUfgAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA1VOSQAAAAAKAAAAAAAAAAAAAqUWLpOXrgAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABEVVUkMAAAAKAAAAAAAAAAAAAGq4dk05eAAAAAIAAAADAAUleAAAAAAAAAAAaVEz1z7zd/vL9gpfuqg15Q6kOpLaLnYaMEojDQaoWZ4AAAAWVTINDAAADaEAABXCAAAAAQAAAAAAAAAAAAAAAAABAQEAAAABAAAAAKEzmyDCEh3IjCpyAIP1/BAE1iP+jHgDDTniFDHMpdlgAAAAAQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAQAAAAAAAAADAAAAAAAFJXgAAAAAaGy3fAAAAAAAAAABAAUleAAAAAAAAAAAaVEz1z7zd/vL9gpfuqg15Q6kOpLaLnYaMEojDQaoWZ4AAAAWVb9xGwAADaEAABXCAAAAAQAAAAAAAAAAAAAAAAABAQEAAAABAAAAAKEzmyDCEh3IjCpyAIP1/BAE1iP+jHgDDTniFDHMpdlgAAAAAQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAQAAAAAAAAADAAAAAAAFJXgAAAAAaGy3fAAAAAAAAAABAAAAAQAAAAAAAAAAAAdSWQAAAAAAA+AYAAAAAAADr2sAAAABAAAAAQAAAAIAAAAAAAAAAAAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAAAEAAAAAAAAAAgAAAA8AAAADZmVlAAAAABIAAAAAAAAAAGlRM9c+83f7y/YKX7qoNeUOpDqS2i52GjBKIw0GqFmeAAAACgAAAAAAAAAAAAAAAACYluQAAAABAAAAAAAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAAAEAAAAAAAAAAgAAAA8AAAADZmVlAAAAABIAAAAAAAAAAGlRM9c+83f7y/YKX7qoNeUOpDqS2i52GjBKIw0GqFmeAAAACv////////////////9ym/EAAAAWAAAAAQAAAAAAAAAAAAAAAgAAAAAAAAADAAAADwAAAAdmbl9jYWxsAAAAAA0AAAAgsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAPAAAACXNldF9wcmljZQAAAAAAABAAAAABAAAAAgAAABAAAAABAAAAEAAAAAoAAAAAAAAAAJYxZhBWnlZ3AAAACgAAAAAAAAAAA4svb21d+NMAAAAKAAAAAAAAAAAAAFrzF8WOngAAAAoAAAAAAAAAAAAAzlZJvDSrAAAACgAAAAAAAAAAADUZdnd4hHsAAAAKAAAAAAAAAAAAAFryNi8g1QAAAAoAAAAAAAAAAAAANFak+TXaAAAACgAAAAAAAAAAAAZXAiMM0PQAAAAKAAAAAAAAAAAAATClyfjScwAAAAoAAAAAAAAAAAAAEPEKMAkQAAAACgAAAAAAAAAAAAS7lEpZRkoAAAAKAAAAAAAAAAAAAFrzEHpAAAAAAAoAAAAAAAAAAAABboY05/qTAAAACgAAAAAAAAAAAAAWjvy21H4AAAAKAAAAAAAAAAAAAqUWLpOXrgAAAAoAAAAAAAAAAAAAarh2TTl4AAAABQAAAZforF6gAAAAAQAAAAAAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAABAAAAAAAAAAMAAAAPAAAACXJlZmxlY3RvcgAAAAAAAA8AAAAGcHJpY2VzAAAAAAAPAAAABnVwZGF0ZQAAAAAAEAAAAAEAAAAQAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQlRDAAAAAAoAAAAAAAAAAJYxZhBWnlZ3AAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRVRIAAAAAAoAAAAAAAAAAAOLL29tXfjTAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAEVVNEVAAAAAoAAAAAAAAAAAAAWvMXxY6eAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADWFJQAAAAAAoAAAAAAAAAAAAAzlZJvDSrAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADU09MAAAAAAoAAAAAAAAAAAA1GXZ3eIR7AAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAEVVNEQwAAAAoAAAAAAAAAAAAAWvI2LyDVAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQURBAAAAAAoAAAAAAAAAAAAANFak+TXaAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAEQVZBWAAAAAoAAAAAAAAAAAAGVwIjDND0AAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRE9UAAAAAAoAAAAAAAAAAAABMKXJ+NJzAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAFTUFUSUMAAAAAAAAKAAAAAAAAAAAAABDxCjAJEAAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABExJTksAAAAKAAAAAAAAAAAABLuUSllGSgAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA0RBSQAAAAAKAAAAAAAAAAAAAFrzEHpAAAAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABEFUT00AAAAKAAAAAAAAAAAAAW6GNOf6kwAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA1hMTQAAAAAKAAAAAAAAAAAAABaO/LbUfgAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA1VOSQAAAAAKAAAAAAAAAAAAAqUWLpOXrgAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABEVVUkMAAAAKAAAAAAAAAAAAAGq4dk05eAAAAAEAAAAAAAAAAbDspE55t8WuEPt1zFws+tftR+5rM7N62QAw8PXYU5iYAAAAAgAAAAAAAAACAAAADwAAAAlmbl9yZXR1cm4AAAAAAAAPAAAACXNldF9wcmljZQAAAAAAAAEAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAKcmVhZF9lbnRyeQAAAAAABQAAAAAAAAASAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAC3dyaXRlX2VudHJ5AAAAAAUAAAAAAAAAEQAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAABBsZWRnZXJfcmVhZF9ieXRlAAAABQAAAAAAAFjgAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEWxlZGdlcl93cml0ZV9ieXRlAAAAAAAABQAAAAAAAAtcAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADXJlYWRfa2V5X2J5dGUAAAAAAAAFAAAAAAAABFQAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAOd3JpdGVfa2V5X2J5dGUAAAAAAAUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAAA5yZWFkX2RhdGFfYnl0ZQAAAAAABQAAAAAAAAVcAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD3dyaXRlX2RhdGFfYnl0ZQAAAAAFAAAAAAAAC1wAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAOcmVhZF9jb2RlX2J5dGUAAAAAAAUAAAAAAABThAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAAA93cml0ZV9jb2RlX2J5dGUAAAAABQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACmVtaXRfZXZlbnQAAAAAAAUAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAAA9lbWl0X2V2ZW50X2J5dGUAAAAABQAAAAAAAAT4AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACGNwdV9pbnNuAAAABQAAAAAAUVs1AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACG1lbV9ieXRlAAAABQAAAAAAI+WHAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEWludm9rZV90aW1lX25zZWNzAAAAAAAABQAAAAAAJjL5AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD21heF9yd19rZXlfYnl0ZQAAAAAFAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAQbWF4X3J3X2RhdGFfYnl0ZQAAAAUAAAAAAAAFXAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAABBtYXhfcndfY29kZV9ieXRlAAAABQAAAAAAAFOEAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAE21heF9lbWl0X2V2ZW50X2J5dGUAAAAABQAAAAAAAAT4",
+        "diagnosticEventsXdr": [
+          "AAAAAQAAAAAAAAAAAAAAAgAAAAAAAAADAAAADwAAAAdmbl9jYWxsAAAAAA0AAAAgsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAAPAAAACXNldF9wcmljZQAAAAAAABAAAAABAAAAAgAAABAAAAABAAAAEAAAAAoAAAAAAAAAAJYxZhBWnlZ3AAAACgAAAAAAAAAAA4svb21d+NMAAAAKAAAAAAAAAAAAAFrzF8WOngAAAAoAAAAAAAAAAAAAzlZJvDSrAAAACgAAAAAAAAAAADUZdnd4hHsAAAAKAAAAAAAAAAAAAFryNi8g1QAAAAoAAAAAAAAAAAAANFak+TXaAAAACgAAAAAAAAAAAAZXAiMM0PQAAAAKAAAAAAAAAAAAATClyfjScwAAAAoAAAAAAAAAAAAAEPEKMAkQAAAACgAAAAAAAAAAAAS7lEpZRkoAAAAKAAAAAAAAAAAAAFrzEHpAAAAAAAoAAAAAAAAAAAABboY05/qTAAAACgAAAAAAAAAAAAAWjvy21H4AAAAKAAAAAAAAAAAAAqUWLpOXrgAAAAoAAAAAAAAAAAAAarh2TTl4AAAABQAAAZforF6g",
+          "AAAAAQAAAAAAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAABAAAAAAAAAAMAAAAPAAAACXJlZmxlY3RvcgAAAAAAAA8AAAAGcHJpY2VzAAAAAAAPAAAABnVwZGF0ZQAAAAAAEAAAAAEAAAAQAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQlRDAAAAAAoAAAAAAAAAAJYxZhBWnlZ3AAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRVRIAAAAAAoAAAAAAAAAAAOLL29tXfjTAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAEVVNEVAAAAAoAAAAAAAAAAAAAWvMXxY6eAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADWFJQAAAAAAoAAAAAAAAAAAAAzlZJvDSrAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADU09MAAAAAAoAAAAAAAAAAAA1GXZ3eIR7AAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAEVVNEQwAAAAoAAAAAAAAAAAAAWvI2LyDVAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQURBAAAAAAoAAAAAAAAAAAAANFak+TXaAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAEQVZBWAAAAAoAAAAAAAAAAAAGVwIjDND0AAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRE9UAAAAAAoAAAAAAAAAAAABMKXJ+NJzAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAFTUFUSUMAAAAAAAAKAAAAAAAAAAAAABDxCjAJEAAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABExJTksAAAAKAAAAAAAAAAAABLuUSllGSgAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA0RBSQAAAAAKAAAAAAAAAAAAAFrzEHpAAAAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABEFUT00AAAAKAAAAAAAAAAAAAW6GNOf6kwAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA1hMTQAAAAAKAAAAAAAAAAAAABaO/LbUfgAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA1VOSQAAAAAKAAAAAAAAAAAAAqUWLpOXrgAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAABEVVUkMAAAAKAAAAAAAAAAAAAGq4dk05eA==",
+          "AAAAAQAAAAAAAAABsOykTnm3xa4Q+3XMXCz61+1H7mszs3rZADDw9dhTmJgAAAACAAAAAAAAAAIAAAAPAAAACWZuX3JldHVybgAAAAAAAA8AAAAJc2V0X3ByaWNlAAAAAAAAAQ==",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACnJlYWRfZW50cnkAAAAAAAUAAAAAAAAAEg==",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAC3dyaXRlX2VudHJ5AAAAAAUAAAAAAAAAEQ==",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEGxlZGdlcl9yZWFkX2J5dGUAAAAFAAAAAAAAWOA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEWxlZGdlcl93cml0ZV9ieXRlAAAAAAAABQAAAAAAAAtc",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADXJlYWRfa2V5X2J5dGUAAAAAAAAFAAAAAAAABFQ=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADndyaXRlX2tleV9ieXRlAAAAAAAFAAAAAAAAAAA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADnJlYWRfZGF0YV9ieXRlAAAAAAAFAAAAAAAABVw=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD3dyaXRlX2RhdGFfYnl0ZQAAAAAFAAAAAAAAC1w=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADnJlYWRfY29kZV9ieXRlAAAAAAAFAAAAAAAAU4Q=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD3dyaXRlX2NvZGVfYnl0ZQAAAAAFAAAAAAAAAAA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACmVtaXRfZXZlbnQAAAAAAAUAAAAAAAAAAQ==",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD2VtaXRfZXZlbnRfYnl0ZQAAAAAFAAAAAAAABPg=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACGNwdV9pbnNuAAAABQAAAAAAUVs1",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACG1lbV9ieXRlAAAABQAAAAAAI+WH",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEWludm9rZV90aW1lX25zZWNzAAAAAAAABQAAAAAAJjL5",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD21heF9yd19rZXlfYnl0ZQAAAAAFAAAAAAAAAEA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEG1heF9yd19kYXRhX2J5dGUAAAAFAAAAAAAABVw=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEG1heF9yd19jb2RlX2J5dGUAAAAFAAAAAAAAU4Q=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAE21heF9lbWl0X2V2ZW50X2J5dGUAAAAABQAAAAAAAAT4"
+        ],
+        "events": {
+          "transactionEventsXdr": [
+            "AAAAAAAAAAAAAAAB15KLcsJwPM/q9+uf9O9NUEpVqLl5/JtFDqLIQrTRzmEAAAABAAAAAAAAAAIAAAAPAAAAA2ZlZQAAAAASAAAAAAAAAABpUTPXPvN3+8v2Cl+6qDXlDqQ6ktoudhowSiMNBqhZngAAAAoAAAAAAAAAAAAAAAAAmJbk",
+            "AAAAAQAAAAAAAAAB15KLcsJwPM/q9+uf9O9NUEpVqLl5/JtFDqLIQrTRzmEAAAABAAAAAAAAAAIAAAAPAAAAA2ZlZQAAAAASAAAAAAAAAABpUTPXPvN3+8v2Cl+6qDXlDqQ6ktoudhowSiMNBqhZngAAAAr/////////////////cpvx"
+          ],
+          "contractEventsXdr": [
+            [
+              "AAAAAAAAAAGw7KROebfFrhD7dcxcLPrX7UfuazOzetkAMPD12FOYmAAAAAEAAAAAAAAAAwAAAA8AAAAJcmVmbGVjdG9yAAAAAAAADwAAAAZwcmljZXMAAAAAAA8AAAAGdXBkYXRlAAAAAAAQAAAAAQAAABAAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANCVEMAAAAACgAAAAAAAAAAljFmEFaeVncAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANFVEgAAAAACgAAAAAAAAAAA4svb21d+NMAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAARVU0RUAAAACgAAAAAAAAAAAABa8xfFjp4AAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANYUlAAAAAACgAAAAAAAAAAAADOVkm8NKsAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANTT0wAAAAACgAAAAAAAAAAADUZdnd4hHsAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAARVU0RDAAAACgAAAAAAAAAAAABa8jYvINUAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANBREEAAAAACgAAAAAAAAAAAAA0VqT5NdoAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAARBVkFYAAAACgAAAAAAAAAAAAZXAiMM0PQAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANET1QAAAAACgAAAAAAAAAAAAEwpcn40nMAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAAVNQVRJQwAAAAAAAAoAAAAAAAAAAAAAEPEKMAkQAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAETElOSwAAAAoAAAAAAAAAAAAEu5RKWUZKAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADREFJAAAAAAoAAAAAAAAAAAAAWvMQekAAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAEQVRPTQAAAAoAAAAAAAAAAAABboY05/qTAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADWExNAAAAAAoAAAAAAAAAAAAAFo78ttR+AAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADVU5JAAAAAAoAAAAAAAAAAAACpRYuk5euAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAAERVVSQwAAAAoAAAAAAAAAAAAAarh2TTl4"
+            ]
+          ]
+        },
+        "ledger": 337272,
+        "createdAt": 1751955324
+      },
+      {
+        "status": "SUCCESS",
+        "txHash": "5686dc3df8ef0b7af08edcf9cc2eecca90fdbab99626117770e46e0042efddcb",
+        "applicationOrder": 4,
+        "feeBump": false,
+        "envelopeXdr": "AAAAAgAAAACWDRNrgN4HpWfA2B7H3QSMtt7GSK/J3/cH+i/Waf406QExLQAAAA1qAAAVxAAAAAEAAAAAAAAAAAAAAABobLeMAAAAAAAAAAEAAAABAAAAAJYNE2uA3gelZ8DYHsfdBIy23sZIr8nf9wf6L9Zp/jTpAAAAGAAAAAAAAAABKrf0Z9GS/LKu+hOOCq4fWWIWaS1ePWMaLC7oHiY6uD8AAAAJc2V0X3ByaWNlAAAAAAAAAgAAABAAAAABAAAABwAAAAoAAAAAAAAAAAAAAAAAAAAAAAAACgAAAAAAAAAAAAAAFAjvQXUAAAAKAAAAAAAAAAAAAFry4TaWFwAAAAoAAAAAAAAAAAAAABlwHrujAAAACgAAAAAAAAAAAAAACkGhPLUAAAAKAAAAAAAAAAAAAAASRzQWKwAAAAoAAAAAAAAAAAAAYLyUqAn+AAAABQAAAZforF6gAAAAAQAAAAAAAAAAAAAAASq39GfRkvyyrvoTjgquH1liFmktXj1jGiwu6B4mOrg/AAAACXNldF9wcmljZQAAAAAAAAIAAAAQAAAAAQAAAAcAAAAKAAAAAAAAAAAAAAAAAAAAAAAAAAoAAAAAAAAAAAAAABQI70F1AAAACgAAAAAAAAAAAABa8uE2lhcAAAAKAAAAAAAAAAAAAAAZcB67owAAAAoAAAAAAAAAAAAAAApBoTy1AAAACgAAAAAAAAAAAAAAEkc0FisAAAAKAAAAAAAAAAAAAGC8lKgJ/gAAAAUAAAGX6KxeoAAAAAAAAAABAAAAAAAAAAEAAAAH2meYeDjstDaE4KhbEjBxwWdgVqPrbT2cAthX7ajkTcMAAAAHAAAABgAAAAEqt/Rn0ZL8sq76E44Krh9ZYhZpLV49YxosLugeJjq4PwAAAAkAAAGX6KxeoAAAAAAAAAABAAAAAAAAAAYAAAABKrf0Z9GS/LKu+hOOCq4fWWIWaS1ePWMaLC7oHiY6uD8AAAAJAAABl+isXqAAAAAAAAAAAgAAAAAAAAAGAAAAASq39GfRkvyyrvoTjgquH1liFmktXj1jGiwu6B4mOrg/AAAACQAAAZforF6gAAAAAAAAAAMAAAAAAAAABgAAAAEqt/Rn0ZL8sq76E44Krh9ZYhZpLV49YxosLugeJjq4PwAAAAkAAAGX6KxeoAAAAAAAAAAEAAAAAAAAAAYAAAABKrf0Z9GS/LKu+hOOCq4fWWIWaS1ePWMaLC7oHiY6uD8AAAAJAAABl+isXqAAAAAAAAAABQAAAAAAAAAGAAAAASq39GfRkvyyrvoTjgquH1liFmktXj1jGiwu6B4mOrg/AAAACQAAAZforF6gAAAAAAAAAAYAAAAAAAAABgAAAAEqt/Rn0ZL8sq76E44Krh9ZYhZpLV49YxosLugeJjq4PwAAABQAAAABAIlUQAAAnEAAAAu4AAAAAACYloAAAAABzKXZYAAAAEAiyeOyFuBoelRjU2uOG6W0J9jAVHsbNazj9Mu4AVSVGIQQGG1UhoGHvx2vNk2J+MYaK51j/FKuFa8tUgxZ3TsD",
+        "resultXdr": "AAAAAAAFp24AAAAAAAAAAQAAAAAAAAAYAAAAABZiId17tj6HU0cnDSIf44RCQvx4Ze+9PZivYVpJrS/TAAAAAA==",
+        "resultMetaXdr": "AAAABAAAAAAAAAACAAAAAwAFJXgAAAAAAAAAAJYNE2uA3gelZ8DYHsfdBIy23sZIr8nf9wf6L9Zp/jTpAAAAFsrsGzEAAA1qAAAVwwAAAAEAAAAAAAAAAAAAAAAAAQEBAAAAAQAAAAChM5sgwhIdyIwqcgCD9fwQBNYj/ox4Aw054hQxzKXZYAAAAAEAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAEAAAAAAAAAAwAAAAAABSU8AAAAAGhstlAAAAAAAAAAAQAFJXgAAAAAAAAAAJYNE2uA3gelZ8DYHsfdBIy23sZIr8nf9wf6L9Zp/jTpAAAAFsrsGzEAAA1qAAAVxAAAAAEAAAAAAAAAAAAAAAAAAQEBAAAAAQAAAAChM5sgwhIdyIwqcgCD9fwQBNYj/ox4Aw054hQxzKXZYAAAAAEAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAEAAAAAAAAAAwAAAAAABSV4AAAAAGhst3wAAAAAAAAAAQAAAAAAAAAOAAAAAwAFJTwAAAAGAAAAAAAAAAEqt/Rn0ZL8sq76E44Krh9ZYhZpLV49YxosLugeJjq4PwAAABQAAAABAAAAEwAAAADaZ5h4OOy0NoTgqFsSMHHBZ2BWo+ttPZwC2FftqORNwwAAAAEAAAAPAAAADgAAAAVhZG1pbgAAAAAAABIAAAAAAAAAAJYNE2uA3gelZ8DYHsfdBIy23sZIr8nf9wf6L9Zp/jTpAAAADgAAAAphc3NldF90dGxzAAAAAAAQAAAAAQAAAAAAAAAOAAAABmFzc2V0cwAAAAAAEAAAAAEAAAAHAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABLH5dkYL+BORXImsTnZP2P5eUUBSUtBUr2CqINF2cq2UAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAHSXSYIa79oluHQAHW5pRvejjN21RnZnNCH0sSNBE4FwQAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAAQNsQWZ0O43FGKVwnNQb73Fb8k8DG+dEYKpzAL3nWeMVAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABpwrZOHKolMpzUngjpVN0fvP6eQACmnfUvchJrBqHThMAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAE4PCZRN876zenIEPbQW6JFAmed8Z68VxHSATEED5wr6gAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAAUERMTiMWywKwo7JTTyHAexwihJiFQRSQ7R2FXxBE/2tAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABgoavkxQqSDdQ0Z3vRlwVqAiggskSD6a4g7Zql4s3jpYAAAAOAAAACmJhc2VfYXNzZXQAAAAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAATRO7qcufYlaCCIeG6YGn6tt1Va2Xd726owvhPtmIFKTAAAADgAAAAhkZWNpbWFscwAAAAMAAAAOAAAADgAAAA5sYXN0X3RpbWVzdGFtcAAAAAAABQAAAZfop8rAAAAADgAAAAZwZXJpb2QAAAAAAAUAAAAABSZcAAAAAA4AAAAKcmVzb2x1dGlvbgAAAAAAAwAEk+AAAAASAAAAAQNsQWZ0O43FGKVwnNQb73Fb8k8DG+dEYKpzAL3nWeMVAAAAAwAAAAIAAAASAAAAASx+XZGC/gTkVyJrE52T9j+XlFAUlLQVK9gqiDRdnKtlAAAAAwAAAAAAAAASAAAAATg8JlE3zvrN6cgQ9tBbokUCZ53xnrxXEdIBMQQPnCvqAAAAAwAAAAQAAAASAAAAAUERMTiMWywKwo7JTTyHAexwihJiFQRSQ7R2FXxBE/2tAAAAAwAAAAUAAAASAAAAAYKGr5MUKkg3UNGd70ZcFagIoILJEg+muIO2apeLN46WAAAAAwAAAAYAAAASAAAAAacK2ThyqJTKc1J4I6VTdH7z+nkAApp31L3ISawah04TAAAAAwAAAAMAAAASAAAAAdJdJghrv2iW4dAAdbmlG96OM3bVGdmc0IfSxI0ETgXBAAAAAwAAAAEAAAAAAAAAAQAFJXgAAAAGAAAAAAAAAAEqt/Rn0ZL8sq76E44Krh9ZYhZpLV49YxosLugeJjq4PwAAABQAAAABAAAAEwAAAADaZ5h4OOy0NoTgqFsSMHHBZ2BWo+ttPZwC2FftqORNwwAAAAEAAAAPAAAADgAAAAVhZG1pbgAAAAAAABIAAAAAAAAAAJYNE2uA3gelZ8DYHsfdBIy23sZIr8nf9wf6L9Zp/jTpAAAADgAAAAphc3NldF90dGxzAAAAAAAQAAAAAQAAAAAAAAAOAAAABmFzc2V0cwAAAAAAEAAAAAEAAAAHAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABLH5dkYL+BORXImsTnZP2P5eUUBSUtBUr2CqINF2cq2UAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAHSXSYIa79oluHQAHW5pRvejjN21RnZnNCH0sSNBE4FwQAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAAQNsQWZ0O43FGKVwnNQb73Fb8k8DG+dEYKpzAL3nWeMVAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABpwrZOHKolMpzUngjpVN0fvP6eQACmnfUvchJrBqHThMAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAE4PCZRN876zenIEPbQW6JFAmed8Z68VxHSATEED5wr6gAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAAUERMTiMWywKwo7JTTyHAexwihJiFQRSQ7R2FXxBE/2tAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABgoavkxQqSDdQ0Z3vRlwVqAiggskSD6a4g7Zql4s3jpYAAAAOAAAACmJhc2VfYXNzZXQAAAAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAATRO7qcufYlaCCIeG6YGn6tt1Va2Xd726owvhPtmIFKTAAAADgAAAAhkZWNpbWFscwAAAAMAAAAOAAAADgAAAA5sYXN0X3RpbWVzdGFtcAAAAAAABQAAAZforF6gAAAADgAAAAZwZXJpb2QAAAAAAAUAAAAABSZcAAAAAA4AAAAKcmVzb2x1dGlvbgAAAAAAAwAEk+AAAAASAAAAAQNsQWZ0O43FGKVwnNQb73Fb8k8DG+dEYKpzAL3nWeMVAAAAAwAAAAIAAAASAAAAASx+XZGC/gTkVyJrE52T9j+XlFAUlLQVK9gqiDRdnKtlAAAAAwAAAAAAAAASAAAAATg8JlE3zvrN6cgQ9tBbokUCZ53xnrxXEdIBMQQPnCvqAAAAAwAAAAQAAAASAAAAAUERMTiMWywKwo7JTTyHAexwihJiFQRSQ7R2FXxBE/2tAAAAAwAAAAUAAAASAAAAAYKGr5MUKkg3UNGd70ZcFagIoILJEg+muIO2apeLN46WAAAAAwAAAAYAAAASAAAAAacK2ThyqJTKc1J4I6VTdH7z+nkAApp31L3ISawah04TAAAAAwAAAAMAAAASAAAAAdJdJghrv2iW4dAAdbmlG96OM3bVGdmc0IfSxI0ETgXBAAAAAwAAAAEAAAAAAAAAAAAFJXgAAAAJRB4HfTX+gh+4blV53fjKVsJ3af9ktmY+eVlEh/d6rJgABWj5AAAAAAAAAAAABSV4AAAABgAAAAAAAAABKrf0Z9GS/LKu+hOOCq4fWWIWaS1ePWMaLC7oHiY6uD8AAAAJAAABl+isXqAAAAAAAAAABAAAAAAAAAAKAAAAAAAAAAAAAAAKQaE8tQAAAAAAAAAAAAUleAAAAAlTk2Isx+HESCcyRfNCFOiK9B8bryCkXntYex9i2xerXAAFaPkAAAAAAAAAAAAFJXgAAAAGAAAAAAAAAAEqt/Rn0ZL8sq76E44Krh9ZYhZpLV49YxosLugeJjq4PwAAAAkAAAGX6KxeoAAAAAAAAAAGAAAAAAAAAAoAAAAAAAAAAAAAYLyUqAn+AAAAAAAAAAAABSV4AAAABgAAAAAAAAABKrf0Z9GS/LKu+hOOCq4fWWIWaS1ePWMaLC7oHiY6uD8AAAAJAAABl+isXqAAAAAAAAAABQAAAAAAAAAKAAAAAAAAAAAAAAASRzQWKwAAAAAAAAAAAAUleAAAAAYAAAAAAAAAASq39GfRkvyyrvoTjgquH1liFmktXj1jGiwu6B4mOrg/AAAACQAAAZforF6gAAAAAAAAAAMAAAAAAAAACgAAAAAAAAAAAAAAGXAeu6MAAAAAAAAAAAAFJXgAAAAJb10K4vAg2FMNYDYJPGj0A8Bq0N8tVLsivGFWnKWRlQ0ABWj5AAAAAAAAAAAABSV4AAAACRp0CfdyyxTguzTsyyDMIMf59bXkAsJ4BQHWh7aDOrEvAAVo+QAAAAAAAAAAAAUleAAAAAYAAAAAAAAAASq39GfRkvyyrvoTjgquH1liFmktXj1jGiwu6B4mOrg/AAAACQAAAZforF6gAAAAAAAAAAEAAAAAAAAACgAAAAAAAAAAAAAAFAjvQXUAAAAAAAAAAAAFJXgAAAAGAAAAAAAAAAEqt/Rn0ZL8sq76E44Krh9ZYhZpLV49YxosLugeJjq4PwAAAAkAAAGX6KxeoAAAAAAAAAACAAAAAAAAAAoAAAAAAAAAAAAAWvLhNpYXAAAAAAAAAAAABSV4AAAACXgGZlWaxEkY9Fou1Sux2Kr347xqlEECbgm/bYOHoMCyAAVo+QAAAAAAAAAAAAUleAAAAAmW36YQGgajHLVN9gVIWHPl+aLklfo7/rIc1HpxoPcZyQAFaPkAAAAAAAAAAQAAAAAAAAABKrf0Z9GS/LKu+hOOCq4fWWIWaS1ePWMaLC7oHiY6uD8AAAABAAAAAAAAAAMAAAAPAAAACXJlZmxlY3RvcgAAAAAAAA8AAAAGcHJpY2VzAAAAAAAPAAAABnVwZGF0ZQAAAAAAEAAAAAEAAAAHAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABLH5dkYL+BORXImsTnZP2P5eUUBSUtBUr2CqINF2cq2UAAAAKAAAAAAAAAAAAAAAAAAAAAAAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAAdJdJghrv2iW4dAAdbmlG96OM3bVGdmc0IfSxI0ETgXBAAAACgAAAAAAAAAAAAAAFAjvQXUAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAEDbEFmdDuNxRilcJzUG+9xW/JPAxvnRGCqcwC951njFQAAAAoAAAAAAAAAAAAAWvLhNpYXAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABpwrZOHKolMpzUngjpVN0fvP6eQACmnfUvchJrBqHThMAAAAKAAAAAAAAAAAAAAAZcB67owAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAATg8JlE3zvrN6cgQ9tBbokUCZ53xnrxXEdIBMQQPnCvqAAAACgAAAAAAAAAAAAAACkGhPLUAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAFBETE4jFssCsKOyU08hwHscIoSYhUEUkO0dhV8QRP9rQAAAAoAAAAAAAAAAAAAABJHNBYrAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABgoavkxQqSDdQ0Z3vRlwVqAiggskSD6a4g7Zql4s3jpYAAAAKAAAAAAAAAAAAAGC8lKgJ/gAAAAIAAAADAAUleAAAAAAAAAAAlg0Ta4DeB6VnwNgex90EjLbexkivyd/3B/ov1mn+NOkAAAAWyuwbMQAADWoAABXEAAAAAQAAAAAAAAAAAAAAAAABAQEAAAABAAAAAKEzmyDCEh3IjCpyAIP1/BAE1iP+jHgDDTniFDHMpdlgAAAAAQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAQAAAAAAAAADAAAAAAAFJXgAAAAAaGy3fAAAAAAAAAABAAUleAAAAAAAAAAAlg0Ta4DeB6VnwNgex90EjLbexkivyd/3B/ov1mn+NOkAAAAWy38KpwAADWoAABXEAAAAAQAAAAAAAAAAAAAAAAABAQEAAAABAAAAAKEzmyDCEh3IjCpyAIP1/BAE1iP+jHgDDTniFDHMpdlgAAAAAQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAQAAAAAAAAADAAAAAAAFJXgAAAAAaGy3fAAAAAAAAAABAAAAAQAAAAAAAAAAAAQl+gAAAAAAAYEQAAAAAAABYcgAAAABAAAAAQAAAAIAAAAAAAAAAAAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAAAEAAAAAAAAAAgAAAA8AAAADZmVlAAAAABIAAAAAAAAAAJYNE2uA3gelZ8DYHsfdBIy23sZIr8nf9wf6L9Zp/jTpAAAACgAAAAAAAAAAAAAAAACYluQAAAABAAAAAAAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAAAEAAAAAAAAAAgAAAA8AAAADZmVlAAAAABIAAAAAAAAAAJYNE2uA3gelZ8DYHsfdBIy23sZIr8nf9wf6L9Zp/jTpAAAACv////////////////9tEIoAAAAWAAAAAQAAAAAAAAAAAAAAAgAAAAAAAAADAAAADwAAAAdmbl9jYWxsAAAAAA0AAAAgKrf0Z9GS/LKu+hOOCq4fWWIWaS1ePWMaLC7oHiY6uD8AAAAPAAAACXNldF9wcmljZQAAAAAAABAAAAABAAAAAgAAABAAAAABAAAABwAAAAoAAAAAAAAAAAAAAAAAAAAAAAAACgAAAAAAAAAAAAAAFAjvQXUAAAAKAAAAAAAAAAAAAFry4TaWFwAAAAoAAAAAAAAAAAAAABlwHrujAAAACgAAAAAAAAAAAAAACkGhPLUAAAAKAAAAAAAAAAAAAAASRzQWKwAAAAoAAAAAAAAAAAAAYLyUqAn+AAAABQAAAZforF6gAAAAAQAAAAAAAAABKrf0Z9GS/LKu+hOOCq4fWWIWaS1ePWMaLC7oHiY6uD8AAAABAAAAAAAAAAMAAAAPAAAACXJlZmxlY3RvcgAAAAAAAA8AAAAGcHJpY2VzAAAAAAAPAAAABnVwZGF0ZQAAAAAAEAAAAAEAAAAHAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABLH5dkYL+BORXImsTnZP2P5eUUBSUtBUr2CqINF2cq2UAAAAKAAAAAAAAAAAAAAAAAAAAAAAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAAdJdJghrv2iW4dAAdbmlG96OM3bVGdmc0IfSxI0ETgXBAAAACgAAAAAAAAAAAAAAFAjvQXUAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAEDbEFmdDuNxRilcJzUG+9xW/JPAxvnRGCqcwC951njFQAAAAoAAAAAAAAAAAAAWvLhNpYXAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABpwrZOHKolMpzUngjpVN0fvP6eQACmnfUvchJrBqHThMAAAAKAAAAAAAAAAAAAAAZcB67owAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAATg8JlE3zvrN6cgQ9tBbokUCZ53xnrxXEdIBMQQPnCvqAAAACgAAAAAAAAAAAAAACkGhPLUAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAFBETE4jFssCsKOyU08hwHscIoSYhUEUkO0dhV8QRP9rQAAAAoAAAAAAAAAAAAAABJHNBYrAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABgoavkxQqSDdQ0Z3vRlwVqAiggskSD6a4g7Zql4s3jpYAAAAKAAAAAAAAAAAAAGC8lKgJ/gAAAAEAAAAAAAAAASq39GfRkvyyrvoTjgquH1liFmktXj1jGiwu6B4mOrg/AAAAAgAAAAAAAAACAAAADwAAAAlmbl9yZXR1cm4AAAAAAAAPAAAACXNldF9wcmljZQAAAAAAAAEAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAKcmVhZF9lbnRyeQAAAAAABQAAAAAAAAAIAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAC3dyaXRlX2VudHJ5AAAAAAUAAAAAAAAABwAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAABBsZWRnZXJfcmVhZF9ieXRlAAAABQAAAAAAAFhgAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEWxlZGdlcl93cml0ZV9ieXRlAAAAAAAABQAAAAAAAAccAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADXJlYWRfa2V5X2J5dGUAAAAAAAAFAAAAAAAAAdQAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAOd3JpdGVfa2V5X2J5dGUAAAAAAAUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAAA5yZWFkX2RhdGFfYnl0ZQAAAAAABQAAAAAAAATcAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD3dyaXRlX2RhdGFfYnl0ZQAAAAAFAAAAAAAABxwAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAOcmVhZF9jb2RlX2J5dGUAAAAAAAUAAAAAAABThAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAAA93cml0ZV9jb2RlX2J5dGUAAAAABQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACmVtaXRfZXZlbnQAAAAAAAUAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAAA9lbWl0X2V2ZW50X2J5dGUAAAAABQAAAAAAAAMwAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACGNwdV9pbnNuAAAABQAAAAAARc1cAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACG1lbV9ieXRlAAAABQAAAAAAIBuIAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEWludm9rZV90aW1lX25zZWNzAAAAAAAABQAAAAAAGWpZAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD21heF9yd19rZXlfYnl0ZQAAAAAFAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAQbWF4X3J3X2RhdGFfYnl0ZQAAAAUAAAAAAAAE3AAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAABBtYXhfcndfY29kZV9ieXRlAAAABQAAAAAAAFOEAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAE21heF9lbWl0X2V2ZW50X2J5dGUAAAAABQAAAAAAAAMw",
+        "diagnosticEventsXdr": [
+          "AAAAAQAAAAAAAAAAAAAAAgAAAAAAAAADAAAADwAAAAdmbl9jYWxsAAAAAA0AAAAgKrf0Z9GS/LKu+hOOCq4fWWIWaS1ePWMaLC7oHiY6uD8AAAAPAAAACXNldF9wcmljZQAAAAAAABAAAAABAAAAAgAAABAAAAABAAAABwAAAAoAAAAAAAAAAAAAAAAAAAAAAAAACgAAAAAAAAAAAAAAFAjvQXUAAAAKAAAAAAAAAAAAAFry4TaWFwAAAAoAAAAAAAAAAAAAABlwHrujAAAACgAAAAAAAAAAAAAACkGhPLUAAAAKAAAAAAAAAAAAAAASRzQWKwAAAAoAAAAAAAAAAAAAYLyUqAn+AAAABQAAAZforF6g",
+          "AAAAAQAAAAAAAAABKrf0Z9GS/LKu+hOOCq4fWWIWaS1ePWMaLC7oHiY6uD8AAAABAAAAAAAAAAMAAAAPAAAACXJlZmxlY3RvcgAAAAAAAA8AAAAGcHJpY2VzAAAAAAAPAAAABnVwZGF0ZQAAAAAAEAAAAAEAAAAHAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABLH5dkYL+BORXImsTnZP2P5eUUBSUtBUr2CqINF2cq2UAAAAKAAAAAAAAAAAAAAAAAAAAAAAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAAdJdJghrv2iW4dAAdbmlG96OM3bVGdmc0IfSxI0ETgXBAAAACgAAAAAAAAAAAAAAFAjvQXUAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAEDbEFmdDuNxRilcJzUG+9xW/JPAxvnRGCqcwC951njFQAAAAoAAAAAAAAAAAAAWvLhNpYXAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABpwrZOHKolMpzUngjpVN0fvP6eQACmnfUvchJrBqHThMAAAAKAAAAAAAAAAAAAAAZcB67owAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAATg8JlE3zvrN6cgQ9tBbokUCZ53xnrxXEdIBMQQPnCvqAAAACgAAAAAAAAAAAAAACkGhPLUAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAFBETE4jFssCsKOyU08hwHscIoSYhUEUkO0dhV8QRP9rQAAAAoAAAAAAAAAAAAAABJHNBYrAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABgoavkxQqSDdQ0Z3vRlwVqAiggskSD6a4g7Zql4s3jpYAAAAKAAAAAAAAAAAAAGC8lKgJ/g==",
+          "AAAAAQAAAAAAAAABKrf0Z9GS/LKu+hOOCq4fWWIWaS1ePWMaLC7oHiY6uD8AAAACAAAAAAAAAAIAAAAPAAAACWZuX3JldHVybgAAAAAAAA8AAAAJc2V0X3ByaWNlAAAAAAAAAQ==",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACnJlYWRfZW50cnkAAAAAAAUAAAAAAAAACA==",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAC3dyaXRlX2VudHJ5AAAAAAUAAAAAAAAABw==",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEGxlZGdlcl9yZWFkX2J5dGUAAAAFAAAAAAAAWGA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEWxlZGdlcl93cml0ZV9ieXRlAAAAAAAABQAAAAAAAAcc",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADXJlYWRfa2V5X2J5dGUAAAAAAAAFAAAAAAAAAdQ=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADndyaXRlX2tleV9ieXRlAAAAAAAFAAAAAAAAAAA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADnJlYWRfZGF0YV9ieXRlAAAAAAAFAAAAAAAABNw=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD3dyaXRlX2RhdGFfYnl0ZQAAAAAFAAAAAAAABxw=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADnJlYWRfY29kZV9ieXRlAAAAAAAFAAAAAAAAU4Q=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD3dyaXRlX2NvZGVfYnl0ZQAAAAAFAAAAAAAAAAA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACmVtaXRfZXZlbnQAAAAAAAUAAAAAAAAAAQ==",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD2VtaXRfZXZlbnRfYnl0ZQAAAAAFAAAAAAAAAzA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACGNwdV9pbnNuAAAABQAAAAAARc1c",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACG1lbV9ieXRlAAAABQAAAAAAIBuI",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEWludm9rZV90aW1lX25zZWNzAAAAAAAABQAAAAAAGWpZ",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD21heF9yd19rZXlfYnl0ZQAAAAAFAAAAAAAAAEA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEG1heF9yd19kYXRhX2J5dGUAAAAFAAAAAAAABNw=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEG1heF9yd19jb2RlX2J5dGUAAAAFAAAAAAAAU4Q=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAE21heF9lbWl0X2V2ZW50X2J5dGUAAAAABQAAAAAAAAMw"
+        ],
+        "events": {
+          "transactionEventsXdr": [
+            "AAAAAAAAAAAAAAAB15KLcsJwPM/q9+uf9O9NUEpVqLl5/JtFDqLIQrTRzmEAAAABAAAAAAAAAAIAAAAPAAAAA2ZlZQAAAAASAAAAAAAAAACWDRNrgN4HpWfA2B7H3QSMtt7GSK/J3/cH+i/Waf406QAAAAoAAAAAAAAAAAAAAAAAmJbk",
+            "AAAAAQAAAAAAAAAB15KLcsJwPM/q9+uf9O9NUEpVqLl5/JtFDqLIQrTRzmEAAAABAAAAAAAAAAIAAAAPAAAAA2ZlZQAAAAASAAAAAAAAAACWDRNrgN4HpWfA2B7H3QSMtt7GSK/J3/cH+i/Waf406QAAAAr/////////////////bRCK"
+          ],
+          "contractEventsXdr": [
+            [
+              "AAAAAAAAAAEqt/Rn0ZL8sq76E44Krh9ZYhZpLV49YxosLugeJjq4PwAAAAEAAAAAAAAAAwAAAA8AAAAJcmVmbGVjdG9yAAAAAAAADwAAAAZwcmljZXMAAAAAAA8AAAAGdXBkYXRlAAAAAAAQAAAAAQAAAAcAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAEsfl2Rgv4E5FciaxOdk/Y/l5RQFJS0FSvYKog0XZyrZQAAAAoAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAAB0l0mCGu/aJbh0AB1uaUb3o4zdtUZ2ZzQh9LEjQROBcEAAAAKAAAAAAAAAAAAAAAUCO9BdQAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAAQNsQWZ0O43FGKVwnNQb73Fb8k8DG+dEYKpzAL3nWeMVAAAACgAAAAAAAAAAAABa8uE2lhcAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAGnCtk4cqiUynNSeCOlU3R+8/p5AAKad9S9yEmsGodOEwAAAAoAAAAAAAAAAAAAABlwHrujAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAdTdGVsbGFyAAAAABIAAAABODwmUTfO+s3pyBD20FuiRQJnnfGevFcR0gExBA+cK+oAAAAKAAAAAAAAAAAAAAAKQaE8tQAAABAAAAABAAAAAgAAABAAAAABAAAAAgAAAA8AAAAHU3RlbGxhcgAAAAASAAAAAUERMTiMWywKwo7JTTyHAexwihJiFQRSQ7R2FXxBE/2tAAAACgAAAAAAAAAAAAAAEkc0FisAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAAB1N0ZWxsYXIAAAAAEgAAAAGChq+TFCpIN1DRne9GXBWoCKCCyRIPpriDtmqXizeOlgAAAAoAAAAAAAAAAAAAYLyUqAn+"
+            ]
+          ]
+        },
+        "ledger": 337272,
+        "createdAt": 1751955324
+      },
+      {
+        "status": "SUCCESS",
+        "txHash": "ad4e1293b32dfa1e9204892b64088d61465337abdf4c2eee2e9d0fa8095bf87a",
+        "applicationOrder": 5,
+        "feeBump": false,
+        "envelopeXdr": "AAAAAgAAAADuBg+afmvWN9+nlruudR93UO1rDpTe8i6yxgPgBKoBVwExLQAAAA2lAAAVwgAAAAEAAAAAAAAAAAAAAABobLeMAAAAAAAAAAEAAAABAAAAAO4GD5p+a9Y336eWu651H3dQ7WsOlN7yLrLGA+AEqgFXAAAAGAAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAJc2V0X3ByaWNlAAAAAAAAAgAAABAAAAABAAAACQAAAAoAAAAAAAAAAAAAar7vtc6AAAAACgAAAAAAAAAAAAB77nns4IAAAAAKAAAAAAAAAAAAAHIYVPMbgAAAAAoAAAAAAAAAAAAAQpzRyeGAAAAACgAAAAAAAAAAAAAE4WY2fkAAAAAKAAAAAAAAAAAAAAASduMCAAAAAAoAAAAAAAAAAAAAEKOEVuGAAAAACgAAAAAAAAAAAAACzMdm/4AAAAAKAAAAAAAAAAAEoCi1tZQ/gAAAAAUAAAGX6KxeoAAAAAEAAAAAAAAAAAAAAAGlJx5hXtZLUEEJA9akotOUWIv8dYiEoyuKQmACnKsp1gAAAAlzZXRfcHJpY2UAAAAAAAACAAAAEAAAAAEAAAAJAAAACgAAAAAAAAAAAABqvu+1zoAAAAAKAAAAAAAAAAAAAHvueezggAAAAAoAAAAAAAAAAAAAchhU8xuAAAAACgAAAAAAAAAAAABCnNHJ4YAAAAAKAAAAAAAAAAAAAAThZjZ+QAAAAAoAAAAAAAAAAAAAABJ24wIAAAAACgAAAAAAAAAAAAAQo4RW4YAAAAAKAAAAAAAAAAAAAALMx2b/gAAAAAoAAAAAAAAAAASgKLW1lD+AAAAABQAAAZforF6gAAAAAAAAAAEAAAAAAAAAAQAAAAfaZ5h4OOy0NoTgqFsSMHHBZ2BWo+ttPZwC2FftqORNwwAAAAoAAAAGAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAACQAAAZforF6gAAAAAAAAAAAAAAAAAAAABgAAAAGlJx5hXtZLUEEJA9akotOUWIv8dYiEoyuKQmACnKsp1gAAAAkAAAGX6KxeoAAAAAAAAAABAAAAAAAAAAYAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAJAAABl+isXqAAAAAAAAAAAgAAAAAAAAAGAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAACQAAAZforF6gAAAAAAAAAAMAAAAAAAAABgAAAAGlJx5hXtZLUEEJA9akotOUWIv8dYiEoyuKQmACnKsp1gAAAAkAAAGX6KxeoAAAAAAAAAAEAAAAAAAAAAYAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAJAAABl+isXqAAAAAAAAAABQAAAAAAAAAGAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAACQAAAZforF6gAAAAAAAAAAYAAAAAAAAABgAAAAGlJx5hXtZLUEEJA9akotOUWIv8dYiEoyuKQmACnKsp1gAAAAkAAAGX6KxeoAAAAAAAAAAHAAAAAAAAAAYAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAJAAABl+isXqAAAAAAAAAACAAAAAAAAAAGAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAAFAAAAAEAmJaAAACcQAAAC7gAAAAAAJiWgAAAAAHMpdlgAAAAQEgm+1bCDSJvdFDSnyeZmEPiZMhmwZmivK2nygo7vIaoIcb88CZBs6VAKQweX0EGp54vhFUUTIK6z0cTSJtZMwo=",
+        "resultXdr": "AAAAAAAHMRAAAAAAAAAAAQAAAAAAAAAYAAAAABEOa41BV0w6YargAzlyRUm7wx575S/rr4HPaL54Gz8aAAAAAA==",
+        "resultMetaXdr": "AAAABAAAAAAAAAACAAAAAwAFJXgAAAAAAAAAAO4GD5p+a9Y336eWu651H3dQ7WsOlN7yLrLGA+AEqgFXAAAAFqvoAosAAA2lAAAVwQAAAAEAAAAAAAAAAAAAAAAAAQEBAAAAAQAAAAChM5sgwhIdyIwqcgCD9fwQBNYj/ox4Aw054hQxzKXZYAAAAAEAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAEAAAAAAAAAAwAAAAAABSU8AAAAAGhstlAAAAAAAAAAAQAFJXgAAAAAAAAAAO4GD5p+a9Y336eWu651H3dQ7WsOlN7yLrLGA+AEqgFXAAAAFqvoAosAAA2lAAAVwgAAAAEAAAAAAAAAAAAAAAAAAQEBAAAAAQAAAAChM5sgwhIdyIwqcgCD9fwQBNYj/ox4Aw054hQxzKXZYAAAAAEAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAEAAAAAAAAAAwAAAAAABSV4AAAAAGhst3wAAAAAAAAAAQAAAAAAAAAUAAAAAAAFJXgAAAAJTFJ7hg0YekCP6O62XQDcF34hNHlC6Yogiee9kKZaq54ABWj5AAAAAAAAAAAABSV4AAAABgAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAJAAABl+isXqAAAAAAAAAABwAAAAAAAAAKAAAAAAAAAAAAAALMx2b/gAAAAAAAAAAAAAUleAAAAAYAAAAAAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAACQAAAZforF6gAAAAAAAAAAYAAAAAAAAACgAAAAAAAAAAAAAQo4RW4YAAAAAAAAAAAwAFJTwAAAAGAAAAAAAAAAGlJx5hXtZLUEEJA9akotOUWIv8dYiEoyuKQmACnKsp1gAAABQAAAABAAAAEwAAAADaZ5h4OOy0NoTgqFsSMHHBZ2BWo+ttPZwC2FftqORNwwAAAAEAAAARAAAADgAAAAVhZG1pbgAAAAAAABIAAAAAAAAAAO4GD5p+a9Y336eWu651H3dQ7WsOlN7yLrLGA+AEqgFXAAAADgAAAAphc3NldF90dGxzAAAAAAAQAAAAAQAAAAAAAAAOAAAABmFzc2V0cwAAAAAAEAAAAAEAAAAJAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRVVSAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA0dCUAAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANDSEYAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQ0FEAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA01YTgAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANBUlMAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQlJMAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA1RIQgAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANYQVUAAAAADgAAAApiYXNlX2Fzc2V0AAAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANVU0QAAAAADgAAAAhkZWNpbWFscwAAAAMAAAAOAAAADgAAAA5sYXN0X3RpbWVzdGFtcAAAAAAABQAAAZfop8rAAAAADgAAAAZwZXJpb2QAAAAAAAUAAAAABSZcAAAAAA4AAAAKcmVzb2x1dGlvbgAAAAAAAwAEk+AAAAAPAAAAA0FSUwAAAAADAAAABQAAAA8AAAADQlJMAAAAAAMAAAAGAAAADwAAAANDQUQAAAAAAwAAAAMAAAAPAAAAA0NIRgAAAAADAAAAAgAAAA8AAAADRVVSAAAAAAMAAAAAAAAADwAAAANHQlAAAAAAAwAAAAEAAAAPAAAAA01YTgAAAAADAAAABAAAAA8AAAADVEhCAAAAAAMAAAAHAAAADwAAAANYQVUAAAAAAwAAAAgAAAAAAAAAAQAFJXgAAAAGAAAAAAAAAAGlJx5hXtZLUEEJA9akotOUWIv8dYiEoyuKQmACnKsp1gAAABQAAAABAAAAEwAAAADaZ5h4OOy0NoTgqFsSMHHBZ2BWo+ttPZwC2FftqORNwwAAAAEAAAARAAAADgAAAAVhZG1pbgAAAAAAABIAAAAAAAAAAO4GD5p+a9Y336eWu651H3dQ7WsOlN7yLrLGA+AEqgFXAAAADgAAAAphc3NldF90dGxzAAAAAAAQAAAAAQAAAAAAAAAOAAAABmFzc2V0cwAAAAAAEAAAAAEAAAAJAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRVVSAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA0dCUAAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANDSEYAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQ0FEAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA01YTgAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANBUlMAAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQlJMAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA1RIQgAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANYQVUAAAAADgAAAApiYXNlX2Fzc2V0AAAAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANVU0QAAAAADgAAAAhkZWNpbWFscwAAAAMAAAAOAAAADgAAAA5sYXN0X3RpbWVzdGFtcAAAAAAABQAAAZforF6gAAAADgAAAAZwZXJpb2QAAAAAAAUAAAAABSZcAAAAAA4AAAAKcmVzb2x1dGlvbgAAAAAAAwAEk+AAAAAPAAAAA0FSUwAAAAADAAAABQAAAA8AAAADQlJMAAAAAAMAAAAGAAAADwAAAANDQUQAAAAAAwAAAAMAAAAPAAAAA0NIRgAAAAADAAAAAgAAAA8AAAADRVVSAAAAAAMAAAAAAAAADwAAAANHQlAAAAAAAwAAAAEAAAAPAAAAA01YTgAAAAADAAAABAAAAA8AAAADVEhCAAAAAAMAAAAHAAAADwAAAANYQVUAAAAAAwAAAAgAAAAAAAAAAAAFJXgAAAAJTBIOCKbv/+1/9CYra1RMqev8t31JP4xtN3HQcrApd+gABWj5AAAAAAAAAAAABSV4AAAABgAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAJAAABl+isXqAAAAAAAAAAAQAAAAAAAAAKAAAAAAAAAAAAAHvueezggAAAAAAAAAAAAAUleAAAAAYAAAAAAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAACQAAAZforF6gAAAAAAAAAAUAAAAAAAAACgAAAAAAAAAAAAAAEnbjAgAAAAAAAAAAAAAFJXgAAAAJrs0QqhKj1rGtzDDrF15UcZKQAMrbnL3cpKU2JJXi7f4ABWj5AAAAAAAAAAAABSV4AAAACbWHiKy0lbSAGDTH1wkwUqR3TQ/Fg1L2IaQ1dmFWkEh2AAVo+QAAAAAAAAAAAAUleAAAAAYAAAAAAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAACQAAAZforF6gAAAAAAAAAAQAAAAAAAAACgAAAAAAAAAAAAAE4WY2fkAAAAAAAAAAAAAFJXgAAAAJh003w9kt+aRpwy9fdIdAVbAqe351EmUps1Dn+AW9rl0ABWj5AAAAAAAAAAAABSV4AAAACRwH6p7HoKpXDI9DS/+TgFAaiv9Jq3RM0QEqG21MQUPOAAVo+QAAAAAAAAAAAAUleAAAAAYAAAAAAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAACQAAAZforF6gAAAAAAAAAAgAAAAAAAAACgAAAAAAAAAABKAotbWUP4AAAAAAAAAAAAAFJXgAAAAJypa225pMujmRlDXUPQYIw16s5NkjCTCg2v5MS7besVUABWj5AAAAAAAAAAAABSV4AAAABgAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAJAAABl+isXqAAAAAAAAAAAAAAAAAAAAAKAAAAAAAAAAAAAGq+77XOgAAAAAAAAAAAAAUleAAAAAYAAAAAAAAAAaUnHmFe1ktQQQkD1qSi05RYi/x1iISjK4pCYAKcqynWAAAACQAAAZforF6gAAAAAAAAAAIAAAAAAAAACgAAAAAAAAAAAAByGFTzG4AAAAAAAAAAAAAFJXgAAAAJhyH7/lHoFoX7sLuNWBBBwviQCJidW44xkUo9hzgAVcYABWj5AAAAAAAAAAAABSV4AAAABgAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAJAAABl+isXqAAAAAAAAAAAwAAAAAAAAAKAAAAAAAAAAAAAEKc0cnhgAAAAAAAAAAAAAUleAAAAAkS+XxH4Tmpojq4OGNei7rBTadgDcosuDhnRMerOpeyfwAFaPkAAAAAAAAAAQAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAABAAAAAAAAAAMAAAAPAAAACXJlZmxlY3RvcgAAAAAAAA8AAAAGcHJpY2VzAAAAAAAPAAAABnVwZGF0ZQAAAAAAEAAAAAEAAAAJAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRVVSAAAAAAoAAAAAAAAAAAAAar7vtc6AAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADR0JQAAAAAAoAAAAAAAAAAAAAe+557OCAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQ0hGAAAAAAoAAAAAAAAAAAAAchhU8xuAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQ0FEAAAAAAoAAAAAAAAAAAAAQpzRyeGAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADTVhOAAAAAAoAAAAAAAAAAAAABOFmNn5AAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQVJTAAAAAAoAAAAAAAAAAAAAABJ24wIAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQlJMAAAAAAoAAAAAAAAAAAAAEKOEVuGAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADVEhCAAAAAAoAAAAAAAAAAAAAAszHZv+AAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADWEFVAAAAAAoAAAAAAAAAAASgKLW1lD+AAAAAAgAAAAMABSV4AAAAAAAAAADuBg+afmvWN9+nlruudR93UO1rDpTe8i6yxgPgBKoBVwAAABar6AKLAAANpQAAFcIAAAABAAAAAAAAAAAAAAAAAAEBAQAAAAEAAAAAoTObIMISHciMKnIAg/X8EATWI/6MeAMNOeIUMcyl2WAAAAABAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAAAAAABAAAAAAAAAAMAAAAAAAUleAAAAABobLd8AAAAAAAAAAEABSV4AAAAAAAAAADuBg+afmvWN9+nlruudR93UO1rDpTe8i6yxgPgBKoBVwAAABaseWhfAAANpQAAFcIAAAABAAAAAAAAAAAAAAAAAAEBAQAAAAEAAAAAoTObIMISHciMKnIAg/X8EATWI/6MeAMNOeIUMcyl2WAAAAABAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAAAAAABAAAAAAAAAAMAAAAAAAUleAAAAABobLd8AAAAAAAAAAEAAAABAAAAAAAAAAAABQC0AAAAAAACL/gAAAAAAAISrAAAAAEAAAABAAAAAgAAAAAAAAAAAAAAAdeSi3LCcDzP6vfrn/TvTVBKVai5efybRQ6iyEK00c5hAAAAAQAAAAAAAAACAAAADwAAAANmZWUAAAAAEgAAAAAAAAAA7gYPmn5r1jffp5a7rnUfd1Dtaw6U3vIussYD4ASqAVcAAAAKAAAAAAAAAAAAAAAAAJiW5AAAAAEAAAAAAAAAAdeSi3LCcDzP6vfrn/TvTVBKVai5efybRQ6iyEK00c5hAAAAAQAAAAAAAAACAAAADwAAAANmZWUAAAAAEgAAAAAAAAAA7gYPmn5r1jffp5a7rnUfd1Dtaw6U3vIussYD4ASqAVcAAAAK/////////////////26aLAAAABYAAAABAAAAAAAAAAAAAAACAAAAAAAAAAMAAAAPAAAAB2ZuX2NhbGwAAAAADQAAACClJx5hXtZLUEEJA9akotOUWIv8dYiEoyuKQmACnKsp1gAAAA8AAAAJc2V0X3ByaWNlAAAAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAAJAAAACgAAAAAAAAAAAABqvu+1zoAAAAAKAAAAAAAAAAAAAHvueezggAAAAAoAAAAAAAAAAAAAchhU8xuAAAAACgAAAAAAAAAAAABCnNHJ4YAAAAAKAAAAAAAAAAAAAAThZjZ+QAAAAAoAAAAAAAAAAAAAABJ24wIAAAAACgAAAAAAAAAAAAAQo4RW4YAAAAAKAAAAAAAAAAAAAALMx2b/gAAAAAoAAAAAAAAAAASgKLW1lD+AAAAABQAAAZforF6gAAAAAQAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAABAAAAAAAAAAMAAAAPAAAACXJlZmxlY3RvcgAAAAAAAA8AAAAGcHJpY2VzAAAAAAAPAAAABnVwZGF0ZQAAAAAAEAAAAAEAAAAJAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRVVSAAAAAAoAAAAAAAAAAAAAar7vtc6AAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADR0JQAAAAAAoAAAAAAAAAAAAAe+557OCAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQ0hGAAAAAAoAAAAAAAAAAAAAchhU8xuAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQ0FEAAAAAAoAAAAAAAAAAAAAQpzRyeGAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADTVhOAAAAAAoAAAAAAAAAAAAABOFmNn5AAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQVJTAAAAAAoAAAAAAAAAAAAAABJ24wIAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQlJMAAAAAAoAAAAAAAAAAAAAEKOEVuGAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADVEhCAAAAAAoAAAAAAAAAAAAAAszHZv+AAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADWEFVAAAAAAoAAAAAAAAAAASgKLW1lD+AAAAAAQAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAACAAAAAAAAAAIAAAAPAAAACWZuX3JldHVybgAAAAAAAA8AAAAJc2V0X3ByaWNlAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAAApyZWFkX2VudHJ5AAAAAAAFAAAAAAAAAAsAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAALd3JpdGVfZW50cnkAAAAABQAAAAAAAAAKAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEGxlZGdlcl9yZWFkX2J5dGUAAAAFAAAAAAAAVzQAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAARbGVkZ2VyX3dyaXRlX2J5dGUAAAAAAAAFAAAAAAAABxAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAANcmVhZF9rZXlfYnl0ZQAAAAAAAAUAAAAAAAAClAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAAA53cml0ZV9rZXlfYnl0ZQAAAAAABQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADnJlYWRfZGF0YV9ieXRlAAAAAAAFAAAAAAAAA7AAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAPd3JpdGVfZGF0YV9ieXRlAAAAAAUAAAAAAAAHEAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAAA5yZWFkX2NvZGVfYnl0ZQAAAAAABQAAAAAAAFOEAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD3dyaXRlX2NvZGVfYnl0ZQAAAAAFAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAKZW1pdF9ldmVudAAAAAAABQAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD2VtaXRfZXZlbnRfYnl0ZQAAAAAFAAAAAAAAAvwAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAIY3B1X2luc24AAAAFAAAAAABImEoAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAIbWVtX2J5dGUAAAAFAAAAAAAhGTIAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAARaW52b2tlX3RpbWVfbnNlY3MAAAAAAAAFAAAAAAAW5iQAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAAPbWF4X3J3X2tleV9ieXRlAAAAAAUAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAA8AAAAMY29yZV9tZXRyaWNzAAAADwAAABBtYXhfcndfZGF0YV9ieXRlAAAABQAAAAAAAAOwAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEG1heF9yd19jb2RlX2J5dGUAAAAFAAAAAAAAU4QAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAIAAAAPAAAADGNvcmVfbWV0cmljcwAAAA8AAAATbWF4X2VtaXRfZXZlbnRfYnl0ZQAAAAAFAAAAAAAAAvw=",
+        "diagnosticEventsXdr": [
+          "AAAAAQAAAAAAAAAAAAAAAgAAAAAAAAADAAAADwAAAAdmbl9jYWxsAAAAAA0AAAAgpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAAPAAAACXNldF9wcmljZQAAAAAAABAAAAABAAAAAgAAABAAAAABAAAACQAAAAoAAAAAAAAAAAAAar7vtc6AAAAACgAAAAAAAAAAAAB77nns4IAAAAAKAAAAAAAAAAAAAHIYVPMbgAAAAAoAAAAAAAAAAAAAQpzRyeGAAAAACgAAAAAAAAAAAAAE4WY2fkAAAAAKAAAAAAAAAAAAAAASduMCAAAAAAoAAAAAAAAAAAAAEKOEVuGAAAAACgAAAAAAAAAAAAACzMdm/4AAAAAKAAAAAAAAAAAEoCi1tZQ/gAAAAAUAAAGX6KxeoA==",
+          "AAAAAQAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAABAAAAAAAAAAMAAAAPAAAACXJlZmxlY3RvcgAAAAAAAA8AAAAGcHJpY2VzAAAAAAAPAAAABnVwZGF0ZQAAAAAAEAAAAAEAAAAJAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADRVVSAAAAAAoAAAAAAAAAAAAAar7vtc6AAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADR0JQAAAAAAoAAAAAAAAAAAAAe+557OCAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQ0hGAAAAAAoAAAAAAAAAAAAAchhU8xuAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQ0FEAAAAAAoAAAAAAAAAAAAAQpzRyeGAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADTVhOAAAAAAoAAAAAAAAAAAAABOFmNn5AAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQVJTAAAAAAoAAAAAAAAAAAAAABJ24wIAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADQlJMAAAAAAoAAAAAAAAAAAAAEKOEVuGAAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADVEhCAAAAAAoAAAAAAAAAAAAAAszHZv+AAAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADWEFVAAAAAAoAAAAAAAAAAASgKLW1lD+A",
+          "AAAAAQAAAAAAAAABpSceYV7WS1BBCQPWpKLTlFiL/HWIhKMrikJgApyrKdYAAAACAAAAAAAAAAIAAAAPAAAACWZuX3JldHVybgAAAAAAAA8AAAAJc2V0X3ByaWNlAAAAAAAAAQ==",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACnJlYWRfZW50cnkAAAAAAAUAAAAAAAAACw==",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAC3dyaXRlX2VudHJ5AAAAAAUAAAAAAAAACg==",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEGxlZGdlcl9yZWFkX2J5dGUAAAAFAAAAAAAAVzQ=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEWxlZGdlcl93cml0ZV9ieXRlAAAAAAAABQAAAAAAAAcQ",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADXJlYWRfa2V5X2J5dGUAAAAAAAAFAAAAAAAAApQ=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADndyaXRlX2tleV9ieXRlAAAAAAAFAAAAAAAAAAA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADnJlYWRfZGF0YV9ieXRlAAAAAAAFAAAAAAAAA7A=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD3dyaXRlX2RhdGFfYnl0ZQAAAAAFAAAAAAAABxA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAADnJlYWRfY29kZV9ieXRlAAAAAAAFAAAAAAAAU4Q=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD3dyaXRlX2NvZGVfYnl0ZQAAAAAFAAAAAAAAAAA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACmVtaXRfZXZlbnQAAAAAAAUAAAAAAAAAAQ==",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD2VtaXRfZXZlbnRfYnl0ZQAAAAAFAAAAAAAAAvw=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACGNwdV9pbnNuAAAABQAAAAAASJhK",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAACG1lbV9ieXRlAAAABQAAAAAAIRky",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEWludm9rZV90aW1lX25zZWNzAAAAAAAABQAAAAAAFuYk",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAD21heF9yd19rZXlfYnl0ZQAAAAAFAAAAAAAAAEA=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEG1heF9yd19kYXRhX2J5dGUAAAAFAAAAAAAAA7A=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAEG1heF9yd19jb2RlX2J5dGUAAAAFAAAAAAAAU4Q=",
+          "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAADwAAAAxjb3JlX21ldHJpY3MAAAAPAAAAE21heF9lbWl0X2V2ZW50X2J5dGUAAAAABQAAAAAAAAL8"
+        ],
+        "events": {
+          "transactionEventsXdr": [
+            "AAAAAAAAAAAAAAAB15KLcsJwPM/q9+uf9O9NUEpVqLl5/JtFDqLIQrTRzmEAAAABAAAAAAAAAAIAAAAPAAAAA2ZlZQAAAAASAAAAAAAAAADuBg+afmvWN9+nlruudR93UO1rDpTe8i6yxgPgBKoBVwAAAAoAAAAAAAAAAAAAAAAAmJbk",
+            "AAAAAQAAAAAAAAAB15KLcsJwPM/q9+uf9O9NUEpVqLl5/JtFDqLIQrTRzmEAAAABAAAAAAAAAAIAAAAPAAAAA2ZlZQAAAAASAAAAAAAAAADuBg+afmvWN9+nlruudR93UO1rDpTe8i6yxgPgBKoBVwAAAAr/////////////////bpos"
+          ],
+          "contractEventsXdr": [
+            [
+              "AAAAAAAAAAGlJx5hXtZLUEEJA9akotOUWIv8dYiEoyuKQmACnKsp1gAAAAEAAAAAAAAAAwAAAA8AAAAJcmVmbGVjdG9yAAAAAAAADwAAAAZwcmljZXMAAAAAAA8AAAAGdXBkYXRlAAAAAAAQAAAAAQAAAAkAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANFVVIAAAAACgAAAAAAAAAAAABqvu+1zoAAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANHQlAAAAAACgAAAAAAAAAAAAB77nns4IAAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANDSEYAAAAACgAAAAAAAAAAAAByGFTzG4AAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANDQUQAAAAACgAAAAAAAAAAAABCnNHJ4YAAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANNWE4AAAAACgAAAAAAAAAAAAAE4WY2fkAAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANBUlMAAAAACgAAAAAAAAAAAAAAEnbjAgAAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANCUkwAAAAACgAAAAAAAAAAAAAQo4RW4YAAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANUSEIAAAAACgAAAAAAAAAAAAACzMdm/4AAAAAQAAAAAQAAAAIAAAAQAAAAAQAAAAIAAAAPAAAABU90aGVyAAAAAAAADwAAAANYQVUAAAAACgAAAAAAAAAABKAotbWUP4A="
+            ]
+          ]
+        },
+        "ledger": 337272,
+        "createdAt": 1751955324
+      }
+    ],
+    "latestLedger": 387257,
+    "latestLedgerCloseTimestamp": 1752205462,
+    "oldestLedger": 337151,
+    "oldestLedgerCloseTimestamp": 1751954719,
+    "cursor": "1448572209876993"
+  }
+}
+```
+
+</Tab>
+</Tabs>
+
+{/* /rpc-method */}
 
 ### Using the Lab
 
diff --git a/docs/data/apis/rpc/api-reference/methods/getVersionInfo.mdx b/docs/data/apis/rpc/api-reference/methods/getVersionInfo.mdx
index 9056e9cc6..391e3f817 100644
--- a/docs/data/apis/rpc/api-reference/methods/getVersionInfo.mdx
+++ b/docs/data/apis/rpc/api-reference/methods/getVersionInfo.mdx
@@ -1,14 +1,121 @@
 ---
-hide_title: true
+title: getVersionInfo
 description: Returns version information
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "getVersionInfo")[0]}
-/>
+Version information about the RPC and Captive core. RPC manages its own, pared-down version of Stellar Core optimized for its own subset of needs. we'll refer to this as a "Captive Core" instance.
+
+## Params (0)
+
+## Result
+
+_(getVersionInfoResult)_
+
+<ResponseField name="version" type="string" example="27.1.1-7e712815319140618b9be8cf0846701a6f9a2cbe">
+
+The version of the RPC server.<br /> Example: `27.1.1-7e712815319140618b9be8cf0846701a6f9a2cbe`
+
+</ResponseField>
+
+<ResponseField name="commitHash" type="string" example="7e712815319140618b9be8cf0846701a6f9a2cbe">
+
+The commit hash of the RPC server. <br /> Example: `7e712815319140618b9be8cf0846701a6f9a2cbe`
+
+</ResponseField>
+
+<ResponseField name="buildTimestamp" type="string" example="2026-07-07T21:12:19">
+
+The build timestamp of the RPC server.<br /> Example: `2026-07-07T21:12:19`
+
+</ResponseField>
+
+<ResponseField name="captiveCoreVersion" type="string" example="stellar-core 27.1.0 (3589a696b0d4ef5a2cf2124e349c671d71886d9c)">
+
+The version of the Captive Core.<br /> Example: `stellar-core 27.1.0 (3589a696b0d4ef5a2cf2124e349c671d71886d9c)`
+
+</ResponseField>
+
+<ResponseField name="protocolVersion" type="integer" example="27">
+
+The protocol version.<br /> Example: `27`
+
+</ResponseField>
+
+## Example
+
+Example request to the `getVersionInfo` method
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getVersionInfo"
+}' \
+https://soroban-testnet.stellar.org | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "getVersionInfo",
+};
+let res = await fetch("https://soroban-testnet.stellar.org", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://soroban-testnet.stellar.org", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "getVersionInfo"
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "getVersionInfo"
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "version": "27.1.1-7e712815319140618b9be8cf0846701a6f9a2cbe",
+    "commitHash": "7e712815319140618b9be8cf0846701a6f9a2cbe",
+    "buildTimestamp": "2026-07-07T21:12:19",
+    "captiveCoreVersion": "stellar-core 27.1.0 (3589a696b0d4ef5a2cf2124e349c671d71886d9c)",
+    "protocolVersion": 27
+  }
+}
+```
+
+{/* /rpc-method */}
 
 ### Using the Lab
 
diff --git a/docs/data/apis/rpc/api-reference/methods/index.mdx b/docs/data/apis/rpc/api-reference/methods/index.mdx
new file mode 100644
index 000000000..87d00c430
--- /dev/null
+++ b/docs/data/apis/rpc/api-reference/methods/index.mdx
@@ -0,0 +1,88 @@
+---
+title: Methods
+description: "All you need to know about available RPC methods, parameters and responses, and making RPC requests."
+---
+
+<CardGroup cols={2}>
+  <Card title="getEvents" icon="file-lines" href="/docs/data/apis/rpc/api-reference/methods/getEvents">
+
+    Returns contract events
+
+  </Card>
+  <Card title="getFeeStats" icon="file-lines" href="/docs/data/apis/rpc/api-reference/methods/getFeeStats">
+
+    Returns statistics about charged inclusion fees for Soroban transactions and Stellar transactions
+
+  </Card>
+  <Card title="getHealth" icon="file-lines" href="/docs/data/apis/rpc/api-reference/methods/getHealth">
+
+    Returns node health
+
+  </Card>
+  <Card title="getLatestLedger" icon="file-lines" href="/docs/data/apis/rpc/api-reference/methods/getLatestLedger">
+
+    Returns latest known ledger
+
+  </Card>
+  <Card title="getLedgerEntries" icon="file-lines" href="/docs/data/apis/rpc/api-reference/methods/getLedgerEntries">
+
+    Returns ledger entries
+
+  </Card>
+  <Card title="getLedgers" icon="file-lines" href="/docs/data/apis/rpc/api-reference/methods/getLedgers">
+
+    Returns list of ledgers
+
+  </Card>
+  <Card title="getNetwork" icon="file-lines" href="/docs/data/apis/rpc/api-reference/methods/getNetwork">
+
+    Returns network config
+
+  </Card>
+  <Card title="getTransaction" icon="file-lines" href="/docs/data/apis/rpc/api-reference/methods/getTransaction">
+
+    Returns transaction details
+
+  </Card>
+  <Card title="getTransactions" icon="file-lines" href="/docs/data/apis/rpc/api-reference/methods/getTransactions">
+
+    Returns list of transactions
+
+  </Card>
+  <Card title="getVersionInfo" icon="file-lines" href="/docs/data/apis/rpc/api-reference/methods/getVersionInfo">
+
+    Returns version information
+
+  </Card>
+  <Card title="queryEvents" icon="file-lines" href="/docs/data/apis/rpc/api-reference/methods/queryEvents">
+
+    Returns events for a ledger range, ascending or descending, with cursors that do not expire (beta)
+
+  </Card>
+  <Card title="sendTransaction" icon="file-lines" href="/docs/data/apis/rpc/api-reference/methods/sendTransaction">
+
+    Submits a transaction
+
+  </Card>
+  <Card title="simulateTransaction" icon="file-lines" href="/docs/data/apis/rpc/api-reference/methods/simulateTransaction">
+
+    Submits a trial contract invocation transaction
+
+  </Card>
+</CardGroup>
+
+Don't know which endpoint you need to get what you want? A lot of the returned fields are deeply-nested [XDR structures](/docs/learn/fundamentals/data-format/xdr#more-about-xdr), so it can be hard to figure out what kind of information is available in each of these. Here's a bit of a dive into what the "workhorse" endpoints provide, in decreasing order of granularity:
+
+- [`getLedgers`](/docs/data/apis/rpc/api-reference/methods/getLedgers) operates at the block level, providing you with the full, complete details of what occurred during application of that ledger (known as "ledger metadata", defined in the protocol by the [`LedgerCloseMeta`](https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-ledger.x#L539) union, specifically the `V1` iteration). Each of the subsequent endpoints is just a microscope into a subset of the data available provided by this endpoint. Metadata includes things like:
+  - Details for recreating the blockchain's state (see [Ledger Headers](/docs/learn/fundamentals/stellar-data-structures/ledgers#ledger-headers) for more).
+  - The consensus information that led to the block closing (see [Stellar Consensus Protocol](/docs/learn/fundamentals/stellar-consensus-protocol)).
+  - The set of transactions, their respective operations, and the results of applying those transactions in this block (see [Transactions](/docs/learn/fundamentals/transactions/operations-and-transactions)).
+- [`getTransaction(s)`](/docs/data/apis/rpc/api-reference/methods/getTransactions) operates across a span of ledgers or on a single transaction hash depending on the variant. The structured data here includes details such as:
+  - The exact transaction structure ("envelope") that was submitted.
+  - Results for each of the operations within the transaction.
+  - All side-effects to ledger state that occurred as a result of this transaction.
+- [`getEvents`](/docs/data/apis/rpc/api-reference/methods/getEvents) lets you search for events that occurred over a ledger range. Events are emitted by the system and by smart contracts to communicate meaningful state changes to off chain indexers (see [Events](/docs/learn/fundamentals/stellar-data-structures/events) for more). Each event is made up of topics (which you can filter on) and data which are `ScVal`s, Stellar's generic "value" type (see [Contract Development](/docs/learn/fundamentals/contract-development/types/built-in-types) for more).
+- [`queryEvents`](/docs/data/apis/rpc/api-reference/methods/queryEvents) is the successor to `getEvents`. It adds descending order and stateless cursors. It is in beta and only runs on RPC nodes that enable it's new storage engine, so it lives in a separate beta spec and not in the main OpenRPC spec.
+- [`getLedgerEntries`](/docs/data/apis/rpc/api-reference/methods/getLedgerEntries), in contrast to the above endpoints, provides information about **live** on-chain state rather than historical actions. The [getLedgerEntries](/docs/data/apis/rpc/api-reference/methods/getLedgerEntries) page itself goes into detail on the different kinds of state stored on chain and how to fetch them.
+
+If you still aren't sure what you're looking for, remember that you can pass `xdrFormat: "json"` as a parameter to each of these endpoints to get a fully unpacked, human-readable JSON version of the XDR structures returned. You can look through these until you find what you need and go back to the Base64+unpack variation in your app. Equipped with an understanding of how to traverse XDR, the structure of the protocol, and your [favorite SDK](/docs/tools/sdks), you should be able to find anything you want about the Stellar network with these endpoints.
diff --git a/docs/data/apis/rpc/api-reference/methods/queryEvents.mdx b/docs/data/apis/rpc/api-reference/methods/queryEvents.mdx
index 8da545260..5a7940b82 100644
--- a/docs/data/apis/rpc/api-reference/methods/queryEvents.mdx
+++ b/docs/data/apis/rpc/api-reference/methods/queryEvents.mdx
@@ -1,22 +1,520 @@
 ---
-hide_title: true
+title: queryEvents
 description: Returns events for a ledger range, ascending or descending, with cursors that do not expire (beta)
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "@site/static/stellar-rpc-beta.openrpc.json";
+<Warning>
 
-:::caution Beta feature
+**Beta feature**
 
 The `queryEvents` method is available only on RPC nodes that enable it's new storage engine, which is currently in beta. Standard Stellar RPC nodes do not support this method. To use it, run RPC from the [`archive-node-beta`](https://github.com/stellar/stellar-rpc/releases/tag/archive-node-beta) tag or connect to a provider that offers one.
 
 This method is in beta and may change before general availability.
 
-:::
+</Warning>
 
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "queryEvents")[0]}
-/>
+{/* rpc-method: generated from the OpenRPC spec */}
+
+Returns contract and system events that match the specified filters within a ledger range. Results are paginated; each response contains a page of events and, when the scan is not complete, a cursor for continuing the query.
+
+Set `order` to `asc` to scan forward from `minLedger`, or to `desc` to scan backward from `maxLedger`. If omitted, `maxLedger` defaults to the latest ledger.
+
+To start a query, specify the applicable ledger bounds, scan order, and optional filters. To retrieve the next page, send the `cursor` returned in the previous response without repeating `minLedger`, `maxLedger`, `order`, or `filters`. The cursor preserves those query parameters. `limit` and `xdrFormat` are not stored in the cursor and may be specified on each request.
+
+Use `scanStatus` to determine whether to request another page, wait for additional ledgers, or stop. An empty `events` array does not necessarily mean the scan is complete.
+
+## Params (7)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="minLedger" type="number">
+
+The first ledger in the range (inclusive). Required for ascending scans (`order: asc`) and optional for descending scans. Specify this parameter only when starting a query, not when continuing with a cursor.
+
+Sequence number of the ledger.
+
+</ParamField>
+
+<ParamField body="maxLedger" type="number">
+
+The last ledger in the range (inclusive). Optional. Without `maxLedger`, an ascending scan continues toward newly closed ledgers and reports `WAITING_FOR_LEDGERS` when it catches up to the chain. A descending scan starts at the latest ledger. Specify this parameter only when starting a query.
+
+Sequence number of the ledger.
+
+</ParamField>
+
+<ParamField body="order" type="string">
+
+The direction of the scan. `asc` (default) scans forward from `minLedger`; `desc` scans backward from `maxLedger`. Specify this parameter only when starting a query.
+
+Available options: `asc`, `desc`
+
+</ParamField>
+
+<ParamField body="filters" type="object[]">
+
+An array of 1 to 256 event filters. An event matches if it satisfies at least one filter; within a filter, all specified fields must match. Omit `filters` to match all events. Specify this parameter only when starting a query.
+
+For example, to match either `transfer` or `mint` events from one contract, send two filters with the same `contractId` and a different `topic0`. The first example below does this.
+
+Topic values are Base64-encoded XDR `ScVal`s, not plain strings. Use the [JSON to XDR](https://lab.stellar.org/xdr/to) page in the Lab to encode a value.
+
+A query may use at most 15 distinct index terms by default; node operators can configure this limit. Each distinct `contractId` is one term, each distinct `type` is one term, and each distinct value at a given topic position is one term. The same value at the same position counts once no matter how many filters repeat it. The same value at two different positions counts twice. For example, `[{ topic0: transfer, topic1: me }, { topic0: transfer, topic2: me }]` uses 3 terms. A query over the budget returns `invalid_params` with `termsUsed` and `termBudget` in `error.data`.
+
+  <Expandable title="items">
+    <ParamField body="type" type="string">
+
+      The type of emitted event.
+
+      Available options: `contract`, `system`
+
+    </ParamField>
+    <ParamField body="contractId" type="string">
+
+      The emitting contract address in StrKey format (`C...`).
+
+    </ParamField>
+    <ParamField body="topic0" type="string">
+
+      The Base64-encoded XDR `ScVal` that the first event topic must match.
+
+    </ParamField>
+    <ParamField body="topic1" type="string">
+
+      The Base64-encoded XDR `ScVal` that the second event topic must match.
+
+    </ParamField>
+    <ParamField body="topic2" type="string">
+
+      The Base64-encoded XDR `ScVal` that the third event topic must match.
+
+    </ParamField>
+    <ParamField body="topic3" type="string">
+
+      The Base64-encoded XDR `ScVal` that the fourth event topic must match.
+
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+<ParamField body="cursor" type="string">
+
+The cursor returned by the previous response, used to continue a query. It preserves the ledger bounds, scan order, and filters. Do not combine `cursor` with `minLedger`, `maxLedger`, `order`, or `filters`; doing so returns an error.
+
+</ParamField>
+
+<ParamField body="limit" type="number">
+
+The maximum number of events to return per page, from 1 to 1,000. Defaults to 100. This setting is not stored in the cursor; include it on each request to retain a nondefault value.
+
+</ParamField>
+
+<ParamField body="xdrFormat" type="string">
+
+Controls how XDR values are represented in the response: decoded JSON or Base64-encoded XDR. Do not depend on a fixed schema for the JSON representation, as it may change with the underlying XDR.
+
+Specifies whether XDR should be encoded as Base64 (default or 'base64') or JSON ('json').
+
+</ParamField>
+
+## Result
+
+_(queryEventsResult)_
+
+<ResponseField name="events" type="object[]" required>
+
+Events returned on this page, up to the configured `limit`. The array may be empty even when more pages remain; check `scanStatus`.
+
+  <Expandable title="items">
+    <ResponseField name="type" type="string">
+
+      The type of emitted event.
+
+      Available options: `contract`, `system`
+
+    </ResponseField>
+    <ResponseField name="ledger" type="number">
+
+      The sequence number of the ledger in which the event was emitted.
+
+    </ResponseField>
+    <ResponseField name="ledgerClosedAt" type="string">
+
+      The ledger close time, formatted as an ISO 8601 timestamp.
+
+    </ResponseField>
+    <ResponseField name="contractId" type="string">
+
+      The address of the contract that emitted the event, in StrKey format.
+
+    </ResponseField>
+    <ResponseField name="id" type="string">
+
+      A unique event identifier consisting of a 19-character TOID and a 10-character, zero-padded event index, separated by a hyphen.
+
+    </ResponseField>
+    <ResponseField name="transactionIndex" type="number">
+
+      The index of the event's transaction within the ledger.
+
+    </ResponseField>
+    <ResponseField name="operationIndex" type="number">
+
+      The index of the operation that emitted the event within its transaction.
+
+    </ResponseField>
+    <ResponseField name="topic" type="string[]">
+
+      The event topics, each represented as a Base64-encoded XDR `ScVal`.
+
+    </ResponseField>
+    <ResponseField name="value" type="string">
+
+      The event data, represented as a Base64-encoded XDR `ScVal`.
+
+    </ResponseField>
+    <ResponseField name="txHash" type="string">
+
+      The hash of the transaction that triggered the event.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="cursor" type="string">
+
+An opaque cursor for retrieving the next page. It preserves the original ledger bounds, scan order, and filters and does not expire. The cursor is absent only when `scanStatus` is `COMPLETE`.
+
+</ResponseField>
+
+<ResponseField name="scanStatus" type="string" required>
+
+Indicates the state of the scan and the next action.
+
+- `HAS_MORE`: more data can be scanned immediately; request the next page.
+- `WAITING_FOR_LEDGERS`: the scan needs ledgers the node does not yet hold; wait and retry with the same cursor.
+- `OLDEST_REACHED`: a descending scan reached the oldest ledger available on this node before reaching the requested lower bound; stop or use a node with deeper history.
+- `COMPLETE`: the requested range has been fully scanned; no cursor is returned.
+
+Available options: `HAS_MORE`, `WAITING_FOR_LEDGERS`, `OLDEST_REACHED`, `COMPLETE`
+
+</ResponseField>
+
+<ResponseField name="scannedLedger" type="number" required>
+
+A scan checkpoint indicating that all matching events from the scan's starting bound through this ledger have been delivered. If a page ends partway through a ledger, this field identifies the last fully scanned ledger; the cursor resumes within the partially scanned ledger. Before any ledger has been fully scanned, the value is `minLedger - 1` for ascending scans or `maxLedger + 1` for descending scans.
+
+</ResponseField>
+
+<ResponseField name="oldestLedger" type="number" required>
+
+The sequence number of the oldest ledger available to the RPC node when it processed the request.
+
+</ResponseField>
+
+<ResponseField name="latestLedger" type="number" required>
+
+The sequence number of the latest ledger known to the RPC node when it processed the request.
+
+</ResponseField>
+
+## Examples
+
+<Tabs>
+<Tab title="Newest transfer or mint events">
+
+Starts a query for the newest `transfer` or `mint` events from one contract, two per page. With `order: desc` and no ledger bounds, the scan starts at the latest ledger and walks back. The two filters share a `contractId` and differ in `topic0`, so an event matches either. Ledger numbers and hashes are illustrative.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "queryEvents",
+  "params": {
+    "order": "desc",
+    "filters": [
+      {
+        "contractId": "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC",
+        "topic0": "AAAADwAAAAh0cmFuc2Zlcg=="
+      },
+      {
+        "contractId": "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC",
+        "topic0": "AAAADwAAAARtaW50"
+      }
+    ],
+    "limit": 2
+  }
+}' \
+https://soroban-testnet.stellar.org | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "queryEvents",
+  params: {
+    order: "desc",
+    filters: [
+      {
+        contractId: "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC",
+        topic0: "AAAADwAAAAh0cmFuc2Zlcg==",
+      },
+      {
+        contractId: "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC",
+        topic0: "AAAADwAAAARtaW50",
+      },
+    ],
+    limit: 2,
+  },
+};
+let res = await fetch("https://soroban-testnet.stellar.org", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://soroban-testnet.stellar.org", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "queryEvents",
+    "params": {
+        "order": "desc",
+        "filters": [
+            {
+                "contractId": "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC",
+                "topic0": "AAAADwAAAAh0cmFuc2Zlcg=="
+            },
+            {
+                "contractId": "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC",
+                "topic0": "AAAADwAAAARtaW50"
+            }
+        ],
+        "limit": 2
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "queryEvents",
+  "params": {
+    "order": "desc",
+    "filters": [
+      {
+        "contractId": "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC",
+        "topic0": "AAAADwAAAAh0cmFuc2Zlcg=="
+      },
+      {
+        "contractId": "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC",
+        "topic0": "AAAADwAAAARtaW50"
+      }
+    ],
+    "limit": 2
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "events": [
+      {
+        "type": "contract",
+        "ledger": 1189981,
+        "ledgerClosedAt": "2024-04-25T17:52:46Z",
+        "contractId": "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC",
+        "id": "0005110929477865472-0000000000",
+        "transactionIndex": 1,
+        "operationIndex": 0,
+        "txHash": "5bd25a1a8fd1fe8ec99ab1fdd57af9a6f0e4c7c8a3c1b7d2e9f0a1b2c3d4e5f6",
+        "topic": [
+          "AAAADwAAAAh0cmFuc2Zlcg==",
+          "AAAAEgAAAAAAAAAAeo0X4ISuIjuArAyYXR0z8qyj0x0MHpv92CTtN4PONek=",
+          "AAAAEgAAAAAAAAAAfn3koV5C+Z6q8U1LfPwlofeZ3jnWI6Iudfg5NOEmOtg="
+        ],
+        "value": "AAAACgAAAAAAAAAAAAAAAAX14QA="
+      },
+      {
+        "type": "contract",
+        "ledger": 1189977,
+        "ledgerClosedAt": "2024-04-25T17:52:26Z",
+        "contractId": "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC",
+        "id": "0005110912298004480-0000000000",
+        "transactionIndex": 3,
+        "operationIndex": 0,
+        "txHash": "e1f2a3b4c5d6e7f8091a2b3c4d5e6f708192a3b4c5d6e7f8091a2b3c4d5e6f70",
+        "topic": [
+          "AAAADwAAAAh0cmFuc2Zlcg==",
+          "AAAAEgAAAAAAAAAAfn3koV5C+Z6q8U1LfPwlofeZ3jnWI6Iudfg5NOEmOtg=",
+          "AAAAEgAAAAAAAAAAeo0X4ISuIjuArAyYXR0z8qyj0x0MHpv92CTtN4PONek="
+        ],
+        "value": "AAAACgAAAAAAAAAAAAAAAACYloA="
+      }
+    ],
+    "cursor": "gec1_AQEAAAASJnIAAAASJm0AAAAB...",
+    "scanStatus": "HAS_MORE",
+    "scannedLedger": 1189978,
+    "oldestLedger": 2,
+    "latestLedger": 1190004
+  }
+}
+```
+
+</Tab>
+<Tab title="Next page">
+
+Continues the query above by sending only the `cursor` from the previous response and `limit`. The order and filters come from the cursor. The scan has no lower bound, so it reports `HAS_MORE` until it reaches the oldest ledger the node holds. Keep sending the cursor until `scanStatus` is `OLDEST_REACHED` or `COMPLETE`.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "queryEvents",
+  "params": {
+    "cursor": "gec1_AQEAAAASJnIAAAASJm0AAAAB...",
+    "limit": 2
+  }
+}' \
+https://soroban-testnet.stellar.org | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "queryEvents",
+  params: {
+    cursor: "gec1_AQEAAAASJnIAAAASJm0AAAAB...",
+    limit: 2,
+  },
+};
+let res = await fetch("https://soroban-testnet.stellar.org", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://soroban-testnet.stellar.org", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "queryEvents",
+    "params": {
+        "cursor": "gec1_AQEAAAASJnIAAAASJm0AAAAB...",
+        "limit": 2
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "queryEvents",
+  "params": {
+    "cursor": "gec1_AQEAAAASJnIAAAASJm0AAAAB...",
+    "limit": 2
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "events": [
+      {
+        "type": "contract",
+        "ledger": 1189977,
+        "ledgerClosedAt": "2024-04-25T17:52:26Z",
+        "contractId": "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC",
+        "id": "0005110912298004481-0000000000",
+        "transactionIndex": 3,
+        "operationIndex": 1,
+        "txHash": "e1f2a3b4c5d6e7f8091a2b3c4d5e6f708192a3b4c5d6e7f8091a2b3c4d5e6f70",
+        "topic": [
+          "AAAADwAAAARtaW50",
+          "AAAAEgAAAAAAAAAAfn3koV5C+Z6q8U1LfPwlofeZ3jnWI6Iudfg5NOEmOtg="
+        ],
+        "value": "AAAACgAAAAAAAAAAAAAAAAX14QA="
+      },
+      {
+        "type": "contract",
+        "ledger": 1189950,
+        "ledgerClosedAt": "2024-04-25T17:50:11Z",
+        "contractId": "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC",
+        "id": "0005110796333883392-0000000000",
+        "transactionIndex": 2,
+        "operationIndex": 0,
+        "txHash": "0a1b2c3d4e5f60718293a4b5c6d7e8f90a1b2c3d4e5f60718293a4b5c6d7e8f9",
+        "topic": [
+          "AAAADwAAAAh0cmFuc2Zlcg==",
+          "AAAAEgAAAAAAAAAAeo0X4ISuIjuArAyYXR0z8qyj0x0MHpv92CTtN4PONek=",
+          "AAAAEgAAAAAAAAAAfn3koV5C+Z6q8U1LfPwlofeZ3jnWI6Iudfg5NOEmOtg="
+        ],
+        "value": "AAAACgAAAAAAAAAAAAAAAAJiWgA="
+      }
+    ],
+    "cursor": "gec1_AQEAAAASJj4AAAASJj0AAAAA...",
+    "scanStatus": "HAS_MORE",
+    "scannedLedger": 1189951,
+    "oldestLedger": 2,
+    "latestLedger": 1190004
+  }
+}
+```
+
+</Tab>
+</Tabs>
+
+{/* /rpc-method */}
 
 ### Errors
 
diff --git a/docs/data/apis/rpc/api-reference/methods/sendTransaction.mdx b/docs/data/apis/rpc/api-reference/methods/sendTransaction.mdx
index 56b5a7f54..788adb42a 100644
--- a/docs/data/apis/rpc/api-reference/methods/sendTransaction.mdx
+++ b/docs/data/apis/rpc/api-reference/methods/sendTransaction.mdx
@@ -1,22 +1,431 @@
 ---
-hide_title: true
+title: sendTransaction
 description: Submits a transaction
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "sendTransaction")[0]}
-/>
+Submit a real transaction to the Stellar network. This is the only way to make changes on-chain.
+
+Unlike Horizon, this does not wait for transaction completion. It simply validates and enqueues the transaction. Clients should call `getTransaction` to learn about transaction success/failure.
+
+This supports all transactions, not only smart contract-related transactions.
+
+## Params (1)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="transaction" type="string" required>
+
+The signed transaction to broadcast for inclusion in a ledger.
+
+A Stellar [TransactionEnvelope](https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-transaction.x#L1009) (as a base64-encoded string)
+
+</ParamField>
+
+## Result
+
+_(sendTransactionResult)_
+
+Transaction status and network state. The result will include if the transaction was successfully enqueued, and information about the current ledger.
+
+<ResponseField name="hash" type="string" required>
+
+Transaction hash (as a hex-encoded string)
+
+</ResponseField>
+
+<ResponseField name="status" type="string" required>
+
+The current status of the transaction by hash.
+
+Available options: `PENDING`, `DUPLICATE`, `TRY_AGAIN_LATER`, `ERROR`
+
+</ResponseField>
+
+<ResponseField name="latestLedger" type="number" required>
+
+The sequence number of the latest ledger known to Stellar RPC at the time it handled the request.
+
+</ResponseField>
+
+<ResponseField name="latestLedgerCloseTime" type="number" required>
+
+The unix timestamp of the close time of the latest ledger known to Stellar RPC at the time it handled the request.
+
+</ResponseField>
+
+<ResponseField name="errorResultXdr" type="string">
+
+(optional) If the transaction status is `ERROR`, this will be a base64 encoded string of the raw TransactionResult XDR struct containing details on why stellar-core rejected the transaction.
+
+</ResponseField>
+
+<ResponseField name="diagnosticEventsXdr" type="string[]">
+
+(optional) If the transaction status is `ERROR`, this field may be present with an array of base64 encoded strings. Each string will decode to a raw DiagnosticEvent XDR struct containing details on why stellar-core rejected the transaction.
+
+</ResponseField>
+
+## Examples
+
+<Tabs>
+<Tab title="Pending Transaction">
+
+Submitting a valid transaction using the `sendTransaction` method, resulting in a `PENDING` status.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "sendTransaction",
+  "params": {
+    "transaction": "AAAAAgAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAGQAJsOiAAAADQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAACgAAAAVIZWxsbwAAAAAAAAEAAAAMU29yb2JhbiBEb2NzAAAAAAAAAAELm/oYAAAAQATr6Ghp/DNO7S6JjEFwcJ9a+dvI6NJr7I/2eQttvoovjQ8te4zKKaapC3mbmx6ld6YKL5T81mxs45TjzdG5zw0="
+  }
+}' \
+https://soroban-testnet.stellar.org | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "sendTransaction",
+  params: {
+    transaction:
+      "AAAAAgAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAGQAJsOiAAAADQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAACgAAAAVIZWxsbwAAAAAAAAEAAAAMU29yb2JhbiBEb2NzAAAAAAAAAAELm/oYAAAAQATr6Ghp/DNO7S6JjEFwcJ9a+dvI6NJr7I/2eQttvoovjQ8te4zKKaapC3mbmx6ld6YKL5T81mxs45TjzdG5zw0=",
+  },
+};
+let res = await fetch("https://soroban-testnet.stellar.org", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://soroban-testnet.stellar.org", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "sendTransaction",
+    "params": {
+        "transaction": "AAAAAgAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAGQAJsOiAAAADQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAACgAAAAVIZWxsbwAAAAAAAAEAAAAMU29yb2JhbiBEb2NzAAAAAAAAAAELm/oYAAAAQATr6Ghp/DNO7S6JjEFwcJ9a+dvI6NJr7I/2eQttvoovjQ8te4zKKaapC3mbmx6ld6YKL5T81mxs45TjzdG5zw0="
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "sendTransaction",
+  "params": {
+    "transaction": "AAAAAgAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAGQAJsOiAAAADQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAACgAAAAVIZWxsbwAAAAAAAAEAAAAMU29yb2JhbiBEb2NzAAAAAAAAAAELm/oYAAAAQATr6Ghp/DNO7S6JjEFwcJ9a+dvI6NJr7I/2eQttvoovjQ8te4zKKaapC3mbmx6ld6YKL5T81mxs45TjzdG5zw0="
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "status": "PENDING",
+    "hash": "d8ec9b68780314ffdfdfc2194b1b35dd27d7303c3bceaef6447e31631a1419dc",
+    "latestLedger": 2553978,
+    "latestLedgerCloseTime": "1700159337"
+  }
+}
+```
+
+</Tab>
+<Tab title="Duplicate Transaction">
+
+Submitting a valid, yet duplicate transaction using the `sendTransaction` method, resulting in a `DUPLICATE` status.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "sendTransaction",
+  "params": {
+    "transaction": "AAAAAgAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAGQAJsOiAAAADQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAACgAAAAVIZWxsbwAAAAAAAAEAAAAMU29yb2JhbiBEb2NzAAAAAAAAAAELm/oYAAAAQATr6Ghp/DNO7S6JjEFwcJ9a+dvI6NJr7I/2eQttvoovjQ8te4zKKaapC3mbmx6ld6YKL5T81mxs45TjzdG5zw0="
+  }
+}' \
+https://soroban-testnet.stellar.org | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "sendTransaction",
+  params: {
+    transaction:
+      "AAAAAgAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAGQAJsOiAAAADQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAACgAAAAVIZWxsbwAAAAAAAAEAAAAMU29yb2JhbiBEb2NzAAAAAAAAAAELm/oYAAAAQATr6Ghp/DNO7S6JjEFwcJ9a+dvI6NJr7I/2eQttvoovjQ8te4zKKaapC3mbmx6ld6YKL5T81mxs45TjzdG5zw0=",
+  },
+};
+let res = await fetch("https://soroban-testnet.stellar.org", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://soroban-testnet.stellar.org", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "sendTransaction",
+    "params": {
+        "transaction": "AAAAAgAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAGQAJsOiAAAADQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAACgAAAAVIZWxsbwAAAAAAAAEAAAAMU29yb2JhbiBEb2NzAAAAAAAAAAELm/oYAAAAQATr6Ghp/DNO7S6JjEFwcJ9a+dvI6NJr7I/2eQttvoovjQ8te4zKKaapC3mbmx6ld6YKL5T81mxs45TjzdG5zw0="
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "sendTransaction",
+  "params": {
+    "transaction": "AAAAAgAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAGQAJsOiAAAADQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAACgAAAAVIZWxsbwAAAAAAAAEAAAAMU29yb2JhbiBEb2NzAAAAAAAAAAELm/oYAAAAQATr6Ghp/DNO7S6JjEFwcJ9a+dvI6NJr7I/2eQttvoovjQ8te4zKKaapC3mbmx6ld6YKL5T81mxs45TjzdG5zw0="
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "status": "DUPLICATE",
+    "hash": "d8ec9b68780314ffdfdfc2194b1b35dd27d7303c3bceaef6447e31631a1419dc",
+    "latestLedger": 2553978,
+    "latestLedgerCloseTime": "1700159337"
+  }
+}
+```
+
+</Tab>
+<Tab title="Error Transaction">
+
+Submitting an invalid transaction using the `sendTransaction` method, resulting in an `ERROR` status.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "sendTransaction",
+  "params": {
+    "transaction": "AAAAAgAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAGQAAAAAAAAACgAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAACgAAAAVIZWxsbwAAAAAAAAEAAAAMU29yb2JhbiBEb2NzAAAAAAAAAAELm/oYAAAAQMQkfl8sdCYQIOdJB0TyazJ126y2TFRjL8yNHSb4TTsH5Ym6qM6gkTx1ENRZ0PFprVGusMTHISzdPHYJ4njBZAQ="
+  }
+}' \
+https://soroban-testnet.stellar.org | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "sendTransaction",
+  params: {
+    transaction:
+      "AAAAAgAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAGQAAAAAAAAACgAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAACgAAAAVIZWxsbwAAAAAAAAEAAAAMU29yb2JhbiBEb2NzAAAAAAAAAAELm/oYAAAAQMQkfl8sdCYQIOdJB0TyazJ126y2TFRjL8yNHSb4TTsH5Ym6qM6gkTx1ENRZ0PFprVGusMTHISzdPHYJ4njBZAQ=",
+  },
+};
+let res = await fetch("https://soroban-testnet.stellar.org", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://soroban-testnet.stellar.org", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "sendTransaction",
+    "params": {
+        "transaction": "AAAAAgAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAGQAAAAAAAAACgAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAACgAAAAVIZWxsbwAAAAAAAAEAAAAMU29yb2JhbiBEb2NzAAAAAAAAAAELm/oYAAAAQMQkfl8sdCYQIOdJB0TyazJ126y2TFRjL8yNHSb4TTsH5Ym6qM6gkTx1ENRZ0PFprVGusMTHISzdPHYJ4njBZAQ="
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "sendTransaction",
+  "params": {
+    "transaction": "AAAAAgAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAGQAAAAAAAAACgAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAACgAAAAVIZWxsbwAAAAAAAAEAAAAMU29yb2JhbiBEb2NzAAAAAAAAAAELm/oYAAAAQMQkfl8sdCYQIOdJB0TyazJ126y2TFRjL8yNHSb4TTsH5Ym6qM6gkTx1ENRZ0PFprVGusMTHISzdPHYJ4njBZAQ="
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "errorResultXdr": "AAAAAAAAAGT////7AAAAAA==",
+    "status": "ERROR",
+    "hash": "84a5f62bff422581dda019811daed0868a3db41833ad6e90a12f0d7db1be8167",
+    "latestLedger": 2553978,
+    "latestLedgerCloseTime": "1700159337"
+  }
+}
+```
+
+</Tab>
+<Tab title="Try Again Later Transaction">
+
+Submitting a valid transaction before an account's previously submitted transaction has settled using the `sendTransaction` method, resulting in a `TRY_AGAIN_LATER` status.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "sendTransaction",
+  "params": {
+    "transaction": "AAAAAgAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAGQAJsOiAAAADQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAACgAAAAVIZWxsbwAAAAAAAAEAAAAMU29yb2JhbiBEb2NzAAAAAAAAAAELm/oYAAAAQATr6Ghp/DNO7S6JjEFwcJ9a+dvI6NJr7I/2eQttvoovjQ8te4zKKaapC3mbmx6ld6YKL5T81mxs45TjzdG5zw0="
+  }
+}' \
+https://soroban-testnet.stellar.org | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "sendTransaction",
+  params: {
+    transaction:
+      "AAAAAgAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAGQAJsOiAAAADQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAACgAAAAVIZWxsbwAAAAAAAAEAAAAMU29yb2JhbiBEb2NzAAAAAAAAAAELm/oYAAAAQATr6Ghp/DNO7S6JjEFwcJ9a+dvI6NJr7I/2eQttvoovjQ8te4zKKaapC3mbmx6ld6YKL5T81mxs45TjzdG5zw0=",
+  },
+};
+let res = await fetch("https://soroban-testnet.stellar.org", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://soroban-testnet.stellar.org", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "sendTransaction",
+    "params": {
+        "transaction": "AAAAAgAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAGQAJsOiAAAADQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAACgAAAAVIZWxsbwAAAAAAAAEAAAAMU29yb2JhbiBEb2NzAAAAAAAAAAELm/oYAAAAQATr6Ghp/DNO7S6JjEFwcJ9a+dvI6NJr7I/2eQttvoovjQ8te4zKKaapC3mbmx6ld6YKL5T81mxs45TjzdG5zw0="
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "sendTransaction",
+  "params": {
+    "transaction": "AAAAAgAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAGQAJsOiAAAADQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAACgAAAAVIZWxsbwAAAAAAAAEAAAAMU29yb2JhbiBEb2NzAAAAAAAAAAELm/oYAAAAQATr6Ghp/DNO7S6JjEFwcJ9a+dvI6NJr7I/2eQttvoovjQ8te4zKKaapC3mbmx6ld6YKL5T81mxs45TjzdG5zw0="
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "status": "TRY_AGAIN_LATER",
+    "hash": "d8ec9b68780314ffdfdfc2194b1b35dd27d7303c3bceaef6447e31631a1419dc",
+    "latestLedger": 2553978,
+    "latestLedgerCloseTime": "1700159337"
+  }
+}
+```
+
+</Tab>
+</Tabs>
+
+{/* /rpc-method */}
 
 ### SDK Guide
 
 The example above is sending a transaction using RPC methods directly. If you are using the Stellar SDK to build applications, you can use the native functions to get the same information.
 
-<CodeExample>
+<CodeGroup>
 
-```python
+```python Python
 # pip install --upgrade stellar-sdk
 from stellar_sdk import SorobanServer, soroban_rpc, Keypair, Network, TransactionBuilder, scval
 
@@ -59,7 +468,7 @@ print("status:", response.status)
 print("errorResultXdr:", response.error_result_xdr)
 ```
 
-```js
+```js JavaScript
 // yarn add @stellar/stellar-sdk
 import * as StellarSdk from "@stellar/stellar-sdk";
 
@@ -116,7 +525,7 @@ async function sendTransaction() {
 sendTransaction();
 ```
 
-```java
+```java Java
 // https://github.com/lightsail-network/java-stellar-sdk?tab=readme-ov-file#installation
 import org.stellar.sdk.KeyPair;
 import org.stellar.sdk.Network;
@@ -182,13 +591,13 @@ public class SendTransactionExample {
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Using the Lab
 
 The `sendTransaction` method is used to **submit a real transaction to the Stellar network**, making it the only way to execute **on-chain changes** through RPC.
 
-Unlike Horizon, this method **does not wait for confirmation**. Instead, it **validates and enqueues** the transaction. To track its final outcome, clients should follow up with a call to [`getTransaction`](../methods/getTransaction.mdx).
+Unlike Horizon, this method **does not wait for confirmation**. Instead, it **validates and enqueues** the transaction. To track its final outcome, clients should follow up with a call to [`getTransaction`](../methods/getTransaction).
 
 This method supports **all Stellar transactions**, including but not limited to smart contract invocations.
 
diff --git a/docs/data/apis/rpc/api-reference/methods/simulateTransaction.mdx b/docs/data/apis/rpc/api-reference/methods/simulateTransaction.mdx
index fcb13d518..e3fb349ea 100644
--- a/docs/data/apis/rpc/api-reference/methods/simulateTransaction.mdx
+++ b/docs/data/apis/rpc/api-reference/methods/simulateTransaction.mdx
@@ -1,22 +1,394 @@
 ---
-hide_title: true
+title: simulateTransaction
 description: Submits a trial contract invocation transaction
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={
-    rpcSpec.methods.filter((meth) => meth.name === "simulateTransaction")[0]
+Submit a trial contract invocation to simulate how it would be executed by the network. This endpoint calculates the effective transaction data, required authorizations, and minimal resource fee. It provides a way to test and analyze the potential outcomes of a transaction without actually submitting it to the network.
+
+This method can also be used to invoke read-only smart contract functions for free.
+
+## Params (4)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="transaction" type="string" required>
+
+In order for the RPC server to successfully simulate a Stellar transaction, the provided transaction must contain only a single operation of the type `invokeHostFunction`.
+
+A Stellar [TransactionEnvelope](https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-transaction.x#L1009) (as a base64-encoded string)
+
+</ParamField>
+
+<ParamField body="resourceConfig" type="object">
+
+Contains configuration for how resources will be calculated when simulating transactions.
+
+Configuration for how resources will be calculated.
+
+  <Expandable title="properties">
+    <ParamField body="instructionLeeway" type="number">
+
+      Allow this many extra instructions when budgeting resources.
+
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+<ParamField body="xdrFormat" type="string">
+
+Lets the user choose the format in which the response should be returned - either as unpacked JSON or as base64-encoded XDR strings. Note that you should not rely on any schema for the JSON, as it will change when the underlying XDR changes.
+
+Specifies whether XDR should be encoded as Base64 (default or 'base64') or JSON ('json').
+
+</ParamField>
+
+<ParamField body="authMode" type="string">
+
+Specifies the authorization mode to use when simulating the transaction. The options are 'enforce' (default, enforces all authorization checks), 'record' (records authorization without enforcement), and 'record_allow_nonroot' (records authorization while allowing non-root invocations).
+
+Specifies the authorization mode to use when simulating the transaction. 'enforce' (default) enforces authorization checks, 'record' records authorization without enforcing, and 'record_allow_nonroot' records authorization while allowing non-root invocations.
+
+Available options: `enforce`, `record`, `record_allow_nonroot`
+
+</ParamField>
+
+## Result
+
+_(simulateTransactionResult)_
+
+The response will include the anticipated affects the given transaction will have on the network. Additionally, information needed to build, sign, and actually submit the transaction will be provided.
+
+<ResponseField name="latestLedger" type="number" required>
+
+The sequence number of the latest ledger known to Stellar RPC at the time it handled the request.
+
+</ResponseField>
+
+<ResponseField name="minResourceFee" type="string">
+
+(optional) Stringified number - Recommended minimum resource fee to add when submitting the transaction. This fee is to be added on top of the [Stellar network fee](https://developers.stellar.org/docs/learn/fundamentals/fees-resource-limits-metering#inclusion-fee). Not present in case of error.
+
+</ResponseField>
+
+<ResponseField name="results" type="object[]">
+
+(optional) - This array will only have one element: the result for the Host Function invocation. Only present on successful simulation (i.e. no error) of `InvokeHostFunction` operations.
+
+  <Expandable title="items">
+    <ResponseField name="xdr" type="string" required>
+
+      Serialized base64 string - return value of the Host Function call.
+
+    </ResponseField>
+    <ResponseField name="auth" type="string[]" required>
+
+      Array of serialized base64 strings - Per-address authorizations recorded when simulating this Host Function call.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="transactionData" type="string">
+
+(optional) Serialized base64 string - The recommended Soroban Transaction Data to use when submitting the simulated transaction. This data contains the refundable fee and resource usage information such as the ledger footprint and IO access data (serialized in a base64 string). Not present in case of error.
+
+</ResponseField>
+
+<ResponseField name="events" type="string[]">
+
+(optional) Array of serialized base64 strings - Array of the events emitted during the contract invocation. The events are ordered by their emission time. (an array of serialized base64 strings). Only present when simulating of `InvokeHostFunction` operations, note that it can be present on error, providing extra context about what failed.
+
+</ResponseField>
+
+<ResponseField name="restorePreamble" type="object">
+
+(optional) - It can only be present on successful simulation (i.e. no error) of `InvokeHostFunction` operations. If present, it indicates that the simulation detected archived ledger entries which need to be restored before the submission of the `InvokeHostFunction` operation. The `minResourceFee` and `transactionData` fields should be used to submit a transaction containing a `RestoreFootprint` operation.
+
+  <Expandable title="properties">
+    <ResponseField name="minResourceFee" type="string" required>
+
+      Stringified number - Recommended minimum resource fee to add when submitting the `RestoreFootprint` operation. This fee is to be added on top of the [Stellar network fee](https://developers.stellar.org/docs/learn/fundamentals/fees-resource-limits-metering#inclusion-fee).
+
+    </ResponseField>
+    <ResponseField name="transactionData" type="string" required>
+
+      Serialized base64 string - The recommended Soroban Transaction Data to use when submitting the `RestoreFootprint` operation.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="stateChanges" type="object[]">
+
+(optional) - On successful simulation of `InvokeHostFunction` operations, this field will be an array of `LedgerEntry`s before and after simulation occurred. Note that _at least_ one of `before` or `after` will be present: `before` and no `after` indicates a deletion event, the inverse is a creation event, and both present indicates an update event. Or just check the `type`.
+
+  <Expandable title="items">
+    <ResponseField name="type" type="string" required>
+
+      Indicates if the entry was created, updated, or deleted
+
+      Available options: `created`, `updated`, `deleted`
+
+    </ResponseField>
+    <ResponseField name="key" type="string" required>
+
+      Base64 - the `LedgerKey` for this delta
+
+    </ResponseField>
+    <ResponseField name="before" type="string | null" required>
+
+      Base64, if present - `LedgerEntry` state prior to simulation
+
+    </ResponseField>
+    <ResponseField name="after" type="string | null" required>
+
+      Base64, if present - `LedgerEntry` state after simulation
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="error" type="string">
+
+(optional) - This field will include details about why the invoke host function call failed. Only present if the transaction simulation failed.
+
+</ResponseField>
+
+## Examples
+
+<Tabs>
+<Tab title="Successful Transaction Simulation">
+
+Transaction simulation that succeeds and returns the necessary information to prepare and submit the transaction.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "simulateTransaction",
+  "params": {
+    "transaction": "AAAAAgAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAGQAJsOiAAAAEQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAGAAAAAAAAAABzAP+dP0PsNzYvFF1pv7a8RQXwH5eg3uZBbbWjE9PwAsAAAAJaW5jcmVtZW50AAAAAAAAAgAAABIAAAAAAAAAACDh1sDGwYAYgJ8EbeJPZwoZhDqEriwlbNnqivULm/oYAAAAAwAAAAMAAAAAAAAAAAAAAAA=",
+    "resourceConfig": {
+      "instructionLeeway": 3000000
+    }
   }
-/>
+}' \
+https://soroban-testnet.stellar.org | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "simulateTransaction",
+  params: {
+    transaction:
+      "AAAAAgAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAGQAJsOiAAAAEQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAGAAAAAAAAAABzAP+dP0PsNzYvFF1pv7a8RQXwH5eg3uZBbbWjE9PwAsAAAAJaW5jcmVtZW50AAAAAAAAAgAAABIAAAAAAAAAACDh1sDGwYAYgJ8EbeJPZwoZhDqEriwlbNnqivULm/oYAAAAAwAAAAMAAAAAAAAAAAAAAAA=",
+    resourceConfig: {
+      instructionLeeway: 3000000,
+    },
+  },
+};
+let res = await fetch("https://soroban-testnet.stellar.org", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://soroban-testnet.stellar.org", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "simulateTransaction",
+    "params": {
+        "transaction": "AAAAAgAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAGQAJsOiAAAAEQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAGAAAAAAAAAABzAP+dP0PsNzYvFF1pv7a8RQXwH5eg3uZBbbWjE9PwAsAAAAJaW5jcmVtZW50AAAAAAAAAgAAABIAAAAAAAAAACDh1sDGwYAYgJ8EbeJPZwoZhDqEriwlbNnqivULm/oYAAAAAwAAAAMAAAAAAAAAAAAAAAA=",
+        "resourceConfig": {
+            "instructionLeeway": 3000000
+        }
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "simulateTransaction",
+  "params": {
+    "transaction": "AAAAAgAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAGQAJsOiAAAAEQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAGAAAAAAAAAABzAP+dP0PsNzYvFF1pv7a8RQXwH5eg3uZBbbWjE9PwAsAAAAJaW5jcmVtZW50AAAAAAAAAgAAABIAAAAAAAAAACDh1sDGwYAYgJ8EbeJPZwoZhDqEriwlbNnqivULm/oYAAAAAwAAAAMAAAAAAAAAAAAAAAA=",
+    "resourceConfig": {
+      "instructionLeeway": 3000000
+    }
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "transactionData": "AAAAAAAAAAIAAAAGAAAAAcwD/nT9D7Dc2LxRdab+2vEUF8B+XoN7mQW21oxPT8ALAAAAFAAAAAEAAAAHy8vNUZ8vyZ2ybPHW0XbSrRtP7gEWsJ6zDzcfY9P8z88AAAABAAAABgAAAAHMA/50/Q+w3Ni8UXWm/trxFBfAfl6De5kFttaMT0/ACwAAABAAAAABAAAAAgAAAA8AAAAHQ291bnRlcgAAAAASAAAAAAAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAAEAHfKyAAAFiAAAAIgAAAAAAAAAAw==",
+    "minResourceFee": "90353",
+    "events": [
+      "AAAAAQAAAAAAAAAAAAAAAgAAAAAAAAADAAAADwAAAAdmbl9jYWxsAAAAAA0AAAAgzAP+dP0PsNzYvFF1pv7a8RQXwH5eg3uZBbbWjE9PwAsAAAAPAAAACWluY3JlbWVudAAAAAAAABAAAAABAAAAAgAAABIAAAAAAAAAACDh1sDGwYAYgJ8EbeJPZwoZhDqEriwlbNnqivULm/oYAAAAAwAAAAM=",
+      "AAAAAQAAAAAAAAABzAP+dP0PsNzYvFF1pv7a8RQXwH5eg3uZBbbWjE9PwAsAAAACAAAAAAAAAAIAAAAPAAAACWZuX3JldHVybgAAAAAAAA8AAAAJaW5jcmVtZW50AAAAAAAAAwAAAAw="
+    ],
+    "results": [
+      {
+        "auth": [],
+        "xdr": "AAAAAwAAAAw="
+      }
+    ],
+    "cost": {
+      "cpuInsns": "1635562",
+      "memBytes": "1295756"
+    },
+    "latestLedger": 2552139
+  }
+}
+```
+
+</Tab>
+<Tab title="Failed Transaction Simulation">
+
+Transaction simulation that fails due to the contract invocation being constructed with an improper number of arguments.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "simulateTransaction",
+  "params": {
+    "transaction": "AAAAAgAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAGQAJsOiAAAADwAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAGAAAAAAAAAABzAP+dP0PsNzYvFF1pv7a8RQXwH5eg3uZBbbWjE9PwAsAAAAJaW5jcmVtZW50AAAAAAAAAQAAAAMAAAADAAAAAAAAAAAAAAAA",
+    "resourceConfig": {
+      "instructionLeeway": 3000000
+    }
+  }
+}' \
+https://soroban-testnet.stellar.org | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "simulateTransaction",
+  params: {
+    transaction:
+      "AAAAAgAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAGQAJsOiAAAADwAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAGAAAAAAAAAABzAP+dP0PsNzYvFF1pv7a8RQXwH5eg3uZBbbWjE9PwAsAAAAJaW5jcmVtZW50AAAAAAAAAQAAAAMAAAADAAAAAAAAAAAAAAAA",
+    resourceConfig: {
+      instructionLeeway: 3000000,
+    },
+  },
+};
+let res = await fetch("https://soroban-testnet.stellar.org", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://soroban-testnet.stellar.org", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "simulateTransaction",
+    "params": {
+        "transaction": "AAAAAgAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAGQAJsOiAAAADwAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAGAAAAAAAAAABzAP+dP0PsNzYvFF1pv7a8RQXwH5eg3uZBbbWjE9PwAsAAAAJaW5jcmVtZW50AAAAAAAAAQAAAAMAAAADAAAAAAAAAAAAAAAA",
+        "resourceConfig": {
+            "instructionLeeway": 3000000
+        }
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "simulateTransaction",
+  "params": {
+    "transaction": "AAAAAgAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAGQAJsOiAAAADwAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAGAAAAAAAAAABzAP+dP0PsNzYvFF1pv7a8RQXwH5eg3uZBbbWjE9PwAsAAAAJaW5jcmVtZW50AAAAAAAAAQAAAAMAAAADAAAAAAAAAAAAAAAA",
+    "resourceConfig": {
+      "instructionLeeway": 3000000
+    }
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "error": "host invocation failed\n\nCaused by:\n    HostError: Error(WasmVm, InternalError)\n    \n    Event log (newest first):\n       0: [Diagnostic Event] contract:cc03fe74fd0fb0dcd8bc5175a6fedaf11417c07e5e837b9905b6d68c4f4fc00b, topics:[error, Error(WasmVm, InternalError)], data:[\"VM call failed: Func(MismatchingParameterLen)\", increment]\n       1: [Diagnostic Event] topics:[fn_call, Bytes(cc03fe74fd0fb0dcd8bc5175a6fedaf11417c07e5e837b9905b6d68c4f4fc00b), increment], data:3\n    \n    Backtrace (newest first):\n       0: soroban_env_host::vm::Vm::invoke_function_raw\n       1: soroban_env_host::host::frame::<impl soroban_env_host::host::Host>::with_frame\n       2: soroban_env_host::host::frame::<impl soroban_env_host::host::Host>::call_n_internal\n       3: soroban_env_host::host::frame::<impl soroban_env_host::host::Host>::invoke_function\n       4: preflight::preflight::preflight_invoke_hf_op\n       5: preflight::preflight_invoke_hf_op::{{closure}}\n       6: core::ops::function::FnOnce::call_once{{vtable.shim}}\n       7: preflight::catch_preflight_panic\n       8: _cgo_0b49d6ed4a0b_Cfunc_preflight_invoke_hf_op\n                 at tmp/go-build/cgo-gcc-prolog:103:11\n       9: runtime.asmcgocall\n                 at ./runtime/asm_amd64.s:848\n    \n    ",
+    "events": [
+      "AAAAAAAAAAAAAAAAAAAAAgAAAAAAAAADAAAADwAAAAdmbl9jYWxsAAAAAA0AAAAgzAP+dP0PsNzYvFF1pv7a8RQXwH5eg3uZBbbWjE9PwAsAAAAPAAAACWluY3JlbWVudAAAAAAAAAMAAAAD",
+      "AAAAAAAAAAAAAAABzAP+dP0PsNzYvFF1pv7a8RQXwH5eg3uZBbbWjE9PwAsAAAACAAAAAAAAAAIAAAAPAAAABWVycm9yAAAAAAAAAgAAAAEAAAAHAAAAEAAAAAEAAAACAAAADgAAAC1WTSBjYWxsIGZhaWxlZDogRnVuYyhNaXNtYXRjaGluZ1BhcmFtZXRlckxlbikAAAAAAAAPAAAACWluY3JlbWVudAAAAA=="
+    ],
+    "cost": {
+      "cpuInsns": "0",
+      "memBytes": "0"
+    },
+    "latestLedger": 2552013
+  }
+}
+```
+
+</Tab>
+</Tabs>
+
+{/* /rpc-method */}
 
-:::note
+<Note>
 
 `simulateTransaction` can also invoke read-only functions for free.
 
-:::
+</Note>
 
 ### Using the Lab
 
diff --git a/docs/data/apis/rpc/api-reference/structure/README.mdx b/docs/data/apis/rpc/api-reference/structure/README.mdx
deleted file mode 100644
index e6843d84c..000000000
--- a/docs/data/apis/rpc/api-reference/structure/README.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: RPC API Reference
-sidebar_position: 31
-sidebar_label: Structure
-description: RPC provides an API for interacting with the Stellar network.
-sidebar_key: rpc-api-structure
----
-
-import DocCardList from "@theme/DocCardList";
-
-How the RPC API is structured.
-
-<DocCardList />
diff --git a/docs/data/apis/rpc/api-reference/structure/_category_.json b/docs/data/apis/rpc/api-reference/structure/_category_.json
deleted file mode 100644
index 6b391f4e5..000000000
--- a/docs/data/apis/rpc/api-reference/structure/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsed": true
-  }  
\ No newline at end of file
diff --git a/docs/data/apis/rpc/api-reference/structure/data-format.mdx b/docs/data/apis/rpc/api-reference/structure/data-format.mdx
index 0077a4e53..2b835f3e6 100644
--- a/docs/data/apis/rpc/api-reference/structure/data-format.mdx
+++ b/docs/data/apis/rpc/api-reference/structure/data-format.mdx
@@ -1,11 +1,11 @@
 ---
-sidebar_position: 60
 title: Data Formats
+description: "XDR Format"
 ---
 
 ### XDR Format
 
-In the Stellar network, transactions are encoded using a standardized protocol called [External Data Representation](../../../../../learn/fundamentals/data-format/xdr.mdx) (XDR).
+In the Stellar network, transactions are encoded using a standardized protocol called [External Data Representation](../../../../../learn/fundamentals/data-format/xdr) (XDR).
 
 In RPC, you will encounter XDR when [simulating](../methods/simulateTransaction) and [sending](../methods/sendTransaction) transactions, as well as when retrieving [transactions](../methods/getTransactions), [ledgers](../methods/getLedgers), and [ledger entries](../methods/getLedgerEntries).
 
@@ -17,9 +17,7 @@ All RPC endpoints which return encoded XDR fields accept the `xdrFormat` attribu
 
 In the event that a `json` output format is requested, response fields suffixed with `Xdr` will be omitted and replaced with their `Json` suffixed counterparts.
 
-<ExampleResponse title="Example getTransaction response">
-
-```json
+```json Example getTransaction response
 {
   // xdrFormat = 'base64'
   "resultMetaXdr": "AAAAAwAAAAAAAAACAAAAAwAWuFYAAAAAAAAAAEBQYAimx5waQHaAptKgy2a/IAHMSe96ETt5wiMOSpKXAAAAF0JZ4rAAACHUAAekYwAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAAAAAAMAAAAAABa4VAAAAABnyjD0AAAAAAAAAAEAFrhWAAAAAAAAAABAUGAIpsecGkB2gKbSoMtmvyABzEnvehE7ecIjDkqSlwAAABdCWeKwAAAh1AAHpGQAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAAAAAADAAAAAAAWuFYAAAAAZ8ow/gAAAAAAAAAAAAAAAAAAAAA=",
@@ -63,5 +61,3 @@ In the event that a `json` output format is requested, response fields suffixed
   }
 }
 ```
-
-</ExampleResponse>
diff --git a/docs/data/apis/rpc/api-reference/structure/index.mdx b/docs/data/apis/rpc/api-reference/structure/index.mdx
new file mode 100644
index 000000000..1b12c3c64
--- /dev/null
+++ b/docs/data/apis/rpc/api-reference/structure/index.mdx
@@ -0,0 +1,26 @@
+---
+title: RPC API Reference
+sidebarTitle: Structure
+description: RPC provides an API for interacting with the Stellar network.
+sidebar_key: rpc-api-structure
+---
+
+How the RPC API is structured.
+
+<CardGroup cols={2}>
+  <Card title="JSON-RPC" icon="file-lines" href="/docs/data/apis/rpc/api-reference/structure/json-rpc">
+
+    Stellar-RPC will accept HTTP POST requests using the JSON-RPC 2.0 specification.
+
+  </Card>
+  <Card title="Pagination" icon="file-lines" href="/docs/data/apis/rpc/api-reference/structure/pagination">
+
+    For methods which support it, the pagination arguments are passed as a final object argument with two values.
+
+  </Card>
+  <Card title="Data Formats" icon="file-lines" href="/docs/data/apis/rpc/api-reference/structure/data-format">
+
+    In the Stellar network, transactions are encoded using a standardized protocol called External Data Representation (XDR).
+
+  </Card>
+</CardGroup>
diff --git a/docs/data/apis/rpc/api-reference/structure/json-rpc.mdx b/docs/data/apis/rpc/api-reference/structure/json-rpc.mdx
index fe3a5dd6a..ad6aab1b2 100644
--- a/docs/data/apis/rpc/api-reference/structure/json-rpc.mdx
+++ b/docs/data/apis/rpc/api-reference/structure/json-rpc.mdx
@@ -1,6 +1,6 @@
 ---
-sidebar_position: 40
 title: JSON-RPC
+description: "Stellar-RPC will accept HTTP POST requests using the [JSON-RPC 2.0] specification."
 ---
 
 Stellar-RPC will accept HTTP POST requests using the [JSON-RPC 2.0] specification. Errors are returned via the [jsonrpc error object] wherever possible (and makes sense).
@@ -11,11 +11,11 @@ To interact with stellar-rpc from inside a JavaScript application, use the [Java
 
 When XDR is passed as a parameter or returned, it is always a string encoded using standard base64.
 
-:::info
+<Info>
 
 Please note that parameter structure must contain named parameters as a by-name object, and not as positional arguments as a by-position array. Positional arguments as a by-position array will be deprecated in future RPC releases.
 
-:::
+</Info>
 
 ## Error codes
 
@@ -65,5 +65,5 @@ Stellar-RPC provides an [OpenRPC] specification document that can be used to moc
 [JavaScript SDK]: https://github.com/stellar/js-stellar-sdk
 [OpenRPC]: https://open-rpc.org/
 [methods]: ../methods
-[specification document here]: https://raw.githubusercontent.com/stellar/stellar-docs/main/static/stellar-rpc.openrpc.json
-[OpenRPC Playground]: https://playground.open-rpc.org/?schemaUrl=https://raw.githubusercontent.com/stellar/stellar-docs/main/static/stellar-rpc.openrpc.json
+[specification document here]: https://developers.stellar.org/stellar-rpc.openrpc.json
+[OpenRPC Playground]: https://playground.open-rpc.org/?schemaUrl=https://developers.stellar.org/stellar-rpc.openrpc.json
diff --git a/docs/data/apis/rpc/api-reference/structure/pagination.mdx b/docs/data/apis/rpc/api-reference/structure/pagination.mdx
index 09b17fca3..6e1fb61f8 100644
--- a/docs/data/apis/rpc/api-reference/structure/pagination.mdx
+++ b/docs/data/apis/rpc/api-reference/structure/pagination.mdx
@@ -1,6 +1,6 @@
 ---
-sidebar_position: 50
 title: Pagination
+description: "For methods which support it, the pagination arguments are passed as a final object argument with two values."
 ---
 
 For methods which support it, the pagination arguments are passed as a final object argument with two values:
@@ -10,9 +10,9 @@ For methods which support it, the pagination arguments are passed as a final obj
 
 | Method | Limit range | Default limit |
 | --- | --- | --- |
-| [`getEvents`](../methods/getEvents.mdx) | 1 to 10000 | 100 |
-| [`getLedgers`](../methods/getLedgers.mdx) | 1 to 200 | 50 |
-| [`getTransactions`](../methods/getTransactions.mdx) | 1 to 200 | 50 |
+| [`getEvents`](../methods/getEvents) | 1 to 10000 | 100 |
+| [`getLedgers`](../methods/getLedgers) | 1 to 200 | 50 |
+| [`getTransactions`](../methods/getTransactions) | 1 to 200 | 50 |
 
 These upper limits are hardcoded in Stellar RPC for performance reasons.
 
diff --git a/docs/data/apis/rpc/index.mdx b/docs/data/apis/rpc/index.mdx
new file mode 100644
index 000000000..79952cf70
--- /dev/null
+++ b/docs/data/apis/rpc/index.mdx
@@ -0,0 +1,42 @@
+---
+title: RPC Introduction
+sidebarTitle: RPC
+"og:title": "Use the Stellar RPC to Access Blockchain Data, Query Transactions & More"
+description: "Learn how to use RPC methods to view current state, access blockchain data, interact with smart contracts, query transactions, and more on the Stellar network."
+---
+
+<Info>
+
+Stellar-RPC was renamed from Soroban-RPC in Nov 2024. Additional context on this decision can be found on our [developer blog].
+
+</Info>
+
+Stellar RPC is a lightweight tool that provides real-time access to Stellar network data. Much like RPC nodes in other blockchain ecosystems, it allows developers to query the network efficiently. Whether you’re building a non-custodial wallet, issuing assets, or monitoring network activity, Stellar RPC is designed to provide trusted, stable infrastructure that anyone can run.
+
+For any new builders coming to Stellar, Stellar RPC should be your starting point—it’s built to align with the growing needs of the ecosystem. RPC can be accessed via cURL or one of the [Stellar SDKs](/docs/tools/sdks).
+
+## Why Run RPC?
+
+Running RPC within your own infrastructure provides a number of benefits. You can:
+
+- Have full operational control without dependency on any third party provider for network data and transaction submission. The only way to harness the true power of a decentralized blockchain!
+- Avoid the added overhead of directly interacting with [Stellar Core], whose primary focus is performance and therefore provides a very limited API
+- Avoid the added overhead of storing way more data than your application actually needs, as would be the case when running [Horizon]
+
+What Stellar RPC is not:
+
+- An indexer for historical data. RPC retains only a bounded, recent window of history (about 7 days by default).
+- A primary backend service for your application. Use RPC as your gateway to the blockchain, but ingest and index only the data you care about.
+- A drop-in replacement for Horizon. Horizon provides several indexing features not commonly supported by RPC nodes. We believe these business opportunities should be passed back to third party applications (indexers, analytics providers, etc) and away from the SDF.
+
+## In These Docs
+
+- [Admin Guide](/docs/data/apis/rpc/admin-guide): how to set up and operate your own RPC instance.
+- [RPC Methods](/docs/data/apis/rpc/api-reference/methods): descriptions of RPC methods, including their expected inputs and outputs.
+- [Structure](/docs/data/apis/rpc/api-reference/structure): how the RPC API is structured.
+- [Ecosystem Providers](/docs/data/apis/rpc/providers): third party providers that provide RPC instances as a service.
+
+[quickstart]: https://github.com/stellar/quickstart
+[developer blog]: https://stellar.org/blog/foundation-news/stellar-rpc-has-arrived
+[Stellar Core]: /docs/validators
+[Horizon]: /docs/data/apis/horizon
diff --git a/docs/data/apis/rpc/providers.mdx b/docs/data/apis/rpc/providers.mdx
index 42ff60baf..edfc17a0c 100644
--- a/docs/data/apis/rpc/providers.mdx
+++ b/docs/data/apis/rpc/providers.mdx
@@ -1,6 +1,6 @@
 ---
-sidebar_position: 60
 title: Providers
+description: "Multiple infrastructure providers have made Stellar RPC services available, and offer plans ranging from free to dedicated instances."
 ---
 
 Multiple infrastructure providers have made Stellar RPC services available, and offer plans ranging from free to dedicated instances. These providers can be used for development, testing, and production.
@@ -26,7 +26,7 @@ These providers allow access to the Futurenet, Testnet and Mainnet network.
 | [GetBlock](https://getblock.io/nodes/xlm/) | ❌ | ❌ | ✅ | ✅ | ✅ |
 | [node101](https://node101.io/en/rpc/stellar) | ❌ | ✅ | ✅ | ✅ | ✅ |
 
-\*_RPC Archive is a new option for those looking to retrieve full ledger history. Currently only the [getLedgers](./api-reference/methods/getLedgers.mdx) RPC method supports this feature. You can choose one of the providers above, or create your own getLedgers archive by following [these steps](./admin-guide/data-lake-integration.mdx)._
+\*_RPC Archive is a new option for those looking to retrieve full ledger history. Currently only the [getLedgers](./api-reference/methods/getLedgers) RPC method supports this feature. You can choose one of the providers above, or create your own getLedgers archive by following [these steps](./admin-guide/data-lake-integration)._
 
 _The "Dedicated Nodes" column represents providers who host full nodes as a service._
 
diff --git a/docs/data/index.mdx b/docs/data/index.mdx
new file mode 100644
index 000000000..6e4b06424
--- /dev/null
+++ b/docs/data/index.mdx
@@ -0,0 +1,64 @@
+---
+title: Data Overview
+description: "There are several products to choose from when interacting with the Stellar Network, and each one is optimized for different access patterns, so it's important to choose the right tool based on your specific use-case. These tools allow users to query network data, submit transactions, and interact with smart contracts without needing to understand the low-level details of Stellar Core."
+---
+
+Use the summaries below to determine which types of data tools are right for your use case.
+
+## Compare Data Products
+
+SDF maintains four data products. Two are APIs and two are for bulk historical data, so start by picking the row that matches how you want to consume the data.
+
+|  | [RPC](/docs/data/apis/rpc) | [Horizon](/docs/data/apis/horizon) | [Hubble](/docs/data/analytics/hubble) | [Galexie](/docs/data/indexers/build-your-own/galexie) |
+| --- | --- | --- | --- | --- |
+| Type | API | API | Data warehouse | Ledger export tool |
+| Interface | JSON-RPC | REST | SQL (BigQuery) | XDR files in your data lake |
+| Real-time data | ✅ | ✅ | ❌ | ❌ |
+| Historical data | About 7 days | 1 year\* | Full | Full |
+| Smart contract data | ✅ | ❌ | ✅ | ✅ |
+| Transaction submission | ✅ | ✅ | ❌ | ❌ |
+| Transaction simulation | ✅ | ❌ | ❌ | ❌ |
+| Curated and parsed data | ❌ | ✅ | ✅ | ❌ |
+| Hosted by SDF | Testnet and futurenet | Mainnet, testnet, and futurenet\* | Public BigQuery dataset | None\*\* |
+
+\*_The SDF-hosted Horizon keeps one year of history and is nearing end-of-life in favor of RPC. A self-hosted Horizon can serve full history, but Hubble or Galexie are the recommended tools for that._
+
+\*\*_SDF does not host a Galexie data lake, but [several providers](/docs/data/indexers/build-your-own/galexie/providers) make public ones available._
+
+The [Ingest SDK](/docs/data/indexers/build-your-own/ingest-sdk) and [Processors](/docs/data/indexers/build-your-own/processors) are libraries for building on top of these products rather than data products themselves. Third-party APIs, indexers, and analytics platforms are listed on their own pages in each section below.
+
+## [Analytics](/docs/data/analytics)
+
+Explore and analyze Stellar network data to uncover trends, track activity, and generate insights for decision-making and reporting.
+
+**Why Use It:**
+
+- You want historical insights and visualizations for network activity and ecosystem health
+- You don't need to submit transactions to the network
+- You don't need real-time data
+
+## [APIs](/docs/data/apis)
+
+Connect to the Stellar network in real-time, enabling seamless data retrieval, transaction submission, and application integration.
+
+**Why Use It:**
+
+- You want to develop applications that interact with Stellar
+- You want real-time data access and transaction submission and processing
+
+## [Indexers](/docs/data/indexers)
+
+Organize and optimize Stellar blockchain data for efficient querying, deeper analysis, and enhanced accessibility.
+
+**Why Use It:**
+
+- You want structured and scalable access to historical and real-time blockchain data
+- You want easy access to processed and transformed raw ledger data for querying
+
+## [Oracles](/docs/data/oracles)
+
+Integrate off-chain data with the Stellar network, enabling smart contracts and decentralized applications to interact with external information sources.
+
+**Why Use It:**
+
+- You want to use off-chain data in conjunction with Stellar smart contracts for expanded functionality and automation
diff --git a/docs/data/indexers/README.mdx b/docs/data/indexers/README.mdx
deleted file mode 100644
index 28b10b792..000000000
--- a/docs/data/indexers/README.mdx
+++ /dev/null
@@ -1,113 +0,0 @@
----
-title: Indexers Overview
-sidebar_label: Indexers
-sidebar_position: 0
----
-
-## What is an indexer, and why would you need one?
-
-When you first start building on a smart contract platform like Stellar, at first you can get everything you need from RPC calls. You write a contract, or launch a Stellar Classic Asset and [wrap it in a smart contract](../../tokens/stellar-asset-contract.mdx), and you make a bundle of RPC calls from your frontend app directly to your smart contracts.
-
-At some point, though, you are likely to run into limitations with this approach.
-
-1. You might need to make _too many_ RPC calls. Imagine: your app lists 20 of a user's NFTs per page. First RPC call: get a list of NFT IDs for this user. Then: 20 simultaneous RPC calls to get data for each NFT. And possibly: for each of those, make additional HTTP requests to S3 buckets or IPFS nodes to fetch image data, etc. This can make your app slow, or even get you rate-limited by an RPC provider.
-2. You might want to show _historic_ data, like every time an NFT changed ownership. This sort of data lives _in the history of the blockchain_, but is not accessible via RPC calls to the most up-to-date version of a specific contract. Those would only return the current owner.
-
-Additionally, even some information that is currently available from [Horizon] will also require indexing services in the future, as Horizon will be deprecated.
-
-## What exactly is indexing?
-
-The word "indexing" has come to encompass a large array of use-cases. What all of them have in common is that they process and structure blockchain data. Let's think of it in the order of what you, an app-builder or small team, will need:
-
-### 1. Off-the-shelf APIs for common data {/* #portfolio-apis */}
-
-This is the kind of stuff you might get from Horizon today, but can include more than that. For example, many indexing services in this category also provide the "every time an NFT changed ownership" kind of data mentioned above.
-
-Lots of apps need this kind of data, and it tends to have a standard shape. This makes it profitable for companies to build SaaS products, offering API access for a price (often with a free tier, appropriate for your early-stage startup or hackathon project).
-
-In the biz, these are called _Portfolio APIs._ Well-known companies offering them:
-
-- [Alchemy]: a widely-used data provider (popular on Ethereum), now live on Stellar. Its [Stellar Data API](https://www.alchemy.com/docs/reference/stellar-data-api-overview) serves indexed **transfer history**, **account balances**, and **NFT holdings** across Stellar assets and contract tokens — letting you query this data without running your own indexer (JSON request bodies, opaque `pageKey` pagination). Alchemy also provides [Stellar RPC](https://www.alchemy.com/docs/stellar/stellar-api-overview#stellar-apis) and appears in the [RPC providers](../apis/rpc/providers.mdx) list.
-
-- [Allium]: currently building Stellar support, launching Q1 2026
-
-- [OBSRVR]: a home-grown Stellar-native offering, providing both RPC services and [Obsrvr Gateway](https://www.withobsrvr.com/products/gateway), promising "powerful APIs for real-time data fetching, transaction processing, and easy integration into existing systems."
-
-- [Horizon]: as mentioned above, Horizon will soon be deprecated, but for now it is the only way to get some of this data.
-
-### 2. Streaming & transforming data to a custom app database {/* #custom-transformations */}
-
-Not all apps have data that fits a standard shape. Most, probably, need custom data transformation.
-
-Consider again the NFT example. Wouldn't it be great to return all needed NFT data in _one_ request, rather than N+1? That's what this style of indexing provides. And even better: you can (often) use these indexing solutions to aggregate data from multiple sources. If your NFT app stores additional information on IPFS, you could consolidate all of that off-chain data to your database as well. This makes your app much faster, saves you network & RPC requests, and creates new architecture possibilities.
-
-Well-known options:
-
-- [The Graph]: one of the earliest and most popular-at-the-time options on Ethereum. They now offer three main products:
-  1. [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs): their main & most famous offering, providing a [decentralized approach](https://thegraph.com/docs/en/subgraphs/developing/publishing/publishing-a-subgraph) to custom data transformation & hosting. The Graph's use of GraphQL APIs made GraphQL a popular choice for this entire category of indexing.
-  2. **Token API**, for Indexing [Use Case #1](#portfolio-apis) described above
-  3. **Substreams**, for [Use Case #3](#analytics) described below
-
-  The Graph offers Stellar support for Substreams, with no current plans to expand Subgraph or Token API support to Stellar.
-
-- [Goldsky]: one of the currently-most-loved options on Ethereum for this use-case. Goldsky provides [two main products](https://docs.goldsky.com/subgraph-vs-mirror):
-  1. **Subgraphs**: similar to those offered by The Graph, but data lives on Goldsky's own infrastructure rather than a decentralized network. Goldsky only offers this for EVM-based chains, with no plans to offer Subgraph support for Stellar.
-  2. **Mirror**, also called **Pipelines**: a highly efficient tool to Extract, Transform, & Load (ETL) data into your own database. Goldsky Mirrors already support Stellar; see [their documentation](https://docs.goldsky.com/chains/stellar).
-
-- [Mercury]: a home-grown Stellar-native team providing streamlined Soroban (Smart Contract) support via their [Retroshades](https://docs.mercurydata.app/retroshades/introduction-to-retroshades) product. Note that this streamlined Soroban support comes at the cost of _only_ supporting Soroban! Mercury also provide [Mercury "Classic"](https://docs.mercurydata.app/mercury-classic/introduction), giving access to contract events & Stellar transactions via a GraphQL interface, which might fit Indexer Use Case #1 more.
-
-- [SubQuery]: Decentralized Indexer SDK, Decentralized RPCs, & AI Apps. Supports 300+ chains. Like The Graph, uses a decentralized model.
-
-- [OnFinality]: a big player in the Polkadot ecosystem, now expanding to other blockchains. OnFinality provides data _hosting_ services for your SubQuery logic. SubQuery is the _software_, OnFinality is the _infra_, hosting 1. the pre-transformed raw Stellar data, 2. your SubGraph SDK-authored Extract, Transform, and Load (ETL) processor and 3. your final transformed data.
-
-- [Allium]: in addition to their Portfolio APIs offering, Allium is also under contract with SDF to build out tools for both Indexing Use Case #2 (this one) and Indexing Use Case #3 (see below), with target launch date of Q1 2026.
-
-- [Space and Time]: one challenge with most indexing approaches is the reintroduction of trusted 3rd parties into what is otherwise a verifiable, trustless software stack. Space and Time aims to fix this with "Proof of Indexing" and "Proof of SQL", using Zero-Knowledge proofs to offer tamper-proof computation for enterprises and dapps. Space and Time's Stellar support [launched](https://www.spaceandtime.io/blog/space-and-time-enables-new-sophisticated-financial-apps-for-the-stellar-ecosystem) in Q4 2025.
-
-- [OBSRVR Flow]: "Structured ledger data and contract events straight to your app or warehouse—no ETL needed." Currently in private beta.
-
-### 3. Blockchain-Flavored Big-Data Analytics {/* #analytics */}
-
-For business intelligence, compliance, tracing suspicious operations, DeFi metric tracking, transaction flow analysis, etc. When your enterprise reaches a certain scale, it's worth paying Data Engineers to set up custom ETL pipelines and manage databases/datalakes, and then paying Data Analysts to answer questions about how people are interacting with your systems.
-
-The companies building tools for Indexer Use Case #2 above (The Graph, Goldsky, Allium, etc) tend to also have tools for Use Case #3.
-
-While often referred to as _indexing_, you can also think of this category as _analytics_. See the [analytics documentation](../analytics/README.mdx) for solutions custom-tailored to this use-case.
-
-## Build Your Own
-
-If none of the indexing providers mentioned above currently meet your needs, you can also build your own. Start with this [tutorial on how to build your own custom network ingestion pipeline](../../build/apps/ingest-sdk/overview.mdx). Along the way, you'll use the following tools & services:
-
-### [Galexie](./build-your-own/galexie/README.mdx)
-
-Galexie is a tool for acquiring Stellar ledger metadata from the network and exporting to external storage, a data lake. Galexie is the foundation of the Composable Data Pipeline (CDP) and serves as the first step in extracting raw Stellar ledger metadata and making it accessible. Learn more about CDP’s benefits and applications in [this blog post](https://stellar.org/blog/developers/composable-data-platform).
-
-**Why Use It:**
-
-- You want to maintain a data lake of pre-computed ledger metadata for historical and currently closed network ledgers.
-
-### [Ingest SDK](./build-your-own/ingest-sdk/README.mdx)
-
-A set of Golang packages which can be used within an application as a programmatic domain model to interact with Stellar network.
-
-**Why Use It:**
-
-- You want rapid development of applications in Golang which can acquire and parse ledger meta data and ledger entries from Stellar network.
-- You want an intuitive, compile-time, type-safe application developer experience.
-- You want to programmatically access History Archives to retrieve ledger entries.
-
-### [Processors](./build-your-own/processors/README.mdx)
-
-A suite of Go packages that help you parse Stellar blockchain data.
-
-[Horizon]: ../apis/horizon/README.mdx
-[Allium]: https://www.allium.so/
-[Alchemy]: https://www.alchemy.com/
-[Goldsky]: https://goldsky.com/
-[OBSRVR]: https://www.withobsrvr.com/
-[The Graph]: https://thegraph.com/docs/en/about/
-[Mercury]: https://docs.mercurydata.app/
-[SubQuery]: https://subquery.network/
-[OnFinality]: https://onfinality.io/
-[Space and Time]: https://www.spaceandtime.io/
-[OBSRVR Flow]: https://www.withobsrvr.com/products/flow
diff --git a/docs/data/indexers/build-your-own/README.mdx b/docs/data/indexers/build-your-own/README.mdx
deleted file mode 100644
index 0b2bd880d..000000000
--- a/docs/data/indexers/build-your-own/README.mdx
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Build Your Own
-sidebar_position: 0
----
-
-If none of the indexing providers mentioned [in the overview](../README.mdx) meet your needs, you can also build your own. Start with this [tutorial on how to build your own custom network ingestion pipeline](../../../build/apps/ingest-sdk/overview.mdx). Along the way, you'll use the following tools & services:
-
-## [Galexie](./galexie/README.mdx)
-
-Galexie is a tool for acquiring Stellar ledger metadata from the network and exporting to external storage,a data lake. Galexie is the foundation of the Composable Data Pipeline (CDP) and serves as the first step in extracting raw Stellar ledger metadata and making it accessible. Learn more about CDP’s benefits and applications in [this blog post](https://stellar.org/blog/developers/composable-data-platform).
-
-**Why Use It:**
-
-- You want to maintain a data lake of pre-computed ledger metadata for historical and currently closed network ledgers.
-
-## [Ingest SDK](./ingest-sdk/README.mdx)
-
-A set of Golang packages which can be used within application as a programmatic domain model to interact with Stellar network.
-
-**Why Use It:**
-
-- You want rapid development of applications in Golang which can acquire and parse ledger meta data and ledger entries from Stellar network.
-- You want an intuitive, compile-time, type-safe application developer experience.
-- You want to programmatically access History Archives to retrieve ledger entries.
-
-## [Processors](./processors/README.mdx)
-
-A suite of Go packages that help you parse Stellar blockchain data.
diff --git a/docs/data/indexers/build-your-own/galexie/README.mdx b/docs/data/indexers/build-your-own/galexie/README.mdx
deleted file mode 100644
index 6071d7d5e..000000000
--- a/docs/data/indexers/build-your-own/galexie/README.mdx
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Galexie
-sidebar_position: 0
----
-
-## What is Galexie?
-
-Galexie is a tool for extracting, processing, exporting Stellar ledger metadata to external storage, and creating a data lake of pre-processed ledger metadata. Galexie is the foundation of the Composable Data Pipeline (CDP) and serves as the first step in extracting raw Stellar ledger metadata and making it accessible. Learn more about CDP’s benefits and applications in this [blog post](https://stellar.org/blog/developers/composable-data-platform).
-
-## What Are the Key Features of Galexie?
-
-Galexie is designed to make streamlined and efficient export of ledger metadata via a simple user-friendly interface. Its key features include:
-
-- Exporting Stellar ledger metadata to cloud storage
-- Configurable to export a specified range of ledgers or continuously stream new ledgers as they are created on the Stellar network
-- Exporting ledger metadata in XDR which is Stellar Core’s native format.
-- Compressing data before export to optimize storage efficiency in the data lake.
-
-![](/assets/galexie/galexie-architecture.png)
-
-## Why XDR Format?
-
-Exporting data in XDR—the native Stellar Core format—enables Galexie to preserve full transaction metadata, ensuring data integrity while keeping storage efficient. The XDR format maintains compatibility with all Stellar components, providing a solid foundation for applications that require consistent access to historical data. Refer to the [XDR](../../../../learn/fundamentals/data-format/xdr.mdx) documentation for more information on this format.
-
-The [Data Lake Storage Format](./data-lake-format.mdx) page describes how Galexie names and compresses these files. Read it if your application reads the data lake directly instead of through the ingest SDK or Stellar RPC.
-
-## Why Run Galexie?
-
-Galexie enables you to make a copy of Stellar ledger metadata over which you have complete control. Galexie can continuously sync your data lake with the latest ledger data freeing you up from tedious data ingestion and allowing you to focus on building customized applications that consume and analyze exported data.
-
-## What Can You Do with the Data Lake Created by Galexie?
-
-Once data is stored in the cloud, it becomes easily accessible for integration with modern data processing and analytics tools, enabling various workflows and insights.
-
-The pre-processed ledger data exported by Galexie can be utilized across various applications, such as:
-
-- Analytics Tools: Analyze trends over time.
-- Audit Applications: Retrieve historical transaction data for auditing and compliance.
-- Monitoring Systems: Create tools to track network metrics.
diff --git a/docs/data/indexers/build-your-own/galexie/admin_guide/README.mdx b/docs/data/indexers/build-your-own/galexie/admin_guide/README.mdx
deleted file mode 100644
index 2586a379d..000000000
--- a/docs/data/indexers/build-your-own/galexie/admin_guide/README.mdx
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: Admin Guide
-sidebar_position: 15
----
-
-This guide provides step-by-step instructions on installing and running the Galexie.
diff --git a/docs/data/indexers/build-your-own/galexie/admin_guide/_category_.json b/docs/data/indexers/build-your-own/galexie/admin_guide/_category_.json
deleted file mode 100644
index 9e3a55f45..000000000
--- a/docs/data/indexers/build-your-own/galexie/admin_guide/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": true
-}
diff --git a/docs/data/indexers/build-your-own/galexie/admin_guide/configuring.mdx b/docs/data/indexers/build-your-own/galexie/admin_guide/configuring.mdx
index f43edacb1..f193c72f2 100644
--- a/docs/data/indexers/build-your-own/galexie/admin_guide/configuring.mdx
+++ b/docs/data/indexers/build-your-own/galexie/admin_guide/configuring.mdx
@@ -1,10 +1,8 @@
 ---
 title: Configuring
-sidebar_position: 20
+description: "Specify the cloud storage service to be used to export ledger metadata."
 ---
 
-# Configuring
-
 ## Steps to Configure Galexie
 
 ### Key Settings Include
@@ -45,7 +43,7 @@ ledgers_per_file = 1
 files_per_partition = 64000
 ```
 
-These two settings decide the object keys in the bucket. See [Data Lake Storage Format](../data-lake-format.mdx) for the naming rules and for the `.config.json` file that records these values in the data lake.
+These two settings decide the object keys in the bucket. See [Data Lake Storage Format](/docs/data/indexers/build-your-own/galexie/data-lake-format) for the naming rules and for the `.config.json` file that records these values in the data lake.
 
 #### Use a Custom Core Config (Optional)
 
@@ -57,7 +55,7 @@ Copy an existing `core.cfg` file such as the `captive-core-pubnet.cfg` provided
 captive_core_toml_path = "my-captive-core.cfg"
 ```
 
-- Please see the [Choosing Your Quorum Set](../../../../../validators/admin-guide/configuring.mdx#choosing-your-quorum-set) for more information about `core.cfg` quorum set configuration
+- Please see the [Choosing Your Quorum Set](../../../../../validators/admin-guide/configuring#choosing-your-quorum-set) for more information about `core.cfg` quorum set configuration
 - A list of customizable core parameters can be found [here](https://github.com/stellar/stellar-core/blob/master/src/main/Config.h)
 
 The default `core.cfg` used by Galexie will enable the following core parameters:
@@ -69,11 +67,11 @@ The default `core.cfg` used by Galexie will enable the following core parameters
 - **EMIT_CLASSIC_EVENTS -** classic events will be enabled and emitted for protocol `>= 23`
 - **BACKFILL_STELLAR_ASSET_EVENTS -** classic events will be enabled and emitted for protocol `<= 22`. This parameter also requires `EMIT_CLASSIC_EVENTS` to be enabled
 
-:::warning
+<Warning>
 
 When you provide a custom core configuration file, it completely replaces the Galexie's default core configuration. This means you must explicitly set any parameters you want to enable, including the ones that are enabled by default in Galexie. Any parameter not listed in your custom config will be set to false.
 
-:::
+</Warning>
 
 ### Running Galexie on an Instance
 
diff --git a/docs/data/indexers/build-your-own/galexie/admin_guide/full-history-exporting.mdx b/docs/data/indexers/build-your-own/galexie/admin_guide/full-history-exporting.mdx
index 090ba553d..937ae1ceb 100644
--- a/docs/data/indexers/build-your-own/galexie/admin_guide/full-history-exporting.mdx
+++ b/docs/data/indexers/build-your-own/galexie/admin_guide/full-history-exporting.mdx
@@ -1,6 +1,6 @@
 ---
 title: Full History Exporting
-sidebar_position: 60
+description: "This page outlines best practices for using Galexie to build a data lake with the complete history of ledger metadata."
 ---
 
 This page outlines best practices for using Galexie to build a data lake with the complete history of ledger metadata.
@@ -28,7 +28,7 @@ The estimates are based on GCP Compute Engine and Google Cloud Storage costs
 
 The best way to export full history with Galexie is by running multiple individual instances of Galexie in parallel. For reference, it is estimated to take approximately 150 days to export full history using a single Galexie instance. Running in parallel with 40-50 Galexie instances takes roughly 4-5 days.
 
-1. Make sure you have set up a storage system and have appropriate hardware available as defined in the Galexie [Prerequisites](./prerequisites.mdx)
+1. Make sure you have set up a storage system and have appropriate hardware available as defined in the Galexie [Prerequisites](./prerequisites)
 2. Determine how many parallel instances of Galexie that you'd want to run
 3. Remember to pass non-overlapping ledger ranges to each of your Galexie instances
 
@@ -42,7 +42,7 @@ Let's say there are 50,000,000 ledgers that Galexie needs to export.
   - 15 instances to process genesis to 29,999,999
   - 35 instances to process 30,000,000 to 50,000,000
 
-Each instance will follow the same [Running Galexie](./running.mdx) instructions
+Each instance will follow the same [Running Galexie](./running) instructions
 
 ```
 galexie append --start <start_ledger> --end <end_ledger>
diff --git a/docs/data/indexers/build-your-own/galexie/admin_guide/index.mdx b/docs/data/indexers/build-your-own/galexie/admin_guide/index.mdx
new file mode 100644
index 000000000..3b9051aed
--- /dev/null
+++ b/docs/data/indexers/build-your-own/galexie/admin_guide/index.mdx
@@ -0,0 +1,4 @@
+---
+title: Admin Guide
+description: "This guide provides step-by-step instructions on installing and running the Galexie."
+---
diff --git a/docs/data/indexers/build-your-own/galexie/admin_guide/installing.mdx b/docs/data/indexers/build-your-own/galexie/admin_guide/installing.mdx
index 0565a31a8..acd0a76f3 100644
--- a/docs/data/indexers/build-your-own/galexie/admin_guide/installing.mdx
+++ b/docs/data/indexers/build-your-own/galexie/admin_guide/installing.mdx
@@ -1,10 +1,8 @@
 ---
 title: Installing
-sidebar_position: 30
+description: "In order to install Galexie into a kubernetes cluster follow these steps."
 ---
 
-# Installing
-
 ## Kubernetes
 
 In order to install Galexie into a Kubernetes cluster follow these steps:
diff --git a/docs/data/indexers/build-your-own/galexie/admin_guide/monitoring.mdx b/docs/data/indexers/build-your-own/galexie/admin_guide/monitoring.mdx
index 564d28b77..60c83a92f 100644
--- a/docs/data/indexers/build-your-own/galexie/admin_guide/monitoring.mdx
+++ b/docs/data/indexers/build-your-own/galexie/admin_guide/monitoring.mdx
@@ -1,10 +1,8 @@
 ---
 title: Monitoring
-sidebar_position: 50
+description: "Galexie publishes metrics through an HTTP-based admin endpoint, which makes it easier to monitor its performance."
 ---
 
-# Monitoring
-
 ### Metrics
 
 Galexie publishes metrics through an HTTP-based admin endpoint, which makes it easier to monitor its performance. The data is exposed in Prometheus format, enabling easy integration with existing monitoring and alerting systems.
diff --git a/docs/data/indexers/build-your-own/galexie/admin_guide/prerequisites.mdx b/docs/data/indexers/build-your-own/galexie/admin_guide/prerequisites.mdx
index 543e3fc9e..c7ae073a7 100644
--- a/docs/data/indexers/build-your-own/galexie/admin_guide/prerequisites.mdx
+++ b/docs/data/indexers/build-your-own/galexie/admin_guide/prerequisites.mdx
@@ -1,10 +1,8 @@
 ---
 title: Prerequisites
-sidebar_position: 10
+description: "Galexie exports Stellar ledger metadata to Google Cloud Storage (GCS) or Amazon Simple Storage Service (S3)."
 ---
 
-# Prerequisites
-
 ## 1. Cloud Platform Account
 
 Galexie exports Stellar ledger metadata to Google Cloud Storage (GCS) or Amazon Simple Storage Service (S3). You will need the relevant account and credentials for the cloud storage service you choose to use
@@ -30,11 +28,11 @@ Galexie exports Stellar ledger metadata to Google Cloud Storage (GCS) or Amazon
 - Instance like AWS EC2 or GCP VM
 - Any host machine with an OCI-compliant container runtime installed like Docker ([Docker installation guide](https://docs.docker.com/engine/install)).
 
-:::note
+<Note>
 
 While it is possible to natively install Galexie (without a container runtime), this requires manual dependency management and is recommended only for advanced users.
 
-:::
+</Note>
 
 ## Hardware Requirements
 
@@ -45,4 +43,4 @@ The minimum hardware requirements for running Galexie are:\
 
 ### Full History Export
 
-Please see the [Full History Exporting](./full-history-exporting.mdx) guide for more information.
+Please see the [Full History Exporting](./full-history-exporting) guide for more information.
diff --git a/docs/data/indexers/build-your-own/galexie/admin_guide/running.mdx b/docs/data/indexers/build-your-own/galexie/admin_guide/running.mdx
index 30052c70f..aa9254313 100644
--- a/docs/data/indexers/build-your-own/galexie/admin_guide/running.mdx
+++ b/docs/data/indexers/build-your-own/galexie/admin_guide/running.mdx
@@ -1,10 +1,8 @@
 ---
 title: Running
-sidebar_position: 40
+description: "The commands and arguments described in this document can be configured in the helm chart as well as running them on an instance as described below."
 ---
 
-# Running
-
 The commands and arguments described in this document can be configured in the helm chart as well as running them on an instance as described below. The helm chart handles the config file path internally to the chart. The `--config-file` argument should not be added to the arguments variable in the helm chart.
 
 With the Docker image available and the configuration file set up, you're now ready to run Galexie and start exporting Stellar ledger data to the storage bucket.
diff --git a/docs/data/indexers/build-your-own/galexie/admin_guide/setup.mdx b/docs/data/indexers/build-your-own/galexie/admin_guide/setup.mdx
index 1d1f2f871..58731ace3 100644
--- a/docs/data/indexers/build-your-own/galexie/admin_guide/setup.mdx
+++ b/docs/data/indexers/build-your-own/galexie/admin_guide/setup.mdx
@@ -1,10 +1,8 @@
 ---
 title: Setup
-sidebar_position: 10
+description: "Galexie runs as a publisher and writes files to buckets and therefore needs to be provisioned with correct account permissions on the bucket to allow writes."
 ---
 
-# Setup
-
 Galexie runs as a publisher and writes files to buckets and therefore needs to be provisioned with correct account permissions on the bucket to allow writes. For client applications that will be consumers of files in the bucket a smaller set of account permissions will be needed to allow read only activity.
 
 ## Google Cloud Platform (GCP) for GCS
@@ -71,11 +69,11 @@ When running Galexie inside of a EKS cluster follow either the AWS documentation
 3. Use that instance profile in the creation of the EC2 instance
 4. Make sure the instance profile has the correct bucket access
 
-#### Credentials (Not Recommended)
+#### Credentials (Not Recommended) {#credentials-not-recommended-1}
 
 In order to use static credentials, [create an IAM user](https://docs.aws.amazon.com/IAM/latest/UserGuide/getting-started-workloads.html) for Galexie making sure the principal of the credentials has access to the correct bucket and generate security credentials.
 
-#### IAM Role Permissions
+#### IAM Role Permissions {#iam-role-permissions-1}
 
 When using AWS IAM to authenticate Galexie to access a bucket, use this example policy making sure to use the correct bucket destination:
 
diff --git a/docs/data/indexers/build-your-own/galexie/data-lake-format.mdx b/docs/data/indexers/build-your-own/galexie/data-lake-format.mdx
index 31af83b65..e242dca90 100644
--- a/docs/data/indexers/build-your-own/galexie/data-lake-format.mdx
+++ b/docs/data/indexers/build-your-own/galexie/data-lake-format.mdx
@@ -1,12 +1,11 @@
 ---
 title: Data Lake Storage Format
 description: How Galexie names and compresses the ledger files in a data lake, as specified by SEP-54.
-sidebar_position: 10
 ---
 
 Galexie stores ledger metadata in an object store as compressed XDR files.
 
-Unless you are building for a highly specialized case, use the [ingest SDK](../ingest-sdk/README.mdx) or [Stellar RPC](../../../apis/rpc/admin-guide/data-lake-integration.mdx) rather than reading these files directly. Both tools hide the layout described here, so your application does not have to manage it.
+Unless you are building for a highly specialized case, use the [ingest SDK](/docs/data/indexers/build-your-own/ingest-sdk) or [Stellar RPC](/docs/data/apis/rpc/admin-guide/data-lake-integration) rather than reading these files directly. Both tools hide the layout described here, so your application does not have to manage it.
 
 Read this page if one of these applies to you:
 
@@ -24,7 +23,7 @@ Galexie writes all ledger files under one configurable path in the bucket. Insid
 <ledgers-path>/<partition>/<batch>.xdr.zst
 ```
 
-Galexie omits the partition directory when [`files_per_partition`](./admin_guide/configuring.mdx#data-organization-optional) is `1`.
+Galexie omits the partition directory when [`files_per_partition`](/docs/data/indexers/build-your-own/galexie/admin_guide/configuring#data-organization-optional) is `1`.
 
 Both the partition name and the batch name start with 8 hexadecimal digits. That value is `0xFFFFFFFF` minus the first ledger sequence of the range. The subtraction reverses the order, so a listing returns the newest ledgers first. A client finds the latest ledger with one listing request and no index.
 
@@ -47,11 +46,11 @@ Put together, the full key of the first batch above is:
 <ledgers-path>/FFFFFFFF--0-15/FFFFFFFD--2-3.xdr.zst
 ```
 
-:::note
+<Note>
 
 A data store does not necessarily hold the whole ledger history. List the oldest partition to find where its history starts.
 
-:::
+</Note>
 
 ## File contents
 
@@ -72,7 +71,7 @@ struct LedgerCloseMetaBatch
 };
 ```
 
-The `ledgersPerBatch` value in the [configuration file](#configuration-file) sets the number of ledgers in each batch. Batch ranges start at sequence 0, but Galexie exports from ledger 2, so the first batch of a data store can hold fewer ledgers than the rest. Refer to the [XDR](../../../../learn/fundamentals/data-format/xdr.mdx) documentation for more information on the encoding.
+The `ledgersPerBatch` value in the [configuration file](#configuration-file) sets the number of ledgers in each batch. Batch ranges start at sequence 0, but Galexie exports from ledger 2, so the first batch of a data store can hold fewer ledgers than the rest. Refer to the [XDR](/docs/learn/fundamentals/data-format/xdr) documentation for more information on the encoding.
 
 ## Configuration file
 
@@ -86,7 +85,7 @@ SEP-54 requires a JSON configuration object at `<ledgers-path>/.config.json`. A
 | `ledgersPerBatch` | integer | The number of ledgers in each batch file. |
 | `batchesPerPartition` | integer | The number of batch files in each partition directory. |
 
-The Galexie [configuration file](./admin_guide/configuring.mdx#data-organization-optional) names the last two values `ledgers_per_file` and `files_per_partition`.
+The Galexie [configuration file](/docs/data/indexers/build-your-own/galexie/admin_guide/configuring#data-organization-optional) names the last two values `ledgers_per_file` and `files_per_partition`.
 
 Data stores written by Galexie versions before v23.0.0 do not hold this file, and their object keys end in `.xdr.zstd` instead of `.xdr.zst`. A client that reads one must get the batch and partition sizes from its own configuration. The Go `datastore` package does that when the file is absent.
 
@@ -116,7 +115,7 @@ A Stellar ledger data lake is available through the [AWS Open Data program](http
 s3://aws-public-blockchain/v1.1/stellar/ledgers/pubnet
 ```
 
-Download ledger 50000000 from the example above and print it as JSON with [`stellar xdr decode`](../../../../tools/cli/stellar-cli.mdx#stellar-xdr-decode):
+Download ledger 50000000 from the example above and print it as JSON with [`stellar xdr decode`](/docs/tools/cli/stellar-cli#stellar-xdr-decode):
 
 ```sh
 curl -s https://aws-public-blockchain.s3.amazonaws.com/v1.1/stellar/ledgers/pubnet/FD054DFF--49984000-50047999/FD050F7F--50000000.xdr.zst \
diff --git a/docs/data/indexers/build-your-own/galexie/examples/README.mdx b/docs/data/indexers/build-your-own/galexie/examples/README.mdx
deleted file mode 100644
index ec59d5ddf..000000000
--- a/docs/data/indexers/build-your-own/galexie/examples/README.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: Example Usages
-sidebar_position: 20
-sidebar_key: galexie-example-usages
----
-
-This section showcases real-world use cases of Galexie.
diff --git a/docs/data/indexers/build-your-own/galexie/examples/gcs-export.mdx b/docs/data/indexers/build-your-own/galexie/examples/gcs-export.mdx
index 8fd4edc3c..cd30c5ee9 100644
--- a/docs/data/indexers/build-your-own/galexie/examples/gcs-export.mdx
+++ b/docs/data/indexers/build-your-own/galexie/examples/gcs-export.mdx
@@ -1,10 +1,8 @@
 ---
 title: Export to GCS
-sidebar_position: 20
+description: "Goals"
 ---
 
-# Export to GCS
-
 ## Goals
 
 - Ledger Metadata is stored on Google Cloud Storage(GCS).
@@ -12,19 +10,19 @@ sidebar_position: 20
   - Ledger Metadata for each newly closed ledger on Stellar Testnet should be expediently exported to GCS.
 - Deployment shall be fully on-cloud, use GCP for all storage and compute needs.
 
-## Solution - Publisher Pipeline
+## Solution - Publisher Pipeline {#solution---publisher-pipeline}
 
 Run the Galexie Dockerhub image, [stellar/stellar-galexie](https://hub.docker.com/r/stellar/stellar-galexie) as an instance in [GCP Compute Engines](https://cloud.google.com/run/docs/create-jobs) and export the ledger metadata to [GCS bucket](https://cloud.google.com/storage/docs/json_api/v1/buckets) storage.
 
-[Galexie](../README.mdx) in this example, performs the main roles of data pipeline. It acts as the `origin` and `publisher` of ledger metadata to the Google Cloud Storage bucket which is the `sink`.
+[Galexie](/docs/data/indexers/build-your-own/galexie) in this example, performs the main roles of data pipeline. It acts as the `origin` and `publisher` of ledger metadata to the Google Cloud Storage bucket which is the `sink`.
 
 ### Prepare the Galexie configuration file locally
 
-#### `testnet-config.toml`
+#### `testnet-config.toml` {#testnet-configtoml}
 
-<CodeExample>
+<CodeGroup>
 
-```
+```text Example
 [datastore_config]
 type = "GCS"
 
@@ -39,28 +37,28 @@ files_per_partition = 10
   network = "testnet"
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Set default zone and project on gcloud
 
 Do this once, so, you don't have to repeat it on all further commands. Example commands assume this is done, ensuring all resources created are in the same GCP project and zone if applicable such as for compute.
 
-<CodeExample>
+<CodeGroup>
 
-```
+```text Example
 gcloud config set compute/zone {your zone here}
 gcloud config set project {your GCP project name}
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Store the galexie configuration file on a Compute Disk
 
 Create a new GCP Compute disk which just holds the configuration file for Galexie. It will be used in proceeding step as a volume mount for the Galexie container to access it.
 
-<CodeExample>
+<CodeGroup>
 
-```
+```text Example
 // create the raw disk in GCP project
 $ gcloud compute disks create galexie-config-disk \
   --size=10GB \
@@ -95,27 +93,27 @@ $ gcloud compute instances delete temp-instance
 
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Create a new gcloud bucket for storage of exported ledger metadata
 
-<CodeExample>
+<CodeGroup>
 
-```
+```text Example
 $ gcloud storage buckets create gs://galexie-data
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Use gcloud to deploy and run Galexie as compute instance.
 
 Configure the volume mount on the instance for Galexie to load configuration file from existing compute disk created in prior step. Specify the starting ledger sequence for Galexie to begin exporting ledger metadata, the requirements for this deloyment are to start with latest from network, which can be initially obtained from any block explorer, such as reported from [steller.expert/explorer/testnet](https://stellar.expert/explorer/testnet).
 
-In this example the `e2-medium` machine type, should suffice for [Galexie Prerequisites](../admin_guide/prerequisites.mdx).
+In this example the `e2-medium` machine type, should suffice for [Galexie Prerequisites](../admin_guide/prerequisites).
 
-<CodeExample>
+<CodeGroup>
 
-```
+```text Example
 gcloud compute instances create-with-container galexie-instance \
   --scopes=cloud-platform \
   --machine-type=e2-medium \
@@ -129,7 +127,7 @@ gcloud compute instances create-with-container galexie-instance \
   --container-arg="/mnt/config/testnet-config.toml"
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Monitor Galexie export status
 
@@ -138,6 +136,6 @@ Proceed to the GCP console:
 - `Cloud Storage->Buckets`, view the contents of the GCS `galexie-data` bucket, should see new files representing the latest ledger metadata from Testnet arriving in the bucket every minute.
 - `Compute Engine->Virtual Machines`, check the log output of `galexie-instance`, you'll see `level=info msg="Uploaded ..` lines indicating each time a new file of ledger metadata is uploaded to the GCS bucket.
 
-## Next step - Consumer Pipelines
+## Next step - Consumer Pipelines {#next-step---consumer-pipelines}
 
-Ledger metadata is now accumulating as files in your GCS bucket, you can start to explore the options for applications to consume this pre-computed network data using the [Ingest SDK](../../ingest-sdk/README.mdx) to assemble consumer driven data pipelines capable of importing and parsing the data to derive custom, enriched data models. Refer to [GCS bucket consumer pipeline](../../../../../build/apps/ingest-sdk/overview.mdx#ledger-metadata-consumer-pipeline) for relevant example code.
+Ledger metadata is now accumulating as files in your GCS bucket, you can start to explore the options for applications to consume this pre-computed network data using the [Ingest SDK](/docs/data/indexers/build-your-own/ingest-sdk) to assemble consumer driven data pipelines capable of importing and parsing the data to derive custom, enriched data models. Refer to [GCS bucket consumer pipeline](../../../../../build/apps/ingest-sdk/overview#ledger-metadata-consumer-pipeline) for relevant example code.
diff --git a/docs/data/indexers/build-your-own/galexie/examples/index.mdx b/docs/data/indexers/build-your-own/galexie/examples/index.mdx
new file mode 100644
index 000000000..78fced952
--- /dev/null
+++ b/docs/data/indexers/build-your-own/galexie/examples/index.mdx
@@ -0,0 +1,5 @@
+---
+title: Example Usages
+description: "This section showcases real-world use cases of Galexie."
+sidebar_key: galexie-example-usages
+---
diff --git a/docs/data/indexers/build-your-own/galexie/index.mdx b/docs/data/indexers/build-your-own/galexie/index.mdx
new file mode 100644
index 000000000..6f7fccd73
--- /dev/null
+++ b/docs/data/indexers/build-your-own/galexie/index.mdx
@@ -0,0 +1,39 @@
+---
+title: Galexie
+description: "Galexie is a tool for extracting, processing, exporting Stellar ledger metadata to external storage, and creating a data lake of pre-processed ledger metadata."
+---
+
+## What is Galexie?
+
+Galexie is a tool for extracting, processing, exporting Stellar ledger metadata to external storage, and creating a data lake of pre-processed ledger metadata. Galexie is the foundation of the Composable Data Pipeline (CDP) and serves as the first step in extracting raw Stellar ledger metadata and making it accessible. Learn more about CDP’s benefits and applications in this [blog post](https://stellar.org/blog/developers/composable-data-platform).
+
+## What Are the Key Features of Galexie?
+
+Galexie is designed to make streamlined and efficient export of ledger metadata via a simple user-friendly interface. Its key features include:
+
+- Exporting Stellar ledger metadata to cloud storage
+- Configurable to export a specified range of ledgers or continuously stream new ledgers as they are created on the Stellar network
+- Exporting ledger metadata in XDR which is Stellar Core’s native format.
+- Compressing data before export to optimize storage efficiency in the data lake.
+
+![](/assets/galexie/galexie-architecture.png)
+
+## Why XDR Format?
+
+Exporting data in XDR—the native Stellar Core format—enables Galexie to preserve full transaction metadata, ensuring data integrity while keeping storage efficient. The XDR format maintains compatibility with all Stellar components, providing a solid foundation for applications that require consistent access to historical data. Refer to the [XDR](/docs/learn/fundamentals/data-format/xdr) documentation for more information on this format.
+
+The [Data Lake Storage Format](/docs/data/indexers/build-your-own/galexie/data-lake-format) page describes how Galexie names and compresses these files. Read it if your application reads the data lake directly instead of through the ingest SDK or Stellar RPC.
+
+## Why Run Galexie?
+
+Galexie enables you to make a copy of Stellar ledger metadata over which you have complete control. Galexie can continuously sync your data lake with the latest ledger data freeing you up from tedious data ingestion and allowing you to focus on building customized applications that consume and analyze exported data.
+
+## What Can You Do with the Data Lake Created by Galexie?
+
+Once data is stored in the cloud, it becomes easily accessible for integration with modern data processing and analytics tools, enabling various workflows and insights.
+
+The pre-processed ledger data exported by Galexie can be utilized across various applications, such as:
+
+- Analytics Tools: Analyze trends over time.
+- Audit Applications: Retrieve historical transaction data for auditing and compliance.
+- Monitoring Systems: Create tools to track network metrics.
diff --git a/docs/data/indexers/build-your-own/galexie/providers.mdx b/docs/data/indexers/build-your-own/galexie/providers.mdx
index 1229460b1..0b054eb89 100644
--- a/docs/data/indexers/build-your-own/galexie/providers.mdx
+++ b/docs/data/indexers/build-your-own/galexie/providers.mdx
@@ -1,6 +1,6 @@
 ---
-sidebar_position: 1000
 title: Providers
+description: "Multiple infrastructure providers have made the Galexie service and data lake available, and offer plans ranging from free to paid access."
 ---
 
 Multiple infrastructure providers have made the Galexie service and data lake available, and offer plans ranging from free to paid access. These providers can be used for development, testing, and production.
@@ -16,4 +16,4 @@ These providers allow access to the Futurenet, Testnet and Mainnet network.
 
 ## Run Your Own Galexie
 
-If you are interested in running your own Galexie service and data lake, please checkout the [Admin Guide](./admin_guide/README.mdx).
+If you are interested in running your own Galexie service and data lake, please checkout the [Admin Guide](/docs/data/indexers/build-your-own/galexie/admin_guide).
diff --git a/docs/data/indexers/build-your-own/index.mdx b/docs/data/indexers/build-your-own/index.mdx
new file mode 100644
index 000000000..10e1c5a1d
--- /dev/null
+++ b/docs/data/indexers/build-your-own/index.mdx
@@ -0,0 +1,28 @@
+---
+title: Build Your Own
+description: "If none of the indexing providers mentioned in the overview meet your needs, you can also build your own. Start with this tutorial on how to build your own custom network ingestion pipeline. Along the way, you'll use the following tools & services:"
+---
+
+If none of the indexing providers mentioned [in the overview](/docs/data/indexers) meet your needs, you can also build your own. Start with this [tutorial on how to build your own custom network ingestion pipeline](/docs/build/apps/ingest-sdk/overview). Along the way, you'll use the following tools & services:
+
+## [Galexie](/docs/data/indexers/build-your-own/galexie)
+
+Galexie is a tool for acquiring Stellar ledger metadata from the network and exporting to external storage,a data lake. Galexie is the foundation of the Composable Data Pipeline (CDP) and serves as the first step in extracting raw Stellar ledger metadata and making it accessible. Learn more about CDP’s benefits and applications in [this blog post](https://stellar.org/blog/developers/composable-data-platform).
+
+**Why Use It:**
+
+- You want to maintain a data lake of pre-computed ledger metadata for historical and currently closed network ledgers.
+
+## [Ingest SDK](/docs/data/indexers/build-your-own/ingest-sdk)
+
+A set of Golang packages which can be used within application as a programmatic domain model to interact with Stellar network.
+
+**Why Use It:**
+
+- You want rapid development of applications in Golang which can acquire and parse ledger meta data and ledger entries from Stellar network.
+- You want an intuitive, compile-time, type-safe application developer experience.
+- You want to programmatically access History Archives to retrieve ledger entries.
+
+## [Processors](/docs/data/indexers/build-your-own/processors)
+
+A suite of Go packages that help you parse Stellar blockchain data.
diff --git a/docs/data/indexers/build-your-own/ingest-sdk/README.mdx b/docs/data/indexers/build-your-own/ingest-sdk/README.mdx
deleted file mode 100644
index d1486e0f2..000000000
--- a/docs/data/indexers/build-your-own/ingest-sdk/README.mdx
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: Ingest SDK
-sidebar_position: 0
----
-
-## What is the Ingest SDK?
-
-The SDK is composed of several published Golang packages under `github.com/stellar/go-stellar-sdk` for acquiring and parsing data from the Stellar network. It provides language level bindings which convert the [binary XDR encoded](../../../../learn/fundamentals/data-format/xdr.mdx) streams emitted from the network into fluent programmatic data model bindings.
-
-## Why use the Ingest SDK?
-
-Applications can leverage the SDK to rapidly develop ingestion pipelines capable of acquiring real-time or historical Stellar network data and deriving custom data models. The SDK enables applications to traverse the hierarchal data structures of the network: [history archives](../../../../validators/admin-guide/environment-preparation.mdx#history-archives), [ledgers](../../../../learn/fundamentals/stellar-data-structures/ledgers.mdx), transactions, operations, ledger state changes, and events.
-
-Use the SDK for an intuitive, compile-time, type-safe developer experience to work with the main types of network data:
-
-### Ledger Entries
-
-Obtain the final state of [ledger entries](../../../../learn/fundamentals/stellar-data-structures/ledgers.mdx) on the network at close of any recent or historically aged checkpoint ledger sequence. A Checkpoint ledger occurs once every 64 ledgers, during which the network will publish this data to [history archives](../../../../validators/admin-guide/environment-preparation.mdx#history-archives) in the format of compressed files which contain lists of `BucketEntry`, wherein each contains one `LedgerEntry` and the `LedgerKey`.
-
-Ledger entries are cryptographically signed as part of each ledger and therefore represent the trusted, cumulative state at a point in time for [assets](../../../../learn/fundamentals/stellar-data-structures/assets.mdx) related to an [account](../../../../learn/fundamentals/stellar-data-structures/accounts.mdx) or [contract](../../../../learn/fundamentals/contract-development/storage/persisting-data.mdx). Examples of asset types:
-
-- trustlines which hold token balances
-- offers which hold bid and asks on the [Stellar DEX](../../../../learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx#sdex)
-- contract data which holds key/value stores for contracts
-
-### Ledger Metadata
-
-Gain access to all transactions and their nested operations which were included in each closed ledger. It also contains the changes(pre/post) for each ledger entry when it is changed due to transaction activity and all [Soroban contract events](../../../../learn/fundamentals/stellar-data-structures/events.mdx) emitted as a result of [contract](../../../../learn/fundamentals/stellar-data-structures/contracts.mdx) invocations during transaction execution. It is effectively a commit log for ledger entries.
-
-Use the metadata to detect incremental changes in ledger entries that occur as a result of each transaction. These changes and the events emitted after each transaction represent valuabe data models specific to a point in time(expressed as a ledger sequence on the network), some real world examples:
-
-- a payment in the form of a token transfer between accounts
-- an offer is placed to trade one token for another token at a given price on the dex
-- token transfers between accounts and contracts
-
-The SDK provides packages which clients can use to acquire and parse the metadata in streaming data format, with readers and callback functions.
-
-The streams of ledger metadata can be sourced in unbounded fashion as ongoing real-time ledgers close on the Stellar network, and also in a historical replay mode with a bounded range of past ledger sequences.
diff --git a/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/README.mdx b/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/README.mdx
deleted file mode 100644
index 18f2117e9..000000000
--- a/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/README.mdx
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: Developer Guide
-sidebar_position: 0
-sidebar_key: ingest-sdk-developer-guide
----
-
-The Stellar [ingest SDK](https://github.com/stellar/go-stellar-sdk/tree/main/ingest) is a set of packages for retrieving and processing ledger metadata from the Stellar network. Developers can use this SDK to build custom ingestion engines.
-
-This guide explains how to set up, configure, and use ingest SDK effectively.
diff --git a/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/architecture.mdx b/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/architecture.mdx
index c4187b390..939a98a40 100644
--- a/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/architecture.mdx
+++ b/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/architecture.mdx
@@ -1,6 +1,6 @@
 ---
 title: Architecture
-sidebar_position: 0
+description: "Ingest SDK Structure"
 ---
 
 ![](/assets/ingest-sdk/architecture.png)
@@ -9,6 +9,6 @@ sidebar_position: 0
 
 Ingest SDK is organized into three main components:
 
-1. **[Ledger Backends](./ledgerbackends/README.mdx)**: Used to stream ledgers from the Stellar network. `https://github.com/stellar/go-stellar-sdk/tree/main/ingest/ledgerbackend`
-2. **[Ledger Readers](./ledgerreaders.mdx)** : Iterators to extract individual changes or transactions from a ledger. `https://github.com/stellar/go-stellar-sdk/tree/main/ingest`
+1. **[Ledger Backends](/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends)**: Used to stream ledgers from the Stellar network. `https://github.com/stellar/go-stellar-sdk/tree/main/ingest/ledgerbackend`
+2. **[Ledger Readers](./ledgerreaders)** : Iterators to extract individual changes or transactions from a ledger. `https://github.com/stellar/go-stellar-sdk/tree/main/ingest`
 3. **[Ledger Processors](https://github.com/stellar/go-stellar-sdk/tree/main/processors)** : Functions to process individual changes or transactions and extract meaningful data such as accounts, offers, claimable balance, etc. They are used in conjunction with `Ledger Readers` to interpret and transform ledger data.
diff --git a/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/index.mdx b/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/index.mdx
new file mode 100644
index 000000000..eb3fd7f51
--- /dev/null
+++ b/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/index.mdx
@@ -0,0 +1,7 @@
+---
+title: Developer Guide
+description: "The Stellar ingest SDK is a set of packages for retrieving and processing ledger metadata from the Stellar network. Developers can use this SDK to build custom ingestion engines."
+sidebar_key: ingest-sdk-developer-guide
+---
+
+This guide explains how to set up, configure, and use ingest SDK effectively.
diff --git a/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/README.mdx b/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/README.mdx
deleted file mode 100644
index a6054d127..000000000
--- a/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/README.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: Ledger Backends
-sidebar_position: 10
----
-
-A ledger backend is a source of Stellar network ledger data. The ingest SDK supports two primary ledger backends, both implementing the [ledgerbackend](https://github.com/stellar/go-stellar-sdk/blob/main/ingest/ledgerbackend/ledger_backend.go) interface. This interface always returns ledger data as [LedgerCloseMeta](#ledgerclosemeta-structure), which is XDR-encoded ledger metadata object.
-
-1. **[Captive Core](./captivecore.mdx)** – Invokes the `stellar-core` binary as a subprocess which connects to the live Stellar network and fetches network data (i.e., ledgers).
-2. **[BufferedStorageBackend](./bufferedstoragebackend.mdx)** – Retrieves ledger metadata from cloud storage.
-3. **[RPCLedgerBackend](./rpcledgerbackend.mdx)** – Retrieves ledger metadata from an RPC server.
-
-Each backend has its own setup and configuration requirements, which are covered in the following sections.
-
-### LedgerCloseMeta Structure
-
-`xdr.LedgerCloseMeta` captures a detailed record of all state changes during the closing of a Stellar ledger. It includes:
-
-- `LedgerHeader` – Metadata about the ledger, including:
-  - Ledger sequence number
-  - Previous ledger hash
-  - Close time
-  - Bucketlist hash
-
-- `TxSet` – The set of transactions included in the ledger.
-
-- `TxProcessing` – Execution results of each transaction, including:
-  - Success or failure of operations within transactions
-  - `OperationMeta`, which tracks `LedgerEntryChanges` caused by transactions
-
-- `UpgradesProcessing` – Any protocol upgrades applied in this ledger.
-
-- `ScpInfo` – Details of the consensus process that finalized this ledger.
-
-- `EvictedLedgerKeys` – Keys of ledger entries removed due to expiration.
diff --git a/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/bufferedstoragebackend.mdx b/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/bufferedstoragebackend.mdx
index 3990ad44c..fb7747d9f 100644
--- a/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/bufferedstoragebackend.mdx
+++ b/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/bufferedstoragebackend.mdx
@@ -1,9 +1,9 @@
 ---
 title: BufferedStorageBackend
-sidebar_position: 5
+description: "BufferedStorageBackend is a ledger backend in Stellar ingest SDK that retrieves ledger metadata from a cloud-based data lake, typically populated by Galexie. While Galexie currently supports only GCS, BufferedStorageBackend is designed to work with any datastore that implements the datastore interface. It returns ledger metadata in XDR format."
 ---
 
-[BufferedStorageBackend](https://github.com/stellar/go-stellar-sdk/blob/main/ingest/ledgerbackend/buffered_storage_backend.go) is a ledger backend in Stellar [ingest SDK](https://github.com/stellar/go-stellar-sdk/tree/main/ingest) that retrieves ledger metadata from a cloud-based data lake, typically populated by [Galexie](../../../galexie/README.mdx). While Galexie currently supports only [GCS](../../../galexie/admin_guide/configuring.mdx), `BufferedStorageBackend` is designed to work with any datastore that implements the [datastore interface](https://github.com/stellar/go-stellar-sdk/blob/main/support/datastore/datastore.go). It returns ledger metadata in [XDR](../../../../../../learn/fundamentals/data-format/xdr.mdx) format.
+[BufferedStorageBackend](https://github.com/stellar/go-stellar-sdk/blob/main/ingest/ledgerbackend/buffered_storage_backend.go) is a ledger backend in Stellar [ingest SDK](https://github.com/stellar/go-stellar-sdk/tree/main/ingest) that retrieves ledger metadata from a cloud-based data lake, typically populated by [Galexie](/docs/data/indexers/build-your-own/galexie). While Galexie currently supports only [GCS](../../../galexie/admin_guide/configuring), `BufferedStorageBackend` is designed to work with any datastore that implements the [datastore interface](https://github.com/stellar/go-stellar-sdk/blob/main/support/datastore/datastore.go). It returns ledger metadata in [XDR](../../../../../../learn/fundamentals/data-format/xdr) format.
 
 ![](/assets/ingest-sdk/bufferedstoragebackend_architecture.png)
 
@@ -16,11 +16,11 @@ sidebar_position: 5
 
 ## Prerequisites
 
-### Installation & Setup
+### Installation & Setup {#installation--setup}
 
-- Run Galexie to export ledger data to GCS cloud storage. Follow the [Galexie admin guide](../../../galexie/README.mdx) for instructions on running Galexie.
+- Run Galexie to export ledger data to GCS cloud storage. Follow the [Galexie admin guide](/docs/data/indexers/build-your-own/galexie) for instructions on running Galexie.
 
-- For purposes of the example code, ensure access to a data lake populated by Galexie, configured as a GCS bucket. For instructions on creating a data lake, refer to the [Galexie admin guide](../../../galexie/README.mdx).
+- For purposes of the example code, ensure access to a data lake populated by Galexie, configured as a GCS bucket. For instructions on creating a data lake, refer to the [Galexie admin guide](/docs/data/indexers/build-your-own/galexie).
 
 ## Configuration
 
@@ -163,4 +163,4 @@ func main() {
 }
 ```
 
-For real-time streaming of new ledgers using `BufferedStorageBackend`, refer to the [Ingestion Pipeline Code](../../../../../../build/apps/ingest-sdk/ingestion-pipeline-code.mdx).
+For real-time streaming of new ledgers using `BufferedStorageBackend`, refer to the [Ingestion Pipeline Code](../../../../../../build/apps/ingest-sdk/ingestion-pipeline-code).
diff --git a/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/captivecore.mdx b/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/captivecore.mdx
index 812bb357d..f14a50314 100644
--- a/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/captivecore.mdx
+++ b/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/captivecore.mdx
@@ -1,19 +1,19 @@
 ---
 title: Captive Core
-sidebar_position: 0
+description: "Captive Core invokes the stellar-core binary as a subprocess to stream ledgers from the Stellar network."
 ---
 
 Captive Core invokes the `stellar-core` binary as a subprocess to stream ledgers from the Stellar network. It can be used to stream a ledger range from the past or to stream new ledgers whenever they are confirmed by the network.
 
 ## Prerequisites
 
-Using captive Core requires stellar-core binary to be [installed](../../../../../../validators/admin-guide/installation.mdx) first.
+Using captive Core requires stellar-core binary to be [installed](../../../../../../validators/admin-guide/installation) first.
 
 ### Installation
 
 1. Install Stellar Core:
-   - Option 1: Build from source by following the [Installation Guide](../../../../../../validators/admin-guide/installation.mdx#installing-from-source)
-   - Option 2: Install via a package manager by referring to the [Package-based Installation Guide](../../../../../../validators/admin-guide/installation.mdx#package-based-installation)
+   - Option 1: Build from source by following the [Installation Guide](../../../../../../validators/admin-guide/installation#installing-from-source)
+   - Option 2: Install via a package manager by referring to the [Package-based Installation Guide](../../../../../../validators/admin-guide/installation#package-based-installation)
 
 2. Verify installation:
 
@@ -68,4 +68,4 @@ if err != nil {
 }
 ```
 
-The `captiveStellarCoreBackend` can now be used to retrieve ledger data within a specified range. For detailed usage, refer to the [code samples](../../examples/README.mdx).
+The `captiveStellarCoreBackend` can now be used to retrieve ledger data within a specified range. For detailed usage, refer to the [code samples](/docs/data/indexers/build-your-own/ingest-sdk/examples).
diff --git a/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/index.mdx b/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/index.mdx
new file mode 100644
index 000000000..e6391030a
--- /dev/null
+++ b/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/index.mdx
@@ -0,0 +1,32 @@
+---
+title: Ledger Backends
+description: "A ledger backend is a source of Stellar network ledger data. The ingest SDK supports two primary ledger backends, both implementing the ledgerbackend interface. This interface always returns ledger data as LedgerCloseMeta, which is XDR-encoded ledger metadata object."
+---
+
+1. **[Captive Core](/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/captivecore)** – Invokes the `stellar-core` binary as a subprocess which connects to the live Stellar network and fetches network data (i.e., ledgers).
+2. **[BufferedStorageBackend](/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/bufferedstoragebackend)** – Retrieves ledger metadata from cloud storage.
+3. **[RPCLedgerBackend](/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/rpcledgerbackend)** – Retrieves ledger metadata from an RPC server.
+
+Each backend has its own setup and configuration requirements, which are covered in the following sections.
+
+### LedgerCloseMeta Structure
+
+`xdr.LedgerCloseMeta` captures a detailed record of all state changes during the closing of a Stellar ledger. It includes:
+
+- `LedgerHeader` – Metadata about the ledger, including:
+  - Ledger sequence number
+  - Previous ledger hash
+  - Close time
+  - Bucketlist hash
+
+- `TxSet` – The set of transactions included in the ledger.
+
+- `TxProcessing` – Execution results of each transaction, including:
+  - Success or failure of operations within transactions
+  - `OperationMeta`, which tracks `LedgerEntryChanges` caused by transactions
+
+- `UpgradesProcessing` – Any protocol upgrades applied in this ledger.
+
+- `ScpInfo` – Details of the consensus process that finalized this ledger.
+
+- `EvictedLedgerKeys` – Keys of ledger entries removed due to expiration.
diff --git a/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/rpcledgerbackend.mdx b/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/rpcledgerbackend.mdx
index eefaf812b..938bd9d22 100644
--- a/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/rpcledgerbackend.mdx
+++ b/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/rpcledgerbackend.mdx
@@ -1,6 +1,6 @@
 ---
 title: RPC Ledger Backend
-sidebar_position: 10
+description: "The RPCLedgerBackend is a LedgerBackend implementation in Stellar Ingest SDK which uses an RPC Server as the backing source of ledger meta data."
 ---
 
 The [RPCLedgerBackend](https://github.com/stellar/go-stellar-sdk/blob/main/ingest/ledgerbackend/rpc_backend.go) is a [LedgerBackend](https://github.com/stellar/go-stellar-sdk/blob/main/ingest/ledgerbackend/ledger_backend.go) implementation in Stellar [Ingest SDK](https://github.com/stellar/go-stellar-sdk/tree/main/ingest) which uses an RPC Server as the backing source of ledger meta data.
@@ -10,7 +10,7 @@ Applications can use this ledger backend in order to obtain ledger meta data fro
 Usage of the RPCLedgerBackend implies having awareness of the retention window and data lake settings on the remote RPC server as these aspects determine the range of ledgers which are accessible through the RPCLedgerBackend.
 
 - `HISTORY_RETENTION_WINDOW` - This is a setting on the RPC server which determines the range of ledgers retained by the RPC in a sliding window from latest on Stellar network. The default is to retain the latest 7 days worth of ledger data from the Stellar network.
-- [Data Lake Integration](../../../../../apis/rpc/admin-guide/data-lake-integration.mdx) - If the RPC has the Data Lake integration enabled then the range of ledgers available will be a minimum of RPC's Retention Window and extends further back in history out to the larger range provided by the data lake.
+- [Data Lake Integration](../../../../../apis/rpc/admin-guide/data-lake-integration) - If the RPC has the Data Lake integration enabled then the range of ledgers available will be a minimum of RPC's Retention Window and extends further back in history out to the larger range provided by the data lake.
 
 ## Example SDK Usage
 
diff --git a/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerreaders.mdx b/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerreaders.mdx
index fe6c7a3da..9e5525d69 100644
--- a/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerreaders.mdx
+++ b/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerreaders.mdx
@@ -1,6 +1,6 @@
 ---
 title: Ledger Readers
-sidebar_position: 15
+description: "These readers are designed to extract data from the Stellar ledger in a structured way and enables iterating over ledger changes."
 ---
 
 These readers are designed to extract data from the Stellar ledger in a structured way and enables iterating over ledger changes.
diff --git a/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/prerequisites.mdx b/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/prerequisites.mdx
index 7190a0d42..92b9e67c9 100644
--- a/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/prerequisites.mdx
+++ b/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/prerequisites.mdx
@@ -1,6 +1,6 @@
 ---
 title: Prerequisites
-sidebar_position: 5
+description: "To build using ingest SDK, you need."
 ---
 
 To build using ingest SDK, you need:
diff --git a/docs/data/indexers/build-your-own/ingest-sdk/examples/README.mdx b/docs/data/indexers/build-your-own/ingest-sdk/examples/README.mdx
deleted file mode 100644
index da69e59cc..000000000
--- a/docs/data/indexers/build-your-own/ingest-sdk/examples/README.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: Example Usages
-sidebar_position: 10
-sidebar_key: ingest-sdk-example-usages
----
-
-This section showcases real-world use cases of the Ingest SDK, focusing on key components like `ingest.LedgerTransaction`, `ingest.LedgerChange`, `ingest.LedgerTransactionReader`, and `ingest.ChangeReader`.
-
-These examples take a Stellar Ledger (`xdr.LedgerCloseMeta`) or a ledger sequence range (start-end) as input. Each of the examples listed here is complete, and can be compiled and run as-is in your IDE/local dev.
-
-## Prerequisites
-
-Some of the examples listed here might invoke the `stellar-core` binary. Refer to the "admin guide" for more details on how to compile `stellar-core` for your platform.
-
-The [Stellar Ingest SDK](https://github.com/stellar/go-stellar-sdk) is a go module and includes several packages in addition to the ingest SDK. You will need to include the module in your go project `go.mod`.
-
-```bash
-go get github.com/stellar/go-stellar-sdk@latest
-go mod tidy
-```
diff --git a/docs/data/indexers/build-your-own/ingest-sdk/examples/changes.mdx b/docs/data/indexers/build-your-own/ingest-sdk/examples/changes.mdx
index 5de238f53..a54730bea 100644
--- a/docs/data/indexers/build-your-own/ingest-sdk/examples/changes.mdx
+++ b/docs/data/indexers/build-your-own/ingest-sdk/examples/changes.mdx
@@ -1,6 +1,6 @@
 ---
 title: Retrieve ledger entry changes within a range
-sidebar_position: 30
+description: "This code invokes the stellar-core binary (as configured in ledgerbackend.CaptiveCoreConfig) to replay ledgers from a given ledger range."
 ---
 
 This code invokes the `stellar-core` binary (as configured in `ledgerbackend.CaptiveCoreConfig`) to replay ledgers from a given ledger range. It uses the `ingest.LedgerChangeReader` to read changes from each ledger (`xdr.LedgerCloseMeta`) and categorizes the changes based on whether they represent created, updated, or deleted ledger entries. The `ingest.Change` structure is used to capture individual changes, and the code tracks various types of changes such as those related to fees, transactions, or operations.
diff --git a/docs/data/indexers/build-your-own/ingest-sdk/examples/index.mdx b/docs/data/indexers/build-your-own/ingest-sdk/examples/index.mdx
new file mode 100644
index 000000000..8b1657336
--- /dev/null
+++ b/docs/data/indexers/build-your-own/ingest-sdk/examples/index.mdx
@@ -0,0 +1,18 @@
+---
+title: Example Usages
+description: "This section showcases real-world use cases of the Ingest SDK, focusing on key components like ingest.LedgerTransaction, ingest.LedgerChange, ingest.LedgerTransactionReader, and ingest.ChangeReader."
+sidebar_key: ingest-sdk-example-usages
+---
+
+These examples take a Stellar Ledger (`xdr.LedgerCloseMeta`) or a ledger sequence range (start-end) as input. Each of the examples listed here is complete, and can be compiled and run as-is in your IDE/local dev.
+
+## Prerequisites
+
+Some of the examples listed here might invoke the `stellar-core` binary. Refer to the "admin guide" for more details on how to compile `stellar-core` for your platform.
+
+The [Stellar Ingest SDK](https://github.com/stellar/go-stellar-sdk) is a go module and includes several packages in addition to the ingest SDK. You will need to include the module in your go project `go.mod`.
+
+```bash
+go get github.com/stellar/go-stellar-sdk@latest
+go mod tidy
+```
diff --git a/docs/data/indexers/build-your-own/ingest-sdk/examples/ledger_entry_statistics.mdx b/docs/data/indexers/build-your-own/ingest-sdk/examples/ledger_entry_statistics.mdx
index 835bc80ed..41ea45eb5 100644
--- a/docs/data/indexers/build-your-own/ingest-sdk/examples/ledger_entry_statistics.mdx
+++ b/docs/data/indexers/build-your-own/ingest-sdk/examples/ledger_entry_statistics.mdx
@@ -1,6 +1,6 @@
 ---
 title: Get count of each ledger entry type from history archive
-sidebar_position: 20
+description: "This example connects to the Stellar History Archive and initializes a checkpoint change reader with ingest.NewCheckpointChangeReader to read ledger entry..."
 ---
 
 This example connects to the Stellar History Archive and initializes a checkpoint change reader with `ingest.NewCheckpointChangeReader` to read ledger entry changes from a history archive snapshot occurring at a given checkpoint ledger. It iterates over the ledger changes, processing different entry types such as `Account`, `ClaimableBalance`, `Trustline`, and `Offer`, using the `ingest.Change` structure. The code tracks statistics in an `entriesInfo` struct, counting the total entries and specific types.
diff --git a/docs/data/indexers/build-your-own/ingest-sdk/examples/transaction_statistics.mdx b/docs/data/indexers/build-your-own/ingest-sdk/examples/transaction_statistics.mdx
index 6d2959978..bdef9e1dd 100644
--- a/docs/data/indexers/build-your-own/ingest-sdk/examples/transaction_statistics.mdx
+++ b/docs/data/indexers/build-your-own/ingest-sdk/examples/transaction_statistics.mdx
@@ -1,6 +1,6 @@
 ---
 title: Get successful/failed transactions from a ledger range
-sidebar_position: 10
+description: "This example illustrates how to run and connect with a Stellar network watcher node, referred to as 'captive core' using the ledgerbackend.CaptiveStellarCore."
 ---
 
 This example illustrates how to run and connect with a Stellar network watcher node, referred to as 'captive core' using the `ledgerbackend.CaptiveStellarCore`. It then requests a historical bounded range of ledgers to be replayed. The captive core instance will emit a stream of ledger metadata (`xdr.LedgerCloseMeta`) which contains the transactions per ledger in the range. It reads each ledger's transactions using the `ingest.LedgerTransactionReader`, categorizes them as successful or failed, and tracks the operations associated with each transaction.
diff --git a/docs/data/indexers/build-your-own/ingest-sdk/index.mdx b/docs/data/indexers/build-your-own/ingest-sdk/index.mdx
new file mode 100644
index 000000000..c35d4c650
--- /dev/null
+++ b/docs/data/indexers/build-your-own/ingest-sdk/index.mdx
@@ -0,0 +1,38 @@
+---
+title: Ingest SDK
+description: "The SDK is composed of several published Golang packages under github.com/stellar/go-stellar-sdk for acquiring and parsing data from the Stellar network."
+---
+
+## What is the Ingest SDK?
+
+The SDK is composed of several published Golang packages under `github.com/stellar/go-stellar-sdk` for acquiring and parsing data from the Stellar network. It provides language level bindings which convert the [binary XDR encoded](/docs/learn/fundamentals/data-format/xdr) streams emitted from the network into fluent programmatic data model bindings.
+
+## Why use the Ingest SDK?
+
+Applications can leverage the SDK to rapidly develop ingestion pipelines capable of acquiring real-time or historical Stellar network data and deriving custom data models. The SDK enables applications to traverse the hierarchal data structures of the network: [history archives](/docs/validators/admin-guide/environment-preparation#history-archives), [ledgers](/docs/learn/fundamentals/stellar-data-structures/ledgers), transactions, operations, ledger state changes, and events.
+
+Use the SDK for an intuitive, compile-time, type-safe developer experience to work with the main types of network data:
+
+### Ledger Entries
+
+Obtain the final state of [ledger entries](/docs/learn/fundamentals/stellar-data-structures/ledgers) on the network at close of any recent or historically aged checkpoint ledger sequence. A Checkpoint ledger occurs once every 64 ledgers, during which the network will publish this data to [history archives](/docs/validators/admin-guide/environment-preparation#history-archives) in the format of compressed files which contain lists of `BucketEntry`, wherein each contains one `LedgerEntry` and the `LedgerKey`.
+
+Ledger entries are cryptographically signed as part of each ledger and therefore represent the trusted, cumulative state at a point in time for [assets](/docs/learn/fundamentals/stellar-data-structures/assets) related to an [account](/docs/learn/fundamentals/stellar-data-structures/accounts) or [contract](/docs/learn/fundamentals/contract-development/storage/persisting-data). Examples of asset types:
+
+- trustlines which hold token balances
+- offers which hold bid and asks on the [Stellar DEX](/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools#sdex)
+- contract data which holds key/value stores for contracts
+
+### Ledger Metadata
+
+Gain access to all transactions and their nested operations which were included in each closed ledger. It also contains the changes(pre/post) for each ledger entry when it is changed due to transaction activity and all [Soroban contract events](/docs/learn/fundamentals/stellar-data-structures/events) emitted as a result of [contract](/docs/learn/fundamentals/stellar-data-structures/contracts) invocations during transaction execution. It is effectively a commit log for ledger entries.
+
+Use the metadata to detect incremental changes in ledger entries that occur as a result of each transaction. These changes and the events emitted after each transaction represent valuabe data models specific to a point in time(expressed as a ledger sequence on the network), some real world examples:
+
+- a payment in the form of a token transfer between accounts
+- an offer is placed to trade one token for another token at a given price on the dex
+- token transfers between accounts and contracts
+
+The SDK provides packages which clients can use to acquire and parse the metadata in streaming data format, with readers and callback functions.
+
+The streams of ledger metadata can be sourced in unbounded fashion as ongoing real-time ledgers close on the Stellar network, and also in a historical replay mode with a bounded range of past ledger sequences.
diff --git a/docs/data/indexers/build-your-own/processors/README.mdx b/docs/data/indexers/build-your-own/processors/README.mdx
deleted file mode 100644
index 1f6ef8fc8..000000000
--- a/docs/data/indexers/build-your-own/processors/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Processors
-sidebar_position: 0
----
-
-Learn more about the processors library in the [Stellar Go SDK](https://github.com/stellar/go)
-
-## [Token Transfer Processor](./token-transfer-processor/README.mdx)
-
-Track all asset movement on the Stellar blockchain
diff --git a/docs/data/indexers/build-your-own/processors/index.mdx b/docs/data/indexers/build-your-own/processors/index.mdx
new file mode 100644
index 000000000..0aa3b94d5
--- /dev/null
+++ b/docs/data/indexers/build-your-own/processors/index.mdx
@@ -0,0 +1,8 @@
+---
+title: Processors
+description: "Learn more about the processors library in the Stellar Go SDK."
+---
+
+## [Token Transfer Processor](/docs/data/indexers/build-your-own/processors/token-transfer-processor)
+
+Track all asset movement on the Stellar blockchain
diff --git a/docs/data/indexers/build-your-own/processors/token-transfer-processor/README.mdx b/docs/data/indexers/build-your-own/processors/token-transfer-processor/README.mdx
deleted file mode 100644
index ad075bb1c..000000000
--- a/docs/data/indexers/build-your-own/processors/token-transfer-processor/README.mdx
+++ /dev/null
@@ -1,231 +0,0 @@
----
-title: Token Transfer Processor
-sidebar_position: 0
----
-
-## Overview
-
-The Token Transfer Processor (TTP) is a [Go package](https://github.com/stellar/go-stellar-sdk/tree/main/processors/token_transfer) which uses the [ingest-sdk](../../ingest-sdk/README.mdx) to parse Stellar network transaction data and derive token transfer events. Before TTP, developers had to manually parse complex ledger data, operation results, and ledger entry changes to understand when and how value moved between accounts, contracts, and other entities on the network.
-
-Prior to [CAP-67 Unified Events](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md), tracking token transfers required significant custom logic to handle different operation types, interpret ledger changes, and reconstruct the flow of assets. CAP-67 introduced a standardized event format that simplifies this process by providing a unified way to represent all token transfer activities.
-
-TTP serves as a facade to CAP-67, automatically generating these standardized events from Stellar ledger data. It can operate in two modes:
-
-- **Standalone mode**: TTP analyzes operations, operation results, and ledger entry changes to derive transfer events
-- **Unified events mode**: TTP reads directly from CAP-67 compliant unified events when available in the ledger data
-
-For more details on operational modes, see the [Modes of Operation](#modes-of-operation) section.
-
-## Key Features
-
-- Captures token movements resulting from:
-  - Simple payments
-  - Path payments
-  - DEX operations
-  - Account merges
-  - Trustline revocations
-  - Claimable balance operations
-  - Liquidity pool operations
-  - Clawback operations
-  - Stellar Asset Contract events
-  - [SEP-41](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0041.md) compliant token events
-
-- Generates CAP-67 standardized token events:
-  - Transfer: Movement of tokens between accounts
-  - Mint: Creation of new tokens
-  - Burn: Destruction of tokens
-  - Clawback: Asset issuer reclaiming tokens
-  - Fee: Network fees paid
-
-- Handles muxed account information in compliance with CAP-67 multiplexing support
-
-- Reconciliation for older protocol versions to ensure consistency between operation changes and generated events
-
-## Events
-
-TTP generates events in Go bindings based on [protobuf definitions](https://github.com/stellar/go-stellar-sdk/blob/main/protos/processors/token_transfer/token_transfer_event.proto). The definitions codify an IDL for the standardized token transfer event models put forth in CAP-67. Each event contains metadata and type-specific information structured as follows:
-
-| Event Type | Description | Key Fields | When Generated |
-| --- | --- | --- | --- |
-| **Transfer** | Asset movement between two entities | `from`, `to`, `amount`, `asset`, `toMuxedInfo` | When assets move between accounts, contracts, or other entities |
-| **Mint** | Asset creation by the issuer | `to`, `amount`, `asset`, `toMuxedInfo` | When an issuer creates new tokens or when assets are sent from the issuer |
-| **Burn** | Asset destruction to the issuer | `from`, `amount`, `asset` | When assets are returned to the issuer for destruction |
-| **Clawback** | Forced asset recovery by issuer | `from`, `amount`, `asset` | When an issuer uses clawback operations to recover assets |
-| **Fee** | Network fee payment or refund | `account`, `amount` | For all transaction fees and Soroban fee refunds |
-
-### Fee Events
-
-TTP generates fee events to track network fees associated with transaction processing. Understanding the different types of fee events is important for accurate accounting:
-
-Fee events are generated for all transactions, whether they succeed or fail. These represent the network fees that accounts pay to submit transactions to the Stellar network.
-
-- **Present for**: Every transaction
-- **Amount representation**: Positive values indicating fees paid
-- **Asset**: Always XLM (Stellar's native asset)
-
-Fee refund events are generated only for Soroban (smart contract) transactions and only when there are unused resources that qualify for a refund.
-
-- **Present for**: Soroban transactions with unused resource fees
-- **Amount representation**: Negative values to indicate money being returned
-- **Asset**: Always XLM
-- **Event type**: Uses the same `Fee` event type, distinguished by the negative amount
-
-:::note
-
-TTP uses negative amounts in fee events to represent refunds rather than creating a separate refund event type. This approach maintains consistency with the CAP-67 specification while clearly indicating the direction of the fee transaction.
-
-:::
-
-### Event Metadata
-
-Every token transfer event includes comprehensive metadata to provide context about when and where the event occurred:
-
-| Field | Type | Description |
-| --- | --- | --- |
-| `ledgerSequence` | `uint32` | The ledger number where this event occurred. This provides chronological ordering across the entire network. |
-| `txHash` | `string` | The transaction hash that generated this event. This allows you to trace events back to their originating transaction. |
-| `operationIndex` | `uint32*` | The one-based index of the operation within the transaction that caused this event as defined by [SEP-35](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0035.md). This field is `nil` for transaction-level events like fees. |
-| `contractAddress` | `string` | The contract address associated with the asset/token being moved. For classic operations or Stellar Asset Contract Events, this field will be the contractId of the underlying classic asset. This enables integration with Stellar's smart contract ecosystem. |
-
-:::note
-
-The `toMuxedInfo` field is included in Transfer and Mint events when the destination uses a muxed account (M-address) and/or when transaction-level memo is set (in the case of non-smart contract transactions), providing additional routing information.
-
-:::
-
-Please refer to [this](../../../../../build/guides/transactions/pooled-accounts-muxed-accounts-memos.mdx) section for more information on muxed account/memo usage.
-
-Please refer to [this](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md#prohibit-the-transaction-memo-and-muxed-source-accounts-from-being-set-on-soroban-transactions) section in CAP-67 to learn more on what to expect in the `toMuxedInfo` field.
-
-:::note
-
-The `contractAddress` field is particularly important for DeFi applications as it provides the bridge between classic Stellar assets and their smart contract representations.
-
-For events from classic transactions and SAC events from smart contract transactions, the `contractAddress` field reflects the SAC address for the asset.
-
-:::
-
-## Go API Overview
-
-TTP provides three distinct functions which derive events from different levels of granularity from the underlying Stellar network data.
-
-### EventsFromLedger
-
-```go
-func (p *EventsProcessor) EventsFromLedger(lcm xdr.LedgerCloseMeta) ([]*TokenTransferEvent, error)
-```
-
-This function processes an entire ledger and returns a flattened list of `TokenTransferEvent` objects. The order of events in the returned slice represents the chronological ordering of debits, credits, and fees as they were applied to accounts, trustlines, and contracts during ledger processing.
-
-The chronological ordering is critical for applications that need to maintain accurate balance tracking or audit trails. For detailed information about how events are ordered, see the [Event Ordering](#event-ordering) section.
-
-### EventsFromTransaction
-
-```go
-func (p *EventsProcessor) EventsFromTransaction(tx ingest.LedgerTransaction) (TransactionEvents, error)
-```
-
-This function processes a single transaction and returns a `TransactionEvents` structure that separates fee-related events from operation-related events:
-
-- `FeeEvents`: Contains fee charges and refunds associated with the transaction
-- `OperationEvents`: Contains all events generated by the transaction's operations
-
-This separation is useful when you need to handle fees differently from operational transfers, such as for accounting or analytics purposes.
-
-### EventsFromOperation
-
-```go
-func (p *EventsProcessor) EventsFromOperation(
-	tx ingest.LedgerTransaction,
-	opIndex uint32,
-	op xdr.Operation,
-	opResult xdr.OperationResult
-	) ([]*TokenTransferEvent, error)
-```
-
-This function processes a single operation within a transaction and returns a list of events generated by that specific operation. This granular approach is useful for applications that need to analyze or react to specific types of operations.
-
-## Modes of Operation
-
-TTP can operate in two distinct modes depending on how the ledger data was generated and what information is available.
-
-### Default Mode (Recommended)
-
-In default mode, TTP analyzes three sources of information to derive token transfer events:
-
-- **Operations**: The operations submitted in transactions
-- **Operation Results**: The success/failure results of each operation
-- **Ledger Entry Changes**: The changes made to the ledger state
-
-This mode works with all Stellar ledgers regardless of how they were generated or which stellar-core version produced them. It is the safest and most compatible option.
-
-```go
-// Default mode - works with all ledgers
-processor := token_transfer.NewEventsProcessor(networkPassphrase)
-```
-
-### Unified Events Stream Mode
-
-In unified events stream mode, TTP reads token transfer events directly from the unified events stream embedded in the ledger data. This mode is more efficient but requires ledgers that were generated with specific stellar-core configuration flags.
-
-```go
-// Unified events mode - only for specially configured ledgers
-processor := token_transfer.NewEventsProcessorForUnifiedEvents(networkPassphrase)
-```
-
-Only use unified events stream mode if you are certain that your ledgers contain unified events. These ledgers must be generated by stellar-core with both `EMIT_CLASSIC_EVENTS=true` and `BACKFILL_STELLAR_ASSET_EVENTS=true` configuration flags enabled. TTP cannot dynamically determine whether a ledger contains unified events or not.
-
-:::caution
-
-If you configure TTP for unified events mode and then provide it ledgers without unified events, TTP will silently produce no events.
-
-:::
-
-**When in doubt, always use the default mode**, as it works reliably with all ledger types.
-
-## Event Ordering
-
-The order of events returned by TTP depends on the Stellar protocol version that was active when the ledger was created. This ordering is crucial for maintaining accurate chronological records of asset movements.
-
-### Pre-Protocol 23 Ordering
-
-Before Whisk, Protocol 23, events follow this chronological pattern:
-
-```
-All Fee Events (from all transactions)
-↓
-For each transaction in ledger:
-  - Operation Events (from all operations in the transaction)
-  - Fee Refund Event (if applicable, immediately after operation events)
-```
-
-In this ordering, fee refunds appear immediately after the operation events for each individual transaction.
-
-### Protocol 23+ Ordering
-
-Starting with Whisk, Protocol 23, events follow this chronological pattern:
-
-```
-All Fee Events (from all transactions)
-↓
-All Operation Events (from all transactions, maintaining transaction and operation order)
-↓
-All Fee Refund Events (from all transactions)
-```
-
-In this newer ordering, all fee refunds are grouped together at the end, after all transactions have been processed.
-
-:::note
-
-TTP automatically detects the protocol version and applies the correct ordering rules. You don't need to configure this manually, but understanding the ordering differences is important for applications that depend on event sequence.
-
-:::
-
-The chronological ordering ensures that when you process events in the order returned by TTP, you're following the exact sequence in which debits and credits were applied to accounts during ledger processing. This is essential for maintaining accurate balance calculations and audit trails.
-
-## References
-
-- [CAP-67: Unified Events](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md)
-- [SEP-41: Asset Token Contract Specification](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0041.md)
-- [CAP-38: Automated Market Makers](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0038.md)
-- [SEP-35: ID Scheme for Stellar Operations](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0035.md)
diff --git a/docs/data/indexers/build-your-own/processors/token-transfer-processor/examples/README.mdx b/docs/data/indexers/build-your-own/processors/token-transfer-processor/examples/README.mdx
deleted file mode 100644
index dabf22c30..000000000
--- a/docs/data/indexers/build-your-own/processors/token-transfer-processor/examples/README.mdx
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: Example Usages
-sidebar_position: 10
-sidebar_key: token-transfer-processor-example-usages
----
-
-This section contains examples of how Token Transfer Processor can be used in your application logic
-
-## Prerequisites
-
-You have an existing go module in current directory or create a new module locally for this example exercise.
-
-```bash
-go mod init example/ttp_processor
-```
-
-Include the Stellar Ingest SDK into your go application module which contains the Token Transfer Processor.
-
-```bash
-go get github.com/stellar/go-stellar-sdk@latest
-go mod tidy
-```
-
-## Helper Code
-
-This section contains some helper code that will be used in all the examples.
-
-```go
-package main
-
-import (
-	"context"
-	"fmt"
-
-	"github.com/stellar/go-stellar-sdk/ingest/ledgerbackend"
-	"github.com/stellar/go-stellar-sdk/processors/token_transfer"
-	"github.com/stellar/go-stellar-sdk/support/log"
-	"github.com/stellar/go-stellar-sdk/xdr"
-
-	"google.golang.org/protobuf/encoding/protojson"
-)
-
-func panicIf(err error) {
-	if err != nil {
-		panic(err)
-	}
-}
-
-// fetchLedgerFromRPC retrieves a ledger using RPCLedgerBackend
-func fetchLedgerFromRPC(ledgerSeq uint32) xdr.LedgerCloseMeta {
-	ctx := context.Background()
-
-	// Using a publicly hosted RPC instance
-	endpoint := "https://mainnet.sorobanrpc.com"
-
-	// Configure the RPC Ledger Backend
-	backend := ledgerbackend.NewRPCLedgerBackend(ledgerbackend.RPCLedgerBackendOptions{
-		RPCServerURL: endpoint,
-	})
-	defer backend.Close()
-
-	// Prepare an unbounded range starting from the latest ledger
-	if err := backend.PrepareRange(ctx, ledgerbackend.BoundedRange(ledgerSeq, ledgerSeq)); err != nil {
-		log.Fatalf("Failed to prepare range: %v", err)
-	}
-
-	ledger, err := backend.GetLedger(ctx, ledgerSeq)
-	panicIf(err)
-	return ledger
-}
-
-func printProtoEvent(event *token_transfer.TokenTransferEvent) {
-	jsonBytes, _ := protojson.MarshalOptions{
-		Multiline:         true,
-		EmitDefaultValues: true,
-		Indent:            "  ",
-	}.Marshal(event)
-	fmt.Printf("### Event Type : %v\n", event.GetEventType())
-	fmt.Println(string(jsonBytes))
-}
-```
diff --git a/docs/data/indexers/build-your-own/processors/token-transfer-processor/examples/event_stats.mdx b/docs/data/indexers/build-your-own/processors/token-transfer-processor/examples/event_stats.mdx
index 6765ef8ad..642df9829 100644
--- a/docs/data/indexers/build-your-own/processors/token-transfer-processor/examples/event_stats.mdx
+++ b/docs/data/indexers/build-your-own/processors/token-transfer-processor/examples/event_stats.mdx
@@ -1,6 +1,6 @@
 ---
 title: Retrieve token transfer events from a ledger
-sidebar_position: 10
+description: "This example fetches a specific Stellar ledger and uses the Token Transfer Processor to extract all token movement events from it."
 ---
 
 This example fetches a specific Stellar ledger and uses the Token Transfer Processor to extract all token movement events from it. The code processes each event, categorizes them by type (transfers, mints, burns, clawbacks, fees), and prints both the individual event details and summary statistics. This demonstrates the basic usage of EventsFromLedger() to analyze all asset activity within a single ledger.
diff --git a/docs/data/indexers/build-your-own/processors/token-transfer-processor/examples/filter_events.mdx b/docs/data/indexers/build-your-own/processors/token-transfer-processor/examples/filter_events.mdx
index e9b39041b..218a89d62 100644
--- a/docs/data/indexers/build-your-own/processors/token-transfer-processor/examples/filter_events.mdx
+++ b/docs/data/indexers/build-your-own/processors/token-transfer-processor/examples/filter_events.mdx
@@ -1,6 +1,6 @@
 ---
 title: Filter events from transaction
-sidebar_position: 20
+description: "This code demonstrates a practical implementation of event filtering using the Token Transfer Processor's EventsFromTransaction function."
 ---
 
 This code demonstrates a practical implementation of event filtering using the Token Transfer Processor's `EventsFromTransaction` function.
diff --git a/docs/data/indexers/build-your-own/processors/token-transfer-processor/examples/index.mdx b/docs/data/indexers/build-your-own/processors/token-transfer-processor/examples/index.mdx
new file mode 100644
index 000000000..c46b04b0d
--- /dev/null
+++ b/docs/data/indexers/build-your-own/processors/token-transfer-processor/examples/index.mdx
@@ -0,0 +1,79 @@
+---
+title: Example Usages
+description: "This section contains examples of how Token Transfer Processor can be used in your application logic."
+sidebar_key: token-transfer-processor-example-usages
+---
+
+## Prerequisites
+
+You have an existing go module in current directory or create a new module locally for this example exercise.
+
+```bash
+go mod init example/ttp_processor
+```
+
+Include the Stellar Ingest SDK into your go application module which contains the Token Transfer Processor.
+
+```bash
+go get github.com/stellar/go-stellar-sdk@latest
+go mod tidy
+```
+
+## Helper Code
+
+This section contains some helper code that will be used in all the examples.
+
+```go
+package main
+
+import (
+	"context"
+	"fmt"
+
+	"github.com/stellar/go-stellar-sdk/ingest/ledgerbackend"
+	"github.com/stellar/go-stellar-sdk/processors/token_transfer"
+	"github.com/stellar/go-stellar-sdk/support/log"
+	"github.com/stellar/go-stellar-sdk/xdr"
+
+	"google.golang.org/protobuf/encoding/protojson"
+)
+
+func panicIf(err error) {
+	if err != nil {
+		panic(err)
+	}
+}
+
+// fetchLedgerFromRPC retrieves a ledger using RPCLedgerBackend
+func fetchLedgerFromRPC(ledgerSeq uint32) xdr.LedgerCloseMeta {
+	ctx := context.Background()
+
+	// Using a publicly hosted RPC instance
+	endpoint := "https://mainnet.sorobanrpc.com"
+
+	// Configure the RPC Ledger Backend
+	backend := ledgerbackend.NewRPCLedgerBackend(ledgerbackend.RPCLedgerBackendOptions{
+		RPCServerURL: endpoint,
+	})
+	defer backend.Close()
+
+	// Prepare an unbounded range starting from the latest ledger
+	if err := backend.PrepareRange(ctx, ledgerbackend.BoundedRange(ledgerSeq, ledgerSeq)); err != nil {
+		log.Fatalf("Failed to prepare range: %v", err)
+	}
+
+	ledger, err := backend.GetLedger(ctx, ledgerSeq)
+	panicIf(err)
+	return ledger
+}
+
+func printProtoEvent(event *token_transfer.TokenTransferEvent) {
+	jsonBytes, _ := protojson.MarshalOptions{
+		Multiline:         true,
+		EmitDefaultValues: true,
+		Indent:            "  ",
+	}.Marshal(event)
+	fmt.Printf("### Event Type : %v\n", event.GetEventType())
+	fmt.Println(string(jsonBytes))
+}
+```
diff --git a/docs/data/indexers/build-your-own/processors/token-transfer-processor/index.mdx b/docs/data/indexers/build-your-own/processors/token-transfer-processor/index.mdx
new file mode 100644
index 000000000..274217b7e
--- /dev/null
+++ b/docs/data/indexers/build-your-own/processors/token-transfer-processor/index.mdx
@@ -0,0 +1,231 @@
+---
+title: Token Transfer Processor
+description: "Overview"
+---
+
+## Overview
+
+The Token Transfer Processor (TTP) is a [Go package](https://github.com/stellar/go-stellar-sdk/tree/main/processors/token_transfer) which uses the [ingest-sdk](/docs/data/indexers/build-your-own/ingest-sdk) to parse Stellar network transaction data and derive token transfer events. Before TTP, developers had to manually parse complex ledger data, operation results, and ledger entry changes to understand when and how value moved between accounts, contracts, and other entities on the network.
+
+Prior to [CAP-67 Unified Events](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md), tracking token transfers required significant custom logic to handle different operation types, interpret ledger changes, and reconstruct the flow of assets. CAP-67 introduced a standardized event format that simplifies this process by providing a unified way to represent all token transfer activities.
+
+TTP serves as a facade to CAP-67, automatically generating these standardized events from Stellar ledger data. It can operate in two modes:
+
+- **Standalone mode**: TTP analyzes operations, operation results, and ledger entry changes to derive transfer events
+- **Unified events mode**: TTP reads directly from CAP-67 compliant unified events when available in the ledger data
+
+For more details on operational modes, see the [Modes of Operation](#modes-of-operation) section.
+
+## Key Features
+
+- Captures token movements resulting from:
+  - Simple payments
+  - Path payments
+  - DEX operations
+  - Account merges
+  - Trustline revocations
+  - Claimable balance operations
+  - Liquidity pool operations
+  - Clawback operations
+  - Stellar Asset Contract events
+  - [SEP-41](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0041.md) compliant token events
+
+- Generates CAP-67 standardized token events:
+  - Transfer: Movement of tokens between accounts
+  - Mint: Creation of new tokens
+  - Burn: Destruction of tokens
+  - Clawback: Asset issuer reclaiming tokens
+  - Fee: Network fees paid
+
+- Handles muxed account information in compliance with CAP-67 multiplexing support
+
+- Reconciliation for older protocol versions to ensure consistency between operation changes and generated events
+
+## Events
+
+TTP generates events in Go bindings based on [protobuf definitions](https://github.com/stellar/go-stellar-sdk/blob/main/protos/processors/token_transfer/token_transfer_event.proto). The definitions codify an IDL for the standardized token transfer event models put forth in CAP-67. Each event contains metadata and type-specific information structured as follows:
+
+| Event Type | Description | Key Fields | When Generated |
+| --- | --- | --- | --- |
+| **Transfer** | Asset movement between two entities | `from`, `to`, `amount`, `asset`, `toMuxedInfo` | When assets move between accounts, contracts, or other entities |
+| **Mint** | Asset creation by the issuer | `to`, `amount`, `asset`, `toMuxedInfo` | When an issuer creates new tokens or when assets are sent from the issuer |
+| **Burn** | Asset destruction to the issuer | `from`, `amount`, `asset` | When assets are returned to the issuer for destruction |
+| **Clawback** | Forced asset recovery by issuer | `from`, `amount`, `asset` | When an issuer uses clawback operations to recover assets |
+| **Fee** | Network fee payment or refund | `account`, `amount` | For all transaction fees and Soroban fee refunds |
+
+### Fee Events
+
+TTP generates fee events to track network fees associated with transaction processing. Understanding the different types of fee events is important for accurate accounting:
+
+Fee events are generated for all transactions, whether they succeed or fail. These represent the network fees that accounts pay to submit transactions to the Stellar network.
+
+- **Present for**: Every transaction
+- **Amount representation**: Positive values indicating fees paid
+- **Asset**: Always XLM (Stellar's native asset)
+
+Fee refund events are generated only for Soroban (smart contract) transactions and only when there are unused resources that qualify for a refund.
+
+- **Present for**: Soroban transactions with unused resource fees
+- **Amount representation**: Negative values to indicate money being returned
+- **Asset**: Always XLM
+- **Event type**: Uses the same `Fee` event type, distinguished by the negative amount
+
+<Note>
+
+TTP uses negative amounts in fee events to represent refunds rather than creating a separate refund event type. This approach maintains consistency with the CAP-67 specification while clearly indicating the direction of the fee transaction.
+
+</Note>
+
+### Event Metadata
+
+Every token transfer event includes comprehensive metadata to provide context about when and where the event occurred:
+
+| Field | Type | Description |
+| --- | --- | --- |
+| `ledgerSequence` | `uint32` | The ledger number where this event occurred. This provides chronological ordering across the entire network. |
+| `txHash` | `string` | The transaction hash that generated this event. This allows you to trace events back to their originating transaction. |
+| `operationIndex` | `uint32*` | The one-based index of the operation within the transaction that caused this event as defined by [SEP-35](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0035.md). This field is `nil` for transaction-level events like fees. |
+| `contractAddress` | `string` | The contract address associated with the asset/token being moved. For classic operations or Stellar Asset Contract Events, this field will be the contractId of the underlying classic asset. This enables integration with Stellar's smart contract ecosystem. |
+
+<Note>
+
+The `toMuxedInfo` field is included in Transfer and Mint events when the destination uses a muxed account (M-address) and/or when transaction-level memo is set (in the case of non-smart contract transactions), providing additional routing information.
+
+</Note>
+
+Please refer to [this](/docs/build/guides/transactions/pooled-accounts-muxed-accounts-memos) section for more information on muxed account/memo usage.
+
+Please refer to [this](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md#prohibit-the-transaction-memo-and-muxed-source-accounts-from-being-set-on-soroban-transactions) section in CAP-67 to learn more on what to expect in the `toMuxedInfo` field.
+
+<Note>
+
+The `contractAddress` field is particularly important for DeFi applications as it provides the bridge between classic Stellar assets and their smart contract representations.
+
+For events from classic transactions and SAC events from smart contract transactions, the `contractAddress` field reflects the SAC address for the asset.
+
+</Note>
+
+## Go API Overview
+
+TTP provides three distinct functions which derive events from different levels of granularity from the underlying Stellar network data.
+
+### EventsFromLedger
+
+```go
+func (p *EventsProcessor) EventsFromLedger(lcm xdr.LedgerCloseMeta) ([]*TokenTransferEvent, error)
+```
+
+This function processes an entire ledger and returns a flattened list of `TokenTransferEvent` objects. The order of events in the returned slice represents the chronological ordering of debits, credits, and fees as they were applied to accounts, trustlines, and contracts during ledger processing.
+
+The chronological ordering is critical for applications that need to maintain accurate balance tracking or audit trails. For detailed information about how events are ordered, see the [Event Ordering](#event-ordering) section.
+
+### EventsFromTransaction
+
+```go
+func (p *EventsProcessor) EventsFromTransaction(tx ingest.LedgerTransaction) (TransactionEvents, error)
+```
+
+This function processes a single transaction and returns a `TransactionEvents` structure that separates fee-related events from operation-related events:
+
+- `FeeEvents`: Contains fee charges and refunds associated with the transaction
+- `OperationEvents`: Contains all events generated by the transaction's operations
+
+This separation is useful when you need to handle fees differently from operational transfers, such as for accounting or analytics purposes.
+
+### EventsFromOperation
+
+```go
+func (p *EventsProcessor) EventsFromOperation(
+	tx ingest.LedgerTransaction,
+	opIndex uint32,
+	op xdr.Operation,
+	opResult xdr.OperationResult
+	) ([]*TokenTransferEvent, error)
+```
+
+This function processes a single operation within a transaction and returns a list of events generated by that specific operation. This granular approach is useful for applications that need to analyze or react to specific types of operations.
+
+## Modes of Operation
+
+TTP can operate in two distinct modes depending on how the ledger data was generated and what information is available.
+
+### Default Mode (Recommended)
+
+In default mode, TTP analyzes three sources of information to derive token transfer events:
+
+- **Operations**: The operations submitted in transactions
+- **Operation Results**: The success/failure results of each operation
+- **Ledger Entry Changes**: The changes made to the ledger state
+
+This mode works with all Stellar ledgers regardless of how they were generated or which stellar-core version produced them. It is the safest and most compatible option.
+
+```go
+// Default mode - works with all ledgers
+processor := token_transfer.NewEventsProcessor(networkPassphrase)
+```
+
+### Unified Events Stream Mode
+
+In unified events stream mode, TTP reads token transfer events directly from the unified events stream embedded in the ledger data. This mode is more efficient but requires ledgers that were generated with specific stellar-core configuration flags.
+
+```go
+// Unified events mode - only for specially configured ledgers
+processor := token_transfer.NewEventsProcessorForUnifiedEvents(networkPassphrase)
+```
+
+Only use unified events stream mode if you are certain that your ledgers contain unified events. These ledgers must be generated by stellar-core with both `EMIT_CLASSIC_EVENTS=true` and `BACKFILL_STELLAR_ASSET_EVENTS=true` configuration flags enabled. TTP cannot dynamically determine whether a ledger contains unified events or not.
+
+<Warning>
+
+If you configure TTP for unified events mode and then provide it ledgers without unified events, TTP will silently produce no events.
+
+</Warning>
+
+**When in doubt, always use the default mode**, as it works reliably with all ledger types.
+
+## Event Ordering
+
+The order of events returned by TTP depends on the Stellar protocol version that was active when the ledger was created. This ordering is crucial for maintaining accurate chronological records of asset movements.
+
+### Pre-Protocol 23 Ordering
+
+Before Whisk, Protocol 23, events follow this chronological pattern:
+
+```
+All Fee Events (from all transactions)
+↓
+For each transaction in ledger:
+  - Operation Events (from all operations in the transaction)
+  - Fee Refund Event (if applicable, immediately after operation events)
+```
+
+In this ordering, fee refunds appear immediately after the operation events for each individual transaction.
+
+### Protocol 23+ Ordering {#protocol-23-ordering}
+
+Starting with Whisk, Protocol 23, events follow this chronological pattern:
+
+```
+All Fee Events (from all transactions)
+↓
+All Operation Events (from all transactions, maintaining transaction and operation order)
+↓
+All Fee Refund Events (from all transactions)
+```
+
+In this newer ordering, all fee refunds are grouped together at the end, after all transactions have been processed.
+
+<Note>
+
+TTP automatically detects the protocol version and applies the correct ordering rules. You don't need to configure this manually, but understanding the ordering differences is important for applications that depend on event sequence.
+
+</Note>
+
+The chronological ordering ensures that when you process events in the order returned by TTP, you're following the exact sequence in which debits and credits were applied to accounts during ledger processing. This is essential for maintaining accurate balance calculations and audit trails.
+
+## References
+
+- [CAP-67: Unified Events](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md)
+- [SEP-41: Asset Token Contract Specification](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0041.md)
+- [CAP-38: Automated Market Makers](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0038.md)
+- [SEP-35: ID Scheme for Stellar Operations](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0035.md)
diff --git a/docs/data/indexers/index.mdx b/docs/data/indexers/index.mdx
new file mode 100644
index 000000000..e280a2c71
--- /dev/null
+++ b/docs/data/indexers/index.mdx
@@ -0,0 +1,113 @@
+---
+title: Indexers Overview
+sidebarTitle: Indexers
+description: "When you first start building on a smart contract platform like Stellar, at first you can get everything you need from RPC calls."
+---
+
+## What is an indexer, and why would you need one?
+
+When you first start building on a smart contract platform like Stellar, at first you can get everything you need from RPC calls. You write a contract, or launch a Stellar Classic Asset and [wrap it in a smart contract](/docs/tokens/stellar-asset-contract), and you make a bundle of RPC calls from your frontend app directly to your smart contracts.
+
+At some point, though, you are likely to run into limitations with this approach.
+
+1. You might need to make _too many_ RPC calls. Imagine: your app lists 20 of a user's NFTs per page. First RPC call: get a list of NFT IDs for this user. Then: 20 simultaneous RPC calls to get data for each NFT. And possibly: for each of those, make additional HTTP requests to S3 buckets or IPFS nodes to fetch image data, etc. This can make your app slow, or even get you rate-limited by an RPC provider.
+2. You might want to show _historic_ data, like every time an NFT changed ownership. This sort of data lives _in the history of the blockchain_, but is not accessible via RPC calls to the most up-to-date version of a specific contract. Those would only return the current owner.
+
+Additionally, even some information that is currently available from [Horizon] will also require indexing services in the future, as Horizon will be deprecated.
+
+## What exactly is indexing?
+
+The word "indexing" has come to encompass a large array of use-cases. What all of them have in common is that they process and structure blockchain data. Let's think of it in the order of what you, an app-builder or small team, will need:
+
+### 1. Off-the-shelf APIs for common data {#portfolio-apis}
+
+This is the kind of stuff you might get from Horizon today, but can include more than that. For example, many indexing services in this category also provide the "every time an NFT changed ownership" kind of data mentioned above.
+
+Lots of apps need this kind of data, and it tends to have a standard shape. This makes it profitable for companies to build SaaS products, offering API access for a price (often with a free tier, appropriate for your early-stage startup or hackathon project).
+
+In the biz, these are called _Portfolio APIs._ Well-known companies offering them:
+
+- [Alchemy]: a widely-used data provider (popular on Ethereum), now live on Stellar. Its [Stellar Data API](https://www.alchemy.com/docs/reference/stellar-data-api-overview) serves indexed **transfer history**, **account balances**, and **NFT holdings** across Stellar assets and contract tokens — letting you query this data without running your own indexer (JSON request bodies, opaque `pageKey` pagination). Alchemy also provides [Stellar RPC](https://www.alchemy.com/docs/stellar/stellar-api-overview#stellar-apis) and appears in the [RPC providers](/docs/data/apis/rpc/providers) list.
+
+- [Allium]: currently building Stellar support, launching Q1 2026
+
+- [OBSRVR]: a home-grown Stellar-native offering, providing both RPC services and [Obsrvr Gateway](https://www.withobsrvr.com/products/gateway), promising "powerful APIs for real-time data fetching, transaction processing, and easy integration into existing systems."
+
+- [Horizon]: as mentioned above, Horizon will soon be deprecated, but for now it is the only way to get some of this data.
+
+### 2. Streaming & transforming data to a custom app database {#custom-transformations}
+
+Not all apps have data that fits a standard shape. Most, probably, need custom data transformation.
+
+Consider again the NFT example. Wouldn't it be great to return all needed NFT data in _one_ request, rather than N+1? That's what this style of indexing provides. And even better: you can (often) use these indexing solutions to aggregate data from multiple sources. If your NFT app stores additional information on IPFS, you could consolidate all of that off-chain data to your database as well. This makes your app much faster, saves you network & RPC requests, and creates new architecture possibilities.
+
+Well-known options:
+
+- [The Graph]: one of the earliest and most popular-at-the-time options on Ethereum. They now offer three main products:
+  1. [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs): their main & most famous offering, providing a [decentralized approach](https://thegraph.com/docs/en/subgraphs/developing/publishing/publishing-a-subgraph) to custom data transformation & hosting. The Graph's use of GraphQL APIs made GraphQL a popular choice for this entire category of indexing.
+  2. **Token API**, for Indexing [Use Case #1](#portfolio-apis) described above
+  3. **Substreams**, for [Use Case #3](#analytics) described below
+
+  The Graph offers Stellar support for Substreams, with no current plans to expand Subgraph or Token API support to Stellar.
+
+- [Goldsky]: one of the currently-most-loved options on Ethereum for this use-case. Goldsky provides [two main products](https://docs.goldsky.com/subgraph-vs-mirror):
+  1. **Subgraphs**: similar to those offered by The Graph, but data lives on Goldsky's own infrastructure rather than a decentralized network. Goldsky only offers this for EVM-based chains, with no plans to offer Subgraph support for Stellar.
+  2. **Mirror**, also called **Pipelines**: a highly efficient tool to Extract, Transform, & Load (ETL) data into your own database. Goldsky Mirrors already support Stellar; see [their documentation](https://docs.goldsky.com/chains/stellar).
+
+- [Mercury]: a home-grown Stellar-native team providing streamlined Soroban (Smart Contract) support via their [Retroshades](https://docs.mercurydata.app/retroshades/introduction-to-retroshades) product. Note that this streamlined Soroban support comes at the cost of _only_ supporting Soroban! Mercury also provide [Mercury "Classic"](https://docs.mercurydata.app/mercury-classic/introduction), giving access to contract events & Stellar transactions via a GraphQL interface, which might fit Indexer Use Case #1 more.
+
+- [SubQuery]: Decentralized Indexer SDK, Decentralized RPCs, & AI Apps. Supports 300+ chains. Like The Graph, uses a decentralized model.
+
+- [OnFinality]: a big player in the Polkadot ecosystem, now expanding to other blockchains. OnFinality provides data _hosting_ services for your SubQuery logic. SubQuery is the _software_, OnFinality is the _infra_, hosting 1. the pre-transformed raw Stellar data, 2. your SubGraph SDK-authored Extract, Transform, and Load (ETL) processor and 3. your final transformed data.
+
+- [Allium]: in addition to their Portfolio APIs offering, Allium is also under contract with SDF to build out tools for both Indexing Use Case #2 (this one) and Indexing Use Case #3 (see below), with target launch date of Q1 2026.
+
+- [Space and Time]: one challenge with most indexing approaches is the reintroduction of trusted 3rd parties into what is otherwise a verifiable, trustless software stack. Space and Time aims to fix this with "Proof of Indexing" and "Proof of SQL", using Zero-Knowledge proofs to offer tamper-proof computation for enterprises and dapps. Space and Time's Stellar support [launched](https://www.spaceandtime.io/blog/space-and-time-enables-new-sophisticated-financial-apps-for-the-stellar-ecosystem) in Q4 2025.
+
+- [OBSRVR Flow]: "Structured ledger data and contract events straight to your app or warehouse—no ETL needed." Currently in private beta.
+
+### 3. Blockchain-Flavored Big-Data Analytics {#analytics}
+
+For business intelligence, compliance, tracing suspicious operations, DeFi metric tracking, transaction flow analysis, etc. When your enterprise reaches a certain scale, it's worth paying Data Engineers to set up custom ETL pipelines and manage databases/datalakes, and then paying Data Analysts to answer questions about how people are interacting with your systems.
+
+The companies building tools for Indexer Use Case #2 above (The Graph, Goldsky, Allium, etc) tend to also have tools for Use Case #3.
+
+While often referred to as _indexing_, you can also think of this category as _analytics_. See the [analytics documentation](/docs/data/analytics) for solutions custom-tailored to this use-case.
+
+## Build Your Own
+
+If none of the indexing providers mentioned above currently meet your needs, you can also build your own. Start with this [tutorial on how to build your own custom network ingestion pipeline](/docs/build/apps/ingest-sdk/overview). Along the way, you'll use the following tools & services:
+
+### [Galexie](/docs/data/indexers/build-your-own/galexie)
+
+Galexie is a tool for acquiring Stellar ledger metadata from the network and exporting to external storage, a data lake. Galexie is the foundation of the Composable Data Pipeline (CDP) and serves as the first step in extracting raw Stellar ledger metadata and making it accessible. Learn more about CDP’s benefits and applications in [this blog post](https://stellar.org/blog/developers/composable-data-platform).
+
+**Why Use It:**
+
+- You want to maintain a data lake of pre-computed ledger metadata for historical and currently closed network ledgers.
+
+### [Ingest SDK](/docs/data/indexers/build-your-own/ingest-sdk)
+
+A set of Golang packages which can be used within an application as a programmatic domain model to interact with Stellar network.
+
+**Why Use It:**
+
+- You want rapid development of applications in Golang which can acquire and parse ledger meta data and ledger entries from Stellar network.
+- You want an intuitive, compile-time, type-safe application developer experience.
+- You want to programmatically access History Archives to retrieve ledger entries.
+
+### [Processors](/docs/data/indexers/build-your-own/processors)
+
+A suite of Go packages that help you parse Stellar blockchain data.
+
+[Horizon]: /docs/data/apis/horizon
+[Allium]: https://www.allium.so/
+[Alchemy]: https://www.alchemy.com/
+[Goldsky]: https://goldsky.com/
+[OBSRVR]: https://www.withobsrvr.com/
+[The Graph]: https://thegraph.com/docs/en/about/
+[Mercury]: https://docs.mercurydata.app/
+[SubQuery]: https://subquery.network/
+[OnFinality]: https://onfinality.io/
+[Space and Time]: https://www.spaceandtime.io/
+[OBSRVR Flow]: https://www.withobsrvr.com/products/flow
diff --git a/docs/data/oracles/README.mdx b/docs/data/oracles/README.mdx
deleted file mode 100644
index 22a9924e3..000000000
--- a/docs/data/oracles/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Oracles
-description: Learn about oracles and off-chain data sources
-sidebar_label: Oracles
-sidebar_position: 10
----
-
-# Oracles
-
-Oracles are services that connect blockchain systems to external, off-chain data sources, enabling smart contracts to interact with real-world information. They act as intermediaries, fetching and verifying data such as market prices, weather conditions, or event outcomes, and then delivering it to the blockchain in a secure and reliable manner. This allows decentralized applications (dApps) to execute based on real-world events, expanding their functionality beyond on-chain data.
diff --git a/docs/data/oracles/index.mdx b/docs/data/oracles/index.mdx
new file mode 100644
index 000000000..9c2303496
--- /dev/null
+++ b/docs/data/oracles/index.mdx
@@ -0,0 +1,6 @@
+---
+title: Oracles
+description: Learn about oracles and off-chain data sources
+---
+
+Oracles are services that connect blockchain systems to external, off-chain data sources, enabling smart contracts to interact with real-world information. They act as intermediaries, fetching and verifying data such as market prices, weather conditions, or event outcomes, and then delivering it to the blockchain in a secure and reliable manner. This allows decentralized applications (dApps) to execute based on real-world events, expanding their functionality beyond on-chain data.
diff --git a/docs/data/oracles/oracle-providers.mdx b/docs/data/oracles/oracle-providers.mdx
index 1ab4f37f1..6bee815c9 100644
--- a/docs/data/oracles/oracle-providers.mdx
+++ b/docs/data/oracles/oracle-providers.mdx
@@ -1,8 +1,6 @@
 ---
 title: Oracle Providers
 description: Explore on-chain data and prices feeds using oracles.
-sidebar_label: Oracle Providers
-sidebar_position: 20
 ---
 
 Oracles exist on the Stellar network to bring off-chain data onto the blockchain. For example, a popular use-case of oracles is the inclusion of token pricing into smart contract logic. Since a smart contract can't access data from outside the Stellar network, oracles provide a means by which the data can be accessed on-chain.
diff --git a/docs/index.mdx b/docs/index.mdx
new file mode 100644
index 000000000..04fbf3310
--- /dev/null
+++ b/docs/index.mdx
@@ -0,0 +1,35 @@
+---
+title: Stellar Developer Docs
+description: "Contains tutorials and how-to guides for writing smart contracts, building applications, interacting with the network, and more."
+hide_sidebar: true
+---
+
+## Navigating the docs
+
+### [Build](/docs/build)
+
+Contains tutorials and how-to guides for writing smart contracts, building applications, interacting with the network, and more.
+
+### [Learn](/docs/learn/fundamentals)
+
+Find all informational and conceptual content here. Learn about Stellar fundamentals like how accounts and transactions function, dive deeper into the functionality of each operation, discover how fees work, and more.
+
+### [Tokens](/docs/tokens)
+
+Information on how to issue assets on the Stellar network and create contract tokens.
+
+### [Data](/docs/data)
+
+Discover various data availability options: RPC, Hubble, Galexie, the Ingest SDK, and Horizon (nearing end-of-life).
+
+### [Tools](/docs/tools)
+
+Learn about all the available tools at your disposal for building on, interacting with, or just watching the Stellar network. Also, find information on how to use the Anchor Platform or Stellar Disbursement Platform.
+
+### [Networks](/docs/networks)
+
+Information about deployed networks (Mainnet, Testnet, and Futurenet), current software versions, and resource limitations and fees.
+
+### [Validators](/docs/validators)
+
+Everything you'll need to know if you want to run, operate, and maintain a core validator node on the Stellar network.
diff --git a/docs/learn/fundamentals/README.mdx b/docs/learn/fundamentals/README.mdx
deleted file mode 100644
index c8f9f776a..000000000
--- a/docs/learn/fundamentals/README.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: "Fundamentals of the Network; Data, Fees, Consensus, SEPs & More"
-sidebar_label: Core Concepts
-description: "Learn the fundamentals and key concepts of the Stellar blockchain, including data structures, fees, consensus, anchors, Stellar Ecosystem Proposals, and more."
-sidebar_position: 10
----
-
-# Core Concepts
-
-import DocCardList from "@theme/DocCardList";
-
-Build your foundational understanding of what makes the Stellar network tick.
-
-<DocCardList />
diff --git a/docs/learn/fundamentals/anchors.mdx b/docs/learn/fundamentals/anchors.mdx
index 4492bb7c0..3f5ae97a8 100644
--- a/docs/learn/fundamentals/anchors.mdx
+++ b/docs/learn/fundamentals/anchors.mdx
@@ -1,15 +1,16 @@
 ---
-title: "Learn About Anchors: On/Off Ramps for Bridging Traditional Finance & Blockchain"
-sidebar_position: 90
-sidebar_label: Anchors
+title: Anchors
+"og:title": "Learn About Anchors: On/Off Ramps for Bridging Traditional Finance & Blockchain"
 description: "Learn about the on and off ramps on Stellar called anchors and their role in bridging between the traditional financial system and blockchain networks."
 ---
 
-import YouTube from "@site/src/components/YouTube";
-
-# Anchors
-
-<YouTube ID="9iN9XT1rHHA" />
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/9iN9XT1rHHA?rel=0&modestbranding=1"
+  title="Informational explainer"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+></iframe>
 
 Anchors are Stellar's on- and off-ramps to traditional financial rails, typically operated by financial institutions or fintech companies. Anchors accept deposits of fiat currencies (such as the US dollar, Argentine peso, or Nigerian naira) via existing rails (such as bank deposits or cash-in points), then send the user the equivalent digital tokens on the Stellar network. The equivalent digital tokens can either represent that same fiat currency or another digital token altogether. Alternatively, anchors allow token holders to redeem their tokens for the real-world assets they represent.
 
@@ -17,17 +18,17 @@ Stellar has anchor services operating worldwide. View the [Anchor Directory](htt
 
 Anchors can issue their own assets on the Stellar network, or they can honor assets that already exist.
 
-You can set up an anchor by using the SDF-maintained [Anchor Platform](../../platforms/anchor-platform/README.mdx), which is the easiest way to deploy an anchor service compatible with Stellar Ecosystem Proposals (SEPs).
+You can set up an anchor by using the SDF-maintained [Anchor Platform](/docs/platforms/anchor-platform), which is the easiest way to deploy an anchor service compatible with Stellar Ecosystem Proposals (SEPs).
 
-Learn how to integrate anchor services into your blockchain-based application by viewing the [Build Apps section](../../build/apps/overview.mdx). If you're looking for MoneyGram Ramps, see the [Integrate with MoneyGram Ramps tutorial](https://developer.moneygram.com/moneygram-developer/docs/integrate-moneygram-ramps).
+Learn how to integrate anchor services into your blockchain-based application by viewing the [Build Apps section](../../build/apps/overview). If you're looking for MoneyGram Ramps, see the [Integrate with MoneyGram Ramps tutorial](https://developer.moneygram.com/moneygram-developer/docs/integrate-moneygram-ramps).
 
 ## Stellar Ecosystem Proposals (SEPs)
 
-Stellar is an open-source network that is designed to interoperate with traditional financial institutions, various types of assets, and other networks. Network participants implement Stellar Ecosystem Proposals (SEPs) so they can interoperate with other products and services on the network. The Stellar community creates SEPs as open-source documents in a [GitHub repository](https://github.com/stellar/stellar-protocol/tree/master/ecosystem#stellar-ecosystem-proposals-seps.mdx); they define how anchors, asset issuers, applications, exchanges, and other service providers should interact and interoperate.
+Stellar is an open-source network that is designed to interoperate with traditional financial institutions, various types of assets, and other networks. Network participants implement Stellar Ecosystem Proposals (SEPs) so they can interoperate with other products and services on the network. The Stellar community creates SEPs as open-source documents in a [GitHub repository](https://github.com/stellar/stellar-protocol/tree/master/ecosystem#stellar-ecosystem-proposals-seps); they define how anchors, asset issuers, applications, exchanges, and other service providers should interact and interoperate.
 
-Read more about SEPs in the [SEPs section](../fundamentals/stellar-ecosystem-proposals.mdx).
+Read more about SEPs in the [SEPs section](../fundamentals/stellar-ecosystem-proposals).
 
-:::info
+<Info>
 
 For anchors, the most important SEPs are:
 
@@ -43,7 +44,7 @@ Anchors also work with:
 - [SEP-12](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md): KYC API
 - [SEP-38](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md): Anchor RFQ API
 
-:::
+</Info>
 
 ### SEP-6 vs. SEP-24: Programmatic vs. Hosted Transfers
 
diff --git a/docs/learn/fundamentals/contract-development/README.mdx b/docs/learn/fundamentals/contract-development/README.mdx
deleted file mode 100644
index d57866720..000000000
--- a/docs/learn/fundamentals/contract-development/README.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Smart Contracts
-sidebar_position: 84
----
-
-import DocCardList from "@theme/DocCardList";
-
-<DocCardList />
diff --git a/docs/learn/fundamentals/contract-development/authorization.mdx b/docs/learn/fundamentals/contract-development/authorization.mdx
index abe178d21..6fb90a288 100644
--- a/docs/learn/fundamentals/contract-development/authorization.mdx
+++ b/docs/learn/fundamentals/contract-development/authorization.mdx
@@ -1,6 +1,6 @@
 ---
 title: Authorization
-sidebar_position: 30
+description: 'Authorization is the process of judging which operations "should" or "should not" be allowed to occur; it is about judging _permission_.'
 ---
 
 Authorization is the process of judging which operations "should" or "should not" be allowed to occur; it is about judging _permission_.
@@ -9,7 +9,7 @@ Authorization differs from _authentication_, which is the narrower problem of ju
 
 Authorization often uses cryptographic authentication (via signatures) to support its judgments, but is a broader, more general process.
 
-View the [authorization starter guide](../../../build/guides/auth/contract-authorization.mdx) to learn more about smart contract authorization on Stellar.
+View the [authorization starter guide](../../../build/guides/auth/contract-authorization) to learn more about smart contract authorization on Stellar.
 
 ## Soroban Authorization Framework
 
@@ -29,7 +29,7 @@ We realize that it's not possible to cover each and every case, but we hope that
 
 #### Contract storage
 
-Contracts have an exclusive read and write access to their [storage](../../../build/smart-contracts/getting-started/storing-data.mdx) in the ledger. This allows contracts to safely control and manage user access to their data. For example, a token contract may ensure that only the administrator can mint more of the token by storing the administrator identity in its storage. Similarly, it can make sure that only an owner of the balance may transfer that balance.
+Contracts have an exclusive read and write access to their [storage](../../../build/smart-contracts/getting-started/storing-data) in the ledger. This allows contracts to safely control and manage user access to their data. For example, a token contract may ensure that only the administrator can mint more of the token by storing the administrator identity in its storage. Similarly, it can make sure that only an owner of the balance may transfer that balance.
 
 #### `Address`
 
@@ -41,7 +41,7 @@ From the contract perspective `Address` is an opaque identifier type. The contra
 
 Both functions ensure that the `Address` has authorized the call of the current function within the current context (where context is defined by `require_auth` calls in the current call stack; see more formal definition in the [section below](#require_auth-implementation-details)). The authentication rules for this authorization are defined by the `Address` and are enforced by the Soroban host. Replay protection is also implemented in the host, i.e., there is normally no need for a contract to manage its own nonces.
 
-[auth example]: ../../../build/smart-contracts/example-contracts/auth.mdx
+[auth example]: ../../../build/smart-contracts/example-contracts/auth
 
 #### Authorizing Sub-contract Calls
 
@@ -49,7 +49,7 @@ One of the key features of Soroban Authorization Framework is the ability to eas
 
 Contracts don't need to do anything special to benefit from this feature. Just calling a sub-contract that calls `require_auth` will ensure that the sub-contract call has been properly authorized.
 
-[timelock example]: ../../../build/smart-contracts/example-contracts/timelock.mdx
+[timelock example]: ../../../build/smart-contracts/example-contracts/timelock
 
 #### When to `require_auth`
 
@@ -63,7 +63,7 @@ The main authorization-related decision a contract writer needs to make for any
 
 There is no explicit restriction on how many `Address` entities the contract uses and how many `Address`es have `require_auth` called. That means that it is possible to authorize a contract call on behalf of multiple users, which may even have different authorization contexts (customized via arguments in `require_auth_for_args`). [Atomic swap] is an example that deals with authorization of two `Address`es.
 
-[atomic swap]: ../../../build/smart-contracts/example-contracts/atomic-swap.mdx
+[atomic swap]: ../../../build/smart-contracts/example-contracts/atomic-swap
 
 Note though, that contracts that deal with multiple authorized `Address`es need a bit more complex support on the client side (to collect and attach the proper signatures).
 
@@ -79,9 +79,9 @@ Account abstraction provides a convenient extension point for every contract tha
 
 Conceptually, every abstract account is a special contract that defines authentication rules and potentially some additional account-specific authorization policies. However, for the sake of optimization and integration with the existing Stellar accounts, Soroban supports 4 different kinds of the account implementations.
 
-Below are the general descriptions of these implementations. See the transaction [guide](../contract-development/contract-interactions/stellar-transaction.mdx) for the concrete information of how different accounts are represented.
+Below are the general descriptions of these implementations. See the transaction [guide](../contract-development/contract-interactions/stellar-transaction) for the concrete information of how different accounts are represented.
 
-##### Stellar Account
+#### Stellar Account {#stellar-account}
 
 Corresponds to `Address::Account`.
 
@@ -89,9 +89,9 @@ This is a special, built-in 'account contract' that handles all the Stellar acco
 
 This supports the Stellar multisig with medium threshold. See Stellar [documentation] for more details on multisig and thresholds.
 
-[documentation]: ../transactions/signatures-multisig.mdx
+[documentation]: ../transactions/signatures-multisig
 
-##### Transaction Invoker
+#### Transaction Invoker {#transaction-invoker}
 
 Corresponds to `Address::Account`.
 
@@ -99,13 +99,13 @@ This is also a Stellar account, but its signature is inferred from the source ac
 
 This is purely an optimization of the [Stellar Account](#stellar-account) that can skip one signature in case the transaction source account also authorizes the contract invocation.
 
-##### Contract Invoker
+#### Contract Invoker {#contract-invoker}
 
 Corresponds to `Address::Contract`.
 
 This is a special case of an 'account' that may appear only when a contract calls another contract. We consider that since the contract makes a call, then it must be authorizing it (otherwise, it shouldn't have made that call). Hence all the `require_auth` calls made on behalf of the **direct** invoker contract `Address` are considered to be authorized (but not any calls on behalf of the contract deeper down the stack).
 
-##### Contract Account
+#### Contract Account {#contract-account}
 
 Corresponds to `Address::Contract`.
 
@@ -117,11 +117,11 @@ Contract accounts can also be treated as a custodial wallet. It holds the user's
 
 For the exact interface and more details, see the [Simple Account example].
 
-[Simple Account example]: ../../../build/smart-contracts/example-contracts/simple-account.mdx
+[Simple Account example]: ../../../build/smart-contracts/example-contracts/simple-account
 
 ### Secp256r1, passkeys and contract accounts
 
-After a successful public validator vote to upgrade Stellar's Mainnet to Protocol 21, the secp256r1 signature scheme was enabled for smart contract transactions. This allows developers to implement passkeys to sign transactions instead of using secret keys or seed phrases. For guidance, see the [passkey wallet guide](../../../build/guides/contract-accounts/smart-wallets.mdx).
+After a successful public validator vote to upgrade Stellar's Mainnet to Protocol 21, the secp256r1 signature scheme was enabled for smart contract transactions. This allows developers to implement passkeys to sign transactions instead of using secret keys or seed phrases. For guidance, see the [passkey wallet guide](../../../build/guides/contract-accounts/smart-wallets).
 
 ### Advanced Concepts
 
@@ -162,7 +162,7 @@ In simpler terms, `SorobanAuthorizedInvocation` trees for an `Address` are subse
 
 During the matching process that happens for every `require_auth` host tries to match the current path in `T` to a `SorobanAuthorizedInvocation` tree for the corresponding `Address`. The path is considered to be matched only when there is a corresponding path of _exhausted_ `R` nodes leading to the current call. This means that if the `Address` signs a sequence of calls `A.foo->B.bar->C.baz`, then its authorization check will fail in case if `A.foo` directly calls `C.baz` because `C.baz` strictly has to be called from `B.bar`.
 
-##### Duplicate Addresses
+#### Duplicate Addresses {#duplicate-addresses}
 
 In case if the same contract function calls `require_auth` for the same `Address` multiple times (e.g. when multiple operations from the same user are being batched), every `require_auth` call still has to have a corresponding node in the `SorobanAuthorizedInvocation` tree. Due to that, there might be multiple valid trees that make all the authorization checks pass. There is nothing wrong about that - the address still must have authorized all the invocations. The only requirement for such cases to be handled correctly is to ensure that the `require_auth` calls for an `Address` happen before the corresponding sub-contract calls.
 
diff --git a/docs/learn/fundamentals/contract-development/contract-interactions/README.mdx b/docs/learn/fundamentals/contract-development/contract-interactions/README.mdx
deleted file mode 100644
index 34b770a5f..000000000
--- a/docs/learn/fundamentals/contract-development/contract-interactions/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Contract Interactions
-sidebar_position: 8
----
-
-import DocCardList from "@theme/DocCardList";
-
-Learn about the methods available for developers and users to interact with deployed contracts.
-
-<DocCardList />
diff --git a/docs/learn/fundamentals/contract-development/contract-interactions/cross-contract.mdx b/docs/learn/fundamentals/contract-development/contract-interactions/cross-contract.mdx
index 8470000a4..4e4d7bad2 100644
--- a/docs/learn/fundamentals/contract-development/contract-interactions/cross-contract.mdx
+++ b/docs/learn/fundamentals/contract-development/contract-interactions/cross-contract.mdx
@@ -1,5 +1,4 @@
 ---
-sidebar_position: 10
 title: Cross-Contract
 description: Interact with a Soroban contract from within another Soroban contract.
 ---
@@ -30,5 +29,5 @@ e.register(Token {}, (admin, decimal, name, symbol))
 
 For calling a contract's other functions, see [Making cross-contract calls].
 
-[token example contract]: ../../../../build/smart-contracts/example-contracts/tokens.mdx
-[making cross-contract calls]: ../../../../build/guides/conventions/cross-contract.mdx
+[token example contract]: ../../../../build/smart-contracts/example-contracts/tokens
+[making cross-contract calls]: ../../../../build/guides/conventions/cross-contract
diff --git a/docs/learn/fundamentals/contract-development/contract-interactions/index.mdx b/docs/learn/fundamentals/contract-development/contract-interactions/index.mdx
new file mode 100644
index 000000000..8e680633e
--- /dev/null
+++ b/docs/learn/fundamentals/contract-development/contract-interactions/index.mdx
@@ -0,0 +1,32 @@
+---
+title: Contract Interactions
+description: "Learn about the methods available for developers and users to interact with deployed contracts."
+---
+
+<CardGroup cols={2}>
+  <Card title="Overview" icon="file-lines" href="/docs/learn/fundamentals/contract-development/contract-interactions/overview">
+
+    Interact with smart contracts.
+
+  </Card>
+  <Card title="Cross-Contract" icon="file-lines" href="/docs/learn/fundamentals/contract-development/contract-interactions/cross-contract">
+
+    Interact with a Soroban contract from within another Soroban contract.
+
+  </Card>
+  <Card title="Tests" icon="file-lines" href="/docs/learn/fundamentals/contract-development/contract-interactions/tests">
+
+    Interacting with contracts in tests
+
+  </Card>
+  <Card title="Stellar Transaction" icon="file-lines" href="/docs/learn/fundamentals/contract-development/contract-interactions/stellar-transaction">
+
+    Invoke and deploy smart contracts with the InvokeHostFunctionOp operation.
+
+  </Card>
+  <Card title="Transaction Simulation" icon="file-lines" href="/docs/learn/fundamentals/contract-development/contract-interactions/transaction-simulation">
+
+    Simulate a contract interaction contained in a Stellar transaction.
+
+  </Card>
+</CardGroup>
diff --git a/docs/learn/fundamentals/contract-development/contract-interactions/overview.mdx b/docs/learn/fundamentals/contract-development/contract-interactions/overview.mdx
index d4079e81d..615924d82 100644
--- a/docs/learn/fundamentals/contract-development/contract-interactions/overview.mdx
+++ b/docs/learn/fundamentals/contract-development/contract-interactions/overview.mdx
@@ -1,19 +1,10 @@
 ---
 title: Overview
+og:title: "Interact with smart contracts."
+og:description: "Interact with smart contracts with function calls, contract invocation, and blockchain operations."
 description: Interact with smart contracts.
-sidebar_position: 5
 ---
 
-<head>
-  <title>Interact with smart contracts.</title>
-  <meta charSet="utf-8" />
-  <meta property="og:title" content="Interact with smart contracts." />
-  <meta
-    property="og:description"
-    content="Interact with smart contracts with function calls, contract invocation, and blockchain operations."
-  />
-</head>
-
 Contracts are invoked through a pair of host functions `call` and `try_call`:
 
 - `try_call(contract, function, args)` calls `function` exported from `contract`, passing `args` and returning an `Error` on a recoverable error. A non-recoverable error traps instead.
@@ -49,6 +40,6 @@ Two groups of errors are non-recoverable:
 
 Both groups break a precondition of the invocation, so the host cannot let the contract continue. A budget error recurs on a retry, because the transaction is still out of budget. A footprint violation recurs too, because a transaction cannot add an entry to its own footprint while it runs.
 
-The footprint case is the one to watch, because it is not obvious. A contract that derives a storage key from volatile state, such as a random value or the ledger sequence, can read an entry that [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction.mdx) never saw. The footprint then misses that entry and the call traps. [Debugging Contract Errors](../errors-and-debugging/debugging-errors.mdx) lists the diagnostic events for this case and the other errors of the apply step.
+The footprint case is the one to watch, because it is not obvious. A contract that derives a storage key from volatile state, such as a random value or the ledger sequence, can read an entry that [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction) never saw. The footprint then misses that entry and the call traps. [Debugging Contract Errors](../errors-and-debugging/debugging-errors) lists the diagnostic events for this case and the other errors of the apply step.
 
 Every other error is recoverable. `try_call` passes a contract error code through unchanged. It reports every other recoverable host error as an error of type `Context` with the code `InvalidAction`, and the granular code stays visible in the diagnostic events.
diff --git a/docs/learn/fundamentals/contract-development/contract-interactions/stellar-transaction.mdx b/docs/learn/fundamentals/contract-development/contract-interactions/stellar-transaction.mdx
index bbf31c9a1..6c1d9429b 100644
--- a/docs/learn/fundamentals/contract-development/contract-interactions/stellar-transaction.mdx
+++ b/docs/learn/fundamentals/contract-development/contract-interactions/stellar-transaction.mdx
@@ -1,36 +1,19 @@
 ---
-sidebar_position: 30
 title: Stellar Transaction
+og:title: "Invoke and deploy smart contracts with the InvokeHostFunctionOp operation."
+og:description: "Invoke and deploy smart contracts with the InvokeHostFunctionOp operation."
 description: Invoke and deploy smart contracts with the InvokeHostFunctionOp operation.
 toc_max_heading_level: 4
 ---
 
-<head>
-  <title>
-    {`Invoke and deploy smart contracts with the InvokeHostFunctionOp operation.`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Invoke and deploy smart contracts with the InvokeHostFunctionOp operation."
-  />
-  <meta
-    property="og:description"
-    content="Invoke and deploy smart contracts with the InvokeHostFunctionOp operation."
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
 ## Example SDK Usage
 
-Some (but not all yet) of the Stellar SDKs have functions built-in to handle most of the process of building a Stellar transaction to interact with a Soroban smart contract. Below, we demonstrate in JavaScript and Python how to build and submit a Stellar transaction that will invoke an instance of the [increment example](../../../../build/smart-contracts/getting-started/storing-data.mdx) smart contract.
+Some (but not all yet) of the Stellar SDKs have functions built-in to handle most of the process of building a Stellar transaction to interact with a Soroban smart contract. Below, we demonstrate in JavaScript and Python how to build and submit a Stellar transaction that will invoke an instance of the [increment example](../../../../build/smart-contracts/getting-started/storing-data) smart contract.
 
 <Tabs>
-<TabItem value="js" label="JavaScript">
+<Tab title="JavaScript">
 
-:::tip
+<Tip>
 
 The existing [JavaScript SDK](https://github.com/stellar/js-stellar-sdk) now incorporates all of the elements needed for Soroban. All you need to do is install it using your preferred package manager.
 
@@ -38,7 +21,7 @@ The existing [JavaScript SDK](https://github.com/stellar/js-stellar-sdk) now inc
 npm install --save @stellar/stellar-sdk
 ```
 
-:::
+</Tip>
 
 ```js
 (async () => {
@@ -144,10 +127,10 @@ npm install --save @stellar/stellar-sdk
 })();
 ```
 
-</TabItem>
-<TabItem value="py" label="Python">
+</Tab>
+<Tab title="Python">
 
-:::tip
+<Tip>
 
 The [`py-stellar-base`](https://stellar-sdk.readthedocs.io/en/soroban) Python SDK has stable support for interacting with Soroban smart contracts as of [v9.0.0](https://github.com/StellarCN/py-stellar-base/releases/tag/9.0.0).
 
@@ -155,7 +138,7 @@ The [`py-stellar-base`](https://stellar-sdk.readthedocs.io/en/soroban) Python SD
 pip install stellar-sdk
 ```
 
-:::
+</Tip>
 
 ```py
 from typing import Optional, Union
@@ -206,14 +189,14 @@ result = client.increment(source_keypair.public_key).sign_and_submit(source_keyp
 print(result)
 ```
 
-</TabItem>
-<TabItem value="java" label="Java">
+</Tab>
+<Tab title="Java">
 
-:::tip
+<Tip>
 
 [java-stellar-sdk](https://github.com/lightsail-network/java-stellar-sdk) provides support for Soroban. Please visit the project homepage for more information.
 
-:::
+</Tip>
 
 ```java
 import java.io.IOException;
@@ -326,7 +309,7 @@ public class SorobanExample {
 }
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 ## XDR Usage
@@ -337,9 +320,9 @@ The `InvokeHostFunctionOp` can be used to perform the following Soroban operatio
 
 - Invoke contract functions.
 - Upload Wasm of the new contracts.
-- Deploy new contracts using the uploaded Wasm or built-in implementations (this currently includes only the [token contract](../../../../tokens/stellar-asset-contract.mdx)).
+- Deploy new contracts using the uploaded Wasm or built-in implementations (this currently includes only the [token contract](../../../../tokens/stellar-asset-contract)).
 
-[`stellar-cli`]: ../../../../build/smart-contracts/getting-started/setup.mdx#install-the-stellar-cli
+[`stellar-cli`]: ../../../../build/smart-contracts/getting-started/setup#install-the-stellar-cli
 
 There is only a single `InvokeHostFunctionOp` allowed per transaction. Contracts should be used to perform multiple actions atomically, for example, to deploy a new contract and initialize it atomically.
 
@@ -349,7 +332,7 @@ Additionally, Soroban transactions containing `InvokeHostFunctionOp` have the fo
 - The transaction **source account cannot be a muxed account**.
 - The **operation source account, if set, cannot be a muxed account**.
 
-See [Send to and receive payments from Contract Accounts](../../../../build/guides/transactions/send-and-receive-c-accounts.mdx) for information on how to provide a muxed ID when making payments in Soroban.
+See [Send to and receive payments from Contract Accounts](../../../../build/guides/transactions/send-and-receive-c-accounts) for information on how to provide a muxed ID when making payments in Soroban.
 
 ### InvokeHostFunctionOp
 
@@ -464,16 +447,16 @@ The `hostFunction` in `InvokeHostFunctionOp` will be executed by the Soroban hos
 
 ##### JavaScript Usage
 
-Each of these variations of host function invocation has convenience methods in the [JavaScript SDK](../../../../tools/sdks/client-sdks.mdx#javascript-sdk):
+Each of these variations of host function invocation has convenience methods in the [JavaScript SDK](../../../../tools/sdks/client-sdks#javascript-sdk):
 
 - [`Operation.invokeHostFunction`](https://stellar.github.io/js-stellar-sdk/Operation.html#.invokeHostFunction) is the lowest-level method that corresponds directly to the XDR.
 - [`Operation.invokeContractFunction`](https://stellar.github.io/js-stellar-sdk/Operation.html#.invokeContractFunction) is an abstraction to invoke the method of a particular contract, similar to [`Contract.call`](https://stellar.github.io/js-stellar-sdk/Contract.html#call).
-- [`Operation.createStellarAssetContract`](https://stellar.github.io/js-stellar-sdk/Operation.html#.createStellarAssetContract) and [`Operation.createCustomContract`](https://stellar.github.io/js-stellar-sdk/Operation.html#.createCustomContract) are abstractions to instantiate contracts: the former is for wrapping an existing [Stellar asset](../../../../tokens/how-to-issue-an-asset.mdx) into a smart contract and the latter is for deploying your own contract.
+- [`Operation.createStellarAssetContract`](https://stellar.github.io/js-stellar-sdk/Operation.html#.createStellarAssetContract) and [`Operation.createCustomContract`](https://stellar.github.io/js-stellar-sdk/Operation.html#.createCustomContract) are abstractions to instantiate contracts: the former is for wrapping an existing [Stellar asset](../../../../tokens/how-to-issue-an-asset) into a smart contract and the latter is for deploying your own contract.
 - [`Operation.uploadContractWasm`](https://stellar.github.io/js-stellar-sdk/Operation.html#.uploadContractWasm) corresponds to the above `HOST_FUNCTION_TYPE_UPLOAD_CONTRACT_WASM` variant, letting you upload the raw WASM buffer to the ledger.
 
 #### Authorization Data
 
-Soroban's [authorization framework](../authorization.mdx) provides a standardized way for passing authorization data to the contract invocations via `SorobanAuthorizationEntry` structures.
+Soroban's [authorization framework](../authorization) provides a standardized way for passing authorization data to the contract invocations via `SorobanAuthorizationEntry` structures.
 
 ```cpp
 struct SorobanAuthorizationEntry
@@ -547,9 +530,9 @@ struct SorobanAuthorizedContractFunction
 Building `SorobanAuthorizedInvocation` trees may be simplified by using the recording auth mode in Soroban's `simulateTransaction` mechanism (see the [docs][simulate-transaction-doc] for more details).
 
 [envelope-xdr]: https://github.com/stellar/stellar-xdr/blob/v27.0/Stellar-transaction.x#L747-L754
-[simulate-transaction-doc]: transaction-simulation.mdx#authorization
+[simulate-transaction-doc]: transaction-simulation#authorization
 
-##### Stellar Account Signatures
+#### Stellar Account Signatures {#stellar-account-signatures}
 
 `signatureArgs` format is user-defined for the [custom accounts], but it is protocol-defined for the Stellar accounts.
 
@@ -564,9 +547,9 @@ pub struct AccountEd25519Signature {
 ```
 
 [structures]: https://github.com/stellar/rs-soroban-env/blob/99d8c92cdc7e5cd0f5311df8f88d04658ecde7d2/soroban-env-host/src/native_contract/account_contract.rs#L51
-[custom accounts]: ../authorization.mdx#account-abstraction
+[custom accounts]: ../authorization#account-abstraction
 
-##### JavaScript Usage
+#### JavaScript Usage {#javascript-usage-1}
 
 There are a couple of helpful methods in the SDK to make dealing with authorization easier:
 
@@ -594,7 +577,7 @@ const signedEntries = simTx.auth.map(async (entry) =>
 
 ### Transaction resources
 
-Every Soroban transaction has to have a `SorobanTransactionData` transaction [extension] populated. This is needed to compute the [Soroban resource fee](../../../fundamentals/fees-resource-limits-metering.mdx).
+Every Soroban transaction has to have a `SorobanTransactionData` transaction [extension] populated. This is needed to compute the [Soroban resource fee](../../../fundamentals/fees-resource-limits-metering).
 
 [extension]: https://github.com/stellar/stellar-xdr/blob/v27.0/Stellar-transaction.x#L957-L964
 
@@ -637,12 +620,12 @@ struct SorobanTransactionData
 };
 ```
 
-This data comprises the Soroban `resources` and the `resourceFee`. The `resourceFee` is the portion of the transaction fee allocated to Soroban resource fees. It has a non-refundable part (fees for instructions, ledger I/O, and transaction size) and a refundable part that is charged based on actual consumption of refundable resources: the contract events emitted by the transaction, the return value of the host function invocation, and the [ledger space rent](../storage/state-archival.mdx).
+This data comprises the Soroban `resources` and the `resourceFee`. The `resourceFee` is the portion of the transaction fee allocated to Soroban resource fees. It has a non-refundable part (fees for instructions, ledger I/O, and transaction size) and a refundable part that is charged based on actual consumption of refundable resources: the contract events emitted by the transaction, the return value of the host function invocation, and the [ledger space rent](../storage/state-archival).
 
 The `SorobanResources` structure includes the ledger footprint and the resource values, which together determine the resource consumption limit and the resource fee. The footprint must contain the `LedgerKey`s that will be read and/or written.
 
-The simplest method to determine the values in `SorobanResources` and `resourceFee` is to use the [`simulateTransaction` mechanism](transaction-simulation.mdx).
+The simplest method to determine the values in `SorobanResources` and `resourceFee` is to use the [`simulateTransaction` mechanism](/docs/learn/fundamentals/contract-development/contract-interactions/transaction-simulation).
 
-#### JavaScript Usage
+#### JavaScript Usage {#javascript-usage-2}
 
 You can use the [`SorobanDataBuilder`](https://stellar.github.io/js-stellar-sdk/SorobanDataBuilder.html) to leverage the [builder pattern](https://en.wikipedia.org/wiki/Builder_pattern) and get/set all of the above resources accordingly. Then, you call `.build()` and pass the resulting structure to the [`setSorobanData`](https://stellar.github.io/js-stellar-sdk/TransactionBuilder.html#setSorobanData) method of the corresponding [`TransactionBuilder`](https://stellar.github.io/js-stellar-sdk/TransactionBuilder.html).
diff --git a/docs/learn/fundamentals/contract-development/contract-interactions/tests.mdx b/docs/learn/fundamentals/contract-development/contract-interactions/tests.mdx
index 688a4beec..a283b0d1f 100644
--- a/docs/learn/fundamentals/contract-development/contract-interactions/tests.mdx
+++ b/docs/learn/fundamentals/contract-development/contract-interactions/tests.mdx
@@ -1,10 +1,9 @@
 ---
-sidebar_position: 20
 title: Tests
 description: Interacting with contracts in tests
 ---
 
-[Debugging contracts](../errors-and-debugging/debugging.mdx) explains that it is much more convenient to debug using native code than Wasm. Given that you are testing native code, it is tempting to interact with your contract directly using function calls. If you attempt this approach, you will find that it doesn't always work. Function call interactions do not set the environment into the correct state for contract execution, so functions involving contract data and determining the current or invoking contract will not work.
+[Debugging contracts](../errors-and-debugging/debugging) explains that it is much more convenient to debug using native code than Wasm. Given that you are testing native code, it is tempting to interact with your contract directly using function calls. If you attempt this approach, you will find that it doesn't always work. Function call interactions do not set the environment into the correct state for contract execution, so functions involving contract data and determining the current or invoking contract will not work.
 
 When writing tests, it is important to always interact with contracts through contract invocation. In a production setting, contract invocation will execute Wasm bytecode loaded from the ledger. So how does this work if you are testing native code? You must register your contract with the environment, so it knows what functions are available and how to call them. While this sounds complex, the `contractimpl` procedural macro automatically generates almost all the code to do this. All you have to do is write a small [stub](https://github.com/stellar/soroban-token-contract/blob/42380647bb817bf01c739c19286f18be881e0e41/src/testutils.rs#L12-L15) to actually call the generated code, such as
 
diff --git a/docs/learn/fundamentals/contract-development/contract-interactions/transaction-simulation.mdx b/docs/learn/fundamentals/contract-development/contract-interactions/transaction-simulation.mdx
index 6a3ef6616..aecf8b841 100644
--- a/docs/learn/fundamentals/contract-development/contract-interactions/transaction-simulation.mdx
+++ b/docs/learn/fundamentals/contract-development/contract-interactions/transaction-simulation.mdx
@@ -1,12 +1,11 @@
 ---
-sidebar_position: 40
 title: Transaction Simulation
 description: Simulate a contract interaction contained in a Stellar transaction.
 ---
 
 ## Footprint
 
-As mentioned in the [persisting data](../storage/persisting-data.mdx) section, a contract can only load or store `CONTRACT_DATA` entries that are declared in a _footprint_ associated with its invocation.
+As mentioned in the [persisting data](../storage/persisting-data) section, a contract can only load or store `CONTRACT_DATA` entries that are declared in a _footprint_ associated with its invocation.
 
 A footprint is a set of ledger keys, each marked as either read-only or read-write. Read-only keys are available to the transaction for reading; read-write keys are available for reading, writing, or both.
 
@@ -20,7 +19,7 @@ In any event (whether successful or failing), the real transaction will execute
 
 ## Authorization
 
-Please refer to the [authorization overview](../authorization.mdx) and transaction authorization [section][auth-data] for general information on Soroban authorization: this section pertains specifically to how simulation works alongside authorization requirements.
+Please refer to the [authorization overview](../authorization) and transaction authorization [section][auth-data] for general information on Soroban authorization: this section pertains specifically to how simulation works alongside authorization requirements.
 
 Soroban's transaction [simulation mechanism][sim-tx] can be used to precompute the [`SorobanAuthorizedInvocation`][auth-invoke] trees that must be authorized by the `Address`es for all the `require_auth` checks to pass. It can be invoked in two different ways:
 
@@ -42,7 +41,7 @@ The recording auth mode is one option for [`simulateTransaction`][sim-tx]. Howev
 
 This is called running simulation with "enforcing" auth mode. This is basically equivalent to running the transaction on-chain (with possibly a slightly stale ledger state); hence, it requires all the signatures to be valid.
 
-From a developer's perspective, the difference between these is whether or not authorization entries are present in the [`InvokeHostFunction` operation](../../../../learn/fundamentals/transactions/list-of-operations.mdx#invoke-host-function) submitted to [`simulateTransaction`][sim-tx]. The [examples below](#typescript-utilities) highlight this distinction in detail, but the short story is that passing `auth` to [`Operation.invokeContractFunction`](https://stellar.github.io/js-stellar-sdk/Operation.html#.invokeContractFunction) (which is a convenience wrapper on [`invokeHostFunction`](https://stellar.github.io/js-stellar-sdk/Operation.html#.invokeHostFunction)) will imply enforcement mode.
+From a developer's perspective, the difference between these is whether or not authorization entries are present in the [`InvokeHostFunction` operation](../../../../learn/fundamentals/transactions/list-of-operations#invoke-host-function) submitted to [`simulateTransaction`][sim-tx]. The [examples below](#typescript-utilities) highlight this distinction in detail, but the short story is that passing `auth` to [`Operation.invokeContractFunction`](https://stellar.github.io/js-stellar-sdk/Operation.html#.invokeContractFunction) (which is a convenience wrapper on [`invokeHostFunction`](https://stellar.github.io/js-stellar-sdk/Operation.html#.invokeHostFunction)) will imply enforcement mode.
 
 ### SDK Usage
 
@@ -58,9 +57,9 @@ We'll cover three types of invocations:
 
 In this variant, we will leverage the "source account authorization" variant: this is when the source account on the transaction is the only one that needs to sign for the invocation (see the "source account" variant of [`SorobanCredentials`](https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-transaction.x#L586-L595)). In this scenario, the signature on the transaction itself directly implies signing the invocation.
 
-<CodeExample>
+<CodeGroup>
 
-```javascript
+```javascript JavaScript
 import {
   Asset,
   Keypair,
@@ -104,7 +103,7 @@ async function main() {
 main().catch((e) => console.error(e));
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Notice that, in contrast to the following example, we didn't need to do simulation separately. This is because we can sign the transaction as-is rather than needing to inspect its authorization entries.
 
@@ -112,9 +111,9 @@ Notice that, in contrast to the following example, we didn't need to do simulati
 
 In this variant, we'll extend the required signatures to more than one party, so the source account is no longer enough. We'll leverage the [`authorizeEntry` helper](https://stellar.github.io/js-stellar-sdk/global.html#authorizeEntry), which is designed specifically for making it easy to sign the entries returned by transaction simulation.
 
-<CodeExample>
+<CodeGroup>
 
-```typescript
+```typescript TypeScript
 import {
   Asset,
   Keypair,
@@ -191,7 +190,7 @@ async function main() {
 main().catch((e) => console.error(e));
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Alternatively, we could go a step lower in the stack and build the authorization entries ourselves using [`authorizeInvocation`](https://stellar.github.io/js-stellar-sdk/global.html#authorizeInvocation), giving us full control over the actual "call stack" that is being invoked. This can be useful if you want to authorize specific invocations, build the invocations yourself, or lower the network bandwidth you use when sharing entries for other parties to sign.
 
@@ -210,6 +209,6 @@ To keep things really simple, we won't do much coding. Instead, we'll just show
 +  const sendTx = await s.sendTransaction(resimTx);
 ```
 
-[auth-data]: stellar-transaction.mdx#authorization-data
+[auth-data]: stellar-transaction#authorization-data
 [auth-invoke]: https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-transaction.x#L558
-[sim-tx]: ../../../../data/apis/rpc/api-reference/methods/simulateTransaction.mdx
+[sim-tx]: ../../../../data/apis/rpc/api-reference/methods/simulateTransaction
diff --git a/docs/learn/fundamentals/contract-development/contract-lifecycle.mdx b/docs/learn/fundamentals/contract-development/contract-lifecycle.mdx
index 032429119..f4ce16c99 100644
--- a/docs/learn/fundamentals/contract-development/contract-lifecycle.mdx
+++ b/docs/learn/fundamentals/contract-development/contract-lifecycle.mdx
@@ -1,24 +1,10 @@
 ---
-sidebar_position: 50
 title: Contract Lifecycle
+og:title: "The process of developing, deploying, and maintaining smart contracts."
+og:description: "Learn about how smart contracts work from development to deployment to execution and then how to monitor and upgrade them."
 description: The process of developing, deploying, and maintaining smart contracts.
 ---
 
-<head>
-  <title>
-    {`The process of developing, deploying, and maintaining smart contracts.`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="The process of developing, deploying, and maintaining smart contracts."
-  />
-  <meta
-    property="og:description"
-    content="Learn about how smart contracts work from development to deployment to execution and then how to monitor and upgrade them."
-  />
-</head>
-
 ## Development
 
 Contract development can be done on a local computer with as little as 3 necessary components: an IDE, a copy of the Rust toolchain, and a copy of the Soroban SDK.
@@ -39,7 +25,7 @@ Before submitting to the network, developers should inspect the resulting Wasm b
 
 The SDK command-line utility can also build and submit the transaction deploying a Wasm contract to the network. Deployment requires sufficient network credentials to sign a transaction performing the deployment and pay its fees. Contracts should be deployed to test networks and thoroughly tested there before being deployed to the live network.
 
-:::note
+<Note>
 
 [Verify your contract on StellarExpert](https://stellar.expert/explorer/public/contract/validation).
 
@@ -47,7 +33,7 @@ This GitHub Actions process compiles and optimizes your Stellar contract, publis
 
 Once validated, StellarExpert displays a link to the exact GitHub commit so anyone can review the original source code and confirm it matches the deployed contract.
 
-:::
+</Note>
 
 ## Execution
 
@@ -67,4 +53,4 @@ Contracts can be monitored in two main ways: by observing events emitted during
 
 ## Upgrading contracts
 
-See the [Upgrading Contracts page](../../../build/guides/conventions/upgrading-contracts.mdx) for details on this.
+See the [Upgrading Contracts page](../../../build/guides/conventions/upgrading-contracts) for details on this.
diff --git a/docs/learn/fundamentals/contract-development/environment-concepts.mdx b/docs/learn/fundamentals/contract-development/environment-concepts.mdx
index 50920bf68..6b44fa649 100644
--- a/docs/learn/fundamentals/contract-development/environment-concepts.mdx
+++ b/docs/learn/fundamentals/contract-development/environment-concepts.mdx
@@ -1,25 +1,10 @@
 ---
-sidebar_position: 7
 title: Environment Concepts
+og:title: "The interface that defines objects, functions, and data available to smart contracts."
+og:description: "Learn about the interface environment that defines the objects, functions, data sources, and more that are available in smart contracts."
 description: The interface that defines objects, functions, and data available to smart contracts.
 ---
 
-<head>
-  <title>
-    {`The interface that defines objects, functions, and data available to smart
-    contracts.`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="The interface that defines objects, functions, and data available to smart contracts."
-  />
-  <meta
-    property="og:description"
-    content="Learn about the interface environment that defines the objects, functions, data sources, and more that are available in smart contracts."
-  />
-</head>
-
 The contract environment is an _interface_ that defines the facilities -- objects, functions, data sources, etc. -- available to contracts.
 
 ## Host and Guest
@@ -36,7 +21,7 @@ The on-chain guest environment is isolated inside a WebAssembly (Wasm) virtual m
 
 The use of a VM helps provide security against any potential guest-code misbehavior, to both host and other guest environments, as well as ensuring portability of guest code between hosts running on different types of hardware.
 
-When developing and testing contract code off-chain, it is possible to compile contract code to native machine code rather than Wasm bytecode, and to [run tests and debug contracts](./errors-and-debugging/debugging.mdx) against a local copy of the host environment by linking directly to it, rather than executing within a VM. This configuration runs much faster and provides much better debugging information, but is only possible locally, off-chain. On-chain deployed contracts are always Wasm.
+When developing and testing contract code off-chain, it is possible to compile contract code to native machine code rather than Wasm bytecode, and to [run tests and debug contracts](./errors-and-debugging/debugging) against a local copy of the host environment by linking directly to it, rather than executing within a VM. This configuration runs much faster and provides much better debugging information, but is only possible locally, off-chain. On-chain deployed contracts are always Wasm.
 
 WebAssembly is a relatively low-level VM, which means that it does not provide a very rich set of standard or "built-in" operations. In contrast to VMs like the JVM, it has no garbage collector (not even a memory allocator), no IO facilities, no standard data structures like lists, arrays, maps or strings, no concepts of objects or types at all besides basic machine types like 32 and 64-bit integers.
 
diff --git a/docs/learn/fundamentals/contract-development/errors-and-debugging/README.mdx b/docs/learn/fundamentals/contract-development/errors-and-debugging/README.mdx
deleted file mode 100644
index df38ff470..000000000
--- a/docs/learn/fundamentals/contract-development/errors-and-debugging/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Errors and Debugging
-sidebar_position: 40
----
-
-import DocCardList from "@theme/DocCardList";
-
-In-depth explanations and articles concerning specific topics of interest.
-
-<DocCardList />
diff --git a/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging-errors.mdx b/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging-errors.mdx
index 6df0cbe91..5353c888f 100644
--- a/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging-errors.mdx
+++ b/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging-errors.mdx
@@ -1,5 +1,4 @@
 ---
-sidebar_position: 30
 title: Debugging Contract Errors
 description: Debug and Understanding Soroban Errors through the General Transaction Cycle.
 ---
@@ -11,7 +10,7 @@ To understand how to debug Soroban errors, first we must understand how the erro
 The typical transaction submission process can be broken down into the following sequential steps, excluding external interactions like wallet interactions. Each step has its own set of potential errors:
 
 1. **Transaction Simulation (optional):**
-   - **What happens:** This step involves executing the RPC endpoint [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction.mdx). The endpoint executes a transaction in 'simulation' mode of host and records the necessary ledger entries, CPU instructions, required authorizations. The end result is akin to running transactions in Core with maxed-out resources, unrestricted ledger access, and no fees.
+   - **What happens:** This step involves executing the RPC endpoint [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction). The endpoint executes a transaction in 'simulation' mode of host and records the necessary ledger entries, CPU instructions, required authorizations. The end result is akin to running transactions in Core with maxed-out resources, unrestricted ledger access, and no fees.
    - **Common failures:** Errors typically involve exceeding the network limit or encountering contract logic issues.
 
 2. **Core Accepts the Transaction:**
@@ -26,7 +25,7 @@ The typical transaction submission process can be broken down into the following
    - **What happens:** Core executes the included transaction.
    - **Common failures:** This step has the widest range of potential errors. Failures could include accessing archived entries, resource depletion, accessing entries outside the specified footprint, or encountering logic failures within the contract.
 
-_For more information about fees, please visit [Fees, Resource Limits, and Metering](../../fees-resource-limits-metering.mdx#inclusion-fee)._
+_For more information about fees, please visit [Fees, Resource Limits, and Metering](../../fees-resource-limits-metering#inclusion-fee)._
 
 ## Detailed Soroban Errors
 
@@ -70,11 +69,11 @@ There are instances when the Core does not appear to include the transaction in
 | --- | --- | --- |
 | Transaction appears ‘stuck’ and is never applied | There is no direct error reporting here because the network can’t reasonably communicate which transaction that it drops (E.g. Node A has dropped the transaction doesn’t necessarily mean that some other Node B has dropped it). When querying against a data endpoint, the transaction might be reported as ‘pending’. | Introduce transaction time bounds on the client side. If a transaction hasn’t been applied within 1-2 minutes it’s highly unlikely that the network still remembers it. _It is strongly recommended thus that all transactions should include a time bound or ledger bound._ Having a bound allows the developer to re-submit the transaction after the time bound is exceeded and optionally bump the fee if the error persists. |
 
-:::info
+<Info>
 
 It is strongly recommended that all transactions should include a time bound or ledger bound.
 
-:::
+</Info>
 
 ### 4. Core Applies the Transaction to the Ledger
 
@@ -87,11 +86,11 @@ When an error occurs, the Core stores a few error-related fields in the transact
 - If the Core instance producing meta has Soroban diagnostics enabled (which it usually should), the meta will also contain diagnostic events with more detailed error information.
 - Note that there might be a few gaps in diagnostic event coverage. Since this is not a protocol change, Core may add more diagnostic events in future releases.
 
-:::note
+<Note>
 
 `$OPERATION` here refers to any one of the Soroban operations: `INVOKE_HOST_FUNCTION`, `RESTORE_FOOTPRINT`, and `EXTEND_FOOTPRINT_TTL`.
 
-:::
+</Note>
 
 | Error and Diagnostics | Explanation | Fix |
 | --- | --- | --- |
diff --git a/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging.mdx b/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging.mdx
index 1921a7591..4ebb9bfe6 100644
--- a/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging.mdx
+++ b/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging.mdx
@@ -1,22 +1,10 @@
 ---
-sidebar_position: 20
 title: Debugging Modes
+og:title: "Debug smart contracts natively and as WASM."
+og:description: "Compile smart contracts natively for local testing or into WASM for deployment in order to debug."
 description: Debug smart contracts natively and as WASM.
 ---
 
-<head>
-  <title>Debug smart contracts natively and as WASM.</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Debug smart contracts natively and as WASM."
-  />
-  <meta
-    property="og:description"
-    content="Compile smart contracts natively for local testing or into WASM for deployment in order to debug."
-  />
-</head>
-
 Soroban contracts are as much as possible regular Rust programs and can be debugged using the same tools you'd usually use.
 
 The debugging facilities available differ significantly depending on whether a contract is compiled natively for local testing, or compiled into Wasm for deployment.
@@ -46,11 +34,11 @@ If on the other hand you wish to compile for deployment, you must tell cargo to
 Building for Wasm will _disable_ many of the debugging facilities described above, typically for one of three reasons:
 
 - The Wasm VM simply can't (or the VM we've chosen doesn't) provide them.
-- The Wasm VM _could_ provide them but doing so would violate constraints of the [contract Rust dialect](../rust-dialect.mdx).
+- The Wasm VM _could_ provide them but doing so would violate constraints of the [contract Rust dialect](../rust-dialect).
 - The Wasm VM _could_ provide them but doing so would make the resulting Wasm code impractically large.
 
 While we encourage most testing to happen in local-testing mode, some problems will obviously only arise in deployment and some debugging facilities thus remain available even there:
 
 - A "sandbox" host with a mock-ledger that can read and write `CONTRACT_DATA` ledger entries to the local filesystem.
-- A general logging system that allows contracts to log values of the [shared host/guest "value" type](../environment-concepts.mdx), even in production.
+- A general logging system that allows contracts to log values of the [shared host/guest "value" type](../environment-concepts), even in production.
 - User-extensible `Error` codes that can be returned from any contract call to indicate problems.
diff --git a/docs/learn/fundamentals/contract-development/errors-and-debugging/errors.mdx b/docs/learn/fundamentals/contract-development/errors-and-debugging/errors.mdx
index d12e890de..718095d31 100644
--- a/docs/learn/fundamentals/contract-development/errors-and-debugging/errors.mdx
+++ b/docs/learn/fundamentals/contract-development/errors-and-debugging/errors.mdx
@@ -1,30 +1,21 @@
 ---
-sidebar_position: 10
 title: Generate Contract Errors
+og:title: "Generating errors from smart contracts."
+og:description: "Generating errors from smart contracts."
 description: Generating errors from smart contracts.
 ---
 
-<head>
-  <title>Generating errors from smart contracts.</title>
-  <meta charSet="utf-8" />
-  <meta property="og:title" content="Generating errors from smart contracts." />
-  <meta
-    property="og:description"
-    content="Generating errors from smart contracts."
-  />
-</head>
-
 There are a number of ways to generate errors in contracts.
 
 One way is error enum types, that are defined by contracts and that map errors to unsigned 32-bit integer values. They are usable as error values in the return types of contract functions.
 
-:::info
+<Info>
 
 The [errors example] demonstrates how to define your own error types.
 
-:::
+</Info>
 
-[errors example]: ../../../../build/smart-contracts/example-contracts/errors.mdx
+[errors example]: ../../../../build/smart-contracts/example-contracts/errors
 
 ## Error Enums
 
diff --git a/docs/learn/fundamentals/contract-development/errors-and-debugging/index.mdx b/docs/learn/fundamentals/contract-development/errors-and-debugging/index.mdx
new file mode 100644
index 000000000..26fbfbb40
--- /dev/null
+++ b/docs/learn/fundamentals/contract-development/errors-and-debugging/index.mdx
@@ -0,0 +1,22 @@
+---
+title: Errors and Debugging
+description: "In-depth explanations and articles concerning specific topics of interest."
+---
+
+<CardGroup cols={2}>
+  <Card title="Generate Contract Errors" icon="file-lines" href="/docs/learn/fundamentals/contract-development/errors-and-debugging/errors">
+
+    Generating errors from smart contracts.
+
+  </Card>
+  <Card title="Debugging Modes" icon="file-lines" href="/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging">
+
+    Debug smart contracts natively and as WASM.
+
+  </Card>
+  <Card title="Debugging Contract Errors" icon="file-lines" href="/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging-errors">
+
+    Debug and Understanding Soroban Errors through the General Transaction Cycle.
+
+  </Card>
+</CardGroup>
diff --git a/docs/learn/fundamentals/contract-development/index.mdx b/docs/learn/fundamentals/contract-development/index.mdx
new file mode 100644
index 000000000..3b5c779a0
--- /dev/null
+++ b/docs/learn/fundamentals/contract-development/index.mdx
@@ -0,0 +1,52 @@
+---
+title: Smart Contracts
+description: "Overview of Contract Development."
+---
+
+<CardGroup cols={2}>
+  <Card title="Overview" icon="file-lines" href="/docs/learn/fundamentals/contract-development/overview">
+
+    This section provides an overview of Stellar contracts, outlining their key concepts of smart contracts on the Stellar network.
+
+  </Card>
+  <Card title="Contract Rust Dialect" icon="file-lines" href="/docs/learn/fundamentals/contract-development/rust-dialect">
+
+    Differences between Soroban Rust and typical Rust programming.
+
+  </Card>
+  <Card title="Environment Concepts" icon="file-lines" href="/docs/learn/fundamentals/contract-development/environment-concepts">
+
+    The interface that defines objects, functions, and data available to smart contracts.
+
+  </Card>
+  <Card title="Contract Interactions" icon="box-archive" href="/docs/learn/fundamentals/contract-development/contract-interactions">
+
+    5 items
+
+  </Card>
+  <Card title="Types" icon="box-archive" href="/docs/learn/fundamentals/contract-development/types">
+
+    3 items
+
+  </Card>
+  <Card title="Storage" icon="box-archive" href="/docs/learn/fundamentals/contract-development/storage">
+
+    2 items
+
+  </Card>
+  <Card title="Authorization" icon="file-lines" href="/docs/learn/fundamentals/contract-development/authorization">
+
+    Authorization is the process of judging which operations "should" or "should not" be allowed to occur; it is about judging _permission_.
+
+  </Card>
+  <Card title="Errors and Debugging" icon="box-archive" href="/docs/learn/fundamentals/contract-development/errors-and-debugging">
+
+    3 items
+
+  </Card>
+  <Card title="Contract Lifecycle" icon="file-lines" href="/docs/learn/fundamentals/contract-development/contract-lifecycle">
+
+    The process of developing, deploying, and maintaining smart contracts.
+
+  </Card>
+</CardGroup>
diff --git a/docs/learn/fundamentals/contract-development/overview.mdx b/docs/learn/fundamentals/contract-development/overview.mdx
index 33792ebbc..2acf17f6e 100644
--- a/docs/learn/fundamentals/contract-development/overview.mdx
+++ b/docs/learn/fundamentals/contract-development/overview.mdx
@@ -1,11 +1,11 @@
 ---
-sidebar_position: 5
 title: Overview
+description: "This section provides an overview of Stellar contracts, outlining their key concepts of smart contracts on the Stellar network."
 ---
 
 This section provides an overview of Stellar contracts, outlining their key concepts of smart contracts on the Stellar network.
 
-Learn to write your first Stellar smart contract in the [Getting Started Guide](../../../build/smart-contracts/getting-started/setup.mdx).
+Learn to write your first Stellar smart contract in the [Getting Started Guide](../../../build/smart-contracts/getting-started/setup).
 
 ## Smart Contract in WebAssembly (Wasm)
 
@@ -25,15 +25,17 @@ flowchart LR
     A[my instance] & B[your instance]--> C[contract Wasm]
 ```
 
-:::info[Important Takeway]
+<Info>
+
+**Important Takeway**
 
 The Wasm bytecode itself is stored separately from the deployed contract instances. This separation allows multiple contract instances to reference the same Wasm executable while maintaining their own contract storage, state, and configurations.
 
-:::
+</Info>
 
 ## Contract Storage
 
-In addition to the ledger entries that are created during the contract upload/deploy process, each contract can create and access its own set of ledger entries. These ledger entries (as well as the contract code and the contract instance ledger entries) are subject to [state archival](./storage/state-archival.mdx) lifetimes, or TTL (time-to-live) behavior. Each storage type has distinct fee structures, TTL (time-to-live) behavior, and is designed to store specific types of data. Using the incorrect storage can lead to logical errors in your application, in addition to impacting costs.
+In addition to the ledger entries that are created during the contract upload/deploy process, each contract can create and access its own set of ledger entries. These ledger entries (as well as the contract code and the contract instance ledger entries) are subject to [state archival](./storage/state-archival) lifetimes, or TTL (time-to-live) behavior. Each storage type has distinct fee structures, TTL (time-to-live) behavior, and is designed to store specific types of data. Using the incorrect storage can lead to logical errors in your application, in addition to impacting costs.
 
 | **Attribute** | **Temporary Storage** | **Persistent Storage** | **Instance Storage** |
 | --- | --- | --- | --- |
@@ -116,16 +118,16 @@ Stellar’s Contract Spec shares many similarities with Ethereum’s ABI but als
 
 [The Stellar CLI](https://github.com/stellar/stellar-cli) provides a command to generate a contract spec from a contract's source code. This process is easy but requires you to have the Wasm binary of the contract.
 
-Sometimes, you may not have access to the contract's source code or the ability to compile it. In such cases, you must use the [`stellar contract fetch`](../../../tools/cli/stellar-cli.mdx#stellar-contract-fetch) command to download the contract's Wasm binary and generate the spec.
+Sometimes, you may not have access to the contract's source code or the ability to compile it. In such cases, you must use the [`stellar contract fetch`](../../../tools/cli/stellar-cli#stellar-contract-fetch) command to download the contract's Wasm binary and generate the spec.
 
-Finally, we use the [`stellar bindings`](../../../tools/cli/stellar-cli.mdx#stellar-contract-bindings-json) command to generate the contract spec from the Wasm binary.
+Finally, we use the [`stellar bindings`](../../../tools/cli/stellar-cli#stellar-contract-bindings-json) command to generate the contract spec from the Wasm binary.
 
 The Stellar Lab has a [Contract Explorer](https://lab.stellar.org/smart-contracts/contract-explorer) also provides the ability to view and to download a contract's contract spec.
 
-:::note
+<Note>
 
-Having read the introduction of a Stellar contract, let's try to write a smart contract by following the [Getting Started guide](../../../build/smart-contracts/getting-started/README.mdx).
+Having read the introduction of a Stellar contract, let's try to write a smart contract by following the [Getting Started guide](/docs/build/smart-contracts/getting-started).
 
-:::
+</Note>
 
 [`scspecentry`]: https://github.com/stellar/stellar-xdr/blob/next/Stellar-contract-spec.x
diff --git a/docs/learn/fundamentals/contract-development/rust-dialect.mdx b/docs/learn/fundamentals/contract-development/rust-dialect.mdx
index 36ec03965..f034df070 100644
--- a/docs/learn/fundamentals/contract-development/rust-dialect.mdx
+++ b/docs/learn/fundamentals/contract-development/rust-dialect.mdx
@@ -1,5 +1,4 @@
 ---
-sidebar_position: 6
 title: Contract Rust Dialect
 description: Differences between Soroban Rust and typical Rust programming.
 ---
@@ -10,11 +9,11 @@ For this reason it makes sense to consider code written for contracts to be a _d
 
 These constraints and priorities are _similar_ to those encountered when writing Rust code for "embedded systems", and the tools, libraries and techniques used in the "contract dialect" are frequently borrowed from the [Rust embedded systems community](https://docs.rust-embedded.org/book/index.html), and by default contracts are recommended to be built with the [`#[no_std]` mode](https://docs.rust-embedded.org/book/intro/no-std.html) that excludes the Rust standard library entirely, relying on the smaller underlying `core` library instead.
 
-:::note
+<Note>
 
-These constraints and priorities are **not enforced when building in local-testing mode**, and in fact local contract tests will _frequently_ use facilities -- to generate test input, inspect test output, and guide testing -- that are not supported in the deployment guest environment. Developers **must understand** the difference between code that is compiled-in to Wasm modules for deployment and code that is conditionally compiled for testing. See [debugging contracts](./errors-and-debugging/debugging.mdx) for more details.
+These constraints and priorities are **not enforced when building in local-testing mode**, and in fact local contract tests will _frequently_ use facilities -- to generate test input, inspect test output, and guide testing -- that are not supported in the deployment guest environment. Developers **must understand** the difference between code that is compiled-in to Wasm modules for deployment and code that is conditionally compiled for testing. See [debugging contracts](./errors-and-debugging/debugging) for more details.
 
-:::
+</Note>
 
 The "contract dialect" has the following characteristics:
 
@@ -40,7 +39,7 @@ This restriction is due to the limited ability of Wasm to support code-sharing:
 
 Many instances where dynamic memory allocation might _seem_ to be required can also be addressed just as well with a library such as [heapless](https://docs.rs/heapless/latest/heapless). This library (and others of its kind) provide data structures with familiar APIs that _appear_ dynamic, but are actually implemented in terms of a single stack or static allocation, with a fixed maximum size established at construction: attempts to grow the dynamic size beyond the maximum size simply fail. In the context of a contract, this can sometimes be preferable behavior, and avoids the question of dynamic allocation entirely.
 
-## Non-standard I/O
+## Non-standard I/O {#non-standard-io}
 
 All standard I/O facilities and access to the operating system that a typical Rust program would expect to perform using the Rust standard library is prohibited; programs that try to import such functions from the host through (for example) the WASI interface will fail to instantiate, since they refer to functions not provided by the host.
 
@@ -66,11 +65,11 @@ Host objects have significantly different semantics than typical Rust data struc
 
 In particular: host objects are **immutable**, and any "modification" to a host object returns a **full new copy** of the object, leaving the initial one unchanged. For the most part this distinction is hidden through wrappers in the SDK, such that objects like `Map` or `Vec` appear to the contract programmer to be uniquely owned mutable values similar to Rust's standard library types, but the underlying host objects are immutable, so have different performance characteristics. Specifically: cloning such an object is O(1), whereas any modification is O(N). Since most host objects are typically very small, the O(N) cost of modification is typically cheaper than any alternative implementation involving shared substructures.
 
-:::note
+<Note>
 
 These container types `Vec` and `Map` should _not_ be used for managing large or unbounded collections of data. For such cases, contracts should store data in multiple separate ledger entries, each with its own unique contract-defined key. Doing so also limits the IO cost of a contract to only the entries it accesses, and furthermore allows concurrent modification of entries with separate keys from separate transactions.
 
-:::
+</Note>
 
 ## Limited WebAssembly features
 
@@ -80,20 +79,19 @@ Soroban intentionally limits which WebAssembly features it supports, to minimize
 
 New Soroban contracts should be built with Rust `v1.84.0` or later, and use the `wasm32v1-none` target. The easiest way to do this is with `stellar contract build` from [stellar-cli], which targets `wasm32v1-none` and applies all required build settings automatically.
 
-:::warning
+<Warning>
 
 The `wasm32-unknown-unknown` target is **not supported** for building Soroban contracts when using Rust 1.82 or newer. On those versions, `wasm32-unknown-unknown` enables WebAssembly features (reference-types, multi-value) that the Soroban runtime does not support. Attempting to build a contract for `wasm32-unknown-unknown` with Rust 1.82+ will produce a build error from the SDK's build script.
 
 Use `wasm32v1-none` (available with Rust 1.84+) as the build target, or use `stellar contract build` which selects the correct target automatically.
 
-:::
-
-:::note
+</Warning>
+<Note>
 
 The `wasm32v1-none` target does not, by default, ship with a version of the `std` library at all. When adding the `wasm32v1-none` target, it was decided that these sorts of stubs were not of any benefit to users.
 
 The `wasm32v1-none` target _does_ include a copy of the `alloc` crate, which contains most of the _containers_ (such as vectors and maps) that are re-exported by `std`. For example, rather than using `std::vec::Vec` one can use `alloc::vec::Vec`, which is the same code under a different name. But as mentioned above in the section on dynamic memory allocation, generally Soroban contracts should avoid `alloc` as well: a crate like `heapless` will usually perform better.
 
-:::
+</Note>
 
 [stellar-cli]: https://github.com/stellar/stellar-cli
diff --git a/docs/learn/fundamentals/contract-development/storage/README.mdx b/docs/learn/fundamentals/contract-development/storage/README.mdx
deleted file mode 100644
index 84004720b..000000000
--- a/docs/learn/fundamentals/contract-development/storage/README.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Storage
-sidebar_position: 10
----
-
-import DocCardList from "@theme/DocCardList";
-
-<DocCardList />
diff --git a/docs/learn/fundamentals/contract-development/storage/index.mdx b/docs/learn/fundamentals/contract-development/storage/index.mdx
new file mode 100644
index 000000000..e21083267
--- /dev/null
+++ b/docs/learn/fundamentals/contract-development/storage/index.mdx
@@ -0,0 +1,17 @@
+---
+title: Storage
+description: "Overview of Storage."
+---
+
+<CardGroup cols={2}>
+  <Card title="Persisting Data" icon="file-lines" href="/docs/learn/fundamentals/contract-development/storage/persisting-data">
+
+    Store and access smart contract data.
+
+  </Card>
+  <Card title="State Archival" icon="file-lines" href="/docs/learn/fundamentals/contract-development/storage/state-archival">
+
+    Smart contract state archival.
+
+  </Card>
+</CardGroup>
diff --git a/docs/learn/fundamentals/contract-development/storage/persisting-data.mdx b/docs/learn/fundamentals/contract-development/storage/persisting-data.mdx
index b9bef0873..ad0715f7d 100644
--- a/docs/learn/fundamentals/contract-development/storage/persisting-data.mdx
+++ b/docs/learn/fundamentals/contract-development/storage/persisting-data.mdx
@@ -1,19 +1,10 @@
 ---
-sidebar_position: 10
 title: Persisting Data
+og:title: "Store and access smart contract data."
+og:description: "Store and access smart contract data."
 description: Store and access smart contract data.
 ---
 
-<head>
-  <title>Store and access smart contract data.</title>
-  <meta charSet="utf-8" />
-  <meta property="og:title" content="Store and access smart contract data." />
-  <meta
-    property="og:description"
-    content="Store and access smart contract data."
-  />
-</head>
-
 ## Ledger entries
 
 Contracts can access ledger entries of type `CONTRACT_DATA`. Host functions are provided to probe, read, write, and delete `CONTRACT_DATA` ledger entries.
@@ -34,7 +25,7 @@ There is no access control for TTL extension operations. Any user may invoke `Ex
 
 A `CONTRACT_DATA` ledger entry is read or written from the ledger in its entirety; there is no way to read or write "only a part" of a `CONTRACT_DATA` ledger entry. There is also a fixed overhead cost to accessing any `CONTRACT_DATA` ledger entry. Contracts are therefore responsible for dividing logically "large" data structures into "pieces" with an appropriate size granularity, to use for reading and writing. If pieces are too large there may be unnecessary costs paid for reading and writing unused data, as well as unnecessary contention in parallel execution; but if pieces are too small there may be unnecessary costs paid for the fixed overhead of each entry.
 
-An unbounded collection is the usual way to get this wrong. A `Vec` or `Map` held under a single key is read and written in full on every update, so its cost grows with the whole collection, and the write fails once the entry passes the maximum contract-data entry size. Every caller that changes the collection writes that same entry, so their transactions contend and execute sequentially. A collection that contract callers can grow has no natural bound, so give each item its own ledger entry instead. The [storage strategies guide](../../../../build/guides/storage/storage-strategies.mdx) shows the layouts that do this, and its [red flags in review](../../../../build/guides/storage/storage-strategies.mdx#-red-flags-in-review) list the storage mistakes to look for.
+An unbounded collection is the usual way to get this wrong. A `Vec` or `Map` held under a single key is read and written in full on every update, so its cost grows with the whole collection, and the write fails once the entry passes the maximum contract-data entry size. Every caller that changes the collection writes that same entry, so their transactions contend and execute sequentially. A collection that contract callers can grow has no natural bound, so give each item its own ledger entry instead. The [storage strategies guide](../../../../build/guides/storage/storage-strategies) shows the layouts that do this, and its [red flags in review](../../../../build/guides/storage/storage-strategies#-red-flags-in-review) list the storage mistakes to look for.
 
 ## Footprints and parallel contention
 
diff --git a/docs/learn/fundamentals/contract-development/storage/state-archival.mdx b/docs/learn/fundamentals/contract-development/storage/state-archival.mdx
index fd513f588..e57ec1c5f 100644
--- a/docs/learn/fundamentals/contract-development/storage/state-archival.mdx
+++ b/docs/learn/fundamentals/contract-development/storage/state-archival.mdx
@@ -1,22 +1,13 @@
 ---
-sidebar_position: 20
 title: State Archival
+og:title: "Smart contract state archival."
+og:description: "Learn about how state archival works on the Soroban smart contract platform."
 description: Smart contract state archival.
 ---
 
-<head>
-  <title>Smart contract state archival.</title>
-  <meta charSet="utf-8" />
-  <meta property="og:title" content="Smart contract state archival." />
-  <meta
-    property="og:description"
-    content="Learn about how state archival works on the Soroban smart contract platform."
-  />
-</head>
-
 Contract data is made up of three different types: `Persistent`, `Temporary`, and `Instance`. In a contract, these are accessed with `env.storage().persistent()`, `env.storage().temporary()`, and `env.storage().instance()` respectively; see the [`storage()` docs](https://docs.rs/soroban-sdk/latest/soroban_sdk/storage/struct.Storage.html).
 
-Learn about choosing the right storage for your use case in this [How-To Guide](../../../../build/guides/storage/choosing-the-right-storage.mdx) and other state archival related guides [here](../../../../build/guides/archival).
+Learn about choosing the right storage for your use case in this [How-To Guide](../../../../build/guides/storage/choosing-the-right-storage) and other state archival related guides [here](../../../../build/guides/archival).
 
 All contract data has a Time To Live (TTL) that must be periodically extended. If an entry's TTL is not periodically extended, the entry's TTL will eventually go to 0 and either become "archived" or permanently deleted depending on the storage type. Each type of storage functions similarly, but has different fees and archival behavior:
 
@@ -56,11 +47,11 @@ The general usage and interface are identical for all storage types. They differ
 
 Starting in Protocol 23 ([CAP-66: Soroban In-Memory Read Resource](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0066.md#automatic-entry-restoration)), archived `Persistent` or `Instance` contract entries can be automatically restored before a host function runs, but only if they're included in the transaction's restore list. In practice, this list is usually populated by the contract invocation simulation (via the Stellar RPC): if the simulation detects an access to an archived entry, it adds that entry to the restore list. When the resulting `InvokeHostFunction` operation executes, those entries are restored first, and then the host function runs; normal rent and fees still apply.
 
-:::important
+<Warning>
 
 If you build a transaction manually without running simulation (and therefore don’t include all needed archived entries in the restore list), automatic restoration will not occur and the transaction will fail when it tries to access those archived entries.
 
-:::
+</Warning>
 
 ## Contract Data Best Practices
 
@@ -94,7 +85,7 @@ If you would like to extend the contract code or contract instance separately, y
 Here are some important points to keep in mind when it comes to archived entries -
 
 1. A Soroban transaction that has a key to an archived Persistent entry in the footprint, but not in the transaction's restore list, will fail immediately during the apply stage prior to contract execution. It does not matter if the contract itself was going to access the entry. (If the entry _is_ included in the restore list, it's [automatically restored](#contract-data-automatic-restoration) before the host function runs instead.)
-2. Due to the previous point that archived entries can never make it into smart contract logic, there is no reason to write code in your contract to handle archived entries. The same applies to contract test cases - while you may want to write tests that check if your extension logic is correct, you don't need to write archival tests because the transaction will fail before getting to the contract. It is possible though to access an archived entry in a Soroban test case, in which case the host will panic. You can read more about this in [Test TTL Extensions](../../../../build/guides/archival/test-ttl-extension.mdx).
+2. Due to the previous point that archived entries can never make it into smart contract logic, there is no reason to write code in your contract to handle archived entries. The same applies to contract test cases - while you may want to write tests that check if your extension logic is correct, you don't need to write archival tests because the transaction will fail before getting to the contract. It is possible though to access an archived entry in a Soroban test case, in which case the host will panic. You can read more about this in [Test TTL Extensions](../../../../build/guides/archival/test-ttl-extension).
 3. Archived persistent entries can never be re-created. They must instead be restored. Once they are restored, then they can be modified or deleted.
 
 ## Terms and Semantics
@@ -157,7 +148,7 @@ liveUntilLedger that is large enough.
 
 #### Transaction resources
 
-`ExtendFootprintTTLOp` is a Soroban operation, and therefore must be the only operation in a transaction. The transaction also needs to populate `SorobanTransactionData` transaction extension explained [here](../contract-interactions/stellar-transaction.mdx#transaction-resources). To fill out `SorobanResources`, use the transaction simulation mentioned in the provided link, or make sure `diskReadBytes` covers the serialized size of every entry in the `readOnly` set.
+`ExtendFootprintTTLOp` is a Soroban operation, and therefore must be the only operation in a transaction. The transaction also needs to populate `SorobanTransactionData` transaction extension explained [here](../contract-interactions/stellar-transaction#transaction-resources). To fill out `SorobanResources`, use the transaction simulation mentioned in the provided link, or make sure `diskReadBytes` covers the serialized size of every entry in the `readOnly` set.
 
 ### RestoreFootprintOp
 
@@ -187,9 +178,9 @@ The restored entry will have its live until ledger extended to the [minimum] the
 
 [minimum]: https://github.com/stellar/stellar-core/blob/2109a168a895349f87b502ae3d182380b378fa47/src/ledger/NetworkConfig.h#L77-L78
 
-#### Transaction resources
+#### Transaction resources {#transaction-resources-1}
 
-`RestoreFootprintOp` is a Soroban operation, and therefore must be the only operation in a transaction. The transaction also needs to populate `SorobanTransactionData` transaction extension explained [here](../contract-interactions/stellar-transaction.mdx#transaction-resources). To fill out `SorobanResources`, use the transaction simulation mentioned in the provided link, or make sure `writeBytes` includes the key and entry size of every entry in the `readWrite` set and make sure `extendedMetaDataSizeBytes` is at least double of `writeBytes`.
+`RestoreFootprintOp` is a Soroban operation, and therefore must be the only operation in a transaction. The transaction also needs to populate `SorobanTransactionData` transaction extension explained [here](../contract-interactions/stellar-transaction#transaction-resources). To fill out `SorobanResources`, use the transaction simulation mentioned in the provided link, or make sure `writeBytes` includes the key and entry size of every entry in the `readWrite` set and make sure `extendedMetaDataSizeBytes` is at least double of `writeBytes`.
 
 ---
 
@@ -199,15 +190,15 @@ We've done our best to build tooling around state archival in both the Stellar R
 
 ### Overview
 
-:::info
+<Info>
 
 The manual operation (`RestoreFootprintOp`) is, for the most part, no longer needed starting in Protocol 23, as archived entries included in a transaction's [restore list](#contract-data-automatic-restoration) (usually populated during transaction simulation) are automatically restored when the `InvokeHostFunctionOp` executes. `RestoreFootprintOp` can be used in rare use cases [described above](#restorefootprintop).
 
-:::
+</Info>
 
 Both restoring and extending the TTL of ledger entries follows a three-step process regardless of their nature (contract data, instances, etc.):
 
-1. **Identify the ledger entries**. This usually means acquiring them from a Stellar RPC server as part of your initial transaction simulation (see the [transaction simulation docs](../contract-interactions/transaction-simulation.mdx) and the [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction.mdx) RPC method).
+1. **Identify the ledger entries**. This usually means acquiring them from a Stellar RPC server as part of your initial transaction simulation (see the [transaction simulation docs](../contract-interactions/transaction-simulation) and the [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction) RPC method).
 
 2. **Prepare your operation**. This means describing the ledger entries within the corresponding operation (i.e., `ExtendFootprintTTLOp` or `RestoreFootprintOp`) and its ledger footprint (the `SorobanTransactionData` field), then simulating it to fill out fee and resource usage information (when restoring, you usually have simulation results already).
 
@@ -222,7 +213,7 @@ Remember, though, that any combination of these scenarios can occur in reality.
 
 ### Preparation
 
-In order to help the scaffolding of the code, we'll reuse the rudimentary, retry-enabled transaction polling function `submitTx` which we outlined in [another guide](../../../../build/guides/transactions/submit-transaction-wait-js.mdx).
+In order to help the scaffolding of the code, we'll reuse the rudimentary, retry-enabled transaction polling function `submitTx` which we outlined in [another guide](../../../../build/guides/transactions/submit-transaction-wait-js).
 
 In the following code, we will also leverage [`Server.prepareTransaction`](https://stellar.github.io/js-stellar-sdk/module-rpc.Server.html#prepareTransaction). This is a helpful method that, given a transaction, will simulate it, then amend the transaction with the simulation results (fees, etc.) and return that. Then, it can just be signed and submitted. We will also use [`SorobanDataBuilder`](https://stellar.github.io/js-stellar-sdk/SorobanDataBuilder.html), a convenient abstraction that lets us use a [builder pattern](https://en.wikipedia.org/wiki/Builder_pattern) to set the appropriate storage footprints for a transaction.
 
@@ -327,7 +318,7 @@ flowchart LR
 
 We need **both** to be live for our contract calls to work.
 
-Let's work through how these can be recovered. The recovery process is slightly different: while we don't need simulation to figure out the footprints, we do need to do an additional ledger entry fetch. We can leverage [`Contract.getFootprint()`](https://stellar.github.io/js-stellar-sdk/Contract.html#getFootprint) to get the ledger key used by a given contract instance, but that won't give us its backing WASM code. For that, we'll recreate [this example](../../../../data/apis/rpc/api-reference/methods/getLedgerEntries.mdx#requesting-a-contracts-wasm-code) here.
+Let's work through how these can be recovered. The recovery process is slightly different: while we don't need simulation to figure out the footprints, we do need to do an additional ledger entry fetch. We can leverage [`Contract.getFootprint()`](https://stellar.github.io/js-stellar-sdk/Contract.html#getFootprint) to get the ledger key used by a given contract instance, but that won't give us its backing WASM code. For that, we'll recreate [this example](../../../../data/apis/rpc/api-reference/methods/getLedgerEntries#requesting-a-contracts-wasm-code) here.
 
 We also need simulation to figure out the fees for our restoration. This, however, can be easily covered by the SDK's [`Server.prepareTransaction`](https://stellar.github.io/js-stellar-sdk/module-rpc.Server.html#prepareTransaction) helper, which will do simulation and assembly for us:
 
diff --git a/docs/learn/fundamentals/contract-development/transaction-lifecycle.mdx b/docs/learn/fundamentals/contract-development/transaction-lifecycle.mdx
index 0b29f20f6..c3e95632b 100644
--- a/docs/learn/fundamentals/contract-development/transaction-lifecycle.mdx
+++ b/docs/learn/fundamentals/contract-development/transaction-lifecycle.mdx
@@ -1,5 +1,4 @@
 ---
-sidebar_position: 50
 title: Transaction Lifecycle
 description: here's how a transaction works, and stuff.
 draft: true
diff --git a/docs/learn/fundamentals/contract-development/types/README.mdx b/docs/learn/fundamentals/contract-development/types/README.mdx
deleted file mode 100644
index 942bad08e..000000000
--- a/docs/learn/fundamentals/contract-development/types/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Types
-sidebar_position: 9
----
-
-import DocCardList from "@theme/DocCardList";
-
-Learn about the types and data structures available to developers in Soroban smart contracts.
-
-<DocCardList />
diff --git a/docs/learn/fundamentals/contract-development/types/built-in-types.mdx b/docs/learn/fundamentals/contract-development/types/built-in-types.mdx
index b3f43d223..66293438e 100644
--- a/docs/learn/fundamentals/contract-development/types/built-in-types.mdx
+++ b/docs/learn/fundamentals/contract-development/types/built-in-types.mdx
@@ -1,32 +1,20 @@
 ---
-sidebar_position: 10
 title: Built-In Types
+og:title: "Built-in types used as smart contract inputs and outputs."
+og:description: "Learn about the built-in types that are available in Soroban smart contracts, including primitive types, symbols, bytes, strings, vecs, maps, and addresses."
 description: Built-in types used as smart contract inputs and outputs.
 ---
 
-<head>
-  <title>Built-in types used as smart contract inputs and outputs.</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Built-in types used as smart contract inputs and outputs."
-  />
-  <meta
-    property="og:description"
-    content="Learn about the built-in types that are available in Soroban smart contracts, including primitive types, symbols, bytes, strings, vecs, maps, and addresses."
-  />
-</head>
-
 Built-in types are available to all contracts for use as contract function inputs and outputs, and are defined by the [environment] and the [Rust SDK].
 
-[environment]: ../environment-concepts.mdx
-[rust sdk]: ../../../../tools/sdks/contract-sdks.mdx#soroban-rust-sdk
+[environment]: ../environment-concepts
+[rust sdk]: ../../../../tools/sdks/contract-sdks#soroban-rust-sdk
 
-:::tip
+<Tip>
 
 Custom types like structs, enums, and unions are also supported. See Custom Types.
 
-:::
+</Tip>
 
 ## Primitive Types
 
@@ -86,7 +74,7 @@ Address is a universal opaque identifier to use in contracts. It may represent a
 
 Address can be used as a contract function input argument (for example, to identify the payment recipient), as a data key (for example, to store the balance), as the authentication & authorization source (for example, to authorize a token transfer) etc.
 
-See [authorization documentation](../authorization.mdx) for more details on how to use the `Address` type.
+See [authorization documentation](../authorization) for more details on how to use the `Address` type.
 
 ## Option (`Option`)
 
diff --git a/docs/learn/fundamentals/contract-development/types/custom-types.mdx b/docs/learn/fundamentals/contract-development/types/custom-types.mdx
index 0388f6f70..b689705a5 100644
--- a/docs/learn/fundamentals/contract-development/types/custom-types.mdx
+++ b/docs/learn/fundamentals/contract-development/types/custom-types.mdx
@@ -1,37 +1,24 @@
 ---
-sidebar_position: 20
 title: Custom Types
+og:title: "Struct, union, and enum types defined by contracts."
+og:description: "View the struct, union, and enum types that are usable as contract inputs, contract outputs, or for storage."
 description: Struct, union, and enum types defined by contracts.
 ---
 
-<head>
-  <title>Struct, union, and enum types defined by contracts.</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Struct, union, and enum types defined by contracts."
-  />
-  <meta
-    property="og:description"
-    content="View the struct, union, and enum types that are usable as contract inputs, contract outputs, or for storage."
-  />
-</head>
-
 Custom types are struct, union, and enum types defined by contracts. They are usable everywhere primitives types can be used: as contract inputs, outputs, or for storage.
 
-:::info
+<Info>
 
 The [custom types example] demonstrates how to define your own types.
 
-[custom types example]: ../../../../build/smart-contracts/example-contracts/custom-types.mdx
-
-:::
+[custom types example]: ../../../../build/smart-contracts/example-contracts/custom-types
 
-:::info
+</Info>
+<Info>
 
-Error enum types are another type contracts can define that have some unique behaviors. See [Errors](../errors-and-debugging/errors.mdx) for more information.
+Error enum types are another type contracts can define that have some unique behaviors. See [Errors](../errors-and-debugging/errors) for more information.
 
-:::
+</Info>
 
 ## Structs (with Named Fields)
 
diff --git a/docs/learn/fundamentals/contract-development/types/fully-typed-contracts.mdx b/docs/learn/fundamentals/contract-development/types/fully-typed-contracts.mdx
index bfd616bd3..ebda7ff69 100644
--- a/docs/learn/fundamentals/contract-development/types/fully-typed-contracts.mdx
+++ b/docs/learn/fundamentals/contract-development/types/fully-typed-contracts.mdx
@@ -1,29 +1,13 @@
 ---
-sidebar_position: 30
 title: "Fully-Typed Contracts"
-desctiption: Smart contract WASM files contain a machine-readable description of the interface type.
-sidebar_label: Fully-Typed Contracts
+og:title: "Smart contract WASM files contain a machine-readable description of the interface type."
+og:description: "All smart contract interface types will be available on-chain right away with no secondary API calls to external services, no secondary API management, and more."
+description: Smart contract WASM files contain a machine-readable description of the interface type.
 ---
 
-<head>
-  <title>
-    {`Smart contract WASM files contain a machine-readable description of the
-    interface type.`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Smart contract WASM files contain a machine-readable description of the interface type."
-  />
-  <meta
-    property="og:description"
-    content="All smart contract interface types will be available on-chain right away with no secondary API calls to external services, no secondary API management, and more."
-  />
-</head>
-
-When you compile a contract created with [soroban-sdk](../../../../tools/sdks/contract-sdks.mdx#soroban-rust-sdk), the Wasm file ends up with a [custom section](https://webassembly.github.io/spec/core/appendix/custom.html) containing a machine-readable description of your contract's interface types, sometimes called its [spec](https://github.com/stellar/rs-soroban-sdk/tree/main/soroban-spec) or its [API](https://github.com/stellar/soroban-docs/pull/381#issuecomment-1507283476). This is similar to [ABIs](https://www.quicknode.com/guides/ethereum-development/smart-contracts/what-is-an-abi) in Ethereum, except that Soroban will store every single one of them on-chain from day one, and they include comments from the contract's author.
-
-These interface types are formatted using [XDR](../../../fundamentals/data-format/xdr.mdx), a data format used widely throughout Stellar. It can be tricky to create or consume XDR manually, but tooling can fetch these interface types to make your life easier. [Stellar CLI](../../../../tools/cli/README.mdx#cli) and [Stellar SDK](../../../../tools/sdks/client-sdks.mdx#javascript-sdk) are two such tools to do so. Let's look at each.
+When you compile a contract created with [soroban-sdk](../../../../tools/sdks/contract-sdks#soroban-rust-sdk), the Wasm file ends up with a [custom section](https://webassembly.github.io/spec/core/appendix/custom.html) containing a machine-readable description of your contract's interface types, sometimes called its [spec](https://github.com/stellar/rs-soroban-sdk/tree/main/soroban-spec) or its [API](https://github.com/stellar/soroban-docs/pull/381#issuecomment-1507283476). This is similar to [ABIs](https://www.quicknode.com/guides/ethereum-development/smart-contracts/what-is-an-abi) in Ethereum, except that Soroban will store every single one of them on-chain from day one, and they include comments from the contract's author.
+
+These interface types are formatted using [XDR](../../../fundamentals/data-format/xdr), a data format used widely throughout Stellar. It can be tricky to create or consume XDR manually, but tooling can fetch these interface types to make your life easier. [Stellar CLI](/docs/tools/cli#cli) and [Stellar SDK](../../../../tools/sdks/client-sdks#javascript-sdk) are two such tools to do so. Let's look at each.
 
 ## Stellar CLI: `stellar contract invoke`
 
@@ -68,13 +52,13 @@ Options:
 
 Like any other CLI, you can also get help for any of these subcommands. Omitting everything before the `--` in the previous command, this would look like: `… -- balance --help`. Stellar CLI again fetches the on-chain interface types, this time using it to generate a full list of all arguments to the function, and even generates examples.
 
-:::tip
+<Tip>
 
 If you're unfamiliar with the `--` double dash separator, this is a pattern used by other CLIs. Everything after the double dash, sometimes called the [slop](https://github.com/clap-rs/clap/issues/971), gets passed to the child process. An example of other CLIs that make use of this are `npm run` and `cargo run`.
 
-:::
+</Tip>
 
-## Stellar JS SDK: `contract.Client`
+## Stellar JS SDK: `contract.Client` {#stellar-js-sdk-contractclient}
 
 To create a contract client for the same contract as shown for `contract invoke` above, you would use this JavaScript:
 
diff --git a/docs/learn/fundamentals/contract-development/types/index.mdx b/docs/learn/fundamentals/contract-development/types/index.mdx
new file mode 100644
index 000000000..4f439a9e7
--- /dev/null
+++ b/docs/learn/fundamentals/contract-development/types/index.mdx
@@ -0,0 +1,22 @@
+---
+title: Types
+description: "Learn about the types and data structures available to developers in Soroban smart contracts."
+---
+
+<CardGroup cols={2}>
+  <Card title="Built-In Types" icon="file-lines" href="/docs/learn/fundamentals/contract-development/types/built-in-types">
+
+    Built-in types used as smart contract inputs and outputs.
+
+  </Card>
+  <Card title="Custom Types" icon="file-lines" href="/docs/learn/fundamentals/contract-development/types/custom-types">
+
+    Struct, union, and enum types defined by contracts.
+
+  </Card>
+  <Card title="Fully-Typed Contracts" icon="file-lines" href="/docs/learn/fundamentals/contract-development/types/fully-typed-contracts">
+
+    &#123;Smart contract WASM files contain a machine-readable description of the interface type.&#125; property="og:title" content="Smart contract WASM files contain a...
+
+  </Card>
+</CardGroup>
diff --git a/docs/learn/fundamentals/data-format/README.mdx b/docs/learn/fundamentals/data-format/README.mdx
deleted file mode 100644
index 7fa85e7fb..000000000
--- a/docs/learn/fundamentals/data-format/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Data Format
-sidebar_position: 85
----
-
-import DocCardList from "@theme/DocCardList";
-
-Learn how Stellar represents and exchanges data.
-
-<DocCardList />
diff --git a/docs/learn/fundamentals/data-format/_category_.json b/docs/learn/fundamentals/data-format/_category_.json
deleted file mode 100644
index 0dadfddb1..000000000
--- a/docs/learn/fundamentals/data-format/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "description": "Understand Stellar's XDR and JSON encodings so you can inspect transactions, debug payloads, and interchange data with other systems."
-}
diff --git a/docs/learn/fundamentals/data-format/index.mdx b/docs/learn/fundamentals/data-format/index.mdx
new file mode 100644
index 000000000..b1b2dc771
--- /dev/null
+++ b/docs/learn/fundamentals/data-format/index.mdx
@@ -0,0 +1,19 @@
+---
+title: Data Format
+description: "Learn how Stellar represents and exchanges data."
+---
+
+Learn how Stellar represents and exchanges data.
+
+<CardGroup cols={2}>
+  <Card title="XDR" icon="file-lines" href="/docs/learn/fundamentals/data-format/xdr">
+
+    Understand Stellar's XDR binary format, why it exists, and how to inspect or parse it safely.
+
+  </Card>
+  <Card title="XDR-JSON" icon="file-lines" href="/docs/learn/fundamentals/data-format/xdr-json">
+
+    Use the XDR-JSON schema to round-trip Stellar XDR payloads through JSON tools without losing fidelity.
+
+  </Card>
+</CardGroup>
diff --git a/docs/learn/fundamentals/data-format/xdr-json.mdx b/docs/learn/fundamentals/data-format/xdr-json.mdx
index fc7a418b5..147836799 100644
--- a/docs/learn/fundamentals/data-format/xdr-json.mdx
+++ b/docs/learn/fundamentals/data-format/xdr-json.mdx
@@ -1,6 +1,5 @@
 ---
 title: XDR-JSON
-sidebar_position: 2
 description: Use the XDR-JSON schema to round-trip Stellar XDR payloads through JSON tools without losing fidelity.
 ---
 
@@ -12,8 +11,8 @@ The JSON-Schema for the XDR-JSON format can be found using the [`stellar xdr typ
 
 ## Tools
 
-- [Stellar CLI > `stellar xdr`](../../../tools/cli/stellar-cli.mdx#stellar-xdr)
-- [Lab > View XDR](../../../tools/lab/README.mdx)
+- [Stellar CLI > `stellar xdr`](../../../tools/cli/stellar-cli#stellar-xdr)
+- [Lab > View XDR](/docs/tools/lab)
 
 ## Libraries
 
@@ -31,11 +30,13 @@ The JSON-Schema for the XDR-JSON format can be found using the [`stellar xdr typ
 
 - **Escaped ASCII Strings:** The JSON format includes strings that are UTF-8 safe, escaped ASCII strings. This is because XDR strings are not UTF-8 encoded, but are instead byte streams that can contain any values. Non-ASCII characters are escaped.
 
-:::info[backwards-incompatible]
+<Info>
+
+**backwards-incompatible**
 
 The defined schema (linked above) is **not** backwards compatible between a given protocol version and prior versions. The best practice is to store required ledger data in XDR format, not in JSON format.
 
-:::
+</Info>
 
 [XDR]: xdr
-[`stellar xdr types schema`]: ../../../tools/cli/stellar-cli.mdx#stellar-xdr-types-schema
+[`stellar xdr types schema`]: ../../../tools/cli/stellar-cli#stellar-xdr-types-schema
diff --git a/docs/learn/fundamentals/data-format/xdr.mdx b/docs/learn/fundamentals/data-format/xdr.mdx
index 5f7c0e750..3dbd662b6 100644
--- a/docs/learn/fundamentals/data-format/xdr.mdx
+++ b/docs/learn/fundamentals/data-format/xdr.mdx
@@ -1,6 +1,5 @@
 ---
 title: XDR
-sidebar_position: 1
 description: Understand Stellar's XDR binary format, why it exists, and how to inspect or parse it safely.
 ---
 
@@ -10,11 +9,11 @@ Stellar stores and communicates ledger data, transactions, results, history, and
 
 Data structures in XDR are specified in `.x` files. These files _only_ contain data structure definitions, no operations or executable code. The `.x` files for the XDR structures used on the Stellar Network are available on [GitHub](https://github.com/stellar/stellar-xdr).
 
-:::tip
+<Tip>
 
 Stellar XDR is encodable into JSON using the [XDR-JSON] schema.
 
-:::
+</Tip>
 
 ## More About XDR
 
@@ -34,7 +33,7 @@ The XDR data is still included (encoded as a base64 string) inside the JSON in c
 
 Since the XDR format is a fundamental underpinning of the Stellar Network, we often find it necessary to dig into these raw binary data structures for clients to interact with things like transactions and authorization entries. It can be hard to understand because of its structure, but this section will aim to enlighten you on the ways to interact with it in a handful of popular languages. The Protocol's schema is defined in the [`stellar/stellar-xdr`](https://github.com/stellar/stellar-xdr) repository, though that contains far more than what we'll need for our purposes.
 
-### XDR's Common Forms
+### XDR's Common Forms {#xdrs-common-forms}
 
 In the Stellar Protocol, XDR takes a handful of different forms that are important to understand and distinguish:
 
@@ -79,9 +78,9 @@ Let's take an [`SCAddress`](https://github.com/stellar/stellar-xdr/blob/70180d5e
 
 In general, unions follow a particular pattern: switch on the type and match the appropriate enum value. So when you have one of these unions, you need to figure out which one it is:
 
-<CodeExample>
+<CodeGroup>
 
-```typescript
+```typescript TypeScript
 import { xdr } from "@stellar/stellar-sdk";
 import Buffer from "buffer";
 
@@ -100,7 +99,7 @@ switch (scAddr.switch()) {
 }
 ```
 
-```python
+```python Python
 import SCAddressType, SCAddress from stellar_sdk.xdr.sc_address_type
 
 if scAddr.type == SCAddressType.SC_ADDRESS_TYPE_ACCOUNT:
@@ -115,7 +114,7 @@ else:
     raise Exception(f"Unexpected address type: {scAddr.type}")
 ```
 
-</CodeExample>
+</CodeGroup>
 
 You can see the references for these in the documentation ([Python](https://stellar-sdk.readthedocs.io/en/stable/api.html#scaddress) and [JavaScript](https://github.com/stellar/js-stellar-base/blob/master/types/curr.d.ts#L13881-L13886), respectively).
 
@@ -146,23 +145,23 @@ Unions appear in _many_ places throughout the XDR and they can be just one arm o
 
 Remember, XDR is the lowest level of communication on the Stellar Network. Generally speaking, there are high-level abstractions that should help with these structures. For example, the above parsing routine is exactly the purpose of the [`Address.fromScAddress`](https://stellar.github.io/js-stellar-sdk/Address.html#.fromScAddress) and [`Address.from_xdr_sc_address`](https://stellar-sdk.readthedocs.io/en/stable/api.html#stellar_sdk.address.Address) abstractions in the JavaScript and Python SDKs, respectively. This greatly simplifies your code:
 
-<CodeExample>
+<CodeGroup>
 
-```typescript
+```typescript TypeScript
 import { Address } from "@stellar/stellar-sdk";
 
 // suppose `scAddr` is an instance of `xdr.ScAddress` we're parsing
 const address = Address.fromScAddress(scAddr);
 ```
 
-```python
+```python Python
 import Address from stellar_sdk;
 
 # suppose `scAddr` is an instance of `xdr.ScAddress` we're parsing
 addr = Address.from_xdr_sc_address(scAddr)
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Always try to find a higher-level abstraction before digging into the raw structure.
 
@@ -214,7 +213,7 @@ In the last part, we "abuse" the fact that there is only one variation of the `b
 
 There are many cases in which the different union arms share structure, and `.value()` lets you take advantage of that.
 
-## Record Marking / Frames in Streams
+## Record Marking / Frames in Streams {#record-marking--frames-in-streams}
 
 In some applications like stellar-core, when multiple XDR objects are stored sequentially in a file or stream, each object is framed using the Record Marking Standard defined in [RFC 5531 Section 11](https://www.rfc-editor.org/rfc/rfc5531#section-11). Each record is composed of one or more fragments. Each fragment begins with a 4-byte header followed by the fragment data:
 
@@ -228,7 +227,7 @@ In Stellar's usage today each record contains exactly one XDR object, encoded as
 - **History archives**: Bucket files and checkpoint ledger files written and read by stellar-core.
 - **Streaming LedgerCloseMeta**: The LedgerCloseMeta stream output by stellar-core.
 
-When decoding XDR with the [stellar-cli](../../../tools/cli/stellar-cli.mdx), streams framed with the record marking can be decoded by specifying the `--input stream-framed`.
+When decoding XDR with the [stellar-cli](../../../tools/cli/stellar-cli), streams framed with the record marking can be decoded by specifying the `--input stream-framed`.
 
 ---
 
@@ -237,4 +236,4 @@ This overview should give you a strong baseline on understanding how to inspect
 {/* TODO: Room to expand much more: Tools -> CLI Visualization, JSON Visualization, Stellar Lab */}
 
 [RFC4506]: http://tools.ietf.org/html/rfc4506.html
-[XDR-JSON]: ./xdr-json.mdx
+[XDR-JSON]: ./xdr-json
diff --git a/docs/learn/fundamentals/fees-resource-limits-metering.mdx b/docs/learn/fundamentals/fees-resource-limits-metering.mdx
index cab2d7dc5..705dc83e0 100644
--- a/docs/learn/fundamentals/fees-resource-limits-metering.mdx
+++ b/docs/learn/fundamentals/fees-resource-limits-metering.mdx
@@ -1,15 +1,12 @@
 ---
-title: "Understanding Fees, Resource Limits, and Metering for Transactions"
-sidebar_label: Fees, Resource Limits, and Metering
+title: "Fees, Resource Limits, and Metering"
+"og:title": "Understanding Fees, Resource Limits, and Metering for Transactions"
 description: "Learn how fees, resource limits, and metering work on the Stellar network. Understand cost structures, transaction pricing, and smart contract resource limits."
-sidebar_position: 70
 ---
 
-# Fees, Resource Limits, and Metering
-
 ## Fees overview
 
-Stellar requires a fee for all transactions to make it to the ledger. This helps prevent spam and prioritizes transactions during traffic surges. All fees are paid using the native Stellar token, the [lumen (or XLM)](./lumens.mdx).
+Stellar requires a fee for all transactions to make it to the ledger. This helps prevent spam and prioritizes transactions during traffic surges. All fees are paid using the native Stellar token, the [lumen (or XLM)](./lumens).
 
 There are two types of fees on Stellar:
 
@@ -40,19 +37,19 @@ The resource fee depends on the following resources:
 - **Ledger I/O:** the number of bytes read from or written to the ledger;
 - **Transaction size:** the size of the transaction submitted to the network in bytes;
 - **Events & return value size:** the size of the events produced by the contract and the return value of the top-level contract function — both events and return value are included in transaction metadata;
-- **Ledger space rent:** the payment for the ledger entry TTL extensions (i.e., rent payments) and rent payments for increasing ledger entry size. Refer to the [state archival](../fundamentals/contract-development/storage/state-archival.mdx) section for more information about smart contract rent.
+- **Ledger space rent:** the payment for the ledger entry TTL extensions (i.e., rent payments) and rent payments for increasing ledger entry size. Refer to the [state archival](../fundamentals/contract-development/storage/state-archival) section for more information about smart contract rent.
 
-:::note
+<Note>
 
 Some parameters may contribute to multiple fee components. For example, the transaction size is charged for network propagation (as network bandwidth is limited) and for historical storage (as storing ledger history is not free).
 
-:::
+</Note>
 
 The implementation details for fee computation are provided by the following [library](https://github.com/stellar/rs-soroban-env/blob/main/soroban-env-host/src/fees.rs). This library is used by the protocol to compute the fees and thus can be considered canonical. The resource fee rates may be updated based on consensus from the network validators.
 
 Find current resource fees in the [Resource Limits & Fees](https://lab.stellar.org/network-limits) on the Stellar Lab.
 
-For help in analyzing smart contract cost and efficiency, see this [How-To Guide](../../build/guides/fees/analyzing-smart-contract-cost.mdx).
+For help in analyzing smart contract cost and efficiency, see this [How-To Guide](../../build/guides/fees/analyzing-smart-contract-cost).
 
 ### Refundable and non-refundable resource fees
 
@@ -62,17 +59,17 @@ The resource fee is calculated with a non-refundable fees portion and a refundab
 
 **Refundable fees:** calculated from rent, events, and return value. These fees are enforced in two distinct phases. Before execution, the declared `sorobanData.resourceFee` must be at least the fee computed from the transaction's _declared_ resources, or the transaction is rejected as invalid (`txSOROBAN_INVALID`). The refundable portion is then charged from the source account and, during execution, reconciled against actual usage (rent, events, and return value); if the refundable budget is not enough for the resources actually consumed, the transaction fails at apply time and any unused portion is refunded.
 
-### Find a transaction’s resource fee
+### Find a transaction’s resource fee {#find-a-transactions-resource-fee}
 
-The best way to find the required resource fee for any smart contract transaction is to use the [`simulateTransaction` endpoint](../fundamentals/contract-development/contract-interactions/transaction-simulation.mdx) from the RPC, which enables you to dry run the execution of a transaction to compute the necessary resource values and fees.
+The best way to find the required resource fee for any smart contract transaction is to use the [`simulateTransaction` endpoint](../fundamentals/contract-development/contract-interactions/transaction-simulation) from the RPC, which enables you to dry run the execution of a transaction to compute the necessary resource values and fees.
 
 ### Resource limitations
 
-:::note
+<Note>
 
 Only smart contract transactions are subject to resource limitations.
 
-:::
+</Note>
 
 Stellar’s ledger close time is constrained to a few seconds, preventing the execution of arbitrarily large transactions, regardless of the resource fees involved. All resources mentioned in the prior section are subject to a per-transaction limit. A transaction’s memory (RAM) is also capped, though not subject to any charge.
 
@@ -88,17 +85,17 @@ The inclusion fee is the maximum bid (a bid denotes a dynamic fee, meaning it va
 
 **Stroop:** the smallest unit of a lumen, one ten-millionth of a lumen (.0000001 XLM).
 
-:::note
+<Note>
 
-Transactions can have up to 100 operations per transaction except for transactions that execute a smart contract. Smart contract transactions are only allowed one operation per transaction (unless the transaction is getting [fee-bumped](../../build/guides/transactions/fee-bump-transactions.mdx); this would add another operation), and the limits are instead specified in CPU instructions and other resource limits.
+Transactions can have up to 100 operations per transaction except for transactions that execute a smart contract. Smart contract transactions are only allowed one operation per transaction (unless the transaction is getting [fee-bumped](../../build/guides/transactions/fee-bump-transactions); this would add another operation), and the limits are instead specified in CPU instructions and other resource limits.
 
-:::
+</Note>
 
 When you set a base fee for a transaction, you are specifying the maximum amount you are willing to pay per operation in that transaction. This doesn’t necessarily mean you’ll pay that amount. You’ll only be charged the lowest amount needed for your transaction to make it to the ledger. If network traffic is light and the number of submitted operations or transactions is below the network ledger limit (configured by validators: on Mainnet, as of July 2026, 1,000 non-smart-contract operations and 2,000 smart contract transactions — other networks differ; see current values on Stellar Lab's [Network Limits](https://lab.stellar.org/network-limits) page), you will only pay the network minimum (configured by validators, currently 100 stroops).
 
 Alternatively, your transaction may not make it to the ledger if the effective base fee is higher than your base fee bid. When network traffic exceeds the ledger limit, the network enters into [surge pricing mode](#surge-pricing), and your effective base fee becomes your maximum bid.
 
-Fees are deducted from the source account unless there is a fee-bump transaction that states otherwise. Learn about fee-bump transactions in the [Fee-Bump Transaction section](../../build/guides/transactions/fee-bump-transactions.mdx).
+Fees are deducted from the source account unless there is a fee-bump transaction that states otherwise. Learn about fee-bump transactions in the [Fee-Bump Transaction section](../../build/guides/transactions/fee-bump-transactions).
 
 ## Surge and dynamic pricing
 
@@ -110,11 +107,11 @@ During surge pricing mode, transactions are sorted based on their inclusion fee
 
 If there are multiple transactions offering the same inclusion fee, but they cannot all fit into the ledger, transactions are picked randomly so that the total operations for the entire set don’t exceed 1,000. The rest of the transactions are pushed to the next ledger or discarded if they’ve been waiting for too long. If your transaction is discarded, it will never appear in a ledger as retrieved from RPC.
 
-:::note
+<Note>
 
-It is recommended to apply [ledger bounds](./transactions/operations-and-transactions.mdx#ledger-bounds) or [time bounds](./transactions/operations-and-transactions.mdx#time-bounds) to transactions — either your transaction makes it to the ledger or fails, depending on your time and/or ledger parameters.
+It is recommended to apply [ledger bounds](./transactions/operations-and-transactions#ledger-bounds) or [time bounds](./transactions/operations-and-transactions#time-bounds) to transactions — either your transaction makes it to the ledger or fails, depending on your time and/or ledger parameters.
 
-:::
+</Note>
 
 **You are more likely to pay a higher inclusion fee when submitting smart contract transactions.** Smart contract transactions have tighter ledger limits than transactions that don’t interact with smart contracts and will therefore experience surge pricing more often. You are more likely to pay your maximum inclusion fee bid or, at least, the minimum inclusion fee bid in your transaction set. So, you must plan your fee bidding strategy accordingly.
 
@@ -130,7 +127,7 @@ Write fees will grow gradually over time when the database size is below the led
 
 Metering is a mechanism in the host environment that accounts for the resource costs incurred during the execution of a smart contract. The outcomes of metering act as the canonical truth of a smart contract’s execution cost and serve as an input for fee computations.
 
-Stellar’s smart contract execution environment comprises a host and a guest. The host encapsulates shared functionalities for all contracts, including host objects, functions, and a Wasm interpreter (VM). The guest environment is where the compiled Wasm contract is interpreted and executed. A detailed discussion of these environments can be found in [Environment Concepts](../fundamentals/contract-development/environment-concepts.mdx).
+Stellar’s smart contract execution environment comprises a host and a guest. The host encapsulates shared functionalities for all contracts, including host objects, functions, and a Wasm interpreter (VM). The guest environment is where the compiled Wasm contract is interpreted and executed. A detailed discussion of these environments can be found in [Environment Concepts](../fundamentals/contract-development/environment-concepts).
 
 The division between the host and guest environments and their shared functionalities necessitates a unique approach to resource accounting. In particular, the resources required for executing Wasm instructions and running host functions must be accounted for uniformly, with costs in terms of CPU instructions and memory bytes.
 
@@ -146,11 +143,11 @@ To maintain equivalence in metering between the host and guest, computation cost
 
 Metering is segmented into host components, referred to as **cost types**. Each cost type can be viewed as a “meta instruction” symbolizing a specific host operation with a known complexity that depends on a runtime input. For instance, cost type `ComputeSha256Hash` represents the cost of computing the SHA256 hash of a byte array.
 
-:::info
+<Info>
 
 Execution of Wasm instructions is accounted for as a host cost type `WasmInsnExec`, which has a constant CPU cost per Wasm instruction. This methodology treats guest instructions and host executions equivalently.
 
-:::
+</Info>
 
 Find a complete list of host cost types and their definitions here: [`ContractCostType`](https://github.com/stellar/stellar-xdr/blob/e372df9f677961aac04c5a4cc80a3667f310b29f/Stellar-contract-config-setting.x#L92-L155).
 
@@ -180,19 +177,19 @@ There are two primary methods to deal with inclusion fee fluctuations and surge
 - [**Method 1:**](#set-the-highest-fee-youre-comfortable-paying) set the highest fee you’re comfortable paying. This does not mean that you’ll pay that amount on every transaction — you will only pay what’s necessary to get into the ledger. Under normal (non-surge) circumstances, you will only pay the standard fee even with a higher maximum fee set. This method is simple, convenient, and efficient but can still potentially fail.
 - [**Method 2:**](#fee-bumps-on-past-transactions) resubmit a transaction with a higher fee using a fee-bump transaction
 
-### Set the highest fee you’re comfortable paying​
+### Set the highest fee you’re comfortable paying​ {#set-the-highest-fee-youre-comfortable-paying}
 
 In general, it’s a good idea to choose the highest fee you’re willing to pay per operation for your transaction to make it to the ledger. Wallet developers may want to offer users a chance to specify their own base fee, though it may make more sense to set a persistent global base fee that’s above the market rate since the average user probably doesn’t care if they’re paying 0.8 cents or 0.00008 cents.
 
 Remember that you’re more likely to pay your maximum fee bid with smart contract transactions.
 
-### Fee-bumps on past transactions​
+### Fee-bumps on past transactions​ {#fee-bumps-on-past-transactions}
 
 Even with a liberal fee-paying policy, your transaction may fail to make it into the ledger due to insufficient funds or untimely surges. Fee-bump transactions can solve this problem. The following snippet shows you how to resubmit a transaction with a higher fee (as long as you have the original transaction envelope):
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 // Let `lastTx` be some transaction that fails submission due to high fees, and
 // `lastFee` be the maximum fee (expressed as an int) willing to be paid by
 // `account` for `lastTx`.
@@ -211,7 +208,7 @@ server.submitTransaction(lastTx).catch(function (error) {
 }).then(...);
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Suppose you submit two distinct transactions with the same source account and sequence number; the second transaction is a fee-bump transaction. In that case, the second transaction will be included in the transaction queue, replacing the first transaction if and only if the fee bid of the second transaction is at least 10x the fee bid of the first transaction.
 
diff --git a/docs/learn/fundamentals/index.mdx b/docs/learn/fundamentals/index.mdx
new file mode 100644
index 000000000..40dc46294
--- /dev/null
+++ b/docs/learn/fundamentals/index.mdx
@@ -0,0 +1,65 @@
+---
+title: Core Concepts
+"og:title": "Fundamentals of the Network; Data, Fees, Consensus, SEPs & More"
+description: "Learn the fundamentals and key concepts of the Stellar blockchain, including data structures, fees, consensus, anchors, Stellar Ecosystem Proposals, and more."
+---
+
+Build your foundational understanding of what makes the Stellar network tick.
+
+<CardGroup cols={2}>
+  <Card title="Stellar Stack" icon="file-lines" href="/docs/learn/fundamentals/stellar-stack">
+
+    Explore the core components and architecture of the Stellar stack, and see how they work together to power a fast, scalable, and decentralized network.
+
+  </Card>
+  <Card title="Lumens" icon="file-lines" href="/docs/learn/fundamentals/lumens">
+
+    Learn about lumens (XLM), the native digital asset of the Stellar network. Understand its role in transactions, network fees, and smart contract rent.
+
+  </Card>
+  <Card title="Stellar Consensus Protocol" icon="file-lines" href="/docs/learn/fundamentals/stellar-consensus-protocol">
+
+    A brief overview of how the Stellar Consensus Protocol (SCP), a proof of agreement protocol, enables consensus and validates transactions on the network.
+
+  </Card>
+  <Card title="Stellar Data Structures" icon="box-archive" href="/docs/learn/fundamentals/stellar-data-structures">
+
+    5 items
+
+  </Card>
+  <Card title="Stellar Decentralized Exchange" icon="file-lines" href="/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools">
+
+    Learn how liquidity pools enable trading on the Stellar Decentralized Exchange. Understand how they work, provide liquidity, and enable decentralized asset swaps on the network.
+
+  </Card>
+  <Card title="Operations & Transactions" icon="box-archive" href="/docs/learn/fundamentals/transactions">
+
+    4 items
+
+  </Card>
+  <Card title="Fees, Resource Limits, and Metering" icon="file-lines" href="/docs/learn/fundamentals/fees-resource-limits-metering">
+
+    Learn how fees, resource limits, and metering work on the Stellar network. Understand cost structures, transaction pricing, and smart contract resource limits.
+
+  </Card>
+  <Card title="Stellar Ecosystem Proposals" icon="file-lines" href="/docs/learn/fundamentals/stellar-ecosystem-proposals">
+
+    Learn about Stellar Ecosystem Proposals (SEPs), standards that enhance interoperability, improve functionality, and expand the network's capabilities.
+
+  </Card>
+  <Card title="Smart Contracts" icon="box-archive" href="/docs/learn/fundamentals/contract-development">
+
+    9 items
+
+  </Card>
+  <Card title="Data Format" icon="box-archive" href="/docs/learn/fundamentals/data-format">
+
+    Understand Stellar's XDR and JSON encodings so you can inspect transactions, debug payloads, and interchange data with other systems.
+
+  </Card>
+  <Card title="Anchors" icon="file-lines" href="/docs/learn/fundamentals/anchors">
+
+    Learn about the on and off ramps on Stellar called anchors and their role in bridging between the traditional financial system and blockchain networks.
+
+  </Card>
+</CardGroup>
diff --git a/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx b/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx
index f31709881..8aeea743e 100644
--- a/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx
+++ b/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx
@@ -1,21 +1,18 @@
 ---
-title: "Liquidity Pools on the Stellar Decentralized Exchange: Provide Liquidity and Enable Asset Swaps"
-sidebar_label: "Stellar Decentralized Exchange"
+title: "Liquidity on Stellar: Stellar Decentralized Exchange & Liquidity Pools"
+sidebarTitle: Stellar Decentralized Exchange
 description: "Learn how liquidity pools enable trading on the Stellar Decentralized Exchange. Understand how they work, provide liquidity, and enable decentralized asset swaps on the network."
-sidebar_position: 55
 ---
 
-# Liquidity on Stellar: Stellar Decentralized Exchange & Liquidity Pools
-
-:::note
+<Note>
 
 This section is scoped specifically to liquidity regarding the AMM and SDEX built into the Stellar protocol and does not include information regarding smart contracts.
 
-:::
+</Note>
 
 Users can trade and convert assets on the Stellar network with the use of path payments through Stellar’s decentralized exchange and liquidity pools.
 
-In this section, we will talk about the SDEX and liquidity pools. To learn about how these work together to execute transactions, see our [Path Payments Guide](../../build/guides/transactions/path-payments.mdx).
+In this section, we will talk about the SDEX and liquidity pools. To learn about how these work together to execute transactions, see our [Path Payments Guide](../../build/guides/transactions/path-payments).
 
 ## SDEX
 
@@ -71,7 +68,7 @@ An account can place a passive sell order via the Create Passive Sell Offer oper
 
 The order price you set is independent of the fee you pay for submitting that order in a transaction. Fees are always paid in XLM, and you specify them as a separate parameter when submitting the order to the network.
 
-To learn more about transaction fees, see our section on [Fees section](./fees-resource-limits-metering.mdx).
+To learn more about transaction fees, see our section on [Fees section](./fees-resource-limits-metering).
 
 ## Liquidity pools
 
@@ -145,9 +142,9 @@ For all of the following examples, we’ll be working with three funded Testnet
 
 The following code sets up the accounts and defines some helper functions. These should be familiar if you’ve played around with other examples like clawbacks.
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 const sdk = require("@stellar/stellar-sdk");
 const BigNumber = require("bignumber.js");
 
@@ -219,7 +216,7 @@ function preamble() {
 }
 ```
 
-```python
+```python Python
 from decimal import Decimal
 from typing import List, Any, Dict
 
@@ -283,7 +280,7 @@ def preamble() -> None:
     # ...
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Here, we use `distributeAssets()` to establish trustlines and set up initial balances of two custom assets (`A` and `B`, issued by `kp0`) for two accounts (`kp2` and `kp3`). For someone to participate in the pool, they must establish trustlines to each of the asset issuers and to the pool share asset (explained below).
 
@@ -293,9 +290,9 @@ Note the `orderAssets()` helper here. Operations related to liquidity pools refe
 
 First, let's create a liquidity pool for the asset pair defined in the preamble. This involves establishing a trustline to the pool itself:
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 const poolShareAsset = new sdk.LiquidityPoolAsset(
   A,
   B,
@@ -316,7 +313,7 @@ function establishPoolTrustline(account, keypair, poolAsset) {
 }
 ```
 
-```python
+```python Python
 pool_share_asset = LiquidityPoolAsset(asset_a=asset_a, asset_b=asset_b)
 
 
@@ -330,7 +327,7 @@ def establish_pool_trustline(source: Keypair, pool_asset: LiquidityPoolAsset) ->
     return server.submit_transaction(tx)
 ```
 
-</CodeExample>
+</CodeGroup>
 
 This lets the participants hold pool shares, which means now they can perform deposits and withdrawals.
 
@@ -338,9 +335,9 @@ This lets the participants hold pool shares, which means now they can perform de
 
 To work with a liquidity pool, you need to know its ID beforehand. It’s a deterministic value, and only a single liquidity pool can exist for a particular asset pair, so you can calculate it locally from the pool parameters.
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 const poolId = sdk
   .getLiquidityPoolId(
     "constant_product",
@@ -369,7 +366,7 @@ function addLiquidity(source, signer, poolId, maxReserveA, maxReserveB) {
 }
 ```
 
-```python
+```python Python
 pool_id = pool_share_asset.liquidity_pool_id
 
 
@@ -397,7 +394,7 @@ def add_liquidity(
     return server.submit_transaction(tx)
 ```
 
-</CodeExample>
+</CodeGroup>
 
 When depositing assets into a liquidity pool, you need to define your acceptable price bounds. In the above function, we allow for a +/-10% margin of error from the “spot price”. This margin is by no means a recommendation and is chosen just for demonstration.
 
@@ -407,9 +404,9 @@ Notice that we also specify the maximum amount of each reserve we’re willing t
 
 If you own shares of a particular pool, you can withdraw reserves from it. The operation structure mirrors the deposit closely:
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 function removeLiquidity(source, signer, poolId, sharesAmount) {
   return server
     .liquidityPools()
@@ -438,7 +435,7 @@ function removeLiquidity(source, signer, poolId, sharesAmount) {
 }
 ```
 
-```python
+```python Python
 def remove_liquidity(
         source: Keypair, pool_id: str, shares_amount: Decimal
 ) -> dict[str, Any]:
@@ -470,7 +467,7 @@ def remove_liquidity(
     return server.submit_transaction(tx)
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Notice here that we specify the minimum amount. Much like with a strict-receive path payment, we’re specifying that we’re not willing to receive less than this amount of each asset from the pool. This effectively defines a minimum withdrawal price.
 
@@ -478,9 +475,9 @@ Notice here that we specify the minimum amount. Much like with a strict-receive
 
 Finally, we can combine these pieces together to simulate some participation in a liquidity pool. We’ll have everyone deposit increasing amounts into the pool, then one participant withdraws their shares. Between each step, we’ll retrieve the spot price.
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 function main() {
   return getAccounts()
     .then((accounts) => {
@@ -538,7 +535,7 @@ function getSpotPrice() {
 preamble().then(main);
 ```
 
-```python
+```python Python
 def main():
     deposit_a = Decimal(1000)
     deposit_b = Decimal(3000)  # maintain a 1:3 ratio
@@ -578,15 +575,15 @@ if __name__ == '__main__':
     main()
 ```
 
-</CodeExample>
+</CodeGroup>
 
 #### Watching Liquidity Pool Activity
 
 You can access the transactions, operations, and effects related to a liquidity pool if you want to track its activity. Let’s see how we can track the latest deposits in a pool (suppose `poolId` is defined as before):
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 server
   .operations()
   .forLiquidityPool(poolId)
@@ -604,7 +601,7 @@ server
   });
 ```
 
-```python
+```python Python
 def watch_liquidity_pool_activity():
     for op in (
         server.operations()
@@ -620,4 +617,4 @@ def watch_liquidity_pool_activity():
         # ...
 ```
 
-</CodeExample>
+</CodeGroup>
diff --git a/docs/learn/fundamentals/lumens.mdx b/docs/learn/fundamentals/lumens.mdx
index cfd9e960e..6ca62160d 100644
--- a/docs/learn/fundamentals/lumens.mdx
+++ b/docs/learn/fundamentals/lumens.mdx
@@ -1,13 +1,11 @@
 ---
-title: "Understanding Lumens, The Native Currency of the Network"
-sidebar_label: Lumens
+title: Lumens (XLM)
+sidebarTitle: Lumens
+"og:title": "Understanding Lumens, The Native Currency of the Network"
 description: "Learn about lumens (XLM), the native digital asset of the Stellar network. Understand its role in transactions, network fees, and smart contract rent."
-sidebar_position: 30
 ---
 
-# Lumens (XLM)
-
-Lumens (XLM) are the native currency of the Stellar network. The lumen is the only token that doesn’t require an issuer or trustline. They are used to pay all transaction [fees](#transaction-fees), fund [rent](./fees-resource-limits-metering.mdx#resource-fee), and to cover [minimum balance requirements](stellar-data-structures/accounts.mdx#base-reserves-and-subentries) on the network.
+Lumens (XLM) are the native currency of the Stellar network. The lumen is the only token that doesn’t require an issuer or trustline. They are used to pay all transaction [fees](#transaction-fees), fund [rent](./fees-resource-limits-metering#resource-fee), and to cover [minimum balance requirements](/docs/learn/fundamentals/stellar-data-structures/accounts#base-reserves-and-subentries) on the network.
 
 To read up on the basics of lumens, head over to our Stellar Learn site: [Stellar Learn: Lumens](https://stellar.org/lumens)
 
@@ -15,9 +13,9 @@ To read up on the basics of lumens, head over to our Stellar Learn site: [Stella
 
 Stellar requires a small fee for all transactions to prevent ledger spam and prioritize transactions during surge pricing. Transaction fees are paid in lumens.
 
-To learn about fees on Stellar, see our [Fees section](./fees-resource-limits-metering.mdx).
+To learn about fees on Stellar, see our [Fees section](./fees-resource-limits-metering).
 
-Smart contract transactions on Stellar employ a different fee structure based on an inclusion fee and resource consumption (which includes [rent](#rent)). Read more in the [Fees and Metering section](./fees-resource-limits-metering.mdx).
+Smart contract transactions on Stellar employ a different fee structure based on an inclusion fee and resource consumption (which includes [rent](#rent)). Read more in the [Fees and Metering section](./fees-resource-limits-metering).
 
 ## Base reserves
 
@@ -37,11 +35,11 @@ For example, an account with one trustline, two offers, and a claimable balance
 
 Minimum balance is not the same as the balance an account can spend. Selling liabilities (the amount an account has committed to open sell offers) are not part of the minimum balance. They reduce the balance available above it: `available balance` = `balance` - `minimum balance` - `liabilities.selling`.
 
-When you close a subentry, the associated base reserve will be added to your available balance. An account must always pay its own minimum balance unless it is being sponsored by another account. Sponsorship can cover both an account's subentries and its own two base reserves — so a sponsored account can even be created with a starting balance of `0`, with the sponsor carrying its reserves. For information about this, see our [Sponsored Reserves guide](../../build/guides/transactions/sponsored-reserves.mdx).
+When you close a subentry, the associated base reserve will be added to your available balance. An account must always pay its own minimum balance unless it is being sponsored by another account. Sponsorship can cover both an account's subentries and its own two base reserves — so a sponsored account can even be created with a starting balance of `0`, with the sponsor carrying its reserves. For information about this, see our [Sponsored Reserves guide](../../build/guides/transactions/sponsored-reserves).
 
 ## Rent
 
-Smart contract data does not require any base reserves in order to live on the ledger, so every smart contract entry must pay rent instead. The rent charged for an entry to exist on the ledger is based on how big the entry is and how long it should be live on the ledger before being archived. There are different rent requirements for each storage type `Persistent`, `Temporary`, and `Instance`, which you can read about in the [State Archival section](../fundamentals/contract-development/storage/state-archival.mdx).
+Smart contract data does not require any base reserves in order to live on the ledger, so every smart contract entry must pay rent instead. The rent charged for an entry to exist on the ledger is based on how big the entry is and how long it should be live on the ledger before being archived. There are different rent requirements for each storage type `Persistent`, `Temporary`, and `Instance`, which you can read about in the [State Archival section](../fundamentals/contract-development/storage/state-archival).
 
 ## Lumen Supply Metrics
 
@@ -76,7 +74,7 @@ As of July 21st, 2026, the Dashboard API shows:
 
 **inflationLumens** For the first five or so years of Stellar’s existence, the supply of lumens increased by 1% annually. This “network inflation” was ended by validator vote on October 28, 2019. The total number of lumens generated by inflation was 5,443,902,087.3472865.
 
-Adding this number to the Original Supply, you get the total lumens that have ever existed: 105,443,902,087.3472865. This number is visible on the [List All Ledgers](../../data/apis/horizon/api-reference/list-all-ledgers.api.mdx) Horizon API endpoint as `_embedded.records.total_coins`. See all Stellar Mainnet Horizon data providers [here](../../data/apis/horizon/providers.mdx).
+Adding this number to the Original Supply, you get the total lumens that have ever existed: 105,443,902,087.3472865. This number is visible on the [List All Ledgers](/docs/data/apis/horizon/api-reference/list-all-ledgers) Horizon API endpoint as `_embedded.records.total_coins`. See all Stellar Mainnet Horizon data providers [here](../../data/apis/horizon/providers).
 
 **burnedLumens** These are all the lumens sent to accounts with no signers, meaning the funds are inaccessible and have been removed forever from Stellar’s lumen supply.
 
@@ -86,7 +84,7 @@ While any address with no signers is counted here, the vast majority of the lume
 
 **upgradeReserve** The Upgrade Reserve is a special address that’s neither circulating nor a part of SDF’s mandate. When Stellar [changed its consensus algorithm](https://stellar.org/blog/upgraded-network-is-here) in 2015 and relaunched the network these lumens were set aside, to be claimed, one-for-one, by holders of the old network tokens. The [Upgrade Reserve account](https://stellar.expert/explorer/public/account/GBEZOC5U4TVH7ZY5N3FLYHTCZSI6VFGTULG7PBITLF5ZEBPJXFT46YZM) is essentially an escrow, and we don’t expect many claimants to come and pull those lumens into the circulating supply at this point.
 
-**feePool** The Fee Pool is where network fees collect. The lumens do not belong to any particular account. No one has access to the fee pool, so these lumens are non-circulating. Network validators could theoretically vote for a protocol change that would affect the fee pool, so we include it in the total supply. Stellar’s transaction fees are extremely low so the fee pool grows very slowly. The Fee Pool is tracked by the protocol itself, and the current number is visible on the [List All Ledgers](../../data/apis/horizon/api-reference/list-all-ledgers.api.mdx) Horizon API endpoint as `_embedded.records.fee_pool`. See all Stellar Mainnet Horizon data providers [here](../../data/apis/horizon/providers.mdx).
+**feePool** The Fee Pool is where network fees collect. The lumens do not belong to any particular account. No one has access to the fee pool, so these lumens are non-circulating. Network validators could theoretically vote for a protocol change that would affect the fee pool, so we include it in the total supply. Stellar’s transaction fees are extremely low so the fee pool grows very slowly. The Fee Pool is tracked by the protocol itself, and the current number is visible on the [List All Ledgers](/docs/data/apis/horizon/api-reference/list-all-ledgers) Horizon API endpoint as `_embedded.records.fee_pool`. See all Stellar Mainnet Horizon data providers [here](../../data/apis/horizon/providers).
 
 **sdfMandate** The SDF Mandate is described in detail on the [Stellar Foundation mandate page](https://stellar.org/foundation/mandate), the authoritative source for the mandate's structure and accounts. The Foundation was funded by lumens generated at Stellar’s inception; all of those lumens will eventually be spent or distributed to enhance and promote Stellar. SDF organizes these holdings into four buckets. The on-chain accounts in each bucket, as of July 2026, are listed below — balances change continuously, so refer to the mandate page or each account's [stellar.expert](https://stellar.expert) page for live figures:
 
@@ -104,13 +102,13 @@ While any address with no signers is counted here, the vast majority of the lume
 - [Growth 2](https://stellar.expert/explorer/public/account/GBEVKAYIPWC5AQT6D4N7FC3XGKRRBMPCAMTO3QZWMHHACLHTMAHAM2TP)
 - [Growth 3](https://stellar.expert/explorer/public/account/GDUY7J7A33TQWOSOQGDO776GGLM3UQERL4J3SPT56F6YS4ID7MLDERI4)
 
-#### Product & Innovation
+#### Product & Innovation {#product--innovation}
 
 - [Product and Innovation 1](https://stellar.expert/explorer/public/account/GCPWKVQNLDPD4RNP5CAXME4BEDTKSSYRR4MMEL4KG65NEGCOGNJW7QI2)
 - [Product and Innovation 2](https://stellar.expert/explorer/public/account/GDKIJJIKXLOM2NRMPNQZUUYK24ZPVFC6426GZAEP3KUK6KEJLACCWNMX)
 - [Product and Innovation Hot 2](https://stellar.expert/explorer/public/account/GDWXQOTIIDO2EUK4DIGIBLEHLME2IAJRNU6JDFS5B2ZTND65P7J36WQZ)
 
-#### Assets & Liquidity
+#### Assets & Liquidity {#assets--liquidity}
 
 - [Assets and Liquidity](https://stellar.expert/explorer/public/account/GAMGGUQKKJ637ILVDOSCT5X7HYSZDUPGXSUW67B2UKMG2HEN5TPWN3LQ)
 - [Assets and Liquidity (Hot)](https://stellar.expert/explorer/public/account/GANII5Y2LABEBK74NWNKS4NREX2T52YTBGQDRDKVBFRIIF5VE4ORYOVY)
diff --git a/docs/learn/fundamentals/stellar-consensus-protocol.mdx b/docs/learn/fundamentals/stellar-consensus-protocol.mdx
index 36952b1c9..dcbe527a0 100644
--- a/docs/learn/fundamentals/stellar-consensus-protocol.mdx
+++ b/docs/learn/fundamentals/stellar-consensus-protocol.mdx
@@ -1,12 +1,9 @@
 ---
-title: "Overview of the Stellar Consensus Protocol (SCP) and Transaction Validation"
-sidebar_label: Stellar Consensus Protocol
+title: Stellar Consensus Protocol
+"og:title": Overview of the Stellar Consensus Protocol (SCP) and Transaction Validation
 description: "A brief overview of how the Stellar Consensus Protocol (SCP), a proof of agreement protocol, enables consensus and validates transactions on the network."
-sidebar_position: 40
 ---
 
-# Stellar Consensus Protocol
-
 Consensus is hugely important in a decentralized payment system. It distributes the monitoring and approval of transactions across many individual nodes (computers) instead of relying on one closed, central system. Nodes are run by organizations or individuals, and the goal is for all nodes to update the ledger in the same way, ensuring each ledger reaches the same state. Consensus is vital for the security of the blockchain, allowing nodes to agree on something safely and preventing double-spend attacks.
 
 The Stellar network reaches consensus using the Stellar Consensus Protocol (SCP), which is a construction of the Federated Byzantine Agreement (FBA). FBA differs from other well-known consensus mechanisms like Proof of Work (which relies on a node’s computational power) and Proof of Stake (which relies on a node’s staking power) by instead relying on the agreement of trusted nodes.
diff --git a/docs/learn/fundamentals/stellar-data-structures/README.mdx b/docs/learn/fundamentals/stellar-data-structures/README.mdx
deleted file mode 100644
index c5305ce7d..000000000
--- a/docs/learn/fundamentals/stellar-data-structures/README.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: "Blockchain Data Structures: Accounts, Smart Contracts, Assets & Ledgers"
-sidebar_label: Stellar Data Structures
-description: "Learn about blockchain data structures, including accounts, transactions, assets, and ledgers. Understand how they work together to make the network function."
-sidebar_position: 50
----
-
-# Stellar Data Structures
-
-import DocCardList from "@theme/DocCardList";
-
-The fundamental data structures and building blocks present on the Stellar network.
-
-<DocCardList />
diff --git a/docs/learn/fundamentals/stellar-data-structures/accounts.mdx b/docs/learn/fundamentals/stellar-data-structures/accounts.mdx
index f526ffeb8..a91e156b2 100644
--- a/docs/learn/fundamentals/stellar-data-structures/accounts.mdx
+++ b/docs/learn/fundamentals/stellar-data-structures/accounts.mdx
@@ -1,35 +1,32 @@
 ---
-title: "Understanding Accounts: Balances, Transactions, and Network Interactions"
-sidebar_label: Accounts
+title: Accounts
+"og:title": "Understanding Accounts: Balances, Transactions, and Network Interactions"
 description: "Learn about accounts on the Stellar network, including how they store balances, sign transactions, and interact with assets, smart contracts, and other features."
-sidebar_position: 20
 ---
 
-# Accounts
-
 Accounts are the central data structure in Stellar—they hold balances, sign transactions, and issue assets. Accounts can only exist with a valid keypair and the required minimum balance of XLM.
 
-To learn about minimum balance requirements, [see our section on Lumens](../lumens.mdx#minimum-balance).
+To learn about minimum balance requirements, [see our section on Lumens](../lumens#minimum-balance).
 
-:::note
+<Note>
 
-There are two types of accounts on Stellar: Stellar accounts (`G...` addresses) and contract accounts (`C...` addresses). For a minimal contract account walkthrough, start with the [Simple Account example](../../../build/smart-contracts/example-contracts/simple-account.mdx). This section focuses on Stellar `G...` accounts.
+There are two types of accounts on Stellar: Stellar accounts (`G...` addresses) and contract accounts (`C...` addresses). For a minimal contract account walkthrough, start with the [Simple Account example](../../../build/smart-contracts/example-contracts/simple-account). This section focuses on Stellar `G...` accounts.
 
-:::
+</Note>
 
 `G...` accounts are made up of the below fields. Click on the field to learn more about it.
 
-- [Account ID](../../glossary.mdx#account-id)
-- [Balances](../../glossary.mdx#balance)
-- [Flags](../../glossary.mdx#flags)
-- [Home domain (up to 32 characters)](../../glossary.mdx#home-domain)
-- [Liabilities](../../glossary.mdx#liability)
-- [Number of entries sponsored by this account](../../../build/guides/transactions/sponsored-reserves.mdx)
-- [Number of sponsored reserves](../../../build/guides/transactions/sponsored-reserves.mdx)
-- [Number of subentries](./accounts.mdx#subentries)
-- [Sequence number](../../glossary.mdx#sequence-number)
-- [Signers](../../fundamentals/transactions/signatures-multisig.mdx)
-- [Thresholds](../../fundamentals/transactions/signatures-multisig.mdx#thresholds)
+- [Account ID](../../glossary#account-id)
+- [Balances](../../glossary#balance)
+- [Flags](../../glossary#flags)
+- [Home domain (up to 32 characters)](../../glossary#home-domain)
+- [Liabilities](../../glossary#liability)
+- [Number of entries sponsored by this account](../../../build/guides/transactions/sponsored-reserves)
+- [Number of sponsored reserves](../../../build/guides/transactions/sponsored-reserves)
+- [Number of subentries](./accounts#subentries)
+- [Sequence number](../../glossary#sequence-number)
+- [Signers](../../fundamentals/transactions/signatures-multisig)
+- [Thresholds](../../fundamentals/transactions/signatures-multisig#thresholds)
 
 ## Base reserves and subentries
 
@@ -49,12 +46,12 @@ Account data is stored in subentries, each of which increases an account’s min
 - Additional signers
 - Data entries (includes data made with the `manageData` operation, not smart contract ledger entries)
 
-A pool share trustline therefore requires two base reserves (currently 1 XLM) and uses two of the account’s 1,000 subentries. Learn more in the [Liquidity Pools section](../liquidity-on-stellar-sdex-liquidity-pools.mdx#trustlines).
+A pool share trustline therefore requires two base reserves (currently 1 XLM) and uses two of the account’s 1,000 subentries. Learn more in the [Liquidity Pools section](../liquidity-on-stellar-sdex-liquidity-pools#trustlines).
 
 ## Trustlines
 
-Trustlines are an explicit opt-in for an account to hold a particular asset. To hold a specific asset, an account must establish a trustline with the issuing account using the [`change_trust` operation](../transactions/list-of-operations.mdx#change-trust). Trustlines track the balance of an asset and can also limit the amount of an asset that an account can hold.
+Trustlines are an explicit opt-in for an account to hold a particular asset. To hold a specific asset, an account must establish a trustline with the issuing account using the [`change_trust` operation](../transactions/list-of-operations#change-trust). Trustlines track the balance of an asset and can also limit the amount of an asset that an account can hold.
 
-A trustline must be established for an account to receive any asset except lumens (XLM). You can create a claimable balance to send assets to an account without a trustline, but the recipient has to create a trustline to claim that balance. Learn more in the [Claimable Balances guide](../../../build/guides/transactions/claimable-balances.mdx).
+A trustline must be established for an account to receive any asset except lumens (XLM). You can create a claimable balance to send assets to an account without a trustline, but the recipient has to create a trustline to claim that balance. Learn more in the [Claimable Balances guide](../../../build/guides/transactions/claimable-balances).
 
 A trustline also tracks liabilities. Buying liabilities equal the total amount of the asset offered to buy aggregated over all offers owned by an account, and selling liabilities equal the total amount of the asset offered to sell aggregated over all offers owned by an account. A trustline must always have a balance sufficiently large to satisfy its selling liabilities and a balance sufficiently below its limit to accommodate its buying liabilities.
diff --git a/docs/learn/fundamentals/stellar-data-structures/assets.mdx b/docs/learn/fundamentals/stellar-data-structures/assets.mdx
index 41d1da223..cf50f176a 100644
--- a/docs/learn/fundamentals/stellar-data-structures/assets.mdx
+++ b/docs/learn/fundamentals/stellar-data-structures/assets.mdx
@@ -1,29 +1,28 @@
 ---
 title: "Assets on Stellar: Explore Trustlines, Smart Contract Integration & More"
-sidebar_label: Assets
+sidebarTitle: Assets
 description: "Learn how assets work on the Stellar network, including issuing, transferring, and managing tokens. Explore trustlines, using assets in smart contracts, & more."
-sidebar_position: 30
 ---
 
-:::info
+<Info>
 
 The term "custom token" has been deprecated in favor of "contract token". View the conversation in the [Stellar Developer Discord](https://discord.com/channels/897514728459468821/966788672164855829/1359276952971640953).
 
-:::
+</Info>
 
-# Assets
+## Assets
 
 Accounts on the Stellar network can be used to track, hold, and transfer any type of asset. Assets can represent many things: cryptocurrencies (such as bitcoin or ether), fiat currencies (such as dollars or pesos), other tokens of value (such as NFTs), pool shares, or bonds and equity.
 
-:::note
+<Note>
 
 Assets exist in two forms on Stellar:
 
 "Classic" assets issued by Stellar accounts (`G...` addresses) and their built-in Stellar Asset Contract (SAC) implementation, and contract tokens issued by a deployed Wasm contract (`C...` addresses).
 
-Learn more about the differences in the [Assets and Tokens section](../../../tokens/README.mdx).
+Learn more about the differences in the [Assets and Tokens section](/docs/tokens).
 
-:::
+</Note>
 
 Classic assets on Stellar have two identifying characteristics: the asset code and the issuer. Since more than one organization can issue a credit representing the same asset, asset codes often overlap (for example, multiple companies offer a USD token on Stellar). Assets are uniquely identified by the combination of their asset code and issuer.
 
@@ -33,9 +32,9 @@ Classic assets on Stellar have two identifying characteristics: the asset code a
 
 An asset’s identifying code. There are three different formats: Alphanumeric 4, Alphanumeric 12, and liquidity pool shares.
 
-Learn about liquidity pool shares in the [Liquidity Pool section](../liquidity-on-stellar-sdex-liquidity-pools.mdx).
+Learn about liquidity pool shares in the [Liquidity Pool section](../liquidity-on-stellar-sdex-liquidity-pools).
 
-Learn more about asset codes in the [Naming an Asset section](../../../tokens/control-asset-access.mdx#naming-an-asset)
+Learn more about asset codes in the [Naming an Asset section](../../../tokens/control-asset-access#naming-an-asset)
 
 ### Issuer
 
@@ -43,15 +42,15 @@ There is no dedicated operation to create an asset on Stellar. Instead, assets a
 
 The public key of the issuing account is linked on the ledger to the asset. Responsibility for and control over an asset resides with the issuing account. Since settings are stored at the account level on the ledger, the issuing account is where you use set_options operations to link to meta-information about an asset and set authorization flags.
 
-Learn how to issue an asset in the [Issuing Assets Tutorial](../../../tokens/how-to-issue-an-asset.mdx).
+Learn how to issue an asset in the [Issuing Assets Tutorial](../../../tokens/how-to-issue-an-asset).
 
 ## Representation
 
 In Horizon, assets are represented in a JSON object:
 
-<CodeExample>
+<CodeGroup>
 
-```json5
+```json5 JSON5
 {
   asset_code: "AstroDollar",
   asset_issuer: "GC2BKLYOOYPDEFJKLKY6FNNRQMGFLVHJKQRGNSSRRGSMPGF32LHCQVGF",
@@ -61,31 +60,31 @@ In Horizon, assets are represented in a JSON object:
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
 In the Stellar SDKs, they’re represented with the asset class:
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 var astroDollar = new StellarSdk.Asset(
   "AstroDollar",
   "GC2BKLYOOYPDEFJKLKY6FNNRQMGFLVHJKQRGNSSRRGSMPGF32LHCQVGF",
 );
 ```
 
-```java
+```java Java
 KeyPair issuer = KeyPair.fromAccountId("GC2BKLYOOYPDEFJKLKY6FNNRQMGFLVHJKQRGNSSRRGSMPGF32LHCQVGF");
 Asset astroDollar = Asset.createNonNativeAsset("AstroDollar", issuer.getAccountId());
 ```
 
-```python
+```python Python
 from stellar_sdk import Asset
 
 astro_dollar = Asset("AstroDollar", "GC2BKLYOOYPDEFJKLKY6FNNRQMGFLVHJKQRGNSSRRGSMPGF32LHCQVGF")
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## Amount precision
 
@@ -111,8 +110,8 @@ Assets issued on the Stellar network are accessible to smart contracts. Every St
 
 The Stellar CLI can deploy a Stellar Asset Contract for a Stellar asset. Deploying the Stellar Asset Contract for a Stellar asset enables that asset for use with smart contracts.
 
-Learn more in the [SAC section](../../../tokens/stellar-asset-contract.mdx).
+Learn more in the [SAC section](../../../tokens/stellar-asset-contract).
 
 ## Token contracts
 
-Token contracts can be deployed on Stellar by deploying a contract that implements the [Token Interface](../../../tokens/token-interface.mdx), which is the same interface implemented by the [Stellar Asset Contract (SAC)](../../../tokens/stellar-asset-contract.mdx) for Stellar assets.
+Token contracts can be deployed on Stellar by deploying a contract that implements the [Token Interface](../../../tokens/token-interface), which is the same interface implemented by the [Stellar Asset Contract (SAC)](../../../tokens/stellar-asset-contract) for Stellar assets.
diff --git a/docs/learn/fundamentals/stellar-data-structures/contracts.mdx b/docs/learn/fundamentals/stellar-data-structures/contracts.mdx
index 070ff9880..968b8179e 100644
--- a/docs/learn/fundamentals/stellar-data-structures/contracts.mdx
+++ b/docs/learn/fundamentals/stellar-data-structures/contracts.mdx
@@ -1,10 +1,10 @@
 ---
 title: Smart Contracts
-sidebar_position: 50
+description: "A smart contract is a programmed set of executable code and state that can be invoked on the Stellar network."
 ---
 
 A smart contract is a programmed set of executable code and state that can be invoked on the Stellar network. Smart contracts store data and also define rules for how that data can be used. Stellar has integrated a smart contracts platform called "Soroban" into the core protocol. These contracts are programs written in the Rust language and compiled as WebAssembly (Wasm) for deployment.
 
-Learn about Stellar smart contract concepts such as storage, authorization, debugging, and more in the [Smart Contract Learn Section](../contract-development/overview.mdx).
+Learn about Stellar smart contract concepts such as storage, authorization, debugging, and more in the [Smart Contract Learn Section](../contract-development/overview).
 
-Write your first Stellar smart contract by following the [Getting Started Guide](../../../build/smart-contracts/getting-started/README.mdx).
+Write your first Stellar smart contract by following the [Getting Started Guide](/docs/build/smart-contracts/getting-started).
diff --git a/docs/learn/fundamentals/stellar-data-structures/events.mdx b/docs/learn/fundamentals/stellar-data-structures/events.mdx
index 593dbda53..fbf76482b 100644
--- a/docs/learn/fundamentals/stellar-data-structures/events.mdx
+++ b/docs/learn/fundamentals/stellar-data-structures/events.mdx
@@ -1,5 +1,4 @@
 ---
-sidebar_position: 11
 title: Events
 description: Monitor off-chain movement of value and smart contract changes.
 ---
@@ -19,7 +18,7 @@ Events are the mechanism that applications off-chain can use to monitor movement
 
 An event's topics don't have to be made of the same type: you can mix different types.
 
-An event also contains a data object of any value or type, including [custom types](../contract-development/types/custom-types.mdx) defined by contracts using `#[contracttype]`:
+An event also contains a data object of any value or type, including [custom types](../contract-development/types/custom-types) defined by contracts using `#[contracttype]`:
 
 ```cpp
 struct ContractEvent
@@ -178,21 +177,21 @@ Starting in protocol 23, classic operations can emit `transfer`, `mint`, `burn`,
 
 ## Reading events
 
-You can use the [`getEvents`](../../../data/apis/rpc/api-reference/methods/getEvents.mdx) endpoint of any RPC service to fetch and filter events by type, contract, and topic.
+You can use the [`getEvents`](../../../data/apis/rpc/api-reference/methods/getEvents) endpoint of any RPC service to fetch and filter events by type, contract, and topic.
 
-:::warning
+<Warning>
 
 Events are ephemeral: RPC providers typically only keep short chunks (less than a week) of history around.
 
-:::
+</Warning>
 
-To learn more about working with events, take a look at the [events guides](../../../build/guides/events/README.mdx) and [this example contract](../../../build/smart-contracts/example-contracts/events.mdx).
+To learn more about working with events, take a look at the [events guides](/docs/build/guides/events) and [this example contract](../../../build/smart-contracts/example-contracts/events).
 
-For a quick high-level demonstration, though, we'll use the [TypeScript SDK](../../../tools/sdks/README.mdx) to infinitely fetch all `transfer` events (defined by the [Soroban Token Interface](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0041.md#interface)) involving the [XLM contract](https://stellar.expert/explorer/testnet/contract/CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC) and display them in a human-friendly format.
+For a quick high-level demonstration, though, we'll use the [TypeScript SDK](/docs/tools/sdks) to infinitely fetch all `transfer` events (defined by the [Soroban Token Interface](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0041.md#interface)) involving the [XLM contract](https://stellar.expert/explorer/testnet/contract/CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC) and display them in a human-friendly format.
 
-<CodeExample>
+<CodeGroup>
 
-```javascript
+```javascript JavaScript
 import {
   humanizeEvents,
   nativeToScVal,
@@ -291,6 +290,6 @@ function cereal(data) {
 main().catch((e) => console.error(e));
 ```
 
-</CodeExample>
+</CodeGroup>
 
 You can also leverage RPC's alternate [XDR encoding formats](../../../data/apis/rpc/api-reference/structure/data-format) like JSON to see human-readable events from the command-line directly, for example by passing `xdrFormat: "json"` as an additional parameter to the `getEvents` [example](../../../data/apis/rpc/api-reference/methods/getEvents#examples).
diff --git a/docs/learn/fundamentals/stellar-data-structures/index.mdx b/docs/learn/fundamentals/stellar-data-structures/index.mdx
new file mode 100644
index 000000000..dfd1ffc8a
--- /dev/null
+++ b/docs/learn/fundamentals/stellar-data-structures/index.mdx
@@ -0,0 +1,35 @@
+---
+title: Stellar Data Structures
+"og:title": "Blockchain Data Structures: Accounts, Smart Contracts, Assets & Ledgers"
+description: "Learn about blockchain data structures, including accounts, transactions, assets, and ledgers. Understand how they work together to make the network function."
+---
+
+The fundamental data structures and building blocks present on the Stellar network.
+
+<CardGroup cols={2}>
+  <Card title="Ledgers" icon="file-lines" href="/docs/learn/fundamentals/stellar-data-structures/ledgers">
+
+    A ledger captures the state of the Stellar network at a point in time, storing accounts, balances, orders, smart contract data, and other persistent information.
+
+  </Card>
+  <Card title="Events" icon="file-lines" href="/docs/learn/fundamentals/stellar-data-structures/events">
+
+    Monitor off-chain movement of value and smart contract changes.
+
+  </Card>
+  <Card title="Accounts" icon="file-lines" href="/docs/learn/fundamentals/stellar-data-structures/accounts">
+
+    Learn about accounts on the Stellar network, including how they store balances, sign transactions, and interact with assets, smart contracts, and other features.
+
+  </Card>
+  <Card title="Assets" icon="file-lines" href="/docs/learn/fundamentals/stellar-data-structures/assets">
+
+    Learn how assets work on the Stellar network, including issuing, transferring, and managing tokens. Explore trustlines, using assets in smart contracts, & more.
+
+  </Card>
+  <Card title="Smart Contracts" icon="file-lines" href="/docs/learn/fundamentals/stellar-data-structures/contracts">
+
+    A smart contract is a programmed set of executable code and state that can be invoked on the Stellar network.
+
+  </Card>
+</CardGroup>
diff --git a/docs/learn/fundamentals/stellar-data-structures/ledgers.mdx b/docs/learn/fundamentals/stellar-data-structures/ledgers.mdx
index 7c91cf0ea..db5ce12d8 100644
--- a/docs/learn/fundamentals/stellar-data-structures/ledgers.mdx
+++ b/docs/learn/fundamentals/stellar-data-structures/ledgers.mdx
@@ -1,28 +1,25 @@
 ---
-title: "Ledgers Store Accounts, Balances, Orders, Smart Contract Data & More"
-sidebar_position: 10
-sidebar_label: Ledgers
+title: Ledgers
+"og:title": "Ledgers Store Accounts, Balances, Orders, Smart Contract Data & More"
 description: "A ledger captures the state of the Stellar network at a point in time, storing accounts, balances, orders, smart contract data, and other persistent information."
 ---
 
-# Ledgers
-
 A ledger represents the state of the Stellar network at a point in time. It is shared across all Core nodes in the network and contains the list of accounts and balances, orders on the distributed exchange, smart contract data, and any other persisting data.
 
-:::note
+<Note>
 
 Blockchains typically refer to the **ledger** as the entire record of all transactions on the blockchain and **blocks** as individual units of data that contain a collection of transactions. In Stellar, "ledger" can refer to both.
 
-:::
+</Note>
 
 In every Stellar Consensus Protocol round, the network reaches consensus on which transaction set to apply to the last closed ledger, and when the new set is applied, a new “last closed ledger” is defined. Each ledger is cryptographically linked to the unique previous ledger, creating a historical chain that goes back to the genesis ledger.
 
 Data is stored on the ledger as ledger entries. Possible ledger entries include:
 
-- [Accounts](./accounts.mdx)
-- [Claimable balances](../../../build/guides/transactions/claimable-balances.mdx)
-- [Liquidity pools](../../fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx)
-- [Contract data](../../fundamentals/contract-development/storage/persisting-data.mdx#ledger-entries)
+- [Accounts](./accounts)
+- [Claimable balances](../../../build/guides/transactions/claimable-balances)
+- [Liquidity pools](../../fundamentals/liquidity-on-stellar-sdex-liquidity-pools)
+- [Contract data](../../fundamentals/contract-development/storage/persisting-data#ledger-entries)
 
 ## Ledger headers
 
@@ -121,11 +118,11 @@ The last used global ID. These IDs are used for generating objects.
 
 ### Maximum number of transactions
 
-The maximum number of operations validators have agreed to process in a given ledger. If more transactions are submitted than this number, the network will enter into surge pricing mode. For more about surge pricing and fee strategies, see our [Fees section](../../fundamentals/fees-resource-limits-metering.mdx).
+The maximum number of operations validators have agreed to process in a given ledger. If more transactions are submitted than this number, the network will enter into surge pricing mode. For more about surge pricing and fee strategies, see our [Fees section](../../fundamentals/fees-resource-limits-metering).
 
 ### Base fee
 
-The fee the network charges per operation in a transaction. Calculated in stroops. See the [Fees section](../../fundamentals/fees-resource-limits-metering.mdx) for more information.
+The fee the network charges per operation in a transaction. Calculated in stroops. See the [Fees section](../../fundamentals/fees-resource-limits-metering) for more information.
 
 ### Base reserve
 
diff --git a/docs/learn/fundamentals/stellar-ecosystem-proposals.mdx b/docs/learn/fundamentals/stellar-ecosystem-proposals.mdx
index a0b911b0e..d8d694497 100644
--- a/docs/learn/fundamentals/stellar-ecosystem-proposals.mdx
+++ b/docs/learn/fundamentals/stellar-ecosystem-proposals.mdx
@@ -1,19 +1,17 @@
 ---
-title: "Stellar Ecosystem Proposals (SEPs): Standards for Interoperability & Development"
-sidebar_label: Stellar Ecosystem Proposals
+title: Stellar Ecosystem Proposals (SEPs)
+sidebarTitle: Stellar Ecosystem Proposals
+"og:title": "Stellar Ecosystem Proposals (SEPs): Standards for Interoperability & Development"
 description: "Learn about Stellar Ecosystem Proposals (SEPs), standards that enhance interoperability, improve functionality, and expand the network's capabilities."
-sidebar_position: 80
 ---
 
-# Stellar Ecosystem Proposals (SEPs)
-
 Each SEP is a distinct blueprint meant to help users build a product or service that interoperates with other products and services on the Stellar network.
 
-:::note
+<Note>
 
 This page covers Stellar Ecosystem Proposals (SEPs), which define standards and protocols for projects building on the Stellar network. SEPs differ from Core Advancement Proposals (CAPs), which propose changes to the Stellar network’s core protocol. You can learn more about CAPs on [GitHub](https://github.com/stellar/stellar-protocol/tree/master/core).
 
-:::
+</Note>
 
 When you build on Stellar, you generally use the Stellar RPC API to interact with the network. However, anytime you want your product or service to interoperate with other products or services in the ecosystem, you must create additional infrastructure to handle those components of an interaction.
 
@@ -27,7 +25,7 @@ There are many SEPs, and they cover a wide variety of standards for interoperati
 
 This section will cover a few notable SEPs that define the standards for some common Stellar use cases.
 
-### SEP-1 - Stellar Info File
+### SEP-1 - Stellar Info File {#sep-1---stellar-info-file}
 
 Defines how to create and host a stellar.toml file: a common place where the Internet can find information about your Stellar integration. You can store a lot of information in your stellar.toml file including organization information, currency information, and contact information. TOML is a simple and commonly used configuration file format designed to be readable by both humans and machines.
 
@@ -37,7 +35,7 @@ Using the `set_options` operation, you can link your Stellar account to the doma
 
 [Link to GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md)
 
-### SEP-5 - Key Derivation Methods for Stellar Accounts
+### SEP-5 - Key Derivation Methods for Stellar Accounts {#sep-5---key-derivation-methods-for-stellar-accounts}
 
 Describes methods for key derivation for Stellar, improving key storage and moving keys between wallets and applications. Guidance in this SEP improves the Stellar ecosystem by:
 
@@ -50,7 +48,7 @@ Describes methods for key derivation for Stellar, improving key storage and movi
 
 [Link to GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0005.md)
 
-### SEP-6 - Deposit and Withdrawal API
+### SEP-6 - Deposit and Withdrawal API {#sep-6---deposit-and-withdrawal-api}
 
 Defines the standard way for anchors and wallets to interact on behalf of users. With this SEP’s guidance, wallets and other clients can interact with anchors directly without the user needing to leave the wallet to go to the anchor’s site.
 
@@ -70,7 +68,7 @@ SEP-24 is the alternative to SEP-6 which supports hosted deposits and withdrawal
 
 [Link to GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md)
 
-### SEP-7 - URI Scheme to Facilitate Delegated Signing
+### SEP-7 - URI Scheme to Facilitate Delegated Signing {#sep-7---uri-scheme-to-facilitate-delegated-signing}
 
 Defines the standard URI scheme that can be used to generate a URI that will serve as a request to sign a transaction. With this SEP’s guidance, non-wallet applications can have their their users sign a transaction without seeing the wallet user's secret key in any form since the URI (request) will typically be signed by the user’s trusted wallet where the secret keys are stored.
 
@@ -85,7 +83,7 @@ This SEP defines a standard protocol enabling the following features within a wa
 
 [Link to GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0007.md)
 
-### SEP-10 - Stellar Authentication
+### SEP-10 - Stellar Authentication {#sep-10---stellar-authentication}
 
 Defines a standard way for clients (such as wallets or exchanges) to create authenticated web sessions for users holding a Stellar account. This SEP also supports authenticating users of shared or pooled Stellar accounts. Clients can use muxed accounts to distinguish users or sub-accounts of shared accounts.
 
@@ -95,7 +93,7 @@ Proves that the user has a Stellar account and that they control the account wit
 
 [Link to GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md)
 
-### SEP-12 - KYC API
+### SEP-12 - KYC API {#sep-12---kyc-api}
 
 Allows for sharing of KYC data and defines a standard way for Stellar clients to upload KYC and other information to anchors and other services. This SEP was made with these goals in mind:
 
@@ -110,7 +108,7 @@ Allows for sharing of KYC data and defines a standard way for Stellar clients to
 
 [Link to GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md)
 
-### SEP-20 - Self-Verification of Validator Nodes
+### SEP-20 - Self-Verification of Validator Nodes {#sep-20---self-verification-of-validator-nodes}
 
 Defines how validators self-verify by setting the home domain of their Stellar account to their website, where they publish information on-chain about their node and organization in a stellar.toml file. This allows other participants to discover other nodes and add them to their quorum sets without needing a centralized database.
 
@@ -118,7 +116,7 @@ Defines how validators self-verify by setting the home domain of their Stellar a
 
 [Link to GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0020.md)
 
-### SEP-24 - Hosted Deposit and Withdrawal
+### SEP-24 - Hosted Deposit and Withdrawal {#sep-24---hosted-deposit-and-withdrawal}
 
 Defines the standard way for anchors and wallets to interact on behalf of users interactively. This means that the user’s application must open a webview hosted by a third-party anchor for the user to provide the information necessary to complete the transaction.
 
@@ -130,7 +128,7 @@ SEP-6 is the alternative to SEP-24 that supports an API-style solution for the s
 
 [Link to GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md)
 
-### SEP-30 - Account Recovery: Multi-Party Recovery of Stellar Accounts
+### SEP-30 - Account Recovery: Multi-Party Recovery of Stellar Accounts {#sep-30---account-recovery-multi-party-recovery-of-stellar-accounts}
 
 Defines the standard API that enables an individual (e.g., a user or wallet) to regain access to a Stellar account that it owns after the individual has lost its private key without providing any third-party control of the account. Using this protocol, the user or wallet will preregister the account and a phone number, email, or other form of authentication with one or more servers implementing the protocol and add those servers as signers of the account. If two or more servers are used with appropriate signer configuration no individual server will have control of the account, but collectively, they may help the individual recover access to the account.
 
@@ -145,7 +143,7 @@ This SEP enables the following use cases for a user:
 
 [Link to GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0030.md)
 
-### SEP-31 - Cross-Border Payment API
+### SEP-31 - Cross-Border Payment API {#sep-31---cross-border-payment-api}
 
 Defines the protocol for two financial accounts that exist outside the Stellar network (anchors) to interact with each other.
 
diff --git a/docs/learn/fundamentals/stellar-stack.mdx b/docs/learn/fundamentals/stellar-stack.mdx
index 06c92f8db..e28fae4c6 100644
--- a/docs/learn/fundamentals/stellar-stack.mdx
+++ b/docs/learn/fundamentals/stellar-stack.mdx
@@ -1,12 +1,9 @@
 ---
-title: "Learn About the Core Components and Architecture of the Stellar Network"
-sidebar_label: Stellar Stack
+title: Stellar Stack
+"og:title": Learn About the Core Components and Architecture of the Stellar Network
 description: "Explore the core components and architecture of the Stellar stack, and see how they work together to power a fast, scalable, and decentralized network."
-sidebar_position: 10
 ---
 
-# Stellar Stack
-
 The Stellar stack is made up of the following components: the networks (Mainnet, Testnet, and Futurenet), Stellar Core, Stellar RPC, and SDKs, each of which plays a specific part in providing financial infrastructure that is resilient to failures, available to anyone, and fast and cheap enough to serve real-world use cases.
 
 ![Stellar Stack](/assets/diagrams/stellar-tech-stack.png)
@@ -15,15 +12,15 @@ The Stellar stack is made up of the following components: the networks (Mainnet,
 
 Stellar has three networks: the public network (Mainnet, also called Pubnet or the Public Network), the test network (Testnet), and a dev network (Futurenet). Mainnet is the main network used by applications in production. The Testnet is a smaller, free-to-use network maintained by SDF that functions like the Mainnet but doesn’t connect to real money and is the best place for developers to test their applications. Futurenet is a dev network you can use to test more bleeding edge features.
 
-Read more about the different networks in the [Networks section](../../networks/README.mdx).
+Read more about the different networks in the [Networks section](/docs/networks).
 
 ## Stellar Core
 
 Stellar Core is the program used by the individual nodes (or computers) that make up the network. Stellar Core keeps a common distributed ledger and engages in consensus to validate and process transactions. Generally, nodes reach consensus, apply a transaction set, and update the ledger every 5-7 seconds.
 
-Nodes reach consensus using the Stellar Consensus Protocol, which can you can learn more about here: [Stellar Consensus Protocol](./stellar-consensus-protocol.mdx)
+Nodes reach consensus using the Stellar Consensus Protocol, which can you can learn more about here: [Stellar Consensus Protocol](./stellar-consensus-protocol)
 
-Anyone can run a Stellar Core node, but you don’t have to in order to build on Stellar. We recommend you do so if you issue an asset and want to ensure the accuracy of the ledger, if you want to participate in network governance by voting on protocol version, minimum fees, and resource and ledger limits, and/or if you want to contribute to Stellar’s overall health and decentralization. Check out our tutorial on installing, configuring, and maintaining your own node here: [Run a Validator Node Tutorial](../../validators/README.mdx).
+Anyone can run a Stellar Core node, but you don’t have to in order to build on Stellar. We recommend you do so if you issue an asset and want to ensure the accuracy of the ledger, if you want to participate in network governance by voting on protocol version, minimum fees, and resource and ledger limits, and/or if you want to contribute to Stellar’s overall health and decentralization. Check out our tutorial on installing, configuring, and maintaining your own node here: [Run a Validator Node Tutorial](/docs/validators).
 
 ## RPC
 
@@ -31,15 +28,15 @@ Stellar's RPC is a JSON RPC server that provides an interface for users and appl
 
 SDF has RPC endpoints available for Futurenet and Testnet. These services are free to use, and are suitable for development and testing.
 
-SDF does not provide a publicly available RPC endpoint for Mainnet. Developers should [select an ecosystem provider](../../data/apis/rpc/providers.mdx) that works for their project before migrating to Mainnet. In some cases, projects may choose to run their own RPC instance.
+SDF does not provide a publicly available RPC endpoint for Mainnet. Developers should [select an ecosystem provider](../../data/apis/rpc/providers) that works for their project before migrating to Mainnet. In some cases, projects may choose to run their own RPC instance.
 
 ## Horizon
 
-:::warning
+<Warning>
 
-Horizon is nearing end-of-life and will eventually be deprecated in favor of Stellar RPC and [Portfolio APIs](../../data/indexers/README.mdx#portfolio-apis). While it will continue to receive updates to maintain compatibility with upcoming protocol releases, it won't receive new feature development.
+Horizon is nearing end-of-life and will eventually be deprecated in favor of Stellar RPC and [Portfolio APIs](/docs/data/indexers#portfolio-apis). While it will continue to receive updates to maintain compatibility with upcoming protocol releases, it won't receive new feature development.
 
-:::
+</Warning>
 
 Horizon is the client-facing RESTful HTTP API server in the platform layer which allows programmatic access to submit transactions and query the network’s historical data. It acts as the interface for applications that want to access the Stellar network. You can communicate with Horizon using an SDK, a web browser, or with simple command tools like cURL.
 
@@ -47,4 +44,4 @@ Horizon is the client-facing RESTful HTTP API server in the platform layer which
 
 SDKs simplify some of the work of accessing Horizon and the Stellar RPC by converting the data into friendlier formats and allowing you to program in the language of your choice. Stellar’s SDKs show you how to request data and create and submit transactions. Soroban's SDKs allow you to write smart contracts in Rust and interact with smart contracts in a myriad of other languages.
 
-View Stellar's [SDK library](../../tools/sdks/README.mdx) to access our SDKs and their documentation.
+View Stellar's [SDK library](/docs/tools/sdks) to access our SDKs and their documentation.
diff --git a/docs/learn/fundamentals/transactions/README.mdx b/docs/learn/fundamentals/transactions/README.mdx
deleted file mode 100644
index c962cd76d..000000000
--- a/docs/learn/fundamentals/transactions/README.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "Learn About Transactions on Stellar: Lifecycle, Operations & More"
-sidebar_position: 60
-sidebar_label: Operations & Transactions
-description: "Learn about transactions on Stellar: how they work, the transaction lifecycle, a list of operations, and how they transfer assets and execute smart contracts."
----
-
-# Operations & Transactions
-
-import DocCardList from "@theme/DocCardList";
-
-<DocCardList />
diff --git a/docs/learn/fundamentals/transactions/index.mdx b/docs/learn/fundamentals/transactions/index.mdx
new file mode 100644
index 000000000..1c81d4a2b
--- /dev/null
+++ b/docs/learn/fundamentals/transactions/index.mdx
@@ -0,0 +1,28 @@
+---
+title: "Operations & Transactions"
+"og:title": "Learn About Transactions on Stellar: Lifecycle, Operations & More"
+description: "Learn about transactions on Stellar: how they work, the transaction lifecycle, a list of operations, and how they transfer assets and execute smart contracts."
+---
+
+<CardGroup cols={2}>
+  <Card title="Operations and Transactions" icon="file-lines" href="/docs/learn/fundamentals/transactions/operations-and-transactions">
+
+    Learn how operations and transactions work on the Stellar network. Understand how multiple operations are bundled into transactions to execute blockchain actions.
+
+  </Card>
+  <Card title="List of Operations" icon="file-lines" href="/docs/learn/fundamentals/transactions/list-of-operations">
+
+    Explore the full list of Stellar operations, including creating accounts, making payments, creating trustlines, all smart contract operations, and more.
+
+  </Card>
+  <Card title="Signatures and Multisig" icon="file-lines" href="/docs/learn/fundamentals/transactions/signatures-multisig">
+
+    This section details signing non-smart contract transactions.
+
+  </Card>
+  <Card title="Transaction Lifecycle" icon="file-lines" href="/docs/learn/fundamentals/transactions/transaction-lifecycle">
+
+    A user creates a transaction by setting the source account, sequence number, list of operations and their respective parameters, fee or fee-bump, and...
+
+  </Card>
+</CardGroup>
diff --git a/docs/learn/fundamentals/transactions/list-of-operations.mdx b/docs/learn/fundamentals/transactions/list-of-operations.mdx
index 5848d5782..f0f8ad254 100644
--- a/docs/learn/fundamentals/transactions/list-of-operations.mdx
+++ b/docs/learn/fundamentals/transactions/list-of-operations.mdx
@@ -1,23 +1,20 @@
 ---
-title: "Explore Stellar Operations: Accounts, Payments, Trustlines & More"
-sidebar_label: List of Operations
+title: List of Operations
+"og:title": "Explore Stellar Operations: Accounts, Payments, Trustlines & More"
 description: "Explore the full list of Stellar operations, including creating accounts, making payments, creating trustlines, all smart contract operations, and more."
-sidebar_position: 20
 ---
 
-# List of Operations
-
 Operations are objects that represent a desired change to the ledger and are submitted to the network grouped in a transaction. For each operation, there is a successful or failed result type. In the case of success, the user can gather information about the effect of the operation. In the case of failure, the user can learn more about the error.
 
-Learn more about transactions and operations in our [Operations and Transactions section](./operations-and-transactions.mdx).
+Learn more about transactions and operations in our [Operations and Transactions section](./operations-and-transactions).
 
 There are currently 26 operations you can use on the Stellar network, these operations, their definitions, SDKs, thresholds, parameters, and errors are listed below.
 
-:::note
+<Note>
 
 All these operations have an optional source account parameter. If the source account parameter is omitted, the source account of the transaction is considered as the source account of the operation.
 
-:::
+</Note>
 
 ## Create account
 
@@ -66,7 +63,7 @@ Sends an amount in a specific asset to a destination account
 | `PAYMENT_SRC_NO_TRUST` | -3 | The source account does not trust the issuer of the asset it is trying to send. |
 | `PAYMENT_SRC_NOT_AUTHORIZED` | -4 | The source account is not authorized to send this payment. |
 | `PAYMENT_NO_DESTINATION` | -5 | The receiving account does not exist. Note that this error will **not** be returned if the receiving account is the issuer of `asset` (i.e, when the asset is being _burned_). |
-| `PAYMENT_NO_TRUST` | -6 | The receiver does not trust the issuer of the asset being sent. For more information, see the [Assets section](../stellar-data-structures/assets.mdx). |
+| `PAYMENT_NO_TRUST` | -6 | The receiver does not trust the issuer of the asset being sent. For more information, see the [Assets section](../stellar-data-structures/assets). |
 | `PAYMENT_NOT_AUTHORIZED` | -7 | The destination account is not authorized by the asset's issuer to hold the asset. |
 | `PAYMENT_LINE_FULL` | -8 | The destination account (receiver) does not have sufficient limits to receive `amount` and still satisfy its buying liabilities. |
 
@@ -74,7 +71,7 @@ Sends an amount in a specific asset to a destination account
 
 A payment where the asset sent can be different than the asset received; allows the user to specify the amount of the asset to send
 
-Learn more about path payments: [Path Payments Guide](../../../build/guides/transactions/path-payments.mdx)
+Learn more about path payments: [Path Payments Guide](../../../build/guides/transactions/path-payments)
 
 **SDKs**: [Python](https://stellar-sdk.readthedocs.io/en/stable/api.html#stellar_sdk.operation.PathPaymentStrictSend) | [JavaScript](https://stellar.github.io/js-stellar-base/Operation.html#.pathPaymentStrictSend) | [Java](https://javadoc.io/doc/network.lightsail/stellar-sdk/latest/org/stellar/sdk/operations/PathPaymentStrictSendOperation.html) | [Go](https://pkg.go.dev/github.com/stellar/go-stellar-sdk/txnbuild#PathPaymentStrictSend)  
 **Threshold**: Medium  
@@ -99,7 +96,7 @@ Learn more about path payments: [Path Payments Guide](../../../build/guides/tran
 | `PATH_PAYMENT_STRICT_SEND_SRC_NO_TRUST` | -3 | The source account does not trust the issuer of the asset it is trying to send. |
 | `PATH_PAYMENT_STRICT_SEND_SRC_NOT_AUTHORIZED` | -4 | The source account is not authorized to send this payment. |
 | `PATH_PAYMENT_STRICT_SEND_NO_DESTINATION` | -5 | The destination account does not exist. |
-| `PATH_PAYMENT_STRICT_SEND_NO_TRUST` | -6 | The destination account does not trust the issuer of the asset being sent. For more, see the [Assets section](../stellar-data-structures/assets.mdx). |
+| `PATH_PAYMENT_STRICT_SEND_NO_TRUST` | -6 | The destination account does not trust the issuer of the asset being sent. For more, see the [Assets section](../stellar-data-structures/assets). |
 | `PATH_PAYMENT_STRICT_SEND_NOT_AUTHORIZED` | -7 | The destination account is not authorized by the asset's issuer to hold the asset. |
 | `PATH_PAYMENT_STRICT_SEND_LINE_FULL` | -8 | The destination account does not have sufficient limits to receive `destination amount` and still satisfy its buying liabilities. |
 | `PATH_PAYMENT_STRICT_SEND_TOO_FEW_OFFERS` | -10 | There is no path of offers connecting the `send asset` and `destination asset`. Stellar only considers paths of length 5 or shorter. |
@@ -110,7 +107,7 @@ Learn more about path payments: [Path Payments Guide](../../../build/guides/tran
 
 A payment where the asset received can be different from the asset sent; allows the user to specify the amount of the asset received
 
-Learn more about path payments: [Path Payments Guide](../../../build/guides/transactions/path-payments.mdx)
+Learn more about path payments: [Path Payments Guide](../../../build/guides/transactions/path-payments)
 
 **SDKs**: [Python](https://stellar-sdk.readthedocs.io/en/stable/api.html#stellar_sdk.operation.PathPaymentStrictReceive) | [JavaScript](https://stellar.github.io/js-stellar-base/Operation.html#.pathPaymentStrictReceive) | [Java](https://javadoc.io/doc/network.lightsail/stellar-sdk/latest/org/stellar/sdk/operations/PathPaymentStrictReceiveOperation.html) | [Go](https://pkg.go.dev/github.com/stellar/go-stellar-sdk/txnbuild#PathPaymentStrictReceive)  
 **Threshold**: Medium  
@@ -135,7 +132,7 @@ Learn more about path payments: [Path Payments Guide](../../../build/guides/tran
 | `PATH_PAYMENT_STRICT_RECEIVE_SRC_NO_TRUST` | -3 | The source account does not trust the issuer of the asset it is trying to send. |
 | `PATH_PAYMENT_STRICT_RECEIVE_SRC_NOT_AUTHORIZED` | -4 | The source account is not authorized to send this payment. |
 | `PATH_PAYMENT_STRICT_RECEIVE_NO_DESTINATION` | -5 | The destination account does not exist. |
-| `PATH_PAYMENT_STRICT_RECEIVE_NO_TRUST` | -6 | The destination account does not trust the issuer of the asset being sent. For more, see the [Assets section](../stellar-data-structures/assets.mdx). |
+| `PATH_PAYMENT_STRICT_RECEIVE_NO_TRUST` | -6 | The destination account does not trust the issuer of the asset being sent. For more, see the [Assets section](../stellar-data-structures/assets). |
 | `PATH_PAYMENT_STRICT_RECEIVE_NOT_AUTHORIZED` | -7 | The destination account is not authorized by the asset's issuer to hold the asset. |
 | `PATH_PAYMENT_STRICT_RECEIVE_LINE_FULL` | -8 | The destination account does not have sufficient limits to receive `destination amount` and still satisfy its buying liabilities. |
 | `PATH_PAYMENT_STRICT_RECEIVE_TOO_FEW_OFFERS` | -10 | There is no path of offers connecting the `send asset` and `destination asset`. Stellar only considers paths of length 5 or shorter. |
@@ -146,7 +143,7 @@ Learn more about path payments: [Path Payments Guide](../../../build/guides/tran
 
 Creates, updates, or deletes an offer to buy a specific amount of an asset for another
 
-Learn more about passive sell offers: [Liquidity on Stellar: SDEX and Liquidity Pools](../liquidity-on-stellar-sdex-liquidity-pools.mdx)
+Learn more about passive sell offers: [Liquidity on Stellar: SDEX and Liquidity Pools](../liquidity-on-stellar-sdex-liquidity-pools)
 
 **SDKs**: [Python](https://stellar-sdk.readthedocs.io/en/stable/api.html#stellar_sdk.operation.ManageBuyOffer) | [JavaScript](https://stellar.github.io/js-stellar-base/Operation.html#.manageBuyOffer) | [Java](https://javadoc.io/doc/network.lightsail/stellar-sdk/latest/org/stellar/sdk/operations/ManageBuyOfferOperation.html) | [Go](https://pkg.go.dev/github.com/stellar/go-stellar-sdk/txnbuild#ManageBuyOffer)  
 **Threshold**: Medium  
@@ -180,7 +177,7 @@ Learn more about passive sell offers: [Liquidity on Stellar: SDEX and Liquidity
 
 Creates, updates, or deletes an offer to sell a specific amount of an asset for another
 
-Learn more about passive sell offers: [Liquidity on Stellar: SDEX and Liquidity Pools](../liquidity-on-stellar-sdex-liquidity-pools.mdx)
+Learn more about passive sell offers: [Liquidity on Stellar: SDEX and Liquidity Pools](../liquidity-on-stellar-sdex-liquidity-pools)
 
 **SDKs**: [Python](https://stellar-sdk.readthedocs.io/en/stable/api.html#stellar_sdk.operation.ManageSellOffer) | [JavaScript](https://stellar.github.io/js-stellar-base/Operation.html#.manageSellOffer) | [Java](https://javadoc.io/doc/network.lightsail/stellar-sdk/latest/org/stellar/sdk/operations/ManageSellOfferOperation.html) | [Go](https://pkg.go.dev/github.com/stellar/go-stellar-sdk/txnbuild#ManageSellOffer)  
 **Threshold**: Medium  
@@ -214,7 +211,7 @@ Learn more about passive sell offers: [Liquidity on Stellar: SDEX and Liquidity
 
 Creates an offer to sell one asset for another without taking a reverse offer of equal price
 
-Learn more about passive sell offers: [Liquidity on Stellar: SDEX and Liquidity Pools](../liquidity-on-stellar-sdex-liquidity-pools.mdx)
+Learn more about passive sell offers: [Liquidity on Stellar: SDEX and Liquidity Pools](../liquidity-on-stellar-sdex-liquidity-pools)
 
 **SDKs**: [Python](https://stellar-sdk.readthedocs.io/en/stable/api.html#stellar_sdk.operation.CreatePassiveSellOffer) | [JavaScript](https://stellar.github.io/js-stellar-base/Operation.html#.createPassiveSellOffer) | [Java](https://javadoc.io/doc/network.lightsail/stellar-sdk/latest/org/stellar/sdk/operations/CreatePassiveSellOfferOperation.html) | [Go](https://pkg.go.dev/github.com/stellar/go-stellar-sdk/txnbuild#CreatePassiveSellOffer)  
 **Threshold**: Medium  
@@ -247,9 +244,9 @@ Learn more about passive sell offers: [Liquidity on Stellar: SDEX and Liquidity
 
 Set options for an account such as flags, inflation destination, signers, home domain, and master key weight
 
-Learn more about flags: [Flags Section](../../../tokens/control-asset-access.mdx#controlling-access-to-an-asset-with-flags)  
+Learn more about flags: [Flags Section](../../../tokens/control-asset-access#controlling-access-to-an-asset-with-flags)  
 Learn more about the home domain: [Stellar Ecosystem Proposals SEP-1](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md)  
-Learn more about signers operations and key weight: [Signature and Multisignature Section](../../fundamentals/transactions/signatures-multisig.mdx)
+Learn more about signers operations and key weight: [Signature and Multisignature Section](../../fundamentals/transactions/signatures-multisig)
 
 **SDKs**: [Python](https://stellar-sdk.readthedocs.io/en/stable/api.html#stellar_sdk.operation.SetOptions) | [JavaScript](https://stellar.github.io/js-stellar-base/Operation.html#.setOptions) | [Java](https://javadoc.io/doc/network.lightsail/stellar-sdk/latest/org/stellar/sdk/operations/SetOptionsOperation.html) | [Go](https://pkg.go.dev/github.com/stellar/go-stellar-sdk/txnbuild#SetOptions)  
 **Threshold**: High (when updating signers or other thresholds) or Medium (when updating everything else)  
@@ -259,13 +256,13 @@ Learn more about signers operations and key weight: [Signature and Multisignatur
 | Parameters | Type | Description |
 | --- | --- | --- |
 | Inflation Destination | account ID | Account of the inflation destination. |
-| Clear flags | integer | Indicates which [account](../stellar-data-structures/accounts.mdx) flags to clear. These account-level flags are primarily used by asset issuers. For details about the flags, please refer to the [Asset Design Considerations page](../../../tokens/control-asset-access.mdx). The bit mask integer subtracts from the existing flags of the account. This allows for setting specific bits without knowledge of existing flags. |
-| Set flags | integer | Indicates which [account](../stellar-data-structures/accounts.mdx) flags to set. These account-level flags are primarily used by asset issuers. For details about the flags, please refer to the [Asset Design Considerations page](../../../tokens/control-asset-access.mdx#controlling-access-to-an-asset-with-flags) The bit mask integer adds onto the existing flags of the account. This allows for setting specific bits without knowledge of existing flags. |
+| Clear flags | integer | Indicates which [account](../stellar-data-structures/accounts) flags to clear. These account-level flags are primarily used by asset issuers. For details about the flags, please refer to the [Asset Design Considerations page](../../../tokens/control-asset-access). The bit mask integer subtracts from the existing flags of the account. This allows for setting specific bits without knowledge of existing flags. |
+| Set flags | integer | Indicates which [account](../stellar-data-structures/accounts) flags to set. These account-level flags are primarily used by asset issuers. For details about the flags, please refer to the [Asset Design Considerations page](../../../tokens/control-asset-access#controlling-access-to-an-asset-with-flags) The bit mask integer adds onto the existing flags of the account. This allows for setting specific bits without knowledge of existing flags. |
 | Master weight | integer | A number from 0-255 (inclusive) representing the weight of the master key. If the weight of the master key is updated to 0, it is effectively disabled. |
-| Low threshold | integer | A number from 0-255 (inclusive) representing the threshold this account sets on all operations it performs that have [a low threshold](../../fundamentals/transactions/signatures-multisig.mdx). |
-| Medium threshold | integer | A number from 0-255 (inclusive) representing the threshold this account sets on all operations it performs that have [a medium threshold](../../fundamentals/transactions/signatures-multisig.mdx). |
-| High threshold | integer | A number from 0-255 (inclusive) representing the threshold this account sets on all operations it performs that have [a high threshold](../../fundamentals/transactions/signatures-multisig.mdx). |
-| Home domain | string | Sets the home domain of an account. See [Federation](../../glossary.mdx#federation). |
+| Low threshold | integer | A number from 0-255 (inclusive) representing the threshold this account sets on all operations it performs that have [a low threshold](../../fundamentals/transactions/signatures-multisig). |
+| Medium threshold | integer | A number from 0-255 (inclusive) representing the threshold this account sets on all operations it performs that have [a medium threshold](../../fundamentals/transactions/signatures-multisig). |
+| High threshold | integer | A number from 0-255 (inclusive) representing the threshold this account sets on all operations it performs that have [a high threshold](../../fundamentals/transactions/signatures-multisig). |
+| Home domain | string | Sets the home domain of an account. See [Federation](../../glossary#federation). |
 | Signer | \{Public Key, weight} | Add, update, or remove a signer from an account. Signer weight is a number from 0-255 (inclusive). The signer is deleted if the weight is 0. |
 
 **Possible errors**:
@@ -286,7 +283,7 @@ Learn more about signers operations and key weight: [Signature and Multisignatur
 
 Creates, updates, or deletes a trustline
 
-Learn more about trustlines: [Trustlines section](../stellar-data-structures/accounts.mdx#trustlines)
+Learn more about trustlines: [Trustlines section](../stellar-data-structures/accounts#trustlines)
 
 **SDKs**: [Python](https://stellar-sdk.readthedocs.io/en/stable/api.html#stellar_sdk.operation.ChangeTrust) | [JavaScript](https://stellar.github.io/js-stellar-base/Operation.html#.changeTrust) | [Java](https://javadoc.io/doc/network.lightsail/stellar-sdk/latest/org/stellar/sdk/operations/ChangeTrustOperation.html) | [Go](https://pkg.go.dev/github.com/stellar/go-stellar-sdk/txnbuild#ChangeTrust)  
 **Threshold**: Medium  
@@ -315,11 +312,11 @@ Learn more about trustlines: [Trustlines section](../stellar-data-structures/acc
 
 Updates the authorized flag of an existing trustline. This operation can only be performed by the asset issuer
 
-:::warning
+<Warning>
 
 This operation is deprecated as of Protocol 17- prefer [_SetTrustlineFlags_](#set-trustline-flags) operation instead.
 
-:::
+</Warning>
 
 **SDKs**: [Python](https://stellar-sdk.readthedocs.io/en/stable/api.html#stellar_sdk.operation.AllowTrust) | [JavaScript](https://stellar.github.io/js-stellar-base/Operation.html#.allowTrust) | [Java](https://javadoc.io/doc/network.lightsail/stellar-sdk/latest/org/stellar/sdk/operations/AllowTrustOperation.html) | [Go](https://pkg.go.dev/github.com/stellar/go-stellar-sdk/txnbuild#AllowTrust)  
 **Threshold**: Low  
@@ -376,7 +373,7 @@ Sponsorship also blocks a merge (`ACCOUNT_MERGE_IS_SPONSOR`), and this covers tw
 
 Sets, modifies, or deletes a data entry (name/value pair) that is attached to an account
 
-Learn more about entries and subentries: [Accounts section](../stellar-data-structures/accounts.mdx#subentries)
+Learn more about entries and subentries: [Accounts section](../stellar-data-structures/accounts#subentries)
 
 **SDKs**: [Python](https://stellar-sdk.readthedocs.io/en/stable/api.html#stellar_sdk.operation.ManageData) | [JavaScript](https://stellar.github.io/js-stellar-base/Operation.html#.manageData) | [Java](https://javadoc.io/doc/network.lightsail/stellar-sdk/latest/org/stellar/sdk/operations/ManageDataOperation.html) | [Go](https://pkg.go.dev/github.com/stellar/go-stellar-sdk/txnbuild#ManageData)  
 **Threshold**: Medium  
@@ -420,7 +417,7 @@ Bumps forward the sequence number of the source account to the given sequence nu
 
 Moves an amount of asset from the operation source account into a new ClaimableBalanceEntry
 
-Learn more about claimable balances: [Claimable Balances Guide](../../../build/guides/transactions/claimable-balances.mdx)
+Learn more about claimable balances: [Claimable Balances Guide](../../../build/guides/transactions/claimable-balances)
 
 **SDKs**: [Python](https://stellar-sdk.readthedocs.io/en/stable/api.html#stellar_sdk.operation.CreateClaimableBalance) | [JavaScript](https://stellar.github.io/js-stellar-base/Operation.html#.createClaimableBalance) | [Java](https://javadoc.io/doc/network.lightsail/stellar-sdk/latest/org/stellar/sdk/operations/CreateClaimableBalanceOperation.html) | [Go](https://pkg.go.dev/github.com/stellar/go-stellar-sdk/txnbuild#CreateClaimableBalance)  
 **Threshold**: Medium  
@@ -447,7 +444,7 @@ Learn more about claimable balances: [Claimable Balances Guide](../../../build/g
 
 Claims a ClaimableBalanceEntry that corresponds to the BalanceID and adds the amount of an asset on the entry to the source account
 
-Learn more about claimable balances and view more parameters: [Claimable Balances Guide](../../../build/guides/transactions/claimable-balances.mdx)
+Learn more about claimable balances and view more parameters: [Claimable Balances Guide](../../../build/guides/transactions/claimable-balances)
 
 **SDKs**: [Python](https://stellar-sdk.readthedocs.io/en/stable/api.html#stellar_sdk.operation.ClaimClaimableBalance) | [JavaScript](https://stellar.github.io/js-stellar-base/Operation.html#.claimClaimableBalance) | [Java](https://javadoc.io/doc/network.lightsail/stellar-sdk/latest/org/stellar/sdk/operations/ClaimClaimableBalanceOperation.html) | [Go](https://pkg.go.dev/github.com/stellar/go-stellar-sdk/txnbuild#ClaimClaimableBalance)  
 **Threshold**: Low  
@@ -456,7 +453,7 @@ Learn more about claimable balances and view more parameters: [Claimable Balance
 
 | Parameters | Type | Description |
 | --- | --- | --- |
-| BalanceID | claimableBalanceID | BalanceID on the ClaimableBalanceEntry that the source account is claiming. The balanceID can be retrieved from a successful `CreateClaimableBalanceResult`. See [Claimable Balance Guide](../../../build/guides/transactions/claimable-balances.mdx#create-claimable-balance) for more information. |
+| BalanceID | claimableBalanceID | BalanceID on the ClaimableBalanceEntry that the source account is claiming. The balanceID can be retrieved from a successful `CreateClaimableBalanceResult`. See [Claimable Balance Guide](../../../build/guides/transactions/claimable-balances#create-claimable-balance) for more information. |
 
 **Possible errors**:
 
@@ -474,7 +471,7 @@ Allows an account to pay the base reserves for another account; sponsoring accou
 
 There must also be an end sponsoring future reserves operation in the same transaction
 
-Learn more about sponsored reserves: [Sponsored Reserves Guide](../../../build/guides/transactions/sponsored-reserves.mdx)
+Learn more about sponsored reserves: [Sponsored Reserves Guide](../../../build/guides/transactions/sponsored-reserves)
 
 **SDKs**: [Python](https://stellar-sdk.readthedocs.io/en/stable/api.html#stellar_sdk.operation.BeginSponsoringFutureReserves) | [JavaScript](https://stellar.github.io/js-stellar-base/Operation.html#.beginSponsoringFutureReserves) | [Java](https://javadoc.io/doc/network.lightsail/stellar-sdk/latest/org/stellar/sdk/operations/BeginSponsoringFutureReservesOperation.html) | [Go](https://pkg.go.dev/github.com/stellar/go-stellar-sdk/txnbuild#BeginSponsoringFutureReserves)  
 **Threshold**: Medium  
@@ -497,7 +494,7 @@ Learn more about sponsored reserves: [Sponsored Reserves Guide](../../../build/g
 
 Terminates the current is-sponsoring-future-reserves relationship in which the source account is sponsored
 
-Learn more about sponsored reserves: [Sponsored Reserves Guide](../../../build/guides/transactions/sponsored-reserves.mdx)
+Learn more about sponsored reserves: [Sponsored Reserves Guide](../../../build/guides/transactions/sponsored-reserves)
 
 **SDKs**: [Python](https://stellar-sdk.readthedocs.io/en/stable/api.html#stellar_sdk.operation.EndSponsoringFutureReserves) | [JavaScript](https://stellar.github.io/js-stellar-base/Operation.html#.endSponsoringFutureReserves) | [Java](https://javadoc.io/doc/network.lightsail/stellar-sdk/latest/org/stellar/sdk/operations/EndSponsoringFutureReservesOperation.html) | [Go](https://pkg.go.dev/github.com/stellar/go-stellar-sdk/txnbuild#EndSponsoringFutureReserves)  
 **Threshold**: Medium  
@@ -518,7 +515,7 @@ Learn more about sponsored reserves: [Sponsored Reserves Guide](../../../build/g
 
 Sponsoring account can remove or transfer sponsorships of existing ledgerEntries and signers; the logic of this operation depends on the state of the source account
 
-Learn more about sponsored reserves: [Sponsored Reserves Guide](../../../build/guides/transactions/sponsored-reserves.mdx)
+Learn more about sponsored reserves: [Sponsored Reserves Guide](../../../build/guides/transactions/sponsored-reserves)
 
 **SDKs**: [Python](https://stellar-sdk.readthedocs.io/en/stable/api.html#stellar_sdk.operation.RevokeSponsorship) | [JavaScript](https://stellar.github.io/js-stellar-base/Operation.html#.revokeAccountSponsorship) | [Java](https://javadoc.io/doc/network.lightsail/stellar-sdk/latest/org/stellar/sdk/operations/RevokeAccountSponsorshipOperation.html) | [Go](https://pkg.go.dev/github.com/stellar/go-stellar-sdk/txnbuild#RevokeSponsorship)  
 **Threshold**: Medium  
@@ -528,7 +525,7 @@ This operation is a union with **two** possible types:
 
 | Union Type | Parameters | Type | Description |
 | --- | --- | --- | --- |
-| `REVOKE_SPONSORSHIP_LEDGER_ENTRY` | LedgerKey | ledgerKey | Ledger key that holds information to identify a specific ledgerEntry that may have its sponsorship modified. See [LedgerKey](../../glossary.mdx#ledgerkey) for more information. |
+| `REVOKE_SPONSORSHIP_LEDGER_ENTRY` | LedgerKey | ledgerKey | Ledger key that holds information to identify a specific ledgerEntry that may have its sponsorship modified. See [LedgerKey](../../glossary#ledgerkey) for more information. |
 
 Or
 
@@ -550,7 +547,7 @@ Or
 
 Burns an amount in a specific asset from an account. Only the issuing account for the asset can perform this operation.
 
-Learn more about clawbacks: [Clawback Guide](../../../build/guides/transactions/clawbacks.mdx)
+Learn more about clawbacks: [Clawback Guide](../../../build/guides/transactions/clawbacks)
 
 **SDKs**: [Python](https://stellar-sdk.readthedocs.io/en/stable/api.html#stellar_sdk.operation.Clawback) | [JavaScript](https://stellar.github.io/js-stellar-base/Operation.html#.clawback) | [Java](https://javadoc.io/doc/network.lightsail/stellar-sdk/latest/org/stellar/sdk/operations/ClawbackOperation.html) | [Go](https://pkg.go.dev/github.com/stellar/go-stellar-sdk/txnbuild#Clawback)  
 **Threshold**: Medium  
@@ -576,9 +573,9 @@ Learn more about clawbacks: [Clawback Guide](../../../build/guides/transactions/
 
 Claws back an unclaimed ClaimableBalanceEntry, burning the pending amount of the asset. Only the issuing account for the asset can perform this operation.
 
-Learn more about clawbacks: [Clawback Guide](../../../build/guides/transactions/clawbacks.mdx)
+Learn more about clawbacks: [Clawback Guide](../../../build/guides/transactions/clawbacks)
 
-Learn more about claimable balances: [Claimable Balances Guide](../../../build/guides/transactions/claimable-balances.mdx)
+Learn more about claimable balances: [Claimable Balances Guide](../../../build/guides/transactions/claimable-balances)
 
 **SDKs**: [Python](https://stellar-sdk.readthedocs.io/en/stable/api.html#stellar_sdk.operation.ClawbackClaimableBalance) | [JavaScript](https://stellar.github.io/js-stellar-base/Operation.html#.clawbackClaimableBalance) | [Java](https://javadoc.io/doc/network.lightsail/stellar-sdk/latest/org/stellar/sdk/operations/ClawbackClaimableBalanceOperation.html) | [Go](https://pkg.go.dev/github.com/stellar/go-stellar-sdk/txnbuild#ClawbackClaimableBalance)  
 **Threshold**: Medium  
@@ -603,7 +600,7 @@ Allows issuing account to configure authorization and trustline flags to an asse
 
 The Asset parameter is of the `TrustLineAsset` type. If you are modifying a trustline to a regular asset (i.e. one in a Code:Issuer format), this is equivalent to the Asset type. If you are modifying a trustline to a pool share, however, this is composed of the liquidity pool's unique ID.
 
-Learn more about flags: [Flags Glossary Entry](../../glossary.mdx#flags)
+Learn more about flags: [Flags Glossary Entry](../../glossary#flags)
 
 **SDKs**: [Python](https://stellar-sdk.readthedocs.io/en/stable/api.html#stellar_sdk.operation.SetTrustLineFlags) | [JavaScript](https://stellar.github.io/js-stellar-base/Operation.html#.setTrustLineFlags) | [Java](https://javadoc.io/doc/network.lightsail/stellar-sdk/latest/org/stellar/sdk/operations/SetTrustlineFlagsOperation.html) | [Go](https://pkg.go.dev/github.com/stellar/go-stellar-sdk/txnbuild#SetTrustLineFlags)  
 **Threshold**: Low  
@@ -635,7 +632,7 @@ Parameters to this operation depend on the ordering of assets in the liquidity p
 
 If the pool is empty, then this operation deposits maxAmountA of A and maxAmountB of B into the pool. If the pool is not empty, then this operation deposits at most maxAmountA of A and maxAmountB of B into the pool. The actual amounts deposited are determined using the current reserves of the pool. You can use these parameters to control a percentage of slippage.
 
-Learn more about liquidity pools: [Liquidity Pools section](../liquidity-on-stellar-sdex-liquidity-pools.mdx)
+Learn more about liquidity pools: [Liquidity Pools section](../liquidity-on-stellar-sdex-liquidity-pools)
 
 **SDKs**: [Python](https://stellar-sdk.readthedocs.io/en/stable/api.html#stellar_sdk.operation.LiquidityPoolDeposit) | [JavaScript](https://stellar.github.io/js-stellar-base/Operation.html#.liquidityPoolDeposit) | [Java](https://javadoc.io/doc/network.lightsail/stellar-sdk/latest/org/stellar/sdk/operations/LiquidityPoolDepositOperation.html) | [Go](https://pkg.go.dev/github.com/stellar/go-stellar-sdk/txnbuild#LiquidityPoolDeposit)  
 **Threshold**: Medium  
@@ -668,7 +665,7 @@ Withdraw assets from a liquidity pool, reducing the number of pool shares in exc
 
 The minAmountA and minAmountB parameters can be used to control a percentage of slippage from the "spot price" on the pool.
 
-Learn more about liquidity pools: [Liquidity Pools section](../liquidity-on-stellar-sdex-liquidity-pools.mdx)
+Learn more about liquidity pools: [Liquidity Pools section](../liquidity-on-stellar-sdex-liquidity-pools)
 
 **SDKs**: [Python](https://stellar-sdk.readthedocs.io/en/stable/api.html#stellar_sdk.operation.LiquidityPoolWithdraw) | [JavaScript](https://stellar.github.io/js-stellar-base/Operation.html#.liquidityPoolWithdraw) | [Java](https://javadoc.io/doc/network.lightsail/stellar-sdk/latest/org/stellar/sdk/operations/LiquidityPoolWithdrawOperation.html) | [Go](https://pkg.go.dev/github.com/stellar/go-stellar-sdk/txnbuild#LiquidityPoolWithdraw)  
 **Threshold**: Medium  
@@ -704,7 +701,7 @@ The `InvokeHostFunctionOp` can be used to perform the following Soroban operatio
 
 Note that Soroban transactions can only contain one operation per transaction.
 
-Learn more [here](../../fundamentals/contract-development/contract-interactions/stellar-transaction.mdx#invokehostfunctionop).
+Learn more [here](../../fundamentals/contract-development/contract-interactions/stellar-transaction#invokehostfunctionop).
 
 **SDKs**: [Python](https://stellar-sdk.readthedocs.io/en/stable/api.html#stellar_sdk.operation.InvokeHostFunction) | [JavaScript](https://stellar.github.io/js-stellar-base/Operation.html#.invokeHostFunction) | [Java](https://javadoc.io/doc/network.lightsail/stellar-sdk/latest/org/stellar/sdk/operations/InvokeHostFunctionOperation.html) | [Go](https://pkg.go.dev/github.com/stellar/go-stellar-sdk/txnbuild#InvokeHostFunction)  
 **Threshold**: Medium  
@@ -732,7 +729,7 @@ Extend the time to live (TTL) of entries for Soroban smart contracts with the `E
 
 Note that Soroban transactions can only contain one operation per transaction.
 
-Learn more in the [State Archival section](../../fundamentals/contract-development/storage/state-archival.mdx).
+Learn more in the [State Archival section](../../fundamentals/contract-development/storage/state-archival).
 
 **SDKs**: [Python](https://stellar-sdk.readthedocs.io/en/stable/api.html#stellar_sdk.operation.ExtendFootprintTTL) | [JavaScript](https://stellar.github.io/js-stellar-base/Operation.html#.extendFootprintTtl) | [Java](https://javadoc.io/doc/network.lightsail/stellar-sdk/latest/org/stellar/sdk/operations/ExtendFootprintTTLOperation.html) | [Go](https://pkg.go.dev/github.com/stellar/go-stellar-sdk/txnbuild#ExtendFootprintTtl)  
 **Threshold**: Medium  
@@ -758,7 +755,7 @@ Make archived Soroban smart contract entries accessible again by restoring them
 
 Note that Soroban transactions can only contain one operation per transaction.
 
-Learn more in the [State Archival section](../../fundamentals/contract-development/storage/state-archival.mdx).
+Learn more in the [State Archival section](../../fundamentals/contract-development/storage/state-archival).
 
 **SDKs**: [Python](https://stellar-sdk.readthedocs.io/en/stable/api.html#stellar_sdk.operation.RestoreFootprint) | [JavaScript](https://stellar.github.io/js-stellar-base/Operation.html#.restoreFootprint) | [Java](https://javadoc.io/doc/network.lightsail/stellar-sdk/latest/org/stellar/sdk/operations/RestoreFootprintOperation.html) | [Go](https://pkg.go.dev/github.com/stellar/go-stellar-sdk/txnbuild#RestoreFootprint)  
 **Threshold**: Medium  
diff --git a/docs/learn/fundamentals/transactions/operations-and-transactions.mdx b/docs/learn/fundamentals/transactions/operations-and-transactions.mdx
index f0c340e44..88a000198 100644
--- a/docs/learn/fundamentals/transactions/operations-and-transactions.mdx
+++ b/docs/learn/fundamentals/transactions/operations-and-transactions.mdx
@@ -1,17 +1,14 @@
 ---
-title: "Operations & Transactions: How Blockchain Actions Are Executed"
-sidebar_label: Operations and Transactions
+title: Operations and Transactions
+"og:title": "Operations & Transactions: How Blockchain Actions Are Executed"
 description: "Learn how operations and transactions work on the Stellar network. Understand how multiple operations are bundled into transactions to execute blockchain actions."
-sidebar_position: 10
 ---
 
-# Operations and Transactions
+<Note>
 
-:::note
+Find how-to guides for smart contract and non-smart contract transactions in the [Transactions How-To Guides section](/docs/build/guides/transactions).
 
-Find how-to guides for smart contract and non-smart contract transactions in the [Transactions How-To Guides section](../../../build/guides/transactions/README.mdx).
-
-:::
+</Note>
 
 ## Operations and transactions: how they work
 
@@ -23,25 +20,25 @@ Operations are individual commands that modify the ledger. Operations are used t
 
 All operations fall into one of three threshold categories: low, medium, or high, and each threshold category has a weight between 0 and 255 (which can be determined using set_options). Thresholds determine what signature weight is required for the operation to be accepted. For example, let’s say an account sets the medium threshold weight to 5. If the account wants to successfully establish a trustline with the `changeTrust` operation, the weight of the signature(s) must be greater than or equal to 5.
 
-To learn more about signature weight, see the [Signatures and Multisig section](../../fundamentals/transactions/signatures-multisig.mdx).
+To learn more about signature weight, see the [Signatures and Multisig section](../../fundamentals/transactions/signatures-multisig).
 
-View a comprehensive list of Stellar operations and their threshold levels in the [List of Operations section](./list-of-operations.mdx).
+View a comprehensive list of Stellar operations and their threshold levels in the [List of Operations section](./list-of-operations).
 
 ### Transactions
 
-The Stellar network encodes transactions using a standardized protocol called External Data Representation (XDR). You can read more about this in our [XDR Section](../data-format/xdr.mdx).
+The Stellar network encodes transactions using a standardized protocol called External Data Representation (XDR). You can read more about this in our [XDR Section](../data-format/xdr).
 
 Accounts can only perform one transaction at a time.
 
 Transactions comprise a bundle of between 1-100 operations (except smart contract transactions, which can only have one operation per transaction) and are signed and submitted to the ledger by accounts. Transactions always need to be authorized by the source account’s public key to be valid, which involves signing the transaction object with the public key’s associated secret key. A transaction plus its signature(s) is called a transaction envelope.
 
-A transaction may need more than one signature- this happens if it has operations that affect more than one account or if it has a high threshold weight. Check out the [Signature and Multisignature Section](../../fundamentals/transactions/signatures-multisig.mdx) for more information.
+A transaction may need more than one signature- this happens if it has operations that affect more than one account or if it has a high threshold weight. Check out the [Signature and Multisignature Section](../../fundamentals/transactions/signatures-multisig) for more information.
 
 Transactions are atomic. Meaning if one operation in a transaction fails, all operations fail, and the entire transaction is not applied to the ledger.
 
 Operations are executed for the source account of the transaction unless an operation override is defined.
 
-Smart contract transactions also go through a simulation process where developers can test how the transaction would be executed on the network using the RPC endpoint `simulateTransaction`. Read more in the [Soroban docs](../../fundamentals/contract-development/contract-interactions/transaction-simulation.mdx).
+Smart contract transactions also go through a simulation process where developers can test how the transaction would be executed on the network using the RPC endpoint `simulateTransaction`. Read more in the [Soroban docs](../../fundamentals/contract-development/contract-interactions/transaction-simulation).
 
 ## Memo
 
@@ -49,7 +46,7 @@ Memos are an optional unstructured data field that can be used to embed any addi
 
 They were previously used to differentiate between individual accounts in a pooled account - something we used muxed accounts for now.
 
-For more information on muxed accounts, see our [Pooled Accounts - Muxed Accounts & Memos Guide](../../../build/guides/transactions/pooled-accounts-muxed-accounts-memos.mdx)
+For more information on muxed accounts, see our [Pooled Accounts - Muxed Accounts & Memos Guide](../../../build/guides/transactions/pooled-accounts-muxed-accounts-memos)
 
 Memos can be one of the following types:
 
@@ -67,19 +64,19 @@ Memos can be one of the following types:
 
 #### Transaction attributes
 
-- [Fee](../fees-resource-limits-metering.mdx)
-- [List of operations](./list-of-operations.mdx)
-- [List of signatures](../../fundamentals/transactions/signatures-multisig.mdx)
-- [Memo or muxed account](../../../build/guides/transactions/pooled-accounts-muxed-accounts-memos.mdx)
-- [Sequence number](../../glossary.mdx#sequence-number)
-- [Source account](../../glossary.mdx#source-account)
+- [Fee](../fees-resource-limits-metering)
+- [List of operations](./list-of-operations)
+- [List of signatures](../../fundamentals/transactions/signatures-multisig)
+- [Memo or muxed account](../../../build/guides/transactions/pooled-accounts-muxed-accounts-memos)
+- [Sequence number](../../glossary#sequence-number)
+- [Source account](../../glossary#source-account)
 - [Preconditions (optional)](#preconditions)
 
 ## Transaction and operation validity
 
 Before being successfully submitted to the Stellar network, transactions go through several validity checks. These checks are grouped into three categories:
 
-### Preconditions (optional) {/* #preconditions */}
+### Preconditions (optional) {#preconditions}
 
 Preconditions are checked first.
 
@@ -163,7 +160,7 @@ The fee must be greater than or equal to the network minimum fee for the number
 
 #### Fee-bump (if applicable)
 
-See Validity of a [Fee-Bump Transaction Guide](../../../build/guides/transactions/fee-bump-transactions.mdx) for more information.
+See Validity of a [Fee-Bump Transaction Guide](../../../build/guides/transactions/fee-bump-transactions) for more information.
 
 #### Sequence number
 
diff --git a/docs/learn/fundamentals/transactions/signatures-multisig.mdx b/docs/learn/fundamentals/transactions/signatures-multisig.mdx
index c38f5dd40..c369657c2 100644
--- a/docs/learn/fundamentals/transactions/signatures-multisig.mdx
+++ b/docs/learn/fundamentals/transactions/signatures-multisig.mdx
@@ -1,13 +1,13 @@
 ---
 title: Signatures and Multisig
-sidebar_position: 20
+description: "This section details signing non-smart contract transactions."
 ---
 
-:::note
+<Note>
 
-This section details signing non-smart contract transactions. For auth related to smart contract transactions, see [authorization](../../fundamentals/contract-development/authorization.mdx).)
+This section details signing non-smart contract transactions. For auth related to smart contract transactions, see [authorization](../../fundamentals/contract-development/authorization).)
 
-:::
+</Note>
 
 Signatures are authorization for transactions on the network. Transactions always need authorization from at least one public key to be valid and generally, the signature comes from the source account. Sometimes transactions require more signatures, which we’ll get into in the multisig section.
 
@@ -15,9 +15,9 @@ Transaction signatures are created by signing the transaction object contents wi
 
 ### Thresholds
 
-Each operation falls under a specific threshold category: low, medium, or high with a number level between 0-255 (to read more about this see our section on [Operations and Transactions](../../fundamentals/transactions/operations-and-transactions.mdx#operations)). This threshold determines what signature weight is needed to authorize an operation.
+Each operation falls under a specific threshold category: low, medium, or high with a number level between 0-255 (to read more about this see our section on [Operations and Transactions](../../fundamentals/transactions/operations-and-transactions#operations)). This threshold determines what signature weight is needed to authorize an operation.
 
-To view each operation’s threshold, see our [List of Operations section](../../fundamentals/transactions/list-of-operations.mdx).
+To view each operation’s threshold, see our [List of Operations section](../../fundamentals/transactions/list-of-operations).
 
 Accounts can set their own signature weight, threshold values, and additional signing keys with the Set Options operation. By default, all operation threshold levels are set to 0, and the master key is set to weight 1. For most cases, it is recommended to set thresholds such that `low <= medium <= high`.
 
@@ -50,13 +50,13 @@ Signers of this type are automatically removed from the account when a matching
 
 This type of signer is especially useful in escrow accounts. You can pre-authorize two different transactions. Both could have the same sequence number but different destinations. This means that only one of them can be executed.
 
-#### Hash(x)
+#### Hash(x) {#hashx}
 
-:::note
+<Note>
 
 Hash(x) signing is a different concept from transaction hashes. Transaction hashes are unique identifiers generated by applying a cryptographic hash function to the data of a transaction in a blockchain. They serve as a digital fingerprint and allow users to verify and reference transactions on the network. Hash(x) is a signature type.
 
-:::
+</Note>
 
 Adding a signature of type hash(x) allows anyone who knows x to sign the transaction. This type of signer is especially useful in [atomic cross-chain swaps](https://en.bitcoin.it/wiki/Atomic_cross-chain_trading) which are needed for inter-blockchain protocols like [lightning networks](https://lightning.network).
 
@@ -79,9 +79,9 @@ Multisig allows you to do all of this without exposing the master key of your an
 
 Your account setup:
 
-<CodeExample>
+<CodeGroup>
 
-```
+```text Example
 Master Key Weight: 2
 Additional Signing Key Weight: 1
 Low Threshold: 0
@@ -89,7 +89,7 @@ Medium Threshold: 2
 High Threshold: 2
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Example 2: Joint accounts
 
@@ -97,9 +97,9 @@ You want to set up a joint account with Bilal and Carina such that any of you ca
 
 Joint account setup:
 
-<CodeExample>
+<CodeGroup>
 
-```
+```text Example
 Master Key Weight: 1
 Low Threshold: 0
 Medium Threshold: 0
@@ -108,7 +108,7 @@ Bilal's Signing Key Weight: 1
 Carina's Signing Key Weight: 1
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Example 3: Expense accounts
 
@@ -116,9 +116,9 @@ You fully control an expense account, but you want your two coworkers Diyuan and
 
 Expense account setup:
 
-<CodeExample>
+<CodeGroup>
 
-```
+```text Example
 Master Key Weight: 3
 Low Threshold: 0
 Medium Threshold: 0
@@ -127,7 +127,7 @@ Diyuan's Key Weight: 1
 Emil's Key Weight: 1
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Example 4: Company accounts
 
@@ -137,9 +137,9 @@ Your company wants to set up an account that requires 3 of 6 employees to agree
 
 Company account setup:
 
-<CodeExample>
+<CodeGroup>
 
-```
+```text Example
 Master Key Weight: 0 (Turned off so this account can't do anything without an employee.)
 Low Threshold: 3
 Medium Threshold: 3
@@ -152,4 +152,4 @@ Employee 5 Key Weight: 1
 Employee 6 Key Weight: 1
 ```
 
-</CodeExample>
+</CodeGroup>
diff --git a/docs/learn/fundamentals/transactions/transaction-lifecycle.mdx b/docs/learn/fundamentals/transactions/transaction-lifecycle.mdx
index 881defc96..58098c06f 100644
--- a/docs/learn/fundamentals/transactions/transaction-lifecycle.mdx
+++ b/docs/learn/fundamentals/transactions/transaction-lifecycle.mdx
@@ -1,6 +1,6 @@
 ---
 title: Transaction Lifecycle
-sidebar_position: 30
+description: "A user creates a transaction by setting the source account, sequence number, list of operations and their respective parameters, fee or fee-bump, and..."
 ---
 
 ### 1. Creation (Transaction Creator)
@@ -9,11 +9,11 @@ A user creates a transaction by setting the source account, sequence number, lis
 
 #### 1b. Transaction Simulation
 
-Smart contract transactions undergo transaction simulation, where the transaction is run in a simulated environment to check for errors and ensure it can be executed successfully. Read more in the [Transaction Simulation section](../contract-development/contract-interactions/transaction-simulation.mdx).
+Smart contract transactions undergo transaction simulation, where the transaction is run in a simulated environment to check for errors and ensure it can be executed successfully. Read more in the [Transaction Simulation section](../contract-development/contract-interactions/transaction-simulation).
 
 ### 2. Signing (Transaction Signers)
 
-Once the transaction is complete, it becomes a transaction envelope containing the transaction itself and a list of signers. All the required signatures must be collected and added to the transaction envelope’s list of signers. Commonly, it’s just the signature of the account doing the transaction, but more complicated setups can require collecting signatures from multiple parties. Read more about signatures in the [Signatures and Multisig section](./signatures-multisig.mdx).
+Once the transaction is complete, it becomes a transaction envelope containing the transaction itself and a list of signers. All the required signatures must be collected and added to the transaction envelope’s list of signers. Commonly, it’s just the signature of the account doing the transaction, but more complicated setups can require collecting signatures from multiple parties. Read more about signatures in the [Signatures and Multisig section](./signatures-multisig).
 
 ### 3. Submitting (Transaction Submitter)
 
diff --git a/docs/learn/glossary.mdx b/docs/learn/glossary.mdx
index 72bfaaec5..47ad0d3b1 100644
--- a/docs/learn/glossary.mdx
+++ b/docs/learn/glossary.mdx
@@ -1,17 +1,14 @@
 ---
-title: "Blockchain Glossary: Key Terms and Concepts for Understanding Stellar"
-sidebar_label: Glossary
-sidebar_position: 40
+title: Glossary
+"og:title": "Blockchain Glossary: Key Terms and Concepts for Understanding Stellar"
 description: "Explore a comprehensive glossary of blockchain terms. Learn key concepts, definitions, and technical terms to better understand the Stellar network and ecosystem."
 ---
 
-# Glossary
-
 ### Account
 
 A central Stellar data structure to hold balances, sign transactions, and issue assets.
 
-See the [Accounts section](./fundamentals/stellar-data-structures/accounts.mdx) to learn more.
+See the [Accounts section](./fundamentals/stellar-data-structures/accounts) to learn more.
 
 ### Account ID
 
@@ -21,9 +18,9 @@ The public key used to create an account. This key persists across different key
 
 The on and off-ramps on the Stellar network that facilitate one-to-one conversion of off-chain representations to and from tokenized assets, for example, digital tokens representing bank deposits.
 
-Read more in the [Anchors section](./fundamentals/anchors.mdx).
+Read more in the [Anchors section](./fundamentals/anchors).
 
-### Application (app) {/* #app */}
+### Application (app) {#app}
 
 A software program designed for users to carry out a specific task (other than operating the computer itself).
 
@@ -31,13 +28,13 @@ A software program designed for users to carry out a specific task (other than o
 
 Fiat, physical, or other tokens of value that are tracked, held, or transferred by the Stellar distributed network.
 
-See the [Assets section](./fundamentals/stellar-data-structures/assets.mdx) to learn more.
+See the [Assets section](./fundamentals/stellar-data-structures/assets) to learn more.
 
 ### Atomic Swap
 
 A decentralized method of exchanging one asset for another without the need for a trusted third-party intermediary. Atomic swaps allow the interchange to either complete fully for both parties or not at all, hence the term "atomic," meaning indivisible. If one party fails to fulfill the required conditions, the trade is automatically canceled and both parties retain their assets.
 
-Learn more in the default [Liquidity on Stellar section](./fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx) or an [Atomic Swap example contract](../build/smart-contracts/example-contracts/atomic-swap.mdx).
+Learn more in the default [Liquidity on Stellar section](./fundamentals/liquidity-on-stellar-sdex-liquidity-pools) or an [Atomic Swap example contract](../build/smart-contracts/example-contracts/atomic-swap).
 
 ### Balance
 
@@ -53,13 +50,13 @@ The fee you’re willing to pay per operation in a transaction.
 
 This differs from the Effective Base Fee which is the actual fee paid per operation for a transaction to make it to the ledger. When the network is in surge pricing mode, the effective base fee varies based on an auction mechanism. When it's not, the effective base fee defaults to the network minimum currently at 100 stroops per operation.
 
-Learn more in our [Fees section](./fundamentals/fees-resource-limits-metering.mdx).
+Learn more in our [Fees section](./fundamentals/fees-resource-limits-metering).
 
 ### Base Reserve
 
 A unit of measurement used to calculate an account’s minimum balance. One base reserve is currently 0.5 XLM.
 
-Learn more in our [Lumens section](./fundamentals/lumens.mdx#base-reserves).
+Learn more in our [Lumens section](./fundamentals/lumens#base-reserves).
 
 ### Burn
 
@@ -81,13 +78,13 @@ An object that holds both the destination account that can claim the ClaimableBa
 
 An amount of asset from a trustline or claimable balance removed (clawed back) from a recipient’s balance sheet.
 
-Learn more in our [Clawback guide](../build/guides/transactions/clawbacks.mdx).
+Learn more in our [Clawback guide](../build/guides/transactions/clawbacks).
 
-### Composable Data Platform {/* #cdp */}
+### Composable Data Platform {#cdp}
 
 An architecture for building custom Stellar data pipelines from raw ledger metadata. CDP uses tools such as Galexie to export ledger metadata to external storage, then lets downstream consumers use the Ingest SDK or other processors to transform that data into application-specific models, analytics, indexes, or streams.
 
-Learn more in our [Ingest SDK tutorial](../build/apps/ingest-sdk/overview.mdx) and the [Composable Data Platform announcement](https://stellar.org/blog/developers/composable-data-platform).
+Learn more in our [Ingest SDK tutorial](../build/apps/ingest-sdk/overview) and the [Composable Data Platform announcement](https://stellar.org/blog/developers/composable-data-platform).
 
 ### Contract Account
 
@@ -97,13 +94,13 @@ An account that is implemented as a smart contract, allowing the contract to def
 
 Tokens created and managed through smart contracts. These assets are programmable and governed by on-chain logic instead of built-in protocol features.
 
-:::note
+<Note>
 
 Contract tokens used to be referred to as "custom tokens", which has been deprecated.
 
-:::
+</Note>
 
-### Core Advancement Proposals (CAPs) {/* #caps */}
+### Core Advancement Proposals (CAPs) {#caps}
 
 Proposals of standards to improve the Stellar protocol. CAPs deal with changes to the core protocol of the Stellar network.
 
@@ -125,7 +122,7 @@ This term has been deprecated in favor of [contract tokens](#contract-token).
 
 A distributed exchange that allows the trading and conversion of assets on the network.
 
-Learn more in our [Liquidity on Stellar](./fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx#sdex) section.
+Learn more in our [Liquidity on Stellar](./fundamentals/liquidity-on-stellar-sdex-liquidity-pools#sdex) section.
 
 ### External Data Representation (XDR)
 
@@ -139,13 +136,13 @@ Read more in [GitHub](https://github.com/stellar/stellar-protocol/blob/master/ec
 
 ### Flags
 
-Flags control access to an asset on the account level. Learn more about flags in our [Controlling Access to an Asset section](../tokens/control-asset-access.mdx#controlling-access-to-an-asset-with-flags).
+Flags control access to an asset on the account level. Learn more about flags in our [Controlling Access to an Asset section](../tokens/control-asset-access#controlling-access-to-an-asset-with-flags).
 
 ### Fuzzing
 
 An automated test that rapidly stuffs massive amounts of randomized, malformed data into a system to reveal adverse or unexpected results that indicate vulnerabilities.
 
-Read more in the [Fuzz Testing Tutorial](../build/smart-contracts/example-contracts/fuzzing.mdx).
+Read more in the [Fuzz Testing Tutorial](../build/smart-contracts/example-contracts/fuzzing).
 
 ### GitHub
 
@@ -179,7 +176,7 @@ An encrypted store or file that serves as a repository of private keys, certific
 
 A representation of the state of the Stellar universe at a given point in time, shared across all network nodes.
 
-Learn more in the [Ledgers section](./fundamentals/stellar-data-structures/ledgers.mdx).
+Learn more in the [Ledgers section](./fundamentals/stellar-data-structures/ledgers).
 
 ### LedgerKey
 
@@ -189,17 +186,17 @@ LedgerKey holds information to identify a specific ledgerEntry. It is a union th
 
 A buying or selling obligation, required to satisfy (selling) or accommodate (buying) transactions.
 
-### Lumen (XLM) {/* #lumen */}
+### Lumen (XLM) {#lumen}
 
 The native, built-in token on the Stellar network.
 
-Learn more about lumens in our [Lumens section](./fundamentals/lumens.mdx).
+Learn more about lumens in our [Lumens section](./fundamentals/lumens).
 
 ### Mainnet or Pubnet
 
 The Stellar Public Network, aka mainnet, the main network used by applications in production.
 
-Read more in our [Networks section](../networks/README.mdx).
+Read more in our [Networks section](/docs/networks).
 
 ### Master key
 
@@ -209,7 +206,7 @@ The private key used in initial account creation.
 
 The smallest permissible balance in lumens for a Stellar account, currently 1 lumen.
 
-Learn more in our [Lumens section](./fundamentals/lumens.mdx#minimum-balance).
+Learn more in our [Lumens section](./fundamentals/lumens#minimum-balance).
 
 ### Network capacity
 
@@ -223,7 +220,7 @@ The number of entries owned by an account, used to calculate the account’s min
 
 An individual command that modifies the ledger.
 
-Learn more in our [Operations and Transactions](./fundamentals/transactions/operations-and-transactions.mdx) section.
+Learn more in our [Operations and Transactions](./fundamentals/transactions/operations-and-transactions) section.
 
 ### OperationID
 
@@ -233,13 +230,13 @@ A unique identifier for an operation, derived from the transaction source [Accou
 
 An offer to buy or sell an asset.
 
-Learn more in our [Liquidity on Stellar: SDEX and Liquidity Pools section](./fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx#orders).
+Learn more in our [Liquidity on Stellar: SDEX and Liquidity Pools section](./fundamentals/liquidity-on-stellar-sdex-liquidity-pools#orders).
 
 ### Orderbook
 
 A record of outstanding orders on the Stellar network.
 
-Learn more in our [Liquidity on Stellar: SDEX and Liquidity Pools section](./fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx#order-books).
+Learn more in our [Liquidity on Stellar: SDEX and Liquidity Pools section](./fundamentals/liquidity-on-stellar-sdex-liquidity-pools#order-books).
 
 ### Passive Order
 
@@ -249,13 +246,13 @@ An order that does not execute against a marketable counter order with the same
 
 The Mainnet and Testnet each have their own unique passphrase, which are used to validate signatures on a given transaction.
 
-Learn more about network passphrases in the [Networks section](../networks/README.mdx#network-passphrases).
+Learn more about network passphrases in the [Networks section](/docs/networks#network-passphrases).
 
 ### Pathfinding
 
 The process of determining the best path of a payment, evaluating the current orderbooks, and finding the series of conversions to achieve the best rate.
 
-It happens during [Stellar Core](#stellar-core)'s market-order execution and in [Horizon aggregation](../data/apis/horizon/api-reference/aggregations/README.mdx).
+It happens during [Stellar Core](#stellar-core)'s market-order execution and in [Horizon aggregation](/docs/data/apis/horizon/api-reference/aggregations).
 
 ### Payment Channel
 
@@ -265,7 +262,7 @@ Allows two parties who frequently transact with one another to move the bulk of
 
 Optional requirements you can add to control a transaction’s validity.
 
-See the [Operation and Transaction Validity section](./fundamentals/transactions/operations-and-transactions.mdx#preconditions) for more information.
+See the [Operation and Transaction Validity section](./fundamentals/transactions/operations-and-transactions#preconditions) for more information.
 
 ### Price
 
@@ -289,7 +286,7 @@ A transaction’s sequence number must always increase by one (unless minimum se
 
 Refers to the master key or to any other signing keys added later. A signer is defined as the pair: public key + weight. Signers can be set with the Set Options operation.
 
-See our [Signatures and Multisig section](./fundamentals/transactions/signatures-multisig.mdx) for more information.
+See our [Signatures and Multisig section](./fundamentals/transactions/signatures-multisig) for more information.
 
 ### Smart Contract
 
@@ -317,37 +314,37 @@ An experimental layer 2 payment channel protocol for Stellar that allowed for bi
 
 A decentralized, federated peer-to-peer network that allows people to send payments in any asset anywhere in the world instantaneously, and with minimal fees.
 
-### Stellar Consensus Protocol (SCP) {/* #scp */}
+### Stellar Consensus Protocol (SCP) {#scp}
 
 Provides a way to reach consensus without relying on a closed system to accurately record financial transactions.
 
-See our [SCP section](./fundamentals/stellar-consensus-protocol.mdx) to learn more.
+See our [SCP section](./fundamentals/stellar-consensus-protocol) to learn more.
 
 ### Stellar Core
 
 A replicated state machine that maintains a local copy of a cryptographic ledger and processes transactions against it, in consensus with a set of peers; also, the reference implementation for the peer-to-peer agent that manages the Stellar network.
 
-### Stellar Decentralized Exchange (SDEX) {/* #sdex */}
+### Stellar Decentralized Exchange (SDEX) {#sdex}
 
 An always-on native marketplace for asset conversions. Pay what you want for something else, and trade when someone agrees on price. Or farm yield with deposits that help network liquidity.
 
-Learn more in our [Liquidity on Stellar section](./fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx).
+Learn more in our [Liquidity on Stellar section](./fundamentals/liquidity-on-stellar-sdex-liquidity-pools).
 
-### Stellar Development Foundation (SDF) {/* #sdf */}
+### Stellar Development Foundation (SDF) {#sdf}
 
 A non-profit organization founded to support the development and growth of the Stellar network.
 
-### Stellar Ecosystem Proposals (SEPs) {/* #seps */}
+### Stellar Ecosystem Proposals (SEPs) {#seps}
 
 Standards and protocols to allow the Stellar ecosystem to interoperate.
 
-Learn more in our [SEPs section](./fundamentals/stellar-ecosystem-proposals.mdx).
+Learn more in our [SEPs section](./fundamentals/stellar-ecosystem-proposals).
 
 ### Stellar RPC
 
 A node that provides an interface for submitting transactions and reading data from the Stellar network.
 
-### Stellar.toml {/* #stellar-toml */}
+### Stellar.toml {#stellar-toml}
 
 A formatted configuration file containing published information about a node and an organization. For more, see the [Stellar Info File spec (SEP-1)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md).
 
@@ -359,7 +356,7 @@ As cents are to dollars, stroops are to assets: the smallest unit of an asset, o
 
 The Stellar Test Network is maintained by the Stellar Development Foundation, which developers can use to test applications. Testnet is free to use and provides the same functionality as the main (public) network.
 
-Read more in our [Networks](../networks/README.mdx).
+Read more in our [Networks](/docs/networks).
 
 ### Threshold
 
@@ -367,21 +364,21 @@ The level of access for an operation.
 
 Also used to describe the ratio of validator nodes in a quorum set that must agree in order to reach consensus as part of the Stellar Consensus Protocol.
 
-Read more about operation thresholds in the [Operations and Transactions section](./fundamentals/transactions/operations-and-transactions.mdx#operations).
+Read more about operation thresholds in the [Operations and Transactions section](./fundamentals/transactions/operations-and-transactions#operations).
 
-Learn more about quorum set validators in our [Stellar Consensus Protocol section](./fundamentals/stellar-consensus-protocol.mdx).
+Learn more about quorum set validators in our [Stellar Consensus Protocol section](./fundamentals/stellar-consensus-protocol).
 
 ### Time Bounds
 
 An optional feature you can apply to a transaction to enforce a time limit on the transaction; either the transaction makes it to the ledger or times out (fails) depending on your time parameters.
 
-Read more about time bounds in our [Operation and Transaction Validity section](./fundamentals/transactions/operations-and-transactions.mdx#transaction-and-operation-validity).
+Read more about time bounds in our [Operation and Transaction Validity section](./fundamentals/transactions/operations-and-transactions#transaction-and-operation-validity).
 
 ### Transaction
 
 A group of 1 to 100 operations that modify the ledger state.
 
-Read more in the [Operations and Transactions section](./fundamentals/transactions/operations-and-transactions.mdx#transactions).
+Read more in the [Operations and Transactions section](./fundamentals/transactions/operations-and-transactions#transactions).
 
 ### Transaction Envelope
 
@@ -391,19 +388,19 @@ A transaction plus its signature(s) is called a transaction envelope.
 
 Stellar requires a small fee for all transactions to prevent ledger spam and prioritize transactions during surge pricing.
 
-Learn more in our [Lumens section](./fundamentals/lumens.mdx#transaction-fees).
+Learn more in our [Lumens section](./fundamentals/lumens#transaction-fees).
 
 ### Trustline
 
 An explicit opt-in for an account to hold a particular asset that tracks liabilities, the balance of the asset, and can also limit the amount of an asset that an account can hold.
 
-Learn more in our [Accounts section](./fundamentals/stellar-data-structures/accounts.mdx#trustlines).
+Learn more in our [Accounts section](./fundamentals/stellar-data-structures/accounts#trustlines).
 
-### TTL (Time To Live) {/* #ttl */}
+### TTL (Time To Live) {#ttl}
 
 A smart contract's TTL is how many ledgers remain until the data entry is no longer live.
 
-Read more in the [State Archival section](./fundamentals/contract-development/storage/state-archival.mdx#ttl).
+Read more in the [State Archival section](./fundamentals/contract-development/storage/state-archival#ttl).
 
 ### Type
 
diff --git a/docs/learn/interactive/README.mdx b/docs/learn/interactive/README.mdx
deleted file mode 100644
index 2c3f46179..000000000
--- a/docs/learn/interactive/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Interactive Learning
-sidebar_position: 60
----
-
-import DocCardList from "@theme/DocCardList";
-
-Learn by doing in this collection of resources designed to get you up and running on the Stellar network in no time!
-
-<DocCardList />
diff --git a/docs/learn/interactive/dapp-world.mdx b/docs/learn/interactive/dapp-world.mdx
index c825b4558..760326c64 100644
--- a/docs/learn/interactive/dapp-world.mdx
+++ b/docs/learn/interactive/dapp-world.mdx
@@ -1,6 +1,6 @@
 ---
 title: Master Rust Smart Contract Development on Stellar
-sidebar_position: 30
+description: "Learn to develop secure, efficient smart contracts on the Stellar network using Rust."
 ---
 
 Learn to develop secure, efficient smart contracts on the Stellar network using Rust. This hands-on course is perfect for blockchain developers aiming to leverage Stellar's decentralized ecosystem.
diff --git a/docs/learn/interactive/fca00c.mdx b/docs/learn/interactive/fca00c.mdx
index 715acd932..bcc5c845b 100644
--- a/docs/learn/interactive/fca00c.mdx
+++ b/docs/learn/interactive/fca00c.mdx
@@ -1,6 +1,6 @@
 ---
 title: Fast, Cheap, and 0ut 0f Control
-sidebar_position: 20
+description: "Fast, Cheap, and 0ut 0f Control (FCA00C) is a collection of games and tutorials designed to familiarize you with smart contracts on the Stellar network."
 ---
 
 Fast, Cheap, and 0ut 0f Control (FCA00C) is a collection of games and tutorials designed to familiarize you with smart contracts on the Stellar network. The Tutorial walks you through the basics of smart contract development in a series of six quests. This is a great place to get started learning about Stellar smart contracts and smart contract development.
diff --git a/docs/learn/interactive/index.mdx b/docs/learn/interactive/index.mdx
new file mode 100644
index 000000000..cc59c0729
--- /dev/null
+++ b/docs/learn/interactive/index.mdx
@@ -0,0 +1,22 @@
+---
+title: Interactive Learning
+description: "Learn by doing in this collection of resources designed to get you up and running on the Stellar network in no time!"
+---
+
+<CardGroup cols={2}>
+  <Card title="Stellar Quest" icon="file-lines" href="/docs/learn/interactive/quest">
+
+    Stellar Quest teaches you about Stellar operations and fundamentals in a gamified experience.
+
+  </Card>
+  <Card title="Fast, Cheap, and 0ut 0f Control" icon="file-lines" href="/docs/learn/interactive/fca00c">
+
+    Fast, Cheap, and 0ut 0f Control (FCA00C) is a collection of games and tutorials designed to familiarize you with smart contracts on the Stellar network.
+
+  </Card>
+  <Card title="Master Rust Smart Contract Development on Stellar" icon="file-lines" href="/docs/learn/interactive/dapp-world">
+
+    Learn to develop secure, efficient smart contracts on the Stellar network using Rust.
+
+  </Card>
+</CardGroup>
diff --git a/docs/learn/interactive/quest.mdx b/docs/learn/interactive/quest.mdx
index 367c4c80f..ef0956082 100644
--- a/docs/learn/interactive/quest.mdx
+++ b/docs/learn/interactive/quest.mdx
@@ -1,6 +1,6 @@
 ---
 title: Stellar Quest
-sidebar_position: 10
+description: "Stellar Quest teaches you about Stellar operations and fundamentals in a gamified experience."
 ---
 
 Stellar Quest teaches you about Stellar operations and fundamentals in a gamified experience. It includes three sets of five quests along with an additional three side quests (fee-bumps, minting NFTs, and muxed accounts) and a pioneer quest that teaches you about setting up a wallet.
diff --git a/docs/learn/migrate/README.mdx b/docs/learn/migrate/README.mdx
deleted file mode 100644
index 30f635c37..000000000
--- a/docs/learn/migrate/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Migrate from Another Chain
-sidebar_position: 50
----
-
-import DocCardList from "@theme/DocCardList";
-
-Adapt your existing projects to work with Stellar.
-
-<DocCardList />
diff --git a/docs/learn/migrate/cosmos.mdx b/docs/learn/migrate/cosmos.mdx
index 04e0ecbc0..384ce1231 100644
--- a/docs/learn/migrate/cosmos.mdx
+++ b/docs/learn/migrate/cosmos.mdx
@@ -1,5 +1,4 @@
 ---
-sidebar_position: 30
 title: Cosmos
 description: Migrate your smart contract code from Cosmos to Soroban
 draft: true
diff --git a/docs/learn/migrate/evm/README.mdx b/docs/learn/migrate/evm/README.mdx
deleted file mode 100644
index a97f360a5..000000000
--- a/docs/learn/migrate/evm/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: EVM Networks
-sidebar_position: 10
----
-
-import DocCardList from "@theme/DocCardList";
-
-Adapt your existing Ethereum-compatible smart contracts to work with Stellar.
-
-<DocCardList />
diff --git a/docs/learn/migrate/evm/index.mdx b/docs/learn/migrate/evm/index.mdx
new file mode 100644
index 000000000..eb3e7f390
--- /dev/null
+++ b/docs/learn/migrate/evm/index.mdx
@@ -0,0 +1,32 @@
+---
+title: EVM Networks
+description: "Adapt your existing Ethereum-compatible smart contracts to work with Stellar."
+---
+
+<CardGroup cols={2}>
+  <Card title="Introduction to Solidity, Rust, and Soroban" icon="file-lines" href="/docs/learn/migrate/evm/introduction-to-solidity-and-rust">
+
+    Explore the fundamentals of Solidity, Rust, and Soroban.
+
+  </Card>
+  <Card title="Solidity and Rust Syntax, Data Types, and Basic Constructs" icon="file-lines" href="/docs/learn/migrate/evm/solidity-and-rust-basics">
+
+    Explore the fundamentals of Solidity and Rust Syntax, Data Types, and Basic Constructs.
+
+  </Card>
+  <Card title="Advanced Smart Contract Concepts with Solidity and Rust" icon="file-lines" href="/docs/learn/migrate/evm/solidity-and-rust-advanced-concepts">
+
+    Learn advanced Solidity and Rust concepts and write safe and efficient smart contracts.
+
+  </Card>
+  <Card title="Smart Contract Development with Soroban and Hardhat" icon="file-lines" href="/docs/learn/migrate/evm/smart-contract-deployment">
+
+    Explore advanced Solidity and Soroban concepts, craft secure and efficient Soroban smart contracts and deploy and test your contracts in a testnet environment.
+
+  </Card>
+  <Card title="Solidity support via Solang" icon="file-lines" href="/docs/learn/migrate/evm/solidity-support-via-solang">
+
+    Compile Solidity contracts to Wasm for Stellar using the Solang compiler.
+
+  </Card>
+</CardGroup>
diff --git a/docs/learn/migrate/evm/introduction-to-solidity-and-rust.mdx b/docs/learn/migrate/evm/introduction-to-solidity-and-rust.mdx
index 683515bec..b72bd0fdb 100644
--- a/docs/learn/migrate/evm/introduction-to-solidity-and-rust.mdx
+++ b/docs/learn/migrate/evm/introduction-to-solidity-and-rust.mdx
@@ -1,11 +1,10 @@
 ---
-sidebar_position: 0
-title: Introduction to Solidity, Rust, and Soroban
+title: Introduction
+sidebarTitle: "Introduction to Solidity, Rust, and Soroban"
+"og:title": "Introduction to Solidity, Rust, and Soroban"
 description: Explore the fundamentals of Solidity, Rust, and Soroban.
 ---
 
-# Introduction
-
 We are excited to introduce you to Soroban, a powerful smart contracts platform designed to be sensible, built-to-scale, and developer-friendly, with a focus on Rust's performance and safety benefits. With its user-friendly interface and powerful features, Soroban offers an ideal platform for developers who are seeking a more efficient and effective way to build decentralized applications and transition from Solidity to Rust. In this article, we will explore the fundamentals of Solidity, Rust, and Soroban, and guide you through setting up the development environment to start your journey with Soroban's Rust smart contract compatibility.
 
 ## Solidity and Dapp Development
@@ -24,7 +23,7 @@ You can learn more about Soroban's features and benefits in the [Soroban Overvie
 
 ## Setting Up the Development Environment for Rust and Soroban
 
-To get started with Rust and Soroban, follow the steps on the [Setup Page](../../../build/smart-contracts/getting-started/setup.mdx).
+To get started with Rust and Soroban, follow the steps on the [Setup Page](../../../build/smart-contracts/getting-started/setup).
 
 Or if you want to jump right in, you can open up our examples in a ready to go dev Environment in Devcontainers by clicking the button below:
 
@@ -35,6 +34,6 @@ Or if you want to jump right in, you can open up our examples in a ready to go d
 [open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
 [open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
 
-# Summary
+## Summary
 
 As you embark on your journey with Soroban, remember that the platform is designed to provide a seamless, efficient, and enjoyable experience for developers transitioning from Solidity to Rust. By leveraging Rust's performance and safety benefits, alongside Soroban's advanced tooling, you'll be well-equipped to develop high-quality, efficient, and secure smart contracts.
diff --git a/docs/learn/migrate/evm/smart-contract-deployment.mdx b/docs/learn/migrate/evm/smart-contract-deployment.mdx
index cba05c081..2584a7252 100644
--- a/docs/learn/migrate/evm/smart-contract-deployment.mdx
+++ b/docs/learn/migrate/evm/smart-contract-deployment.mdx
@@ -1,14 +1,8 @@
 ---
-sidebar_position: 3
 title: Smart Contract Development with Soroban and Hardhat
 description: Explore advanced Solidity and Soroban concepts, craft secure and efficient Soroban smart contracts and deploy and test your contracts in a testnet environment.
 ---
 
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-# Smart Contract Development with Soroban and Hardhat
-
 In this tutorial, we will discover the similarities in smart contract deployment by examining workflows with Soroban and [Hardhat](https://hardhat.org). We will dive into the intricacies of each framework, learn to write secure and efficient smart contract code, and harness the power of Rust and Soroban to create customized contract logic.
 
 ## Table of Contents
@@ -26,7 +20,7 @@ Soroban and Hardhat are both frameworks that enable developers to build, test, a
 
 ### Soroban Framework
 
-Soroban is a Rust-based framework tailored for developing smart contracts on the Stellar network. Designed as a lightweight framework, with [tools to support developers](../../../tools/developer-tools/README.mdx), Soroban allows developers to develop smart contracts through a simple and intuitive workflow.
+Soroban is a Rust-based framework tailored for developing smart contracts on the Stellar network. Designed as a lightweight framework, with [tools to support developers](/docs/tools/developer-tools), Soroban allows developers to develop smart contracts through a simple and intuitive workflow.
 
 ### Hardhat
 
@@ -44,9 +38,9 @@ Soroban, with its lightweight design, offers developers an exceptional platform
 
 Hardhat offers a streamlined workflow for deploying smart contracts on the Ethereum Virtual Machine, with key components such as `ethers.js`, `scripts`, and `testing` playing crucial roles.
 
-On the other hand, Soroban presents a compelling alternative, boasting powerful SDKs that facilitate smart contract development and deployment. In the upcoming section, we will delve into [Soroban's SDKs](../../../tools/sdks/README.mdx), drawing comparisons with Hardhat components, and highlighting the unique advantages each platform brings to the table.
+On the other hand, Soroban presents a compelling alternative, boasting powerful SDKs that facilitate smart contract development and deployment. In the upcoming section, we will delve into [Soroban's SDKs](/docs/tools/sdks), drawing comparisons with Hardhat components, and highlighting the unique advantages each platform brings to the table.
 
-### Ethers.js
+### Ethers.js {#ethersjs}
 
 `Ethers.js` is a widely-used `JavaScript` library designed for seamless interaction with the EVM. It offers a user-friendly interface that simplifies connecting to Ethereum nodes, managing accounts, and sending transactions. Additionally, `Ethers.js` provides a robust API for efficient communication with smart contracts. This library is a core component of the Hardhat framework and can be imported into scripts to streamline the deployment of smart contracts.
 
@@ -62,7 +56,7 @@ async function main() {
 
 ### Soroban Client
 
-Soroban offers a comparable library, [`stellar-sdk`](../../../tools/sdks/client-sdks.mdx#javascript-sdk), that enables seamless interaction smart contracts deployed on the Stellar Network. This library supplies a comprehensive networking layer API for Stellar RPC methods as well as the Horizon API (nearing end-of-life), simplifying the process of building and signing transactions. Additionally, `stellar-sdk` streamlines communication with RPC instances and supports submitting transactions or querying network state with ease.
+Soroban offers a comparable library, [`stellar-sdk`](../../../tools/sdks/client-sdks#javascript-sdk), that enables seamless interaction smart contracts deployed on the Stellar Network. This library supplies a comprehensive networking layer API for Stellar RPC methods as well as the Horizon API (nearing end-of-life), simplifying the process of building and signing transactions. Additionally, `stellar-sdk` streamlines communication with RPC instances and supports submitting transactions or querying network state with ease.
 
 ### Scripts
 
@@ -89,7 +83,7 @@ main()
 
 ### Soroban Scripts
 
-Soroban offers an extensive collection of SDKs that include scripting capabilities, ensuring a smooth workflow for deploying and managing smart contracts. Developers can automate tasks such as compiling, deploying, and interacting with smart contracts using a variety of SDKs that support scripting in languages like [`JavaScript`, `TypeScript`, `Python`, and others](../../../tools/sdks/client-sdks.mdx).
+Soroban offers an extensive collection of SDKs that include scripting capabilities, ensuring a smooth workflow for deploying and managing smart contracts. Developers can automate tasks such as compiling, deploying, and interacting with smart contracts using a variety of SDKs that support scripting in languages like [`JavaScript`, `TypeScript`, `Python`, and others](../../../tools/sdks/client-sdks).
 
 ```python
 # This example shows how to deploy a compiled contract to the Stellar network.
@@ -176,7 +170,7 @@ In summary, while Hardhat provides an excellent environment for deploying smart
 
 ## Developing Smart Contracts with Rust and Soroban
 
-### Introduction
+### Introduction {#introduction-1}
 
 Now that we've examined the deployment workflow with Hardhat, let's explore developing and deploying smart contracts with Rust and Soroban. The key advantage of using Soroban is its ability to leverage Rust's safety features and performance, making it an excellent choice for developing secure and efficient smart contracts.
 
@@ -184,7 +178,7 @@ We've learned that Smart contracts are self-executing contracts that can be prog
 
 ### Setup
 
-If you haven't already setup up the dev environment for Soroban, you can get started by following the steps on the [Setup Page](../../../build/smart-contracts/getting-started/setup.mdx).
+If you haven't already setup up the dev environment for Soroban, you can get started by following the steps on the [Setup Page](../../../build/smart-contracts/getting-started/setup).
 
 This project requires using the `soroban_token_contract.wasm` file which you will need to import manually.
 
@@ -284,7 +278,7 @@ In this project we will need to create 3 files:
 To interact with the token contract, we'll use a built in interface that you can find in the `token_interface.rs` tab. The token sets its admin and metadata in a `__constructor` function, which the host runs as part of the deployment itself, and exposes a `mint` function that we will use to mint tokens for our vault contract. Because the constructor runs at deployment, there is no separate initialization call to make — or to front-run. If you want to see the full code of the token contract, you can check it out [here](https://github.com/stellar/soroban-examples/tree/main/token/src).
 
 <Tabs>
-<TabItem value="lib.rs" label="src/lib.rs">
+<Tab title="src/lib.rs">
 
 ```rust
 #![no_std]
@@ -473,8 +467,8 @@ impl VaultTrait for Vault {
 }
 ```
 
-</TabItem>
-<TabItem value="test.rs" label="src/test.rs" default>
+</Tab>
+<Tab title="src/test.rs">
 
 ```rust
 #![cfg(test)]
@@ -588,9 +582,9 @@ fn test() {
 }
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="token.rs" label="src/token.rs">
+<Tab title="src/token.rs">
 
 ```rust
 #![allow(unused)]
@@ -618,9 +612,9 @@ pub fn create_contract(
 }
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="token_interface.rs" label="src/token_interface.rs">
+<Tab title="src/token_interface.rs">
 
 ```rust
 //! This contract demonstrates a sample implementation of the Soroban token
@@ -842,7 +836,7 @@ impl TokenTrait for Token {
 }
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
 
 Now that we've added these files to our project, let's break down what happens in the `lib.rs` file above and discover how "yield" is generated from our vault contract
@@ -923,7 +917,7 @@ If the user were to call the `withdraw` method with 100 shares, the following wo
 - 100 shares would be burned.
 - 100 + (100/100) tokens would be transferred from the vault contract to the withdrawer.
 
-### Testing
+### Testing {#testing-1}
 
 To test the vault contract, we will can simply run the following command in our terminal from our vault contract directory:
 
@@ -950,15 +944,15 @@ Below you will find a series of commands that will help you build, deploy and in
 > _Note_ : If you decide to use scripts, be sure to double-check your import paths.
 
 <Tabs>
-<TabItem value="build" label="build.sh">
+<Tab title="build.sh">
 
 ```bash
 stellar contract build
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="deploy token" label="deploy_token.sh">
+<Tab title="deploy_token.sh">
 
 Everything after the `--` is passed to the token's `__constructor`, so the token is deployed and initialized in one transaction.
 
@@ -975,9 +969,9 @@ stellar contract deploy \
     --symbol <TOKEN_SYMBOL>
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="mint" label="mint.sh">
+<Tab title="mint.sh">
 
 ```bash
 stellar contract invoke \
@@ -991,9 +985,9 @@ stellar contract invoke \
     --amount 100
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="balance" label="balance.sh">
+<Tab title="balance.sh">
 
 ```bash
 stellar contract invoke \
@@ -1006,9 +1000,9 @@ stellar contract invoke \
     --id <USER_OR_VAULT_ADDRESS>
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="upload wasm" label="upload.sh">
+<Tab title="upload.sh">
 
 ```bash
 stellar contract upload \
@@ -1018,9 +1012,9 @@ stellar contract upload \
     --network-passphrase 'Test SDF Network ; September 2015'
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="deploy vault" label="deploy_vault.sh">
+<Tab title="deploy_vault.sh">
 
 Everything after the `--` is passed to the vault's `__constructor`, so `upload.sh` must be run first to get the token Wasm hash.
 
@@ -1035,9 +1029,9 @@ stellar contract deploy \
     --token <TOKEN_CONTRACT_ADDRESS>
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="get share" label="share_id.sh">
+<Tab title="share_id.sh">
 
 ```bash
 stellar contract invoke \
@@ -1049,9 +1043,9 @@ stellar contract invoke \
     share_id
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="deposit" label="deposit.sh">
+<Tab title="deposit.sh">
 
 ```bash
 stellar contract invoke \
@@ -1065,9 +1059,9 @@ stellar contract invoke \
     --amount 100
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="reserve" label="get_rsrv.sh">
+<Tab title="get_rsrv.sh">
 
 ```bash
 stellar contract invoke \
@@ -1079,9 +1073,9 @@ stellar contract invoke \
     get_rsrvs
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="withdraw" label="withdraw.sh">
+<Tab title="withdraw.sh">
 
 ```bash
 stellar contract invoke \
@@ -1095,7 +1089,7 @@ stellar contract invoke \
     --amount 100
 ```
 
-</TabItem>
+</Tab>
 
 </Tabs>
 
diff --git a/docs/learn/migrate/evm/solidity-and-rust-advanced-concepts.mdx b/docs/learn/migrate/evm/solidity-and-rust-advanced-concepts.mdx
index 0cbb1f248..a0624d71a 100644
--- a/docs/learn/migrate/evm/solidity-and-rust-advanced-concepts.mdx
+++ b/docs/learn/migrate/evm/solidity-and-rust-advanced-concepts.mdx
@@ -1,14 +1,8 @@
 ---
-sidebar_position: 2
 title: Advanced Smart Contract Concepts with Solidity and Rust
 description: Learn advanced Solidity and Rust concepts and write safe and efficient smart contracts.
 ---
 
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-# Advanced Smart Contract Concepts with Solidity and Rust
-
 In this tutorial, we will cover advanced Solidity and Rust concepts such as inheritance, interfaces, libraries, and modifiers. Additionally, we will learn how to write safe and efficient Rust code for smart contracts. Finally, we will learn how to convert common Solidity concepts to Rust.
 
 ## Table of Contents
@@ -170,7 +164,7 @@ impl AllocContract {
 
 In this example, the `alloc` crate is imported into the smart contract using the `extern crate alloc;` statement. The `alloc` crate is then used to create a temporary vector that holds values from 0 to `count`. The values in the vector are then summed and returned.
 
-For more details on how to use the `alloc` crate, including a hands-on practical exercise, visit the [alloc example contract](../../../build/smart-contracts/example-contracts/alloc.mdx#how-it-works).
+For more details on how to use the `alloc` crate, including a hands-on practical exercise, visit the [alloc example contract](../../../build/smart-contracts/example-contracts/alloc#how-it-works).
 
 #### Inheriting Functionality from Other Crates
 
@@ -405,17 +399,17 @@ Here's a breakdown of the code above:
 
 It's worth mentioning that the Soroban Rust SDK comes with several built-in requirements that developers can use, such as the [`require_auth`](https://docs.rs/soroban-sdk/latest/soroban_sdk/struct.Address.html#method.require_auth) method provided by the `Address` struct.
 
-### Interfaces
+### Interfaces {#interfaces-1}
 
 Interfaces are an essential part of building smart contracts with Soroban.
 
-There are many types of smart contract interfaces, and each has a specific purpose. One example of an interface built with Soroban is the [Token Interface](../../../tokens/token-interface.mdx). This interface ensures that tokens deployed on Soroban are interoperable with Soroban's built-in tokens (such as the Stellar Asset Contract). The Token Interface consists of three compatibility requirements:
+There are many types of smart contract interfaces, and each has a specific purpose. One example of an interface built with Soroban is the [Token Interface](../../../tokens/token-interface). This interface ensures that tokens deployed on Soroban are interoperable with Soroban's built-in tokens (such as the Stellar Asset Contract). The Token Interface consists of three compatibility requirements:
 
 - `function interface`
 - `authorization`
 - `events`
 
-For more information on smart contract interfaces built with Soroban, including the Token Interface, visit the [tokens section](../../../tokens/README.mdx) of the documentation.
+For more information on smart contract interfaces built with Soroban, including the Token Interface, visit the [tokens section](/docs/tokens) of the documentation.
 
 ## Writing Safe and Efficient Rust Code for Smart Contracts
 
@@ -542,7 +536,7 @@ In contrast to Solidity's global variables, Soroban relies on passing an [`Env`]
 
 The `Env` provides access to information about the currently executing contract, who invoked it, contract data, functions for signing, hashing, etc.
 
-For instance, you would use `env.storage().persistent().get(key)` to access a `persistent` target value from the contract's [storage](https://docs.rs/soroban-sdk/latest/soroban_sdk/struct.Env.html). Read more about the different storage types [here](../../fundamentals/contract-development/storage/persisting-data.mdx).
+For instance, you would use `env.storage().persistent().get(key)` to access a `persistent` target value from the contract's [storage](https://docs.rs/soroban-sdk/latest/soroban_sdk/struct.Env.html). Read more about the different storage types [here](../../fundamentals/contract-development/storage/persisting-data).
 
 - `env.storage()` is used to get a struct for accessing and updating contract data that has been stored.
 - Used as `env.storage().persistent().get()` or `env.persistent().storage().set()`.
@@ -587,7 +581,7 @@ use soroban_sdk::{Env, Address};
 
 The Soroban Rust SDK and Solidity provide a number of ways to handle errors. These include:
 
-#### Solidity
+#### Solidity {#solidity-1}
 
 Solidity provides a `require` function that can be used to check for certain conditions and revert the transaction if they are not met. For example, the following code sets a minimum value for the amount of Ether sent with the transaction:
 
@@ -599,7 +593,7 @@ function deposit() public payable {
 }
 ```
 
-#### Soroban
+#### Soroban {#soroban-1}
 
 The [panic!](https://doc.rust-lang.org/book/ch09-00-error-handling.html) macro serves as Rust's error-handling mechanism, which closely resembles the `require` function in Solidity.
 
@@ -898,7 +892,7 @@ By utilizing these authorization methods provided by the `Address` object from t
 
 Soroban's approach to authorization in this example offers several advantages over Solidity's model of ERC20 by eliminating the need for separate approval management. Instead, authorization checks can be directly incorporated into any Soroban function. This simplifies the contract codebase and reduces the complexity associated with managing separate approval states.
 
-Soroban authorization provides Contract-level Authorization, Account Abstraction Functionality, and more advanced Authorization checks. To learn more about these advantages, visit the [Authorization section](../../fundamentals/contract-development/authorization.mdx) of the documentation.
+Soroban authorization provides Contract-level Authorization, Account Abstraction Functionality, and more advanced Authorization checks. To learn more about these advantages, visit the [Authorization section](../../fundamentals/contract-development/authorization) of the documentation.
 
 ## Summary
 
diff --git a/docs/learn/migrate/evm/solidity-and-rust-basics.mdx b/docs/learn/migrate/evm/solidity-and-rust-basics.mdx
index 9bdbb5131..b02c03286 100644
--- a/docs/learn/migrate/evm/solidity-and-rust-basics.mdx
+++ b/docs/learn/migrate/evm/solidity-and-rust-basics.mdx
@@ -1,11 +1,10 @@
 ---
-sidebar_position: 1
-title: Solidity and Rust Syntax, Data Types, and Basic Constructs
+title: Getting Started with Rust and Solidity
+sidebarTitle: "Solidity and Rust Syntax, Data Types, and Basic Constructs"
+"og:title": "Solidity and Rust Syntax, Data Types, and Basic Constructs"
 description: Explore the fundamentals of Solidity and Rust Syntax, Data Types, and Basic Constructs.
 ---
 
-# Getting Started with Rust and Solidity
-
 In this tutorial, we'll explore Rust and Solidity, two powerful programming languages. Rust, a systems programming language, is renowned for its safety, concurrency, and performance features, which can be advantageous when building smart contracts. On the other hand, Solidity is a high-level language specifically designed for creating smart contracts on the Ethereum Virtual Machine. This section aims to provide a high-level overview of the similarities and differences between the two languages.
 
 ## Table of Contents
@@ -107,7 +106,7 @@ Some of the basic constructs in Solidity include:
 4. `Events`: Used to log changes in the contract state.
 5. `Inheritance`: Solidity supports single and multiple inheritance.
 
-We will explore some of these constructs in more detail in the next article, [Advanced Solidity Concepts](./solidity-and-rust-advanced-concepts.mdx#advanced-solidity-concepts).
+We will explore some of these constructs in more detail in the next article, [Advanced Solidity Concepts](./solidity-and-rust-advanced-concepts#advanced-solidity-concepts).
 
 ### Rust Syntax
 
@@ -119,9 +118,9 @@ fn main() {
 }
 ```
 
-### Data Types
+### Data Types {#data-types-1}
 
-The [Soroban Rust SDK](https://docs.rs/soroban-sdk/latest/soroban_sdk/index.html) supports a variety of [Built-In Types](../../fundamentals/contract-development/types/built-in-types.mdx) which consist of both Primitive and [Custom Types](../../fundamentals/contract-development/types/custom-types.mdx), such as:
+The [Soroban Rust SDK](https://docs.rs/soroban-sdk/latest/soroban_sdk/index.html) supports a variety of [Built-In Types](../../fundamentals/contract-development/types/built-in-types) which consist of both Primitive and [Custom Types](../../fundamentals/contract-development/types/custom-types), such as:
 
 #### Primitive Data Types
 
@@ -320,7 +319,7 @@ Rust enforces [**strict ownership rules**](https://doc.rust-lang.org/book/ch04-0
 
 Contract development in Rust involves certain restrictions due to either unavailable features in the deployment environment or high runtime costs. Thus, the code written for contracts can be seen as a distinct _dialect_ of Rust, focusing on deterministic behavior and minimized code size.
 
-To learn more about Rust's Contract Dialect, check out the [Contract Rust Dialect Page](../../fundamentals/contract-development/rust-dialect.mdx).
+To learn more about Rust's Contract Dialect, check out the [Contract Rust Dialect Page](../../fundamentals/contract-development/rust-dialect).
 
 ## Writing and Interacting with Simple Smart Contracts
 
@@ -453,7 +452,7 @@ impl IncrementContract {
 }
 ```
 
-This code is an implementation of a smart contract written in Rust using the [`Soroban Rust SDK`](../../../tools/sdks/contract-sdks.mdx#soroban-rust-sdk), a Rust-based smart contract development toolkit developed by the [Stellar Development Foundation (SDF)](https://stellar.org/foundation). The Soroban Rust SDK provides a powerful set of tools for writing smart contracts that run on the Soroban Virtual Machine.
+This code is an implementation of a smart contract written in Rust using the [`Soroban Rust SDK`](../../../tools/sdks/contract-sdks#soroban-rust-sdk), a Rust-based smart contract development toolkit developed by the [Stellar Development Foundation (SDF)](https://stellar.org/foundation). The Soroban Rust SDK provides a powerful set of tools for writing smart contracts that run on the Soroban Virtual Machine.
 
 Here's a line-by-line explanation of what the code is doing:
 
@@ -539,7 +538,7 @@ env.storage().instance().get(&COUNTER).unwrap_or(0)
 
 This is a repeat of the code we saw earlier, which retrieves the value associated with the key `COUNTER` from the contract storage. If there is no value set for the key `COUNTER`, a default value of 0 is used. Finally, the `unwrap()` method is called to extract the actual value from the `Ok` wrapper, which is then returned to the caller of the function.
 
-Now that we have written our smart contract, it's time to explore how we can interact with it using the [Stellar CLI](../../../tools/cli/stellar-cli.mdx), one of many robust [Developer Tools](../../../tools/developer-tools/README.mdx) available. This powerful command-line tool allows us to interact with the Soroban Virtual Machine from a local machine, providing us with an efficient and flexible way to manage our smart contract.
+Now that we have written our smart contract, it's time to explore how we can interact with it using the [Stellar CLI](../../../tools/cli/stellar-cli), one of many robust [Developer Tools](/docs/tools/developer-tools) available. This powerful command-line tool allows us to interact with the Soroban Virtual Machine from a local machine, providing us with an efficient and flexible way to manage our smart contract.
 
 ### Interacting with the Rust Smart Counter
 
@@ -593,7 +592,7 @@ inherits = "release"
 debug-assertions = true
 ```
 
-> _Note_: For a detailed explanation of the `Cargo.toml` configuration used in this tutorial, check out the [Hello World Example](../../../build/smart-contracts/getting-started/hello-world.mdx).
+> _Note_: For a detailed explanation of the `Cargo.toml` configuration used in this tutorial, check out the [Hello World Example](../../../build/smart-contracts/getting-started/hello-world).
 
 Next, build the project using the `stellar contract build` command.
 
diff --git a/docs/learn/migrate/evm/solidity-support-via-solang.mdx b/docs/learn/migrate/evm/solidity-support-via-solang.mdx
index db645d80f..87c83aed1 100644
--- a/docs/learn/migrate/evm/solidity-support-via-solang.mdx
+++ b/docs/learn/migrate/evm/solidity-support-via-solang.mdx
@@ -1,21 +1,20 @@
 ---
-sidebar_position: 4
 title: Solidity support via Solang
 description: Compile Solidity contracts to Wasm for Stellar using the Solang compiler.
 ---
 
 Leverage the Hyperledger Solang compiler to compile Solidity contracts to Soroban.
 
-- Learn about the Solidity SDK and links to Solang in Tools: [Contract SDKs](../../../tools/sdks/contract-sdks.mdx)
+- Learn about the Solidity SDK and links to Solang in Tools: [Contract SDKs](../../../tools/sdks/contract-sdks)
 - Solang docs (Soroban target): https://solang.readthedocs.io/en/latest/targets/soroban.html
 - Solang repository and examples: https://github.com/hyperledger/solang/tree/main/examples/soroban
 - Solang Web IDE: https://solang.io/
 
-:::caution
+<Warning>
 
 Solidity support via Solang for Stellar is experimental and evolving. Not all Solidity features are supported yet, and breaking changes may occur. We Don't recommend using Solang for production contracts at this time.
 
-:::
+</Warning>
 
 - The easiest way to use Solang is via the Web IDE, but you can also build Solang from source or use prebuilt binaries.
 - For deployment and interaction, use the Stellar CLI and client SDKs after compiling your Wasm artifact.
diff --git a/docs/learn/migrate/index.mdx b/docs/learn/migrate/index.mdx
new file mode 100644
index 000000000..b6a41bda9
--- /dev/null
+++ b/docs/learn/migrate/index.mdx
@@ -0,0 +1,12 @@
+---
+title: Migrate from Another Chain
+description: "Adapt your existing projects to work with Stellar."
+---
+
+<CardGroup cols={2}>
+  <Card title="EVM Networks" icon="box-archive" href="/docs/learn/migrate/evm">
+
+    5 items
+
+  </Card>
+</CardGroup>
diff --git a/docs/learn/migrate/near.mdx b/docs/learn/migrate/near.mdx
index b5db4667f..9fc0ea126 100644
--- a/docs/learn/migrate/near.mdx
+++ b/docs/learn/migrate/near.mdx
@@ -1,5 +1,4 @@
 ---
-sidebar_position: 40
 title: Near
 description: Migrate your smart contract code from Near to Soroban
 draft: true
diff --git a/docs/learn/migrate/solana.mdx b/docs/learn/migrate/solana.mdx
index 89792c531..fbaeb6836 100644
--- a/docs/learn/migrate/solana.mdx
+++ b/docs/learn/migrate/solana.mdx
@@ -1,5 +1,4 @@
 ---
-sidebar_position: 20
 title: Solana
 description: Migrate your smart contract code from Solana to Soroban
 draft: true
diff --git a/docs/networks/README.mdx b/docs/networks/README.mdx
deleted file mode 100644
index fa73ef324..000000000
--- a/docs/networks/README.mdx
+++ /dev/null
@@ -1,137 +0,0 @@
----
-sidebar_position: 20
-sidebar_label: Networks Overview
-title: "Explore Mainnet, Testnet & Futurenet: Roles, Use Cases & Connectivity"
-description: "Explore the different networks, including Mainnet, Testnet, and Futurenet. Learn their roles, use cases, and how to connect for development and testing."
----
-
-# Networks
-
-Stellar has three networks: the public network (Mainnet, also called Pubnet or the Public Network), the test network (Testnet), and a dev network (Futurenet).
-
-- **Mainnet** is the main network used by applications in production. It connects to real financial rails and requires XLM to cover minimum balances, transaction fees, and rent.
-- **Testnet** is a smaller, free-to-use network maintained by SDF that functions like Mainnet but doesn't connect to real money. It resets on a regular cadence, making it the best place for developers to test applications in a stable environment that mirrors Mainnet functionality.
-- **Futurenet** is a dev network for testing bleeding-edge features. It resets whenever necessary, so it's less predictable than Testnet, but it's where new features are introduced before stable releases.
-
-## Network Comparison
-
-| Feature | Mainnet | Testnet | Futurenet |
-| --- | --- | --- | --- |
-| **Purpose** | Production network | Stable testing environment | Bleeding-edge feature testing |
-| **Network Passphrase** | `Public Global Stellar Network ; September 2015` | `Test SDF Network ; September 2015` | `Test SDF Future Network ; October 2022` |
-| **Network ID** | <code style={{overflowWrap:'anywhere'}}>7ac33997544e3175d266bd022439b22cdb16508c01163f26e5cb2a3e1045a979</code> | <code style={{overflowWrap:'anywhere'}}>cee0302d59844d32bdca915c8203dd44b33fbb7edc19051ea37abedf28ecd472</code> | <code style={{overflowWrap:'anywhere'}}>a3a1c6a78286713e29be0e9785670fa838d13917cd8eaeb4a3579ff1debc7fd5</code> |
-| **Validator Nodes** | Run by the public | SDF runs three core validator nodes | SDF runs core validator nodes |
-| **Validator** | `core-live-a.stellar.org` `core-live-b.stellar.org` `core-live-c.stellar.org` | `core-live-testnet.stellar.org` | `core-live-futurenet.stellar.org` |
-| **Funding** | Real XLM required from another account | Free via Friendbot | Free via Friendbot |
-| **Horizon API** | [Multiple providers available](../data/apis/horizon/providers.mdx) | https://horizon-testnet.stellar.org | https://horizon-futurenet.stellar.org |
-| **Stellar RPC** | [Third-party providers only](../data/apis/rpc/providers.mdx) | `https://soroban-testnet.stellar.org` | `https://rpc-futurenet.stellar.org` |
-| **Operations per Ledger** | 1,000\* | 200\* | 1,000\* |
-| **Smart Contract Transactions per Ledger** | Max 2,000\* | Max 2,000\* | Max 2,000\* |
-| **Network Resets** | Never | Regular cadence | As needed (unpredictable) |
-| **Friendbot Available** | No | Yes (10,000 XLM) | Yes (10,000 XLM) |
-| **Friendbot API** | N/A | `https://friendbot.stellar.org` | `https://friendbot-futurenet.stellar.org` |
-| **History Archive** | `http://history.stellar.org/prd/core-live/core_live_001/`, `http://history.stellar.org/prd/core-live/core_live_002/`, `http://history.stellar.org/prd/core-live/core_live_003/` | `http://history.stellar.org/prd/core-testnet/core_testnet_001`, `http://history.stellar.org/prd/core-testnet/core_testnet_002`, `http://history.stellar.org/prd/core-testnet/core_testnet_003` ([more info](https://github.com/stellar/stellar-core/blob/master/docs/stellar-core_testnet.cfg)) | `http://history.stellar.org/dev/core-futurenet/core_futurenet_001/`, `http://history.stellar.org/dev/core-futurenet/core_futurenet_002/`, `http://history.stellar.org/dev/core-futurenet/core_futurenet_003/` |
-
-\*Values as of July 2026. These limits are set by validator vote and can change over time — check the current values on Stellar Lab's [Network Limits](https://lab.stellar.org/network-limits) page, or see [Resource Limits & Fees](./resource-limits-fees.mdx) for other ways to query them live. The precise smart contract capacity per ledger can also vary based on [resource limits](../learn/fundamentals/fees-resource-limits-metering.mdx#resource-limitations). See [Fees and Metering](../learn/fundamentals/fees-resource-limits-metering.mdx) for detailed smart contract network settings.
-
-## Friendbot
-
-Friendbot is a bot that funds accounts and contracts with fake XLM on Testnet or Futurenet. You can request XLM from Friendbot using the [Stellar Lab](../tools/lab/account.mdx#fund-account) or with various SDKs.
-
-**Key details:**
-
-- Requests are rate limited, so use wisely
-- Provides 10,000 fake XLM when funding a new account
-- Can fund both account addresses (G...) and contract addresses (C...)
-- For multiple accounts: fund your first account with Friendbot, then use that account to fund subsequent accounts using the Create Account operation
-
-## Getting Started
-
-**For Production:** Use Mainnet with real XLM and production-ready infrastructure.
-
-**For Testing:** Use Testnet for stable development and testing that mirrors production behavior.
-
-**For Experimental Features:** Use Futurenet to test the latest features before they're released.
-
-## Testnet and Futurenet data reset
-
-Testnet and Futurenet are reset periodically to the genesis ledger to declutter the network, remove spam, reduce the time needed to catch up on the latest ledger, and help maintain the system. Resets clear all ledger entries (accounts, trustlines, offers, smart contract data, etc.), transactions, and historical data from Stellar Core, Horizon, and the Stellar RPC- which is why developers should not rely on the persistence of accounts or the state of any balances when using Testnet or Futurenet.
-
-Futurenet resets are on a less regular cadence than Testnet resets and don't have a set schedule.
-
-Testnet resets typically happen 2-4 times per year at 17:00 UTC and are announced at least two weeks in advance on the [Stellar Dashboard](https://dashboard.stellar.org) and through several developer community channels.
-
-Here are the scheduled 2026 dates:
-
-- December 16, 2026
-
-If you run a Testnet or Futurenet Horizon instance, you need to re-join and re-sync to the network after a reset. Check out how to do that here: [Testnet Reset](https://github.com/stellar/packages/blob/master/docs/testnet-reset.md).
-
-Check out [this How-To Guide](../build/guides/basics/automate-reset-data.mdx) on automating Testnet and Futurenet reset data.
-
-## Test data automation
-
-It is recommended that you have testing infrastructure that can repopulate the Testnet and Futurenet with useful data after a reset. This will make testing more reliable and will help you scale your testing infrastructure to a private network if you choose to do so. For example, you may want to:
-
-- Generate issuers of assets for testing the development of a wallet;
-- Generate orders on the order book (both current and historical) for testing the development of a trading client;
-- Recreate liquidity pools;
-- Redeploy smart contracts.
-
-If you maintain an application, you should think about creating a data set that is representative enough to test your primary use cases, and allow for robust testing even when Testnet or Futurenet are not available.
-
-A script can automate this entire process by creating an account with Friendbot and submitting a set of transactions that are predefined as a part of your testing infrastructure.
-
-## Network passphrases
-
-Stellar’s Mainnet, Testnet, and Futurenet each have their own unique passphrase. These are used when validating signatures on a given transaction. If you sign a transaction for one network but submit it to another, it won’t be considered valid. By convention, the format of a passphrase is ‘`[Network Name] ; [Month of Creation] [Year of Creation]`’.
-
-The passphrases for the Stellar Mainnet, Testnet, and Futurenet are:
-
-- Mainnet: '`Public Global Stellar Network ; September 2015`'
-- Testnet: '`Test SDF Network ; September 2015`'
-- Futurenet: '`Test SDF Future Network ; October 2022`'
-
-Passphrases serve two main purposes: (1) used as the seed for the root account (master network key) at genesis and (2) used to build hashes of transactions, which are ultimately what is signed by each signer’s secret key in a transaction envelope; this allows you to verify that a transaction was intended for a specific network by its signers.
-
-Many SDKs have the passphrases hardcoded for Stellar's networks. If you’re running a private network, you’ll have to manually pass in a passphrase to be used whenever transaction hashes are generated. All of Stellar’s official SDKs allow you to use a network with a custom passphrase.
-
-## Network IDs
-
-Each Stellar network also has a network ID, which is the SHA-256 hash of the network passphrase. The network ID is used in transaction signing and contract address generation and ensures that hashes and IDs generated are different on each network.
-
-The IDs for the Stellar Mainnet, Testnet, and Futurenet are:
-
-| Network | Network ID |
-| --- | --- |
-| Mainnet | `7ac33997544e3175d266bd022439b22cdb16508c01163f26e5cb2a3e1045a979` |
-| Testnet | `cee0302d59844d32bdca915c8203dd44b33fbb7edc19051ea37abedf28ecd472` |
-| Futurenet | `a3a1c6a78286713e29be0e9785670fa838d13917cd8eaeb4a3579ff1debc7fd5` |
-
-## What Testnet and Futurenet should and should not be used for
-
-### Testnet and Futurenet are good for
-
-- Creating test accounts (with funding from Friendbot);
-- Developing applications and contracts and exploring tutorials on Stellar without the potential to lose any assets;
-- Testing existing applications against new releases or release candidates of Stellar Core, Horizon, and the Stellar RPC;
-- Performing data analysis on a smaller, non-trivial data set compared to the Mainnet.
-
-### Testnet and Futurenet are bad for
-
-- Load and stress testing;
-- High availability test infrastructure- SDF does not guarantee Testnet availability;
-- Long-term storage of data on the network since the network resets periodically;
-- A testing infrastructure that requires more control over the test environment, such as:
-  - The ability to control the data reset frequency;
-  - The need to secure private or sensitive data (before launching on the Mainnet). You can always run your own test network for use cases that don’t work well with SDF’s Testnet.
-
-## Moving your project from Testnet or Futurenet to production
-
-Mainnet, Testnet, and Futurenet each have their own unique passphrase, which is used to validate signatures on a given transaction.
-
-See above sections for the network passphrase for each network.
-
-For applications that don’t rely on the state of the network (such as specific accounts needing to exist), you move to production by changing the network passphrase and ensuring your Horizon instance is connected to Mainnet.
-
-If you’ve been running a Stellar Core or Horizon instance against the Testnet and want to switch to production, changing the passphrase will require both respective databases to be completely reinitialized. If you run your own RPC on Testnet or Futurenet, you may want to use an RPC service when you move to Mainnet. Check out the RPC service providers [here](../data/apis/rpc/providers.mdx).
diff --git a/docs/networks/audits/README.mdx b/docs/networks/audits/README.mdx
deleted file mode 100644
index e7ed05a27..000000000
--- a/docs/networks/audits/README.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-sidebar_position: 40
-title: Audits
-description: Third-party security audits of Stellar network software, by product and version.
----
-
-# Audits
-
-Security audits of Stellar network software, organized by product. Each product page lists the audited versions and links to the published audit reports.
-
-Audits are performed by third-party firms and cover a specific version of the software. A version that isn't listed here hasn't been audited, or its report hasn't been published.
-
-For the latest compatible versions for each network, see [Software Versions](../software-versions.mdx).
diff --git a/docs/networks/audits/index.mdx b/docs/networks/audits/index.mdx
new file mode 100644
index 000000000..6eeb33995
--- /dev/null
+++ b/docs/networks/audits/index.mdx
@@ -0,0 +1,10 @@
+---
+title: Audits
+description: Third-party security audits of Stellar network software, by product and version.
+---
+
+Security audits of Stellar network software, organized by product. Each product page lists the audited versions and links to the published audit reports.
+
+Audits are performed by third-party firms and cover a specific version of the software. A version that isn't listed here hasn't been audited, or its report hasn't been published.
+
+For the latest compatible versions for each network, see [Software Versions](/docs/networks/software-versions).
diff --git a/docs/networks/audits/soroban-poseidon.mdx b/docs/networks/audits/soroban-poseidon.mdx
index ec0a9bae2..1246483cc 100644
--- a/docs/networks/audits/soroban-poseidon.mdx
+++ b/docs/networks/audits/soroban-poseidon.mdx
@@ -1,13 +1,10 @@
 ---
-sidebar_position: 40
 title: Soroban Poseidon SDK
 description: Security audits of Soroban Poseidon SDK.
 ---
 
-# Soroban Poseidon SDK
-
 Audits of [soroban-poseidon](https://github.com/stellar/rs-soroban-poseidon), the Rust library for the Poseidon and Poseidon2 hash functions.
 
 | Version | Auditor | Audit |
 | --- | --- | --- |
-| `v25.0.0` | Halborn | [Report](/assets/audits/2027-03-07%20-%20Halborn%20-%20soroban-poseidon%20v25.0.0.pdf) |
+| `v25.0.0` | Halborn | [Report](/assets/audits/2027-03-07-halborn-soroban-poseidon-v25.0.0.pdf) |
diff --git a/docs/networks/audits/soroban-sdk.mdx b/docs/networks/audits/soroban-sdk.mdx
index 848f92587..78264af4d 100644
--- a/docs/networks/audits/soroban-sdk.mdx
+++ b/docs/networks/audits/soroban-sdk.mdx
@@ -1,11 +1,8 @@
 ---
-sidebar_position: 30
 title: Soroban Rust SDK
 description: Security audits of Soroban Rust SDK.
 ---
 
-# Soroban Rust SDK
-
 Audits of [soroban-sdk](https://github.com/stellar/rs-soroban-sdk), the Rust SDK for building smart contracts.
 
 <table className="audits-table">
@@ -23,7 +20,7 @@ Audits of [soroban-sdk](https://github.com/stellar/rs-soroban-sdk), the Rust SDK
       </td>
       <td>Halborn</td>
       <td>
-        <a href="/assets/audits/2027-03-07%20-%20Halborn%20-%20soroban-sdk%20v25.1.0.pdf">
+        <a href="/assets/audits/2027-03-07-halborn-soroban-sdk-v25.1.0.pdf">
           Report
         </a>
       </td>
@@ -34,7 +31,7 @@ Audits of [soroban-sdk](https://github.com/stellar/rs-soroban-sdk), the Rust SDK
       </td>
       <td></td>
       <td>
-        <a href="/assets/audits/2027-03-07%20-%20Halborn%20-%20bytes-lit%20v0.0.5.pdf">
+        <a href="/assets/audits/2027-03-07-halborn-bytes-lit-v0.0.5.pdf">
           Report
         </a>
       </td>
@@ -45,7 +42,7 @@ Audits of [soroban-sdk](https://github.com/stellar/rs-soroban-sdk), the Rust SDK
       </td>
       <td></td>
       <td>
-        <a href="/assets/audits/2027-03-07%20-%20Halborn%20-%20crates-git-revision%20v0.0.6.pdf">
+        <a href="/assets/audits/2027-03-07-halborn-crates-git-revision-v0.0.6.pdf">
           Report
         </a>
       </td>
@@ -56,7 +53,7 @@ Audits of [soroban-sdk](https://github.com/stellar/rs-soroban-sdk), the Rust SDK
       </td>
       <td></td>
       <td>
-        <a href="/assets/audits/2027-03-07%20-%20Halborn%20-%20stellar-strkey%20v0.0.13%20v0.0.16.pdf">
+        <a href="/assets/audits/2027-03-07-halborn-stellar-strkey-v0.0.13-v0.0.16.pdf">
           Report
         </a>
       </td>
@@ -67,7 +64,7 @@ Audits of [soroban-sdk](https://github.com/stellar/rs-soroban-sdk), the Rust SDK
       </td>
       <td></td>
       <td>
-        <a href="/assets/audits/2027-03-07%20-%20Halborn%20-%20stellar-strkey%20v0.0.13%20v0.0.16.pdf">
+        <a href="/assets/audits/2027-03-07-halborn-stellar-strkey-v0.0.13-v0.0.16.pdf">
           Report
         </a>
       </td>
diff --git a/docs/networks/audits/stellar-core.mdx b/docs/networks/audits/stellar-core.mdx
index b50d9ac87..a0e0d22d5 100644
--- a/docs/networks/audits/stellar-core.mdx
+++ b/docs/networks/audits/stellar-core.mdx
@@ -1,16 +1,14 @@
 ---
-sidebar_position: 10
-title: Stellar Core
+title: Stellar Core and Soroban Host Environment
+sidebarTitle: Stellar Core
 description: Security audits of Stellar Core.
 ---
 
-# Stellar Core and Soroban Host Environment
-
 Audits of [stellar-core](https://github.com/stellar/stellar-core), the reference implementation of the Stellar protocol, and [rs-soroban-env](https://github.com/stellar/rs-soroban-env), the smart contract host environment.
 
 | Version | Auditor | Audit |
 | --- | --- | --- |
-| `v25.0.0` | Runtime Verification | [Stellar Core & Soroban Environment Audit](/assets/audits/2026-02-06%20-%20Runtime%20Verification%20-%20stellar-core%20v25.0.0%20-%20soroban%20environment.pdf) |
-| `v24.0.0` | Oak Security | [Stellar Core Protocol 24 Changes](/assets/audits/2025-11-13%20-%20Oak%20-%20stellar-core%20v24.0.0%20-%20protocol%2024%20changes.pdf) |
-| `v23.0.0` | Oak Security | [Stellar Core Protocol 23 Changes](/assets/audits/2025-10-17%20-%20Oak%20-%20stellar-core%20v23.0.0%20-%20protocol%2023%20changes.pdf) |
-| `v20.0.0` | Veridise | [Stellar Soroban Core](/assets/audits/2024-01-03%20-%20Veridise%20-%20stellar-core%20v20.0.0%20-%20soroban.pdf) |
+| `v25.0.0` | Runtime Verification | [Stellar Core & Soroban Environment Audit](/assets/audits/2026-02-06-runtime-verification-stellar-core-v25.0.0-soroban-environment.pdf) |
+| `v24.0.0` | Oak Security | [Stellar Core Protocol 24 Changes](/assets/audits/2025-11-13-oak-stellar-core-v24.0.0-protocol-24-changes.pdf) |
+| `v23.0.0` | Oak Security | [Stellar Core Protocol 23 Changes](/assets/audits/2025-10-17-oak-stellar-core-v23.0.0-protocol-23-changes.pdf) |
+| `v20.0.0` | Veridise | [Stellar Soroban Core](/assets/audits/2024-01-03-veridise-stellar-core-v20.0.0-soroban.pdf) |
diff --git a/docs/networks/audits/stellar-rpc.mdx b/docs/networks/audits/stellar-rpc.mdx
index a87802515..d9610a48b 100644
--- a/docs/networks/audits/stellar-rpc.mdx
+++ b/docs/networks/audits/stellar-rpc.mdx
@@ -1,5 +1,4 @@
 ---
-sidebar_position: 20
 title: Stellar RPC
 description: Security audits of Stellar RPC.
 ---
@@ -8,4 +7,4 @@ Audits of [stellar-rpc](https://github.com/stellar/stellar-rpc), the RPC server
 
 | Version | Auditor | Audit |
 | --- | --- | --- |
-| `v22.1.0` | OtterSec | [Soroban RPC Security Assessment](/assets/audits/2024-12-20%20-%20OtterSec%20-%20stellar-rpc%20commit%20a60044e.pdf) |
+| `v22.1.0` | OtterSec | [Soroban RPC Security Assessment](/assets/audits/2024-12-20-ottersec-stellar-rpc-commit-a60044e.pdf) |
diff --git a/docs/networks/index.mdx b/docs/networks/index.mdx
new file mode 100644
index 000000000..e91ae5921
--- /dev/null
+++ b/docs/networks/index.mdx
@@ -0,0 +1,135 @@
+---
+title: Networks
+sidebarTitle: Networks Overview
+"og:title": "Explore Mainnet, Testnet & Futurenet: Roles, Use Cases & Connectivity"
+description: "Explore the different networks, including Mainnet, Testnet, and Futurenet. Learn their roles, use cases, and how to connect for development and testing."
+---
+
+Stellar has three networks: the public network (Mainnet, also called Pubnet or the Public Network), the test network (Testnet), and a dev network (Futurenet).
+
+- **Mainnet** is the main network used by applications in production. It connects to real financial rails and requires XLM to cover minimum balances, transaction fees, and rent.
+- **Testnet** is a smaller, free-to-use network maintained by SDF that functions like Mainnet but doesn't connect to real money. It resets on a regular cadence, making it the best place for developers to test applications in a stable environment that mirrors Mainnet functionality.
+- **Futurenet** is a dev network for testing bleeding-edge features. It resets whenever necessary, so it's less predictable than Testnet, but it's where new features are introduced before stable releases.
+
+## Network Comparison
+
+| Feature | Mainnet | Testnet | Futurenet |
+| --- | --- | --- | --- |
+| **Purpose** | Production network | Stable testing environment | Bleeding-edge feature testing |
+| **Network Passphrase** | `Public Global Stellar Network ; September 2015` | `Test SDF Network ; September 2015` | `Test SDF Future Network ; October 2022` |
+| **Network ID** | <code style={{overflowWrap:'anywhere'}}>7ac33997544e3175d266bd022439b22cdb16508c01163f26e5cb2a3e1045a979</code> | <code style={{overflowWrap:'anywhere'}}>cee0302d59844d32bdca915c8203dd44b33fbb7edc19051ea37abedf28ecd472</code> | <code style={{overflowWrap:'anywhere'}}>a3a1c6a78286713e29be0e9785670fa838d13917cd8eaeb4a3579ff1debc7fd5</code> |
+| **Validator Nodes** | Run by the public | SDF runs three core validator nodes | SDF runs core validator nodes |
+| **Validator** | `core-live-a.stellar.org` `core-live-b.stellar.org` `core-live-c.stellar.org` | `core-live-testnet.stellar.org` | `core-live-futurenet.stellar.org` |
+| **Funding** | Real XLM required from another account | Free via Friendbot | Free via Friendbot |
+| **Horizon API** | [Multiple providers available](/docs/data/apis/horizon/providers) | https://horizon-testnet.stellar.org | https://horizon-futurenet.stellar.org |
+| **Stellar RPC** | [Third-party providers only](/docs/data/apis/rpc/providers) | `https://soroban-testnet.stellar.org` | `https://rpc-futurenet.stellar.org` |
+| **Operations per Ledger** | 1,000\* | 200\* | 1,000\* |
+| **Smart Contract Transactions per Ledger** | Max 2,000\* | Max 2,000\* | Max 2,000\* |
+| **Network Resets** | Never | Regular cadence | As needed (unpredictable) |
+| **Friendbot Available** | No | Yes (10,000 XLM) | Yes (10,000 XLM) |
+| **Friendbot API** | N/A | `https://friendbot.stellar.org` | `https://friendbot-futurenet.stellar.org` |
+| **History Archive** | `http://history.stellar.org/prd/core-live/core_live_001/`, `http://history.stellar.org/prd/core-live/core_live_002/`, `http://history.stellar.org/prd/core-live/core_live_003/` | `http://history.stellar.org/prd/core-testnet/core_testnet_001`, `http://history.stellar.org/prd/core-testnet/core_testnet_002`, `http://history.stellar.org/prd/core-testnet/core_testnet_003` ([more info](https://github.com/stellar/stellar-core/blob/master/docs/stellar-core_testnet.cfg)) | `http://history.stellar.org/dev/core-futurenet/core_futurenet_001/`, `http://history.stellar.org/dev/core-futurenet/core_futurenet_002/`, `http://history.stellar.org/dev/core-futurenet/core_futurenet_003/` |
+
+\*Values as of July 2026. These limits are set by validator vote and can change over time — check the current values on Stellar Lab's [Network Limits](https://lab.stellar.org/network-limits) page, or see [Resource Limits & Fees](/docs/networks/resource-limits-fees) for other ways to query them live. The precise smart contract capacity per ledger can also vary based on [resource limits](/docs/learn/fundamentals/fees-resource-limits-metering#resource-limitations). See [Fees and Metering](/docs/learn/fundamentals/fees-resource-limits-metering) for detailed smart contract network settings.
+
+## Friendbot
+
+Friendbot is a bot that funds accounts and contracts with fake XLM on Testnet or Futurenet. You can request XLM from Friendbot using the [Stellar Lab](/docs/tools/lab/account#fund-account) or with various SDKs.
+
+**Key details:**
+
+- Requests are rate limited, so use wisely
+- Provides 10,000 fake XLM when funding a new account
+- Can fund both account addresses (G...) and contract addresses (C...)
+- For multiple accounts: fund your first account with Friendbot, then use that account to fund subsequent accounts using the Create Account operation
+
+## Getting Started
+
+**For Production:** Use Mainnet with real XLM and production-ready infrastructure.
+
+**For Testing:** Use Testnet for stable development and testing that mirrors production behavior.
+
+**For Experimental Features:** Use Futurenet to test the latest features before they're released.
+
+## Testnet and Futurenet data reset
+
+Testnet and Futurenet are reset periodically to the genesis ledger to declutter the network, remove spam, reduce the time needed to catch up on the latest ledger, and help maintain the system. Resets clear all ledger entries (accounts, trustlines, offers, smart contract data, etc.), transactions, and historical data from Stellar Core, Horizon, and the Stellar RPC- which is why developers should not rely on the persistence of accounts or the state of any balances when using Testnet or Futurenet.
+
+Futurenet resets are on a less regular cadence than Testnet resets and don't have a set schedule.
+
+Testnet resets typically happen 2-4 times per year at 17:00 UTC and are announced at least two weeks in advance on the [Stellar Dashboard](https://dashboard.stellar.org) and through several developer community channels.
+
+Here are the scheduled 2026 dates:
+
+- December 16, 2026
+
+If you run a Testnet or Futurenet Horizon instance, you need to re-join and re-sync to the network after a reset. Check out how to do that here: [Testnet Reset](https://github.com/stellar/packages/blob/master/docs/testnet-reset.md).
+
+Check out [this How-To Guide](/docs/build/guides/basics/automate-reset-data) on automating Testnet and Futurenet reset data.
+
+## Test data automation
+
+It is recommended that you have testing infrastructure that can repopulate the Testnet and Futurenet with useful data after a reset. This will make testing more reliable and will help you scale your testing infrastructure to a private network if you choose to do so. For example, you may want to:
+
+- Generate issuers of assets for testing the development of a wallet;
+- Generate orders on the order book (both current and historical) for testing the development of a trading client;
+- Recreate liquidity pools;
+- Redeploy smart contracts.
+
+If you maintain an application, you should think about creating a data set that is representative enough to test your primary use cases, and allow for robust testing even when Testnet or Futurenet are not available.
+
+A script can automate this entire process by creating an account with Friendbot and submitting a set of transactions that are predefined as a part of your testing infrastructure.
+
+## Network passphrases
+
+Stellar’s Mainnet, Testnet, and Futurenet each have their own unique passphrase. These are used when validating signatures on a given transaction. If you sign a transaction for one network but submit it to another, it won’t be considered valid. By convention, the format of a passphrase is ‘`[Network Name] ; [Month of Creation] [Year of Creation]`’.
+
+The passphrases for the Stellar Mainnet, Testnet, and Futurenet are:
+
+- Mainnet: '`Public Global Stellar Network ; September 2015`'
+- Testnet: '`Test SDF Network ; September 2015`'
+- Futurenet: '`Test SDF Future Network ; October 2022`'
+
+Passphrases serve two main purposes: (1) used as the seed for the root account (master network key) at genesis and (2) used to build hashes of transactions, which are ultimately what is signed by each signer’s secret key in a transaction envelope; this allows you to verify that a transaction was intended for a specific network by its signers.
+
+Many SDKs have the passphrases hardcoded for Stellar's networks. If you’re running a private network, you’ll have to manually pass in a passphrase to be used whenever transaction hashes are generated. All of Stellar’s official SDKs allow you to use a network with a custom passphrase.
+
+## Network IDs
+
+Each Stellar network also has a network ID, which is the SHA-256 hash of the network passphrase. The network ID is used in transaction signing and contract address generation and ensures that hashes and IDs generated are different on each network.
+
+The IDs for the Stellar Mainnet, Testnet, and Futurenet are:
+
+| Network | Network ID |
+| --- | --- |
+| Mainnet | `7ac33997544e3175d266bd022439b22cdb16508c01163f26e5cb2a3e1045a979` |
+| Testnet | `cee0302d59844d32bdca915c8203dd44b33fbb7edc19051ea37abedf28ecd472` |
+| Futurenet | `a3a1c6a78286713e29be0e9785670fa838d13917cd8eaeb4a3579ff1debc7fd5` |
+
+## What Testnet and Futurenet should and should not be used for
+
+### Testnet and Futurenet are good for
+
+- Creating test accounts (with funding from Friendbot);
+- Developing applications and contracts and exploring tutorials on Stellar without the potential to lose any assets;
+- Testing existing applications against new releases or release candidates of Stellar Core, Horizon, and the Stellar RPC;
+- Performing data analysis on a smaller, non-trivial data set compared to the Mainnet.
+
+### Testnet and Futurenet are bad for
+
+- Load and stress testing;
+- High availability test infrastructure- SDF does not guarantee Testnet availability;
+- Long-term storage of data on the network since the network resets periodically;
+- A testing infrastructure that requires more control over the test environment, such as:
+  - The ability to control the data reset frequency;
+  - The need to secure private or sensitive data (before launching on the Mainnet). You can always run your own test network for use cases that don’t work well with SDF’s Testnet.
+
+## Moving your project from Testnet or Futurenet to production
+
+Mainnet, Testnet, and Futurenet each have their own unique passphrase, which is used to validate signatures on a given transaction.
+
+See above sections for the network passphrase for each network.
+
+For applications that don’t rely on the state of the network (such as specific accounts needing to exist), you move to production by changing the network passphrase and ensuring your Horizon instance is connected to Mainnet.
+
+If you’ve been running a Stellar Core or Horizon instance against the Testnet and want to switch to production, changing the passphrase will require both respective databases to be completely reinitialized. If you run your own RPC on Testnet or Futurenet, you may want to use an RPC service when you move to Mainnet. Check out the RPC service providers [here](/docs/data/apis/rpc/providers).
diff --git a/docs/networks/resource-limits-fees.mdx b/docs/networks/resource-limits-fees.mdx
index 01906df44..16f63f200 100644
--- a/docs/networks/resource-limits-fees.mdx
+++ b/docs/networks/resource-limits-fees.mdx
@@ -1,6 +1,6 @@
 ---
-sidebar_position: 30
 title: Resource Limits & Fees
+description: "Where to find the current resource limits and fees"
 ---
 
 ## Where to find the current resource limits and fees
diff --git a/docs/networks/software-versions.mdx b/docs/networks/software-versions.mdx
index bafe460be..21ffbe3b9 100644
--- a/docs/networks/software-versions.mdx
+++ b/docs/networks/software-versions.mdx
@@ -1,16 +1,15 @@
 ---
-sidebar_position: 20
 title: Software Versions
 description: Soroban software releases and changelogs.
 ---
 
-:::caution
+<Warning>
 
 Release candidates are software releases that are also released to the [Testnet] test network. Software releases may occur between Testnet releases. If you're interacting with Testnet, the recommended software versions to use in development are provided below. Releases to Testnet may include network resets and network passphrase changes.
 
-:::
+</Warning>
 
-[testnet]: ./README.mdx
+[testnet]: /docs/networks
 
 ## Protocol 29 (Mainnet, October 1, 2026)
 
@@ -601,7 +600,7 @@ Key protocol-related changes:
 
 ### Release notes
 
-#### Core
+#### Core {#core-1}
 
 New features in Protocol 21:
 
@@ -610,20 +609,20 @@ New features in Protocol 21:
 - Use refined cost model for VM instantiation in order to reduce the VM instantiation metered costs: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0054.md
 - Intra-transaction VM module caching for the further Soroban cost reduction: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0055.md, https://github.com/stellar/stellar-protocol/blob/master/core/cap-0056.md
 
-#### Soroban Rust SDK
+#### Soroban Rust SDK {#soroban-rust-sdk-1}
 
 Key protocol-related changes:
 
 - Support for secp256r1 signature verification
 - Support for extending TTL of contract instance and code separate from each other
 
-#### Stellar CLI (Previously Soroban CLI)
+#### Stellar CLI (Previously Soroban CLI) {#stellar-cli-previously-soroban-cli-1}
 
-:::note
+<Note>
 
 Soroban CLI has been renamed to Stellar CLI.
 
-:::
+</Note>
 
 - Add stellar-cli crate alongside soroban-cli
 - Rename to stellar-cli
@@ -831,7 +830,7 @@ This is the first version of the Soroban SDK that supports protocol 21. It is ma
 | Testnet Network Passphrase | `Test SDF Network ; September 2015` |
 | Mainnet Network Passphrase | `Public Global Stellar Network ; September 2015` |
 
-### Changelog
+### Changelog {#changelog-1}
 
 #### Soroban RPC
 
@@ -943,7 +942,7 @@ Mainnet activated Protocol 20 on February 20, 2024 at 1700 UTC and ran the Phase
 - Update extend_ttl docs
 - Bug 1076 conversion error flattening
 
-#### Soroban RPC
+#### Soroban RPC {#soroban-rpc-1}
 
 - Migrate Soroban Tools to Soroban RPC
 - Use soroban-tools Crates
@@ -959,7 +958,7 @@ Mainnet activated Protocol 20 on February 20, 2024 at 1700 UTC and ran the Phase
 - Add diagnostic events to sendTransaction response
 - Remove panics from internal codebase
 
-#### Soroban CLI
+#### Soroban CLI {#soroban-cli-1}
 
 - feat: soroban init command
 - Bump dependencies for pubnet release
@@ -973,7 +972,7 @@ Mainnet activated Protocol 20 on February 20, 2024 at 1700 UTC and ran the Phase
 - Update typescript bindings for latest versions
 - Warn about RC versions only when using pubnet
 
-## Stable v20.1.0 (January 11, 2024)
+## Stable v20.1.0 (January 11, 2024) {#stable-v2010-january-11-2024}
 
 ### Software
 
@@ -1008,7 +1007,7 @@ Mainnet activated Protocol 20 on February 20, 2024 at 1700 UTC and ran the Phase
 - Export functions for creating Timepoint/Duration
 - Allow `&Env` in contract fns
 
-## Stable v20.0.0 (December 18, 2023)
+## Stable v20.0.0 (December 18, 2023) {#stable-v2000-december-18-2023}
 
 ### Software
 
@@ -1037,11 +1036,11 @@ Mainnet activated Protocol 20 on February 20, 2024 at 1700 UTC and ran the Phase
 
 ### Changelog
 
-#### XDR
+#### XDR {#xdr-1}
 
 - Update the docs for extendTTL/restore ops to match the threshold change
 
-#### Soroban Environment
+#### Soroban Environment {#soroban-environment-1}
 
 - Make RecordedAuthPayload consistently return None for invoker.
 - Expiration-related fixes
@@ -1433,7 +1432,7 @@ Mainnet activated Protocol 20 on February 20, 2024 at 1700 UTC and ran the Phase
 - Fix various typescript bindings
 - Make output consistent for all ways to get version
 
-## Preview 11 (September 11, 2023): Testnet and Futurenet Edition
+## Preview 11 (September 11, 2023): Testnet and Futurenet Edition {#preview-11-september-11-2023-testnet-and-futurenet-edition}
 
 ### Software
 
@@ -1460,11 +1459,11 @@ Mainnet activated Protocol 20 on February 20, 2024 at 1700 UTC and ran the Phase
 | Futurenet Network Passphrase | `Test SDF Future Network ; October 2022` |
 | Testnet Network Passphrase | `Test SDF Network ; September 2015` |
 
-:::note
+<Note>
 
 The Soroban RPC version for Preview 11 is presently in Stellar's unstable and testing apt repositories. Additionally, its Docker image release can be accessed at [docker.io/stellar/soroban-rpc:20.0.0-rc3-39](https://hub.docker.com/layers/stellar/soroban-rpc/20.0.0-rc3-39/images/sha256-227170869bca74998e1b6cc1e07deb3aca8d03e36154b3da700d6669e19d485b?context=explore).
 
-:::
+</Note>
 
 ### Changelog
 
@@ -1980,9 +1979,9 @@ See https://github.com/stellar/soroban-tools/releases v0.7.0 for more details.
 | Laboratory | `v2.7.0` |
 | Futurenet Network Passphrase | `Test SDF Future Network ; October 2022` |
 
-### Breaking changes note
+### Breaking changes note {#breaking-changes-note-1}
 
-This release comes with a revamp of authorization approach that is breaking for most of the contracts that did any sort of auth logic or used tokens. [example](../build/smart-contracts/example-contracts/auth.mdx) and [authorization overview](../learn/fundamentals/contract-development/authorization.mdx) for more details.
+This release comes with a revamp of authorization approach that is breaking for most of the contracts that did any sort of auth logic or used tokens. [example](../build/smart-contracts/example-contracts/auth) and [authorization overview](../learn/fundamentals/contract-development/authorization) for more details.
 
 ### Changelog
 
diff --git a/docs/platforms/README.mdx b/docs/platforms/README.mdx
deleted file mode 100644
index a63c59859..000000000
--- a/docs/platforms/README.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
-# SDF Platforms
-
-SDF has open-sourced some "platforms" that make it easier to accomplish certain things on the network.
-
-## Anchor Platform
-
-The Anchor Platform is a set of tools and APIs that enable developers and businesses to build their own on and off-ramp services for the Stellar network. It provides a standardized interface, including the implementation of several Stellar Ecosystem Proposals (SEPs), to make it easy for businesses to integrate with Stellar-based wallets and exchanges.
-
-[Learn more about the Anchor Platform API here!](./anchor-platform/README.mdx)
-
-## Stellar Disbursement Platform
-
-The Stellar Disbursement Platform (SDP) enables organizations to disburse bulk payments to recipients using Stellar.
-
-[Learn more about the Stellar Disbursement Platform API here!](./stellar-disbursement-platform/README.mdx)
diff --git a/docs/platforms/anchor-platform/README.mdx b/docs/platforms/anchor-platform/README.mdx
deleted file mode 100644
index 8f1171b2c..000000000
--- a/docs/platforms/anchor-platform/README.mdx
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: "The Anchor Platform: Build and Manage On/Off-Ramps on the Stellar Network"
-sidebar_position: 10
-sidebar_label: Product Overview
-description: "Learn how the Anchor Platform (AP) simplifies the process of building and managing a Stellar on and off-ramp. Learn about integrating with the AP or get API information."
-pagination_next: platforms/anchor-platform/admin-guide/README
----
-
-# Anchor Platform
-
-The Anchor Platform provides a set of tools and APIs for building on and off-ramp services on the Stellar network. With standardized interfaces and full implementations of key [Stellar Ecosystem Proposals](../../learn/glossary.mdx#seps) (SEPs), it simplifies integration with Stellar-based wallets and exchanges, enabling you to focus on your core business logic rather than protocol implementation details.
-
-## Supported SEPs
-
-The Anchor Platform implements the following Stellar Ecosystem Proposals:
-
-- **[SEP-1](sep-guide/sep1/README.mdx)** — Stellar.toml file serving for service discovery
-- **[SEP-6](sep-guide/sep6/README.mdx)** — Deposit and withdrawal operations
-- **[SEP-10](sep-guide/sep10/README.mdx)** — Web authentication using challenge/response transactions
-- **SEP-12** — Customer KYC/AML data management
-- **[SEP-24](sep-guide/sep24/README.mdx)** — Interactive deposit and withdrawal flows
-- **[SEP-31](sep-guide/sep31/integration.mdx)** — Cross-border payment processing (receive only)
-- **SEP-38** — Price quotes and exchange rate services
-- **[SEP-45](sep-guide/sep45/README.mdx)** — Web authentication using challenge/responses for contract accounts
-
-## Key Features
-
-- **Complete SEP implementations** — Full support for deposit, withdrawal, and payment processing workflows
-- **Authentication & authorization** — SEP-10 and SEP-45 support for both traditional and smart contract accounts
-- **Customer management** — SEP-12 integration for KYC/AML compliance and customer data handling
-- **Transaction processing** — Comprehensive transaction lifecycle management with status tracking and webhook callbacks
-- **Quote & exchange services** — SEP-38 integration for price discovery and exchange rate calculations
-- **Multi-asset support** — Flexible configuration for multiple assets with various deposit and withdrawal methods
-- **Smart contract support** — Native support for Stellar contract accounts (C-accounts) via SEP-45
-
-## Documentation Links
-
-- **[Architecture](./admin-guide/architecture.mdx)** — System architecture and component overview
-- **[Getting Started](./admin-guide/getting-started.mdx)** — Initial setup and deployment instructions
-- **[Event Handling](./admin-guide/events/README.mdx)** — Event delivery, webhooks, and integration patterns
-- **[SEP Guides](./sep-guide/README.mdx)** — Implementation guides for Stellar Ecosystem Proposals
-- **[API Reference](./api-reference/README.mdx)** — Complete API documentation and reference
-
-## Additional Resources
-
-The documentation for the Anchor Platform is a work in progress. Developers are welcome to dive into the code and existing documentation on the [GitHub repository](https://github.com/stellar/anchor-platform).
diff --git a/docs/platforms/anchor-platform/admin-guide/README.mdx b/docs/platforms/anchor-platform/admin-guide/README.mdx
deleted file mode 100644
index d955ccbfc..000000000
--- a/docs/platforms/anchor-platform/admin-guide/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Admin Guide
-sidebar_position: 10
----
-
-import DocCardList from "@theme/DocCardList";
-
-All you need to know about setting up, running, and using the Anchor Platform.
-
-<DocCardList />
diff --git a/docs/platforms/anchor-platform/admin-guide/_category_.json b/docs/platforms/anchor-platform/admin-guide/_category_.json
deleted file mode 100644
index 1ea3c9990..000000000
--- a/docs/platforms/anchor-platform/admin-guide/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
-  "collapsed": false
-}
-
diff --git a/docs/platforms/anchor-platform/admin-guide/architecture.mdx b/docs/platforms/anchor-platform/admin-guide/architecture.mdx
index 47f604d64..700d1b726 100644
--- a/docs/platforms/anchor-platform/admin-guide/architecture.mdx
+++ b/docs/platforms/anchor-platform/admin-guide/architecture.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Architecture"
-sidebar_position: 20
+description: "Before starting with the Anchor Platform, let's get familiar with the architecture."
 ---
 
 ## Architecture
@@ -25,11 +25,11 @@ The client is an application, such as a wallet or remittance sender, that acts o
 
 The SEP server is a client-facing server and therefore needs to be accessible from an external network. The SEP server processes user requests and manages the state of transactions they initiate. When the SEP server needs to provide information it doesn't have to the client, such as the exchange rate for an asset pair or the KYC status of a customer, it makes synchronous [callback][callback-api] requests to the business server and returns the information in a SEP-compliant format.
 
-:::note
+<Note>
 
 The SEP server will never store any sensitive information, such as KYC (PII), in the database.
 
-:::
+</Note>
 
 #### Business Server
 
@@ -66,6 +66,6 @@ The Payment Observer monitors the Stellar blockchain using Stellar RPC or Horizo
 If you already have a solution for monitor payments to your Stellar accounts, such as an integration with your exchange, Horizon, or RPC, then this component is not required, although your business server will need to notify the Anchor Platform when a payment associated with an Anchor Platform transaction was made to your one of your Stellar accounts via the [Platform API][platform-api].
 
 [seps]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/README.md
-[platform-api]: ../api-reference/platform/transactions/README.mdx
-[callback-api]: ../api-reference/callbacks/README.mdx
-[events]: ./events/README.mdx
+[platform-api]: /docs/platforms/anchor-platform/api-reference/platform/transactions
+[callback-api]: /docs/platforms/anchor-platform/api-reference/callbacks
+[events]: /docs/platforms/anchor-platform/admin-guide/events
diff --git a/docs/platforms/anchor-platform/admin-guide/assets-and-client-wallets.mdx b/docs/platforms/anchor-platform/admin-guide/assets-and-client-wallets.mdx
index a7b263fa2..f3f6f21a6 100644
--- a/docs/platforms/anchor-platform/admin-guide/assets-and-client-wallets.mdx
+++ b/docs/platforms/anchor-platform/admin-guide/assets-and-client-wallets.mdx
@@ -1,10 +1,8 @@
 ---
 title: "Assets and Wallet Clients"
-sidebar_position: 40
+description: "This guide covers how to configure assets and wallet clients in the Anchor Platform."
 ---
 
-# Assets and Wallet Clients
-
 This guide covers how to configure assets and wallet clients in the Anchor Platform.
 
 ## Assets Configuration
@@ -90,7 +88,7 @@ items:
     ...
 ```
 
-### Field Explanations
+### Field Explanations {#field-explanations-1}
 
 **Custodial Client Configuration:**
 
diff --git a/docs/platforms/anchor-platform/admin-guide/component/rpc/request.mdx b/docs/platforms/anchor-platform/admin-guide/component/rpc/request.mdx
deleted file mode 100644
index 9157143af..000000000
--- a/docs/platforms/anchor-platform/admin-guide/component/rpc/request.mdx
+++ /dev/null
@@ -1,29 +0,0 @@
-The Request object must contain the following attributes:
-
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- jsonrpc
-  - string
-  - A String specifying the version of the JSON-RPC protocol. MUST be exactly "2.0"
-- method
-  - string
-  - A String containing the name of the method to be invoked. List of available methods you can see in [JSON-RPC Methods][json-rpc-methods]
-- params
-  - object
-  - A Structured value that holds the parameter values, corresponding to method call, to be used during the invocation of the method
-- id
-  - string
-  - An identifier established by the client. The Server will reply with the same value in the Response object
-
-</AttributeTable>
-
-:::tip
-
-It's possible to provide multiple updates in a single JSON-RPC request (by placing multiple JSON-RPC request objects). When an update is done in this way, all updates will be done sequentially.
-
-Most importantly, each JSON-RPC request is not atomic. If one update fails, all previous updates WILL be applied and all subsequent updates WILL be processed and applied as well.
-
-:::
diff --git a/docs/platforms/anchor-platform/admin-guide/component/rpc/response.mdx b/docs/platforms/anchor-platform/admin-guide/component/rpc/response.mdx
deleted file mode 100644
index 02d808103..000000000
--- a/docs/platforms/anchor-platform/admin-guide/component/rpc/response.mdx
+++ /dev/null
@@ -1,33 +0,0 @@
-The Response is expressed as a single JSON Object, with the following attributes:
-
-<AttributeTable>
-
-- ATTRIBUTE
-  - DATA TYPE
-  - DESCRIPTION
-- jsonrpc
-  - string
-  - A String specifying the version of the JSON-RPC protocol. It's set to "2.0"
-- result
-  - object
-  - A Structured value that holds the updated transaction details
-- id
-  - string
-  - An identifier sent by the client
-- error
-  - object
-  - A Structured value that holds the error details
-    - id
-      - string
-      - Unique id of the transaction for which an error occurred
-    - code
-      - number
-      - A number that indicates the error type that occurred. Please see a list of [error codes](#error-codes) below
-    - message
-      - string
-      - A String providing a short description of the error
-    - data
-      - string
-      - A primitive or structured value that contains additional information about the error
-
-</AttributeTable>
diff --git a/docs/platforms/anchor-platform/admin-guide/events/README.mdx b/docs/platforms/anchor-platform/admin-guide/events/README.mdx
deleted file mode 100644
index fe2e9c169..000000000
--- a/docs/platforms/anchor-platform/admin-guide/events/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Event Handling
-sidebar_position: 120
----
-
-import DocCardList from "@theme/DocCardList";
-
-Receive transaction updates through HTTP webhook events.
-
-<DocCardList />
diff --git a/docs/platforms/anchor-platform/admin-guide/events/delivery.mdx b/docs/platforms/anchor-platform/admin-guide/events/delivery.mdx
index cd6d3148e..6c7134783 100644
--- a/docs/platforms/anchor-platform/admin-guide/events/delivery.mdx
+++ b/docs/platforms/anchor-platform/admin-guide/events/delivery.mdx
@@ -1,17 +1,17 @@
 ---
 title: "Delivery Guarantees"
-sidebar_position: 30
+description: "Depending on the messaging system you use, there will be different delivery guarantees."
 ---
 
 ## Delivery Guarantees
 
 Depending on the messaging system you use, there will be different delivery guarantees. the event service uses Kafka as the messaging system, so the delivery guarantees will depend on the producer configuration and the broker configuration that you use. Depending on the number of partitions configured for the `TRANSACTION` topic, the events may be delivered out of order.
 
-:::caution
+<Warning>
 
 Any transaction logic that depends on the order should use the transaction `status` and the `updated_at` fields to determine the order of the events.
 
-:::
+</Warning>
 
 Next subsections will describe the delivery guarantees from the client and the business server perspective.
 
@@ -23,8 +23,8 @@ For each client, the event service will attempt to deliver each event up to thre
 
 The event service will attempt to deliver each event to the businesss server up to three times with an exponential backoff. If the event is not delivered after three attempts due to HTTP 4xx or 5xx errors, the event will be skipped. If the business server is not reachable after three attempts, the event service will no longer attempt to deliver any events to the business server.
 
-:::note
+<Note>
 
 The business server delivery guarantees are the same as the client delivery guarantees. In the future, the event service will skip the events that are not delivered to clients that are not reachable.
 
-:::
+</Note>
diff --git a/docs/platforms/anchor-platform/admin-guide/events/getting-started.mdx b/docs/platforms/anchor-platform/admin-guide/events/getting-started.mdx
index 7547bbf70..748a58d7c 100644
--- a/docs/platforms/anchor-platform/admin-guide/events/getting-started.mdx
+++ b/docs/platforms/anchor-platform/admin-guide/events/getting-started.mdx
@@ -1,6 +1,6 @@
 ---
 title: Getting Started
-sidebar_position: 10
+description: "Anchor Platform provides an event service that sends HTTP webhook notifications to."
 ---
 
 Anchor Platform provides an event service that sends HTTP webhook notifications to:
@@ -11,7 +11,7 @@ Anchor Platform provides an event service that sends HTTP webhook notifications
 - Quote updates
 - Customer KYC status changes
 
-Event schemas for business servers are defined in the [API reference](../../api-reference/callbacks/post-event.api.mdx).
+Event schemas for business servers are defined in the [API reference](/docs/platforms/anchor-platform/api-reference/callbacks/post-event).
 
 **Client Applications**
 
diff --git a/docs/platforms/anchor-platform/admin-guide/events/index.mdx b/docs/platforms/anchor-platform/admin-guide/events/index.mdx
new file mode 100644
index 000000000..e8505fa76
--- /dev/null
+++ b/docs/platforms/anchor-platform/admin-guide/events/index.mdx
@@ -0,0 +1,22 @@
+---
+title: Event Handling
+description: "Receive transaction updates through HTTP webhook events."
+---
+
+<CardGroup cols={2}>
+  <Card title="Getting Started" icon="file-lines" href="/docs/platforms/anchor-platform/admin-guide/events/getting-started">
+
+    Anchor Platform provides an event service that sends HTTP webhook notifications to.
+
+  </Card>
+  <Card title="Integration" icon="file-lines" href="/docs/platforms/anchor-platform/admin-guide/events/integration">
+
+    This guide will walk you through integrating with the event service to start receiving events.
+
+  </Card>
+  <Card title="Delivery Guarantees" icon="file-lines" href="/docs/platforms/anchor-platform/admin-guide/events/delivery">
+
+    Depending on the messaging system you use, there will be different delivery guarantees.
+
+  </Card>
+</CardGroup>
diff --git a/docs/platforms/anchor-platform/admin-guide/events/integration.mdx b/docs/platforms/anchor-platform/admin-guide/events/integration.mdx
index 6819473c6..a3e4bb991 100644
--- a/docs/platforms/anchor-platform/admin-guide/events/integration.mdx
+++ b/docs/platforms/anchor-platform/admin-guide/events/integration.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Integration"
-sidebar_position: 20
+description: "This guide will walk you through integrating with the event service to start receiving events."
 ---
 
 This guide will walk you through integrating with the event service to start receiving events. The event service currently only supports Apache Kafka as the backend message broker.
@@ -15,16 +15,16 @@ Anchor Platform will send events to the `TRANSACTION` Kafka topic. The event ser
 
 First, the event service's Kafka producer need to be configured using the `event.queue` section of the configuration file or setting the environment variables. The following is the set of required environment variables needed to configure the event service's Kafka producer:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 # dev.env
 EVENTS_ENABLED=true
 EVENTS_QUEUE_TYPE=kafka
 EVENTS_QUEUE_KAFKA_BOOTSTRAP_SERVER=localhost:9092
 ```
 
-```yaml
+```yaml YAML
 # dev.services.yaml
 events:
   enabled: true
@@ -34,21 +34,21 @@ events:
       bootstrap_server: localhost:9092
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Anchor Platform allows a subset of the Kafka producer's client configuration to be set. See the [default values file][default-values-file] for more information what is available. For more information on the Kafka producer's client configuration, see the [Kafka documentation](https://kafka.apache.org/documentation/#producerconfigs).
 
 Next, the event processor needs to be configured in the `event_processor` section of the Anchor Platform Configuration file or setting the environment variables.
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 # dev.env
 EVENT_PROCESSOR_CLIENT_STATUS_CALLBACK_ENABLED=true
 EVENT_PROCESSOR_CALLBACK_API_REQUEST_ENABLED=true
 ```
 
-```yaml
+```yaml YAML
 # dev.services.yaml
 event_processor:
   client_status_callback:
@@ -57,7 +57,7 @@ event_processor:
     enabled: true
 ```
 
-</CodeExample>
+</CodeGroup>
 
 This will enable the event processor to start processing events from `TRANSACTION` topic. In this example, the event processor will send events to client and business server callback endpoints.
 
@@ -84,19 +84,19 @@ Anchor Platform signs the callback requests it sends to client applications. The
 
 ### As a Business Server
 
-In addition to SEP transaction status updates, business servers can receive events about SEP-31 quote creation or SEP-12 customer information updates. The schema of the event data will depend on the type of event being sent. Visit the [Event API documentation](../../api-reference/callbacks/post-event.api.mdx) for more information about the schema of the event data.
+In addition to SEP transaction status updates, business servers can receive events about SEP-31 quote creation or SEP-12 customer information updates. The schema of the event data will depend on the type of event being sent. Visit the [Event API documentation](/docs/platforms/anchor-platform/api-reference/callbacks/post-event) for more information about the schema of the event data.
 
 To receive events as a business server, you will need to expose a callback URL that the event service can send events to. The event service will send a POST request to this endpoint with the event data in the request body.
 
-#### Configuration
+#### Configuration {#configuration-1}
 
 The event service's callback API can be configured using the `callback_api` section of the Anchor Platform configuration file or setting the environment variables.
 
 The following is an example of how to configure the event service's callback API with JWT authentication:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 # dev.env
 
 # note `/callback` will not be used for event callbacks
@@ -109,7 +109,7 @@ CALLBACK_API_AUTH_JWT_HTTP_HEADER=Authorization
 SECRET_CALLBACK_API_AUTH_SECRET="a secret for signing jwts"
 ```
 
-```yaml
+```yaml YAML
 # dev.services.yaml
 callback_api:
   base_url: http://localhost:8081/callback
@@ -120,13 +120,13 @@ callback_api:
       http_header: Authorization
 ```
 
-</CodeExample>
+</CodeGroup>
 
 The following is an example of how to configure the event service's callback API with API key authentication:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 # dev.env
 CALLBACK_API_BASE_URL=http://localhost:8081/callback
 CALLBACK_API_AUTH_TYPE=api_key
@@ -134,7 +134,7 @@ CALLBACK_API_AUTH_API_KEY_HTTP_HEADER=X-Api-Key
 SECRET_CALLBACK_API_AUTH_SECRET="your API key"
 ```
 
-```yaml
+```yaml YAML
 # dev.services.yaml
 callback_api:
   base_url: http://localhost:8081/callback
@@ -144,7 +144,7 @@ callback_api:
       http_header: X-Api-Key
 ```
 
-</CodeExample>
+</CodeGroup>
 
 This configures the event service's callback API that will be used to send events to client and business server callback endpoints. The following are the supported configuration options:
 
@@ -158,4 +158,4 @@ This configures the event service's callback API that will be used to send event
     - `http_header`: The header in which the API key will be sent.
 
 [default-values-file]: https://github.com/stellar/anchor-platform/blob/develop/platform/src/main/resources/config/anchor-config-default-values.yaml
-[clients-config]: ../../sep-guide/sep10/README.mdx#client-configuration
+[clients-config]: /docs/platforms/anchor-platform/sep-guide/sep10#client-configuration
diff --git a/docs/platforms/anchor-platform/admin-guide/getting-started.mdx b/docs/platforms/anchor-platform/admin-guide/getting-started.mdx
index b2f310c35..6b42dc716 100644
--- a/docs/platforms/anchor-platform/admin-guide/getting-started.mdx
+++ b/docs/platforms/anchor-platform/admin-guide/getting-started.mdx
@@ -1,10 +1,8 @@
 ---
 title: "Getting Started"
-sidebar_position: 30
+description: "This guide will help you quickly get the Anchor Platform (TESTNET only) with a business reference running locally using Docker Compose."
 ---
 
-# Getting Started
-
 This guide will help you quickly get the Anchor Platform (TESTNET only) with a business reference running locally using Docker Compose.
 
 Please note that this is not meant to be run in production.
@@ -52,7 +50,7 @@ docker-compose ps
 
 All services should show as "Up" in the status column.
 
-## What's Included
+## What's Included {#whats-included}
 
 The `quick-run` setup includes:
 
@@ -64,11 +62,11 @@ The `quick-run` setup includes:
   - `reference-config.yaml` - Reference server settings
   - `stellar.localhost.toml` - SEP-1 TOML file
 
-:::tip
+<Tip>
 
-For more information about configuring assets and client wallets, see the [Assets and Client Wallets](./assets-and-client-wallets.mdx) guide.
+For more information about configuring assets and client wallets, see the [Assets and Client Wallets](./assets-and-client-wallets) guide.
 
-:::
+</Tip>
 
 ## Testing with Stellar Demo Wallet
 
diff --git a/docs/platforms/anchor-platform/admin-guide/index.mdx b/docs/platforms/anchor-platform/admin-guide/index.mdx
new file mode 100644
index 000000000..153e079ac
--- /dev/null
+++ b/docs/platforms/anchor-platform/admin-guide/index.mdx
@@ -0,0 +1,27 @@
+---
+title: Admin Guide
+description: "All you need to know about setting up, running, and using the Anchor Platform."
+---
+
+<CardGroup cols={2}>
+  <Card title="Architecture" icon="file-lines" href="/docs/platforms/anchor-platform/admin-guide/architecture">
+
+    Before starting with the Anchor Platform, let's get familiar with the architecture.
+
+  </Card>
+  <Card title="Getting Started" icon="file-lines" href="/docs/platforms/anchor-platform/admin-guide/getting-started">
+
+    This guide will help you quickly get the Anchor Platform (TESTNET only) with a business reference running locally using Docker Compose.
+
+  </Card>
+  <Card title="Assets and Wallet Clients" icon="file-lines" href="/docs/platforms/anchor-platform/admin-guide/assets-and-client-wallets">
+
+    This guide covers how to configure assets and wallet clients in the Anchor Platform.
+
+  </Card>
+  <Card title="Event Handling" icon="box-archive" href="/docs/platforms/anchor-platform/admin-guide/events">
+
+    3 items
+
+  </Card>
+</CardGroup>
diff --git a/docs/platforms/anchor-platform/api-reference/README.mdx b/docs/platforms/anchor-platform/api-reference/README.mdx
deleted file mode 100644
index 1a9f52ea6..000000000
--- a/docs/platforms/anchor-platform/api-reference/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: API Reference
-sidebar_position: 20
----
-
-import DocCardList from "@theme/DocCardList";
-
-View all Anchor Platform API information.
-
-<DocCardList />
diff --git a/docs/platforms/anchor-platform/api-reference/_category_.json b/docs/platforms/anchor-platform/api-reference/_category_.json
deleted file mode 100644
index 0d4475828..000000000
--- a/docs/platforms/anchor-platform/api-reference/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": false
-}
diff --git a/docs/platforms/anchor-platform/api-reference/callbacks/README.mdx b/docs/platforms/anchor-platform/api-reference/callbacks/README.mdx
deleted file mode 100644
index f723800f7..000000000
--- a/docs/platforms/anchor-platform/api-reference/callbacks/README.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: Callbacks Server
-sidebar_position: 20
----
-
-The Anchor Platform provides several callback functionalities for your business server.
-
-<EndpointsTable title="Callbacks">
-
-|        |                                         |
-| ------ | --------------------------------------- |
-| GET    | [/customer](./get-customer.api.mdx)     |
-| PUT    | [/customer](./put-customer.api.mdx)     |
-| DELETE | [/customer/:id](./del-customer.api.mdx) |
-| POST   | [/event](./post-event.api.mdx)          |
-| GET    | [/rate](./get-rates.api.mdx)            |
-
-</EndpointsTable>
diff --git a/docs/platforms/anchor-platform/api-reference/callbacks/del-customer.ParamsDetails.json b/docs/platforms/anchor-platform/api-reference/callbacks/del-customer.ParamsDetails.json
deleted file mode 100644
index bfe41a5bb..000000000
--- a/docs/platforms/anchor-platform/api-reference/callbacks/del-customer.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"in":"path","name":"id","schema":{"type":"string"},"required":true}]}
\ No newline at end of file
diff --git a/docs/platforms/anchor-platform/api-reference/callbacks/del-customer.RequestSchema.json b/docs/platforms/anchor-platform/api-reference/callbacks/del-customer.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/anchor-platform/api-reference/callbacks/del-customer.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/anchor-platform/api-reference/callbacks/del-customer.StatusCodes.json b/docs/platforms/anchor-platform/api-reference/callbacks/del-customer.StatusCodes.json
deleted file mode 100644
index 828722b0c..000000000
--- a/docs/platforms/anchor-platform/api-reference/callbacks/del-customer.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"204":{"description":"Success."},"404":{"description":"Customer not found.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/anchor-platform/api-reference/callbacks/del-customer.api.mdx b/docs/platforms/anchor-platform/api-reference/callbacks/del-customer.api.mdx
deleted file mode 100644
index 2f52b57d6..000000000
--- a/docs/platforms/anchor-platform/api-reference/callbacks/del-customer.api.mdx
+++ /dev/null
@@ -1,78 +0,0 @@
----
-id: del-customer
-title: "Delete Customer Data"
-description: "The request for this endpoint is identical to the"
-sidebar_label: "Delete Customer Data"
-hide_title: true
-hide_table_of_contents: true
-api: eJztVE1v2zAM/SsCd9gGOHaa7eRb0eZQYBiKpTslASZLTKxNllSRXhsY/u+DHLtptmy/YL7Ypvgh8j2+DljuCco13LTEvsFIsM3geUYYBvNqeT+7WkA2fHy4SocaSUUT2HgHJTzUKCI+tkgsdj4Krg0JdDp441gYEkajY6OkFewF17hx62+3y0/Lh6Uo1Fj02/ZdzRyoLIq94bqtcuWbghitlXF6z0L07JW3RWV9VTSSGGOBytOBGJuCMMzm86tF3ug3U+KZRouM7zduuqPGnXGohXHi2Fu+cRt3O7il64kp9C0JLVkKH8Vji+354XiWGh4qGO/yjYMMfMAo0++dhhI02mmukEGQUTbIacblugOTxhck15CBkw1CCUZDBqRqbCSUHfAhJCtxNG4PfQapCRNRQ8mxxX6bLBS8I6Tkv5h/TK9zgFatUkiUp/iPlxymGwrnE4St0zlkoLxjdJzcZQjWqKGr4julmO7PS/rqOypOXcY0AzbHK2GMPl7sxegL5rMe12P0NgM2bJPfcjD06ckAnxkdGe+O8/yBBygn6mbwU9oWL1I4za1Brv0IETIO6HANJbxwsuiM7hMcGH9OkLXRQgkTVZW0tpLqR161ZBwSzY6+OT7LJliUTtU+JipDKmnczqeWU7bj5D/k83wOlzZqdXCqjt75lsTNWIbE9f2doIDK7EY4xo1DsTquiLgeSop7K3nnYyNC9AmWgeP/znvcC5p2mUQjNYrqMKR/yfdUG4vCDIsdok/EMm4v5EkCom+EFMoadCxeMScXD2n3jzN5m+qMxB1lgfBUWu52qPi88u/+l0oMGzhR5dTeakAFMrBGoSNMIIwLdx2kqlEsBhhO6JZF8fT0lMvhNPdxX4yhVHy6u1l+Xi1ni3ye19zYgbPBEzfSvUo8CsrLbt1Klr8j3Z2W7L+MnsvoKAuMz1wEK41LijHg042LugZ1UtbS6KQStSdOJ11XScKv0fZ9Mj+2GA9QrrdJFKKRVeLHugNtKH1rKHfSEv4DnXdfRlF6L/52udEo3eGkPQDZqEpGQ7/tM6hRaoyv5OpaKQz8KuQPsT1TqyPi0Pe/AB/asHM=
-sidebar_class_name: "delete api-method"
-info_path: docs/platforms/anchor-platform/api-reference/callbacks/callbacks-server
-custom_edit_url: null
-hide_send_button: true
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={'SEP-12,SEP-31'} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Delete Customer Data"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"delete"}
-  path={"/customer/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The request for this endpoint is identical to the
-[`DELETE /customer`](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#customer-delete)
-request defined in SEP-12.
-
-Delete the customer's data or queue the customers data for deletion.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./del-customer.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./del-customer.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./del-customer.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/anchor-platform/api-reference/callbacks/del-customer.mdx b/docs/platforms/anchor-platform/api-reference/callbacks/del-customer.mdx
new file mode 100644
index 000000000..574601999
--- /dev/null
+++ b/docs/platforms/anchor-platform/api-reference/callbacks/del-customer.mdx
@@ -0,0 +1,7 @@
+---
+title: Delete Customer Data
+openapi: "openapi/anchor-platform/bundled-callbacks.yaml DELETE /customer/{id}"
+playground: none
+---
+
+<Badge color="blue">SEP-12</Badge> <Badge color="blue">SEP-31</Badge>
diff --git a/docs/platforms/anchor-platform/api-reference/callbacks/get-customer.ParamsDetails.json b/docs/platforms/anchor-platform/api-reference/callbacks/get-customer.ParamsDetails.json
deleted file mode 100644
index bb37c257d..000000000
--- a/docs/platforms/anchor-platform/api-reference/callbacks/get-customer.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"in":"query","name":"id","description":"The ID of the customer as returned in the response of a previous PUT request.","schema":{"type":"string"}},{"in":"query","name":"account","description":"The Stellar or Muxed Account authenticated with the Platform via SEP-10.","schema":{"type":"string"}},{"in":"query","name":"memo","description":"The memo value identifying a customer with a shared account, where the shared account is `account`.","schema":{"type":"string"}},{"in":"query","name":"memo_type","description":"The type of memo used to identify a customer with a shared account.","schema":{"type":"string","enum":["id","hash","text"]}},{"in":"query","name":"type","description":"The type of action the customer is being KYCd for. See the\n[Type Specification](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#type-specification)\ndocumented in SEP-12.\n","schema":{"type":"string"}},{"in":"query","name":"transaction_id","description":"The transaction id with which the customer's info is associated. When information from the customer depends on the\ntransaction (e.g., more information is required for larger amounts)\n","schema":{"type":"string"}},{"in":"query","name":"lang","description":"Defaults to `en`. Language code specified using ISO 639-1. Human readable descriptions, choices, and\nmessages should be in this language.\n","schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/anchor-platform/api-reference/callbacks/get-customer.RequestSchema.json b/docs/platforms/anchor-platform/api-reference/callbacks/get-customer.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/anchor-platform/api-reference/callbacks/get-customer.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/anchor-platform/api-reference/callbacks/get-customer.StatusCodes.json b/docs/platforms/anchor-platform/api-reference/callbacks/get-customer.StatusCodes.json
deleted file mode 100644
index 05ec4ff97..000000000
--- a/docs/platforms/anchor-platform/api-reference/callbacks/get-customer.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Valid request. Customer either already exists or the customer identified by the parameters is new and must\nprovide the field values described in the response body. Response bodies are identical to the schema defined\nin [SEP-12](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#customer-get).\n","content":{"application/json":{"schema":{"type":"object","required":["status"],"properties":{"id":{"type":"string"},"status":{"type":"string","enum":["ACCEPTED","PROCESSING","NEEDS_INFO","REJECTED"]},"fields":{"type":"object","additionalProperties":{"required":["type","description"],"properties":{"type":{"type":"string","enum":["string","binary","number","date"]},"description":{"type":"string"},"choices":{"type":"array","items":{"type":"string"}},"optional":{"type":"boolean"}}}},"provided_fields":{"type":"object","additionalProperties":{"required":["type","description"],"properties":{"type":{"type":"string","enum":["string","binary","number","date"]},"description":{"type":"string"},"choices":{"type":"array","items":{"type":"string"}},"optional":{"type":"boolean"},"status":{"type":"string","enum":["ACCEPTED","PROCESSING","REJECTED","VERIFICATION_REQUIRED"]},"error":{"type":"string"}}}},"message":{"type":"string"}},"title":"GetCustomerResponse"},"examples":{"SuccessKYC":{"summary":"The case when a customer has been successfully KYC'd and approved","value":{"id":"d1ce2f48-3ff1-495d-9240-7a50d806cfed","status":"ACCEPTED","provided_fields":{"first_name":{"description":"The customer's first name","type":"string","status":"ACCEPTED"},"last_name":{"description":"The customer's last name","type":"string","status":"ACCEPTED"},"email_address":{"description":"The customer's email address","type":"string","status":"ACCEPTED"}}}}}}}},"400":{"description":"Error.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}},"404":{"description":"Not Found.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/anchor-platform/api-reference/callbacks/get-customer.api.mdx b/docs/platforms/anchor-platform/api-reference/callbacks/get-customer.api.mdx
deleted file mode 100644
index 9a68eaef1..000000000
--- a/docs/platforms/anchor-platform/api-reference/callbacks/get-customer.api.mdx
+++ /dev/null
@@ -1,89 +0,0 @@
----
-id: get-customer
-title: "Retrieve Customer's Info"
-description: "The request and response for this endpoint is identical to the"
-sidebar_label: "Retrieve Customer's Info"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWG1z2zYS/is7uA9pZihKdtJco28eRcnp2jo+y+lNx/bYELES0YAAC4CWNR7995sFSImyGbu13ZvLTfzFFAksnt199gV7wwS6zMrSS6PZkJ3kCBZ/r9B54FqARVca7RDmxoLPpQPUojRSe5AOpEDtZcYVeAM+xzN9evlhfAL9rHLeFGgvz7/LvS/dsN9fSJ9XszQzRd95VIrb5n+vtMabzKj+TJlZv+DOo+1jZtzKeSz6DsveYLC3nxbib43g3gL9yzPdCVXgXGoUIDVMx0e9vf30TJ/pkx3wXCmzdJApido78GZIawD2UniPPstJG5hLVMKFR4f2Cm0wjbToSLaxAi0pbnEhCTJw0LiEBiJcSQ68hkCWOfr0X7FMWfmXjQ9Jqcm8rYEw6EAbDzm/QuBbtI0WKGpfI5Tc8gI9WgcOyeM6vK5lJyA9uNxUimzvK6sjBWqr1aYS213RPSkQxxwvtq8aKTOsBaGAZY4atGlj4BYDjjS6aj+FUY7Z56id575yYOZtlXzOPRR8BVxZ5GIVD2jU3JDiDhcgC3KXOfocoykameT5ubEFp3iBJXfAswxLjyIBi79hFp6MBeelUqARhYPCWAz70tve6FwV9rcWxc9VKbgP5tyc3+0BuOWA9EyzhHm+cGx4ykaNIuw8Ydc9h2V4TSx9wxIW2Vo/vNqjRaZEG46bCDZkC/SNCJawrXfY8PSGSUohv1doVyxhmhfIhkwKlnQkmck7clbbtMDd1v23SBMdW1q8kqZyQJFUszBlCXNZjgVnwxvmVyWd6byVesHW66QbE88yU2nfCWwaQ4988HN1jQIO4mLglc9juiM3LKWPSeJIcU8eCeEezDd4FKYCC9MJiD7AFVcV1vl2vpJ60eZ5wMLB5ZzirVYuIf5ajETa+UKZ+7J+vnw01ouwtgswfSCHBeCVQ0Eh1UB/EPd9gBKGuiqIr4FVOXc5URuvPTv/ItgHcfIsBPMOF6WDGZKZf/x1FBJiClPEusad0MZpiZmcExuk0c+dzAlaz7VPeHmmhcmqArW/Vdoe40BvuXZR74svBGhrCcia78tc1qWxMdSLmBDJXtw5k0kKjhT+Tdm7nSnn1hS7FhZYohYOTF022ud9h+kiTbYZsZEiW2WFipTidkGJoyDiuJePs4XigVm7FniHc16pWA0uUV+m8BPXi4ovEDIjEGrfoIDKEU0m04/w5tXb3l4K/6gKroEKDp8p6kY2cl0CWW5khi6hjuVMF+gcX6BrFcCQ+KQDVR/3kIPPE9YkSUff9wcD+rerzS9cSbHJmNAkcEAZClxTHvFaOu+a6rONhRi6pOxsdbsxkC40PdSAFRU1HKU1V1LgthLF3OVqQ8w6kvvMiFUKx62fEmO5v91gQjRE0+KdaanhNEbCX9ppRi9kRnvUnuzLy1LVkdn/zZGRb+46ycyoIWDkoUhaylyxU6HCWloqrV5Gx0nR4d6kWX5PKjwYjcZHJ+N3LGFHxx9H4+l0cviBJexwPH43vZgcvv/IEnY8/ud4RIvO1wmLDUIXUC6EJJ24OtoB11agI5/eUSbK/TLmzYuZ1DwGY1XMQktBXU5AuUPhDsvUodT6xq3lJEt6LDpMtl5TMxPVa32dGaOQa7Ze04KavuLim5E6jfQURm5ImLBfxseT95PRwcnk4+HF8fhfnybHNTnRWmO7cBGyOmF2w/bSK3r1YduiNjmFcOM1L0oVbTGtsgyd+/HXUQjcqijIwLHwZdxhvH60WpWcU0OAGlzcOa+UWlFz8EKE3MdLIg5SKQ3proloJvYy3J+//qH3aj7f671++73ovd1/Pej9nX8/ED8M3mTzsKkxatt2HVScS+v8RSxct5P8yW5ZDkshLE3ueOruceuEKf5HZdPKPyUaCy7VBRfConMPig+roVn9h46o/xL2uqv+jYlT6VMy+G7kfomjSXcWX+9WgLj7fEvYAI81+F/fxX9oPLw3lRZfgw4h1DxqRx1PuBZ+Roqt+rK5CZB7Lp3U1RToc1PfOMNN0+dsyDbzE6JBuB7HIyqr2JA1HUDGlZrx7HM6o+4MnevFtWmdA7jOcmOpQ2B0FLWYpDJJiwZ/lQ7SQff1cKWz3BpN19BRfYyDg6MJ7LTrmxlKc508CEdub4ulNeSWejR1n9zY67imfXNQcIFNJ7aRt8ylQpoHSEeyKUfFW2IzIgsdOK+nHNBiThjInOlokxdu05a5uudyuD2az+eY+d2Tb6/vOiKOIGqqbNWbBq+whCmZIaXp4U3TlR+UPMsR9oMbtt4d9vvL5TLl4Wtq7KJfb3X9nyaj8eF03NtPB2nuCxU4WxrnC65bgo/RW4lXuOmCXziYEAHuFNNNoH2bin6bin6biv5fTkVjkaMJUr9UXIYGN2Sbm7rinLJNxTlPWG6cp3c3NzPu8JNV6zW9jhMFqkNCOrr1Czacc+XwgZzynEPQTlVi5ZWttpQxmoP8OZjPNBK9B+F2IPsEmH/9oPQeDerx7RPgP31s+gC8ZmL7DBi//pHpPbZ6BjN9pbPT+4xye2L8SPP8jw1W79G4ngtv9TynH1bS4Wx4SrOKHLlA27rjHISy19p154a2c7X5MD5h6/V/AIMyEEU=
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/anchor-platform/api-reference/callbacks/callbacks-server
-custom_edit_url: null
-hide_send_button: true
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={'SEP-6,SEP-12,SEP-31'} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Customer's Info"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/customer"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The request and response for this endpoint is identical to the
-[`GET /customer`](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#customer-get)
-request and response defined in SEP-12.
-
-This endpoint allows clients to:
-
-  1. Fetch the fields the server requires in order to register a new customer via a SEP-12
-[`PUT /customer`](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#customer-put) request
-
-If the server does not have a customer registered for the parameters sent in the request, it should return the
-fields required in the response. The same response should be returned when no parameters are sent.
-
-  2. Check the status of a customer that may already be registered
-
-This allows clients to check whether the customers information was accepted, rejected, or still needs more info.
-If the server still needs more info, or the server needs updated information, it should return the fields required.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./get-customer.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-customer.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-customer.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/anchor-platform/api-reference/callbacks/get-customer.mdx b/docs/platforms/anchor-platform/api-reference/callbacks/get-customer.mdx
new file mode 100644
index 000000000..1d8dc3da8
--- /dev/null
+++ b/docs/platforms/anchor-platform/api-reference/callbacks/get-customer.mdx
@@ -0,0 +1,8 @@
+---
+title: "Retrieve Customer's Info"
+openapi: "openapi/anchor-platform/bundled-callbacks.yaml GET /customer"
+playground: none
+---
+
+<Badge color="blue">SEP-6</Badge> <Badge color="blue">SEP-12</Badge>
+<Badge color="blue">SEP-31</Badge>
diff --git a/docs/platforms/anchor-platform/api-reference/callbacks/get-rates.ParamsDetails.json b/docs/platforms/anchor-platform/api-reference/callbacks/get-rates.ParamsDetails.json
deleted file mode 100644
index 500bfc175..000000000
--- a/docs/platforms/anchor-platform/api-reference/callbacks/get-rates.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"in":"query","name":"type","description":"The type of rate requested. If `firm`, the response must include `rate.id` and `rate.expires_at`.","schema":{"type":"string","enum":["indicative","firm"]},"required":true},{"in":"query","name":"client_id","description":"An identifier for the client application making the request. This ID can be used to offer different fees to different clients.\n\nClient IDs will be the Stellar public key the public key used to authenticate via SEP-10. Anchors must ensure\nthat the public key specified in the request matches a public key known to belong to the sending anchor.\n\nThis parameter will only be specified if the client is authenticated via SEP-10. Anchors can define whether or not\nauthentication is required for fetching indicative rates. Firm rates always require authentication.\n","schema":{"type":"string"}},{"in":"query","name":"sell_asset","description":"The asset the client application will send to the anchor in exchange for `buy_asset` in\n[Asset Identification Format](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md#asset-identification-format).\n","schema":{"type":"string"},"required":true},{"in":"query","name":"buy_asset","description":"The asset the that the anchor will send in exchange for `sell_asset` in\n[Asset Identification Format](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md#asset-identification-format).\n","schema":{"type":"string"},"required":true},{"in":"query","name":"sell_amount","description":"The amount of `sell_asset` the client application will send in exchange for `buy_asset`. Will not be used in\nconjunction with `buy_amount`.\n","schema":{"type":"string"}},{"in":"query","name":"buy_amount","description":"The amount of `buy_asset` the anchor will send in exchange for `sell_asset`. Will not be used in conjunction\nwith `sell_amount`.\n","schema":{"type":"string"}},{"in":"query","name":"country_code","description":"The [ISO 3166-1 alpha-2](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2) code of the user's current address.\nAnchors should expect this parameter to be provided if one of the assets of the buy/sell pair is fiat and it\nis available in two or more countries.\n","schema":{"type":"string"}},{"in":"query","name":"expire_after","description":"The client's desired `expires_at` date and time for the quote that can be used if this is a firm quote. This should\nbe a [UTC ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) string. Anchors should return `400 Bad\nRequest` if an expiration date on or after the requested value cannot be provided.\n","schema":{"type":"string"}},{"in":"query","name":"sell_delivery_method","description":"The method the client or user will use to deliver `sell_asset` to the Anchor. This value may affect the\nexpiration and price provided. The values used for this parameter is defined in the application's configuration.\nWill not be used in conjunction with `buy_delivery_method`.\n","schema":{"type":"string"}},{"in":"query","name":"buy_delivery_method","description":"The method the client or user wants used to receive `buy_asset` from the Anchor. This value may affect the\nexpiration and price provided. The values used for this parameter is defined in the application's configuration.\nWill not be used in conjunction with `sell_delivery_method`.\n","schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/anchor-platform/api-reference/callbacks/get-rates.RequestSchema.json b/docs/platforms/anchor-platform/api-reference/callbacks/get-rates.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/anchor-platform/api-reference/callbacks/get-rates.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/anchor-platform/api-reference/callbacks/get-rates.StatusCodes.json b/docs/platforms/anchor-platform/api-reference/callbacks/get-rates.StatusCodes.json
deleted file mode 100644
index 4e0fbc75c..000000000
--- a/docs/platforms/anchor-platform/api-reference/callbacks/get-rates.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success.","content":{"application/json":{"schema":{"type":"object","properties":{"rate":{"type":"object","properties":{"id":{"type":"string","description":"ID of the firm quote. NOT USED when `type=indicative`."},"expires_at":{"type":"string","format":"date-time","description":"Expiration for the quote. NOT USED when `type=indicative`."},"price":{"type":"string","description":"The conversion price offered by the anchor for one unit of `buy_asset` in terms of `sell_asset`, without including fees. In traditional finance, `buy_asset` would be referred to as the base asset and `sell_asset` as the counter asset. The formula `sell_amount - fee = price * buy_amount` must hold true ([ref](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md#price-formulas))."},"sell_amount":{"type":"string","description":"The amount of `sell_asset` the anchor will exchange for `buy_asset`. It could be different from the `sell_amount` provided in the request, depending on how fees are applied by the Anchor."},"buy_amount":{"type":"string","description":"The amount of `buy_asset` the anchor will provide with `sell_asset`. It could be different from the `buy_amount` provided in the request, depending on how fees are applied by the Anchor."},"fee":{"type":"object","description":"An object describing the fees added on top of the rate provided via the `price` attribute.","properties":{"total":{"type":"string","description":"The total fee to be applied."},"asset":{"type":"string","description":"The asset the fee will be charged in. Must be represented in [Asset Identification Format](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md#asset-identification-format)."},"details":{"type":"array","items":{"type":"object","properties":{"name":{"type":"string","description":"The name of the fee, for example `ACH fee`, `Brazilian conciliation fee`, `Service fee`, etc."},"description":{"type":"string","description":"A text describing the fee."},"amount":{"type":"string","description":"The amount of asset applied. If `fee.details` is provided, `sum(fee.details.amount)` should be equals `fee.total`."}},"required":["name","amount"],"title":"RateFeeDetailResponse"}}},"required":["total","asset"],"title":"RateFeeResponse"}},"required":["price","sell_amount","buy_amount"]}},"title":"RateResponse"}}}},"422":{"description":"Unprocessable Entity. This status should be returned when the anchor understood the request but cannot\nreturn a success response.\nIn these cases, the Platform will respond to the client application's request with a `400 Bad Request`\nand include the error message provided by the anchor in the response body.\n","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}},"500":{"description":"Error. The Platform will respond to the client application with the same response code and body.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/anchor-platform/api-reference/callbacks/get-rates.api.mdx b/docs/platforms/anchor-platform/api-reference/callbacks/get-rates.api.mdx
deleted file mode 100644
index 5b939927d..000000000
--- a/docs/platforms/anchor-platform/api-reference/callbacks/get-rates.api.mdx
+++ /dev/null
@@ -1,105 +0,0 @@
----
-id: get-rates
-title: "Retrieve Rates"
-description: "Transactions that involve two non-equivalent on & off-chain assets (such as USDC on Stellar and fiat EUR) must"
-sidebar_label: "Retrieve Rates"
-hide_title: true
-hide_table_of_contents: true
-api: eJztW+tv4zYS/1cGOuA2uZPtbLYtCgP7Id1N2wB37WKToB/iXExLo4iNRGpJyl5fkP7thxlSDz8Sp9m9uz7yyZFEcjjv3wyZ2yhFmxhZOalVNI7OjFBWJPRkweXCgVRzXcwR3EKD0mqAH2o5FwUqB1rBX0Fn2SDJhVQgrEVnYc/WSQ7Cwvnp2zc05tRhUQgDQqWQSeHg+Pz9PpS1dRNVWwT8mORCXSMY4TBQFQYh0WVZK5kIhyk4DS5HSApJlEVVFfRBagUGP9RonVTXPMJ1HAzhpxxVmGOhFDc4UWG4bVZ8VwiXaVNCpg292NhQvDrMokppk9I2lJuVhEpyWkNDhi7JQbrhRE3Ue+YqEQpmCBdSpbzxOV7u5c5VdjwaLRaLoVRztE5XmEoxTHQ5cmhKO5KjbsKHWjscClvtgzYTdZFJUz5qkWxEQ7vpQzjrtkt6gMrouUzpHZy8ZUXhx0oaL2CZEXsTFWTfClAALctCYkaPeEHParNgKm2ia0Ua9Nq1FSYyk8kWTVq/r1bSUiVFnbJFIEz9+CuZTqESRpTo0EyUVxrrQliteB/H0uVoYGqxKK5ESeSnoA1MZ/WyfV7IoiCFBCIpSNXjzHY0bAyz2oHCORqYaZcP4UTxlqwoERZiGU8U9kmmWMg5muVViS7X6ZTlycQ3vpRied8m1snGYKVKEDypiQrskc/1uPOPkpTTuh29Y8FM1HnFDpOgnDf+YtBWWln0Zu512OmAxTQXhUyFQ2/lLEDmqTIyQdDZyjpM6cS/CxPJiDIhi3VX4sX9vAcc/EXnaAvpchDw/dnZO7BOuNpOVKJT3sP0y4ND+Eak8J1wuBDLKW+EDGrFEOIVM4hhykxMY6+kDHHKsadhOSVbyHRR6IUd04IDcocp2zwPxo+SlDVRAIPu/TAogp0rF3MEAZW2ktyY1q79lq28VuQMQrmrFBNZisJOIcVMKm8MLHBaChKtMnlde5ccrpNz2okikMMPtSgacdq6ZErtyBQdaWIYBBBW8i6+vn94/dp7d8/U4hVxwi+vgxX8DTqxwt+BZeO510UKztT4OFKdFcdwL6m9dVr7W4itayrVaEFp51X2GD62LBos6pfX7GSNpoT1UpduyTZKbqxrlZKPoTHaMO/A4W31w9oq05cH/9obbDOL/elERXHkxLWNxhcRJ5XoMo4+DixW/Or0+N3g1cso9n98TR91hd5gTtJoHF2j89PiqItu0fjiNpKU+j/UaJZRHClRYjSO3LLCKF6HB5RglxVbL0m28UxMh3CSwZQSwjReiQdehiHCBX3IJijyE6catFfCTYdRHNkkx1JE41u/hXFknZHqOoojVHVJnHYpMYojIhld3sURbUUaTKMx6eou3s5Wm0Y2eDtSIFNUTmYSTYMGtgGOUtx0wZPZp8QlLaXOkOZr6yGLzjI0kEr6oWUyRAYe3ZsATti03nhaJ29tm56ISBPIq3pWyARucMmve48NOVG7nDggyARzKYBM4eXBEJrU7AOEsrXBiWKgtbZSSM9d9GlCbylckiPlld7oG6UXigjPsNAkkhB00Fu4RxjBa2Qvp3r2tCo4+/VoZn2ZUxbrMZRu5YgE7h0IFjlyFtaG3HyiepMZxvg8QibC2mWQRtvszMljlCF82+AaC6JYiGU7E1bXHLJP3mewd/fZYBdOtzqYD4j3GB9LjgS8hjql6mBrtg4H1ERdHPGqJ8HCw2rfalMK14HIa+nyesbQ0Xqra34HldFOJ7oYzQo9G5XCOjQjTLRdWoflyGI1ODh49fWwTP/CZAdyhdQgY1L7O0T2WDduudshwdbGg5g68W0IrI+n/oAS62W77TLziZBhSU8SO83wAcMbwk80jHJuExNJsIlWP9cqCeu4fAWRPdGluhV2Mdfzi19tF1sZgh4/E+UZ6iPOJ3LEZZNZXhG+3crTxcnpj/Dq5VdfDV6CKKpcDA47s0Q1XMgb6StBba5H9DQ6Of3xys+4CjP2ocHPJIzaonlhIakN5yaRpgYt5aYm2tpc1wUXh5g4X3h1QZ3zQFP5cTDXql06NAfC06xejkhGUAnJGIj7AgQJpJsoCvxzIQsxK5Dz0EJTUC81NwVILBLtE8XqwcaVyByarWL1xv6CYJnlXDHt4RPgMoj26WSJLUjg0trHmj4A4HQmrS/HuFb2NbhHC16WEzWj4uDi/OwNkEK//urg5VpRbzVrUFo9oK8D2sNAqHRAewhRYpi7stgHz32XHYO+DLraKJh+cXBAJdJEvfdZfUpbFKpf7DODWpG8WUZ9EEApmGuXRKjgA422PyUTrlXFW7XiP/WjkTZsrt5zqY1EsMqvtBbBdK+yDbL3bFD1LbLMmzJOVE8MXXnbcsjonSdar96299C5QA/NN9XbSiG7XsXtCCe98LjeOviEOPmJ8hbUS2sQp+8l4EpYzYwuf+8i39rI2SXzS8rFvuqx9P3w4IB+VqV7WicJBdUojhKtHCpHY3p7Hv1saeDtJiE9+xkTSnCVocrOSU+GgOruUTLdVlKt7u3kbROg+9Hqhx/P4Pz0+C0BbAVTWuJ1h5mnQ8IgXYzcRsXHqGgcceiisLVB+rgzhJWo+jjybDe7+eP4rtUcjSVCTf+KSrEUZss+IKBNUPqqldzADWRn1FhdB0sxG4+um3KXiguq+HzH0IhU0j5EAZlUQiUYr6y64FA9o2iboTGhovPdz5mwDarlurkf38IQ32Zt2n3sOST2uhCrnY4BbQke0+6AvQuD2eeGukx3ELZm9/dZf31w+igtPoBW+4jufmR6Qi21IPBefd6ErtXmcYdpVoriGFKsQq2rFeR64Qt8aiCyQ3dWFUIh8dqDqr+W1Qewa9Nw7+PPR7Lat4DPymmGW+PSRtvFfwH/ftb0VjyBlDajqclQtZ1mgijtRqkpwGz4Ri4I54yc1Q6HGyGQu6SPEzoPZU/xqDYwyWz5uvNxumsLUVqqaeokuTDXLOMh/JNcjp2+MmiRT0qkgt9M8UkMh55xj2VhjCBUIR2Wdnfu8eDjMQKjkW0OQozZcfGjKKsCYXr05nvuLMcw/caIf8tCCk7eCf3lc4f/eopmTuHNP6JLAh89crt2cwQOP24zSm8DT3LgEMGDLfmOadeT55ZyY9fUn67Lvc2W/f60QfUz9F1n61fxZwBDwn69lsCFF36748s4ctIVtGVqBn+L+JaXfx+AS3S3Pt97TWP2m/N7M1cn+qQcr3UeeuHvkmb0V+tv4i6Ovjg83MRP56oymhAUV4fHykm3bCoqPhLqicfXPZh66NALmbVK0VinA8Rtmpx04uZrGzon5ppJgPWArX/A5Q8ALRVCduOA+KmnWk11Bk1xNlFcEIfOOS3jjwxKYv66FwJXkUsbuUP/fabTpUeunwlv8i62dqK2Ycx1q/Cze2Z0zC+8xr/chph5wNrZ8OOE7EXbntW2IuGeBwmXZfM7kAwjbIeKYKs/srnBZTRuTn/iiIukradAVJWEQo+PgPj0x+XROBpx4UD+aebNSVBtimgcNfklEUUxE8nNcFZbqdDagR87DBE5NPgTXUZERqpME5sBX0fj6NXwYHiwNSieLlWSG610beFNIGPh6N1Je0NgtRhoDkHWD6gro0kV7dHc/ev6KtF2p/ylSLHxnc6wcklNJxdiMXk+H2W03sq4SWwxNrZQ8lna4IsuXjQ3TSz2Lhi0JXBHeX38NhL+DDCYR8feKWsliqNCJkjxs8250VElkhzhkNXQaTf0lgR/5fZSmGpH/zh5c/zD6fHgcHjAXSW200pbVwrVW/g9UhtujtCcKa5l19alnu8UPd8per5T9Hyn6PlO0fOdouc7Rb/FO0UelVK5O6oKIRUBVoYKtwEqXvge82Uc5do6er69pZbkuSnu7ui1P2UgAJlKLszSaJyJwuIDsGDvfcC++/C/uFa0lUuPosNVp4Cho4gOTx7Px/O9oed7Q0+6N/SARfZvqT3RLNfc609wqegBea7cuPrcAv3D3DF6QID9+1ZPlN9v7pLRTntpWpafh+H/08WjXUr9DEw+30TaEc1Xr3J9gqSfLyc9/XLSAwpauxT2CQp6vqe09c7MrlC7eSXpv6ODP/vdpR3J4CE1XNKDkaSHaHxB/3CRo0jR9E4jjpIEq34u2ThLWTmM+O74LLq7+w+n2PMK
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/anchor-platform/api-reference/callbacks/callbacks-server
-custom_edit_url: null
-hide_send_button: true
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={'SEP-31,SEP-38'} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Rates"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/rate"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Transactions that involve two non-equivalent on & off-chain assets (such as USDC on Stellar and fiat EUR) must
-use exchange rates that are communicated to the client application requesting the transaction. When clients make
-requests to the Platform for these exchange rates, the Platform sends this request to the anchor to fetch it.
-
-Rates can be [indicative](https://www.investopedia.com/terms/i/indicativequote.asp) or
-[firm](https://www.investopedia.com/terms/f/firmquote.asp). The anchor must provide an ID and expiration if the
-client requests a firm rate.
-
-Anchors can provide discounted rates specific client applications. The Platform includes the `client_id` parameter
-for this reason.
-
-Either `sell_amount` or `buy_amount` will be included in requests as parameters, but never both. In the same way,
-either `sell_delivery_method` and `buy_delivery_method` may be included in requests, but never both, since either
-`sell_asset` or `buy_asset` is a Stellar asset.
-
-
-Upon receiving the response, the Anchor Platform will validate the amount and price of the response.
-
-If the validation fails, the Platform will respond to the client application's request with a HTTP status
-code of `502 Bad Gateway`.
-
-The `sell_amount`, `buy_amount`, `price`, and `fee` are validated as follows:
-
-- if `rate.fee` exists,
-  - `rate.fee.asset` must have a positive value of `significant_decimals` defined in the asset configuration.
-  - `rate.fee.total` must equal to the sum of `rate.fee.details.amount`.
-  - if the `rate.fee.asset == rate.sell_asset`, `sell_amount ~= price * buy_amount + fee` must hold true.
-  - if the `rate.fee.asset == rate.buy_asset`,  `sell_amount ~= price * (buy_amount + fee)` must hold true.
-- if `rate.fee` does not exist, `sell_amount ~= price * buy_amount` must hold true.
-
-The `~=` is defined as equality within rounding error.
-    The rounding error is defined as `10^(-significant_decimals)`
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./get-rates.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-rates.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-rates.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/anchor-platform/api-reference/callbacks/get-rates.mdx b/docs/platforms/anchor-platform/api-reference/callbacks/get-rates.mdx
new file mode 100644
index 000000000..0b701586c
--- /dev/null
+++ b/docs/platforms/anchor-platform/api-reference/callbacks/get-rates.mdx
@@ -0,0 +1,7 @@
+---
+title: Retrieve Rates
+openapi: "openapi/anchor-platform/bundled-callbacks.yaml GET /rate"
+playground: none
+---
+
+<Badge color="blue">SEP-31</Badge> <Badge color="blue">SEP-38</Badge>
diff --git a/docs/platforms/anchor-platform/api-reference/callbacks/index.mdx b/docs/platforms/anchor-platform/api-reference/callbacks/index.mdx
new file mode 100644
index 000000000..e26f10745
--- /dev/null
+++ b/docs/platforms/anchor-platform/api-reference/callbacks/index.mdx
@@ -0,0 +1,12 @@
+---
+title: Callbacks Server
+description: "The Anchor Platform provides several callback functionalities for your business server."
+---
+
+| Callbacks |  |
+| --- | --- |
+| GET | [/customer](/docs/platforms/anchor-platform/api-reference/callbacks/get-customer) |
+| PUT | [/customer](/docs/platforms/anchor-platform/api-reference/callbacks/put-customer) |
+| DELETE | [/customer/:id](/docs/platforms/anchor-platform/api-reference/callbacks/del-customer) |
+| POST | [/event](/docs/platforms/anchor-platform/api-reference/callbacks/post-event) |
+| GET | [/rate](/docs/platforms/anchor-platform/api-reference/callbacks/get-rates) |
diff --git a/docs/platforms/anchor-platform/api-reference/callbacks/post-event.RequestSchema.json b/docs/platforms/anchor-platform/api-reference/callbacks/post-event.RequestSchema.json
deleted file mode 100644
index c5e0a749a..000000000
--- a/docs/platforms/anchor-platform/api-reference/callbacks/post-event.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string"},"type":{"type":"string","enum":["transaction_created","transaction_status_changed","quote_created","customer_updated"],"description":"The transaction event type. Can be one of the following:\n- `transaction_created` - a transaction was created through the SEP endpoints. The payload is in the `transaction` field.\n- `transaction_status_changed` - the status of a transaction has changed. The payload is in the `transaction` field.\n- `quote_created` - a quote was created via the SEP38 API. The payload is in the `quote` field.\n"},"timestamp":{"type":"string","format":"date-time"},"payload":{"type":"object","properties":{"transaction":{"oneOf":[{"type":"object","required":["id","sep","kind","status","amount_expected","destination_account","started_at"],"properties":{"id":{"type":"string"},"sep":{"type":"string","enum":["24"]},"kind":{"type":"string","enum":["deposit","withdrawal"]},"status":{"type":"string","description":"Possible status value for SEP-24 transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_user_transfer_start","pending_user_transfer_complete","pending_anchor","pending_trust","pending_user","no_market","too_small","too_large"],"title":"StatusSEP24"},"type":{"type":"string","description":"This field is always empty for SEP-24 transactions."},"amount_expected":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_in":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_out":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee_details":{"type":"object","required":["total","asset"],"properties":{"total":{"type":"string"},"asset":{"type":"string"},"details":{"type":"array","items":{"type":"object","required":["name","amount"],"properties":{"name":{"type":"string"},"amount":{"type":"string"},"description":{"type":"string"}},"title":"FeeDescription"}}},"title":"FeeDetails"},"quote_id":{"type":"string"},"started_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"completed_at":{"type":"string","format":"date-time"},"transfer_received_at":{"type":"string","format":"date-time"},"user_action_required_by":{"type":"string","format":"date-time"},"message":{"type":"string"},"refunds":{"type":"object","properties":{"amount_refunded":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"payments":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string"},"id_type":{"type":"string","enum":["stellar","external"]},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"requested_at":{"type":"string","format":"date-time"},"refunded_at":{"type":"string","format":"date-time"}}}}},"title":"Refunds"},"stellar_transactions":{"type":"array","items":{"type":"object","required":["id","created_at","envelope","payments"],"properties":{"id":{"type":"string","description":"The ID of the transaction in the Stellar network."},"memo":{"type":"string","description":"The memo of the transaction in the Stellar network."},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text","hash","id"]},"created_at":{"type":"string","format":"date-time","description":"The time the transaction was registered in the Stellar network."},"envelope":{"type":"string","description":"The transaction envelope, containing all the transaction information."},"payments":{"type":"array","items":{"type":"object","required":["id","payment_type","source_account","destination_account","amount"],"properties":{"id":{"type":"string","description":"The ID of the payment in the Stellar Network."},"payment_type":{"type":"string","description":"The type of payment in the Stellar Network.","enum":["payment","path_payment"],"default":"payment"},"source_account":{"type":"string","description":"The account being debited in the Stellar Network."},"destination_account":{"type":"string","description":"The account being credited in the Stellar Network."},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"}}}}},"title":"StellarTransaction"}},"source_account":{"type":"string"},"destination_account":{"type":"string"},"external_transaction_id":{"type":"string"},"memo":{"type":"string"},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"refund_memo":{"description":"If provided, this memo should be used for refund transactions.","type":"string"},"refund_memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"client_domain":{"type":"string"},"client_name":{"type":"string"},"customers":{"type":"object","description":"The user that initiated the transaction is both the sender and receiver.\n","properties":{"sender":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"receiver":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}}},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}},"title":"TransactionSEP24"},{"type":"object","required":["id","sep","kind","status","started_at"],"properties":{"id":{"type":"string"},"sep":{"type":"string","enum":["31"]},"kind":{"type":"string","enum":["receive"]},"status":{"type":"string","description":"Possible status value for SEP-31 transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_sender","pending_receiver","pending_transaction_info_update","pending_customer_info_update"],"title":"StatusSEP31"},"type":{"type":"string","description":"This field is always empty for SEP-31 transactions."},"amount_expected":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_in":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_out":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee_details":{"type":"object","required":["total","asset"],"properties":{"total":{"type":"string"},"asset":{"type":"string"},"details":{"type":"array","items":{"type":"object","required":["name","amount"],"properties":{"name":{"type":"string"},"amount":{"type":"string"},"description":{"type":"string"}},"title":"FeeDescription"}}},"title":"FeeDetails"},"quote_id":{"type":"string"},"started_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"completed_at":{"type":"string","format":"date-time"},"transfer_received_at":{"type":"string","format":"date-time"},"user_action_required_by":{"type":"string","format":"date-time"},"message":{"type":"string"},"refunds":{"type":"object","properties":{"amount_refunded":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"payments":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string"},"id_type":{"type":"string","enum":["stellar","external"]},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"requested_at":{"type":"string","format":"date-time"},"refunded_at":{"type":"string","format":"date-time"}}}}},"title":"Refunds"},"stellar_transactions":{"type":"array","items":{"type":"object","required":["id","created_at","envelope","payments"],"properties":{"id":{"type":"string","description":"The ID of the transaction in the Stellar network."},"memo":{"type":"string","description":"The memo of the transaction in the Stellar network."},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text","hash","id"]},"created_at":{"type":"string","format":"date-time","description":"The time the transaction was registered in the Stellar network."},"envelope":{"type":"string","description":"The transaction envelope, containing all the transaction information."},"payments":{"type":"array","items":{"type":"object","required":["id","payment_type","source_account","destination_account","amount"],"properties":{"id":{"type":"string","description":"The ID of the payment in the Stellar Network."},"payment_type":{"type":"string","description":"The type of payment in the Stellar Network.","enum":["payment","path_payment"],"default":"payment"},"source_account":{"type":"string","description":"The account being debited in the Stellar Network."},"destination_account":{"type":"string","description":"The account being credited in the Stellar Network."},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"}}}}},"title":"StellarTransaction"}},"source_account":{"type":"string"},"destination_account":{"type":"string"},"external_transaction_id":{"type":"string"},"memo":{"type":"string"},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"refund_memo":{"description":"if provided, this memo should be used for refund transactions.","type":"string"},"refund_memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"client_domain":{"type":"string"},"client_name":{"type":"string"},"customers":{"type":"object","description":"The Identification info of the sending and receiving customers. If they were created through [SEP-12](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md),\nthis object should contain the SEP-12 customer `id`. Otherwise, the `account` address of the customer.\n","properties":{"sender":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"receiver":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}}},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}},"title":"TransactionSEP31"}]},"quote":{"type":"object","properties":{"id":{"type":"string"},"sell_amount":{"type":"string"},"sell_asset":{"type":"string"},"buy_amount":{"type":"string"},"buy_asset":{"type":"string"},"expires_at":{"type":"string","format":"date-time"},"price":{"type":"string"},"total_price":{"type":"string"},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"transaction_id":{"type":"string"},"created_at":{"type":"string","format":"date-time"}},"title":"Quote"},"customer":{"type":"object","properties":{"id":{"type":"string"}},"title":"Customer"}}}},"required":["id","type","payload","timestamp"],"title":"Event"}}}}}
\ No newline at end of file
diff --git a/docs/platforms/anchor-platform/api-reference/callbacks/post-event.StatusCodes.json b/docs/platforms/anchor-platform/api-reference/callbacks/post-event.StatusCodes.json
deleted file mode 100644
index 0adf7dfc4..000000000
--- a/docs/platforms/anchor-platform/api-reference/callbacks/post-event.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"The event is successfully processed and ready to receive next event. The response body is empty."},"400":{"description":"The event is invalid or rejected. The response body contains the error message."}}}
\ No newline at end of file
diff --git a/docs/platforms/anchor-platform/api-reference/callbacks/post-event.api.mdx b/docs/platforms/anchor-platform/api-reference/callbacks/post-event.api.mdx
deleted file mode 100644
index 346d4eb3f..000000000
--- a/docs/platforms/anchor-platform/api-reference/callbacks/post-event.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: post-event
-title: "Receive an Event"
-description: "Receive a JSON object representing an event."
-sidebar_label: "Receive an Event"
-hide_title: true
-hide_table_of_contents: true
-api: eJztHGtv2zjyrxD80jvAjyTtPs7fut0skMNtm61zXy4JXFoaW2wkUiWpOEbg/34YkpIoWXZso0CzgPIlNh8zw+HMcB40n6lhS00nt/TyEYTR9H5An4Yacts2vbwe/kwH9v/FO//h7TkOkjkoZrgUVzGd0FxqYwHQAY1BR4rn2Ecn9DNEwB+BMPLv6aePRM6/QmSIglyBBmG4WBImCODc0Z2gA6rgWwHa/CbjNZ0800gKg3Anz5Tlecoji3T8VSP0Z6qjBDKGn8w6BzqhDgEd0FwhiYaDxl4eB2O0UVws6WbgG9odAwqiyJABRjGhWYQoZ5ECZiCmg0arNswUehYlTCxt57dCGggGR4U2MgM1K/LYNt23WXSTAAlAOmYQJGlEPjBB5kCkACIXxCRAFjJN5YqL5eRODMmXDgq/kCFhDYgrponvJCZRslgmFtb08pqAiHPJhdEjgoTkbJ1KFhOuCRd2UIjiC1lwSOPRFuomG5ACnOpakfImPQnS44YejbXBX7dU29RY5CNn5QLf/kreX1/tRGPn1gisUPAMtGFZ3iUZC6kyZuiE4mYOcShO8YBflsNgVfhVCvi0oJPb7WmoBlxBjFLIUY405HRAH7iwXyxj6YCyTBbCzOAph8jJWwzacGG1ZMaiCLvdBGUgnjGD8neQbiDCPapx8Y7ebzxBe4bFkEvNkYQVN0ms2IqldqJfQsfUpnZcS635PK2E6ZGlBWqBIs4qhYKlA8RcRDLLUzCASug/xpazi0LE9iM85ZbHAwpKSYW7BSLmYjnTBtKUhS3wZEAJlgZNhQY1s+gXoGaWxTt7A2LKAUxESQOpUYVuQ6ADKuQsY+oBsMtIOdMZS1P/OWVqCbilhpsUuTi1XJpeXl+822fg2haIa6cCqBosXbG1JpDlZr2L0SME3ha+DukPxdgNR6HVGjrk0Pd3yaKbsd2zqRf+3s2uyeLilREkC/NaKFoAzGIwjKf6JZKMNFbod1Dkuo8hCIWvjZkpxdZ0QLmB7EWKBMugMn3bFNnuToJ2M6+hDvtY+AfA78HYzVafW9mm9AN22dbaHB98xnj/4ag5ld07alZltJRz3o6kE+2edwvKbZvN14cDyEBrtuzeQ2e8O0WkS1NmlbF/JYrnyVoAvBaKcrbOrOd/hDYe5D/wePaSe12fstXpet+lqD/aVr4WUnxsdKRCljpwxKRNw7B99kpnDZfdsVnD6TrRjlu31nvsSBvKxSOkMrdOUimWB7mrXSHV1e9lyBSGHt7vn7p1EAFmJdXDyNmdTB4GGkeeAHynPuzAgMOOQEOmiSzSGONFH10TvnCQuCZCGiKKNB2F4S08IdsTphPctNhqX7Ajh0lLZzzLM9iiGyM0BUuuDSiI93GrEoSDmNUInv3MAcHMAePCZhjStIOJbilcitGpdnBLmj0Qt9EDqmWhIgjCsO7gbJcnc7yke/xt1n4MWNsg8TD2ejF8CXgtV36kZYhJZuVXm/lYsCJF+SkbN1tsOogoP5jMATc4hjk32yIVrruL9SdgihTEL6F6TedX05J7am+CLMTmgA04lH2b+iAPT4hdXnC3wX3NxpLwmFhrGUTcf0Imb5DG6qidlQtrknq1ILmSjzyGeEAMhtwWna4IKTTENuB2YFoB92CbTwG6vyW7opSjKYplxnhX4FWN2BnTldnVTvO8vXSMTYhJGBoxbrhPiLY4oMlcGpcg1SBiUISJmPhYSLksdVNV3bCXSfBcvYrfaMIU+Gy49hTFmA9frDEjO0RCtcXrUu5k6nJC5L1NGukBmRfG8t33uzx7MGJ0J+7EH1IRZoecX5CSVwOX+eSxT3sGEqiLxYJH3OafJVkUabqu6cJZJYxSTuaF5gK0fkN+Y9EDiLiFdotyj9ybkC92iV9QjjwxuqUPLXg/kzofdTLAgyKYLvGxPPNKU3Ei8GjK3LpjuDsLDj1qLrlJrHDWyleePFKRP4sniKsGFscKtC5JkWIYJYyj82O4WZ/izLqsarnV1meqV4iZW8KITpiqiRiQVQLKOXnNHtSgaj9GtOP8uYqd9XIa1etNrze93hyqN5syRJO94vSK0yvO4YpTtwbxT1kpO7kC+/0rq3jB4oDKqj8+v2Mx9e35Dyymeh+6bqjcg7BAGsSUYiH9nYpgRHXbIuzuKo++Pf+u5dEW6/ryaF8e7cujfXm0L4/25dG+PNqXR/vyaF8e7cujfXm0L4++svOrL4++mvIo78ujP7o8euXScf5HNvYMKJmgfVK1LoVadS/hj8iVHbcmK8zRtX9scusSlPf/SIzJ9WQ8XnKTFPNRJLOx95nK/8NcSSMjmY7nqZyPM4bH4RgiqdfaQDbWkA/Pzs4vRln8z8GdsILif1XkRcWfbOUPQMJMtE2ojsgnzHyuuIatXG4zz1lO62u+fQq+T8H3Nd9eb3q96Wu+veL0ivN3UZxdNV8s/92XZYiTc7ga0nS2JxB1/TsLPfNivW+27d452ZVb9VGpzlzxqDtQsHWq2e7+3vr01qe3Pke7uwdkeY7OJ4fI/rLmKwj0TzRlAcgPJSSXGtvK4frcbfniQfhcQpDGcI+BlCB0LoV26C/OzrZTP7hH7tULrokuogi0dpqZK4lfkPM28cDiNaqtDyOIwCyKezzEPvBQoiJzGa8RmL2lYaXl3YuIuXhkKY+JzTB9tXc2uqD69IK2YmGvuhBfknWCgCk+oV3l5/aZPsCaTso3VQbUSuHet1U29yjaJpHlwyo+T0wndAz+jRUN6tFmdW6faaFSOqFlYiViaTpn0cOoNFtDN3YETwyL3e7RAUy8UESE76h8rl9cuXSDSjmp5dDLy473UOoHM+jF2cW74dkvw4t/3Zz/NPnpfHLx6+jsl/P/0eYjGc1nMJq47PUoanni7kAFj0iUF52aN5LaWtNx86Y8Z4NB7mjdugHhb8YcMcHfXDlkRvtmibsesnNGcBnktry60V7mbtNXor1v3LcIGB1cs9i3ceHVin3jmtcp9o3svkKxl4Zd1yb2TaquStRrDm5IdNyBOGLTfd37kBl17ey2LevVLYCg2F+7hAdK1KFDm/XxfYxr1MR3D9zc76x5b63UndbN7+XafaE1PAr3UVeXP2twe3jcLOkF1bd2XaehR9vlnG3FO4TtG2vQT0a1s2B0OGerMkOrANNWitmeia1SRD21UYEImsPCQ50qbxLesdwmZa2E4bGzm3HLCbOr6LB9QAVhX7u5bcDDIK/V2h4ahnR7D1IXpgWncxi9BZtw+uK3XdcW2JdtQ9MpDUFYrxCLS9iBfow7rt6OzkZnnf77dC2iREkhC00+eAdH47NeROcQ1QUrLA6G0YULn8h1ygw60uhNol9nA679cGNYoPdEvMnUJGMxkLmLECt4q4SnQLj1Hr2n6uIKP40slMwwzLBKQoIH7KxjeSecN/ZGVy6mRu/WJKChRs0WC6xuNTC3x3ehsFFg5dZXy5taf5AOaMojEBrqS6H0fc6iBMiF3Ybar5yMx6vVasRs70iq5dhP1eP/XH24/Di9HF6MzkaJyVKrNui0ZkwEgKtXAAXpfCYweOfv+BcDA4s1zlO0TxtP/bN3nG+pc5zvBzRBh3pyS5+f50zDf1W62WDztwLUmk5u79FDV5zNkWm3eLwlwKzxqlz5D47S4Y0LhLxDv/06YcOPv/40vUG1968aZjLGOYqt0PqyFZ1Qim8qVhfGbNszTZlYFs6DcTDx7/9PZV3M
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/anchor-platform/api-reference/callbacks/callbacks-server
-custom_edit_url: null
-hide_send_button: true
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={'SEP-6,SEP-24,SEP-31'} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Receive an Event"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/event"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Receive a JSON object representing an event.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./post-event.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./post-event.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/anchor-platform/api-reference/callbacks/post-event.mdx b/docs/platforms/anchor-platform/api-reference/callbacks/post-event.mdx
new file mode 100644
index 000000000..e93d9354c
--- /dev/null
+++ b/docs/platforms/anchor-platform/api-reference/callbacks/post-event.mdx
@@ -0,0 +1,8 @@
+---
+title: Receive an Event
+openapi: "openapi/anchor-platform/bundled-callbacks.yaml POST /event"
+playground: none
+---
+
+<Badge color="blue">SEP-6</Badge> <Badge color="blue">SEP-24</Badge>
+<Badge color="blue">SEP-31</Badge>
diff --git a/docs/platforms/anchor-platform/api-reference/callbacks/put-customer.RequestSchema.json b/docs/platforms/anchor-platform/api-reference/callbacks/put-customer.RequestSchema.json
deleted file mode 100644
index 5dfac89ca..000000000
--- a/docs/platforms/anchor-platform/api-reference/callbacks/put-customer.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"application/json":{"schema":{"type":"object","properties":{"id":{"description":"The ID of the customer as returned in the response of a previous PUT request.","type":"string"},"account":{"description":"The Stellar or Muxed Account authenticated with the Platform via SEP-10.","type":"string"},"memo":{"description":"The memo value identifying a customer with a shared account, where the shared account is `account`.","type":"string"},"memo_type":{"description":"The type of memo used to identify a customer with a shared account.","type":"string","enum":["id","hash","text"]},"type":{"description":"The type of action the customer is being KYCd for.\nSee the [Type Specification](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#type-specification) documented in SEP-12 for more info.\nFor SEP-31 you can define your own types in the assets configuration.\nFor SEP-24 pre-defined value `sep24-customer` is used.\n","type":"string"},"transaction_id":{"description":"The transaction id with which the customer's info is associated. When information from the customer depends on the\ntransaction (e.g., more information is required for larger amounts)\n","type":"string"},"first_name":{"type":"string"},"last_name":{"type":"string"},"additional_name":{"type":"string"},"address_country_code":{"type":"string"},"state_or_province":{"type":"string"},"city":{"type":"string"},"postal_code":{"type":"string"},"address":{"type":"string"},"mobile_number":{"type":"string"},"email_address":{"type":"string"},"birth_date":{"type":"string","format":"date"},"birth_place":{"type":"string"},"birth_country_code":{"type":"string"},"bank_name":{"type":"string"},"bank_account_number":{"type":"string"},"bank_account_type":{"type":"string"},"bank_number":{"type":"string"},"bank_phone_number":{"type":"string"},"bank_branch_number":{"type":"string"},"external_transfer_memo":{"type":"string"},"clabe_number":{"type":"string"},"cbu_alias":{"type":"string"},"mobile_money_number":{"type":"string"},"mobile_money_provider":{"type":"string"},"crypto_address":{"type":"string"},"crypto_memo":{"description":"Deprecated. Use `external_transfer_memo` instead.","type":"string"},"tax_id":{"type":"string"},"tax_id_name":{"type":"string"},"occupation":{"type":"string"},"employer_name":{"type":"string"},"employer_address":{"type":"string"},"language_code":{"type":"string"},"id_type":{"type":"string"},"id_country_code":{"type":"string"},"id_issue_date":{"type":"string","format":"date"},"id_expiration_date":{"type":"string","format":"date"},"id_number":{"type":"string"},"ip_address":{"type":"string"},"sex":{"type":"string"},"referral_id":{"type":"string"},"mobile_number_verification":{"type":"string"},"email_address_verification":{"type":"string"}},"title":"PutCustomerRequest"}},"multipart/form-data":{"schema":{"type":"object","properties":{"id":{"description":"The ID of the customer as returned in the response of a previous PUT request.","type":"string"},"account":{"description":"The Stellar or Muxed Account authenticated with the Platform via SEP-10.","type":"string"},"memo":{"description":"The memo value identifying a customer with a shared account, where the shared account is `account`.","type":"string"},"memo_type":{"description":"The type of memo used to identify a customer with a shared account.","type":"string","enum":["id","hash","text"]},"type":{"description":"The type of action the customer is being KYCd for.\nSee the [Type Specification](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#type-specification) documented in SEP-12 for more info.\nFor SEP-31 you can define your own types in the assets configuration.\nFor SEP-24 pre-defined value `sep24-customer` is used.\n","type":"string"},"first_name":{"type":"string"},"last_name":{"type":"string"},"additional_name":{"type":"string"},"address_country_code":{"type":"string"},"state_or_province":{"type":"string"},"city":{"type":"string"},"postal_code":{"type":"string"},"address":{"type":"string"},"mobile_number":{"type":"string"},"email_address":{"type":"string"},"birth_date":{"type":"string","format":"date"},"birth_place":{"type":"string"},"birth_country_code":{"type":"string"},"bank_name":{"type":"string"},"bank_account_number":{"type":"string"},"bank_account_type":{"type":"string"},"bank_number":{"type":"string"},"bank_phone_number":{"type":"string"},"bank_branch_number":{"type":"string"},"external_transfer_memo":{"type":"string"},"clabe_number":{"type":"string"},"cbu_alias":{"type":"string"},"mobile_money_number":{"type":"string"},"mobile_money_provider":{"type":"string"},"crypto_address":{"type":"string"},"crypto_memo":{"description":"Deprecated. Use `external_transfer_memo` instead.","type":"string"},"tax_id":{"type":"string"},"tax_id_name":{"type":"string"},"occupation":{"type":"string"},"employer_name":{"type":"string"},"employer_address":{"type":"string"},"language_code":{"type":"string"},"id_type":{"type":"string"},"id_country_code":{"type":"string"},"id_issue_date":{"type":"string","format":"date"},"id_expiration_date":{"type":"string","format":"date"},"id_number":{"type":"string"},"photo_id_front":{"type":"string","format":"binary"},"photo_id_back":{"type":"string","format":"binary"},"notary_approval_of_photo_id":{"type":"string","format":"binary"},"ip_address":{"type":"string"},"photo_proof_residence":{"type":"string","format":"binary"},"sex":{"type":"string"},"photo_proof_of_income":{"type":"string","format":"binary"},"proof_of_liveness":{"type":"string","format":"binary"},"referral_id":{"type":"string"},"mobile_number_verification":{"type":"string"},"email_address_verification":{"type":"string"}},"title":"PutCustomerMultipartRequest"}}}}}
\ No newline at end of file
diff --git a/docs/platforms/anchor-platform/api-reference/callbacks/put-customer.StatusCodes.json b/docs/platforms/anchor-platform/api-reference/callbacks/put-customer.StatusCodes.json
deleted file mode 100644
index c82c221df..000000000
--- a/docs/platforms/anchor-platform/api-reference/callbacks/put-customer.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Success.","content":{"application/json":{"schema":{"type":"object","required":["status"],"properties":{"id":{"type":"string"},"status":{"type":"string","enum":["ACCEPTED","PROCESSING","NEEDS_INFO","REJECTED"]},"fields":{"type":"object","additionalProperties":{"required":["type","description"],"properties":{"type":{"type":"string","enum":["string","binary","number","date"]},"description":{"type":"string"},"choices":{"type":"array","items":{"type":"string"}},"optional":{"type":"boolean"}}}},"provided_fields":{"type":"object","additionalProperties":{"required":["type","description"],"properties":{"type":{"type":"string","enum":["string","binary","number","date"]},"description":{"type":"string"},"choices":{"type":"array","items":{"type":"string"}},"optional":{"type":"boolean"},"status":{"type":"string","enum":["ACCEPTED","PROCESSING","REJECTED","VERIFICATION_REQUIRED"]},"error":{"type":"string"}}}},"message":{"type":"string"}},"title":"GetCustomerResponse"}}}},"400":{"description":"Invalid data.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}},"404":{"description":"Not Found.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/anchor-platform/api-reference/callbacks/put-customer.api.mdx b/docs/platforms/anchor-platform/api-reference/callbacks/put-customer.api.mdx
deleted file mode 100644
index 101bdb8ef..000000000
--- a/docs/platforms/anchor-platform/api-reference/callbacks/put-customer.api.mdx
+++ /dev/null
@@ -1,81 +0,0 @@
----
-id: put-customer
-title: "Create or Update Customer Info"
-description: "**The Anchor Platform does not persist any customer KYC data.**"
-sidebar_label: "Create or Update Customer Info"
-hide_title: true
-hide_table_of_contents: true
-api: eJztGmtv47jxrxDsh7tdyHLWF7Sov6Ve78G9XjbNo8UhDmRKGkW8lUgdSSUxAv/3YkjJelhytr0W6AL+ksic4bw4M5wh+UoNe9R0fk8XpTYyB6Xpg0dfJhoKO3yzvJr8kXr2/4dZ9TE7rz5++IDYMehI8cJwKeicvn9/mwK5EFEqFbnKmEmkykksQRMhDSlAaa4NYWJLooon+emXBYmZYf7792uxFkhAwW8lWLyYKNCFFBpIIhUxKdcERFxILgxhCgiPQRgesYwYSUwKa3G/ubq7JdOa/ubh+9SYQs+n00du0jL0I5lPtYEsY6r+PymUNDKS2TTMZDjNmTagphBJvdUG8qmGYnJ29mHm5/EfasKTojTv1mJQ1hgSLiAmXBBnPB9VW2QcUOyiyHjE0GSa5OzLXl9NnrlJUQuSyCyTz1w87m0RynjrkeeURynhGq3xzFQMcaU3YdbofmV8vRZ5qQ15YhmPmQErXm1+REeLk4JpDbFXyW5KJSys1vA7TTY83vjkupYvksIwLlAuKbIt0Ubhd8Ihi1H6LFuLEMaEI6yl4aZlhumvWoqNpY4GMtsCBpmuRcgFU9s2Q/K1/PIyM7xgykzRKSdogB7LtaAelQUoK9QqpnNalKYODurRai3+IuMtnb/SajJ+9pXBMR2lkDP8Qup0TmX4K0SGerRQyMVw0AjlMf7tBhJGweojkUlnQVAht07Ot4yNlcrnZEIYKRQ8cVlqgjFQietTr5bArRfdeZRFkSyd7Iecb1xUEKnIz+ULxOTCYRNWmtTFm4G4se0+0p84cw5/Nsg0h1wOc0QIOmtZR3SyRcdijeqWGSM6ZQpiUomPAQEKrBBdCMbIpvrejAoTuNEhiRCCNrWSldr5Vi3bm4IdcvQoiDLHtMpj6tGU6RRx4MXQh12NfEwQFuFg1x+4JiGgoX76ZRFjGPhrcQPOHve3OPGmgIgnlWv+t1MhijbRbQ7vSCyjMgdh2tnP5u5cYroWifTX4pNUxO0hZCtLEjFRpUz8qYh8FlZtXTs55imXCRL+WLr4bJGZnaPjT+qs6/xoo6GYnU/2+wAaC9fRhfmBOxjFhHY2DsYisoVDeOX/LiP30iaqifyY1jLiGCw++WcKwgJUbuUniZJ5dzljKEDEmrhlXos2v+/Bf/S9xoo1Fa5tnHN0PjRzxtQjZooc3VC/G1Y24UqbQLAcWumpAWfsGJTFMUfWLDuKo0DrwAaD2gaRjIcRtWEGAqmCQsknLqJhrIib7SCgkNqwbJx8JccgLJchzyAQZR6CGsSAnPEsOEYj5MqkAe6wh2CPulWic2oR9uhFxkb0dPA3jRYy8WXc9hZa5aFj2nXw6vwzwusNKkUqxVFLWqxQ4b581OAvBhQ6lvX8BFRQbxmHLpGx8CjLKCwDlnF2dPFzKWB7jEoHz/poPMZPbQsjj3pLhTK8DX6EQkHkcsWdBrIZNsaGcKENsHhwUzPspcpeI6Bxt5FRVBbMCTMYC0Umt6DGCewxjpkgY+KxZI8w7tw8HndGHr8dHDwOuNYlfH1U8jiAl4K7beXfmnbEcXhx1A4aXgbHFSSgFMvGVrGTtIInUPut9+0M9hY6Ogk3GQ5dNXVvVYdb8EANfap0T5XuqdL9lirdU/F3Kv5Oxd+p+DsVf/+z4q9IpZFo8ERJV3qMEnQnmp1JIYu+fOUcIQ1T24AV6J0sC2QS1GS+ksIbdaqjVigpk0CBxrJgKH0Nkh6rcds0ZRJwEckhrxo2Uj0r408gBqUenPf/V1f/XNfSTYG9s4K6KtcqNjs7O8wVN2UUgdaYAv7jE+j6yAirNNyFS3v1M1StD27a5aDZ67LvYrFYXt0uP1KPXl1/XixvblaXP1KPXi6XH2+C1eWnz9Sj18u/LheI9GBLEjzPHxK0qTeuOsK1FbBzuldRB8oMZ5VG5v1A5TIercLbcyGPUnaWYSjDp5JHbXaUKcWQFjeQD8UXZt7CqdeChlJmwETlENW+EwcnIw0a6fd45N4JPfqP5fXq02pxcbv6fBlcL/9+t7qunBOUkkNp3q5ODlqzx6HNqBX1P0Krm3bhXU0/HwrwlbDXdu5W9PdEeXd1x/TwhiN9180SbvZDo9TSDtRqnB+qcSkN+SRLEX8LOlT1p9B4K0vn96/0C2zpvL4N96httb7uVnz3gH5hUlndIKIWzKR0Tve30hR3R/WEV+7Iq1QZndO6ZY1YlmEN4Iel5rjHTRyuDy8sL9Dr7VVvJHOKrNCG183N5NIh1Rm8CYb9QUgz5IrR7u+qAHPNez+g+rckrT231VU2o61msiVIv4fsgAZaxwY+0DE2QNcoNr87/eEBj47e3W6wlUC6TWA7Aza9H52dzc4nZ3+azP5Me21ef8KYXq2mrjfY7+VGwP2F6nRuveFuw9YD9vq0lilG2rOW/TtdWWu8acYOTN7twUbATevVItrruA4gfenq7qg/cmD2di/U9oROCzQAGBCl1/A0gH2f0xka845eV9P1t6EG5gDj0MDtur8VX1iyNz87VfNIuPSq35HYGcHCxC0S2xBjMnSwH/wz/4z23xbZ49qtiFIlBZ77LqosqcnF1Yp0zuaqt0LN8W7/RVKhJG4vfv3gaJyuO2nTzROdnMVAwm33NPg55RkQbs9iCyWxPHeHuvXrHXvXy0h08ALIJ7d40+tS+nd6f8itq6csuvU6iCUJRKbLuY8/xMIdA1ZbXqPejd1U0Et5BFiSzF9p5dwXBYtSIDO7DM3mNJ9On5+ffWahvlSP02qqnv5ttVhe3iwnM//MT02e2b0XE3DORIvwQgG+RpKK3BX2XVJdF5EVusFB+bgvG05Py05Py771p2VVxsebkGmRMW6bFxtdr1WBeE/3BeKDR1OpDY69voZMw53Kdjsc/q0EtaXz+wcsShVnIcb1PXYqKTC7S+6r14WTYXLrmr+qhh28xtt59aSLKILCtNAPCvZOgXt1d4u1Q/UmLndbF9K1ZL3mE2Xc7f4Fg5L/Sw==
-sidebar_class_name: "put api-method"
-info_path: docs/platforms/anchor-platform/api-reference/callbacks/callbacks-server
-custom_edit_url: null
-hide_send_button: true
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={'SEP-6,SEP-12,SEP-24,SEP-31'} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create or Update Customer Info"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"put"}
-  path={"/customer"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-**The Anchor Platform does not persist any customer KYC data.**
-
-The request and response for this endpoint are identical to the
-[`PUT /customer`](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#customer-put)
-request and response defined in SEP-12.
-
-Client applications make requests with the following request body, which is forwarded to the anchor. Anchors
-must validate and persist the data passed, and return the customer's `id`. Requests containing only string fields will
-be forwarded to the anchor as with the `application/json` content type. Requests containing
-binary fields will be forwarded to the anchor as with the `multipart/form-data` content type.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./put-customer.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./put-customer.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/anchor-platform/api-reference/callbacks/put-customer.mdx b/docs/platforms/anchor-platform/api-reference/callbacks/put-customer.mdx
new file mode 100644
index 000000000..4560e76dc
--- /dev/null
+++ b/docs/platforms/anchor-platform/api-reference/callbacks/put-customer.mdx
@@ -0,0 +1,8 @@
+---
+title: Create or Update Customer Info
+openapi: "openapi/anchor-platform/bundled-callbacks.yaml PUT /customer"
+playground: none
+---
+
+<Badge color="blue">SEP-6</Badge> <Badge color="blue">SEP-12</Badge>
+<Badge color="blue">SEP-24</Badge> <Badge color="blue">SEP-31</Badge>
diff --git a/docs/platforms/anchor-platform/api-reference/index.mdx b/docs/platforms/anchor-platform/api-reference/index.mdx
new file mode 100644
index 000000000..e397bcfea
--- /dev/null
+++ b/docs/platforms/anchor-platform/api-reference/index.mdx
@@ -0,0 +1,17 @@
+---
+title: API Reference
+description: "View all Anchor Platform API information."
+---
+
+<CardGroup cols={2}>
+  <Card title="Platform Server" icon="box-archive" href="/docs/platforms/anchor-platform/api-reference/platform">
+
+    2 items
+
+  </Card>
+  <Card title="Callbacks Server" icon="box-archive" href="/docs/platforms/anchor-platform/api-reference/callbacks">
+
+    5 items
+
+  </Card>
+</CardGroup>
diff --git a/docs/platforms/anchor-platform/api-reference/platform/README.mdx b/docs/platforms/anchor-platform/api-reference/platform/README.mdx
deleted file mode 100644
index fbffe1216..000000000
--- a/docs/platforms/anchor-platform/api-reference/platform/README.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: Platform Server
-sidebar_position: 10
----
-
-import { MethodTable } from "@site/src/components/MethodTable";
-
-Data on the Anchor Platform is available through two different APIs:
-
-<MethodTable title="API Types">
-
-|                                       |     |
-| ------------------------------------- | --- |
-| [REST API](./transactions/README.mdx) |     |
-| [JSON-RPC API](./rpc/README.mdx)      |     |
-
-</MethodTable>
diff --git a/docs/platforms/anchor-platform/api-reference/platform/index.mdx b/docs/platforms/anchor-platform/api-reference/platform/index.mdx
new file mode 100644
index 000000000..9bce4c5e7
--- /dev/null
+++ b/docs/platforms/anchor-platform/api-reference/platform/index.mdx
@@ -0,0 +1,11 @@
+---
+title: Platform Server
+description: "Data on the Anchor Platform is available through two different APIs: a REST API and a JSON-RPC API."
+---
+
+Data on the Anchor Platform is available through two different APIs:
+
+| API Types |  |
+| --- | --- |
+| [REST API](/docs/platforms/anchor-platform/api-reference/platform/transactions) |  |
+| [JSON-RPC API](/docs/platforms/anchor-platform/api-reference/platform/rpc) |  |
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/README.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/README.mdx
deleted file mode 100644
index 60798cab0..000000000
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: JSON-RPC API
-sidebar_position: 20
----
-
-import DocCardList from "@theme/DocCardList";
-
-Interact with your Anchor Platform instance through the use of lightweight, easy-to-use RPC requests.
-
-<DocCardList />
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/anchor-platform.openrpc.json b/docs/platforms/anchor-platform/api-reference/platform/rpc/anchor-platform.openrpc.json
index d7a88deae..db64091b5 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/anchor-platform.openrpc.json
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/anchor-platform.openrpc.json
@@ -1276,7 +1276,7 @@
               "type": "string"
             },
             "customers": {
-              "description": "The Identification info of the sending and receiving customers. If they were created through [SEP-12](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md),\n            this object should contain the SEP-12 customer `id`. Otherwise, the `account` address of the customer.",
+              "description": "The Identification info of the sending and receiving customers. If they were created through [SEP-12](https://stellar.org/protocol/sep-12),\n            this object should contain the SEP-12 customer `id`. Otherwise, the `account` address of the customer.",
               "type": "object",
               "properties": {
                 "sender": {
@@ -1992,7 +1992,7 @@
                     "type": "string"
                   },
                   "customers": {
-                    "description": "The Identification info of the sending and receiving customers. If they were created through [SEP-12](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md),\n            this object should contain the SEP-12 customer `id`. Otherwise, the `account` address of the customer.",
+                    "description": "The Identification info of the sending and receiving customers. If they were created through [SEP-12](https://stellar.org/protocol/sep-12),\n            this object should contain the SEP-12 customer `id`. Otherwise, the `account` address of the customer.",
                     "type": "object",
                     "properties": {
                       "sender": {
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/index.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/index.mdx
new file mode 100644
index 000000000..eb0f84e52
--- /dev/null
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/index.mdx
@@ -0,0 +1,17 @@
+---
+title: JSON-RPC API
+description: "Interact with your Anchor Platform instance through the use of lightweight, easy-to-use RPC requests."
+---
+
+<CardGroup cols={2}>
+  <Card title="Overview" icon="file-lines" href="/docs/platforms/anchor-platform/api-reference/platform/rpc/overview">
+
+    JSON-RPC is a stateless, light-weight remote procedure call (RPC) protocol.
+
+  </Card>
+  <Card title="Methods" icon="box-archive" href="/docs/platforms/anchor-platform/api-reference/platform/rpc/methods">
+
+    23 items
+
+  </Card>
+</CardGroup>
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/README.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/README.mdx
deleted file mode 100644
index 2b0cdd403..000000000
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/README.mdx
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: JSON-RPC Methods
-order: 20
-sidebar_label: Methods
----
-
-This section lists the Anchor Platform JSON-RPC API methods that should be called by Stellar clients to update status of the transaction.
-
-The OpenRPC Specification for JSON-RPC API is available [here](https://playground.open-rpc.org/?schemaUrl=https://raw.githubusercontent.com/stellar/stellar-docs/main/static/assets/rpc-methods/open-rpc.json).
-
-Postman collection is available [here](https://documenter.getpostman.com/view/9257637/2s9Y5U1kra)
-
-<EndpointsTable title="JSON-RPC Methods">
-
-|  |  |
-| --- | --- |
-|  | [do_stellar_payment](./do_stellar_payment.mdx) |
-|  | [do_stellar_refund](./do_stellar_refund.mdx) |
-|  | [get_transaction](./get_transaction.mdx) |
-|  | [get_transactions](./get_transactions.mdx) |
-|  | [notify_amounts_updated](./notify_amounts_updated.mdx) |
-|  | [notify_customer_info_updated](./notify_customer_info_updated.mdx) |
-|  | [notify_interactive_flow_completed](./notify_interactive_flow_completed.mdx) |
-|  | [notify_offchain_funds_available](./notify_offchain_funds_available.mdx) |
-|  | [notify_offchain_funds_pending](./notify_offchain_funds_pending.mdx) |
-|  | [notify_offchain_funds_received](./notify_offchain_funds_received.mdx) |
-|  | [notify_offchain_funds_sent](./notify_offchain_funds_sent.mdx) |
-|  | [notify_onchain_funds_received](./notify_onchain_funds_received.mdx) |
-|  | [notify_onchain_funds_sent](./notify_onchain_funds_sent.mdx) |
-|  | [notify_refund_pending](./notify_refund_pending.mdx) |
-|  | [notify_refund_sent](./notify_refund_sent.mdx) |
-|  | [notify_transaction_error](./notify_transaction_error.mdx) |
-|  | [notify_transaction_expired](./notify_transaction_expired.mdx) |
-|  | [notify_transaction_on_hold](./notify_transaction_on_hold.mdx) |
-|  | [notify_transaction_recovery](./notify_transaction_recovery.mdx) |
-|  | [notify_trust_set](./notify_trust_set.mdx) |
-|  | [request_offchain_funds](./request_offchain_funds.mdx) |
-|  | [request_onchain_funds](./request_onchain_funds.mdx) |
-|  | [request_trust](./request_trust.mdx) |
-
-</EndpointsTable>
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_payment.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_payment.mdx
index 3f82ad67f..72e96f879 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_payment.mdx
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_payment.mdx
@@ -1,13 +1,398 @@
 ---
 title: do_stellar_payment
-hide_title: true
+description: "<RpcMethod"
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={
-    rpcSpec.methods.filter((meth) => meth.name === "do_stellar_payment")[0]
+`SEP-6` `SEP-24`
+
+Submits a payment to the Stellar network by a custody service.
+
+## Params (2)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="transaction_id" type="string" required>
+
+The unique identifier of this transaction.
+
+A unique transaction identifier.
+
+</ParamField>
+
+<ParamField body="message" type="string">
+
+Human readable explanation of transaction status.
+
+A human readable message.
+
+</ParamField>
+
+## Result
+
+_(do_stellar_paymentResponse)_
+
+<ResponseField name="id" type="string">
+
+A unique transaction identifier.
+
+</ResponseField>
+
+<ResponseField name="sep" type="integer">
+
+Protocol of the transaction.
+
+Available options: `6`, `24`, `31`
+
+</ResponseField>
+
+<ResponseField name="kind" type="string">
+
+The kind of transaction that is desired.
+
+Available options: `undefined`, `receive`, `deposit`, `deposit-exchange`, `withdrawal`, `withdrawal-exchange`
+
+</ResponseField>
+
+<ResponseField name="status" type="string">
+
+Processing status of the transaction.
+
+Available options: `pending_anchor`, `pending_trust`, `pending_user`, `pending_user_transfer_start`, `pending_user_transfer_complete`, `incomplete`, `no_market`, `too_small`, `too_large`, `pending_sender`, `pending_receiver`, `pending_transaction_info_update`, `pending_customer_info_update`, `completed`, `refunded`, `expired`, `error`, `pending_external`, `pending_stellar`
+
+</ResponseField>
+
+<ResponseField name="amount_expected" type="object">
+
+The amount expected in the payment.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_in" type="object">
+
+Amount expected/received by anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_out" type="object">
+
+The amount expected to be sent by anchor to user at end of transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="fee_details" type="object">
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="total" type="number" required>
+    </ResponseField>
+    <ResponseField name="asset" type="string" required>
+    </ResponseField>
+    <ResponseField name="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ResponseField name="name" type="string">
+        </ResponseField>
+        <ResponseField name="description" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="number">
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="quote_id" type="string">
+
+The id returned from a SEP-38 POST /quote response
+
+</ResponseField>
+
+<ResponseField name="started_at" type="string">
+
+Start date and time of transaction.
+
+</ResponseField>
+
+<ResponseField name="updated_at" type="string">
+
+The date and time of transaction reaching the current status.
+
+</ResponseField>
+
+<ResponseField name="completed_at" type="string">
+
+The date and time of transaction reaching completed or refunded status.
+
+</ResponseField>
+
+<ResponseField name="transfer_received_at" type="string">
+
+The date and time of receiving transfer.
+
+</ResponseField>
+
+<ResponseField name="message" type="string">
+
+Human readable explanation of transaction status
+
+</ResponseField>
+
+<ResponseField name="refunds" type="object">
+
+An object describing any on or offchain refund associated with this transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount_refunded" type="object">
+
+      The total amount refunded in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="amount_fee" type="object">
+
+      The total amount charged in fees for processing all refund payments, in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="payments" type="object[]">
+
+      A list of objects containing information on the individual payments made back as refunds.
+
+      <Expandable title="items">
+        <ResponseField name="id" type="string">
+
+          The Stellar transaction hash.
+
+        </ResponseField>
+        <ResponseField name="id_type" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="object">
+
+          The amount sent back for the payment identified by id, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="fee" type="object">
+
+          The amount charged as a fee for processing the refund, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="requested_at" type="string">
+
+          The date and time of requesting refund.
+
+        </ResponseField>
+        <ResponseField name="refunded_at" type="string">
+
+          The date and time of making refund.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+## Example
+
+Example request to the `do_stellar_payment` method.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "do_stellar_payment",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Do Stellar payment"
+  }
+}' \
+https://platform-server.exampleanchor.com | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "do_stellar_payment",
+  params: {
+    transaction_id: "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    message: "Do Stellar payment",
+  },
+};
+let res = await fetch("https://platform-server.exampleanchor.com", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://platform-server.exampleanchor.com", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "do_stellar_payment",
+    "params": {
+        "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+        "message": "Do Stellar payment"
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "do_stellar_payment",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Do Stellar payment"
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "sep": "24",
+    "kind": "deposit",
+    "status": "completed",
+    "amount_expected": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_in": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_out": {
+      "amount": "0.9",
+      "asset": "iso4217:USD"
+    },
+    "fee_details": {
+      "total": "0.1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "started_at": "2023-08-04T10:04:06.280923Z",
+    "updated_at": "2023-08-04T10:04:15.716233Z",
+    "message": "Transaction complete",
+    "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
+    "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
   }
-/>
+}
+```
+
+{/* /rpc-method */}
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_refund.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_refund.mdx
index 681686277..ea554b7c2 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_refund.mdx
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_refund.mdx
@@ -1,13 +1,483 @@
 ---
 title: do_stellar_refund
-hide_title: true
+description: "<RpcMethod"
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={
-    rpcSpec.methods.filter((meth) => meth.name === "do_stellar_refund")[0]
+`SEP-6` `SEP-24` `SEP-31`
+
+Submits a refund payment to the Stellar network by a custody service
+
+## Params (3)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="transaction_id" type="string" required>
+
+The unique identifier of this transaction.
+
+A unique transaction identifier.
+
+</ParamField>
+
+<ParamField body="message" type="string">
+
+Human readable explanation of transaction status.
+
+A human readable message.
+
+</ParamField>
+
+<ParamField body="refund" type="object">
+
+An object describing refund associated with this transaction.
+
+  <Expandable title="properties">
+    <ParamField body="amount" type="object" required>
+
+      Amount to be refunded
+
+      <Expandable title="properties">
+        <ParamField body="amount" type="string" required>
+
+          Amount of assets to refund
+
+        </ParamField>
+        <ParamField body="asset" type="string" required>
+
+          The asset of refund
+
+        </ParamField>
+      </Expandable>
+    </ParamField>
+    <ParamField body="amount_fee" type="object" required>
+
+      Amount of fee
+
+      <Expandable title="properties">
+        <ParamField body="amount" type="string" required>
+
+          The amount of fee
+
+        </ParamField>
+        <ParamField body="asset" type="string" required>
+
+          The asset of fee charged by anchor
+
+        </ParamField>
+      </Expandable>
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+## Result
+
+_(do_stellar_refundResponse)_
+
+<ResponseField name="id" type="string">
+
+A unique transaction identifier.
+
+</ResponseField>
+
+<ResponseField name="sep" type="integer">
+
+Protocol of the transaction.
+
+Available options: `6`, `24`, `31`
+
+</ResponseField>
+
+<ResponseField name="kind" type="string">
+
+The kind of transaction that is desired.
+
+Available options: `undefined`, `receive`, `deposit`, `deposit-exchange`, `withdrawal`, `withdrawal-exchange`
+
+</ResponseField>
+
+<ResponseField name="status" type="string">
+
+Processing status of the transaction.
+
+Available options: `pending_anchor`, `pending_trust`, `pending_user`, `pending_user_transfer_start`, `pending_user_transfer_complete`, `incomplete`, `no_market`, `too_small`, `too_large`, `pending_sender`, `pending_receiver`, `pending_transaction_info_update`, `pending_customer_info_update`, `completed`, `refunded`, `expired`, `error`, `pending_external`, `pending_stellar`
+
+</ResponseField>
+
+<ResponseField name="amount_expected" type="object">
+
+The amount expected in the payment.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_in" type="object">
+
+Amount expected/received by anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_out" type="object">
+
+The amount expected to be sent by anchor to user at end of transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="fee_details" type="object">
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="total" type="number" required>
+    </ResponseField>
+    <ResponseField name="asset" type="string" required>
+    </ResponseField>
+    <ResponseField name="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ResponseField name="name" type="string">
+        </ResponseField>
+        <ResponseField name="description" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="number">
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="quote_id" type="string">
+
+The id returned from a SEP-38 POST /quote response
+
+</ResponseField>
+
+<ResponseField name="started_at" type="string">
+
+Start date and time of transaction.
+
+</ResponseField>
+
+<ResponseField name="updated_at" type="string">
+
+The date and time of transaction reaching the current status.
+
+</ResponseField>
+
+<ResponseField name="completed_at" type="string">
+
+The date and time of transaction reaching completed or refunded status.
+
+</ResponseField>
+
+<ResponseField name="transfer_received_at" type="string">
+
+The date and time of receiving transfer.
+
+</ResponseField>
+
+<ResponseField name="message" type="string">
+
+Human readable explanation of transaction status
+
+</ResponseField>
+
+<ResponseField name="refunds" type="object">
+
+An object describing any on or offchain refund associated with this transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount_refunded" type="object">
+
+      The total amount refunded in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="amount_fee" type="object">
+
+      The total amount charged in fees for processing all refund payments, in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="payments" type="object[]">
+
+      A list of objects containing information on the individual payments made back as refunds.
+
+      <Expandable title="items">
+        <ResponseField name="id" type="string">
+
+          The Stellar transaction hash.
+
+        </ResponseField>
+        <ResponseField name="id_type" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="object">
+
+          The amount sent back for the payment identified by id, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="fee" type="object">
+
+          The amount charged as a fee for processing the refund, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="requested_at" type="string">
+
+          The date and time of requesting refund.
+
+        </ResponseField>
+        <ResponseField name="refunded_at" type="string">
+
+          The date and time of making refund.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+## Example
+
+Example request to the `do_stellar_refund` method.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "do_stellar_refund",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Do Stellar refund",
+    "refund": {
+      "amount": {
+        "amount": 1,
+        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+      },
+      "amount_fee": {
+        "amount": 0.1,
+        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+      }
+    }
   }
-/>
+}' \
+https://platform-server.exampleanchor.com | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "do_stellar_refund",
+  params: {
+    transaction_id: "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    message: "Do Stellar refund",
+    refund: {
+      amount: {
+        amount: 1,
+        asset:
+          "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5",
+      },
+      amount_fee: {
+        amount: 0.1,
+        asset:
+          "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5",
+      },
+    },
+  },
+};
+let res = await fetch("https://platform-server.exampleanchor.com", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://platform-server.exampleanchor.com", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "do_stellar_refund",
+    "params": {
+        "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+        "message": "Do Stellar refund",
+        "refund": {
+            "amount": {
+                "amount": 1,
+                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+            },
+            "amount_fee": {
+                "amount": 0.1,
+                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+            }
+        }
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "do_stellar_refund",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Do Stellar refund",
+    "refund": {
+      "amount": {
+        "amount": 1,
+        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+      },
+      "amount_fee": {
+        "amount": 0.1,
+        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+      }
+    }
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "sep": "24",
+    "kind": "deposit",
+    "status": "completed",
+    "amount_expected": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_in": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_out": {
+      "amount": "0.9",
+      "asset": "iso4217:USD"
+    },
+    "fee_details": {
+      "total": "0.1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "started_at": "2023-08-04T10:04:06.280923Z",
+    "updated_at": "2023-08-04T10:04:15.716233Z",
+    "message": "Transaction complete",
+    "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
+    "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
+  }
+}
+```
+
+{/* /rpc-method */}
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transaction.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transaction.mdx
index c313dc6a1..4417f8003 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transaction.mdx
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transaction.mdx
@@ -1,11 +1,675 @@
 ---
 title: get_transaction
-hide_title: true
+description: "<RpcMethod"
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "get_transaction")[0]}
-/>
+`SEP-6` `SEP-24` `SEP-31`
+
+Retrieve a transaction by its ID.
+
+## Params (1)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="id" type="string" required>
+
+The unique identifier of this transaction.
+
+A unique transaction identifier.
+
+</ParamField>
+
+## Result
+
+_(get_transactionResponse)_
+
+<ResponseField name="id" type="string">
+
+A unique transaction identifier.
+
+</ResponseField>
+
+<ResponseField name="sep" type="integer">
+
+Protocol of the transaction.
+
+Available options: `6`, `24`, `31`
+
+</ResponseField>
+
+<ResponseField name="kind" type="string">
+
+The kind of transaction that is desired.
+
+Available options: `undefined`, `receive`, `deposit`, `deposit-exchange`, `withdrawal`, `withdrawal-exchange`
+
+</ResponseField>
+
+<ResponseField name="status" type="string">
+
+Processing status of the transaction.
+
+Available options: `pending_anchor`, `pending_trust`, `pending_user`, `pending_user_transfer_start`, `pending_user_transfer_complete`, `incomplete`, `no_market`, `too_small`, `too_large`, `pending_sender`, `pending_receiver`, `pending_transaction_info_update`, `pending_customer_info_update`, `completed`, `refunded`, `expired`, `error`, `pending_external`, `pending_stellar`
+
+</ResponseField>
+
+<ResponseField name="funding_method" type="string">
+
+Funding method used for transferring or settling assets.
+
+</ResponseField>
+
+<ResponseField name="type" type="string">
+
+DEPRECATED in favor of funding_method. Type of deposit, withdrawal or receive.
+
+</ResponseField>
+
+<ResponseField name="amount_expected" type="object">
+
+The amount expected in the payment.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_in" type="object">
+
+Amount expected/received by anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_out" type="object">
+
+The amount expected to be sent by anchor to user at end of transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="fee_details" type="object">
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="total" type="number" required>
+    </ResponseField>
+    <ResponseField name="asset" type="string" required>
+    </ResponseField>
+    <ResponseField name="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ResponseField name="name" type="string">
+        </ResponseField>
+        <ResponseField name="description" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="number">
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="quote_id" type="string">
+
+The id returned from a SEP-38 POST /quote response
+
+</ResponseField>
+
+<ResponseField name="started_at" type="string">
+
+Start date and time of transaction.
+
+</ResponseField>
+
+<ResponseField name="updated_at" type="string">
+
+The date and time of transaction reaching the current status.
+
+</ResponseField>
+
+<ResponseField name="completed_at" type="string">
+
+The date and time of transaction reaching completed or refunded status.
+
+</ResponseField>
+
+<ResponseField name="transfer_received_at" type="string">
+
+The date and time of receiving transfer.
+
+</ResponseField>
+
+<ResponseField name="user_action_required_by" type="string">
+
+Time and date by which user action is required.
+
+</ResponseField>
+
+<ResponseField name="message" type="string">
+
+Human readable explanation of transaction status
+
+</ResponseField>
+
+<ResponseField name="refunds" type="object">
+
+An object describing any on or offchain refund associated with this transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount_refunded" type="object">
+
+      The total amount refunded in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="amount_fee" type="object">
+
+      The total amount charged in fees for processing all refund payments, in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="payments" type="object[]">
+
+      A list of objects containing information on the individual payments made back as refunds.
+
+      <Expandable title="items">
+        <ResponseField name="id" type="string">
+
+          The Stellar transaction hash.
+
+        </ResponseField>
+        <ResponseField name="id_type" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="object">
+
+          The amount sent back for the payment identified by id, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="fee" type="object">
+
+          The amount charged as a fee for processing the refund, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="requested_at" type="string">
+
+          The date and time of requesting refund.
+
+        </ResponseField>
+        <ResponseField name="refunded_at" type="string">
+
+          The date and time of making refund.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="stellar_transactions" type="object[]">
+  <Expandable title="items">
+    <ResponseField name="id" type="string" required>
+
+      The Stellar transaction hash.
+
+    </ResponseField>
+    <ResponseField name="memo" type="string">
+    </ResponseField>
+    <ResponseField name="memo_type" type="string">
+
+      The memo type of the transaction in the Stellar network. Should be present if memo is not null.
+
+      Available options: `id`, `hash`, `text`
+
+    </ResponseField>
+    <ResponseField name="created_at" type="string" required>
+
+      The date and time when the transaction is created.
+
+    </ResponseField>
+    <ResponseField name="envelop" type="string">
+
+      The transaction envelope, containing all the transaction information.
+
+    </ResponseField>
+    <ResponseField name="payments" type="object[]" required>
+      <Expandable title="items">
+        <ResponseField name="id" type="string" required>
+
+           The ID of the payment in the Stellar Network.
+
+        </ResponseField>
+        <ResponseField name="payment_type" type="string" required>
+
+           The ID of the payment in the Stellar Network.
+
+          Available options: `payment`, `path_payment`
+
+          Default: `"payment"`
+
+        </ResponseField>
+        <ResponseField name="source_account" type="string" required>
+
+          The account being debited in the Stellar Network.
+
+        </ResponseField>
+        <ResponseField name="destination_account" type="string" required>
+
+          The account being credited in the Stellar Network.
+
+        </ResponseField>
+        <ResponseField name="amount" type="object" required>
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A stringified amount of an asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="source_account" type="string">
+
+The account being debited in the Stellar Network.
+
+</ResponseField>
+
+<ResponseField name="destination_account" type="string">
+
+The account being credited in the Stellar Network.
+
+</ResponseField>
+
+<ResponseField name="external_transaction_id" type="string">
+
+A unique transaction identifier.
+
+</ResponseField>
+
+<ResponseField name="memo" type="string"></ResponseField>
+
+<ResponseField name="memo_type" type="string">
+
+The memo type of the transaction in the Stellar network. Should be present if memo is not null.
+
+Available options: `id`, `hash`, `text`
+
+</ResponseField>
+
+<ResponseField name="refund_memo" type="string"></ResponseField>
+
+<ResponseField name="refund_memo_type" type="string">
+
+The memo type of the transaction in the Stellar network. Should be present if memo is not null.
+
+Available options: `id`, `hash`, `text`
+
+</ResponseField>
+
+<ResponseField name="client_domain" type="string">
+
+The domain of the client.
+
+</ResponseField>
+
+<ResponseField name="request_client_ip_address" type="string">
+
+The IP address of the client requesting the transaction.
+
+</ResponseField>
+
+<ResponseField name="customers" type="object">
+
+The Identification info of the sending and receiving customers. If they were created through [SEP-12](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md), this object should contain the SEP-12 customer `id`. Otherwise, the `account` address of the customer.
+
+  <Expandable title="properties">
+    <ResponseField name="sender" type="object">
+
+      A object that identify end-user.
+      For a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.
+      For a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.
+      For a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.
+
+      <Expandable title="properties">
+        <ResponseField name="id" type="string">
+
+          The `id` of the customer registered through SEP-12.
+
+        </ResponseField>
+        <ResponseField name="account" type="string">
+
+          Either the Stellar account or Muxed account address of the on-chain entity.
+
+        </ResponseField>
+        <ResponseField name="memo" type="string">
+
+          The memo value identifying a customer with a shared account, where the shared account is `account`.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="receiver" type="object">
+
+      A object that identify end-user.
+      For a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.
+      For a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.
+      For a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.
+
+      <Expandable title="properties">
+        <ResponseField name="id" type="string">
+
+          The `id` of the customer registered through SEP-12.
+
+        </ResponseField>
+        <ResponseField name="account" type="string">
+
+          Either the Stellar account or Muxed account address of the on-chain entity.
+
+        </ResponseField>
+        <ResponseField name="memo" type="string">
+
+          The memo value identifying a customer with a shared account, where the shared account is `account`.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="creator" type="object">
+
+A object that identify end-user. For a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend. For a SEP-31 Sending Anchor, the `account` and `memo` fields should be used. For a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.
+
+  <Expandable title="properties">
+    <ResponseField name="id" type="string">
+
+      The `id` of the customer registered through SEP-12.
+
+    </ResponseField>
+    <ResponseField name="account" type="string">
+
+      Either the Stellar account or Muxed account address of the on-chain entity.
+
+    </ResponseField>
+    <ResponseField name="memo" type="string">
+
+      The memo value identifying a customer with a shared account, where the shared account is `account`.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+## Example
+
+Example request to the `get_transaction` method.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "get_transaction",
+  "params": {
+    "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
+  }
+}' \
+https://platform-server.exampleanchor.com | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "get_transaction",
+  params: {
+    id: "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+  },
+};
+let res = await fetch("https://platform-server.exampleanchor.com", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://platform-server.exampleanchor.com", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "get_transaction",
+    "params": {
+        "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "get_transaction",
+  "params": {
+    "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "sep": "31",
+    "kind": "receive",
+    "status": "completed",
+    "funding_method": "SWIFT",
+    "amount_expected": {
+      "amount": "100",
+      "asset": "iso4217:USD"
+    },
+    "amount_in": {
+      "amount": "100.0000",
+      "asset": "iso4217:USD"
+    },
+    "amount_out": {
+      "amount": "98.0000000",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "fee_details": {
+      "total": "2.0000",
+      "asset": "iso4217:USD"
+    },
+    "quote_id": "quote-id",
+    "message": "Please don't forget to foo bar",
+    "refunds": {
+      "amount_refunded": {
+        "amount": "90.0000",
+        "asset": "iso4217:USD"
+      },
+      "amount_fee": {
+        "amount": "8.0000",
+        "asset": "iso4217:USD"
+      },
+      "payments": [
+        {
+          "id": "1111",
+          "id_type": "stellar",
+          "amount": {
+            "amount": "50.0000",
+            "asset": "iso4217:USD"
+          },
+          "fee": {
+            "amount": "4.0000",
+            "asset": "iso4217:USD"
+          }
+        },
+        {
+          "id": "2222",
+          "id_type": "stellar",
+          "amount": {
+            "amount": "40.0000",
+            "asset": "iso4217:USD"
+          },
+          "fee": {
+            "amount": "4.0000",
+            "asset": "iso4217:USD"
+          }
+        }
+      ]
+    },
+    "stellar_transactions": [
+      {
+        "id": "stellar-tx-id",
+        "memo": "my-memo",
+        "memo_type": "text",
+        "envelope": "here_comes_the_envelope",
+        "payments": [
+          {
+            "id": "payment-id",
+            "amount": {
+              "amount": "100.0000",
+              "asset": "iso4217:USD"
+            },
+            "payment_type": "payment",
+            "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
+            "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
+          }
+        ]
+      }
+    ],
+    "external_transaction_id": "external-tx-id",
+    "customers": {
+      "sender": {
+        "id": "sender-id"
+      },
+      "receiver": {
+        "id": "receiver-id"
+      }
+    },
+    "creator": {
+      "id": "creator-id"
+    }
+  }
+}
+```
+
+{/* /rpc-method */}
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transactions.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transactions.mdx
index ccf6db438..4f5904049 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transactions.mdx
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transactions.mdx
@@ -1,11 +1,703 @@
 ---
 title: get_transactions
-hide_title: true
+description: "<RpcMethod"
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "get_transactions")[0]}
-/>
+`SEP-6` `SEP-24` `SEP-31`
+
+Query a list of transactions by SEP, transaction status or other criteria.
+
+## Params (5)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="sep" type="integer" required>
+
+Sep of the transaction belongs to
+
+Protocol of the transaction.
+
+Available options: `6`, `24`, `31`
+
+</ParamField>
+
+<ParamField body="order_by" type="string">
+
+Specifies field that transactions will be ordered by. Note, that secondary sort is transaction id in ascending value.
+
+The order by string used to sort the results.
+
+Available options: `created_at`, `transfer_received_at`, `user_action_required_by`
+
+Default: `"created_at"`
+
+</ParamField>
+
+<ParamField body="statuses" type="array">
+
+The statuses of the transaction to filter by.
+
+Available options: `incomplete`, `completed`, `refunded`, `expired`, `error`, `pending_stellar`, `pending_external`, `pending_user_transfer_start`, `pending_user_transfer_complete`, `pending_anchor`, `pending_trust`, `pending_user`, `no_market`, `too_small`, `too_large`, `pending_sender`, `pending_receiver`, `pending_transaction_info_update`, `pending_customer_info_update`
+
+</ParamField>
+
+<ParamField body="page_size" type="integer">
+
+The number of records to return in each page.
+
+Default: `20`
+
+</ParamField>
+
+<ParamField body="page_number" type="integer">
+
+Page number to use for continuous search. Page count beings at 0.
+
+Default: `0`
+
+</ParamField>
+
+## Result
+
+_(get_transactionResponse)_
+
+<ResponseField name="records" type="object[]">
+  <Expandable title="items">
+    <ResponseField name="id" type="string">
+
+      A unique transaction identifier.
+
+    </ResponseField>
+    <ResponseField name="sep" type="integer">
+
+      Protocol of the transaction.
+
+      Available options: `6`, `24`, `31`
+
+    </ResponseField>
+    <ResponseField name="kind" type="string">
+
+      The kind of transaction that is desired.
+
+      Available options: `undefined`, `receive`, `deposit`, `deposit-exchange`, `withdrawal`, `withdrawal-exchange`
+
+    </ResponseField>
+    <ResponseField name="status" type="string">
+
+      Processing status of the transaction.
+
+      Available options: `pending_anchor`, `pending_trust`, `pending_user`, `pending_user_transfer_start`, `pending_user_transfer_complete`, `incomplete`, `no_market`, `too_small`, `too_large`, `pending_sender`, `pending_receiver`, `pending_transaction_info_update`, `pending_customer_info_update`, `completed`, `refunded`, `expired`, `error`, `pending_external`, `pending_stellar`
+
+    </ResponseField>
+    <ResponseField name="funding_method" type="string">
+
+      Funding method used for transferring or settling assets.
+
+    </ResponseField>
+    <ResponseField name="type" type="string">
+
+      DEPRECATED in favor of funding_method. Type of deposit, withdrawal or receive.
+
+    </ResponseField>
+    <ResponseField name="amount_expected" type="object">
+
+      The amount expected in the payment.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A stringified amount of an asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="amount_in" type="object">
+
+      Amount expected/received by anchor.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A stringified amount of an asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="amount_out" type="object">
+
+      The amount expected to be sent by anchor to user at end of transaction.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A stringified amount of an asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="fee_details" type="object">
+
+      Description of fee charged by the anchor.
+
+      <Expandable title="properties">
+        <ResponseField name="total" type="number" required>
+        </ResponseField>
+        <ResponseField name="asset" type="string" required>
+        </ResponseField>
+        <ResponseField name="details" type="object[]">
+
+          Details about fee charged.
+
+          <Expandable title="items">
+            <ResponseField name="name" type="string">
+            </ResponseField>
+            <ResponseField name="description" type="string">
+            </ResponseField>
+            <ResponseField name="amount" type="number">
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="quote_id" type="string">
+
+      The id returned from a SEP-38 POST /quote response
+
+    </ResponseField>
+    <ResponseField name="started_at" type="string">
+
+      Start date and time of transaction.
+
+    </ResponseField>
+    <ResponseField name="updated_at" type="string">
+
+      The date and time of transaction reaching the current status.
+
+    </ResponseField>
+    <ResponseField name="completed_at" type="string">
+
+      The date and time of transaction reaching completed or refunded status.
+
+    </ResponseField>
+    <ResponseField name="transfer_received_at" type="string">
+
+      The date and time of receiving transfer.
+
+    </ResponseField>
+    <ResponseField name="user_action_required_by" type="string">
+
+      Time and date by which user action is required.
+
+    </ResponseField>
+    <ResponseField name="message" type="string">
+
+      Human readable explanation of transaction status
+
+    </ResponseField>
+    <ResponseField name="refunds" type="object">
+
+      An object describing any on or offchain refund associated with this transaction.
+
+      <Expandable title="properties">
+        <ResponseField name="amount_refunded" type="object">
+
+          The total amount refunded in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="amount_fee" type="object">
+
+          The total amount charged in fees for processing all refund payments, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="payments" type="object[]">
+
+          A list of objects containing information on the individual payments made back as refunds.
+
+          <Expandable title="items">
+            <ResponseField name="id" type="string">
+
+              The Stellar transaction hash.
+
+            </ResponseField>
+            <ResponseField name="id_type" type="string">
+            </ResponseField>
+            <ResponseField name="amount" type="object">
+
+              The amount sent back for the payment identified by id, in units of amount_in_asset.
+
+              <Expandable title="properties">
+                <ResponseField name="amount" type="string">
+
+                  A numerical representation of an amount of some asset.
+
+                </ResponseField>
+                <ResponseField name="asset" type="string">
+
+                  An asset.
+
+                </ResponseField>
+              </Expandable>
+            </ResponseField>
+            <ResponseField name="fee" type="object">
+
+              The amount charged as a fee for processing the refund, in units of amount_in_asset.
+
+              <Expandable title="properties">
+                <ResponseField name="amount" type="string">
+
+                  A numerical representation of an amount of some asset.
+
+                </ResponseField>
+                <ResponseField name="asset" type="string">
+
+                  An asset.
+
+                </ResponseField>
+              </Expandable>
+            </ResponseField>
+            <ResponseField name="requested_at" type="string">
+
+              The date and time of requesting refund.
+
+            </ResponseField>
+            <ResponseField name="refunded_at" type="string">
+
+              The date and time of making refund.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="stellar_transactions" type="object[]">
+      <Expandable title="items">
+        <ResponseField name="id" type="string" required>
+
+          The Stellar transaction hash.
+
+        </ResponseField>
+        <ResponseField name="memo" type="string">
+        </ResponseField>
+        <ResponseField name="memo_type" type="string">
+
+          The memo type of the transaction in the Stellar network. Should be present if memo is not null.
+
+          Available options: `id`, `hash`, `text`
+
+        </ResponseField>
+        <ResponseField name="created_at" type="string" required>
+
+          The date and time when the transaction is created.
+
+        </ResponseField>
+        <ResponseField name="envelop" type="string">
+
+          The transaction envelope, containing all the transaction information.
+
+        </ResponseField>
+        <ResponseField name="payments" type="object[]" required>
+          <Expandable title="items">
+            <ResponseField name="id" type="string" required>
+
+               The ID of the payment in the Stellar Network.
+
+            </ResponseField>
+            <ResponseField name="payment_type" type="string" required>
+
+               The ID of the payment in the Stellar Network.
+
+              Available options: `payment`, `path_payment`
+
+              Default: `"payment"`
+
+            </ResponseField>
+            <ResponseField name="source_account" type="string" required>
+
+              The account being debited in the Stellar Network.
+
+            </ResponseField>
+            <ResponseField name="destination_account" type="string" required>
+
+              The account being credited in the Stellar Network.
+
+            </ResponseField>
+            <ResponseField name="amount" type="object" required>
+              <Expandable title="properties">
+                <ResponseField name="amount" type="string">
+
+                  A stringified amount of an asset.
+
+                </ResponseField>
+                <ResponseField name="asset" type="string">
+
+                  An asset.
+
+                </ResponseField>
+              </Expandable>
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="source_account" type="string">
+
+      The account being debited in the Stellar Network.
+
+    </ResponseField>
+    <ResponseField name="destination_account" type="string">
+
+      The account being credited in the Stellar Network.
+
+    </ResponseField>
+    <ResponseField name="external_transaction_id" type="string">
+
+      A unique transaction identifier.
+
+    </ResponseField>
+    <ResponseField name="memo" type="string">
+    </ResponseField>
+    <ResponseField name="memo_type" type="string">
+
+      The memo type of the transaction in the Stellar network. Should be present if memo is not null.
+
+      Available options: `id`, `hash`, `text`
+
+    </ResponseField>
+    <ResponseField name="refund_memo" type="string">
+    </ResponseField>
+    <ResponseField name="refund_memo_type" type="string">
+
+      The memo type of the transaction in the Stellar network. Should be present if memo is not null.
+
+      Available options: `id`, `hash`, `text`
+
+    </ResponseField>
+    <ResponseField name="client_domain" type="string">
+
+      The domain of the client.
+
+    </ResponseField>
+    <ResponseField name="request_client_ip_address" type="string">
+
+      The IP address of the client requesting the transaction.
+
+    </ResponseField>
+    <ResponseField name="customers" type="object">
+
+      The Identification info of the sending and receiving customers. If they were created through [SEP-12](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md),
+                  this object should contain the SEP-12 customer `id`. Otherwise, the `account` address of the customer.
+
+      <Expandable title="properties">
+        <ResponseField name="sender" type="object">
+
+          A object that identify end-user.
+          For a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.
+          For a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.
+          For a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.
+
+          <Expandable title="properties">
+            <ResponseField name="id" type="string">
+
+              The `id` of the customer registered through SEP-12.
+
+            </ResponseField>
+            <ResponseField name="account" type="string">
+
+              Either the Stellar account or Muxed account address of the on-chain entity.
+
+            </ResponseField>
+            <ResponseField name="memo" type="string">
+
+              The memo value identifying a customer with a shared account, where the shared account is `account`.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="receiver" type="object">
+
+          A object that identify end-user.
+          For a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.
+          For a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.
+          For a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.
+
+          <Expandable title="properties">
+            <ResponseField name="id" type="string">
+
+              The `id` of the customer registered through SEP-12.
+
+            </ResponseField>
+            <ResponseField name="account" type="string">
+
+              Either the Stellar account or Muxed account address of the on-chain entity.
+
+            </ResponseField>
+            <ResponseField name="memo" type="string">
+
+              The memo value identifying a customer with a shared account, where the shared account is `account`.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="creator" type="object">
+
+      A object that identify end-user.
+      For a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.
+      For a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.
+      For a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.
+
+      <Expandable title="properties">
+        <ResponseField name="id" type="string">
+
+          The `id` of the customer registered through SEP-12.
+
+        </ResponseField>
+        <ResponseField name="account" type="string">
+
+          Either the Stellar account or Muxed account address of the on-chain entity.
+
+        </ResponseField>
+        <ResponseField name="memo" type="string">
+
+          The memo value identifying a customer with a shared account, where the shared account is `account`.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+## Example
+
+Example request to the `get_transactions` method.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "get_transactions",
+  "params": {
+    "sep": "31",
+    "order_by": "created_at",
+    "statuses": [
+      "completed"
+    ]
+  }
+}' \
+https://platform-server.exampleanchor.com | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "get_transactions",
+  params: {
+    sep: "31",
+    order_by: "created_at",
+    statuses: ["completed"],
+  },
+};
+let res = await fetch("https://platform-server.exampleanchor.com", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://platform-server.exampleanchor.com", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "get_transactions",
+    "params": {
+        "sep": "31",
+        "order_by": "created_at",
+        "statuses": [
+            "completed"
+        ]
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "get_transactions",
+  "params": {
+    "sep": "31",
+    "order_by": "created_at",
+    "statuses": ["completed"]
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "records": [
+      {
+        "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+        "sep": "31",
+        "kind": "receive",
+        "status": "completed",
+        "funding_method": "SWIFT",
+        "amount_expected": {
+          "amount": "100",
+          "asset": "iso4217:USD"
+        },
+        "amount_in": {
+          "amount": "100.0000",
+          "asset": "iso4217:USD"
+        },
+        "amount_out": {
+          "amount": "98.0000000",
+          "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+        },
+        "fee_details": {
+          "total": "2.0000",
+          "asset": "iso4217:USD"
+        },
+        "quote_id": "quote-id",
+        "message": "Please don't forget to foo bar",
+        "refunds": {
+          "amount_refunded": {
+            "amount": "90.0000",
+            "asset": "iso4217:USD"
+          },
+          "amount_fee": {
+            "amount": "8.0000",
+            "asset": "iso4217:USD"
+          },
+          "payments": [
+            {
+              "id": "1111",
+              "id_type": "stellar",
+              "amount": {
+                "amount": "50.0000",
+                "asset": "iso4217:USD"
+              },
+              "fee": {
+                "amount": "4.0000",
+                "asset": "iso4217:USD"
+              }
+            },
+            {
+              "id": "2222",
+              "id_type": "stellar",
+              "amount": {
+                "amount": "40.0000",
+                "asset": "iso4217:USD"
+              },
+              "fee": {
+                "amount": "4.0000",
+                "asset": "iso4217:USD"
+              }
+            }
+          ]
+        },
+        "stellar_transactions": [
+          {
+            "id": "stellar-tx-id",
+            "memo": "my-memo",
+            "memo_type": "text",
+            "envelope": "here_comes_the_envelope",
+            "payments": [
+              {
+                "id": "payment-id",
+                "amount": {
+                  "amount": "100.0000",
+                  "asset": "iso4217:USD"
+                },
+                "payment_type": "payment",
+                "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
+                "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
+              }
+            ]
+          }
+        ],
+        "external_transaction_id": "external-tx-id",
+        "customers": {
+          "sender": {
+            "id": "sender-id"
+          },
+          "receiver": {
+            "id": "receiver-id"
+          }
+        },
+        "creator": {
+          "id": "creator-id"
+        }
+      }
+    ]
+  }
+}
+```
+
+{/* /rpc-method */}
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/index.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/index.mdx
new file mode 100644
index 000000000..959a855cb
--- /dev/null
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/index.mdx
@@ -0,0 +1,36 @@
+---
+title: JSON-RPC Methods
+sidebarTitle: Methods
+description: "This section lists the Anchor Platform JSON-RPC API methods that should be called by Stellar clients to update status of the transaction."
+order: 20
+---
+
+The OpenRPC Specification for JSON-RPC API is available [here](https://playground.open-rpc.org/?schemaUrl=https://developers.stellar.org/docs/platforms/anchor-platform/api-reference/platform/rpc/anchor-platform.openrpc.json).
+
+Postman collection is available [here](https://documenter.getpostman.com/view/9257637/2s9Y5U1kra)
+
+| JSON-RPC Methods |  |
+| --- | --- |
+|  | [do_stellar_payment](/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_payment) |
+|  | [do_stellar_refund](/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_refund) |
+|  | [get_transaction](/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transaction) |
+|  | [get_transactions](/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transactions) |
+|  | [notify_amounts_updated](/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_amounts_updated) |
+|  | [notify_customer_info_updated](/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_customer_info_updated) |
+|  | [notify_interactive_flow_completed](/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_interactive_flow_completed) |
+|  | [notify_offchain_funds_available](/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_available) |
+|  | [notify_offchain_funds_pending](/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_pending) |
+|  | [notify_offchain_funds_received](/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_received) |
+|  | [notify_offchain_funds_sent](/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_sent) |
+|  | [notify_onchain_funds_received](/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_received) |
+|  | [notify_onchain_funds_sent](/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_sent) |
+|  | [notify_refund_pending](/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_pending) |
+|  | [notify_refund_sent](/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_sent) |
+|  | [notify_transaction_error](/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_error) |
+|  | [notify_transaction_expired](/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_expired) |
+|  | [notify_transaction_on_hold](/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_on_hold) |
+|  | [notify_transaction_recovery](/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_recovery) |
+|  | [notify_trust_set](/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_trust_set) |
+|  | [request_offchain_funds](/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_offchain_funds) |
+|  | [request_onchain_funds](/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_onchain_funds) |
+|  | [request_trust](/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_trust) |
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_amounts_updated.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_amounts_updated.mdx
index 8daed8f44..270289f22 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_amounts_updated.mdx
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_amounts_updated.mdx
@@ -1,13 +1,474 @@
 ---
 title: notify_amounts_updated
-hide_title: true
+description: "<RpcMethod"
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={
-    rpcSpec.methods.filter((meth) => meth.name === "notify_amounts_updated")[0]
+`SEP-6` `SEP-24`
+
+Update amount_out and fee_details values
+
+## Params (4)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="transaction_id" type="string" required>
+
+The unique identifier of this transaction.
+
+A unique transaction identifier.
+
+</ParamField>
+
+<ParamField body="message" type="string">
+
+Human readable explanation of transaction status.
+
+A human readable message.
+
+</ParamField>
+
+<ParamField body="amount_out" type="object" required>
+
+Amount sent by anchor to user
+
+  <Expandable title="properties">
+    <ParamField body="amount" type="string" required>
+
+      A numerical representation of an amount of some asset.
+
+    </ParamField>
+    <ParamField body="asset" type="string" required>
+
+      The asset to be sent by anchor to user at end of transaction
+
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+<ParamField body="fee_details" type="object" required>
+
+Description of fees charged by the anchor
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ParamField body="total" type="number" required>
+    </ParamField>
+    <ParamField body="asset" type="string" required>
+    </ParamField>
+    <ParamField body="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ParamField body="name" type="string">
+        </ParamField>
+        <ParamField body="description" type="string">
+        </ParamField>
+        <ParamField body="amount" type="number">
+        </ParamField>
+      </Expandable>
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+## Result
+
+_(notify_amounts_updatedResponse)_
+
+<ResponseField name="id" type="string">
+
+A unique transaction identifier.
+
+</ResponseField>
+
+<ResponseField name="sep" type="integer">
+
+Protocol of the transaction.
+
+Available options: `6`, `24`, `31`
+
+</ResponseField>
+
+<ResponseField name="kind" type="string">
+
+The kind of transaction that is desired.
+
+Available options: `undefined`, `receive`, `deposit`, `deposit-exchange`, `withdrawal`, `withdrawal-exchange`
+
+</ResponseField>
+
+<ResponseField name="status" type="string">
+
+Processing status of the transaction.
+
+Available options: `pending_anchor`, `pending_trust`, `pending_user`, `pending_user_transfer_start`, `pending_user_transfer_complete`, `incomplete`, `no_market`, `too_small`, `too_large`, `pending_sender`, `pending_receiver`, `pending_transaction_info_update`, `pending_customer_info_update`, `completed`, `refunded`, `expired`, `error`, `pending_external`, `pending_stellar`
+
+</ResponseField>
+
+<ResponseField name="amount_expected" type="object">
+
+The amount expected in the payment.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_in" type="object">
+
+Amount expected/received by anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_out" type="object">
+
+The amount expected to be sent by anchor to user at end of transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="fee_details" type="object">
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="total" type="number" required>
+    </ResponseField>
+    <ResponseField name="asset" type="string" required>
+    </ResponseField>
+    <ResponseField name="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ResponseField name="name" type="string">
+        </ResponseField>
+        <ResponseField name="description" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="number">
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="quote_id" type="string">
+
+The id returned from a SEP-38 POST /quote response
+
+</ResponseField>
+
+<ResponseField name="started_at" type="string">
+
+Start date and time of transaction.
+
+</ResponseField>
+
+<ResponseField name="updated_at" type="string">
+
+The date and time of transaction reaching the current status.
+
+</ResponseField>
+
+<ResponseField name="completed_at" type="string">
+
+The date and time of transaction reaching completed or refunded status.
+
+</ResponseField>
+
+<ResponseField name="transfer_received_at" type="string">
+
+The date and time of receiving transfer.
+
+</ResponseField>
+
+<ResponseField name="message" type="string">
+
+Human readable explanation of transaction status
+
+</ResponseField>
+
+<ResponseField name="refunds" type="object">
+
+An object describing any on or offchain refund associated with this transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount_refunded" type="object">
+
+      The total amount refunded in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="amount_fee" type="object">
+
+      The total amount charged in fees for processing all refund payments, in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="payments" type="object[]">
+
+      A list of objects containing information on the individual payments made back as refunds.
+
+      <Expandable title="items">
+        <ResponseField name="id" type="string">
+
+          The Stellar transaction hash.
+
+        </ResponseField>
+        <ResponseField name="id_type" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="object">
+
+          The amount sent back for the payment identified by id, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="fee" type="object">
+
+          The amount charged as a fee for processing the refund, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="requested_at" type="string">
+
+          The date and time of requesting refund.
+
+        </ResponseField>
+        <ResponseField name="refunded_at" type="string">
+
+          The date and time of making refund.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+## Example
+
+Example request to the `notify_amounts_updated` method.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_amounts_updated",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Amounts updated",
+    "amount_out": {
+      "amount": 1
+    },
+    "fee_details": {
+      "total": 0.1,
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    }
   }
-/>
+}' \
+https://platform-server.exampleanchor.com | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "notify_amounts_updated",
+  params: {
+    transaction_id: "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    message: "Amounts updated",
+    amount_out: {
+      amount: 1,
+    },
+    fee_details: {
+      total: 0.1,
+      asset:
+        "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5",
+    },
+  },
+};
+let res = await fetch("https://platform-server.exampleanchor.com", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://platform-server.exampleanchor.com", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "notify_amounts_updated",
+    "params": {
+        "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+        "message": "Amounts updated",
+        "amount_out": {
+            "amount": 1
+        },
+        "fee_details": {
+            "total": 0.1,
+            "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+        }
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_amounts_updated",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Amounts updated",
+    "amount_out": {
+      "amount": 1
+    },
+    "fee_details": {
+      "total": 0.1,
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    }
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "sep": "24",
+    "kind": "deposit",
+    "status": "completed",
+    "amount_expected": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_in": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_out": {
+      "amount": "0.9",
+      "asset": "iso4217:USD"
+    },
+    "fee_details": {
+      "total": "0.1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "started_at": "2023-08-04T10:04:06.280923Z",
+    "updated_at": "2023-08-04T10:04:15.716233Z",
+    "message": "Transaction complete",
+    "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
+    "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
+  }
+}
+```
+
+{/* /rpc-method */}
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_customer_info_updated.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_customer_info_updated.mdx
index ffc4795d8..7c8194571 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_customer_info_updated.mdx
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_customer_info_updated.mdx
@@ -1,15 +1,418 @@
 ---
 title: notify_customer_info_updated
-hide_title: true
+description: "<RpcMethod"
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notify_customer_info_updated",
-    )[0]
+`SEP-6` `SEP-31`
+
+The customer's status for the transaction has been updated. Use this method to notify the wallet of the status change. If `customer_id` and `customer_type` are provided, the transaction status will reflect the customer's status. If not, the transaction status will default to the standard pending status for the SEP.
+
+## Params (4)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="transaction_id" type="string" required>
+
+The unique identifier of this transaction.
+
+A unique transaction identifier.
+
+</ParamField>
+
+<ParamField body="message" type="string">
+
+Human readable explanation of transaction status.
+
+A human readable message.
+
+</ParamField>
+
+<ParamField body="customer_id" type="string">
+
+The SEP-12 ID of the customer
+
+</ParamField>
+
+<ParamField body="customer_type" type="string">
+
+The SEP-12 type of the customer
+
+</ParamField>
+
+## Result
+
+_(notify_customer_info_updatedResponse)_
+
+<ResponseField name="id" type="string">
+
+A unique transaction identifier.
+
+</ResponseField>
+
+<ResponseField name="sep" type="integer">
+
+Protocol of the transaction.
+
+Available options: `6`, `24`, `31`
+
+</ResponseField>
+
+<ResponseField name="kind" type="string">
+
+The kind of transaction that is desired.
+
+Available options: `undefined`, `receive`, `deposit`, `deposit-exchange`, `withdrawal`, `withdrawal-exchange`
+
+</ResponseField>
+
+<ResponseField name="status" type="string">
+
+Processing status of the transaction.
+
+Available options: `pending_anchor`, `pending_trust`, `pending_user`, `pending_user_transfer_start`, `pending_user_transfer_complete`, `incomplete`, `no_market`, `too_small`, `too_large`, `pending_sender`, `pending_receiver`, `pending_transaction_info_update`, `pending_customer_info_update`, `completed`, `refunded`, `expired`, `error`, `pending_external`, `pending_stellar`
+
+</ResponseField>
+
+<ResponseField name="amount_expected" type="object">
+
+The amount expected in the payment.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_in" type="object">
+
+Amount expected/received by anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_out" type="object">
+
+The amount expected to be sent by anchor to user at end of transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="fee_details" type="object">
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="total" type="number" required>
+    </ResponseField>
+    <ResponseField name="asset" type="string" required>
+    </ResponseField>
+    <ResponseField name="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ResponseField name="name" type="string">
+        </ResponseField>
+        <ResponseField name="description" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="number">
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="quote_id" type="string">
+
+The id returned from a SEP-38 POST /quote response
+
+</ResponseField>
+
+<ResponseField name="started_at" type="string">
+
+Start date and time of transaction.
+
+</ResponseField>
+
+<ResponseField name="updated_at" type="string">
+
+The date and time of transaction reaching the current status.
+
+</ResponseField>
+
+<ResponseField name="completed_at" type="string">
+
+The date and time of transaction reaching completed or refunded status.
+
+</ResponseField>
+
+<ResponseField name="transfer_received_at" type="string">
+
+The date and time of receiving transfer.
+
+</ResponseField>
+
+<ResponseField name="message" type="string">
+
+Human readable explanation of transaction status
+
+</ResponseField>
+
+<ResponseField name="refunds" type="object">
+
+An object describing any on or offchain refund associated with this transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount_refunded" type="object">
+
+      The total amount refunded in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="amount_fee" type="object">
+
+      The total amount charged in fees for processing all refund payments, in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="payments" type="object[]">
+
+      A list of objects containing information on the individual payments made back as refunds.
+
+      <Expandable title="items">
+        <ResponseField name="id" type="string">
+
+          The Stellar transaction hash.
+
+        </ResponseField>
+        <ResponseField name="id_type" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="object">
+
+          The amount sent back for the payment identified by id, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="fee" type="object">
+
+          The amount charged as a fee for processing the refund, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="requested_at" type="string">
+
+          The date and time of requesting refund.
+
+        </ResponseField>
+        <ResponseField name="refunded_at" type="string">
+
+          The date and time of making refund.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+## Example
+
+Example request to the `notify_customer_info_updated` method.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_customer_info_updated",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Customer info updated",
+    "customer_id": "45f8884d-d6e1-477f-a680-503179263359",
+    "customer_type": "sep31-receiver"
+  }
+}' \
+https://platform-server.exampleanchor.com | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "notify_customer_info_updated",
+  params: {
+    transaction_id: "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    message: "Customer info updated",
+    customer_id: "45f8884d-d6e1-477f-a680-503179263359",
+    customer_type: "sep31-receiver",
+  },
+};
+let res = await fetch("https://platform-server.exampleanchor.com", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://platform-server.exampleanchor.com", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "notify_customer_info_updated",
+    "params": {
+        "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+        "message": "Customer info updated",
+        "customer_id": "45f8884d-d6e1-477f-a680-503179263359",
+        "customer_type": "sep31-receiver"
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_customer_info_updated",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Customer info updated",
+    "customer_id": "45f8884d-d6e1-477f-a680-503179263359",
+    "customer_type": "sep31-receiver"
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "sep": "24",
+    "kind": "deposit",
+    "status": "completed",
+    "amount_expected": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_in": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_out": {
+      "amount": "0.9",
+      "asset": "iso4217:USD"
+    },
+    "fee_details": {
+      "total": "0.1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "started_at": "2023-08-04T10:04:06.280923Z",
+    "updated_at": "2023-08-04T10:04:15.716233Z",
+    "message": "Transaction complete",
+    "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
+    "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
   }
-/>
+}
+```
+
+{/* /rpc-method */}
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_interactive_flow_completed.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_interactive_flow_completed.mdx
index 55ba759ec..77666553d 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_interactive_flow_completed.mdx
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_interactive_flow_completed.mdx
@@ -1,15 +1,547 @@
 ---
 title: notify_interactive_flow_completed
-hide_title: true
+description: "<RpcMethod"
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notify_interactive_flow_completed",
-    )[0]
+`SEP-24`
+
+Platform has collected the transaction amounts and fees from the business
+
+## Params (7)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="transaction_id" type="string" required>
+
+The unique identifier of this transaction.
+
+A unique transaction identifier.
+
+</ParamField>
+
+<ParamField body="message" type="string">
+
+Human readable explanation of transaction status.
+
+A human readable message.
+
+</ParamField>
+
+<ParamField body="amount_in" type="object" required>
+
+The amount expected in the payment
+
+  <Expandable title="properties">
+    <ParamField body="amount" type="string" required>
+
+      A numerical representation of an amount of some asset.
+
+    </ParamField>
+    <ParamField body="asset" type="string" required>
+
+      The asset to be received by the Anchor
+
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+<ParamField body="amount_out" type="object" required>
+
+Amount sent by anchor to user
+
+  <Expandable title="properties">
+    <ParamField body="amount" type="string" required>
+
+      A numerical representation of an amount of some asset.
+
+    </ParamField>
+    <ParamField body="asset" type="string" required>
+
+      The asset to be sent by anchor to user at end of transaction
+
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+<ParamField body="fee_details" type="object" required>
+
+Description of fees charged by the anchor
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ParamField body="total" type="number" required>
+    </ParamField>
+    <ParamField body="asset" type="string" required>
+    </ParamField>
+    <ParamField body="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ParamField body="name" type="string">
+        </ParamField>
+        <ParamField body="description" type="string">
+        </ParamField>
+        <ParamField body="amount" type="number">
+        </ParamField>
+      </Expandable>
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+<ParamField body="amount_expected" type="object">
+
+The amount expected in the payment
+
+  <Expandable title="properties">
+    <ParamField body="amount" type="string" required>
+
+      A numerical representation of an amount of some asset.
+
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+<ParamField body="user_action_required_by" type="string">
+
+Time and date by which user action is required
+
+A date and time.
+
+</ParamField>
+
+## Result
+
+_(notify_interactive_flow_completedResponse)_
+
+<ResponseField name="id" type="string">
+
+A unique transaction identifier.
+
+</ResponseField>
+
+<ResponseField name="sep" type="integer">
+
+Protocol of the transaction.
+
+Available options: `6`, `24`, `31`
+
+</ResponseField>
+
+<ResponseField name="kind" type="string">
+
+The kind of transaction that is desired.
+
+Available options: `undefined`, `receive`, `deposit`, `deposit-exchange`, `withdrawal`, `withdrawal-exchange`
+
+</ResponseField>
+
+<ResponseField name="status" type="string">
+
+Processing status of the transaction.
+
+Available options: `pending_anchor`, `pending_trust`, `pending_user`, `pending_user_transfer_start`, `pending_user_transfer_complete`, `incomplete`, `no_market`, `too_small`, `too_large`, `pending_sender`, `pending_receiver`, `pending_transaction_info_update`, `pending_customer_info_update`, `completed`, `refunded`, `expired`, `error`, `pending_external`, `pending_stellar`
+
+</ResponseField>
+
+<ResponseField name="amount_expected" type="object">
+
+The amount expected in the payment.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_in" type="object">
+
+Amount expected/received by anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_out" type="object">
+
+The amount expected to be sent by anchor to user at end of transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="fee_details" type="object">
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="total" type="number" required>
+    </ResponseField>
+    <ResponseField name="asset" type="string" required>
+    </ResponseField>
+    <ResponseField name="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ResponseField name="name" type="string">
+        </ResponseField>
+        <ResponseField name="description" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="number">
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="quote_id" type="string">
+
+The id returned from a SEP-38 POST /quote response
+
+</ResponseField>
+
+<ResponseField name="started_at" type="string">
+
+Start date and time of transaction.
+
+</ResponseField>
+
+<ResponseField name="updated_at" type="string">
+
+The date and time of transaction reaching the current status.
+
+</ResponseField>
+
+<ResponseField name="completed_at" type="string">
+
+The date and time of transaction reaching completed or refunded status.
+
+</ResponseField>
+
+<ResponseField name="transfer_received_at" type="string">
+
+The date and time of receiving transfer.
+
+</ResponseField>
+
+<ResponseField name="message" type="string">
+
+Human readable explanation of transaction status
+
+</ResponseField>
+
+<ResponseField name="refunds" type="object">
+
+An object describing any on or offchain refund associated with this transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount_refunded" type="object">
+
+      The total amount refunded in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="amount_fee" type="object">
+
+      The total amount charged in fees for processing all refund payments, in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="payments" type="object[]">
+
+      A list of objects containing information on the individual payments made back as refunds.
+
+      <Expandable title="items">
+        <ResponseField name="id" type="string">
+
+          The Stellar transaction hash.
+
+        </ResponseField>
+        <ResponseField name="id_type" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="object">
+
+          The amount sent back for the payment identified by id, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="fee" type="object">
+
+          The amount charged as a fee for processing the refund, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="requested_at" type="string">
+
+          The date and time of requesting refund.
+
+        </ResponseField>
+        <ResponseField name="refunded_at" type="string">
+
+          The date and time of making refund.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+## Example
+
+Example request to the `notify_interactive_flow_completed` method.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_interactive_flow_completed",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Interactive flow completed successfully.",
+    "amount_in": {
+      "amount": 1,
+      "asset": "iso4217:USD"
+    },
+    "amount_out": {
+      "amount": 0.9,
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "fee_details": {
+      "total": 0.1,
+      "asset": "iso4217:USD"
+    },
+    "amount_expected": {
+      "amount": 1
+    }
+  }
+}' \
+https://platform-server.exampleanchor.com | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "notify_interactive_flow_completed",
+  params: {
+    transaction_id: "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    message: "Interactive flow completed successfully.",
+    amount_in: {
+      amount: 1,
+      asset: "iso4217:USD",
+    },
+    amount_out: {
+      amount: 0.9,
+      asset:
+        "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5",
+    },
+    fee_details: {
+      total: 0.1,
+      asset: "iso4217:USD",
+    },
+    amount_expected: {
+      amount: 1,
+    },
+  },
+};
+let res = await fetch("https://platform-server.exampleanchor.com", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://platform-server.exampleanchor.com", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "notify_interactive_flow_completed",
+    "params": {
+        "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+        "message": "Interactive flow completed successfully.",
+        "amount_in": {
+            "amount": 1,
+            "asset": "iso4217:USD"
+        },
+        "amount_out": {
+            "amount": 0.9,
+            "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+        },
+        "fee_details": {
+            "total": 0.1,
+            "asset": "iso4217:USD"
+        },
+        "amount_expected": {
+            "amount": 1
+        }
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_interactive_flow_completed",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Interactive flow completed successfully.",
+    "amount_in": {
+      "amount": 1,
+      "asset": "iso4217:USD"
+    },
+    "amount_out": {
+      "amount": 0.9,
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "fee_details": {
+      "total": 0.1,
+      "asset": "iso4217:USD"
+    },
+    "amount_expected": {
+      "amount": 1
+    }
   }
-/>
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "sep": "24",
+    "kind": "deposit",
+    "status": "completed",
+    "amount_expected": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_in": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_out": {
+      "amount": "0.9",
+      "asset": "iso4217:USD"
+    },
+    "fee_details": {
+      "total": "0.1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "started_at": "2023-08-04T10:04:06.280923Z",
+    "updated_at": "2023-08-04T10:04:15.716233Z",
+    "message": "Transaction complete",
+    "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
+    "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
+  }
+}
+```
+
+{/* /rpc-method */}
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_available.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_available.mdx
index 9bca880e3..e560d738f 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_available.mdx
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_available.mdx
@@ -1,15 +1,419 @@
 ---
 title: notify_offchain_funds_available
-hide_title: true
+description: "<RpcMethod"
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notify_offchain_funds_available",
-    )[0]
+`SEP-6` `SEP-24`
+
+Funds are ready for the user / recipient to pick up.
+
+## Params (4)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="transaction_id" type="string" required>
+
+The unique identifier of this transaction.
+
+A unique transaction identifier.
+
+</ParamField>
+
+<ParamField body="message" type="string">
+
+Human readable explanation of transaction status.
+
+A human readable message.
+
+</ParamField>
+
+<ParamField body="external_transaction_id" type="string">
+
+The unique identifier of this transaction on the external network.
+
+A unique transaction identifier.
+
+</ParamField>
+
+<ParamField body="user_action_required_by" type="string">
+
+Time and date by which user action is required
+
+A date and time.
+
+</ParamField>
+
+## Result
+
+_(notify_offchain_funds_availableResponse)_
+
+<ResponseField name="id" type="string">
+
+A unique transaction identifier.
+
+</ResponseField>
+
+<ResponseField name="sep" type="integer">
+
+Protocol of the transaction.
+
+Available options: `6`, `24`, `31`
+
+</ResponseField>
+
+<ResponseField name="kind" type="string">
+
+The kind of transaction that is desired.
+
+Available options: `undefined`, `receive`, `deposit`, `deposit-exchange`, `withdrawal`, `withdrawal-exchange`
+
+</ResponseField>
+
+<ResponseField name="status" type="string">
+
+Processing status of the transaction.
+
+Available options: `pending_anchor`, `pending_trust`, `pending_user`, `pending_user_transfer_start`, `pending_user_transfer_complete`, `incomplete`, `no_market`, `too_small`, `too_large`, `pending_sender`, `pending_receiver`, `pending_transaction_info_update`, `pending_customer_info_update`, `completed`, `refunded`, `expired`, `error`, `pending_external`, `pending_stellar`
+
+</ResponseField>
+
+<ResponseField name="amount_expected" type="object">
+
+The amount expected in the payment.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_in" type="object">
+
+Amount expected/received by anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_out" type="object">
+
+The amount expected to be sent by anchor to user at end of transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="fee_details" type="object">
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="total" type="number" required>
+    </ResponseField>
+    <ResponseField name="asset" type="string" required>
+    </ResponseField>
+    <ResponseField name="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ResponseField name="name" type="string">
+        </ResponseField>
+        <ResponseField name="description" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="number">
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="quote_id" type="string">
+
+The id returned from a SEP-38 POST /quote response
+
+</ResponseField>
+
+<ResponseField name="started_at" type="string">
+
+Start date and time of transaction.
+
+</ResponseField>
+
+<ResponseField name="updated_at" type="string">
+
+The date and time of transaction reaching the current status.
+
+</ResponseField>
+
+<ResponseField name="completed_at" type="string">
+
+The date and time of transaction reaching completed or refunded status.
+
+</ResponseField>
+
+<ResponseField name="transfer_received_at" type="string">
+
+The date and time of receiving transfer.
+
+</ResponseField>
+
+<ResponseField name="message" type="string">
+
+Human readable explanation of transaction status
+
+</ResponseField>
+
+<ResponseField name="refunds" type="object">
+
+An object describing any on or offchain refund associated with this transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount_refunded" type="object">
+
+      The total amount refunded in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="amount_fee" type="object">
+
+      The total amount charged in fees for processing all refund payments, in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="payments" type="object[]">
+
+      A list of objects containing information on the individual payments made back as refunds.
+
+      <Expandable title="items">
+        <ResponseField name="id" type="string">
+
+          The Stellar transaction hash.
+
+        </ResponseField>
+        <ResponseField name="id_type" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="object">
+
+          The amount sent back for the payment identified by id, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="fee" type="object">
+
+          The amount charged as a fee for processing the refund, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="requested_at" type="string">
+
+          The date and time of requesting refund.
+
+        </ResponseField>
+        <ResponseField name="refunded_at" type="string">
+
+          The date and time of making refund.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+## Example
+
+Example request to the `notify_offchain_funds_available` method.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_offchain_funds_available",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Offchain funds available",
+    "stellar_transaction_id": "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e"
   }
-/>
+}' \
+https://platform-server.exampleanchor.com | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "notify_offchain_funds_available",
+  params: {
+    transaction_id: "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    message: "Offchain funds available",
+    stellar_transaction_id:
+      "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e",
+  },
+};
+let res = await fetch("https://platform-server.exampleanchor.com", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://platform-server.exampleanchor.com", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "notify_offchain_funds_available",
+    "params": {
+        "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+        "message": "Offchain funds available",
+        "stellar_transaction_id": "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e"
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_offchain_funds_available",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Offchain funds available",
+    "stellar_transaction_id": "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e"
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "sep": "24",
+    "kind": "deposit",
+    "status": "completed",
+    "amount_expected": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_in": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_out": {
+      "amount": "0.9",
+      "asset": "iso4217:USD"
+    },
+    "fee_details": {
+      "total": "0.1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "started_at": "2023-08-04T10:04:06.280923Z",
+    "updated_at": "2023-08-04T10:04:15.716233Z",
+    "message": "Transaction complete",
+    "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
+    "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
+  }
+}
+```
+
+{/* /rpc-method */}
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_pending.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_pending.mdx
index a7573189c..77883d6d5 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_pending.mdx
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_pending.mdx
@@ -1,15 +1,419 @@
 ---
 title: notify_offchain_funds_pending
-hide_title: true
+description: "<RpcMethod"
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notify_offchain_funds_pending",
-    )[0]
+`SEP-6` `SEP-24` `SEP-31`
+
+Payment has been submitted to external network, but is not yet confirmed
+
+## Params (4)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="transaction_id" type="string" required>
+
+The unique identifier of this transaction.
+
+A unique transaction identifier.
+
+</ParamField>
+
+<ParamField body="message" type="string">
+
+Human readable explanation of transaction status.
+
+A human readable message.
+
+</ParamField>
+
+<ParamField body="external_transaction_id" type="string">
+
+The unique identifier of this transaction on the external network.
+
+A unique transaction identifier.
+
+</ParamField>
+
+<ParamField body="user_action_required_by" type="string">
+
+Time and date by which user action is required
+
+A date and time.
+
+</ParamField>
+
+## Result
+
+_(notify_offchain_funds_pendingResponse)_
+
+<ResponseField name="id" type="string">
+
+A unique transaction identifier.
+
+</ResponseField>
+
+<ResponseField name="sep" type="integer">
+
+Protocol of the transaction.
+
+Available options: `6`, `24`, `31`
+
+</ResponseField>
+
+<ResponseField name="kind" type="string">
+
+The kind of transaction that is desired.
+
+Available options: `undefined`, `receive`, `deposit`, `deposit-exchange`, `withdrawal`, `withdrawal-exchange`
+
+</ResponseField>
+
+<ResponseField name="status" type="string">
+
+Processing status of the transaction.
+
+Available options: `pending_anchor`, `pending_trust`, `pending_user`, `pending_user_transfer_start`, `pending_user_transfer_complete`, `incomplete`, `no_market`, `too_small`, `too_large`, `pending_sender`, `pending_receiver`, `pending_transaction_info_update`, `pending_customer_info_update`, `completed`, `refunded`, `expired`, `error`, `pending_external`, `pending_stellar`
+
+</ResponseField>
+
+<ResponseField name="amount_expected" type="object">
+
+The amount expected in the payment.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_in" type="object">
+
+Amount expected/received by anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_out" type="object">
+
+The amount expected to be sent by anchor to user at end of transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="fee_details" type="object">
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="total" type="number" required>
+    </ResponseField>
+    <ResponseField name="asset" type="string" required>
+    </ResponseField>
+    <ResponseField name="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ResponseField name="name" type="string">
+        </ResponseField>
+        <ResponseField name="description" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="number">
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="quote_id" type="string">
+
+The id returned from a SEP-38 POST /quote response
+
+</ResponseField>
+
+<ResponseField name="started_at" type="string">
+
+Start date and time of transaction.
+
+</ResponseField>
+
+<ResponseField name="updated_at" type="string">
+
+The date and time of transaction reaching the current status.
+
+</ResponseField>
+
+<ResponseField name="completed_at" type="string">
+
+The date and time of transaction reaching completed or refunded status.
+
+</ResponseField>
+
+<ResponseField name="transfer_received_at" type="string">
+
+The date and time of receiving transfer.
+
+</ResponseField>
+
+<ResponseField name="message" type="string">
+
+Human readable explanation of transaction status
+
+</ResponseField>
+
+<ResponseField name="refunds" type="object">
+
+An object describing any on or offchain refund associated with this transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount_refunded" type="object">
+
+      The total amount refunded in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="amount_fee" type="object">
+
+      The total amount charged in fees for processing all refund payments, in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="payments" type="object[]">
+
+      A list of objects containing information on the individual payments made back as refunds.
+
+      <Expandable title="items">
+        <ResponseField name="id" type="string">
+
+          The Stellar transaction hash.
+
+        </ResponseField>
+        <ResponseField name="id_type" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="object">
+
+          The amount sent back for the payment identified by id, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="fee" type="object">
+
+          The amount charged as a fee for processing the refund, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="requested_at" type="string">
+
+          The date and time of requesting refund.
+
+        </ResponseField>
+        <ResponseField name="refunded_at" type="string">
+
+          The date and time of making refund.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+## Example
+
+Example request to the `notify_offchain_funds_pending` method.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_offchain_funds_pending",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Offchain funds pending",
+    "external_transaction_id": "3320c6faad48c3cf39b6d4ac15ed50b6e5868b62551e69cde15df2d66c8ca360"
   }
-/>
+}' \
+https://platform-server.exampleanchor.com | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "notify_offchain_funds_pending",
+  params: {
+    transaction_id: "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    message: "Offchain funds pending",
+    external_transaction_id:
+      "3320c6faad48c3cf39b6d4ac15ed50b6e5868b62551e69cde15df2d66c8ca360",
+  },
+};
+let res = await fetch("https://platform-server.exampleanchor.com", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://platform-server.exampleanchor.com", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "notify_offchain_funds_pending",
+    "params": {
+        "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+        "message": "Offchain funds pending",
+        "external_transaction_id": "3320c6faad48c3cf39b6d4ac15ed50b6e5868b62551e69cde15df2d66c8ca360"
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_offchain_funds_pending",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Offchain funds pending",
+    "external_transaction_id": "3320c6faad48c3cf39b6d4ac15ed50b6e5868b62551e69cde15df2d66c8ca360"
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "sep": "24",
+    "kind": "deposit",
+    "status": "completed",
+    "amount_expected": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_in": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_out": {
+      "amount": "0.9",
+      "asset": "iso4217:USD"
+    },
+    "fee_details": {
+      "total": "0.1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "started_at": "2023-08-04T10:04:06.280923Z",
+    "updated_at": "2023-08-04T10:04:15.716233Z",
+    "message": "Transaction complete",
+    "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
+    "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
+  }
+}
+```
+
+{/* /rpc-method */}
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_received.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_received.mdx
index 9e19062ee..4464c3373 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_received.mdx
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_received.mdx
@@ -1,15 +1,542 @@
 ---
 title: notify_offchain_funds_received
-hide_title: true
+description: "<RpcMethod"
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notify_offchain_funds_received",
-    )[0]
+`SEP-6` `SEP-24`
+
+Payment is being processed internally by anchor
+
+## Params (7)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="transaction_id" type="string" required>
+
+The unique identifier of this transaction.
+
+A unique transaction identifier.
+
+</ParamField>
+
+<ParamField body="message" type="string">
+
+Human readable explanation of transaction status.
+
+A human readable message.
+
+</ParamField>
+
+<ParamField body="funds_received_at" type="string">
+
+The date and time of receiving funds.
+
+A date and time.
+
+</ParamField>
+
+<ParamField body="external_transaction_id" type="string">
+
+The unique identifier of this transaction on the external network.
+
+A unique transaction identifier.
+
+</ParamField>
+
+<ParamField body="amount_in" type="object" required>
+
+The amount expected in the payment
+
+  <Expandable title="properties">
+    <ParamField body="amount" type="string" required>
+
+      A numerical representation of an amount of some asset.
+
+    </ParamField>
+    <ParamField body="asset" type="string" required>
+
+      The asset to be received by the Anchor
+
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+<ParamField body="amount_out" type="object" required>
+
+Amount sent by anchor to user
+
+  <Expandable title="properties">
+    <ParamField body="amount" type="string" required>
+
+      A numerical representation of an amount of some asset.
+
+    </ParamField>
+    <ParamField body="asset" type="string" required>
+
+      The asset to be sent by anchor to user at end of transaction
+
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+<ParamField body="fee_details" type="object" required>
+
+Description of fees charged by the anchor
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ParamField body="total" type="number" required>
+    </ParamField>
+    <ParamField body="asset" type="string" required>
+    </ParamField>
+    <ParamField body="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ParamField body="name" type="string">
+        </ParamField>
+        <ParamField body="description" type="string">
+        </ParamField>
+        <ParamField body="amount" type="number">
+        </ParamField>
+      </Expandable>
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+## Result
+
+_(notify_offchain_funds_receivedResponse)_
+
+<ResponseField name="id" type="string">
+
+A unique transaction identifier.
+
+</ResponseField>
+
+<ResponseField name="sep" type="integer">
+
+Protocol of the transaction.
+
+Available options: `6`, `24`, `31`
+
+</ResponseField>
+
+<ResponseField name="kind" type="string">
+
+The kind of transaction that is desired.
+
+Available options: `undefined`, `receive`, `deposit`, `deposit-exchange`, `withdrawal`, `withdrawal-exchange`
+
+</ResponseField>
+
+<ResponseField name="status" type="string">
+
+Processing status of the transaction.
+
+Available options: `pending_anchor`, `pending_trust`, `pending_user`, `pending_user_transfer_start`, `pending_user_transfer_complete`, `incomplete`, `no_market`, `too_small`, `too_large`, `pending_sender`, `pending_receiver`, `pending_transaction_info_update`, `pending_customer_info_update`, `completed`, `refunded`, `expired`, `error`, `pending_external`, `pending_stellar`
+
+</ResponseField>
+
+<ResponseField name="amount_expected" type="object">
+
+The amount expected in the payment.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_in" type="object">
+
+Amount expected/received by anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_out" type="object">
+
+The amount expected to be sent by anchor to user at end of transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="fee_details" type="object">
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="total" type="number" required>
+    </ResponseField>
+    <ResponseField name="asset" type="string" required>
+    </ResponseField>
+    <ResponseField name="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ResponseField name="name" type="string">
+        </ResponseField>
+        <ResponseField name="description" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="number">
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="quote_id" type="string">
+
+The id returned from a SEP-38 POST /quote response
+
+</ResponseField>
+
+<ResponseField name="started_at" type="string">
+
+Start date and time of transaction.
+
+</ResponseField>
+
+<ResponseField name="updated_at" type="string">
+
+The date and time of transaction reaching the current status.
+
+</ResponseField>
+
+<ResponseField name="completed_at" type="string">
+
+The date and time of transaction reaching completed or refunded status.
+
+</ResponseField>
+
+<ResponseField name="transfer_received_at" type="string">
+
+The date and time of receiving transfer.
+
+</ResponseField>
+
+<ResponseField name="message" type="string">
+
+Human readable explanation of transaction status
+
+</ResponseField>
+
+<ResponseField name="refunds" type="object">
+
+An object describing any on or offchain refund associated with this transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount_refunded" type="object">
+
+      The total amount refunded in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="amount_fee" type="object">
+
+      The total amount charged in fees for processing all refund payments, in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="payments" type="object[]">
+
+      A list of objects containing information on the individual payments made back as refunds.
+
+      <Expandable title="items">
+        <ResponseField name="id" type="string">
+
+          The Stellar transaction hash.
+
+        </ResponseField>
+        <ResponseField name="id_type" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="object">
+
+          The amount sent back for the payment identified by id, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="fee" type="object">
+
+          The amount charged as a fee for processing the refund, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="requested_at" type="string">
+
+          The date and time of requesting refund.
+
+        </ResponseField>
+        <ResponseField name="refunded_at" type="string">
+
+          The date and time of making refund.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+## Example
+
+Example request to the `notify_offchain_funds_received` method.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_offchain_funds_received",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Funds received successfully",
+    "funds_received_at": "2023-07-04T12:34:56Z",
+    "external_transaction_id": "3320c6faad48c3cf39b6d4ac15ed50b6e5868b62551e69cde15df2d66c8ca360",
+    "amount_in": {
+      "amount": 1
+    },
+    "amount_out": {
+      "amount": 0.9
+    },
+    "fee_details": {
+      "total": 0.1,
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_expected": {
+      "amount": 1
+    }
   }
-/>
+}' \
+https://platform-server.exampleanchor.com | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "notify_offchain_funds_received",
+  params: {
+    transaction_id: "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    message: "Funds received successfully",
+    funds_received_at: "2023-07-04T12:34:56Z",
+    external_transaction_id:
+      "3320c6faad48c3cf39b6d4ac15ed50b6e5868b62551e69cde15df2d66c8ca360",
+    amount_in: {
+      amount: 1,
+    },
+    amount_out: {
+      amount: 0.9,
+    },
+    fee_details: {
+      total: 0.1,
+      asset:
+        "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5",
+    },
+    amount_expected: {
+      amount: 1,
+    },
+  },
+};
+let res = await fetch("https://platform-server.exampleanchor.com", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://platform-server.exampleanchor.com", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "notify_offchain_funds_received",
+    "params": {
+        "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+        "message": "Funds received successfully",
+        "funds_received_at": "2023-07-04T12:34:56Z",
+        "external_transaction_id": "3320c6faad48c3cf39b6d4ac15ed50b6e5868b62551e69cde15df2d66c8ca360",
+        "amount_in": {
+            "amount": 1
+        },
+        "amount_out": {
+            "amount": 0.9
+        },
+        "fee_details": {
+            "total": 0.1,
+            "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+        },
+        "amount_expected": {
+            "amount": 1
+        }
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_offchain_funds_received",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Funds received successfully",
+    "funds_received_at": "2023-07-04T12:34:56Z",
+    "external_transaction_id": "3320c6faad48c3cf39b6d4ac15ed50b6e5868b62551e69cde15df2d66c8ca360",
+    "amount_in": {
+      "amount": 1
+    },
+    "amount_out": {
+      "amount": 0.9
+    },
+    "fee_details": {
+      "total": 0.1,
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_expected": {
+      "amount": 1
+    }
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "sep": "24",
+    "kind": "deposit",
+    "status": "completed",
+    "amount_expected": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_in": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_out": {
+      "amount": "0.9",
+      "asset": "iso4217:USD"
+    },
+    "fee_details": {
+      "total": "0.1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "started_at": "2023-08-04T10:04:06.280923Z",
+    "updated_at": "2023-08-04T10:04:15.716233Z",
+    "message": "Transaction complete",
+    "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
+    "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
+  }
+}
+```
+
+{/* /rpc-method */}
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_sent.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_sent.mdx
index 5478e2b59..f39a94713 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_sent.mdx
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_sent.mdx
@@ -1,15 +1,423 @@
 ---
 title: notify_offchain_funds_sent
-hide_title: true
+description: "<RpcMethod"
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notify_offchain_funds_sent",
-    )[0]
+`SEP-6` `SEP-24` `SEP-31`
+
+Transaction flow is fully completed for the SEP-6 and SEP-24 withdrawal flow or SEP-31 receive flow. Payment has been submitted to external network, but is not yet confirmed for SEP-24 deposit flow
+
+## Params (4)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="transaction_id" type="string" required>
+
+The unique identifier of this transaction.
+
+A unique transaction identifier.
+
+</ParamField>
+
+<ParamField body="message" type="string">
+
+Human readable explanation of transaction status.
+
+A human readable message.
+
+</ParamField>
+
+<ParamField body="funds_sent_at" type="string">
+
+The date and time of sending funds.
+
+A date and time.
+
+</ParamField>
+
+<ParamField body="external_transaction_id" type="string">
+
+The unique identifier of this transaction on the external network.
+
+A unique transaction identifier.
+
+</ParamField>
+
+## Result
+
+_(notify_offchain_funds_sentResponse)_
+
+<ResponseField name="id" type="string">
+
+A unique transaction identifier.
+
+</ResponseField>
+
+<ResponseField name="sep" type="integer">
+
+Protocol of the transaction.
+
+Available options: `6`, `24`, `31`
+
+</ResponseField>
+
+<ResponseField name="kind" type="string">
+
+The kind of transaction that is desired.
+
+Available options: `undefined`, `receive`, `deposit`, `deposit-exchange`, `withdrawal`, `withdrawal-exchange`
+
+</ResponseField>
+
+<ResponseField name="status" type="string">
+
+Processing status of the transaction.
+
+Available options: `pending_anchor`, `pending_trust`, `pending_user`, `pending_user_transfer_start`, `pending_user_transfer_complete`, `incomplete`, `no_market`, `too_small`, `too_large`, `pending_sender`, `pending_receiver`, `pending_transaction_info_update`, `pending_customer_info_update`, `completed`, `refunded`, `expired`, `error`, `pending_external`, `pending_stellar`
+
+</ResponseField>
+
+<ResponseField name="amount_expected" type="object">
+
+The amount expected in the payment.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_in" type="object">
+
+Amount expected/received by anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_out" type="object">
+
+The amount expected to be sent by anchor to user at end of transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="fee_details" type="object">
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="total" type="number" required>
+    </ResponseField>
+    <ResponseField name="asset" type="string" required>
+    </ResponseField>
+    <ResponseField name="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ResponseField name="name" type="string">
+        </ResponseField>
+        <ResponseField name="description" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="number">
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="quote_id" type="string">
+
+The id returned from a SEP-38 POST /quote response
+
+</ResponseField>
+
+<ResponseField name="started_at" type="string">
+
+Start date and time of transaction.
+
+</ResponseField>
+
+<ResponseField name="updated_at" type="string">
+
+The date and time of transaction reaching the current status.
+
+</ResponseField>
+
+<ResponseField name="completed_at" type="string">
+
+The date and time of transaction reaching completed or refunded status.
+
+</ResponseField>
+
+<ResponseField name="transfer_received_at" type="string">
+
+The date and time of receiving transfer.
+
+</ResponseField>
+
+<ResponseField name="message" type="string">
+
+Human readable explanation of transaction status
+
+</ResponseField>
+
+<ResponseField name="refunds" type="object">
+
+An object describing any on or offchain refund associated with this transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount_refunded" type="object">
+
+      The total amount refunded in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="amount_fee" type="object">
+
+      The total amount charged in fees for processing all refund payments, in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="payments" type="object[]">
+
+      A list of objects containing information on the individual payments made back as refunds.
+
+      <Expandable title="items">
+        <ResponseField name="id" type="string">
+
+          The Stellar transaction hash.
+
+        </ResponseField>
+        <ResponseField name="id_type" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="object">
+
+          The amount sent back for the payment identified by id, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="fee" type="object">
+
+          The amount charged as a fee for processing the refund, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="requested_at" type="string">
+
+          The date and time of requesting refund.
+
+        </ResponseField>
+        <ResponseField name="refunded_at" type="string">
+
+          The date and time of making refund.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+## Example
+
+Example request to the `notify_offchain_funds_sent` method.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_offchain_funds_sent",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Offchain funds sent",
+    "funds_sent_at": "2023-07-04T12:34:38Z",
+    "external_transaction_id": "3320c6faad48c3cf39b6d4ac15ed50b6e5868b62551e69cde15df2d66c8ca360"
   }
-/>
+}' \
+https://platform-server.exampleanchor.com | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "notify_offchain_funds_sent",
+  params: {
+    transaction_id: "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    message: "Offchain funds sent",
+    funds_sent_at: "2023-07-04T12:34:38Z",
+    external_transaction_id:
+      "3320c6faad48c3cf39b6d4ac15ed50b6e5868b62551e69cde15df2d66c8ca360",
+  },
+};
+let res = await fetch("https://platform-server.exampleanchor.com", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://platform-server.exampleanchor.com", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "notify_offchain_funds_sent",
+    "params": {
+        "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+        "message": "Offchain funds sent",
+        "funds_sent_at": "2023-07-04T12:34:38Z",
+        "external_transaction_id": "3320c6faad48c3cf39b6d4ac15ed50b6e5868b62551e69cde15df2d66c8ca360"
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_offchain_funds_sent",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Offchain funds sent",
+    "funds_sent_at": "2023-07-04T12:34:38Z",
+    "external_transaction_id": "3320c6faad48c3cf39b6d4ac15ed50b6e5868b62551e69cde15df2d66c8ca360"
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "sep": "24",
+    "kind": "deposit",
+    "status": "completed",
+    "amount_expected": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_in": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_out": {
+      "amount": "0.9",
+      "asset": "iso4217:USD"
+    },
+    "fee_details": {
+      "total": "0.1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "started_at": "2023-08-04T10:04:06.280923Z",
+    "updated_at": "2023-08-04T10:04:15.716233Z",
+    "message": "Transaction complete",
+    "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
+    "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
+  }
+}
+```
+
+{/* /rpc-method */}
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_received.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_received.mdx
index 24ef7eaca..24e7c511a 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_received.mdx
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_received.mdx
@@ -1,15 +1,489 @@
 ---
 title: notify_onchain_funds_received
-hide_title: true
+description: "<RpcMethod"
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notify_onchain_funds_received",
-    )[0]
+`SEP-6` `SEP-24` `SEP-31`
+
+Notify that the payment is being processed internally by anchor for SEP-6 or SEP-24. For SEP-31, notify that the payment is being processed by the Receiving Anchor. In the request, amount parameters are optional, but have a strict rule of how to set them. Either none, only `amount_in`, or all of fields (`amount_in`, `amount_out`, `fee_details`) must be specified.
+
+## Params (6)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="transaction_id" type="string" required>
+
+The unique identifier of this transaction.
+
+A unique transaction identifier.
+
+</ParamField>
+
+<ParamField body="message" type="string">
+
+Human readable explanation of transaction status.
+
+A human readable message.
+
+</ParamField>
+
+<ParamField body="stellar_transaction_id" type="string" required>
+
+The unique transaction identifier for this transfer on the Stellar network.
+
+The Stellar transaction hash.
+
+</ParamField>
+
+<ParamField body="amount_in" type="object" required>
+
+The amount expected in the payment
+
+  <Expandable title="properties">
+    <ParamField body="amount" type="string" required>
+
+      A numerical representation of an amount of some asset.
+
+    </ParamField>
+    <ParamField body="asset" type="string" required>
+
+      The asset to be received by the Anchor
+
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+<ParamField body="amount_out" type="object" required>
+
+Amount sent by anchor to user
+
+  <Expandable title="properties">
+    <ParamField body="amount" type="string" required>
+
+      A numerical representation of an amount of some asset.
+
+    </ParamField>
+    <ParamField body="asset" type="string" required>
+
+      The asset to be sent by anchor to user at end of transaction
+
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+<ParamField body="fee_details" type="object" required>
+
+Description of fees charged by the anchor
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ParamField body="total" type="number" required>
+    </ParamField>
+    <ParamField body="asset" type="string" required>
+    </ParamField>
+    <ParamField body="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ParamField body="name" type="string">
+        </ParamField>
+        <ParamField body="description" type="string">
+        </ParamField>
+        <ParamField body="amount" type="number">
+        </ParamField>
+      </Expandable>
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+## Result
+
+_(notify_onchain_funds_receivedResponse)_
+
+<ResponseField name="id" type="string">
+
+A unique transaction identifier.
+
+</ResponseField>
+
+<ResponseField name="sep" type="integer">
+
+Protocol of the transaction.
+
+Available options: `6`, `24`, `31`
+
+</ResponseField>
+
+<ResponseField name="kind" type="string">
+
+The kind of transaction that is desired.
+
+Available options: `undefined`, `receive`, `deposit`, `deposit-exchange`, `withdrawal`, `withdrawal-exchange`
+
+</ResponseField>
+
+<ResponseField name="status" type="string">
+
+Processing status of the transaction.
+
+Available options: `pending_anchor`, `pending_trust`, `pending_user`, `pending_user_transfer_start`, `pending_user_transfer_complete`, `incomplete`, `no_market`, `too_small`, `too_large`, `pending_sender`, `pending_receiver`, `pending_transaction_info_update`, `pending_customer_info_update`, `completed`, `refunded`, `expired`, `error`, `pending_external`, `pending_stellar`
+
+</ResponseField>
+
+<ResponseField name="amount_expected" type="object">
+
+The amount expected in the payment.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_in" type="object">
+
+Amount expected/received by anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_out" type="object">
+
+The amount expected to be sent by anchor to user at end of transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="fee_details" type="object">
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="total" type="number" required>
+    </ResponseField>
+    <ResponseField name="asset" type="string" required>
+    </ResponseField>
+    <ResponseField name="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ResponseField name="name" type="string">
+        </ResponseField>
+        <ResponseField name="description" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="number">
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="quote_id" type="string">
+
+The id returned from a SEP-38 POST /quote response
+
+</ResponseField>
+
+<ResponseField name="started_at" type="string">
+
+Start date and time of transaction.
+
+</ResponseField>
+
+<ResponseField name="updated_at" type="string">
+
+The date and time of transaction reaching the current status.
+
+</ResponseField>
+
+<ResponseField name="completed_at" type="string">
+
+The date and time of transaction reaching completed or refunded status.
+
+</ResponseField>
+
+<ResponseField name="transfer_received_at" type="string">
+
+The date and time of receiving transfer.
+
+</ResponseField>
+
+<ResponseField name="message" type="string">
+
+Human readable explanation of transaction status
+
+</ResponseField>
+
+<ResponseField name="refunds" type="object">
+
+An object describing any on or offchain refund associated with this transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount_refunded" type="object">
+
+      The total amount refunded in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="amount_fee" type="object">
+
+      The total amount charged in fees for processing all refund payments, in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="payments" type="object[]">
+
+      A list of objects containing information on the individual payments made back as refunds.
+
+      <Expandable title="items">
+        <ResponseField name="id" type="string">
+
+          The Stellar transaction hash.
+
+        </ResponseField>
+        <ResponseField name="id_type" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="object">
+
+          The amount sent back for the payment identified by id, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="fee" type="object">
+
+          The amount charged as a fee for processing the refund, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="requested_at" type="string">
+
+          The date and time of requesting refund.
+
+        </ResponseField>
+        <ResponseField name="refunded_at" type="string">
+
+          The date and time of making refund.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+## Example
+
+Example request to the `notify_onchain_funds_received` method.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_onchain_funds_received",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Onchain funds received",
+    "stellar_transaction_id": "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e",
+    "amount_in": {
+      "amount": 1
+    }
   }
-/>
+}' \
+https://platform-server.exampleanchor.com | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "notify_onchain_funds_received",
+  params: {
+    transaction_id: "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    message: "Onchain funds received",
+    stellar_transaction_id:
+      "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e",
+    amount_in: {
+      amount: 1,
+    },
+  },
+};
+let res = await fetch("https://platform-server.exampleanchor.com", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://platform-server.exampleanchor.com", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "notify_onchain_funds_received",
+    "params": {
+        "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+        "message": "Onchain funds received",
+        "stellar_transaction_id": "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e",
+        "amount_in": {
+            "amount": 1
+        }
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_onchain_funds_received",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Onchain funds received",
+    "stellar_transaction_id": "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e",
+    "amount_in": {
+      "amount": 1
+    }
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "sep": "24",
+    "kind": "deposit",
+    "status": "completed",
+    "amount_expected": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_in": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_out": {
+      "amount": "0.9",
+      "asset": "iso4217:USD"
+    },
+    "fee_details": {
+      "total": "0.1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "started_at": "2023-08-04T10:04:06.280923Z",
+    "updated_at": "2023-08-04T10:04:15.716233Z",
+    "message": "Transaction complete",
+    "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
+    "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
+  }
+}
+```
+
+{/* /rpc-method */}
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_sent.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_sent.mdx
index 1a776c958..37570d5f7 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_sent.mdx
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_sent.mdx
@@ -1,15 +1,411 @@
 ---
 title: notify_onchain_funds_sent
-hide_title: true
+description: "<RpcMethod"
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notify_onchain_funds_sent",
-    )[0]
+`SEP-6` `SEP-24`
+
+Transaction flow is fully completed for SEP-6 or SEP-24 deposit
+
+## Params (3)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="transaction_id" type="string" required>
+
+The unique identifier of this transaction.
+
+A unique transaction identifier.
+
+</ParamField>
+
+<ParamField body="message" type="string">
+
+Human readable explanation of transaction status.
+
+A human readable message.
+
+</ParamField>
+
+<ParamField body="stellar_transaction_id" type="string" required>
+
+The unique transaction identifier for this transfer on the Stellar network.
+
+The Stellar transaction hash.
+
+</ParamField>
+
+## Result
+
+_(notify_onchain_funds_sentResponse)_
+
+<ResponseField name="id" type="string">
+
+A unique transaction identifier.
+
+</ResponseField>
+
+<ResponseField name="sep" type="integer">
+
+Protocol of the transaction.
+
+Available options: `6`, `24`, `31`
+
+</ResponseField>
+
+<ResponseField name="kind" type="string">
+
+The kind of transaction that is desired.
+
+Available options: `undefined`, `receive`, `deposit`, `deposit-exchange`, `withdrawal`, `withdrawal-exchange`
+
+</ResponseField>
+
+<ResponseField name="status" type="string">
+
+Processing status of the transaction.
+
+Available options: `pending_anchor`, `pending_trust`, `pending_user`, `pending_user_transfer_start`, `pending_user_transfer_complete`, `incomplete`, `no_market`, `too_small`, `too_large`, `pending_sender`, `pending_receiver`, `pending_transaction_info_update`, `pending_customer_info_update`, `completed`, `refunded`, `expired`, `error`, `pending_external`, `pending_stellar`
+
+</ResponseField>
+
+<ResponseField name="amount_expected" type="object">
+
+The amount expected in the payment.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_in" type="object">
+
+Amount expected/received by anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_out" type="object">
+
+The amount expected to be sent by anchor to user at end of transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="fee_details" type="object">
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="total" type="number" required>
+    </ResponseField>
+    <ResponseField name="asset" type="string" required>
+    </ResponseField>
+    <ResponseField name="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ResponseField name="name" type="string">
+        </ResponseField>
+        <ResponseField name="description" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="number">
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="quote_id" type="string">
+
+The id returned from a SEP-38 POST /quote response
+
+</ResponseField>
+
+<ResponseField name="started_at" type="string">
+
+Start date and time of transaction.
+
+</ResponseField>
+
+<ResponseField name="updated_at" type="string">
+
+The date and time of transaction reaching the current status.
+
+</ResponseField>
+
+<ResponseField name="completed_at" type="string">
+
+The date and time of transaction reaching completed or refunded status.
+
+</ResponseField>
+
+<ResponseField name="transfer_received_at" type="string">
+
+The date and time of receiving transfer.
+
+</ResponseField>
+
+<ResponseField name="message" type="string">
+
+Human readable explanation of transaction status
+
+</ResponseField>
+
+<ResponseField name="refunds" type="object">
+
+An object describing any on or offchain refund associated with this transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount_refunded" type="object">
+
+      The total amount refunded in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="amount_fee" type="object">
+
+      The total amount charged in fees for processing all refund payments, in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="payments" type="object[]">
+
+      A list of objects containing information on the individual payments made back as refunds.
+
+      <Expandable title="items">
+        <ResponseField name="id" type="string">
+
+          The Stellar transaction hash.
+
+        </ResponseField>
+        <ResponseField name="id_type" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="object">
+
+          The amount sent back for the payment identified by id, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="fee" type="object">
+
+          The amount charged as a fee for processing the refund, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="requested_at" type="string">
+
+          The date and time of requesting refund.
+
+        </ResponseField>
+        <ResponseField name="refunded_at" type="string">
+
+          The date and time of making refund.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+## Example
+
+Example request to the `notify_onchain_funds_sent` method.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_onchain_funds_sent",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Onchain funds sent",
+    "stellar_transaction_id": "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e"
+  }
+}' \
+https://platform-server.exampleanchor.com | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "notify_onchain_funds_sent",
+  params: {
+    transaction_id: "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    message: "Onchain funds sent",
+    stellar_transaction_id:
+      "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e",
+  },
+};
+let res = await fetch("https://platform-server.exampleanchor.com", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://platform-server.exampleanchor.com", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "notify_onchain_funds_sent",
+    "params": {
+        "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+        "message": "Onchain funds sent",
+        "stellar_transaction_id": "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e"
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_onchain_funds_sent",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Onchain funds sent",
+    "stellar_transaction_id": "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e"
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "sep": "24",
+    "kind": "deposit",
+    "status": "completed",
+    "amount_expected": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_in": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_out": {
+      "amount": "0.9",
+      "asset": "iso4217:USD"
+    },
+    "fee_details": {
+      "total": "0.1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "started_at": "2023-08-04T10:04:06.280923Z",
+    "updated_at": "2023-08-04T10:04:15.716233Z",
+    "message": "Transaction complete",
+    "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
+    "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
   }
-/>
+}
+```
+
+{/* /rpc-method */}
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_pending.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_pending.mdx
index bc24b1229..6c02c9eda 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_pending.mdx
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_pending.mdx
@@ -1,13 +1,489 @@
 ---
 title: notify_refund_pending
-hide_title: true
+description: "<RpcMethod"
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={
-    rpcSpec.methods.filter((meth) => meth.name === "notify_refund_pending")[0]
+`SEP-6` `SEP-24`
+
+Refund has been submitted, but is not yet confirmed
+
+## Params (3)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="transaction_id" type="string" required>
+
+The unique identifier of this transaction.
+
+A unique transaction identifier.
+
+</ParamField>
+
+<ParamField body="message" type="string">
+
+Human readable explanation of transaction status.
+
+A human readable message.
+
+</ParamField>
+
+<ParamField body="refund" type="object">
+  <Expandable title="properties">
+    <ParamField body="amount" type="object" required>
+
+      Amount to be refunded
+
+      <Expandable title="properties">
+        <ParamField body="amount" type="string" required>
+
+          Amount of assets to refund
+
+        </ParamField>
+        <ParamField body="asset" type="string" required>
+
+          The asset of refund
+
+        </ParamField>
+      </Expandable>
+    </ParamField>
+    <ParamField body="amount_fee" type="object" required>
+
+      Amount of fee
+
+      <Expandable title="properties">
+        <ParamField body="amount" type="string" required>
+
+          The amount of fee
+
+        </ParamField>
+        <ParamField body="asset" type="string" required>
+
+          The asset of fee charged by anchor
+
+        </ParamField>
+      </Expandable>
+    </ParamField>
+    <ParamField body="id" type="string" required>
+
+      The Stellar transaction hash.
+
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+## Result
+
+_(notify_refund_pendingResponse)_
+
+<ResponseField name="id" type="string">
+
+A unique transaction identifier.
+
+</ResponseField>
+
+<ResponseField name="sep" type="integer">
+
+Protocol of the transaction.
+
+Available options: `6`, `24`, `31`
+
+</ResponseField>
+
+<ResponseField name="kind" type="string">
+
+The kind of transaction that is desired.
+
+Available options: `undefined`, `receive`, `deposit`, `deposit-exchange`, `withdrawal`, `withdrawal-exchange`
+
+</ResponseField>
+
+<ResponseField name="status" type="string">
+
+Processing status of the transaction.
+
+Available options: `pending_anchor`, `pending_trust`, `pending_user`, `pending_user_transfer_start`, `pending_user_transfer_complete`, `incomplete`, `no_market`, `too_small`, `too_large`, `pending_sender`, `pending_receiver`, `pending_transaction_info_update`, `pending_customer_info_update`, `completed`, `refunded`, `expired`, `error`, `pending_external`, `pending_stellar`
+
+</ResponseField>
+
+<ResponseField name="amount_expected" type="object">
+
+The amount expected in the payment.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_in" type="object">
+
+Amount expected/received by anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_out" type="object">
+
+The amount expected to be sent by anchor to user at end of transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="fee_details" type="object">
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="total" type="number" required>
+    </ResponseField>
+    <ResponseField name="asset" type="string" required>
+    </ResponseField>
+    <ResponseField name="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ResponseField name="name" type="string">
+        </ResponseField>
+        <ResponseField name="description" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="number">
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="quote_id" type="string">
+
+The id returned from a SEP-38 POST /quote response
+
+</ResponseField>
+
+<ResponseField name="started_at" type="string">
+
+Start date and time of transaction.
+
+</ResponseField>
+
+<ResponseField name="updated_at" type="string">
+
+The date and time of transaction reaching the current status.
+
+</ResponseField>
+
+<ResponseField name="completed_at" type="string">
+
+The date and time of transaction reaching completed or refunded status.
+
+</ResponseField>
+
+<ResponseField name="transfer_received_at" type="string">
+
+The date and time of receiving transfer.
+
+</ResponseField>
+
+<ResponseField name="message" type="string">
+
+Human readable explanation of transaction status
+
+</ResponseField>
+
+<ResponseField name="refunds" type="object">
+
+An object describing any on or offchain refund associated with this transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount_refunded" type="object">
+
+      The total amount refunded in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="amount_fee" type="object">
+
+      The total amount charged in fees for processing all refund payments, in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="payments" type="object[]">
+
+      A list of objects containing information on the individual payments made back as refunds.
+
+      <Expandable title="items">
+        <ResponseField name="id" type="string">
+
+          The Stellar transaction hash.
+
+        </ResponseField>
+        <ResponseField name="id_type" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="object">
+
+          The amount sent back for the payment identified by id, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="fee" type="object">
+
+          The amount charged as a fee for processing the refund, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="requested_at" type="string">
+
+          The date and time of requesting refund.
+
+        </ResponseField>
+        <ResponseField name="refunded_at" type="string">
+
+          The date and time of making refund.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+## Example
+
+Example request to the `notify_refund_pending` method.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_refund_pending",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Refund pending",
+    "refund": {
+      "id": "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e",
+      "amount": {
+        "amount": 1,
+        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+      },
+      "amount_fee": {
+        "amount": 0.1,
+        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+      }
+    }
   }
-/>
+}' \
+https://platform-server.exampleanchor.com | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "notify_refund_pending",
+  params: {
+    transaction_id: "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    message: "Refund pending",
+    refund: {
+      id: "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e",
+      amount: {
+        amount: 1,
+        asset:
+          "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5",
+      },
+      amount_fee: {
+        amount: 0.1,
+        asset:
+          "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5",
+      },
+    },
+  },
+};
+let res = await fetch("https://platform-server.exampleanchor.com", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://platform-server.exampleanchor.com", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "notify_refund_pending",
+    "params": {
+        "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+        "message": "Refund pending",
+        "refund": {
+            "id": "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e",
+            "amount": {
+                "amount": 1,
+                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+            },
+            "amount_fee": {
+                "amount": 0.1,
+                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+            }
+        }
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_refund_pending",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Refund pending",
+    "refund": {
+      "id": "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e",
+      "amount": {
+        "amount": 1,
+        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+      },
+      "amount_fee": {
+        "amount": 0.1,
+        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+      }
+    }
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "sep": "24",
+    "kind": "deposit",
+    "status": "completed",
+    "amount_expected": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_in": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_out": {
+      "amount": "0.9",
+      "asset": "iso4217:USD"
+    },
+    "fee_details": {
+      "total": "0.1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "started_at": "2023-08-04T10:04:06.280923Z",
+    "updated_at": "2023-08-04T10:04:15.716233Z",
+    "message": "Transaction complete",
+    "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
+    "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
+  }
+}
+```
+
+{/* /rpc-method */}
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_sent.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_sent.mdx
index fc0255d3f..a46569ef7 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_sent.mdx
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_sent.mdx
@@ -1,13 +1,489 @@
 ---
 title: notify_refund_sent
-hide_title: true
+description: "<RpcMethod"
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={
-    rpcSpec.methods.filter((meth) => meth.name === "notify_refund_sent")[0]
+`SEP-6` `SEP-24` `SEP-31`
+
+Refund payment completed
+
+## Params (3)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="transaction_id" type="string" required>
+
+The unique identifier of this transaction.
+
+A unique transaction identifier.
+
+</ParamField>
+
+<ParamField body="message" type="string">
+
+Human readable explanation of transaction status.
+
+A human readable message.
+
+</ParamField>
+
+<ParamField body="refund" type="object">
+  <Expandable title="properties">
+    <ParamField body="amount" type="object" required>
+
+      Amount to be refunded
+
+      <Expandable title="properties">
+        <ParamField body="amount" type="string" required>
+
+          Amount of assets to refund
+
+        </ParamField>
+        <ParamField body="asset" type="string" required>
+
+          The asset of refund
+
+        </ParamField>
+      </Expandable>
+    </ParamField>
+    <ParamField body="amount_fee" type="object" required>
+
+      Amount of fee
+
+      <Expandable title="properties">
+        <ParamField body="amount" type="string" required>
+
+          The amount of fee
+
+        </ParamField>
+        <ParamField body="asset" type="string" required>
+
+          The asset of fee charged by anchor
+
+        </ParamField>
+      </Expandable>
+    </ParamField>
+    <ParamField body="id" type="string" required>
+
+      The Stellar transaction hash.
+
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+## Result
+
+_(notify_refund_sentResponse)_
+
+<ResponseField name="id" type="string">
+
+A unique transaction identifier.
+
+</ResponseField>
+
+<ResponseField name="sep" type="integer">
+
+Protocol of the transaction.
+
+Available options: `6`, `24`, `31`
+
+</ResponseField>
+
+<ResponseField name="kind" type="string">
+
+The kind of transaction that is desired.
+
+Available options: `undefined`, `receive`, `deposit`, `deposit-exchange`, `withdrawal`, `withdrawal-exchange`
+
+</ResponseField>
+
+<ResponseField name="status" type="string">
+
+Processing status of the transaction.
+
+Available options: `pending_anchor`, `pending_trust`, `pending_user`, `pending_user_transfer_start`, `pending_user_transfer_complete`, `incomplete`, `no_market`, `too_small`, `too_large`, `pending_sender`, `pending_receiver`, `pending_transaction_info_update`, `pending_customer_info_update`, `completed`, `refunded`, `expired`, `error`, `pending_external`, `pending_stellar`
+
+</ResponseField>
+
+<ResponseField name="amount_expected" type="object">
+
+The amount expected in the payment.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_in" type="object">
+
+Amount expected/received by anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_out" type="object">
+
+The amount expected to be sent by anchor to user at end of transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="fee_details" type="object">
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="total" type="number" required>
+    </ResponseField>
+    <ResponseField name="asset" type="string" required>
+    </ResponseField>
+    <ResponseField name="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ResponseField name="name" type="string">
+        </ResponseField>
+        <ResponseField name="description" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="number">
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="quote_id" type="string">
+
+The id returned from a SEP-38 POST /quote response
+
+</ResponseField>
+
+<ResponseField name="started_at" type="string">
+
+Start date and time of transaction.
+
+</ResponseField>
+
+<ResponseField name="updated_at" type="string">
+
+The date and time of transaction reaching the current status.
+
+</ResponseField>
+
+<ResponseField name="completed_at" type="string">
+
+The date and time of transaction reaching completed or refunded status.
+
+</ResponseField>
+
+<ResponseField name="transfer_received_at" type="string">
+
+The date and time of receiving transfer.
+
+</ResponseField>
+
+<ResponseField name="message" type="string">
+
+Human readable explanation of transaction status
+
+</ResponseField>
+
+<ResponseField name="refunds" type="object">
+
+An object describing any on or offchain refund associated with this transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount_refunded" type="object">
+
+      The total amount refunded in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="amount_fee" type="object">
+
+      The total amount charged in fees for processing all refund payments, in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="payments" type="object[]">
+
+      A list of objects containing information on the individual payments made back as refunds.
+
+      <Expandable title="items">
+        <ResponseField name="id" type="string">
+
+          The Stellar transaction hash.
+
+        </ResponseField>
+        <ResponseField name="id_type" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="object">
+
+          The amount sent back for the payment identified by id, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="fee" type="object">
+
+          The amount charged as a fee for processing the refund, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="requested_at" type="string">
+
+          The date and time of requesting refund.
+
+        </ResponseField>
+        <ResponseField name="refunded_at" type="string">
+
+          The date and time of making refund.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+## Example
+
+Example request to the `notify_refund_sent` method.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_refund_sent",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Refund sent",
+    "refund": {
+      "id": "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e",
+      "amount": {
+        "amount": 1,
+        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+      },
+      "amount_fee": {
+        "amount": 0.1,
+        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+      }
+    }
   }
-/>
+}' \
+https://platform-server.exampleanchor.com | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "notify_refund_sent",
+  params: {
+    transaction_id: "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    message: "Refund sent",
+    refund: {
+      id: "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e",
+      amount: {
+        amount: 1,
+        asset:
+          "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5",
+      },
+      amount_fee: {
+        amount: 0.1,
+        asset:
+          "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5",
+      },
+    },
+  },
+};
+let res = await fetch("https://platform-server.exampleanchor.com", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://platform-server.exampleanchor.com", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "notify_refund_sent",
+    "params": {
+        "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+        "message": "Refund sent",
+        "refund": {
+            "id": "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e",
+            "amount": {
+                "amount": 1,
+                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+            },
+            "amount_fee": {
+                "amount": 0.1,
+                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+            }
+        }
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_refund_sent",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Refund sent",
+    "refund": {
+      "id": "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e",
+      "amount": {
+        "amount": 1,
+        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+      },
+      "amount_fee": {
+        "amount": 0.1,
+        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+      }
+    }
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "sep": "24",
+    "kind": "deposit",
+    "status": "completed",
+    "amount_expected": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_in": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_out": {
+      "amount": "0.9",
+      "asset": "iso4217:USD"
+    },
+    "fee_details": {
+      "total": "0.1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "started_at": "2023-08-04T10:04:06.280923Z",
+    "updated_at": "2023-08-04T10:04:15.716233Z",
+    "message": "Transaction complete",
+    "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
+    "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
+  }
+}
+```
+
+{/* /rpc-method */}
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_error.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_error.mdx
index 83b48d8f8..84e968cea 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_error.mdx
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_error.mdx
@@ -1,15 +1,398 @@
 ---
 title: notify_transaction_error
-hide_title: true
+description: "<RpcMethod"
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notify_transaction_error",
-    )[0]
+`SEP-6` `SEP-24` `SEP-31`
+
+There was an error processing transaction
+
+## Params (2)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="transaction_id" type="string" required>
+
+The unique identifier of this transaction.
+
+A unique transaction identifier.
+
+</ParamField>
+
+<ParamField body="message" type="string">
+
+Human readable explanation of transaction status.
+
+A human readable message.
+
+</ParamField>
+
+## Result
+
+_(notify_transaction_errorResponse)_
+
+<ResponseField name="id" type="string">
+
+A unique transaction identifier.
+
+</ResponseField>
+
+<ResponseField name="sep" type="integer">
+
+Protocol of the transaction.
+
+Available options: `6`, `24`, `31`
+
+</ResponseField>
+
+<ResponseField name="kind" type="string">
+
+The kind of transaction that is desired.
+
+Available options: `undefined`, `receive`, `deposit`, `deposit-exchange`, `withdrawal`, `withdrawal-exchange`
+
+</ResponseField>
+
+<ResponseField name="status" type="string">
+
+Processing status of the transaction.
+
+Available options: `pending_anchor`, `pending_trust`, `pending_user`, `pending_user_transfer_start`, `pending_user_transfer_complete`, `incomplete`, `no_market`, `too_small`, `too_large`, `pending_sender`, `pending_receiver`, `pending_transaction_info_update`, `pending_customer_info_update`, `completed`, `refunded`, `expired`, `error`, `pending_external`, `pending_stellar`
+
+</ResponseField>
+
+<ResponseField name="amount_expected" type="object">
+
+The amount expected in the payment.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_in" type="object">
+
+Amount expected/received by anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_out" type="object">
+
+The amount expected to be sent by anchor to user at end of transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="fee_details" type="object">
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="total" type="number" required>
+    </ResponseField>
+    <ResponseField name="asset" type="string" required>
+    </ResponseField>
+    <ResponseField name="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ResponseField name="name" type="string">
+        </ResponseField>
+        <ResponseField name="description" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="number">
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="quote_id" type="string">
+
+The id returned from a SEP-38 POST /quote response
+
+</ResponseField>
+
+<ResponseField name="started_at" type="string">
+
+Start date and time of transaction.
+
+</ResponseField>
+
+<ResponseField name="updated_at" type="string">
+
+The date and time of transaction reaching the current status.
+
+</ResponseField>
+
+<ResponseField name="completed_at" type="string">
+
+The date and time of transaction reaching completed or refunded status.
+
+</ResponseField>
+
+<ResponseField name="transfer_received_at" type="string">
+
+The date and time of receiving transfer.
+
+</ResponseField>
+
+<ResponseField name="message" type="string">
+
+Human readable explanation of transaction status
+
+</ResponseField>
+
+<ResponseField name="refunds" type="object">
+
+An object describing any on or offchain refund associated with this transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount_refunded" type="object">
+
+      The total amount refunded in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="amount_fee" type="object">
+
+      The total amount charged in fees for processing all refund payments, in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="payments" type="object[]">
+
+      A list of objects containing information on the individual payments made back as refunds.
+
+      <Expandable title="items">
+        <ResponseField name="id" type="string">
+
+          The Stellar transaction hash.
+
+        </ResponseField>
+        <ResponseField name="id_type" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="object">
+
+          The amount sent back for the payment identified by id, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="fee" type="object">
+
+          The amount charged as a fee for processing the refund, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="requested_at" type="string">
+
+          The date and time of requesting refund.
+
+        </ResponseField>
+        <ResponseField name="refunded_at" type="string">
+
+          The date and time of making refund.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+## Example
+
+Example request to the `notify_transaction_error` method.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_transaction_error",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Transaction error"
+  }
+}' \
+https://platform-server.exampleanchor.com | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "notify_transaction_error",
+  params: {
+    transaction_id: "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    message: "Transaction error",
+  },
+};
+let res = await fetch("https://platform-server.exampleanchor.com", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://platform-server.exampleanchor.com", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "notify_transaction_error",
+    "params": {
+        "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+        "message": "Transaction error"
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_transaction_error",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Transaction error"
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "sep": "24",
+    "kind": "deposit",
+    "status": "completed",
+    "amount_expected": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_in": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_out": {
+      "amount": "0.9",
+      "asset": "iso4217:USD"
+    },
+    "fee_details": {
+      "total": "0.1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "started_at": "2023-08-04T10:04:06.280923Z",
+    "updated_at": "2023-08-04T10:04:15.716233Z",
+    "message": "Transaction complete",
+    "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
+    "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
   }
-/>
+}
+```
+
+{/* /rpc-method */}
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_expired.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_expired.mdx
index 6587a4cf9..5d59d4f5d 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_expired.mdx
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_expired.mdx
@@ -1,15 +1,398 @@
 ---
 title: notify_transaction_expired
-hide_title: true
+description: "<RpcMethod"
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notify_transaction_expired",
-    )[0]
+`SEP-6` `SEP-24` `SEP-31`
+
+Funds were never received by the anchor and the transaction is considered abandoned by the user
+
+## Params (2)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="transaction_id" type="string" required>
+
+The unique identifier of this transaction.
+
+A unique transaction identifier.
+
+</ParamField>
+
+<ParamField body="message" type="string">
+
+Human readable explanation of transaction status.
+
+A human readable message.
+
+</ParamField>
+
+## Result
+
+_(notify_transaction_expiredResponse)_
+
+<ResponseField name="id" type="string">
+
+A unique transaction identifier.
+
+</ResponseField>
+
+<ResponseField name="sep" type="integer">
+
+Protocol of the transaction.
+
+Available options: `6`, `24`, `31`
+
+</ResponseField>
+
+<ResponseField name="kind" type="string">
+
+The kind of transaction that is desired.
+
+Available options: `undefined`, `receive`, `deposit`, `deposit-exchange`, `withdrawal`, `withdrawal-exchange`
+
+</ResponseField>
+
+<ResponseField name="status" type="string">
+
+Processing status of the transaction.
+
+Available options: `pending_anchor`, `pending_trust`, `pending_user`, `pending_user_transfer_start`, `pending_user_transfer_complete`, `incomplete`, `no_market`, `too_small`, `too_large`, `pending_sender`, `pending_receiver`, `pending_transaction_info_update`, `pending_customer_info_update`, `completed`, `refunded`, `expired`, `error`, `pending_external`, `pending_stellar`
+
+</ResponseField>
+
+<ResponseField name="amount_expected" type="object">
+
+The amount expected in the payment.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_in" type="object">
+
+Amount expected/received by anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_out" type="object">
+
+The amount expected to be sent by anchor to user at end of transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="fee_details" type="object">
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="total" type="number" required>
+    </ResponseField>
+    <ResponseField name="asset" type="string" required>
+    </ResponseField>
+    <ResponseField name="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ResponseField name="name" type="string">
+        </ResponseField>
+        <ResponseField name="description" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="number">
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="quote_id" type="string">
+
+The id returned from a SEP-38 POST /quote response
+
+</ResponseField>
+
+<ResponseField name="started_at" type="string">
+
+Start date and time of transaction.
+
+</ResponseField>
+
+<ResponseField name="updated_at" type="string">
+
+The date and time of transaction reaching the current status.
+
+</ResponseField>
+
+<ResponseField name="completed_at" type="string">
+
+The date and time of transaction reaching completed or refunded status.
+
+</ResponseField>
+
+<ResponseField name="transfer_received_at" type="string">
+
+The date and time of receiving transfer.
+
+</ResponseField>
+
+<ResponseField name="message" type="string">
+
+Human readable explanation of transaction status
+
+</ResponseField>
+
+<ResponseField name="refunds" type="object">
+
+An object describing any on or offchain refund associated with this transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount_refunded" type="object">
+
+      The total amount refunded in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="amount_fee" type="object">
+
+      The total amount charged in fees for processing all refund payments, in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="payments" type="object[]">
+
+      A list of objects containing information on the individual payments made back as refunds.
+
+      <Expandable title="items">
+        <ResponseField name="id" type="string">
+
+          The Stellar transaction hash.
+
+        </ResponseField>
+        <ResponseField name="id_type" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="object">
+
+          The amount sent back for the payment identified by id, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="fee" type="object">
+
+          The amount charged as a fee for processing the refund, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="requested_at" type="string">
+
+          The date and time of requesting refund.
+
+        </ResponseField>
+        <ResponseField name="refunded_at" type="string">
+
+          The date and time of making refund.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+## Example
+
+Example request to the `notify_transaction_expired` method.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_transaction_expired",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Transaction expired"
+  }
+}' \
+https://platform-server.exampleanchor.com | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "notify_transaction_expired",
+  params: {
+    transaction_id: "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    message: "Transaction expired",
+  },
+};
+let res = await fetch("https://platform-server.exampleanchor.com", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://platform-server.exampleanchor.com", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "notify_transaction_expired",
+    "params": {
+        "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+        "message": "Transaction expired"
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_transaction_expired",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Transaction expired"
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "sep": "24",
+    "kind": "deposit",
+    "status": "completed",
+    "amount_expected": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_in": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_out": {
+      "amount": "0.9",
+      "asset": "iso4217:USD"
+    },
+    "fee_details": {
+      "total": "0.1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "started_at": "2023-08-04T10:04:06.280923Z",
+    "updated_at": "2023-08-04T10:04:15.716233Z",
+    "message": "Transaction complete",
+    "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
+    "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
   }
-/>
+}
+```
+
+{/* /rpc-method */}
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_on_hold.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_on_hold.mdx
index bd00841ec..7f6d973e2 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_on_hold.mdx
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_on_hold.mdx
@@ -1,15 +1,407 @@
 ---
 title: notify_transaction_on_hold
-hide_title: true
+description: "<RpcMethod"
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notify_transaction_on_hold",
-    )[0]
+`SEP-6` `SEP-24`
+
+Notify transaction is currently on hold by the anchor (e.g. compliance hold). Anchor should update message to guide user through the steps.
+
+## Params (3)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="transaction_id" type="string" required>
+
+The unique identifier of this transaction.
+
+A unique transaction identifier.
+
+</ParamField>
+
+<ParamField body="message" type="string">
+
+Human readable explanation of transaction status.
+
+A human readable message.
+
+</ParamField>
+
+<ParamField body="user_action_required_by" type="string">
+
+Time and date by which user action is required
+
+A date and time.
+
+</ParamField>
+
+## Result
+
+_(notify_transaction_on_holdResponse)_
+
+<ResponseField name="id" type="string">
+
+A unique transaction identifier.
+
+</ResponseField>
+
+<ResponseField name="sep" type="integer">
+
+Protocol of the transaction.
+
+Available options: `6`, `24`, `31`
+
+</ResponseField>
+
+<ResponseField name="kind" type="string">
+
+The kind of transaction that is desired.
+
+Available options: `undefined`, `receive`, `deposit`, `deposit-exchange`, `withdrawal`, `withdrawal-exchange`
+
+</ResponseField>
+
+<ResponseField name="status" type="string">
+
+Processing status of the transaction.
+
+Available options: `pending_anchor`, `pending_trust`, `pending_user`, `pending_user_transfer_start`, `pending_user_transfer_complete`, `incomplete`, `no_market`, `too_small`, `too_large`, `pending_sender`, `pending_receiver`, `pending_transaction_info_update`, `pending_customer_info_update`, `completed`, `refunded`, `expired`, `error`, `pending_external`, `pending_stellar`
+
+</ResponseField>
+
+<ResponseField name="amount_expected" type="object">
+
+The amount expected in the payment.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_in" type="object">
+
+Amount expected/received by anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_out" type="object">
+
+The amount expected to be sent by anchor to user at end of transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="fee_details" type="object">
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="total" type="number" required>
+    </ResponseField>
+    <ResponseField name="asset" type="string" required>
+    </ResponseField>
+    <ResponseField name="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ResponseField name="name" type="string">
+        </ResponseField>
+        <ResponseField name="description" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="number">
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="quote_id" type="string">
+
+The id returned from a SEP-38 POST /quote response
+
+</ResponseField>
+
+<ResponseField name="started_at" type="string">
+
+Start date and time of transaction.
+
+</ResponseField>
+
+<ResponseField name="updated_at" type="string">
+
+The date and time of transaction reaching the current status.
+
+</ResponseField>
+
+<ResponseField name="completed_at" type="string">
+
+The date and time of transaction reaching completed or refunded status.
+
+</ResponseField>
+
+<ResponseField name="transfer_received_at" type="string">
+
+The date and time of receiving transfer.
+
+</ResponseField>
+
+<ResponseField name="message" type="string">
+
+Human readable explanation of transaction status
+
+</ResponseField>
+
+<ResponseField name="refunds" type="object">
+
+An object describing any on or offchain refund associated with this transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount_refunded" type="object">
+
+      The total amount refunded in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="amount_fee" type="object">
+
+      The total amount charged in fees for processing all refund payments, in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="payments" type="object[]">
+
+      A list of objects containing information on the individual payments made back as refunds.
+
+      <Expandable title="items">
+        <ResponseField name="id" type="string">
+
+          The Stellar transaction hash.
+
+        </ResponseField>
+        <ResponseField name="id_type" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="object">
+
+          The amount sent back for the payment identified by id, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="fee" type="object">
+
+          The amount charged as a fee for processing the refund, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="requested_at" type="string">
+
+          The date and time of requesting refund.
+
+        </ResponseField>
+        <ResponseField name="refunded_at" type="string">
+
+          The date and time of making refund.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+## Example
+
+Example request to the `notify_transaction_on_hold` method.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_transaction_on_hold",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Transaction on hold, please contact customer service to lift the hold."
+  }
+}' \
+https://platform-server.exampleanchor.com | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "notify_transaction_on_hold",
+  params: {
+    transaction_id: "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    message:
+      "Transaction on hold, please contact customer service to lift the hold.",
+  },
+};
+let res = await fetch("https://platform-server.exampleanchor.com", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://platform-server.exampleanchor.com", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "notify_transaction_on_hold",
+    "params": {
+        "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+        "message": "Transaction on hold, please contact customer service to lift the hold."
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_transaction_on_hold",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Transaction on hold, please contact customer service to lift the hold."
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "sep": "24",
+    "kind": "deposit",
+    "status": "completed",
+    "amount_expected": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_in": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_out": {
+      "amount": "0.9",
+      "asset": "iso4217:USD"
+    },
+    "fee_details": {
+      "total": "0.1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "started_at": "2023-08-04T10:04:06.280923Z",
+    "updated_at": "2023-08-04T10:04:15.716233Z",
+    "message": "Transaction complete",
+    "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
+    "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
   }
-/>
+}
+```
+
+{/* /rpc-method */}
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_recovery.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_recovery.mdx
index d134b5393..7a5df9544 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_recovery.mdx
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_recovery.mdx
@@ -1,15 +1,398 @@
 ---
 title: notify_transaction_recovery
-hide_title: true
+description: "<RpcMethod"
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notify_transaction_recovery",
-    )[0]
+`SEP-6` `SEP-24` `SEP-31`
+
+Transaction status is changed from error / expired to pending_anchor(SEP-6 or SEP-24) or pending_receiver(SEP-31)
+
+## Params (2)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="transaction_id" type="string" required>
+
+The unique identifier of this transaction.
+
+A unique transaction identifier.
+
+</ParamField>
+
+<ParamField body="message" type="string">
+
+Human readable explanation of transaction status.
+
+A human readable message.
+
+</ParamField>
+
+## Result
+
+_(notify_transaction_recoveryResponse)_
+
+<ResponseField name="id" type="string">
+
+A unique transaction identifier.
+
+</ResponseField>
+
+<ResponseField name="sep" type="integer">
+
+Protocol of the transaction.
+
+Available options: `6`, `24`, `31`
+
+</ResponseField>
+
+<ResponseField name="kind" type="string">
+
+The kind of transaction that is desired.
+
+Available options: `undefined`, `receive`, `deposit`, `deposit-exchange`, `withdrawal`, `withdrawal-exchange`
+
+</ResponseField>
+
+<ResponseField name="status" type="string">
+
+Processing status of the transaction.
+
+Available options: `pending_anchor`, `pending_trust`, `pending_user`, `pending_user_transfer_start`, `pending_user_transfer_complete`, `incomplete`, `no_market`, `too_small`, `too_large`, `pending_sender`, `pending_receiver`, `pending_transaction_info_update`, `pending_customer_info_update`, `completed`, `refunded`, `expired`, `error`, `pending_external`, `pending_stellar`
+
+</ResponseField>
+
+<ResponseField name="amount_expected" type="object">
+
+The amount expected in the payment.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_in" type="object">
+
+Amount expected/received by anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_out" type="object">
+
+The amount expected to be sent by anchor to user at end of transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="fee_details" type="object">
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="total" type="number" required>
+    </ResponseField>
+    <ResponseField name="asset" type="string" required>
+    </ResponseField>
+    <ResponseField name="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ResponseField name="name" type="string">
+        </ResponseField>
+        <ResponseField name="description" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="number">
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="quote_id" type="string">
+
+The id returned from a SEP-38 POST /quote response
+
+</ResponseField>
+
+<ResponseField name="started_at" type="string">
+
+Start date and time of transaction.
+
+</ResponseField>
+
+<ResponseField name="updated_at" type="string">
+
+The date and time of transaction reaching the current status.
+
+</ResponseField>
+
+<ResponseField name="completed_at" type="string">
+
+The date and time of transaction reaching completed or refunded status.
+
+</ResponseField>
+
+<ResponseField name="transfer_received_at" type="string">
+
+The date and time of receiving transfer.
+
+</ResponseField>
+
+<ResponseField name="message" type="string">
+
+Human readable explanation of transaction status
+
+</ResponseField>
+
+<ResponseField name="refunds" type="object">
+
+An object describing any on or offchain refund associated with this transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount_refunded" type="object">
+
+      The total amount refunded in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="amount_fee" type="object">
+
+      The total amount charged in fees for processing all refund payments, in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="payments" type="object[]">
+
+      A list of objects containing information on the individual payments made back as refunds.
+
+      <Expandable title="items">
+        <ResponseField name="id" type="string">
+
+          The Stellar transaction hash.
+
+        </ResponseField>
+        <ResponseField name="id_type" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="object">
+
+          The amount sent back for the payment identified by id, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="fee" type="object">
+
+          The amount charged as a fee for processing the refund, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="requested_at" type="string">
+
+          The date and time of requesting refund.
+
+        </ResponseField>
+        <ResponseField name="refunded_at" type="string">
+
+          The date and time of making refund.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+## Example
+
+Example request to the `notify_transaction_recovery` method.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_transaction_recovery",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Transaction recovered"
+  }
+}' \
+https://platform-server.exampleanchor.com | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "notify_transaction_recovery",
+  params: {
+    transaction_id: "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    message: "Transaction recovered",
+  },
+};
+let res = await fetch("https://platform-server.exampleanchor.com", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://platform-server.exampleanchor.com", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "notify_transaction_recovery",
+    "params": {
+        "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+        "message": "Transaction recovered"
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_transaction_recovery",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Transaction recovered"
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "sep": "24",
+    "kind": "deposit",
+    "status": "completed",
+    "amount_expected": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_in": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_out": {
+      "amount": "0.9",
+      "asset": "iso4217:USD"
+    },
+    "fee_details": {
+      "total": "0.1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "started_at": "2023-08-04T10:04:06.280923Z",
+    "updated_at": "2023-08-04T10:04:15.716233Z",
+    "message": "Transaction complete",
+    "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
+    "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
   }
-/>
+}
+```
+
+{/* /rpc-method */}
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_trust_set.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_trust_set.mdx
index 5968934e5..559b485b1 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_trust_set.mdx
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_trust_set.mdx
@@ -1,11 +1,404 @@
 ---
 title: notify_trust_set
-hide_title: true
+description: "<RpcMethod"
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "notify_trust_set")[0]}
-/>
+`SEP-6` `SEP-24`
+
+The user has added a trustline for the asset
+
+## Params (3)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="transaction_id" type="string" required>
+
+The unique identifier of this transaction.
+
+A unique transaction identifier.
+
+</ParamField>
+
+<ParamField body="message" type="string">
+
+Human readable explanation of transaction status.
+
+A human readable message.
+
+</ParamField>
+
+<ParamField body="success" type="boolean">
+
+Flag which indicates if trustline was configured by user.
+
+</ParamField>
+
+## Result
+
+_(notify_trust_setResponse)_
+
+<ResponseField name="id" type="string">
+
+A unique transaction identifier.
+
+</ResponseField>
+
+<ResponseField name="sep" type="integer">
+
+Protocol of the transaction.
+
+Available options: `6`, `24`, `31`
+
+</ResponseField>
+
+<ResponseField name="kind" type="string">
+
+The kind of transaction that is desired.
+
+Available options: `undefined`, `receive`, `deposit`, `deposit-exchange`, `withdrawal`, `withdrawal-exchange`
+
+</ResponseField>
+
+<ResponseField name="status" type="string">
+
+Processing status of the transaction.
+
+Available options: `pending_anchor`, `pending_trust`, `pending_user`, `pending_user_transfer_start`, `pending_user_transfer_complete`, `incomplete`, `no_market`, `too_small`, `too_large`, `pending_sender`, `pending_receiver`, `pending_transaction_info_update`, `pending_customer_info_update`, `completed`, `refunded`, `expired`, `error`, `pending_external`, `pending_stellar`
+
+</ResponseField>
+
+<ResponseField name="amount_expected" type="object">
+
+The amount expected in the payment.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_in" type="object">
+
+Amount expected/received by anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_out" type="object">
+
+The amount expected to be sent by anchor to user at end of transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="fee_details" type="object">
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="total" type="number" required>
+    </ResponseField>
+    <ResponseField name="asset" type="string" required>
+    </ResponseField>
+    <ResponseField name="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ResponseField name="name" type="string">
+        </ResponseField>
+        <ResponseField name="description" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="number">
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="quote_id" type="string">
+
+The id returned from a SEP-38 POST /quote response
+
+</ResponseField>
+
+<ResponseField name="started_at" type="string">
+
+Start date and time of transaction.
+
+</ResponseField>
+
+<ResponseField name="updated_at" type="string">
+
+The date and time of transaction reaching the current status.
+
+</ResponseField>
+
+<ResponseField name="completed_at" type="string">
+
+The date and time of transaction reaching completed or refunded status.
+
+</ResponseField>
+
+<ResponseField name="transfer_received_at" type="string">
+
+The date and time of receiving transfer.
+
+</ResponseField>
+
+<ResponseField name="message" type="string">
+
+Human readable explanation of transaction status
+
+</ResponseField>
+
+<ResponseField name="refunds" type="object">
+
+An object describing any on or offchain refund associated with this transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount_refunded" type="object">
+
+      The total amount refunded in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="amount_fee" type="object">
+
+      The total amount charged in fees for processing all refund payments, in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="payments" type="object[]">
+
+      A list of objects containing information on the individual payments made back as refunds.
+
+      <Expandable title="items">
+        <ResponseField name="id" type="string">
+
+          The Stellar transaction hash.
+
+        </ResponseField>
+        <ResponseField name="id_type" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="object">
+
+          The amount sent back for the payment identified by id, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="fee" type="object">
+
+          The amount charged as a fee for processing the refund, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="requested_at" type="string">
+
+          The date and time of requesting refund.
+
+        </ResponseField>
+        <ResponseField name="refunded_at" type="string">
+
+          The date and time of making refund.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+## Example
+
+Example request to the `notify_trust_set` method.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_trust_set",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Trustline set"
+  }
+}' \
+https://platform-server.exampleanchor.com | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "notify_trust_set",
+  params: {
+    transaction_id: "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    message: "Trustline set",
+  },
+};
+let res = await fetch("https://platform-server.exampleanchor.com", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://platform-server.exampleanchor.com", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "notify_trust_set",
+    "params": {
+        "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+        "message": "Trustline set"
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "notify_trust_set",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Trustline set"
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "sep": "24",
+    "kind": "deposit",
+    "status": "completed",
+    "amount_expected": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_in": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_out": {
+      "amount": "0.9",
+      "asset": "iso4217:USD"
+    },
+    "fee_details": {
+      "total": "0.1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "started_at": "2023-08-04T10:04:06.280923Z",
+    "updated_at": "2023-08-04T10:04:15.716233Z",
+    "message": "Transaction complete",
+    "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
+    "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
+  }
+}
+```
+
+{/* /rpc-method */}
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_offchain_funds.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_offchain_funds.mdx
index 7066f66bb..2719d924d 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_offchain_funds.mdx
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_offchain_funds.mdx
@@ -1,13 +1,593 @@
 ---
 title: request_offchain_funds
-hide_title: true
+description: "<RpcMethod"
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={
-    rpcSpec.methods.filter((meth) => meth.name === "request_offchain_funds")[0]
+`SEP-6` `SEP-24`
+
+The user has to initiate transfer to the anchor
+
+## Params (8)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="transaction_id" type="string" required>
+
+The unique identifier of this transaction.
+
+A unique transaction identifier.
+
+</ParamField>
+
+<ParamField body="message" type="string">
+
+Human readable explanation of transaction status.
+
+A human readable message.
+
+</ParamField>
+
+<ParamField body="amount_in" type="object" required>
+
+The amount expected in the payment
+
+  <Expandable title="properties">
+    <ParamField body="amount" type="string" required>
+
+      A numerical representation of an amount of some asset.
+
+    </ParamField>
+    <ParamField body="asset" type="string" required>
+
+      The asset to be received by the Anchor
+
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+<ParamField body="amount_out" type="object">
+
+This is required if the transaction is associated with a firm quote and for transactions where `amount_in.asset` and `amount_out.asset` are the same.
+
+  <Expandable title="properties">
+    <ParamField body="amount" type="string" required>
+
+      A numerical representation of an amount of some asset.
+
+    </ParamField>
+    <ParamField body="asset" type="string" required>
+
+      The asset to be sent by anchor to user at end of transaction
+
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+<ParamField body="fee_details" type="object" required>
+
+Description of fees charged by the anchor
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ParamField body="total" type="number" required>
+    </ParamField>
+    <ParamField body="asset" type="string" required>
+    </ParamField>
+    <ParamField body="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ParamField body="name" type="string">
+        </ParamField>
+        <ParamField body="description" type="string">
+        </ParamField>
+        <ParamField body="amount" type="number">
+        </ParamField>
+      </Expandable>
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+<ParamField body="amount_expected" type="object">
+
+The amount expected in the payment
+
+  <Expandable title="properties">
+    <ParamField body="amount" type="string" required>
+
+      A numerical representation of an amount of some asset.
+
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+<ParamField body="user_action_required_by" type="string">
+
+Time and date by which user action is required
+
+A date and time.
+
+</ParamField>
+
+<ParamField body="instructions" type="object">
+
+A set of SEP-9 fields that describe how the user can complete the offchain deposit
+
+</ParamField>
+
+## Result
+
+_(request_offchain_fundsResponse)_
+
+<ResponseField name="id" type="string">
+
+A unique transaction identifier.
+
+</ResponseField>
+
+<ResponseField name="sep" type="integer">
+
+Protocol of the transaction.
+
+Available options: `6`, `24`, `31`
+
+</ResponseField>
+
+<ResponseField name="kind" type="string">
+
+The kind of transaction that is desired.
+
+Available options: `undefined`, `receive`, `deposit`, `deposit-exchange`, `withdrawal`, `withdrawal-exchange`
+
+</ResponseField>
+
+<ResponseField name="status" type="string">
+
+Processing status of the transaction.
+
+Available options: `pending_anchor`, `pending_trust`, `pending_user`, `pending_user_transfer_start`, `pending_user_transfer_complete`, `incomplete`, `no_market`, `too_small`, `too_large`, `pending_sender`, `pending_receiver`, `pending_transaction_info_update`, `pending_customer_info_update`, `completed`, `refunded`, `expired`, `error`, `pending_external`, `pending_stellar`
+
+</ResponseField>
+
+<ResponseField name="amount_expected" type="object">
+
+The amount expected in the payment.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_in" type="object">
+
+Amount expected/received by anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_out" type="object">
+
+The amount expected to be sent by anchor to user at end of transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="fee_details" type="object">
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="total" type="number" required>
+    </ResponseField>
+    <ResponseField name="asset" type="string" required>
+    </ResponseField>
+    <ResponseField name="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ResponseField name="name" type="string">
+        </ResponseField>
+        <ResponseField name="description" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="number">
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="quote_id" type="string">
+
+The id returned from a SEP-38 POST /quote response
+
+</ResponseField>
+
+<ResponseField name="started_at" type="string">
+
+Start date and time of transaction.
+
+</ResponseField>
+
+<ResponseField name="updated_at" type="string">
+
+The date and time of transaction reaching the current status.
+
+</ResponseField>
+
+<ResponseField name="completed_at" type="string">
+
+The date and time of transaction reaching completed or refunded status.
+
+</ResponseField>
+
+<ResponseField name="transfer_received_at" type="string">
+
+The date and time of receiving transfer.
+
+</ResponseField>
+
+<ResponseField name="message" type="string">
+
+Human readable explanation of transaction status
+
+</ResponseField>
+
+<ResponseField name="refunds" type="object">
+
+An object describing any on or offchain refund associated with this transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount_refunded" type="object">
+
+      The total amount refunded in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="amount_fee" type="object">
+
+      The total amount charged in fees for processing all refund payments, in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="payments" type="object[]">
+
+      A list of objects containing information on the individual payments made back as refunds.
+
+      <Expandable title="items">
+        <ResponseField name="id" type="string">
+
+          The Stellar transaction hash.
+
+        </ResponseField>
+        <ResponseField name="id_type" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="object">
+
+          The amount sent back for the payment identified by id, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="fee" type="object">
+
+          The amount charged as a fee for processing the refund, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="requested_at" type="string">
+
+          The date and time of requesting refund.
+
+        </ResponseField>
+        <ResponseField name="refunded_at" type="string">
+
+          The date and time of making refund.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+## Example
+
+Example request to the `request_offchain_funds` method.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "request_offchain_funds",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Request offchain funds",
+    "amount_in": {
+      "amount": 1,
+      "asset": "iso4217:USD"
+    },
+    "amount_out": {
+      "amount": 0.9,
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "fee_details": {
+      "total": 0.1,
+      "asset": "iso4217:USD"
+    },
+    "amount_expected": {
+      "amount": 1
+    },
+    "instructions": {
+      "organization.bank_number": {
+        "value": "123456789",
+        "description": "US Bank routing number"
+      },
+      "organization.bank_account_number": {
+        "value": "123456789",
+        "description": "US Bank account number"
+      }
+    }
+  }
+}' \
+https://platform-server.exampleanchor.com | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "request_offchain_funds",
+  params: {
+    transaction_id: "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    message: "Request offchain funds",
+    amount_in: {
+      amount: 1,
+      asset: "iso4217:USD",
+    },
+    amount_out: {
+      amount: 0.9,
+      asset:
+        "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5",
+    },
+    fee_details: {
+      total: 0.1,
+      asset: "iso4217:USD",
+    },
+    amount_expected: {
+      amount: 1,
+    },
+    instructions: {
+      "organization.bank_number": {
+        value: "123456789",
+        description: "US Bank routing number",
+      },
+      "organization.bank_account_number": {
+        value: "123456789",
+        description: "US Bank account number",
+      },
+    },
+  },
+};
+let res = await fetch("https://platform-server.exampleanchor.com", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://platform-server.exampleanchor.com", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "request_offchain_funds",
+    "params": {
+        "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+        "message": "Request offchain funds",
+        "amount_in": {
+            "amount": 1,
+            "asset": "iso4217:USD"
+        },
+        "amount_out": {
+            "amount": 0.9,
+            "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+        },
+        "fee_details": {
+            "total": 0.1,
+            "asset": "iso4217:USD"
+        },
+        "amount_expected": {
+            "amount": 1
+        },
+        "instructions": {
+            "organization.bank_number": {
+                "value": "123456789",
+                "description": "US Bank routing number"
+            },
+            "organization.bank_account_number": {
+                "value": "123456789",
+                "description": "US Bank account number"
+            }
+        }
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "request_offchain_funds",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Request offchain funds",
+    "amount_in": {
+      "amount": 1,
+      "asset": "iso4217:USD"
+    },
+    "amount_out": {
+      "amount": 0.9,
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "fee_details": {
+      "total": 0.1,
+      "asset": "iso4217:USD"
+    },
+    "amount_expected": {
+      "amount": 1
+    },
+    "instructions": {
+      "organization.bank_number": {
+        "value": "123456789",
+        "description": "US Bank routing number"
+      },
+      "organization.bank_account_number": {
+        "value": "123456789",
+        "description": "US Bank account number"
+      }
+    }
   }
-/>
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "sep": "24",
+    "kind": "deposit",
+    "status": "completed",
+    "amount_expected": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_in": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_out": {
+      "amount": "0.9",
+      "asset": "iso4217:USD"
+    },
+    "fee_details": {
+      "total": "0.1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "started_at": "2023-08-04T10:04:06.280923Z",
+    "updated_at": "2023-08-04T10:04:15.716233Z",
+    "message": "Transaction complete",
+    "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
+    "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
+  }
+}
+```
+
+{/* /rpc-method */}
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_onchain_funds.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_onchain_funds.mdx
index 6c14cd105..fe984917b 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_onchain_funds.mdx
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_onchain_funds.mdx
@@ -1,13 +1,585 @@
 ---
 title: request_onchain_funds
-hide_title: true
+description: "<RpcMethod"
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={
-    rpcSpec.methods.filter((meth) => meth.name === "request_onchain_funds")[0]
+`SEP-6` `SEP-24` `SEP-31`
+
+The user has to initiate transfer to the anchor
+
+## Params (11)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="transaction_id" type="string" required>
+
+The unique identifier of this transaction.
+
+A unique transaction identifier.
+
+</ParamField>
+
+<ParamField body="message" type="string">
+
+Human readable explanation of transaction status.
+
+A human readable message.
+
+</ParamField>
+
+<ParamField body="amount_in" type="object" required>
+
+The amount expected in the payment
+
+  <Expandable title="properties">
+    <ParamField body="amount" type="string" required>
+
+      A numerical representation of an amount of some asset.
+
+    </ParamField>
+    <ParamField body="asset" type="string" required>
+
+      The asset to be received by the Anchor
+
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+<ParamField body="amount_out" type="object" required>
+
+Amount sent by anchor to user
+
+  <Expandable title="properties">
+    <ParamField body="amount" type="string" required>
+
+      A numerical representation of an amount of some asset.
+
+    </ParamField>
+    <ParamField body="asset" type="string" required>
+
+      The asset to be sent by anchor to user at end of transaction
+
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+<ParamField body="amount_out" type="object">
+
+This is required if the transaction is associated with a firm quote and for transactions where `amount_in.asset` and `amount_out.asset` are the same.
+
+  <Expandable title="properties">
+    <ParamField body="amount" type="string" required>
+
+      A numerical representation of an amount of some asset.
+
+    </ParamField>
+    <ParamField body="asset" type="string" required>
+
+      The asset to be sent by anchor to user at end of transaction
+
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+<ParamField body="fee_details" type="object" required>
+
+Description of fees charged by the anchor
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ParamField body="total" type="number" required>
+    </ParamField>
+    <ParamField body="asset" type="string" required>
+    </ParamField>
+    <ParamField body="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ParamField body="name" type="string">
+        </ParamField>
+        <ParamField body="description" type="string">
+        </ParamField>
+        <ParamField body="amount" type="number">
+        </ParamField>
+      </Expandable>
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+<ParamField body="amount_expected" type="object">
+
+The amount expected in the payment
+
+  <Expandable title="properties">
+    <ParamField body="amount" type="string" required>
+
+      A numerical representation of an amount of some asset.
+
+    </ParamField>
+
+  </Expandable>
+</ParamField>
+
+<ParamField body="destination_account" type="string">
+
+Destination account
+
+</ParamField>
+
+<ParamField body="memo" type="string">
+
+Value of memo to attach to transaction
+
+</ParamField>
+
+<ParamField body="memo_type" type="string">
+
+Type of memo that anchor should attach to the transaction
+
+</ParamField>
+
+<ParamField body="user_action_required_by" type="string">
+
+Time and date by which user action is required
+
+A date and time.
+
+</ParamField>
+
+## Result
+
+_(request_onchain_fundsResponse)_
+
+<ResponseField name="id" type="string">
+
+A unique transaction identifier.
+
+</ResponseField>
+
+<ResponseField name="sep" type="integer">
+
+Protocol of the transaction.
+
+Available options: `6`, `24`, `31`
+
+</ResponseField>
+
+<ResponseField name="kind" type="string">
+
+The kind of transaction that is desired.
+
+Available options: `undefined`, `receive`, `deposit`, `deposit-exchange`, `withdrawal`, `withdrawal-exchange`
+
+</ResponseField>
+
+<ResponseField name="status" type="string">
+
+Processing status of the transaction.
+
+Available options: `pending_anchor`, `pending_trust`, `pending_user`, `pending_user_transfer_start`, `pending_user_transfer_complete`, `incomplete`, `no_market`, `too_small`, `too_large`, `pending_sender`, `pending_receiver`, `pending_transaction_info_update`, `pending_customer_info_update`, `completed`, `refunded`, `expired`, `error`, `pending_external`, `pending_stellar`
+
+</ResponseField>
+
+<ResponseField name="amount_expected" type="object">
+
+The amount expected in the payment.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_in" type="object">
+
+Amount expected/received by anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_out" type="object">
+
+The amount expected to be sent by anchor to user at end of transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="fee_details" type="object">
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="total" type="number" required>
+    </ResponseField>
+    <ResponseField name="asset" type="string" required>
+    </ResponseField>
+    <ResponseField name="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ResponseField name="name" type="string">
+        </ResponseField>
+        <ResponseField name="description" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="number">
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="quote_id" type="string">
+
+The id returned from a SEP-38 POST /quote response
+
+</ResponseField>
+
+<ResponseField name="started_at" type="string">
+
+Start date and time of transaction.
+
+</ResponseField>
+
+<ResponseField name="updated_at" type="string">
+
+The date and time of transaction reaching the current status.
+
+</ResponseField>
+
+<ResponseField name="completed_at" type="string">
+
+The date and time of transaction reaching completed or refunded status.
+
+</ResponseField>
+
+<ResponseField name="transfer_received_at" type="string">
+
+The date and time of receiving transfer.
+
+</ResponseField>
+
+<ResponseField name="message" type="string">
+
+Human readable explanation of transaction status
+
+</ResponseField>
+
+<ResponseField name="refunds" type="object">
+
+An object describing any on or offchain refund associated with this transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount_refunded" type="object">
+
+      The total amount refunded in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="amount_fee" type="object">
+
+      The total amount charged in fees for processing all refund payments, in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="payments" type="object[]">
+
+      A list of objects containing information on the individual payments made back as refunds.
+
+      <Expandable title="items">
+        <ResponseField name="id" type="string">
+
+          The Stellar transaction hash.
+
+        </ResponseField>
+        <ResponseField name="id_type" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="object">
+
+          The amount sent back for the payment identified by id, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="fee" type="object">
+
+          The amount charged as a fee for processing the refund, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="requested_at" type="string">
+
+          The date and time of requesting refund.
+
+        </ResponseField>
+        <ResponseField name="refunded_at" type="string">
+
+          The date and time of making refund.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+## Example
+
+Example request to the `request_onchain_funds` method.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "request_onchain_funds",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Requesting onchain funds",
+    "amount_in": {
+      "amount": 1,
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_out": {
+      "amount": 0.9,
+      "asset": "iso4217:USD"
+    },
+    "fee_details": {
+      "total": 0.1,
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_expected": {
+      "amount": 1
+    }
+  }
+}' \
+https://platform-server.exampleanchor.com | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "request_onchain_funds",
+  params: {
+    transaction_id: "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    message: "Requesting onchain funds",
+    amount_in: {
+      amount: 1,
+      asset:
+        "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5",
+    },
+    amount_out: {
+      amount: 0.9,
+      asset: "iso4217:USD",
+    },
+    fee_details: {
+      total: 0.1,
+      asset:
+        "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5",
+    },
+    amount_expected: {
+      amount: 1,
+    },
+  },
+};
+let res = await fetch("https://platform-server.exampleanchor.com", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://platform-server.exampleanchor.com", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "request_onchain_funds",
+    "params": {
+        "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+        "message": "Requesting onchain funds",
+        "amount_in": {
+            "amount": 1,
+            "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+        },
+        "amount_out": {
+            "amount": 0.9,
+            "asset": "iso4217:USD"
+        },
+        "fee_details": {
+            "total": 0.1,
+            "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+        },
+        "amount_expected": {
+            "amount": 1
+        }
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "request_onchain_funds",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Requesting onchain funds",
+    "amount_in": {
+      "amount": 1,
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_out": {
+      "amount": 0.9,
+      "asset": "iso4217:USD"
+    },
+    "fee_details": {
+      "total": 0.1,
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_expected": {
+      "amount": 1
+    }
   }
-/>
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "sep": "24",
+    "kind": "deposit",
+    "status": "completed",
+    "amount_expected": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_in": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_out": {
+      "amount": "0.9",
+      "asset": "iso4217:USD"
+    },
+    "fee_details": {
+      "total": "0.1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "started_at": "2023-08-04T10:04:06.280923Z",
+    "updated_at": "2023-08-04T10:04:15.716233Z",
+    "message": "Transaction complete",
+    "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
+    "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
+  }
+}
+```
+
+{/* /rpc-method */}
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_trust.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_trust.mdx
index 62a368d0a..436f0cf46 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_trust.mdx
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_trust.mdx
@@ -1,11 +1,406 @@
 ---
 title: request_trust
-hide_title: true
+description: "<RpcMethod"
 ---
 
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
+{/* rpc-method: generated from the OpenRPC spec */}
 
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "request_trust")[0]}
-/>
+`SEP-6` `SEP-24`
+
+The user must add a trustline for the asset to complete
+
+## Params (3)
+
+<Tip>
+
+Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments in a by-position array
+
+</Tip>
+
+<ParamField body="transaction_id" type="string" required>
+
+The unique identifier of this transaction.
+
+A unique transaction identifier.
+
+</ParamField>
+
+<ParamField body="message" type="string">
+
+Human readable explanation of transaction status.
+
+A human readable message.
+
+</ParamField>
+
+<ParamField body="user_action_required_by" type="string">
+
+Time and date by which user action is required
+
+A date and time.
+
+</ParamField>
+
+## Result
+
+_(request_trustResponse)_
+
+<ResponseField name="id" type="string">
+
+A unique transaction identifier.
+
+</ResponseField>
+
+<ResponseField name="sep" type="integer">
+
+Protocol of the transaction.
+
+Available options: `6`, `24`, `31`
+
+</ResponseField>
+
+<ResponseField name="kind" type="string">
+
+The kind of transaction that is desired.
+
+Available options: `undefined`, `receive`, `deposit`, `deposit-exchange`, `withdrawal`, `withdrawal-exchange`
+
+</ResponseField>
+
+<ResponseField name="status" type="string">
+
+Processing status of the transaction.
+
+Available options: `pending_anchor`, `pending_trust`, `pending_user`, `pending_user_transfer_start`, `pending_user_transfer_complete`, `incomplete`, `no_market`, `too_small`, `too_large`, `pending_sender`, `pending_receiver`, `pending_transaction_info_update`, `pending_customer_info_update`, `completed`, `refunded`, `expired`, `error`, `pending_external`, `pending_stellar`
+
+</ResponseField>
+
+<ResponseField name="amount_expected" type="object">
+
+The amount expected in the payment.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_in" type="object">
+
+Amount expected/received by anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="amount_out" type="object">
+
+The amount expected to be sent by anchor to user at end of transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount" type="string">
+
+      A stringified amount of an asset.
+
+    </ResponseField>
+    <ResponseField name="asset" type="string">
+
+      An asset.
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="fee_details" type="object">
+
+Description of fee charged by the anchor.
+
+  <Expandable title="properties">
+    <ResponseField name="total" type="number" required>
+    </ResponseField>
+    <ResponseField name="asset" type="string" required>
+    </ResponseField>
+    <ResponseField name="details" type="object[]">
+
+      Details about fee charged.
+
+      <Expandable title="items">
+        <ResponseField name="name" type="string">
+        </ResponseField>
+        <ResponseField name="description" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="number">
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+<ResponseField name="quote_id" type="string">
+
+The id returned from a SEP-38 POST /quote response
+
+</ResponseField>
+
+<ResponseField name="started_at" type="string">
+
+Start date and time of transaction.
+
+</ResponseField>
+
+<ResponseField name="updated_at" type="string">
+
+The date and time of transaction reaching the current status.
+
+</ResponseField>
+
+<ResponseField name="completed_at" type="string">
+
+The date and time of transaction reaching completed or refunded status.
+
+</ResponseField>
+
+<ResponseField name="transfer_received_at" type="string">
+
+The date and time of receiving transfer.
+
+</ResponseField>
+
+<ResponseField name="message" type="string">
+
+Human readable explanation of transaction status
+
+</ResponseField>
+
+<ResponseField name="refunds" type="object">
+
+An object describing any on or offchain refund associated with this transaction.
+
+  <Expandable title="properties">
+    <ResponseField name="amount_refunded" type="object">
+
+      The total amount refunded in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="amount_fee" type="object">
+
+      The total amount charged in fees for processing all refund payments, in units of amount_in_asset.
+
+      <Expandable title="properties">
+        <ResponseField name="amount" type="string">
+
+          A numerical representation of an amount of some asset.
+
+        </ResponseField>
+        <ResponseField name="asset" type="string">
+
+          An asset.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+    <ResponseField name="payments" type="object[]">
+
+      A list of objects containing information on the individual payments made back as refunds.
+
+      <Expandable title="items">
+        <ResponseField name="id" type="string">
+
+          The Stellar transaction hash.
+
+        </ResponseField>
+        <ResponseField name="id_type" type="string">
+        </ResponseField>
+        <ResponseField name="amount" type="object">
+
+          The amount sent back for the payment identified by id, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="fee" type="object">
+
+          The amount charged as a fee for processing the refund, in units of amount_in_asset.
+
+          <Expandable title="properties">
+            <ResponseField name="amount" type="string">
+
+              A numerical representation of an amount of some asset.
+
+            </ResponseField>
+            <ResponseField name="asset" type="string">
+
+              An asset.
+
+            </ResponseField>
+          </Expandable>
+        </ResponseField>
+        <ResponseField name="requested_at" type="string">
+
+          The date and time of requesting refund.
+
+        </ResponseField>
+        <ResponseField name="refunded_at" type="string">
+
+          The date and time of making refund.
+
+        </ResponseField>
+      </Expandable>
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
+
+## Example
+
+Example request to the `request_trust` method.
+
+**Request**
+
+<CodeGroup>
+
+```bash cURL
+curl -X POST \
+-H 'Content-Type: application/json' \
+-d '{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "request_trust",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Request trust"
+  }
+}' \
+https://platform-server.exampleanchor.com | jq
+```
+
+```js JavaScript
+let requestBody = {
+  jsonrpc: "2.0",
+  id: 8675309,
+  method: "request_trust",
+  params: {
+    transaction_id: "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    message: "Request trust",
+  },
+};
+let res = await fetch("https://platform-server.exampleanchor.com", {
+  method: "POST",
+  headers: {
+    "Content-Type": "application/json",
+  },
+  body: JSON.stringify(requestBody),
+});
+let json = await res.json();
+console.log(json);
+```
+
+```python Python
+import json, requests
+res = requests.post("https://platform-server.exampleanchor.com", json={
+    "jsonrpc": "2.0",
+    "id": 8675309,
+    "method": "request_trust",
+    "params": {
+        "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+        "message": "Request trust"
+    }
+})
+print(json.dumps(res.json(), indent=4))
+```
+
+```json JSON
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "method": "request_trust",
+  "params": {
+    "transaction_id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "message": "Request trust"
+  }
+}
+```
+
+</CodeGroup>
+
+**Result**
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 8675309,
+  "result": {
+    "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
+    "sep": "24",
+    "kind": "deposit",
+    "status": "completed",
+    "amount_expected": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_in": {
+      "amount": "1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "amount_out": {
+      "amount": "0.9",
+      "asset": "iso4217:USD"
+    },
+    "fee_details": {
+      "total": "0.1",
+      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
+    },
+    "started_at": "2023-08-04T10:04:06.280923Z",
+    "updated_at": "2023-08-04T10:04:15.716233Z",
+    "message": "Transaction complete",
+    "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
+    "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
+  }
+}
+```
+
+{/* /rpc-method */}
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/overview.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/overview.mdx
index 544a5413e..1a0acf49d 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/overview.mdx
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/overview.mdx
@@ -1,16 +1,16 @@
 ---
 title: Overview
-sidebar_position: 10
+description: "JSON-RPC is a stateless, light-weight remote procedure call (RPC) protocol."
 ---
 
 JSON-RPC is a stateless, light-weight remote procedure call (RPC) protocol.
 
 It's simple and easy to use, as it uses a single HTTP endpoint and a JSON object that contains the method name and parameters. It is transport agnostic in that the concepts can be used within the same process, over sockets, over http, or in many various message passing environments. It uses [JSON](http://www.json.org) ([RFC 4627](http://www.ietf.org/rfc/rfc4627.txt)) as data format.
 
-:::note
+<Note>
 
 All member names exchanged between the Client and the Server that are considered for matching of any kind should be considered to be case-sensitive.
 
-:::
+</Note>
 
 You can read more about JSON-RPC protocol [here](https://www.jsonrpc.org/specification).
diff --git a/docs/platforms/anchor-platform/api-reference/platform/transactions/README.mdx b/docs/platforms/anchor-platform/api-reference/platform/transactions/README.mdx
deleted file mode 100644
index 8bedab7d1..000000000
--- a/docs/platforms/anchor-platform/api-reference/platform/transactions/README.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: Transactions
-sidebar_position: 10
----
-
-Transactions are representations of a SEP transaction. It holds information about the protocol being used, and all necessary information passed by an external party (such as wallet or an anchor).
-
-Should not be confused with stellar [transactions](../../../../../learn/glossary.mdx#transaction).
-
-<EndpointsTable title="Endpoints">
-
-|     |                                              |
-| --- | -------------------------------------------- |
-| GET | [/transactions/:id](get-transaction.api.mdx) |
-| GET | [/transactions/](./get-transactions.api.mdx) |
-
-</EndpointsTable>
diff --git a/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transaction.ParamsDetails.json b/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transaction.ParamsDetails.json
deleted file mode 100644
index d243feae6..000000000
--- a/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transaction.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"in":"path","name":"id","required":true,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transaction.RequestSchema.json b/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transaction.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transaction.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transaction.StatusCodes.json b/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transaction.StatusCodes.json
deleted file mode 100644
index ebfd5f4c9..000000000
--- a/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transaction.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Transaction found.","content":{"application/json":{"schema":{"oneOf":[{"type":"object","required":["id","sep","kind","status","started_at"],"properties":{"id":{"type":"string"},"sep":{"type":"string","enum":["6"]},"kind":{"type":"string","enum":["deposit","deposit-exchange","withdrawal","withdrawal-exchange"]},"status":{"type":"string","description":"Possible status value for SEP-6 transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_customer_info_update","pending_user_transfer_start","pending_user_transfer_complete","pending_anchor","pending_trust","pending_user","no_market","too_small","too_large"],"title":"StatusSEP6"},"type":{"type":"string","description":"The method the user used to deposit or withdraw offchain funds."},"amount_expected":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_in":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_out":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee_details":{"type":"object","required":["total","asset"],"properties":{"total":{"type":"string"},"asset":{"type":"string"},"details":{"type":"array","items":{"type":"object","required":["name","amount"],"properties":{"name":{"type":"string"},"amount":{"type":"string"},"description":{"type":"string"}},"title":"FeeDescription"}}},"title":"FeeDetails"},"quote_id":{"type":"string"},"started_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"completed_at":{"type":"string","format":"date-time"},"transfer_received_at":{"type":"string","format":"date-time"},"user_action_required_by":{"type":"string","format":"date-time"},"message":{"type":"string"},"refunds":{"type":"object","properties":{"amount_refunded":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"payments":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string"},"id_type":{"type":"string","enum":["stellar","external"]},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"requested_at":{"type":"string","format":"date-time"},"refunded_at":{"type":"string","format":"date-time"}}}}},"title":"Refunds"},"stellar_transactions":{"type":"array","items":{"type":"object","required":["id","created_at","envelope","payments"],"properties":{"id":{"type":"string","description":"The ID of the transaction in the Stellar network."},"memo":{"type":"string","description":"The memo of the transaction in the Stellar network."},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text","hash","id"]},"created_at":{"type":"string","format":"date-time","description":"The time the transaction was registered in the Stellar network."},"envelope":{"type":"string","description":"The transaction envelope, containing all the transaction information."},"payments":{"type":"array","items":{"type":"object","required":["id","payment_type","source_account","destination_account","amount"],"properties":{"id":{"type":"string","description":"The ID of the payment in the Stellar Network."},"payment_type":{"type":"string","description":"The type of payment in the Stellar Network.","enum":["payment","path_payment"],"default":"payment"},"source_account":{"type":"string","description":"The account being debited in the Stellar Network."},"destination_account":{"type":"string","description":"The account being credited in the Stellar Network."},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"}}}}},"title":"StellarTransaction"}},"source_account":{"type":"string"},"destination_account":{"type":"string"},"external_transaction_id":{"type":"string"},"memo":{"type":"string"},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"refund_memo":{"type":"string","description":"If provided, this memo should be used for refund transactions."},"refund_memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"client_domain":{"type":"string"},"client_name":{"type":"string"},"customers":{"type":"object","description":"The user that initiated the transaction is both the sender and receiver.\n","properties":{"sender":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"receiver":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}}},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}},"title":"TransactionSEP6"},{"type":"object","required":["id","sep","kind","status","amount_expected","destination_account","started_at"],"properties":{"id":{"type":"string"},"sep":{"type":"string","enum":["24"]},"kind":{"type":"string","enum":["deposit","withdrawal"]},"status":{"type":"string","description":"Possible status value for SEP-24 transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_user_transfer_start","pending_user_transfer_complete","pending_anchor","pending_trust","pending_user","no_market","too_small","too_large"],"title":"StatusSEP24"},"type":{"type":"string","description":"This field is always empty for SEP-24 transactions."},"amount_expected":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_in":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_out":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee_details":{"type":"object","required":["total","asset"],"properties":{"total":{"type":"string"},"asset":{"type":"string"},"details":{"type":"array","items":{"type":"object","required":["name","amount"],"properties":{"name":{"type":"string"},"amount":{"type":"string"},"description":{"type":"string"}},"title":"FeeDescription"}}},"title":"FeeDetails"},"quote_id":{"type":"string"},"started_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"completed_at":{"type":"string","format":"date-time"},"transfer_received_at":{"type":"string","format":"date-time"},"user_action_required_by":{"type":"string","format":"date-time"},"message":{"type":"string"},"refunds":{"type":"object","properties":{"amount_refunded":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"payments":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string"},"id_type":{"type":"string","enum":["stellar","external"]},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"requested_at":{"type":"string","format":"date-time"},"refunded_at":{"type":"string","format":"date-time"}}}}},"title":"Refunds"},"stellar_transactions":{"type":"array","items":{"type":"object","required":["id","created_at","envelope","payments"],"properties":{"id":{"type":"string","description":"The ID of the transaction in the Stellar network."},"memo":{"type":"string","description":"The memo of the transaction in the Stellar network."},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text","hash","id"]},"created_at":{"type":"string","format":"date-time","description":"The time the transaction was registered in the Stellar network."},"envelope":{"type":"string","description":"The transaction envelope, containing all the transaction information."},"payments":{"type":"array","items":{"type":"object","required":["id","payment_type","source_account","destination_account","amount"],"properties":{"id":{"type":"string","description":"The ID of the payment in the Stellar Network."},"payment_type":{"type":"string","description":"The type of payment in the Stellar Network.","enum":["payment","path_payment"],"default":"payment"},"source_account":{"type":"string","description":"The account being debited in the Stellar Network."},"destination_account":{"type":"string","description":"The account being credited in the Stellar Network."},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"}}}}},"title":"StellarTransaction"}},"source_account":{"type":"string"},"destination_account":{"type":"string"},"external_transaction_id":{"type":"string"},"memo":{"type":"string"},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"refund_memo":{"description":"If provided, this memo should be used for refund transactions.","type":"string"},"refund_memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"client_domain":{"type":"string"},"client_name":{"type":"string"},"customers":{"type":"object","description":"The user that initiated the transaction is both the sender and receiver.\n","properties":{"sender":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"receiver":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}}},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}},"title":"TransactionSEP24"},{"type":"object","required":["id","sep","kind","status","started_at"],"properties":{"id":{"type":"string"},"sep":{"type":"string","enum":["31"]},"kind":{"type":"string","enum":["receive"]},"status":{"type":"string","description":"Possible status value for SEP-31 transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_sender","pending_receiver","pending_transaction_info_update","pending_customer_info_update"],"title":"StatusSEP31"},"type":{"type":"string","description":"This field is always empty for SEP-31 transactions."},"amount_expected":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_in":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_out":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee_details":{"type":"object","required":["total","asset"],"properties":{"total":{"type":"string"},"asset":{"type":"string"},"details":{"type":"array","items":{"type":"object","required":["name","amount"],"properties":{"name":{"type":"string"},"amount":{"type":"string"},"description":{"type":"string"}},"title":"FeeDescription"}}},"title":"FeeDetails"},"quote_id":{"type":"string"},"started_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"completed_at":{"type":"string","format":"date-time"},"transfer_received_at":{"type":"string","format":"date-time"},"user_action_required_by":{"type":"string","format":"date-time"},"message":{"type":"string"},"refunds":{"type":"object","properties":{"amount_refunded":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"payments":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string"},"id_type":{"type":"string","enum":["stellar","external"]},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"requested_at":{"type":"string","format":"date-time"},"refunded_at":{"type":"string","format":"date-time"}}}}},"title":"Refunds"},"stellar_transactions":{"type":"array","items":{"type":"object","required":["id","created_at","envelope","payments"],"properties":{"id":{"type":"string","description":"The ID of the transaction in the Stellar network."},"memo":{"type":"string","description":"The memo of the transaction in the Stellar network."},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text","hash","id"]},"created_at":{"type":"string","format":"date-time","description":"The time the transaction was registered in the Stellar network."},"envelope":{"type":"string","description":"The transaction envelope, containing all the transaction information."},"payments":{"type":"array","items":{"type":"object","required":["id","payment_type","source_account","destination_account","amount"],"properties":{"id":{"type":"string","description":"The ID of the payment in the Stellar Network."},"payment_type":{"type":"string","description":"The type of payment in the Stellar Network.","enum":["payment","path_payment"],"default":"payment"},"source_account":{"type":"string","description":"The account being debited in the Stellar Network."},"destination_account":{"type":"string","description":"The account being credited in the Stellar Network."},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"}}}}},"title":"StellarTransaction"}},"source_account":{"type":"string"},"destination_account":{"type":"string"},"external_transaction_id":{"type":"string"},"memo":{"type":"string"},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"refund_memo":{"description":"if provided, this memo should be used for refund transactions.","type":"string"},"refund_memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"client_domain":{"type":"string"},"client_name":{"type":"string"},"customers":{"type":"object","description":"The Identification info of the sending and receiving customers. If they were created through [SEP-12](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md),\nthis object should contain the SEP-12 customer `id`. Otherwise, the `account` address of the customer.\n","properties":{"sender":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"receiver":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}}},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}},"title":"TransactionSEP31"}]}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}},"404":{"description":"Transaction not found.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transaction.api.mdx b/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transaction.api.mdx
deleted file mode 100644
index 95b1ec2e0..000000000
--- a/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transaction.api.mdx
+++ /dev/null
@@ -1,73 +0,0 @@
----
-id: get-transaction
-title: "Retrieve a Transaction"
-description: "Provides the information necessary for the business to determine the state of the transaction identified by `id`, decide if any action must be taken to continue processing the transaction, and act on the decision."
-sidebar_label: "Retrieve a Transaction"
-hide_title: true
-hide_table_of_contents: true
-api: eJztXN1P67gS/1csv+yuFFLgoPPQN/Yuu6q0HwjOfeKgHjeeNF4SO8d2KBXq/341ttOmbQotQqLnyi+Qxh8zHs+HZ36tn6llU0OHd/SLZtKwzAolDb1P6NOJgdq13F5dn3ymift/fhEePp1hJ1WDZjhkxOmQTsF2ZqEJ5WAyLWr3aUivtXoUHAyxBRAhc6UrN5ZIyMAYpuckV9q1ThojJBhDrCIcLOhKSHAtxjILROXug11RI4KDtCIXwMlkTr4J/i0hHDLBgYicMDknoWPVGEsmQCx7AIkEMiWtkA2QWitkRMjp5uwJYZLjBERJ14YzG6FkShNaM80qZBKl9UwFrrVmtqAJlawCOqSC04Rq+N4IDZwOrW4goSYroGJ0+EztvMZexmohp3SxuMfOplbSgMH289NT/LcuzY6kSa4ayZEVXApIi71ZXZcicwIe/GtwyHOHpJLwT+7YDcTV5F/I7Bqbd55vAzVN6IOQ7oNltjH+QVvgY2ZRD2qNmmCF51fwnlX5ibbeJxRkUyGxz/R+Eei80ItDrYywTrnc0wk8ZQWTU6AJnQlbcM1mrFz7sOqCFMISemhsqKsyRkxKr3KNIY+sbMBpqDOIrnqYDoNCZqqqS7Dg9sM/+v3PG8ndIzzVTsQJBa2VRh0CyYWcjo2FsmTdN/BkQUu3ovZV1hirKtBjNKJxU3PmiLXNjQE9dtzloMduo3a2dnhtOzCZFWs8Wd2YzRlQt9W4YvoBsMkqNTYVK8vwXDKN0k6oFbZEGd86Gd5eXX9GTfCCf20DvhRAKrCF4s7kkCz+4d4puM0nSpN2n4nK86xgQhKUs0mREKtUI+0YnmrIcBeGL+u7704TyoyBHsUO7X3K7Uf0GPNKBpd+9IotIY+MIdXYY+EoBxhzsEyU5jWWrLLOPHZw5JsPYQgVcZMy05rNaUKFhepVjpzbb6W6zZGPCn0M7Rbemmm8JMLfAX7r9F1stfmVLRL6vVEWxruc9cq/9xiqj910SNH1nFhRAY7xnuiwMUsPedCopf/SkIF4PJRPdIHec4/bbRtP5vtPUOFxZdq/h97N96pIn6WMl2HhSAwvsJUDHAtHNZtXIO1B1rjXgUTw8a5I1EbzVTxexuH7PkP9aF95LKwgTTCHmnNrAwcMWqw5tptgdM5xuR0brx3P3ujH3fk309B6NdSLRyhV7c5LrVrudf7tO9yMfutNZHyGcevXQSTYmdIPqfc7ldr33FSpN0y+0x52UMBuB5Aht4VqSo7ZV63BgLSYm7mZhCFSWSKbskw79mfhCcVeMIPplODO+jo7sp+29PGPDVt8z5ghGqbCWNDAX5LWUhH2ElaXRjsycYknExLzTVaWPUJcpsjpW/3gljaHSfxGJ9SoRmcwZlkW/AMHY4V0RDtvd51kDtf0QH9TtH93RLvG4n7iDWr42uQrvQo9nUBsMW4/3uPsOWtK63J4/3KxJaa9mAqdyQRwgzlMhN1Wqe66+0T/BkqZBv4aqWOKX+uePHDbrSMt9tiAfcW3WAXyboTYdQrud7jH7CyJ4MR5y07y/RdU6gvyuAy14/0iySjHmhgW7XhCbCGMJ2+WjLl0HEsiftq1mki6Qe6HFFdWCnRFXFVM9CVeyx47c7q2WNPrnreX7qoctmDoxIQVGOe2JWDIRNnC10NBctCuPBlyIZ1+lVsnYN/tdRaCVEf8J0OYBuK7mcCRL7HOCUh+gowaR9eXg8mtLw+RS1c/MgmZNNbJPbTfOPY6PdKv8qv8XWnCXJezc9LKKnFLwxouyQWUvKNxpslzkaHIsQyUN2U5X/GFo9o5Wj1pS8k/kV9Z9gCSb5Dd4jwQDy7km1viN9SjwIzZ0P+N+T6TUCE8v3j7hHtlMH3q42QWjGYpic6JxhZaNdMiCNzHgn1DzZWwBeg142sjj9Lkr+YJ+PIF41xj/T6wouSJL83hRtn5Ww6zvvzabrU7M61WiDVAwogpmF4xkZBZATrABmstaEHL/UhpT/wZce+9vEVFu4l2E+1mX7tZtCmaioYTDScazv6Gs3rbyX8CaPZmpHYTA9uV478/ont+cSCk28Fv3w+pPb/4QKj2qLHY84tDwFhhgm8UhrByxuaGQFXb+S5BRwA2ArARgI0AbARgIwAbAdgIwEYANgKwEYCNAGwEYI8sfkUA9gMB2HcFXJNtOUUANgKwsR4e6+E/Yj08ArDRbqLdRAA2Gk40nI8FYB1S9mYE9v2RVfz19R7Iagif7wimfjr7QDA1nKFXL5bHgy5A2skpe38e2/vr2T549NPZu8KjG6KL8GiERyM8GuHRCI9GeDTCoxEejfBohEcjPBrh0QiPHln8ivDo0cCjIsKjHw2PjsI1e/5mORcDWiGYUFRdQaHO3Nv5UzJy/eZkhjW6ECSX9ck7X6C8/7mwtjbDwWAqbNFM0kxVg3Bmav+f1FpZlalyMCnVZFAxDIcDyJSZGwvVwEB9cnp6dp5W/Jfkq3SK4pfUqkqIbH6j1ivRrqCakn+w8jkTBrZquet1znZYxHxjCT6W4CPmG+0m2k3EfKPhRMP5UQxnF+aL8N+9T/4u+i5g/pVxcuPLiYfcvPxyJdjjov3F4P50tZsQ+9GdVOHKvWgXcbG9iO4t0mjFh98k/UHrCYmyNL5+evdMH2BOh+215Ql1mvTi9eV4z7a/X9jfXR6KLXRIB928cfAs+MJh+/qxveO70SUd0jZTqUtmsRR24ruk8MQQNPI/3sUEhiIpTJVwyTiJF/6n9DQ9pavVXYd5yK2bp9dKWlrE03JoM6ZhvmZAEK5SEqRNych2PE6hTCi5MFJr8YiXqIfM1Hmq0BNVYOIKNhC+BZBrVTnbGjkSYFPisO5AHiSblOFK9+6l7TnYrHAze9DNm+fy7vaOeEnjLlwX1pDL65H3iqXIQBpYYZH0smZZAeTcyWsl/eFgMJvNUuZaU6WngzDUDP4c/efq79urk/P0NC1sVTrlqpWxFZOdiW/AagGPQBh54e7655U9/N9eYx9MEasOqNFCOihSO2ja28Ud3fjuxxAL3glF5cLW5+cJM/BfXS4W+Pp7A3pOh3f3aIxaoKI44+HC4DOnw5yVBl4Q9c83wRn8QnYx2Baa5Xxl8xS/g+O8geDowxNaAHOZ+NJNXGYZ1LYzZMvJrXmHP66+0MXif3vS8go=
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/anchor-platform/api-reference/platform/transactions/platform-server
-custom_edit_url: null
-hide_send_button: true
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={'SEP-6,SEP-24,SEP-31'} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Transaction"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/transactions/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Provides the information necessary for the business to determine the state of the transaction identified by `id`, decide if any action must be taken to continue processing the transaction, and act on the decision.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./get-transaction.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-transaction.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-transaction.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transaction.mdx b/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transaction.mdx
new file mode 100644
index 000000000..4ebda64bb
--- /dev/null
+++ b/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transaction.mdx
@@ -0,0 +1,8 @@
+---
+title: Retrieve a Transaction
+openapi: "openapi/anchor-platform/bundled-platform.yaml GET /transactions/{id}"
+playground: none
+---
+
+<Badge color="blue">SEP-6</Badge> <Badge color="blue">SEP-24</Badge>
+<Badge color="blue">SEP-31</Badge>
diff --git a/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transactions.ParamsDetails.json b/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transactions.ParamsDetails.json
deleted file mode 100644
index 712b31ef8..000000000
--- a/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transactions.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"in":"query","name":"sep","required":true,"schema":{"type":"string","enum":["6","24","31"]},"description":"Lookup transactions belonging to this SEP."},{"in":"query","name":"order_by","schema":{"type":"string","enum":["created_at","transfer_received_at","user_action_required_by"],"default":"created_at"},"description":"Specifies field that transactions will be ordered by. Note, that secondary sort is transaction id in ascending value.\nI.e. when timestamps for 2 or more transactions is identical, they will be sorted by id."},{"in":"query","name":"order","schema":{"type":"string","enum":["asc","desc"],"default":"asc"},"description":"Specifies order. Note, that when the field is null, all transactions with null value will be last, regardless of soring order (NULLS LAST).\nFor example, transfer time may not be specified for some transactions, resulting into `transfer_received_at` being null. If so, transactions with non-null values will be sorted and returned first, followed by all transactions with null timestamps."},{"in":"query","name":"statuses","schema":{"type":"array","items":{"type":"string","description":"Possible status values for all transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_user_transfer_start","pending_user_transfer_complete","pending_anchor","pending_trust","pending_user","no_market","too_small","too_large","pending_sender","pending_receiver","pending_transaction_info_update","pending_customer_info_update"],"title":"StatusSEPAll"}},"description":"Filters transactions for specified array of statuses. If not provided, filtering is disabled (default behavior)"},{"in":"query","name":"page_size","schema":{"type":"integer","default":20},"description":"Size of a single search page. Must be positive."},{"in":"query","name":"page_number","schema":{"type":"integer","default":0},"description":"Page number to use for continuous search. Page count beings at 0."}]}
\ No newline at end of file
diff --git a/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transactions.RequestSchema.json b/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transactions.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transactions.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transactions.StatusCodes.json b/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transactions.StatusCodes.json
deleted file mode 100644
index dd70c4c4f..000000000
--- a/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transactions.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Transaction found.","content":{"application/json":{"schema":{"oneOf":[{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","required":["id","sep","kind","status","started_at"],"properties":{"id":{"type":"string"},"sep":{"type":"string","enum":["6"]},"kind":{"type":"string","enum":["deposit","deposit-exchange","withdrawal","withdrawal-exchange"]},"status":{"type":"string","description":"Possible status value for SEP-6 transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_customer_info_update","pending_user_transfer_start","pending_user_transfer_complete","pending_anchor","pending_trust","pending_user","no_market","too_small","too_large"],"title":"StatusSEP6"},"type":{"type":"string","description":"The method the user used to deposit or withdraw offchain funds."},"amount_expected":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_in":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_out":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee_details":{"type":"object","required":["total","asset"],"properties":{"total":{"type":"string"},"asset":{"type":"string"},"details":{"type":"array","items":{"type":"object","required":["name","amount"],"properties":{"name":{"type":"string"},"amount":{"type":"string"},"description":{"type":"string"}},"title":"FeeDescription"}}},"title":"FeeDetails"},"quote_id":{"type":"string"},"started_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"completed_at":{"type":"string","format":"date-time"},"transfer_received_at":{"type":"string","format":"date-time"},"user_action_required_by":{"type":"string","format":"date-time"},"message":{"type":"string"},"refunds":{"type":"object","properties":{"amount_refunded":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"payments":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string"},"id_type":{"type":"string","enum":["stellar","external"]},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"requested_at":{"type":"string","format":"date-time"},"refunded_at":{"type":"string","format":"date-time"}}}}},"title":"Refunds"},"stellar_transactions":{"type":"array","items":{"type":"object","required":["id","created_at","envelope","payments"],"properties":{"id":{"type":"string","description":"The ID of the transaction in the Stellar network."},"memo":{"type":"string","description":"The memo of the transaction in the Stellar network."},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text","hash","id"]},"created_at":{"type":"string","format":"date-time","description":"The time the transaction was registered in the Stellar network."},"envelope":{"type":"string","description":"The transaction envelope, containing all the transaction information."},"payments":{"type":"array","items":{"type":"object","required":["id","payment_type","source_account","destination_account","amount"],"properties":{"id":{"type":"string","description":"The ID of the payment in the Stellar Network."},"payment_type":{"type":"string","description":"The type of payment in the Stellar Network.","enum":["payment","path_payment"],"default":"payment"},"source_account":{"type":"string","description":"The account being debited in the Stellar Network."},"destination_account":{"type":"string","description":"The account being credited in the Stellar Network."},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"}}}}},"title":"StellarTransaction"}},"source_account":{"type":"string"},"destination_account":{"type":"string"},"external_transaction_id":{"type":"string"},"memo":{"type":"string"},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"refund_memo":{"type":"string","description":"If provided, this memo should be used for refund transactions."},"refund_memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"client_domain":{"type":"string"},"client_name":{"type":"string"},"customers":{"type":"object","description":"The user that initiated the transaction is both the sender and receiver.\n","properties":{"sender":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"receiver":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}}},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}},"title":"TransactionSEP6"}}},"title":"TransactionListSEP6"},{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","required":["id","sep","kind","status","amount_expected","destination_account","started_at"],"properties":{"id":{"type":"string"},"sep":{"type":"string","enum":["24"]},"kind":{"type":"string","enum":["deposit","withdrawal"]},"status":{"type":"string","description":"Possible status value for SEP-24 transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_user_transfer_start","pending_user_transfer_complete","pending_anchor","pending_trust","pending_user","no_market","too_small","too_large"],"title":"StatusSEP24"},"type":{"type":"string","description":"This field is always empty for SEP-24 transactions."},"amount_expected":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_in":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_out":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee_details":{"type":"object","required":["total","asset"],"properties":{"total":{"type":"string"},"asset":{"type":"string"},"details":{"type":"array","items":{"type":"object","required":["name","amount"],"properties":{"name":{"type":"string"},"amount":{"type":"string"},"description":{"type":"string"}},"title":"FeeDescription"}}},"title":"FeeDetails"},"quote_id":{"type":"string"},"started_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"completed_at":{"type":"string","format":"date-time"},"transfer_received_at":{"type":"string","format":"date-time"},"user_action_required_by":{"type":"string","format":"date-time"},"message":{"type":"string"},"refunds":{"type":"object","properties":{"amount_refunded":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"payments":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string"},"id_type":{"type":"string","enum":["stellar","external"]},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"requested_at":{"type":"string","format":"date-time"},"refunded_at":{"type":"string","format":"date-time"}}}}},"title":"Refunds"},"stellar_transactions":{"type":"array","items":{"type":"object","required":["id","created_at","envelope","payments"],"properties":{"id":{"type":"string","description":"The ID of the transaction in the Stellar network."},"memo":{"type":"string","description":"The memo of the transaction in the Stellar network."},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text","hash","id"]},"created_at":{"type":"string","format":"date-time","description":"The time the transaction was registered in the Stellar network."},"envelope":{"type":"string","description":"The transaction envelope, containing all the transaction information."},"payments":{"type":"array","items":{"type":"object","required":["id","payment_type","source_account","destination_account","amount"],"properties":{"id":{"type":"string","description":"The ID of the payment in the Stellar Network."},"payment_type":{"type":"string","description":"The type of payment in the Stellar Network.","enum":["payment","path_payment"],"default":"payment"},"source_account":{"type":"string","description":"The account being debited in the Stellar Network."},"destination_account":{"type":"string","description":"The account being credited in the Stellar Network."},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"}}}}},"title":"StellarTransaction"}},"source_account":{"type":"string"},"destination_account":{"type":"string"},"external_transaction_id":{"type":"string"},"memo":{"type":"string"},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"refund_memo":{"description":"If provided, this memo should be used for refund transactions.","type":"string"},"refund_memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"client_domain":{"type":"string"},"client_name":{"type":"string"},"customers":{"type":"object","description":"The user that initiated the transaction is both the sender and receiver.\n","properties":{"sender":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"receiver":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}}},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}},"title":"TransactionSEP24"}}},"title":"TransactionListSEP24"},{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","required":["id","sep","kind","status","started_at"],"properties":{"id":{"type":"string"},"sep":{"type":"string","enum":["31"]},"kind":{"type":"string","enum":["receive"]},"status":{"type":"string","description":"Possible status value for SEP-31 transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_sender","pending_receiver","pending_transaction_info_update","pending_customer_info_update"],"title":"StatusSEP31"},"type":{"type":"string","description":"This field is always empty for SEP-31 transactions."},"amount_expected":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_in":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_out":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee_details":{"type":"object","required":["total","asset"],"properties":{"total":{"type":"string"},"asset":{"type":"string"},"details":{"type":"array","items":{"type":"object","required":["name","amount"],"properties":{"name":{"type":"string"},"amount":{"type":"string"},"description":{"type":"string"}},"title":"FeeDescription"}}},"title":"FeeDetails"},"quote_id":{"type":"string"},"started_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"completed_at":{"type":"string","format":"date-time"},"transfer_received_at":{"type":"string","format":"date-time"},"user_action_required_by":{"type":"string","format":"date-time"},"message":{"type":"string"},"refunds":{"type":"object","properties":{"amount_refunded":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"payments":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string"},"id_type":{"type":"string","enum":["stellar","external"]},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"requested_at":{"type":"string","format":"date-time"},"refunded_at":{"type":"string","format":"date-time"}}}}},"title":"Refunds"},"stellar_transactions":{"type":"array","items":{"type":"object","required":["id","created_at","envelope","payments"],"properties":{"id":{"type":"string","description":"The ID of the transaction in the Stellar network."},"memo":{"type":"string","description":"The memo of the transaction in the Stellar network."},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text","hash","id"]},"created_at":{"type":"string","format":"date-time","description":"The time the transaction was registered in the Stellar network."},"envelope":{"type":"string","description":"The transaction envelope, containing all the transaction information."},"payments":{"type":"array","items":{"type":"object","required":["id","payment_type","source_account","destination_account","amount"],"properties":{"id":{"type":"string","description":"The ID of the payment in the Stellar Network."},"payment_type":{"type":"string","description":"The type of payment in the Stellar Network.","enum":["payment","path_payment"],"default":"payment"},"source_account":{"type":"string","description":"The account being debited in the Stellar Network."},"destination_account":{"type":"string","description":"The account being credited in the Stellar Network."},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"}}}}},"title":"StellarTransaction"}},"source_account":{"type":"string"},"destination_account":{"type":"string"},"external_transaction_id":{"type":"string"},"memo":{"type":"string"},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"refund_memo":{"description":"if provided, this memo should be used for refund transactions.","type":"string"},"refund_memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"client_domain":{"type":"string"},"client_name":{"type":"string"},"customers":{"type":"object","description":"The Identification info of the sending and receiving customers. If they were created through [SEP-12](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md),\nthis object should contain the SEP-12 customer `id`. Otherwise, the `account` address of the customer.\n","properties":{"sender":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"receiver":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}}},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}},"title":"TransactionSEP31"}}},"title":"TransactionListSEP31"}]}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}},"404":{"description":"Transaction not found.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transactions.api.mdx b/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transactions.api.mdx
deleted file mode 100644
index 8f27bfd6b..000000000
--- a/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transactions.api.mdx
+++ /dev/null
@@ -1,73 +0,0 @@
----
-id: get-transactions
-title: "Retrieve a List of Transactions"
-description: "Allows to query list of transactions for desired SEP. This api supports pagination, and it's possible (and recommended) to make multiple requests to query transactions. The last page is reached when the number of elements returned by the endpoint is smaller than provided `page_size`."
-sidebar_label: "Retrieve a List of Transactions"
-hide_title: true
-hide_table_of_contents: true
-api: eJztXVtv47YS/isEX7oLKEo2G/TBb+lpehAg3Qab7dNu4NDS2GIjkSpJ5dLA//1ghpQt2bJjp4smPeDLxqZIznCu5Hxe8Yk7MbN89JV/MUJZkTmpleXXCX84sFDTk6uzy4MfeUJ/j0/Ch48fsJOuwQgccp7zEZ+B682S8BxsZmSNX/mIn5alvrfMafZnA+aRldI6pqfMdQaxqTYsBysN5Ozq7DJlXwppmagls01da+Msq8VMKiKbMKFyJt0PltXaWjkpgb3DJgOZripQOeTvkWAlboFVTelkXQIz8GcD1nVY6bKAJIGVwjqkBExaZkBkBeTsvgDFXAFMNdUEDDIPJVSgHPZxjVGQs8kjdQGV11oqh+NtJcoSDHOFUKw2+k7mkLMbnH5s5V9wk/KE18KIChwYlPoTlygy4o4nXIkK+IhbqHnCkX2UDx8500DCbVZAJfjoibvHmro5I9WMJxxUU6EKUX2kOlTbfFUvF1rfNnVfDRMotZpJNUMZOVQBKoPPk2HGtMnBjCfY8jw3mQHhIB8LxxNOVKdgxgYykHdtc2PBjD0z43a9OP81Mj8VTen4qDvR2qKuasjkVIJlUwlljqJ3/SXey7JkE2DEO+ktZZ+0g8T3tZBplQvzyKw2pMXOaCZzJhUTNgOVo5TuRNlA+k2dp5AGM5EVWCeq2tv0MdOGVdpAnwlpmcxBOZmJEgnD44IvJOvNSebPSH4nsQubBZfsSxHbt4iPCPQks/ACL1lpmWrKMmGiLFcl7Ap65sWzWBn6VsIMzITJS7AW/chqZNdTY+8+/X5xccUuTq++vE+/qV+0YfAgqrpEFoLBkIBZJR6Z0o7kFVjOSd5WV31RI0GLEUDNmFROs5sh07thE8AeyHXKzpGvZGhRWh0sF2ZXdeZDUIgHU2lwuVON4c8rdIuklmazWefWCddYsENqF8YI7CodVHbIHPp6vmzDpp+zXQ9KcJXJjilJlWnUhgOe8PZjTqFp2mDQxb4PNQWphIMxGk209r4ytg7KUnRb4MGBUaLsNFEAWGjIOmHcxqcdZtoOQmVFj6gzjV2dASWqx5Uwt0ChSOsxRerwuRRm1p3TYj7pzhnspk9mIbCxVFM9bupc9DjLGut0Bab3+DrhTroSFXVFirg6uzwtSz5fc8xfZIkpYj1pLs2fTIB8KtgJGTJ6SZt6EjalacgXLMulFZMScvYuRAU2gULcSW3eb7TBRe4aMkKpHMxILoswc3y0HmPkX4BsCmalmqENgjBZQVk3Zb82lty61lY6eQeb3YFY8Rl5R2bWebnETB+yutOssUBCzbRyUjW6sYG5lFHPTDfK+VBhmXDsKOXzazR/W2uFnjl64sdHR/inT6ezQWJT3ag8JQ9SDpTD3qKuS5nR5ubwD4tDnjor0gp+m9LuIKxNT/6AjMza4F7MSU8atz8mtzuEhcUEy03FVy7Ra/1e41Yq+kKW5D+YkHKvV6nKfD3ezP1EW/cmuCMhOlt65UB2QEqkTwfwkBVCkYNi9MyNuKcAsvyy7IIUwhJeFhHJGGgj/IohcTByvMGIORTMfkRL8IJ/TgG4+67AFTqnTQaSxX9y9MugfNxLtXpmejrNCiEVQzlT1uSiQv8cw0MNGWrhGXv33XnChbUwYNjh+ZBx+xHrT+ZLGZz60Uu2pHpjDOnGvRWOpgDjHJyQ5bNRymlH7rGBI/94H4bQEFcp7xU3KR+1Ul3nyKerIYY2C6/nGttE+AvAz52+87VnfmXzhP/ZaAfjTcF6Gd8HHHWqTYVPOIaeA9yq4hgfifYbs4iQe40aPCzuzueGM+XOE1RgrZgN69CH+UETGfKU8SItvBHHC2xNAd4KR7V4pMrKPt6404ZE5uNNmajN5st8vMjD10OO+tqx8q2wEipqezpk6wN7DJr3Atvn4HQUuEhj49727O/sf3tVKlB3UOqa9kutWe60/x3a3Jz/TFXPAvoVJV9TufLrYArcvTa3qY87ld5131TpF0y+0R82UMBue5BhV4VuypxOcwYsYFF06mfC4pF2vtzS8T8HDyj2QtgClZaT93U0spu1DPFPVaNVvu8F1m9n0jqqBG6R1sIQdhJWl0Y7MqFDpZAKD99UY1kTol+K1Cp9aRxcs+YwiVd0wq1uTAZjkWUhPuRgXSiqd1o37WT2t/RAf1W0nzqi7bG4m3iDGT43+dKuQk8SiCvG7ddePbRtnK+JaSemQudQR8xhIt26SXXXPST6F1DKDOTPkXpL+asfyQO3nfIIDXpOAbuKb75M5P0S3fAOYTjgvuVgiYAERcvO4ftXqPQX5HGRase7ZZLzaadSSOAPkbcLxug4jiURP20fPlsh968UV1ZKDEW5roQcOngtemw807XFmsHwvL50qnIQuiKVdBLz3LoELJtoV1C7r0UHoMFXodNvam0HHErWz7IQpHqe/2CZMMB8Nxs4IoBq+oiQ5gEyaomuh4HZVUDATql+ZBM2aRzJPTz/TOx1eqTflId0BHX5cMxaWREAxm5kfhOgpaXF2WY6lRmKHMtA06YsH5d84ah2jtZOJo2VCqz9gf0ksltQ+QrZNc4D8RBCbmiJN2hHgRm7Yv8r8/3IQoXw+OTlE+50ghkyH5JZcJqFJDo7GlcY3cyKIHCfC3ZNNWfSFWScS+drM4827NfmASGH0CDy3ARAD/trdeBLc6go9/iSzawvv7aqpj3TcoUEmwlmC2GWTCQIUBq/yes/QQ9a6CPlA/nnPPfRK+A60W+i30S/2dFv5u0RTUfHiY4THWd3x1m2ds4/HjTb8PBCWhdQtdfDgldRtk1VhO+PGR+f7AkadxDi74cFH5/E38cMo73HJ/vAvdIuf0kmynvxaBlUtXvcJOgI8UaIN0K8EeKNEG+EeCPEGyHeCPFGiDdCvBHijRDvG8tfEeJ9RYj3u0K6ybqcIsQbId5YcY8V939jxT1CvNFvot9EiDc6TnSc14V4ESnbjvESlvZ6IO/3B2/DO0ieA29Dhv6OeO3HD6+I1/7DLw/4+OG7IrAroosIbERgIwIbEdiIwEYENiKwEYGNCGxEYCMCGxHYiMC+sfwVEdg3g8DKiMC+NgJ77it+4f16lANaIdhQt12ireTu7fz0BkX/dlYsA4YkuSiBfvU10Ot3hXO1HR0ezqQrmkma6eow7Jnavwe10U5nujyclHpyWAlMh4eQaftoHVSHFuqDo6MPx2mVv0++KTIUv6TWVEJm84rqF7upZpuy37C4ei8trJWL+6XUdliElWOVP1b5I6wc/Sb6TYSVo+NEx/m3OM4mWBnhv+2wMva49sfDk6EXVf8kcvbZFxz3eUP19lqxR06Hy8XDB9rukdmP7hwmzqihXcTJ+iK6b9tGP9//jduvtJ5wlFbWV1i/PvFbeOSj9laWhJOtbb2dBd9H7l+j7K9mCeUYPuKHKyi4BXPX3jrSmJKPeHuMqUvhsE524Luk4RIG/5+H8XRDbz3HcxSuFifxcv+YHqVHfLmwyzAPu6J5Bl2opcU8LYKi8YzmCwoMsSytQLmUnbtOOCq0DfUYwWoj74SD9thKYSz0DHdEiCyD8BOBqdEVOd45kQAXrpoJ5EHhK/FtL0BTPAeXFTSzR+S87zr8tHqVDY6aMeksO7089yGzlBkoC0ugkp/WeLUMOyZ5LaU/Ojy8v79PBT1NtZkdhqH28OL8P2efrs4OjtOjtHCVvySg1tZVQnUm/gzOSLgDJthFuGhn2+08T0ufiBf1bL+oJ3g1ljjQQ6Qi3NMQDu5d7Cvvudh1wtFMsf3paSIs/G7K+Ryb/U0G6HjtHQx8NBWlhS3aefc5xJD3bI+bezaw7cOK/+lPiCmcfm+0Oz//bzftbJVU56Kjvy2ueLPOq92s87yOX67gf/qGlu2evbwq6KX2uuctLVvZ6d4a80J+/v5NLc9zuLhMZsnjNX4xEpnko6+IlBYgqEK62JydZhnUrjNqbWvZ25P99+wLn8//B7O2B6Q=
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/anchor-platform/api-reference/platform/transactions/platform-server
-custom_edit_url: null
-hide_send_button: true
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={'SEP-6,SEP-24,SEP-31'} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a List of Transactions"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/transactions"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Allows to query list of transactions for desired SEP. This api supports pagination, and it's possible (and recommended) to make multiple requests to query transactions. The last page is reached when the number of elements returned by the endpoint is smaller than provided `page_size`.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./get-transactions.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-transactions.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-transactions.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transactions.mdx b/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transactions.mdx
new file mode 100644
index 000000000..19038702c
--- /dev/null
+++ b/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transactions.mdx
@@ -0,0 +1,8 @@
+---
+title: Retrieve a List of Transactions
+openapi: "openapi/anchor-platform/bundled-platform.yaml GET /transactions"
+playground: none
+---
+
+<Badge color="blue">SEP-6</Badge> <Badge color="blue">SEP-24</Badge>
+<Badge color="blue">SEP-31</Badge>
diff --git a/docs/platforms/anchor-platform/api-reference/platform/transactions/index.mdx b/docs/platforms/anchor-platform/api-reference/platform/transactions/index.mdx
new file mode 100644
index 000000000..21ff20768
--- /dev/null
+++ b/docs/platforms/anchor-platform/api-reference/platform/transactions/index.mdx
@@ -0,0 +1,11 @@
+---
+title: Transactions
+description: "Transactions are representations of a SEP transaction. It holds information about the protocol being used, and all necessary information passed by an external party (such as wallet or an anchor)."
+---
+
+Should not be confused with stellar [transactions](/docs/learn/glossary#transaction).
+
+| Endpoints |  |
+| --- | --- |
+| GET | [/transactions/:id](/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transaction) |
+| GET | [/transactions/](/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transactions) |
diff --git a/docs/platforms/anchor-platform/index.mdx b/docs/platforms/anchor-platform/index.mdx
new file mode 100644
index 000000000..7fc5154da
--- /dev/null
+++ b/docs/platforms/anchor-platform/index.mdx
@@ -0,0 +1,43 @@
+---
+title: Anchor Platform
+sidebarTitle: Product Overview
+"og:title": "The Anchor Platform: Build and Manage On/Off-Ramps on the Stellar Network"
+description: "Learn how the Anchor Platform (AP) simplifies the process of building and managing a Stellar on and off-ramp. Learn about integrating with the AP or get API information."
+---
+
+The Anchor Platform provides a set of tools and APIs for building on and off-ramp services on the Stellar network. With standardized interfaces and full implementations of key [Stellar Ecosystem Proposals](/docs/learn/glossary#seps) (SEPs), it simplifies integration with Stellar-based wallets and exchanges, enabling you to focus on your core business logic rather than protocol implementation details.
+
+## Supported SEPs
+
+The Anchor Platform implements the following Stellar Ecosystem Proposals:
+
+- **[SEP-1](/docs/platforms/anchor-platform/sep-guide/sep1)** — Stellar.toml file serving for service discovery
+- **[SEP-6](/docs/platforms/anchor-platform/sep-guide/sep6)** — Deposit and withdrawal operations
+- **[SEP-10](/docs/platforms/anchor-platform/sep-guide/sep10)** — Web authentication using challenge/response transactions
+- **SEP-12** — Customer KYC/AML data management
+- **[SEP-24](/docs/platforms/anchor-platform/sep-guide/sep24)** — Interactive deposit and withdrawal flows
+- **[SEP-31](/docs/platforms/anchor-platform/sep-guide/sep31/integration)** — Cross-border payment processing (receive only)
+- **SEP-38** — Price quotes and exchange rate services
+- **[SEP-45](/docs/platforms/anchor-platform/sep-guide/sep45)** — Web authentication using challenge/responses for contract accounts
+
+## Key Features
+
+- **Complete SEP implementations** — Full support for deposit, withdrawal, and payment processing workflows
+- **Authentication & authorization** — SEP-10 and SEP-45 support for both traditional and smart contract accounts
+- **Customer management** — SEP-12 integration for KYC/AML compliance and customer data handling
+- **Transaction processing** — Comprehensive transaction lifecycle management with status tracking and webhook callbacks
+- **Quote & exchange services** — SEP-38 integration for price discovery and exchange rate calculations
+- **Multi-asset support** — Flexible configuration for multiple assets with various deposit and withdrawal methods
+- **Smart contract support** — Native support for Stellar contract accounts (C-accounts) via SEP-45
+
+## Documentation Links
+
+- **[Architecture](/docs/platforms/anchor-platform/admin-guide/architecture)** — System architecture and component overview
+- **[Getting Started](/docs/platforms/anchor-platform/admin-guide/getting-started)** — Initial setup and deployment instructions
+- **[Event Handling](/docs/platforms/anchor-platform/admin-guide/events)** — Event delivery, webhooks, and integration patterns
+- **[SEP Guides](/docs/platforms/anchor-platform/sep-guide)** — Implementation guides for Stellar Ecosystem Proposals
+- **[API Reference](/docs/platforms/anchor-platform/api-reference)** — Complete API documentation and reference
+
+## Additional Resources
+
+The documentation for the Anchor Platform is a work in progress. Developers are welcome to dive into the code and existing documentation on the [GitHub repository](https://github.com/stellar/anchor-platform).
diff --git a/docs/platforms/anchor-platform/sep-guide/README.mdx b/docs/platforms/anchor-platform/sep-guide/README.mdx
deleted file mode 100644
index a723d99de..000000000
--- a/docs/platforms/anchor-platform/sep-guide/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: SEP Guides
-sidebar_position: 30
----
-
-import DocCardList from "@theme/DocCardList";
-
-Guides for implementing Stellar Ecosystem Proposals (SEPs) with the Anchor Platform.
-
-<DocCardList />
diff --git a/docs/platforms/anchor-platform/sep-guide/_category_.json b/docs/platforms/anchor-platform/sep-guide/_category_.json
deleted file mode 100644
index aa65b42d3..000000000
--- a/docs/platforms/anchor-platform/sep-guide/_category_.json
+++ /dev/null
@@ -1,5 +0,0 @@
-{
-  "label": "SEP Guides",
-  "collapsed": false
-}
-
diff --git a/docs/platforms/anchor-platform/sep-guide/index.mdx b/docs/platforms/anchor-platform/sep-guide/index.mdx
new file mode 100644
index 000000000..8cd2be8bc
--- /dev/null
+++ b/docs/platforms/anchor-platform/sep-guide/index.mdx
@@ -0,0 +1,37 @@
+---
+title: SEP Guides
+description: "Guides for implementing Stellar Ecosystem Proposals (SEPs) with the Anchor Platform."
+---
+
+<CardGroup cols={2}>
+  <Card title="Stellar Info File (SEP-1)" icon="file-lines" href="/docs/platforms/anchor-platform/sep-guide/sep1">
+
+    SEP-1 (Stellar Info File) allows wallets and other Stellar applications to discover information about your anchor service.
+
+  </Card>
+  <Card title="Stellar Authentication (SEP-10)" icon="file-lines" href="/docs/platforms/anchor-platform/sep-guide/sep10">
+
+    SEP-10 (Stellar Web Authentication) enables wallet applications to create authenticated sessions with Stellar anchors by proving control over a Stellar account.
+
+  </Card>
+  <Card title="Stellar Authentication for Contract Accounts (SEP-45)" icon="file-lines" href="/docs/platforms/anchor-platform/sep-guide/sep45">
+
+    SEP-45 (Stellar Web Authentication for Contract Accounts) enables smart wallet applications to create authenticated sessions with Stellar anchors by proving...
+
+  </Card>
+  <Card title="Programmatic Deposits and Withdrawals (SEP-6)" icon="box-archive" href="/docs/platforms/anchor-platform/sep-guide/sep6">
+
+    3 items
+
+  </Card>
+  <Card title="Hosted Deposits and Withdrawals (SEP-24)" icon="box-archive" href="/docs/platforms/anchor-platform/sep-guide/sep24">
+
+    6 items
+
+  </Card>
+  <Card title="Cross-Border Payments (SEP-31)" icon="box-archive" href="/docs/platforms/anchor-platform/sep-guide/sep31">
+
+    3 items
+
+  </Card>
+</CardGroup>
diff --git a/docs/platforms/anchor-platform/sep-guide/sep1/README.mdx b/docs/platforms/anchor-platform/sep-guide/sep1/README.mdx
deleted file mode 100644
index 1157ae767..000000000
--- a/docs/platforms/anchor-platform/sep-guide/sep1/README.mdx
+++ /dev/null
@@ -1,198 +0,0 @@
----
-title: Stellar Info File (SEP-1)
-sidebar_position: 50
----
-
-## Overview
-
-SEP-1 (Stellar Info File) allows wallets and other Stellar applications to discover information about your anchor service. By hosting a `stellar.toml` file at `/.well-known/stellar.toml`, you enable applications to automatically find:
-
-- Your organization's information
-- Supported assets and currencies
-- Authentication endpoints (SEP-10)
-- SEP endpoints for SEP-6, SEP-24, SEP-31, SEP-38, SEP-45
-
-For details, please refer to the [SEP-1 specification][sep-1].
-
-## Creating Your stellar.toml File
-
-Create a `stellar.toml` file with your service information. Here's a minimal example to get started:
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-ACCOUNTS = ["GD...G"]  # Your distribution account public keys
-SIGNING_KEY = "GD...G"  # Your signing key (public key) for SEP-10 authentication
-NETWORK_PASSPHRASE = "Test SDF Network ; September 2015"  # Use "Public Global Stellar Network ; September 2015" for mainnet
-
-[DOCUMENTATION]
-ORG_NAME = "Your organization"
-ORG_URL = "https://your-website.com"
-ORG_DESCRIPTION = "A description of your organization"
-```
-
-</CodeExample>
-
-:::tip
-
-For a complete list of all available `stellar.toml` attributes, see the [SEP-1 specification][sep-1]. You'll need to add additional sections like `[[CURRENCIES]]`, `TRANSFER_SERVER`, `TRANSFER_SERVER_SEP0024`, `WEB_AUTH_ENDPOINT`, `WEB_AUTH_FOR_CONTRACTS_ENDPOINT`, `DIRECT_PAYMENT_SERVER` etc., as you configure the supported assets and other SEPs.
-
-:::
-
-:::important
-
-**Production vs. Development**: You'll need separate `stellar.toml` files for testnet and mainnet:
-
-- **Testnet**: Use `NETWORK_PASSPHRASE = "Test SDF Network ; September 2015"`
-- **Mainnet**: Use `NETWORK_PASSPHRASE = "Public Global Stellar Network ; September 2015"`
-
-Make sure your production file includes your actual Mainnet distribution accounts, signing keys, and production service URLs.
-
-:::
-
-## Configuration
-
-To enable SEP-1, you need to configure how the Anchor Platform should access your `stellar.toml` file. The platform supports three methods:
-
-| Type | Use Case | Description |
-| --- | --- | --- |
-| `file` | **Recommended for most cases** | Read from a local file on the server |
-| `string` | Quick testing or simple configs | Provide the TOML content directly in the config |
-| `url` | External hosting | Fetch from a remote URL (useful for dynamic content) |
-
-### Environment Variables
-
-Configure SEP-1 using the following environment variables:
-
-- `SEP1_ENABLED`: Set to `true` to enable SEP-1
-- `SEP1_TOML_TYPE`: One of `file`, `string`, or `url`
-- `SEP1_TOML_VALUE`: The value depends on the type (see examples below)
-
-### Method 1: File (Recommended)
-
-Best for: Production deployments where you manage the file on disk.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP1_ENABLED=true
-SEP1_TOML_TYPE=file
-SEP1_TOML_VALUE=/path/to/your/stellar.toml
-```
-
-</CodeExample>
-
-:::tip
-
-When using Docker, mount your `stellar.toml` file as a volume and reference the path inside the container. For example:
-
-```yaml
-# docker-compose.yaml
-volumes:
-  - ./config/stellar.toml:/config/stellar.toml:ro
-```
-
-Then set `SEP1_TOML_VALUE=/config/stellar.toml` in your environment.
-
-:::
-
-### Method 2: String
-
-Best for: Quick testing, development, or when managing config via environment variables.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP1_ENABLED=true
-SEP1_TOML_TYPE=string
-SEP1_TOML_VALUE="ACCOUNTS = [\"GD...G\"]
-SIGNING_KEY = \"GD...G\"
-NETWORK_PASSPHRASE = \"Test SDF Network ; September 2015\"
-[DOCUMENTATION]
-ORG_NAME = \"Your organization\"
-ORG_URL = \"https://your-website.com\""
-```
-
-</CodeExample>
-
-:::caution
-
-When using the `string` type, ensure your TOML content is properly escaped for your environment file format. For complex configurations, the `file` type is easier to manage.
-
-:::
-
-### Method 3: URL
-
-Best for: Dynamic content or when hosting the file externally.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP1_ENABLED=true
-SEP1_TOML_TYPE=url
-SEP1_TOML_VALUE=https://example.com/stellar.toml
-```
-
-</CodeExample>
-
-:::note
-
-When using the `url` type, the Anchor Platform will fetch the file on each request. Make sure the URL is accessible from your Anchor Platform server and returns valid TOML content.
-
-:::
-
-## Accessing Your stellar.toml File
-
-Once configured and enabled, the Anchor Platform automatically serves your `stellar.toml` file at the standard SEP-1 endpoint:
-
-- **`/.well-known/stellar.toml`** - The primary endpoint (served with `Content-Type: text/plain`)
-- **`/`** - Redirects to `/.well-known/stellar.toml` when SEP-1 is enabled
-
-### Testing Your Configuration
-
-After starting the Anchor Platform, verify your configuration:
-
-```bash
-# Test the endpoint
-curl http://localhost:8080/.well-known/stellar.toml
-
-# Or test the redirect
-curl -L http://localhost:8080/
-```
-
-You should see your `stellar.toml` content returned as plain text.
-
-### Alternative: External Hosting
-
-You can also host your `stellar.toml` file using a static file server like [nginx] or a CDN. If you choose this approach:
-
-1. Host the file at `https://your-domain.com/.well-known/stellar.toml`
-2. Ensure it's publicly accessible
-3. Make sure your `stellar.toml` file includes the correct URLs pointing to your Anchor Platform endpoints
-
-The Anchor Platform's SEP-1 service is optional if you're hosting the file externally, but it provides a convenient way to manage everything in one place.
-
-[sep-1]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md
-[sep-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
-[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[sep-38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
-[sep24-get-info]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md#info
-[anchor-platform-image]: https://hub.docker.com/r/stellar/anchor-platform
-[docker-compose]: https://docs.docker.com/compose/
-[minikube]: https://minikube.sigs.k8s.io/docs/
-[kubernetes]: https://kubernetes.io/
-[nginx]: https://www.nginx.com/
-[ap-default-values]: https://github.com/stellar/anchor-platform/blob/develop/platform/src/main/resources/config/anchor-config-default-values.yaml
-[stellar-demo-wallet]: https://demo-wallet.stellar.org
-[stellar-lab]: https://lab.stellar.org/
-[postgresql]: https://www.postgresql.org/
-[aurora-postgresql]: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraPostgreSQL.html
-[h2]: https://www.h2database.com/html/main.html
-[sqlite]: https://www.sqlite.org/index.html
-[flyway]: https://documentation.red-gate.com/fd/redgate-flyway-documentation-138346877.html
-[sep-24-ref-ui]: https://github.com/stellar/sep24-reference-ui
-[sep-24-ref]: https://github.com/stellar/anchor-platform/tree/develop/kotlin-reference-server
diff --git a/docs/platforms/anchor-platform/sep-guide/sep1/index.mdx b/docs/platforms/anchor-platform/sep-guide/sep1/index.mdx
new file mode 100644
index 000000000..5c298876b
--- /dev/null
+++ b/docs/platforms/anchor-platform/sep-guide/sep1/index.mdx
@@ -0,0 +1,197 @@
+---
+title: Stellar Info File (SEP-1)
+description: "SEP-1 (Stellar Info File) allows wallets and other Stellar applications to discover information about your anchor service."
+---
+
+## Overview
+
+SEP-1 (Stellar Info File) allows wallets and other Stellar applications to discover information about your anchor service. By hosting a `stellar.toml` file at `/.well-known/stellar.toml`, you enable applications to automatically find:
+
+- Your organization's information
+- Supported assets and currencies
+- Authentication endpoints (SEP-10)
+- SEP endpoints for SEP-6, SEP-24, SEP-31, SEP-38, SEP-45
+
+For details, please refer to the [SEP-1 specification][sep-1].
+
+## Creating Your stellar.toml File {#creating-your-stellartoml-file}
+
+Create a `stellar.toml` file with your service information. Here's a minimal example to get started:
+
+<CodeGroup>
+
+```toml TOML
+# dev.stellar.toml
+ACCOUNTS = ["GD...G"]  # Your distribution account public keys
+SIGNING_KEY = "GD...G"  # Your signing key (public key) for SEP-10 authentication
+NETWORK_PASSPHRASE = "Test SDF Network ; September 2015"  # Use "Public Global Stellar Network ; September 2015" for mainnet
+
+[DOCUMENTATION]
+ORG_NAME = "Your organization"
+ORG_URL = "https://your-website.com"
+ORG_DESCRIPTION = "A description of your organization"
+```
+
+</CodeGroup>
+
+<Tip>
+
+For a complete list of all available `stellar.toml` attributes, see the [SEP-1 specification][sep-1]. You'll need to add additional sections like `[[CURRENCIES]]`, `TRANSFER_SERVER`, `TRANSFER_SERVER_SEP0024`, `WEB_AUTH_ENDPOINT`, `WEB_AUTH_FOR_CONTRACTS_ENDPOINT`, `DIRECT_PAYMENT_SERVER` etc., as you configure the supported assets and other SEPs.
+
+</Tip>
+<Warning>
+
+**Production vs. Development**: You'll need separate `stellar.toml` files for testnet and mainnet:
+
+- **Testnet**: Use `NETWORK_PASSPHRASE = "Test SDF Network ; September 2015"`
+- **Mainnet**: Use `NETWORK_PASSPHRASE = "Public Global Stellar Network ; September 2015"`
+
+Make sure your production file includes your actual Mainnet distribution accounts, signing keys, and production service URLs.
+
+</Warning>
+
+## Configuration
+
+To enable SEP-1, you need to configure how the Anchor Platform should access your `stellar.toml` file. The platform supports three methods:
+
+| Type | Use Case | Description |
+| --- | --- | --- |
+| `file` | **Recommended for most cases** | Read from a local file on the server |
+| `string` | Quick testing or simple configs | Provide the TOML content directly in the config |
+| `url` | External hosting | Fetch from a remote URL (useful for dynamic content) |
+
+### Environment Variables
+
+Configure SEP-1 using the following environment variables:
+
+- `SEP1_ENABLED`: Set to `true` to enable SEP-1
+- `SEP1_TOML_TYPE`: One of `file`, `string`, or `url`
+- `SEP1_TOML_VALUE`: The value depends on the type (see examples below)
+
+### Method 1: File (Recommended)
+
+Best for: Production deployments where you manage the file on disk.
+
+<CodeGroup>
+
+```bash bash
+# dev.env
+SEP1_ENABLED=true
+SEP1_TOML_TYPE=file
+SEP1_TOML_VALUE=/path/to/your/stellar.toml
+```
+
+</CodeGroup>
+
+<Tip>
+
+When using Docker, mount your `stellar.toml` file as a volume and reference the path inside the container. For example:
+
+```yaml
+# docker-compose.yaml
+volumes:
+  - ./config/stellar.toml:/config/stellar.toml:ro
+```
+
+Then set `SEP1_TOML_VALUE=/config/stellar.toml` in your environment.
+
+</Tip>
+
+### Method 2: String
+
+Best for: Quick testing, development, or when managing config via environment variables.
+
+<CodeGroup>
+
+```bash bash
+# dev.env
+SEP1_ENABLED=true
+SEP1_TOML_TYPE=string
+SEP1_TOML_VALUE="ACCOUNTS = [\"GD...G\"]
+SIGNING_KEY = \"GD...G\"
+NETWORK_PASSPHRASE = \"Test SDF Network ; September 2015\"
+[DOCUMENTATION]
+ORG_NAME = \"Your organization\"
+ORG_URL = \"https://your-website.com\""
+```
+
+</CodeGroup>
+
+<Warning>
+
+When using the `string` type, ensure your TOML content is properly escaped for your environment file format. For complex configurations, the `file` type is easier to manage.
+
+</Warning>
+
+### Method 3: URL
+
+Best for: Dynamic content or when hosting the file externally.
+
+<CodeGroup>
+
+```bash bash
+# dev.env
+SEP1_ENABLED=true
+SEP1_TOML_TYPE=url
+SEP1_TOML_VALUE=https://example.com/stellar.toml
+```
+
+</CodeGroup>
+
+<Note>
+
+When using the `url` type, the Anchor Platform will fetch the file on each request. Make sure the URL is accessible from your Anchor Platform server and returns valid TOML content.
+
+</Note>
+
+## Accessing Your stellar.toml File {#accessing-your-stellartoml-file}
+
+Once configured and enabled, the Anchor Platform automatically serves your `stellar.toml` file at the standard SEP-1 endpoint:
+
+- **`/.well-known/stellar.toml`** - The primary endpoint (served with `Content-Type: text/plain`)
+- **`/`** - Redirects to `/.well-known/stellar.toml` when SEP-1 is enabled
+
+### Testing Your Configuration
+
+After starting the Anchor Platform, verify your configuration:
+
+```bash
+# Test the endpoint
+curl http://localhost:8080/.well-known/stellar.toml
+
+# Or test the redirect
+curl -L http://localhost:8080/
+```
+
+You should see your `stellar.toml` content returned as plain text.
+
+### Alternative: External Hosting
+
+You can also host your `stellar.toml` file using a static file server like [nginx] or a CDN. If you choose this approach:
+
+1. Host the file at `https://your-domain.com/.well-known/stellar.toml`
+2. Ensure it's publicly accessible
+3. Make sure your `stellar.toml` file includes the correct URLs pointing to your Anchor Platform endpoints
+
+The Anchor Platform's SEP-1 service is optional if you're hosting the file externally, but it provides a convenient way to manage everything in one place.
+
+[sep-1]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md
+[sep-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
+[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
+[sep-38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
+[sep24-get-info]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md#info
+[anchor-platform-image]: https://hub.docker.com/r/stellar/anchor-platform
+[docker-compose]: https://docs.docker.com/compose/
+[minikube]: https://minikube.sigs.k8s.io/docs/
+[kubernetes]: https://kubernetes.io/
+[nginx]: https://www.nginx.com/
+[ap-default-values]: https://github.com/stellar/anchor-platform/blob/develop/platform/src/main/resources/config/anchor-config-default-values.yaml
+[stellar-demo-wallet]: https://demo-wallet.stellar.org
+[stellar-lab]: https://lab.stellar.org/
+[postgresql]: https://www.postgresql.org/
+[aurora-postgresql]: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraPostgreSQL.html
+[h2]: https://www.h2database.com/html/main.html
+[sqlite]: https://www.sqlite.org/index.html
+[flyway]: https://documentation.red-gate.com/fd/redgate-flyway-documentation-138346877.html
+[sep-24-ref-ui]: https://github.com/stellar/sep24-reference-ui
+[sep-24-ref]: https://github.com/stellar/anchor-platform/tree/develop/kotlin-reference-server
diff --git a/docs/platforms/anchor-platform/sep-guide/sep10/README.mdx b/docs/platforms/anchor-platform/sep-guide/sep10/README.mdx
deleted file mode 100644
index 2f1af7cd2..000000000
--- a/docs/platforms/anchor-platform/sep-guide/sep10/README.mdx
+++ /dev/null
@@ -1,291 +0,0 @@
----
-title: Stellar Authentication (SEP-10)
-sidebar_position: 60
----
-
-## Overview
-
-SEP-10 (Stellar Web Authentication) enables wallet applications to create authenticated sessions with Stellar anchors by proving control over a Stellar account. Once authenticated, wallets receive a JSON Web Token (JWT) that they use in subsequent requests to the anchor's standardized services.
-
-For the complete specification, see [SEP-10: Stellar Web Authentication](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md).
-
-The Anchor Platform implements SEP-10 with support for:
-
-- **Challenge/Response Flow**: GET `/auth` to request a challenge, POST `/auth` to validate and receive a JWT
-- **Client Attribution**: Optional verification of client application identity for noncustodial wallets
-- **Custodial Wallet Support**: Support for custodial wallets that manage user accounts
-- **Multiple Home Domains**: Support for multiple domains and wildcard patterns
-
-## Typical Authentication Flow
-
-1. The **Client** requests a unique challenge from the **Server**
-2. The **Client** verifies and signs the challenge
-3. The **Client** submits the signed challenge to the **Server**
-4. The **Server** verifies the challenge and responds with a JWT session token
-
-## Enable SEP-10
-
-To enable SEP-10, set the following environment variables in your `dev.env` file.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP10_ENABLED=true
-SEP10_HOME_DOMAINS=localhost:8080
-SECRET_SEP10_SIGNING_SEED="a Stellar private key"
-SECRET_SEP10_JWT_SECRET="a secret encryption key"
-```
-
-</CodeExample>
-
-### Required Configuration (If Enabled)
-
-| Variable | Default | Description |
-| --- | --- | --- |
-| `SEP10_ENABLED` | `false` | Set to `true` to enable SEP-10 authentication |
-| `SEP10_HOME_DOMAINS` | `localhost:8080` | List of home domains (comma-separated). Supports wildcard patterns like `*.stellar.org`. The `home_domain` must match the host where your `stellar.toml` file is served. |
-| `SECRET_SEP10_SIGNING_SEED` | _Required_ | The private key corresponding to the `SIGNING_KEY` in your `stellar.toml` file. Used to sign authentication challenges. Wallets verify this signature before signing and returning the challenge. |
-| `SECRET_SEP10_JWT_SECRET` | _Required_ | The encryption key used to sign and verify JWT tokens issued to authenticated wallets. |
-
-:::important
-
-The `SIGNING_KEY` in your `stellar.toml` file must be the public key derived from `SECRET_SEP10_SIGNING_SEED`. Wallets will verify that challenge transactions are signed by this key.
-
-:::
-
-### Optional Configuration
-
-<CodeExample>
-
-```bash
-# dev.env
-# Optional: Specify web_auth_domain (default: first home_domain if only one is specified)
-SEP10_WEB_AUTH_DOMAIN=localhost:8080
-
-# Optional: Challenge transaction timeout in seconds (default: 900)
-SEP10_AUTH_TIMEOUT=900
-
-# Optional: JWT token timeout in seconds (default: 86400 = 24 hours)
-SEP10_JWT_TIMEOUT=86400
-
-# Optional: Require Authorization header in GET /auth requests (default: false)
-SEP10_REQUIRE_AUTH_HEADER=false
-
-# Optional: Client attribution requirement (default: false)
-SEP10_CLIENT_ATTRIBUTION_REQUIRED=false
-
-# Optional: Client allow list (default: empty, all configured clients allowed)
-# Comma-separated list of client names that are allowed to authenticate
-SEP10_CLIENT_ALLOW_LIST=client1,client2
-```
-
-</CodeExample>
-
-| Variable | Default | Description |
-| --- | --- | --- |
-| `SEP10_WEB_AUTH_DOMAIN` | First `home_domain` if only one is specified, otherwise empty | The `web_auth_domain` property used in SEP-10 responses. Required if you have multiple `home_domains` or use wildcard patterns. Must match the host of the SEP server. |
-| `SEP10_AUTH_TIMEOUT` | `900` | Time in seconds that a challenge transaction remains valid. Clients must sign and submit the challenge within this window. |
-| `SEP10_JWT_TIMEOUT` | `86400` | Time in seconds that an issued JWT token remains valid. After expiration, clients must re-authenticate. |
-| `SEP10_REQUIRE_AUTH_HEADER` | `false` | If `true`, requires a valid Authorization header (Bearer JWT) in GET `/auth` challenge requests. This prevents unauthorized access to the endpoint and is useful for re-authentication flows where clients need to refresh their JWT tokens. |
-| `SEP10_CLIENT_ATTRIBUTION_REQUIRED` | `false` | If `true`, noncustodial wallets must provide a `client_domain` in challenge requests. Requires client configuration (see below). |
-| `SEP10_CLIENT_ALLOW_LIST` | Empty (all configured clients allowed) | Comma-separated list of client names that are allowed to authenticate. Only relevant when `SEP10_CLIENT_ATTRIBUTION_REQUIRED=true`. If empty, all configured clients are allowed. |
-
-:::tip
-
-**Multiple Home Domains**: If you specify multiple `home_domains` (e.g., `ap.stellar.org,*.sdp.stellar.org`), you must also set `SEP10_WEB_AUTH_DOMAIN` to specify which domain hosts the authentication endpoint.
-
-:::
-
-## Client Attribution
-
-Client attribution allows you to restrict authentication to specific wallet applications and verify their identity. This is an optional feature that should only be enabled if it's a business requirement.
-
-:::info
-
-By default, the Anchor Platform allows anyone with a Stellar account to authenticate. Client attribution is only needed if you want to:
-
-- Restrict authentication to specific wallet applications
-- Verify the identity of noncustodial wallet applications
-- Track which wallet applications your users are using
-
-:::
-
-### Enabling Client Attribution
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP10_CLIENT_ATTRIBUTION_REQUIRED=true
-```
-
-</CodeExample>
-
-When `SEP10_CLIENT_ATTRIBUTION_REQUIRED=true`, noncustodial wallets must:
-
-1. Provide a `client_domain` parameter in the challenge request
-2. Sign the challenge transaction with the `SIGNING_KEY` from that domain's `stellar.toml` file
-3. Have their domain listed in your client configuration
-
-### Client Configuration
-
-Configure allowed clients in your YAML configuration file:
-
-<CodeExample>
-
-```yaml
-clients:
-  # Each item in the list may contain the following fields:
-  #   - name: (required) the name of the client
-  #   - type: (required) `custodial` or `noncustodial`
-  #
-  #   If the type is `custodial`,
-  #   - signing_keys: (required) the custodial SEP-10 signing key(s) of the client.
-  #   - callback_urls.sep6: (optional) the URL of the client's SEP-6 callback API endpoint.
-  #   - callback_urls.sep24: (optional) the URL of the client's SEP-24 callback API endpoint.
-  #   - callback_urls.sep31: (optional) the URL of the client's SEP-31 callback API endpoint.
-  #   - callback_urls.sep12: (optional) the URL of the client's SEP-12 callback API endpoint.
-  #   - allow_any_destination: (optional) default to false. If set to true, allows any destination for deposits.
-  #   - destination_accounts: (optional) list of accounts allowed to be used for the deposit.
-  #                           If allow_any_destination is set to true, this configuration option is ignored.
-  #
-  #   If the type is `noncustodial`,
-  #   - domains: (required) the domains of the client.
-  #   - callback_urls.sep6: (optional) the URL of the client's SEP-6 callback API endpoint.
-  #   - callback_urls.sep24: (optional) the URL of the client's SEP-24 callback API endpoint.
-  #   - callback_urls.sep31: (optional) the URL of the client's SEP-31 callback API endpoint.
-  #   - callback_urls.sep12: (optional) the URL of the client's SEP-12 callback API endpoint.
-
-  # custodial client
-  - name: bluecorp
-    type: custodial
-    signing_keys: "the signing key 1 of bluecorp","the signing key 2 of bluecorp"
-    callback_urls:
-      sep6: https://callback.bluecorp.com/api/v1/anchor/callback/sep6
-      sep12: https://callback.bluecorp.com/api/v1/anchor/callback/sep12
-    allow_any_destination: false
-    destination_accounts: GA...
-
-  # noncustodial client
-  - name: pinkcorp
-    type: noncustodial
-    domains: pinkcorp.com
-    callback_urls:
-      sep6: https://callback.pinkcorp.com/api/v2/anchor/callback/sep6
-      sep12: https://callback.pinkcorp.com/api/v2/anchor/callback/sep12
-
- - name: redcorp
-    type: custodial
-    signing_keys: "the signing key of redcorp",
-
-```
-
-</CodeExample>
-
-Or configure via environment variables:
-
-<CodeExample>
-
-```bash
-# dev.env
-# custodial client
-CLIENTS[0]_NAME=bluecorp
-CLIENTS[0]_TYPE=custodial
-CLIENTS[0]_SIGNING_KEYS="the signing key 1 of bluecorp","the signing key 2 of bluecorp"
-CLIENTS[0]_ALLOW_ANY_DESTINATION=false
-CLIENTS[0]_DESTINATION_ACCOUNTS=GA...
-
-# noncustodial client
-CLIENTS[1]_NAME=pinkcorp
-CLIENTS[1]_TYPE=noncustodial
-CLIENTS[1]_DOMAINS=pinkcorp.com
-
-# custodial client
-CLIENTS[2]_NAME=redcorp
-CLIENTS[2]_TYPE=custodial
-CLIENTS[2]_SIGNING_KEYS="the signing key of redcorp"
-```
-
-</CodeExample>
-
-## Configure stellar.toml
-
-Update your `stellar.toml` file to advertise SEP-10 support. Wallets discover your authentication endpoint through this file.
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-SIGNING_KEY = "add your signing key here (public key from SECRET_SEP10_SIGNING_SEED)"
-WEB_AUTH_ENDPOINT = "http://localhost:8080/auth"
-```
-
-</CodeExample>
-
-These fields should match the configuration options set in the [Enable SEP-10](#enable-sep-10) section above.
-
-`WEB_AUTH_ENDPOINT` - The URL where the authentication service is running. This is the URL that clients will use to authenticate with the anchor. The endpoint must support:
-
-- `GET <WEB_AUTH_ENDPOINT>` - Request a challenge
-- `POST <WEB_AUTH_ENDPOINT>` - Exchange signed challenge for session JWT
-
-`SIGNING_KEY` - The public key corresponding to the private key specified in `SECRET_SEP10_SIGNING_SEED`. This key is used to sign authentication challenges presented to wallet applications.
-
-:::important
-
-- **`SIGNING_KEY`**: Must be the public key derived from `SECRET_SEP10_SIGNING_SEED`
-- **`WEB_AUTH_ENDPOINT`**: Use `https://` in production. The path `/auth` is the standard SEP-10 endpoint.
-- **Host Matching**: The host in `WEB_AUTH_ENDPOINT` should match one of your `SEP10_HOME_DOMAINS` (or the `SEP10_WEB_AUTH_DOMAIN` if specified).
-
-:::
-
-## How to Test the Authentication Flow
-
-The SEP-10 authentication flow consists of two steps:
-
-1. **GET `/auth`** - Request a challenge transaction
-   - Parameters: `account` (required), `memo` (optional), `home_domain` (optional), `client_domain` (optional)
-   - Returns: A challenge transaction in XDR format
-
-2. **POST `/auth`** - Validate the signed challenge and receive a JWT
-   - Body: `{ "transaction": "<signed_challenge_xdr>" }`
-   - Returns: `{ "token": "<jwt_token>" }`
-
-The JWT token should be included in subsequent API requests as a Bearer token in the `Authorization` header.
-
-:::tip
-
-**Testing Your Configuration**: You can test SEP-10 authentication using curl and Stellar CLI. For more information about Stellar CLI, see the [Stellar CLI documentation](../../../../tools/cli/README.mdx).
-
-```bash
-# Verify if `stellar` command line is installed
-stellar --version
-
-# List your Stellar keys/identities
-stellar keys ls
-
-# Get your account ID (public key) and secret seed
-# Replace 'alice' with your identity name from `stellar keys ls`
-IDENTITY_NAME="alice"
-ACCOUNT_ID=$(stellar keys public-key "$IDENTITY_NAME")
-SECRET_SEED=$(stellar keys secret "$IDENTITY_NAME")
-
-# Step 1: Request challenge and save the transaction XDR
-CHALLENGE_RESPONSE=$(curl -s "http://localhost:8080/auth?account=$ACCOUNT_ID")
-CHALLENGE_XDR=$(echo "$CHALLENGE_RESPONSE" | jq -r '.transaction')
-
-# Step 2: Sign the challenge transaction using Stellar CLI
-# Note: The output includes info messages; the signed XDR is on the last line
-SIGNED_CHALLENGE_XDR=$(echo "$CHALLENGE_XDR" | stellar tx sign --sign-with-key "$SECRET_SEED" 2>&1 | tail -1)
-
-# Step 3: Submit the signed challenge and receive JWT token
-curl -X POST "http://localhost:8080/auth" \
-  -H "Content-Type: application/json" \
-  -d "{\"transaction\": \"$SIGNED_CHALLENGE_XDR\"}"
-```
-
-:::
-
-[sep1-ap]: ../sep1/README.mdx
-[sep-10]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md
diff --git a/docs/platforms/anchor-platform/sep-guide/sep10/index.mdx b/docs/platforms/anchor-platform/sep-guide/sep10/index.mdx
new file mode 100644
index 000000000..49c7f11ce
--- /dev/null
+++ b/docs/platforms/anchor-platform/sep-guide/sep10/index.mdx
@@ -0,0 +1,291 @@
+---
+title: Stellar Authentication (SEP-10)
+description: "SEP-10 (Stellar Web Authentication) enables wallet applications to create authenticated sessions with Stellar anchors by proving control over a Stellar account."
+---
+
+## Overview
+
+SEP-10 (Stellar Web Authentication) enables wallet applications to create authenticated sessions with Stellar anchors by proving control over a Stellar account. Once authenticated, wallets receive a JSON Web Token (JWT) that they use in subsequent requests to the anchor's standardized services.
+
+For the complete specification, see [SEP-10: Stellar Web Authentication](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md).
+
+The Anchor Platform implements SEP-10 with support for:
+
+- **Challenge/Response Flow**: GET `/auth` to request a challenge, POST `/auth` to validate and receive a JWT
+- **Client Attribution**: Optional verification of client application identity for noncustodial wallets
+- **Custodial Wallet Support**: Support for custodial wallets that manage user accounts
+- **Multiple Home Domains**: Support for multiple domains and wildcard patterns
+
+## Typical Authentication Flow
+
+1. The **Client** requests a unique challenge from the **Server**
+2. The **Client** verifies and signs the challenge
+3. The **Client** submits the signed challenge to the **Server**
+4. The **Server** verifies the challenge and responds with a JWT session token
+
+## Enable SEP-10
+
+To enable SEP-10, set the following environment variables in your `dev.env` file.
+
+<CodeGroup>
+
+```bash bash
+# dev.env
+SEP10_ENABLED=true
+SEP10_HOME_DOMAINS=localhost:8080
+SECRET_SEP10_SIGNING_SEED="a Stellar private key"
+SECRET_SEP10_JWT_SECRET="a secret encryption key"
+```
+
+</CodeGroup>
+
+### Required Configuration (If Enabled)
+
+| Variable | Default | Description |
+| --- | --- | --- |
+| `SEP10_ENABLED` | `false` | Set to `true` to enable SEP-10 authentication |
+| `SEP10_HOME_DOMAINS` | `localhost:8080` | List of home domains (comma-separated). Supports wildcard patterns like `*.stellar.org`. The `home_domain` must match the host where your `stellar.toml` file is served. |
+| `SECRET_SEP10_SIGNING_SEED` | _Required_ | The private key corresponding to the `SIGNING_KEY` in your `stellar.toml` file. Used to sign authentication challenges. Wallets verify this signature before signing and returning the challenge. |
+| `SECRET_SEP10_JWT_SECRET` | _Required_ | The encryption key used to sign and verify JWT tokens issued to authenticated wallets. |
+
+<Warning>
+
+The `SIGNING_KEY` in your `stellar.toml` file must be the public key derived from `SECRET_SEP10_SIGNING_SEED`. Wallets will verify that challenge transactions are signed by this key.
+
+</Warning>
+
+### Optional Configuration
+
+<CodeGroup>
+
+```bash bash
+# dev.env
+# Optional: Specify web_auth_domain (default: first home_domain if only one is specified)
+SEP10_WEB_AUTH_DOMAIN=localhost:8080
+
+# Optional: Challenge transaction timeout in seconds (default: 900)
+SEP10_AUTH_TIMEOUT=900
+
+# Optional: JWT token timeout in seconds (default: 86400 = 24 hours)
+SEP10_JWT_TIMEOUT=86400
+
+# Optional: Require Authorization header in GET /auth requests (default: false)
+SEP10_REQUIRE_AUTH_HEADER=false
+
+# Optional: Client attribution requirement (default: false)
+SEP10_CLIENT_ATTRIBUTION_REQUIRED=false
+
+# Optional: Client allow list (default: empty, all configured clients allowed)
+# Comma-separated list of client names that are allowed to authenticate
+SEP10_CLIENT_ALLOW_LIST=client1,client2
+```
+
+</CodeGroup>
+
+| Variable | Default | Description |
+| --- | --- | --- |
+| `SEP10_WEB_AUTH_DOMAIN` | First `home_domain` if only one is specified, otherwise empty | The `web_auth_domain` property used in SEP-10 responses. Required if you have multiple `home_domains` or use wildcard patterns. Must match the host of the SEP server. |
+| `SEP10_AUTH_TIMEOUT` | `900` | Time in seconds that a challenge transaction remains valid. Clients must sign and submit the challenge within this window. |
+| `SEP10_JWT_TIMEOUT` | `86400` | Time in seconds that an issued JWT token remains valid. After expiration, clients must re-authenticate. |
+| `SEP10_REQUIRE_AUTH_HEADER` | `false` | If `true`, requires a valid Authorization header (Bearer JWT) in GET `/auth` challenge requests. This prevents unauthorized access to the endpoint and is useful for re-authentication flows where clients need to refresh their JWT tokens. |
+| `SEP10_CLIENT_ATTRIBUTION_REQUIRED` | `false` | If `true`, noncustodial wallets must provide a `client_domain` in challenge requests. Requires client configuration (see below). |
+| `SEP10_CLIENT_ALLOW_LIST` | Empty (all configured clients allowed) | Comma-separated list of client names that are allowed to authenticate. Only relevant when `SEP10_CLIENT_ATTRIBUTION_REQUIRED=true`. If empty, all configured clients are allowed. |
+
+<Tip>
+
+**Multiple Home Domains**: If you specify multiple `home_domains` (e.g., `ap.stellar.org,*.sdp.stellar.org`), you must also set `SEP10_WEB_AUTH_DOMAIN` to specify which domain hosts the authentication endpoint.
+
+</Tip>
+
+## Client Attribution
+
+Client attribution allows you to restrict authentication to specific wallet applications and verify their identity. This is an optional feature that should only be enabled if it's a business requirement.
+
+<Info>
+
+By default, the Anchor Platform allows anyone with a Stellar account to authenticate. Client attribution is only needed if you want to:
+
+- Restrict authentication to specific wallet applications
+- Verify the identity of noncustodial wallet applications
+- Track which wallet applications your users are using
+
+</Info>
+
+### Enabling Client Attribution
+
+<CodeGroup>
+
+```bash bash
+# dev.env
+SEP10_CLIENT_ATTRIBUTION_REQUIRED=true
+```
+
+</CodeGroup>
+
+When `SEP10_CLIENT_ATTRIBUTION_REQUIRED=true`, noncustodial wallets must:
+
+1. Provide a `client_domain` parameter in the challenge request
+2. Sign the challenge transaction with the `SIGNING_KEY` from that domain's `stellar.toml` file
+3. Have their domain listed in your client configuration
+
+### Client Configuration
+
+Configure allowed clients in your YAML configuration file:
+
+<CodeGroup>
+
+```yaml YAML
+clients:
+  # Each item in the list may contain the following fields:
+  #   - name: (required) the name of the client
+  #   - type: (required) `custodial` or `noncustodial`
+  #
+  #   If the type is `custodial`,
+  #   - signing_keys: (required) the custodial SEP-10 signing key(s) of the client.
+  #   - callback_urls.sep6: (optional) the URL of the client's SEP-6 callback API endpoint.
+  #   - callback_urls.sep24: (optional) the URL of the client's SEP-24 callback API endpoint.
+  #   - callback_urls.sep31: (optional) the URL of the client's SEP-31 callback API endpoint.
+  #   - callback_urls.sep12: (optional) the URL of the client's SEP-12 callback API endpoint.
+  #   - allow_any_destination: (optional) default to false. If set to true, allows any destination for deposits.
+  #   - destination_accounts: (optional) list of accounts allowed to be used for the deposit.
+  #                           If allow_any_destination is set to true, this configuration option is ignored.
+  #
+  #   If the type is `noncustodial`,
+  #   - domains: (required) the domains of the client.
+  #   - callback_urls.sep6: (optional) the URL of the client's SEP-6 callback API endpoint.
+  #   - callback_urls.sep24: (optional) the URL of the client's SEP-24 callback API endpoint.
+  #   - callback_urls.sep31: (optional) the URL of the client's SEP-31 callback API endpoint.
+  #   - callback_urls.sep12: (optional) the URL of the client's SEP-12 callback API endpoint.
+
+  # custodial client
+  - name: bluecorp
+    type: custodial
+    signing_keys: "the signing key 1 of bluecorp","the signing key 2 of bluecorp"
+    callback_urls:
+      sep6: https://callback.bluecorp.com/api/v1/anchor/callback/sep6
+      sep12: https://callback.bluecorp.com/api/v1/anchor/callback/sep12
+    allow_any_destination: false
+    destination_accounts: GA...
+
+  # noncustodial client
+  - name: pinkcorp
+    type: noncustodial
+    domains: pinkcorp.com
+    callback_urls:
+      sep6: https://callback.pinkcorp.com/api/v2/anchor/callback/sep6
+      sep12: https://callback.pinkcorp.com/api/v2/anchor/callback/sep12
+
+ - name: redcorp
+    type: custodial
+    signing_keys: "the signing key of redcorp",
+
+```
+
+</CodeGroup>
+
+Or configure via environment variables:
+
+<CodeGroup>
+
+```bash bash
+# dev.env
+# custodial client
+CLIENTS[0]_NAME=bluecorp
+CLIENTS[0]_TYPE=custodial
+CLIENTS[0]_SIGNING_KEYS="the signing key 1 of bluecorp","the signing key 2 of bluecorp"
+CLIENTS[0]_ALLOW_ANY_DESTINATION=false
+CLIENTS[0]_DESTINATION_ACCOUNTS=GA...
+
+# noncustodial client
+CLIENTS[1]_NAME=pinkcorp
+CLIENTS[1]_TYPE=noncustodial
+CLIENTS[1]_DOMAINS=pinkcorp.com
+
+# custodial client
+CLIENTS[2]_NAME=redcorp
+CLIENTS[2]_TYPE=custodial
+CLIENTS[2]_SIGNING_KEYS="the signing key of redcorp"
+```
+
+</CodeGroup>
+
+## Configure stellar.toml {#configure-stellartoml}
+
+Update your `stellar.toml` file to advertise SEP-10 support. Wallets discover your authentication endpoint through this file.
+
+<CodeGroup>
+
+```toml TOML
+# dev.stellar.toml
+SIGNING_KEY = "add your signing key here (public key from SECRET_SEP10_SIGNING_SEED)"
+WEB_AUTH_ENDPOINT = "http://localhost:8080/auth"
+```
+
+</CodeGroup>
+
+These fields should match the configuration options set in the [Enable SEP-10](#enable-sep-10) section above.
+
+`WEB_AUTH_ENDPOINT` - The URL where the authentication service is running. This is the URL that clients will use to authenticate with the anchor. The endpoint must support:
+
+- `GET <WEB_AUTH_ENDPOINT>` - Request a challenge
+- `POST <WEB_AUTH_ENDPOINT>` - Exchange signed challenge for session JWT
+
+`SIGNING_KEY` - The public key corresponding to the private key specified in `SECRET_SEP10_SIGNING_SEED`. This key is used to sign authentication challenges presented to wallet applications.
+
+<Warning>
+
+- **`SIGNING_KEY`**: Must be the public key derived from `SECRET_SEP10_SIGNING_SEED`
+- **`WEB_AUTH_ENDPOINT`**: Use `https://` in production. The path `/auth` is the standard SEP-10 endpoint.
+- **Host Matching**: The host in `WEB_AUTH_ENDPOINT` should match one of your `SEP10_HOME_DOMAINS` (or the `SEP10_WEB_AUTH_DOMAIN` if specified).
+
+</Warning>
+
+## How to Test the Authentication Flow
+
+The SEP-10 authentication flow consists of two steps:
+
+1. **GET `/auth`** - Request a challenge transaction
+   - Parameters: `account` (required), `memo` (optional), `home_domain` (optional), `client_domain` (optional)
+   - Returns: A challenge transaction in XDR format
+
+2. **POST `/auth`** - Validate the signed challenge and receive a JWT
+   - Body: `{ "transaction": "<signed_challenge_xdr>" }`
+   - Returns: `{ "token": "<jwt_token>" }`
+
+The JWT token should be included in subsequent API requests as a Bearer token in the `Authorization` header.
+
+<Tip>
+
+**Testing Your Configuration**: You can test SEP-10 authentication using curl and Stellar CLI. For more information about Stellar CLI, see the [Stellar CLI documentation](/docs/tools/cli).
+
+```bash
+# Verify if `stellar` command line is installed
+stellar --version
+
+# List your Stellar keys/identities
+stellar keys ls
+
+# Get your account ID (public key) and secret seed
+# Replace 'alice' with your identity name from `stellar keys ls`
+IDENTITY_NAME="alice"
+ACCOUNT_ID=$(stellar keys public-key "$IDENTITY_NAME")
+SECRET_SEED=$(stellar keys secret "$IDENTITY_NAME")
+
+# Step 1: Request challenge and save the transaction XDR
+CHALLENGE_RESPONSE=$(curl -s "http://localhost:8080/auth?account=$ACCOUNT_ID")
+CHALLENGE_XDR=$(echo "$CHALLENGE_RESPONSE" | jq -r '.transaction')
+
+# Step 2: Sign the challenge transaction using Stellar CLI
+# Note: The output includes info messages; the signed XDR is on the last line
+SIGNED_CHALLENGE_XDR=$(echo "$CHALLENGE_XDR" | stellar tx sign --sign-with-key "$SECRET_SEED" 2>&1 | tail -1)
+
+# Step 3: Submit the signed challenge and receive JWT token
+curl -X POST "http://localhost:8080/auth" \
+  -H "Content-Type: application/json" \
+  -d "{\"transaction\": \"$SIGNED_CHALLENGE_XDR\"}"
+```
+
+</Tip>
+
+[sep1-ap]: /docs/platforms/anchor-platform/sep-guide/sep1
+[sep-10]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md
diff --git a/docs/platforms/anchor-platform/sep-guide/sep24/README.mdx b/docs/platforms/anchor-platform/sep-guide/sep24/README.mdx
deleted file mode 100644
index 89e4dc5d6..000000000
--- a/docs/platforms/anchor-platform/sep-guide/sep24/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Hosted Deposits and Withdrawals (SEP-24)
-sidebar_position: 90
----
-
-import DocCardList from "@theme/DocCardList";
-
-SEP-24 allows for a means by which wallets and/or exchanges allow the user to directly interact with an on & off-ramp.
-
-<DocCardList />
diff --git a/docs/platforms/anchor-platform/sep-guide/sep24/configuration.mdx b/docs/platforms/anchor-platform/sep-guide/sep24/configuration.mdx
index 279850b2f..cab6ffc4d 100644
--- a/docs/platforms/anchor-platform/sep-guide/sep24/configuration.mdx
+++ b/docs/platforms/anchor-platform/sep-guide/sep24/configuration.mdx
@@ -1,15 +1,15 @@
 ---
 title: "Configuration"
-sidebar_position: 20
+description: "Next, let's modify stellar.toml file created [earlier][sep1-ap]."
 ---
 
 ## Modify a Stellar Info File
 
 Next, let's modify `stellar.toml` file created [earlier][sep1-ap]. Wallets need to know that SEP-24 functionality is supported by your business, and they also need to know all currencies you support.
 
-<CodeExample>
+<CodeGroup>
 
-```toml
+```toml TOML
 # dev.stellar.toml
 ACCOUNTS = ["add your public keys for your distribution accounts here"]
 SIGNING_KEY = "add your signing key here"
@@ -42,17 +42,17 @@ ORG_URL = "Your website"
 ORG_DESCRIPTION = "A description of your organization"
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Note that you'll need to create another file for your production deployment that uses the public network's passphrase, your production service URLs, your Mainnet distribution accounts and signing key, as well as the Mainnet issuing accounts of the assets your service utilizes.
 
-## Enable Hosted Deposits & Withdrawals
+## Enable Hosted Deposits & Withdrawals {#enable-hosted-deposits--withdrawals}
 
 Now you're ready to enable hosted deposits and withdrawals via the SEP-24 API. Specify the following in your `dev.assets.yaml` file, and change the values depending on your preferences. This example asset file will enable support for Circle's USDC and a fiat USD.
 
-<CodeExample>
+<CodeGroup>
 
-```yaml
+```yaml YAML
 # dev.assets.yaml
 items:
   - id: stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5
@@ -98,15 +98,15 @@ items:
           - cash
 ```
 
-</CodeExample>
+</CodeGroup>
 
 The information provided for the `assets` value closely maps to the information that will be exposed to the wallet application using the [`GET /info`][sep24-get-info] SEP-24 endpoint. The Anchor Platform also uses this information to validate requests made to your service.
 
 Add the following variables to your environment file.
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 # dev.env
 // Required
 SEP24_ENABLED=true
@@ -119,7 +119,7 @@ SECRET_SEP24_MORE_INFO_URL_JWT_SECRET="your encryption key shared with your busi
 SEP24_INITIAL_USER_DEADLINE_SECONDS=1209600
 ```
 
-</CodeExample>
+</CodeGroup>
 
 `SEP24_INTERACTIVE_URL_BASE_URL` is the URL that the Anchor Platform will provide to wallet applications when they initiate transactions. Wallet applications will open this URL in a web view inside their app, handing over control of the user experience from the wallet to your business. This URL points to the web widget your business implements. It contains all business-defined logic. We'll dive further into this experience in subsequent sections.
 
@@ -133,9 +133,9 @@ SEP24_INITIAL_USER_DEADLINE_SECONDS=1209600
 
 Wallets should now be able to discover, authenticate, and initiate transactions with your service! Your project and source files should now look something like this.
 
-<CodeExample>
+<CodeGroup>
 
-```
+```text Example
 ├── dev.env
 ├── docker-compose.yaml
 ├── config
@@ -143,13 +143,13 @@ Wallets should now be able to discover, authenticate, and initiate transactions
 │   ├── dev.stellar.toml
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Your environment should now look like the following.
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 # dev.env
 ASSETS_TYPE=file
 ASSETS_VALUE=/home/dev.assets.yaml
@@ -169,7 +169,7 @@ SECRET_SEP24_INTERACTIVE_URL_JWT_SECRET="your encryption key shared with your bu
 SECRET_SEP24_MORE_INFO_URL_JWT_SECRET="your encryption key shared with your business server"
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To test this out, go to the [Stellar Demo Wallet][stellar-demo-wallet].
 
@@ -207,5 +207,5 @@ The demo wallet should be able to find your `stellar.toml` file, authenticate us
 [flyway]: https://documentation.red-gate.com/fd/redgate-flyway-documentation-138346877.html
 [sep-24-ref-ui]: https://github.com/stellar/sep24-reference-ui
 [sep-24-ref]: https://github.com/stellar/anchor-platform/tree/develop/kotlin-reference-server
-[sep1-ap]: ../sep1/README.mdx
-[json-rpc-methods]: ../../api-reference/platform/rpc/methods/README.mdx
+[sep1-ap]: /docs/platforms/anchor-platform/sep-guide/sep1
+[json-rpc-methods]: /docs/platforms/anchor-platform/api-reference/platform/rpc/methods
diff --git a/docs/platforms/anchor-platform/sep-guide/sep24/example.mdx b/docs/platforms/anchor-platform/sep-guide/sep24/example.mdx
index 77854e390..870bd7848 100644
--- a/docs/platforms/anchor-platform/sep-guide/sep24/example.mdx
+++ b/docs/platforms/anchor-platform/sep-guide/sep24/example.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Example"
-sidebar_position: 40
+description: "Integrating with the Anchor Platform involves three key areas."
 ---
 
 Integrating with the Anchor Platform involves three key areas:
@@ -27,9 +27,9 @@ The Anchor Platform adds a JWT `token` query parameter to the business's URL giv
 
 The decoded contents of the `token` will look something like this:
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 {
   "jti": "e26cf292-814f-4918-9b40-b4f76a300f98",
   "sub": "GB244654NC6YPEFU3AY7L25COGES445P3Q63W6Q76JHR3UBJMLT2XBOB:1234567",
@@ -42,13 +42,13 @@ The decoded contents of the `token` will look something like this:
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Note that the `sub` value identifies the user using a Stellar account and integer. This is what the value will be when custodial applications that use an omnibus account authenticate with your service. When non-custodial wallets authenticate, the token may look slightly different.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 {
   "jti": "e26cf292-814f-4918-9b40-b4f76a300f98",
   "sub": "GB244654NC6YPEFU3AY7L25COGES445P3Q63W6Q76JHR3UBJMLT2XBOB",
@@ -62,7 +62,7 @@ Note that the `sub` value identifies the user using a Stellar account and intege
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
 The `sub` value here only contains a public key to identify the user, and the `data.client_domain` field identifies the wallet application used to authenticate.
 
@@ -70,9 +70,9 @@ In both cases, all information in the `data` object is optional, and will only b
 
 Let's add a backend server to our compose file that will be used to verify the token and create authenticated web sessions for users initiating transactions.
 
-<CodeExample>
+<CodeGroup>
 
-```yaml
+```yaml YAML
 # docker-compose.yaml
 ---
 business-server:
@@ -85,13 +85,13 @@ business-server:
     - platform-server
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Let's create a simple Docker container for our application.
 
-<CodeExample>
+<CodeGroup>
 
-```docker
+```docker Dockerfile
 FROM node:19
 
 WORKDIR /home
@@ -101,25 +101,25 @@ RUN npm install
 CMD ["node", "server.js"]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Now let's create a minimal NodeJS application.
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 yarn init -y
 yarn add express jsonwebtoken
 touch server.js
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Below is an example of a backend server authenticating a user using NodeJS.
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 # server.js
 const express = require("express");
 const jwt = require("jsonwebtoken");
@@ -194,13 +194,13 @@ app.listen(port, () => {
 });
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Run this with the platform server and database and initiate a new transaction with the [demo wallet][stellar-demo-wallet]. Then, we'll send the token to our server.
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 curl \
   -X POST \
   -H 'Content-Type: application/json' \
@@ -208,15 +208,15 @@ curl \
   http://localhost:8081/session | jq
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## Providing Updates to the Platform
 
 Let's create an endpoint for our business server that accepts the information collected in our UI.
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 # server.js
 
 // Production systems should either let the Anchor Platform generate its own memos
@@ -311,15 +311,15 @@ async function updatePlatformTransaction(requestBody) {
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
 This will update the Anchor Platform's database with the information provided and enable wallet applications to fetch this updated information so it can relay it back to the user. You should have already informed the user of the transaction's amounts and that your business's is waiting for the on-chain payment to arrive, but providing these updates allows users to view their transactions' statuses through their mobile application without opening the business' UI again.
 
-:::note
+<Note>
 
 At this time, the Anchor Platform does not send notifications to the wallet application when transaction statuses change, however, it is on our roadmap to add these notifications or "callback requests" so that wallet applications do not have to poll the Anchor Platform for updates.
 
-:::
+</Note>
 
 ## Fetching Updates from the Platform
 
@@ -336,9 +336,9 @@ While streaming transaction status changes from a Kafka cluster may be a more ro
 
 First, let's configure the Anchor Platform to observe the Stellar network for incoming payments.
 
-<CodeExample>
+<CodeGroup>
 
-```yaml
+```yaml YAML
 # docker-compose.yml
 ---
 stellar-observer:
@@ -352,26 +352,26 @@ stellar-observer:
     - db
 ```
 
-</CodeExample>
+</CodeGroup>
 
 The `--stellar-observer` command starts a process that monitors the distribution accounts configured in your `config.yaml` file for withdrawal payments.
 
 If a payment is sent to one of these accounts and the memo attached to the transaction matches a `memo` value provided or generated by the Anchor Platform, the Anchor Platform will consider the transaction that memo is associated with as received and update the transaction's status to `pending_anchor`. It does this by making a `JSON-RPC API` request, so we need to configure the URL it should use.
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 # dev.env
 PLATFORM_API_BASE_URL=http://platform-server:8085
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Let's make some additions to the `server.js` file so we can poll the Anchor Platform for our expected payments.
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 // server.js
 ...
 /*
@@ -406,7 +406,7 @@ async function getPlatformTransaction(transactionId) {
 })()
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## Full Example Implementation
 
diff --git a/docs/platforms/anchor-platform/sep-guide/sep24/faq.mdx b/docs/platforms/anchor-platform/sep-guide/sep24/faq.mdx
index 5972a06cf..30c6ceb41 100644
--- a/docs/platforms/anchor-platform/sep-guide/sep24/faq.mdx
+++ b/docs/platforms/anchor-platform/sep-guide/sep24/faq.mdx
@@ -1,6 +1,6 @@
 ---
 title: "FAQ"
-sidebar_position: 50
+description: "As part of the flow, once a user makes a request, i.e."
 ---
 
 ### How To Use JWTs?
@@ -20,11 +20,11 @@ Currently, it's recommended to provide fees/exchange rates in the iFrame/web vie
 
 [SEP-24] standard provides a `/fee` endpoint to allow businesses to set static fees for their transactions. However, it's not currently supported by the Anchor Platform.
 
-:::note
+<Note>
 
 /fee endpoint will be deprecated in the future.
 
-:::
+</Note>
 
 ### How to identify the user account?
 
@@ -36,4 +36,4 @@ Utilize the `data.client_domain` attributes within the JWT token. In the presenc
 
 [sep-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
 [sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[clients]: ../sep10/README.mdx
+[clients]: /docs/platforms/anchor-platform/sep-guide/sep10
diff --git a/docs/platforms/anchor-platform/sep-guide/sep24/getting-started.mdx b/docs/platforms/anchor-platform/sep-guide/sep24/getting-started.mdx
index c62009d36..73468f048 100644
--- a/docs/platforms/anchor-platform/sep-guide/sep24/getting-started.mdx
+++ b/docs/platforms/anchor-platform/sep-guide/sep24/getting-started.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Getting Started"
-sidebar_position: 10
+description: "This guide will walk you through configuring and integrating with the Anchor Platform for the purpose of building an on & off-ramp service compatible with..."
 ---
 
 This guide will walk you through configuring and integrating with the Anchor Platform for the purpose of building an on & off-ramp service compatible with [SEP-24][sep-24], the ecosystem's standardized protocol for hosted deposits and withdrawals.
@@ -28,7 +28,7 @@ The customer can then use the digital asset on the Stellar network for remittanc
 5. Once the anchor receives the payment, the customer receives the withdrawn funds via bank transfer.
 
 [sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[installation-ap]: ../../admin-guide/getting-started.mdx
-[sep1-ap]: ../sep1/README.mdx
-[sep10-ap]: ../sep10/README.mdx
-[sep45-ap]: ../sep45/README.mdx
+[installation-ap]: ../../admin-guide/getting-started
+[sep1-ap]: /docs/platforms/anchor-platform/sep-guide/sep1
+[sep10-ap]: /docs/platforms/anchor-platform/sep-guide/sep10
+[sep45-ap]: /docs/platforms/anchor-platform/sep-guide/sep45
diff --git a/docs/platforms/anchor-platform/sep-guide/sep24/index.mdx b/docs/platforms/anchor-platform/sep-guide/sep24/index.mdx
new file mode 100644
index 000000000..818bef3a4
--- /dev/null
+++ b/docs/platforms/anchor-platform/sep-guide/sep24/index.mdx
@@ -0,0 +1,37 @@
+---
+title: Hosted Deposits and Withdrawals (SEP-24)
+description: "SEP-24 allows for a means by which wallets and/or exchanges allow the user to directly interact with an on & off-ramp."
+---
+
+<CardGroup cols={2}>
+  <Card title="Getting Started" icon="file-lines" href="/docs/platforms/anchor-platform/sep-guide/sep24/getting-started">
+
+    This guide will walk you through configuring and integrating with the Anchor Platform for the purpose of building an on & off-ramp service compatible with...
+
+  </Card>
+  <Card title="Configuration" icon="file-lines" href="/docs/platforms/anchor-platform/sep-guide/sep24/configuration">
+
+    Next, let's modify stellar.toml file created earlier.
+
+  </Card>
+  <Card title="Integration" icon="file-lines" href="/docs/platforms/anchor-platform/sep-guide/sep24/integration">
+
+    One of the main points of interaction with the Anchor Platform is notifying the Anchor Platform about events related to the transaction.
+
+  </Card>
+  <Card title="Example" icon="file-lines" href="/docs/platforms/anchor-platform/sep-guide/sep24/example">
+
+    Integrating with the Anchor Platform involves three key areas.
+
+  </Card>
+  <Card title="FAQ" icon="file-lines" href="/docs/platforms/anchor-platform/sep-guide/sep24/faq">
+
+    As part of the flow, once a user makes a request, i.e.
+
+  </Card>
+  <Card title="Set Up a Production Server" icon="file-lines" href="/docs/platforms/anchor-platform/sep-guide/sep24/setting-up-production-server">
+
+    Once the test server is live and you have tested both deposit and withdraw flows, it's time to get started with the real deploy connected to real KYC and...
+
+  </Card>
+</CardGroup>
diff --git a/docs/platforms/anchor-platform/sep-guide/sep24/integration.mdx b/docs/platforms/anchor-platform/sep-guide/sep24/integration.mdx
index 3e514f5f8..7ee0960d0 100644
--- a/docs/platforms/anchor-platform/sep-guide/sep24/integration.mdx
+++ b/docs/platforms/anchor-platform/sep-guide/sep24/integration.mdx
@@ -1,16 +1,16 @@
 ---
 title: "Integration"
-sidebar_position: 30
+description: "One of the main points of interaction with the Anchor Platform is notifying the Anchor Platform about events related to the transaction."
 ---
 
-import Security from "../../admin-guide/component/security/security.mdx";
-import UsingApiKey from "../../admin-guide/component/security/api_key.mdx";
-import UsingJwt from "../../admin-guide/component/security/jwt.mdx";
-import Rpc from "../../admin-guide/component/rpc/rpc.mdx";
-import RpcRequest from "../../admin-guide/component/rpc/request.mdx";
-import RpcResponse from "../../admin-guide/component/rpc/response.mdx";
-import RpcError from "../../admin-guide/component/rpc/error.mdx";
-import Observer from "../../admin-guide/component/observer/observer.mdx";
+import Security from "/snippets/anchor-platform/security.mdx";
+import UsingApiKey from "/snippets/anchor-platform/api_key.mdx";
+import UsingJwt from "/snippets/anchor-platform/jwt.mdx";
+import Rpc from "/snippets/anchor-platform/rpc.mdx";
+import RpcRequest from "/snippets/anchor-platform/request.mdx";
+import RpcResponse from "/snippets/anchor-platform/response.mdx";
+import RpcError from "/snippets/anchor-platform/error.mdx";
+import Observer from "/snippets/anchor-platform/observer.mdx";
 
 One of the main points of interaction with the Anchor Platform is notifying the Anchor Platform about events related to the transaction.
 
@@ -73,7 +73,7 @@ SEP-24 deposit flow diagram defines sequence/rules of the transaction's status t
 
 [![sep24 deposit flow](/assets/ap/sep24-deposit-flow-diagram.png)](/assets/ap/sep24-deposit-flow-diagram.png)
 
-:::tip
+<Tip>
 
 Statuses in <span style={{color: "green"}}>green</span> are mandatory and define the shortest way.
 
@@ -81,15 +81,15 @@ Statuses in <span style={{color: "#B0BF1A"}}>yellow</span> are optional and can
 
 Statuses in <span style={{color: "red"}}>red</span> mean the transaction is in an error status or it has expired.
 
-:::
+</Tip>
 
 ### Ready to Receive Funds
 
 The first step of the deposit flow after starting the deposit itself is collecting KYC. It's usually done in the web-app, but can also be optionally provided by the wallet application, using [SEP-9]. Once the necessary KYC is collected, a `request_offchain_funds` JSON-RPC request should be made.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // request-offchain-funds.json
 [
   {
@@ -119,7 +119,7 @@ The first step of the deposit flow after starting the deposit itself is collecti
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 - `amount_in` is the amount the user has to sent to the business.
 - `amount_out` is the amount the user will receive.
@@ -130,35 +130,35 @@ Information abouts amounts (in/out/fee) is required if you want to move the tran
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh request-offchain-funds.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::tip
+<Tip>
 
 When the KYC process is long (for example, ID verification), it's advised to first set the transaction status to `pending_anchor` by using `notify_interactive_flow_completed` JSON-RPC request. This will indicate to the user that KYC is being processed.
 
-:::
+</Tip>
 
 ### Processing KYC Information
 
-:::tip
+<Tip>
 
 This step is optional. Most businesses don't use it. You can skip it and go to the [next step](#funds-received).
 
 Using this status is recommended when KYC verification may need to be performed asynchronously.
 
-:::
+</Tip>
 
 You **must** specify the `amount_x` fields.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // kyc-in-process.json
 [
   {
@@ -188,25 +188,25 @@ You **must** specify the `amount_x` fields.
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh kyc-in-process.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Funds Received
 
 If offchain funds were received, you'll want to provide an updated transaction information.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // offchain-funds-received.json
 [
   {
@@ -235,7 +235,7 @@ If offchain funds were received, you'll want to provide an updated transaction i
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 - `funds_received_at` is the date and time of receiving funds
 - `external_transaction_id` is the ID of transaction on external network
@@ -244,21 +244,21 @@ The amount fields are optional. If skipped, the values from previous JSON-RPC re
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh offchain-funds-received.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Waiting For User Funds
 
 In a real world, the transfer confirmation process may take time. In such cases, transactions should be set to a new status indicating that the confirmation of the transfer has been received but the funds themselves have not been received yet.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // offchain-funds-sent.json
 [
   {
@@ -275,25 +275,25 @@ In a real world, the transfer confirmation process may take time. In such cases,
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh offchain-funds-sent.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Sending Onchain Funds
 
 Next, send a transaction on the Stellar network to fulfill a user request. After the transaction completion, it's necessary to send the `notify_onchain_funds_sent` JSON-RPC request to notify a user that the funds were successfully sent.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // onchain-funds-sent.json
 [
   {
@@ -309,19 +309,19 @@ Next, send a transaction on the Stellar network to fulfill a user request. After
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 - `stellar_transaction_id` is the transaction id on Stellar network of the transfer
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh onchain-funds-sent.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
 After this JSON-RPC request, the transaction will be transferred to the `completed` status.
 
@@ -329,9 +329,9 @@ After this JSON-RPC request, the transaction will be transferred to the `complet
 
 This status has to be set if a payment requires an asset trustline that wasn't configured by the user. There are two ways of how the transaction may be moved to the `pending_trust` status. The first one is when the business server detects that the trustline isn't configured. The second one is when the business itself detects that the trustline is missing and wants to notify the user that it has to be configured. To move the transaction to the `pending_trust` status, it's necessary to make the following JSON-RPC request:
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // request-trust.json
 [
   {
@@ -346,31 +346,31 @@ This status has to be set if a payment requires an asset trustline that wasn't c
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh request-trust.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::info
+<Info>
 
 The business server periodically checks if the trustline was configured. If it was, it may send a payment and change the status of the transaction to `pending_stellar`.
 
-:::
+</Info>
 
 ### Trust Set
 
 This status has to be set if the business has detected that the trustline was or wasn't configured by user.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // trust-set.json
 [
   {
@@ -386,33 +386,33 @@ This status has to be set if the business has detected that the trustline was or
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 - `success` flag which defines if trustline was or wasn't configured by user
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh trust-set.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::info
+<Info>
 
 Depending on the `success` flag, the status of the transaction will be changed to `pending_stellar` if the trustline was set, or to `pending_anchor` if it wasn't.
 
-:::
+</Info>
 
 ### Sending Refund
 
 There is a possibility to send funds back to the user (refund). You can refund the whole sum(full refund) or do a set of partial refunds. Also, if user sent more money than expected, you can refund a part of the sum back to the user and send the rest as onchain funds.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // refund-sent.json
 [
   {
@@ -438,23 +438,23 @@ There is a possibility to send funds back to the user (refund). You can refund t
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh refund-sent.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::info
+<Info>
 
 If a sum of refunds is less than `amount_in`, the status of the transaction will be set to `pending_anchor`. Only if the sum of refunds is equal to `amount_in`, the status of the transaction will be set to `refunded`.
 
-:::
+</Info>
 
 ### Refund Pending
 
@@ -464,9 +464,9 @@ It's similar to [Refund sent](#refund-sent), but it handles a case when a refund
 
 If you encounter an unrecoverable error when processing the transaction, it's required to set the transaction status to `error`. You can use the message field to describe the error details.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // transaction-error.json
 [
   {
@@ -481,31 +481,31 @@ If you encounter an unrecoverable error when processing the transaction, it's re
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh transaction-error.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::tip
+<Tip>
 
 If a user has made a transfer, you should do a transaction recovery, and then you can retry processing the transaction or initiate a refund.
 
-:::
+</Tip>
 
 ### Expired Transaction
 
 Your business may want to handle abandoned transactions by expiring those have remained inactive for a certain period. To achieve this, check the transaction status using the `GET /transactions` endpoint and sort the results by the `user_action_required_by` timestamp. If the timestamp has passed, manually execute the appropriate logic, such as expiring the transaction or initiating an auto-refund, based on the transaction's current status. For example, to expire transaction business should change the transaction status to `expired`:
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // transaction-expired.json
 [
   {
@@ -520,31 +520,31 @@ Your business may want to handle abandoned transactions by expiring those have r
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh transaction-expired.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::tip
+<Tip>
 
 This JSON-RPC method can't be used after the user has made a transfer.
 
-:::
+</Tip>
 
 ### On-Hold Transaction
 
 In rare cases, you may want to pause current transaction and request more information from the user (after the transfer has been received). This could be used for compliance use cases.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // transaction-hold.json
 [
   {
@@ -559,25 +559,25 @@ In rare cases, you may want to pause current transaction and request more inform
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh transaction-hold.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Transaction Recovery
 
 Transaction status can be changed from `error/expired` to `pending_anchor`. After recovery, you can refund the received assets or proceed with processing of the transaction. To recover a transaction, it's necessary to make the following JSON-RPC request:
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // transaction-recovery.json
 [
   {
@@ -592,17 +592,17 @@ Transaction status can be changed from `error/expired` to `pending_anchor`. Afte
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh transaction-recovery.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## Updating Withdrawal Transaction Via JSON-RPC
 
@@ -610,7 +610,7 @@ This diagram defines a sequence/rules of transaction's status transition for SEP
 
 [![sep24 withdrawal flow](/assets/ap/sep24-withdrawal-flow-diagram.png)](/assets/ap/sep24-withdrawal-flow-diagram.png)
 
-:::tip
+<Tip>
 
 Statuses in <span style={{color: "green"}}>green</span> are mandatory and define the shortest way.
 
@@ -618,19 +618,19 @@ Statuses in <span style={{color: "#B0BF1A"}}>yellow</span> are optional and can
 
 Statuses in <span style={{color: "red"}}>red</span> mean the transaction is in an error status or it has expired.
 
-:::
+</Tip>
 
 Once the deposit flow is finished, implementing the withdrawal is straightforward. Some parts of the flow are similar and can be reused.
 
 The starting point both for withdrawal and for deposit is the same.
 
-### Ready to Receive Funds
+### Ready to Receive Funds {#ready-to-receive-funds-1}
 
 Similar to deposit, the next step is to notify the user that the anchor is ready to receive funds. However, as your service will be receiving transactions over the Stellar network, the update will look differently.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // request-onchain-funds.json
 [
   {
@@ -663,7 +663,7 @@ Similar to deposit, the next step is to notify the user that the anchor is ready
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 - `memo` Value of memo to attach to the transaction
 - `memo_type` Type of memo that the anchor should attach to the transaction
@@ -671,15 +671,15 @@ Similar to deposit, the next step is to notify the user that the anchor is ready
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh request-onchain-funds.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::tip
+<Tip>
 
 Setting `memo`, `memo_type`, and `destination_account` is optional.
 
@@ -687,25 +687,24 @@ If integration with a third-party custodian is enabled, the Anchor Platform can
 
 If your business manages the assets, the Anchor Platform can generate memos for you. When the status is changed to `pending_user_transfer_start`, the Anchor Platform sets the `memo` and `memo_type` automatically (only if it's not included in the request).
 
-:::
-
-:::note
+</Tip>
+<Note>
 
 The Stellar account that will be used to receive funds should be configured.
 
-:::
+</Note>
 
-### Processing KYC Information
+### Processing KYC Information {#processing-kyc-information-1}
 
 This step is optional, and it's similar to [Processing KYC Information](#processing-kyc-information) of the deposit flow.
 
-### Funds Received
+### Funds Received {#funds-received-1}
 
 If onchain funds were received, you need to provide amounts and change the status of the transaction to `pending_anchor`.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // onchain-funds-received.json
 [
   {
@@ -730,31 +729,31 @@ If onchain funds were received, you need to provide amounts and change the statu
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh onchain-funds-received.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::tip
+<Tip>
 
 This method will be called automatically by the Stellar payment observer when it detects that onchain funds have been received.
 
-:::
+</Tip>
 
 ### Amount Updated
 
 If onchain funds were received, but for some reason the `amount_in` differs from specified in the interactive flow (`amount_expected`), you can update `amount_out` and `fee_details` to make them correspond to the actual `amount_in`. The status of the transaction in this case won't be changed and will be equal to `pending_anchor`.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // amounts-updated.json
 [
   {
@@ -775,31 +774,31 @@ If onchain funds were received, but for some reason the `amount_in` differs from
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh amounts-updated.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::note
+<Note>
 
 Only `amount_out` and `fee_details` can be updated using this JSON-RPC request, and you don't need to specify the assets of the amounts.
 
-:::
+</Note>
 
 ### Offchain Funds Sent
 
 To complete the transaction and change its status to `completed`, you need to make the `notify_offchain_funds_sent` JSON-RPC request.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // offchain-funds-sent.json
 [
   {
@@ -816,25 +815,25 @@ To complete the transaction and change its status to `completed`, you need to ma
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh offchain-funds-sent.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Offchain Funds Available
 
 You can move transaction status to `pending_user_transfer_complete` if offchain funds were sent, and if it's ready for the user / recipient to pick it up.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // offchain-funds-available.json
 [
   {
@@ -850,25 +849,25 @@ You can move transaction status to `pending_user_transfer_complete` if offchain
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh offchain-funds-available.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Offchain Funds Pending
 
 Another option is to move the transaction's status to `pending_external`. This status means that the payment has been submitted to an external network, but is not yet confirmed.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // offchain-funds-pending.json
 [
   {
@@ -884,35 +883,35 @@ Another option is to move the transaction's status to `pending_external`. This s
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh offchain-funds-pending.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Refund Sent
 
 The refund logic works in the same way as for the deposit flow. For more details, see [Refund Sent](#refund-sent) of the deposit flow.
 
-### Transaction Error
+### Transaction Error {#transaction-error-1}
 
 Works in the same manner as for the deposit flow. For more details, see [Transaction Error](#transaction-error) of the deposit flow.
 
-### Expired Transaction
+### Expired Transaction {#expired-transaction-1}
 
 Works in the same manner as for the deposit flow. For more details, see [Expired Transaction](#expired-transaction) of the deposit flow.
 
-### On-Hold Transaction
+### On-Hold Transaction {#on-hold-transaction-1}
 
 Works in the same manner as for the deposit flow. For more details, see [On-Hold Transaction](#on-hold-transaction) of the deposit flow.
 
-### Transaction Recovery
+### Transaction Recovery {#transaction-recovery-1}
 
 Works in the same manner as for the deposit flow. For more details, see [Transaction Recovery](#transaction-recovery) of the deposit flow.
 
@@ -922,6 +921,6 @@ Works in the same manner as for the deposit flow. For more details, see [Transac
 
 [sep-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
 [sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[event-handling]: ../../admin-guide/events/README.mdx
-[rate-callback]: ../../api-reference/callbacks/README.mdx
-[json-rpc-methods]: ../../api-reference/platform/rpc/methods/README.mdx
+[event-handling]: /docs/platforms/anchor-platform/admin-guide/events
+[rate-callback]: /docs/platforms/anchor-platform/api-reference/callbacks
+[json-rpc-methods]: /docs/platforms/anchor-platform/api-reference/platform/rpc/methods
diff --git a/docs/platforms/anchor-platform/sep-guide/sep24/setting-up-production-server.mdx b/docs/platforms/anchor-platform/sep-guide/sep24/setting-up-production-server.mdx
index 53e6af849..7d750fe45 100644
--- a/docs/platforms/anchor-platform/sep-guide/sep24/setting-up-production-server.mdx
+++ b/docs/platforms/anchor-platform/sep-guide/sep24/setting-up-production-server.mdx
@@ -1,6 +1,6 @@
 ---
 title: Set Up a Production Server
-sidebar_position: 60
+description: "Once the test server is live and you have tested both deposit and withdraw flows, it's time to get started with the real deploy connected to real KYC and..."
 ---
 
 Once the test server is live and you have tested both deposit and withdraw flows, it's time to get started with the real deploy connected to real KYC and real banking rails providers. Before using any banking APIs, it's critical that you perform a full security audit on the system to make sure that there aren't any vulnerabilities.
@@ -9,44 +9,44 @@ Once the test server is live and you have tested both deposit and withdraw flows
 
 Make sure to keep the test server up, and deploy the production (mainnet) system in a separate environment. Having two deploys allows you to validate new features on the testnet before moving them to the final production deploy. You can also have a third staging environment if there's a big team working on this codebase and/or there will be many pushes to be tested internally before sharing with other institutions.
 
-To switch to Stellar's public (mainnet) network, all you have to do is change the network [passphrase](../../../../networks/README.mdx#network-passphrases) (for authenticating requests) and [Horizon URL](https://horizon.stellar.org).
+To switch to Stellar's public (mainnet) network, all you have to do is change the network [passphrase](/docs/networks#network-passphrases) (for authenticating requests) and [Horizon URL](https://horizon.stellar.org).
 
 You can copy your existing development configs to create a production configuration.
 
 First, you need to change your info file (`stellar.toml`):
 
-<CodeExample>
+<CodeGroup>
 
-```toml
+```toml TOML
 # stellar.toml
 NETWORK_PASSPHRASE = "Public Global Stellar Network ; September 2015"
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Next, change your Anchor Platform configuration in `production.env` file:
 
 ### For Horizon server connection:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 # production.env STELLAR_NETWORK_NETWORK="Public"
 STELLAR_NETWORK_HORIZON_URL="https://horizon.stellar.org"
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### For Stellar RPC server connection:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 # production.env STELLAR_NETWORK_NETWORK="Public"
 STELLAR_NETWORK_RPC_URL="https://mainnet.sorobanrpc.com"
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## Connecting to Real KYC
 
@@ -56,7 +56,7 @@ How you handle KYC is up to you: there are many services that provide KYC soluti
 
 Some countries require different KYC fields depending on the amount to be deposited or withdrawn. If that's the case in your jurisdiction and you need to adapt your KYC forms based on the deposit or withdrawal amount, simply add an amount field before the KYC form, and make sure that the KYC fields are updated based on that value.
 
-KYC information should be linked to the session created through [Stellar Web Authentication](../sep10/README.mdx) and, consequently, to the user, so you only need to ask the user for it once. After the first KYC flow is complete, a user shouldn't have to input the information again.
+KYC information should be linked to the session created through [Stellar Web Authentication](/docs/platforms/anchor-platform/sep-guide/sep10) and, consequently, to the user, so you only need to ask the user for it once. After the first KYC flow is complete, a user shouldn't have to input the information again.
 
 Make sure the errors and validation messages are clear and include instructions for what to do next to ensure a good user experience and increase the KYC conversion rate. You should also localize messages based on the user's language and location.
 
@@ -66,7 +66,7 @@ Pre-filling the KYC form is a great way to reduce the friction of getting starte
 
 All fields from [SEP-9](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md) can be sent by wallets in the previously mentioned endpoints, but the most common are: email, first name, last name and phone number. Also, you should still enable the pre-filled fields to be editable, since the user might have inputted a different name in the Wallet's sign-up process, and could want to edit it before finalizing the Anchor's KYC process.
 
-All SEP-9 data that was sent from the wallet is a part of the [Interactive JWT](./faq.mdx#how-to-use-jwts), send by the Anchor Platform
+All SEP-9 data that was sent from the wallet is a part of the [Interactive JWT](./faq#how-to-use-jwts), send by the Anchor Platform
 
 ## Connecting to Real Banking Rails
 
diff --git a/docs/platforms/anchor-platform/sep-guide/sep31/README.mdx b/docs/platforms/anchor-platform/sep-guide/sep31/README.mdx
deleted file mode 100644
index cf9b2dda9..000000000
--- a/docs/platforms/anchor-platform/sep-guide/sep31/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Cross-Border Payments (SEP-31)
-sidebar_position: 100
----
-
-import DocCardList from "@theme/DocCardList";
-
-SEP-31 allows for a means by which wallets and/or exchanges interact with Stellar's existing set of send-side services.
-
-<DocCardList />
diff --git a/docs/platforms/anchor-platform/sep-guide/sep31/configuration.mdx b/docs/platforms/anchor-platform/sep-guide/sep31/configuration.mdx
index 05dab1a9d..7c371f98d 100644
--- a/docs/platforms/anchor-platform/sep-guide/sep31/configuration.mdx
+++ b/docs/platforms/anchor-platform/sep-guide/sep31/configuration.mdx
@@ -1,15 +1,15 @@
 ---
 title: "Configuration"
-sidebar_position: 20
+description: "Let's start by modifying our stellar.toml file created [earlier][sep1-ap]."
 ---
 
 ## Modify a Stellar Info File
 
 Let's start by modifying our `stellar.toml` file created [earlier][sep1-ap]. Wallets need to know that SEP-31 functionality is supported by your business, and they also need to know all currencies you support.
 
-<CodeExample>
+<CodeGroup>
 
-```toml
+```toml TOML
 # dev.stellar.toml
 ACCOUNTS = ["add your public keys for your distribution accounts here"]
 SIGNING_KEY = "add your signing key here"
@@ -31,7 +31,7 @@ ORG_URL = "Your website"
 ORG_DESCRIPTION = "A description of your organization"
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Note that you'll need to create another file for your production deployment that uses the public network's passphrase, your production service URLs, your mainnet distribution accounts and signing key, as well as the mainnet issuing accounts of the assets your service utilizes.
 
@@ -39,9 +39,9 @@ Note that you'll need to create another file for your production deployment that
 
 Now you're ready to enable cross-border payments the SEP-31 API. Specify the following in your `dev.assets.yaml` file.
 
-<CodeExample>
+<CodeGroup>
 
-```yaml
+```yaml YAML
 # dev.assets.yaml
 items:
   - id: stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5
@@ -58,7 +58,7 @@ items:
           - ACH
 ```
 
-</CodeExample>
+</CodeGroup>
 
 The information provided in the `sep31` and `send` objects closely map to the information that will be exposed to the wallet application using the [`GET /info`][sep31-get-info] SEP-31 endpoint. The Anchor Platform also uses this information to validate requests made to your service. `sep31.fields.transaction` should be left empty and will be removed in a future release, but you can adjust the `send.min_amount` and `send.max_amount` values according to your service's limits.
 
@@ -66,40 +66,40 @@ The `sep31.quotes_supported` and `sep31.quotes_required` determine whether or no
 
 Add the following variable to your environment file.
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 # dev.env
 SEP31_ENABLED=true
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Senders should now be able to discover, authenticate, and initiate transactions with your service! Run the following command to start the Anchor Platform.
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 docker compose up
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Check that your API is live.
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 curl http://localhost:8080/sep31/info | jq
 ```
 
-</CodeExample>
+</CodeGroup>
 
 You should get the following.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 {
   "receive": {
     "USDC": {
@@ -116,7 +116,7 @@ You should get the following.
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## Enable the Customer KYC API
 
@@ -126,41 +126,41 @@ See the [Anchor Platform KYC API specification][platform-api-kyc] for details on
 
 To make this API available to clients, lets add the service URL to our Stellar Info File.
 
-<CodeExample>
+<CodeGroup>
 
-```toml
+```toml TOML
 # dev.stellar.toml
 KYC_SERVER = "http://localhost:8080/sep12"
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Lets enable it in our environment too.
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 # dev.env
 SEP12_ENABLED=true
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Finally, we have to define your business' customer types. Each type of customer requires different a set of KYC information. For example, you can offer your cross-border payments service in two distinct regulatory jurisdictions, so customers in different jurisdictions have different KYC requirements and would be represented using different types.
 
-:::info
+<Info>
 
 Currently, customer types must be mutually exclusive, meaning a customer cannot be more than one type.
 
 This limitation is in place because the Anchor Platform cannot validate whether a customer is approved for a specific type of transaction, such as one sending a large amount. It can only validate that a customer is approved for one of the customer types defined. This limitation will be removed in a future release.
 
-:::
+</Info>
 
 In this guide, we'll only have two types, a sending customer type and a receiving customer type. Currently, our customer types are defined in our assets configuration, but this will change in a future release.
 
-<CodeExample>
+<CodeGroup>
 
-```yaml
+```yaml YAML
 # dev.assets.yaml
 sep31:
   sep12:
@@ -174,23 +174,23 @@ sep31:
           description: customers receiving from senders
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Let's ping the info endpoint again to verify. After `docker compose up`, run the following command:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 curl http://localhost:8080/sep31/info | jq
 ```
 
-</CodeExample>
+</CodeGroup>
 
 You should get the following:
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 {
   "receive": {
     "USDC": {
@@ -207,7 +207,7 @@ You should get the following:
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## Enable the RFQ API
 
@@ -217,9 +217,9 @@ The Anchor Platform provides the [SEP-38 RFQ API][sep38] to senders for this pur
 
 To make this API available to clients, lets add the service URL to our Stellar Info File.
 
-<CodeExample>
+<CodeGroup>
 
-```toml
+```toml TOML
 # dev.stellar.toml
 DIRECT_PAYMENT_SERVER = "http://localhost:8080/sep31"
 WEB_AUTH_ENDPOINT = "http://localhost:8080/auth"
@@ -227,24 +227,24 @@ KYC_SERVER = "http://localhost:8080/sep12"
 QUOTE_SERVER = "http://localhost:8080/sep38"
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Lets enable it in our environment too.
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 # dev.env
 SEP38_ENABLED=true
 ```
 
-</CodeExample>
+</CodeGroup>
 
 We also need to enable USDC to be used in this API, as well as add an off-chain asset it can be exchanged with.
 
-<CodeExample>
+<CodeGroup>
 
-```yaml
+```yaml YAML
 # dev.assets.yaml
 items:
   - id: stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5
@@ -278,23 +278,23 @@ items:
           description: Have BRL sent directly to your bank account.
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Let's test that your RFQ API is live! Following `docker compose up`:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 curl http://localhost:8080/sep38/info | jq
 ```
 
-</CodeExample>
+</CodeGroup>
 
 You should get the following:
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 {
   "assets": [
     {
@@ -314,15 +314,15 @@ You should get the following:
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## Configure Callback API Authentication
 
 Just as your business will need to make requests to the Anchor Platform, the Anchor Platform will need to make requests to your business. Let's add authentication to these requests as well.
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 # dev.env
 CALLBACK_API_BASE_URL=http://server:8081
 CALLBACK_API_AUTH_TYPE=jwt
@@ -330,15 +330,15 @@ CALLBACK_API_AUTH_JWT_EXPIRATION_MILLISECONDS=30000
 SECRET_CALLBACK_API_AUTH_SECRET=<your jwt encryption key>
 ```
 
-</CodeExample>
+</CodeGroup>
 
 `CALLBACK_API_BASE_URL` uses `server` instead of `localhost` as the host because the Anchor Platform will be making requests to your business server from within the local network created by docker compose. When configuring your service in a staging or production environment, make sure to update your service urls.
 
 We'll define the server that implements the endpoints defined in the Callback API in the following section.
 
 [sep31-get-info]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md#get-info
-[sep1-ap]: ../sep1/README.mdx
-[get-rates-api]: ../../api-reference/callbacks/get-rates.api.mdx
+[sep1-ap]: /docs/platforms/anchor-platform/sep-guide/sep1
+[get-rates-api]: /docs/platforms/anchor-platform/api-reference/callbacks/get-rates
 [sep38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
 [sep38-post-quote]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md#post-quote
-[platform-api-kyc]: ../../api-reference/callbacks/get-customer.api.mdx
+[platform-api-kyc]: /docs/platforms/anchor-platform/api-reference/callbacks/get-customer
diff --git a/docs/platforms/anchor-platform/sep-guide/sep31/getting-started.mdx b/docs/platforms/anchor-platform/sep-guide/sep31/getting-started.mdx
index 8bfdb162a..943fc1ec9 100644
--- a/docs/platforms/anchor-platform/sep-guide/sep31/getting-started.mdx
+++ b/docs/platforms/anchor-platform/sep-guide/sep31/getting-started.mdx
@@ -1,22 +1,22 @@
 ---
 title: "Getting Started"
-sidebar_position: 10
+description: "This guide will walk you through configuring and integrating with the Anchor Platform for the purpose of building a cross-border payments recieve-side..."
 ---
 
 This guide will walk you through configuring and integrating with the Anchor Platform for the purpose of building a cross-border payments recieve-side service compatible with [SEP-31][sep-31], the ecosystem's standardized protocol for cross-border payments.
 
 By leveraging the Anchor Platform's support for SEP-31, businesses make their service compatible with Stellar's existing set of send-side services.
 
-:::info
+<Info>
 
 As we improve the documentation, parts of this guide that are relevant to other use cases may be moved into their own sections.
 
-:::
+</Info>
 
 Before continuing with this section, make sure that you have already [installed][installation-ap] the Anchor Platform and configured the necessary features required by SEP-31: [SEP-1 (Stellar Info File)][sep1-ap], [SEP-10 (Stellar Authentication)][sep10-ap] and [SEP-45 (Stellar Web Authentication for contract account)][sep45-ap].
 
 [sep-31]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md
-[installation-ap]: ../../admin-guide/getting-started.mdx
-[sep1-ap]: ../sep1/README.mdx
-[sep10-ap]: ../sep10/README.mdx
-[sep45-ap]: ../sep45/README.mdx
+[installation-ap]: ../../admin-guide/getting-started
+[sep1-ap]: /docs/platforms/anchor-platform/sep-guide/sep1
+[sep10-ap]: /docs/platforms/anchor-platform/sep-guide/sep10
+[sep45-ap]: /docs/platforms/anchor-platform/sep-guide/sep45
diff --git a/docs/platforms/anchor-platform/sep-guide/sep31/index.mdx b/docs/platforms/anchor-platform/sep-guide/sep31/index.mdx
new file mode 100644
index 000000000..3e7a170ed
--- /dev/null
+++ b/docs/platforms/anchor-platform/sep-guide/sep31/index.mdx
@@ -0,0 +1,22 @@
+---
+title: Cross-Border Payments (SEP-31)
+description: "SEP-31 allows for a means by which wallets and/or exchanges interact with Stellar's existing set of send-side services."
+---
+
+<CardGroup cols={2}>
+  <Card title="Getting Started" icon="file-lines" href="/docs/platforms/anchor-platform/sep-guide/sep31/getting-started">
+
+    This guide will walk you through configuring and integrating with the Anchor Platform for the purpose of building a cross-border payments recieve-side...
+
+  </Card>
+  <Card title="Configuration" icon="file-lines" href="/docs/platforms/anchor-platform/sep-guide/sep31/configuration">
+
+    Let's start by modifying our stellar.toml file created earlier.
+
+  </Card>
+  <Card title="Integration" icon="file-lines" href="/docs/platforms/anchor-platform/sep-guide/sep31/integration">
+
+    Integrating with the Anchor Platform for facilitating cross-border payments involves implementing the following, at a minimum.
+
+  </Card>
+</CardGroup>
diff --git a/docs/platforms/anchor-platform/sep-guide/sep31/integration.mdx b/docs/platforms/anchor-platform/sep-guide/sep31/integration.mdx
index cbb5fe171..4e1a4c6d2 100644
--- a/docs/platforms/anchor-platform/sep-guide/sep31/integration.mdx
+++ b/docs/platforms/anchor-platform/sep-guide/sep31/integration.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Integration"
-sidebar_position: 30
+description: "Integrating with the Anchor Platform for facilitating cross-border payments involves implementing the following, at a minimum."
 ---
 
 Integrating with the Anchor Platform for facilitating cross-border payments involves implementing the following, at a minimum:
@@ -18,9 +18,9 @@ The following may also be required depending on your use case:
 
 First, lets create a business server and add it to our docker compose file.
 
-<CodeExample>
+<CodeGroup>
 
-```yaml
+```yaml YAML
 version: "3.8"
 
 services:
@@ -61,7 +61,7 @@ services:
       - ./dev.env
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Next, create a simple web server using your preferred programming language and a `Dockerfile` that starts the server. `docker compose up` should successfully start all three services.
 
@@ -79,9 +79,9 @@ The first approach uses a Stellar account and memo. When using the Anchor Platfo
 
 The second approach uses customer IDs generated by your service. For example, if a sending organization is registering a customer, your business will receive a `PUT /customer` request like the following:
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 {
   "account": "GDJUOFZGW5WYBK4GIETCSSM6MTTIJ4SUMCQITPTLUWMQ6B4UIX2IEX47",
   "memo": "780284017",
@@ -92,41 +92,41 @@ The second approach uses customer IDs generated by your service. For example, if
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
 In this example, the `GDJ...X47` public key identifies the sending organization, and the `780284017` memo identifies the customer. Memos are usually 64-bit integers, but they can also be other data types, so they should be saved as strings. In response, your business should return a customer ID.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 {
   "id": "fb5ddc93-1d5d-490d-ba5f-2c361cea41f7"
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Your business server can use any identifier for customers as long as it is a string.
 
 Following the registration of a customer, the sending organization can use either approach when checking the customer's status. For example, you may get a `GET /customer` request like the following:
 
-<CodeExample>
+<CodeGroup>
 
-```
+```text Example
 /customer?account=GDJUOFZGW5WYBK4GIETCSSM6MTTIJ4SUMCQITPTLUWMQ6B4UIX2IEX47&memo=780284017&type=sep31-sender
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Or, the sending organization could use the identifier you returned when they originally registered the customer.
 
-<CodeExample>
+<CodeGroup>
 
-```
+```text Example
 /customer?id=fb5ddc93-1d5d-490d-ba5f-2c361cea41f7&type=sep31-sender
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Your business will need to maintain a mapping between the account & memo used to originally register the customer and the ID you return in the response, as well as the KYC data provided. In future iterations of the Anchor Platform, we may maintain this mapping for your business so you only have to work with the IDs you generate.
 
@@ -183,9 +183,9 @@ The easiest way to do that is to run the Stellar Observer, which will detect the
 
 The Stellar Observer monitors the Stellar ledger for payments made to your account(s) and updates the corresponding transaction records with on-chain payment information. To run the observer, add the following to your docker compose file.
 
-<CodeExample>
+<CodeGroup>
 
-```yaml
+```yaml YAML
 services:
   ...
   observer:
@@ -197,7 +197,7 @@ services:
       - ./config:/home
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Polling for Received Payments
 
@@ -205,13 +205,13 @@ The Stellar Observer makes JSON-RPC requests to the Platform API whenever it det
 
 Your business should periodically poll the `GET /transactions` Platform API endpoint to detect these updates. You can refer to the following example:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 curl http://localhost:8080/transactions?sep=31&order_by=transfer_received_at&order=desc
 ```
 
-</CodeExample>
+</CodeGroup>
 
 The response will include a list of cross-border payment transactions initiated by sending organizations. This list will be ordered according to the time a payment was received for that transaction. For each transaction returned, your business should check whether or not it has already detected the payment for that transaction. If it has, you have detected all payments made to your account(s).
 
@@ -221,7 +221,7 @@ SEP-31 flow diagram defines sequence/rules of the transaction's status transitio
 
 [![sep31 flow](/assets/ap/sep31-transition-diagram.png)](/assets/ap/sep31-transition-diagram.png)
 
-:::tip
+<Tip>
 
 Statuses in <span style={{color: "green"}}>green</span> are mandatory and define the shortest flow.
 
@@ -229,7 +229,7 @@ Statuses in <span style={{color: "#B0BF1A"}}>yellow</span> are optional and can
 
 Statuses in <span style={{color: "red"}}>red</span> mean the transaction is in an error status or it has expired.
 
-:::
+</Tip>
 
 You can create a [template][sep24-integration-make-json-rpc-request] for making a JSON-RPC requests to the Anchor Platform.
 
@@ -239,9 +239,9 @@ This chapter also contains information about the format of [request][sep24-integ
 
 SEP-31 Transactions should initially be in the `pending_receiver` status. To request funds from the Sending Anchor, the Receiving Anchor should change the transaction status to `pending_sender` by making the following RPC request:
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // request-onchain-funds.json
 [
   {
@@ -259,17 +259,17 @@ SEP-31 Transactions should initially be in the `pending_receiver` status. To req
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh request-onchain-funds.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
 The transaction status will be changed to `pending_sender`.
 
@@ -277,9 +277,9 @@ The transaction status will be changed to `pending_sender`.
 
 If the Sending Anchor has sent the funds, the Receiving Anchor should change the transaction status to `pending_receiver` by making the following JSON-RPC request:
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // onchain-funds-received.json
 [
   {
@@ -304,17 +304,17 @@ If the Sending Anchor has sent the funds, the Receiving Anchor should change the
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh onchain-funds-received.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
 The transaction status will be changed to `pending_receiver`.
 
@@ -322,9 +322,9 @@ The transaction status will be changed to `pending_receiver`.
 
 To complete the transaction and change its status to `completed`, you need to make a `notify_offchain_funds_sent` JSON-RPC request.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // offchain-funds-sent.json
 [
   {
@@ -341,25 +341,25 @@ To complete the transaction and change its status to `completed`, you need to ma
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh offchain-funds-sent.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Offchain Funds Pending
 
 Another option is to move the transaction's status to `pending_external`. This status means that payment has been submitted to external network, but it is not yet confirmed.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // offchain-funds-pending.json
 [
   {
@@ -375,17 +375,17 @@ Another option is to move the transaction's status to `pending_external`. This s
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh offchain-funds-pending.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Verifying Customer Information
 
@@ -393,9 +393,9 @@ In some cases, the Receiving Anchor might need to request an updated information
 
 After the Sending Anchor makes a SEP-12 `PUT /customer` request, call the `notify_customer_info_updated` JSON-RPC method againto update the transaction status. Additionally, call this method whenever the SEP-12 status for a customer changes, such as when the customer's information is being validated and the status changes from `NEEDS_INFO` to `PROCESSING`. This ensures that any clients configured with a callback URL are notified of the latest customer status, allowing the client to prompt the user to update their information.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // notify-customer-info-updated.json
 [
   {
@@ -412,25 +412,25 @@ After the Sending Anchor makes a SEP-12 `PUT /customer` request, call the `notif
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh notify-customer-info-updated.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Refund Sent
 
 There is a possibility to send all funds back to the `Sending Anchor` (refund). You need to refund the whole sum(full refund).
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // refund-sent.json
 [
   {
@@ -456,31 +456,31 @@ There is a possibility to send all funds back to the `Sending Anchor` (refund).
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh refund-sent.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::note
+<Note>
 
 You can't do multiple refunds in SEP-31 flow. For this reason, the amount to refund plus the amount fee should equal `amount_in`. Otherwise, you will get an error.
 
-:::
+</Note>
 
 ### Transaction Error
 
 If you encounter an unrecoverable error when processing the transaction, it's required to set the transaction status to `error`. You can use the message field to describe the details of the error.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // transaction-error.json
 [
   {
@@ -495,31 +495,31 @@ If you encounter an unrecoverable error when processing the transaction, it's re
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh transaction-error.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::tip
+<Tip>
 
 If a user has made a transfer, you should do a transaction recovery, and then you can retry processing the transaction or initiate a refund.
 
-:::
+</Tip>
 
 ### Expired Transaction
 
 Your business may want to expire those transactions that have been abandoned by the user after some time. It's a good practice to clean up inactive transactions in the `incomplete` status. To do so, simply change the transaction's status to `expired`.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // transaction-expired.json
 [
   {
@@ -534,31 +534,31 @@ Your business may want to expire those transactions that have been abandoned by
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh transaction-expired.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::tip
+<Tip>
 
 This JSON-RPC method can't be used after the user has made a transfer.
 
-:::
+</Tip>
 
 ### Transaction Recovery
 
 The transaction status can be changed from `error/expired` to `pending-anchor`. After recovery, you can refund the received assets or proceed with the processing of the transaction. To recover the transaction, it's necessary to make the following JSON-RPC request:
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // transaction-recovery.json
 [
   {
@@ -573,46 +573,46 @@ The transaction status can be changed from `error/expired` to `pending-anchor`.
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh transaction-recovery.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Configuration
 
 You can enable these types of transactions by updating your `assets.yaml` file configuration:
 
-<CodeExample>
+<CodeGroup>
 
-```yaml
+```yaml YAML
 items:
   - ...
     sep31:
       quotes_required: false
 ```
 
-</CodeExample>
+</CodeGroup>
 
-[ap-api]: ../../README.mdx
-[ap-sep10]: ../sep10/README.mdx
+[ap-api]: /docs/platforms/anchor-platform
+[ap-sep10]: /docs/platforms/anchor-platform/sep-guide/sep10
 [sep12]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md
 [demo-wallet]: https://demo-wallet.stellar.org
 [indicative]: https://www.investopedia.com/terms/i/indicativequote.asp
 [firm]: https://www.investopedia.com/terms/f/firmquote.asp
-[get-customer]: ../../api-reference/callbacks/get-customer.api.mdx
-[put-customer]: ../../api-reference/callbacks/put-customer.api.mdx
-[get-rate]: ../../api-reference/callbacks/get-rates.api.mdx
-[put-customer-callback]: ../../api-reference/callbacks/put-customer.api.mdx
-[delete-customer]: ../../api-reference/callbacks/del-customer.api.mdx
-[json-rpc-methods]: ../../api-reference/platform/rpc/methods/README.mdx
-[sep24-integration-make-json-rpc-request]: ../sep24/integration.mdx#making-json-rpc-requests
-[sep24-integration-rpc-request]: ../sep24/integration.mdx#json-rpc-request
-[sep24-integration-rpc-response]: ../sep24/integration.mdx#json-rpc-response
-[sep24-integration-error-codes]: ../sep24/integration.mdx#error-codes
+[get-customer]: /docs/platforms/anchor-platform/api-reference/callbacks/get-customer
+[put-customer]: /docs/platforms/anchor-platform/api-reference/callbacks/put-customer
+[get-rate]: /docs/platforms/anchor-platform/api-reference/callbacks/get-rates
+[put-customer-callback]: /docs/platforms/anchor-platform/api-reference/callbacks/put-customer
+[delete-customer]: /docs/platforms/anchor-platform/api-reference/callbacks/del-customer
+[json-rpc-methods]: /docs/platforms/anchor-platform/api-reference/platform/rpc/methods
+[sep24-integration-make-json-rpc-request]: ../sep24/integration#making-json-rpc-requests
+[sep24-integration-rpc-request]: ../sep24/integration#json-rpc-request
+[sep24-integration-rpc-response]: ../sep24/integration#json-rpc-response
+[sep24-integration-error-codes]: ../sep24/integration#error-codes
diff --git a/docs/platforms/anchor-platform/sep-guide/sep45/README.mdx b/docs/platforms/anchor-platform/sep-guide/sep45/README.mdx
deleted file mode 100644
index 77a875d9a..000000000
--- a/docs/platforms/anchor-platform/sep-guide/sep45/README.mdx
+++ /dev/null
@@ -1,142 +0,0 @@
----
-title: Stellar Authentication for Contract Accounts (SEP-45)
-sidebar_position: 70
----
-
-## Overview
-
-SEP-45 (Stellar Web Authentication for Contract Accounts) enables smart wallet applications to create authenticated sessions with Stellar anchors by proving control over a contract account (`C...`). Once authenticated, wallets receive a JSON Web Token (JWT) that they use in subsequent requests to the anchor's standardized services.
-
-For the complete specification, see [SEP-45: Stellar Web Authentication for Contract Accounts][sep-45].
-
-The Anchor Platform implements SEP-45 with support for:
-
-- **Challenge/Response Flow**: GET `/sep45/auth` to request authorization entries, POST `/sep45/auth` to validate and receive a JWT
-- **Contract Account Authentication**: Support for contract accounts (`C...`) using Soroban authorization entries
-- **Transaction Simulation**: Automatic simulation of transactions to verify authorization entries
-- **Multiple Home Domains**: Support for multiple domains and wildcard patterns
-
-:::info
-
-**SEP-45 vs SEP-10**: SEP-45 does not replace SEP-10. SEP-45 supports contract accounts (`C...`), while SEP-10 supports classic accounts (`G...`) and muxed accounts (`M...`). Services wishing to support all account types should implement both SEPs.
-
-:::
-
-## Typical Authentication Flow
-
-1. The **Client** requests a unique challenge from the **Server**
-2. The **Client** verifies and signs the challenge
-3. The **Client** submits the signed challenge to the **Server**
-4. The **Server** verifies the challenge and responds with a JWT session token
-
-An implementation of the SEP-45 contract is provided in the [Anchor Platform repository][sep-45-contract]. An instance of this contract is deployed at `CD3LA6RKF5D2FN2R2L57MWXLBRSEWWENE74YBEFZSSGNJRJGICFGQXMX` on testnet.
-
-## Enable SEP-45
-
-SEP-45 requires integration with Stellar RPC to simulate transactions. The Anchor Platform can connect to the Stellar RPC server of your choice. You can use a public Stellar RPC provider, or you can run your own. A list of public providers can be found [here][rpc-providers].
-
-To enable SEP-45, set the following environment variables in your `dev.env` file.
-
-<CodeExample>
-
-```bash
-# dev.env
-STELLAR_NETWORK_TYPE=rpc
-STELLAR_NETWORK_RPC_URL=https://soroban-testnet.stellar.org
-SEP45_ENABLED=true
-SEP45_HOME_DOMAINS=localhost:8080
-SEP45_WEB_AUTH_CONTRACT_ID="CD3LA6RKF5D2FN2R2L57MWXLBRSEWWENE74YBEFZSSGNJRJGICFGQXMX"
-SECRET_SEP10_SIGNING_SEED="a Stellar private key"
-SECRET_SEP45_JWT_SECRET="a secret encryption key"
-```
-
-</CodeExample>
-
-### Required Configuration (If Enabled)
-
-| Variable | Default | Description |
-| --- | --- | --- |
-| `STELLAR_NETWORK_TYPE` | _Required_ | Must be set to `rpc` for SEP-45. This enables RPC mode for the Anchor Platform. |
-| `STELLAR_NETWORK_RPC_URL` | _Required_ | The URL of the Stellar RPC server used to simulate transactions. You can use a public provider or run your own. A list of public providers can be found [here][rpc-providers]. |
-| `SEP45_ENABLED` | `false` | Set to `true` to enable SEP-45 authentication |
-| `SEP45_HOME_DOMAINS` | _Required_ | List of home domains (comma-separated). Supports wildcard patterns like `*.stellar.org`. The `home_domain` must match the host where your `stellar.toml` file is served. |
-| `SEP45_WEB_AUTH_CONTRACT_ID` | _Required_ | The contract ID of the SEP-45 contract. This contract must implement the `web_auth_verify` function as described in the [SEP-45 specification][sep-45]. |
-| `SECRET_SEP10_SIGNING_SEED` | _Required_ | The private key corresponding to the `SIGNING_KEY` in your `stellar.toml` file. SEP-45 uses the same signing key as SEP-10. Used to sign authentication challenges. |
-| `SECRET_SEP45_JWT_SECRET` | _Required_ | The encryption key used to sign and verify JWT tokens issued to authenticated wallets. |
-
-:::important
-
-- **RPC Requirement**: SEP-45 requires Stellar RPC to simulate transactions. You must set `STELLAR_NETWORK_TYPE=rpc` and provide a valid `STELLAR_NETWORK_RPC_URL`.
-- **Contract ID**: The `SEP45_WEB_AUTH_CONTRACT_ID` must match the contract deployed at the address specified in your `stellar.toml` file's `WEB_AUTH_CONTRACT_ID` field.
-- **Signing Key**: The `SIGNING_KEY` in your `stellar.toml` file must be the public key derived from `SECRET_SEP10_SIGNING_SEED`.
-
-:::
-
-### Optional Configuration
-
-<CodeExample>
-
-```bash
-# dev.env
-# Optional: Specify web_auth_domain (default: first home_domain if only one is specified)
-SEP45_WEB_AUTH_DOMAIN=localhost:8080
-
-# Optional: Challenge timeout in seconds (default: 900)
-SEP45_AUTH_TIMEOUT=900
-
-# Optional: JWT token timeout in seconds (default: 86400 = 24 hours)
-SEP45_JWT_TIMEOUT=86400
-```
-
-</CodeExample>
-
-| Variable | Default | Description |
-| --- | --- | --- |
-| `SEP45_WEB_AUTH_DOMAIN` | First `home_domain` if only one is specified, otherwise empty | The `web_auth_domain` property used in SEP-45 responses. Required if you have multiple `home_domains` or use wildcard patterns. Must match the host of the SEP server. |
-| `SEP45_AUTH_TIMEOUT` | `900` | Time in seconds that a challenge remains valid. Clients must sign and submit the authorization entries within this window. |
-| `SEP45_JWT_TIMEOUT` | `86400` | Time in seconds that an issued JWT token remains valid. After expiration, clients must re-authenticate. |
-
-:::tip
-
-**Multiple Home Domains**: If you specify multiple `home_domains` (e.g., `ap.stellar.org,*.sdp.stellar.org`), you must also set `SEP45_WEB_AUTH_DOMAIN` to specify which domain hosts the authentication endpoint.
-
-:::
-
-## Configure stellar.toml
-
-Update your `stellar.toml` file to advertise SEP-45 support. Wallets discover your authentication endpoint through this file.
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-
-ACCOUNTS = ["add your public keys for your distribution accounts here"]
-SIGNING_KEY = "add your signing key here (public key from SECRET_SEP10_SIGNING_SEED)"
-WEB_AUTH_FOR_CONTRACTS_ENDPOINT = "http://localhost:8080/sep45/auth"
-WEB_AUTH_CONTRACT_ID = "CD3LA6RKF5D2FN2R2L57MWXLBRSEWWENE74YBEFZSSGNJRJGICFGQXMX"
-```
-
-</CodeExample>
-
-These fields should match the configuration options set in the [Enable SEP-45](#enable-sep-45) section above.
-
-`WEB_AUTH_FOR_CONTRACTS_ENDPOINT` - The URL where the authentication service is running. This is the URL that clients will use to authenticate with the anchor. The endpoint must support:
-
-- `GET <WEB_AUTH_FOR_CONTRACTS_ENDPOINT>` - Request authorization entries
-- `POST <WEB_AUTH_FOR_CONTRACTS_ENDPOINT>` - Exchange signed authorization entries for session JWT
-
-`WEB_AUTH_CONTRACT_ID` - The contract ID of the SEP-45 contract. This is the contract that will be used to construct the challenge. The contract must implement the `web_auth_verify` function as described in the [SEP-45 specification][sep-45]. This should match `SEP45_WEB_AUTH_CONTRACT_ID`.
-
-:::important
-
-- **`SIGNING_KEY`**: Must be the public key derived from `SECRET_SEP10_SIGNING_SEED`
-- **`WEB_AUTH_FOR_CONTRACTS_ENDPOINT`**: Use `https://` in production. The path `/sep45/auth` is the standard SEP-45 endpoint.
-- **Host Matching**: The host in `WEB_AUTH_FOR_CONTRACTS_ENDPOINT` should match one of your `SEP45_HOME_DOMAINS` (or the `SEP45_WEB_AUTH_DOMAIN` if specified).
-
-:::
-
-[sep1-ap]: ../sep1/README.mdx
-[sep-45]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0045.md
-[sep-45-contract]: https://github.com/stellar/anchor-platform/tree/main/soroban/contracts/web-auth
-[rpc-providers]: ../../../../data/apis/rpc/providers.mdx
diff --git a/docs/platforms/anchor-platform/sep-guide/sep45/index.mdx b/docs/platforms/anchor-platform/sep-guide/sep45/index.mdx
new file mode 100644
index 000000000..ce3ef1ac5
--- /dev/null
+++ b/docs/platforms/anchor-platform/sep-guide/sep45/index.mdx
@@ -0,0 +1,142 @@
+---
+title: Stellar Authentication for Contract Accounts (SEP-45)
+description: "SEP-45 (Stellar Web Authentication for Contract Accounts) enables smart wallet applications to create authenticated sessions with Stellar anchors by proving..."
+---
+
+## Overview
+
+SEP-45 (Stellar Web Authentication for Contract Accounts) enables smart wallet applications to create authenticated sessions with Stellar anchors by proving control over a contract account (`C...`). Once authenticated, wallets receive a JSON Web Token (JWT) that they use in subsequent requests to the anchor's standardized services.
+
+For the complete specification, see [SEP-45: Stellar Web Authentication for Contract Accounts][sep-45].
+
+The Anchor Platform implements SEP-45 with support for:
+
+- **Challenge/Response Flow**: GET `/sep45/auth` to request authorization entries, POST `/sep45/auth` to validate and receive a JWT
+- **Contract Account Authentication**: Support for contract accounts (`C...`) using Soroban authorization entries
+- **Transaction Simulation**: Automatic simulation of transactions to verify authorization entries
+- **Multiple Home Domains**: Support for multiple domains and wildcard patterns
+
+<Info>
+
+**SEP-45 vs SEP-10**: SEP-45 does not replace SEP-10. SEP-45 supports contract accounts (`C...`), while SEP-10 supports classic accounts (`G...`) and muxed accounts (`M...`). Services wishing to support all account types should implement both SEPs.
+
+</Info>
+
+## Typical Authentication Flow
+
+1. The **Client** requests a unique challenge from the **Server**
+2. The **Client** verifies and signs the challenge
+3. The **Client** submits the signed challenge to the **Server**
+4. The **Server** verifies the challenge and responds with a JWT session token
+
+An implementation of the SEP-45 contract is provided in the [Anchor Platform repository][sep-45-contract]. An instance of this contract is deployed at `CD3LA6RKF5D2FN2R2L57MWXLBRSEWWENE74YBEFZSSGNJRJGICFGQXMX` on testnet.
+
+## Enable SEP-45
+
+SEP-45 requires integration with Stellar RPC to simulate transactions. The Anchor Platform can connect to the Stellar RPC server of your choice. You can use a public Stellar RPC provider, or you can run your own. A list of public providers can be found [here][rpc-providers].
+
+To enable SEP-45, set the following environment variables in your `dev.env` file.
+
+<CodeGroup>
+
+```bash bash
+# dev.env
+STELLAR_NETWORK_TYPE=rpc
+STELLAR_NETWORK_RPC_URL=https://soroban-testnet.stellar.org
+SEP45_ENABLED=true
+SEP45_HOME_DOMAINS=localhost:8080
+SEP45_WEB_AUTH_CONTRACT_ID="CD3LA6RKF5D2FN2R2L57MWXLBRSEWWENE74YBEFZSSGNJRJGICFGQXMX"
+SECRET_SEP10_SIGNING_SEED="a Stellar private key"
+SECRET_SEP45_JWT_SECRET="a secret encryption key"
+```
+
+</CodeGroup>
+
+### Required Configuration (If Enabled)
+
+| Variable | Default | Description |
+| --- | --- | --- |
+| `STELLAR_NETWORK_TYPE` | _Required_ | Must be set to `rpc` for SEP-45. This enables RPC mode for the Anchor Platform. |
+| `STELLAR_NETWORK_RPC_URL` | _Required_ | The URL of the Stellar RPC server used to simulate transactions. You can use a public provider or run your own. A list of public providers can be found [here][rpc-providers]. |
+| `SEP45_ENABLED` | `false` | Set to `true` to enable SEP-45 authentication |
+| `SEP45_HOME_DOMAINS` | _Required_ | List of home domains (comma-separated). Supports wildcard patterns like `*.stellar.org`. The `home_domain` must match the host where your `stellar.toml` file is served. |
+| `SEP45_WEB_AUTH_CONTRACT_ID` | _Required_ | The contract ID of the SEP-45 contract. This contract must implement the `web_auth_verify` function as described in the [SEP-45 specification][sep-45]. |
+| `SECRET_SEP10_SIGNING_SEED` | _Required_ | The private key corresponding to the `SIGNING_KEY` in your `stellar.toml` file. SEP-45 uses the same signing key as SEP-10. Used to sign authentication challenges. |
+| `SECRET_SEP45_JWT_SECRET` | _Required_ | The encryption key used to sign and verify JWT tokens issued to authenticated wallets. |
+
+<Warning>
+
+- **RPC Requirement**: SEP-45 requires Stellar RPC to simulate transactions. You must set `STELLAR_NETWORK_TYPE=rpc` and provide a valid `STELLAR_NETWORK_RPC_URL`.
+- **Contract ID**: The `SEP45_WEB_AUTH_CONTRACT_ID` must match the contract deployed at the address specified in your `stellar.toml` file's `WEB_AUTH_CONTRACT_ID` field.
+- **Signing Key**: The `SIGNING_KEY` in your `stellar.toml` file must be the public key derived from `SECRET_SEP10_SIGNING_SEED`.
+
+</Warning>
+
+### Optional Configuration
+
+<CodeGroup>
+
+```bash bash
+# dev.env
+# Optional: Specify web_auth_domain (default: first home_domain if only one is specified)
+SEP45_WEB_AUTH_DOMAIN=localhost:8080
+
+# Optional: Challenge timeout in seconds (default: 900)
+SEP45_AUTH_TIMEOUT=900
+
+# Optional: JWT token timeout in seconds (default: 86400 = 24 hours)
+SEP45_JWT_TIMEOUT=86400
+```
+
+</CodeGroup>
+
+| Variable | Default | Description |
+| --- | --- | --- |
+| `SEP45_WEB_AUTH_DOMAIN` | First `home_domain` if only one is specified, otherwise empty | The `web_auth_domain` property used in SEP-45 responses. Required if you have multiple `home_domains` or use wildcard patterns. Must match the host of the SEP server. |
+| `SEP45_AUTH_TIMEOUT` | `900` | Time in seconds that a challenge remains valid. Clients must sign and submit the authorization entries within this window. |
+| `SEP45_JWT_TIMEOUT` | `86400` | Time in seconds that an issued JWT token remains valid. After expiration, clients must re-authenticate. |
+
+<Tip>
+
+**Multiple Home Domains**: If you specify multiple `home_domains` (e.g., `ap.stellar.org,*.sdp.stellar.org`), you must also set `SEP45_WEB_AUTH_DOMAIN` to specify which domain hosts the authentication endpoint.
+
+</Tip>
+
+## Configure stellar.toml {#configure-stellartoml}
+
+Update your `stellar.toml` file to advertise SEP-45 support. Wallets discover your authentication endpoint through this file.
+
+<CodeGroup>
+
+```toml TOML
+# dev.stellar.toml
+
+ACCOUNTS = ["add your public keys for your distribution accounts here"]
+SIGNING_KEY = "add your signing key here (public key from SECRET_SEP10_SIGNING_SEED)"
+WEB_AUTH_FOR_CONTRACTS_ENDPOINT = "http://localhost:8080/sep45/auth"
+WEB_AUTH_CONTRACT_ID = "CD3LA6RKF5D2FN2R2L57MWXLBRSEWWENE74YBEFZSSGNJRJGICFGQXMX"
+```
+
+</CodeGroup>
+
+These fields should match the configuration options set in the [Enable SEP-45](#enable-sep-45) section above.
+
+`WEB_AUTH_FOR_CONTRACTS_ENDPOINT` - The URL where the authentication service is running. This is the URL that clients will use to authenticate with the anchor. The endpoint must support:
+
+- `GET <WEB_AUTH_FOR_CONTRACTS_ENDPOINT>` - Request authorization entries
+- `POST <WEB_AUTH_FOR_CONTRACTS_ENDPOINT>` - Exchange signed authorization entries for session JWT
+
+`WEB_AUTH_CONTRACT_ID` - The contract ID of the SEP-45 contract. This is the contract that will be used to construct the challenge. The contract must implement the `web_auth_verify` function as described in the [SEP-45 specification][sep-45]. This should match `SEP45_WEB_AUTH_CONTRACT_ID`.
+
+<Warning>
+
+- **`SIGNING_KEY`**: Must be the public key derived from `SECRET_SEP10_SIGNING_SEED`
+- **`WEB_AUTH_FOR_CONTRACTS_ENDPOINT`**: Use `https://` in production. The path `/sep45/auth` is the standard SEP-45 endpoint.
+- **Host Matching**: The host in `WEB_AUTH_FOR_CONTRACTS_ENDPOINT` should match one of your `SEP45_HOME_DOMAINS` (or the `SEP45_WEB_AUTH_DOMAIN` if specified).
+
+</Warning>
+
+[sep1-ap]: /docs/platforms/anchor-platform/sep-guide/sep1
+[sep-45]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0045.md
+[sep-45-contract]: https://github.com/stellar/anchor-platform/tree/main/soroban/contracts/web-auth
+[rpc-providers]: /docs/data/apis/rpc/providers
diff --git a/docs/platforms/anchor-platform/sep-guide/sep6/README.mdx b/docs/platforms/anchor-platform/sep-guide/sep6/README.mdx
deleted file mode 100644
index dbe79e701..000000000
--- a/docs/platforms/anchor-platform/sep-guide/sep6/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Programmatic Deposits and Withdrawals (SEP-6)
-sidebar_position: 80
----
-
-import DocCardList from "@theme/DocCardList";
-
-SEP-6 allows for a means by which wallets and/or exchanges interact with an anchor on behalf of users, never requiring the user to directly interact with the on & off-ramp.
-
-<DocCardList />
diff --git a/docs/platforms/anchor-platform/sep-guide/sep6/configuration.mdx b/docs/platforms/anchor-platform/sep-guide/sep6/configuration.mdx
index 57252eb13..15b85f976 100644
--- a/docs/platforms/anchor-platform/sep-guide/sep6/configuration.mdx
+++ b/docs/platforms/anchor-platform/sep-guide/sep6/configuration.mdx
@@ -1,38 +1,36 @@
 ---
 title: "Configuration"
-sidebar_position: 20
+description: "To enable SEP-6 deposits and withdraws, the Anchor Platform must be configured to do the following."
 ---
 
-# Configuration
-
 To enable SEP-6 deposits and withdraws, the Anchor Platform must be configured to do the following:
 
 - Provide the necessary service URLs for SEP-6, 12, & 38 endpoints in the `stellar.toml` file
 - Provide information about the on & off-chain assets, as well as the payment rails, supported by your business via SEP-6 and SEP-38 `/info` endpoints
 - Support the endpoints and callbacks required to request KYC information and provide exchange rates
 
-## Enable Programmatic Deposits & Withdrawals
+## Enable Programmatic Deposits & Withdrawals {#enable-programmatic-deposits--withdrawals}
 
 Add the following variables to your environment file.
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 # dev.env
 SEP6_ENABLED=true
 SEP12_ENABLED=true
 SEP38_ENABLED=true
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Modify a Stellar Info File
 
 Let's modify the `stellar.toml` file created [earlier][sep1-ap]. Wallets need to know that SEP-6 functionality is supported by your business, and they also need to know all the Stellar assets you support.
 
-<CodeExample>
+<CodeGroup>
 
-```toml
+```toml TOML
 # dev.stellar.toml
 ACCOUNTS = ["add your public keys for your distribution accounts here"]
 SIGNING_KEY = "add your signing key here"
@@ -57,7 +55,7 @@ ORG_URL = "Your website"
 ORG_DESCRIPTION = "A description of your organization"
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Note that you will need to create another file for your production deployment that uses the public network's passphrase, your production service URLs, your Mainnet distribution accounts and signing key, as well as the Mainnet issuing accounts of the assets your service utilizes.
 
@@ -71,9 +69,9 @@ The methods specified in the `deposit` and `withdraw` sections are the methods t
 
 Also note that fiat assets, those with the `schema: iso4217`, do not need the `sep6_enabled`, `deposit`, or `withdraw` configuration objects specified. In the same way, Stellar assets, those with `schema: stellar`, do not need the `sep38.sell_delivery_methods` or `sep38.buy_delivery_methods` configuration objects specified.
 
-<CodeExample>
+<CodeGroup>
 
-```yaml
+```yaml YAML
 items:
   - id: stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5
     distribution_account: GBLSAHONJRODSFTLOV225NZR4LHICH63RIFQTQN37L5CRTR2IMQ5UEK7
@@ -110,7 +108,7 @@ items:
           description: ACH credit for US bank accounts
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Managing Distribution Accounts
 
@@ -120,14 +118,14 @@ If you do not have your own Stellar account and instead use a third party that p
 
 To configure the Anchor Platform to expect the Stellar account and memo to be provided via API instead of configured via the assets file, specify the following environment variable.
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 # dev.env
 SEP6_DEPOSIT_INFO_GENERATOR_TYPE=none
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Enable Callbacks to the Business Server
 
@@ -137,9 +135,9 @@ Additionally, businesses need to provide clients with a [Rates][get-rates-api] A
 
 To enable these requests to your business server, first you'll need to add your business server to the docker compose file. Then, to support requests to your business server from the Anchor Platform, you need to enable callbacks.
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 # dev.env
 CALLBACK_API_BASE_URL=http://business-server:3000/callbacks
 CALLBACK_API_AUTH_TYPE=jwt
@@ -148,7 +146,7 @@ CALLBACK_API_AUTH_JWT_HTTP_HEADER=Authorization
 SECRET_CALLBACK_API_AUTH_SECRET="a secret used to sign JWTs"
 ```
 
-</CodeExample>
+</CodeGroup>
 
 The above tells the Anchor Platform to include a [JWT][how-to-use-jwt], signed with the configured secret, in the `Authorization` header of requests made to `/callbacks/<callback endpoint>` so your server can authenticate the Anchor Platform before processing requests.
 
@@ -158,34 +156,34 @@ See the [KYC API][platform-api-kyc] and [Rates API][get-rates-api] for details o
 
 `more_info_url` is an optional URL provided by your business server for wallet applications to display information about previously initiated transactions. This URL is typically used by wallets in their transaction history views, and your business can specify the information to be displayed about the transaction.
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 # dev.env
 SEP6_MORE_INFO_URL_BASE_URL=http://example.com
 SECRET_SEP6_MORE_INFO_URL_JWT_SECRET="your encryption key shared with your business server"
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Businesses can set a deadline for user actions on transactions using the `user_action_required_by` field. For examples, see [JSON-RPC Methods][json-rpc-methods]. In addition, the `initial_user_deadline_seconds` parameter sets a default time (in seconds) a user has to act before the transaction moves into the `EXPIRED` status.
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 # dev.env
 SEP6_INITIAL_USER_DEADLINE_SECONDS=1209600
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## Test With the Demo Wallet
 
 Wallets should now be able to discover, authenticate, and initiate transactions with your service! Your project and source files should now look something like this.
 
-<CodeExample>
+<CodeGroup>
 
-```
+```text Example
 ├── dev.env
 ├── docker-compose.yaml
 ├── config
@@ -193,13 +191,13 @@ Wallets should now be able to discover, authenticate, and initiate transactions
 │   ├── dev.stellar.toml
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Your environment should now look something like the following.
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 # dev.env
 ASSETS_TYPE=file
 ASSETS_VALUE=/home/dev.assets.yaml
@@ -229,7 +227,7 @@ CALLBACK_API_AUTH_JWT_HTTP_HEADER=Authorization
 SECRET_CALLBACK_API_AUTH_SECRET="a secret used to sign JWTs"
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To test this out, go to the [Stellar Demo Wallet][stellar-demo-wallet].
 
@@ -244,11 +242,11 @@ Initiate a deposit transaction by doing the following:
 The demo wallet should be able to find your `stellar.toml` file, authenticate using the Stellar keypair you just created, and initiate a transaction.
 
 [sep-6]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md
-[sep1-ap]: ../sep1/README.mdx
+[sep1-ap]: /docs/platforms/anchor-platform/sep-guide/sep1
 [stellar-demo-wallet]: https://demo-wallet.stellar.org/
-[get-rates-api]: ../../api-reference/callbacks/get-rates.api.mdx
+[get-rates-api]: /docs/platforms/anchor-platform/api-reference/callbacks/get-rates
 [sep38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
-[platform-api-kyc]: ../../api-reference/callbacks/get-customer.api.mdx
-[request-onchain-funds]: ../../api-reference/platform/rpc/methods/request_onchain_funds.mdx
-[how-to-use-jwt]: ../sep24/faq.mdx
-[json-rpc-methods]: ../../api-reference/platform/rpc/methods/README.mdx
+[platform-api-kyc]: /docs/platforms/anchor-platform/api-reference/callbacks/get-customer
+[request-onchain-funds]: ../../api-reference/platform/rpc/methods/request_onchain_funds
+[how-to-use-jwt]: ../sep24/faq
+[json-rpc-methods]: /docs/platforms/anchor-platform/api-reference/platform/rpc/methods
diff --git a/docs/platforms/anchor-platform/sep-guide/sep6/getting-started.mdx b/docs/platforms/anchor-platform/sep-guide/sep6/getting-started.mdx
index f253b3623..9c8ed5f87 100644
--- a/docs/platforms/anchor-platform/sep-guide/sep6/getting-started.mdx
+++ b/docs/platforms/anchor-platform/sep-guide/sep6/getting-started.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Getting Started"
-sidebar_position: 10
+description: "This guide will walk you through configuring and integration with the Anchor Platform for the purpose of build an on & off-ramp service compatible with..."
 ---
 
 This guide will walk you through configuring and integration with the Anchor Platform for the purpose of build an on & off-ramp service compatible with [SEP-6][sep-6], the ecosystem's standardized protocol for programmatic deposit and withdrawals.
@@ -28,7 +28,7 @@ The customer can then use the digital asset on the Stellar network for remittanc
 5. Once the anchor receives the payment, the customer receives the withdrawn funds via any method supported by the anchor (such as bank transfer)
 
 [sep-6]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md
-[installation-ap]: ../../admin-guide/getting-started.mdx
-[sep1-ap]: ../sep1/README.mdx
-[sep10-ap]: ../sep10/README.mdx
-[sep45-ap]: ../sep45/README.mdx
+[installation-ap]: ../../admin-guide/getting-started
+[sep1-ap]: /docs/platforms/anchor-platform/sep-guide/sep1
+[sep10-ap]: /docs/platforms/anchor-platform/sep-guide/sep10
+[sep45-ap]: /docs/platforms/anchor-platform/sep-guide/sep45
diff --git a/docs/platforms/anchor-platform/sep-guide/sep6/index.mdx b/docs/platforms/anchor-platform/sep-guide/sep6/index.mdx
new file mode 100644
index 000000000..9be1edef6
--- /dev/null
+++ b/docs/platforms/anchor-platform/sep-guide/sep6/index.mdx
@@ -0,0 +1,22 @@
+---
+title: Programmatic Deposits and Withdrawals (SEP-6)
+description: "SEP-6 allows for a means by which wallets and/or exchanges interact with an anchor on behalf of users, never requiring the user to directly interact with the on & off-ramp."
+---
+
+<CardGroup cols={2}>
+  <Card title="Getting Started" icon="file-lines" href="/docs/platforms/anchor-platform/sep-guide/sep6/getting-started">
+
+    This guide will walk you through configuring and integration with the Anchor Platform for the purpose of build an on & off-ramp service compatible with...
+
+  </Card>
+  <Card title="Configuration" icon="file-lines" href="/docs/platforms/anchor-platform/sep-guide/sep6/configuration">
+
+    To enable SEP-6 deposits and withdraws, the Anchor Platform must be configured to do the following.
+
+  </Card>
+  <Card title="Integration" icon="file-lines" href="/docs/platforms/anchor-platform/sep-guide/sep6/integration">
+
+    One of the main points of interaction with the Anchor Platform is notifying the Platform about events related to transactions.
+
+  </Card>
+</CardGroup>
diff --git a/docs/platforms/anchor-platform/sep-guide/sep6/integration.mdx b/docs/platforms/anchor-platform/sep-guide/sep6/integration.mdx
index 8e621ee80..848e25370 100644
--- a/docs/platforms/anchor-platform/sep-guide/sep6/integration.mdx
+++ b/docs/platforms/anchor-platform/sep-guide/sep6/integration.mdx
@@ -1,16 +1,16 @@
 ---
 title: "Integration"
-sidebar_position: 30
+description: "One of the main points of interaction with the Anchor Platform is notifying the Platform about events related to transactions."
 ---
 
-import Security from "../../admin-guide/component/security/security.mdx";
-import UsingApiKey from "../../admin-guide/component/security/api_key.mdx";
-import UsingJwt from "../../admin-guide/component/security/jwt.mdx";
-import Rpc from "../../admin-guide/component/rpc/rpc.mdx";
-import RpcRequest from "../../admin-guide/component/rpc/request.mdx";
-import RpcResponse from "../../admin-guide/component/rpc/response.mdx";
-import RpcError from "../../admin-guide/component/rpc/error.mdx";
-import Observer from "../../admin-guide/component/observer/observer.mdx";
+import Security from "/snippets/anchor-platform/security.mdx";
+import UsingApiKey from "/snippets/anchor-platform/api_key.mdx";
+import UsingJwt from "/snippets/anchor-platform/jwt.mdx";
+import Rpc from "/snippets/anchor-platform/rpc.mdx";
+import RpcRequest from "/snippets/anchor-platform/request.mdx";
+import RpcResponse from "/snippets/anchor-platform/response.mdx";
+import RpcError from "/snippets/anchor-platform/error.mdx";
+import Observer from "/snippets/anchor-platform/observer.mdx";
 
 One of the main points of interaction with the Anchor Platform is notifying the Platform about events related to transactions.
 
@@ -80,7 +80,7 @@ The deposit exchange flow is the same as the deposit flow, except the amounts wi
 
 [![sep6 deposit flow](/assets/ap/sep6-deposit-flow-diagram.png)](/assets/ap/sep6-deposit-flow-diagram.png)
 
-:::tip
+<Tip>
 
 Statuses in <span style={{color: "green"}}>green</span> are mandatory and define the shortest way.
 
@@ -88,7 +88,7 @@ Statuses in <span style={{color: "#B0BF1A"}}>yellow</span> are optional and can
 
 Statuses in <span style={{color: "red"}}>red</span> mean the transaction is in an error status or it has expired.
 
-:::
+</Tip>
 
 ### Verifying KYC Information
 
@@ -96,9 +96,9 @@ Although Anchor Platform does not require a customer to have their KYC informati
 
 After the user has submitted their KYC information, call the `notify_customer_info_updated` JSON-RPC method againto update the transaction status. Additionally, call this method whenever the SEP-12 status for a customer changes, such as when the customer's information is being validated and the status changes from `NEEDS_INFO` to `PROCESSING`. This ensures that any clients configured with a callback URL are notified of the latest customer status, allowing the client to prompt the user to update their information.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // notify-customer-info-updated.json
 [
   {
@@ -115,25 +115,25 @@ After the user has submitted their KYC information, call the `notify_customer_in
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh notify-customer-info-updated.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Ready to Receive Funds
 
 After the user has submitted their KYC information, the anchor can notify the Platform that they are ready to receive funds. The anchor should use the `request_offchain_funds` RPC to provide the final amounts to the user. To do so, make the following JSON-RPC request.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // request-offchain-funds.json
 [
   {
@@ -173,7 +173,7 @@ After the user has submitted their KYC information, the anchor can notify the Pl
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 - `amount_in` is the amount the user has to send to the business.
 - `amount_out` is the amount the user will receive.
@@ -185,27 +185,27 @@ Information about amounts (in/out/fee) is required if you want to move the trans
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh request-offchain-funds.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::caution
+<Warning>
 
 For exchange deposits with a firm quote (the request is associated with a `quote_id`), no amounts should not be provided.
 
-:::
+</Warning>
 
 ### Funds Received
 
 If offchain funds were received, you'll want to provide updated transaction information.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // offchain-funds-received.json
 [
   {
@@ -234,7 +234,7 @@ If offchain funds were received, you'll want to provide updated transaction info
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 - `funds_received_at` is the date and time of receiving funds.
 - `external_transaction_id` is the ID of transaction on external network.
@@ -243,21 +243,21 @@ The amount fields are optional. If skipped, the values prior to this request wil
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh offchain-funds-received.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Waiting For User Funds
 
 In the real world, the transfer confirmation process may take time. In such cases, transactions should be set to a new status indicating that the confirmation of the transfer has been received but the funds themselves have not been received yet.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // offchain-funds-sent.json
 [
   {
@@ -274,25 +274,25 @@ In the real world, the transfer confirmation process may take time. In such case
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh offchain-funds-sent.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Sending Onchain Funds
 
 Next, send a transaction on the Stellar network to fulfill the user deposit. After the Stellar transaction has been submitted, it's necessary to send the `notify_onchain_funds_sent` JSON-RPC request to notify a user that the funds were successfully sent.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // onchain-funds-sent.json
 [
   {
@@ -308,19 +308,19 @@ Next, send a transaction on the Stellar network to fulfill the user deposit. Aft
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 - `stellar_transaction_id` is the transaction id on Stellar network of the transfer.
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh onchain-funds-sent.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
 After this JSON-RPC request, the transaction will be transferred to the `completed` status.
 
@@ -328,9 +328,9 @@ After this JSON-RPC request, the transaction will be transferred to the `complet
 
 This status has to be set if a payment requires an asset trustline that wasn't configured by the user. There are two ways of how the transaction may be moved to the `pending_trust` status. The first one is when the business server detects that the trustline isn't configured. The second one is when the business itself detects that the trustline is missing and wants to notify the user that it has to be configured. To move the transaction to the `pending_trust` status, make the following JSON-RPC request.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // request-trust.json
 [
   {
@@ -345,31 +345,31 @@ This status has to be set if a payment requires an asset trustline that wasn't c
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh request-trust.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::info
+<Info>
 
 The payment processing system periodically checks if the trustline was configured. If it was, it will automatically send a payment and change the status of the transaction to `pending_stellar`.
 
-:::
+</Info>
 
 ### Trust Set
 
 This status has to be set if the business has detected that the trustline was or wasn't configured by user.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // trust-set.json
 [
   {
@@ -385,33 +385,33 @@ This status has to be set if the business has detected that the trustline was or
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 - `success` flag which defines if trustline was or wasn't configured by user
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh trust-set.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::info
+<Info>
 
 Depending on the `success` flag, the status of the transaction will be changed to `pending_stellar` if the trustline was set, or to `pending_anchor` if it wasn't.
 
-:::
+</Info>
 
 ### Refund Sent
 
 Sometimes, funds need to be sent back to the user (refund). You can refund the whole sum (full refund) or do a set of partial refunds back to the `source_account` using the `refund_memo` and `refund_memo_type` associated with the transaction if present. Also, if user sent more money than expected, you can refund a part of the sum back to the user and send the rest as onchain funds.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // refund-sent.json
 [
   {
@@ -437,23 +437,23 @@ Sometimes, funds need to be sent back to the user (refund). You can refund the w
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh refund-sent.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::info
+<Info>
 
 If a sum of refunds is less than `amount_in`, the status of the transaction will be set to `pending_anchor`. Only if the sum of refunds is equal to `amount_in`, the status of the transaction will be set to `refunded`.
 
-:::
+</Info>
 
 ### Refund Pending
 
@@ -463,9 +463,9 @@ This is similar to [Refund Sent](#refund-sent), but it handles the case when a r
 
 If you encounter an unrecoverable error when processing the transaction, it's required to set the transaction status to `error`. You can use the message field to describe the error details.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // transaction-error.json
 [
   {
@@ -480,31 +480,31 @@ If you encounter an unrecoverable error when processing the transaction, it's re
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh transaction-error.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::tip
+<Tip>
 
 If a user has made a transfer, you should do a transaction recovery, and then you can retry processing the transaction or initiate a refund.
 
-:::
+</Tip>
 
 ### Expired Transaction
 
 Your business may want to handle abandoned transactions by expiring those have remained inactive for a certain period. To achieve this, check the transaction status using the `GET /transactions` endpoint and sort the results by the `user_action_required_by` timestamp. If the timestamp has passed, manually execute the appropriate logic, such as expiring the transaction or initiating an auto-refund, based on the transaction's current status.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // transaction-expired.json
 [
   {
@@ -519,31 +519,31 @@ Your business may want to handle abandoned transactions by expiring those have r
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh transaction-expired.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::tip
+<Tip>
 
 This JSON-RPC method can't be used after the user has made a transfer.
 
-:::
+</Tip>
 
 ### Transaction Recovery
 
 Transaction status can be changed from `error/expired` to `pending_anchor`. After recovery, you can refund the received assets or proceed with processing of the transaction. To recover a transaction, make the following JSON-RPC request.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // transaction-recovery.json
 [
   {
@@ -558,17 +558,17 @@ Transaction status can be changed from `error/expired` to `pending_anchor`. Afte
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh transaction-recovery.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## Updating Withdrawal (Exchange) Transaction Via JSON-RPC
 
@@ -578,7 +578,7 @@ The withdrawal exchange flow is the same as the withdrawal flow, except the amou
 
 [![sep6 withdrawal flow](/assets/ap/sep6-withdrawal-flow-diagram.png)](/assets/ap/sep6-withdrawal-flow-diagram.png)
 
-:::tip
+<Tip>
 
 Statuses in <span style={{color: "green"}}>green</span> are mandatory and define the shortest way.
 
@@ -586,19 +586,19 @@ Statuses in <span style={{color: "#B0BF1A"}}>yellow</span> are optional and can
 
 Statuses in <span style={{color: "red"}}>red</span> mean the transaction is in an error status or it has expired.
 
-:::
+</Tip>
 
 Once the withdrawal flow is finished, implementing the withdrawal is straightforward. Some parts of the flow are similar and can be reused.
 
 The starting point both for withdrawal and for deposit is the same.
 
-### Ready to Receive Funds
+### Ready to Receive Funds {#ready-to-receive-funds-1}
 
 Similarly to deposit, the step after KYC has been collected is to notify the user that the anchor is ready to receive funds. However, as your service will be receiving transactions over the Stellar network, the RPC request will be different. The anchor should use the `request_onchain_funds` RPC to provide the final amounts to the user. To do so, make the following JSON-RPC request.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // request-onchain-funds.json
 [
   {
@@ -631,7 +631,7 @@ Similarly to deposit, the step after KYC has been collected is to notify the use
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 - `amount_in` is the amount the user has to send to the business.
 - `amount_out` is the amount the user will receive.
@@ -643,21 +643,20 @@ Similarly to deposit, the step after KYC has been collected is to notify the use
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh request-onchain-funds.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::caution
+<Warning>
 
 For exchange withdrawals with a firm quote (the request is associated with a `quote_id`), no amounts should not be provided.
 
-:::
-
-:::tip
+</Warning>
+<Tip>
 
 Setting `memo`, `memo_type`, and `destination_account` is optional.
 
@@ -665,21 +664,20 @@ If integration with a third-party custodian is enabled, the Anchor Platform can
 
 If your business manages the assets, the Anchor Platform can generate memos for you. When the status is changed to `pending_user_transfer_start`, the Anchor Platform sets the `memo` and `memo_type` automatically (only if it's not included in the request).
 
-:::
-
-:::note
+</Tip>
+<Note>
 
 The Stellar account that will be used to receive funds should be configured.
 
-:::
+</Note>
 
-### Funds Received
+### Funds Received {#funds-received-1}
 
 If onchain funds were received, you need to provide amounts and change the status of the transaction to `pending_anchor`.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // onchain-funds-received.json
 [
   {
@@ -704,31 +702,31 @@ If onchain funds were received, you need to provide amounts and change the statu
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh onchain-funds-received.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::tip
+<Tip>
 
 This method will be called by the Stellar payment observer when it detects that onchain funds have been received.
 
-:::
+</Tip>
 
 ### Amount Updated
 
 If onchain funds were received, but for some reason the `amount_in` differs from specified in the interactive flow (`amount_expected`), you can update `amount_out` and `fee_details` to make them correspond to the actual `amount_in`. The status of the transaction in this case won't be changed and will be equal to `pending_anchor`.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // amounts-updated.json
 [
   {
@@ -749,31 +747,31 @@ If onchain funds were received, but for some reason the `amount_in` differs from
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh amounts-updated.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::note
+<Note>
 
 Only `amount_out` and `fee_details` can be updated using this JSON-RPC request, and you don't need to specify the assets of the amounts.
 
-:::
+</Note>
 
 ### Offchain Funds Available
 
 You can move transaction status to `pending_user_transfer_complete` if offchain funds were sent, and if it's ready for the user / recipient to pick it up.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // offchain-funds-available.json
 [
   {
@@ -789,25 +787,25 @@ You can move transaction status to `pending_user_transfer_complete` if offchain
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh offchain-funds-available.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Offchain Funds Pending
 
 Another option is to move the transaction's status to `pending_external`. This status means that the payment has been submitted to an external network, but is not yet confirmed.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // offchain-funds-pending.json
 [
   {
@@ -823,25 +821,25 @@ Another option is to move the transaction's status to `pending_external`. This s
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh offchain-funds-pending.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Offchain Funds Sent
 
 To complete the transaction and change its status to `completed`, you need to make the `notify_offchain_funds_sent` JSON-RPC request.
 
-<CodeExample>
+<CodeGroup>
 
-```json
+```json JSON
 // offchain-funds-sent.json
 [
   {
@@ -858,31 +856,31 @@ To complete the transaction and change its status to `completed`, you need to ma
 ]
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To execute this, you need to run:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./call-json-rpc.sh offchain-funds-sent.json
 ```
 
-</CodeExample>
+</CodeGroup>
 
-### Refund Sent
+### Refund Sent {#refund-sent-1}
 
 The refund logic works in the same way as for the deposit flow. For more details, see [Refund Sent](#refund-sent) of the deposit flow.
 
-### Transaction Error
+### Transaction Error {#transaction-error-1}
 
 Works in the same manner as for the deposit flow. For more details, see [Transaction Error](#transaction-error) of the deposit flow.
 
-### Expired Transaction
+### Expired Transaction {#expired-transaction-1}
 
 Works in the same manner as for the deposit flow. For more details, see [Expired Transaction](#expired-transaction) of the deposit flow.
 
-### Transaction Recovery
+### Transaction Recovery {#transaction-recovery-1}
 
 Works in the same manner as for the deposit flow. For more details, see [Transaction Recovery](#transaction-recovery) of the deposit flow.
 
@@ -891,7 +889,7 @@ Works in the same manner as for the deposit flow. For more details, see [Transac
 <Observer />
 
 [sep-6]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md
-[event-handling]: ../../admin-guide/events/README.mdx
-[customer-callback]: ../../api-reference/callbacks/README.mdx
-[rate-callback]: ../../api-reference/callbacks/README.mdx
-[get-transactions]: ../../api-reference/platform/transactions/get-transactions.api.mdx
+[event-handling]: /docs/platforms/anchor-platform/admin-guide/events
+[customer-callback]: /docs/platforms/anchor-platform/api-reference/callbacks
+[rate-callback]: /docs/platforms/anchor-platform/api-reference/callbacks
+[get-transactions]: /docs/platforms/anchor-platform/api-reference/platform/transactions/get-transactions
diff --git a/docs/platforms/index.mdx b/docs/platforms/index.mdx
new file mode 100644
index 000000000..3da5c1ea8
--- /dev/null
+++ b/docs/platforms/index.mdx
@@ -0,0 +1,16 @@
+---
+title: SDF Platforms
+description: 'SDF has open-sourced some "platforms" that make it easier to accomplish certain things on the network.'
+---
+
+## Anchor Platform
+
+The Anchor Platform is a set of tools and APIs that enable developers and businesses to build their own on and off-ramp services for the Stellar network. It provides a standardized interface, including the implementation of several Stellar Ecosystem Proposals (SEPs), to make it easy for businesses to integrate with Stellar-based wallets and exchanges.
+
+[Learn more about the Anchor Platform API here!](/docs/platforms/anchor-platform)
+
+## Stellar Disbursement Platform
+
+The Stellar Disbursement Platform (SDP) enables organizations to disburse bulk payments to recipients using Stellar.
+
+[Learn more about the Stellar Disbursement Platform API here!](/docs/platforms/stellar-disbursement-platform)
diff --git a/docs/platforms/stellar-disbursement-platform/README.mdx b/docs/platforms/stellar-disbursement-platform/README.mdx
deleted file mode 100644
index 9e818a972..000000000
--- a/docs/platforms/stellar-disbursement-platform/README.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: Stellar Disbursement Platform Introduction
-sidebar_label: Introduction
-pagination_label: Stellar Disbursement Platform Introduction
-sidebar_position: 10
-pagination_next: platforms/stellar-disbursement-platform/admin-guide/overview
----
-
-# Stellar Disbursement Platform
-
-The Stellar Disbursement Platform (SDP) is a tool built for organizations to make bulk payments to a group of recipients over the Stellar network.
-
-This is an open-source project that is built on top of the Stellar network, and the code can be found on the following repositories:
-
-- [stellar/stellar-disbursement-platform-backend](https://github.com/stellar/stellar-disbursement-platform-backend): This repository contains the backend and infrastructure code for the Stellar Disbursement Platform.
-- [stellar/stellar-disbursement-platform-frontend](https://github.com/stellar/stellar-disbursement-platform-frontend): This repository contains the web frontend code for the Stellar Disbursement Platform.
-- [stellar/helm-charts](https://github.com/stellar/helm-charts/tree/main/charts/stellar-disbursement-platform): This repository contains the Helm chart for deploying the Stellar Disbursement Platform using Kubernetes.
-
-In this section, you'll find an [Admin Guide](./admin-guide/overview.mdx) that will teach you how to run the Stellar Disbursement Platform as well as an [API Reference](./api-reference/admin.tag.mdx).
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/advanced-configuration.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/advanced-configuration.mdx
index bb8d02d3e..fcaeb9231 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/advanced-configuration.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/advanced-configuration.mdx
@@ -2,7 +2,6 @@
 title: Advanced Configuration
 description: Understand how to configure the SDP for various scenarios. This includes multi-tenancy, testnet vs. mainnet, etc.
 keywords: [SDP, configuration]
-sidebar_position: 45
 ---
 
 In this guide, you will learn about advanced configuration options for the Stellar Disbursement Platform (SDP). These configurations allow you to tailor the SDP to meet specific requirements, such as multi-tenancy, network selection, and performance tuning.
@@ -11,11 +10,11 @@ In this guide, you will learn about advanced configuration options for the Stell
 
 Upon provisioning a new SDP instance, it is configured to operate either in Mainnet or Testnet mode based on the environment variables set during setup. Most users will start with Testnet for development and testing purposes before transitioning to Mainnet for production use.
 
-:::caution
+<Warning>
 
 An SDP instance is designed to operate on either Testnet or Mainnet. Switching between these networks on an existing instance is not supported and may lead to unexpected behavior. If you need to change the network, it is recommended to set up a new SDP instance with the desired configuration.
 
-:::
+</Warning>
 
 Once you validated your setup on Testnet, you can deploy a new instance configured for Mainnet by setting the appropriate environment variables during the provisioning process.
 
@@ -125,7 +124,7 @@ curl -H "SDP-Tenant-Name: tenant1" https://sdp.stellar.org/ ...
 
 In a production environment, it is common to use subdomain routing. For example, `tenant1.sdp.stellar.org` and `tenant2.sdp.stellar.org` will both point to the same SDP instance.
 
-#### Helm Charts
+#### Helm Charts {#helm-charts-1}
 
 When deploying via Helm, you configure the wildcard domain using the `sdp.route.mtnDomain` value. This creates an Ingress rule that matches all subdomains.
 
@@ -138,11 +137,11 @@ sdp:
     mtnDomain: "*.sdp.stellar.org"
 ```
 
-:::note
+<Note>
 
 Ensure your DNS provider has a wildcard A record (e.g., `*.sdp.stellar.org`) pointing to your Ingress Controller's Load Balancer IP.
 
-:::
+</Note>
 
 #### Docker Compose (Local Development)
 
@@ -161,7 +160,7 @@ For local development with Docker Compose you must map specific tenant subdomain
 
 In multi-tenant mode, you provision new tenants using the Admin API (port `8003` by default). Each tenant will have its own isolated data.
 
-**Endpoint**: [POST /tenants](../api-reference/create-tenant.api.mdx) **Example Request:**
+**Endpoint**: [POST /tenants](/docs/platforms/stellar-disbursement-platform/api-reference/create-tenant) **Example Request:**
 
 ```bash
 curl --location 'http://localhost:8003/tenants' \
@@ -192,7 +191,7 @@ This is determined by the field `distribution_account_type` in the API call abov
 - **Key/Secret Isolation**: Segregated per tenant
 - **Appropriate for**: Multi-tenant and single-tenant
 - **How is it configured?**: The distribution account is randomly generated and funded during the provisioning process, and the secret is encrypted and safely stored in the database. The account is funded from the HOST distribution account by an amount defined in `TENANT_XLM_BOOTSTRAP_AMOUNT`.
-- **Multiple accounts**: This is the only account type that supports more than one distribution account per tenant. The account created here becomes the tenant's default, and Owners can add more from the dashboard. See [Distribution Accounts](./design-and-architecture.mdx#distribution-accounts).
+- **Multiple accounts**: This is the only account type that supports more than one distribution account per tenant. The account created here becomes the tenant's default, and Owners can add more from the dashboard. See [Distribution Accounts](./design-and-architecture#distribution-accounts).
 
 - `DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT`
 - **Platform**: [Circle](https://www.circle.com)
@@ -210,11 +209,11 @@ This is determined by the field `distribution_account_type` in the API call abov
 - **Appropriate for**: Single-tenant only
 - **How is it configured?**: The tenant will use the HOST account **as is**. The host is responsible for creating the account and configuring it with the `DISTRIBUTION_SEED` secret.
 
-:::warning
+<Warning>
 
 Once a tenant is created, the `distribution_account_type` cannot be changed. If you wish to use a different distribution account type, you will need to create a new tenant.
 
-:::
+</Warning>
 
 ## Embedded Wallets Configuration
 
@@ -231,11 +230,13 @@ To enable Embedded Wallets, you need to:
 3. Configure TSS with the same RPC endpoint
 4. Enable RPC features in the frontend dashboard
 
-:::caution[HTTPS Requirement]
+<Warning>
+
+**HTTPS Requirement**
 
 **The frontend dashboard MUST be served over HTTPS for Embedded Wallets to work.** Passkeys use the WebAuthn standard, which requires a secure context.
 
-:::
+</Warning>
 
 ### Backend (SDP Core Service) Configuration
 
@@ -271,10 +272,12 @@ The frontend dashboard requires a single environment variable to enable embedded
 
 ### HTTPS Requirement for Passkeys
 
-:::danger[Critical: HTTPS Required]
+<Danger>
+
+**Critical: HTTPS Required**
 
 Embedded Wallets use passkeys (WebAuthn) for authentication. **Passkeys only work in secure contexts**.
 
 If your frontend is not served over HTTPS, receivers will not be able to create passkeys or authenticate with their embedded wallets.
 
-:::
+</Danger>
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/cli-manual.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/cli-manual.mdx
index 0c0cc5b67..3b55d6e19 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/cli-manual.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/cli-manual.mdx
@@ -2,7 +2,6 @@
 title: CLI Manual
 description: Guide to using the Stellar Disbursement Platform CLI
 keywords: [SDP, CLI]
-sidebar_position: 50
 ---
 
 ## Root Command
@@ -15,7 +14,7 @@ The `stellar-disbursement-platform` is the main entry point for the application.
 stellar-disbursement-platform [command] [flags]
 ```
 
-:::tip
+<Tip>
 
 For all the following commands, you can use the `--help` flag to get more information about the command and its options. For example:
 
@@ -23,7 +22,7 @@ For all the following commands, you can use the `--help` flag to get more inform
 stellar-disbursement-platform serve --help
 ```
 
-:::
+</Tip>
 
 ## Global Flags
 
@@ -44,7 +43,7 @@ The following flags are available for all commands:
 
 The `serve` command starts the Stellar Disbursement Platform backend server. This server handles API requests, processes disbursements, and manages tenant operations.
 
-### Usage
+### Usage {#usage-1}
 
 ```bash
 stellar-disbursement-platform serve [flags]
@@ -120,7 +119,7 @@ The `tss` command runs the Transaction Submission Service, which is responsible
 stellar-disbursement-platform tss [flags]
 ```
 
-### Flags
+### Flags {#flags-1}
 
 | Flag | Description |
 | :-- | :-- |
@@ -175,7 +174,7 @@ The `db admin` command manages the migrations for the admin schema, which handle
 stellar-disbursement-platform db admin [command] [flags]
 ```
 
-#### Subcommands
+#### Subcommands {#subcommands-1}
 
 | Command   | Description               |
 | :-------- | :------------------------ |
@@ -384,7 +383,7 @@ stellar-disbursement-platform auth add-user <email> <first name> <last name> [fl
 | `--roles` | Set the user roles. It should be comma-separated. Example: `role1, role2`. Available roles: `owner`, `financial_controller`, `developer`, `business`, `initiator`, `approver`. |
 | `--tenant-id` | The tenant ID to which the user will be added. |
 
-#### Example
+#### Example {#example-1}
 
 To add a new user with specific roles and a password:
 
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/configuring-sdp.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/configuring-sdp.mdx
index 75db8cc7d..fc7798b91 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/configuring-sdp.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/configuring-sdp.mdx
@@ -2,31 +2,32 @@
 title: Configuration
 description: Understand the configuration options available for the Stellar Disbursement Platform (SDP)
 keywords: [SDP, configuration]
-sidebar_position: 40
 ---
 
 Stellar Disbursement Platform services can be configured using a set of configuration options that are passed to the command line or set as environment variables. Depending on how you're using and deploying the SDP, these configurations can be set in a ConfigMap in Kubernetes, as environment variables in a Docker container, passed in as command line arguments, etc.
 
 In this section we will discuss the different configuration options available for the SDP.
 
-:::tip[Notes]
+<Tip>
+
+**Notes**
 
 - Configurations that are tagged with 🔑 are sensitive and should be stored securely.
 - All configurations can be passed in as either environment variables or CLI flags. For instance, the env var `BASE_URL` could be passed in through the `--base-url` flag. CLI flags take priority over env vars, even though env vars are more convenient.
 
-:::
+</Tip>
 
 ## SDP Core Service
 
 For the most up-to-date configuration, you can run the following command in the [stellar-disbursement-platform-backend git repository](https://github.com/stellar/stellar-disbursement-platform-backend):
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./stellar-disbursement-platform serve --help
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Operational Configuration
 
@@ -157,7 +158,7 @@ The following configurations are required when using Google reCAPTCHA v2 to prot
 - `ADMIN_API_KEY`: The api key of the admin accountused to authenticate HTTP requests to the Admin server. The Admin-targeted requests should add the "Authorization" header, formatted as Base64-encoded `"ADMIN_ACCOUNT:ADMIN_API_KEY"`.
 - `ADMIN_PORT`: the port of the Admin server used to create and manage tenants. Default is 8003.
 - `INSTANCE_NAME`: the name of the SDP instance to be displayed in the `stellar.toml` file. Example: "SDP Testnet".
-- `SINGLE_TENANT_MODE`: When set to `"true"`, it enables the single-tenant mode, which is useful for local development or single-tenant setups. In addition to set it to true, you'll need to configure the default tenant by calling the [`POST /tenants/default-tenant`](../api-reference/default-tenant.api.mdx) request.
+- `SINGLE_TENANT_MODE`: When set to `"true"`, it enables the single-tenant mode, which is useful for local development or single-tenant setups. In addition to set it to true, you'll need to configure the default tenant by calling the [`POST /tenants/default-tenant`](/docs/platforms/stellar-disbursement-platform/api-reference/default-tenant) request.
 - `TENANT_XLM_BOOTSTRAP_AMOUNT`: The amount of XLM that the HOST Stellar account will deposit deposited to the tenant distribution account for tenant bootstrap.
 
 ### Bridge Integration Configuration
@@ -172,19 +173,19 @@ The following configurations are required when using the Bridge Integration.
 
 For the most up-to-date configuration, you can run the following command in the [stellar-disbursement-platform-backend git repository](https://github.com/stellar/stellar-disbursement-platform-backend):
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 ./stellar-disbursement-platform tss --help
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### General Configuration
 
 - `QUEUE_POLLING_INTERVAL` - Polling interval (seconds) to query the database for pending transactions to process. Default: 6.
 
-### Operational Configuration
+### Operational Configuration {#operational-configuration-1}
 
 Operational Configuration allows controlling metrics, logging, and other operational aspects of the Transaction Submission Servic (TSS)
 
@@ -196,7 +197,7 @@ Operational Configuration allows controlling metrics, logging, and other operati
 - `SENTRY_DSN` - 🔑 The DSN (client key) of the Sentry project. If not provided, Sentry will not be used.
 - `ENVIRONMENT` - The environment where the application is running. Example: "development", "staging", "production". Default: "development".
 
-### Database Configuration
+### Database Configuration {#database-configuration-1}
 
 The following configurations are related to the PostgreSQL database used by the SDP Core Service.
 
@@ -206,7 +207,7 @@ The following configurations are related to the PostgreSQL database used by the
 - `DB_CONN_MAX_IDLE_TIME_SECONDS` - Close idle connections after N seconds. Default: 10.
 - `DB_CONN_MAX_LIFETIME_SECONDS` - Recycle connections after N seconds. Default: 300.
 
-### Stellar Configuration
+### Stellar Configuration {#stellar-configuration-1}
 
 Stellar Configuration allows configuring accounts, transactions, and other Stellar-related settings.
 
@@ -214,14 +215,14 @@ Stellar Configuration allows configuring accounts, transactions, and other Stell
 - `HORIZON_URL` - The URL of the Horizon server to use for submitting transactions. Default "https://horizon-testnet.stellar.org/".
 - `MAX_BASE_FEE` - The max base fee for submitting a Stellar transaction. Default: 10000.
 
-#### Channel Accounts Configuration
+#### Channel Accounts Configuration {#channel-accounts-configuration-1}
 
 The following configurations are required for using channel accounts to submit transactions to the Stellar network.
 
 - `NUM_CHANNEL_ACCOUNTS` - Number of channel accounts to utilize for transaction submission. Default: 2.
 - `CHANNEL_ACCOUNT_ENCRYPTION_PASSPHRASE` - 🔑 A Stellar ed25519 secret key (starting with `S`) used to encrypt/decrypt the channel accounts' private keys. When not set, it will default to the value of the 'DISTRIBUTION_SEED' option.
 
-#### Distribution Accounts Configuration
+#### Distribution Accounts Configuration {#distribution-accounts-configuration-1}
 
 The following configurations are related to the distribution accounts used to send funds to recipients. This configuration should match the configuration in the SDP Core Service.
 
@@ -233,10 +234,10 @@ The following configurations are related to the distribution accounts used to se
 
 The SDP Dashboard is a web application that allows users to manage their accounts, view transaction history, and more. Environment variables can be set either on a global `window._env_` object or as `process.env` variables. All environment variables used in this repo are in `src/constants/envVariables.ts` file, including types. The default location of the `window._env_` object is `public/settings/env-config.js`.
 
-### General Configuration
+### General Configuration {#general-configuration-1}
 
 - `API_URL` - The base URL of the SDP Core Service. Default: "http://localhost:8000".
 - `STELLAR_EXPERT_URL` - The base URL of the Stellar Expert explorer. Default: "https://stellar.expert/explorer/testnet".
 - `HORIZON_URL` - The base URL of the Horizon server. Default: "https://horizon-testnet.stellar.org".
 - `RECAPTCHA_SITE_KEY` - The Google reCAPTCHA v2 - I'm not a robot site key. This key needs to match the key used in the SDP Core Service.
-- `SINGLE_TENANT_MODE` - When set to `"true"`, it enables the single-tenant mode, which is useful for local development or single-tenant setups. In addition to set it to true, you'll need to configure the default tenant by calling the [`POST /tenants/default-tenant`](../api-reference/default-tenant.api.mdx) request. Default: "false".
+- `SINGLE_TENANT_MODE` - When set to `"true"`, it enables the single-tenant mode, which is useful for local development or single-tenant setups. In addition to set it to true, you'll need to configure the default tenant by calling the [`POST /tenants/default-tenant`](/docs/platforms/stellar-disbursement-platform/api-reference/default-tenant) request. Default: "false".
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/deploy-the-sdp.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/deploy-the-sdp.mdx
index d22c2eec7..75782ecff 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/deploy-the-sdp.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/deploy-the-sdp.mdx
@@ -1,6 +1,6 @@
 ---
 title: Deployment
-sidebar_position: 30
+description: "Add the official Stellar Helm chart repository to your local Helm client."
 ---
 
 ## Deployment via Helm Charts
@@ -45,11 +45,11 @@ The following parameters can be set in the `minimal-values.yaml` file or overrid
 
 Refer to the [Helm Chart README](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/helmchart/sdp/README.md#parameters) for a complete list of parameters.
 
-:::tip
+<Tip>
 
-There is a more detailed explanation of how to configure the SDP in the [Configuration Guide](configuring-sdp).
+There is a more detailed explanation of how to configure the SDP in the [Configuration Guide](/docs/platforms/stellar-disbursement-platform/admin-guide/configuring-sdp).
 
-:::
+</Tip>
 
 #### 3. Install the Chart
 
@@ -67,7 +67,7 @@ helm install sdp -f minimal-values.yaml stellar/stellar-disbursement-platform \
 
 This section outlines how to deploy the SDP using Docker Compose for a production-like environment. Unlike the development setup, this configuration uses pre-built production images and requires explicit configuration of environment variables and secrets.
 
-### Minimum System Requirements
+### Minimum System Requirements {#minimum-system-requirements-1}
 
 - **Stellar Accounts**: You will need a **Distribution Account** (funded) and a **SEP-10 Signing Account**.
 - **Network Access**: Outbound access to the Stellar network (Horizon/Soroban) and any third-party integrations (Twilio, AWS SES, etc.).
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/design-and-architecture.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/design-and-architecture.mdx
index 0418be9d7..92d220b8b 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/design-and-architecture.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/design-and-architecture.mdx
@@ -1,19 +1,19 @@
 ---
 title: Architecture
-sidebar_position: 20
+description: "The Stellar Disbursement Platform consists of three services deployed together."
 ---
 
 The Stellar Disbursement Platform consists of three services deployed together:
 
 - **Dashboard**: the user interface administrators use to initiate and track the progress of disbursements
 - **SDP Core Service**: the core backend service that performs several functions:
-  - **Dashboard API**: the API used by the front-end UI for all disbursement requests. The API is documented [here](../api-reference)
-  - **Admin API**: the API used by the host organization to manage tenant provisioning and configuration. The API is documented [here](../api-reference/admin)
+  - **Dashboard API**: the API used by the front-end UI for all disbursement requests. The API is documented [here](https://developers.stellar.org/docs/platforms/stellar-disbursement-platform/api-reference)
+  - **Admin API**: the API used by the host organization to manage tenant provisioning and configuration. The API is documented [here](/docs/platforms/stellar-disbursement-platform/api-reference/admin)
   - **Messaging Service**: a recurring process that sends text messages to users prompting them to download the wallet selected for a particular disbursement and verify their phone with an OTP
   - **Wallet Registration**: a web application registers a recipient by collecting and verifying their OTP code and verification information via Stellar’s [SEP-24: Hosted Deposit and Withdrawal](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md) protocol
 - **Transaction Submission Service**: the service that submits all payment transactions to the Stellar network. This service is designed to maximize payment throughput, handle queuing, and graceful resubmission/error handling
 
-## Dependencies {/* #dependencies */}
+## Dependencies {#dependencies}
 
 - **Container Orchestration**: the SDP is packaged as Docker containers and can be deployed to Kubernetes or AWS Fargate. SDF provides a Helm Chart for Kubernetes
 - **Postgres**: the SDP uses a Postgres database server for all of its services
@@ -26,7 +26,7 @@ The Stellar Disbursement Platform consists of three services deployed together:
 
 ![Architecture Diagram](/assets/SDP/SDP2-2.png)
 
-### User Roles {/* #user-roles */}
+### User Roles {#user-roles}
 
 The SDP defines the following user roles:
 
@@ -35,14 +35,14 @@ The SDP defines the following user roles:
 - **API User**: a user that belongs to a tenant and uses the `Dashboard API` to create and manage disbursements, recipients, and other tenant-specific data programmatically
 - **Receivers**: the end users that receive the funds sent via the SDP. Receivers can either use a wallet application that supports SEP-24 for automatic registration, or they can receive funds directly to their Stellar account.
 
-### Workflow {/* #workflow */}
+### Workflow {#workflow}
 
 1. Host admin uses the `Tenant Admin` API to provision and manage tenants.
 2. `Dashboard User` and `API User` use the SDP Core Service to send disbursements and manage / invite other users. This can be done via the Dashboard UI or directly via the `Dashboard API`.
 3. For payments that require SEP-24 registration, the `SDP Core Service` sends a message to notify the receivers. The message contains a deeplink that launches the target wallet, which in turn triggers the **SEP-24 deposit flow** and registers the receivers.
 4. The TSS pulls payments that ready to be processed then submits them to the Stellar Network through Channel Accounts.
 
-## Database & Schemas {/* #database */}
+## Database & Schemas {#database}
 
 The SDP uses a Postgres database for all of its services. The database schema is managed by the SDP Core Service and is versioned in the codebase. The database schema is designed to be tenant-aware, meaning that each tenant has its own set of tables and data. This allows the SDP to be multi-tenant and support multiple organizations using the same instance.
 
@@ -52,9 +52,9 @@ There are 3 types of schemas in the database:
 - **TSS Schema**: contains tables for managing transactions. This schema is used by the Transaction Submission Service to manage the state of payment transactions.
 - **Tenant Schemas**: each tenant has its own schema that contains tables for managing disbursements, recipients, and other tenant-specific data. These schemas are prefixed with `sdp_`.
 
-## Distribution Accounts {/* #distribution-accounts */}
+## Distribution Accounts {#distribution-accounts}
 
-Each tenant sends funds from one or more distribution accounts. A tenant starts with a single account, created when the tenant is provisioned, which is marked as the default. Tenants using the other account types described in [Multi-tenant Distribution Accounts](./advanced-configuration.mdx#multi-tenant-distribution-accounts) keep a single account.
+Each tenant sends funds from one or more distribution accounts. A tenant starts with a single account, created when the tenant is provisioned, which is marked as the default. Tenants using the other account types described in [Multi-tenant Distribution Accounts](./advanced-configuration#multi-tenant-distribution-accounts) keep a single account.
 
 Tenants configured with the `DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT` account type can hold up to 20 accounts, and Owners can add more at any time from the dashboard.
 
@@ -63,13 +63,13 @@ Tenants configured with the `DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT` account type
 - Accounts are archived rather than deleted, so past disbursements and payments keep pointing at the account that sent them.
 - Exactly one account is the default, and it cannot be archived. It is what a tenant starts with, and what pre-multi-distribution account records are attributed to.
 
-Access to an account is granted per user, and is separate from the user's role. See [Security](./security.mdx) for how the two combine.
+Access to an account is granted per user, and is separate from the user's role. See [Security](./security) for how the two combine.
 
-## Multi-tenancy {/* #multi-tenancy */}
+## Multi-tenancy {#multi-tenancy}
 
 The SDP can be deployed in a multi-tenant configuration, where multiple organizations share the same instance of the SDP. Each organization is referred to as a tenant and has its own set of data and configuration. A host organization can manage multiple tenants and manage their configuration through the Admin API.
 
-### Tenant Resolution {/* #tenant-resolution */}
+### Tenant Resolution {#tenant-resolution}
 
 The SDP uses a tenant resolution strategy to determine which tenant a request belongs to. Tenant resolution is only required for unauthenticated requests, as authenticated requests include the tenant information already in the JWT token.
 
@@ -78,13 +78,13 @@ The SDP uses a tenant resolution strategy to determine which tenant a request be
 
 Resolution priority goes as follows: JWT token (authenticated requests) > Header > Subdomain.
 
-#### Single Tenant Mode {/* #single-tenant-mode */}
+#### Single Tenant Mode {#single-tenant-mode}
 
-When single tenant mode is enabled using the `SINGLE_TENANT_MODE` environment variable, all tenants will automatically resolve to the default tenant. A default tenant is set by calling the API [`POST /tenants/default-tenant`](../api-reference/default-tenant.api.mdx).
+When single tenant mode is enabled using the `SINGLE_TENANT_MODE` environment variable, all tenants will automatically resolve to the default tenant. A default tenant is set by calling the API [`POST /tenants/default-tenant`](/docs/platforms/stellar-disbursement-platform/api-reference/default-tenant).
 
 Default tenant is useful for development purposes or when the SDP is used by a single organization. This allows the organization to skip specifying the tenant in every request and simplifies the SDP setup operationally by removing the need of providing wildcard TLS certificates for multi-tenant configurations.
 
-#### Subdomain Resolution {/* #subdomain-resolution */}
+#### Subdomain Resolution {#subdomain-resolution}
 
 When running the SDP in multi-tenant mode, the SDP uses the subdomain of the request URL to resolve the tenant. For example, `tenant1.sdp.backend.test` would resolve to the tenant `tenant1`. This allows the SDP to differentiate between tenants without requiring the tenant name to be specified in the request.
 
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/embedded-wallets.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/embedded-wallets.mdx
index 45ba17f51..8a19af665 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/embedded-wallets.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/embedded-wallets.mdx
@@ -2,11 +2,8 @@
 title: Embedded Wallets
 description: Learn how to use Embedded Wallets to enable receivers without existing Stellar wallets to receive disbursements using passkey authentication.
 keywords: [embedded wallets, passkeys, WebAuthn, smart contracts, disbursements]
-sidebar_position: 50
 ---
 
-# Embedded Wallets
-
 ## Introduction
 
 Embedded Wallets allow receivers to receive disbursements without needing to download or manage a separate wallet application. When you create a disbursement with Embedded Wallets as the target wallet provider, the SDP automatically creates a lightweight, passkey-secured smart contract wallet for each receiver.
@@ -61,11 +58,13 @@ When a receiver creates an embedded wallet:
 
 **No Weak Passwords**: Users can't create weak or easily-guessed credentials. All passkeys use strong cryptography.
 
-:::info[Learn More About Passkeys]
+<Info>
+
+**Learn More About Passkeys**
 
 For more details about passkey technology, visit [passkeys.dev](https://passkeys.dev/docs/intro/what-are-passkeys) or read about the [WebAuthn specification](https://www.w3.org/TR/webauthn).
 
-:::
+</Info>
 
 ---
 
@@ -80,11 +79,11 @@ The Embedded Wallet flow includes the following steps:
 5. **Verification**: The receiver completes identity verification (e.g., entering an OTP or date of birth)
 6. **Payment Transfer**: Once verified, the SDP automatically transfers the disbursement funds to the receiver's contract wallet
 
-:::danger
+<Danger>
 
 Each link is unique per receiver. Treat it as sensitive: if a link is leaked and you have **no verification** enabled, an attacker could create the receiver’s wallet and claim the funds. Skipping verification should only be done in low-risk scenarios and with small disbursement amounts.
 
-:::
+</Danger>
 
 ### Behind the Scenes
 
@@ -127,11 +126,11 @@ When creating a new disbursement, select **"Embedded Wallet"** as the wallet pro
 - **Asset**: Choose the asset to disburse (e.g., USDC, XLM)
 - **Verification Type**: Select what information receivers must verify (e.g., PIN, date of birth)
 
-:::note
+<Note>
 
 There is also a "None" option, but using it is only recommended for low-risk scenarios due to security concerns (e.g. disbursing small amounts).
 
-:::
+</Note>
 
 Once you've uploaded your disbursement CSV file and submitted the disbursement, the SDP will begin sending invitations to all receivers in the list.
 
@@ -145,13 +144,15 @@ Receivers will receive an invitation message (via SMS or email) with a secure li
 https://your-tenant.sdp.stellar.org/wallet?asset=native&token=c09bd254-b77a-4685-bc18-377231484267&signature=26b48d7ce...
 ```
 
-:::danger[Reminder]
+<Danger>
+
+**Reminder**
 
 Each link is unique per receiver. Treat it as sensitive: if a link is leaked and you have **no verification** enabled, an attacker could create the receiver’s wallet and claim the funds. Skipping verification should only be done in low-risk scenarios and with small disbursement amounts.
 
 We also recommend enabling verification because it requires users to authenticate via SEP-45 before receiving funds. This confirms their passkey works correctly. This helps avoid cases where accounts are created and funds disbursed, but users are prevented from accessing the wallet due to passkey issues that would have been caught during verification.
 
-:::
+</Danger>
 
 When the receiver clicks the link, they'll see a page inviting them to create their wallet account:
 
@@ -173,11 +174,13 @@ When the receiver clicks the link, they'll see a page inviting them to create th
 - The Transaction Submission Service (TSS) deploys the contract to the Stellar network
 - Once deployed, the receiver's wallet is ready to receive funds
 
-:::tip[Returning Users]
+<Tip>
+
+**Returning Users**
 
 If a receiver already has a passkey for a different disbursement, they can simply authenticate with their existing passkey instead of creating a new one. The same passkey can be used across multiple disbursements.
 
-:::
+</Tip>
 
 ---
 
@@ -201,13 +204,15 @@ The verification step ensures that the receiver is who they claim to be. Dependi
 3. If verification succeeds, the receiver wallet status changes from `READY` to `REGISTERED`
 4. The SDP automatically initiates the payment to the receiver's contract wallet address
 
-:::info[Verification Flow]
+<Info>
+
+**Verification Flow**
 
 The verification process uses the SDP's native SEP-24 implementation. The receiver authenticates with a SEP-24 JWT token that's generated during the passkey authentication flow.
 
 For background on SEP-45 (contract-account web authentication), see [SEP-45](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0045.md).
 
-:::
+</Info>
 
 ---
 
@@ -232,7 +237,7 @@ Once verification is complete, the SDP automatically transfers the disbursement
 
 To learn more about the technologies behind Embedded Wallets, check out these resources:
 
-### Passkeys & WebAuthn
+### Passkeys & WebAuthn {#passkeys--webauthn}
 
 - [passkeys.dev](https://passkeys.dev) - Comprehensive guide to passkeys
 - [WebAuthn Specification](https://www.w3.org/TR/webauthn) - W3C standard for web authentication
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/getting-started.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/getting-started.mdx
index df0bb62ca..f188e0804 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/getting-started.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/getting-started.mdx
@@ -1,6 +1,6 @@
 ---
 title: Getting Started
-sidebar_position: 10
+description: "This guide covers running the Stellar Disbursement Platform locally, sending a sample disbursement, and claiming it through the demo wallet on Testnet."
 ---
 
 This guide covers running the Stellar Disbursement Platform locally, sending a sample disbursement, and claiming it through the demo wallet on Testnet. Treat this walkthrough as a learning environment rather than the path for production deployments.
@@ -81,11 +81,11 @@ Click the Review button. When you are ready to start the disbursement, click the
 
 ### Receive Payment
 
-:::note
+<Note>
 
-This section shows the Testnet-only Demo Wallet flow so you can observe the receiver experience while running SDP locally. For production or real wallet integrations, follow the guidance in [Making Your Wallet SDP-Ready](./making-your-wallet-sdp-ready.mdx).
+This section shows the Testnet-only Demo Wallet flow so you can observe the receiver experience while running SDP locally. For production or real wallet integrations, follow the guidance in [Making Your Wallet SDP-Ready](./making-your-wallet-sdp-ready).
 
-:::
+</Note>
 
 Claim the payment in the demo wallet by first creating a wallet:
 
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/index.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/index.mdx
new file mode 100644
index 000000000..329b469d6
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/index.mdx
@@ -0,0 +1,4 @@
+---
+title: Admin Guide
+description: "All you need to know about setting up, running, and using the Stellar Disbursement Platform."
+---
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/making-your-wallet-sdp-ready.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/making-your-wallet-sdp-ready.mdx
index d77e6f7aa..13bce7169 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/making-your-wallet-sdp-ready.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/making-your-wallet-sdp-ready.mdx
@@ -1,6 +1,6 @@
 ---
 title: Making Your Wallet SDP-Ready
-sidebar_position: 80
+description: "Remember that any SDP instance will need an agreement with a wallet provider before sending disbursements into that wallet."
 ---
 
 Remember that any SDP instance will need an agreement with a wallet provider before sending disbursements into that wallet. This ensures the wallets are comfortable receiving funds from your organization and governs any commercial arrangement between the organizations. The wallet will need to allowlist the SDP domain before the SDP can send disbursements to that wallet. When the wallet domain is added to a SDP, it's effectively being allowlisted by the SDP. Both sides listing the other allows them to retrieve the stellar.toml file and check the signing key needed for the [SEP-10] handshake.
@@ -13,20 +13,20 @@ The default list of SDP wallets depends on which network is being used (testnet
 
 To insert it directly into the database, update your values and run the following Postgres query. Make sure to check your database and namespace first.
 
-<CodeExample>
+<CodeGroup>
 
-```sql
+```sql SQL
 INSERT INTO wallets (name, homepage, deep_link_schema, sep_10_client_domain)
 VALUES ('Vibrant Assist', 'https://vibrantapp.com', 'https://vibrantapp.com/sdp', 'api.vibrantapp.com');
 ```
 
-</CodeExample>
+</CodeGroup>
 
 To configure a wallet through the code, add it to the testnet or pubnet section of `DefaultWalletsNetworkMap`. This will be used when you execute the `./stellar-disbursement-platform db setup-for-network` CLI command, which updates the SDP database and makes the wallet available for new disbursements. Add your new wallet following the same format already present in the code.
 
-<CodeExample>
+<CodeGroup>
 
-```go
+```go Go
 var DefaultWalletsNetworkMap = WalletsNetworkMapType{
 	utils.PubnetNetworkType: {
 		{
@@ -53,7 +53,7 @@ var DefaultWalletsNetworkMap = WalletsNetworkMapType{
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## Recipient Registration Experience
 
@@ -80,11 +80,11 @@ https://<host-with-optional-path>?asset=<asset>&domain=<domain>&name=<name>&sign
 - `name`: the name of the organization sending payments.
 - `signature`: a signature from the SDP's [SEP-10] signing key.
 
-:::info
+<Info>
 
 Note that the deep link is specific to each SDP, payer org, and asset. It is not specific per individual receiver. There is no risk in sharing the link with receivers who are part of the same disbursement. The link will be the same for multiple receivers and they will prove their identity as part of the [SEP-24] deposit flow.
 
-:::
+</Info>
 
 Below is an example of a registration link (signed)
 
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/monitoring.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/monitoring.mdx
index 1703d5aea..1a47af8a1 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/monitoring.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/monitoring.mdx
@@ -2,7 +2,6 @@
 title: Monitoring
 description: How the SDP exposes runtime metrics and logs, and how to wire them into Prometheus and Grafana
 keywords: [SDP, monitoring, metrics, Prometheus, Grafana, Loki]
-sidebar_position: 70
 ---
 
 This guide explains how the Stellar Disbursement Platform (SDP) exposes runtime metrics and how to hook those metrics into the Prometheus + Grafana stack.
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/overview.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/overview.mdx
index e9378c632..5dfbc0e32 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/overview.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/overview.mdx
@@ -1,7 +1,6 @@
 ---
 title: Overview
-sidebar_position: 5
-pagination_label: "Admin Guide: Overview"
+description: "The entire SDP step-by-step process usually looks something like the following after the SDP is deployed and organizational users have been set up."
 ---
 
 The entire SDP step-by-step process usually looks something like the following after the SDP is deployed and organizational users have been set up:
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/security.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/security.mdx
index 7c2b4eff5..6eb5baa4e 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/security.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/security.mdx
@@ -1,6 +1,6 @@
 ---
 title: Security
-sidebar_position: 60
+description: "This manual outlines the security measures implemented in the Stellar Disbursement Platform (SDP) to protect the integrity of the platform and its users."
 ---
 
 This manual outlines the security measures implemented in the Stellar Disbursement Platform (SDP) to protect the integrity of the platform and its users. By adhering to these guidelines, you can ensure that your use of the SDP is as secure as possible.
@@ -58,11 +58,11 @@ Each API endpoint specifies which JWT roles may access it—for example, API key
 
 #### Distribution Account Access
 
-Roles are tenant-wide and determine what a user may do. Access to a [distribution account](./design-and-architecture.mdx#distribution-accounts) is granted separately, per account, and determines where they may do it. Both are required: a user who holds the right role but no access to an account cannot act on that account, and a user with access to an account cannot exceed what their role allows there.
+Roles are tenant-wide and determine what a user may do. Access to a [distribution account](./design-and-architecture#distribution-accounts) is granted separately, per account, and determines where they may do it. Both are required: a user who holds the right role but no access to an account cannot act on that account, and a user with access to an account cannot exceed what their role allows there.
 
 The Owner role is the exception. It applies tenant-wide, is never scoped to a single account, and is the only role that can grant or revoke access to accounts.
 
-Owners manage per-distribution account access from [Dashboard Home](./user-interface/dashboard-home.mdx#managing-access), choosing the role a user holds on that account. A user who has been given no account access can sign in but sees no disbursements, payments, or receivers.
+Owners manage per-distribution account access from [Dashboard Home](./user-interface/dashboard-home#managing-access), choosing the role a user holds on that account. A user who has been given no account access can sign in but sees no disbursements, payments, or receivers.
 
 #### API Key Permissions
 
@@ -81,11 +81,11 @@ Available scopes map directly to the major SDP resources:
 - `read:statistics`
 - `read:exports`
 
-In addition to permissions, an API key can be restricted to acting on specific [distribution accounts](./design-and-architecture.mdx#distribution-accounts) through the `distribution_wallet_ids` field. For tenant-wide changes (`/organization` and `/distribution-wallets`), the API key must be minted by an Owner.
+In addition to permissions, an API key can be restricted to acting on specific [distribution accounts](./design-and-architecture#distribution-accounts) through the `distribution_wallet_ids` field. For tenant-wide changes (`/organization` and `/distribution-wallets`), the API key must be minted by an Owner.
 
 #### Selecting an Account
 
-In the dashboard, the active distribution account that requests act on is chosen in the [account picker](./user-interface/account-picker.mdx). Integrations calling the API directly set the `X-Wallet-Id` header themselves.
+In the dashboard, the active distribution account that requests act on is chosen in the [account picker](./user-interface/account-picker). Integrations calling the API directly set the `X-Wallet-Id` header themselves.
 
 The header narrows what a request reaches and never widens it. A caller with access to three accounts that names one of them acts only on that one, and naming an account they have no access to reaches nothing.
 
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/troubleshooting.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/troubleshooting.mdx
index 5d2677bfa..a3c87c36b 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/troubleshooting.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/troubleshooting.mdx
@@ -1,11 +1,8 @@
 ---
 title: Troubleshooting
-sidebar_position: 90
+description: "This guide helps you diagnose and resolve common issues with the Stellar Disbursement Platform (SDP)."
 ---
 
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
 This guide helps you diagnose and resolve common issues with the Stellar Disbursement Platform (SDP).
 
 ## Quick Reference
@@ -27,7 +24,7 @@ This guide helps you diagnose and resolve common issues with the Stellar Disburs
 
 ## Payments
 
-### Payment Stuck in "Pending" {/* #payment-stuck-in-pending */}
+### Payment Stuck in "Pending" {#payment-stuck-in-pending}
 
 Payments can get stuck in "Pending" status for several reasons. Work through these checks in order.
 
@@ -58,35 +55,34 @@ Use [Stellar Expert](https://stellar.expert/explorer/public) or the Stellar CLI
 
 Channel accounts may become invalid after testnet resets. Look for errors like this in your logs:
 
-<details>
-  <summary>Example error: "Resource Missing"</summary>
+<Accordion title='Example error: "Resource Missing"'>
 
 ```
 time="2025-12-19T18:43:37.017Z" level=error msg="[DRY_RUN Crash Reporter] unexpected TSS error: preparing bundle for processing: building transaction: horizon response error: getting account detail: horizon error: \"Resource Missing\" - check horizon.Error.Problem for more information" app_version=6.0.1 asset=XLM channel_account=GBKEVxxxx ...
 ```
 
-</details>
+</Accordion>
 
 **Diagnosis:** This error means either the **destination account** or the **channel account** doesn't exist on the network. Check both using [Stellar Expert](https://stellar.expert/explorer/public).
 
 **Solution:**
 
 <Tabs>
-<TabItem value="destination" label="Destination Account Missing">
+<Tab title="Destination Account Missing">
 
 The receiver's account hasn't been created on the Stellar network. The account must be funded with the minimum balance (currently 1 XLM on mainnet) before it can receive payments.
 
-</TabItem>
-<TabItem value="channel" label="Channel Accounts Missing">
+</Tab>
+<Tab title="Channel Accounts Missing">
 
 Channel accounts may disappear after testnet resets. See [Recreating Channel Accounts](#recreating-channel-accounts) below.
 
-</TabItem>
+</Tab>
 </Tabs>
 
 ---
 
-### Payment Failed with Operation Error {/* #payment-failed-operation-error */}
+### Payment Failed with Operation Error {#payment-failed-operation-error}
 
 When a payment fails, the Status History shows a Horizon error with operation codes that explain why the transaction was rejected.
 
@@ -110,18 +106,19 @@ The operation code (e.g., `op_no_trust`) tells you exactly what went wrong.
 | `op_underfunded` | Source account doesn't have enough of the asset | Fund the payment's source distribution account with more of the asset |
 | `op_no_destination` | Destination account doesn't exist | Receiver must create and fund their Stellar account first |
 
-:::info[Trustlines explained]
+<Info>
+
+**Trustlines explained**
 
 On Stellar, accounts must explicitly "trust" an asset before receiving it. This is a security feature—it prevents spam tokens. The receiver needs to add a trustline for the specific asset (like EURC) using their wallet or a Stellar tool.
 
-Accounts added from the dashboard get their trustlines automatically. If that step fails and the account is active with no trustline for the asset, add it from the Trustlines panel on the [Distribution Accounts](./user-interface/distribution-accounts.mdx) page.
+Accounts added from the dashboard get their trustlines automatically. If that step fails and the account is active with no trustline for the asset, add it from the Trustlines panel on the [Distribution Accounts](./user-interface/distribution-accounts) page.
 
-:::
+</Info>
 
 #### Example: `op_no_trust`
 
-<details>
-  <summary>Full error message</summary>
+<Accordion title="Full error message">
 
 ```
 horizon response error: StatusCode=400, Type=https://stellar.org/horizon-errors/transaction_failed,
@@ -131,7 +128,7 @@ Descriptions of each code can be found at: https://developers.stellar.org/docs/d
 Extras=transaction: tx_fee_bump_inner_failed - inner transaction: tx_failed - operation codes: [ op_no_trust ]
 ```
 
-</details>
+</Accordion>
 
 **Diagnosis:** The receiver account exists but hasn't added a trustline for the asset you're trying to send (in this case, EURC).
 
@@ -141,7 +138,7 @@ For a complete list of operation result codes, see the [Stellar documentation](h
 
 ---
 
-### Slow Payments Due to Insufficient Channel Accounts {/* #slow-payments-due-to-insufficient-channel-accounts */}
+### Slow Payments Due to Insufficient Channel Accounts {#slow-payments-due-to-insufficient-channel-accounts}
 
 If payments are processing slower than expected, you may not have enough channel accounts. Channel accounts allow the SDP to submit multiple transactions in parallel. Without enough of them, transactions queue up and process sequentially.
 
@@ -167,7 +164,9 @@ Use the `ensure` command to increase the number of channel accounts. This comman
 ./stellar-disbursement-platform channel-accounts ensure 10
 ```
 
-:::tip[How many channel accounts do you need?]
+<Tip>
+
+**How many channel accounts do you need?**
 
 The optimal number depends on your disbursement volume:
 
@@ -176,7 +175,7 @@ The optimal number depends on your disbursement volume:
 
 Start with a conservative number and increase if you notice slow processing times.
 
-:::
+</Tip>
 
 #### 3. Verify TSS Configuration
 
@@ -195,7 +194,7 @@ If this value is higher than the actual number of channel accounts available, TS
 
 Issues with invitations, OTPs, and other messages sent to receivers.
 
-### Receiver Not Receiving the Invitation {/* #receiver-not-receiving-invitation */}
+### Receiver Not Receiving the Invitation {#receiver-not-receiving-invitation}
 
 When you trigger a disbursement targeting an unregistered receiver (via email, SMS, or WhatsApp), they should receive an invitation link to register. If they haven't received it, work through these checks.
 
@@ -209,7 +208,7 @@ SCHEDULER_RECEIVER_INVITATION_JOB_SECONDS=30
 
 **Check:** Is this set to a reasonable interval (10–60 seconds)? If it's set too high or missing, invitations may be significantly delayed.
 
-#### 2. Check SDP Logs for Submission Failures {/* #check-logs-submission-failures */}
+#### 2. Check SDP Logs for Submission Failures {#check-logs-submission-failures}
 
 The SDP logs will show whether the message was sent and if the messaging provider accepted or rejected it.
 
@@ -226,11 +225,11 @@ docker logs <sdp-container-name> 2>&1 | grep -iE "invitation|otp|message"
 | Twilio (SMS) | Geofencing, unverified numbers | Is the destination country enabled? Is your sender ID verified? |
 | Twilio (WhatsApp) | Template not approved, 24h window | Is your message template approved? Are you outside the 24h conversation window? |
 
-:::tip
+<Tip>
 
 If you're testing, check spam/junk folders first—especially for email invitations.
 
-:::
+</Tip>
 
 #### 3. Verify Receiver Contact Info
 
@@ -242,7 +241,7 @@ Double-check that the receiver's contact information (email, phone number) in th
 
 ---
 
-### Receiver Not Receiving OTP During Registration {/* #receiver-not-receiving-otp */}
+### Receiver Not Receiving OTP During Registration {#receiver-not-receiving-otp}
 
 During registration, receivers enter the contact details (phone number or email) that the payer used when submitting the disbursement. The SDP sends an OTP to verify ownership of that contact method.
 
@@ -272,7 +271,7 @@ If the contact info matches but the OTP still isn't arriving, the issue is likel
 
 ## Receiver Registration
 
-### Receiver Verification Locked Out {/* #receiver-verification-locked-out */}
+### Receiver Verification Locked Out {#receiver-verification-locked-out}
 
 During SEP-24 registration, receivers must confirm their verification value (e.g., date of birth or PIN) to prove their identity. If a receiver enters the wrong value too many times, the system locks them out and displays:
 
@@ -291,7 +290,7 @@ SELECT * FROM sdp_<tenant_name>.receiver_verifications
 WHERE attempts >= 15;
 ```
 
-#### 2. Confirm the Receiver's Identity
+#### 2. Confirm the Receiver's Identity {#2-confirm-the-receivers-identity}
 
 Cross-reference the receiver ID to make sure you're resetting the right account:
 
@@ -317,7 +316,7 @@ After resetting, the receiver can try again. You may need to walk them through t
 
 ## Channel Accounts
 
-### Recreating Channel Accounts {/* #recreating-channel-accounts */}
+### Recreating Channel Accounts {#recreating-channel-accounts}
 
 After a testnet reset, your channel accounts no longer exist on-chain but are still referenced in the database. You need to clean up invalid accounts and create new ones.
 
@@ -331,11 +330,11 @@ Run these commands inside the TSS container:
 ./stellar-disbursement-platform channel-accounts ensure 10
 ```
 
-:::tip
+<Tip>
 
 The `ensure` command is idempotent—it only creates accounts if you have fewer than the specified number. Running `ensure 10` when you already have 10 valid accounts does nothing.
 
-:::
+</Tip>
 
 ---
 
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/README.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/README.mdx
deleted file mode 100644
index 10e04c0d6..000000000
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: User Interface
-sidebar_position: 100
----
-
-import DocCardList from "@theme/DocCardList";
-
-A description and walkthrough of the various parts of the SDP user interface.
-
-<DocCardList />
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/account-picker.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/account-picker.mdx
index 2e7adc5b0..5a59803e5 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/account-picker.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/account-picker.mdx
@@ -1,11 +1,11 @@
 ---
 title: Account Picker
-sidebar_position: 65
+description: "The account picker sits at the top of every page and names the distribution account you are currently working in, along with its balance. Everything below it (disbursements, payments, receivers, and analytics) is scoped to the account you pick."
 ---
 
-The account picker sits at the top of every page and names the [distribution account](./distribution-accounts.mdx) you are currently working in, along with its balance. Everything below it (disbursements, payments, receivers, and analytics) is scoped to the account you pick.
+The account picker sits at the top of every page and names the [distribution account](./distribution-accounts) you are currently working in, along with its balance. Everything below it (disbursements, payments, receivers, and analytics) is scoped to the account you pick.
 
-The picker only becomes **interactable** when you have access to **more than one distribution account**. Multiple accounts are available only to organizations whose distribution account is held in the SDP's [database vault](../design-and-architecture.mdx#distribution-accounts). With only one accessible account, it stays a static label naming that account; organizations on a shared or Circle distribution account never get more than one.
+The picker only becomes **interactable** when you have access to **more than one distribution account**. Multiple accounts are available only to organizations whose distribution account is held in the SDP's [database vault](../design-and-architecture#distribution-accounts). With only one accessible account, it stays a static label naming that account; organizations on a shared or Circle distribution account never get more than one.
 
 ![Account Picker](/assets/SDP/SDP49.png)
 
@@ -27,4 +27,4 @@ Actions that have to be charged to a specific account, such as creating a disbur
 
 ## Adding, Sharing, and Archiving Accounts
 
-Adding an account, granting or revoking access to it, and archiving it are all done by Owners from the [dashboard home page](./dashboard-home.mdx#managing-distribution-accounts).
+Adding an account, granting or revoking access to it, and archiving it are all done by Owners from the [dashboard home page](./dashboard-home#managing-distribution-accounts).
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/analytics.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/analytics.mdx
index 8248d1588..31a4eade0 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/analytics.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/analytics.mdx
@@ -1,11 +1,11 @@
 ---
 title: Analytics
-sidebar_position: 60
+description: "The Analytics page provides comprehensive insights into various aspects of financial transactions, enabling the user to track and understand key..."
 ---
 
 The Analytics page provides comprehensive insights into various aspects of financial transactions, enabling the user to track and understand key payment-related metrics. As more metrics and statistics become available, additional tiles will be added to this screen. The page displays the successful payment rate and the number of successful, failed, canceled, and remaining payments. It also shows the total balance, the total disbursed, and the average payment amount, each broken down by asset, along with the number of recipients and recipient wallets involved in the transactions.
 
-These figures are scoped to the distribution account currently selected in the [account picker](./account-picker.mdx), or every account you have access to when **All accounts** is selected.
+These figures are scoped to the distribution account currently selected in the [account picker](./account-picker), or every account you have access to when **All accounts** is selected.
 
 In more detail:
 
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/circle-configuration.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/circle-configuration.mdx
index 6cbb94b1b..2907ae66c 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/circle-configuration.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/circle-configuration.mdx
@@ -1,6 +1,6 @@
 ---
 title: Circle Configuration
-sidebar_position: 70
+description: "If the tenant was created with a [Circle] distribution account, then the tenant owner will need to manually configure that account from within the SDP dashboard."
 ---
 
 If the tenant was created with a [Circle] distribution account, then the tenant owner will need to manually configure that account from within the SDP dashboard.
@@ -13,12 +13,12 @@ Clicking on the banner will take the user to the Distribution Accounts section,
 
 ![Circle Configuration](/assets/SDP/SDP31.png)
 
-:::info
+<Info>
 
 The API key will get stored in the database encrypted by the key `DISTRIBUTION_ACCOUNT_ENCRYPTION_PASSPHRASE`, while the Wallet ID is stored in plain text.
 
 The Wallet ID is used to identify the Circle (internal) account when making disbursements. It's useful because a Circle account can have multiple wallets, each one with different currencies and balances.
 
-:::
+</Info>
 
 [Circle]: https://www.circle.com
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/dashboard-home.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/dashboard-home.mdx
index 96d333c73..07b9d5ae9 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/dashboard-home.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/dashboard-home.mdx
@@ -1,9 +1,9 @@
 ---
 title: Dashboard Home
-sidebar_position: 10
+description: "The main page of the dashboard contains a summary of recent disbursement activity and key performance metrics."
 ---
 
-The main page of the dashboard contains a summary of recent disbursement activity and key performance metrics, scoped to the distribution account(s) currently selected in the [account picker](./account-picker.mdx).
+The main page of the dashboard contains a summary of recent disbursement activity and key performance metrics, scoped to the distribution account(s) currently selected in the [account picker](./account-picker).
 
 This includes:
 
@@ -54,13 +54,13 @@ Each entry shows:
 
 ## Managing Distribution Accounts
 
-The home page lists each [distribution account](./distribution-accounts.mdx) you have access to, with its live balance. Owners manage the organization's accounts from here.
+The home page lists each [distribution account](./distribution-accounts) you have access to, with its live balance. Owners manage the organization's accounts from here.
 
 ### Adding an Account
 
-Owners can add a distribution account using **Add account**. Give the account a name that identifies what it is for, since that name appears in the [account picker](./account-picker.mdx) and against every disbursement it funds.
+Owners can add a distribution account using **Add account**. Give the account a name that identifies what it is for, since that name appears in the [account picker](./account-picker) and against every disbursement it funds.
 
-The new account is created and funded automatically. It starts with no balance of your disbursement assets, so fund it before using it for payouts. Adding accounts is available to organizations whose distribution account is held in the SDP's database vault; see [Distribution Accounts](../design-and-architecture.mdx#distribution-accounts).
+The new account is created and funded automatically. It starts with no balance of your disbursement assets, so fund it before using it for payouts. Adding accounts is available to organizations whose distribution account is held in the SDP's database vault; see [Distribution Accounts](../design-and-architecture#distribution-accounts).
 
 ### Managing Access
 
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/disbursements.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/disbursements.mdx
index edf041587..c5898d9be 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/disbursements.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/disbursements.mdx
@@ -1,11 +1,11 @@
 ---
 title: Disbursements
-sidebar_position: 20
+description: "The Disbursements page provides a paginated list of all disbursements, detailing each disbursement's status and related payment information."
 ---
 
 The Disbursements page provides a paginated list of all disbursements, detailing each disbursement's status and related payment information.
 
-The list is scoped to the distribution account currently selected in the [account picker](./account-picker.mdx). You see the disbursements made from that account.
+The list is scoped to the distribution account currently selected in the [account picker](./account-picker). You see the disbursements made from that account.
 
 ![Disbursements](/assets/SDP/SDP20.png)
 
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/distribution-accounts.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/distribution-accounts.mdx
index 50d2ba444..b0e8f5888 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/distribution-accounts.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/distribution-accounts.mdx
@@ -1,11 +1,11 @@
 ---
 title: Distribution Accounts
-sidebar_position: 50
+description: "Distribution accounts are the Stellar accounts your organization sends funds from."
 ---
 
 Distribution accounts are the Stellar accounts your organization sends funds from. Your organization may have more than one, for example to keep separate programs or funding sources apart.
 
-The Distribution Accounts page shows the account you currently have selected in the [account picker](./account-picker.mdx).
+The Distribution Accounts page shows the account you currently have selected in the [account picker](./account-picker).
 
 ![Distribution Accounts](/assets/SDP/SDP23.png)
 
@@ -20,7 +20,7 @@ The page includes the following:
   - Add trustline: Trust any asset by entering its asset code and the issuer's public key. Asset codes are not unique on their own, so check the issuer carefully.
   - Add from preset assets: Pick from the assets your organization already has configured, without typing an issuer. Assets the account already trusts are shown as "Already added" and cannot be selected twice.
 - Account history: A record of payments to and from this account, taken directly from the Stellar network, with a link to view the account on Stellar Expert.
-- Bridge integration: Shown only to the Owner and Financial Controller roles, on the default account only, and when [bridge integration has been configured](../configuring-sdp.mdx#bridge-integration-configuration). It sets up a virtual USD bank account you can use to fund the distribution account by bank transfer; deposits are converted to USDC on Stellar and credited to the account automatically.
+- Bridge integration: Shown only to the Owner and Financial Controller roles, on the default account only, and when [bridge integration has been configured](../configuring-sdp#bridge-integration-configuration). It sets up a virtual USD bank account you can use to fund the distribution account by bank transfer; deposits are converted to USDC on Stellar and credited to the account automatically.
   - Get Started with Bridge: Opts your organization in and starts Bridge's KYC and terms of service checks. The panel then tracks the progress of those checks.
   - Create Virtual Account: Appears once both KYC and the terms of service are approved, and issues the virtual account.
   - Once the account exists, the panel shows its deposit details and the accepted payment methods instead of a button.
@@ -29,4 +29,4 @@ The page includes the following:
 
 Add funds to a distribution account: You can deposit Stellar-based digital assets into the account by sending them to the provided public key. Make sure the account has a trustline to the asset before you send funds. As a general principle, do not use a distribution account as a long-term holding place for money. It is meant to be a pass-through wallet to fund disbursements.
 
-Check the [account picker](./account-picker.mdx) before you send funds, so you copy the public key of the account you intend to fund.
+Check the [account picker](./account-picker) before you send funds, so you copy the public key of the account you intend to fund.
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/index.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/index.mdx
new file mode 100644
index 000000000..a905f4812
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/index.mdx
@@ -0,0 +1,47 @@
+---
+title: User Interface
+description: "A description and walkthrough of the various parts of the SDP user interface."
+---
+
+<CardGroup cols={2}>
+  <Card title="Dashboard Home" icon="file-lines" href="/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/dashboard-home">
+
+    The main page of the dashboard contains a summary of recent disbursement activity and key performance metrics.
+
+  </Card>
+  <Card title="Disbursements" icon="file-lines" href="/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/disbursements">
+
+    The Disbursements page provides a paginated list of all disbursements, detailing each disbursement's status and related payment information.
+
+  </Card>
+  <Card title="Receivers" icon="file-lines" href="/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/receivers">
+
+    The Receivers page displays a list of individuals set to receive payments, with wallet information and payment history.
+
+  </Card>
+  <Card title="Payments" icon="file-lines" href="/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/payments">
+
+    The Payments page provides a list of all payments, detailing each payment's status and related information.
+
+  </Card>
+  <Card title="Distribution Accounts" icon="file-lines" href="/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/distribution-accounts">
+
+    Distribution accounts are the Stellar accounts your organization sends funds from.
+
+  </Card>
+  <Card title="Analytics" icon="file-lines" href="/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/analytics">
+
+    The Analytics page provides comprehensive insights into various aspects of financial transactions, enabling the user to track and understand key...
+
+  </Card>
+  <Card title="Account Picker" icon="file-lines" href="/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/account-picker">
+
+    The account picker sits at the top of every page and names the distribution account you are currently working in, along with its balance.
+
+  </Card>
+  <Card title="Circle Configuration" icon="file-lines" href="/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/circle-configuration">
+
+    If the tenant was created with a Circle distribution account, then the tenant owner will need to manually configure that account from within the SDP dashboard.
+
+  </Card>
+</CardGroup>
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/payments.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/payments.mdx
index 40bde32bf..76b8a2df5 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/payments.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/payments.mdx
@@ -1,13 +1,13 @@
 ---
 title: Payments
-sidebar_position: 40
+description: "The Payments page provides a list of all payments, detailing each payment's status and related information."
 ---
 
 The Payments page provides a list of all payments, detailing each payment's status and related information.
 
 Direct payments are also created from this page: one-off payments sent to a receiver without going through a disbursement.
 
-The list is scoped to the distribution account currently selected in the [account picker](./account-picker.mdx). You see the payments sent from that account.
+The list is scoped to the distribution account currently selected in the [account picker](./account-picker). You see the payments sent from that account.
 
 ![Payments](/assets/SDP/SDP22.png)
 
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/receivers.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/receivers.mdx
index e83fc2471..a3acd9876 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/receivers.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/receivers.mdx
@@ -1,11 +1,11 @@
 ---
 title: Receivers
-sidebar_position: 30
+description: "The Receivers page displays a list of individuals set to receive payments, with wallet information and payment history."
 ---
 
 The Receivers page displays a list of individuals set to receive payments, with wallet information and payment history. This information allows you to track and manage the payments made to each receiver, and provides a snapshot of each receiver's interaction with a disbursement.
 
-The list is scoped to the distribution account currently selected in the [account picker](./account-picker.mdx). A receiver appears there if they have been disbursed to from that account, or were created from it.
+The list is scoped to the distribution account currently selected in the [account picker](./account-picker). A receiver appears there if they have been disbursed to from that account, or were created from it.
 
 ![Receivers](/assets/SDP/SDP20x.png)
 
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/_category_.json b/docs/platforms/stellar-disbursement-platform/api-reference/_category_.json
deleted file mode 100644
index 0d4475828..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": false
-}
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/admin.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/admin.mdx
new file mode 100644
index 000000000..a8440d2b9
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/admin.mdx
@@ -0,0 +1,5 @@
+---
+title: Admin (Tenant Management)
+---
+
+The Admin API oversees the management of tenants within the system, facilitating tasks such as provisioning new tenants, updating their information, and retrieving tenant data.
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/admin.tag.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/admin.tag.mdx
deleted file mode 100644
index ac04e35d2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/admin.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: admin
-title: "Admin (Tenant Management)"
-description: "Admin (Tenant Management)"
-custom_edit_url: null
----
-
-
-
-The Admin API oversees the management of tenants within the system, facilitating tasks such as provisioning new tenants, updating their information, and retrieving tenant data.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/api-keys.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/api-keys.mdx
new file mode 100644
index 000000000..4f269c2b4
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/api-keys.mdx
@@ -0,0 +1,5 @@
+---
+title: API Keys
+---
+
+API Keys functionality allows to create access key with granular permissions and resource management.
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/api-keys.tag.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/api-keys.tag.mdx
deleted file mode 100644
index 71bb54e4f..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/api-keys.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: api-keys
-title: "API Keys"
-description: "API Keys"
-custom_edit_url: null
----
-
-
-
-API Keys functionality allows to create access key with granular permissions and resource management.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/archive-distribution-wallet.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/archive-distribution-wallet.ParamsDetails.json
deleted file mode 100644
index 9bf3d3e70..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/archive-distribution-wallet.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"The unique identifier of the distribution account","required":true,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/archive-distribution-wallet.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/archive-distribution-wallet.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/archive-distribution-wallet.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/archive-distribution-wallet.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/archive-distribution-wallet.StatusCodes.json
deleted file mode 100644
index a64acb27e..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/archive-distribution-wallet.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Distribution account archived successfully","content":{"application/json":{"schema":{"type":"object","description":"A distribution account the tenant sends funds from.","properties":{"id":{"type":"string","description":"Unique identifier for the account"},"name":{"type":"string","description":"Human-readable name for the account"},"description":{"type":"string","description":"Optional description"},"distribution_account_address":{"type":"string","description":"The account's Stellar address. Absent until the account has been provisioned on the network."},"distribution_account_type":{"type":"string","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"],"description":"How the account's secret is stored. Additional accounts are always `DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT`."},"distribution_account_status":{"type":"string","enum":["ACTIVE","PENDING_USER_ACTIVATION"],"description":"Status of the underlying Stellar account"},"status":{"type":"string","enum":["ACTIVE","PENDING","ARCHIVED"],"description":"Lifecycle status. `PENDING` accounts have been reserved but not yet funded on the network and cannot send. `ARCHIVED` accounts accept no new disbursements and are never deleted.\n"},"is_default":{"type":"boolean","description":"Whether this is the tenant's default account. Exactly one account is the default, and it cannot be archived."},"created_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"archived_at":{"type":"string","format":"date-time","description":"When the account was archived, if it has been"}},"title":"DistributionWallet"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/archive-distribution-wallet.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/archive-distribution-wallet.api.mdx
deleted file mode 100644
index 64e134768..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/archive-distribution-wallet.api.mdx
+++ /dev/null
@@ -1,75 +0,0 @@
----
-id: archive-distribution-wallet
-title: "Archive Distribution Account"
-description: "Archives a distribution account. Owner only."
-sidebar_label: "Archive Distribution Account"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWFtv2zoS/isDvrQBZNnNZncBv7mJz9Z7giQbO+1DGjiUNI54QpEqL3a9hv77wVCS7cTOracHOFhsHmxHnMs3M9TMR66Y43eW9a/ZibDOiMQ7oRV84VKis+wmYhna1IiSHrM+G5g0F3O0wCHbVuBpqr1yMZwvFBrQSi7jr+qrauSzVsDSDywdKA0KF2Qk8cZigbSWeAf3iCVYNHOh7sAgz2wEVkPJrQODqTaZBev4EgxaLec8kRjDZKE3HlKulHaQIPC1d5WBQeeNgqNerw8uR3CouHLvLGQ44166CBa5SHMw+M0LgxZKowvtCAZX2uVoWhcwE8a6KFglS7LGVnChgnTqxBzXKfmqWMR0iYZTpkbZJovbKa8zziJWcsMLdGioKiumeIGsz0TGIiaoAiV3OXtclkmO4JX45hFEhsqJmaAqzAK8fYViEWvizFjfGY8Rs2mOBWf9FXPLknySlrpjVXVDwrbUyqKl9cNej74eQjjZ42VTAOvTFK2deSmXLGKpVg6VIyu8LKVIQ266v1kytdqFopPfMHU7YQ/2xrZVXbCoMgszHz6NLmLKsKFqOFEHI7LdkB/7udpJ7Uyb4KZNZxU1lXrJ1CdfcNWhfU07F0hpn7EHSi/ZPA8/uITtx2RkKznTxviUZ5lBa1+2Otkgemdh7FBKbqBRj2GQWFQOvHJCbqOHnFtIEBW9P3NhhVaYgVZBRqFbaHMfP4muhrQLDZUvQpcajSeXo49Xk9H52XRwfHx+dTaJx5Ph6engMh6efWbR8yInH6efB1enk6fkjkeXx6fDjdhOA/ykF9vRvrNgMTXoQFBb0gazGAZZJpqKbNqeQeBywZcWbl+F8PbpJFnHnd9bwTZNg+PJ6POQRexieHYyOvvX9Go8vJyGpwPyuhvXONhsW4ZXGRq5pG62Lvxmc77dP4vY4PL40+jz8GTX9amYYbpMJUJtOIbbRu12k7+cz7HeVgZpOmAWpgU1+iW68IbvbLPQoJtpQI0ghtsWxe3rBhIZoMopnKOBDCU6zKijVxETdtpMjq1MJFpL5GrnZfqSY5ggLheWtsq+AbQZosPvPHVyCVptXqtGaT2sCJpwe4Zd2DepQe4wm3K3r0wzbQpaYRl32HGiQNLxZfZmndbp65X2ZEY96B8LbtexRCBmFGXbU1hVRcwJJ/HRxGnGZ1WRwNG++fSRZ3CJ3zxa90cG0MPhgcZo83IrPUHHhbTAE+3r8VQrVhHD785w+6Knqv6j2D7sxnaluHe5NuK/mP3pwb0e9G6jUL5IMMRdoLX8bk+vb+LE77woJW7hYGfawYM4NzBaR0e9D1umH2usU/i33RT+ok0isgzVn5+/J8LbIGhhHu3CpIh+0V79j5d51oS4r8JH2xW+RKu9STEMglqrfVMspt4Itww0+iNyg2bgXc761zfEaAt0uSYyXmpb825aY93tidtZ1Oeg7kpkVbdpSoxMm3lL0L2RrM8YmWw9jinzdWq2/a5TwEvxKy532WyzU0MZIUeeoQEqcnuuUDA+uYB/f5nA++H48O//OABtmqdTGFyM4B6XRHCbM8MDe+3xoTZLpRkPLz70fhIyGA8vOh96NbY6Zlg5fY+qOngTosOjn4no8OhnIPqPR7N8HawgCusj3FOItgAESK3jb6QeZpxQMx3cNbOuZWEnW/QELiR3NGGp9ixitCVrGP+Me3GP9qkvCm6WDZl/3sb78cnFAbEMDk5rCYkX0oWjiTZ3XDUpsuA0FPweIfHyHkq+rImS08DhzmhfEoU0mIpShAU9x/pw03pfHwH2nTf+WhDpAmPSEDauQJeoOk27KY2mVggu54Ga1VCIfuqyJdGPzG3uC1KdIRE3Ym2hZ7W8daal1Iv64qPUVjhtBNo+4ejAta3tdZvvzjZV7ZRNkjoJT+9RZTfvc+dK2+9274TLfRKnuui+ycJBH0LwayjLdjvXTLQRq4momhlunfGp86YJsD3VPlvT+A2RzUwYeH8ktNbES7EtMIFW9oejyVEWnTTnxtlnIW/JdZ1B7NJFUrd58Gw8L4XxCWUBwVDAn2EpdTjUvRgJeEtyv/oEjUKHtr7GcmgKez4b0/VcSn2pDauBGWtz1w1CHT3r2EYsYlKkqGwY823jLXmaIxyGPlXPULLV73YXi0XMw2qw1qja7unoeHg2HnYO416cu0KGPknDu+Bq23A9peHBfdRgfev16GJlzaH+f7P5gzebzUB0+N11S8lFOBuHgq4aTnXN9nEqFrF+uNVsadVNxHKiYv1rtlol3OKVkVVFj+ux2L++idicG0GJCdQrE5Z+Z6w/49LiM8V9f9lcdh7Aj1yV7o2xZQKKaMCcS0//sYjd47K+sK1uqqjlEgS3XhiEXbKlssPdH7DTi/MxXVbxHfpxH+hH84PM78XzmN/UGOizip5QWa1qclNVa/l66UmNJsZ16BRCVVW/A9vAkb4=
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Archive Distribution Account"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/distribution-wallets/{id}/archive"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Archives a distribution account. Owner only.
-
-Archived accounts accept no new disbursements but keep serving reads, so past records stay resolvable. Two accounts cannot be archived and return 400: the tenant's default, which requires promoting another account first, and the last remaining active account.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./archive-distribution-wallet.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./archive-distribution-wallet.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./archive-distribution-wallet.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/archive-distribution-wallet.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/archive-distribution-wallet.mdx
new file mode 100644
index 000000000..90104f845
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/archive-distribution-wallet.mdx
@@ -0,0 +1,5 @@
+---
+title: Archive Distribution Account
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml POST /distribution-wallets/{id}/archive"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/authenticate-mfa.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/authenticate-mfa.ParamsDetails.json
deleted file mode 100644
index c301cc557..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/authenticate-mfa.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"Device-ID","in":"header","description":"Identifier of the device","required":false,"style":"simple","explode":false,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/authenticate-mfa.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/authenticate-mfa.RequestSchema.json
deleted file mode 100644
index aae3eb586..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/authenticate-mfa.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"description":"MFA request data","content":{"*/*":{"schema":{"required":["mfa_code"],"type":"object","properties":{"mfa_code":{"type":"string","description":"Multi-factor authentication code"},"remember_me":{"type":"boolean","description":"Boolean flag to remember the user"},"recaptcha_token":{"type":"string","description":"Token for reCAPTCHA validation. ReCAPTCHA token is required unless the `DISABLE_RECAPTCHA` configuration is set to true."}}}}},"required":true}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/authenticate-mfa.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/authenticate-mfa.StatusCodes.json
deleted file mode 100644
index b0b401d23..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/authenticate-mfa.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Successful authentication","content":{"application/json":{"schema":{"type":"object","properties":{"token":{"type":"string","description":"Authentication token"}}}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/authenticate-mfa.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/authenticate-mfa.api.mdx
deleted file mode 100644
index 4aefda820..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/authenticate-mfa.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: authenticate-mfa
-title: "Provide Multi-Factor Authentication"
-description: "Governs the multi-factor authentication process for SDP user login, including the ability to remember the device so MFA is not always required."
-sidebar_label: "Provide Multi-Factor Authentication"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNV1tv2zYU/isEn5pCspyg2wC9OZeuWdvVq1PsIQ3SI+nIYkORKknF8Qz99+GQUmwnqdNuKVC/2CYPP37nwnNZcQdzy9NzPmldhcqJHJzQil9EvECbG9H4vyn/XV+jUZa5ClndSifiEnKnDYOtg6wxOkdrWakNmx1PWWvRMKnnQkVMqFy2hVBzjwKZkMItmdPMYI11hsavF3gtcmRWs7cvJ0xYprRjIBewtMzgl1YYLEY84rpB4+88LXjKN2jg25cTHvEGDNTo0JB+K66gRp7yY48enx7ziAtSrEIo0PC7+p4WhFYKNEyXG7x4xAcSPC1BWoy4dUtJ2FbUjSQJvGmkLnAtkFdYA09X3C0bL+mMUHPedRcBDq071MWSJLZpkAl6AVaAAx7xXCuHypHs8+Q5fa3h19TOeV3CZU4sLqLhWp19xtyRbQxZzwm0dOpW8h7Bu1Z5u8PzHqEjfYIzL+tNwExriaDuIR6GdVZKmN8LBQqeAJlD4/IKLp2+QvU4zzMS8zFo8GgyPTt6NWHXIEXhqY7Y+9tVD0hRNpiOtUpSANP9n45PZ5PDNyeX7096+U8s16oU8zaEHh206Ii4My2OeEefzRChZb9gG61ssPfBeHzf07M2p4dTtvKOYbddDk0j+43ks9Vq2/+7/fyNxttOBcFCQbEu4i8e4n4IBXsfovTp2KIx2jzO9hgdCGkZZLp13mvhYEfP0Bmwj97UrXXbv6/bB0Xu0Eb8g8UPV+7bSXPrwLWbcqqld0MQNVoL8weec1ATb8DnqTUN/iel2E011yyGe16M9zeQ7574kcAe+yam/DJHFffpMM50sYz7rE6/AzgqK7QKKf8KlzzdeTLi1yDbWwRKxzW6SlNFabSP5gZcxVOe1CUlX4vmeqgorZE85f6Qxbw1wi1n5P7gn0MEg4be0oYfoBGvcfngiyN9w4MLFYkSjQOhqFyC8rX0j7/P2LOT2cEvv+4xyr9+9ZJNpqfsCpdUE3tzbOHdKXRdxGcn0/3xEzFjs5NpvD8O3ILObOVTRrf3XYwOXjwlo4MXT8HorxbN8ttoeVF223N8jdEGgZBX+4u/0HFOgS5Uqf11wvmmYuZQSjDsWNisNRZrVI5NJbhSm5p8T0GMxgYav43GozHFaVvXYCj8zypkuzGezY6ne1TJgDmtJctaIZ0vntrMQfUmslTkarhClrXyijWwJBS/CmxudNtQo2QwF43wG9Qw+nw83K7QLbS5Gt2v1j8dxY/qozqrhPVXKqYbVLHVrcmRGlzKx8xV4Gg7UPF1shlaxTtwEQNV+A3KRCwHxTJkpW5V4Q9W9EdKvaBoMdhoK5w2Am1KPGJ2bgNe0n/HxYaR4qY3UpxBfoWquHhWOdfYNEnmwlVtNsp1nXwXwl7KvPK3VJZDOIe2qBfzWglVGrDOtLlrTa8g+cU95tPRd2hWGl91/49qA8Rjui0wY4Psf9amQlnHeQXG2Z2UN+QSZxCTGoRK+oWd+jymxiuUNfNAnn+BjdTLYfLa/dZaS3Kv2wyNQod29JGylENT23flDI2fglI+qNXTHGkzT7xQrMvY9mIRlyJHZX1PMCTeBvIK2YHPU6GGElaaJIvFYgR+16P1R23y5vTo5M/ZSXwwGo8qV0ufJ6k816A2gKdGX4sCWRhSXoYhZXK3l95KPat1P/cTTrh9xXF445JGglBUmLzFVn1b4qc8GvAqalbSc75aZWDxg5FdR8uhrKTnF9ToGAEZlZTziy4aKh31MYWwtLGeZ79qoh1D8YNcQwO2OXIP7RbvoqE/Owrw8RkhrCVotl0LTfIcG7exfa/53urdpu9mZzwKTR0NuH645QYWNL7DwhPoun8B3AX5Yg==
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Provide Multi-Factor Authentication"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/mfa"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Governs the multi-factor authentication process for SDP user login, including the ability to remember the device so MFA is not always required.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./authenticate-mfa.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./authenticate-mfa.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./authenticate-mfa.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/authenticate-mfa.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/authenticate-mfa.mdx
new file mode 100644
index 000000000..cf77fdc66
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/authenticate-mfa.mdx
@@ -0,0 +1,5 @@
+---
+title: Provide Multi-Factor Authentication
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml POST /mfa"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/authentication.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/authentication.mdx
new file mode 100644
index 000000000..1a897ee93
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/authentication.mdx
@@ -0,0 +1,5 @@
+---
+title: Authentication
+---
+
+Authentication controls the log in/log out process for all SDP users, as well as the token refresh process. Authentication uses a JWT approach signed with an ES256 private key.
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/authentication.tag.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/authentication.tag.mdx
deleted file mode 100644
index a7c1b1271..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/authentication.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: authentication
-title: "Authentication"
-description: "Authentication"
-custom_edit_url: null
----
-
-
-
-Authentication controls the log in/log out process for all SDP users, as well as the token refresh process. Authentication uses a JWT approach signed with an ES256 private key.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/balances.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/balances.mdx
new file mode 100644
index 000000000..71639547e
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/balances.mdx
@@ -0,0 +1,5 @@
+---
+title: Balances
+---
+
+Endpoints related to balances. A balance is an amount of a particular asset held by an organization, tenant, or account.
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/balances.tag.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/balances.tag.mdx
deleted file mode 100644
index 77993d11d..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/balances.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: balances
-title: "Balances"
-description: "Balances"
-custom_edit_url: null
----
-
-
-
-Endpoints related to balances. A balance is an amount of a particular asset held by an organization, tenant, or account.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/bridge-integration.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/bridge-integration.mdx
new file mode 100644
index 000000000..95e06b29c
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/bridge-integration.mdx
@@ -0,0 +1,20 @@
+---
+title: Bridge Integration
+---
+
+Bridge integration endpoints for connecting organizations with Bridge services.
+
+**Integration Flow:**
+
+1. Organization opts into Bridge (OPTED_IN status)
+2. Complete KYC verification process via Bridge
+3. Create virtual account for USD deposits (READY_FOR_DEPOSIT status)
+4. Receive USD deposits that are automatically converted to USDC on Stellar
+
+**Status Description:**
+
+- NOT_ENABLED → Bridge service not configured
+- NOT_OPTED_IN → Organization hasn't opted in
+- OPTED_IN → Organization opted in, KYC link created
+- READY_FOR_DEPOSIT → Virtual account created, ready for deposits
+- ERROR → Integration error occurred
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/bridge-integration.tag.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/bridge-integration.tag.mdx
deleted file mode 100644
index 458e0ab90..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/bridge-integration.tag.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-id: bridge-integration
-title: "Bridge Integration"
-description: "Bridge Integration"
-custom_edit_url: null
----
-
-
-
-Bridge integration endpoints for connecting organizations with Bridge services.
-
-**Integration Flow:**
-1. Organization opts into Bridge (OPTED_IN status)
-2. Complete KYC verification process via Bridge
-3. Create virtual account for USD deposits (READY_FOR_DEPOSIT status)
-4. Receive USD deposits that are automatically converted to USDC on Stellar
-
-**Status Description:**
-- NOT_ENABLED → Bridge service not configured
-- NOT_OPTED_IN → Organization hasn't opted in
-- OPTED_IN → Organization opted in, KYC link created
-- READY_FOR_DEPOSIT → Virtual account created, ready for deposits
-- ERROR → Integration error occurred
-
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-api-key.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/create-api-key.RequestSchema.json
deleted file mode 100644
index e37f84500..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-api-key.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"application/json":{"schema":{"type":"object","required":["name","permissions"],"properties":{"name":{"type":"string","description":"Human-readable name for the API key"},"permissions":{"type":"array","description":"List of permissions granted to this API key","items":{"type":"string","enum":["read:all","write:all","read:disbursements","write:disbursements","read:receivers","write:receivers","read:payments","write:payments","read:organization","write:organization","read:users","write:users","read:wallets","write:wallets","read:distribution_wallets","write:distribution_wallets","read:statistics","read:exports"]},"minItems":1},"distribution_wallet_ids":{"type":"array","items":{"type":"string"},"description":"IDs of the distribution accounts this key may act on. Omit the field to inherit the accounts its creator can reach at that moment. An empty array grants no account access. A key cannot be scoped to an account its creator cannot reach.\n"},"expiry_date":{"type":"string","format":"date-time","description":"Optional expiration date for the API key (must be in the future)"},"allowed_ips":{"oneOf":[{"type":"string","description":"Single IP address or CIDR range"},{"type":"array","items":{"type":"string"},"description":"Array of IP addresses or CIDR ranges"}],"description":"IP restrictions for the API key. If not provided, the key can be used from any IP"}},"title":"CreateAPIKeyRequest"}}},"required":true}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-api-key.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/create-api-key.StatusCodes.json
deleted file mode 100644
index 2a44364db..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-api-key.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"201":{"description":"API key created successfully","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","description":"Unique identifier for the API key"},"name":{"type":"string","description":"Human-readable name for the API key"},"key":{"type":"string","description":"The actual API key (only returned once at creation)"},"permissions":{"type":"array","items":{"type":"string"},"description":"List of permissions granted to this API key"},"allowed_ips":{"type":"array","items":{"type":"string"},"description":"List of allowed IP addresses or CIDR ranges"},"distribution_wallet_ids":{"type":"array","items":{"type":"string"},"description":"IDs of the distribution accounts this API key may act on.","title":"DistributionWalletIDs"},"expiry_date":{"type":"string","format":"date-time","description":"Expiration date of the API key"},"created_at":{"type":"string","format":"date-time","description":"When the API key was created"},"created_by":{"type":"string","description":"User who created the API key"},"updated_at":{"type":"string","format":"date-time","description":"When the API key was last updated"},"updated_by":{"type":"string","description":"User who last updated the API key"},"last_used_at":{"type":"string","format":"date-time","description":"When the API key was last used"}},"title":"CreateAPIKeyResponse"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-api-key.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/create-api-key.api.mdx
deleted file mode 100644
index 7c39008aa..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-api-key.api.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-id: create-api-key
-title: "Create API Key"
-description: "Creates a new API Key to access SDP endpoints. API Key can be configured to have a granular read/write access, also API key can be restricted to the specific IP or range of the IPs."
-sidebar_label: "Create API Key"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVWW1vGzkO/iuCPjXA+CW+dHvnb2mTw3q72PjqFAUuDQJ6hra1mZGmlBTXa8x/P1CasSeTt6ab4nbzxbZEPnpIkRSlbKWDpZXjC3k8nYj3uLHyMpEZ2pRU6ZTRcizfEYJDK0BoXItaTjgjIE3RWjE7mQrUWWmUdra/E0hBizmK1OiFWnrCjFVWcIMCxJJA+xxIEEI2WJNyWKMlAnJrAsj1HoTQOlKpiyBuhcKWmKqFSsVkKgwJAr1EYRZhbjK1fZlIUyIB2zDJdlYcTyfvcSMTSfjFo3VvTbaR461MjXaoHX+FssxVGhQHv1v2wFbadIUF8De3KVGOpZn/jqmrcRRhxi7UUKBMZIlUKGuV0cGZJTERp9CyfpDZ47BZeim7Lv/ZF6B77ByY5yhYSSwMBetq18jq9kp7TCCCzR3IX5V17KCWTtiGnU+V3UEnUjks7H08UfuCbWVuY8hzmciwffX3MJwpO/dksUDt7E6gOxpECVNUN0h7sfZIEClhcxuoNRAEDC1Bqz/Cju2EOoNB0Nv2Qs2vMLWGPMfWGvvfjUWO1Nwz2lVX9oHJoGgdOGWdSncj+LU05Ky8rBJZKD2Jjj6sEnkPzpXK7tvZB3an6u755MQ2OdEG51QzXjsbd53zrICNgNQJo/virFAu6CwU5iE4lF4h1YM7XeWsSDmpDIU0JYR0JYClwInC8B71xbEWWJRuIwL3GHFWaNPg1GnfF8dNvmvjOOVtasoYmrAj3F2TRcOy/c+arcevpaLNVQbu3hxbGCrAybFkgZ5TIVtve+wsfIFcBKgQPYKlu9knXhXeBp5KR1955wkPmAXkuVljdqXKsEdG49lCji+eyvmZ0suci5eALCMurIbEu8nJh1jcZJV8dxwcB9+bRQscO/BWVncK/2S6K7yhXHR80BeTheAtKMncqAyzJMy2yra3mIkFmUKA3ojJVFZVIp1yOXYK8odYjWXFAvuS6shjGLCl0TYW0NHwkD86BjbHRcDMhPUhqhY+z9lP313db9dulT1duT9q9cWjUBlqpxYK6b66/aKHAH88iXUeMtd5yPcRbHS+EYTOk8ZMGJ0iZ29woTL64OkD5lvD7zlHz938+ZOL1miPh/7/r/g2u9EqwHKfIyctxU+B1OTEvkylO+0UuJpqax/qZLoC951LfFqhvlU012CbFG0vMP+GAP5okcR6ZXYp3iHry+wHkM3BOlFDt1d5FuM2SJc2z11xmfwhxC2zfrDkxqLKNbdK5NFweLesvoVMNKX5xaooEhl62n0n6EDlVsDc+Nh5RMUQ/I7APrlSFf/YtnuOjI8avFsZUn9g9sON+3bSkjtG35bTvphjsLtAa2F5T8LXduJXKMocWzzkb8aJW3buaTQLHQ0PW9BdjZ0L/3HXhf82NFdZhvrH++8B8/YMap4WU0/KbUK/9RaBkI69W8nxxSX3NwW6leHbYGlCSJfAc3IApepd8+WXESjcPhjAUy7HMnRGDfCMDYlc2/D7U6JU8YLZaVBqj8aCu0LIkPhq7EBppZfc4/I1+pdP5+LV6Wz0+qcDPqPi6NWu4ZJN63Abjw8lXiTCcqTMTqeHwxdiJman097hMHKLNoutM9eoq4NnMRodvSSj0dFLMPqPR9p8G60gKkogKNA9zKhFIFBqFv7C6qEac0582D8/nO7DutbbVcRb7Vfrzn35SL9y0ahfdroEORqOjnrDN73Rv84PX49fH45H/+wP3xz+V3ZarlbRUnphgmfqA2TmMOdnm5PWXV5Mc3B8TnGYykRy9kSPvekP+0NOKV8UQJu6DX0c49XsZHogFL82OWNyMfcqd6Htbd/oLfeNBVyjmPv8WjQvAuG2KJZkfMn9DGGqShUmzA3GxrlZXaNbG7ru39sp/7Uoftaf9Tn3irykFqZE3bPGU4p88+IyGq/cytZUjBbOlE1H14FLBOjYhqQmw+amtjBeZ0GR77KGw4EDm7A0VjlDCu2YefTEhY14g/qz137X6ZW1k3pzSK9RZ5evVs6VdjwYLJVb+Xk/NcXgWQgHYxGM31HZNJlnA9laLFil9ILAOvIpX8ajgc2N6dE97T/DsgWFo+7PmNZAPGXbGueikf1ua1aYF710BeTso5RbcgNHiIMClB7UA4/a85QZP2NeiAAU+GdY5mbD4fWkJcJblnvv50gaHVp+6EmkQyrs2WKGdKNSrkuNWTXNvqHlIAj1zKJna7FE5ipFbnn3pfa4hHSFYhTqVDzuGWs8GKzX6z6E2YBWq9rBr5N3p7/NTnuj/rC/ckUeSjq3EwXoFnBstZvH8G6VaT04/22f1+vT0uFXNyhzUOEFLrhwW/dVF3LXV10mcsUt1/hCbrdzsPiR8qri4Xguji8uE3kDpPipI3RrSXNUcyMW3jjku+iz3jmvzOK5j+d1p9/kl7KocZymWLpHZdtd4fRsdi4TOa//KVCYjHUI1vx4C2vuBfnfCq55DwljW5mDXvrYPUdMDgm401TEl/X6S+s9EPSmxbDbtURD4nXxAZXtNrYsVbWTj1MPatSubaR57y6rqvof8cIZ0w==
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create API Key"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/api-keys"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Creates a new API Key to access SDP endpoints. API Key can be configured to have a granular read/write access, also API key can be restricted to the specific IP or range of the IPs.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./create-api-key.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./create-api-key.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-api-key.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/create-api-key.mdx
new file mode 100644
index 000000000..d9d5c79e1
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/create-api-key.mdx
@@ -0,0 +1,5 @@
+---
+title: Create API Key
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml POST /api-keys"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-asset.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/create-asset.ParamsDetails.json
deleted file mode 100644
index 757a2f198..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-asset.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"X-Wallet-Id","in":"header","required":false,"description":"Optional. Selects the distribution account whose trustlines are affected. Omit it to act on the tenant's default account. An API key does not get that fallback: a key scoped to exactly one account may omit the header, any other key must send it.\n","schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-asset.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/create-asset.RequestSchema.json
deleted file mode 100644
index 945c3f4c0..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-asset.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"description":"Asset to be created","content":{"application/json":{"schema":{"required":["code","issuer"],"type":"object","properties":{"code":{"type":"string","description":"The asset code","example":"USDC"},"issuer":{"type":"string","description":"The issuer","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"}}}}},"required":true}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-asset.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/create-asset.StatusCodes.json
deleted file mode 100644
index 587d96eb4..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-asset.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"201":{"description":"Asset created successfully","content":{}},"400":{"description":"Bad request, invalid request body or the provided code/issuer is invalid.","content":{}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-asset.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/create-asset.api.mdx
deleted file mode 100644
index a56f66172..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-asset.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: create-asset
-title: "Create Asset"
-description: "This endpoint is used to create a new asset that can be used in a Disbursement. Note: the organization must hold a balance in a particular asset to use it in a disbursement."
-sidebar_label: "Create Asset"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlWFtz27YS/is7eDnJjCgpjlrP8E2+nfrEx1YiJ27reDoguRJRgwADgFZYDf97ZwFSomPZadp0phc/2DS5u9hvd7H7AWvm+NKy+JpdmCVX4hfuhFbsZsAytKkRpf83Zpe5sIAqK7VQDoSFymIGTkNqkDsEDgpXwK1FBy7nDlKuIMEgJhRwOBI2qYzFApUbwrl2GIPLEXRvXSgq6yDXMgMOCZdcpRi0S26cSCvJTbeIJtsgXPie9a2zAdMlGm/yNGMxO/ROTkmRDVjJDS/QoSHca6Z4gSxm30dXXEp00WnGBkwQ6Bx5hoYNmMEPlTCYsXjBpcVPg3PhH7gcwhwlps56YJmwzoik8sB4mupKOVjl2iI4U1knhUIL3CDwxQJTh9kQLgoC5NHx1IFW3pJDxZX7j4UMF7ySrrM2hKmC6ewUbrGGTKMFpR0suxQsuJQJT29j4F7CproMScOPPHWyBq1w41nBa9C0PK0YkA+Aqxq0y9F4Az47FlUGwg3fKzZgNs2x4CxeM1eXFEWCrJasaW5C1NC6A53VJHE/ZtMuiwm2NURhT7VyqByJ87KUIvU5HP1sSWfdW26bkWuW6gwpZdZWaKh0W1908jOmPuGGysEJtKTqxR94/LDgsa201jx+5EUpSePt/OiQNZsFf5OpVrZv5r8HB0eT/dOTb8+uXu3P9v9/dPxufnj1Zv9o9vbq3cvzH14eXb4+fndyNjmfXk6mr797+ePZ2cnZ9BvW0E+/KJ2p0L+wpVY2oNwbv3gs6G24wVZpitYuKinre7En65Px+KH+Ac+gzeoAhLrjUmxeQKKzGrTx9VMafScyzHzwRgE8dY1WZ7hjuR3uvlW8crk24pcvK46n84/G6B1Zayg3znD7eQvWcVf15VRVJGjIRIHW8uWO+mqTtkn/xg92rh3cw7l1o1toMn7RM/2pRmt6Mn75MIQn2iQiy1D9+fF7BN7Wg87NyUM3CdGJrtQ/PM2LFuKuDE/6GX6DVlcmRd/Qg1bTmraYVka42s+uA+QGzbRyOYuvb6jpfoxoyy1RRe2+jGhfRu2Qo+ewPiortAoT8BZrFj+pOWB3XFYbC7RQgS7XNFxLbcNUJSfYyDdNS7MBzV03YysjWcy8Xuf/nPIYAt1HsQkoL8UrrB8002lb94EvhDkFVDJcKKGWwBXMj2bwv6tLeHY83/vm2+fUk8Lbn7phSf2njcg9e58M/mbA5sezF+Ov5BnMj2fRi3HwLWCGtdO3qJrnX+TR3uRrerQ3+Roeva7Q1L/NLS8KGxb2mEc9B7xL3cIfSJ3RVqCW8GZLMo63my7M+DCpt4P6D4xcWnuhPTbh/PieO5RER/u8FmaSu4U2BRUabRo0NmDeH46HY9oUVVFwU7es4Gkbz+ZHs+c0NTk4rSUklZDUDcw9zmyJRBX8FiGp5C2UvCYr/i2HpdFVCXoBBlNRCv9B32EY0t3qCt1Km9vhTuLy13LxvXqv/FGEllSgS1RR2ylLo6mLB+orbOsKMWjtze8wR/w28x+oXroji2+3HfVeaCn1ikrTYKmtcNoItDH5EcG1DfZG7d+ofwqJyjZIEXFwVNnNs9y50saj0VK4vEqGqS5GX2TheQwe/MaVuts74cTRinlUQi0Mt85UqatMC3Ch70d1Z06HX4BsYfys/iPQOhOfw7bCBDrZ340mR1lEac6Ns0+63JMbOYM4KrhQo/bFk3g+B+M7lAV4Q97/DEupayqvzyKBypLcqypBo9ChDScwh6awF4s5mjuRUl/qYLVuDrVZjrxQpBeRbcUGTIoUlfXNsuvyJU9zhD3fp8LAJlvxaLRarYbcf/XWWlU7Ojs9PD6fH0d7w/Ewd4X0TZnoQMFVz3A4fUN3/L7XY9Zbuve3u2Nop5zDj25USi4UjQkfuHXLhq5Zy4ZuBiwnmhRfs/U64RbfGtk09DpMs/j6hiiWETyh4XJ90wy6AUv0KROWPjxy/9CP4b/3KmJnNgKzvX+10zFZ1gw66nsY4hddko2txIPjx1ZjmqZYuidl+xx5djG/ZINAnuM1KwI9MXxFl0t8Rd7QnZULlHwd3q2Z5GpZhRNBsEkbjD8gWbeeZLUPVC/dJ1X3PPyUxQUg9Jtg7VRZrwOFa5qNfPj0qMbmyixIUxZumqb5FSlFHqM=
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create Asset"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/assets"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint is used to create a new asset that can be used in a Disbursement. Note: the organization must hold a balance in a particular asset to use it in a disbursement.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./create-asset.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./create-asset.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./create-asset.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-asset.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/create-asset.mdx
new file mode 100644
index 000000000..a9be998cc
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/create-asset.mdx
@@ -0,0 +1,5 @@
+---
+title: Create Asset
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml POST /assets"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-direct-payment.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/create-direct-payment.ParamsDetails.json
deleted file mode 100644
index aa90559ad..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-direct-payment.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"X-Wallet-Id","in":"header","required":false,"description":"Names the distribution account this request acts on. Required when the tenant has more than one active account. With a single active account, or an API key scoped to exactly one account, it may be omitted.\n","schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-direct-payment.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/create-direct-payment.RequestSchema.json
deleted file mode 100644
index 3bc64badb..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-direct-payment.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"application/json":{"schema":{"type":"object","required":["amount","asset","receiver","wallet"],"properties":{"amount":{"type":"string","description":"The payment amount"},"asset":{"type":"object","properties":{"id":{"type":"string","description":"Asset ID (use either id or type)"},"type":{"type":"string","enum":["native","classic","contract","fiat"],"description":"Asset type (use either id or type)"},"code":{"type":"string","description":"Asset code (required for classic and fiat assets)"},"issuer":{"type":"string","description":"Asset issuer address (required for classic assets)"},"contract_id":{"type":"string","description":"Contract ID (required for contract assets)"}},"description":"Asset reference - specify either id or type with required fields"},"receiver":{"type":"object","properties":{"id":{"type":"string","description":"Receiver ID"},"email":{"type":"string","description":"Receiver email address"},"phone_number":{"type":"string","description":"Receiver phone number"},"wallet_address":{"type":"string","description":"Receiver wallet address (Stellar account or contract)"}},"description":"Receiver reference - specify exactly one identifier"},"wallet":{"type":"object","properties":{"id":{"type":"string","description":"Wallet ID"},"address":{"type":"string","description":"Wallet address (Stellar account or contract)"}},"description":"Wallet reference - specify either id or address"},"external_payment_id":{"type":"string","description":"Optional external payment identifier"}},"title":"CreateDirectPaymentRequest"}}},"required":true}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-direct-payment.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/create-direct-payment.StatusCodes.json
deleted file mode 100644
index 201d67fff..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-direct-payment.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"201":{"description":"Direct payment created successfully","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"ddf22f55-3259-4822-a4e2-ce01334997f4"},"amount":{"type":"string","description":"The amount of the payment","example":"100.00"},"stellar_transaction_id":{"type":"string","description":"The ID of the transaction in the Stellar network. It can be used to track the payment in the Stellar network using [Stellar Laboratory](https://laboratory.stellar.org), or [StellarExpert](https://stellar.expert).","example":"0b339d1c89d314186b8147c2af4c9a9ed5bbdbcd7ada8d138633907649b"},"circle_transaction_id":{"type":"string","description":"The Circle transaction ID. It is only present when the payment was made using Circle.","example":"74a68b6a-3f67-424b-b8b0-e593a19d7463"},"circle_transaction_type":{"type":"string","enum":["PAYOUT","TRANSFER"],"description":"Which Circle API the payment went through. It is only present when the payment was made using Circle.","example":"TRANSFER"},"stellar_operation_id":{"type":"string"},"source_wallet_id":{"type":"string","description":"ID of the distribution account the payment was sent from.","example":"4c379f5e-09b5-4472-a286-b84e249a1512"},"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_history":{"type":"array","description":"An aggregated list of metadata objects containing the statuses and the timestamp of when these status changes occurred.","items":{"type":"object","properties":{"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_message":{"type":"string"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"PaymentStatusHistoryEntry"},"title":"PaymentStatusHistory"},"type":{"type":"string","description":"The type of the payment.","enum":["DISBURSEMENT","DIRECT"]},"disbursement":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","format":"uuid","example":"c51ba1d5-52d3-412f-a59c-6ef32d59ab43"},"name":{"type":"string","description":"The name of the disbursement","example":"disbursement-june-29"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: `{{.OrganizationName}}` which is the Organization Name configured and `{{.RegistrationLink}}` which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED","CANCELED"],"title":"DisbursementStatus"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"status_history":{"type":"array","items":{"type":"object","properties":{"user_id":{"type":"string","example":"3f351b9e-ed0f-40fa-a314-14757b42dab1"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED","CANCELED"],"title":"DisbursementStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementStatusHistoryEntry"},"title":"DisbursementStatusHistory"},"file_name":{"type":"string","example":"disbursement-feb-03-2023.csv"},"created_at":{"type":"string","description":"The creation timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:57.831975Z"},"updated_at":{"type":"string","description":"The last update timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:58.316511Z"}},"title":"DisbursementLite"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"receiver_wallet":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"enabled":{"type":"boolean","example":true},"user_managed":{"type":"boolean","example":false}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"sep24_transaction_id":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invitation_sent_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}},"otp_confirmed_at":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"},"otp_confirmed_with":{"type":"string"}},"title":"ReceiverWalletLite"},"external_payment_id":{"type":"string","description":"Optional external payment identifier provided by the client.","example":"payment-001"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"Payment"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-direct-payment.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/create-direct-payment.api.mdx
deleted file mode 100644
index 4b5627b9e..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-direct-payment.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: create-direct-payment
-title: "Create Direct Payment"
-description: "Creates a new direct payment that is immediately sent to the specified receiver if they have a valid registered wallet. Direct payments bypass the disbursement workflow and are processed instantly."
-sidebar_label: "Create Direct Payment"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdW1tz27gO/iscvWw7Yzm6+ZY3J3Zat4mT2k6z3W7GS0mQzY1uS1JJvRn/9zMkJVmK7cRts3PO2T60rgSCHwASAEHoUeN4wbTjr9oVXkUQc6bdNjQfmEdJykkSa8faKQXMgSGMYnhAPqHgcZQqcsSXmCPCEIki8AnmEK4Qky8SxJeAWAoeCQj4iIIH5B4oIoF4s0JLfA8Io3scEvF2QRgHCj56wGEIvIkGtZkYclcpZkxy9QlzM8pAQnhI6F0QJg8Ixz7CFFBKEw8YAx+RmHEc83DV1BpakgLFQqaRX0ql5shl1xpaiimOgAMVOnnUYhyBdqz9qt9ITPrI1xoaEUpZAvaBag2Nwl8ZoeBrxwEOGTxV3hhHUGLmlLiZeIGw5yWZVB9hSLAAxhH2OENJ3ESTnCd6WEIsB3OIcczREjMUJRSE2mOUxCDGEKFGxa+JbghfIowYiRfh07cNlFCEY9S/GqE7WCHmJSn4wlLwDXs8XOUcc2LCUYRXyAWURIRz8Ju/x1pDY94SIqwdP2p8lQrtCLHihbZe3yptAOMnib8SFF4Sc6HY40cNp2lIPKn/oz+Z0M3jNqvE/RM8XtPqVw1HAo/W0DBjoF6qlaQ1NLVWxJpNqbAvJ8DkbGrMFsin5pktoVzK+Zh1MdEOWPVJiP/yBH3BCo0G6E3GAAHhS7EDfGEJMfCtmE5x2OYEcRYJBcRYWFFraF6IGSOe+JXEnGKJKSCYb29aNa/g+NzMXuLvnHkXL0GL3hSGQUFCUY5HbjwBA0nFMcmaMJYBPZS5okbY9ykwtm+aDfdC/vkhNjjNiaUZ6pyLNyXr9W58FAKgEHuA9NylrbZVih7E5ttMQCD0mUBbLthXWVKTwpGOBoI5RJiE3zFK0heaFgzSZRLDPM4i9xB7lXzkMJQPWxdbcV4wPpyRGrix/ZRDGGJa+siKnXYZqOSz00YVx0Z8iLmIRRW4r2MRFR1yexysgJufkzsf/uLKrFgavnGgMQ7nucs7aPdcyh84RMXo0mFWFSrcGOEh7I6sExUWtPV6XfXtnGYgH7A0iZnSt2WY4p86hnoqgDw5g49Y5olAH2RhuMqd4g9Fm0MsDt9wlEr5fD+wrKDV0m2r1dOdrmXp2AFL98Awbdvp9TqBIxfCd8QgRYsSmRoVctZmNQ2jaRiCL1PrZM4pjpmI8El8kCHFPKNBMUdlNCIqySgWYAxc5FRNNOLIw7HIADKmEgWxGu+qGPeMRZnIQNDX4vE5dhOKeUJXt2+WnKfs+OgoLJ81c5GaCV28lVlKMXD4TRhmM6YgBPn8bbOmIsO17Z5vet2eb5uO2W27XdPpeBYOHK+He+C3XNd3Pb+Dfdz1Tbvbtu2e0Wk7PVfGFEK9EH5IradyaE2no4HUHxEZXbhCKQWZFpcZXaG/B5HSYR9yjSlOdbk6Dm533TbW7aDd0R3LcXW36xo6tHo2Nnt+x2nbewR4KbW46n+5vJ5pDW026Y+nZ8PJdiZxsyTespBQpI419OoMQJNssXw1eUsslcVeJu87bSIIk4x6MM+j0CGG2+yFPal5HbQUJ6BJVAfreHanF7RAN3puS3ecjqVjq9vW3a4DltPDZsu0lCCYZwdEBbGcFO0Ob5BbbTDpnwmjTYb9wRetoV0Nx4PR+J341b+eDgdaQ5ten54Op1OtoZ31R+fy0Wl/fDoUP283vjr3z1MFroQ5XxImNmYFLqYUr7aztxjhxYLCQvrjkDDpwyLg2MccI+VhmYxjmMTC4LyUTxwpY185IxIB4zhKxehiybBSEd4SxwtgKPG8jFLwhQUIh4i97Mz/v9QeAWN4sWPHyvCa62iXMEFCI8xFcMIcdEFaW6SWYdm6YemGPTONY6d13DJ/q8XsGqD3yvjDmNOV9gLRc+eXbQ3LLLmu32ZVwaPpyfVkOrwYjoWeB6PJ8HSm3YrUp3Lgf52cTcDJYvJXVk0MKw5hM11Fu1lG/JpivZbpYtNv6S3Lt3XHtAIdt3qe3obAtvxWD7uOdM2qkHAIJkG5B0YlBam80P/MYtCtXvWgMVfllNxj5qtqziFKQ8wPBOJljCcRKgaVKQCDWBRW7gmX3Jl4VszLmkgM/cOHAGch/wPlUyPC4l9ErsozGoPfRCMVFPLXvygPIdMJ/gtDacIYcUVATUT6KkmDJAyTB+lBCkT3mBLshsCO0R+Pj81LusAx+VuiEmWX9foP9CCDF1EVmCoBEhRi1oAsMnFaE65IcJlUNHdO4rstLiGJ79ACYhGPwEfuCk0HV6Vi8rJXWex6Q2LkYQaq0kMYihNeBkdS00JDCY8znkSYEw+H4QrhNIXYF/hURILYf5L1fEmyopS2CVeEC02JI+4qyWTUQjs11ESnIfHu0E7BlWVVXa6plldlVUmf7vEXU4zhRX90Lnzk+8vxcD6+vjgZTrSGejzvjwfzm/75+XA27w8GE+U6q5S7KCqOtAr6VAGaCRzPBtx9/nw6609m0meX/vz08uLqfDjb68gHlY248eb3QEmQHz/msgzwLIz+bDi/PJufjCaz91pD+zLsT+YXl2P5n6vRWGto4/5sdDnun89Hg0KDFRCfK9OdydkOCeQHBtCMAd2TTm3WoB3YLdPtgQ6+EeiOEWAd26ajm06n1XEdy8eu+V+2yT8aPren3BdD91IKooCEMN8XKvZ4/wBc3bB1AbHpsXt5DlDH4zk+8PAp6YVPrKVhz8XB59TU1m1jZpjHlnXc6jS7ttnrtH4TsLLU/y5YIWYcqUGvj6zbtM12y3zGjueEw08XgzcQggCD57i27rRdQ3d819Gx4zl627NbRtdodTpG60dKsrVJrqeD058tvtYYvjs5GTid0Vn7/OZj56pzMRh+np7eTDqDq+ubz/b4iz2YfRp+Pjt3xv2Z0//03v7t/PzsvN96eRn+0JZ7aRH9IFMfQvhJpu2caWvjHLZXdFnhk2ovF1Kx+qQ1amnczxUpNxi7hm3Ypu/opm84utPt9HS37fd032u1HTPo9bpdeI1CdaUWY/XAAt8Q/qmtO55j6F3X6ehG127jbqvjmNiqbb2ijFtsu9cSvYV9WfrRnVYL606na+nYANDNttFpd8DwQYWml93uZ+JScQnXZ4wwaadlEkG687xWHVfUru7VeJymTS+JZDiEdG4acy8kohjrJxEm8fO8cEp0H+6b27x8gHQuctP5vgu6lzEdMT8V7GWtOBapdVW5bpKEgOMqn7yAK3OECMd48dIAeUdaNbuqYhdGL6o9z9TQK77p9Nf+B/vXD/bnj/aHs/f2p4vB2eX044U1vrj47WR6aX8ezdrD66tPN9PBjfWh41xY9mQyPa9OFEGU7C4nVQj2pLjKgJbzYsXwRV/4rIdqGoZxgOs7jMfm3DYXJ5DDefW2eX1/MjcZvhtNZ8OJTN3Ozvvv3tUzt8IHMLUqvqMq9dPVoFeH/Br5pmnsyTd3zlpPOdcNLeHpXJ5wafSzEbOO5Clrce+5qyFgG3B9u/9j91GiBeSe+Op4LtJF5WLrB+d8mG4Y5v9TurJdkBPXauuG5hjG9s3ZCfZRcfv2ajdkQGlyQHY5AI5JyBB2kyyvXsiByvIUv7xh1+qPkG3HreB1jDO+TCj5G/x/XLjDQW97mc0l+f4Cr5KzNH6JQxsnHNXk3MAoJnIMs8L66YhShfa2Cs8S6hLfh/if198e8TYICpjONkwh0VmSxf9yMwe5iLss7FQtPAF13SWriWpUsVMYeBklfCX7104AU6D9TLjnr7eiQSsCvkxE/1uaMNXwJt5pR0WXnWjwAnpfNMBlNNSONU2MLBhPhYKVBqrsNyE5JR9hx01RviBVpUG1z1XvhXAs66gfbmbozXBqtdpv82616eBqXrSsCQee9+TV+D3pyls3tOnwyjReCRmaDq9001DYlMzokSd3EK/ffhciy3lNRJbzGog+ZUBXh8GSpKhskdyHqAJAQiom/ksMl/FL7NXJplNwuNkNRc/EJqSU5ReRG2weF1uubI2TZZPN+6ICsnlSaxmrbPfqmbc+R95ZtXlQ75TaPH/a+lThvjnG1nnvot2ZDlXekzhQh5U8/BflhGrVCl2FmIu8QmwZTZaimbJep2k0DbG9syjCIomulSR283gzHVy9FbcWGPEkCZGbkZDLa4WkcpUgr4AifAfIzcK7TcOuuL1BC5pksmpHwSMpkS8ScTOyq+NkZx3wfwvi7/Hv8Sy/yxE9uCnEeu6MU5qIQFH2RCsooq6alHXLJ+wa5RW4bK/Mu22kR5cDaxdfFNKEEZ5QAuxY4NDR1/ycWjTG6LXacJorSXexdwexv+mjWRC+zFx15v8eDm+P0Uy1LOdQVoUXUJdjOZmUisQBxYzTzOMZzQUUduEv2bT5HZIFVKYDPyNaweIl2R7ARQXtD0uzhDDSvSWmnD0LuUJ3xCnAkagNHeUPnpXnJTHeQxghyUji9yENk1XRmfH8XlMtOx8zF2gMHJhqCOdAI3YZTIHeE69aXKp0dR1JIj0JdJaTNbSQeBAz6faLeJVibwnIkn5KpR6C1/HR0cPDQxPLt5JbPpQdnY9Oh+PpULeaRnPJo1CGF5HaRDiuMFYticUXBZt2/5qzqbSr/2u+ecjDJIdv/CgNRXlxnWv2MU/9vmpl6ncrKpqMi2ePjy5mcE3D9Vo8VqH7+OttQysu3WVC2SiyCZEr+oTlJcNdX0JUtfvv+yhip57vYLX18cg9DjOQKXXjMSc4VXrR5cX1hmLrcLMZ0fc8SPmztNVU/+pyKkpabv5RRqRSJYofxLcU+EGgEV/HyDgpCOSzRy3E8SJT5w3FU+wtvJUp3slMMf8h1kHxKl5VED5NRZUg4m8h1s4hj48qD12vS3r1au+I8qMcRS2scLter/8DG2oQ8g==
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create Direct Payment"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/payments"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Creates a new direct payment that is immediately sent to the specified receiver if they have a valid registered wallet. Direct payments bypass the disbursement workflow and are processed instantly.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./create-direct-payment.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./create-direct-payment.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./create-direct-payment.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-direct-payment.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/create-direct-payment.mdx
new file mode 100644
index 000000000..96f3b0bd3
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/create-direct-payment.mdx
@@ -0,0 +1,5 @@
+---
+title: Create Direct Payment
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml POST /payments"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-disbursement.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/create-disbursement.ParamsDetails.json
deleted file mode 100644
index aa90559ad..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-disbursement.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"X-Wallet-Id","in":"header","required":false,"description":"Names the distribution account this request acts on. Required when the tenant has more than one active account. With a single active account, or an API key scoped to exactly one account, it may be omitted.\n","schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-disbursement.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/create-disbursement.RequestSchema.json
deleted file mode 100644
index 6cdee61ea..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-disbursement.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"*/*":{"schema":{"type":"object","properties":{"name":{"type":"string"},"wallet_id":{"type":"string"},"asset_id":{"type":"string"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"receiver_registration_message_template":{"type":"string"}},"example":{"name":"My New Disbursement name","wallet_id":"e2de8544-b7e2-40a9-ad40-411f70d5c4bf","asset_id":"d227a68c-2f40-11ee-be56-0242ac120002","verification_field":"DATE_OF_BIRTH","registration_contact_type":"PHONE_NUMBER","receiver_registration_message_template":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."}}}},"required":false}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-disbursement.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/create-disbursement.StatusCodes.json
deleted file mode 100644
index 73cb4217d..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-disbursement.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"201":{"description":"A new disbursement","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","example":"619da857-8725-4c58-933d-c120a458e0f5"},"name":{"type":"string","description":"The name of the disbursement","example":"Disbursement Name"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: {{.OrganizationName}} which is the Organization Name configured and {{.RegistrationLink}} which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"created_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"}},"title":"Wallet"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED","CANCELED"],"title":"DisbursementStatus"},"source_wallet_id":{"type":"string","description":"ID of the distribution account the disbursement is funded from.","example":"4c379f5e-09b5-4472-a286-b84e249a1512"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"status_history":{"type":"array","items":{"type":"object","properties":{"user_id":{"type":"string","example":"3f351b9e-ed0f-40fa-a314-14757b42dab1"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED","CANCELED"],"title":"DisbursementStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementStatusHistoryEntry"},"title":"DisbursementStatusHistory"},"file_name":{"type":"string","example":"disbursement-feb-03-2023.csv"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"total_payments":{"type":"integer","description":"Total number of payments","example":10},"total_payments_sent":{"type":"integer","description":"Total number of successful payments","example":8},"total_payments_failed":{"type":"integer","description":"Total number of failed payments","example":1},"total_payments_remaining":{"type":"integer","description":"Total number of remaining payments","example":1},"amount_disbursed":{"type":"string","description":"The total amount disbursed so far","example":"800.00"},"total_amount":{"type":"string","description":"The total amount to be disbursed","example":"1000.00"},"average_amount":{"type":"string","description":"The average amount per payment","example":"100.00"}},"title":"Disbursement"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Bad request","extras":{"status":400,"message":"Invalid wallet provided"}}},"example":{"error":"Bad request","extras":{"status":400,"message":"Invalid wallet provided"}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-disbursement.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/create-disbursement.api.mdx
deleted file mode 100644
index 623e3f424..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-disbursement.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: create-disbursement
-title: "Create Disbursement"
-description: "Creates a new disbursement in  `draft ` state with basic details. Important: a disbursement is not triggered until the organization adds receivers through the Upload Disbursement Instructions endpoint and the status changes from  `draft ` to  `ready `."
-sidebar_label: "Create Disbursement"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlGtt2GjnyV3T0MskcGhpojM0bNnjDjoM9BsebyeQQdasatO6WOpLahPHh3/dIanBz8SWJMzs7+2IwUt1LVaUq3WFNpgp3PuAeU2EuFaTAtcIfK5iCiiTLNBMcd/CJBKJBIYI4zBEtbUaMI/SJShJr9AkpTTSgOdMzFBLFIkRBE5aoKhqkmZCacN1BZAuBQlxopCWbTkECRTnXLEF6BkjIKeHsD2K4QIRShSREwG5BKqRnUuTTmd13lSWCUFQWAg240jKPDKhCwGkmGNeIcGohDKO5QtGM8CkoFEuRlsTQAqFPEghdoE9VXMEiA2mZGNC1MsrEcAVnRJIUNEijzjvMSQq4g//lXZMkAe0NKK5gZlQ5A0JB4gqW8DlnEijuxCRRsK3yIUlBWV4pU1qyMHdaiCKRc430jBltfM5BaUQirZDgVXRZ4ETzGXALrIETrtGMKJQKCUjPCEeCg4Fht7DCV0XXxmgEKcanyfZqBQmJCEfdiwG6gQVSkciAGjXBFxLpZFFgLDYzjVKyQCEgkTKtgVZ/57iCVTSDlODOHdaLzGjHiMWneLn86LQBSh8LujA7IsG1UWznDv9c+9l87ECL8N8QWdVLYx/NQJlVp/kdGhU8t5aYMLp3lSj18OItSBazyLrAJGaQ7NlWwcDz1J6l7rg/OT+dHA8ux29wBb/vdy8nb8+H9p+LwRBX8LA7HpwPu2eTQW8yvHp73L80Z04znRiM70rkTi21pVHQ1PiB48Goh0R64lh4mJX+2+7gzFB9cz7sryhV3M+T7rA3ue6enfXHk26vd9kfjbZ27ttRYvOyxNGJY2hs+LDMumM62eA6BaXIFCYa0iwhep+ZlhUMX0iaJXBvS/x2gYYw3zzedmnDqBgaFA5bQeCFbWh4gU+OPEID3wvq9bjt01YUhDEuWxrTRqNNDg4jrxEHvlevA3ghtA48vxE0SFRv+L7fwPvNv2PlR+yzrf7nage/FzmaEXMOUUYWVu45YZrxKYqFRAuRu8h1d1c9L4VKEzqWyyo6SVh0YxbLljpj/Ga5NGfXUQdZxcvlcrkTkOwvKhNcuYPV8OvmYzNKdXcSAq6UDy/JsqTQXO3fyoA8/yTvO4zbUXI8A5Rz9jkHxChwzWIGEol4FTjLbK0dCx/Ujyg5bLW9w3aj5QVR69A7ajapZ0xOgtYh+HHLuPH+WLKPB7PzSbIbDmyM9D1HZR8XUa60SNEKCOXKRWkFnCLGb5kmLh9a6xeZtIoM6CcKMckT/QkVpBFT/CeNJOhccqBVNHAJpVj+SaHCzIjpnxTKhFIsTMCgJtQl2VgkiZgbb11zdEskI2ECqrPfadF8xqKZqQkMgvK6VZihGbNpblKcSeX7fXsDR8L4DZoCNxkcKAoXaNS7WCtFC7tppQz0inEUEQUuvxalSSZBFaVOSQMVJzjJtUiJZhFJkgUiWQacGu603Qucvq5uOMGfdqb/x1KGi+TfGhXu9dsilBwBbXlBq0W8oH3Y8IgP4NUP/PZBG3wKYf2xs32P6R0LpamdukoxpQ3MTKSQkekTcDOtM9Wp1W4dPMmyaiRSA68gm9T9SZQw4HpCRUoYfxwXyZhH4ba6i4sCZBPj3JOH6qqneaopmhn0Bl9kq1o6IXofpljI1KxgSjR4mtnke4++4Teant/2mvVxw++0/E7Qqh4Eh78ZxHlGfwTi5b1XuRp7XcV9vw/FMYEoCJtecBD6XkDDwCNBFHgHUbPlH/qtdtu3+SES9BmRuWuYQnZvmcjVqHdikDClcpDPReN2mxArQakNhP84Pu4F7cHpwdn1L+2L9tte/93o5Pqy3bu4un7XHL5v9sa/9t+dngXD7jjo/vqm+dvZ2elZt/VC1m94fnNcNxbqtOovZfldpBQS+E6kBwXSVoF0uS+XjjQkCZHIuhRaO9LK56w17Jm2N8lH7wOX3dMxruDLfrf3HlfwaNy9HPd7JnJ2r0b2y8n524uzvvvxpDs86Z/1e+W4Wa4cRo6gIS1yGcHkkYvNtmCDXqlI2XephJ27eZzbfGZy0mYiC6Jm+yhugecfhS0vCNoNjzQOD7zwMIBGcETqrXrjr3J5ckaazJjSQi5K9ImUZGGu5hpS9XTgyBXIBxR9r5hm3GzVwyPwgPqxF/gx8UizHnj1oN1qh0GDEpeB/oueYw6G0iTNXuxgLh8j+cbpvc+1XODn7DSbYpbA5OksXfZXL4bQ85ueYbEaqZfKa39SZNNCk2RSFIVlv2Bcw9T2jLbClAFAPE9Dd+dZg5ao1f0dzBNVXM6+Er3KowiUivNkL6XDXUIxYQnQbyDlAPcLtEtGgimkjO6/ntIa9kFiJDWxcbLys2deSi2LyMGuYypFSqCYyA13OPT9qu/fO4CD+QYqWpiW2z2fZSJ1f02F3II0V8uvoVPArChlIFfq2qZiiTxwxIs+Q+D7u42EY0Jt9xLUC3YQQEqxp7KyTSYtyTMC/k6Mdp5jUBTXwH1NrK02VsGGlVGuZbxnYUUk8P0SWjzgtyRhFLn8jjIpbhkFin88emelPe2eK05yPROS/WH96+9ppqHQaEPMfaqsl1W5BfEjETvTNHdNcypkyCgF/uPtsl+6ewaescGJEeyKYSQ+FTn/W7jXw24QFyLu84Cg7AGX4Kp824hyUMsCtYIol0wv7MDpGIgE2c31DHc+fDQTlS+euXJOgXtFUPBCQRde0VM33x194Mr0BC2WG1jgzqOQFXxLknyNwRBKQc+EaYlnQrlRmGEC1+jGTNHwK29X87FcJriDLfhKjJExp9N3WZj7Uj1jv8Bi91pcHA/XJHTTNduaLNI64bbh98/rMXrVHzVaB6+LYdaodzFZTbTMzaZQzAa+raHdsoJH/Yu6/0KcoVH/wqv7jjcnM7rT4gb48vVXcdQIXpKjRvASHP2ag1w8jy27Fa0nqA9xVGLAsrQi/NmA26DDeCwsuaL4WN3hNxrvFwnRpkI3tnfDHeXYaFf9qm/8NE9TYm6JG32A/ThejXoXr801mSAtRILCnCXaNnLLs2vbcE/JDaAwT27WlabtlaOpFHnmStGIZcwuCNOL1iXqHPRcyJvq3ursr8Xi7/x3Pi6652bWnAH3ihiWSWHiqxlC296CY0VwpEW2akxsoausR/YmJqGIcFPk2kBoATfGDBIyoZgWkoHqGD489EE5fLXi09u4L2aFkryQRDfA6cdXq0bplOlZHrom6ddgeN1BYzeaL1hZrNzZjSOKbVYqxmNJ3CuFXBYCGrvop2xa/QrJYmmz6PeItkLxlGxzCNFq7zdLM4Mk9aIZkVo9ynJpX01LgJq5x9WKHx6V5ykx3kCSIovI8k8hS8TCTrGePGu5eT6BfslDkBw0KPfwQYNM1Xk8AnnLonI3vmCzKuS0Zjd5IvZUsa2CExYBV+VJeDcj0QxQw8Ypl0MNrk6tNp/Pq8SuWmwFqKqdDU76w1Hfa1T96kyniY2TJlGnhJcQuzctaOtRy0aoKT3K+H9/D1SkMw1fdC1LzBBnWZjjrqh+PuDN6uejGR4pbRbu7kKi4Eomy6X52WWvzoePprJyw1FbwVVWCdWUS5Qps/DAW6GyZf5+z4b2KtsVqpvPq1aFKV5WVpXsidOLZ4eM9zvMk6L7Td0ogkyXlncuGxtV7sX5yPRkw+KlUmpnQFiSuXnZQeaOAUx2Kp8bW/kUX4xRV0t8UaK9XVo5Fs1fw/BekLs7V1ctl+v9bulBiPUbNLfbqPTjcrn8D2fYv2w=
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create Disbursement"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/disbursements"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Creates a new disbursement in  `draft ` state with basic details. Important: a disbursement is not triggered until the organization adds receivers through the Upload Disbursement Instructions endpoint and the status changes from  `draft ` to  `ready `.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./create-disbursement.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./create-disbursement.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./create-disbursement.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-disbursement.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/create-disbursement.mdx
new file mode 100644
index 000000000..04a3c5a47
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/create-disbursement.mdx
@@ -0,0 +1,5 @@
+---
+title: Create Disbursement
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml POST /disbursements"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-distribution-wallet.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/create-distribution-wallet.RequestSchema.json
deleted file mode 100644
index 4f5ad6295..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-distribution-wallet.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"application/json":{"schema":{"type":"object","required":["name"],"properties":{"name":{"type":"string","maxLength":64,"description":"Human-readable name for the new account"},"description":{"type":"string","description":"Optional description"}},"title":"DistributionWalletRequest"}}},"required":true}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-distribution-wallet.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/create-distribution-wallet.StatusCodes.json
deleted file mode 100644
index 606714e1c..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-distribution-wallet.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"201":{"description":"Distribution account created successfully","content":{"application/json":{"schema":{"type":"object","description":"A distribution account the tenant sends funds from.","properties":{"id":{"type":"string","description":"Unique identifier for the account"},"name":{"type":"string","description":"Human-readable name for the account"},"description":{"type":"string","description":"Optional description"},"distribution_account_address":{"type":"string","description":"The account's Stellar address. Absent until the account has been provisioned on the network."},"distribution_account_type":{"type":"string","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"],"description":"How the account's secret is stored. Additional accounts are always `DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT`."},"distribution_account_status":{"type":"string","enum":["ACTIVE","PENDING_USER_ACTIVATION"],"description":"Status of the underlying Stellar account"},"status":{"type":"string","enum":["ACTIVE","PENDING","ARCHIVED"],"description":"Lifecycle status. `PENDING` accounts have been reserved but not yet funded on the network and cannot send. `ARCHIVED` accounts accept no new disbursements and are never deleted.\n"},"is_default":{"type":"boolean","description":"Whether this is the tenant's default account. Exactly one account is the default, and it cannot be archived."},"created_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"archived_at":{"type":"string","format":"date-time","description":"When the account was archived, if it has been"}},"title":"DistributionWallet"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"409":{"description":"An account with this name already exists"}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-distribution-wallet.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/create-distribution-wallet.api.mdx
deleted file mode 100644
index e413ddce1..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-distribution-wallet.api.mdx
+++ /dev/null
@@ -1,73 +0,0 @@
----
-id: create-distribution-wallet
-title: "Create Distribution Account"
-description: "Creates and provisions a new distribution account. The account is generated, funded, and given its own signing key, isolated from the tenant's other accounts."
-sidebar_label: "Create Distribution Account"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWN9z4jgS/le69DIzVcYwudxeLW8kcDfcppJcIDMP2VQi2w3WRpY8kgzxUfzvVy3bYAL5tTtbtQ+XhwBSd+vrbqn7k1bM8bll/Rs2FNYZERVOaAXfuJToLLsNWII2NiKnYdZnpwa5QwtcJZAbvRBWaGWBg8IlJG0TPI51oVwI0xSbHyAszFGh4Q6TAGaFSuiTjM3FAhUIZ0EvFVgxV0LN4QHLAITVkhRgZnQGLkVwqLhyHyxol6JprNvwV/WrulgqNKCVLEMYLLiQPJLof4PTtaaFwpJ5snU/HE+mV+OT6+n44vxucHp6cX0+DSfT0dnZ4Cocntx9HVyfTe83LrgyxwCKnKxxyPijyIoM9AyOem0gLGA6J0eFVuNkE7l2lKsgs4AZ/F6gdSc6KVl/xWKtHCpHX3meSxF7I93fLGVgxWycYsbpG0Fhfaaj3zBu7AiDCaVT8QwpfbkhGE6gJQ0/utUkLGrOApbxxzNUc5ey/k/HT3P+pci46hjkiQ8l2YCZNj56lPbaa7Z+ori/zK7dC/+FS2gPr9cBc8JJ0tsP1lUVKbYmsa27zhToB2yula1cPep9po/dJYcHdijEPjMJ2CKO0dpZIWXJgt+fht0lBwePRWsbg0WVWH8YrN/iIXuaNpG8Hs1rJb4XCCJB5cRMoNnkqJWf5/L/9oT/2GQHrB2cu9r4HU8Sg9a+brVVWz5YmDiUkhuo1UMYRBaVg0I5IdvoIeUWIkS1rWGYgFb1lnZLbR7CZ9FVkPahoSoyX0lfKiij868seFmkqTnPyZ2Or07PRluxvSL9RS/b3n6wYDE26MuvddpgEsIgSUSdkaZqATcIXC55ad9aFZ8PknXcFQcz2IRpcDodfx2xgF2Ozofj83/dXU9GV3d+dECr7vs18Tap1pJ31DyMLKmObxK/3ZzvX58FbHB1+mX8dTTcX/pMzDAuY4lQGQ7hvla738Yv5QustpVBi2aBCUSFA6UdlOjqdvdkm/nmF3NFQlQIQrhvULQs8zjGnCw1fTYqjMUM/ZxKfOYULtBAghIdJtSB1gET9i7BGS+ka0Ui0loiV3uH6VuKvp26VFjaKjudtjazbeujRx47WYJWO+2dlGrZqrEL17gXIXATp2KBid83dd294+5QmmbaZDTDEu6w40SGpFPkybt1mkXfrnQgMmqnfiy53fgSgJiRl01NeaWFUe9aB+y419tvTyc8gabF/YEGtNs80BhtXi+lQ3RcSAs80kXVnirFdcDw0RluX11pXf2Rbwda77XihUu1Ef/F5E937u2g9wuFKrIIvd8ZWsvnB2p97Sc+8iyX2MLBzrWDHT+3MJqFjnufW6afamxC+Lf9EP5Tm0gkCao/P37PuLdF0MD8eR/mYMtylsKlVT3xJIJLIhUl4KOwzvqDYjEujHAl69+s2Alyg2ZQEA+9uV3fUpxcqok+59qfiZzTHOu2e05nWd9WyJpZoLHeWGEk6zNGVppFJhSVyvH2UhvveS5+wXKfwtXp8SGGFHmCBigBXPhbClcwGV7Cv79N4eNocvT3nz6BNvXoHQwux3SPIVZX0a9deyxgghapzNK2m4wuP/d+EDKYjC47n3sVtspnWDn9gGr96V2Ijo5/JKKj4x+B6D8FmvJtsLwo5NzwDN3ziFoAPKRm4e+k7vcrHbCr7X1ttD0jtd4z5XVbmISaaQ+4bhENeRm2ujpcSu6oMdHuYQGjTV3Z+UfYC3u004ss46asOfDLNj5OhpefqDlzcFpLiAohnWf02sy5qoNs6Uab8QeEqJAPkPOy4hf+njs3usiJeRmMRS78hF5gdSdoVt8w50M0/a8FkV4KpjXP4Qp0jqpjdWFipCsBlUpwKfeMpoJCrE3nDfd8Yq5iOjQR6wSJ7xDZmelCbejeTEupl7TfDObaCqeNQNsnHB24sZW9bv3ZaTO8Tl4HqRPx+AFVcvsxdS63/W53LlxaRGGss+67LHzqg3d+A6VsDkRF4Gqxir+pmeHWmSJ2hakdbC6DL+Y0fIdnM+Pb2R9xrTHxmm9LjKCR/d3epCizTpxy4+yLkFtyXWcQuxkXqlsPvOjPa258QZmBN+TxJ5hLXTZvWi+ftert65ciQqPQYf1a5dBk9mI2QbMQMdWlxq0aZqjNvOuFOnrWsbVYwKSIUdl2BRzkPE4Rjnydqrow2ep3u8vlMuR+1lurVW33bHw6Op+MOkdhL0xdJn2lpY6fcdUyXD2hwc4jzqC+8u09R2wI0v/fLN/xZll3UYePrptLLvwt0udwVXOvG3aQe90GLCWK1r9hq1XELV4buV7TcNU7+ze3AVtwI8g1z+6Cpp0TWXtAamWnVc46U0JB4rKoevoTgrsOGo2Bvxi/KNtmkZcXE3pWieqX1kwnpGP4kl5P+ZL4Ir3b+l5DAn5sxSRX86Ki65VN2p98j3g8eOJRfyGvmilVthA+ZTaVI/Sf3DqoslpVtGa93shXU89q1KFtpCmPt+v1+n8PzWVi
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create Distribution Account"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/distribution-wallets"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Creates and provisions a new distribution account. The account is generated, funded, and given its own signing key, isolated from the tenant's other accounts.
-
-Owner only. Available only to tenants using the `DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT` account type, up to a maximum of 20 accounts.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./create-distribution-wallet.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./create-distribution-wallet.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-distribution-wallet.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/create-distribution-wallet.mdx
new file mode 100644
index 000000000..39fcce587
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/create-distribution-wallet.mdx
@@ -0,0 +1,5 @@
+---
+title: Create Distribution Account
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml POST /distribution-wallets"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-receiver.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/create-receiver.ParamsDetails.json
deleted file mode 100644
index aa90559ad..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-receiver.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"X-Wallet-Id","in":"header","required":false,"description":"Names the distribution account this request acts on. Required when the tenant has more than one active account. With a single active account, or an API key scoped to exactly one account, it may be omitted.\n","schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-receiver.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/create-receiver.RequestSchema.json
deleted file mode 100644
index dee4eba49..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-receiver.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"application/json":{"schema":{"oneOf":[{"type":"object","required":["external_id","verifications"],"properties":{"email":{"type":"string","description":"Email address of the receiver","format":"email"},"phone_number":{"type":"string","description":"Phone number of the receiver"},"external_id":{"type":"string","description":"External identifier for the receiver"},"verifications":{"type":"array","description":"Verification requirements for the receiver","items":{"type":"object","properties":{"type":{"type":"string","enum":["date_of_birth","pin","national_id","year_month"],"description":"Type of verification required"},"value":{"type":"string","description":"Expected verification value"}},"required":["type","value"]}}}},{"type":"object","required":["external_id","wallets"],"properties":{"email":{"type":"string","description":"Email address of the receiver","format":"email"},"phone_number":{"type":"string","description":"Phone number of the receiver"},"external_id":{"type":"string","description":"External identifier for the receiver"},"wallets":{"type":"array","description":"Wallet information for the receiver (max 1 wallet)","items":{"type":"object","properties":{"address":{"type":"string","description":"Stellar address of the wallet"},"memo":{"type":"string","description":"Optional memo for the wallet address"}},"required":["address"]},"maxItems":1}}}],"title":"CreateReceiverRequest"}}},"required":true}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-receiver.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/create-receiver.StatusCodes.json
deleted file mode 100644
index 3539e9f0e..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-receiver.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"201":{"description":"Receiver created successfully","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"f83bb638-dda4-41e6-80c9-d03e6eec2aef"},"phone_number":{"type":"string","example":"+15552368475"},"external_id":{"type":"string","example":"usr12334"},"email":{"type":"string","example":"jdoe@mail.org"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"successful_payments":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"canceled_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"registered_wallets":{"type":"string","example":"1"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"wallets":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"enabled":{"type":"boolean","example":true},"user_managed":{"type":"boolean","example":false}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invited_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"last_message_sent_at":{"type":"string","description":"timestamp when the receiver last received an invitation about this wallet","example":"2023-02-10T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"payments_received":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"canceled_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}}},"title":"ReceiverWallet"}}},"title":"Receiver"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}},"409":{"description":"Conflict - receiver already exists","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object"}}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-receiver.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/create-receiver.api.mdx
deleted file mode 100644
index f02a8be25..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-receiver.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: create-receiver
-title: "Create Receiver"
-description: "Creates a new Receiver. Allows clients to create a single receiver record, which can later be referenced in payments or disbursements."
-sidebar_label: "Create Receiver"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWm1X27gS/is6/tSeGyfOO+TTBhJaWlooodAt5eTI9iTWYkteSQZyOfnv94xkJ85LCWy79+7ds3wgiT3zaGYkzYtGj46mU+X0rp1zCIDdgVTOTcUJQQWSpZoJ7vScQwlUgyKUcLgnBWGV9ONY3CsSxAy4VkQLEhhKQolifBoDkTktfhEyrJD7iAURCSgnMdUgiY80E5DAAwgJ4ySls8SgCUlCpvxMKjAPqk7FESlIikIdhwuxCnGcipNSSRPQqEPv+tHhNAGn53xxr2gcg3aPQ6fiMFQoAhoaDgm/Z0xC6PQmNFawrvhHmoAiOgIURUvmZ/iC0CAQGddER0wRhAClCQ1QaF4l5zkmuY+AG2YNnHJNIqpIIiQQHVFOBAfkYXdQ4FXJFdPR0nirbytoEcpJ/+yY3MKMqECkEKLR4YEGOp7liDkx0yShM7SvSJjWEFa/cafiqCCChDq9R0fPUrQOqsWnznx+Y60BSh+IcIYUgeAauMavNE1jFhjT135TaJvHEpTgcDoxJs9Bhf8bBHrFvtcOPGiQnMZjhvNwB5JNckiz5FKJs6sZKISEhLJ4U8z1CRoiGaFhKEEpIibG3HK5IiZCJlQ7vRxvXnHSSHAY8yzxQe7GP0NqYqk34OeVFZ12C5sTExYC12zCQJKJkBugq6ZZwlIp6WwD9bJETXJ72x20gV1xmIakDLmYqFXr27eb+gDPEpzKkGoYi8nYZ1JHyM1wbXEjQzHBM6BynAiuo02HcjFLAc15t0X20JiAxtlWCdYtmkKgIVwFsszz+eryM0gF8s18Pp9XXrJe740P+WelroAWRtm1Rq0DJoxbLXGS1uHIq4Q+kDqxkK+fv1Zzk+5WaqQhjqlcnwM7IGqTQCJ2w5ymdpUTJF+oYVEK7I3FVzy/wWHow7FVrT43blczHcNGPDu3ztiZr2JpmYF5oFLBlTVBw6vjx6qcBU4ek0OisiAApSZZHOMMPdu7P23+7csJHmiSGqUme03f7zT33DCkLbdVh4675wX7bug1oQMQNChMnrPal4j/qrfb7Uazs9fqtp+xspeMmZL1RrPZMkzf27VL8t9CAb8gWVXIKfLkhhxT/TRjw2s0Xa/hes2LutdrtXvtetXzvK+IoYWm8bhIcnbgIMNy1l7CNaEshvCZHJ5RjvIAXsgj0Yqc8enLmKZMaZAQjjfdxxamumUyizkc0wTTm20e57nuQinQ40CE2wPcYtjPo8EhjmzpmVLZrnX55uBg0OoeH3VOrt53z7ofBsPL0eHVeXdw9vnqsvnx1+bg4tPw8uik9bF/0ep/etv8enJydNJvb9Fvh0U8r+p5xscUrqNv2eZP+uRnWmjXNtrzml6zHrbceui13NZed9/1O+G+GwbtTqs+2d/f24OSTvLHR/Qa+9CA0HMn4HfcVtDy3D2/1XW9vWaH7rW7rTptrJij8H0nTMMyTv24IG0a0n0I226r3aZuq7vXcKkH4NY7XrfTBS8E3yxXW3k8hXTJfIk1QV8ppkz0iUQCKZ3u4Iu0TlWvVruz/DRNq4FIjKOAdFz3xrYYG4cCt+bTWDRlbgh31U2sECAdx4zfjr9XL+yWqabCFOGNt+XUj6FsXF+IGCgv4+SRLVMgxwnldLqLwZRs5Wm3aUYx6crG+/ETCUJp8x5+6b9rfnnXvHzffHf0tvnpw+DodPT+Q+Pjhw9fD0anzcvji87w89mnq9HgqvGu2/rQaJ6fj07KA23PH9YIxttz658UXrI0/GEMxu/YizD2NzFiqvQ4AaXoFMYKF+R2tNWURbMElKZJuiydF+khIha/QqyDjZg2l6S+yPJqPN/p2+Ssez8hHBek40KU//dg/E9cfWZcVZrqbLtN86p4cN4/unAqzvmwP/jVfL45Hl0Mz4cDp+IcnfTfvBkOnJvNKKWs3xrZARZDjSOmtJCzPz4n/0WRF1t322iL2hadk4ukuzbo163hfGXUt9Y6Q67lzBZJ6+RXeWW37Z1jDgCcludtVk4HNCRF9fXT6iSQUjyjjB+ApixWC5cGxDLaOkfS3bM+t3+o25aq8DOnmY6EZP+G8E9X7vlCby7VvBI0ZbkJI9vOLI2ei4W0kMP5KDRZ0XMpRjFQy6uXoNc5FiZsbprwSEifhSHwP99+31FvKUEhZmtTTNToSGT8bz7Nk1zFbTPcKs/wOSiRyQAIX3AtZnl/03yHgk9iFmjiLnMQGkug4YzAA1Na/S/tutjkCoJMMj0zp+8HQCXIfqYjp3d9g0dLCehIYK8kFcaZpRTfOTW5aPYghLwrWiaZjJ2e4yBrgTxCJaycZfxlTErZe9g88uvnm8lmaLbhQtBeNknBDG40OCPvri7Iq+Go0e68zvsbo8HZuGhyVJ2illrFW+vjzCvOaHhW936SZGQ0PHPrnpXN6kwetbgFPn/9IokarZ8pUaP1MyT6lIGcPU8sQ0oWTbXvSVQSwIhUDPw7sps4jvvhfNlbGpZ2sj2GM0XfL/kON0Xo+oFgOV8rHfctH681TZa9qPVeRd5aWGyyG1PyTGzllmcJxVHxoNSAJGcx1ZjJ4OK0Ayprp27Vq3q4kbIkoZivORcRkKcxXo0GZ68Jw56qFiImfsZibU6ThZxSns+h6akm9BaIn8W3y96oFoSSqRRZiqfYEgKW2hasQDelS6Nz0PdC3lY3JvevJ+I3/o1fYA2HQ3IiUuBu7rJTKdDtYeNU42sriuBEi7Q4x1+DqxDKQ/MCaxLTcfbB+n3DGOEP7F/jcpaQCsW0kAxUD+VwyXVetNfyT7fcjHbT3EiuT4Nb4OHNq+IQZMp0lPn2AOQlCK975MK2k3NRZsV+sw3onMxoxfhEUqVlFuhM5goWjYgn57T6As0m0gS3H1GtgNil2z34pKD9w9pEECduEFGp1ZMil+hqWgLUsGyu5Q+e1GeXGm8hTogBMvKHkMZihstrpyYkw5Y/eZ/5IDloULZZr0Em6nQyAnnHgvJJWy4mNiZqhsgVE1flZBUnZgFwZRxsERlSGkRAGsZP2SCPWL1a7f7+vkrNW4OWs6rayfHh8ONo6DaqXjXSSWwcOWYRCeUlYNuzIqVLGCtupnSJ4K9ziyQPDBoedC2N8Zh0nhvlMU+Qrp1lgnSDR7NK48PHR58q+Czj+Rwf2wDXu77BoCIZHnGavKtSxFyMQiFT+dnnthsmZfv8/S6bbDX0Lcw2LuUUMdnBnrwlOLR2cS/KbfveZpq95OgHAaT6SdpyRnx2OsKTDz+/7JKYkytH0nu8BkDvURq8cLS4hGGePTox5dPMVhQWE/cF3cinbk0+lX8pZSOUz0oSridsVhH8X7qcsMry+Giztfl8QZ/fd/gex+Kyk6XGWcDrD/8Bk6sSXQ==
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create Receiver"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/receivers"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Creates a new Receiver. Allows clients to create a single receiver record, which can later be referenced in payments or disbursements.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./create-receiver.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./create-receiver.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./create-receiver.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-receiver.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/create-receiver.mdx
new file mode 100644
index 000000000..3e187253c
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/create-receiver.mdx
@@ -0,0 +1,5 @@
+---
+title: Create Receiver
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml POST /receivers"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-tenant.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/create-tenant.RequestSchema.json
deleted file mode 100644
index 6214ed2d4..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-tenant.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"*/*":{"schema":{"required":["distribution_account_type","name","organization_name","owner_email","owner_first_name","owner_last_name"],"type":"object","properties":{"name":{"type":"string","description":"The tenant name. It should match the pattern `^[a-z-]+$`"},"distribution_account_type":{"type":"string","description":"The distribution account type of the tenant.","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"owner_email":{"type":"string","description":"The owner user e-mail address"},"owner_first_name":{"type":"string","description":"The owner user first name"},"owner_last_name":{"type":"string","description":"The owner user last name"},"organization_name":{"type":"string","description":"The organization name"},"base_url":{"type":"string","description":"The SDP backend server's base URL. If this field is not provided, the SDP will generate one based on the host `BASE_URL` configuration, and the tenant name."},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL. If this field is not provided, the SDP will generate one based on the host `SDP_UI_BASE_URL` configuration, and the tenant name."}},"example":{"name":"redcorp","distribution_account_type":"DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","owner_email":"owner@redcorp.org","owner_first_name":"Owner","owner_last_name":"Last","organization_name":"Red Corp","base_url":"https://redcorp-backend.sdp.org","sdp_ui_base_url":"https://redcorp.sdp.org"}}}},"required":false}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-tenant.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/create-tenant.StatusCodes.json
deleted file mode 100644
index f8f8a6d85..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-tenant.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"201":{"description":"Provision a new tenant","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"name":{"type":"string","description":"The tenant name. It should match the pattern `^[a-z-]+$`.","example":"bluecorp"},"base_url":{"type":"string","description":"The SDP backend server's base URL.","example":"https://bluecorp-backend.sdp.org"},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL.","example":"https://bluecorp.sdp.org"},"status":{"type":"string","enum":["TENANT_CREATED","TENANT_PROVISIONED","TENANT_ACTIVATED","TENANT_DEACTIVATED"]},"distribution_account_address":{"type":"string","description":"The Stellar account address used for distributing funds.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"distribution_account_type":{"type":"string","description":"The Stellar account type used for distributing funds.","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"distribution_account_status":{"type":"string","description":"The status of the distribution account used for distributing funds.","enum":["ACTIVE","PENDING_USER_ACTIVATION"]},"is_default":{"type":"boolean","description":"Boolean flag that shows whether the tenant is the default or not.","default":false},"created_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"deleted_at":{"type":"string","description":"The timestamp when the tenant was (soft) deleted.","format":"date-time","example":"2024-03-27T17:21:51Z"}},"required":["base_url","created_at","distribution_account_address","distribution_account_status","distribution_account_type","id","is_default","name","sdp_ui_base_url","status","updated_at"],"example":{"id":"840dca45-d1df-44cd-83c1-65c04235c25f","name":"redcorp","base_url":"https://redcorp-backend.sdp.org","sdp_ui_base_url":"https://redcorp.sdp.org","status":"TENANT_PROVISIONED","distribution_account":"GCQVDMPOEN3HHJJ64V42KUTONOXN7C6V2PSVPALEVJ7PIYOB6M3DJV7N","is_default":true,"created_at":"2024-03-27T17:21:51.000Z","updated_at":"2024-03-27T17:21:51.000Z"},"title":"Tenant"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-tenant.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/create-tenant.api.mdx
deleted file mode 100644
index 75afaf575..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-tenant.api.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-id: create-tenant
-title: "Create Tenant"
-description: "Create Tenant"
-sidebar_label: "Create Tenant"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNWW132jgW/is6OnvOtrO2eU3o8GkJMFPSBChv7TZlqbCvQRNb8khyKc3hv++RbIOdUJLMpmf3E4m4eu690tVzH4k7rMhK4uYNbnkhZXhuYR6BIIpy1vNwE7cFEAUTYIQpbGEBf8Yg1QX3trh5h13OFDCl//yl9Iv+kO4aQqL/0qZUgKfBPSqVoMtYwy6I6/KYqYXaRoAtzEioP7hYEUa/G8+LbGzDQCwgJDTY/+dTIVXRICDZyNzCBrWJ+fIPcHXEkdAJKQpSB2WsmneZlY6KrbCFPZCuoJF2jpt4sgakTMpIT3BQTyG55nHgoZAod43UGlBElALB0Jd/3xD7uz3/x9++4J11ItUnuc1PR+l0pKch7hu3SVwOtjCwONSL2+mNJ6PexXTSG/QXrXZ7MO1PnPGke3XVGjnd/gxbp006F4tZa3o1+ZFduzdqX3UPZvNdcWeelJeZgGIJAoGtpyHieQKkxLsjO/tcSDPV7NUB7lAVz0XTMw9gD+ryaXC5aXusJZGwiMUTl2zcGaIlcW+BeUiC+Ari7xJpCDQdXTmop+uBSuRTCDxEJWJcoUjwr9QDzzK1ohE2NAjQCpg+1IA4AwPhIc6MyZpLhb5ctMbdxXR09QW5nPl0FScMYCHCvFzVJadBZyK9aBHTxfMTmvZKHpHrJSfCQxc/JZlxZ7iY9hbPzGlnYfhGwiiAA09gAZ7LRYRPHusnn67CoUn++2fqweFidYzimnigh45QXRNfEamOEmcTj8BD7STwwxbhtVKRbJZKqU87LS5Hepn/B9t6f87edrfTK3bgeJ8EEsyIjDiTCdtWyxX9UayEod5VaegNMdik24CtfDMhURRQ16RU+kPqafnOcpriqXesGvd7iyuN2vkSvJrdWP5ateuN87L9xver9lnFX5bfAJQbv/q6xH9uq3AKMS2DGEyhvTBJFJxkW5k5e7D/L3+uT/ov+FVExfLoxqVdbtLtt/qTRXvUbU26HWxlA8PRYNYb9wb9/GCrPenNinad7mFw/qM+nfWkp6WtIAiI2HfpdLLuIR7yucj1crZCfsw8WVyQ39sfW5e1j5e12bva5W9va++vO78Nxu+uq/3r608X40Ft1pucd6fD9x/GnQ/Vy0b9ulobjcZXLyAz7sduFMZjgf8P9cbRdH9cNA8TTmwzEXVUZT0xfVNGXWzhYbff6fV/X0zH3VFWcb1B38RL5cIDn8SByoW35DwAwh7Ed5GMIz8gK6TWxDDIRqLNGtQaRL5ZUZnEn2AjLnSjdAxi6i0jYtcId29B1LEF8rkI9TfYIwpsRY2aPlRmtVyt2+WaXW1MKo1mtdI8q3zSVRdH3suDehDAj0GP0C0NQSoSRnqBWH51NkSiV5L76jVKQZ2/Glahud0cSLmwsI+wyOmyPXWGLd3FClW0vyfdZ+g9dxZ2Z15QM7ol4jf1sueS+pntVTzfrtddz35Tcyv2+ZlbrldrZ271zM/c5JXPTxIQB84/zuTHFsdw5vtZ53o46PZrb99eXp7XZ/Xqu+lk0B987Dfa57PqcDwbtq66s8vGsPevwcX5da1zOWv0i6vZVCKG4hk5VgdOuVz+VFzYE3Y7CyuqTE2l9+VEJNWPqaApI7Fac0G/g/dy2geE4OLhKTLaVgkiH0d4wKksDpcgNEQIUpLVkQaTpJmrtzQM3OcKFdI8RJH5qZcrOeT7M34msMGW4MaCqi1u3tzhCyKp24rVGjdv5ru5hb/ZLvdgBcxO3z3sJfe2dnpE9N8PCCp5L0H7BxP4poBptSuNi1vY4uZJXAt/JUG8x9dhhKDWXB/hiBvFHxEdIi4lrKdPfqL8EhfJsTMTs+zGunyS/b0AIkAkSe73kUT0HTzMpZWuV3KJXQPxQOjLlCKU6dZImJF+lx8m6FV3XD07f60bUjK6QK1hD93C1jlwSgFPH0jtJIHV9TXuDivlF4oMjbtDu1JOYktyRneK3wLbvX5WRNX6S0ZUrb9ERO9jENunhWVMUUQECUH9OKJcACakzPGferpphpT53LhLGS4TkB0ql7GQEAJTaBgQpbut3ntdyCBkEkbDKTtlXadxGBKxvSdCj2O8GneGr7XgIUhxHqBlTANl9Fn+xiuR4igkt4CWcXCLIrLVKGaUoJXgcaQ1nwCXRtR8wb+miirzzkBtuLh1Turk/48QP7PPbKKfSbRLhngEzJY8Fi7otxLN54l8pDINRb+L8ChTvffgDi8hmo2QSxhaAvJ5zPYPKj4PAr7R1SIg4pIqLijIpo7DRjcywSuln7aXWyQ7ShcpEwnzV5kSWFG1jpeOy8PSsxBeN5FJfh/KNivnRBRn12CdFWW+IFKJ2FWxSBPU+6Ie21PnGZn5wnTt/ya1DOKx3DawRJntX85mDUFou2silDwZcs6upARAKSSUldKBk/k8lsZbCEJkgJKLFkQB3+ryejQTFEtt9y5egmCgQDqfNUspEKEc+GMQX6mbf2RIw9RSs2SMbO7bMjWzcEBdYDL/1NeKiLsGVDU8dZCuzVJps9k4xHxr0NKpsnTVa3f7465ddcrOWoWB4UndokPCcsD3FUGBZPb8reCbKkUBoczcs5Knl6TR3+Cs0c8trJ849dDdndbYUxHsdno4IermzVzLB0HJUpP0jb6Jpr3jID7aidS0J8lFI1Mb+vebnZUZtVwXIpX7+oEqLQiT4WCsr/PL9GehkHvmDkE2+icjsjF6ZLf7D0beEAg=
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create Tenant"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/tenants"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Create Tenant
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./create-tenant.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./create-tenant.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-tenant.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/create-tenant.mdx
new file mode 100644
index 000000000..2c0319756
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/create-tenant.mdx
@@ -0,0 +1,5 @@
+---
+title: Create Tenant
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml POST /tenants"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-user.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/create-user.RequestSchema.json
deleted file mode 100644
index f4fd53b02..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-user.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"*/*":{"schema":{"type":"object","properties":{"first_name":{"type":"string"},"last_name":{"type":"string"},"roles":{"type":"array","items":{"type":"string"}},"email":{"type":"string"}},"example":{"first_name":"John","last_name":"Doe","roles":["business"],"email":"email@email.com"}}}},"required":false}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-user.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/create-user.StatusCodes.json
deleted file mode 100644
index c48054463..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-user.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"201":{"description":"Created","content":{"application/json":{"schema":{"required":["email","first_name","id","is_active","last_name","roles"],"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"first_name":{"type":"string","example":"John"},"last_name":{"type":"string","example":"Doe"},"email":{"type":"string"},"roles":{"type":"array","items":{"type":"string"}},"is_active":{"type":"boolean"}},"example":[{"id":"7a4c6555-1f73-49b3-a211-f95bd2b8ec90","first_name":"John","last_name":"Doe","email":"email@email.com","roles":["developer"],"is_active":true},{"id":"5f4df1dd-c84f-482a-84ad-541ffd46e75a","first_name":"Jane","last_name":"Doe","email":"email@email.com","roles":["financial_controller"],"is_active":false}],"title":"User"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-user.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/create-user.api.mdx
deleted file mode 100644
index 42df31ef0..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-user.api.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-id: create-user
-title: "Create User"
-description: "This endpoint creates a new SDP user as the result of an SDP owner adding their information in the UI. It also handles sending the invite email."
-sidebar_label: "Create User"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNWEtv2zgQ/isET00hWbZjx4lPmzZZbLqLNgsn2IMbBCNpZLGWSJWk7HgN//fFUFIs5+E03RboJVI0r28enBl6zS3MDB9P+bVBbfiNx2M0kRaFFUryMb9KhWEo40IJaVmkESwaBkzikk3OLllpUDMwzKbINJoys0wlDKQjqqUkahwLOSMOoZmQidI5kHYmpBO7vuiwC8sgM4qlIOMMDTMoGyEm5EJYZJiDyDrc46pA7RRcxHzM3ztIhJ57XOPXEo19p+IVH695pKRFaen1bfCWHiZKMQd6s6sC+Zir8AtGlnu80KTXCjRETYQ29lZCji1eY7WQM77xeAb7qFpllZaaAlrDintcWMzNExIbjzvnniHdQV5k+BAV/6BSyXeg8DOF/N78lIelERKNy2ptoHr+VsUyUjnfbMgGxU1ojPk4gcyg+2IKJU3lR7/bo8duZVSBj7nXDjMURSYil53giyG+dsy3ZqY1IK/tk8cFqRPmFiIrFrjjXePXjfdC6kT8OI6tKPLe6PAoxPjQH4UnfX8wOur6x0nS94e9JOweI3ZHJwllcV8JtPW5POyviTY75WhPwr+rerYR25JDpTIEuVtC0yo8fASD6Gg4HPq9ZHToD07CQx/6vZ6fnAzDuB8eY3TS3c3Nnnp7rrRalRjjAjNKEqWvhdbqEjdeDWqYDOKkF8d+dDxI/MFxH/zjAcT+cNBLknhwhKMhPAIFEr8XVCIkyEhAdksFrFWWPcJXnQYqOWFd9lyfqc7M4KlDcS2htKnS4t/XnYz9JY1aK/1kseCd1WBe1mAs2LLNJ8s8JFc8nqMxMHuqk20etJ8aBv+oLNtxc4uisTPo9lqaH0r8TMVVag4fp+Z3pUMRxyh/fl6e9m4L4BsYnB8Go1ILu3IH9x2CRn1a2pSPpzdUlHd+pGKcofTrueeHKl759Tmg9yqEKI1Q0jgtc1zx8V5Jjy8gK+81kKEcbaroiBbKuCgAgeBB6XYGwqkX9EYGSk3Hzok18CcUzipibSe2Ha4QfyJh3U3YaZ3XallIEWLUjDIHQtJuUC8ZH/65Ym/OJ/3h0QFTuv56y04vL9gcV7Qw1AHZ0UcNlYxUaukcTM4ve90fhIxNzi/9XrfCVvnM1lbNUW4OXoWoP/iRiPqDH4Ho7xL16ttgOVZWgIYc7fOIWgAcpMbwVxKvJpxMlDNX9+GJxSwDzc6ECUttMEdp2WUGlrZLyj2VMWpTwRh1uh2aZ6bMc9Art9Yi26/jzeTs8oAJ2nWtUhkLS5FZlijNlJ6BrENkmFUshzmysMzmrIAVaXFfgc20KgtahzVGohCOoBao3VbbWJdol0rPO49i9+tB/Cw/S3cfIJOSqQKlb1SpI2SFVtQhmU3BErmCoiSzyql/Qp3HQMaOQL2IRSBZiCxRpYydYEr/ZJlaUrVoLJQRVmmBZkw4fDY1lb6gfvpxK0h+UQfJDyGao4xv3qTWFmYcBDNh0zKkZSB4lYaDMXPO30NZNeVc3X5qNueVkIkGY3UZ2VLXDlJe7Es57bzCs0S7KfZ/XGtUvOTbEkPW8H63NylmuR+loK3ZC7nFF1iNGOQgZFB/2OvPS278gVnOnCKHP8YiU6vmmrn/rNFVasb+LEPUEi2azmfqUhZ1bj4lE9QLEVFfatyqYXaUngWOyVeJb2o2j2ciQmnc8G8abwFRiqzv+lQ1Q0nXOAiWy2UHHNVpq0VN8NfF+/OPk3O/3+l2Uptnrk/SgM5BthRX1zRWX5B3Wkzrgvwr3vPr0WLxzgZFBsLdslxo1vUGMuVl86tFSpvJeMrX6xAMXutss6HP1QQZT29oq9ECQncLutl4zVDb7kTvq1j4V2R2uwTRDwd0RamYTqMIC9siP1ofd/aly0+TK+5Vi9R4zXMVk4yGJd1DYOkWJY/Do1k6d7O0fiGIDUmuWrYfDusKIv0lwE+KrNfVpN5s7vkr0rMSdZwabsrCzWaz+Q/VOEzJ
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create User"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/users"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint creates a new SDP user as the result of an SDP owner adding their information in the UI. It also handles sending the invite email.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./create-user.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./create-user.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-user.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/create-user.mdx
new file mode 100644
index 000000000..50483481c
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/create-user.mdx
@@ -0,0 +1,5 @@
+---
+title: Create User
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml POST /users"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-wallet.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/create-wallet.RequestSchema.json
deleted file mode 100644
index 984d36be8..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-wallet.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"application/json":{"schema":{"type":"object","required":["name","homepage","deep_link_schema","sep_10_client_domain"],"properties":{"name":{"type":"string","description":"Human-readable name of the wallet provider"},"homepage":{"type":"string","description":"Homepage URL of the wallet provider"},"deep_link_schema":{"type":"string","description":"Deep link schema for the wallet application"},"sep_10_client_domain":{"type":"string","description":"SEP-10 client domain for authentication"},"enabled":{"type":"boolean","description":"Whether the wallet is enabled for use","default":true},"assets":{"type":"array","description":"Array of asset references supported by this wallet","items":{"oneOf":[{"type":"object","description":"Asset reference by ID","properties":{"id":{"type":"string","description":"Asset ID"}},"required":["id"]},{"type":"object","description":"Classic asset reference","properties":{"type":{"type":"string","enum":["classic"]},"code":{"type":"string","description":"Asset code"},"issuer":{"type":"string","description":"Asset issuer address"}},"required":["type","code","issuer"]},{"type":"object","description":"Native XLM asset reference","properties":{"type":{"type":"string","enum":["native"]}},"required":["type"]}]}},"assets_ids":{"type":"array","description":"Legacy: Array of asset IDs (cannot be used with assets field)\n","items":{"type":"string"}}},"title":"CreateWalletRequest"}}},"required":true}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-wallet.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/create-wallet.StatusCodes.json
deleted file mode 100644
index 90e5e1f01..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-wallet.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"201":{"description":"Wallet created successfully","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"created_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"}},"title":"Wallet"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"409":{"description":"Conflict - wallet name, homepage, or deep link schema already exists","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object"}}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-wallet.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/create-wallet.api.mdx
deleted file mode 100644
index b28f26a9c..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-wallet.api.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-id: create-wallet
-title: "Create Wallet"
-description: "Creates a new wallet provider that can be used for disbursements. The wallet must be configured with supported assets and proper authentication domains."
-sidebar_label: "Create Wallet"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNWF1z27YS/SsYPMUzoiQrdtzyzYndqds0cSPn5s5VNB6QXImoSIDBhxRVw/9+ZwFQpCTHctpkWj/YNLl7cHax2F3shho21zSe0A+sKMBoOu3RDHSqeGW4FDSmrxQwA5owImBFVk6MVEoueQaKmJwZkjJBEiBWQ0ZmUpGM68QqDSUIo/vkLodGr7TaoGgqxYzPrYKMrLjJibZVJZWBjDCtwWjCRIaLVKAIsyYHYXjKkBHJZMm40H3ao/jZvbzJtkS9HbRHFXyyoM1Lma1pvKGpFAaEwUdWVUVAG/yh0cgN1WkOJcMns66AxlQmf0Da4HAFGTpJsBJoj+ayhIrN8TEDqO4LLhb3AaFHNVT3p8P7tOAgzL2ni2715hgOGpdxUO1y2igu5nTf+T/bkolIActYUgBBJSJnxLQebXaC1h1ex3GDJHn/7vUjgAfWHQW+AqgIahCv4eKhg97xPS7woK+OLjK+vo1Oh8RrhYBwC+2GCi4AAh2XdTATKQtg4gD0Qw4mhx2yXJOg79Ct9js+Y7YwNDbKQt2jPmA7CzCl2PoA/hLfoqudPFEwAwUiBd2J/WRNTM51WJ72KDdQOmgp4O2MxpPD8NxbZRccEW+u6H7s8ey4jz3SzRWt690zwDM6rXvHiLwqmNY83bf2gIpHOSQDwpa4WupxcEmayuwJoe2JO9m6R7nWFtRTtbw0YVmmQOsD0x1E4LGFfoIz3jDDl0D++/q3v+0P4aDo9EFq09q99xF5z7PjUfka5ixdx2QvOm+uNHmWMiGk2SZ2l6dDdp5xKLKTj6IboruMayRiuClgLzO/82nZC7QWhMOkQFdSaO+L0fAU/+wdU380UweZEW3TFLSe2aJYu635i1n+KQcEPrOycgads4z9CNl5dHZ+zqKzix9GERsCRKcvhhcvLmCYQXKK0felJN8i/YcniglDLrXm6JXHk3irlxtT6XgwWHp9VlX9VJZfk1JbLFbxKINl/xDrKfn/GKeBziqER7ywa/fMPIQ0k6rELzRjBiLDXa1t4UfD0fNoeBE9P70bDePzYXx23n9x9sP/ENhW2fcA7sRw6CtqF7dnw+FhZL5kGWmi+5tFIigln5C+rsAwXmjCEmmNK2FeESvgZ6OYPrpS7X/QtgdO3XuBpVUq/idk3924p5Om2jBju3LClonvXUrQ+sFjFOzc7v+WB30jDdmxs6XRLHQ2PO1A72tsXfj80IU/SZXwLAPx/f33BfNaBg3NHw9pvpJiVvDUkKjpgjCJ9UiTlnoEG/z9Lo8V2KOuCXzm2uh/MkK2cawhtYqbteuaXgJToC6tyWk8mdZT3EOTS7w2VNKd14rhNzpYhXsQAqglKO30rSpoTCkqNrhjNMGz7KK3Bbfiv8IDfWCIFn+ZyYHhLQq9xbjgYk6YIOOrW/LLhzvy7Ho8On9xgg73b+/J5e0NWcAaLz++tuziYT3GRTwsuml8fXs6/EbMSOi7HTdvM9kYuQBRn3wVo9HZt2Q0OvsWjH63oNZPo+VEScUUK8F8mVGHgKPULPwJ1V1twdPwrr2mXrdHNuhts33bFHQrwH5xbr893AR028lwLcK+q73DTHzr0x6zrSuaPrzpwluopsN+QCk0q3hquj3ppBHFpp6LmXQuD3V2bKAomCJXnRkCuS2YwSKO8U97FI+l34qL/rA/RHttWTK1pjHFYcPjGM/GV7cneLdjxEhZkMTywrgLnlRzJkKYaGIkKdkCSGKLBanY2k0z8C0jcyVthe2ygpRX3H2Qy3B5bFYXYFZSLfoH8fPvo/hRfBR3ePPEJQWRFYhIS6tSwHEA5lU/6OE6UJGCGFk1k4M9uJ6b3uAHjJVmOjSTVmROMcd/ikKu8MQoqKTmRioOOkYeEZlojzcIf6PuPCmqgpOihKULENn0WdN3zrnJbeJ7zq9BOImJM35LZd0cae3IBjFnFRczxbRRNjVWBQObEceje9r/CstmylXPv2NaA3HMthUkpJH9y9bkUJRRmjNl9KOUO3IDowAGmJYG4cWj9hwz42coSuKA/AASqkKuMbyOWkKsRrlfbQJKgAHdd9daA6rUb2djUEuedi83gWZfqvnACUVyFukg1qMFT0Hobg6/rFiaAxm5POX7CMSKB4PVatVn7qtDC6p68Prm1fWb8XU06g/7uSkLVyuwTSmZ6AD7WzXZDjx3kkxn4PlvnuCGQmHgsxlUBRapOjhpEzqyCV21k+kce7V4QjebhGl4r4q6xte+osaTaY8umeJY2lyb12uKPBa2Bax9e4teie78KGfJCusr/V6PilXMa1ymKVTmUdluO3n7dnxHezQJY+fSV0vFVjhKZivsInFw7fI3Crh3G1owMbe+wHtMN8g5aEcWrh0JD51xIBPrDsP9fscbgr87xXlXZbPxzU5db+X9py9qBNc20rh107qu/w+xJ35j
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create Wallet"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/wallets"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Creates a new wallet provider that can be used for disbursements. The wallet must be configured with supported assets and proper authentication domains.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./create-wallet.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./create-wallet.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-wallet.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/create-wallet.mdx
new file mode 100644
index 000000000..2379b1cd3
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/create-wallet.mdx
@@ -0,0 +1,5 @@
+---
+title: Create Wallet
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml POST /wallets"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/default-tenant.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/default-tenant.RequestSchema.json
deleted file mode 100644
index 777c7889f..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/default-tenant.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"*/*":{"schema":{"required":["id"],"type":"object","properties":{"id":{"type":"string","description":"The tenant id."}},"example":{"id":"1736bed3-7b92-4760-8ff2-51fb08ee079f"}}}},"required":false}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/default-tenant.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/default-tenant.StatusCodes.json
deleted file mode 100644
index bddc27e7b..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/default-tenant.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"201":{"description":"Default tenant details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"name":{"type":"string","description":"The tenant name. It should match the pattern `^[a-z-]+$`.","example":"bluecorp"},"base_url":{"type":"string","description":"The SDP backend server's base URL.","example":"https://bluecorp-backend.sdp.org"},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL.","example":"https://bluecorp.sdp.org"},"status":{"type":"string","enum":["TENANT_CREATED","TENANT_PROVISIONED","TENANT_ACTIVATED","TENANT_DEACTIVATED"]},"distribution_account_address":{"type":"string","description":"The Stellar account address used for distributing funds.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"distribution_account_type":{"type":"string","description":"The Stellar account type used for distributing funds.","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"distribution_account_status":{"type":"string","description":"The status of the distribution account used for distributing funds.","enum":["ACTIVE","PENDING_USER_ACTIVATION"]},"is_default":{"type":"boolean","description":"Boolean flag that shows whether the tenant is the default or not.","default":false},"created_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"deleted_at":{"type":"string","description":"The timestamp when the tenant was (soft) deleted.","format":"date-time","example":"2024-03-27T17:21:51Z"}},"required":["base_url","created_at","distribution_account_address","distribution_account_status","distribution_account_type","id","is_default","name","sdp_ui_base_url","status","updated_at"],"example":{"id":"840dca45-d1df-44cd-83c1-65c04235c25f","name":"redcorp","base_url":"https://redcorp-backend.sdp.org","sdp_ui_base_url":"https://redcorp.sdp.org","status":"TENANT_PROVISIONED","distribution_account":"GCQVDMPOEN3HHJJ64V42KUTONOXN7C6V2PSVPALEVJ7PIYOB6M3DJV7N","is_default":true,"created_at":"2024-03-27T17:21:51.000Z","updated_at":"2024-03-27T17:21:51.000Z"},"title":"Tenant"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/default-tenant.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/default-tenant.api.mdx
deleted file mode 100644
index c406524f0..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/default-tenant.api.mdx
+++ /dev/null
@@ -1,73 +0,0 @@
----
-id: default-tenant
-title: "Default Tenant"
-description: "Sets the tenant specified in the request body as the default one, resolving all the incoming API request to that tenant when the env `SINGLE_TENANT_MODE` is set to true. Once set, the default tenant can be overwritten but never unset, although it is only effective when `SINGLE_TENANT_MODE` is set to true."
-sidebar_label: "Default Tenant"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWW1zGjkS/iuqqau6ZJcBDNhk+YYNSXBsIAaTbBwf0Yx6GK1npFlJAyEu/vtVa2Z4sfFLstmr+7BfDJZa3U+3Wq1Hza1j6Ew7rSunzWIunOuSw0D7iieGS+G0nBEYTUwIxICgwhCdgM8DDoxwYccV/JmCNsSTbEloJssgoGlkiBRQIgq0jOZczAiNIjvNhS9jHGgPe+v1RhITUlPYWYSQ6QcxJ19Gvf6bs+503O23++Pp+aDT/UK4JhqydSqFMhkIH3CktAMhV+dTQTwgcg5qobgxIIiXGiJgDoqkwi6jkQllOgsJN6hcimhJIAjAN3wOGaDnAPksPovOrnWuSaohSCMSSEUYzCGSSQzCkCRVidSgiVQbl0edYb6EEW9JKNFczCIgUs2o4N8obk2ZjEOuMaRykQV9exbB6Bue5Nu1xGBvbSIXBB1froNPBSOax0mEW6vXIDSYNCEyAWW10ihaIiAFsZwXKgUAIzIgiZJzznB0wSPmU8XI+GxEfFCGB9ynBrT1Pk4jw91iW6QI+CzN1OvyZ+GUnLW5HnNaTh7JsZV3Sk6O+FiypdO6dXwpDAiDX3+p/IIf2g8hpvgNRbkChtnNGaa2WSbgtBzp/QE+KksUGjMcNMpzhn9zGW0UFzPn7nEYbwWRlZ3VquTAVxonERQanINm/cgDVneb3m81t9E8qrqvgqDmHh4EXvUVQLX5W+CsVrh0gzCgkQY7ohMpdAaoVj3Aj10Ed1KLgaE80k5pOxQ0SSIMOZei8ofGZdtx+ZEorJ18pnslR9AYviueuKBMeoboUKYRIzE1fmhTLKHGgBLky3+uqPvNvf71X1/KO5i8KAVfqgTtelTDNFXR82xjlnvUvwE8AKDmoP6tCaoglxdnu0ZCYxLdqlQKY26+rqxZUpZqhsY1S6Ypn34/hstehVEdehLPzfGz7O/YNdSkeu/GiTTGA5BXrJOLbnvc7TilYmB4MZj0Rr1Bf3uwfTLuTXblOt3N4PWq5DCOJrwU/ZhS35epMFPKmAK9F8cetw1EEVUkX0zyxVnZs3VybULMSJAKpncD8ubkY/u0/vG0PnlXP339tv7+vPN6MHp3Xuufn386Hg3qk974qHs5fP9h1PlQO202zmv1i4vRmfMQ/Azzj2DHFU8Cz3ei0xuNL3rHl+PeoD9tn5wMLvvj8mjcPTtrX5S7/YlTelykczydtC/Pxg/JnfQuTs66G7EHd+vhpLnvcCaLdd5erlvq1jF4pvs2jbpOyRl2+51e/830ctS9KDKuN+hbvFxP8wt8C54nZQRU3MN3nI2TIKKzjEPoEC/FRQgmBLVz8d3hJ4oIacpWY26tKMS+AmqATanZF6BAqhhnHEYNuIbHsJOZtWqt4Vbrbq05Pmi2agetw4NPmHVpwn6+UgYRPKx0T7nlMWhD42RDOArORTV5oWVgXpJcaflHYe1cbleborwT2CeqyONp+9gZLuEttpNF+X10v0Kva+fO7lzfv9ZfNarMp41Dlx2wwG00fOa+qvsH7tGhX23U6od+7TAozLQcBcxeSNv30bqC55P3LpA998fdNduy+fHdX8n3BcfWzPeTzvlw0O3X3749PT1qTBq1d5fjQX/wsd88OZrUhqPJsH3WnZw2h73fB8dH5/XO6aTZ341mC4nu7hnZlwflarX6aTewj8itSo7hxuZUzvYyktTYx4IuBU1NKBX/BuzncR9QSqr7p8iSPKOoflrDvZoq0tgDhSpi0JrO9lwwmZtb+ZbDcPrSkB03NygKO43qwZbmuyv+TsXZ1tTvb81rqTzOGIi/f1/2e7cB8AwB64cGP1XcLJ3W1a1zTDX326kJndbV9eq65Hx1fclgBsLNHx8uvnXd/KTj9yyCIDS+YqySG1g6rUdXlpw5jdK1BjQUgwkl1ppEahsEiiCcSlaedSU/fvnjCUuAZayZxaxcWD2FOyMMbxbBY6AKVObVOow04e9gee+SaOf7nL0kQ6AMFL7UDOXCPuOFpaynH8bkRXdUOzx6iRdpNjq1b/obWJY3tXBHHxYSNJKpxXMx6g4Pqj8JGRl1h+5BNcOW+UxujbwBsXr5XYhqjZ+JqNb4GYjep6CWz4NlRUlCFY3BPIxoC4CFVBj+E5fb08NFIK25vDIXxLfDtZcqDbaJMYyoQZaAe495DUpnMJrlarmKeZrGMVXLO+R5v44Xo87wJRI1SoyUEfFSHhnLK7cbHBo7HDG9AeKl0Q1J6BK12FFKZkpi2yIgCnyecDuBnZ+sr5FbF2AWUt2UH+X3/x8QsaNkuz1oUmA/RrhapsoH7LpgxcxoL9c5FNsASgq2fkddyXZ7cAKLU9EZC2QqmF0Y4j/YVsJsUZBIzY1UHHQLcbjkSmf6Kvmny7aC5CZ5kApyc/2iYDAzbsLUK/syrnyXhpetrNW1hrIs0jkj88XzHb3iIlBUG5X6JlW5g7gv5qk9LX+HZ4Gyt9pfca1Q8ZRvC/BIIfvD3oQQxa4fUmX0o5C35CpGAVRiykUlH3jUn6fceAtRTKyivAGaRHLdk3z8rKXY+yTvUg+UAAN5j9CAivUgGIGac3+7OZLDRIpcsUKuDFydi5WciPsgtCUDReFNqB8Cqdk6taHcrUplsViUqZ212vKlunLWO+n2R123Vq6WQxNHtk7ijR1TsaW46NOtO5c7VWarc/lPi/2fFvv/uMWekwcDX00liSgXtjmR9Ssz0nnl5KRz0xspaOd1yQmRn7aunNtbfKleqmi1wuGMNrSurpHbKk49pAxX2M/JmcyGGZ9k2e+Os+d6QYWxh78qFUJt34fEbE3fe0PssObhYIRNMS//aSCWzL7E6QJ/NqALy45Xq/8CnFNOnA==
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Default Tenant"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/tenants/default-tenant"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Sets the tenant specified in the request body as the default one, resolving all the incoming API request to that tenant when the env `SINGLE_TENANT_MODE` is set to true. Once set, the default tenant can be overwritten but never unset, although it is only effective when `SINGLE_TENANT_MODE` is set to true.
-
-Default tenant is useful for development purposes or when the SDP is used by a single organization. This allows the organization to skip specifying the tenant in every request and simplifies the SDP setup operationally by removing the need of providing wildcard TLS certificates for multi-tenant configurations.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./default-tenant.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./default-tenant.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/default-tenant.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/default-tenant.mdx
new file mode 100644
index 000000000..740819730
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/default-tenant.mdx
@@ -0,0 +1,5 @@
+---
+title: Default Tenant
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml POST /tenants/default-tenant"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement.ParamsDetails.json
deleted file mode 100644
index d083a4ef5..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"ID of the `Disbursement`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement.StatusCodes.json
deleted file mode 100644
index ac3e5bdc7..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Deleted Disbursement details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","example":"619da857-8725-4c58-933d-c120a458e0f5"},"name":{"type":"string","description":"The name of the disbursement","example":"Disbursement Name"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: {{.OrganizationName}} which is the Organization Name configured and {{.RegistrationLink}} which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"created_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"}},"title":"Wallet"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED","CANCELED"],"title":"DisbursementStatus"},"source_wallet_id":{"type":"string","description":"ID of the distribution account the disbursement is funded from.","example":"4c379f5e-09b5-4472-a286-b84e249a1512"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"status_history":{"type":"array","items":{"type":"object","properties":{"user_id":{"type":"string","example":"3f351b9e-ed0f-40fa-a314-14757b42dab1"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED","CANCELED"],"title":"DisbursementStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementStatusHistoryEntry"},"title":"DisbursementStatusHistory"},"file_name":{"type":"string","example":"disbursement-feb-03-2023.csv"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"total_payments":{"type":"integer","description":"Total number of payments","example":10},"total_payments_sent":{"type":"integer","description":"Total number of successful payments","example":8},"total_payments_failed":{"type":"integer","description":"Total number of failed payments","example":1},"total_payments_remaining":{"type":"integer","description":"Total number of remaining payments","example":1},"amount_disbursed":{"type":"string","description":"The total amount disbursed so far","example":"800.00"},"total_amount":{"type":"string","description":"The total amount to be disbursed","example":"1000.00"},"average_amount":{"type":"string","description":"The average amount per payment","example":"100.00"}},"title":"Disbursement"}}}},"400":{"description":"Bad Request, Cannot delete a disbursement that has started","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement.api.mdx
deleted file mode 100644
index f273a52ff..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: delete-a-disbursement
-title: "Deletes a Draft Disbursement"
-description: "Deletes a Disbursement in Draft or Ready Status by `id`."
-sidebar_label: "Deletes a Draft Disbursement"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWW132rgS/is6+rLtORgMmJDwjQZym7uUZIG2p9vmuLI1Bm1syZXkZFmO//s9km1iAnlpm917z+2HJrFmnnnRaGY02mBNlgoPPuMRU0EmFSTAtcJXDUxBhZKlmgmOB3gEMWhQiKA6IWIcjSSJNBISzYDQNZprojOFgjX6yujXJm5gkYIkBuacboGGdRTcwCmRJAEN0uiywZwkgAeYUdzAzIhPiV7h+zqdj5CIkF4B+lqHs0IlfMuYBIoHWmbQwEqvYwOpWJLGgBsY/kxjQQEPIhIrQxCuICF4sMF6nVpKLRlf4jy/MmgqFVyBMusd1zU/DvmH7nqHgiYsVriBQ8G1sXSwwSRNYxZah7T+UIZ5sy9cBH9AaB0jjfs0K0Qzuq/gfa8sVoAyzr5lgBgFrlnEQFaOortuhz+JdccAH7VPKDnu9Z3jfqfneGHv2DnpdqkTtjsu8XrH4EY9nDfKnXmODobySbE77poa7Nx4OwR2A9KXsGRKF8HjJ6AUWYKvIUljop+pRZgpLRJUMaFMAUVaIAWcIsZvmLboynyr5KomMqxfKUQki/VXVIpGTPFfNJKgM8mBNtE5t9aVy78oVG4zYvoXhVKhFAtiMNCEUksaiTgWt4wv7zS6IZKRIAY1QJtN80IuCWd/WaWMP/Ic3a5YuEJMWYD6unWYkRmxZSaBIsKpwZjV3DZh/Po+Rsz4NVoCN8cSqDmq89Hl1ilaWKLKGegV4ygkCpBeMWUguNAolaDK81/zQKMwnGRaJESzkMTxGpE0BU6NdtrSAqevmztB8ElkaEVuABGUkrUNhVvCtPFSJCRaiwxFUiSH3dNEpzELrx+w2+6q+QqyWYRWLaLMbpFQ+0UU7UcT8CwxqXH8bng+wQ18+fZiOvan79+9Gc9wo/jsD6cj/+NwMhkv/OFoNBvP5/coD1FcNbBm2hpfV/q0UGhh9Mgb+JbEMegfzQp3/u0RSk6A9hyv1yOO1z/uOMQFcNpHbv+oDy6FoP3Y2b5D+sACSbhGQ6WY0oZnJRJIyfIJvpXWqRq0WjcFP0nTZigSw68g9duuH8YMuPapSAjjj2ORlDkUbpr7WBQg9U1w+w8l86d1aimaGniDF0owB8Qn+hBSJGRiVjAlGhzNEtiB77idruP2nW570XEHPXfg9ZpH3vHvBjhL6d8BnN9F1ccidPIGJkq9RAxFEYHQC7qOdxS4jkcDzyFe6DlHYbfnHru9ft+19SG0NfWpzDw0SiFLWxfyfj46NSBMqQzkc2EKapNiJSi1A/ivN29GXv/87Gjy8df+Zf/daPxhfvpx1h9dvv/4oTv91B0tfht/OJt40+HCG/72tvv7ZHI2GfZeaPc7jttdtM0ODXrtl9r5fVBa9B4/A3pUgvZK0PxQLZ1riGMikQ0ptA2kKubsbtgzbVvAxzLqaDY8W+AGno2Ho0+4geeL4WwxHpnMOXw/t7+cXry7nIyLj6fD6el4Mh7V82a9cyh6TitaZDIEv8ic/nPapbsmkpo8zILMllYShiLjeq97MQUwymw9MzVpt5B5Ybd/EvXAcU+CnuN5/Y5DOsdHTnDsQcc7Ie1eu2O0vAHJorIH9CMG8eHDVzlruBj7F2f+m/PZ4i1u4E/j4cx/dzG1f1yeT3EDT4eL84vpcOKfj6r6VHPVh5q4Myttu0n+iikt5Lomn0hJ1qbv1pCopxNHpkA+4Og7x3Sjbq8dnIAD1I0cz42IQ7ptz2l7/V4/8DqUFBXovxg55mAoTZL0xQ5m/pjIt4Xfx1zLNX4OpSGKWAz+01W6Hq9OBIHjdh2jYjNUL1XX/qHMpoUmsV82hfW4YFzDEuR+y28YEM+SoLjzbFlr0truHrKvysvZd8KrLAxBqSiLD0o63hcUERYD/QFRBeNhg/bFSDCNlPH990va8j4ojCQmN/pVnD3zUmpVRAXvNqdSpASKiNwJh2PXbbruXQAUPD8gRQsU3OVvuiOk7W6lkBuQ5mr5PXJKnkpSCrJy130pVsgDRxznuVnyDo0U3hCKZvAtA6Ub6JRwc+8qSj0iuzVJr4hGK6KQ0kRqa+cLDRxASvGMRmxUDDoQCURW3vIsY25coSV5uo7kxT/jiva+K95zkumVkOyvf8C45yu9X6+KU2QgyivxoYGStXMbIls98FRotGPnnRqVIM9t16Dvc2xd2N134ZmQAaMU+N/vvwfMu9OgUtPbV9NYdCYy/n++zVFp4qEd9uo7PIOipbVTl4KrOikKwkwyvbYT0zdAJMhhpld48PnKzCwT0CthJq5FzrBDVrOKW/XcoVobRnNs0ORNNX7NZIwHGBuUSsjcOLvwRl3UXdeYsl9hvX9DK4OzmFetgFCQdkpWVhjC7ezp3x8X6NV43ukdvTaT5OKrj4aX5+ga1qbJLifCO3jVcLiANbsxH1+23RfSDM3Hl07bLXQrbEYbLa6B56+/S6OO95IadbyX0Oi3DOT6eWpZUrQd0D+kUU0Bq1Il+Jtht/WP8UhYcWUdrK6TOzPgy5ho0yyavcf2pqQKNfpNt+maOM2ShJgLy86V9DDGq/no8rW5sRGkhYhRkLFY25miqM0R7ew3IdeAgiy+3jY9dmyLllJkadEVhSxldkGYsaiuSeegb4W8bh5sFP63VPzCv/BFOcglHIkUuFNmmFQKk/2KboKpUhXBkRZpdUe+B9ewI2ezYGY5KCTc9Fs2TVnGnYm3hFQopoVkoAZGDwd9VgVeq/zp7Fxd0tJJTkDCa+D06lU1s1syvcqCYl73PQivB8gav1VlXYVzMRkvyaxVjEeSKC2zUGeyNNDsi35qT5vfYVkkbY37GdMqiKdsu4UAVbQ/bM0K4sQJV0Rq9ajKNbqWlgAtc6VolR8etecpM95CnCALZPWnkMZibR9UnjxrmTJ0v2YBSG4eM5tfTJbSIBN1Ec1B3rCwPhgu1WwKuWxZIkdEjirJGjhmIXBlK3uVeFMSrgB1bJ4qaqjBGrRat7e3TWJXLVrJqlqT89PxdD52Ok23udJJbPNkKpROCK8B1x5f7WPrvcfTnZyzuWubfubRtqwJGv7UrTQ2Q/m8tGlT9hGfd+YM5o44YNTMWVZCabO82QREwXsZ57n5XBSCweerBq6evGyzQZkyv9PtS+yD5ryalY+6r9FjT78HVa9qHDcF7obEmfkLN/A1rIuH5vzKvGYUVdKoVSwMwxBSXWPZa0R3Wq3R2AyecAOTvdJ6bUtr+YsRcFCj+7W70ML8nzceYNlsisKd51v6YulBjtLKrfHGiDzP/wPLAvXO
-sidebar_class_name: "delete api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Deletes a Draft Disbursement"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"delete"}
-  path={"/disbursements/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Deletes a Disbursement in Draft or Ready Status by `id`.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./delete-a-disbursement.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./delete-a-disbursement.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./delete-a-disbursement.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement.mdx
new file mode 100644
index 000000000..1d60bea0d
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement.mdx
@@ -0,0 +1,5 @@
+---
+title: Deletes a Draft Disbursement
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml DELETE /disbursements/{id}"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/delete-api-key.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/delete-api-key.ParamsDetails.json
deleted file mode 100644
index cba9874e7..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/delete-api-key.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"The unique identifier of the API key to delete","required":true,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/delete-api-key.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/delete-api-key.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/delete-api-key.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/delete-api-key.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/delete-api-key.StatusCodes.json
deleted file mode 100644
index 7b707f33b..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/delete-api-key.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"204":{"description":"API key deleted successfully"},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/delete-api-key.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/delete-api-key.api.mdx
deleted file mode 100644
index 6d25a4cdb..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/delete-api-key.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: delete-api-key
-title: "Delete API Key"
-description: "Permanently deletes an API key. This action cannot be undone. Once deleted, the API key will no longer be able to authenticate API requests."
-sidebar_label: "Delete API Key"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdV99v2zYQ/lcIPiWAbDmZtwF6yxYXy1q0Xp1iD2kwUNLZYk2R6vEUVzP0vw9HSY6TOMmydUCxF/8Q7777viN5d9pKUisvkyt5Nr8Qr6Hx8jqSOfgMdUXaWZnIOWCpLFgyjcjBAIEXygp2WEMzFpeF9kJlbC0yZa0jkYKobe4sjMU7m0HvlkeCChgcxUYbI6wTxtkVIPuo1IAgJ1RNBVjSmaLOHOFzDZ78WEbSVYCKg13kMpHnAflsfvEaGhnJSqEqgQBZ01ZaVYJMpM5lJDVrqRQV8r7Ay4Lp6s81CJ1z3KUGFG55hy25XoWMJNPRCLlMCGuIpM8KKJVMtpKaigN6Qm1Xsm2v2dhXznrwvH46mfLX3fhDiD5LwtdZBt4va2Ma2UZyOjl56PTBcpYc6j+B1WXOElhiO1VVhlOnnY0/eTbePmTo0k+QEWcMOaGkO36A6PCAkEjCF0Lln0fwpKjet7N1mQIyRAneqxUcylPbhhCqrAzs8ZBvHYk7Om9pDIGmk5M96PsePfR08t3DFL5ymOo8B/vf5+8RebcMBpoHjgcreuVq+z/f5mUv8dAOT/d3+D14V2MGwu682h7aQ1ajpiZc/p9AIeBZTYVMrq75KpZAheOqsbvJoR4kMlaVHq2h8fFW561kILwZikiNRiZSMsCAv+A8d4nYj7ITrCrd1aN7F70/l2HTRAEqBxS8pUpbbVdcVRfnc/Hr75fiaLY4/f6HY+Gwf/rHruDKaKhrd/CGEtfB8kYsZvOTyVdiJhaz+ehk0nHrNIstuTXY9vhFjE6nX5PR6fRrMPqtBmz+Hq1gKnZt5jFGewQCpSHwZ3aXfFS1XboQThPfBbkgMEahONc+rdFDCZbE3ChaOix572Uk+Uh2NH4cT8YTPqd1WSps+ib2NMbR4nx+LLhXC3LOiLTWhi8QCocrZfsUee50pVqDSGuzFpVqGCU8VWKFrq64MyJkutJhwd0Ahk45RLdAG4fr8cE++21R/Gg/2jC+6DDSuArsqC8uFToufIIKRbzcUXFWkKuG2eAeXCSUzcNC5nLgWYiHmlChgmPBf4xxGz4tCJXzmhxq8AnzGIkr3+HF/fco30vSqOqTNEpVtgabXx8VRJVP4nilqajTcebK+EUIx0k3u+2oNMNx9oFsbxZUabtE5QnrjGrsBfK+0HN7On6BsiWG9vZvpA0Qz2nbQCoG23+spgBTjrJCIfknKe/ZxYQAcam0jfsHT+p5TsYvYEoRgAL/HCrjGj5ezyoRtWe713UKaHmmH3/kKkWApX+3XADe6Izr0iCrpzl2uIqD0cgtR743i6TRGVgfmvpQeCuVFSBOQ53qeihjJXG82WzGKqwGtN7Vx28ufp69XcxGp+PJuKDShDpZOU+lsnvA3cgv+heW+1VmezsjfWtvLn1nIfhCcWWUttyAQma2/SByJYdBREYy0Tm/jBXOE69st6ny8AFN2/LjrpMkV9eRvFGomUCYVnLt+Xcuk6UyHp7IztH7/jXmWLz4DeiglKFzWt6UG2Vq/icjuYamewlrr9to6L3MtVs4yzKoaM/lwWR7Z3Y7n72ZXc5kJNWDhr0Ox6H/wQEOMro/EXQs+LONHnHZbrtxoG139t3Sox69yp14FtG27V8umWLj
-sidebar_class_name: "delete api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Delete API Key"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"delete"}
-  path={"/api-keys/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Permanently deletes an API key. This action cannot be undone. Once deleted, the API key will no longer be able to authenticate API requests.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./delete-api-key.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./delete-api-key.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./delete-api-key.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/delete-api-key.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/delete-api-key.mdx
new file mode 100644
index 000000000..b022e4a24
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/delete-api-key.mdx
@@ -0,0 +1,5 @@
+---
+title: Delete API Key
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml DELETE /api-keys/{id}"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/delete-asset.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/delete-asset.ParamsDetails.json
deleted file mode 100644
index 2670d669f..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/delete-asset.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"X-Wallet-Id","in":"header","required":false,"description":"Optional. Selects the distribution account whose trustlines are affected. Omit it to act on the tenant's default account. An API key does not get that fallback: a key scoped to exactly one account may omit the header, any other key must send it.\n","schema":{"type":"string"}},{"name":"id","in":"path","description":"ID of the asset to delete","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/delete-asset.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/delete-asset.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/delete-asset.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/delete-asset.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/delete-asset.StatusCodes.json
deleted file mode 100644
index 235c47f63..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/delete-asset.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Asset deleted successfully","content":{}},"204":{"description":"Asset already deleted","content":{}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Asset not found","content":{}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/delete-asset.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/delete-asset.api.mdx
deleted file mode 100644
index 3b94e349f..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/delete-asset.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: delete-asset
-title: "Delete Asset"
-description: "This endpoint is used to soft delete an asset."
-sidebar_label: "Delete Asset"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlWG1v2zYQ/isHflkCyC/Jsg3Qt3TxsKzFmtUtOiANBlo6W6wpUiWPSVRD/304SnL8kpdma4EBy4fEFo93z3M8PXfMSpBceJFeitduIY36LElZI64SkaPPnKri11S8LZQHNHlllSFQHoLHHMiCt3OCHDUSgjQgvUcaikTYCl30dZ6LVJxFg1NeFImopJMlEjoOvBJGlihS8efgvdQaaXCei0QojlqgzNGJRDj8FJTDXKRzqT3uonsdP0g9hClqzMgDFQi58uTULPAayCyzwRDcFNYjkAuetDLoQToEOZ9jRpgP4XWpCBQxM5kRWBM9ERpp6DsPOc5l0NR7G8KpgdOLc1hiDblFD8YSLJCACkkwl1rPZLZMQUYLn9mqzRreyox0DdbgGlkpa7AcniO2zBOQpgZLBbrooAyewKPJQdHwgxGJ8FmBpRTpSlBdcRaZslmIpknWiVXrfFaSCrGbvPMzsPMYNB4ew2vPcyvv5AImwlOtYxRVVpoN8LbSNsf1uTyM54q9+coaj57Xj8dj/rONJVZIFz4HH7IMvZ8HrWuRiMwaQkMiXTVNIo7HJw/tl9qhzOvez97Wk/tCv5A5vMFPAT1tbRCyqrTKYi2PPnq2Xe3TtLOPmMXadlz5pFqS6Jx1+9nYPYIzJKm0BzmzoT3/dmPDCSYn/ZORmvaHuR3tc3tnZKDCOvV5JxvfgtyXgxaeJIVNOxPKGUbeJXovF3hfJUWeeCtjCd7hEL9bgi2edzD6QCfjow3XuzvWKfx+P4W/WDdTeY7m2+fvAXp3CHqYD74ArEJzG8xu6TeJ8JgFp6iOyvsCpUN3GqgQ6eUVv6IlUmFZsdcSEDUjFaMoDn60UnnDuoPuutfv4LRIheDtvfcpp6BluRljTVVW6iXWe+/BaXcWMZ+dBgITkMoos+AGMz27gN/ev4WDyfT4hx8Pwbru6V+9EHP36ZRvy99OU2kSMZ1cHI2/EjKYTi4GR+MWW8sZVmSXaJrDZyE6PvmaiI5PvgaiPwK6+stgRVNYd/iHEG0AiJD6wJ94O3cvoczcxnCKYsuZEmotHZwpPwvOY4mG4EJLmltX8tmLRHBJtjB+Go6HY67TUJbS1XGCQXjcx8H07OKQZxsJZK2GWVCa3yMHdmM28twgS7lEmAW9hErW7CU+lbBwNlTcTh1mqlJxwV6ji5reRzdIN9Yth3u5++9B/GA+mDj6cUgDtkIz8Da4DKFyllWtnXSU76DwwGSrfqDYccfjTB4XMpsjZNLADFuh6ietudXa3nC1OKysV2SdQp8yjgFc+tbfqPs7yDeSNKi6JA145EKTXx0URJVPR6OFoiLMhpktR8/ycJhCJL+GUvfl3A6YnVlkpczcSU8uZBRcR5DPhZ460+EzmM1dFPN/Q6138RS3G5xBb/uP2RSoy0FWSEf+UcgbdiNyiKNSKjPqHjzK5ykav6IuITqK+HOstK25vJ5kAsGz3cswQ2eQ0LcDN6Er/ev5FN21yliXelodzKF1i1E0Gtj5wHdmidAqQ+NjQ++Ft5JZgXAcdartoewrHY1ubm6GMq5Gb91WP3p1/vPk9+lkcDwcDwsqddTJynoqpdlw3F62oL9tbWnM6m4eeP6drlN+wlsaVVoqww0iIl91Y8KlaMcEkYhU5XyNLKwnfr5azaTHd043DT9udT69vErEtXRKzljjL1ciV54/P3DR20R/8Ka7mxzCYzeYezH3Lcxw/7qWOvA3kYgl1u19qblqkr4JPg/W//cqem+m24xuX+3XCec7amtwmmVY0cba3ly9NZyeTV5N3k5EIuTeTLKMM0n3gY/u3rPeHXpaFPybMd27ZbVqJ56mWdu3Sw/uWP/3oisrJtE0zd9lfBqd
-sidebar_class_name: "delete api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Delete Asset"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"delete"}
-  path={"/assets/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint is used to soft delete an asset.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./delete-asset.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./delete-asset.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./delete-asset.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/delete-asset.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/delete-asset.mdx
new file mode 100644
index 000000000..4e18a7b07
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/delete-asset.mdx
@@ -0,0 +1,5 @@
+---
+title: Delete Asset
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml DELETE /assets/{id}"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/delete-wallet.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/delete-wallet.ParamsDetails.json
deleted file mode 100644
index 0f53b3f65..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/delete-wallet.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"ID of the wallet to delete","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/delete-wallet.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/delete-wallet.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/delete-wallet.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/delete-wallet.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/delete-wallet.StatusCodes.json
deleted file mode 100644
index 71877f7d3..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/delete-wallet.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"204":{"description":"Wallet deleted successfully","content":{}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/delete-wallet.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/delete-wallet.api.mdx
deleted file mode 100644
index 383c356ee..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/delete-wallet.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: delete-wallet
-title: "Delete Wallet"
-description: "Soft deletes a wallet provider."
-sidebar_label: "Delete Wallet"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdV9tu4zYQ/RVinhJAtpzUbQG9pY0XTXexTddZ7EMSFJQ0trimSO2QitcV9O/FUJLjxLls2hQo+uKLODxzzpA6Qzbg5dJBcgmfpNboHVxHkKPLSFVeWQMJzO3Cixw1enRCinWIExXZG5UjjSECWyFJjj7LIYHTENrBQQSVJFmiR+IsDRhZIiSgcohAMXwlfQH3c56dCrsQvsAhnbc9BYiA8EutCHNIPNUYgfMbzZhOlZXmAPxaaZsjJAupHQdkBZYSkgb8pgqRnpRZQtteM5qrrHHoePx4MuWvu2Q6KX3+XLg6y9C5Ra31BiLIrPFoPCRN20YwnRztA3w0svaFJfUn5ndmgKwqrbJQu/iz4+Bmn61NP2MWSklcaa86rkhk6QFRrN+TdM8jOC99vRtn6jJFYogSnZNLfKhmbRtSyFDsWx7w3npxR+ctjSHRdHK0A31/Rg89nXy3X8I3llKV52j+/fo9Iu+WwUDzga3Cit7Y2vzPl3nRS3xohae7K/wBna0pQ2G2s9oe2mFWk/Kb4Ao/oSSkk9oXkFxe82tZoi8s28n2tQ9GkUDcOYKLG5W3wDh0M5hLTRoSAJ4/wM+5zF0ddpNs9cpKvcXNngGd9NsyrJkoUOZIgldUKqPMUkgj5qfn4tdPF+JgNj/+/odDYal/+oc4OT8TK9ywN/Z+dwdvsL4OltdhPjs/mrwSMzGfnY+OJh23TrNovF2haQ9fxOh4+pqMjqevwej3GmnzbbRCqNi2n8cY7RAIlIbEX3g68E5VZmFDOuVDn5l71FqSOFUurclhicaLcy39wlLJaw8R8JbsaPw4nownvE/rspS0gQQuChRPYxzMT88PheJ2663VIq2V5veHhKWlNH2JHHfFUq5QpLVeiUpuGCU8lWJJtq64iRJmqlJhwN4ghaY6ZDfo15ZW473a/fcoXpkrc1EoF1IaYSs0o95bKrLse8IX0vNwR8Ua4W01HCPuwUVCmjwMZDZHkUkjUuwMKkws+I/Wds27hbCyTnlLCl3CPEbi0nV4cf89yneKNKr6Io1Sma3Q5NcHhfeVS+J4qXxRp+PMlvGLEA4TEcRvqWyG7ewC2T4sqFJmQdJ5qjNfUy+Q18U/t6bjFyhbUOhu/0TaAPGctjWmYoj922oK1OUoKyR59yTlnbjYE2JcSmXi/sGTep6T8QvqUgSgwD/HStsNb69nlYjacdzbOkUyfAofX7FLeaTS/baYI92ojH1pkNXTHFtaxiFoZBcj14dFoFWGxoWePhhvJbMCxXHwqa6HMlYSx+v1eizDaEDrp7r43dnPs/fz2eh4PBkXvtTBJyvrfCnNDnB3FRDbu8Adk2luT0jfcMfovd7jVx9XWirDLSFwbfqTwSX0JwOIIFE5X2QK6zwPNE0qHX4k3bb8uLP25PI6ghtJSqZs65cN5Mrx73x7cXiU78GH/g5yKJ68qjzIemhbhnvWjdQ1/4MIVrjpbkbtdRsNjY95dQMnWYaV35myd6q8c246nb2bXcwgArnXLVehW/Y/OMGDjO63444Ff7bRI1OapuvFbbuN74YendGr3IpnEW3b/gUSkxlp
-sidebar_class_name: "delete api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Delete Wallet"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"delete"}
-  path={"/wallets/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Soft deletes a wallet provider.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./delete-wallet.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./delete-wallet.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./delete-wallet.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/delete-wallet.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/delete-wallet.mdx
new file mode 100644
index 000000000..5b0a29e7f
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/delete-wallet.mdx
@@ -0,0 +1,5 @@
+---
+title: Delete Wallet
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml DELETE /wallets/{id}"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/disbursements.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/disbursements.mdx
new file mode 100644
index 000000000..1e969b954
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/disbursements.mdx
@@ -0,0 +1,5 @@
+---
+title: Disbursements
+---
+
+Endpoints related to disbursements. A disbursement is a group of payments sent to multiple individuals at once. An SDP user with the appropriate role triggers a new disbursement through the SDP dashboard by uploading a list of receivers and amounts. When the receiver has linked their wallet to the SDP, the payment automatically begins. SDP users can track their disbursements in real-time through the SDP dashboard. Each disbursement must have a unique name defined by the organization.
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/disbursements.tag.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/disbursements.tag.mdx
deleted file mode 100644
index badcdef40..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/disbursements.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: disbursements
-title: "Disbursements"
-description: "Disbursements"
-custom_edit_url: null
----
-
-
-
-Endpoints related to disbursements. A disbursement is a group of payments sent to multiple individuals at once. An SDP user with the appropriate role triggers a new disbursement through the SDP dashboard by uploading a list of receivers and amounts. When the receiver has linked their wallet to the SDP, the payment automatically begins. SDP users can track their disbursements in real-time through the SDP dashboard. Each disbursement must have a unique name defined by the organization.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/distribution-wallets.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/distribution-wallets.mdx
new file mode 100644
index 000000000..6e30729d0
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/distribution-wallets.mdx
@@ -0,0 +1,7 @@
+---
+title: Distribution Wallets
+---
+
+Endpoints related to distribution accounts (the Stellar accounts a tenant sends funds from). A tenant starts with a single account, created when the tenant is provisioned, which is marked as the default. Tenants using the `DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT` account type can hold up to 20, and Owners can add more at any time.
+
+Access to an account is granted per user and is separate from the user's role: both are required to act on an account. API keys need the `read:distribution_wallets` or `write:distribution_wallets` permission, and the Owner-only operations additionally require that the key was created by an Owner, so permissions alone are not sufficient. Accounts are archived rather than deleted, so past disbursements and payments keep pointing at the account that sent them.
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/distribution-wallets.tag.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/distribution-wallets.tag.mdx
deleted file mode 100644
index 66e799868..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/distribution-wallets.tag.mdx
+++ /dev/null
@@ -1,23 +0,0 @@
----
-id: distribution-wallets
-title: "Distribution Wallets"
-description: "Distribution Wallets"
-custom_edit_url: null
----
-
-
-
-Endpoints related to distribution accounts (the Stellar accounts a tenant sends funds from). A tenant starts with a single account, created when the tenant is provisioned, which is marked as the default. Tenants using the `DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT` account type can hold up to 20, and Owners can add more at any time.
-
-Access to an account is granted per user and is separate from the user's role: both are required to act on an account. API keys need the `read:distribution_wallets` or `write:distribution_wallets` permission, and the Owner-only operations additionally require that the key was created by an Owner, so permissions alone are not sufficient. Accounts are archived rather than deleted, so past disbursements and payments keep pointing at the account that sent them.
-
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions.ParamsDetails.json
deleted file mode 100644
index 6704cb13a..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"ID of the Disbursement","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions.StatusCodes.json
deleted file mode 100644
index 1b796ca9d..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Disbursement CSV file","headers":{"Content-Disposition":{"description":"The filename of the returned CSV file.","style":"simple","explode":false,"schema":{"type":"string"}},"Content-Type":{"description":"text/csv","style":"simple","explode":false,"schema":{"type":"string"}}},"content":{"text/csv":{"example":""}}},"400":{"description":"Bad request, invalid request parameters","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Disbursement Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions.api.mdx
deleted file mode 100644
index 99fcd6980..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: download-disbursement-instructions
-title: "Download Disbursement Instructions"
-description: "Allows an SDP user to download the raw CSV file that was uploaded when creating the disbursement. This will only return results after instructions have been attached to a draft disbursement."
-sidebar_label: "Download Disbursement Instructions"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdV1tv2zYU/isHfEoA2XKybAP0ljbplnXo0jrdHlJjoKRjizVFqiRl1xP034dDSo5s59KuLbDND7Yhnsv3nUOdS8McX1iW3LILYdPaWCxROctmEcvRZkZUTmjFEnYupV5b4AqmF9dQWzTgNOR6raTmObgCwfA1PJ/+DnMhEVzBHay5hboiAcxhXaCCzCB3Qi28Qj5wOYabQlhYCylBK7kBg642CgzaWjoLfO7QgFDWmTojTBYKvkJIERVw53hWYE6QOOSGz92ucRYxXaHhpHiVs4RddMCHrK8GxlnEKm54iQ4NhadhipfIEiZyFjFBEam4K9h+mK4uQM89uaFlFjGDH2phMGeJMzVGzLqNJHtWlJVEFjH8WEmdI0vmXFoSyAosOUsa5jaVl3RGqAVr2xlZs5VWFi2dn04m9LMLZOh+mxUWsQJ57ik17LlWDpUbXQhbaSuC4r6dmwK9KtHvqYXUYL61S/H9AkLRFsqNP9nH4PCjizO7+jIvbcSy4Maf9jaThuFH7q0lLIid3RfQZzwHSiJaF4FQKy7F9gEM7sqOF15VUmT+2sXvbYjvAUKdvseM7khl6JI6EdKKxmhzSGT/xl2g40Ja4KmunU9PUGwpNs5w+6SnNnyI98kh77eK167QRvyF+Tcn9+mgmXXc1UM5VZcpet4lWssXeO8laL2LLt9bHOyVdrDD8w5G7+hscjIwva+xDeF3hyF8oU0q8hzVt4/fA/TuEPQwz54oGUTvha7V/zzn847ifek+G6b7DVpdmwxBbbX618ZiVhvhNr5NPENu0JzXrmDJ7YxqdYmu0NRzFugZUdtIWDzsTzZuRN7GYrcBWTSrvvvURvryNLtzN6Wwh7gMnW7580q8xM1BvTjv7qzPIYR2AJRhLhQ15q7D//LHDRxdTk+//+EYtOme/gnn11ewxA0V/K4h7tjre2MwS3mZXl6fTL4SMpheXo9OJgFb4AyN00tU7fFnITo9+5qITs++BqLXNZrNp8Hyonc95yFEAwAeUu/4A6n7tivUXHt3wvn2N3UoJTc7swtcS+7m2pSUexYxupIBxo/jyXhC97QuS2423bDwuI2j6cX1MQgLHJzWEtJaSHqfDGiz4KoLkaVBruRLhLSWS6j4xr8lYbxbGF1XNIoYzEQl/IFe0Tw68K7QrbVZjg9i9++D+E69U372FX681hWqUVdrKqOpDoZhWtgOilbgdNUPY3vmIuAqjOOZzhEyriDFULC8Io1zmmZ5ui0G/eCnjUCbEI4R3NpgL+5+R8M6Naq6II1Sni1R5bOjwrnKJnG8EK6o03Gmy/izLBwnYfDfQtn019l6sJ2YZyXU3PBQImvTEaS8uKdyOv4MZnPju92XUOtNPMVtjSn0sv+YTYGyHGUFN84+CnkgFzuDGJdcqLh78Cifp2j8jLIEb8jjz7GSetPveI+/a7UluZd1ikahQzt+R1XKoSntb/MpmpXIqC71tDqYY20WsRca6fnIdmIRkyJDZX2P7wtvRXshnPo6FXoo2UrieL1ej7k/9dY6VRv/evX88tX0cnQ6nowLV0pfJyttXcnVwHC/P+7y2tsgdypPczdG/feX6a4/+SWqklwoamM+vk034NyynQGHRSzpVudBiGYRK7R1JN00Kbf41si2pcehRyW3s4ituBE8pf5025BR+p9v970HY3z0ptu4j+HBpfxeGn3vVdR4V1zWfjGM2BI3Yf9vZ22/R3tM4eA8y7ByA5XthrkzBP50ecMixg/6/NL3+e4PWb0Xxv4gEVzTdxs9oNI0YYpo2618OHpQo6O2ZayIcdv+DfWrZUI=
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Download Disbursement Instructions"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/disbursements/{id}/instructions"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Allows an SDP user to download the raw CSV file that was uploaded when creating the disbursement. This will only return results after instructions have been attached to a draft disbursement.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./download-disbursement-instructions.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./download-disbursement-instructions.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./download-disbursement-instructions.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions.mdx
new file mode 100644
index 000000000..6a8fd8493
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions.mdx
@@ -0,0 +1,5 @@
+---
+title: Download Disbursement Instructions
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /disbursements/{id}/instructions"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/export-disbursements.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/export-disbursements.ParamsDetails.json
deleted file mode 100644
index f7a6b767d..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/export-disbursements.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"X-Wallet-Id","in":"header","required":false,"description":"Optional. Narrows the results to a single distribution account. Omit it to cover every account you have access to.\n","schema":{"type":"string"}},{"name":"q","in":"query","description":"A search term used to query through the disbursement names.","required":false,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"status","in":"query","description":"Comma-separated list of disbursement statuses to filter by.","required":false,"style":"form","explode":true,"schema":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED","CANCELED"],"title":"DisbursementStatus"},"example":"DRAFT"},{"name":"created_at_after","in":"query","description":"Only return disbursements that are created after this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"created_at_before","in":"query","description":"Only return disbursements that are created before this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"sort","in":"query","description":"Field used to sort disbursements","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"created_at","enum":["name","created_at"]}},{"name":"direction","in":"query","description":"Direction for sorting disbursements.","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"desc","enum":["asc","desc"]}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/export-disbursements.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/export-disbursements.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/export-disbursements.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/export-disbursements.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/export-disbursements.StatusCodes.json
deleted file mode 100644
index eb84f547b..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/export-disbursements.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"CSV file of disbursements","content":{"text/csv":{"schema":{"type":"string","format":"binary"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/export-disbursements.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/export-disbursements.api.mdx
deleted file mode 100644
index 41573087f..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/export-disbursements.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: export-disbursements
-title: "Export Disbursements"
-description: "Exports a CSV file of disbursements."
-sidebar_label: "Export Disbursements"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNWFFz2zYM/is4PrV3ku1k3XbnNy92t25tk9Xpulzr61ESbHGhSBWkkno+/fcdKNmRncRJ2vTWl0QWQeD7QAgEsBJeLpwYvheTz6Ul78QsEhm6lFTplTViuF4ACUfTv2CuNIKdQ6ZcUpHDAo13PREJWyJJ3vIiE0OBYdO4KyQiUUqSBXoktrgSRhYohuLv+J3UGn38IhORUGwzR5khiUgQfqoUYSaGc6kd7mI7Dg9S9+C1JLKXDnyOQOgq7R14CxKcMguNjNeTSiqWB5mmtjK+B8eF8qA8S6b2AgnwAmm5XoelrSCXF8gv0LHC3gcjIuHSHAsphivhlyVTYN1mIeo62rD6tObyqUJail3kI3AoKc3BIxVQOcwYRJAFn5OtFnng0vUzsOrg7GtucX6p2ercUiEidr+2GYqhpwrvh9d56Su3H/SRLQoZO+Rz9JiBVs7vBgM0ijC4f660R4Jk+YigI4GmKjhkx29Gz09FJN5MRuMzEYnp6ejN6WQsInEyejsND0fHr05eTpqXR6PXR5OXkzGHuFc+mO5G6LTxQM1IZFE268FEx00pIVP/KP1HOfchRvc47NjoJRD6isz2FwM+lx4kIbQKIWgDnysHmfTYg+eWCumHcHZ2dha/ehWPx4948F2Oh4PBT/HgIB4c3kI0wbklfDSmjbrviKqz5Peze65QZ5uvlOW3ST5mdGc4l5X2W0fQCfqAOequzbqfcaYI04B6L6HxWgzmlgIhZRbXk/o3IMU4OnRk+BVezup6xiZdaY1Dx2oOBwP+t5OFbruG2C3WeDQ+QMDPvp+6C36+Hdg8hJ4YikQZSUtR13UdiWeDg+t23xpZ+dyS+hezbVOyLLVKw+3X/8ex8A0mbfIPpnySJfFd6VVDEYks3RK2nqS7W0Obua/kTFUkSKyiQOfkAm/K/IHn5svY4BCvrYctnlcw1oaeDQ46qnd31GsX/nDdhc8tJSrL0Hx7/91C7wpBi9NhWpHyy1CR/IKSkEaVz8Xw/YzDsUCfW65oFhhsS14S/aa+cf3d+HNIF+vypiIthkKwlrWRKZNqcHdNbcDLUv2BNxQLrXeDh6ApjoD9J5Xh71YamI5P4Pd3p/BkMj388aenYKl9+xFGJy/gHMMV3CaJLX07NVcdienk5GDwSMhgOjmJDwYNtoYzrLw9R1M/fRCiw2ePiejw2WMg+pNz6/1gBVHYFMC3IeoACJC2szjHqzJzG8y1FczUo9aSoFvJwImWnjMbn72IBIdkA+Pn3qA34DitioLT3VCc5gj7dTyZjk+eguIOwFurIamU9uHesLSQpnVRqPcKeY6QVPocSrlsr38uwhdkq5LzNWGqShUWQr3tO9YN+ktL571rvvv+IH4wH8wp1y9s0oAt0cTOVpQilGQ5TzVlj3ItFGvA26D+BnURSJOFhdRmCKk0kCDMbWWysDHnH1rbS44WwtI65S0pdEPGEcN71+jrt//jblaKy9ZJcSLTczTZ7EnufemG/f5C+bxKeqkt+g/S8HQIgfwGynIdzk3/1YoFVsrMSTpPVeoragnyufi7zrT3AGZzCnfJ11Bbq7iL2yUmsJb9YjY56iJOc0ne7YXcket7QuwXUpl++2Ivn7to/Ia6gKAo4M+w1HbJ4XUnE6i4o4Y/qgTJoEfXtMTcxrrj+RTpQqWcl9a0Wpg9S4t+EIrtPHatWCS0StG4cEWvE28p0xzhMOSp5g5lXcN+//LysifDatDWbnX9ly+OJq+nk/iwN+jlvtAhT5bW+UKajuJmkAG7Q4mtXLO6KkvuO/ho834oN0stleHrIeBeteXC+3YcEqxtWZ9FIrfOs8hqlUiHb0nXNb9uEj6XEZlyMtG3jUC6gL9upnAjj3NctrOMC6krDPVM9BBMXzcy2INpM6/4QmCP3prvwXrD0ODbo75nm30/2JsRwBfivkcDve+smwb9C23fs9fdY7/bVF+BmPEPUowidAvRujx82Ff7P80w99DdHshueb0RGKUplt0T2fTaWy3TrxOezslr9fF5qI/bB3bWesksOzp3C/DGNP9lIDduWa2a6ruuN/LN0q07NoPmRpq9MKvr+j8Ucgkf
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Export Disbursements"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/exports/disbursements"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Exports a CSV file of disbursements.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./export-disbursements.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./export-disbursements.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./export-disbursements.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/export-disbursements.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/export-disbursements.mdx
new file mode 100644
index 000000000..2e7fbf511
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/export-disbursements.mdx
@@ -0,0 +1,5 @@
+---
+title: Export Disbursements
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /exports/disbursements"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/export-payments-csv.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/export-payments-csv.ParamsDetails.json
deleted file mode 100644
index daa4461a1..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/export-payments-csv.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"X-Wallet-Id","in":"header","required":false,"description":"Optional. Narrows the results to a single distribution account. Omit it to cover every account you have access to.\n","schema":{"type":"string"}},{"name":"q","in":"query","description":"Search payments by ID, external_payment_id, receiver wallet address, or disbursement name.","required":false,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"type","in":"query","description":"Type of payments","required":false,"style":"form","explode":true,"schema":{"type":"string","enum":["DIRECT","DISBURSEMENT"]}},{"name":"status","in":"query","description":"Exact match on the status of the payment.","required":false,"style":"form","explode":true,"schema":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"example":"DRAFT"},{"name":"receiver_id","in":"query","description":"UUID that represents a receiver in the database","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"b6b667ad-6cc2-46cf-9be7-561daace7d48"},{"name":"created_at_after","in":"query","description":"Only return payments that are created after this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"created_at_before","in":"query","description":"Only return payments that are created before this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"sort","in":"query","description":"Field used to sort payments.","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"updated_at","enum":["updated_at","created_at"]}},{"name":"direction","in":"query","description":"Direction for sorting payments.","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"desc","enum":["asc","desc"]}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/export-payments-csv.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/export-payments-csv.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/export-payments-csv.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/export-payments-csv.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/export-payments-csv.StatusCodes.json
deleted file mode 100644
index 82feebb63..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/export-payments-csv.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"CSV file of payments","content":{"text/csv":{"schema":{"type":"string","format":"binary"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/export-payments-csv.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/export-payments-csv.api.mdx
deleted file mode 100644
index 1b0297ce9..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/export-payments-csv.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: export-payments-csv
-title: "Export Payments"
-description: "Exports a CSV file of payments."
-sidebar_label: "Export Payments"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNWW1z4jYQ/isafbqbsYHQNNfyjQbS0vZy9Jy0zdwxGdlesBpb8q3k5Cjj/95Z2QaTEPLSZNovYKz17vOsV6vdZcWtWBg++MTHX3ON1vCZx2MwEcrcSq34oFlggh0Hv7O5TIHpOcvFMgNlTYd7XOeAgqQnMR9wcPLTev04+J17PBcoMrCAZGrFlciAD/if/h8iTcH6k5h7XJKxBEQMyD2O8KWQCDEfzEVq4DaoD+5CpB12KhD1jWE2AYZgitQaZjUTzEi1SIHF0liUYUHyTESRLpTtsA+ZtExakoz0NSCDa8Bls86WumCJuAa6AYYUdj4r7nETJZAJPlhxu8yJAulWC16W3prVl4bLlwJwyW8jD0BglKz9x8Ilm4w8Bl8toBLpZb1wKWOPIUQgCd2N8xMTcYxgjMc0Eq+wQAMkzMh0Z5fXjF2mBGquMeMevZtUx8AHFgt4HB23spfR2TLfComXw+FxUEVG0TmafBwfn3GPjybBD+cfg/H78ekZn7WBGitsYfZDHX8VkWWZsFHCtHIxUz1G+OlXzeEFfXnHW/fZbLP9ODwhsh/Hw9EF9/h0fDqanP5IV8PzYDziHg/Oj4/HQcA9fjKc/OpuHQ9Pj8d0OfO4ldZhrbdhUPmmJNQiy91SZaTlwCbaLmW834vn55MRs4mwDCFHMC6OxSZaZeXZWFgRCgMvGJdt/OFReHT0TsT+URT1/cOjaO5/H8I7/9ujg1iICN7Fh9+16UUIwkJ8KeylmFuXZPZw/KDSJUOwBarNXnWcBQKrdTGniNlEGmILHXaiMRN2wC4uLi789+/90eiV2Pd7vSO/d+D3+vdwDGGu8YGd+ziSlab/EUuj0e4ndiIhjVlhIKYMT/JbB9YLbu25KFLLB7zI49rzrX28dXPzbrbzViwRIod7L6VRI8bmGh0lqRavzYogtPgI98vdnJXljEyaXCsDhtT0ez362oa9q2YgZ2hlKeeRdfhqu5G5puv7Mc1dyNG2l0rgkpdlWXr8sHdw1+S5EoVNNMq/Id42JfI8lZErVbp/GRLeYVKHf0FELyxHKmysrNgBosZ7wtWiMA9rqA+ojZwqshCQVGRgjFjArpPY8VzviDUOfqot2+K5gdEYOuwdtFTffqJsXPjNXReeaAxlHIN6ff/dQ2+DoMZpICpQ2qUrIH8AgYDDwiZ88GlGkZiBTTSVnwtwtgUt8W5VjJpuK/QM4HVTiBaY8gHnpKDRHxCfCnLbyhq3yOUvcHd7DmvHOuewqoxl5DohFW1UoVgwmrKf/zhjb8ZB/9ujt1TEVXcv2XA6YVewpF1cZ4Utfbeq49LjwXh60HshZCwYT/2DXoWt4sxWVl+BKt8+CVH/8CUR9Q9fAtFvlEwfB8uJsnWrch+iFgAHaTttU6hKNdfOXF2EBRbSVCAbtUv2aSosJTV699zjFJIVjHedXqdHcVpkGWW6qmTcr+NNMJq+ZZKqMKt1ysJCptYdFBoXQtUuco1RJq6AhUV61TrxqV1aoC5yytIIkcylW3CdkW1ZV2BvNF51dla1/y+In9VndUYlC5lUTOegfKMLjIDlqClFVZWONDUU6gd03hTlt9R5TKjYLUQ6BhYJxUJgc12ouGkk5jpN9Q1FC0KujbQaJZgB4fDZJ1Pp69bffrt98/PaSX4ooitQ8exNYm1uBt3uQtqkCDuRzrpP0vB2wBz5NZRlE85Vp1yLOVZSzVEYi0VkC6wJ0nuxD73TzhOYzdEdI/+GWqPiIW43ELJG9tlsEkgzP0oEWrMXckuuaxGgmwmpuvWNvXweovETpBlzihz+GPJULym8HmTCCpp9sF+KEFCBBVMNLyxgZj7MA8BrGVFeamjVMDsaF10n5Ou5b2oxj6cyAmXc6dwk3lxECbC+y1PVGUq6Bt3uzc1NR7hVp61+1HR/nRyPT4Ox3+/0OonNUpcnc21sJlRLcTVrYtPNab2VZlabYuQRY6k627v6Mk+FVHQoOLSruj74VA+rjKsYapszjyfaWFpdrah/Pce0LOl2leGpboilEWF633SqDfNVxz07GV7Bsp5CXYu0AFffeE+BvGOes8dQPR96pq2nDGT2gFjPfp4J4+kTjT1gtucoz0T0kvOHPVh3DEVeFfAjZwmPQ7wecTwT8gNTgn3xVk0gnmn34VZ+j+n2uGBjf0Y/UBIA1xF5TR38tGz1H43V99Dd/o9gy+GVwDCKIG+/jPU8Yast/HFMA1VxpxG4co1AfUHOapbUsqXzdqdRmaZPArLzkdWqajPKci1fLd37xPq/j0qavDAry/IfhrndGg==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Export Payments"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/exports/payments"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Exports a CSV file of payments.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./export-payments-csv.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./export-payments-csv.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./export-payments-csv.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/export-payments-csv.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/export-payments-csv.mdx
new file mode 100644
index 000000000..d90b8fb7e
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/export-payments-csv.mdx
@@ -0,0 +1,5 @@
+---
+title: Export Payments
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /exports/payments"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/export-receivers-csv.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/export-receivers-csv.ParamsDetails.json
deleted file mode 100644
index c9644f4e5..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/export-receivers-csv.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"X-Wallet-Id","in":"header","required":false,"description":"Optional. Narrows the results to a single distribution account. Omit it to cover every account you have access to.\n","schema":{"type":"string"}},{"name":"q","in":"query","description":"A search term used to query through the receiver phone_number, email, and ID.","required":false,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"status","in":"query","description":"Exact match on the status of the receiver wallet.","required":false,"style":"form","explode":true,"schema":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"example":"DRAFT"},{"name":"created_at_after","in":"query","description":"Only return receivers that are created after this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"created_at_before","in":"query","description":"Only return receivers that are created before this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"sort","in":"query","description":"Field used to sort receivers","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"updated_at","enum":["updated_at","created_at"]}},{"name":"direction","in":"query","description":"Direction for sorting receivers.","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"desc","enum":["asc","desc"]}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/export-receivers-csv.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/export-receivers-csv.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/export-receivers-csv.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/export-receivers-csv.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/export-receivers-csv.StatusCodes.json
deleted file mode 100644
index 10abf1ea2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/export-receivers-csv.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"CSV file of receivers","content":{"text/csv":{"schema":{"type":"string","format":"binary"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/export-receivers-csv.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/export-receivers-csv.api.mdx
deleted file mode 100644
index 60bb93e0e..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/export-receivers-csv.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: export-receivers-csv
-title: "Export Receivers"
-description: "Exports a CSV file of receivers."
-sidebar_label: "Export Receivers"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNWNty2zYQ/ZUdPMUz1MWum87wzY1k183FruUk9TgaD0SuRMQkwCxAO6qG/95ZkJQpX+RLlWledCGWu+csFosDLISTMyvCczH8nhtyVowDEaONSOVOGS3CZgAkvBl9gqlKEcwUCCNUV0i2KwJhciTJ5oexCAX6F04agzejTyIQuSSZoUPiYAuhZYYiFH93Pss0Rdc5jEUgFIdLUMZIIhCE3wpFGItwKlOLt2Ed+R8y7cIHSWSuLbgEgdAWqbPgDEiwSs9ShFhZR2pSsD3IKDKFdl04ypQD5dgyMldIgFdI82Yc5qaARF4hP0DLDrtftAiEjRLMpAgXws1zpsC+9UyUZbBk9a3h8q1AmovbyPfAoqQoAYeUQWExZhDeFlxCppglNZcqg5AnRuOFLrIJUgCYSZUGIHUMh4PufYmybp4yjqmhTAQ8H6mJUYSOCnwaA+ukK+x6GsPvMnKQSRclYLRHXL3G5bGC/9rP8QahBgJ1kXHVDk729k9FIE6Ge4Mz/31wODodngwHIhD77/YODoYDLmmnnI+zrMqq7kYVz5Ijyyz3JpXLVjIiQukwvpDuQk6dr801aTnS6RwIXUH6ZpGAS6QDSQi1M/CewCXKQiwddmHfUCZdCGdnZ2ed9+87g8EGp7bNb6fff93pb3f6Ow+QnODUEG6EZeXqJ6JpDbn1zPYVpvFyVbL9DcFNVnCMU1mkToSiyOM69a3CXnl4Mzli3F6msSKMPO61lAaNGUwNeUpKz1Y7+A+gxRhahKT/5x+Oy3LMIW1utEXLbnb6ff5axX3vfsPpMNqhdj48fne9yF7x74dBTX3RiVBMlJY0F2VZloHY7W/fjflRy8IlhtQ/GK+Gknmeqshvc72vlo3vCWkmXzHiKcuJN0WnKnpIZOiBgnUk7eMe6o58Y1dtB+wiQ2vlDO/r6J7nck0scYgPxsEKzxsYTaDd/nbL9e03yiaFv9xN4b6hiYpj1D8+fw/Qu0FQ47QYFaTc3GuP31ES0l7hEhGej7kUM3SJYekyQx9b8pDoVULG9tq1Z5GuGhFTUCpCIdhDE2DEhCrM7TBL4DJXb/EeSVBn1mcHKgkEnDupNK9VqWE0OIY/P5/Cq+Fo59fXW2CofnoBe8eHcIlzXsd1Y1jxd0tZlYEYDY+3+xtCBqPhcWe7X2GrOMPCmUvU5dazEO3sbhLRzu4mEP3F/fRpsLwpLGXuQ4haADyk1c7Ntar01PhwtWQZOUxTSTBQdlKQxQy1g+NUOu5qPPciEFySFYzfuv1un+u0yDJudaE4TRDW+3g1GhxvgWKJ74xJYVKo1Pm9wtBM6jpFXlRn8hJhUqSXkMs5e6ml9oxMkdd9WuXKD3hV7VrRNbprQ5fdO7n7+SB+0V/0KasWDqnB5Kg71hQUIeRkuEdVYkfZGgorYJM30veWu0qt80BkYoRIapggTE2h40Y6T02amutqX86NVc6QQhsyjg6c28pfr/7uxK0kdfI6SZ2JjC5Rx+NXiXO5DXu9mXJJMelGJus9y8NWCJ78Esq8KefqlFWbeVZKT0laR0XkCqoJ8ry4x+a0+wxmU/L7yH+h1rh4jNs1TqCxfTGbBNOsEyWSnF0LuWXXc4TYy6TSvfrBWj6P0fgD0wy8I48/xjw1cy6vR5lAwedmeFtMkDQ6tNXBlw+r9mg6QrpSEfelhlYNs2to1vNGHTPt2NosEKmKUFu/PTeNN5dRgrDj+1S1h7KvsNe7vr7uSj/qvdWv2t67wzfDD6NhZ6fb7yYuS32fzI11mdQtx9VNBZy0tuuVPrO4kSNPudWo+72XmHkqleZtweNd1BLhvL7rqA4GTdRxIBJjHQ8vFhNp8SOlZcmPqybP0iFWVk7Shy432kA3fVtwL6tLnNf3FlcyLdCrmuA5KF9yGbAGyfL+4YVwNnoIX4PznquBH4v4iQfqp0FeHvRfiPmRo/K6+a2O4S+M+4Tz7JrY7UPzDYAx/yHFCPypIGik4PNW6/90K7mG7uoV60rGK4O9KMK8PRvLM/XK0ehgyPds8o4WvvRauP7ByWqG9Lzl87bYrkLzJwO595XFolLaZbm0r4YefGN5dVxZcxbGZVn+CzmK8U4=
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Export Receivers"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/exports/receivers"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Exports a CSV file of receivers.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./export-receivers-csv.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./export-receivers-csv.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./export-receivers-csv.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/export-receivers-csv.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/export-receivers-csv.mdx
new file mode 100644
index 000000000..3ff70c5ab
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/export-receivers-csv.mdx
@@ -0,0 +1,5 @@
+---
+title: Export Receivers
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /exports/receivers"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/forgot-password.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/forgot-password.RequestSchema.json
deleted file mode 100644
index b5a7e752e..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/forgot-password.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"description":"Forgot password request data","content":{"*/*":{"schema":{"required":["email"],"type":"object","properties":{"email":{"type":"string","description":"Email of the user","format":"email"},"recaptcha_token":{"type":"string","description":"Token for reCAPTCHA validation"}}}}},"required":true}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/forgot-password.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/forgot-password.StatusCodes.json
deleted file mode 100644
index f1035f1a4..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/forgot-password.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Forgot password email sent successfully","content":{"*/*":{"schema":{"required":["message"],"type":"object","properties":{"message":{"type":"string"}},"title":"MessageResponse"}}}},"400":{"description":"Bad Request","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/forgot-password.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/forgot-password.api.mdx
deleted file mode 100644
index 91942258d..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/forgot-password.api.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-id: forgot-password
-title: "Forgot Password"
-description: "Sends an email with a token to an SDP user who has gone through the Forgot Password process."
-sidebar_label: "Forgot Password"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNV1Fv2zYQ/isEn5pCstyg2wC9pUmGdt1Wr/awhzQoTtLZ4iyR7PEU1zP834ejpMZzt3jZOmB6kUUeP37fHXl33mmGVdD5jb7ouEbLpgQ2zurbRFcYSjI+fuZ6jrYKCqzCFkyjNoZrBYrdGq1iJxPzq5nqApLa1E7VENTKWVRck+tWteIa1beOVo7VDELYOKqUJ1diCBOdaOeR4s6vKp3rZTQc7XSiCT90GPiFq7Y63x1RG2D9CDsYqwoYdKJLZxkty7qn2VN5hbLGFuSXmBrCSjwQhYlw3nrUuXbFr1iyTrQnYccGgyzpzfLdaBaYjF3pY39dRze5ZRQubtGJyGqBdT5g7EVXCZ7LGt5HT56GXUSHLx0pwsuL2eLy5YW6g8ZUfdj28iQHspg6jAPBOxt6BefT6Wkn9mEOaFmFrpQwLbum2T7Cny2GACs87dHR8DPxIoUNNzL0Q2/0dhCie6HP/0zKC6jU2/4MnKB7ItJEjk6H5AoZTBMUFK7jGO5+4T7R+JEJwsmd9sOT6I9p6SpcoU2HQ5wWrtqmFlpZLb91REUbjLNycXd6jVudP7gy0XfQdJ8Q9reJbpFrJ1fNu+glD1zrXGf9zUv9/dULSHdI/VYdNTrXESBg2ZHh7Vyc2fvrBQIhSSI5UAzevMbtZ04TK0fmt3hsVY1QISkJFRhr7GrMJ9/9slBPrufnX319phwNo+/VxeyVWuNWEsfgmj/g6UQb2aSHlUDMr2fPpl+ImZpfz9Jn055br1nt4vXdnz2K0fnzL8no/PmXYPRTh7T9e7SiqfJA0CL/NaMDAn2OGzb+IMvjFTd26eJ2w1WfMzYNkLoyoegoYCtJaNYAS/6U2MuBRgo9jW8m08lUzmnXtkByFRY1qocxnsyvZmfKhFjBXKOKzjQcs6qjFdjBRUEKWwtrVEXXrJWHraDEUVArcp2X/E5YGm/ihLtDiglg3N0ibxytJ5+n8f8dxXf2nV3UJsQtrXIebRpcRyVKmZaspbgGlumeipO678cKdwSXKLBVnJCspEqwqkC1dJ2t4sJaPprGbeS0EHoXDDsyGHLhkaqb0ONlwzutDpyU+sFJaQHlGm11+6Rm9iHPspXhuismpWuzRyGc5SqK/0RlOx7nEMkOZlGVsUuCwNSV3NEgUOLCp2I6eYSyJcWy9W+kjRCntG2wUKPtP1ZTY9OmZQ3E4UHKB3YZE2LWgrHZMPCgnlMyXmLTqggU+VfoG7eV43VSieqC2L3uCiSLjGHyTrIUI7XhzXKOdGdKyUujrIHmxNEqi0apW6ZhMEt0Y0qUDiXffUq8Hsoa1XnMU30NFaw8yzabzQTibEQblobs+1eX1z/Or9PzyXRSc9vEPCmlugV7AHzUUB+nmd198/Nf9+9DqWD8yJlvwFipKFHqbugtbvRxb3Gb6Fq6j/xG73YFBPyZmv1ehvvakN/cSudCBgqpCze3+2QsV/d9z2WvMF0IgftGR1q9fTIaXZQlej6ePmyDZm/mC530/ZG0pK4SM4KN/PmATex69vvfAbNNoO4=
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Forgot Password"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/forgot-password"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Sends an email with a token to an SDP user who has gone through the Forgot Password process.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./forgot-password.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./forgot-password.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/forgot-password.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/forgot-password.mdx
new file mode 100644
index 000000000..8f344ae1b
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/forgot-password.mdx
@@ -0,0 +1,5 @@
+---
+title: Forgot Password
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml POST /forgot-password"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-assets.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-assets.ParamsDetails.json
deleted file mode 100644
index f545be8c2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-assets.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"enabled","in":"query","required":false,"description":"When set, each asset also reports whether the selected distribution account can send it and what it currently holds. `true` returns only assets the account is set up for, `false` only those it is not.\n","schema":{"type":"boolean"}},{"name":"X-Wallet-Id","in":"header","required":false,"description":"Optional. When the enabled filter is used, selects the distribution account that the enabled and balance fields describe. Omit it to describe the tenant's default account.\n","schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-assets.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-assets.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-assets.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-assets.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-assets.StatusCodes.json
deleted file mode 100644
index 6a34555fa..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-assets.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"A list of assets. When the `enabled` filter is used, each entry also carries `enabled` and `balance`.","content":{"application/json":{"schema":{"type":"array","items":{"oneOf":[{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},{"allOf":[{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},{"type":"object","description":"An asset as reported for one distribution account, returned when the `enabled` filter is used.","properties":{"enabled":{"type":"boolean","description":"Whether the selected account is set up to send this asset"},"balance":{"type":"string","description":"What the account currently holds of this asset. Omitted when the balance could not be read."}}}],"title":"AssetWithEnabledInfo"}]}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}},"404":{"description":"The distribution account named by X-Wallet-Id is not visible to the caller","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"distribution wallet not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-assets.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-assets.api.mdx
deleted file mode 100644
index 6b803e7ea..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-assets.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: get-all-assets
-title: "Get All Assets"
-description: "Fetches the list of available assets to populate the dropdown box in the New Disbursement flow. Note: the organization must hold a balance in a particular asset to use it in a disbursement."
-sidebar_label: "Get All Assets"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWFFz2zYS/isYvFwyQ0qyLNs3elNiO/XFtZ2TE/eaeGqQXImoQYAFFlZUjf57Z0FSpiw5jq/p3fWmfrAkYvnh+xYL7C4WHMXU8eFHfm6nQstfBUqj+XXEM3CplWX4OeTHgGkOjmEOTEmHzEyYuBNSiUQBE84BOoaGlab0SiAEw8yaMjMzzRLzmUkdnp3BjB1Kl3jroACNbKLMrMPODMIwGJgWD1Z4hyw3KmOCJUIJnQIBCVYKizL1SthqcprbO2ASq/GsNUWHR9yUYAPkScaH/A3gSKlRYM0jXgorCkCw5IgF16IAPuSgSVvGIy7JA794sHMecQu/eGkh48OJUA4eOuoqB80cYMRApHlNTihnmIXSWHRslgPmYINYBwpShIz4opWJD6pFmhqvkaWCoHRGqoTO2CwXSN9Tby1oVPPgGtdhN2g93DAL6K12zGg1X61JDis86YgZ8yWbGBuxmyDgpjLH3NTuc0wb7HzSPOIuzaEQfLjgOC/JJ4kxCoTmy2W08tMP8ZVQCjA+WfkqB5GBfdpZ5+GLUB0W3EZca6+ziVQIlth4B1lUe6rSs9VZSM5pI5DHmpiZSFCZY9XsCXTYeSGDK9GsHoaXEbTQ+DcynQivsIF/xB/EQ0/5cnlNWl1ptANH4/1ejz7W5Y7ut05YnJbsm5r1zYbwEEag0c6rMEqFtRJc6w0SelMrvaFgT41G0EgERFkqmYbI7/7siMViU4WwVlBoS4QisDcazidhL9QWJvkZUqStYmknoaxUymzTFxGHz6IoFT2aTASkg2Q3HuwnvXiQJYNYDNJBvJ/u7vX+3ts7OOjt8SURzmAb0gP3hb0UbNuTvB8fviYQ6ZwH+7UwlTUTWWbBuTXAN69eHQ4OTo73T6/eHlwcfH949GH8+uqfB4cX768+7J79a/fw8t3Rh+PTwdnocjB6993uj6enx6ejSokFgZD9JHAbkYmxBY3wTCDEKIt1Jf1efzfu9ePe7uVObzjYG+7t/Eigvsy+PWgGCn4n6H4NuleDLh+6+jIHNkZQ98f0KpBQYkAKq8HpOBFK/RV0fwXdfzboHobag1XTTQJ3dfqmzGQsM3p7ForqHAyUrJ842jsbkd1UHJv5dkuVsVlDbKZ5NFX9gLl0lRJahDpVPB20V01KXRUk64UHZbJ76CqpYlt6k35T41VGZQVLgFkQWYcvQ85cW5AriflR5YITPTF8eb2kv4gPejubyfS9Fh5zY+WvoUZ7bs575HABa82W7bykOEQr3NMIDgX6tp32RQKWIApwTky3OL6SuYr0FQ1+ZpCtybxn0cwz6O20kB++8UcCV0uzu7k0x8YmMstA//Hrsl3dPYGvMKhkDDZlXD5WalLhm7Fkzlqlb103szvpJLVEaMIOSGnc/rf8sMZ+FqgGkhPjdb2Ey4g7SL2VOA+59xUIC3bkMefDj9e0RwvA3FDXNIXAR9AQ74qme3Jg75rWyVvFh5zTaw3qmJRV5NvY98VnKd/CfPPorUOt6gOrhoKRE4XUUk+Z0Gx8eMH+cXXJXhyN+3v7L5mx9dOf2OjihN3CnI7YuktZw3vQpywjPj662Ol9I2ZsfHQR7/QqbpVmtkBzC3r58lmM+oNvyag/+BaM3lEb/HW0gilbNdePMWoRCJTWG24KUEnZgKars0WT3dfuES6UQCogaO15xCkkKxoHnV6nR3Hqi0LY+YMKYTvGi/HhxUva0oKhMYolXiqsMn/reiLceBTiFlji1S0rxZxQwlPBptb4kjKkhVSWMgyYuzpnN7NrwJmxt50N3/3vUfykP+lLSvY0pWamBB07420KrLSGDquqBZeupmI0Q1NWNcIGXBS61nBCmgzCTUcC1bkUXszph1JmRtFCpZeTaKjvHRKPmH10FV63/ozbFz5xWTspTkR6Czq7fpEjlm7Y7U4l5j7ppKboPgvh5ZAF8Ssq8yacXV3pBLOgSuqJFQ6tT9HbWiCtCz61pp1nKJvYkFB+j7QG4iltM0hYY/tvq8lBFXGaC4vui5Rbdl20AN1CSN2tH3xRz1MyvgNVsAAU+GdQKjOn8HpSCfOO7N76BKwGBFfdBiHYwp1PxmDvJJXTvJFV0+wYO+0Go9hMYlebRVzJFLQLibo5eEuR5sD64ZyqcihhDbvd2WzWEWE0oNWvuu7pyeujs/FR3O/0OjkWKpyTpXFYCN0CfgPIRkqx1VXn2imzuK9K/vQXvHUqQviM3VIJqUMPS65c1CXLR16XLNcRz41DerJYJMLBe6uWS3pcpRwqZDLp6l5s28Vl23H/Vxe+W714C/O16/A7oTw0Zd6dsJIGQrUYNdXC81z4Z7sG/oKX1i/D7z0VLWqDUZpCia2xjW5greZ+c3TJIy426q3bUG/VX1p3ZkLPW9gPC7qKAv1v3X2sv7JYVNXccrmyr4YefWN12V9Zkzeocf8NwKEdiQ==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get All Assets"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/assets"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches the list of available assets to populate the dropdown box in the New Disbursement flow. Note: the organization must hold a balance in a particular asset to use it in a disbursement.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./get-all-assets.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-all-assets.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-all-assets.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-assets.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-assets.mdx
new file mode 100644
index 000000000..372f61bd8
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-assets.mdx
@@ -0,0 +1,5 @@
+---
+title: Get All Assets
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /assets"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-roles.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-roles.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-roles.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-roles.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-roles.StatusCodes.json
deleted file mode 100644
index 1627f5faf..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-roles.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"type":"object","properties":{"roles":{"type":"array","items":{"type":"string"}}},"example":{"roles":["developer","financial_controller","business","owner"]}},"example":{"roles":["developer","financial_controller","business","owner"]}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-roles.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-roles.api.mdx
deleted file mode 100644
index a6004feb5..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-roles.api.mdx
+++ /dev/null
@@ -1,62 +0,0 @@
----
-id: get-all-roles
-title: "Get All Roles"
-description: "Fetches available SDP roles, such as owner, financial controller, business user, and developer."
-sidebar_label: "Get All Roles"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNV99v2zYQ/lcO99QAsuVk2QboLVvTruvQpnOKPbhGQUlnizVFakfKrmf4fx+OkhLnR5t2S4e9WBZ5/O77juTdaYdBLT1mM3zriT3OEyzJF6yboJ3FDJ9RKCryoNZKG5UbgunTC2BnyCfg26IC5cFtLHECC22VLbQyUDgb2Bkjo3nrtSXvofXyqmwJJa3JuIZ4jAnKU4m3FyVm+JzCmTG/Cz4myOQbZz15zHZ4MpnI4ya/1y8xQXFHNsisahqji4iXfvBiskNfVFQr+Re2DWGGLv9ARcAEGxbvQXcOoqoDM8WstpigDlQfjvvA2i5xv98nSB9V3Rg6WD7DK3mY4FVM3l/HBBMcgiL6JXg4f2QwgTudHN8N2Fur2lA51n9R+XihI2bH94RINAVW/mEEH1RoD+1sW+fEAlGT92pJ9+7Azaj1NPCVC3BD5jWLwc/p5PgA+faKbwncbc13d7fmmeNclyXZb78v96u7JvAFBlGHp6JlHbaYzXb4EykmPmtDhdlsvp9LGELl5FovKXJTMoWpZAKfcn/JPfFaco9AtGwwQ5S1A/RUpHZqDh1c39JGvyS5pjeDedbHPMYNKlIlccxLSlttl6BszGS//nEJT86nJ9//cASO+9H3cHbxAla0lfxkVU238SQpiJMOVs7o9PziePJIzGB6fjE6nnTcOs2wC25Fdn/0VYxOTh+T0cnpYzB60xJvv4xWNIVGsaopfJrRAYFIaXD8pyyPJ1nbhYvudJDzjNNAxiiGp9rnLXuqyQa4MCosHNey95igHMmOxo/jyXgi57Sta8VbzPCyIvg8xpPp04sj0B4UBOcM5K02ARaOwfFS2T5EHoKDWq0I8tasoFFbQYmjCpbs2gbcApgK3eg44dbEEA68Wwobx6vxndj9/yi+s+/sZaV9dGnBNWRH3rVcEDTsJHtBqFSQ6Y6KsxBchL8HrmskZKJwJUGhLOQEC9faMi6s5MUYt5HTwtQ4r4NjTT4THiOY+Q4v7Z+j8iBIo6YP0ihXxYpsOX9ShdD4LE2XOlRtPi5cnX4VwlEGUfwVle1wnH0k25tFVdouWPnAbRFa7gXKvoSH9nT8FcoWHCvMv5E2QDykbUM5DLb/WE1Fph4VleLgP0v5wC4NTJTWStu0H/isnodk/EKmhggU+ZfUGLeV4/WgEpAGbQkv25zYUiA/fidZKhDX/vViSrzWheSlQVZPc+x4mUajkVuMfG+WoNEFWR8L85B4G1VUBCcxT3U1VLCyNN1sNmMVZyNav9Snv734+fzV9Hx0Mp6Mq1CbmCcb50Ot7AHwcwpwZgwMDfmNJLO77lL+g++EvlYE+hjSxihtpaRErbu+sZhhbCzkuyHSnSdYOR9kYrfLlae3bPZ7Ge5KQzabJ7hWrIVvbFmSoVpJL7IiyfVnRUGNNC9rZdquWN1qx240Os/PLzFBdae+rWJ96/8I+jBltwfYtwtoR0F+98knlux2XfXc76/su6lPruglDtYSSPlg+Bvolu4O
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get All Roles"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/users/roles"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches available SDP roles, such as owner, financial controller, business user, and developer.
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-all-roles.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-all-roles.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-roles.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-roles.mdx
new file mode 100644
index 000000000..5855ccf55
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-roles.mdx
@@ -0,0 +1,5 @@
+---
+title: Get All Roles
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /users/roles"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-tenants.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-tenants.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-tenants.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-tenants.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-tenants.StatusCodes.json
deleted file mode 100644
index 7890c5fc3..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-tenants.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"A list of provisioned tenants with their configurations","content":{"application/json":{"schema":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"name":{"type":"string","description":"The tenant name. It should match the pattern `^[a-z-]+$`.","example":"bluecorp"},"base_url":{"type":"string","description":"The SDP backend server's base URL.","example":"https://bluecorp-backend.sdp.org"},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL.","example":"https://bluecorp.sdp.org"},"status":{"type":"string","enum":["TENANT_CREATED","TENANT_PROVISIONED","TENANT_ACTIVATED","TENANT_DEACTIVATED"]},"distribution_account_address":{"type":"string","description":"The Stellar account address used for distributing funds.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"distribution_account_type":{"type":"string","description":"The Stellar account type used for distributing funds.","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"distribution_account_status":{"type":"string","description":"The status of the distribution account used for distributing funds.","enum":["ACTIVE","PENDING_USER_ACTIVATION"]},"is_default":{"type":"boolean","description":"Boolean flag that shows whether the tenant is the default or not.","default":false},"created_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"deleted_at":{"type":"string","description":"The timestamp when the tenant was (soft) deleted.","format":"date-time","example":"2024-03-27T17:21:51Z"}},"required":["base_url","created_at","distribution_account_address","distribution_account_status","distribution_account_type","id","is_default","name","sdp_ui_base_url","status","updated_at"],"example":{"id":"840dca45-d1df-44cd-83c1-65c04235c25f","name":"redcorp","base_url":"https://redcorp-backend.sdp.org","sdp_ui_base_url":"https://redcorp.sdp.org","status":"TENANT_PROVISIONED","distribution_account":"GCQVDMPOEN3HHJJ64V42KUTONOXN7C6V2PSVPALEVJ7PIYOB6M3DJV7N","is_default":true,"created_at":"2024-03-27T17:21:51.000Z","updated_at":"2024-03-27T17:21:51.000Z"},"title":"Tenant"},"title":"Tenants"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-tenants.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-tenants.api.mdx
deleted file mode 100644
index 7de1913e1..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-tenants.api.mdx
+++ /dev/null
@@ -1,62 +0,0 @@
----
-id: get-all-tenants
-title: "Get All Tenants"
-description: "Get All Tenants"
-sidebar_label: "Get All Tenants"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNWGtz4rgS/Ssq1VbtpNY2xpAwyzcC3gwkAYbXzJ0My8p2G2tjS15JDsum+O+3ZJsEAnnM3LlV+wmQW6dPt1rdx9xjRZYSN29wK0gow3MD8xQEUZSzboCb+AJUK44nwAhTEhtYgEw5kyBx8x47tq0/ApC+oKneg5u4hWIqFeIhSgW/o5JyBgFSBQJaURUhFQEVyOcspMuscKaxfc4UMKUhSZrG1M+fVP6UGvceSz+ChOhvap0CbmIiBFljA1MFidxZ596f4Cts4FToYBQt2NJgx0YqQdkSGxj+Jkka66Vqo3bmQVAzG96vjllvnNnm+zB0zNNq6NnvAezGryHeGJiRBI4h7adhEkEZNNIbLNRVSEY8iwOUEOXnSUApUQoEQ3/8fkPMf8z5Lz/9Ye1x8uIMfC5S7dcjEhaZiN/me9wZIo/4t8ACJEHcgfhZIg2BpqOrfSeRUqlsVipbZ2a5z5JBanGx1M5lkC4yuvh2DtNuJSAy8jgRATp/k/89v4qoTB49OJYlunAnbr/VnyzaI7c1cTvY2C4MR4NZd9wd9HcXW+1Jd7Zv13EfF+cbAwdUu/AyHceC+D7PmFqQIBAgj/I4EraCOCYClZtRuRllEgIUcoEeXbAlCjMWyP2EXLQ/t3q1z73a7LLW++1D7eN157fB+PLa6V9ffzkfD2qz7uTMnQ4/fhp3Pjm9Rv3aqY1G4yv8HP2C8/dw1zteJV6eRKc7noy659NJd9BftNrtwbQ/scYT9+qqNbLc/gwbL5t0zhez1vRq8pxduztqX7mPZs+e1vNFcxhwYavblb6Qu3APOXhj+HkZudjAQ7ff6fYvFtOxO9pWXHfQz/lSuQggJFmsduh5nMdA2AG/82IdhTFZIhWRvIOsJFpFoCIQOeOyx1BZ8C+wEReIcWXliKW3kMQSNgb2BRAFwYKoYwkKuUj0ExwQBaaiCexVpmM7ddOumU5jUm00nWrztPpFV12WBj8eNIAYngc90m5pAlKRJNUJYrvZWRGJ3kkeqhNUglrfS2ujZ+BfGRUQ6EN/aIh7iX2li7xcti/dYUNPsb0qKufRYYd+6J17pzPfibAYifh93Q58Uj81g2oQmvW6H5jva37VPDv17bpTO/Wd03DrpokFBPlA2p1HDx28fHgwQI7Mj6d7dm3L63u8kx9LTt4zP84618OB2699+NDrndVndedyOhn0B5/7jfbZzBmOZ8PWlTvrNYbd/wzOz65rnd6s0d/PZlOJDPbvyLE6sGzb/rKf2BfsNgZWVOU1VQipwxWJNxtdWnW7eqiopoxkKuKC/gPBd8ikZ+QQCMHF4cXa6AJRgrxBUB20WZYlHggNkYCUZHlk5hRh7pRgSQP3uUJ7YT6y2Pqp29Ud5Kc7/p/AObYEPxNUrXHz5h6fE0n9VqYi3LyZb+ZP29EFKNSKY/QonBNQEdfXbQl5JoneiivqwaAQaTJHL24I1rhbr2N9rEXez4EIEIXzRzGc0ktYH/TFVhlHXiMoAhJArrwVoUxPMcJyldb7NEHv3LFzenaiZ0exukCtYRfdwtp6vP57ePruaCcFrD73sTus2j+IGRq7Q7NqF9yKmNG94rfANiffxMip/0hGTv1HMPqYgVi/jVZuilIiSALqeUY7BHJKW8d/6e353KIs5Lm7svVstV6HSi8TEhJgCg1jovRg1GePDaxLsqDRsGzL1nWaJQkR6yd68TjGu3FneKK1CUGK8xh5GY1VLqW4WBJWpkgixVFCbgF5WXyLUrLWKPkqQUvBs1TLMwE+TWn+gN+V4mfrnYFacXFrvShp/x0Uv7KvbBJRmbtkiKfATMkz4YN+X9Z9tlB6VJZUOEOKp1uB+gTOQIQF+QOfB4B8wpAHKOQZC/KNkf4Rx3ylq0VAyiVVXFCQTc3DRDeywKuUn2awkyQzLZO0nefzd9uhvaQqyjzL50nlmxBOmigP/oHKelvOhX7dvrHqqCgLBZFKZL7KRBmgPhf12pla3xBZKPJp+r+EtoV4LbYVeGhr+93RRBAnph8RoeSLlHfsKkoAVBJCWaVceDGe18L4AHGCcqDinQjSmK91eb0aCcqktrvMPBAMFEjrq+5SCkQiB+EYxB31d/8PKGlqVVjJjUwemrI0M3BMfWAyn/XbxpsSPwLk5H3qUWU2K5XVamWR/GmOVm6Vlatu2+2PXdOxbCtSSZz3yZRLlRC2A3w4zvfazEMHV/C3qqQxoSx/KSr+JylG/Q3ejvq5gSMulV66v9eCeCrizUYvF626eTM38B0RlHi6Td/o18ZyemhtcAu697Z8H1ItJO5InBXD44kU1OLhQXRcuBO82fwXeGjR8A==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get All Tenants"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/tenants"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Get All Tenants
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-all-tenants.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-all-tenants.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-tenants.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-tenants.mdx
new file mode 100644
index 000000000..d034f87b3
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-tenants.mdx
@@ -0,0 +1,5 @@
+---
+title: Get All Tenants
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /tenants"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-users.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-users.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-users.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-users.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-users.StatusCodes.json
deleted file mode 100644
index 606e521b6..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-users.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Returns a paginated list of User Details","content":{"application/json":{"schema":{"type":"array","items":{"required":["email","first_name","id","is_active","last_name","roles"],"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"first_name":{"type":"string","example":"John"},"last_name":{"type":"string","example":"Doe"},"email":{"type":"string"},"roles":{"type":"array","items":{"type":"string"}},"is_active":{"type":"boolean"}},"example":[{"id":"7a4c6555-1f73-49b3-a211-f95bd2b8ec90","first_name":"John","last_name":"Doe","email":"email@email.com","roles":["developer"],"is_active":true},{"id":"5f4df1dd-c84f-482a-84ad-541ffd46e75a","first_name":"Jane","last_name":"Doe","email":"email@email.com","roles":["financial_controller"],"is_active":false}],"title":"User"},"title":"Users"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-users.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-users.api.mdx
deleted file mode 100644
index ee22285eb..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-users.api.mdx
+++ /dev/null
@@ -1,62 +0,0 @@
----
-id: get-all-users
-title: "Get All Users"
-description: "Fetches all SDP users within the organization, whether they are active yet or not."
-sidebar_label: "Get All Users"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNV99v2zYQ/lcIPjWA5V+x48RPy5a0azt02ZxiD2lQnKSTxZoiVfIU1zX0vw9HyY6dpEnbtcBeJFs8fvy+u+MduZYEcy+nV/KtR+fldUem6BOnSlLWyKl8jpTk6AVoLWZnF6JiM7FUlCsjKEdh3RyM+gxs3xHLHClHxyMrAQ4FJKRuUKyQhHXCWOrKjrQlujDhZSqn8gXSqdbN+h3p0JfWePRyupbDfp9f+5T+Rqqc8QJECXNlgDAVWnkSNhOMIs6QQGkGS6whNMQYUJZaJWHV3gfPQGvpkxwL4F+0KlFOJTgHK9mRirAIBBx+rJTDlD2EBSgtOzJTztN7AwWyZcoP/77RKTtSw+2gsxqDT1t4G3/AhGRHlo5dQKpRqdIdCp6cMnPZkfgJilLzp8Hk8CjG9DCaxCfDaDQ56kfHWTaMxoMs7h8j9icnmaz3iD2K98rmhu1vqT5qfmaRrRv59yzrjcxHvHhnRr3rsdvh2FqNYML4dvWrxj1yAqPkaDweR4NschiNTuLDCIaDQZSdjON0GB9jctLfj02rc09m0LKV0rx/Cc9uYottxKZXMsUb1BwkDt8OW3IV1p2W1DgbpdkgTaPkeJRFo+MhRMcjSKPxaJBl6egIJ2O4RwoMfi+pTBkwiQL9nhPbWa3v8ctAe6w55RSF6PGO4CDt/veyrtnLo/7g/vZ6a6Ci3Dr1GdPv2EJfyHF0zroHswc/kQP/NIInoGrXzlRF3Ggr0HuYP5DGjcxtMm1pyDeWxJ7MWxabdUb9wQ7y3Rk/E7gJzeH90Dy3LlZpiubnx+VhdbcEvsIg6PCYVE7RKuzkXxEcutOKcjm9uuYsLZByy1tpjoEb8JDsVW0z8Ohu+BdPrhzvDsmzNqAzFtno2IW+LUSleo1cifbdeNp6O3hM5AgpOsH+BGWUmQswodW9+udSPDufDcdHB9y7mq/vxenFS7HAFfexdv/u4XHd40UaWM7O2fnFoP+DmInZ+UU06DfcGs1iTXaBpj74JkbD0Y9kNBz9CEZ/VehWX0crmIoSHBRIX2a0QyBQ2iz8kac3jchkNizXlscZodbgxJnyceU8FmhIXGigzLqCYy87klOyoTHp9rvcdnxVFOBWciovcxSPYzybnV0cCMXnF7JWi7hSmkRm3d5RyguyooAFirjSC1HCilHCVxBzZ6uSjzsOE1WqMGBvmmPXdnWDtLRu0b3nu/8fxXfmnbnMlQ9LGmFLNJG3lUtQlM5y3RKUA/FwQ8UaQTbAPwDXEWDSMJDYFEUCRsQoMluZNEzM+Y/WdsnZ4rC0XpF1Cv2UeUTiyjd4vfYdpTtOisrWSVEMyQJNev0sJyr9tNebK8qrmHt275sQDqYiiN9SWW3S2QeyrVlQpUzmwJOrEqpcK5DjQk/FtPsNyjIXest/kbaBeErbEmOxsf1uNTnqIkpycOQfpbxj1yOH2CtAmV774VE9T8n4HXUhAlDgn2Kp7YrT60klovJs97qK0Rkk9N13XKUIXeH/zGboblTCdWkjq6XZtW7eC0aRzSLfmnWkVgkaH1rypvCWkOQohqFONT2Usaa93nK57EIYDWjtVN/74+Vv529m59Gw2+/mVOhQJ0vrqQCzA/wCSZxqLTYXt70is749n/ycK2TbHgg/Ua/UoMKFJshbt6eIK1ltrrS59cQf1usYPL51uq75c9MFplfXHXkDTkEcLhzXdWfTmPjYsUAu66dJgiWfUG5AV01funPm2jvNvDi/lB0J91rZIrSy9gejb4bMagf7bq9sKPCTbx4PTlmvm0ZZ11v7ZuiLM1qJG2t24HVd1/8C8yOQ2g==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get All Users"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/users"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches all SDP users within the organization, whether they are active yet or not.
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-all-users.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-all-users.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-users.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-users.mdx
new file mode 100644
index 000000000..384c66b5e
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-users.mdx
@@ -0,0 +1,5 @@
+---
+title: Get All Users
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /users"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-wallets.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-wallets.ParamsDetails.json
deleted file mode 100644
index 78c279809..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-wallets.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"include_deleted","in":"query","description":"When set to `true`, includes soft-deleted wallets in the response. When `false` or omitted, only non-deleted wallets are returned.","required":false,"style":"form","explode":true,"schema":{"type":"boolean","default":false}},{"name":"enabled","in":"query","description":"Filter wallets by enabled/disabled status.","required":false,"style":"form","explode":true,"schema":{"type":"boolean"}},{"name":"user_managed","in":"query","description":"Filter by user-managed wallets.","required":false,"style":"form","explode":true,"schema":{"type":"boolean"}},{"name":"supported_assets","in":"query","description":"Comma-separated list of asset codes or IDs to filter wallets by supported assets (max 20).","required":false,"style":"form","explode":true,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-wallets.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-wallets.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-wallets.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-wallets.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-wallets.StatusCodes.json
deleted file mode 100644
index a2db96fbe..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-wallets.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"A list of wallets","content":{"application/json":{"schema":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"created_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"}},"title":"Wallet"}}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-wallets.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-wallets.api.mdx
deleted file mode 100644
index 1d6d1f82d..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-wallets.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: get-all-wallets
-title: "Get All Wallets"
-description: "Fetches the list of available wallet providers to populate the dropdown box in the New Disbursement flow. The organization should coordinate with the wallet provider before selecting a particular wallet provider for a disbursement. By default, soft-deleted wallets are excluded from the response. Use the `include_deleted` parameter to include them."
-sidebar_label: "Get All Wallets"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWN9v2zgS/lcGfGoAyXbcpNn1W7pJe709dHPn9ApcGziUNLa4oUiVHMXxGvrfF0PJv2LHaboJsA+Xh9gWZz5+H2fEGXIuSE68GHwRn6XWSF5cRSJDnzpVkrJGDMQ7pDRHD5QjaOUJ7BjkrVRaJhphGtygdPZWZeg8kIXSlpWWhMElc7bM7NRAYu9AmfDsI07hTPmkch4LNARjbacduMwRrJtIo/6QPDn43FY6g9RalynDiFNFeYC4Ny8kOLYOwaPGlJSZgIRSOlJppaXbsh5bBxKyNQodeDuDDMey0hSBt2OKM9RImLXOHqRDwLtUVxlmMHa2CEQc+tIajx345BvF18oEo1ELcM1MZIGEjlenHWXToiMiYUt0Qe6HTAzEe6RTrRfBiMTSlYM0F0YWKAbi3gwiEopD9a1CNxP3A/g5RwMeiSe/JlfhdbQg4XcrbcO0khYgrsdSe7wG68AWigizCKzRMzDW7Fwsh1Q5gxmrdPitUg4zMQgokfA00yxlbF0hIoF3pbYZigETjIRPcyykGMwFzUo2S6zVKE0QF4LUAtV1tFwVNJySj6zGO6U5EAueyQxat26mfPgCniRV/jlZr7OsPLpRIY2cfCfVZAbsE7c+C+ovxc9XZWkdYTaS3jdJuIfjL7YoZOyR85Tjv9wh2BdSyzlmHXw4CzvDeGvxl7M1Hh5eFfIO+r2D55DnySkzEXV9xVhNMnse7/d6/LEp5XRJfrp8/VJrCA2xsSxLrdLwpnZ/9+wx355ROid5kRRh4dee2+R3TInfZ8fvO6mGh8q22bIsWZRB57HM5M+YHcdHx8cyPjr5qR/LHmJ8+KZ38uYEexkmh6KO2tDtQ/qvSpw0BKfeK0/sk9sCSzl5xC8nKv2g271t/GVZdlJbsL/HcnTYG6VaoaFRZgupzH4sWao4w9vONlaGWI60Mjejh2L4OKeuz0qGZ7zUoQwZTLuQOHt4RGSSMCZV4AZ8v9d/HfdO4teHl/3e4Lg3ODruvDn66X8MXJXZSwDXkSBFwajZ+kXNf5E42pWob2UG/8FvFXr6gRR9IBXROet2idqc+wxJKu1BJraiUCUax5qFkpOPJ31dL7Udbmv7ZGRFuXXqj7A7vqy47yctmpqwZmeqIsGgu0Dvd75Hjcxl/Jc0xEdLsCFzxWIxz1HvcA35vsdLAjeheb0dmnfWJSrL0Lx8XHarWxH4DoOgw2NaOUWz0Du9RenQnVaUi8GXK64JBVJuueuaYOAmeUh0V9u/R3e7aL0qp8VACPZbwA5ZZqNkHXxVDUr1K27XzNN2vZsmN0fJLSmvqFQmtK4GhmcX8M/Pl/DqfNg/fnPAJbR5OoLTiw9wgzOuj23F3sBblOsGlvNzeH5x2HsmZjA8v4gPew23RjPMyd6gqQ+exKh/9JyM+kfPwejf3OF8H61gutbXP8BojUCgtNlLcYYqM7Zhunb7HxJqPrFsHI8utCSuLRx7EQlOyYbGSafX6XGeVkUh3UwMBJ+h9mO8Gp5dHIDyIIGs1ZBUSlM4Ea2fvUK7VsgbhKTSN1DKGaOEpxImzlYlN0oOU1WqMGBv+XizNrtBmlp309lau78fxa/mq7nMlQ9TGrAlmtjbyqXIR0beuYBySTzcULEGyAb4HXARSJOFAW5/IZUGEoSxrUwWHHP+obWdcrY4LK1XZJ1CP2AeMXzxDV63/YzXz6lx2S5SnMj0Bk129WrRDk0U5VXStEJPQTgYQBC/pDJbpHNz6G/Ngiplxk56clVKlWsFclzosZh2nqBs7EJ1+SvSFhCPaZtiAgvbH1aToy7iNJeO/F7Ka3Zdcohdbpm77YO9eh6T8Q/UBQSgwD/DUtsZp9ejSqDybPdrlaAzSOg7X3mXInSF/208RHer0vWeu6XZsW7SDUaxHce+NYuEVikaH4ryYuMtZZoj9MM+1dRQxhp0u9PptCPDaEBrXX33Xx9+Of84PI/7nV4np0KHfbK0ngpp1oDfI8Gp1rC6K9nYZuarHuX/V1gvfIXV1krCO+qWms+BdRvredtUfRHT1f1ibj3xo/k8kR4/OV3X/LgpitxqLW5iluf+ByP7t7jb2in/Bmc7L+pupa4wNJLRU4Q+6dpqD6HVHdlfI7LnUmrP7Pfuvn6QwoveOe1hv+NmbKXgin84xRLC8SJadJec0I3/aZpiSWteW0enjUPJ+/NLEQm51Y/ehH60/cLoiyEzW8O+3/A2FPg/L/ZOl/m86XbremnfDD3o0UpcZbuor+q6/hMPH4dw
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get All Wallets"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/wallets"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches the list of available wallet providers to populate the dropdown box in the New Disbursement flow. The organization should coordinate with the wallet provider before selecting a particular wallet provider for a disbursement. By default, soft-deleted wallets are excluded from the response. Use the `include_deleted` parameter to include them.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./get-all-wallets.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-all-wallets.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-all-wallets.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-all-wallets.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-wallets.mdx
new file mode 100644
index 000000000..76e70658c
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/get-all-wallets.mdx
@@ -0,0 +1,5 @@
+---
+title: Get All Wallets
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /wallets"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-api-key.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-api-key.ParamsDetails.json
deleted file mode 100644
index 363e7e2e2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-api-key.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"The unique identifier of the API key","required":true,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-api-key.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-api-key.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-api-key.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-api-key.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-api-key.StatusCodes.json
deleted file mode 100644
index 41e38f1bf..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-api-key.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"API key retrieved successfully","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","description":"Unique identifier for the API key"},"name":{"type":"string","description":"Human-readable name for the API key"},"permissions":{"type":"array","items":{"type":"string"},"description":"List of permissions granted to this API key"},"allowed_ips":{"type":"array","items":{"type":"string"},"description":"List of allowed IP addresses or CIDR ranges"},"distribution_wallet_ids":{"type":"array","items":{"type":"string"},"description":"IDs of the distribution accounts this API key may act on.","title":"DistributionWalletIDs"},"expiry_date":{"type":"string","format":"date-time","description":"Expiration date of the API key"},"created_at":{"type":"string","format":"date-time","description":"When the API key was created"},"created_by":{"type":"string","description":"User who created the API key"},"updated_at":{"type":"string","format":"date-time","description":"When the API key was last updated"},"updated_by":{"type":"string","description":"User who last updated the API key"},"last_used_at":{"type":"string","format":"date-time","description":"When the API key was last used"}},"title":"APIKey"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-api-key.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-api-key.api.mdx
deleted file mode 100644
index 3b8649f8b..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-api-key.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: get-api-key
-title: "Get API Key Details"
-description: "Retrieves a specific API key by its ID. Returns the API key details including permissions and restrictions, but does not include the actual key value for security reasons."
-sidebar_label: "Get API Key Details"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWN9v2zYQ/lcOfEoA+UezbAP01tVp67XYvLhFH9IgoKSzxUYiVfIYxzP0vw9HSYliu0nTpsC2pzgi77vvO1LHT9wIkksn4jPxfDaFN7h24jwSGbrUqoqU0SIWp0hW4RU6kOAqTNVCpcDTL3ENyRoUOZhOhnCK5K12QDneDGdIUhUOlE4Lnym9hAptqZxTRjuQOgOLjqxKOZeLIPEEmUEH2lAbhAFQpuRlETCvZOERFsaCw9RbRWuwKJ3RbigiYSq0ktGmmYjFK6Tns+kbXItIVNLKEgkt690ILUsUsVCZiIRinZWkXGyLf5cjeK0+ewSVoSa1UGjBLPoqRSQsfvbKYiZish4j4dIcSynijaB1xWlYpF6Kuj7nya4y2qHj8aPxmP/czdqVz7alz8D5NEXnFr4oOF9qNKEmjpRVVag0SB59chy+2U1vkk+YEhfBcoFINclVtktxuwLvd9Rz6fvy66gt5kNQr30p9cCizGRSIHDQPrDeFulhSmslS1eEpdtT2e1kb5UjXqj+hltaqQkzIAOUK9dPKovCrDC7UNVTJG3RYDoDmWUWnUMHxsKL6eQUrNRLdCFYMVDiOfpiJYsC6UJl30NgOnHd7uyDg0xT4zW5O7qhlGt+s8BofnVIUcHYk17gh0BqOgl08bpSdn2RSdq72AtjS0kiFjxhQKrEnR1wwghhrwJP2n6R6kikFiVhdiHpG1N8yFHf6UEr6aBF7SdI1l+x9x1aWOWmi98m66vsB5AtpCNooftZHsW4D7JNm8cuvPtBxB2zrm+3U9uA65ofHo+f7ba791p6yo1Vf2P2dM0NrTV27yuD12SlexjBkSTfn6d9maBliBKdk8s9r0Hd6MRrWVYF9niIPwzBHZ23NLpEx+NnPejtiLor4U+7JXxpbKKyDPWPr98X5N0y6Gge79JkRS+N1//zZV60Evet8HF/hU/RGW9TDH6niapb6M7cBLPyG0qL9rmnXMRn52wiSqTcsMVZYlDE5iUWI1mpwSWu3Wijslowir3qHI+3hYiF4OgOfM5FbqrQT3F7/FSqMU9b/qTdlE0nz1FmaIHXUyrNJk9qmE9m8PuHd3BwMj/6+ZdDPvyapxddy+AjpzVhd/A6P9bA8irMT2bPxk/EDOYns8GzccOt0QwbMpeo68NHMTo6fkpGR8dPwegvj3b9dbTCVLjxxF9i1CMQKHWJP3N4aPNKL0xI17b7OWFRSAsT5RJvHZaoCWaFJD5VeO1FJHhLNjR+HY6HY96nviylXbeO+36Mg/lkdgiKv0fImAISrwoKRtLYpdRtiRy7vFJeIiS+uIRKrhklPJWwtMZX7D4spqpSYcBcYWNFu+waaWXs5XDvR8G/i+JH/VG/Y2fHKTWYCvWg7SyVNdz1gHJJPNxQMRrIVJ3/2oKLwpcZD6QmQ0ilhgSb9hQCc/6HHS7vFouVcYqMVehi5jGAM9fgjdq/g6xXpEHVFmmQyPQSdXZ+kBNVLh6NlopynwxTU44ehXAYQxB/Q2Xdbefma7SdFlQpvbDSkfUpedsK7L5B7l3T4SOULWw4275HWgfxkLYVJtDN/WY1ORblIM2lJXcv5d68EVnEUSmVHrUP7tXzkIzXWJQQgAL/DKvCrHl7PagEvON5b3yCViOhG37kLkVoS/fnYo72SqXclzpZLc2hsctRmDQwi4Frp0WiUClqF070rvFWMs0RjkKfas5QxopHo9VqNZRhNKC1oW70dvri5I/5yeBoOB7mVBahT1bGUSl1D/gVErTXLjBpLkq2W83m1iX9x+5h2tOH8JpGVSGVDl8yXL1Na1bORGdWRCRilfHNU24c8chmk0iH721R1/y4OW3is/NIXEmr+PYgOJpMOf6diXghC4f3FO/gtL2hOYSvvNLZK6A7UzXPCAVgRxUJDgl3SfV5HXWnMjNsBp6nKVbUC9kxvHcs3auTdyIScuccb4i1Pxh9L51to9BQaD79vhCy2TQuoa5v5jdDX4xoJd4oZwV1Xf8DaMwXbA==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get API Key Details"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/api-keys/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Retrieves a specific API key by its ID. Returns the API key details including permissions and restrictions, but does not include the actual key value for security reasons.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./get-api-key.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-api-key.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-api-key.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-api-key.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-api-key.mdx
new file mode 100644
index 000000000..c07c44e8f
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/get-api-key.mdx
@@ -0,0 +1,5 @@
+---
+title: Get API Key Details
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /api-keys/{id}"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-bridge-integration.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-bridge-integration.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-bridge-integration.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-bridge-integration.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-bridge-integration.StatusCodes.json
deleted file mode 100644
index a5a7d31b3..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-bridge-integration.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Bridge integration status retrieved successfully","content":{"application/json":{"schema":{"type":"object","description":"Complete Bridge integration information including status and related data","properties":{"status":{"type":"string","description":"Current status of the Bridge integration","enum":["NOT_ENABLED","NOT_OPTED_IN","OPTED_IN","READY_FOR_DEPOSIT","ERROR"],"example":"OPTED_IN","title":"BridgeIntegrationStatus"},"customer_id":{"type":"string","description":"Bridge customer ID","example":"cust_123abc"},"kyc_status":{"type":"object","description":"KYC verification link information","properties":{"id":{"type":"string","description":"Unique identifier for the KYC link","example":"kyc_456def"},"full_name":{"type":"string","description":"Full name of the person undergoing KYC","example":"John Doe"},"email":{"type":"string","format":"email","description":"Email address for KYC verification","example":"john@example.com"},"type":{"type":"string","description":"Type of KYC verification","enum":["individual","business"],"example":"business","title":"KYCType"},"kyc_link":{"type":"string","format":"uri","description":"URL for completing KYC verification","example":"https://bridge.stellar.org/kyc/456def"},"tos_link":{"type":"string","format":"uri","description":"URL for accepting terms of service","example":"https://bridge.stellar.org/tos/456def"},"kyc_status":{"type":"string","description":"KYC verification status:\n- not_started: KYC process not yet started\n- incomplete: KYC process started but not complete\n- awaiting_ubo: Awaiting Ultimate Beneficial Owner verification\n- under_review: KYC submission under review\n- approved: KYC verification approved\n- rejected: KYC verification rejected\n- paused: KYC process paused\n- offboarded: Customer offboarded\n","enum":["not_started","incomplete","awaiting_ubo","under_review","approved","rejected","paused","offboarded"],"example":"under_review","title":"KYCStatus"},"tos_status":{"type":"string","description":"Terms of Service acceptance status:\n- pending: Terms of service not yet accepted\n- approved: Terms of service accepted\n","enum":["pending","approved"],"example":"approved","title":"TOSStatus"},"rejection_reasons":{"type":"array","items":{"type":"string"},"description":"Reasons for KYC rejection (if applicable)","example":["Incomplete documentation","Address verification failed"]},"created_at":{"type":"string","format":"date-time","description":"When the KYC link was created","example":"2025-01-01T00:00:00Z"},"customer_id":{"type":"string","description":"Bridge customer ID","example":"cust_123abc"}},"required":["id","full_name","email","type","kyc_link","tos_link","kyc_status","tos_status","customer_id"],"title":"KYCLinkInfo"},"virtual_account":{"type":"object","description":"Virtual account information for USD deposits","properties":{"id":{"type":"string","description":"Unique identifier for the virtual account","example":"va_789xyz"},"status":{"type":"string","description":"Virtual account status:\n- activated: Account is active and ready for deposits\n- deactivated: Account is deactivated\n","enum":["activated","deactivated"],"example":"activated","title":"VirtualAccountStatus"},"developer_fee_percent":{"type":"string","description":"Developer fee percentage as a string","example":"0.5"},"customer_id":{"type":"string","description":"Bridge customer ID","example":"cust_123abc"},"source_deposit_instructions":{"type":"object","description":"Bank deposit instructions for sending USD to the virtual account","properties":{"bank_beneficiary_name":{"type":"string","description":"Name of the bank account beneficiary","example":"Stellar Bridge"},"currency":{"type":"string","description":"Currency for deposits","example":"usd"},"bank_name":{"type":"string","description":"Name of the receiving bank","example":"Wells Fargo"},"bank_address":{"type":"string","description":"Address of the receiving bank","example":"123 Main St, San Francisco, CA"},"bank_account_number":{"type":"string","description":"Bank account number for deposits","example":"1234567890"},"bank_routing_number":{"type":"string","description":"Bank routing number","example":"121000248"},"payment_rails":{"type":"array","items":{"type":"string"},"description":"Supported payment rails for deposits","example":["ach","wire"]}},"required":["bank_beneficiary_name","currency","bank_name","bank_address","bank_account_number","bank_routing_number","payment_rails"],"title":"VirtualAccountDepositInstructions"},"destination":{"type":"object","description":"Destination configuration for converted funds","properties":{"payment_rail":{"type":"string","description":"Payment rail for destination","example":"stellar"},"currency":{"type":"string","description":"Destination currency","example":"usdc"},"address":{"type":"string","description":"Stellar address for receiving USDC","example":"GDQP2KPQGKIHYJGXNUIYOMHARUARCA7DJT5FO2FFOOKY3B2WSQHG4W37"},"blockchain_memo":{"type":"string","description":"Blockchain memo for the destination transaction","example":"12345"}},"required":["payment_rail","currency","address"],"title":"VirtualAccountDestination"}},"required":["id","status","developer_fee_percent","customer_id","source_deposit_instructions","destination"],"title":"VirtualAccountInfo"},"opted_in_by":{"type":"string","description":"User ID who opted the organization into Bridge","example":"user_789"},"opted_in_at":{"type":"string","format":"date-time","description":"Timestamp when organization opted into Bridge","example":"2025-01-01T00:00:00Z"},"virtual_account_created_by":{"type":"string","description":"User ID who created the virtual account","example":"user_789"},"virtual_account_created_at":{"type":"string","format":"date-time","description":"Timestamp when virtual account was created","example":"2025-01-01T00:00:00Z"}},"required":["status"],"title":"BridgeIntegrationInfo"},"examples":{"not_enabled":{"summary":"Bridge service not enabled","value":{"status":"NOT_ENABLED"}},"not_opted_in":{"summary":"Organization not opted in","value":{"status":"NOT_OPTED_IN"}},"opted_in":{"summary":"Organization opted in, KYC pending","value":{"status":"OPTED_IN","customer_id":"cust_123abc","kyc_status":{"id":"kyc_456def","full_name":"John Doe","email":"john@example.com","type":"business","kyc_link":"https://bridge.stellar.org/kyc/456def","tos_link":"https://bridge.stellar.org/tos/456def","kyc_status":"under_review","tos_status":"approved","created_at":"2025-01-01T00:00:00Z","customer_id":"cust_123abc"},"opted_in_by":"user_789","opted_in_at":"2025-01-01T00:00:00Z"}},"ready_for_deposit":{"summary":"Virtual account created and ready","value":{"status":"READY_FOR_DEPOSIT","customer_id":"cust_123abc","virtual_account":{"id":"va_789xyz","status":"activated","developer_fee_percent":"0.5","customer_id":"cust_123abc","source_deposit_instructions":{"bank_beneficiary_name":"Stellar Bridge","currency":"usd","bank_name":"Wells Fargo","bank_address":"123 Main St, San Francisco, CA","bank_account_number":"1234567890","bank_routing_number":"121000248","payment_rails":["ach","wire"]},"destination":{"payment_rail":"stellar","currency":"usdc","address":"GDQP2KPQGKIHYJGXNUIYOMHARUARCA7DJT5FO2FFOOKY3B2WSQHG4W37","blockchain_memo":"12345"}},"virtual_account_created_by":"user_789","virtual_account_created_at":"2025-01-01T00:00:00Z"}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-bridge-integration.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-bridge-integration.api.mdx
deleted file mode 100644
index cdc820376..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-bridge-integration.api.mdx
+++ /dev/null
@@ -1,64 +0,0 @@
----
-id: get-bridge-integration
-title: "Get Bridge Integration Status"
-description: "Retrieves the current Bridge integration status and information for the organization."
-sidebar_label: "Get Bridge Integration Status"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWm1v2zgS/isEP7WA3+Km211/ujRO2rTdJI2T6/XSQKClsc21RGpJyllv4P9+GIqSKPk12y5wd0XRJhI575x5ZsQnGoEOFU8Nl4IO6A0YxWEBmpgZkDBTCoQhbxWPpkC4MDBVDJcSbZjJNGEiIlxMpEryxxOp7E6ppkzwP+3DzjdxAyZTQpOYL4BEzDAyUTKxKx3tk+sLwkUYZxEXU/Lx66nPYcGVyVhMWBjKTBgSgWE81p1vgraoTCGX6SKiAzoFk1O8qISlLaohzBQ3Szq4f6JvgSlQJ5mZ0cH9w+qhRRXoVAoNmg6eaL/Xw//qhtluAuVMFhGdhSFoPcnieElbNJTCgDBIi6VpzEO7rfubRoJPVIczSBj+ZJYp0AGV498gNLTV4HwqkzQGA5u84Ju+sp5nOQUxMxBZm9MWTRVay/Bc0XydJ4E2iovpugQuDBxdOfEdx2t2BpEldHBPL69ug7PLk7efzoa0ZX+7ur49GwYXl7RFvR9vzk6GX4Pzq5tgeHZ9Nbq4pS16dnNzdUMfWhT+YKg6Hfg7DDf20ZqXR7k2qxYNM21kAirg0X7lnBrFHnKBAlec8Xlw1H/FxiGSni/DYM1sWxyHQbwAxSfO8yTmYu67bM0hh8h7J/jvGRAegTB8wkGVZw75IYua/Cjw8eufIpig+BiagWAJ7OdznsUxwaWFv1NQWgqSiQjUVLpTWuP1Qc4EGUpATpAwHm/ikmtPB25Fk+0ZPiUsihRobVVrmrHG8jc5E/9wv3ZCmSDrnOM+/W6XqVVtE3kXxFxEfMGjjKGY40xzAVrXA7N8WgXmx6+nSLuIFuuRXXbIFF938s0nq3uYn/0iJW41w8yYVA+63bEN5o42EMdMdaSadufLsFsFgJH6+yRiYQipFciASmwy0KAWPIRDBTJSewJtPFBbXLZ2oPKNg2+iTYQ0SEcZiAbWVqmSmIzxBVmCTV74Etdy4ewK9aVuCRlnxm4rVuEe9sg4qh1kYzkgJ+43chcbnjBMziBgwkPOYnL1KEDVBEUC9twEChYcHnO2OhsnXGteHCqSv7Tc0lTJRaFKTefiFS5TgIln47LiFS5LWaabZsmf4Vs5mYwlUxGuOC2yYPXwm38iPCvTFq3sSFvUNxBtUV9dfOukplhrc8kw+1khsIaX7OrHq0HFO2JVtseQPjSCbouYHeUx68KZiRD8YEpBYCEdkNtGjJfRlO/LDVg5a215tcwzoqPuW6WmtGerQuHbq1GlcG5ALkWggGkpfL2ZUgyxBzeQbLDHqmmQm5xCmWhL2uQFnxAHW8YxvPRP9z29KD1PIhlmCQhTJKUTl7pr0ThhPEY1sTgrQEQSMLMzB0XMQNvwBNZ8+GUGolbvyCPTxJGtJaF+r/+63Ttq945ue72B/fvvvxUfWOf8nnEFka0fKE5VcltlybMcvfLg5eVaRqwFd13uh9pp+MTF/EJMJGrnwHLgwPJ+nPLPBrpu4vm70ZBEkErNjf7BkKUB7GuWXbDgzc+//LH8E5U69IA3dfEONQsNXzCbLU8KTXX+FBxWZtHSilZoi9si2LzRe1473eVTK1v1W/2Ie4sKNzrRHYvquEewgBhNHkwAghRUCGLj2albYlhsIxOw4A23sSkQpgkj5aZKpl7n9d8MnrXMVAiBs27AhTYqs9nmADT9lol54Rjib7Ue03lOtbFq5JbYqkfumIl5MC7KtloeiIsvPUiMJMpQ80jVjDDKsY/rl3ITYz8VLg/tvMJ6VNaoZzpCklaZ5yugIAS+QMMhgRrhLxDHmpwzNZUlAwfL9/MoisB+Nkf9V+RXxgUZmRYZMUHOFRMh16FskdOTinNu5EBkyRjUAYHpeybftN2GR/1Xx69/evPzL72Sn5KZBTPP4uc2OX4NFke9Xq9//DNySNkSK2agcIjxHcV7lKWptIjVUSSW4lZFMTnNaIs+cgX0oVmtNp8HL1r9KGsExGYvbbZlU/+HbSlwmKtw4aeJ3AaGixxu7M0aw2oxCaWY8GmmqsoWSrEAa8BJJqL14uYLuj8Grj0nOB9UkvrB4Lqh56WCmiaVS2qZwGbZgw9pkZj8Zrs6qXejYb27fzf8fN3/eP353ceL918/vPvX5d3F16tf35/c3J3cnJ68GX64fX1+1T8/v7r6+PXV2/6X0ef3746/vHpjz1Qsw3k4Y1wECSTygPNUbiC4oQQMnkmJUUxoFq6Z1x7nNTBW82UtqguD7QjEyo8bMV6J0DbX6npR3V0H6/G9VaQC7EnsLgIugvEBIXSnbYkmjzNJ7Ma1US1O82RRqerBBQrhWI3nX4bwtzwBbViSkkcE8zUJcsG2ybEN0jdAb1B0Gc81i9u3F5z69tjG+0eZpzn9fl6704hXF6oPOwapRWw5yjaTYOMPAjtBiwp1liSIc0oE6PfHxboWXbA4A3/SXJsLo2hIt4inOuErPyiQbBEYW+mWQ+KVF6Q7iBYEW/lgpOzK16l74+caPK4B3OYsyy7wxq+16Ws1Ky1HpeuzzGKU6U8Zq5HigUM/f+Z34FiursnaEMabt/izCj/sN8fiLus1c1l1whoJZ1eYs2gZTKQqMmvd983WsDjqZeu30fWbPlDsioEN3bddVXWzVTPb6BU3tnm2LdvNck9btaXPafYlPhaxXUWtqai1A81uYB+I34Lhfdy9BXZ7uHkNNjfQ7BowrIO3EnQ19Qw9BPAdIGcDxvGAyK7y5Ef6rlKyLfDxT4se947WP1reCZaZmVT8z/yE/tUPknVUDErJDS2RrRhGsY29/J4Pj87fqxZNQGs23dDGOj3LclfKQS+lITU9KzEKRse9I490c0dpwlfrJjyXasyjCMTfb78t6lUSFGIer4uJGp3LTPyfu3niVNzk4WPfwzeQZ0WLHPJdxUkxbGqzh0Mu/j2BByRhZtJdJLA5By8JUFcw27xxqUAtQGl7pyBTmGQoXiYo7hqM0NC5JfwbB1W7n/KPsFyfnbjAzEHKDBh+GkKfMi6wMWOCjIbX5MOXW/LibNR//dNLgt/l7NPA3qOYw7JDW9Rl7ho9+9UGgYAli54YnV0f9X6QZGR0dt0+6uWy5TqTJyPnIFYvnyVR//hHStQ//hESfc5ALQ8Tyy4lKVMsAbNdIk8AK1LB+HfcbusGjuItO4fVi5o95HqcKQ123nAdM4NdBfoeawgonYvxptPrYGmtMNDtDMhuGi9Gw+uXdjBOjJQxGWc8Nrb99rs0jUPWhM2BjLN4Xoyf7FNGpkpmKY7+FIQ85faFXEDewBfcBZhHqead9ebnv07Eb+KbuJ1xbVli2wCi7bJLqiRmPmJmzH4UyEXB2YRMi+Fng1zLAk57u0pGQEImyBjyFGU3zvCXOJaPGC0qx3RSccCPGPg94t4Bma77vx15RmqnzkjtMQvnIKKHFwXkn3Izy8bYV3SfReHlgFjlS1GWRThrNwO3y4qbYIrl6DNTTsFicrPTp51naDZRtr59j2oFiX26PcKYFGv/sjYziJN2OGPK6J0ie+u6RgF0E8ZF1z3Yqc8+Nd5DnBBLqBgNx3Jpr3DsPWvYeE7Jx2wMSoABd+XOXv24mriP6F5fWWsocVFbTtrV/ZCYhyC0repF4k1ZOAPSt3kqr6FIa9DtPj4+dph9a6m5rbr76eL07HJ01u53ep2ZSWKbJ1OpTcKER/gdlNcWvQpPRtWkzks6TxVm+l+8AemKkYE/TDeNGRdYs6wxnxyAuacbAMxDi86kNvj26WnMNNypeLXCx3kBGtw/YEesOI5z7E3JVlETEfHMASvKib3hULXO65Bz5aOqd2fYQLO1Kjq3VdT9gNSLV8Jry9fKdC4C/rtqbdny9JTX6NWqXJ+/2rrDqVisRms+rFar/wBwag44
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get Bridge Integration Status"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/bridge-integration"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Retrieves the current Bridge integration status and information for the organization.
-Returns live data from the Bridge API including KYC status and virtual account details.
-
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-bridge-integration.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-bridge-integration.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-bridge-integration.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-bridge-integration.mdx
new file mode 100644
index 000000000..6b95ef569
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/get-bridge-integration.mdx
@@ -0,0 +1,5 @@
+---
+title: Get Bridge Integration Status
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /bridge-integration"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-audit.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-audit.ParamsDetails.json
deleted file mode 100644
index 9bf3d3e70..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-audit.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"The unique identifier of the distribution account","required":true,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-audit.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-audit.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-audit.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-audit.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-audit.StatusCodes.json
deleted file mode 100644
index 79dce2e1d..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-audit.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Access history retrieved successfully","content":{"application/json":{"schema":{"type":"array","items":{"allOf":[{"type":"object","description":"Grants one user one role on one distribution account.","properties":{"id":{"type":"string"},"user_id":{"type":"string"},"wallet_id":{"type":"string"},"role":{"type":"string","enum":["financial_controller","developer","business","initiator","approver"],"description":"The role the user holds on this account. Owner is always tenant-wide and never appears here."},"granted_by":{"type":"string","description":"ID of the Owner who granted the access"},"created_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"}},"title":"WalletMembership"},{"type":"object","description":"One grant or revoke recorded in the append-only audit history.","properties":{"operation":{"type":"string","enum":["INSERT","UPDATE","DELETE"],"description":"The change that was recorded. `INSERT` is a grant, `DELETE` a revoke, and `UPDATE` a change to an existing grant"},"changed_at":{"type":"string","format":"date-time"}}}],"title":"WalletMembershipAuditEntry"}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-audit.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-audit.api.mdx
deleted file mode 100644
index 6b17333ca..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-audit.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: get-distribution-wallet-audit
-title: "Get Account Access History"
-description: "Returns the grants and revokes recorded against a distribution account, newest first, from an append-only audit table. Owner only. Archived accounts remain queryable. Capped at the 100 most recent entries, with no pagination, so older entries are not returned."
-sidebar_label: "Get Account Access History"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWNtuI7kR/ZUCn8ZA62LHSQC9edfaWWc3M87Ig33wGGOqu6Tmik32FKulUQT9e1Bkty1bsr2eTIAgyIsvvBTPqSpWHfZGsZ4HNbpW5yYwmWnDxjv4TVuLHNRNpgoMOZlahtVIfUBuyAXgEmFO2nEA7QogXPoFBiDMPRVYgJ5r4wKDhmLXrs5z3zjOwOEKA8PMUOAMZuQr0A50XaMret7ZNeimMAyspxb78H7lkEDG+3BGeWmWckYyJqdW2jj40iCt0/ofxVIBmiPQ4+EQKh9Y4KFjQMdkMGSwMlyC81DruXFaEGYQPHhbIHWrQBOC87JZqGPRV5nyNVJcf1GokXqLvOu95Lwzwa8yVWvSFTKSeHmjnK5QjZQpVKaMeLTWXKrHbr4qERpnvjQIpkDHZmaE/yzSOeRRlSnCL40hLNSIqcFMhbzESqvRRvG6ljNll5ur7fZGFofau4BB5k+GQ/n1EMJZnmMIUJrAntbCngyK20MTZ2aNtWuVqdw7RsdiQNe1NXn0y+D3IFY2+yg0kZZ9hrGKp2tr38+ib9oVfvo75rznk7cp3bxDaELMBgTyFsG7+Pcht0isapJosUlcTXHAI5kSi5+fmFvFeD41KxD2JzKFrqnkXs2M0y432n4WT5G3FilyW6IVYCpT0yYYhyHElDBsNHsZ1nVNfom0fwslPSJ1SYfojNLbQnwDXJpwx769NzJiV3odgNFpx72VKTDeW4dLpHjtNAUokbAvnOLNxuLzdH2I2UMsF+ddXqbDVqWHdn8c1TFbxGpOqMWq5kNWZ54qmVGFZuyxqTDGpS5euWebKTYsMVHpIv4dqylSKE2tttlLSfbetXUNPLVV7b6oGZcY7VWp9pLsZ9tdnXguQy7eTcYfrlSmPl6en12NVabOx7+Or8aH456X2s0l8pphpe9Lbh9uk6HbGO/EIoPbZOsWdEsni4G/TWfJcGfQSwXGryawcfO0PUYtTr8qAlJgnopBLItjx7SWhRKt0+HxfvX56HTDpSfzTyy+ocjcRfdhOJDI08FbjF+ZdHjZQmDNze461wgzMVFhCHp+oBa0PPGrrupUK1oc6p1neMDzHkZ30OnweMf04x13LvzTvgt/8jQ1RYHuP++/J+jdI+hgnu7DFEY/+cb9j4d51lI8FOHT3Qh/wOAbypPmSLu2remAeUOG17FZ/oCakM4aLtXo+kauXIVcetEjc0zCQ6bUYLcv9lIvC4ONKbYD3UqUgLTs9ElDVo2UEnvdcRNxe/LL7qH3Hb02v+B6r5SetWkaYwglahFVEmFtnFQY7WByfgl/++0K3ownJ3/+y5HU3DT6Gc4uL2CBsaS2kumBvU49JbMSl8n48nj4nZDBZHzZOx4mbIkzbNgv0G2PXoXo5PR7Ijo5/R6I/iEy+Y/BikvhTsE+hWgHQITUHRwFeezIxs18PK7tChNGazXBuQnThgJWIssvrWbpJxJ7lSlJyQTjr/1hfyh52lSVpnXbCJ+38WZyfnmUOiF7b2HaGCv3icDTXLvWRUHaXqUXCNPGLqDWa7ESR6WD+qYWcUOYm9rECdFjUQR0pzvkladF/6CE/++C+Ml9clciD+VIB75G12trTU1e6mBSFSa0UERO+rqTd4/MJR0hE7kvEHLtYIqpYCUdKv9Y61eSLYS1D4a9PKhGgqMH1yHZG7S/e8WOk3p166TeVOcLdMXNm5K5DqPBYG64bKb93FeDV1k4GkEkfwdl3aVzes22yyIr42akA1OTc0MtQYkLvxTT/iuYzSh2u3+HWmfiJW4rnEK39pvZlGirXl5q4vAs5J11AybEgTzOB+3As3xeovEz2gqioYi/wNr6taTXi0xAXlhz+KWZIjlkDP1PUqUYqQrvZxOkpcmlLnW0Wph9T/NBXNTzs15ol2XKmhxdiD2+K7y1zkuEk1inUg8VW6PBYLVa9XWcjdbarWHw68WP43eTce+kP+yXXNlYJ2sfuNJux/BbZDhLzzlon+Q/p9fG44qzuZdP//9Mkz7TtN2N8SsPaquNi09Kic6mlUfX6pA8UpkaxS80SSHdZKr0gWX1ZjPVAT+S3W5lOHW40fVNppaajLCKKqowQf4u1GimbcBnIvXmQ/vZ5gi+5aPPQYZdU3eSI0ttG/lPZWqB6/TpaXuzzTpZIHDThKRXzTtb9jT4A5X5dnwVPfRYSCyikGj/2Pms8xDOY6WSIMjPnUf6wy2bTZIp2+3d+jT15I6W4h1zYbDdbv8Fi2BeeQ==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get Account Access History"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/distribution-wallets/{id}/audit"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Returns the grants and revokes recorded against a distribution account, newest first, from an append-only audit table. Owner only. Archived accounts remain queryable. Capped at the 100 most recent entries, with no pagination, so older entries are not returned.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./get-distribution-wallet-audit.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-distribution-wallet-audit.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-distribution-wallet-audit.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-audit.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-audit.mdx
new file mode 100644
index 000000000..e9b3ab955
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-audit.mdx
@@ -0,0 +1,5 @@
+---
+title: Get Account Access History
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /distribution-wallets/{id}/audit"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-balance.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-balance.ParamsDetails.json
deleted file mode 100644
index 9bf3d3e70..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-balance.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"The unique identifier of the distribution account","required":true,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-balance.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-balance.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-balance.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-balance.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-balance.StatusCodes.json
deleted file mode 100644
index 6199001f4..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-balance.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Balances retrieved successfully","content":{"application/json":{"schema":{"type":"object","description":"Live on-chain balances, keyed by asset. Non-native assets are keyed `CODE:ISSUER`; the native asset is keyed `XLM`.","properties":{"wallet_id":{"type":"string","description":"The account these balances belong to. Absent on the aggregate total across accounts."},"balances":{"type":"object","additionalProperties":{"type":"string"},"description":"Asset key to amount"}},"title":"WalletBalanceResponse"},"example":{"wallet_id":"8d1f6a2e-3c4b-4a5d-9e6f-7a8b9c0d1e2f","balances":{"USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5":"12500.0000000","XLM":"104.9999200"}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-balance.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-balance.api.mdx
deleted file mode 100644
index 5afe5342c..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-balance.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: get-distribution-wallet-balance
-title: "Get Account Balance"
-description: "Returns one distribution account's live on-chain balances. An account the caller has no access to is indistinguishable from one that does not exist; both return 404."
-sidebar_label: "Get Account Balance"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWG1T2zgQ/isafbky49ghpKW4nwIJlGtKUwKld5RpZXsd62JLriQDuYz/+83KdkhIgOvLzdxdPkCQd1fPs7vWPmJODZto6l/SPtdG8aAwXApywdIUjKZXDo1Ah4rnuEx9egqmUEITKYBEyx4sDGUhzC+apPwaiBStMGFckIClTISgXdJbGBGTAAlxC0USpomQ+AS0JkYSrgkXGJqLScF1woIUSKxkZvc0CTMkkoBOhsAt1+YVCaRJiLLISLfddalDZQ6KIbDjiPr0CMwyvYrdfoWMOjRnimVgQGEi5lSwDKhPeUQdypF0zkxC72fiLAFSCP61AMIjEIbHHBSRsSW3KTXUoQq+FlxBRH2jCnCoDhPIGPXn1Mxy3BO9xISW5RUa61wKDRqfd9pt/LUKoWagkbvicA0R0YVNZFyk6Yw6NJTCgDDoyvI85aHNifeHRv/5+v4y+ANCs8Z1uLGkDpnCDCISzAjTGoxLTqRoCWbQ2q5owhTUVl8O3vUH/vF4fD44/fLKZmnZFOteG34cvv2CNcwVVtHwKgM3tmifebSerk2lWWo1DQvIJIBUigkx0iW9QIMwRAqLhU0mCibMADHSsJSwUEmtmzDapaVDmyibEsaiiOP2LB2twL5X2PtQe5b7FGbY+iyzfVKWDjXcpOi30qqndUdgGLhlWY4mK5mhL6Pt+AXrQGsn7AatLnsetfbgRdzaZS+DvbAdbUMnpqtMzsf9A/9of7/f3T0+fDG8eLM72n3bH3wYH1yc7vZH5xcfdk5+2+mfvR98OBx2T3pn3d771zu/D4eHw95z6tPtzvN2221XH+rQj8O3uNruunt7e3vYuCV+HNptb6/38LlghUmk4n9C9CMNu9osoJRUG9MPt0axjRVcjaANM8WynSiyABSGyEBrNoFNr63luVSaGgc9kYas8LyD0WzUbW8vhb7vsUjhznoKD6UKeBSB+Ofz9wC9OwQNzO46TGR0KAvxPy9zXFPcVOHucoVPQctChWAnWeVV1qE1hIXiZmbH0T4wBapXmIT6l1c4GTIwicS3fQKWEY4nn3rLQ6dVHQram/Oo9ILFqNOgrps5V6iU+pRixGbDMSa+yszytosMsJy/gdnagdurG9VWkSTAIlAEa8y44GJCmCDj/oj8enFGng3GnecvtohU9epn0hsd4wmIR349elfiNVO4CouVGQ9G2+2fhIyMB6PWdrvCVnEmcyOnIMqtb0LU6f5MRJ3uz0D0vgA1+3uwrClZKKGHEC0BsJCajb+iu51cXMTSbldPsLGBNGWK9LkOCqUhw6E7SpmJpcqw9tSh2JIVjF237eIQ0UWWMTWrh/njMZ6N+6Mt1A+MGClTEhQ8xTdKEakmTNQpsuIyY1MgQZFOSc5mGMWuMjJRsshRvCkIec7tA3kNykqDZncB5kaqqbtRb/y7IH4Sn8RZglJa42smcxCt+rTJlcSTsFLSXNdQUAXJvJGv98I5hImoEu0yQuUuSADVkdXIp1imqbzBblGQS82NVBy0jzha5FJX8bz6dytaSlIrr5PUClg4BRFdPUuMybXveRNukiJwQ5l53xRhyyeW/ALKrGlnbcHWZpYVF7Fi2qgiNIWqCWJdzFM1db+BWazsvPsRak2Ip7jdQEAa2+9mk0CaodhXRj8KecnOMwrAyxgXXr3wKJ+naLyGNCM2kMUfQZ7KGbbXk0xIodHuTRGAEmBAu5/wlDKgMv0uHoO65iGeSw2tGqYr1cSzRi0Zt3Rt5tCUh4CS21/cC3s5CxMgHXtOVTMUY/med3Nz4zL71EarXbU3PD4YnIwHrY7bdhOTpfaczKU2GRNLgY/AkF59bbm7nK4cNfM75fSfuYrXc8fArfHylHGB48nmbV5Ll0u6SbpQh/r2Dt6olyuHJlIbtJ/PA6bhXKVlicvV9PEvrxx6zRRHnFbhRFzj94j6MUs1PJLMZ6f11XyLfM/FfiPHZuAKnLbXLC3wL+rQKcyqfy+UV6XTjGyEWz3ohSHkZsllTSGvaMCjwRleP9eG/NQO+foLRt8I576KqCDgz9J5wGU+ryREWS7sq0cPetQUF8yRQVmWfwGCunRM
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get Account Balance"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/distribution-wallets/{id}/balance"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Returns one distribution account's live on-chain balances. An account the caller has no access to is indistinguishable from one that does not exist; both return 404.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./get-distribution-wallet-balance.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-distribution-wallet-balance.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-distribution-wallet-balance.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-balance.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-balance.mdx
new file mode 100644
index 000000000..3000c5345
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-balance.mdx
@@ -0,0 +1,5 @@
+---
+title: Get Account Balance
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /distribution-wallets/{id}/balance"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-capabilities.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-capabilities.ParamsDetails.json
deleted file mode 100644
index 43dcda226..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-capabilities.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"The unique identifier of the distribution account","required":true,"schema":{"type":"string"}},{"name":"user_id","in":"query","description":"Report this user's capabilities instead of the caller's. Owner only.","required":false,"schema":{"type":"string"}},{"name":"role","in":"query","description":"Report the capabilities a user would have if granted this role. Owner only.","required":false,"schema":{"type":"string","enum":["financial_controller","developer","business","initiator","approver"]}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-capabilities.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-capabilities.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-capabilities.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-capabilities.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-capabilities.StatusCodes.json
deleted file mode 100644
index a2a28f21f..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-capabilities.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Capabilities retrieved successfully","content":{"application/json":{"schema":{"type":"object","description":"What the subject may actually do on one account, combining their tenant-wide role with the role they hold on that account. Both gates apply, so this is reported as a capability set rather than a single effective role.\n","properties":{"wallet_id":{"type":"string"},"user_id":{"type":"string","description":"Present when the capabilities of another user were requested"},"role":{"type":"string","description":"Present when the capabilities of a hypothetical role were requested"},"capabilities":{"type":"object","additionalProperties":{"type":"boolean"}}},"example":{"wallet_id":"8d1f6a2e-3c4b-4a5d-9e6f-7a8b9c0d1e2f","capabilities":{"can_create_disbursement":true,"can_start_disbursement":false,"can_pause_disbursement":false,"can_cancel_disbursement":false,"can_create_payment":true,"can_retry_payment":true,"can_cancel_payment":false}},"title":"WalletCapabilitiesResponse"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-capabilities.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-capabilities.api.mdx
deleted file mode 100644
index 35174da7d..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-capabilities.api.mdx
+++ /dev/null
@@ -1,75 +0,0 @@
----
-id: get-distribution-wallet-capabilities
-title: "Get Account Capabilities"
-description: "Reports what the caller may do on one distribution account, combining their tenant-wide role with the role they hold on that account."
-sidebar_label: "Get Account Capabilities"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWG1z2zYS/is7+JJkhnqx66atvjmNm8v1pvXF6eRD4nGWxEpETQIMsLSi0+i/3yxAKpSlxHlxZ25umg9JRAC7z77iwa4V4yKo2Wv11AT2Jm/ZOAuvsKqIg7rMlKZQeNPIZzVTL6hxngMsS2TgkqCQnR5qXIF24Cw4S6CHsrAoXGs5g8LVubHGLuSg8cBk0fJoaTSBdxXB0nAZhcZfXNIKSldpkcqir5M0fmPf2N+XlnyAAi1gFRxguE6gELg0XkODnldQuLbSoF0G+QoaDEHUv20D+Suj347hVGt4K+reAlbOLoKAMQycJJarxnFJbMTMVW81MoiErXAwc1h4tEw6rYrAcS+3QGsdQ04QyLIYYziAW1pAq8ETt94GOJlOo/2u5SG+l6UJkGNxHaJjNIYyd+j1gyDeoBBGUbFY1ZjimnwGy9IUJSxRpC5LsoAJHCwj3JzAWPICqMA2RD9Hcx6E/Yhg5Qn1Cuh9UbWaEggsJK7jN1ZlyjXkUX4+12qmnhEP0yhl0c/YYG4qw4aCylSDHmti8pJ1a2WxJjVTRqtMGcmwBrlUt9PupWC05l1LYDRZNnNDHtw8OeVAtqlMeXrXGk9azdi3lKlQlFSjmq0VrxrRKafsQm022RZG5/gey7uW/GoPTKoBSbPQO64Y2AjGBibUPbxUIQ/CGGLOgrPVaryDb45V+EyAEpXPREe7qDDlbEqCEm9oN2tN6LL2K0FmimxbSyOZG4u2MFhdFc6yd2J9RHlDlaSLylTeBmMphGiJYYPs5DM2jXc35NXlZnMpukPjbKAg2o6nU/ln19ZhakkleUM3pCG0sTTmbVWJfwQGWZbj2DSVKWLCTv4MImO9b5HL/6SC9xz7qm95oY0bYs/DgtvYGj40v/vvd/DEcQkLZAlj01SrDIJLMZOwxYCTBpQgb2O+gkAMHrkkL+KkD0j3qwhoPqeCzU1SnAq58RKbWKOztVrGypVK2M/GbFslB5Jg12XnnmLPi21oLyPdHNC6iC+lJnkCSTgKTFoUxWy/By07fbzz/Z6y4alD2YBaG9GI1fmOr7p9uXMVoVWbzSZT9B7rJmEfuFL9qI/mj/GYRt8VJ/noBL/Xo5/o8Xz0A/6Y/1RM9REdz9U+kgLtVeEJma60CXnrA9UxoVNjk+XA6PnWalexstxIp//4coG2oOoT60l5g6vbeqXoVocWOpHblShNXMOGxTFq/3J40dW7uHCTqZNDFf8ENbxIUfuWyt7NdvLe+bvz7CkxmioA5nJJS6KlgzHe7PFg1uxo2qQ/YtvRvm1/WGy5dN78h/Rfbtzng1aBkdvhPtvWOUW7awoBFwdqtLNzUAcdDvWbY9ix8wOMXtHJ9Ggg+vaJrQu/23fhL87nRmuyf73/PmLeBwQ9zJN9mGLRL661/+dhnncmHorwyTDCLyi41hcEdnuqr5RAResNryJZfELoyZ+2XKrZ60vhCDVx6aS1LihaJORxpiZDSjhKHThM1kZvJsUuGw3kb3oq2vpKzZQSsb3WC/F+cs9Q99YN2JhfaZ+DnXbZGkMJJaGOrwXLmPgAWrh4eg7/fPUSHp5dHH//+BE43329gtPz53BNkX51rG9HXk//klgJz8XZ+dH0npDBxdn56GiasCWbYc3umuzm0RchOj65T0THJ/eB6N/CmD8PVtwK28fKxxANAERIu9xcEtjYuYvqunvvgqmq0MPTwWUL5xXy3PlaYq8yJSmZYPwwno6nkqdtXaNfdU+hT8t4ePH0/JEwQwR2roK8NZWUlQfnF2g7FwV549Z4TZC31TV0F3X8Kg9G1zZCnTwVpjFxQZh5vPV67ZZ46fz1+OBr7X8LokwMXnZ8GS24huyoazmNd5HNR8Ytj+0IRSi4a/on3C1xWXy5R6bpNMUZRE6pbyXuLj+qyi0lW4SeB8POGwozwTGC1yHJm3T/jobEa9R0ThrJs5+svnxYMjdhNpksDJdtPi5cPfkiCY9maY6whbLq0zk96Ltt0Spj5x4D+7bg1ncGSlz4rpiOv8CyuY+X3reY1ou4y7Yl5dDv/WprSqrqUVGi5/BJyIN9E/ZEkxqNnXQfPmnPXWb8g6oaoqCIX1NTuVX3tLyj1to48/q1zclbYgrpvcfk6/D7/IL8jSmkL/VmdTDHzi8mcdPIzUeh25apyhQkHH22HUmcNliUBMexT6U7VGTNJpPlcjnGuBqldUfD5F/Pfz777eJsdDyejkuuq9gnGxe4RjsQ/IwYTtMTGG4NkXb6zfoDh/p7Pvn3fHJnPtld8kzvedJUaGycX0iSrjuy+FodIosqU7M4B9zhi5eZKl1gObRe5xjoD19tNvI53ffCIrUJmFeDidkdufrNc8SDJl7TameceYNVS5HdZl8F8V6GiZ9A2s01P8C8lB/eCM4vdOvDF93M8hF8zdj4IMieK9rVEGQP3mi1udxkPdsUuGnhtCio4cGRvRfezhvm2dlLmTPt8dPryE+7/4j0g3BuE+AEQf6WmB88sl4n9rvZbPenpY+e6EzcWi4WbDab/wIafFCD
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get Account Capabilities"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/distribution-wallets/{id}/capabilities"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Reports what the caller may do on one distribution account, combining their tenant-wide role with the role they hold on that account.
-
-Owners can also ask what a third party could do, by passing `user_id`. Add `role` alongside it to ask hypothetically what that user could do if granted that role. `role` cannot be sent on its own and returns 400 without `user_id`. This backs the dashboard's access-granting picker, which warns when a grant would be inert because the user's tenant-wide role already excludes the action.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./get-distribution-wallet-capabilities.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-distribution-wallet-capabilities.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-distribution-wallet-capabilities.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-capabilities.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-capabilities.mdx
new file mode 100644
index 000000000..2e660635c
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-capabilities.mdx
@@ -0,0 +1,5 @@
+---
+title: Get Account Capabilities
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /distribution-wallets/{id}/capabilities"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet.ParamsDetails.json
deleted file mode 100644
index 9bf3d3e70..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"The unique identifier of the distribution account","required":true,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet.StatusCodes.json
deleted file mode 100644
index 9a8fab0b7..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Distribution account retrieved successfully","content":{"application/json":{"schema":{"type":"object","description":"A distribution account the tenant sends funds from.","properties":{"id":{"type":"string","description":"Unique identifier for the account"},"name":{"type":"string","description":"Human-readable name for the account"},"description":{"type":"string","description":"Optional description"},"distribution_account_address":{"type":"string","description":"The account's Stellar address. Absent until the account has been provisioned on the network."},"distribution_account_type":{"type":"string","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"],"description":"How the account's secret is stored. Additional accounts are always `DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT`."},"distribution_account_status":{"type":"string","enum":["ACTIVE","PENDING_USER_ACTIVATION"],"description":"Status of the underlying Stellar account"},"status":{"type":"string","enum":["ACTIVE","PENDING","ARCHIVED"],"description":"Lifecycle status. `PENDING` accounts have been reserved but not yet funded on the network and cannot send. `ARCHIVED` accounts accept no new disbursements and are never deleted.\n"},"is_default":{"type":"boolean","description":"Whether this is the tenant's default account. Exactly one account is the default, and it cannot be archived."},"created_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"archived_at":{"type":"string","format":"date-time","description":"When the account was archived, if it has been"}},"title":"DistributionWallet"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet.api.mdx
deleted file mode 100644
index ca22af50e..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: get-distribution-wallet
-title: "Get Distribution Account"
-description: "Retrieves a single distribution account. Owner only."
-sidebar_label: "Get Distribution Account"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWFtv2zYU/isHfGkDyLKbZRvgNzfxWm9BksVO+5AGDiUeW1woUuXFrmfovw+kJFuJnaRpO2DYSy7iuXzfIXXOJ66JpXND+tfkhBureeIsVxI+UiHQGnITEYYm1bzwj0mfXKLVHBdogILhci4QWNuRpqly0sZwvpSoQUmxiklEVIGaeoMRI33yDm07W5WMRKSgmuZoUXtAayJpjqRPOCMR4T55QW1GHiKaZAhO8s8OgTOUls+4TzwDm+3HRiKi8bPjGhnpW+0wIibNMKekvyZ2Vfic3kvOSVneeGNTKGnQ+PXDXs//ug/hZE8W0HWlGBiXpmjMzAmxIhFJlbQorQ9Di0LwNBSm+5fxsda7WFTyF6Z2h/dgL7nA2qKk0oJByQzMXPipVe43otB+Kyyv2HC2y/lhnqud2s6UDmmaepZRvVXPhXrvcio7GimjiUDwTvuC3XN6LuZ5+IMKaD/2QVrFmdbBp5QxjcY8H3WyRfTKwNiiEFRD7R7DIDEoLThpuWijh4waSBAlFFotuOFKIgMlg41Eu1T6Ln4UXQVpFxpKl4c3dDSeXI7eXk1G52fTwfHx+dXZJB5Phqeng8t4ePaBRE+bnLydfhhcnU4eszseXR6fDrdmOy//e7Vss31lwGCq0QI3YKzSyGIYMMbrHanNDFCNQMWSrgzcfhXC28eLZCy1bu8ONmUaHE9GH4YkIhfDs5PR2bvp1Xh4OQ1PBz7rLq9xiNn0DCcZarHicr7d+O3hfHl+EpHB5fH70YfhyW7qUz7DdJUKhCpwDLe12+22fhldYHWsNBrUvqckzoJUFlZowxu+c8yASgYpld7IN4IYbhsUrcg0TbHwkUDi0jeUxGmDOYY1ycLOSVygBoYCLbL4U3i7uJkynFEnbKsSiVICqdx5mT5maDP0rzk3/qhsW9QrA3WY7eAYfqGpFStQcvta1U61bRSgcdvQSxCoTjO+QBbOTaqRWmRTavdt00zp3K8QRi12LM/R+7iCvdinSfr1TnsqI+/1jyU1Gy4R8Jln2fQUUpYRsdwKfDBy6vlZlt7gqPdmd0BdSepspjT/G9n3TKD70wO1VnrP0IwIfrGamucj7LxM0uUJah8iR2PofE8/LCue+IXmhcAWDnKmLNzjuYXRJDrqvWmFfuhRNiX8abeEvymdcMZQ/vv1e4TeFkED82gXpmf0m3Lyf77Ns5rivh0+au/wJRrldIqhWVZeZR3aYOo0t6ugNd8i1agHzmakf33jZV+ONlNerc5rbeqXSLc9lDrLSiZ315yVxEfUi0a8Oi1InxAfqUk09gWvKtJOt2FOC/4HrnaFXn1Aw+5BhpShBr+3lEs/pKiE8ckF/P5xAq+H48OffzkApeunUxhcjOAOgwiv9fS9eI20rsL6HRkPL970fhAyGA8vOm96FbaKM6ytukNZHrwI0eHRj0R0ePQjEP3pUK++DlYwhc3nzWOIWgACpCbxZ+8e2j+XMxXS1WOgESgnrckNF4JaP3z83pOI+CNZwfg17sU9f05dnlO9qnXu0zFej08uDvwApmCVEpA4LmxQ7UrPqaxLZMAqyOkdQuLEHRR0VWkIq4DCXCtXeHWlMeUFDwtqgZXub7Jv1PE+Kf7fgvhJfpKTWstQCapA2am7TKGV74BgMxpUSwXFKzNVNPryQbhKzfiFVDH0msYLmtCqGkk3U0KopT8tGgtluFWao+l7HB24NlW8bv2701ZxnaIuUieh6R1KdvM6s7Yw/W53zm3mkjhVefdFEQ76EMhvoKya41yJtNqs0mhypqmx2qXW6Zpg88H35J7GL2A202HOfQ+1JsRz3JaYQGP7zWwyFHknzai25knILbuu1YjdnHLZrR88yec5Gu9R5BACBfwMC6HC986zTMD5Sx/4wyWoJVo0/nsgIhZ1bs5nY9QLnvq+1NCqYcZKz7vBqKNmHVObRUTwFKUJ071pvAVNM4TD0KeqGepj9bvd5XIZ07AaotWupns6Oh6ejYedw7gXZzYXoU8Wyticylbgd2jh3j3NYHMb9OC+YSObvvWyq54FFr/YbiEoD19Mgcu6lhHXZJ+MIBHpc+a/ETNlrLdarxNq8EqLsvSPqznQv76JyIJq7i9RgtZg3Pi/GenPqDD4BKPXl/XN1wF8y73ZXmbN6JN+7i2ocP4/EpE7XFW3d+VNGTXD08OtFgbh07PlsqNR76mwd0N/b0F3xu1dGLf1Hz76XjgP53kFwf8so0dc1utqmJflxr5aetSjprhh7hmUZfkPHpx9Ow==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get Distribution Account"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/distribution-wallets/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Retrieves a single distribution account. Owner only.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./get-distribution-wallet.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-distribution-wallet.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-distribution-wallet.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet.mdx
new file mode 100644
index 000000000..9017cb238
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet.mdx
@@ -0,0 +1,5 @@
+---
+title: Get Distribution Account
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /distribution-wallets/{id}"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallets-total-balance.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallets-total-balance.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallets-total-balance.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallets-total-balance.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallets-total-balance.StatusCodes.json
deleted file mode 100644
index 7e898decc..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallets-total-balance.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Total balance retrieved successfully","content":{"application/json":{"schema":{"type":"object","description":"Live on-chain balances, keyed by asset. Non-native assets are keyed `CODE:ISSUER`; the native asset is keyed `XLM`.","properties":{"wallet_id":{"type":"string","description":"The account these balances belong to. Absent on the aggregate total across accounts."},"balances":{"type":"object","additionalProperties":{"type":"string"},"description":"Asset key to amount"}},"title":"WalletBalanceResponse"},"example":{"balances":{"USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5":"37500.0000000","XLM":"314.9997600"}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallets-total-balance.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallets-total-balance.api.mdx
deleted file mode 100644
index c462fa1e4..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallets-total-balance.api.mdx
+++ /dev/null
@@ -1,62 +0,0 @@
----
-id: get-distribution-wallets-total-balance
-title: "Get Total Balance"
-description: "Returns the combined live balances of every distribution account the caller has access to, summed per asset. This is the Total Balance shown on the dashboard."
-sidebar_label: "Get Total Balance"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNV21z0zgQ/is7+kRnHCd9gQ6+T2mTQo9QQtNS7koHZHsTi9iST5ITchn/95uV7eD0hR4HN0M+JBlp9eyzj9a76zWzfGZYcM0GwlgtwsIKJeGKpylaw248FqOJtMhpmQXsHG2hpQGbIEQqC4XEGFKxQAh5ymWEBtQUcIF6BXEbkUeRKqStDhK6hoQbWkZjwCoPTJFlGEOOGrgxaH24SIQBUTm7UJancFQ5AZOopQQl3VbMTRIqrmOfeUzlqDl5PI1ZwF6gbcdVh+WwaijmMY0mV9KgYcGa7fV69LMddeW8jhA0Wi1wgTGYwtGfFmm6Yh6LlLQoLZ3neZ6KyBHpfjYEsmYmSjDj9M+ucmQBU+FnjCy7rfGI5FSyEyVcyI2uHsxxhTGEq0aeMyU7kluydisGuMba6tPxm8EwOJ1MLofnn35zMrVNSdXa8P3o9ScSLtcknRWVDEun1EcRt+iSjnJ2h+5Fgu3bNa1UCDFVcgZW+dAPDUrbXBmfzTTOuEWwTloeaWVMA2N8VnqsQblPMB7HgtzzdLxFe5tpeZtq38U+xxVYBTwjX6wsPWaFTelclR91ZpzXaUEw+IVnOZmst2hdTgbHwYujo8HB4enJs9HVq8Px4evB8N3k+Or8cDC+vHq3f/bH/uDi7fDdyejgrH9x0H/7cv/P0ehk1H/KArZ/+LTX83vVh3ns/eg1re4e+M+fPz981uuxkj4eO+jt3s3KS8kLmygt/sb4R7Jv++ZRa6Xv1RK/WM3vvY5tBGO5Ldp2sshC1ASRoTF8hvfAV3G2dK55sDNlYSvOrzQaRwe93Rb07RMbCffvSniidCjiGOX/r98D4X1lUPM0GBVa2BULrtfsCLlG3S9swoLrm/KGwrSJotI2Q+eb0xbrtmttp3p4TTfclDiDeoHaOMxCpyxgjMAaXxOKraLf9riJgefiFa7uPPn9WmQnFCTIY9RAMnIhhZwBlzAZjOH3qwt4MpzsPX22A0rXqx+hPz6lR5Fqj+QZ3sZjHhPkpIKl5JkMx7u9n8QMJsNxZ7dXcatihrVVc5Tlzncx2jv4mYz2Dn4Go7cF6tW/o+VMIeeaZ2gfZtQi4Cg1jv+i466ECjlVzl1dSicW05RrGAgTFtpgRtV/nHI7VTqju2ceo5SsaBz6PZ8KIM0AXK/qrvJtjCeTwXiHGhkHq1QKYSFSC1OlQekZl7VENFtAxucIYZHOIecrQnGrHGZaFTkNLBojkQu3oRaoXY9qvEu0S6Xn/r2N79ei+EF+kM3QxCWoHGXHqEJHCLlWVK7AJtx1/4oKtWPl4O+B84DLuJ70YpraJIQIU1XIuOnjU5WmaknZojFXRlilBZqAeHTg2lR43fq3E7dE6uS1SJ2QR3OU8c2TxNrcBN3uTNikCP1IZd3vQtgJqolxQ2XVpHM1QtZmLiohp5obq4vIFroOkO7FPnan/ndENtWupfxIaA3EY7EtMYTG9j9Hk2Ca0dSprfkm5ZZd12rEbsaF7NYL34znsTBeYpqBA3L8Y8xTtaL0ejQSKAzZvSpC1BItGv8DVSmLOjNvphPUCxFRXWrCqmn6Ss+6zqijph1Tm3ksFRHS7BesN4U351GCsOfqVNVDCSvodpfLpc/drkOrj5ru6PR4eDYZdvb8np/YLHV1MlfGZly2gF+g3X67uV1o1l9Hk1///atuNxa/2G6eciGpKzm51vWwcs3uG1bYZuCnl85EGUuW63XIDV7qtCxpuWo3wfWNxxZcCx5Sq7m+Kb2mA9J8M0fqH/0owpwmpAVPi6oB3prptqapF8MLeq240zPnrmfWfwi92ZKrFvbtplxRoO/Se+DIel115LLc2FdbD56oQ2ysSdmbsiz/AZdlheY=
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get Total Balance"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/distribution-wallets/balance"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Returns the combined live balances of every distribution account the caller has access to, summed per asset. This is the Total Balance shown on the dashboard.
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-distribution-wallets-total-balance.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-distribution-wallets-total-balance.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallets-total-balance.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallets-total-balance.mdx
new file mode 100644
index 000000000..a86851a38
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallets-total-balance.mdx
@@ -0,0 +1,5 @@
+---
+title: Get Total Balance
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /distribution-wallets/balance"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-circle-balances.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-circle-balances.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-circle-balances.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-circle-balances.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-circle-balances.StatusCodes.json
deleted file mode 100644
index eac951347..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-circle-balances.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Returns the organization's Circle balances","content":{"application/json":{"schema":{"required":["account","balances"],"type":"object","properties":{"account":{"required":["status","type"],"type":"object","properties":{"address":{"type":"string","description":"The address of the distribution account, present when the account type is `STELLAR`.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"circle_wallet_id":{"type":"string","description":"The ID of the Circle wallet, present when the account type is `CIRCLE`.","example":"1000646072"},"type":{"type":"string","description":"The type of the distribution account.","example":"DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"status":{"type":"string","example":"ACTIVE","enum":["ACTIVE","PENDING_USER_ACTIVATION"]}},"title":"DistributionAccount"},"balances":{"type":"array","description":"The organization's Circle balances","items":{"type":"object","properties":{"asset_code":{"type":"string","description":"The asset code of the balance in the Stellar network.","example":"USDC"},"asset_issuer":{"type":"string","description":"The asset issuer of the balance in the Stellar network.","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"amount":{"type":"string","description":"The amount of the balance.","example":"100.00"}},"description":"The balances of the organization's distribution account. Currently, this is only used for the Circle distribution accounts.","title":"Balance"}}}}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-circle-balances.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-circle-balances.api.mdx
deleted file mode 100644
index 6853ac552..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-circle-balances.api.mdx
+++ /dev/null
@@ -1,62 +0,0 @@
----
-id: get-organization-circle-balances
-title: "Get Organization (Circle) Balances"
-description: "ATTENTION, this endpoint is only enabled when the tenant distribution account type is `CIRCLE`."
-sidebar_label: "Get Organization (Circle) Balances"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNWF1z2joQ/Ssavdxkhq8ATWZ448NJSQghGEhvU4YKe8FqbMmV5FDK8N/vSLaDAyQhve2dm4eEyLtH5+yudoVXWJG5xLV73CA+YQ5IPM5hF6QjaKgoZ7iG64OB1R20b7o5pDwqETA35JQpRCXizF8iYGTqg4sWHjCkPEAKGGEKuVQqQaeRxkHEcXjEFFLLELTn12a73+xYXws4h3kIgmirtotr+ALUjZgTRn+ataMmFY4Px08Ec1iADDmTIHFthculkv7znHMfVCSYNGx4BuwviWI4NN3AOZwpYEqjkDD0qWNMi9+khlph6XgQEP1JwPeICnB1vBI9OIenmchpdbiG+fQbOPpZKLQ2RWOqqc8WlFRERZqI8X4bxXUFSPMxMdRhZnO8nbiBBygxRnxmYrEvJTkUCpDA1CaBO8myB1anU++bbMEPEoS+3vei+al+Wfl0WRldVS7PP1Zur1vnN/bVdbl7ff25Yd9URu3BqTXs3d7Zrbvy5Vn1ulzp9+0OXuewY9IwWRDfBzWh7mFy2q1USZLG2P8QCZl62yg4KZVKp9XT0llZc4r3P4SHQX0lps93abXtQb/dGOpDNKk3mzfD7qCQhLTQakxG9WFnoD1YFOiCeNXe6o5w7mDIvXZxKDZm43UuLcI96jc66s1Be2RliD4t9Kxuq929mAxtqz8xq3W9Ix6vdVipisOQCVQ9OQrrzPnZ7E2EIMu9gX/zMFMFQRbqpUMkJaiJw90DE27skbZP057siWhcb7YC3ycCMVALLh6eF8DQbjW11HhXKmUE4j37xh6/svNFo9GqnrXPTzt3V2e9s+uWNbKbd/2zVm94N6p0/660BrfW6LxT7dYH1frtx8rnTue8U/9g2AZptzqAp7HdYrhz1gqlEtYVseufZjBF2Mrz3jOGmpEQwJS/TCZTOpAiCS6acZFtFPsQpCaYVmcyX/A6/snh6r7B0iAu6sP3CKR6z+R4vRhBCH5APbRAEepLRKY8UkZb7LjWUVaCvF32GW0nu9qGjETK44L+BPePizuc9G5rYlEwBaM7ACnJfM8ZjmU+Fd8TDdzlCj2TuWGR7lMtnWSQtz3+JLDBluBEgqolrt2vcAOIAFGPlIdr9+P1WPsrj+t70hxMqIh+hIuZFihBPIKQxj8SPq5hrB1TXFsnLo5sFn3TfEN6Bbvdt54wNVWAPCAuCKRrhFBG2RwRhuxWD13eDdCRZZc/nB4jLpLVCar32ugBlvrAMRLANp5u3HqTGFZn1rZ6J6XfxAzZVi9/Uoq5xZrRSvEHYOvjdzEqV38no3L1dzC6jUAsD6NlTFFIBAlAvcwoQ8BQSjf+rt1N/6Zsxs12Se9MR1CLymkkJAT6KtbziZpxEejc4xzWJRnTOCuUCiVdp1EQELFMJsDrGEd2q3esGzxBinMfTSPqK9Pjs5NCIsVRQB4ATSP/AYVkqVHMKkFzwaNQzxcBDg2pecAfQbw0RHeH1P+L4hf2hQ2SsUcY4iGwvOSRcACFgutOipRHzNe0mApnSPEwnbBbcDlEmGsemEuOQxiaAprxiLnG0dP/+D5f6GoREHJJFRcUZE3zyKN7GeMVk795NxOkfJgEKT8lzgMwd3zkKRXKWrE4p8qLpgWHB8V3IRzXkBH/RGWZlrNMriDGzKiibCaIVCJyVCQSgen14NWcFt6hbCbMvPw30lKIt7QtYIpS219W44Ef5B2PCCVfpZyxKyoBUAwIZcVk4VU9b8n4CH6ADJDh70Lo86UurzeVoEhqu6toCoKBAln4oruUAhHIm5kN4pE6ui+lshKaBS7mRWOU57O8TMxy2KcOMGmmedp4Q+J4gMqmT8UzVGPVisXFYlEg5qlBS1xlsdNuWl3bypcLpYKnAt/0yZBLFRCWAb4AhbJvN1D6egNl3m886zyrzUXsP3gVkwwQBT9UMfQJZXrOmACskqvG/bMXHh6XSq+tVlMiYSj89Vovx6Oidj/O4UciqCZl7i+5dHrpu8kD6N5fdxwI9U3mkfhRPLy2LpvPbj0Xlv5aS3bm3YOZd8kHjZ4+YssM9vZAjSno3+vcCy6rVTxN1+sn+/jRix6JxNRax3C8Xq//AUqytrU=
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get Organization (Circle) Balances"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/balances"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-ATTENTION, this endpoint is only enabled when the tenant distribution account type is `CIRCLE`.
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-organization-circle-balances.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-organization-circle-balances.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-circle-balances.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-circle-balances.mdx
new file mode 100644
index 000000000..e7f67d9c5
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-circle-balances.mdx
@@ -0,0 +1,5 @@
+---
+title: Get Organization (Circle) Balances
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /balances"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-info.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-info.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-info.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-info.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-info.StatusCodes.json
deleted file mode 100644
index e2aa62c87..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-info.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Returns organization details","content":{"application/json":{"schema":{"required":["distribution_account","is_approval_required","logo_url","name","payment_cancellation_period_days","privacy_policy_link","receiver_invitation_resend_interval_days","timezone_utc_offset"],"type":"object","properties":{"name":{"type":"string","example":"Stellar Aid"},"logo_url":{"type":"string","example":"https://stellar-disbursement-platform-backend-dev.stellar.org/organization/logo"},"distribution_account":{"required":["status","type"],"type":"object","properties":{"address":{"type":"string","description":"The address of the distribution account, present when the account type is `STELLAR`.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"circle_wallet_id":{"type":"string","description":"The ID of the Circle wallet, present when the account type is `CIRCLE`.","example":"1000646072"},"type":{"type":"string","description":"The type of the distribution account.","example":"DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"status":{"type":"string","example":"ACTIVE","enum":["ACTIVE","PENDING_USER_ACTIVATION"]}},"title":"DistributionAccount"},"distribution_account_public_key":{"type":"string","description":"DEPRECATED! Please refer to distribution_account.address instead.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"timezone_utc_offset":{"type":"string","example":"+00:00"},"is_approval_required":{"type":"boolean","description":"Enables multi-user approval workflow for disbursements","example":true},"receiver_invitation_resend_interval_days":{"type":"integer","description":"The amount of days that the SDP will wait to resend the invitation to the receivers that have not registered. If `0`, that means the resending invitation feature is disabled.","example":5},"payment_cancellation_period_days":{"type":"integer","description":"The amount of days that the SDP will wait to cancel a payment that is waiting for the receiver to register. If `0`, that means the payment cancellation feature is disabled.","example":5},"webhook_url":{"type":["string","null"],"format":"uri","description":"HTTPS destination the SDP delivers outbox events to. Must use https.","example":"https://example.org/sdp-events"},"privacy_policy_link":{"type":"string","description":"The link to the organization privacy policy","example":"https://stellar.org/privacy-policy"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: {{.OrganizationName}} which is the Organization Name configured and {{.RegistrationLink}} which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"otp_message_template":{"type":"string","description":"The custom OTP message template set to send OTP code to the receiver complete the registration flow. The `default` message isn't returned. In the message's content it's possible to add the following template variables: {{.OrganizationName}} which is the Organization Name configured and {{.OTP}} which is the OTP code to send to the receiver complete the registration flow (in case this is not present in the message, it's automatically appended at the end).","example":"{{.OTP}} is your {{.OrganizationName}} phone verification code."}},"title":"Organization"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-info.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-info.api.mdx
deleted file mode 100644
index 26d5dda57..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-info.api.mdx
+++ /dev/null
@@ -1,62 +0,0 @@
----
-id: get-organization-info
-title: "Get Organization Info"
-description: "This endpoint returns the organization's info. It is used in many places across the UI. It returns the name in the navbar and the public key of the organization’s distribution account."
-sidebar_label: "Get Organization Info"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVWetyGjkWfhWN/iSphYbYnqSKf8QwDo4vxOBkdh1XW3QfQINa6pHUEEJRta+xr7dPsnWkbmgwxmQmu7XzxwbpXL5zdG4SC2rZyNDGHb3WIyb5N2a5kvS+QmMwkeap+9qg/TE3BGScKi4t0WAzLQ2xYyCqxPfCEC6HKiAdS7ghmYGYcEkSJuckFSwCQ1iklfGctx1HWBYmWQLI4T9PB0wTJmP3Nc0GgkdkAnOiho80//uf/zIk5sZqPshwgbAoUpm0Aa1QlYJ2VJ2YNugZ2LKtHTlUtEI1mFRJA4Y2FvSoXsd/my64yXGW1ZIYLOPC0AqNlLQgLfKxNBU8cgS13wwyL6iJxpAw/KTh94xriNHpZcRhjphWKDchS1OtpkyEK/IKFWqkwkwLWqHoKFqhKZsnIG0YMRmBEE5lmILmKg5jNkdcqeZTFs3DVAkezUPB5cSZGwGfgg65nHLr+TQYkHHIpQWNmnMBlifwTUkIMxuFajg0YDE+7DwF2qBq8BtE1ulBN1vuPejwNRYFFVopR7RC4StLUoFLPYuANWnymC5Ltu1lGlubmkatZjxzNeZmkGkD6IRqKpgdKp1UByyagIyrMUyDnDJQelQrn1wNFaLinUewdUzGMps5XyCyZ41ncazBmF2mbGcVkJy4COpdMVwhqTsbS2Zj8MmR7xCUj6n20Ou3Ly6aNw/Bhr/OTn9tnh//en786cPx+S/vjz9etn657n24PLq6vPzHu9718adO/037tvvxc6/1+ej87cnl0fHNTe8CHRNxHQkIZ0wIsCGPDzOn0yosOXX8xPMfYsJp5+b0or1lwet6vf7m5E397RFi8voPweGk7vHpppZWp9e/6by77Xeur8Lm6en17VU/yF0atN6Fn5q3F33kkFmCAbGXvn31iVYOFrmTzrtiTXa/rBRBuDc/mqf9zqd2Cehqodu+anWuzsLbXvsmdKtN1Ejvl+hWbr0bSo5q5qnwRIqEvh6HE5g/fyCtdvemfdrst1s/ka4AZoBoGIImVpFdwoMiKbg0Flj844J6VzHb69G/1euNeh1ZdxblNe9AKQFMPrK9LdlAgCFJJiyvZgY0KcSQmdKToVAzMlSalGuZKWOwOoPld5TsNSZcH4HeXXcSl31qSJCJ2DGzLll6rS6ZcSHIjHGLB+R1uL21ZtzAlQJULmDMpkCkwqY+4saChjggnSF5qD9UPEUCLO/1Xi6Xo7LYITCbaVcPYm7Qc5uH//PygKb3gx3g9RBGcsWelBtHgPjx9MrO8F7zDnjS/EJY2YqDzJ/BYKzUZLNZ3q1jV2ZCYI/CVsgsbdBM80cOeN/vd3skBmO5zA80Nz0G4Q9UZXagvhKYYjwSqwJymRmLQx1xbTjY2ZnzFddvTZxWPTvmz65B5KBSjpRFvG0MX7lE4iXuGxQcnJy8mpOXU8qflh8SwwSMYSMILSQ4UhzYcKLMWJWQgskPv1YRlzzrCDc+OPKsCQiyPsQwZJmwDyRXTbiRL4rJ2KWQP598+4Uh+bRJuH1hSKqM4QMBKJrFPlWHSgg1w+hcIZoyzV0tapDFIijPwFcsgeWSzMY8GmPsoYDyPkEC1Dnko0xD7IbyxSK4KbntgsvJtgx3ciOQOH5DTAZzF2GFU7ZKCHnJJYmwN1i8bHDjCkkxNvAND1S84SyzKmGWR0yIOZZVkDGi84kMMn61GaR/V5kvUetcLufwXGVkqFWy2z0BORU8mjxhdznlMbSUTf9cIF33u6twWB2hAbtyHxJEKoZHfowUmmshX11DJdhr/uIhd93vPmIrOWJnYO13yP8g7la4ucEg0084Ix0rCWQKmg/z66OzK6DlGW3jnr5c4tZJ/fXj6+qtZJkdK82/ubvjwdfT/Vcb0Frpx3G8RGutZuZ5CY/GWJklA9AoInfyDvHOzJU/VzDolbJkw8w1ikLPSf11SfI2x39TsJNtIMo0t3PauFvQd8A06GZmx7Rxd7+8R347VvgqMQLnKoZbdOOmSlGIxm7hZLi2TykyF7J7eHjeu2UNKy+ylH+A+aNi08zR+kgbA4tdrkjLuMQsZtKV6/PPffKy3Tv6+c0ronS+GpJmt4OPMUHxGLElD18xUIkXi6fba3df138QMtJrd6uv6x6bt5ksrJqAXL76LkRHJz8S0dHJj0D0MQM9PwyWIyUp0ywB+zSiEgAHqVD8O7K76oLPdk5dXmWK15lW6VJCuvkDC549rVAMSQ/jbVAP6hinWZIwPc8b2X4ZL3ut7issiIxYpQQZZFxY14bLwe/GpYRNgAwyMSm6tltlZKRVluIAryHiKXcbys3fJe0SLF6zgp299v8L4hf5RfbzHsQkUSnIqlGZjoCkWmE1XV09PBR3D0uLZ44tcZXV06lrjhGTZIBNOpMxyef9dcfWkCrDrdIcTANxVMldPjsf9th2/7IYuUfcjrNBEKmk9l0SXjWIM34FZV6Es2/zOZmzisuhZsbqLHLXJWdgcQvbe6bBd1g21K5n/hnTChHP2TaDASlo/7A1YxBJNRozbc1eyCW6mtUAtYRxWcsX9trznBnvQSTECfIvGpAKNXcD4bO5lhmk+5ANQEuwYIIvWKUs6MRcD3ugpzx66l7niKpqWDU5WYUKHoE0sH6Jps2URWMgR65O+R6Kshq12mw2C5jbddJyVlO76Jy2r3rt6lFQD8Y2Ea5OpsrYhMmS4DOwm4Nr/oPCRrFZrOevv/ZPKXk7svDV1lLBuMSulb9E+OHljqqtX5LGylhcXywGzMCtFsslLvvm07i7r9DimuCmokrRD3Hacc+LtBlFkOJ8NGUi8+1wa4TdmKXO2viwyh510InroPkHlF5syXlJ9naL9hDw77LyBMti4fvzcrmi91tPcuQmFtTox/vlcvkfGdq9+Q==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get Organization Info"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/organization"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint returns the organization's info. It is used in many places across the UI. It returns the name in the navbar and the public key of the organization’s distribution account.
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-organization-info.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-organization-info.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-info.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-info.mdx
new file mode 100644
index 000000000..001249977
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-info.mdx
@@ -0,0 +1,5 @@
+---
+title: Get Organization Info
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /organization"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-logo.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-logo.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-logo.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-logo.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-logo.StatusCodes.json
deleted file mode 100644
index cfa14924a..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-logo.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"OK","content":{"application/octet-stream":{"schema":{"type":"string","format":"binary"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-logo.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-logo.api.mdx
deleted file mode 100644
index d0629b9c9..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-logo.api.mdx
+++ /dev/null
@@ -1,62 +0,0 @@
----
-id: get-organization-logo
-title: "Retrieve Organization Logo"
-description: "Retrieves the logo of the organization for display in the UI navbar."
-sidebar_label: "Retrieve Organization Logo"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNVlFv4zYM/isEn1rAsXPBbQP81luDW9fDmi097KENBtlhYi22pEl0clmQ/z5Qtnu5DteuWx/mF9si9en7aJrkAVmtA+Z3eOPXyug/FWtrcJHgkkLptYuvOf5C7DVtKQBXBLVdW7Cr+GxP9sHKeljq4Gq1B22i/eMVGLUtlE8xQevIR8+rJeb4nvj01A92bTFBT8FZEyhgfsDJeCy3L8ncXGOCpTVMhsWqnKt1GTEyWzLxKLAn1YgtlBU1Sp547whzDOy1WWOCK+sbxZhjoY3yezzKlWBDXFlhtybGBJ3iCnPMTmVmdcc0kN+Sl+gdsPU15ojHhSyXrde8n8vRnYx3pDz5i1awHpgop69pj49DLV7WDxGtSC3Jg6hV2mizBmVgfjmDH3+9hbPpfPLNt+dgfb/6G1zMrmBDewm2UQ09xsMEtRzSweIxwfl09mb8SsxgPp2N3ow7bp1mOLDdkDmev4jR5O1rMpq8fQ1GP7fk9/+MVnQFp7xqiL/O6IRApDQc/IdsR0lGbVY2Hqe5Frc5U10rD5c6FK0P1JBhmNWKJZnl22OCkpIdje/ScTqWPG2bRjI8x9uK4GmMs/nl7Bx0AAVsbQ1Fq2uO//XpHxCALTRqQ1C09Qac2gtKXFWw9rZ1Uh48ldrpaLBb8rEcDKcb4p31m/Rvsfv/Ubw39+a20iEeacA6MqNgW18SOG9/p5KBK8Vi7qhYA2zdUCAfwSWgzDIaSrskKJWBgmBlW7OMGyt5qWu7k2zx5GzQbL2mkAuPEdyFDi/r76PlSZBGrg/SqFDlhsxycVYxu5Bn2Vpz1RZpaZvsRQjnOUTxD1T2Qzp3vaB3i6q0WXkV2Lclt74XKN+Fn/um6QuUrXys/P9F2gDxnLYdFTD4/ms1FdXNqKyU5/Ak5RO/jD1R1ihtsn7hST3PyfiB6gYiUNegydV2L+n1rBJog/hdtwV5Q0whvZcqxeSbcLOak9/qUurSIKunmVq/zqLTyK5GoXdLsNYlmUBS0YbC61RZEUxinep6qGDlWbbb7VIVrRGt3xqyD1ffT3+aT0eTdJxW3NSxTjobuFHmBHgYWOB0woB+xPii4hw+jxKvNeb03YHpE2euVtpIE4nqDv1AcYengBIaYbZIsLKBxXw4FCrQR18fj7LctYT8bpHgVnmtCmkHd4tjMnQpmUE2JDX+oizJyeiyVXXbNamvjEcyrDyMO++nt3g8/gWhdo+S
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Organization Logo"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/organization/logo"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Retrieves the logo of the organization for display in the UI navbar.
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-organization-logo.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-organization-logo.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-logo.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-logo.mdx
new file mode 100644
index 000000000..52f691d8b
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-logo.mdx
@@ -0,0 +1,5 @@
+---
+title: Retrieve Organization Logo
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /organization/logo"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-profile.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-profile.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-profile.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-profile.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-profile.StatusCodes.json
deleted file mode 100644
index b571a354e..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-profile.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Returns user profile","content":{"application/json":{"schema":{"type":"object","properties":{"first_name":{"type":"string","example":"Jane"},"last_name":{"type":"string","example":"Doe"},"email":{"type":"string","example":"jdoe@mail.org"},"roles":{"type":"array","items":{"type":"string"}},"organization_name":{"type":"string"}},"example":{"first_name":"Jane","last_name":"Doe","email":"jdoe@mail.org","roles":["developer"],"organization_name":"Stellar Aid"},"title":"Profile"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-profile.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-profile.api.mdx
deleted file mode 100644
index 21e7db2ad..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-profile.api.mdx
+++ /dev/null
@@ -1,62 +0,0 @@
----
-id: get-profile
-title: "Get Profile"
-description: "Fetches the individual information of the logged in user to populate the Profile page."
-sidebar_label: "Get Profile"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNVt9v4zYM/lcEPV0BJ84Ftw3w07o163o3bLmlwx7S4KDYTKxGljSKTi8L/L8PlO02adf2unXA8pA44q/vo2iSe0lqHWQ2l1N0K21ALhJZQMhRe9LOykz+AJSXEASVILQt9FYXtTJC25XDSrGScKsoNW69hkJoK+oAKMgJ73xtFEEUdxGEV2sYykQ6DxjtLwqZyXOgHkIiEYJ3NkCQ2V6ORyP+OUb1K1CNNrSR/K1h7iyBJdZX3hudxwDpdWCjvQx5CZXiJ9p5kJl0y2vISSbSI8Mh3YZcaQz0yaoKDnQDobZrmUj4rCpv+Oi9siCbRBr1RepnLmpDpbR5WvO6cPAtqw0drtkGnWmhdTYKUe1kIjVBFR76appEOlwrq/+MGXgEHKvdBj2m3XI7ohbx38K/h/EW4lwWsAXD6eRi+hsUckZgjEJxqgvmRpoi6f7+G/4kMkBeo6adzOZ7+R0oBDytqZTZfNEsElkBlY4rZw3xAhWLZHpXCwFwCxiieY2MWLJd73bGtdDm9ND5XYa9/gCc4uPCYy2HHSFRgioABZed0lbbtVBWzM6m4v3vl+LNZDb+6usT4bA7/SROpxdiAzsu/y4XR/74QjlI65ZzM5tM345eCZmYTaaDt6MWW8tZ7MltwDYnL0I0fveaiMbvXgPRxxpw92WwoqrwClUF9DiiAwARUh/4DzaPrw73wBiuK+C+rs90WNYYoAJLYmoUcavku5eJ5JJsYXwzHA1HXKd1VSncyUxeliCe9vFmdjY9EToIJcg5I5a1NiRWDsXhexa491ZqA2JZm43wasde4qkSa3S155aNkGuvo8BtuV8fRLdANw43wwe5+/9BvLJX9rLUIYa0wnmwg+BqzIHnArd3QaUiFrdQnBXkfD+07rlLhLJFFOSuAJErK5YgVq62RTQs+Y8x7oarBcG7oMmhhpAxjoGYh9Zf2v0OioMkDXyXpMFS5RuwxeJNSeRDlqZrTWW9HOauSl/k4SQTkfwtlF1fzu3E7tQiK21XqAJhnVONHUG+F3ruTocvYLbCOIL/DbXexXPcbmApet1/zKYEUw3yUiGFJyEf6KWEAGmltE27gyf5PEfjRzCViI4i/gK8cTsur2eZiDqw3od6CWiBIAyvuEsRYBV+Wc0AtzrnvtTT6mDyvE6j0sCtBqFTS6TROdgQN4G+8XqVlyDGsU+1M5R9ZWl6c3MzVFEavXWmIf3p4vvJz7PJYDwcDUuqTOyT3gWqlD1wfA4k7ta9oxazv1vi/rvdsxsQBJ8p9UZpy3MkEtx3m8Rc+ruNuHSB+Gi/X6oAv6FpGj5uJ0E2XyRyq1CrJU+B+aJJ+uHEq8cGuLWf5jl43lO2ytTtbLq3nh7tNOeTS5lI9WCcbeI46x7Yey+yuwPf9+dlC4G/m+QRk/2+HZZNc6vfih616Cj22pzCRdM0fwE45lJ5
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get Profile"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/profile"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches the individual information of the logged in user to populate the Profile page.
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-profile.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-profile.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-profile.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-profile.mdx
new file mode 100644
index 000000000..0a333fa09
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/get-profile.mdx
@@ -0,0 +1,5 @@
+---
+title: Get Profile
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /profile"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-receiver-registration-info.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-receiver-registration-info.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-receiver-registration-info.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-receiver-registration-info.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-receiver-registration-info.StatusCodes.json
deleted file mode 100644
index a8595f4cf..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-receiver-registration-info.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Registration context","content":{"application/json":{"schema":{"type":"object","properties":{"privacy_policy_link":{"type":"string"},"organization_name":{"type":"string"},"organization_logo":{"type":"string"},"truncated_contact_info":{"type":"string"},"is_registered":{"type":"boolean"},"is_recaptcha_disabled":{"type":"boolean"},"recaptcha_site_key":{"type":"string"}}},"example":{"privacy_policy_link":"https://example.com/privacy","organization_name":"Stellar Aid","organization_logo":"https://example.com/logo.png","truncated_contact_info":"******1234","is_registered":false,"is_recaptcha_disabled":false,"recaptcha_site_key":"6Lc...site_key"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-receiver-registration-info.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-receiver-registration-info.api.mdx
deleted file mode 100644
index 260a8a0ae..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-receiver-registration-info.api.mdx
+++ /dev/null
@@ -1,62 +0,0 @@
----
-id: get-receiver-registration-info
-title: "Get Receiver Registration Info"
-description: "Returns the registration context for the receiver, including organization details and reCAPTCHA configuration."
-sidebar_label: "Get Receiver Registration Info"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNV1Fv2zYQ/isEn5pBlhwv6wC9eanRZi06r06xh8QwaOpssaZIjjw5cQ3994GklCqJnaxbMCwvlsjvPn53vNyd9hTZ2tH8in6CtXBoGQqt6DyhBThuhQmvOf0EWFvlCJZAbA9JuFYIt0hW2rabHMQWbEKE4rIuhFoTbddMia/RoABkQjrCVEEsnI+nl+fvxp5mJdZ1JE1pQrWB+HJR0Jy+BfzUEvd1XqiVpgm14IxWDhzN93Q0HPqfh/IfS6YJDU8KPZ4ZIwUPgOyL80Z76ngJFfNPuDNAc6qXX4B7Q2O9PhTxSGPFlvHdwmgp+G4hhdr0jBxaoda0SWg/DgvFKngeJfVaH0ShrRVnCMXCO8E4LoQPxiGocIt4ZWCh6CGWWktg6g7CmUFeskUhHFvKY9BvOCcQFhvYHTi0aRIKt6wyEo4GiJaIxuVZ1gJTrqusRdKDwaIzBCmZJWNRPETEQB3k9FupUWt6PGr0h/B3OvrxjD4K2IpJB0dj1O4eCgt9/YGnaXq30IS4nA1PHyfoZ8VqLLUVX6F4ucQEa7U9mBNwi5a55xkcMqz7OFVXS7CeogLn2PpQDjcP77/VQT9qJPf8/CajO+hseNqjfmjRtNwOeG0F7mh+taezyXR0Nq6xpPnVvJl7cyy1LxtrCB4xv0UzB2Z0NhAKwTKOYguDAox2AjMR64gDuwXrAmltJc0p9XTdYTMf9RiWX4BZsPHMO/eZEe/Bp+79qx238mPxKYEVYEMNYkL56sgUmb2Zkl//uCSvJrPRT69PiLbt6oKMpxdkAztfEtt/gnt8Plv9IZHWX8tsMj0dvpAyMptMB6fDqC36TPaoN6Cak+9S1N3Pyyganb2Eot9rsLu/JytAiWGWVYDHFfUEBEndwX96c+rz9q5GC5T9gvZGuGVtHVSgkEwlw5W2lb97mlCfklHGz+kwHfo8rauKWV9gLksgT3O8mr2ZnhDhCCOotSTLWsjYrfvl0xHUpGIbIMtabohhO88SVhlZW10bole+twsjwobeQuz33ekK8EbbTfoodv8/idfqWl2WwoUjFdEG1MDp2nIgxmpfBgmWDP12lKIVQR3oD9AlYZLxG1wXQDhTZAlkpWtVBMPSv0ipb3y22FhwtBXgcq9jQK5c5Mva30HRC9LAtEEaLBnfgCrmr7oOtxZY1svQ4L6L4SQnwfk7KbsuneN018KCV0KtLHNoa461bR3sBr0n7zT9Ds9WNjS7f+NaR/GcbzewJB32H3tTgqwGvGQW3ZOSe7gMLUBWMaGyduFJf55z4x3IigSioL8AI/XOp9eznpDaedz7eglWAYJLr32VQrCV+201A7sVHHpjVCsz1XadBdBArwauhSVUCg7KhRbfFV7DeAlkFOpU7KGeK8+ym5ublIXdwNaauuzDxfnk42wyGKXDtMRKhjpptMOKqR7xW0DSfQKQe+N8+xFwr+rsv01Q//2nS9tLPHdmJBNhbA6x2LezyBU9OovQtknME1pqhx673y+Zg89WNo1fjt0kv5ondMus8GNoGHySrsH58SXOn2POwXjKLZN17G8Phsl749LbySVNKHvUEjehJbYPnr3bUrse98OeGyWEuTc5YrLfx4bbNHf4uHXUonWxQ/vYzpum+QuUUju1
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get Receiver Registration Info"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/sep24-interactive-deposit/info"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Returns the registration context for the receiver, including organization details and reCAPTCHA configuration.
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-receiver-registration-info.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-receiver-registration-info.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-receiver-registration-info.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-receiver-registration-info.mdx
new file mode 100644
index 000000000..5497f6e75
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/get-receiver-registration-info.mdx
@@ -0,0 +1,5 @@
+---
+title: Get Receiver Registration Info
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /sep24-interactive-deposit/info"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-sep-24-info.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-sep-24-info.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-sep-24-info.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-sep-24-info.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/get-sep-24-info.StatusCodes.json
deleted file mode 100644
index e5dd6fd1a..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-sep-24-info.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"SEP-24 info response","content":{"application/json":{"schema":{"type":"object","properties":{"deposit":{"type":"object","additionalProperties":{"type":"object","properties":{"enabled":{"type":"boolean"},"min_amount":{"type":"number"},"max_amount":{"type":"number"}}}},"withdraw":{"type":"object","additionalProperties":{"type":"object","properties":{"enabled":{"type":"boolean"},"min_amount":{"type":"number"},"max_amount":{"type":"number"}}}},"fee":{"type":"object","properties":{"enabled":{"type":"boolean"}}},"features":{"type":"object","properties":{"account_creation":{"type":"boolean"},"claimable_balances":{"type":"boolean"}}}}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-sep-24-info.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-sep-24-info.api.mdx
deleted file mode 100644
index 6334fc1df..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/get-sep-24-info.api.mdx
+++ /dev/null
@@ -1,62 +0,0 @@
----
-id: get-sep-24-info
-title: "SEP-24 Info"
-description: "Returns supported assets and feature flags for SEP-24 registration deposits."
-sidebar_label: "SEP-24 Info"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVVsFu4zYQ/ZUBTwkgW14jbQHd0sbYplu07jpFD0kQjKiRxTVFsiQVr9fwvxdDyamTZpNNN4fWF1nk8M171HD4tiLiMojiUrynpQrRY1TWiOtMVBSkVy69FuI9xc6bAKFzzvpIFWAIFAOgqaAmjJ0nqDUuA9TWw2I2H01PwB9gQkXOBhXDWGTCOupHzytRiLcUF7P59OTc1FZkwlNw1gQKotiK6WTCj/tsBnhlagv7aJEJaU0kEzkendNKphT5h8CLtiLIhlrkf3HjSBTClh9IRpEJ55lQVH3KgehjgVhVijFRz+8teRqQDJaaqoPA0lpNaMQuE60yN9jazhwmNF1bkk/T+PHz07vdLhNrFZvK4/r/wrcm+ioKPUaquC/QglIymRvpqS/tR0VJjarljDclajTyHvJB5v6XiZZiY7l0l5RSYmxEIfJAbnqSq76MA/lb8ny2tqLzWhRC7K55WHZexc2Cq7HP8z2hJ3/aMchdVnTqHW3Ew4PIUdarT/2Zaggr8sCFj8ooswQ0sDibw09/XMDRbDH95ttjsH4YvYHT+TmsaMNH0GBLD/FEJhQn6WF5Yxaz+ZvJKzFLXeHNpOfWa4ZttCsyu+MXMZqevCaj6clrMPqtI7/5MlopFBx6bCl+ntEBgURpn/hPXi64ClOhcToVNYctImmNHs5UKDsfqCUTYa4x1ta3/O1FJrgkexrfjSfjCddp17boN6IQFw3B0xhHi7P5MagACNFaDWWndEwd3/olmmGLAkQLLa4Iyk6vwOGGUdIowtLbzoGtwZNUTqUJe0se4kF2Q3Ft/Wr8j73771G8MlfmolEhpTRgHZlRsJ2XBM5b7kkQG4w83VOxBqJN8I/AZelC5QlpKwKJBkqC2namSgsbftHarrlafH9RWa8oFMxjBJehx8uH56g62KSRGzZpVKJckamuj5oYXSjyfKli05Vjadv8RQjHBSTxd1Q2+3IOiewQllQpU3sM0XcyuYUkkL9LfO6bjl+grPbJBHyNtD3Ec9rWVMI+9l+raUi3I9mgj+FJygdxefREeYvK5MPAk3qek/Ej6RYSUOJfkdN2w+X1rBLoAse960ryhiKF8RV3qUi+Db/WC/K3SnJf2ssaaI6tX+YpaGTrURjCMqGVJDZyxfau8TqUDcE09an+DmWsIs/X6/UY02xCG5aG/OfzH2a/LGaj6XgybmKrU590NsQWzQHw0GUHw3mvxWz/tpGv7XqHayHSx5g7jSpZjyRrO1iIS5EshBh6+3UmGhsij2+3JQb63evdjof7S6C4vM7ELXrF1oXfdtn+XmLXsSLu6qdSkmOXcou666+lB96Ybcmdo3k7uxC73V9CR0PE
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"SEP-24 Info"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/sep24/info"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Returns supported assets and feature flags for SEP-24 registration deposits.
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./get-sep-24-info.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./get-sep-24-info.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/get-sep-24-info.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/get-sep-24-info.mdx
new file mode 100644
index 000000000..df18413ae
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/get-sep-24-info.mdx
@@ -0,0 +1,5 @@
+---
+title: SEP-24 Info
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /sep24/info"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/grant-distribution-wallet-membership.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/grant-distribution-wallet-membership.ParamsDetails.json
deleted file mode 100644
index 9bf3d3e70..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/grant-distribution-wallet-membership.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"The unique identifier of the distribution account","required":true,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/grant-distribution-wallet-membership.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/grant-distribution-wallet-membership.RequestSchema.json
deleted file mode 100644
index 99416c157..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/grant-distribution-wallet-membership.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"application/json":{"schema":{"type":"object","required":["user_id","role"],"properties":{"user_id":{"type":"string","description":"The user being granted access"},"role":{"type":"string","enum":["financial_controller","developer","business","initiator","approver"],"description":"The role to grant on this account. `owner` is rejected, since Owner is always tenant-wide."}},"title":"WalletMembershipRequest"}}},"required":true}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/grant-distribution-wallet-membership.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/grant-distribution-wallet-membership.StatusCodes.json
deleted file mode 100644
index ebe808f83..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/grant-distribution-wallet-membership.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"201":{"description":"Access granted successfully","content":{"application/json":{"schema":{"type":"object","description":"Grants one user one role on one distribution account.","properties":{"id":{"type":"string"},"user_id":{"type":"string"},"wallet_id":{"type":"string"},"role":{"type":"string","enum":["financial_controller","developer","business","initiator","approver"],"description":"The role the user holds on this account. Owner is always tenant-wide and never appears here."},"granted_by":{"type":"string","description":"ID of the Owner who granted the access"},"created_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"}},"title":"WalletMembership"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}},"409":{"description":"The user already has access to this account, or the account is archived"}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/grant-distribution-wallet-membership.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/grant-distribution-wallet-membership.api.mdx
deleted file mode 100644
index 4b263b90f..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/grant-distribution-wallet-membership.api.mdx
+++ /dev/null
@@ -1,75 +0,0 @@
----
-id: grant-distribution-wallet-membership
-title: "Grant Account Access"
-description: "Grants a user a role on a distribution account. Owner only."
-sidebar_label: "Grant Account Access"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWNty2zYQ/RUMnuwZSpRdt53qzYnd1k2buJYzeVA8zpJciYhAgAFAKayG/95ZgJRli7bjXKaXPMQULouzuweLA6y5g7nl4yk/EdYZkVROaMXegJToLL+KeIY2NaKkZj7mvxhQzjJglUXDgBktkWnFgGXb8yFNdaXckL1aKTRMK1kP36q36jLHtslPTEEp7ViCbE52MWM5GoyYFSpFJhwTloFcQW2ZQwXKDVYiwyE7VgxMmoslZt1SzMECLVOaKVwFc3b4VvGI6xINEKqzrHNg29fg6h9YJGhsLkoe8RIMFOjQUGDWXEGBfMxFxiMuKAgluJzfjQy5VinxoUImMlROzAR5PmMux97g8Igb/FAJgxkfO1NhxG2aYwF8vOauLmlNmqXmvGmuwmC07pnOahqRauVQOfqEspQi9T7G7y2hWe+a0sl7TG8vOuWUxWvvGOWD0l0aipcTaGlu17+DqNd7okSCQs036YQ0RWt509rvMYOqKgjJTChQqQB5TY4ZLSUav8oSJSHiEU8qKxSZozQIJ8BpaoayNHqJZpesBMrzzOmAiJjqciJVx893mtj4johmkAKEWUe/wNN+BvKmibgTjnzidxl0ERLFGxp0O8W+wZZa2RDfw9EB/bkN+9gHbRNDW/nfs0rKmkefn/fejaxVmzf66DYzffduZ36XH33UaKL7adNEfOWjdV/vP0uTjsS5lpndJcsDjGCgMqZwSUWxLBGM9aVsSD61ibxO6sf30dlJVzLCYqtcb4hArTcbKjUIZBVcn9WZNgX18AwcDpwo0OelzJ445wGaE7+biB+NRrsUfgYZ67bBF1D2NtnQGG0eD+EJOhDSMkh05XzQwsQm4vjRGbCPrtSEf+Rbz/Z8raByuTbiL8y+uXOfDppbB67aHqcqShWZKNBamPdsrNZP/AhFGTZei4O/1I7d8vMGRrfQ0ehgy/TdGZsQfrcbwp+1SUSWofr28bvHvRsEHcyjXZjk0c+6Uv/zNM9aF/syfLSd4Qu0ujIpMrWZtcnyT7vh22gCkAYhq1kOti1gdCJv19aIadPVN6/mqKtVeL4IWUwrI1ztBdkzBIPmuHI5H0+vSBsV6HJN8q7UvuJ4hTbm8fYpNggnj43XImviYlPH6KCwaJad3KuM5GPOyWy36oSyG8K/vfYmzFCKF1jvVKLjdjd4qrAcIUPDiEggFKkkUGxycs5+e3PJ9k4nh9//sE9hCK3X7Pj8jC2wpkO3VaC37HViNJil9E9Ozw9GXwkZm5yeDw5GAVvwma2dXqBq9p+E6PDoayI6PPoaiP6s0NSfBssPZZsLwX2ItgB4SN3CH2i6JzAViosbBX96sxU3YunmQAsqqF/sNGR6pj309mSeOJQSDDsRNqmMxQKVY+cSHJ3oxCMecaJ3cOnH4Wg4Is5XRQGmbjfqwzb2Jifn+35TMqe1ZEklJJUAw7SZg2rD7bd1AQtkSSUXrISarPhWYHOjq5LEjcFUlMJ3kB7z275bXaFbabMY9t4v/l0Qw3VWWL+kYrpENWjLY2k0lW7mcvCVLEAhOanLTt7dMRd5AUkdqc78xZhuxb7GBh1KP6TUK2KewVJb4bQRaMeEY8CmNtiL27+DbCtIg7IN0iCBdIEqu9rLnSvtOI7nwuVVMkx1ET/Jwv6Yeec3UOpua1gPth3mvRJqZsA6U6WuMq2DM307qr05HT7Bs5nxB/SXuNaZeMy3FSasG/vZ3uQoi0Gag3H2Qchb42JnEOMChIrbhgf9ecyNX1EWzBvy+DMspa6JXo96wuiGNWcvqgSNQoftQ4tDU9hXswmapUipLnVutTCH2sxjP2igZwPbDou4FCkq62thV8RLSHNkh75OhfOYbI3jeLVaDcH3emvtVBv/fvb89OXkdHA4HA1zV0hfc0kMFKC2DPtbLztuRUa4aN+tNVtPK//F5672PHP40cWlBKH8xY9iuG5l0ZT3ySIe8bF/CdpWRlcRz0lRjad8vU7A4msjm4aaw8k2nl5FfAlGQEIn0XRNpuk74+MZSIsPxHbvon0a2Wef83bW62d3mCs6yZcgK/rFI77AOrzgNVdN1MkBghs6ngdQg0uafjNxR+g3UTeDqFO6B8duy9LzV5NLeppo3+4KndEcAys67GEVQGofJK8yfduaS1DzKmjvYJNYDTvCZeGFS/tBXvWG4a4yCo7Q/+RW75T1OsiiptmMD133zmhDu4k4xaFpmr8BXiXjFw==
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Grant Account Access"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/distribution-wallets/{id}/memberships"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Grants a user a role on a distribution account. Owner only.
-
-The Owner role cannot be granted here, since it is always tenant-wide. An archived account takes no new grants.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./grant-distribution-wallet-membership.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./grant-distribution-wallet-membership.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./grant-distribution-wallet-membership.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/grant-distribution-wallet-membership.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/grant-distribution-wallet-membership.mdx
new file mode 100644
index 000000000..57e3309bb
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/grant-distribution-wallet-membership.mdx
@@ -0,0 +1,5 @@
+---
+title: Grant Account Access
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml POST /distribution-wallets/{id}/memberships"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/index.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/index.mdx
new file mode 100644
index 000000000..620bf87df
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/index.mdx
@@ -0,0 +1,4 @@
+---
+title: API Reference
+description: "View all Stellar Disbursement Platform API information."
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers.ParamsDetails.json
deleted file mode 100644
index a680a9a4e..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"ID of the Disbursement","required":true,"style":"simple","explode":false,"schema":{"type":"string"}},{"name":"page","in":"query","description":"The page number to fetch.","required":false,"style":"form","explode":true,"schema":{"type":"number","default":1}},{"name":"page_limit","in":"query","description":"The number of records to return per page.","required":false,"style":"form","explode":true,"schema":{"type":"number","default":20}},{"name":"sort","in":"query","description":"Field used to sort receivers","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"updated_at","enum":["updated_at","created_at"]}},{"name":"direction","in":"query","description":"Direction for sorting receivers.","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"desc","enum":["asc","desc"]}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers.StatusCodes.json
deleted file mode 100644
index dd4875e79..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"A list of Disbursement Receivers","content":{"application/json":{"schema":{"type":"object","properties":{"pagination":{"type":"object","properties":{"next":{"type":"string","example":"?page=3&page_limit=2"},"prev":{"type":"string","example":"?page=1&page_limit=2"},"pages":{"type":"integer","example":8},"total":{"type":"integer","example":16}},"title":"Pagination"},"data":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"ec3a57c0-5660-4b5a-af76-acadc7b09b93"},"email":{"type":"string","example":"receiver@mail.org"},"phone_number":{"type":"string","example":"+15552368475"},"external_id":{"type":"string","example":"usr129001"},"receiver_wallet":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"enabled":{"type":"boolean","example":true},"user_managed":{"type":"boolean","example":false}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invited_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"last_message_sent_at":{"type":"string","description":"timestamp when the receiver last received an invitation about this wallet","example":"2023-02-10T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"payments_received":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"canceled_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}}},"title":"ReceiverWallet"},"payment":{"type":"object","properties":{"id":{"type":"string","example":"ddf22f55-3259-4822-a4e2-ce01334997f4"},"amount":{"type":"string","description":"The amount of the payment","example":"100.00"},"stellar_transaction_id":{"type":"string","description":"The ID of the transaction in the Stellar network. It can be used to track the payment in the Stellar network using [Stellar Laboratory](https://laboratory.stellar.org), or [StellarExpert](https://stellar.expert).","example":"0b339d1c89d314186b8147c2af4c9a9ed5bbdbcd7ada8d138633907649b"},"circle_transaction_id":{"type":"string","description":"The Circle transaction ID. It is only present when the payment was made using Circle.","example":"74a68b6a-3f67-424b-b8b0-e593a19d7463"},"circle_transaction_type":{"type":"string","enum":["PAYOUT","TRANSFER"],"description":"Which Circle API the payment went through. It is only present when the payment was made using Circle.","example":"TRANSFER"},"stellar_operation_id":{"type":"string"},"source_wallet_id":{"type":"string","description":"ID of the distribution account the payment was sent from.","example":"4c379f5e-09b5-4472-a286-b84e249a1512"},"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_history":{"type":"array","description":"An aggregated list of metadata objects containing the statuses and the timestamp of when these status changes occurred.","items":{"type":"object","properties":{"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_message":{"type":"string"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"PaymentStatusHistoryEntry"},"title":"PaymentStatusHistory"},"type":{"type":"string","description":"The type of the payment.","enum":["DISBURSEMENT","DIRECT"]},"disbursement":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","format":"uuid","example":"c51ba1d5-52d3-412f-a59c-6ef32d59ab43"},"name":{"type":"string","description":"The name of the disbursement","example":"disbursement-june-29"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: `{{.OrganizationName}}` which is the Organization Name configured and `{{.RegistrationLink}}` which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED","CANCELED"],"title":"DisbursementStatus"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"status_history":{"type":"array","items":{"type":"object","properties":{"user_id":{"type":"string","example":"3f351b9e-ed0f-40fa-a314-14757b42dab1"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED","CANCELED"],"title":"DisbursementStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementStatusHistoryEntry"},"title":"DisbursementStatusHistory"},"file_name":{"type":"string","example":"disbursement-feb-03-2023.csv"},"created_at":{"type":"string","description":"The creation timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:57.831975Z"},"updated_at":{"type":"string","description":"The last update timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:58.316511Z"}},"title":"DisbursementLite"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"receiver_wallet":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"enabled":{"type":"boolean","example":true},"user_managed":{"type":"boolean","example":false}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"sep24_transaction_id":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invitation_sent_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}},"otp_confirmed_at":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"},"otp_confirmed_with":{"type":"string"}},"title":"ReceiverWalletLite"},"external_payment_id":{"type":"string","description":"Optional external payment identifier provided by the client.","example":"payment-001"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"Payment"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementReceiver"}}},"title":"DisbursementReceiverPagination"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers.api.mdx
deleted file mode 100644
index 53b93dfcb..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: list-all-disbursement-receivers
-title: "List All Disbursement Receivers"
-description: "Fetches a list of receivers within a specific disbursement using the disbursement  `id `. This endpoint supports pagination and sorting."
-sidebar_label: "List All Disbursement Receivers"
-hide_title: true
-hide_table_of_contents: true
-api: eJztW2tz27iS/SsofthJakWZT72qbu0qlpwokR+R5ORmMi4FJJsSxnwNANrxdem/bwEkJdKiJNvx7M3cmi+JRTYapxtAd+MAvFc4XjCl91UZEOaklEEIEWfKVUPxgLmUJJzEkdJTToC7S2AIo4AwjmIfUXCB3ABl6JbwJYkQRiwBl/jERV5JGUoZiRaIL6H6GH0jHvrWRLMlYQgiL4lJxBFLkySmnKEEL0iERe8IRx5iMeUkWjSVhhInQOWLkaf0lDFhvB8EZfiTApnSUBJMcQhc/Oh9vVciHILSU4inNBQi7EowXyoPjR0NhIECcVmt0lAo/JESCp7S4zSFhsL4XSD0MRImASgNBb4nQeyB0vNxwISAu4QQK717hd8lUpJTEi2U1aqxBpPgBRRw/kiB3m3hmS1B+ANQlIYOUMRj5IvxaFYgFV3mmPyYhmVEOeKHgDKVsksfpwFXevpDcPOAhIQfhpijy+ZGTD0mgFLgKY1QAlSa8OdANrQyZjFX9qM9IRB4KGXgCYhCfjOdXwBgPsglgEqaeJiDN8cCGURpKNZc5aFLofhxVbbGIxRciXuvSYNCDPkxLZbLxqqX8HuNWQJDySAsf8mHV6vVleiSJXHEgAk1hqaJ/6q4++uAUl5rqLyG3TjiYv317hWcJAFx5eo/+p0JBffbOGPnd3CFSxMqYgUnWfebiHJYNoLvvM5y+I7lSu8p/yNm8z/M/9oskH8YykrogZvHtNS3W+JF1nnelEQcFnKer9t2Vg2FxxwH+8X01koIEi77u9jYvWooHuZlX2FKsZhMhEPIDvuFePttA9fEdtvVVLvV0lTLsbGK/XZLxS723LajdZ2uKVBAiEmwX1Uxdf9XiDZjupA+WsYRzPMAsLf5f+u2bRtmq2O1bdnjdw40wsH8kAkpo7rR1TRdtCpAzG9xEAD/cQd1NFMzdc9SdU+zVKvT7qpOy+uqnmu3LN3vdjsdKHf84z1qRhcM8DTVB6elWq6lqR3Haqtax2zhjt22dGwo5flSLL0x4RLKS5luYw93wbNVy7axarU7hoo1AFVvae1WGzQPHOnzLO7t0/SJOBRHHPUZI4yLNss4BJlH97Zbcp6w3tHRTdYeJ0nTjUPRnkEy17W5GxCI+NyLQ0yi/bpwQlQPbprbujyAZB6Q6Hq+O4IewnTEvESolzM3wk4AZec6cRwAjsp6RMheNZSUAZ2HOMKLQw1kCigP+2c5zMWgMw5BgOkcex4Fxvbb8Pb4n/335j/fm58+mO9P3pkfTwcn59MPp8bZ6emvb6bn5qfRrDW8vPj4eTr4bLxvW6eGOZlMx+WOQgjjmjqpKjDP3tZIlbLnXqiGZpiqZqiaOdO1nmX3bL2padqvQkcpHT9bB4luyJN0dLd1BJjxeQiMiQTBxISs11ZNpJyEwDgOE3S7hEhWr0UQQUJj8ctDOEISZl5dO3HKERdVeL7S63Dq2jZOmYnmCb7L9gz77c0yXCY6L6A8oo2PSQDeI3vR5FTAkQtPbENFQopItHhao8yKOQ7jtNrkiWkVMwZ87sria1+3l9PBseg5kyeMpYfS4Ns3bwZWe3TSGn/+0L5onw6Gn6bHnyftwcXl50/m2RdzMPs4/HQyts76M6v/8Z3563h8Mu7bNfbt70jXtKamVRJJP2u2kosY87Tep3npOJj0T2ZKQ5kM+4Mv8v+3o+lsOBkOlIZyMu6/fTsciG3pwyzFsrg1zTpYdzVfEsZjevf8Mfl/hLxeunW9ieIcy1obc1CF6KEF+mttOq/0+i7zzjDi9E5Z1Yln0qVV++MFgOf5huHbtmoadle1OoahYgsM1QVNN02r2237lpzdO6fb9p4zky226wXUuom5ySSc4ohhuVnaUQ1u97OhBEqtEcni7DRTjCLgtzG9bqIRRy6OkAPrPSan2L0uY9zRNmdLvhaPx9iJKRZjdfWqKBWC9bNmbpIoj183UEzXDYffxcBs2hSCIJ+/blajmWOaXU93O13P1C2903I6utV2DexbblfWbI7jOa7Xxh7ueLrZaZlmV2u3rK4jAy6hbgDPcuuxbFrx6Wgg/UcYiqPgDiUURArcJLXCf7eYoRB7kHss01S1q23hVsdpYdX0W23VMixHdTqOpoLdNbHe9dpWy9xhQH2hsVn7F/0v55di8c8m/bPpyXCyTZl9XhJ3WVjYvxhV0Yt/+JLG6WL5YvausZQm+5otqx0TIRin1IV8g/OogdusBY8IESfNCgnXlWvxIWhpjk/jsArWcs1217dB1bqOrVpW21Cx0WmpTscCw+pi3dYNZW/q2J5OmWxNNNgRsS+GZ4PR2VvxV/9yKuP29PL4eDidigjeH43lo+P+2fFwXI3lF5nuJ6SdB7RHhPBiQWEhKs41BRICx2KDjrIIy5CgPrLCRFqUdSJo2MjLgtG66Iv99ZRha0e4SxwtgKHYdVNKwWu+RPr7Gd2eV8u1E/wlsmup1K9m1wqgalbdLyTf7wgy2x4WEg/82yw7eDR9czmZDk+HZ8LPg9FkeDxTrsRmtExgPzODb8NJI/JHCoh4EHHik4z0fcjwl72bppJy3zjWtXUH656t2oZnqpZu+Cq2u67aAt80PLuLHcvcRwbUsM84hB0wSiVI6YX6exqBanQrPA+FhYhpWcQs9mAcwiTA/JFA3JTxOERFow3NDJFX2njl7HjBzyLR9FvOrH5DedeIsOgXnpPo4DXRKEsK+etfsgghywn+C0NJzBhxREKNEfayEOHHQRDfyghSILrBlAhOgfXQt/v75jld4Ij8S6I6wyGsVt/QrUxehEkVZQEkJESvPlmkVO4mPallUvLcmETXW1oEJYIWEIl8BB5y7tB0cLF2jKiRylvWVyRCLmaQ7UwJQ1HM18mRVLzQyIzHKY9DzImLg+AO4SSByBP4sowEkfeg6vkSp2iJbwDhUroikjYXFPpdnMqshWo91ETHAXGvUa3h2ciKp0Cb2fQqzSoZ011+sMQYnvZHYxEj352fDednl6dvhhOlkT2e988G88/98Xg4m/cHg0kWOsuSdRKVvcgG0XEGaCZwPGuvNp31JzMZs9fx/Pj89GI8nO0M5GWyfxPNb4CK88PMT744pNkLoz8bzs9P5m9Gk9k7paF8GfYn89PzM/njYnSmNJSz/mx0ftYfz0eDwoMlEJ9K3ckjoZfcP0oq7tCWyPRNW3e6oIKn+aql+VjFpm6putW2245leDjjRP+NY/Knps/tLnfl0J2SkiQiAcwP88aV6O+Do2qmKiA2XXZzmESsifRCXsTEShm2Lw/uc1NLNbWZpvcMo2e3mx1T77btR/CS27Ak25c1enlknaapt2x9zzgWFLIkqX6cNfB9DK7lmKrVcjTV8hxLxZZrqS3XtLWOZrfbmmSrdrFnD+puAQpJ2TpibTelVqcmk0YFR/5SvNv+afisJXdoEj1TqQcB/KDSVq7U3gSH7RldsCFySqH1RFoTjXKm/X1c9/dx3d/HdX+N4zoGiWEdZAx/tnO9rC7dcyL3uPO9vw9DfurDkIYS82Qud7g0/NGMWUXyULW4OVkz7XcexxTLfX2ZJd+4Poq2PZd/4AAVrTdHERseJ6HxDfGy7bkoF7MQW904583U/I7MX6Vc2Sbk/qLo6+66Vg/x6iTK18CksKXpytZ1vMsIp3wZU/Iv8F7u6h1QGtdU1dlMpvg5ASi/A7ZqKLu538zOtWfXOJSzmKOKnRsYRUeWppdUP2yxKlxobrvwJKYO8TyI/nz/7TBvg6CAaW3DFBadxGn0Hz7Mfm5i3Qhb5RGeQHYSJonGrNUqV83ATSnhd/IK+RvAFGg/FZH765W45BoCX8biLvpCXp6RV8p7ylF5p82O7om3OipfMmZAb4pr6SkNlJ6iCGVFX1Ph88wp5R43CTwhH6DmXCmfoxkvsQTsAS2fIuFIsq7vP8/Qq+HUsFuvxalx9nQuTymv4U6E+/z2cUVfcQM5UysGZTq80LUXQoamwwtV1zJsmc3onsfXEK1ePwmRYb0kIsN6CUQfxaXtx8GSomj94cIuRCUAElL1evhK1qx+VqPnWaHYRVcuWl8EmIuEJMZekQwsy2C0m1pTE/M0DUMsasfKTrxex6vp4OK1IOsx4nEcICclAZdselxi0OXJR4ivATlpcF1UIfIpRgsap0n+DQFJiHwRiwOBuosWtfTXzwXxt+i3aJYfYeAIxQlEah5oEhqLIIj4Esvz/wyKoBPjNV33QF1jffIrKKzikomMVrJh5byHQhIzwmNKgPUEDhV9zbdnxX0QtUKJJrmTVAe71xB5m+sjC8KXqZNtdZ+i4XUv+75nDeWumM7ZmVAuJq0ikU8x4zR1eUpzA8W48ENj2nyCZT6Vqe5HTCtUHLLtFhxUyD7bmiUEoeouMeVsL+SS3BGnAEeCEjnKH+y155AZ7yAIkVQk8XuQBPFdcSFh/1rLbqp8SB2gEXBgzd9ElOJAQ3buT4HeELfMqZQuMx1JITX2VZaLNZSAuBAxmeCLwJtgdwnIkHEqy6FCV+/o6Pb2tonlW6ktb8qOxqPj4dl0qBpNrbnkYSDjZBIzHuKopFh8VIb6QbD7m5RK2LnfFFA/04dyeZrh8J0fJYGgyFa5m+7zIuVr5UhE2NWT5/SbOuVKkHWMC9H7ewczuKTBaiUeZ3lGVC8eYTnllX9XtNM5+z5kq0V7DXebL+RucJCCrJMaT+30sZ+mHQCx/hLumVAOfHe2p/f8m7Zn9vuIj8P29F3+Am0D4Er8yO4RPHEWvJrkH6K9Rju/tKyFU9RN0V0ZSQGTeMpKXHnJKy+BKXvRd11Iyt7b2uNUqvi3Q8Fj4a1a7VrWavkfQnstnIfFYAZB/CuGrLbJ/X1WCa5Wa/ns1c4WuYlry4UFq9Xq/wBaEya3
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Disbursement Receivers"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/disbursements/{id}/receivers"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches a list of receivers within a specific disbursement using the disbursement  `id `. This endpoint supports pagination and sorting.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./list-all-disbursement-receivers.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./list-all-disbursement-receivers.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./list-all-disbursement-receivers.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers.mdx
new file mode 100644
index 000000000..3ac7c7d2e
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers.mdx
@@ -0,0 +1,5 @@
+---
+title: List All Disbursement Receivers
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /disbursements/{id}/receivers"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursements.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursements.ParamsDetails.json
deleted file mode 100644
index d3bc4c9b1..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursements.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"X-Wallet-Id","in":"header","required":false,"description":"Optional. Narrows the results to a single distribution account. Omit it to cover every account you have access to.\n","schema":{"type":"string"}},{"name":"page","in":"query","description":"The page requested.","required":false,"style":"form","explode":true,"schema":{"type":"number","default":1}},{"name":"page_limit","in":"query","description":"Define how many results will be returned in the response.","required":false,"style":"form","explode":true,"schema":{"type":"number","default":20}},{"name":"q","in":"query","description":"A search term used to query through the disbursement names.","required":false,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"status","in":"query","description":"Comma-separated list of disbursement statuses to filter by.","required":false,"style":"form","explode":true,"schema":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED","CANCELED"]},"example":"DRAFT"},{"name":"created_at_after","in":"query","description":"Only return disbursements that are created after this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"created_at_before","in":"query","description":"Only return disbursements that are created before this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"sort","in":"query","description":"Field used to sort disbursements","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"created_at","enum":["name","created_at"]}},{"name":"direction","in":"query","description":"Direction for sorting disbursements.","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"desc","enum":["asc","desc"]}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursements.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursements.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursements.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursements.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursements.StatusCodes.json
deleted file mode 100644
index 709538ce9..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursements.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"A list of Disbursement details","content":{"application/json":{"schema":{"type":"object","properties":{"pagination":{"type":"object","properties":{"next":{"type":"string","example":"?page=3&page_limit=2"},"prev":{"type":"string","example":"?page=1&page_limit=2"},"pages":{"type":"integer","example":8},"total":{"type":"integer","example":16}},"title":"Pagination"},"data":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","example":"619da857-8725-4c58-933d-c120a458e0f5"},"name":{"type":"string","description":"The name of the disbursement","example":"Disbursement Name"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: {{.OrganizationName}} which is the Organization Name configured and {{.RegistrationLink}} which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"created_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"}},"title":"Wallet"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED","CANCELED"],"title":"DisbursementStatus"},"source_wallet_id":{"type":"string","description":"ID of the distribution account the disbursement is funded from.","example":"4c379f5e-09b5-4472-a286-b84e249a1512"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"status_history":{"type":"array","items":{"type":"object","properties":{"user_id":{"type":"string","example":"3f351b9e-ed0f-40fa-a314-14757b42dab1"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED","CANCELED"],"title":"DisbursementStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementStatusHistoryEntry"},"title":"DisbursementStatusHistory"},"file_name":{"type":"string","example":"disbursement-feb-03-2023.csv"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"total_payments":{"type":"integer","description":"Total number of payments","example":10},"total_payments_sent":{"type":"integer","description":"Total number of successful payments","example":8},"total_payments_failed":{"type":"integer","description":"Total number of failed payments","example":1},"total_payments_remaining":{"type":"integer","description":"Total number of remaining payments","example":1},"amount_disbursed":{"type":"string","description":"The total amount disbursed so far","example":"800.00"},"total_amount":{"type":"string","description":"The total amount to be disbursed","example":"1000.00"},"average_amount":{"type":"string","description":"The average amount per payment","example":"100.00"}},"title":"Disbursement"}}},"title":"DisbursementPagination"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursements.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursements.api.mdx
deleted file mode 100644
index 598d4abc7..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursements.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: list-all-disbursements
-title: "List All Disbursements"
-description: "Fetches all disbursements the organization has created. This endpoint supports pagination. The response includes basic aggregations on payments within the disbursement."
-sidebar_label: "List All Disbursements"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVWutz2zYS/1cw+HBNZkSJelmOZjo3iiVffPWrlpKcm3pUkFxKqEmAAUC5qkf/+82ClEQ9LMuOcu198YNY7P52sdhdLPBIDRtp2v5Cu1x7qdIQgzCa3pVoANpXPDFcCtqmp2D8MWjCoogERVJixkCkGjHB/2RITMZME18BMxCUyWDMNQERJJILQ3SaJFIZTRI24sKSIwkQBTqRQgPhwo/SADTxmOY+YaORgpEl1EQKkrBpJvWBmzEXVngRTpmWqExA2RlnAW3Tc65NJ4pW1SvRhCkWgwGFyj9SwWKgbfof5zOLIjDOWUBLlKPiY2ABKFqiCr6mXEFA2yGLNKwb6Mr+waIyuWRKyYfMMAp0GqGRJGFEczGKLF6juJdaYzHfl6kwZXIVc0O4QUpfTkARmICazsfJVKZkzCaAH0Ajw/Kvgpao9scQM9p+pGaaoArIW4zobFZaaJWwEczV+ZqCmtJ18LgESEVQSdC4cts01mYaIcNQqpiWKPyRRDIA2jYqhS1QRBp71nQBhCyNDG1X12ENIx5zsxtcF0IugIzlA4mZmC5s+sCjiHiI2aRKQEByf5j70vdRoeYWdfi6G3qHaGDKHxMDKiaphgDX19ISM1YyHY03XJgga30I8FtcQRtmUr0b9ImMY+ZowC1iICAR14bIcBVkxgisZ4c8MqCINz0g6BIFkcY2MN10Tge0RG96ne4tLdH+oHMz6HVpiV53PvbtHydXF9fnvezjSefypHfe69K7GQpjcWKlZ1wKlsgj1JCZIQuNXeMdNrkS0TR3tI3wxwxhCuYhj1huxGDcC5iBMjmVKmamTW5vb2+diwun2z3g2hZ1rLnukeNWHbf2hKIehFI9EwpeoGnG7m+kqpbqmVhyyiEKFhsR6VeVPKQDL0JGYQkKfm0xl4pjd8WdGnAFvkW9OzjOyUgolVWIi9GqTgfdlUulEEdBHWb/sx/vZrM7FJmFYY1saq6Lv9aj4zy0FLMzCcAwHuFS+FIYEAZnsiSJuG/TeuV3jdMfN1FK73fw0caJwiLA8Ez4sth4nlbAH2ZrNFq43j8xb/1Y/8cyff2ITkgTBZN9ZlY3Z7JRJjyfyoWBkY1Ii7nHsxI10rBoN1n1aIaE3Fh510u9ZyUaMFO0FVOKoTtxA7F+3i482O4N61VEKvjXFAgPQBgeclC4vOspbsUqR9V3ATtutpzjVq3pNPzmsfOuXg8cv1pzWaN5DG7YRPzZvtgHA1I+K3bF5S6R9wx91gc+ATVUMMIqzRpvGIPWuGQG4iRiZk8UfqqNjMl80jLogMBSZcJNXtYaSeZydVYN/5bvst9ILppwLX4wi0qnTM6yUicf/kGTfKsQbn7QJJFacy8CW3YGgSUNZRTJBwwOC0QTpjjzItBt8vhYvirU8GiP2Yw8jLk/JjwrZYvj1mAoM+SjVGHSEwHyuCmY7ZyL+3UeERf3ZAQCssrCm5J+93phFCPz+i0zBnnDBfGZzjMM10RIQxIF2iq6YoFSpjhLjYyZ4T6LoilhSQIiQHTG0oII3pZXnOB2UVXPTxbkgXEbQjGcYtEdKhlvN0+ZnETcv39Cb7uq+BVUOXOtgkfhajHfDDMverr26V10zs6x0vlwddkbXn68eN+7oaXs87Bz2R1+7pyf9wbDTrd70+v31yi3Udwtw0MR9EkGaIA4ZiX6YE9Br40KS/s2WcDeQdB0Gs0mcxqt45rDXACneuS2jlrgBuBVd+3tJadP3FNMGNLRmmuDc8YyBnuy2TlvbEyi25XKJJvPkqTsyxjna0iGVXfoRxyEGQYyZlzs5sUS7gQwKW/yCgCSITr3cEc9+wymig4SZI/8CkXBFk6hrbIwBTMDjuG2jijWRrW647acenVQc9tNt91olo8ax78g4zQJvgfjQtLJDtAoi2l9CB8KQwZ+w6s7jSPPdRqB13BYw284R3696R67zVbLtfnBt/XLc5G5g6CIpS0K+djvniATrnUKal82GTWGWAVarzD81/v33Ubr7PTo/PNPrevWRbf3qX/y+abVvf74+VP98rbeHfzc+3R63rjsDBqdnz/Ufzk/Pz3vNA+0+jXHrQ+quELtZvVQK7/JNIAIvpHpUc60mTOdbculfQNRxBSxLkUWjjT3Obsadk9nx9vvcZpcSitWDv1MIIqWqfJhmEXO4T7l0lm3UKRsdIQ2+wJckzC1+Qxz0moia/j11ruwCY77zms6jUar5rDa8ZHjHTeg1njHqs2qLTUnoHiY19HDEA9DO43VGfSGV6fD92c3gw+0RG97nZvhxdWl/ef67JKW6GVncHZ12TkfnnXn+algqk8FcfbotVyk4ZhrI9X09SVpqkE9YeilYephvVn13oEDgRs6DTdkDqtXG0610Wq2vEYtYFkG+gs9BzeGNixODrYxZ7tEfsjs3hNGTek+lEgU8giGz2fpor86IXiOW3cQYtnXh8pr/6PIZg9bw3m7eeupay1M4QSS9QtxXy+mFo9n7gbnoc4PuC9kr1PbBw7TaKuk401BIeMRBK8QlU3crtCmGAVYSKHtXy5pMfdJYSzG2Dic+9meh1ILkWRzFzE1IFqSkK2cn+mx65Zdd+kA2ZxXSDESW9NLnEUhVXchhU1A4dHyJXLyOXNJCai5udalWCFPbHE6e2qk2DawRA23utm8+ShYasZS8T+tdgdq1YBSckv5ZXt/RrE9ssJGIM9b+LMSzc+K2zrks2J3cQGDXkpDVtRcopjLabjVAuf1Gd+TcbY09c2lOZXK40EA4vuvy3btlgD2ILB6aPBTxc3UXsa9B6ZAdVIzpu0vd9hLjMGMJd7mjcBiYzhEK+utWw1qMr/RS1VE25Ti7DnzPiqb6VMUsaw/Ev4TbLnEya2e327a+0Dbb8ljFRO2i/HvzwPyptevNY/eEqnyr0PSuT4j92CvRvLO7gq/tWvGWYn2e9dV90DISL937VTdDFumM3k08h7E7O2LENUah0RUaxwC0c/YEN8PliUlizvfpxAVAFhIq6139FMuQmnF5XFzfjBZ6SZeR8xg2YFrT23NrTMYrbJbdtFP0zhmWPquHG6283jT716/xdqfESNlRLyUR8Z2p4qX7raLGLN7IF4a3S+vye2980jJNMnyq88TbgfsFbMpSBdgHqS6L29NOX8viL+KX8UgbwkyQWQCwsmOXyRREuNXdlfFdQ5FCmJkMj9trbEr2eYlDmBXgPhMYOYOZSoCO3Gld6ogkZobqTjoNuJwyBed8avkv52VIjjJjeR4zL8HEdy9mXd/RtyMUy/r/LyEw9t29qhiAWU6d+esx5qTWa24CBXTRqW+SVWuIK6LeW5Nyy/QLFQ2x3yLanMWz+n2AB6Z075amzFEseOPmTJ6J+QCXcUogAoWp5X8w059nlPjA0QxsYws/gCSSE5ta/7ZvZbiIxLyU+qBEmBAZ69A8HmBvgr7oCbcL7YYc5hlqUYVS+TI0NE5WYlG3AehbWqeB96E+WMgNRunshyKvNqVysPDQ5nZUcstn6or52cnvct+z6mV3fLYxJGNk4nUJmaiwBjf4ZBOFJH1lzgr0eZxWbD8Pz05yrOPgT9MJYmwkTzLrfeYFytf6GqxcocNbG1w4PHRYxo+qmg2w89ZssESJuAar2eeeHFUNNX29ztbUd3DdPkkaMKiFGyZVHqJuG95kfMMqMWDoFdC+7YXNzvAfX09pm97ULMD0+I1zyuBHfxVyw6sW97bfH/Ue75Q2Q/24vXMK3Hv8fZk11pnb1teu2P3eyayQ37xPcoSxB3+k90i27NaaV6kvyx+/UWPJ3eou/oSdMXqGUHH9yEprsjG8Xrl4PqvHvaO2cZp5d6eVvI/0GjzITEt8F4/DmUQ8CcC2jrl8TE7C81mC/ps6MkZi5euGTVa4242m/0XJXclWg==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Disbursements"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/disbursements"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches all disbursements the organization has created. This endpoint supports pagination. The response includes basic aggregations on payments within the disbursement.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./list-all-disbursements.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./list-all-disbursements.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./list-all-disbursements.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursements.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursements.mdx
new file mode 100644
index 000000000..081db4333
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursements.mdx
@@ -0,0 +1,5 @@
+---
+title: List All Disbursements
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /disbursements"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-payments.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-payments.ParamsDetails.json
deleted file mode 100644
index 8dec9fb79..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-payments.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"X-Wallet-Id","in":"header","required":false,"description":"Optional. Narrows the results to a single distribution account. Omit it to cover every account you have access to.\n","schema":{"type":"string"}},{"name":"page","in":"query","description":"The page requested.","required":false,"style":"form","explode":true,"schema":{"type":"number","default":1}},{"name":"q","in":"query","description":"Search payments by ID, external_payment_id, receiver wallet address, or disbursement name.","required":false,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"type","in":"query","description":"Type of payments","required":false,"style":"form","explode":true,"schema":{"type":"string","enum":["DIRECT","DISBURSEMENT"]}},{"name":"page_limit","in":"query","description":"Define how many results will be returned in the response.","required":false,"style":"form","explode":true,"schema":{"type":"number","default":20}},{"name":"status","in":"query","description":"Exact match on the status of the payment.","required":false,"style":"form","explode":true,"schema":{"type":"string","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"]},"example":"DRAFT"},{"name":"receiver_id","in":"query","description":"UUID that represents a receiver in the database","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"b6b667ad-6cc2-46cf-9be7-561daace7d48"},{"name":"created_at_after","in":"query","description":"Only return payments that are created after this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"created_at_before","in":"query","description":"Only return payments that are created before this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"sort","in":"query","description":"Field used to sort payments","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"updated_at","enum":["updated_at","created_at"]}},{"name":"direction","in":"query","description":"Direction for sorting payments.","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"desc","enum":["asc","desc"]}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-payments.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-payments.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-payments.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-payments.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-payments.StatusCodes.json
deleted file mode 100644
index 12e8d0db9..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-payments.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"A paginated list of payments","content":{"application/json":{"schema":{"type":"object","properties":{"pagination":{"type":"object","properties":{"next":{"type":"string","example":"?page=3&page_limit=2"},"prev":{"type":"string","example":"?page=1&page_limit=2"},"pages":{"type":"integer","example":8},"total":{"type":"integer","example":16}},"title":"Pagination"},"data":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"ddf22f55-3259-4822-a4e2-ce01334997f4"},"amount":{"type":"string","description":"The amount of the payment","example":"100.00"},"stellar_transaction_id":{"type":"string","description":"The ID of the transaction in the Stellar network. It can be used to track the payment in the Stellar network using [Stellar Laboratory](https://laboratory.stellar.org), or [StellarExpert](https://stellar.expert).","example":"0b339d1c89d314186b8147c2af4c9a9ed5bbdbcd7ada8d138633907649b"},"circle_transaction_id":{"type":"string","description":"The Circle transaction ID. It is only present when the payment was made using Circle.","example":"74a68b6a-3f67-424b-b8b0-e593a19d7463"},"circle_transaction_type":{"type":"string","enum":["PAYOUT","TRANSFER"],"description":"Which Circle API the payment went through. It is only present when the payment was made using Circle.","example":"TRANSFER"},"stellar_operation_id":{"type":"string"},"source_wallet_id":{"type":"string","description":"ID of the distribution account the payment was sent from.","example":"4c379f5e-09b5-4472-a286-b84e249a1512"},"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_history":{"type":"array","description":"An aggregated list of metadata objects containing the statuses and the timestamp of when these status changes occurred.","items":{"type":"object","properties":{"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_message":{"type":"string"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"PaymentStatusHistoryEntry"},"title":"PaymentStatusHistory"},"type":{"type":"string","description":"The type of the payment.","enum":["DISBURSEMENT","DIRECT"]},"disbursement":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","format":"uuid","example":"c51ba1d5-52d3-412f-a59c-6ef32d59ab43"},"name":{"type":"string","description":"The name of the disbursement","example":"disbursement-june-29"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: `{{.OrganizationName}}` which is the Organization Name configured and `{{.RegistrationLink}}` which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED","CANCELED"],"title":"DisbursementStatus"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"status_history":{"type":"array","items":{"type":"object","properties":{"user_id":{"type":"string","example":"3f351b9e-ed0f-40fa-a314-14757b42dab1"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED","CANCELED"],"title":"DisbursementStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementStatusHistoryEntry"},"title":"DisbursementStatusHistory"},"file_name":{"type":"string","example":"disbursement-feb-03-2023.csv"},"created_at":{"type":"string","description":"The creation timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:57.831975Z"},"updated_at":{"type":"string","description":"The last update timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:58.316511Z"}},"title":"DisbursementLite"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"receiver_wallet":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"enabled":{"type":"boolean","example":true},"user_managed":{"type":"boolean","example":false}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"sep24_transaction_id":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invitation_sent_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}},"otp_confirmed_at":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"},"otp_confirmed_with":{"type":"string"}},"title":"ReceiverWalletLite"},"external_payment_id":{"type":"string","description":"Optional external payment identifier provided by the client.","example":"payment-001"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"Payment"}}},"title":"PaymentPagination"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-payments.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-payments.api.mdx
deleted file mode 100644
index ca016ec32..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-payments.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: list-all-payments
-title: "List All Payments"
-description: "Returns all individual payments matching the request criteria. This endpoint supports pagination, and filtering on payment status, type, receiver ID, and timestamp. Each payment has details on the transaction itself, receiver, disbursement, asset, status history, and blockchain information."
-sidebar_label: "List All Payments"
-hide_title: true
-hide_table_of_contents: true
-api: eJztW+tv2zgS/1cIfbjdApajl5/A4eDGTuvWcVLbaTbbDbyUOLK50askldQb+H8/kJJsOXZsN01xd8B9aWOJHP5mOJwXR4+awDOutb9ol3gRQiS4dlvRCHCP0UTQONLa2ghEyiKOcBAgGhF6T0mKA5TkE1CIhTen0QyJOSAGX1PgAnmMCmAUV9FkTjmCiCQxjQTiaZLETHCU4BmNsFyignBEkE8DOSGaoTgqaCMusEh5BYlFAhXEwAN6Dwz1u9kcQUPgAodJFfWwN19Nm2OOCAhMAy6pSVyC4YhjT66HqOAQ+Gt6FUQod1PGQc6uIMw5iEq+OJpTLmK2yFZ0g9i78+aYRohGfsxCxUFVq2hxAkz96BOtrQ0oF50gWAm1oiWY4RAEMCntRy3CIWht7Tf9GgcBCL1PtIpGpbjngAkwraJJUVIGRGv7OODwdFsu1B84qKIhZix+4Ln8eRoIjkSMMOI0mgUguROMuqliHntenEaiii5CKhAVcqQXS6nCPbBF8R4t4hTN8T3IB8AlweofkVbRuDeHEGvtR01uitbWJO1opi2XlRVXCZ5Bwc7XFNhCewp+MgepASt9AVLdxTEXi0ASlJLWKhp8S4KYgNYWLIUdUKI0dJXoCPg4DYTWNsuwvu7HNAbM1krEkbtQigbfBLAIB9P8xZSSkio+qO1DmBAGnFdQzDaUCcmlX4O1HVJWb/ZLeZEAiv0VS6+Ho6JBlIbSbnT7o97pRKto3f747dVo3DvvDSfa7VN1mAY0pGI/3C74NAI0jx9QiKPFSpcfaBAgV+qKNERAEI0KXU/iiL+KfLdVxzLKPGTGYD/+3jfsicwcFmYntyGxr37l+/CK+lDah1HnTG7DqNfp3mgV7bI37PaH7+Rfnatxr6tVtPHV6WlvPNYq2lmnP1CPTjvD057883Yp18RhokBkxErsF/o+pWS/DK6u+l0k5lggBgkDrk4SXp+XfOsIFtjFHF7xZJTxu3W3Xm9gotc9z9KduufrLRcaeq1uEow9aBCnWWbPY4AFkCkWU+wLpQd7eLyIgkWujGtroXjGDFBOCylCSEjvR7CAKjpT7qKNbm5ubvTzc73b/UncW4ZR1w1TN6xneHTBj9kB23Eckxml/yIuecwOWJkzCgFBKQciXZ8c/1Ps48qOaGlCcsGXjuvGw/XWbBpOQhmokOWA3SyGIT9miiMZRhVMvaq1WXMlIZT4weqXeni7XN7KJTPjzCUZyzDkf5uwO0UMCAQFlIsnnsqLIwGRkPNwkgTUU9HVyV9cTn7cxhi7f4EnpZkwGYsJmi29jjMPj43gm9hpY1dK9y/py/5p/2Pt0v4p1U9LGNwfM9Pcnoln2eL5VBoJmCkLtJrbXFY0EQsc7B9m1pdyIBVqvcs138uKJu1taTZmDEs9ogJCflgulOznjRDfsvxaTbetWkt3mpalYwcs3QPDtG2n1Wr4jkSBQxla7tarp9FhNvaJ59xY1TSMqmFIulxAEGA2LQX5092Yt9fpd4s1NlKEzE2NM8IoAvEQs7sq6gvk4UgGI4UBEQx7d2WMz8xFqYzG0Zfi8QC7McMys7j9dS5EwtsnJ8HqWTVnqRqz2RsVVRYTe9/kxqznFANBPX9T3RCR4dp2i5hes0Vs0zGbdbdpOg3Pwr7jtXALSM11ieuRBia4SUy7WbftltGoOy1XytWjzAvgRWI9VVM3ZNrvKvlRmZMFC5RHB+hhDtGG/B6wzCkJ5BLLKG3y1XBwvenWsW779YbuWI6ru03X0KHWsrHZIg2nbj/DQAb9+TjqsnNzcSUDqcmoMxyf9UbbCfH1nHrzgsPOZX8TvfxHzFmczuavxu8KS0nZVwnnzj2RA+OUeTDNMpSjNm59FnaljFugFTs+i8NNsI5nN1p+DXSj5dZ0x2lYOraadd1tOmA5LWzWTCtjRIXUR6nTzjj6FaPfst1UtMcZuBXMaV4G2GFEn3i1COHZjMFsw6+FILC0wSizsBxJ74ZpVJRNskWAZ2UNaYyK0oacXagMXwnCm+NoBhzFnpcylmXPRxrz/y2xh8C5rCbsUvCVjHYxkxVnpHPCAnQ5VNuMHi1bNyzdsCem0XZq7Zr5u7bpP0uA3meb34sEW2gHBqn3zxiZbQmLPEV/kh6us+tSUl0pkm2ZrJWrDC/14Ntw0oh+TQFRApGgPgVWMgjr5UrSTVOVEa4F69VMF5ukptcsYuuOafk6rrU8vQ6+bZFaC7uOMs1ZiHsMJjnyGRilEKT0Qv8rjUC3WnKZVeLKYCZtWmYxc62aCgiTAIsjgXgpF3GIiknrHAIiWZO4p0JRV8W3Yl0uC6CA/swD5z9RvjSiPPpFrEoaVdTPnEL++pfMQqhwQvzCURJzTl3pUGNZa1JD/TgI4gdlQQpE95hR7AbA2+jPx8fqBZvhiP6tUA1xCMvln+hBOS+aVQvLA5AcIVf16SxlMoGNiKIyKkluQKO7LSoBje7QDCLpj2ROuEDj7uVKMDJGUsWavALwK42Qh3meNFKOolisnCPdkEIlYx6nIpaFVg8HwQLhJIGISHyZR4KIPIl6blaly5K7oiopkgmSrGxKr4V2SqiKTgPq3aGdjGc7K58Cq2bqVdIqZdM9cTDE6J13+gNpI99fDHvT4dX5295Iq2SPp51hd3rdGQx6k2mn2x1lprM8cteIkiEtgz7NAMky4H6H+5w9H086o4my2St7fnpxfjnoTZ415N3SQVxb83tg1M9TuKkvM/C9MDqT3vTibPq2P5q81yraTa8zmp5fDNWPy/5Qq2jDzqR/MewMpv1uIcESiM+l5VS+f5QjP9KBpjyrg+1NiWzfrpluC3Qghq87ho91bJuObjqNWsN1LIJd8z+8Jz/VfW4v+ZwPfXakHOTTAKbPuYpnrL8Prm7YuoRY9fi9ygPWBZbjLL0cL23iRhi2zw/uE1Ndt42JYbYtq11rVJu22WrUfpewSkWgo2AFmAuUTXp9ZM2qbdZr5p59HFCh7Ii6H/vxqoHvY/Ac19adumvoDnEdHTueo9c9u2Y0jVqjYdTU5qnK1CH5dCQopMaWF7kad08lEcp5CuxYMtno4lZng+C7t2+7TqN/Vh9cf2xcNs67vc/j0+tRo3t5df3ZHt7Y3cmn3uezgTPsTJzOp/f274PB2aBTO6yGLzpyh5TohUQJBPCDROs50draOGxrdFENUSqFVopUaJ/ajY0wLstmf1z5moZt2CZxdJMYju40Gy3drZOWTrxa3TH9VqvZhPLCP76iYbXAAmJI+1TXHc8x9KbrNHSjaddxs9ZwTGxtHL1RvnRx7F6L9RomqvSjO7Ua1p1G09KxAaCbdaNRb4BBIHNNh83uZ+oyHAnU4ZxytU/zOIRkZ75WnlfUru6z+ThJql4cKncIydQ0pl5A5U0riUNMo/20cEJ1AvfVbVoEIJnK2HS65/bsAKYTThJJXl09RDK0LgvXjeMAcFSmIwvo8lDKGCHEEZ4dmqAK8uVtzxoCik0vqj2FKdrLw7vT3zof7N8+2J8/2h/O3tufzrtnF+OP59bw/Pz3t+ML+3N/Uu9dXX66HnevrQ8N59yyR6PxoLxQCGG8u5xUGvBMiJttoOUcrBgetIV7LVTVMIwjTN9xNNZ521RmIMfTam3T+v5gbtR71x9PeiMVup0NOu/ebUZuhQ3gmVZ8R1Xqh6tBrw75NeJN03gm3ty56mbIuaxosUimKsNl4Y96zE0kT0k/UDHf2b2xBXjzuO9oNjkcsxSdQKtWlfVVxLqOk7D4npIsPZfhYmZiNxPnfJpuGOb/UriyXZDTljselm/E1HvHMLdvJa8inIp5zOjfQF7vFhIYi3dEn9mOM/ySg5p3rCwr2vM1UsXmSnwrGNowFmiDzTWKYh3HMEuUn874mYSzrbG3t+YsZi4lBKKfvy+7uVsDOGKA4oODlzIqFqrn7y1gBqyTStPw5VZekocg5rHsF5yBwoblK+2kdAvOgd0XPYMpC7S2psmJBd2x5DNjpUx97Q0S+hF2XFLkAs+S3KzjsHwlgSNVwvtwPUG/9sZWrf5GXkFmT6fqyusOFtJ25I0KG/SeNDIuK9q4d2kar4QMjXuXumlk2DKe0aOI7yBavvkuRJbzmogs5zUQfZL9HcfBUkPRqqv0OUQlAArSZifJUgVAfhbw5daySMnKmT+6DLCQtlnuvabKeTyD0agaVUPqaRqGWAYiG2ndbhq/jruXb2TlFyMRxwFyUxoIVZqNS+VYVUYP8R0gNw3uSj1IsrN1xuJUVT4YeDSh6oVqYt11a7+zlvLfBfGP6I9oktfDcYTiBCI9u7+Vjluarqz3ivIciqxNxavazxNyldU1oqyHFB0LfpxGpGhMXF8eMEhiTkXMKPC2xKGjL3msXzQX6Bv1tSQXku5i7w4isu5FmFExT90sb/oeCm/aWZf4CsqiUOfsgiEfpriikc8wFyz1RMpyBuW+iEN7Wv0Oznym3MuPsFaQOMTbA7ioGPtibuYQhLo3x0zwvZBL404EAziR+fVJ/mAvP4fYeA9BiBQhhZ9AEsSL4nZ7/1nL2h4+pi6wCATwrM9cAAv5hT8Gdk+9coJe6ow5UYP02Nd5PqyiBdSDiCuvXBjeBHtzQJayU5kPlbTaJycPDw9VrN4qavlUfjLon/aG455uVY3qXISBspNJzEWIoxJh2eSPOkGASm3+G4bmcR2m/P8riqO+osh9noBv4iQJZPFnme/ZYx4dfdFW0dGtrDdxIZ89Pspu4isWLJfycebdZMxEKM+rNrs+oihv0O5PEnYCuoPF+iuHexykoOKyyvcs91O/NtiD+uvLIe/4nGDPQvnnCS9c60e+BTiwZ6tPEV4I7Xva/PdAWX1R8EIY399pvwfMZn//CxG9Zl/8Hqw7mvV/KuAje9yPQ7xqvX8h5P3d6/vULWuMf+lxPNhivmfpchv7ev1b+SNrV1HpcKVIhr7PbP+HPoPbw+7mN30bAs8GdDwPkvJmbFUwNmoD73qy/Iq3ssI7lRXmf0ihFa+iRYn207QzgyD/lYB2Tnl8zHLO5XI1Pnv17IzVN4vZaCmN2+Vy+W+hxdT9
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Payments"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/payments"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Returns all individual payments matching the request criteria. This endpoint supports pagination, and filtering on payment status, type, receiver ID, and timestamp. Each payment has details on the transaction itself, receiver, disbursement, asset, status history, and blockchain information.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./list-all-payments.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./list-all-payments.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./list-all-payments.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-payments.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-payments.mdx
new file mode 100644
index 000000000..86ab4b033
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-payments.mdx
@@ -0,0 +1,5 @@
+---
+title: List All Payments
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /payments"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-receivers.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-receivers.ParamsDetails.json
deleted file mode 100644
index 8f729d2aa..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-receivers.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"X-Wallet-Id","in":"header","required":false,"description":"Optional. Selects the distribution account whose receivers are returned. A receiver is reachable from an account if they were created from it or have been paid from it. Omit it to cover every account you have access to.\n","schema":{"type":"string"}},{"name":"page","in":"query","description":"The page requested.","required":false,"style":"form","explode":true,"schema":{"type":"number","default":1}},{"name":"page_limit","in":"query","description":"Define how many results will be returned in the response.","required":false,"style":"form","explode":true,"schema":{"type":"number","default":20}},{"name":"q","in":"query","description":"A search term used to query through the receiver phone_number, email, and ID.","required":false,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"status","in":"query","description":"Exact match on the status of the receiver wallet.","required":false,"style":"form","explode":true,"schema":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"]},"example":"DRAFT"},{"name":"created_at_after","in":"query","description":"Only return receivers that are created after this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"created_at_before","in":"query","description":"Only return receivers that are created before this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"sort","in":"query","description":"Field used to sort receivers","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"updated_at","enum":["updated_at","created_at"]}},{"name":"direction","in":"query","description":"Direction for sorting receivers.","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"desc","enum":["asc","desc"]}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-receivers.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-receivers.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-receivers.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-receivers.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-receivers.StatusCodes.json
deleted file mode 100644
index 6b3c0ae1c..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-receivers.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"A paginated list of Receiver details","content":{"application/json":{"schema":{"type":"object","properties":{"pagination":{"type":"object","properties":{"next":{"type":"string","example":"?page=3&page_limit=2"},"prev":{"type":"string","example":"?page=1&page_limit=2"},"pages":{"type":"integer","example":8},"total":{"type":"integer","example":16}},"title":"Pagination"},"data":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"f83bb638-dda4-41e6-80c9-d03e6eec2aef"},"phone_number":{"type":"string","example":"+15552368475"},"external_id":{"type":"string","example":"usr12334"},"email":{"type":"string","example":"jdoe@mail.org"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"successful_payments":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"canceled_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"registered_wallets":{"type":"string","example":"1"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"wallets":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"enabled":{"type":"boolean","example":true},"user_managed":{"type":"boolean","example":false}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invited_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"last_message_sent_at":{"type":"string","description":"timestamp when the receiver last received an invitation about this wallet","example":"2023-02-10T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"payments_received":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"canceled_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}}},"title":"ReceiverWallet"}}},"title":"Receiver"}}},"title":"ReceiverPagination"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-receivers.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-receivers.api.mdx
deleted file mode 100644
index 02032c5be..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-receivers.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: list-all-receivers
-title: "List All Receivers"
-description: "Returns all receivers matching the request criteria. This endpoint supports pagination and filtering on receiver status, receiver attributes, and timestamp. Each payment has details on the receiver, high-level payments metrics, and wallets associated with the receiver."
-sidebar_label: "List All Receivers"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWm1v2zgS/isEPxy2OMuW3x0Dizu3dtq0SZvGabNtNzBoaWyxoUiVpJJ6A//3A0nJlhOvnKTuYe+wX+JImhk+M0MOhzO8xZrMFe5/wWcQAL0GqfBlBYegAkkTTQXHfXwGOpVcIcIYkjkZiokOIsrnSEeAJHxLQWkUSKpBUlJF5xFVCHiYCMo1UmmSCKkVSsiccmIEI8JDNKPM0PM5EnwlGylNdKoq6xdEa0mnqQZVsWyaxqA0iZMqGpEgQglZxMA1iohCIWhCmTICHTIno4IiOo88BtfAcnqFYtCSBpnUG8IYaIWIUiKgREOIbqiONsRUcQWLBKRV4SjEfXxMlR4wtrZfBSdEkhi0eeh/ucWcxID7+Dfvwg7gHYW4gqmxbAQkBIkr2NiPSghxf0aYgrseeGf/IayKxsAg0MpiCqlyZrHWDAKRco1uIqGg4CYizZNxIIRVNFjblCokgQQRmTJAMyliRNZS6MyMsEA3IAEFEqwxLBHVSEgUkWtAUwCOEkJXX6roXUy1IdECBcKMAtcgFyuxC5E6VhIEoBTSovo7xxWsgghigvu3WC8SYyujGJ/j5bKyMl9C5pDb7VsKcoHvWuk8AjO/VrMRwuo20yq9YEbgTMgYVzB8T5gIAfe1TGELFJ7GU+ujEGYkZRr363dhTRiNqS4HN4QZ5YAicYNiwhdIgkqZVuiGMoamax8hms9blQiu4Oeo0PCLOnwrhz5ACogMIqRBxihVEBr/WlqkIynS+eYaQUkkOEzcqBUEMaHMrbCj4T7U2TI5XMQoV2P0nQTaha08ODg2JGab+F0g2CPUCgaexibMDs8Gh+e4gs9Gg+En+/vyaHw+OhsNcQUfHg9evhwN8eXSSCZxYodyLAVls/U4IXpCZto6tkTtd5wtstlVCAs6ItrGhnxxW0lIm6gdEg1VdChkTHQfffr06ZN3cuINh3t0XVG/hu93PL/u+Y0/UXIKMyF3rP0HaulE/YXUVELuCByHFFi4WnWGfq3gPmfoKjbgNAkz0xcm7sbLtXPwZXEZhlRCYHGXx8KcDM2EtCqZDGCl1V4X3lotg6GgELFP9uXlcnlphnQRVxkxDd83P3cDYZa+QIgYVdoEjnzfz/MOYx3BNXBt+EmSMBrYZKH2VRkht/exiulXCIxZE2lSC00dhHWqtJuWw3e9Neyspt+/zEb1a/Mf6/3qVzMRcSLh+iGc9fucZO4Gz1gp1zC30WjF21tWsBaasHKyemdpCKm2452u9V5WcEh00VZESmImFNUQq912oWG5brNeczrtNHteGJKW16pDx+v5wYEX+k3oAAQNAjOra2FHK5f4z3q73W40O71Wt+0CgAbJCZvsgpIqWW80my3LZLbMcvKvoYB/G7KqkDbSFNZkKWPDbzQ9v+H5zfO632+1++161ff9zzj31STPjnfIMQwqtYncLH0U14xQBuEDOXyrHOEBPJJHGityyuePY5pTpUFCOMmOA+VMdcdkY0A4IbFJc9XT5ytRCvQksJGtbNgP4+ELM7Kjp0qlu+bly+fPh63u0WHn+OJN97R7Mhx9HL+4OOsOTz9cfGy+/dQcnr8ffTw8br0dnLcG7181Px8fHx4P2lv022ER36/6Pi6u6IFjM6/uG3XPK7rnN/1mPWx59dBvea1e98CbdsIDLwzanVZ9dnDQ60FBJ/njI/qNA2hA6HszmHa8VtDyvd601fX8XrNDeu1uq04aG+bIt4xjqi0UZ5MfB9ImITmAsO212m3itbq9hkd8AK/e8budLvghTO10dZt1maSPdCoJ12igFFXa8EQiBnsCK+WLtE5Uv1a7dvwkSaqBiG2ggGRS9ycBo8D1JBRmaZbLIgn1Qriu3pcVAiQTRvnVpCTf3oGppsLEiLfRlpszcNG4UyEYEF6UY/KMZQWnCuQkJpzMdzHYvKXodnf6z52uNDBG5ISEoQS1I8q8fPHb4HXzt9fNj2+arw9fNd+fDA/fjd+cNN6enHx+Pn7X/Hh03hl9OH1/MR5eNF53WyeN5tnZ+Lg4UAyx2JqiFgkm7usWqn1sL4Uc8skyKL+mj5JxcF8GI0pPYlDKZDTKTMjt0jazv1XRCd1EsFlcQkZi/hSaQoqFmdW5piLV7siRrfRtOOv+HrbjnHSSQ/lf34z/3lcfuK9mBZAfrjzc36WUi1tjN8BqqElElRZy8XSf/Bchr5buttFmtgJgDohEg2dIdy3Qz1u3841RXznrjLiWC7zcRu6ot3/b/rZ4MLIELb9+/5D6gZNUR0LSPyDc32EUpBRbVoI74EjyFHdnp6llBWeheFuJb1msoaxg4LdCow011yjycVp+vSD5LsfPFOxc07zvmkMhpzQMgf98v2zXbg3gAQRWDwVBKqle2EbGcyAS5CDVEe5/uTQ1kxh0JEwXZG63tYSYT7hWLFApkNd5JySVDPcxNpy54LFR1OlSFL8OKgl9A1tq0pnF3Rbr+ijI2NTtMmYLHg9P0euLc/TLaNxod56ZtoV7O0GD0yN0BQtTaMoqVxvy7rRnlhU8Hp3W/T0hQ+PRqVf3HTanM7rV4gr48tmjEDVa+0TUaO0D0XtT8HsYLEuKVr2yP0NUAGAhbZYWlzYlnLnMNouXY5fQoiFV01QqsK3BU0a0ifTG97iCzZR0MLpVv+qbeZrGMTH7me0jlcv4ZTw8fWY6aARpIRiappRpW8wUck54ZiLT30IxuQI0TdnVuumoBSJoLkWamAKihIAm1H6wHTNdGJ2DvhHyqrq11fXXgvg7/53bnq8ZkiORAPeUSGUAKJHCxC5Xjacqg2JaMCLJey93xGVt3giQydlQQLjpkc1EysO8dzMTjIkbVzhOhKJaSAqqb3B46Et2qKllv15YMJKXZEbypiS4Ah5e/pIfEudUR+nUHRAfI+FZ3zW8V1AW+XR2rdqMzGpF+UwSpWUa6FRmChq/6F0+rT5Cs5m0+8uPqJaL2KXbDUxRTvtkbSJgsRdERGpVCrlAV9MSoGaOFbXsRak+u9R4BSxGVpDFH0LCxCK/31C+1lJl6N6kU5AcNCjX1DbdUvVuNgZ5TYNiJSKDaQq3NUvkiZmnMrIKZjQAruy2nAfehAQRoIaNU24PNbL6tdrNzU2V2K9WWsaqasdHL0ZvxyOvUfWrkY6ZjZOJUDomvCDY3F1AA8ZQ8fbCRqS5XScqf98DuXMPJNveNHzXtYSZgtYyc89tlgl9wetM6NIU0ZQ2L29vp0TBB8mWS/Pa7WQmPwqpykpR266BFH2x/a7DVkRXsFhfn7gmLAWbg1UeM9yP3F7YAWp1eeKJ0PZ9O6EE7reno3zK5YMSJKv7Dk+Es9dLASU4t1xV+LmIH9jgfxjk1cWDJ2Le0bov86+7FvDU1bq7v14ydrGJvwZwaR4kNQjs4a+SZ/6Pi1v/7zfZSuy6ef9vw7WOYBAEkBTdfq8wsHHkfjkytTFy76x1Zc9a2T/GO/knvijIvnuYcxDMXwNoK8vtrTvJLZcrevfpTzlW9xsdtbHG5XK5/A+RzYqf
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Receivers"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/receivers"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Returns all receivers matching the request criteria. This endpoint supports pagination and filtering on receiver status, receiver attributes, and timestamp. Each payment has details on the receiver, high-level payments metrics, and wallets associated with the receiver.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./list-all-receivers.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./list-all-receivers.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./list-all-receivers.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-receivers.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-receivers.mdx
new file mode 100644
index 000000000..00b1af51e
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-receivers.mdx
@@ -0,0 +1,5 @@
+---
+title: List All Receivers
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /receivers"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-api-keys.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/list-api-keys.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-api-keys.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-api-keys.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/list-api-keys.StatusCodes.json
deleted file mode 100644
index da11ccb9b..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-api-keys.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"API keys retrieved successfully","content":{"application/json":{"schema":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","description":"Unique identifier for the API key"},"name":{"type":"string","description":"Human-readable name for the API key"},"permissions":{"type":"array","items":{"type":"string"},"description":"List of permissions granted to this API key"},"allowed_ips":{"type":"array","items":{"type":"string"},"description":"List of allowed IP addresses or CIDR ranges"},"distribution_wallet_ids":{"type":"array","items":{"type":"string"},"description":"IDs of the distribution accounts this API key may act on.","title":"DistributionWalletIDs"},"expiry_date":{"type":"string","format":"date-time","description":"Expiration date of the API key"},"created_at":{"type":"string","format":"date-time","description":"When the API key was created"},"created_by":{"type":"string","description":"User who created the API key"},"updated_at":{"type":"string","format":"date-time","description":"When the API key was last updated"},"updated_by":{"type":"string","description":"User who last updated the API key"},"last_used_at":{"type":"string","format":"date-time","description":"When the API key was last used"}},"title":"APIKey"}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-api-keys.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/list-api-keys.api.mdx
deleted file mode 100644
index 8942a61d8..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-api-keys.api.mdx
+++ /dev/null
@@ -1,62 +0,0 @@
----
-id: list-api-keys
-title: "List API Keys"
-description: "Retrieves all API keys created by the current user. The results are ordered by creation date in descending order (most recent first). API key values are not included in the response for security reasons."
-sidebar_label: "List API Keys"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdV21v20YM/ivEfWoAvyXLNkDfsiZbvRadV6fohzQIThJtXS3dqTwqjmf4vw88SY7ivLcpMMxfbOvIhw8p6iG1VqznXkVn6mgyhre48uq8p1L0CZmSjbMqUh+QyeAletB5DmK3wJWHhFAzphCvgDOEpCJCy1B5pAGcZgiEvsrZgyYERylSbRz8jLOQakYwFiQa2tTYeW0GrwrnGQgTwZsZ8rw3aOPCpc4rrEGtYzA2yasUUwHiOmjprEeYOQKPSUWGV0CovbN+oHrKlUgh/jhVkXpnPB9NxiHxnmqdvYrW6mA0kq+btdhmT01RUvBVkqD3syrPV6qnEmcZLYurLsvcJCHY8IsX/7XySYaFll+8KlFFShNp8TOMhe9cd/EXTFj1VElCmU3NyqQdG89k7Fzt3rCP1nytEEyKls3MIIViSHUa+mrTU1YX+DjUm6rQtk+oUx3nCOJ0F1iJVBjvjbP+Cak1sTa7weRmgJtBBw3mpK10GTvgzPhuUJ3nbonphSlfImiDBuMJ6DQl9B49OILX4+MPQNrO0QdnI0BxJd4XS53nyBcm/R4C42Mv8aWiXXDQSeIqy/5G3lDoFeiEwVlpZjacC/Zxx/FTIDU+DnTxqjS0upBH7a6bPXNUaFaREoM+mwJvdcCJIHQe2IZq5z40QnCh+RtDfMrQdkFhqbfy0g0Qr57Q+x4JlpnbytMO2apMfwDZXHuGBrob5VmMuyC7tOXsovI/iLgX1pvrdqoVUW3k01OHo/3bQvjR6oozR+YfTL9B9e5RNyRydOczg1dM+gn66Flz1bWzVREjCUSB3uv5Hc9Bkyde6aLMscNDvXcMN/K8ptEGOhztd6B3PbYl/Ol2CX93FJs0Rfvj63dPetcMGp7twFTR2Vr9hpqQjirOVHR2vjmXNDlzMjbnGGJrOVJDXZr+op6gHukSyQf/inIVKSWOLe5U8qipdtGvtbM00ni7rXvUFLSWoQy1bAlSMm2srA3awvR4An9+OoVXJ9ODn3/ZE+Wur160/S56WQ+9m3gi1RKkhpVGmZ5M9kcvxAymJ5P+/qjmVucMa3YLtJu9ZzE6OHxJRgeHL8Ho7wpp9TRawRRKTbpAvp9Rh0Cg1Ab+Ku5Bo4yduRCu0aopY55rgmPj44o8FrI0TnLNIoly71VPSUvWNH4djAYj6dOqKDStVKRkU30Y49X0eLIHxoMGdi6HuDI5hy3I0VzbpkReVpRCLxDiKl9AqVeCEq5qmJOrShmdhIkpTThwl1jvUW10i7x0tBjcqt1/j+Jn+9meyloiIS24Em3fu4oShJKcSBNwplmOayrOAruyXR524HqgbT3xEpciJNpCLGtmZdPgmMkfWc+kWwhL5w07Mugj4dGHM1/jDZvvftopUr9sitSPdbJAm56/yphLHw2Hc8NZFQ8SVwyfhbAXQUh+S2XVtrMPZBuzkJWxM9KeqUq4oibBdoF+8J4OnpHZjML4+J7UWojHcltiDK3tN2eTYV70k0wT+wcpd+yGTIjDQhs7bC48mM9jabzBvIAAFPinWOZuJe31aCZQebF7W8VIFhn94LOoFCMV/q/ZFOnSJKJLbVoNzYGj+TAY9d2s7xuznspNgtaHqdwKb6mTDOEg6FQ9QwUrGg6Xy+VAh9OA1rj64bvx65P305P+wWA0yLjIg06WznOhbQc4vOlsX/N3RGZ9vYL8z174m7nEeMXDMtfGhgVd6rpuNpgztd1gznsqc57l2noda48fKd9s5HI9gaKz85661GTkdTisRb12KMrKI9t6pI6SBEtZkAL1MBN3Vroby9QfJ6eqp/StMboIY7T5IejtkV11sHfndE2hfm24x2W9rof0ZrO1r4/u9WhSbK2lhuebzeZfneJjRQ==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List API Keys"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/api-keys"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Retrieves all API keys created by the current user. The results are ordered by creation date in descending order (most recent first). API key values are not included in the response for security reasons.
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./list-api-keys.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./list-api-keys.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-api-keys.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/list-api-keys.mdx
new file mode 100644
index 000000000..7e56be9ea
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/list-api-keys.mdx
@@ -0,0 +1,5 @@
+---
+title: List API Keys
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /api-keys"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallet-memberships.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallet-memberships.ParamsDetails.json
deleted file mode 100644
index 9bf3d3e70..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallet-memberships.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"The unique identifier of the distribution account","required":true,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallet-memberships.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallet-memberships.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallet-memberships.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallet-memberships.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallet-memberships.StatusCodes.json
deleted file mode 100644
index 86db27810..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallet-memberships.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Access list retrieved successfully","content":{"application/json":{"schema":{"type":"array","items":{"type":"object","description":"Grants one user one role on one distribution account.","properties":{"id":{"type":"string"},"user_id":{"type":"string"},"wallet_id":{"type":"string"},"role":{"type":"string","enum":["financial_controller","developer","business","initiator","approver"],"description":"The role the user holds on this account. Owner is always tenant-wide and never appears here."},"granted_by":{"type":"string","description":"ID of the Owner who granted the access"},"created_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"}},"title":"WalletMembership"}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallet-memberships.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallet-memberships.api.mdx
deleted file mode 100644
index 038f8d5f4..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallet-memberships.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: list-distribution-wallet-memberships
-title: "List Account Access"
-description: "Lists the users who have access to a distribution account, and the role each holds. Owner only."
-sidebar_label: "List Account Access"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWFFv2zYQ/isEnxJAtpws2wC9ZUvaZe3arE7RhzQIKOlssaZI9Xiy6xn678NRkmPHTrJ03TAsD7FM8o7fd3fid/RKkpp6mVzLM+0JdVqTdlZ8UMYAeXkTyRx8hrriYZnI19qTF1SAqD2gF4vCiULNQagsA+8FOaFEvulKZZmrLUVC2TwYojMgQGWFKJzJ/VC8XVhA4axZDmUkXQWo2PIi7/bbRNYC+w3KFNAXuvIykpVCVQIBMo+VtKoEmUidy0hqxlwpKuR9IldMwerPNQidgyU90QxiEiDuIyAjifC51gi5TAhriKTPCiiVTFaSlhXvyVZ2Kpvmhhf7ylkPnuePRyP+2IZw2obMaE8CgVDDHHLh6zA8qY1ZykhmzhJYYmtVVUZnITbxJ88uVrsQFKJiO01Q+o1xl36CjHbC8BKVJS+cbRMaHkKCnA3P+yLBWaqQ80S6pafzPUGIJHu8fWBuERL50CxD2J2IJNi65GKdaKtsppW55figMwYwcJuDYWAykmnttQXvQxVo0oocD6uqQjcH3C3tq742++pu65MjQYX2a/ZdvfKIWailFwRWWRosdA6hyC3MAYWqKlDoRQEIQ+Y05VBDfpsu9zHbxnJx1pdiuxm/Zp19GG3fNvaaISj2qmif14nDkmdkrggGpEsIeanyZ9o0kSRNnBN5/w2UDf9F8mR0tFvi762qqXCo/4D8K4p5XbTb5QaIDvfWDXwhVHvLftuDJ0X15jpbMx92UYL3arqn+jqe8EWVVVudHQ75xpHY4nkHo9/oZHS04fq+xTqE3+2G8IXDVOc52H8+fg/Qu0PQwzzZhcmMXrja/s/TPOko7svwyWaG34F3NWYg7Nqq6Vx7yGrUtAxq9RMoBDytqZDJ9Q0LRwlUONa+KQRGrF6JjDdP4kF7evp4pfMmLrfU0APOeyms0chESvbabzrm4LfR2dz6Tj8q/QqWOwfSaVesIZOiAJUDCs6z0lbbqVBWjM8uxa8frsTB+fj4+x8OhcNu9FacXl6IGQR579R5y18v1K1bzs74/PJo9I2QifH55eBo1GJrOYsVuRnY5vBZiI5PviWi45Nvgej3GnD512CFpWLdLD2EaANAgNRv/JnNgxJoO3Fhu04RxgTGKBRn2qc1eijBkrg0ilhJOPcyklySLYwfh6PhiOu0LkuFy054H/dxMD67PAyKK8g5I9JaG36rUDicKtuFKHSfpZqBSGszE5VaspeuJ52iqysWVYRMVzpMcB8Q5LTf3QItHM6Ge7vF/xbEj/ajveK2hLe0wlVgB92JU6Hj01BQoYinWyjcxriqbyvuubvrzjOXg8iUFSm0x1bb//AXY9yCqwWhcl6TQw0+YRwDce1bf3H3Ocg3gjSouiANUpXNwOY3BwVR5ZM4nmoq6nSYuTJ+lofDRATyayjLvpzby0m3LLDSdoLKE9YZ1dgR5LzQUzkdPoPZBIPm/R1qvYunuC0gFf3ar2ZTgCkHWaGQ/KOQN9bFhABxqbSNu4FH+TxF4xcwpQiOAv4cKuOWXF5PMhHc2U/FqzoFtEDghx/5lCLA0r+djAHnOuNzqafVwRw6nMZh0cBNBr5bFkmjM7A+KH1/8FYqK0Ach3Oq1VD2lcTxYrEYqjAbvHWmPn598fP5m/H54Hg4GhZUmnBOVs5TqeyGY77NitP2HiHa69/9o2Z11z39C5ftTjEIvlBcGaVtuB4w41XXeFzLfY2HjGQSLtibvcdNJAvniW1Wq1R5eI+maXi41Y7k+iaSc4Vapawb1yt2zc+5TCbKeHgkFAfvurv3ofiam/tenr1cWtbKuTI1f5ORnMGy/f2guWmiXnAZbjvBeatow2Snx93q4l6eX/G1c0eiZ0Giuwf2vhfO/R6ghcD/m+gBk9WqbQCaZr2+nXrQoqO4Zs4Mmqb5E/sNXlg=
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List Account Access"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/distribution-wallets/{id}/memberships"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Lists the users who have access to a distribution account, and the role each holds. Owner only.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./list-distribution-wallet-memberships.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./list-distribution-wallet-memberships.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./list-distribution-wallet-memberships.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallet-memberships.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallet-memberships.mdx
new file mode 100644
index 000000000..11fe2ab71
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallet-memberships.mdx
@@ -0,0 +1,5 @@
+---
+title: List Account Access
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /distribution-wallets/{id}/memberships"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallets.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallets.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallets.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallets.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallets.StatusCodes.json
deleted file mode 100644
index e65b9aa5c..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallets.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Distribution accounts retrieved successfully","content":{"application/json":{"schema":{"type":"array","items":{"type":"object","description":"A distribution account the tenant sends funds from.","properties":{"id":{"type":"string","description":"Unique identifier for the account"},"name":{"type":"string","description":"Human-readable name for the account"},"description":{"type":"string","description":"Optional description"},"distribution_account_address":{"type":"string","description":"The account's Stellar address. Absent until the account has been provisioned on the network."},"distribution_account_type":{"type":"string","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"],"description":"How the account's secret is stored. Additional accounts are always `DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT`."},"distribution_account_status":{"type":"string","enum":["ACTIVE","PENDING_USER_ACTIVATION"],"description":"Status of the underlying Stellar account"},"status":{"type":"string","enum":["ACTIVE","PENDING","ARCHIVED"],"description":"Lifecycle status. `PENDING` accounts have been reserved but not yet funded on the network and cannot send. `ARCHIVED` accounts accept no new disbursements and are never deleted.\n"},"is_default":{"type":"boolean","description":"Whether this is the tenant's default account. Exactly one account is the default, and it cannot be archived."},"created_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"archived_at":{"type":"string","format":"date-time","description":"When the account was archived, if it has been"}},"title":"DistributionWallet"}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallets.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallets.api.mdx
deleted file mode 100644
index 0955eeecd..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallets.api.mdx
+++ /dev/null
@@ -1,62 +0,0 @@
----
-id: list-distribution-wallets
-title: "List Distribution Accounts"
-description: "Lists the distribution accounts the caller has access to. Owners see every account in the tenant. Archived accounts are included so historical records stay resolvable."
-sidebar_label: "List Distribution Accounts"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVWN9v2zgS/lcGfGkLyLKb6+0BfnMT39a3QZKNnfYhDRxKGlvcUKSWP+JqDf/vh6GkWI6dpNnrAbt5cAyS8803Q3Lmo9fM8aVlw2t2IqwzIvFOaAVfuJToLLuJWIY2NaKkYTZkp8I6Cy5HyLrreZpqr5qZlIwN5NzSOFoLTsdwvlJoLFhEwHs0VWsDQgUrh4orF8PIpLm4x2yLyQ2CUKn0GWZgNeTCOm1EyiUYTLXJLFjHKzBotbznicSYRUyXaDiRm2QN726EbYARM2hLrSxaNlyzo8GA/u3GfHIwUoPOCCSi1ocoF17KikUs1cqhcoTDy1KKNLDo/2YJbM1smmPB6ZurSmRDxo3hZCccFrYzrpPfMHXs8Q6MDma+k0KwqDILCx8+jS4oG6WhfDhRhymyjh8CU8s9P1dK/O4RRIbKiYVAAwttgpvGJdtETPECX4b65AuuegZ5RpsDZHQIbMfoJczz8IVL6A4TSCc58wZ8zrPMoLUvo862jN5YmDqUkhtozGMYJRaVA6+ckF324awniApKo++FFVphBro+2ArdSpu7+El2NaV9aqh8EW7mZDq7nHy8mk3Oz+aj4+Pzq7NZPJ2NT09Hl/H47DOLnl9y8nH+eXR1Ontq3fHk8vh0vF22d+k/6VU32jd0i1ODDgTdPG0wi2GUZaLZkZ2Ly+WKVxZuv4vh7dNJso47f3AH2zSNjmeTz2MWsYvx2cnk7Of51XR8OQ+jI/K6H9c0YIJehOi8ytDISqjlduO3h/P1/lnERpfHnyafxyeH6ugC0yqVCDVwDLeN2e02fzm/x/pYGbRoqNYk3oHSDip04YbvHTPgKoOUK1pEhSCG25ZFB5nqcklIoHBFBSXxxmKBYU5lYecUlWnIUKLDLP4abpew8wwX3EvXyUSitUSu9i7TlxxdjnTNhaWjsi1Rbyw0MC2lGMbfeOpkBVptr1Vj1KyNAjXh2vASBN40i3BuUoPcYTbn7tA2LbQpaIZl3GHPiQLJxpfZq21ap99vdCAzaqd+rKhXNrARiAVF2dYUttlEzAkn8VEvqnsY29BfxD4M3u+3rivFvcu1EX9g9ida00ML2m0faIw2+6FvIobfnOEHm9guwt5tUr5I0BBEgdby5YGC2MSJ33hRSuzwYGfawU6cWxqtow+D9x3oxxYPKfzHfgr/rU0isgzV/z9/T4S3ZdDwtJh6I1zFhtdr9hG5QTPyLmfD65vNDYXpck2iZ4nBN6cp1u+W1d7qQf+EwmJswPJGsiFjBNL6mFJMNe2up616KcUvWO2rlCa5IUGQI8/QAKWPC0UVliuYnlzAf77M4O14evTPn96BNs3oHEYXE7jDioRLrTB28UgskZMalg7NdHzxfvCDmMF0fNF7P6i51THD2uk7VJt3r2J09OFHMjr68CMY/erRVN9HKyyFkhteoHuaUYdAoNQ6/p3MQ+0SaqGDu6aGtd31pNN24EJyR5WT9p5FjI5kTeNf8SAe0Dn1RcFN1Yi05zHeTk8u3lH34OC0lpB4IV2QnNosuWpSRO8SKPgdQuLlHZS8qhug08BhabQvSRoYTEUpwoS+x1q0tt4fpN0hHfnXovhVfVWzphFzBbpE1bPamxRJs1KZApfz0HJrKiQrdNmKo0dwdSsOjz2d0YtPUTdeaK8e9MhCS6lXdFoMltoKerKhHRKPHlzbGq/f/O91JUivbJLUS3h6hyq7eZs7V9phv78ULvdJnOqi/yqEd0MIwT9QqdrjXCuMZlktMNTCcOuMT503TYDta+XZPY1fEdnChFbyv4TWQrwU2woTaNf+6WhylEUvzblx9lnKnXV9ZxD7BReq3ww8G89LYXxCWUAACvwzLKUOYv3FSMBbWveLT9AodGhJzEbMoSns+WKK5l6kVJfasBqasTbLfljU04uebZZFTIoUlQ0dui28JU9zhKNQp+oeSljDfn+1WsU8zAa0xtT2TyfH47PpuHcUD+LcFTLUyVJbV3DVAaZfLWDn54dRo+AfV5z1Vpv8jX6jaRqQw2+uX0ouwhsjJHDdyJZrdlC23EQs19bR/HqdcItXRm42NFy3neH1TcTuuRHkKeiiqO2EpHPukPrIKDyCqNlw6etG+EjT7aipn8f0guZ7vfMu9M7mC6G3U6rqYD9uzjUF+txET5is13Vn3mwe1tdTT1o0IbarKZ83m83mv/MH/no=
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List Distribution Accounts"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/distribution-wallets"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Lists the distribution accounts the caller has access to. Owners see every account in the tenant. Archived accounts are included so historical records stay resolvable.
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./list-distribution-wallets.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./list-distribution-wallets.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallets.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallets.mdx
new file mode 100644
index 000000000..5ac7b7b85
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallets.mdx
@@ -0,0 +1,5 @@
+---
+title: List Distribution Accounts
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /distribution-wallets"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-receiver-verification-types.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/list-receiver-verification-types.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-receiver-verification-types.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-receiver-verification-types.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/list-receiver-verification-types.StatusCodes.json
deleted file mode 100644
index 4d49e771d..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-receiver-verification-types.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"A list of verification types","content":{"application/json":{"schema":{"type":"array","items":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-receiver-verification-types.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/list-receiver-verification-types.api.mdx
deleted file mode 100644
index aed9f0ad1..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-receiver-verification-types.api.mdx
+++ /dev/null
@@ -1,62 +0,0 @@
----
-id: list-receiver-verification-types
-title: "List Verification Types"
-description: "Returns the supported receiver verification types."
-sidebar_label: "List Verification Types"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNVlFv2zYQ/isEnxpAtpws2wC9uYu7em0dL3Y3DK4RUNLZYi2R2vGUxDP034ejpERJmmbtOmB+sGXy7rvvO5F3d5Cktk5GK3kBCegrQCfXgUzBJahL0tbISF4AVWicoAyEq8rSIkEqsHUQV4B6oxPF1oL2JbihDKQtAf3SNJWRfKsddRF+69kv2VwGEsGV1jhwMjrIk9GIf+6TGItcOxJ284l4MpCJNQSG2E+VZd5uhx8dOx+kSzIoFD+xg4ykQlR7GUhNULjeuiPUZisDCaYqOC9n4+Xk8vzV5cvpxfK1DOQfk/HF5bvzmf8zn85kIGfj5fR8Nn57OT27nL1/93JywTkkTTkj9uW+0pCnsuZPIE9Hx49lvjeqosyi/gvSr5Bl44+QkAxkifwCSDcZBUSLj1XWgYQbQuWeR3CkqOrbmaqIARmiAOfUFj4B3+iEG1WUOfR4yJklcU/nHY0u0OnouAf90OM2hd89TuEri7FOUzD/ff6ekHfHoOXpIKlQ015Gq4N8CQoBxxVlMlqt6zXLpMzyNdmCj614S4bdDXNh/8gPuiPvAP19ZcwKcxlJyWBdrAVra+j3I97dgFK/Ab4CD+5Zm+TmemWgUkDBaVTaaLMVyojF2Vz88vtSvJgsTr7/4UhYbFcvxXg+FTvYcwEwqoCHeHzhOEgDy4dnMZkfj74RM7GYzAfHo4Zbo1kcyO7A1EdfxOjk9FsyOjn9Fox+rQD3/4yWNxWlQlUAPc2oR8BT6gL/ye6Sj602G+vDtaVsQZDnCsWZdnGFDgowJOa5oo3Fgt+9DCQfyYbGj8PRcMTntCoKhXsZyWUG4vMYLxZn8yOhnVCCrM1FXOmcxMaisLhVpk2RE2RFoXYg4irfiVLtGcWvKrFFW5XcJxASXWq/YblPUS+6Abq2uBs+yt3/j+IH88EsM+18SCNsCWbgbIUJiBItlytBmSLebqhwV7Qe/hNwgVAm9RuJTUEkyogYxMZWJvWOGf/Jc3vNpwWhtE6TRQ0uYh4DsXINXtj+DtJekgZlm6RBrJIdmHT9IiMqXRSGW01ZFQ8TW4RfhHAUCS/+lsq+O87NPNKaeVXabFA5wiqhCluB/F7ouXc6/AJlG/Qt5d9I6yCe03YNsehsv1pNBnkxSDKF5D5LuWcXEgKEhdImbBc+q+c5Ga8hL4QH8vxTKHO75+P1rBJRObZ7U8WABgjc8ANXKQIs3PlmAXilE65LnayW5tDiNvRGA7sZuNYskLlOwDjfqbvCW6okA3Hi61TTQxkrCsPr6+uh8rserXV14dvpT5PZYjI4GY6GGRW5r5OldVQo0wPmeVf0Jz/RTbr3ys3hbkD5uim7bQQENxSWudKG+4UXcmjHiJW8HSOa6vxwkFgHMrOO2PJwiJWD95jXNS83jSBarQN5pVCrmJvAal0HXW/iyWMHXNnHSQIlzy5XKq+a1vRg2ro35/w8WcpAqkfdbOe7WfvA6N2W2fewH7bLhgJ/18ETLodD0yvr+ta+2XrSo5XYWXNm13Vd/w01I6KZ
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List Verification Types"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/receivers/verification-types"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Returns the supported receiver verification types.
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./list-receiver-verification-types.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./list-receiver-verification-types.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-receiver-verification-types.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/list-receiver-verification-types.mdx
new file mode 100644
index 000000000..32f373572
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/list-receiver-verification-types.mdx
@@ -0,0 +1,5 @@
+---
+title: List Verification Types
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /receivers/verification-types"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-registration-contact-types.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/list-registration-contact-types.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-registration-contact-types.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-registration-contact-types.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/list-registration-contact-types.StatusCodes.json
deleted file mode 100644
index 94d8d921d..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-registration-contact-types.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"A list of registration contact types","content":{"application/json":{"schema":{"type":"array","items":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-registration-contact-types.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/list-registration-contact-types.api.mdx
deleted file mode 100644
index 000a50692..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-registration-contact-types.api.mdx
+++ /dev/null
@@ -1,62 +0,0 @@
----
-id: list-registration-contact-types
-title: "List Registration Contact Types"
-description: "Returns the supported registration contact types for disbursement instructions."
-sidebar_label: "List Registration Contact Types"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNVm1v2zYQ/ivEfWoA2XKybAP0zW28NWuaenGKfnCMgJLPFmuJ5I6npJ6h/z6QkhLlfe1aYP5gy+Tdw+c58V52wHLtIJnDkXJpRQ5L1OxgEcESXUbKsjIaEjhDrkg7wTkKV1lriHEpCNfKMUlvJDKjWWYseGvRiZUhsexhCqUdU5V5UzeECIzFxvF4CQmcKMdnPbQ3Ddi5x4IICJ012qGDZAcHo5H/uUtwLArlWJjVM6QgAv8fNXt/aW2hsmAWf3YeZAcuy7GU/sk7QAKSSG4hAsVYut66Y1J6DRGgrkofv8n78fEJRDB9++F0cnn68f3ryRlEzfLl+PTo8tP45GRyfjk+OjqbzGb3LB+zWETAigsM0X80MlD7TwSHo/2HAfmoZcW5IfU3Lr9BuEk/Y8YQgSX/plg1sUciQw/jUEeAX5ikexnBseSqb6erMkXyECU6J9f4CHyjE7/I0hbY4wGnhsUdnbc0uoMOR/s96PseNyH86WEIfzOUquUS9Y+P3xPybhm0PB1mFSneQjLfwWuUhDSuOIdkvqgXXibnxufTGsPZ0m9B3E+JQZsSgy4lHNIVkguIFRWQAHio7qSZV9aQ7593myFWvUOfIvfysQ1xk4Y5yiVSk41KK70WUovZ0VT88elcvJrMDn7+ZU8YalcvxXh6LDa49XVCyxLv4/mE9Ic0sP7qzCbT/dF3YiZmk+lgf9RwazSLHZsN6nrvqxgdHH5PRgeH34PRnxXS9t/RCqbCSpIl8tOMegQCpe7gv7w7+Eur9MqE49pyNmMsCkmi33PEtJC8MlT6dw8R+CvZ0Ph1OBqO/D2tylLSFhI4z1E8j/FqdjTdE8oJKdiYQqSVKjj0JENrqdsQOcFGlHKDIq2KjbByG7qfX5ViTaayTT/JlFVhw1whhRbYna6Rrw1thg9i9/+jeKEv9HmuXDhSC2NRD5ypKENhyfhiJTiX7LcbKkYLNgH+EbhISL0MG5lZosikFimKlan0Mjjm/k9RmGt/WwitcYoNKXSJ5zEQc9fgxe3voD8rDGwbpEEqsw3q5eJVzmxdEsdrxXmVDjNTxl+FsJeIIP6Gyra7zs1M05oFVUqvSDbDSkWtQP9e+KV3OvwKZSsKDeW/SOsgXtJ2janobL9ZTY5FOchySeyepdyzi5kQ41IqHbcLz+p5ScZbLEoRgJrhEm1htv56vahEVM7bvatSJI2MbnjhqxQjle7DaoZ0pTJflzpZLc2hoXUcjAZmNXCtWQSFylC70Ke7wmtllqM4CHWq6aEeK4nj6+vroQy7Aa11dfHJ8ZvJ6WwyOBiOhjmXRaiT1jgupe4B+7FY9Kc/0Y5/opuM75Sd3e2Y8gMm9rZbMH7h2BZSad9UgtpdO2nM4ZlJYxFBbhx7q90ulQ4/UlHXfrnpFMl8EcGVJCVT3yXmizrqmpcfTTboS/84y9D60eZKFlXTu+4NY3fGoN8n5xCBfNDuNqHdtQ8evdvS2x72/X7aUPDfdfSEy27XNNO6vrFvtp70aCV21j6qi7qu/wH10sqG
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List Registration Contact Types"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/registration-contact-types"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Returns the supported registration contact types for disbursement instructions.
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./list-registration-contact-types.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./list-registration-contact-types.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-registration-contact-types.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/list-registration-contact-types.mdx
new file mode 100644
index 000000000..1f178016b
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/list-registration-contact-types.mdx
@@ -0,0 +1,5 @@
+---
+title: List Registration Contact Types
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /registration-contact-types"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/log-in.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/log-in.RequestSchema.json
deleted file mode 100644
index 4b42b51b0..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/log-in.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"*/*":{"schema":{"required":["email","password"],"type":"object","properties":{"email":{"type":"string"},"password":{"type":"string"},"recaptcha_token":{"type":"string","description":"Token for reCAPTCHA validation. ReCAPTCHA token is required unless the `DISABLE_RECAPTCHA` configuration is set to true."}},"example":{"email":"johndoe@mail.com","password":"mysecret"}}}},"required":false}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/log-in.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/log-in.StatusCodes.json
deleted file mode 100644
index c558bbe87..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/log-in.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"type":"object","properties":{"token":{"type":"string"}},"example":{"token":"eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VyIjp7ImlkIjoidXNlci1pZCIsImVtYWlsIjoiZW1haWxAZW1haWwuY29tIiwicm9sZXMiOlt7Im5hbWUiOiJTdXBlcnZpc29yIn1dfSwiZXhwIjoxNjc1OTYyOTQ3fQ.4Zj9yBXch-iuFYF-kc_EhHPxjpwp_egMOLbOv4bZKO1MFvcmEgZ5MlXH1_1fZfgUxaNBcMCdRM6MGSqKocwGnA"}},"example":{"token":"eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VyIjp7ImlkIjoidXNlci1pZCIsImVtYWlsIjoiZW1haWxAZW1haWwuY29tIiwicm9sZXMiOlt7Im5hbWUiOiJTdXBlcnZpc29yIn1dfSwiZXhwIjoxNjc1OTYyOTQ3fQ.4Zj9yBXch-iuFYF-kc_EhHPxjpwp_egMOLbOv4bZKO1MFvcmEgZ5MlXH1_1fZfgUxaNBcMCdRM6MGSqKocwGnA"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Invalid credentials","extras":{"status":400,"message":"Invalid username or password"}}},"example":{"error":"Invalid credentials","extras":{"status":400,"message":"Invalid username or password"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/log-in.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/log-in.api.mdx
deleted file mode 100644
index 86288d0e7..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/log-in.api.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-id: log-in
-title: "Log In"
-description: "Allows credentialed SDP users to log in to the SDP dashboard with a password. Note: all passwords must be at least 8 characters long and a combination of uppercase letters, lowercase letters, numbers, and symbols."
-sidebar_label: "Log In"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWNty2zYQ/RUMnpKO7nWSmk+VHSWhb1IsJXbkeFwQXImQQIABQNOsRv/eWZBy5MSxmzbT6XT6RAjY+y52D7Sijs0tDS5oP3cJKCc4c0IretmgMVhuROZ/BrQvpS4s4QZiJGMSYjJ+OSK5BWOJ00TqOREKVy4BfxQzm0SamZgUwiWEkYxZW2gTt8iJdhAQJuXtniVpbh2JgDBHJDDryC+EJ8ww7lCD1GpOmIoJI1ynkVDeTqJnJM8yMJxZIBIc0jaI1MWXWypPI79AGbZMIy1tizaozsB4UWFMA3qk56GiDWrgUw7W7em4pMGKcq0cKIfLn9o/4cfyBFKGKyQVBmIMIqRMSNqgG6cwjK7MgAZURwvgDs8MqnQCLHJXHMFqQ2adEWpO11sy7js0wFnmeMKunF6C+prmy/RNkIzMtCEG9vujyf6bPrlmUsTe9xY5vd31AomwZOMYyZUEa31af3sZjvt7R4Or00FN/xvhWs3EPK+iiIwWnC8Dk0OLrtcNCjcszSRs+UsXOlGxhl/xZ4vrdDtoAU1LC9yAo+v1et3YCvGMSQt+x2Za2SqGvU4HP3cdHh7SxnbeWJbJurjbC6vV3SQ+nKRvxPgL12oqCuVBEr3mYigOXr37PeyeiNCG6vQZ3w+fh8vs/P3+wW4LyoMu770vw0X2IkzlMlxoEZ+fSC662XQ/tGH63n04kxb3p2fdhJ3d9KtvkX/o7bpQFIKnu3Z6fiyG0r0I02dJdPYOlU7i8z3J1TTjvd0yVN14Ni7E9DwpwoW+OVnw7nDyoRxO3v48e9vamS52y71znjRF/urDq+aSXw2SN6ObRVZkVzA/Hh5Fw+udaHo47B6/uubpYD59dizP33SvurPpbP7uhp3s8eP9+PT4+fHr8adDzYvXqv9/ZB6IDMZm576K3WMxOa36zo8rXTBGm3tbCNw4w+zjEqxjLt+mqzopikjBWjaH+27Gl9e+MoOGyjedrTFi6bYpG2U7nc6W+Fs2HDaKpUC0uR0c9B/W5dXdNLmOYQ6qWU+KZqTjson0NKC4rlSBskIrHLAruoSSBg9yNug1k/mthPUl2uUSjS0x074sMuYSGtC21HOBg8qCuQZTKcgNdlbPZoHnRrhyjGVS5XEPmAGDY34rXywTh1B+NS2QShvxe9XSE2AxGOzzjgkl/Bz2A/7gbEKeDMa9Z8+fYpSq3SvSH4VkCSVO1zogd+TRBhWopBKLdTQejLqdH2QZGQ9GzW6nsq3ymax8A1o//S6Lejs/0qLezo+w6G0OpvxzZnlSkjHDUnDftmjLgKpL14o/Ibvv40LNtFcnHN4vOnYgJTPkpbBRbiykoBwZSeZm2qSYeyxjMLYy40Wr0+pgneZpygxegAmiwwdlPBm/HD1FIMGI01qSKBfSeeyizZypOkQedKZsCSTK5ZJkrEQpfpeRudF5huDQABeZ8Af6GkyFTWvtClyhzbL1NVj615n4UX1Uk0RYr1IRnYFqWp0bDiQzGvs2cQlzeFyZohGJe/H3iKtAMB5gLyKcKcTdM52r2DMm+APxPlaLgUxb4bQRYAO0o0kubCWvXX+b8VaQmlkdpGbE+BJUfPkkcS6zQbs9Fy7JI4R77e+S8DQg3vlbU8pNOVeotCbzXgk1M8w6k3OXm9pBzIt7LKet7/BsZvx0/juubUQ85lsBEdnQ/mVvEpBpEx9Tzj5o8hZd2xmAdsqEatcbD/rzmBtvQKb+OVfdkhgyqUssr0c9IblFusM8AqPAgW19xC7lwKR2OBuDuRYc+9LGrdrMljbztidq6lnT1mQNKgUHZT1Q2DTejPEESM/3qWqGoqyg3S6KosX8qZdWs9r2Ubg/OBkPmr1Wp5W4VPo+iQM6ZWpL8JGeE/+avNNdtl6T/9lHdT2aHNy4diaZUDjBfGhXNYK5oBWCuWzQBJFNcEFXq4hZeGfkeo3b1QQKLi4RFRnBIpw+F5frxmYofsZU+1VAmxNU+xlE4VN93dgQ9TmHzG0dfwWr7+Ct0XA8oY0KiAUrmuoYeQwr8N8BVnigtV7/AYliDNw=
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Log In"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/login"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Allows credentialed SDP users to log in to the SDP dashboard with a password. Note: all passwords must be at least 8 characters long and a combination of uppercase letters, lowercase letters, numbers, and symbols.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./log-in.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./log-in.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/log-in.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/log-in.mdx
new file mode 100644
index 000000000..b2bf8aceb
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/log-in.mdx
@@ -0,0 +1,5 @@
+---
+title: Log In
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml POST /login"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/organization.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/organization.mdx
new file mode 100644
index 000000000..b96da4bc5
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/organization.mdx
@@ -0,0 +1,5 @@
+---
+title: Organization
+---
+
+Organization endpoints manage the process of getting and updating organizational profile information. The organization's profile has basic information set at the time of SDP deployment. It can be modified by the Owner. Organizations can also manage their preferences, like which assets to use, through these endpoints.
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/organization.tag.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/organization.tag.mdx
deleted file mode 100644
index 9ce214826..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/organization.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: organization
-title: "Organization"
-description: "Organization"
-custom_edit_url: null
----
-
-
-
-Organization endpoints manage the process of getting and updating organizational profile information. The organization's profile has basic information set at the time of SDP deployment. It can be modified by the Owner. Organizations can also manage their preferences, like which assets to use, through these endpoints.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/patch-organization-circle.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/patch-organization-circle.RequestSchema.json
deleted file mode 100644
index e463486b2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/patch-organization-circle.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"description":"Circle configuration to be updated","content":{"application/json":{"schema":{"type":"object","properties":{"api_key":{"type":"string","description":"The Circle API key with permissions to POST & GET transfers"},"wallet_id":{"type":"string","description":"The ID of the Circle walet from where the funds will be sent"}}}}},"required":true}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/patch-organization-circle.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/patch-organization-circle.StatusCodes.json
deleted file mode 100644
index 30f626650..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/patch-organization-circle.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Circle configuration updated successfully","content":{"application/json":{"schema":{"type":"object","properties":{"message":{"type":"string","example":"Circle configuration updated"}}}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/patch-organization-circle.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/patch-organization-circle.api.mdx
deleted file mode 100644
index b19760336..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/patch-organization-circle.api.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-id: patch-organization-circle
-title: "Circle Account Setup"
-description: "Updates the Circle configuration for the organization. Only account owners have permission to do this. Note: in the first time configuration, all fields are mandatory, but after it is been configured at least once, you can replace a single field at a time."
-sidebar_label: "Circle Account Setup"
-hide_title: true
-hide_table_of_contents: true
-api: eJztV8Fu3DYQ/ZUBD0UMSCvHSFtAN8c2GjdFvc066MFZBJQ0WjFLkQo58kZd6N+LoSRbcRw7aX3ooT7YMjUzfG+GnHnaC5IbL9IrceE20qi/JClrxDoSBfrcqSb8m4q3TSEJPVCFcKJcrhFya0q1aV3wgNK68NLOwizgwugOZJ7b1hDYnUHnoZLXCA26WnnPnmShsECV8gv43RKmoEwIVSrnCUjVd/aKQGoNpUJdeJAOoZamkGRdF0HWEsiS0IEiUB4yRHPjjQVIAo3SE1iTYwSdbSGXBhw2WuYIErwyG41DdLaWAcBCRMI2OOx/XohULCXl1TxnQ1ZEJBx+bNHTS1t0It3fyeO9uSMLGUIbUlyISOTWEBpib9k0WuXBLPngOcRe+LzCWvITdQ2KVNjsA+YkItE4BkkK/eCr3m+xmxl6cspsxN3iXt4W9Xh5DlvsYKeomhXJM8blxeoSfoBfzi6BnDS+ROdFH4md1BrpvSq+bafzU7Dl/CDtpEaC0tkadhU6HIrfmsLDTmnNufGcjp5/hvwqh4VIybUYFnxjjR9IHx0efmPWx3yDb/McvS9brbunS36N3ssN3pcS/CTrRuMjuAa6fSRe3MfopSzgzXDQng4zOmfd40U8RZJKe5CZbSkUa3DsmRo56R/dqe8nch7z1inqRHq1Fy9ROnTHLVUivVr360h8inNb4AZNPN6qOLNFFxtZc3B+DvkkNOGUhijhyD/oGYlrqdubCLxRjVRZvtcN32vGKxmFSOb9LMlDveKhXoLRu2u+BLxt67RIRQg2kVpx3ofUzqndJEc26jV2X+SXrawb94QKZYGOzwhJZZTZgDSwOl3Cr39ewrOz1dGPPx2AdePq++kGc8ca0/RZPBEJxZsMYblmq7Pl88MnQgars2X8/HDANnCGPdktmv7guxAdvXhKREcvngLRHy267ttgBVNopJM10tcRzQAESNPGH9ld8P3gK/zmdqCcTa1j1t1vr+msEU+LPUcsbUCsKDSdFaHW0sGp8lnrPNZoCJZaUmldzceH7wc6PzD5eXG4OOSj3ta1dN3Ywx+O8Wx1ujzg6SuBrNWQtUpTUAjz2xRmSi23CFmrt9DIjqOEVQkbZ9uG54TDXDUqvLDXOGiMaXeDtLNuu7h3zPy3IL4z78xlpXzY0oBt0MTeti5HaJzlHglUyUGyBChBFjTTpLwTLgJpivCCm1xQMBlCaVtTBEeen1Zru+MD57CxXpF1Cn3KOGK48kO8ZPwbF7Mkxc2YpDiT+RZNsX5WETU+TZKNoqrNFrmtk++KcJBCIH8DpZtuxKAoR7PASpnSSU+uzal1I8FJXD5Y08V3MCtdmJj/htoU4jFuO8xgsv3HbCrUdZxX0pF/EPLMLiGHmNRSmWRceJDPYzReoa4hBAr4C2y07fh4PcoEWtbU8LrN0Bkk9It33OgIXe0vyhW6a5VzX5pojTAX1m2SYBTbMvajWSS0ytH40AKn3t3IvEI4Cn1qGMMcK02S3W63kOFtiDa6+uS385Oz31dn8dHicFFRrUOrbaynWppZ4EkTj98vK6S2udtr9rfi6/+PpGgai4SfKGm0VIYnUKjJfpRUV2LOnsXrZ6JqHYnKemK7/T6THt863fe8PAzF9GrN8s0pmfE0u1r30TSnb8XfyVCS+JLR3Kq9L7RxH00ex3mODT1oO1eJy+PLk1ciGvQjq31bsJOTO/4AlDtWgvzFSIMq3Q9re6Gl2bThs0AMQfngyS8kxTZIivGBaU2vTDeDeFezDEz4N/O612W/HwRL39/YD6++6jHmdrLmgq77vv8bPWW6Qw==
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Circle Account Setup"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/organization/circle-config"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates the Circle configuration for the organization. Only account owners have permission to do this. Note: in the first time configuration, all fields are mandatory, but after it is been configured at least once, you can replace a single field at a time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./patch-organization-circle.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./patch-organization-circle.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/patch-organization-circle.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/patch-organization-circle.mdx
new file mode 100644
index 000000000..87992bc5f
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/patch-organization-circle.mdx
@@ -0,0 +1,5 @@
+---
+title: Circle Account Setup
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml PATCH /organization/circle-config"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/payments.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/payments.mdx
new file mode 100644
index 000000000..41d3a1fda
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/payments.mdx
@@ -0,0 +1,5 @@
+---
+title: Payments
+---
+
+Endpoints related to payments. An SDP payment is an individual payment from an organization to a receiver. Each payment is part of a disbursement and occurs on the Stellar network. Granular payment status is stored in the SDP database and can be viewed in real-time on the SDP dashboard.
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/payments.tag.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/payments.tag.mdx
deleted file mode 100644
index e89ad4323..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/payments.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: payments
-title: "Payments"
-description: "Payments"
-custom_edit_url: null
----
-
-
-
-Endpoints related to payments. An SDP payment is an individual payment from an organization to a receiver. Each payment is part of a disbursement and occurs on the Stellar network. Granular payment status is stored in the SDP database and can be viewed in real-time on the SDP dashboard.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/profile.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/profile.mdx
new file mode 100644
index 000000000..8daa7e948
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/profile.mdx
@@ -0,0 +1,5 @@
+---
+title: Profile
+---
+
+Profiles endpoints manage the process of getting and updating individual profile information. Profile information is set when the account is created and can be updated by the user on the SDP dashboard Profile page. Note: profiles never refer to receivers of funds.
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/profile.tag.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/profile.tag.mdx
deleted file mode 100644
index 7f8a1db9f..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/profile.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: profile
-title: "Profile"
-description: "Profile"
-custom_edit_url: null
----
-
-
-
-Profiles endpoints manage the process of getting and updating individual profile information. Profile information is set when the account is created and can be updated by the user on the SDP dashboard Profile page. Note: profiles never refer to receivers of funds.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/promote-distribution-wallet-to-default.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/promote-distribution-wallet-to-default.ParamsDetails.json
deleted file mode 100644
index 9bf3d3e70..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/promote-distribution-wallet-to-default.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"The unique identifier of the distribution account","required":true,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/promote-distribution-wallet-to-default.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/promote-distribution-wallet-to-default.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/promote-distribution-wallet-to-default.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/promote-distribution-wallet-to-default.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/promote-distribution-wallet-to-default.StatusCodes.json
deleted file mode 100644
index 2c913ff23..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/promote-distribution-wallet-to-default.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Distribution account promoted successfully","content":{"application/json":{"schema":{"type":"object","description":"A distribution account the tenant sends funds from.","properties":{"id":{"type":"string","description":"Unique identifier for the account"},"name":{"type":"string","description":"Human-readable name for the account"},"description":{"type":"string","description":"Optional description"},"distribution_account_address":{"type":"string","description":"The account's Stellar address. Absent until the account has been provisioned on the network."},"distribution_account_type":{"type":"string","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"],"description":"How the account's secret is stored. Additional accounts are always `DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT`."},"distribution_account_status":{"type":"string","enum":["ACTIVE","PENDING_USER_ACTIVATION"],"description":"Status of the underlying Stellar account"},"status":{"type":"string","enum":["ACTIVE","PENDING","ARCHIVED"],"description":"Lifecycle status. `PENDING` accounts have been reserved but not yet funded on the network and cannot send. `ARCHIVED` accounts accept no new disbursements and are never deleted.\n"},"is_default":{"type":"boolean","description":"Whether this is the tenant's default account. Exactly one account is the default, and it cannot be archived."},"created_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"archived_at":{"type":"string","format":"date-time","description":"When the account was archived, if it has been"}},"title":"DistributionWallet"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/promote-distribution-wallet-to-default.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/promote-distribution-wallet-to-default.api.mdx
deleted file mode 100644
index e316349ca..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/promote-distribution-wallet-to-default.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: promote-distribution-wallet-to-default
-title: "Promote Account To Default"
-description: "Makes this the tenant's default distribution account. Owner only. The previous default becomes an ordinary active account. Only an active account can be promoted; archived or still-provisioning accounts return 400."
-sidebar_label: "Promote Account To Default"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWF1z27YS/Ss7eEk8Q1GK6947o/ukWGqj1tdWLTl5cDwySKxM1CDA4EOKrob/vQOQlGhLtuM2nblTP0gygV2cswvuHmBDLL0zpH9NhtxYzRNnuZLwiQqB1pCbiDA0qeaFf0z65L/0Hg3YjPsPBIuSSvvGAMMFdcICa3uhaaqctDFcrCRqUFKsY5hlCIXGJVduZ5ZgqnI0QCUozbikeg00tXyJLSdSrP2Eh88hpRIS71LlyiL7D1CdZnyJDJQGY7kQnUKrJTdcSS7vGjsDGq3TEk56vZhERBWoqUc9ZqRPJpW3dkyqkMzUsIJMIlJQTXO0qH38NkTSHEmfcEYiwn2sCmoz8jiAnr6T/ItD4Ayl5QvuQ7MI4TwUPRIRjV8c18hI32qHETFphjkl/Q2x68Kv6a3kHSnLGz/ZFEoaNH78uNfzXw8hDA+sso0fGJemaMzCCbEmEUmVtCit90KLQvA0BKn7u/GuNvtQVPI7pnaP9uAgt9YeAoOSGVi48KlV7pNSaJ8WyysynO1TfrzO1V5oF0qHZZpwllGdqZdcfXA5lR2NlNFEIHijQ84eGL3k8yL8oALaj72TVnDmtfM5ZUyjMS97ne0QvTEwtSgE1VCbxzBIDEoLTlou2ughowYSRAnbF8S/NTLMkWhXSt/HT6KrIO1DQ+nyUE/G09nl+P3VbHxxPh+cnl5cnc/i6Wx0dja4jEfnH0n0/JTh+/nHwdXZ7Kl5p+PL07PRbtpeqfqgVm22bwwYTDVa4AaMVRpZDAPGeJ2RbV2gGoGKFV0buP0mhLdPB8lYat3BDDZhGpzOxh9HJCKT0flwfP7z/Go6upyHpwO/6j6vafDZlAwnGWqx9pVtm/jd5nz9+iQig8vTD+OPo+H+0md8gek6FQiV4xhua7PbXfwyusRqW2k0qH0lTpwFqSys0YY3fG+bAZXMV3I/yReCGG4bFC3PNE2x8J5A4soXlMRpgzmGMclC5iQuUQNDgRZZ/Dm8XdzM60bTikSilEAq916mTxnaDHXV455qc9umNPpKUyvWoOTutaqN6rlRgMZtQy/BbYcK+ybVSC2yObWH0rRQOvcjhFGLHctz9DauYK+2aRb9dqMDkZEP6seKmi2XCPjCs2xqCinLiFhuBT7qOFUfJWXpJ5wc6k/vKYNL/OLQ2L/SgB42D9Ra6ZdL6RAt5cIATZSr2lNlWEYEv1pNzYsrldWf5/Zun9uVpM5mSvP/IfvbyX076P1CIV2eYOCdozH07kCtr3niV5oXAls4yLmy8IDnDkaz0EnvXcv1Y4ttCH/YD+FPSiecMZR/f/yeoLdD0MA82YfpGf2knPyHp3lRUzyU4ZN2hi/RKKdTDI2gsmreFIOp09yug4x+j1SjHjibkf71jVe0OdpMeVVeKFPpbj9Guu2O21lVJ5buhrOyW4vZjlUdtpXroRfVWt1pQfqEeO/N4lOfhCpKbQjbaNCC/4rrfWFbb9qQUciQMtTg8015ddyQMB1O4JdPM3g7mh7/+K8jfy6pns5hMBnDPa691q2PDw/8NSeJyq3P0nQ0edf7TshgOpp03vUqbBVn2Fh1j7I8ehWi45Pviej45Hsg+s2hXn8brDAVtqe5pxC1AARIzcJfvHlod1wuVFiubnuNIBu2lApMBLW+2frck4j4LVnB+Hfci3t+n7o8p3pd6/rnfbydDidHXnBQsEoJSBwXNpxSlL6jsg6RAasgp/cIiRP3UNB1pZmsAgp3WrnCq0mNKS94GFBLrM45zerb08Cho8f/F8TP8rOc1drNXycUKDt15Sm08lURbEaDSqugeCWqikZPP3JXqTc/kCqGzWVDKF+NhF0oIdTK7xaNhTLcKs3R9D2ODlybyl+3/u60VWunqIPUSWh6j5LdvM2sLUy/273jNnNJnKq8+yoPR30I5LdQ1s12rkRpPa3SpHKhqbHapdbpmmBzwH02p/ErmC106H1/hVrj4iVuK0ygmfun2WQo8k6aUW3Ns5Bb87pWI3ZzymW3fvAsn5dofECRQ3AU8DMshArnuxeZgDN+3q8uQS3RovHnn4hY1Lm5WExRL3nq61JDq4YZK33XDZM6atEx9bSICJ6iNKHjN4W3oGmGcBzqVNVDva9+t7tarWIaRoO32tR0z8ano/PpqHMc9+LM5iLUSd/Hcypbjuv7NhjUJ4uZgt0926Mblq2Y+udeRtb9yuJX2y0E5eEUG+K9qdXPNTmkfkhE+uH+8YAAuolI5vVT/5psNgk1eKVFWfrHVQPrX99EZEk197ddQSQxbvxvRvoLKgw+k4i3l/UN5RH8mfvNg3Sbni19w15S4fx/JCL3uK5uWcubMmq6vodbDQzCHUHLZE9wP5CUk4upv2Gie0LhPgiF+od3fxDPYyVSYfCfZfSEyWZTyZCy3M6vhp60qDluqXsKZVn+AfdwVjA=
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Promote Account To Default"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/distribution-wallets/{id}/promote-to-default"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Makes this the tenant's default distribution account. Owner only. The previous default becomes an ordinary active account. Only an active account can be promoted; archived or still-provisioning accounts return 400.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./promote-distribution-wallet-to-default.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./promote-distribution-wallet-to-default.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./promote-distribution-wallet-to-default.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/promote-distribution-wallet-to-default.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/promote-distribution-wallet-to-default.mdx
new file mode 100644
index 000000000..3f7e18818
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/promote-distribution-wallet-to-default.mdx
@@ -0,0 +1,5 @@
+---
+title: Promote Account To Default
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml POST /distribution-wallets/{id}/promote-to-default"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/provide-signed-challenge-transaction.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/provide-signed-challenge-transaction.RequestSchema.json
deleted file mode 100644
index 79f6a12f8..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/provide-signed-challenge-transaction.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"application/json":{"schema":{"type":"object","properties":{"transaction":{"type":"string"}}},"example":{"transaction":"AAAAAgAAAADIiRu2BrqqeOcP28PWCkD4D5Rjjsqh71HwvqFX+F4VXAAAAGQAAAAAAAAAAAAAAAEAAAAAXzrUcQAAAABfOtf1AAAAAAAAAAEAAAABAAAAAEEB8rhqNa70RYjaNnF1ARE2CbL50iR9HPXST/fImJN1AAAACgAAADB0aGlzaXNhdGVzdC5zYW5kYm94LmFuY2hvci5hbmNob3Jkb21haW4uY29tIGF1dGgAAAABAAAAQGdGOFlIQm1zaGpEWEY0L0VJUFZucGVlRkxVTDY2V0tKMVBPYXZuUVVBNjBoL09XaC91M2Vvdk54WFJtSTAvQ2UAAAAAAAAAAvheFVwAAABAheKE1HjGnUCNwPbX8mz7CqotShKbA+xM2Hbjl6X0TBpEprVOUVjA6lqMJ1j62vrxn1mF3eJzsLa9s9hRofG3AsiYk3UAAABArIrkvqmA0V9lIZcVyCUdja6CiwkPwsV8BfI4CZOyR1Oq7ysvNJWwY0G42dpxN9OP1qz4dum8apG2hqvxVWjkDQ=="}},"application/x-www-form-urlencoded":{"schema":{"type":"object","properties":{"transaction":{"type":"string"}},"example":{"transaction":"AAAAAgAAAADIiRu2BrqqeOcP28PWCkD4D5Rjjsqh71HwvqFX+F4VXAAAAGQAAAAAAAAAAAAAAAEAAAAAXzrUcQAAAABfOtf1AAAAAAAAAAEAAAABAAAAAEEB8rhqNa70RYjaNnF1ARE2CbL50iR9HPXST/fImJN1AAAACgAAADB0aGlzaXNhdGVzdC5zYW5kYm94LmFuY2hvci5hbmNob3Jkb21haW4uY29tIGF1dGgAAAABAAAAQGdGOFlIQm1zaGpEWEY0L0VJUFZucGVlRkxVTDY2V0tKMVBPYXZuUVVBNjBoL09XaC91M2Vvdk54WFJtSTAvQ2UAAAAAAAAAAvheFVwAAABAheKE1HjGnUCNwPbX8mz7CqotShKbA+xM2Hbjl6X0TBpEprVOUVjA6lqMJ1j62vrxn1mF3eJzsLa9s9hRofG3AsiYk3UAAABArIrkvqmA0V9lIZcVyCUdja6CiwkPwsV8BfI4CZOyR1Oq7ysvNJWwY0G42dpxN9OP1qz4dum8apG2hqvxVWjkDQ=="}}}},"required":true}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/provide-signed-challenge-transaction.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/provide-signed-challenge-transaction.StatusCodes.json
deleted file mode 100644
index a53ab767f..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/provide-signed-challenge-transaction.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"SEP-10 handshake was successful.","content":{"application/json":{"schema":{"type":"object","properties":{"token":{"type":"string"}},"example":{"token":"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJHQTZVSVhYUEVXWUZJTE5VSVdBQzM3WTRRUEVaTVFWREpIREtWV0ZaSjJLQ1dVQklVNUlYWk5EQSIsImp0aSI6IjE0NGQzNjdiY2IwZTcyY2FiZmRiZGU2MGVhZTBhZDczM2NjNjVkMmE2NTg3MDgzZGFiM2Q2MTZmODg1MTkwMjQiLCJpc3MiOiJodHRwczovL2ZsYXBweS1iaXJkLWRhcHAuZmlyZWJhc2VhcHAuY29tLyIsImlhdCI6MTUzNDI1Nzk5NCwiZXhwIjoxNTM0MzQ0Mzk0fQ.8nbB83Z6vGBgC1X9r3N6oQCFTBzDiITAfCJasRft0z0"}},"example":{"token":"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJHQTZVSVhYUEVXWUZJTE5VSVdBQzM3WTRRUEVaTVFWREpIREtWV0ZaSjJLQ1dVQklVNUlYWk5EQSIsImp0aSI6IjE0NGQzNjdiY2IwZTcyY2FiZmRiZGU2MGVhZTBhZDczM2NjNjVkMmE2NTg3MDgzZGFiM2Q2MTZmODg1MTkwMjQiLCJpc3MiOiJodHRwczovL2ZsYXBweS1iaXJkLWRhcHAuZmlyZWJhc2VhcHAuY29tLyIsImlhdCI6MTUzNDI1Nzk5NCwiZXhwIjoxNTM0MzQ0Mzk0fQ.8nbB83Z6vGBgC1X9r3N6oQCFTBzDiITAfCJasRft0z0"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/provide-signed-challenge-transaction.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/provide-signed-challenge-transaction.api.mdx
deleted file mode 100644
index 83cae59c6..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/provide-signed-challenge-transaction.api.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-id: provide-signed-challenge-transaction
-title: "Provide Signed Challenge Transaction"
-description: "Allows the wallet to post the signed SEP-10 challenge transaction. More information     [here](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md#challenge). The endpoint url can change but is provided in the toml file under the  `WEB_AUTH_ENDPOINT ` variable."
-sidebar_label: "Provide Signed Challenge Transaction"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWFtz2roW/isanZd2NhfjhDRhZj9wMcQ0mJsxl7Szt2wLLHyRkWQIZPjvZyRDk7S7TXtOHvZD/QC2tC7fkpbWWlqPUKAVh7V7OMIrwgVDgtAEfi5AH3OPkVR91mA9iuiOAxFgsENRhAUQFKSUCzXEySrBPhgbg2JFA14gKZIVBoKhhCNPyiiBHmUYkGRJWayUAPncB5jhz+8CIVJeK5dXRASZW/JoXOYCRxFi5/9iyqigHo3KbkTdcoy4wKyMPcr3XOC4zHFa1LSKVor9/3wB8L4E7AADnPgpJYkAGYuAhxKJUMJzMwEIBymjW+JjH5BEWSNoHIEliTDIEh8zNQb+nhqNv+oT+/Yvw2oN+qZlg7/BFjGC3AiXYAHSFOeLZ/qwBge5zLFamOYZj/20HrAAGd5kmIsG9few9gg9mgicCPmK0jQinpJWXnO5AY+QewGOkXwT+xTDGqTuGnsCFmDKpG5BMFezz3Q8EXPBSLKCx+OxAPEDitMIf0MM6/JZyZ+WSUaZ3mCbDe57A/16MG2GrctWdbRe803woXK7227asz/al85MkneG9ZePoX5nBzbx1FRj2RfLylfzjfzVaFyzYGOhD9povkZW0q7UR4bedO+qGhnd3A5mY7u8NOOupfibEl+roaFOdEAzK/A7zsFvVg/zaTWcxzeXd3E7m+vB1iPVwI0t6l50Q1evBGh6mc31G2F22hW/s/qif9jxO/12ZA7jygF1UmNqzLU7zelO2ovM6zjRKHxw7NZcdzTxsec0BvPZIps4TsNaN+iddjNDzZtKT3e2fli9nLa7YmzXt0N98mTqNsBtZ6fUBfijUbldd5JJ09oN3Nl1fPjQ3FAxDj669T8eevqtu46uZprdSI2UOf2Js65fRZtet7K+0rfsIanE7QvcPfA7dMNvghFddi7qnMzDi4mSz0wWbjdxXXNuInPhOfvmxF+jqybZhYMdd64bS/OyuejvR5X+5sOeb63udDfXOpe6nz5YN/1BZXO49LP4GqUdPdhsH5zpOmwN//wTSq957pMPxd1uV5QnuZixCCce9bH/hk7620d/++iv+6j0GxlTCZPOKFiG1QBPacJzt9M1Tf69TG2nrBWgxOcBCmWC44Bnnoc5X2aRjO1vFZppiH/C33MqiPfdwO14pE+65uRgVixicjMZVb2meWWG6cxpdm9KeN89+FNTEt0O7YUzdoL5xHBm08miaxtVZ+z4jeGhdzG1R6OJ4SDbaU9HRmqODDF1tAUar7t3w4rvDMPIsSbRfBpWjeHY5GacamhsXplrQ7M6w4O19slcN3cL29vP9TZZxCOy6Ez0XscJFnYjWLS8Q0+31tbaCXuxoVv26qLXWh0WnTbp6UO9Zy/ifmtV6dnhrrcekrtmN/UuehI39W9HO+9At3f6gs9njR0eVwiadcO76SjwbuvZIo72i2k38HRHfcsjcreXGKPAb5pXPXtysFpmxTqEVau5I4tZsDPX9MGye1rvMNR6h1BbDkvXidu4vlhcbTuNVbMyu2EX1hUdNtt249Aipl1fNruIj5ZCO2i/t+TfuCVyUy7/6QQ3kA9GeTH1docVM0bZt4f168K4hQUiEQfIpVleDOeMyoEEQ/xVTcfTU4APRZlIVzgpnkrDokv9fTFBseSW71BJxQknNJFV+yMM8R7WfshZgFsUZV8kHD8XYIxFQGWZKit4iQeJANagLKIrWhllIoAFyDHbYpZryVgEa1DxcuxljIj9WK5jvlQNjBhmdcn2ZCxKyUe8/2a9JBVl5JBfAQKMZIUttwyRhCQrgBIwbg1Ad2qDd8ZYr169B5SdRv8C9YEJQryXMfm0Ki/kwQIkUkkuVu7B2BhUtDdCdr7fKGy5zeBRhYbj+19CpF++JSL98i0QDTPM9j8HS5GCFDEUY/F9RM8A5PHzpHgj2VWElUdy9HQJMr5X853zpBSwpGqeCEkIx/nlELQIdzPGcYwTAQYRErI2ld4ivR8znsv5UNJKmvTsLI4Rk+dG3g5/LOPduDV4L2+JCAhKI+BmJBJgSRmgbIWS06JyeR2OZfHgZlEIUrSXUtQoAitGsxTQJWDYIylRE3R7ulietSdY7CgLS9+s9r8P4qfkU2IHhCuVCaApToqcZszD8iotQxwQAVJX6xwKTYCgSvw/iCsAlPhqQoYwdT13MVjSLPEVYyA/ZPdB+hfDKeVEUEYwr0kcRXD/daPAf7ZIxfS0SEUXeSFO/J9qNfxQwvsaUMZ/gbI/H4C8PXIiU1aRZMkQFyzzRMZOBsp9Ea/taekXLFsylfD+H9POIl6zbYddcKb9n60JcBQXvQAxwX8I+RldWTCMyzEiSfk08EN7XjPjFkcxUIIUfh+nEd1L93rVEpBxSfcxczFLsMC89EnGNYFZzPvLMWZb4sm4dDbrBLNE2aqsiIp0WeQnsgKMiIcTriLeOVSnyAsw0FWcyrOulFUrl3e7XQmpWSXtxMrLd2bTsMZGUS9ppUDEkYqsMq/HKHkm+NSQAnlHCnxpSYGXPakXsedZT+p3A/DVBuApaQr8IMpphEgiE5bawsdTgXUPVYEFC1CVWJ8LMJD1V+0ePj66iOMJi45HOZynyNr9Z1m75Rrk17FwztpPlV8z36GiLbU/lXqvd2uOhbOIuufhVHyHWZXNL2rGQX9sw0JeTNYeYUx9yfNMcuH5h4R9PP4XJ+q1fQ==
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Provide Signed Challenge Transaction"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/sep10/auth"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Allows the wallet to post the signed SEP-10 challenge transaction. More information     [here](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md#challenge). The endpoint url can change but is provided in the toml file under the  `WEB_AUTH_ENDPOINT ` variable.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./provide-signed-challenge-transaction.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./provide-signed-challenge-transaction.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/provide-signed-challenge-transaction.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/provide-signed-challenge-transaction.mdx
new file mode 100644
index 000000000..86d4cc092
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/provide-signed-challenge-transaction.mdx
@@ -0,0 +1,5 @@
+---
+title: Provide Signed Challenge Transaction
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml POST /sep10/auth"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/receivers.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/receivers.mdx
new file mode 100644
index 000000000..0d6a6384e
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/receivers.mdx
@@ -0,0 +1,7 @@
+---
+title: Receivers
+---
+
+Endpoints related to receivers. A receiver is an individual receiving a payment in a disbursement. The receiver is tracked by phone number to reduce the need for personally identifiable information. Each receiver must be unique within the disbursement.
+
+Each receiver will have at least one wallet associated with them. The wallet public key will remain null until the receiver registers with a wallet provider and links the wallet to the SDP through SEP-24. Receivers must verify their identity through that process, which requires the SDP to store verification information on receivers like date of birth, national ID number, or personal PIN. This information can be updated by the organization through the receiver endpoints.
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/receivers.tag.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/receivers.tag.mdx
deleted file mode 100644
index 64d048dff..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/receivers.tag.mdx
+++ /dev/null
@@ -1,23 +0,0 @@
----
-id: receivers
-title: "Receivers"
-description: "Receivers"
-custom_edit_url: null
----
-
-
-
-Endpoints related to receivers. A receiver is an individual receiving a payment in a disbursement. The receiver is tracked by phone number to reduce the need for personally identifiable information. Each receiver must be unique within the disbursement.
-
-Each receiver will have at least one wallet associated with them. The wallet public key will remain null until the receiver registers with a wallet provider and links the wallet to the SDP through SEP-24. Receivers must verify their identity through that process, which requires the SDP to store verification information on receivers like date of birth, national ID number, or personal PIN. This information can be updated by the organization through the receiver endpoints.
-
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/refresh-token.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/refresh-token.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/refresh-token.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/refresh-token.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/refresh-token.StatusCodes.json
deleted file mode 100644
index 97725a9a9..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/refresh-token.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Returns a new access token","content":{"application/json":{"schema":{"type":"object","properties":{"token":{"type":"string"}},"example":{"token":"eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VyIjp7ImlkIjoidXNlci1pZCIsImVtYWlsIjoiZW1haWxAZW1haWwuY29tIiwicm9sZXMiOlt7Im5hbWUiOiJTdXBlcnZpc29yIn1dfSwiZXhwIjoxNjc1OTYyOTQ3fQ.4Zj9yBXch-iuFYF-kc_EhHPxjpwp_egMOLbOv4bZKO1MFvcmEgZ5MlXH1_1fZfgUxaNBcMCdRM6MGSqKocwGnA"}},"example":{"token":"eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VyIjp7ImlkIjoidXNlci1pZCIsImVtYWlsIjoiZW1haWxAZW1haWwuY29tIiwicm9sZXMiOlt7Im5hbWUiOiJTdXBlcnZpc29yIn1dfSwiZXhwIjoxNjc1OTYyOTQ3fQ.4Zj9yBXch-iuFYF-kc_EhHPxjpwp_egMOLbOv4bZKO1MFvcmEgZ5MlXH1_1fZfgUxaNBcMCdRM6MGSqKocwGnA"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/refresh-token.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/refresh-token.api.mdx
deleted file mode 100644
index 58d10469d..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/refresh-token.api.mdx
+++ /dev/null
@@ -1,62 +0,0 @@
----
-id: refresh-token
-title: "Refresh Token"
-description: "A user’s token expires after 15 minutes. This endpoint handles refreshing the user’s token without disrupting their experience. It is triggered within the 30-second window before the token expires."
-sidebar_label: "Refresh Token"
-hide_title: true
-hide_table_of_contents: true
-api: eJztV9tu2zgQ/RWCTw0gX5u0iN9ybZU0sRs7TWLXCChqZNGWSJakoqiGgf7G/t5+yYKU1DpJm7S7KbBYrB8sm5w5c2Y4nBktsSEzjXsTvJOZGLhhlBgmOJ56OARNFZPubw/voEyD+vPLHxoZsQCO4FYyBRqRyIBCnS2UMp4Z0E00iplGwEMpGDcoJjxMQCMFkQIdMz5DJob7aDkzscgMCplWmTSVFFPWDCgGnEIT+QYxjYxisxkoCJ0S4w7uZbuhgQpuF3kochRAJBS4vTt8m9jDQoJybvoh7uGzktjISmEPK9BScA0a95a4227bx91QnIHJFNeIIA45IpSCrtzAHqaCG+DGahEpkyqerbm2qkusaQwpsb9MIQH3sAjmQA32sFSWlmGl4RLum5g2ivEZXq08DLcklQmsSWEojuLgDWV9dnR4/tnvnDJf+/xsi+75r/yFvPywd7TdhOKoQ7sfCn8uX/tpsvDngoWXpwllHTne87WffjBXF4m26+OLTkwubnfKZ55ddbeNz3JG0209vjxh/cS89tOtOLg4t0ZH4eVuQvlY0u524fNOGA1zNr6Mc38ubk/ntNMfXRX90fuX0fvm5ni+Xexe0rjBssOrw8aCXh/Ebwe3c5nLa5id9N8F/ZvNYHzc75wc3tD0YDbeOkku33auO9E4mp3fktNderIXnp28Onkz/HQsaP6G7/wfmUciY2Oz+b1M3iUhOoNPGWjzfKkLSgn1MHXvF5R9MIQlGpHA3nt7T0tFd45GEf2kpVX5sb51Hvp2zklmYqHYZwh/u3M/TxprQ0y2LsezNADndwpakxl879rfS++KBj4VBt1x8xuL2s5mu7OGfF/jdwI7bA00U8wUuDdZ4l0gCpRtNbg3ma6mVt/EwlZhKVwOSmL3cKvqFo26rGpQN6C0Q8lUgnsYW/UafWiPr4zvuo2vcSSSHUPxIAd3Kr4uF1AMJASFbKYQxm0LIhwN9wfo6GKEXhwMu1uvNpBQ1eo12hn4aAGF7SicpHAfD3uYWSMlrD3f4cGg034mZmh4MGh02iW30me0dNFabfwSo+7mczLqbj4Ho/cZqOLnaDlRJIkiKZgfM1ojUKeUM/zJqrvmwXgknDlm7FXAQwNJQhTaZzrIlIYUuEGDhJhIqNSePfawTcmSxutmu9m2eZqlKVEF7uFRDOhxjBfD/cGGnWgIMkIkKMhYYlAkFBJqRngVIjtaoJQsAAVZskCSFBbFrRI0UyKTSERIAWWSuQ1xA8rV09o6B5MLtWg+iN2/j+JH/pG78dGa5EhI4A0tMkUBSSVsPUUmJm4MLKkIjoxw8N+B8xDhodugIgRECUcBoEhkPHSKsf2TJCK32aJACs2MUAx0z/JooIku8VrVsxGuBakhqyA1AkIXwMPpi9gYqXut1oyZOAuaVKStX0LY6JWz81cqRZ3O2pGtxJxXjEeKaKMyajJVOWjPxTx1ps1f8CxSrmv+E9dqiKd8yyFAtezf9iaGJG3QmCijH6W8JtcyCqCVEsZb1cKj/jzlxltIUuSAHP8QZCKK+p3n8buWaSt3nAWgONgXqY+2ShlQqe5HQ1A3jNq6VLtV0WwKNWs5oYaIGroS83DCKHDtenpdeCWhMaCuq1NlD7VYvVYrz/MmcbsOrVLVrXf+3sHp8KDRbbabsUkTVydto04JXwOuXqBQ/QZ1p8gsv01e/6l3yKorGbg1LZkQxm3zclFdVkPMBN8dYqYeju2Q05vg5TIgGs5VslrZ5bIJ9SZTD98QxUhgG9BkuvLqvminngXYrrJDKUg7KN2QJCvb4r1h9s5UNegPR9jD5EErXbhWWv2w8PUWL9bA7/fqkoP9Xnk/UFkuy0a9Wn2VL7d+qFH5WEvbSE5Xq9VfzTPb6Q==
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Refresh Token"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/refresh-token"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-A user’s token expires after 15 minutes. This endpoint handles refreshing the user’s token without disrupting their experience. It is triggered within the 30-second window before the token expires.
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./refresh-token.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./refresh-token.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/refresh-token.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/refresh-token.mdx
new file mode 100644
index 000000000..ed9384723
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/refresh-token.mdx
@@ -0,0 +1,5 @@
+---
+title: Refresh Token
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml POST /refresh-token"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/registration.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/registration.mdx
new file mode 100644
index 000000000..9a4b81f43
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/registration.mdx
@@ -0,0 +1,9 @@
+---
+title: Registration
+---
+
+The registration endpoints guide the process for a receiver to verify their identity and link their wallet address to an SDP. The registration process only needs to happen once per receiver to link their wallet. Only SDP-compatible wallet providers can facilitate the registration process. These endpoints must be supported and hit by the wallet providers after the receiver gets the initial invite. After the wallet address is successfully linked, the payment automatically begins.
+
+There are two parts to the registration flow. First, the wallet must authenticate and initiate a registration flow using the Anchor Platform Endpoints defined below. Note that these endpoints are hosted on a different host than the Stellar Disursement Platform.
+
+The second part of the registration flow is handled by the webview that is opened within the wallet application. This webview uses the endpoints defined in the Stellar Disbursement Platfrom Endpoints section to complete the registration process. The wallet application can chose not to use the webview and intstead integrate directly with the API.
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/registration.tag.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/registration.tag.mdx
deleted file mode 100644
index 65139164b..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/registration.tag.mdx
+++ /dev/null
@@ -1,25 +0,0 @@
----
-id: registration
-title: "Registration"
-description: "Registration"
-custom_edit_url: null
----
-
-
-
-The registration endpoints guide the process for a receiver to verify their identity and link their wallet address to an SDP. The registration process only needs to happen once per receiver to link their wallet. Only SDP-compatible wallet providers can facilitate the registration process. These endpoints must be supported and hit by the wallet providers after the receiver gets the initial invite. After the wallet address is successfully linked, the payment automatically begins.
-
-There are two parts to the registration flow. First, the wallet must authenticate and initiate a registration flow using the Anchor Platform Endpoints defined below. Note that these endpoints are hosted on a different host than the Stellar Disursement Platform.
-
-The second part of the registration flow is handled by the webview that is opened within the wallet application. This webview uses the endpoints defined in the Stellar Disbursement Platfrom Endpoints section to complete the registration process. The wallet application can chose not to use the webview and intstead integrate directly with the API.
-
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction.ParamsDetails.json
deleted file mode 100644
index 6f2462ae0..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"account","in":"query","description":"The client account (G...) that the client wishes to authenticate with the server.","required":true,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"memo","in":"query","description":"The memo to attach to the challenge transaction. Only permitted if a Stellar account (G...) is used. The memo must be of type id. Other memo types are not supported.","required":false,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"home_domain","in":"query","description":"Home domain for SEP-10. Defaults to the server base domain if omitted.","required":false,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"client_domain","in":"query","description":"Client domain for wallet attribution. Required when SEP-10 client attribution is enabled (default).","required":false,"style":"form","explode":true,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction.StatusCodes.json
deleted file mode 100644
index 7e6cb7444..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"type":"object","properties":{"transaction":{"type":"string"},"network_passphrase":{"type":"string"}},"example":{"transaction":"AAAAAgAAAADIiRu2BrqqeOcP28PWCkD4D5Rjjsqh71HwvqFX+F4VXAAAAGQAAAAAAAAAAAAAAAEAAAAAXzrUcQAAAABfOtf1AAAAAAAAAAEAAAABAAAAAEEB8rhqNa70RYjaNnF1ARE2CbL50iR9HPXST/fImJN1AAAACgAAADB0aGlzaXNhdGVzdC5zYW5kYm94LmFuY2hvci5hbmNob3Jkb21haW4uY29tIGF1dGgAAAABAAAAQGdGOFlIQm1zaGpEWEY0L0VJUFZucGVlRkxVTDY2V0tKMVBPYXZuUVVBNjBoL09XaC91M2Vvdk54WFJtSTAvQ2UAAAAAAAAAAfheFVwAAABAheKE1HjGnUCNwPbX8mz7CqotShKbA+xM2Hbjl6X0TBpEprVOUVjA6lqMJ1j62vrxn1mF3eJzsLa9s9hRofG3Ag==","network_passphrase":"Test SDF Network ; September 2015"}},"example":{"transaction":"AAAAAgAAAADIiRu2BrqqeOcP28PWCkD4D5Rjjsqh71HwvqFX+F4VXAAAAGQAAAAAAAAAAAAAAAEAAAAAXzrUcQAAAABfOtf1AAAAAAAAAAEAAAABAAAAAEEB8rhqNa70RYjaNnF1ARE2CbL50iR9HPXST/fImJN1AAAACgAAADB0aGlzaXNhdGVzdC5zYW5kYm94LmFuY2hvci5hbmNob3Jkb21haW4uY29tIGF1dGgAAAABAAAAQGdGOFlIQm1zaGpEWEY0L0VJUFZucGVlRkxVTDY2V0tKMVBPYXZuUVVBNjBoL09XaC91M2Vvdk54WFJtSTAvQ2UAAAAAAAAAAfheFVwAAABAheKE1HjGnUCNwPbX8mz7CqotShKbA+xM2Hbjl6X0TBpEprVOUVjA6lqMJ1j62vrxn1mF3eJzsLa9s9hRofG3Ag==","network_passphrase":"Test SDF Network ; September 2015"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction.api.mdx
deleted file mode 100644
index a861fd4dd..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: request-challenge-transaction
-title: "Request Challenge Transaction"
-description: "Allows the wallet to get the SEP-10 challenge transaction to be signed. More information [here](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md#challenge). The endpoint url can change but is provided in the Get Stellar toml endpoint response under the `WEB_AUTH_ENDPOINT` variable."
-sidebar_label: "Request Challenge Transaction"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWFtT4zgW/isq7QvUJI6Thu4mW/OQO9cQkhBgaIqR7ZNYiSw5kpwQqPz3KclOIMBAdy+ztVvVfsjFOjr6zkVH39ED1mSkcPkad2FElZZEU8HxTQ4HoHxJY/u3jCuMiblCOgQ0J4yBRlqgkfkKAfUanXzRRX5oRvgIkJaEK+KbuUbOA6ToiEPgoBMhAVE+FDKyK6HrECTcbIVax6pcKIyoDhPP8UVUUBoYI3L1nY+l0MIXrOAx4RUiojTIAvhCLZSGqKAgzrtu0XWi4F9rJNsO6oeAgAexoFyjRDLkE26gGpxeohFVKJZiRgMIEOXWnhZo1EtXRVpE7HG+BBULrgAlPABphf+8aFRvK+f9/dtGu945PWj3/0QzIinxGDg4h0UMqVMPAlzGXZgmoHRtBbD/6CmcwzGRJAIN0kTkAXMSAS5j4vsi4RrnMDWhmCYgF/h5gIyZPqPANcrk0VbLcZxtpEOShikbnlMVgjJxIYkOgWvqEw1oTnVoxRTIGUgDXcI0oRICXNYygRxWesEMIBM9nMNwFzMRwHrUDyEiuPyA9SI2YkpLykd4ucytTYkgEu/bYaQsPq2JH5pfFv5r6eWgU84WKAYZUa1NCIeIrIP3zBNUoUSZLFwvEiVKm/QUQ2RAIxo46FSHIDMMixgUIhIQFxqpJI6F1BBs+mZImPoQ54QigttARITyt320LyJAqSAaCpntPwfVYUgSptXKY2kkkUfUWpwOkUg99Q8ZkSbZd5lRS/PxiSFZaSFaS+olaXy7GUY0D4GvS02W6Y+CJrjAzaYL0FaQOmL7Q228MbrS7a/MeMl1zdemTadHOId9wTVwbUZJHDOzv6jghbEyIg8vlxDeGHyzv2NpqoWm6QJP0vwVPDnMQc+FnNzGRKk4lETBq6HBcEeimMELlbhinpH5qB/QblKqyukUTv1O6Wvnojap79R3u+OxmoZfivvz2bR5+VtzZ3BpxFtnlc2nYT8v7+W5b4eqw1M9LD4br6Y/G9WvMpy2yRe3ezUmbd4sVrqNUs073nVpd2+/c9nrF4YH0WHbzq8ZfPWqS1rsnly2w6A1uA9qu/dXF7uTq2hv5zhqJlelcObT3dCL2sL7dDjxSsWQXOwkV6U9fdBqFoPWaL3+WStonTbZwVlUvCetuHHRuHKP3cHhefOPxG8NWHdyN+jXr0oDVx+dDKqdq8s/kvPBoNoeV8Wxu3dJanvFk9JgFkx2dy6ah7rXr8zOSuePpg5DaA7mdrkQjhrF/XGLn9fa8453+TW6/1KbCt0Lj7zKb3cnpX1vzD5fuv1q3Ijl4PR8MK58ZtOTw+L4c2km73gxan6Cw3t1TPbUXtgVw9anyuj33/Hrscd9UBr16k3UTkfRv1EPYg2RBxKV3OLur3T4lQ6b6WASYue1QlYlAcrIysdVNJBSyJdF6vnBUAdNKFOIeCJJqUs60SavlkS9u9Iye3I4Ah0Kw7xGYKWIDnEZG7ZYdAuGAOEcTs/JlHMlkuEyxqbaK/ATSfWiZ6xLDagCkSArZtojBBLTI3h5vBkpIel9ynNDIIYxGkcSyikfIcJRr95Bhxd9tNXolXY/byMhs7e3qNI5QBNYmBMsO1k39K1O1lSt8Uyv0Sm6H4RsdcxabKnN6EGLCfDl9g8hKu18JKLSzkcgOjNk5PtgWVG0ZuV/h+gJAAtpk/aYLDQdj12Oass9VgS1TpWXSAWRYTMdRrQhJSb2OIdNSqYwvjiu45o8TaKIyEXGkt/WsdWrdyzjJUgLwZCXUKYtyRJyRHjmIksVIzIxrRCboJgsjJa0OUAjKZLYUGMJPo2pHRCzrO1ZrZ5VHudVIv+/BfEb/8b7IVV2SY5EDDyvRCJ9MB2gKSNpr0RVBsV2r1b9K+pyiPAgbUxEALar9AANRcIDOzE0f0zXbLJFQiwU1UJSUGWDI4+un/e3wRMn5ePMSXmP+BPgwXd1yG9q2C4ja/waymKVzmlbn4lZqygfSqK0THydyMxAExf9XkydH7BsKO2h8p+YtlLxnm1z8NBK9qetCYFFeT8kUqs3IT+RK2gJUDDtTSF78aY975mxDyxCVpHFH0DMxMKk17uWoEQZuaPEA8lBg3K+mSqlQUbqdNgDOaO+bUEzszKYjpCjghXKi2FeZWI5zKgPPG03VoU3Jn4IqGTrVHqGGl3lQmE+nzvEjlpt2VRVOD6oNdq9Rr7kuE6oI2brZCyUjgh/ojjjIGh9Y4I2r0w2is7DI1H5dWP10zdW2Zmo4U4XYmba+GUW04eMP11jy59wDlsGdZPDoVDavH94MLcN55Itl+Z1egIaXhVQZZvzdRv+t4HbWnX82+ifuNR61boJLDYu2maEJWB5YO5HoP+/XF694YPshu4nHfBhN1NvINy8JvtJoP+du6c3rHh+T/Zox435k+5GXL6+WeZWBNZso3RyxfchfpqnL5oyo2Xd+rQafbxc/gW/mEHj
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Request Challenge Transaction"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/sep10/auth"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Allows the wallet to get the SEP-10 challenge transaction to be signed. More information [here](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md#challenge). The endpoint url can change but is provided in the Get Stellar toml endpoint response under the `WEB_AUTH_ENDPOINT` variable.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./request-challenge-transaction.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./request-challenge-transaction.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./request-challenge-transaction.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction.mdx
new file mode 100644
index 000000000..b0491e5ec
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction.mdx
@@ -0,0 +1,5 @@
+---
+title: Request Challenge Transaction
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /sep10/auth"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/request-registration-url.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/request-registration-url.RequestSchema.json
deleted file mode 100644
index 388273560..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/request-registration-url.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"application/json":{"schema":{"type":"object","required":["asset_code"],"properties":{"asset_code":{"type":"string","description":"Stellar asset code for the deposit."},"account":{"type":"string","description":"Stellar account for the deposit; defaults to the SEP-10 subject."},"lang":{"type":"string","description":"Language for the interactive flow."},"claimable_balance_supported":{"type":"string","description":"Indicates if claimable balances are supported."}}},"example":{"asset_code":"USDC","account":"GACW7NONV43MZIFHCOKCQJAKSJSISSICFVUJ2C6EZIW5773OU3HD64VI","lang":"en"}},"application/x-www-form-urlencoded":{"schema":{"type":"object","required":["asset_code"],"properties":{"asset_code":{"type":"string","description":"Stellar asset code for the deposit."},"account":{"type":"string","description":"Stellar account for the deposit; defaults to the SEP-10 subject."},"lang":{"type":"string","description":"Language for the interactive flow."},"claimable_balance_supported":{"type":"string","description":"Indicates if claimable balances are supported."}}},"example":{"asset_code":"USDC","account":"GACW7NONV43MZIFHCOKCQJAKSJSISSICFVUJ2C6EZIW5773OU3HD64VI","lang":"en"}}},"required":false}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/request-registration-url.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/request-registration-url.StatusCodes.json
deleted file mode 100644
index 10befb833..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/request-registration-url.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"An anchor requires the user to fill out information on a webpage hosted by the anchor.","content":{"application/json":{"schema":{"type":"object","properties":{"type":{"type":"string","description":"Always set to interactive_customer_info_needed.","example":"interactive_customer_info_needed"},"url":{"type":"string","description":"URL hosted by the anchor. The wallet should show this URL to the user as a popup.","example":"https://api.example.com/kycflow?account=GACW7NONV43MZIFHCOKCQJAKSJSISSICFVUJ2C6EZIW5773OU3HD64VI"},"id":{"type":"string","description":"The anchor's internal ID for this deposit / withdrawal request. The wallet will use this ID to query the /transaction endpoint to check status of the request.","example":"82fhs729f63dh0v4"}}}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/request-registration-url.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/request-registration-url.api.mdx
deleted file mode 100644
index db52f2cd4..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/request-registration-url.api.mdx
+++ /dev/null
@@ -1,73 +0,0 @@
----
-id: request-registration-url
-title: "Request Registration URL"
-description: "The deposit endpoint allows a wallet to get deposit information from an anchor,  so a user has all the information needed to initiate a deposit."
-sidebar_label: "Request Registration URL"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWGFv2zgS/SsD3odrANty3Wxz58PhkMbp1W23ycZJC2waBJQ0trimSC1JRfUZ/u+HISVbdtM47XaBO6BfEkviPL4ZDmceuWSOzywbXrMLnAnrDHdCK3bTYSnaxIjCPw7ZZYaQYqGtcIAqLbRQDriUurLAoeJSogOnYYZuPU6oqTa5B4Sp0TlwBVwlmTYdAKuBQ2nRQMYtIYHLcMtEIaaYEqhQwgnuEHiD3fuoPqoxMbAaJDrrrQM42AITMV0AT1NBSFxu4bqMOz/cz56X1oEt49wTdmh44sQdygXcCQ4cCl2UBWgDmMeYEqHY6IosK6FSXRG/GIHHEulnww/OJXKLkGSYzP1sKTouJKaQ6qTMUbnA5jpDgzdPMucKO4yimXBZGfcSnUfWoZTcNP+7hdFOJ1pGsdRxlHPr0ESYaLuwDvPIYtHt9weHvTz9S82iOzjofVSsw3SBYWHHKRuyC/y9ROvaC3518ZZ1GH5yaBSXI51YNlzupMBLoVLItQmrBMSbdVhpJBuyP4k+W3WYCWxf6HRBnBKtHCpHP3lRSJF4/tFvljgumU0yzDn9cosC2ZDp+DdMHAs4wmBKuc6tRXeb6BQp0wtD8XECvdOtbxsU64xQM7a7KybBN/A2QDYw1aZe7pAI5AJPEl0Gzo/ECwa7YP+AFKe8lJTu2n+YnJ53n/Ypf8lLP5nkarZ/prdczUo+2/Bt5T5Mpa48ViK5yCm1b2MuuUrw1pZFoY2jMO6bYqxSWh20IKawRoIayQI3CGu4HlutVpSBPC8k7q4Du5qMTlgrkOzfxycfjt6dvXt/+OznX8cvX52cvTn55fXxm8nryXgyGZ+8fH/1enDy/PTX8Yefjo6enV09ezV6fvh+zJoAMVSMZmwn0aduVVVdqhTd0khUNHn6I6t+ZNVXZtWqnRdTLi36N7bQyoZ0GPT7nxfY46Y9Qm1tN23KaZgKKUGX231VK2q/GBcU9UxbRw1q0eqGPdb59pq5ncPh674FOpYVX1iwQQ+0EuA2Ka3TOZpbcuA2tPceay0P2zeassc3nH0kri7e3h8NICFTyxWb6VKm9K8ClwkLZFVvAR90EiZBAGzTbLodL0Svfutb3nyRUJL/q06of35zOq06TDxiL1yu/fqrDZEmrTMe1dtP2LUUi6ASLksNr7iEuqNuxaKi5CotBrPxiOLwe4kmBC9yhitLC6PVRv45Xcsb67grLeipH9zAb4Xsb4NpZo8Gf58+f5Zm/btD2iV+oxzetxNe8BRqlfL90heN0WZ/UEdep1ngMe01cigY+jriDLd7Z1ptfHv6uW9Xipcu00b8B9M/3bnHk2ZhEVvjVJnH6P3O0Vo+u2fv13626mvNg73TDrb83NBoJjrsP21B71o0MbSYlEa4BRteL9nk9Pxp/7h0GRte36xuyNxlmjRtoX2qFJy+MVKTg8N21tqo3gpRq8Ywgjd3aKxHD1KWEW4z64TCH+LzArlBEyZfx4EX4g0uPq+BtR+hRmfIUzRAK82FEmpGB6HJ6Bxef7iEJ6eTwU/PD+iEEd7ewvH5GOa4oA2keI67eKzDBE0SYGl9WmH5w8ya5u+5BZ9h6fQc1ergqxgNDr8no8Hh92D0C1W0x9HyQ6HghufovsyoRcBTaib2tdMLTNrJF5szzOkXtMi6Gm3UyPpVrS3Wzw8KqNbWp87pPRXOF+FGCI6EjUtjkU6hcC65Iz1Bacc6jHZDiMBRr9/r0xYp85ybRd1vHsZ4MhmdH4Cgvum0lhCXQgbBqc2Mq3p1vNDM+RwhLuUcCr4gFP+Ww8xoOnBPwWAiCuE/6DsMerKZXaGrtJn37m2J/1sU6abikpoqTalAF6i6VpcmQSiMplIcbiSEranQFYUumm66A9cBrlL/wZ8LEq7o9mGqS5V6w4we6FqGEtWEkqeNQDskHl243j2Wp60gdYs6SN2YJ3NU6aPuJR5EOBiCd35NZdHspCBu62HeK6GmhltnysSVBrcPPg+uae8rPJsa33D/iGsNxD7fKoyhGfvN3mQo826ScePsg5Rb4yJnEKOcCxXVLx70Z58br1Dm4IE8/xQLqReUXns9gdLSuDdljEahQxtuoxya3J5NJ2juRNLW0zXNnjazyA/q6mnX1sM6TIoElfWls6n5BU8yhIGvU5ubqGEUVVXV4/6rR6tNbfR2fHL6bnLaHfT6vczl0pdoEg85Vy3gumBD+44MwiXZVr1p3Uf9uCL9v74irdWAw08uKiQXqnXWDKrymnlVSWNbutJnhIfyrX+jLW86jE6gZLdcxtzilZGrFb0O2mB4fdNhd9wIiovXs51GrpAYnSN13JOQXd1LYkfDZRk0y75Lq1WngThOEizcF4z9MWNLSJ+fTS5Zh8X1dWse1EkLudN+CLT5Z4pq7hVV/YPcaT6pRYvJrmQLhOkv0b/XZLkMem21Wo8Pn75oUce0GU0Le7Narf4LCDnNQQ==
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Request Registration URL"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/sep24/transactions/deposit/interactive"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The deposit endpoint allows a wallet to get deposit information from an anchor,  so a user has all the information needed to initiate a deposit.
-
-It also lets the anchor specify additional information that the user must submit interactively via a popup or embedded browser window to be able to deposit. Please check the detailed documentation [here](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md#deposit-2).
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./request-registration-url.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./request-registration-url.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/request-registration-url.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/request-registration-url.mdx
new file mode 100644
index 000000000..b9fced9e4
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/request-registration-url.mdx
@@ -0,0 +1,5 @@
+---
+title: Request Registration URL
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml POST /sep24/transactions/deposit/interactive"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/reset-password.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/reset-password.RequestSchema.json
deleted file mode 100644
index 16dffae57..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/reset-password.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"description":"Reset password request data","content":{"*/*":{"schema":{"required":["password","reset_token"],"type":"object","properties":{"password":{"type":"string","description":"New password for the user"},"reset_token":{"type":"string","description":"Token used to identify a valid password reset request"}}}}},"required":true}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/reset-password.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/reset-password.StatusCodes.json
deleted file mode 100644
index 753760ed3..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/reset-password.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Password reset successfully","content":{}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/reset-password.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/reset-password.api.mdx
deleted file mode 100644
index 7d470f464..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/reset-password.api.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-id: reset-password
-title: "Reset Rassword"
-description: "Allows an SDP user who has gone through the Forgot Password process to set their new password with a token sent via email."
-sidebar_label: "Reset Rassword"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNVlFv20YM/ivEPTWFZLlBtwF6S5sM6zq0Xp1hD2lQnCTaulq6u/KouJrh/z7wJDV20yXrVmDzi22J/Pjx4x3JnWK9Diq/Umcd12jZlJqNs+o6URWGkoyPf3N11jRuG0BbWJ4voAtIsK0d1DrA2lkErsl16xq4RvjR0doxLHQIW0cVeHIlhgDsICCLiSGwuAU/WWwN16CB3QYtBLQMN0YDtto0M5Uo55EirxeVyhVhQJ7AVaIIP3QY+JmrepXvPuP9RoxvA422UGnWKlGls4yWxe1x9li+Qlljq+WXmBrCStTxh9EC8rvIVFTi3qPKlSveY8kqUZ6ELBsMgvHJL99NloHJ2LX6XN9Xh3KsHEUhRWa1P475INJlFLELWIngppKqrnrQcKMbUx1KIcqMgqi9fJKDpJk6HEJ7Z8OQzul8flfhxTFg6Eop9qprmv5IYYF/+iWAZ7qCNyONo5Jo75vxQGbvg7PH9blfeSRy9LBY58jaNAF04bp4MmFw3CcKPzLp8GCk/fhJ1Me0dBWu0aajqGnhqj61uhVv+a0iKtpgnJVbt1Mb7FV+r2eibnTTfULYXyeqRa6d3ATvomRec61ylcUCpAdnNSDdIA2ROmpUrqJ/wLIjw/1StBzkeoaakKQJHCSsvXmJ/R3NxMqR+SMWBmrUFRJI2bSxxq6nHvHz75fw6GJ5+t33J+BofPoOzhYvYIO9XOtRmSM8lSgjQQZYqcPyYvFk/o2YwfJikT6ZD9yGnGEX79X+5KsYnT79loxOn34LRr92SP3foxVNwWvSLfJfMzogMDSfMfAHcVdy5o1duRjOcCNmS8am0QTnJhQdBWylly8azStHrdRezjNSGGj8MJvP5nJOu7bVJDfhska4H+PR8nxxAibEceEaKDrTcOyYjtbajhLFYdPqDULRNRvwuheU+FTDmlznwa2AsDTexBfuBoeeO0W3yFtHm9nd/vq/o/jWvrWXtQkxpAXn0abBdVSijF5pWsC1Znk9UHEW2EX4L8AloG0VX0hTglJbKBBWrrNVdKzlj2wDcloIvQuGHRkMufBI4SoMeNn4nVYHIqV+FCktdLlBW10/qpl9yLNsbbjuilnp2uyrEE5yiMl/otJPxzlEsqNZzMrYFenA1JXc0ZjgNGzvrensKzJbURxh/ya1CeKh3LZYwGT7j7OpsWnTstbE4V7KB3YZE2LWamOz8cG9+TyUxk/YtBCBIv8KfeN6OV4PZgJdELuXXYFkkTHM3kqXYqQ2vF4tkW5MKX1pSmukOXO0zqJR6lZpGM0S1ZgSbUDpaFPj9bqsEU5jnxpmqGDlWbbdbmc6vo1oo2vIfnnx/OLV8iI9nc1nNbdN7JMyqVttD4CHxfTN7bA+6jK72z3ov129xznC+JEz32hjZdxEHXbj3nGlPts7rhNVy2KSX6ndrtABf6Nmv5fHw9zIr65lqSGjC5kZV9f7ZBpltyvR8yH99FLi3+5AsqXvk8norCzR88HrOxvj0bq0eL28VMmwR+U71bpKfEhvZa3X27ge7fd/AnGon1Q=
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Reset Rassword"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/reset-password"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Allows an SDP user who has gone through the Forgot Password process to set their new password with a token sent via email.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./reset-password.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./reset-password.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/reset-password.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/reset-password.mdx
new file mode 100644
index 000000000..a12492905
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/reset-password.mdx
@@ -0,0 +1,5 @@
+---
+title: Reset Rassword
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml POST /reset-password"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/reset-user-password.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/reset-user-password.RequestSchema.json
deleted file mode 100644
index 54be59942..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/reset-user-password.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"application/json":{"schema":{"type":"object","required":["current_password","new_password"],"properties":{"current_password":{"type":"string"},"new_password":{"type":"string"}}},"example":{"current_password":"currentPassword123!","new_password":"newPassword123!"}}},"required":true}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/reset-user-password.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/reset-user-password.StatusCodes.json
deleted file mode 100644
index 4ae14ca21..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/reset-user-password.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"required":["message"],"type":"object","properties":{"message":{"type":"string"}},"title":"MessageResponse"},"example":{"message":"user password updated successfully"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/reset-user-password.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/reset-user-password.api.mdx
deleted file mode 100644
index 4c3ab0222..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/reset-user-password.api.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-id: reset-user-password
-title: "Reset Password"
-description: "Updates the password for the logged in user."
-sidebar_label: "Reset Password"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNV21v2zYQ/iscPzWAZDlp1gH6ljYZ2nVrvTjBPqRGQUlni7VEqkcyrmfovw9HSn5NnWZrgfmDJZH38jxH8u644lbMDE/v+Aj1VFbAJxEvwOQoGyu14im/bQphwTBbAmuEMQuNBZtq9AOVns2gYFIxZwAHPOK6ARSk+qbgKb8GA/bWAI46TR5xhM8OjH2piyVPVzzXyoKy9CqappK5104+GfK+4iYvoRb0ZpcN8JTr7BPktrMjEQpCnztEUPZjs3GjYLH5nES8QYJmJRjvdV9h48BYlGrG2z0ThwJtG3H4IuqmgodN9kM9+dOz5z/tI0vpc0fA292Qs+jAD5hGKxPQnw2H9NhdqPdvefTt0dyOXg3GiJlf+/0g70atF3wgFhG30lIg+B9B6LoDzHejtDbBacdsdpTz26xgxuU5GDN1VbWkULQRP3+I7UtRsOuwk55C+zg/QNR4yG7/SFyCFbIyTGTaWX8OgqJnalGYRz214UfcTg+53SrhbKlR/g3FDyf37aC5scK6bTnl6gw87yM7Y/+cdDj4O23ZDs8NjN7R+fB0y/S+xjqEzw9D+KvGTBYFqB8fv6/Q2yDocBrIHUq75Ondir8EgYAXzpY8vZu0k4h/iXNdwAxU3CXIONPFMlaiJmf0HkIEykitjLcyhyVPj2pG/F5Ubm2BHNVgS02JpxE2L4mmIBQ8aUIJSJCSdryVSg3gPWBw6bDiKfeGekJjCmCI0TatdaBEI9/C8uAUXXQr6VeDlSAKQEZrJaSSasaEYuPLEfvtrxv27Gp89vOLE6axG/3ILkZv2ByWVHK6EO3Y4xGX5CSYpR06vhqdDr8TMja+GsWnw4AtcGYrq+eg2pMnITo7/56Izs6/B6I/HeDy22B5UdYIFDXYryPaAuAh9Y4/k7qvHXQWrzd9wdXRqrrOynuFdJPQpJpqj74rSWMLVSWQXUqTOTRQg7JsVAk71VjTVqJzAmgCq18Gw8GQtr2ra4F0wm5KYMdtPBtfjk6YNEwwq3XFMicr69skjTOhuogbZjWrxRxY5qo5a8SSrPhRwWaoXcP0lCHkspF+Qt9DaLR67wrsQuN8cLAU/z+IH9QHdVNK410qphtQsdEOc2ANakqxzJbC0nSAohWz2pt/wFzEhCr8BCU7lgvFMmBT7VThFUv6qCq9oM2H0GgjrUYJJiUcMbszwV7SPeNiK0hx0wUpzkQ+B1VMnpXWNiZNkpm0pcsGua6TJ1k4SZknv4ay7E9HaKU7Mc9KqikKY9Hl1mFHsO+wj67p4AnMpujL4H+h1pt4jNsCMtbL/ms2JVR1nJcCrTkKeUsusQiQ1EKqpBs4yucxGq+hqpk35PEX0FR6SdvrUSbMGZJ76zJABRbM4AMlPQtYm/fTMeC9zCkv9bQ6mAONs8QLxXoam04s4pXMgTrpdLXO443IS2BnPk+Fkky20iRZLBYD4We9tU7VJL+/eXX1bnwVnw2Gg9LWlU+7jTa2FmrLsL+wsa3b2k6W2bqtPfVe2BUSC19s0lRCKsrTHvmqa0DueNeA+LvdTgsyiXipjSWZ1SoTBm6xalsaDiUkvZtQo4NSZJTv7yZt1Fe1TZv0KkCPbwjJpi86aAnbqNe4yHNo7FHZ7X5qdHHz6jWPQqdFVx1dkBKKBTESC+qb6IJsQ/+2CmMrXgk1c6HDDUZpacRBAZ77Aty9EK1+Si23IO5X+MCE/onXgyqrVSjvbbuWD1Nf1ehi20vTYk7atv0Hop6+/A==
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Reset Password"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/profile/reset-password"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates the password for the logged in user.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./reset-user-password.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./reset-user-password.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/reset-user-password.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/reset-user-password.mdx
new file mode 100644
index 000000000..da5549296
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/reset-user-password.mdx
@@ -0,0 +1,5 @@
+---
+title: Reset Password
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml PATCH /profile/reset-password"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement.ParamsDetails.json
deleted file mode 100644
index d083a4ef5..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"ID of the `Disbursement`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement.StatusCodes.json
deleted file mode 100644
index 91ecb041e..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Disbursement details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","example":"619da857-8725-4c58-933d-c120a458e0f5"},"name":{"type":"string","description":"The name of the disbursement","example":"Disbursement Name"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: {{.OrganizationName}} which is the Organization Name configured and {{.RegistrationLink}} which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"created_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"}},"title":"Wallet"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED","CANCELED"],"title":"DisbursementStatus"},"source_wallet_id":{"type":"string","description":"ID of the distribution account the disbursement is funded from.","example":"4c379f5e-09b5-4472-a286-b84e249a1512"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"status_history":{"type":"array","items":{"type":"object","properties":{"user_id":{"type":"string","example":"3f351b9e-ed0f-40fa-a314-14757b42dab1"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED","CANCELED"],"title":"DisbursementStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementStatusHistoryEntry"},"title":"DisbursementStatusHistory"},"file_name":{"type":"string","example":"disbursement-feb-03-2023.csv"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"total_payments":{"type":"integer","description":"Total number of payments","example":10},"total_payments_sent":{"type":"integer","description":"Total number of successful payments","example":8},"total_payments_failed":{"type":"integer","description":"Total number of failed payments","example":1},"total_payments_remaining":{"type":"integer","description":"Total number of remaining payments","example":1},"amount_disbursed":{"type":"string","description":"The total amount disbursed so far","example":"800.00"},"total_amount":{"type":"string","description":"The total amount to be disbursed","example":"1000.00"},"average_amount":{"type":"string","description":"The average amount per payment","example":"100.00"}},"title":"Disbursement"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Disbursement not found"}}},"example":{"error":"Not found","extras":{"status":404,"message":"Disbursement not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement.api.mdx
deleted file mode 100644
index 4731d0092..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: retrieve-a-disbursement
-title: "Retrieve a Disbursement"
-description: "Fetches information on a specific disbursement by  `id `."
-sidebar_label: "Retrieve a Disbursement"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWW1z2zgO/iscftl2xrJlW44Tf3NjZ5urm2Rjt51uN6NSEmRzI5FakkrW69F/vwElO3LsvLRN727uS15E4sEDEARIcEUNm2s6+EJHXAe50pCCMJpeNWgEOlQ8M1wKOqAnYMIFaMJFLFXK8CuRgjCiMwh5zEMS1QBIsCTkK4/I1yZtUJmBshKnER3QSzCKww0M6xppg2ZMsRQMKKSzooKlQAeUR7RBOTLImFnQ+7ROR0TGxCyAfK3DWbUK/sq5gogOjMqhQbVZJgipeZolQBsU/s4SGQEdxCzROCFcQMroYEXNMrMzjeJiToviCtF0JoUGjeMd18Vf21zqBEgEhvFE0wYNpTBo4WBFWZYlPLSuaP2pUWi1q1QGf0JoHaLQcYaXKnm0S+y+N2YLILngf+VAeATC8JiDWjso2nY3/M2sGwb0oH0UscNe3znsd3qOF/YOnaNuN3LCdsdlXu8Q3LhHi0a1Is/hgDOfVLvlrjPELtDLIfAbUL6COdemDBs/Ba3ZHHwDaZYw80wWYa6NTMlaiOQaImIk0SAiwsUNNxZd47e1Xt0kKPo1gpjliflKKtWEa/GLIQpMrgRETXIqrHXV8C+aVMtMuPlFk0xqzYMEEJpFkZ0ayySRt1zM7xjdMMVZkIAekNWqea7mTPB/LCn0R1GQ2wUPF4RrC1Aftw5DnTGf5woiwkSEGJc1t024uL6PkXBxTeYgcENChNt0OrrYOMVIO2ntDPKKCxIyDcQsuEYIIQ3JFGhr6JYHGqXhLDcSs0PIkmRJWJaBiJCdsXNBRK+bW0HwWeZkwW6AMJKxpQ2FW8YNeimWiixlTmIl0/3uaZLjhIfXD9htVxW/gmqWoVWLKFwtFhq/jKLdaAKRp5gVx++HpxPaoBdvz8/G/tmH92/Gl7RRfvaHZyP/03AyGc/84Wh0OZ5O783cN+OqQQ031vg66eOS0Ax5FA16y5IEzPdmhTv/9ljEjiDqOV6vxxyvf9hxmAvgtA/c/kEf3AiC9mN7+w7pIw8UE4YMtebaoMxCppCx+RNyC2MyPWi1bkp5lmXNUKYoryHz264fJhyE8SOZMi4ex2IZdyK4ae5iRQCZj8HtP5TEn+bU0lGG8IgXKsAN4jOzD6ksgXRAI2bAMTyFLfiO2+k6bt/ptmcdd9BzB16veeAd/o7AeRb9DODiLqo+laFTNCjT+iViKI4ZhF7QdbyDwHW8KPAc5oWecxB2e+6h2+v3XVsfQltLn8rMQyRF7Ny6kg/T0TGCcK1zUM+FKWdjilWg9Rbgr2/ejLz+6cnB5NO7/kX//Wj8cXr86bI/uvjw6WP37HN3NPtt/PFk4p0NZ97wt7fd3yeTk8mw90Kr33Hc7qyNKzTotV9q5XdBI0jgB0EPKtBeBVrsq6VTA0nCFLEhRTaBtI45uxp2Txtmcv1YRh1dDk9mtEEvx8PRZ9qg09nwcjYeYeYcfpjaP47P319MxuXH4+HZ8XgyHtXzZv3kMC0VomqZqxD8MnP6zzku3R0eI8zDPMhtaWVhKHNhdk4vWADj3NYzrEnbhcwLu/2juAeOexT0HM/rdxzWOTxwgkMPOt4Ra/faHWR5AwpPy2UVijkk+zff2lnD2dg/P/HfnF7O3tIG/TweXvrvz8/sPxenZ7RBz4az0/Oz4cQ/Ha3rU81VH2vqTqy2zSL5C66NVMuafqYUW+J520Cqn04cuQb1gKPvHNONu712cAQORG7seG7MHNZte07b6/f6gdeJWFmB/ouRgxtDG5ZmL7Yxi8dUvi39PhZGLelzZuKkmCfgP12l6/HqxBA4btdBis1Qv1Rd+w9lNiMNS/zqUFiPCy4MzEHtHvlRgIg8Dco7z0a0pq3t7iD7urqcfSO8zsMQtI7zZK+mw11FMeMJRN+hqhTcb9CuGgV4kELff7umjeyDyliKudFfx9kzL6WWIillNzk1IlqSmKmtcDh03abr3gVAKfMdWowkwV3+jraUtN2NFnYDCq+W36KnkllrykCt3XVfi1XywBanRYFDntvebSV8ECw3C6n4P5b5C7UQQCm552hVIGmj2DMy/k6SLkMHIap74L7uSVHU3LKhQc+kIVtm3rFY6/Hcdg35vsTPBC6Xpru7NCdSBTyKQPz8ddlv3R2BZ0wozfB2zUCLT2Qu/r/DK64s3BcAXj0AtppRYiP5k7EtvIYwV9wsbdfzDTAFapibBR18ucK+YwpmIbFvOoeyS4pDtFUv9Lq14lFBEUrdrPunuUrogFKEWGuY4kKWnq7ruTv+ZfwdLHevWtXGKBtPC2ARKNvuqkoFE7aJ9K9PM/JqPO30Dl4TqaqvPhlenJJrWOJpuWrpbuGtu7slLK70dHzRdl+IGZmOL5y2W3IrbSYrI69BFK+/iVHHe0lGHe8lGP2Wg1o+j5adSjYd9ocY1QhYSmvFf6G4TTfY/rfqqoK2vhduxfhFwgye+nDtqb3y6JJGv+k2XYzTPE0Z3jy27pb7MV5NRxev8erFiJEyIUHOE2Obg7LWELRN3JRdAwny5HpzerH9VzJXMs/K403IM24HJPY3TU27AHMr1XVzb8X/36L4h/hDzKqOLBNEZiCc8vZLMiUxsxKzYPa+WlKRghiZrS+79+AatneMA9iUISETeHCyOcoKbrWuFWRScyMVBz1AHg75oku8VvXb2bqDZJWTnICF1yCiq1fr5tucm0UelI23b0F4PSDW+A2V5TqcyxZ3Nc1axUWsmDYqD02uKgNxXcxTa9r8BstiZevnj5i2hnjKtlsIyHrud1uzgCR1wgVTRj9KuTavZRRAC+8GrerDo/Y8ZcZbSFJigSz/CLJELu3LyJN7Ldc4710egBJgQDf/wCxlQKX6PJ6CuuFhvcNb0WxKNW/ZSY6MHV1Na9CEhyC0Le3rxJuxcAGkY/NUWUMRa9Bq3d7eNpkdtWiVqG5NTo/HZ9Ox02m6zYVJE5snM6lNykQNeP3sSRi59/C5lW5Wd6exH3pzreqBgb9NK0uws15U9qyqM8SXrWYBXvQGPMJmyUJqg8OrVcA0fFBJUeDnsggMvlw16Prdyh40Iq7x72jzjPqgPa8uqxfZ1+Sxd9u91Nf1TWBxu2FJjv/RBr2GZflKXFzhk0RZIZFWOTAMQ8hMTWTngLt1xvp1jA0mtlNTr21Nrf5A9L107hftkgL+LBoPiKxWZcUuis38cuhBicrEjeVoQVEU/wb0UN3U
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Disbursement"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/disbursements/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches information on a specific disbursement by  `id `.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./retrieve-a-disbursement.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retrieve-a-disbursement.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retrieve-a-disbursement.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement.mdx
new file mode 100644
index 000000000..c9a530fb0
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement.mdx
@@ -0,0 +1,5 @@
+---
+title: Retrieve a Disbursement
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /disbursements/{id}"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment.ParamsDetails.json
deleted file mode 100644
index af9f67731..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"ID of the `Payment`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment.StatusCodes.json
deleted file mode 100644
index 1d7843a83..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Payment details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"ddf22f55-3259-4822-a4e2-ce01334997f4"},"amount":{"type":"string","description":"The amount of the payment","example":"100.00"},"stellar_transaction_id":{"type":"string","description":"The ID of the transaction in the Stellar network. It can be used to track the payment in the Stellar network using [Stellar Laboratory](https://laboratory.stellar.org), or [StellarExpert](https://stellar.expert).","example":"0b339d1c89d314186b8147c2af4c9a9ed5bbdbcd7ada8d138633907649b"},"circle_transaction_id":{"type":"string","description":"The Circle transaction ID. It is only present when the payment was made using Circle.","example":"74a68b6a-3f67-424b-b8b0-e593a19d7463"},"circle_transaction_type":{"type":"string","enum":["PAYOUT","TRANSFER"],"description":"Which Circle API the payment went through. It is only present when the payment was made using Circle.","example":"TRANSFER"},"stellar_operation_id":{"type":"string"},"source_wallet_id":{"type":"string","description":"ID of the distribution account the payment was sent from.","example":"4c379f5e-09b5-4472-a286-b84e249a1512"},"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_history":{"type":"array","description":"An aggregated list of metadata objects containing the statuses and the timestamp of when these status changes occurred.","items":{"type":"object","properties":{"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_message":{"type":"string"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"PaymentStatusHistoryEntry"},"title":"PaymentStatusHistory"},"type":{"type":"string","description":"The type of the payment.","enum":["DISBURSEMENT","DIRECT"]},"disbursement":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","format":"uuid","example":"c51ba1d5-52d3-412f-a59c-6ef32d59ab43"},"name":{"type":"string","description":"The name of the disbursement","example":"disbursement-june-29"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: `{{.OrganizationName}}` which is the Organization Name configured and `{{.RegistrationLink}}` which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED","CANCELED"],"title":"DisbursementStatus"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"status_history":{"type":"array","items":{"type":"object","properties":{"user_id":{"type":"string","example":"3f351b9e-ed0f-40fa-a314-14757b42dab1"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED","CANCELED"],"title":"DisbursementStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementStatusHistoryEntry"},"title":"DisbursementStatusHistory"},"file_name":{"type":"string","example":"disbursement-feb-03-2023.csv"},"created_at":{"type":"string","description":"The creation timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:57.831975Z"},"updated_at":{"type":"string","description":"The last update timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:58.316511Z"}},"title":"DisbursementLite"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"receiver_wallet":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"enabled":{"type":"boolean","example":true},"user_managed":{"type":"boolean","example":false}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"sep24_transaction_id":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invitation_sent_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}},"otp_confirmed_at":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"},"otp_confirmed_with":{"type":"string"}},"title":"ReceiverWalletLite"},"external_payment_id":{"type":"string","description":"Optional external payment identifier provided by the client.","example":"payment-001"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"Payment"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Payment not found"}}},"example":{"error":"Not found","extras":{"status":404,"message":"Payment not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment.api.mdx
deleted file mode 100644
index ab1c0832f..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: retrieve-a-payment
-title: "Retrieve a Payment"
-description: "Fetches detailed information on a specific payment by  `id `."
-sidebar_label: "Retrieve a Payment"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWm132rgS/is6+rLtOZj4jddvNJCWlpAUSLPdbg+VrTFo47eV5GTZHP77PZJtMAGStM2ee/d+aYk9Gj0zIz8zGukeS7IQuPsFX5JVBLEU+GsNUxA+Z6lkSYy7+AykvwSBKEjCQqCIxUHCI6JeoyRGBIkUfBYwH6W5EuStEPrGKPpWxzWcpMC18JDiLp6A5AxuoVdMiGs4JZxEIIErIPc4JhHgLmYU1zBTAFIil/ghqmEfJQGSS0DfCk16Mg5/ZowDxV3JM6hhIVeh0iZYlIaAaxj+SsOEAu4GJBRKwF9CRHD3HstVqiUlZ/ECr9dflTaRJrEAod7bpqn+24VRzF04R+Aa9pNYKru695ikach8bfvJH0LJ3+/Pl3h/gK/dwJWnJMtnY3Qfk0JPtB1dTGlg20GjYTh2o2O4bds2iAu24YNpOY7b6bQCF69rmERJlqN5qGvXkNkSUC5b+jXdBGg7q2WaddNUeoWEMCR8LjmJBfGVlvlhzPvzbGNXGY1YrB9Nc8UoBnmX8Js6Gkrkkxh5gDIBFMlEjfJvqhiPjEWZYPECfSkfj4iXcCITvvr6aillKronJ+HmWb0wqZ7wxesaSvhm4OAvFZjtmFIQ9PPX9R0XmZ7jdKjltzvUsVyr3fTaltvybRK4fod0gDY8j3o+bRFK2tRy2k3H6ZitptvxlF99xv0Qfsitp3rojk+Hfe0/JlAShyuUchDKXXdLiHf8d0cEigiFwmO5pl27Wi5ptr0mMZyg2TJc2/UMr+2ZBjQ6DrE6tOU2nSMG5NAPrOY4izT39D5fXM1wDc8mvfH0bDDZJ6HrJfOXpYW9y+EuevWPXPIkWyxfzN4Nlspi31DZwZgowSTjPszvSBiCfFbgtt8CZUrEy3TgiO/rb/EhaG1OwJNoF6zrO61O0ADD7HgNw3VbtkHsdtPw2i7YbodYDcvODSEyE89bTrnsATYootaf9M5U0CaDXv8zruHLwbg/HL9Vv3pX00Ef1/D06vR0MJ3iGj7rDUf60WlvfDpQP7/WsGRSoy9IdJqD28CcL5lQH2YFLuGcrPbQ9mJEFgsOCyKBopAJzWERSEKJJChnWIEUMxMWq4DLjX0gEIlpTkYsAiFJlKrR5ZIRG0f4SxIvQKDE9zPOgaoIMAmReJrM/11uj0AIsjjwxa7V2MJHh4zJywKVnIgEQ4nuLFLbtB3DtA3TmVlm1210G9ZveL0+AuhdHvxBLPkKPyGk3x8hmX0PK4kH/q1XHTycvrmaTAfng7Hyc384GZzO8Nd1DVMmvIwLiGAno35XBt+Hk8XszwwQoxBLFjDgFULYTlfxbpbp2mjrWL9hecSiDaNhU8dwLTswSKPjG00IHJs2OsRzNTXnldVzMCnJIzAqJUjlhfFHFoNhd9Q0HHxgt8DnHBaK03LGLFbVXEKUhkQ+E4ifCZlEqBy0KQEExKoQvWVSaxfqWTmvqCM19BuFgGSh/IaKqRET8S8ScZAZj4HW0TBPCsXrX3KG0OWE/EWgNBGCeSqhJojQnCKCJAyTO80gJaJbwhnxQhBd9O3+vn7BFyRmf2tUYxLBev0N3enkxYRWURVASkLNGrBFxoFqKlJaJhXPjVh8s6clZPENWkCs8hFQVXBP+5cbx6gaaQkbh6BXLEY+EYDkkgmlIk7kJjmyHS/UcuNJJhNV4vskDFeIpCnEVOHLMxLE9EHV8znJ0JLcAiKVdMWk8lSQcLRKMp210EEP1dFpyPwbdNDwPLLqKfB6vrwqq0pzui+fLDEG573hSHHku4vxYD6+On8zmOBa/njeG/fn173RaDCb9/r9SU6dVclDEhUirYI+zQHNFI5HE+4xPp/OepOZ5uwNn59enF+OBrOjRN6vfIhbNr8FrjZluZ8CBuHhHUUJozcbzC/O5m+Gk9k7XMOfB73J/PxirP+4HI5xDY97s+HFuDeaD/ulBysgPlWmO9OzPSeRPzOBZgL4kXJquwadwGlYXgcMoGZguGZADOJYrmG5rUbLc21KPOu/HJN/NH3uT3kshx6VVEIBC2F+LFUcYf8APMN0DAWx7otbvQ/goKhpTp65+dTyihN3yrDH8uBjbmoajjkzra5tdxutetuxOq3GbwpWltLvghUSIVE+6OWRteuO1WxYj8RxxKTmESIE/HDNsYUQBAR813MMt+mZhks91yCu7xpN32mYbbPRapkNHTzdInnKPz0FCmnZ6iRX0/6pUsKEyIA/V00urTItByF2FL5986bvtoZnzdH1h9Zl67w/+DQ9vZ60+pdX15+c8WenP/s4+HQ2cse9mdv7+M75bTQ6G/UaTy/DH/rknlpEP6iUQgg/qbRZKG1syWF/RZfdEL2k0GYhlatPR2OnjMt3sz+/+NqmYzoWdQ2Lmq7htlsdw2vSjkH9RtO1gk6n3YbqxD8/o2l3wAZqKn5qGq7vmkbbc1uG2XaapN1ouRaxdz69STF1+dm9lOkNQnXrx3AbDWK4rbZtEBPAsJpmq9kCk0Kemp6m3U/M4ySWqCcEEzpOyySC9OB+rTqu7F3d5uNJmtb9JNLpENK5Zc79kEEs5zSJCIsf10VSZlC4re/rogDpXNWm82N91acxnQiaKvVKH8SqtK4610uSEEhc1aM6veqjVDVCRGKyeGqAbv1Ww36tw1wGvez2lFT0qA1vT3/tvXd+fe98+uC8P3vnfDzvn11MP5zb4/Pz395ML5xPw1lzcHX58Xrav7bft9xz25lMpqPqRBFEyeF2UkXgSImbB9B2n+wYPsmFjzJU3TTNZ1Df83Rs921ztQN5vq7Ovq7vL+Ymg7fD6Www0aXb2aj39u1u5VZygMhXxXd0pX66G/TikF+i3rTMI/XmwVl3S851DScynesdLo9+NmPuInmo+o7J5aFznH3Au587/CWBxyScFxvXZ7VtL/QPEqJy9PYoYtvHSXlyy2i+PVflYk6xuxvnYphhmta/qVzZb8jh9Vo9dU1r/5TsKiaZXCac/Q305Y7IgPPkQHmZh5STH/kS4yzygCsVx5ug2syNfzYw8DiRaMfMLYpyHte0KpofjvgnFeehcfZDc5Zwj1EK8T8fl8PWbQE8QyA3w903Q1l8lmTx//fyCgoLDy0At7oAymPpeDPon1OrNQvwM87kSp/gvwHCgfcyxcdfvqqD9AjkMlHH/wvIT/zVK3xSkJ84uWd0jZUWflteA8h4iLsYq9Gl8qmKXO7a6hTbPJyyD3DgeKj4EvL2whIIBV49DCKxbp6+v56hV4Op3Wi+Voe/+dO5Pmy8gZVi7eJmwo6+8pJCrlaFdjq4tMwXQoamg0vDMnNsuc3oXiY3EK9ffxci231JRLb7Eog+ZsBXz4OlRdHmosgxRBUAGlI58Z9quOYXdXdFT1ckr3IzXO25oMuQSJUVVeyxbqSKHEarbtZNtU6zKCKqBNzZUB/W8Wrav3yteu4EySQJkZexUOqmeFJphOsDjIjcAPKy8KYsJvRTghY8yXTPiYPPUqZfJKqvf+i+xMEu1v8WxN/j3+NZcRJBYpSkEBv5ybkqmRSVIrkk+hg/h6K6gsmm6/ZAXW1zgKs6UeVdEU1PeuDOsQ2HNBFMJpyB6CocBvpS7LLKax3GTmczLZxkeMS/gZhub4EsmFxmXr5j/R4Nr7tIG7+BsiqXc360U4hpq1gccCIkz3yZ8cJAFRf5VEzr32FZwHXC/BnTShVP2XYHHiplf9iaJYSR4S8Jl+JRyBW5E8kBTlRn46R48Kg9T5nxDsIIaUUaP4U0TFblvYLHv7X8wsmHzAMegwRR/12xlAQeiYtgCvyW+dXWSOVO0okWMpLAEIVYDYfMh1johF4Sb0r8JSBb81SeQ5Wu7snJ3d1dnei3WlsxVJyMhqeD8XRg2HWzvpRRqHkyTYSMSFxRXF7cQwRtr+7tMM39tvL66UuDRTqQ8Jc8SUPVkVoX5twX1cOXcuukesVdRtV+eJkIqd7c33tEwBUP12v1OKf/7pevNVye1uoSgzJRtJeKy4BHzXk1Ke4VvkZHLh4eBFwmtVhltFsSZuovXMM3sMpvOK7VtYIiLSpE+Yue70MqK0P2ytidmurtQPUKyF4ivdGJtPihtB+E8zBT5xDUv+vakSH393maXq838vmroyMKEzeWKwvW6/V/ADJlWvY=
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Payment"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/payments/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches detailed information on a specific payment by  `id `.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./retrieve-a-payment.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retrieve-a-payment.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retrieve-a-payment.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment.mdx
new file mode 100644
index 000000000..50974107c
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment.mdx
@@ -0,0 +1,5 @@
+---
+title: Retrieve a Payment
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /payments/{id}"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver.ParamsDetails.json
deleted file mode 100644
index de64631b5..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"ID of the `Receiver`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver.StatusCodes.json
deleted file mode 100644
index 29abe7066..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Receiver Details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"f83bb638-dda4-41e6-80c9-d03e6eec2aef"},"phone_number":{"type":"string","example":"+15552368475"},"external_id":{"type":"string","example":"usr12334"},"email":{"type":"string","example":"jdoe@mail.org"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"successful_payments":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"canceled_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"registered_wallets":{"type":"string","example":"1"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"wallets":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"enabled":{"type":"boolean","example":true},"user_managed":{"type":"boolean","example":false}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invited_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"last_message_sent_at":{"type":"string","description":"timestamp when the receiver last received an invitation about this wallet","example":"2023-02-10T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"payments_received":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"canceled_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}}},"title":"ReceiverWallet"}}},"title":"Receiver"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver.api.mdx
deleted file mode 100644
index c33a4fc7f..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: retrieve-a-receiver
-title: "Retrieve a Receiver"
-description: "Fetches detailed information on a specific receiver by  `id `, including all associated wallets."
-sidebar_label: "Retrieve a Receiver"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWVlz2zgS/isoPCU1okRJ1GE9jRLJjhM7cSwfM3FcCki0RMQkwAFAO1oV//tW83BkS7bixDO1u7Uvlkn08XWj0d1oLqllc0MHF/QYAhDXoA29rFEOJtAisUJJOqC7YIMQDOFgmYiAEyFnSscMl4mShBGTQCBmIiC6lEL8BSFfBCdfakTIIEq5kHPCoogwY1QgmAVOblgUgTV1WqMqAZ3L2+d0QI/BagHXMKxA0RpNmGYxWAQ4uFhSyWKgAyo4rVGBIBNmQ3of+f6IqBmxIZAvlagvqE7DX6nQwOnA6hRq1NhFhOKMiJMIaI3CtyRSHOhgxiKDBEEIMaODJbWLJKe0Wsg5zbJLlGYSJQ0YXG+5Lv7cxVEpJ6PchYbWaKCkBWmRliVJJILc/MZXgwzLdYXK/wqBRUdodJYVhTrB10EhfJYbMqCzftv3u+2+wznzHK8JXafvBjsOd9vQBQhaDGY0q9EkVBKmMo190I9L/K3Z6XRa7W7f63WQE75Z0JJF021QUqObrXbby5liJqLHyb9yBb8jWV3pOfIEGjBspsw+zthyW23HbTlu+6TpDrzOoNOsu677CWVYZVk0TdgiBmnNFjnIYNIgAGNm6ZO4Zvk5+UEONzeOyQCeyKPRi1LI+dOY5sJY0MCn5fl7nKlZMOXxy6csVuldPUxrtsBDaCE22+OVGQN2GuRn6zG1p5PRa9Rc0Atj0m1xuffq1cjr7e92D87f9Y56h6Px2eT1+XFvdHR6ftZ+/2d7dPJxfLZ74L0fnnjDj2/anw4Odg+GnQ32bfGI69Zdl2YYTsLmr4YFG75ad+oTPbTtGPXdtttucs9pctdzvH5vx/G7fMfhQafrNWc7O/0+rNikf12j29qBFnDXmYHfdbzAc52+7/Uct9/usn6n5zVZ6447qnR3IGwOpfDJrwPpMM52gHccr9NhjtfrtxzmAjjNrtvr9sDl4OfhWhSHxySdCV8zacnQGGEs8oQqhoTNt/CF1iZm0GhcF/wsSeqBivNEAcm06U6DSIC0U67waD4uiyXC4XBdX5fFAZJpJOTV9KG6sx1Tw/AExefZVjI/glXn+kpFwOSqHKyEWY2mBvQ0ZpLNtzHkpXF128/zba423ViIIqanjHMNZkuW2Xv9x/Bt+4+37bN37be7b9ofD0e7HybvDlvvDw8/vZp8aJ/tn3THp0cfzyej89bbnnfYah8fTw5WFcUQqw0V+i7BtFjdQPUc5SVN+C/LEPJaPEnGzrqMiBk7jcEYNoepwYDcLO1ul2JFDMayOCE3Ici8bbrt51Bi9cQJkySHWbSAzFepJTYUpmzpNuJsus9QjivSaQXlv70Y/7+u/mBdNZbZdLNPZRrjDWZ0PNw9oTV6PB6O/sx/9/YnJ+Pj8YjW6O7BcG9vPMLLzf0qZYq8NSkU3KqahsJYpRc/vyf/IOTbo7tJW3FZowOKyclB0m0H9NPGcn5H65vCO2Np9YJmm8gL6s1r+DarUc9trl+WTiVLbai0+Bfw57sogdZqQ6QXFxjNfmY7y9tSVqNlqt10P8yyFV/fwqDvlSV3zPyOotLjuc0Vyfc5/k7Bxda017dmV2lfcA7y79+XzdZ9B/ADBIUZ3roZaPGuSuX/RHg9HAaz0sRNEeCtRsAxGJXqAIi85cpK0QaCVAu7yIcur4Bp0MPUhnRwcYmjjxhsqHBkM8+rfj6EGdBG1TaYxlLwjKIYfV2NblId0QGlyF5Jn6CXCzes6vieeBPxDhZrDcuwjNqiDQmBcdAEN7SoxNimTEZH5O35CXkxnrQ63ZdE6fLtlAyP9skVLHAeVE6T7sirBkuFWNyGyfio6T4TMjIZHzlNt8BW2EyWVl2BzF4+CVHLe05ELe85EH1MQS9+DFZOSm6Hew8hWgGQQ6oU/4XseS7AmWSurqw0k6LpJyNh/FQbwJaMHEXMYjXEvac1iiFZwOjV3bqLcZrGMcOaT09CII/LeDEZHb0kwhBGrFIR8VMR4fHRROk5k6WLDLGKxOwKiJ9GV6RqDvEtI3Ot0gRHlBoCkYh8QWG7bVe0S7A3Sl/V13z3nwfxs/wsT/AegColUQlIp0wtiVaY9ogNmcXlAoqSxKqkGtLeE1cjTPJ8AftaEjBJfCjyU84Y4kMUqRuMFg2JMsIqLcAMEIdDLsqLX6P8dfiKk5ykdJLjs+AKJL98UV2k58KGqV9cop8i4eWA5MbfQllU4WxysCVZbpWQM82M1WlgU10aiPtit+1p/QmWzXRe3H7FtErENttuwCcV7U9bE0IUO0HItDWPQl6ha1gN0MCrV6N88ag928x4A1FMckE5fg5JpBYYXlstIalBunepD1qCBVP/jFnKgo7Nh9kE9LUIVqc1JUwcbjdyIkfNHFOS1WgkApAmL+lV4k1YEAJp5XmqqKEoa9Bo3Nzc1Fm+mksrWU3jYP/1+P1k7LTqbj20cZTnyUQZGzO5Irj62kIYWfnecifVLL+3Sf/E16CyZFj4ZhtJhIO0rDR5WbYYF7fjTfyWMhAcb0mhMhaXlkufGTjVUZbh66JGDC4ua/SaaYGjsLwP4cKUY7HyI8+DJr84Lr8XvSQPfVHaCLkqfRLr3jWLUnyiNXoFi+LbVXaJk8eieCKkYmEYBJDYFZa1xvRO67U3xiskWyu3V3m5Lf9B6Rvh3K/nBQT8m9UeYFkui2KeZbf0xdKDHKWJt5ajBVmW/RtWTbHy
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Receiver"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/receivers/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches detailed information on a specific receiver by  `id `, including all associated wallets.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./retrieve-a-receiver.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retrieve-a-receiver.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retrieve-a-receiver.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver.mdx
new file mode 100644
index 000000000..0aa7e92ca
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver.mdx
@@ -0,0 +1,5 @@
+---
+title: Retrieve a Receiver
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /receivers/{id}"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant.ParamsDetails.json
deleted file mode 100644
index 73ceaa98d..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"ID or Name of the `Tenant`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant.StatusCodes.json
deleted file mode 100644
index 7dd590df7..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Tenant details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"name":{"type":"string","description":"The tenant name. It should match the pattern `^[a-z-]+$`.","example":"bluecorp"},"base_url":{"type":"string","description":"The SDP backend server's base URL.","example":"https://bluecorp-backend.sdp.org"},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL.","example":"https://bluecorp.sdp.org"},"status":{"type":"string","enum":["TENANT_CREATED","TENANT_PROVISIONED","TENANT_ACTIVATED","TENANT_DEACTIVATED"]},"distribution_account_address":{"type":"string","description":"The Stellar account address used for distributing funds.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"distribution_account_type":{"type":"string","description":"The Stellar account type used for distributing funds.","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"distribution_account_status":{"type":"string","description":"The status of the distribution account used for distributing funds.","enum":["ACTIVE","PENDING_USER_ACTIVATION"]},"is_default":{"type":"boolean","description":"Boolean flag that shows whether the tenant is the default or not.","default":false},"created_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"deleted_at":{"type":"string","description":"The timestamp when the tenant was (soft) deleted.","format":"date-time","example":"2024-03-27T17:21:51Z"}},"required":["base_url","created_at","distribution_account_address","distribution_account_status","distribution_account_type","id","is_default","name","sdp_ui_base_url","status","updated_at"],"example":{"id":"840dca45-d1df-44cd-83c1-65c04235c25f","name":"redcorp","base_url":"https://redcorp-backend.sdp.org","sdp_ui_base_url":"https://redcorp.sdp.org","status":"TENANT_PROVISIONED","distribution_account":"GCQVDMPOEN3HHJJ64V42KUTONOXN7C6V2PSVPALEVJ7PIYOB6M3DJV7N","is_default":true,"created_at":"2024-03-27T17:21:51.000Z","updated_at":"2024-03-27T17:21:51.000Z"},"title":"Tenant"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant.api.mdx
deleted file mode 100644
index 925559bd6..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: retrieve-a-tenant
-title: "Retrieve a Tenant"
-description: "Retrieve a Tenant"
-sidebar_label: "Retrieve a Tenant"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWGtz27oR/SsYTGdqT0mKetjK5TfZUhLJtqTolTSOq0DkUsQ1CfACoH11PfrvHYCkLFmynaTuTKefZIOL3bMPnt3lA1ZkKbF3jVtBQhm+sTBPQRBFOesG2MMjUILCHbQmwAhT2MIpESQBBUJfe8CMJIA9TANsYcqwh1OiImzhAKQvaKoVYQ9324gL1CcJIB4iFQH6niv87mALC/gjowIC7CmRgYWlWsVaqaRJGgO2MPyZxjwA7IUkllrAjyAh2HvAapUaSSUoW+L1+kZrkylnEqR+XnNd/bOLJjeNAlCExhJb2OdMAVNakqRpTH0TgMrvUos/7Jvji9/BN8EQOlyK5sZosA9JgyfGDQ9Xm/XTBQR1u7n4rWY3mqeu/S4Ma/ZJNVy47wDc5m8hXltFTPc1PfEiAqRyT/QFB3UVkhHP4gAlRPmRCXNKlALB0Pd/XRP7L/vmH38zEX/EtIgz8LlItd0FkTDPRPxjtsftIVoQ/xZYgCSIOxB/l0irQNPR5a6RSKlUepVKacwu7jkySB0ultq4DNJ5Ruc/j2HarQRERgtORIDOfsj+jl1FVCYPJo5liX41Jp1+qz+Zn486rUmnja3yYDgazLrj7qC/fdg6n3Rnu3LtzuPhzdrCAdUmFpn2Y058n2dMzUkQCJAHcRxwW0EcE4GKy6i4jDIJAQq5QI8m2BKFGQvkbkA+nH9p9epfevXZRb33/mP901X7/WB8cVXrX119PRsP6rPu5LQzHX76PG5/rvWajatafTQaX+Ln4OeYfwW7vvEq8CIT7e54MuqeTSfdQX/eOj8fTPsTZzzpXF62Rk6nP8PWyyLts/msNb2cPCd33h2dX3YexZ7N1vNFs+9wLlvy3ra6TQx+0H1TRh1s4WGn3+72P8yn486orLjuoG/wUjkPICRZrLbgLTiPgbA9fGf5OQpjskQqIoZB7iW6j0BFIAzigmOozPHnujWdM64co7GwZsh5bWFfAFEQzIk6FKCQi0Q/wQFRYCuawE5l1txaw3brdq05qTa9WtU7qX7VVZelwdsrDSCG55UeoFuagFQkSXWA2HZ07olER5KH6hgVSp1fhbXebojXj6S8E9hXWOTlsn3pHbaKVv5YRUU/2mfoDXfuZOdmy8O8JeJ3DTfwSePEDqpBaDcafmC/q/tV+/TEdxu1+olfOwlLMx4WEJiGtN2PNgxePNxrIAf6x9M727LF63uYyQ8Fx3Dmp1n7ajjo9OsfP/Z6p41Zo3YxnQz6gy/95vnprDYcz4aty86s1xx2/zk4O72qt3uzZn83msWIs/2OHKoDx3Xdr7uBfUFubWFFlampYk5br3UdNdzq/vQzZSRTERf0LwjebvYBIbg4MJHpalCCyNc17HEqy5IFCK0iASnJ8kCDyd3cqrcCBu5zhXbcfERR2mm41S3NT2/8NxXnqWnsp0aLvucZ+7/Iy/PxCwsXD4WusR26EUieCR90qylurQvVEvxMULUyS8gZkdRvZSrC3vWN3gF2w1ouMYigzRqTgIq4Jqcl5FuNvowrOZ3LygMN1poozFybbzo5qWCtvjQ+1knIo3QGRIDIMWyiQVJ6Aau9VtIqqsFkFEVAAhBI55tQphs/YWaw7X2eoKPOuHZyeqzbbX46R61hF93CynlkzB195R6Wq9VZGneGVfeNkKFxZ2hX3Rxb7jN6UPwW2Pr4pxDVGm+JqNZ4C0SfMhCrH4NlRNFmF34O0RYAA6k0/Ie+blo9ZSE35gr+LsfjNpWLTEhIgCk0jInSs4TOPbawLskcRtNxHVfXaZYkRKyejNiHdRyN28NjPc4RpDiP0SKjsTLTJxdLwooQSaQ4SsgtoEUW36KUrLQWc0rQUvAs1ROtAJ+m1Dzgd8W8WFpnoO65uHVe3AL+NyB+Y9/YJKLSmGSIp8DsgnlSwTUr5sMxlQUUzpDiaTnTP1FnIcIC88DnASCfMLSAnL7MxUj/E8f8XleLgJRLqrigID2Nw0bXMtdXKX7tYCtIdloEqRyBbo7KOWdJVZQtHJ8nlZ/ScOwh4/wGyqos53zkL5d87RVloSBSicxXmSgc1HlRr+XU+QnPQmF633/iWqniNd/uYYFK2V/2JoI4sf2ICCVfhLwlV1ECoJIQyirFwYv+vObGR4gTZBTlaySkMV/p8nrVE5RJLXeRLUAwUCCdb5qlFIhEDsIxiDvqb39CKWDqQbpihGwe2rIQs3BMfWDSdPySeFPiR4BqhqceB3OvUrm/v3eIeWq0FVdl5bJ73umPO3bNcZ1IJbHhyZRLlRC2pfhQV98hmg2HK/hTVdKYUGY2yfzjUt7xr3HR8bGFPRro7SXiUukHDw96l5iKeL3Wxzlle9c3Fr4jgpKFpuvrB70t6L+DzcfJJxg2cxw+GhVr3TF6+XvoQdhlP2K6Gd2RONP/YQvfwir//rrW23/R0TSw/EHL9yFVW1f2hkk90GymoQ+dCV6v/w2fAoz7
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Tenant"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/tenants/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Retrieve a Tenant
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./retrieve-a-tenant.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retrieve-a-tenant.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retrieve-a-tenant.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant.mdx
new file mode 100644
index 000000000..63a0eeec9
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant.mdx
@@ -0,0 +1,5 @@
+---
+title: Retrieve a Tenant
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /tenants/{id}"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics.ParamsDetails.json
deleted file mode 100644
index a13174600..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"X-Wallet-Id","in":"header","required":false,"description":"Optional. Narrows the statistics to a single distribution account. Naming an account outside your access returns 404 rather than disclosing that it exists. Omit it to cover every account you have access to.\n","schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics.StatusCodes.json
deleted file mode 100644
index 969c8e1b2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"General Statistics response","content":{"application/json":{"schema":{"type":"object","properties":{"total_disbursements":{"type":"integer","description":"Total number of disbursements","format":"int64","example":20},"payment_counters":{"type":"object","properties":{"canceled":{"type":"integer","format":"int64"},"draft":{"type":"integer","format":"int64","example":1},"ready":{"type":"integer","format":"int64","example":2},"pending":{"type":"integer","format":"int64","example":3},"paused":{"type":"integer","format":"int64","example":1},"success":{"type":"integer","format":"int64","example":5},"failed":{"type":"integer","format":"int64","example":1},"total":{"type":"integer","format":"int64","example":14}},"title":"PaymentCounters"},"payment_amounts_by_asset":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","description":"Issuer of the asset. Empty for the native asset.","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"payment_amounts":{"type":"object","properties":{"canceled":{"type":"string"},"draft":{"type":"string","example":"100.00"},"ready":{"type":"string","example":"200.00"},"pending":{"type":"string","example":"300.00"},"paused":{"type":"string","example":"100.00"},"success":{"type":"string","example":"500.00"},"failed":{"type":"string","example":"100.00"},"average":{"type":"string","example":"100.00"},"total":{"type":"string","example":"1400.00"}},"title":"PaymentAmounts"}},"title":"PaymentAmountsByAsset"}},"receiver_wallets_counters":{"type":"object","properties":{"draft":{"type":"integer","format":"int64","example":1},"ready":{"type":"integer","format":"int64","example":1},"registered":{"type":"integer","format":"int64","example":1},"flagged":{"type":"integer","format":"int64","example":1},"total":{"type":"integer","format":"int64","example":4}},"title":"ReceiverWalletsCounters"},"total_receivers":{"type":"integer","description":"Total number of receivers","format":"int64","example":1000}},"title":"GeneralStatistics"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"404":{"description":"Distribution account not found, or outside the caller's access","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"distribution wallet not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics.api.mdx
deleted file mode 100644
index 641af3d13..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: retrieve-all-statistics
-title: "Retrieve All Statistics"
-description: "Fetches all metrics on all disbursements the organization has created. The response includes basic aggregations on payments, receivers, receiver wallets, and assets."
-sidebar_label: "Retrieve All Statistics"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWG1z2zYM/is8fll7J9uK4zZ3/ubWbpc1S906bbaluRwtwRYXilRJyKnm03/fgZId+aV56brdti+JRQLggxeCAJYcxdzx/gWfoEDpUEaOXwY8BhdZmaE0mvf5K8AoAceEUiwFtDJyzGj/GUs3za2DFDQ6hgkwY+dCyz8E8bJEOBZZEAhxm50lwCy4zGgHTOpI5TE4NhVORkzM5xbmnsnLzkThRQbMQgRyAbbxk90IpYA2hY6ZcA7QtXnATQbWiziOeZ+/J6SwgIFSDeUCngkrUkCwpPeSa5EC7/NfWudeaOs45gGXpHYCIgbLA27hcy4txLw/E8rBtnne+h9CtdmpsNbcVHZw6zMZGiaYk3qugAyGVk5zbx4RRSbXSIyp1HMm1kvM5OhkDKwwuaVFcI5ZwNxqx3phj1mBCViGidAkM1KGDqBvZBIZfJEOXZu9TaX/RsMiQ6aDBdhifUphcpaIBaxOQNP+pHnAXZRAKnh/ybHIyDwEWs95WV6SOSofOtrvhiH927TIa9BghWK3dl87ngc8MhpBI7GJLFMy8j7r/O6Id7l7tpn+DhGS5yx5GGV1MhoU6mojABtMUiPMvfc2oZ0RF9N5OgXLzGwzgHnAZ8amAisBz3s84PBFpJkC3u+GJQWPj8srbz4fQvfBjISOQFHw7MG2dVoZ8NiKGT6EtoHsoCSniLh4JF+XFAIdk2cfx3noTZG7h6m1BdXlPtgeyfmsDPhMyAdacutIHyuP5euVxCmRPvi4cvzLld8bsSBSWnRX0+LK56LGOcJaUVA+QUgfECue/SoyMexevQYy/mEyfEkIKnrpXA52H8dm6B97Ogp6yk+et81GaYYFmxnrF7VAuVjtbRz5+sWLYe/o+NXzk/M3R+Ojn4ejj5OX5++PhuMP5x8PT389HJ69G318ddI7HZz1Bu9+PPzt5OTVyeDZHkN9051ZJaDdG7LHPgdh2A5Dvuda7CHurol378Ie8sNb8u0LcCeS3ajfQ/5sTb4T6ncKFwuwYn5P1NySb1+HfcS9mnr3DgxqN35960Ux8Beh9B6oHu2r+tF+ROr8J3NhxTeXDsF+U4qZKTGf/2PJaSM3va9NXFUwrpmjqkdyXUN9wwN5y3unHmEYNiHVFUCj8CpL2u+FB7vlwgctckyMlX9A/P3qA7DW7MmKJaFGKx4Qf1TC5U26yiokIgXn9l64Ss21XdYw+KlBtqHmLYrVOb3woCF5m+PvFFy5prfrmuGecpVpg2xmch0HzNh1pUrvR0QRaH9wdT359ztzv0k2iuwq79yCrvSljAxRbiUWvg14AcKCHeSY8P7FJZW5KWBiqJGYg8cjaIt3XLOXcGAXq0Yit4r3OSfWleQJaVcp0JR/Wx5k8g0UO1dwUPum7qF8G8LIkELquk2YDMfsp/Mz9mQ06T57/pT8UK1escH4mF1DQc933dtsyNvqbsqAT0bjg/A7IWOT0bh1EFbYKp3ZEs016PLpoxB1e98TUbf3PRC9y8EWD4PlSdm61fwaogYAD2l18Gdi99Et9cz44+rEOkFQSlg2bPQtbKwEUm4m3/OAU0hWMI7aYTukOM3TVNiC0nsC7G4ZTybD8VMmHRMMjVFsmkuFvkJstva+q03FNbBprq7X/XrV686tybP68ZCZ9Bu++8TG6Rrwxtjr9u4L9K+D+El/0meJdP5IzUwGuuVMbiNgmTWUsOrG29VQjGZoslWpvSWuGlv4dGliypmaTaHKTZ4xoQ+lzA1Fi4XMOInGSnB9wtFiF66S16n/t5o9bCurjdSaiugadHz5JEHMXL/TmUtM8mk7MmnnURKe9plXfg2lWIVzNemoybxWUs+scGjzCHNbK7hqLu70afsRms2sf1T+imorEffpdgNTtqL9Zm0SUGkrSoRFdyfkBl0HLUAnFVJ36oU79blPjR9BpcwL8vhjyJQpqnnRfXct93OlN/kUrAYEVw2IEGzq3s4mYBcyory0UquG2TZ23vFELTNruZos4EpGQFOg/nrwNshElADr+jxVvaEkq9/p3NzctIXf9dJqVtc5OX45Op2MWt122E4wVT5PZsZhKnRD8Gr+xwaqOYnaTjfL2xLlPzPorN8ehC/YyZSQmp4ob7tlXadccLcx0E2MQ1pdLqfCwQerypKWq3emf3EZ8IWwUkzpjbm4LIPV00eFTSwdbXxl/Nm03/9wErrX1NdQ7IyMF0Ll4AvAYFkTDKIIMmzs7VTAG3Xm69EZD7jYqS+ufX1R/yCHrLZ00ZC9XcBUEOgvAdrLslxW1UtZrumrra9yrEfiFTVZ47Isyz8Bw+pvow==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve All Statistics"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/statistics"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches all metrics on all disbursements the organization has created. The response includes basic aggregations on payments, receivers, receiver wallets, and assets.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./retrieve-all-statistics.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retrieve-all-statistics.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retrieve-all-statistics.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics.mdx
new file mode 100644
index 000000000..6ba18c6a6
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics.mdx
@@ -0,0 +1,5 @@
+---
+title: Retrieve All Statistics
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /statistics"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics.ParamsDetails.json
deleted file mode 100644
index d083a4ef5..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"ID of the `Disbursement`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics.StatusCodes.json
deleted file mode 100644
index a7d75ea2d..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Returns statistics for disbursement","content":{"application/json":{"schema":{"type":"object","properties":{"payment_counters":{"type":"object","properties":{"canceled":{"type":"integer","format":"int64"},"draft":{"type":"integer","format":"int64","example":1},"ready":{"type":"integer","format":"int64","example":2},"pending":{"type":"integer","format":"int64","example":3},"paused":{"type":"integer","format":"int64","example":1},"success":{"type":"integer","format":"int64","example":5},"failed":{"type":"integer","format":"int64","example":1},"total":{"type":"integer","format":"int64","example":14}},"title":"PaymentCounters"},"payment_amounts_by_asset":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","description":"Issuer of the asset. Empty for the native asset.","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"payment_amounts":{"type":"object","properties":{"canceled":{"type":"string"},"draft":{"type":"string","example":"100.00"},"ready":{"type":"string","example":"200.00"},"pending":{"type":"string","example":"300.00"},"paused":{"type":"string","example":"100.00"},"success":{"type":"string","example":"500.00"},"failed":{"type":"string","example":"100.00"},"average":{"type":"string","example":"100.00"},"total":{"type":"string","example":"1400.00"}},"title":"PaymentAmounts"}},"title":"PaymentAmountsByAsset"}},"receiver_wallets_counters":{"type":"object","properties":{"draft":{"type":"integer","format":"int64","example":1},"ready":{"type":"integer","format":"int64","example":1},"registered":{"type":"integer","format":"int64","example":1},"flagged":{"type":"integer","format":"int64","example":1},"total":{"type":"integer","format":"int64","example":4}},"title":"ReceiverWalletsCounters"},"total_receivers":{"type":"integer","description":"Total number of receivers","format":"int64","example":100}},"title":"DisbursementsStatistics"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics.api.mdx
deleted file mode 100644
index b13cef695..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: retrieve-disbursement-statistics
-title: "Retrieve Disbursement Statistics"
-description: "Fetches metrics on a specific disbursement by  `id `."
-sidebar_label: "Retrieve Disbursement Statistics"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNWG1T2zgQ/isafYIZ54UQyoy/BRJarhxNCZS5owxV7E2sxpZcSQ71Zfzfb1a2E+eFQDjauS+QSM+unl3tWzSjho01de/owDDDteGepvcO9UF7iseGS0FdegbGC0CTCIziniZSEEZ0DB4fcY/4XA8TpSECYcgwJeQb98m3OnWojEEx1HHuU5deoTRMoVvBV051aMwUi8CAQkIzKlgE1KXcpw7lSCNmJqCr3M67RI6ICYB8qyq25yv4kXAFPnWNSsCh2qQhqtQ8ikOgDoWfcSh9oO6IhRoBXgARo+6MmjS2SKO4GNMsu0dtOpZCg8b9VrOJ/5a5XIFJlNBEz60iI6mWHEQd6klh8JM7oyyOQ+5ZFzW+a9QxW+cgh9/BQ8FYoUMNzxnELEWFD55MRO6z5yQ8JjwI0R1zJBcGxqCoQ0dSRczkS+/aNHOor9jIvASLfmTWo+5Bhn5ifrqjXCtzaAzCR2fvJnmIkizRLzNrhapOPA+03lHyKHPoiPEXenLlSCMNC3eVa2coyY2N3n5+8aflvVsH5LHAIlzUD8P0gWkN1dtjSrEUM8lA9IJYseIPnk2O1WyoMKM3g+4pMsjxXOsE1CaJlaS1uDJxrWyd9KLYpDZhcFEww6fl3tKR709Ouu3j87N3F7cfj/vHf3Z7Xwant1fH3f7N7ZfDy78Ou9efe1/OLtqXnet25/OHw78vLs4uOkcbHPWqnClrwnqGbPDPQbNZbzbphrTYAG7Nweu5sAF+uICvJsBWJutRvwF+NIevhfpW5WwKio2fiZoFfDUdNoHbBXo9BzrFNT69dZJ2bCJk9gY84FNQD48sDMHoHUrn76yFudyYawPqVSVmFLLx+LcVp6XadFW4+Db3cLVGWd0P5R1srrnLVeIaJYhIomFeKxayW+1oNquMqkOBrowbWYaodvNgvY3fCJaYQCr+D/hv169BKbmhNGZI3Sj2giDEsSKp4nLXoIoItN6YdbmZc+fMadBLaciSmQsW5Tnt5kFF86rEr1ScX83h+tWcSTXkvg/i19/LZusWBF4AsHZo8BLFTWpn2hNgClQnMQF17+5xqozABBLH4zFYbjjjurSxGCEbM+5nFPWoaTkaJyqkLqUoX6ofoLm5RdVDFv0/5h8hXcuxTuF36zsSAPNBEfQs44KLMWGCDLp98sftNdnrDVpH7/aJVMXqA+n0z8kEUuzPxbS+pK8c3HO1GKeDXv+g+UbMyKDXrx00c265zWRm5AREtr8To1b7LRm12m/B6HMCKn0ZLQsl8x9PTzGqELCUyoN/oLiNZi5G0h5XlM6BgTBkilRLKOmHzGDxxbunDsWQzGkc15v1JsZpEkVMpVi/AyDbdewNuv19wjVhxEgZkmHCQ2NHQKnGTBQu0sRIErEJkGESTkgxw9lVRsZKJnHRHXjM7YacQj5ElqcLMI9STerrLeZ/R/Gr+CquA67tkYLIGERNy0R5QGIlsYIREzCD2zkVKYiRcTlLr6hzCBO+3cBRnnhMkCGQkUyEbwUD/BKG8hGjRUEsNTdScdAu8qiRO53raxT/a9XfsrW4cFJtyLwJCP9+LzAm1m6jMeYmSIZ1T0aNnTTsu8QaP6eSluGsLdkCZq3iYqSYNirxTKIKA8tfD1vvtL6DZSNlu8x/Ma1U8ZxtjzAkJfbV1gQQRjUvYMrorZQruIZRAI2IcdEoFrba85wZHyCMiFWUP35AHMoUw+tZS0iiEfcxGYISYEDXv2KVMqAi/Wk0ADXlHtal0qyCZl2qccOCanJU0wXMoSH3QGjbnMvCGzMvANKydSrvoajLbTQeHx/rzO5abYWoblycn/YuB71aq96sByYKbZ2MpTYRExXF5dPWsl1Lj1tLdWe2GF5e/bhWNAUDP00jDhkX2DusUbNiirijusrA5T4+7QVSG9ybzYZMw40KswyX8zbg3t07dMoUZ0NsAXcz6nONn/35G9mThuxdFc9t+2Tbo9xG3mWHE9jepixM8Bt16ATS/Akwu8+cskcirXyj43kQm4rI2iC4NGK9711Th7K1rjqxXbX4gNo30llt2zkF/Js5T4jMZnnPzrI5Pt96UqIwcW45WpBl2b/P83aE
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Disbursement Statistics"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/statistics/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches metrics on a specific disbursement by  `id `.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./retrieve-disbursement-statistics.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retrieve-disbursement-statistics.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retrieve-disbursement-statistics.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics.mdx
new file mode 100644
index 000000000..8a01b7899
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics.mdx
@@ -0,0 +1,5 @@
+---
+title: Retrieve Disbursement Statistics
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /statistics/{id}"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-stellar-info-file.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-stellar-info-file.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-stellar-info-file.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-stellar-info-file.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-stellar-info-file.StatusCodes.json
deleted file mode 100644
index 547374386..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-stellar-info-file.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Token is valid and the webpage will be loaded normally.","content":{"text/toml":{"example":"ACCOUNTS=[\"GBC2HVWFIFN7WJHFORVBCDKJORXXXXXXXXXXXXXXXXXXXXXXXX\", \"GDA34JZ26FZY64XCSY46CUNSHLX762LHJXQXXXXXXXXXXXXXXXXXXXXXXXX\"] SIGNING_KEY=\"GDA34JZ26FZY64XCSY46XXXXXXXXXXXXXXXXXXXXXXXX\" NETWORK_PASSPHRASE=\"Test SDF Network ; September 2015\" HORIZON_URL=\"https://horizon-testnet.stellar.org\" WEB_AUTH_ENDPOINT=\"https://ap-stellar-disbursement-platform-backend-dev.stellar.org/sep10/auth\" TRANSFER_SERVER_SEP0024=\"https://ap-stellar-disbursement-platform-backend-dev.stellar.org/sep24\"\n[[DOCUMENTATION]] ORG_NAME=\"Stellar Aid\"\n[[CURRENCIES]] code = \"EUROC\" issuer = \"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5\" is_asset_anchored = true anchor_asset_type = \"fiat\" status = \"live\" desc = \"EUROC\"\n[[CURRENCIES]] code = \"USDC\" issuer = \"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5\" is_asset_anchored = true anchor_asset_type = \"fiat\" status = \"live\" desc = \"USDC\"\n"}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-stellar-info-file.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-stellar-info-file.api.mdx
deleted file mode 100644
index dd97fe7e3..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-stellar-info-file.api.mdx
+++ /dev/null
@@ -1,62 +0,0 @@
----
-id: retrieve-stellar-info-file
-title: "Retrieve Stellar Info File"
-description: "Allows the wallet to fetch the SEP-10 server url, SEP-10 signing public key and SEP-24 server url."
-sidebar_label: "Retrieve Stellar Info File"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNV21vGjkQ/isjf2ok3kJoInHKBwJLIKELYSGvi5BZBtYXr71ne6Ec4r+fbCBHr03T3kWn8gV5PH7mGdv7zHhNDJ1rUn0ifZwzbRQ1TAoyypEp6kix1A2rpMa5XGowMcKSco4GjIQZmih2tsDr5Y9LoFEtUEGmeO7FxOaCiTmk2YSzCJ5xBVRM3Wy5crCgQHJEpriN356SKumjUQwXGBjknKq2mMkm40hyRKFOpdCoSXVNyqWS/fuS7kA+owCmYUE5m7qIjjpOUjpHWDLOYYLAJZ3iFIRUCeV8ZTlEUhgUxkIa/GyKRibcDvAzTVKOdivq9e7QHwTnTyG5vKiXW7d3zXbTP7u7ajW7/duLeuP6qtu/f+UXkhyE5LJRO6lcPZZPm48Pp5X7evBQOa0P/aDVuT87LXdaV/c3rwOMIGhf+m3/cnztPZx/G+z11eB7g7tu/3rcqwVBr9WvBd55SAaoDQSNJvhollI9w28QYGowmaCCcun4Y0ig1e23H7v+eNjvnIckNibV1WIxlor9KUXeoDYCTUFvj6sg1TwkcOddjGvDQWvs+Y1et+0PDlbSNL9zzk+ZnmRKY4LC5FNOzUyqJD+h0TOKaX6Ki0PYosb0uFSkmYlDAoN+zQ+aXn8ceP1b99crlcqVd4pTroQkFE9PjW59+MnzB7VBu+uPRtDtX4792ie7dbv7CTU23frWh/2+59fbXjAaQSSnCOcQEm/Y79ZDAkzrDJUzXV5cNCpn7eZp5+76rHf2qeHdBvW7/lmjN7y7PfEfThqDG++22an4tUGldtM6eex0mp3aR4cyplqjGVMRxVLhFM7BqAxhO95NmlW6DT5j1IQEtKEm087C2QJDAvazOaT3Ov9h0PiF6W/ZhYJsNptNjiRoYmlFZI6G5EhKTUyqpFhYIuf5ZyGXorg/aPeB58hWiawSrkmmOKkSshlZc5QpZlZBFGOyFZwLpApVLbOQa2I5kiqhKbvGFflKNjPjvg+nahAjnaICKzGUOVWkAoJGD67uBvDBC8ofT49Aqp11DLVe2wqmlSVBE/wnHskRZoNsYckmRwKvd1x6J2Z7AXfctjnD2lhd3Rz9FKNy5T0ZlSvvwegmQ7X6MVrOFVKqaILmdUYHBBylfeA/7HJi7yQTM+nCMePqyF43GgeaBL2dJtmzJzlir+SWxlmhVCjZe5olCVUrW+Ns3f0uxoeg0TuyVZCCkZLDJGPcwEwqkGpOxW6LtC3lCX1GmGT8GVK6sijOSmGuZJaCnIHCiKXMTUhbss1BdLGtGYWv9u7XoxiKUAxipl1IATJFkdcyUxFCquTvGBkwMTV2ektFCjDSwX8DLvfSWTiZjKiwXcVMZmLqFsZ2YDsne1sUplIzIxVDXbU88vC0E6HiD9Wn0Yd9RZszE2eTQiST4k8hHFXBJf9CZbW/ztvWbufmsmJipqg2KotMpnYJ2nMxb51p4ScymynXbv2X1PYQb+W2xAnsff91NjHyJB/FVBn9XcoHfkWjEIsJZaK4M3w3n7fSaCFPwAE5/lNMuVzZ6/VmJpBp63edTVAJNKgLoVUpgyrR3VmAasEiq0v7tA47IeeUl7O83rnlCGcRCo1W0fbCm9IoRig7ndrWUItVLRaXy2WBulmHtluqi5123fMDL18ulAqxSbjTyVRqk1BxALx/CbzkZ98CsHsMfKE467/79//nybKrHe6pkHLKhC0xLvf1rut4IgddhxXww75jlCOx1MZ6rdcTqnGo+GZjzdu6UX0a5ciCKkYntmY8jTa5fSmzjcoz2kJQiyJMbZuzoDx7YePwbQvz0gtdegOy2fwFFaPKXA==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Stellar Info File"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/.well-known/stellar.toml"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Allows the wallet to fetch the SEP-10 server url, SEP-10 signing public key and SEP-24 server url.
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retrieve-stellar-info-file.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retrieve-stellar-info-file.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-stellar-info-file.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-stellar-info-file.mdx
new file mode 100644
index 000000000..160e998dc
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-stellar-info-file.mdx
@@ -0,0 +1,5 @@
+---
+title: Retrieve Stellar Info File
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /.well-known/stellar.toml"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retry-payments.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/retry-payments.RequestSchema.json
deleted file mode 100644
index 5d9ba93d9..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retry-payments.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"application/json":{"schema":{"type":"object","required":["payment_ids"],"properties":{"payment_ids":{"type":"array","items":{"type":"string"}}}},"example":{"payment_ids":["9f687f8f-1f8f-4c8a-8e0f-1e67ed7c1330","6c2b9f20-53fd-4f1b-b7e2-9a2b1eb1d7c0"]}}},"required":true}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retry-payments.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/retry-payments.StatusCodes.json
deleted file mode 100644
index 6bb15a943..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retry-payments.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Payments retried successfully","content":{"application/json":{"schema":{"required":["message"],"type":"object","properties":{"message":{"type":"string"}},"title":"MessageResponse"},"example":{"message":"Payments retried successfully"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retry-payments.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/retry-payments.api.mdx
deleted file mode 100644
index e3f972df0..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retry-payments.api.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-id: retry-payments
-title: "Retry Payments"
-description: "Retries failed payments by ID."
-sidebar_label: "Retry Payments"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNV99v2zYQ/lcIPjWAZdlOmh96S5sMzbp1XpxiD65RUNLJYi2RKnmKqxn+34ejJFuxk7jZWmB5sB3y7uP3Hcm744qjmFseTPlYVDkotHzW4zHYyMgCpVY84LeARoJliZAZxKxoDFlYsZurPu9xXYARZHwTN+bVBq3HDXwtweIbHVc8WPFIKwSF9FMURSYj5+l/sbTWitsohVzQL6wK4AHX4ReIsMGRBmIi23D4LGPHtzBEASVYcuxObnGEMaLiPS4R8u64RSPVnK/X63WPwzeRFxnsoUz5RXJ6fpacJ96QPk6ic+GdwyDxhnB6BvFZNDw+HvAeP41G4UUyGnivj5PYO0mGoReewci7EKNwCOEwPosGfObW2upBU4IbsIVWthYxGgzo6+FOtFFlxm1JzGwZRWBtUmYZafvu2HZjmYO1Yg4Ux92QP4xra/hI7HocJVLc+O+10W2jhT8M6gbigJR6N04ei8EbEbPb+ki9RPHz0sAYbfaF7d6EK0AhM8tEqEtkmAKrHZ1INMIeXGld/5G24b62j0qUmGoj/4b4p4v7ftLcosCya6fKPASn+5lDsXujGh78g0b2QOeWRrvQyWDYgd712ITweD+Ev2gTyjgG9fPj94S8LYOGp4WoNBIrHkxX/A0IA+ayxJQH09l6RjIx1ZQ4C4FRSqsLmuR+m2h9uiJ0vS2YezDW4ZQm4wHnBNDiT0hPTbm7yjYDFvI9VHuH+rIJrAsOS0HEYBiFTkgl1ZwJxSZXY/brX3fs1fVk9Pr0iGnTjH5ml+MbtoCKyoASOeziUcKlRWpYOjCT6/Fw8IOYscn12BsOam61ZrZCvQC1PnoRo9HJj2Q0OvkRjP4swVTfR8uZskIYkQM+zahDwFFqF/5K7i6L09W43dbr6yfLYXMHZmuCSLSj2FSACUKWCcOupA1LY4Hc2DgTmGiT03nhPU7HuKZ+1h/0qXDaMs+FqXjA71Jgz2O8mlyNj5i0TDDUOmNhKTNkiTZMm7lQTVgtQ81ysQAWltli27agZoLNjS4LphNmIJKFdBP6HoxL6u3qCnCpzaK/F+//H8VP6pO6S6V1SyqmC1Ce1aWJgBVGU1pjmAqk6ZqKVgy1g38ErseEit1EpGNgkVAsBJboUsXOMaV/skwv6YQZKLSVqKlHDIiHx6a2xvObby/uBMkrmiB5oYgWoOLZqxSxsIHvzyWmZdiPdO6/COEoYE78hkrVXgHryDZmTpVUiREWTRlhaRqBtC94aE/7L1CWGFd6/ou0FuKQtiWErLX912pSyHIvSoVB+yzljp2PBsDPhVR+M/CsnkMy3kGWMwfk+MdQZLqi43VQCSst2b0vQzAKEGz/E2U2BJPbP5IJmHsZUV5qZTU0+9rMfWfk6cSzjVmPZzICalyD1SZZFyJKgY1cnqrrLmEFvr9cLvvCzTq0xtX6v928vf4wufZG/UE/xTxzubXQFnOhOsDupcQ6T6UHWabzVDr8BGvqA8I39ItMSEVlxHFdNf3E5tFUv8moo5j1eKot0txqFQoLH022XtNwXRGC6azH74WRIqTMPqVs3xQpakEWQOn6bU3SuyMGZJ6VdaXaabjWvdbjMoqgwGdtu23R+PLu7Tve42HzgMx1TE5GLEmIWFIbRG9Ql1Dd44bGVjwTal7W/WMNSpsg9urpwtXT5gfJaqdU1aG4W7BrJfRJuh51Wa3qar1eb+zrqSc9mti21rSJ9FT8Bwceeiw=
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retry Payments"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/payments/retry"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Retries failed payments by ID.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./retry-payments.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./retry-payments.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retry-payments.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/retry-payments.mdx
new file mode 100644
index 000000000..79e2eb356
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/retry-payments.mdx
@@ -0,0 +1,5 @@
+---
+title: Retry Payments
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml PATCH /payments/retry"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/revoke-distribution-wallet-membership.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/revoke-distribution-wallet-membership.ParamsDetails.json
deleted file mode 100644
index f64b2a8f5..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/revoke-distribution-wallet-membership.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"The unique identifier of the distribution account","required":true,"schema":{"type":"string"}},{"name":"membershipID","in":"path","description":"The unique identifier of the access grant being revoked","required":true,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/revoke-distribution-wallet-membership.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/revoke-distribution-wallet-membership.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/revoke-distribution-wallet-membership.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/revoke-distribution-wallet-membership.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/revoke-distribution-wallet-membership.StatusCodes.json
deleted file mode 100644
index 4798d80f2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/revoke-distribution-wallet-membership.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"204":{"description":"Access revoked successfully"},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/revoke-distribution-wallet-membership.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/revoke-distribution-wallet-membership.api.mdx
deleted file mode 100644
index 086354742..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/revoke-distribution-wallet-membership.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: revoke-distribution-wallet-membership
-title: "Revoke Account Access"
-description: "Revokes a user's access to a distribution account. Owner only. The grant history is preserved in the account's audit trail."
-sidebar_label: "Revoke Account Access"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdV99v2zYQ/lcIviwBZMvJsg3QW7a4WNauzeIUfUiNgZLOFmuKVI+kXU/Q/z4cJTlK4iZLlmHDXvxDPH73fXfU3bHmTiwtT675mbQOZeqdNJp9EEqBs3we8RxshrKixzzhl7A2K7BMMG8Bv7FMZBlYy5xhguVDCJFlxms3Zu82GpAZrbZjdlUAW6LQjhXSOoNbJi2rECzgGnImNXMF9FsJ3efSMYdCqjGPuKkABaGf5zsuQ94t7V+hTAFtISse8UqgKMEBksiaa1ECT7jMecQlCaqEK/hdlUTTa/nZA5M5aCcXkiQsArt9KnnEET57iZDzxKGHiNusgFLwpOZuW5FP2qWXvGmiHY1yx/T87PmEuhS0cU1B6iXDEJr8SbTmZGwroy1YWj+enNDXbSKnra8On1kf/i+8UlveRPxkcnR/z3stvCsMyj8Co8xoB9qRnagqJbOQ0fiTJeP6PkGTfoKMIlwh5d/Jlh4gGtyjI+LwxaGwjyNYJ5wf2mlP6SCIEqwVS9gXpqYJLkRZKRjw4G+NY7d03tDoHZ1MjgbQd3d00CeTb++H8JXBVOY56H8+fl+Rd8Ogp7nndJCiV8br/3maF53EfRk+GWb4EqzxmAHTu11NB20h8yjdNlSlH0Eg4Kl3BU+u5/QmluAKQ0UuBwUOQiGjVR4Py89o09bpuJZ5E99UExvXw9LScPKH674IelQ84Zz89DRmlI42XkMyu7iISr6G7b26dNod35BbVoDIARllXkhNdUhoNju7YL98uGIH09nxd98fMoPd09/Z6cU5W8GWKntXEG/h9RWxhaV8zaYXR5MXYsZm04vR0aTl1mpmtTMr0M3hkxgdn7wko+OTl2D0mwfc/jVawZTt2uTXGA0IBEq948+0nZoal3phgjvp6JXhMwdKCWRn0qYeLZSgHbtQwi0MlpR7HnE6ki2NH8aT8YTOqS9Lgduu5z2McTA7uzikCUIwZ4xiqZeK3jNkBpdCdyEKw0kpVsBSr1asEltC6UaWJRpfUSNFyGQlw4JZA4bG2nvX4DYGV+O9bfm/RfGj/qivCmmDS81MBXrU1aAKDdVH5grhaLmlYjRzpupHiTtwERM6DwuZyYFlQrMU2kIWNhb0RymzaWeOyljpDEqwCfEYsWvb4sXd9ygfBGlUdUEapSJbgc7nB4VzlU3ieCld4dNxZsr4SQiHCQvid1S2/XG2gWxnFlRJvUBhHfrMeewEUl7cYzkdP0HZAkMX/DvSeojHtG0gZb3ts9UUoMpRVgh09kHKA7vYIUBcCqnj7sGDeh6T8TOokgWgwD+HSpktHa9HlTBvye61TwE1OLDjj1SlHGBp3y1mgGuZUV3qZXU0xwaXcTAamcXIdmYRVzIDbUPv7wtvJbIC2HGoU20PJawkjjebzViE1YDWbbXxm/Ofpm9n09HxeDIuXKlCnayMdaXQA+D2IsNO27sEa2fsu8Wmvpmo/uVbWNdPHHxxcaWE1NR2Qjzqbkq55vumFB7xJFy8BoMKPbt1C5pHvDDWEUZdp8LCe1RNQ4/bTpNczyO+FihFSl3muiZX9DvnyUIoCw+E7eCyuwwdsufc8Pbq7purps66FsrTPx7xFWzbeyZd916e4oN3vmcQvZWDZt5E/URBEW5N6FhWbrD53lh/a3A9m76ZXk15xMW9MWQVxpDuBznYy+3unNOyoE8K6d4tdd0OOU2zs2+XvrqjU7nLF4lomuZP8bUC1A==
-sidebar_class_name: "delete api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Revoke Account Access"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"delete"}
-  path={"/distribution-wallets/{id}/memberships/{membershipID}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Revokes a user's access to a distribution account. Owner only. The grant history is preserved in the account's audit trail.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./revoke-distribution-wallet-membership.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./revoke-distribution-wallet-membership.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./revoke-distribution-wallet-membership.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/revoke-distribution-wallet-membership.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/revoke-distribution-wallet-membership.mdx
new file mode 100644
index 000000000..13be992be
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/revoke-distribution-wallet-membership.mdx
@@ -0,0 +1,5 @@
+---
+title: Revoke Account Access
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml DELETE /distribution-wallets/{id}/memberships/{membershipID}"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/send-one-time-passcode.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/send-one-time-passcode.RequestSchema.json
deleted file mode 100644
index d63b1c66d..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/send-one-time-passcode.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"description":"Object containing phone number","content":{"application/json":{"schema":{"required":["recaptcha_token"],"type":"object","properties":{"phone_number":{"type":"string","description":"Phone number to which the OTP will be sent. Either `phone_number` or `email` is required."},"email":{"type":"string","description":"Email to which the OTP will be sent. Either `phone_number` or `email` is required."},"recaptcha_token":{"type":"string","description":"Token for reCAPTCHA validation (required unless reCAPTCHA is disabled)."}}}}},"required":true}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/send-one-time-passcode.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/send-one-time-passcode.StatusCodes.json
deleted file mode 100644
index 84b6c46fc..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/send-one-time-passcode.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"OTP sent successfully","content":{"application/json":{"schema":{"type":"object","properties":{"message":{"type":"string"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"}}},"example":{"message":"if your phone number is registered, you'll receive an OTP","verification_field":"DATE_OF_BIRTH"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/send-one-time-passcode.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/send-one-time-passcode.api.mdx
deleted file mode 100644
index 0c5bb2af3..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/send-one-time-passcode.api.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-id: send-one-time-passcode
-title: "Send One-Time Passcode"
-description: "This endpoint generates a 6-digit OTP and sends it to the user contact (email or phone number SMS) provided in the request body, as long as it matches the receiver contact info stored in the SDP. A valid SEP-24 token should be included in this request's Authorization header."
-sidebar_label: "Send One-Time Passcode"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWG1v2zgS/isDftkEkOw0yO0B+uY0XjS329gbu7dYpIFLS2OLG4rUkqO4PsP//TCk1CgvTdq7LHAfLh9imxrOPPPCmYfaCZJrL7IrcYlr5clJUtaI60QU6HOn6vAzE/NSeUBT1FYZgjUadJLQg4Qf00KtFcFkPgVpCvBoCg+KgCxQidB4dJBbQzInOMBKKg3WQV1ag2CaaokOZu9nh1A7e6sKLECZsNHhnw16gqUttglID9qaNX8qgkpSXqJv5XJUtz0jyqwseLLuTtfsbDqAEdxKrQqYjafp8QmQvUEDvrSNLmCJoEyumy/2le8A/OBh1FBpnfpXCA6UKAt0A5EIW2MM2HkhMjFDU0wMzlWFU+l9bgsUiWi1nNpiK7Ldg7BOln9gThG5Msqs78VFJIKfoCHeKetaqzyYG/7heftO+LzESvI3NqMcFpxKh7msKS/lIvjI2aRtjSITNtgTiagdYyeFnjcHo4vWaLbrpD05ZdbiYS1M+6kjC5tS5WUIM9fARmnN4fRoaABjRSU6+NS38Inz/ylUwido48zQB2KfiLD8MoZxqKPXNv4wcC/CmIcaWlkHDt+OpvO379oii5Vy0GmHxmj0vielPBTKy6XG4nAg9vyX9JJIrsGw4GtrfMzS8dHRExU0nwZvwTd5jt6vGq2331M4z1dGhd7LNT6OxD4Rt+jUqlW8WCnUxVMBQ9NUXJRno/l4MflpcXp+OX8nEvH7eHS5eD+5CD+m5xciERej+fnkYvTL4vxscfHh/en4MpSuIs0a/9kz91OwFmKGn2VVa7wHVqgVbG3zoMuEbHOTQ4dFwgI/aN21D5CGK0g87dYD9DFbJ0/l41QWcBmP/OtlAZ2z33Awz5Ck0h7k0jYUzkTcGKJETvoXLe33+863N499+2Bk2wix+Mud+3bQwpOkpi/XdrJ98kz9PiyeFoa4sAT33LxD0dk5OXrT0/xwx1+pOOj2mDdO0VZkVzsxG0+PT3g+iezqen+diM8pD541mrSdPCkP0NTIilXy92gajVfW+KDkBrcie3ZnIm6lbr5oYEMVUmn5bNQ21HotGYQYeqyPT1JlCJ3MSd1iWmBtvaKhpVowfHeLLhpunBaZCOo6r2ZcNjGvpygduujcl/zJWv2M20e1/9SI7s9VaZgEwD9+m8PBeHb8tx8PeRDE1QWMpudwg1ue6W2g7ukTiVBsJKrlupqNp2+OXglZICRvjiK26DPswgDaH34Xoq4QXgfR8clrIPq1Qbf9NlhBFGrpZIX0dUQ9AHFKt4b/5O2CDwh3oMs72jW+O4v3iU5vSEXWcbfwiAn02hLzy+BNO5hmhFpLB2fKLxvnseJxPNWSVtZVXFpxqPjo5d8HR4MjPgZNVUm3Ddwa4XkdB7Oz6SHPLwlkrYZlozQF2mHdWpo2A575UCVvEJaNvoFabllLWJWwdrapwa543qlahQeWWTP1rBukjXU3g8c8538O4kfz0YRLCZs0YGs0qbeNy5EvEoFVUymJH0co1gDZoP4JdUm4uvADboGQS8MscmUbU4SNJf/Q2m64GF1sZ9Yp9BnjSOHKR33D9jMtekFK6zZI6VLmN2iK64OSqPbZcLhWVDbLQW6r4XdpOMxgHq8oLZRtd1rinagVC14ps3LSk2tyalzrIOeFXsrp4Ds8W7lABv4b1zoVL/m2wSV0sv+xNyXqKs1L6cg/C7knNySHOKykMsN24Vl/XnLjHeoKgqKAv8Ba2y2X14ueQONZ7udmic4goR985CZI6Co/Wc3Q3aqc+1LnVgtzYN16GIRSu0p9K5YIrXI0PrTHrq/XMi8RjkOfiiOadWXD4WazGcjwNGhrt/rhL+dvxxezcXo8OBqUVOnQhpkXVNL0FPMNGSYGU74jQ++SfK/b7O6Y5f/fOzz53qGdo4SfaVhrqQyPpZCoXUvDrsRXaRi/t6Cab1YlE7fsSux2S+nxg9P7PS/HQZpdXTPpc4rvqIFcJt1sv6OMb2Oi0jkDuuOIj64D+6TbMcpzrOlZ2T63nE5mc5FE0sk3PC6XTDi54RktN0we+TUMRSq7i2s7oaVZN5FER51cj/IRC7kJLKT9wl51j8y2h/AhzYmO8H9268ktu13kOPv9F/n46Ks72tB20pzS6/1+/29EXeDG
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Send One-Time Passcode"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/sep24-interactive-deposit/otp"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint generates a 6-digit OTP and sends it to the user contact (email or phone number SMS) provided in the request body, as long as it matches the receiver contact info stored in the SDP. A valid SEP-24 token should be included in this request's Authorization header.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./send-one-time-passcode.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./send-one-time-passcode.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/send-one-time-passcode.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/send-one-time-passcode.mdx
new file mode 100644
index 000000000..1abc214d1
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/send-one-time-passcode.mdx
@@ -0,0 +1,5 @@
+---
+title: Send One-Time Passcode
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml POST /sep24-interactive-deposit/otp"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/sidebar.ts b/docs/platforms/stellar-disbursement-platform/api-reference/sidebar.ts
deleted file mode 100644
index 96df514f4..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/sidebar.ts
+++ /dev/null
@@ -1,670 +0,0 @@
-import type { SidebarsConfig } from "@docusaurus/plugin-content-docs";
-
-const sidebar: SidebarsConfig = {
-  apisidebar: [
-    {
-      type: "category",
-      label: "Admin (Tenant Management)",
-      link: {
-        type: "doc",
-        id: "platforms/stellar-disbursement-platform/api-reference/admin",
-      },
-      items: [
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/get-all-tenants",
-          label: "Get All Tenants",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/create-tenant",
-          label: "Create Tenant",
-          className: "api-method post",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant",
-          label: "Retrieve a Tenant",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant",
-          label: "Soft delete a Tenant",
-          className: "api-method delete",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/update-a-tenant",
-          label: "Update a Tenant",
-          className: "api-method patch",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/default-tenant",
-          label: "Default Tenant",
-          className: "api-method post",
-        },
-      ],
-    },
-    {
-      type: "category",
-      label: "Authentication",
-      link: {
-        type: "doc",
-        id: "platforms/stellar-disbursement-platform/api-reference/authentication",
-      },
-      items: [
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/log-in",
-          label: "Log In",
-          className: "api-method post",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/refresh-token",
-          label: "Refresh Token",
-          className: "api-method post",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/authenticate-mfa",
-          label: "Provide Multi-Factor Authentication",
-          className: "api-method post",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/forgot-password",
-          label: "Forgot Password",
-          className: "api-method post",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/reset-password",
-          label: "Reset Rassword",
-          className: "api-method post",
-        },
-      ],
-    },
-    {
-      type: "category",
-      label: "API Keys",
-      link: {
-        type: "doc",
-        id: "platforms/stellar-disbursement-platform/api-reference/api-keys",
-      },
-      items: [
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/list-api-keys",
-          label: "List API Keys",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/create-api-key",
-          label: "Create API Key",
-          className: "api-method post",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/get-api-key",
-          label: "Get API Key Details",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/update-api-key",
-          label: "Update API Key",
-          className: "api-method patch",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/delete-api-key",
-          label: "Delete API Key",
-          className: "api-method delete",
-        },
-      ],
-    },
-    {
-      type: "category",
-      label: "Balances",
-      link: {
-        type: "doc",
-        id: "platforms/stellar-disbursement-platform/api-reference/balances",
-      },
-      items: [
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/get-organization-circle-balances",
-          label: "Get Organization (Circle) Balances",
-          className: "api-method get",
-        },
-      ],
-    },
-    {
-      type: "category",
-      label: "Bridge Integration",
-      link: {
-        type: "doc",
-        id: "platforms/stellar-disbursement-platform/api-reference/bridge-integration",
-      },
-      items: [
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/get-bridge-integration",
-          label: "Get Bridge Integration Status",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/update-bridge-integration",
-          label: "Update Bridge Integration Status",
-          className: "api-method patch",
-        },
-      ],
-    },
-    {
-      type: "category",
-      label: "Disbursements",
-      link: {
-        type: "doc",
-        id: "platforms/stellar-disbursement-platform/api-reference/disbursements",
-      },
-      items: [
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/list-all-disbursements",
-          label: "List All Disbursements",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/create-disbursement",
-          label: "Create Disbursement",
-          className: "api-method post",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement",
-          label: "Retrieve a Disbursement",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement",
-          label: "Deletes a Draft Disbursement",
-          className: "api-method delete",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers",
-          label: "List All Disbursement Receivers",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions",
-          label: "Download Disbursement Instructions",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions",
-          label: "Upload Disbursement Instructions",
-          className: "api-method post",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status",
-          label: "Update a Disbursement Status",
-          className: "api-method patch",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/list-registration-contact-types",
-          label: "List Registration Contact Types",
-          className: "api-method get",
-        },
-      ],
-    },
-    {
-      type: "category",
-      label: "Distribution Wallets",
-      link: {
-        type: "doc",
-        id: "platforms/stellar-disbursement-platform/api-reference/distribution-wallets",
-      },
-      items: [
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/list-distribution-wallets",
-          label: "List Distribution Accounts",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/create-distribution-wallet",
-          label: "Create Distribution Account",
-          className: "api-method post",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/get-distribution-wallets-total-balance",
-          label: "Get Total Balance",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet",
-          label: "Get Distribution Account",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-balance",
-          label: "Get Account Balance",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-capabilities",
-          label: "Get Account Capabilities",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/list-distribution-wallet-memberships",
-          label: "List Account Access",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/grant-distribution-wallet-membership",
-          label: "Grant Account Access",
-          className: "api-method post",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/revoke-distribution-wallet-membership",
-          label: "Revoke Account Access",
-          className: "api-method delete",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-audit",
-          label: "Get Account Access History",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/archive-distribution-wallet",
-          label: "Archive Distribution Account",
-          className: "api-method post",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/promote-distribution-wallet-to-default",
-          label: "Promote Account To Default",
-          className: "api-method post",
-        },
-      ],
-    },
-    {
-      type: "category",
-      label: "Organization",
-      link: {
-        type: "doc",
-        id: "platforms/stellar-disbursement-platform/api-reference/organization",
-      },
-      items: [
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/get-organization-info",
-          label: "Get Organization Info",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/update-organization-profile",
-          label: "Update Organization Profile",
-          className: "api-method patch",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/get-organization-logo",
-          label: "Retrieve Organization Logo",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/patch-organization-circle",
-          label: "Circle Account Setup",
-          className: "api-method patch",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/get-all-assets",
-          label: "Get All Assets",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/create-asset",
-          label: "Create Asset",
-          className: "api-method post",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/delete-asset",
-          label: "Delete Asset",
-          className: "api-method delete",
-        },
-      ],
-    },
-    {
-      type: "category",
-      label: "Payments",
-      link: {
-        type: "doc",
-        id: "platforms/stellar-disbursement-platform/api-reference/payments",
-      },
-      items: [
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/list-all-payments",
-          label: "List All Payments",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/create-direct-payment",
-          label: "Create Direct Payment",
-          className: "api-method post",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment",
-          label: "Retrieve a Payment",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/retry-payments",
-          label: "Retry Payments",
-          className: "api-method patch",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/update-payment-status",
-          label: "Update Payment Status",
-          className: "api-method patch",
-        },
-      ],
-    },
-    {
-      type: "category",
-      label: "Profile",
-      link: {
-        type: "doc",
-        id: "platforms/stellar-disbursement-platform/api-reference/profile",
-      },
-      items: [
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/get-profile",
-          label: "Get Profile",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/update-user-profile",
-          label: "Update User Profile",
-          className: "api-method patch",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/reset-user-password",
-          label: "Reset Password",
-          className: "api-method patch",
-        },
-      ],
-    },
-    {
-      type: "category",
-      label: "Receivers",
-      link: {
-        type: "doc",
-        id: "platforms/stellar-disbursement-platform/api-reference/receivers",
-      },
-      items: [
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/list-receiver-verification-types",
-          label: "List Verification Types",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/list-all-receivers",
-          label: "List All Receivers",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/create-receiver",
-          label: "Create Receiver",
-          className: "api-method post",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver",
-          label: "Retrieve a Receiver",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/update-receiver",
-          label: "Update a Receiver",
-          className: "api-method patch",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet",
-          label: "Update Receiver Wallet",
-          className: "api-method patch",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet-status",
-          label: "Update Receiver Wallet Status",
-          className: "api-method patch",
-        },
-      ],
-    },
-    {
-      type: "category",
-      label: "Registration",
-      link: {
-        type: "doc",
-        id: "platforms/stellar-disbursement-platform/api-reference/registration",
-      },
-      items: [
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/get-receiver-registration-info",
-          label: "Get Receiver Registration Info",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/send-one-time-passcode",
-          label: "Send One-Time Passcode",
-          className: "api-method post",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/verify-receiver-registration",
-          label: "Verify Receiver Registration",
-          className: "api-method post",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/start-wallet-registration",
-          label: "Start Wallet Registration",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/retrieve-stellar-info-file",
-          label: "Retrieve Stellar Info File",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction",
-          label: "Request Challenge Transaction",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/provide-signed-challenge-transaction",
-          label: "Provide Signed Challenge Transaction",
-          className: "api-method post",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/get-sep-24-info",
-          label: "SEP-24 Info",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/request-registration-url",
-          label: "Request Registration URL",
-          className: "api-method post",
-        },
-      ],
-    },
-    {
-      type: "category",
-      label: "Statistics",
-      link: {
-        type: "doc",
-        id: "platforms/stellar-disbursement-platform/api-reference/statistics",
-      },
-      items: [
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics",
-          label: "Retrieve All Statistics",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics",
-          label: "Retrieve Disbursement Statistics",
-          className: "api-method get",
-        },
-      ],
-    },
-    {
-      type: "category",
-      label: "Users",
-      link: {
-        type: "doc",
-        id: "platforms/stellar-disbursement-platform/api-reference/users",
-      },
-      items: [
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/get-all-users",
-          label: "Get All Users",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/create-user",
-          label: "Create User",
-          className: "api-method post",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/update-user-activation-status",
-          label: "Update User Activation Status",
-          className: "api-method patch",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/get-all-roles",
-          label: "Get All Roles",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/update-user-role",
-          label: "Update User Role",
-          className: "api-method patch",
-        },
-      ],
-    },
-    {
-      type: "category",
-      label: "Exports",
-      items: [
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/export-disbursements",
-          label: "Export Disbursements",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/export-payments-csv",
-          label: "Export Payments",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/export-receivers-csv",
-          label: "Export Receivers",
-          className: "api-method get",
-        },
-      ],
-    },
-    {
-      type: "category",
-      label: "Wallets",
-      items: [
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/get-all-wallets",
-          label: "Get All Wallets",
-          className: "api-method get",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/create-wallet",
-          label: "Create Wallet",
-          className: "api-method post",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/update-wallet",
-          label: "Update Wallet",
-          className: "api-method patch",
-        },
-        {
-          type: "doc",
-          id: "platforms/stellar-disbursement-platform/api-reference/delete-wallet",
-          label: "Delete Wallet",
-          className: "api-method delete",
-        },
-      ],
-    },
-  ],
-};
-
-export default sidebar.apisidebar;
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant.ParamsDetails.json
deleted file mode 100644
index f62d61c53..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"ID of the `Tenant`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant.StatusCodes.json
deleted file mode 100644
index c5e44d306..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Deleted Tenant details, with a non-empty `deleted_at` field","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"name":{"type":"string","description":"The tenant name. It should match the pattern `^[a-z-]+$`.","example":"bluecorp"},"base_url":{"type":"string","description":"The SDP backend server's base URL.","example":"https://bluecorp-backend.sdp.org"},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL.","example":"https://bluecorp.sdp.org"},"status":{"type":"string","enum":["TENANT_CREATED","TENANT_PROVISIONED","TENANT_ACTIVATED","TENANT_DEACTIVATED"]},"distribution_account_address":{"type":"string","description":"The Stellar account address used for distributing funds.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"distribution_account_type":{"type":"string","description":"The Stellar account type used for distributing funds.","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"distribution_account_status":{"type":"string","description":"The status of the distribution account used for distributing funds.","enum":["ACTIVE","PENDING_USER_ACTIVATION"]},"is_default":{"type":"boolean","description":"Boolean flag that shows whether the tenant is the default or not.","default":false},"created_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"deleted_at":{"type":"string","description":"The timestamp when the tenant was (soft) deleted.","format":"date-time","example":"2024-03-27T17:21:51Z"}},"required":["base_url","created_at","distribution_account_address","distribution_account_status","distribution_account_type","id","is_default","name","sdp_ui_base_url","status","updated_at"],"example":{"id":"840dca45-d1df-44cd-83c1-65c04235c25f","name":"redcorp","base_url":"https://redcorp-backend.sdp.org","sdp_ui_base_url":"https://redcorp.sdp.org","status":"TENANT_PROVISIONED","distribution_account":"GCQVDMPOEN3HHJJ64V42KUTONOXN7C6V2PSVPALEVJ7PIYOB6M3DJV7N","is_default":true,"created_at":"2024-03-27T17:21:51.000Z","updated_at":"2024-03-27T17:21:51.000Z"},"title":"Tenant"}}}},"304":{"description":"The tenant was already deleted before this request.","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"name":{"type":"string","description":"The tenant name. It should match the pattern `^[a-z-]+$`.","example":"bluecorp"},"base_url":{"type":"string","description":"The SDP backend server's base URL.","example":"https://bluecorp-backend.sdp.org"},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL.","example":"https://bluecorp.sdp.org"},"status":{"type":"string","enum":["TENANT_CREATED","TENANT_PROVISIONED","TENANT_ACTIVATED","TENANT_DEACTIVATED"]},"distribution_account_address":{"type":"string","description":"The Stellar account address used for distributing funds.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"distribution_account_type":{"type":"string","description":"The Stellar account type used for distributing funds.","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"distribution_account_status":{"type":"string","description":"The status of the distribution account used for distributing funds.","enum":["ACTIVE","PENDING_USER_ACTIVATION"]},"is_default":{"type":"boolean","description":"Boolean flag that shows whether the tenant is the default or not.","default":false},"created_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"deleted_at":{"type":"string","description":"The timestamp when the tenant was (soft) deleted.","format":"date-time","example":"2024-03-27T17:21:51Z"}},"required":["base_url","created_at","distribution_account_address","distribution_account_status","distribution_account_type","id","is_default","name","sdp_ui_base_url","status","updated_at"],"example":{"id":"840dca45-d1df-44cd-83c1-65c04235c25f","name":"redcorp","base_url":"https://redcorp-backend.sdp.org","sdp_ui_base_url":"https://redcorp.sdp.org","status":"TENANT_PROVISIONED","distribution_account":"GCQVDMPOEN3HHJJ64V42KUTONOXN7C6V2PSVPALEVJ7PIYOB6M3DJV7N","is_default":true,"created_at":"2024-03-27T17:21:51.000Z","updated_at":"2024-03-27T17:21:51.000Z"},"title":"Tenant"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant.api.mdx
deleted file mode 100644
index f21a9e515..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: soft-delete-a-tenant
-title: "Soft delete a Tenant"
-description: "Soft delete a Tenant"
-sidebar_label: "Soft delete a Tenant"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWW1z4jgS/isq1VVtUmcDARJm+UaCZ4e8AAOEmZtMjpGtdqyNLXklOSyb4r9fSbYJDORlZvNh6yr5QpBa3U+3Wt2PxD3W5Ebh9hXu0IRxfO1gkYIkmgneo7iNxyLUXYhBQ2cCnHCNHZwSSRLQIM3Ce8xJAriNGcUOZhy3cUp0hB1MQQWSpUYVbuNeF4kQ6QjQt1zRtwp2sIQ/MiaB4raWGThY6UVslCmWpDFgB8OfaSwo4HZIYmUEgggSgtv3WC9SK6kl4zd4ubw22lQquAJl5uu1mvnYRJG7QlEOAVHQhMXKQXOmI0QQF9yFJNUL9I3mkjOiv6GQQWy8CwTXwLVRS9I0ZoGNU/V3ZXTfb2MT/u8Q2IhJE1XNcmSMbuM3nhLrcxsftBpHPtCG2/J/rbvN1lHNfReGdffwIPRr7wBqrV9DvHSKwG9r2nR5EgHSubtmQQX1NFKRyGKKEqKDyO5JSrQGydG3/14R9y/3+t//stvzgMmPMwiETI1dnyiYZTJ+me1xd4h8EtwCp0iBvAP5i0JGBbocnW8aibROVbtaLY25xbqKomlFyBtjXNF0lrHZj2O47FUpUZEviKTo+EX2N+xqojO1c+N4lpgTNPH6nf5kdjLyOhOvi51yYDgaTHvj3qC/Ptg5mfSmm3Jd72HweulgyowJPzN+zEgQiIzrGaFUgtqJY4fbGuKYSFQsRsVilCmgKBQSPZjgNyjMOFWbAfnt5HPntPH5tDE9a5y+/9D4eNF9PxifXdT7FxdfjseDxrQ3OfIuhx8/jbuf6qet5kW9MRqNz/Fj8HPMP4PdrHgWeLET3d54MuodX056g/6sc3IyuOxPKuOJd37eGVW8/hQ7T4t0j2fTzuX55DG5k97o5Nx7EHt0tx5Pmm2Hc9mySK6rW8Xghe7bNPKwg4dev9vr/za7HHujMuN6g77Fy9SMQkiyWK/B84WIgfAtfMf5OApjcoN0RGwFmSs0j0BHIC3iosYwlePPdSMhERe6YjUW1mwlXzo4kEDyCrsrQKGQiZnBlGhwNUtgIzPrtXrTrTXcemty0GrXD9qHB19M1mUpfX2lD73gheWWJaA0SVITIL4enTlRaE+JUO+jQmnlZ2Et17vn1UNR3gjsM1Xk6bR96gw7Rb9/yKKiH21X6FXt3Nid6zUP85aI3zVrNCDNQ5ce0NBtNgPqvmsEB+7RYVBr1huHQf0wLM20sQRqG9J6P1pV8GJyq4Hs6B/fr1mXLY7v7kq+Kzi2Zn6cdi+GA6/f+PDh9PSoOW3Wzy4ng/7gc791cjStD8fTYefcm562hr3/DI6PLhrd02mrvxnNgg+tn5FdeVCp1WpfNgP7hNzSwZppm1MFmVsuTR41as1tqjTZzFoSSyB0UaYt8iEUEpCOmEImD0HZU/5Gkd4o0htFeqNIbxTpjSK9UaQ3ivT/QpGau16TjglFo5z7vB71ASmFfP4QdfOnK0R8kWl7fvKFS5M0WhL1rKVl/md820H/+kKj9yLjr/ju9YhnL0e8zTB4lvhgnU5AKXKzo3MWTq6dpAKHdTEsXHxAUNpo1pprWvEIlMhkAKZWF6vK+CkIMsn0wr6GHhPFgk6mI9y+ujaPkpthNe+pRV1DBK2eVBPQkTAHPJ+yj6xGBa7mVVFV7xldmvNm6WH+8JqfTWyMlBDGZivyWB0DkSBzJKuYkJSdwWIrmYyUkOwvu68oAkJBIrPrhHHTPwm3/PD00wTteeP64dG+6Vr56Ax1hj10C4vKQ+HZ0Fc+C+dqzV6NveFB7ZWQobE3dA9qObbcZ3SvxS3w5f4PIao3XxNRvfkaiD5mIBcvg2VF0epp/jFEawAspNLwH2a57ZiMh8KaK8pgyTK7TPmZVJAA12gYE21astl77GCTkjmMVqVWqZk8zZKEyMV3THW3jr1xd7hvWBFBWogY+RmLtSVxQt4QXoRIIS1QQm4B+Vl8i1KyMFrsKEE3UmSpIYYSApYyOyHuCtpVWueg50LeVp4k0/8MiF/5Vz4xV2tjkiORAneL+pNKYWpjzjGZKqAIjrRIS2r8nToHEU7tRCAooIBw5ENexOzCyHyJYzE32SIhFYppIRmotsHhoiuV66sWny5dC5KbFkEqmcT1XkkXbpiOMr8SiKT6Qxr222iSvysUUBZlOufMubwrG68YDyVRWmaBzmThoNkX/dyeVn7As1DaDvh3XCtVPOfbHHxUyv60NxHEiRtERGr1JOQ1uaqWANWEMF4tBp705zk3PkCcIKsov41BGouFSa9nPUGZMnJnmQ+SgwZV+WqqlAaZqEE4BnnHgvWXiAKm4aNVK+SK0FWFmINjFgBXtu+XhTclQQSobuvUA79tV6vz+bxC7KzVVixV1fPeidcfe269UqtEOoltnUyF0gnha4of6e0btWZVxjX8qatpTBi3d7L8mSZv+le4aPrYwW1GzT0gEkqbift7w8ovZbxcmuG8arevrh18RyQjvqnYV/eGd5v/6epn0+8wrAgd3hsVF6R9tPsX2p1wy1bETR+6I3FmvmEH38Ii/yV4ae7PRTMzgPKJThBAqteWbLFJw2VWXKjrnXsTDy+X/wOGgF7r
-sidebar_class_name: "delete api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Soft delete a Tenant"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"delete"}
-  path={"/tenants/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Soft delete a Tenant
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./soft-delete-a-tenant.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./soft-delete-a-tenant.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./soft-delete-a-tenant.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant.mdx
new file mode 100644
index 000000000..eb28b37de
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant.mdx
@@ -0,0 +1,5 @@
+---
+title: Soft delete a Tenant
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml DELETE /tenants/{id}"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/start-wallet-registration.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/start-wallet-registration.ParamsDetails.json
deleted file mode 100644
index 2d6b81d62..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/start-wallet-registration.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"token","in":"query","description":"SEP-24 token for authorization.","required":true,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"transaction_id","in":"query","description":"SEP-24 transaction ID.","required":true,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"lang","in":"query","description":"Optional language override for the webview.","required":false,"style":"form","explode":true,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/start-wallet-registration.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/start-wallet-registration.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/start-wallet-registration.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/start-wallet-registration.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/start-wallet-registration.StatusCodes.json
deleted file mode 100644
index f0d83c878..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/start-wallet-registration.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"HTML webview for receiver registration.","content":{"text/html":{"schema":{"type":"string"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/start-wallet-registration.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/start-wallet-registration.api.mdx
deleted file mode 100644
index 179aef79e..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/start-wallet-registration.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: start-wallet-registration
-title: "Start Wallet Registration"
-description: "Serves the SEP-24 interactive registration UI."
-sidebar_label: "Start Wallet Registration"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNV21v2zYQ/isEPyWAbDlGtgH+li7GmrXrsjpFP6RGQUtnizVFqseTXc/Qfx+OkhI5dpymL8D8wTbF43PPHU/3spWkFl6ObuVbWGhPqEg7K6eRTMEnqIuwHMkJ4Aq8oAzEZHzdG54LbQlQJaRXILBzVry76stIugLq9VXKx0khvVfGAO3oiWShUOVAgExiK63KQY4kuSXwrmbdn0vAjdxjVNMIkmLuUKiSMof634DMFBA+lxohlSPCEiLpaWMYfO4wl5GEL4VxKdztJhnkSo62kjYFi3lCbReyqqJ7WqisZ5ud/ajTr+N3f0RcXf4cWkbZxXEyf4c/yggWLdUChFsBok4huI6vdQ2zlYb1LsO5Mv47KE4ZyxfOevC8PxwM+GeX28ubv1632gMbhAT0CnAnrJhX4iyBpaAJvlCcUW548TiBqork+SGlL1Qq3sLnEjztAquiMDoJKuNPnmUP4LvZJ0j4YIEc56Rr8wDR4T6Nh5dxCaS08ULNXEnB9/XBij1LqPyTmqr6w7ad7dv2zravAqQ/3bivJy09KSq7crbMZxDszsF7tYDDVxhUqLww0OEh3zgSO3be02gVnQ/OOtAPT7Q+9JCUqGkT8s9kfD08/4ffoYuSMjm6nXIQ50CZ4zy2gGCW4i0Zr0NC63XDNPac6SSj4qpNaiUaOZKSkVplE/Z67ZYXoBCwVndnvir0K9h/jy+6OU5koFJAwRestNV2IZQVk8tr8ef7G3Eyngx/+fVUcGYMTz+Ki+srsYQNv0pN5tjBa1NIDcvXMhlfnw1+ELNQN84GNbfaZrEN2bs6fRaj4fmPZDQ8/xGMOhHzFK0gKu7K3mOMOgQOFEOOW23nLqjTFJLzhMAYheJS+1mJHnKwJK6NIs7afPcykhySNY3f+oP+gOO0zHOFGzmSN1zbj2KcTC6vT4X2QglyzohZqQ2FlO1woWzjIi/IiVwtQcxKsxSF2jBKeKrEAl1ZCDfnJK8LHTa4FNWdRaPdAq0dLvt7vvv/UfxgP9ibTPug0gpXgO15V2ICokDHaVBQpoi3ayrOCnIB/gBcJJRNw0biUhCJsmLGFbq0aTiY8cIYt+ZoQSic1+RQgx8xj5649TVe3Pz20o6TekXjpN5MJUuw6fQkIyr8KI4XmrJy1k9cHj8L4XQkgvF3VDZtONetYiMWrNJ2jsoTlgmV2BjY9h5H77T/DMvmGIrd95jWQjxl2xpmopX9ZmsyMHkvyRSSP0q5IxcTAsS50jZuHhy15ykzXoLJRQAK/FMojNtweD1piSg9y70qZ4AWCHz/A2cpAsz933MeGHTCeak1q6HZd7iIg1DPzXu+EYuk0QlYH0p8m3gLlWQghiFP1TWUsUZxvF6v+yrsBrTmqI9fX/0+fjMZ94b9QT80h5wnC+cpV7YDHKYRUY8j4sE8spNwtvfN0/MnoKYMhE61MEpbrhbBjG3TQdzKAx0E5+TQQ0wjmTlPLLbdzpSHd2iqih/XNYA7i1R7NTOdTv1R+idvm6b+VDw9OR2kvoRNpxitlCkhdDXRd9LYG5COaX84gH0jjefNQ0cINaPXPY0pL1Azj9A9Rm2rwNdVn7lIEiioc+p+mNlpNv8Y38hIqr2uYhm6iuYPw7ZbdtMFbS6q1snf7KKDottt3atU1Z18vfXoiXbKrIXZIdOqqv4D+jGymw==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Start Wallet Registration"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/wallet-registration/start"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Serves the SEP-24 interactive registration UI.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./start-wallet-registration.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./start-wallet-registration.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./start-wallet-registration.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/start-wallet-registration.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/start-wallet-registration.mdx
new file mode 100644
index 000000000..1a94d8092
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/start-wallet-registration.mdx
@@ -0,0 +1,5 @@
+---
+title: Start Wallet Registration
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml GET /wallet-registration/start"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/statistics.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/statistics.mdx
new file mode 100644
index 000000000..374b308c8
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/statistics.mdx
@@ -0,0 +1,5 @@
+---
+title: Statistics
+---
+
+Statistics endpoints return general aggregated data per organization, as well as disbursement-specific metrics. SDP users can use this data to monitor their disbursements over time.
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/statistics.tag.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/statistics.tag.mdx
deleted file mode 100644
index 3586c69ff..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/statistics.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: statistics
-title: "Statistics"
-description: "Statistics"
-custom_edit_url: null
----
-
-
-
-Statistics endpoints return general aggregated data per organization, as well as disbursement-specific metrics. SDP users can use this data to monitor their disbursements over time.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status.ParamsDetails.json
deleted file mode 100644
index bae8b948c..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"ID of the disbursement","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status.RequestSchema.json
deleted file mode 100644
index c96bcede2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body"}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status.StatusCodes.json
deleted file mode 100644
index 40d44d85b..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Message Response","content":{"application/json":{"schema":{"required":["message"],"type":"object","properties":{"message":{"type":"string"}},"title":"MessageResponse"},"example":{"message":"Disbursement started"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Bad request","extras":{"status":400,"message":"Disbursement is not ready to be started"}}},"example":{"error":"Bad request","extras":{"status":400,"message":"Disbursement is not ready to be started"}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Disbursement not found"}}},"example":{"error":"Not found","extras":{"status":404,"message":"Disbursement not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status.api.mdx
deleted file mode 100644
index eab97dc8d..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: update-a-disbursement-status
-title: "Update a Disbursement Status"
-description: "Updates the status of a disbursement according to the state machine. The disbursement must move from  `draft ` to  `ready ` in order to start the disbursement and trigger payments. Payments will start as soon as this endpoint is hit. A disbursement can also be moved into  `paused ` state by an SDP user to prevent further payments from going out and restarted when they are ready."
-sidebar_label: "Update a Disbursement Status"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWN9v2zYQ/lcOfGoA2XKybAP05jYpmnXrvDrFHtJgoaSzxVoi2SMV1zP0vw9HyY6cOEmztdsw7MU/pLuP33dH8o5cCy/nTiQX4kS5tCaHFWrvxGUkcnQZKeuV0SIR72wuPTrwBYLz0tcOzAwk5D03kFlmKFd6Dt5sLREqmRVK4xDOC9x1qGrnoTLXCDMyFcBVTnLm4Yr94YpQ5iu4AqXBUI7ET52X5AP27sg6B09qPkcCK1dBxBAm3S9YqrLsXKUDZ4zmb18oB6hza5T2oBwUyg9hvIucSQ2ydAZSDExzUDqws7J2mMNVJzJdgdQwPZlA7VqqlvCaEWY1+aLHq9U6NxwnU7fcCQM7zGFZoGZ9K5CEEEIwFJEwFklyLs7ybTbG/ZxNQ1JEJKwkWaFH4rSuhZYVikSoXERCcSat9IW4nd6zE07n7bCKSBB+rBVhLhJPNUbC+VXJeE5VtkQRCfxkS5OjSGaydGyQFVhJkayFX9lg6UnpuWiaS0Zz1miHjt8fjUb8tUvkJ3ROzhHedpYiEpnRnskkayGtLVUW4hB/cOyw7g14w/VCVC0OT+SOh0k/YMaSLHEwvWpZbAz3EI6EVz6o7VhtSTWsW4YI9CF2FhF0GRVNw1DH+9Q+lzm8xY81Ov8UoQ8rQiJDe/QwZ0/SPY7QLvCena6rFIkhHghXsxuVjkbQSFuNNxQ2gxyPRtF9IVQOtPHtKuAllWI/qn/zcG0WD+9m8Z2WtS8Mqd8x/8+m8Y3xsCNzX2gP+6G95fE1gdvUfHM3NS8NpSrPUX/9vOxXd0PgMwxaGcd3ZbDil6bW/+3pNesU7psAx/cuWr31/MrYAd5hVpPyq1Bbn6MkpHHtC5FcXHKBq9AXJm+rbFaEaswvRdwvqy5eq7yJ3aZiO6TrTbmuqRSJEIy1GWrKGW1D3h9wG1pp1Wtc3Snp426FhOkBBUruoHjySKW59ei6lR9+PYdnp9Ojb787AEPd099gPDmDBYbWo+sgdvA2zUQLyymfnk4OR1+IGUxPJ4PDUcut1Qxrbxaom4MnMTo6/pKMjo6/BKNfaqTV59EKprBt6O5j1CMQKG0G/sjuYd9RembCcF0/M/VYlpJgZ7JPSulnhirOvYgET8mWxvfD0XDE87SuKkkrkQhu5B/GeDY9mRxwQZXgjSkhrVXJa4nA0FzqLkSOq2wlFwhpXS5uOmRvQMKcTG25LSXMlFXhhbnm3ro3uka/NLQY3ondv4/ie/1en/ORg4fUYCzqgTM1ZQiWDG+x4AsZupCWitHgjd005rfgovbMUyBkJsdwTEmx3ayCY8F/ytIsebYQWuOUN6TQJcxjABeuxYu770F/hxrYLkiDVGYL1Pnls8J765I4nitf1OkwM1X8JISDBIL4LZXVZjq3h8rOLKhSekbSeaozX1MnkPPiH8vp8AnKZhQK6V+RtoF4TNsSU9jY/mk1BZbVICskefcg5Z5d7AkxrqTScffgQT2PyXiFZQUBKPDP0ZZmFU77j6612rHd6zpF0ujRDd/zLuWRKvfzbIp0rTLelzayOppDQ/M4GA3MbOA6s0iUKkM+hiXb4+3YyqxAOAr7VFtDGSuJ4+VyOZThbUDrXF3849mL0zfT08HRcDQsfFWGfdIa5yupe8DtSRvkrq7tYXtnz1nf9Gb/35f8w/clXWH1+MnHtpRKc/0NE2Pd9WQXYqcnE5FIwiVJ15ZdRqIwzrPdep1Kh++obBp+3JbV5OIyEteSlEy5pF6sGY5/59urkHsnx7O33U3FAdx78bJXwKZd0NwrXMuy5n8iEgtctXc8zWUTbRoO5tS+GGcZWt9zuXNw2OldJ+PzF69EJOSdJmURmpTuB+PvJXS7C2pJ8GcT3eOyXrctUNNs7dtX93p0IrfaWUPTNH8AW6xS0A==
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update a Disbursement Status"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/disbursements/{id}/status"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates the status of a disbursement according to the state machine. The disbursement must move from  `draft ` to  `ready ` in order to start the disbursement and trigger payments. Payments will start as soon as this endpoint is hit. A disbursement can also be moved into  `paused ` state by an SDP user to prevent further payments from going out and restarted when they are ready.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./update-a-disbursement-status.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./update-a-disbursement-status.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./update-a-disbursement-status.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status.mdx
new file mode 100644
index 000000000..228bf9d27
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status.mdx
@@ -0,0 +1,5 @@
+---
+title: Update a Disbursement Status
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml PATCH /disbursements/{id}/status"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-a-tenant.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-a-tenant.ParamsDetails.json
deleted file mode 100644
index f62d61c53..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-a-tenant.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"ID of the `Tenant`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-a-tenant.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-a-tenant.RequestSchema.json
deleted file mode 100644
index cf2bb8cc5..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-a-tenant.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"description":"List of fields to update for the tenant","content":{"*/*":{"schema":{"type":"object","properties":{"base_url":{"type":"string","description":"The SDP backend server's base URL."},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL."},"status":{"type":"string","enum":["TENANT_CREATED","TENANT_PROVISIONED","TENANT_ACTIVATED","TENANT_DEACTIVATED"]}}}}},"required":true}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-a-tenant.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-a-tenant.StatusCodes.json
deleted file mode 100644
index 91064ccb6..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-a-tenant.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Updated Tenant details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"name":{"type":"string","description":"The tenant name. It should match the pattern `^[a-z-]+$`.","example":"bluecorp"},"base_url":{"type":"string","description":"The SDP backend server's base URL.","example":"https://bluecorp-backend.sdp.org"},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL.","example":"https://bluecorp.sdp.org"},"status":{"type":"string","enum":["TENANT_CREATED","TENANT_PROVISIONED","TENANT_ACTIVATED","TENANT_DEACTIVATED"]},"distribution_account_address":{"type":"string","description":"The Stellar account address used for distributing funds.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"distribution_account_type":{"type":"string","description":"The Stellar account type used for distributing funds.","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"distribution_account_status":{"type":"string","description":"The status of the distribution account used for distributing funds.","enum":["ACTIVE","PENDING_USER_ACTIVATION"]},"is_default":{"type":"boolean","description":"Boolean flag that shows whether the tenant is the default or not.","default":false},"created_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"deleted_at":{"type":"string","description":"The timestamp when the tenant was (soft) deleted.","format":"date-time","example":"2024-03-27T17:21:51Z"}},"required":["base_url","created_at","distribution_account_address","distribution_account_status","distribution_account_type","id","is_default","name","sdp_ui_base_url","status","updated_at"],"example":{"id":"840dca45-d1df-44cd-83c1-65c04235c25f","name":"redcorp","base_url":"https://redcorp-backend.sdp.org","sdp_ui_base_url":"https://redcorp.sdp.org","status":"TENANT_PROVISIONED","distribution_account":"GCQVDMPOEN3HHJJ64V42KUTONOXN7C6V2PSVPALEVJ7PIYOB6M3DJV7N","is_default":true,"created_at":"2024-03-27T17:21:51.000Z","updated_at":"2024-03-27T17:21:51.000Z"},"title":"Tenant"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-a-tenant.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-a-tenant.api.mdx
deleted file mode 100644
index 23c93ebda..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-a-tenant.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: update-a-tenant
-title: "Update a Tenant"
-description: "This endpoint updates the Tenant data."
-sidebar_label: "Update a Tenant"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWelzGjkW/1dUqq1ae5bmtsnwDQOZ4AMIYJKJ4yWi9dqtcbfUI6lDGBf/+5SkbgMGH8k6W1vrL2D1O37v6HeIO6zJjcLNK9yiMeP4uoApKF+yRDPBcRNPQqYQcJoIxjVKE0o0KKRDQBPghGtEiSZFXMAiAUkMU4/iJr60hC1Hgws4IZLEoEEaXXeYkxhwEzOKC5gZNQnRIX6ou9dBIrC6vjhBX4wiCX+mTALFTS1TKGCll5ERplicRIALGL4lkaCAmwGJlCHwQ4gJbt5hvUwspZaM3+DV6tpJA6VPBF0aim0A50xpAyFgEFGFtMgcgAIhLS6d2+cLroFrI+KX0i/mY0ermP8BvvWFNL7SDJR5OicKZqmMdvHthgLQuDNEc+LfAqdIgfwK8p8KGRHocnRexKsCVjSZpWz2/WIveyVKVDgXRFJ0siVSE52qfZKAp7FJnkm33+pPZu1RtzXpdnAhPxiOBtPeuDfobx622pPedJuu010fXq/M38M42wOVCK6c26rl8m68XNbR+9QETViktsNDkiRivs3U0h/KsL08VozudcI3YjOviSuN2vEcaM1rzH+tevXGcdl7EwRV76gSzMtvAMqNXwPjUJf+LwmMSzBkGIqop5EKRRpRFBPthzYDE6I1SI6+/PuKeH951//6h31J1pjmUQq+kInR+6q5tqkk1DpRzVIpV+ZlfEVFk6KQNz8jMZ/Sv6X3v5y9BUyZUTFPjR0z4vsi5XpGKJWg9uLYY7aGKCISZcwoY0apAmqLz1oFv0FByqnadshv7Y+t09rH09r0rHb69l3t/UXn7WB8dlHtX1x8OhkPatPe5Lh7OXz/Ydz5UD1t1C+qtdFofI4fg+8w/wh2w/Es8CwSnd54MuqdXE56g/6s1W4PLvuT4njSPT9vjYrd/hQXnibpnMymrcvzyWN07d6ofd5dkz0arceTZtdgR5u3qk1x9z54ofk2jbq4gIfdfqfX/212Oe6O8ozrDfoWL1MzCgFJI70Bby5EBITv4Dtx5yiIyA3SIbEVZKHQIgQdwmYTQ8y19Uw2EhJxoYtWYqbN9tNVAfsSTJmdEb3PQYGQsXmCTS32NIthKzOr5WrdK9e8amNSaTSrleZR5ZPJOtdZX1kohQgeF7qn3LIYlCZxYhzEN72zIAodKBHoQ5QJLf4orK3edrUuyluOfaaKPJ22T73DhWzqWmdR1o92K/R97dyKzvWGha4l4jf1MvVJ/cijFRp49bpPvTc1v+IdH/nlerV25FePglxNE0ugtiFt9qP7Cp493Gkge/rHQ55N2uz13V/J9znH1sz3087FcNDt1969Oz09rk/r1bPLyaA/+NhvtI+n1eF4Omydd6enjWHv98HJ8UWtczpt9Le9mU2lm+/IvjwolsvlT9uOfYJuVcCaaZtT2UjtZqT6vinohFA0cmPt640+IKWQz79EHTdyITIXqbbvj2NcmaTRkqhnNa1Wq9y2yp4Jj5NUh0Kyv4D+dONeDnp3yOBpPAdrdwxKkZs9zdOZufEuZTBwX2i0ZeYaRa6nXq5sSH7I8TMFu9DUd0NjSN+KlP9fxOVx/wWZiftcV9903QiUSKUPpo1mXHlqK/BTyfTS7sInRDG/leoQN6+uzUr6zfMFhRvgXracenNBl15WPc13px64YoK7hfoWlrj5JGcBfyVRei/BKIpBh4K67dsP7ZZuUOCS63mqdMfoylRTO/w7Ra7yWvbcirGJpnP3CRAJ0hlz71aSsDNY7pSKVpZWNjVQCISCRCZxCONmOiLcTv+nHybooDuuHh0fmpnEnc5Qa9hDt7AsrtvKlrz8XsGJNeEed4eV8ishQ+Pu0KuUHTZnM7rT4hb46vC7EFXrr4moWn8NRO9TkMuXwbKk6P5u5zFEGwAspFzxn4bdzkOMB8Kqy5pcvkN0mJqnUkEMXKNhRLQZuEzsTTqDVA5Go1gulk2epnFM5PLBHrJfxsG4Mzw0My9BWogIzVMWaTuiC3lDeOYie+cTk1tA8zS6RQlZGin2lKAbKdLEjP0SfJYw+0B8zYbqXDsHvRDytvjkqvS/AfEz/8ztdZ9RyZFIgHtZCUukMOXVbRBMZVAER1ok+eLzQFwBEU7tA1OTkE84moOrg5YxNP9EkViYbJGQCMW0kAxU0+Dw0JVy8krZp0c3nOQlmZPyOfH6IB8Gb5gO03nRF3HpuyQcNpE1/h7KMk9ntxflNyHGKsYDSZSWqa9TmRmYXwk+GdPid1gWSNtE/xPTchHP2baAOcppf9iaEKLY80MitXoS8gZdSUuAUkwYL2UHT9rznBnvIIqRFeR2bUgisTTp9awlKFWG7iydg+SgQRU/myqlQcZqEIxBfmX+5j1TBtNsGyVL5InAUxlZAUfMB67s6JAX3oT4IaCqrVPr7aVZKi0WiyKxT620jFWVznvtbn/c9arFcjHUcWTrZCKUjgnfEOyuPBFB91ftW2Xmbj2KvfwqPyv6Gr7pUhIRxu1+7q7s3IhwhbMRARdwk1GzE4ZCafPg7s5saJcyWq3MsavxzatrM39IRuamvl/dmR3MfKf3t/SPwj4YZcvyIdr/g8BeuHnj4suNyQcXskGJUbwydylZ61tPUG2n1pu4VTlnNHf6q0JO1PJ9SPTG450Zd2u6GrYm7Xdm281+Y4jtjxNYkoX5NYMs7Dy1Wv0N0zG4Cw==
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update a Tenant"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/tenants/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint updates the Tenant data.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./update-a-tenant.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./update-a-tenant.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./update-a-tenant.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-a-tenant.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-a-tenant.mdx
new file mode 100644
index 000000000..30a68e0b1
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/update-a-tenant.mdx
@@ -0,0 +1,5 @@
+---
+title: Update a Tenant
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml PATCH /tenants/{id}"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-api-key.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-api-key.ParamsDetails.json
deleted file mode 100644
index 807944a20..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-api-key.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"The unique identifier of the API key to update","required":true,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-api-key.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-api-key.RequestSchema.json
deleted file mode 100644
index 13164e642..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-api-key.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"application/json":{"schema":{"type":"object","required":["permissions"],"properties":{"permissions":{"type":"array","description":"List of permissions granted to this API key","items":{"type":"string","enum":["read:all","write:all","read:disbursements","write:disbursements","read:receivers","write:receivers","read:payments","write:payments","read:organization","write:organization","read:users","write:users","read:wallets","write:wallets","read:distribution_wallets","write:distribution_wallets","read:statistics","read:exports"]},"minItems":1},"distribution_wallet_ids":{"type":"array","items":{"type":"string"},"description":"IDs of the distribution accounts this key may act on. Omit the field to leave the key's current accounts unchanged; providing a list replaces them. An empty array removes all account access. A key cannot be scoped to an account the caller cannot reach.\n"},"allowed_ips":{"oneOf":[{"type":"string","description":"Single IP address or CIDR range"},{"type":"array","items":{"type":"string"},"description":"Array of IP addresses or CIDR ranges"}],"description":"IP restrictions for the API key. If not provided, existing restrictions remain unchanged"}},"title":"UpdateAPIKeyRequest"}}},"required":true}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-api-key.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-api-key.StatusCodes.json
deleted file mode 100644
index 3e1341556..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-api-key.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"API key updated successfully","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","description":"Unique identifier for the API key"},"name":{"type":"string","description":"Human-readable name for the API key"},"permissions":{"type":"array","items":{"type":"string"},"description":"List of permissions granted to this API key"},"allowed_ips":{"type":"array","items":{"type":"string"},"description":"List of allowed IP addresses or CIDR ranges"},"distribution_wallet_ids":{"type":"array","items":{"type":"string"},"description":"IDs of the distribution accounts this API key may act on.","title":"DistributionWalletIDs"},"expiry_date":{"type":"string","format":"date-time","description":"Expiration date of the API key"},"created_at":{"type":"string","format":"date-time","description":"When the API key was created"},"created_by":{"type":"string","description":"User who created the API key"},"updated_at":{"type":"string","format":"date-time","description":"When the API key was last updated"},"updated_by":{"type":"string","description":"User who last updated the API key"},"last_used_at":{"type":"string","format":"date-time","description":"When the API key was last used"}},"title":"APIKey"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-api-key.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-api-key.api.mdx
deleted file mode 100644
index 40bd8997f..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-api-key.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: update-api-key
-title: "Update API Key"
-description: "Updates an existing API key's permissions and IP restrictions. The API key name and expiration date cannot be modified after creation."
-sidebar_label: "Update API Key"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWVFv2zgS/isEX64BZDvJ5fYA31PaZFFfF1tfnKIPaRDQ0tjihiJVcmjHa+i/H4aUbFl2kqabYhebl9jkzPD7hsPhcLzmKOaOD2/4+XjEPsDK8duEZ+BSK0uURvMh/1RmAsExoRk8SIdSzxlJ38PqH46VYAvpnDSaJDI2GjMLDq1MSd312XUOjTjTooAgBQ+ltIIkGBlnqdDaIJsCK0wmZxIyJmYIlqUWglifJ9yUEHVG2QbW+Xj0AVY84aWwogAES2zWnFbiQy4znnBJLEqBOe9SI2xey68emMxAI61smZkxbIFGw3xYiyfcwlcvLWR8iNZDwl2aQyH4cM1xVdKCxFzPeVXdRmFw+NZkK5JIjUbQSB9FWSqZBi6D3xxBWe+bMtPfIMWdRW94y920U6Ulp6AER4rtya0dYa1Y7VH/RTokpu39m1uhETJijLl0jQfIhQiF26eZcNC+IFwWRDYUSvGEL61EqD+H4Uy6qbcOCtDoNgLd0SBqIQW5oE1sxNojQaQUq11DrYEgYOxcaPl78O5GqDMYBL1rL9R8C1NLoRS01th+bxihlVNP1u66so9MBkWHAukIpZsReCiNRcdvq4QXUo+io0+qhB+wcyezQzv7yO5U3T0fXbgmuNvGmUhT4zW6uOsU84VYMZEiM7rPPhYSg85MggrBoUAsIAzFHJB6a0Hj1o7XaS70HLL/sNKahcwoZwimKOYslEqkQItB0WfnmkFR4ooFMsxCYRaUbJRqzNF/cK7PzgO0bapwqSljtIoNh4AqJWfZRtKCSPP+F03+EEqZJWR3sgz+Mho+zkK+6Mb1ruMmUs8VUG4TWWbBOWYseze6uGKWaPIq+e49OQ+0zaxlHDrmHa/2knInzbKZse2k1WejGSPy0f2QJdvcvaNnoRBSbzeMV1XCUaKCToq9ismMVySwmwbDgCuNdjENnR4f078OzzqbxlSaMefDrs68UuSu706OuxlQZoeSVOc+20v4HefRJsX74zlT730hdI/OsZgqiNfbAWNP5+VvjZSXZOz9UP+Di9bWno7SPy9nNdHVylt8G8cXLcXPAdToIsANZcjqLlzuBzZ7ZmwhkA85CfRQFrAXAZedQma3dqA1QgUD2Z3A71zicw56pyBZCsdqq+0FpqtviH0Hli1z0+h3wdan85XBKuGwOfjtVV6EuG2kC5vm7rz7QcBdJy3WNWcVUuHZoWT3VmSsSZivltvAWmOfd9gFoJDKMTE1Pl6HUTGEO1rhnl2pin/E7WSf2yctPObGyt8h++Hkvh00p9LKt+W0L6YQeBfgnJgfOOI1T3gQRamghYP/apDt8NzCaBY6Oz5pme5qbFz4z30X/mzsVGYZ6B/vv0fobRE0MM/2YRKjn43Xf/NtntUUD+3wWXuHr8AZb1MIhVXUak6Kg9RbiatQS74FYcGee8z58OaWarcCMDdZfIWmeXit0iQfiFL27mHlBmuZVZzs2EXzhPVW8SEPtV9jfkJujn5oL7K9XEsZX8Od2qsOy3hP5SAyqo6NRiF1qMw1m1yM2X8/X7M3l5PTf/10RFd7HL3blJS8qYp27TUP7GiW9mFyOT45fiVkbHI57p0cR2yRM1ujuQddHb0I0enZayI6PXsNRP/zYFffBiuIsk2T4zFELQABUrPwV1IPlxid2KttY+JyeyZ2qtTWi/72ibLupjlit52Cs3WypZ6ZQLC+PicISgnLLloNADZWAumWpmjjCadDEIn/u3/cP6aT4YtC2FXdtHnaxpvJxfiISccEQ2MUm3qpMBTm7TaAo6q5EPfApl7ds6aNEN6TbG6NL6mas5DKUoYJs4BY2jera8Clsff9g32lvxbEL/qLvqZKWYZGnilB9+psVlpDmZZhLpCmIxSjGZqyqWc75pLQxAtPbZOF7h29x0NKDIrULDAUDvG9WRon0VgJbkg4euzGRXuD+n+v3QzqlbWTelOR3oPObt/kiKUbDgZzibmf9lNTDF5k4WjIAvkNlFVzgEIbgtVigZXUMyscWp+itzXB5k335J72X8BsZsN9+keoNSae47aEKWtkv5tNDqropbmw6J6E3JIboAUYUHdhUA88yec5Gu9BFSwYCvgzKJVZUXg9y4R5R3If/BSsBgRHvaCEI9jCfZxNwC5kSnmpoVXD7Bs7HwShnpn1XC2WcCVT0C5kzCbVlyLNgZ2GPBVvbbI1HAyWy2VfhNlgrVZ1g19G7y5/nVz2TvvH/RwLFTJzaRwWQrcMx/4Lq1vz3SzT6ij/dXr09S2G8ICDUgkZum7BJ+u66LnhTdHDEz6UGV0duXFIM+v1VDj4ZFVV0XC8tYY3twlfCCupxxIqo0w6+pzx4UwoB0/45c1V3ak6Yi/u9R+k0tzSmrZjIZSnbzzh9BANPzdU1Mit73nCGifeRUS9a1LfKu6V0tRIjBrnaQolPinbLizH59fv3vOET+sfGwqTkZIVS2o0i2VEaYKLQv0YxtZcCT33sbyNRikSxV5JEn8FqD+0+qW7fujWPJFJfKM/orJex4KnqjbycepRjdq3G5eTI6qq+j+pFWO2
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update API Key"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/api-keys/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates an existing API key's permissions and IP restrictions. The API key name and expiration date cannot be modified after creation.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./update-api-key.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./update-api-key.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./update-api-key.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-api-key.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-api-key.mdx
new file mode 100644
index 000000000..cc9f3156e
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/update-api-key.mdx
@@ -0,0 +1,5 @@
+---
+title: Update API Key
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml PATCH /api-keys/{id}"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-bridge-integration.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-bridge-integration.RequestSchema.json
deleted file mode 100644
index e32bf7890..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-bridge-integration.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"required":true,"content":{"application/json":{"schema":{"type":"object","description":"Request to update Bridge integration status","properties":{"status":{"type":"string","description":"Target status for the integration","enum":["OPTED_IN","READY_FOR_DEPOSIT"],"example":"OPTED_IN"},"email":{"type":"string","format":"email","description":"Email address for KYC verification (optional, defaults to user email)","example":"john@example.com"},"full_name":{"type":"string","description":"Full name for KYC verification (optional, defaults to user name)","example":"John Doe"},"kyc_type":{"type":"string","description":"Type of KYC verification","enum":["individual","business"],"example":"business","title":"KYCType"}},"required":["status"],"title":"BridgeIntegrationPatchRequest"},"examples":{"opt_in":{"summary":"Opt into Bridge integration","value":{"status":"OPTED_IN","email":"john@example.com","full_name":"John Doe","kyc_type":"business"}},"create_virtual_account":{"summary":"Create virtual account","value":{"status":"READY_FOR_DEPOSIT"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-bridge-integration.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-bridge-integration.StatusCodes.json
deleted file mode 100644
index 87353f10b..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-bridge-integration.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Bridge integration updated successfully","content":{"application/json":{"schema":{"type":"object","description":"Complete Bridge integration information including status and related data","properties":{"status":{"type":"string","description":"Current status of the Bridge integration","enum":["NOT_ENABLED","NOT_OPTED_IN","OPTED_IN","READY_FOR_DEPOSIT","ERROR"],"example":"OPTED_IN","title":"BridgeIntegrationStatus"},"customer_id":{"type":"string","description":"Bridge customer ID","example":"cust_123abc"},"kyc_status":{"type":"object","description":"KYC verification link information","properties":{"id":{"type":"string","description":"Unique identifier for the KYC link","example":"kyc_456def"},"full_name":{"type":"string","description":"Full name of the person undergoing KYC","example":"John Doe"},"email":{"type":"string","format":"email","description":"Email address for KYC verification","example":"john@example.com"},"type":{"type":"string","description":"Type of KYC verification","enum":["individual","business"],"example":"business","title":"KYCType"},"kyc_link":{"type":"string","format":"uri","description":"URL for completing KYC verification","example":"https://bridge.stellar.org/kyc/456def"},"tos_link":{"type":"string","format":"uri","description":"URL for accepting terms of service","example":"https://bridge.stellar.org/tos/456def"},"kyc_status":{"type":"string","description":"KYC verification status:\n- not_started: KYC process not yet started\n- incomplete: KYC process started but not complete\n- awaiting_ubo: Awaiting Ultimate Beneficial Owner verification\n- under_review: KYC submission under review\n- approved: KYC verification approved\n- rejected: KYC verification rejected\n- paused: KYC process paused\n- offboarded: Customer offboarded\n","enum":["not_started","incomplete","awaiting_ubo","under_review","approved","rejected","paused","offboarded"],"example":"under_review","title":"KYCStatus"},"tos_status":{"type":"string","description":"Terms of Service acceptance status:\n- pending: Terms of service not yet accepted\n- approved: Terms of service accepted\n","enum":["pending","approved"],"example":"approved","title":"TOSStatus"},"rejection_reasons":{"type":"array","items":{"type":"string"},"description":"Reasons for KYC rejection (if applicable)","example":["Incomplete documentation","Address verification failed"]},"created_at":{"type":"string","format":"date-time","description":"When the KYC link was created","example":"2025-01-01T00:00:00Z"},"customer_id":{"type":"string","description":"Bridge customer ID","example":"cust_123abc"}},"required":["id","full_name","email","type","kyc_link","tos_link","kyc_status","tos_status","customer_id"],"title":"KYCLinkInfo"},"virtual_account":{"type":"object","description":"Virtual account information for USD deposits","properties":{"id":{"type":"string","description":"Unique identifier for the virtual account","example":"va_789xyz"},"status":{"type":"string","description":"Virtual account status:\n- activated: Account is active and ready for deposits\n- deactivated: Account is deactivated\n","enum":["activated","deactivated"],"example":"activated","title":"VirtualAccountStatus"},"developer_fee_percent":{"type":"string","description":"Developer fee percentage as a string","example":"0.5"},"customer_id":{"type":"string","description":"Bridge customer ID","example":"cust_123abc"},"source_deposit_instructions":{"type":"object","description":"Bank deposit instructions for sending USD to the virtual account","properties":{"bank_beneficiary_name":{"type":"string","description":"Name of the bank account beneficiary","example":"Stellar Bridge"},"currency":{"type":"string","description":"Currency for deposits","example":"usd"},"bank_name":{"type":"string","description":"Name of the receiving bank","example":"Wells Fargo"},"bank_address":{"type":"string","description":"Address of the receiving bank","example":"123 Main St, San Francisco, CA"},"bank_account_number":{"type":"string","description":"Bank account number for deposits","example":"1234567890"},"bank_routing_number":{"type":"string","description":"Bank routing number","example":"121000248"},"payment_rails":{"type":"array","items":{"type":"string"},"description":"Supported payment rails for deposits","example":["ach","wire"]}},"required":["bank_beneficiary_name","currency","bank_name","bank_address","bank_account_number","bank_routing_number","payment_rails"],"title":"VirtualAccountDepositInstructions"},"destination":{"type":"object","description":"Destination configuration for converted funds","properties":{"payment_rail":{"type":"string","description":"Payment rail for destination","example":"stellar"},"currency":{"type":"string","description":"Destination currency","example":"usdc"},"address":{"type":"string","description":"Stellar address for receiving USDC","example":"GDQP2KPQGKIHYJGXNUIYOMHARUARCA7DJT5FO2FFOOKY3B2WSQHG4W37"},"blockchain_memo":{"type":"string","description":"Blockchain memo for the destination transaction","example":"12345"}},"required":["payment_rail","currency","address"],"title":"VirtualAccountDestination"}},"required":["id","status","developer_fee_percent","customer_id","source_deposit_instructions","destination"],"title":"VirtualAccountInfo"},"opted_in_by":{"type":"string","description":"User ID who opted the organization into Bridge","example":"user_789"},"opted_in_at":{"type":"string","format":"date-time","description":"Timestamp when organization opted into Bridge","example":"2025-01-01T00:00:00Z"},"virtual_account_created_by":{"type":"string","description":"User ID who created the virtual account","example":"user_789"},"virtual_account_created_at":{"type":"string","format":"date-time","description":"Timestamp when virtual account was created","example":"2025-01-01T00:00:00Z"}},"required":["status"],"title":"BridgeIntegrationInfo"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-bridge-integration.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-bridge-integration.api.mdx
deleted file mode 100644
index f63ab828d..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-bridge-integration.api.mdx
+++ /dev/null
@@ -1,73 +0,0 @@
----
-id: update-bridge-integration
-title: "Update Bridge Integration Status"
-description: "Updates the Bridge integration status. Supports two main operations:"
-sidebar_label: "Update Bridge Integration Status"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWulv2zgW/1cIfmoB+YibTmf8adM4adN0kjR2pptNAoGWnm3WEqmSlD1u4P998UjKknzk6AEMFjsYtLVEvvv4kU/3NAYdKZ4ZLgXt0qssZgY0MRMgbxWPx0C4MDBWDBcQbZjJdZP08yyTymhi5pKkjAsiM3BrdPdW7DXJeWYaXBAjCzIv3N4uuaXnF4OjXnhydktfkgY5VGBZnl4fkoSLKRlJRaQaM8G/Oa5SDCVTMRfjW9Fp+g3kL65MzhJyEEUyF6bK4PLooHcdHp9fhr2ji/P+yaDOaeZ3Mr+TjQwoy59lmZIzltwKGtCVSicx7dLcWsYpc1KahAZUQ5Qrbha0e3NP3wJToA5yM6Hdm7vlXUAVfM1Bm7cyXtDuvf3JFcS0a1QOAY2kMCAMvmJZlvDIkm190eiPe6qjCaQM/2UWGdAulcMvEBkarDnu0nFBgztJd7uPBjRTqJzhoC0P97jkoY3iYrzBY8DUGIynYt2EYcJrxgCRp7R7s/IxDTa9Qe8CCn+zNEuQ2WrlMqCQMp5sE2QkVcoM7foV65Id4VPC4liBdpKhN2eg+MgblLyQdjFLAhLDiOUJRq8kuQZFLNGXtCrVFzkR//I/m5FMUbpRniShYCk8bqrjPEkILn2+MLirLssHORGkJwFlmC6i0LF+1FuLDIgcbTCvOImLmM94nDO06DDXXIDWde+sngbUcGMfnV4fIm26XAaVaL4pwuiuXLmRLRfMRBMfqtbfjo+NPZmZkLuYz9OUqQXGRmYwvuSWYKYBnbEkh2oAV6POh9KmI2t+LG1bNW2pNeoY2bIR+qoR+qpRF9TXpLXKslXGzXRY2v/QmDqTQjtzdNpt/Kvu0y057bI9JjqPItAadVvQn1ZWDiXabXs14cJlpft3lORYoYvqwERMFCRWtJgZ9t1F5zBXCsSq6sjRjt5UCeuz80F4dHbw9uNRjwb2VyUuHixMAT26vDy/3FGgHgjsvtMGoyXXRqagQh4/rpxXo9hDTnq1xMfn4V7nFRtGRe5vmG2H4zZKjm2tFZdtOOQp8l4J/jUHwmMQho84qFUXKLp3TX4UeP/1bzGMvrt8en9noDQGu4hBjSXG2en14c4i+evayKM94p9Sm120WI88ZIdc8U0nX360ukcu972xd5thYkymu63W0AZzUxtIEqaaUo1b00XUKgPASP1jErEogswKZEClthhoUDMewVMFMlJXBNqaUDtctpFQHm7eigYR0iAdZSDuWltlSmIxxhdk4SATvsS1XHi7Qn2pX0KGubHbilW4h80ZR7XDfCi75MD/IleJ4amFeiBgxCPOEnI+F6BqgiIBmzehghmHuWOr82HKteZFUhH30nKzILhQpaZz8QqXKcDCs3VZ8QqXZSzX62Zxz/CtHI0stscVh0UVLB/eVjOiYmUa0NKONKBVA9GAVtXFt15qii3WSYbVzwqBOH/Frp5ea1QqKVZWewzpJ8PnImb7LmZ9ODMRQTWYMhDYSLtksBbjq2hy+5wBS2dtLC+XVYzoqVetUlO6YqtC4cF5v1TYGZBLESpgWoqq3kwphtiDG0i32GO5eWaxFFaFdkWbvOAj4mHLMKmj4Rt6svI8iWWUpyBMUZQOfOmuReOI8QTVXEG5OGTmwRqEiKpheAobPvw8AVHrd2TONPFka0Wo0+68brT3Gu29Qbvdtf//55figzU0zuMa0g1WLc9yrLSHSl2uVcRacNflvqtlw0cupidiJFG7LSD5YZzy19pZvAoqMS6u+j0SQyY1N5sH1x+DLJtgvbTsjIVvfv/j78U3VOqpCb6uSyWpWWT4jNlqWdxXcO2egsfKLF5Y0QptcVsM2zdWnteye/XUylb+qqd4ZVHhRi+6Z1GmewwzSNDk4QggzEBFILbmTt0SvWIbGYEFb7iNjYEwTRhZbSplajdf/2LwrGWuIgi9dUMutFG5rTZPQNNvmZgWjiHVrdZj2tVUG6tG7oiteuQOmZiGw6Jtq8UTcfFZBRIjiVWoVUjVjNB32Mefl5yJ8TwVLZ568orqUVmjnusYSVplnq+Aggj4DA2HBGqEP0OSaHLM1FiuGHhY/jiPogk8zmav84r8ibeXfROQPhPkWDERcR3JgBwelJydkUORp0NQTwjMqmfcpt023Ou82n/925vf/2iv+CmZWzDzLH5+k+e3xmKv3W539n9HDhlbYMcMFePJjzRvfwUMMfEUiaW4U1EsThMa0DlXQO/Wu9X2fKhEazXK1gJiu5e223Jd/7tdJbDnVDiplglnA8OFgxuPVo1euZhEUoz4OFdlZ4ukmIE14CgX8WZzqwr6eAxcVJzgfVBKWg0Gfxp6XimoaVK6pFYJbJV9cpIWhal62C4z9arfq5/u3/U+XXROLz69Oz15f/3h3b/Prk6uz/98f3B5dXB5ePCm92Hw+vi8c3x8fn56/ept53P/0/t3+59fvbE5lchoGk0YF2EKqXxCPq02ENywAgwVkxKjmNAs2jCvTecNMFbzZS2qC4M9EIilH7divBVC296r60314T5Yj++dIhVgT+LpIuQiHD4hhK60bdFkPpHEbrQmrc15Kje9a8EFCuFYjed3Q/gBT0EblmZkjmC+Pmmygu2SYxekXwO9YXHKeK5Z/L5HwWnVHrt4/yzzrM/Knnfcef6EwMWWvQ7fb+9t3oBfCZabiVT8mxXgu6+567UWlJJbGq2dUBjFtiLER66zfcNZBjQFrdl4Czjy1/4rI67koGfSkJqepRgFo/32XoX0+o5lYcJXmyY8lmrI4xjEr7ffDvVKCQox9zfFRI2OZS7+x9088ipu8/B+1cOX4Eq3vQZyu4rBkWFjjfnlT0TV8fQdkjATiSPsDKdvFgLhdJr6+9EGX5tmqxkobYfZucIJGsUpdjHk7qOpnS2qo+4SRmb8FBabmNyHpiuzE2B45YheZVxgw2eC9HsX5MPnAXlx1O+8/u0lwfte+zQkBxcnZAqLJg2oH9vV6NnbQLz3tWTRF/2ji732T5KM9I8uGnttJ5vTmdwbOQWxfPksiTr7P1Oizv7PkOhTDmrxNLHsUpIxxVIwuyWqCGBFKhh/xe22I2DWXpYfRRyVefEL57goxchhP996CgTa43qYKw0WPl8kzGCTxJDD6S0o7bR/02w325geq5HvYALkYRov+r2Ll/aehxgpEzLMeWI2Pm+xk/+UTYEM82RanKbsU0bGSuYZnmQVRDzj9oWcgcOjBXcBZi7VtLnZy/9xIt6KWzGYcG1Z2q+GRMOXtUxJLLnETJi943KiINSWWXGWXyMX2KszfBHJGEjEBBmCq4124wR/JImcY5Aqh3il4oB3cni9duMPQy3/dyOuGKmReSM1hiyagojvXhSDpTE3k3yIUdh6FoWXXWKVX4myKLJI+ysdu8xqxcVIMYfNc+UVLA4iD/q0+QzNRso21h9RrSDxmG5zGJJi7XdrM4EkbUQTpox+UOTKupZRAC38Rq3lHzyoz2NqvIckJZZQcdORyIWdSD6aa1iLxuQ0H4ISYEA37dWtnWSej/xMqDK9rI0tcVFDjhrluDPhEQhty2ZR7zMWTYB0bJ1yrRtpdVut+XzeZPatpea36tbHk8Ojs/5Ro9NsNycmTWx5zqQ2KRMVwle1D8oq6IL0y7Nnpe7cl3jt/x8UVj4o9E3JwN+mlSWMC2xL1lH3HpPd0C2Y7C6gE6kNvr2/HzINVypZLvGx66ndmzv8zkhxnJXZrw6Dos0jiJuC/UDJeaQxcNMf/1nSJppeBsWOAzs+fHBtFVxeHAwO3+Otm//OMZUxblIMZ6f4Z5fabypXN+722T1NmBjnDuE6ohiDbAORTC0i8f9AtYpXYlERcR3yOE3wT9Rr65b7e4d3lsvVevdq5w5v22I1uvFuuVz+F8p6I+g=
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update Bridge Integration Status"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/bridge-integration"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates the Bridge integration status. Supports two main operations:
-1. Opt-in to Bridge (status: "OPTED_IN") - Creates KYC link for organization onboarding
-2. Create Virtual Account (status: "READY_FOR_DEPOSIT") - Creates virtual account after KYC approval
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./update-bridge-integration.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./update-bridge-integration.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-bridge-integration.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-bridge-integration.mdx
new file mode 100644
index 000000000..ee053f7fc
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/update-bridge-integration.mdx
@@ -0,0 +1,5 @@
+---
+title: Update Bridge Integration Status
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml PATCH /bridge-integration"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-organization-profile.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-organization-profile.RequestSchema.json
deleted file mode 100644
index bd63d6633..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-organization-profile.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"multipart/form-data":{"schema":{"type":"object","properties":{"logo":{"type":"string","description":"The logo of the organization, file type must be png or jpeg.","format":"binary"},"data":{"type":"string","description":"A JSON string that contains the details to update. Every key is optional; only the keys you send are changed.\n\n- `organization_name` (string): the new name of the organization, up to 64 characters.\n- `timezone_utc_offset` (string): the new timezone offset of the organization.\n- `is_approval_required` (boolean): whether the approval workflow is enabled or not.\n- `is_link_shortener_enabled` (boolean): whether registration links sent to receivers are shortened.\n- `is_memo_tracing_enabled` (boolean): whether payments carry a tracing memo.\n- `receiver_registration_message_template` (string): the message template sent to the receivers inviting them to registration. Up to 255 characters, and it cannot contain HTML, JS or CSS. Sending this field empty sets the `default` value for it.\n- `otp_message_template` (string): the message template sent to the receivers sending the OTP to complete the registration flow. Sending this field empty sets the `default` value for it.\n- `privacy_policy_link` (string): a URL to the organization privacy policy. Sending it empty clears it.\n- `webhook_url` (string): an https URL the SDP delivers outbox events to. Owner only; sending it empty clears it.\n- `receiver_invitation_resend_interval_days` (number): how often an unregistered receiver is re-invited. Sending 0 clears it.\n- `payment_cancellation_period_days` (number): how long a READY payment waits before it is canceled automatically. Sending 0 clears it.\n- `mfa_disabled` (boolean): whether multi-factor authentication is turned off for dashboard sign-in.\n- `captcha_disabled` (boolean): whether reCAPTCHA is turned off.\n- `receiver_invitations_disabled` (boolean): whether receiver invitation messages are suppressed.\n\nFor example:\n\n`{\"organization_name\": \"NewOrgName\", \"timezone_utc_offset\": \"+02:00\", \"is_approval_required\": true, \"receiver_registration_message_template\": \"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register.\", \"otp_message_template\": \"{{.OTP}} is your {{.OrganizationName}} phone verification code.\"}`\n","format":"json"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-organization-profile.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-organization-profile.StatusCodes.json
deleted file mode 100644
index 9ec036c0f..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-organization-profile.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"required":["message"],"type":"object","properties":{"message":{"type":"string"}},"title":"MessageResponse"},"example":{"message":"organization profile updated successfully"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-organization-profile.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-organization-profile.api.mdx
deleted file mode 100644
index c8d782436..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-organization-profile.api.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-id: update-organization-profile
-title: "Update Organization Profile"
-description: "Updates the organization profile details. Only account owners have permission to do this. Note: both fields are optional but at least one should be sent in the request. It is not necessary to set the header Content-Type for this request. It is set automatically by the HTTP client."
-sidebar_label: "Update Organization Profile"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWG1v2zgS/isDfkpwtuzm2j3A+ymbZtG3Tby1g8MiCRxaGlmsJVJLjuyqhv/7YUjJkRM3aW+7wH24fmhsc/jMM5zhvHAjSC6cGF2LS7uQWn2RpIwWtz2RoIutKv3XkbgqE0nogDIE05GE0ppU5QgJklS5i+BS5zXIODaVJjBrjdZBJlcIJdpCOcebyEBigDLlIrgwhCOYG8ogVZgnDqRFMF6xzGFeEUiCHKUjMBrBZabKE5gjONQESntOFv+s0FEEbwmUA20INMbonLQ1q3NIXi5DmaCFM6MJNfWndYmQGuu5PAThPbIiU0hSsczzGua1B3kznY4hzhVqikRPmBKtP4y3ye6kuqc5DkckeqJR8ItJajHaiDiw4I9FlZMqpaVBamzRTyRJ/tnFGRb+E9UlipEw808Yk+iJ0rJaUuh4NTcL05FyZJVeiIdOnGYILAkmfeTIHng3MgAUlSM+4FIvwFj4VOKC7WRmksRIzJWWthbbnmh5Pq33FN5NLi8grAJlkoBNl0qHgGpih/1U+dOL4HyFtoYl1uyINhh+BsPBxVuWWDuoTcVBkPiIiTOpF5hEN/pG9+Gua9tMywLv4CgQOB55BI1r4N8PH0ZVMpufXjKslTGhdZHHJVXgF6NxVlE8M2nqkA4ht2IQRA4pCXjKzWRZWrOS+YzDQ1lM7uBobkyOUh+PYJ0hZWj99lYS1sYu09ys+XRQy3mOCXtKG9qh5kovZy4zllCjnTVSB6EtLpSjEMPA+1y4W2TAYoxqxXeYz7iFS3ZaCizMjKyMlV48qaOUdYGaHMTS2hokNJuAEQJcq2vW5TMr+BIvcEZYlLmkR35s1qFd31EPaaGlr/RKUQg/LIJl90oiuPL+Pnn1quPwHkidgCKIpeaE0sQsvJn+9qEH7yZ84meTSQQT1EmAVi4kMcCipJozSIjwuwRTWeV0ByuZVyHlqMZXhsofZaTbEUG4nI5ZIDZFmSNhI9lxNMfPX+VeWrWScT0rTa7i2sdcl7qEq48fWpoPyobfCGHjPQ1Fjfo4R8luaxStcZ4Zs5xVNt9ToCEjKl3QkyFMXo8hwTwch6lobj4DrnzgkYngkuuRzyI/7w7rayp34ehDJwSjRd41U5rQ8o1NZO3u4EhXxRzt8QgyswaTEmpmVulw3mgx2TkJfJ3pe0xM7g0fPlTfXJhZLHWMeR70l2iVSQ6qzY1egISP56ev/2hvG6ylIgdzTI1FNlTx/WM8TPZL2xNEilTOEuW+frV97eqnMiZjGTVDzajez8oBVVZzekpTHzqJdNncSJuAUwvdV00ejGVJcfaMJotnp+Pp2ZvTfdyv+ss9B9f6ZLejvWlNvqvK0qJzTVn51VjAz5Iv1Ii/321uxKM6cyNGcCMucH1pFxf+ew9uxIGyEQT/MTwZDYdB6FAtYCmyFfL6tyXIgPuHqULbJfeCgT3MXuDSmVpTwGYTdXsVZrzdRnCWq3jJix87qj4ovdxu75Mn2igQP5TCAg2Gn463W3ZYbSp7WB+UGdfKFVqVtpETmwSjG7G9u9Hd3uOTM1ps/T/up1xptAs90MlwyH/2W4/L96LX7bNkWeaNhoGH2muy2kPnfrixh1vhp3uvVvBRG8QMSVHOP/0WhD42hLl3aiJpD0Ic7K1DU5SAq2JuadMqz2sRTuDl8MVjo68030Jj1RdMvsf8p+1Ea409YCVbQla65xEcSaq6ciGBMcQTh7jdP6uGhrgwvju/N/OeRavn5fBFB/nhjr8TOLjmn49d86uxc5UkqP9+vxy27p7ANwh4OxzGlVVUi9H1RvyC0qI9rSgTo+vb7S0fA2WGB59SUpwxO8mLYtANZcEwlouyR6lsLkZC8PYWfcLWBoO6OnZWyVK9x/rxaNEce7gwzXTXNGqc66T2LcG7f0/h6Hxy8uqnY+7awq8zOB2/5UmChxtO3Q/xRE8oVhJgOUwn5+MXwx/EDCbn4/6LYeAWbIYNmSXq7fF3MTp5+SMZnbz8EYx+r9DW30bLi0IprSyQvs6oQ8BTahX/ydt9MCudhiG4ybkT4r7Jwmvl5pV16IvgOJfExYR9L3qCQzLQ+Fc0jIYcp1VR8HQbxuWnMY4mr8fHXNokkDH8WKFy8vW1G/x+sC3kEmFe5cv7SYgMSFhYU5U8HlqMVan8glk1816rXSPxxBcdnOj/tyhyXzTlWYJVajAl6r4zlY2RyxknsPAAoFxDxT8Hle2A/AAujGC8wO0A9678LpGaSid+Y8Zf8tysOVoslsYpMlahG4VngGsX8AbN337SOaR+2RxSfy7jJerk9sgPE6PBYKEoq+ZRbIrBdyEcj2AaXpIaKvX+S0cjFgZLnVrpyFYxVbYxMDxFPePT6DssS60vMn/FtBbiOdvWOIdW9r+2JsO86PMITu5Jyh25AVnEQSGVHjQ/PGnPc2a8wbzwjwDhliRY5qZuh+qn71rlWO59NUerkZBfjERPENrCXaYTtCsVc15qzWpoRsYuBl6ob9K+a8R6Ilcxcqs42uwSbynjDOHE56lQQxlrNBis1+tI+lWP1mx1gw9vz84vJuf9k2gYZVTkPk+WxlEhdQc4vFlCtzGH+1fLvZTTebX8/6PwE4/CTc0j/EyDMpdKc2n0Pts0HdL1XrPPc0ZmHPHvm81cOryy+XbLP4cKN7q+7YmVtIrnWd989dqiyy3VErlkdU3g6sYPNmJ08HV522s3ncYxltQRf9SN7vV549Pp2RvRE/PmFbswCW9iZA/cu/8YWMpHbcDStwHNB2bfLum6Q+NhnxHY8v/M/eCWzSY0GdvtTj4sfXVHc4StNPvpdrvd/gcMFvUi
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update Organization Profile"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/organization"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates the organization profile details. Only account owners have permission to do this. Note: both fields are optional but at least one should be sent in the request. It is not necessary to set the header Content-Type for this request. It is set automatically by the HTTP client.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./update-organization-profile.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./update-organization-profile.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-organization-profile.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-organization-profile.mdx
new file mode 100644
index 000000000..d199983c5
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/update-organization-profile.mdx
@@ -0,0 +1,5 @@
+---
+title: Update Organization Profile
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml PATCH /organization"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-payment-status.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-payment-status.ParamsDetails.json
deleted file mode 100644
index af9f67731..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-payment-status.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"ID of the `Payment`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-payment-status.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-payment-status.RequestSchema.json
deleted file mode 100644
index 6f58c662b..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-payment-status.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"application/json":{"schema":{"type":"object","required":["status"],"properties":{"status":{"type":"string","enum":["CANCELED"]}}},"example":{"status":"CANCELED"}}},"required":true}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-payment-status.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-payment-status.StatusCodes.json
deleted file mode 100644
index 8912811e5..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-payment-status.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Payment updated successfully","content":{"application/json":{"schema":{"required":["message"],"type":"object","properties":{"message":{"type":"string"}},"title":"MessageResponse"},"example":{"message":"Payment canceled"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-payment-status.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-payment-status.api.mdx
deleted file mode 100644
index 8f9cbbdac..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-payment-status.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: update-payment-status
-title: "Update Payment Status"
-description: "Cancels a payment by setting its status to `CANCELED`."
-sidebar_label: "Update Payment Status"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdV21v2zYQ/isEPyWAbDlZtgH65iYumrXr3DjFPrjGSklni7VEquQprmbovw9HSo4dO07TtcCwfIht6l6e53i6lzVHsbA8mvKxqAtQaPks4CnYxMgSpVY84pdCJZBbJljpZVhcMwuIUi2YRMssCqwsQ80+Xg7fXo7ejK4+9nnAdQlGkJHrlEf8fZkKhNbNxKnwgJfCiAIQDIFYcyUK4BGXKQ+4JOelwIw/RHR9xfScYQbsY2vP+TPwuZIGUh6hqSDgFuucrFlZlDnwgMOXMtcp8GgucksCSQaF4NGaY106STRSLXjTzLw1sPhCpzVJJFohKKSvoixzmThm4SdLiNb7pnT8CRLcQTXlPlIU4tJQdFCCddr+fA9IwEFVBWl2geWzpmmIiXCctnTvRZzEbjDcgS21st7h+WBAH7thbWPJKndTKbNVkoC18yrPax58fQS2GRdgrVgAUX4YmN0QdIIHLiPgKNHd5O9e6KalwncjsTGxYZK41IWUQtIE/OIQ6xciZTf+rp9D8jgbMEabQ/e56/sKUEh6tWJdoUtor+h4oRH2SU+N/yNuZ/vc3itRYaaN/BvSH07u60Hv57uqihgc7yN58DDzWxz8rUa2w/MeRufoYnC2ZfqhxiaEP+2H8KU2sUxTUD8+fo/Qu0fQwbzYh0mMXupK/c+ved5SPHTDF9s3fANWVyYBpjZa3ZtiIamMxNo1nBcgDJhhhRmPpjOq+wVgplPfepLMtSh6yMO2+9lwLdMmtF0Hs2DuuvZVmZxHnJOZzsuEou3Dse1rQ1uU8jXUe5Vh2GanuzqWgUjBMLpYIRX1XaHY5GrMfvvzlp2MJuc//3LKtGlP/2LD8TVbQk1Nse2oO/a65urN0nVMRuOzwXdCxiajce9s4LF5zmyNegmqOX0WovOL74no/OJ7IHpXgam/DpYTZZsB5zFEWwAcpM7xZ1J33Y9e3Jv7aWR0tPeT9lw7dG3TnCDkuTDsStq4MhZcZxznAufaFJQqPOCUwR71r/1Bf0BpXRWFMDWP+G0G7LiNk8nV+JRJGhFR65zFlczprTNMm4VQbUTdhFiIJbC4ypfdMOlOBVsYXZU01RlIZCndA30HxjXFzrsCXGmz7O+F+r8H8YP6oG4zaZ1LxXQJqtdWpNJoqpYMM4H02EPRiqEuu7n2gbmACZW6B4lOgcYaFoMva04xox95rleUXAZKbSVqI8FGhKPHptbbC9vPXroVpF7ZBqkXi2QJKp2dZIiljcJwITGr4n6ii/BZFk4j5shvoNRd9lsHthVzrKSaG2HRVAlWpiVI94JP3Wn/GczmxvXEf0OtM/EUtxXErJP9ZjYZ5EUvyYRBexTyllyIBiAshFRhe3CUz1M0XkFeMGfI4U+hzHVN6fUkE1ZZkntdxWAUINj+BypqCKawf8wnYO5kQnWpo9XC7GuzCJ1QT897thULeC4ToFk/2myHw1IkGbBzV6d8yyVbURiuVqu+cE+dtVbVhm+uL0dvJ6PeeX/Qz7DIXVkttcVCqC3DfkVl3fawWVJ3is3WKvjtq3HbORC+YFjmQioq3I7Kup03pryrPjzgkVuI77fHTFskkfU6Fhbem7xp6Ni3jGg6C/idMFLEVP+na55KS9/TzeL7KKGTm3Z3O2WPLNkHkXeNUFEXvBN5Rb94wJdQ+22+mTVB10oJkX9w6f32bkn9XnFvaG2CTmOYJFDiUdntEW48vL18xQMet0t84bZ/bsSKFnOx8ii1C4Qb0dzZmudCLSo/SHqjlC9ir+svXddvvxCtg3F4OFZ4JvSfeB1UWa/9TNE0G3n/6FGNNrabkFMgmqb5B+xQPXw=
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update Payment Status"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/payments/{id}/status"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Cancels a payment by setting its status to `CANCELED`.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./update-payment-status.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./update-payment-status.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./update-payment-status.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-payment-status.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-payment-status.mdx
new file mode 100644
index 000000000..124383b16
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/update-payment-status.mdx
@@ -0,0 +1,5 @@
+---
+title: Update Payment Status
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml PATCH /payments/{id}/status"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet-status.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet-status.ParamsDetails.json
deleted file mode 100644
index 960e01f0d..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet-status.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"receiver_wallet_id","in":"path","description":"ID of the receiver wallet.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet-status.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet-status.RequestSchema.json
deleted file mode 100644
index cb428bb2d..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet-status.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"application/json":{"schema":{"type":"object","required":["status"],"properties":{"status":{"type":"string","enum":["READY"]}}},"example":{"status":"READY"}}},"required":true}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet-status.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet-status.StatusCodes.json
deleted file mode 100644
index b6b811684..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet-status.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Receiver wallet status updated successfully","content":{"application/json":{"schema":{"required":["message"],"type":"object","properties":{"message":{"type":"string"}},"title":"MessageResponse"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet-status.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet-status.api.mdx
deleted file mode 100644
index 53678ba90..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet-status.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: update-receiver-wallet-status
-title: "Update Receiver Wallet Status"
-description: "Updates a receiver wallet's status. Only `READY` is supported."
-sidebar_label: "Update Receiver Wallet Status"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWG1v2zYQ/isEvywBZMvJsg3Qt7RJ0azbmtkpisE1Wko6W6wpkuVLXM/Qfx+OlBw7dpxmbYFh+RDL5N3xee6oe/GKOjazNBvTIRTAb8FYOkloCbYwXDuuJM3oG10yB5YwYlohsmBCgPvBEuuY87ZPXkuxJB+Gl+cXf30g3BLrtVbGQdmnCVUaDENjV+XaXHfe22BpFMzQhGpmWA0OcWTjFZWsBprR7tz38dz3vKQJ5YhNM1fR+4CvLoiaElfBfcAIxsAnzw2UNHPGQ0KtWwo8w/JaC6AJhc9aqBJoNmXCokBRQc1otqJuqYOkM1zOaNNMojWw7pkqlyhRKOlAOnxkWgteBNrpR4u4VrumVP4RCreFakyjTzEO2qDrHAcbtOP6DpCEgvR1CCL6n06apkEaLBDaUGz3w/a2G8KC1UraeNTpYIAf224dbjuzjT3xIZ4lsb4owNqpF2JJky93xSb1GqxlM0Du9z207YtOcE9UEuq4CyH9PQoNW2ZIvEno2T5uz1hJhjGWT8F+GCQYo8y+eG2ffQGOcWEJy5V34dpGxRBEZ5h99KQm/iG3k11ubyTzrlKG/w3ldyf35aB377P0dQ6B94Hw3r/cLQ76h3Jki+cdjO6gs8HJhun7GmsX/rjrwhfK5LwsQX5//z1A7w5BB/NsFyYyeqG8/J+HedpS3Bfhs80ID8Eqbwogcq3VvSkWCm+4W4Yy8wyYAXPuXUWz8QTzeg2uUmUsMEUVChNu0rSrKDaNWdCmq93q1KS2K2gWzG1XzbwRNKMU7XfHjzAM0U+bINb+YJq/guVOyjhvr22IKamAlWAIRpxxyeWMMElGF9fk17c35OhydPrTz8dEmXb1PTm/viJzWGI1bAvslr2utkazGKfR5fXJ4BshI6PL697JIGKLnMnKqTnI5vhJiE7PviWi07NvgehPD2b5ZbCCKFn3Ow8h2gAQIHUHf0L1UO3wjR7etSGXD9d9VJ2qAK2tkCMHQjBDLrjNvbFQg3TkWjA3VabGe0ITitc3Qv6lP+gP8E77umZmSTN6UwE5bONodHF9jB0hI04pQXLPBb6LhigzY7J1pyVOkZrNgeRezIlmS7QSVhmZGeU1dnQGCq552FDYh7iN0yW4hTLz/o6f/3sQ38l38qbiNhwpidIge22e0kZhDiWuYg63IxQliVO662nvmUsIk2XYKFQJpGCS5BCTXVCs8IsQaoE3y4BWljtlONgMcfTI2EZ7afvZKzec1NOtk3o5K+Ygy8lR5Zy2WZrOuKt83i9UnT7JwnFGAvk1lGV39W0A24oFVlxODbPO+MJ50xLEuLjHYtp/ArOpCZXya6h1Jh7jtoCcdLL/mk0Fou4VFTPOHoS8IZc6A5DWjMu0XTjI5zEaL0HUJBgK+EvQQi3xej3KhHiLcq98DkaCA9t/hxnNgant6+kIzC0vMC91tFqYfWVmaRDqqWnPtmIJFbwAbOyz9aR4rllRATkNeSrWW7SVpeliseizsBustao2/e3q+eUfo8veaX/Qr1wtQk7VyrqayQ3DcWol6xkozq1kPbhuJZ2NQfDrp+e2jDj47FItGJeYyAO1VduVjNcDMiJp+xKa0Gzv3Hw3XlbKOtRerXJm4Y0RTYPLsbRk40lCb5nhLMdSMV7Rklt8LteT8YOcj4btTHdMDs7ie6l1ZVNizbxlwuM3mtA5LPf/FNBMmqQrxIgzCj6PaHo3aO7O0E4v3CSdxnlRgHYHZTc7w+vzm+cvaULzdvavw48G1LAFzvNsEVGr4J7Q4IW1FRVMznzsT6NRvHBsp2eYh56hfUBae/1yvymJTPA/8tqrslrFjqRp1vJx60GN1redNIYJf2P4B0dLZeI=
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update Receiver Wallet Status"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/receivers/wallets/{receiver_wallet_id}/status"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates a receiver wallet's status. Only `READY` is supported.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./update-receiver-wallet-status.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./update-receiver-wallet-status.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./update-receiver-wallet-status.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet-status.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet-status.mdx
new file mode 100644
index 000000000..896441d0a
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet-status.mdx
@@ -0,0 +1,5 @@
+---
+title: Update Receiver Wallet Status
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml PATCH /receivers/wallets/{receiver_wallet_id}/status"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet.ParamsDetails.json
deleted file mode 100644
index 98fd7186d..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"receiver_id","in":"path","description":"ID of the `Receiver`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}},{"name":"receiver_wallet_id","in":"path","description":"ID of the receiver wallet.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet.RequestSchema.json
deleted file mode 100644
index a8e14991a..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"application/json":{"schema":{"type":"object","required":["stellar_address"],"properties":{"stellar_address":{"type":"string","description":"Stellar account or contract address for the receiver wallet."},"stellar_memo":{"type":"string","description":"Optional memo for the Stellar address."}}},"example":{"stellar_address":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL","stellar_memo":"12345"}}},"required":true}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet.StatusCodes.json
deleted file mode 100644
index 95e92b3a1..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Receiver wallet updated successfully","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"enabled":{"type":"boolean","example":true},"user_managed":{"type":"boolean","example":false}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invited_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"last_message_sent_at":{"type":"string","description":"timestamp when the receiver last received an invitation about this wallet","example":"2023-02-10T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"payments_received":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"canceled_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}}},"title":"ReceiverWallet"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet.api.mdx
deleted file mode 100644
index 4cb6d942b..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: update-receiver-wallet
-title: "Update Receiver Wallet"
-description: "Updates a receiver wallet's Stellar address and memo for user-managed wallets."
-sidebar_label: "Update Receiver Wallet"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWW1TIrsS/iupfLm7VQwMb6J8Q8Fdd9V1AfWcdS1OmGkgx5lkTpLRw6X477c6mUHeFF09t25dPwjM9MvT3Ul3pzOjho01bd7QLgTA70FpelugIehA8cRwKWiTXiYhM6AJIyojIg8sisD8S5OegShiirAwVKA1YSIkMcSSjKQiqQblxUywMYQZiy7SApUJKIbCT8KF+Fz/tSWjBZowxWIwiKh5M6OCxUCbNEcw4CEtUI7wEmYmdB3zSZvIETETIH/kkv9A1Qr+SrmCkDaNSqFAtZlGKFfzOImAFij8nUQyBNocsUgjQTCBmNHmjJppYimN4mJM5/PCJihn48uxrfnznQHeOmmgzaEMp0gRSGFAGPzKkiTigY1C6U+NuGabouTwTwjMCqobql3IB1nIcb0kCkNqOGgrZo1gA9q6QxaLKAhkKgyRiiBSxQKzWFi4nra6bF5YKMSFt1vbN/uFRY/rFOWuLeQinc/n6Gxm3b7NKvrp6LfWl+pvX6pXX6tfjj9Xv5+1j7/1vp5Vzs/Ofhz2vlWvTvp7ncuL79e99nXlS6N2Vql2u71Tuo6YlivVWt1pXI2/faATKbRzbcX38WPVoO6qS0hqN1RIdBoEoPUojaIpLfx68Fejy8NtLl44iu77Vb9aDmteOfRrXm2/ceAN98IDLwzqe7Xy6OBgfx+otcuhfrtGv3IAFQh9bwTDPa8W1Hxvf1hreP5+dY/t1xu1MqvgfqWGG8uQO+yUGwvF+e3tQOosZAcQ1r1avc68WmO/4jEfwCvv+Y29BvghDMuoz6WN5yRd8aFiwpCW1lwb5JnIGBI23sE3MSbRzVLp3vGzJCkGMrZ7BJJB2R8EEQdhBqGMGRfPy2IJ90K4L27KCgGSQcTF3eCp5LMbU0mHCYpHeSDYMIJl5w6ljICJZTnZdsCaMshqyvMMNj8uh92VljzoL8hSjzb88lbfmZ3WCAbu7RaqQAHu6gEzz0Ot+JWq51c8v9ov+81avVkvF33f/4EysszwJhlc3PNXyTjYlBExbQYxaM3GMNC4ILdLW81zhsegDYsT8jABsVoNUGL+KyRMEAvTZjjChjI1xEy4zjLkVpxlfxOnkYZFg4RNYxBmxxKpIENOOsihvIBnxHgE4Qu1+HYpMBHAK3kU4I7nYvw6JmfFgMVYmJdZmFIMqwo3EOvdqZNpDWYQ2MblObWXvfYRanb0XOt0pUJs25qHh+1a4+R47/T6a+OicdbuXPWOrruN9sXl9VX1/Pdqu/+9c3V8Wjtv9Wut75+rP05Pj09b9S32Pa+o7PtF318pJC3HNrebmJl0u09FGmPf1O62jvu0QLudVvt3+/nppNfvdDttWqDHp61PnzptbKbWq5R2eavnFCxUDSZcG6mmvx6T/yLkxdbdpm0kVYz7n2Jy8pB01wb9sbWcr2j97LzTEUZNXWe1Tp6dNOb2ZW1bY3XIQtJ1HfT79U+glNy6pFd1t8EwHulF8gLiGG1TahTbHd+5+0Pbypu2XQqWmolU/N8Q/uPGvRz05qIUaTwEa3dWMLYdddab9QwHPZeGrNj5CCNXVPPLS6LXORYurG668FiqIQ9DEP+8/54w7xFBDrO2CRMtOpap+D8P8ygzcVuEa8sR7oKWqQqAiAVXvlM0BKniZmonDofAFKhWaia0eXOLp+kYzESG7lgfTOyMAl/SUt6G6NJsaUAxL2Uzj6WniwnBHE+BoO7z+UaqItqkFNXkKHoYDeeuZSyP6T7hX2G6kTla2ep1zc8EWAjuPO3qPzZHvfYF+XLdJx86vUp97yMeuN3TAWldnJA7mOIoIpturMjLBxtOLIar17ko+++EjPQ6F17Zd9iczWRm5B2I+cdXIarU3hNRpfYeiL6noKYvg2VJyWIC9hSiJQAWUq74L2S3JRI3dvdxBtR5bpyxKERrw4nHzc3FyJ1gskqaz0zaXA9TpQHbSnIRMYMVHVcSLVBc4M6oRtEv+ig+jWOGfQvtL81dtsv40GtffCQcZ49GyogMUx4ZO7ORasxE5nBNjCQxuwMyTKM7kje4+JSRsZJpggM3BQFPuH0h8ciwPPURYB6kuituROJ/D+JP8VP08SyDKgWRCQgvS2iJkphsiZkwg68dFCmIkUk+clwTV7ATW3yBvTkJmCBDcFnRMk7wRxTJB1x7ChKpuZGKg24iDo/cZIullH164ZKTvCRzkjdkwR2I8PZDPgwYczNJh24Q8BoJH5vEGr+AMs03h7ZgMzJrFRcjxbRRaWBSlRm4Pu7bGtPiKywbKVtS32JaLmKXbQ8wJDntL1szgSj2gglTRj8LeYmuZBRACY+PpezBs/bsMuMzRDGxgiz+EJJITnF57bSEpBrpvqZDUAIM6OJPzHkGVKy/jXqg7nmwPHHKYBalGpcskSdHns7ICjTiAQhts2GexhMWTIBUbJ5yFRllNUulh4eHIrNvrbSMVZdOT446572OVyn6xYmJI5t1E6lNzMSSYHfHQRaT2sUtx0q2WRrQv/+lS1ZxDPxtSkmE0795ZuMs62NuFjNZTQu0uXrVkklaefF43XGLA0ptUMZsNmQaLlU0n+NjV4uaN7cFes8Ux0Gf7XdCrrOhX3aP8aQnPnSzkfhH8tStzlbb8hIrsL7esyjFX7RA72C6dpGEVzlvxLPlJuctoB49O7/F4a/rJNBvjvDIofH6KO5R0EZPj5Y5jlYQQGKepV3ucC9a/aPPtECH2c1RbCc3VLEHvA1iDw61tO6xHap9NqMRE+PU9dlOKO4HttH03NmmJ/uCZm31y3pX5SzB/2jXVpbZzLVU8/mC3r16kiPzbU6NYbqdz+f/AdPW/4k=
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update Receiver Wallet"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/receivers/{receiver_id}/wallets/{receiver_wallet_id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates a receiver wallet's Stellar address and memo for user-managed wallets.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./update-receiver-wallet.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./update-receiver-wallet.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./update-receiver-wallet.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet.mdx
new file mode 100644
index 000000000..6cffc4f5e
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet.mdx
@@ -0,0 +1,5 @@
+---
+title: Update Receiver Wallet
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml PATCH /receivers/{receiver_id}/wallets/{receiver_wallet_id}"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver.ParamsDetails.json
deleted file mode 100644
index de64631b5..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"ID of the `Receiver`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver.RequestSchema.json
deleted file mode 100644
index f7573e146..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"description":"List of fields to patch for the receiver","content":{"*/*":{"schema":{"type":"object","properties":{"date_of_birth":{"type":"string","description":"Date of birth of the receiver"},"pin":{"type":"string","description":"Personal identification number of the receiver"},"national_id":{"type":"string","description":"National ID of the receiver"},"email":{"type":"string","description":"Email of the receiver"},"phone_number":{"type":"string","description":"Phone number of the receiver"},"external_id":{"type":"string","description":"External ID of the receiver"}},"example":{"date_of_birth":"1980-01-01","pin":"1234","national_id":"123456789","email":"john@example.com","external_id":"external123"},"title":"PatchReceiverRequest"}}},"required":true}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver.StatusCodes.json
deleted file mode 100644
index cc2d2ece5..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Updated Receiver Details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"f83bb638-dda4-41e6-80c9-d03e6eec2aef"},"phone_number":{"type":"string","example":"+15552368475"},"external_id":{"type":"string","example":"usr12334"},"email":{"type":"string","example":"jdoe@mail.org"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"successful_payments":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"canceled_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"registered_wallets":{"type":"string","example":"1"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"wallets":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"enabled":{"type":"boolean","example":true},"user_managed":{"type":"boolean","example":false}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invited_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"last_message_sent_at":{"type":"string","description":"timestamp when the receiver last received an invitation about this wallet","example":"2023-02-10T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"payments_received":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"canceled_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}}},"title":"ReceiverWallet"}}},"title":"Receiver"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}},"409":{"description":"Conflicting phone number or email","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object"}}},"example":{"error":"The provided email is already associated with another user.","extras":{"email":"email must be unique"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver.api.mdx
deleted file mode 100644
index 87f6f9b17..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: update-receiver
-title: "Update a Receiver"
-description: "This endpoint allows an organization to add and update information on the receiver, including email address, external ID, date of birth, personal PIN, and national ID number. The response includes all information on the receiver."
-sidebar_label: "Update a Receiver"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWmt32jgT/is6+tTui8GAuYRPSwNp06ZZGtJmt90eVtgDVmNLXklOyubw3/eMZBMIJCTb7nvPh5DYc3lmNNJcxA01bK5p7xM9gxD4FShNP1doBDpUPDNcCtqj5zHXBESUSS4MYUkirzVhgkg1Z4L/wZCMGElYFBEmIpJnETNAuJhJlbq3SBADUYWSCuEiTPKIizmBlPEEeRVoXSHw1YASLCHHgwqxcuSMTLkycYVkoLTEd6Pj04pVJax4S01Enk5BVcm5VaQzKTQUekAj7IcQVWmFygyUfXkc0R59b60o3UIrNGOKpWDQRb1PN1SwFGiP8ohWKEc3ZczE9K7vjgeIHzX9Vor6DXUp+D3nCiLaMyqHCtVmkaA4zdMsAVqh8DVLZAS0N2OJRoIwhpTR3g01i8xSGsXFnC6Xn5000OaFjBZIsQnhhGuDIGYckkjjQmXMhDGZSbXhAlqhoRQGhEEZP9R+wI8ttXL6BUKD7lDoL8NBW5XMwETOJnaltlHedctgfWFLD62ALCs0Q5fukzIq44FHIAyf8dCtrYuEXWLLeJnwaL/407Xg2iHLBu5+KUMb37tMjKWAicP6CFuR+gHLyn3zKMuGt5tsW5YVxmwYbi8srR90fc+ve36dFqtE641mQO/41j5stTvdA7ryFP0iY/FjIbsaypTegb36r95ook2GG7spRhiv5fY5c7FOlwh0cxvZB27j26Bs+P72dnD7OiKlPDIAw3iiN8OfZVlShFPti5biKXth9wqsfEpn3eZ02m52vShigRfUoe11/fDAi/wmtAHCBoPZYwLkVuI/6q1Wq9Fsd4NO6xHBcMuYa1VvNJvBg/F8S/4lkvAjklWlmiNPqACdOWHmYcaG32h6fsPzm+d1vxe0eq161ff9j3aVpWHJJGOLFITRe+Qgg87DELSe5U/imjGeQPRIDt8ax0QIT+RR6EXBxfxpTHOuDSiIJtcsSWAfU90x2fiNJiyV+aYephRbYFoykOr98cq0BjMJbbZ5SO378eAQNTt6rnW+Ly5fvngxCDrHR+2TizedUeftYPhhfHhx1hmM3l98aJ7+0hycvxt+ODoJTvvnQf/dq+bHk5Ojk35rh317POL7Vd+3Z1d5aPQdGz7aduoTPbRvG3X9pt+sR4FXj/zAC7qdA2/ajg68KGy1g/rs4KDbhTWb1Ldr9BsH0IDI92YwbXtBGPhedxp0PL/bbLNuqxPUWWPDHeVxd8KNheJ88u1AWixiBxC1vKDVYl7Q6TY85gN49bbfaXfAj2Bad5k33RNeH/hUMWFIX2uO53uFxjKFjM338MXGZLpXq105fpZlNrfgQQHZpO5PwoSDMJNI4tZ8WBbLuBfBVXVbVgSQTRIuLif3VWL7MdV0lKF4e9oKNk1g3blTKRNgYl1OkdRyDWqSMsHm+xhssbi+7Bd2mctF1waShKlJUW3v2byHP/dfN39+3fzwpvn66FXz3dvB0U/jN28bp2/ffnwx/qn54fi8PXw/encxHlw0XneCt43m2dn4ZF1RCqncUbNuEkzc2x1U3yO9uG7k22RwccWfJONgW0bCtJmkoDWbw0RjQO6WtlmtGJ6CNizNyHUMmy0LQYnlf9h5EQvTlcBsKnNDDHZuxU7fhbPuf4d0XJJOSij/6cn4/3n1kXlVG2by3T4VeYpThcFZ/+icVujZsD/4xX6+PB6fD8+GA1qhRyf9ly+HAxw43M1S2p1bY6dgpWoSc22kWvz1NfknQl5t3V3a3CCC9mx/5SHpvg36cWc639D6ynlnKIxauP7oLrmj3v0Ony4rNNjVNL1g2DC5xuu79UmglHxE51v0Z6sjDYhjdH2OYvtXfel+0Lb6joZQsNzEUvE/IPrbjXs86O1QLTrBZYUWaWTXNOhO+17AoKfSkA0zb1GUegK/vib5LsffKdgtTXN7aY6kmvIoAvH3r8tu624BPILAmRFsm4EWH8lc/FeE1/1hMCtM3BUBwXoEnIGWuQqBiBXXKgoOtt13KMUs4aHBaXG2MQZTbnr8r3TrfQ7BKXSm5BWPICpm3Byn0ApYtCBMaxlyO4e65iYmTEgTgyJY6Vc3XFjOzpyINNeGTIHkgv+eAy3PNQ1hrrhZ2MH0C2AKVD/Hcd2nzzge/uphETIH4RWDYm8qo4VXTLDx72ISJzSXwo23L2FBew9yVugVS/KVBFSUgoll5GbhYWxn5nZoWCtrVl274dGSImJ1VU7Sc4UGWgGlIWNcL7ck6+bcZv2Mv4HFVqroF8eKq4FjYBEogqHhykCskceDEXl9cU6eDceNVvs5xpB7OiH90TG5hEWVlt3qprxyzu/EYkyMh6O6/52QkfFw5NV9h83ZTG6MvASxfP4kRI3geyJqBN8D0bsc1OJxsCwpWd213IdoDYCFVCr+HdntYY2XPVZdUeaMXcdJBlxPc6UB+wEySpjBUgzXHgMalHYwOlW/6mOc5mnKsOC0G/phGc/Gg9Fzu8uJkTIh05wnxl6zrN+U2RuYlF0CmebJJSk7E3uBRuZK5hmO5BWEPOP2hcRez6xpF2Cupbqsbvnu3w/ir+JXYa8PubsxzEB4xdmfKYkHKDExM/jaQbE3iVl5KXFHnLvzwxd4KpGQCTwLbQIp7/NmEq8nMVoUZFJzIxUH3UMcHvlUTB1qxacXrTnJywoneVMWXoKIPj8rpzhzbuJ86iY4T5HwvEes8SsoizKctQVbkFmruJgppo3KQ5OrwsDyhu7BNa0+wbKZsmnyW0wrReyz7RqmpKT9y9bEkKReGDNl9IOQ1+hqRgHUsO+vFQ8etGefGa8gSYkVZPFHkCVygeG11xKSa6R7k09BCTCgq7/iKWVApfqn2RjUFQ/XR4UFTLxZqVkiT848XZBVaMJDENqWGOXBm7EwBtKw55TLoSirV6tdX19XmX1rpRWsunZyfDg8HQ+9RtWvxiZN7DmZSW1SJtYEuxsywsja5ffGQXNzW279z3w5oMhaBr6aWpbgIHlZeP2mqHI+rcb7eJfY4xFOCWKpDb66uZkyDe9VslziY5emep8+YxGlOI6CbSkUcV2MhYtr/3v9/uysuPp8Tu77jsFOyGX2FYu1Ao5WinqPR3T5GSfvLn/fFoKHTrF3juy3jPgtgWWlJOqHIWRm7fVWKb5RJI7654evaMWVj70bmtpJGVXsGr8gwa5tUVihbKtuuLR1Q/EHYtxp1N3CxGHE34h4J8vNjatKlssVvXt1L0fhqJX/0MTlcvkn0nMUYQ==
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update a Receiver"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/receivers/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint allows an organization to add and update information on the receiver, including email address, external ID, date of birth, personal PIN, and national ID number. The response includes all information on the receiver.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./update-receiver.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./update-receiver.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./update-receiver.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver.mdx
new file mode 100644
index 000000000..dd7215bb3
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver.mdx
@@ -0,0 +1,5 @@
+---
+title: Update a Receiver
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml PATCH /receivers/{id}"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-user-activation-status.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-user-activation-status.RequestSchema.json
deleted file mode 100644
index ace4f32c5..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-user-activation-status.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"*/*":{"schema":{"type":"object","properties":{"user_id":{"type":"string"},"is_active":{"type":"boolean"}},"example":{"user_id":"5ca230c9-da95-4bd1-b2a2-aa5d0df65efd","is_active":false}}}},"required":false}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-user-activation-status.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-user-activation-status.StatusCodes.json
deleted file mode 100644
index 9eefde470..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-user-activation-status.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Created","content":{"application/json":{"schema":{"required":["email","first_name","id","is_active","last_name","roles"],"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"first_name":{"type":"string","example":"John"},"last_name":{"type":"string","example":"Doe"},"email":{"type":"string"},"roles":{"type":"array","items":{"type":"string"}},"is_active":{"type":"boolean"}},"example":[{"id":"7a4c6555-1f73-49b3-a211-f95bd2b8ec90","first_name":"John","last_name":"Doe","email":"email@email.com","roles":["developer"],"is_active":true},{"id":"5f4df1dd-c84f-482a-84ad-541ffd46e75a","first_name":"Jane","last_name":"Doe","email":"email@email.com","roles":["financial_controller"],"is_active":false}],"title":"User"},"example":{"message":"user activation was updated successfully"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-user-activation-status.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-user-activation-status.api.mdx
deleted file mode 100644
index 39bcc010d..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-user-activation-status.api.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-id: update-user-activation-status
-title: "Update User Activation Status"
-description: "Updates the SDP user’s activation status. This endpoint is primarily used to move a user into active status when they accept the invite to join an SDP organization account and create a password."
-sidebar_label: "Update User Activation Status"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWG1v2zYQ/isEPzWF5bfYefGnpUmGthu6DE6wD24QnMSTxUYiVZKy4wYG9jf29/ZLhiNlW25Sp+laYNiXSBGPd89zxzve+Z47mFo+mvAri8by6xYXaBMjSye14iN+VQpwaJnLkI3PLlhl0fz951+WQeLkDEiKWQeusm12mUnLUIlSS+WYtKw0sgAj8wVtE8xpVugZMvBamFROBzVYq2DzDBWZWjBIEiydNyvVTDqk3R+0VAyUB6LNFJT8FBBAkuhKOQZKsMQgODJSgrVzbUSbt7gu0XjRN2JNihifrFmMPQLe4gY/VmjdKy0WfHTPE60cKkevLzsv6WGTDAugN7cokY+4jj9g4niLl4bsOImWVonkjRQNQeuMVFO+bHFpbwLzxmqsdY6g+HLZ4ngHRZnjlho+TKC/302OIwHHw2gQi14U96EfAQxFV6QHQ0wF39KdQm5xuSSNREsaFKuP9MWWWtkAtt/t0mM7+KfelaSz4QUoy1wm3medD5bkmi7ZmJlwLEDmvMVTaay7UVAgoduG2OI5bBaNztEfwt2efcypDZ/x3uH+QYxiPzqMj/vR4PCgGx2laT8a9tK4e4TYPTxOKQoNYDv1vdWZIvkN1J3iZxpJOtB/LPqB5mYFjIEFucVhYR/Z8ZwDMwnu4YcwSA6Gw2HUSw/3o8FxvB9Bv9eL0uNhLPrxESbH3e3Y1Dy3aHouayrh+ZP/2050sY7YaMIFzjCnIFH4GmidqXDZqkEN04FIe0JEydEgjQZHfYiOBiCi4aCXpmJwgIdDeAAKFH4rqFQqUImE/IYOsNF5/gBfyAY6ctL56FFZ4NspWKC1MKVFX7gapW8OllW+mghmqyRBa9Mqzxc8JN2g23uYVVcKKpdpIz89L7V25wQao82jpw3vnAH7tIZQgxtyqiri4Iu1Ax4ezc+qVQ2Dv9OObdHcoFjZGXR7Dc2f7/iRikNo9h+G5mdtYikEqh8fl8fZbQB8hYDnYTGpjHQLn/mvEAyak8plfDS5plN9FyVa4BRVVN9rUazFIqoTid6DC1FZqZX1Wm5xwUc7d7b4DPJqrYEMFegyTTlegksycgMQCt6hlLGdTc5wwmxm1G2QscpQDnsVKypjcm3wXpPQplyW8hck3NvBO6ljHDIzQxBoGEURpJJqumoc3v5xyV6cj/vDgz2mTf31hp1cvGG3uKBmoXbOlj6qzmQkqKWcGJ9f9LrfCRkbn19EvW7AFjize6dvUS33noWoP/ieiPqD74Ho9wrN4utgeVFWgoEC3ZcRNQB4SCvDH2l7uC5Vqr25uqiPHeY5GHYmbVwZiwUqxy5ycKk2BcWejjQaG2ActrttuhxtVRRgKBkuqf3dqePF+Oxij5peYE7rnMWVzB1LtdnqVK1vguEWWVzlt6yEBWnxX4FNja5KplNmMJGl9At6hiY037V1hW6uzW37ge/+exDfq/fKzwRkUjFdooqsrkyCrDSaqiVzGfhJIUDRijnt1T+iruW7e1qgusQSUCxGlupKCb8xo3/yXM/ptBgstZVOG4l2RDgiNrFBX6d+RqLhpKisnRTFkNyiEtcvMudKO+p0ptJlVUydRedZGvZGYSBaQ1msjnOYpmoxz0qq1IB1pkpcZWqCFBf3VEzbz2CWGn+j/RtqKxVPcZtjzFay38wmw7yIkgyMszshN+Q6ziB2CpCqU3/YyecpGq8xL5hX5PELLHO9oOP1JBNWWZL7pYrRKHRo2++pSjk0hf0tHaOZyYTq0opWDbOtzbTjhSKdRrYWa/FcJqisbwRWhbeEJEPW93Uq3KGka9TpzOfzNvhVr63eaju/vjk9fzc+j/rtbjtzRe7rZKmtK0A1FIfZmFEXzDbTMVuPx1tFpzEe/19+KagvKId3rlPmIP3g5x18X7c0Ez8FkC8aTc11i2faOlq9v4/B4pXJl0v6HC6l0eSamiYjIfZT2vWytbonNy3XaXBmdEkYNj0W/e5AI1QQOvF8G8sPutOtduzi5PL0NW+FRo1mGS1ok4E5DUow981Xi8OD+/nW38/1C2FcLalFw/jnDUDASH8J8aNb7u/D7b9cruXD0hd31I5aSVNMrpfL5T/CiIRX
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update User Activation Status"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/users/activation"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates the SDP user’s activation status. This endpoint is primarily used to move a user into active status when they accept the invite to join an SDP organization account and create a password.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./update-user-activation-status.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./update-user-activation-status.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-user-activation-status.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-user-activation-status.mdx
new file mode 100644
index 000000000..1c82c0ef8
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/update-user-activation-status.mdx
@@ -0,0 +1,5 @@
+---
+title: Update User Activation Status
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml PATCH /users/activation"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-user-profile.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-user-profile.RequestSchema.json
deleted file mode 100644
index ae4b71cd4..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-user-profile.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"*/*":{"schema":{"type":"object","properties":{"first_name":{"type":"string"},"last_name":{"type":"string"},"email":{"type":"string"}},"example":{"first_name":"FirstName","last_name":"LastName","email":"email@email.com"}}}},"required":false}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-user-profile.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-user-profile.StatusCodes.json
deleted file mode 100644
index f77145009..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-user-profile.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"required":["message"],"type":"object","properties":{"message":{"type":"string"}},"title":"MessageResponse"},"example":{"message":"user profile updated successfully"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-user-profile.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-user-profile.api.mdx
deleted file mode 100644
index 5fcd116d7..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-user-profile.api.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-id: update-user-profile
-title: "Update User Profile"
-description: "Updates the profile details of the logged in user. Note: all fields are optional but at least one should be sent in the request."
-sidebar_label: "Update User Profile"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNV1Fv2zYQ/isHPjWFbDlZtgF6WtqmaNcu9eYEe3CNgpLOFmuKVMlTXM/Qfx+Okhw7SZ1ma4G+WBLv+PH7jvTdcSNILrxIpmLs7FxpFLNI5OgzpypS1ohEXFW5JPRABULVOkGOJJX2YOdhWNvFAnNQBmqPbggXljABqTXMFercg3QINgBKDWlNIAk0Sk9gDYIvbK1zSBE8GmIYBnX4qUZPQxEJW6GTPPt1viV05dH1nCPROT+z+VokG5FZQ2iIX5/GT/nhswJLyW+0rlAkwqYfMSMRicoxPCn0bJ0r5+mDkSXu+HpyyixEEwktD1mxlErfY2HTZ1lWGm8vIV7yxwW/74GLt3I73KG2z9/C7zCzpWgaBmblymEukrnUHsOIr6zxrZ6T0Ygf+1v67o2IdmMkq0qrLEQ4/ujZZTdgNytMRYney0U4JYfj2DveGwxSxKEQf7ROf3WExX6cthCCT9X27NVh+3PwdZah9/Na63UXi9PR8V2xV0bWVFin/sH8MbIP60PnrLv/EHwmJ/3DCJ4k1bt+pi5TdAxxIHi3zlJHQ1xYgj2ZNyz6dU5HxzvIt2d8T+B2a366uzUvrUtVnqP5/vtyv7obAl/hEHR4zGqnaC2S6UY8Q+nQndVUiGQ6a2YcBiosJ6lKUlYwO8lGEVfbVOXRXaPzAaB2/McWPLMHnrDQVssu/FaQrNQbXIvbWfqsi3iIGhQoc3TAMZXKKLMAaWDyYgy//30JT84nJz//cgTWdaMf4Gz8Gpa45lzb5Z89PBEJxYu0sHxCJ+fj49E3YgaT8/HgeNRyazXDhuwSTXP0KEYnp9+S0cnpt2D0Z41u/XW0gitU0skS6cuMdggESv3Cn3h6OMfKzG1YrkuzE0KtpYMXyqe181hylR1rSXPrSt57EQk+ki2NX4ej4YjPaV2W0q1FIi4LhMMYTyYvxkegPEgga7nEK00wtw6sW0jThcgDWSjlEiGt9RIquWaUMCph4WxdcUPhMFOVCgZ7jS70Av3qBmll3XJ4J3Y/HsX35r25LJQPSxqwFZqBt7XLQhfFuQuokMTmloo1QLbqW6pbcBFIkwdDZnOETBpul+a2NnmYWPCH1nbFp8VhZb0i6xT6hHkMYOpbvLh7DvKdIA2qLkiDVGZLNPnsSUFU+SSOF4qKOuV2I34UwlECQfyWyro/zm0j2bkFVcrMnfTk6oxq1wnkfaGH9nT4CGVzF+rL/5HWQzykbYUp9L7/WU2BuhxkhXTkD1Le8YvJIcalVCbuBg7qeUjGK9QlBKDAP8dK2zUfrweVQO3Z702dojNI6IfvOUsRutK/m0/QXauM81Ivq6M5tG4RB6eBnQ985xYJrTLk7jDZbBNvJbMC4STkqbaGMlYSx6vVaiiDNaB1U3389vXz84vJ+eBkOBoWVOqQJyvrqZRmB7i9WgDfLeDmcrGXanYuFz/C1agrKYSfKa60VIYrTwjJpus9pqK6udoV1hMPbTap9HjldNPwcFs7kuksEtfSKZly3ZjOmqgvZ9ysLJGLwfNW/eCSF2Z3XTMBvmY1Ue90lmVY0Y75Tku31yyNzy6fvxKRSLvrW2lznuTkiq92chV6pEjIO2V0Gcpo98Ice5NZ7yx+u063HPmXGd87ZbNpi3TTbP1b0xdndIHqvXkjZk3T/Au552MB
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update User Profile"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/profile"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates the profile details of the logged in user. Note: all fields are optional but at least one should be sent in the request.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./update-user-profile.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./update-user-profile.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-user-profile.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-user-profile.mdx
new file mode 100644
index 000000000..7dd242e83
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/update-user-profile.mdx
@@ -0,0 +1,5 @@
+---
+title: Update User Profile
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml PATCH /profile"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-user-role.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-user-role.RequestSchema.json
deleted file mode 100644
index acbe46130..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-user-role.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"*/*":{"schema":{"type":"object","properties":{"user_id":{"type":"string"},"roles":{"type":"array","items":{"type":"string"}}},"example":{"user_id":"5ca230c9-da95-4bd1-b2a2-aa5d0df65efd","roles":["developer"]}}}},"required":false}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-user-role.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-user-role.StatusCodes.json
deleted file mode 100644
index b630610b2..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-user-role.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"type":"object","properties":{"message":{"type":"string"}},"example":{"message":"user roles were updated successfully"}},"example":{"message":"user roles were updated successfully"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-user-role.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-user-role.api.mdx
deleted file mode 100644
index 6ffaad56c..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-user-role.api.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-id: update-user-role
-title: "Update User Role"
-description: "Updates an SDP user’s role by  `user_ID `."
-sidebar_label: "Update User Role"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNV1Fv2zYQ/isHPjWFZDlu0qF6S5sMzTq03pxgD67RUtLZYi2R6pGKoxkG9jf29/ZLhqPkRG7SpFlTYC+WTN5993131JFcCycXVsRTcW6RrJgFIkObkqqcMlrE4rzKpEMLUsPkeAy1Rfrnr78tkCkQkgbgIw99OD2GjwMRCFMhSXY9za6cGfl3U6AIBOHnGq17abJGxGuRGu1QO359Gj3lh01zLCW/uaZCEQuTfMLUiUBUxNhOoeVZH1RlPUPrSOmF2ASCqdnejCSSjQiEcljaWzw2m0DgpSyrAnegxWEqR8+G6Yswky8Ow4Mk2w+TkRyFUh5mw2z+/BDnmbiKNxUZXmDBLMVs41FZriLMRDyXhUU/YiujbctvNBzyYzfh796IoJ8YWVWFSn1Oo0+WTb49SyVaKxd4m+YdyVd2XryvrYUVEkLtK5iBrdMUrZ3XRdF8tzf7Hwz3b2o/17J2uSH1J2aPlwUkMnTrSsFLR9Lej2CddHXfTtdlgsQQd6T4izR1NMRb42BH5jWLbZyD4X4P+UuPHwnclubZzdL8bChRWYb6x9fldnXXBL7BwOuwmNakXCPi6Vq8RElIR7XLRTydbWaBuAxTk+ECddh1pTAxWRNqWTIZfm9TiNoqo61HWWIj4js9A3Ehi/oKgQOV6HLD/aSSLs05DZJZiIg/Fxu17YPp0gW3YI5TUyFi4b23Kiac1TZxfS3XXa5Sb5Ap79btqCuvLxHkKDMk4AJKpZVebPv6L3+cwZOTyejw+R4Y6kY/wNH4FJbYcGfv8rKDx02Vg7Sw/DlMTsb7w0diBpOTcbg/bLm1mmHtzBL1Zu9BjEYHj8lodPAYjH6rkZpvo+VNoZIkS3RfZ9Qj4CltA39md//RKD03Ppxy/OmIicOikATHyiY1WSxROxgX0s0NlVx7Xs1ItqXx02A4GPI6rctSEn8HZznC3RhPJsfjPVAWJDhjCkhqVTiYGwJDC6m7FFlwBkq5REjqYgmVbBjFj0pYkKkrMHMgTFWl/IS5QALXi67RrQwtBzdy9/+j+F6/12e5sj6kBlOhDq2pKUWoyHCjBJdLx9MtFaPBGQ9/C1wAUmd+glsSpFJDgjA3tc68Y85/isKseLUQVsYqZ0ihjZlHCFPb4kXdM8x6SQqrLklhItMl6mz2JHeusnEULZTL62SQmjJ6EMJeDF78FZVmu5ytJ9uZeVVKz0laR3XqauoEcl3cfTUdPEDZnPxm9j3SthD3aVthAlvb/6wmx6IM01ySs3dS7tlFjhCjUioddQN36rlPxmssSvBAnn+GVWEaXl73KoHast2bOkHS6NAO3nOXckilfTefIF2olPvSVlZHc2BoEXmj0MxD25kFolApauvPANvGW8k0Rxj5PtXuoYwVR9FqtRpIP+vROlcb/Xr66uTt5CQcDYaD3JWF75OVsa6UugfcXmSAbzLQXWV2+kzvKvPQG1PX+x1euqgqpNK8RXju6+6gMPXnant105gFIjfW8cR6nUiL51RsNjzctvp4OuNTCCmZcJufzjbBdve5PsO8avmGZxz++tDC17BNsDU6SlOsXG/6xnFv53wzPjp79VoE7cmHLwYmYyeSK+YuV/5IEwh5Y9db+l2ve2GO2ynd9IJ/ua22HPmXGd/qsl63e+pmc2XfTn3Vo0vU1prLwZe5fwHboUtd
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update User Role"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/users/roles"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates an SDP user’s role by  `user_ID `.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./update-user-role.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./update-user-role.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-user-role.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-user-role.mdx
new file mode 100644
index 000000000..2e0fd263b
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/update-user-role.mdx
@@ -0,0 +1,5 @@
+---
+title: Update User Role
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml PATCH /users/roles"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-wallet.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-wallet.ParamsDetails.json
deleted file mode 100644
index 700562307..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-wallet.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"ID of the wallet to update","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-wallet.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-wallet.RequestSchema.json
deleted file mode 100644
index 1e44d4a1d..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-wallet.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"description":"Wallet to be updated","content":{"application/json":{"schema":{"type":"object","properties":{"name":{"type":"string","description":"Human-readable name of the wallet provider"},"homepage":{"type":"string","description":"Homepage URL of the wallet provider"},"deep_link_schema":{"type":"string","description":"Deep link schema for the wallet application"},"sep_10_client_domain":{"type":"string","description":"SEP-10 client domain for authentication"},"enabled":{"type":"boolean","description":"Whether the wallet is enabled for use"},"assets":{"type":"array","description":"Array of asset references supported by this wallet","items":{"oneOf":[{"type":"object","description":"Asset reference by ID","properties":{"id":{"type":"string","description":"Asset ID"}},"required":["id"]},{"type":"object","description":"Classic asset reference","properties":{"type":{"type":"string","enum":["classic"]},"code":{"type":"string","description":"Asset code"},"issuer":{"type":"string","description":"Asset issuer address"}},"required":["type","code","issuer"]},{"type":"object","description":"Native XLM asset reference","properties":{"type":{"type":"string","enum":["native"]}},"required":["type"]}]}}},"minProperties":1,"title":"UpdateWalletRequest"}}},"required":true}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-wallet.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/update-wallet.StatusCodes.json
deleted file mode 100644
index 80eb47292..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-wallet.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Wallet updated successfully","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"created_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"}},"title":"Wallet"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-wallet.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-wallet.api.mdx
deleted file mode 100644
index 8fbc4c027..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/update-wallet.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: update-wallet
-title: "Update Wallet"
-description: "This endpoint is used to enable or disable a wallet provider. Note: the organization should coordinate with the wallet provider before selecting a particular wallet provider for a disbursement."
-sidebar_label: "Update Wallet"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWFtz27YS/isYPMUzom6R4x6+ObE78WlO6lpO06mj8YDkSkRFAiguUlQN//uZBUiJuviS1p3pNA+OTex++HaxWOzumlo2MzS+o59ZUYA1dNKhGZhUc2W5FDSmtzk3BESmJBeWcEOcgYxYSUCwpAAiNcm48b8ysvQoRGm54BnoLvkoLcTE5ig3Y4L/wRCWmFy6IiOplDrjglkgS25zL7cHQRKYSg3EQAGp5WJGGFFMW566gukD6anUhCGhxGkDJQjbpR0qFWi/8VVGY/pJZcxCMJh2qGKalWBBox/WVLASaEx5RjuUowMUsznd98rVBZHTNl8rifO4tEM1/O64hozGVjvoUGNXBWIaXqoCBeCrKmQGNJ6ywqBAmkPJaLymdqW8pNVczGhVTQIaGPtWZiuU2OXxebN7AjUBJJ5KYUFYlGdKFTz11vd+M6i0PtxPJr9B6p2h0VeWg8HV4It9Vvu+eO9KJiINLPNRgEp7zmmOh1YdmssSFJs9B7eWJJ9uPjwCmAGo+4KL+f1DbtwHvgBQBDVI0PBR00JvuQw3MKDuB/37tOAg7H0mS8bF05uML6+jQZ8ELRK0Qng6m4OwrQ3CTcpamImUBTBxAPo5B5vDDll/O72+R3cGEJIZg7d5i8i0ZqsDvHP8ir718kTDFDSIFAwxTimpLWQkWRGLOWDZXBhuofTQUsCPU39p9sNob5ddcES8ujgINp497dSAdHVBq6p9ze5QeVJ1niLyrmDG8HTf2gMqAeWQDAhX4m5pwMEtaeov8vOIe9mqQ7kxDvRztYI0YVmmwZgD0z1EzWMD/QxnfGSWL4D88uF/f9kfwkPRyVFqk2pS4ULJxXULddChllufF9sJ+SZkO1rtYmEi9R+MksIEVsN+/8GEWKdCYlyagjFTVxSrl8uLx0MVvjKf32N6yjL2H8hOo9HpKYtGZ98NI9YHiAZv+mdvzqCfQTLAOHgov26RfuaJZsKSc2M4euXx/LnVy61VJu71FkGfKdVNZfkt2WyLxRSPMlh0D7Gek3qf4tQzmUJ4xEs14KndM3sMaSp1iSsUjzayvIQd+GF/+Drqn0WvB7fDfnzaj0en3Tej735F4DocXhq42sZwXU5UPm5HxyLzLctIE90vFomgtXxGIrkAy3hhCEuks/71CIr4+Hy1mpknd6rCP7RtcGjbJ4GvmtT8j5csPx4w7vmkqbHMuraccGUSyoYSjDl6jWo7N+e/4UE/Skt27NzSaDYa9Qct6H2NjQtfH7rwe6kTnmUg/n7/PWDelkFDc3RIEy36XjrxLz/maW3isRMetU/4Box0OgUiNlrNTTGQOs3tyldIb4Fp0OfO5jS+m2BdX4LNZRYajDT3jQgu0l4otExvzbOKIoxeNM2J0wWNKUX1Bn2MXg5uaO+xLfwU/wGOVH51VIZ+LAeG3RMeKOPCd1mCjC+uyX8/35JXl+Ph6ZsT7PTC13tyfn1F5rDC3qrul3bwmtYpwOIxjC+vB/0XYkbq0tpzCzaTtZVzENXJNzEajl6S0XD0Eox+cqBXz6PlRcmmfX2IUYuAp9Rs/Duq+zcML+zNtsu83F6JWm/zqmyLj/ZLs18EbNeOFxvtArLufEKj3HQtd6HE2maCjSuayrupu7dQTU19RKkuTyss17mYSu/a+t0eWyhwkHDRGhmQ64JZLAowzmmH4vULLj/r9rt9tMuVJdMrPx4B8jjGq/HF9Qm2aYxYKQuSOF5Y36u1RyIGe/iSzYEkrpgTxVaI4r8yMtPSKWzTNKRccb8gF3Uf2OwuwC6lnncP4uSfR/GL+CL8XAm3FEQqEFGdRpWWmOKJzZnvbQMVKYiVqhkC7MF1CBOZX8CYICkTOAzxudgr5vhHUcgl3gwNShpupeZgYuQRkTsT8Hr1/1F7fBSp2klRwtI5iGzyqqljZ9zmLgk17LcgnMTEG7+hsmqurvFkazFvFRdTzYzVLrVO1wY204pHz7T7DZZNtX/I/4ppDcRTti0hIY3sn7Ymh6KM0pxpax6l3JLrWQ3Qw/TTqz88as9TZryHoiQeyPPPQBVyheH1pCXEGZT7wSWgBVgw3S+YkS3o0vw4HYNe8LTdLNU0u1LPel4oktPI1GIdWvAUhGnn6nPF0hzI0OepUC8gVtzrLZfLLvOrHq1WNb0PV+8uP44vo2G3381tWfg3QUljSyZawKFLJ5u56U6SWW+LwX/FxLh+OSx8tT1V4KtV1d5c13XaHa3rNNqhMY6f8HU0FhfW64QZ+KSLqsLP4aGN7yYdumCao+H+iaudkG3GwA969NVNPQg5IY8Ono+ybooIgRXEghUO/6IdOodVmHP7d7EuQ5BXWHgXdo9uw3ipUTwo9PGdDRrnaQrKPirbLnuvz2/fvacdmtSD7TI86JotcYTOloGl9O7w5a3/tqYFEzMXapAAiuHKDiqmua+Y6l9aM8pdP+yXZMES/NmqH3ZV1utQj1XVRj4sPahR+3bjcnREVVX/B4dw43E=
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update Wallet"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/wallets/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint is used to enable or disable a wallet provider. Note: the organization should coordinate with the wallet provider before selecting a particular wallet provider for a disbursement.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./update-wallet.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./update-wallet.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./update-wallet.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/update-wallet.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/update-wallet.mdx
new file mode 100644
index 000000000..feef23a69
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/update-wallet.mdx
@@ -0,0 +1,5 @@
+---
+title: Update Wallet
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml PATCH /wallets/{id}"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions.ParamsDetails.json b/docs/platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions.ParamsDetails.json
deleted file mode 100644
index 6704cb13a..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions.ParamsDetails.json
+++ /dev/null
@@ -1 +0,0 @@
-{"parameters":[{"name":"id","in":"path","description":"ID of the Disbursement","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions.RequestSchema.json
deleted file mode 100644
index 74938dc9e..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"content":{"multipart/form-data":{"schema":{"required":["file"],"type":"object","properties":{"file":{"type":"string","description":"Disbursement instructions file to upload. The CSV file columns can vary depending om the way the disbursement was configured, and the fields are a subset of the following: [`phone`, `email`, `id`, `amount`, `verification`, `paymentID`, `walletAddress`]","format":"binary"}}}}},"required":true}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions.StatusCodes.json
deleted file mode 100644
index 4078d31b6..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"201":{"description":"Created","content":{"application/json":{"schema":{"type":"object","properties":{"message":{"type":"string"}},"example":{"message":"File uploaded succesfully"}},"example":{"message":"File uploaded succesfully"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"foo":{"type":"string"},"message":{"type":"string"}}}},"example":{"error":"Invalid file format *.xyz","extras":{"foo":"bar","message":"Not authorized"}}},"example":{"error":"Invalid file format *.xyz","extras":{"foo":"bar","message":"Not authorized"}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Disbursement not found"}}},"example":{"error":"Not found","extras":{"status":404,"message":"Disbursement not found"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions.api.mdx
deleted file mode 100644
index 2afcbd962..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions.api.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: upload-disbursement-instructions
-title: "Upload Disbursement Instructions"
-description: "Adds a file containing a list of receivers to a  `DRAFT` disbursement. This step is required before a disbursement can begin. The file must be a CSV and has a different possible formats according with the disbursement configuration, and they can be found at [public/resources/disbursementTemplates](https://github.com/stellar/stellar-disbursement-platform-frontend/tree/58873bbf36cff4614e603daf449079b1d9fad24a/public/resources/disbursementTemplates). The operation is idempotent, guaranteed by deleting and recreating the disbursement attributes when this endpoint is called."
-sidebar_label: "Upload Disbursement Instructions"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWFlz2zYQ/isYPMUdSpQdNWn45sTO1G2ndSOnfVA8NUgsRdQgwOKQomr03zsLkDJ12LncTqdTP8g8dhffHgC/3RV1bGZpNqVnwubeWKhBOUuvE8rBFkY0TmhFM3rKuSWMlEICKbRyTCihZoQRKawjuiQGChBzMJY4TRghN2dvTl9f3RDeszskV5WwxDpoiLDEwB9eGOAkh1IbIGxLmBRMkRxmQqEaxKVrbx3JUfTV5BfCFCcVs0GxLMGgVqOtFbkEUmpTM2cJKwptOIJdCFcRV8HOMlqVYuYNQ0+TYNNVsGyXJ6X2ihPmyLTxuRRFasBqbwqwad/MFdSNZA7s9ZPKucZmaToTrvL5sNB1ah1IyUz3f9DXHKAegh2URisHiqfOAKRff/PN86d5Xj59VpTl+NnxGJ6NnnJWjscvRs9f5Mf8Rcn4yZilH4frKEZRNxA9xQQIDnWjHSiXkJlnhikHmI4l4SDBhQQrjqk1wMLtXvSYc0bk3oEliwoUcZhgULzRQjlco2BSAh/ShG6WvuA0o28bqRnvV92Fss74AiUsTWjDDKvBgcHyXFHFaqAZFZwmVGBFNsxVdLdML86wFhFl3zJNaFdrNHPGQ0KtW0q0Z0XdSKAJhfeN1BxoVjJpUaCooGY0W1G3bIKkM0LN6Hp9Ha2BdS81X6JEEfLm8LL20omGGZeGlHLmgo07a3dAphRLGrdau4LOf4cCwTYGY+UEWNQIUns4dj3v+0tEL5Rx4zhNfIh4LAPcPe1elr5WNlT7nBnMfAMqbBddh0Au2HI/7QtmNxsH+GbXkFKAxIMi7GbrcwuuS0ippdQLoWYZmd40lVZwk5AbqJmQeCE4/rJae+Xwag5GlKIIBYP3DVuGIjnDmwUWlTvl3IC1N9c0oXG304zmQjGzpGv82017eGAbrWyM7MnoGP9tB/IV1jpgmfXSyppGtmDS3y3KrfYr5J781WAtmx1IIQKE9ywUYF+OvsbMxHQBJ9YXBdjSS7n8PBVUGo9G+66+ZJy8iaX8eO6CMdoccBaBO8Pshy2UWh/UfyCQO3FpMdALNWdS8FjqsUTIV8P3yz9pH01Yj+bM0N4a9EftCPOu0kb8CZz+M0vEVB2oyreqJ/gvypV1zPm+nPJ1Dubz0rUTjz6Kbp3x6PgzkvQYhmNqnu6n5rU2ueAc1N+fl8Pe3QH4CIHoxnjfDfT4NZKd/3R5la2Hhwpg3C+Are+p2mj+zbaDeQuFN8ItA+95CcyAOfWuotn0GslHDa7SSKEaHc7tQIQyukX7bLoSfJ2KbUplwcw7PuWNpBmlaLBbb4JpjXHvr7qJL2vE97DcYx6n7TaJtLICxsFs9QiKTM4uyXe/XpEn55OTr58dEW3ap7+R08sLcgtLJIgtxduy17G9aBbzPjm/PB49EjIyOb8cHI8itugzWTl9C2p99EmITsaPiehk/BiIfvZglh8HK4iSDeO+D1EPQIDULfwHqofDR6gyfruFC/R6EhueLTZOLtuGB3NPE4olGWE8H46GI6xTX9dI4jKKXPVhG08mZ5dH2Ggw4rSWJPdC4oYyRJsZU22IQldas1sguZe3pCWTba86M9o3bQ8rGhFe6DmYQFu71RW4hTa3w73Y/fsgvlPvVGi0cUmFLZ8axN6QNEbjOUtcxUJ3FqFoRZxuOqK+Y+6O3Beaw3ZbjIp9ak8MNNoKp40AmyGOAZl+XPObs+IWFP+C9rm1cJTFKcMGyrIrZxvAtmLBK6FKw+IR6U3rIObFfSinw0/wrGvrH2Ey8CHfFpCTTvazvalA1oOiYsY9PMzoycWJRc2EStsHD/rzITe+BVmTYCjg59BIvezGDw/vNW9R7nufg1HgwA7f4SnlwNT2p3ICZi4KPJc6t1qYQ21maRAa6HJgW7GESlGAsuFD3x28DSsqICfhnIrfULSVpelisRiy8DZYa1Vt+sPFq/MfJ+eDk+FoWLlahnMSP901Uz3DcR6y7dXORGTr3OlNHf4fzv0/nPvS4VzLDxy8d2kjmVBII0J9r1qCOaVbBJMmNGuHcb0ivU5ohaw0m9LVKmcW3hq5XuPjyBGy6XVC58wIliM/mK7QKF7zzeDt3ip/8qYtySNy75jvoBsd91FIfOZMeryjCb2FZZworq/XSceeEFN88SquPLhC9TvFQxO+ddIpnRYFNK4nvtc/bVH4y58mVzSheTtIrMMEMgyzgt3k7hLJf0LZHp27DXSuvUDwB73d5YsRLP4i9IMqq1Uki+v1Rj6+ulejjeAmsOjrer3+CzIgngA=
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Upload Disbursement Instructions"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/disbursements/{id}/instructions"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Adds a file containing a list of receivers to a  `DRAFT` disbursement. This step is required before a disbursement can begin. The file must be a CSV and has a different possible formats according with the disbursement configuration, and they can be found at [public/resources/disbursementTemplates](https://github.com/stellar/stellar-disbursement-platform-frontend/tree/58873bbf36cff4614e603daf449079b1d9fad24a/public/resources/disbursementTemplates). The operation is idempotent, guaranteed by deleting and recreating the disbursement attributes when this endpoint is called.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails
-  {...require("./upload-disbursement-instructions.ParamsDetails.json")}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./upload-disbursement-instructions.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./upload-disbursement-instructions.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions.mdx
new file mode 100644
index 000000000..de4e2a22c
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions.mdx
@@ -0,0 +1,5 @@
+---
+title: Upload Disbursement Instructions
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml POST /disbursements/{id}/instructions"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/users.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/users.mdx
new file mode 100644
index 000000000..ca63bae82
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/users.mdx
@@ -0,0 +1,5 @@
+---
+title: Users
+---
+
+The users endpoints facilitate the creation of new SDP users - including setting the appropriate role, sending an email invitation, and activating a user - and managing roles.
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/users.tag.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/users.tag.mdx
deleted file mode 100644
index ca02e0b38..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/users.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: users
-title: "Users"
-description: "Users"
-custom_edit_url: null
----
-
-
-
-The users endpoints facilitate the creation of new SDP users - including setting the appropriate role, sending an email invitation, and activating a user - and managing roles.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/verify-receiver-registration.RequestSchema.json b/docs/platforms/stellar-disbursement-platform/api-reference/verify-receiver-registration.RequestSchema.json
deleted file mode 100644
index 171b53605..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/verify-receiver-registration.RequestSchema.json
+++ /dev/null
@@ -1 +0,0 @@
-{"title":"Body","body":{"description":"Verification data including phone_number/email, OTP, verification value, and reCAPTCHA token","content":{"application/json":{"schema":{"type":"object","properties":{"email":{"type":"string","description":"Email associated with the receiver in the SDP database. Either `phone_number` or `email` is required."},"phone_number":{"type":"string","description":"Phone number associated with the receiver in the SDP database. Either `phone_number` or `email` is required."},"otp":{"type":"string","description":"One-Time Password received for verification"},"verification":{"type":"string","description":"Verification value provided by the user"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"recaptcha_token":{"type":"string","description":"Token received from Google reCAPTCHA"}},"title":"ReceiverRegistrationRequest"}}},"required":true}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/verify-receiver-registration.StatusCodes.json b/docs/platforms/stellar-disbursement-platform/api-reference/verify-receiver-registration.StatusCodes.json
deleted file mode 100644
index 3fb428297..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/verify-receiver-registration.StatusCodes.json
+++ /dev/null
@@ -1 +0,0 @@
-{"responses":{"200":{"description":"Verification successful","content":{"application/json":{"schema":{"type":"object","properties":{"message":{"type":"string","example":"ok"}}}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
\ No newline at end of file
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/verify-receiver-registration.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/verify-receiver-registration.api.mdx
deleted file mode 100644
index 9743e74b7..000000000
--- a/docs/platforms/stellar-disbursement-platform/api-reference/verify-receiver-registration.api.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-id: verify-receiver-registration
-title: "Verify Receiver Registration"
-description: "This endpoint verifies the receiver's registration by validating the OTP and other verification values provided in the request body. A valid SEP-24 token should be included in the Authorization header of the request."
-sidebar_label: "Verify Receiver Registration"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWG1v2zYQ/isEv6wBJMs1sg3wNydx16xt4sVuh8E1HEo6W6wlUiUpu56h/z4cKcXyS+J2S4dhXxKLOt49D8m7e6gNNWyuaXdM72DOtVHMcCnoxKMx6Ejx3D526SjhmoCIc8mFIUtQfMZBE5MAURABX4L6QRPV8EHCNVmylMfMcDG3lrejAWEiJtIkoConkTNesrQATXIllzyGmHBR+f5cgDYklPG6RXrOIRn2B37nnBi5AEF0Ios0JiEQLqK0aEzuFSaRiv/pIiTAYlBEzpqOW9SjMgeH+DqmXfoBUa3vKk47i+LRataFjNe0u9lbog9NPjEzrAKE7PNECpiKIgtBBZAxnnq4Gt6RRfDsEim47A1Gl697jiX1aCSFAWEwLsvztJoTfNIYfEN1lEDG8JdZ50C7VIafIDLUo7lChoaDxrc2eMNMG8XFnO7vdx/NCNNaRpwZiMmKm2Rnu+tVHl4NLNuQaWiRPrd7e98kfE+kIvc28D3h2q49VxC3aOnRpuFpWAO0Js7630AnTX4a1K0Af8QzIAOm9UqquEYRk5ncPefoc+f5pPMPBwdkmyTh2nIsNKh9x9MZhzQ+5h5EkWG+X/VG/entq+nF9d3oNfXoH/3e3fTd7Y19GFzfUI/e9EbXtze9t9Prq+nN+3cX/TssDIabFPaQvbLRSsyQiOUmStjUnduT/EY2ibcLpmRGfpFynsI2B2hZbsMeS807l5e0LEuXpLiBtGtUAXZA51Jod/477faJ1NVFFIHWsyJ9vqzLQGs2h6P78YVluWUmF0jAcjg/hvKCxaRm+nz1QCn5FYl3BYbxVBMWysLYU+cmlkjAKKZPRiq33F4ecnsvWFWtIf7u5L4eNNWGmaJpV1Wq0nt8Tx3Nh319gEFvpCE7NLco6jjn7ZcNz/szvqdj61tDVChu1rQ73tBhf9A5xyZKu+NJOfHoFz+SMcxB+FUj9LEv+4Jl6BJ/u9AgNJdCWycLWNPukzM9asta7QEDZWASid04l/as5wxB0EBD3jn3uTCgWGT4EvwYcqm5CXaKKvJQS1AOQaFS2qXWb01viOfHbfAFMAXKsXzYSJbzN7A+SIKjggKPKuMCuzwTtt/8+vuIvOgPOz/+dIa9xY1OSW9wTRawRslRrdiOP+pRjkGcWzxgw/7gZfuZkFnN9LLtsDnOZGNLdHn2TYjqE/E8iDrnz4HotwLU+utgWVOSM8UyMI8jagCo9ZcN/Bmn23aEpehuKwf7jaR0CmtbSXclznbciovt464uOD5et/WD7n3Qdxu1jouZtCtTddChgTRlilxxHRZKQwbCkEHKzEyqDI+pC6odjp9b7VYbU6rIMqbW9i4A5GkfL4ZXgzMUU4wYKVMSFjw1VgxJNWei2k1NjCQZWwAJi3RBcrZGL3aUkbmSRY5qXUHEc25fSBR2phFdgFlJtWgdqor/HMSP4qOwlygMKYjMQfhaFiqyeg57DzEJM/jaQZGCGJnX95U9d+6SgC+wrpKICbwAzWSBtyunfGcyTeUKD7ZyNVIqDrqLOHwy1s5fUP3348Yi+Xm1SH7IogWIePIiMSbX3SCYc5MUYSuSWfBNHs66xJJ/gLKuM8/dISszy4qLmWLaqCIyhaoI4r6YU3va+gZmM2UVxj+hVrs4xW0FIalt/zabBNLMjxKmjH4ScsMuMAogyBgXQTXwJJ9TNF5DmhHryOKPIU/lur7ZP51rhUa7N0UISoAB3fqIBdWAyvTtbAhqySOsSzWtCmZLqnlgjXw583Vl5tGURyC0LbV1j8hZlADp2Drl2j366gbBarVqMfvWequm6uDt9WX/Ztj3O612KzFZaks6io2MiYZj9zGA1FcOsvc5YKfmbLai9f/8taRqrwa+mCBPGbdXWrvmm0qmjemjMm2/y008mqDC647pZoNX9PcqLUscdo22O56gOlSchdi5xpPSq3v/VlteumX3R4hsKyYP7g2lV8/oRRHk5knbpggd3A5H1HPqFO9yMsY5iq2w77IVikv8imSc5t24sQ1NmZgXTm07n3jG2IFKWViVUv1AVvUrsW4g3JdBjgj+RVpHp2w2TgOV5YO9e/XojGppa2vc20lZln8B8hoZrw==
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-import Translate from "@docusaurus/Translate";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Verify Receiver Registration"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/sep24-interactive-deposit/verification"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint verifies the receiver's registration by validating the OTP and other verification values provided in the request body. A valid SEP-24 token should be included in the Authorization header of the request.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
->
-  <Translate id="theme.openapi.request.title">Request</Translate>
-</Heading>
-
-<ParamsDetails>
-  
-</ParamsDetails>
-
-<RequestSchema
-  {...require("./verify-receiver-registration.RequestSchema.json")}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  {...require("./verify-receiver-registration.StatusCodes.json")}
->
-  
-</StatusCodes>
-
-
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/verify-receiver-registration.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/verify-receiver-registration.mdx
new file mode 100644
index 000000000..15dd1fd31
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/verify-receiver-registration.mdx
@@ -0,0 +1,5 @@
+---
+title: Verify Receiver Registration
+openapi: "openapi/stellar-disbursement-platform/bundled.yaml POST /sep24-interactive-deposit/verification"
+playground: none
+---
diff --git a/docs/platforms/stellar-disbursement-platform/index.mdx b/docs/platforms/stellar-disbursement-platform/index.mdx
new file mode 100644
index 000000000..63fbfd1f4
--- /dev/null
+++ b/docs/platforms/stellar-disbursement-platform/index.mdx
@@ -0,0 +1,14 @@
+---
+title: Stellar Disbursement Platform
+sidebarTitle: Introduction
+"og:title": Stellar Disbursement Platform Introduction
+description: "The Stellar Disbursement Platform (SDP) is a tool built for organizations to make bulk payments to a group of recipients over the Stellar network."
+---
+
+This is an open-source project that is built on top of the Stellar network, and the code can be found on the following repositories:
+
+- [stellar/stellar-disbursement-platform-backend](https://github.com/stellar/stellar-disbursement-platform-backend): This repository contains the backend and infrastructure code for the Stellar Disbursement Platform.
+- [stellar/stellar-disbursement-platform-frontend](https://github.com/stellar/stellar-disbursement-platform-frontend): This repository contains the web frontend code for the Stellar Disbursement Platform.
+- [stellar/helm-charts](https://github.com/stellar/helm-charts/tree/main/charts/stellar-disbursement-platform): This repository contains the Helm chart for deploying the Stellar Disbursement Platform using Kubernetes.
+
+In this section, you'll find an [Admin Guide](/docs/platforms/stellar-disbursement-platform/admin-guide/overview) that will teach you how to run the Stellar Disbursement Platform as well as an [API Reference](/docs/platforms/stellar-disbursement-platform/api-reference/admin).
diff --git a/docs/tokens/README.mdx b/docs/tokens/README.mdx
deleted file mode 100644
index 523b489a7..000000000
--- a/docs/tokens/README.mdx
+++ /dev/null
@@ -1,93 +0,0 @@
----
-sidebar_position: 10
-title: "Issuing Assets vs. Creating Custom Tokens: Key Differences & Best Practices"
-sidebar_label: Stellar Assets and Contract Tokens
-description: "Learn about the differences between issuing assets on the Stellar network, creating smart contract tokens, and information and best practices for each."
----
-
-:::info
-
-The term "custom token" has been deprecated in favor of "contract token". View the conversation in the [Stellar Developer Discord](https://discord.com/channels/897514728459468821/966788672164855829/1359276952971640953).
-
-:::
-
-# Stellar Assets and Contract Tokens
-
-Tokens exist in two forms on Stellar:
-
-1. Assets issued by Stellar accounts (`G...` addresses) and their built-in [Stellar Asset Contract (SAC)][sac] implementation, and
-2. [Contract tokens][ti] issued by a deployed WASM contract (`C...` addresses).
-
-Several factors can help you determine whether to issue an asset on Stellar or create a contract token with a smart contract for your project.
-
-However:
-
-### TL;DR
-
-If possible, we recommend issuing a Stellar asset and using the SAC to interact with that asset in smart contracts or to send to contract addresses. More on why below.
-
-## Issuing assets on Stellar
-
-Stellar has first-class support for asset tokenization — issuing an asset can be done using a [built-in transaction](./quickstart.mdx) without the development of a smart contract.
-
-Stellar’s transactions are fast and cost-effective, making the network great for remittances and micropayments. It also has built-in features for compliance, asset management, and auditing. If you are looking to perform transfers of value, issuing assets on Stellar has all the needed capabilities.
-
-Stellar assets:
-
-- Are compatible with Stellar ecosystem products (such as Stellar wallets) and other ecosystem products (such as exchanges).
-- Benefit from [anchors](../learn/fundamentals/anchors.mdx), the bridges between the Stellar network and traditional financial systems. Explore the global [Stellar anchor directory](https://anchors.stellar.org) for further details.
-- Give the issuer granular control over asset management with features that allow the issuer to [name the asset](./control-asset-access.mdx#naming-an-asset), [determine access control](./control-asset-access.mdx#controlling-access-to-an-asset-with-flags), [limit asset supply](./control-asset-access.mdx#limiting-the-supply-of-an-asset), [publish asset information](./publishing-asset-info.mdx), and [ensure compliance](./anatomy-of-an-asset.mdx#compliance).
-
-:::note
-
-Note that while these items are also possible with smart contract tokens, it is more work to build the token contract rather than using the already-implemented features of Stellar asset tokens.
-
-:::
-
-Assets issued on the Stellar network are accessible to smart contracts with the use of that asset’s Stellar Asset Contract (SAC).
-
-### Stellar Asset Contract
-
-The Stellar Asset Contract (SAC) is compiled into the protocol layer and allows smart contracts to interact with assets issued on Stellar. An instance of the SAC can be deployed for every Stellar asset by anyone who wants to interact with the asset from a contract. The SAC has access to all account balances (for XLM) and trustline balances (for all other assets) as well as smart contract token balances.
-
-Read more about the SAC [here][sac].
-
-Learn how to deploy a Stellar Asset Contract for an asset in [this How-To Guide](../tools/cli/cookbook/deploy-stellar-asset-contract.mdx).
-
-**Benefits of the SAC:**
-
-- Compatibility: the SAC benefits from Stellar assets' existing interoperability.
-- Cost and resource efficiency: the SAC is built into the protocol instead of being a contract that runs in a virtual machine. Each function within the SAC will be more resource-efficient than its contract-coded counterpart.
-- Less work: you don’t have to write an entirely new contract. A Stellar asset’s SAC already exists on the network and just needs to be deployed to be used.
-- Customization: Admin addresses can be contracts. Asset issuers can set a different smart contract as an admin for their asset’s SAC. Making the admin another smart contract allows the addition of custom and decentralized logic for the assets admin capabilities, such as authorizing balances and trust lines, minting tokens, etc.
-
-**Downside of the SAC:**
-
-- Other than the customization noted above, it is not possible to modify the behavior of Stellar assets or their SAC. If you’re looking to use assets in a way not supported by Stellar assets, you can create your own smart contract token using the token interface and all applications that interact with tokens using the token interface will be able to interact with the contract token.
-
-## Contract tokens
-
-If you have a unique use case where the capabilities Stellar Assets are not sufficient, you can create a contract token that implements the [token interface][ti]. The token interface specifies the functions and events a contract must implement to be compatible with applications that use tokens.
-
-The SAC also implements the token interface and applications that interoperate with the token interface can seamlessly interact with Stellar assets and contract tokens.
-
-:::note
-
-Smart contracts cannot use Stellar assets unless that Stellar asset has a deployed SAC. Anyone can deploy the SAC for a Stellar asset to its reserved address.
-
-:::
-
-**These example scenarios are not possible with the SAC and demonstrate what you could use the token interface for:**
-
-- As the creator of a new token, you decide to implement a feature within your token smart contract that enables you to receive a 1% fee from every transaction involving your token. Whenever someone transfers your token to another user, 1% of the transferred amount is automatically deducted and sent to a designated wallet address that you control.
-- You want to develop a factory contract that automates the creation of instances of a specific token. This contract serves as a centralized and standardized way to deploy new token contracts on demand without manual intervention each time a new instance is needed.
-
-## Helpful links
-
-- [Issue an asset tutorial][how-to-issue]
-- [Stellar Asset Contract][sac]
-- [Token Interface][ti]
-
-[how-to-issue]: ./how-to-issue-an-asset.mdx
-[sac]: ./stellar-asset-contract.mdx
-[ti]: ./token-interface.mdx
diff --git a/docs/tokens/anatomy-of-an-asset.mdx b/docs/tokens/anatomy-of-an-asset.mdx
index 557f39ff2..ef4eb0121 100644
--- a/docs/tokens/anatomy-of-an-asset.mdx
+++ b/docs/tokens/anatomy-of-an-asset.mdx
@@ -1,14 +1,13 @@
 ---
 title: Assets Overview & Comparison
 description: Asset Overview and Comparison of Stellar Asset (with SAC), SEP-41 Contract Token, and T-REX (Token for Regulated Exchanges)
-sidebar_position: 20
 ---
 
-:::info
+<Info>
 
 The term "custom token" has been deprecated in favor of "contract token". View the conversation in the [Stellar Developer Discord](https://discord.com/channels/897514728459468821/966788672164855829/1359276952971640953).
 
-:::
+</Info>
 
 This brief compares the three primary tokenization models available on the Stellar network:
 
@@ -35,7 +34,7 @@ to help issuers select the most appropriate model for their use case.
 | **Relevant SEPs** | [SEP-1 (Stellar Info File)][sep-1] <br /><br /> [SEP-14 (Dynamic Asset Metadata)][sep-14] <br /><br />[SEP-41 (Soroban Token Interface)][sep-41] | [SEP-41 (Soroban Token Interface)][sep-41] | [SEP-41 (Soroban Token Interface)][sep-41] <br /><br /> [SEP-57 (T-REX / Token for Regulated EXchanges)][sep-57] |
 | **Examples** | [USDC](https://stellar.expert/explorer/public/asset/USDC-GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN) (Circle) <br /><br /> [EURC](https://stellar.expert/explorer/public/asset/EURC-GDHU6WRG4IEQXM5NZ4BMPKOXHW76MZM4Y2IEMFDVXBSDP6SJY4ITNPP2) (Circle) <br /><br /> [AQUA](https://stellar.expert/explorer/public/asset/AQUA-GBNZILSTVQZ4R7IKQDGHYGY2QXL5QOFJYQMXPKWRRM5PAV7Y4M67AQUA) (Aquarius) | [SolvBTC](https://stellar.expert/explorer/public/asset/CBIJBDNZNF4X35BJ4FFZWCDBSCKOP5NB4PLG4SNENRMLAPYG4P5FM6VN) (Solv Protocol) |  |
 
-_\* Starting with Yardstick, Protocol 26, by assigning a smart contract (`C...` address) as the owner of a Stellar Asset Contract, balances and transfer rules can be fully managed within the contract. Additionally, smart contracts can create trustlines programmatically using the SAC's [`trust` function](./stellar-asset-contract.mdx#creating-trustlines-from-a-contract), so a missing trustline no longer needs to be set up in a separate, prior transaction._
+_\* Starting with Yardstick, Protocol 26, by assigning a smart contract (`C...` address) as the owner of a Stellar Asset Contract, balances and transfer rules can be fully managed within the contract. Additionally, smart contracts can create trustlines programmatically using the SAC's [`trust` function](./stellar-asset-contract#creating-trustlines-from-a-contract), so a missing trustline no longer needs to be set up in a separate, prior transaction._
 
 ## 1. Stellar Assets (with Built-in [Stellar Asset Contracts][sac])
 
@@ -49,7 +48,7 @@ All assets issued by Stellar accounts (G…` addresses) are **Stellar Assets**.
 
 ### How they work
 
-- For protocol-level behavior and trustline semantics, see [Asset Design Considerations](./control-asset-access.mdx).
+- For protocol-level behavior and trustline semantics, see [Asset Design Considerations](./control-asset-access).
 - Implemented at the protocol level, the **Stellar Asset Contract (SAC)** provides a smart contract interface that enables Stellar assets to interoperate seamlessly with Stellar smart contracts.
 - Transfers between accounts and contracts using SAC resolve to the same trustline balance updates the Stellar protocol has always used. - Transfers to and from a `G...` account results in the same modifications to trustline ledger entries. - Transfers to and from contracts result in updates to the token contract's data entries.
 
@@ -58,8 +57,8 @@ All assets issued by Stellar accounts (G…` addresses) are **Stellar Assets**.
 - Has the benefits of Stellar assets (low cost, less computationally expensive), making these great for remittances and micropayments.
 - Can be used in Stellar smart contracts via SAC with a [SEP-41][sep-41] interface.
 - Maintains issuer controls and trustline semantics even when used from contracts.
-- Wide ecosystem wallet and indexer support. Assets issued by `G...` accounts are compatible with Stellar ecosystem products (such as Stellar wallets) and other ecosystem products (such as exchanges). For example, benefit from [anchors](../learn/fundamentals/anchors.mdx), the bridges between the Stellar network and traditional financial systems. Explore the global [Stellar anchor directory](https://anchors.stellar.org) for further details.
-- Give the issuer granular control over asset management with features that allow the issuer to [name the asset](./control-asset-access.mdx#naming-an-asset), [determine access control](./control-asset-access.mdx#controlling-access-to-an-asset-with-flags), [limit asset supply](./control-asset-access.mdx#limiting-the-supply-of-an-asset), [publish asset information](./publishing-asset-info.mdx), and [ensure compliance](./anatomy-of-an-asset.mdx#compliance). Stellar assets provide built-in issuer control mechanisms by default. In contrast, contract tokens offer flexibility but require all control and compliance features to be explicitly designed and implemented in the contract.
+- Wide ecosystem wallet and indexer support. Assets issued by `G...` accounts are compatible with Stellar ecosystem products (such as Stellar wallets) and other ecosystem products (such as exchanges). For example, benefit from [anchors](../learn/fundamentals/anchors), the bridges between the Stellar network and traditional financial systems. Explore the global [Stellar anchor directory](https://anchors.stellar.org) for further details.
+- Give the issuer granular control over asset management with features that allow the issuer to [name the asset](./control-asset-access#naming-an-asset), [determine access control](./control-asset-access#controlling-access-to-an-asset-with-flags), [limit asset supply](./control-asset-access#limiting-the-supply-of-an-asset), [publish asset information](./publishing-asset-info), and [ensure compliance](./anatomy-of-an-asset#compliance). Stellar assets provide built-in issuer control mechanisms by default. In contrast, contract tokens offer flexibility but require all control and compliance features to be explicitly designed and implemented in the contract.
 - Native operations on Stellar Assets emit standardized events through the Stellar Asset Contract, allowing off-chain systems and indexers to observe asset activity in a uniform way. Event semantics are defined at the protocol level according to [CAP-67](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md).
 - Operations on Stellar Assets emit the same standardized events defined by SEP-41, because the Stellar Asset Contract implements the SEP-41 token interface, Payment operations on Stellar Assets surface identical transfer events, allowing off-chain systems and indexers to observe asset activity through a uniform way.
 - By default, the admin of a Stellar Asset Contract (SAC) is the asset issuer (a `G...` address). However, the admin can be changed to a smart contract. Assigning a contract as the SAC admin enables custom, onchain policy for administrative actions for privileged operations.
@@ -68,7 +67,7 @@ All assets issued by Stellar accounts (G…` addresses) are **Stellar Assets**.
 ### Tradeoffs
 
 - Accounts must have an active trustline to receive, hold, and transact.
-- As of Yardstick, Protocol 26, trustlines can be added programmatically through contract invocations using the SAC's [`trust` function](./stellar-asset-contract.mdx#creating-trustlines-from-a-contract), enabling assets that rely on bridging or chain abstraction patterns ([Learn more about CAP-73](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0073.md)). On earlier protocol versions, the trustline must be created with a separate `changeTrust` operation before a contract can interact with the account's balance.
+- As of Yardstick, Protocol 26, trustlines can be added programmatically through contract invocations using the SAC's [`trust` function](./stellar-asset-contract#creating-trustlines-from-a-contract), enabling assets that rely on bridging or chain abstraction patterns ([Learn more about CAP-73](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0073.md)). On earlier protocol versions, the trustline must be created with a separate `changeTrust` operation before a contract can interact with the account's balance.
 
 ### When to use
 
@@ -81,7 +80,7 @@ All assets issued by Stellar accounts (G…` addresses) are **Stellar Assets**.
 
 Fully customizable contract tokens that implement the **[SEP-41][sep-41] token standard**, with their own storage and logic. [Contract tokens][ti] issued by a deployed Wasm contract (`C...` addresses).
 
-### How they work
+### How they work {#how-they-work-1}
 
 - Issued and managed entirely in contract code.
 - Can be held by both `G…` accounts and `C…` accounts (no trustlines required).
@@ -93,27 +92,27 @@ Fully customizable contract tokens that implement the **[SEP-41][sep-41] token s
   - Custom transfer logic
   - Fee structures
 
-### Strengths
+### Strengths {#strengths-1}
 
 - Fully programmable token logic beyond what Stellar Asset Contract expresses.
 - [SEP-41][sep-41] standard ensures broad tooling compatibility.
 - Can be integrated into existing applications and DeFi protocols.
 - Some ecosystem wallet support.
 
-### Tradeoffs
+### Tradeoffs {#tradeoffs-1}
 
 - Higher execution costs compared to Stellar Asset operations.
 - Less widespread ecosystem support compared to Stellar Assets, including centralized exchange support.
 
-### When to use
+### When to use {#when-to-use-1}
 
 - DeFi primitives requiring complex tokenomics.
 - Asset behaviors not representable by Stellar Assets alone.
 - When extending SEP-41 with custom functionality.
 
-## 3. ERC-3643 / SEP-57 (T-REX) Tokens
+## 3. ERC-3643 / SEP-57 (T-REX) Tokens {#3-erc-3643--sep-57-t-rex-tokens}
 
-### What these are
+### What these are {#what-these-are-1}
 
 A permissioned token standard for regulated, compliance-aware assets that extends [SEP-41][sep-41] with identity and rules enforcement. T-REX tokens are issued by a deployed Wasm contract (`C...` addresses) and implement compliance logic directly in the contract suite.
 
@@ -168,13 +167,15 @@ Choose the right token implementation based on the use case:
   - Regulatory requirements for Real World Assets (RWAs)
   - Interoperability with Ethereum ERC-3643
 
-:::note[Summary: TLDR]
+<Note>
+
+**Summary: TLDR**
 
 - Stellar Assets are best for simple payments and fiat-backed assets, with optional smart contract interoperability via the Stellar Asset Contract.
 - SEP-41 Contract Tokens are ideal for DeFi and advanced tokenomics requiring full programmability.
 - SEP-57 ERC-3643 Tokens are designed for regulated Real World Assets, offering on-chain compliance and identity with institutional-grade controls.
 
-:::
+</Note>
 
 ## More Info about Stellar Asset Contract (SAC)
 
@@ -190,8 +191,8 @@ The SAC has read/write access to:
 
 This allows Stellar assets to interoperate seamlessly with smart contracts.
 
-- [Read more about the Stellar Asset Contract](./stellar-asset-contract.mdx)
-- [How to deploy a Stellar Asset Contract](../tools/cli/cookbook/deploy-stellar-asset-contract.mdx)
+- [Read more about the Stellar Asset Contract](./stellar-asset-contract)
+- [How to deploy a Stellar Asset Contract](../tools/cli/cookbook/deploy-stellar-asset-contract)
 
 ### Benefits of the SAC
 
@@ -199,7 +200,7 @@ This allows Stellar assets to interoperate seamlessly with smart contracts.
 
 The SAC preserves full compatibility with the existing Stellar asset model, including trustlines and authorization flags. For Stellar DEX, compatibility does not currently exist for SAC, but it does exist for the underlying assets via classic operations.
 
-#### Cost & Resource Efficiency
+#### Cost & Resource Efficiency {#cost--resource-efficiency}
 
 Because the SAC is compiled into the protocol (rather than implemented as a user-deployed contract running in a VM), its functions are more resource-efficient than equivalent contract-coded logic.
 
@@ -228,11 +229,11 @@ Key points:
 - Contract tokens allow full customization of token logic
 - Contract tokens provide the flexibility to implement features not available in Stellar Assets, such as transfer fees, vesting schedules, or custom mint/burn rules
 
-:::note
+<Note>
 
 Smart contracts cannot use Stellar assets unless that Stellar asset has a deployed SAC. Anyone can deploy the SAC for a Stellar asset to its reserved address.
 
-:::
+</Note>
 
 ### When You Need a Contract Token (Examples)
 
@@ -245,7 +246,7 @@ Issuing assets is a core feature of Stellar: any asset can be tokenized (or mint
 
 Issuing an asset on Stellar is easy and only takes a few operations. However, there are additional considerations you may need to think about depending on your use case, such as publishing asset information, compliance, and asset supply, which we’ll cover in this documentation. Assets on Stellar have two identifying characteristics: the asset code and the issuer. Since more than one organization can issue a credit representing the same asset, asset codes often overlap (for example, multiple companies offer a USD token on Stellar). Assets are uniquely identified by the combination of their asset code and issuer.
 
-Assets issued on the Stellar network are accessible to smart contracts. Every Stellar asset has reserved a [Stellar Asset Contract](./stellar-asset-contract.mdx) that can be deployed by anyone who wants to be able to interact with the asset from a contract.
+Assets issued on the Stellar network are accessible to smart contracts. Every Stellar asset has reserved a [Stellar Asset Contract](./stellar-asset-contract) that can be deployed by anyone who wants to be able to interact with the asset from a contract.
 
 ## Stablecoins
 
@@ -253,7 +254,7 @@ One major category of assets is the stablecoin. A stablecoin is a blockchain-bas
 
 Reserve-backed stablecoins are pegged to a real-world asset at a 1:1 ratio. Because the underlying asset is maintained as collateral, users should be able to trade their stablecoin for the asset at any time. Asset reserves can be maintained by independent custodians and should be regularly audited.
 
-Currently, one of Stellar's most significant use cases is the tokenization of fiat currency for processes like cross-border payments. With anchors, users can connect Stellar tokens to existing rails that allow for the deposit of real-world assets in exchange for digital currency and vice versa. Learn more about anchors in our [Anchors section](../learn/fundamentals/anchors.mdx).
+Currently, one of Stellar's most significant use cases is the tokenization of fiat currency for processes like cross-border payments. With anchors, users can connect Stellar tokens to existing rails that allow for the deposit of real-world assets in exchange for digital currency and vice versa. Learn more about anchors in our [Anchors section](../learn/fundamentals/anchors).
 
 ### Treasury management
 
@@ -263,11 +264,11 @@ When issuing a reserve-backed stablecoin, you must set up its off-chain reserve,
 
 As an asset issuer, you may need to comply with regulatory requirements that vary based on jurisdiction. Stellar has built-in features that can help meet these requirements, such as:
 
-- [Controlling access to an asset with flags](./control-asset-access.mdx#controlling-access-to-an-asset-with-flags)
+- [Controlling access to an asset with flags](./control-asset-access#controlling-access-to-an-asset-with-flags)
 - [SEP-8: Regulated Assets](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0008.md) - regulated assets are assets that require an issuer’s approval (or a delegated third party’s approval) on a per-transaction basis. Check out this Stellar Ecosystem Proposal to learn how to implement regulated assets into your use case.
 
-[sac]: ./stellar-asset-contract.mdx
-[ti]: ./token-interface.mdx
+[sac]: ./stellar-asset-contract
+[ti]: ./token-interface
 [sep-1]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md
 [sep-14]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0014.md
 [sep-41]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0041.md
diff --git a/docs/tokens/control-asset-access.mdx b/docs/tokens/control-asset-access.mdx
index 29381d2bb..3c28b9f03 100644
--- a/docs/tokens/control-asset-access.mdx
+++ b/docs/tokens/control-asset-access.mdx
@@ -1,13 +1,13 @@
 ---
 title: Asset Design Considerations
-sidebar_position: 40
+description: "It is best practice on the Stellar network to create two accounts when issuing an asset: 1) the issuing account and 2) the distribution account."
 ---
 
 ## Issuing and distribution accounts
 
 It is best practice on the Stellar network to create two accounts when issuing an asset: 1) the issuing account and 2) the distribution account.
 
-The **issuing account** creates (or mints) the asset on the network by executing a payment operation. The issuing account will always be linked to the asset’s identity. Any account wanting to hold the asset must first establish a trustline with the issuing account. Read about trustlines in our [Trustlines section](../learn/fundamentals/stellar-data-structures/accounts.mdx#trustlines).
+The **issuing account** creates (or mints) the asset on the network by executing a payment operation. The issuing account will always be linked to the asset’s identity. Any account wanting to hold the asset must first establish a trustline with the issuing account. Read about trustlines in our [Trustlines section](../learn/fundamentals/stellar-data-structures/accounts#trustlines).
 
 The **distribution account** is the first recipient of the issued asset and handles all other transactions.
 
@@ -29,7 +29,7 @@ Using a distribution account is better for auditing because an issuing account c
 
 One thing you must decide when issuing an asset is what to call it. An asset code is the asset’s identifying code. There are three possible formats: Alphanumeric 4, Alphanumeric 12, and liquidity pool shares.
 
-Learn about liquidity pool shares in the [Liquidity on Stellar section](../learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx).
+Learn about liquidity pool shares in the [Liquidity on Stellar section](../learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools).
 
 - Alphanumeric 4-character maximum: Any characters from the set a-z, A-Z, 0-9 are allowed. The code can be shorter than 4 characters, but the trailing characters must all be empty.
 - Alphanumeric 12-character maximum: Any characters from the set a-z, A-Z, 0-9 are allowed. The code can be any number of characters from 5 to 12, but the trailing characters must all be empty.
@@ -70,11 +70,11 @@ There are three levels of authorization an asset issuer can remove using the `Se
 
 - `AUTHORIZED_FLAG`: signifies complete authorization allowing an account to transact freely with the asset to make and receive payments and place orders.
 - `AUTHORIZED_TO_MAINTAIN_LIABILITIES_FLAG`: denotes limited authorization that allows an account to maintain current orders but not to otherwise transact with the asset.
-- `CLAWBACK_ENABLED`: enables the issuing account to take back (burning) all of the asset. See our [section on Clawbacks](../build/guides/transactions/clawbacks.mdx) for more information.
+- `CLAWBACK_ENABLED`: enables the issuing account to take back (burning) all of the asset. See our [section on Clawbacks](../build/guides/transactions/clawbacks) for more information.
 
 #### Clawback Enabled (0x8)
 
-With the `AUTH_CLAWBACK_ENABLED_FLAG` flag set, any _subsequent_ trustlines established with this account will have clawbacks enabled. You can read more about clawbacks (and selectively controlling them on a per-trustline basis) [here](../build/guides/transactions/clawbacks.mdx).
+With the `AUTH_CLAWBACK_ENABLED_FLAG` flag set, any _subsequent_ trustlines established with this account will have clawbacks enabled. You can read more about clawbacks (and selectively controlling them on a per-trustline basis) [here](../build/guides/transactions/clawbacks).
 
 Note that this flag requires that revocable is also set.
 
@@ -106,13 +106,13 @@ The authorization sandwich allows the issuer to inspect the specific payment and
 
 ### Sample code
 
-In the following code samples, proper error checking is omitted. However, you should always validate your results, as there are many ways that requests can fail. Refer to the [Error Handling](../data/apis/horizon/api-reference/errors/error-handling.mdx) page for tips on error management strategies.
+In the following code samples, proper error checking is omitted. However, you should always validate your results, as there are many ways that requests can fail. Refer to the [Error Handling](../data/apis/horizon/api-reference/errors/error-handling) page for tips on error management strategies.
 
 The following example sets authorization to be both required and revocable:
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 var StellarSdk = require("@stellar/stellar-sdk");
 var server = new StellarSdk.Horizon.Server(
   "https://horizon-testnet.stellar.org",
@@ -147,7 +147,7 @@ server
   });
 ```
 
-```java
+```java Java
 import org.stellar.sdk.*;
 import org.stellar.sdk.Network;
 import org.stellar.sdk.operations.SetOptionsOperation;
@@ -173,7 +173,7 @@ setAuthorization.sign(issuingKeys);
 server.submitTransaction(setAuthorization);
 ```
 
-```python
+```python Python
 from stellar_sdk import Keypair, Network, Server, TransactionBuilder, AuthorizationFlag
 from stellar_sdk.exceptions import BaseHorizonError
 
@@ -212,18 +212,20 @@ except BaseHorizonError as e:
     print(f"Error: {e}")
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## Limiting the supply of an asset
 
-:::danger[Warning]
+<Danger>
+
+**Warning**
 
 This section details how to lock your account with the purpose of limiting the supply of your issued asset. However, locking your account means you’ll never be able to do anything with it ever again- whether that’s adjusting signers, changing the home domain, claiming any held XLM, or any other operation. Your account will be completely frozen.
 
-:::
+</Danger>
 
 With that warning in mind, it is possible to lock down the issuing account of an asset so that the asset’s supply cannot increase. To do this, first set the issuing account’s master weight to 0 using the Set Options operation. This prevents the issuing account from being able to sign transactions and therefore, making the issuer unable to issue any more assets. Be sure to do this only after you’ve issued all desired assets to the distribution account. If the asset has a Stellar Asset Contract, also make sure the admin for the contract was not updated from the default (which is the issuer) using the `set_admin` contract call. If the admin was not the issuer, then the admin would be able to mint the asset even with the issuing account locked.
 
-Learn more about signature weights in the [Signatures and Multisig section](../learn/fundamentals/transactions/signatures-multisig.mdx).
+Learn more about signature weights in the [Signatures and Multisig section](../learn/fundamentals/transactions/signatures-multisig).
 
-See how to do this in the optional steps of the [Issuing an Asset Tutorial](./how-to-issue-an-asset.mdx#configure-maximum-supply).
+See how to do this in the optional steps of the [Issuing an Asset Tutorial](./how-to-issue-an-asset#configure-maximum-supply).
diff --git a/docs/tokens/cross-chain-transfers.mdx b/docs/tokens/cross-chain-transfers.mdx
index dcd8ac8e9..080ea0517 100644
--- a/docs/tokens/cross-chain-transfers.mdx
+++ b/docs/tokens/cross-chain-transfers.mdx
@@ -1,18 +1,17 @@
 ---
-sidebar_position: 90
 title: "Cross-Chain USDC Transfers with CCTP"
-sidebar_label: CCTP
+sidebarTitle: CCTP
 description: "Use Circle's Cross-Chain Transfer Protocol (CCTP) to move native USDC between Stellar and other supported chains."
 ---
 
-# Cross-Chain USDC Transfers with CCTP
-
 Circle's **Cross-Chain Transfer Protocol (CCTP)** supports native USDC transfers between Stellar and other CCTP-enabled chains — no wrapped assets, no third-party bridges.
 
-:::info[Full documentation]
+<Info>
+
+**Full documentation**
 
 CCTP on Stellar is documented and maintained by Circle. For contract addresses, supported chains, SDKs, code samples, and the attestation API:
 
 [CCTP on Stellar — Circle developer docs](https://developers.circle.com/cctp/references/stellar)
 
-:::
+</Info>
diff --git a/docs/tokens/how-to-issue-an-asset.mdx b/docs/tokens/how-to-issue-an-asset.mdx
index e9beabf47..c2c3563fb 100644
--- a/docs/tokens/how-to-issue-an-asset.mdx
+++ b/docs/tokens/how-to-issue-an-asset.mdx
@@ -1,46 +1,43 @@
 ---
-title: "Issue an Asset on Stellar: Set Trustlines, Manage Supply & Distribution"
-sidebar_label: Issue an Asset Tutorial
+title: Issue an Asset Tutorial
+"og:title": "Issue an Asset on Stellar: Set Trustlines, Manage Supply & Distribution"
 description: "Learn how to issue a Stellar asset, set trustlines, and manage supply. Follow this step-by-step guide to create and distribute assets on the network."
-sidebar_position: 70
 ---
 
-# Issue an Asset Tutorial
-
 In this tutorial, we will walk through the steps to issue an asset on the Stellar test network.
 
-:::note
+<Note>
 
-If you'd like to interact with an asset issued on the Stellar network in smart contracts, you can create or deploy the [Stellar Asset Contract](./stellar-asset-contract.mdx) for that asset.
+If you'd like to interact with an asset issued on the Stellar network in smart contracts, you can create or deploy the [Stellar Asset Contract](./stellar-asset-contract) for that asset.
 
-:::
+</Note>
 
 ## Prerequisites
 
 You must ensure you have the required amount of XLM to create your issuing and distribution accounts and cover the minimum balance and transaction fees. If you’re issuing an asset on the testnet, you can fund your account by getting test XLM from friendbot. If you’re issuing an asset in production, you will need to acquire XLM from another wallet or exchange.
 
-If you’d like to avoid your users having to deal with transaction fees, consider using fee-bump transactions. Read more in our [Fee-Bump Transaction Guide](../build/guides/transactions/fee-bump-transactions.mdx).
+If you’d like to avoid your users having to deal with transaction fees, consider using fee-bump transactions. Read more in our [Fee-Bump Transaction Guide](../build/guides/transactions/fee-bump-transactions).
 
-Learn about the testnet and mainnet in our [Networks section](../networks/README.mdx).
+Learn about the testnet and mainnet in our [Networks section](/docs/networks).
 
-Learn more about fees in our [Fees, Resource Limits, and Metering section](../learn/fundamentals/fees-resource-limits-metering.mdx).
+Learn more about fees in our [Fees, Resource Limits, and Metering section](../learn/fundamentals/fees-resource-limits-metering).
 
 ## Foundational tools
 
 ### Issuer account keypair
 
-First, you must generate a unique keypair. The public key will act as your [issuing identity](../learn/fundamentals/stellar-data-structures/assets.mdx#issuer) on the network, while you use the secret key to sign transactions.
+First, you must generate a unique keypair. The public key will act as your [issuing identity](../learn/fundamentals/stellar-data-structures/assets#issuer) on the network, while you use the secret key to sign transactions.
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 const issuerKeypair = StellarSdk.Keypair.random();
 
 console.log("Issuer Public Key:", issuerKeypair.publicKey());
 console.log("Issuer Secret Key:", issuerKeypair.secret());
 ```
 
-```python
+```python Python
 from stellar_sdk import Keypair
 
 issuer_keypair = Keypair.random()
@@ -49,14 +46,14 @@ print("Issuer Public Key:", issuer_keypair.public_key)
 print("Issuer Secret Key:", issuer_keypair.secret)
 ```
 
-```java
+```java Java
 KeyPair issuerKeypair = KeyPair.random();
 
 System.out.println("Issuer Public Key: " + issuerKeypair.getAccountId());
 System.out.println("Issuer Secret Key: " + issuerKeypair.getSecretSeed());
 ```
 
-```go
+```go Go
 import (
   "github.com/stellar/go-stellar-sdk/keypair"
   "fmt"
@@ -68,102 +65,101 @@ fmt.Println("Issuer Public Key:", issuerKeypair.Address())
 fmt.Println("Issuer Secret Key:", issuerKeypair.Seed())
 ```
 
-</CodeExample>
-
-:::info
+</CodeGroup>
 
-Your account address will not change once you issue your asset, even if you modify its [signers](../learn/fundamentals/transactions/signatures-multisig.mdx). Many issuers employ [vanity public keys](https://github.com/JFWooten4/stellar-vanity-toolkit) related to their asset. For instance, you might configure a custom signer in [base32](../learn/glossary.mdx#account-id) like `GASTRO...USD`.
+<Info>
 
-:::
+Your account address will not change once you issue your asset, even if you modify its [signers](../learn/fundamentals/transactions/signatures-multisig). Many issuers employ [vanity public keys](https://github.com/JFWooten4/stellar-vanity-toolkit) related to their asset. For instance, you might configure a custom signer in [base32](../learn/glossary#account-id) like `GASTRO...USD`.
 
-:::note
+</Info>
+<Note>
 
 Many users secure their issuing account with cold storage techniques, such as a hardware wallet or multisignature setup. This adds an extra layer of protection by keeping your secret key offline or requiring multiple approvals for transactions.
 
-:::
+</Note>
 
 ### Distribution account keypair
 
-Your asset can be issued and transferred between accounts through a payment, contract, or claimable balance. Although it is not required to create a distribution account, it is best practice, so we will do so in this example. Read more in our [Issuing and Distribution Accounts section](./control-asset-access.mdx#issuing-and-distribution-accounts).
+Your asset can be issued and transferred between accounts through a payment, contract, or claimable balance. Although it is not required to create a distribution account, it is best practice, so we will do so in this example. Read more in our [Issuing and Distribution Accounts section](./control-asset-access#issuing-and-distribution-accounts).
 
 #### Three Operations
 
 ##### Generate a new keypair
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 const distributorKeypair = StellarSdk.Keypair.random();
 ```
 
-```python
+```python Python
 distributor_keypair = Keypair.random()
 ```
 
-```java
+```java Java
 KeyPair distributorKeypair = KeyPair.random();
 ```
 
-```go
+```go Go
 distributorKeypair := keypair.MustRandom()
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ##### Import an existing keypair
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 const distributorKeypair = StellarSdk.Keypair.fromSecret(‘SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U6MM63WBSBZATAQI3EBTQ4’)
 ```
 
-```python
+```python Python
 distributor_keypair = Keypair.from_secret("SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U6MM63WBSBZATAQI3EBTQ4")
 ```
 
-```java
+```java Java
 KeyPair distributorKeypair = KeyPair.fromSecretSeed("SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U6MM63WBSBZATAQI3EBTQ4");
 ```
 
-```go
+```go Go
 distributorKeypair := keypair.MustParseFull("SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U6MM63WBSBZATAQI3EBTQ4")
 ```
 
-</CodeExample>
+</CodeGroup>
 
-##### Employ [multiple signatures](../learn/fundamentals/transactions/signatures-multisig.mdx)
+##### Employ [multiple signatures](../learn/fundamentals/transactions/signatures-multisig)
 
-:::danger
+<Danger>
 
-Be careful when working with raw secret keys. If you don't have issuer trustline [clawback](../build/guides/transactions/clawbacks.mdx) enabled, any misstep here could permanently render assets lost. Many users put their first few projects on [testnet](../networks/README.mdx#testnet) or try out [Quests](../learn/interactive/quest.mdx) which provide a low-stakes introductory sandbox.
+Be careful when working with raw secret keys. If you don't have issuer trustline [clawback](../build/guides/transactions/clawbacks) enabled, any misstep here could permanently render assets lost. Many users put their first few projects on [testnet](/docs/networks#testnet) or try out [Quests](../learn/interactive/quest) which provide a low-stakes introductory sandbox.
 
-:::
+</Danger>
 
 ### Local asset object
 
-The asset object is a combination of your [code](./control-asset-access.mdx#naming-an-asset) and your issuing public key. After your issuance, anyone can search the network for your unique asset.
+The asset object is a combination of your [code](./control-asset-access#naming-an-asset) and your issuing public key. After your issuance, anyone can search the network for your unique asset.
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 const astroDollar = new StellarSdk.Asset(
   "AstroDollar",
   issuerKeypair.publicKey(),
 );
 ```
 
-```python
+```python Python
 from stellar_sdk import Keypair, Asset
 
 astro_dollar = Asset("AstroDollar", issuer_keypair.public_key)
 ```
 
-```java
+```java Java
 Asset astroDollar = Asset.createNonNativeAsset("AstroDollar", issuerKeypair.getAccountId());
 ```
 
-```go
+```go Go
 import (
   "github.com/stellar/go-stellar-sdk/keypair"
   "github.com/stellar/go-stellar-sdk/txnbuild"
@@ -172,37 +168,35 @@ import (
 astroDollar := txnbuild.CreditAsset{Code: "AstroDollar", Issuer: issuerKeypair.Address()}
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::info
+<Info>
 
-While anyone can create an asset, there may be real-world [compliance](./anatomy-of-an-asset.mdx#compliance) implications relevant to your use case.
+While anyone can create an asset, there may be real-world [compliance](./anatomy-of-an-asset#compliance) implications relevant to your use case.
 
-:::
+</Info>
+<Note>
 
-:::note
+You’ll want to make sure you publish information about your asset to establish trust with your users and prevent errors. Learn how to do so with our [Publish Information About Your Asset section](./publishing-asset-info).
 
-You’ll want to make sure you publish information about your asset to establish trust with your users and prevent errors. Learn how to do so with our [Publish Information About Your Asset section](./publishing-asset-info.mdx).
-
-:::
+</Note>
 
 ## Network transactions
 
-These examples read accounts from and submit transactions to [Stellar RPC](../data/apis/rpc/README.mdx). RPC takes a transaction and answers immediately with the status `PENDING`, so you then poll for the final result. See [sendTransaction](../data/apis/rpc/api-reference/methods/sendTransaction.mdx) and [getTransaction](../data/apis/rpc/api-reference/methods/getTransaction.mdx).
+These examples read accounts from and submit transactions to [Stellar RPC](../data/apis/rpc). RPC takes a transaction and answers immediately with the status `PENDING`, so you then poll for the final result. See [sendTransaction](../data/apis/rpc/api-reference/methods/sendTransaction) and [getTransaction](../data/apis/rpc/api-reference/methods/getTransaction).
 
 ### Build transaction to establish distributor trustline
 
-Accounts must establish a [trustline](../learn/fundamentals/stellar-data-structures/accounts.mdx#trustlines) with the issuing account to hold that issuer’s asset. This is true for all assets except for the network’s native token, [Lumens](../learn/fundamentals/lumens.mdx).
-
-:::note
+Accounts must establish a [trustline](../learn/fundamentals/stellar-data-structures/accounts#trustlines) with the issuing account to hold that issuer’s asset. This is true for all assets except for the network’s native token, [Lumens](../learn/fundamentals/lumens).
 
-If you’d like to avoid your users having to deal with trustlines or XLM, consider using sponsored reserves. Read more in our [Sponsored Reserves guide](../build/guides/transactions/sponsored-reserves.mdx).
+<Note>
 
-:::
+If you’d like to avoid your users having to deal with trustlines or XLM, consider using sponsored reserves. Read more in our [Sponsored Reserves guide](../build/guides/transactions/sponsored-reserves).
 
-<CodeExample>
+</Note>
+<CodeGroup>
 
-```js
+```js JavaScript
 const StellarSdk = require("@stellar/stellar-sdk");
 const server = new StellarSdk.rpc.Server("https://soroban-testnet.stellar.org");
 const account = await server.getAccount(distributorKeypair.publicKey());
@@ -224,7 +218,7 @@ const transaction = new StellarSdk.TransactionBuilder(account, {
   .build();
 ```
 
-```python
+```python Python
 from stellar_sdk import Keypair, Asset, Network, SorobanServer, TransactionBuilder
 
 server = SorobanServer("https://soroban-testnet.stellar.org")
@@ -242,7 +236,7 @@ transaction = (
 )
 ```
 
-```java
+```java Java
 SorobanServer server = new SorobanServer("https://soroban-testnet.stellar.org");
 TransactionBuilderAccount distributorAccount = server.getAccount(distributorKeypair.getAccountId());
 
@@ -259,7 +253,7 @@ Transaction transaction = new TransactionBuilder(distributorAccount, Network.TES
   .build();
 ```
 
-```go
+```go Go
 import (
   "context"
 
@@ -289,15 +283,15 @@ transaction, _ := txnbuild.NewTransaction(
 )
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ### Issuer payment to distributor
 
-Payments are the most popular operation to actually issue (or mint) your asset, compared to [other issuances](../learn/fundamentals/transactions/list-of-operations.mdx#path-payment-strict-send). A payment creates the amount of an asset specified, up to [the maximum 64-bit integer](../learn/fundamentals/stellar-data-structures/assets.mdx#amount-precision). Relevantly, you do not need to scale up the issuing amount of your asset by the XDR [minimum increment](../learn/fundamentals/stellar-data-structures/assets.mdx#amount-precision).
+Payments are the most popular operation to actually issue (or mint) your asset, compared to [other issuances](../learn/fundamentals/transactions/list-of-operations#path-payment-strict-send). A payment creates the amount of an asset specified, up to [the maximum 64-bit integer](../learn/fundamentals/stellar-data-structures/assets#amount-precision). Relevantly, you do not need to scale up the issuing amount of your asset by the XDR [minimum increment](../learn/fundamentals/stellar-data-structures/assets#amount-precision).
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 // We're using TransactionBuilder(...) as a short-hand here
 // to show that these operations can be "chained" together.
 const transaction = new StellarSdk.TransactionBuilder(...)
@@ -311,7 +305,7 @@ const transaction = new StellarSdk.TransactionBuilder(...)
   }))
 ```
 
-```python
+```python Python
 # We're using TransactionBuilder(...) as a short-hand here
 # to show that these operations can be "chained" together.
 transaction = (
@@ -324,7 +318,7 @@ transaction = (
 )
 ```
 
-```java
+```java Java
 // We're using TransactionBuilder(...) as a short-hand here
 // to show that these operations can be "chained" together.
 Transaction transaction = new TransactionBuilder(...)
@@ -336,7 +330,7 @@ Transaction transaction = new TransactionBuilder(...)
     .build())
 ```
 
-```go
+```go Go
 // We're using TransactionBuilder(...) as a short-hand here
 // to show that these operations can be "chained" together.
 transaction, _ := txnbuild.NewTransaction(
@@ -356,29 +350,29 @@ transaction, _ := txnbuild.NewTransaction(
 )
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::note
+<Note>
 
 You can also create a market directly from the issuing account and issue tokens via trading.
 
-:::
+</Note>
 
 ### Optional transactions
 
 #### Configure maximum supply
 
-:::danger
+<Danger>
 
 This section details how to lock your account with the purpose of limiting the supply of your issued asset. However, locking your account means you’ll never be able to do anything with it ever again&mdash;whether that’s adjusting signers, changing the home domain, claiming any held XLM, or any other operation. Your account will be completely frozen.
 
-:::
+</Danger>
 
-You can permanently configure the exact number of an asset that will ever exist. Learn more about asset supply in our section on [Limiting the Supply of an Asset](./control-asset-access.mdx#limiting-the-supply-of-an-asset)
+You can permanently configure the exact number of an asset that will ever exist. Learn more about asset supply in our section on [Limiting the Supply of an Asset](./control-asset-access#limiting-the-supply-of-an-asset)
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 const lockAccountTransaction = new StellarSdk.TransactionBuilder(...)
   // This `setOptions` operation locks the issuer account
   // so there can never be any more of the asset minted
@@ -388,14 +382,14 @@ const lockAccountTransaction = new StellarSdk.TransactionBuilder(...)
   }))
 ```
 
-```python
+```python Python
 lock_account_transaction = (
   TransactionBuilder(...)
   .append_set_options_op(master_weight=0)
 )
 ```
 
-```java
+```java Java
 Transaction lockAccountTransaction = new TransactionBuilder(...)
   .addOperation(SetOptionsOperation.builder()
     .masterKeyWeight(0)
@@ -404,7 +398,7 @@ Transaction lockAccountTransaction = new TransactionBuilder(...)
   )
 ```
 
-```go
+```go Go
 lockAccountTransaction, _ := txnbuild.NewTransaction(
   txnbuild.TransactionParams{
     SourceAccount:        issuerAccount,
@@ -420,15 +414,15 @@ lockAccountTransaction, _ := txnbuild.NewTransaction(
 )
 ```
 
-</CodeExample>
+</CodeGroup>
 
 #### Approve distributor trustline
 
-If you enable the [authorization flag](./control-asset-access.mdx#authorization-required-0x1), the issuing account also needs to approve the distributor account's trustline request before the issuing payment. You will need to do this for all new accounts when set for your asset.
+If you enable the [authorization flag](./control-asset-access#authorization-required-0x1), the issuing account also needs to approve the distributor account's trustline request before the issuing payment. You will need to do this for all new accounts when set for your asset.
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 const issuingAccount = await server.getAccount(issuerKeypair.publicKey());
 const transaction = new StellarSdk.TransactionBuilder(...)
   .addOperation(
@@ -444,7 +438,7 @@ const transaction = new StellarSdk.TransactionBuilder(...)
   .build();
 ```
 
-```python
+```python Python
 from stellar_sdk import SorobanServer, Keypair, Network, TransactionBuilder, SetTrustLineFlags
 
 server = SorobanServer("https://soroban-testnet.stellar.org")
@@ -462,7 +456,7 @@ transaction = (
 )
 ```
 
-```java
+```java Java
 TransactionBuilderAccount issuerAccount = server.getAccount(issuerKeys.getAccountId());
 Transaction transaction = new TransactionBuilder(...)
   .addOperation(SetTrustlineFlagsOperation.builder()
@@ -476,7 +470,7 @@ Transaction transaction = new TransactionBuilder(...)
   .build();
 ```
 
-```go
+```go Go
 issuerAccount, _ := client.LoadAccount(ctx, issuerKeypair.Address())
 
 transaction, _ := txnbuild.NewTransaction(
@@ -496,13 +490,13 @@ transaction, _ := txnbuild.NewTransaction(
 )
 ```
 
-</CodeExample>
+</CodeGroup>
 
 ## Full Code Sample
 
-<CodeExample title="Issuing an Asset">
+<CodeGroup>
 
-```js
+```js JavaScript
 var StellarSdk = require("@stellar/stellar-sdk");
 var server = new StellarSdk.rpc.Server("https://soroban-testnet.stellar.org");
 
@@ -578,7 +572,7 @@ issueAstroDollar().catch(function (error) {
 });
 ```
 
-```python
+```python Python
 from stellar_sdk import Asset, Keypair, Network, SorobanServer, TransactionBuilder
 from stellar_sdk.soroban_rpc import GetTransactionStatus, SendTransactionStatus
 
@@ -658,7 +652,7 @@ payment_transaction_resp = submit(payment_transaction)
 print(f"Payment Transaction Resp:\n{payment_transaction_resp}")
 ```
 
-```java
+```java Java
 SorobanServer server = new SorobanServer("https://soroban-testnet.stellar.org");
 
 // Keys for accounts to issue and receive the new asset
@@ -708,7 +702,7 @@ GetTransactionResponse paymentResult = server.pollTransaction(paymentSend.getHas
 System.out.println("Payment Transaction: " + paymentResult.getStatus());
 ```
 
-```go
+```go Go
 package main
 
 import (
@@ -825,4 +819,4 @@ func main() {
 }
 ```
 
-</CodeExample>
+</CodeGroup>
diff --git a/docs/tokens/index.mdx b/docs/tokens/index.mdx
new file mode 100644
index 000000000..8f463142d
--- /dev/null
+++ b/docs/tokens/index.mdx
@@ -0,0 +1,92 @@
+---
+title: "Issuing Assets vs. Creating Custom Tokens: Key Differences & Best Practices"
+sidebarTitle: Stellar Assets and Contract Tokens
+description: "Learn about the differences between issuing assets on the Stellar network, creating smart contract tokens, and information and best practices for each."
+---
+
+<Info>
+
+The term "custom token" has been deprecated in favor of "contract token". View the conversation in the [Stellar Developer Discord](https://discord.com/channels/897514728459468821/966788672164855829/1359276952971640953).
+
+</Info>
+
+## Stellar Assets and Contract Tokens
+
+Tokens exist in two forms on Stellar:
+
+1. Assets issued by Stellar accounts (`G...` addresses) and their built-in [Stellar Asset Contract (SAC)][sac] implementation, and
+2. [Contract tokens][ti] issued by a deployed WASM contract (`C...` addresses).
+
+Several factors can help you determine whether to issue an asset on Stellar or create a contract token with a smart contract for your project.
+
+However:
+
+### TL;DR
+
+If possible, we recommend issuing a Stellar asset and using the SAC to interact with that asset in smart contracts or to send to contract addresses. More on why below.
+
+## Issuing assets on Stellar
+
+Stellar has first-class support for asset tokenization — issuing an asset can be done using a [built-in transaction](/docs/tokens/quickstart) without the development of a smart contract.
+
+Stellar’s transactions are fast and cost-effective, making the network great for remittances and micropayments. It also has built-in features for compliance, asset management, and auditing. If you are looking to perform transfers of value, issuing assets on Stellar has all the needed capabilities.
+
+Stellar assets:
+
+- Are compatible with Stellar ecosystem products (such as Stellar wallets) and other ecosystem products (such as exchanges).
+- Benefit from [anchors](/docs/learn/fundamentals/anchors), the bridges between the Stellar network and traditional financial systems. Explore the global [Stellar anchor directory](https://anchors.stellar.org) for further details.
+- Give the issuer granular control over asset management with features that allow the issuer to [name the asset](/docs/tokens/control-asset-access#naming-an-asset), [determine access control](/docs/tokens/control-asset-access#controlling-access-to-an-asset-with-flags), [limit asset supply](/docs/tokens/control-asset-access#limiting-the-supply-of-an-asset), [publish asset information](/docs/tokens/publishing-asset-info), and [ensure compliance](/docs/tokens/anatomy-of-an-asset#compliance).
+
+<Note>
+
+Note that while these items are also possible with smart contract tokens, it is more work to build the token contract rather than using the already-implemented features of Stellar asset tokens.
+
+</Note>
+
+Assets issued on the Stellar network are accessible to smart contracts with the use of that asset’s Stellar Asset Contract (SAC).
+
+### Stellar Asset Contract
+
+The Stellar Asset Contract (SAC) is compiled into the protocol layer and allows smart contracts to interact with assets issued on Stellar. An instance of the SAC can be deployed for every Stellar asset by anyone who wants to interact with the asset from a contract. The SAC has access to all account balances (for XLM) and trustline balances (for all other assets) as well as smart contract token balances.
+
+Read more about the SAC [here][sac].
+
+Learn how to deploy a Stellar Asset Contract for an asset in [this How-To Guide](/docs/tools/cli/cookbook/deploy-stellar-asset-contract).
+
+**Benefits of the SAC:**
+
+- Compatibility: the SAC benefits from Stellar assets' existing interoperability.
+- Cost and resource efficiency: the SAC is built into the protocol instead of being a contract that runs in a virtual machine. Each function within the SAC will be more resource-efficient than its contract-coded counterpart.
+- Less work: you don’t have to write an entirely new contract. A Stellar asset’s SAC already exists on the network and just needs to be deployed to be used.
+- Customization: Admin addresses can be contracts. Asset issuers can set a different smart contract as an admin for their asset’s SAC. Making the admin another smart contract allows the addition of custom and decentralized logic for the assets admin capabilities, such as authorizing balances and trust lines, minting tokens, etc.
+
+**Downside of the SAC:**
+
+- Other than the customization noted above, it is not possible to modify the behavior of Stellar assets or their SAC. If you’re looking to use assets in a way not supported by Stellar assets, you can create your own smart contract token using the token interface and all applications that interact with tokens using the token interface will be able to interact with the contract token.
+
+## Contract tokens
+
+If you have a unique use case where the capabilities Stellar Assets are not sufficient, you can create a contract token that implements the [token interface][ti]. The token interface specifies the functions and events a contract must implement to be compatible with applications that use tokens.
+
+The SAC also implements the token interface and applications that interoperate with the token interface can seamlessly interact with Stellar assets and contract tokens.
+
+<Note>
+
+Smart contracts cannot use Stellar assets unless that Stellar asset has a deployed SAC. Anyone can deploy the SAC for a Stellar asset to its reserved address.
+
+</Note>
+
+**These example scenarios are not possible with the SAC and demonstrate what you could use the token interface for:**
+
+- As the creator of a new token, you decide to implement a feature within your token smart contract that enables you to receive a 1% fee from every transaction involving your token. Whenever someone transfers your token to another user, 1% of the transferred amount is automatically deducted and sent to a designated wallet address that you control.
+- You want to develop a factory contract that automates the creation of instances of a specific token. This contract serves as a centralized and standardized way to deploy new token contracts on demand without manual intervention each time a new instance is needed.
+
+## Helpful links
+
+- [Issue an asset tutorial][how-to-issue]
+- [Stellar Asset Contract][sac]
+- [Token Interface][ti]
+
+[how-to-issue]: /docs/tokens/how-to-issue-an-asset
+[sac]: /docs/tokens/stellar-asset-contract
+[ti]: /docs/tokens/token-interface
diff --git a/docs/tokens/publishing-asset-info.mdx b/docs/tokens/publishing-asset-info.mdx
index 7aee329fc..4dea35605 100644
--- a/docs/tokens/publishing-asset-info.mdx
+++ b/docs/tokens/publishing-asset-info.mdx
@@ -1,6 +1,6 @@
 ---
 title: Publish Information About An Asset
-sidebar_position: 80
+description: "Stellar assets are defined by who issued them, what they represent, and the terms and conditions for their use."
 ---
 
 Stellar assets are defined by who issued them, what they represent, and the terms and conditions for their use. These should all be defined and made public by the issuer in a [Stellar info file](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md). It’s crucial to provide clear information about what it represents. On Stellar, you do that by linking your issuing account to a home domain, publishing a Stellar info file on that domain, and making sure that file is complete and accurate.
@@ -17,7 +17,7 @@ That way, everyone knows where to find it, anyone can look it up, and it proves
 
 Using a `set_options` operation, you can link your Stellar account to the domain that hosts your Stellar info file, thereby creating a definitive on-chain connection between this information and that account.
 
-## Completing your `stellar.toml`
+## Completing your `stellar.toml` {#completing-your-stellartoml}
 
 The first Stellar Ecosystem Proposal (SEP) is [SEP-1: Stellar Info File](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md) and specifies everything you would ever need to include in your Stellar info file. This section will walk through the sections of SEP-1 that relate to asset issuers. Use this section in conjunction with the SEP to ensure you complete your `stellar.toml` correctly.
 
@@ -65,7 +65,7 @@ Basic information about your organization goes into a TOML table called [`DOCUME
 - `ORG_OFFICIAL_EMAIL` The best business email address for your organization. This should be hosted at the same domain as your official website.
 - `ORG_SUPPORT_EMAIL` The best email for support requests.
 
-#### Suggested fields for asset issuers:
+#### Suggested fields for asset issuers: {#suggested-fields-for-asset-issuers-1}
 
 - `ORG_GITHUB` Your organization's official Github account.
 - `ORG_KEYBASE` Your organization's official Keybase account. Your Keybase account should contain proof of ownership of any public online accounts you list here, including your organization's domain.
@@ -78,7 +78,7 @@ Issuers that list verified information including phone/address attestations and
 
 Information about the primary point(s) of contact for your organization goes into a TOML [array of tables](https://github.com/toml-lang/toml#array-of-tables) called `[[PRINCIPALS]]`. You need to put contact information for at least one person in your organization. If you don't, exchanges can't verify your offering, and it is unlikely that buyers will be interested. Multiple principals can be added with additional `[[PRINCIPALS]]` entries.
 
-#### Required field for all asset issuers:
+#### Required field for all asset issuers: {#required-field-for-all-asset-issuers-1}
 
 - `name` The name of the primary contact.
 - `email` The primary contact's official email address. This should be hosted at the same domain as your organization's official website.
@@ -156,9 +156,9 @@ server {
 
 ## Sample code to set the home domain of your issuing account
 
-<CodeExample title="Set Home Domain">
+<CodeGroup>
 
-```js
+```js JavaScript
 var StellarSdk = require("@stellar/stellar-sdk");
 var server = new StellarSdk.Horizon.Server(
   "https://horizon-testnet.stellar.org",
@@ -193,7 +193,7 @@ server
   });
 ```
 
-```python
+```python Python
 from stellar_sdk import Keypair, Network, Server, TransactionBuilder
 from stellar_sdk.exceptions import BaseHorizonError
 
@@ -231,7 +231,7 @@ except BaseHorizonError as e:
   print(f"Error: {e}")
 ```
 
-```java
+```java Java
 Server server = new Server("https://horizon-testnet.stellar.org");
 
 // Keys for issuing account
@@ -249,7 +249,7 @@ setHomeDomain.sign(issuingKeys);
 server.submitTransaction(setHomeDomain);
 ```
 
-```go
+```go Go
 func main() {
 	client := horizonclient.DefaultTestNetClient
 
@@ -292,13 +292,13 @@ func main() {
 }
 ```
 
-</CodeExample>
+</CodeGroup>
 
-## Sample `stellar.toml`
+## Sample `stellar.toml` {#sample-stellartoml}
 
-<CodeExample>
+<CodeGroup>
 
-```toml
+```toml TOML
 NETWORK_PASSPHRASE="Public Global Stellar Network ; September 2015"
 FEDERATION_SERVER="https://api.domain.com/federation"
 AUTH_SERVER="https://api.domain.com/auth"
@@ -363,7 +363,7 @@ image="https://static.thenounproject.com/png/2292360-200.png"
 fixed_number=10000
 ```
 
-</CodeExample>
+</CodeGroup>
 
 [sep-0001]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md
 [sep-0020]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0020.md
diff --git a/docs/tokens/quickstart.mdx b/docs/tokens/quickstart.mdx
index 65f387766..2bf092991 100644
--- a/docs/tokens/quickstart.mdx
+++ b/docs/tokens/quickstart.mdx
@@ -1,13 +1,13 @@
 ---
-sidebar_position: 30
 title: Quickstart
+description: "Issue your first asset on the Stellar network in one, single transaction!"
 ---
 
 Issue your first asset on the Stellar network in **one, single transaction**!
 
-<CodeExample>
+<CodeGroup>
 
-```js
+```js JavaScript
 import {
   Keypair,
   Horizon,
@@ -63,7 +63,7 @@ const res = await server.submitTransaction(transaction);
 console.log(`transaction hash:\n${res.hash}`);
 ```
 
-```python
+```python Python
 import requests
 from stellar_sdk import Asset, Keypair, Network, Server, TransactionBuilder
 
@@ -109,4 +109,4 @@ res = server.submit_transaction(transaction)
 print(f"Transaction hash:\n{res['hash']}")
 ```
 
-</CodeExample>
+</CodeGroup>
diff --git a/docs/tokens/stellar-asset-contract.mdx b/docs/tokens/stellar-asset-contract.mdx
index cdbdb2117..cc1acec96 100644
--- a/docs/tokens/stellar-asset-contract.mdx
+++ b/docs/tokens/stellar-asset-contract.mdx
@@ -1,29 +1,28 @@
 ---
-sidebar_position: 50
 title: "Use Issued Assets in Smart Contracts with the Stellar Asset Contract (SAC)"
+sidebarTitle: Stellar Asset Contract
 description: "Learn to make payments and interact with assets issued on the Stellar network in smart contracts using the Stellar Asset Contract (SAC), a built-in contract."
-sidebar_label: Stellar Asset Contract
 ---
 
-:::info
+<Info>
 
 The term "custom token" has been deprecated in favor of "contract token". View the conversation in the [Stellar Developer Discord](https://discord.com/channels/897514728459468821/966788672164855829/1359276952971640953).
 
-:::
+</Info>
 
-# Stellar Asset Contract (SAC)
+## Stellar Asset Contract (SAC)
 
 The Stellar Asset Contract (SAC) is an implementation of [CAP-46-6 Smart Contract Standardized Asset] and [SEP-41 Token Interface] for Stellar [assets].
 
-See examples of how to use the SAC in the [Tokens How-To Guides](../build/guides/tokens/README.mdx).
+See examples of how to use the SAC in the [Tokens How-To Guides](/docs/build/guides/tokens).
 
 ## Overview
 
-:::note
+<Note>
 
-Stellar assets are issued by Stellar accounts. Issue an asset on Stellar by following the [Issue an Asset Tutorial](./how-to-issue-an-asset.mdx).
+Stellar assets are issued by Stellar accounts. Issue an asset on Stellar by following the [Issue an Asset Tutorial](./how-to-issue-an-asset).
 
-:::
+</Note>
 
 The Stellar Asset Contract allows users and contracts to make payments with, and interact with, assets. The SAC can interact with assets held by Stellar accounts or contracts.
 
@@ -51,17 +50,17 @@ Some functionality available on the Stellar network in transaction operations, s
 
 Every Stellar asset on Stellar has reserved a contract address that the Stellar Asset Contract can be deployed to. Anyone can initiate the deploy and the Stellar asset issuer does not need to be involved.
 
-It can be deployed using the [Stellar CLI] as shown [here](../tools/cli/cookbook/deploy-stellar-asset-contract.mdx).
+It can be deployed using the [Stellar CLI] as shown [here](../tools/cli/cookbook/deploy-stellar-asset-contract).
 
-Or the [Stellar SDK] can be used as shown [here](../learn/fundamentals/contract-development/contract-interactions/stellar-transaction.mdx#xdr-usage) by calling `InvokeHostFunctionOp` with `HOST_FUNCTION_TYPE_CREATE_CONTRACT` and a `CONTRACT_ID_PREIMAGE_FROM_ASSET` contract ID preimage. The resulting token will have a deterministic identifier, which will be the sha256 hash of `HashIDPreimage::ENVELOPE_TYPE_CONTRACT_ID` xdr specified [here][contract_id].
+Or the [Stellar SDK] can be used as shown [here](../learn/fundamentals/contract-development/contract-interactions/stellar-transaction#xdr-usage) by calling `InvokeHostFunctionOp` with `HOST_FUNCTION_TYPE_CREATE_CONTRACT` and a `CONTRACT_ID_PREIMAGE_FROM_ASSET` contract ID preimage. The resulting token will have a deterministic identifier, which will be the sha256 hash of `HashIDPreimage::ENVELOPE_TYPE_CONTRACT_ID` xdr specified [here][contract_id].
 
 Anyone can deploy the instances of Stellar Asset Contract. Note, that the initialization of the Stellar Asset Contracts happens automatically during the deployment. The asset issuer becomes the _initial_ administrator once the contract has been deployed; administrative authority is mutable and can be transferred afterwards with the SAC's `set_admin` function.
 
 A deployed SAC can be identified on-chain from its contract instance: its `SCContractInstance.executable` is `CONTRACT_EXECUTABLE_STELLAR_ASSET` rather than a Wasm hash. Once a contract is verified as a SAC this way, its built-in `name()` and `symbol()` methods report the wrapped asset's identity — there is no generic SEP-41 `asset()`/`issuer()` accessor to rely on. Note that a contract-address hash and the current `admin` value are not, by themselves, proof of an asset's provenance: verify the executable first, since the administrator may have been changed via `set_admin`.
 
 [contract_id]: https://github.com/stellar/stellar-xdr/blob/curr/Stellar-transaction.x
-[stellar cli]: ../tools/cli/stellar-cli.mdx
-[stellar sdk]: ../tools/sdks/README.mdx
+[stellar cli]: ../tools/cli/stellar-cli
+[stellar sdk]: /docs/tools/sdks
 
 ## Interacting with classic Stellar assets
 
@@ -69,7 +68,7 @@ The Stellar Asset Contract is the only way for contracts to interact with Stella
 
 The issuer of the asset will be the initial administrator of the deployed contract (administrative authority can later be moved with `set_admin`). Because the Native Stellar token doesn't have an issuer, it will not have an administrator either. It also cannot be burned.
 
-After the contract has been deployed, users can use their classic account (for lumens) or trustline (for other assets) balance. There are some differences depending on if you are using a classic account `Address` vs a contract `Address` (corresponding either to a regular contract or to a custom account contract). The following section references some issuer and trustline flags from Stellar classic, which you can learn more about [here](./control-asset-access.mdx#controlling-access-to-an-asset-with-flags).
+After the contract has been deployed, users can use their classic account (for lumens) or trustline (for other assets) balance. There are some differences depending on if you are using a classic account `Address` vs a contract `Address` (corresponding either to a regular contract or to a custom account contract). The following section references some issuer and trustline flags from Stellar classic, which you can learn more about [here](./control-asset-access#controlling-access-to-an-asset-with-flags).
 
 - Using `Address::Account`
   - The balance must exist in a trustline (or an account for the native balance). This means the contract will not store the balance in ContractData. If the trustline or account is missing, any function that tries to interact with that balance will fail (as of Yardstick, Protocol 26, a contract can create the missing trustline itself by first calling the SAC's [`trust` function](#creating-trustlines-from-a-contract)).
@@ -81,11 +80,11 @@ After the contract has been deployed, users can use their classic account (for l
 - Using `Address::Contract`
   - The balance and authorization state will be stored in contract storage, as opposed to a trustline.
   - Balances are stored in a 128-bit signed integer.
-  - A balance can only be clawed back if the issuer account had the `AUTH_CLAWBACK_ENABLED_FLAG` set when the balance was created. A balance is created when either an `Address::Contract` is on the receiving end of a successful transfer, or if the admin sets the authorization state. Read more about `AUTH_CLAWBACK_ENABLED_FLAG` [here](./control-asset-access.mdx#clawback-enabled-0x8).
+  - A balance can only be clawed back if the issuer account had the `AUTH_CLAWBACK_ENABLED_FLAG` set when the balance was created. A balance is created when either an `Address::Contract` is on the receiving end of a successful transfer, or if the admin sets the authorization state. Read more about `AUTH_CLAWBACK_ENABLED_FLAG` [here](./control-asset-access#clawback-enabled-0x8).
 
 ### Balance Authorization Required
 
-In the `Address::Contract` case, if the issuer has `AUTH_REQUIRED_FLAG` set, then the specified `Address::Contract` will need to be explicitly authorized with `set_auth` before it can receive a balance. This logic lines up with how trustlines interact with the `AUTH_REQUIRED_FLAG` issuer flag, allowing asset issuers to have the same control in Soroban as they do in Stellar classic. Read more about `AUTH_REQUIRED_FLAG` [here](./control-asset-access.mdx#authorization-required-0x1).
+In the `Address::Contract` case, if the issuer has `AUTH_REQUIRED_FLAG` set, then the specified `Address::Contract` will need to be explicitly authorized with `set_auth` before it can receive a balance. This logic lines up with how trustlines interact with the `AUTH_REQUIRED_FLAG` issuer flag, allowing asset issuers to have the same control in Soroban as they do in Stellar classic. Read more about `AUTH_REQUIRED_FLAG` [here](./control-asset-access#authorization-required-0x1).
 
 ### Revoking Authorization
 
@@ -95,17 +94,17 @@ The admin can only revoke authorization from an `Address`, if the issuer of the
 
 As of Yardstick, Protocol 26 ([CAP-73]), the SAC's `trust` function allows a contract to create an asset's trustline for a `G...` address as part of a contract invocation. Before Yardstick, Protocol 26, a missing trustline could only be created with a separate `changeTrust` operation, so any contract function touching a trustline balance would fail until the account holder set up the trustline in a separate transaction.
 
-The `trust` function is useful any time a contract distributes an asset to accounts that may not hold it yet: for example, an airdrop or payout contract calling `trust` before `mint` or `transfer`, or bridging and chain abstraction flows that deliver assets to freshly created accounts. See [setting a custom SAC admin](../build/guides/tokens/custom-sac-admin.mdx) for a worked example of a contract calling `trust` before minting to a recipient.
+The `trust` function is useful any time a contract distributes an asset to accounts that may not hold it yet: for example, an airdrop or payout contract calling `trust` before `mint` or `transfer`, or bridging and chain abstraction flows that deliver assets to freshly created accounts. See [setting a custom SAC admin](../build/guides/tokens/custom-sac-admin) for a worked example of a contract calling `trust` before minting to a recipient.
 
 A few things to keep in mind:
 
 - The call is a no-op if `addr` is a contract address, or if the trustline already exists, so it's safe to call unconditionally before a transfer or mint.
 - When a trustline is actually created, the SAC requires authorization from `addr`, preserving the opt-in nature of trustlines.
-- The account holding the new trustline must satisfy the network's [base reserve](../learn/fundamentals/lumens.mdx#base-reserves) requirement for the additional ledger entry.
+- The account holding the new trustline must satisfy the network's [base reserve](../learn/fundamentals/lumens#base-reserves) requirement for the additional ledger entry.
 
 ### Sending to a muxed address
 
-As of Whisk, Protocol 23 ([CAP-67]), the `to` argument of the SAC's `transfer` function is a `MuxedAddress` rather than an `Address`. A `MuxedAddress` is either a plain address or an `M...` [muxed account](../build/guides/transactions/pooled-accounts-muxed-accounts-memos.mdx) address, which pairs a `G...` account with a 64-bit multiplexing id. This is how a contract payment identifies one user of a pooled account, the way a memo does for a classic payment: a transaction that invokes a contract must set `MEMO_NONE`, so before Whisk there was no way to tag a SAC payment at all.
+As of Whisk, Protocol 23 ([CAP-67]), the `to` argument of the SAC's `transfer` function is a `MuxedAddress` rather than an `Address`. A `MuxedAddress` is either a plain address or an `M...` [muxed account](../build/guides/transactions/pooled-accounts-muxed-accounts-memos) address, which pairs a `G...` account with a 64-bit multiplexing id. This is how a contract payment identifies one user of a pooled account, the way a memo does for a classic payment: a transaction that invokes a contract must set `MEMO_NONE`, so before Whisk there was no way to tag a SAC payment at all.
 
 `transfer` is the only SAC function that accepts a `MuxedAddress`. `approve`, `balance`, `transfer_from`, `burn`, `burn_from`, `mint`, `clawback`, `set_authorized` and `trust` all still take an `Address`.
 
@@ -113,7 +112,7 @@ The multiplexing id changes nothing on the ledger. The SAC strips the id off the
 
 - The trustline rules for `Address::Account` are unchanged: the underlying `G...` account still needs an authorized trustline for the asset, or the transfer fails.
 - The `to` topic of the emitted event is the underlying address, never the muxed address. The id travels in the event `data` instead. Only a call that passes a muxed address makes `data` a map, `{ amount: i128, to_muxed_id: u64 }`; a call that passes a plain address keeps the plain `amount: i128`.
-- When one side of the transfer is the asset issuer, the SAC emits `mint` or `burn` rather than `transfer`. The `mint` event keeps the id; the `burn` event drops it. See [Events: SEP-41 Tokens vs. Stellar Asset Contracts](./token-interface.mdx#events-sep-41-tokens-vs-stellar-asset-contracts).
+- When one side of the transfer is the asset issuer, the SAC emits `mint` or `burn` rather than `transfer`. The `mint` event keeps the id; the `burn` event drops it. See [Events: SEP-41 Tokens vs. Stellar Asset Contracts](./token-interface#events-sep-41-tokens-vs-stellar-asset-contracts).
 
 A muxed address is not interchangeable with an address everywhere:
 
@@ -123,13 +122,13 @@ A muxed address is not interchangeable with an address everywhere:
 
 Both parts are readable from the contract. In the Rust SDK, `MuxedAddress::address()` returns the address part, and `MuxedAddress::id()` returns `Some(id)` for a muxed address and `None` for a plain one. On the client side, the JavaScript SDK builds the argument from the strkey with `new Address('M...').toScVal()`.
 
-See [Send to and receive payments from Contract Accounts](../build/guides/transactions/send-and-receive-c-accounts.mdx) for a worked flow, including how the muxed id appears in Horizon and RPC responses.
+See [Send to and receive payments from Contract Accounts](../build/guides/transactions/send-and-receive-c-accounts) for a worked flow, including how the muxed id appears in Horizon and RPC responses.
 
 ## Authorization semantics
 
-See the [authorization overview](../learn/fundamentals/contract-development/authorization.mdx) and [auth example](../build/smart-contracts/example-contracts/auth.mdx) for general information about authorization in Soroban.
+See the [authorization overview](../learn/fundamentals/contract-development/authorization) and [auth example](../build/smart-contracts/example-contracts/auth) for general information about authorization in Soroban.
 
-The token contract contains three kinds of operations that follow the token [interface](./token-interface.mdx#code):
+The token contract contains three kinds of operations that follow the token [interface](./token-interface#code):
 
 - getters, such as `balance`, which do not change the state of the contract
 - unprivileged mutators, such as `incr_allow` and `xfer`, which change the state of the contract but do not require special privileges
@@ -301,13 +300,13 @@ pub(crate) enum ContractError {
 
 Source: https://github.com/stellar/rs-soroban-env/blob/main/soroban-env-host/src/builtin_contracts/contract_error.rs
 
-[assets]: ../learn/fundamentals/stellar-data-structures/assets.mdx
+[assets]: ../learn/fundamentals/stellar-data-structures/assets
 [`token` module]: https://docs.rs/soroban-sdk/latest/soroban_sdk/token/index.html
 [`TokenInterface` trait]: https://docs.rs/soroban-sdk/latest/soroban_sdk/token/trait.TokenInterface.html
 [`TokenClient` struct]: https://docs.rs/soroban-sdk/latest/soroban_sdk/token/struct.TokenClient.html
 [`StellarAssetInterface` trait]: https://docs.rs/soroban-sdk/latest/soroban_sdk/token/trait.StellarAssetInterface.html
 [`StellarAssetClient` struct]: https://docs.rs/soroban-sdk/latest/soroban_sdk/token/struct.StellarAssetClient.html
 [cap-46-6 smart contract standardized asset]: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0046-06.md
-[sep-41 token interface]: ./token-interface.mdx
+[sep-41 token interface]: ./token-interface
 [CAP-67]: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md
 [CAP-73]: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0073.md
diff --git a/docs/tokens/token-interface.mdx b/docs/tokens/token-interface.mdx
index fd1bb3882..b039c8735 100644
--- a/docs/tokens/token-interface.mdx
+++ b/docs/tokens/token-interface.mdx
@@ -1,17 +1,16 @@
 ---
-sidebar_position: 60
 title: "Create Contract Tokens on Stellar: Standards & Integration"
+sidebarTitle: Token Interface
 description: "Learn about and create contract tokens on the Stellar network. Learn about the standards, functionality, and integration of contract tokens."
-sidebar_label: Token Interface
 ---
 
-:::info
+<Info>
 
 The term "custom token" has been deprecated in favor of "contract token". View the conversation in the [Stellar Developer Discord](https://discord.com/channels/897514728459468821/966788672164855829/1359276952971640953).
 
-:::
+</Info>
 
-# Token Interface
+## Token Interface
 
 Token contracts, including the Stellar Asset Contract and example token implementations expose the following common interface.
 
@@ -29,9 +28,9 @@ For any given contract function, there are three requirements that should be con
 
 ### Code
 
-The interface below uses the Rust [soroban-sdk](../tools/sdks/contract-sdks.mdx#soroban-rust-sdk) to declare a trait that complies with the [SEP-41](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0041.md) token interface.
+The interface below uses the Rust [soroban-sdk](../tools/sdks/contract-sdks#soroban-rust-sdk) to declare a trait that complies with the [SEP-41](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0041.md) token interface.
 
-The `to` argument of `transfer` is a `MuxedAddress`, which accepts either a plain address or an `M...` muxed account address. See [sending to a muxed address](./stellar-asset-contract.mdx#sending-to-a-muxed-address) for what the id does and where it is not accepted.
+The `to` argument of `transfer` is a `MuxedAddress`, which accepts either a plain address or an `M...` muxed account address. See [sending to a muxed address](./stellar-asset-contract#sending-to-a-muxed-address) for what the id does and where it is not accepted.
 
 ```rust
 pub trait TokenInterface {
@@ -188,15 +187,17 @@ pub trait TokenInterface {
 }
 ```
 
-:::caution[CAUTION WHEN MODIFYING ALLOWANCES]
+<Warning>
+
+**CAUTION WHEN MODIFYING ALLOWANCES**
 
 The `approve` function overwrites the previous value with `amount`, so it is possible for the previous allowance to be spent in an earlier transaction before `amount` is written in a later transaction. The result of this is that `spender` can spend more than intended. This issue can be avoided by first setting the allowance to 0, verifying that the spender didn't spend any portion of the previous allowance, and then setting the allowance to the new desired amount. You can read more about this issue here - https://github.com/ethereum/EIPs/issues/20#issuecomment-263524729.
 
-:::
+</Warning>
 
 ### Events: SEP-41 Tokens vs. Stellar Asset Contracts
 
-The event shapes in the interface above are the ones a SEP-41 contract token emits. A [Stellar Asset Contract](./stellar-asset-contract.mdx) — the built-in contract every Stellar asset has — emits the same event names with **one extra topic**: the asset's [SEP-11](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0011.md) identifier, always last.
+The event shapes in the interface above are the ones a SEP-41 contract token emits. A [Stellar Asset Contract](./stellar-asset-contract) — the built-in contract every Stellar asset has — emits the same event names with **one extra topic**: the asset's [SEP-11](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0011.md) identifier, always last.
 
 Code written against the shapes above will therefore mis-parse an event emitted by a Stellar Asset Contract, reading the asset identifier as a missing field or ignoring it entirely.
 
@@ -212,25 +213,27 @@ Code written against the shapes above will therefore mis-parse an event emitted
 | `set_authorized` | not part of this interface | `["set_authorized", id, sep0011_asset]` |
 | `set_admin` | not part of this interface | `["set_admin", admin, sep0011_asset]` |
 
-On the Stellar Asset Contract side, the extra topic does not change the data payload: `amount: i128` for `transfer`, `mint`, `burn`, and `clawback`; `[amount: i128, live_until_ledger: u32]` for `approve`; `authorize: bool` for `set_authorized`; and `new_admin: Address` for `set_admin`. When the destination of a Stellar Asset Contract `transfer` or `mint` carries a multiplexing id, the data becomes `{ amount: i128, to_muxed_id }: Map` instead — see [Monitoring Payments as event stream](../build/guides/transactions/send-and-receive-payments.mdx#monitoring-payments-as-event-stream) for a worked example.
+On the Stellar Asset Contract side, the extra topic does not change the data payload: `amount: i128` for `transfer`, `mint`, `burn`, and `clawback`; `[amount: i128, live_until_ledger: u32]` for `approve`; `authorize: bool` for `set_authorized`; and `new_admin: Address` for `set_admin`. When the destination of a Stellar Asset Contract `transfer` or `mint` carries a multiplexing id, the data becomes `{ amount: i128, to_muxed_id }: Map` instead — see [Monitoring Payments as event stream](../build/guides/transactions/send-and-receive-payments#monitoring-payments-as-event-stream) for a worked example.
 
 A SEP-41 contract token keeps whatever payload the interface above documents for it, so do not carry these payload shapes back across the table.
 
-:::caution[A Stellar Asset Contract transfer does not always emit a transfer event]
+<Warning>
+
+**A Stellar Asset Contract transfer does not always emit a transfer event**
 
-When the asset issuer is one side of the transfer, the contract emits a different event: `mint` if `from` is the issuer, `burn` if `to` is the issuer — and the `burn` drops any multiplexing id. You only get a `transfer` event when neither side is the issuer, or when both are. See [Interacting with classic Stellar assets](./stellar-asset-contract.mdx#interacting-with-classic-stellar-assets).
+When the asset issuer is one side of the transfer, the contract emits a different event: `mint` if `from` is the issuer, `burn` if `to` is the issuer — and the `burn` drops any multiplexing id. You only get a `transfer` event when neither side is the issuer, or when both are. See [Interacting with classic Stellar assets](./stellar-asset-contract#interacting-with-classic-stellar-assets).
 
-:::
+</Warning>
 
 #### Telling a classic operation from a contract invocation
 
-Since protocol 23, classic operations emit these same events, published under the asset's Stellar Asset Contract address whether or not that contract has been deployed — see [Tracking the movement of value](../learn/fundamentals/stellar-data-structures/events.mdx#tracking-the-movement-of-value).
+Since protocol 23, classic operations emit these same events, published under the asset's Stellar Asset Contract address whether or not that contract has been deployed — see [Tracking the movement of value](../learn/fundamentals/stellar-data-structures/events#tracking-the-movement-of-value).
 
 Not all of them, though. `approve` and `set_admin` are never emitted by a classic operation, because no classic operation is equivalent to them: allowances and contract administration exist only on the contract side. So those two always come from a contract invocation, and the rest — `transfer`, `mint`, `burn`, `clawback`, and `set_authorized` — can come from either path.
 
 The two paths produce byte-identical events, so nothing inside an event distinguishes them. To tell them apart, join the event back to its operation using `txHash` and `operationIndex`, then read the operation's type. Note that this separates a classic operation from a contract invocation, not a direct call to the asset contract from one made by another contract on a user's behalf — both of those are `InvokeHostFunction` operations emitting the same event.
 
-If you would rather not do that join yourself, the [Token Transfer Processor](../data/indexers/build-your-own/processors/token-transfer-processor/README.mdx) normalizes both paths into a single stream of typed events.
+If you would rather not do that join yourself, the [Token Transfer Processor](/docs/data/indexers/build-your-own/processors/token-transfer-processor) normalizes both paths into a single stream of typed events.
 
 One event in the unified set has no counterpart here: `fee` is transaction-level, carries only two topics and no asset identifier, and is never emitted by a contract function.
 
@@ -246,7 +249,7 @@ Its important to note the that the token interface not only incorporates the aut
 
 To provide more context, when you use the token interface, there is a function called `authorized` that returns "true" if an address has token authorization.
 
-More details on Authorization can be found [here](../learn/fundamentals/contract-development/authorization.mdx).
+More details on Authorization can be found [here](../learn/fundamentals/contract-development/authorization).
 
 For the functions in the token interface, [trapping](https://doc.rust-lang.org/book/ch09-00-error-handling.html) should be used as the standard way to handle failure conditions since the interface is not designed to return error codes. This means that when a function encounters an error, it will halt execution and revert any state changes that occurred during the function call.
 
diff --git a/docs/tokens/usdt0-layerzero.mdx b/docs/tokens/usdt0-layerzero.mdx
index 315caf1fb..e8c3974c8 100644
--- a/docs/tokens/usdt0-layerzero.mdx
+++ b/docs/tokens/usdt0-layerzero.mdx
@@ -1,19 +1,17 @@
 ---
-sidebar_position: 100
 title: "USDT0 Transfers with LayerZero"
-sidebar_label: USDT0 Transfers with LayerZero
 description: "Use USDT0, Tether's USDT delivered over LayerZero's OFT standard, on Stellar. Mainnet addresses, how LayerZero fits, integration pointers, and amount precision."
 ---
 
-# USDT0 Transfers with LayerZero
-
 [USDT0](https://usdt0.to) brings Tether's USDT to other chains over LayerZero's [Omnichain Fungible Token (OFT) standard](https://docs.layerzero.network/v2/concepts/applications/oft-standard). USDT is locked in an adapter contract on Ethereum, and the same amount of USDT0 is minted on the destination chain. Sending USDT0 out of a chain burns it there and unlocks or mints it on the destination, so total supply stays constant across chains.
 
-On Stellar, USDT0 is a **classic asset with a SAC**. Classic flows use a trustline plus a payment. Soroban contracts call the SAC. See the [tokenization model comparison](./anatomy-of-an-asset.mdx#tokenization-model-comparison) for what that implies.
+On Stellar, USDT0 is a **classic asset with a SAC**. Classic flows use a trustline plus a payment. Soroban contracts call the SAC. See the [tokenization model comparison](./anatomy-of-an-asset#tokenization-model-comparison) for what that implies.
+
+For an overview of what USDT0 unlocks on Stellar, the partners supporting it today, and a deployment checklist, see the [USDT0 on Stellar launch guide](/launch/usdt0).
 
-For an overview of what USDT0 unlocks on Stellar, the partners supporting it today, and a deployment checklist, see the [USDT0 on Stellar launch guide](pathname:///launch/usdt0).
+<Info>
 
-:::info[Full documentation]
+**Full documentation**
 
 For the architecture, the OFT interface, supported chains, and the transfer UI:
 
@@ -21,7 +19,7 @@ For the architecture, the OFT interface, supported chains, and the transfer UI:
 - [USDT0 contract deployments](https://docs.usdt0.to/technical-documentation/deployments)
 - [How to transfer USDT0](https://docs.usdt0.to/tutorial/how-to-transfer) and the [transfer UI](https://usdt0.to/transfer)
 
-:::
+</Info>
 
 ## Mainnet addresses
 
@@ -57,8 +55,8 @@ Transfer time depends on the source chain's finality and on DVN verification, no
 
 USDT0 needs no special integration code on Stellar. Use the same paths as for any other Stellar asset with a SAC:
 
-- **Classic accounts and wallets.** The recipient opens a trustline to `USDT0:GATISXX6BZ6NC7IKQBY37CJD4SOZL3CYZJWXEDG6JVIY4WBS6KXJHN6Q` once. After that, any account holding USDT0 can send it to the recipient with a payment operation. See [Send and Receive Payments](../build/guides/transactions/send-and-receive-payments.mdx) and [Verify Trustlines](../build/guides/basics/verify-trustlines.mdx).
-- **Smart contracts.** Call the SAC at `CBSJZEIO5C7KC2SF3MKSNXXJSW5G3VTNBX4ATMKUI3B2MR4JKM4R26YF` through the [token interface](./token-interface.mdx), the same way as any other token. See [Use Issued Assets in Smart Contracts with the SAC](./stellar-asset-contract.mdx). A contract balance in USDT0 lives in the SAC storage entries, separate from account trustlines.
+- **Classic accounts and wallets.** The recipient opens a trustline to `USDT0:GATISXX6BZ6NC7IKQBY37CJD4SOZL3CYZJWXEDG6JVIY4WBS6KXJHN6Q` once. After that, any account holding USDT0 can send it to the recipient with a payment operation. See [Send and Receive Payments](../build/guides/transactions/send-and-receive-payments) and [Verify Trustlines](../build/guides/basics/verify-trustlines).
+- **Smart contracts.** Call the SAC at `CBSJZEIO5C7KC2SF3MKSNXXJSW5G3VTNBX4ATMKUI3B2MR4JKM4R26YF` through the [token interface](./token-interface), the same way as any other token. See [Use Issued Assets in Smart Contracts with the SAC](./stellar-asset-contract). A contract balance in USDT0 lives in the SAC storage entries, separate from account trustlines.
 - **Bridging in or out.** End users move USDT0 with the [transfer UI](https://usdt0.to/transfer). Programmatic sends from Stellar go through the OFT contract's `quote_send` and `send` functions, with fees paid in XLM. The [USDT0 developer guide](https://docs.usdt0.to/technical-documentation/developer) documents the OFT interface and the message flow. Query `quote_send` for the current fee rather than relying on a documented number.
 
 ### Amount precision
diff --git a/docs/tools/README.mdx b/docs/tools/README.mdx
deleted file mode 100644
index 86243e6cf..000000000
--- a/docs/tools/README.mdx
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: "Blockchain Development Tools: SDKs, APIs & Utilities for Building"
-sidebar_position: 0
-sidebar_label: Tools Overview
-description: "Explore tools for building, testing, and deploying blockchain applications. Access SDKs, APIs, and utilities to streamline development on the Stellar network."
----
-
-# Tools Overview
-
-This section of the docs will provide links to the SDKs and developer tools for use when developing on Stellar as well as documentation for various SDF-maintained platforms such as the Anchor Platform and Stellar Disbursement Platform (SDP).
-
-## Developer Tools
-
-### [SDKs](./sdks/README.mdx)
-
-Stellar’s Software Development Kits (SDKs) provide devs with the tools, libraries, and documentation to interact with and develop on the blockchain. They simplify tasks such as creating and deploying smart contracts and sending transactions while also offering APIs to access data and integrate functionalities into applications.
-
-### [Stellar CLI](./cli/README.mdx)
-
-The command line interface to Soroban smart contracts. It allows you to build, deploy, and interact with smart contracts; configure identities; generate key pairs; manage networks; and more.
-
-### [Lab](./lab/README.mdx)
-
-Stellar Lab is our new go-to tool for development, experimenting, and testing, as well as exploring APIs developers use to interact with the Stellar network.
-
-### [Quickstart](./quickstart/README.mdx)
-
-Quickstart is a local Stellar network environment (node) that allows developers to run a local version of the Stellar network for development and testing.
-
-### [OpenZeppelin Relayer](./openzeppelin-relayer.mdx)
-
-OpenZeppelin Relayer is an open source framework for submitting Stellar transactions. Its Channels plugin adds parallel submission and automatic fee bumping. You can run both yourself, or you can use [Stellar Channels](https://docs.openzeppelin.com/relayer/guides/stellar-channels-guide), the managed service OpenZeppelin operates on top of them, where OpenZeppelin runs the pool of channel accounts and covers the fees under a fair use policy.
-
-### [OpenZeppelin Contracts](./openzeppelin-contracts.mdx)
-
-OpenZeppelin Stellar Contracts is a collection of audited contracts and utilities for Stellar. The contracts are developed by OpenZeppelin in collaboration with the Stellar community and the Stellar Development Foundation (SDF), in an effort to bring a library of high-quality and audited contracts that can be used to build applications on the Stellar network.
-
-### [Scaffold Stellar](./scaffold-stellar.mdx)
-
-Scaffold Stellar is a developer toolkit for building decentralized applications (dApps) and smart contracts on Stellar. It provides CLI tools, reusable contract templates, a smart contract registry, and a modern frontend.
-
-### [More Developer Tools](./developer-tools/README.mdx)
-
-Find other SDF and ecosystem-maintained developer tools that help streamline the development process for applications and smart contracts on Stellar.
-
-## SDF Platforms
-
-### [Anchor Platform](../platforms/anchor-platform/README.mdx)
-
-The Anchor Platform is a set of tools and APIs that enable developers and businesses to build their own on and off-ramp services for the Stellar network. It provides a standardized interface, including the implementation of several Stellar Ecosystem Proposals (SEPs), to make it easy for businesses to integrate with Stellar-based wallets and exchanges.
-
-### [Stellar Disbursement Platform (SDP)](../platforms/stellar-disbursement-platform/README.mdx)
-
-The Stellar Disbursement Platform (SDP) is a tool built for organizations to make bulk payments to a group of recipients over the Stellar network.
diff --git a/docs/tools/cli/README.mdx b/docs/tools/cli/README.mdx
deleted file mode 100644
index 9cb008257..000000000
--- a/docs/tools/cli/README.mdx
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: Stellar CLI
-description: The CLI for interacting with the Stellar network
-sidebar_position: 20
----
-
-# Stellar CLI
-
-The command line interface to Soroban smart contracts. It allows you to build, deploy, and interact with smart contracts; configure identities; generate key pairs; manage networks; and more.
-
-## Install
-
-Install the latest release on macOS, Linux or WSL with the install script:
-
-```sh
-curl -fsSL https://github.com/stellar/stellar-cli/raw/main/install.sh | sh
-```
-
-For Homebrew, winget, cargo, GitHub Actions and shell autocomplete, see [Install the CLI](./install-cli.mdx). To install the CLI with Rust, the Wasm target and an editor, see [Setup](../../build/smart-contracts/getting-started/setup.mdx#install-the-stellar-cli).
-
-## Learn more
-
-- [Stellar CLI Guides](./cookbook/README.mdx) gives examples of how to use the CLI.
-- [Stellar CLI Manual](./stellar-cli.mdx) is the auto-generated reference for every command.
diff --git a/docs/tools/cli/_category_.json b/docs/tools/cli/_category_.json
deleted file mode 100644
index 0d4475828..000000000
--- a/docs/tools/cli/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": false
-}
diff --git a/docs/tools/cli/agent-cli/README.mdx b/docs/tools/cli/agent-cli/README.mdx
deleted file mode 100644
index b7f64d88d..000000000
--- a/docs/tools/cli/agent-cli/README.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: Stellar CLI for Agents
-sidebar_label: Stellar CLI for Agents
-sidebar_position: 15
-description: Use the Stellar CLI and CLI Skills to give your AI agents an agent-friendly wallet and native way to inspect, move, and manage assets on Stellar.
----
-
-Use the Stellar CLI and CLI Skills to give your AI agents an agent-friendly wallet and native way to inspect, move, and manage assets on Stellar. After following the [Quickstart](./quickstart.mdx) to onboard your agent, you can use natural language to prompt your agent to use the Stellar CLI.
-
-Verified against `stellar-cli` 28.1.0.
-
-| What You Ask Your Agent | What Your Agent Executes | How It Works Under the Hood |
-| --- | --- | --- |
-| **"Learn how to use the Stellar CLI"** | `stellar skill` | Dumps structured CLI conventions directly into the agent’s prompt/context window. |
-| **"How much USDC is in alice's account?"** | `stellar token balance` | Reads the balance in smallest units, or as a decimal with `--decimal`. No key setup needed. |
-| **"Send 20 USDC to `G...`"** | `stellar token transfer` | Executes an onchain transfer and returns the transaction hash. |
-| **"Limit agent spending to 50 USDC"** | `stellar token approve` | Grants a capped, time-bound allowance enforced directly onchain by the Stellar network. |
-| **"Draft a payment for my review"** | `stellar tx new payment --build-only` | Builds an unsubmitted transaction payload to a file for human sign-off or air-gapped execution. |
-
-## Agent Ergonomics
-
-Browser wallets are hard for agents. The CLI provides four key agent primitive enhancements:
-
-- **Unified Asset Resolution:** Interacts with native XLM, SAC (Stellar Asset Contracts), or SEP-41 tokens using consistent identifiers (`CODE:ISSUER`, contract ID, or custom alias).
-- **Self-Scaffolding Context:** Running `stellar contract init` automatically generates an `AGENTS.md` guide in local project directories, giving LLMs instant awareness of local commands and tool rules. [Build and deploy a contract](./guides/build-and-deploy-contracts.mdx#the-generated-agentsmd) covers what it contains and how to customize it.
-- **Structured JSON Outputs (`--output json`):** The `stellar token` commands return typed JSON, including transaction hashes and a typed error envelope. Coverage elsewhere varies, and `tx send` and `tx new` have no `--output` flag. [Output and errors](./reference/output-and-errors.mdx) lists what each command supports.
-- **Onchain Diagnostic Errors:** When a transaction reverts, the CLI returns the contract's diagnostic event trail inside the error envelope. Agents can read _why_ a transaction failed.
-
-## Capability Surface
-
-Beyond only using the Stellar CLI as a wallet, your agent can also use the full power of CLI to interact with, build, and deploy contracts. Humans can read the full [Stellar CLI Manual](../stellar-cli.mdx).
-
-| Functional Area | What Your Agent Can Do | CLI Commands |
-| --- | --- | --- |
-| **System & Agent Context** | Check environment health and load usage rules into LLM context windows. | `stellar doctor`<br />`stellar skill` |
-| **Balances & Metadata** | Read token holdings, inspect token names, symbols, and decimal precision. | `stellar token balance`<br />`stellar token decimals / name / symbol` |
-| **Transfers & Payments** | Move tokens and get back the transaction hash, as a bare line by default or as JSON with `--output json`. | `stellar token transfer` |
-| **Spending Limits** | Set spending limits and audit active delegate approvals. | `stellar token approve`<br />`stellar token allowance` |
-| **Transactions & Contracts** | Build raw operations, deploy Soroban contracts, and invoke custom smart contracts. | `stellar tx new <OP>`<br />`stellar contract deploy / invoke` |
-| **Safe Offline Operations** | Draft unsigned transactions for human-in-the-loop approval workflows. | `stellar tx new <OP> --build-only` |
-
-## Safety Architecture
-
-Giving an agent financial execution power requires hard guardrails. The first two below are enforced by the network or by a human signer, not by the agent following instructions. The third is a convention your agent has to follow:
-
-1. **Protocol Allowance Enforcement:** Primary funds remain in your treasury account. Issue your agent a capped allowance using `stellar token approve`. If the agent attempts to overspend, the Stellar ledger rejects the transaction.
-2. **Human Approval Workflows:** Use `--build-only` flags on sensitive transactions. Your agent formats the payload into a file, leaving final signing authority to a human or air-gapped machine.
-3. **Explicit Smallest-Unit Amounts:** `token transfer` and `token approve` take `--amount` in the token's smallest unit and do no conversion. Read `stellar token decimals` first and have the agent show its arithmetic before it sends.
-
-## Where to go next
-
-- [Skills](skills.mdx) covers `stellar skill`, the built-in guide that teaches your agent the CLI's conventions.
-- [Delegate spending](guides/delegate-spending.mdx) is the page to read before any real money is involved.
-- [Build and deploy a contract](guides/build-and-deploy-contracts.mdx) takes your agent from `stellar contract init` to a deployed contract it can call.
-- [Authority & Security Model](reference/authority-model.mdx) is explicit about what the CLI does not protect you from.
-- [Architecture](reference/architecture.mdx) covers how the read and write paths differ, where state lives, and how to split building, signing, and submitting across machines.
-- [Output and errors](reference/output-and-errors.mdx) covers which commands emit structured JSON your agent can branch on, because the coverage is not uniform.
-- [Troubleshooting](reference/troubleshooting.mdx) for when something does not work.
diff --git a/docs/tools/cli/agent-cli/_category_.json b/docs/tools/cli/agent-cli/_category_.json
deleted file mode 100644
index 9e3a55f45..000000000
--- a/docs/tools/cli/agent-cli/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": true
-}
diff --git a/docs/tools/cli/agent-cli/guides/_category_.json b/docs/tools/cli/agent-cli/guides/_category_.json
deleted file mode 100644
index b2d23ddf6..000000000
--- a/docs/tools/cli/agent-cli/guides/_category_.json
+++ /dev/null
@@ -1 +0,0 @@
-{ "label": "Agent Cookbook", "collapsed": true, "position": 30 }
diff --git a/docs/tools/cli/agent-cli/guides/build-and-deploy-contracts.mdx b/docs/tools/cli/agent-cli/guides/build-and-deploy-contracts.mdx
index d0f296087..b71382dc0 100644
--- a/docs/tools/cli/agent-cli/guides/build-and-deploy-contracts.mdx
+++ b/docs/tools/cli/agent-cli/guides/build-and-deploy-contracts.mdx
@@ -1,6 +1,5 @@
 ---
 title: Build and deploy a contract
-sidebar_position: 80
 description: Have your agent create a contract project with `stellar contract init`, build, deploy, and invoke it, and use the `AGENTS.md` file the project ships with.
 keywords:
   [
@@ -15,8 +14,6 @@ keywords:
   ]
 ---
 
-# Build and deploy a contract
-
 Have your agent create a contract project, build it, deploy it to testnet, and call it. The project comes with an `AGENTS.md` file that tells your agent how to work in it.
 
 ## Ask your agent
@@ -27,7 +24,7 @@ Create a Stellar contract project called my-project, build it, deploy it to test
 
 ## Before you start
 
-- Follow the [Quickstart](../quickstart.mdx) first. `stellar contract init` writes `AGENTS.md` from `stellar-cli` 28.0.0 on.
+- Follow the [Quickstart](/docs/tools/cli/agent-cli/quickstart) first. `stellar contract init` writes `AGENTS.md` from `stellar-cli` 28.0.0 on.
 - Install Rust 1.84 or later and the `wasm32v1-none` target with `rustup target add wasm32v1-none`. Rust 1.82 and 1.83 cannot build contracts.
 - Fund a testnet identity, for example `agent-1` from the Quickstart.
 
@@ -74,7 +71,7 @@ Create a Stellar contract project called my-project, build it, deploy it to test
 
 ## Read stdout, not `--output json`
 
-`contract init`, `contract build`, `contract deploy`, and `contract invoke` have no `--output` flag. [Output and errors](../reference/output-and-errors.mdx) lists the commands that do. Parse these four by stream:
+`contract init`, `contract build`, `contract deploy`, and `contract invoke` have no `--output` flag. [Output and errors](/docs/tools/cli/agent-cli/reference/output-and-errors) lists the commands that do. Parse these four by stream:
 
 | Command | stdout | stderr |
 | --- | --- | --- |
@@ -85,7 +82,7 @@ Create a Stellar contract project called my-project, build it, deploy it to test
 
 Keep the two streams apart. `2>&1` mixes progress lines into the value you parse. A failure prints `❌ error: ...` on stderr and exits non-zero, so check the exit code before you read stdout.
 
-## The generated `AGENTS.md`
+## The generated `AGENTS.md` {#the-generated-agentsmd}
 
 `stellar contract init` writes `AGENTS.md` at the workspace root. It is a short Markdown brief for coding agents. It covers:
 
@@ -98,7 +95,7 @@ Keep the two streams apart. `2>&1` mixes progress lines into the value you parse
 
 The template lives in the CLI source at [`contract-workspace-template/AGENTS.md`](https://github.com/stellar/stellar-cli/blob/v28.1.0/cmd/soroban-cli/src/utils/contract-workspace-template/AGENTS.md).
 
-`AGENTS.md` describes this project. [`stellar skill`](../skills.mdx) describes the CLI itself. Give your agent both.
+`AGENTS.md` describes this project. [`stellar skill`](/docs/tools/cli/agent-cli/skills) describes the CLI itself. Give your agent both.
 
 ### How agents pick it up
 
@@ -114,13 +111,13 @@ The file is a copy made when you ran `init`. It does not change when you upgrade
 - Name the identity and network the agent must use, for example `--source agent-1 --network testnet`.
 - Add your own rules, for example "run `cargo test` before every deploy".
 
-A rule in `AGENTS.md` is an instruction to the agent, not a limit the CLI enforces. To limit what an agent can spend, see [Delegate spending](delegate-spending.mdx).
+A rule in `AGENTS.md` is an instruction to the agent, not a limit the CLI enforces. To limit what an agent can spend, see [Delegate spending](/docs/tools/cli/agent-cli/guides/delegate-spending).
 
 Running `init` again keeps your edits. For example, `stellar contract init . --name increment` adds a contract and skips every file that already exists, `AGENTS.md` included. `--overwrite` replaces every template file, `AGENTS.md` included, so save your changes before you use it.
 
 ## Related pages
 
-- [Skills](../skills.mdx)
-- [Output and errors](../reference/output-and-errors.mdx)
-- [Hello World](../../../../build/smart-contracts/getting-started/hello-world.mdx)
-- [Stellar CLI Manual](../../stellar-cli.mdx)
+- [Skills](/docs/tools/cli/agent-cli/skills)
+- [Output and errors](/docs/tools/cli/agent-cli/reference/output-and-errors)
+- [Hello World](/docs/build/smart-contracts/getting-started/hello-world)
+- [Stellar CLI Manual](/docs/tools/cli/stellar-cli)
diff --git a/docs/tools/cli/agent-cli/guides/build-and-submit-transactions.mdx b/docs/tools/cli/agent-cli/guides/build-and-submit-transactions.mdx
index 08ce4cd45..52f324503 100644
--- a/docs/tools/cli/agent-cli/guides/build-and-submit-transactions.mdx
+++ b/docs/tools/cli/agent-cli/guides/build-and-submit-transactions.mdx
@@ -1,12 +1,9 @@
 ---
 title: Build and submit transactions
-sidebar_position: 50
 description: Build unsigned transactions with `--build-only`, sign and inspect them offline, then submit with `stellar tx`.
 keywords: [Stellar, agent, build-only, tx, sign, simulate, XDR]
 ---
 
-# Build and submit transactions
-
 Build a payment, sign it, and send it as three separate steps, so a person or an offline machine can approve it before anything is signed.
 
 ## Ask your agent
@@ -132,7 +129,7 @@ Elapsed time alone is not the cause: only another transaction from the same sour
 
 ## Related pages
 
-- [Send tokens](send-tokens.mdx)
-- [Delegate spending](delegate-spending.mdx)
-- [Authority model](../reference/authority-model.mdx)
-- [Quickstart](../quickstart.mdx)
+- [Send tokens](/docs/tools/cli/agent-cli/guides/send-tokens)
+- [Delegate spending](/docs/tools/cli/agent-cli/guides/delegate-spending)
+- [Authority model](/docs/tools/cli/agent-cli/reference/authority-model)
+- [Quickstart](/docs/tools/cli/agent-cli/quickstart)
diff --git a/docs/tools/cli/agent-cli/guides/check-balances-and-metadata.mdx b/docs/tools/cli/agent-cli/guides/check-balances-and-metadata.mdx
index 6dac7a3a8..40b8d28ed 100644
--- a/docs/tools/cli/agent-cli/guides/check-balances-and-metadata.mdx
+++ b/docs/tools/cli/agent-cli/guides/check-balances-and-metadata.mdx
@@ -1,12 +1,9 @@
 ---
 title: Check balances and metadata
-sidebar_position: 20
 description: Read balances and token metadata with `stellar token balance`, `name`, `symbol`, and `decimals`, no key required.
 keywords: [Stellar, agent, balance, token metadata, decimals, CLI]
 ---
 
-# Check balances and metadata
-
 Check what an account holds and what a token is before touching it. These are reads, so they need no key, no funded account, and no signing.
 
 ## Ask your agent
@@ -49,7 +46,7 @@ stellar network add mainnet \
   --network-passphrase "Public Global Stellar Network ; September 2015"
 ```
 
-The public `https://mainnet.sorobanrpc.com` needs no signup and is enough for reads. Stellar's [RPC providers page](../../../../data/apis/rpc/providers.mdx) lists others.
+The public `https://mainnet.sorobanrpc.com` needs no signup and is enough for reads. Stellar's [RPC providers page](/docs/data/apis/rpc/providers) lists others.
 
 ## Two output quirks
 
@@ -90,7 +87,7 @@ A balance read against an account that does not exist on the network at all fail
 
 ## Related pages
 
-- [Send tokens](send-tokens.mdx)
-- [Delegate spending](delegate-spending.mdx)
-- [Quickstart](../quickstart.mdx)
-- [Output and errors](../reference/output-and-errors.mdx)
+- [Send tokens](/docs/tools/cli/agent-cli/guides/send-tokens)
+- [Delegate spending](/docs/tools/cli/agent-cli/guides/delegate-spending)
+- [Quickstart](/docs/tools/cli/agent-cli/quickstart)
+- [Output and errors](/docs/tools/cli/agent-cli/reference/output-and-errors)
diff --git a/docs/tools/cli/agent-cli/guides/delegate-spending.mdx b/docs/tools/cli/agent-cli/guides/delegate-spending.mdx
index 80302cefa..1de1592b7 100644
--- a/docs/tools/cli/agent-cli/guides/delegate-spending.mdx
+++ b/docs/tools/cli/agent-cli/guides/delegate-spending.mdx
@@ -1,6 +1,5 @@
 ---
 title: Delegate spending
-sidebar_position: 30
 description: "How much can your agent spend without you, and what is the worst case if it goes wrong. A funded account, an allowance, a co-signed vault, a zero-XLM agent, and a self-expiring grant, compared honestly."
 keywords:
   [
@@ -17,8 +16,6 @@ keywords:
   ]
 ---
 
-# Delegate spending
-
 Let an agent spend some of your money, with a cap and a deadline the network enforces, without ever holding your key.
 
 ## Ask your agent
@@ -28,7 +25,7 @@ Grant agent-1 an allowance of 25 USDC from treasury on testnet USDC, expiring in
 show me the allowance.
 ```
 
-That prompt is [Pattern 2](#pattern-2-an-allowance). `treasury` is the funded account you control, and `agent-1` is your agent's own key from the [Quickstart](../quickstart.mdx). The examples use testnet USDC, `USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5`, which has 7 decimals, so 25 USDC is `250000000`.
+That prompt is [Pattern 2](#pattern-2-an-allowance). `treasury` is the funded account you control, and `agent-1` is your agent's own key from the [Quickstart](/docs/tools/cli/agent-cli/quickstart). The examples use testnet USDC, `USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5`, which has 7 decimals, so 25 USDC is `250000000`.
 
 ## Choose a pattern
 
@@ -259,7 +256,7 @@ Revoke by approving zero: `--amount 0 --expiration-ledger 0`. Zero is the one ca
 
 An agent account that holds no XLM cannot pay a transaction fee, so it cannot submit anything by itself. Create it with sponsored reserves, give it the asset it will spend or an allowance to draw on, and pay each transaction's fee yourself with a fee bump. Stopping the agent means declining to sign the next one.
 
-Generate the agent's key without `--fund`. The sponsorship transaction below is what creates the account, and friendbot funding it first would defeat the point: the agent must hold no XLM. This is the one place where the [Quickstart](../quickstart.mdx)'s `keys generate --fund` is the wrong move.
+Generate the agent's key without `--fund`. The sponsorship transaction below is what creates the account, and friendbot funding it first would defeat the point: the agent must hold no XLM. This is the one place where the [Quickstart](/docs/tools/cli/agent-cli/quickstart)'s `keys generate --fund` is the wrong move.
 
 Create the account with a zero starting balance. The three operations must ride in one transaction, and the sponsored account signs for the `end` operation. `tx op add` does not raise the fee as it adds operations, so set the fee for three operations up front:
 
@@ -411,7 +408,7 @@ Setting `--expiration-ledger` behind the current ledger, with a positive amount,
 
 ## Related pages
 
-- [Send tokens](send-tokens.mdx)
-- [Check balances and metadata](check-balances-and-metadata.mdx)
-- [Authority model](../reference/authority-model.mdx)
-- [Quickstart](../quickstart.mdx)
+- [Send tokens](/docs/tools/cli/agent-cli/guides/send-tokens)
+- [Check balances and metadata](/docs/tools/cli/agent-cli/guides/check-balances-and-metadata)
+- [Authority model](/docs/tools/cli/agent-cli/reference/authority-model)
+- [Quickstart](/docs/tools/cli/agent-cli/quickstart)
diff --git a/docs/tools/cli/agent-cli/guides/pay-for-apis-x402.mdx b/docs/tools/cli/agent-cli/guides/pay-for-apis-x402.mdx
index 04deba8ac..e795fc1bc 100644
--- a/docs/tools/cli/agent-cli/guides/pay-for-apis-x402.mdx
+++ b/docs/tools/cli/agent-cli/guides/pay-for-apis-x402.mdx
@@ -1,12 +1,9 @@
 ---
 title: Pay for APIs with x402
-sidebar_position: 60
 description: Pay for x402-protected APIs on Stellar with USDC, using the stellar CLI only for the identity and the SEP-41 settlement rail.
 keywords: [Stellar, agent, x402, payments, USDC, SEP-41, CLI]
 ---
 
-# Pay for APIs with x402
-
 Pay an x402-protected API in USDC from your agent's code, and confirm the payment settled onchain. The demo below costs 0.01 testnet USDC.
 
 ## Ask your agent
@@ -26,7 +23,7 @@ Use Node 22 or later. On Node 18, `npm install` prints `EBADENGINE` for `@x402/s
 
 ## Steps
 
-1. Give the agent a funded identity. See [Quickstart](../quickstart.mdx) if you have not already. Skip `--secure-store` here: the x402 client needs the raw secret key in step 3, and a secure-store identity refuses to reveal it. This is the one flow where the key cannot live in the OS keychain.
+1. Give the agent a funded identity. See [Quickstart](/docs/tools/cli/agent-cli/quickstart) if you have not already. Skip `--secure-store` here: the x402 client needs the raw secret key in step 3, and a secure-store identity refuses to reveal it. This is the one flow where the key cannot live in the OS keychain.
 
    ```bash
    stellar keys generate agent-1 --network testnet --fund
@@ -51,7 +48,7 @@ Use Node 22 or later. On Node 18, `npm install` prints `EBADENGINE` for `@x402/s
      --dest-amount <SMALLEST_UNITS> --send-max <CEILING_IN_STROOPS>
    ```
 
-   Both commands print nothing to stdout on success: exit 0 and a single `ℹ️  Signing transaction: <HASH>` line on stderr, with no result code. That is how the whole `tx new` family behaves; see [`tx new` has no machine-readable receipt](../reference/output-and-errors.mdx#tx-new-has-no-machine-readable-receipt). Re-read the balance to confirm.
+   Both commands print nothing to stdout on success: exit 0 and a single `ℹ️  Signing transaction: <HASH>` line on stderr, with no result code. That is how the whole `tx new` family behaves; see [`tx new` has no machine-readable receipt](/docs/tools/cli/agent-cli/reference/output-and-errors#tx-new-has-no-machine-readable-receipt). Re-read the balance to confirm.
 
    A self-addressed path payment is a swap. Acquire several times the challenge amount, not exactly it: each paid call spends again and step 6 is not replayable, so one client-side mistake sends you back here.
 
@@ -149,7 +146,7 @@ Capture the body on the first request. Each call pays again: a paid response is
 
 ## Facilitators
 
-A facilitator is a third party that verifies and settles the payment for the server. They differ in maturity, and [x402 facilitators](../../../../build/agentic-payments/x402/README.mdx#x402-facilitators) keeps the current list. The main options:
+A facilitator is a third party that verifies and settles the payment for the server. They differ in maturity, and [x402 facilitators](/docs/build/agentic-payments/x402#x402-facilitators) keeps the current list. The main options:
 
 - **OpenZeppelin's "Built on Stellar" facilitator** is free, public, covers both testnet and mainnet, sponsors transaction fees, and settles in roughly five seconds. It is the most production-credible option today.
 - **Coinbase's hosted facilitator** supports Stellar on testnet only.
@@ -166,7 +163,7 @@ x402 on Stellar works with any SEP-41 token. USDC is the default, and it is the
 
 Stellar's own x402 announcement names an "x402-MCP server" that would let an agent "authorize payments via smart wallets within user-defined spending policies." That is listed as in active development, not shipped. There is no policy layer for x402 on Stellar today.
 
-The actual bound on an x402 agent's spending is the balance of the account it pays from, or an allowance you granted with `stellar token approve` if the signer sits behind one. Read [Authority model](../reference/authority-model.mdx) before pointing an x402 client at a mainnet key with a real balance.
+The actual bound on an x402 agent's spending is the balance of the account it pays from, or an allowance you granted with `stellar token approve` if the signer sits behind one. Read [Authority model](/docs/tools/cli/agent-cli/reference/authority-model) before pointing an x402 client at a mainnet key with a real balance.
 
 ## Common pitfalls
 
@@ -178,7 +175,7 @@ A facilitator sits in your payment path as a third party. It verifies and settle
 
 ## Related pages
 
-- [Send tokens](send-tokens.mdx)
-- [Delegate spending](delegate-spending.mdx)
-- [Authority model](../reference/authority-model.mdx)
-- [Quickstart](../quickstart.mdx)
+- [Send tokens](/docs/tools/cli/agent-cli/guides/send-tokens)
+- [Delegate spending](/docs/tools/cli/agent-cli/guides/delegate-spending)
+- [Authority model](/docs/tools/cli/agent-cli/reference/authority-model)
+- [Quickstart](/docs/tools/cli/agent-cli/quickstart)
diff --git a/docs/tools/cli/agent-cli/guides/send-tokens.mdx b/docs/tools/cli/agent-cli/guides/send-tokens.mdx
index 80e349f81..2f0ddd8b7 100644
--- a/docs/tools/cli/agent-cli/guides/send-tokens.mdx
+++ b/docs/tools/cli/agent-cli/guides/send-tokens.mdx
@@ -1,12 +1,9 @@
 ---
 title: Send tokens
-sidebar_position: 10
 description: Send the native asset or a classic asset with `stellar token transfer`, and confirm what shipped.
 keywords: [Stellar, agent, token transfer, payments, CLI]
 ---
 
-# Send tokens
-
 Send someone tokens and confirm the money arrived.
 
 ## Ask your agent
@@ -86,7 +83,7 @@ A nonexistent destination does not announce itself. On a classic asset it return
 
 ## Related pages
 
-- [Check balances and metadata](check-balances-and-metadata.mdx)
-- [Delegate spending](delegate-spending.mdx)
-- [Quickstart](../quickstart.mdx)
-- [Authority model](../reference/authority-model.mdx)
+- [Check balances and metadata](/docs/tools/cli/agent-cli/guides/check-balances-and-metadata)
+- [Delegate spending](/docs/tools/cli/agent-cli/guides/delegate-spending)
+- [Quickstart](/docs/tools/cli/agent-cli/quickstart)
+- [Authority model](/docs/tools/cli/agent-cli/reference/authority-model)
diff --git a/docs/tools/cli/agent-cli/guides/sign-messages.mdx b/docs/tools/cli/agent-cli/guides/sign-messages.mdx
index efeb8ba9a..74abc33ff 100644
--- a/docs/tools/cli/agent-cli/guides/sign-messages.mdx
+++ b/docs/tools/cli/agent-cli/guides/sign-messages.mdx
@@ -1,12 +1,9 @@
 ---
 title: Sign messages
-sidebar_position: 40
 description: Sign and verify a message offline with `stellar message sign` and `stellar message verify`, SEP-53.
 keywords: [Stellar, agent, message signing, SEP-53, verify]
 ---
 
-# Sign messages
-
 Prove control of a key by signing a piece of text, and let someone else verify it. `stellar message sign` and `verify` implement SEP-53 and run fully offline, with no funded account or network flag.
 
 ## Ask your agent
@@ -55,6 +52,6 @@ SEP-53 proves control of a single key. It does not prove control of an account.
 
 ## Related pages
 
-- [Delegate spending](delegate-spending.mdx)
-- [Authority model](../reference/authority-model.mdx)
-- [Quickstart](../quickstart.mdx)
+- [Delegate spending](/docs/tools/cli/agent-cli/guides/delegate-spending)
+- [Authority model](/docs/tools/cli/agent-cli/reference/authority-model)
+- [Quickstart](/docs/tools/cli/agent-cli/quickstart)
diff --git a/docs/tools/cli/agent-cli/guides/usdt0-on-mainnet.mdx b/docs/tools/cli/agent-cli/guides/usdt0-on-mainnet.mdx
index 375ebd793..1e4d8c414 100644
--- a/docs/tools/cli/agent-cli/guides/usdt0-on-mainnet.mdx
+++ b/docs/tools/cli/agent-cli/guides/usdt0-on-mainnet.mdx
@@ -1,6 +1,5 @@
 ---
 title: USDT0 on mainnet
-sidebar_position: 70
 description: Work with USDT0 on Stellar mainnet from the CLI. Addresses, trustlines, the clawback flags, and how to acquire it safely.
 keywords:
   [
@@ -16,15 +15,13 @@ keywords:
   ]
 ---
 
-# USDT0 on mainnet
-
 Get USDT0 into a mainnet account, hold it, and move some of it.
 
-:::caution
+<Warning>
 
 Every command on this page moves real value on mainnet, and a confirmed transaction cannot be reversed. Before you let an agent run them, bound what it can reach: give it a [capped allowance](#give-an-agent-a-capped-allowance) or a small balance of its own, never the key to the account that holds your funds.
 
-:::
+</Warning>
 
 ## Ask your agent
 
@@ -33,15 +30,15 @@ Check the USDT0 balance of GATISXX6BZ6NC7IKQBY37CJD4SOZL3CYZJWXEDG6JVIY4WBS6KXJH
 then tell me what the current XLM to USDT0 rate is.
 ```
 
-:::tip
+<Tip>
 
 Read [Acquire USDT0](#acquire-usdt0) before you buy any. It covers which route to use and how to bound a trade.
 
-:::
+</Tip>
 
 ## Addresses
 
-USDT0 is a classic Stellar asset with a Stellar Asset Contract. Its supply is unified with USDT on other chains, minted and burned on Stellar by a LayerZero OFT contract. It is live on mainnet only. [USDT0 on Stellar](pathname:///launch/usdt0) is the source of truth for these values.
+USDT0 is a classic Stellar asset with a Stellar Asset Contract. Its supply is unified with USDT on other chains, minted and burned on Stellar by a LayerZero OFT contract. It is live on mainnet only. [USDT0 on Stellar](/launch/usdt0) is the source of truth for these values.
 
 | Thing | Value |
 | --- | --- |
@@ -60,7 +57,7 @@ stellar contract id asset --asset USDT0:GATISXX6BZ6NC7IKQBY37CJD4SOZL3CYZJWXEDG6
 
 ## Set up mainnet first
 
-The built-in `mainnet` entry has no RPC URL, so mainnet commands fail with `Invalid URL Bring Your Own` until you add one. Pick an endpoint from Stellar's [RPC providers page](../../../../data/apis/rpc/providers.mdx). Once you pass `--rpc-url`, you must also pass `--network-passphrase`:
+The built-in `mainnet` entry has no RPC URL, so mainnet commands fail with `Invalid URL Bring Your Own` until you add one. Pick an endpoint from Stellar's [RPC providers page](/docs/data/apis/rpc/providers). Once you pass `--rpc-url`, you must also pass `--network-passphrase`:
 
 ```bash
 stellar network add mainnet \
@@ -112,7 +109,7 @@ stellar tx new create-account --source <FUNDED_IDENTITY> --destination <NEW_ADDR
 
 ## Acquire USDT0
 
-Transfer USDT0 to Stellar from another network at [usdt0.to/transfer](https://usdt0.to/transfer), or buy it on a venue that supports Stellar, such as Kraken or SushiSwap. [USDT0 on Stellar](pathname:///launch/usdt0) lists the integrated exchanges, ramps, and custodians. A cross-chain transfer costs the source network's gas plus the LayerZero message, and some routes enforce a minimum amount.
+Transfer USDT0 to Stellar from another network at [usdt0.to/transfer](https://usdt0.to/transfer), or buy it on a venue that supports Stellar, such as Kraken or SushiSwap. [USDT0 on Stellar](/launch/usdt0) lists the integrated exchanges, ramps, and custodians. A cross-chain transfer costs the source network's gas plus the LayerZero message, and some routes enforce a minimum amount.
 
 To swap from the CLI, use a path payment and always set `--dest-min`, so a bad rate fails instead of executing. The CLI has no price command, so quote the trade against Horizon's path endpoint first and set the bound below the quote:
 
@@ -145,7 +142,7 @@ stellar token transfer-from --id USDT0:GATISXX6… --spender <AGENT> --from <OWN
   --to <DESTINATION> --amount <SMALLEST_UNIT> --network mainnet
 ```
 
-See [Delegate spending](delegate-spending.mdx).
+See [Delegate spending](/docs/tools/cli/agent-cli/guides/delegate-spending).
 
 ## Revocation and clawback
 
@@ -173,6 +170,6 @@ Without `--limit`, the trustline is effectively uncapped. `--limit 0` removes th
 
 ## Related pages
 
-- [Send tokens](send-tokens.mdx)
-- [Build and submit transactions](build-and-submit-transactions.mdx)
-- [Authority model](../reference/authority-model.mdx)
+- [Send tokens](/docs/tools/cli/agent-cli/guides/send-tokens)
+- [Build and submit transactions](/docs/tools/cli/agent-cli/guides/build-and-submit-transactions)
+- [Authority model](/docs/tools/cli/agent-cli/reference/authority-model)
diff --git a/docs/tools/cli/agent-cli/index.mdx b/docs/tools/cli/agent-cli/index.mdx
new file mode 100644
index 000000000..bafba07b5
--- /dev/null
+++ b/docs/tools/cli/agent-cli/index.mdx
@@ -0,0 +1,57 @@
+---
+title: Stellar CLI for Agents
+sidebarTitle: Stellar CLI for Agents
+description: Use the Stellar CLI and CLI Skills to give your AI agents an agent-friendly wallet and native way to inspect, move, and manage assets on Stellar.
+---
+
+Use the Stellar CLI and CLI Skills to give your AI agents an agent-friendly wallet and native way to inspect, move, and manage assets on Stellar. After following the [Quickstart](/docs/tools/cli/agent-cli/quickstart) to onboard your agent, you can use natural language to prompt your agent to use the Stellar CLI.
+
+Verified against `stellar-cli` 28.1.0.
+
+| What You Ask Your Agent | What Your Agent Executes | How It Works Under the Hood |
+| --- | --- | --- |
+| **"Learn how to use the Stellar CLI"** | `stellar skill` | Dumps structured CLI conventions directly into the agent’s prompt/context window. |
+| **"How much USDC is in alice's account?"** | `stellar token balance` | Reads the balance in smallest units, or as a decimal with `--decimal`. No key setup needed. |
+| **"Send 20 USDC to `G...`"** | `stellar token transfer` | Executes an onchain transfer and returns the transaction hash. |
+| **"Limit agent spending to 50 USDC"** | `stellar token approve` | Grants a capped, time-bound allowance enforced directly onchain by the Stellar network. |
+| **"Draft a payment for my review"** | `stellar tx new payment --build-only` | Builds an unsubmitted transaction payload to a file for human sign-off or air-gapped execution. |
+
+## Agent Ergonomics
+
+Browser wallets are hard for agents. The CLI provides four key agent primitive enhancements:
+
+- **Unified Asset Resolution:** Interacts with native XLM, SAC (Stellar Asset Contracts), or SEP-41 tokens using consistent identifiers (`CODE:ISSUER`, contract ID, or custom alias).
+- **Self-Scaffolding Context:** Running `stellar contract init` automatically generates an `AGENTS.md` guide in local project directories, giving LLMs instant awareness of local commands and tool rules. [Build and deploy a contract](/docs/tools/cli/agent-cli/guides/build-and-deploy-contracts#the-generated-agentsmd) covers what it contains and how to customize it.
+- **Structured JSON Outputs (`--output json`):** The `stellar token` commands return typed JSON, including transaction hashes and a typed error envelope. Coverage elsewhere varies, and `tx send` and `tx new` have no `--output` flag. [Output and errors](/docs/tools/cli/agent-cli/reference/output-and-errors) lists what each command supports.
+- **Onchain Diagnostic Errors:** When a transaction reverts, the CLI returns the contract's diagnostic event trail inside the error envelope. Agents can read _why_ a transaction failed.
+
+## Capability Surface
+
+Beyond only using the Stellar CLI as a wallet, your agent can also use the full power of CLI to interact with, build, and deploy contracts. Humans can read the full [Stellar CLI Manual](/docs/tools/cli/stellar-cli).
+
+| Functional Area | What Your Agent Can Do | CLI Commands |
+| --- | --- | --- |
+| **System & Agent Context** | Check environment health and load usage rules into LLM context windows. | `stellar doctor`<br />`stellar skill` |
+| **Balances & Metadata** | Read token holdings, inspect token names, symbols, and decimal precision. | `stellar token balance`<br />`stellar token decimals / name / symbol` |
+| **Transfers & Payments** | Move tokens and get back the transaction hash, as a bare line by default or as JSON with `--output json`. | `stellar token transfer` |
+| **Spending Limits** | Set spending limits and audit active delegate approvals. | `stellar token approve`<br />`stellar token allowance` |
+| **Transactions & Contracts** | Build raw operations, deploy Soroban contracts, and invoke custom smart contracts. | `stellar tx new <OP>`<br />`stellar contract deploy / invoke` |
+| **Safe Offline Operations** | Draft unsigned transactions for human-in-the-loop approval workflows. | `stellar tx new <OP> --build-only` |
+
+## Safety Architecture
+
+Giving an agent financial execution power requires hard guardrails. The first two below are enforced by the network or by a human signer, not by the agent following instructions. The third is a convention your agent has to follow:
+
+1. **Protocol Allowance Enforcement:** Primary funds remain in your treasury account. Issue your agent a capped allowance using `stellar token approve`. If the agent attempts to overspend, the Stellar ledger rejects the transaction.
+2. **Human Approval Workflows:** Use `--build-only` flags on sensitive transactions. Your agent formats the payload into a file, leaving final signing authority to a human or air-gapped machine.
+3. **Explicit Smallest-Unit Amounts:** `token transfer` and `token approve` take `--amount` in the token's smallest unit and do no conversion. Read `stellar token decimals` first and have the agent show its arithmetic before it sends.
+
+## Where to go next
+
+- [Skills](/docs/tools/cli/agent-cli/skills) covers `stellar skill`, the built-in guide that teaches your agent the CLI's conventions.
+- [Delegate spending](/docs/tools/cli/agent-cli/guides/delegate-spending) is the page to read before any real money is involved.
+- [Build and deploy a contract](/docs/tools/cli/agent-cli/guides/build-and-deploy-contracts) takes your agent from `stellar contract init` to a deployed contract it can call.
+- [Authority & Security Model](/docs/tools/cli/agent-cli/reference/authority-model) is explicit about what the CLI does not protect you from.
+- [Architecture](/docs/tools/cli/agent-cli/reference/architecture) covers how the read and write paths differ, where state lives, and how to split building, signing, and submitting across machines.
+- [Output and errors](/docs/tools/cli/agent-cli/reference/output-and-errors) covers which commands emit structured JSON your agent can branch on, because the coverage is not uniform.
+- [Troubleshooting](/docs/tools/cli/agent-cli/reference/troubleshooting) for when something does not work.
diff --git a/docs/tools/cli/agent-cli/quickstart.mdx b/docs/tools/cli/agent-cli/quickstart.mdx
index 9bc0b19e7..4df3a6471 100644
--- a/docs/tools/cli/agent-cli/quickstart.mdx
+++ b/docs/tools/cli/agent-cli/quickstart.mdx
@@ -1,14 +1,11 @@
 ---
 title: Quickstart
-sidebar_label: Agent Quickstart
-sidebar_position: 10
+sidebarTitle: Agent Quickstart
 description: Install the stellar CLI, connect it to your agent, fund a testnet key, and make your first agent-driven transfer.
 keywords:
   [Stellar, agent, quickstart, CLI, testnet, stellar token, CI, secure store]
 ---
 
-# Quickstart
-
 ## Before you start
 
 You need a terminal on macOS, Linux, WSL, or Windows, and an AI agent that can run shell commands (Claude Code, Codex, Cursor, or similar). Contract development also needs the `wasm32v1-none` target, but nothing on this page does.
@@ -17,7 +14,7 @@ Every command below targets testnet, where friendbot funds accounts for free. Mo
 
 ## Step 1: Install the CLI
 
-You need `stellar-cli` 28.1.0 or later. That release adds the `stellar token` metadata, allowance, `transfer-from`, and burn subcommands and the `stellar skill` command these docs rely on. Follow [Install the Stellar CLI](../install-cli.mdx), then confirm the version:
+You need `stellar-cli` 28.1.0 or later. That release adds the `stellar token` metadata, allowance, `transfer-from`, and burn subcommands and the `stellar skill` command these docs rely on. Follow [Install the Stellar CLI](/docs/tools/cli/install-cli), then confirm the version:
 
 ```bash
 stellar --version
@@ -45,11 +42,11 @@ Run `stellar skill` and follow its conventions for every stellar command in this
 
 Give the agent its own identity rather than sharing yours, so its transactions come from an account you fund separately and can see in isolation.
 
-:::warning
+<Warning>
 
 Keys are stored locally on your device, and nothing stops your agent from reaching them. It runs as your user, so it can read `~/.config/stellar/identity/`, run `stellar keys secret` to print a secret key or seed phrase, or sign with any identity on the machine, including yours. `--secure-store` keeps the seed out of a plaintext file, but the agent can still use it through the CLI. Keep only what you are willing to lose in any identity on a machine your agent runs on.
 
-:::
+</Warning>
 
 ```bash
 stellar keys generate agent-1 --network testnet --fund
@@ -85,7 +82,7 @@ Pick one. This is the decision that determines your exposure.
 - **Own key.** The agent holds `agent-1` and spends from it directly. Simple, and bounded only by that account's balance. Use it on testnet and for small mainnet amounts.
 - **Allowance.** You keep funds in an account the agent does not control, and grant `agent-1` a capped, expiring allowance with `stellar token approve`. The network enforces the cap. Use it when the funding account holds more than you want at risk.
 
-[Delegate spending](./guides/delegate-spending.mdx) walks through the allowance path, including how the agent spends it with `stellar token transfer-from`. [Authority model](./reference/authority-model.mdx) explains what neither option protects you from.
+[Delegate spending](/docs/tools/cli/agent-cli/guides/delegate-spending) walks through the allowance path, including how the agent spends it with `stellar token transfer-from`. [Authority model](/docs/tools/cli/agent-cli/reference/authority-model) explains what neither option protects you from.
 
 ## Step 5: Set your defaults
 
@@ -153,10 +150,10 @@ stellar tx fetch result --hash "$TX" --network testnet
 
 **Never retry a timed-out write blindly.** On `transaction submission timeout` the RPC accepted the transaction but never reported a final status, so the outcome is unknown. It can still land later. The command exits 1 and `$TX` can be empty, exactly like a real failure. Take the hash from the stderr line `ℹ️  Signing transaction: <HASH>` (text mode only, since JSON mode writes nothing to stderr) and check `stellar tx fetch result --hash <HASH>`. If it is still not found, read both balances and the source account's sequence number before you decide. Only rebuild the payment once you have confirmed the first one did not land.
 
-An error starting with `❌` that names a cause (`TxBadAuth`, `TxBadSeq`, a rejected simulation) is a real failure and safe to retry. See [Output and errors](reference/output-and-errors.mdx) before you build error handling, because only the `stellar token` family returns typed errors.
+An error starting with `❌` that names a cause (`TxBadAuth`, `TxBadSeq`, a rejected simulation) is a real failure and safe to retry. See [Output and errors](/docs/tools/cli/agent-cli/reference/output-and-errors) before you build error handling, because only the `stellar token` family returns typed errors.
 
 ## Next steps
 
-- [Send tokens](guides/send-tokens.mdx)
-- [Delegate spending](guides/delegate-spending.mdx)
-- [Authority model](reference/authority-model.mdx)
+- [Send tokens](/docs/tools/cli/agent-cli/guides/send-tokens)
+- [Delegate spending](/docs/tools/cli/agent-cli/guides/delegate-spending)
+- [Authority model](/docs/tools/cli/agent-cli/reference/authority-model)
diff --git a/docs/tools/cli/agent-cli/reference/_category_.json b/docs/tools/cli/agent-cli/reference/_category_.json
deleted file mode 100644
index 5c64bb31b..000000000
--- a/docs/tools/cli/agent-cli/reference/_category_.json
+++ /dev/null
@@ -1 +0,0 @@
-{ "label": "Reference", "collapsed": true, "position": 40 }
diff --git a/docs/tools/cli/agent-cli/reference/architecture.mdx b/docs/tools/cli/agent-cli/reference/architecture.mdx
index 5a9d6fbed..7076dafc2 100644
--- a/docs/tools/cli/agent-cli/reference/architecture.mdx
+++ b/docs/tools/cli/agent-cli/reference/architecture.mdx
@@ -1,16 +1,13 @@
 ---
 title: Architecture
-sidebar_position: 10
 description: How the Stellar CLI is put together, where it keeps state, how read and write paths differ, and how an agent connects to it.
 keywords:
   [Stellar, CLI, architecture, simulation, signing, local state, MCP, skills]
 ---
 
-# Architecture
-
 The Stellar CLI is a single static binary that communicates directly with a Stellar RPC endpoint. It operates without server components, sessions, accounts, or intermediary proxies. Both human operators and autonomous agents run the exact same binary.
 
-Because no middleware sits between the client and the network, commands compose cleanly and no third-party service can block or modify transactions. See [Authority model](authority-model.mdx).
+Because no middleware sits between the client and the network, commands compose cleanly and no third-party service can block or modify transactions. See [Authority model](/docs/tools/cli/agent-cli/reference/authority-model).
 
 ## Local State
 
@@ -83,7 +80,7 @@ stellar network add mainnet --rpc-url <YOUR_MAINNET_RPC_URL> \
 
 ```
 
-Refer to the [RPC providers directory](../../../../data/apis/rpc/providers.mdx) for endpoints. The public endpoint `https://mainnet.sorobanrpc.com` requires no API key.
+Refer to the [RPC providers directory](/docs/data/apis/rpc/providers) for endpoints. The public endpoint `https://mainnet.sorobanrpc.com` requires no API key.
 
 ## Write Path
 
@@ -142,11 +139,11 @@ Arguments passed after `--` are validated by the generated interface, allowing a
 ## Agent Integration Tools
 
 - **Raven MCP Server:** Hosted Model Context Protocol endpoint (`[https://raven.stellar.buzz/mcp](https://raven.stellar.buzz/mcp)`). Provides documentation search, network graph data, and ecosystem queries across `stellarDocs`, `scout`, and `lumenloop` namespaces. Read-only research endpoint requiring OAuth browser authentication; cannot sign or submit transactions.
-- **`stellar skill`:** Outputs built-in CLI usage documentation directly from the compiled binary. See [Skills](../skills.mdx).
+- **`stellar skill`:** Outputs built-in CLI usage documentation directly from the compiled binary. See [Skills](/docs/tools/cli/agent-cli/skills).
 - **`AGENTS.md`:** Standard workspace template emitted by `stellar contract init` (v28.0.0+) providing build and test directives for contract development agents.
 
 ## Related Pages
 
-- [Authority model](authority-model.mdx)
-- [Output and errors](output-and-errors.mdx)
-- [Build and submit transactions](../guides/build-and-submit-transactions.mdx)
+- [Authority model](/docs/tools/cli/agent-cli/reference/authority-model)
+- [Output and errors](/docs/tools/cli/agent-cli/reference/output-and-errors)
+- [Build and submit transactions](/docs/tools/cli/agent-cli/guides/build-and-submit-transactions)
diff --git a/docs/tools/cli/agent-cli/reference/authority-model.mdx b/docs/tools/cli/agent-cli/reference/authority-model.mdx
index c683be09a..6f6878bf6 100644
--- a/docs/tools/cli/agent-cli/reference/authority-model.mdx
+++ b/docs/tools/cli/agent-cli/reference/authority-model.mdx
@@ -1,6 +1,5 @@
 ---
 title: "Authority & Security Model"
-sidebar_position: 20
 description: What bounds an agent's spending authority when it drives the Stellar CLI, which controls exist today, and which do not.
 keywords:
   [
@@ -15,8 +14,6 @@ keywords:
   ]
 ---
 
-# Authority & Security Model
-
 The Stellar CLI signs and submits transactions strictly as instructed. It operates without an intermediate proxy, approval service, or built-in transaction filter. Security and spend limits are achieved through **protocol-level constraints** on the Stellar network and **custodial scoping** of agent keys.
 
 ## What the CLI Does (and Does Not) Enforce
diff --git a/docs/tools/cli/agent-cli/reference/output-and-errors.mdx b/docs/tools/cli/agent-cli/reference/output-and-errors.mdx
index 1e57717a1..6dbed297e 100644
--- a/docs/tools/cli/agent-cli/reference/output-and-errors.mdx
+++ b/docs/tools/cli/agent-cli/reference/output-and-errors.mdx
@@ -1,17 +1,14 @@
 ---
 title: Output and errors
-sidebar_position: 30
 description: Which stellar commands support --output and which values each accepts, the token family's typed error envelope, and how every other command reports failure.
 keywords: [Stellar, agent, CLI, output, errors, JSON, exit codes, stellar token]
 ---
 
-# Output and errors
-
-:::note
+<Note>
 
 A global `--output json` flag that works on every command is coming soon. Until then, `--output` is declared per command, and each command has its own values and default.
 
-:::
+</Note>
 
 The `stellar token` family returns a typed, machine-parseable error envelope. Other commands report failure as text on stderr plus a non-zero exit code. Check the table below before you wire an agent to parse CLI output.
 
@@ -292,6 +289,6 @@ Running `keys fund` on a `#6` you have not scoped creates a real, separate accou
 
 ## Related pages
 
-- [Quickstart](../quickstart.mdx)
-- [Troubleshooting](troubleshooting.mdx)
-- [Authority model](authority-model.mdx)
+- [Quickstart](/docs/tools/cli/agent-cli/quickstart)
+- [Troubleshooting](/docs/tools/cli/agent-cli/reference/troubleshooting)
+- [Authority model](/docs/tools/cli/agent-cli/reference/authority-model)
diff --git a/docs/tools/cli/agent-cli/reference/troubleshooting.mdx b/docs/tools/cli/agent-cli/reference/troubleshooting.mdx
index 741eb9b8c..eb95c71e6 100644
--- a/docs/tools/cli/agent-cli/reference/troubleshooting.mdx
+++ b/docs/tools/cli/agent-cli/reference/troubleshooting.mdx
@@ -1,12 +1,9 @@
 ---
 title: Troubleshooting
-sidebar_position: 40
 description: Start with stellar doctor, then fix funding, trustline, network, and signing errors your agent will hit with the stellar CLI.
 keywords: [Stellar, agent, troubleshooting, stellar doctor, stellar CLI, errors]
 ---
 
-# Troubleshooting
-
 ## Start with `stellar doctor`
 
 Run this before debugging anything else:
@@ -206,7 +203,7 @@ stellar network add mainnet --rpc-url <YOUR_MAINNET_RPC_URL> \
   --network-passphrase "Public Global Stellar Network ; September 2015"
 ```
 
-Pick an endpoint from Stellar's [RPC providers page](../../../../data/apis/rpc/providers.mdx), or use the public `https://mainnet.sorobanrpc.com` if you want one without a signup.
+Pick an endpoint from Stellar's [RPC providers page](/docs/data/apis/rpc/providers), or use the public `https://mainnet.sorobanrpc.com` if you want one without a signup.
 
 ### Default network unreachable
 
@@ -244,13 +241,13 @@ Fix: pass `--network` explicitly at the sign stage, every time.
 stellar tx sign --sign-with-key <NAME> --network <NET>
 ```
 
-**Cause 2, not enough signature weight.** On an account with multiple signers, a signature that does not meet the operation's threshold fails the same way. This is the expected result when an agent signs alone on a co-signed vault, and it is not an error to fix: it is the control working. No fee is charged and the source account's sequence number is unchanged, so the same envelope can still be co-signed and submitted. See [Delegate spending](../guides/delegate-spending.mdx).
+**Cause 2, not enough signature weight.** On an account with multiple signers, a signature that does not meet the operation's threshold fails the same way. This is the expected result when an agent signs alone on a co-signed vault, and it is not an error to fix: it is the control working. No fee is charged and the source account's sequence number is unchanged, so the same envelope can still be co-signed and submitted. See [Delegate spending](/docs/tools/cli/agent-cli/guides/delegate-spending).
 
 Tell the two apart by hashing: a passphrase mismatch changes the envelope hash, a weight shortfall does not.
 
 ## Delegated spending
 
-Errors specific to the four patterns in [Delegate spending](../guides/delegate-spending.mdx), each measured on testnet.
+Errors specific to the four patterns in [Delegate spending](/docs/tools/cli/agent-cli/guides/delegate-spending), each measured on testnet.
 
 ### `TxBadAuthExtra` when co-signing
 
@@ -344,6 +341,6 @@ stellar keys secret <NAME>
 
 ## Related pages
 
-- [Output and errors](output-and-errors.mdx)
-- [Quickstart](../quickstart.mdx)
-- [Authority model](authority-model.mdx)
+- [Output and errors](/docs/tools/cli/agent-cli/reference/output-and-errors)
+- [Quickstart](/docs/tools/cli/agent-cli/quickstart)
+- [Authority model](/docs/tools/cli/agent-cli/reference/authority-model)
diff --git a/docs/tools/cli/agent-cli/skills.mdx b/docs/tools/cli/agent-cli/skills.mdx
index 4de7a3e1a..3f2851cdc 100644
--- a/docs/tools/cli/agent-cli/skills.mdx
+++ b/docs/tools/cli/agent-cli/skills.mdx
@@ -1,12 +1,11 @@
 ---
 title: Skills
-sidebar_label: Skills
-sidebar_position: 20
+sidebarTitle: Skills
 description: "What the stellar skill subcommand gives your agent, what it leaves out, and an optional skill for broader Stellar development."
 keywords: [Stellar, agent, skills, SKILL.md, stellar skill, agent experience]
 ---
 
-The Stellar CLI ships with a built-in `skill` subcommand. Running `stellar skill` prints a short Markdown guide that tells an AI agent how to drive the CLI, so there is nothing separate to install. [Quickstart](quickstart.mdx) has your agent run it at the start of a session.
+The Stellar CLI ships with a built-in `skill` subcommand. Running `stellar skill` prints a short Markdown guide that tells an AI agent how to drive the CLI, so there is nothing separate to install. [Quickstart](/docs/tools/cli/agent-cli/quickstart) has your agent run it at the start of a session.
 
 ## Ask your agent
 
@@ -22,7 +21,7 @@ The guide is static text compiled into the binary ([source](https://github.com/s
 
 ## Project context: `AGENTS.md`
 
-`stellar skill` describes the CLI. A project made with `stellar contract init` also gets an `AGENTS.md` file that describes that project. [Build and deploy a contract](guides/build-and-deploy-contracts.mdx#the-generated-agentsmd) covers what it contains, how agents read it, and how to customize it.
+`stellar skill` describes the CLI. A project made with `stellar contract init` also gets an `AGENTS.md` file that describes that project. [Build and deploy a contract](/docs/tools/cli/agent-cli/guides/build-and-deploy-contracts#the-generated-agentsmd) covers what it contains, how agents read it, and how to customize it.
 
 ## Optional: Stellar development skill
 
diff --git a/docs/tools/cli/cookbook/README.mdx b/docs/tools/cli/cookbook/README.mdx
deleted file mode 100644
index 5737302cf..000000000
--- a/docs/tools/cli/cookbook/README.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: Cookbook
-hide_table_of_contents: true
-sidebar_class_name: sidebar-category-items-hidden
-sidebar_position: 150
----
-
-import DocCardList from "@theme/DocCardList";
-
-Guides that will help you use the Stellar CLI.
-
-If you do not have the CLI yet, see [Install the CLI](../install-cli.mdx).
diff --git a/docs/tools/cli/cookbook/_category_.json b/docs/tools/cli/cookbook/_category_.json
deleted file mode 100644
index d0ae8bacd..000000000
--- a/docs/tools/cli/cookbook/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsible": false
-}
diff --git a/docs/tools/cli/cookbook/asset-management.mdx b/docs/tools/cli/cookbook/asset-management.mdx
index c6ae9365a..be4362753 100644
--- a/docs/tools/cli/cookbook/asset-management.mdx
+++ b/docs/tools/cli/cookbook/asset-management.mdx
@@ -1,7 +1,289 @@
 ---
 title: Asset Management
-hide_table_of_contents: false
-description: Issue a Stellar Asset, deploy its contract, and mint, burn, freeze, and clawback.
+description: Issue a Stellar Asset, deploy it's contract, and mint, burn, freeze, and clawback.
 ---
 
-Stub file: the real file is generated in build time by `pnpm stellar-cli:build`.
+The [stellar-cli] can be used to issue and administer assets on the Stellar network.
+
+The following guide assumes that the [stellar-cli] has been configured to use testnet, or a local test network. To use testnet, run the following command.
+
+```bash
+stellar network use testnet
+```
+
+### Asset Issuance
+
+To create a Stellar Asset using the [stellar-cli] several steps take place:
+
+- An issuer account must exist.
+- An asset code selected.
+- Optionally, an admin is configured.
+
+#### Issuer Creation
+
+To create an issuer, generate a key and fund it. Funding uses friendbot, the testnet faucet, and is only available on testnet.
+
+```bash
+stellar keys generate issuer
+```
+
+```bash
+stellar keys fund issuer
+```
+
+View the public key with:
+
+```bash
+stellar keys public-key issuer
+```
+
+Configure the issuer key to be used for signing transactions:
+
+```bash
+stellar keys use issuer
+```
+
+#### Issuer Config
+
+Issuer accounts have several configuration flags that can be toggled and affect all assets issued by the issuer.
+
+In this guide the issuer account will be setup with the revocable and clawback-enabled features will be enabled. These features allow the asset admin to revoke authorisation to use an asset, which has the effect of freezing their balance, and to clawback, which has the effect of forcibly burning the asset.
+
+```bash
+stellar tx new set-options \
+  --set-revocable \
+  --set-clawback-enabled
+```
+
+For other options, see the manual for the [stellar tx new set-options] command.
+
+To view the tx before sending, use the `--build-only` option and pipe the transaction through the tx edit command:
+
+```bash cookbooktest.ignore="because piping isn't supported"
+stellar tx new set-options \
+  --set-revocable \
+  --set-clawback-enabled \
+  --build-only \
+  | stellar tx edit \
+  | stellar sign \
+  | stellar send
+```
+
+#### Choosing the Asset Code
+
+Choose an asset code 1 to 12 characters long.
+
+The asset code along with the issuer account address will uniquely identify the asset. An issuer can issue multiple assets, distinguished by their asset code.
+
+For the rest of this guide the asset code `ABC` will be used.
+
+#### Asset Contract Setup
+
+A built-in contract exists on network for every asset. It's address is reserved and can be calculated using the following command.
+
+```bash
+stellar contract asset id --asset ABC:issuer
+```
+
+The contract is not deployed automatically. Anyone can deploy the contract, it is not an action requiring authorisation.
+
+#### Contract Deployment {#contract-deployment}
+
+Deploy the built-in asset contract.
+
+The `--asset` option specifies the name of the asset, which is in the format `<asset-code>:<asset-issuer>`.
+
+The `--alias` option stores locally an alias that can be used in subsequent commands to reference the contract address.
+
+```bash
+stellar contract asset deploy --asset ABC:issuer --alias mycontract
+```
+
+Run the following command to get some read only data from the contract to confirm it's deployed.
+
+```bash
+stellar contract invoke --id mycontract -- name
+```
+
+#### Admin Setup {#admin-setup}
+
+At this point the issuer is the admin of the contract. Let's create another account that'll be the admin.
+
+```bash
+stellar keys generate admin
+```
+
+```bash
+stellar keys public-key admin
+```
+
+```bash
+stellar keys fund admin
+```
+
+Using the issuer account, invoke the asset contract's `set_admin` function.
+
+```bash
+stellar keys use issuer
+```
+
+```bash
+stellar contract invoke --source issuer --id mycontract -- set_admin --new_admin admin
+```
+
+### Actions
+
+Once the asset contract is deployed and setup, the following actions can take place.
+
+#### Mint (Admin Only)
+
+Generate and fund a user account that the minted asset will be transferred to.
+
+```bash
+stellar keys generate user
+```
+
+```bash
+stellar keys fund user
+```
+
+```bash
+stellar keys public-key user
+```
+
+Using the user account, trust the asset so that the user account can hold the asset.
+
+```bash
+stellar keys use user
+```
+
+```bash
+stellar tx new change-trust --line ABC:issuer
+```
+
+To mint the asset to the user, use the admin account, invoke the asset contract's `mint` function.
+
+```bash
+stellar keys use admin
+```
+
+```bash
+stellar contract invoke --id mycontract -- mint --to user --amount 25
+```
+
+Check the balance after the mint.
+
+```bash
+stellar contract invoke --id mycontract -- balance --id user
+```
+
+#### Transfer
+
+Generate and fund a second user account that the user account from the previous step can transfer the asset to.
+
+```bash
+stellar keys generate user2
+```
+
+```bash
+stellar keys fund user2
+```
+
+```bash
+stellar keys public-key user2
+```
+
+Using the user2 account, trust the asset so that the new user account can hold the asset.
+
+```bash
+stellar keys use user2
+```
+
+```bash
+stellar tx new change-trust --line ABC:issuer
+```
+
+Using the user account, invoke the asset contract's `transfer` function.
+
+```bash
+stellar keys use user
+```
+
+```bash
+stellar contract invoke --id mycontract -- transfer --from user --to user2 --amount 3
+```
+
+Check the balances after the transfer.
+
+```bash
+stellar contract invoke --id mycontract -- balance --id user
+```
+
+```bash
+stellar contract invoke --id mycontract -- balance --id user2
+```
+
+#### Burn
+
+Using the user account, invoke the asset contract's `burn` function.
+
+```bash
+stellar keys use user
+```
+
+```bash
+stellar contract invoke --id mycontract -- burn --from user --amount 5
+```
+
+Check the balance after the burn.
+
+```bash
+stellar contract invoke --id mycontract -- balance --id user
+```
+
+#### Revoke Authorization / Freeze (Admin Only) {#revoke-authorization--freeze-admin-only}
+
+An admin can revoke a user's authorisation to use the asset. The user will continue to hold the balance but will be unable to transfer it or create new payments. Any existing liabilities, such as those created by offers created on Stellar, will continue to exist and could still be executed.
+
+Using the admin, invoke the asset contract's `set_authorized` function.
+
+```bash
+stellar keys use admin
+```
+
+```bash
+stellar contract invoke --id mycontract -- set_authorized --id user --authorize false
+```
+
+Using the user account, invoke the asset contract's `transfer` function. The invocation will fail because they are no longer authorized to transfer.
+
+```bash
+stellar keys use user
+```
+
+```bash cookbooktest.fail cookbooktest.stderr="balance is deauthorized"
+stellar contract invoke --id mycontract -- transfer --from user --to user2 --amount 3
+```
+
+#### Clawback (Admin Only)
+
+An admin can clawback a user's balance. The amount clawed back will be burned.
+
+Using the admin, invoke the asset contract's `clawback` function.
+
+```bash
+stellar keys use admin
+```
+
+```bash
+stellar contract invoke --id mycontract -- clawback --from user --amount 1
+```
+
+Check the balance after the clawback.
+
+```bash
+stellar contract invoke --id mycontract -- balance --id user
+```
+
+[stellar-cli]: ../stellar-cli
+[stellar tx new set-options]: ../stellar-cli#stellar-tx-new-set-options
diff --git a/docs/tools/cli/cookbook/contract-build-meta.mdx b/docs/tools/cli/cookbook/contract-build-meta.mdx
index 358f9a112..ca127eea6 100644
--- a/docs/tools/cli/cookbook/contract-build-meta.mdx
+++ b/docs/tools/cli/cookbook/contract-build-meta.mdx
@@ -1,7 +1,33 @@
 ---
 title: Add meta data to contract WASM on build
-hide_table_of_contents: true
 description: Include meta data in the contract WASM byte code on build
 ---
 
-Stub file: the real file is generated in build time by `pnpm stellar-cli:build`.
+To build a smart contract, use the `stellar contract build` command. The `--meta` option will allow you to add additional meta data entries to the `contractmetav0` custom section of the resulting WASM file at build time.
+
+```bash cookbooktest.ignore
+export SHA=$(git rev-parse HEAD)
+```
+
+```bash
+stellar contract build \
+    --manifest-path ./cmd/crates/soroban-test/tests/fixtures/test-wasms/hello_world/Cargo.toml \
+    --meta source_repo=https://github.com/stellar/stellar-cli \
+    --meta commit_sha=$SHA
+```
+
+You can then use `stellar contract info meta` to see the meta data:
+
+```bash
+stellar contract info meta \
+  --wasm target/wasm32v1-none/release/test_hello_world.wasm
+```
+
+```bash cookbooktest.ignore
+Contract meta:
+ • rsver: 1.91.0 (Rust version)
+ • rssdkver: 23.0.1#510d3feb724c2b01d7e7ab7652f03b9f8efc3f35 (Soroban SDK version and its commit hash)
+ • cliver: 23.1.4#v20.0.0-646-g70895dd66fb7dbf2f4c2a81cf38546512ba4198e-dirty
+ • source_repo: https://github.com/stellar/stellar-cli
+ • commit_sha: c6f881689d3f4936cb3262089eb70142e9ca9c91
+```
diff --git a/docs/tools/cli/cookbook/contract-invoke-arguments.mdx b/docs/tools/cli/cookbook/contract-invoke-arguments.mdx
index b093ebc12..eb42aa2ea 100644
--- a/docs/tools/cli/cookbook/contract-invoke-arguments.mdx
+++ b/docs/tools/cli/cookbook/contract-invoke-arguments.mdx
@@ -1,7 +1,169 @@
 ---
 title: "Contract Invoke: Argument Types"
-hide_table_of_contents: true
 description: How to pass each argument type when invoking a Stellar smart contract using the CLI
 ---
 
-Stub file: the real file is generated in build time by `pnpm stellar-cli:build`.
+When using `stellar contract invoke`, each `--arg-name <value>` flag is parsed according to the contract's type spec. This guide shows the correct format for each supported type.
+
+### Integers (`u32`, `i32`, `u64`, `i64`)
+
+Pass bare numeric literals directly on the command line.
+
+```bash cookbooktest.ignore
+stellar contract invoke --id mycontract -- my_function \
+    --count 42 \
+    --offset -7
+```
+
+### Large Integers (`u128`, `i128`, `u256`, `i256`)
+
+Pass bare numeric literals, just like small integers. The CLI reads the raw value as a string internally, bypassing JSON number precision limits entirely.
+
+```bash cookbooktest.ignore
+stellar contract invoke --id mycontract -- my_function \
+    --amount 340282366920938463463374607431768211455
+```
+
+### Boolean
+
+Pass `true` or `false` as unquoted literals.
+
+```bash cookbooktest.ignore
+stellar contract invoke --id mycontract -- my_function \
+    --is_active true \
+    --is_paused false
+```
+
+### String
+
+Bare words work for simple strings. Numbers and booleans are also accepted and are automatically converted to their string representation, so you do not need to add extra quoting. Explicit JSON quoting is also accepted.
+
+```bash cookbooktest.ignore
+# Bare word
+stellar contract invoke --id mycontract -- my_function \
+    --label hello
+
+# Number auto-converted to string "42"
+stellar contract invoke --id mycontract -- my_function \
+    --label 42
+
+# Boolean auto-converted to string "true"
+stellar contract invoke --id mycontract -- my_function \
+    --label true
+
+# Explicitly quoted JSON string
+stellar contract invoke --id mycontract -- my_function \
+    --label '"hello world"'
+```
+
+### Symbol
+
+Symbols follow the same rules as `String`: bare words, numbers, and booleans are all accepted, and non-string JSON values are auto-converted.
+
+```bash cookbooktest.ignore
+stellar contract invoke --id mycontract -- my_function \
+    --status active
+```
+
+### Address
+
+You can pass either a locally known identity name (e.g. `alice`) or a raw Stellar strkey (`G…` for accounts, `C…` for contracts).
+
+```bash cookbooktest.ignore
+# Using an identity alias
+stellar contract invoke --id mycontract -- my_function \
+    --owner alice
+
+# Using a raw strkey
+stellar contract invoke --id mycontract -- my_function \
+    --owner GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN
+```
+
+### Bytes / BytesN {#bytes--bytesn}
+
+Pass a hex-encoded string representing the byte sequence.
+
+```bash cookbooktest.ignore
+stellar contract invoke --id mycontract -- my_function \
+    --hash "deadbeef01020304"
+```
+
+### Optional Arguments
+
+Simply omit the flag. The CLI will supply a `void` / null value for any `Option<T>` parameter that is not provided.
+
+```bash cookbooktest.ignore
+# If `--memo` is optional, leaving it out passes None
+stellar contract invoke --id mycontract -- my_function \
+    --amount 100
+```
+
+### Vec
+
+Pass a JSON array, quoting the whole value so the shell does not split it.
+
+```bash cookbooktest.ignore
+stellar contract invoke --id mycontract -- my_function \
+    --recipients '["alice", "bob", "carol"]'
+```
+
+### Map
+
+Pass a JSON object with string keys.
+
+```bash cookbooktest.ignore
+stellar contract invoke --id mycontract -- my_function \
+    --metadata '{"key": "value", "version": "1"}'
+```
+
+### Tuple
+
+Pass a JSON array whose elements match the tuple's field order.
+
+```bash cookbooktest.ignore
+stellar contract invoke --id mycontract -- my_function \
+    --point '[10, 20]'
+```
+
+### Struct (User-Defined Type)
+
+Pass a JSON object with the struct's named fields.
+
+```bash cookbooktest.ignore
+stellar contract invoke --id mycontract -- my_function \
+    --config '{"max_supply": "1000000", "decimals": 7}'
+```
+
+### Enum / Union (User-Defined Type) {#enum--union-user-defined-type}
+
+For unit variants, pass the variant name as a plain string. For variants that carry a value, pass a JSON object with the variant name as the key.
+
+```bash cookbooktest.ignore
+# Unit variant
+stellar contract invoke --id mycontract -- my_function \
+    --status "Active"
+
+# Variant with a value
+stellar contract invoke --id mycontract -- my_function \
+    --result '{"Ok": 42}'
+```
+
+### File-Based Arguments
+
+For long or complex JSON values, use the `--arg-file-path` flag variant to load the value from a file instead of inlining it on the command line. The flag name is derived from the argument name by appending `-file-path`.
+
+```bash cookbooktest.ignore
+# Write the JSON to a file first
+echo '{"max_supply": "1000000", "decimals": 7}' > config.json
+
+# Then reference the file
+stellar contract invoke --id mycontract -- my_function \
+    --config-file-path config.json
+```
+
+For `Bytes` and `BytesN` parameters, the file's raw binary content is read directly — no hex encoding is required.
+
+```bash cookbooktest.ignore
+stellar contract invoke --id mycontract -- my_function \
+    --hash-file-path /path/to/binary.bin
+```
diff --git a/docs/tools/cli/cookbook/contract-lifecycle.mdx b/docs/tools/cli/cookbook/contract-lifecycle.mdx
index 2464cb9cf..21f3deb73 100644
--- a/docs/tools/cli/cookbook/contract-lifecycle.mdx
+++ b/docs/tools/cli/cookbook/contract-lifecycle.mdx
@@ -1,7 +1,64 @@
 ---
 title: Contract Lifecycle
-hide_table_of_contents: true
 description: Manage the lifecycle of a Stellar smart contract using the CLI
 ---
 
-Stub file: the real file is generated in build time by `pnpm stellar-cli:build`.
+To manage the lifecycle of a Stellar smart contract using the CLI, follow these steps:
+
+1. Set your preferred network. For this guide, we will use `testnet`. A list of available networks can be found [here](/docs/networks)
+
+```bash
+stellar network use testnet
+```
+
+2. Create an identity for Alice:
+
+```bash
+stellar keys generate alice -q
+```
+
+3. Fund the identity:
+
+```bash
+stellar keys fund alice
+```
+
+4. Deploy a contract:
+
+```bash
+stellar keys use alice
+```
+
+```bash
+stellar contract deploy --wasm /path/to/contract.wasm --alias mycontract
+```
+
+This will display the resulting contract ID, e.g.:
+
+```
+CBB65ZLBQBZL5IYHDHEEPCVUUMFOQUZSQKAJFV36R7TZETCLWGFTRLOQ
+```
+
+To learn more about how to build contract `.wasm` files, take a look at our [getting started tutorial](../../../build/smart-contracts/getting-started/setup).
+
+5. Invoke a contract function:
+
+```bash
+stellar contract invoke --id mycontract -- <FUNCTION>
+```
+
+6. View the contract's state:
+
+```bash
+stellar contract read --id mycontract --durability <DURABILITY> --key <KEY>
+```
+
+Note: `<DURABILITY>` is either `persistent` or `temporary`. `KEY` provides the key of the storage entry being read.
+
+7. Manage expired states:
+
+```bash
+stellar contract extend --id mycontract --ledgers-to-extend 1000 --durability <DURABILITY> --key <KEY>
+```
+
+This extends the state of the instance provided by the given key to at least 1000 ledgers from the current ledger.
diff --git a/docs/tools/cli/cookbook/deploy-contract.mdx b/docs/tools/cli/cookbook/deploy-contract.mdx
index cdbe6dcf8..ddb9918f7 100644
--- a/docs/tools/cli/cookbook/deploy-contract.mdx
+++ b/docs/tools/cli/cookbook/deploy-contract.mdx
@@ -1,7 +1,20 @@
 ---
-title: Deploy a contract from installed Wasm bytecode
-hide_table_of_contents: true
-description: Deploy an instance of a compiled contract that is already installed on the network
+title: Deploy a contract from uploaded Wasm bytecode
+description: Deploy an instance of a compiled contract that has already been uploaded on the network
 ---
 
-Stub file: the real file is generated in build time by `pnpm stellar-cli:build`.
+To deploy an instance of a compiled smart contract that has already been uploaded onto the Stellar network, use the `stellar contract deploy` command:
+
+```bash
+stellar contract deploy \
+    --source S... \
+    --network testnet \
+    --wasm-hash <hex-encoded-wasm-hash> \
+    --alias <alias>
+```
+
+<Tip>
+
+Optionally assign an alias by replacing `<alias>` with your desired alias name for the contract. The alias is a locally stored mapping to the contract address, and can be used in other stellar-cli commands in place of the address.
+
+</Tip>
diff --git a/docs/tools/cli/cookbook/deploy-stellar-asset-contract.mdx b/docs/tools/cli/cookbook/deploy-stellar-asset-contract.mdx
index ab723afc7..eb1a6dd65 100644
--- a/docs/tools/cli/cookbook/deploy-stellar-asset-contract.mdx
+++ b/docs/tools/cli/cookbook/deploy-stellar-asset-contract.mdx
@@ -1,7 +1,53 @@
 ---
 title: Deploy the Stellar Asset Contract for a Stellar asset
-hide_table_of_contents: true
 description: Deploy an SAC for a Stellar asset so that it can interact with smart contracts
 ---
 
-Stub file: the real file is generated in build time by `pnpm stellar-cli:build`.
+The Stellar CLI can deploy a [Stellar Asset Contract] for a Stellar asset so that any Stellar smart contract can interact with the asset.
+
+Every Stellar asset has reserved a contract that anyone can deploy. Once deployed any contract can interact with that asset by holding a balance of the asset, receiving the asset, or sending the asset.
+
+Deploying the Stellar Asset Contract for a Stellar asset enables that asset for use in smart contracts.
+
+The Stellar Asset Contract can be deployed for any possible Stellar asset, either assets already in use on Stellar or assets that have never seen any activity. This means that the issuer doesn't need to have been created, and no one needs to be yet holding the asset on Stellar.
+
+To perform the deploy, use the following command:
+
+```bash cookbooktest.ignore
+stellar contract asset deploy \
+    --source S... \
+    --network testnet \
+    --asset USDC:GCYEIQEWOCTTSA72VPZ6LYIZIK4W4KNGJR72UADIXUXG45VDFRVCQTYE
+```
+
+The `asset` argument corresponds to the symbol and it's issuer address, which is how assets are identified on Stellar.
+
+The same can be done for the native [Lumens] asset:
+
+```bash cookbooktest.fail cookbooktest.stderr="contract already exists"
+stellar contract asset deploy \
+    --source S... \
+    --network testnet \
+    --asset native
+```
+
+<Note>
+
+Deploying the native asset will fail on testnet or mainnet as a Stellar Asset Contract already exists.
+
+</Note>
+
+For any asset, the contract address can be fetched with:
+
+```bash
+stellar contract id asset \
+    --network testnet \
+    --asset native
+```
+
+[stellar asset contract]: ../../../tokens/stellar-asset-contract
+[lumens]: ../../../learn/fundamentals/lumens
+[sep-41]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0041.md
+[`soroban_sdk::token`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/token/
+[`token::tokenclient`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/token/struct.TokenClient.html
+[`token::stellarassetclient`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/token/struct.StellarAssetClient.html
diff --git a/docs/tools/cli/cookbook/extend-contract-instance.mdx b/docs/tools/cli/cookbook/extend-contract-instance.mdx
index eaf8e82ec..935243f13 100644
--- a/docs/tools/cli/cookbook/extend-contract-instance.mdx
+++ b/docs/tools/cli/cookbook/extend-contract-instance.mdx
@@ -1,7 +1,23 @@
 ---
 title: Extend a deployed contract instance's TTL
-hide_table_of_contents: true
 description: Use the CLI to extend the time to live (TTL) of a contract instance
 ---
 
-Stub file: the real file is generated in build time by `pnpm stellar-cli:build`.
+You can use the Stellar CLI to extend the TTL of a contract instance like so:
+
+```bash
+stellar contract extend \
+    --source S... \
+    --network testnet \
+    --id C... \
+    --ledgers-to-extend 535679 \
+    --durability persistent
+```
+
+This example uses 535,679 ledgers as the new archival TTL. This is the maximum allowable value for this argument on the CLI. This corresponds to roughly 30 days (averaging 5 second ledger close times).
+
+When you extend a contract instance, this includes:
+
+- the contract instance itself
+- any `env.storage().instance()` entries in the contract
+- the contract's Wasm code
diff --git a/docs/tools/cli/cookbook/extend-contract-storage.mdx b/docs/tools/cli/cookbook/extend-contract-storage.mdx
index b395619bc..a7cf815d3 100644
--- a/docs/tools/cli/cookbook/extend-contract-storage.mdx
+++ b/docs/tools/cli/cookbook/extend-contract-storage.mdx
@@ -1,7 +1,36 @@
 ---
 title: Extend a deployed contract's storage entry TTL
-hide_table_of_contents: true
 description: Use the CLI to extend the time to live (TTL) of a contract's persistent storage entry
 ---
 
-Stub file: the real file is generated in build time by `pnpm stellar-cli:build`.
+You can use the Stellar CLI to extend the TTL of a contract's persistent storage entry. For a storage entry that uses a simple `Symbol` as its storage key, you can run a command like so:
+
+```bash
+stellar contract extend \
+    --source S... \
+    --network testnet \
+    --id C... \
+    --key COUNTER \
+    --ledgers-to-extend 535679 \
+    --durability persistent
+```
+
+This example uses 535,679 ledgers as the new archival TTL. This is the maximum allowable value for this argument on the CLI. This corresponds to roughly 30 days (averaging 5 second ledger close times).
+
+If your storage entry uses a more advanced storage key, such as `Balance(Address)` in a token contract, you'll need to provide the key in a base64-encoded XDR form:
+
+```bash
+stellar contract extend \
+    --source S... \
+    --network testnet \
+    --id C... \
+    --key-xdr AAAABgAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAAA4AAAAHQmFsYW5jZQAAAAAB \
+    --ledgers-to-extend 535679 \
+    --durability persistent
+```
+
+<Info>
+
+Be sure to check out our [guide on creating XDR ledger keys](../../../build/guides/rpc/generate-ledger-keys-python) for help generating them.
+
+</Info>
diff --git a/docs/tools/cli/cookbook/extend-contract-wasm.mdx b/docs/tools/cli/cookbook/extend-contract-wasm.mdx
index 254c2cdb8..9a372b314 100644
--- a/docs/tools/cli/cookbook/extend-contract-wasm.mdx
+++ b/docs/tools/cli/cookbook/extend-contract-wasm.mdx
@@ -1,7 +1,34 @@
 ---
 title: Extend a deployed contract's Wasm code TTL
-hide_table_of_contents: true
 description: Use Stellar CLI to extend contract's Wasm bytecode TTL, with or without local binary
 ---
 
-Stub file: the real file is generated in build time by `pnpm stellar-cli:build`.
+You can use the Stellar CLI to extend the TTL of a contract's Wasm bytecode. This can be done in two forms: if you do or do not have the compiled contract locally. If you do have the compiled binary on your local machine:
+
+```bash
+stellar contract extend \
+    --source S... \
+    --network testnet \
+    --wasm ../relative/path/to/soroban_contract.wasm \
+    --ledgers-to-extend 535679 \
+    --durability persistent
+```
+
+This example uses 535,679 ledgers as the new archival TTL. This is the maximum allowable value for this argument on the CLI. This corresponds to roughly 30 days (averaging 5 second ledger close times).
+
+If you do not have the compiled binary on your local machine, you can still use the CLI to extend the bytecode TTL. You'll need to know the Wasm hash of the installed contract code:
+
+```bash
+stellar contract extend \
+    --source S... \
+    --network testnet \
+    --wasm-hash <hex-encoded-wasm-hash> \
+    --ledgers-to-extend 535679 \
+    --durability persistent
+```
+
+<Info>
+
+You can learn more about finding the correct Wasm hash for a contract instance [here (JavaScript)](../../../build/guides/rpc/retrieve-contract-code-js) and [here (Python)](../../../build/guides/rpc/retrieve-contract-code-python).
+
+</Info>
diff --git a/docs/tools/cli/cookbook/index.mdx b/docs/tools/cli/cookbook/index.mdx
new file mode 100644
index 000000000..4039fb6ed
--- /dev/null
+++ b/docs/tools/cli/cookbook/index.mdx
@@ -0,0 +1,6 @@
+---
+title: Cookbook
+description: "Guides that will help you use the Stellar CLI."
+---
+
+If you do not have the CLI yet, see [Install the CLI](../install-cli).
diff --git a/docs/tools/cli/cookbook/payments-and-assets.mdx b/docs/tools/cli/cookbook/payments-and-assets.mdx
index 36689d87e..131e1db55 100644
--- a/docs/tools/cli/cookbook/payments-and-assets.mdx
+++ b/docs/tools/cli/cookbook/payments-and-assets.mdx
@@ -1,7 +1,60 @@
 ---
 title: Payments and Assets
-hide_table_of_contents: true
 description: Send XLM, stellar classic, or a soroban asset using the Stellar CLI
 ---
 
-Stub file: the real file is generated in build time by `pnpm stellar-cli:build`.
+To send payments and work with assets using the Stellar CLI, follow these steps:
+
+1. Set your preferred network. For this guide, we will use `testnet`. A list of available networks can be found [here](/docs/networks)
+
+```bash
+stellar network use testnet
+```
+
+2. Fund the accounts:
+
+```bash
+stellar keys generate alice
+```
+
+```bash
+stellar keys fund alice
+```
+
+```bash
+stellar keys generate bob
+```
+
+```bash
+stellar keys fund bob
+```
+
+3. Obtain the stellar asset contract ID:
+
+```bash
+stellar contract id asset --asset native
+```
+
+4. Get Bob's public key:
+
+```bash
+stellar keys address bob
+```
+
+5. Send 100 XLM from Alice to Bob:
+
+```bash
+stellar keys use alice
+```
+
+```bash
+stellar contract invoke --id <ASSET_CONTRACT_ID> -- transfer --to bob --from alice --amount 100
+```
+
+6. Check account balance:
+
+```bash
+stellar contract invoke --id <ASSET_CONTRACT_ID> -- balance --id bob
+```
+
+For more information on the functions available to the stellar asset contract, see the [token interface code](../../../tokens/token-interface#code)
diff --git a/docs/tools/cli/cookbook/restore-contract-instance.mdx b/docs/tools/cli/cookbook/restore-contract-instance.mdx
index 5ca9f0717..172e64217 100644
--- a/docs/tools/cli/cookbook/restore-contract-instance.mdx
+++ b/docs/tools/cli/cookbook/restore-contract-instance.mdx
@@ -1,7 +1,14 @@
 ---
 title: Restore an archived contract using the Stellar CLI
-hide_table_of_contents: true
 description: Restore an archived contract instance using the Stellar CLI
 ---
 
-Stub file: the real file is generated in build time by `pnpm stellar-cli:build`.
+If your contract instance has been archived, it can easily be restored using the Stellar CLI.
+
+```bash
+stellar contract restore \
+    --source S... \
+    --network testnet \
+    --id C... \
+    --durability persistent
+```
diff --git a/docs/tools/cli/cookbook/restore-contract-storage.mdx b/docs/tools/cli/cookbook/restore-contract-storage.mdx
index 898d9c56f..3f2f8eecb 100644
--- a/docs/tools/cli/cookbook/restore-contract-storage.mdx
+++ b/docs/tools/cli/cookbook/restore-contract-storage.mdx
@@ -1,7 +1,32 @@
 ---
 title: Restore archived contract data using the Stellar CLI
-hide_table_of_contents: true
 description: Restore archived contract storage entries using Stellar CLI
 ---
 
-Stub file: the real file is generated in build time by `pnpm stellar-cli:build`.
+If a contract's persistent storage entry has been archived, you can restore it using the Stellar CLI. For a storage entry that uses a simple `Symbol` as its storage key, you can run a command like so:
+
+```bash
+stellar contract restore \
+    --source S... \
+    --network testnet \
+    --id C... \
+    --key COUNTER \
+    --durability persistent
+```
+
+If your storage entry uses a more advanced storage key, such as `Balance(Address)` in a token contract, you'll need to provide the key in a base64-encoded XDR form:
+
+```bash
+stellar contract restore \
+    --source S... \
+    --network testnet \
+    --id C... \
+    --key-xdr AAAABgAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAAA4AAAAHQmFsYW5jZQAAAAAB \
+    --durability persistent
+```
+
+<Info>
+
+Be sure to check out our [guide on creating XDR ledger keys](../../../build/guides/rpc/generate-ledger-keys-python) for help generating them.
+
+</Info>
diff --git a/docs/tools/cli/cookbook/stellar-keys.mdx b/docs/tools/cli/cookbook/stellar-keys.mdx
index b09ffc5c6..64bfc43e7 100644
--- a/docs/tools/cli/cookbook/stellar-keys.mdx
+++ b/docs/tools/cli/cookbook/stellar-keys.mdx
@@ -1,7 +1,122 @@
 ---
 title: Stellar Keys
-hide_table_of_contents: true
-description: Manage Stellar keys
+description: Manage stellar keys
 ---
 
-Stub file: the real file is generated in build time by `pnpm stellar-cli:build`.
+This guide walks you through generating, inspecting, and removing a Stellar identity using the CLI.
+
+### 1. Generate a New Identity
+
+Run the following command to create a new keypair and save it under the alias named `carol`:
+
+```bash
+stellar keys generate carol
+```
+
+Output:
+
+```
+✅ Key saved with alias carol in ".config/soroban/identity/carol.toml"
+```
+
+The CLI stores this identity in a TOML file.
+
+### 2. Verify the Identity File
+
+Navigate to the configuration directory and list the contents:
+
+```bash cookbooktest.ignore
+cd .config/soroban/identity && ls
+```
+
+Output:
+
+```
+carol.toml
+```
+
+The file carol.toml contains the seed phrase for your identity.
+
+### 3. View the Seed Phrase
+
+```bash cookbooktest.ignore
+cat carol.toml
+```
+
+Output:
+
+```
+seed_phrase = "patrol clean public grocery roof aim have valve cherry dismiss lunar tail duty license capable little version banana amount often cover dice couple party"
+```
+
+<Warning>
+
+Note: The seed phrase is sensitive information. Handle it with care and never expose it publicly.
+
+</Warning>
+
+### 4. Derive the Secret Key
+
+To display the secret key for the carol identity:
+
+```bash
+stellar keys secret carol
+```
+
+Output:
+
+```
+SCJP663VYFZPYN75H2DYJA3FYUBP5UR23HZ4ZDHDMDY6TXVYUYMWNKTI
+```
+
+<Warning>
+
+Note: The secret key is sensitive information. Handle it with care and never expose it publicly.
+
+</Warning>
+
+### 5. Derive the Public Key
+
+To display the corresponding public key for the carol identity:
+
+```bash
+stellar keys public-key carol
+```
+
+Output:
+
+```
+GD3BFFX7DTNJAGDVVM5RYGGQQNURZTH4VSBLWF55YXY3L6T2WWZK57EI
+```
+
+This is the public address of your key.
+
+### 6. Fund this account
+
+```bash
+stellar keys fund carol
+```
+
+Output:
+
+```
+✅ Account carol funded on "Test SDF Network ; September 2015"
+```
+
+You can also fund the account while creating the key by using `stellar keys generate --fund`.
+
+### 7. Remove the Identity
+
+When you no longer need this identity, remove it using:
+
+```bash
+stellar keys rm carol --force
+```
+
+Output:
+
+```
+ℹ️  Removing the key's cli config file
+```
+
+At this point, the identity file carol.toml is deleted, and the alias is no longer available in the CLI.
diff --git a/docs/tools/cli/cookbook/tx-new-create-claimable-balance.mdx b/docs/tools/cli/cookbook/tx-new-create-claimable-balance.mdx
index eff2879f8..07d9bf50d 100644
--- a/docs/tools/cli/cookbook/tx-new-create-claimable-balance.mdx
+++ b/docs/tools/cli/cookbook/tx-new-create-claimable-balance.mdx
@@ -1,7 +1,246 @@
 ---
 title: Create Claimable Balance
-hide_table_of_contents: true
 description: Create claimable balances with various claim predicates using the Stellar CLI
 ---
 
-Stub file: the real file is generated in build time by `pnpm stellar-cli:build`.
+Claimable balances allow you to send payments that can be claimed by the recipient based on specific conditions. This is useful for escrow-like functionality, conditional payments, or time-locked transfers.
+
+## Setup
+
+For the following examples we will use these accounts:
+
+```bash
+stellar network use testnet
+```
+
+```bash
+stellar keys generate --fund alice
+```
+
+```bash
+stellar keys generate bob --fund
+```
+
+```bash
+stellar keys generate charlie --fund
+```
+
+## Basic Examples
+
+### Unconditional Claimable Balance
+
+Create a claimable balance that can be claimed immediately by the recipient:
+
+```bash
+stellar tx new create-claimable-balance \
+  --source alice \
+  --amount 50_000_000 \
+  --asset native \
+  --claimant bob
+```
+
+You can also explicitly specify unconditional:
+
+```bash
+stellar tx new create-claimable-balance \
+  --source alice \
+  --amount 50_000_000 \
+  --asset native \
+  --claimant 'bob:"unconditional"'
+```
+
+### Multiple Claimants
+
+Create a claimable balance that can be claimed by any of multiple recipients:
+
+```bash
+stellar tx new create-claimable-balance \
+  --source alice \
+  --amount 75_000_000 \
+  --asset native \
+  --claimant bob \
+  --claimant charlie
+```
+
+## Time-Based Predicates
+
+### Before Absolute Time
+
+Create a claimable balance that must be claimed before a specific date:
+
+```bash
+stellar tx new create-claimable-balance \
+  --source alice \
+  --amount 30_000_000 \
+  --asset native \
+  --claimant 'bob:{"before_absolute_time":"1735689599"}'
+```
+
+### Before Relative Time
+
+Create a claimable balance that must be claimed within 1 hour (3600 seconds) from creation:
+
+```bash
+stellar tx new create-claimable-balance \
+  --source alice \
+  --amount 25_000_000 \
+  --asset native \
+  --claimant 'bob:{"before_relative_time":"3600"}'
+```
+
+## Logical Predicates
+
+### Not Predicate
+
+Create a claimable balance that can be claimed after a certain time (NOT before relative time):
+
+```bash
+stellar tx new create-claimable-balance \
+  --source alice \
+  --amount 40_000_000 \
+  --asset native \
+  --claimant 'bob:{"not":{"before_relative_time":"7200"}}'
+```
+
+This means: "Can be claimed, but NOT before 2 hours have passed" (effectively: can be claimed after 2 hours).
+
+### And Predicate
+
+Create a claimable balance with multiple conditions that must ALL be true:
+
+```bash
+stellar tx new create-claimable-balance \
+  --source alice \
+  --amount 60_000_000 \
+  --asset native \
+  --claimant 'bob:{"and":[{"before_absolute_time":"1735689599"},{"not":{"before_relative_time":"86400"}}]}'
+```
+
+This means: "Can be claimed before Dec 31, 2024 AND after 1 day has passed".
+
+### Or Predicate
+
+Create a claimable balance where either condition can be true:
+
+```bash
+stellar tx new create-claimable-balance \
+  --source alice \
+  --amount 35_000_000 \
+  --asset native \
+  --claimant 'bob:{"or":[{"before_relative_time":"3600"},{"not":{"before_absolute_time":"1717200000"}}]}'
+```
+
+This means: "Can be claimed within 1 hour OR after June 1, 2024".
+
+## Complex Examples
+
+### Mixed Claimants with Different Predicates
+
+Create a claimable balance with multiple claimants having different claim conditions:
+
+```bash
+stellar tx new create-claimable-balance \
+  --source alice \
+  --amount 100_000_000 \
+  --asset native \
+  --claimant 'bob:{"before_relative_time":"3600"}' \
+  --claimant 'charlie:{"not":{"before_relative_time":"86400"}}'
+```
+
+This creates a balance where:
+
+- Bob can claim within 1 hour
+- Charlie can claim after 1 day has passed
+
+### Escrow-Style Payment
+
+Create an escrow where the recipient has 30 days to claim, otherwise it returns to sender:
+
+```bash
+stellar tx new create-claimable-balance \
+  --source alice \
+  --amount 200_000_000 \
+  --asset native \
+  --claimant 'bob:{"before_relative_time":"2592000"}' \
+  --claimant 'alice:{"not":{"before_relative_time":"2592000"}}'
+```
+
+This means:
+
+- Bob can claim within 30 days
+- Alice can reclaim after 30 days if Bob hasn't claimed
+
+### Custom Asset Claimable Balance
+
+Create a claimable balance for a custom asset:
+
+```bash cookbooktest.ignore
+stellar tx new create-claimable-balance \
+  --source alice \
+  --amount 1000_000_000 \
+  --asset USDC:GBUG7QTBTT47XVDVE6RZYWRUZBPLOIO57INE6LYZDMIXMMDCREQRUQKI \
+  --claimant 'bob:{"before_absolute_time":"1735689599"}'
+```
+
+## Understanding Predicates
+
+**Note**: Predicates must be valid JSON, so you must use proper quoting and escaping.
+
+### Predicate Types
+
+| Type | Description | Example |
+| --- | --- | --- |
+| `unconditional` | Can be claimed anytime | `"unconditional"` |
+| `before_absolute_time` | Must claim before specific timestamp | `{"before_absolute_time":"1735689599"}` |
+| `before_relative_time` | Must claim within X seconds from creation | `{"before_relative_time":"3600"}` |
+| `not` | Negates another predicate | `{"not":{...}}` |
+| `and` | Both predicates must be true | `{"and":[{...},{...}]}` |
+| `or` | Either predicate can be true | `{"or":[{...},{...}]}` |
+
+### Time Format Notes
+
+- **Absolute times**: Use Unix timestamps (seconds since epoch)
+- **Relative times**: Seconds from claimable balance creation time
+- **Timestamps**: Must be in the future when creating the balance
+
+## Common Use Cases
+
+### 1. Simple Payment with Deadline
+
+```bash
+# Bob has 7 days to claim
+stellar tx new create-claimable-balance \
+  --source alice \
+  --amount 50_000_000 \
+  --claimant 'bob:{"before_relative_time":"604800"}'
+```
+
+### 2. Delayed Payment
+
+```bash
+# Bob can only claim after 1 day
+stellar tx new create-claimable-balance \
+  --source alice \
+  --amount 100_000_000 \
+  --claimant 'bob:{"not":{"before_relative_time":"86400"}}'
+```
+
+### 3. Emergency Fund
+
+```bash
+# Bob can claim immediately, but if he doesn't claim within 48 hours, Alice can reclaim
+stellar tx new create-claimable-balance \
+  --source alice \
+  --amount 500_000_000 \
+  --claimant 'bob:{"before_relative_time":"172800"}' \
+  --claimant 'alice:{"not":{"before_relative_time":"172800"}}'
+```
+
+## Notes
+
+- `--amount`: Amount in stroops (1 XLM = 10,000,000 stroops)
+- `--asset`: Use "native" for XLM or "CODE:ISSUER" format for other assets
+- `--claimant`: Account with optional predicate (can be specified multiple times)
+- Predicates are evaluated when the claimable balance is claimed, not when created
+- `And` and `Or` predicates must have exactly 2 sub-predicates
+- Complex predicates can be nested to create sophisticated claim conditions
diff --git a/docs/tools/cli/cookbook/tx-new.mdx b/docs/tools/cli/cookbook/tx-new.mdx
index a9b0b6230..8cc59aba9 100644
--- a/docs/tools/cli/cookbook/tx-new.mdx
+++ b/docs/tools/cli/cookbook/tx-new.mdx
@@ -1,7 +1,187 @@
 ---
 title: tx Commands
-hide_table_of_contents: true
 description: Create stellar transactions using the Stellar CLI
 ---
 
-Stub file: the real file is generated in build time by `pnpm stellar-cli:build`.
+So far the examples of the CLI interacting with the blockchain have been through the `contract` command. Uploading contracts, deploying contracts, and invoking them. Each of these are different types of transactions, which must be signed and submitted to the network (and in the case of contract related transactions simulated first).
+
+Technically these three are different operations, of which a transaction can contain up to 100 operations. However, in the case of contract related operations a transaction is limited to just one.
+
+So for all other transactions the CLI provides the `tx` subcommands. These are:
+
+- `new`
+- `sign`
+- `send`
+- `simulate`
+
+## `tx new`
+
+For the following examples we will use the following accounts:
+
+```sh
+stellar keys generate --fund alice --network testnet
+stellar keys generate bob
+# You can add a public key to the keys
+stellar keys add --public-key GBUG7QTBTT47XVDVE6RZYWRUZBPLOIO57INE6LYZDMIXMMDCREQRUQKI charlie
+## and use testnet
+stellar network use testnet
+```
+
+### Create Account
+
+Creates and funds a new Stellar account. Above `alice` was funded by [friendbot](/docs/networks#friendbot). However, `bob` and `charlie` were not. So we can use the `create-account` command to fund them.
+
+`bob` will receive 10 XLM and `charlie` will get 1 XLM.
+
+```sh
+stellar tx new create-account \
+  --source alice \
+  --destination bob \
+  --starting-balance 100_000_000
+
+stellar tx new create-account \
+  --source alice \
+  --destination charlie \
+  --starting-balance 10_000_000
+```
+
+Notes:
+
+- `--starting-balance`: Initial balance in stroops to fund the account with (1 XLM = 10,000,000 stroops)
+
+### Payment
+
+`bob` feels bad that `charlie` only got 1 XLM, so they will send 4 more XLM to `charlie`.
+
+```sh
+stellar tx new payment \
+  --source bob \
+  --destination charlie \
+  --asset native \
+  --amount 40_000_000
+```
+
+Notes:
+
+- `--asset`: The asset to send - either "native" for XLM or "CODE:ISSUER" format for other assets
+
+### Bump Sequence
+
+Bump an account's sequence number forward:
+
+```sh
+stellar tx new bump-sequence \
+  --source alice \
+  --bump-to 123450
+```
+
+### Account Merge
+
+Merge one account into another, transferring all XLM.
+
+`bob` decides to continue spreading the wealth and merges their account into `charlie`'s.
+
+```sh
+stellar tx new account-merge \
+  --source bob \
+  --account charlie
+```
+
+Notes:
+
+- `--source`: The account to remove from the ledger, thus this is its final tranaction
+
+### Set Trustline Flags
+
+Modify authorization flags on a trustline:
+
+```sh
+stellar tx new set-trustline-flags \
+  --source alice \
+  --asset USDC:GBUG7QTBTT47XVDVE6RZYWRUZBPLOIO57INE6LYZDMIXMMDCREQRUQKI \
+  --trustor charlie \
+  --set-authorize \
+  --set-authorize-to-maintain-liabilities \
+  --set-trustline-clawback-enabled
+```
+
+Arguments:
+
+- `--source`: The issuing account setting the flags (must be the asset issuer)
+- `--asset`: The asset in CODE:ISSUER format
+- `--trustor`: The account whose trustline flags to modify
+- `--set-authorize`: Enable full authorization
+- `--set-authorize-to-maintain-liabilities`: Enable limited authorization
+- `--set-trustline-clawback-enabled`: Enable clawback for this trustline
+- `--clear-*`: Corresponding clear flags to remove each setting
+
+### Set Options
+
+Configure account settings:
+
+```sh
+stellar tx new set-options \
+  --source alice \
+  --inflation-dest GBUG7QTBTT47XVDVE6RZYWRUZBPLOIO57INE6LYZDMIXMMDCREQRUQKI \
+  --home-domain "example.com" \
+  --master-weight 100 \
+  --med-threshold 100 \
+  --low-threshold 100 \
+  --high-threshold 100 \
+  --signer GBXSGN5GX4PZOSBHB4JJF67CEGSGT7DGBGGUGWXI4WOQMQEA4SFV2HTJ \
+  --signer-weight 1 \
+  --set-required \
+  --set-revocable \
+  --set-clawback-enabled \
+  --set-immutable
+```
+
+Notes:
+
+- `--source`: Account to modify settings for
+- `--inflation-dest`: Set inflation destination account
+- `--home-domain`: Set home domain for federation/compliance
+- `--master-weight`: Weight of the account's master key (0-255)
+- `--low-threshold`: Weight threshold for low security operations
+- `--med-threshold`: Weight threshold for medium security operations
+- `--high-threshold`: Weight threshold for high security operations
+- `--signer`: Add a new signer public key
+- `--signer-weight`: Weight for the new signer (0 removes the signer)
+- `--set-required`: Enable requiring authorization for new trustlines
+- `--set-revocable`: Enable revoking of trustlines
+- `--set-clawback-enabled`: Enable clawback for asset issuing account
+- `--set-immutable`: Make account settings immutable
+- `--clear-*`: Corresponding clear flags to remove each setting
+
+### Change Trust
+
+Create or modify a trustline:
+
+```sh
+stellar tx new change-trust \
+  --source alice \
+  --line USDC:ISSUER \
+  --limit 100000000
+```
+
+Arguments:
+
+- `--source`: Account creating/modifying the trustline
+- `--line`: Asset to create trustline for in CODE:ISSUER format
+- `--limit`: Maximum amount that can be held (0 removes trustline)
+
+### Manage Data
+
+Manage account data entries:
+
+```sh
+stellar tx new manage-data \
+  --source alice \
+  --data-name config \
+  --data-value 7465737476616c7565 # hex encoded
+```
+
+Notes:
+
+- `--data-name`: Name of the data entry (up to 64 bytes)
+- `--data-value`: Hex encoded value to store (up to 64 bytes, omit to delete)
diff --git a/docs/tools/cli/cookbook/tx-op-add.mdx b/docs/tools/cli/cookbook/tx-op-add.mdx
index ac63be656..15c7eee20 100644
--- a/docs/tools/cli/cookbook/tx-op-add.mdx
+++ b/docs/tools/cli/cookbook/tx-op-add.mdx
@@ -1,7 +1,49 @@
 ---
 title: tx op add
-hide_table_of_contents: true
 description: Create stellar transactions using the Stellar CLI
 ---
 
-Stub file: the real file is generated in build time by `pnpm stellar-cli:build`.
+As seen before you can use pipes to pass a transaction envelope between commands. Before we have only been looking at transactions with one operation, however, as mentioned there can be up to 100 operations in a single transaction.
+
+To add an operation to a transaction you can use the `tx op add` command. This command takes the transaction envolope from the previous command and adds an operation to it.
+
+Let's consider a more complicated example. Consider issuing an asset, here `USDC` with the requirement that only the issuer can transfer funds to the distrubtor.
+
+```sh
+
+stellar keys generate --fund issuer
+stellar keys generate --fund distributor
+
+ISSUER_PK=$(stellar keys address issuer)
+
+ASSET="USDC:$ISSUER_PK"
+
+# Issue the asset by setting its options, establishing a trustline, and
+# transferring the smallest amount possible to the distributor. Then
+# deauthorize the distributor so that people can only send Claimable Balances,
+# rather than transferring assets directly.
+
+# first the issuer sets the options for being able to clawback and revoke the asset
+stellar tx new set-options --inclusion-fee 1000 --source issuer --set-clawback-enabled --set-revocable --build-only \
+# next the distributor establishes a trustline with the asset. Note that here the distributor the source account for the operation, not the issuer
+| stellar tx op add change-trust --op-source distributor --line $ASSET \
+# then the issuer sends the smallest amount possible to the distributor
+| stellar tx op add payment --destination distributor --asset $ASSET --amount 1 \
+# finally the issuer deauthorizes the distributor from being able to send the asset
+| stellar tx op add set-trustline-flags --asset $ASSET --trustor distributor --clear-authorize \
+# Then both accounts need to sign the transaction
+| stellar tx sign --sign-with-key issuer \
+| stellar tx sign --sign-with-key distributor \
+| stellar tx send
+
+# Next is an example of sandwiching an operation. That is giving permission in one operation, preforming the operation, and then removing the permission in a third operation.
+# Here is an example of minting new assets to the distributor with a sandwich transaction
+# First authorize the distributor to receive the asset
+stellar tx new set-trustline-flags --inclusion-fee 1000 --build-only --source issuer --asset $ASSET --trustor $distributor_PK --set-authorize \
+# Then mint the asset to the distributor
+| stellar tx op add payment --destination distributor --asset $ASSET --amount 1_000_000_000_000 \
+# Finally remove the authorization
+| stellar tx op add set-trustline-flags --asset $ASSET --trustor distributor --clear-authorize \
+| stellar tx sign --sign-with-key issuer \
+| stellar tx send
+```
diff --git a/docs/tools/cli/cookbook/tx-sign.mdx b/docs/tools/cli/cookbook/tx-sign.mdx
index fef2999fd..d47032261 100644
--- a/docs/tools/cli/cookbook/tx-sign.mdx
+++ b/docs/tools/cli/cookbook/tx-sign.mdx
@@ -1,7 +1,76 @@
 ---
 title: tx sign and tx send
-hide_table_of_contents: true
 description: Create stellar transactions using the Stellar CLI
 ---
 
-Stub file: the real file is generated in build time by `pnpm stellar-cli:build`.
+The previous examples of using `tx new` showed how to create transactions. However, these transactions were immediately ready to be signed and submitted to the network.
+
+To avoid this each of the subcommands has the `--build-only` argument, which as the name suggests only builds the transaction and prints the transaction envelope.
+
+## `tx sign`
+
+Let's return to the first example of creating `bob`s account:
+
+```sh
+stellar tx new create-account \
+  --source alice \
+  --destination bob \
+  --starting-balance 100_000_000 \
+  --build-only
+```
+
+would output something like:
+
+```sh
+AAAAAgAAAADwSUp9CwmVlPN40mKX1I1j39y6DmYc36QS1aK2x6eYVQAAAGQAEcMsAAAAAQAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAACTMkzn1TwPo8SIhnKvnyuv9K2/aWjpX9NTYfyiA7vXaAAAAAAX14QAAAAAAAAAAAA==
+```
+
+You can inspect it with [stellar lab!](https://lab.stellar.org/xdr/view?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;&xdr$blob=AAAAAgAAAADwSUp9CwmVlPN40mKX1I1j39y6DmYc36QS1aK2x6eYVQAAAGQAEcMsAAAAAQAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAACTMkzn1TwPo8SIhnKvnyuv9K2//aWjpX9NTYfyiA7vXaAAAAAAX14QAAAAAAAAAAAA==;;) Where you can also sign and send the transaction.
+
+However, you can also sign the transaction with the `tx sign` command. To do this you can pipe the output of the `tx new` command to the `tx sign` command:
+
+```sh
+stellar tx new create-account \
+    --source alice \
+    --destination bob \
+    --starting-balance 100_000_000 \
+    --build-only \
+  | stellar tx sign --sign-with-key alice
+```
+
+This should output something like:
+
+```sh
+AAAAAgAAAAAebE8Ewg9uzvHRAl+UmvP0kixsyp238kkz0zOy+91FeQAAAGQAFJk4AAAAAQAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAPpiy8qfSw4pLYG/Bav78FfrFWlte7YQfiHX41DQ+nGWAAAAAAX14QAAAAAAAAAAAfvdRXkAAABA4kjz9Yeub/IrzogjMr57U4nYwCmSJAXxIW+7Xyjan/UweIByF7uEhVS4gEl1N138uq07njVxZwRMtugWyMleCg==
+```
+
+You can again [view it in lab and see that there is now a signature attached to the transaction envelope](https://lab.stellar.org/xdr/view?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;&xdr$blob=AAAAAgAAAAAebE8Ewg9uzvHRAl+UmvP0kixsyp238kkz0zOy+91FeQAAAGQAFJk4AAAAAQAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAPpiy8qfSw4pLYG//Bav78FfrFWlte7YQfiHX41DQ+nGWAAAAAAX14QAAAAAAAAAAAfvdRXkAAABA4kjz9Yeub//IrzogjMr57U4nYwCmSJAXxIW+7Xyjan//UweIByF7uEhVS4gEl1N138uq07njVxZwRMtugWyMleCg==;;).
+
+<Tip>
+
+Or sign with lab! Though currently you must send it from lab and cannot return to the CLI (a work in progress!).
+
+```sh
+stellar tx new create-account \
+    --source alice \
+    --destination bob \
+    --starting-balance 100_000_000 \
+    --build-only \
+  | stellar tx sign --sign-with-lab
+```
+
+</Tip>
+
+## `tx send`
+
+Finally, to submit the transaction to the network you can use the `tx send` command. This command will submit the transaction to the network.
+
+```sh
+stellar tx new create-account \
+    --source alice \
+    --destination bob \
+    --starting-balance 100_000_000 \
+    --build-only \
+  | stellar tx sign --sign-with-key alice \
+  | stellar tx send
+```
diff --git a/docs/tools/cli/cookbook/upload-deploy.mdx b/docs/tools/cli/cookbook/upload-deploy.mdx
index f22801972..e0558c4ca 100644
--- a/docs/tools/cli/cookbook/upload-deploy.mdx
+++ b/docs/tools/cli/cookbook/upload-deploy.mdx
@@ -1,7 +1,13 @@
 ---
 title: Upload and deploy a smart contract
-hide_table_of_contents: true
 description: Combine the upload and deploy commands in the Stellar CLI to accomplish both tasks
 ---
 
-Stub file: the real file is generated in build time by `pnpm stellar-cli:build`.
+You can combine the `upload` and `deploy` commands of the Stellar CLI to accomplish both tasks:
+
+```bash
+stellar contract deploy \
+    --source S... \
+    --network testnet \
+    --wasm ../relative/path/to/soroban_contract.wasm
+```
diff --git a/docs/tools/cli/cookbook/upload-wasm.mdx b/docs/tools/cli/cookbook/upload-wasm.mdx
index 2790a3da7..87cb78a76 100644
--- a/docs/tools/cli/cookbook/upload-wasm.mdx
+++ b/docs/tools/cli/cookbook/upload-wasm.mdx
@@ -1,7 +1,19 @@
 ---
 title: Upload Wasm bytecode
-hide_table_of_contents: true
 description: Use the Stellar CLI to upload a compiled smart contract on the ledger
 ---
 
-Stub file: the real file is generated in build time by `pnpm stellar-cli:build`.
+To use the Stellar CLI to upload a compiled smart contract on the ledger, use the `stellar contract upload` command:
+
+```bash
+stellar contract upload \
+    --source S... \
+    --network testnet \
+    --wasm ../relative/path/to/soroban_contract.wasm
+```
+
+<Note>
+
+Note this command will return the hash ID of the Wasm bytecode, rather than an address for a contract instance.
+
+</Note>
diff --git a/docs/tools/cli/index.mdx b/docs/tools/cli/index.mdx
new file mode 100644
index 000000000..76c2f57c6
--- /dev/null
+++ b/docs/tools/cli/index.mdx
@@ -0,0 +1,21 @@
+---
+title: Stellar CLI
+description: The CLI for interacting with the Stellar network
+---
+
+The command line interface to Soroban smart contracts. It allows you to build, deploy, and interact with smart contracts; configure identities; generate key pairs; manage networks; and more.
+
+## Install
+
+Install the latest release on macOS, Linux or WSL with the install script:
+
+```sh
+curl -fsSL https://github.com/stellar/stellar-cli/raw/main/install.sh | sh
+```
+
+For Homebrew, winget, cargo, GitHub Actions and shell autocomplete, see [Install the CLI](./install-cli). To install the CLI with Rust, the Wasm target and an editor, see [Setup](../../build/smart-contracts/getting-started/setup#install-the-stellar-cli).
+
+## Learn more
+
+- [Stellar CLI Guides](./cookbook) gives examples of how to use the CLI.
+- [Stellar CLI Manual](./stellar-cli) is the auto-generated reference for every command.
diff --git a/docs/tools/cli/install-cli.mdx b/docs/tools/cli/install-cli.mdx
index 84d1afea2..dfc232220 100644
--- a/docs/tools/cli/install-cli.mdx
+++ b/docs/tools/cli/install-cli.mdx
@@ -1,13 +1,10 @@
 ---
-title: Install the CLI
+title: Install the Stellar CLI
+sidebarTitle: Install the CLI
+"og:title": Install the CLI
 description: How to Install the Stellar CLI.
-sidebar_position: 10
 ---
 
-import { StellarCliGitHubVersion } from "@site/src/components/StellarCliGitHubVersion";
-
-# Install the Stellar CLI
-
 ### Stellar CLI
 
 There are a few ways to install the latest released version of Stellar CLI.
@@ -36,7 +33,7 @@ Install with cargo from source ([github.com/stellar/stellar-cli](https://github.
 cargo install --locked stellar-cli
 ```
 
-:::note
+<Note>
 
 Installing from source requires Rust and C build systems.
 
@@ -50,17 +47,19 @@ To install a C build system on Debian/Ubuntu, use:
 sudo apt update && sudo apt install -y build-essential
 ```
 
-:::
+</Note>
 
 Install in your GitHub action (this is a preferred option of installing cli in your GitHub actions)
 
-<StellarCliGitHubVersion />
+```yaml
+uses: stellar/stellar-cli@v25.2.0
+```
 
-:::note
+<Note>
 
 You can also use the third-party tool [SVM (Stellar Version Manager)](https://www.npmjs.com/package/svm-cli), a version manager for Stellar CLI that allows you to install and switch between different versions of stellar-cli.
 
-:::
+</Note>
 
 ## Set up Autocomplete
 
@@ -86,9 +85,9 @@ echo "source <(stellar completion --shell bash)" >> ~/.bashrc
 
 ## Stellar CLI Cookbook
 
-To understand how to get the most of the Stellar CLI, see the [Stellar CLI Cookbook](./cookbook/README.mdx) for recipes and a collection of resources to teach you how to use the CLI. Examples of recipes included in the CLI cookbook include: send payments, manage contract lifecycle, extend contract instance/storage/wasm, and more.
+To understand how to get the most of the Stellar CLI, see the [Stellar CLI Cookbook](/docs/tools/cli/cookbook) for recipes and a collection of resources to teach you how to use the CLI. Examples of recipes included in the CLI cookbook include: send payments, manage contract lifecycle, extend contract instance/storage/wasm, and more.
 
 ## Video Tutorials
 
-- Video Tutorial on `network container`, `keys`, and `contract init` from the [2024-06-27 developers meeting](/meetings/2024/06/27)
-- Video Tutorial on `alias` and `snapshot` from the [2024-09-12 developers meeting](/meetings/2024/09/12)
+- Video Tutorial on `network container`, `keys`, and `contract init` from the [2024-06-27 developers meeting](https://developers.stellar.org/meetings/2024/06/27)
+- Video Tutorial on `alias` and `snapshot` from the [2024-09-12 developers meeting](https://developers.stellar.org/meetings/2024/09/12)
diff --git a/docs/tools/cli/plugins-list.mdx b/docs/tools/cli/plugins-list.mdx
index 9bb4424dc..c9ab68ce4 100644
--- a/docs/tools/cli/plugins-list.mdx
+++ b/docs/tools/cli/plugins-list.mdx
@@ -1,36 +1,35 @@
 ---
 title: Plugins List
 description: See a list of published Stellar CLI plugin
-sidebar_position: 30
 ---
 
 This is a list of all plugins made available by the community, so please review with care before using them.
 
-### [stellar-scaffold/cli](https://github.com/stellar-scaffold/cli)
+### [stellar-scaffold/cli](https://github.com/stellar-scaffold/cli) {#stellar-scaffoldcli}
 
 The Stellar app lifecycle streamlined. `stellar scaffold` CLI: init, learn, &amp; build ambitious apps. `stellar registry` CLI: author, publish, deploy &amp; upgrade Wasm binaries + smart contracts (or use someone else's)
 
 [https://github.com/stellar-scaffold/cli](https://github.com/stellar-scaffold/cli)
 
-### [lightsail-network/stellar-contract-bindings](https://github.com/lightsail-network/stellar-contract-bindings)
+### [lightsail-network/stellar-contract-bindings](https://github.com/lightsail-network/stellar-contract-bindings) {#lightsail-networkstellar-contract-bindings}
 
 CLI tool designed to generate language bindings for Stellar Soroban smart contracts.
 
 [https://github.com/lightsail-network/stellar-contract-bindings](https://github.com/lightsail-network/stellar-contract-bindings)
 
-### [OpenZeppelin/stellar-upgrader-cli](https://github.com/OpenZeppelin/stellar-upgrader-cli)
+### [OpenZeppelin/stellar-upgrader-cli](https://github.com/OpenZeppelin/stellar-upgrader-cli) {#openzeppelinstellar-upgrader-cli}
 
 CLI that help developers to upgrade stellar contracts
 
 [https://github.com/OpenZeppelin/stellar-upgrader-cli](https://github.com/OpenZeppelin/stellar-upgrader-cli)
 
-### [brozorec/smart-account-sign](https://github.com/brozorec/smart-account-sign)
+### [brozorec/smart-account-sign](https://github.com/brozorec/smart-account-sign) {#brozorecsmart-account-sign}
 
 CLI tool for interacting with Stellar Smart Accounts
 
 [https://github.com/brozorec/smart-account-sign](https://github.com/brozorec/smart-account-sign)
 
-### [fnando/stellar-hello-plugin](https://github.com/fnando/stellar-hello-plugin)
+### [fnando/stellar-hello-plugin](https://github.com/fnando/stellar-hello-plugin) {#fnandostellar-hello-plugin}
 
 This is just a sample plugin for the Stellar CLI
 
diff --git a/docs/tools/cli/plugins.mdx b/docs/tools/cli/plugins.mdx
index eb88c4fbe..f1ab8bced 100644
--- a/docs/tools/cli/plugins.mdx
+++ b/docs/tools/cli/plugins.mdx
@@ -1,11 +1,8 @@
 ---
 title: Plugins
 description: How to Use Plugins with the Stellar CLI
-sidebar_position: 20
 ---
 
-# Plugins
-
 Plugins extend the functionality of the Stellar CLI by adding custom commands. The Stellar CLI automatically detects and loads any executable (which doesn't have to be a binary) in your `PATH` that starts with `stellar-`.
 
 ## How Plugins Work
@@ -22,11 +19,13 @@ cargo install --locked stellar-strkey --features cli
 
 This installs the `stellar-strkey` binary in your `~/.cargo/bin` directory. Make sure this directory is in your `$PATH` for the CLI to detect it.
 
-:::danger[Security Warning]
+<Danger>
+
+**Security Warning**
 
 Be careful! Plugins have the same access to your system as the Stellar CLI itself. Only install plugins from sources you trust.
 
-:::
+</Danger>
 
 ## Listing Available Plugins
 
@@ -99,11 +98,11 @@ For example, if you create a plugin named `stellar-contract-bindings-ruby`, user
 
 The CLI converts spaces to dashes when searching for the plugin executable, so both formats work.
 
-:::tip
+<Tip>
 
 If you're using GitHub to host your plugin's repository, consider adding a `stellar-cli-plugin` [repository topic](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics). This way, your plugin will be listed by `stellar plugin search`.
 
-:::
+</Tip>
 
 ## Troubleshooting
 
diff --git a/docs/tools/cli/stellar-cli.mdx b/docs/tools/cli/stellar-cli.mdx
index 267f82c20..3103c876b 100644
--- a/docs/tools/cli/stellar-cli.mdx
+++ b/docs/tools/cli/stellar-cli.mdx
@@ -1,7 +1,5561 @@
 ---
-sidebar_position: 12
+title: Stellar CLI Manual
+description: This document contains the help content for the Stellar command-line program.
 ---
 
-# Stellar CLI Manual
+This document contains the help content for the `stellar` command-line program.
 
-Stub file: the real file is generated in build time by `pnpm stellar-cli:build`.
+## `stellar`
+
+Work seamlessly with Stellar accounts, contracts, and assets from the command line.
+
+- Generate and manage keys and accounts
+- Build, deploy, and interact with contracts
+- Deploy asset contracts
+- Stream events
+- Start local testnets
+- Decode, encode XDR
+- More!
+
+For additional information see:
+
+- Stellar Docs: https://developers.stellar.org
+- Smart Contract Docs: https://developers.stellar.org/docs/build/smart-contracts/overview
+- CLI Docs: https://developers.stellar.org/docs/tools/developer-tools/cli/stellar-cli
+
+To get started generate a new identity:
+
+```
+stellar keys generate alice
+```
+
+Use keys with the `--source` flag in other commands.
+
+Commands that work with contracts are organized under the `contract` subcommand. List them:
+
+```
+stellar contract --help
+```
+
+Use contracts like a CLI:
+
+```
+stellar contract invoke --contract-id CCR6QKTWZQYW6YUJ7UP7XXZRLWQPFRV6SWBLQS4ZQOSAF4BOUD77OTE2 --source alice --network testnet -- --help
+```
+
+Anything after the `--` double dash (the "slop") is parsed as arguments to the contract-specific CLI, generated on-the-fly from the contract schema. For the hello world example, with a function called `hello` that takes one string argument `to`, here's how you invoke it:
+
+```
+stellar contract invoke --contract-id CCR6QKTWZQYW6YUJ7UP7XXZRLWQPFRV6SWBLQS4ZQOSAF4BOUD77OTE2 --source alice --network testnet -- hello --to world
+```
+
+**Usage:** `stellar [OPTIONS] <COMMAND>`
+
+###### **Subcommands:**
+
+- `contract` — Tools for smart contract developers
+- `doctor` — Diagnose and troubleshoot CLI and network issues
+- `events` — Watch the network for contract events
+- `env` — Prints the environment variables
+- `keys` — Create and manage identities including keys and addresses
+- `network` — Configure connection to networks
+- `container` — Start local networks in containers
+- `config` — Manage CLI configuration
+- `snapshot` — Download a snapshot of a ledger from an archive
+- `token` — Interact with SEP-41 tokens and Stellar Asset Contracts
+- `tx` — Sign, Simulate, and Send transactions
+- `xdr` — Decode and encode XDR
+- `strkey` — Decode and encode strkey
+- `completion` — Print shell completion code for the specified shell
+- `cache` — Cache for transactions and contract specs
+- `version` — Print version information
+- `skill` — Print an AI-agent skill guide for using the Stellar CLI
+- `plugin` — The subcommand for CLI plugins
+- `ledger` — Fetch ledger information
+- `message` — Sign and verify arbitrary messages using SEP-53
+- `fee-stats` — ⚠️ Deprecated, use `fees stats` instead. Fetch network feestats
+- `fees` — Fetch network feestats and configure CLI fee settings
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+- `-f`, `--filter-logs <FILTER_LOGS>` — Filter logs output. To turn on `stellar_cli::log::footprint=debug` or off `=off`. Can also use env var `RUST_LOG`
+- `-q`, `--quiet` — Do not write logs to stderr including `INFO`
+- `-v`, `--verbose` — Log DEBUG events
+- `--very-verbose` [alias: `vv`] — Log DEBUG and TRACE events
+- `--no-cache` — Do not cache your simulations and transactions
+
+## `stellar contract`
+
+Tools for smart contract developers
+
+**Usage:** `stellar contract <COMMAND>`
+
+###### **Subcommands:**
+
+- `asset` — Utilities to deploy a Stellar Asset Contract or get its id
+- `alias` — Utilities to manage contract aliases
+- `bindings` — Generate code client bindings for a contract
+- `build` — Build a contract from source
+- `extend` — Extend the time to live ledger of a contract-data ledger entry
+- `deploy` — Deploy a wasm contract
+- `fetch` — Fetch a contract's Wasm binary
+- `id` — Generate the contract id for a given contract or asset
+- `info` — Access info about contracts
+- `init` — Initialize a Soroban contract project
+- `inspect` — ⚠️ Deprecated, use `contract info`. Inspect a WASM file listing contract functions, meta, etc
+- `upload` — Install a WASM file to the ledger without creating a contract instance
+- `install` — ⚠️ Deprecated, use `contract upload`. Install a WASM file to the ledger without creating a contract instance
+- `invoke` — Invoke a contract function
+- `optimize` — ⚠️ Deprecated, use `build --optimize`. Optimize a WASM file
+- `read` — Print the current value of a contract-data ledger entry
+- `restore` — Restore an evicted value for a contract-data legder entry
+
+## `stellar contract asset`
+
+Utilities to deploy a Stellar Asset Contract or get its id
+
+**Usage:** `stellar contract asset <COMMAND>`
+
+###### **Subcommands:**
+
+- `id` — Get Id of builtin Soroban Asset Contract. Deprecated, use `stellar contract id asset` instead
+- `deploy` — Deploy builtin Soroban Asset Contract
+
+## `stellar contract asset id`
+
+Get Id of builtin Soroban Asset Contract. Deprecated, use `stellar contract id asset` instead
+
+**Usage:** `stellar contract asset id [OPTIONS] --asset <ASSET>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--asset <ASSET>` — ID of the Stellar classic asset to wrap, e.g. "native", "USDC:G...5", "USDC:alias"
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar contract asset deploy`
+
+Deploy builtin Soroban Asset Contract
+
+**Usage:** `stellar contract asset deploy [OPTIONS] --asset <ASSET> --source-account <SOURCE_ACCOUNT>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--asset <ASSET>` — ID of the Stellar classic asset to wrap, e.g. "USDC:G...5"
+- `--alias <ALIAS>` — The alias that will be used to save the assets's id. Whenever used, `--alias` will always overwrite the existing contract id configuration without asking for confirmation
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+- `--resource-fee <RESOURCE_FEE>` — Set the fee for smart contract resource consumption, in stroops. 1 stroop = 0.0000001 xlm. Overrides the simulated resource fee
+- `--instructions <INSTRUCTIONS>` — ⚠️ Deprecated, use `--instruction-leeway` to increase instructions. Number of instructions to allocate for the transaction
+- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Allow this many extra instructions when budgeting resources with transaction simulation
+- `--cost` — Output the cost execution to stderr
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar contract alias`
+
+Utilities to manage contract aliases
+
+**Usage:** `stellar contract alias <COMMAND>`
+
+###### **Subcommands:**
+
+- `rm` — Remove contract alias
+- `add` — Add contract alias
+- `show` — Show the contract id associated with a given alias
+- `ls` — List all aliases
+
+## `stellar contract alias rm`
+
+Remove contract alias
+
+**Usage:** `stellar contract alias rm [OPTIONS] <ALIAS>`
+
+**Command Alias:** `remove`
+
+###### **Arguments:**
+
+- `<ALIAS>` — The contract alias that will be removed
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar contract alias add`
+
+Add contract alias
+
+**Usage:** `stellar contract alias add [OPTIONS] --contract-id <CONTRACT_ID> <ALIAS>`
+
+###### **Arguments:**
+
+- `<ALIAS>` — The contract alias that will be used
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--overwrite` — Overwrite the contract alias if it already exists
+- `--contract-id <CONTRACT_ID>` [alias: `id`] — The contract id that will be associated with the alias
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar contract alias show`
+
+Show the contract id associated with a given alias
+
+**Usage:** `stellar contract alias show [OPTIONS] <ALIAS>`
+
+###### **Arguments:**
+
+- `<ALIAS>` — The contract alias that will be displayed
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar contract alias ls`
+
+List all aliases
+
+**Usage:** `stellar contract alias ls [OPTIONS]`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+## `stellar contract bindings`
+
+Generate code client bindings for a contract
+
+**Usage:** `stellar contract bindings <COMMAND>`
+
+###### **Subcommands:**
+
+- `rust` — Generate Rust bindings
+- `typescript` — ⚠️ Deprecated, use the JavaScript Stellar SDK instead (https://github.com/stellar/js-stellar-sdk#cli). Generate a TypeScript / JavaScript package
+- `python` — Generate Python bindings
+- `java` — Generate Java bindings
+- `flutter` — Generate Flutter bindings
+- `swift` — Generate Swift bindings
+- `php` — Generate PHP bindings
+- `kmp` — Generate Kotlin Multiplatform bindings
+
+## `stellar contract bindings rust`
+
+Generate Rust bindings
+
+**Usage:** `stellar contract bindings rust --wasm <WASM>`
+
+###### **Options:**
+
+- `--wasm <WASM>` — Path to wasm binary
+
+## `stellar contract bindings typescript`
+
+⚠️ Deprecated, use the JavaScript Stellar SDK instead (https://github.com/stellar/js-stellar-sdk#cli). Generate a TypeScript / JavaScript package
+
+**Usage:** `stellar contract bindings typescript [OPTIONS] --output-dir <OUTPUT_DIR> <--wasm <WASM>|--wasm-hash <WASM_HASH>|--contract-id <CONTRACT_ID>>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--wasm <WASM>` — Wasm file path on local filesystem. Provide this OR `--wasm-hash` OR `--contract-id`
+- `--wasm-hash <WASM_HASH>` — Hash of Wasm blob on a network. Provide this OR `--wasm` OR `--contract-id`
+- `--contract-id <CONTRACT_ID>` [alias: `id`] — Contract ID/alias on a network. Provide this OR `--wasm-hash` OR `--wasm`
+- `--output-dir <OUTPUT_DIR>` — Where to place generated project
+- `--overwrite` — Whether to overwrite output directory if it already exists
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar contract bindings python`
+
+Generate Python bindings
+
+**Usage:** `stellar contract bindings python`
+
+## `stellar contract bindings java`
+
+Generate Java bindings
+
+**Usage:** `stellar contract bindings java`
+
+## `stellar contract bindings flutter`
+
+Generate Flutter bindings
+
+**Usage:** `stellar contract bindings flutter`
+
+## `stellar contract bindings swift`
+
+Generate Swift bindings
+
+**Usage:** `stellar contract bindings swift`
+
+## `stellar contract bindings php`
+
+Generate PHP bindings
+
+**Usage:** `stellar contract bindings php`
+
+## `stellar contract bindings kmp`
+
+Generate Kotlin Multiplatform bindings
+
+**Usage:** `stellar contract bindings kmp`
+
+## `stellar contract build`
+
+Build a contract from source
+
+Builds all crates that are referenced by the cargo manifest (Cargo.toml) that have cdylib as their crate-type. Crates are built for the wasm32 target. Unless configured otherwise, crates are built with their default features and with their release profile.
+
+In workspaces builds all crates unless a package name is specified, or the command is executed from the sub-directory of a workspace crate.
+
+To view the commands that will be executed, without executing them, use the --print-commands-only option.
+
+**Usage:** `stellar contract build [OPTIONS]        build <COMMAND>`
+
+###### **Subcommands:**
+
+- `archive` — Generate (or inspect) the reproducible source archive for a contract
+
+###### **Container Options:**
+
+- `--image <IMAGE>` — Build inside this container image (e.g. `docker.io/stellar/stellar-cli:latest`). When set, the build runs in the container against the bind-mounted working tree instead of locally. Any tag or digest ref is accepted.
+
+  On Linux the container runs as your uid:gid so built wasm isn't root-owned; this assumes the image keeps CARGO_HOME/RUSTUP_HOME writable by non-root users, as the official image does.
+
+- `--pull` — Pull `--image` before building to refresh a moving tag.
+
+  By default the build uses the image already present locally and doesn't pull (matching `docker run`), so a locally-built or digest-pinned image is used as-is. Pass `--pull` to fetch the newest image for the tag first.
+
+- `-d`, `--docker-host <DOCKER_HOST>` — Optional argument to override the default docker host. This is useful when you are using a non-standard docker host path for your Docker-compatible container runtime, e.g. Docker Desktop defaults to $HOME/.docker/run/docker.sock instead of /var/run/docker.sock
+- `--engine <ENGINE>` — Container engine to use [default: docker]
+
+  Possible values:
+  - `docker`: Docker, or any Docker-compatible CLI
+  - `apple-container`: Apple's `container` CLI (macOS 26+, Apple silicon)
+
+- `--cpus <CPUS>` — Limit the number of CPUs available to the container, e.g. `2`. A whole number: Apple's `container` engine does not accept fractional CPUs
+- `--memory <MEMORY>` — Limit the memory available to the container, e.g. `2g` or `512m`
+
+###### **Features:**
+
+- `--features <FEATURES>` — Build with the list of features activated, space or comma separated
+- `--all-features` — Build with the all features activated
+- `--no-default-features` — Build with the default feature not activated
+
+###### **Metadata:**
+
+- `--meta <META>` — Add key-value to contract meta (adds the meta to the `contractmetav0` custom section)
+
+###### **Options:**
+
+- `--manifest-path <MANIFEST_PATH>` — Path to Cargo.toml
+- `--package <PACKAGE>` — Package to build
+
+  If omitted, all packages that build for crate-type cdylib are built.
+
+- `--profile <PROFILE>` — Build with the specified profile
+
+  Default value: `release`
+
+- `--out-dir <OUT_DIR>` — Directory to copy wasm files to
+
+  If provided, wasm files can be found in the cargo target directory, and the specified directory.
+
+  If ommitted, wasm files are written only to the cargo target directory.
+
+- `--locked` — Assert that `Cargo.lock` will remain unchanged
+- `--optimize <OPTIMIZE>` — Optimize the generated wasm. Enabled by default; pass `--optimize=false` to disable. Requires the `additional-libs` feature
+
+  Default value: `true`
+
+  Possible values: `true`, `false`
+
+###### **Other:**
+
+- `--print-commands-only` — Print commands to build without executing them
+
+## `stellar contract build archive`
+
+Generate (or inspect) the reproducible source archive for a contract.
+
+Produces a gzipped tarball of the source tree and prints its SHA-256 (the SEP-58 `source_sha256`). Use `--dry-run` to list exactly what would be archived without writing anything — handy for confirming the contents before publishing the archive.
+
+The archive is the current working directory, honoring the project's `.gitignore` and `.ignore` files (the `.git` directory itself is always skipped). Run this from the project (or workspace) root you want archived.
+
+**Usage:** `stellar contract build archive [OPTIONS]`
+
+###### **Options:**
+
+- `-o`, `--out-file <OUT_FILE>` — Where to write the gzipped tarball. Required unless `--dry-run` is used
+- `--dry-run` — List the entries that would be archived and the computed source_sha256, without writing any file
+
+## `stellar contract extend`
+
+Extend the time to live ledger of a contract-data ledger entry.
+
+If no keys are specified the contract itself is extended.
+
+**Usage:** `stellar contract extend [OPTIONS] --ledgers-to-extend <LEDGERS_TO_EXTEND> --source-account <SOURCE_ACCOUNT>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--ledgers-to-extend <LEDGERS_TO_EXTEND>` — Number of ledgers to extend the entries
+- `--ttl-ledger-only` — Only print the new Time To Live ledger
+- `--contract-id <CONTRACT_ID>` [alias: `id`] — Contract ID to which owns the data entries. If no keys provided the Contract's instance will be extended
+- `--key <KEY>` — Storage key (symbols only)
+- `--key-xdr <KEY_XDR>` — Storage key (base64-encoded XDR)
+- `--wasm <WASM>` — Path to Wasm file of contract code to extend
+- `--wasm-hash <WASM_HASH>` — Path to Wasm file of contract code to extend
+- `--durability <DURABILITY>` — Storage entry durability
+
+  Default value: `persistent`
+
+  Possible values:
+  - `persistent`: Persistent
+  - `temporary`: Temporary
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+- `--resource-fee <RESOURCE_FEE>` — Set the fee for smart contract resource consumption, in stroops. 1 stroop = 0.0000001 xlm. Overrides the simulated resource fee
+- `--instructions <INSTRUCTIONS>` — ⚠️ Deprecated, use `--instruction-leeway` to increase instructions. Number of instructions to allocate for the transaction
+- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Allow this many extra instructions when budgeting resources with transaction simulation
+- `--cost` — Output the cost execution to stderr
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar contract deploy`
+
+Deploy a wasm contract
+
+**Usage:** `stellar contract deploy [OPTIONS] --source-account <SOURCE_ACCOUNT> [-- <CONTRACT_CONSTRUCTOR_ARGS>...]`
+
+###### **Arguments:**
+
+- `<CONTRACT_CONSTRUCTOR_ARGS>` — If provided, will be passed to the contract's `__constructor` function with provided arguments for that function as `--arg-name value`
+
+###### **Build Options:**
+
+- `--package <PACKAGE>` — Package to build when auto-building without --wasm
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Metadata:**
+
+- `--meta <META>` — Add key-value to contract meta (adds the meta to the `contractmetav0` custom section)
+
+###### **Options:**
+
+- `--wasm <WASM>` — WASM file to deploy. When neither --wasm nor --wasm-hash is provided inside a Cargo workspace, builds the project automatically. One of --wasm or --wasm-hash is required when outside a Cargo workspace
+- `--wasm-hash <WASM_HASH>` — Hash of the already installed/deployed WASM file
+- `--salt <SALT>` — Custom salt 32-byte salt for the token id
+- `-i`, `--ignore-checks` — Whether to ignore safety checks when deploying contracts
+
+  Default value: `false`
+
+- `--alias <ALIAS>` — The alias that will be used to save the contract's id. Whenever used, `--alias` will always overwrite the existing contract id configuration without asking for confirmation
+- `--optimize <OPTIMIZE>` — Optimize the generated wasm. Enabled by default; pass `--optimize=false` to disable. Requires the `additional-libs` feature
+
+  Default value: `true`
+
+  Possible values: `true`, `false`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+- `--resource-fee <RESOURCE_FEE>` — Set the fee for smart contract resource consumption, in stroops. 1 stroop = 0.0000001 xlm. Overrides the simulated resource fee
+- `--instructions <INSTRUCTIONS>` — ⚠️ Deprecated, use `--instruction-leeway` to increase instructions. Number of instructions to allocate for the transaction
+- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Allow this many extra instructions when budgeting resources with transaction simulation
+- `--cost` — Output the cost execution to stderr
+- `--auth-mode <AUTH_MODE>` — Set the authorization mode for transaction simulation. When unset, the RPC default is used: record with the root mode if no authorization entries exist, otherwise enforce the provided entries. Should only be set for `InvokeHostFunction` transactions. The `enforce` mode is for simulating transactions that already contain authorization entries
+
+  Possible values:
+  - `enforce`: Validate the authorization entries already on the transaction
+  - `root`: Record authorization entries, requiring each to be rooted at the transaction's top-level operation
+  - `non-root`: Record all authorization entries, including non-root entries
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar contract fetch`
+
+Fetch a contract's Wasm binary
+
+**Usage:** `stellar contract fetch [OPTIONS]`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--contract-id <CONTRACT_ID>` [alias: `id`] — Contract ID to fetch
+- `--wasm-hash <WASM_HASH>` — Wasm to fetch
+- `-o`, `--out-file <OUT_FILE>` — Where to write output otherwise stdout is used
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar contract id`
+
+Generate the contract id for a given contract or asset
+
+**Usage:** `stellar contract id <COMMAND>`
+
+###### **Subcommands:**
+
+- `asset` — Derive the contract id for a builtin Stellar Asset Contract
+- `wasm` — Derive the contract id for a Wasm contract
+
+## `stellar contract id asset`
+
+Derive the contract id for a builtin Stellar Asset Contract
+
+**Usage:** `stellar contract id asset [OPTIONS] --asset <ASSET>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--asset <ASSET>` — ID of the Stellar classic asset to wrap, e.g. "native", "USDC:G...5", "USDC:alias"
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar contract id wasm`
+
+Derive the contract id for a Wasm contract
+
+**Usage:** `stellar contract id wasm [OPTIONS] --salt <SALT> --source-account <SOURCE_ACCOUNT>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--salt <SALT>` — ID of the Soroban contract
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+
+## `stellar contract info`
+
+Access info about contracts
+
+**Usage:** `stellar contract info <COMMAND>`
+
+###### **Subcommands:**
+
+- `interface` — Output the interface of a contract
+- `meta` — Output the metadata stored in a contract
+- `env-meta` — Output the env required metadata stored in a contract
+- `build` — Output the contract build information, if available
+- `hash` — Output the SHA-256 hash of a contract's Wasm
+
+## `stellar contract info interface`
+
+Output the interface of a contract.
+
+A contract's interface describes the functions, parameters, and types that the contract makes accessible to be called.
+
+The data outputted by this command is a stream of `SCSpecEntry` XDR values. See the type definitions in [stellar-xdr](https://github.com/stellar/stellar-xdr). [See also XDR data format](https://developers.stellar.org/docs/learn/encyclopedia/data-format/xdr).
+
+Outputs no data when no data is present in the contract.
+
+**Usage:** `stellar contract info interface [OPTIONS] <--wasm <WASM>|--wasm-hash <WASM_HASH>|--contract-id <CONTRACT_ID>>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--wasm <WASM>` — Wasm file path on local filesystem. Provide this OR `--wasm-hash` OR `--contract-id`
+- `--wasm-hash <WASM_HASH>` — Hash of Wasm blob on a network. Provide this OR `--wasm` OR `--contract-id`
+- `--contract-id <CONTRACT_ID>` [alias: `id`] — Contract ID/alias on a network. Provide this OR `--wasm-hash` OR `--wasm`
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `rust`
+
+  Possible values:
+  - `rust`: Rust code output of the contract interface
+  - `xdr-base64`: XDR output of the info entry
+  - `json`: JSON output of the info entry (one line, not formatted)
+  - `json-formatted`: Formatted (multiline) JSON output of the info entry
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar contract info meta`
+
+Output the metadata stored in a contract.
+
+A contract's meta is a series of key-value pairs that the contract developer can set with any values to provided metadata about the contract. The meta also contains some information like the version of Rust SDK, and Rust compiler version.
+
+The data outputted by this command is a stream of `SCMetaEntry` XDR values. See the type definitions in [stellar-xdr](https://github.com/stellar/stellar-xdr). [See also XDR data format](https://developers.stellar.org/docs/learn/encyclopedia/data-format/xdr).
+
+Outputs no data when no data is present in the contract.
+
+**Usage:** `stellar contract info meta [OPTIONS] <--wasm <WASM>|--wasm-hash <WASM_HASH>|--contract-id <CONTRACT_ID>>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--wasm <WASM>` — Wasm file path on local filesystem. Provide this OR `--wasm-hash` OR `--contract-id`
+- `--wasm-hash <WASM_HASH>` — Hash of Wasm blob on a network. Provide this OR `--wasm` OR `--contract-id`
+- `--contract-id <CONTRACT_ID>` [alias: `id`] — Contract ID/alias on a network. Provide this OR `--wasm-hash` OR `--wasm`
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `text`
+
+  Possible values:
+  - `text`: Text output of the meta info entry
+  - `xdr-base64`: XDR output of the info entry
+  - `json`: JSON output of the info entry (one line, not formatted)
+  - `json-formatted`: Formatted (multiline) JSON output of the info entry
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar contract info env-meta`
+
+Output the env required metadata stored in a contract.
+
+Env-meta is information stored in all contracts, in the `contractenvmetav0` WASM custom section, about the environment that the contract was built for. Env-meta allows the Soroban Env to know whether the contract is compatibility with the network in its current configuration.
+
+The data outputted by this command is a stream of `SCEnvMetaEntry` XDR values. See the type definitions in [stellar-xdr](https://github.com/stellar/stellar-xdr). [See also XDR data format](https://developers.stellar.org/docs/learn/encyclopedia/data-format/xdr).
+
+Outputs no data when no data is present in the contract.
+
+**Usage:** `stellar contract info env-meta [OPTIONS] <--wasm <WASM>|--wasm-hash <WASM_HASH>|--contract-id <CONTRACT_ID>>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--wasm <WASM>` — Wasm file path on local filesystem. Provide this OR `--wasm-hash` OR `--contract-id`
+- `--wasm-hash <WASM_HASH>` — Hash of Wasm blob on a network. Provide this OR `--wasm` OR `--contract-id`
+- `--contract-id <CONTRACT_ID>` [alias: `id`] — Contract ID/alias on a network. Provide this OR `--wasm-hash` OR `--wasm`
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `text`
+
+  Possible values:
+  - `text`: Text output of the meta info entry
+  - `xdr-base64`: XDR output of the info entry
+  - `json`: JSON output of the info entry (one line, not formatted)
+  - `json-formatted`: Formatted (multiline) JSON output of the info entry
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar contract info build`
+
+Output the contract build information, if available.
+
+If the contract has a meta entry like `source_repo=github:user/repo`, this command will try to fetch the attestation information for the WASM file.
+
+**Usage:** `stellar contract info build [OPTIONS] <--wasm <WASM>|--wasm-hash <WASM_HASH>|--contract-id <CONTRACT_ID>>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--wasm <WASM>` — Wasm file path on local filesystem. Provide this OR `--wasm-hash` OR `--contract-id`
+- `--wasm-hash <WASM_HASH>` — Hash of Wasm blob on a network. Provide this OR `--wasm` OR `--contract-id`
+- `--contract-id <CONTRACT_ID>` [alias: `id`] — Contract ID/alias on a network. Provide this OR `--wasm-hash` OR `--wasm`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar contract info hash`
+
+Output the SHA-256 hash of a contract's Wasm.
+
+The hash can be computed from a local .wasm file (`--wasm`) or read from a deployed contract (`--id`). The two flags are mutually exclusive.
+
+Stellar Asset Contracts have no Wasm and therefore no hash; using `--id` against a SAC will return an error.
+
+**Usage:** `stellar contract info hash [OPTIONS] <--wasm <WASM>|--contract-id <CONTRACT_ID>>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--wasm <WASM>` — Path to a local .wasm file
+- `--contract-id <CONTRACT_ID>` [alias: `id`] — Contract ID or alias of a deployed contract
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar contract init`
+
+Initialize a Soroban contract project.
+
+This command will create a Cargo workspace project and add a sample Stellar contract. The name of the contract can be specified by `--name`. It can be run multiple times with different names in order to generate multiple contracts, and files won't be overwritten unless `--overwrite` is passed.
+
+**Usage:** `stellar contract init [OPTIONS] <PROJECT_PATH>`
+
+###### **Arguments:**
+
+- `<PROJECT_PATH>`
+
+###### **Options:**
+
+- `--name <NAME>` — An optional flag to specify a new contract's name.
+
+  Default value: `hello-world`
+
+- `--overwrite` — Overwrite all existing files.
+
+## `stellar contract inspect`
+
+⚠️ Deprecated, use `contract info`. Inspect a WASM file listing contract functions, meta, etc
+
+**Usage:** `stellar contract inspect [OPTIONS] --wasm <WASM>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--wasm <WASM>` — Path to wasm binary
+- `--output <OUTPUT>` — Output just XDR in base64
+
+  Default value: `docs`
+
+  Possible values:
+  - `xdr-base64`: XDR of array of contract spec entries
+  - `xdr-base64-array`: Array of xdr of contract spec entries
+  - `docs`: Pretty print of contract spec entries
+
+## `stellar contract upload`
+
+Install a WASM file to the ledger without creating a contract instance
+
+**Usage:** `stellar contract upload [OPTIONS] --source-account <SOURCE_ACCOUNT>`
+
+###### **Build Options:**
+
+- `--package <PACKAGE>` — Package to build when --wasm is not provided
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Metadata:**
+
+- `--meta <META>` — Add key-value to contract meta (adds the meta to the `contractmetav0` custom section)
+
+###### **Options:**
+
+- `--wasm <WASM>` — Path to wasm binary. When omitted inside a Cargo workspace, builds the project automatically. Required when outside a Cargo workspace
+- `-i`, `--ignore-checks` — Whether to ignore safety checks when deploying contracts
+
+  Default value: `false`
+
+- `--optimize <OPTIMIZE>` — Optimize the generated wasm. Enabled by default; pass `--optimize=false` to disable. Requires the `additional-libs` feature
+
+  Default value: `true`
+
+  Possible values: `true`, `false`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+- `--resource-fee <RESOURCE_FEE>` — Set the fee for smart contract resource consumption, in stroops. 1 stroop = 0.0000001 xlm. Overrides the simulated resource fee
+- `--instructions <INSTRUCTIONS>` — ⚠️ Deprecated, use `--instruction-leeway` to increase instructions. Number of instructions to allocate for the transaction
+- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Allow this many extra instructions when budgeting resources with transaction simulation
+- `--cost` — Output the cost execution to stderr
+- `--auth-mode <AUTH_MODE>` — Set the authorization mode for transaction simulation. When unset, the RPC default is used: record with the root mode if no authorization entries exist, otherwise enforce the provided entries. Should only be set for `InvokeHostFunction` transactions. The `enforce` mode is for simulating transactions that already contain authorization entries
+
+  Possible values:
+  - `enforce`: Validate the authorization entries already on the transaction
+  - `root`: Record authorization entries, requiring each to be rooted at the transaction's top-level operation
+  - `non-root`: Record all authorization entries, including non-root entries
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar contract install`
+
+⚠️ Deprecated, use `contract upload`. Install a WASM file to the ledger without creating a contract instance
+
+**Usage:** `stellar contract install [OPTIONS] --source-account <SOURCE_ACCOUNT>`
+
+###### **Build Options:**
+
+- `--package <PACKAGE>` — Package to build when --wasm is not provided
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Metadata:**
+
+- `--meta <META>` — Add key-value to contract meta (adds the meta to the `contractmetav0` custom section)
+
+###### **Options:**
+
+- `--wasm <WASM>` — Path to wasm binary. When omitted inside a Cargo workspace, builds the project automatically. Required when outside a Cargo workspace
+- `-i`, `--ignore-checks` — Whether to ignore safety checks when deploying contracts
+
+  Default value: `false`
+
+- `--optimize <OPTIMIZE>` — Optimize the generated wasm. Enabled by default; pass `--optimize=false` to disable. Requires the `additional-libs` feature
+
+  Default value: `true`
+
+  Possible values: `true`, `false`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+- `--resource-fee <RESOURCE_FEE>` — Set the fee for smart contract resource consumption, in stroops. 1 stroop = 0.0000001 xlm. Overrides the simulated resource fee
+- `--instructions <INSTRUCTIONS>` — ⚠️ Deprecated, use `--instruction-leeway` to increase instructions. Number of instructions to allocate for the transaction
+- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Allow this many extra instructions when budgeting resources with transaction simulation
+- `--cost` — Output the cost execution to stderr
+- `--auth-mode <AUTH_MODE>` — Set the authorization mode for transaction simulation. When unset, the RPC default is used: record with the root mode if no authorization entries exist, otherwise enforce the provided entries. Should only be set for `InvokeHostFunction` transactions. The `enforce` mode is for simulating transactions that already contain authorization entries
+
+  Possible values:
+  - `enforce`: Validate the authorization entries already on the transaction
+  - `root`: Record authorization entries, requiring each to be rooted at the transaction's top-level operation
+  - `non-root`: Record all authorization entries, including non-root entries
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar contract invoke`
+
+Invoke a contract function
+
+Generates an "implicit CLI" for the specified contract on-the-fly using the contract's schema, which gets embedded into every Soroban contract. The "slop" in this command, everything after the `--`, gets passed to this implicit CLI. Get in-depth help for a given contract:
+
+stellar contract invoke ... -- --help
+
+**Usage:** `stellar contract invoke [OPTIONS] --contract-id <CONTRACT_ID> --source-account <SOURCE_ACCOUNT> [-- <CONTRACT_FN_AND_ARGS>...]`
+
+###### **Arguments:**
+
+- `<CONTRACT_FN_AND_ARGS>` — Function name as subcommand, then arguments for that function as `--arg-name value`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--contract-id <CONTRACT_ID>` [alias: `id`] — Contract ID to invoke
+- `--is-view` — ⚠️ Deprecated, use `--send=no`. View the result simulating and do not sign and submit transaction
+- `--send <SEND>` — Whether or not to send a transaction
+
+  Default value: `default`
+
+  Possible values:
+  - `default`: Send transaction if simulation indicates there are ledger writes, published events, or auth required, otherwise return simulation result
+  - `no`: Do not send transaction, return simulation result
+  - `yes`: Always send transaction
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+- `--resource-fee <RESOURCE_FEE>` — Set the fee for smart contract resource consumption, in stroops. 1 stroop = 0.0000001 xlm. Overrides the simulated resource fee
+- `--instructions <INSTRUCTIONS>` — ⚠️ Deprecated, use `--instruction-leeway` to increase instructions. Number of instructions to allocate for the transaction
+- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Allow this many extra instructions when budgeting resources with transaction simulation
+- `--cost` — Output the cost execution to stderr
+- `--auth-mode <AUTH_MODE>` — Set the authorization mode for transaction simulation. When unset, the RPC default is used: record with the root mode if no authorization entries exist, otherwise enforce the provided entries. Should only be set for `InvokeHostFunction` transactions. The `enforce` mode is for simulating transactions that already contain authorization entries
+
+  Possible values:
+  - `enforce`: Validate the authorization entries already on the transaction
+  - `root`: Record authorization entries, requiring each to be rooted at the transaction's top-level operation
+  - `non-root`: Record all authorization entries, including non-root entries
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar contract optimize`
+
+⚠️ Deprecated, use `build --optimize`. Optimize a WASM file
+
+**Usage:** `stellar contract optimize [OPTIONS] --wasm <WASM>...`
+
+###### **Options:**
+
+- `--wasm <WASM>` — Path to one or more wasm binaries
+- `--wasm-out <WASM_OUT>` — Path to write the optimized WASM file to (defaults to same location as --wasm with .optimized.wasm suffix)
+
+## `stellar contract read`
+
+Print the current value of a contract-data ledger entry
+
+**Usage:** `stellar contract read [OPTIONS]`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--output <OUTPUT>` — Type of output to generate
+
+  Default value: `string`
+
+  Possible values:
+  - `string`: String
+  - `json`: Json
+  - `xdr`: XDR
+
+- `--contract-id <CONTRACT_ID>` [alias: `id`] — Contract ID to which owns the data entries. If no keys provided the Contract's instance will be extended
+- `--key <KEY>` — Storage key (symbols only)
+- `--key-xdr <KEY_XDR>` — Storage key (base64-encoded XDR)
+- `--wasm <WASM>` — Path to Wasm file of contract code to extend
+- `--wasm-hash <WASM_HASH>` — Path to Wasm file of contract code to extend
+- `--durability <DURABILITY>` — Storage entry durability
+
+  Default value: `persistent`
+
+  Possible values:
+  - `persistent`: Persistent
+  - `temporary`: Temporary
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar contract restore`
+
+Restore an evicted value for a contract-data legder entry.
+
+If no keys are specificed the contract itself is restored.
+
+**Usage:** `stellar contract restore [OPTIONS] --source-account <SOURCE_ACCOUNT>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--contract-id <CONTRACT_ID>` [alias: `id`] — Contract ID to which owns the data entries. If no keys provided the Contract's instance will be extended
+- `--key <KEY>` — Storage key (symbols only)
+- `--key-xdr <KEY_XDR>` — Storage key (base64-encoded XDR)
+- `--wasm <WASM>` — Path to Wasm file of contract code to extend
+- `--wasm-hash <WASM_HASH>` — Path to Wasm file of contract code to extend
+- `--durability <DURABILITY>` — Storage entry durability
+
+  Default value: `persistent`
+
+  Possible values:
+  - `persistent`: Persistent
+  - `temporary`: Temporary
+
+- `--ledgers-to-extend <LEDGERS_TO_EXTEND>` — Number of ledgers to extend the entry
+- `--ttl-ledger-only` — Only print the new Time To Live ledger
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+- `--resource-fee <RESOURCE_FEE>` — Set the fee for smart contract resource consumption, in stroops. 1 stroop = 0.0000001 xlm. Overrides the simulated resource fee
+- `--instructions <INSTRUCTIONS>` — ⚠️ Deprecated, use `--instruction-leeway` to increase instructions. Number of instructions to allocate for the transaction
+- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Allow this many extra instructions when budgeting resources with transaction simulation
+- `--cost` — Output the cost execution to stderr
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar doctor`
+
+Diagnose and troubleshoot CLI and network issues
+
+**Usage:** `stellar doctor [OPTIONS]`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+## `stellar events`
+
+Watch the network for contract events
+
+**Usage:** `stellar events [OPTIONS]`
+
+#### **FILTERS:** {#filters}
+
+- `--id <CONTRACT_IDS>` — A set of (up to 5) contract IDs to filter events on. This parameter can be passed multiple times, e.g. `--id C123.. --id C456..`, or passed with multiple parameters, e.g. `--id C123 C456`.
+
+  Though the specification supports multiple filter objects (i.e. combinations of type, IDs, and topics), only one set can be specified on the command-line today, though that set can have multiple IDs/topics.
+
+- `--topic <TOPIC_FILTERS>` — A set of (up to 5) topic filters to filter event topics on. A single topic filter can contain 1-4 different segments, separated by commas. An asterisk (`*` character) indicates a wildcard segment.
+
+  In addition to up to 4 possible topic filter segments, the "**" wildcard can also be added, and will allow for a flexible number of topics in the returned events. The "**" wildcard must be the last segment in a query.
+
+  If the "\*\*" wildcard is not included, only events with the exact number of topics as the given filter will be returned.
+
+  **Example:** topic filter with two segments: `--topic "AAAABQAAAAdDT1VOVEVSAA==,*"`
+
+  **Example:** two topic filters with one and two segments each: `--topic "AAAABQAAAAdDT1VOVEVSAA==" --topic '*,*'`
+
+  **Example:** topic filter with four segments and the "**" wildcard: --topic "AAAABQAAAAdDT1VOVEVSAA==,_,_,\*,**"
+
+  Note that all of these topic filters are combined with the contract IDs into a single filter (i.e. combination of type, IDs, and topics).
+
+- `--type <EVENT_TYPE>` — Specifies which type of contract events to display
+
+  Default value: `all`
+
+  Possible values: `all`, `contract`, `system`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--start-ledger <START_LEDGER>` — The first ledger sequence number in the range to pull events https://developers.stellar.org/docs/learn/encyclopedia/network-configuration/ledger-headers#ledger-sequence
+- `--cursor <CURSOR>` — The cursor corresponding to the start of the event range
+- `--output <OUTPUT>` — Output formatting options for event stream
+
+  Default value: `pretty`
+
+  Possible values:
+  - `pretty`: Human-readable output with decoded event names and parameters
+  - `plain`: Human-readable output without colors
+  - `json`: JSON output with decoded event names and parameters
+  - `raw`: Raw event output without self-describing decoding
+
+- `-c`, `--count <COUNT>` — The maximum number of events to display (defer to the server-defined limit)
+
+  Default value: `10`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar env`
+
+Prints the environment variables
+
+Prints to stdout in a format that can be used as .env file. Environment variables have precedence over defaults.
+
+By default, secret values are concealed. To display them, use `--reveal`.
+
+Pass a name to get the value of a single environment variable. Its value is printed without shell quoting (control characters are neutralized), suitable for command substitution. Concealed variables print nothing unless `--reveal` is passed.
+
+If there are no environment variables in use, prints the defaults.
+
+**Usage:** `stellar env [OPTIONS] [NAME]`
+
+###### **Arguments:**
+
+- `<NAME>` — Env variable name to get the value of.
+
+  E.g.: $ stellar env STELLAR_ACCOUNT
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--reveal` — Whether to reveal the value of concealed env vars. By default, concealed env vars are hidden behind a placeholder value
+
+## `stellar keys`
+
+Create and manage identities including keys and addresses
+
+**Usage:** `stellar keys <COMMAND>`
+
+###### **Subcommands:**
+
+- `add` — Add a new identity (keypair, ledger, OS specific secure store)
+- `public-key` — Given an identity return its address (public key)
+- `fund` — Fund an identity on a test network
+- `generate` — Generate a new identity using a 24-word seed phrase The seed phrase can be stored in a config file (default) or in an OS-specific secure store
+- `ls` — List identities
+- `rm` — Remove an identity
+- `secret` — Output an identity's secret key
+- `use` — Set the default identity that will be used on all commands. This allows you to skip `--source-account` or setting a environment variable, while reusing this value in all commands that require it
+- `unset` — Unset the default key identity defined previously with `keys use <identity>`
+
+## `stellar keys add`
+
+Add a new identity (keypair, ledger, OS specific secure store)
+
+**Usage:** `stellar keys add [OPTIONS] <NAME>`
+
+###### **Arguments:**
+
+- `<NAME>` — Name of identity
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--secret-key` — ⚠️ Deprecated, use `--secure-store`. Enter secret (S) key when prompted
+- `--seed-phrase` — ⚠️ Deprecated, use `--secure-store`. Enter key using 12-24 word seed phrase
+- `--secure-store` — Save the new key in your OS's credential secure store.
+
+  On Mac this uses Keychain, on Windows it is Secure Store Service, and on \*nix platforms it uses a combination of the kernel keyutils and DBus-based Secret Service.
+
+  This only supports seed phrases for now.
+
+- `--public-key <PUBLIC_KEY>` — Add a public key, ed25519, or muxed account, e.g. G1.., M2..
+- `--ledger` — Derive the address from a connected Ledger hardware wallet at `m/44'/148'/N'`, where `N` defaults to 0 and can be set with `--hd-path`. Persists the derived public key (and `--hd-path`, when provided) so later commands work without the device
+- `--overwrite` — Overwrite existing identity if it already exists. When combined with --secure-store, also replaces the existing Secure Store entry
+- `--hd-path <HD_PATH>` — When importing a seed phrase, which `hd_path` to derive the key at. Persisted on the identity so later commands derive the same account without re-passing the flag. Not valid with `--public-key` or a raw secret key
+
+## `stellar keys public-key`
+
+Given an identity return its address (public key)
+
+**Usage:** `stellar keys public-key [OPTIONS] [NAME]`
+
+**Command Alias:** `address`
+
+###### **Arguments:**
+
+- `<NAME>` — Name of identity to lookup. Required unless `--ledger` is provided
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--hd-path <HD_PATH>` — If identity is a seed phrase use this hd path, default is 0. With --ledger this is the Ledger account index (default 0)
+- `--ledger` — Derive the address from a connected Ledger hardware wallet at `m/44'/148'/N'`, where `N` defaults to 0 and can be set with `--hd-path`
+
+## `stellar keys fund`
+
+Fund an identity on a test network
+
+**Usage:** `stellar keys fund [OPTIONS] [NAME]`
+
+###### **Arguments:**
+
+- `<NAME>` — Name of identity to lookup. Required unless `--ledger` is provided
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--hd-path <HD_PATH>` — If identity is a seed phrase use this hd path, default is 0. With --ledger this is the Ledger account index (default 0)
+- `--ledger` — Derive the address from a connected Ledger hardware wallet at `m/44'/148'/N'`, where `N` defaults to 0 and can be set with `--hd-path`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar keys generate`
+
+Generate a new identity using a 24-word seed phrase The seed phrase can be stored in a config file (default) or in an OS-specific secure store
+
+**Usage:** `stellar keys generate [OPTIONS] <NAME>`
+
+###### **Arguments:**
+
+- `<NAME>` — Name of identity
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--seed <SEED>` — Optional seed to use when generating seed phrase. Random otherwise
+- `-s`, `--as-secret` — Output the generated identity as a secret key
+- `--secure-store` — Save the new key in your OS's credential secure store.
+
+  On Mac this uses Keychain, on Windows it is Secure Store Service, and on \*nix platforms it uses a combination of the kernel keyutils and DBus-based Secret Service.
+
+- `--hd-path <HD_PATH>` — Which `hd_path` to derive the key at from the seed phrase. Honored across all storage modes: with `--as-secret` it picks which derived key is stored, with `--secure-store` or plain seed-phrase storage it is persisted on the identity so later commands derive the same account without re-passing the flag
+- `--fund` — Fund generated key pair
+
+  Default value: `false`
+
+- `--overwrite` — Overwrite existing identity if it already exists. When combined with --secure-store, also replaces the existing Secure Store entry
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar keys ls`
+
+List identities
+
+**Usage:** `stellar keys ls [OPTIONS]`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `-l`, `--long`
+
+## `stellar keys rm`
+
+Remove an identity
+
+**Usage:** `stellar keys rm [OPTIONS] <NAME>`
+
+###### **Arguments:**
+
+- `<NAME>` — Identity to remove
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--force` — Skip confirmation prompt
+
+## `stellar keys secret`
+
+Output an identity's secret key
+
+**Usage:** `stellar keys secret [OPTIONS] <NAME>`
+
+###### **Arguments:**
+
+- `<NAME>` — Name of identity to lookup, default is test identity
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--phrase` — Output seed phrase instead of private key
+- `--hd-path <HD_PATH>` — If identity is a seed phrase use this hd path, default is 0
+
+## `stellar keys use`
+
+Set the default identity that will be used on all commands. This allows you to skip `--source-account` or setting a environment variable, while reusing this value in all commands that require it
+
+**Usage:** `stellar keys use [OPTIONS] <NAME>`
+
+###### **Arguments:**
+
+- `<NAME>` — Set the default network name
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+## `stellar keys unset`
+
+Unset the default key identity defined previously with `keys use <identity>`
+
+**Usage:** `stellar keys unset [OPTIONS]`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+## `stellar network`
+
+Configure connection to networks
+
+**Usage:** `stellar network <COMMAND>`
+
+###### **Subcommands:**
+
+- `add` — Add a new network
+- `rm` — Remove a network
+- `ls` — List networks
+- `use` — Set the default network that will be used on all commands. This allows you to skip `--network` or setting a environment variable, while reusing this value in all commands that require it
+- `health` — Fetch the health of the configured RPC
+- `info` — Checks the health of the configured RPC
+- `settings` — Fetch the network's config settings
+- `unset` — Unset the default network defined previously with `network use <network>`
+- `root-account` — Compute the root account keypair for a network
+
+## `stellar network add`
+
+Add a new network
+
+**Usage:** `stellar network add [OPTIONS] --rpc-url <RPC_URL> --network-passphrase <NETWORK_PASSPHRASE> <NAME>`
+
+###### **Arguments:**
+
+- `<NAME>` — Name of network
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — Optional header to include in requests to the RPC, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+
+## `stellar network rm`
+
+Remove a network
+
+**Usage:** `stellar network rm [OPTIONS] <NAME>`
+
+###### **Arguments:**
+
+- `<NAME>` — Network to remove
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+## `stellar network ls`
+
+List networks
+
+**Usage:** `stellar network ls [OPTIONS]`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `-l`, `--long` — Get more info about the networks
+
+## `stellar network use`
+
+Set the default network that will be used on all commands. This allows you to skip `--network` or setting a environment variable, while reusing this value in all commands that require it
+
+**Usage:** `stellar network use [OPTIONS] <NAME>`
+
+###### **Arguments:**
+
+- `<NAME>` — Set the default network name
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+## `stellar network health`
+
+Fetch the health of the configured RPC
+
+**Usage:** `stellar network health [OPTIONS]`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `text`
+
+  Possible values:
+  - `text`: Text output of network health status
+  - `json`: JSON result of the RPC request
+  - `json-formatted`: Formatted (multiline) JSON output of the RPC request
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar network info`
+
+Checks the health of the configured RPC
+
+**Usage:** `stellar network info [OPTIONS]`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `text`
+
+  Possible values:
+  - `text`: Text output of network info
+  - `json`: JSON result of the RPC request
+  - `json-formatted`: Formatted (multiline) JSON output of the RPC request
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar network settings`
+
+Fetch the network's config settings
+
+**Usage:** `stellar network settings [OPTIONS]`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--internal` — Include internal config settings that are not upgradeable and are internally maintained by the network
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `json`
+
+  Possible values:
+  - `xdr`: XDR (`ConfigUpgradeSet` type)
+  - `json`: JSON, XDR-JSON of the `ConfigUpgradeSet` XDR type
+  - `json-formatted`: JSON formatted, XDR-JSON of the `ConfigUpgradeSet` XDR type
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar network unset`
+
+Unset the default network defined previously with `network use <network>`
+
+**Usage:** `stellar network unset [OPTIONS]`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+## `stellar network root-account`
+
+Compute the root account keypair for a network
+
+**Usage:** `stellar network root-account <COMMAND>`
+
+###### **Subcommands:**
+
+- `public-key` — Output a network's root account address (public key)
+- `secret` — Output a network's root account secret key
+
+## `stellar network root-account public-key`
+
+Output a network's root account address (public key)
+
+**Usage:** `stellar network root-account public-key [OPTIONS]`
+
+**Command Alias:** `address`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to derive the root account from
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar network root-account secret`
+
+Output a network's root account secret key
+
+**Usage:** `stellar network root-account secret [OPTIONS]`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to derive the root account from
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar container`
+
+Start local networks in containers
+
+**Usage:** `stellar container <COMMAND>`
+
+###### **Subcommands:**
+
+- `logs` — Get logs from a running network container
+- `start` — Start a container running a Stellar node, RPC, API, and friendbot (faucet)
+- `stop` — Stop a network container started with `stellar container start`
+- `use` — Set the default container engine used by `stellar container` commands
+- `unset` — Unset the default container engine defined previously with `container use <engine>`
+
+## `stellar container logs`
+
+Get logs from a running network container
+
+**Usage:** `stellar container logs [OPTIONS] [NAME]`
+
+###### **Arguments:**
+
+- `<NAME>` — Container to get logs from
+
+  Default value: `local`
+
+###### **Options:**
+
+- `-d`, `--docker-host <DOCKER_HOST>` — Optional argument to override the default docker host. This is useful when you are using a non-standard docker host path for your Docker-compatible container runtime, e.g. Docker Desktop defaults to $HOME/.docker/run/docker.sock instead of /var/run/docker.sock
+- `--engine <ENGINE>` — Container engine to use [default: docker]
+
+  Possible values:
+  - `docker`: Docker, or any Docker-compatible CLI
+  - `apple-container`: Apple's `container` CLI (macOS 26+, Apple silicon)
+
+## `stellar container start`
+
+Start a container running a Stellar node, RPC, API, and friendbot (faucet).
+
+`stellar container start NETWORK [OPTIONS]`
+
+By default, when starting a testnet container, without any optional arguments, it will run the equivalent of the following docker command:
+
+`docker run --rm -p 8000:8000 --name stellar stellar/quickstart:latest --testnet --enable rpc,horizon`
+
+**Usage:** `stellar container start [OPTIONS] [NETWORK]`
+
+###### **Arguments:**
+
+- `<NETWORK>` — Network to start. Default is `local`
+
+  Possible values: `local`, `testnet`, `futurenet`, `pubnet`
+
+###### **Options:**
+
+- `-d`, `--docker-host <DOCKER_HOST>` — Optional argument to override the default docker host. This is useful when you are using a non-standard docker host path for your Docker-compatible container runtime, e.g. Docker Desktop defaults to $HOME/.docker/run/docker.sock instead of /var/run/docker.sock
+- `--engine <ENGINE>` — Container engine to use [default: docker]
+
+  Possible values:
+  - `docker`: Docker, or any Docker-compatible CLI
+  - `apple-container`: Apple's `container` CLI (macOS 26+, Apple silicon)
+
+- `--cpus <CPUS>` — Limit the number of CPUs available to the container, e.g. `2`. A whole number: Apple's `container` engine does not accept fractional CPUs
+- `--memory <MEMORY>` — Limit the memory available to the container, e.g. `2g` or `512m`
+- `--name <NAME>` — Optional argument to specify the container name
+- `-l`, `--limits <LIMITS>` — Optional argument to specify the limits for the local network only
+- `-p`, `--ports-mapping <PORTS_MAPPING>` — Argument to specify the `HOST_PORT:CONTAINER_PORT` mapping
+
+  Default value: `8000:8000`
+
+- `-t`, `--image-tag-override <IMAGE_TAG_OVERRIDE>` — Optional argument to override the default docker image tag for the given network
+- `--protocol-version <PROTOCOL_VERSION>` — Optional argument to specify the protocol version for the local network only
+
+## `stellar container stop`
+
+Stop a network container started with `stellar container start`
+
+**Usage:** `stellar container stop [OPTIONS] [NAME]`
+
+###### **Arguments:**
+
+- `<NAME>` — Container to stop
+
+  Default value: `local`
+
+###### **Options:**
+
+- `-d`, `--docker-host <DOCKER_HOST>` — Optional argument to override the default docker host. This is useful when you are using a non-standard docker host path for your Docker-compatible container runtime, e.g. Docker Desktop defaults to $HOME/.docker/run/docker.sock instead of /var/run/docker.sock
+- `--engine <ENGINE>` — Container engine to use [default: docker]
+
+  Possible values:
+  - `docker`: Docker, or any Docker-compatible CLI
+  - `apple-container`: Apple's `container` CLI (macOS 26+, Apple silicon)
+
+## `stellar container use`
+
+Set the default container engine used by `stellar container` commands
+
+**Usage:** `stellar container use [OPTIONS] <ENGINE>`
+
+###### **Arguments:**
+
+- `<ENGINE>` — Container engine to use by default
+
+  Possible values:
+  - `docker`: Docker, or any Docker-compatible CLI
+  - `apple-container`: Apple's `container` CLI (macOS 26+, Apple silicon)
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+## `stellar container unset`
+
+Unset the default container engine defined previously with `container use <engine>`
+
+**Usage:** `stellar container unset [OPTIONS]`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+## `stellar config`
+
+Manage CLI configuration
+
+**Usage:** `stellar config <COMMAND>`
+
+###### **Subcommands:**
+
+- `migrate` — Migrate the local configuration to the global directory
+- `dir` — Show the global configuration directory
+
+## `stellar config migrate`
+
+Migrate the local configuration to the global directory
+
+**Usage:** `stellar config migrate [OPTIONS]`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+## `stellar config dir`
+
+Show the global configuration directory.
+
+The location will depend on how your system is configured.
+
+- It looks up for `XDG_CONFIG_HOME` environment variable. If it's set, `$XDG_CONFIG_HOME/stellar` will be used. - If not set, it defaults to `$HOME/.config`. - Can be overridden by `--config-dir` flag.
+
+**Usage:** `stellar config dir [OPTIONS]`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+## `stellar snapshot`
+
+Download a snapshot of a ledger from an archive
+
+**Usage:** `stellar snapshot <COMMAND>`
+
+###### **Subcommands:**
+
+- `create` — Create a ledger snapshot using a history archive
+- `merge` — Merge multiple ledger snapshots into a single snapshot file
+
+## `stellar snapshot create`
+
+Create a ledger snapshot using a history archive.
+
+Filters (address, wasm-hash) specify what ledger entries to include.
+
+Account addresses include the account, and trustlines.
+
+Contract addresses include the related wasm, contract data.
+
+If a contract is a Stellar asset contract, it includes the asset issuer's account and trust lines, but does not include all the trust lines of other accounts holding the asset. To include them specify the addresses of relevant accounts.
+
+Any invalid contract id passed as `--address` will be ignored.
+
+**Usage:** `stellar snapshot create [OPTIONS]`
+
+#### **Archive Options:** {#archive-options}
+
+- `--archive-url <ARCHIVE_URL>` — Archive URL
+
+#### **Filter Options:** {#filter-options}
+
+- `--address <ADDRESS>` — Account or contract address/alias to include in the snapshot
+- `--wasm-hash <WASM_HASHES>` — WASM hashes to include in the snapshot
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--ledger <LEDGER>` — The ledger sequence number to snapshot. Defaults to latest history archived ledger
+- `--output <OUTPUT>` — Format of the out file
+
+  Default value: `json`
+
+  Possible values: `json`
+
+- `--out <OUT>` — Out path that the snapshot is written to
+
+  Default value: `snapshot.json`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar snapshot merge`
+
+Merge multiple ledger snapshots into a single snapshot file.
+
+When the same ledger key appears in multiple snapshots, the entry from the last snapshot in the argument list takes precedence. Metadata (protocol_version, sequence_number, timestamp, etc.) is taken from the last snapshot.
+
+Example: stellar snapshot merge A.json B.json --out merged.json
+
+This allows combining snapshots from different contract deployments or manually edited snapshots without regenerating from scratch.
+
+**Usage:** `stellar snapshot merge [OPTIONS] <SNAPSHOTS> <SNAPSHOTS>...`
+
+###### **Arguments:**
+
+- `<SNAPSHOTS>` — Snapshot files to merge (at least 2 required)
+
+###### **Options:**
+
+- `-o`, `--out <OUT>` — Output path for the merged snapshot
+
+  Default value: `snapshot.json`
+
+## `stellar token`
+
+Interact with SEP-41 tokens and Stellar Asset Contracts
+
+**Usage:** `stellar token <COMMAND>`
+
+###### **Subcommands:**
+
+- `transfer` — Transfer tokens from one account to another
+- `transfer-from` — Transfer tokens on an owner's behalf using a granted allowance
+- `burn` — Burn tokens from an account, destroying them
+- `burn-from` — Burn tokens from an owner's account using a granted allowance
+- `balance` — Read the token balance of an account or contract
+- `name` — Read the token's name (SEP-41 metadata)
+- `symbol` — Read the token's symbol (SEP-41 metadata)
+- `decimals` — Read the token's decimals (SEP-41 metadata)
+- `approve` — Approve an allowance for a spender to transfer on your behalf
+- `allowance` — Read the allowance a spender has on an owner's behalf
+
+## `stellar token transfer`
+
+Transfer tokens from one account to another
+
+**Usage:** `stellar token transfer [OPTIONS] --id <ID> --from <FROM> --to <TO> --amount <AMOUNT>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--id <ID>` — The token to transfer from: a contract id or alias, `native`, or a classic asset as `CODE:ISSUER`
+- `--from <FROM>` — Account to transfer tokens from. Signs and authorizes the transfer, so it must be an identity or secret key you control
+- `--to <TO>` — Account or contract to transfer the tokens to. Accepts a `G…`/`M…` account, a `C…` contract address, or an alias
+- `--amount <AMOUNT>` — Amount to transfer, in the token's smallest unit (stroops for a Stellar Asset Contract)
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `text`
+
+  Possible values:
+  - `text`: Human-readable text
+  - `json`: Compact, single-line JSON output
+  - `json-formatted`: Formatted (multiline) JSON output
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+## `stellar token transfer-from`
+
+Transfer tokens on an owner's behalf using a granted allowance
+
+**Usage:** `stellar token transfer-from [OPTIONS] --id <ID> --spender <SPENDER> --from <FROM> --to <TO> --amount <AMOUNT>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--id <ID>` — The token to transfer from: a contract id or alias, `native`, or a classic asset as `CODE:ISSUER`
+- `--spender <SPENDER>` — Spender drawing on its allowance. Signs and authorizes the transfer, so it must be an identity or secret key you control
+- `--from <FROM>` — Owner whose tokens are moved. Must have granted `--spender` an allowance. Accepts a `G…`/`M…` account, a `C…` contract address, or an alias
+- `--to <TO>` — Account or contract to transfer the tokens to. Accepts a `G…`/`M…` account, a `C…` contract address, or an alias
+- `--amount <AMOUNT>` — Amount to transfer, in the token's smallest unit (stroops for a Stellar Asset Contract)
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `text`
+
+  Possible values:
+  - `text`: Human-readable text
+  - `json`: Compact, single-line JSON output
+  - `json-formatted`: Formatted (multiline) JSON output
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+## `stellar token burn`
+
+Burn tokens from an account, destroying them
+
+**Usage:** `stellar token burn [OPTIONS] --id <ID> --from <FROM> --amount <AMOUNT>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--id <ID>` — The token to burn: a contract id or alias, `native`, or a classic asset as `CODE:ISSUER`
+- `--from <FROM>` — Account whose tokens are destroyed. Signs and authorizes the burn, so it must be an identity or secret key you control
+- `--amount <AMOUNT>` — Amount to burn, in the token's smallest unit (stroops for a Stellar Asset Contract)
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `text`
+
+  Possible values:
+  - `text`: Human-readable text
+  - `json`: Compact, single-line JSON output
+  - `json-formatted`: Formatted (multiline) JSON output
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+## `stellar token burn-from`
+
+Burn tokens from an owner's account using a granted allowance
+
+**Usage:** `stellar token burn-from [OPTIONS] --id <ID> --spender <SPENDER> --from <FROM> --amount <AMOUNT>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--id <ID>` — The token to burn from: a contract id or alias, `native`, or a classic asset as `CODE:ISSUER`
+- `--spender <SPENDER>` — Spender drawing on its allowance. Signs and authorizes the burn, so it must be an identity or secret key you control
+- `--from <FROM>` — Owner whose tokens are destroyed. Must have granted `--spender` an allowance. Accepts a `G…`/`M…` account, a `C…` contract address, or an alias
+- `--amount <AMOUNT>` — Amount to burn, in the token's smallest unit (stroops for a Stellar Asset Contract)
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `text`
+
+  Possible values:
+  - `text`: Human-readable text
+  - `json`: Compact, single-line JSON output
+  - `json-formatted`: Formatted (multiline) JSON output
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+## `stellar token balance`
+
+Read the token balance of an account or contract
+
+**Usage:** `stellar token balance [OPTIONS] --id <ID> --account <ACCOUNT>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--id <ID>` — The token to query: a contract id or alias, `native`, or a classic asset as `CODE:ISSUER`
+- `--account <ACCOUNT>` — Account or contract whose balance to read
+- `--decimal` — Format the balance as a decimal using the token's `decimals`, instead of the raw smallest unit (stroops for a Stellar Asset Contract)
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `text`
+
+  Possible values:
+  - `text`: Human-readable text
+  - `json`: Compact, single-line JSON output
+  - `json-formatted`: Formatted (multiline) JSON output
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar token name`
+
+Read the token's name (SEP-41 metadata)
+
+**Usage:** `stellar token name [OPTIONS] --id <ID>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--id <ID>` — The token to query: a contract id or alias, `native`, or a classic asset as `CODE:ISSUER`
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `text`
+
+  Possible values:
+  - `text`: Human-readable text
+  - `json`: Compact, single-line JSON output
+  - `json-formatted`: Formatted (multiline) JSON output
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar token symbol`
+
+Read the token's symbol (SEP-41 metadata)
+
+**Usage:** `stellar token symbol [OPTIONS] --id <ID>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--id <ID>` — The token to query: a contract id or alias, `native`, or a classic asset as `CODE:ISSUER`
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `text`
+
+  Possible values:
+  - `text`: Human-readable text
+  - `json`: Compact, single-line JSON output
+  - `json-formatted`: Formatted (multiline) JSON output
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar token decimals`
+
+Read the token's decimals (SEP-41 metadata)
+
+**Usage:** `stellar token decimals [OPTIONS] --id <ID>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--id <ID>` — The token to query: a contract id or alias, `native`, or a classic asset as `CODE:ISSUER`
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `text`
+
+  Possible values:
+  - `text`: Human-readable text
+  - `json`: Compact, single-line JSON output
+  - `json-formatted`: Formatted (multiline) JSON output
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar token approve`
+
+Approve an allowance for a spender to transfer on your behalf
+
+**Usage:** `stellar token approve [OPTIONS] --id <ID> --from <FROM> --spender <SPENDER> --amount <AMOUNT> --expiration-ledger <EXPIRATION_LEDGER>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--id <ID>` — The token to approve an allowance on: a contract id or alias, `native`, or a classic asset as `CODE:ISSUER`
+- `--from <FROM>` — Account granting the allowance. Signs and authorizes the approval, so it must be an identity or secret key you control
+- `--spender <SPENDER>` — Account or contract allowed to spend on `--from`'s behalf. Accepts a `G…`/`M…` account, a `C…` contract address, or an alias
+- `--amount <AMOUNT>` — Allowance to grant, in the token's smallest unit (stroops for a Stellar Asset Contract). Replaces any existing allowance
+- `--expiration-ledger <EXPIRATION_LEDGER>` — Ledger sequence after which the allowance expires. Must be at or beyond the current ledger when the amount is positive
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `text`
+
+  Possible values:
+  - `text`: Human-readable text
+  - `json`: Compact, single-line JSON output
+  - `json-formatted`: Formatted (multiline) JSON output
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+## `stellar token allowance`
+
+Read the allowance a spender has on an owner's behalf
+
+**Usage:** `stellar token allowance [OPTIONS] --id <ID> --from <FROM> --spender <SPENDER>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--id <ID>` — The token to query: a contract id or alias, `native`, or a classic asset as `CODE:ISSUER`
+- `--from <FROM>` — Account or contract that granted the allowance (the owner of the funds)
+- `--spender <SPENDER>` — Account or contract allowed to spend on `--from`'s behalf
+- `--decimal` — Format the allowance as a decimal using the token's `decimals`, instead of the raw smallest unit (stroops for a Stellar Asset Contract)
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `text`
+
+  Possible values:
+  - `text`: Human-readable text
+  - `json`: Compact, single-line JSON output
+  - `json-formatted`: Formatted (multiline) JSON output
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar tx`
+
+Sign, Simulate, and Send transactions
+
+**Usage:** `stellar tx <COMMAND>`
+
+###### **Subcommands:**
+
+- `update` — Update the transaction
+- `edit` — Edit a transaction envelope from stdin. This command respects the environment variables `STELLAR_EDITOR`, `EDITOR` and `VISUAL`, in that order
+- `hash` — Calculate the hash of a transaction envelope
+- `new` — Create a new transaction
+- `operation` — Manipulate the operations in a transaction, including adding new operations
+- `send` — Send a transaction envelope to the network
+- `sign` — Sign a transaction envelope appending the signature to the envelope
+- `simulate` — Simulate a transaction envelope from stdin
+- `fetch` — Fetch a transaction from the network by hash If no subcommand is passed in, the transaction envelope will be returned
+- `decode` — Decode a transaction envelope from XDR to JSON
+- `encode` — Encode a transaction envelope from JSON to XDR
+
+## `stellar tx update`
+
+Update the transaction
+
+**Usage:** `stellar tx update <COMMAND>`
+
+###### **Subcommands:**
+
+- `sequence-number` — Edit the sequence number on a transaction
+
+## `stellar tx update sequence-number`
+
+Edit the sequence number on a transaction
+
+**Usage:** `stellar tx update sequence-number <COMMAND>`
+
+**Command Alias:** `seq-num`
+
+###### **Subcommands:**
+
+- `next` — Fetch the source account's seq-num and increment for the given tx
+
+## `stellar tx update sequence-number next`
+
+Fetch the source account's seq-num and increment for the given tx
+
+**Usage:** `stellar tx update sequence-number next [OPTIONS]`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar tx edit`
+
+Edit a transaction envelope from stdin. This command respects the environment variables `STELLAR_EDITOR`, `EDITOR` and `VISUAL`, in that order.
+
+Example: Start a new edit session
+
+$ stellar tx edit
+
+Example: Pipe an XDR transaction envelope
+
+$ stellar tx new manage-data --data-name hello --build-only | stellar tx edit
+
+**Usage:** `stellar tx edit`
+
+## `stellar tx hash`
+
+Calculate the hash of a transaction envelope
+
+**Usage:** `stellar tx hash [OPTIONS] [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR or file containing XDR to decode, or stdin if empty
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar tx new`
+
+Create a new transaction
+
+**Usage:** `stellar tx new <COMMAND>`
+
+###### **Subcommands:**
+
+- `account-merge` — Transfer XLM balance to another account and remove source account
+- `begin-sponsoring-future-reserves` — Begin sponsoring future reserves for another account
+- `bump-sequence` — Bump sequence number to invalidate older transactions
+- `change-trust` — Create, update, or delete a trustline
+- `claim-claimable-balance` — Claim a claimable balance by its balance ID
+- `clawback` — Clawback an asset from an account
+- `clawback-claimable-balance` — Clawback a claimable balance by its balance ID
+- `create-account` — Create and fund a new account
+- `create-claimable-balance` — Create a claimable balance that can be claimed by specified accounts
+- `create-passive-sell-offer` — Create a passive sell offer on the Stellar DEX
+- `end-sponsoring-future-reserves` — End sponsoring future reserves
+- `liquidity-pool-deposit` — Deposit assets into a liquidity pool
+- `liquidity-pool-withdraw` — Withdraw assets from a liquidity pool
+- `manage-buy-offer` — Create, update, or delete a buy offer
+- `manage-data` — Set, modify, or delete account data entries
+- `manage-sell-offer` — Create, update, or delete a sell offer
+- `path-payment-strict-send` — Send a payment with a different asset using path finding, specifying the send amount
+- `path-payment-strict-receive` — Send a payment with a different asset using path finding, specifying the receive amount
+- `payment` — Send asset to destination account
+- `revoke-sponsorship` — Revoke sponsorship of a ledger entry or signer
+- `set-options` — Set account options like flags, signers, and home domain
+- `set-trustline-flags` — Configure authorization and trustline flags for an asset
+
+## `stellar tx new account-merge`
+
+Transfer XLM balance to another account and remove source account
+
+**Usage:** `stellar tx new account-merge [OPTIONS] --source-account <SOURCE_ACCOUNT> --account <ACCOUNT>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--account <ACCOUNT>` — Muxed Account to merge with, e.g. `GBX...`, 'MBX...'
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx new begin-sponsoring-future-reserves`
+
+Begin sponsoring future reserves for another account
+
+**Usage:** `stellar tx new begin-sponsoring-future-reserves [OPTIONS] --source-account <SOURCE_ACCOUNT> --sponsored-id <SPONSORED_ID>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--sponsored-id <SPONSORED_ID>` — Account that will be sponsored
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx new bump-sequence`
+
+Bump sequence number to invalidate older transactions
+
+**Usage:** `stellar tx new bump-sequence [OPTIONS] --source-account <SOURCE_ACCOUNT> --bump-to <BUMP_TO>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--bump-to <BUMP_TO>` — Sequence number to bump to
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx new change-trust`
+
+Create, update, or delete a trustline
+
+**Usage:** `stellar tx new change-trust [OPTIONS] --source-account <SOURCE_ACCOUNT> --line <LINE>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--line <LINE>`
+- `--limit <LIMIT>` — Limit for the trust line, 0 to remove the trust line
+
+  Default value: `9223372036854775807`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx new claim-claimable-balance`
+
+Claim a claimable balance by its balance ID
+
+**Usage:** `stellar tx new claim-claimable-balance [OPTIONS] --source-account <SOURCE_ACCOUNT> --balance-id <BALANCE_ID>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--balance-id <BALANCE_ID>` — Balance ID of the claimable balance to claim (64-character hex string)
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx new clawback`
+
+Clawback an asset from an account
+
+**Usage:** `stellar tx new clawback [OPTIONS] --source-account <SOURCE_ACCOUNT> --from <FROM> --asset <ASSET> --amount <AMOUNT>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--from <FROM>` — Account to clawback assets from, e.g. `GBX...`
+- `--asset <ASSET>` — Asset to clawback
+- `--amount <AMOUNT>` — Amount of the asset to clawback, in stroops. 1 stroop = 0.0000001 of the asset
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx new clawback-claimable-balance`
+
+Clawback a claimable balance by its balance ID
+
+**Usage:** `stellar tx new clawback-claimable-balance [OPTIONS] --source-account <SOURCE_ACCOUNT> --balance-id <BALANCE_ID>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--balance-id <BALANCE_ID>` — Balance ID of the claimable balance to clawback. Accepts multiple formats: - API format with type prefix (72 chars): 000000006f2179b31311fa8064760b48942c8e166702ba0b8fbe7358c4fd570421840461 - Direct hash format (64 chars): 6f2179b31311fa8064760b48942c8e166702ba0b8fbe7358c4fd570421840461 - Address format (base32): BAAMLBZI42AD52HKGIZOU7WFVZM6BPEJCLPL44QU2AT6TY3P57I5QDNYIA
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx new create-account`
+
+Create and fund a new account
+
+**Usage:** `stellar tx new create-account [OPTIONS] --source-account <SOURCE_ACCOUNT> --destination <DESTINATION>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--destination <DESTINATION>` — Account Id to create, e.g. `GBX...`
+- `--starting-balance <STARTING_BALANCE>` — Initial balance in stroops of the account, default 1 XLM
+
+  Default value: `10_000_000`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx new create-claimable-balance`
+
+Create a claimable balance that can be claimed by specified accounts
+
+**Usage:** `stellar tx new create-claimable-balance [OPTIONS] --source-account <SOURCE_ACCOUNT> --amount <AMOUNT>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--asset <ASSET>` — Asset to be held in the ClaimableBalanceEntry
+
+  Default value: `native`
+
+- `--amount <AMOUNT>` — Amount of asset to store in the entry, in stroops. 1 stroop = 0.0000001 of the asset
+- `--claimant <CLAIMANTS>` — Claimants of the claimable balance. Format: account_id or account_id:predicate_json Can be specified multiple times for multiple claimants.
+
+  Examples:
+  - `--claimant alice (unconditional)` - `--claimant 'bob:{"before_absolute_time":"1735689599"}'` - `--claimant 'charlie:{"and":[{"before_absolute_time":"1735689599"},{"before_relative_time":"3600"}]}'`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx new create-passive-sell-offer`
+
+Create a passive sell offer on the Stellar DEX
+
+**Usage:** `stellar tx new create-passive-sell-offer [OPTIONS] --source-account <SOURCE_ACCOUNT> --selling <SELLING> --buying <BUYING> --amount <AMOUNT> --price <PRICE>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--selling <SELLING>` — Asset to sell
+- `--buying <BUYING>` — Asset to buy
+- `--amount <AMOUNT>` — Amount of selling asset to offer, in stroops. 1 stroop = 0.0000001 of the asset (e.g. 1 XLM = `10_000_000` stroops)
+- `--price <PRICE>` — Price of 1 unit of selling asset in terms of buying asset as "numerator:denominator" (e.g., "1:2" means 0.5)
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx new end-sponsoring-future-reserves`
+
+End sponsoring future reserves
+
+**Usage:** `stellar tx new end-sponsoring-future-reserves [OPTIONS] --source-account <SOURCE_ACCOUNT>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx new liquidity-pool-deposit`
+
+Deposit assets into a liquidity pool
+
+**Usage:** `stellar tx new liquidity-pool-deposit [OPTIONS] --source-account <SOURCE_ACCOUNT> --liquidity-pool-id <LIQUIDITY_POOL_ID> --max-amount-a <MAX_AMOUNT_A> --max-amount-b <MAX_AMOUNT_B>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--liquidity-pool-id <LIQUIDITY_POOL_ID>` — Liquidity pool ID to deposit to
+- `--max-amount-a <MAX_AMOUNT_A>` — Maximum amount of the first asset to deposit, in stroops
+- `--max-amount-b <MAX_AMOUNT_B>` — Maximum amount of the second asset to deposit, in stroops
+- `--min-price <MIN_PRICE>` — Minimum price for the first asset in terms of the second asset as "numerator:denominator" (e.g., "1:2" means 0.5)
+
+  Default value: `1:1`
+
+- `--max-price <MAX_PRICE>` — Maximum price for the first asset in terms of the second asset as "numerator:denominator" (e.g., "1:2" means 0.5)
+
+  Default value: `1:1`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx new liquidity-pool-withdraw`
+
+Withdraw assets from a liquidity pool
+
+**Usage:** `stellar tx new liquidity-pool-withdraw [OPTIONS] --source-account <SOURCE_ACCOUNT> --liquidity-pool-id <LIQUIDITY_POOL_ID> --amount <AMOUNT> --min-amount-a <MIN_AMOUNT_A> --min-amount-b <MIN_AMOUNT_B>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--liquidity-pool-id <LIQUIDITY_POOL_ID>` — Liquidity pool ID to withdraw from
+- `--amount <AMOUNT>` — Amount of pool shares to withdraw, in stroops
+- `--min-amount-a <MIN_AMOUNT_A>` — Minimum amount of the first asset to receive, in stroops
+- `--min-amount-b <MIN_AMOUNT_B>` — Minimum amount of the second asset to receive, in stroops
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx new manage-buy-offer`
+
+Create, update, or delete a buy offer
+
+**Usage:** `stellar tx new manage-buy-offer [OPTIONS] --source-account <SOURCE_ACCOUNT> --selling <SELLING> --buying <BUYING> --amount <AMOUNT> --price <PRICE>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--selling <SELLING>` — Asset to sell
+- `--buying <BUYING>` — Asset to buy
+- `--amount <AMOUNT>` — Amount of buying asset to purchase, in stroops. 1 stroop = 0.0000001 of the asset (e.g. 1 XLM = `10_000_000` stroops). Use `0` to remove the offer
+- `--price <PRICE>` — Price of 1 unit of buying asset in terms of selling asset as "numerator:denominator" (e.g., "1:2" means 0.5)
+- `--offer-id <OFFER_ID>` — Offer ID. If 0, will create new offer. Otherwise, will update existing offer
+
+  Default value: `0`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx new manage-data`
+
+Set, modify, or delete account data entries
+
+**Usage:** `stellar tx new manage-data [OPTIONS] --source-account <SOURCE_ACCOUNT> --data-name <DATA_NAME>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--data-name <DATA_NAME>` — String up to 64 bytes long. If this is a new Name it will add the given name/value pair to the account. If this Name is already present then the associated value will be modified
+- `--data-value <DATA_VALUE>` — Up to 64 bytes long hex string If not present then the existing Name will be deleted. If present then this value will be set in the `DataEntry`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx new manage-sell-offer`
+
+Create, update, or delete a sell offer
+
+**Usage:** `stellar tx new manage-sell-offer [OPTIONS] --source-account <SOURCE_ACCOUNT> --selling <SELLING> --buying <BUYING> --amount <AMOUNT> --price <PRICE>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--selling <SELLING>` — Asset to sell
+- `--buying <BUYING>` — Asset to buy
+- `--amount <AMOUNT>` — Amount of selling asset to offer, in stroops. 1 stroop = 0.0000001 of the asset (e.g. 1 XLM = `10_000_000` stroops). Use `0` to remove the offer
+- `--price <PRICE>` — Price of 1 unit of selling asset in terms of buying asset as "numerator:denominator" (e.g., "1:2" means 0.5)
+- `--offer-id <OFFER_ID>` — Offer ID. If 0, will create new offer. Otherwise, will update existing offer
+
+  Default value: `0`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx new path-payment-strict-send`
+
+Send a payment with a different asset using path finding, specifying the send amount
+
+**Usage:** `stellar tx new path-payment-strict-send [OPTIONS] --source-account <SOURCE_ACCOUNT> --send-asset <SEND_ASSET> --send-amount <SEND_AMOUNT> --destination <DESTINATION> --dest-asset <DEST_ASSET> --dest-min <DEST_MIN>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--send-asset <SEND_ASSET>` — Asset to send (pay with)
+- `--send-amount <SEND_AMOUNT>` — Amount of send asset to deduct from sender's account, in stroops. 1 stroop = 0.0000001 of the asset (e.g. 1 XLM = `10_000_000` stroops)
+- `--destination <DESTINATION>` — Account that receives the payment
+- `--dest-asset <DEST_ASSET>` — Asset that the destination will receive
+- `--dest-min <DEST_MIN>` — Minimum amount of destination asset that the destination account can receive. The operation will fail if this amount cannot be met
+- `--path <PATH>` — List of intermediate assets for the payment path, comma-separated (up to 5 assets). Each asset should be in the format 'code:issuer' or 'native' for XLM
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx new path-payment-strict-receive`
+
+Send a payment with a different asset using path finding, specifying the receive amount
+
+**Usage:** `stellar tx new path-payment-strict-receive [OPTIONS] --source-account <SOURCE_ACCOUNT> --send-asset <SEND_ASSET> --send-max <SEND_MAX> --destination <DESTINATION> --dest-asset <DEST_ASSET> --dest-amount <DEST_AMOUNT>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--send-asset <SEND_ASSET>` — Asset to send (pay with)
+- `--send-max <SEND_MAX>` — Maximum amount of send asset to deduct from sender's account, in stroops. 1 stroop = 0.0000001 of the asset (e.g. 1 XLM = `10_000_000` stroops)
+- `--destination <DESTINATION>` — Account that receives the payment
+- `--dest-asset <DEST_ASSET>` — Asset that the destination will receive
+- `--dest-amount <DEST_AMOUNT>` — Exact amount of destination asset that the destination account will receive, in stroops. 1 stroop = 0.0000001 of the asset
+- `--path <PATH>` — List of intermediate assets for the payment path, comma-separated (up to 5 assets). Each asset should be in the format 'code:issuer' or 'native' for XLM
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx new payment`
+
+Send asset to destination account
+
+**Usage:** `stellar tx new payment [OPTIONS] --source-account <SOURCE_ACCOUNT> --destination <DESTINATION> --amount <AMOUNT>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--destination <DESTINATION>` — Account to send to, e.g. `GBX...`
+- `--asset <ASSET>` — Asset to send, default native, e.i. XLM
+
+  Default value: `native`
+
+- `--amount <AMOUNT>` — Amount of the aforementioned asset to send, in stroops. 1 stroop = 0.0000001 of the asset (e.g. 1 XLM = `10_000_000` stroops)
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx new revoke-sponsorship`
+
+Revoke sponsorship of a ledger entry or signer
+
+**Usage:** `stellar tx new revoke-sponsorship [OPTIONS] --source-account <SOURCE_ACCOUNT> --account-id <ACCOUNT_ID>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--account-id <ACCOUNT_ID>` — Account ID (required for all sponsorship types)
+- `--asset <ASSET>` — Asset for trustline sponsorship (format: CODE:ISSUER)
+- `--data-name <DATA_NAME>` — Data name for data entry sponsorship
+- `--offer-id <OFFER_ID>` — Offer ID for offer sponsorship
+- `--liquidity-pool-id <LIQUIDITY_POOL_ID>` — Pool ID for liquidity pool sponsorship. Accepts multiple formats: - API format with type prefix (72 chars): 000000006f2179b31311fa8064760b48942c8e166702ba0b8fbe7358c4fd570421840461 - Direct hash format (64 chars): 6f2179b31311fa8064760b48942c8e166702ba0b8fbe7358c4fd570421840461 - Address format (base32): LAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
+- `--claimable-balance-id <CLAIMABLE_BALANCE_ID>` — Claimable balance ID for claimable balance sponsorship. Accepts multiple formats: - API format with type prefix (72 chars): 000000006f2179b31311fa8064760b48942c8e166702ba0b8fbe7358c4fd570421840461 - Direct hash format (64 chars): 6f2179b31311fa8064760b48942c8e166702ba0b8fbe7358c4fd570421840461 - Address format (base32): BAAMLBZI42AD52HKGIZOU7WFVZM6BPEJCLPL44QU2AT6TY3P57I5QDNYIA
+- `--signer-key <SIGNER_KEY>` — Signer key for signer sponsorship
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx new set-options`
+
+Set account options like flags, signers, and home domain
+
+**Usage:** `stellar tx new set-options [OPTIONS] --source-account <SOURCE_ACCOUNT>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--inflation-dest <INFLATION_DEST>` — Account of the inflation destination
+- `--master-weight <MASTER_WEIGHT>` — A number from 0-255 (inclusive) representing the weight of the master key. If the weight of the master key is updated to 0, it is effectively disabled
+- `--low-threshold <LOW_THRESHOLD>` — A number from 0-255 (inclusive) representing the threshold this account sets on all operations it performs that have a low threshold. https://developers.stellar.org/docs/learn/encyclopedia/security/signatures-multisig#multisig
+- `--med-threshold <MED_THRESHOLD>` — A number from 0-255 (inclusive) representing the threshold this account sets on all operations it performs that have a medium threshold. https://developers.stellar.org/docs/learn/encyclopedia/security/signatures-multisig#multisig
+- `--high-threshold <HIGH_THRESHOLD>` — A number from 0-255 (inclusive) representing the threshold this account sets on all operations it performs that have a high threshold. https://developers.stellar.org/docs/learn/encyclopedia/security/signatures-multisig#multisig
+- `--home-domain <HOME_DOMAIN>` — Sets the home domain of an account. See https://developers.stellar.org/docs/learn/encyclopedia/network-configuration/federation
+- `--signer <SIGNER>` — Add, update, or remove a signer from an account
+- `--signer-weight <SIGNER_WEIGHT>` — Signer weight is a number from 0-255 (inclusive). The signer is deleted if the weight is 0
+- `--set-required` — When enabled, an issuer must approve an account before that account can hold its asset. https://developers.stellar.org/docs/tokens/control-asset-access#authorization-required-0x1
+- `--set-revocable` — When enabled, an issuer can revoke an existing trustline's authorization, thereby freezing the asset held by an account. https://developers.stellar.org/docs/tokens/control-asset-access#authorization-revocable-0x2
+- `--set-clawback-enabled` — Enables the issuing account to take back (burning) all of the asset. https://developers.stellar.org/docs/tokens/control-asset-access#clawback-enabled-0x8
+- `--set-immutable` — With this setting, none of the other authorization flags (`AUTH_REQUIRED_FLAG`, `AUTH_REVOCABLE_FLAG`) can be set, and the issuing account can't be merged. https://developers.stellar.org/docs/tokens/control-asset-access#authorization-immutable-0x4
+- `--clear-required`
+- `--clear-revocable`
+- `--clear-immutable`
+- `--clear-clawback-enabled`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx new set-trustline-flags`
+
+Configure authorization and trustline flags for an asset
+
+**Usage:** `stellar tx new set-trustline-flags [OPTIONS] --source-account <SOURCE_ACCOUNT> --trustor <TRUSTOR> --asset <ASSET>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--trustor <TRUSTOR>` — Account to set trustline flags for, e.g. `GBX...`, or alias, or muxed account, `M123...``
+- `--asset <ASSET>` — Asset to set trustline flags for
+- `--set-authorize` — Signifies complete authorization allowing an account to transact freely with the asset to make and receive payments and place orders
+- `--set-authorize-to-maintain-liabilities` — Denotes limited authorization that allows an account to maintain current orders but not to otherwise transact with the asset
+- `--set-trustline-clawback-enabled` — Enables the issuing account to take back (burning) all of the asset. See our section on Clawbacks: https://developers.stellar.org/docs/learn/encyclopedia/transactions-specialized/clawbacks
+- `--clear-authorize`
+- `--clear-authorize-to-maintain-liabilities`
+- `--clear-trustline-clawback-enabled`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx operation`
+
+Manipulate the operations in a transaction, including adding new operations
+
+**Usage:** `stellar tx operation <COMMAND>`
+
+**Command Alias:** `op`
+
+###### **Subcommands:**
+
+- `add` — Add Operation to a transaction
+
+## `stellar tx operation add`
+
+Add Operation to a transaction
+
+**Usage:** `stellar tx operation add <COMMAND>`
+
+###### **Subcommands:**
+
+- `account-merge` — Transfer XLM balance to another account and remove source account
+- `begin-sponsoring-future-reserves` — Begin sponsoring future reserves for another account
+- `bump-sequence` — Bump sequence number to invalidate older transactions
+- `change-trust` — Create, update, or delete a trustline
+- `claim-claimable-balance` — Claim a claimable balance by its balance ID
+- `clawback` — Clawback an asset from an account
+- `clawback-claimable-balance` — Clawback a claimable balance by its balance ID
+- `create-account` — Create and fund a new account
+- `create-claimable-balance` — Create a claimable balance that can be claimed by specified accounts
+- `create-passive-sell-offer` — Create a passive sell offer on the Stellar DEX
+- `end-sponsoring-future-reserves` — End sponsoring future reserves
+- `liquidity-pool-deposit` — Deposit assets into a liquidity pool
+- `liquidity-pool-withdraw` — Withdraw assets from a liquidity pool
+- `manage-buy-offer` — Create, update, or delete a buy offer
+- `manage-data` — Set, modify, or delete account data entries
+- `manage-sell-offer` — Create, update, or delete a sell offer
+- `path-payment-strict-receive` — Send a payment with a different asset using path finding, specifying the receive amount
+- `path-payment-strict-send` — Send a payment with a different asset using path finding, specifying the send amount
+- `payment` — Send asset to destination account
+- `revoke-sponsorship` — Revoke sponsorship of a ledger entry or signer
+- `set-options` — Set account options like flags, signers, and home domain
+- `set-trustline-flags` — Configure authorization and trustline flags for an asset
+
+## `stellar tx operation add account-merge`
+
+Transfer XLM balance to another account and remove source account
+
+**Usage:** `stellar tx operation add account-merge [OPTIONS] --source-account <SOURCE_ACCOUNT> --account <ACCOUNT> [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR or file containing XDR to decode, or stdin if empty
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Source account used for the operation
+- `--account <ACCOUNT>` — Muxed Account to merge with, e.g. `GBX...`, 'MBX...'
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx operation add begin-sponsoring-future-reserves`
+
+Begin sponsoring future reserves for another account
+
+**Usage:** `stellar tx operation add begin-sponsoring-future-reserves [OPTIONS] --source-account <SOURCE_ACCOUNT> --sponsored-id <SPONSORED_ID> [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR or file containing XDR to decode, or stdin if empty
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Source account used for the operation
+- `--sponsored-id <SPONSORED_ID>` — Account that will be sponsored
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx operation add bump-sequence`
+
+Bump sequence number to invalidate older transactions
+
+**Usage:** `stellar tx operation add bump-sequence [OPTIONS] --source-account <SOURCE_ACCOUNT> --bump-to <BUMP_TO> [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR or file containing XDR to decode, or stdin if empty
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Source account used for the operation
+- `--bump-to <BUMP_TO>` — Sequence number to bump to
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx operation add change-trust`
+
+Create, update, or delete a trustline
+
+**Usage:** `stellar tx operation add change-trust [OPTIONS] --source-account <SOURCE_ACCOUNT> --line <LINE> [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR or file containing XDR to decode, or stdin if empty
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Source account used for the operation
+- `--line <LINE>`
+- `--limit <LIMIT>` — Limit for the trust line, 0 to remove the trust line
+
+  Default value: `9223372036854775807`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx operation add claim-claimable-balance`
+
+Claim a claimable balance by its balance ID
+
+**Usage:** `stellar tx operation add claim-claimable-balance [OPTIONS] --source-account <SOURCE_ACCOUNT> --balance-id <BALANCE_ID> [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR or file containing XDR to decode, or stdin if empty
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Source account used for the operation
+- `--balance-id <BALANCE_ID>` — Balance ID of the claimable balance to claim (64-character hex string)
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx operation add clawback`
+
+Clawback an asset from an account
+
+**Usage:** `stellar tx operation add clawback [OPTIONS] --source-account <SOURCE_ACCOUNT> --from <FROM> --asset <ASSET> --amount <AMOUNT> [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR or file containing XDR to decode, or stdin if empty
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Source account used for the operation
+- `--from <FROM>` — Account to clawback assets from, e.g. `GBX...`
+- `--asset <ASSET>` — Asset to clawback
+- `--amount <AMOUNT>` — Amount of the asset to clawback, in stroops. 1 stroop = 0.0000001 of the asset
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx operation add clawback-claimable-balance`
+
+Clawback a claimable balance by its balance ID
+
+**Usage:** `stellar tx operation add clawback-claimable-balance [OPTIONS] --source-account <SOURCE_ACCOUNT> --balance-id <BALANCE_ID> [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR or file containing XDR to decode, or stdin if empty
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Source account used for the operation
+- `--balance-id <BALANCE_ID>` — Balance ID of the claimable balance to clawback. Accepts multiple formats: - API format with type prefix (72 chars): 000000006f2179b31311fa8064760b48942c8e166702ba0b8fbe7358c4fd570421840461 - Direct hash format (64 chars): 6f2179b31311fa8064760b48942c8e166702ba0b8fbe7358c4fd570421840461 - Address format (base32): BAAMLBZI42AD52HKGIZOU7WFVZM6BPEJCLPL44QU2AT6TY3P57I5QDNYIA
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx operation add create-account`
+
+Create and fund a new account
+
+**Usage:** `stellar tx operation add create-account [OPTIONS] --source-account <SOURCE_ACCOUNT> --destination <DESTINATION> [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR or file containing XDR to decode, or stdin if empty
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Source account used for the operation
+- `--destination <DESTINATION>` — Account Id to create, e.g. `GBX...`
+- `--starting-balance <STARTING_BALANCE>` — Initial balance in stroops of the account, default 1 XLM
+
+  Default value: `10_000_000`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx operation add create-claimable-balance`
+
+Create a claimable balance that can be claimed by specified accounts
+
+**Usage:** `stellar tx operation add create-claimable-balance [OPTIONS] --source-account <SOURCE_ACCOUNT> --amount <AMOUNT> [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR or file containing XDR to decode, or stdin if empty
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Source account used for the operation
+- `--asset <ASSET>` — Asset to be held in the ClaimableBalanceEntry
+
+  Default value: `native`
+
+- `--amount <AMOUNT>` — Amount of asset to store in the entry, in stroops. 1 stroop = 0.0000001 of the asset
+- `--claimant <CLAIMANTS>` — Claimants of the claimable balance. Format: account_id or account_id:predicate_json Can be specified multiple times for multiple claimants.
+
+  Examples:
+  - `--claimant alice (unconditional)` - `--claimant 'bob:{"before_absolute_time":"1735689599"}'` - `--claimant 'charlie:{"and":[{"before_absolute_time":"1735689599"},{"before_relative_time":"3600"}]}'`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx operation add create-passive-sell-offer`
+
+Create a passive sell offer on the Stellar DEX
+
+**Usage:** `stellar tx operation add create-passive-sell-offer [OPTIONS] --source-account <SOURCE_ACCOUNT> --selling <SELLING> --buying <BUYING> --amount <AMOUNT> --price <PRICE> [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR or file containing XDR to decode, or stdin if empty
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Source account used for the operation
+- `--selling <SELLING>` — Asset to sell
+- `--buying <BUYING>` — Asset to buy
+- `--amount <AMOUNT>` — Amount of selling asset to offer, in stroops. 1 stroop = 0.0000001 of the asset (e.g. 1 XLM = `10_000_000` stroops)
+- `--price <PRICE>` — Price of 1 unit of selling asset in terms of buying asset as "numerator:denominator" (e.g., "1:2" means 0.5)
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx operation add end-sponsoring-future-reserves`
+
+End sponsoring future reserves
+
+**Usage:** `stellar tx operation add end-sponsoring-future-reserves [OPTIONS] --source-account <SOURCE_ACCOUNT> [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR or file containing XDR to decode, or stdin if empty
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Source account used for the operation
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx operation add liquidity-pool-deposit`
+
+Deposit assets into a liquidity pool
+
+**Usage:** `stellar tx operation add liquidity-pool-deposit [OPTIONS] --source-account <SOURCE_ACCOUNT> --liquidity-pool-id <LIQUIDITY_POOL_ID> --max-amount-a <MAX_AMOUNT_A> --max-amount-b <MAX_AMOUNT_B> [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR or file containing XDR to decode, or stdin if empty
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Source account used for the operation
+- `--liquidity-pool-id <LIQUIDITY_POOL_ID>` — Liquidity pool ID to deposit to
+- `--max-amount-a <MAX_AMOUNT_A>` — Maximum amount of the first asset to deposit, in stroops
+- `--max-amount-b <MAX_AMOUNT_B>` — Maximum amount of the second asset to deposit, in stroops
+- `--min-price <MIN_PRICE>` — Minimum price for the first asset in terms of the second asset as "numerator:denominator" (e.g., "1:2" means 0.5)
+
+  Default value: `1:1`
+
+- `--max-price <MAX_PRICE>` — Maximum price for the first asset in terms of the second asset as "numerator:denominator" (e.g., "1:2" means 0.5)
+
+  Default value: `1:1`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx operation add liquidity-pool-withdraw`
+
+Withdraw assets from a liquidity pool
+
+**Usage:** `stellar tx operation add liquidity-pool-withdraw [OPTIONS] --source-account <SOURCE_ACCOUNT> --liquidity-pool-id <LIQUIDITY_POOL_ID> --amount <AMOUNT> --min-amount-a <MIN_AMOUNT_A> --min-amount-b <MIN_AMOUNT_B> [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR or file containing XDR to decode, or stdin if empty
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Source account used for the operation
+- `--liquidity-pool-id <LIQUIDITY_POOL_ID>` — Liquidity pool ID to withdraw from
+- `--amount <AMOUNT>` — Amount of pool shares to withdraw, in stroops
+- `--min-amount-a <MIN_AMOUNT_A>` — Minimum amount of the first asset to receive, in stroops
+- `--min-amount-b <MIN_AMOUNT_B>` — Minimum amount of the second asset to receive, in stroops
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx operation add manage-buy-offer`
+
+Create, update, or delete a buy offer
+
+**Usage:** `stellar tx operation add manage-buy-offer [OPTIONS] --source-account <SOURCE_ACCOUNT> --selling <SELLING> --buying <BUYING> --amount <AMOUNT> --price <PRICE> [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR or file containing XDR to decode, or stdin if empty
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Source account used for the operation
+- `--selling <SELLING>` — Asset to sell
+- `--buying <BUYING>` — Asset to buy
+- `--amount <AMOUNT>` — Amount of buying asset to purchase, in stroops. 1 stroop = 0.0000001 of the asset (e.g. 1 XLM = `10_000_000` stroops). Use `0` to remove the offer
+- `--price <PRICE>` — Price of 1 unit of buying asset in terms of selling asset as "numerator:denominator" (e.g., "1:2" means 0.5)
+- `--offer-id <OFFER_ID>` — Offer ID. If 0, will create new offer. Otherwise, will update existing offer
+
+  Default value: `0`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx operation add manage-data`
+
+Set, modify, or delete account data entries
+
+**Usage:** `stellar tx operation add manage-data [OPTIONS] --source-account <SOURCE_ACCOUNT> --data-name <DATA_NAME> [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR or file containing XDR to decode, or stdin if empty
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Source account used for the operation
+- `--data-name <DATA_NAME>` — String up to 64 bytes long. If this is a new Name it will add the given name/value pair to the account. If this Name is already present then the associated value will be modified
+- `--data-value <DATA_VALUE>` — Up to 64 bytes long hex string If not present then the existing Name will be deleted. If present then this value will be set in the `DataEntry`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx operation add manage-sell-offer`
+
+Create, update, or delete a sell offer
+
+**Usage:** `stellar tx operation add manage-sell-offer [OPTIONS] --source-account <SOURCE_ACCOUNT> --selling <SELLING> --buying <BUYING> --amount <AMOUNT> --price <PRICE> [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR or file containing XDR to decode, or stdin if empty
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Source account used for the operation
+- `--selling <SELLING>` — Asset to sell
+- `--buying <BUYING>` — Asset to buy
+- `--amount <AMOUNT>` — Amount of selling asset to offer, in stroops. 1 stroop = 0.0000001 of the asset (e.g. 1 XLM = `10_000_000` stroops). Use `0` to remove the offer
+- `--price <PRICE>` — Price of 1 unit of selling asset in terms of buying asset as "numerator:denominator" (e.g., "1:2" means 0.5)
+- `--offer-id <OFFER_ID>` — Offer ID. If 0, will create new offer. Otherwise, will update existing offer
+
+  Default value: `0`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx operation add path-payment-strict-receive`
+
+Send a payment with a different asset using path finding, specifying the receive amount
+
+**Usage:** `stellar tx operation add path-payment-strict-receive [OPTIONS] --source-account <SOURCE_ACCOUNT> --send-asset <SEND_ASSET> --send-max <SEND_MAX> --destination <DESTINATION> --dest-asset <DEST_ASSET> --dest-amount <DEST_AMOUNT> [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR or file containing XDR to decode, or stdin if empty
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Source account used for the operation
+- `--send-asset <SEND_ASSET>` — Asset to send (pay with)
+- `--send-max <SEND_MAX>` — Maximum amount of send asset to deduct from sender's account, in stroops. 1 stroop = 0.0000001 of the asset (e.g. 1 XLM = `10_000_000` stroops)
+- `--destination <DESTINATION>` — Account that receives the payment
+- `--dest-asset <DEST_ASSET>` — Asset that the destination will receive
+- `--dest-amount <DEST_AMOUNT>` — Exact amount of destination asset that the destination account will receive, in stroops. 1 stroop = 0.0000001 of the asset
+- `--path <PATH>` — List of intermediate assets for the payment path, comma-separated (up to 5 assets). Each asset should be in the format 'code:issuer' or 'native' for XLM
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx operation add path-payment-strict-send`
+
+Send a payment with a different asset using path finding, specifying the send amount
+
+**Usage:** `stellar tx operation add path-payment-strict-send [OPTIONS] --source-account <SOURCE_ACCOUNT> --send-asset <SEND_ASSET> --send-amount <SEND_AMOUNT> --destination <DESTINATION> --dest-asset <DEST_ASSET> --dest-min <DEST_MIN> [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR or file containing XDR to decode, or stdin if empty
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Source account used for the operation
+- `--send-asset <SEND_ASSET>` — Asset to send (pay with)
+- `--send-amount <SEND_AMOUNT>` — Amount of send asset to deduct from sender's account, in stroops. 1 stroop = 0.0000001 of the asset (e.g. 1 XLM = `10_000_000` stroops)
+- `--destination <DESTINATION>` — Account that receives the payment
+- `--dest-asset <DEST_ASSET>` — Asset that the destination will receive
+- `--dest-min <DEST_MIN>` — Minimum amount of destination asset that the destination account can receive. The operation will fail if this amount cannot be met
+- `--path <PATH>` — List of intermediate assets for the payment path, comma-separated (up to 5 assets). Each asset should be in the format 'code:issuer' or 'native' for XLM
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx operation add payment`
+
+Send asset to destination account
+
+**Usage:** `stellar tx operation add payment [OPTIONS] --source-account <SOURCE_ACCOUNT> --destination <DESTINATION> --amount <AMOUNT> [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR or file containing XDR to decode, or stdin if empty
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Source account used for the operation
+- `--destination <DESTINATION>` — Account to send to, e.g. `GBX...`
+- `--asset <ASSET>` — Asset to send, default native, e.i. XLM
+
+  Default value: `native`
+
+- `--amount <AMOUNT>` — Amount of the aforementioned asset to send, in stroops. 1 stroop = 0.0000001 of the asset (e.g. 1 XLM = `10_000_000` stroops)
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx operation add revoke-sponsorship`
+
+Revoke sponsorship of a ledger entry or signer
+
+**Usage:** `stellar tx operation add revoke-sponsorship [OPTIONS] --source-account <SOURCE_ACCOUNT> --account-id <ACCOUNT_ID> [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR or file containing XDR to decode, or stdin if empty
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Source account used for the operation
+- `--account-id <ACCOUNT_ID>` — Account ID (required for all sponsorship types)
+- `--asset <ASSET>` — Asset for trustline sponsorship (format: CODE:ISSUER)
+- `--data-name <DATA_NAME>` — Data name for data entry sponsorship
+- `--offer-id <OFFER_ID>` — Offer ID for offer sponsorship
+- `--liquidity-pool-id <LIQUIDITY_POOL_ID>` — Pool ID for liquidity pool sponsorship. Accepts multiple formats: - API format with type prefix (72 chars): 000000006f2179b31311fa8064760b48942c8e166702ba0b8fbe7358c4fd570421840461 - Direct hash format (64 chars): 6f2179b31311fa8064760b48942c8e166702ba0b8fbe7358c4fd570421840461 - Address format (base32): LAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
+- `--claimable-balance-id <CLAIMABLE_BALANCE_ID>` — Claimable balance ID for claimable balance sponsorship. Accepts multiple formats: - API format with type prefix (72 chars): 000000006f2179b31311fa8064760b48942c8e166702ba0b8fbe7358c4fd570421840461 - Direct hash format (64 chars): 6f2179b31311fa8064760b48942c8e166702ba0b8fbe7358c4fd570421840461 - Address format (base32): BAAMLBZI42AD52HKGIZOU7WFVZM6BPEJCLPL44QU2AT6TY3P57I5QDNYIA
+- `--signer-key <SIGNER_KEY>` — Signer key for signer sponsorship
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx operation add set-options`
+
+Set account options like flags, signers, and home domain
+
+**Usage:** `stellar tx operation add set-options [OPTIONS] --source-account <SOURCE_ACCOUNT> [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR or file containing XDR to decode, or stdin if empty
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Source account used for the operation
+- `--inflation-dest <INFLATION_DEST>` — Account of the inflation destination
+- `--master-weight <MASTER_WEIGHT>` — A number from 0-255 (inclusive) representing the weight of the master key. If the weight of the master key is updated to 0, it is effectively disabled
+- `--low-threshold <LOW_THRESHOLD>` — A number from 0-255 (inclusive) representing the threshold this account sets on all operations it performs that have a low threshold. https://developers.stellar.org/docs/learn/encyclopedia/security/signatures-multisig#multisig
+- `--med-threshold <MED_THRESHOLD>` — A number from 0-255 (inclusive) representing the threshold this account sets on all operations it performs that have a medium threshold. https://developers.stellar.org/docs/learn/encyclopedia/security/signatures-multisig#multisig
+- `--high-threshold <HIGH_THRESHOLD>` — A number from 0-255 (inclusive) representing the threshold this account sets on all operations it performs that have a high threshold. https://developers.stellar.org/docs/learn/encyclopedia/security/signatures-multisig#multisig
+- `--home-domain <HOME_DOMAIN>` — Sets the home domain of an account. See https://developers.stellar.org/docs/learn/encyclopedia/network-configuration/federation
+- `--signer <SIGNER>` — Add, update, or remove a signer from an account
+- `--signer-weight <SIGNER_WEIGHT>` — Signer weight is a number from 0-255 (inclusive). The signer is deleted if the weight is 0
+- `--set-required` — When enabled, an issuer must approve an account before that account can hold its asset. https://developers.stellar.org/docs/tokens/control-asset-access#authorization-required-0x1
+- `--set-revocable` — When enabled, an issuer can revoke an existing trustline's authorization, thereby freezing the asset held by an account. https://developers.stellar.org/docs/tokens/control-asset-access#authorization-revocable-0x2
+- `--set-clawback-enabled` — Enables the issuing account to take back (burning) all of the asset. https://developers.stellar.org/docs/tokens/control-asset-access#clawback-enabled-0x8
+- `--set-immutable` — With this setting, none of the other authorization flags (`AUTH_REQUIRED_FLAG`, `AUTH_REVOCABLE_FLAG`) can be set, and the issuing account can't be merged. https://developers.stellar.org/docs/tokens/control-asset-access#authorization-immutable-0x4
+- `--clear-required`
+- `--clear-revocable`
+- `--clear-immutable`
+- `--clear-clawback-enabled`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx operation add set-trustline-flags`
+
+Configure authorization and trustline flags for an asset
+
+**Usage:** `stellar tx operation add set-trustline-flags [OPTIONS] --source-account <SOURCE_ACCOUNT> --trustor <TRUSTOR> --asset <ASSET> [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR or file containing XDR to decode, or stdin if empty
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Source account used for the operation
+- `--trustor <TRUSTOR>` — Account to set trustline flags for, e.g. `GBX...`, or alias, or muxed account, `M123...``
+- `--asset <ASSET>` — Asset to set trustline flags for
+- `--set-authorize` — Signifies complete authorization allowing an account to transact freely with the asset to make and receive payments and place orders
+- `--set-authorize-to-maintain-liabilities` — Denotes limited authorization that allows an account to maintain current orders but not to otherwise transact with the asset
+- `--set-trustline-clawback-enabled` — Enables the issuing account to take back (burning) all of the asset. See our section on Clawbacks: https://developers.stellar.org/docs/learn/encyclopedia/transactions-specialized/clawbacks
+- `--clear-authorize`
+- `--clear-authorize-to-maintain-liabilities`
+- `--clear-trustline-clawback-enabled`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+- `--build-only` — Build the transaction and only write the base64 xdr to stdout
+
+## `stellar tx send`
+
+Send a transaction envelope to the network
+
+**Usage:** `stellar tx send [OPTIONS] [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR or file containing XDR to decode, or stdin if empty
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar tx sign`
+
+Sign a transaction envelope appending the signature to the envelope
+
+**Usage:** `stellar tx sign [OPTIONS] [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR, or file containing XDR to decode, or stdin if empty
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+## `stellar tx simulate`
+
+Simulate a transaction envelope from stdin
+
+**Usage:** `stellar tx simulate [OPTIONS] --source-account <SOURCE_ACCOUNT> [TX_XDR]`
+
+###### **Arguments:**
+
+- `<TX_XDR>` — Base-64 transaction envelope XDR or file containing XDR to decode, or stdin if empty
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Allow this many extra instructions when budgeting resources during transaction simulation
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+- `--auth-mode <AUTH_MODE>` — Set the authorization mode for transaction simulation. When unset, the RPC default is used: record with the root mode if no authorization entries exist, otherwise enforce the provided entries. Should only be set for `InvokeHostFunction` transactions. The `enforce` mode is for simulating transactions that already contain authorization entries
+
+  Possible values:
+  - `enforce`: Validate the authorization entries already on the transaction
+  - `root`: Record authorization entries, requiring each to be rooted at the transaction's top-level operation
+  - `non-root`: Record all authorization entries, including non-root entries
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+- `--sign-with-lab` — Sign with https://lab.stellar.org
+- `--sign-with-ledger` — Sign with a ledger wallet
+- `--auto-sign` — Sign without prompting for approval. Only applies to signatures that require user approval, like non-root Soroban auth entries
+
+###### **Transaction Options:**
+
+- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Account that where transaction originates from. Alias `source`. Can be an identity (--source alice), a public key (--source GDKW...), a muxed account (--source MDA…), a secret key (--source SC36…), or a seed phrase (--source "kite urban…"). If `--build-only` was NOT provided, this key will also be used to sign the final transaction. In that case, trying to sign with public key will fail
+- `--fee <FEE>` — ⚠️ Deprecated, use `--inclusion-fee`. Fee amount for transaction, in stroops. 1 stroop = 0.0000001 xlm
+- `--inclusion-fee <INCLUSION_FEE>` — Maximum fee amount for transaction inclusion, in stroops. 1 stroop = 0.0000001 xlm. Defaults to 100 if no arg, env, or config value is provided
+
+## `stellar tx fetch`
+
+Fetch a transaction from the network by hash If no subcommand is passed in, the transaction envelope will be returned
+
+**Usage:** `stellar tx fetch [OPTIONS]        fetch <COMMAND>`
+
+###### **Subcommands:**
+
+- `result` — Fetch the transaction result
+- `meta` — Fetch the transaction meta
+- `fee` — Fetch the transaction fee information
+- `events` — Fetch the transaction events
+
+###### **Options:**
+
+- `--hash <HASH>` — Hash of transaction to fetch
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `json`
+
+  Possible values:
+  - `json`: JSON output with parsed XDRs (one line, not formatted)
+  - `json-formatted`: Formatted (multiline) JSON output with parsed XDRs
+  - `xdr`: Original RPC output (containing XDRs)
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar tx fetch result`
+
+Fetch the transaction result
+
+**Usage:** `stellar tx fetch result [OPTIONS] --hash <HASH>`
+
+###### **Options:**
+
+- `--hash <HASH>` — Transaction hash to fetch
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `json`
+
+  Possible values:
+  - `json`: JSON output with parsed XDRs (one line, not formatted)
+  - `json-formatted`: Formatted (multiline) JSON output with parsed XDRs
+  - `xdr`: Original RPC output (containing XDRs)
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar tx fetch meta`
+
+Fetch the transaction meta
+
+**Usage:** `stellar tx fetch meta [OPTIONS] --hash <HASH>`
+
+###### **Options:**
+
+- `--hash <HASH>` — Transaction hash to fetch
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `json`
+
+  Possible values:
+  - `json`: JSON output with parsed XDRs (one line, not formatted)
+  - `json-formatted`: Formatted (multiline) JSON output with parsed XDRs
+  - `xdr`: Original RPC output (containing XDRs)
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar tx fetch fee`
+
+Fetch the transaction fee information
+
+**Usage:** `stellar tx fetch fee [OPTIONS] --hash <HASH>`
+
+###### **Options:**
+
+- `--hash <HASH>` — Transaction hash to fetch
+- `--output <OUTPUT>` — Output format for fee command
+
+  Default value: `table`
+
+  Possible values:
+  - `json`: JSON output of the ledger entry with parsed XDRs (one line, not formatted)
+  - `json-formatted`: Formatted (multiline) JSON output of the ledger entry with parsed XDRs
+  - `table`: Formatted in a table comparing fee types
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar tx fetch events`
+
+Fetch the transaction events
+
+**Usage:** `stellar tx fetch events [OPTIONS] --hash <HASH>`
+
+###### **Options:**
+
+- `--hash <HASH>` — Transaction hash to fetch
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `json`
+
+  Possible values:
+  - `json`: JSON output of the events with parsed XDRs (one line, not formatted)
+  - `json-formatted`: Formatted (multiline) JSON output of events with parsed XDRs
+  - `text`: Human readable event output with parsed XDRs
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar tx decode`
+
+Decode a transaction envelope from XDR to JSON
+
+**Usage:** `stellar tx decode [OPTIONS] [INPUT]...`
+
+###### **Arguments:**
+
+- `<INPUT>` — XDR or files containing XDR to decode, or stdin if empty
+
+###### **Options:**
+
+- `--input <INPUT_FORMAT>`
+
+  Default value: `single-base64`
+
+  Possible values: `single-base64`, `single`
+
+- `--output <OUTPUT_FORMAT>`
+
+  Default value: `json`
+
+  Possible values: `json`, `json-formatted`
+
+## `stellar tx encode`
+
+Encode a transaction envelope from JSON to XDR
+
+**Usage:** `stellar tx encode [OPTIONS] [INPUT]...`
+
+###### **Arguments:**
+
+- `<INPUT>` — XDR or files containing XDR to decode, or stdin if empty
+
+###### **Options:**
+
+- `--input <INPUT_FORMAT>`
+
+  Default value: `json`
+
+  Possible values: `json`
+
+- `--output <OUTPUT_FORMAT>`
+
+  Default value: `single-base64`
+
+  Possible values: `single-base64`, `single`
+
+## `stellar xdr`
+
+Decode and encode XDR
+
+**Usage:** `stellar xdr <COMMAND>`
+
+###### **Subcommands:**
+
+- `types` — View information about types
+- `guess` — Guess the XDR type
+- `decode` — Decode XDR
+- `encode` — Encode XDR
+- `compare` — Compare two XDR values with each other
+- `generate` — Generate XDR values
+- `xfile` — Preprocess XDR .x files
+- `version` — Print version information
+
+## `stellar xdr types`
+
+View information about types
+
+**Usage:** `stellar xdr types <COMMAND>`
+
+###### **Subcommands:**
+
+- `list` —
+- `schema` —
+- `schema-files` — Generate JSON schema files for the XDR types, writing a file for each type to the out directory
+
+## `stellar xdr types list`
+
+**Usage:** `stellar xdr types list [OPTIONS]`
+
+###### **Options:**
+
+- `--output <OUTPUT>`
+
+  Default value: `plain`
+
+  Possible values: `plain`, `json`, `json-formatted`
+
+## `stellar xdr types schema`
+
+**Usage:** `stellar xdr types schema [OPTIONS] --type <TYPE>`
+
+###### **Options:**
+
+- `--type <TYPE>` — XDR type to generate schema for
+- `--output <OUTPUT>`
+
+  Default value: `json-schema-draft201909`
+
+  Possible values: `json-schema-draft201909`
+
+## `stellar xdr types schema-files`
+
+Generate JSON schema files for the XDR types, writing a file for each type to the out directory
+
+**Usage:** `stellar xdr types schema-files [OPTIONS] --out-dir <OUT_DIR>`
+
+###### **Options:**
+
+- `--out-dir <OUT_DIR>`
+- `--output <OUTPUT>`
+
+  Default value: `json-schema-draft201909`
+
+  Possible values: `json-schema-draft201909`
+
+## `stellar xdr guess`
+
+Guess the XDR type.
+
+Prints a list of types that the XDR values can be decoded into.
+
+**Usage:** `stellar xdr guess [OPTIONS] [INPUT]`
+
+###### **Arguments:**
+
+- `<INPUT>` — XDR or file containing XDR to decode, or stdin if empty
+
+###### **Options:**
+
+- `--input <INPUT_FORMAT>`
+
+  Default value: `single-base64`
+
+  Possible values: `single`, `single-base64`, `stream`, `stream-base64`, `stream-framed`
+
+- `--output <OUTPUT_FORMAT>`
+
+  Default value: `list`
+
+  Possible values: `list`
+
+- `--certainty <CERTAINTY>` — Certainty as an arbitrary value
+
+  Default value: `2`
+
+## `stellar xdr decode`
+
+Decode XDR
+
+**Usage:** `stellar xdr decode [OPTIONS] --type <TYPE> [INPUT]...`
+
+###### **Arguments:**
+
+- `<INPUT>` — XDR or files containing XDR to decode, or stdin if empty
+
+###### **Options:**
+
+- `--type <TYPE>` — XDR type to decode
+- `--input <INPUT_FORMAT>`
+
+  Default value: `stream-base64`
+
+  Possible values: `single`, `single-base64`, `stream`, `stream-base64`, `stream-framed`
+
+- `--output <OUTPUT_FORMAT>`
+
+  Default value: `json`
+
+  Possible values: `json`, `json-formatted`, `text`, `rust-debug`, `rust-debug-formatted`
+
+## `stellar xdr encode`
+
+Encode XDR
+
+**Usage:** `stellar xdr encode [OPTIONS] --type <TYPE> [INPUT]...`
+
+###### **Arguments:**
+
+- `<INPUT>` — XDR or files containing XDR to decode, or stdin if empty
+
+###### **Options:**
+
+- `--type <TYPE>` — XDR type to encode
+- `--input <INPUT_FORMAT>`
+
+  Default value: `json`
+
+  Possible values: `json`
+
+- `--output <OUTPUT_FORMAT>`
+
+  Default value: `single-base64`
+
+  Possible values: `single`, `single-base64`, `stream`
+
+## `stellar xdr compare`
+
+Compare two XDR values with each other
+
+Outputs: `-1` when the left XDR value is less than the right XDR value, `0` when the left XDR value is equal to the right XDR value, `1` when the left XDR value is greater than the right XDR value
+
+**Usage:** `stellar xdr compare [OPTIONS] --type <TYPE> <LEFT> <RIGHT>`
+
+###### **Arguments:**
+
+- `<LEFT>` — XDR file to decode and compare with the right value
+- `<RIGHT>` — XDR file to decode and compare with the left value
+
+###### **Options:**
+
+- `--type <TYPE>` — XDR type of both inputs
+- `--input <INPUT>`
+
+  Default value: `single-base64`
+
+  Possible values: `single`, `single-base64`
+
+## `stellar xdr generate`
+
+Generate XDR values
+
+**Usage:** `stellar xdr generate <COMMAND>`
+
+###### **Subcommands:**
+
+- `default` — Generate default XDR values
+- `arbitrary` — Generate arbitrary XDR values
+
+## `stellar xdr generate default`
+
+Generate default XDR values
+
+**Usage:** `stellar xdr generate default [OPTIONS] --type <TYPE>`
+
+###### **Options:**
+
+- `--type <TYPE>` — XDR type to generate
+- `--output <OUTPUT_FORMAT>`
+
+  Default value: `single-base64`
+
+  Possible values: `single`, `single-base64`, `json`, `json-formatted`, `text`
+
+## `stellar xdr generate arbitrary`
+
+Generate arbitrary XDR values
+
+**Usage:** `stellar xdr generate arbitrary [OPTIONS] --type <TYPE>`
+
+###### **Options:**
+
+- `--type <TYPE>` — XDR type to generate
+- `--output <OUTPUT_FORMAT>`
+
+  Default value: `single-base64`
+
+  Possible values: `single`, `single-base64`, `json`, `json-formatted`, `text`
+
+- `--hint <HINT>` — Keep generating values until the value's JSON representation contains this string. Useful for hinting toward a particular union/enum variant or sub-value. Repeat the flag to require several substrings; all of them must be present in the same value
+- `--hint-attempts <HINT_ATTEMPTS>` — Maximum number of generation attempts when --hint is set before giving up
+
+  Default value: `20000`
+
+## `stellar xdr xfile`
+
+Preprocess XDR .x files
+
+**Usage:** `stellar xdr xfile <COMMAND>`
+
+###### **Subcommands:**
+
+- `preprocess` — Preprocess XDR .x files by evaluating #ifdef/#ifndef/#elif/#else/#endif directives
+
+## `stellar xdr xfile preprocess`
+
+Preprocess XDR .x files by evaluating #ifdef/#ifndef/#elif/#else/#endif directives
+
+**Usage:** `stellar xdr xfile preprocess [OPTIONS] [INPUT]`
+
+###### **Arguments:**
+
+- `<INPUT>` — XDR .x file to preprocess, or stdin if omitted
+
+###### **Options:**
+
+- `--features <FEATURES>` — Features/symbols to define
+- `--all-features` — Enable all features/symbols found in the input
+
+## `stellar xdr version`
+
+Print version information
+
+**Usage:** `stellar xdr version`
+
+## `stellar strkey`
+
+Decode and encode strkey
+
+**Usage:** `stellar strkey [OPTIONS] <COMMAND>`
+
+###### **Subcommands:**
+
+- `decode` — Decode strkey
+- `encode` — Encode strkey
+- `zero` — Generate the zero strkey
+- `version` — Print version information
+
+###### **Options:**
+
+- `-q`, `--quiet` — Suppress stderr log and warning output
+
+## `stellar strkey decode`
+
+Decode strkey
+
+Reads the strkey from stdin.
+
+**Usage:** `stellar strkey decode`
+
+## `stellar strkey encode`
+
+Encode strkey
+
+Reads the JSON from stdin.
+
+**Usage:** `stellar strkey encode`
+
+## `stellar strkey zero`
+
+Generate the zero strkey
+
+**Usage:** `stellar strkey zero [OPTIONS] <STRKEY>`
+
+###### **Arguments:**
+
+- `<STRKEY>` — Strkey type to generate the zero value for
+
+  Possible values: `public_key_ed25519`, `pre_auth_tx`, `hash_x`, `muxed_account_ed25519`, `signed_payload_ed25519`, `contract`, `liquidity_pool`, `claimable_balance_v0`
+
+###### **Options:**
+
+- `--output <OUTPUT>` — Output format
+
+  Default value: `strkey`
+
+  Possible values: `strkey`, `json`
+
+## `stellar strkey version`
+
+Print version information
+
+**Usage:** `stellar strkey version`
+
+## `stellar completion`
+
+Print shell completion code for the specified shell
+
+Ensure the completion package for your shell is installed, e.g. bash-completion for bash.
+
+To enable autocomplete in the current bash shell, run: `source <(stellar completion --shell bash)`
+
+To enable autocomplete permanently, run: `echo "source <(stellar completion --shell bash)" >> ~/.bashrc`
+
+**Usage:** `stellar completion --shell <SHELL>`
+
+###### **Options:**
+
+- `--shell <SHELL>` — The shell type
+
+  Possible values: `bash`, `elvish`, `fish`, `powershell`, `zsh`
+
+## `stellar cache`
+
+Cache for transactions and contract specs
+
+**Usage:** `stellar cache <COMMAND>`
+
+###### **Subcommands:**
+
+- `clean` — Delete the cache
+- `path` — Show the location of the cache
+- `actionlog` — Access details about cached actions like transactions, and simulations. (Experimental. May see breaking changes at any time.)
+
+## `stellar cache clean`
+
+Delete the cache
+
+**Usage:** `stellar cache clean`
+
+## `stellar cache path`
+
+Show the location of the cache
+
+**Usage:** `stellar cache path`
+
+## `stellar cache actionlog`
+
+Access details about cached actions like transactions, and simulations. (Experimental. May see breaking changes at any time.)
+
+**Usage:** `stellar cache actionlog <COMMAND>`
+
+###### **Subcommands:**
+
+- `ls` — List cached actions (transactions, simulations)
+- `read` — Read cached action
+
+## `stellar cache actionlog ls`
+
+List cached actions (transactions, simulations)
+
+**Usage:** `stellar cache actionlog ls [OPTIONS]`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `-l`, `--long`
+
+## `stellar cache actionlog read`
+
+Read cached action
+
+**Usage:** `stellar cache actionlog read --id <ID>`
+
+###### **Options:**
+
+- `--id <ID>` — ID of the cache entry
+
+## `stellar version`
+
+Print version information
+
+**Usage:** `stellar version [OPTIONS]`
+
+###### **Options:**
+
+- `--only-version` — Print only the version
+- `--only-version-major` — Print only the major version
+- `--only-commit` — Print only the commit sha
+
+## `stellar skill`
+
+Print an AI-agent skill guide for using the Stellar CLI
+
+Outputs a Markdown document describing how to use the Stellar CLI idiomatically. It is meant to be read by AI coding agents (or pasted into their instructions) so they follow the CLI's conventions: using named networks, identities, and contract aliases instead of raw RPC URLs, secret keys, and hard-coded contract ids.
+
+**Usage:** `stellar skill`
+
+## `stellar plugin`
+
+The subcommand for CLI plugins
+
+**Usage:** `stellar plugin <COMMAND>`
+
+###### **Subcommands:**
+
+- `search` — Search for CLI plugins using GitHub
+- `ls` — List installed plugins
+
+## `stellar plugin search`
+
+Search for CLI plugins using GitHub
+
+**Usage:** `stellar plugin search`
+
+## `stellar plugin ls`
+
+List installed plugins
+
+**Usage:** `stellar plugin ls`
+
+## `stellar ledger`
+
+Fetch ledger information
+
+**Usage:** `stellar ledger <COMMAND>`
+
+###### **Subcommands:**
+
+- `entry` — Work with ledger entries
+- `latest` — Get the latest ledger sequence and information from the network
+- `fetch` —
+
+## `stellar ledger entry`
+
+Work with ledger entries
+
+**Usage:** `stellar ledger entry <COMMAND>`
+
+###### **Subcommands:**
+
+- `fetch` — Fetch ledger entries. This command supports all types of ledger entries supported by the RPC. Read more about the RPC command here: [https://developers.stellar.org/docs/data/apis/rpc/api-reference/methods/getLedgerEntries#types-of-ledgerkeys](https://developers.stellar.org/docs/data/apis/rpc/api-reference/methods/getLedgerEntries#types-of-ledgerkeys)
+
+## `stellar ledger entry fetch`
+
+Fetch ledger entries. This command supports all types of ledger entries supported by the RPC. Read more about the RPC command here: [https://developers.stellar.org/docs/data/apis/rpc/api-reference/methods/getLedgerEntries#types-of-ledgerkeys](https://developers.stellar.org/docs/data/apis/rpc/api-reference/methods/getLedgerEntries#types-of-ledgerkeys)
+
+**Usage:** `stellar ledger entry fetch <COMMAND>`
+
+###### **Subcommands:**
+
+- `account` — Fetch account entry by public key or alias
+- `contract-data` — Fetch contract ledger entry by address or alias and storage key
+- `claimable-balance` — Fetch a claimable balance ledger entry by id
+- `liquidity-pool` — Fetch a liquidity pool ledger entry by id
+- `contract-code` — Fetch a Contract's WASM bytecode by WASM hash
+- `trustline` — Fetch a trustline by account and asset
+- `data` — Fetch key-value data entries attached to an account (see manageDataOp)
+- `offer` — Fetch an offer by account and offer id
+
+## `stellar ledger entry fetch account`
+
+Fetch account entry by public key or alias
+
+**Usage:** `stellar ledger entry fetch account [OPTIONS] --account <ACCOUNT>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--account <ACCOUNT>` — Account alias or address to lookup
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `json`
+
+  Possible values:
+  - `json`: JSON output of the ledger entry with parsed XDRs (one line, not formatted)
+  - `json-formatted`: Formatted (multiline) JSON output of the ledger entry with parsed XDRs
+  - `xdr`: Original RPC output (containing XDRs)
+
+- `--hd-path <HD_PATH>` — If identity is a seed phrase use this hd path, default is 0
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar ledger entry fetch contract-data`
+
+Fetch contract ledger entry by address or alias and storage key
+
+**Usage:** `stellar ledger entry fetch contract-data [OPTIONS] --contract <CONTRACT>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--contract <CONTRACT>` — Contract alias or address to fetch
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `json`
+
+  Possible values:
+  - `json`: JSON output of the ledger entry with parsed XDRs (one line, not formatted)
+  - `json-formatted`: Formatted (multiline) JSON output of the ledger entry with parsed XDRs
+  - `xdr`: Original RPC output (containing XDRs)
+
+- `--durability <DURABILITY>` — Storage entry durability
+
+  Default value: `persistent`
+
+  Possible values:
+  - `persistent`: Persistent
+  - `temporary`: Temporary
+
+- `--key <KEY>` — Storage key (symbols only)
+- `--key-xdr <KEY_XDR>` — Storage key (base64-encoded XDR)
+- `--instance` — If the contract instance ledger entry should be included in the output
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar ledger entry fetch claimable-balance`
+
+Fetch a claimable balance ledger entry by id
+
+**Usage:** `stellar ledger entry fetch claimable-balance [OPTIONS]`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--id <ID>` — Claimable Balance Ids to fetch an entry for
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `json`
+
+  Possible values:
+  - `json`: JSON output of the ledger entry with parsed XDRs (one line, not formatted)
+  - `json-formatted`: Formatted (multiline) JSON output of the ledger entry with parsed XDRs
+  - `xdr`: Original RPC output (containing XDRs)
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar ledger entry fetch liquidity-pool`
+
+Fetch a liquidity pool ledger entry by id
+
+**Usage:** `stellar ledger entry fetch liquidity-pool [OPTIONS]`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--id <ID>` — Liquidity pool ids
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `json`
+
+  Possible values:
+  - `json`: JSON output of the ledger entry with parsed XDRs (one line, not formatted)
+  - `json-formatted`: Formatted (multiline) JSON output of the ledger entry with parsed XDRs
+  - `xdr`: Original RPC output (containing XDRs)
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar ledger entry fetch contract-code`
+
+Fetch a Contract's WASM bytecode by WASM hash
+
+**Usage:** `stellar ledger entry fetch contract-code [OPTIONS]`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--wasm-hash <WASM_HASH>` — Get WASM bytecode by hash
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `json`
+
+  Possible values:
+  - `json`: JSON output of the ledger entry with parsed XDRs (one line, not formatted)
+  - `json-formatted`: Formatted (multiline) JSON output of the ledger entry with parsed XDRs
+  - `xdr`: Original RPC output (containing XDRs)
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar ledger entry fetch trustline`
+
+Fetch a trustline by account and asset
+
+**Usage:** `stellar ledger entry fetch trustline [OPTIONS] --account <ACCOUNT> --asset <ASSET>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `json`
+
+  Possible values:
+  - `json`: JSON output of the ledger entry with parsed XDRs (one line, not formatted)
+  - `json-formatted`: Formatted (multiline) JSON output of the ledger entry with parsed XDRs
+  - `xdr`: Original RPC output (containing XDRs)
+
+- `--account <ACCOUNT>` — Account alias or address to lookup
+- `--asset <ASSET>` — Assets to get trustline info for
+- `--hd-path <HD_PATH>` — If account is a seed phrase use this hd path, default is 0
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar ledger entry fetch data`
+
+Fetch key-value data entries attached to an account (see manageDataOp)
+
+**Usage:** `stellar ledger entry fetch data [OPTIONS] --account <ACCOUNT> --data-name <DATA_NAME>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `json`
+
+  Possible values:
+  - `json`: JSON output of the ledger entry with parsed XDRs (one line, not formatted)
+  - `json-formatted`: Formatted (multiline) JSON output of the ledger entry with parsed XDRs
+  - `xdr`: Original RPC output (containing XDRs)
+
+- `--account <ACCOUNT>` — Account alias or address to lookup
+- `--data-name <DATA_NAME>` — Fetch key-value data entries attached to an account (see manageDataOp)
+- `--hd-path <HD_PATH>` — If identity is a seed phrase use this hd path, default is 0
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar ledger entry fetch offer`
+
+Fetch an offer by account and offer id
+
+**Usage:** `stellar ledger entry fetch offer [OPTIONS] --account <ACCOUNT> --offer <OFFER>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `json`
+
+  Possible values:
+  - `json`: JSON output of the ledger entry with parsed XDRs (one line, not formatted)
+  - `json-formatted`: Formatted (multiline) JSON output of the ledger entry with parsed XDRs
+  - `xdr`: Original RPC output (containing XDRs)
+
+- `--account <ACCOUNT>` — Account alias or address to lookup
+- `--offer <OFFER>` — ID of an offer made on the Stellar DEX
+- `--hd-path <HD_PATH>` — If identity is a seed phrase use this hd path, default is 0
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar ledger latest`
+
+Get the latest ledger sequence and information from the network
+
+**Usage:** `stellar ledger latest [OPTIONS]`
+
+###### **Options:**
+
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `text`
+
+  Possible values:
+  - `text`: Text output of network info
+  - `json`: JSON result of the RPC request
+  - `json-formatted`: Formatted (multiline) JSON output of the RPC request
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar ledger fetch`
+
+**Usage:** `stellar ledger fetch [OPTIONS] <SEQ>`
+
+###### **Arguments:**
+
+- `<SEQ>` — Ledger Sequence to start fetch (inclusive)
+
+###### **Options:**
+
+- `--limit <LIMIT>` — Number of ledgers to fetch
+
+  Default value: `1`
+
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `text`
+
+  Possible values:
+  - `text`: Text output of network info
+  - `json`: JSON result of the RPC request
+  - `json-formatted`: Formatted (multiline) JSON output of the RPC request
+
+- `--xdr-format <XDR_FORMAT>` — Format of the xdr in the output
+
+  Default value: `json`
+
+  Possible values:
+  - `json`: XDR fields will be fetched as json and accessible via the headerJson and metadataJson fields
+  - `xdr`: XDR fields will be fetched as xdr and accessible via the headerXdr and metadataXdr fields
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar message`
+
+Sign and verify arbitrary messages using SEP-53
+
+**Usage:** `stellar message <COMMAND>`
+
+###### **Subcommands:**
+
+- `sign` — Sign an arbitrary message using SEP-53
+- `verify` — Verify a SEP-53 signed message
+
+## `stellar message sign`
+
+Sign an arbitrary message using SEP-53
+
+Signs a message following the SEP-53 specification for arbitrary message signing. The provided message will get prefixed with "Stellar Signed Message:\n", hashed with SHA-256, and signed with the ed25519 private key.
+
+Example: stellar message sign "Hello, World!" --sign-with-key alice
+
+**Usage:** `stellar message sign [OPTIONS] --sign-with-key <SIGN_WITH_KEY> [MESSAGE]`
+
+###### **Arguments:**
+
+- `<MESSAGE>` — The message to sign. If not provided, reads from stdin. This should **not** include the SEP-53 prefix "Stellar Signed Message:\n", as it will be added automatically
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--base64` — Treat the message as base64-encoded binary data
+
+###### **Signing Options:**
+
+- `--sign-with-key <SIGN_WITH_KEY>` — Sign with a local key or key saved in OS secure storage. Can be an identity (--sign-with-key alice), a secret key (--sign-with-key SC36…), or a seed phrase (--sign-with-key "kite urban…"). If using seed phrase, `--hd-path` defaults to the `0` path
+- `--hd-path <HD_PATH>` — If using a seed phrase to sign, sets which hierarchical deterministic path to use, e.g. `m/44'/148'/{hd_path}`. Example: `--hd-path 1`. Default: `0`
+
+## `stellar message verify`
+
+Verify a SEP-53 signed message
+
+Verifies that a signature was produced by the holder of the private key corresponding to the given account public key, following the SEP-53 specification. The provided message will get prefixed with "Stellar Signed Message:\n" before verification.
+
+Example: stellar message verify "Hello, World!" --signature BASE64_SIG --public-key GABC...
+
+**Usage:** `stellar message verify [OPTIONS] --signature <SIGNATURE> --public-key <PUBLIC_KEY> [MESSAGE]`
+
+###### **Arguments:**
+
+- `<MESSAGE>` — The message to verify. If not provided, reads from stdin. This should **not** include the SEP-53 prefix "Stellar Signed Message:\n", as it will be added automatically
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--base64` — Treat the message as base64-encoded binary data
+- `-s`, `--signature <SIGNATURE>` — The base64-encoded signature to verify
+- `-p`, `--public-key <PUBLIC_KEY>` — The public key to verify the signature against. Can be an identity (--public-key alice), a public key (--public-key GDKW...)
+- `--hd-path <HD_PATH>` — If public key identity is a seed phrase use this hd path, default is 0
+
+## `stellar fee-stats`
+
+⚠️ Deprecated, use `fees stats` instead. Fetch network feestats
+
+**Usage:** `stellar fee-stats [OPTIONS]`
+
+###### **Options:**
+
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `text`
+
+  Possible values:
+  - `text`: Text output of network info
+  - `json`: JSON result of the RPC request
+  - `json-formatted`: Formatted (multiline) JSON output of the RPC request
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar fees`
+
+Fetch network feestats and configure CLI fee settings
+
+**Usage:** `stellar fees <COMMAND>`
+
+###### **Subcommands:**
+
+- `stats` — Fetch the feestats from the network
+- `use` — Set the default inclusion fee settings for the CLI
+- `unset` — Remove the default inclusion fee settings for the CLI
+
+## `stellar fees stats`
+
+Fetch the feestats from the network
+
+**Usage:** `stellar fees stats [OPTIONS]`
+
+###### **Options:**
+
+- `--output <OUTPUT>` — Format of the output
+
+  Default value: `text`
+
+  Possible values:
+  - `text`: Text output of network info
+  - `json`: JSON result of the RPC request
+  - `json-formatted`: Formatted (multiline) JSON output of the RPC request
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar fees use`
+
+Set the default inclusion fee settings for the CLI
+
+**Usage:** `stellar fees use [OPTIONS] <--amount <AMOUNT>|--fee-metric <FEE_METRIC>>`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
+
+###### **Options:**
+
+- `--amount <AMOUNT>` — Set the default inclusion fee amount, in stroops. 1 stroop = 0.0000001 xlm
+- `--fee-metric <FEE_METRIC>` — Set the default inclusion fee based on a metric from the network's fee stats
+
+  Possible values: `max`, `min`, `mode`, `p10`, `p20`, `p30`, `p40`, `p50`, `p60`, `p70`, `p80`, `p90`, `p95`, `p99`
+
+###### **RPC Options:**
+
+- `--rpc-url <RPC_URL>` — RPC server endpoint
+- `--rpc-header <RPC_HEADERS>` — RPC Header(s) to include in requests to the RPC provider, example: "X-API-Key: abc123". Multiple headers can be added by passing the option multiple times
+- `--network-passphrase <NETWORK_PASSPHRASE>` — Network passphrase to sign the transaction sent to the rpc server
+- `-n`, `--network <NETWORK>` — Name of network to use from config
+
+## `stellar fees unset`
+
+Remove the default inclusion fee settings for the CLI
+
+**Usage:** `stellar fees unset [OPTIONS]`
+
+###### **Global Options:**
+
+- `--config-dir <CONFIG_DIR>` — Location of config directory. By default, it uses `$XDG_CONFIG_HOME/stellar` if set, falling back to `~/.config/stellar` otherwise. Contains configuration files, aliases, and other persistent settings
diff --git a/docs/tools/developer-tools/IDEs.mdx b/docs/tools/developer-tools/IDEs.mdx
index e76208f55..23f8b2278 100644
--- a/docs/tools/developer-tools/IDEs.mdx
+++ b/docs/tools/developer-tools/IDEs.mdx
@@ -1,7 +1,5 @@
 ---
 title: IDEs
 description: Explore IDEs for Stellar.
-sidebar_label: IDEs
-sidebar_position: 70
 draft: true
 ---
diff --git a/docs/tools/developer-tools/README.mdx b/docs/tools/developer-tools/README.mdx
deleted file mode 100644
index 2511d9cef..000000000
--- a/docs/tools/developer-tools/README.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: "Developer Tools; Build, Test, Deploy Apps & Set Up Ramps with SDKs & APIs"
-description: "Discover developer tools to build, test, deploy apps, and set up ramps. Explore SDKs, APIs, and more to streamline development on the Stellar network."
-sidebar_label: More Developer Tools
-sidebar_position: 50
----
-
-import DocCardList from "@theme/DocCardList";
-
-# More Developer Tools
-
-Check out even more helpful tools created by SDF and the community in this section.
-
-<DocCardList />
diff --git a/docs/tools/developer-tools/_category_.json b/docs/tools/developer-tools/_category_.json
deleted file mode 100644
index 9e3a55f45..000000000
--- a/docs/tools/developer-tools/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": true
-}
diff --git a/docs/tools/developer-tools/analytics-platforms.mdx b/docs/tools/developer-tools/analytics-platforms.mdx
index 535dc0301..da83b7086 100644
--- a/docs/tools/developer-tools/analytics-platforms.mdx
+++ b/docs/tools/developer-tools/analytics-platforms.mdx
@@ -1,12 +1,8 @@
 ---
 title: Analytics Platforms
 description: Explore the full history of Stellar network data.
-sidebar_label: Analytics Platforms
-sidebar_position: 18
 ---
 
-# Analytics Platforms
-
 There's a wide range of analytics platforms that make exploring Stellar network data easy and fun! The following platforms allow you to easily create aggregates, visualizations, and dashboards to figure out exactly the story you want to tell, with Stellar data..
 
 ### [Artemis](https://app.artemisanalytics.com/project/stellar?from=projects)
diff --git a/docs/tools/developer-tools/anchor-tools.mdx b/docs/tools/developer-tools/anchor-tools.mdx
index c6d9fba51..fb6c8e087 100644
--- a/docs/tools/developer-tools/anchor-tools.mdx
+++ b/docs/tools/developer-tools/anchor-tools.mdx
@@ -1,12 +1,8 @@
 ---
 title: Anchor Tools
 description: Explore a suite of developer tools for Stellar, including anchor directory, demo wallet, and Polaris.
-sidebar_label: Anchor Tools
-sidebar_position: 20
 ---
 
-# Anchor Tools
-
 ### [Anchor Directory](https://anchors.stellar.org/?)
 
 View all anchors on Stellar, their currencies, and where they operate.
diff --git a/docs/tools/developer-tools/asset-tools.mdx b/docs/tools/developer-tools/asset-tools.mdx
index 9cd08d928..d8da80db5 100644
--- a/docs/tools/developer-tools/asset-tools.mdx
+++ b/docs/tools/developer-tools/asset-tools.mdx
@@ -1,12 +1,8 @@
 ---
 title: Asset Sandbox
 description: Explore a suite of developer tools for Stellar, including asset sandbox.
-sidebar_label: Asset Sandbox
-sidebar_position: 30
 ---
 
-# Asset Sandbox
-
-### [Asset Sandbox](https://stellar.cheesecakelabs.com)
+### [Asset Sandbox](https://stellar.cheesecakelabs.com) {#asset-sandbox-1}
 
 A sandbox supported by SDF and Cheesecake Labs for businesses to experiment with asset issuance on Stellar's test network.
diff --git a/docs/tools/developer-tools/block-explorers.mdx b/docs/tools/developer-tools/block-explorers.mdx
index 596e6deb2..2f04642eb 100644
--- a/docs/tools/developer-tools/block-explorers.mdx
+++ b/docs/tools/developer-tools/block-explorers.mdx
@@ -1,12 +1,8 @@
 ---
 title: Block Explorers
 description: Explore a suite of developer tools for Stellar, including block explorers.
-sidebar_label: Block Explorers
-sidebar_position: 40
 ---
 
-# Block Explorers
-
 Block explorers exist to publicly display blockchain data in an easily digestible way. They can be browsed with an ordinary web browser, and do not require any special developer skills to use. The block explorers available for Soroban index data related to payments, accounts, deployed contracts, transaction history, and more.
 
 ### [StellarExpert](https://stellar.expert/explorer/public)
@@ -25,7 +21,7 @@ Check data related to payments, accounts, deployed contracts, and more for Stell
 
 Explore transactions, accounts, assets, contracts, and ledgers, with a built-in AI assistant that answers questions about on-chain data. Available for Mainnet, Testnet, and Futurenet.
 
-:::note
+<Note>
 
 Soroscan is a newer explorer under active development. A few things the Soroscan team is still working on:
 
@@ -33,7 +29,7 @@ Soroscan is a newer explorer under active development. A few things the Soroscan
 - Deeper detail across account, contract, and asset views
 - Expanding the built-in AI assistant
 
-:::
+</Note>
 
 ### [Soroban Scan](https://sorobanscan.rumblefish.dev)
 
diff --git a/docs/tools/developer-tools/index.mdx b/docs/tools/developer-tools/index.mdx
new file mode 100644
index 000000000..7719cb38b
--- /dev/null
+++ b/docs/tools/developer-tools/index.mdx
@@ -0,0 +1,65 @@
+---
+title: More Developer Tools
+"og:title": "Developer Tools; Build, Test, Deploy Apps & Set Up Ramps with SDKs & APIs"
+description: "Discover developer tools to build, test, deploy apps, and set up ramps. Explore SDKs, APIs, and more to streamline development on the Stellar network."
+---
+
+Check out even more helpful tools created by SDF and the community in this section.
+
+<CardGroup cols={2}>
+  <Card title="Analytics Platforms" icon="file-lines" href="/docs/tools/developer-tools/analytics-platforms">
+
+    Explore the full history of Stellar network data.
+
+  </Card>
+  <Card title="Anchor Tools" icon="file-lines" href="/docs/tools/developer-tools/anchor-tools">
+
+    Explore a suite of developer tools for Stellar, including anchor directory, demo wallet, and Polaris.
+
+  </Card>
+  <Card title="Asset Sandbox" icon="file-lines" href="/docs/tools/developer-tools/asset-tools">
+
+    Explore a suite of developer tools for Stellar, including asset sandbox.
+
+  </Card>
+  <Card title="Block Explorers" icon="file-lines" href="/docs/tools/developer-tools/block-explorers">
+
+    Explore a suite of developer tools for Stellar, including block explorers.
+
+  </Card>
+  <Card title="Jupyter Notebooks" icon="file-lines" href="/docs/tools/developer-tools/jupyter-notebooks">
+
+    Experiment with contracts in Jupyter Notebooks
+
+  </Card>
+  <Card title="Online IDE" icon="file-lines" href="/docs/tools/developer-tools/online-ide">
+
+    An online IDE for Stellar smart contract development.
+
+  </Card>
+  <Card title="Network Insights" icon="file-lines" href="/docs/tools/developer-tools/network-insights">
+
+    Tools to find unique insights about the Stellar network
+
+  </Card>
+  <Card title="Network Status" icon="file-lines" href="/docs/tools/developer-tools/network-status">
+
+    Explore a suite of developer tools for monitoring Stellar network status.
+
+  </Card>
+  <Card title="Node Operator Tools" icon="file-lines" href="/docs/tools/developer-tools/node-operator-tools">
+
+    Explore a suite of developer tools for Stellar, including node operator tools.
+
+  </Card>
+  <Card title="Security Tools" icon="file-lines" href="/docs/tools/developer-tools/security-tools">
+
+    Explore a suite of security tools for Stellar developers.
+
+  </Card>
+  <Card title="Wallet Integration" icon="file-lines" href="/docs/tools/developer-tools/wallets">
+
+    Explore a suite of developer tools for Stellar wallets.
+
+  </Card>
+</CardGroup>
diff --git a/docs/tools/developer-tools/jupyter-notebooks.mdx b/docs/tools/developer-tools/jupyter-notebooks.mdx
index 995e39921..178a26ca0 100644
--- a/docs/tools/developer-tools/jupyter-notebooks.mdx
+++ b/docs/tools/developer-tools/jupyter-notebooks.mdx
@@ -1,21 +1,17 @@
 ---
 title: Jupyter Notebooks
 description: Experiment with contracts in Jupyter Notebooks
-sidebar_label: Jupyter Notebooks
-sidebar_position: 71
 ---
 
-# Jupyter Notebooks
-
 Jupyter Notebooks are a document format that can include code, text, and other rich output. And with the appropriate setup they support Soroban Rust contracts.
 
 To use Soroban contracts in a Jupyter Notebook, the following setup is required. The following setup uses Visual Studio Code, but any Jupyter client and server can be used.
 
-:::caution
+<Warning>
 
 Rust support in Jupyter Notebooks is experimental. You might run into bugs, or unexpected behavior.
 
-:::
+</Warning>
 
 ## Getting Started
 
diff --git a/docs/tools/developer-tools/network-insights.mdx b/docs/tools/developer-tools/network-insights.mdx
index e0ab69c28..8e6207584 100644
--- a/docs/tools/developer-tools/network-insights.mdx
+++ b/docs/tools/developer-tools/network-insights.mdx
@@ -1,12 +1,8 @@
 ---
 title: Network Insights
 description: Tools to find unique insights about the Stellar network
-sidebar_label: Network Insights
-sidebar_position: 85
 ---
 
-# Network Insights
-
 ### [StellarFee](https://stellarfee.expert)
 
 A GUI tool which is a useful fee estimator, transaction simulator to find the resources consumed and the expected fees for a transaction.
diff --git a/docs/tools/developer-tools/network-status.mdx b/docs/tools/developer-tools/network-status.mdx
index b1f648f72..74dea2096 100644
--- a/docs/tools/developer-tools/network-status.mdx
+++ b/docs/tools/developer-tools/network-status.mdx
@@ -1,12 +1,8 @@
 ---
 title: Network Status
 description: Explore a suite of developer tools for monitoring Stellar network status.
-sidebar_label: Network Status
-sidebar_position: 90
 ---
 
-# Network Status
-
 ### [Dashboard](https://dashboard.stellar.org)
 
 Displays the current status of the Testnet and Mainnet. Monitor fee stats, recent operations, lumen supply, and more.
diff --git a/docs/tools/developer-tools/node-operator-tools.mdx b/docs/tools/developer-tools/node-operator-tools.mdx
index 0b7726d2d..1315439c9 100644
--- a/docs/tools/developer-tools/node-operator-tools.mdx
+++ b/docs/tools/developer-tools/node-operator-tools.mdx
@@ -1,15 +1,11 @@
 ---
 title: Node Operator Tools
 description: Explore a suite of developer tools for Stellar, including node operator tools.
-sidebar_label: Node Operator Tools
-sidebar_position: 100
 ---
 
-# Node Operator Tools
-
 ### [Stellar Archivist](https://github.com/stellar/rs-stellar-archivist)
 
-A command line tool for scanning, repairing, and mirroring Stellar Core history archives. See [Publishing History Archives](../../validators/admin-guide/publishing-history-archives.mdx#complete-history-archive) for usage.
+A command line tool for scanning, repairing, and mirroring Stellar Core history archives. See [Publishing History Archives](../../validators/admin-guide/publishing-history-archives#complete-history-archive) for usage.
 
 ### [Go SDK Tools](https://github.com/stellar/go-stellar-sdk/tree/master/tools)
 
diff --git a/docs/tools/developer-tools/online-ide.mdx b/docs/tools/developer-tools/online-ide.mdx
index 55d819a49..0ae580e8c 100644
--- a/docs/tools/developer-tools/online-ide.mdx
+++ b/docs/tools/developer-tools/online-ide.mdx
@@ -1,12 +1,8 @@
 ---
 title: Online IDE
 description: An online IDE for Stellar smart contract development.
-sidebar_label: Online IDE
-sidebar_position: 72
 ---
 
-# Online IDE
-
 ### [Soropg](https://soropg.com)
 
 Soropg is an online IDE specifically designed for Stellar smart contract development. It provides a browser-based environment where developers can write, compile, and test Stellar smart contracts without needing to set up a local development environment.
diff --git a/docs/tools/developer-tools/security-tools.mdx b/docs/tools/developer-tools/security-tools.mdx
index 13ae7c311..285097528 100644
--- a/docs/tools/developer-tools/security-tools.mdx
+++ b/docs/tools/developer-tools/security-tools.mdx
@@ -1,12 +1,8 @@
 ---
 title: Security Tools
 description: Explore a suite of security tools for Stellar developers.
-sidebar_label: Security Tools
-sidebar_position: 115
 ---
 
-# Security Tools
-
 ### [Scout: Bug Fighter](https://www.coinfabrik.com/products/scout)
 
 A static code analysis tool built to assist Soroban developers and auditors in identifying potential security threats and applying best practices.
diff --git a/docs/tools/developer-tools/wallets.mdx b/docs/tools/developer-tools/wallets.mdx
index ec711c895..54781a4af 100644
--- a/docs/tools/developer-tools/wallets.mdx
+++ b/docs/tools/developer-tools/wallets.mdx
@@ -1,12 +1,8 @@
 ---
 title: Wallet Integration
 description: Explore a suite of developer tools for Stellar wallets.
-sidebar_label: Wallet Integration
-sidebar_position: 130
 ---
 
-# Wallet Integration
-
 ### [Stellar Wallet Kit](https://github.com/Creit-Tech/Stellar-Wallets-Kit)
 
 A simple-to-use wallet kit to manage integration to multiple Stellar ecosystem wallet. Learn more about how to integrate this library from [the Stellar Wallets Kit Docs](https://stellarwalletskit.dev).
diff --git a/docs/tools/index.mdx b/docs/tools/index.mdx
new file mode 100644
index 000000000..1f46aba91
--- /dev/null
+++ b/docs/tools/index.mdx
@@ -0,0 +1,51 @@
+---
+title: Tools Overview
+"og:title": "Blockchain Development Tools: SDKs, APIs & Utilities for Building"
+description: "Explore tools for building, testing, and deploying blockchain applications. Access SDKs, APIs, and utilities to streamline development on the Stellar network."
+---
+
+This section of the docs will provide links to the SDKs and developer tools for use when developing on Stellar as well as documentation for various SDF-maintained platforms such as the Anchor Platform and Stellar Disbursement Platform (SDP).
+
+## Developer Tools
+
+### [SDKs](/docs/tools/sdks)
+
+Stellar’s Software Development Kits (SDKs) provide devs with the tools, libraries, and documentation to interact with and develop on the blockchain. They simplify tasks such as creating and deploying smart contracts and sending transactions while also offering APIs to access data and integrate functionalities into applications.
+
+### [Stellar CLI](/docs/tools/cli)
+
+The command line interface to Soroban smart contracts. It allows you to build, deploy, and interact with smart contracts; configure identities; generate key pairs; manage networks; and more.
+
+### [Lab](/docs/tools/lab)
+
+Stellar Lab is our new go-to tool for development, experimenting, and testing, as well as exploring APIs developers use to interact with the Stellar network.
+
+### [Quickstart](/docs/tools/quickstart)
+
+Quickstart is a local Stellar network environment (node) that allows developers to run a local version of the Stellar network for development and testing.
+
+### [OpenZeppelin Relayer](/docs/tools/openzeppelin-relayer)
+
+OpenZeppelin Relayer is an open source framework for submitting Stellar transactions. Its Channels plugin adds parallel submission and automatic fee bumping. You can run both yourself, or you can use [Stellar Channels](https://docs.openzeppelin.com/relayer/guides/stellar-channels-guide), the managed service OpenZeppelin operates on top of them, where OpenZeppelin runs the pool of channel accounts and covers the fees under a fair use policy.
+
+### [OpenZeppelin Contracts](/docs/tools/openzeppelin-contracts)
+
+OpenZeppelin Stellar Contracts is a collection of audited contracts and utilities for Stellar. The contracts are developed by OpenZeppelin in collaboration with the Stellar community and the Stellar Development Foundation (SDF), in an effort to bring a library of high-quality and audited contracts that can be used to build applications on the Stellar network.
+
+### [Scaffold Stellar](/docs/tools/scaffold-stellar)
+
+Scaffold Stellar is a developer toolkit for building decentralized applications (dApps) and smart contracts on Stellar. It provides CLI tools, reusable contract templates, a smart contract registry, and a modern frontend.
+
+### [More Developer Tools](/docs/tools/developer-tools)
+
+Find other SDF and ecosystem-maintained developer tools that help streamline the development process for applications and smart contracts on Stellar.
+
+## SDF Platforms
+
+### [Anchor Platform](/docs/platforms/anchor-platform)
+
+The Anchor Platform is a set of tools and APIs that enable developers and businesses to build their own on and off-ramp services for the Stellar network. It provides a standardized interface, including the implementation of several Stellar Ecosystem Proposals (SEPs), to make it easy for businesses to integrate with Stellar-based wallets and exchanges.
+
+### [Stellar Disbursement Platform (SDP)](/docs/platforms/stellar-disbursement-platform)
+
+The Stellar Disbursement Platform (SDP) is a tool built for organizations to make bulk payments to a group of recipients over the Stellar network.
diff --git a/docs/tools/infra-tools/README.mdx b/docs/tools/infra-tools/README.mdx
deleted file mode 100644
index b074bb9a7..000000000
--- a/docs/tools/infra-tools/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Infrastructure Tools
-sidebar_position: 70
----
-
-import DocCardList from "@theme/DocCardList";
-
-A list of network and infrastructure tools for Stellar.
-
-<DocCardList />
diff --git a/docs/tools/infra-tools/cross-chain.mdx b/docs/tools/infra-tools/cross-chain.mdx
index 92b4e6faa..ce0e7d6ce 100644
--- a/docs/tools/infra-tools/cross-chain.mdx
+++ b/docs/tools/infra-tools/cross-chain.mdx
@@ -1,7 +1,6 @@
 ---
 title: Cross-Chain
-sidebar_label: Cross-Chain
-sidebar_position: 10
+description: "Bridges and messaging layers that connect different blockchains."
 ---
 
 Bridges and messaging layers that connect different blockchains.
diff --git a/docs/tools/infra-tools/index.mdx b/docs/tools/infra-tools/index.mdx
new file mode 100644
index 000000000..85bbc33d0
--- /dev/null
+++ b/docs/tools/infra-tools/index.mdx
@@ -0,0 +1,12 @@
+---
+title: Infrastructure Tools
+description: "A list of network and infrastructure tools for Stellar."
+---
+
+<CardGroup cols={2}>
+  <Card title="Cross-Chain" icon="file-lines" href="/docs/tools/infra-tools/cross-chain">
+
+    Bridges and messaging layers that connect different blockchains.
+
+  </Card>
+</CardGroup>
diff --git a/docs/tools/lab/README.mdx b/docs/tools/lab/README.mdx
deleted file mode 100644
index fd78e884f..000000000
--- a/docs/tools/lab/README.mdx
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Lab
-description: Explore Lab, a developer tool to learn about the Stellar network
-sidebar_label: Lab
-sidebar_position: 30
----
-
-# Lab
-
-### [Stellar Lab](https://lab.stellar.org)
-
-Stellar Lab is our go-to tool for development, experimenting, and testing, as well as [exploring APIs](https://lab.stellar.org/endpoints) developers use to interact with the Stellar network. Whether you're a developer seeking to [test transactions](https://lab.stellar.org/transaction/build), [deploy](https://lab.stellar.org/smart-contracts/deploy-contract) and [invoke smart contracts](https://lab.stellar.org/smart-contracts/contract-explorer), or explore RPC methods or Horizon endpoints, Stellar Lab provides a modern and user-friendly interface that makes the process smooth and intuitive.
-
-![Lab: Homepage](/assets/lab/lab-01232026.png)
-
-### Features of Stellar Lab
-
-- **[Easily Create Accounts](https://lab.stellar.org/account/create)**: Create Accounts on Mainnet, Testnet, and Futurenet using a web UI. You can use [Friendbot](https://lab.stellar.org/account/fund?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;;) to fund those accounts directly on Lab for Testnet and Futurenet. You can also add a trustline to USDC and EURC on Testnet.
-
-- **[Smart Contract Deployment](https://lab.stellar.org/smart-contracts/deploy-contract)**: Deploy smart contracts directly from the Lab interface without needing command-line tools. Upload your contract WASM files and deploy them to the network with a user-friendly workflow.
-
-- **[Invoke Smart Contracts](https://lab.stellar.org/smart-contracts/contract-explorer)**: Interact with deployed smart contracts through an intuitive interface. Select contract functions, fill in parameters with type hints, simulate transactions, and invoke contract methods — all from your browser.
-
-- **[Transaction Dashboard](https://lab.stellar.org/transaction-dashboard)**: View comprehensive transaction details including XDR, operations, results, and metadata. Explore transaction history, examine individual operations, and debug transaction failures with detailed error information.
-
-- **[Access RPC Methods and Horizon Endpoints](https://lab.stellar.org/endpoints)**: Leverage powerful Stellar RPC methods and Stellar Horizon endpoints in a web UI to interact with the Stellar network and obtain crucial data. Try RPC methods to get states from the ledger like accounts, trustlines, contract WASM, and more.
-
-- **[Simulate](https://lab.stellar.org/transaction/simulate) and [Submit](https://lab.stellar.org/transaction/submit)**: Lab supports the ability to use custom RPC providers so that you can simulate transactions, save transactions, and submit transactions directly using Lab. You can also submit transactions using Horizon.
-
-- **[Save and Share API Requests](https://lab.stellar.org/endpoints/saved)**: Easily save your requests and transactions for the future or share them with teammates to build faster together.
-
-- **[XDR ⇔ JSON Support](https://lab.stellar.org/xdr/view)**: We have introduced a canonical [XDR to JSON mapping](https://www.npmjs.com/package/@stellar/stellar-xdr-json-web) which is used on Stellar Lab (also used in the [Stellar CLI](https://github.com/stellar/stellar-cli)). You can see this at work in the Lab where [XDR can be converted to JSON](https://lab.stellar.org/xdr/view).
-
-- **Mobile Friendly**: We heard that you use Lab on mobile, so we optimized the Lab to have a mobile responsive layout.
-
-### Video Tutorial for Stellar Lab
-
-- Video Tutorials for Lab are available on [Lumen Loop's YouTube Channel](https://www.youtube.com/watch?v=sv2gV13q7FI&list=PLj3KReXFn3x73pPlgSun-2FYTrP4tZVPL)
-
-### Help Us Improve!
-
-We’re committed to making Stellar Lab even better. If you have any feature requests, please submit them on [Github](https://github.com/stellar/laboratory/issues). Your feedback is important to us with product iterations and in shaping the future of Stellar Lab.
diff --git a/docs/tools/lab/_category_.json b/docs/tools/lab/_category_.json
deleted file mode 100644
index 0d4475828..000000000
--- a/docs/tools/lab/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": false
-}
diff --git a/docs/tools/lab/account.mdx b/docs/tools/lab/account.mdx
index 60cfb7874..2bd095740 100644
--- a/docs/tools/lab/account.mdx
+++ b/docs/tools/lab/account.mdx
@@ -1,33 +1,30 @@
 ---
 title: Account
 description: Explore Stellar Lab's Account Page by creating and funding account on Stellar
-sidebar_position: 15
 ---
 
-# Account
-
 ## [Create Account Keypair](https://lab.stellar.org/account/create)
 
 ![Lab: Create Account](/assets/lab/lab-keypair-01232026.png)
 
-From the Lab’s main navigation, click on the "Account" link to expand sub-navigation. Click the "Create Account Keypair" page. Here you can generate a [keypair](../../learn/glossary.mdx#keypair) by following these steps:
+From the Lab’s main navigation, click on the "Account" link to expand sub-navigation. Click the "Create Account Keypair" page. Here you can generate a [keypair](../../learn/glossary#keypair) by following these steps:
 
 1. Make sure you are on the Stellar network for which you want to generate the keypair. You can see the current network in the upper right corner of the page. Click on dropdown to change the network (don’t forget to provide any necessary information). We will use Testnet network for this example.
 2. Click the "Generate keypair" button to create public and secret keys for an account. Save them someplace safe, even if they are used only for testing.
 
-:::warning
+<Warning>
 
 Anyone with the account’s secret key has full access and control over the account. Keep the secret key safe.
 
-:::
+</Warning>
 
 3. An account is active only once it is funded. You can use Friendbot to fund it on Testnet and Futurenet networks only. Click on the "Fund account with Friendbot" button to add 10,000 XLM to the account. When the operation completes, a message will be displayed at the bottom.
 
-:::info
+<Info>
 
 The Friendbot can be used for new account or accounts with balance under a starting balance of 10,000 XLM. Click the "Fund account with Friendbot" button again to see what happens. It’s the Lab, so feel free to experiment (as long as you are on Testnet or Futurenet network)!
 
-:::
+</Info>
 
 4. Optionally, to save the generated keypair, click the "Save Keypair" button. Enter the name in the pop-up and click the "Save" button to save the keypair in the browser's local storage. Click the "Saved" link on the main menu to expand the submenu, then click on the "[Keypairs](./saved/keypairs)" link to view saved keypairs. The save feature is available only on Testnet and Futurenet networks.
 
@@ -43,8 +40,8 @@ If you already have a keypair you want to fund, go to the "Fund Account" page (u
 4. You will see a response message once the operation is completed.
 5. Once an account is funded with 10,000 XLM, you can create a trustline with USDC or EURC to interact with these assets.
 
-:::info
+<Info>
 
-You can also create an account using a Stellar SDK. Follow a guide [here](../../build/guides/transactions/create-account.mdx).
+You can also create an account using a Stellar SDK. Follow a guide [here](../../build/guides/transactions/create-account).
 
-:::
+</Info>
diff --git a/docs/tools/lab/api-explorer/README.mdx b/docs/tools/lab/api-explorer/README.mdx
deleted file mode 100644
index 4c910db12..000000000
--- a/docs/tools/lab/api-explorer/README.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: API Explorer
-sidebar_position: 40
----
-
-import DocCardList from "@theme/DocCardList";
-
-# Developer Tools
-
-This section demonstrates how to use RPC methods and Horizon endpoints on the Stellar Lab across different networks, including features like sharing URLs and saving requests for future use.
-
-You can explore the various endpoints from the RPC and Horizon, make requests to these endpoints, and save them for future use.
-
-<DocCardList />
diff --git a/docs/tools/lab/api-explorer/horizon-endpoint.mdx b/docs/tools/lab/api-explorer/horizon-endpoint.mdx
index fa97f0f54..e1ef49b79 100644
--- a/docs/tools/lab/api-explorer/horizon-endpoint.mdx
+++ b/docs/tools/lab/api-explorer/horizon-endpoint.mdx
@@ -1,10 +1,13 @@
-# Horizon Endpoints
+---
+title: Horizon Endpoints
+description: "Horizon is nearing end-of-life and will eventually be deprecated in favor of Stellar RPC and Portfolio APIs. While it will continue to receive updates to maintain compatibility with upcoming protocol releases, it won't receive new feature development. Consider switching to Stellar RPC or another data product."
+---
 
-:::warning
+<Warning>
 
-Horizon is nearing end-of-life and will eventually be deprecated in favor of Stellar RPC and [Portfolio APIs](../../../data/indexers/README.mdx#portfolio-apis). While it will continue to receive updates to maintain compatibility with upcoming protocol releases, it won't receive new feature development. Consider switching to [Stellar RPC or another data product](../../../data/apis/README.mdx).
+Horizon is nearing end-of-life and will eventually be deprecated in favor of Stellar RPC and [Portfolio APIs](/docs/data/indexers#portfolio-apis). While it will continue to receive updates to maintain compatibility with upcoming protocol releases, it won't receive new feature development. Consider switching to [Stellar RPC or another data product](/docs/data/apis).
 
-:::
+</Warning>
 
 Horizon provides an HTTP API to access data stored on the Stellar network. This API acts as a bridge between applications and Stellar Core. Stellar Lab's [API Explorer](https://lab.stellar.org/endpoints) offers a Horizon Endpoints UI, enabling developers to interact with Horizon on Futurenet, Testnet, Mainnet, and custom networks. Developers can use Stellar Lab to build and submit transactions, query account balances, and stream events such as transactions for an account.
 
@@ -14,11 +17,11 @@ Stellar Lab's Horizon Endpoints lists each resource type in the menu, allowing d
 
 ![Lab: Horizon Page](/assets/lab/horizon-endpoints.png)
 
-:::info
+<Info>
 
 For detailed information about each endpoint on a page, click the **View Docs** link in the header to access its API Reference documentation.
 
-:::
+</Info>
 
 ![Lab: Horizon - View Docs](/assets/lab/lab-horizon-view-docs.png)
 
@@ -145,7 +148,7 @@ The Payments for Account endpoint `/accounts/:account-id/payments` provides succ
 
 ![Lab: Horizon - Payments](/assets/lab/horizon-payments.png)
 
-When I click the **Submit** button, the endpoint returns the records of payments (see the [api reference](../../../data/apis/horizon/api-reference/get-payments-by-account-id.api.mdx) for more information on the response format) including the [payment object](../../../data/apis/horizon/api-reference/resources/payments/object.mdx) that were submitted successfully in the account in `JSON` format.
+When I click the **Submit** button, the endpoint returns the records of payments (see the [api reference](/docs/data/apis/horizon/api-reference/get-payments-by-account-id) for more information on the response format) including the [payment object](../../../data/apis/horizon/api-reference/resources/payments/object) that were submitted successfully in the account in `JSON` format.
 
 ![Lab: Horizon - Payments Response](/assets/lab/horizon-payments-response.png)
 
@@ -275,7 +278,7 @@ When I click the **Submit** button, the `/assets` endpoint returns the `USDC` as
 
 ![Lab: Horizon - Assets Page](/assets/lab/horizon-assets-usdc-response.png)
 
-The JSON response for the `USDC` asset includes [the asset object](../../../data/apis/horizon/api-reference/resources/assets/object.mdx), which contains details about USDC, such as the asset's TOML file (also known as [the Stellar info file](../../../tokens/publishing-asset-info.mdx)), the number of claimable balances, liquidity pools, contracts, accounts, balances, and flags.
+The JSON response for the `USDC` asset includes [the asset object](../../../data/apis/horizon/api-reference/resources/assets/object), which contains details about USDC, such as the asset's TOML file (also known as [the Stellar info file](../../../tokens/publishing-asset-info)), the number of claimable balances, liquidity pools, contracts, accounts, balances, and flags.
 
 It shows that `auth_revocable` is set to `true` under `flags`, indicating that this account (in this case, the `USDC` issuer) can freeze the balance of a holder of an asset it has issued.
 
@@ -353,4 +356,4 @@ Clicking the icon opens a modal. We recommend providing an identifiable name to
 
 ![Lab: Horizon - Modal](/assets/lab/horizon-save-modal.png)
 
-Saved endpoints are located in the main menu under the "Saved" menu, "[Requests](../saved/requests.mdx)" submenu.
+Saved endpoints are located in the main menu under the "Saved" menu, "[Requests](../saved/requests)" submenu.
diff --git a/docs/tools/lab/api-explorer/index.mdx b/docs/tools/lab/api-explorer/index.mdx
new file mode 100644
index 000000000..425effaf0
--- /dev/null
+++ b/docs/tools/lab/api-explorer/index.mdx
@@ -0,0 +1,21 @@
+---
+title: Developer Tools
+sidebarTitle: API Explorer
+"og:title": API Explorer
+description: "This section demonstrates how to use RPC methods and Horizon endpoints on the Stellar Lab across different networks, including features like sharing URLs and saving requests for future use."
+---
+
+You can explore the various endpoints from the RPC and Horizon, make requests to these endpoints, and save them for future use.
+
+<CardGroup cols={2}>
+  <Card title="Horizon Endpoints" icon="file-lines" href="/docs/tools/lab/api-explorer/horizon-endpoint">
+
+    Horizon is considered deprecated.
+
+  </Card>
+  <Card title="RPC Methods" icon="file-lines" href="/docs/tools/lab/api-explorer/rpc-methods">
+
+    RPC methods are a set of functions that allow developers to interact directly with the Stellar network.
+
+  </Card>
+</CardGroup>
diff --git a/docs/tools/lab/api-explorer/rpc-methods.mdx b/docs/tools/lab/api-explorer/rpc-methods.mdx
index 5f2eaeeee..2f3b74d6f 100644
--- a/docs/tools/lab/api-explorer/rpc-methods.mdx
+++ b/docs/tools/lab/api-explorer/rpc-methods.mdx
@@ -1,12 +1,15 @@
-# RPC Methods
+---
+title: RPC Methods
+description: "RPC methods are a set of functions that allow developers to interact directly with the Stellar network."
+---
 
 RPC methods are a set of functions that allow developers to interact directly with the Stellar network. You can learn more about all the RPC methods [here](../../../data/apis/rpc/api-reference/methods). The Lab provides an easy way to use these methods from the UI. To access the "RPC Methods" items, click on the "API Explorer" link in the main navigation, then click the "RPC Methods" submenu link, which will open another submenu listing all RPC methods by name. Click on the method name to open that page.
 
-:::warning
+<Warning>
 
 RPC URL is required to submit these methods. You can update or set the RPC URL in the network selector in the top right corner.
 
-:::
+</Warning>
 
 ## Example
 
@@ -30,4 +33,4 @@ The Stellar Lab allows you to share RPC methods with filled data. Simply click o
 
 ## Saved Requests
 
-You can save methods in the browser’s local storage by clicking the Save button (next to the Share button). Once you click that button, a modal will pop up, where you will need to enter the name and click save. To view your saved RPC methods in the Lab, click the "Saved" link in the main menu, then click the "[Requests](../saved/requests.mdx)" submenu link. Then click the "RPC Methods" tab in the top right.
+You can save methods in the browser’s local storage by clicking the Save button (next to the Share button). Once you click that button, a modal will pop up, where you will need to enter the name and click save. To view your saved RPC methods in the Lab, click the "Saved" link in the main menu, then click the "[Requests](../saved/requests)" submenu link. Then click the "RPC Methods" tab in the top right.
diff --git a/docs/tools/lab/index.mdx b/docs/tools/lab/index.mdx
new file mode 100644
index 000000000..5ac24be70
--- /dev/null
+++ b/docs/tools/lab/index.mdx
@@ -0,0 +1,38 @@
+---
+title: Lab
+description: Explore Lab, a developer tool to learn about the Stellar network
+---
+
+### [Stellar Lab](https://lab.stellar.org)
+
+Stellar Lab is our go-to tool for development, experimenting, and testing, as well as [exploring APIs](https://lab.stellar.org/endpoints) developers use to interact with the Stellar network. Whether you're a developer seeking to [test transactions](https://lab.stellar.org/transaction/build), [deploy](https://lab.stellar.org/smart-contracts/deploy-contract) and [invoke smart contracts](https://lab.stellar.org/smart-contracts/contract-explorer), or explore RPC methods or Horizon endpoints, Stellar Lab provides a modern and user-friendly interface that makes the process smooth and intuitive.
+
+![Lab: Homepage](/assets/lab/lab-01232026.png)
+
+### Features of Stellar Lab
+
+- **[Easily Create Accounts](https://lab.stellar.org/account/create)**: Create Accounts on Mainnet, Testnet, and Futurenet using a web UI. You can use [Friendbot](https://lab.stellar.org/account/fund?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;;) to fund those accounts directly on Lab for Testnet and Futurenet. You can also add a trustline to USDC and EURC on Testnet.
+
+- **[Smart Contract Deployment](https://lab.stellar.org/smart-contracts/deploy-contract)**: Deploy smart contracts directly from the Lab interface without needing command-line tools. Upload your contract WASM files and deploy them to the network with a user-friendly workflow.
+
+- **[Invoke Smart Contracts](https://lab.stellar.org/smart-contracts/contract-explorer)**: Interact with deployed smart contracts through an intuitive interface. Select contract functions, fill in parameters with type hints, simulate transactions, and invoke contract methods — all from your browser.
+
+- **[Transaction Dashboard](https://lab.stellar.org/transaction-dashboard)**: View comprehensive transaction details including XDR, operations, results, and metadata. Explore transaction history, examine individual operations, and debug transaction failures with detailed error information.
+
+- **[Access RPC Methods and Horizon Endpoints](https://lab.stellar.org/endpoints)**: Leverage powerful Stellar RPC methods and Stellar Horizon endpoints in a web UI to interact with the Stellar network and obtain crucial data. Try RPC methods to get states from the ledger like accounts, trustlines, contract WASM, and more.
+
+- **[Simulate](https://lab.stellar.org/transaction/simulate) and [Submit](https://lab.stellar.org/transaction/submit)**: Lab supports the ability to use custom RPC providers so that you can simulate transactions, save transactions, and submit transactions directly using Lab. You can also submit transactions using Horizon.
+
+- **[Save and Share API Requests](https://lab.stellar.org/endpoints/saved)**: Easily save your requests and transactions for the future or share them with teammates to build faster together.
+
+- **[XDR ⇔ JSON Support](https://lab.stellar.org/xdr/view)**: We have introduced a canonical [XDR to JSON mapping](https://www.npmjs.com/package/@stellar/stellar-xdr-json-web) which is used on Stellar Lab (also used in the [Stellar CLI](https://github.com/stellar/stellar-cli)). You can see this at work in the Lab where [XDR can be converted to JSON](https://lab.stellar.org/xdr/view).
+
+- **Mobile Friendly**: We heard that you use Lab on mobile, so we optimized the Lab to have a mobile responsive layout.
+
+### Video Tutorial for Stellar Lab
+
+- Video Tutorials for Lab are available on [Lumen Loop's YouTube Channel](https://www.youtube.com/watch?v=sv2gV13q7FI&list=PLj3KReXFn3x73pPlgSun-2FYTrP4tZVPL)
+
+### Help Us Improve!
+
+We’re committed to making Stellar Lab even better. If you have any feature requests, please submit them on [Github](https://github.com/stellar/laboratory/issues). Your feedback is important to us with product iterations and in shaping the future of Stellar Lab.
diff --git a/docs/tools/lab/quickstart-with-lab.mdx b/docs/tools/lab/quickstart-with-lab.mdx
index 5f426ec60..cf3fc63c4 100644
--- a/docs/tools/lab/quickstart-with-lab.mdx
+++ b/docs/tools/lab/quickstart-with-lab.mdx
@@ -1,4 +1,7 @@
-# Using Lab with Quickstart
+---
+title: Using Lab with Quickstart
+description: "Quickstart provides an easy way to set up a local Stellar network environment."
+---
 
 ## Overview
 
@@ -6,7 +9,7 @@
 
 ## Prerequisites
 
-- [Stellar CLI](../cli/install-cli.mdx)
+- [Stellar CLI](../cli/install-cli)
 - [Docker](https://www.docker.com)
 
 ## Start Quickstart
@@ -27,7 +30,7 @@ Quickstart will usually start on `http://localhost:8000`. With this information,
 2. Select `Custom` network in the dropdown.
 3. For the RPC URL, input `http://localhost:8000/rpc`.
 4. For the Horizon URL, input `http://localhost:8000.`.
-5. For the [network passphrase](../../networks/README.mdx), input `Test SDF Network ; September 2015`
+5. For the [network passphrase](/docs/networks), input `Test SDF Network ; September 2015`
 6. Click the button `Switch to Custom Network` and switched to using your Quickstart.
 
 You should be able to use Horizon endpoints, RPC endpoints, Friendbot on Lab, with requests now send to your local environment (Quickstart). Lab gives you a user friendly interface to interact with you local environment.
diff --git a/docs/tools/lab/saved/README.mdx b/docs/tools/lab/saved/README.mdx
deleted file mode 100644
index 8f958c099..000000000
--- a/docs/tools/lab/saved/README.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: Saved
-sidebar_position: 20
----
-
-import DocCardList from "@theme/DocCardList";
-
-# Saved
-
-View keypairs, requests, and transactions saved in local storage.
-
-<DocCardList />
diff --git a/docs/tools/lab/saved/index.mdx b/docs/tools/lab/saved/index.mdx
new file mode 100644
index 000000000..153dde9a0
--- /dev/null
+++ b/docs/tools/lab/saved/index.mdx
@@ -0,0 +1,22 @@
+---
+title: Saved
+description: "View keypairs, requests, and transactions saved in local storage."
+---
+
+<CardGroup cols={2}>
+  <Card title="Keypairs" icon="file-lines" href="/docs/tools/lab/saved/keypairs">
+
+    View saved keypairs (accounts).
+
+  </Card>
+  <Card title="Requests" icon="file-lines" href="/docs/tools/lab/saved/requests">
+
+    View saved Horizon endpoints and RPC methods.
+
+  </Card>
+  <Card title="Transactions" icon="file-lines" href="/docs/tools/lab/saved/transactions">
+
+    View saved transactions.
+
+  </Card>
+</CardGroup>
diff --git a/docs/tools/lab/saved/keypairs.mdx b/docs/tools/lab/saved/keypairs.mdx
index fe3ddb904..17fa28db2 100644
--- a/docs/tools/lab/saved/keypairs.mdx
+++ b/docs/tools/lab/saved/keypairs.mdx
@@ -1,17 +1,15 @@
 ---
 title: "Keypairs"
-sidebar_label: Keypairs
 description: "View saved keypairs (accounts)."
-sidebar_position: 0
 ---
 
-# [Keypairs](https://lab.stellar.org/account/saved)
+Open [Saved Keypairs](https://lab.stellar.org/account/saved) in Stellar Lab.
 
-:::important
+<Warning>
 
 You can only save keypairs on test networks—never on Mainnet—and you should never reuse Mainnet keypairs on test networks or share your secret keys with anyone.
 
-:::
+</Warning>
 
 ## Overview
 
@@ -31,7 +29,7 @@ This page shows your saved keypairs for the selected network (only Testnet and F
 
 ## Manually save keypair
 
-To add a keypair manually, click the "Add keypair manually" button located in the top right corner of the screen. This will open a modal where you can enter a name for your keypair along with the [Stellar secret key](../../../learn/glossary.mdx#secret-private-key) (which begins with the letter "S") or recovery passphrase (a 12 or 24-word phrase).
+To add a keypair manually, click the "Add keypair manually" button located in the top right corner of the screen. This will open a modal where you can enter a name for your keypair along with the [Stellar secret key](../../../learn/glossary#secret-private-key) (which begins with the letter "S") or recovery passphrase (a 12 or 24-word phrase).
 
 ![Lab: Add keypair manually](/assets/lab/lab-account-saved-manual.png)
 
diff --git a/docs/tools/lab/saved/requests.mdx b/docs/tools/lab/saved/requests.mdx
index 2947c4c9e..132165ba2 100644
--- a/docs/tools/lab/saved/requests.mdx
+++ b/docs/tools/lab/saved/requests.mdx
@@ -1,19 +1,17 @@
 ---
 title: "Requests"
-sidebar_label: Requests
 description: "View saved Horizon endpoints and RPC methods."
-sidebar_position: 1
 ---
 
-# [Requests](https://lab.stellar.org/endpoints/saved)
+Open [Saved Requests](https://lab.stellar.org/endpoints/saved) in Stellar Lab.
 
 On this page, you can view saved requests for both the **RPC Methods** and **Horizon Endpoints**. Select the tab you want to view in the top right corner.
 
-:::info
+<Info>
 
 Only items for the selected network are shown. If you don’t see the item you’re looking for, try changing the network.
 
-:::
+</Info>
 
 ## RPC Methods
 
diff --git a/docs/tools/lab/saved/transactions.mdx b/docs/tools/lab/saved/transactions.mdx
index 6957e235a..62bf24ca2 100644
--- a/docs/tools/lab/saved/transactions.mdx
+++ b/docs/tools/lab/saved/transactions.mdx
@@ -1,11 +1,9 @@
 ---
 title: "Transactions"
-sidebar_label: Transactions
 description: "View saved transactions."
-sidebar_position: 2
 ---
 
-# [Transactions](https://lab.stellar.org/transaction/saved)
+Open [Saved Transactions](https://lab.stellar.org/transaction/saved) in Stellar Lab.
 
 ![Lab: Saved Transactions](/assets/lab/lab-transactions-saved.png)
 
diff --git a/docs/tools/lab/smart-contracts/README.mdx b/docs/tools/lab/smart-contracts/README.mdx
deleted file mode 100644
index c7d0a48c2..000000000
--- a/docs/tools/lab/smart-contracts/README.mdx
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: Smart Contracts
-sidebar_position: 50
----
-
-import DocCardList from "@theme/DocCardList";
-
-Stellar Lab provides a comprehensive suite of tools for exploring, testing, and interacting with smart contracts on the Stellar network. These tools are designed to help developers understand contract behavior, debug issues, and test contract interactions without writing additional code.
-
-:::tip
-
-If you don't know any Stellar smart contract ID, view [Smart Contract List](https://lab.stellar.org/smart-contracts/contract-list) and click on any of the items. This will direct you to the "Contract Explorer" page, where the selected ID is pre-filled. Load the contract and check it out!
-
-:::
-
-### Tips for New Developers
-
-- **Start with Testnet**: Always begin your development and testing on Testnet where XLM is free and mistakes have no real-world consequences
-- **Examine Example Contracts**: Study well-known contracts to understand common patterns and best practices
-- **Save Your Configurations**: Type in the Contract ID you want to explore on [Contract Explorer](https://lab.stellar.org/smart-contracts/contract-explorer), it will give you an option to save for quick access via 'Save Contract ID'
-- **Check Network Status**: Ensure you're connected to the correct network
-
-## Additional Resources
-
-- [Smart Contracts Documentation](../../../build/smart-contracts/README.mdx)
-- [Soroban CLI Tools](../../cli/README.mdx)
-- [Example Contracts](../../../build/smart-contracts/example-contracts/README.mdx)
-
-<DocCardList />
diff --git a/docs/tools/lab/smart-contracts/contract-explorer.mdx b/docs/tools/lab/smart-contracts/contract-explorer.mdx
index 6ab32108d..c5b295174 100644
--- a/docs/tools/lab/smart-contracts/contract-explorer.mdx
+++ b/docs/tools/lab/smart-contracts/contract-explorer.mdx
@@ -1,19 +1,15 @@
 ---
 title: "Contract Explorer"
-sidebar_label: Contract Explorer
 description: "Explore and interact with deployed Stellar smart contracts through a browser-based interface. View contract specs, source code, storage, build info, version history, and invoke contract methods directly."
-sidebar_position: 0
 ---
 
-# Contract Explorer
-
 The [Contract Explorer](https://lab.stellar.org/smart-contracts/contract-explorer) is your primary interface for examining deployed smart contracts on the Stellar network. Through an intuitive browser-based interface, you can access comprehensive insights into [contract specifications](#contract-spec), [source code](#source-code), [storage state](#contract-storage), [build information](#build-info), [version history](#version-history), and [client bindings](#bindings) — plus [invoke contract](#invoke-contract) methods directly without any command-line tools.
 
-:::warning
+<Warning>
 
-RPC URL is required to view the contract information. You can update or set the RPC URL in the network selector in the top right corner. See [RPC Providers](../../../data/apis/rpc/providers.mdx).
+RPC URL is required to view the contract information. You can update or set the RPC URL in the network selector in the top right corner. See [RPC Providers](../../../data/apis/rpc/providers).
 
-:::
+</Warning>
 
 ![Lab: Contract Explorer](/assets/lab/lab-contract-explorer.png)
 
@@ -62,21 +58,21 @@ This action redirects you to the [Build Transactions page](https://lab.stellar.o
 
 ![Lab: Contract Explorer: Contract Storage Restore in action](/assets/lab/restore-footprint.gif)
 
-:::tip
+<Tip>
 
 Verify that the prepared Soroban Transaction XDR includes the contract data you want to restore in its `footprint.read_write` resources, and confirm that both read and write bytes are non-zero.
 
-:::
+</Tip>
 
 ## Build Info
 
 If the smart contract has build verification configured (following the [Contract Source Validation SEP](https://github.com/orgs/stellar/discussions/1573)), this section displays information from the GitHub attestation.
 
-:::info
+<Info>
 
 "Build Verified" only means that the GitHub Action run has attested to have built the Wasm, but does not verify the source code. Always make sure you fully understand what the smart contract does before using it.
 
-:::
+</Info>
 
 ![Lab: Contract Explorer: Build Info](/assets/lab/lab-contract-explorer-build.png)
 
@@ -94,11 +90,11 @@ Bindings are a feature of the [Stellar CLI](../../cli) that generate fully typed
 
 The Invoke Contract page lets you interact with smart contracts directly through the web interface—no command-line tools or custom scripts required.
 
-:::warning
+<Warning>
 
 A connected wallet is required to invoke the contract.
 
-:::
+</Warning>
 
 ### How to Use
 
@@ -112,11 +108,11 @@ A connected wallet is required to invoke the contract.
 
 ![Lab: Contract Explorer: Invoke Contract](/assets/lab/lab-contract-explorer-invoke.gif)
 
-:::info
+<Info>
 
 Once you simulate the function, you will see a tooltip that says either `Read` or `Write` next to the title of the function you invoked. When a transaction doesn't change the state of the contract, it is considered a `Read` operation. In this scenario, it is not necessary to submit the transaction to the network, as it does not modify any data. You can simply simulate the transaction to see the results without incurring any costs.
 
-:::
+</Info>
 
 ### Use Cases
 
diff --git a/docs/tools/lab/smart-contracts/index.mdx b/docs/tools/lab/smart-contracts/index.mdx
new file mode 100644
index 000000000..475c14f76
--- /dev/null
+++ b/docs/tools/lab/smart-contracts/index.mdx
@@ -0,0 +1,41 @@
+---
+title: Smart Contracts
+description: "Stellar Lab provides a comprehensive suite of tools for exploring, testing, and interacting with smart contracts on the Stellar network. These tools are designed to help developers understand contract behavior, debug issues, and test contract interactions without writing additional code."
+---
+
+<Tip>
+
+If you don't know any Stellar smart contract ID, view [Smart Contract List](https://lab.stellar.org/smart-contracts/contract-list) and click on any of the items. This will direct you to the "Contract Explorer" page, where the selected ID is pre-filled. Load the contract and check it out!
+
+</Tip>
+
+### Tips for New Developers
+
+- **Start with Testnet**: Always begin your development and testing on Testnet where XLM is free and mistakes have no real-world consequences
+- **Examine Example Contracts**: Study well-known contracts to understand common patterns and best practices
+- **Save Your Configurations**: Type in the Contract ID you want to explore on [Contract Explorer](https://lab.stellar.org/smart-contracts/contract-explorer), it will give you an option to save for quick access via 'Save Contract ID'
+- **Check Network Status**: Ensure you're connected to the correct network
+
+## Additional Resources
+
+- [Smart Contracts Documentation](/docs/build/smart-contracts)
+- [Soroban CLI Tools](/docs/tools/cli)
+- [Example Contracts](/docs/build/smart-contracts/example-contracts)
+
+<CardGroup cols={2}>
+  <Card title="Contract Explorer" icon="file-lines" href="/docs/tools/lab/smart-contracts/contract-explorer">
+
+    Explore and interact with deployed Stellar smart contracts through a browser-based interface. View contract specs, source code, storage, build info, version history, and invoke contract methods directly.
+
+  </Card>
+  <Card title="Smart Contract List" icon="file-lines" href="/docs/tools/lab/smart-contracts/smart-contract-list">
+
+    A list of Stellar smart contracts on the selected network
+
+  </Card>
+  <Card title="Upload and Deploy Contract" icon="file-lines" href="/docs/tools/lab/smart-contracts/upload-deploy-contract">
+
+    Upload your contract's WASM bytecode and deploy the contract to the network.
+
+  </Card>
+</CardGroup>
diff --git a/docs/tools/lab/smart-contracts/smart-contract-list.mdx b/docs/tools/lab/smart-contracts/smart-contract-list.mdx
index 885ff7147..511747d84 100644
--- a/docs/tools/lab/smart-contracts/smart-contract-list.mdx
+++ b/docs/tools/lab/smart-contracts/smart-contract-list.mdx
@@ -1,12 +1,8 @@
 ---
 title: "Smart Contract List"
-sidebar_label: Smart Contract List
 description: "A list of Stellar smart contracts on the selected network"
-sidebar_position: 1
 ---
 
-# Smart Contract List
-
 This page shows a list of recent Stellar smart contracts on the selected network. On Mainnet, there's an option to view popular contracts list. The table displays the smart contract ID or address, along with its creation date and time. Clicking on the contract address will direct you to the "Contract Explorer" page, where the selected address is pre-filled.
 
 ![Lab: Smart Contract List](/assets/lab/smart-contract-list-01232026.png)
diff --git a/docs/tools/lab/smart-contracts/upload-deploy-contract.mdx b/docs/tools/lab/smart-contracts/upload-deploy-contract.mdx
index 6079110b5..1155ae7cb 100644
--- a/docs/tools/lab/smart-contracts/upload-deploy-contract.mdx
+++ b/docs/tools/lab/smart-contracts/upload-deploy-contract.mdx
@@ -1,13 +1,9 @@
 ---
 title: "Upload and Deploy Contract"
-sidebar_label: Upload and Deploy Contract
 description: "Upload your contract's WASM bytecode and deploy the contract to the network."
-sidebar_position: 2
 ---
 
-# Upload and Deploy Contract
-
-There are several ways to upload and deploy contracts to the Stellar network. If you are familiar with the CLI workflow, you can easily upload and deploy contracts using two different commands on the [Stellar CLI](../../cli/README.mdx). If you prefer to do it all in a web interface, the ["Upload and Deploy Contract"](https://lab.stellar.org/smart-contracts/deploy-contract) page on Stellar Lab provides a convenient way to upload and deploy contracts to the network.
+There are several ways to upload and deploy contracts to the Stellar network. If you are familiar with the CLI workflow, you can easily upload and deploy contracts using two different commands on the [Stellar CLI](/docs/tools/cli). If you prefer to do it all in a web interface, the ["Upload and Deploy Contract"](https://lab.stellar.org/smart-contracts/deploy-contract) page on Stellar Lab provides a convenient way to upload and deploy contracts to the network.
 
 ![Lab: Contract Explorer](/assets/lab/lab-upload-deploy-page.png)
 
@@ -16,11 +12,11 @@ The deployment process consists of two distinct phases:
 1. **Upload phase**: Uploading `WASM` bytecode to the network
 2. **Deploy phase**: Deploying a contract instance from the successfully uploaded bytecode
 
-:::tip
+<Tip>
 
 Each upload and deploy phase requires creating a transaction and signing the transaction.
 
-:::
+</Tip>
 
 ## Upload Phase
 
diff --git a/docs/tools/lab/transaction-dashboard.mdx b/docs/tools/lab/transaction-dashboard.mdx
index b13bdf0d6..a8cb65c87 100644
--- a/docs/tools/lab/transaction-dashboard.mdx
+++ b/docs/tools/lab/transaction-dashboard.mdx
@@ -1,11 +1,8 @@
 ---
 title: Transaction Dashboard
 description: Use Stellar Lab's Transaction Dashboard Page to get a comprehensive view of transaction details for both classic and smart contracts
-sidebar_position: 60
 ---
 
-# Transaction Dashboard
-
 ![Lab: Transaction Dashboard](/assets/lab/ab-tx-dashboard-01232026.png)
 
 The [Transaction Dashboard](https://lab.stellar.org/transaction-dashboard) provides a comprehensive view of transaction details. For classic transactions, it offers deep insights into operations. For smart contract transactions, it offers details on its interactions (token summary, contracts, events, state change), resource consumption, signatures, and fee breakdowns.
@@ -16,13 +13,13 @@ Transaction details for both smart contract and classic transactions include the
 
 The dashboard automatically detects whether you're viewing a classic transaction or a smart contract transaction and displays the relevant tabs accordingly.
 
-:::note
+<Note>
 
 This feature uses an RPC and RPC retains at maximum 7 days of historical data. Any transaction older than 7 days will be displayed as invalid.
 
-See [Indexers](../../data/indexers/README.mdx) and [Block Explorers](../developer-tools/block-explorers.mdx#stellarexpert) for reference
+See [Indexers](/docs/data/indexers) and [Block Explorers](../developer-tools/block-explorers#stellarexpert) for reference
 
-:::
+</Note>
 
 ## Dashboard Tabs for Smart Contracts
 
diff --git a/docs/tools/lab/transactions.mdx b/docs/tools/lab/transactions.mdx
index a03737973..886d38a14 100644
--- a/docs/tools/lab/transactions.mdx
+++ b/docs/tools/lab/transactions.mdx
@@ -1,11 +1,8 @@
 ---
 title: Transactions
 description: Explore Stellar Lab's Build Transaction Page by creating and submitting a transaction on Stellar
-sidebar_position: 30
 ---
 
-# Transactions
-
 ## [Build Transaction](https://lab.stellar.org/transaction/build)
 
 ![Lab: Build Transaction](/assets/lab/lab-transactions-build.png)
diff --git a/docs/tools/lab/view-xdr/README.mdx b/docs/tools/lab/view-xdr/README.mdx
deleted file mode 100644
index 4ea9dc018..000000000
--- a/docs/tools/lab/view-xdr/README.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: View XDR
-sidebar_position: 10
----
-
-import DocCardList from "@theme/DocCardList";
-
-# View XDR
-
-This section provides tools to work with [XDR](../../../learn/fundamentals/data-format/xdr.mdx) (External Data Representation) data. You can decode XDR into easy-to-read JSON format, convert JSON back into XDR format, or compare two XDR data sets to view their differences side-by-side. Learn more about XDR-JSON conversion [here](../../../learn/fundamentals/data-format/xdr-json.mdx).
-
-<DocCardList />
diff --git a/docs/tools/lab/view-xdr/diff-xdr.mdx b/docs/tools/lab/view-xdr/diff-xdr.mdx
index a53f6f69d..3dfbf73f4 100644
--- a/docs/tools/lab/view-xdr/diff-xdr.mdx
+++ b/docs/tools/lab/view-xdr/diff-xdr.mdx
@@ -1,17 +1,13 @@
 ---
 title: "Diff XDRs"
-sidebar_label: Diff XDRs
 description: "The Diff XDRs tool compares two base-64 encoded XDRs and highlights the differences between them in JSON format."
-sidebar_position: 2
 ---
 
-# Diff XDRs
+<Info>
 
-:::info
+Learn more about XDR to JSON conversion tools [here](../../../learn/fundamentals/data-format/xdr-json).
 
-Learn more about XDR to JSON conversion tools [here](../../../learn/fundamentals/data-format/xdr-json.mdx).
-
-:::
+</Info>
 
 ## Accessing the Diff XDRs Tool
 
@@ -21,7 +17,7 @@ To access the [Diff XDRs](https://lab.stellar.org/xdr/diff) page, select "View X
 
 ## Comparing XDR Data
 
-On this page, you can compare two base-64 encoded [XDRs](../../../learn/fundamentals/data-format/xdr.mdx) by viewing their JSON difference. Enter the Original XDR in the first input field, followed by the Changed XDR in the second field. Both XDRs must share the same XDR type, which is automatically populated when a valid Original XDR value is entered. If the suggested type appears incorrect, you can select an alternative from the dropdown menu. A search function is available to help locate the appropriate type.
+On this page, you can compare two base-64 encoded [XDRs](../../../learn/fundamentals/data-format/xdr) by viewing their JSON difference. Enter the Original XDR in the first input field, followed by the Changed XDR in the second field. Both XDRs must share the same XDR type, which is automatically populated when a valid Original XDR value is entered. If the suggested type appears incorrect, you can select an alternative from the dropdown menu. A search function is available to help locate the appropriate type.
 
 ![Lab: XDR type dropdown](/assets/lab/lab-xdr-diff-dropdown.png)
 
diff --git a/docs/tools/lab/view-xdr/index.mdx b/docs/tools/lab/view-xdr/index.mdx
new file mode 100644
index 000000000..74f62cfeb
--- /dev/null
+++ b/docs/tools/lab/view-xdr/index.mdx
@@ -0,0 +1,24 @@
+---
+title: View XDR
+description: "This section provides tools to work with XDR (External Data Representation) data. You can decode XDR into easy-to-read JSON format, convert JSON back into XDR format, or compare two XDR data sets to view their differences side-by-side."
+---
+
+Learn more about XDR-JSON conversion [here](/docs/learn/fundamentals/data-format/xdr-json).
+
+<CardGroup cols={2}>
+  <Card title="XDR to JSON" icon="file-lines" href="/docs/tools/lab/view-xdr/xdr-to-json">
+
+    The XDR to JSON converter transforms base-64 encoded XDR data into readable JSON format.
+
+  </Card>
+  <Card title="JSON to XDR" icon="file-lines" href="/docs/tools/lab/view-xdr/json-to-xdr">
+
+    The JSON to XDR converter transforms JSON objects into base-64 encoded XDR format.
+
+  </Card>
+  <Card title="Diff XDRs" icon="file-lines" href="/docs/tools/lab/view-xdr/diff-xdr">
+
+    The Diff XDRs tool compares two base-64 encoded XDRs and highlights the differences between them in JSON format.
+
+  </Card>
+</CardGroup>
diff --git a/docs/tools/lab/view-xdr/json-to-xdr.mdx b/docs/tools/lab/view-xdr/json-to-xdr.mdx
index e273e78dc..99d92d0a4 100644
--- a/docs/tools/lab/view-xdr/json-to-xdr.mdx
+++ b/docs/tools/lab/view-xdr/json-to-xdr.mdx
@@ -1,17 +1,13 @@
 ---
 title: "JSON to XDR"
-sidebar_label: JSON to XDR
 description: "The JSON to XDR converter transforms JSON objects into base-64 encoded XDR format."
-sidebar_position: 1
 ---
 
-# JSON to XDR
+<Info>
 
-:::info
+Learn more about JSON to XDR conversion tools [here](../../../learn/fundamentals/data-format/xdr-json).
 
-Learn more about JSON to XDR conversion tools [here](../../../learn/fundamentals/data-format/xdr-json.mdx).
-
-:::
+</Info>
 
 ## Accessing the JSON to XDR Converter
 
@@ -21,7 +17,7 @@ To access the [JSON to XDR](https://lab.stellar.org/xdr/to) page, select "View X
 
 ## Inputting JSON Data
 
-On this page, you can enter a valid [XDR](../../../learn/fundamentals/data-format/xdr.mdx) JSON object into the input field. To get sample data, navigate to the "[XDR to JSON](./xdr-to-json.mdx)" page, then use the "Copy JSON" button located below the JSON output to copy a formatted object for testing purposes.
+On this page, you can enter a valid [XDR](../../../learn/fundamentals/data-format/xdr) JSON object into the input field. To get sample data, navigate to the "[XDR to JSON](./xdr-to-json)" page, then use the "Copy JSON" button located below the JSON output to copy a formatted object for testing purposes.
 
 ## Understanding the Output
 
diff --git a/docs/tools/lab/view-xdr/xdr-to-json.mdx b/docs/tools/lab/view-xdr/xdr-to-json.mdx
index f33da6537..89e4418ae 100644
--- a/docs/tools/lab/view-xdr/xdr-to-json.mdx
+++ b/docs/tools/lab/view-xdr/xdr-to-json.mdx
@@ -1,17 +1,13 @@
 ---
 title: "XDR to JSON"
-sidebar_label: XDR to JSON
 description: "The XDR to JSON converter transforms base-64 encoded XDR data into readable JSON format."
-sidebar_position: 0
 ---
 
-# XDR to JSON
+<Info>
 
-:::info
+Learn more about XDR to JSON conversion tools [here](../../../learn/fundamentals/data-format/xdr-json).
 
-Learn more about XDR to JSON conversion tools [here](../../../learn/fundamentals/data-format/xdr-json.mdx).
-
-:::
+</Info>
 
 To access the [XDR to JSON](https://lab.stellar.org/xdr/view) page, select "View XDR" from the left-hand navigation menu, then choose the "XDR to JSON" option from the submenu.
 
@@ -19,7 +15,7 @@ To access the [XDR to JSON](https://lab.stellar.org/xdr/view) page, select "View
 
 ## Inputting XDR Data
 
-On this page, you can enter a base-64 encoded [XDR](../../../learn/fundamentals/data-format/xdr.mdx) into the input field located at the top. Alternatively, you can get a sample XDR by selecting the "fetch the latest transaction" link positioned below the input field.
+On this page, you can enter a base-64 encoded [XDR](../../../learn/fundamentals/data-format/xdr) into the input field located at the top. Alternatively, you can get a sample XDR by selecting the "fetch the latest transaction" link positioned below the input field.
 
 ## Understanding the Output
 
diff --git a/docs/tools/openzeppelin-contracts.mdx b/docs/tools/openzeppelin-contracts.mdx
index c119a36ac..fcc7a4007 100644
--- a/docs/tools/openzeppelin-contracts.mdx
+++ b/docs/tools/openzeppelin-contracts.mdx
@@ -1,25 +1,27 @@
 ---
 title: OpenZeppelin Contracts and Toolings
 description: OpenZeppelin Contract Library and Toolings
-sidebar_label: OpenZeppelin Contracts and Toolings
-sidebar_position: 44
 ---
 
-<script async src="https://wizard.openzeppelin.com/build/embed.js"></script>
-
-::::note
+<Note>
 
 OpenZeppelin is bringing its trusted [smart contracts libraries](https://github.com/OpenZeppelin/stellar-contracts) and developer workflows to Stellar, a Rust-based blockchain. Developers can build payments, stablecoins, and DeFi apps on Stellar using familiar, audited building blocks. To see more, go to: https://www.openzeppelin.com/networks/stellar.
 
 For latest OpenZeppelin developer docs, please visit: [https://docs.openzeppelin.com/stellar-contracts](https://docs.openzeppelin.com/stellar-contracts).
 
-::::
+</Note>
 
 ## Getting started with Contract Wizard
 
 [OpenZeppelin's Contract Wizard](https://wizard.openzeppelin.com/stellar) includes support for Stellar’s Rust-based smart contracts, making it easier for developers to generate and deploy secure, audited contracts. After you have selected your desired template and options you can download it as a single file, a Rust development package, or a [Scaffold Stellar Package](./scaffold-stellar). Try it out below or visit the wizard [here](https://wizard.openzeppelin.com/stellar).
 
-<oz-wizard data-lang="stellar"></oz-wizard>
+<iframe
+  src="https://wizard.openzeppelin.com/embed?lang=stellar"
+  title="OpenZeppelin Contracts Wizard"
+  allow="clipboard-write"
+  className="w-full rounded-xl"
+  style={{ border: 0, height: "calc(100vh - 206px)", minHeight: "600px" }}
+/>
 
 For a walkthrough on using these contracts check out the video linked below!
 
@@ -77,7 +79,7 @@ OpenZeppelin Stellar Contracts is a collection of audited contracts and utilitie
 
 **Token Vault** The Fungible Token Vault extends the Fungible Token and implements [SEP-56 Tokenized Vault Standard](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0056.md), enabling fungible tokens to represent shares in an underlying asset pool. The tokenized vault standard is the formalized interface for yield-bearing vaults that hold underlying assets. Vault shares enable hyperfungible collaterals in DeFi and remain fully compatible with standard fungible token operations.
 
-**Confidential Token** The Confidential Token (`stellar-confidential`, released in `v0.8.0`) wraps an existing SEP-41 token and adds private balances and transfer amounts. Users deposit the underlying token, transfer it confidentially, and withdraw it. Standard SEP-41 clients cannot call the contract directly, because it exposes `confidential_balance` and `confidential_transfer` instead of `balance` and `transfer`. Balances are Pedersen commitments, and the contract verifies an UltraHonk proof onchain for every operation that spends private state. Sender and recipient addresses stay public. Auditors decrypt amounts with registered auditor keys, and an optional compliance extension adds freezing, an external authorization policy (such as an allowlist), and clawback. Proofs are not yet zero-knowledge. See [Confidential Tokens](../build/apps/privacy.mdx#confidential-tokens) for resources and current limitations.
+**Confidential Token** The Confidential Token (`stellar-confidential`, released in `v0.8.0`) wraps an existing SEP-41 token and adds private balances and transfer amounts. Users deposit the underlying token, transfer it confidentially, and withdraw it. Standard SEP-41 clients cannot call the contract directly, because it exposes `confidential_balance` and `confidential_transfer` instead of `balance` and `transfer`. Balances are Pedersen commitments, and the contract verifies an UltraHonk proof onchain for every operation that spends private state. Sender and recipient addresses stay public. Auditors decrypt amounts with registered auditor keys, and an optional compliance extension adds freezing, an external authorization policy (such as an allowlist), and clawback. Proofs are not yet zero-knowledge. See [Confidential Tokens](/docs/build/apps/privacy#confidential-tokens) for resources and current limitations.
 
 **Smart Accounts**
 
diff --git a/docs/tools/openzeppelin-relayer.mdx b/docs/tools/openzeppelin-relayer.mdx
index 8ef7a6f21..5d9519b5b 100644
--- a/docs/tools/openzeppelin-relayer.mdx
+++ b/docs/tools/openzeppelin-relayer.mdx
@@ -1,8 +1,6 @@
 ---
 title: OpenZeppelin Relayer
 description: OpenZeppelin Relayer is an open source framework for submitting transactions to the Stellar network, and Stellar Channels is the managed service OpenZeppelin runs on top of it.
-sidebar_label: OpenZeppelin Relayer
-sidebar_position: 43
 ---
 
 Launchtube, which served as an experimental service for fee sponsorship and contract invocations, has been instrumental in early-stage deployments and developer experimentation. However, while functional for testing and early use cases, Launchtube does not have the same maturity or scalability as OpenZeppelin’s Relayer, which is why the Stellar Development Foundation has discontinued the Launchtube service and points developers to OpenZeppelin’s managed Stellar Channels service as the replacement.
@@ -11,11 +9,11 @@ OpenZeppelin Relayer is an open source (AGPL-3.0) framework for submitting Stell
 
 [Stellar Channels](https://docs.openzeppelin.com/relayer/guides/stellar-channels-guide) is the managed service OpenZeppelin operates on top of the Relayer and the Channels plugin. There are no servers, relayers, or channel accounts for you to configure, because OpenZeppelin runs the pool of channel accounts and covers the fees, subject to a fair use policy.
 
-:::note
+<Note>
 
 The examples on this page use the managed Channels service, so they authenticate with a Channels API key rather than talking to a relayer you run yourself.
 
-:::
+</Note>
 
 ## Stellar Channels status
 
@@ -286,11 +284,11 @@ Let’s create another simple application, this application submits a transfer t
 
 The application is based on the Next.js framework and has server side code and client side code. The `@openzeppelin/relayer-plugin-channels` SDK makes HTTPS-requests to OpenZeppelin endpoints, which will trigger CORS errors when run client side, but by using the SDK server side, CORS will not be an issue.
 
-### Server Side
+### Server Side {#server-side-1}
 
 In this simple application we only have one function server side, and that’s a function making a transfer of XLM tokens from one account to another, by submitting a transaction through Channels.
 
-#### 1. Initialize the Channels client
+#### 1. Initialize the Channels client {#1-initialize-the-channels-client-1}
 
 First the two necessary SDKs are imported, and the Channels client is initialized. In this tutorial we use testnet, so the Channels endpoint for testnet is used as the base URL. The API key can be generated [here](https://channels.openzeppelin.com/testnet/gen).
 
@@ -435,11 +433,11 @@ export const SendTransaction = async (destinationPublicKey: string, amount: stri
 }
 ```
 
-### Client Side
+### Client Side {#client-side-1}
 
 The client side code shows a form with input fields for a transfer-to-address, and amount to transfer, on the page in the browser. When the form is filled out and submitted, the server side function will be called with the form values as parameters. When the function returns with the transaction hash, the hash is shown on the page instead of the form. The functionality is very simple, but serves well as an end-to-end example of submitting a token transfer transaction with Channels.
 
-#### 1. Call server side function
+#### 1. Call server side function {#1-call-server-side-function-1}
 
 The client code has a function `sendXLM()` that works as a form action function. The function calls the server side function `SendTransaction()` with the transfer destination public key and amount as parameters.
 
@@ -457,7 +455,7 @@ const sendXLM = async (formData: FormData) => {
 
 The response is stored as the result state.
 
-#### 2. Markup code
+#### 2. Markup code {#2-markup-code-1}
 
 The page markup code checks if `result` contains a value. If not, the form for submitting a transfer is shown, and if `result` does contain a value, it’s shown on the page instead. That’s all there is to the client side markup code.
 
diff --git a/docs/tools/quickstart/README.mdx b/docs/tools/quickstart/README.mdx
deleted file mode 100644
index 00cdc0005..000000000
--- a/docs/tools/quickstart/README.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: Quickstart
-description: Quickstart is a local Stellar network environment (node) for development and testing.
-sidebar_label: Quickstart
-sidebar_position: 40
----
-
-# Quickstart
-
-Quickstart is a local Stellar network environment (node) that allows developers to run a local version of the Stellar network for development and testing. Quickstart runs a local version of Stellar Core, Horizon, RPC, and everything else needed to replicate the public network.
-
-For more information about running Stellar services in production, see the documentation for the individual services here:
-
-- [How to run Stellar Core in production](../../validators/README.mdx)
-- [How to run Horizon in production](../../data/apis/horizon/admin-guide/overview.mdx)
-- [How to run RPC in production](../../data/apis/rpc/admin-guide/README.mdx)
-
-Quickstart is intended for use in development, not in production, although running it in public mode will cause it to join the public network.
-
-**Run Quickstart**
-
-Ready to get started? The Getting Started section of the Quickstart documentation will show how to run Quickstart, but there are some configurations to decide on first. Most importantly, the network mode Quickstart will run in (pubnet, testnet, futurenet, local). Read about the modes in the Network Modes section.
-
-:::info
-
-Quickstart can be deployed using the Getting Started guide, but the configurations used in the guide may not be ideal for your use case, so please familiarize yourself with the options to configure Quickstart to fit your use case.
-
-:::
-
-:::caution
-
-Please note: the quickstart image is not intended for production purposes. Information about setting up a production environment is available [here](../../validators/README.mdx).
-
-:::
diff --git a/docs/tools/quickstart/advanced-usage/README.mdx b/docs/tools/quickstart/advanced-usage/README.mdx
deleted file mode 100644
index ef067ee06..000000000
--- a/docs/tools/quickstart/advanced-usage/README.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: Advanced Usage
-description: Quickstart can be configured to your personal preferences and use cases
-sidebar_label: Advanced Usage
-sidebar_position: 50
----
-
-import DocCardList from "@theme/DocCardList";
-
-# Advanced Usage
-
-Quickstart works out of the box, and when launched using the Stellar CLI, no setup or configuration is required. While the standard configuration may work for many use cases, it may not fit everyone’s needs. If a custom setup and configuration is needed, the Quickstart container can be run using the docker CLI.
-
-Read more about Quickstart configuration and setup:
-
-<DocCardList />
diff --git a/docs/tools/quickstart/advanced-usage/_category_.json b/docs/tools/quickstart/advanced-usage/_category_.json
deleted file mode 100644
index 4fb601999..000000000
--- a/docs/tools/quickstart/advanced-usage/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsed": true
-}
\ No newline at end of file
diff --git a/docs/tools/quickstart/advanced-usage/container.mdx b/docs/tools/quickstart/advanced-usage/container.mdx
index db440c94e..5960db612 100644
--- a/docs/tools/quickstart/advanced-usage/container.mdx
+++ b/docs/tools/quickstart/advanced-usage/container.mdx
@@ -1,12 +1,8 @@
 ---
 title: Container
 description: Quickstart is packaged as a docker container
-sidebar_label: Container
-sidebar_position: 10
 ---
 
-# Container
-
 Quickstart is packaged as a docker container image and provides a default, non-validating, ephemeral configuration that should work for most developers. By configuring a container using this image with a host-based volume (described below in the "Configuration" section) an operator gains access to full configuration customization and persistence of data.
 
 The Quickstart [docker image](https://hub.docker.com/r/stellar/quickstart) uses the following software:
@@ -18,4 +14,4 @@ The Quickstart [docker image](https://hub.docker.com/r/stellar/quickstart) uses
 - [stellar-rpc](https://github.com/stellar/stellar-rpc/tree/main/cmd/stellar-rpc)
 - [supervisord](http://supervisord.org)
 
-The Stellar CLI has commands for starting and stopping a Quickstart container, and also a command to get logs from a running container. See Stellar CLI [documentation](../../cli/stellar-cli.mdx#stellar-container) for more information.
+The Stellar CLI has commands for starting and stopping a Quickstart container, and also a command to get logs from a running container. See Stellar CLI [documentation](../../cli/stellar-cli#stellar-container) for more information.
diff --git a/docs/tools/quickstart/advanced-usage/index.mdx b/docs/tools/quickstart/advanced-usage/index.mdx
new file mode 100644
index 000000000..15d9eb9b4
--- /dev/null
+++ b/docs/tools/quickstart/advanced-usage/index.mdx
@@ -0,0 +1,36 @@
+---
+title: Advanced Usage
+description: Quickstart can be configured to your personal preferences and use cases
+---
+
+Quickstart works out of the box, and when launched using the Stellar CLI, no setup or configuration is required. While the standard configuration may work for many use cases, it may not fit everyone’s needs. If a custom setup and configuration is needed, the Quickstart container can be run using the docker CLI.
+
+Read more about Quickstart configuration and setup:
+
+<CardGroup cols={2}>
+  <Card title="Container" icon="file-lines" href="/docs/tools/quickstart/advanced-usage/container">
+
+    Quickstart is packaged as a docker container
+
+  </Card>
+  <Card title="Service Options" icon="file-lines" href="/docs/tools/quickstart/advanced-usage/service-options">
+
+    Quickstart can be started with all services enabled, or with selected services enabled
+
+  </Card>
+  <Card title="Operation Modes" icon="file-lines" href="/docs/tools/quickstart/advanced-usage/operation-modes">
+
+    Quickstart can operate in different modes for different use cases
+
+  </Card>
+  <Card title="Ports" icon="file-lines" href="/docs/tools/quickstart/advanced-usage/ports">
+
+    Quickstart can operate in different modes for different use cases
+
+  </Card>
+  <Card title="Run Commands" icon="file-lines" href="/docs/tools/quickstart/advanced-usage/run-command-examples">
+
+    Examples of run commands for starting Quickstart in the different modes
+
+  </Card>
+</CardGroup>
diff --git a/docs/tools/quickstart/advanced-usage/operation-modes.mdx b/docs/tools/quickstart/advanced-usage/operation-modes.mdx
index 4eb28237b..7f99e1daf 100644
--- a/docs/tools/quickstart/advanced-usage/operation-modes.mdx
+++ b/docs/tools/quickstart/advanced-usage/operation-modes.mdx
@@ -1,12 +1,8 @@
 ---
 title: Operation Modes
 description: Quickstart can operate in different modes for different use cases
-sidebar_label: Operation Modes
-sidebar_position: 30
 ---
 
-# Operation Modes
-
 ## Background vs. Interactive containers
 
 Docker containers can be run interactively (using the `-it` flags) or in a detached, background state (using the `-d` flag). Many of the example commands below use the `-it` flags to aid in debugging but in many cases, you will simply want to run a node in the background. It's recommended that you use the [guides](https://docs.docker.com/get-started) at docker to familiarize yourself with using docker.
@@ -49,11 +45,11 @@ By default, ledgers close automatically. (In local network mode, that's once eve
 
 Manual close is only usable in local network mode. Stellar Core requires `NODE_IS_VALIDATOR=true` to service a manual close request, and the local network is the only Quickstart configuration that sets it. The flag is accepted on the other networks and the container will start normally, but the `manualclose` request itself will fail.
 
-:::note
+<Note>
 
 The core configuration is only generated the first time a container initializes. Adding this flag to a container that already has a configuration (on a persistent volume, for example) has no effect. To pick up the change, start a fresh ephemeral container or clear the mounted volume.
 
-:::
+</Note>
 
 With manual close enabled, ledgers only advance when you explicitly trigger a close by sending the `manualclose` command to stellar-core's HTTP endpoint on port `11626`:
 
@@ -61,4 +57,4 @@ With manual close enabled, ledgers only advance when you explicitly trigger a cl
 curl "http://localhost:11626/manualclose"
 ```
 
-Each `manualclose` invocation advances the ledger by one. For a complete example of starting a local network with the flag enabled, see [Run Commands](./run-command-examples.mdx).
+Each `manualclose` invocation advances the ledger by one. For a complete example of starting a local network with the flag enabled, see [Run Commands](./run-command-examples).
diff --git a/docs/tools/quickstart/advanced-usage/ports.mdx b/docs/tools/quickstart/advanced-usage/ports.mdx
index ca359adfa..42c7b78b3 100644
--- a/docs/tools/quickstart/advanced-usage/ports.mdx
+++ b/docs/tools/quickstart/advanced-usage/ports.mdx
@@ -1,12 +1,8 @@
 ---
 title: Ports
 description: Quickstart can operate in different modes for different use cases
-sidebar_label: Ports
-sidebar_position: 40
 ---
 
-# Ports
-
 Quickstart exposes one main port through which services provide their APIs:
 
 | Port | Service                         | Description    |
diff --git a/docs/tools/quickstart/advanced-usage/run-command-examples.mdx b/docs/tools/quickstart/advanced-usage/run-command-examples.mdx
index e2fad4a4f..302e95c68 100644
--- a/docs/tools/quickstart/advanced-usage/run-command-examples.mdx
+++ b/docs/tools/quickstart/advanced-usage/run-command-examples.mdx
@@ -1,21 +1,13 @@
 ---
 title: Run Commands
 description: Examples of run commands for starting Quickstart in the different modes
-sidebar_label: Run Commands
-sidebar_position: 50
 ---
 
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
-# Run Commands
-
 Below is a list of various ways you might want to run the Quickstart container annotated to illustrate what options are enabled. It's also recommended that you should learn and get familiar with the docker command. Start an ephemeral local-only dev/test network:
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
+<Tabs>
 
-<TabItem value="unix" label="macOS/Linux">
+<Tab title="macOS/Linux">
 
 ```sh
 docker run -d \
@@ -25,9 +17,9 @@ docker run -d \
   --local
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="windows" label="Windows (PowerShell)">
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 docker run -d `
@@ -37,15 +29,15 @@ docker run -d `
   --local
 ```
 
-</TabItem>
+</Tab>
 
 </Tabs>
 
 Start an ephemeral testnet node in the foreground:
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
+<Tabs>
 
-<TabItem value="unix" label="macOS/Linux">
+<Tab title="macOS/Linux">
 
 ```sh
 docker run --rm -it \
@@ -55,9 +47,9 @@ docker run --rm -it \
   --testnet
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="windows" label="Windows (PowerShell)">
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 docker run --rm -it `
@@ -67,15 +59,15 @@ docker run --rm -it `
   --testnet
 ```
 
-</TabItem>
+</Tab>
 
 </Tabs>
 
 Start a new persistent node using the host directory `/str`:
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
+<Tabs>
 
-<TabItem value="unix" label="macOS/Linux">
+<Tab title="macOS/Linux">
 
 ```sh
 docker run -it --rm \
@@ -86,9 +78,9 @@ docker run -it --rm \
   --testnet
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="windows" label="Windows (PowerShell)">
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 docker run -it --rm `
@@ -99,15 +91,15 @@ docker run -it --rm `
   --testnet
 ```
 
-</TabItem>
+</Tab>
 
 </Tabs>
 
-Start an ephemeral local network with manual ledger close enabled. Ledgers only advance when you send the `manualclose` command to stellar-core's HTTP endpoint (see [Operation Modes](./operation-modes.mdx)):
+Start an ephemeral local network with manual ledger close enabled. Ledgers only advance when you send the `manualclose` command to stellar-core's HTTP endpoint (see [Operation Modes](./operation-modes)):
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
+<Tabs>
 
-<TabItem value="unix" label="macOS/Linux">
+<Tab title="macOS/Linux">
 
 ```sh
 docker run -d \
@@ -119,9 +111,9 @@ docker run -d \
   --enable-core-manual-close
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="windows" label="Windows (PowerShell)">
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 docker run -d `
@@ -133,6 +125,6 @@ docker run -d `
   --enable-core-manual-close
 ```
 
-</TabItem>
+</Tab>
 
 </Tabs>
diff --git a/docs/tools/quickstart/advanced-usage/service-options.mdx b/docs/tools/quickstart/advanced-usage/service-options.mdx
index 0cd0d597d..f8a09e6ca 100644
--- a/docs/tools/quickstart/advanced-usage/service-options.mdx
+++ b/docs/tools/quickstart/advanced-usage/service-options.mdx
@@ -1,12 +1,8 @@
 ---
 title: Service Options
 description: Quickstart can be started with all services enabled, or with selected services enabled
-sidebar_label: Service Options
-sidebar_position: 20
 ---
 
-# Service Options
-
 All network modes run all the services (Core, Horizon, and RPC) by default, but the --enable option can be used to enable just some of the services. The enable option behavior is slightly different in local network mode.
 
 The option takes a comma-separated list of service names to enable. To enable all services which is the default behavior, use:
@@ -21,8 +17,8 @@ To run only select services, simply specify only those services. For example, to
  --enable rpc
 ```
 
-:::info
+<Info>
 
 In local network mode, the core service always runs no matter what options are passed, the Friendbot faucet service runs whenever Horizon is running, and Horizon is run when RPC is requested so that Friendbot is available.
 
-:::
+</Info>
diff --git a/docs/tools/quickstart/cloud/README.mdx b/docs/tools/quickstart/cloud/README.mdx
deleted file mode 100644
index e81110169..000000000
--- a/docs/tools/quickstart/cloud/README.mdx
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Cloud Deployment
-description: Quickstart can be deployed to any cloud to create a shareable test network
-sidebar_label: Cloud Deployment
-sidebar_position: 45
----
-
-import DocCardList from "@theme/DocCardList";
-
-# Cloud Deployment
-
-Quickstart can be deployed to a cloud platform to create a shareable test network for coordinated and multi-person testing.
-
-Any platform supporting a container runtime can deploy the Quickstart image:
-
-```
-docker.io/stellar/quickstart:latest
-```
-
-Use the following environment variables to configure the image:
-
-- `NETWORK` - The network that the container will setup or connect to. One of:
-  - `local` - A new local network will be created for development / testing.
-  - `testnet` - The container will connect to the public testnet.
-- `NETWORK_PASSPHRASE` - For `local` networks the network passphrase that will be used.
-- `RANDOMIZE_NETWORK_PASSPHRASE` - For `local` networks the network passphrase will have a random suffix.
-- `LIMITS` - The network limits that will be configured for smart contracts. One of:
-  - `testnet` - Limits that match the public testnet.
-  - `unlimited` - Max limits supported by the network under any configuration. Useful for experimental testing prior to optimization.
-
-:::warning
-
-Quickstart is designed for development and testing, not production.
-
-:::
-
-Examples for how to deploy on different providers:
-
-<DocCardList />
diff --git a/docs/tools/quickstart/cloud/_category_.json b/docs/tools/quickstart/cloud/_category_.json
deleted file mode 100644
index 4fb601999..000000000
--- a/docs/tools/quickstart/cloud/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsed": true
-}
\ No newline at end of file
diff --git a/docs/tools/quickstart/cloud/digitalocean.mdx b/docs/tools/quickstart/cloud/digitalocean.mdx
index cf54b12cd..cf174cb2e 100644
--- a/docs/tools/quickstart/cloud/digitalocean.mdx
+++ b/docs/tools/quickstart/cloud/digitalocean.mdx
@@ -1,12 +1,9 @@
 ---
 title: DigitalOcean
+sidebarTitle: Digital Ocean
 description: Deploy Quickstart to DigitalOcean
-sidebar_label: Digital Ocean
-sidebar_position: 10
 ---
 
-# DigitalOcean
-
 Deploy to DigitalOcean App Platform using the following link:
 
 [![Deploy to DigitalOcean](https://www.deploytodo.com/do-btn-blue.svg)](https://cloud.digitalocean.com/apps/new?repo=https://github.com/stellar/quickstart/tree/master)
diff --git a/docs/tools/quickstart/cloud/fly.io.mdx b/docs/tools/quickstart/cloud/fly.io.mdx
index 8f3d46279..27b45e63d 100644
--- a/docs/tools/quickstart/cloud/fly.io.mdx
+++ b/docs/tools/quickstart/cloud/fly.io.mdx
@@ -1,24 +1,16 @@
 ---
 title: Fly.io
 description: Deploy Quickstart to fly.io
-sidebar_label: Fly.io
-sidebar_position: 10
 ---
 
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
-# Fly.io
-
 Deploy to Fly.io using the following steps.
 
 Install the Fly CLI. See [fly.io/docs/flyctl/install](https://fly.io/docs/flyctl/install) for instructions.
 
 Launch the image:
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
+<Tabs>
+<Tab title="macOS/Linux">
 
 ```shell
 fly launch \
@@ -30,8 +22,8 @@ fly launch \
     --internal-port 8000
 ```
 
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
+</Tab>
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 fly launch `
@@ -44,5 +36,5 @@ fly launch `
     --internal-port 8000
 ```
 
-</TabItem>
+</Tab>
 </Tabs>
diff --git a/docs/tools/quickstart/cloud/index.mdx b/docs/tools/quickstart/cloud/index.mdx
new file mode 100644
index 000000000..92105b43e
--- /dev/null
+++ b/docs/tools/quickstart/cloud/index.mdx
@@ -0,0 +1,44 @@
+---
+title: Cloud Deployment
+description: Quickstart can be deployed to any cloud to create a shareable test network
+---
+
+Quickstart can be deployed to a cloud platform to create a shareable test network for coordinated and multi-person testing.
+
+Any platform supporting a container runtime can deploy the Quickstart image:
+
+```
+docker.io/stellar/quickstart:latest
+```
+
+Use the following environment variables to configure the image:
+
+- `NETWORK` - The network that the container will setup or connect to. One of:
+  - `local` - A new local network will be created for development / testing.
+  - `testnet` - The container will connect to the public testnet.
+- `NETWORK_PASSPHRASE` - For `local` networks the network passphrase that will be used.
+- `RANDOMIZE_NETWORK_PASSPHRASE` - For `local` networks the network passphrase will have a random suffix.
+- `LIMITS` - The network limits that will be configured for smart contracts. One of:
+  - `testnet` - Limits that match the public testnet.
+  - `unlimited` - Max limits supported by the network under any configuration. Useful for experimental testing prior to optimization.
+
+<Warning>
+
+Quickstart is designed for development and testing, not production.
+
+</Warning>
+
+Examples for how to deploy on different providers:
+
+<CardGroup cols={2}>
+  <Card title="Digital Ocean" icon="file-lines" href="/docs/tools/quickstart/cloud/digitalocean">
+
+    Deploy Quickstart to DigitalOcean
+
+  </Card>
+  <Card title="Fly.io" icon="file-lines" href="/docs/tools/quickstart/cloud/fly.io">
+
+    Deploy Quickstart to fly.io
+
+  </Card>
+</CardGroup>
diff --git a/docs/tools/quickstart/debugging/README.mdx b/docs/tools/quickstart/debugging/README.mdx
deleted file mode 100644
index 7d3560e09..000000000
--- a/docs/tools/quickstart/debugging/README.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: Debugging
-description: Use Quickstart for debugging
-sidebar_label: Debugging
-sidebar_position: 40
----
-
-import DocCardList from "@theme/DocCardList";
-
-# Debugging
-
-There will come a time when you want to inspect the running container, either to debug one of the services, to review logs, or perhaps some other administrative tasks.
-
-There are different ways to debug Quickstart:
-
-<DocCardList />
diff --git a/docs/tools/quickstart/debugging/_category_.json b/docs/tools/quickstart/debugging/_category_.json
deleted file mode 100644
index 4fb601999..000000000
--- a/docs/tools/quickstart/debugging/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsed": true
-}
\ No newline at end of file
diff --git a/docs/tools/quickstart/debugging/diagnostic-events.mdx b/docs/tools/quickstart/debugging/diagnostic-events.mdx
index 485c48fc7..5d1a33f8e 100644
--- a/docs/tools/quickstart/debugging/diagnostic-events.mdx
+++ b/docs/tools/quickstart/debugging/diagnostic-events.mdx
@@ -1,20 +1,16 @@
 ---
 title: Diagnostic Events
 description: Soroban diagnostic events contain logs about internal events
-sidebar_label: Diagnostic Events
-sidebar_position: 10
 ---
 
-# Diagnostic Events
-
 Soroban diagnostic events contain logs about internal events that have occurred while a contract is executing. They're particularly useful for debugging why a contract is trapped (panicked).
 
 To enable Soroban diagnostic events, provide the following command line flag when starting the container: `--enable-soroban-diagnostic-events`
 
 In local network mode, diagnostics are enabled by default and can be disabled with: `--disable-soroban-diagnostic-events`
 
-:::info
+<Info>
 
 Diagnostic events are unmetered and their execution is not metered or constrained by network limits or transaction resource limits. This means the resources consumed by an instance with diagnostic events enabled may exceed resources typically required by a deployment with diagnostic events disabled.
 
-:::
+</Info>
diff --git a/docs/tools/quickstart/debugging/index.mdx b/docs/tools/quickstart/debugging/index.mdx
new file mode 100644
index 000000000..21a4b7042
--- /dev/null
+++ b/docs/tools/quickstart/debugging/index.mdx
@@ -0,0 +1,21 @@
+---
+title: Debugging
+description: Use Quickstart for debugging
+---
+
+There will come a time when you want to inspect the running container, either to debug one of the services, to review logs, or perhaps some other administrative tasks.
+
+There are different ways to debug Quickstart:
+
+<CardGroup cols={2}>
+  <Card title="Diagnostic Events" icon="file-lines" href="/docs/tools/quickstart/debugging/diagnostic-events">
+
+    Soroban diagnostic events contain logs about internal events
+
+  </Card>
+  <Card title="Viewing Logs" icon="file-lines" href="/docs/tools/quickstart/debugging/viewing-logs">
+
+    View logs inside Quickstart the container
+
+  </Card>
+</CardGroup>
diff --git a/docs/tools/quickstart/debugging/viewing-logs.mdx b/docs/tools/quickstart/debugging/viewing-logs.mdx
index 5d989de5b..2034aa6f1 100644
--- a/docs/tools/quickstart/debugging/viewing-logs.mdx
+++ b/docs/tools/quickstart/debugging/viewing-logs.mdx
@@ -1,12 +1,8 @@
 ---
 title: Viewing Logs
 description: View logs inside Quickstart the container
-sidebar_label: Viewing Logs
-sidebar_position: 20
 ---
 
-# Viewing Logs
-
 You can view logs by starting a new interactive shell inside the running container:
 
 ```sh
diff --git a/docs/tools/quickstart/explorer.mdx b/docs/tools/quickstart/explorer.mdx
index 5111b629e..8546aac49 100644
--- a/docs/tools/quickstart/explorer.mdx
+++ b/docs/tools/quickstart/explorer.mdx
@@ -1,8 +1,6 @@
 ---
 title: Explorer
 description: Using Explorer When Lab runs in Quickstart
-sidebar_label: Explorer
-sidebar_position: 15
 ---
 
 When you run **Stellar Lab** via **Quickstart**, a lightweight block/transaction explorer is automatically available alongside Lab. This makes it easy to inspect network activity on your local Quickstart network while you build and test.
diff --git a/docs/tools/quickstart/faucet.mdx b/docs/tools/quickstart/faucet.mdx
index 3d8a15ee3..1c7dff6dc 100644
--- a/docs/tools/quickstart/faucet.mdx
+++ b/docs/tools/quickstart/faucet.mdx
@@ -1,11 +1,8 @@
 ---
 title: Faucet
 description: Use the Friendbot faucet to fund accounts on Quickstart
-sidebar_position: 30
 ---
 
-# Faucet
-
 Quickstart uses Friendbot as a native asset faucet for testnet, futurenet, and local networks, just like Friendbot is used on the public testnet and futurenet.
 
 Friendbot is available on `:8000/friendbot` and can be used to fund accounts and contracts. For example:
diff --git a/docs/tools/quickstart/getting-started/README.mdx b/docs/tools/quickstart/getting-started/README.mdx
deleted file mode 100644
index 9f27cc97b..000000000
--- a/docs/tools/quickstart/getting-started/README.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: Getting Started
-description: Use Stellar CLI to install Quickstart
-sidebar_label: Getting Started
-sidebar_position: 10
----
-
-# Getting Started
-
-In this guide, you will set up Quickstart using the Stellar CLI. Quickstart will use the standard configuration, which will work for many use cases. For a more customized setup of Quickstart, see the Advanced Usage section.
-
-## Prerequisites
-
-Before following the steps in this guide, the following must be installed and setup on your local system:
-
-- [Stellar CLI](../../../build/smart-contracts/getting-started/setup.mdx#install-the-stellar-cli)
-- [Docker](https://docs.docker.com/get-started/get-docker)
-
-## Start Quickstart
-
-When you use the Stellar CLI to start Quickstart, the docker image will automatically be downloaded, and the standard configuration applied. All you need to do to get started is to run this command:
-
-```sh
-stellar container start local
-```
-
-In this example, the network mode local is chosen, see the Network Modes section for more information about available network modes. After running the command, Quickstart is running on your local system. In the next step, you will use Stellar Lab to verify Quickstart is working correctly.
diff --git a/docs/tools/quickstart/getting-started/_category_.json b/docs/tools/quickstart/getting-started/_category_.json
deleted file mode 100644
index 4fb601999..000000000
--- a/docs/tools/quickstart/getting-started/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsed": true
-}
\ No newline at end of file
diff --git a/docs/tools/quickstart/getting-started/connect-stellar-lab.mdx b/docs/tools/quickstart/getting-started/connect-stellar-lab.mdx
index 8af8d2a28..8e373ab4a 100644
--- a/docs/tools/quickstart/getting-started/connect-stellar-lab.mdx
+++ b/docs/tools/quickstart/getting-started/connect-stellar-lab.mdx
@@ -1,12 +1,8 @@
 ---
 title: Connect Stellar Lab
 description: Connect Quickstart to Stellar Lab
-sidebar_label: Connect Stellar Lab
-sidebar_position: 10
 ---
 
-# Connect Stellar Lab
-
 One way to confirm that Quickstart was successfully started and is available is to connect to Quickstart from [Stellar Lab](https://lab.stellar.org).
 
 Navigate to [Stellar Lab](https://lab.stellar.org) and in the top right corner, use the dropdown to select the Custom network. This will allow you to provide connection details - use these testnet details:
diff --git a/docs/tools/quickstart/getting-started/deploy-smart-contract.mdx b/docs/tools/quickstart/getting-started/deploy-smart-contract.mdx
index 88c81eb29..6cc148bff 100644
--- a/docs/tools/quickstart/getting-started/deploy-smart-contract.mdx
+++ b/docs/tools/quickstart/getting-started/deploy-smart-contract.mdx
@@ -1,16 +1,8 @@
 ---
 title: Deploy Smart Contract
 description: Deploy a smart contract to the Quickstart local network.
-sidebar_label: Deploy Smart Contract
-sidebar_position: 20
 ---
 
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
-# Deploy Smart Contract
-
 Now you can deploy a smart contract on the Quickstart local network. If you already have a smart contract, you can deploy your existing smart contract, otherwise, you can follow this guide to create a smart contract and build it.
 
 ## Create Identity
@@ -27,9 +19,9 @@ The identity will have a private and a public key, and can be called by the name
 
 Deploying a smart contract to Quickstart testnet is not very different from deploying a smart contract to the public testnet. Specify the RPC URL to be Quickstart’s and you can deploy it:
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
+<Tabs>
 
-<TabItem value="unix" label="macOS/Linux">
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract deploy \
@@ -39,9 +31,9 @@ stellar contract deploy \
   --alias hello_world
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="windows" label="Windows (PowerShell)">
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract deploy `
@@ -51,7 +43,7 @@ stellar contract deploy `
   --alias hello_world
 ```
 
-</TabItem>
+</Tab>
 
 </Tabs>
 
@@ -59,9 +51,9 @@ stellar contract deploy `
 
 Now you have deployed the smart contract to the Quickstart testnet, you can also invoke it:
 
-<Tabs groupId="platform" defaultValue={getPlatform()}>
+<Tabs>
 
-<TabItem value="unix" label="macOS/Linux">
+<Tab title="macOS/Linux">
 
 ```sh
 stellar contract invoke \
@@ -73,9 +65,9 @@ stellar contract invoke \
   --to RPC
 ```
 
-</TabItem>
+</Tab>
 
-<TabItem value="windows" label="Windows (PowerShell)">
+<Tab title="Windows (PowerShell)">
 
 ```powershell
 stellar contract invoke `
@@ -87,7 +79,7 @@ stellar contract invoke `
   --to RPC
 ```
 
-</TabItem>
+</Tab>
 
 </Tabs>
 
diff --git a/docs/tools/quickstart/getting-started/index.mdx b/docs/tools/quickstart/getting-started/index.mdx
new file mode 100644
index 000000000..ea0a65ef7
--- /dev/null
+++ b/docs/tools/quickstart/getting-started/index.mdx
@@ -0,0 +1,23 @@
+---
+title: Getting Started
+description: Use Stellar CLI to install Quickstart
+---
+
+In this guide, you will set up Quickstart using the Stellar CLI. Quickstart will use the standard configuration, which will work for many use cases. For a more customized setup of Quickstart, see the Advanced Usage section.
+
+## Prerequisites
+
+Before following the steps in this guide, the following must be installed and setup on your local system:
+
+- [Stellar CLI](/docs/build/smart-contracts/getting-started/setup#install-the-stellar-cli)
+- [Docker](https://docs.docker.com/get-started/get-docker)
+
+## Start Quickstart
+
+When you use the Stellar CLI to start Quickstart, the docker image will automatically be downloaded, and the standard configuration applied. All you need to do to get started is to run this command:
+
+```sh
+stellar container start local
+```
+
+In this example, the network mode local is chosen, see the Network Modes section for more information about available network modes. After running the command, Quickstart is running on your local system. In the next step, you will use Stellar Lab to verify Quickstart is working correctly.
diff --git a/docs/tools/quickstart/index.mdx b/docs/tools/quickstart/index.mdx
new file mode 100644
index 000000000..803030b82
--- /dev/null
+++ b/docs/tools/quickstart/index.mdx
@@ -0,0 +1,29 @@
+---
+title: Quickstart
+description: Quickstart is a local Stellar network environment (node) for development and testing.
+---
+
+Quickstart is a local Stellar network environment (node) that allows developers to run a local version of the Stellar network for development and testing. Quickstart runs a local version of Stellar Core, Horizon, RPC, and everything else needed to replicate the public network.
+
+For more information about running Stellar services in production, see the documentation for the individual services here:
+
+- [How to run Stellar Core in production](/docs/validators)
+- [How to run Horizon in production](/docs/data/apis/horizon/admin-guide/overview)
+- [How to run RPC in production](/docs/data/apis/rpc/admin-guide)
+
+Quickstart is intended for use in development, not in production, although running it in public mode will cause it to join the public network.
+
+**Run Quickstart**
+
+Ready to get started? The Getting Started section of the Quickstart documentation will show how to run Quickstart, but there are some configurations to decide on first. Most importantly, the network mode Quickstart will run in (pubnet, testnet, futurenet, local). Read about the modes in the Network Modes section.
+
+<Info>
+
+Quickstart can be deployed using the Getting Started guide, but the configurations used in the guide may not be ideal for your use case, so please familiarize yourself with the options to configure Quickstart to fit your use case.
+
+</Info>
+<Warning>
+
+Please note: the quickstart image is not intended for production purposes. Information about setting up a production environment is available [here](/docs/validators).
+
+</Warning>
diff --git a/docs/tools/quickstart/network-modes.mdx b/docs/tools/quickstart/network-modes.mdx
index 4bba3a0e5..e17e13e68 100644
--- a/docs/tools/quickstart/network-modes.mdx
+++ b/docs/tools/quickstart/network-modes.mdx
@@ -1,12 +1,8 @@
 ---
 title: Network Modes
 description: Quickstart supports the network modes local, testnet, futurenet and pubnet
-sidebar_label: Network Modes
-sidebar_position: 20
 ---
 
-# Network Modes
-
 Quickstart can operate in different network modes, and you need to decide which mode is suitable for your purpose before starting the container. The four available network modes are `local`, `testnet`, `futurenet` and `pubnet` (mainnet).
 
 The [Stellar Lab](https://lab.stellar.org) can connect to Quickstart, which makes it easy to create and fund accounts.
@@ -20,7 +16,7 @@ The local network mode allows you to customize Quickstart by adding parameters t
   - `default` leaves limits set extremely low which is stellar-core's default configuration
   - `testnet` sets limits to match those used on testnet (the default quickstart configuration)
   - `unlimited` sets limits to the maximum resources that can be configured
-- `--enable-core-manual-close` to turn off automatic ledger closing, so ledgers advance only when you trigger them yourself (defaults to `false`). See [Operation Modes](./advanced-usage/operation-modes.mdx#manual-close-mode).
+- `--enable-core-manual-close` to turn off automatic ledger closing, so ledgers advance only when you trigger them yourself (defaults to `false`). See [Operation Modes](./advanced-usage/operation-modes#manual-close-mode).
 
 Some settings and values are specific to the local network mode, which you must be aware of when running Quickstart in local network mode.
 
@@ -59,8 +55,8 @@ The futurenet network mode works like the testnet, and the biggest difference is
 
 In pubnet network mode, Quickstart will be a part of the public production Steller network, also known as the mainnet. In pubnet mode, Quickstart will consume more disk, memory, and CPU resources because of the size of the ledger and frequency of transactions. If disk space warnings occur and the image is being used on a Docker runtime that uses a VM, like that of macOS and Windows, the VM may need to have its disk space allocation increased.
 
-:::caution
+<Warning>
 
 Quickstart is not suitable for any production use as it has a fixed root account. Any private network intended for production use would also require a unique network passphrase.
 
-:::
+</Warning>
diff --git a/docs/tools/ramps/README.mdx b/docs/tools/ramps/README.mdx
deleted file mode 100644
index c43c52ebb..000000000
--- a/docs/tools/ramps/README.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: Ramps
-sidebar_position: 60
----
-
-import DocCardList from "@theme/DocCardList";
-
-On and off-ramps (called [anchors](../../learn/fundamentals/anchors.mdx) in the Stellar universe) that connect the Stellar network to traditional financial rails.
-
-Stellar has anchor services operating worldwide. View the [Anchor Directory](https://anchors.stellar.org) for information on Stellar anchors.
-
-Anchors can issue their own assets on the Stellar network, or they can honor assets that already exist.
-
-You can set up an anchor by using the SDF-maintained [Anchor Platform](../../platforms/anchor-platform/README.mdx), which is the easiest way to deploy an anchor service compatible with Stellar Ecosystem Proposals (SEPs).
-
-<DocCardList />
diff --git a/docs/tools/ramps/index.mdx b/docs/tools/ramps/index.mdx
new file mode 100644
index 000000000..20f0db694
--- /dev/null
+++ b/docs/tools/ramps/index.mdx
@@ -0,0 +1,18 @@
+---
+title: Ramps
+description: "On and off-ramps (called anchors in the Stellar universe) that connect the Stellar network to traditional financial rails."
+---
+
+Stellar has anchor services operating worldwide. View the [Anchor Directory](https://anchors.stellar.org) for information on Stellar anchors.
+
+Anchors can issue their own assets on the Stellar network, or they can honor assets that already exist.
+
+You can set up an anchor by using the SDF-maintained [Anchor Platform](/docs/platforms/anchor-platform), which is the easiest way to deploy an anchor service compatible with Stellar Ecosystem Proposals (SEPs).
+
+<CardGroup cols={2}>
+  <Card title="MoneyGram Ramps" icon="file-lines" href="/docs/tools/ramps/moneygram">
+
+    MoneyGram Ramps is a MoneyGram product that enables users of third-party applications, such as crypto wallets and exchanges, to cash-in (deposit) and...
+
+  </Card>
+</CardGroup>
diff --git a/docs/tools/ramps/moneygram.mdx b/docs/tools/ramps/moneygram.mdx
index f9dda8ea6..5197e8c3b 100644
--- a/docs/tools/ramps/moneygram.mdx
+++ b/docs/tools/ramps/moneygram.mdx
@@ -1,7 +1,6 @@
 ---
 title: MoneyGram Ramps
-sidebar_label: MoneyGram Ramps
-sidebar_position: 10
+description: "MoneyGram Ramps is a MoneyGram product that enables users of third-party applications, such as crypto wallets and exchanges, to cash-in (deposit) and..."
 ---
 
 MoneyGram Ramps is a MoneyGram product that enables users of third-party applications, such as crypto wallets and exchanges, to cash-in (deposit) and cash-out (withdrawal) USDC on Stellar.
diff --git a/docs/tools/scaffold-stellar.mdx b/docs/tools/scaffold-stellar.mdx
index c21c25d57..809a8a5e2 100644
--- a/docs/tools/scaffold-stellar.mdx
+++ b/docs/tools/scaffold-stellar.mdx
@@ -1,12 +1,8 @@
 ---
 title: Scaffold Stellar
 description: Convention-over-configuration toolkit for Stellar smart contract development
-sidebar_label: Scaffold Stellar
-sidebar_position: 45
 ---
 
-import YouTube from "@site/src/components/YouTube";
-
 **Scaffold Stellar** is a developer toolkit for building decentralized applications (dApps) and smart contracts on the Stellar blockchain. It helps you go from idea to working full-stack dApp faster — by providing CLI tools, reusable contract templates, a smart contract registry, and a modern frontend.
 
 Visit the [Scaffold Stellar](https://scaffoldstellar.org) homepage for guides, docs, and more.
@@ -36,7 +32,9 @@ cargo install --locked stellar-scaffold-cli
 cargo install --locked stellar-registry-cli
 ```
 
-:::tip[For a faster install, use cargo-binstall]
+<Tip>
+
+**For a faster install, use cargo-binstall**
 
 Instead of building from source, you can speed up the installation by getting the binary directly using [cargo-binstall](https://github.com/cargo-bins/cargo-binstall). This is especially useful in CI environments.
 
@@ -48,11 +46,17 @@ cargo install cargo-binstall
 cargo binstall stellar-scaffold-cli stellar-registry-cli
 ```
 
-:::
+</Tip>
 
 While the CLIs are installing, check out this intro to Scaffold Stellar!
 
-<YouTube ID="86hWe8Ragtg" />
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/86hWe8Ragtg?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
 
 ### Creating a New Project
 
diff --git a/docs/tools/sdks/README.mdx b/docs/tools/sdks/README.mdx
deleted file mode 100644
index 998232e88..000000000
--- a/docs/tools/sdks/README.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: "Explore SDKs for Blockchain Development with JavaScript, Python & More"
-sidebar_label: SDKs
-description: "Explore SDKs for building blockchain applications. Use JavaScript, Python, and more to interact with the Stellar network and streamline development."
-sidebar_position: 10
----
-
-# SDKs
-
-import DocCardList from "@theme/DocCardList";
-
-The SDK section is split into three categories:
-
-- [Contract SDKs](./contract-sdks.mdx) that are used to build smart contracts that will be deployed to the Stellar network;
-- [Client & XDR SDKs](./client-sdks.mdx) that are used by applications to interact with the network;
-- [Build your own SDK](./build-your-own.mdx) that details the minimum requirements for building your own SDK.
-
-<DocCardList />
diff --git a/docs/tools/sdks/_category_.json b/docs/tools/sdks/_category_.json
deleted file mode 100644
index 0d4475828..000000000
--- a/docs/tools/sdks/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": false
-}
diff --git a/docs/tools/sdks/build-your-own.mdx b/docs/tools/sdks/build-your-own.mdx
index 811f140fa..96e295cb9 100644
--- a/docs/tools/sdks/build-your-own.mdx
+++ b/docs/tools/sdks/build-your-own.mdx
@@ -1,13 +1,13 @@
 ---
 title: "Build Your Own Contract SDK"
-sidebar_position: 30
+description: "This is for building an SDK for writing smart contracts."
 ---
 
-:::note
+<Note>
 
 This is for building an SDK for writing smart contracts.
 
-:::
+</Note>
 
 Soroban currently has one SDF-maintained SDK for writing contracts in Rust, which can be found [here][soroban-sdk]. A community-maintained SDK is available for writing contracts in AssemblyScript, which can be found [here][as-soroban-sdk].
 
diff --git a/docs/tools/sdks/client-sdks.mdx b/docs/tools/sdks/client-sdks.mdx
index 7b01bec0c..c714e1c71 100644
--- a/docs/tools/sdks/client-sdks.mdx
+++ b/docs/tools/sdks/client-sdks.mdx
@@ -1,19 +1,16 @@
 ---
-title: "Simplify Blockchain Development with SDKs for Java, Python, and More"
-sidebar_label: "Client & XDR SDKs"
-sidebar_position: 20
+title: "Client & XDR SDKs"
+"og:title": "Simplify Blockchain Development with SDKs for Java, Python, and More"
 description: "Explore the Stellar SDK library to simplify blockchain development. Leverage Rust, JavaScript, Python, and more to build on and integrate with the network."
 ---
 
-# Client & XDR SDKs
-
 Client and XDR SDKs are used by applications to interact with the network.
 
-:::note
+<Note>
 
-For SDKs for building smart contracts, see [Contract SDKs](./contract-sdks.mdx).
+For SDKs for building smart contracts, see [Contract SDKs](./contract-sdks).
 
-:::
+</Note>
 
 All SDKs are open-source; file a GitHub issue or pull request in the specific SDK repository if you have questions or suggestions.
 
@@ -59,7 +56,7 @@ Functionality for interacting with Stellar data can be found in the following Ru
   Provides Stellar Strkey (Address) [SEP-23] encoding/decoding. **Maintained by SDF.**
 
 [XDR]: ../../learn/fundamentals/data-format/xdr
-[XDR-JSON]: ../../learn/fundamentals/data-format/xdr-json.mdx
+[XDR-JSON]: ../../learn/fundamentals/data-format/xdr-json
 [SEP-23]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0023.md
 
 - `soroban-client` - [Code](https://github.com/rahul-soshte/rs-soroban-client) | [Docs](https://docs.rs/soroban-client/latest/soroban_client)
@@ -127,9 +124,9 @@ This SDK is split up into separate packages, all of which you can find in the [G
 - `txnbuild` [SDK](https://github.com/stellar/go-stellar-sdk/tree/main/txnbuild) | [Docs](https://godoc.org/github.com/stellar/go-stellar-sdk/txnbuild): enables the construction, signing, and encoding of Stellar transactions.
 - `Horizon Client` [SDK](https://github.com/stellar/go-stellar-sdk/tree/main/clients/horizonclient) | [Docs](https://godoc.org/github.com/stellar/go-stellar-sdk/clients/horizonclient): provides a web client for interfacing with Horizon server REST endpoints to retrieve ledger information and submit transactions built with `txnbuild`.
 - `RPC Client` [SDK](https://github.com/stellar/go-stellar-sdk/tree/main/clients/rpcclient) | [Docs](https://pkg.go.dev/github.com/stellar/go-stellar-sdk/clients/rpcclient): provides an SDK wrapper to invoke RPC endpoints.
-- [Ingest SDK](../../data/indexers/build-your-own/ingest-sdk/README.mdx): acquire and parse data from the Stellar network.
+- [Ingest SDK](/docs/data/indexers/build-your-own/ingest-sdk): acquire and parse data from the Stellar network.
 
-## C# .NET
+## C# .NET {#c-net}
 
 [C# .NET SDK](https://github.com/Beans-BV/dotnet-stellar-sdk) | [Docs](https://elucidsoft.github.io/dotnet-stellar-sdk)
 
diff --git a/docs/tools/sdks/contract-sdks.mdx b/docs/tools/sdks/contract-sdks.mdx
index 07c50304f..448008c7f 100644
--- a/docs/tools/sdks/contract-sdks.mdx
+++ b/docs/tools/sdks/contract-sdks.mdx
@@ -1,18 +1,16 @@
 ---
-title: "Build smart contracts that will be deployed to the Stellar network"
-sidebar_label: Contract SDKs
-sidebar_position: 10
+title: Contract SDKs
+"og:title": Build smart contracts that will be deployed to the Stellar network
+description: "Contract SDKs are used to build smart contracts that will be deployed to the Stellar network."
 ---
 
-# Contract SDKs
-
 Contract SDKs are used to build smart contracts that will be deployed to the Stellar network.
 
-:::note
+<Note>
 
-For Client and XDR SDKs, visit this [page](./client-sdks.mdx).
+For Client and XDR SDKs, visit this [page](./client-sdks).
 
-:::
+</Note>
 
 All SDKs are open-source; file a GitHub issue or pull request in the specific SDK repository if you have questions or suggestions.
 
@@ -73,13 +71,13 @@ OpenZeppelin Contracts are published in four crates:
 - Stellar Contract Utilities: https://crates.io/crates/stellar-contract-utils
 - Stellar Tokens: https://crates.io/crates/stellar-tokens
 
-Refer to the [OpenZeppelin for Stellar Contracts](../openzeppelin-contracts.mdx#openzeppelin-stellar-contracts-and-utilities) page for additional information.
+Refer to the [OpenZeppelin for Stellar Contracts](../openzeppelin-contracts#openzeppelin-stellar-contracts-and-utilities) page for additional information.
 
 ## Stellar Axelar Std Derive Rust Crate
 
 Axelar has created a Rust crate with useful macros for Stellar smart contract development. Please see Rust Crate [`stellar_axelar_std_derive`](https://axelarnetwork.github.io/axelar-amplifier-stellar/stellar_axelar_std_derive/index.html) for Attribute Macros and Derive Macros, and additional information.
 
-## Stellar Multicall / Router SDK
+## Stellar Multicall / Router SDK {#stellar-multicall--router-sdk}
 
 The Stellar Router SDK is a lightweight multicall contract that enables developers to execute multiple Soroban contract calls within a single transaction. While Soroban normally allows only one contract invocation per transaction, the Router bundles multiple calls through a single entry point, effectively enable complex, multi-step workflows to be executed atomically.
 
diff --git a/docs/tools/sdks/index.mdx b/docs/tools/sdks/index.mdx
new file mode 100644
index 000000000..38bdfa230
--- /dev/null
+++ b/docs/tools/sdks/index.mdx
@@ -0,0 +1,29 @@
+---
+title: SDKs
+"og:title": "Explore SDKs for Blockchain Development with JavaScript, Python & More"
+description: "Explore SDKs for building blockchain applications. Use JavaScript, Python, and more to interact with the Stellar network and streamline development."
+---
+
+The SDK section is split into three categories:
+
+- [Contract SDKs](/docs/tools/sdks/contract-sdks) that are used to build smart contracts that will be deployed to the Stellar network;
+- [Client & XDR SDKs](/docs/tools/sdks/client-sdks) that are used by applications to interact with the network;
+- [Build your own SDK](/docs/tools/sdks/build-your-own) that details the minimum requirements for building your own SDK.
+
+<CardGroup cols={2}>
+  <Card title="Contract SDKs" icon="file-lines" href="/docs/tools/sdks/contract-sdks">
+
+    Contract SDKs are used to build smart contracts that will be deployed to the Stellar network.
+
+  </Card>
+  <Card title="Client & XDR SDKs" icon="file-lines" href="/docs/tools/sdks/client-sdks">
+
+    Explore the Stellar SDK library to simplify blockchain development. Leverage Rust, JavaScript, Python, and more to build on and integrate with the network.
+
+  </Card>
+  <Card title="Build Your Own Contract SDK" icon="file-lines" href="/docs/tools/sdks/build-your-own">
+
+    This is for building an SDK for writing smart contracts.
+
+  </Card>
+</CardGroup>
diff --git a/docs/validators/README.mdx b/docs/validators/README.mdx
deleted file mode 100644
index 5c2a9ff27..000000000
--- a/docs/validators/README.mdx
+++ /dev/null
@@ -1,76 +0,0 @@
----
-title: "Validators: Role, Setup, and Importance in Network Security & Consensus"
-sidebar_label: Validators Introduction
-description: "Learn how validators support network security and consensus. Understand their role, setup requirements, and how they help maintain the integrity of the Stellar network."
-sidebar_position: 10
----
-
-# Validators Introduction
-
-Stellar is a peer-to-peer network made up of nodes, which are computers that keep a common distributed [ledger](../learn/fundamentals/stellar-data-structures/ledgers.mdx), and that communicate to validate and add [transactions](../learn/fundamentals/transactions/operations-and-transactions.mdx) to it. Nodes use a program called Stellar Core — an implementation of the [Stellar Consensus Protocol](../learn/fundamentals/stellar-consensus-protocol.mdx) — to stay in sync as they work to agree on the validity of transaction sets and to apply them to the ledger. Generally, nodes reach consensus, apply a transaction set, and update the ledger every 5-7 seconds.
-
-This section of the docs explains how to run a validator node, which participates in consensus to validate transactions and determine network settings. A validator node _should not_ be used for network data access and transaction submission. There are two varieties of _non-validating_ nodes that can be used for those purposes, each of which has its own process for set up, interaction, maintenance, and monitoring. They are:
-
-1. [**Stellar RPC Nodes**](../data/apis/rpc/README.mdx) can be used for simulating and/or submitting transactions, as well as exposing an RPC service to query and retrieve current network state. This is the best choice for real-time use-cases.
-2. [**Galexie Nodes**](../data/indexers/build-your-own/galexie/README.mdx) can be used for retrieving and storing network data en masse for further processing. Notably, it does _not_ support transaction submission so is more suitable for indexers or analytics use-cases.
-
-If you are interested in running a validator node — because you issue an asset that you would like to help secure through transaction validation, because you want to help increase network health and decentralization, or because you want to participate in network governance — then this section of the docs is for you. It explains the technical and operational aspects of installing, configuring, and maintaining a Stellar Core validator node, and should help you figure out the best way to set up your Stellar integration.
-
-:::tip[Interested in Tier 1?]
-
-If your organization is evaluating or planning to join the Tier 1 quorum — the core group of organizations whose validators bear the safety and liveness of the network — see [Tier 1 Organizations](./tier-1-orgs.mdx) for requirements, estimated costs, and a step-by-step onboarding path. The Admin Guide below covers the technical setup for a single validator; the Tier 1 page covers what it takes to run three and join the quorum.
-
-:::
-
-## Node Setup Process
-
-The basic flow, which you can navigate through using the "Admin Guide" on the left, goes (roughly) like this:
-
-### Initial Setup
-
-1. Use the information on this _Introduction_ page to determine which [type of node](#types-of-nodes) you want to run.
-2. [Prerequisite](./admin-guide/prerequisites.mdx) software must be installed (and configured according to your needs).
-3. [Install](./admin-guide/installation.mdx) the Stellar Core software on your instance.
-4. [Configure](./admin-guide/configuring.mdx) the Stellar Core software to suit your needs and environment.
-5. [Prepare](./admin-guide/environment-preparation.mdx) your node instance and environment. This includes the optional step of setting your node up to [publish history archives](./admin-guide/publishing-history-archives.mdx) of the ledger.
-6. [Start your node](./admin-guide/running-node.mdx) and join the network.
-7. [Logging](./admin-guide/logging.mdx) and [monitoring](./admin-guide/monitoring.mdx) should be appropriately set up and used to meet your needs.
-
-### Ongoing Requirements
-
-8. [Maintenance](./admin-guide/maintenance.mdx) is required from time to time to keep your node up-to-date and participating in the network.
-9. [Network upgrades](./admin-guide/network-upgrades.mdx) require validator consensus, and you will need to consider casting a vote in the event of a protocol upgrade.
-10. [Soroban settings](./admin-guide/soroban-settings.mdx) are network-wide, configurable, and changes can be proposed by anyone. Similar to protocol upgrades, changes to these settings will require validator consensus, so you should be prepared to participate.
-
-### Other Information
-
-- Stellar Core uses a robust [command line](./admin-guide/commands.mdx) tool to control and operate a node. We've gathered information on some of the most-used commands, and linked to further, more comprehensive CLI documentation.
-- We've collected some miscellaneous helpful and [advanced](./admin-guide/advanced.mdx) information that could be useful as you understand and implement your core node.
-
-## Types of validator nodes {/* #types-of-nodes */}
-
-There are two types of validator nodes, and they perform the same basic functions: they run Stellar Core, connect to peers, submit transactions, and store the state of the ledger. The difference is this: a **Basic Validator** does not publish a history archive; a **Full Validator** publishes one covering the network's complete history.
-
-:::info
-
-Non-validating nodes, like Stellar RPC or Galexie, bundle an optimized "Captive" Core to serve their operational needs.
-
-:::
-
-### Basic Validator
-
-#### Validating, no public archive
-
-A Basic Validator keeps track of the ledger and submits transactions for possible inclusion, but it is _not_ configured to publish history archives. It does require a secret key, and is [configured to participate in consensus](./admin-guide/configuring.mdx#validating-node) by voting on — and signing off on — changes to the ledger, meaning it supports the network and increases decentralization.
-
-The advantage: signatures can serve as official endorsements of specific ledgers in real time. That’s important if, for instance, you issue an asset on Stellar that represents a real-world asset: you can let your customers know that you will only honor transactions and redeem assets from ledgers signed by your validator, and in the unlikely scenario that something happens to the network, you can use your node as the final arbiter of truth. Setting up your node as a validator allows you to resolve any questions _up front and in writing_ about how you plan to deal with disasters and disputes.
-
-### Full Validator
-
-#### Validating, offers a complete public archive
-
-A Full Validator is the same as a Basic Validator except that it also publishes a [History Archive](./admin-guide/environment-preparation.mdx) covering the network's **complete history** — snapshots of the ledger, including all transactions and their results. A Full Validator writes to an internet-facing blob store — such as AWS or Azure — so it's a bit more expensive and complex to run, but it also does the most to support the network’s resilience and decentralization.
-
-When other nodes join the network — or experience difficulty and temporarily fall out of sync — they can consult archives offered by Full Validators to catch up on the history of the network. Redundant archives prevent a single point of failure, and allow network participants to verify the veracity of a given history.
-
-Generally, organizations that run Full Validators are also part of — or on track to join — [Tier 1](./tier-1-orgs.mdx), which is a core group of network participants who run three Full Validators to contribute maximum redundancy.
diff --git a/docs/validators/admin-guide/README.mdx b/docs/validators/admin-guide/README.mdx
deleted file mode 100644
index 33e208d68..000000000
--- a/docs/validators/admin-guide/README.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: Admin Guide
-sidebar_position: 20
----
-
-import DocCardList from "@theme/DocCardList";
-
-Stellar Core is the program nodes use to communicate with other nodes to create and maintain the Stellar peer-to-peer network. It's an implementation of the Stellar Consensus Protocol configured to construct a chain of ledgers guaranteed to be in agreement across all participating nodes at all times.
-
-These pages describe various aspects of installing, configuring, and maintaining a `stellar-core` node.
-
-<DocCardList />
diff --git a/docs/validators/admin-guide/_category_.json b/docs/validators/admin-guide/_category_.json
deleted file mode 100644
index 3dcd42977..000000000
--- a/docs/validators/admin-guide/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsed": false
-}
diff --git a/docs/validators/admin-guide/advanced.mdx b/docs/validators/admin-guide/advanced.mdx
index a681feb3d..58713ebc2 100644
--- a/docs/validators/admin-guide/advanced.mdx
+++ b/docs/validators/admin-guide/advanced.mdx
@@ -1,6 +1,6 @@
 ---
 title: Advanced
-sidebar_position: 130
+description: "This page contains information that is useful to know but that should not stop somebody from running a node."
 ---
 
 This page contains information that is useful to know but that should not stop somebody from running a node.
diff --git a/docs/validators/admin-guide/commands.mdx b/docs/validators/admin-guide/commands.mdx
index fda51c677..c5c444426 100644
--- a/docs/validators/admin-guide/commands.mdx
+++ b/docs/validators/admin-guide/commands.mdx
@@ -1,19 +1,19 @@
 ---
 title: Commands
-sidebar_position: 120
+description: "Stellar Core can be controlled using a robust CLI."
 ---
 
 Stellar Core can be controlled using a robust CLI.
 
-:::info
+<Info>
 
 We will cover a selection of the _essential_ commands and syntax here, but the **very best resource** for utilizing the `stellar-core` command line is located in the [stellar-core GitHub repo].
 
 Additionally, while the commands on this page are _CLI_ commands, there is an additional set of [_HTTP_ endpoint commands] that provide further administrative control over a running core node.
 
-:::
+</Info>
 
-## Get `--help` Anywhere
+## Get `--help` Anywhere {#get---help-anywhere}
 
 The `--help` (aliases: `-h` or `-?`) option can be specified at _any place_ in the command line. It will show you the help message for the relevant command. Some example useage is as follows:
 
@@ -65,11 +65,11 @@ The **`catchup`** command will execute a catchup from history archives without c
 - `--metadata-output-stream <STREAM>`: Filename or file-descriptor number `fd:N` to stream metadata to.
 - `--force-back`: Force ledger state to a previous state, preserving older historical data.
 
-:::info
+<Info>
 
 To reiterate, this page covers a selection of the _essential_ commands, but we've only scratched the surface. The **very best, most comprehensive resource** for utilizing the `stellar-core` command line is located in the [stellar-core GitHub repo].
 
-:::
+</Info>
 
 [stellar-core GitHub repo]: https://github.com/stellar/stellar-core/blob/master/docs/software/commands.md
 [_HTTP_ endpoint commands]: https://github.com/stellar/stellar-core/blob/master/docs/software/commands.md#http-commands
diff --git a/docs/validators/admin-guide/configuring.mdx b/docs/validators/admin-guide/configuring.mdx
index e96054a5f..a59ac701c 100644
--- a/docs/validators/admin-guide/configuring.mdx
+++ b/docs/validators/admin-guide/configuring.mdx
@@ -1,17 +1,17 @@
 ---
 title: Configuring
-sidebar_position: 40
+description: "Before attempting to configure stellar-core, it is highly recommended to first try running a private network or joining the test network."
 ---
 
-:::info
+<Info>
 
 Before attempting to configure stellar-core, it is highly recommended to first try running a private network or joining the test network.
 
-:::
+</Info>
 
 ## Configuration Basics
 
-After you've [installed](./installation.mdx) Stellar Core, your next step is to complete a configuration file that specifies crucial things about your node — like whether it connects to the Testnet or the Mainnet public network, what database it writes to, and which other nodes are in its [quorum set](#choosing-your-quorum-set).
+After you've [installed](./installation) Stellar Core, your next step is to complete a configuration file that specifies crucial things about your node — like whether it connects to the Testnet or the Mainnet public network, what database it writes to, and which other nodes are in its [quorum set](#choosing-your-quorum-set).
 
 All configuration for stellar-core is done with a [TOML](https://github.com/toml-lang/toml) file. By default, Stellar Core loads that file from `./stellar-core.cfg` and Debian packages will use the `/etc/stellar/stellar-core.cfg` file. You can specify a different file to load on the command line:
 
@@ -23,11 +23,11 @@ When installing using official Debian packages systemd unit file is configured t
 
 This page will walk you through the key fields you'll need to include in your config file to get your node up and running.
 
-:::info
+<Info>
 
-This page attempts (as strictly as is possible) to focus on the specific fields and values that you may need to modify in your Stellar Core configuration file. To keep this page concise, we try to avoid conceptual context and background information. You will likely find some of that related information on the [prerequisites](./prerequisites.mdx) or [environment preparation](./environment-preparation.mdx) pages, if you'd like.
+This page attempts (as strictly as is possible) to focus on the specific fields and values that you may need to modify in your Stellar Core configuration file. To keep this page concise, we try to avoid conceptual context and background information. You will likely find some of that related information on the [prerequisites](./prerequisites) or [environment preparation](./environment-preparation) pages, if you'd like.
 
-:::
+</Info>
 
 ### Example Configurations
 
@@ -37,18 +37,18 @@ While we're looking at some of the config basics on this page, we've written thi
 
 - If you want to connect to the Testnet network, check out the [example Testnet config]. As you can see, most of the fields from the [complete example config] are omitted since the default settings work fine. You can easily tailor this config to meet your Testnet needs.
 
-- If you want to connect to the Mainnet network, check out this [example Mainnet config] for a full validator. It includes a properly crafted quorum set with all the current [Tier 1 validators](../tier-1-orgs.mdx), which is a good place to start for most configurations. This node is set up to both [validate](#validating-node) and write history to a [public archive](./environment-preparation.mdx#configuring-to-publish-data-to-an-archive), but you can disable either feature by adjusting this config so it's a little lighter.
+- If you want to connect to the Mainnet network, check out this [example Mainnet config] for a full validator. It includes a properly crafted quorum set with all the current [Tier 1 validators](../tier-1-orgs), which is a good place to start for most configurations. This node is set up to both [validate](#validating-node) and write history to a [public archive](./environment-preparation#configuring-to-publish-data-to-an-archive), but you can disable either feature by adjusting this config so it's a little lighter.
 
-Auditing of the P2P network is enabled by default, see the [overlay topology](./monitoring.mdx#overlay-topology-survey) section for more detail if you'd like to disable it
+Auditing of the P2P network is enabled by default, see the [overlay topology](./monitoring#overlay-topology-survey) section for more detail if you'd like to disable it
 
 ### Network Passphrase
 
-Use the `NETWORK_PASSPHRASE` field to specify whether your node connects to the Testnet or the Mainnet [network](../../networks/README.mdx).
+Use the `NETWORK_PASSPHRASE` field to specify whether your node connects to the Testnet or the Mainnet [network](/docs/networks).
 
 - `NETWORK_PASSPHRASE="Test SDF Network ; September 2015"`
 - `NETWORK_PASSPHRASE="Public Global Stellar Network ; September 2015"`
 
-For more about the Network Passphrase and how it works, check out the [Networks section](../../networks/README.mdx#network-passphrases).
+For more about the Network Passphrase and how it works, check out the [Networks section](/docs/networks#network-passphrases).
 
 ### Database
 
@@ -60,11 +60,11 @@ The flat XDR files of Stellar Core are placed in a directory specified in the co
 
 ## Validating Node
 
-:::note
+<Note>
 
 If you don't intend for your node to participate in consensus votes, you can skip ahead to configuring your [quorum set](#choosing-your-quorum-set)
 
-:::
+</Note>
 
 If you want to validate, you must generate a public/private key for your node. Nodes shouldn't share keys. You should carefully _secure your private key_. If it is compromised, someone can send false messages to the network and those messages will look like they came from you.
 
@@ -94,11 +94,13 @@ HOME_DOMAIN=<your domain name here, same as NODE_HOME_DOMAIN>
 QUALITY="MEDIUM"
 ```
 
-:::note[Tier 1 quality rating]
+<Note>
 
-The example above uses `QUALITY="MEDIUM"`, which is appropriate for a new validator building a track record. If your organization is a [Tier 1 participant](../tier-1-orgs.mdx) (or aspiring to become one), you should declare your own organization as `QUALITY="HIGH"`. Note that `HIGH` quality requires [publishing a history archive](./publishing-history-archives.mdx) and at least three validators under the same home domain — both requirements are programmatically enforced. Declaring a lower quality level significantly reduces your weight in [leader election](#impact-of-validator-quality-on-nomination) and may limit your participation in consensus.
+**Tier 1 quality rating**
 
-:::
+The example above uses `QUALITY="MEDIUM"`, which is appropriate for a new validator building a track record. If your organization is a [Tier 1 participant](../tier-1-orgs) (or aspiring to become one), you should declare your own organization as `QUALITY="HIGH"`. Note that `HIGH` quality requires [publishing a history archive](./publishing-history-archives) and at least three validators under the same home domain — both requirements are programmatically enforced. Declaring a lower quality level significantly reduces your weight in [leader election](#impact-of-validator-quality-on-nomination) and may limit your participation in consensus.
+
+</Note>
 
 If you don't include a `NODE_SEED` or set `NODE_IS_VALIDATOR=true`, your node will still watch SCP and see all the data in the network, but it will not send validation messages.
 
@@ -110,11 +112,11 @@ If you want other validators to add your node to their quorum sets, you should a
 
 To create your quorum set, Stellar Core relies on two arrays of tables: `[[HOME_DOMAINS]]` and `[[VALIDATORS]]`. Check out the example config's [`HOME_DOMAINS` array] and [`VALIDATORS` array] to see them in action.
 
-:::info
+<Info>
 
 It is beneficial to take a brief detour here and explore some background information of validator quorums and network consensus. If you'd like, you can skip ahead and begin creating your [home domains array](#home-domains-array) now. Otherwise, read on, my friend!
 
-:::
+</Info>
 
 No matter what kind of node you run — Basic or Full Validator — you need to select a quorum set, which consists of validators (grouped by organization) that your node checks with to determine whether to apply a transaction set to a ledger. If you want to know more about how quorum sets work, check this article about [how Stellar approaches quorums]. If you want to see what a quorum set consisting of all the Tier 1 validators looks like — a tried and true setup — check out the [public network config for a Full Validator].
 
@@ -138,7 +140,7 @@ While this does not absolve you of all responsibility — you still need to pick
 
 When you add a validating node to your quorum set, it's generally because you trust the _organization_ running the node: you trust SDF, not some anonymous Stellar public key.
 
-In order to create a self-verified link between a node and the organization that runs it, a validator declares a home domain on-chain using a [`set_options` operation](../../learn/fundamentals/transactions/list-of-operations.mdx#set-options), and publishes organizational information in a `stellar.toml` file hosted on that domain. To find out how that works, take a look at [SEP-20].
+In order to create a self-verified link between a node and the organization that runs it, a validator declares a home domain on-chain using a [`set_options` operation](../../learn/fundamentals/transactions/list-of-operations#set-options), and publishes organizational information in a `stellar.toml` file hosted on that domain. To find out how that works, take a look at [SEP-20].
 
 As a result of that link, you can look up a node by its Stellar public key and check the `stellar.toml` file to find out who runs it. It's possible to do that manually, but you can also just consult the list of nodes on [Obsrvr Radar](https://radar.withobsrvr.com/). If you decide to trust an organization, you can use that list to collect the information necessary to add their nodes to your configuration.
 
@@ -207,11 +209,13 @@ PUBLIC_KEY="GC2V2EFSXN6SQTWVYA5EPJPBWWIMSD2XQNKUOHGEKB535AQE2I6IXV2Z"
 ADDRESS="core.rando.com"
 ```
 
-:::info[Important Note]
+<Info>
+
+**Important Note**
 
-Your quorum set is automatically configured based on the information you provide in the `[[VALIDATORS]]` and/or `[[HOME_DOMAINS]]` tables. Removing a validator will result in a new quorum set being generated and may have unintended consequence for you and other network participants. Be sure to carefully consider the implications of removing a validator from your configuration and follow the guidance to [coordinate with other validators](../tier-1-orgs.mdx#coordinate-with-other-validators) before making changes.
+Your quorum set is automatically configured based on the information you provide in the `[[VALIDATORS]]` and/or `[[HOME_DOMAINS]]` tables. Removing a validator will result in a new quorum set being generated and may have unintended consequence for you and other network participants. Be sure to carefully consider the implications of removing a validator from your configuration and follow the guidance to [coordinate with other validators](../tier-1-orgs#coordinate-with-other-validators) before making changes.
 
-:::
+</Info>
 
 ### Validator Quality
 
@@ -249,11 +253,13 @@ Both requirements are programmatically enforced. Stellar Core stops with a confi
 
 ### Automatic Quorum Set Generation
 
-:::info[Important Note]
+<Info>
+
+**Important Note**
 
 It is ideal to configure at least 4 entities in your quorum if you'll be using automatic quorum set generation. The tradeoff here is about fault tolerance: a quorum with fewer than 4 entities will tolerate **zero** node failures. Take this moment to ensure your configured quorum meets your required fault tolerance.
 
-:::
+</Info>
 
 Once you add validators to your configuration, stellar core automatically generates a quorum set using the following rules:
 
diff --git a/docs/validators/admin-guide/environment-preparation.mdx b/docs/validators/admin-guide/environment-preparation.mdx
index 367070a20..c7816283d 100644
--- a/docs/validators/admin-guide/environment-preparation.mdx
+++ b/docs/validators/admin-guide/environment-preparation.mdx
@@ -1,11 +1,11 @@
 ---
 title: Environment Preparation
-sidebar_position: 50
+description: "Initialize the Database and Local State"
 ---
 
 ## Initialize the Database and Local State
 
-After configuring your [database](./configuring.mdx#database) and [buckets](./configuring.mdx#buckets) settings, before running Stellar Core for the first time, you must initialize the database:
+After configuring your [database](./configuring#database) and [buckets](./configuring#buckets) settings, before running Stellar Core for the first time, you must initialize the database:
 
 ```bash
 stellar-core new-db
@@ -39,11 +39,11 @@ Some deployments of Stellar Core will want to retain metadata for the _entire hi
 
 This can be especially costly if it must be run more than once. For instance, when bringing a new node online. Or when needing to reingest historical data to include more meta in your stored data (as happened in [Protocol 23](https://stellar.org/blog/developers/stellar-events-retroactive-events)).
 
-:::info
+<Info>
 
 Due to the very large size requirements, we **recommend against** retaining metadata for the whole network history unless absolutely necessary for your use-case.
 
-:::
+</Info>
 
 Some operators therefore prefer to shut down their stellar-core processes and _take filesystem-level snapshots_ or _database-level dumps_ of the contents of Stellar Core's database and bucket directory, after metadata generation has occurred the first time. Such snapshots can then be restored, putting stellar-core in a state containing metadata without performing full replay.
 
@@ -51,7 +51,7 @@ Any reasonably recent state will do — if such a snapshot is a little old, stel
 
 ## History Archives
 
-Stellar Core normally interacts with one or more history archives, which are configurable facilities where [Full Validators](../README.mdx#full-validator) store flat files containing history checkpoints: bucket files and history logs. History archives are usually off-site commodity storage services such as Amazon S3, Google Cloud Storage, Azure Blob Storage, or custom SCP/SFTP/HTTP servers.
+Stellar Core normally interacts with one or more history archives, which are configurable facilities where [Full Validators](/docs/validators#full-validator) store flat files containing history checkpoints: bucket files and history logs. History archives are usually off-site commodity storage services such as Amazon S3, Google Cloud Storage, Azure Blob Storage, or custom SCP/SFTP/HTTP servers.
 
 Use command templates in the config file to give the specifics of which services you will use and how to access them. The [example config] will demonstrate how to configure a history archive through command templates.
 
@@ -59,17 +59,17 @@ Use command templates in the config file to give the specifics of which services
 
 No matter what kind of node you're running, you should configure it to `get` history from one or more public archives. You can configure any number of archives to download from: Stellar Core will automatically round-robin between them.
 
-When you're [choosing your quorum set](./configuring.mdx#choosing-your-quorum-set), you should include high-quality nodes — which, by definition, publish archives — and add the location for each node's archive in the `HISTORY` field in the [validators array](./configuring.mdx#validators-array).
+When you're [choosing your quorum set](./configuring#choosing-your-quorum-set), you should include high-quality nodes — which, by definition, publish archives — and add the location for each node's archive in the `HISTORY` field in the [validators array](./configuring#validators-array).
 
-:::note
+<Note>
 
 If you notice a lot of errors related to downloading archives, you should ensure all archives in your configuration are up-to-date. You can review the [example Mainnet configuration] to see how you might use up-to-date Tier 1 validators for their history archives.
 
-:::
+</Note>
 
 ### Configuring to Publish Data to an Archive
 
-Archive sections can also be configured with `put` and `mkdir` commands to cause the instance to publish to that archive (for nodes configured as [full validators](../README.mdx#full-validator)).
+Archive sections can also be configured with `put` and `mkdir` commands to cause the instance to publish to that archive (for nodes configured as [full validators](/docs/validators#full-validator)).
 
 The very first time you want to use your archive, _before starting your node_, you need to initialize it with:
 
@@ -77,7 +77,7 @@ The very first time you want to use your archive, _before starting your node_, y
 stellar-core new-hist <historyarchive>
 ```
 
-:::note
+<Note>
 
 In a secure, production, environment Stellar Core should be run as a dedicated user. Debian packages will ensure the `stellar` user exists on the system. For this reason you may need to run commands as the stellar user, for example:
 
@@ -85,25 +85,27 @@ In a secure, production, environment Stellar Core should be run as a dedicated u
 sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg new-hist <historyarchive>
 ```
 
-:::
+</Note>
 
-More detailed guidance and strategies for publishing history archives can be found in the [publishing history archives](./publishing-history-archives.mdx) page. Please check there for more information.
+More detailed guidance and strategies for publishing history archives can be found in the [publishing history archives](./publishing-history-archives) page. Please check there for more information.
 
-:::info[IMPORTANT:]
+<Info>
+
+**IMPORTANT:**
 
 - Make sure that you configure both `put` and `mkdir` if `put` doesn't automatically create sub-folders.
 - Writing to the same archive from different nodes is not supported and will result in undefined behavior, _potentially data loss_.
 - Do not run `new-hist` on an existing archive unless you want to erase it.
 
-:::
+</Info>
 
 ## Other Preparation
 
 In addition, you should ensure that your operating environment is also functional. This means you will have considered and prepared the following.
 
-- [Clock synchronization](./prerequisites.mdx#clock-synchronization) via an NTP service such as chrony
-- [Logging](./logging.mdx) and log rotation
-- [Monitoring](./monitoring.mdx) and alerting infrastructure
+- [Clock synchronization](./prerequisites#clock-synchronization) via an NTP service such as chrony
+- [Logging](./logging) and log rotation
+- [Monitoring](./monitoring) and alerting infrastructure
 
 [example config]: https://github.com/stellar/stellar-core/blob/master/docs/stellar-core_example.cfg
 [example Mainnet configuration]: https://github.com/stellar/packages/blob/master/docs/examples/pubnet-validator-full/stellar-core.cfg
diff --git a/docs/validators/admin-guide/index.mdx b/docs/validators/admin-guide/index.mdx
new file mode 100644
index 000000000..c1fd1bcc9
--- /dev/null
+++ b/docs/validators/admin-guide/index.mdx
@@ -0,0 +1,74 @@
+---
+title: Admin Guide
+description: "Stellar Core is the program nodes use to communicate with other nodes to create and maintain the Stellar peer-to-peer network. It's an implementation of the Stellar Consensus Protocol configured to construct a chain of ledgers guaranteed to be in agreement across all participating nodes at all times."
+---
+
+These pages describe various aspects of installing, configuring, and maintaining a `stellar-core` node.
+
+<CardGroup cols={2}>
+  <Card title="Prerequisites" icon="file-lines" href="/docs/validators/admin-guide/prerequisites">
+
+    You can install Stellar Core a number of different ways, and once you do, you can configure it to participate in the network on a several different levels:...
+
+  </Card>
+  <Card title="Installing" icon="file-lines" href="/docs/validators/admin-guide/installation">
+
+    There are three common ways to install and run Stellar Core.
+
+  </Card>
+  <Card title="Configuring" icon="file-lines" href="/docs/validators/admin-guide/configuring">
+
+    Before attempting to configure stellar-core, it is highly recommended to first try running a private network or joining the test network.
+
+  </Card>
+  <Card title="Environment Preparation" icon="file-lines" href="/docs/validators/admin-guide/environment-preparation">
+
+    After configuring your database and buckets settings, before running Stellar Core for the first time, you must initialize the database.
+
+  </Card>
+  <Card title="Publishing History Archives" icon="file-lines" href="/docs/validators/admin-guide/publishing-history-archives">
+
+    If you want to run a Full Validator, you need to set up your node to publish a history archive.
+
+  </Card>
+  <Card title="Running" icon="file-lines" href="/docs/validators/admin-guide/running-node">
+
+    Once you've set up your environment, configured your node, set up your quorum set, and selected archives to get history from, you're ready to start Stellar Core.
+
+  </Card>
+  <Card title="Logging" icon="file-lines" href="/docs/validators/admin-guide/logging">
+
+    Stellar Core sends logs to standard error and stellar-core.log by default, configurable with the LOG_FILE_PATH field.
+
+  </Card>
+  <Card title="Monitoring" icon="file-lines" href="/docs/validators/admin-guide/monitoring">
+
+    Once your node is up and running, it's important to keep an eye on it to make sure it stays afloat and continues to contribute to the health of the overall...
+
+  </Card>
+  <Card title="Maintenance" icon="file-lines" href="/docs/validators/admin-guide/maintenance">
+
+    Maintenance here refers to anything involving taking your validator temporarily out of the network (to apply security patches, system upgrade, etc).
+
+  </Card>
+  <Card title="Upgrading the Network" icon="file-lines" href="/docs/validators/admin-guide/network-upgrades">
+
+    The network itself has network wide settings that can be updated.
+
+  </Card>
+  <Card title="Soroban Settings" icon="file-lines" href="/docs/validators/admin-guide/soroban-settings">
+
+    Soroban has a large collection of settings stored on-ledger that can be modified through a validator vote.
+
+  </Card>
+  <Card title="Commands" icon="file-lines" href="/docs/validators/admin-guide/commands">
+
+    Stellar Core can be controlled using a robust CLI.
+
+  </Card>
+  <Card title="Advanced" icon="file-lines" href="/docs/validators/admin-guide/advanced">
+
+    This page contains information that is useful to know but that should not stop somebody from running a node.
+
+  </Card>
+</CardGroup>
diff --git a/docs/validators/admin-guide/installation.mdx b/docs/validators/admin-guide/installation.mdx
index 71c893996..6cd1a4366 100644
--- a/docs/validators/admin-guide/installation.mdx
+++ b/docs/validators/admin-guide/installation.mdx
@@ -1,6 +1,6 @@
 ---
 title: Installing
-sidebar_position: 30
+description: "There are three common ways to install and run Stellar Core."
 ---
 
 There are three common ways to install and run Stellar Core:
@@ -76,11 +76,11 @@ The Stellar Core source code repository contains extensive and thorough instruct
 
 SDF maintains a [quickstart image](https://github.com/stellar/quickstart) that runs a Stellar Core validator, a "Captive Core" bundled with Stellar RPC, and all other necessary components to support local development. It's a quick way to set up a default, non-validating, ephemeral configuration that should work for most developers. Additionally, the quickstart image can be spun up pre-configured for use as a Mainnet, Testnet, Futurenet, or Local network node.
 
-:::info
+<Info>
 
 The quickstart image is not intended to serve as a production-level instance node. Please plan your production instance(s) carefully.
 
-:::
+</Info>
 
 ### Production Environments
 
@@ -112,13 +112,13 @@ docker run --entrypoint=/bin/sha256sum stellar/stellar-core:latest /usr/bin/stel
 
 Stellar Core is also packaged by some third-party package managers.
 
-:::caution
+<Warning>
 
 Third-party packages are not supported or verified by the Stellar Development Foundation. They are built and maintained by their respective communities, and may lag behind the latest [release](https://github.com/stellar/stellar-core/releases). For production use, we recommend the [SDF-published packages](#package-based-installation) or [Docker images](#docker-based-installation).
 
-Tier 1 validators should use the [packages](#package-based-installation), as they receive security patches. See [Tier 1 Organizations](../tier-1-orgs.mdx).
+Tier 1 validators should use the [packages](#package-based-installation), as they receive security patches. See [Tier 1 Organizations](/docs/validators/tier-1-orgs).
 
-:::
+</Warning>
 
 ### Homebrew (macOS and Linux)
 
diff --git a/docs/validators/admin-guide/logging.mdx b/docs/validators/admin-guide/logging.mdx
index 8d30dc68d..c6df2c7e3 100644
--- a/docs/validators/admin-guide/logging.mdx
+++ b/docs/validators/admin-guide/logging.mdx
@@ -1,6 +1,6 @@
 ---
 title: Logging
-sidebar_position: 70
+description: "Stellar Core sends logs to standard error and stellar-core.log by default, configurable with the LOG_FILE_PATH field."
 ---
 
 Stellar Core sends logs to standard error and `stellar-core.log` by default, configurable with the `LOG_FILE_PATH` field.
@@ -25,11 +25,11 @@ sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg http-command "
 
 Against a running system.
 
-:::info
+<Info>
 
 Please take a look at the [HTTP Commands reference] for more information about the partitions available for use in the `ll` command.
 
-:::
+</Info>
 
 The default log level is `INFO`, which is moderately verbose and should emit progress messages every few seconds under normal operation.
 
diff --git a/docs/validators/admin-guide/maintenance.mdx b/docs/validators/admin-guide/maintenance.mdx
index fdb782a78..db82648bb 100644
--- a/docs/validators/admin-guide/maintenance.mdx
+++ b/docs/validators/admin-guide/maintenance.mdx
@@ -1,6 +1,6 @@
 ---
 title: Maintenance
-sidebar_position: 90
+description: "Maintenance here refers to anything involving taking your validator temporarily out of the network (to apply security patches, system upgrade, etc)."
 ---
 
 Maintenance here refers to anything involving taking your validator temporarily out of the network (to apply security patches, system upgrade, etc).
@@ -9,7 +9,7 @@ As an administrator of a validator, you must ensure that the maintenance you are
 
 Safe means that the other validators that depend on yours will not be affected too much when you turn off your validator for maintenance and that your validator will continue to operate as part of the network when it comes back up.
 
-If you are changing some settings that may impact network wide settings such as protocol version, review [the network upgrades page](./network-upgrades.mdx).
+If you are changing some settings that may impact network wide settings such as protocol version, review [the network upgrades page](./network-upgrades).
 
 If you're changing your quorum set configuration, also read the [section on what to do](#special-considerations-during-quorum-set-updates).
 
diff --git a/docs/validators/admin-guide/monitoring.mdx b/docs/validators/admin-guide/monitoring.mdx
index 086b68155..34ae21d7e 100644
--- a/docs/validators/admin-guide/monitoring.mdx
+++ b/docs/validators/admin-guide/monitoring.mdx
@@ -1,17 +1,17 @@
 ---
 title: Monitoring
-sidebar_position: 80
+description: "Once your node is up and running, it's important to keep an eye on it to make sure it stays afloat and continues to contribute to the health of the overall..."
 ---
 
 Once your node is up and running, it's important to keep an eye on it to make sure it stays afloat and continues to contribute to the health of the overall network. To help with that, Stellar Core exposes vital information that you can use to monitor your node and diagnose potential problems.
 
 You can access this information using commands and inspecting Stellar Core's output. The first half of this page will cover this approach. You can also connect [Prometheus](#using-prometheus) to make monitoring easier, combine it with [Alertmanager](#configure-notifications-using-alertmanager) to automate notification, and use pre-built [Grafana dashboards](#visualize-metrics-using-grafana) to create visual representations of your node's well-being.
 
-:::info
+<Info>
 
 [**Obsrvr Radar**](https://radar.withobsrvr.com/), a community-run monitoring dashboard, can also be useful for viewing network health as a whole. You should keep a very close eye on your own node(s) using some of the tools suggested on this page, but monitoring performance of all the network's nodes can also be useful to understand how they all interact with each other.
 
-:::
+</Info>
 
 However you decide to monitor, the most important thing is that you have a system in place to ensure that your integration keeps ticking.
 
@@ -73,7 +73,7 @@ Some notable fields from this `info` endpoint are:
   - `age`: time elapsed since this ledger closed (during normal operation less than 10 seconds)
   - `num`: ledger number
   - `version`: protocol version of this ledger
-- `network` the [network passphrase]([Networks section](../../networks/README.mdx#network-passphrases)) for the network this core instance is using
+- `network` the [network passphrase]([Networks section](/docs/networks#network-passphrases)) for the network this core instance is using
 - `peers`: information on the connectivity to the network
   - `authenticated_count`: the number of live connections
   - `pending_count`: the number of connections that are not fully established yet
@@ -431,8 +431,8 @@ In the example above, 6 nodes are functioning properly, one is down (`stronghold
 If a node is stuck in state `Joining SCP`, this command allows to quickly find the reason:
 
 - too many validators missing (down or without a good connectivity), solutions are:
-  - [adjust your quorum set](./configuring.mdx#choosing-your-quorum-set) (thresholds, grouping, etc.) based on the nodes that are not missing
-  - try to get a [better connectivity path](./configuring.mdx#quorum-and-overlay-network) to the missing validators
+  - [adjust your quorum set](./configuring#choosing-your-quorum-set) (thresholds, grouping, etc.) based on the nodes that are not missing
+  - try to get a [better connectivity path](./configuring#quorum-and-overlay-network) to the missing validators
 - network split would cause SCP to stick because of nodes that disagree. This would happen if either there is a bug in SCP, the network does not have quorum intersection, or the disagreeing nodes are misbehaving (compromised, etc.).
 
 Note that the node not being able to reach consensus does not mean that the network as a whole will be unable to reach consensus (and the opposite is true, the network may fail because of a different set of validators failing).
diff --git a/docs/validators/admin-guide/network-upgrades.mdx b/docs/validators/admin-guide/network-upgrades.mdx
index 349938cf9..4eadd6bba 100644
--- a/docs/validators/admin-guide/network-upgrades.mdx
+++ b/docs/validators/admin-guide/network-upgrades.mdx
@@ -1,13 +1,13 @@
 ---
 title: Upgrading the Network
-sidebar_position: 100
+description: "The network itself has network wide settings that can be updated."
 ---
 
 The network itself has network wide settings that can be updated.
 
 This is performed by validators voting for and agreeing to new values the same way that consensus is reached for transaction sets, etc.
 
-A node can be configured to vote for upgrades using the `upgrades` endpoint . See [Commands](./commands.mdx) for more information.
+A node can be configured to vote for upgrades using the `upgrades` endpoint . See [Commands](./commands) for more information.
 
 The network settings are:
 
@@ -44,7 +44,7 @@ The mechanism to update Soroban settings is more complex than updating something
 
 This means that someone wishing to propose a setting upgrade will need to create a smart contract that writes the `ConfigUpgradeSet` bytes into `ContractData` (remember, a `Temporary` entry is required), invoke it to write the upgrade xdr, and then share the serialized `ConfigUpgradeSetKey` to vote on.
 
-We have much more detail on the [next page](./soroban-settings.mdx) about _how_ to craft an upgrade proposal for these settings. Be sure to read and understand that.
+We have much more detail on the [next page](./soroban-settings) about _how_ to craft an upgrade proposal for these settings. Be sure to read and understand that.
 
 ## Example Upgrade Command
 
diff --git a/docs/validators/admin-guide/prerequisites.mdx b/docs/validators/admin-guide/prerequisites.mdx
index ce4dcb228..fe8fc70b7 100644
--- a/docs/validators/admin-guide/prerequisites.mdx
+++ b/docs/validators/admin-guide/prerequisites.mdx
@@ -1,23 +1,24 @@
 ---
 title: Prerequisites
-sidebar_position: 20
+description: "You can install Stellar Core a number of different ways, and once you do, you can configure it to participate in the network on a several different levels: it can be either a Basic Validator or a Full Validator. No matter how you install Stellar Core or what kind of node you run, however, you need to set up and connect to the peer-to-peer network and store the state of the ledger in a SQL database."
 ---
 
-You can install Stellar Core a [number of different ways](./installation.mdx), and once you do, you can [configure](./configuring.mdx) it to participate in the network on a several [different levels](../README.mdx#types-of-nodes): it can be either a Basic Validator or a Full Validator. No matter how you install Stellar Core or what kind of node you run, however, you need to set up and connect to the peer-to-peer network and store the state of the ledger in a SQL [database](./configuring.mdx#database).
+You can install Stellar Core a [number of different ways](./installation), and once you do, you can [configure](./configuring) it to participate in the network on a several [different levels](/docs/validators#types-of-nodes): it can be either a Basic Validator or a Full Validator. No matter how you install Stellar Core or what kind of node you run, however, you need to set up and connect to the peer-to-peer network and store the state of the ledger in a SQL [database](./configuring#database).
 
 ## Hardware Requirements
 
-:::info
+<Info>
 
 CPU, RAM, Disk and network depends on network activity. If you decide to collocate certain workloads, you will need to take this into account.
 
-:::
+</Info>
+<Tip>
 
-:::tip[For Tier 1 organizations]
+**For Tier 1 organizations**
 
-[Tier 1 organizations](../tier-1-orgs.mdx) run three geographically dispersed Full Validators, each meeting these requirements independently. Each node needs its own hardware, its own unique validator key, and its own history archive. Plan for three times the resources listed below, spread across different data centers or cloud regions. See [Tier 1 Organizations](../tier-1-orgs.mdx) for the full requirements and onboarding path.
+[Tier 1 organizations](../tier-1-orgs) run three geographically dispersed Full Validators, each meeting these requirements independently. Each node needs its own hardware, its own unique validator key, and its own history archive. Plan for three times the resources listed below, spread across different data centers or cloud regions. See [Tier 1 Organizations](../tier-1-orgs) for the full requirements and onboarding path.
 
-:::
+</Tip>
 
 Stellar Core is designed to run on relatively modest hardware so that a whole range of individuals and organizations can participate in the network, and basic nodes should be able to function pretty well without tremendous overhead. That said, the more you ask of your node, the greater the requirements.
 
@@ -49,21 +50,23 @@ A Stellar Core node needs to connect to other nodes on the internet via their `P
 
 Stellar Core also needs to connect to certain internal systems, though exactly how this is accomplished can vary based on your setup.
 
-### Inbound
+### Inbound {#inbound-1}
 
 - Stellar Core exposes an _unauthenticated_ HTTP endpoint on its `HTTP_PORT`. You can specify a port when you [configure] Stellar Core, but most people use the default, which is **11626**.
 - The `HTTP_PORT` is used by other systems (such as Stellar RPC) to submit transactions, so this port may have to be exposed to the rest of your internal IP addresses.
-- It's also used to query Stellar Core [info](./commands.mdx) and provide [metrics](./monitoring.mdx).
-- And to perform administrative commands such as [scheduling upgrades](./network-upgrades.mdx) and changing log levels
-- For more on that, see [commands](./commands.mdx)
+- It's also used to query Stellar Core [info](./commands) and provide [metrics](./monitoring).
+- And to perform administrative commands such as [scheduling upgrades](./network-upgrades) and changing log levels
+- For more on that, see [commands](./commands)
+
+<Note>
 
-:::note[Note on exposing the HTTP endpoint]
+**Note on exposing the HTTP endpoint**
 
 If you need to expose this endpoint to other hosts in your local network, we strongly recommended you use an intermediate reverse proxy server to implement authentication. Don't expose the HTTP endpoint to the raw and cruel open internet.
 
-:::
+</Note>
 
-### Outbound
+### Outbound {#outbound-1}
 
 - Stellar Core requires access to a database (PostgreSQL, for example). If that database resides on a different machine on your network, you'll need to allow that connection. You'll specify the database when you [configure] Stellar Core.
 - Your node needs outbound NTP (UDP port 123) so that its clock stays synchronized and Stellar Core can check for clock drift — see [Clock Synchronization](#clock-synchronization) below.
@@ -71,7 +74,7 @@ If you need to expose this endpoint to other hosts in your local network, we str
 
 ## Clock Synchronization
 
-Stellar Core depends on an accurate system clock: ledgers close on network time, scheduled [network upgrades](./network-upgrades.mdx) are armed relative to it, and consensus includes an optimization that requires validators' clocks across the network to be closely synchronized. Every validator must run an NTP synchronization service.
+Stellar Core depends on an accurate system clock: ledgers close on network time, scheduled [network upgrades](./network-upgrades) are armed relative to it, and consensus includes an optimization that requires validators' clocks across the network to be closely synchronized. Every validator must run an NTP synchronization service.
 
 The node logs a warning when it detects clock drift:
 
@@ -147,11 +150,11 @@ A common misconception is that validators need to provision storage proportional
 
 **Soroban (smart contract) state is bounded by [state archival](https://developers.stellar.org/docs/learn/encyclopedia/storage/state-archival).** Contract data and contract code entries carry a rent balance; when a Temporary entry's balance reaches zero, it is deleted from live state. Temporary entries are cheaper to create than Persistent entries and dominate total contract data volume, so as they expire and are removed, a significant amount of state is freed up — keeping the live state on disk from growing unboundedly.
 
-**Classic ledger entries — accounts, trustlines, offers, claimable balances, liquidity pool shares, and data entries — do not expire.** They persist on the live state indefinitely. They grow slowly, though, because [reserve requirements](../../learn/fundamentals/stellar-data-structures/accounts.mdx#base-reserves-and-subentries) act as anti-spam friction on creation. In practice, the resulting working set still lands in the 30–60 GB range cited above, so local validator state stays compact even as cumulative network history grows.
+**Classic ledger entries — accounts, trustlines, offers, claimable balances, liquidity pool shares, and data entries — do not expire.** They persist on the live state indefinitely. They grow slowly, though, because [reserve requirements](../../learn/fundamentals/stellar-data-structures/accounts#base-reserves-and-subentries) act as anti-spam friction on creation. In practice, the resulting working set still lands in the 30–60 GB range cited above, so local validator state stays compact even as cumulative network history grows.
 
-**History archives live on object storage, not on the validator.** Full validators publish history archives to a separate object store (S3, R2, Backblaze B2, etc.) — that's where the multi-TB archive data lives. The validator process itself doesn't hold the archive on its local disk. See [Publishing History Archives](./publishing-history-archives.mdx) for the recommended setup.
+**History archives live on object storage, not on the validator.** Full validators publish history archives to a separate object store (S3, R2, Backblaze B2, etc.) — that's where the multi-TB archive data lives. The validator process itself doesn't hold the archive on its local disk. See [Publishing History Archives](./publishing-history-archives) for the recommended setup.
 
-**`CATCHUP_COMPLETE=true` is almost never the right choice.** This setting makes the node sync the entire ledger from genesis on startup and is rarely appropriate for a validator. The standard pattern for new validators — including new Tier 1 candidates — is to sync against current network state, publish a history archive forward from that point, and use [`stellar-archivist mirror`](./publishing-history-archives.mdx#mirroring-an-archive) to backfill historical data into the published archive as a separate operation. The validator's local disk requirements are determined by the live state model above, not by historical depth.
+**`CATCHUP_COMPLETE=true` is almost never the right choice.** This setting makes the node sync the entire ledger from genesis on startup and is rarely appropriate for a validator. The standard pattern for new validators — including new Tier 1 candidates — is to sync against current network state, publish a history archive forward from that point, and use [`stellar-archivist mirror`](./publishing-history-archives#mirroring-an-archive) to backfill historical data into the published archive as a separate operation. The validator's local disk requirements are determined by the live state model above, not by historical depth.
 
 ### Database
 
@@ -211,6 +214,6 @@ If you choose to use Kubernetes regardless, consider the following:
 - Ensure that sufficient resources are always available to the pods
 - Depending on how history archives are published, you may need to fork docker images to include extra tooling
 
-[configure]: ./configuring.mdx
+[configure]: ./configuring
 [c5d.2xlarge]: https://aws.amazon.com/ec2/instance-types/c5/
 [n4-highcpu-8]: https://cloud.google.com/compute/docs/general-purpose-machines#n4-highcpu
diff --git a/docs/validators/admin-guide/publishing-history-archives.mdx b/docs/validators/admin-guide/publishing-history-archives.mdx
index b4bdb9726..fb36b0b79 100644
--- a/docs/validators/admin-guide/publishing-history-archives.mdx
+++ b/docs/validators/admin-guide/publishing-history-archives.mdx
@@ -1,20 +1,22 @@
 ---
 title: Publishing History Archives
-sidebar_position: 50
+description: "If you want to run a Full Validator, you need to set up your node to publish a history archive covering the network's complete history. You can host an archive using a blob store such as Amazon's S3 or Digital Ocean's spaces, or you can simply serve a local archive directly via an HTTP server such as Nginx or Apache. If you're setting up a Basic Validator, you can skip this section. No matter what kind of node you're planning to run, make sure to set it up to get history, which is covered in Environment Preparation."
 ---
 
-If you want to run a [Full Validator](../README.mdx#full-validator), you need to set up your node to publish a history archive covering the network's complete history. You can host an archive using a blob store such as Amazon's S3 or Digital Ocean's spaces, or you can simply serve a local archive directly via an HTTP server such as Nginx or Apache. If you're setting up a [Basic Validator](../README.mdx#basic-validator), you can skip this section. No matter what kind of node you're planning to run, make sure to set it up to `get` history, which is covered in [Environment Preparation](./environment-preparation.mdx).
+If you want to run a [Full Validator](/docs/validators#full-validator), you need to set up your node to publish a history archive covering the network's complete history. You can host an archive using a blob store such as Amazon's S3 or Digital Ocean's spaces, or you can simply serve a local archive directly via an HTTP server such as Nginx or Apache. If you're setting up a [Basic Validator](/docs/validators#basic-validator), you can skip this section. No matter what kind of node you're planning to run, make sure to set it up to `get` history, which is covered in [Environment Preparation](./environment-preparation).
 
 Getting to a complete archive takes two stages:
 
 - Configuring your node to publish, described in the sections below. This fills the archive forward from the moment your node starts.
 - [Completing the archive](#complete-history-archive), which backfills everything from before that point.
 
-:::caution[One archive per node]
+<Warning>
 
-Each node must publish to its own dedicated archive. Writing to the same archive from multiple nodes is not supported and will result in undefined behavior, potentially including data loss. If you're running multiple Full Validators (as [Tier 1 organizations](../tier-1-orgs.mdx) do), configure a separate archive for each — for example, `history-a.example.com`, `history-b.example.com`, and `history-c.example.com`.
+**One archive per node**
 
-:::
+Each node must publish to its own dedicated archive. Writing to the same archive from multiple nodes is not supported and will result in undefined behavior, potentially including data loss. If you're running multiple Full Validators (as [Tier 1 organizations](../tier-1-orgs) do), configure a separate archive for each — for example, `history-a.example.com`, `history-b.example.com`, and `history-c.example.com`.
+
+</Warning>
 
 ## Caching and History Archives
 
@@ -202,7 +204,7 @@ At this stage your validator is publishing each new checkpoint as the network ad
 
 ## Complete History Archive
 
-This is the second stage. A [Full Validator](../README.mdx#full-validator) publishes an archive reaching back to the network's first ledger. The [stellar-archivist](https://github.com/stellar/rs-stellar-archivist) command line tool gives you what you need to close the gap.
+This is the second stage. A [Full Validator](/docs/validators#full-validator) publishes an archive reaching back to the network's first ledger. The [stellar-archivist](https://github.com/stellar/rs-stellar-archivist) command line tool gives you what you need to close the gap.
 
 ### Installing stellar-archivist
 
@@ -220,13 +222,13 @@ For detailed usage, please run `stellar-archivist-rs --help` (or `stellar-archiv
 
 stellar-archivist is a standalone tool. It does not link against or communicate with `stellar-core`; all it needs is read and write access to the archive itself. That access can be a local filesystem path (`file://`), an HTTP(S) source, or a cloud object store (`s3://`, `gcs://`, `azblob://`, `b2://`), so you can run it from any machine that can reach your archive.
 
-:::caution
+<Warning>
 
 Run stellar-archivist on a separate host from your validator to avoid resource contention.
 
 Do **not** stop your validator to work on its archive. stellar-archivist operates on the archive files directly and does not interfere with live publishing. Your node should stay online and keep publishing checkpoints throughout.
 
-:::
+</Warning>
 
 ### Choosing a command
 
@@ -238,7 +240,7 @@ Do **not** stop your validator to work on its archive. stellar-archivist operate
 
 All three accept `--low` and `--high` to restrict the work to a ledger range; both bounds are rounded outward to the nearest checkpoint.
 
-### Checking file contents with `--verify`
+### Checking file contents with `--verify` {#checking-file-contents-with---verify}
 
 By default, every command checks only that files exist. Adding `--verify` also checks that their contents are sound, which requires significantly more CPU and memory.
 
@@ -330,7 +332,7 @@ stellar-archivist-rs repair \
 
 Repair runs in stages and reports each one separately: a main pass that audits the destination, a file retry that re-fetches everything recorded as broken, and a checkpoint retry for cross-file and chain failures.
 
-:::tip
+<Tip>
 
 The JSON report written by `scan` can be handed straight back to `repair` as a plan, using `--plan`. Repair then re-fetches exactly those files.
 
@@ -341,7 +343,7 @@ stellar-archivist-rs repair \
   --plan report.json
 ```
 
-:::
+</Tip>
 
 A final scan confirms the archive has been repaired:
 
@@ -356,11 +358,11 @@ stellar-archivist-rs scan file:///mnt/xvdf/stellar-core-archive/node_001
 2026-08-21T22:05:57.686747Z  INFO Scan complete: 395 files found, 0 missing or corrupt
 ```
 
-:::tip
+<Tip>
 
 Add `--dry-run` to report what would be repaired without writing anything. Combined with `--report`, this writes a plan you can review and apply later.
 
-:::
+</Tip>
 
 ### Mirroring an archive
 
@@ -387,7 +389,7 @@ stellar-archivist-rs mirror \
 
 Afterwards, the destination contains a new archive covering history up to checkpoint 1023.
 
-:::tip
+<Tip>
 
 Mirroring is resumable. Running it again against the same destination with a higher `--high` picks up from the destination's current checkpoint and copies only what is missing.
 
@@ -402,7 +404,7 @@ stellar-archivist-rs mirror \
   --low 63 --high 895 --overwrite
 ```
 
-:::
+</Tip>
 
 You should now have a complete history archive being written by your full validator. Congratulations!
 
diff --git a/docs/validators/admin-guide/running-node.mdx b/docs/validators/admin-guide/running-node.mdx
index 6467268dd..deb4ef5c3 100644
--- a/docs/validators/admin-guide/running-node.mdx
+++ b/docs/validators/admin-guide/running-node.mdx
@@ -1,11 +1,11 @@
 ---
 title: Running
-sidebar_position: 60
+description: "Starting Your Node"
 ---
 
 ## Starting Your Node
 
-Once you've [set up your environment](./prerequisites.mdx), [configured your node](./configuring.mdx), set up your [quorum set](./configuring.mdx#choosing-your-quorum-set), and selected archives to `get` [history from](./environment-preparation.mdx#history-archives), you're ready to start Stellar Core.
+Once you've [set up your environment](./prerequisites), [configured your node](./configuring), set up your [quorum set](./configuring#choosing-your-quorum-set), and selected archives to `get` [history from](./environment-preparation#history-archives), you're ready to start Stellar Core.
 
 Use a command equivalent to:
 
@@ -15,7 +15,7 @@ sudo systemctl start stellar-core
 
 At this point, you're ready to observe your core node's activity as it joins the network.
 
-You may want to skip ahead and review the [Logging](./logging.mdx) page to familiarize yourself with Stellar Core's output.
+You may want to skip ahead and review the [Logging](./logging) page to familiarize yourself with Stellar Core's output.
 
 ## Interacting With Your Instance
 
@@ -25,13 +25,13 @@ When your node is running, you can interact with Stellar Core via an administrat
 sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg http-command <http-command>
 ```
 
-The HTTP endpoint is [not intended to be exposed to the public internet](./prerequisites.mdx#internal-system-access). It's typically accessed by administrators, or by a mid-tier application to submit transactions to the Stellar network.
+The HTTP endpoint is [not intended to be exposed to the public internet](./prerequisites#internal-system-access). It's typically accessed by administrators, or by a mid-tier application to submit transactions to the Stellar network.
 
-Details of available _HTTP_ endpoint commands can be found in the [stellar-core-GitHub repo](https://github.com/stellar/stellar-core/blob/master/docs/software/commands.md#http-commands). Additionally, [the commands page](./commands.mdx) contains an overview of some of the most useful _CLI_ commands (non-HTTP commands) for managing a running core node.
+Details of available _HTTP_ endpoint commands can be found in the [stellar-core-GitHub repo](https://github.com/stellar/stellar-core/blob/master/docs/software/commands.md#http-commands). Additionally, [the commands page](./commands) contains an overview of some of the most useful _CLI_ commands (non-HTTP commands) for managing a running core node.
 
 ## Joining the Network
 
-Your node will go through the following phases as it joins the network, and you can query for the output below by using the info endpoint mentioned [here](./monitoring.mdx#general-node-information) :
+Your node will go through the following phases as it joins the network, and you can query for the output below by using the info endpoint mentioned [here](./monitoring#general-node-information) :
 
 ### Establish Connection to Other Peers.
 
@@ -95,13 +95,13 @@ And will then move through the various phases of downloading and applying state,
 
 For the fastest sync — including for new Full Validators and Tier 1 candidates — leave `CATCHUP_RECENT` at its default and do **not** set `CATCHUP_COMPLETE=true`. Your node will sync against current network state in minutes to hours rather than weeks.
 
-`CATCHUP_COMPLETE=true` makes the node replay the _entire history_ of the network on startup, which takes weeks and is almost never the right choice for a validator — see [Why local disk stays bounded](./prerequisites.mdx#why-local-disk-stays-bounded). The standard pattern for new validators that want to publish a complete history archive is to sync against current state first, publish forward from that point, and use the [`stellar-archivist mirror`](./publishing-history-archives.mdx#mirroring-an-archive) tool to backfill historical data into the published archive as a separate offline operation. See the [complete example configuration] for more details.
+`CATCHUP_COMPLETE=true` makes the node replay the _entire history_ of the network on startup, which takes weeks and is almost never the right choice for a validator — see [Why local disk stays bounded](./prerequisites#why-local-disk-stays-bounded). The standard pattern for new validators that want to publish a complete history archive is to sync against current state first, publish forward from that point, and use the [`stellar-archivist mirror`](./publishing-history-archives#mirroring-an-archive) tool to backfill historical data into the published archive as a separate offline operation. See the [complete example configuration] for more details.
 
-:::info
+<Info>
 
 The `CATCHUP_COMPLETE` and `CATCHUP_RECENT` config fields are mutually exclusive. If the `CATCHUP_COMPLETE` field is set to `true`, the `CATCHUP_RECENT` field will be ignored.
 
-:::
+</Info>
 
 ### Synced
 
diff --git a/docs/validators/admin-guide/soroban-settings.mdx b/docs/validators/admin-guide/soroban-settings.mdx
index 7664939a0..711b999ed 100644
--- a/docs/validators/admin-guide/soroban-settings.mdx
+++ b/docs/validators/admin-guide/soroban-settings.mdx
@@ -1,19 +1,19 @@
 ---
 title: Soroban Settings
-sidebar_position: 110
+description: "Soroban has a large collection of settings stored on-ledger that can be modified through a validator vote."
 ---
 
-Soroban has a large collection of settings stored on-ledger that can be modified through a validator vote. Here you can find out how to propose a new settings upgrade as well as how to examine a proposed upgrade. You can also look at the [Commands page](./commands.mdx) for more details on the stellar-core commands used below.
+Soroban has a large collection of settings stored on-ledger that can be modified through a validator vote. Here you can find out how to propose a new settings upgrade as well as how to examine a proposed upgrade. You can also look at the [Commands page](./commands) for more details on the stellar-core commands used below.
 
 ## Propose a Settings Upgrade
 
-This section will describe how to propose a settings upgrade, but take a look at the [Upgrading the Network page](./network-upgrades.mdx#upgrading-soroban-settings) for more information on how the settings upgrade mechanism works internally.
+This section will describe how to propose a settings upgrade, but take a look at the [Upgrading the Network page](./network-upgrades#upgrading-soroban-settings) for more information on how the settings upgrade mechanism works internally.
 
-:::info
+<Info>
 
 If you are being asked to vote for an upgrade, please move on to the [Examine a Proposed Upgrade](#examine-a-proposed-upgrade) section for details on how to accomplish that.
 
-:::
+</Info>
 
 ### Frozen ledger keys
 
@@ -58,7 +58,7 @@ The output of the phase 2 JSON file, for example, would look like:
 AAAAAgAAAAEAAAAAHc1lAAAAAAAF9eEAAAAAAAAAABkCgAAAAAAAAgAAAMgAB6EgAAAAfQABEXAAAAAoAAIIAAAAABkAAQQAAAAAAAAAGGoAAAAAAAAnEAAAAAAAAAb6AAAAAukO3QD///////0NfwAAAAAAAOFfAAAD6A==
 ```
 
-:::info
+<Info>
 
 `stellar` CLI can be installed using brew or cargo:
 
@@ -70,7 +70,7 @@ cargo install --locked stellar-cli
 
 You can also download a [precompiled binary] of the latest release for your system from GitHub.
 
-:::
+</Info>
 
 ### 2. Generate Settings Upgrade Transactions
 
@@ -127,11 +127,11 @@ nfyIVkHBNlHcyKH+8oKgrgJmA/MnLCW3E4Fhg4XYTkqZa2MyqzRdB2+mN3DOKUFKtZIAXp6o3DHrkgR0
 
 These four transactions can then be submitted to the network through your node. Replace the blob placeholders below with the `TransactionEnvelope`s in lines 1, 3, 5, and 7.
 
-:::note
+<Note>
 
 If you didn't provide the `--signtxs` parameter to the `get-settings-upgrade-txs` command, don't forget to sign them before submitting to the network.
 
-:::
+</Note>
 
 ```bash
 http-command 'tx?blob=<LINE_1_OUTPUT>'
diff --git a/docs/validators/index.mdx b/docs/validators/index.mdx
new file mode 100644
index 000000000..5bc50834e
--- /dev/null
+++ b/docs/validators/index.mdx
@@ -0,0 +1,75 @@
+---
+title: Validators Introduction
+"og:title": "Validators: Role, Setup, and Importance in Network Security & Consensus"
+description: "Learn how validators support network security and consensus. Understand their role, setup requirements, and how they help maintain the integrity of the Stellar network."
+---
+
+Stellar is a peer-to-peer network made up of nodes, which are computers that keep a common distributed [ledger](/docs/learn/fundamentals/stellar-data-structures/ledgers), and that communicate to validate and add [transactions](/docs/learn/fundamentals/transactions/operations-and-transactions) to it. Nodes use a program called Stellar Core — an implementation of the [Stellar Consensus Protocol](/docs/learn/fundamentals/stellar-consensus-protocol) — to stay in sync as they work to agree on the validity of transaction sets and to apply them to the ledger. Generally, nodes reach consensus, apply a transaction set, and update the ledger every 5-7 seconds.
+
+This section of the docs explains how to run a validator node, which participates in consensus to validate transactions and determine network settings. A validator node _should not_ be used for network data access and transaction submission. There are two varieties of _non-validating_ nodes that can be used for those purposes, each of which has its own process for set up, interaction, maintenance, and monitoring. They are:
+
+1. [**Stellar RPC Nodes**](/docs/data/apis/rpc) can be used for simulating and/or submitting transactions, as well as exposing an RPC service to query and retrieve current network state. This is the best choice for real-time use-cases.
+2. [**Galexie Nodes**](/docs/data/indexers/build-your-own/galexie) can be used for retrieving and storing network data en masse for further processing. Notably, it does _not_ support transaction submission so is more suitable for indexers or analytics use-cases.
+
+If you are interested in running a validator node — because you issue an asset that you would like to help secure through transaction validation, because you want to help increase network health and decentralization, or because you want to participate in network governance — then this section of the docs is for you. It explains the technical and operational aspects of installing, configuring, and maintaining a Stellar Core validator node, and should help you figure out the best way to set up your Stellar integration.
+
+<Tip>
+
+**Interested in Tier 1?**
+
+If your organization is evaluating or planning to join the Tier 1 quorum — the core group of organizations whose validators bear the safety and liveness of the network — see [Tier 1 Organizations](/docs/validators/tier-1-orgs) for requirements, estimated costs, and a step-by-step onboarding path. The Admin Guide below covers the technical setup for a single validator; the Tier 1 page covers what it takes to run three and join the quorum.
+
+</Tip>
+
+## Node Setup Process
+
+The basic flow, which you can navigate through using the "Admin Guide" on the left, goes (roughly) like this:
+
+### Initial Setup
+
+1. Use the information on this _Introduction_ page to determine which [type of node](#types-of-nodes) you want to run.
+2. [Prerequisite](/docs/validators/admin-guide/prerequisites) software must be installed (and configured according to your needs).
+3. [Install](/docs/validators/admin-guide/installation) the Stellar Core software on your instance.
+4. [Configure](/docs/validators/admin-guide/configuring) the Stellar Core software to suit your needs and environment.
+5. [Prepare](/docs/validators/admin-guide/environment-preparation) your node instance and environment. This includes the optional step of setting your node up to [publish history archives](/docs/validators/admin-guide/publishing-history-archives) of the ledger.
+6. [Start your node](/docs/validators/admin-guide/running-node) and join the network.
+7. [Logging](/docs/validators/admin-guide/logging) and [monitoring](/docs/validators/admin-guide/monitoring) should be appropriately set up and used to meet your needs.
+
+### Ongoing Requirements
+
+8. [Maintenance](/docs/validators/admin-guide/maintenance) is required from time to time to keep your node up-to-date and participating in the network.
+9. [Network upgrades](/docs/validators/admin-guide/network-upgrades) require validator consensus, and you will need to consider casting a vote in the event of a protocol upgrade.
+10. [Soroban settings](/docs/validators/admin-guide/soroban-settings) are network-wide, configurable, and changes can be proposed by anyone. Similar to protocol upgrades, changes to these settings will require validator consensus, so you should be prepared to participate.
+
+### Other Information
+
+- Stellar Core uses a robust [command line](/docs/validators/admin-guide/commands) tool to control and operate a node. We've gathered information on some of the most-used commands, and linked to further, more comprehensive CLI documentation.
+- We've collected some miscellaneous helpful and [advanced](/docs/validators/admin-guide/advanced) information that could be useful as you understand and implement your core node.
+
+## Types of validator nodes {#types-of-nodes}
+
+There are two types of validator nodes, and they perform the same basic functions: they run Stellar Core, connect to peers, submit transactions, and store the state of the ledger. The difference is this: a **Basic Validator** does not publish a history archive; a **Full Validator** publishes one covering the network's complete history.
+
+<Info>
+
+Non-validating nodes, like Stellar RPC or Galexie, bundle an optimized "Captive" Core to serve their operational needs.
+
+</Info>
+
+### Basic Validator
+
+#### Validating, no public archive
+
+A Basic Validator keeps track of the ledger and submits transactions for possible inclusion, but it is _not_ configured to publish history archives. It does require a secret key, and is [configured to participate in consensus](/docs/validators/admin-guide/configuring#validating-node) by voting on — and signing off on — changes to the ledger, meaning it supports the network and increases decentralization.
+
+The advantage: signatures can serve as official endorsements of specific ledgers in real time. That’s important if, for instance, you issue an asset on Stellar that represents a real-world asset: you can let your customers know that you will only honor transactions and redeem assets from ledgers signed by your validator, and in the unlikely scenario that something happens to the network, you can use your node as the final arbiter of truth. Setting up your node as a validator allows you to resolve any questions _up front and in writing_ about how you plan to deal with disasters and disputes.
+
+### Full Validator
+
+#### Validating, offers a complete public archive
+
+A Full Validator is the same as a Basic Validator except that it also publishes a [History Archive](/docs/validators/admin-guide/environment-preparation) covering the network's **complete history** — snapshots of the ledger, including all transactions and their results. A Full Validator writes to an internet-facing blob store — such as AWS or Azure — so it's a bit more expensive and complex to run, but it also does the most to support the network’s resilience and decentralization.
+
+When other nodes join the network — or experience difficulty and temporarily fall out of sync — they can consult archives offered by Full Validators to catch up on the history of the network. Redundant archives prevent a single point of failure, and allow network participants to verify the veracity of a given history.
+
+Generally, organizations that run Full Validators are also part of — or on track to join — [Tier 1](/docs/validators/tier-1-orgs), which is a core group of network participants who run three Full Validators to contribute maximum redundancy.
diff --git a/docs/validators/tier-1-orgs.mdx b/docs/validators/tier-1-orgs.mdx
index 43fe8f1ec..e8821255a 100644
--- a/docs/validators/tier-1-orgs.mdx
+++ b/docs/validators/tier-1-orgs.mdx
@@ -1,35 +1,36 @@
 ---
 title: Tier 1 Organizations
-sidebar_position: 30
+description: "Tier 1 organizations are a group of organizations that bear the safety and liveness of the Stellar network on their shoulders. They earn this role because most other organizations on the network require agreement from them — by including them in their quorum sets — in order to commit to a new ledger."
 ---
 
-# Tier 1 Organizations
-
 Tier 1 organizations are a group of organizations that bear the safety and liveness of the Stellar network on their shoulders. They earn this role because most other organizations on the network require agreement from them — by including them in their quorum sets — in order to commit to a new ledger.[^1]
 
 To become a Tier 1 organization, a team running validators must convince enough other organizations to trust them. SDF works closely with Tier 1 organizations to ensure network health, maintain robust quorum intersection, and build in redundancy to minimize disruptions. This guide outlines the requirements, costs, and process for organizations that want to join (or evaluate joining) the Tier 1 quorum.
 
-:::info[In short]
+<Info>
+
+**In short**
 
 Run three geographically dispersed Full Validators, achieve sustained 99.9%+ uptime visible on [Obsrvr Radar](https://radar.withobsrvr.com/), complete [SEP-20](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0020.md) and [SEP-1](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md) self-verification, and coordinate actively with the existing Tier 1 community. Joining is not a unilateral SDF decision — every existing Tier 1 organization independently decides whether to add you to their quorum set. Expect a process measured in months, not weeks.
 
-:::
+</Info>
+<Info>
 
-:::info[Not ready for Tier 1?]
+**Not ready for Tier 1?**
 
-Running a single [Basic or Full Validator](./README.mdx) is a meaningful contribution to network decentralization and a great way to build operational experience. The [Admin Guide](./admin-guide/README.mdx) covers everything you need for single-node setup. This page covers the additional requirements for running three Full Validators as a Tier 1 organization.
+Running a single [Basic or Full Validator](/docs/validators) is a meaningful contribution to network decentralization and a great way to build operational experience. The [Admin Guide](/docs/validators/admin-guide) covers everything you need for single-node setup. This page covers the additional requirements for running three Full Validators as a Tier 1 organization.
 
-:::
+</Info>
 
 ## What Tier 1 Requires
 
 | Requirement | Details |
 | --- | --- |
-| **Full Validators** | 3, each [publishing a complete separate history archive](./admin-guide/publishing-history-archives.mdx). Make sure to follow caching guidelines. |
-| **Installation** | Stellar Core installed from the [SDF-published Ubuntu packages](./admin-guide/installation.mdx#package-based-installation), not third-party packages, so security patches reach you promptly |
+| **Full Validators** | 3, each [publishing a complete separate history archive](./admin-guide/publishing-history-archives). Make sure to follow caching guidelines. |
+| **Installation** | Stellar Core installed from the [SDF-published Ubuntu packages](/docs/validators/admin-guide/installation#package-based-installation), not third-party packages, so security patches reach you promptly |
 | **Geographic dispersion** | Nodes in different data centers or cloud regions |
 | **Self-verification** | [SEP-20](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0020.md) on-chain identity linking + [SEP-1](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md) stellar.toml |
-| **Uptime** | 99.9%+ target with 24/7 [monitoring and alerting](./admin-guide/monitoring.mdx) |
+| **Uptime** | 99.9%+ target with 24/7 [monitoring and alerting](./admin-guide/monitoring) |
 | **Coordination** | Active communication with other Tier 1 organizations |
 | **Trust** | Other Tier 1 organizations must choose to include you in their quorum sets |
 
@@ -99,16 +100,16 @@ The checklist below covers the operational work. Completing it is necessary but
 
 ### Phase 1: First Full Validator
 
-Work through the [Admin Guide](./admin-guide/README.mdx) to stand up a single Full Validator on Mainnet:
+Work through the [Admin Guide](/docs/validators/admin-guide) to stand up a single Full Validator on Mainnet:
 
-- [ ] Review [prerequisites](./admin-guide/prerequisites.mdx) and provision a server
-- [ ] Enable [NTP clock synchronization](./admin-guide/prerequisites.mdx#clock-synchronization)
-- [ ] [Install](./admin-guide/installation.mdx#package-based-installation) Stellar Core from the SDF-published Ubuntu packages
-- [ ] [Configure](./admin-guide/configuring.mdx) for Mainnet with a validator key pair (`stellar-core gen-seed`)
-- [ ] [Prepare your environment](./admin-guide/environment-preparation.mdx) and initialize the database
-- [ ] Set up a [history archive](./admin-guide/publishing-history-archives.mdx)
-- [ ] [Start your node](./admin-guide/running-node.mdx) and sync to the network
-- [ ] Set up [monitoring](./admin-guide/monitoring.mdx) with Prometheus + Grafana
+- [ ] Review [prerequisites](./admin-guide/prerequisites) and provision a server
+- [ ] Enable [NTP clock synchronization](./admin-guide/prerequisites#clock-synchronization)
+- [ ] [Install](/docs/validators/admin-guide/installation#package-based-installation) Stellar Core from the SDF-published Ubuntu packages
+- [ ] [Configure](./admin-guide/configuring) for Mainnet with a validator key pair (`stellar-core gen-seed`)
+- [ ] [Prepare your environment](./admin-guide/environment-preparation) and initialize the database
+- [ ] Set up a [history archive](./admin-guide/publishing-history-archives)
+- [ ] [Start your node](./admin-guide/running-node) and sync to the network
+- [ ] Set up [monitoring](./admin-guide/monitoring) with Prometheus + Grafana
 
 ### Phase 2: Three Full Validators
 
@@ -116,8 +117,8 @@ Scale to the Tier 1 architecture:
 
 - [ ] Provision 2 additional servers in **different geographic regions**
 - [ ] Generate **unique** key pairs for each node — never share seeds
-- [ ] Configure each with its own [history archive](./admin-guide/publishing-history-archives.mdx) (one archive per node)
-- [ ] Deploy the standard Tier 1 [quorum set](./admin-guide/configuring.mdx#choosing-your-quorum-set) on all three nodes, declaring your own organization as `HIGH` quality
+- [ ] Configure each with its own [history archive](./admin-guide/publishing-history-archives) (one archive per node)
+- [ ] Deploy the standard Tier 1 [quorum set](./admin-guide/configuring#choosing-your-quorum-set) on all three nodes, declaring your own organization as `HIGH` quality
 - [ ] Extend monitoring to cover all three nodes
 
 ### Phase 3: Identity and Verification
@@ -140,7 +141,7 @@ Earn the confidence of existing Tier 1 organizations:
 - [ ] Respond promptly to maintenance coordination from other validators
 - [ ] Engage with SDF about Tier 1 candidacy when your track record is established
 
-### What Happens When You're Ready
+### What Happens When You're Ready {#what-happens-when-youre-ready}
 
 Once SDF and existing Tier 1 organizations agree you meet the bar:
 
@@ -170,7 +171,7 @@ The `#validator` channel on the [Stellar Dev Discord](https://discord.gg/stellar
 | Stellar Dev Discord (`#validator`) — primary coordination channel for validator operators. Release announcements, upgrade coordination, incident response. | [discord.gg/stellardev](https://discord.gg/stellardev) |
 | stellar-core GitHub releases — official release notes | [github.com/stellar/stellar-core/releases](https://github.com/stellar/stellar-core/releases) |
 | Obsrvr Radar — public validator uptime and quorum monitoring | [radar.withobsrvr.com](https://radar.withobsrvr.com/) |
-| Admin Guide | [Admin Guide](./admin-guide/README.mdx) |
+| Admin Guide | [Admin Guide](/docs/validators/admin-guide) |
 | Example Mainnet Full Validator config | [stellar/packages on GitHub](https://github.com/stellar/packages/blob/master/docs/examples/pubnet-validator-full/stellar-core.cfg) |
 | SEP-20 (Self-Verification) | [stellar-protocol on GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0020.md) |
 | SEP-1 (stellar.toml) | [stellar-protocol on GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md) |
diff --git a/docusaurus.config.ts b/docusaurus.config.ts
deleted file mode 100644
index 928191440..000000000
--- a/docusaurus.config.ts
+++ /dev/null
@@ -1,265 +0,0 @@
-import remarkMath from 'remark-math';
-import rehypeKatex from 'rehype-katex';
-import { themes as prismThemes } from 'prism-react-renderer';
-
-import navbarItems from './config/theme/navbar';
-import footerColumns from './config/theme/footer';
-import { headTags } from './config/theme/headTags';
-
-import type { Config } from '@docusaurus/types';
-import type * as Preset from '@docusaurus/preset-classic';
-import type * as Plugin from '@docusaurus/types/src/plugin';
-import type * as OpenApiPlugin from 'docusaurus-plugin-openapi-docs';
-
-const config: Config = {
-  // future: {
-  //   faster: true,
-  //   v4: {
-  //     removeLegacyPostBuildHeadAttribute: true,
-  //     mdx1CompatDisabledByDefault: true,
-  //   }
-  // },
-  title: "Stellar Docs",
-  tagline:
-    "Stellar is a self-serve distributed ledger that you can use as a backend to power all kinds of apps and services",
-  url: "https://developers.stellar.org",
-  baseUrl: "/",
-  trailingSlash: false,
-  onBrokenAnchors: "ignore",
-  onBrokenLinks: "throw",
-  favicon: "img/docusaurus/favicon-96x96.png",
-  organizationName: "stellar",
-  projectName: "stellar-docs",
-  scripts: [
-    {
-      src: 'https://translate.google.com/translate_a/element.js',
-      async: true,
-    },
-  ],
-  clientModules: [
-    // Exposes a WebMCP `search_docs` tool to in-browser AI agents (#2556).
-    './src/clientModules/webmcp.ts',
-    './src/clientModules/apiReferenceMarkdownButton.js',
-  ],
-  plugins: [
-    "docusaurus-plugin-sass",
-    [
-      "docusaurus-plugin-sentry",
-      {
-        DSN: "efc31f19f9c54082b8d993bfb62eee57",
-      },
-    ],
-    [
-      "docusaurus-plugin-openapi-docs",
-      {
-        id: "openapi",
-        docsPluginId: "classic",
-        config: {
-          horizon: {
-            specPath: "openapi/horizon/bundled.yml",
-            outputDir: "docs/data/apis/horizon/api-reference",
-            showInfoPage: false,
-            sidebarOptions: {
-              groupPathsBy: "tagGroup",
-            },
-          } satisfies OpenApiPlugin.Options,
-          ap_platform: {
-            specPath: "openapi/anchor-platform/bundled-platform.yaml",
-            outputDir: "docs/platforms/anchor-platform/api-reference/platform/transactions",
-            hideSendButton: true,
-            showInfoPage: false,
-            template: "src/template.mustache",
-          } satisfies OpenApiPlugin.Options,
-          ap_callbacks: {
-            specPath: "openapi/anchor-platform/bundled-callbacks.yaml",
-            outputDir: "docs/platforms/anchor-platform/api-reference/callbacks",
-            hideSendButton: true,
-            showInfoPage: false,
-            template: "src/template.mustache",
-          } satisfies OpenApiPlugin.Options,
-          stellar_disbursement_platform: {
-            specPath: "openapi/stellar-disbursement-platform/bundled.yaml",
-            outputDir: "docs/platforms/stellar-disbursement-platform/api-reference",
-            showInfoPage: false,
-            sidebarOptions: {
-              groupPathsBy: "tag",
-              categoryLinkSource: 'tag',
-            },
-            template: "src/template.mustache",
-          } satisfies OpenApiPlugin.Options,
-        } satisfies Plugin.PluginOptions,
-      },
-    ],
-    './src/plugins/route-export/index.ts',
-    './src/plugins/analytics-module/index.ts',
-    'docusaurus-markdown-source-plugin',
-    // Dumps the .md-twin → source-file map consumed by the postbuild step
-    // that restores <CodeExample> content (scripts/rewrite_md_code_examples.mjs).
-    './src/plugins/markdown-source-map/index.ts',
-    [
-      "docusaurus-plugin-llms",
-      {
-        generateLLMsTxt: false, // keep our curated static/llms.txt untouched
-        generateLLMsFullTxt: true,
-        docsDir: "docs",
-        llmsFullTxtFilename: "llms-full.txt",
-        title: "Stellar Developer Documentation",
-        description:
-          "Full text of the Stellar developer documentation, concatenated as Markdown for LLM ingestion.",
-        includeBlog: false,
-        excludeImports: true,
-        removeDuplicateHeadings: true,
-      },
-    ],
-  ],
-  markdown: {
-    mermaid: true,
-    hooks: {
-      onBrokenMarkdownLinks: 'throw',
-    },
-  },
-  themes: ["docusaurus-theme-openapi-docs", "@docusaurus/theme-mermaid"],
-  presets: [
-    [
-      "classic",
-      {
-        blog: {
-          path: 'meetings',
-          blogTitle: 'Meeting Notes',
-          blogDescription: 'Notes and recordings from the Stellar protocol & developers meetings',
-          blogSidebarTitle: 'All meetings',
-          blogSidebarCount: 'ALL',
-          postsPerPage: 12,
-          routeBasePath: 'meetings',
-          onUntruncatedBlogPosts: 'ignore',
-        },
-        docs: {
-          showLastUpdateTime: true,
-          showLastUpdateAuthor: true,
-          breadcrumbs: true,
-          routeBasePath: "/docs",
-          docItemComponent: "@theme/ApiItem",
-          remarkPlugins: [remarkMath, [
-            require('@docusaurus/remark-plugin-npm2yarn'), { sync: true }
-          ]],
-          rehypePlugins: [rehypeKatex],
-          sidebarPath: "config/sidebars.ts",
-          sidebarItemsGenerator: require("./src/sidebar-generator"),
-          editUrl: "https://github.com/stellar/stellar-docs/edit/main",
-          exclude: ['**/component/**', '**/CONTRIBUTING.md'],
-        },
-        theme: {
-          customCss: [require.resolve("./src/css/custom.scss")],
-        },
-        gtag: {
-          trackingID: "G-ZCT4GYX8KN",
-          anonymizeIP: true,
-        },
-        googleTagManager: {
-          containerId: "GTM-M2JLH37",
-        },
-        sitemap: {
-          // Files under static/ bypass the Docusaurus build, so pages served
-          // from there never appear in the generated sitemap. /launch/usdt0 is
-          // a permanent page and was invisible to crawlers without this.
-          createSitemapItems: async ({
-            defaultCreateSitemapItems,
-            ...rest
-          }) => {
-            const items = await defaultCreateSitemapItems(rest);
-            return [
-              ...items,
-              {
-                url: `${rest.siteConfig.url}/launch/usdt0`,
-                changefreq: "weekly",
-                priority: 0.5
-              },
-            ];
-          },
-        },
-      } satisfies Preset.Options,
-    ],
-  ],
-  stylesheets: [
-    {
-      href: 'https://cdn.jsdelivr.net/npm/katex@0.13.24/dist/katex.min.css',
-      type: 'text/css',
-      integrity: 'sha384-odtC+0UGzzFL/6PNoE8rX/SPcQDXBJ+uRepguP4QkPCm2LBxH3FA3y+fKSiJ+AmM',
-      crossorigin: 'anonymous',
-    },
-  ],
-  headTags: headTags,
-  themeConfig: {
-    docs: {
-      sidebar: {
-        autoCollapseCategories: false,
-      },
-    },
-    image: 'img/docusaurus/dev-docs-preview.png',
-    metadata: [
-      { name: 'facebook-domain-verification', content: 'd0o7hha86jfxvtqyxz3d9i5wtfanmy' }
-    ],
-    navbar: {
-      logo: {
-        width: 100,
-        src: "img/docusaurus/stellar-logo.svg",
-        srcDark: "img/docusaurus/stellar-logo-dark.svg",
-        href: "/",
-      },
-      items: [
-        navbarItems.build,
-        navbarItems.learn,
-        navbarItems.tokens,
-        navbarItems.data,
-        navbarItems.tools,
-        navbarItems.networks,
-        navbarItems.validators,
-        ...navbarItems.translation,
-        {
-          href: "https://github.com/stellar/stellar-docs",
-          position: "right",
-          className: "header-github-link",
-          'aria-label': "GitHub",
-        },
-      ],
-    },
-    algolia: {
-      appId: "VNSJF5AWIZ",
-      apiKey: "c932e7670879e29070e269d202fb6740",
-      indexName: "crawler_Stellar Docs - Docusaurus",
-    },
-    footer: {
-      links: [
-        footerColumns.resources,
-        footerColumns.tools,
-        footerColumns.community,
-        footerColumns.about,
-      ],
-    },
-    prism: {
-      theme: prismThemes.github,
-      darkTheme: prismThemes.vsDark,
-      additionalLanguages: [
-        "bash",
-        "dart",
-        "diff",
-        "docker",
-        "java",
-        "json",
-        "json5",
-        "kotlin",
-        "log",
-        "nginx",
-        "powershell",
-        "php",
-        "python",
-        "rust",
-        "scala",
-        "toml",
-        "yaml",
-      ],
-    },
-  } satisfies Preset.ThemeConfig,
-};
-
-export default config;
diff --git a/eslint.config.mjs b/eslint.config.mjs
deleted file mode 100644
index 3c6578021..000000000
--- a/eslint.config.mjs
+++ /dev/null
@@ -1,27 +0,0 @@
-import path from "node:path";
-import { fileURLToPath } from "node:url";
-import js from "@eslint/js";
-import { FlatCompat } from "@eslint/eslintrc";
-
-const __filename = fileURLToPath(import.meta.url);
-const __dirname = path.dirname(__filename);
-const compat = new FlatCompat({
-    baseDirectory: __dirname,
-    recommendedConfig: js.configs.recommended,
-    allConfig: js.configs.all
-});
-
-export default [{
-    ignores: [
-        "**/dist",
-        "**/node_modules",
-        "**/docs",
-        "**/.github",
-        "**/build",
-        "*.js",
-        "*.ts",
-        "*.d.ts",
-        "**/static",
-        "**/.docusaurus",
-    ],
-}, ...compat.extends("plugin:@docusaurus/recommended")];
\ No newline at end of file
diff --git a/static/img/docusaurus/favicon-96x96.png b/favicon.png
similarity index 100%
rename from static/img/docusaurus/favicon-96x96.png
rename to favicon.png
diff --git a/for-agents.js b/for-agents.js
new file mode 100644
index 000000000..c7c6b7fca
--- /dev/null
+++ b/for-agents.js
@@ -0,0 +1,232 @@
+/* "For agents" panel, ported from developers.stellar.org.
+   Opens from any link whose href ends with "#for-agents" (see navbar.primary in docs.json).
+   Styles live in style.css under "For agents panel". */
+(function () {
+  if (window.__forAgentsPanelLoaded) return;
+  window.__forAgentsPanelLoaded = true;
+
+  var RAVEN_MCP_URL = "https://raven.stellar.buzz/mcp";
+  var SKILL_REPO_URL = "https://github.com/stellar/stellar-dev-skill";
+
+  var npxSkillsInstall = {
+    note: "Works with any tool that supports the Agent Skills standard.",
+    snippets: ["npx skills add " + SKILL_REPO_URL]
+  };
+  var browseSkillsInstead = {
+    note: "Tell your agent:",
+    snippets: ["Read skills.stellar.org before you start building on Stellar."]
+  };
+
+  var TOOLS = [
+    {
+      id: "claude-code", label: "Claude Code",
+      raven: { snippets: ['claude mcp add --transport http stellar-raven "' + RAVEN_MCP_URL + '"\n# then run /mcp -> Authenticate -> sign in in your browser'] },
+      skills: {
+        install: { note: "Adds the skill to your tool permanently.", snippets: ["/plugin marketplace add stellar/stellar-dev-skill", "/plugin install stellar-dev@stellar-dev"] },
+        tryWithoutInstalling: browseSkillsInstead
+      }
+    },
+    {
+      id: "codex", label: "Codex",
+      raven: { snippets: ['codex mcp add stellar-raven --url "' + RAVEN_MCP_URL + '"\ncodex mcp login stellar-raven  # opens your browser'] },
+      skills: {
+        install: { note: "Codex reads skills from ~/.codex/skills/.", snippets: ["git clone " + SKILL_REPO_URL + " ~/.codex/skills/stellar-dev-skill"] },
+        tryWithoutInstalling: browseSkillsInstead
+      }
+    },
+    {
+      id: "vscode", label: "VS Code",
+      raven: { snippets: ['code --add-mcp \'{"name":"stellar-raven","type":"http","url":"' + RAVEN_MCP_URL + '"}\''] },
+      skills: { install: npxSkillsInstall, tryWithoutInstalling: browseSkillsInstead }
+    },
+    {
+      id: "cursor", label: "Cursor",
+      raven: {
+        note: "Add to ~/.cursor/mcp.json (or .cursor/mcp.json per project). Cursor runs the OAuth sign-in on first use.",
+        snippets: ['{\n  "mcpServers": {\n    "stellar-raven": { "url": "' + RAVEN_MCP_URL + '" }\n  }\n}']
+      },
+      skills: { install: npxSkillsInstall, tryWithoutInstalling: browseSkillsInstead }
+    },
+    {
+      id: "claude-desktop", label: "Claude desktop",
+      raven: {
+        note: "Go to Settings -> Connectors -> Add custom connector, paste the endpoint, and approve the browser sign-in.",
+        snippets: [RAVEN_MCP_URL]
+      },
+      skills: { install: npxSkillsInstall, tryWithoutInstalling: browseSkillsInstead }
+    },
+    {
+      id: "other", label: "Other clients",
+      raven: {
+        note: "For clients without native remote or OAuth support, bridge with mcp-remote.",
+        snippets: ['{\n  "mcpServers": {\n    "stellar-raven": {\n      "command": "npx",\n      "args": [\n        "-y",\n        "mcp-remote@latest",\n        "' + RAVEN_MCP_URL + '",\n        "--transport",\n        "http-only"\n      ]\n    }\n  }\n}'],
+        links: [{ label: "mcp-remote", href: "https://github.com/geelen/mcp-remote" }]
+      },
+      skills: { install: npxSkillsInstall, tryWithoutInstalling: browseSkillsInstead }
+    }
+  ];
+
+  var SECTIONS = {
+    raven: {
+      title: "Raven MCP Server",
+      description: "Connect your AI agent to Stellar data and tooling.",
+      guide: { label: "Full guide", href: "/docs/build/building-with-ai" },
+      links: [
+        { label: "Try in chat", href: "https://raven.stellar.buzz/playground" },
+        { label: "View source", href: "https://github.com/stellar-experimental/stellar-raven" }
+      ]
+    },
+    skills: {
+      title: "Stellar Skills",
+      description: "Stellar context for your agent before it writes code.",
+      home: { label: "skills.stellar.org", href: "https://skills.stellar.org/" },
+      modes: [{ id: "install", label: "Install" }, { id: "tryWithoutInstalling", label: "Try without installing" }]
+    },
+    llmsTxt: { title: "llms.txt", href: "/llms.txt", description: "Machine-readable overview of the Stellar docs." }
+  };
+
+  var state = { toolId: TOOLS[0].id, mode: "install" };
+  var panel = null;
+  var returnFocus = null;
+
+  function esc(s) {
+    return String(s).replace(/[&<>"']/g, function (c) {
+      return { "&": "&amp;", "<": "&lt;", ">": "&gt;", '"': "&quot;", "'": "&#39;" }[c];
+    });
+  }
+
+  function link(l, external) {
+    var ext = external || /^https?:/.test(l.href);
+    return '<a class="fa-link" href="' + esc(l.href) + '"' + (ext ? ' target="_blank" rel="noopener noreferrer"' : "") + ">" +
+      esc(l.label) + ' <span aria-hidden="true">&rarr;</span></a>';
+  }
+
+  function copyBlock(code) {
+    return '<div class="fa-copy"><pre class="fa-code">' + esc(code) + "</pre>" +
+      '<button type="button" class="fa-copy-btn" aria-label="Copy command" data-copy="' + esc(code) + '"></button></div>';
+  }
+
+  function tool() {
+    for (var i = 0; i < TOOLS.length; i++) if (TOOLS[i].id === state.toolId) return TOOLS[i];
+    return TOOLS[0];
+  }
+
+  function render() {
+    var t = tool();
+    var raven = t.raven;
+    var skills = t.skills[state.mode];
+    var html = "";
+
+    html += '<div class="fa-header"><span class="fa-title" id="fa-panel-title">Use Stellar with AI</span>' +
+      '<button type="button" class="fa-close" aria-label="Close"></button></div>';
+    html += '<div class="fa-body">';
+
+    html += '<div class="fa-picker"><span class="fa-picker-label">Your tool</span><div class="fa-pills" role="radiogroup">';
+    TOOLS.forEach(function (x) {
+      html += '<button type="button" role="radio" class="fa-pill' + (x.id === state.toolId ? " is-active" : "") +
+        '" aria-checked="' + (x.id === state.toolId) + '" data-tool="' + x.id + '">' + esc(x.label) + "</button>";
+    });
+    html += "</div></div>";
+
+    html += '<section class="fa-section"><div class="fa-section-head"><h3 class="fa-section-title">' + esc(SECTIONS.raven.title) + "</h3>" +
+      link(SECTIONS.raven.guide) + "</div><p class=\"fa-desc\">" + esc(SECTIONS.raven.description) + "</p>";
+    if (raven.note) html += '<p class="fa-note">' + esc(raven.note) + "</p>";
+    raven.snippets.forEach(function (c) { html += copyBlock(c); });
+    html += '<div class="fa-links">';
+    SECTIONS.raven.links.forEach(function (l) { html += link(l, true); });
+    (raven.links || []).forEach(function (l) { html += link(l, true); });
+    html += "</div></section>";
+
+    html += '<section class="fa-section"><div class="fa-section-head"><h3 class="fa-section-title">' + esc(SECTIONS.skills.title) + "</h3>" +
+      link(SECTIONS.skills.home, true) + "</div><p class=\"fa-desc\">" + esc(SECTIONS.skills.description) + "</p>";
+    html += '<div class="fa-pills" role="group">';
+    SECTIONS.skills.modes.forEach(function (m) {
+      html += '<button type="button" class="fa-pill' + (m.id === state.mode ? " is-active" : "") +
+        '" aria-pressed="' + (m.id === state.mode) + '" data-mode="' + m.id + '">' + esc(m.label) + "</button>";
+    });
+    html += "</div>";
+    if (skills.note) html += '<p class="fa-note">' + esc(skills.note) + "</p>";
+    skills.snippets.forEach(function (c) { html += copyBlock(c); });
+    html += "</section>";
+
+    html += '<section class="fa-section">' + link({ label: SECTIONS.llmsTxt.title, href: SECTIONS.llmsTxt.href }) +
+      '<p class="fa-desc">' + esc(SECTIONS.llmsTxt.description) + "</p></section>";
+
+    html += "</div>";
+    panel.innerHTML = html;
+  }
+
+  function refocus(selector) {
+    var el = panel.querySelector(selector);
+    if (el) el.focus();
+  }
+
+  function ensurePanel() {
+    if (panel) return panel;
+    panel = document.createElement("div");
+    panel.id = "for-agents-panel";
+    panel.setAttribute("role", "dialog");
+    panel.setAttribute("aria-labelledby", "fa-panel-title");
+    panel.setAttribute("aria-modal", "true");
+    panel.hidden = true;
+    document.body.appendChild(panel);
+
+    panel.addEventListener("click", function (e) {
+      var el = e.target.closest("button");
+      if (!el) return;
+      if (el.classList.contains("fa-close")) return close();
+      // render() replaces the panel's contents, so put focus back on the same pill.
+      if (el.dataset.tool) { state.toolId = el.dataset.tool; render(); refocus('[data-tool="' + state.toolId + '"]'); return; }
+      if (el.dataset.mode) { state.mode = el.dataset.mode; render(); refocus('[data-mode="' + state.mode + '"]'); return; }
+      if (el.dataset.copy !== undefined) {
+        navigator.clipboard.writeText(el.dataset.copy).then(function () {
+          el.classList.add("is-copied");
+          setTimeout(function () { el.classList.remove("is-copied"); }, 2000);
+        }).catch(function (err) {
+          console.error("For agents panel: copy failed", err);
+        });
+      }
+    });
+    render();
+    return panel;
+  }
+
+  function open() {
+    returnFocus = document.activeElement;
+    ensurePanel();
+    panel.hidden = false;
+    document.body.classList.add("fa-open");
+    var first = panel.querySelector(".fa-close");
+    if (first) first.focus();
+  }
+
+  function close() {
+    if (!panel) return;
+    panel.hidden = true;
+    document.body.classList.remove("fa-open");
+    if (returnFocus && returnFocus.focus) returnFocus.focus();
+    returnFocus = null;
+  }
+
+  document.addEventListener("click", function (e) {
+    var a = e.target.closest("a[href]");
+    if (a && /#for-agents$/.test(a.getAttribute("href"))) {
+      e.preventDefault();
+      panel && !panel.hidden ? close() : open();
+      return;
+    }
+    if (panel && !panel.hidden && e.composedPath().indexOf(panel) === -1) close();
+  });
+
+  document.addEventListener("keydown", function (e) {
+    if (!panel || panel.hidden) return;
+    if (e.key === "Escape") return close();
+    // Keep Tab focus inside the open panel.
+    if (e.key !== "Tab") return;
+    var items = panel.querySelectorAll("button, a[href]");
+    if (!items.length) return;
+    var first = items[0], last = items[items.length - 1];
+    if (e.shiftKey && document.activeElement === first) { e.preventDefault(); last.focus(); }
+    else if (!e.shiftKey && document.activeElement === last) { e.preventDefault(); first.focus(); }
+  });
+})();
diff --git a/static/img/docusaurus/dev-docs-preview.png b/img/docusaurus/dev-docs-preview.png
similarity index 100%
rename from static/img/docusaurus/dev-docs-preview.png
rename to img/docusaurus/dev-docs-preview.png
diff --git a/static/img/hubble/add-column-chart.png b/img/hubble/add-column-chart.png
similarity index 100%
rename from static/img/hubble/add-column-chart.png
rename to img/hubble/add-column-chart.png
diff --git a/static/img/hubble/add-contract-data.png b/img/hubble/add-contract-data.png
similarity index 100%
rename from static/img/hubble/add-contract-data.png
rename to img/hubble/add-contract-data.png
diff --git a/static/img/hubble/add-custom-query.png b/img/hubble/add-custom-query.png
similarity index 100%
rename from static/img/hubble/add-custom-query.png
rename to img/hubble/add-custom-query.png
diff --git a/static/img/hubble/add-pie-chart.png b/img/hubble/add-pie-chart.png
similarity index 100%
rename from static/img/hubble/add-pie-chart.png
rename to img/hubble/add-pie-chart.png
diff --git a/static/img/hubble/add-quick-filter.png b/img/hubble/add-quick-filter.png
similarity index 100%
rename from static/img/hubble/add-quick-filter.png
rename to img/hubble/add-quick-filter.png
diff --git a/static/img/hubble/airflow_dag_toggle.png b/img/hubble/airflow_dag_toggle.png
similarity index 100%
rename from static/img/hubble/airflow_dag_toggle.png
rename to img/hubble/airflow_dag_toggle.png
diff --git a/static/img/hubble/bq-connector.png b/img/hubble/bq-connector.png
similarity index 100%
rename from static/img/hubble/bq-connector.png
rename to img/hubble/bq-connector.png
diff --git a/static/img/hubble/click_add_data.png b/img/hubble/click_add_data.png
similarity index 100%
rename from static/img/hubble/click_add_data.png
rename to img/hubble/click_add_data.png
diff --git a/static/img/hubble/column-chart-config.png b/img/hubble/column-chart-config.png
similarity index 100%
rename from static/img/hubble/column-chart-config.png
rename to img/hubble/column-chart-config.png
diff --git a/static/img/hubble/create-data-source.png b/img/hubble/create-data-source.png
similarity index 100%
rename from static/img/hubble/create-data-source.png
rename to img/hubble/create-data-source.png
diff --git a/static/img/hubble/create-report.png b/img/hubble/create-report.png
similarity index 100%
rename from static/img/hubble/create-report.png
rename to img/hubble/create-report.png
diff --git a/static/img/hubble/data_model_diagram.png b/img/hubble/data_model_diagram.png
similarity index 100%
rename from static/img/hubble/data_model_diagram.png
rename to img/hubble/data_model_diagram.png
diff --git a/static/img/hubble/dbt_enriched_base_tables.png b/img/hubble/dbt_enriched_base_tables.png
similarity index 100%
rename from static/img/hubble/dbt_enriched_base_tables.png
rename to img/hubble/dbt_enriched_base_tables.png
diff --git a/static/img/hubble/expired-entry-column-chart.png b/img/hubble/expired-entry-column-chart.png
similarity index 100%
rename from static/img/hubble/expired-entry-column-chart.png
rename to img/hubble/expired-entry-column-chart.png
diff --git a/static/img/hubble/filter-contract.png b/img/hubble/filter-contract.png
similarity index 100%
rename from static/img/hubble/filter-contract.png
rename to img/hubble/filter-contract.png
diff --git a/static/img/hubble/filtered-report.png b/img/hubble/filtered-report.png
similarity index 100%
rename from static/img/hubble/filtered-report.png
rename to img/hubble/filtered-report.png
diff --git a/static/img/hubble/history_table_export.png b/img/hubble/history_table_export.png
similarity index 100%
rename from static/img/hubble/history_table_export.png
rename to img/hubble/history_table_export.png
diff --git a/static/img/hubble/hubble_visualization_demo.gif b/img/hubble/hubble_visualization_demo.gif
similarity index 100%
rename from static/img/hubble/hubble_visualization_demo.gif
rename to img/hubble/hubble_visualization_demo.gif
diff --git a/static/img/hubble/persistent-only.png b/img/hubble/persistent-only.png
similarity index 100%
rename from static/img/hubble/persistent-only.png
rename to img/hubble/persistent-only.png
diff --git a/static/img/hubble/pie-config.png b/img/hubble/pie-config.png
similarity index 100%
rename from static/img/hubble/pie-config.png
rename to img/hubble/pie-config.png
diff --git a/static/img/hubble/pie-contract-data.png b/img/hubble/pie-contract-data.png
similarity index 100%
rename from static/img/hubble/pie-contract-data.png
rename to img/hubble/pie-contract-data.png
diff --git a/static/img/hubble/pie_chart_durability.png b/img/hubble/pie_chart_durability.png
similarity index 100%
rename from static/img/hubble/pie_chart_durability.png
rename to img/hubble/pie_chart_durability.png
diff --git a/static/img/hubble/select-data-sources.png b/img/hubble/select-data-sources.png
similarity index 100%
rename from static/img/hubble/select-data-sources.png
rename to img/hubble/select-data-sources.png
diff --git a/static/img/hubble/state_table_export.png b/img/hubble/state_table_export.png
similarity index 100%
rename from static/img/hubble/state_table_export.png
rename to img/hubble/state_table_export.png
diff --git a/static/img/hubble/stellar_dbt_architecture.png b/img/hubble/stellar_dbt_architecture.png
similarity index 100%
rename from static/img/hubble/stellar_dbt_architecture.png
rename to img/hubble/stellar_dbt_architecture.png
diff --git a/static/img/hubble/stellar_etl_airflow_architecture.png b/img/hubble/stellar_etl_airflow_architecture.png
similarity index 100%
rename from static/img/hubble/stellar_etl_airflow_architecture.png
rename to img/hubble/stellar_etl_airflow_architecture.png
diff --git a/static/img/hubble/stellar_etl_architecture.png b/img/hubble/stellar_etl_architecture.png
similarity index 100%
rename from static/img/hubble/stellar_etl_architecture.png
rename to img/hubble/stellar_etl_architecture.png
diff --git a/static/img/hubble/stellar_overall_architecture.png b/img/hubble/stellar_overall_architecture.png
similarity index 100%
rename from static/img/hubble/stellar_overall_architecture.png
rename to img/hubble/stellar_overall_architecture.png
diff --git a/static/img/migrating/counter.png b/img/migrating/counter.png
similarity index 100%
rename from static/img/migrating/counter.png
rename to img/migrating/counter.png
diff --git a/static/img/migrating/deploy-counter.png b/img/migrating/deploy-counter.png
similarity index 100%
rename from static/img/migrating/deploy-counter.png
rename to img/migrating/deploy-counter.png
diff --git a/static/img/migrating/deployed-contracts.png b/img/migrating/deployed-contracts.png
similarity index 100%
rename from static/img/migrating/deployed-contracts.png
rename to img/migrating/deployed-contracts.png
diff --git a/static/img/migrating/increment.png b/img/migrating/increment.png
similarity index 100%
rename from static/img/migrating/increment.png
rename to img/migrating/increment.png
diff --git a/static/img/migrating/vault-project.png b/img/migrating/vault-project.png
similarity index 100%
rename from static/img/migrating/vault-project.png
rename to img/migrating/vault-project.png
diff --git a/img/sds-icons/icons-alert-circle.svg b/img/sds-icons/icons-alert-circle.svg
new file mode 100644
index 000000000..76acefada
--- /dev/null
+++ b/img/sds-icons/icons-alert-circle.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M12 8V12M12 16H12.01M22 12C22 17.5228 17.5228 22 12 22C6.47715 22 2 17.5228 2 12C2 6.47715 6.47715 2 12 2C17.5228 2 22 6.47715 22 12Z" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/icons-alert-triangle.svg b/img/sds-icons/icons-alert-triangle.svg
new file mode 100644
index 000000000..fc4461196
--- /dev/null
+++ b/img/sds-icons/icons-alert-triangle.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M11.9998 8.99999V13M11.9998 17H12.0098M10.6151 3.89171L2.39019 18.0983C1.93398 18.8863 1.70588 19.2803 1.73959 19.6037C1.769 19.8857 1.91677 20.142 2.14613 20.3088C2.40908 20.5 2.86435 20.5 3.77487 20.5H20.2246C21.1352 20.5 21.5904 20.5 21.8534 20.3088C22.0827 20.142 22.2305 19.8857 22.2599 19.6037C22.2936 19.2803 22.0655 18.8863 21.6093 18.0983L13.3844 3.89171C12.9299 3.10654 12.7026 2.71396 12.4061 2.58211C12.1474 2.4671 11.8521 2.4671 11.5935 2.58211C11.2969 2.71396 11.0696 3.10655 10.6151 3.89171Z" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/icons-announcement-01.svg b/img/sds-icons/icons-announcement-01.svg
new file mode 100644
index 000000000..50a6b16c3
--- /dev/null
+++ b/img/sds-icons/icons-announcement-01.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M22 8.00001V12M10.25 5.5H6.8C5.11984 5.5 4.27976 5.5 3.63803 5.82698C3.07354 6.1146 2.6146 6.57355 2.32698 7.13803C2 7.77977 2 8.61985 2 10.3L2 11.5C2 12.4319 2 12.8978 2.15224 13.2654C2.35523 13.7554 2.74458 14.1448 3.23463 14.3478C3.60218 14.5 4.06812 14.5 5 14.5V18.75C5 18.9822 5 19.0983 5.00963 19.196C5.10316 20.1456 5.85441 20.8968 6.80397 20.9904C6.90175 21 7.01783 21 7.25 21C7.48217 21 7.59826 21 7.69604 20.9904C8.64559 20.8968 9.39685 20.1456 9.49037 19.196C9.5 19.0983 9.5 18.9822 9.5 18.75V14.5H10.25C12.0164 14.5 14.1772 15.4469 15.8443 16.3556C16.8168 16.8858 17.3031 17.1509 17.6216 17.1119C17.9169 17.0757 18.1402 16.9431 18.3133 16.7011C18.5 16.4402 18.5 15.918 18.5 14.8737V5.12629C18.5 4.082 18.5 3.55985 18.3133 3.29889C18.1402 3.0569 17.9169 2.9243 17.6216 2.88813C17.3031 2.84912 16.8168 3.1142 15.8443 3.64436C14.1772 4.55312 12.0164 5.5 10.25 5.5Z" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/icons-arrow-right.svg b/img/sds-icons/icons-arrow-right.svg
new file mode 100644
index 000000000..500a8ef6a
--- /dev/null
+++ b/img/sds-icons/icons-arrow-right.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M5 12H19M19 12L12 5M19 12L12 19" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/icons-arrow-up-right.svg b/img/sds-icons/icons-arrow-up-right.svg
new file mode 100644
index 000000000..a7af55f81
--- /dev/null
+++ b/img/sds-icons/icons-arrow-up-right.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M7 17L17 7M17 7H7M17 7V17" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/icons-check-circle.svg b/img/sds-icons/icons-check-circle.svg
new file mode 100644
index 000000000..5835a3916
--- /dev/null
+++ b/img/sds-icons/icons-check-circle.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M7.5 12L10.5 15L16.5 9M22 12C22 17.5228 17.5228 22 12 22C6.47715 22 2 17.5228 2 12C2 6.47715 6.47715 2 12 2C17.5228 2 22 6.47715 22 12Z" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/icons-check.svg b/img/sds-icons/icons-check.svg
new file mode 100644
index 000000000..3c876dd41
--- /dev/null
+++ b/img/sds-icons/icons-check.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M20 6L9 17L4 12" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/icons-chevron-left.svg b/img/sds-icons/icons-chevron-left.svg
new file mode 100644
index 000000000..b7f65b40b
--- /dev/null
+++ b/img/sds-icons/icons-chevron-left.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M15 18L9 12L15 6" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/icons-chevron-right.svg b/img/sds-icons/icons-chevron-right.svg
new file mode 100644
index 000000000..f0dbcca17
--- /dev/null
+++ b/img/sds-icons/icons-chevron-right.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M9 18L15 12L9 6" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/icons-code-02.svg b/img/sds-icons/icons-code-02.svg
new file mode 100644
index 000000000..7471e0117
--- /dev/null
+++ b/img/sds-icons/icons-code-02.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M17 17L22 12L17 7M7 7L2 12L7 17M14 3L10 21" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/icons-copy-01.svg b/img/sds-icons/icons-copy-01.svg
new file mode 100644
index 000000000..e06ace389
--- /dev/null
+++ b/img/sds-icons/icons-copy-01.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M5 15C4.06812 15 3.60218 15 3.23463 14.8478C2.74458 14.6448 2.35523 14.2554 2.15224 13.7654C2 13.3978 2 12.9319 2 12V5.2C2 4.0799 2 3.51984 2.21799 3.09202C2.40973 2.71569 2.71569 2.40973 3.09202 2.21799C3.51984 2 4.0799 2 5.2 2H12C12.9319 2 13.3978 2 13.7654 2.15224C14.2554 2.35523 14.6448 2.74458 14.8478 3.23463C15 3.60218 15 4.06812 15 5M12.2 22H18.8C19.9201 22 20.4802 22 20.908 21.782C21.2843 21.5903 21.5903 21.2843 21.782 20.908C22 20.4802 22 19.9201 22 18.8V12.2C22 11.0799 22 10.5198 21.782 10.092C21.5903 9.71569 21.2843 9.40973 20.908 9.21799C20.4802 9 19.9201 9 18.8 9H12.2C11.0799 9 10.5198 9 10.092 9.21799C9.71569 9.40973 9.40973 9.71569 9.21799 10.092C9 10.5198 9 11.0799 9 12.2V18.8C9 19.9201 9 20.4802 9.21799 20.908C9.40973 21.2843 9.71569 21.5903 10.092 21.782C10.5198 22 11.0799 22 12.2 22Z" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/icons-cube-01.svg b/img/sds-icons/icons-cube-01.svg
new file mode 100644
index 000000000..ca16ae233
--- /dev/null
+++ b/img/sds-icons/icons-cube-01.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M20.5 7.27777L12 12M12 12L3.49997 7.27777M12 12L12 21.5M21 16.0586V7.94147C21 7.59883 21 7.4275 20.9495 7.27471C20.9049 7.13953 20.8318 7.01545 20.7354 6.91076C20.6263 6.79242 20.4766 6.70922 20.177 6.54282L12.777 2.43171C12.4934 2.27415 12.3516 2.19537 12.2015 2.16448C12.0685 2.13715 11.9315 2.13715 11.7986 2.16448C11.6484 2.19537 11.5066 2.27415 11.223 2.43171L3.82297 6.54282C3.52345 6.70922 3.37369 6.79242 3.26463 6.91076C3.16816 7.01545 3.09515 7.13953 3.05048 7.27471C3 7.42751 3 7.59883 3 7.94147V16.0586C3 16.4012 3 16.5725 3.05048 16.7253C3.09515 16.8605 3.16816 16.9846 3.26463 17.0893C3.37369 17.2076 3.52345 17.2908 3.82297 17.4572L11.223 21.5683C11.5066 21.7259 11.6484 21.8047 11.7986 21.8356C11.9315 21.8629 12.0685 21.8629 12.2015 21.8356C12.3516 21.8047 12.4934 21.7259 12.777 21.5683L20.177 17.4572C20.4766 17.2908 20.6263 17.2076 20.7354 17.0893C20.8318 16.9846 20.9049 16.8605 20.9495 16.7253C21 16.5725 21 16.4012 21 16.0586Z" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/icons-dots-vertical.svg b/img/sds-icons/icons-dots-vertical.svg
new file mode 100644
index 000000000..93931e94d
--- /dev/null
+++ b/img/sds-icons/icons-dots-vertical.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M12 13C12.5523 13 13 12.5523 13 12C13 11.4477 12.5523 11 12 11C11.4477 11 11 11.4477 11 12C11 12.5523 11.4477 13 12 13Z" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/><path d="M12 6C12.5523 6 13 5.55228 13 5C13 4.44772 12.5523 4 12 4C11.4477 4 11 4.44772 11 5C11 5.55228 11.4477 6 12 6Z" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/><path d="M12 20C12.5523 20 13 19.5523 13 19C13 18.4477 12.5523 18 12 18C11.4477 18 11 18.4477 11 19C11 19.5523 11.4477 20 12 20Z" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/icons-file-04.svg b/img/sds-icons/icons-file-04.svg
new file mode 100644
index 000000000..1626b2de0
--- /dev/null
+++ b/img/sds-icons/icons-file-04.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M14 2.26946V6.4C14 6.96005 14 7.24008 14.109 7.45399C14.2049 7.64215 14.3578 7.79513 14.546 7.89101C14.7599 8 15.0399 8 15.6 8H19.7305M20 9.98822V17.2C20 18.8802 20 19.7202 19.673 20.362C19.3854 20.9265 18.9265 21.3854 18.362 21.673C17.7202 22 16.8802 22 15.2 22H8.8C7.11984 22 6.27976 22 5.63803 21.673C5.07354 21.3854 4.6146 20.9265 4.32698 20.362C4 19.7202 4 18.8802 4 17.2V6.8C4 5.11984 4 4.27976 4.32698 3.63803C4.6146 3.07354 5.07354 2.6146 5.63803 2.32698C6.27976 2 7.11984 2 8.8 2H12.0118C12.7455 2 13.1124 2 13.4577 2.08289C13.7638 2.15638 14.0564 2.27759 14.3249 2.44208C14.6276 2.6276 14.887 2.88703 15.4059 3.40589L18.5941 6.59411C19.113 7.11297 19.3724 7.3724 19.5579 7.67515C19.7224 7.94356 19.8436 8.2362 19.9171 8.5423C20 8.88757 20 9.25445 20 9.98822Z" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/icons-folder.svg b/img/sds-icons/icons-folder.svg
new file mode 100644
index 000000000..669c203e5
--- /dev/null
+++ b/img/sds-icons/icons-folder.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M13 7L11.8845 4.76892C11.5634 4.1268 11.4029 3.80573 11.1634 3.57116C10.9516 3.36373 10.6963 3.20597 10.4161 3.10931C10.0992 3 9.74021 3 9.02229 3H5.2C4.0799 3 3.51984 3 3.09202 3.21799C2.71569 3.40973 2.40973 3.71569 2.21799 4.09202C2 4.51984 2 5.0799 2 6.2V7M2 7H17.2C18.8802 7 19.7202 7 20.362 7.32698C20.9265 7.6146 21.3854 8.07354 21.673 8.63803C22 9.27976 22 10.1198 22 11.8V16.2C22 17.8802 22 18.7202 21.673 19.362C21.3854 19.9265 20.9265 20.3854 20.362 20.673C19.7202 21 18.8802 21 17.2 21H6.8C5.11984 21 4.27976 21 3.63803 20.673C3.07354 20.3854 2.6146 19.9265 2.32698 19.362C2 18.7202 2 17.8802 2 16.2V7Z" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/icons-home-05.svg b/img/sds-icons/icons-home-05.svg
new file mode 100644
index 000000000..4d3f560f1
--- /dev/null
+++ b/img/sds-icons/icons-home-05.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M12.9823 2.764C12.631 2.49075 12.4553 2.35412 12.2613 2.3016C12.0902 2.25526 11.9098 2.25526 11.7387 2.3016C11.5447 2.35412 11.369 2.49075 11.0177 2.764L4.23539 8.03912C3.78202 8.39175 3.55534 8.56806 3.39203 8.78886C3.24737 8.98444 3.1396 9.20478 3.07403 9.43905C3 9.70352 3 9.9907 3 10.5651V17.8C3 18.9201 3 19.4801 3.21799 19.908C3.40973 20.2843 3.71569 20.5903 4.09202 20.782C4.51984 21 5.0799 21 6.2 21H8.2C8.48003 21 8.62004 21 8.727 20.9455C8.82108 20.8976 8.89757 20.8211 8.9455 20.727C9 20.62 9 20.48 9 20.2V13.6C9 13.0399 9 12.7599 9.10899 12.546C9.20487 12.3578 9.35785 12.2049 9.54601 12.109C9.75992 12 10.0399 12 10.6 12H13.4C13.9601 12 14.2401 12 14.454 12.109C14.6422 12.2049 14.7951 12.3578 14.891 12.546C15 12.7599 15 13.0399 15 13.6V20.2C15 20.48 15 20.62 15.0545 20.727C15.1024 20.8211 15.1789 20.8976 15.273 20.9455C15.38 21 15.52 21 15.8 21H17.8C18.9201 21 19.4802 21 19.908 20.782C20.2843 20.5903 20.5903 20.2843 20.782 19.908C21 19.4801 21 18.9201 21 17.8V10.5651C21 9.9907 21 9.70352 20.926 9.43905C20.8604 9.20478 20.7526 8.98444 20.608 8.78886C20.4447 8.56806 20.218 8.39175 19.7646 8.03913L12.9823 2.764Z" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/icons-info-circle.svg b/img/sds-icons/icons-info-circle.svg
new file mode 100644
index 000000000..2c98aeb16
--- /dev/null
+++ b/img/sds-icons/icons-info-circle.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M12 16V12M12 8H12.01M22 12C22 17.5228 17.5228 22 12 22C6.47715 22 2 17.5228 2 12C2 6.47715 6.47715 2 12 2C17.5228 2 22 6.47715 22 12Z" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/icons-message-square-01.svg b/img/sds-icons/icons-message-square-01.svg
new file mode 100644
index 000000000..9c54d4d9e
--- /dev/null
+++ b/img/sds-icons/icons-message-square-01.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M3 7.8C3 6.11984 3 5.27976 3.32698 4.63803C3.6146 4.07354 4.07354 3.6146 4.63803 3.32698C5.27976 3 6.11984 3 7.8 3H16.2C17.8802 3 18.7202 3 19.362 3.32698C19.9265 3.6146 20.3854 4.07354 20.673 4.63803C21 5.27976 21 6.11984 21 7.8V13.2C21 14.8802 21 15.7202 20.673 16.362C20.3854 16.9265 19.9265 17.3854 19.362 17.673C18.7202 18 17.8802 18 16.2 18H9.68375C9.0597 18 8.74767 18 8.44921 18.0613C8.18443 18.1156 7.9282 18.2055 7.68749 18.3285C7.41617 18.4671 7.17252 18.662 6.68521 19.0518L4.29976 20.9602C3.88367 21.2931 3.67563 21.4595 3.50054 21.4597C3.34827 21.4599 3.20422 21.3906 3.10923 21.2716C3 21.1348 3 20.8684 3 20.3355V7.8Z" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/icons-phone-01.svg b/img/sds-icons/icons-phone-01.svg
new file mode 100644
index 000000000..551866194
--- /dev/null
+++ b/img/sds-icons/icons-phone-01.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M12 17.5H12.01M8.2 22H15.8C16.9201 22 17.4802 22 17.908 21.782C18.2843 21.5903 18.5903 21.2843 18.782 20.908C19 20.4802 19 19.9201 19 18.8V5.2C19 4.07989 19 3.51984 18.782 3.09202C18.5903 2.71569 18.2843 2.40973 17.908 2.21799C17.4802 2 16.9201 2 15.8 2H8.2C7.0799 2 6.51984 2 6.09202 2.21799C5.71569 2.40973 5.40973 2.71569 5.21799 3.09202C5 3.51984 5 4.0799 5 5.2V18.8C5 19.9201 5 20.4802 5.21799 20.908C5.40973 21.2843 5.71569 21.5903 6.09202 21.782C6.51984 22 7.07989 22 8.2 22ZM12.5 17.5C12.5 17.7761 12.2761 18 12 18C11.7239 18 11.5 17.7761 11.5 17.5C11.5 17.2239 11.7239 17 12 17C12.2761 17 12.5 17.2239 12.5 17.5Z" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/icons-play.svg b/img/sds-icons/icons-play.svg
new file mode 100644
index 000000000..e71827b9e
--- /dev/null
+++ b/img/sds-icons/icons-play.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M5 4.98963C5 4.01847 5 3.53289 5.20249 3.26522C5.37889 3.03203 5.64852 2.88773 5.9404 2.8703C6.27544 2.8503 6.67946 3.11965 7.48752 3.65835L18.0031 10.6687C18.6708 11.1139 19.0046 11.3364 19.1209 11.6169C19.2227 11.8622 19.2227 12.1378 19.1209 12.3831C19.0046 12.6636 18.6708 12.8862 18.0031 13.3313L7.48752 20.3417C6.67946 20.8804 6.27544 21.1497 5.9404 21.1297C5.64852 21.1123 5.37889 20.968 5.20249 20.7348C5 20.4671 5 19.9815 5 19.0104V4.98963Z" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/icons-search-md.svg b/img/sds-icons/icons-search-md.svg
new file mode 100644
index 000000000..1f5c50824
--- /dev/null
+++ b/img/sds-icons/icons-search-md.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M21 21L16.65 16.65M19 11C19 15.4183 15.4183 19 11 19C6.58172 19 3 15.4183 3 11C3 6.58172 6.58172 3 11 3C15.4183 3 19 6.58172 19 11Z" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/icons-tool-02.svg b/img/sds-icons/icons-tool-02.svg
new file mode 100644
index 000000000..36d9b5581
--- /dev/null
+++ b/img/sds-icons/icons-tool-02.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M6 6L10.5 10.5M6 6H3L2 3L3 2L6 3V6ZM19.259 2.74101L16.6314 5.36863C16.2354 5.76465 16.0373 5.96265 15.9632 6.19098C15.8979 6.39183 15.8979 6.60817 15.9632 6.80902C16.0373 7.03735 16.2354 7.23535 16.6314 7.63137L16.8686 7.86863C17.2646 8.26465 17.4627 8.46265 17.691 8.53684C17.8918 8.6021 18.1082 8.6021 18.309 8.53684C18.5373 8.46265 18.7354 8.26465 19.1314 7.86863L21.5893 5.41072C21.854 6.05488 22 6.76039 22 7.5C22 10.5376 19.5376 13 16.5 13C16.1338 13 15.7759 12.9642 15.4298 12.8959C14.9436 12.8001 14.7005 12.7521 14.5532 12.7668C14.3965 12.7824 14.3193 12.8059 14.1805 12.8802C14.0499 12.9501 13.919 13.081 13.657 13.343L6.5 20.5C5.67157 21.3284 4.32843 21.3284 3.5 20.5C2.67157 19.6716 2.67157 18.3284 3.5 17.5L10.657 10.343C10.919 10.081 11.0499 9.95005 11.1198 9.81949C11.1941 9.68068 11.2176 9.60347 11.2332 9.44681C11.2479 9.29945 11.1999 9.05638 11.1041 8.57024C11.0358 8.22406 11 7.86621 11 7.5C11 4.46243 13.4624 2 16.5 2C17.5055 2 18.448 2.26982 19.259 2.74101ZM12.0001 14.9999L17.5 20.4999C18.3284 21.3283 19.6716 21.3283 20.5 20.4999C21.3284 19.6715 21.3284 18.3283 20.5 17.4999L15.9753 12.9753C15.655 12.945 15.3427 12.8872 15.0408 12.8043C14.6517 12.6975 14.2249 12.7751 13.9397 13.0603L12.0001 14.9999Z" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/icons-users-01.svg b/img/sds-icons/icons-users-01.svg
new file mode 100644
index 000000000..61102fccb
--- /dev/null
+++ b/img/sds-icons/icons-users-01.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M22 21V19C22 17.1362 20.7252 15.5701 19 15.126M15.5 3.29076C16.9659 3.88415 18 5.32131 18 7C18 8.67869 16.9659 10.1159 15.5 10.7092M17 21C17 19.1362 17 18.2044 16.6955 17.4693C16.2895 16.4892 15.5108 15.7105 14.5307 15.3045C13.7956 15 12.8638 15 11 15H8C6.13623 15 5.20435 15 4.46927 15.3045C3.48915 15.7105 2.71046 16.4892 2.30448 17.4693C2 18.2044 2 19.1362 2 21M13.5 7C13.5 9.20914 11.7091 11 9.5 11C7.29086 11 5.5 9.20914 5.5 7C5.5 4.79086 7.29086 3 9.5 3C11.7091 3 13.5 4.79086 13.5 7Z" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/icons-wallet-02.svg b/img/sds-icons/icons-wallet-02.svg
new file mode 100644
index 000000000..1d48fd29d
--- /dev/null
+++ b/img/sds-icons/icons-wallet-02.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M16 8.00007V4.50073C16 3.66899 16 3.25312 15.8248 2.99755C15.6717 2.77425 15.4346 2.62257 15.1678 2.57715C14.8623 2.52517 14.4847 2.69944 13.7295 3.04799L4.85901 7.14206C4.18551 7.45291 3.84875 7.60834 3.60211 7.84939C3.38406 8.06249 3.21762 8.32262 3.1155 8.6099C3 8.93486 3 9.30575 3 10.0475V15.0001M16.5 14.5001H16.51M3 11.2001L3 17.8001C3 18.9202 3 19.4802 3.21799 19.9081C3.40973 20.2844 3.71569 20.5903 4.09202 20.7821C4.51984 21.0001 5.07989 21.0001 6.2 21.0001H17.8C18.9201 21.0001 19.4802 21.0001 19.908 20.7821C20.2843 20.5903 20.5903 20.2844 20.782 19.9081C21 19.4802 21 18.9202 21 17.8001V11.2001C21 10.08 21 9.51992 20.782 9.09209C20.5903 8.71577 20.2843 8.40981 19.908 8.21806C19.4802 8.00007 18.9201 8.00007 17.8 8.00007L6.2 8.00007C5.0799 8.00007 4.51984 8.00007 4.09202 8.21806C3.7157 8.40981 3.40973 8.71577 3.21799 9.09209C3 9.51991 3 10.08 3 11.2001ZM17 14.5001C17 14.7762 16.7761 15.0001 16.5 15.0001C16.2239 15.0001 16 14.7762 16 14.5001C16 14.2239 16.2239 14.0001 16.5 14.0001C16.7761 14.0001 17 14.2239 17 14.5001Z" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/icons-x-close.svg b/img/sds-icons/icons-x-close.svg
new file mode 100644
index 000000000..7ec3c4e4e
--- /dev/null
+++ b/img/sds-icons/icons-x-close.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M18 6L6 18M6 6L18 18" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/icons-zap.svg b/img/sds-icons/icons-zap.svg
new file mode 100644
index 000000000..8af718086
--- /dev/null
+++ b/img/sds-icons/icons-zap.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="currentColor"><path d="M13 2L4.09346 12.6879C3.74465 13.1064 3.57024 13.3157 3.56758 13.4925C3.56526 13.6461 3.63373 13.7923 3.75326 13.8889C3.89075 14 4.16318 14 4.70803 14H12L11 22L19.9065 11.3121C20.2554 10.8936 20.4298 10.6843 20.4324 10.5075C20.4347 10.3539 20.3663 10.2077 20.2467 10.1111C20.1093 10 19.8368 10 19.292 10H12L13 2Z" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/logos-discord.svg b/img/sds-icons/logos-discord.svg
new file mode 100644
index 000000000..d842bfe94
--- /dev/null
+++ b/img/sds-icons/logos-discord.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg"><g clip-path="url(#clip0_2079_929)"><path d="M20.317 4.36979C18.761 3.65555 17.119 3.14623 15.4319 2.85459C15.4166 2.85173 15.4007 2.85378 15.3867 2.86044C15.3726 2.8671 15.3609 2.87803 15.3534 2.89169C15.1424 3.26699 14.9087 3.75649 14.7451 4.14119C12.9004 3.86499 11.0651 3.86499 9.2583 4.14119C9.0947 3.74789 8.8525 3.26699 8.6406 2.89169C8.63276 2.87835 8.62107 2.86768 8.60706 2.86108C8.59306 2.85448 8.57739 2.85225 8.5621 2.85469C6.87488 3.14566 5.2327 3.65493 3.6769 4.36969C3.66359 4.37538 3.65238 4.38506 3.6448 4.39739C0.533404 9.04579 -0.318996 13.5799 0.099204 18.0578C0.100386 18.0688 0.103757 18.0794 0.109116 18.089C0.114476 18.0986 0.121714 18.1071 0.130404 18.1139C2.1832 19.6215 4.1717 20.5367 6.1233 21.1433C6.13848 21.1478 6.15468 21.1476 6.16972 21.1427C6.18477 21.1377 6.19795 21.1283 6.2075 21.1157C6.6691 20.4853 7.0806 19.8205 7.4335 19.1215C7.43835 19.1119 7.44112 19.1014 7.44163 19.0907C7.44213 19.08 7.44036 19.0693 7.43643 19.0593C7.4325 19.0493 7.4265 19.0403 7.41883 19.0328C7.41115 19.0253 7.40198 19.0195 7.3919 19.0158C6.7391 18.7682 6.1176 18.4663 5.5197 18.1235C5.5088 18.1171 5.49964 18.1081 5.49304 18.0973C5.48643 18.0865 5.48258 18.0743 5.48183 18.0617C5.48108 18.049 5.48345 18.0364 5.48873 18.0249C5.49401 18.0135 5.50204 18.0034 5.5121 17.9958C5.6379 17.9015 5.7638 17.8035 5.8839 17.7044C5.89458 17.6956 5.9075 17.6899 5.92121 17.6881C5.93492 17.6862 5.94887 17.6882 5.9615 17.6939C9.8893 19.4872 14.1415 19.4872 18.0229 17.6939C18.0355 17.6879 18.0496 17.6856 18.0635 17.6873C18.0774 17.6889 18.0906 17.6945 18.1014 17.7034C18.2216 17.8024 18.3474 17.9015 18.4742 17.9958C18.4843 18.0034 18.4924 18.0133 18.4977 18.0247C18.5031 18.0362 18.5055 18.0487 18.5049 18.0613C18.5042 18.074 18.5005 18.0862 18.494 18.097C18.4875 18.1078 18.4784 18.1169 18.4676 18.1234C17.8695 18.4727 17.2429 18.7709 16.5946 19.0148C16.5845 19.0186 16.5754 19.0246 16.5678 19.0322C16.5602 19.0398 16.5542 19.049 16.5504 19.059C16.5466 19.0691 16.5449 19.0799 16.5455 19.0906C16.5461 19.1014 16.549 19.1119 16.5539 19.1215C16.9143 19.8195 17.3258 20.4843 17.7789 21.1147C17.7882 21.1277 17.8013 21.1375 17.8164 21.1426C17.8315 21.1477 17.8478 21.148 17.8631 21.1433C19.8241 20.5366 21.8126 19.6214 23.8654 18.1139C23.8742 18.1074 23.8816 18.0992 23.887 18.0897C23.8924 18.0801 23.8957 18.0696 23.8967 18.0587C24.3971 12.8817 23.0585 8.38479 20.3482 4.39829C20.3416 4.38534 20.3305 4.37529 20.317 4.36979ZM8.02 15.3312C6.8375 15.3312 5.8631 14.2455 5.8631 12.9122C5.8631 11.579 6.8186 10.4933 8.0201 10.4933C9.2309 10.4933 10.1958 11.5885 10.1769 12.9123C10.1769 14.2455 9.2214 15.3312 8.02 15.3312ZM15.9948 15.3312C14.8123 15.3312 13.8379 14.2455 13.8379 12.9122C13.8379 11.579 14.7933 10.4933 15.9948 10.4933C17.2056 10.4933 18.1705 11.5885 18.1516 12.9123C18.1516 14.2455 17.2056 15.3312 15.9948 15.3312Z" fill="var(--sds-logo-fill, #8F8F8F)"/></g><defs><clipPath id="clip0_2079_929"><rect width="24" height="24" fill="white"/></clipPath></defs></svg>
\ No newline at end of file
diff --git a/img/sds-icons/logos-linkedin.svg b/img/sds-icons/logos-linkedin.svg
new file mode 100644
index 000000000..b77583ac4
--- /dev/null
+++ b/img/sds-icons/logos-linkedin.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg"><g clip-path="url(#clip0_2079_550)"><path d="M20.447 20.452H16.893V14.883C16.893 13.555 16.866 11.846 15.041 11.846C13.188 11.846 12.905 13.291 12.905 14.785V20.452H9.351V9H12.765V10.561H12.811C13.288 9.661 14.448 8.711 16.181 8.711C19.782 8.711 20.448 11.081 20.448 14.166L20.447 20.452ZM5.337 7.433C4.193 7.433 3.274 6.507 3.274 5.368C3.274 4.23 4.194 3.305 5.337 3.305C6.477 3.305 7.401 4.23 7.401 5.368C7.401 6.507 6.476 7.433 5.337 7.433ZM7.119 20.452H3.555V9H7.119V20.452ZM22.225 0H1.771C0.792 0 0 0.774 0 1.729V22.271C0 23.227 0.792 24 1.771 24H22.222C23.2 24 24 23.227 24 22.271V1.729C24 0.774 23.2 0 22.222 0H22.225Z" fill="var(--sds-logo-fill, #8F8F8F)"/></g><defs><clipPath id="clip0_2079_550"><rect width="24" height="24" fill="white"/></clipPath></defs></svg>
\ No newline at end of file
diff --git a/img/sds-icons/logos-x-twitter.svg b/img/sds-icons/logos-x-twitter.svg
new file mode 100644
index 000000000..70f941404
--- /dev/null
+++ b/img/sds-icons/logos-x-twitter.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M18.901 1.15308H22.581L14.541 10.3431L24 22.8461H16.594L10.794 15.2621L4.156 22.8461H0.474L9.074 13.0161L0 1.15408H7.594L12.837 8.08608L18.901 1.15308ZM17.61 20.6441H19.649L6.486 3.24008H4.298L17.61 20.6441Z" fill="var(--sds-logo-fill, #8F8F8F)"/></svg>
\ No newline at end of file
diff --git a/img/sds-icons/logos-youtube.svg b/img/sds-icons/logos-youtube.svg
new file mode 100644
index 000000000..411af0b00
--- /dev/null
+++ b/img/sds-icons/logos-youtube.svg
@@ -0,0 +1 @@
+<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M23.498 6.18592C23.3624 5.6752 23.095 5.20906 22.7226 4.83419C22.3502 4.45931 21.8858 4.18886 21.376 4.04992C19.505 3.54492 12 3.54492 12 3.54492C12 3.54492 4.495 3.54492 2.623 4.04992C2.11341 4.18911 1.64929 4.45966 1.27708 4.8345C0.904861 5.20935 0.637591 5.67536 0.502 6.18592C0 8.06992 0 11.9999 0 11.9999C0 11.9999 0 15.9299 0.502 17.8139C0.637586 18.3246 0.904975 18.7908 1.27739 19.1657C1.64981 19.5405 2.11418 19.811 2.624 19.9499C4.495 20.4549 12 20.4549 12 20.4549C12 20.4549 19.505 20.4549 21.377 19.9499C21.8869 19.8111 22.3513 19.5407 22.7237 19.1658C23.0961 18.7909 23.3635 18.3247 23.499 17.8139C24 15.9299 24 11.9999 24 11.9999C24 11.9999 24 8.06992 23.498 6.18592ZM9.545 15.5679V8.43192L15.818 11.9999L9.545 15.5679Z" fill="var(--sds-logo-fill, #8F8F8F)"/></svg>
\ No newline at end of file
diff --git a/static/img/docusaurus/flutter-dark.png b/img/wallet/flutter-dark.png
similarity index 100%
rename from static/img/docusaurus/flutter-dark.png
rename to img/wallet/flutter-dark.png
diff --git a/static/img/docusaurus/flutter.png b/img/wallet/flutter.png
similarity index 100%
rename from static/img/docusaurus/flutter.png
rename to img/wallet/flutter.png
diff --git a/static/img/docusaurus/kt-dark.png b/img/wallet/kt-dark.png
similarity index 100%
rename from static/img/docusaurus/kt-dark.png
rename to img/wallet/kt-dark.png
diff --git a/static/img/docusaurus/kt.png b/img/wallet/kt.png
similarity index 100%
rename from static/img/docusaurus/kt.png
rename to img/wallet/kt.png
diff --git a/static/img/docusaurus/swift-dark.png b/img/wallet/swift-dark.png
similarity index 100%
rename from static/img/docusaurus/swift-dark.png
rename to img/wallet/swift-dark.png
diff --git a/static/img/docusaurus/swift.png b/img/wallet/swift.png
similarity index 100%
rename from static/img/docusaurus/swift.png
rename to img/wallet/swift.png
diff --git a/static/img/docusaurus/ts.png b/img/wallet/ts.png
similarity index 100%
rename from static/img/docusaurus/ts.png
rename to img/wallet/ts.png
diff --git a/index.mdx b/index.mdx
new file mode 100644
index 000000000..3d0576439
--- /dev/null
+++ b/index.mdx
@@ -0,0 +1,420 @@
+---
+mode: "custom"
+title: "Welcome"
+description: "Build on Stellar with guides, APIs, tools, and platform docs for apps, smart contracts, tokens, data, and network infrastructure."
+---
+
+export const HeroDotBackground = () => {
+  const canvasRef = useRef(null)
+
+useEffect(() => {
+if (typeof window === "undefined") return
+
+    const canvas = canvasRef.current
+    if (!canvas) return
+
+    const context = canvas.getContext("2d")
+    if (!context) return
+
+    const desktopPoints = [
+      { x: 0.06, y: 0.84 },
+      { x: 0.28, y: 0.5 },
+      { x: 0.56, y: 0.16 },
+    ]
+    const mobilePoints = [
+      { x: 0.1, y: 0.82 },
+      { x: 0.32, y: 0.56 },
+    ]
+    const lightDotColor = "#7D73B2"
+    const darkDotColor = "#FFDA00"
+    const clamp = (value, min, max) => Math.min(Math.max(value, min), max)
+    const lerp = (start, end, progress) => start + (end - start) * progress
+    const getBasePoints = (width) =>
+      width < 768 ? mobilePoints : desktopPoints
+    const getJitteredPoints = (points, width) => {
+      const spread = width < 768 ? 0.05 : 0.09
+
+      return points.map((point) => ({
+        x: clamp(point.x + (Math.random() - 0.5) * spread * 2, 0, 1),
+        y: clamp(point.y + (Math.random() - 0.5) * spread * 2, 0, 1),
+      }))
+    }
+    const isDarkMode = () =>
+      document.documentElement.classList.contains("dark") ||
+      document.documentElement.getAttribute("data-theme") === "dark"
+
+    let frameId = 0
+    let timeoutId = 0
+    let animationStart = 0
+    let width = 0
+    let height = 0
+    let currentPoints = getBasePoints(window.innerWidth)
+    let startPoints = currentPoints
+    let endPoints = currentPoints
+    let reducedMotion = false
+
+    const motionQuery = window.matchMedia("(prefers-reduced-motion: reduce)")
+    const syncReducedMotion = () => {
+      reducedMotion = motionQuery.matches
+    }
+
+    const draw = (points) => {
+      if (!width || !height) return
+
+      const limitedWidth = Math.min(width, 1440)
+      const offsetX = (width - limitedWidth) / 2
+      const dropOff = width < 768 ? 260 : 500
+      const spacing = width < 768 ? 12 : 10
+      const baseRadius = width < 768 ? 3.4 : 4
+
+      context.clearRect(0, 0, width, height)
+      context.fillStyle = isDarkMode() ? darkDotColor : lightDotColor
+      context.globalAlpha = isDarkMode() ? 0.18 : 0.32
+
+      const mappedPoints = points.map((point) => ({
+        x: offsetX + point.x * limitedWidth,
+        y: point.y * height,
+      }))
+
+      for (let x = -20; x <= width + 20; x += spacing) {
+        for (let y = -20; y <= height + 20; y += spacing) {
+          let scale = 0
+
+          mappedPoints.forEach((point) => {
+            const dx = x - point.x
+            const dy = y - point.y
+            const distance = Math.sqrt(dx * dx + dy * dy)
+            const pointScale = Math.pow(
+              1 - Math.min(distance / dropOff, 1),
+              0.4
+            )
+
+            scale = Math.max(scale, pointScale)
+          })
+
+          if (scale <= 0.02) continue
+
+          context.beginPath()
+          context.arc(x, y, baseRadius * scale, 0, Math.PI * 2)
+          context.fill()
+        }
+      }
+    }
+
+    const resizeCanvas = () => {
+      const rect = canvas.getBoundingClientRect()
+      width = rect.width
+      height = rect.height
+
+      const dpr = window.devicePixelRatio || 1
+      canvas.width = Math.round(width * dpr)
+      canvas.height = Math.round(height * dpr)
+      context.setTransform(dpr, 0, 0, dpr, 0, 0)
+
+      currentPoints = getBasePoints(width).map((point) => ({ ...point }))
+      startPoints = currentPoints.map((point) => ({ ...point }))
+      endPoints = getJitteredPoints(currentPoints, width)
+      draw(currentPoints)
+    }
+
+    const animateToNextState = (timestamp) => {
+      if (!animationStart) animationStart = timestamp
+
+      const progress = Math.min((timestamp - animationStart) / 1200, 1)
+      currentPoints = startPoints.map((point, index) => ({
+        x: lerp(point.x, endPoints[index].x, progress),
+        y: lerp(point.y, endPoints[index].y, progress),
+      }))
+
+      draw(currentPoints)
+
+      if (progress < 1) {
+        frameId = window.requestAnimationFrame(animateToNextState)
+        return
+      }
+
+      animationStart = 0
+      startPoints = currentPoints.map((point) => ({ ...point }))
+      endPoints = getJitteredPoints(currentPoints, width)
+      timeoutId = window.setTimeout(() => {
+        frameId = window.requestAnimationFrame(animateToNextState)
+      }, 140)
+    }
+
+    const startAnimation = () => {
+      window.clearTimeout(timeoutId)
+      window.cancelAnimationFrame(frameId)
+      animationStart = 0
+
+      if (reducedMotion) {
+        currentPoints = getBasePoints(width).map((point) => ({ ...point }))
+        draw(currentPoints)
+        return
+      }
+
+      startPoints = currentPoints.map((point) => ({ ...point }))
+      endPoints = getJitteredPoints(currentPoints, width)
+      frameId = window.requestAnimationFrame(animateToNextState)
+    }
+
+    const handleMotionChange = () => {
+      syncReducedMotion()
+      startAnimation()
+    }
+
+    syncReducedMotion()
+
+    const resizeObserver = new ResizeObserver(() => {
+      resizeCanvas()
+      startAnimation()
+    })
+    resizeObserver.observe(canvas)
+
+    const themeObserver = new MutationObserver(() => {
+      draw(currentPoints)
+    })
+    themeObserver.observe(document.documentElement, {
+      attributes: true,
+      attributeFilter: ["class", "data-theme"],
+    })
+
+    if (motionQuery.addEventListener) {
+      motionQuery.addEventListener("change", handleMotionChange)
+    } else {
+      motionQuery.addListener(handleMotionChange)
+    }
+
+    resizeCanvas()
+    startAnimation()
+
+    return () => {
+      window.clearTimeout(timeoutId)
+      window.cancelAnimationFrame(frameId)
+      resizeObserver.disconnect()
+      themeObserver.disconnect()
+
+      if (motionQuery.removeEventListener) {
+        motionQuery.removeEventListener("change", handleMotionChange)
+      } else {
+        motionQuery.removeListener(handleMotionChange)
+      }
+    }
+
+}, [])
+
+return (
+
+<canvas
+      ref={canvasRef}
+      aria-hidden="true"
+      className="pointer-events-none absolute inset-0 h-full w-full"
+    />
+)
+}
+
+<section className="relative isolate overflow-hidden bg-white py-24 text-neutral-950 dark:bg-neutral-950 dark:text-white sm:py-28">
+  <div
+    aria-hidden="true"
+    className="stellar-hero-base pointer-events-none absolute inset-0 dark:hidden"
+  />
+  <div
+    aria-hidden="true"
+    className="stellar-hero-base-dark pointer-events-none absolute inset-0 hidden dark:block"
+  />
+  <HeroDotBackground />
+  <div
+    aria-hidden="true"
+    className="stellar-hero-wash-light pointer-events-none absolute inset-0 dark:hidden"
+  />
+  <div
+    aria-hidden="true"
+    className="stellar-hero-wash-dark pointer-events-none absolute inset-0 hidden dark:block"
+  />
+  <div className="relative z-10 mx-auto max-w-7xl px-4 sm:px-6 lg:px-8">
+    <div className="mx-auto max-w-4xl text-center">
+      <h1 className="mx-auto max-w-4xl text-4xl font-medium tracking-tight text-neutral-950 dark:text-white sm:text-5xl lg:text-6xl">
+        Build blockchain apps, payments, and smart contracts on Stellar
+      </h1>
+      <p className="mx-auto mt-6 max-w-3xl text-base leading-7 text-neutral-700 dark:text-neutral-300 sm:text-lg lg:text-xl">
+        Explore end-to-end guides, API references, developer tools, network
+        docs, and production platforms for building on Stellar with confidence.
+      </p>
+      <div className="mt-8 flex flex-wrap justify-center gap-4">
+        <a
+          href="/docs/build"
+          className="stellar-accent-button inline-flex items-center justify-center rounded-lg px-6 py-3 text-sm font-semibold transition"
+        >
+          Start Building
+        </a>
+        <a
+          href="/docs/tools/quickstart"
+          className="stellar-accent-outline-button inline-flex items-center justify-center rounded-lg border px-6 py-3 text-sm font-semibold transition"
+        >
+          Run Quickstart
+        </a>
+      </div>
+    </div>
+  </div>
+</section>
+
+<section className="mx-auto mt-16 max-w-7xl px-4 sm:px-6 lg:px-8">
+  <div>
+    <h2 className="text-3xl font-bold tracking-tight text-neutral-950 dark:text-white sm:text-4xl">
+      Quick Start
+    </h2>
+    <p className="mt-3 max-w-3xl text-base text-neutral-600 dark:text-neutral-300">
+      Get a working Stellar development flow in place, fund a test account, and choose the track that fits your product.
+    </p>
+  </div>
+
+  <div className="mt-8">
+    <Steps>
+      <Step title="Choose your local workflow">
+        Start with [Quickstart](/docs/tools/quickstart) if you want a local Stellar environment, or jump into the [Build overview](/docs/build) if you want tutorials and implementation guides first.
+
+        ```bash
+        docker run --rm -it stellar/quickstart --standalone
+        ```
+      </Step>
+      <Step title="Set up a test account">
+        Use [Stellar Lab](/docs/tools/lab/account) or Friendbot on [Testnet](/docs/networks) to create and fund an account before you test transactions, smart contracts, or wallet flows.
+
+        <Accordion title="Example Friendbot response">
+          ```json
+          {
+            "successful": true,
+            "network": "testnet",
+            "account": "G..."
+          }
+          ```
+        </Accordion>
+      </Step>
+      <Step title="Make your first call">
+        Choose an integration surface based on your use case: [RPC](/docs/data/apis/rpc) for real-time app and contract workflows, [Horizon](/docs/data/apis/horizon) for legacy integrations, or [SDKs](/docs/tools/sdks) if you want a language-specific developer experience.
+      </Step>
+      <Step title="Pick a build path">
+        Use [Smart Contract Getting Started](/docs/build/smart-contracts/getting-started), [Applications](/docs/build/apps), or [Tokens](/docs/tokens) depending on whether you are shipping onchain logic, a wallet or app, or asset issuance flows.
+      </Step>
+    </Steps>
+
+  </div>
+</section>
+
+<section className="mx-auto mt-20 max-w-7xl px-4 sm:px-6 lg:px-8">
+  <div>
+    <h2 className="text-3xl font-bold tracking-tight text-neutral-950 dark:text-white sm:text-4xl">
+      Explore Docs
+    </h2>
+    <p className="mt-3 max-w-3xl text-base text-neutral-600 dark:text-neutral-300">
+      Jump straight into the major areas of the site, from hands-on implementation to infrastructure and ecosystem services.
+    </p>
+  </div>
+
+  <div className="mt-8">
+    <CardGroup cols={3}>
+      <Card
+        title="Access Data and APIs"
+        img="https://cdn.sanity.io/images/e2r40yh6/production-i18n/50d150dfafbb3f434727f8b5c484674660ef0893-2476x1394.png?w=1224&h=689&auto=format&dpr=2"
+        href="/docs/data"
+        cta="Explore data"
+      >
+        Use RPC, Horizon, analytics, and indexer documentation to retrieve network data, submit transactions, and power applications.
+      </Card>
+            <Card
+        title="Build on Stellar"
+        img="https://cdn.sanity.io/images/e2r40yh6/production-i18n/df267cb064df1eb9d6a66e523a6f3df144934352-2048x1536.png?rect=0,192,2048,1153&w=1224&h=689&auto=format&dpr=2"
+        href="/docs/build"
+        cta="Start building"
+      >
+        Go from first prototype to production with smart contract tutorials, application guides, and task-focused implementation docs.
+      </Card>
+      <Card
+        title="Operate and Integrate"
+        img="https://cdn.sanity.io/images/e2r40yh6/production-i18n/5e7c99582a29b90706ca1ef6b52e5043005377c9-2476x1394.png?w=1224&h=689&auto=format&dpr=2"
+        href="/docs/platforms"
+        cta="View platforms"
+      >
+        Find platform docs, developer tools, network references, and validator guidance for running Stellar in real-world environments.
+      </Card>
+    </CardGroup>
+  </div>
+</section>
+
+<section className="mx-auto mt-20 max-w-7xl px-4 sm:px-6 lg:px-8">
+  <div>
+    <h2 className="text-3xl font-bold tracking-tight text-neutral-950 dark:text-white sm:text-4xl">
+      Popular Paths
+    </h2>
+    <p className="mt-3 max-w-3xl text-base text-neutral-600 dark:text-neutral-300">
+      Start with curated entry points for common Stellar product and infrastructure workflows.
+    </p>
+  </div>
+
+  <div className="mt-8">
+    <CardGroup cols={2}>
+      <Card title="Ship a Smart Contract" icon="cube" href="/docs/build/smart-contracts/getting-started" cta="Start contracts">
+        Install the toolchain, compile Wasm, deploy to Testnet, and learn the contract model from the ground up.
+      </Card>
+      <Card title="Build an App or Wallet" icon="mobile-screen" href="/docs/build/apps" cta="Start apps">
+        Explore frontend, wallet, passkey, and example-app documentation to assemble a complete user experience.
+      </Card>
+      <Card title="Integrate Real-Time Data" icon="bolt" href="/docs/data/apis/rpc" cta="Use RPC">
+        Use Stellar RPC for transaction submission, simulation, event retrieval, and contract-related app workflows.
+      </Card>
+      <Card title="Issue and Manage Assets" icon="wallet" href="/docs/tokens/how-to-issue-an-asset" cta="Issue assets">
+        Walk through asset issuance, trustlines, distribution, and publishing asset metadata for discoverability.
+      </Card>
+    </CardGroup>
+  </div>
+</section>
+
+<section className="mx-auto mt-20 max-w-7xl px-4 sm:px-6 lg:px-8">
+  <div>
+    <h2 className="text-3xl font-bold tracking-tight text-neutral-950 dark:text-white sm:text-4xl">
+      Resources
+    </h2>
+    <p className="mt-3 max-w-3xl text-base text-neutral-600 dark:text-neutral-300">
+      Get help, stay current, and connect with the broader Stellar developer ecosystem.
+    </p>
+  </div>
+
+  <div className="mt-8">
+    <CardGroup cols={3}>
+      <Card title="Discord Community" icon="message" href="https://discord.com/invite/zVYdY3ktTn" cta="Join Discord">
+        Ask implementation questions, follow ecosystem conversations, and connect with other Stellar builders.
+      </Card>
+      <Card title="Stellar Blog" icon="newspaper" href="https://stellar.org/blog" cta="Read updates">
+        Keep up with release notes, ecosystem announcements, and platform updates from the Stellar team.
+      </Card>
+      <Card title="Developer Tools" icon="toolbox" href="/docs/tools/developer-tools" cta="Browse tools">
+        Discover IDEs, explorers, analytics services, wallets, and other tools used across the ecosystem.
+      </Card>
+    </CardGroup>
+  </div>
+</section>
+
+<section className="mx-auto mt-20 max-w-7xl px-4 pb-16 sm:px-6 lg:px-8">
+  <div className="stellar-accent-panel rounded-3xl p-8">
+    <h2 className="text-3xl font-bold tracking-tight text-neutral-950 dark:text-white sm:text-4xl">
+      Ready to build on Stellar?
+    </h2>
+    <p className="mt-3 max-w-3xl text-base text-neutral-700 dark:text-neutral-300">
+      Start with a local network, walk through a first integration, and use the
+      docs as your reference all the way to production deployment.
+    </p>
+    <div className="mt-8 flex flex-wrap gap-4">
+      <a
+        href="/docs/tools/quickstart"
+        className="stellar-accent-button inline-flex items-center justify-center rounded-lg px-6 py-3 text-sm font-semibold transition"
+      >
+        Open Quickstart
+      </a>
+      <a
+        href="/docs/build/smart-contracts/getting-started"
+        className="stellar-accent-outline-button inline-flex items-center justify-center rounded-lg border px-6 py-3 text-sm font-semibold transition"
+      >
+        Smart Contract Guide
+      </a>
+    </div>
+  </div>
+</section>
diff --git a/lab-saved-title-links.js b/lab-saved-title-links.js
new file mode 100644
index 000000000..2a56fd653
--- /dev/null
+++ b/lab-saved-title-links.js
@@ -0,0 +1,81 @@
+
+(function () {
+  "use strict";
+
+  if (typeof window === "undefined" || typeof document === "undefined") return;
+
+  // Only these pages get a linked h1, matching developers.stellar.org.
+  var TITLE_LINKS = {
+    "/docs/tools/lab/saved/keypairs": "https://lab.stellar.org/account/saved",
+    "/docs/tools/lab/saved/transactions": "https://lab.stellar.org/transaction/saved",
+    "/docs/tools/lab/saved/requests": "https://lab.stellar.org/endpoints/saved",
+  };
+  var LINKED_ATTR = "data-lab-title-link";
+
+  function currentHref() {
+    var path = window.location.pathname.replace(/\/+$/, "");
+    return Object.prototype.hasOwnProperty.call(TITLE_LINKS, path)
+      ? TITLE_LINKS[path]
+      : null;
+  }
+
+  function titleEl() {
+    return document.getElementById("page-title") || document.querySelector("header h1");
+  }
+
+  // Mintlify reuses the h1 across client-side navigations, so we never wrap its
+  // React-owned text in an <a>; we only toggle attributes, and strip them on
+  // any page that is not in TITLE_LINKS.
+  function sync() {
+    var href = currentHref();
+    var linked = document.querySelectorAll("[" + LINKED_ATTR + "]");
+    for (var i = 0; i < linked.length; i++) {
+      if (!href || linked[i] !== titleEl()) {
+        linked[i].removeAttribute(LINKED_ATTR);
+        linked[i].removeAttribute("role");
+        linked[i].removeAttribute("tabindex");
+        linked[i].removeAttribute("title");
+      }
+    }
+    if (!href) return;
+    var h1 = titleEl();
+    if (!h1 || h1.getAttribute(LINKED_ATTR) === href) return;
+    h1.setAttribute(LINKED_ATTR, href);
+    h1.setAttribute("role", "link");
+    h1.setAttribute("tabindex", "0");
+    h1.setAttribute("title", "Open in Stellar Lab");
+  }
+
+  function open(event) {
+    var h1 = event.target && event.target.closest
+      ? event.target.closest("[" + LINKED_ATTR + "]")
+      : null;
+    if (!h1) return;
+    // Re-check the route at click time so a stale attribute can never fire.
+    var href = currentHref();
+    if (!href || h1.getAttribute(LINKED_ATTR) !== href) return;
+    if (event.type === "keydown" && event.key !== "Enter") return;
+    event.preventDefault();
+    window.open(href, "_blank", "noopener,noreferrer");
+  }
+
+  document.addEventListener("click", open);
+  document.addEventListener("keydown", open);
+
+  var style = document.createElement("style");
+  style.textContent =
+    "[" + LINKED_ATTR + "]{cursor:pointer}" +
+    "[" + LINKED_ATTR + "]:hover,[" + LINKED_ATTR + "]:focus-visible{text-decoration:underline}";
+  document.head.appendChild(style);
+
+  if (document.readyState === "loading") {
+    document.addEventListener("DOMContentLoaded", sync);
+  } else {
+    sync();
+  }
+
+  new MutationObserver(sync).observe(document.documentElement, {
+    childList: true,
+    subtree: true,
+  });
+})();
diff --git a/launch/usdt0.mdx b/launch/usdt0.mdx
new file mode 100644
index 000000000..e13b6d34d
--- /dev/null
+++ b/launch/usdt0.mdx
@@ -0,0 +1,9 @@
+---
+title: "USDT0 on Stellar"
+description: "USDT0 is available on the Stellar network. How it arrives, what it unlocks, the contract addresses, and what to check before you build."
+mode: "custom"
+---
+
+import { Usdt0Launch } from "/snippets/usdt0-launch.jsx";
+
+<Usdt0Launch />
diff --git a/logo/dark.svg b/logo/dark.svg
new file mode 100644
index 000000000..2ceaa1cc5
--- /dev/null
+++ b/logo/dark.svg
@@ -0,0 +1 @@
+<svg viewBox="0 0 160 40" xmlns="http://www.w3.org/2000/svg"><g clip-path="url(#clip0_27_1534)"><path fill-rule="evenodd" clip-rule="evenodd" d="M40.6 5.23017L34.908 8.13017L7.422 22.1302C7.32906 21.4213 7.28229 20.7071 7.282 19.9922C7.28576 17.1395 8.0347 14.3374 9.45464 11.8633C10.8746 9.38919 12.9163 7.32896 15.3774 5.8867C17.8386 4.44444 20.6338 3.67018 23.4863 3.64062C26.3388 3.61106 29.1495 4.32722 31.64 5.71817L34.898 4.05817L35.384 3.81017C32.3995 1.64394 28.8741 0.345091 25.1975 0.0571559C21.521 -0.230779 17.8364 0.503418 14.551 2.1786C11.2656 3.85379 8.5074 6.40472 6.58114 9.54948C4.65488 12.6942 3.63562 16.3104 3.636 19.9982C3.636 20.5075 3.65533 21.0148 3.694 21.5202C3.74815 22.2358 3.58944 22.9514 3.23784 23.5771C2.88623 24.2027 2.35744 24.7104 1.718 25.0362L0 25.9122V29.9982L5.058 27.4202L6.696 26.5842L8.31 25.7622L37.286 10.9982L40.542 9.34017L47.272 5.91017V1.82617L40.6 5.23017ZM47.272 10L9.956 29L6.7 30.662L0 34.076V38.158L6.654 34.768L12.346 31.868L39.86 17.848C39.953 18.5616 39.9998 19.2804 40 20C39.9982 22.8559 39.2495 25.6617 37.8282 28.1388C36.4069 30.6159 34.3624 32.6782 31.8976 34.1209C29.4329 35.5637 26.6337 36.3366 23.7779 36.3631C20.9221 36.3896 18.1091 35.6687 15.618 34.272L15.418 34.378L11.886 36.178C14.8699 38.3443 18.3945 39.6435 22.0705 39.9322C25.7465 40.2208 29.4307 39.4876 32.7161 37.8135C36.0014 36.1395 38.7601 33.5898 40.6872 30.4461C42.6143 27.3025 43.6348 23.6873 43.636 20C43.636 19.486 43.616 18.972 43.578 18.464C43.5239 17.7486 43.6825 17.0332 44.0337 16.4077C44.3849 15.7821 44.9131 15.2743 45.552 14.948L47.272 14.072V10ZM93.3438 23.6699C93.3438 17.0359 97.7718 12.8359 103.48 12.8359C109.886 12.8359 113.654 18.1559 113.226 24.7959H97.1497C97.2657 29.2999 100.528 31.4739 103.596 31.4739C106.704 31.4739 108.412 30.0759 109.304 28.0179H112.954C112.022 31.5919 108.684 34.5819 103.596 34.5819C96.9937 34.5819 93.3438 29.8439 93.3438 23.6699ZM103.48 15.8639C100.372 15.8639 97.4997 17.5659 97.1878 21.7659H109.498C109.382 18.8159 107.246 15.8639 103.48 15.8639ZM71.8492 17.9181L68.5972 17.1801C65.9472 16.5961 63.9972 15.3561 63.9972 12.8701C63.9972 9.72406 67.7972 8.75406 69.9772 8.75406C72.7772 8.75406 76.0352 9.88006 76.9672 13.1021H80.8132C79.6852 7.70206 75.2132 5.41406 70.1332 5.41406C65.5892 5.41406 59.9592 7.70606 59.9592 13.1021C59.9592 17.7621 63.8032 19.9381 67.6872 20.7921L71.1972 21.5301C74.7312 22.3461 77.2552 23.5101 77.2552 26.5001C77.2552 29.3001 74.8872 31.2381 70.6932 31.2381C66.3052 31.2381 63.6652 29.2181 62.9272 25.3361H59.0352C59.7732 30.9361 63.9672 34.5781 70.6072 34.5781C76.2072 34.5781 81.3252 31.6261 81.3252 26.1501C81.3252 20.4821 76.1612 18.8501 71.8492 17.9181ZM85.3801 7.9375H88.9141V13.1795H92.8741V16.0155H88.9141V28.4035C88.9141 30.5775 89.0681 31.1215 91.0881 31.1215H92.8741V34.0715H90.3121C86.3121 34.0715 85.3801 33.1795 85.3801 28.8295V16.0155H82.0781V13.1795H85.3801V7.9375ZM158.938 13.0675C156.18 13.1835 154.084 14.4675 153.036 16.8335V13.1835H149.578V34.0755H153.112V23.1255C153.112 18.4655 154.744 16.7255 158.006 16.7255C158.669 16.7256 159.331 16.7778 159.986 16.8815V13.1055C159.638 13.0752 159.288 13.0625 158.938 13.0675ZM146.215 21.3817L146.177 26.1977C146.137 29.7257 146.293 32.0937 146.719 34.0797H143.147C142.996 33.1291 142.905 32.1698 142.875 31.2077C141.595 33.3857 139.459 34.5857 135.731 34.5857C131.809 34.5857 128.547 32.4097 128.547 28.5657C128.547 23.6257 134.139 22.1597 142.681 21.2257V20.7217C142.681 16.8777 140.585 15.6357 137.943 15.6357C134.993 15.6357 133.323 17.1897 133.167 19.7897H129.517C129.827 15.2857 133.867 12.7617 137.905 12.7617C143.769 12.7617 146.255 15.4397 146.215 21.3817ZM136.507 31.7897C139.809 31.7897 142.953 30.2737 142.953 25.3437V24.0217C136.545 24.6437 132.469 25.6137 132.469 28.4877C132.469 30.4697 133.983 31.7897 136.507 31.7897ZM119.136 5.90625H115.602V34.0742H119.136V5.90625ZM122.668 5.90625H126.202V34.0742H122.668V5.90625Z" fill="white"></path></g></svg>
\ No newline at end of file
diff --git a/logo/light.svg b/logo/light.svg
new file mode 100644
index 000000000..ff199154c
--- /dev/null
+++ b/logo/light.svg
@@ -0,0 +1 @@
+<svg viewBox="0 0 160 40" xmlns="http://www.w3.org/2000/svg"><g clip-path="url(#clip0_27_1534)"><path fill-rule="evenodd" clip-rule="evenodd" d="M40.6 5.23017L34.908 8.13017L7.422 22.1302C7.32906 21.4213 7.28229 20.7071 7.282 19.9922C7.28576 17.1395 8.0347 14.3374 9.45464 11.8633C10.8746 9.38919 12.9163 7.32896 15.3774 5.8867C17.8386 4.44444 20.6338 3.67018 23.4863 3.64062C26.3388 3.61106 29.1495 4.32722 31.64 5.71817L34.898 4.05817L35.384 3.81017C32.3995 1.64394 28.8741 0.345091 25.1975 0.0571559C21.521 -0.230779 17.8364 0.503418 14.551 2.1786C11.2656 3.85379 8.5074 6.40472 6.58114 9.54948C4.65488 12.6942 3.63562 16.3104 3.636 19.9982C3.636 20.5075 3.65533 21.0148 3.694 21.5202C3.74815 22.2358 3.58944 22.9514 3.23784 23.5771C2.88623 24.2027 2.35744 24.7104 1.718 25.0362L0 25.9122V29.9982L5.058 27.4202L6.696 26.5842L8.31 25.7622L37.286 10.9982L40.542 9.34017L47.272 5.91017V1.82617L40.6 5.23017ZM47.272 10L9.956 29L6.7 30.662L0 34.076V38.158L6.654 34.768L12.346 31.868L39.86 17.848C39.953 18.5616 39.9998 19.2804 40 20C39.9982 22.8559 39.2495 25.6617 37.8282 28.1388C36.4069 30.6159 34.3624 32.6782 31.8976 34.1209C29.4329 35.5637 26.6337 36.3366 23.7779 36.3631C20.9221 36.3896 18.1091 35.6687 15.618 34.272L15.418 34.378L11.886 36.178C14.8699 38.3443 18.3945 39.6435 22.0705 39.9322C25.7465 40.2208 29.4307 39.4876 32.7161 37.8135C36.0014 36.1395 38.7601 33.5898 40.6872 30.4461C42.6143 27.3025 43.6348 23.6873 43.636 20C43.636 19.486 43.616 18.972 43.578 18.464C43.5239 17.7486 43.6825 17.0332 44.0337 16.4077C44.3849 15.7821 44.9131 15.2743 45.552 14.948L47.272 14.072V10ZM93.3438 23.6699C93.3438 17.0359 97.7718 12.8359 103.48 12.8359C109.886 12.8359 113.654 18.1559 113.226 24.7959H97.1497C97.2657 29.2999 100.528 31.4739 103.596 31.4739C106.704 31.4739 108.412 30.0759 109.304 28.0179H112.954C112.022 31.5919 108.684 34.5819 103.596 34.5819C96.9937 34.5819 93.3438 29.8439 93.3438 23.6699ZM103.48 15.8639C100.372 15.8639 97.4997 17.5659 97.1878 21.7659H109.498C109.382 18.8159 107.246 15.8639 103.48 15.8639ZM71.8492 17.9181L68.5972 17.1801C65.9472 16.5961 63.9972 15.3561 63.9972 12.8701C63.9972 9.72406 67.7972 8.75406 69.9772 8.75406C72.7772 8.75406 76.0352 9.88006 76.9672 13.1021H80.8132C79.6852 7.70206 75.2132 5.41406 70.1332 5.41406C65.5892 5.41406 59.9592 7.70606 59.9592 13.1021C59.9592 17.7621 63.8032 19.9381 67.6872 20.7921L71.1972 21.5301C74.7312 22.3461 77.2552 23.5101 77.2552 26.5001C77.2552 29.3001 74.8872 31.2381 70.6932 31.2381C66.3052 31.2381 63.6652 29.2181 62.9272 25.3361H59.0352C59.7732 30.9361 63.9672 34.5781 70.6072 34.5781C76.2072 34.5781 81.3252 31.6261 81.3252 26.1501C81.3252 20.4821 76.1612 18.8501 71.8492 17.9181ZM85.3801 7.9375H88.9141V13.1795H92.8741V16.0155H88.9141V28.4035C88.9141 30.5775 89.0681 31.1215 91.0881 31.1215H92.8741V34.0715H90.3121C86.3121 34.0715 85.3801 33.1795 85.3801 28.8295V16.0155H82.0781V13.1795H85.3801V7.9375ZM158.938 13.0675C156.18 13.1835 154.084 14.4675 153.036 16.8335V13.1835H149.578V34.0755H153.112V23.1255C153.112 18.4655 154.744 16.7255 158.006 16.7255C158.669 16.7256 159.331 16.7778 159.986 16.8815V13.1055C159.638 13.0752 159.288 13.0625 158.938 13.0675ZM146.215 21.3817L146.177 26.1977C146.137 29.7257 146.293 32.0937 146.719 34.0797H143.147C142.996 33.1291 142.905 32.1698 142.875 31.2077C141.595 33.3857 139.459 34.5857 135.731 34.5857C131.809 34.5857 128.547 32.4097 128.547 28.5657C128.547 23.6257 134.139 22.1597 142.681 21.2257V20.7217C142.681 16.8777 140.585 15.6357 137.943 15.6357C134.993 15.6357 133.323 17.1897 133.167 19.7897H129.517C129.827 15.2857 133.867 12.7617 137.905 12.7617C143.769 12.7617 146.255 15.4397 146.215 21.3817ZM136.507 31.7897C139.809 31.7897 142.953 30.2737 142.953 25.3437V24.0217C136.545 24.6437 132.469 25.6137 132.469 28.4877C132.469 30.4697 133.983 31.7897 136.507 31.7897ZM119.136 5.90625H115.602V34.0742H119.136V5.90625ZM122.668 5.90625H126.202V34.0742H122.668V5.90625Z" fill="currentColor"></path></g></svg>
\ No newline at end of file
diff --git a/meetings/2024-01-18.mdx b/meetings/2024-01-18.mdx
deleted file mode 100644
index b4a223eb4..000000000
--- a/meetings/2024-01-18.mdx
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: "2024-01-18"
-authors: naman
-tags: [protocol]
----
-
-import AudioPlayer from "@site/src/components/AudioPlayer";
-
-<AudioPlayer src="https://pub-b2eaaee2bbe74d70820bacb7298958f5.r2.dev/0101802024_protocol_developer_call.mp3" />
-
-[Discord agenda thread](https://discord.com/channels/897514728459468821/1196897067445010452)
-
-1. The need for zk-enabling encryption curves like BLS12-381. [Github thread](https://github.com/stellar/rs-soroban-env/issues/779).
-1. Use cases that ecosystem is interestd in:
-   1. Excellar, i.e. folks that kicked off this conversation by submitting a [PR for BLS12-381](https://github.com/stellar/rs-soroban-env/pull/1310), wants to add a DAO-controlled oracle where the elliptical curve provides the ability to add new DAO voters
-   2. Zkbricks wants to build an L2 system for that enables secret state for arbitrary smart contracts
-   3. Skyhitz wants to use stellar for efficient compute, cost, and scalability while using zk to prove ownership of high-value assets on another chain
-   4. Use case enumeration continues in the [discord thread](https://discord.com/channels/897514728459468821/1197663875512942653).
-1. Considerations for host function implementation
-   1. Core devs questioned whether BLS12-381 was the right curve and also highlighted the need to determine the correct level of abstraction given there is a tradeoff between flexibility and efficiency. Lower level of abstraction will enable more flexibility but result in more hot loops in the wasm while a higher level of abstraction will be highly efficient but will restrict generality.
-   2. ZkBricks thought that there is a need to directly expose pairings and group operations without any level of abstraction. The space is in active development and flexibility is needed to try out new approaches and proof systems. From the point of view of crypto agility, it would be good to expose a generic interface that supports a variety of curves in the backend.
-1. Path Forward
-   1. Core devs mentioned crypto curves can be experimented locally by linking rust crates, which it turns out, had failed in the past. This will be explored and fixed.
-   2. ZkBricks and others will prototype locally and provide feedback.
-1. What are the best practices for managing transactions in the frontend, with respect to transaction ordering.
-1. Core devs confirmed that ordering is intentionally arbitrary.
-1. Request for an API for current version of the environment/sdk
-1. Github issue filed for the RPC to return versions of the current node.
diff --git a/meetings/2024-01-26.mdx b/meetings/2024-01-26.mdx
deleted file mode 100644
index f5b59353e..000000000
--- a/meetings/2024-01-26.mdx
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: "2024-01-26"
-authors: kalepail
-tags: [developer]
----
-
-import AudioPlayer from "@site/src/components/AudioPlayer";
-
-<AudioPlayer src="https://pub-b2eaaee2bbe74d70820bacb7298958f5.r2.dev/Soroban-Dev-Call-01-26-24.mp3" />
-
-[Discord agenda thread](https://discord.com/channels/897514728459468821/1199121845656486009)
-
-1. Plan and schedule for these meetings
-   1. Protocol meetings every other Thursday at 4pm ET
-   2. Developer meetings every other Friday at 1pm ET
-   3. Will continue to adjust as needed
-2. Fee bump bug - [announcement](https://stellar.org/blog/developers/fee-bump-bug-disclosure) | [discussion thread](https://discord.com/channels/897514728459468821/1200432249594707998/1200432306314281000)
-   1. Fee sponsorship bug: unused fee is refunded to the inner tx source rather than the sponsor source.
-   2. Fix in new release. Up to the ecosystem and validators to upgrade. The fix will likely be rolled out before Phase 2.
-   3. Up to validators to determine if they’d like to push the v20 upgrade date to wait for the fix; or upgrade with current release.
-3. TxMeta Deprecation in Horizon - [announcement](https://discord.com/channels/897514728459468821/900374272751591424/1199438109796999298)
-4. Ideas around testing against ledger snapshots - [request](https://discord.com/channels/897514728459468821/1199121845656486009/1199158421254049912)
-   1. Define the needs a bit more clearly
-   2. Definitely something here we should be addressing to make testing against specific ledger state easier
-5. How do you get a list of smart contracts? - [thread](https://discord.com/channels/897514728459468821/1199121845656486009/1199739331078803496)
-   1. Observe create contract ops as ledgers close
-   2. Use an [indexing service](/docs/data/indexers)
-6. What is the status of contracts caching support? - [question](https://discord.com/channels/897514728459468821/1199121845656486009/1200484710447587490)
-   1. [response](https://discord.com/channels/897514728459468821/1199121845656486009/1200516877680644276)
diff --git a/meetings/2024-02-01.mdx b/meetings/2024-02-01.mdx
deleted file mode 100644
index 7411b1174..000000000
--- a/meetings/2024-02-01.mdx
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title: "2024-02-01"
-authors: naman
-tags: [protocol]
----
-
-import AudioPlayer from "@site/src/components/AudioPlayer";
-
-<AudioPlayer src="https://pub-b2eaaee2bbe74d70820bacb7298958f5.r2.dev/Stellar-Protocol-Meeting-02-01-2024.mp3" />
-
-[Discord agenda thread](https://discord.com/channels/897514728459468821/1201979721211203614)
-
-1. The proposal is to advance stellar-core by adding a host function to verify the secp256r1 signature, which is the most common elliptic curve used outside of the blockchain space. It is useful in connecting off-chain authentication interfaces with on-chain functionality.
-1. Note that the proposal is not for a new signer type but a host function.
-1. Leigh investigated adding support for the WebAuthN use case, by allowing a custom account / smart contract to sign soroban auth entries using a secp256r1-signed payload.
-1. secp256r1 is supported by phones, passkeys, and enables an app to replace passwords. This is a massive benefit to user-facing applications like wallets.
-1. Pros and cons of the interface: blockchains generally implement the recovery interface over the verification interface but verification is easier for developers as it reduces burden on the client and the network.
-1. The WebAuthN use case requires encoding and decoding of base64 payloads and decoding JSON blobs, which is not currently supported in Soroban.
-1. While there are hacky ways of accomplishing the latter, it’s not a great developer experience and final implementation is susceptible to breakages on updates.
-1. It is also costly to bundle decoding with verification in guest.
-1. Soroban has always led with a batteries included mindset. Keeping in line with that approach, it makes sense to further investigate and determine whether a host function makes sense for these as well.
-1. Leigh’s implementation may require further evaluation of the crates used for ecdsa and p256.
-1. Brief discussion around proposed process for adding of a host function by a non-core dev.
diff --git a/meetings/2024-02-08.mdx b/meetings/2024-02-08.mdx
deleted file mode 100644
index 3a530ba35..000000000
--- a/meetings/2024-02-08.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: "2024-02-08"
-authors: kalepail
-tags: [developer]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1Hgp8K_XDeq4yaON3TWeHDtQTAyVR1crY" />
-
-[Discord agenda thread](https://discord.com/channels/897514728459468821/1204462856037470248)
-
-1. Stellar Asset List (SEP-42) draft presentation by [OrbitLens](https://github.com/orbitlens)
-   1. [SEP draft](https://github.com/orbitlens/stellar-protocol/blob/sep-0042-token-lists/ecosystem/sep-0042.md)
-   2. [Discord discussion](https://discord.com/channels/897514728459468821/1162558946867953704)
-2. Stellar + Soroban documentation survey
-   1. [Take the survey](https://discord.com/channels/897514728459468821/1204462856037470248/1205196745877757962)
diff --git a/meetings/2024-02-15.mdx b/meetings/2024-02-15.mdx
deleted file mode 100644
index 3001295e3..000000000
--- a/meetings/2024-02-15.mdx
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: "2024-02-15"
-authors: naman
-tags: [protocol]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1oBuYg_LvGRGnKpjezok6PQGVN8ZpqVvy" />
-
-[Discord agenda thread](https://discord.com/channels/897514728459468821/1207385360116490360)
-
-1. The meeting was focused on the process of adding host functions, using WebAuthN as the example use case; continued from the previous meeting.
-2. Discussion of remaining concerns with adding secp256r1 verification host function from previous meeting.
-   - What does it mean for secp256r1 to be added as a host function vs. as a signer type?
-     - As a host function, user can sign soroban auth entries. Need another stellar account to fund and submit tx to the chain. The latter can be done by a stellar account which may be operated by a wallet or a contract.
-     - \_\_check_auth is invoked when the contract being interacted with calls require_auth
-3. CAP-52 was drafted to introduce encoding/decoding functions for Base64, which is needed by WebAuthN. Considerations discussed in the meeting:
-   - Performance: 1066 bytes that costs 1M instr to encode a 32byte hash; so the cost is very small and it’s questionable whether a host function is required.
-   - Interface required two functions (encode/decode)
-   - Implementation wise, WebAuthN requires url alphabet and padding, which decoder likely needs to support. Should we use symbols or ints? Do we need custom alphabets?
-   - Do we really need more encoding schemes? Isn’t XDR enough?
-   - Expensive auth mechanisms, i.e. webauthn, cannot be coupled with contracts with heavy business logic (which might be a lot of contracts), thus making adoption problematic.
-   - We should probably add building blocks to enable the ecosystem to add new use cases.
-4. CAP-53 was drafted to introduce encoding/decoding functions for JSON, which is needed by WebAuthN. Considerations discussed in the meeting:
-   - Performance: 3.9Kb, 2.5M CPU instr.
-   - If the size of the input blob is unknown, execution time will increase.
-   - Valuable to have such a lightweight function that’ll be used in various place.
-   - Interface: 11 functions
-     - What to do with numbers and decimals? Add decimals and floats?
-     - We only have to extract one field for WebAuthN but what about the general case?
-   - The number type in JSON is decimal but soroban does not support that. How should this be handled?
-   - Discussion around alternative interface and implementations.
-5. Core dev concerns
-   - Maintainability: if you add a host function, you have to maintain it forever. If there are more versions, we have to keep it around.
-   - Expanded surface area for security bugs.
-   - Should define a path where core dev is not in the implementation loop, as their schedules are packed with stability work. How to prioritize against stability work, which may get derailed due to new functionality such as what’s being currently discussed.
-   - Next steps:
-     - Core team to put together a plan for adding Base64. This is an important exercise that helps determine even more challenges of doing so. The output of this exercise may be that base64 _shouldn’t_ in fact be implemented at this point.
-     - Discussion around the JSON interface is to be continued.
diff --git a/meetings/2024-02-22.mdx b/meetings/2024-02-22.mdx
deleted file mode 100644
index 576044934..000000000
--- a/meetings/2024-02-22.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: "2024-02-22"
-authors: kalepail
-tags: [developer]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1ZZm1eLe6L0ZRtpTxF77RfrLkW9ThAWh4" />
-
-[Discord agenda thread](https://discord.com/channels/897514728459468821/1209582245824823337)
-
-1. Latest and greatest on the TypeScript bindings with [@chadoh](https://github.com/chadoh)
-2. [Available RPC providers](/docs/data/apis/rpc/providers)
-3. Standing up a [`stellar-rpc` docker container](/docs/data/apis/rpc/admin-guide#docker-image)
-4. Installing and invoking a Stellar Asset Contract on mainnet in Phase 0
diff --git a/meetings/2024-02-29.mdx b/meetings/2024-02-29.mdx
deleted file mode 100644
index 73d794c3a..000000000
--- a/meetings/2024-02-29.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: "2024-02-29"
-authors: naman
-tags: [protocol]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1zKvUx74UqvfmpNvU8BJt5RAqj-XHyBke" />
-
-[Discord agenda thread](https://discord.com/channels/897514728459468821/1212118102565855243)
-
-1. Tommaso (@tdep) proposed a core change to allow for extending instance and code TTL with separate values on the host environment to allow for more cost-efficient designs a. Proposal and discussion are captured in github discussions [stellar-core#1447](https://github.com/stellar/stellar-protocol/discussions/1447)
-2. Tommaso received feedback on the proposal as well as implementation. Since it didn't require a metering change, core devs thought it to be a quick change.
-3. The ecosystem voted in favor of the proposal by upvoting the post on Github Discussions. 13 votes were [recorded](https://github.com/stellar/stellar-protocol/discussions).
-4. As next steps, a CAP will be authored to capture the proposal and put forth for approval from CAP Core Team.
diff --git a/meetings/2024-03-07.mdx b/meetings/2024-03-07.mdx
deleted file mode 100644
index a4dde75c4..000000000
--- a/meetings/2024-03-07.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: "2024-03-07"
-authors: kalepail
-tags: [developer]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1FJueTZweJPaOyno0fxHOfU3Ec2S0gvO_" />
-
-[Discord agenda thread](https://discord.com/channels/897514728459468821/911254664576643122/1215404506964172890)
-
-1. [Sorobill tool](https://github.com/kalepail/sorobill)
-2. Deploying contracts and testing invocations against the unlimited [quickstart](https://github.com/stellar/quickstart).
-3. Using Sorobil package as a tool to get a snapshot of all the limits the contract is touching. [Relevant blog post](https://kalepail.com/blockchain/show-me-the-bill-part-2)
-4. How to measure the contract costs and what limits you are touching
-5. Utilizing the Sorobil tool to decode XDR and understand failed transactions.
diff --git a/meetings/2024-03-14.mdx b/meetings/2024-03-14.mdx
deleted file mode 100644
index 7e30ba096..000000000
--- a/meetings/2024-03-14.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: "2024-03-14"
-authors: naman
-tags: [protocol]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1Gztue3zvZBQzVPshM0_Yy8ntYh7Bk33d" />
-
-[Discord agenda thread](https://discord.com/channels/897514728459468821/1217193723612368926)
-
-1. CAP Core Team deliberated over the latest proposals put forth by the Stellar ecosystem to advance stellar-core.
-2. Nicholas and David from the CAP Core Team listened to the following proposals and discussed the proposals with the authors. a. CAP Core team will deliver their vote over email.
-3. Proposals discussed:  
-   a. [CAP-51](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0051.md): add support for secp256r1 verification; by @leigh  
-   b. [CAP-53](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0053.md): create separate functions for extending the time-to-live for contract instance and contract code; by @tdep  
-   c. [CAP-54](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0054.md): lower total costs by refining the Soroban cost model used for VM instantiation into multiple separate and more-accurate costs; by @graydon  
-   d. [CAP-55](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0055.md): lower total costs by linking fewer host functions during VM instantiation in Soroban; by @graydon  
-   e. [CAP-56](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0056.md): lower total costs by caching parsed Wasm modules within a Soroban transaction; by @graydon
diff --git a/meetings/2024-03-21.mdx b/meetings/2024-03-21.mdx
deleted file mode 100644
index a0d2041b4..000000000
--- a/meetings/2024-03-21.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: "2024-03-21"
-authors: kalepail
-tags: [developer]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1vSkQFbdg80548ShpjOpyD9scnQjebkQi" />
-
-[Discord agenda thread](https://discord.com/channels/897514728459468821/1219381314931917000)
-
-1.  There's a discussion on a TX meta change increasing visibility and analytics within the Stellar network. (https://github.com/stellar/stellar-xdr/pull/175)
-2.  Read-only invocations for contracts is explained, focusing on ensuring certain functions remain read-only without side effects. (https://github.com/stellar/stellar-protocol/discussions/1454) (https://github.com/stellar/stellar-protocol/discussions/1456) (https://github.com/stellar/stellar-protocol/discussions/1464)
-3.  Enabling contract discovery is introduced to enhance the visibility and authenticity of smart contracts within the Stellar ecosystem.
-4.  The implementation of a standardized contract meta data schema is proposed to link contracts to source code and enhance contract discoverability.(https://docs.rs/soroban-sdk/latest/soroban_sdk/macro.contractmeta.html)
-5.  Issues related to inclusion fees in the Stellar network, highlighting the importance of monitoring fees closely and understanding the implications of [surge pricing](/docs/learn/fundamentals/fees-resource-limits-metering#inclusion-fee)
-6.  Plans are discussed for designing a new RPC endpoint to provide developers with better visibility and information on setting inclusion fees, aiming to improve transparency and decision-making regarding fee trade-offs.
diff --git a/meetings/2024-03-28.mdx b/meetings/2024-03-28.mdx
deleted file mode 100644
index 86ea107e6..000000000
--- a/meetings/2024-03-28.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: "2024-03-28"
-authors: naman
-tags: [protocol]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1e7AgsEAno0pZBYkICuKaqC3HMQkjWRd9" />
-
-[Agenda thread](https://github.com/stellar/stellar-protocol/discussions/1475)
-
-1. The Standards Working Group proposed changes to the SEP process that empower the ecosystem by making the current process more decentralized and ecosystem-friendly.
-2. The process has already been used for several proposals over the last three months.
-3. Esteblock from Soroswap shared their journey of participating in the proposal for Asset List ([SEP-42](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0042.md)) and implementing the proposed standard
-4. Discussion continues in the proposal doc.
-5. Next step is to get further ecosystem feedback then update the Github SEP repository with the updated SEP process.
diff --git a/meetings/2024-04-04.mdx b/meetings/2024-04-04.mdx
deleted file mode 100644
index 1891ee56a..000000000
--- a/meetings/2024-04-04.mdx
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: "2024-04-04"
-authors: naman
-tags: [developer]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-Today's recording has two parts. The first 12 minutes are audio-only. The next 45 minutes have video as well. Please note the slides were shared in discord chat over screensharing, due to technical difficulties.
-
-Part 1 (audio-only):
-
-<DriveVideo ID="14ddYFIMDgsX70hTCv8C1tKaAGmJiprw7" />
-
-Part 2 (video):
-
-<DriveVideo ID="1p4LrgGLfRdVww-7d21w3BGyPrLfiIDmF" />
-
-[Discord Agenda thread](https://discord.com/channels/897514728459468821/1224408179363024918)
-
-1. Piyal surfaced the proposal for a [Wallet Standard](https://github.com/stellar/stellar-protocol/discussions/1467) and requested feedback.
-2. Cubist, an ecosystem project, discussed CubeSigner, a low-latency API for generating keys and signing transactions inside secure hardware.
-3. Stellar-based example of CubeSigner is available in the [Cubist Labs Github repository](https://github.com/cubist-labs/CubeSigner-TypeScript-SDK/tree/main/examples/stellar)
-4. Cubist devs can be contacted via the Stellar discord or the [web form](https://cubist.dev/contact-form-cubesigner-hardware-backed-key-management).
diff --git a/meetings/2024-04-11.mdx b/meetings/2024-04-11.mdx
deleted file mode 100644
index 6d0b6cdfd..000000000
--- a/meetings/2024-04-11.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: "2024-04-11"
-authors: naman
-tags: [protocol]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1OCt2lXcrwhVyRd4dcwj8mfCOzxXON6nL" />
-
-Piyal from Freighter discussed the proposal to standardize the wallet interface. Key points from the discussion are captured below. For full notes, please view the recording; and also refer to the proposal and the post on github discussions.
-
-1. [The draft proposal](https://github.com/stellar/stellar-protocol/blob/83191be659166e05f8df1257c6f655de9d1afe63/ecosystem/sep-0043.md)
-2. [Ongoing discussion](https://github.com/stellar/stellar-protocol/discussions/1467)
-3. Requiring the network passphrase might be uneeded complexity.
-4. Both WalletConnect and mobile wallets likely have significant differences than the proposed interface (which is targetted at browser extension wallets); and thus likely require a separate SEP. The said SEPs should be created by teams working on wallet integration with the said platforms.
-5. What is the role of the Stellar Wallet Kit in the ecosystem and how does it play with the standard itself?
-6. As next steps, Piyal will incorporate the suggestions from the ecosystem into the proposal.
diff --git a/meetings/2024-04-18.mdx b/meetings/2024-04-18.mdx
deleted file mode 100644
index c27e251f5..000000000
--- a/meetings/2024-04-18.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: "2024-04-18"
-authors: kalepail
-tags: [developer]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1ZUdrK0YuF69un_KA3rJGvZaD_wmgYG8N" />
-
-[Discord agenda thread](https://discord.com/channels/897514728459468821/911254664576643122/1215404506964172890)
-
-1. Justin from [ortege.ai](https://www.ortege.ai) demo'd Ortege, a data analytics platform for Stellar and Soroban.
-2. Ortege lets anyone in the Stellar ecosystem create dashboards to track any and all desired metrics. Ortege's queries, widgets, and dashboards are shareable making it the perfect platform to surface
-3. Justin will be releasing an AI soon and enable querying and insights via natural language.
-4. All are invited to create a free account and track the success metrics for their dashboard.
diff --git a/meetings/2024-04-25.mdx b/meetings/2024-04-25.mdx
deleted file mode 100644
index d785b5551..000000000
--- a/meetings/2024-04-25.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: "2024-04-25"
-authors: naman
-tags: [protocol]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1WdZeRnjwl0FCxwtQhy2DNqMtNIiZIgtD" />
-
-1. Garand discussed changes to the State Archival proposal based on feedback received at Meridian 2023. The proposed changes are:
-
-- Previously, a downstream system called the ESS (Expired State Store) would store expired entries. In the new proposal, There is no ESS. All Archived entries, as well as all information required to generate restoration proofs for those entries, is stored directly in the History Archive.
-- RPC nodes can generate proofs for archived state during preflight
-- Captive-core can be directly queried for archived state, meaning that RPC/Horizon instances can potentially service queries for archival state
-
-2. [The draft proposal](https://docs.google.com/document/d/1FAs3Yfo-o-gVqccrP29NSG8ysRvdEoyvuL7ywV4ijXI/edit#heading=h.1xwsoyifxbfm)
-3. [Ongoing discussion](https://github.com/stellar/stellar-protocol/discussions/1480)
-4. Snapshot size is TBD; it's a function of bucket list size as well as memory and historic demands placed on the RPC.
-5. Bloom filters are the likely solution for proof of non-exitance though they come with trade-offs. They enable fast and cheap lookup but are probabilistic not deterministic.
-6. Further comments are welcome.
diff --git a/meetings/2024-05-02.mdx b/meetings/2024-05-02.mdx
deleted file mode 100644
index a79a3603f..000000000
--- a/meetings/2024-05-02.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: "2024-05-02"
-authors: naman
-tags: [developer]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1-XWdGA3vMqoMI6DqBDtjKR_DTeOImpbZ" />
-
-[Discord Agenda thread](https://discord.com/channels/897514728459468821/1234887262530048010/1234887262530048010)
-
-1. Fifo presented [Stellar Plus](https://docs.cheesecakelabs.com/stellar-plus), which is a Javascript library to simplify the Stellar and Soroban development.
-2. Ecosystem members found the design for Stellar Plus composable and encompassing of all Stellar related functionality including management of assets, accounts, wasm-related operations, as well as RPC utils.
-3. The links to Fifo's presentation and Stellar Plus are:
-   - [Miro Board showing Stellar Plus architecture](https://miro.com/app/board/uXjVKMDkMPI=/?share_link_id=643609701897)
-   - [Stellar Plus Repositore](https://discord.com/channels/897514728459468821/1234887262530048010/1235699608274079865)
-   - [Examples Repository](https://github.com/fazzatti/stellar-plus-examples)
-   - [Docs](https://docs.cheesecakelabs.com/stellar-plus)
diff --git a/meetings/2024-05-09.mdx b/meetings/2024-05-09.mdx
deleted file mode 100644
index 4ccb01f7b..000000000
--- a/meetings/2024-05-09.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: "2024-05-09"
-authors: naman
-tags: [developer]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1PvA8cxInSfRjmewJbILhgpZYv4CBExZv" />
-
-1. Tyler built a voting application using passkeys to sign the transaction, which is an implementation of the secp256r1 verification function.
-2. He showed a cross-platform implementation (web and mobile) and demonstrated that passkeys are the perfect interface between web3 contracts and web2 authentication mechanisms that most end users are accostomed to.
-3. Ecosystem members discussed the use of smart wallets that would use passkeys as a signer. Challenges were identified around fees requires for smart wallets, the need for a common implementation for a smart wallet, as well as how might it interface with existing password managers.
-4. The voting application can be tried out at [passkey.sorobanbyexample.org](https://passkey.sorobanbyexample.org)
-5. Code for the demo is here [github.com/kalepail/soroban-passkey](https://github.com/kalepail/soroban-passkey)
diff --git a/meetings/2024-06-13.mdx b/meetings/2024-06-13.mdx
deleted file mode 100644
index ab1afb5d8..000000000
--- a/meetings/2024-06-13.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: "2024-06-13"
-authors: kalepail
-tags: [developer]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1goVLHLJWWwRy1xgBpJa4VF1y9axrlIqA" />
-
-1. Tyler created Super Peach, a web3 application that uses passkeys to sign transactions. He demonstrated how passkeys can be used in authorization flows and how they can be used to sign transactions.
-   - Code: https://github.com/kalepail/superpeach
-   - Demo: https://superpeach.xyz
-2. Introduced `passkey-kit`. A TypeScript SDK for creating and managing Smart Wallets via passkeys (includes the actual [Smart Wallet interface](https://github.com/kalepail/passkey-kit/tree/main/contracts))
-   - Code: https://github.com/kalepail/passkey-kit
-   - Demo: https://passkey-kit-demo.pages.dev
-3. Introduced Launchtube, a service for submitting transactions onchain by covering both the transaction fee AND the sequence number. Wild!
-   - Code: https://github.com/kalepail/launchtube (ask in the `#passkeys` channel on Discord for a testnet token)
-4. He shared his vision for pushing the passkey implementation through to becoming a [standard for the ecosystem](https://docs.google.com/document/d/1c_Wom6eK1UpC3E7VuQZfOBCLc2d5lvqAhMN7VPieMBQ/edit).
-
-Join the `#passkeys` channel on the Discord to continue the discussion
diff --git a/meetings/2024-06-20.mdx b/meetings/2024-06-20.mdx
deleted file mode 100644
index e27c19a64..000000000
--- a/meetings/2024-06-20.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: "2024-06-20"
-authors: naman
-tags: [developer]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1nrEQdhiTH4wsQVgaiOO0RcmD-AS-5S2v" />
-
-1. [Kirckz discusses Meru](https://docs.google.com/presentation/d/1Fu4AkB0mrvOkK6UDFJHgKwCV-Ul4JRF-xPqTYJ3CQqw), a Financial services app for Freelancers and remote workers in Latin America.
-2. He shares his experience integrating Meru with Blend, a liquidity protocol primitive for Stellar.
-3. Kirckz shares the challenges faced during the integration and how they were overcome.
-4. He shares the sdks and libraries his team used to facilitate the integration.
-
-Follow Meru on X (formerly Twitter) to stay updated: https://x.com/getmeru
diff --git a/meetings/2024-06-27.mdx b/meetings/2024-06-27.mdx
deleted file mode 100644
index 524404bed..000000000
--- a/meetings/2024-06-27.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: "2024-06-27"
-authors: naman
-tags: [developer]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1PS49Cvs_DLdEwquh6c9e5JuN3MASaTpz" />
-
-1. [Chad](https://github.com/chadoh) and [Willem](https://github.com/willemneal) from [Aha Labs](https://github.com/AhaLabs) discuss the updates to the new and improved [stellar-cli](https://github.com/stellar/stellar-cli)
-2. Some highlights include the change from the name 'soroban' to 'stellar' when using the CLI tool and the addition of new commands.
-3. They cover some cool functions like local network setup, account creation, and transaction signing. with the following commands:
-   - `stellar network container [start|logs]`
-   - `stellar keys [generate|fund|ls]`
-   - `stellar contract init` to get a whole new Soroban project
-   - and so much more!
-4. They also discuss expected future updates including support for more Stellar operations and integration with Stellar Lab V2!
diff --git a/meetings/2024-07-11.mdx b/meetings/2024-07-11.mdx
deleted file mode 100644
index 3a763c41f..000000000
--- a/meetings/2024-07-11.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: "2024-07-11"
-authors: naman
-tags: [developer]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1uBv-Qv6bHzri7OeRyBJo7hxJtH6CKjEH" />
-
-1. SDF Data team gave a crash course in analysis of Stellar data, and covered how to access Hubble, tips for efficient querying, and how to get started with data exploration.
-2. [Slides](https://docs.google.com/presentation/d/1QsCwFLFcDF4RmNIwtSSnNrUfZb0RM0kLxOOxC7ENY5M/edit#slide=id.g2cb5821e4de_1_1143) are publicly available and legible async.
-3. Tips for data anlaysis are also covered in [docs](/docs/data/analytics/hubble/analyst-guide)
-4. Share your queries and post questions in #hubble in Stellar discord, which is a dedicated channel for data-related topics.
diff --git a/meetings/2024-07-18.mdx b/meetings/2024-07-18.mdx
deleted file mode 100644
index fb59f067d..000000000
--- a/meetings/2024-07-18.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: "2024-07-18"
-authors: naman
-tags: [developer]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1lml1VxNkwsRKS9BbnIMFNRXX1Kn6ktvq" />
-
-Note: the first part of the call was lost. The video posted above captures the second half of the call where various ecosystem developers shared their use cases and needs for a smart wallet on Stellar.
-
-1. Tyler put forward a [proposal](https://github.com/stellar/stellar-protocol/discussions/1499) for a smart wallet as a public good. Given that the native auth can be overloaded by using `__check_auth`, Stellar implementation of a smart wallet is fairly straightforward. The capability to customize the auth is already built into the core protocol.
-2. See the [proposal](https://github.com/stellar/stellar-protocol/discussions/1499) here and implementation [here](https://github.com/kalepail/passkey-kit/blob/main/contracts/webauthn-wallet/src/lib.rs)
-3. The proposal only uses WebAuthN-based signers i.e. passkeys. It does not use ed25519, which, perhaps it should given that ~100% of the accounts on Stellar use the scheme. It also introduces the notion of temporary and admin signers to illustrate the notion that the account can be managed by multiple signers, each with a different access policy.
-4. The biggest unlock with custom auth is the ability to execute custom logic. We heard from various ecosystem members about how might they us it. 4a. A dev is building a perpetual protocol and thought smart wallets could be used to automatically manage defi positions, which would be a significant improvement over status quo where the user has to constantly track assets to determine _when_ to execute a trade. 4b. Folks are excited about foregoing the seed phrase for passkeys, which is especially meaningful when onboarding net new users to the blockchain. 4c. Authorizing a cross-chain message from a different chain, especially programmatic authorization, requires an implementation of custom accounts. 4d. Some apps have noted that users prefer not to have a wallet but simply experience the value of the app, especially games. For this, the app may assign a temporary account to the user and control access via check_auth. 4c. Microtransactions without needing user sign is super interesting for apps as well.
-5. This has been a very insightful meeting and we learnt about how the Stellar ecosystem plans to leverage smart wallet. Let's continue the conversation in discord!
diff --git a/meetings/2024-07-25.mdx b/meetings/2024-07-25.mdx
deleted file mode 100644
index 988012b91..000000000
--- a/meetings/2024-07-25.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: "2024-07-25"
-authors: naman
-tags: [protocol]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1ScrEdoscrVQX_PzaMBCHavycg8dLpaIx" />
-
-A Core Dev, Dima, discussed the proposal to add constructor support to Soroban, Stellar's smart contract system.
-
-Relevant links: [Draft CAP](https://github.com/stellar/stellar-protocol/blob/50dde0611440d6dc562a33462e6ba5f1504b2753/core/cap-0058.md), [Ongoing discussion](https://github.com/stellar/stellar-protocol/discussions/1501), [Motivating Discord Thread](https://discord.com/channels/897514728459468821/1067534037310255225)
-
-Key points discussed:
-
-1. The proposal improves usability of Soroban for contract and SDK developers. A constructor guarantees contract initialization thus reducing overhead contract code that's usually added to ensure initialization.
-2. There was general agreement for the proposal, questions were primarily implementation-focused like whether constructors should handle arguments, what should happen with upgrades, backwards comptability with contract creation functions, and behaviour on wasm update.
-3. The high impact topic of naming is put to ecosystem vote, please cast yours [here](https://github.com/stellar/stellar-protocol/discussions/1507).
diff --git a/meetings/2024-08-01.mdx b/meetings/2024-08-01.mdx
deleted file mode 100644
index 32548befa..000000000
--- a/meetings/2024-08-01.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: "2024-08-01"
-authors: naman
-tags: [developer]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1Hog269Q96QMEJeC2DZHIMUkjMtj98YYj" />
-
-1. Piyal demonstrated that Freighter's swap functionality is now served by [Soroswap](https://soroswap.finance). It was previously served by Stellar Dex.
-2. Freighter has made integration instructions available [here](https://github.com/stellar/freighter/blob/d248f2ad0aa03da72ea6eeaf7907ac0454fdcc72/extension/INTEGRATING_SOROSWAP.MD?plain=1#L2).
-3. Esteban shared that [Palta Labs](https://paltalabs.io) has created a DEX aggregator and made it available to all via the [Router SDK](https://docs.soroswap.finance/03-technical-reference/07-optimal-route/01-soroswap-router-sdk).
-4. The Router SDK finds the optimal path for the swap in terms of swap cost across all dexes on Soroban.
diff --git a/meetings/2024-08-08.mdx b/meetings/2024-08-08.mdx
deleted file mode 100644
index 282e5cadd..000000000
--- a/meetings/2024-08-08.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "2024-08-12"
-authors: naman
-tags: [developer]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1Q6a8WpUKplujhbD6MMzrTlfjfdXFTrBd" />
-
-1. Tdep discussed Zephyr, an execution env built on top of the indexer Mercury. He also walked through examples demonstrating how Zephyr can simplify dapp development.
diff --git a/meetings/2024-08-15.mdx b/meetings/2024-08-15.mdx
deleted file mode 100644
index 3c654c2ec..000000000
--- a/meetings/2024-08-15.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: "2024-08-15"
-authors: julian
-tags: [developer]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1V5Arzh7LgWMj2E7FjZyGTFUl0vV31xll" />
-
-1. @Soiled and @Robeart from Orbit spoke about using Blend to create decentralized stablecoins for all currencies under the Orbit Protocol, utilizing a decentralized pegkeeper to maintain their price, and leveraging these stablecoins and smart wallets to create an orderbook less perpetual exchange, bringing Forex to Stellar
-
-2.[Link to the presentation](https://docs.google.com/presentation/d/1mDOrBLfe8-Bq6VCy7r5bb4w_uZjq-EOorbV3ZwYfs1k/edit?usp=sharing)
-
-_Note_: The hosts microphone audio is not in the video so there is some silence during Q/A. Here are the question asked during the Q/A:
-
-1. (From ! markus_0) why do you always have an infinite amount of tokens in the pool? Wouldn't it be safer to start small and mint more as demand opens up 2.(From HunterIonize) What purpose does this serve exactly? Sorry to be blunt
-2. How do you see the Orbit Protocol contributing to financial inclusion on a global scale, particularly in underbanked regions? What challenges do you anticipate in achieving this?
-3. In 5-10 years, how do you see the landscape of Forex on blockchain evolving? What role do you believe Stellar will play in this evolution, and how will Blend and Orbit Protocol be at the forefront?
-4. Are there any asks of the developer community?
diff --git a/meetings/2024-08-22.mdx b/meetings/2024-08-22.mdx
deleted file mode 100644
index ebca14dc4..000000000
--- a/meetings/2024-08-22.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: "2024-08-23"
-authors: naman
-tags: [protocol]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1Eqi0znJ21aSfjXYJ10V7eByhr-sTzujY" />
-
-[Discord agenda thread](https://discord.com/channels/897514728459468821/900374272751591424/1275577430043525204)
-
-Core Developers discussed the latest proposals to advance Stellar Core in this week's Protocol Meeting.
-
-1. The proposal for addition of a constructor to Soroban’s flavor of Rust was introduced in a previous protocol meeting ([previous meeting](./2024-07-25.mdx)), documented in [CAP-58](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0058.md). A constructor is a function that will only be executed the first time the contract is created.
-2. In this meeting, Dima discussed the updates made since the last meeting:
-   1. Default constructor - if a constructor is not defined explicitly, the contract is treated as if it has a constructor
-   2. Semantics of the return value - if the transactions succeeds, it is required to return a valid value
-   3. Constructor interaction with custom accounts - custom accounts must be aware of the context that they are authorizing.
-3. Graydon discussed the upgrade to the Wasmi virtual machine, documented in [CAP-60](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0060.md). Wasmi works by translating WebAssembly code to to an Internal Representation (IR) and then executing it. The upgrade is impactful in two ways.
-   1. Translating from WebAssembly to IR takes longer but the execution of the resulting IR is performant.
-   2. The upgrade introduces lazy compilation. Of all functions in a contract, only ones that are called in a given transaction will translated thus reducing both latency and fees.
-4. Jay discussed addition of BLS12-381 cryptographic curve, documented in [CAP-59](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0059.md).
-   1. Addition of pairing-friendly elliptic curves enables zk-based applications. 11 host functions have been added to expose mapping, pairing, and arithmetic on the BLS12-381 curve.
-   2. Examples case of BLS signature verification was presented. It consumed 26M instructions (running natively), which is promising given the per-transaction limit is 100M.
-   3. There was general agreement that the interface is the right one as it allows a contract developer to implement a wide variety of use cases. Discussion continues in discord.
-   4. Jay requested that developers should build applications against the function and give feedback.
diff --git a/meetings/2024-08-29.mdx b/meetings/2024-08-29.mdx
deleted file mode 100644
index 9a5a73e14..000000000
--- a/meetings/2024-08-29.mdx
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title: "2024-08-29"
-authors: naman
-tags: [protocol]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1RBFt9diUPAgoeurw4xluyA9Qq1JNG2w8" />
-
-Agenda: [Discord thread](https://discord.com/channels/897514728459468821/900374272751591424/1278045556211716171)
-
-CAP Core team deliberated on the proposed CAPs:
-
-1. Addition of a constructor to Soroban's flavor of Rust. [CAP](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0058.md)
-   1. Team's concern was about potential break in compatibility, which Dima had addressed. There were no further concerns.
-2. Addition of BLS12-381 curve and required field arithmetics - [CAP](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0059.md)
-   1. Team's concern was about providing functions to check invalid input. It's too computationally expensive to do the check at the contract layer so the it may need to be implemented as a host function. Jay is seeking ecosystem input around use cases that require strict input validation.
-   2. There were no further concerns.
-3. Increase performance by upgrading Soroban's VM. [CAP Discussion](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0060.md)
-   1. Team's comments were about accuracy of the measurement method but the demonstrated benefits of wall clock time were thought to be promising.
-   2. There was a suggestion to expose performance improvements to contract developers thus creating the incentive to optimize contracts to leverage the improvements.
-   3. There were no further concerns.
diff --git a/meetings/2024-09-05.mdx b/meetings/2024-09-05.mdx
deleted file mode 100644
index c8716b796..000000000
--- a/meetings/2024-09-05.mdx
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: "2024-09-05"
-authors: anataliocs
-tags: [developer]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1bw1KCnF2C6cz0NhWNGKoUOg4oiC-OZck" />
-
-Agenda: [Discord thread](https://discord.com/channels/897514728459468821/900374272751591424/1280678171053789317)
-
-Platform team demonstrated Galexie, a part of CDP(Composable Data Platform):
-
-1. Galexie
-   1. Data Extraction: Extracts raw ledger data from the Stellar network
-   2. Compression: Compresses raw data for efficient storage
-   3. Storage Options: Supports runtime configuration through the Datastore abstraction to use various physical storage layers, starting with Google Cloud Storage (GCS)
-   4. Modes of Operation: Can operate in either batch mode or streaming mode
-2. Composable Data Platform
-   1. Flexible Datastore: Multiple options for physical data storage layers
-   2. Galexie: Used to extract, compress and export data to your chosen Datastore
-   3. Transform: Structure data in a model suitable to your application
-3. Pluggable Data Pipelines
-   1. Workflows: Create ETL(extract, transform, load) pipelines
-   2. Streaming: Fast, lightweight streaming data
diff --git a/meetings/2024-09-12.mdx b/meetings/2024-09-12.mdx
deleted file mode 100644
index 80b9202ea..000000000
--- a/meetings/2024-09-12.mdx
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: "2024-09-12"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1raU1Z9EQBLCkkuUO9yyF8yD2l_3nwk4a" />
-
-Agenda: [Discord thread](https://discord.com/channels/897514728459468821/900374272751591424/1282934024892973077)
-
-Developer Experience team member Nando Vieira introduced the CLI features alias and snapshot:
-
-1. Alias
-   1. Install of Hello World example for showcasing alias
-   2. Showed examples of how contract IDs are often passed as parameters in CLI commands like invoke (copying ID string or command substitution)
-   3. How to deploy a smart contract and create an alias
-   4. How to invoke the smart contract with the alias
-2. Snapshot
-   1. How to create a ledger snapshop
-   2. How to use the snapshot in a test case
-
-Towards the end Nando went through the developer documentation, with focus on the added command line examples for Windows users, and a useful cookbook for CLI commands.
diff --git a/meetings/2024-09-19.mdx b/meetings/2024-09-19.mdx
deleted file mode 100644
index 5a1fa1014..000000000
--- a/meetings/2024-09-19.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: "2024-09-19"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1yIzMrtyuJkX6W8MlIbwrGNivYqHuhoxH" />
-
-Agenda: [Discord thread](https://discord.com/channels/897514728459468821/900374272751591424/1285627254130610297)
-
-SDF DevRel team member Carsten Jacobsen showed how to build a simple Hello World dapp based on a Soroban smart contract and Next.js through these steps:
-
-1. Create the default Hello World smart contract using the Stellar CLI
-2. Create TypeScript bindings (package) using the Stellar CLI
-3. Create the default Next.js using the npx create-next-app command
-4. Add and link the TypeScript binding package to the Next.js project
-5. Create a simple frontend with a form to submit a string
-6. Import the package in the Next.js page, and setup a client
-7. Create submit-function to send form value to the smart contract
-8. Use useState to store the smart contract response and display it
diff --git a/meetings/2024-09-26.mdx b/meetings/2024-09-26.mdx
deleted file mode 100644
index 11a1e16c4..000000000
--- a/meetings/2024-09-26.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: "2024-09-26"
-authors: anataliocs
-tags: [developer]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1gV-4lV32eN5R5rvtK5SY3aH1FVcbwI7D" />
-
-Agenda: [Discord thread](https://discord.com/channels/897514728459468821/900374272751591424/1288890126038208532)
-
-Summary: Hoops Finance, a DeFi protocol, discussed their platform they are building. https://www.hoops.finance/
-
-1. They abstract away the complexity of DeFi investments for normal users through a series of guided prompts.
-2. Provides simplified access to LP liquidity provisioning abstraction
-3. Public AMM API for read/write data on AMMs on Stellar
-4. Hoops Finance API: https://api.v1.xlm.services/#overview
diff --git a/meetings/2024-10-24.mdx b/meetings/2024-10-24.mdx
deleted file mode 100644
index 096c1e5fd..000000000
--- a/meetings/2024-10-24.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: "2024-10-24"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="1saHsJ793C5yQu9pUC9Ao-rAeuIoLjScQ" />
-
-Agenda: [Discord thread](https://discord.com/channels/897514728459468821/900374272751591424/1298362698123182080)
-
-SDF’s Platform team had an internal hackathon last week, with the purpose of building applications utilizing the [Composable Data Platform (CDP)](https://stellar.org/blog/developers/composable-data-platform). In this week’s developer meeting some of the team members present their projects. The apps are widely varied (trading app, fraud detection, JS browser-based ingester, etc) but the intent here is to show how easy CDP is to use.
-
-Projects presented in the meeting:
-
-1. Trade Aggregations Service
-2. Deceptiscan - CDP fraud detection
-3. Composable Data Platform Hackies - data indexer, payment indexer, contract expiration alerter, data indexes in DuckDB, torrents for data indexes and ledger metadata)
-4. Data ingest with frontend JS
-5. Real-time analytics
diff --git a/meetings/2024-11-14.mdx b/meetings/2024-11-14.mdx
deleted file mode 100644
index 53d606f8f..000000000
--- a/meetings/2024-11-14.mdx
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title: "2024-11-14"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import DriveVideo from "@site/src/components/DriveVideo";
-
-<DriveVideo ID="16-QDUaoFTvLD0WUshuVQs1lp36XeuMn9" />
-
-Agenda: [Discord thread](https://discord.com/events/897514728459468821/1304859059425382553/1306725344870400000)
-
-At this week’s developer meeting, Jeesun demonstrated the new Stellar Lab, showcasing its enhanced features designed to improve the developer experience.
-
-The tech stack of the new Stellar Lab was discussed in the meeting, and the following demos were used to show the Lab's functionality:
-
-1. Enable MultiSig Exercise
-2. Stellar Wallets Kit
-3. Create & Fund Account
-4. Save KeyPairs Feature
-5. Save Transactions Feature
-6. XDR to JSON mapping
-7. RPC Methods - including simulateTransaction
diff --git a/meetings/2024-12-05.mdx b/meetings/2024-12-05.mdx
deleted file mode 100644
index ecebf39dd..000000000
--- a/meetings/2024-12-05.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "2024-12-05"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="UCYfq-RuQkY" />
-
-In this week's call we talk to Alberto Chaves from Trustless Work about building an escrow service on Stellar, followed by a quick introduction to using AI-based tools to develop Soroban smart contracts.
diff --git a/meetings/2024-12-12.mdx b/meetings/2024-12-12.mdx
deleted file mode 100644
index 2fb974e44..000000000
--- a/meetings/2024-12-12.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "2024-12-12"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="w_senlMbHVM" />
-
-In this meeting, SDF Developer Advocate Chris Anatalio talks about the future stack, including smart contract wallets and Passkeys. In the second half, SDF Core Software Engineer Siddharth Suresh talks about increasing Soroban limits.
diff --git a/meetings/2024-12-19.mdx b/meetings/2024-12-19.mdx
deleted file mode 100644
index 8f9c4a396..000000000
--- a/meetings/2024-12-19.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "2024-12-19"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="51SitOUZySk" />
-
-In this meeting SDF Core Software Engineer Jay talks about BLS building blocks, and walks through examples and demos.
diff --git a/meetings/2024/01/18.mdx b/meetings/2024/01/18.mdx
new file mode 100644
index 000000000..184870f3d
--- /dev/null
+++ b/meetings/2024/01/18.mdx
@@ -0,0 +1,34 @@
+---
+title: "2024-01-18"
+description: "Discord agenda thread"
+---
+
+_January 18, 2024_ · [Naman Kumar](https://github.com/namankumar), Product Manager
+
+🎧 **Audio Recording**
+
+<video
+  controls
+  preload="metadata"
+  className="w-full h-14"
+  src="https://pub-b2eaaee2bbe74d70820bacb7298958f5.r2.dev/0101802024_protocol_developer_call.mp3"
+/>
+
+[Discord agenda thread](https://discord.com/channels/897514728459468821/1196897067445010452)
+
+1. The need for zk-enabling encryption curves like BLS12-381. [Github thread](https://github.com/stellar/rs-soroban-env/issues/779).
+1. Use cases that ecosystem is interestd in:
+   1. Excellar, i.e. folks that kicked off this conversation by submitting a [PR for BLS12-381](https://github.com/stellar/rs-soroban-env/pull/1310), wants to add a DAO-controlled oracle where the elliptical curve provides the ability to add new DAO voters
+   2. Zkbricks wants to build an L2 system for that enables secret state for arbitrary smart contracts
+   3. Skyhitz wants to use stellar for efficient compute, cost, and scalability while using zk to prove ownership of high-value assets on another chain
+   4. Use case enumeration continues in the [discord thread](https://discord.com/channels/897514728459468821/1197663875512942653).
+1. Considerations for host function implementation
+   1. Core devs questioned whether BLS12-381 was the right curve and also highlighted the need to determine the correct level of abstraction given there is a tradeoff between flexibility and efficiency. Lower level of abstraction will enable more flexibility but result in more hot loops in the wasm while a higher level of abstraction will be highly efficient but will restrict generality.
+   2. ZkBricks thought that there is a need to directly expose pairings and group operations without any level of abstraction. The space is in active development and flexibility is needed to try out new approaches and proof systems. From the point of view of crypto agility, it would be good to expose a generic interface that supports a variety of curves in the backend.
+1. Path Forward
+   1. Core devs mentioned crypto curves can be experimented locally by linking rust crates, which it turns out, had failed in the past. This will be explored and fixed.
+   2. ZkBricks and others will prototype locally and provide feedback.
+1. What are the best practices for managing transactions in the frontend, with respect to transaction ordering.
+1. Core devs confirmed that ordering is intentionally arbitrary.
+1. Request for an API for current version of the environment/sdk
+1. Github issue filed for the RPC to return versions of the current node.
diff --git a/meetings/2024/01/26.mdx b/meetings/2024/01/26.mdx
new file mode 100644
index 000000000..3f0f39a50
--- /dev/null
+++ b/meetings/2024/01/26.mdx
@@ -0,0 +1,35 @@
+---
+title: "2024-01-26"
+description: "Discord agenda thread"
+---
+
+_January 26, 2024_ · [Tyler van der Hoeven](https://github.com/kalepail), Developer Advocate Director
+
+🎧 **Audio Recording**
+
+<video
+  controls
+  preload="metadata"
+  className="w-full h-14"
+  src="https://pub-b2eaaee2bbe74d70820bacb7298958f5.r2.dev/Soroban-Dev-Call-01-26-24.mp3"
+/>
+
+[Discord agenda thread](https://discord.com/channels/897514728459468821/1199121845656486009)
+
+1. Plan and schedule for these meetings
+   1. Protocol meetings every other Thursday at 4pm ET
+   2. Developer meetings every other Friday at 1pm ET
+   3. Will continue to adjust as needed
+2. Fee bump bug - [announcement](https://stellar.org/blog/developers/fee-bump-bug-disclosure) | [discussion thread](https://discord.com/channels/897514728459468821/1200432249594707998/1200432306314281000)
+   1. Fee sponsorship bug: unused fee is refunded to the inner tx source rather than the sponsor source.
+   2. Fix in new release. Up to the ecosystem and validators to upgrade. The fix will likely be rolled out before Phase 2.
+   3. Up to validators to determine if they’d like to push the v20 upgrade date to wait for the fix; or upgrade with current release.
+3. TxMeta Deprecation in Horizon - [announcement](https://discord.com/channels/897514728459468821/900374272751591424/1199438109796999298)
+4. Ideas around testing against ledger snapshots - [request](https://discord.com/channels/897514728459468821/1199121845656486009/1199158421254049912)
+   1. Define the needs a bit more clearly
+   2. Definitely something here we should be addressing to make testing against specific ledger state easier
+5. How do you get a list of smart contracts? - [thread](https://discord.com/channels/897514728459468821/1199121845656486009/1199739331078803496)
+   1. Observe create contract ops as ledgers close
+   2. Use an [indexing service](/docs/data/indexers)
+6. What is the status of contracts caching support? - [question](https://discord.com/channels/897514728459468821/1199121845656486009/1200484710447587490)
+   1. [response](https://discord.com/channels/897514728459468821/1199121845656486009/1200516877680644276)
diff --git a/meetings/2024/02/01.mdx b/meetings/2024/02/01.mdx
new file mode 100644
index 000000000..d3dd728f7
--- /dev/null
+++ b/meetings/2024/02/01.mdx
@@ -0,0 +1,29 @@
+---
+title: "2024-02-01"
+description: "Discord agenda thread"
+---
+
+_February 1, 2024_ · [Naman Kumar](https://github.com/namankumar), Product Manager
+
+🎧 **Audio Recording**
+
+<video
+  controls
+  preload="metadata"
+  className="w-full h-14"
+  src="https://pub-b2eaaee2bbe74d70820bacb7298958f5.r2.dev/Stellar-Protocol-Meeting-02-01-2024.mp3"
+/>
+
+[Discord agenda thread](https://discord.com/channels/897514728459468821/1201979721211203614)
+
+1. The proposal is to advance stellar-core by adding a host function to verify the secp256r1 signature, which is the most common elliptic curve used outside of the blockchain space. It is useful in connecting off-chain authentication interfaces with on-chain functionality.
+1. Note that the proposal is not for a new signer type but a host function.
+1. Leigh investigated adding support for the WebAuthN use case, by allowing a custom account / smart contract to sign soroban auth entries using a secp256r1-signed payload.
+1. secp256r1 is supported by phones, passkeys, and enables an app to replace passwords. This is a massive benefit to user-facing applications like wallets.
+1. Pros and cons of the interface: blockchains generally implement the recovery interface over the verification interface but verification is easier for developers as it reduces burden on the client and the network.
+1. The WebAuthN use case requires encoding and decoding of base64 payloads and decoding JSON blobs, which is not currently supported in Soroban.
+1. While there are hacky ways of accomplishing the latter, it’s not a great developer experience and final implementation is susceptible to breakages on updates.
+1. It is also costly to bundle decoding with verification in guest.
+1. Soroban has always led with a batteries included mindset. Keeping in line with that approach, it makes sense to further investigate and determine whether a host function makes sense for these as well.
+1. Leigh’s implementation may require further evaluation of the crates used for ecdsa and p256.
+1. Brief discussion around proposed process for adding of a host function by a non-core dev.
diff --git a/meetings/2024/02/08.mdx b/meetings/2024/02/08.mdx
new file mode 100644
index 000000000..28f890ece
--- /dev/null
+++ b/meetings/2024/02/08.mdx
@@ -0,0 +1,22 @@
+---
+title: "2024-02-08"
+description: "Discord agenda thread"
+---
+
+_February 8, 2024_ · [Tyler van der Hoeven](https://github.com/kalepail), Developer Advocate Director
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1Hgp8K_XDeq4yaON3TWeHDtQTAyVR1crY/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+[Discord agenda thread](https://discord.com/channels/897514728459468821/1204462856037470248)
+
+1. Stellar Asset List (SEP-42) draft presentation by [OrbitLens](https://github.com/orbitlens)
+   1. [SEP draft](https://github.com/orbitlens/stellar-protocol/blob/sep-0042-token-lists/ecosystem/sep-0042.md)
+   2. [Discord discussion](https://discord.com/channels/897514728459468821/1162558946867953704)
+2. Stellar + Soroban documentation survey
+   1. [Take the survey](https://discord.com/channels/897514728459468821/1204462856037470248/1205196745877757962)
diff --git a/meetings/2024/02/15.mdx b/meetings/2024/02/15.mdx
new file mode 100644
index 000000000..d01391cc1
--- /dev/null
+++ b/meetings/2024/02/15.mdx
@@ -0,0 +1,45 @@
+---
+title: "2024-02-15"
+description: "Discord agenda thread"
+---
+
+_February 15, 2024_ · [Naman Kumar](https://github.com/namankumar), Product Manager
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1oBuYg_LvGRGnKpjezok6PQGVN8ZpqVvy/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+[Discord agenda thread](https://discord.com/channels/897514728459468821/1207385360116490360)
+
+1. The meeting was focused on the process of adding host functions, using WebAuthN as the example use case; continued from the previous meeting.
+2. Discussion of remaining concerns with adding secp256r1 verification host function from previous meeting.
+   - What does it mean for secp256r1 to be added as a host function vs. as a signer type?
+     - As a host function, user can sign soroban auth entries. Need another stellar account to fund and submit tx to the chain. The latter can be done by a stellar account which may be operated by a wallet or a contract.
+     - \_\_check_auth is invoked when the contract being interacted with calls require_auth
+3. CAP-52 was drafted to introduce encoding/decoding functions for Base64, which is needed by WebAuthN. Considerations discussed in the meeting:
+   - Performance: 1066 bytes that costs 1M instr to encode a 32byte hash; so the cost is very small and it’s questionable whether a host function is required.
+   - Interface required two functions (encode/decode)
+   - Implementation wise, WebAuthN requires url alphabet and padding, which decoder likely needs to support. Should we use symbols or ints? Do we need custom alphabets?
+   - Do we really need more encoding schemes? Isn’t XDR enough?
+   - Expensive auth mechanisms, i.e. webauthn, cannot be coupled with contracts with heavy business logic (which might be a lot of contracts), thus making adoption problematic.
+   - We should probably add building blocks to enable the ecosystem to add new use cases.
+4. CAP-53 was drafted to introduce encoding/decoding functions for JSON, which is needed by WebAuthN. Considerations discussed in the meeting:
+   - Performance: 3.9Kb, 2.5M CPU instr.
+   - If the size of the input blob is unknown, execution time will increase.
+   - Valuable to have such a lightweight function that’ll be used in various place.
+   - Interface: 11 functions
+     - What to do with numbers and decimals? Add decimals and floats?
+     - We only have to extract one field for WebAuthN but what about the general case?
+   - The number type in JSON is decimal but soroban does not support that. How should this be handled?
+   - Discussion around alternative interface and implementations.
+5. Core dev concerns
+   - Maintainability: if you add a host function, you have to maintain it forever. If there are more versions, we have to keep it around.
+   - Expanded surface area for security bugs.
+   - Should define a path where core dev is not in the implementation loop, as their schedules are packed with stability work. How to prioritize against stability work, which may get derailed due to new functionality such as what’s being currently discussed.
+   - Next steps:
+     - Core team to put together a plan for adding Base64. This is an important exercise that helps determine even more challenges of doing so. The output of this exercise may be that base64 _shouldn’t_ in fact be implemented at this point.
+     - Discussion around the JSON interface is to be continued.
diff --git a/meetings/2024/02/22.mdx b/meetings/2024/02/22.mdx
new file mode 100644
index 000000000..358c2ba50
--- /dev/null
+++ b/meetings/2024/02/22.mdx
@@ -0,0 +1,21 @@
+---
+title: "2024-02-22"
+description: "Discord agenda thread"
+---
+
+_February 22, 2024_ · [Tyler van der Hoeven](https://github.com/kalepail), Developer Advocate Director
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1ZZm1eLe6L0ZRtpTxF77RfrLkW9ThAWh4/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+[Discord agenda thread](https://discord.com/channels/897514728459468821/1209582245824823337)
+
+1. Latest and greatest on the TypeScript bindings with [@chadoh](https://github.com/chadoh)
+2. [Available RPC providers](/docs/data/apis/rpc/providers)
+3. Standing up a [`stellar-rpc` docker container](/docs/data/apis/rpc/admin-guide#docker-image)
+4. Installing and invoking a Stellar Asset Contract on mainnet in Phase 0
diff --git a/meetings/2024/02/29.mdx b/meetings/2024/02/29.mdx
new file mode 100644
index 000000000..a075454c7
--- /dev/null
+++ b/meetings/2024/02/29.mdx
@@ -0,0 +1,21 @@
+---
+title: "2024-02-29"
+description: "Discord agenda thread"
+---
+
+_February 29, 2024_ · [Naman Kumar](https://github.com/namankumar), Product Manager
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1zKvUx74UqvfmpNvU8BJt5RAqj-XHyBke/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+[Discord agenda thread](https://discord.com/channels/897514728459468821/1212118102565855243)
+
+1. Tommaso (@tdep) proposed a core change to allow for extending instance and code TTL with separate values on the host environment to allow for more cost-efficient designs a. Proposal and discussion are captured in github discussions [stellar-core#1447](https://github.com/stellar/stellar-protocol/discussions/1447)
+2. Tommaso received feedback on the proposal as well as implementation. Since it didn't require a metering change, core devs thought it to be a quick change.
+3. The ecosystem voted in favor of the proposal by upvoting the post on Github Discussions. 13 votes were [recorded](https://github.com/stellar/stellar-protocol/discussions).
+4. As next steps, a CAP will be authored to capture the proposal and put forth for approval from CAP Core Team.
diff --git a/meetings/2024/03/07.mdx b/meetings/2024/03/07.mdx
new file mode 100644
index 000000000..e669b1f50
--- /dev/null
+++ b/meetings/2024/03/07.mdx
@@ -0,0 +1,22 @@
+---
+title: "2024-03-07"
+description: "Discord agenda thread"
+---
+
+_March 7, 2024_ · [Tyler van der Hoeven](https://github.com/kalepail), Developer Advocate Director
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1FJueTZweJPaOyno0fxHOfU3Ec2S0gvO_/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+[Discord agenda thread](https://discord.com/channels/897514728459468821/911254664576643122/1215404506964172890)
+
+1. [Sorobill tool](https://github.com/kalepail/sorobill)
+2. Deploying contracts and testing invocations against the unlimited [quickstart](https://github.com/stellar/quickstart).
+3. Using Sorobil package as a tool to get a snapshot of all the limits the contract is touching. [Relevant blog post](https://kalepail.com/blockchain/show-me-the-bill-part-2)
+4. How to measure the contract costs and what limits you are touching
+5. Utilizing the Sorobil tool to decode XDR and understand failed transactions.
diff --git a/meetings/2024/03/14.mdx b/meetings/2024/03/14.mdx
new file mode 100644
index 000000000..4f763638d
--- /dev/null
+++ b/meetings/2024/03/14.mdx
@@ -0,0 +1,25 @@
+---
+title: "2024-03-14"
+description: "Discord agenda thread"
+---
+
+_March 14, 2024_ · [Naman Kumar](https://github.com/namankumar), Product Manager
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1Gztue3zvZBQzVPshM0_Yy8ntYh7Bk33d/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+[Discord agenda thread](https://discord.com/channels/897514728459468821/1217193723612368926)
+
+1. CAP Core Team deliberated over the latest proposals put forth by the Stellar ecosystem to advance stellar-core.
+2. Nicholas and David from the CAP Core Team listened to the following proposals and discussed the proposals with the authors. a. CAP Core team will deliver their vote over email.
+3. Proposals discussed:  
+   a. [CAP-51](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0051.md): add support for secp256r1 verification; by @leigh  
+   b. [CAP-53](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0053.md): create separate functions for extending the time-to-live for contract instance and contract code; by @tdep  
+   c. [CAP-54](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0054.md): lower total costs by refining the Soroban cost model used for VM instantiation into multiple separate and more-accurate costs; by @graydon  
+   d. [CAP-55](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0055.md): lower total costs by linking fewer host functions during VM instantiation in Soroban; by @graydon  
+   e. [CAP-56](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0056.md): lower total costs by caching parsed Wasm modules within a Soroban transaction; by @graydon
diff --git a/meetings/2024/03/21.mdx b/meetings/2024/03/21.mdx
new file mode 100644
index 000000000..d5a7b71b0
--- /dev/null
+++ b/meetings/2024/03/21.mdx
@@ -0,0 +1,23 @@
+---
+title: "2024-03-21"
+description: "Discord agenda thread"
+---
+
+_March 21, 2024_ · [Tyler van der Hoeven](https://github.com/kalepail), Developer Advocate Director
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1vSkQFbdg80548ShpjOpyD9scnQjebkQi/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+[Discord agenda thread](https://discord.com/channels/897514728459468821/1219381314931917000)
+
+1.  There's a discussion on a TX meta change increasing visibility and analytics within the Stellar network. (https://github.com/stellar/stellar-xdr/pull/175)
+2.  Read-only invocations for contracts is explained, focusing on ensuring certain functions remain read-only without side effects. (https://github.com/stellar/stellar-protocol/discussions/1454) (https://github.com/stellar/stellar-protocol/discussions/1456) (https://github.com/stellar/stellar-protocol/discussions/1464)
+3.  Enabling contract discovery is introduced to enhance the visibility and authenticity of smart contracts within the Stellar ecosystem.
+4.  The implementation of a standardized contract meta data schema is proposed to link contracts to source code and enhance contract discoverability.(https://docs.rs/soroban-sdk/latest/soroban_sdk/macro.contractmeta.html)
+5.  Issues related to inclusion fees in the Stellar network, highlighting the importance of monitoring fees closely and understanding the implications of [surge pricing](/docs/learn/fundamentals/fees-resource-limits-metering#inclusion-fee)
+6.  Plans are discussed for designing a new RPC endpoint to provide developers with better visibility and information on setting inclusion fees, aiming to improve transparency and decision-making regarding fee trade-offs.
diff --git a/meetings/2024/03/28.mdx b/meetings/2024/03/28.mdx
new file mode 100644
index 000000000..6c1d33d5d
--- /dev/null
+++ b/meetings/2024/03/28.mdx
@@ -0,0 +1,22 @@
+---
+title: "2024-03-28"
+description: "Agenda thread"
+---
+
+_March 28, 2024_ · [Naman Kumar](https://github.com/namankumar), Product Manager
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1e7AgsEAno0pZBYkICuKaqC3HMQkjWRd9/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+[Agenda thread](https://github.com/stellar/stellar-protocol/discussions/1475)
+
+1. The Standards Working Group proposed changes to the SEP process that empower the ecosystem by making the current process more decentralized and ecosystem-friendly.
+2. The process has already been used for several proposals over the last three months.
+3. Esteblock from Soroswap shared their journey of participating in the proposal for Asset List ([SEP-42](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0042.md)) and implementing the proposed standard
+4. Discussion continues in the proposal doc.
+5. Next step is to get further ecosystem feedback then update the Github SEP repository with the updated SEP process.
diff --git a/meetings/2024/04/04.mdx b/meetings/2024/04/04.mdx
new file mode 100644
index 000000000..29f177917
--- /dev/null
+++ b/meetings/2024/04/04.mdx
@@ -0,0 +1,35 @@
+---
+title: "2024-04-04"
+description: "Today's recording has two parts."
+---
+
+_April 4, 2024_ · [Naman Kumar](https://github.com/namankumar), Product Manager
+
+Today's recording has two parts. The first 12 minutes are audio-only. The next 45 minutes have video as well. Please note the slides were shared in discord chat over screensharing, due to technical difficulties.
+
+Part 1 (audio-only):
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/14ddYFIMDgsX70hTCv8C1tKaAGmJiprw7/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+Part 2 (video):
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1p4LrgGLfRdVww-7d21w3BGyPrLfiIDmF/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+[Discord Agenda thread](https://discord.com/channels/897514728459468821/1224408179363024918)
+
+1. Piyal surfaced the proposal for a [Wallet Standard](https://github.com/stellar/stellar-protocol/discussions/1467) and requested feedback.
+2. Cubist, an ecosystem project, discussed CubeSigner, a low-latency API for generating keys and signing transactions inside secure hardware.
+3. Stellar-based example of CubeSigner is available in the [Cubist Labs Github repository](https://github.com/cubist-labs/CubeSigner-TypeScript-SDK/tree/main/examples/stellar)
+4. Cubist devs can be contacted via the Stellar discord or the [web form](https://cubist.dev/contact-form-cubesigner-hardware-backed-key-management).
diff --git a/meetings/2024/04/11.mdx b/meetings/2024/04/11.mdx
new file mode 100644
index 000000000..cbcf94cde
--- /dev/null
+++ b/meetings/2024/04/11.mdx
@@ -0,0 +1,23 @@
+---
+title: "2024-04-11"
+description: "Piyal from Freighter discussed the proposal to standardize the wallet interface."
+---
+
+_April 11, 2024_ · [Naman Kumar](https://github.com/namankumar), Product Manager
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1OCt2lXcrwhVyRd4dcwj8mfCOzxXON6nL/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+Piyal from Freighter discussed the proposal to standardize the wallet interface. Key points from the discussion are captured below. For full notes, please view the recording; and also refer to the proposal and the post on github discussions.
+
+1. [The draft proposal](https://github.com/stellar/stellar-protocol/blob/83191be659166e05f8df1257c6f655de9d1afe63/ecosystem/sep-0043.md)
+2. [Ongoing discussion](https://github.com/stellar/stellar-protocol/discussions/1467)
+3. Requiring the network passphrase might be uneeded complexity.
+4. Both WalletConnect and mobile wallets likely have significant differences than the proposed interface (which is targetted at browser extension wallets); and thus likely require a separate SEP. The said SEPs should be created by teams working on wallet integration with the said platforms.
+5. What is the role of the Stellar Wallet Kit in the ecosystem and how does it play with the standard itself?
+6. As next steps, Piyal will incorporate the suggestions from the ecosystem into the proposal.
diff --git a/meetings/2024/04/18.mdx b/meetings/2024/04/18.mdx
new file mode 100644
index 000000000..461b572ca
--- /dev/null
+++ b/meetings/2024/04/18.mdx
@@ -0,0 +1,21 @@
+---
+title: "2024-04-18"
+description: "Discord agenda thread"
+---
+
+_April 18, 2024_ · [Tyler van der Hoeven](https://github.com/kalepail), Developer Advocate Director
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1ZUdrK0YuF69un_KA3rJGvZaD_wmgYG8N/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+[Discord agenda thread](https://discord.com/channels/897514728459468821/911254664576643122/1215404506964172890)
+
+1. Justin from [ortege.ai](https://www.ortege.ai) demo'd Ortege, a data analytics platform for Stellar and Soroban.
+2. Ortege lets anyone in the Stellar ecosystem create dashboards to track any and all desired metrics. Ortege's queries, widgets, and dashboards are shareable making it the perfect platform to surface
+3. Justin will be releasing an AI soon and enable querying and insights via natural language.
+4. All are invited to create a free account and track the success metrics for their dashboard.
diff --git a/meetings/2024/04/25.mdx b/meetings/2024/04/25.mdx
new file mode 100644
index 000000000..10d838b56
--- /dev/null
+++ b/meetings/2024/04/25.mdx
@@ -0,0 +1,25 @@
+---
+title: "2024-04-25"
+---
+
+_April 25, 2024_ · [Naman Kumar](https://github.com/namankumar), Product Manager
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1WdZeRnjwl0FCxwtQhy2DNqMtNIiZIgtD/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+1. Garand discussed changes to the State Archival proposal based on feedback received at Meridian 2023. The proposed changes are:
+
+- Previously, a downstream system called the ESS (Expired State Store) would store expired entries. In the new proposal, There is no ESS. All Archived entries, as well as all information required to generate restoration proofs for those entries, is stored directly in the History Archive.
+- RPC nodes can generate proofs for archived state during preflight
+- Captive-core can be directly queried for archived state, meaning that RPC/Horizon instances can potentially service queries for archival state
+
+2. [The draft proposal](https://docs.google.com/document/d/1FAs3Yfo-o-gVqccrP29NSG8ysRvdEoyvuL7ywV4ijXI/edit#heading=h.1xwsoyifxbfm)
+3. [Ongoing discussion](https://github.com/stellar/stellar-protocol/discussions/1480)
+4. Snapshot size is TBD; it's a function of bucket list size as well as memory and historic demands placed on the RPC.
+5. Bloom filters are the likely solution for proof of non-exitance though they come with trade-offs. They enable fast and cheap lookup but are probabilistic not deterministic.
+6. Further comments are welcome.
diff --git a/meetings/2024/05/02.mdx b/meetings/2024/05/02.mdx
new file mode 100644
index 000000000..6c1cacd17
--- /dev/null
+++ b/meetings/2024/05/02.mdx
@@ -0,0 +1,24 @@
+---
+title: "2024-05-02"
+description: "Discord Agenda thread"
+---
+
+_May 2, 2024_ · [Naman Kumar](https://github.com/namankumar), Product Manager
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1-XWdGA3vMqoMI6DqBDtjKR_DTeOImpbZ/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+[Discord Agenda thread](https://discord.com/channels/897514728459468821/1234887262530048010/1234887262530048010)
+
+1. Fifo presented [Stellar Plus](https://docs.cheesecakelabs.com/stellar-plus), which is a Javascript library to simplify the Stellar and Soroban development.
+2. Ecosystem members found the design for Stellar Plus composable and encompassing of all Stellar related functionality including management of assets, accounts, wasm-related operations, as well as RPC utils.
+3. The links to Fifo's presentation and Stellar Plus are:
+   - [Miro Board showing Stellar Plus architecture](https://miro.com/app/board/uXjVKMDkMPI=/?share_link_id=643609701897)
+   - [Stellar Plus Repositore](https://discord.com/channels/897514728459468821/1234887262530048010/1235699608274079865)
+   - [Examples Repository](https://github.com/fazzatti/stellar-plus-examples)
+   - [Docs](https://docs.cheesecakelabs.com/stellar-plus)
diff --git a/meetings/2024/05/09.mdx b/meetings/2024/05/09.mdx
new file mode 100644
index 000000000..8dabe21c7
--- /dev/null
+++ b/meetings/2024/05/09.mdx
@@ -0,0 +1,19 @@
+---
+title: "2024-05-09"
+---
+
+_May 9, 2024_ · [Naman Kumar](https://github.com/namankumar), Product Manager
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1PvA8cxInSfRjmewJbILhgpZYv4CBExZv/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+1. Tyler built a voting application using passkeys to sign the transaction, which is an implementation of the secp256r1 verification function.
+2. He showed a cross-platform implementation (web and mobile) and demonstrated that passkeys are the perfect interface between web3 contracts and web2 authentication mechanisms that most end users are accostomed to.
+3. Ecosystem members discussed the use of smart wallets that would use passkeys as a signer. Challenges were identified around fees requires for smart wallets, the need for a common implementation for a smart wallet, as well as how might it interface with existing password managers.
+4. The voting application can be tried out at [passkey.sorobanbyexample.org](https://passkey.sorobanbyexample.org)
+5. Code for the demo is here [github.com/kalepail/soroban-passkey](https://github.com/kalepail/soroban-passkey)
diff --git a/meetings/2024/06/13.mdx b/meetings/2024/06/13.mdx
new file mode 100644
index 000000000..aed855fcc
--- /dev/null
+++ b/meetings/2024/06/13.mdx
@@ -0,0 +1,26 @@
+---
+title: "2024-06-13"
+description: "Join the #passkeys channel on the Discord to continue the discussion"
+---
+
+_June 13, 2024_ · [Tyler van der Hoeven](https://github.com/kalepail), Developer Advocate Director
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1goVLHLJWWwRy1xgBpJa4VF1y9axrlIqA/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+1. Tyler created Super Peach, a web3 application that uses passkeys to sign transactions. He demonstrated how passkeys can be used in authorization flows and how they can be used to sign transactions.
+   - Code: https://github.com/kalepail/superpeach
+   - Demo: https://superpeach.xyz
+2. Introduced `passkey-kit`. A TypeScript SDK for creating and managing Smart Wallets via passkeys (includes the actual [Smart Wallet interface](https://github.com/kalepail/passkey-kit/tree/main/contracts))
+   - Code: https://github.com/kalepail/passkey-kit
+   - Demo: https://passkey-kit-demo.pages.dev
+3. Introduced Launchtube, a service for submitting transactions onchain by covering both the transaction fee AND the sequence number. Wild!
+   - Code: https://github.com/kalepail/launchtube (ask in the `#passkeys` channel on Discord for a testnet token)
+4. He shared his vision for pushing the passkey implementation through to becoming a [standard for the ecosystem](https://docs.google.com/document/d/1c_Wom6eK1UpC3E7VuQZfOBCLc2d5lvqAhMN7VPieMBQ/edit).
+
+Join the `#passkeys` channel on the Discord to continue the discussion
diff --git a/meetings/2024/06/20.mdx b/meetings/2024/06/20.mdx
new file mode 100644
index 000000000..2686a37a8
--- /dev/null
+++ b/meetings/2024/06/20.mdx
@@ -0,0 +1,21 @@
+---
+title: "2024-06-20"
+description: "Follow Meru on X (formerly Twitter) to stay updated: https://x.com/getmeru"
+---
+
+_June 20, 2024_ · [Naman Kumar](https://github.com/namankumar), Product Manager
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1nrEQdhiTH4wsQVgaiOO0RcmD-AS-5S2v/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+1. [Kirckz discusses Meru](https://docs.google.com/presentation/d/1Fu4AkB0mrvOkK6UDFJHgKwCV-Ul4JRF-xPqTYJ3CQqw), a Financial services app for Freelancers and remote workers in Latin America.
+2. He shares his experience integrating Meru with Blend, a liquidity protocol primitive for Stellar.
+3. Kirckz shares the challenges faced during the integration and how they were overcome.
+4. He shares the sdks and libraries his team used to facilitate the integration.
+
+Follow Meru on X (formerly Twitter) to stay updated: https://x.com/getmeru
diff --git a/meetings/2024/06/27.mdx b/meetings/2024/06/27.mdx
new file mode 100644
index 000000000..8a821893a
--- /dev/null
+++ b/meetings/2024/06/27.mdx
@@ -0,0 +1,22 @@
+---
+title: "2024-06-27"
+---
+
+_June 27, 2024_ · [Naman Kumar](https://github.com/namankumar), Product Manager
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1PS49Cvs_DLdEwquh6c9e5JuN3MASaTpz/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+1. [Chad](https://github.com/chadoh) and [Willem](https://github.com/willemneal) from [Aha Labs](https://github.com/AhaLabs) discuss the updates to the new and improved [stellar-cli](https://github.com/stellar/stellar-cli)
+2. Some highlights include the change from the name 'soroban' to 'stellar' when using the CLI tool and the addition of new commands.
+3. They cover some cool functions like local network setup, account creation, and transaction signing. with the following commands:
+   - `stellar network container [start|logs]`
+   - `stellar keys [generate|fund|ls]`
+   - `stellar contract init` to get a whole new Soroban project
+   - and so much more!
+4. They also discuss expected future updates including support for more Stellar operations and integration with Stellar Lab V2!
diff --git a/meetings/2024/07/11.mdx b/meetings/2024/07/11.mdx
new file mode 100644
index 000000000..e30100969
--- /dev/null
+++ b/meetings/2024/07/11.mdx
@@ -0,0 +1,18 @@
+---
+title: "2024-07-11"
+---
+
+_July 11, 2024_ · [Naman Kumar](https://github.com/namankumar), Product Manager
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1uBv-Qv6bHzri7OeRyBJo7hxJtH6CKjEH/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+1. SDF Data team gave a crash course in analysis of Stellar data, and covered how to access Hubble, tips for efficient querying, and how to get started with data exploration.
+2. [Slides](https://docs.google.com/presentation/d/1QsCwFLFcDF4RmNIwtSSnNrUfZb0RM0kLxOOxC7ENY5M/edit#slide=id.g2cb5821e4de_1_1143) are publicly available and legible async.
+3. Tips for data anlaysis are also covered in [docs](/docs/data/analytics/hubble/analyst-guide)
+4. Share your queries and post questions in #hubble in Stellar discord, which is a dedicated channel for data-related topics.
diff --git a/meetings/2024/07/18.mdx b/meetings/2024/07/18.mdx
new file mode 100644
index 000000000..da123d5d0
--- /dev/null
+++ b/meetings/2024/07/18.mdx
@@ -0,0 +1,22 @@
+---
+title: "2024-07-18"
+description: "Note: the first part of the call was lost."
+---
+
+_July 18, 2024_ · [Naman Kumar](https://github.com/namankumar), Product Manager
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1lml1VxNkwsRKS9BbnIMFNRXX1Kn6ktvq/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+Note: the first part of the call was lost. The video posted above captures the second half of the call where various ecosystem developers shared their use cases and needs for a smart wallet on Stellar.
+
+1. Tyler put forward a [proposal](https://github.com/stellar/stellar-protocol/discussions/1499) for a smart wallet as a public good. Given that the native auth can be overloaded by using `__check_auth`, Stellar implementation of a smart wallet is fairly straightforward. The capability to customize the auth is already built into the core protocol.
+2. See the [proposal](https://github.com/stellar/stellar-protocol/discussions/1499) here and implementation [here](https://github.com/kalepail/passkey-kit/blob/main/contracts/webauthn-wallet/src/lib.rs)
+3. The proposal only uses WebAuthN-based signers i.e. passkeys. It does not use ed25519, which, perhaps it should given that ~100% of the accounts on Stellar use the scheme. It also introduces the notion of temporary and admin signers to illustrate the notion that the account can be managed by multiple signers, each with a different access policy.
+4. The biggest unlock with custom auth is the ability to execute custom logic. We heard from various ecosystem members about how might they us it. 4a. A dev is building a perpetual protocol and thought smart wallets could be used to automatically manage defi positions, which would be a significant improvement over status quo where the user has to constantly track assets to determine _when_ to execute a trade. 4b. Folks are excited about foregoing the seed phrase for passkeys, which is especially meaningful when onboarding net new users to the blockchain. 4c. Authorizing a cross-chain message from a different chain, especially programmatic authorization, requires an implementation of custom accounts. 4d. Some apps have noted that users prefer not to have a wallet but simply experience the value of the app, especially games. For this, the app may assign a temporary account to the user and control access via check_auth. 4c. Microtransactions without needing user sign is super interesting for apps as well.
+5. This has been a very insightful meeting and we learnt about how the Stellar ecosystem plans to leverage smart wallet. Let's continue the conversation in discord!
diff --git a/meetings/2024/07/25.mdx b/meetings/2024/07/25.mdx
new file mode 100644
index 000000000..0df743f2c
--- /dev/null
+++ b/meetings/2024/07/25.mdx
@@ -0,0 +1,24 @@
+---
+title: "2024-07-25"
+description: "A Core Dev, Dima, discussed the proposal to add constructor support to Soroban, Stellar's smart contract system."
+---
+
+_July 25, 2024_ · [Naman Kumar](https://github.com/namankumar), Product Manager
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1ScrEdoscrVQX_PzaMBCHavycg8dLpaIx/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+A Core Dev, Dima, discussed the proposal to add constructor support to Soroban, Stellar's smart contract system.
+
+Relevant links: [Draft CAP](https://github.com/stellar/stellar-protocol/blob/50dde0611440d6dc562a33462e6ba5f1504b2753/core/cap-0058.md), [Ongoing discussion](https://github.com/stellar/stellar-protocol/discussions/1501), [Motivating Discord Thread](https://discord.com/channels/897514728459468821/1067534037310255225)
+
+Key points discussed:
+
+1. The proposal improves usability of Soroban for contract and SDK developers. A constructor guarantees contract initialization thus reducing overhead contract code that's usually added to ensure initialization.
+2. There was general agreement for the proposal, questions were primarily implementation-focused like whether constructors should handle arguments, what should happen with upgrades, backwards comptability with contract creation functions, and behaviour on wasm update.
+3. The high impact topic of naming is put to ecosystem vote, please cast yours [here](https://github.com/stellar/stellar-protocol/discussions/1507).
diff --git a/meetings/2024/08/01.mdx b/meetings/2024/08/01.mdx
new file mode 100644
index 000000000..f0b708028
--- /dev/null
+++ b/meetings/2024/08/01.mdx
@@ -0,0 +1,18 @@
+---
+title: "2024-08-01"
+---
+
+_August 1, 2024_ · [Naman Kumar](https://github.com/namankumar), Product Manager
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1Hog269Q96QMEJeC2DZHIMUkjMtj98YYj/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+1. Piyal demonstrated that Freighter's swap functionality is now served by [Soroswap](https://soroswap.finance). It was previously served by Stellar Dex.
+2. Freighter has made integration instructions available [here](https://github.com/stellar/freighter/blob/d248f2ad0aa03da72ea6eeaf7907ac0454fdcc72/extension/INTEGRATING_SOROSWAP.MD?plain=1#L2).
+3. Esteban shared that [Palta Labs](https://paltalabs.io) has created a DEX aggregator and made it available to all via the [Router SDK](https://docs.soroswap.finance/03-technical-reference/07-optimal-route/01-soroswap-router-sdk).
+4. The Router SDK finds the optimal path for the swap in terms of swap cost across all dexes on Soroban.
diff --git a/meetings/2024/08/08.mdx b/meetings/2024/08/08.mdx
new file mode 100644
index 000000000..6a89a4691
--- /dev/null
+++ b/meetings/2024/08/08.mdx
@@ -0,0 +1,15 @@
+---
+title: "2024-08-12"
+---
+
+_August 8, 2024_ · [Naman Kumar](https://github.com/namankumar), Product Manager
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1Q6a8WpUKplujhbD6MMzrTlfjfdXFTrBd/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+1. Tdep discussed Zephyr, an execution env built on top of the indexer Mercury. He also walked through examples demonstrating how Zephyr can simplify dapp development.
diff --git a/meetings/2024/08/15.mdx b/meetings/2024/08/15.mdx
new file mode 100644
index 000000000..c9970b283
--- /dev/null
+++ b/meetings/2024/08/15.mdx
@@ -0,0 +1,25 @@
+---
+title: "2024-08-15"
+description: "Note: The hosts microphone audio is not in the video so there is some silence during Q/A."
+---
+
+_August 15, 2024_ · [Julian Martinez](https://github.com/Julian-dev28), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1V5Arzh7LgWMj2E7FjZyGTFUl0vV31xll/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+1. @Soiled and @Robeart from Orbit spoke about using Blend to create decentralized stablecoins for all currencies under the Orbit Protocol, utilizing a decentralized pegkeeper to maintain their price, and leveraging these stablecoins and smart wallets to create an orderbook less perpetual exchange, bringing Forex to Stellar
+
+2.[Link to the presentation](https://docs.google.com/presentation/d/1mDOrBLfe8-Bq6VCy7r5bb4w_uZjq-EOorbV3ZwYfs1k/edit?usp=sharing)
+
+_Note_: The hosts microphone audio is not in the video so there is some silence during Q/A. Here are the question asked during the Q/A:
+
+1. (From ! markus_0) why do you always have an infinite amount of tokens in the pool? Wouldn't it be safer to start small and mint more as demand opens up 2.(From HunterIonize) What purpose does this serve exactly? Sorry to be blunt
+2. How do you see the Orbit Protocol contributing to financial inclusion on a global scale, particularly in underbanked regions? What challenges do you anticipate in achieving this?
+3. In 5-10 years, how do you see the landscape of Forex on blockchain evolving? What role do you believe Stellar will play in this evolution, and how will Blend and Orbit Protocol be at the forefront?
+4. Are there any asks of the developer community?
diff --git a/meetings/2024/08/22.mdx b/meetings/2024/08/22.mdx
new file mode 100644
index 000000000..9454f952c
--- /dev/null
+++ b/meetings/2024/08/22.mdx
@@ -0,0 +1,32 @@
+---
+title: "2024-08-23"
+description: "Discord agenda thread"
+---
+
+_August 22, 2024_ · [Naman Kumar](https://github.com/namankumar), Product Manager
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1Eqi0znJ21aSfjXYJ10V7eByhr-sTzujY/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+[Discord agenda thread](https://discord.com/channels/897514728459468821/900374272751591424/1275577430043525204)
+
+Core Developers discussed the latest proposals to advance Stellar Core in this week's Protocol Meeting.
+
+1. The proposal for addition of a constructor to Soroban’s flavor of Rust was introduced in a previous protocol meeting ([previous meeting](/meetings/2024/07/25)), documented in [CAP-58](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0058.md). A constructor is a function that will only be executed the first time the contract is created.
+2. In this meeting, Dima discussed the updates made since the last meeting:
+   1. Default constructor - if a constructor is not defined explicitly, the contract is treated as if it has a constructor
+   2. Semantics of the return value - if the transactions succeeds, it is required to return a valid value
+   3. Constructor interaction with custom accounts - custom accounts must be aware of the context that they are authorizing.
+3. Graydon discussed the upgrade to the Wasmi virtual machine, documented in [CAP-60](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0060.md). Wasmi works by translating WebAssembly code to to an Internal Representation (IR) and then executing it. The upgrade is impactful in two ways.
+   1. Translating from WebAssembly to IR takes longer but the execution of the resulting IR is performant.
+   2. The upgrade introduces lazy compilation. Of all functions in a contract, only ones that are called in a given transaction will translated thus reducing both latency and fees.
+4. Jay discussed addition of BLS12-381 cryptographic curve, documented in [CAP-59](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0059.md).
+   1. Addition of pairing-friendly elliptic curves enables zk-based applications. 11 host functions have been added to expose mapping, pairing, and arithmetic on the BLS12-381 curve.
+   2. Examples case of BLS signature verification was presented. It consumed 26M instructions (running natively), which is promising given the per-transaction limit is 100M.
+   3. There was general agreement that the interface is the right one as it allows a contract developer to implement a wide variety of use cases. Discussion continues in discord.
+   4. Jay requested that developers should build applications against the function and give feedback.
diff --git a/meetings/2024/08/29.mdx b/meetings/2024/08/29.mdx
new file mode 100644
index 000000000..c8305aa5e
--- /dev/null
+++ b/meetings/2024/08/29.mdx
@@ -0,0 +1,28 @@
+---
+title: "2024-08-29"
+description: "Agenda: Discord thread"
+---
+
+_August 29, 2024_ · [Naman Kumar](https://github.com/namankumar), Product Manager
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1RBFt9diUPAgoeurw4xluyA9Qq1JNG2w8/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+Agenda: [Discord thread](https://discord.com/channels/897514728459468821/900374272751591424/1278045556211716171)
+
+CAP Core team deliberated on the proposed CAPs:
+
+1. Addition of a constructor to Soroban's flavor of Rust. [CAP](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0058.md)
+   1. Team's concern was about potential break in compatibility, which Dima had addressed. There were no further concerns.
+2. Addition of BLS12-381 curve and required field arithmetics - [CAP](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0059.md)
+   1. Team's concern was about providing functions to check invalid input. It's too computationally expensive to do the check at the contract layer so the it may need to be implemented as a host function. Jay is seeking ecosystem input around use cases that require strict input validation.
+   2. There were no further concerns.
+3. Increase performance by upgrading Soroban's VM. [CAP Discussion](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0060.md)
+   1. Team's comments were about accuracy of the measurement method but the demonstrated benefits of wall clock time were thought to be promising.
+   2. There was a suggestion to expose performance improvements to contract developers thus creating the incentive to optimize contracts to leverage the improvements.
+   3. There were no further concerns.
diff --git a/meetings/2024/09/05.mdx b/meetings/2024/09/05.mdx
new file mode 100644
index 000000000..6f69a6024
--- /dev/null
+++ b/meetings/2024/09/05.mdx
@@ -0,0 +1,31 @@
+---
+title: "2024-09-05"
+description: "Agenda: Discord thread"
+---
+
+_September 5, 2024_ · [Chris Anatalio](https://github.com/anataliocs), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1bw1KCnF2C6cz0NhWNGKoUOg4oiC-OZck/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+Agenda: [Discord thread](https://discord.com/channels/897514728459468821/900374272751591424/1280678171053789317)
+
+Platform team demonstrated Galexie, a part of CDP(Composable Data Platform):
+
+1. Galexie
+   1. Data Extraction: Extracts raw ledger data from the Stellar network
+   2. Compression: Compresses raw data for efficient storage
+   3. Storage Options: Supports runtime configuration through the Datastore abstraction to use various physical storage layers, starting with Google Cloud Storage (GCS)
+   4. Modes of Operation: Can operate in either batch mode or streaming mode
+2. Composable Data Platform
+   1. Flexible Datastore: Multiple options for physical data storage layers
+   2. Galexie: Used to extract, compress and export data to your chosen Datastore
+   3. Transform: Structure data in a model suitable to your application
+3. Pluggable Data Pipelines
+   1. Workflows: Create ETL(extract, transform, load) pipelines
+   2. Streaming: Fast, lightweight streaming data
diff --git a/meetings/2024/09/12.mdx b/meetings/2024/09/12.mdx
new file mode 100644
index 000000000..b3a72b26a
--- /dev/null
+++ b/meetings/2024/09/12.mdx
@@ -0,0 +1,29 @@
+---
+title: "2024-09-12"
+description: "Agenda: Discord thread"
+---
+
+_September 12, 2024_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1raU1Z9EQBLCkkuUO9yyF8yD2l_3nwk4a/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+Agenda: [Discord thread](https://discord.com/channels/897514728459468821/900374272751591424/1282934024892973077)
+
+Developer Experience team member Nando Vieira introduced the CLI features alias and snapshot:
+
+1. Alias
+   1. Install of Hello World example for showcasing alias
+   2. Showed examples of how contract IDs are often passed as parameters in CLI commands like invoke (copying ID string or command substitution)
+   3. How to deploy a smart contract and create an alias
+   4. How to invoke the smart contract with the alias
+2. Snapshot
+   1. How to create a ledger snapshop
+   2. How to use the snapshot in a test case
+
+Towards the end Nando went through the developer documentation, with focus on the added command line examples for Windows users, and a useful cookbook for CLI commands.
diff --git a/meetings/2024/09/19.mdx b/meetings/2024/09/19.mdx
new file mode 100644
index 000000000..05dd7c619
--- /dev/null
+++ b/meetings/2024/09/19.mdx
@@ -0,0 +1,27 @@
+---
+title: "2024-09-19"
+description: "Agenda: Discord thread"
+---
+
+_September 19, 2024_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1yIzMrtyuJkX6W8MlIbwrGNivYqHuhoxH/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+Agenda: [Discord thread](https://discord.com/channels/897514728459468821/900374272751591424/1285627254130610297)
+
+SDF DevRel team member Carsten Jacobsen showed how to build a simple Hello World dapp based on a Soroban smart contract and Next.js through these steps:
+
+1. Create the default Hello World smart contract using the Stellar CLI
+2. Create TypeScript bindings (package) using the Stellar CLI
+3. Create the default Next.js using the npx create-next-app command
+4. Add and link the TypeScript binding package to the Next.js project
+5. Create a simple frontend with a form to submit a string
+6. Import the package in the Next.js page, and setup a client
+7. Create submit-function to send form value to the smart contract
+8. Use useState to store the smart contract response and display it
diff --git a/meetings/2024/09/26.mdx b/meetings/2024/09/26.mdx
new file mode 100644
index 000000000..3d9febaa6
--- /dev/null
+++ b/meetings/2024/09/26.mdx
@@ -0,0 +1,23 @@
+---
+title: "2024-09-26"
+description: "Agenda: Discord thread"
+---
+
+_September 26, 2024_ · [Chris Anatalio](https://github.com/anataliocs), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1gV-4lV32eN5R5rvtK5SY3aH1FVcbwI7D/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+Agenda: [Discord thread](https://discord.com/channels/897514728459468821/900374272751591424/1288890126038208532)
+
+Summary: Hoops Finance, a DeFi protocol, discussed their platform they are building. https://www.hoops.finance/
+
+1. They abstract away the complexity of DeFi investments for normal users through a series of guided prompts.
+2. Provides simplified access to LP liquidity provisioning abstraction
+3. Public AMM API for read/write data on AMMs on Stellar
+4. Hoops Finance API: https://api.v1.xlm.services/#overview
diff --git a/meetings/2024/10/24.mdx b/meetings/2024/10/24.mdx
new file mode 100644
index 000000000..8f754fe54
--- /dev/null
+++ b/meetings/2024/10/24.mdx
@@ -0,0 +1,26 @@
+---
+title: "2024-10-24"
+description: "Agenda: Discord thread"
+---
+
+_October 24, 2024_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/1saHsJ793C5yQu9pUC9Ao-rAeuIoLjScQ/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+Agenda: [Discord thread](https://discord.com/channels/897514728459468821/900374272751591424/1298362698123182080)
+
+SDF’s Platform team had an internal hackathon last week, with the purpose of building applications utilizing the [Composable Data Platform (CDP)](https://stellar.org/blog/developers/composable-data-platform). In this week’s developer meeting some of the team members present their projects. The apps are widely varied (trading app, fraud detection, JS browser-based ingester, etc) but the intent here is to show how easy CDP is to use.
+
+Projects presented in the meeting:
+
+1. Trade Aggregations Service
+2. Deceptiscan - CDP fraud detection
+3. Composable Data Platform Hackies - data indexer, payment indexer, contract expiration alerter, data indexes in DuckDB, torrents for data indexes and ledger metadata)
+4. Data ingest with frontend JS
+5. Real-time analytics
diff --git a/meetings/2024/11/14.mdx b/meetings/2024/11/14.mdx
new file mode 100644
index 000000000..7a9d6d2b2
--- /dev/null
+++ b/meetings/2024/11/14.mdx
@@ -0,0 +1,28 @@
+---
+title: "2024-11-14"
+description: "Agenda: Discord thread"
+---
+
+_November 14, 2024_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://drive.google.com/file/d/16-QDUaoFTvLD0WUshuVQs1lp36XeuMn9/preview"
+  title="Meeting Playback Video"
+  allow="autoplay; fullscreen"
+  loading="lazy"
+/>
+
+Agenda: [Discord thread](https://discord.com/events/897514728459468821/1304859059425382553/1306725344870400000)
+
+At this week’s developer meeting, Jeesun demonstrated the new Stellar Lab, showcasing its enhanced features designed to improve the developer experience.
+
+The tech stack of the new Stellar Lab was discussed in the meeting, and the following demos were used to show the Lab's functionality:
+
+1. Enable MultiSig Exercise
+2. Stellar Wallets Kit
+3. Create & Fund Account
+4. Save KeyPairs Feature
+5. Save Transactions Feature
+6. XDR to JSON mapping
+7. RPC Methods - including simulateTransaction
diff --git a/meetings/2024/12/05.mdx b/meetings/2024/12/05.mdx
new file mode 100644
index 000000000..f5fa7e400
--- /dev/null
+++ b/meetings/2024/12/05.mdx
@@ -0,0 +1,16 @@
+---
+title: "2024-12-05"
+description: "In this week's call we talk to Alberto Chaves from Trustless Work about building an escrow service on Stellar, followed by a quick introduction to using..."
+---
+
+_December 5, 2024_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/UCYfq-RuQkY?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+In this week's call we talk to Alberto Chaves from Trustless Work about building an escrow service on Stellar, followed by a quick introduction to using AI-based tools to develop Soroban smart contracts.
diff --git a/meetings/2024/12/12.mdx b/meetings/2024/12/12.mdx
new file mode 100644
index 000000000..5733f2da2
--- /dev/null
+++ b/meetings/2024/12/12.mdx
@@ -0,0 +1,16 @@
+---
+title: "2024-12-12"
+description: "In this meeting, SDF Developer Advocate Chris Anatalio talks about the future stack, including smart contract wallets and Passkeys."
+---
+
+_December 12, 2024_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/w_senlMbHVM?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+In this meeting, SDF Developer Advocate Chris Anatalio talks about the future stack, including smart contract wallets and Passkeys. In the second half, SDF Core Software Engineer Siddharth Suresh talks about increasing Soroban limits.
diff --git a/meetings/2024/12/19.mdx b/meetings/2024/12/19.mdx
new file mode 100644
index 000000000..67667af0f
--- /dev/null
+++ b/meetings/2024/12/19.mdx
@@ -0,0 +1,16 @@
+---
+title: "2024-12-19"
+description: "In this meeting SDF Core Software Engineer Jay talks about BLS building blocks, and walks through examples and demos."
+---
+
+_December 19, 2024_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/51SitOUZySk?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+In this meeting SDF Core Software Engineer Jay talks about BLS building blocks, and walks through examples and demos.
diff --git a/meetings/2025-01-16.mdx b/meetings/2025-01-16.mdx
deleted file mode 100644
index 0527400b4..000000000
--- a/meetings/2025-01-16.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "2025-01-16"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="PJx6effsvTA" />
-
-Stellar Development Foundation's Ecosystem DevRel team got together to talk about the past year, and what 2025 brings.
diff --git a/meetings/2025-01-23.mdx b/meetings/2025-01-23.mdx
deleted file mode 100644
index 0e2da587a..000000000
--- a/meetings/2025-01-23.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: "2025-01-23"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="51SitOUZySk" />
-
-<b>Part 1</b>
-
-In this week's meeting Hoops Finance's founders Bastian and Tim talk about the progress they have made, some design considerations and the future of Hoops Finance.
-
-<YouTube ID="JDlIL5y5bn8" />
-
-<b>Part 2</b>
-
-Recording from a protocol meeting where two Core Advancement Proposals -
-
-CAP-62 (Soroban Live State Prioritization) and CAP-66 (Soroban In-memory Read Resource) where discussed.
-
-Here's are some resources to read up on:
-
-CAP-62 - https://github.com/stellar/stellar-protocol/blob/master/core/cap-0062.md<br /> Discussion - https://github.com/stellar/stellar-protocol/discussions/1575
-
-CAP-66 - https://github.com/stellar/stellar-protocol/blob/master/core/cap-0066.md<br /> Discussion - https://github.com/stellar/stellar-protocol/discussions/1585
diff --git a/meetings/2025-01-30.mdx b/meetings/2025-01-30.mdx
deleted file mode 100644
index 60a7f71b3..000000000
--- a/meetings/2025-01-30.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: "2025-01-30"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="1pF9evTU3QE" />
-
-<b>Part 1</b>
-
-RampMeDaddy will be joining us for this Stellar Developer Meeting. RampMeDaddy is currently participating in the Stellar x Draper Embark Program, and we ask what the team is up to, learn more about what they are building and a casual chat about how they are building their dapp on Stellar/Soroban.
-
-Visit their website here: https://rampmedaddy.com
-
-<YouTube ID="ZL1LfJqmw_M" />
-
-<b>Part 2</b>
-
-In this protocol meeting two Core Advancement Proposals are discussed - Dima will be presenting CAP-64 (Memo Authorization for Soroban), and Graydon will be presenting CAP-65 (Reusable Module Cache).
-
-Here are some resources:
-
-CAP-64 - https://github.com/stellar/stellar-protocol/blob/master/core/cap-0064.md<br /> Discussion - https://github.com/stellar/stellar-protocol/discussions/1610
-
-CAP-65 - https://github.com/stellar/stellar-protocol/blob/master/core/cap-0065.md<br /> Discussion - https://github.com/stellar/stellar-protocol/discussions/1615
diff --git a/meetings/2025-02-06.mdx b/meetings/2025-02-06.mdx
deleted file mode 100644
index 8838abb0b..000000000
--- a/meetings/2025-02-06.mdx
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: "2025-02-06"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-## Part 1
-
-<YouTube ID="QrLA66qU9N8" />
-
-The dev team behind Reflector and Refractor presents their tools for decentralized finance and transaction management on Stellar. Reflector delivers on-chain price feeds to enhance DeFi protocols, while Refractor provides a pending transaction storage and multisig aggregator for coordinated signing. They’ll cover how these products support trustless financial interactions and improve smart contract execution on Stellar.
-
-Visit their website here: https://reflector.network
-
-## Part 2
-
-<YouTube ID="lzxv5ij6TLw" />
-
-In this protocol meeting we discuss two Core Advancement Proposals - Dima will be presenting CAP-63 (Parallelism-friendly Transaction Scheduling), and Siddharth will be presenting CAP-67 (Unified Asset Events).
-
-Here are some resources to read up on:
-
-- [CAP-63](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0063.md)
-
-- [CAP-63 Discussion](https://github.com/stellar/stellar-protocol/discussions/1602)
-
-- [CAP-67](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md)
-
-- [CAP-67 Discussion](https://github.com/stellar/stellar-protocol/discussions/1553)
diff --git a/meetings/2025-02-13.mdx b/meetings/2025-02-13.mdx
deleted file mode 100644
index d71d1d262..000000000
--- a/meetings/2025-02-13.mdx
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: "2025-02-13"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-## Part 1
-
-<YouTube ID="8UGDT1pGZYU" />
-
-OrbitLens will showcase StellarBroker and StellarExpert services. StellarBroker is a multi-source liquidity swap router that aggregates liquidity from Soroban AMMs, Classic AMMs, and Classic orderbooks. The second part of the presentation will focus on Stellar smart contracts insights and on-chain transaction analytics using StellarExpert blockchain explorer.
-
-Links:
-
-- [StellarBroker](https://stellar.broker)
-
-- [StellarExpert](https://stellar.expert)
-
-## Part 2
-
-<YouTube ID="u204TwiHJpE" />
-
-This protocol meeting we discuss two Core Advancement Proposals - Dima is presenting CAP-68 and CAP-69, both of which add new host functions.
-
-Here are some resources to read up on:
-
-- [CAP-68](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0068.md)
-
-- [CAP-68 Discussion](https://github.com/stellar/stellar-protocol/discussions/1626)
-
-- [CAP-69](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0069.md)
-
-- [CAP-69 Discussion](https://github.com/stellar/stellar-protocol/discussions/1633)
diff --git a/meetings/2025-02-20.mdx b/meetings/2025-02-20.mdx
deleted file mode 100644
index 48745d596..000000000
--- a/meetings/2025-02-20.mdx
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: "2025-02-20"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-## Part 1
-
-<YouTube ID="2XVt87tG5LI" />
-
-SDF Developer Advocate Elliot Voris gives an introduction to the KaleFail project, and cover how it was built, the purpose and future features. KaleFail is building on top of Kalepail’s KALE project and both serve as fully fledged demo applications, showcasing key Stellar/Soroban features.
-
-Links:
-
-- [KaleFail](https://kalefail.elliotfriend.com)
-
-- [Source Code](https://github.com/elliotfriend/project-kalefail)
-
-- [KALE](https://kalepail.com/kale)
-
-## Part 2
-
-<YouTube ID="hDIP22z6nq4" />
-
-In this protocol meeting, a Core Advancement Proposals is discussed - Siddharth Suresh will will be presenting the memo related updates to CAP-67.
-
-Here are some resources to read up on:
-
-- [CAP-67](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md)
-
-- [Discussion](https://github.com/stellar/stellar-protocol/discussions/1553)
diff --git a/meetings/2025-02-27.mdx b/meetings/2025-02-27.mdx
deleted file mode 100644
index 578c6b108..000000000
--- a/meetings/2025-02-27.mdx
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: "2025-02-27"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-## Part 1
-
-<YouTube ID="hfl1n5BKbs4" />
-
-Blend, a universal liquidity protocol build on Stellar/Soroban, is preparing to release V2 and launched the Blend V2 Audit + Certora Formal Verification competition this past Monday. There are $125K in USDC up for grabs, and the team are joining this week’s meeting to talk about the competition and walk through some code. Join to learn more about Blend and the competition!
-
-Links:
-
-- [Blend](https://www.blend.capital)
-
-- [Competition](https://code4rena.com/audits/2025-02-blend-v2-audit-certora-formal-verification)
-
-## Part 2
-
-<YouTube ID="9oCKAhbFzUY" />
-
-In this protocol meeting Dima's and Leigh's prototypes for dealing with memos/muxed accounts in CAP-67 are discussed, as well as updates to CAP-66 (Soroban In-memory Read Resource).
-
-Links:
-
-- [CAP-66](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0066.md)
-
-- [CAP-66 Discussion](https://github.com/stellar/stellar-protocol/discussions/1585)
-
-- [CAP-67](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md)
-
-- [CAP-67 Discussions](https://github.com/stellar/stellar-protocol/discussions/1553#discussioncomment-12306846) and [CAP-67 Discussions](https://github.com/stellar/stellar-protocol/discussions/1553#discussioncomment-12309408)
diff --git a/meetings/2025-03-06.mdx b/meetings/2025-03-06.mdx
deleted file mode 100644
index 11e3d0260..000000000
--- a/meetings/2025-03-06.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: "2025-03-06"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="e_DH9zIRnu8" />
-
-In this meeting we have a conversation with Christian Santagata from OpenZeppelin about the Stellar x OpenZeppelin multi-year partnership, and talk about what the team is working on in the Stellar ecosystem. The conversation includes topics about Stellar token contracts and token standards, and how to use the OpenZeppelin Contract Wizard that now supports Stellar contracts.
-
-Links:
-
-- [OpenZeppelin Contract Wizard](https://wizard.openzeppelin.com/stellar)
-
-- [OpenZeppelin Stellar Contracts](https://github.com/OpenZeppelin/stellar-contracts)
-
-- [Dev Walkthrough](https://www.youtube.com/watch?v=iD7ZspsZLVo)
diff --git a/meetings/2025-03-27.mdx b/meetings/2025-03-27.mdx
deleted file mode 100644
index 0cb6010bf..000000000
--- a/meetings/2025-03-27.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: "2025-03-27"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-## Part 1
-
-<YouTube ID="zqrE4mWNog0" />
-
-We are meeting with the OpenZeppelin team again to catch up on the latest feature additions, and this time we have invited two of their engineers, Boyan Barakov and Ozgun Ozerk, to answer technical questions from the audience.
-
-Links:
-
-- [OpenZeppelin Contract Wizard](https://wizard.openzeppelin.com/stellar)
-
-- [OpenZeppelin Stellar Contracts](https://github.com/OpenZeppelin/stellar-contracts)
-
-- [Dev Walkthrough](https://www.youtube.com/watch?v=iD7ZspsZLVo)
-
-## Part 2
-
-<YouTube ID="2q3NlmrtmQg" />
-
-This is a short protocol meeting, following up on previous discussions.
diff --git a/meetings/2025-04-03.mdx b/meetings/2025-04-03.mdx
deleted file mode 100644
index a02b752bc..000000000
--- a/meetings/2025-04-03.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: "2025-04-03"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="ea2fTBiLvoM" />
-
-First we take a look at look at Stellar Lab, a lot of features and improvements have been added since we did a Stellar Lab presentation last year. Stellar Lab is a powerful tool for everyone developing on Stellar.
-
-We are looking for community feedback on the Upgradeable Contracts SEP, and will present the details of this proposal.
-
-Links:
-
-- [Stellar Lab](https://lab.stellar.org)
-
-- [Upgradeable Contracts SEP](https://github.com/stellar/stellar-protocol/pull/1671)
diff --git a/meetings/2025-04-10.mdx b/meetings/2025-04-10.mdx
deleted file mode 100644
index b9d80dd67..000000000
--- a/meetings/2025-04-10.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: "2025-04-10"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="346G-EQ8ScY" />
-
-Pamphile (better know as tupui) is a senior software engineer working at Bitpanda. Previously he worked in the team who brought Flight Simulator 2020, and he created a consulting company to work on open source software.
-
-Now he is building his project named Tansu on the Stellar blockchain. Tansu is a decentralized system which aims to secure the software supply chain and break siloed communities by using a DAO.
-
-Link:
-
-- [Tansu](https://tansu.dev)
diff --git a/meetings/2025-04-17.mdx b/meetings/2025-04-17.mdx
deleted file mode 100644
index 93ac66c59..000000000
--- a/meetings/2025-04-17.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: "2025-04-17"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="7O4tOSn_UFc" />
-
-This week we’ll dive into one of the most overlooked tools - Quickstart.
-
-Quickstart is a local Stellar network environment (node) that allows developers to run a local version of the Stellar network for development and testing.
-
-Learn about Quickstart, see how to install it and how to deploy the Hello World sample dapp on Quickstart.
-
-Link:
-
-- [Stellar Quickstart](/docs/tools/quickstart)
diff --git a/meetings/2025-05-01.mdx b/meetings/2025-05-01.mdx
deleted file mode 100644
index 53aa78fc2..000000000
--- a/meetings/2025-05-01.mdx
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: "2025-05-01"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="fuX07T1HUf0" />
-
-We are close to completing the implementation of Whisk, Protocol 23 CAPs, the next step in the CAP lifecycle is voting by the Core CAP team. In this protocol meeting an update was provided on the CAPs and any final questions from the community was answered.
-
-Read up on the CAPs here:
-
-[CAP-62](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0062.md) - [Discussion](https://github.com/orgs/stellar/discussions/1575)
-
-[CAP-63](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0063.md) - [Discussion](https://github.com/orgs/stellar/discussions/1602)
-
-[CAP-65](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0065.md) - [Discussion](https://github.com/orgs/stellar/discussions/1615)
-
-[CAP-66](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0066.md) - [Discussion](https://github.com/orgs/stellar/discussions/1585)
-
-[CAP-67](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md) - [Discussion](https://github.com/orgs/stellar/discussions/1553)
-
-[CAP-68](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0068.md) - [Discussion](https://github.com/orgs/stellar/discussions/1626)
-
-[CAP-69](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0069.md) - [Discussion](https://github.com/orgs/stellar/discussions/1633)
-
-[CAP-70](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0070.md) - [Discussion](https://github.com/orgs/stellar/discussions/1719)
diff --git a/meetings/2025-05-22.mdx b/meetings/2025-05-22.mdx
deleted file mode 100644
index c2f23fcb5..000000000
--- a/meetings/2025-05-22.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "2025-05-22"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="UT8XXdcssQ8" />
-
-At this Stellar Developer Meeting we are having a chat with Bram Hoogenkamp from OpenZeppelin about the OpenZeppelin Monitor - providing monitoring and alerting for smart contracts.
diff --git a/meetings/2025-07-10.mdx b/meetings/2025-07-10.mdx
deleted file mode 100644
index c8ecdc0f6..000000000
--- a/meetings/2025-07-10.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: "2025-07-10"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="0syGaIn3ULk" />
-
-In this call we are getting an update on the exciting Scaffold Stellar project by Fifo from Aha Labs.
-
-Scaffold Stellar is a great way to fast-track new projects built on Stellar. It has starter smart contracts, frontend, plugins and tooling built-in.
-
-[Scaffold Stellar Repo](https://github.com/theahaco/scaffold-stellar)
diff --git a/meetings/2025-07-17.mdx b/meetings/2025-07-17.mdx
deleted file mode 100644
index 9fd78e0ee..000000000
--- a/meetings/2025-07-17.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: "2025-07-17"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="RNtqou5oaeE" />
-
-In this meeting the Nomyx team will give us an introduction to their advanced smart contract architecture (an implementation of the Diamond Pattern) and the Nomyx Diamond proxy viewer interface, that facilitates inspection of deployed diamonds and makes them a bit easier to work with.
-
-They will also be showcasing a live deployment instance of the diamond proxy standard currently used for the Nomyx platform which removes limitations related to the upper contract size limit, allowing developers to launch complex products.
-
-[Nomyx Website](https://www.nomyx.io)
diff --git a/meetings/2025-07-24.mdx b/meetings/2025-07-24.mdx
deleted file mode 100644
index 69cbe9c92..000000000
--- a/meetings/2025-07-24.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: "2025-07-24"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="mSABuOLuZs8" />
-
-In this meeting we are talking to Esteban and Francisco from PaltaLabs. Stellar Hacks is currently running a hackathon in collaboration with PaltaLabs, where the goal is to build using their projects Soroswap and DeFindex.
-
-Let's see how the hackathon is going, and some advice if you are still considering entering, there's still time to enter!
-
-Links:
-
-- [Hackathon](https://dorahacks.io/hackathon/stellar-hacks-paltalabs/detail)
-- [Soroswap](https://docs.soroswap.finance)
-- [DeFindex](https://docs.defindex.io)
diff --git a/meetings/2025-08-07.mdx b/meetings/2025-08-07.mdx
deleted file mode 100644
index 40a3bcfb4..000000000
--- a/meetings/2025-08-07.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: "2025-08-07"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="EuAUCfAWg-4" />
-
-In this meeting we talk to Flashback founder Brieuc Berruet, who participated in the DraperU x Stellar incubator program last year, to get an update on his project (spoiler alert - it's live!).
-
-Learn more about the project, and see a cool demo!
-
-[Flashback Website](https://www.flashback.tech)
diff --git a/meetings/2025-09-25.mdx b/meetings/2025-09-25.mdx
deleted file mode 100644
index df796b371..000000000
--- a/meetings/2025-09-25.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: "2025-09-25"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="bTiFz8VHQyQ" />
-
-In this week’s Stellar Developer Meeting we discuss new Core Advancement Proposals.
-
-Here are some resources to read up on:
-
-[CAP-71](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0071.md) - [Discussion](https://github.com/orgs/stellar/discussions/1784)
-
-[CAP-72](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0072.md) - [Discussion](https://github.com/orgs/stellar/discussions/1763)
-
-[CAP-73](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0073.md) - [Discussion](https://github.com/orgs/stellar/discussions/1668)
diff --git a/meetings/2025-10-02.mdx b/meetings/2025-10-02.mdx
deleted file mode 100644
index 896ee24d5..000000000
--- a/meetings/2025-10-02.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: "2025-10-02"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="8UmxYfDkWLg" />
-
-In this meeting we will discuss CAP-74, BN254 and Poseidon hash functions.
-
-[CAP-74](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0074.md) - [Discussion](https://github.com/orgs/stellar/discussions/1780)
diff --git a/meetings/2025-10-09.mdx b/meetings/2025-10-09.mdx
deleted file mode 100644
index cc468c916..000000000
--- a/meetings/2025-10-09.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: "2025-10-09"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="-uTKQIQpwAU" />
-
-## OpenZeppelin UI Builder demo
-
-We are meeting with the OpenZeppelin team again to catch up on the latest developer tooling work they are doing.
-
-This time Steve will demo UI Builder, an easy way to spin up a front-end for any contract call in seconds. UI Builder allows you to select a function and then it auto-generates a React UI with wallet connect and multi-network support, and exports a complete app.
-
-[OpenZeppelin UI Builder](https://builder.openzeppelin.com)
-
-<YouTube ID="rWWB7-8A-g8" />
-
-## Protocol Discussion
-
-In this Core Advancement Proposal discussion CAP-75 (Host functions for enabling Poseidon and Poseidon2 hash functions) is presented.
-
-This CAP proposes adding host functions for cryptographic primitives enabling Poseidon family of hash functions, which are widely-adopted hash choices in efficient zero-knowledge proof systems. Supporting these as host functions in Soroban can facilitate adoption of ZK applications and interoperability with other ecosystems.
-
-Link to [CAP-75](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0075.md)
diff --git a/meetings/2025-10-16.mdx b/meetings/2025-10-16.mdx
deleted file mode 100644
index 7bea1e6fd..000000000
--- a/meetings/2025-10-16.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: "2025-10-16"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="cafR1uVsPFM" />
-
-## Protocol Discussion
-
-In this call the recent state archival issue, introduced by Whisk (Protocol 23), is discussed. Questions from community builders are also answered.
diff --git a/meetings/2025-10-23.mdx b/meetings/2025-10-23.mdx
deleted file mode 100644
index 3f14427c0..000000000
--- a/meetings/2025-10-23.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: "2025-10-23"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="-nY8U8nNmas" />
-
-In this meeting we are talking to Dobprotocol to learn more about how they use Stellar to build a unique platform, turning machines into investable assets.
-
-Website: https://www.dobprotocol.com
diff --git a/meetings/2025-10-30.mdx b/meetings/2025-10-30.mdx
deleted file mode 100644
index 561836fe0..000000000
--- a/meetings/2025-10-30.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: "2025-10-30"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="nxU16dOjN3M" />
-
-In this meeting we are continuing our mini series about the Stellar-based open source tooling OpenZeppelin is developing. In the last session we talked briefly about Relayer and this time we are diving deeper into this tool, and OpenZeppelin Managed Service.
-
-OpenZeppelin Relayer: https://docs.openzeppelin.com/relayer
diff --git a/meetings/2025-11-06.mdx b/meetings/2025-11-06.mdx
deleted file mode 100644
index aa6cc2e3e..000000000
--- a/meetings/2025-11-06.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: "2025-11-06"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="-T3Ia32nnP0" />
-
-In this meeting we do a walkthrough of OpenZeppelin’s Q3 library releases for Smart Account, Vault and RWA.
-
-Links to docs:
-
-- Smart Account: https://docs.openzeppelin.com/stellar-contracts/accounts/smart-account
-- Vault: https://docs.openzeppelin.com/stellar-contracts/tokens/vault/vault
-- RWA: https://docs.openzeppelin.com/stellar-contracts/tokens/rwa/rwa
diff --git a/meetings/2025/01/16.mdx b/meetings/2025/01/16.mdx
new file mode 100644
index 000000000..dd74271dc
--- /dev/null
+++ b/meetings/2025/01/16.mdx
@@ -0,0 +1,16 @@
+---
+title: "2025-01-16"
+description: "Stellar Development Foundation's Ecosystem DevRel team got together to talk about the past year, and what 2025 brings."
+---
+
+_January 16, 2025_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/PJx6effsvTA?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+Stellar Development Foundation's Ecosystem DevRel team got together to talk about the past year, and what 2025 brings.
diff --git a/meetings/2025/01/23.mdx b/meetings/2025/01/23.mdx
new file mode 100644
index 000000000..1e3da710b
--- /dev/null
+++ b/meetings/2025/01/23.mdx
@@ -0,0 +1,38 @@
+---
+title: "2025-01-23"
+description: "In this week's meeting Hoops Finance's founders Bastian and Tim talk about the progress they have made, some design considerations and the future of Hoops..."
+---
+
+_January 23, 2025_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/51SitOUZySk?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+<b>Part 1</b>
+
+In this week's meeting Hoops Finance's founders Bastian and Tim talk about the progress they have made, some design considerations and the future of Hoops Finance.
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/JDlIL5y5bn8?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+<b>Part 2</b>
+
+Recording from a protocol meeting where two Core Advancement Proposals -
+
+CAP-62 (Soroban Live State Prioritization) and CAP-66 (Soroban In-memory Read Resource) where discussed.
+
+Here's are some resources to read up on:
+
+CAP-62 - https://github.com/stellar/stellar-protocol/blob/master/core/cap-0062.md<br /> Discussion - https://github.com/stellar/stellar-protocol/discussions/1575
+
+CAP-66 - https://github.com/stellar/stellar-protocol/blob/master/core/cap-0066.md<br /> Discussion - https://github.com/stellar/stellar-protocol/discussions/1585
diff --git a/meetings/2025/01/30.mdx b/meetings/2025/01/30.mdx
new file mode 100644
index 000000000..2c36e3156
--- /dev/null
+++ b/meetings/2025/01/30.mdx
@@ -0,0 +1,38 @@
+---
+title: "2025-01-30"
+description: "RampMeDaddy will be joining us for this Stellar Developer Meeting."
+---
+
+_January 30, 2025_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/1pF9evTU3QE?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+<b>Part 1</b>
+
+RampMeDaddy will be joining us for this Stellar Developer Meeting. RampMeDaddy is currently participating in the Stellar x Draper Embark Program, and we ask what the team is up to, learn more about what they are building and a casual chat about how they are building their dapp on Stellar/Soroban.
+
+Visit their website here: https://rampmedaddy.com
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/ZL1LfJqmw_M?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+<b>Part 2</b>
+
+In this protocol meeting two Core Advancement Proposals are discussed - Dima will be presenting CAP-64 (Memo Authorization for Soroban), and Graydon will be presenting CAP-65 (Reusable Module Cache).
+
+Here are some resources:
+
+CAP-64 - https://github.com/stellar/stellar-protocol/blob/master/core/cap-0064.md<br /> Discussion - https://github.com/stellar/stellar-protocol/discussions/1610
+
+CAP-65 - https://github.com/stellar/stellar-protocol/blob/master/core/cap-0065.md<br /> Discussion - https://github.com/stellar/stellar-protocol/discussions/1615
diff --git a/meetings/2025/02/06.mdx b/meetings/2025/02/06.mdx
new file mode 100644
index 000000000..18f6dadd1
--- /dev/null
+++ b/meetings/2025/02/06.mdx
@@ -0,0 +1,42 @@
+---
+title: "2025-02-06"
+description: "The dev team behind Reflector and Refractor presents their tools for decentralized finance and transaction management on Stellar."
+---
+
+_February 6, 2025_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+## Part 1
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/QrLA66qU9N8?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+The dev team behind Reflector and Refractor presents their tools for decentralized finance and transaction management on Stellar. Reflector delivers on-chain price feeds to enhance DeFi protocols, while Refractor provides a pending transaction storage and multisig aggregator for coordinated signing. They’ll cover how these products support trustless financial interactions and improve smart contract execution on Stellar.
+
+Visit their website here: https://reflector.network
+
+## Part 2
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/lzxv5ij6TLw?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+In this protocol meeting we discuss two Core Advancement Proposals - Dima will be presenting CAP-63 (Parallelism-friendly Transaction Scheduling), and Siddharth will be presenting CAP-67 (Unified Asset Events).
+
+Here are some resources to read up on:
+
+- [CAP-63](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0063.md)
+
+- [CAP-63 Discussion](https://github.com/stellar/stellar-protocol/discussions/1602)
+
+- [CAP-67](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md)
+
+- [CAP-67 Discussion](https://github.com/stellar/stellar-protocol/discussions/1553)
diff --git a/meetings/2025/02/13.mdx b/meetings/2025/02/13.mdx
new file mode 100644
index 000000000..3ed78ca29
--- /dev/null
+++ b/meetings/2025/02/13.mdx
@@ -0,0 +1,46 @@
+---
+title: "2025-02-13"
+description: "OrbitLens will showcase StellarBroker and StellarExpert services."
+---
+
+_February 13, 2025_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+## Part 1
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/8UGDT1pGZYU?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+OrbitLens will showcase StellarBroker and StellarExpert services. StellarBroker is a multi-source liquidity swap router that aggregates liquidity from Soroban AMMs, Classic AMMs, and Classic orderbooks. The second part of the presentation will focus on Stellar smart contracts insights and on-chain transaction analytics using StellarExpert blockchain explorer.
+
+Links:
+
+- [StellarBroker](https://stellar.broker)
+
+- [StellarExpert](https://stellar.expert)
+
+## Part 2
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/u204TwiHJpE?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+This protocol meeting we discuss two Core Advancement Proposals - Dima is presenting CAP-68 and CAP-69, both of which add new host functions.
+
+Here are some resources to read up on:
+
+- [CAP-68](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0068.md)
+
+- [CAP-68 Discussion](https://github.com/stellar/stellar-protocol/discussions/1626)
+
+- [CAP-69](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0069.md)
+
+- [CAP-69 Discussion](https://github.com/stellar/stellar-protocol/discussions/1633)
diff --git a/meetings/2025/02/20.mdx b/meetings/2025/02/20.mdx
new file mode 100644
index 000000000..2bf19be1c
--- /dev/null
+++ b/meetings/2025/02/20.mdx
@@ -0,0 +1,44 @@
+---
+title: "2025-02-20"
+description: "SDF Developer Advocate Elliot Voris gives an introduction to the KaleFail project, and cover how it was built, the purpose and future features."
+---
+
+_February 20, 2025_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+## Part 1
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/2XVt87tG5LI?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+SDF Developer Advocate Elliot Voris gives an introduction to the KaleFail project, and cover how it was built, the purpose and future features. KaleFail is building on top of Kalepail’s KALE project and both serve as fully fledged demo applications, showcasing key Stellar/Soroban features.
+
+Links:
+
+- [KaleFail](https://kalefail.elliotfriend.com)
+
+- [Source Code](https://github.com/elliotfriend/project-kalefail)
+
+- [KALE](https://kalepail.com/kale)
+
+## Part 2
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/hDIP22z6nq4?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+In this protocol meeting, a Core Advancement Proposals is discussed - Siddharth Suresh will will be presenting the memo related updates to CAP-67.
+
+Here are some resources to read up on:
+
+- [CAP-67](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md)
+
+- [Discussion](https://github.com/stellar/stellar-protocol/discussions/1553)
diff --git a/meetings/2025/02/27.mdx b/meetings/2025/02/27.mdx
new file mode 100644
index 000000000..be35803ca
--- /dev/null
+++ b/meetings/2025/02/27.mdx
@@ -0,0 +1,46 @@
+---
+title: "2025-02-27"
+description: "Blend, a universal liquidity protocol build on Stellar/Soroban, is preparing to release V2 and launched the Blend V2 Audit + Certora Formal Verification..."
+---
+
+_February 27, 2025_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+## Part 1
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/hfl1n5BKbs4?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+Blend, a universal liquidity protocol build on Stellar/Soroban, is preparing to release V2 and launched the Blend V2 Audit + Certora Formal Verification competition this past Monday. There are $125K in USDC up for grabs, and the team are joining this week’s meeting to talk about the competition and walk through some code. Join to learn more about Blend and the competition!
+
+Links:
+
+- [Blend](https://www.blend.capital)
+
+- [Competition](https://code4rena.com/audits/2025-02-blend-v2-audit-certora-formal-verification)
+
+## Part 2
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/9oCKAhbFzUY?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+In this protocol meeting Dima's and Leigh's prototypes for dealing with memos/muxed accounts in CAP-67 are discussed, as well as updates to CAP-66 (Soroban In-memory Read Resource).
+
+Links:
+
+- [CAP-66](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0066.md)
+
+- [CAP-66 Discussion](https://github.com/stellar/stellar-protocol/discussions/1585)
+
+- [CAP-67](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md)
+
+- [CAP-67 Discussions](https://github.com/stellar/stellar-protocol/discussions/1553#discussioncomment-12306846) and [CAP-67 Discussions](https://github.com/stellar/stellar-protocol/discussions/1553#discussioncomment-12309408)
diff --git a/meetings/2025/03/06.mdx b/meetings/2025/03/06.mdx
new file mode 100644
index 000000000..245b485c8
--- /dev/null
+++ b/meetings/2025/03/06.mdx
@@ -0,0 +1,24 @@
+---
+title: "2025-03-06"
+description: "In this meeting we have a conversation with Christian Santagata from OpenZeppelin about the Stellar x OpenZeppelin multi-year partnership, and talk about..."
+---
+
+_March 6, 2025_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/e_DH9zIRnu8?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+In this meeting we have a conversation with Christian Santagata from OpenZeppelin about the Stellar x OpenZeppelin multi-year partnership, and talk about what the team is working on in the Stellar ecosystem. The conversation includes topics about Stellar token contracts and token standards, and how to use the OpenZeppelin Contract Wizard that now supports Stellar contracts.
+
+Links:
+
+- [OpenZeppelin Contract Wizard](https://wizard.openzeppelin.com/stellar)
+
+- [OpenZeppelin Stellar Contracts](https://github.com/OpenZeppelin/stellar-contracts)
+
+- [Dev Walkthrough](https://www.youtube.com/watch?v=iD7ZspsZLVo)
diff --git a/meetings/2025/03/27.mdx b/meetings/2025/03/27.mdx
new file mode 100644
index 000000000..9a597d488
--- /dev/null
+++ b/meetings/2025/03/27.mdx
@@ -0,0 +1,38 @@
+---
+title: "2025-03-27"
+description: "We are meeting with the OpenZeppelin team again to catch up on the latest feature additions, and this time we have invited two of their engineers, Boyan..."
+---
+
+_March 27, 2025_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+## Part 1
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/zqrE4mWNog0?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+We are meeting with the OpenZeppelin team again to catch up on the latest feature additions, and this time we have invited two of their engineers, Boyan Barakov and Ozgun Ozerk, to answer technical questions from the audience.
+
+Links:
+
+- [OpenZeppelin Contract Wizard](https://wizard.openzeppelin.com/stellar)
+
+- [OpenZeppelin Stellar Contracts](https://github.com/OpenZeppelin/stellar-contracts)
+
+- [Dev Walkthrough](https://www.youtube.com/watch?v=iD7ZspsZLVo)
+
+## Part 2
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/2q3NlmrtmQg?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+This is a short protocol meeting, following up on previous discussions.
diff --git a/meetings/2025/04/03.mdx b/meetings/2025/04/03.mdx
new file mode 100644
index 000000000..e4071ade8
--- /dev/null
+++ b/meetings/2025/04/03.mdx
@@ -0,0 +1,24 @@
+---
+title: "2025-04-03"
+description: "First we take a look at look at Stellar Lab, a lot of features and improvements have been added since we did a Stellar Lab presentation last year."
+---
+
+_April 3, 2025_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/ea2fTBiLvoM?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+First we take a look at look at Stellar Lab, a lot of features and improvements have been added since we did a Stellar Lab presentation last year. Stellar Lab is a powerful tool for everyone developing on Stellar.
+
+We are looking for community feedback on the Upgradeable Contracts SEP, and will present the details of this proposal.
+
+Links:
+
+- [Stellar Lab](https://lab.stellar.org)
+
+- [Upgradeable Contracts SEP](https://github.com/stellar/stellar-protocol/pull/1671)
diff --git a/meetings/2025/04/10.mdx b/meetings/2025/04/10.mdx
new file mode 100644
index 000000000..f59852e6f
--- /dev/null
+++ b/meetings/2025/04/10.mdx
@@ -0,0 +1,22 @@
+---
+title: "2025-04-10"
+description: "Pamphile (better know as tupui) is a senior software engineer working at Bitpanda."
+---
+
+_April 10, 2025_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/346G-EQ8ScY?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+Pamphile (better know as tupui) is a senior software engineer working at Bitpanda. Previously he worked in the team who brought Flight Simulator 2020, and he created a consulting company to work on open source software.
+
+Now he is building his project named Tansu on the Stellar blockchain. Tansu is a decentralized system which aims to secure the software supply chain and break siloed communities by using a DAO.
+
+Link:
+
+- [Tansu](https://tansu.dev)
diff --git a/meetings/2025/04/17.mdx b/meetings/2025/04/17.mdx
new file mode 100644
index 000000000..04941dc1a
--- /dev/null
+++ b/meetings/2025/04/17.mdx
@@ -0,0 +1,24 @@
+---
+title: "2025-04-17"
+description: "This week we’ll dive into one of the most overlooked tools - Quickstart."
+---
+
+_April 17, 2025_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/7O4tOSn_UFc?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+This week we’ll dive into one of the most overlooked tools - Quickstart.
+
+Quickstart is a local Stellar network environment (node) that allows developers to run a local version of the Stellar network for development and testing.
+
+Learn about Quickstart, see how to install it and how to deploy the Hello World sample dapp on Quickstart.
+
+Link:
+
+- [Stellar Quickstart](/docs/tools/quickstart)
diff --git a/meetings/2025/05/01.mdx b/meetings/2025/05/01.mdx
new file mode 100644
index 000000000..e26939b13
--- /dev/null
+++ b/meetings/2025/05/01.mdx
@@ -0,0 +1,34 @@
+---
+title: "2025-05-01"
+description: "We are close to completing the implementation of Whisk, Protocol 23 CAPs, the next step in the CAP lifecycle is voting by the Core CAP team."
+---
+
+_May 1, 2025_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/fuX07T1HUf0?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+We are close to completing the implementation of Whisk, Protocol 23 CAPs, the next step in the CAP lifecycle is voting by the Core CAP team. In this protocol meeting an update was provided on the CAPs and any final questions from the community was answered.
+
+Read up on the CAPs here:
+
+[CAP-62](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0062.md) - [Discussion](https://github.com/orgs/stellar/discussions/1575)
+
+[CAP-63](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0063.md) - [Discussion](https://github.com/orgs/stellar/discussions/1602)
+
+[CAP-65](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0065.md) - [Discussion](https://github.com/orgs/stellar/discussions/1615)
+
+[CAP-66](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0066.md) - [Discussion](https://github.com/orgs/stellar/discussions/1585)
+
+[CAP-67](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md) - [Discussion](https://github.com/orgs/stellar/discussions/1553)
+
+[CAP-68](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0068.md) - [Discussion](https://github.com/orgs/stellar/discussions/1626)
+
+[CAP-69](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0069.md) - [Discussion](https://github.com/orgs/stellar/discussions/1633)
+
+[CAP-70](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0070.md) - [Discussion](https://github.com/orgs/stellar/discussions/1719)
diff --git a/meetings/2025/05/22.mdx b/meetings/2025/05/22.mdx
new file mode 100644
index 000000000..2f300ce8a
--- /dev/null
+++ b/meetings/2025/05/22.mdx
@@ -0,0 +1,16 @@
+---
+title: "2025-05-22"
+description: "At this Stellar Developer Meeting we are having a chat with Bram Hoogenkamp from OpenZeppelin about the OpenZeppelin Monitor - providing monitoring and..."
+---
+
+_May 22, 2025_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/UT8XXdcssQ8?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+At this Stellar Developer Meeting we are having a chat with Bram Hoogenkamp from OpenZeppelin about the OpenZeppelin Monitor - providing monitoring and alerting for smart contracts.
diff --git a/meetings/2025/07/10.mdx b/meetings/2025/07/10.mdx
new file mode 100644
index 000000000..0e4c75884
--- /dev/null
+++ b/meetings/2025/07/10.mdx
@@ -0,0 +1,20 @@
+---
+title: "2025-07-10"
+description: "In this call we are getting an update on the exciting Scaffold Stellar project by Fifo from Aha Labs."
+---
+
+_July 10, 2025_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/0syGaIn3ULk?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+In this call we are getting an update on the exciting Scaffold Stellar project by Fifo from Aha Labs.
+
+Scaffold Stellar is a great way to fast-track new projects built on Stellar. It has starter smart contracts, frontend, plugins and tooling built-in.
+
+[Scaffold Stellar Repo](https://github.com/theahaco/scaffold-stellar)
diff --git a/meetings/2025/07/17.mdx b/meetings/2025/07/17.mdx
new file mode 100644
index 000000000..facbdfe85
--- /dev/null
+++ b/meetings/2025/07/17.mdx
@@ -0,0 +1,20 @@
+---
+title: "2025-07-17"
+description: "In this meeting the Nomyx team will give us an introduction to their advanced smart contract architecture (an implementation of the Diamond Pattern) and the..."
+---
+
+_July 17, 2025_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/RNtqou5oaeE?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+In this meeting the Nomyx team will give us an introduction to their advanced smart contract architecture (an implementation of the Diamond Pattern) and the Nomyx Diamond proxy viewer interface, that facilitates inspection of deployed diamonds and makes them a bit easier to work with.
+
+They will also be showcasing a live deployment instance of the diamond proxy standard currently used for the Nomyx platform which removes limitations related to the upper contract size limit, allowing developers to launch complex products.
+
+[Nomyx Website](https://www.nomyx.io)
diff --git a/meetings/2025/07/24.mdx b/meetings/2025/07/24.mdx
new file mode 100644
index 000000000..70245746e
--- /dev/null
+++ b/meetings/2025/07/24.mdx
@@ -0,0 +1,24 @@
+---
+title: "2025-07-24"
+description: "In this meeting we are talking to Esteban and Francisco from PaltaLabs."
+---
+
+_July 24, 2025_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/mSABuOLuZs8?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+In this meeting we are talking to Esteban and Francisco from PaltaLabs. Stellar Hacks is currently running a hackathon in collaboration with PaltaLabs, where the goal is to build using their projects Soroswap and DeFindex.
+
+Let's see how the hackathon is going, and some advice if you are still considering entering, there's still time to enter!
+
+Links:
+
+- [Hackathon](https://dorahacks.io/hackathon/stellar-hacks-paltalabs/detail)
+- [Soroswap](https://docs.soroswap.finance)
+- [DeFindex](https://docs.defindex.io)
diff --git a/meetings/2025/08/07.mdx b/meetings/2025/08/07.mdx
new file mode 100644
index 000000000..12d57cdb5
--- /dev/null
+++ b/meetings/2025/08/07.mdx
@@ -0,0 +1,20 @@
+---
+title: "2025-08-07"
+description: "In this meeting we talk to Flashback founder Brieuc Berruet, who participated in the DraperU x Stellar incubator program last year, to get an update on his..."
+---
+
+_August 7, 2025_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/EuAUCfAWg-4?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+In this meeting we talk to Flashback founder Brieuc Berruet, who participated in the DraperU x Stellar incubator program last year, to get an update on his project (spoiler alert - it's live!).
+
+Learn more about the project, and see a cool demo!
+
+[Flashback Website](https://www.flashback.tech)
diff --git a/meetings/2025/09/25.mdx b/meetings/2025/09/25.mdx
new file mode 100644
index 000000000..7755e72f2
--- /dev/null
+++ b/meetings/2025/09/25.mdx
@@ -0,0 +1,24 @@
+---
+title: "2025-09-25"
+description: "In this week’s Stellar Developer Meeting we discuss new Core Advancement Proposals."
+---
+
+_September 25, 2025_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/bTiFz8VHQyQ?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+In this week’s Stellar Developer Meeting we discuss new Core Advancement Proposals.
+
+Here are some resources to read up on:
+
+[CAP-71](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0071.md) - [Discussion](https://github.com/orgs/stellar/discussions/1784)
+
+[CAP-72](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0072.md) - [Discussion](https://github.com/orgs/stellar/discussions/1763)
+
+[CAP-73](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0073.md) - [Discussion](https://github.com/orgs/stellar/discussions/1668)
diff --git a/meetings/2025/10/02.mdx b/meetings/2025/10/02.mdx
new file mode 100644
index 000000000..9a9597e53
--- /dev/null
+++ b/meetings/2025/10/02.mdx
@@ -0,0 +1,18 @@
+---
+title: "2025-10-02"
+description: "In this meeting we will discuss CAP-74, BN254 and Poseidon hash functions."
+---
+
+_October 2, 2025_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/8UmxYfDkWLg?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+In this meeting we will discuss CAP-74, BN254 and Poseidon hash functions.
+
+[CAP-74](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0074.md) - [Discussion](https://github.com/orgs/stellar/discussions/1780)
diff --git a/meetings/2025/10/09.mdx b/meetings/2025/10/09.mdx
new file mode 100644
index 000000000..d91358ab5
--- /dev/null
+++ b/meetings/2025/10/09.mdx
@@ -0,0 +1,38 @@
+---
+title: "2025-10-09"
+description: "We are meeting with the OpenZeppelin team again to catch up on the latest developer tooling work they are doing."
+---
+
+_October 9, 2025_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/-uTKQIQpwAU?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## OpenZeppelin UI Builder demo
+
+We are meeting with the OpenZeppelin team again to catch up on the latest developer tooling work they are doing.
+
+This time Steve will demo UI Builder, an easy way to spin up a front-end for any contract call in seconds. UI Builder allows you to select a function and then it auto-generates a React UI with wallet connect and multi-network support, and exports a complete app.
+
+[OpenZeppelin UI Builder](https://builder.openzeppelin.com)
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/rWWB7-8A-g8?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## Protocol Discussion
+
+In this Core Advancement Proposal discussion CAP-75 (Host functions for enabling Poseidon and Poseidon2 hash functions) is presented.
+
+This CAP proposes adding host functions for cryptographic primitives enabling Poseidon family of hash functions, which are widely-adopted hash choices in efficient zero-knowledge proof systems. Supporting these as host functions in Soroban can facilitate adoption of ZK applications and interoperability with other ecosystems.
+
+Link to [CAP-75](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0075.md)
diff --git a/meetings/2025/10/16.mdx b/meetings/2025/10/16.mdx
new file mode 100644
index 000000000..f9d06ef6f
--- /dev/null
+++ b/meetings/2025/10/16.mdx
@@ -0,0 +1,18 @@
+---
+title: "2025-10-16"
+description: "In this call the recent state archival issue, introduced by Whisk (Protocol 23), is discussed."
+---
+
+_October 16, 2025_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/cafR1uVsPFM?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## Protocol Discussion
+
+In this call the recent state archival issue, introduced by Whisk (Protocol 23), is discussed. Questions from community builders are also answered.
diff --git a/meetings/2025/10/23.mdx b/meetings/2025/10/23.mdx
new file mode 100644
index 000000000..c64e4c981
--- /dev/null
+++ b/meetings/2025/10/23.mdx
@@ -0,0 +1,18 @@
+---
+title: "2025-10-23"
+description: "In this meeting we are talking to Dobprotocol to learn more about how they use Stellar to build a unique platform, turning machines into investable assets."
+---
+
+_October 23, 2025_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/-nY8U8nNmas?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+In this meeting we are talking to Dobprotocol to learn more about how they use Stellar to build a unique platform, turning machines into investable assets.
+
+Website: https://www.dobprotocol.com
diff --git a/meetings/2025/10/30.mdx b/meetings/2025/10/30.mdx
new file mode 100644
index 000000000..4b90f8e3f
--- /dev/null
+++ b/meetings/2025/10/30.mdx
@@ -0,0 +1,18 @@
+---
+title: "2025-10-30"
+description: "In this meeting we are continuing our mini series about the Stellar-based open source tooling OpenZeppelin is developing."
+---
+
+_October 30, 2025_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/nxU16dOjN3M?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+In this meeting we are continuing our mini series about the Stellar-based open source tooling OpenZeppelin is developing. In the last session we talked briefly about Relayer and this time we are diving deeper into this tool, and OpenZeppelin Managed Service.
+
+OpenZeppelin Relayer: https://docs.openzeppelin.com/relayer
diff --git a/meetings/2025/11/06.mdx b/meetings/2025/11/06.mdx
new file mode 100644
index 000000000..260b783ab
--- /dev/null
+++ b/meetings/2025/11/06.mdx
@@ -0,0 +1,22 @@
+---
+title: "2025-11-06"
+description: "In this meeting we do a walkthrough of OpenZeppelin’s Q3 library releases for Smart Account, Vault and RWA."
+---
+
+_November 6, 2025_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/-T3Ia32nnP0?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+In this meeting we do a walkthrough of OpenZeppelin’s Q3 library releases for Smart Account, Vault and RWA.
+
+Links to docs:
+
+- Smart Account: https://docs.openzeppelin.com/stellar-contracts/accounts/smart-account
+- Vault: https://docs.openzeppelin.com/stellar-contracts/tokens/vault/vault
+- RWA: https://docs.openzeppelin.com/stellar-contracts/tokens/rwa/rwa
diff --git a/meetings/2026-01-22.mdx b/meetings/2026-01-22.mdx
deleted file mode 100644
index 1bbd62026..000000000
--- a/meetings/2026-01-22.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: "2026-01-22"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="pq4xrdRzfIs" />
-
-## OpenZeppelin Q4 Releases
-
-In this year’s first Stellar Developer Meeting, on Thursday, January 22nd at 8am PT on Twitch, we will catch up with Ozgun and Boyan from the OpenZeppelin team and take a look at the libraries released in Q4 last year.
-
-<YouTube ID="CetcWbsdRdE" />
-
-## Protocol Discussion
-
-We had three CAPs prepared for this meeting. CAP-77 will provide a way to make ledger keys inaccessible based on the network configuration upgrade performed with a validator vote. CAP-78 proposes an interface which allows developers to specify TTL extension policies such as 'if an entry TTL is less than 29 days, extend it to have 30 days TTL'. CAP-79 introduces host functions for converting Stellar strkey format strings to/from Address/MuxedAddress objects.
-
-Read more about the proposals here:
-
-[CAP-77](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0077.md) - [Discussion](https://github.com/orgs/stellar/discussions/1811)
-
-[CAP-78](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0078.md) - [Discussion](https://github.com/orgs/stellar/discussions/1825)
-
-[CAP-79](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0079.md) - [Discussion](https://github.com/orgs/stellar/discussions/1840)
diff --git a/meetings/2026-01-29.mdx b/meetings/2026-01-29.mdx
deleted file mode 100644
index 48a4ea9f0..000000000
--- a/meetings/2026-01-29.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: "2026-01-29"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="TXuKiEEwEsU" />
-
-## Protocol Discussion
-
-We have one new CAP to discuss and that is CAP-80. This proposal adds BN254 Multi-Scalar Multiplication and modular arithmetic used in a variety of ZK proof applications. Adding host support for these will greatly improve the performance of these use cases.
-
-We also follow up on a previous CAP - the CAP-73.
-
-Read more about the proposal here:
-
-[CAP-80](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0080.md) - [Discussion](https://github.com/orgs/stellar/discussions/1826)
-
-[CAP-73](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0073.md) - [Discussion](https://github.com/orgs/stellar/discussions/1668)
diff --git a/meetings/2026-02-26.mdx b/meetings/2026-02-26.mdx
deleted file mode 100644
index 9dab0a04f..000000000
--- a/meetings/2026-02-26.mdx
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title: "2026-02-26"
-authors: carstenjacobsen
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="nLxODJal-xQ" />
-
-## Protocol Discussion
-
-In this protocol meeting we had two CAPs to discuss and that was CAP-81 and CAP-82.
-
-CAP-81: This CAP introduces a simpler and more efficient eviction scan process. Instead of scanning the BucketList, the new eviction scan just uses in-memory Soroban state. This simplifies the logic while reducing disk reads and speeding up eviction speed.
-
-CAP-82: This CAP adds checked variants of the existing 256-bit integer arithmetic host functions. Unlike the existing functions which trap on overflow, the checked variants return Void on overflow, allowing contracts to handle arithmetic errors gracefully.
-
-Read more about the proposals here:
-
-[CAP-81](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0081.md) - [Discussion](https://github.com/orgs/stellar/discussions/1868)
-
-[CAP-82](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0082.md) - [Discussion](https://github.com/orgs/stellar/discussions/1834)
diff --git a/meetings/2026-04-16.mdx b/meetings/2026-04-16.mdx
deleted file mode 100644
index ec974fa41..000000000
--- a/meetings/2026-04-16.mdx
+++ /dev/null
@@ -1,112 +0,0 @@
----
-title: "2026-04-16"
-authors: kaankacar
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="u3zmNZXHYHw" />
-
-## Protocol 26 "Yardstick" Hits Testnet
-
-Protocol 26, codenamed Yardstick, went live on testnet on April 16, 2026 at 17:00 UTC — literally the day of this meeting. Mainnet validator votes are scheduled for May 6th. If you are running any kind of infrastructure on Stellar — nodes, SDKs, integrations — now is the time to pull the Protocol 26 changes, update your SDKs, and test against testnet before the mainnet vote. The `#protocol-next` channel in the Stellar developer Discord is where the ecosystem coordinates during upgrades.
-
-Two CAPs shipped with this release:
-
-**CAP-81** rewrites the Soroban eviction scan. Instead of scanning the BucketList on disk, eviction now works directly from in-memory Soroban state. The result is faster evictions, fewer disk reads, and more efficient node operations. This is the kind of under-the-hood improvement that compounds as Soroban usage grows — less I/O overhead means the network handles growing state more gracefully at scale.
-
-**CAP-82** adds checked arithmetic variants for the existing 256-bit integer host functions. Where the current functions trap on overflow, the new checked variants return `Void` instead, letting contracts handle arithmetic errors explicitly and gracefully rather than panicking. If you're writing DeFi contracts — lending protocols, swap routers, pricing curves — this matters: checked arithmetic means operations fail explicitly and predictably instead of silently wrapping or trapping.
-
-[CAP-81](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0081.md) — [Discussion](https://github.com/orgs/stellar/discussions/1868)
-
-[CAP-82](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0082.md) — [Discussion](https://github.com/orgs/stellar/discussions/1834)
-
-## Ecosystem Snapshot: $2B in Tokenized Real-World Assets
-
-Stellar has crossed $2 billion in tokenized real-world assets on the network — more than 4x growth in 12 months and 2.5x growth year-to-date as of April. This is not speculative TVL. These are actual financial instruments: tokenized treasuries, bonds, and private credit sitting on-chain today. The institutional names driving this are serious: Franklin Templeton's tokenized treasury fund, Ondo Finance, RedSwan Digital, and Centrifuge. These are not crypto-native experiments — these are traditional finance institutions choosing Stellar as their settlement layer.
-
-What makes this meaningful for developers is that those $2 billion in assets do not just sit there. They are becoming collateral in lending protocols, being deployed in DeFi, and earning yields. That creates real primitives to build on top of.
-
-## DeFi Ecosystem Update
-
-The Stellar DeFi ecosystem is maturing quickly. Here is the current state:
-
-**Blend** has crossed $80 million in TVL, making it one of the most significant lending protocol deployments on Stellar.
-
-**Stellar Templars Protocol** added six new real-world assets to lending markets on Stellar. You can now borrow stablecoins against tokenized institutional assets. The newly added collateral types include:
-
-- **DEJA** (Centrifuge) — a AAA-rated CLO strategy
-- **DEJTRY** — the Janus Henderson short-term US Treasury strategy
-- **CETES** and **USTRY** (EtherFuse) — tokenized Mexican and US Treasury exposure
-- **soBTC/USDC pair** — you can now use Bitcoin as collateral to borrow on Stellar
-
-Institutional-grade RWAs as DeFi collateral is a significant milestone. Sovereign debt meeting DeFi accessibility is a phrase worth sitting with.
-
-**Sushi** deployed their first concentrated liquidity DEX on Stellar. PYUSD/USDC and XLM/USDC pools are live. Cross-chain functionality is coming soon through Squid Router, which connects Stellar assets to 80+ other blockchains.
-
-**EURA** — a MiCA-compliant euro stablecoin from All Unity — is live on Stellar. This is a fully backed, regulated euro stablecoin built for institutional use. A regulated euro stablecoin on Stellar is a notable addition for builders targeting European markets or building compliant financial applications.
-
-For a full picture of where Stellar DeFi stands, the SDF published a post titled _"What the DeFi is happening on Stellar?"_ that captures how the ecosystem has been quietly maturing while others debate narratives.
-
-## x402 and MPP: Agentic Payments Are Live on Stellar Mainnet
-
-Both x402 and MPP — the two leading agentic payment protocols — are now live on Stellar mainnet. This is a significant milestone for anyone building at the intersection of AI and payments.
-
-### The Problem They Solve
-
-The entire payment infrastructure of the internet was designed for humans. An AI agent that needs to call a paid API hits a fundamental wall: there's a form, a billing dashboard, an API key a human configured. The agent hits a paywall and the workflow breaks. x402 and MPP solve this by making machine-to-machine payments as simple as an HTTP request.
-
-### x402
-
-x402 is built on the HTTP 402 "Payment Required" status code — a code that has existed since the 1990s but was never meaningfully implemented until now. The flow is simple: an agent requests a resource, the server responds with a price, the agent authorizes stablecoin payment, and the resource is delivered. One HTTP round trip.
-
-On Stellar, this settles in under 5 seconds. Stellar's fees — approximately 0.00001 XLM per transaction — are essential here: if your transaction fee costs more than the payment itself, micropayments do not work. Stellar also has USDC, PYUSD, and USDY as first-class native assets — not bridged, not wrapped.
-
-x402 is co-governed by Coinbase (who launched it), Cloudflare, Google, and Visa. Google has integrated it into their agentic payments protocol. Cloudflare built it into their pay-per-crawl tooling. The SDF also brought OpenZeppelin into the picture — they secure over $130 billion in on-chain assets — to power the x402 facilitator and provide audited smart account contracts with programmable spending limits and guardrails.
-
-### MPP (Machine Payments Protocol)
-
-MPP was co-developed by Stripe and Tempo and launched last month, and it is live on Stellar. Where x402 handles one payment per request, MPP introduces _sessions_: an agent pre-authorizes a spending limit up front, then streams micro-payments within that session, settling in bulk at the end. If your agent is querying a data feed thousands of times an hour, MPP sessions are the right model — you avoid the overhead of a per-request authorization for every single call.
-
-On Stellar, MPP settles via Soroban SAC transfers. Agents never need to hold gas tokens because the SDK handles server-sponsored fees.
-
-MPP launched with over 100 integrated services including Stripe, Anthropic, OpenAI, Shopify, and Visa. The core spec has been submitted to the IETF for standardization as the official HTTP payment standard.
-
-### The Full Picture
-
-To connect this back to everything else in this meeting: those DeFi protocols, tokenized assets, and stablecoin rails all become accessible to AI agents through these payment primitives. An agent can borrow against a tokenized treasury, pay for a data feed, execute a swap, and settle cross-chain — all programmatically, without a human in the loop.
-
-### Resources for Building
-
-If you want to start building with these protocols, the best starting points are:
-
-- [developers.stellar.org](https://developers.stellar.org) → Build → Agentic Payments — x402 and MPP docs are here
-- [Stellar Dev Skill](https://github.com/stellar/stellar-dev-skill) — a plugin for AI coding assistants (Claude Code, OpenCode, Codex) that gives your AI assistant deep current knowledge of the full Stellar stack including x402 and MPP
-- [developers.stellar.org/tools/ai](https://developers.stellar.org/docs/tools/ai) — the building with AI page, including links to the `llms.txt` file for feeding Stellar context directly into LLM prompts, and Stella, the AI assistant trained on Stellar docs
-
-## Guest Demo: Noether — First Perpetual DEX on Stellar
-
-The second half of this meeting featured Yahya and Mert, co-founders of **Noether** from the No Ethers team, recent graduates of the latest Stellar Community Fund funding round. Noether is, to their knowledge, the first perpetual DEX on Stellar.
-
-### Why a Perp DEX on Stellar?
-
-The opportunity is straightforward: every serious DeFi ecosystem needs a perpetual DEX, and Stellar did not have one. Mert has been building on Stellar since smart contracts launched on the network, has hosted over 10 Stellar workshops in Turkey, and has mentored builders and served as a judge in Stellar hackathons. When Yahya identified the gap, they locked in and built.
-
-### What They Showed
-
-Mert walked through a live testnet demo of Noether:
-
-**Faucet** — A testnet faucet page where users can claim up to 1,000 USDC per day. Before claiming, users need to set up a trustline to the testnet USDC asset — a standard Stellar requirement for holding any non-native asset.
-
-**Trade Page** — The core trading interface has three components:
-
-- **Order book** on the left, showing pending limit orders with long orders on one side and short orders on the other, and the current market price in the middle.
-- **Price chart** in the center, pulling real-time price data from Binance via a price proxy.
-- Three trading pairs available at launch, with more pairs planned for the following month.
-
-**Smart Contract Status** — The contracts are currently at MVP stage. Mainnet launch is planned approximately two to three months out, following a smart contract audit that will be supported by the Stellar Development Foundation. The team emphasized they will not launch on mainnet before the audit is complete.
-
-### On AI in Development
-
-When asked what percentage of their codebase was written with AI assistance, Mert estimated around 70% — with an important caveat: the core financial logic in smart contracts was written and verified by hand. Their approach was to use AI for the less critical parts (landing pages, boilerplate, tooling) while personally reviewing and proving the correctness of anything financially sensitive. As Mert put it: "We write the code with AI but we read it."
diff --git a/meetings/2026-04-23.mdx b/meetings/2026-04-23.mdx
deleted file mode 100644
index 7e3887794..000000000
--- a/meetings/2026-04-23.mdx
+++ /dev/null
@@ -1,105 +0,0 @@
----
-title: "2026-04-23"
-authors: kaankacar
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="E6asxPAA3wU" />
-
-## Messari State of Stellar Q1 2026
-
-Messari published their State of Stellar Q1 2026 report ahead of this meeting, and there are numbers in it that every developer building on Stellar should understand — not as vanity metrics, but as signal for where the ecosystem is actually heading and where the real opportunities are.
-
-**RWA market cap** — $2 billion at the time of the meeting, up from approximately $1.5 billion at the end of Q1 2026. That is roughly a 33% increase quarter over quarter and a 3x increase year over year from the $500 million mark in Q1 2025. The biggest single-quarter move across any metric in the report.
-
-**Average daily smart contract volume** — $16 million per day in the last quarter. One year ago it was $2 million per day. For five or six consecutive quarters, Soroban transaction volume has only gone up. This is real usage: contracts being called, operations executed, applications that real users are touching.
-
-**Stablecoin market cap** — $300 million, up 20% quarter over quarter. Protocols driving this include Aquarius, Blend, and SolarSwap.
-
-The synthesis: Stellar is executing a compounding flywheel that is now clearly visible. Institutional capital flows in via RWAs, higher TVL attracts more DeFi protocols, more DeFi protocols drive more Soroban invocations, more on-chain activity attracts more developers, more developers build more user-facing applications, more users generate more stablecoin and payment volume — and all of that makes Stellar more compelling for the next wave of institutional adoption.
-
-The full report is on [messari.io](https://messari.io) and is worth reading in detail.
-
-## MoneyGram and SDF Extend Partnership
-
-Announced on April 22nd at Stellar House in Mexico City: MoneyGram and the Stellar Development Foundation have announced a multi-year extension of their partnership. The framing is important — this is about scaling real-world stablecoin utility globally.
-
-This partnership has been running since 2021. In that time they built the world's largest cash on- and off-ramp for digital assets, launched the MoneyGram Ramps API so developers can plug into the network directly, and created a stablecoin balance feature inside the MoneyGram app that lets customers hold funds in digital dollars and cash out at physical locations.
-
-The next phase focuses on Latin America. The MoneyGram app with stablecoin support first went live in Colombia. With this announcement, it is extending to El Salvador, with more countries across Central and South America planned throughout 2026. The stack powering this is Stellar, Cross-Mint, and Circle's USDC.
-
-The real-world scale here: MoneyGram operates nearly half a million retail locations across 200+ countries. That is not a sandbox — that is live infrastructure for people sending money to families and communities that depend on cash-based services. Stellar Development Foundation CEO Denelle Dixon said: "Stellar was built on the belief that the global financial system should work for everyone." This partnership is what that looks like in practice.
-
-## Aquarius Hits $50M TVL
-
-Aquarius, the decentralized liquidity management platform built on Stellar, crossed $50 million in total value locked. Aquarius is Stellar's answer to DeFi liquidity infrastructure — AMMs, liquidity pools, reward systems — and it is designed to be a foundational liquidity layer that other Stellar protocols build on top of. When Aquarius TVL grows, the entire Stellar DeFi ecosystem becomes more liquid and more efficient.
-
-For developers asking where to start: Aquarius has been investing in documentation. Their docs at [docs.aqua.network](https://docs.aqua.network) now include real code examples — how to execute swaps through the optimal path, how to claim LP rewards, how to add fee configurations to swaps for building routers into existing applications. If you are building anything on Stellar that involves swapping assets, yield strategies, or liquidity-adjacent features, the Aquarius docs are a solid reference for what production-quality Stellar DeFi integration looks like.
-
-## Stellar Agents Hackathon: 260+ Projects
-
-The Stellar Agents hackathon on DoraHacks just wrapped, with around 600 hackers submitting over 260 projects. The hackathon was focused on agentic payments using x402 and MPP — the two protocols covered in the previous developer meeting. What the hackathon showed is what happens when you put those primitives in the hands of 600 builders from around the world.
-
-The following are standout submissions, highlighted not to endorse any specific project but to use them as a window into what is actually possible to build on Stellar right now.
-
-### Stellar 8004 — On-Chain Identity and Reputation for AI Agents
-
-[stellar8004.com](https://stellar8004.com) addresses one of the most important unsolved problems in the emerging AI agent economy: there is no standard way to find agents, verify who built them, or evaluate whether they are reliable. You cannot search for a trustworthy A2A agent for a given task and get a verifiable answer. Every platform has its own walled garden, and there is no portable reputation.
-
-Stellar 8004 takes its name from ERC-8004 on Ethereum (now going multi-chain) and gives every AI agent a blockchain-backed identity, a discoverable endpoint, and a reputation system you can verify on-chain. Think of it as LinkedIn for agents, except the reputation is not self-reported — it is attested on-chain.
-
-The stack is built on three Soroban contracts:
-
-- **Identity registry contract** — agents register with on-chain metadata and wallet binding
-- **Reputation registry contract** — users leave feedback with average scoring
-- **Validation registry contract** — third-party organizations can endorse agents through on-chain attestations
-
-The live explorer at [stellar8004.com](https://stellar8004.com) lets you browse registered agents, check reputation scores, interact with them, and leave feedback. Registered agents can also advertise x402 and MPP payment support in their metadata, so agents can be discovered and paid per query in USDC.
-
-For builders, the team also published a TypeScript SDK at `tryon.lab/stellar8004` and a Claude Code skill with slash commands for building on top of the registry with AI assistance.
-
-The conceptually powerful part is the agent-to-agent trust loop. When a DeFi agent wants to call a data analysis agent, it currently has no way to verify that agent is legitimate or reliable. With a registry like this, it can query on-chain, check the score, verify attestations, and decide whether to proceed programmatically.
-
-One note for anyone building in this space: distribution is everything for infrastructure like this. In just one hackathon there were four or five similar projects targeting the same use case. If you are building an agent registry or identity system, check the ecosystem page first and understand the competitive landscape.
-
-### MPP Router (Rozo)
-
-[mpprouter.dev](https://mpprouter.dev) is a payment network router specifically designed for agent-to-agent micropayments. On Tempo, there are over 400 MPP endpoints. This router makes it possible for users and agents on Stellar to reach and use those endpoints by paying on Stellar.
-
-It's on mainnet. The problem it solves is real and concrete: 400 agents on another network, and this project makes them reachable from Stellar. The way to find good project ideas is to find the pain points of a network — this one found a clear one.
-
-### Stellar Security Audit Agent
-
-With over $3 billion lost to hacks and exploits in 2025 (the worst year on record), and the industry already down over $600 million in just the first weeks of 2026, autonomous smart contract auditing is becoming genuinely important infrastructure.
-
-Built under the handle Chinese Powered, this is an autonomous AI security auditor for Soroban smart contracts. It works in three steps:
-
-1. **Bytecode verification** — fetches the deployed WASM bytecode from Stellar and compares it against the source code. This step matters because one of the most common attack vectors is deploying different code than what was audited.
-2. **AI-powered vulnerability analysis** — runs a full checklist equivalent to the OWASP top categories for smart contracts: access control flaws, integer overflows, reentrancy, storage exploits, initialization attacks, denial-of-service vectors.
-3. **On-chain audit record** — audit results are written immutably into a smart contract on Stellar, creating a public, verifiable audit record that anyone can query.
-
-The insight that makes this composable is step three: by writing audit results on-chain, you create an auditing layer that other contracts or agents can query. The project is currently on testnet and needs more work before it is production-ready — particularly around trust establishment and distribution — but the vision it represents is one of the most important unsolved problems in DeFi.
-
-### Stellar Mobile Agent Builder
-
-Over 75% of crypto users access services via mobile, and in the markets where Stellar is most relevant — Latin America, Africa, Southeast Asia — mobile-first is not a preference, it is the only option.
-
-Built by Sam Felix, this project flips the assumption that running an AI agent requires cloud infrastructure. Take an old Android phone, run a FastAPI agent runtime on it using Ollama for local inference, and connect it to Stellar via MPP for per-request micropayments. Anyone with a phone can become a node in the AI agent economy.
-
-What is particularly clever is the no-code layer on top: a visual drag-and-drop builder where non-technical users can design agent workflows without writing any code. The exact use case is letting someone in an emerging market use their device to provide or access AI capabilities that would otherwise be inaccessible or expensive. Not yet on mainnet, but the direction is worth noting for anyone building for global audiences.
-
-### Talos — Autonomous Agent Corporation Framework
-
-Highlighted as one of the most polished projects from the CDMX hackathon, Talos is an autonomous agent corporation framework. It lets you create sub-agents and orchestrate them to act as corporate employees: dedicated agents for GTM strategy, marketing campaigns, engineering lead hiring, and so on. The payment layer runs on x402. If you have worked with Paperclip or similar autonomous agent setups before, the mental model will be familiar. One of the most common questions at the CDMX hackathon was how to use AI to steer an entire project or company — Talos is one of the more complete answers that came out of that event.
-
-## Stellar House Mexico City
-
-Stellar House is SDF's format for bringing together builders, partners, and ecosystem members in a physical space — typically two to three days of talks, workshops, and demos. The Mexico City event just wrapped, and all sessions were live-streamed on the SDF YouTube channel (find them under the Playlists section of the channel).
-
-Mexico City was particularly significant for two reasons: the MoneyGram announcement came out of it, and Mexico and Latin America broadly are central to Stellar's mission. The event also featured pitch presentations from several teams that came through the CDMX hackathon — building a pipeline from hackathon to Stellar House is a format that seems to be working.
-
-## Stellar AI Guide MX
-
-For developers building on Stellar with AI tooling, a new open-source resource is available at [github.com/kaankacar/stellar-ai-guide-mx](https://github.com/kaankacar/stellar-ai-guide-mx). Check the building with AI section at [developers.stellar.org](https://developers.stellar.org) for the full set of AI resources, including the `llms.txt` file for feeding Stellar context into LLMs and Stella, the AI assistant trained on Stellar documentation.
diff --git a/meetings/2026-04-30.mdx b/meetings/2026-04-30.mdx
deleted file mode 100644
index 9acd5fabc..000000000
--- a/meetings/2026-04-30.mdx
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: "2026-04-30"
-authors: kaankacar
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="5O1cDDGv7_o" />
-
-## Protocol Discussion: Modular Custom Accounts and Signature Security in Protocol 27
-
-This protocol meeting covered two related authorization changes coming in Protocol 27, presented by Dmytro Kozhevin: a recap of CAP-71's authentication delegation for custom accounts, and a newly published security addendum, CAP-71-02, that closes a narrow signature replay gap.
-
-## CAP-71 Recap: Authentication Delegation for Custom Accounts
-
-CAP-71 has been around for a while and hasn't changed — the news is that it is actually being implemented in Protocol 27. It improves what modular custom accounts can do by adding **built-in delegation support at the protocol level**. A "root" account can delegate logic — for example, the cryptography implementation — to separate "sub-account" contracts. That makes it possible to have an abstract, configurable meta-account shared by multiple users, with the actual signing logic living in different contracts.
-
-This architecture has already been attempted in the wild (OpenZeppelin's contract examples use it), but until now it was painful: delegating the authorization context required several rounds of pre-simulation to propagate the context. CAP-71-01 builds the delegation mechanism directly into the protocol, which should make life significantly easier for anyone developing custom accounts.
-
-## CAP-71-02: Closing a Signature Replay Gap
-
-The reason a separate addendum exists: CAP-71 introduced a new kind of signature payload preimage, and that surfaced a small oversight in the original design. Soroban uses a unified format for signature payloads — a preimage carrying most of the necessary context, hashed with SHA-256 and then signed with an arbitrary cryptographic algorithm. "Most" is the key word: the standard authorization payload does **not** include the signer's address.
-
-Most of the time this doesn't matter. In a typical token transfer from A to B, the authorizing address is present in the payload anyway. Even when it isn't — like minting with a Stellar Asset Contract, where the admin address is not in the payload — a SAC has only a single admin, so the signature can't be reused.
-
-The one obscure case where it does matter, described in detail in the security notice published just before the meeting, requires a specific combination of factors to line up:
-
-- An admin-style contract where the authorizing signer is **implicit** — fetched from storage rather than named in the payload
-- That admin being **rotated** to a different public address
-- The old and new addresses **reusing the same private key**
-
-Sharing a private key across public addresses is rare and generally not something you should do, and an analysis showed this combination has never occurred on-chain. But if it ever did happen, the impact would be serious — a signature could be replayed to, for example, mint a token a second time. The gap was discovered through security audits.
-
-The fix introduces a new credential type, `SOROBAN_CREDENTIALS_ADDRESS_V2`, whose only difference from the current address credentials is that the protocol uses an **address-bound signature payload preimage** — the signer's address is guaranteed to be part of what gets signed. The structure is otherwise identical, so supporting it downstream is just a matter of switching from one credential type and payload format to the other.
-
-## Migration Guidance
-
-As of Protocol 27, the old address credentials are **not** being deprecated — the probability of the issue is low enough that there's no urgency for an abrupt, breaking fix. The intention is to migrate to address v2 eventually (possibly Protocol 28 or later): client tooling — the CLI, developer SDKs, and so on — can update to the new credential and payload format at their own pace after the Protocol 27 upgrade, and once the ecosystem has moved, the old format can be deprecated non-disruptively. If you maintain an admin-style contract and are worried in the meantime, you can pass the signer address in the payload explicitly.
-
-Read more about the proposals here:
-
-[CAP-71](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0071.md) - [Discussion](https://github.com/orgs/stellar/discussions/1784)
-
-[CAP-71-01](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0071-01.md) - [Discussion](https://github.com/orgs/stellar/discussions/1784)
-
-[CAP-71-02](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0071-02.md) - [Discussion](https://github.com/orgs/stellar/discussions/1899)
diff --git a/meetings/2026-05-07.mdx b/meetings/2026-05-07.mdx
deleted file mode 100644
index ff3caab0b..000000000
--- a/meetings/2026-05-07.mdx
+++ /dev/null
@@ -1,93 +0,0 @@
----
-title: "2026-05-07"
-authors: kaankacar
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="WHYHzDF8KJ8" />
-
-## Machine Payments Protocol: A Deep Dive
-
-This week's meeting is a hands-on walkthrough of the Machine Payments Protocol (MPP) on Stellar — what it is, when to reach for it, and the specific moment in your code where an operation becomes an MPP operation. The goal is to answer one question by the end: "So what? Why should I care about MPP?"
-
-MPP is the second of the two agentic-payment primitives covered in recent meetings. The first, x402, is the more familiar of the two — it's effectively a programmable paywall built on top of the long-standing HTTP `402 Payment Required` status. A human or an agent hits a route, gets a `402`, pays, and is allowed through. MPP is the less obvious sibling, and the value proposition only becomes clear once you understand its two modes.
-
-## Charge Mode vs. Channel Mode
-
-MPP has two payment modes, and the distinction is the entire point of the protocol.
-
-**Charge mode** is pay-per-request. A route returns a payment challenge, the caller pays for that single request, and the receipt unlocks the response. If you've worked with x402, charge mode will feel almost identical — it is the right choice when requests are infrequent or the underlying data isn't changing rapidly. One call, one transaction, one receipt.
-
-**Channel mode** is where MPP earns its keep. Imagine you're charging for access to a premium LLM that emits 50 tokens per second, and the underlying cost model is per-token rather than per-request. Pay-per-request breaks down immediately: you'd need the user to send a transaction every 1/50th of a second, which is impossible. Channel mode solves this by letting the user open a funded channel up front, spend against it at high frequency, and then settle in a single on-chain transaction when the channel closes. The channel can be closed manually (a button, an explicit "end session") or by a timeout — a timeout is usually the better default, because a user closing their laptop doesn't close the channel for them.
-
-The mental model: charge mode is a turnstile; channel mode is a bar tab. Both are useful, and a single tool can expose both — pick the mode that matches the cost shape of the underlying operation.
-
-## The Receipt Flow
-
-The channel-mode handshake is worth internalizing because it's where most of the "wait, how does this work?" questions come from:
-
-1. The client calls the MCP tool. The server returns `402 Payment Required` with a channel challenge.
-2. The client opens a channel against the server. The client's wallet receives a receipt for that channel.
-3. The client retries the call, this time presenting the receipt. The server returns `200` and serves the response.
-4. Subsequent high-frequency calls reuse the open channel — no new transaction per call.
-5. When the channel closes (button, timeout, or explicit end-session), a single settlement transaction lands on-chain.
-
-Charge mode collapses steps 2–5 into a single pay-and-go interaction — you pay, you get the receipt, you make the call, done.
-
-## Demo Walkthrough
-
-The full demo is on GitHub and the code is meant to be read alongside this video — it is intentionally not production-ready. The demo is an MCP server with four tools:
-
-- **`get_network_status`** — free, returns testnet liveness.
-- **`lookup_account`** — free, fetches live XLM balance for an account.
-- **`analyze_account_risk`** — paid, demonstrates charge mode.
-- **`explain_latest_transactions`** — paid, demonstrates channel mode.
-
-The free tools work the way you'd expect — `200 OK`, no payment required. They're effectively the free trial of the MCP.
-
-Calling `analyze_account_risk` without paying returns `402 Payment Required` with a charge-mode challenge: "100 base units to use this tool." Paying via the **Run Selected Tool** button produces a receipt, the call retries, and the server returns `200` with the result. Mode shown in the receipt: `charge`. One request, one transaction.
-
-Calling `explain_latest_transactions` after activating a channel session uses channel mode. The first call against an inactive channel returns `402`; opening the channel and retrying returns `200`, and subsequent calls against the same open channel don't require new transactions. The demo includes an explicit **Close Channel** button for clarity — in production you'd almost certainly use a timeout instead, so a user walking away doesn't leave a channel hanging open.
-
-## The Wallet Setup
-
-The demo uses four wallet roles, and the setup is worth calling out:
-
-- **Buyer wallet** — the end user paying for tool access.
-- **Seller wallet** — the MCP operator receiving payment.
-- **Fee payer wallet** — sponsors gas fees via OpenZeppelin's relayer. Not required for MPP to work, but heavily recommended for UX. In 2026 there's very little excuse to make users hold the native asset just to interact with your tool, and fee sponsorship is the cleanest way to remove that friction.
-- **Channel commitment key** — a separate wallet that holds the cumulative channel commitments. This is included to illustrate that the actors in an MPP setup can be decomposed — there are paths beyond "I get paid for my service" toward monetizing the commitment-holding role itself. The demo configuration here is illustrative, not best practice.
-
-The wallets live in-client (the same model used in the AK Gaming hackathon's game studio), so there's no browser extension or passkey prompt in this demo. That's a deliberate choice for clarity, not a recommendation — for anything heading toward production, look at OpenZeppelin's policy-based smart accounts (OZ Policy). With OZ Policy you can express rules like "any transaction over $10 requires my signature," which is most of what you actually want from a smart agent wallet.
-
-## The Exact Moment an Operation Becomes MPP
-
-The pivot of the video: where in the code does a regular HTTP handler turn into an MPP-gated handler?
-
-In the charge-mode handler, the route checks for a valid payment receipt. If the receipt is present and valid, the handler proceeds to the underlying business logic and returns the response. If it isn't, the handler returns a `402` with the charge challenge attached. That gating block — the small "molecule" sitting between the request and the response — is the entire MPP surface area for charge mode. Flipping the same handler from charge mode to channel mode is essentially a one-line change in the configuration of that gating block.
-
-If you've worked with x402, charge mode is going to feel like familiar territory. The thing to internalize is that channel mode is _not_ x402 with extra steps — it's a different settlement model for a different cost shape, and it's the reason MPP exists as its own primitive.
-
-## SDKs and Reference Implementations
-
-Two pointers for going deeper:
-
-- The MPP documentation on [developers.stellar.org](https://developers.stellar.org), including the list of supported MPP intents.
-- The recommended SDK for creating MPP patterns on Stellar — the easiest path to a working integration.
-
-For a better-looking, more-complete reference implementation than the demo shown in this stream, look up [@ElliotFriend](https://x.com/ElliotFriend) on X — Elliot's MPP demo (including `MPP Stellar Buzz`, a per-channel chatbot) is a strong example of channel mode used correctly: open a channel when the conversation starts, settle once when it ends, no per-token transaction overhead in between.
-
-## Where MPP Fits
-
-The use cases that map cleanly onto MPP all share one property: **high-frequency paid calls**. That keyword is the easiest filter. If your access pattern is bursty or per-token or per-tick, channel mode. If it's an occasional one-off charge for a piece of data, charge mode. If it's neither, you may not need MPP at all.
-
-Concrete examples worth thinking about:
-
-- **Paid data feeds and oracles** — charge per query, or open a channel for high-frequency consumers.
-- **Premium developer tools and analytics APIs** — the obvious one. Per-call billing for tools that today rely on API keys and out-of-band invoicing.
-- **AI-enabled explorers** — paste a wallet or contract address into a chatbot and have it narrate the on-chain activity. Open question on the table during the meeting — a strong opportunity for builders.
-- **AI auditing tools** — auditing a Soroban contract for vulnerabilities, with the caveat that no AI auditor should be the only thing standing between a project and mainnet.
-- **Agent service marketplaces** — agents paying agents per-call, with MPP as the settlement layer.
-- **Usage-based infrastructure** — anything where the cost shape is "metered, often, small."
diff --git a/meetings/2026-05-14.mdx b/meetings/2026-05-14.mdx
deleted file mode 100644
index 41c5f2c5b..000000000
--- a/meetings/2026-05-14.mdx
+++ /dev/null
@@ -1,94 +0,0 @@
----
-title: "2026-05-14"
-authors: kaankacar
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="pZMpqTGGA_Y" />
-
-## A Packed Two-Part Meeting
-
-This week's meeting splits cleanly in half. The first half belongs to Renat — a builder in our community working out of Estonia — presenting a draft SEP for zero-knowledge group membership state on Soroban. The second half is mine: an introduction to open-source, free, locally-runnable orchestration layers for AI-assisted development. If ZK isn't your thing, stick around for the second half. If running fleets of agents isn't your thing, the first half is the better one for you.
-
-Renat is upfront about the framing: he's a builder, not a mathematician. The work he's presenting isn't a new cryptographic result — it's the integration story of getting Stellar's ZK primitives (shipped in Protocol 22 and Protocol 25) to compose into something useful, and then sharing what works, what doesn't, and what's still unsolved.
-
-## The Problem: Group State Without Metadata
-
-The naive way to put a group on-chain is to store a list of addresses. That works, and it's terrible for privacy — anyone who reads the contract storage knows who is in the group, who is an admin, and what the governance rules are.
-
-The use cases Renat is targeting all want the opposite shape: a messenger that hides which group a user belongs to, DAO credentials that prove "I'm a member" without revealing _who_ I am, governance contracts that enforce rules without leaking the rule structure (is this a democracy, a tyranny, a one-on-one?). The problem is "prove membership and authority without revealing identity," which is the classic zero-knowledge setting.
-
-## Three Iterations: Groth16 → PLONK → Post-Quantum
-
-Renat walked through the iteration history:
-
-**Groth16** was the starting point. It worked, but supporting governance rules over a hidden group required contributing randomness via a trusted-setup ceremony. The standard reassurance — "you only need one honest contributor out of fifty" — is mathematically fine, and the Ethereum KZG ceremony had ~141,000 contributors as proof-by-example, but the operational burden of running a credible ceremony at a small-project scale didn't fit.
-
-**PLONK** was the second iteration, chosen explicitly to dodge the trusted-setup ceremony. This is what's currently live on testnet, and it owes its existence to the Soroban primitives shipped in Protocols 22 and 25. The contract interface is small: update the Merkle tree, verify membership, create group — with the proof transported separately from identity. A postmortem about getting the proof from client to contract is part of the package; that turned out to be the part of the work that bit the hardest.
-
-**Post-Quantum (no ceremony at all)** is the direction Renat wants to take this next. It's currently blocked on memory consumption inside the Soroban environment — not CPU, which was his initial guess, but memory. The Stellar developers helped him diagnose this. Cost is also a factor at the post-quantum end — somewhere north of 16 cents per update versus less than a cent for the PLONK path.
-
-## Cost, Limits, and the Open Payer Problem
-
-The PLONK version is cheap. State updates cost less than a cent, and the actual messages in the messenger reference implementation are free. That's a usable cost envelope for a real product.
-
-The limits worth knowing:
-
-- **PLONK is bounded by K max 2** in the current configuration — meaning "democracy" in the governance taxonomy doesn't scale to large groups yet. Two voters max per vote at the current parameters.
-- **TTL and contract capacity** need to be designed into any SEP draft. They don't disqualify the approach, but they aren't free parameters either.
-- **The payer/anonymous-user interface** is the most interesting open problem: somewhere in the flow, gas needs to come from somewhere, and "the anonymous member pays" leaks information unless handled carefully. This is the surface point of contact between the fee-paying entity and the privacy-preserving member, and there's no good answer in the current draft.
-
-The code is MIT-licensed and reproducible — the runs are public, the reference messenger implementation is published, and Renat is explicit that what's shown is reference-quality, not production-ready.
-
-## What Renat Is Looking For
-
-This part is the actual call to action: Renat is looking for a SEP champion in the developer community. Someone who can read the draft, push it through the ecosystem-proposal process, and validate that the work is useful beyond his own messenger project.
-
-If that sounds like you, his Discord handle is pinned in the meeting comments, and his email and GitHub are reachable from the reference implementation's README. He's open to "this works" feedback, "this doesn't work" feedback, and — the most useful kind — "this works but here's the obstacle you missed." He's planning to attend [Meridian 2026](https://meridian.stellar.org) in Lisbon this October, so the champion conversation can also happen in person.
-
-## The Orchestrator Shift
-
-The pivot of the second half: if you've been building on Stellar for any length of time, you're using AI. Pretending otherwise is silly. The interesting question is what _kind_ of AI use you're doing.
-
-There are two roles to recognize. The earlier role — the **facilitator** — is what most of us got used to between November 2022 and roughly the end of 2024: you write what you think, you write what you want, you guide the model through the build, and you stay close to the work. Cursor Composer, Sonnet 4, GPT-o3 — all of these reward facilitation.
-
-The newer role — the **orchestrator** — is what Opus 4.7, Composer 2, the Claude Agents SDK, and the autonomous-agent stacks (Hermes, Open Claw, custom-built agents) are designed for. You're no longer the one writing prompts to a single model; you're managing a fleet, and your job is to keep that fleet aimed at a useful outcome. That's a different skill, and the tools for that role are still finding their shape.
-
-The three tools in the second half of this meeting are all attempts at giving the orchestrator a control plane.
-
-## Cline Kanban
-
-Cline Kanban — free, open-source, runs locally — is the lightest of the three. It's a Kanban board for agent work, built on top of Cline (the open-source coding agent that ships an SDK, a CLI, and a VS Code extension of its own). You drop into a project directory, run `kanban`, and a local web UI comes up. The board can attach to any of the major agents — Cline itself, Claude Code, Codex, Factory Droid, Kiro, Hermes — and you use it to define tasks, set dependencies between them, and drag work through To Do → In Progress → Review → Done.
-
-The demo: a fresh directory called `x402-contest-demo`, a one-line ask to "create an exploratory x402 demo on Stellar," and the Kanban agent decomposed it into five linked tasks. From that point on, the orchestrator's job is to review each completed task, decide whether to merge to main, and unblock the next one in the chain. The board offers auto-commit, open-PR, and "leave on branch" flows; while you're getting a feel for an agent's output quality, "ask for approval at each step" is the right default.
-
-The shape of this tool: best when the underlying work is _coding_ and you want a lightweight layer on top of one or more agents to keep tasks orderly and dependencies explicit.
-
-## Paperclip: A Control Plane for AI Labor
-
-[Paperclip](https://paperclip.ing) takes the orchestrator framing one step further. Where Cline Kanban treats your project as a repo, Paperclip treats it as a _company_. You onboard with `npx paperclip-ai onboard --yes`, name the company, give it a mission, hire your first agent (the CEO by default), and from there you're the board.
-
-The demo company was "Paper Excel" — Dunder Mifflin in spirit — with the goal "to be the best paper company in the world with the best-looking UI." The CEO went to work hiring the first team: CTO, CMO, UX designer, research lead, intern. Each role has its own starter prompt, its own heartbeat interval, and its own assigned skill set. The dashboard tracks issues, an organizational chart, an inbox for the board (i.e., you) to receive agent emails, and routines for recurring work. The agent backends are pluggable: Claude Code, Codex, OpenRouter, Gemini CLI, Hermes Agent, Open Claw.
-
-Two practical notes:
-
-- **It is not a magic productivity multiplier.** It's a coordination layer for running multiple agents — most of the agents in the demo were slacking on their first day, and roughly half the issues failed on first run with API errors. This is alpha-quality at the experience level, even where the underlying agent capabilities are strong.
-- **It will burn through tokens fast.** Bring-your-own-API-key with per-agent spending caps is the right way to experiment. The demo ran on a Claude Code subscription and was probably $50–100 of usage in 30 minutes. For exploratory work, point it at a free model on OpenRouter — output quality is worse, but cost is bounded.
-
-The shape of this tool: best when the work is broader than coding — a research-and-marketing-and-content-and-product company-shaped problem — and you want to see what "running a small AI org" actually feels like before staffing one in real life.
-
-## BMAD Method (Saved for Next Week)
-
-The third tool is the BMAD method — this week's favorite, and the one I most wanted to demo. The meeting ran long (the first half earned its time), and BMAD is worth a real walkthrough rather than five rushed minutes. Tune in next week for that one.
-
-The one-sentence pitch: BMAD is for builders who want an Agile development flow with their agents, and for builders who want a thoughtful brainstorming partner that's read more about the problem space than they have. If either of those describes your current bottleneck, the deferred demo will be the one to catch.
-
-## Where This Is Going
-
-Two takeaways:
-
-The move from facilitator to orchestrator isn't a tooling upgrade — it's a skill change. The tools shown today are the early shape of what that change looks like: local-first, agent-agnostic, opinionated about how you compose work. They're not finished. They will get better.
-
-And: if you have time before next week, read Renat's draft and the reference implementation. A SEP that lets Soroban hold private group state cheaply is exactly the kind of primitive that quietly unlocks an entire category of applications later. The champion role is open.
diff --git a/meetings/2026-05-21.mdx b/meetings/2026-05-21.mdx
deleted file mode 100644
index 2a1a78cc9..000000000
--- a/meetings/2026-05-21.mdx
+++ /dev/null
@@ -1,86 +0,0 @@
----
-title: "2026-05-21"
-authors: kaankacar
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="isaeBeur6ro" />
-
-## Another Two-Part Meeting
-
-This week splits in half again. The first half belongs to our guest — a builder out of Kolkata who joined the community last October and started shipping ZK tooling almost immediately. He's here to present Root14 — a privacy _toolkit_ for Stellar built on the zero-knowledge primitives that landed in recent protocol upgrades. The second half is mine: a fast tour through roughly ten open-source, mostly-free AI tools, continuing the orchestrator theme from last week. If cryptography isn't your thing, skip to the tools. If you've had enough of me talking about agents, the first half is the one for you.
-
-A quick reframing before he starts, because it's load-bearing for everything he says: Root14 is **not** a private payments app. It's not a mixer and it's not a shielded pool. It's the cryptographic infrastructure that sits _underneath_ all of those things. The analogy he uses is OpenSSL versus a single HTTPS website — Root14 isn't the website, it's the part every website ends up importing.
-
-## The Substrate: Why the Economics Only Work on Stellar
-
-He grounds the whole talk in CAP-59, which shipped the native BLS12-381 host functions to Soroban: G1/G2 addition, scalar multiplication, multi-scalar multiplication, pairing checks, and full scalar-field arithmetic. That's the complete substrate you need to do production-grade Groth16 verification natively, available to any contract.
-
-His pitch for _why Stellar_ comes down to cost. A pairing check that would take tens of millions of Wasm instructions on another chain runs as a single host call here. No other smart-contract chain has this combination at this cost point today — which is exactly what pulled him to the network and got him researching ZK on it in the first place.
-
-## What's in the Toolkit
-
-Root14 is a layered toolkit, and he walked through it piece by piece:
-
-- **Root14 Core** — a single contract that does two things. You call `register` and get back a content-addressed circuit identifier (the SHA-256 of the verification key, so the binding is unforgeable). After that, any contract on the network calls `verify` with a circuit ID, a proof, and the public inputs, and gets back a boolean. That's the entire interface. The contract holds no business logic, no value, no decisions — just registered verification keys and pairing checks. It's live on testnet today. The load-bearing insight: every existing privacy project on Stellar embeds its own verifier inside its own contract and pays for its own audit on essentially the same pairing code. A shared registry makes that duplication disappear.
-- **Circuit Library** — a set of vetted primitive circuits with published constraint counts and content-addressed identifiers: range proofs (credit thresholds, age bounds), set membership (KYC allow-lists), set non-membership (sanctions screening), and knowledge-of-preimage (ownership groups). Register a primitive once and every dapp on the network can use it.
-- **SDK and CLI** — a single `cargo add` gets you proof generation and serialization in Rust; the CLI is a human-friendly shell over the same SDK, with templates for generating contracts.
-- **MCP server** — the part he's most excited about. It lets Claude or any MCP-compatible model register a circuit, generate a proof, and trigger a verify call through natural language. As far as he can tell, it's the first ZK-on-Stellar MCP integration anywhere. A registry indexer streams on-chain events so developers can discover which circuits exist and how to compose them.
-
-## The zkTLS Bridge
-
-The piece closest to his heart is Root14's zkTLS. It bridges web2 and web3 trust: a user generates a zero-knowledge proof that they received a _specific response_ from a _specific web2 server_ without revealing the rest of the session. Prove you have over $1,000 in a bank account without showing the statement. Prove a KYC status with a particular issuer without exposing the underlying credential. Prove a tweet exists at a URL without leaking the OAuth token. There's a prototype today and production integration is on the roadmap; combined with the verifier registry, it's a clean way to pull real-world data into Soroban contracts without trusting a centralized oracle.
-
-## Private Payments, Honestly
-
-He was candid about the one piece that isn't usable right now. His original SCF submission leaned on private payments, and the mainnet privacy-pool deployments lagged on the AML/KYT-sensitive side — building privacy-preserving payments without thinking hard about compliance is how you get into legal trouble. So that part is currently down while he reworks it to be KYC/AML-aware. The developer-facing shape is still the goal, though: you don't write pairing code, you don't run a trusted-setup ceremony, you don't touch arkworks — you write your application contract, bind it to the relevant circuit identifiers in the registry, and call `verify` when you need a proof checked.
-
-## Production Readiness
-
-This isn't framed as a research prototype. Verification keys registered on mainnet will be immutable and content-addressed — no upgrade method, no admin power to silently re-point an identifier. Canonical registration transactions go through an SDF-approved multisig. The phase-2 trusted-setup ceremony will be multi-party with public transcripts and end-to-end-verified attestations from every contributor, and everything is open source under the Root14 name.
-
-## The Q&A: AI, Groth16 vs. PLONK, and the Business Question
-
-We tend to roast our guests with hard questions so they've already sweated out the answers before they reach an SCF panel, and the audience delivered:
-
-- **How much AI, and what's the setup?** He works ZK problems out with pen and paper first, then drives Claude Code layer by layer — architecture, then circuits, then verifier — prototyping, testing, and bouncing the output off other agents before moving on. He also leaned on the `llms.txt` file from the docs to make the model Stellar-aware out of the gate. His honest caveat matches mine: AI tends to cut corners on ZK, so it's an accelerant, not an autopilot.
-- **Long-term sustainability?** A shared verifier registry doesn't make much money on its own — maybe a small fee on registrations or calls. The real business is zkTLS as a B2B product: managing ZK infrastructure for Stellar-native teams and selling into developer/user onboarding flows.
-- **Why Groth16 over PLONK, and who runs the ceremony?** Groth16 won on cost and proof size for a hackathon timeline; PLONK needs more pairings and polynomial-commitment work, roughly double the budget for the same proof. He reuses an existing phase-1 powers-of-tau output (the Ethereum or Aztec ignition ceremonies, both public and audited with 100+ contributors) and only runs phase 2 per-circuit. Nothing about Root14 is religiously locked to Groth16.
-
-Root14 is in SCF #43 — the docs site is mid-rebuild, so keep an eye out and vote it up when public voting opens.
-
-## The Orchestrator Theme, Continued
-
-The pivot to the second half: last week I made the case that the job is shifting from _facilitator_ (you write the code, you stay close to the work) to _orchestrator_ (you manage a fleet of agents). This week's theme is narrower and a little more pointed. Stop writing "make no mistakes" to your model. If you can't steer the build, it's usually because you don't understand what's being built — and if you _wouldn't_ be able to build it without AI, that's the most dangerous place to be. The tools below are all attempts to keep you hands-on enough to understand the thing you're shipping.
-
-## Hands-On Frameworks: BMAD and Superpowers
-
-[The BMAD Method](https://github.com/bmad-code-org/BMAD-METHOD) is the one I most wanted to show. It installs locally and free with `npx bmad-method install` — it's just a set of skills, hooks, and workflows, scoped to your project rather than installed globally. The point is spec-driven development with an Agile shape: it slows you down on purpose and walks you through brainstorming, market and domain research, technical research, and then planning out a PRD and stories. Each phase has a named agent — Mary is the business analyst you brainstorm with — and `/bmad-help` is your "what do I do next" button at any point. I kicked off a "Hey Mary, I want to build something with agentic payments on Stellar but I don't know what" session live to show the brainstorming loop.
-
-[Superpowers](https://github.com/obra/superpowers) is an alternative skills framework that does more or less the same job minus the explicit Agile emphasis. Try both and keep whichever fits how you think. The shared point of both: a more hands-on approach so you actually understand what's being built.
-
-## Letting Agents Use a Browser: kernel.sh and browser-use
-
-Claude Code and Codex can fetch a page's data but can't really _drive_ a browser — and they can't touch Chrome extensions, which is painful if you're testing a Stellar wallet extension. [kernel.sh](https://www.kernel.sh) fixes that: it spins up cloud browsers and lets your agent build automated workflows (it calls them "apps") through a free MCP server. My demo had Claude Code's kernel MCP walk stellar.expert for mainnet stats, click into the Soroban tab, hop to CoinGecko for the XLM/USD price, and capture it all to JSON. It's open-source infra with a free tier; the paid plan exists, but the free MCP is enough to expand your sense of what's possible.
-
-[browser-use](https://github.com/browser-use/browser-use) is the tool your model reaches for _first_ when you ask for browser automation — which is exactly why I show it. First-recommended isn't the same as best. It wants its own API keys (Google's and Anthropic's), and I'd rather point an agent at tools that ride the CLI I'm already paying for. Useful to know it exists, but kernel was the smoother experience for me.
-
-## Free Compute: freebuff
-
-[freebuff](https://freebuff.com) is the free tier of CodeBuff — it gives you a few hours a day of DeepSeek V4 Flash for free, with ads. The agent ("Buffy") does the usual implementation, codebase navigation, testing, and multi-agent orchestration (it'll spawn a stack of sub-agents), and it drives a browser using browser-use under the hood, so you get the browser-automation demo and the free-compute demo in one. DeepSeek V4 Flash is light but genuinely good for exploratory work when you don't want to burn frontier-model budget. CodeBuff's paid tier is around $100/month; if you're going to consider that, spend your free hours first.
-
-## Memory: claude-mem, mnemon, and Raindrop Workshop
-
-The unsolved problem under all of this is memory — how does the agent remember where it left off? Three takes:
-
-- **[claude-mem](https://github.com/thedotmack/claude-mem)** is the most widely used, and it's my favorite plug-in for this. It runs locally, works with Claude Code and Codex, and at the end of each session it scans the whole thing — what you discussed, what the agent did, where it went wrong, how it reached its conclusions — and writes session summaries plus, my favorite part, _discoveries_. Open the folder again and the agent already knows where it left off. No more hand-written handoff markdown. The trade-off is that it stores a lot, including things you didn't need.
-- **[mnemon](https://github.com/mnemon-dev/mnemon)** is the same idea but LLM-supervised: it lets your model decide _what_ to remember and _when_ to recall it, which keeps the store much tighter. It's newer and smaller than claude-mem, has an MCP server, and persists across sessions. Import claude-mem's history into mnemon's graph and you can see what the former would look like with structure; run mnemon on its own and you get a clean "mind palace."
-- **[Raindrop Workshop](https://github.com/raindrop-ai/workshop)** is the outsider. It's a local debugger that doesn't store everything and isn't LLM-supervised — it stores _workflows_, the step-by-step way to do a recurring thing. Ask the agent to do that thing again and it fetches the tree and follows it. It's cost-efficient precisely because it only remembers _how_, not _what_.
-
-## Where This Is Going
-
-We covered a lot at a shallow depth on purpose. I want your help picking which of these deserves a full, hour-long deep dive in an upcoming session — tell me on Discord. The throughline of the whole second half: software is getting fast and cheap, and cheap software is also dangerous software. A more hands-on approach is the cheapest insurance you can buy. Stop writing "make no mistakes," start writing `/bmad-help`, and understand the thing you're building.
-
-One housekeeping note worth repeating: CCTP is live on Stellar now, so cross-chain interop apps are something you can start building today.
diff --git a/meetings/2026-06-11.mdx b/meetings/2026-06-11.mdx
deleted file mode 100644
index 51915538d..000000000
--- a/meetings/2026-06-11.mdx
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: "2026-06-11"
-authors: kaankacar
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="AdhPqUbZXvA" />
-
-## Back After a Week
-
-We skipped a week — the DevRel team was in Istanbul for the hackathon we threw during Istanbul Blockchain Week, and the side event at the end gathered more than 400 people. This week we're back, and the guests are Paul and David from Sodax. You may know them from Balanced or Hana Wallet; they're some of the OGs, and they walked us through what Sodax is and why a Stellar builder should care. The plan was to close with a new AI package from our side, but the Sodax half earned its time, so that one slid to next week.
-
-## Sodax: Cross-Network Liquidity as Developer Tooling
-
-Sodax is a cross-network execution and liquidity system — an intent-based one — and the framing David led with is that it's essential _developer tooling_, not a destination app. If you're building on Stellar and you want to open your front door to users who hold assets on other networks, you normally have to build bridges, source liquidity, and maintain infrastructure. Sodax does that part so you don't: you stay on Stellar, build the way you want, and reach users elsewhere through a single developer SDK.
-
-The liquidity piece is the part that's easy to underrate. It isn't only cross-network _connectivity_ — Sodax has already sourced the liquidity, so the cross-network swaps and DeFi actions actually settle. As a developer you stop worrying about where the depth comes from.
-
-## From ICON to Sodax
-
-Paul gave the origin story, and it's a good one. The Sodax brand is new — early 2025 — but the team isn't. Before Sodax they were ICON (the ICX token), a layer-1 from the ICO era with an interoperability vision that was years ahead of its time. Over time the lesson landed: to do intent-based, liquidity-powered interoperability you don't actually need to run your own blockchain. So they spun the L1 down, put their logic hub on Sonic (a fast, sub-second-finality EVM chain), and built the smart contracts out across Stellar, Solana, Sui, and more — deliberately spanning EVM and non-EVM networks to open routes other systems treat as impossible.
-
-Balanced (once the number-one DEX on ICON) and Hana Wallet (formerly the ICON wallet, now a self-custodial multi-network wallet on mobile and desktop) both come from those same ICON roots and are now powered by Sodax under the hood. Both went through Stellar's SCF program — they pitched at Meridian in London two years ago and Hana again at Meridian Brazil last year.
-
-## The Spoke-Chain Model
-
-In the Sodax model, Stellar is a **spoke chain** — which means everything in the Sodax docs applies to and for Stellar builders. The count keeps climbing, but they're on roughly 20 networks now, and they recently plugged in native Bitcoin, which they're rightly proud of. Some of the more exotic spokes are Near, Stacks (a Bitcoin L2), and Injective (Cosmos).
-
-The asset model is worth understanding. When you swap into "BTC" on Stellar through Sodax, you get a **soda variant** — a trading- and liquidity-backed Sodax representation of Bitcoin that lives on Stellar but is plugged into real Bitcoin liquidity on the Bitcoin network. The solver sees native-asset liquidity across all 20 networks at once and reasons across all of it when a trade fires, so there's depth without anyone provisioning pools — and you can withdraw straight back out to a native Bitcoin wallet. If you've used something like Near Intents, the UX will feel familiar.
-
-## Three Lines to a Cross-Network Swap
-
-Paul's honest line was that the demo is hard to make sound impressive because the SDK abstracts so much away. Integration is three steps:
-
-1. **Quote** — ask for the price of the swap you want.
-2. **Swap** — do it. One line.
-3. **Status** — poll for `not started`, `solved`, or `failed`.
-
-If a swap fails, the recovery system automatically returns funds — even if they'd already left the wallet. There's also a built-in wallet-connection component (wrap it around your frontend, stack the providers, done), which matters when you're juggling 20 networks, and Stellar trustlines are handled inside the SDK. `npm install` the SDK (or `pnpm add` it) and that's most of what you need to ship a real cross-network app.
-
-## Earn, and a Bit of Alpha
-
-Beyond swaps, the SDK exposes a cross-network money market — your end users can deposit, borrow, and earn supply interest. David dropped a bit of alpha too: leveraged staking yield is coming, so things like native ETH or native Solana staking would become accessible to your users even if your app lives entirely on Stellar or some other unrelated network.
-
-## Built for Agents
-
-This is the part that fit the room. Sodax shipped a best-in-class **builder MCP server** ([builders.sodax.com](https://builders.sodax.com)) — plug it into Claude or your cursor agent and it levels your agent up into a "prime Sodax developer." You don't need a docs-indexer like Context7; the MCP _is_ the docs. Even before you commit to building with Sodax, you can point the builder MCP at your existing Stellar repo and have it assess, in about ten minutes, where Sodax could open up cross-network opportunity for you. On top of that, they've embedded agent skills directly inside the SDK, so even if you never wire up the MCP, an agent crawling the package runs into the skills and uses the swap/lend/borrow modules correctly — in their words, "so that even Sonnet 4.6 doesn't make mistakes."
-
-I can vouch for that last claim. The morning of the meeting I didn't even use the MCP — I pointed Sonnet 4.6 (not the strongest model) at `docs.sodax.com` with roughly "surprise me," and about thirty minutes and 20% of a Pro plan later I had a one-shot mainnet demo: assets, addresses, cross-chain swaps, bridge limits, every supported chain. The question stopped being _can_ you vibe-code something on Sodax and became _why not_.
-
-## The Fee Model
-
-Sodax takes a flat **0.1%** on swaps — the same shape as a Uniswap-style backend fee. The interesting part for builders: any partner integrating the SDK can set their _own_ partner fee on top. A wallet like Hana, or your own app, can add (say) 0.5% and keep it. You have full control over what you charge your users, which means an integrator can end up earning more per swap than Sodax itself.
-
-## Why Mainnet Only
-
-A recurring audience question: does it support testnet? Short answer, no — and the reason is structural. The solver sources real liquidity from real markets, and there's no monetary value backing assets on testnet, so the solver simply has nothing to solve. Replicating it would mean standing up and maintaining dozens of testnet liquidity pools, bridges, and staking platforms in parallel. They're open to bringing _parts_ of the stack to testnet and want to hear from developers about which parts would actually help — but for now Sodax is a mainnet product, which is also fine, because you're not deploying your own contracts. It's a plug you put into your app and it works.
-
-Where to go next: [docs.sodax.com](https://docs.sodax.com) for the SDK, [builders.sodax.com](https://builders.sodax.com) for the MCP, and [sodax.com/partners](https://www.sodax.com/partners) to see how the integration and fee split work. Their whole team hangs out in Discord and answers builder questions directly.
-
-## Next Week
-
-I ran out of time to show the AI package we built, so set a reminder. Next week's is the one I've been most excited about: the tool the SDF DevRel team shipped that drops 42 skills and hooks into your setup, packs in information about every project ever built on Stellar for market research, and wraps the whole thing in an Agile workflow. It needs a full half-hour to do it justice. See you then.
diff --git a/meetings/2026-06-18.mdx b/meetings/2026-06-18.mdx
deleted file mode 100644
index c63ea3047..000000000
--- a/meetings/2026-06-18.mdx
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: "2026-06-18"
-authors: kaankacar
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="9dfzsu5ChCM" />
-
-## A Doozy of a Week
-
-This week was a doozy — not just one exciting guest, but a pile of news and a stack of tools to use and maybe break. Before the guest, a quick ecosystem roundup. The big one: **v16 of the JavaScript SDK is live**. If you're building on the JS SDK, upgrade your codebase and read the release notes to see what changed. Ask in the Stellar Developers Discord if anything trips you up.
-
-Two more things worth your time. Our **Real World ZK hackathon** with onlyhacks is still running — 11 days left to submit, $10,000 in prizes. The brief is simple: build anything that uses zero knowledge and runs on Stellar — privacy pools, private payments, confidential tokens, identity and compliance proofs, provable computation, verifiable data. If it's ZK and it's on Stellar, it counts.
-
-And if your team is closer to launch, **SDF and CV Labs have opened the Stellar CV Labs Accelerator** — SDF's first EMEA-focused program. It's a 12-week remote-first accelerator with a two-week in-person boot camp in Cape Town, supporting 10 early-stage startups across DeFi, payments, and RWA in the ME region. Selected teams get technical support, tokenomics advisory, go-to-market guidance, mentor 1:1s, ecosystem perks, and up to **$150,000 in XLM** in initial development funding from SDF. Post-program, top teams are eligible for additional SDF grants and a joint IC review with CVVC's fund — up to another $150k per team for the top two. Applications are open until **July 3rd**.
-
-For context on why any of this matters: per the Electric Capital developer report, close to **1,800 builders** shipped on Stellar this week, and we had nearly 150 builders live on the call when we started (peaking past 470 by the end). There's a synergy here, and I hope you can feel it too.
-
-## Guest: XCCY — A Fixed-Rate Engine for DeFi
-
-This week's guest was **XCCY** (short for **cross-currency swaps**) — an on-chain interest rate engine that's integrating to Stellar. The pitch: lock in a fixed yield on stablecoins, borrow at a fixed rate for a known period, and hedge variable interest rates instead of guessing where yields will go. Their current platform already shows around $1M in liquidity and roughly $2M in 24-hour volume.
-
-**Dennis** (co-founder and CEO; background in math/CS, several DeFi protocols, and HFT trading) and **Dmitri** (CPO; a TradFi derivatives background) walked us through it. XCCY was accepted into **SCF's 41st cohort**, is deployed on EVM mainnets today, and started building on Stellar two weeks ago.
-
-### The Problem
-
-There's a huge amount of unhedged floating-rate exposure across DeFi. In TradFi this is solved with an **interest rate swap** — a derivative that lets you exchange a fixed, predefined rate for a floating rate tied to some source (Fed funds rate, or in DeFi a lending market's borrow/lend rate). XCCY brings that primitive on-chain, leaning into an RWA-looping narrative and fixed rates on Stellar — natural given the depth of RWAs and lending markets like Blend and YieldBlox on the network.
-
-### Three Primitives
-
-Dennis demoed the platform (live, on Stellar testnet, network errors and all) and the math behind it:
-
-1. **Oracle Hub** — XCCY uses two oracle types. **Reflector** (5-minute candles) for collateral pricing, and **RedStone** for some assets like RWAs. For rates they derive **APR oracles** by applying exponentially weighted moving average smoothing — because lending-market rates only update on trades, so without smoothing the rate can sit unchanged for long stretches.
-2. **vIMM** (virtual IMM) — an AMM-style engine, close to Uniswap v3 with liquidity ticks, but instead of trading token-vs-token it trades a **fixed rate against a variable rate** tied to an underlying (e.g. a Blend rate). Pools issue **fixed tokens** (representing a fixed ~1% APR factor) and **variable tokens** (whose growth tracks the underlying). It's a zero-sum game — the sum of LP and taker tokens is always zero, so when one side loses on a rate change, the counterparty earns it.
-3. **Collateral Engine** — handles LTVs, liquidation bands, and stages. Stable-vs-stable isolated pools can run very high LTV (~99%); portfolio exposure with volatile collateral needs more buffer. Crucially, because an interest rate swap's P&L is driven by _accrued_ value over time rather than instantaneous price spikes, the engine can support high leverage for shorter tenors using dynamic upper/lower "worst-case" bounds — more collateral for longer maturities, less for closer ones. Settlement happens automatically at maturity, much like options.
-
-### What's Next for XCCY
-
-Mainnet is several months out, gated mostly on audits given the complexity, with the Stellar testnet and SDK landing in a few weeks. The API already exists and is being ported to Stellar this month — and they explicitly want to adapt it for **AI agents**, so a strategy can be wired up with "one prompt or one skill." Cross-chain arbitrage across their existing EVM pools is on the roadmap too. Reach them on the Stellar Discord, Telegram, or X.
-
-It's a fitting guest for where Stellar is: nearly **$3 billion in RWAs** on the network today, and teams like XCCY are coming precisely because of the institutional and real-world-asset depth.
-
-## stellar-build: Your Whole Dev Journey in One Command
-
-The AI half of the meeting was a walkthrough of **stellar-build** (stellar.new) — the tool the DevRel team shipped last Friday and used at the Istanbul hackathon. It's a one-command installer that drops **42 skills** plus curated data on **700+ projects built on Stellar** and **9,000 projects** from Electric Capital's developer reports into your setup. Since Friday it's been installed about **101 times**.
-
-The idea: answer almost every question a builder would otherwise ask a mentor during a hackathon — _is this a good idea, has it been done on Stellar, can it be done on Stellar, who are my competitors_ — not just "how do I implement X." It's built on the **BMAD method**, so it's a hands-on, orchestrated journey rather than a one-shot app generator. You're the orchestrator; the AI personas and their data do the legwork while you say yes, no, or maybe.
-
-Those personas are the DevRel team rendered as agents: **Justin** (analyst), **Bri** (tech writer), **Nicole** (PM), **Kaan** (UX), **Tyler** (architect), and **Elliot** (senior dev) — spanning the idea, planning, solutioning, implementation, and launch phases. There's a **party mode** that brings everyone into the room at once, and a **stellar-help** router that re-orients you whenever you forget where you are.
-
-### Live Demo
-
-I drove it live for the ZK hackathon. Asked **Justin** what to build; he pulled my prior context (via the **mnemon** memory plugin), then loaded the **competitive-landscape** skill and went treasure hunting through both the curated catalog and the Electric Capital dump. He surfaced real neighbors — **Zarf Protocol** (an SCF 42 privacy-preserving token distribution with ZK private claims), **Sora Drop** (an open-source but non-private airdrop tool, ~$48k from SCF 28), and a stealth team porting the same primitive — making the point that the Merkle-claim mechanic is already being commoditized, so the opening is a sharp, specific application rather than yet another ZK toolkit.
-
-From there we routed into a **PR FAQ** validation (working-backwards stress test) with Justin, then pulled in **Tyler** to sketch the architecture with full context handed off cleanly — issuer contract, circuit spec, storage layout, interface signatures. Every persona ends its turn with concrete next steps, which matters: even the human versions of these people aren't always in the room.
-
-That's stellar-build — the entire DevRel team as agents on your screen. Grab it for this week's Real World ZK hackathon on DoraHacks, and I'll see you next week.
diff --git a/meetings/2026-06-25.mdx b/meetings/2026-06-25.mdx
deleted file mode 100644
index 4b05360b7..000000000
--- a/meetings/2026-06-25.mdx
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: "2026-06-25"
-authors: kaankacar
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="xqBgocb6bCM" />
-
-## Another Doozy of a Week
-
-Before the guests, a quick bit of ecosystem context for why this week felt busy. Per the on-chain data, **Stellar's RWA market cap just crossed $3 billion** — you can see it for yourself on the Dune dashboards. And the ideal Stellar developer meeting, in my book, is one with as many guests as possible, because the conversation I keep having with projects is that they want a real way _into_ the ecosystem. Contributing is one way; introducing yourself on this call is another. This week we had two guests and, with a bit of luck, a new viewer record.
-
-We also had four days left to submit to the **Real World ZK hackathon on DoraHacks** — more on that from our second guest below.
-
-## Guest: Gaian — Stablecoin Rails for Southeast Asia
-
-Our first guest was **Gaian** (gaian.network), a stablecoin payment infrastructure for the APAC region. In one sentence: it's an API that connects crypto wallets to local banking rails using **USDC on Stellar**, moving value between stablecoins and local currencies like the Vietnamese dong to power merchant payments, on/off ramps, and cross-border transfers that settle straight into real bank accounts. Imagine paying for a coffee in Hanoi straight from your Freighter, Albedo, or Beans wallet — that's the promise. Kelvin walked us through it live from Vietnam (at 1 a.m. his time).
-
-Gaian isn't new — the team has been at it for over a year and pivoted twice; what they demoed is the **v2** of the API. They're live across APAC (Vietnam, the Philippines, part of Thailand) plus Brazil and Peru, and in Vietnam and the Philippines they operate as the **anchor themselves**, working directly with the top banks.
-
-### How the Flow Works
-
-There are several actors but only one payment. A consumer holding USDC talks to a wallet; the wallet talks to the Gaian API; Gaian uses the blockchain as the settlement layer and a partner PSP in the destination country to land fiat in the merchant's bank account. Crucially, **the merchant sees no blockchain at all** — they just receive fiat.
-
-### Authentication
-
-The v2 API authenticates every request with an **HMAC signature**. You get an API key and secret from the self-service dashboard, build a canonical message out of the timestamp, method, path, query, and body, HMAC it with your secret, and base64-encode the result. Every request must carry that signature and timestamp.
-
-### The Order Lifecycle
-
-There are two halves — onboarding a user, then placing an order:
-
-1. **Onboarding.** Create a user (`POST /v2/users`), associate a wallet address to that user (the address is just a string — the wallet provider controls it), then generate a **KYC URL** for the user (providers vary by country) and poll their status by ID or wallet address until it's approved.
-2. **Payment.** Ask Gaian for a code by passing the scanned **QR string**, the fiat amount, and the user's wallet address. Gaian returns a code ID, the fiat amount, the total (including the bank's processing fee), the exchange rate, and the decoded bank details. Then **place the order** with that code ID — Gaian returns an order ID, a status label, the settlement wallet address, and the token address (USDC today). The wallet **signs and broadcasts** the USDC transfer to the settlement wallet (not an API call), and finally notifies Gaian with the transaction hash so Gaian can verify it on-chain and mark the order settled (there's no automatic chain listener yet). There's also a **prefund** flow where a wallet pre-funds stablecoin with Gaian.
-
-### The Demo
-
-Kelvin ran the whole thing live from a Bruno collection and a demo wallet, paying ~21,000 VND (under a dollar, with a small minimum bank fee) to a real Vietnamese bank account. The first code expired mid-explanation — a hazard of a good demo — and re-verifying settled it. The real headline: the **self-service dashboard** means any viewer can sign up, grab API keys, and integrate Gaian's payment capability into their own wallet without ever talking to sales, up to a ~$4,000 cap before KYB is required.
-
-Gaian went **live on Stellar** the previous Friday, and for now it's mainnet-only — going fast to production rather than testnet-first. The one thing I asked for repeatedly (and will keep pestering them about) is a **self-service sandbox on testnet**, so we can amplify Gaian as an anchor to builders across the Philippines and Vietnam.
-
-## The Real World ZK Hackathon
-
-Our second guest was **Jeremy** (also known as J Romero), the ecosystem partner running the **Real World ZK hackathon** on DoraHacks. The scope is deliberately wide open: anything that touches zero knowledge on Stellar qualifies — privacy pools, private payments, confidential tokens, verifiable computation, even ZK games.
-
-The news he dropped live: for the first time ever, they **extended the deadline** by about a week, so it lands just before the US holiday (giving builders more time and keeping judging off the judges' holiday plates). The prize pool is **$10,000 in XLM** across five places ($5,000 for first down to $750 for fifth), plus a random $100 in XLM for someone who fills out the feedback survey. Requirements are light — an open-source repo and a short demo video.
-
-Everything runs on **DoraHacks** (search "Stellar"), but the real hub is the dedicated **Telegram group** (1,000+ people), where ecosystem ZK teams — Nethermind, Boundless, OpenZeppelin, Aztec — hang out to help. A prolific builder who's won three prior Stellar hackathons (including the ZK Gaming one) is helping as a mentor this round. There's also a resources tab on the hackathon page you can point your AI at, and office hours were being scheduled. Jeremy's parting advice: don't let AI name your project (three teams showed up with identical AI-generated names), and build the thing _you're_ passionate about — Stellar has always been about local builders shipping local solutions.
-
-## Closing
-
-I also gave a shout to the **Pulso hackathon** in São Paulo (on DoraHacks), whose prize includes a fully sponsored trip to the Stellar Summit, with live pitches across Argentina, Brazil, and Colombia. I'd planned to close with a live `stellar-build` session — using the Justin and Nicole personas to show off the new self-running loop and spin up a ZK project idea — but at 75 minutes and seven cups of coffee deep, I saved it for next week. Next week we also have another guest, so please be there.
diff --git a/meetings/2026-07-02.mdx b/meetings/2026-07-02.mdx
deleted file mode 100644
index e75adc951..000000000
--- a/meetings/2026-07-02.mdx
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: "2026-07-02"
-authors: kaankacar
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="N7PtAJaELzA" />
-
-## A Week About Privacy
-
-This week wasn't about AI — it was about your second-favorite subject: **privacy**. Per the Electric Capital developer report there are now more than **2,000 developers building on Stellar** in a given week, and hopefully you're one of them.
-
-Two reasons privacy was the theme. First, there was exactly **one day left** to submit to the Real World ZK hackathon on DoraHacks — the best possible time to be building with zero knowledge. Second, an hour before the call we published the **developer preview of confidential tokens** on Stellar, which pairs naturally with this week's guest. So the plan was: guest first, then a plain-English tour of confidential tokens.
-
-## Guest: Zarf — Private Token Distribution by Email
-
-Our guest was **Zarf** (zarf.to), a Turkish project that lets you distribute tokens to an **email address** rather than a wallet address. Recipients claim with a familiar "sign in with Google" button, and their browser quietly proves they own that email using a zero-knowledge proof — so the recipient's wallet is never linked to a person, and nothing on-chain says who received what. This was a special one for me personally: **Yaman**, one of the founders, is the first person I ever met in web3, at my first hackathon a bit over four years ago.
-
-Yaman introduced Zarf alongside **Dennis**, who has spent three to four years in the ZK space (previously an exploration engineer at O1 Labs on the Mina protocol, and before that in web2 cyber security). The team builds things that are only possible with zero-knowledge proofs, and got excited about Stellar once the protocol gained **native, cheap ZK-proof verification** — with the heavy elliptic-curve math implemented as protocol-level precompiles, verifying a proof on Stellar became genuinely inexpensive.
-
-### The Problem
-
-When you send tokens on a blockchain, the recipient's wallet is always exposed. In token distributions and private sales, anyone can watch who claimed what — a strong signal for whales-watching and an easy way to get doxxed. Zarf's origin was a hackathon project at Devconnect in Buenos Aires: a proof-of-attendance tool that let you _prove_ you'd attended an event via an email you received, then mint it as a POAP-style NFT. That grew into the more general idea of using an identity you already have — a Google account — for private, programmable token distributions.
-
-### How It Works
-
-The primitive underneath Zarf is **ZK JWT** — zero-knowledge proofs over the JSON Web Token that Google signs when you log in. When you sign in with Google, Google digitally signs your JWT; inside the circuit, Zarf verifies that signature against Google's published public keys, confirms the key really belongs to Google, and parses your email — all in zero knowledge. That proof then lets you **claim from any wallet you like**, and different claims can come from totally unlinked wallets (wallet A for one batch, wallet B for the next), even a single-use stealth address.
-
-Dennis was careful to distinguish ZK JWT from **ZK email**: ZK email proves the signature of an email's _sender_, while ZK JWT is specifically for authentication and identity. They prefer ZK JWT because the UX is far better — no forwarding emails or uploading `.eml` files; you just open the page and log in with Google, and the proof is generated behind the scenes.
-
-The best framing we landed on: Zarf is a **privacy-focused version of the Stellar disbursement platform** — instead of handing over a CSV of wallet addresses, you hand over emails, and people claim from whatever wallet they want, so nobody can track balances or link an identity to a wallet.
-
-### The Architecture
-
-A few implementation details worth capturing:
-
-- **Proof system.** Zarf uses **Noir** rather than Circom. Noir brings faster proof generation and, importantly, **no per-circuit trusted setup ceremony** (it relies on a universal setup instead).
-- **Four contracts.** A factory, a vesting contract, a verifier contract (invoked on every claim to check the proof), and a **JWK registry** that holds Google's public keys.
-- **The Google key-rotation challenge.** Google rotates the public keys that sign JWTs roughly every two weeks (not exactly, and not all at once). Zarf runs a **Cloudflare worker** that fetches the current keys and writes them on-chain so verification stays valid. This is the biggest open problem; the team is exploring more trustless approaches (e.g. zkTLS to prove the certificate URL directly) and even offering a shared Google-certificate registry as a public good for the whole ecosystem.
-- **The privacy model.** To break the email↔wallet link, Zarf parses your email from the JWT, generates a secret **pin code**, hashes the pin, hashes your email, and places the hashed identity in a **Merkle tree**. At claim time the circuit verifies the Google-signed JWT, derives your unique identifier, walks the Merkle proof to the root, and compares that root against the distributor's on-chain vesting contract. The pin prevents anyone who merely knows your email from brute-forcing to find you in the tree.
-
-### The Demo
-
-Yaman created a live token distribution on testnet — upload an email list, auto-build the Merkle tree, set a vesting schedule, deploy — then tried to claim. Proof generation and some caching got in the way and the claim didn't land cleanly on the call (it had worked in rehearsal). As I like to say: you're not really a builder if your demo works every time. It's a fine reminder of exactly why beta testers matter — better to get roasted in private than in front of 250 live viewers. Zarf is **SCF cohort 42**, heading to mainnet after its audit (likely within the week), and looking for beta testers via zarf.to and X (@zarf).
-
-## Confidential Tokens: The Other Half of Privacy
-
-After the guests left, I did a "so what?" walkthrough of the **confidential token rails** we previewed that day, built by OpenZeppelin — because Zarf and confidential tokens solve two _different_ privacy problems and it's worth seeing the contrast:
-
-- **Zarf hides identity.** The email↔wallet link is never revealed. But once a claim lands, the recipient's wallet, the amount, and the claim event are all still public on-chain — fine in many cases, problematic in others.
-- **Confidential tokens hide amounts.** Instead of storing a plaintext balance, the token stores each balance as an **encrypted commitment**. Transfers move encrypted amounts and carry a zero-knowledge proof that the transfer is _valid_ (the sender had enough, the amount is a positive integer, inputs equal outputs) **without revealing any of the amounts**. Only the holder — and optionally an **auditor** who holds a decryption key — can read the balance, which is how you'd add a compliance layer.
-
-The mental model is a handful of methods: **register, deposit, merge, transfer, withdraw**. To participate at all you first **register** (a one-time zero-knowledge proof generated locally in the browser). You then **deposit** public tokens into your encrypted balance, **merge** received amounts so they become spendable, and **transfer** confidentially. Confidential tokens behave like SEP-41 tokens, so in theory they compose — but they're best at **additive accounting** (adding and subtracting amounts), and not the right tool for multiplication, price discovery, or deep public composability, where time-sensitive proof generation gets in the way. This is a confidential _token_, not a dark pool that hides the operation itself.
-
-To make it concrete I vibe-coded a tiny **confidential wallet** for the meeting — two accounts, Alice and Bob — that walks through registering, depositing public XLM into an encrypted balance, merging, and then transferring confidentially so nobody can see how much moved. It reuses OpenZeppelin's confidential-token contract from the developer preview, so I was cutting corners, but it makes the flow tangible. The GitHub link is in the stream, and the real source of truth is the developer preview itself.
-
-## Closing
-
-With ~20 hours left on the Real World ZK hackathon deadline and a strong turnout of hackers, there was still time to ship something small and submit. Next week's guest is Hyperron. Thanks for watching — see you then.
diff --git a/meetings/2026-07-09.mdx b/meetings/2026-07-09.mdx
deleted file mode 100644
index 8891e1d71..000000000
--- a/meetings/2026-07-09.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-title: "2026-07-09"
-authors: kaankacar
-tags: [protocol]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="IIfVUmkzCdA" />
-
-This week was a protocol discussion. Dmytro Kozhevin (Dima) from the core team presented two CAPs: [CAP-85](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0085.md) and [CAP-84](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0084.md). He started with CAP-85, because CAP-84 had already drawn some concerns and was likely to take longer.
-
-## CAP-85: Externally Managed Contract Executables
-
-CAP-85 came out of ecosystem requests. Every Soroban contract can already update its own Wasm, but only one contract at a time. If you run a fleet of contract instances that must share the same code, for example a set of token contracts, you need a custom batching contract today. That only works if the whole update fits into one transaction's resource limits.
-
-The CAP adds a third executable type next to Wasm and the Stellar Asset Contract: an **executable reference**.
-
-- The contract does not store its own Wasm hash. It points to a contract data entry owned by another contract, which the CAP calls the owner contract. You can think of it as a manager contract.
-- Lookup gets one more step: find the reference, read the Wasm hash from the owner contract's entry, then load the code.
-- When the owner contract updates the hash, every contract that points to it updates atomically. No need to iterate over the fleet.
-- One manager contract can own many references, so a whole protocol with several different implementations can be updated in one transaction.
-- Existing contracts can switch to an executable reference with an update, and they can switch back to a plain Wasm executable later. Nothing is one-way.
-
-### Safety: the executable tag
-
-A plain contract data entry could be deleted, or set to a value that is not a valid Wasm hash. A bug in a manager contract could then make the whole fleet unusable until someone fixes the entry. To remove that class of errors, the CAP adds a new object type, `ExecutableTagObject`, which wraps a string and must be used as the key of a reference entry. Because the protocol can now recognize reference entries, it:
-
-- does not allow anyone to delete them, and
-- only allows updates to the hash of a Wasm that is already uploaded on chain.
-
-The only remaining way to break the fleet is to point it at valid Wasm that does the wrong thing, which the protocol cannot detect.
-
-### TTL extension and state archival
-
-The existing functions that extend the TTL of contract code will extend both the code and the reference entry when a contract uses a reference. The intent of these functions is to keep everything the contract needs to run alive, so extending only one of the two entries would be surprising.
-
-The reference entry is persistent storage, so state archival works as usual. If it gets archived, simulation generates a restore, someone pays the restore fee, and the contract keeps working.
-
-### Questions from chat
-
-- **Smart wallets and modules**: A smart wallet could use a manager contract to update all of its modules atomically. Dima called this a good example of a use that the CAP did not originally target.
-- **Authorization context**: Custom accounts receive a context that describes contract creation, so the CAP extends that structure with the new executable type. A policy could allow or block contracts created from a reference. This is a small backwards-compatibility point: an account that parses the context needs a newer SDK to read the new type. It only matters if the account itself creates such contracts.
-- **Alternatives**: The team compared other designs and chose the one that is the most flexible and ergonomic for Soroban.
-
-## CAP-84: Muxed Contract Addresses
-
-[CAP-67](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md) brought muxed addresses to Soroban, but only for classic `G` accounts. A muxed address bakes an off-chain identifier into the address. A custodian such as an exchange can serve thousands of users from a handful of on-chain accounts, and the identifier appears in the token events.
-
-CAP-84 extends the same idea to contracts. A muxed contract address is the 32-byte contract ID plus a 64-bit ID, and it gets its own strkey. The existing muxed address object and host functions cover the new type, so:
-
-- SEP-41 does not need to change, and
-- contracts that already accept muxed addresses pick up the new type automatically.
-
-### Is there demand?
-
-George raised the main concern in the [discussion thread](https://github.com/stellar/stellar-protocol/discussions/1950). The XDR change is small, but a new strkey type is a large ecosystem change. Every SDK, and every wallet or backend that handles addresses, has to support it. George asked for concrete use cases from builders, and asked whether Soroban's programmability could solve the problem without a protocol change. He gave claimable balances as an example of a feature that shipped before the need was clear.
-
-Dima's answers:
-
-- Jake Urban wrote the CAP and works with builders of custodial contract wallets. These builders want to integrate SEP-24 on and off ramps, but they cannot use memos or muxed destinations with contract accounts today.
-- Memos are not safe in Soroban. Authorization is detached from the transaction on purpose, so you cannot reliably tie a memo to a given event.
-- The other option discussed during CAP-67 was a new transfer function with a separate destination ID. That brings back the two-part address problem of memos, and every contract would need to change to support it.
-- An account per user is expensive and hard to operate, especially for contract accounts. A custom wrapper token would bypass most of the ecosystem.
-- Integrators that already parse the CAP-67 unified events get the muxed ID from the events without needing to handle the new strkey.
-
-Dima's view: the CAP is not guaranteed to be merged, but if the protocol supports muxed contract addresses, this is the cleanest way to do it. George agreed that the implementation details matter and asked for a concrete picture of how a custodial contract account would work with SEP-24 without the CAP. The discussion moved to the thread and continued the next week.
-
-Please add your comments to the [CAP-85](https://github.com/orgs/stellar/discussions/1969) and [CAP-84](https://github.com/stellar/stellar-protocol/discussions/1950) discussion threads.
diff --git a/meetings/2026-07-16-protocol.mdx b/meetings/2026-07-16-protocol.mdx
deleted file mode 100644
index 3159437cb..000000000
--- a/meetings/2026-07-16-protocol.mdx
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: "2026-07-16 Protocol Discussion"
-authors: kaankacar
-tags: [protocol]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="jNOereJv_Fk" />
-
-This week's protocol discussion had two parts. First we wrapped up the [CAP-84](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0084.md) debate from [last week](./2026-07-09.mdx). Then Dmytro Kozhevin (Dima) presented [CAP-86](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0086.md). Discord gave a few people audio trouble at the start, so if you could not hear Dima live, the recording above is the place to catch up.
-
-## CAP-84 Follow-Up: Why Muxed Contract Addresses
-
-Jake Urban, the author of CAP-84, joined to explain the product case. His core point: every valid reason to mux a `G` account also applies to contract accounts.
-
-- **Omnibus accounts**: Most exchanges take deposits and withdrawals on `G` accounts with memos or muxed addresses. If an exchange or custodian moves to smart accounts, it loses both options, because a contract invocation cannot carry a memo.
-- **Per-payment IDs**: On and off ramps attach an off-chain ID to a payment to reconcile it with the on-chain transfer. A muxed contract address can carry that ID in the address itself.
-
-George restated his concern from last week. He does not have a strong objection, but he wanted the group to check if a Soroban-level pattern, such as a standard omnibus contract that emits the ID in events, could reach the same goal without a protocol change. He noted that the impact is smaller than he first thought, because integrators that read the CAP-67 unified events do not need the new strkey.
-
-Jake's reply:
-
-- A contract-level pattern would give each address type a different interface, which is a footgun for developers and would slow contract account adoption.
-- Today you send a muxed deposit by calling the token contract directly. With a custom pattern, you would call the contract account, which then calls the token. That is a worse developer experience.
-- Muxed `G` addresses already exist, so leaving contracts out feels like going halfway.
-
-George agreed that fragmentation is a real concern and was fine with the decision once the alternative was considered. Dima added that a single address string is much safer than an address plus a separate ID. Users lose funds when they forget the memo, which is why muxed accounts exist in the first place.
-
-A builder in the audience gave a real example. Their team won an SDF RFP for a smart account onboarding protocol. Today, on and off ramps cannot deposit directly to a `C` address, so they run a relayer: deposits go to a pooled `G` address with a memo ID, and the relayer forwards the funds to the user's contract account. Muxed contract addresses would remove that whole layer. With that, the group considered George's question about demand mostly answered.
-
-## CAP-86: Sparse Map Reads and Writes
-
-CAP-86 fixes a problem that Soroban has had since launch: you cannot change a `#[contracttype]` struct without breaking every reader of that struct.
-
-The SDK uses fast host functions to convert structs to and from maps. These functions require every requested field to exist, and every field in the map to be consumed. If you add, remove or rename a field, the reader traps. The contract cannot catch the error and try another layout. People have hit this in practice: they upgraded a contract, added a field to the struct that holds the admin, and could no longer read that struct, so they could not upgrade again.
-
-The CAP adds two host functions, `sparse_map_new_from_linear_memory` and `sparse_map_unpack_to_linear_memory`:
-
-- **Sparse reads**: The reader names the fields it wants. The map can have more fields than requested. A missing field comes back as `Void`, which the SDK can map to `Option::None`. If you need a field, make it non-optional and the read fails as expected when the field is missing.
-- **Sparse writes**: A `None` field is not written to the map at all. This saves storage and makes event payloads with many optional fields smaller. Dima mentioned SEP-41 events with an attached map as one use.
-
-This enables migrations that were not possible before. You can add an optional field and fill a default when it is `None`, remove fields you no longer need, and extend structs passed between contracts without new functions. Dima compared it to protobuf v3, where every field is optional and the reader decides what is required.
-
-Caveats:
-
-- If two contracts disagree on a field name, an optional field could silently read as `None`. This needs a miscommunication and an optional field, so Dima considers it a small risk compared to the one it removes.
-- Old readers break if a writer starts omitting `None` fields, because they expect every field. The SDK will decide when to use sparse writes.
-- The CAP adds new functions and does not change existing ones, so no deployed contract changes behavior. To use the new semantics, you must update the SDK and rebuild your contract.
-
-Performance is the same as the current functions, or slightly faster when you skip fields.
-
-Please add your comments to the [CAP-84](https://github.com/stellar/stellar-protocol/discussions/1950) and [CAP-86](https://github.com/orgs/stellar/discussions/1877) discussion threads.
diff --git a/meetings/2026-07-16.mdx b/meetings/2026-07-16.mdx
deleted file mode 100644
index 5f2d9881a..000000000
--- a/meetings/2026-07-16.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-title: "2026-07-16"
-authors: kaankacar
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="Zv_scYurQMI" />
-
-## The Week I Mostly Shut Up
-
-Probably my favorite Stellar Developers meeting so far, and — unusually for me — I spent most of it not talking. The occasion: introducing **Stellar Raven**, the unified Stellar-ecosystem MCP gateway. My pitch in one line: the first, last, and only thing you need to build on Stellar — Stellar docs and ecosystem context in one connection. You might think "oh, it's just an MCP." You would be mistaken, and I brought four guests to explain why.
-
-Quick introductions. **Bri** has been on the ecosystem team at the foundation for about four and a half years and does a lot of the storytelling around what Tyler builds — a job description that now includes Raven. **Boxy** built **Stellar Light** and focuses on data indexing: making ecosystem data smart and high-quality enough that Raven keeps getting smarter from it. **Ralph** wears many hats in the ecosystem but joined as the builder of **Lumen Loop** (lumenloop.com), a discovery platform for everything happening on Stellar. And **Tyler** — still a developer advocate director, and together with Bri quietly spinning off a new team inside the foundation to work on exactly this kind of thing. Don't tell anybody.
-
-## What Raven Actually Is
-
-Tyler's framing: the problem Raven solves is **context**. It's an MCP (Model Context Protocol) server that aims to ensure agents know the _truth_ about Stellar when you ask a question or build something.
-
-The corpus of Stellar truth is scattered, and some of that is structural. We're open source with a very open culture, so a lot of what's true about Stellar lives outside the foundation's control. We run a hackathon on one SDK version, ship a new release two months later, and now SEO is actively working against us: LLMs index a pile of once-true, now-outdated information. Everyone builds off a Blend or Soroswap repo at a hackathon; those repos are static (you can't update deployed contracts), so freshly generated content keeps encoding stale best practices. Recency is a bad signal when the new content was generated off the old standards; scoring what's actually true is genuinely tricky.
-
-Tyler had solved this for himself with a personal deep-research workflow, but "install these ten skills and four MCP servers" is not a shippable product. Raven is that build workflow surfaced as a single service — the **fifth version** he's tried to build over almost a year, and it only got serious once Lumen Loop and Stellar Light/Scout existed as APIs he could route to. Under the hood, Raven pulls together **Lumen Loop**, **Stellar Light**, the **Stellar docs**, all the **Stellar skills**, and the **Algolia** indexes behind the docs and the site, plus general research tools like Parallel and Perplexity in the research pipeline.
-
-The broader thesis: anyone seriously evaluating chains is comparing Stellar against several ecosystems, each with its own sprawl of bespoke skills and MCPs. Nobody maintains all that. If we want people to give Stellar a fair chance with their LLMs, there has to be **one tool**. That's the niche.
-
-## The Sources: Lumen Loop and Stellar Light
-
-Ralph and Boxy overlap on purpose — two independent sources of ecosystem truth mean you can cross-check what works.
-
-**Lumen Loop** is content-first and agentically driven: backend agents discover content, attach metadata, generate summaries and embeddings, look up SCF information, occasionally disagree with it and self-correct, and publish the result to an open **ecosystem database on GitHub** that others (like Boxy) build on. Ralph's favorite party trick lives at labs.lumenloop.com: a **constellation view** of the entire ecosystem — every piece of content and how it relates to everything else. We've never been able to see that before, and it's just one source behind Raven.
-
-**Stellar Light** started as a discoverability problem and grew once agents entered the picture. Boxy's current frontier is **repo indexing**: ingesting thousands of repositories from Electric Capital and other sources and actually trying to understand the code depth inside each one, so questions get answered from real code rather than vibes. It's hard, and token-hungry — Boxy has been hitting model limits doing it.
-
-The shared hope: less time on the boring things. SCF reviews, hackathon judging, hunting for the right link — all of that is exactly the shape of work Raven quickens.
-
-## Truth Is a Garden
-
-The part I found most interesting is how Raven improves itself, because the core issue with LLMs is that **they don't know when they're wrong**. Give an agent disparate sources and superseded information and it will grab something, hold it confidently, and careen off a cliff in a burning cloud of tokens. MCPs don't fix that. Skills don't fix that. Continuous re-research of truth fixes that — Tyler's metaphor: truth is a **garden**, not granite. Things go live, die, migrate; somebody has to keep re-indexing and re-scoring. Concretely:
-
-- **Golden QA.** The team mined Stack Exchange, Discord, and old Stella logs for almost **500 common Stellar questions**, then ran long, expensive research against each — Lumen Loop, Stellar Light, the docs, the site, web research — to produce golden answers.
-- **Evals.** Ask Raven the same questions, have a model grade Raven's answer against the golden one, and — the fun part — assign blame. Is a miss a Lumen Loop problem? A Stellar Light problem? Are the docs missing something, or contradicted by a repo?
-- **The loop.** Misses land in an improvements directory and become issues on the right repository, where Ralph's and Boxy's agents pick them up. Telemetry (the whole thing runs on Cloudflare) captures what tools got called and what came back, so agent flows can compare what Raven found against what it should have. Bri pointed out this already works in the other direction too: several issues open on the docs repo right now exist because Raven couldn't answer something correctly _from the docs_ — Raven is making the docs better, not just consuming them.
-
-Two real examples of misses: asked about asset issuers in Latin America, Raven almost never surfaced **Etherfuse** — apparently they don't describe themselves as an asset issuer anywhere, even though everyone expects to find them under that word. And "where can I swap assets on Stellar" almost never returned **Sushi**, new on Stellar and competing with a crowd of existing swap services. Both became golden questions; both improved. When you hit something like this, open an issue on the Stellar Raven repo — that's the mechanism.
-
-Tyler's longer-term vision is **forward-deployed agents**: Raven plus opt-in memory and profiles, so an agent embedded with a partner learns you're always asking about, say, Argentine anchors, and gets more specific over time. You could stand up an agent today, hand it the Raven MCP and your Sentry logs, put it on a loop, and have it PR fee optimizations against your own repo. The pieces exist; they just need packaging.
-
-## Q&A: Live Data, Cheap Models, and Where to Run It
-
-A viewer asked how much you can learn about real-life anchor operations — which turned into the best design discussion of the call: **should Raven serve live data?** Tyler's answer is no, mostly. Raven is a model _context_ protocol, not a data API. It shouldn't call the RPC for you; it should tell your agent where the RPC docs are, who provides endpoints, and let _your_ model write the code. Same for the recent explosion of data sources: **Mercury** (just came back, and very cool), **stellarindexer.com**, **Alchemy's new Stellar API**, Dune, the data-lake tooling like Galexie. Your agent doesn't know what it doesn't know — but once Raven points it at the right sources, your agent is the best tool for the job. Tyler's analogy, which I intend to steal: "I'm going to borrow your body to use my brain." We're giving the agent the tools, not building it the house.
-
-The same logic answers the hosted demo question. There's a **playground** on the Raven site, and you should treat it as exactly that: heavily rate-limited, a really cheap reasoning model, capped search/execute turns — Tyler is understandably not exposing hundreds of dollars of frontier-model compute to the open internet. Use it to see which tools get called and get a feel for the answers (we asked it "who is Justin Rice" live, and for a throttled setup it did honestly fine), but the real product is **Raven installed in your own IDE or agent**, where a frontier model gets far more out of the same context. That's also why there's a sign-in: a standard OAuth MCP login, needed for rate limiting today and the opt-in memory features later.
-
-Other questions from chat, rapid-fire:
-
-- **Test suites and security?** Raven would be phenomenal at it as the repo indexing matures — find repos that already cover fuzz testing and common error patterns, then plug that into whatever monitors your backend. The follow-on idea everyone liked: index **audit reports**. Lumen Loop surfaces audits but only as links; the trick is accurate summaries so Raven knows _when_ an audit is relevant, then hands your agent the full source. Same pattern as Raven's planned **ephemeral artifacts** for oversized responses — just the right context at just the right time.
-- **Does Raven speak Spanish?** Whatever your terminal speaks. The proxied APIs are mostly English semantic search, but your agent translates on both ends.
-- **Can we make a sassy Raven?** Wrap it in your own agent and give it whatever personality you want — one of the crew confessed theirs answers as Princess Donut from Dungeon Crawler Carl. Mine calls me Mr. Kaan. I want professional distance from my agent.
-- **Is this a Stella replacement?** Different animal. Tyler was blunt: Stella was a great experiment and he's glad it died — it made Discord unsearchable, a huge share of prompts were vandalism attempts or non-Stellar questions, and an agent-as-a-service collects PII you then have to worry about. Raven inverts the model: a service that _your_ agent calls, with tool-use-shaped telemetry instead of raw prompts. My addition: Stella existed because models couldn't read our docs properly back then. Frontier models read docs fine now — the scarce thing is dynamic, current ecosystem context, and that's precisely what Raven addresses.
-
-## Tangents Worth Keeping
-
-Building this stuff is not cheap: Tyler estimated around **20 billion tokens** in the last couple of weeks alone. That led into a review of token-saving tools — **headroom** (compresses JSON and log output), **caveman** (make prose short, why speak much when few word do trick), and **ponytail** (don't over-engineer; less code when little code does the trick). Verdict: modern models are too smart to be talked to stupidly. Headroom-style compression made them suspicious they were missing something, so they looped and burned _more_ tokens; caveman's brevity triggered extra reasoning to reconstruct the stripped context. Only ponytail earned its keep, and less for token savings than for code quality. If you're going to install one, install that one.
-
-Best mini case study of the call came from Bri, who is building an application with confidential token transfers and used Raven as a **research tool**: "Alice owns 1,000 USDC, Bob owns 300; Alice deposits 500 into the confidential token wrapper and privately transfers 200 to Bob — walk me through step by step what happens." Raven's answer taught Bri more about confidential transfers than a week of reading. Researching with Raven is as legitimate a use case as building with it — and it's not a one-and-done oracle. Ask, learn a little, redirect, pair it with your other tools.
-
-## Closing
-
-We peaked around 380 live viewers, blew past the hour as usual, and rolled into the protocol discussion half an hour later. Brazilian builders: we'll be at the **Stellar Builder Summit** in São Paulo — find me there and ask me about Raven. Otherwise, ask on the Discord or tag Tyler (@kalepail), Lumen Loop, Boxy, or Bri on X. Every question makes Raven better.
-
-Also, I publicly demanded Raven swag. A bandana would be sick. Slogan's already written: _just ask the Raven._ See you next week.
diff --git a/meetings/2026-07-23.mdx b/meetings/2026-07-23.mdx
deleted file mode 100644
index 51e1d1e1a..000000000
--- a/meetings/2026-07-23.mdx
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: "2026-07-23"
-authors: kaankacar
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="0RpAMlqRmkY" />
-
-## Stellar Quest Is Back
-
-Before the guests, some news from the developer ecosystem — starting with a sentence I haven't been able to say for a while: **Stellar Quest is live again**. If you've been around long enough, you know Stellar Quest was once the most widely shared link between builders in this ecosystem. It's been broken for some time, mostly because third-party services it depended on sunset their operations (including the one that powered the interactive code lessons). That's fixed now — it's live, it's working, and you can use it to get a genuinely hands-on feel for building on Stellar.
-
-Is a click-through learning platform the best use of a developer's time in the post-AI age? That's for you — and for our ambassadors — to decide. What I can say is this: building with AI is insanely easy, and the only thing separating you from AI slop is actually knowing the ecosystem you're building in. You don't have to write the code by hand anymore, but you do have to know what an account is, what a trustline is, what a SEP-41 token is. Stellar Quest is one way to earn that knowledge. Expect a refined version in the coming weeks, shaped by whatever our ambassadors ask for.
-
-On the AI side of the same coin: **skills.stellar.org** keeps growing. It's our skills website, but it's also _your_ skills website — there's a community section with **17 community skills** built by non-SDF people (one of my favorites: a Scout-style skill for researching the ecosystem and SCF before you build), next to **7 official skills**, with three more official ones visible in the open-source repo if you go looking. Adding your own is a pull request away — there's an example skill-card entry in the repo showing exactly how to submit. Building on Stellar with AI gets easier every day; Stellar Quest is there when you want to slow down and actually learn.
-
-## Guest: Hypertron — Private Payments and Operations for Businesses
-
-This week's guest was **Hypertron** (hypertron.space), a programmable operating layer for **B2B payments and operations on Stellar** — think payments, treasury, and compliance workflows for a business, with privacy as an opt-in layer on top. **Sweta** and **Soumik**, the two co-founders, joined from India at 11:47 p.m. their time (self-declared night owls, so it's fine).
-
-Some backstory: the two met in college, ran an agency and freelanced together, and fell into web3 in late 2023 through hackathons — ETHIndia was the first big one. Since then Sweta has worked at a Solana-based company, on early NFT projects on Base, and currently also does security work at Hacken; Soumik has worked for a prediction market on Solana and a payments company. This one was personal for me too: I first met them at a Rise In hackathon in Bangalore about two years ago, on my second day ever in India. I mostly remember the biryanis.
-
-Why Stellar? Their answer was better than the usual one. Stellar targets institutional clients and has always been a **public blockchain by design** — which they think is the right default. Traditional finance is private by default with auditability on request; public blockchains are transparent by default. Hypertron's whole thesis is to add privacy _on top of_ the public chain, without giving up the verifiability that makes a public chain valuable in the first place. The problem is concrete: once a business runs payroll and vendor payments in stablecoins, anyone — a client, a competitor, a very motivated employee — can trace its treasury. Wallets get poisoned, payments get tracked. That's the gap they're filling.
-
-### The Application Layer
-
-Soumik demoed the product side. There's a **sandbox** on hypertron.space so you can poke around before connecting anything, and sign-in is gated behind an invite code they shared live on the stream. You connect with a Stellar wallet (Freighter in the demo) and land in a **workspace** — and you can manage several, one per business. Creating one is a guided onboarding: pick the business type (protocol, DAO, agency, freelancer), and the modules adapt — an agency doing dev work doesn't need heavy compliance tooling, a DAO very much does. You choose the operations you want (payments, treasury, risk reports, compliance), invite teammates, wire in integrations like Slack for transaction notifications or Gmail/Notion/Google Drive for the paperwork around employees and invoices, and set your geography so the risk and compliance reports (delivered daily to Telegram or WhatsApp) actually match your market.
-
-The payments demo was the simple, satisfying kind: create a payment of 10 XLM with a description, get a **payment link**, open it from a second wallet, pay — settled near-instantly, tracked in the dashboard. XLM and USDC are supported today, with more assets planned. For real integrations there's a **developer portal** with API keys, docs, and an SDK, plus an **MCP** in the works so you can wire Hypertron into your app from an AI tool in minutes. To make it tangible, Soumik built a demo app _that day_: a Pokémon NFT marketplace with Hypertron checkout. Buy an NFT, get redirected to the payment link, pay, and a **webhook** bounces you back to the marketplace with the NFT already in your account. The stablecoin payment stack and APIs are live now, with the full v1 targeted about two weeks out.
-
-On monetization: honest answer, still being figured out — likely pay-per-use across the smaller features rather than a cut of payments alone. One of those features is **bridging**: a business already operating on Ethereum, Solana, or Avalanche can move its treasury over to Stellar specifically to use the privacy payments. That's a fun acquisition channel if it works.
-
-### The Privacy Stack
-
-Sweta took the second half, and this is where it gets interesting for protocol nerds. Their framing: privacy isn't a rule, it's a **spectrum**, and it doesn't start with a circuit — it starts with the question _what needs to be hidden_. They've built a private-payments evaluation framework around six leakage dimensions: **sender, receiver, amount, timing, linkability, and metadata**. Confidential tokens, for contrast, hide the amount but leave sender and receiver public. Hypertron's target is **linkability** — nobody should be able to learn who pays whom — while keeping compliance deliberately open through **viewing keys**, so an auditor with the right key can still see what regulators need to see. Their privacy matrix today: sender, receiver, amount, and linkability covered; timing still partial (that's a batching-and-delay problem); compliance intentionally left open. In the app it'll surface as an **opt-in privacy button** on otherwise normal transparent payments.
-
-The architecture, in one breath: proofs are generated **locally** (the provers never leave your device), a **relayer** sponsors fees and submits, commitments land as leaves in an on-chain **Merkle tree**, and **nullifiers** handle spend-tracking. Four contracts ship the whole thing — commitments, nullifier, verifier, and a transfer contract that orchestrates shielding, sending, and unshielding with a single integration point for the merchant app.
-
-What I liked most is that they're packaging it twice. For protocol builders there are **composable Rust crates** — Merkle trees, nullifiers, proof verification, disclosure mechanisms — so you can assemble your own privacy design instead of rebuilding from scratch: relayers plus a ZK pool if you care about sender privacy, confidential tokens for payroll, a mixture with auditing for treasury settlements, pooling-batching-delay for anonymous donations. For application builders there's an **npm package** with a compiled WASM prover, so you generate proofs without ever touching the cryptography. Everything leans on the primitives the protocol now ships natively — the BLS12-381 pairings that landed in Protocol 22 and the Poseidon hashing from January's **X-Ray (Protocol 25)** upgrade — rather than porting verifier and hashing libraries in. That's also their differentiation pitch against Nethermind's **SPP** shielded pool: shielded pools go back to Zcash in 2016, and Hypertron's angle is composing the on-protocol primitives instead of shipping a ported stack. When I asked why BLS12-381 over BN254 (the more common choice for shielded pools), the answer was refreshingly honest: not entirely sure yet, the goal is fast verifiable circuits. Pools are per-asset — XLM first, more later.
-
-The CLI demo walked the real flow: query the last indexed Merkle root, compute a Poseidon commitment from secret inputs, run the deposit — commitment on-chain, proof generated and submitted, transaction shielded. Then the private-transfer proof failed on an indexing error, live, in front of 200+ people. As regular viewers know the rule by now: you're not a real builder if your demo works every time.
-
-### The Fine Print
-
-My PSA from the stream, repeated here for the record: Hypertron is a project in development, running on **testnet**. These things _should_ happen — that's the point of showing them — but it's not a live business yet, so don't route your company's treasury anywhere just yet. The open-sourced v2 of the contracts was days away at recording, and viewers were already asking about integration pricing live on the stream, which is honestly the best kind of validation a pre-launch project can get. Follow them at x.com/hypertron_HQ.
-
-## Closing
-
-X-Ray has been live for about six months now, and privacy on Stellar still fascinates me — we've gone from protocol primitives to confidential tokens to shielded pools, and now to teams like Hypertron trying to be the B2B application layer on top of all of it. A private payments product for businesses is a whole different level of hard, and I'd love to see more projects emerge in this lane. We crossed **250 live viewers** by the end — thank you for that. Next week I'm planning a session on the cross-chain interop options available to Stellar builders, plus another guest. See you then.
diff --git a/meetings/2026-07-30.mdx b/meetings/2026-07-30.mdx
deleted file mode 100644
index 440d4827f..000000000
--- a/meetings/2026-07-30.mdx
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: "2026-07-30"
-authors: kaankacar
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="57fB8A5vhj0" />
-
-## Two Developer Advocates, One Call
-
-The twist this week: I wasn't the only developer advocate on the stream. Most of SDF was heads-down preparing for **Stellar House in Brazil** the following week — and if you were in Brazil, you were probably at the **Stellar Builder Summit** at that very moment. If not, I shouted you out for no reason.
-
-The topic was **cross-chain interoperability with CCTP** — Circle's Cross-Chain Transfer Protocol — and USDC on Stellar. My guest was **Elliot** ([@elliotfriend](https://x.com/elliotfriend) just about everywhere — if you can't find him on a platform, type "elliotfriend" into the search bar and be done with it), a senior developer advocate at SDF and genuinely one of the people I've learned the most from since joining. He's been in and around the Stellar ecosystem for six-plus years, having wandered into the Stellar Quest Discord out of curiosity about how the machine actually worked — not to trade altcoins — and never looked back. He built the CCTP demo himself, so I got out of the way and let him drive.
-
-## CCTP in One Paragraph
-
-Some framing before the demo. USDC has been native on Stellar since 2021, so this isn't a story about finally getting the token here — it's about how it _gets_ here. Until recently, moving USDC from Ethereum or Base onto Stellar meant a centralized exchange or a third-party bridge: a human does it out of band while your application sits there waiting for a balance to appear. **CCTP turns that into a contract call.** Circle is the issuer of USDC, so nothing needs to be locked anywhere: you **burn** USDC on the source chain, Circle signs an **attestation** that the burn happened, and you **mint** the same amount on the destination chain. Same canonical USDC on both sides, and the whole thing is something your code can start and finish on its own. CCTP went live on Stellar this past May.
-
-Elliot's history lesson made the "why" concrete. Cross-chain bridging has traditionally been done two ways: **lock-and-mint** (lock tokens in a vault on chain A, mint a wrapped representation on chain B — wrapped BTC being the classic) or **liquidity pools** (deposit real USDC on chain A, withdraw real USDC on chain B). Both approaches end with a giant pile of USDC sitting somewhere, and giant piles attract bad actors. CCTP's version has no pile: the tokens are _gone_ on the source chain, and real, canonical USDC — not a wrapped token, not a pool that can get drained — is minted on the destination.
-
-## The Demo: Stellar to Arc
-
-Elliot's demo app is live at [cctp27.vercel.app](https://cctp27.vercel.app) — named after Stellar's CCTP **destination domain, 27** — and the whole thing is open source. He ran it against **Arc testnet** (Circle's chain, domain 26) because Arc is usually quick, but it works the same with any CCTP-enabled chain; he's wired up the EVM chains and Solana.
-
-First transfer: 5 USDC, Stellar to Arc. The deposit-for-burn invocation on the Stellar side takes a handful of arguments worth knowing:
-
-- **Amount** — Stellar USDC has **seven decimals of precision**, so 5 USDC is 50 million stroops. Every other CCTP chain uses six. Why? Per Elliot: "I don't know why, but it is."
-- **Destination domain** — 26 for Arc, 27 for Stellar.
-- **Mint recipient** — the destination address, passed as 32 bytes.
-- **Burn token** — the USDC SAC address.
-- **Destination caller** — leave it all zeros and _anybody_ can call the mint function on the destination chain, making the mint permissionless; set it if you want only the recipient to be able to.
-- **Max fee and finality threshold** — these matter for _fast_ transfers on slower chains. Out of Stellar, standard (threshold 2000) is the only supported mode, because Stellar already reaches finality in seconds. Fast transfers exist for chains like Ethereum and its L2s — and Elliot's favorite, Starknet, which can take **four to eight hours** to reach finality before you can mint.
-
-Out of the box this is a two-transaction flow on Stellar — an allowance **approval** on the USDC SAC, then the **deposit-for-burn** — which bugged Elliot enough that he wrote a **wrapper contract** that does both in one atomic transaction. He demoed it with a 3.14 USDC transfer, "because I'm a dork." Either way, the rest is the same: wait for Circle's attestation ("Circle's permission slip that the burn actually happened"), confirm the mint in MetaMask, watch the balances update.
-
-## The Gotchas: Getting USDC _Into_ Stellar
-
-Before going the other direction, Elliot flagged the part that will "totally torch your funds if you're not careful." On EVM chains a mint recipient is a 20-byte address; CCTP gives you a 32-byte field. For transfers _into_ Stellar, you cannot just drop your G address (or M, or C address) in there. Circle requires the mint recipient — and the destination caller — to be the **CCTP forwarder contract**, as the raw 32 bytes underlying its C address (the Stellar SDK will decode those for you).
-
-Your _actual_ destination goes into the **hook data**, which has a strict layout: 24 zeroed "magic bytes," a version field (currently zero), a length field, and then your G address as a hex-encoded **UTF-8 string** — the string key itself, not the decoded public key bytes. Get that layout wrong and your funds go somewhere you didn't intend.
-
-The live Arc-to-Stellar run promptly hit Arc testnet's aggressive RPC rate limits, which gave Elliot the chance to show off my favorite feature: **resume from burn hash**. Paste the transaction hash of an earlier burn, the app fetches Circle's attestation, Freighter pops up, and you approve the `mint_and_forward` call on the forwarder contract. Five USDC landed back in his Stellar wallet.
-
-## Solana, ATAs, and Every Chain's Opinion
-
-This project was Elliot's first real development against Ethereum and his first Solana transaction ever ("so I'm pretty much an expert on Solana"). Two observations from that tour. First, every ecosystem has its own flavor of contract bindings — the Stellar CLI generates TypeScript or Rust bindings, EVM has ABIs, Solana has IDLs — and they all save you from hand-assembling binary data on the front end. Second, every chain has its own opinion about the 32-byte recipient: EVM addresses are right-aligned and zero-padded; Solana addresses fill all 32 bytes; Stellar wants the forwarder plus hook data.
-
-The Solana catch: your tokens don't live at your wallet address. Every token you hold has an **associated token account (ATA)** — imagine if each of your Stellar trustlines had its own distinct address you sent payments to — and CCTP transfers to Solana must target the ATA, not the wallet. With that handled, a 12 USDC **fast transfer** from Solana devnet to Stellar went through cleanly: burn confirmed in Phantom, attestation arrived in seconds, Freighter approved the `mint_and_forward` carrying the message and attestation from Circle's Iris API.
-
-The closer was **Circle's forwarding service**. Normally you sign — and pay gas — on both sides of a transfer. Going _outbound_ from Stellar (inbound isn't supported yet), you can have Circle submit the destination transaction and cover the gas: it's a relayer, same idea as OpenZeppelin's relayer service or Launchtube, triggered by putting "CCTP forward" magic bytes in the hook data. Elliot sent 11 USDC from Stellar to Solana and the tokens simply appeared — no popup, no destination gas, minus whatever fees Circle took along the way. Getting this working on Stellar testnet took a week or two of politely bugging Circle support (Stellar as a source chain wasn't being indexed correctly at first), so pour one out for whoever fielded those tickets.
-
-## What's Next for the Demo
-
-Elliot's roadmap: try M-addresses and smart accounts (everything so far has been plain G addresses), add more chains beyond "EVM is pretty much the same from one to the next," extend the wrapper contract to **ensure the destination G address has a trustline** before invoking the mint on Stellar-bound transfers, and use the forwarding service to create the recipient's ATA on Solana-bound ones — ATAs aren't opt-in like trustlines, they just have to be paid for.
-
-## Closing
-
-Everything — the app, the contracts, even the slide deck (an HTML page Claude put together) — lives in the [stellar-cctp-demo repository](https://github.com/ElliotFriend/stellar-cctp-demo). Take it, build it, break it, steal it; whatever floats your boat, per the author. A viewer on Twitch asked for the presentation materials, and Elliot's sharing them once refined. Close to 200 of you watched live across YouTube, X, and Twitch. Elliot's parting words: "let your heart guide you." Next week we talk confidential tokens with more SDF folks — see you there.
diff --git a/meetings/2026-08-06.mdx b/meetings/2026-08-06.mdx
deleted file mode 100644
index 375875191..000000000
--- a/meetings/2026-08-06.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: "2026-08-06"
-authors: kaankacar
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="7nta-uFWiRY" />
-
-## Live from Stellar House
-
-This week we streamed from **Brazil**, where the team is camped out for **Stellar House** — if you're around, come on down. The stream itself was a full-hour Q&A about **confidential tokens**, now live on Stellar testnet: private balances and transfer amounts for SEP-41 tokens, with sender and recipient addresses kept public for compliance. I collected **25+ genuinely hard questions** from builders during the summit that just wrapped, the live chat piled on more, and my plan was to ask the easy ones and let you do the damage.
-
-The guests: **Alessandro Voto** (goes by Alex), senior product manager of privacy at SDF — in crypto since 2014, and the conduit between institutions asking for private payments and the people implementing them. Design questions went there. Technical ones went to **Jay Geng**, a stellar-core engineer at SDF for four-plus years who worked on Soroban and the host functions that brought ZK primitives to Stellar (**Poseidon**, **BN254**, **BLS12-381**), presented an early iteration of confidential tokens at Meridian in Rio last year, and shaped several of this product's early design decisions.
-
-We started with 100+ viewers across three platforms and ended past 250.
-
-## Private Does Not Mean Illegal
-
-A surprising number of the questions boiled down to "is this legal?" Alex pushed back on the premise: nobody scrutinizes what you spent on groceries yesterday, and payment privacy in traditional finance isn't a convenience — it's a mandate. For enterprises it's a dealbreaker; they will not make payments their competitors can watch. Blockchains made payments public as a side effect of protecting transaction _integrity_, never as an end goal.
-
-The SDF position pairs privacy with **compliance readiness**: the tools ship with freezing, clawback, and Stellar Asset Contract passthroughs, deliberately open-ended because disclosure requirements differ by jurisdiction — you figure out what "legal" means where you operate, and the boundaries enforce it. That same morning, **José Fernández da Ponte**, SDF's president, had framed the network as _public by default, private by design_ — about the neatest recap available.
-
-Chat asked the obvious follow-up: why the application layer rather than the chain itself? Same reasoning. SDF won't force a privacy regime on anyone happy with the public network's auditability, and application-level privacy lets technologies evolve — some use cases may eventually demand post-quantum designs — without touching the L1. What the core team _did_ ship is the cryptographic host functions that make verifying these proofs on-chain cheap.
-
-## Why Hide Amounts but Not the Addresses?
-
-The single most asked question — more than five builders raised it with me at the summit alone.
-
-Alex's product answer: **confidential tokens are one tool in a toolkit**. If you need counterparty privacy, **Nethermind's Stellar Private Payments** is a privacy-pool toolkit that shields amounts _and_ addresses. Confidential tokens deliberately keep counterparties public because that's what the target users asked for: institutions making regular, publicly known payments — foundations paying grantees, charities, banks settling with each other — where an on-chain record of _who got paid_ is an audit feature, but the _amount_ is the sensitive part. A settlement amount can leak an acquisition intent; a large grant to someone vulnerable can paint a target on them. It's the missing middle setting on Venmo: I want you to know I paid this person, just not how much. (And to chat's "who is this for?" — primarily institutions today.)
-
-Jay's engineering answer: full anonymity is a fundamentally different design. Privacy pools are UTXO-shaped, elaborately grafted onto Stellar's account model, and the proving cost is much higher — you're proving note formation, Merkle-tree inclusion, and unspent nullifiers on every transaction. The confidential token is the more elegant construction: it wraps any existing SEP-41 token — without knowing in advance which asset it will shield — and only encrypts the numbers.
-
-## Auditors, Viewing Keys, and the Escrow Question
-
-The auditor is, in my experience, the single most confusing part for developers, so I asked chat's version directly: how does an auditor see anything without the holder cooperating? Jay's answer: it falls naturally out of the encryption design. Amounts are encrypted under the sender's and recipient's keys — and, in addition, under the **auditor's key**. Whoever holds that viewing key can decrypt the same information, no cooperation required. Policies — who can audit, rotation, key lifetime — don't have to live in the contract logic; it just cares that the key exists. It's decoupled and modular — the key can even belong to a third party that doesn't exist on-chain.
-
-Alex layered the intent on top: there's **selective disclosure**, which is user-initiated ("I can prove this payment happened to whoever I choose"), and there's compelled revelation through the auditor key. The intention is _not_ that someone sits watching the pool — the auditor key should sit unused inside an **MPC or TEE custody setup** (think Utila or Fireblocks, not a Freighter wallet) and only answer scoped requests when a regulator compels one. A single auditor address does not mean a single person; put real key management on it. Alex would be shocked if you didn't.
-
-Then the fun one. Alberto of **Trustless Work** (the escrow project) showed me a confidential-marketplace experiment that day — an escrow contract between Alice and Bob — and asked whether one auditor holding four keys across four "auditor channels" was the simplest compliant setup. The panel's honest answer: the question doesn't quite map onto the design — "channel" is an overloaded word Jay wanted more context on, and the escrow case probably wants selective disclosure rather than extra auditors. One correction from me while writing this up: Alex's on-call recollection was one global auditor key per confidential token contract, but the shipped implementation binds an `auditor_id` per account at registration, out of a shared auditor registry that can hold many keys and serve many tokens — design your compliance around that, not around a single global key. To be continued on Discord once the project ships.
-
-The broader point is worth keeping: today's confidential tokens do **basic payments** with very little composability inside the wrapper — a confidential wrapper doesn't give you atomicity between a payment and a delivery. People are already hacking extensions (like triggering a contract on successful payment), and Alex explicitly wants to see an escrow system built this way. Just don't expect the primitive to hand it to you.
-
-## C-Addresses, Passkeys, and Key Derivation
-
-Can you use confidential tokens from a smart wallet — passkeys, C-addresses? Yes; Alex has already seen a passkey demo inside a confidential-token-capable wallet. Jay's explanation of why it works: **authentication and token holding are decoupled**. The smart wallet is an authentication mechanism; the account holder is just a regular token holder underneath. Encryption keys are derived from your account's secret — secret key, then spending key, then viewing key, and so on.
-
-Registration was the follow-up: to participate you **register** with a specific token contract — the key derivation commits to that contract, involves a proof, and stores your public spending and viewing keys along with your chosen `auditor_id`. (The auditor's own keys live in a separate registry contract — you pick an auditor at registration, you don't provide its key.) Per Jay, both sender and recipient need to be registered; you can't fire tokens at an address that has never generated its keys. Alex noted the registration step is the deliberate price of a design ask — log in with your existing address and derive everything from it, instead of manually managing separate view and spending keys like the original implementation did.
-
-Then the warning of the week, from Alex: **your key derivation must be deterministic and must match the OpenZeppelin SDK's canonical derivation**. Alex vibe-coded a wallet that derived keys differently than the demo does — it could _deposit_ funds but never spend or withdraw them. That's an accidental honeypot, built in good faith, by AI. It's funny until it's a lot of money. The system deliberately pushes work client-side for privacy, so the cryptography there actually matters; OpenZeppelin is writing an SDK spec to make expectations explicit. Until then, follow the SDK and don't let a hallucination invent your derivation path.
-
-## Wallet Hygiene: Retention Windows and Replay
-
-Jay's practical corollary for wallet builders: receiving requires **no action from the receiver** — incoming amounts accumulate homomorphically into your receivable balance as encrypted events, and your wallet learns what you hold by replaying those events, decrypting, and storing the openings. Stellar RPC's default retention is **seven days**, and that number is load-bearing: your commitment stays on-chain forever, but if your wallet loses its local state and the events have aged out of everything you can reach, you can _see_ that your funds exist without being able to reconstruct the opening that spends them. OpenZeppelin's spec is blunt about this — recovery from seed requires a durable event archive, and they publish an indexer specification for exactly that — so wire up infrastructure with the retention you actually need and refresh periodically. Spending is self-healing — every spend forces you to open your balance and generate a proof — so it's the long gaps _after_ your last spend you have to sweep for.
-
-## Timing Leaks, Scale, and the Road to Mainnet
-
-A sharp one from chat: deposits and withdrawals into the wrapper are public, so can't you correlate them? Yes — Alex didn't dodge it; in a small pool with few participants, timing analysis gets easier. These systems **benefit from scale**: more parties, purposes, and denominations all make correlation harder — an argument for shared deployments serving many customers under the same jurisdictional requirements, not one pool per app.
-
-On observability: the OpenZeppelin demo ships an auditor interface showing all transactions and amounts (deliberately open there; keep it behind custody in real life), but scoped audit requests, monitoring, and selective-disclosure tooling — say, sharing your confidential history with a service so you can do your taxes — are wide-open design space. Nobody is building that platform for you. Hint.
-
-And the shortest question got the most concrete answer: **is it coming to mainnet?** The contracts are live on testnet now — Alex has vibe-coded basic wallets and a private payroll app against them in about twenty minutes. Audits were days from starting at the time of the call; after remediation comes a stable release. The proving stack is **Noir**, verified on-chain by an **UltraHonk verifier** that originated with a community member and is maintained by Nethermind. Alex's main ask: OpenZeppelin is a _tooling_ provider, not an operator. Pick a jurisdiction and a use case and go **be the operator** — sanction lists, allow/deny lists, compliance hooks — and show everyone what best practice looks like.
-
-## Bonus Round: Confidential Agentic Payments
-
-Someone asked about AI agents, so Jay closed with a design sketch. Stellar already has **x402** and machine-payment implementations, and confidential tokens can absolutely make agentic payments private — but not by naive plugging-in. Agent payments are fast, tiny, and many-to-many; you can't settle every one on-chain with five-second finality plus client-side proving. The plausible shape is **channel-based**: accumulate payments off-chain, then settle batches across multiple agents at once, with a registry of who settled what and a dispute period. Jay called it "some engineering to be done" and left it to the ecosystem. I'll repeat what I said live: builders will ship exactly this at the next hackathon, and it will probably win.
-
-## Closing
-
-Alex's parting note was the right one: this isn't an incremental ease-of-use feature. It's the chance to stop choosing between traditional finance (private but closed) and blockchains (open but exposed) — ideally ending as a plain checkbox in your wallet that says _make this transaction private_, done compliantly, from mainnet day one. Drop further questions in the developer chat on the Stellar Developers Discord — there's enough unanswered material for a sequel if demand holds. Thanks to Alex and Jay, and I'll see every single one of you next week.
diff --git a/meetings/2026-08-13.mdx b/meetings/2026-08-13.mdx
deleted file mode 100644
index af9a65396..000000000
--- a/meetings/2026-08-13.mdx
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: "2026-08-13"
-authors: kaankacar
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="SesCqhylBYw" />
-
-## A Short One, For a Good Reason
-
-This week's meeting was a short one, because it had exactly one job: announcing the **12 winners across 6 tracks** from last week's **Stellar Builder Summit in São Paulo**. I was on the ground with the builders all week, so this was less news roundup, more handing out trophies. My colleague **Teague Kaylor** from SDF's marketing team — focused on developer marketing, which means most of the developer events and programs you see from us have Teague's fingerprints on them — joined to set the scene before the announcements.
-
-## What the Builder Summit Is
-
-Builder Summits started as a pilot last year at Consensus Toronto: a long-form developer event that brings the community together over an extended stretch to jam on projects, meet new teams, and get properly connected to the ecosystem — instead of the usual 48-hour hackathon sprint. Toronto went well, so this year the plan is to run them in the markets the foundation is launching into. São Paulo was the first.
-
-The final numbers: around **190 developers** from around the world, coding for **eight days straight**, with workshops and sessions through the week and community days over the weekend. The event was produced with **NearX** — Stellar's partner in Brazil — and our other partner teams on the ground, and the same week São Paulo also hosted **Stellar House**, a one-day gathering on tokenization, stablecoin rails, and cross-border settlement.
-
-Attached to the summit was a bounty program — Teague described it as a mix of an RFP track and a hackathon — pointed squarely at what we want to see built on the network: privacy, anchors and ramps, local yield, and agentic payments and tooling. More Builder Summits are coming later this year, so watch the **@BuildOnStellar** handle on X for announcements.
-
-## The Winners: 12 Across 6 Tracks
-
-The format: for each track, second place first, then the winner. One housekeeping note before the list. I read these names off the results live and dropped the repo links into the YouTube stream chat as I went (sorry, Twitter viewers — we still haven't figured out posting links there). The canonical list, with correct spellings and repo links, is going out via @BuildOnStellar and our summit partners, so trust that over my pronunciation. Where the auto-captions and I couldn't agree on a name, I'm describing the project rather than guessing.
-
-### Privacy: Confidential Tokens & Private Payment Wallets
-
-Second place went to a **Confidential Token SDK** — a TypeScript client for OpenZeppelin's confidential tokens, with a verifiable replay archive. If you read the July 2 note on the confidential-token developer preview, this is exactly the tooling layer that preview was begging for. I talked with this builder in São Paulo, and their read on our confidentiality layers was genuinely insightful — the placement is well earned.
-
-The winner: a **privacy wallet** — a passkey-based smart wallet with confidential transfers and a shielded pool whose idle liquidity earns yield. Keep this builder in mind; they show up again below.
-
-### Enterprise Compliance & RWA
-
-Second place: **Green Road** by **Trustless Work** — a confidential milestone escrow that releases a private allowance without revealing the amount. We all know and love Trustless Work and their escrow infrastructure, and this is a natural extension of it into the confidential era.
-
-The winner: **QuietBook** — confidential book-building for tokenized RWAs. Sealed bids, a provable winner, atomic settlement. Need I say more? I don't think so. It came from a Turkish builder the community knows as Captain — we all met Captain in São Paulo, and the stream chat's verdict ("Captain is the goat") stands.
-
-### Anchors & Ramps: Regional Kits
-
-Second place, Trustless Work again: a **LatAm ramp kit** — a drop-in SDK and React component kit that adds fiat ramps to any LatAm app. Two placements in a single summit is a statement.
-
-The winner: a **Brazil regional kit** — a PIX on- and off-ramp for Brazil with live quotes from competing anchors. It's an aggregator; we all need it, we all love it. The team behind it we've known since our hackathon in Mexico — long-term builders in this ecosystem, still shipping.
-
-### Anchors & Ramps: Emerging-Market Yield
-
-Second place went to a project that parks idle receivables in Brazilian treasuries while measuring the currency risk. The captions and I jointly butchered the team's name on stream — apologies again; the official winners list will do it justice.
-
-The winner, from a Brazilian DeFi team: **BRL that earns Brazilian treasury yield right up to the second a PIX payment fires**. Which, as I said on the call, is pretty cool.
-
-### Agentic Payments
-
-Second place: a discovery layer that lets AI agents find what to pay for on Stellar. Every agent-payment stack eventually hits the "pay for _what_, exactly?" question, so yes — we all need this one too.
-
-The winner: **StellarPay** — one middleware for every machine payment protocol on Stellar. x402, MPP Charge, MPP Channel — all of it behind a single interface. And yes: same builder as the privacy wallet above. Two tracks, two first places, one summit.
-
-### CLI Plugins & Dev Tooling
-
-Second place: a CLI plugin that lets an AI agent safely call a Soroban contract, gated by an on-chain policy. If you've ever wired an agent up to a Soroban contract, believe you me, you might just need this.
-
-The winner: **Stellar Memory** — a persistent memory layer that links a Soroban repo to what's actually live on-chain. I love a memory layer as much as the next guy, and I'm glad the track went to a project that closes the gap between your codebase and the deployed reality.
-
-## Closing
-
-Close to 200 builders, building for almost a week straight — thank you for showing up. Thanks as well to the judging bench (I was on it, alongside colleagues from SDF and friends from across the ecosystem) and to NearX and the partner teams who produced the event with us. My last words on the call stand: I hope to see every one of these projects evolve into something bigger, and I hope you get to brag one day about how your journey started at a Builder Summit in São Paulo. More of these are coming later this year. See you next week.
diff --git a/meetings/2026-08-20.mdx b/meetings/2026-08-20.mdx
deleted file mode 100644
index e289cb68a..000000000
--- a/meetings/2026-08-20.mdx
+++ /dev/null
@@ -1,82 +0,0 @@
----
-title: "2026-08-20"
-authors: kaankacar
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="npqRSfq-rWA" />
-
-## Why Wallets, Why Now
-
-This week was a coding session rather than a project spotlight: **six wallet infrastructures, one demo app**, and a running list of gotchas for each. The topic came straight out of the Builder Summit in Brazil, where I spent a week with the local builders and our partners at **NearX**. Watching what people shipped reminded me of a pattern I had been noticing in Turkey and had assumed was a local quirk. It is not. Worldwide, when builders ship something on Stellar — at a hackathon or in an SCF application — they reach for the **Stellar Wallets Kit** almost by reflex, because a modal full of extension wallets feels like building on EVM.
-
-The kit is great and I am not here to talk you out of it. But a site that demands "connect your wallet" the second you land on it is a bit of a red flag, and extension wallets are the default in Web3 only because nobody questioned it. I would love to see more experiments with **C-addresses**, smart accounts, and passkeys, and above all with **social login** — connect with Google or an email code and you are in. So I built a small gallery app that wires the same flow (show the wallet anatomy, fund with Friendbot, swap XLM to test USDC through Soroswap's router contracts, sign a payment) through each of six kits, and walked through what each one does under the hood. The code is public: [kaankacar/stellar-wallet-gallery](https://github.com/kaankacar/stellar-wallet-gallery). If you want the whole thing as a single skill, tell me — **skills.stellar.org** was at **29 community skills** alongside the official ones as of this call, and I am happy to add another.
-
-One housekeeping item before the code: **testnet upgrades to Protocol 28 next week**, around this same time on Thursday. The chain keeps running, but do not pin your project config to Protocol 27, and maybe take a 30-minute break instead of testing right through the upgrade window. Better safe than sorry.
-
-## Stellar Wallets Kit: The One You Already Use
-
-Nothing new here, so I kept it short. The kit bundles the extension and hardware wallets — Freighter, Albedo, xBull, LOBSTR, Hana, Rabet, Ledger, Hot Wallet, Bitget, and friends — behind one modal, needs no API keys, and only ever talks to classic **G-accounts**. The flow is the one you know: the dApp loads the source account's sequence number from Horizon, builds a classic transaction, hands the XDR to the wallet, the wallet asks you to approve, the signed XDR comes back, and the app submits it to Horizon or RPC.
-
-Two gotchas worth saying out loud:
-
-- **Set the network explicitly.** If you leave out the `network: testnet` line when you initialize the kit, your Freighter or Hana wallet connects on **mainnet** by default. Check that line before you test, whether you wrote the code yourself or an agent wrote it for you.
-- **Use v2, and check that you actually are.** For the newer builders: there is a v1 and a v2, and yes, we know the payments example in our own documentation still uses v1. We are fixing that; you should be on v2 today.
-
-The default modules work with zero config. Only **Trezor** and **WalletConnect** need app credentials, so either add those or drop the two modules and ship with the defaults.
-
-## Blux: Pretty, Customizable, and a Little Rough
-
-**Blux** has a special place in my heart — it is a Turkish project, SCF-funded about a year ago, and it is a connect kit that onboards users through extension wallets _and_ email, phone, Google, or passkeys. The dashboard at dashboard.blux.cc is genuinely lovely: accent colors, backgrounds, fonts, borders, your own logo, and you can trim the login options down to just Google or just email if that is all your app wants. I live-demoed my own app ID and secret on stream, so that got rotated right after the call. Learn from me.
-
-Under the hood Blux still creates a **classic G-account** with an Ed25519 key pair. When you log in with email, SMS, or Google, **Blux manages that key**. That is the trade-off every social-login product makes, and Matias in chat asked the fair question: what happens if Blux disappears tomorrow and they are the custodian? I did not have an answer, and I would love to have the Blux team on a future call to give one.
-
-The gotchas I hit:
-
-- **Social login is off by default.** Email, SMS, Google, and passkey have to be enabled explicitly in the config, or you have just installed another wallet kit.
-- **The login modal has no close button**, and the **signing overlay locks page scroll**, so you cannot dismiss it or move around the app without a refresh.
-- **Soroban transactions through the overlay resolved maybe half the time** in my testing. I have not dug into why.
-- Blux is **React only**, the provider must not be mounted without a real app ID (the ID is validated server-side on every auth call), avoid React strict mode, and the npm README is stale.
-
-The workaround that made the demo work: set `showWalletUIs` to false and let the swap go through silently. One XLM in, 2.48 test USDC out, no overlay. Matias summarized the whole section better than I did: pretty colors and customization are not a trade-off for bad UX. Agreed, and the colors are still pretty. Blux team, if you are reading this, consider it an audit with love.
-
-## Privy: Social Login Done Properly, With One Caveat
-
-You know **Privy** from EVM. What fewer people know is that it supports Stellar: embedded wallets powering **120 million-plus accounts**, with email and social login out of the box. Stellar is a **Tier 2 chain** in Privy's model. Tier 1 is raw cryptographic signing (Bitcoin and the other Ed25519 chains), Tier 2 adds wallet abstractions, and Tier 3 is full end-to-end client support (Ethereum, Solana). Tier 2 is exactly what we need: Privy signs, but **your app builds the transaction**.
-
-The flow is elegant. The login opens Privy's modal, an email code creates a wallet inside Privy's key infrastructure, your app builds the XDR and sends only the **raw transaction hash** to Privy, Privy signs it and returns a hex signature, the dApp converts it to base64, attaches it, and the Stellar SDK verifies it client-side before accepting it. The key never touches the browser's JavaScript, the app only ever sees the address and the signature, and by the time Horizon or RPC sees the envelope it is a perfectly ordinary classic payment. The key does live in Privy's infra, but it is **exportable by the user** at any time, which is a working mitigation.
-
-Gotchas:
-
-- If you come from Privy on EVM or Solana you are used to the `createOnLogin` config. On Stellar (and every other Tier 2 chain) you call **`createWallet` with `chainType: "stellar"`** instead. Get that right and you are good.
-- You still need an app ID from dashboard.privy.io or nothing works.
-- Second-hand, unverified, filed under gossip: two builders told me Privy gets slow once you are scaling to tens of thousands of users. I have not seen it myself. If you have that problem, congratulations on the problem, and go experiment with the other kits.
-
-## Para: MPC, Finally
-
-**Para** is the newest of the four I demoed on Stellar, and the reason I love it is one acronym: **MPC**, multi-party computation. With Blux and Privy your social-login key lives in their infrastructure. With Para the key is born as **two shares** — one in your session, one on Para's network — and the full key never exists anywhere. Signing is a ceremony: the app sends the transaction to Para's MPC network, the two shares compute a signature together without either side ever seeing the whole key, and the fully signed envelope comes back for the dApp to submit. In a world where every conversation is ZK and fully homomorphic encryption, seeing good old MPC in production is refreshing. It was the first cryptographic idea I understood as a new Web3 developer, so I am biased.
-
-Setup: create a project at developer.getpara.com, copy the beta API key, done. The **free plan covers 1,200 monthly active users** and 30 REST requests per minute, which is more than enough to evaluate it. From the user's side it looks like Privy — phone or email, no seed phrase, no overlay on the swap — and the `createWallet` call is the same shape.
-
-Gotchas, in order of severity:
-
-- Same mainnet trap as the wallets kit: if you do not pass the **network passphrase** into the Para signer hook, it defaults to the **public network**.
-- Para's SDK currently pins **stellar-sdk 14.6.1** while my project is on 16. As long as only XDR strings cross the boundary it does not matter, but it could.
-- The SDK **lazily imports ethers** even when you only use Stellar. You never touch EVM, you still download it.
-- I could not find an export option for your share of the key. In principle you should be able to take your share and do the computation locally; check developer.getpara.com for the current answer.
-
-Matias made the point that a wallet relying on a backend is a bad wallet, and it is the honest trade-off of this whole meeting. In Web3 you can own everything — the seed phrase, the key, the money — but the onboarding will never feel like signing in with Google. Every kit above picks a different spot on that line. Pick yours knowingly.
-
-## One Thing Every Social-Login Kit Shares
-
-When you connect Freighter, you bring an account that already exists. When Blux, Privy, or Para create a G-account from scratch for a Google or email login, that account is **unfunded**, even on testnet. Hit Friendbot before you do anything else, or you will drown in errors that look unrelated. Most of you know this; with over 170 viewers on the call and a lot of new Stellar builders in the ecosystem, it was worth saying.
-
-## Passkey Kit vs. Smart Account Kit
-
-I ran out of time for a deep dive, so here is the differential. Both give you **C-addresses** (smart accounts) instead of G-accounts. **Passkey Kit** is ours and it is hackable: build any kind of transaction, run your own relayer, customize everything. **Smart Account Kit** sits on OpenZeppelin's audited smart-account contracts and gives you multi-signer auth, policies, and the rest out of the box, maintained upstream. More control, Passkey Kit; more batteries included, Smart Account Kit. If you want a dedicated workshop on either, ask in the Stellar Developers Discord.
-
-## Closing
-
-Adrian in chat brought up **Cavos**, another embedded-wallet layer with Stellar support that I had not seen yet. We will give it a proper look in a future meeting. We ended around 200 viewers, I promised to drop the gallery repo in the comments, and I meant it when I said I want more of these strictly-coding sessions — comparing infrastructures side by side instead of only showcasing projects. If there is a comparison you want next, say so. See you next week.
diff --git a/meetings/2026-08-27.mdx b/meetings/2026-08-27.mdx
deleted file mode 100644
index d7173ca69..000000000
--- a/meetings/2026-08-27.mdx
+++ /dev/null
@@ -1,73 +0,0 @@
----
-title: "2026-08-27"
-authors: kaankacar
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="5dVgKuapDPg" />
-
-## Housekeeping: Protocol 28 and Another Privacy Preview
-
-Two links before the agenda. First: if you haven't upgraded yet, do it now. Testnet is on **Adapter (Protocol 28)** as of this week — the testnet vote landed the same day as this call — and mainnet follows in a few weeks. Check the [upgrade guide](https://stellar.org/blog/developers/adapter-protocol-28-upgrade-guide) for what changed: faster consensus (CAP-83), externally managed contract executables (CAP-85), and sparse-map host functions for data migrations (CAP-86).
-
-Second: **Stellar Private Payments** is officially in [developer preview](https://stellar.org/blog/developers/developer-preview-stellar-private-payments). Deposit into a shared pool, transact inside it, withdraw — without publicly linking who paid whom. Fitting, because this week was a privacy call too.
-
-## This Week's Guest: Moonlight
-
-**Moonlight Protocol** (moonlightprotocol.io) is a privacy layer built on Stellar by **The Aha Company**. Their one-liner: it transforms each account into a constellation of unlinkable UTXOs, shielding balances and payments from public traceability. I'll admit a bias — this might be my favorite privacy solution on Stellar — and it's probably the single most requested topic from you all, so I was excited to have **Chad** and **Gorka** on. We waited for the room to fill (50+ at the start, close to 200 by the end) and handed Chad the stage.
-
-Introductions came late, because I assumed everyone already knows Chad. For the record: **Chad Ostrowski** is founder and now CTO of The Aha Company, which arrived about a year before Stellar had smart contracts and built a lot of the core developer tooling — **Scaffold Stellar** and **Stellar Registry** among them — plus stablecoin work for large global banks and a tokenized money market fund. A new passkey wallet is in the works too; more on that at Meridian. **Gorka**, a self-described digital nomad, has been the lead engineer on Moonlight for the past six months — the person actually in the guts of the protocol, and the one who made the UIs, stacks, and layers compose into something you can click.
-
-## Chad's Tour: Compliant Privacy Without ZK
-
-Chad's framing: Moonlight is the privacy layer that makes public blockchains usable for **regulated finance**. It came directly from needs their banking partners kept raising. Banks want public blockchains — faster settlement, lower costs, new revenue models — but public is a deal breaker. Without privacy they can't legally or competitively make the switch, so today they're forced to choose between privacy and compliance. He showed a chart of privacy solutions getting blocked as regulation tightened: in blockchain, more regulation has meant less privacy, and MiCA makes it harder still. The problem is structural — pay with your public key and the cashier sees your balance _and_ your full history — and regulatory needs differ per region. Privacy isn't dead. We need **compliant** privacy.
-
-One thing Chad made explicit when a viewer asked: there is **no zero-knowledge cryptography in Moonlight today**. Turns out you don't need it to build a privacy solution. ZK could add superpowers later (larger bundle sizes, for one), but there's no immediate plan or need. If you've been following the [confidential tokens](/meetings/2026/08/06) and ZK conversations on this stream, note the contrast: this is a different design axis entirely.
-
-The four building blocks:
-
-### UTXOs (Pronounced "Ucho")
-
-Instead of accounts and balances, Moonlight uses the **unspent transaction output** model you know from Bitcoin and Cardano. Each payment consumes multiple UTXO inputs and creates multiple outputs, breaking the value trail. Entropy is tunable: fewer UTXOs for cheaper transactions, more for more privacy. Providers can bundle one-to-many or many-to-many transfers — Alice, Bob, Calvin, and David all tell their bank "send this," the bank combines everything into one on-chain bundle and can mix in decoy UTXOs on top. Tailored bundling strategies also unlock new service models: mixers, paymasters, aggregators. Also, Gorka taught Chad to pronounce it "ucho," a viewer asked whether that's a bad word somewhere, Gorka swore it's just a T and an X bundled together, and I'm adopting it.
-
-### Standardized Derivation
-
-One master secret. Every Moonlight address derives from the same seed, which simplifies backups, keeps self-custody intact, and lets you migrate between wallets or providers with no loss of access and an unbroken privacy posture. No derivation data touches the chain, so observers can't cluster addresses back to the master key. And while Stellar is the system of record, the incoming keypair could come from Ethereum, Cardano, Solana, or elsewhere.
-
-### Privacy Providers and Councils
-
-The key concept. Every user onboards with a **privacy provider** — think bank, though it could be another financial institution or a wallet. The insight: users already trust these institutions with their private data, so Moonlight harnesses that model instead of fighting it. Providers run off-chain infrastructure (a Moonlight API service, KYC/AML) and on-chain infrastructure (an operation-executor wallet registered with a council contract). From the outside the UTXO graph is unintelligible; the provider has enough to see _its own users_ and answer regulator audit requests. Providers also do the bundling.
-
-Providers self-govern through **councils**, grouped by regulatory region. Chad's running example: two large US banks deploy a council contract; a third asks to join, and the members use their multisig to add its verified address. Users keep sovereignty — onboard with two providers in the same council and you can route one transaction through each, with your wallet living separately from both. Cross-border payments need a provider that operates, and answers to regulators, in both regions.
-
-### Privacy Channels
-
-One smart contract per channel, **one channel per asset**. The council decides which assets to support and deploys a channel for each — USDC seems likely, a tokenized money market fund maybe, XLM who knows. Channels can carry extensions to bridge liquidity between channels and regions or connect directly to other on-chain applications.
-
-## The Testnet Dashboard
-
-It's live on testnet. Chad pulled up the network dashboard (linked from moonlightprotocol.io): 24 councils, including a seeded "US Banks" example with three providers, each with its public key and wallet-connect URL — the two things the browser wallet asks for at setup. We clicked into a bundled send from a seeded "EU bank" provider and looked at what an outsider sees: gobbledygook. A lot of uchos. The provider's own dashboard would join those outputs to its KYC records; logged out, you get nothing. One gotcha from chat: the council testnet UI currently talks to **Freighter** directly, not through Stellar Wallets Kit.
-
-I said on the call that the council concept makes enormous sense to me — entities choosing which channels and assets to offer, per region, is how compliance actually works — and a few months after mainnet I'd love to see a long list of providers plugging institutions into this layer.
-
-## Gorka's Demo: Alice, Bob, and 42 XLM
-
-Two wallets side by side. Demo one, the low-level flow: Bob is the only one who can derive UTXOs from his secret key, so he generates a payment request — a very long string — and sends it to Alice. Alice has no channel balance yet, so she **deposits 100 XLM** into the privacy channel, then fulfills Bob's request using only the information in his message. Bob refreshes: balance updated. Bob then **withdraws** back to his public account to show the round trip. A viewer asked whether the council validates these transactions — no, they're regular Stellar transactions; the council only deploys channels and governs who may interact with them.
-
-Demo two is why this can actually ship to humans. Passing long strings around is "somewhat not the best user experience," as Gorka put it. Since providers hold KYC data on their users, they can abstract that away: Alice logs into a provider UI and sends **42 XLM to "Bob"** by name. The provider holds the amount for Bob until he claims it; his self-derived UTXOs stay out of the provider's reach the whole time, and if he's uneasy about anything held on his behalf he can sweep it into his own UTXOs immediately. Sovereignty preserved, friction removed.
-
-## Fifo Drops In
-
-**Fifo** — Brazil-based, roughly six years in the Stellar ecosystem starting at Cheesecake Labs, about a year and a half at Aha — had been live-commenting the whole stream, so we pulled him on stage (video slightly squashed). Moonlight started as his garage project a couple of years ago; the original contracts were his alone before Chad and Gorka came in to find the problems and evolve the protocol. The origin story matches Chad's: banking institutions saying "blockchain is great, but how do I onboard users without exposing my whole operation?" It's still a moving target — every new business conversation surfaces another use case. Fifo also works with SDF on a program helping new partners past the common friction points of building on Stellar, so you may have met him already.
-
-## Q&A and How to Try It
-
-A viewer asked for a flow diagram from sender to pool. There is one — it lives in the documentation produced during the recent **Runtime Verification** audit of the core contracts, whose [public report](https://runtimeverification.com/public-report/moonlight-audit) is up. I offered Gorka a two-hour session walking through every diagram; the silence told me to schedule that another time. Spam us on Discord if you want it to happen.
-
-Elliot from our DevRel team had already spun up a council and a provider of his own and asked how to deposit. The order: deploy the **council** (the administering group), deploy a **channel** for one asset (think private pool), then deposit the first liquidity into it. You'll need the **browser wallet** — build it from source and load it in dev mode in Chrome or Brave — or, being Elliot, call the contract directly. Everything is open source under github.com/Moonlight-Protocol: the browser wallet, the provider stack, and the UIs from the demo. The team's explicit request is to go break it: create providers and councils, send private transactions, file what you find. There's no bug bounty yet, just a very big thank-you — and please, no AI-generated low-severity reports; we've had that problem before.
-
-## Closing
-
-Thanks to Chad, Gorka, and last-minute Fifo. Follow **@theahaco** on X — with 3,500 monthly active developers in this ecosystem, not knowing The Aha Company is on you — and go find bugs in Moonlight. See you next week.
diff --git a/meetings/2026-09-03.mdx b/meetings/2026-09-03.mdx
deleted file mode 100644
index 0debcb13a..000000000
--- a/meetings/2026-09-03.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-title: "2026-09-03"
-authors: kaankacar
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="fzUx9zoE0JU" />
-
-## Dress Code: Confidential
-
-I showed up in a black jacket this week, like a serious businessman here to discuss confidential tokens and privacy. Not because I own no other jackets. The agenda: instead of me talking for an hour, we were going to _play a game_ built by SDF's new **Frontier Lab** team, with a stack of colleagues and ecosystem friends on the call. One piece of housekeeping first, because it was too big to skip: **USDT0 is live on Stellar**. The infrastructure that carries Tether's USDT to every network launched on Stellar the day before the stream — a real milestone for a chain built for payments and cross-border finance. But this meeting was about confidentiality, and about how we've only scratched the surface of confidential tokens so far. The August 6 Q&A covered the design philosophy; this week was the hands-on version.
-
-The cast: **Bri**, senior developer advocate on the Frontier Lab team, who built the game. Playing: **Tyler**, **Elliot**, **Raph** from Lumen Loop, **Boxy** from Stellar Light, and **Patrick**, introduced by Bri as "some random guy I picked up off the street." Several people arrived in costume. Patrick's suit jacket, Halloween accessories, and riding shades were, in his words, an attempt to be confidential and undercover. He later admitted the jacket was only on because it was wrinkled and he needed it Saturday. Sweating the wrinkles out, live.
-
-## Who Ate Gerald?
-
-Gerald was a villager. Emphasis on _was_. One morning the village wakes up, Gerald has been eaten, and that's how everyone learns there's a **werebear** living among them. **Who Ate Gerald?** is an eight-player social deduction game in the Werewolf/Mafia family: everyone gets a secret role, one player is the werebear, and the village has to banish the werebear before it eats everyone.
-
-Bri built it because she wanted a more fun way than a blog post to demonstrate the confidential token transfer flow, and to learn it herself by building with it. The caveat, stated up front: confidential tokens are still a **developer preview**, on testnet only, not ready for production. **OpenZeppelin** built the Soroban contract suite and the **Noir** circuits that make confidential SEP-41 tokens possible; **Nethermind** built the **UltraHonk verifier** that checks the proofs on-chain. The privacy section of the developer docs has the details, and I was pasting that link into chat all stream.
-
-A day in the village:
-
-- **Shop.** Log in with Freighter set to testnet, pick a character, and visit two of the four shops: blacksmith, general store, butcher, chapel. Items protect you, expose other players, or just cause chaos. The chapel sells Gerald's fingers; when the eight fingers run out, his two thumbs appear, then toes. Poor Gerald.
-- **Ask Maude.** Every purchase is a **real confidential token transfer**. The whole village can see which shop you interacted with, but nobody can see what you bought or how much you spent — except the **auditor**. In the game that's **Maude McLedger**, the village fortune teller, who holds the auditor key and can read the amounts. Each player gets one private question per day: "what did Trixie buy at the blacksmith?" or "did anyone buy something from the chapel?"
-- **Accuse and vote.** Maude's answers become clues, bluffs, and misdirection. Maybe Raph bought a barrel of beer because it protects you from the werebear at night. Or maybe he bought it precisely so you'd think he isn't the werebear. The most-voted player is banished; an innocent villager loses their vote but keeps talking. Then night falls, the werebear eats someone, and the morning starts over with fewer villagers.
-
-You receive **25 XLM** of pocket money per day, so blowing it all on day one means no fancy items later. Bri also quietly raised the discussion timer from two minutes to ten, in case things got heated. They did.
-
-## Where the Value Actually Lives
-
-Before the demo, Bri gave the clearest explanation of confidential tokens I've heard so far, built on two mental models. The first: **where the value sits**.
-
-1. **Regular XLM in your wallet.** Public, boring, visible on any explorer. Bri's testnet account was sitting on almost 18,000 test XLM.
-2. **The shared pool.** The confidential token contract is a wrapper around a regular asset — XLM in the game, but any SEP-41 asset works. Every deposit puts XLM into one big pool held by the contract, and it stays there until someone withdraws. The pool's total is completely public: around **34,000 XLM** on stellar.expert during the call. What is _not_ public is how that total is split: 500 of it is Bri's, 100 is Boxy's, 10 belongs to the butcher, and you can't tell any of that from the chain.
-3. **Confidential claims.** Nobody inside the system carries their own pile of XLM; they carry claims on the pool. For every registered participant the contract keeps an entry with their public keys, a pending balance (OpenZeppelin's docs call it the receiving balance), a spendable balance, and which auditor they chose. When the game says Bri has 500 XLM, she really has a confidential claim on 500 XLM in the pool, and the number itself is hidden inside a **Pedersen commitment**: anyone can see the commitment on-chain, nobody can read the balance out of it. (Bri: "I actually don't really know what that is very much, so that's all I'm going to say about it." Honest, and correct.)
-
-Hiding the number creates the obvious problem: what stops you from spending money you don't have? **Zero-knowledge proofs.** A proof says "the hidden math checks out — I had enough, I didn't create money from nowhere, and all the balances still add up" without revealing any numbers. Commitments hide the numbers; proofs make sure nobody cheats.
-
-## The Six Steps of a Confidential Payment
-
-The second mental model is the lifecycle, which the game displays as a checklist that lights up as you play:
-
-1. **Register** — each address registers once per wrapper contract. Bri's was already green because she has played the game, in her words, thirty million times.
-2. **Deposit** — public XLM goes into the pool.
-3. **Merge** — the sender moves their pending balance into their spendable balance.
-4. **Transfer** — the sender confidentially moves part of their spendable balance into the receiver's pending balance.
-5. **Merge** — the receiver moves the incoming claim from pending to spendable.
-6. **Withdraw** — the receiver exchanges part of their claim for regular XLM back in their wallet.
-
-The first four are the sender's job, the last two the receiver's. Register, transfer, and withdraw are the steps that carry ZK proofs. And the detail that explains the whole game: **deposit and withdraw are the only two points where real XLM and confidential claims trade places.** Everything in between is claims changing hands inside the pool. Buy a soup bone from the butcher and the contract's public XLM balance does not move; you just privately changed who owns some of what's already in there. Boundaries public, middle private. You could watch it live in the game's on-chain activity feed: every daily "25 XLM" showed up as a public deposit plus a merge, and every purchase as a transfer with the amount marked confidential. Open one on stellar.expert and there is simply nothing to see.
-
-## Maude, the Auditor
-
-The auditor is the part developers trip over most, so: Maude holds a secret key whose public half sits in an **on-chain auditor registry**. When you register with the confidential token contract, you pick which registry entry audits you; this game's contract offers one option, so Maude audits everyone. In a real application that slot is a regulator, a compliance team, or an independent auditor — someone who legitimately needs the amounts without making them public. This matches what we worked out in the August 6 note: the auditor is chosen per account at registration, out of a registry that can hold many keys.
-
-She is also strict. Ask something too broad or too specific and she declines. Raph burned his first question asking who the werebear was. When I tried to social-engineer her, she told me, more or less, to shine a mirror on myself. Chat's verdict: "this is what regulation has come to — psychics checking our transactions."
-
-## How the Game Went
-
-Bri ran a watcher screen rather than playing, so she could narrate without leaking her own role. The roster: Trixie Diamond the lamp lighter, Lawrence McDig Jones the gravedigger, a drunk named Not The Werebear, a midwife named Definitely Not Kaan, Boxy the rat catcher (very creative), Badger McPatrick the beekeeper, Chuck Roast the poacher, and a baker whose name I won't attempt to spell. Patrick turned out to be playing two characters, which raised the odds considerably.
-
-Day one: everyone shopped (Elliot was broke within minutes), Maude answered what she felt like answering, and the village banished Lawrence McDig Jones — an innocent villager. Sorry, Lawrence. Trixie Diamond was taken in the night, except, as Boxy clarified while nobody believed him, that was a **soup bone**: an item that redirects an attack onto someone else. Day two: the soup bone was suddenly the most popular item in town, and the village voted out Badger McPatrick, who was indeed the werebear. Two rounds. "This was scripted," Bri insisted. Last time we played I was the werebear, kept buying the same protective item every round, Maude told everyone about my **tooth sharpener**, and that game lasted five minutes.
-
-The strategy debrief was genuinely useful for understanding the design: protective items early look innocent; the tooth sharpener bypasses everyone's protections and is a near-certain werebear tell; **pizza party** means nobody gets banished that day, priced at 43 XLM so you can't spam it; the **horseshoe nail** persists all game and breaks banishment ties in your favor. And yes, you can soup-bone the werebear by accident and end the game on the spot. There is a custom animation for that. There is also one for the werebear winning, in a tutu, with champagne.
-
-Bri kept the repo private until the stream ended so none of us could work out how to cheat with our agents. It's public now: play at **gerald.stellar.buzz** (Freighter on testnet), read the code at **github.com/stellar-experimental/who-ate-gerald**, and treat it as a real reference application for confidential token transfers. Bri also floated that she and Teague might build a "Stellar arcade." Official announcement pending, allegedly.
-
-## Closing
-
-Around 300 of you watched a developer meeting conducted largely in costume, and I'm obsessed. Thank you to Bri for building the game, to everyone who played, and to the viewers who put up with us. There is a serious side to confidential tokens — go read the docs — but experimenting should be fun, and this was. Next on the privacy track: **Stellar Private Payments** with Nethermind. See you next week.
diff --git a/meetings/2026-09-10.mdx b/meetings/2026-09-10.mdx
deleted file mode 100644
index c324fd71a..000000000
--- a/meetings/2026-09-10.mdx
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: "2026-09-10"
-authors: kaankacar
-tags: [protocol]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="MVWcXyVbhNk" />
-
-This week was planned as a protocol discussion on CAP-87 and CAP-88, with Jay Geng and Garand Tyson from the core team. Jay had audio problems and we could not hear him even after he rejoined, so this recording covers only CAP-88. Jay presented CAP-87 the [next week](./2026-09-17-protocol.mdx).
-
-## CAP-88: Millisecond-Resolution Close Times
-
-Garand presented [CAP-88](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0088.md), which he expects to be a straightforward change.
-
-**The problem**: All ledger close times on Stellar are whole seconds. This has two effects:
-
-- Two ledgers cannot close less than one second apart. Sub-second ledgers are still far away, but the limit is there.
-- The network cannot target a ledger time that is not a whole number of seconds. With 5-second ledgers today, a small step such as 4.5 seconds is not possible.
-
-**The change**: Close times move to millisecond resolution for consensus and validators. The time is the same, it is just not rounded to the second.
-
-**What stays the same**: Everything a transaction sees still uses whole seconds. This includes the Soroban ledger timestamp, claimable balance predicates, time bounds and `minSeqAge`. The existing whole-second `closeTime` in `StellarValue` stays, and the new millisecond value is added next to it. Downstream systems that decode ledger headers must update their XDR definitions for the new union arms, but they can keep using the whole-second value, or pick up the new one. The near-term targets are steps like 5 to 4 or 3.5 seconds, so whole seconds are still fine at the transaction level. If ledger times get much shorter, the team may revisit milliseconds in the transaction interface.
-
-## Questions
-
-- **Milliseconds for random numbers**: Someone in chat suggested that milliseconds in the interface would help pseudo-random number generation. Garand and Dima disagreed. Soroban already has a PRNG on the host, and validators set the timestamp. A Byzantine validator could choose arbitrary millisecond values more easily than whole-second values, which are tied more closely to real-world time.
-- **Why not micro or nanoseconds**: Network latency in a distributed system makes anything below milliseconds useless at the consensus layer. Stellar launched with whole seconds because ledger times were much longer at the time, and clock sync (NTP) and servers have improved a lot since then.
-- **Do validators need synced clocks**: No. The validator that proposes a ledger includes its local timestamp in milliseconds. Clocks can still drift between validators, as they can with whole seconds today. The change improves the resolution, it does not require millisecond-level sync.
-
-Please add your comments to the [CAP-88 discussion thread](https://github.com/orgs/stellar/discussions/1998).
diff --git a/meetings/2026-09-17-protocol.mdx b/meetings/2026-09-17-protocol.mdx
deleted file mode 100644
index 40e534323..000000000
--- a/meetings/2026-09-17-protocol.mdx
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: "2026-09-17 Protocol Discussion"
-authors: kaankacar
-tags: [protocol]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="-JaNSo6jN_U" />
-
-After the [Stellar Private Payments AMA](./2026-09-17.mdx), Jay Geng from the core team presented [CAP-87](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0087.md). This is the CAP that audio problems pushed out of the [previous week's discussion](./2026-09-10.mdx).
-
-## Why Post-Quantum Signatures
-
-The signature schemes that blockchains use today rely on the hardness of factoring and the discrete log problem, including its elliptic curve version. Shor's algorithm solves these problems in polynomial time on a large enough quantum computer. Nobody knows when that day comes, but Stellar wants to be ready.
-
-A few months ago SDF published a three-stage quantum readiness plan for Stellar. CAP-87 is the first stage: add post-quantum signature verification to Soroban as host functions, so smart wallets can adopt a post-quantum scheme on their own. Network-level signatures are not part of this CAP.
-
-## Why ML-DSA
-
-NIST has three post-quantum signature candidates:
-
-- **ML-DSA** (FIPS 204), lattice-based.
-- **SLH-DSA** (SPHINCS+), hash-based. Signatures and keys are roughly an order of magnitude larger, and it is much more expensive to compute.
-- **Falcon**, also lattice-based and more compact, but its standard is not final yet.
-
-ML-DSA is the most mature choice. Large cloud providers support it in their KMS products, Cloudflare supports it, and OpenSSL and Apple's CryptoKit list it. Its signatures are a few kilobytes, which fits a blockchain much better than hash-based schemes. Jay noted that the other two could still come later, because the blockchain world is split on all three.
-
-## What CAP-87 Adds
-
-Three host functions, one per ML-DSA parameter set: `verify_sig_ml_dsa_44`, `verify_sig_ml_dsa_65` and `verify_sig_ml_dsa_87`. They share the same interface: public key, message, signature and an optional context string for domain separation. The context must be shorter than 256 bytes, as the standard requires.
-
-- The numbers 44, 65 and 87 refer to the size of the internal matrix. For ML-DSA-44 it is a 4x4 matrix of polynomials.
-- Key and signature sizes are exact. For ML-DSA-44, the verifying key is 1,312 bytes and the signature is 2,420 bytes. Any other size makes the function fail at once.
-- Each function decodes the key, decodes the signature, then verifies.
-
-### Costs
-
-The CAP adds nine new cost types, three per parameter set:
-
-- **Decode verifying key**: constant cost. This step does more than parse bytes. The public key holds a seed, and the host expands it into the full matrix with SHAKE.
-- **Decode signature**: constant cost.
-- **Verify**: linear in message and context length, because the message is hashed together with the context and the public key. Everything else is constant.
-
-Jay shared early calibration numbers for ML-DSA-44: about 38k CPU instructions to decode the signature, about 850k to decode the verifying key, and about 686k to verify. About half of the work is in decoding.
-
-## Questions
-
-- **What makes it quantum safe**: Lattice signatures rely on different hard problems, Short Integer Solution and Learning With Errors. Both come down to finding short vectors in a lattice, and there is no known efficient attack on them, even with a quantum computer.
-- **Which library**: AWS has a formally verified implementation, but it is low-level C. The team prefers a pure Rust dependency. The two mature Rust options are RustCrypto and libcrux. RustCrypto is the likely choice: its code is simpler and cleaner, it is widely used, and its decode and verify steps are well separated. The interface does not depend on the library, so it can change later.
-- **Passkey smart accounts**: ML-DSA is a new option, not a replacement. Passkeys today use secp256r1, and post-quantum passkeys need support from the platform and wallet side, for example in the WebAuthn layer. Jay warned against adopting it too early: if you give up hardware signing just to get a post-quantum property, that is a step backward. More ecosystem work is needed here.
-
-Please add your comments to the [CAP-87 discussion thread](https://github.com/orgs/stellar/discussions/1915).
diff --git a/meetings/2026-09-17.mdx b/meetings/2026-09-17.mdx
deleted file mode 100644
index 4bcde4b96..000000000
--- a/meetings/2026-09-17.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-title: "2026-09-17"
-authors: kaankacar
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="QO40dHfJO9Y" />
-
-## An AMA for the Newest Kid in Town
-
-This week was a straight-up AMA about **Stellar Private Payments (SPP)**, Nethermind's privacy-pool implementation for Stellar. We played around with Nethermind's demo on a stream a couple of months back, and the August 6 confidential-tokens Q&A kept pointing at SPP as the tool you reach for when you need _counterparty_ privacy rather than hidden amounts. So this time we went to the source. A few days before the stream we asked on X and in the developer Discord for your questions; my job was to read them to **Antonio Larriba** from **Nethermind**, who joined from Europe at 8 p.m. his time and took the whole hour in stride.
-
-Quick introduction, since the Electric Capital developer numbers for Stellar keep climbing and a lot of you are new here: Antonio is a computer scientist with a PhD in cryptography — electronic voting and anonymous identification, specifically — and has been a cryptography engineer at Nethermind for a bit over three years. He has led the Stellar Private Payments work for the whole project. He also blamed _Cryptonomicon_, read as a teenager, for the privacy obsession. There is clearly a story there; I did not ask, since it is private.
-
-The questions came mostly from builders in LATAM and the MENA region, and they were largely conceptual: people understand how SPP differs from confidential tokens, they wanted to know how the design actually holds up.
-
-## What "Compliance" Means Inside a Pool
-
-The first question came from a developer in Turkey who had read both the Nethermind blog post and ours and kept snagging on one sentence they share: _privacy and compliance are not opposing requirements_. Fine — but what does compliance mean concretely? What can a regulator, an issuer, or an auditor actually do with an SPP pool?
-
-Antonio's framing: a fully private pool is easy to build, and history shows what happens next — honest users end up sharing a pool with hacked funds, and everyone's money is tainted by association. Compliance in SPP is the set of rules that keeps bad actors out without making the privacy useless, and it is **part of the protocol**, not an add-on:
-
-- Every interaction is a **zero-knowledge proof** that you own funds in the pool, that they are really part of the pool, and that they have not been spent.
-- On top of that, you prove **membership in a whitelist and non-membership in a blocklist**. These lists are called **association sets**, and the parties maintaining them are **Association Set Providers (ASPs)**.
-- The rules are **configurable per pool**. An ASP could implement a blocklist mirroring a government sanctions list, or a whitelist that is ZK-friendly and never asks for personal information. Or a pool operator can run a pool with **no whitelist and no blocklist at all** — fully private, no admin superpowers, "for the good and the bad," as Antonio put it.
-
-The part I found most important: if a whitelist is KYC-based, you give up some privacy **exactly once, at onboarding**. After that, everything happens inside the proofs. The ASP can accept or block your notes, but it cannot see which notes you own or how you spend them. A chat question later asked whether mentioning KYT (know-your-transaction) means the model is not trustless — the answer is the same: nothing is enforced per transaction today, the whitelist and blocklist operate at the public-key level, and whether a pool uses any of it is the operator's call. Everything is open source, so you can read how the lists are enforced rather than take anyone's word for it.
-
-## Where SPP Sits in the Privacy-Pool Family
-
-I asked Antonio where SPP lands in the wider privacy landscape, and he was refreshingly unbothered about being first: SPP is a **privacy pool**, in the lineage of private notes spent inside circuits. Tornado Cash is the famous one, Railgun uses similar techniques, and a handful of newer teams are working on compliance-aware pools too. The shared goal is severing the public link between an origin account and a destination account. What makes SPP interesting is the feature set layered on top of that, which is where we spent the middle of the call.
-
-## The Feature List, For the Hackathon Crowd
-
-Antonio led with the packaging, because there is a hackathon on and I personally know more than five teams building on SPP right now:
-
-- A **TypeScript SDK** on npm and a **Rust SDK** on crates.io, both named `stellar-private-payments`. They are new, so feedback and bug reports are genuinely wanted.
-- **Deposit and withdraw** to break the origin-destination link. The privacy you get is statistical and scales with the **anonymity set** — the number of people using the pool.
-- **Internal transfers**: you can pay other people, trade, or move funds between your own accounts without leaving the pool, so none of that activity leaks.
-- **Selective disclosure**: generate a proof that you own, say, ten notes with a given balance, without revealing your secrets or any personal information. Useful when you need to show an honest origin of funds without opening everything up.
-- An optional **global view key**. Some pools are being deployed where users encrypt certain secrets to a pool administrator, who can decrypt them off-chain when legally required and audit the trace. It is view-only — your funds can only ever be spent by you — and whether a pool enables it is, again, configurable. Institutions want this, and institutions are where the volume (and therefore the anonymity set) will come from.
-- A **CLI**, which Antonio rightly pointed out is the natural interface if you want to hand an agent a set of tools and let it operate the pool for you.
-
-On the roadmap, with the usual "no details yet": lighter-weight **tracing via KYT at deposit time** — screen funds once on the way in, then leave the user fully private instead of relying on a powerful view key — and **ragequit**, so that if a pool bans you unfairly you can get your funds back, at the cost of the privacy you would otherwise have had.
-
-## Multi-Asset and Multi-Policy Pools
-
-My own question, which I prefaced with "this might be stupid": does trading inside the pool mean **multi-asset pools** are possible? Antonio said they could ship one relatively soon, but most multi-asset designs **sacrifice privacy**. Fifty people using token A and fifty using token B in one pool does not give you an anonymity set of 100; it gives you two sets of 50 dressed up as one. Better UX, no extra privacy. The team has ideas for a design where every asset shares the same large anonymity set — best of both worlds — but it needs changes to the pool and is not on this year's roadmap.
-
-My follow-up, a thought of a thought: not multi-asset but **multi-policy** — one configurable, interoperable pool usable by different contracts and assets. That one is technically possible today. The trade-off is that an arithmetic circuit pays for every operation whether you use it or not, so more policies in one pool means longer proving times. If you are at the hackathon this weekend: just do it.
-
-## Anonymity-Set Economics: Who Deposits First?
-
-The question I was most curious about. Many of SPP's guarantees are only as strong as the number of people in the pool, and pools are per asset today. How does a mainnet pool bootstrap an anonymity set, and what is the smallest set Antonio would call useful?
-
-On bootstrapping: "believers and privacy enthusiasts," with a laugh, but then a real answer. SPP supports **splitting and mixing notes inside the pool**, so there are no fixed denominations like the mixers of old — one deposit can become twenty withdrawals. That means you can deposit 0.1 of a token to test the waters instead of committing a round 1,000. Antonio's bet is that enough people want privacy badly enough to take the small leap of faith first, and that institutional volume follows.
-
-On the minimum: it depends on your threat model — an average user and a journalist whose life depends on it are different cases — and the anonymity set is not the only thing that matters. **Metadata hygiene** matters just as much: deposit from account A and withdraw to account A and you have bought yourself nothing. Use unrelated accounts, ideally with a third account paying the transaction fee. With proper hygiene and enough time in the pool, his bare-minimum number was **12**, which he noted is roughly the ring size he recalled from Monero's ring signatures. I appreciated getting an actual number.
-
-My tangent for the builders in the audience: protocols with AMMs or treasuries could upgrade their contracts to be SPP-compatible and move a chunk of liquidity into a pool, giving it a base of depositors from day one. Nobody told me this was impossible.
-
-## Housekeeping: Demo Errors and Where to Ask
-
-Several of you hit timeouts and simulation failures using the demo with Freighter on testnet. Antonio's explanation: SPP is under active development, breaking changes land multiple times a week, and each one can mean recompiled circuits, new binaries, and redeployed contracts. If your browser is holding old circuits or old state in local storage, proofs get generated against stale data and simulation fails. The fix: open developer tools, **clear local storage** for the demo page, delete the page's cookies, and reload. For the record, "simulation failed" is my least favorite error on Stellar too.
-
-Where to get help: if you are sure it is a bug in the code and not in your setup, open an issue on the GitHub repo (responses can be slow while they build). For questions, there is a **Telegram group** for people developing on SPP — Antonio shared the link, I posted it in the chat, and I warned him that every privacy builder on Stellar is about to join. His X profile went into the comments too, so your timelines can gain a few more privacy freaks.
-
-## Closing
-
-About 200 of you were watching live. Round two ran roughly an hour later: a protocol discussion on **CAP-87**, the proposal adding host functions for **ML-DSA post-quantum signature verification**, on a Google Meet with the core developers. Builders in Istanbul: the **Stellar Pro Hackathon** at Grand Pera is this weekend, and I expect several of you to show Antonio your projects and ask him a bunch of questions about SPP. Busy weekend for him. Thank you, Antonio — hopefully I will see you at Meridian. See you next week.
diff --git a/meetings/2026-09-24.mdx b/meetings/2026-09-24.mdx
deleted file mode 100644
index f6d428ce2..000000000
--- a/meetings/2026-09-24.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-title: "2026-09-24"
-authors: kaankacar
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="0CqboqwZnH4" />
-
-## Road to Hack Meridian, Episode One
-
-This week kicked off a live stream series that runs all the way to **Meridian**, our flagship conference, and **Hack Meridian**, the hackathon that happens right before it. The idea is simple: we want builders walking into Hack Meridian with as many resources as possible, and the first resource you should look at when building on Stellar is **Raven**. "If you're building on Stellar, just ask Raven" isn't an official slogan, but it's the one we keep repeating. I look at a lot of protocols to see how they help their developers, and — biased as I am — Raven is probably the best thing happening to a Web3 builder right now.
-
-Thankfully I wasn't alone at 11 p.m. staring at my comment section. My guest was **Feems** from **Guava Global**, the studio managing the Hack Meridian efforts. Feems leads hackathon program design and the hacker experience: live streams, workshops, coordination with the activation hosts across Europe, and co-hosting these Thursday streams with me from here on.
-
-## Hack Meridian, the Facts
-
-Guava describes itself as a strategy and production studio that delivers events, activations, and experiences that bring ideas, brands, and communities to life. Hack Meridian is their big one this year:
-
-- **Lisbon, October 25–26**, at **ONE16** — an old railway station, which is a very cool venue.
-- **Two tracks.** **Genesis** is for developers and founders bringing a new idea to Stellar. **Scale** is for existing projects looking to scale onto Stellar or integrate with it. The specific themes within those two categories drop soon.
-- On-site support, workshops, mentors, prizes, and a room full of developers from across Europe.
-- **Find Your Way**, the campaign this stream is part of: more than **10 partners** throwing **20+ IRL activations** across Europe — Madrid, Barcelona, Paris, London, Porto, and more — for builders, founders, and newbies alike. The calendar lives on hackmeridian.com, and Guava Global's X account retweets everything.
-
-## Raven at a Glance
-
-Feems' framing beat mine (mine was "a time capsule of your future self talking down to you, informing you every step of the way"). When you build in an ecosystem, the biggest question is _has this been built already?_ — and answering it normally means scouring tons of documentation. Raven collapses that into one place: hundreds of developer docs plus everything happening in the Stellar ecosystem, so you can ideate faster, check **relevancy** — the biggest problem at the scale stage — and keep up with how fast the development side moves. Think of it as your **builder sidekick**.
-
-Setup is one line. Go to **raven.stellar.org**, copy the command for your AI tool of choice — Codex, Claude, whatever — run it, authenticate, done. I demoed it from a clean Claude Code terminal running Opus 5.5: open the MCP list, see that stellar-raven needs authentication, click authenticate, agree to the terms in the browser window, and you're connected in under a minute.
-
-One piece of builder feedback worth adding. Technical questions are getting rarer — not because builders have no technical problems, but because the ecosystem has more than enough tooling to do practically anything on Stellar. The question has evolved from "how do I do this on Stellar" to "how do I find the material that lets my AI build X on Stellar," and that is precisely the gap Raven closes. Fewer technical questions also means more **ideation** questions: at the last Meridian, for every technical question we got ten about ideas, and whether that idea had already been validated in a recent SCF round.
-
-## The Demo: From "a ZK Track" to a Shortlist
-
-Feems walked through the questions every builder asks. Ideation: what could I build? (The part that takes longest; the heartbreaking failure mode is spending months on something nobody wants.) Validation: does anyone want this, does it fit the ecosystem, does it line up with funding? For Scale projects: market research and a real consumer base — which, not coincidentally, is what judges look at too. A future stream will cover judging properly.
-
-So I played a Hack Meridian participant. My prompt, roughly: _I'm at Hack Meridian and want to build something around privacy, maybe ZK — let's pretend there's a ZK track. Use Raven to see what privacy solutions are live on Stellar, and check previous SCF rounds for funded privacy projects. Also, you're being live streamed, so show how and why you're using Raven at every step._ (I regretted that last sentence immediately. Don't tell your agent it's on TV.) Someone in chat pointed out I'm also a judge; I am, and a hard one to please — I try not to be impressed by projects.
-
-While it ran I plugged a sibling project: **Stellar Build**, a more private, hands-on set of skills and personas for the AI of your choice that doesn't touch dynamic data. Stellar Build helps you decide what to build; Raven tells you what has already happened — and Stellar Build uses Raven under the hood, because Raven is the best.
-
-Raven came back with the privacy projects live on Stellar today, each with its SCF cohort and the amount awarded: a reusable-KYC project, **Moonlight** (compliant confidential transactions), and **Zarf** — the Turkish team doing private token distribution with ZK, who you met in the July 2 note. It also laid out what the protocol itself supports right now, the technical border of what you can build — a border that gets wider every day. And because Raven indexes the Electric Capital developer report, not just SCF, it surfaced projects like **KALIEN**, Tyler's ZK-proven Asteroids game. Cohorts 23, 37, 40, and 42 flew past, each with the track applied to and the funding received.
-
-Here's the point. I started "knowing" three things: I'm at the hackathon, there's a ZK track, I want to build on it. I got back ideas proven to have a place in the ecosystem — not to copy, but to build something bigger, smaller, nicher, or better on top of. Step two: pick one and go nicher. I grabbed one of the listed projects and asked whether a more niche version existed — think threshold encryption, confidential transfers, sealed-bid auctions. Raven's answer: a few, none funded or listed as projects, so maybe I'd walked down a wrong road — or a new one. The closest match was **Stelvin**, a sealed-bid batch DEX that uses **drand** time-lock encryption rather than ZK, built by a Turkish builder I know who won our Istanbul hackathon in June 2025. It also surfaced **Sub Rosa**, a sealed commit-and-reveal protocol that, if I remember correctly, has received InstaRewards and is heading into the upcoming SCF round. The name-dropping isn't the point; the speed is. You go from "privacy, I guess" to "here is the shape of the final product" in minutes, as long as you know the next question to ask: what can be nicher, what can be bigger.
-
-And my standing advice to builders: you chose Stellar and you chose this hackathon — so at the very least, choose to build something that brings you joy.
-
-## Protocol 28, and a Correction
-
-Feems asked how a newcomer finds technical documentation through Raven. The answer explains what Raven _is_: an MCP, and MCPs fetch dynamic data. Every call pulls not only the Stellar skills, every SCF submission, and every project in the Electric Capital report, but the developer documentation itself — Raven's **Stellar docs family** is a full-text search over developers.stellar.org. So I asked it what changed with **Protocol 28**.
-
-Raven said Protocol 28 has three CAPs and "is not live yet." I let that slide on stream, so for the record: the three CAPs are right — **CAP-83** (validators can vote to drop the transaction set from the current ledger), **CAP-85** (externally managed contract executables), and **CAP-86** (host functions for sparse Symbol-keyed map creation and unpacking) — but "not live yet" was stale. Per the software-versions page in these very docs, Protocol 28 hit testnet on August 27 and **mainnet on September 16**, a week before this stream. The tooling part was correct: stellar-core and **Stellar CLI v28** are out, open source, on GitHub. Go update.
-
-## Scale Track: Find Your Nearest Neighbor
-
-We'd just wrapped a hackathon in Istanbul with the same Genesis/Scale split, so Feems asked how Scale projects should use Raven. For a Scale builder the question is "what's my next step," and you answer it by being inspired by something. What my teammates and I did with the Istanbul Scale track was help each team ask Raven: _is there a project similar to mine, what are the differentiators between theirs and mine, and how do I make mine better?_ That's where scaling starts, and where differentiating yourself from the rest of the ecosystem starts.
-
-## How We Actually Use It
-
-Me: every time a builder asks me anything about Stellar, I ask Raven first — partly to answer, partly to check it still works. I use it to research older content, and almost daily to find out whether a tool is being built somewhere in the world. Say I want a Go CLI for Stellar: maybe someone is already building it, or building something that gets me there faster. The research side is the side I use most.
-
-Feems: understanding past hackathons and the projects that came out of them, to build better personas for these streams and the hackathon itself. It aggregates all things Stellar, which is exactly what a program designer needs.
-
-## What's Next
-
-Feems closed with the activation calendar — events next week in Madrid, Barcelona, Lisbon, Berlin, and Paris from hosts including CryptoDays and Layer X, with the slide refreshed every week.
-
-Next Thursday the topic is **LayerZero OFT and USDT0**: how USDT0 works on Stellar and how the underlying OFT infrastructure works. We ran an informal survey of builders, and cross-chain applications and privacy were the runaway answers. We have NEAR Intents, we have CCTP, we have a bunch of things — but LayerZero is one of the newest integrations and deserves a proper walkthrough. The week after will probably be privacy again: we've covered SPP and confidential tokens a lot, but one more, more mathematically detailed session — maybe with one more guest — wouldn't hurt.
-
-## Closing
-
-More than **150 people** watched this at midnight my time, and Feems joined at 4 a.m. in theirs — one finds a way. I also owe you a promise: I will spend thirty minutes of my night learning how to zoom in on my terminal, so nobody has to squint next time. I just got my visa, so fingers crossed I'll be in Lisbon, side by side with Feems, helping you build more interesting things. Follow Guava Global on X and keep an eye on hackmeridian.com. See you next week.
diff --git a/meetings/2026-10-01.mdx b/meetings/2026-10-01.mdx
deleted file mode 100644
index c3ad08b50..000000000
--- a/meetings/2026-10-01.mdx
+++ /dev/null
@@ -1,90 +0,0 @@
----
-title: "2026-10-01"
-authors: kaankacar
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="Zo8LK7puSTc" />
-
-## Happy Stellartober
-
-October is the month of **Hack Meridian** and the **Meridian** conference, which is exactly why I refused to spend the call talking about either of them (mostly — see the intermission below). This week was about **USDT0 on Stellar**: Tether's USDT delivered to Stellar over **LayerZero**'s OFT standard. Think of it as a prologue to a USDT0 AMA — if everything goes well, next week I'll have people who were actually involved in issuing USDT0 and wiring Stellar into LayerZero on the stream, and my job this week was to make sure you ask them the right questions.
-
-The agenda: slides (necessary, for once), a short intermission about Hack Meridian, then a live tour of **nine demos in one website**, including launching an omnichain token on Stellar and driving a vault on Stellar from **MetaMask**. Everything I showed lives in one public repo, and every address I mentioned is verified on-chain.
-
-## What USDT0 Is
-
-USDT0 is Tether's USDT moved over LayerZero's **Omnichain Fungible Token (OFT)** standard. The canonical USDT stays locked in an adapter contract on **Ethereum**; every other chain holds USDT0 minted against that locked supply. USDT itself is Tether's asset; USDT0 is built and operated by **Everdawn Labs** (I said "I should fact check this" on the call — I did, and it's correct). It's live on 23 networks, and as of **September 2** Stellar is one of them.
-
-One ground rule: **USDT0 is on Stellar mainnet only.** Anything called USDT0 on testnet is somebody's mock. The LayerZero _endpoint_, however, is live on testnet, so your own test tokens work there — which is exactly what the demos use.
-
-Where we stood as of the call — not a sales pitch, just a sense of the potential:
-
-- **23,717 accounts** hold a USDT0 trustline, up from about 13,500 roughly 17 days earlier — growth of about three quarters in two and a half weeks.
-- About **2.58 million USDT0** sits on Stellar, almost all of it held inside 23 contracts.
-- **Seven DVN operators** are registered on Stellar mainnet; USDT0 requires three of them.
-- USDT0 is the biggest LayerZero tenant on Stellar but not the only one: of the last 50 messages leaving Stellar when I built the slide, 38 were USDT0. The rest came from other apps — PayPal's and Ethena's among them.
-
-## Each Leg Has Its Own Mechanism
-
-An OFT keeps one total supply across chains by pairing a debit on the source with a credit on the destination, but the mechanism differs per leg. On **Stellar** it's **mint/burn**: sending burns your USDT0 through the Stellar Asset Contract; receiving has a contract called the **SAC manager** mint to you, so supply on Stellar always equals what was bridged in. On **Ethereum** the OFT is an **adapter**: sending locks canonical USDT (approve first), receiving unlocks it, nothing is ever minted. That invariant is the whole security story — USDT0 minted everywhere else equals USDT locked in the Ethereum adapter — so never promise "burn and mint on both ends"; always check the leg.
-
-Remember CCTP? Same story with decimals, as we saw in [Elliot's CCTP call](./2026-07-30.mdx): Stellar has seven, USDT on Ethereum has six. OFT solves this with a **shared precision**, six for USDT0, and amounts travel on the wire as a 64-bit integer in those six decimals. Send `12345678` stroops and the wire amount is `1234567`; the trailing eight stroops are **dust**, removed before the message is built, and they stay in your account. The practical rule: always call `quote_oft` first — it returns the exact amount that will arrive, and skipping it fails your simulation.
-
-A LayerZero message is not a transaction that travels. It's five steps: **send, verify, commit, execute, mint**. The source OFT calls the endpoint and a packet is emitted with a nonce, endpoint IDs, sender, receiver and payload. Each required **DVN** — decentralized verifier network — independently attests the packet on the destination chain. Once the required set has attested, the verification is committed on the receive library (anyone can call this). An executor calls `lz_receive` on the destination OFT — anyone can be the executor. And on Stellar, the OFT asks the SAC manager to mint to the recipient. The DVN set is dynamic and may grow or shrink; for now, know that DVNs exist and why.
-
-## Three Contracts and a Classic Asset
-
-On EVM chains one contract is both the token and the LayerZero app. On Stellar it's several pieces — the most confusing part for me when I first learned LayerZero:
-
-1. **The classic asset, USDT0.** Its issuer account is locked, and the flags allow freezing and clawback, like Tether does on every chain.
-2. **The Stellar Asset Contract.** The SEP-41 view of the asset — balance, transfer, burn, the usual suspects. Its admin is not a key; it is a contract.
-3. **The SAC manager.** The admin contract. It holds the admin role and mints only for holders of the minter role. The OFT holds that role, and the SAC manager itself is owned by a multisig.
-4. **The OFT contract.** The actual LayerZero app: `quote_oft`, `quote_send`, `send`, `lz_receive`. It stores the peers and the enforced options, and it points at the SAC and the endpoint.
-
-The classic asset, SAC, and OFT addresses are on [the USDT0 page in our docs](https://developers.stellar.org/docs/tokens/usdt0-layerzero) — point your AI at it. The SAC manager is the SAC's admin, so you can read its address from the SAC itself. Everything about USDT0 is readable without a key or a signature: Horizon gives you the classic side, Stellar RPC gives you the contract side through simulation, and LayerZero's **deployment registry** is the source of truth for every LayerZero address. One lesson from the chain data: the Stellar testnet endpoint was redeployed in August, so **always fetch the registry at runtime** instead of hardcoding. The Stellar CLI works too — a `contract invoke` with any account as source is a simulation, no signing involved.
-
-## Sending USDT0 From Stellar
-
-Sending is five steps and looks like a normal Soroban invocation: build the send parameters; call `quote_oft` for the exact amount that arrives and use it as the minimum; call `quote_send` for the fee, paid in **XLM**; call `send` — the OFT burns your USDT0 through the SAC and the endpoint emits a `PacketSent` with a **GUID**; then track that GUID on **LayerZero Scan** until it says delivered.
-
-Some details cost real money if you get them wrong: the recipient is raw bytes, either a G or a C address; a G recipient needs a **trustline before the message lands**; and the seventh decimal never leaves your account, which is why you call `quote_oft`. Tracking uses the LayerZero Scan API, no key needed — by transaction hash, by GUID, or the latest messages for Stellar. One testnet quirk: Scan indexes Stellar messages by GUID first, so the transaction link can lag a few minutes. Delivery is **permissionless**: once the required DVNs have attested, anyone can finish the message. Remember CCTP? It sort of works like that.
-
-The first question I get from Stellar developers is how this differs from CCTP, so I put together an honest side-by-side (slides coming to X). The short version: not identical, but if you dabble in CCTP, USDT0 over OFT will not be a problem for you.
-
-## Intermission: Hack Meridian
-
-My intermission guest was **Feems** from **Guava**, the production studio helping produce Hack Meridian, who you met on last week's stream. The facts: **Hack Meridian** is a two-day hackathon on **October 25–26 in Lisbon**, with two tracks — **Genesis**, for people with great ideas who want to build (with Raven, the Stellar MCP, at hand), and **Scale**, for existing teams already on Stellar looking to grow. Expect workshops, mentors, office hours and prizes, then a day to chill before the **Meridian** conference on **October 28–29**.
-
-Leading up to it, partners are running a plethora of events across Europe — Barcelona on October 3, Paris on October 6, an online AMA with me on October 8, plus Berlin, Paris and Porto, with more announced each week. Go to one to get a taste of Hack Meridian. My proposal, only half joking: she should do this intermission every week until the hackathon. Thank you for staying up late for it.
-
-## The Demos: Fork This Repo
-
-Everything lives at [kaankacar/stellar-layerzero-demos](https://github.com/kaankacar/stellar-layerzero-demos). Please fork it and do a bunch of weird stuff with it — every time I play with LayerZero, another use case opens up. Highlights of the tour:
-
-- **Explainer** — an interactive version of the slides, with the DVNs live on testnet and the "Stellar twist" of multiple contracts. I'm an academic boy, so there are multiple-choice quizzes too.
-- **Inspector** — mainnet, read-only, refreshed every 30 seconds: USDT0 supply and holders, plus the **wired peers** — the 21 networks your app on Stellar can connect to: Arbitrum, Berachain, Tempo, Optimism, Monad and more. I don't know half of these chains, but each one is a user base you might want to reach. (HyperCore shows up in LayerZero's testnet API but has no registry ID, so it's unusable for now.) A simulate view shows how many DVNs a route requires: three.
-- **Bridge tracker** — paste a transaction hash and follow it, or browse the latest USDT0 messages touching Stellar; the last four were from Polygon and Ethereum, each attested by three DVNs. Timing varies: my first Ethereum testnet transfer took 20 minutes because of Ethereum's block times; Arbitrum takes about two seconds.
-- **Quotes and a playground** — mock only, because real USDT0 is mainnet only.
-
-### Launching an Omnichain Token, Live
-
-The **launchpad** generates an issuer keypair in your browser and keeps it in local storage — testing only, not how you'd launch a real token, but it walks the exact steps. I'd already launched a **KAAN** token (please don't buy it if anyone offers it to you; I'm not selling, and I don't even have any). For the live run I named the asset after the last person in chat — **ELLIOT** — in lock/unlock mode (the alternative is mint/burn, like USDT0), one million supply.
-
-The Stellar side, one Freighter popup per step at a thousandth of an XLM each: fund a throwaway issuer via Friendbot, deploy the SAC, deploy the SAC manager (USDT0 has one, why shouldn't ELLIOT), open a trustline (always — OFT or not, a SAC means a trustline), mint a million ELLIOT, hand the SAC admin to the SAC manager, deploy the OFT, and **lock the issuer** — simulating USDT0's trust model with clawback and master weight.
-
-Then the part that makes it omnichain: deploy the OFT on **Arbitrum Sepolia** via MetaMask, enforce options, and wire the two OFTs as peers — three wallet-signed transactions. Result: ELLIOT live on two chains, one OFT owned through Freighter and one through MetaMask, on a pathway using the active testnet DVN. Recipients need an ELLIOT trustline; open one and I'll send you some. Want more chains? Repeat the last three steps per chain: deploy the OFT, enforce options, wire the peers.
-
-### A Vault on Stellar, Driven From MetaMask
-
-The last demo: a vault on Stellar testnet that you operate with MetaMask on Arbitrum Sepolia. To be clear, I am not saying MetaMask has integrated Stellar. I'm saying that, right now, MetaMask on an EVM L2 can interact with a contract that lives on Stellar. I minted some mock USDT0 on Arbitrum, hit **deposit via LayerZero**, signed the MetaMask popup, and watched the tracker: one DVN verification required.
-
-Then the demo stalled — I hate it when my demos don't work — so I nudged it with my Freighter: committed the verification and called the endpoint's `lz_receive` myself. "You were the executor." Exactly the logic from Elliot's CCTP demo: instead of waiting for execution, you finish the message. A moment later the vault on Stellar held **500 more mock USDT0**, deposited from MetaMask.
-
-Now imagine the rest. Five years ago people talked about omnichain tokens with no good use cases; the industry is in a more established place now. Omnichain DEXes, omnichain lending and borrowing, omnichain wallets — anything. Every user of Ethereum, Arbitrum, Berachain or Monad is now a potential user of your financial application on Stellar. Fork the repo, ask Raven what else is possible, and build it.
-
-## Closing
-
-Around **250 people** were still watching when I closed, and I hate ending a stream with a quarter of a thousand viewers on. I'll be at Hack Meridian helping every one of you — if you're around, ask me about LayerZero. Thanks for watching, enjoy the outro music, and I'll see you next week — hopefully with something as interesting as this week's topic.
diff --git a/meetings/2026-10-08.mdx b/meetings/2026-10-08.mdx
deleted file mode 100644
index ef0cf44d4..000000000
--- a/meetings/2026-10-08.mdx
+++ /dev/null
@@ -1,90 +0,0 @@
----
-title: "2026-10-08"
-authors: kaankacar
-tags: [developer]
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="FK4_RmHCirU" />
-
-## A USDT0 AMA
-
-Last week I built a USDT0 demo and walked through how the LayerZero infrastructure works on Stellar ([2026-10-01](./2026-10-01.mdx)). Most of your questions about **USDT0** arrived _after_ that call, so this week I brought reinforcements. I collected around 30 questions from you and from a few ambassador chapters, shortlisted nine, and hoped to get through four. We got through six or seven.
-
-My guest was **Fabricius "Fifo" Zatti**. If you've been in the ecosystem for more than six months, you probably know him already. He has been around Stellar for about six years. He started at **Cheesecake Labs**, where he was the top contributor to **Stellar Plus**, and now works at **The Aha Company**. He also wrote **Colibri**, the TypeScript toolkit for Stellar that includes contract build verification. He works with SDF on a program that brings experts from the ecosystem to help partners build on Stellar.
-
-On USDT0, Fifo was one of the Stellar-side technical contacts for the **LayerZero Labs** and **Everdawn Labs** teams. He worked on the issuer setup sequence, six versus seven decimals, multisig tooling, build reproducibility and verification, DVN data needs, and partner readiness. To be clear: he is not from LayerZero or Everdawn, and he did not build the LayerZero protocol internals or set USDT0 policy. He said he might not have every answer, and he gave honest ones where his memory was fuzzy.
-
-For scale, as of the call: about **5 million USDT0** circulating on Stellar, across roughly **25,000 accounts**.
-
-## Before the Questions: Hack Meridian
-
-**Hack Meridian** is our flagship hackathon before the **Meridian** conference. It runs on **October 25–26 in Lisbon**. If you have no visa restrictions, come show us what you're building, and **make your repos public** so we can judge them. No idea what to build? Ask [Raven](https://raven.stellar.org). Prizes go up to **$30,000 in XLM**.
-
-There's more than one way to take part. That day was my third stream: an AMA as a road to Hack Meridian with **Web Zero**, a Spain-based developer community, and a presentation on Stellar tooling at a workshop organized by **Her DAO**. The next day there was an event in **Berlin** on building with AI. Our production partner is **Guava Global**, part creative studio, part production house, part cultural connector.
-
-## Fifo's Seat at the Table
-
-My first question: this was not a one-seat operation, so what did his seat look like, and did any Stellar idea take longer than necessary to land?
-
-Fifo tries to stay **neutral and transparent** about how things work and how choices affect the ecosystem. LayerZero is a huge protocol, and USDT0 already runs on many networks with its own standards. Soroban is a new space for them. So his job was to make sure the teams had all the information when they chose a path. For almost every project that comes to Stellar, he spends extra time on three things: **how storage works**, **how authorization works**, and **the bridge between classic and Soroban**. He doesn't see these as friction points. He sees them as places where you can use Stellar to your advantage. Much of his role was to question design choices: does this come from a requirement, or from tooling you're used to on other networks? If the latter, can we find a better way on Stellar?
-
-The stressful part was **build reproducibility**. Everyone wanted USDT0 out quickly, but also well tested and bulletproof, and reproducibility was a hard requirement. The existing standard, [SEP-55 (Contract Build Verification)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0055.md), works through attestations tied to the CI process in a repository. During the engagement the team saw they needed a different angle: reproduce the contract build itself. That's hard with Rust compiled to Wasm, where differences in the environment can change the output hash. A lot of people worked on it, and the result is the new [SEP-58 (Contract Build Reproducibility for Verification)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0058.md). Fifo can't wait to see the ecosystem pick it up, probe it, and improve it.
-
-## Why a Classic Asset and Not a Pure Soroban Token?
-
-This came from last week's stream. When USDT0 leaves Stellar, the seventh decimal is lost; when it arrives, the seventh decimal is empty. A pure Soroban token could carry six decimals, like USDT0 on EVM chains. So why did USDT0 land as a classic asset with a SAC?
-
-Fifo called this the hottest question for any asset issuer coming to Stellar. He admits a bias: he comes from "the old testament of Stellar" and loves the classic side, while also saying Soroban filled real gaps. He thinks the USDT0 teams were pragmatic. A pure Soroban token could work. Good examples exist, such as **SolvBTC** and the **Centrifuge** assets. But the key question for builders is: **how do you expect people to use this asset?** His case for classic:
-
-1. **Reach.** Classic assets have been around longer. Wallets, non-custodial apps and secondary markets support a new classic asset automatically, so the surface area is immense.
-2. **Nothing to build or audit.** If the control flags meet your requirements, you deploy no extra contracts and need no separate audit. Classic assets get audited with the protocol, and every classic asset runs the same battle-tested implementation.
-3. **Both worlds.** Through the SAC you reach DeFi and smart contracts. You also keep the classic side: the native DEX, liquidity pools and path payments, all cheap and scalable.
-
-For USDT0 specifically, it checked every box. The control flags give the needed control, and the SAC manager adds the extra administration rules. Fifo called the SAC manager "something fancy they did there" and recommends studying it. The OFT then plugs into the classic asset to handle minting and burning. On decimals, he thinks the trade-off is small. Coming in, you get _more_ resolution on Stellar. Going out, you round or leave some dust behind.
-
-### The Other Side of the Coin
-
-I played devil's advocate and asked for the downsides. Fifo agreed readily:
-
-- **Classic is limited to what the protocol offers.** You get the control flags, or you extend the admin with a contract, and that's it.
-- **No atomic global pause.** With classic you pause through trustlines, one by one. You can bundle several in one transaction, but nothing guarantees you pause every holder at once. A Soroban token can do that.
-- **No per-transfer rules.** Need compliance checks during each transfer? [SEP-57, T-REX](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0057.md), does that for Soroban tokens. You can't add it to a classic asset; workarounds don't behave the same.
-- **Trustlines are part of the user flow.** Where you already run KYC, the trustline fits in nicely. Where you want users to just hold the token, you have to build it into the workflow, sometimes through the trust function in smart contracts.
-
-Classic assets are a good solution, but not a silver bullet. The unique part is that Stellar has both, and they work together. My summary: the two big advantages of a Soroban token are **customizability** and **onboarding**. With smart wallets, users can hold a Soroban token from day one without waiting for a trustline.
-
-## Why a Separate SAC Manager?
-
-In LayerZero's standard OFT, one contract is both the token and the app. On Stellar, the USDT0 OFT mints through a separate **SAC manager** (the three-actor picture from last week: the asset, the SAC admin, and the OFT). Why not make the OFT the SAC admin directly?
-
-You can. Fifo recalled this being a big topic, and he believes the reason was **how the teams wanted to set up the multisig and governance**, though he doesn't remember every detail. The general lesson is about how much responsibility you put in one contract. On Stellar you weigh **storage and resources**, because they scale differently. You also weigh **upgradability**: separate contracts let you upgrade one piece while others stay fixed. He doesn't think upgradability drove this case. The classic asset also mattered. You can't change how the SAC works; it's an interface you build on top of. So a small admin contract on top was necessary, and with the token logic already handled by classic, it wasn't a big lift.
-
-His advice, which I want to repeat: **don't copy other projects**, even big ones. Evaluate the design for your own use case. Flexible, composable building blocks exist so you can adapt them to your reality. Many developers now treat USDT0 almost as its own standard for cross-chain apps, so it matters to know which parts are design choices, which are security choices, and which are required.
-
-## What Does "Waiting for Confirmations" Mean on Stellar?
-
-Stellar closes a ledger and it's final, with no reorgs. So what does it mean when a LayerZero app waits for confirmations on Stellar, and how should an app pick that number?
-
-In LayerZero, the full path from a source contract through the endpoint, the DVNs and the destination endpoint to the destination contract is a **channel** (a pathway). You configure each channel independently. Two key settings are **finality**, the number of block confirmations to wait for on the source, and **verification**, which DVNs must verify the message and how many.
-
-Confirmations exist because some chains can reorg. Competing chains get validated, one wins, and transactions on the loser roll back. That's why Bitcoin and Ethereum transfers wait X blocks. If the destination step ran before the source was truly final and the source then reverted, you'd have a big problem. On Stellar the setting still exists, but a transaction is **final after one ledger, about five seconds**. Fifo's recommendation: configure Stellar channels with a low value. Add a couple more if you want a safety margin, but you don't need to. For the other chains on your channel, assess each one separately.
-
-## Why Does Leaving Stellar Take About Half an Hour?
-
-A viewer said leaving Stellar takes about half an hour, while arriving from Polygon takes under two minutes. What are the delivery states?
-
-It comes down to **channel configuration**. A message goes through three legs:
-
-1. **The source transaction.** On Stellar that's about five seconds, plus however many confirmations the channel waits for. USDT0 has its own channel with its own configuration.
-2. **The DVNs.** If the channel requires three DVNs, it takes as long as those DVNs need to pick up, verify and confirm the message on the destination.
-3. **Execution on the destination.** The message runs on the destination chain, and that chain's confirmation time applies.
-
-Open [LayerZero Scan](https://layerzeroscan.com) and find your message. It breaks down each step: time on the source, time waiting for DVNs, which DVNs took part, and the final leg. You can see where the time goes and whether it's just configuration.
-
-I asked whether the number of **signers inside a DVN** slows delivery. LayerZero's own DVN, for example, is on Stellar mainnet and has multiple signers. Fifo's answer: it can, but likely not significantly; it depends on each DVN's implementation. If something is slow, look first at the **on-chain configuration for that channel**: the finality set for the sending and receiving networks is usually the biggest bottleneck. The DVN set also varies by channel: two of three, one of two, four of five. That affects processing time too. Neither of us remembered the signer counts on mainnet offhand; you can look them up from a message on LayerZero Scan. One more point from me: signer count also matters for **security**, so think about which DVNs you choose.
-
-## Closing
-
-Thank you, Fifo, for answering six or seven of my questions. I have 20 more, and I'm saving them for **Hack Meridian**. If you want to watch me ask them live, come to Lisbon on October 25–26. See you next week at the Stellar Developers Meeting.
diff --git a/meetings/2026/01/22.mdx b/meetings/2026/01/22.mdx
new file mode 100644
index 000000000..934c6cd8d
--- /dev/null
+++ b/meetings/2026/01/22.mdx
@@ -0,0 +1,38 @@
+---
+title: "2026-01-22"
+description: "In this year’s first Stellar Developer Meeting, on Thursday, January 22nd at 8am PT on Twitch, we will catch up with Ozgun and Boyan from the OpenZeppelin..."
+---
+
+_January 22, 2026_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/pq4xrdRzfIs?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## OpenZeppelin Q4 Releases
+
+In this year’s first Stellar Developer Meeting, on Thursday, January 22nd at 8am PT on Twitch, we will catch up with Ozgun and Boyan from the OpenZeppelin team and take a look at the libraries released in Q4 last year.
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/CetcWbsdRdE?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## Protocol Discussion
+
+We had three CAPs prepared for this meeting. CAP-77 will provide a way to make ledger keys inaccessible based on the network configuration upgrade performed with a validator vote. CAP-78 proposes an interface which allows developers to specify TTL extension policies such as 'if an entry TTL is less than 29 days, extend it to have 30 days TTL'. CAP-79 introduces host functions for converting Stellar strkey format strings to/from Address/MuxedAddress objects.
+
+Read more about the proposals here:
+
+[CAP-77](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0077.md) - [Discussion](https://github.com/orgs/stellar/discussions/1811)
+
+[CAP-78](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0078.md) - [Discussion](https://github.com/orgs/stellar/discussions/1825)
+
+[CAP-79](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0079.md) - [Discussion](https://github.com/orgs/stellar/discussions/1840)
diff --git a/meetings/2026/01/29.mdx b/meetings/2026/01/29.mdx
new file mode 100644
index 000000000..45dff29f9
--- /dev/null
+++ b/meetings/2026/01/29.mdx
@@ -0,0 +1,26 @@
+---
+title: "2026-01-29"
+description: "We have one new CAP to discuss and that is CAP-80."
+---
+
+_January 29, 2026_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/TXuKiEEwEsU?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## Protocol Discussion
+
+We have one new CAP to discuss and that is CAP-80. This proposal adds BN254 Multi-Scalar Multiplication and modular arithmetic used in a variety of ZK proof applications. Adding host support for these will greatly improve the performance of these use cases.
+
+We also follow up on a previous CAP - the CAP-73.
+
+Read more about the proposal here:
+
+[CAP-80](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0080.md) - [Discussion](https://github.com/orgs/stellar/discussions/1826)
+
+[CAP-73](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0073.md) - [Discussion](https://github.com/orgs/stellar/discussions/1668)
diff --git a/meetings/2026/02/26.mdx b/meetings/2026/02/26.mdx
new file mode 100644
index 000000000..a9e63e0c2
--- /dev/null
+++ b/meetings/2026/02/26.mdx
@@ -0,0 +1,28 @@
+---
+title: "2026-02-26"
+description: "In this protocol meeting we had two CAPs to discuss and that was CAP-81 and CAP-82."
+---
+
+_February 26, 2026_ · [Carsten Jacobsen](https://github.com/carstenjacobsen), Senior Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/nLxODJal-xQ?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## Protocol Discussion
+
+In this protocol meeting we had two CAPs to discuss and that was CAP-81 and CAP-82.
+
+CAP-81: This CAP introduces a simpler and more efficient eviction scan process. Instead of scanning the BucketList, the new eviction scan just uses in-memory Soroban state. This simplifies the logic while reducing disk reads and speeding up eviction speed.
+
+CAP-82: This CAP adds checked variants of the existing 256-bit integer arithmetic host functions. Unlike the existing functions which trap on overflow, the checked variants return Void on overflow, allowing contracts to handle arithmetic errors gracefully.
+
+Read more about the proposals here:
+
+[CAP-81](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0081.md) - [Discussion](https://github.com/orgs/stellar/discussions/1868)
+
+[CAP-82](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0082.md) - [Discussion](https://github.com/orgs/stellar/discussions/1834)
diff --git a/meetings/2026/04/16.mdx b/meetings/2026/04/16.mdx
new file mode 100644
index 000000000..902b9c04e
--- /dev/null
+++ b/meetings/2026/04/16.mdx
@@ -0,0 +1,117 @@
+---
+title: "2026-04-16"
+description: "Protocol 26, codenamed Yardstick, went live on testnet on April 16, 2026 at 17:00 UTC — literally the day of this meeting."
+---
+
+_April 16, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/u3zmNZXHYHw?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## Protocol 26 "Yardstick" Hits Testnet {#protocol-26-yardstick-hits-testnet}
+
+Protocol 26, codenamed Yardstick, went live on testnet on April 16, 2026 at 17:00 UTC — literally the day of this meeting. Mainnet validator votes are scheduled for May 6th. If you are running any kind of infrastructure on Stellar — nodes, SDKs, integrations — now is the time to pull the Protocol 26 changes, update your SDKs, and test against testnet before the mainnet vote. The `#protocol-next` channel in the Stellar developer Discord is where the ecosystem coordinates during upgrades.
+
+Two CAPs shipped with this release:
+
+**CAP-81** rewrites the Soroban eviction scan. Instead of scanning the BucketList on disk, eviction now works directly from in-memory Soroban state. The result is faster evictions, fewer disk reads, and more efficient node operations. This is the kind of under-the-hood improvement that compounds as Soroban usage grows — less I/O overhead means the network handles growing state more gracefully at scale.
+
+**CAP-82** adds checked arithmetic variants for the existing 256-bit integer host functions. Where the current functions trap on overflow, the new checked variants return `Void` instead, letting contracts handle arithmetic errors explicitly and gracefully rather than panicking. If you're writing DeFi contracts — lending protocols, swap routers, pricing curves — this matters: checked arithmetic means operations fail explicitly and predictably instead of silently wrapping or trapping.
+
+[CAP-81](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0081.md) — [Discussion](https://github.com/orgs/stellar/discussions/1868)
+
+[CAP-82](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0082.md) — [Discussion](https://github.com/orgs/stellar/discussions/1834)
+
+## Ecosystem Snapshot: $2B in Tokenized Real-World Assets {#ecosystem-snapshot-2b-in-tokenized-real-world-assets}
+
+Stellar has crossed $2 billion in tokenized real-world assets on the network — more than 4x growth in 12 months and 2.5x growth year-to-date as of April. This is not speculative TVL. These are actual financial instruments: tokenized treasuries, bonds, and private credit sitting on-chain today. The institutional names driving this are serious: Franklin Templeton's tokenized treasury fund, Ondo Finance, RedSwan Digital, and Centrifuge. These are not crypto-native experiments — these are traditional finance institutions choosing Stellar as their settlement layer.
+
+What makes this meaningful for developers is that those $2 billion in assets do not just sit there. They are becoming collateral in lending protocols, being deployed in DeFi, and earning yields. That creates real primitives to build on top of.
+
+## DeFi Ecosystem Update
+
+The Stellar DeFi ecosystem is maturing quickly. Here is the current state:
+
+**Blend** has crossed $80 million in TVL, making it one of the most significant lending protocol deployments on Stellar.
+
+**Stellar Templars Protocol** added six new real-world assets to lending markets on Stellar. You can now borrow stablecoins against tokenized institutional assets. The newly added collateral types include:
+
+- **DEJA** (Centrifuge) — a AAA-rated CLO strategy
+- **DEJTRY** — the Janus Henderson short-term US Treasury strategy
+- **CETES** and **USTRY** (EtherFuse) — tokenized Mexican and US Treasury exposure
+- **soBTC/USDC pair** — you can now use Bitcoin as collateral to borrow on Stellar
+
+Institutional-grade RWAs as DeFi collateral is a significant milestone. Sovereign debt meeting DeFi accessibility is a phrase worth sitting with.
+
+**Sushi** deployed their first concentrated liquidity DEX on Stellar. PYUSD/USDC and XLM/USDC pools are live. Cross-chain functionality is coming soon through Squid Router, which connects Stellar assets to 80+ other blockchains.
+
+**EURA** — a MiCA-compliant euro stablecoin from All Unity — is live on Stellar. This is a fully backed, regulated euro stablecoin built for institutional use. A regulated euro stablecoin on Stellar is a notable addition for builders targeting European markets or building compliant financial applications.
+
+For a full picture of where Stellar DeFi stands, the SDF published a post titled _"What the DeFi is happening on Stellar?"_ that captures how the ecosystem has been quietly maturing while others debate narratives.
+
+## x402 and MPP: Agentic Payments Are Live on Stellar Mainnet
+
+Both x402 and MPP — the two leading agentic payment protocols — are now live on Stellar mainnet. This is a significant milestone for anyone building at the intersection of AI and payments.
+
+### The Problem They Solve
+
+The entire payment infrastructure of the internet was designed for humans. An AI agent that needs to call a paid API hits a fundamental wall: there's a form, a billing dashboard, an API key a human configured. The agent hits a paywall and the workflow breaks. x402 and MPP solve this by making machine-to-machine payments as simple as an HTTP request.
+
+### x402
+
+x402 is built on the HTTP 402 "Payment Required" status code — a code that has existed since the 1990s but was never meaningfully implemented until now. The flow is simple: an agent requests a resource, the server responds with a price, the agent authorizes stablecoin payment, and the resource is delivered. One HTTP round trip.
+
+On Stellar, this settles in under 5 seconds. Stellar's fees — approximately 0.00001 XLM per transaction — are essential here: if your transaction fee costs more than the payment itself, micropayments do not work. Stellar also has USDC, PYUSD, and USDY as first-class native assets — not bridged, not wrapped.
+
+x402 is co-governed by Coinbase (who launched it), Cloudflare, Google, and Visa. Google has integrated it into their agentic payments protocol. Cloudflare built it into their pay-per-crawl tooling. The SDF also brought OpenZeppelin into the picture — they secure over $130 billion in on-chain assets — to power the x402 facilitator and provide audited smart account contracts with programmable spending limits and guardrails.
+
+### MPP (Machine Payments Protocol)
+
+MPP was co-developed by Stripe and Tempo and launched last month, and it is live on Stellar. Where x402 handles one payment per request, MPP introduces _sessions_: an agent pre-authorizes a spending limit up front, then streams micro-payments within that session, settling in bulk at the end. If your agent is querying a data feed thousands of times an hour, MPP sessions are the right model — you avoid the overhead of a per-request authorization for every single call.
+
+On Stellar, MPP settles via Soroban SAC transfers. Agents never need to hold gas tokens because the SDK handles server-sponsored fees.
+
+MPP launched with over 100 integrated services including Stripe, Anthropic, OpenAI, Shopify, and Visa. The core spec has been submitted to the IETF for standardization as the official HTTP payment standard.
+
+### The Full Picture
+
+To connect this back to everything else in this meeting: those DeFi protocols, tokenized assets, and stablecoin rails all become accessible to AI agents through these payment primitives. An agent can borrow against a tokenized treasury, pay for a data feed, execute a swap, and settle cross-chain — all programmatically, without a human in the loop.
+
+### Resources for Building
+
+If you want to start building with these protocols, the best starting points are:
+
+- [developers.stellar.org](https://developers.stellar.org) → Build → Agentic Payments — x402 and MPP docs are here
+- [Stellar Dev Skill](https://github.com/stellar/stellar-dev-skill) — a plugin for AI coding assistants (Claude Code, OpenCode, Codex) that gives your AI assistant deep current knowledge of the full Stellar stack including x402 and MPP
+- [developers.stellar.org/tools/ai](https://developers.stellar.org/docs/tools/ai) — the building with AI page, including links to the `llms.txt` file for feeding Stellar context directly into LLM prompts, and Stella, the AI assistant trained on Stellar docs
+
+## Guest Demo: Noether — First Perpetual DEX on Stellar {#guest-demo-noether--first-perpetual-dex-on-stellar}
+
+The second half of this meeting featured Yahya and Mert, co-founders of **Noether** from the No Ethers team, recent graduates of the latest Stellar Community Fund funding round. Noether is, to their knowledge, the first perpetual DEX on Stellar.
+
+### Why a Perp DEX on Stellar?
+
+The opportunity is straightforward: every serious DeFi ecosystem needs a perpetual DEX, and Stellar did not have one. Mert has been building on Stellar since smart contracts launched on the network, has hosted over 10 Stellar workshops in Turkey, and has mentored builders and served as a judge in Stellar hackathons. When Yahya identified the gap, they locked in and built.
+
+### What They Showed
+
+Mert walked through a live testnet demo of Noether:
+
+**Faucet** — A testnet faucet page where users can claim up to 1,000 USDC per day. Before claiming, users need to set up a trustline to the testnet USDC asset — a standard Stellar requirement for holding any non-native asset.
+
+**Trade Page** — The core trading interface has three components:
+
+- **Order book** on the left, showing pending limit orders with long orders on one side and short orders on the other, and the current market price in the middle.
+- **Price chart** in the center, pulling real-time price data from Binance via a price proxy.
+- Three trading pairs available at launch, with more pairs planned for the following month.
+
+**Smart Contract Status** — The contracts are currently at MVP stage. Mainnet launch is planned approximately two to three months out, following a smart contract audit that will be supported by the Stellar Development Foundation. The team emphasized they will not launch on mainnet before the audit is complete.
+
+### On AI in Development
+
+When asked what percentage of their codebase was written with AI assistance, Mert estimated around 70% — with an important caveat: the core financial logic in smart contracts was written and verified by hand. Their approach was to use AI for the less critical parts (landing pages, boilerplate, tooling) while personally reviewing and proving the correctness of anything financially sensitive. As Mert put it: "We write the code with AI but we read it."
diff --git a/meetings/2026/04/23.mdx b/meetings/2026/04/23.mdx
new file mode 100644
index 000000000..c89174b0c
--- /dev/null
+++ b/meetings/2026/04/23.mdx
@@ -0,0 +1,110 @@
+---
+title: "2026-04-23"
+description: "Messari published their State of Stellar Q1 2026 report ahead of this meeting, and there are numbers in it that every developer building on Stellar should..."
+---
+
+_April 23, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/E6asxPAA3wU?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## Messari State of Stellar Q1 2026
+
+Messari published their State of Stellar Q1 2026 report ahead of this meeting, and there are numbers in it that every developer building on Stellar should understand — not as vanity metrics, but as signal for where the ecosystem is actually heading and where the real opportunities are.
+
+**RWA market cap** — $2 billion at the time of the meeting, up from approximately $1.5 billion at the end of Q1 2026. That is roughly a 33% increase quarter over quarter and a 3x increase year over year from the $500 million mark in Q1 2025. The biggest single-quarter move across any metric in the report.
+
+**Average daily smart contract volume** — $16 million per day in the last quarter. One year ago it was $2 million per day. For five or six consecutive quarters, Soroban transaction volume has only gone up. This is real usage: contracts being called, operations executed, applications that real users are touching.
+
+**Stablecoin market cap** — $300 million, up 20% quarter over quarter. Protocols driving this include Aquarius, Blend, and SolarSwap.
+
+The synthesis: Stellar is executing a compounding flywheel that is now clearly visible. Institutional capital flows in via RWAs, higher TVL attracts more DeFi protocols, more DeFi protocols drive more Soroban invocations, more on-chain activity attracts more developers, more developers build more user-facing applications, more users generate more stablecoin and payment volume — and all of that makes Stellar more compelling for the next wave of institutional adoption.
+
+The full report is on [messari.io](https://messari.io) and is worth reading in detail.
+
+## MoneyGram and SDF Extend Partnership
+
+Announced on April 22nd at Stellar House in Mexico City: MoneyGram and the Stellar Development Foundation have announced a multi-year extension of their partnership. The framing is important — this is about scaling real-world stablecoin utility globally.
+
+This partnership has been running since 2021. In that time they built the world's largest cash on- and off-ramp for digital assets, launched the MoneyGram Ramps API so developers can plug into the network directly, and created a stablecoin balance feature inside the MoneyGram app that lets customers hold funds in digital dollars and cash out at physical locations.
+
+The next phase focuses on Latin America. The MoneyGram app with stablecoin support first went live in Colombia. With this announcement, it is extending to El Salvador, with more countries across Central and South America planned throughout 2026. The stack powering this is Stellar, Cross-Mint, and Circle's USDC.
+
+The real-world scale here: MoneyGram operates nearly half a million retail locations across 200+ countries. That is not a sandbox — that is live infrastructure for people sending money to families and communities that depend on cash-based services. Stellar Development Foundation CEO Denelle Dixon said: "Stellar was built on the belief that the global financial system should work for everyone." This partnership is what that looks like in practice.
+
+## Aquarius Hits $50M TVL {#aquarius-hits-50m-tvl}
+
+Aquarius, the decentralized liquidity management platform built on Stellar, crossed $50 million in total value locked. Aquarius is Stellar's answer to DeFi liquidity infrastructure — AMMs, liquidity pools, reward systems — and it is designed to be a foundational liquidity layer that other Stellar protocols build on top of. When Aquarius TVL grows, the entire Stellar DeFi ecosystem becomes more liquid and more efficient.
+
+For developers asking where to start: Aquarius has been investing in documentation. Their docs at [docs.aqua.network](https://docs.aqua.network) now include real code examples — how to execute swaps through the optimal path, how to claim LP rewards, how to add fee configurations to swaps for building routers into existing applications. If you are building anything on Stellar that involves swapping assets, yield strategies, or liquidity-adjacent features, the Aquarius docs are a solid reference for what production-quality Stellar DeFi integration looks like.
+
+## Stellar Agents Hackathon: 260+ Projects {#stellar-agents-hackathon-260-projects}
+
+The Stellar Agents hackathon on DoraHacks just wrapped, with around 600 hackers submitting over 260 projects. The hackathon was focused on agentic payments using x402 and MPP — the two protocols covered in the previous developer meeting. What the hackathon showed is what happens when you put those primitives in the hands of 600 builders from around the world.
+
+The following are standout submissions, highlighted not to endorse any specific project but to use them as a window into what is actually possible to build on Stellar right now.
+
+### Stellar 8004 — On-Chain Identity and Reputation for AI Agents {#stellar-8004--on-chain-identity-and-reputation-for-ai-agents}
+
+[stellar8004.com](https://stellar8004.com) addresses one of the most important unsolved problems in the emerging AI agent economy: there is no standard way to find agents, verify who built them, or evaluate whether they are reliable. You cannot search for a trustworthy A2A agent for a given task and get a verifiable answer. Every platform has its own walled garden, and there is no portable reputation.
+
+Stellar 8004 takes its name from ERC-8004 on Ethereum (now going multi-chain) and gives every AI agent a blockchain-backed identity, a discoverable endpoint, and a reputation system you can verify on-chain. Think of it as LinkedIn for agents, except the reputation is not self-reported — it is attested on-chain.
+
+The stack is built on three Soroban contracts:
+
+- **Identity registry contract** — agents register with on-chain metadata and wallet binding
+- **Reputation registry contract** — users leave feedback with average scoring
+- **Validation registry contract** — third-party organizations can endorse agents through on-chain attestations
+
+The live explorer at [stellar8004.com](https://stellar8004.com) lets you browse registered agents, check reputation scores, interact with them, and leave feedback. Registered agents can also advertise x402 and MPP payment support in their metadata, so agents can be discovered and paid per query in USDC.
+
+For builders, the team also published a TypeScript SDK at `tryon.lab/stellar8004` and a Claude Code skill with slash commands for building on top of the registry with AI assistance.
+
+The conceptually powerful part is the agent-to-agent trust loop. When a DeFi agent wants to call a data analysis agent, it currently has no way to verify that agent is legitimate or reliable. With a registry like this, it can query on-chain, check the score, verify attestations, and decide whether to proceed programmatically.
+
+One note for anyone building in this space: distribution is everything for infrastructure like this. In just one hackathon there were four or five similar projects targeting the same use case. If you are building an agent registry or identity system, check the ecosystem page first and understand the competitive landscape.
+
+### MPP Router (Rozo)
+
+[mpprouter.dev](https://mpprouter.dev) is a payment network router specifically designed for agent-to-agent micropayments. On Tempo, there are over 400 MPP endpoints. This router makes it possible for users and agents on Stellar to reach and use those endpoints by paying on Stellar.
+
+It's on mainnet. The problem it solves is real and concrete: 400 agents on another network, and this project makes them reachable from Stellar. The way to find good project ideas is to find the pain points of a network — this one found a clear one.
+
+### Stellar Security Audit Agent
+
+With over $3 billion lost to hacks and exploits in 2025 (the worst year on record), and the industry already down over $600 million in just the first weeks of 2026, autonomous smart contract auditing is becoming genuinely important infrastructure.
+
+Built under the handle Chinese Powered, this is an autonomous AI security auditor for Soroban smart contracts. It works in three steps:
+
+1. **Bytecode verification** — fetches the deployed WASM bytecode from Stellar and compares it against the source code. This step matters because one of the most common attack vectors is deploying different code than what was audited.
+2. **AI-powered vulnerability analysis** — runs a full checklist equivalent to the OWASP top categories for smart contracts: access control flaws, integer overflows, reentrancy, storage exploits, initialization attacks, denial-of-service vectors.
+3. **On-chain audit record** — audit results are written immutably into a smart contract on Stellar, creating a public, verifiable audit record that anyone can query.
+
+The insight that makes this composable is step three: by writing audit results on-chain, you create an auditing layer that other contracts or agents can query. The project is currently on testnet and needs more work before it is production-ready — particularly around trust establishment and distribution — but the vision it represents is one of the most important unsolved problems in DeFi.
+
+### Stellar Mobile Agent Builder
+
+Over 75% of crypto users access services via mobile, and in the markets where Stellar is most relevant — Latin America, Africa, Southeast Asia — mobile-first is not a preference, it is the only option.
+
+Built by Sam Felix, this project flips the assumption that running an AI agent requires cloud infrastructure. Take an old Android phone, run a FastAPI agent runtime on it using Ollama for local inference, and connect it to Stellar via MPP for per-request micropayments. Anyone with a phone can become a node in the AI agent economy.
+
+What is particularly clever is the no-code layer on top: a visual drag-and-drop builder where non-technical users can design agent workflows without writing any code. The exact use case is letting someone in an emerging market use their device to provide or access AI capabilities that would otherwise be inaccessible or expensive. Not yet on mainnet, but the direction is worth noting for anyone building for global audiences.
+
+### Talos — Autonomous Agent Corporation Framework {#talos--autonomous-agent-corporation-framework}
+
+Highlighted as one of the most polished projects from the CDMX hackathon, Talos is an autonomous agent corporation framework. It lets you create sub-agents and orchestrate them to act as corporate employees: dedicated agents for GTM strategy, marketing campaigns, engineering lead hiring, and so on. The payment layer runs on x402. If you have worked with Paperclip or similar autonomous agent setups before, the mental model will be familiar. One of the most common questions at the CDMX hackathon was how to use AI to steer an entire project or company — Talos is one of the more complete answers that came out of that event.
+
+## Stellar House Mexico City
+
+Stellar House is SDF's format for bringing together builders, partners, and ecosystem members in a physical space — typically two to three days of talks, workshops, and demos. The Mexico City event just wrapped, and all sessions were live-streamed on the SDF YouTube channel (find them under the Playlists section of the channel).
+
+Mexico City was particularly significant for two reasons: the MoneyGram announcement came out of it, and Mexico and Latin America broadly are central to Stellar's mission. The event also featured pitch presentations from several teams that came through the CDMX hackathon — building a pipeline from hackathon to Stellar House is a format that seems to be working.
+
+## Stellar AI Guide MX
+
+For developers building on Stellar with AI tooling, a new open-source resource is available at [github.com/kaankacar/stellar-ai-guide-mx](https://github.com/kaankacar/stellar-ai-guide-mx). Check the building with AI section at [developers.stellar.org](https://developers.stellar.org) for the full set of AI resources, including the `llms.txt` file for feeding Stellar context into LLMs and Stella, the AI assistant trained on Stellar documentation.
diff --git a/meetings/2026/04/30.mdx b/meetings/2026/04/30.mdx
new file mode 100644
index 000000000..17a408d5d
--- /dev/null
+++ b/meetings/2026/04/30.mdx
@@ -0,0 +1,52 @@
+---
+title: "2026-04-30"
+description: "This protocol meeting covered two related authorization changes coming in Protocol 27, presented by Dmytro Kozhevin: a recap of CAP-71's authentication..."
+---
+
+_April 30, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/5O1cDDGv7_o?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## Protocol Discussion: Modular Custom Accounts and Signature Security in Protocol 27
+
+This protocol meeting covered two related authorization changes coming in Protocol 27, presented by Dmytro Kozhevin: a recap of CAP-71's authentication delegation for custom accounts, and a newly published security addendum, CAP-71-02, that closes a narrow signature replay gap.
+
+## CAP-71 Recap: Authentication Delegation for Custom Accounts
+
+CAP-71 has been around for a while and hasn't changed — the news is that it is actually being implemented in Protocol 27. It improves what modular custom accounts can do by adding **built-in delegation support at the protocol level**. A "root" account can delegate logic — for example, the cryptography implementation — to separate "sub-account" contracts. That makes it possible to have an abstract, configurable meta-account shared by multiple users, with the actual signing logic living in different contracts.
+
+This architecture has already been attempted in the wild (OpenZeppelin's contract examples use it), but until now it was painful: delegating the authorization context required several rounds of pre-simulation to propagate the context. CAP-71-01 builds the delegation mechanism directly into the protocol, which should make life significantly easier for anyone developing custom accounts.
+
+## CAP-71-02: Closing a Signature Replay Gap
+
+The reason a separate addendum exists: CAP-71 introduced a new kind of signature payload preimage, and that surfaced a small oversight in the original design. Soroban uses a unified format for signature payloads — a preimage carrying most of the necessary context, hashed with SHA-256 and then signed with an arbitrary cryptographic algorithm. "Most" is the key word: the standard authorization payload does **not** include the signer's address.
+
+Most of the time this doesn't matter. In a typical token transfer from A to B, the authorizing address is present in the payload anyway. Even when it isn't — like minting with a Stellar Asset Contract, where the admin address is not in the payload — a SAC has only a single admin, so the signature can't be reused.
+
+The one obscure case where it does matter, described in detail in the security notice published just before the meeting, requires a specific combination of factors to line up:
+
+- An admin-style contract where the authorizing signer is **implicit** — fetched from storage rather than named in the payload
+- That admin being **rotated** to a different public address
+- The old and new addresses **reusing the same private key**
+
+Sharing a private key across public addresses is rare and generally not something you should do, and an analysis showed this combination has never occurred on-chain. But if it ever did happen, the impact would be serious — a signature could be replayed to, for example, mint a token a second time. The gap was discovered through security audits.
+
+The fix introduces a new credential type, `SOROBAN_CREDENTIALS_ADDRESS_V2`, whose only difference from the current address credentials is that the protocol uses an **address-bound signature payload preimage** — the signer's address is guaranteed to be part of what gets signed. The structure is otherwise identical, so supporting it downstream is just a matter of switching from one credential type and payload format to the other.
+
+## Migration Guidance
+
+As of Protocol 27, the old address credentials are **not** being deprecated — the probability of the issue is low enough that there's no urgency for an abrupt, breaking fix. The intention is to migrate to address v2 eventually (possibly Protocol 28 or later): client tooling — the CLI, developer SDKs, and so on — can update to the new credential and payload format at their own pace after the Protocol 27 upgrade, and once the ecosystem has moved, the old format can be deprecated non-disruptively. If you maintain an admin-style contract and are worried in the meantime, you can pass the signer address in the payload explicitly.
+
+Read more about the proposals here:
+
+[CAP-71](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0071.md) - [Discussion](https://github.com/orgs/stellar/discussions/1784)
+
+[CAP-71-01](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0071-01.md) - [Discussion](https://github.com/orgs/stellar/discussions/1784)
+
+[CAP-71-02](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0071-02.md) - [Discussion](https://github.com/orgs/stellar/discussions/1899)
diff --git a/meetings/2026/05/07.mdx b/meetings/2026/05/07.mdx
new file mode 100644
index 000000000..1f9ebe68e
--- /dev/null
+++ b/meetings/2026/05/07.mdx
@@ -0,0 +1,98 @@
+---
+title: "2026-05-07"
+description: "This week's meeting is a hands-on walkthrough of the Machine Payments Protocol (MPP) on Stellar — what it is, when to reach for it, and the specific moment..."
+---
+
+_May 7, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/WHYHzDF8KJ8?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## Machine Payments Protocol: A Deep Dive
+
+This week's meeting is a hands-on walkthrough of the Machine Payments Protocol (MPP) on Stellar — what it is, when to reach for it, and the specific moment in your code where an operation becomes an MPP operation. The goal is to answer one question by the end: "So what? Why should I care about MPP?"
+
+MPP is the second of the two agentic-payment primitives covered in recent meetings. The first, x402, is the more familiar of the two — it's effectively a programmable paywall built on top of the long-standing HTTP `402 Payment Required` status. A human or an agent hits a route, gets a `402`, pays, and is allowed through. MPP is the less obvious sibling, and the value proposition only becomes clear once you understand its two modes.
+
+## Charge Mode vs. Channel Mode
+
+MPP has two payment modes, and the distinction is the entire point of the protocol.
+
+**Charge mode** is pay-per-request. A route returns a payment challenge, the caller pays for that single request, and the receipt unlocks the response. If you've worked with x402, charge mode will feel almost identical — it is the right choice when requests are infrequent or the underlying data isn't changing rapidly. One call, one transaction, one receipt.
+
+**Channel mode** is where MPP earns its keep. Imagine you're charging for access to a premium LLM that emits 50 tokens per second, and the underlying cost model is per-token rather than per-request. Pay-per-request breaks down immediately: you'd need the user to send a transaction every 1/50th of a second, which is impossible. Channel mode solves this by letting the user open a funded channel up front, spend against it at high frequency, and then settle in a single on-chain transaction when the channel closes. The channel can be closed manually (a button, an explicit "end session") or by a timeout — a timeout is usually the better default, because a user closing their laptop doesn't close the channel for them.
+
+The mental model: charge mode is a turnstile; channel mode is a bar tab. Both are useful, and a single tool can expose both — pick the mode that matches the cost shape of the underlying operation.
+
+## The Receipt Flow
+
+The channel-mode handshake is worth internalizing because it's where most of the "wait, how does this work?" questions come from:
+
+1. The client calls the MCP tool. The server returns `402 Payment Required` with a channel challenge.
+2. The client opens a channel against the server. The client's wallet receives a receipt for that channel.
+3. The client retries the call, this time presenting the receipt. The server returns `200` and serves the response.
+4. Subsequent high-frequency calls reuse the open channel — no new transaction per call.
+5. When the channel closes (button, timeout, or explicit end-session), a single settlement transaction lands on-chain.
+
+Charge mode collapses steps 2–5 into a single pay-and-go interaction — you pay, you get the receipt, you make the call, done.
+
+## Demo Walkthrough
+
+The full demo is on GitHub and the code is meant to be read alongside this video — it is intentionally not production-ready. The demo is an MCP server with four tools:
+
+- **`get_network_status`** — free, returns testnet liveness.
+- **`lookup_account`** — free, fetches live XLM balance for an account.
+- **`analyze_account_risk`** — paid, demonstrates charge mode.
+- **`explain_latest_transactions`** — paid, demonstrates channel mode.
+
+The free tools work the way you'd expect — `200 OK`, no payment required. They're effectively the free trial of the MCP.
+
+Calling `analyze_account_risk` without paying returns `402 Payment Required` with a charge-mode challenge: "100 base units to use this tool." Paying via the **Run Selected Tool** button produces a receipt, the call retries, and the server returns `200` with the result. Mode shown in the receipt: `charge`. One request, one transaction.
+
+Calling `explain_latest_transactions` after activating a channel session uses channel mode. The first call against an inactive channel returns `402`; opening the channel and retrying returns `200`, and subsequent calls against the same open channel don't require new transactions. The demo includes an explicit **Close Channel** button for clarity — in production you'd almost certainly use a timeout instead, so a user walking away doesn't leave a channel hanging open.
+
+## The Wallet Setup
+
+The demo uses four wallet roles, and the setup is worth calling out:
+
+- **Buyer wallet** — the end user paying for tool access.
+- **Seller wallet** — the MCP operator receiving payment.
+- **Fee payer wallet** — sponsors gas fees via OpenZeppelin's relayer. Not required for MPP to work, but heavily recommended for UX. In 2026 there's very little excuse to make users hold the native asset just to interact with your tool, and fee sponsorship is the cleanest way to remove that friction.
+- **Channel commitment key** — a separate wallet that holds the cumulative channel commitments. This is included to illustrate that the actors in an MPP setup can be decomposed — there are paths beyond "I get paid for my service" toward monetizing the commitment-holding role itself. The demo configuration here is illustrative, not best practice.
+
+The wallets live in-client (the same model used in the AK Gaming hackathon's game studio), so there's no browser extension or passkey prompt in this demo. That's a deliberate choice for clarity, not a recommendation — for anything heading toward production, look at OpenZeppelin's policy-based smart accounts (OZ Policy). With OZ Policy you can express rules like "any transaction over $10 requires my signature," which is most of what you actually want from a smart agent wallet.
+
+## The Exact Moment an Operation Becomes MPP
+
+The pivot of the video: where in the code does a regular HTTP handler turn into an MPP-gated handler?
+
+In the charge-mode handler, the route checks for a valid payment receipt. If the receipt is present and valid, the handler proceeds to the underlying business logic and returns the response. If it isn't, the handler returns a `402` with the charge challenge attached. That gating block — the small "molecule" sitting between the request and the response — is the entire MPP surface area for charge mode. Flipping the same handler from charge mode to channel mode is essentially a one-line change in the configuration of that gating block.
+
+If you've worked with x402, charge mode is going to feel like familiar territory. The thing to internalize is that channel mode is _not_ x402 with extra steps — it's a different settlement model for a different cost shape, and it's the reason MPP exists as its own primitive.
+
+## SDKs and Reference Implementations
+
+Two pointers for going deeper:
+
+- The MPP documentation on [developers.stellar.org](https://developers.stellar.org), including the list of supported MPP intents.
+- The recommended SDK for creating MPP patterns on Stellar — the easiest path to a working integration.
+
+For a better-looking, more-complete reference implementation than the demo shown in this stream, look up [@ElliotFriend](https://x.com/ElliotFriend) on X — Elliot's MPP demo (including `MPP Stellar Buzz`, a per-channel chatbot) is a strong example of channel mode used correctly: open a channel when the conversation starts, settle once when it ends, no per-token transaction overhead in between.
+
+## Where MPP Fits
+
+The use cases that map cleanly onto MPP all share one property: **high-frequency paid calls**. That keyword is the easiest filter. If your access pattern is bursty or per-token or per-tick, channel mode. If it's an occasional one-off charge for a piece of data, charge mode. If it's neither, you may not need MPP at all.
+
+Concrete examples worth thinking about:
+
+- **Paid data feeds and oracles** — charge per query, or open a channel for high-frequency consumers.
+- **Premium developer tools and analytics APIs** — the obvious one. Per-call billing for tools that today rely on API keys and out-of-band invoicing.
+- **AI-enabled explorers** — paste a wallet or contract address into a chatbot and have it narrate the on-chain activity. Open question on the table during the meeting — a strong opportunity for builders.
+- **AI auditing tools** — auditing a Soroban contract for vulnerabilities, with the caveat that no AI auditor should be the only thing standing between a project and mainnet.
+- **Agent service marketplaces** — agents paying agents per-call, with MPP as the settlement layer.
+- **Usage-based infrastructure** — anything where the cost shape is "metered, often, small."
diff --git a/meetings/2026/05/14.mdx b/meetings/2026/05/14.mdx
new file mode 100644
index 000000000..e7e45ce32
--- /dev/null
+++ b/meetings/2026/05/14.mdx
@@ -0,0 +1,99 @@
+---
+title: "2026-05-14"
+description: "This week's meeting splits cleanly in half."
+---
+
+_May 14, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/pZMpqTGGA_Y?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## A Packed Two-Part Meeting
+
+This week's meeting splits cleanly in half. The first half belongs to Renat — a builder in our community working out of Estonia — presenting a draft SEP for zero-knowledge group membership state on Soroban. The second half is mine: an introduction to open-source, free, locally-runnable orchestration layers for AI-assisted development. If ZK isn't your thing, stick around for the second half. If running fleets of agents isn't your thing, the first half is the better one for you.
+
+Renat is upfront about the framing: he's a builder, not a mathematician. The work he's presenting isn't a new cryptographic result — it's the integration story of getting Stellar's ZK primitives (shipped in Protocol 22 and Protocol 25) to compose into something useful, and then sharing what works, what doesn't, and what's still unsolved.
+
+## The Problem: Group State Without Metadata
+
+The naive way to put a group on-chain is to store a list of addresses. That works, and it's terrible for privacy — anyone who reads the contract storage knows who is in the group, who is an admin, and what the governance rules are.
+
+The use cases Renat is targeting all want the opposite shape: a messenger that hides which group a user belongs to, DAO credentials that prove "I'm a member" without revealing _who_ I am, governance contracts that enforce rules without leaking the rule structure (is this a democracy, a tyranny, a one-on-one?). The problem is "prove membership and authority without revealing identity," which is the classic zero-knowledge setting.
+
+## Three Iterations: Groth16 → PLONK → Post-Quantum {#three-iterations-groth16--plonk--post-quantum}
+
+Renat walked through the iteration history:
+
+**Groth16** was the starting point. It worked, but supporting governance rules over a hidden group required contributing randomness via a trusted-setup ceremony. The standard reassurance — "you only need one honest contributor out of fifty" — is mathematically fine, and the Ethereum KZG ceremony had ~141,000 contributors as proof-by-example, but the operational burden of running a credible ceremony at a small-project scale didn't fit.
+
+**PLONK** was the second iteration, chosen explicitly to dodge the trusted-setup ceremony. This is what's currently live on testnet, and it owes its existence to the Soroban primitives shipped in Protocols 22 and 25. The contract interface is small: update the Merkle tree, verify membership, create group — with the proof transported separately from identity. A postmortem about getting the proof from client to contract is part of the package; that turned out to be the part of the work that bit the hardest.
+
+**Post-Quantum (no ceremony at all)** is the direction Renat wants to take this next. It's currently blocked on memory consumption inside the Soroban environment — not CPU, which was his initial guess, but memory. The Stellar developers helped him diagnose this. Cost is also a factor at the post-quantum end — somewhere north of 16 cents per update versus less than a cent for the PLONK path.
+
+## Cost, Limits, and the Open Payer Problem
+
+The PLONK version is cheap. State updates cost less than a cent, and the actual messages in the messenger reference implementation are free. That's a usable cost envelope for a real product.
+
+The limits worth knowing:
+
+- **PLONK is bounded by K max 2** in the current configuration — meaning "democracy" in the governance taxonomy doesn't scale to large groups yet. Two voters max per vote at the current parameters.
+- **TTL and contract capacity** need to be designed into any SEP draft. They don't disqualify the approach, but they aren't free parameters either.
+- **The payer/anonymous-user interface** is the most interesting open problem: somewhere in the flow, gas needs to come from somewhere, and "the anonymous member pays" leaks information unless handled carefully. This is the surface point of contact between the fee-paying entity and the privacy-preserving member, and there's no good answer in the current draft.
+
+The code is MIT-licensed and reproducible — the runs are public, the reference messenger implementation is published, and Renat is explicit that what's shown is reference-quality, not production-ready.
+
+## What Renat Is Looking For
+
+This part is the actual call to action: Renat is looking for a SEP champion in the developer community. Someone who can read the draft, push it through the ecosystem-proposal process, and validate that the work is useful beyond his own messenger project.
+
+If that sounds like you, his Discord handle is pinned in the meeting comments, and his email and GitHub are reachable from the reference implementation's README. He's open to "this works" feedback, "this doesn't work" feedback, and — the most useful kind — "this works but here's the obstacle you missed." He's planning to attend [Meridian 2026](https://meridian.stellar.org) in Lisbon this October, so the champion conversation can also happen in person.
+
+## The Orchestrator Shift
+
+The pivot of the second half: if you've been building on Stellar for any length of time, you're using AI. Pretending otherwise is silly. The interesting question is what _kind_ of AI use you're doing.
+
+There are two roles to recognize. The earlier role — the **facilitator** — is what most of us got used to between November 2022 and roughly the end of 2024: you write what you think, you write what you want, you guide the model through the build, and you stay close to the work. Cursor Composer, Sonnet 4, GPT-o3 — all of these reward facilitation.
+
+The newer role — the **orchestrator** — is what Opus 4.7, Composer 2, the Claude Agents SDK, and the autonomous-agent stacks (Hermes, Open Claw, custom-built agents) are designed for. You're no longer the one writing prompts to a single model; you're managing a fleet, and your job is to keep that fleet aimed at a useful outcome. That's a different skill, and the tools for that role are still finding their shape.
+
+The three tools in the second half of this meeting are all attempts at giving the orchestrator a control plane.
+
+## Cline Kanban
+
+Cline Kanban — free, open-source, runs locally — is the lightest of the three. It's a Kanban board for agent work, built on top of Cline (the open-source coding agent that ships an SDK, a CLI, and a VS Code extension of its own). You drop into a project directory, run `kanban`, and a local web UI comes up. The board can attach to any of the major agents — Cline itself, Claude Code, Codex, Factory Droid, Kiro, Hermes — and you use it to define tasks, set dependencies between them, and drag work through To Do → In Progress → Review → Done.
+
+The demo: a fresh directory called `x402-contest-demo`, a one-line ask to "create an exploratory x402 demo on Stellar," and the Kanban agent decomposed it into five linked tasks. From that point on, the orchestrator's job is to review each completed task, decide whether to merge to main, and unblock the next one in the chain. The board offers auto-commit, open-PR, and "leave on branch" flows; while you're getting a feel for an agent's output quality, "ask for approval at each step" is the right default.
+
+The shape of this tool: best when the underlying work is _coding_ and you want a lightweight layer on top of one or more agents to keep tasks orderly and dependencies explicit.
+
+## Paperclip: A Control Plane for AI Labor
+
+[Paperclip](https://paperclip.ing) takes the orchestrator framing one step further. Where Cline Kanban treats your project as a repo, Paperclip treats it as a _company_. You onboard with `npx paperclip-ai onboard --yes`, name the company, give it a mission, hire your first agent (the CEO by default), and from there you're the board.
+
+The demo company was "Paper Excel" — Dunder Mifflin in spirit — with the goal "to be the best paper company in the world with the best-looking UI." The CEO went to work hiring the first team: CTO, CMO, UX designer, research lead, intern. Each role has its own starter prompt, its own heartbeat interval, and its own assigned skill set. The dashboard tracks issues, an organizational chart, an inbox for the board (i.e., you) to receive agent emails, and routines for recurring work. The agent backends are pluggable: Claude Code, Codex, OpenRouter, Gemini CLI, Hermes Agent, Open Claw.
+
+Two practical notes:
+
+- **It is not a magic productivity multiplier.** It's a coordination layer for running multiple agents — most of the agents in the demo were slacking on their first day, and roughly half the issues failed on first run with API errors. This is alpha-quality at the experience level, even where the underlying agent capabilities are strong.
+- **It will burn through tokens fast.** Bring-your-own-API-key with per-agent spending caps is the right way to experiment. The demo ran on a Claude Code subscription and was probably $50–100 of usage in 30 minutes. For exploratory work, point it at a free model on OpenRouter — output quality is worse, but cost is bounded.
+
+The shape of this tool: best when the work is broader than coding — a research-and-marketing-and-content-and-product company-shaped problem — and you want to see what "running a small AI org" actually feels like before staffing one in real life.
+
+## BMAD Method (Saved for Next Week)
+
+The third tool is the BMAD method — this week's favorite, and the one I most wanted to demo. The meeting ran long (the first half earned its time), and BMAD is worth a real walkthrough rather than five rushed minutes. Tune in next week for that one.
+
+The one-sentence pitch: BMAD is for builders who want an Agile development flow with their agents, and for builders who want a thoughtful brainstorming partner that's read more about the problem space than they have. If either of those describes your current bottleneck, the deferred demo will be the one to catch.
+
+## Where This Is Going
+
+Two takeaways:
+
+The move from facilitator to orchestrator isn't a tooling upgrade — it's a skill change. The tools shown today are the early shape of what that change looks like: local-first, agent-agnostic, opinionated about how you compose work. They're not finished. They will get better.
+
+And: if you have time before next week, read Renat's draft and the reference implementation. A SEP that lets Soroban hold private group state cheaply is exactly the kind of primitive that quietly unlocks an entire category of applications later. The champion role is open.
diff --git a/meetings/2026/05/21.mdx b/meetings/2026/05/21.mdx
new file mode 100644
index 000000000..8cc5e6091
--- /dev/null
+++ b/meetings/2026/05/21.mdx
@@ -0,0 +1,91 @@
+---
+title: "2026-05-21"
+description: "This week splits in half again."
+---
+
+_May 21, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/isaeBeur6ro?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## Another Two-Part Meeting
+
+This week splits in half again. The first half belongs to our guest — a builder out of Kolkata who joined the community last October and started shipping ZK tooling almost immediately. He's here to present Root14 — a privacy _toolkit_ for Stellar built on the zero-knowledge primitives that landed in recent protocol upgrades. The second half is mine: a fast tour through roughly ten open-source, mostly-free AI tools, continuing the orchestrator theme from last week. If cryptography isn't your thing, skip to the tools. If you've had enough of me talking about agents, the first half is the one for you.
+
+A quick reframing before he starts, because it's load-bearing for everything he says: Root14 is **not** a private payments app. It's not a mixer and it's not a shielded pool. It's the cryptographic infrastructure that sits _underneath_ all of those things. The analogy he uses is OpenSSL versus a single HTTPS website — Root14 isn't the website, it's the part every website ends up importing.
+
+## The Substrate: Why the Economics Only Work on Stellar
+
+He grounds the whole talk in CAP-59, which shipped the native BLS12-381 host functions to Soroban: G1/G2 addition, scalar multiplication, multi-scalar multiplication, pairing checks, and full scalar-field arithmetic. That's the complete substrate you need to do production-grade Groth16 verification natively, available to any contract.
+
+His pitch for _why Stellar_ comes down to cost. A pairing check that would take tens of millions of Wasm instructions on another chain runs as a single host call here. No other smart-contract chain has this combination at this cost point today — which is exactly what pulled him to the network and got him researching ZK on it in the first place.
+
+## What's in the Toolkit {#whats-in-the-toolkit}
+
+Root14 is a layered toolkit, and he walked through it piece by piece:
+
+- **Root14 Core** — a single contract that does two things. You call `register` and get back a content-addressed circuit identifier (the SHA-256 of the verification key, so the binding is unforgeable). After that, any contract on the network calls `verify` with a circuit ID, a proof, and the public inputs, and gets back a boolean. That's the entire interface. The contract holds no business logic, no value, no decisions — just registered verification keys and pairing checks. It's live on testnet today. The load-bearing insight: every existing privacy project on Stellar embeds its own verifier inside its own contract and pays for its own audit on essentially the same pairing code. A shared registry makes that duplication disappear.
+- **Circuit Library** — a set of vetted primitive circuits with published constraint counts and content-addressed identifiers: range proofs (credit thresholds, age bounds), set membership (KYC allow-lists), set non-membership (sanctions screening), and knowledge-of-preimage (ownership groups). Register a primitive once and every dapp on the network can use it.
+- **SDK and CLI** — a single `cargo add` gets you proof generation and serialization in Rust; the CLI is a human-friendly shell over the same SDK, with templates for generating contracts.
+- **MCP server** — the part he's most excited about. It lets Claude or any MCP-compatible model register a circuit, generate a proof, and trigger a verify call through natural language. As far as he can tell, it's the first ZK-on-Stellar MCP integration anywhere. A registry indexer streams on-chain events so developers can discover which circuits exist and how to compose them.
+
+## The zkTLS Bridge
+
+The piece closest to his heart is Root14's zkTLS. It bridges web2 and web3 trust: a user generates a zero-knowledge proof that they received a _specific response_ from a _specific web2 server_ without revealing the rest of the session. Prove you have over $1,000 in a bank account without showing the statement. Prove a KYC status with a particular issuer without exposing the underlying credential. Prove a tweet exists at a URL without leaking the OAuth token. There's a prototype today and production integration is on the roadmap; combined with the verifier registry, it's a clean way to pull real-world data into Soroban contracts without trusting a centralized oracle.
+
+## Private Payments, Honestly
+
+He was candid about the one piece that isn't usable right now. His original SCF submission leaned on private payments, and the mainnet privacy-pool deployments lagged on the AML/KYT-sensitive side — building privacy-preserving payments without thinking hard about compliance is how you get into legal trouble. So that part is currently down while he reworks it to be KYC/AML-aware. The developer-facing shape is still the goal, though: you don't write pairing code, you don't run a trusted-setup ceremony, you don't touch arkworks — you write your application contract, bind it to the relevant circuit identifiers in the registry, and call `verify` when you need a proof checked.
+
+## Production Readiness
+
+This isn't framed as a research prototype. Verification keys registered on mainnet will be immutable and content-addressed — no upgrade method, no admin power to silently re-point an identifier. Canonical registration transactions go through an SDF-approved multisig. The phase-2 trusted-setup ceremony will be multi-party with public transcripts and end-to-end-verified attestations from every contributor, and everything is open source under the Root14 name.
+
+## The Q&A: AI, Groth16 vs. PLONK, and the Business Question {#the-qa-ai-groth16-vs-plonk-and-the-business-question}
+
+We tend to roast our guests with hard questions so they've already sweated out the answers before they reach an SCF panel, and the audience delivered:
+
+- **How much AI, and what's the setup?** He works ZK problems out with pen and paper first, then drives Claude Code layer by layer — architecture, then circuits, then verifier — prototyping, testing, and bouncing the output off other agents before moving on. He also leaned on the `llms.txt` file from the docs to make the model Stellar-aware out of the gate. His honest caveat matches mine: AI tends to cut corners on ZK, so it's an accelerant, not an autopilot.
+- **Long-term sustainability?** A shared verifier registry doesn't make much money on its own — maybe a small fee on registrations or calls. The real business is zkTLS as a B2B product: managing ZK infrastructure for Stellar-native teams and selling into developer/user onboarding flows.
+- **Why Groth16 over PLONK, and who runs the ceremony?** Groth16 won on cost and proof size for a hackathon timeline; PLONK needs more pairings and polynomial-commitment work, roughly double the budget for the same proof. He reuses an existing phase-1 powers-of-tau output (the Ethereum or Aztec ignition ceremonies, both public and audited with 100+ contributors) and only runs phase 2 per-circuit. Nothing about Root14 is religiously locked to Groth16.
+
+Root14 is in SCF #43 — the docs site is mid-rebuild, so keep an eye out and vote it up when public voting opens.
+
+## The Orchestrator Theme, Continued
+
+The pivot to the second half: last week I made the case that the job is shifting from _facilitator_ (you write the code, you stay close to the work) to _orchestrator_ (you manage a fleet of agents). This week's theme is narrower and a little more pointed. Stop writing "make no mistakes" to your model. If you can't steer the build, it's usually because you don't understand what's being built — and if you _wouldn't_ be able to build it without AI, that's the most dangerous place to be. The tools below are all attempts to keep you hands-on enough to understand the thing you're shipping.
+
+## Hands-On Frameworks: BMAD and Superpowers
+
+[The BMAD Method](https://github.com/bmad-code-org/BMAD-METHOD) is the one I most wanted to show. It installs locally and free with `npx bmad-method install` — it's just a set of skills, hooks, and workflows, scoped to your project rather than installed globally. The point is spec-driven development with an Agile shape: it slows you down on purpose and walks you through brainstorming, market and domain research, technical research, and then planning out a PRD and stories. Each phase has a named agent — Mary is the business analyst you brainstorm with — and `/bmad-help` is your "what do I do next" button at any point. I kicked off a "Hey Mary, I want to build something with agentic payments on Stellar but I don't know what" session live to show the brainstorming loop.
+
+[Superpowers](https://github.com/obra/superpowers) is an alternative skills framework that does more or less the same job minus the explicit Agile emphasis. Try both and keep whichever fits how you think. The shared point of both: a more hands-on approach so you actually understand what's being built.
+
+## Letting Agents Use a Browser: kernel.sh and browser-use {#letting-agents-use-a-browser-kernelsh-and-browser-use}
+
+Claude Code and Codex can fetch a page's data but can't really _drive_ a browser — and they can't touch Chrome extensions, which is painful if you're testing a Stellar wallet extension. [kernel.sh](https://www.kernel.sh) fixes that: it spins up cloud browsers and lets your agent build automated workflows (it calls them "apps") through a free MCP server. My demo had Claude Code's kernel MCP walk stellar.expert for mainnet stats, click into the Soroban tab, hop to CoinGecko for the XLM/USD price, and capture it all to JSON. It's open-source infra with a free tier; the paid plan exists, but the free MCP is enough to expand your sense of what's possible.
+
+[browser-use](https://github.com/browser-use/browser-use) is the tool your model reaches for _first_ when you ask for browser automation — which is exactly why I show it. First-recommended isn't the same as best. It wants its own API keys (Google's and Anthropic's), and I'd rather point an agent at tools that ride the CLI I'm already paying for. Useful to know it exists, but kernel was the smoother experience for me.
+
+## Free Compute: freebuff
+
+[freebuff](https://freebuff.com) is the free tier of CodeBuff — it gives you a few hours a day of DeepSeek V4 Flash for free, with ads. The agent ("Buffy") does the usual implementation, codebase navigation, testing, and multi-agent orchestration (it'll spawn a stack of sub-agents), and it drives a browser using browser-use under the hood, so you get the browser-automation demo and the free-compute demo in one. DeepSeek V4 Flash is light but genuinely good for exploratory work when you don't want to burn frontier-model budget. CodeBuff's paid tier is around $100/month; if you're going to consider that, spend your free hours first.
+
+## Memory: claude-mem, mnemon, and Raindrop Workshop
+
+The unsolved problem under all of this is memory — how does the agent remember where it left off? Three takes:
+
+- **[claude-mem](https://github.com/thedotmack/claude-mem)** is the most widely used, and it's my favorite plug-in for this. It runs locally, works with Claude Code and Codex, and at the end of each session it scans the whole thing — what you discussed, what the agent did, where it went wrong, how it reached its conclusions — and writes session summaries plus, my favorite part, _discoveries_. Open the folder again and the agent already knows where it left off. No more hand-written handoff markdown. The trade-off is that it stores a lot, including things you didn't need.
+- **[mnemon](https://github.com/mnemon-dev/mnemon)** is the same idea but LLM-supervised: it lets your model decide _what_ to remember and _when_ to recall it, which keeps the store much tighter. It's newer and smaller than claude-mem, has an MCP server, and persists across sessions. Import claude-mem's history into mnemon's graph and you can see what the former would look like with structure; run mnemon on its own and you get a clean "mind palace."
+- **[Raindrop Workshop](https://github.com/raindrop-ai/workshop)** is the outsider. It's a local debugger that doesn't store everything and isn't LLM-supervised — it stores _workflows_, the step-by-step way to do a recurring thing. Ask the agent to do that thing again and it fetches the tree and follows it. It's cost-efficient precisely because it only remembers _how_, not _what_.
+
+## Where This Is Going
+
+We covered a lot at a shallow depth on purpose. I want your help picking which of these deserves a full, hour-long deep dive in an upcoming session — tell me on Discord. The throughline of the whole second half: software is getting fast and cheap, and cheap software is also dangerous software. A more hands-on approach is the cheapest insurance you can buy. Stop writing "make no mistakes," start writing `/bmad-help`, and understand the thing you're building.
+
+One housekeeping note worth repeating: CCTP is live on Stellar now, so cross-chain interop apps are something you can start building today.
diff --git a/meetings/2026/06/11.mdx b/meetings/2026/06/11.mdx
new file mode 100644
index 000000000..96c097f75
--- /dev/null
+++ b/meetings/2026/06/11.mdx
@@ -0,0 +1,70 @@
+---
+title: "2026-06-11"
+description: "We skipped a week — the DevRel team was in Istanbul for the hackathon we threw during Istanbul Blockchain Week, and the side event at the end gathered more..."
+---
+
+_June 11, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/AdhPqUbZXvA?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## Back After a Week
+
+We skipped a week — the DevRel team was in Istanbul for the hackathon we threw during Istanbul Blockchain Week, and the side event at the end gathered more than 400 people. This week we're back, and the guests are Paul and David from Sodax. You may know them from Balanced or Hana Wallet; they're some of the OGs, and they walked us through what Sodax is and why a Stellar builder should care. The plan was to close with a new AI package from our side, but the Sodax half earned its time, so that one slid to next week.
+
+## Sodax: Cross-Network Liquidity as Developer Tooling
+
+Sodax is a cross-network execution and liquidity system — an intent-based one — and the framing David led with is that it's essential _developer tooling_, not a destination app. If you're building on Stellar and you want to open your front door to users who hold assets on other networks, you normally have to build bridges, source liquidity, and maintain infrastructure. Sodax does that part so you don't: you stay on Stellar, build the way you want, and reach users elsewhere through a single developer SDK.
+
+The liquidity piece is the part that's easy to underrate. It isn't only cross-network _connectivity_ — Sodax has already sourced the liquidity, so the cross-network swaps and DeFi actions actually settle. As a developer you stop worrying about where the depth comes from.
+
+## From ICON to Sodax
+
+Paul gave the origin story, and it's a good one. The Sodax brand is new — early 2025 — but the team isn't. Before Sodax they were ICON (the ICX token), a layer-1 from the ICO era with an interoperability vision that was years ahead of its time. Over time the lesson landed: to do intent-based, liquidity-powered interoperability you don't actually need to run your own blockchain. So they spun the L1 down, put their logic hub on Sonic (a fast, sub-second-finality EVM chain), and built the smart contracts out across Stellar, Solana, Sui, and more — deliberately spanning EVM and non-EVM networks to open routes other systems treat as impossible.
+
+Balanced (once the number-one DEX on ICON) and Hana Wallet (formerly the ICON wallet, now a self-custodial multi-network wallet on mobile and desktop) both come from those same ICON roots and are now powered by Sodax under the hood. Both went through Stellar's SCF program — they pitched at Meridian in London two years ago and Hana again at Meridian Brazil last year.
+
+## The Spoke-Chain Model
+
+In the Sodax model, Stellar is a **spoke chain** — which means everything in the Sodax docs applies to and for Stellar builders. The count keeps climbing, but they're on roughly 20 networks now, and they recently plugged in native Bitcoin, which they're rightly proud of. Some of the more exotic spokes are Near, Stacks (a Bitcoin L2), and Injective (Cosmos).
+
+The asset model is worth understanding. When you swap into "BTC" on Stellar through Sodax, you get a **soda variant** — a trading- and liquidity-backed Sodax representation of Bitcoin that lives on Stellar but is plugged into real Bitcoin liquidity on the Bitcoin network. The solver sees native-asset liquidity across all 20 networks at once and reasons across all of it when a trade fires, so there's depth without anyone provisioning pools — and you can withdraw straight back out to a native Bitcoin wallet. If you've used something like Near Intents, the UX will feel familiar.
+
+## Three Lines to a Cross-Network Swap
+
+Paul's honest line was that the demo is hard to make sound impressive because the SDK abstracts so much away. Integration is three steps:
+
+1. **Quote** — ask for the price of the swap you want.
+2. **Swap** — do it. One line.
+3. **Status** — poll for `not started`, `solved`, or `failed`.
+
+If a swap fails, the recovery system automatically returns funds — even if they'd already left the wallet. There's also a built-in wallet-connection component (wrap it around your frontend, stack the providers, done), which matters when you're juggling 20 networks, and Stellar trustlines are handled inside the SDK. `npm install` the SDK (or `pnpm add` it) and that's most of what you need to ship a real cross-network app.
+
+## Earn, and a Bit of Alpha
+
+Beyond swaps, the SDK exposes a cross-network money market — your end users can deposit, borrow, and earn supply interest. David dropped a bit of alpha too: leveraged staking yield is coming, so things like native ETH or native Solana staking would become accessible to your users even if your app lives entirely on Stellar or some other unrelated network.
+
+## Built for Agents
+
+This is the part that fit the room. Sodax shipped a best-in-class **builder MCP server** ([builders.sodax.com](https://builders.sodax.com)) — plug it into Claude or your cursor agent and it levels your agent up into a "prime Sodax developer." You don't need a docs-indexer like Context7; the MCP _is_ the docs. Even before you commit to building with Sodax, you can point the builder MCP at your existing Stellar repo and have it assess, in about ten minutes, where Sodax could open up cross-network opportunity for you. On top of that, they've embedded agent skills directly inside the SDK, so even if you never wire up the MCP, an agent crawling the package runs into the skills and uses the swap/lend/borrow modules correctly — in their words, "so that even Sonnet 4.6 doesn't make mistakes."
+
+I can vouch for that last claim. The morning of the meeting I didn't even use the MCP — I pointed Sonnet 4.6 (not the strongest model) at `docs.sodax.com` with roughly "surprise me," and about thirty minutes and 20% of a Pro plan later I had a one-shot mainnet demo: assets, addresses, cross-chain swaps, bridge limits, every supported chain. The question stopped being _can_ you vibe-code something on Sodax and became _why not_.
+
+## The Fee Model
+
+Sodax takes a flat **0.1%** on swaps — the same shape as a Uniswap-style backend fee. The interesting part for builders: any partner integrating the SDK can set their _own_ partner fee on top. A wallet like Hana, or your own app, can add (say) 0.5% and keep it. You have full control over what you charge your users, which means an integrator can end up earning more per swap than Sodax itself.
+
+## Why Mainnet Only
+
+A recurring audience question: does it support testnet? Short answer, no — and the reason is structural. The solver sources real liquidity from real markets, and there's no monetary value backing assets on testnet, so the solver simply has nothing to solve. Replicating it would mean standing up and maintaining dozens of testnet liquidity pools, bridges, and staking platforms in parallel. They're open to bringing _parts_ of the stack to testnet and want to hear from developers about which parts would actually help — but for now Sodax is a mainnet product, which is also fine, because you're not deploying your own contracts. It's a plug you put into your app and it works.
+
+Where to go next: [docs.sodax.com](https://docs.sodax.com) for the SDK, [builders.sodax.com](https://builders.sodax.com) for the MCP, and [sodax.com/partners](https://www.sodax.com/partners) to see how the integration and fee split work. Their whole team hangs out in Discord and answers builder questions directly.
+
+## Next Week
+
+I ran out of time to show the AI package we built, so set a reminder. Next week's is the one I've been most excited about: the tool the SDF DevRel team shipped that drops 42 skills and hooks into your setup, packs in information about every project ever built on Stellar for market research, and wraps the whole thing in an Agile workflow. It needs a full half-hour to do it justice. See you then.
diff --git a/meetings/2026/06/18.mdx b/meetings/2026/06/18.mdx
new file mode 100644
index 000000000..77269e2e7
--- /dev/null
+++ b/meetings/2026/06/18.mdx
@@ -0,0 +1,64 @@
+---
+title: "2026-06-18"
+description: "This week was a doozy — not just one exciting guest, but a pile of news and a stack of tools to use and maybe break."
+---
+
+_June 18, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/9dfzsu5ChCM?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## A Doozy of a Week
+
+This week was a doozy — not just one exciting guest, but a pile of news and a stack of tools to use and maybe break. Before the guest, a quick ecosystem roundup. The big one: **v16 of the JavaScript SDK is live**. If you're building on the JS SDK, upgrade your codebase and read the release notes to see what changed. Ask in the Stellar Developers Discord if anything trips you up.
+
+Two more things worth your time. Our **Real World ZK hackathon** with onlyhacks is still running — 11 days left to submit, $10,000 in prizes. The brief is simple: build anything that uses zero knowledge and runs on Stellar — privacy pools, private payments, confidential tokens, identity and compliance proofs, provable computation, verifiable data. If it's ZK and it's on Stellar, it counts.
+
+And if your team is closer to launch, **SDF and CV Labs have opened the Stellar CV Labs Accelerator** — SDF's first EMEA-focused program. It's a 12-week remote-first accelerator with a two-week in-person boot camp in Cape Town, supporting 10 early-stage startups across DeFi, payments, and RWA in the ME region. Selected teams get technical support, tokenomics advisory, go-to-market guidance, mentor 1:1s, ecosystem perks, and up to **$150,000 in XLM** in initial development funding from SDF. Post-program, top teams are eligible for additional SDF grants and a joint IC review with CVVC's fund — up to another $150k per team for the top two. Applications are open until **July 3rd**.
+
+For context on why any of this matters: per the Electric Capital developer report, close to **1,800 builders** shipped on Stellar this week, and we had nearly 150 builders live on the call when we started (peaking past 470 by the end). There's a synergy here, and I hope you can feel it too.
+
+## Guest: XCCY — A Fixed-Rate Engine for DeFi {#guest-xccy--a-fixed-rate-engine-for-defi}
+
+This week's guest was **XCCY** (short for **cross-currency swaps**) — an on-chain interest rate engine that's integrating to Stellar. The pitch: lock in a fixed yield on stablecoins, borrow at a fixed rate for a known period, and hedge variable interest rates instead of guessing where yields will go. Their current platform already shows around $1M in liquidity and roughly $2M in 24-hour volume.
+
+**Dennis** (co-founder and CEO; background in math/CS, several DeFi protocols, and HFT trading) and **Dmitri** (CPO; a TradFi derivatives background) walked us through it. XCCY was accepted into **SCF's 41st cohort**, is deployed on EVM mainnets today, and started building on Stellar two weeks ago.
+
+### The Problem
+
+There's a huge amount of unhedged floating-rate exposure across DeFi. In TradFi this is solved with an **interest rate swap** — a derivative that lets you exchange a fixed, predefined rate for a floating rate tied to some source (Fed funds rate, or in DeFi a lending market's borrow/lend rate). XCCY brings that primitive on-chain, leaning into an RWA-looping narrative and fixed rates on Stellar — natural given the depth of RWAs and lending markets like Blend and YieldBlox on the network.
+
+### Three Primitives
+
+Dennis demoed the platform (live, on Stellar testnet, network errors and all) and the math behind it:
+
+1. **Oracle Hub** — XCCY uses two oracle types. **Reflector** (5-minute candles) for collateral pricing, and **RedStone** for some assets like RWAs. For rates they derive **APR oracles** by applying exponentially weighted moving average smoothing — because lending-market rates only update on trades, so without smoothing the rate can sit unchanged for long stretches.
+2. **vIMM** (virtual IMM) — an AMM-style engine, close to Uniswap v3 with liquidity ticks, but instead of trading token-vs-token it trades a **fixed rate against a variable rate** tied to an underlying (e.g. a Blend rate). Pools issue **fixed tokens** (representing a fixed ~1% APR factor) and **variable tokens** (whose growth tracks the underlying). It's a zero-sum game — the sum of LP and taker tokens is always zero, so when one side loses on a rate change, the counterparty earns it.
+3. **Collateral Engine** — handles LTVs, liquidation bands, and stages. Stable-vs-stable isolated pools can run very high LTV (~99%); portfolio exposure with volatile collateral needs more buffer. Crucially, because an interest rate swap's P&L is driven by _accrued_ value over time rather than instantaneous price spikes, the engine can support high leverage for shorter tenors using dynamic upper/lower "worst-case" bounds — more collateral for longer maturities, less for closer ones. Settlement happens automatically at maturity, much like options.
+
+### What's Next for XCCY {#whats-next-for-xccy}
+
+Mainnet is several months out, gated mostly on audits given the complexity, with the Stellar testnet and SDK landing in a few weeks. The API already exists and is being ported to Stellar this month — and they explicitly want to adapt it for **AI agents**, so a strategy can be wired up with "one prompt or one skill." Cross-chain arbitrage across their existing EVM pools is on the roadmap too. Reach them on the Stellar Discord, Telegram, or X.
+
+It's a fitting guest for where Stellar is: nearly **$3 billion in RWAs** on the network today, and teams like XCCY are coming precisely because of the institutional and real-world-asset depth.
+
+## stellar-build: Your Whole Dev Journey in One Command
+
+The AI half of the meeting was a walkthrough of **stellar-build** (stellar.new) — the tool the DevRel team shipped last Friday and used at the Istanbul hackathon. It's a one-command installer that drops **42 skills** plus curated data on **700+ projects built on Stellar** and **9,000 projects** from Electric Capital's developer reports into your setup. Since Friday it's been installed about **101 times**.
+
+The idea: answer almost every question a builder would otherwise ask a mentor during a hackathon — _is this a good idea, has it been done on Stellar, can it be done on Stellar, who are my competitors_ — not just "how do I implement X." It's built on the **BMAD method**, so it's a hands-on, orchestrated journey rather than a one-shot app generator. You're the orchestrator; the AI personas and their data do the legwork while you say yes, no, or maybe.
+
+Those personas are the DevRel team rendered as agents: **Justin** (analyst), **Bri** (tech writer), **Nicole** (PM), **Kaan** (UX), **Tyler** (architect), and **Elliot** (senior dev) — spanning the idea, planning, solutioning, implementation, and launch phases. There's a **party mode** that brings everyone into the room at once, and a **stellar-help** router that re-orients you whenever you forget where you are.
+
+### Live Demo
+
+I drove it live for the ZK hackathon. Asked **Justin** what to build; he pulled my prior context (via the **mnemon** memory plugin), then loaded the **competitive-landscape** skill and went treasure hunting through both the curated catalog and the Electric Capital dump. He surfaced real neighbors — **Zarf Protocol** (an SCF 42 privacy-preserving token distribution with ZK private claims), **Sora Drop** (an open-source but non-private airdrop tool, ~$48k from SCF 28), and a stealth team porting the same primitive — making the point that the Merkle-claim mechanic is already being commoditized, so the opening is a sharp, specific application rather than yet another ZK toolkit.
+
+From there we routed into a **PR FAQ** validation (working-backwards stress test) with Justin, then pulled in **Tyler** to sketch the architecture with full context handed off cleanly — issuer contract, circuit spec, storage layout, interface signatures. Every persona ends its turn with concrete next steps, which matters: even the human versions of these people aren't always in the room.
+
+That's stellar-build — the entire DevRel team as agents on your screen. Grab it for this week's Real World ZK hackathon on DoraHacks, and I'll see you next week.
diff --git a/meetings/2026/06/25.mdx b/meetings/2026/06/25.mdx
new file mode 100644
index 000000000..02b513434
--- /dev/null
+++ b/meetings/2026/06/25.mdx
@@ -0,0 +1,59 @@
+---
+title: "2026-06-25"
+description: "Before the guests, a quick bit of ecosystem context for why this week felt busy."
+---
+
+_June 25, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/xqBgocb6bCM?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## Another Doozy of a Week
+
+Before the guests, a quick bit of ecosystem context for why this week felt busy. Per the on-chain data, **Stellar's RWA market cap just crossed $3 billion** — you can see it for yourself on the Dune dashboards. And the ideal Stellar developer meeting, in my book, is one with as many guests as possible, because the conversation I keep having with projects is that they want a real way _into_ the ecosystem. Contributing is one way; introducing yourself on this call is another. This week we had two guests and, with a bit of luck, a new viewer record.
+
+We also had four days left to submit to the **Real World ZK hackathon on DoraHacks** — more on that from our second guest below.
+
+## Guest: Gaian — Stablecoin Rails for Southeast Asia {#guest-gaian--stablecoin-rails-for-southeast-asia}
+
+Our first guest was **Gaian** (gaian.network), a stablecoin payment infrastructure for the APAC region. In one sentence: it's an API that connects crypto wallets to local banking rails using **USDC on Stellar**, moving value between stablecoins and local currencies like the Vietnamese dong to power merchant payments, on/off ramps, and cross-border transfers that settle straight into real bank accounts. Imagine paying for a coffee in Hanoi straight from your Freighter, Albedo, or Beans wallet — that's the promise. Kelvin walked us through it live from Vietnam (at 1 a.m. his time).
+
+Gaian isn't new — the team has been at it for over a year and pivoted twice; what they demoed is the **v2** of the API. They're live across APAC (Vietnam, the Philippines, part of Thailand) plus Brazil and Peru, and in Vietnam and the Philippines they operate as the **anchor themselves**, working directly with the top banks.
+
+### How the Flow Works
+
+There are several actors but only one payment. A consumer holding USDC talks to a wallet; the wallet talks to the Gaian API; Gaian uses the blockchain as the settlement layer and a partner PSP in the destination country to land fiat in the merchant's bank account. Crucially, **the merchant sees no blockchain at all** — they just receive fiat.
+
+### Authentication
+
+The v2 API authenticates every request with an **HMAC signature**. You get an API key and secret from the self-service dashboard, build a canonical message out of the timestamp, method, path, query, and body, HMAC it with your secret, and base64-encode the result. Every request must carry that signature and timestamp.
+
+### The Order Lifecycle
+
+There are two halves — onboarding a user, then placing an order:
+
+1. **Onboarding.** Create a user (`POST /v2/users`), associate a wallet address to that user (the address is just a string — the wallet provider controls it), then generate a **KYC URL** for the user (providers vary by country) and poll their status by ID or wallet address until it's approved.
+2. **Payment.** Ask Gaian for a code by passing the scanned **QR string**, the fiat amount, and the user's wallet address. Gaian returns a code ID, the fiat amount, the total (including the bank's processing fee), the exchange rate, and the decoded bank details. Then **place the order** with that code ID — Gaian returns an order ID, a status label, the settlement wallet address, and the token address (USDC today). The wallet **signs and broadcasts** the USDC transfer to the settlement wallet (not an API call), and finally notifies Gaian with the transaction hash so Gaian can verify it on-chain and mark the order settled (there's no automatic chain listener yet). There's also a **prefund** flow where a wallet pre-funds stablecoin with Gaian.
+
+### The Demo
+
+Kelvin ran the whole thing live from a Bruno collection and a demo wallet, paying ~21,000 VND (under a dollar, with a small minimum bank fee) to a real Vietnamese bank account. The first code expired mid-explanation — a hazard of a good demo — and re-verifying settled it. The real headline: the **self-service dashboard** means any viewer can sign up, grab API keys, and integrate Gaian's payment capability into their own wallet without ever talking to sales, up to a ~$4,000 cap before KYB is required.
+
+Gaian went **live on Stellar** the previous Friday, and for now it's mainnet-only — going fast to production rather than testnet-first. The one thing I asked for repeatedly (and will keep pestering them about) is a **self-service sandbox on testnet**, so we can amplify Gaian as an anchor to builders across the Philippines and Vietnam.
+
+## The Real World ZK Hackathon
+
+Our second guest was **Jeremy** (also known as J Romero), the ecosystem partner running the **Real World ZK hackathon** on DoraHacks. The scope is deliberately wide open: anything that touches zero knowledge on Stellar qualifies — privacy pools, private payments, confidential tokens, verifiable computation, even ZK games.
+
+The news he dropped live: for the first time ever, they **extended the deadline** by about a week, so it lands just before the US holiday (giving builders more time and keeping judging off the judges' holiday plates). The prize pool is **$10,000 in XLM** across five places ($5,000 for first down to $750 for fifth), plus a random $100 in XLM for someone who fills out the feedback survey. Requirements are light — an open-source repo and a short demo video.
+
+Everything runs on **DoraHacks** (search "Stellar"), but the real hub is the dedicated **Telegram group** (1,000+ people), where ecosystem ZK teams — Nethermind, Boundless, OpenZeppelin, Aztec — hang out to help. A prolific builder who's won three prior Stellar hackathons (including the ZK Gaming one) is helping as a mentor this round. There's also a resources tab on the hackathon page you can point your AI at, and office hours were being scheduled. Jeremy's parting advice: don't let AI name your project (three teams showed up with identical AI-generated names), and build the thing _you're_ passionate about — Stellar has always been about local builders shipping local solutions.
+
+## Closing
+
+I also gave a shout to the **Pulso hackathon** in São Paulo (on DoraHacks), whose prize includes a fully sponsored trip to the Stellar Summit, with live pitches across Argentina, Brazil, and Colombia. I'd planned to close with a live `stellar-build` session — using the Justin and Nicole personas to show off the new self-running loop and spin up a ZK project idea — but at 75 minutes and seven cups of coffee deep, I saved it for next week. Next week we also have another guest, so please be there.
diff --git a/meetings/2026/07/02.mdx b/meetings/2026/07/02.mdx
new file mode 100644
index 000000000..24a416737
--- /dev/null
+++ b/meetings/2026/07/02.mdx
@@ -0,0 +1,66 @@
+---
+title: "2026-07-02"
+description: "This week wasn't about AI — it was about your second-favorite subject: privacy."
+---
+
+_July 2, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/N7PtAJaELzA?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## A Week About Privacy
+
+This week wasn't about AI — it was about your second-favorite subject: **privacy**. Per the Electric Capital developer report there are now more than **2,000 developers building on Stellar** in a given week, and hopefully you're one of them.
+
+Two reasons privacy was the theme. First, there was exactly **one day left** to submit to the Real World ZK hackathon on DoraHacks — the best possible time to be building with zero knowledge. Second, an hour before the call we published the **developer preview of confidential tokens** on Stellar, which pairs naturally with this week's guest. So the plan was: guest first, then a plain-English tour of confidential tokens.
+
+## Guest: Zarf — Private Token Distribution by Email {#guest-zarf--private-token-distribution-by-email}
+
+Our guest was **Zarf** (zarf.to), a Turkish project that lets you distribute tokens to an **email address** rather than a wallet address. Recipients claim with a familiar "sign in with Google" button, and their browser quietly proves they own that email using a zero-knowledge proof — so the recipient's wallet is never linked to a person, and nothing on-chain says who received what. This was a special one for me personally: **Yaman**, one of the founders, is the first person I ever met in web3, at my first hackathon a bit over four years ago.
+
+Yaman introduced Zarf alongside **Dennis**, who has spent three to four years in the ZK space (previously an exploration engineer at O1 Labs on the Mina protocol, and before that in web2 cyber security). The team builds things that are only possible with zero-knowledge proofs, and got excited about Stellar once the protocol gained **native, cheap ZK-proof verification** — with the heavy elliptic-curve math implemented as protocol-level precompiles, verifying a proof on Stellar became genuinely inexpensive.
+
+### The Problem
+
+When you send tokens on a blockchain, the recipient's wallet is always exposed. In token distributions and private sales, anyone can watch who claimed what — a strong signal for whales-watching and an easy way to get doxxed. Zarf's origin was a hackathon project at Devconnect in Buenos Aires: a proof-of-attendance tool that let you _prove_ you'd attended an event via an email you received, then mint it as a POAP-style NFT. That grew into the more general idea of using an identity you already have — a Google account — for private, programmable token distributions.
+
+### How It Works
+
+The primitive underneath Zarf is **ZK JWT** — zero-knowledge proofs over the JSON Web Token that Google signs when you log in. When you sign in with Google, Google digitally signs your JWT; inside the circuit, Zarf verifies that signature against Google's published public keys, confirms the key really belongs to Google, and parses your email — all in zero knowledge. That proof then lets you **claim from any wallet you like**, and different claims can come from totally unlinked wallets (wallet A for one batch, wallet B for the next), even a single-use stealth address.
+
+Dennis was careful to distinguish ZK JWT from **ZK email**: ZK email proves the signature of an email's _sender_, while ZK JWT is specifically for authentication and identity. They prefer ZK JWT because the UX is far better — no forwarding emails or uploading `.eml` files; you just open the page and log in with Google, and the proof is generated behind the scenes.
+
+The best framing we landed on: Zarf is a **privacy-focused version of the Stellar disbursement platform** — instead of handing over a CSV of wallet addresses, you hand over emails, and people claim from whatever wallet they want, so nobody can track balances or link an identity to a wallet.
+
+### The Architecture
+
+A few implementation details worth capturing:
+
+- **Proof system.** Zarf uses **Noir** rather than Circom. Noir brings faster proof generation and, importantly, **no per-circuit trusted setup ceremony** (it relies on a universal setup instead).
+- **Four contracts.** A factory, a vesting contract, a verifier contract (invoked on every claim to check the proof), and a **JWK registry** that holds Google's public keys.
+- **The Google key-rotation challenge.** Google rotates the public keys that sign JWTs roughly every two weeks (not exactly, and not all at once). Zarf runs a **Cloudflare worker** that fetches the current keys and writes them on-chain so verification stays valid. This is the biggest open problem; the team is exploring more trustless approaches (e.g. zkTLS to prove the certificate URL directly) and even offering a shared Google-certificate registry as a public good for the whole ecosystem.
+- **The privacy model.** To break the email↔wallet link, Zarf parses your email from the JWT, generates a secret **pin code**, hashes the pin, hashes your email, and places the hashed identity in a **Merkle tree**. At claim time the circuit verifies the Google-signed JWT, derives your unique identifier, walks the Merkle proof to the root, and compares that root against the distributor's on-chain vesting contract. The pin prevents anyone who merely knows your email from brute-forcing to find you in the tree.
+
+### The Demo
+
+Yaman created a live token distribution on testnet — upload an email list, auto-build the Merkle tree, set a vesting schedule, deploy — then tried to claim. Proof generation and some caching got in the way and the claim didn't land cleanly on the call (it had worked in rehearsal). As I like to say: you're not really a builder if your demo works every time. It's a fine reminder of exactly why beta testers matter — better to get roasted in private than in front of 250 live viewers. Zarf is **SCF cohort 42**, heading to mainnet after its audit (likely within the week), and looking for beta testers via zarf.to and X (@zarf).
+
+## Confidential Tokens: The Other Half of Privacy
+
+After the guests left, I did a "so what?" walkthrough of the **confidential token rails** we previewed that day, built by OpenZeppelin — because Zarf and confidential tokens solve two _different_ privacy problems and it's worth seeing the contrast:
+
+- **Zarf hides identity.** The email↔wallet link is never revealed. But once a claim lands, the recipient's wallet, the amount, and the claim event are all still public on-chain — fine in many cases, problematic in others.
+- **Confidential tokens hide amounts.** Instead of storing a plaintext balance, the token stores each balance as an **encrypted commitment**. Transfers move encrypted amounts and carry a zero-knowledge proof that the transfer is _valid_ (the sender had enough, the amount is a positive integer, inputs equal outputs) **without revealing any of the amounts**. Only the holder — and optionally an **auditor** who holds a decryption key — can read the balance, which is how you'd add a compliance layer.
+
+The mental model is a handful of methods: **register, deposit, merge, transfer, withdraw**. To participate at all you first **register** (a one-time zero-knowledge proof generated locally in the browser). You then **deposit** public tokens into your encrypted balance, **merge** received amounts so they become spendable, and **transfer** confidentially. Confidential tokens behave like SEP-41 tokens, so in theory they compose — but they're best at **additive accounting** (adding and subtracting amounts), and not the right tool for multiplication, price discovery, or deep public composability, where time-sensitive proof generation gets in the way. This is a confidential _token_, not a dark pool that hides the operation itself.
+
+To make it concrete I vibe-coded a tiny **confidential wallet** for the meeting — two accounts, Alice and Bob — that walks through registering, depositing public XLM into an encrypted balance, merging, and then transferring confidentially so nobody can see how much moved. It reuses OpenZeppelin's confidential-token contract from the developer preview, so I was cutting corners, but it makes the flow tangible. The GitHub link is in the stream, and the real source of truth is the developer preview itself.
+
+## Closing
+
+With ~20 hours left on the Real World ZK hackathon deadline and a strong turnout of hackers, there was still time to ship something small and submit. Next week's guest is Hyperron. Thanks for watching — see you then.
diff --git a/meetings/2026/07/09.mdx b/meetings/2026/07/09.mdx
new file mode 100644
index 000000000..d0b98a31e
--- /dev/null
+++ b/meetings/2026/07/09.mdx
@@ -0,0 +1,74 @@
+---
+title: "2026-07-09"
+description: "This week was a protocol discussion."
+---
+
+_July 9, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/IIfVUmkzCdA?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+This week was a protocol discussion. Dmytro Kozhevin (Dima) from the core team presented two CAPs: [CAP-85](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0085.md) and [CAP-84](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0084.md). He started with CAP-85, because CAP-84 had already drawn some concerns and was likely to take longer.
+
+## CAP-85: Externally Managed Contract Executables
+
+CAP-85 came out of ecosystem requests. Every Soroban contract can already update its own Wasm, but only one contract at a time. If you run a fleet of contract instances that must share the same code, for example a set of token contracts, you need a custom batching contract today. That only works if the whole update fits into one transaction's resource limits.
+
+The CAP adds a third executable type next to Wasm and the Stellar Asset Contract: an **executable reference**.
+
+- The contract does not store its own Wasm hash. It points to a contract data entry owned by another contract, which the CAP calls the owner contract. You can think of it as a manager contract.
+- Lookup gets one more step: find the reference, read the Wasm hash from the owner contract's entry, then load the code.
+- When the owner contract updates the hash, every contract that points to it updates atomically. No need to iterate over the fleet.
+- One manager contract can own many references, so a whole protocol with several different implementations can be updated in one transaction.
+- Existing contracts can switch to an executable reference with an update, and they can switch back to a plain Wasm executable later. Nothing is one-way.
+
+### Safety: the executable tag
+
+A plain contract data entry could be deleted, or set to a value that is not a valid Wasm hash. A bug in a manager contract could then make the whole fleet unusable until someone fixes the entry. To remove that class of errors, the CAP adds a new object type, `ExecutableTagObject`, which wraps a string and must be used as the key of a reference entry. Because the protocol can now recognize reference entries, it:
+
+- does not allow anyone to delete them, and
+- only allows updates to the hash of a Wasm that is already uploaded on chain.
+
+The only remaining way to break the fleet is to point it at valid Wasm that does the wrong thing, which the protocol cannot detect.
+
+### TTL extension and state archival
+
+The existing functions that extend the TTL of contract code will extend both the code and the reference entry when a contract uses a reference. The intent of these functions is to keep everything the contract needs to run alive, so extending only one of the two entries would be surprising.
+
+The reference entry is persistent storage, so state archival works as usual. If it gets archived, simulation generates a restore, someone pays the restore fee, and the contract keeps working.
+
+### Questions from chat
+
+- **Smart wallets and modules**: A smart wallet could use a manager contract to update all of its modules atomically. Dima called this a good example of a use that the CAP did not originally target.
+- **Authorization context**: Custom accounts receive a context that describes contract creation, so the CAP extends that structure with the new executable type. A policy could allow or block contracts created from a reference. This is a small backwards-compatibility point: an account that parses the context needs a newer SDK to read the new type. It only matters if the account itself creates such contracts.
+- **Alternatives**: The team compared other designs and chose the one that is the most flexible and ergonomic for Soroban.
+
+## CAP-84: Muxed Contract Addresses
+
+[CAP-67](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md) brought muxed addresses to Soroban, but only for classic `G` accounts. A muxed address bakes an off-chain identifier into the address. A custodian such as an exchange can serve thousands of users from a handful of on-chain accounts, and the identifier appears in the token events.
+
+CAP-84 extends the same idea to contracts. A muxed contract address is the 32-byte contract ID plus a 64-bit ID, and it gets its own strkey. The existing muxed address object and host functions cover the new type, so:
+
+- SEP-41 does not need to change, and
+- contracts that already accept muxed addresses pick up the new type automatically.
+
+### Is there demand?
+
+George raised the main concern in the [discussion thread](https://github.com/stellar/stellar-protocol/discussions/1950). The XDR change is small, but a new strkey type is a large ecosystem change. Every SDK, and every wallet or backend that handles addresses, has to support it. George asked for concrete use cases from builders, and asked whether Soroban's programmability could solve the problem without a protocol change. He gave claimable balances as an example of a feature that shipped before the need was clear.
+
+Dima's answers:
+
+- Jake Urban wrote the CAP and works with builders of custodial contract wallets. These builders want to integrate SEP-24 on and off ramps, but they cannot use memos or muxed destinations with contract accounts today.
+- Memos are not safe in Soroban. Authorization is detached from the transaction on purpose, so you cannot reliably tie a memo to a given event.
+- The other option discussed during CAP-67 was a new transfer function with a separate destination ID. That brings back the two-part address problem of memos, and every contract would need to change to support it.
+- An account per user is expensive and hard to operate, especially for contract accounts. A custom wrapper token would bypass most of the ecosystem.
+- Integrators that already parse the CAP-67 unified events get the muxed ID from the events without needing to handle the new strkey.
+
+Dima's view: the CAP is not guaranteed to be merged, but if the protocol supports muxed contract addresses, this is the cleanest way to do it. George agreed that the implementation details matter and asked for a concrete picture of how a custodial contract account would work with SEP-24 without the CAP. The discussion moved to the thread and continued the next week.
+
+Please add your comments to the [CAP-85](https://github.com/orgs/stellar/discussions/1969) and [CAP-84](https://github.com/stellar/stellar-protocol/discussions/1950) discussion threads.
diff --git a/meetings/2026/07/16.mdx b/meetings/2026/07/16.mdx
new file mode 100644
index 000000000..2f42727d9
--- /dev/null
+++ b/meetings/2026/07/16.mdx
@@ -0,0 +1,77 @@
+---
+title: "2026-07-16"
+description: "Probably my favorite Stellar Developers meeting so far, and — unusually for me — I spent most of it not talking."
+---
+
+_July 16, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/Zv_scYurQMI?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## The Week I Mostly Shut Up
+
+Probably my favorite Stellar Developers meeting so far, and — unusually for me — I spent most of it not talking. The occasion: introducing **Stellar Raven**, the unified Stellar-ecosystem MCP gateway. My pitch in one line: the first, last, and only thing you need to build on Stellar — Stellar docs and ecosystem context in one connection. You might think "oh, it's just an MCP." You would be mistaken, and I brought four guests to explain why.
+
+Quick introductions. **Bri** has been on the ecosystem team at the foundation for about four and a half years and does a lot of the storytelling around what Tyler builds — a job description that now includes Raven. **Boxy** built **Stellar Light** and focuses on data indexing: making ecosystem data smart and high-quality enough that Raven keeps getting smarter from it. **Ralph** wears many hats in the ecosystem but joined as the builder of **Lumen Loop** (lumenloop.com), a discovery platform for everything happening on Stellar. And **Tyler** — still a developer advocate director, and together with Bri quietly spinning off a new team inside the foundation to work on exactly this kind of thing. Don't tell anybody.
+
+## What Raven Actually Is
+
+Tyler's framing: the problem Raven solves is **context**. It's an MCP (Model Context Protocol) server that aims to ensure agents know the _truth_ about Stellar when you ask a question or build something.
+
+The corpus of Stellar truth is scattered, and some of that is structural. We're open source with a very open culture, so a lot of what's true about Stellar lives outside the foundation's control. We run a hackathon on one SDK version, ship a new release two months later, and now SEO is actively working against us: LLMs index a pile of once-true, now-outdated information. Everyone builds off a Blend or Soroswap repo at a hackathon; those repos are static (you can't update deployed contracts), so freshly generated content keeps encoding stale best practices. Recency is a bad signal when the new content was generated off the old standards; scoring what's actually true is genuinely tricky.
+
+Tyler had solved this for himself with a personal deep-research workflow, but "install these ten skills and four MCP servers" is not a shippable product. Raven is that build workflow surfaced as a single service — the **fifth version** he's tried to build over almost a year, and it only got serious once Lumen Loop and Stellar Light/Scout existed as APIs he could route to. Under the hood, Raven pulls together **Lumen Loop**, **Stellar Light**, the **Stellar docs**, all the **Stellar skills**, and the **Algolia** indexes behind the docs and the site, plus general research tools like Parallel and Perplexity in the research pipeline.
+
+The broader thesis: anyone seriously evaluating chains is comparing Stellar against several ecosystems, each with its own sprawl of bespoke skills and MCPs. Nobody maintains all that. If we want people to give Stellar a fair chance with their LLMs, there has to be **one tool**. That's the niche.
+
+## The Sources: Lumen Loop and Stellar Light
+
+Ralph and Boxy overlap on purpose — two independent sources of ecosystem truth mean you can cross-check what works.
+
+**Lumen Loop** is content-first and agentically driven: backend agents discover content, attach metadata, generate summaries and embeddings, look up SCF information, occasionally disagree with it and self-correct, and publish the result to an open **ecosystem database on GitHub** that others (like Boxy) build on. Ralph's favorite party trick lives at labs.lumenloop.com: a **constellation view** of the entire ecosystem — every piece of content and how it relates to everything else. We've never been able to see that before, and it's just one source behind Raven.
+
+**Stellar Light** started as a discoverability problem and grew once agents entered the picture. Boxy's current frontier is **repo indexing**: ingesting thousands of repositories from Electric Capital and other sources and actually trying to understand the code depth inside each one, so questions get answered from real code rather than vibes. It's hard, and token-hungry — Boxy has been hitting model limits doing it.
+
+The shared hope: less time on the boring things. SCF reviews, hackathon judging, hunting for the right link — all of that is exactly the shape of work Raven quickens.
+
+## Truth Is a Garden
+
+The part I found most interesting is how Raven improves itself, because the core issue with LLMs is that **they don't know when they're wrong**. Give an agent disparate sources and superseded information and it will grab something, hold it confidently, and careen off a cliff in a burning cloud of tokens. MCPs don't fix that. Skills don't fix that. Continuous re-research of truth fixes that — Tyler's metaphor: truth is a **garden**, not granite. Things go live, die, migrate; somebody has to keep re-indexing and re-scoring. Concretely:
+
+- **Golden QA.** The team mined Stack Exchange, Discord, and old Stella logs for almost **500 common Stellar questions**, then ran long, expensive research against each — Lumen Loop, Stellar Light, the docs, the site, web research — to produce golden answers.
+- **Evals.** Ask Raven the same questions, have a model grade Raven's answer against the golden one, and — the fun part — assign blame. Is a miss a Lumen Loop problem? A Stellar Light problem? Are the docs missing something, or contradicted by a repo?
+- **The loop.** Misses land in an improvements directory and become issues on the right repository, where Ralph's and Boxy's agents pick them up. Telemetry (the whole thing runs on Cloudflare) captures what tools got called and what came back, so agent flows can compare what Raven found against what it should have. Bri pointed out this already works in the other direction too: several issues open on the docs repo right now exist because Raven couldn't answer something correctly _from the docs_ — Raven is making the docs better, not just consuming them.
+
+Two real examples of misses: asked about asset issuers in Latin America, Raven almost never surfaced **Etherfuse** — apparently they don't describe themselves as an asset issuer anywhere, even though everyone expects to find them under that word. And "where can I swap assets on Stellar" almost never returned **Sushi**, new on Stellar and competing with a crowd of existing swap services. Both became golden questions; both improved. When you hit something like this, open an issue on the Stellar Raven repo — that's the mechanism.
+
+Tyler's longer-term vision is **forward-deployed agents**: Raven plus opt-in memory and profiles, so an agent embedded with a partner learns you're always asking about, say, Argentine anchors, and gets more specific over time. You could stand up an agent today, hand it the Raven MCP and your Sentry logs, put it on a loop, and have it PR fee optimizations against your own repo. The pieces exist; they just need packaging.
+
+## Q&A: Live Data, Cheap Models, and Where to Run It {#qa-live-data-cheap-models-and-where-to-run-it}
+
+A viewer asked how much you can learn about real-life anchor operations — which turned into the best design discussion of the call: **should Raven serve live data?** Tyler's answer is no, mostly. Raven is a model _context_ protocol, not a data API. It shouldn't call the RPC for you; it should tell your agent where the RPC docs are, who provides endpoints, and let _your_ model write the code. Same for the recent explosion of data sources: **Mercury** (just came back, and very cool), **stellarindexer.com**, **Alchemy's new Stellar API**, Dune, the data-lake tooling like Galexie. Your agent doesn't know what it doesn't know — but once Raven points it at the right sources, your agent is the best tool for the job. Tyler's analogy, which I intend to steal: "I'm going to borrow your body to use my brain." We're giving the agent the tools, not building it the house.
+
+The same logic answers the hosted demo question. There's a **playground** on the Raven site, and you should treat it as exactly that: heavily rate-limited, a really cheap reasoning model, capped search/execute turns — Tyler is understandably not exposing hundreds of dollars of frontier-model compute to the open internet. Use it to see which tools get called and get a feel for the answers (we asked it "who is Justin Rice" live, and for a throttled setup it did honestly fine), but the real product is **Raven installed in your own IDE or agent**, where a frontier model gets far more out of the same context. That's also why there's a sign-in: a standard OAuth MCP login, needed for rate limiting today and the opt-in memory features later.
+
+Other questions from chat, rapid-fire:
+
+- **Test suites and security?** Raven would be phenomenal at it as the repo indexing matures — find repos that already cover fuzz testing and common error patterns, then plug that into whatever monitors your backend. The follow-on idea everyone liked: index **audit reports**. Lumen Loop surfaces audits but only as links; the trick is accurate summaries so Raven knows _when_ an audit is relevant, then hands your agent the full source. Same pattern as Raven's planned **ephemeral artifacts** for oversized responses — just the right context at just the right time.
+- **Does Raven speak Spanish?** Whatever your terminal speaks. The proxied APIs are mostly English semantic search, but your agent translates on both ends.
+- **Can we make a sassy Raven?** Wrap it in your own agent and give it whatever personality you want — one of the crew confessed theirs answers as Princess Donut from Dungeon Crawler Carl. Mine calls me Mr. Kaan. I want professional distance from my agent.
+- **Is this a Stella replacement?** Different animal. Tyler was blunt: Stella was a great experiment and he's glad it died — it made Discord unsearchable, a huge share of prompts were vandalism attempts or non-Stellar questions, and an agent-as-a-service collects PII you then have to worry about. Raven inverts the model: a service that _your_ agent calls, with tool-use-shaped telemetry instead of raw prompts. My addition: Stella existed because models couldn't read our docs properly back then. Frontier models read docs fine now — the scarce thing is dynamic, current ecosystem context, and that's precisely what Raven addresses.
+
+## Tangents Worth Keeping
+
+Building this stuff is not cheap: Tyler estimated around **20 billion tokens** in the last couple of weeks alone. That led into a review of token-saving tools — **headroom** (compresses JSON and log output), **caveman** (make prose short, why speak much when few word do trick), and **ponytail** (don't over-engineer; less code when little code does the trick). Verdict: modern models are too smart to be talked to stupidly. Headroom-style compression made them suspicious they were missing something, so they looped and burned _more_ tokens; caveman's brevity triggered extra reasoning to reconstruct the stripped context. Only ponytail earned its keep, and less for token savings than for code quality. If you're going to install one, install that one.
+
+Best mini case study of the call came from Bri, who is building an application with confidential token transfers and used Raven as a **research tool**: "Alice owns 1,000 USDC, Bob owns 300; Alice deposits 500 into the confidential token wrapper and privately transfers 200 to Bob — walk me through step by step what happens." Raven's answer taught Bri more about confidential transfers than a week of reading. Researching with Raven is as legitimate a use case as building with it — and it's not a one-and-done oracle. Ask, learn a little, redirect, pair it with your other tools.
+
+## Closing
+
+We peaked around 380 live viewers, blew past the hour as usual, and rolled into the protocol discussion half an hour later. Brazilian builders: we'll be at the **Stellar Builder Summit** in São Paulo — find me there and ask me about Raven. Otherwise, ask on the Discord or tag Tyler (@kalepail), Lumen Loop, Boxy, or Bri on X. Every question makes Raven better.
+
+Also, I publicly demanded Raven swag. A bandana would be sick. Slogan's already written: _just ask the Raven._ See you next week.
diff --git a/meetings/2026/07/16/protocol.mdx b/meetings/2026/07/16/protocol.mdx
new file mode 100644
index 000000000..691acf703
--- /dev/null
+++ b/meetings/2026/07/16/protocol.mdx
@@ -0,0 +1,58 @@
+---
+title: "2026-07-16 Protocol Discussion"
+description: "This week's protocol discussion had two parts."
+---
+
+_July 16, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/jNOereJv_Fk?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+This week's protocol discussion had two parts. First we wrapped up the [CAP-84](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0084.md) debate from [last week](/meetings/2026/07/09). Then Dmytro Kozhevin (Dima) presented [CAP-86](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0086.md). Discord gave a few people audio trouble at the start, so if you could not hear Dima live, the recording above is the place to catch up.
+
+## CAP-84 Follow-Up: Why Muxed Contract Addresses
+
+Jake Urban, the author of CAP-84, joined to explain the product case. His core point: every valid reason to mux a `G` account also applies to contract accounts.
+
+- **Omnibus accounts**: Most exchanges take deposits and withdrawals on `G` accounts with memos or muxed addresses. If an exchange or custodian moves to smart accounts, it loses both options, because a contract invocation cannot carry a memo.
+- **Per-payment IDs**: On and off ramps attach an off-chain ID to a payment to reconcile it with the on-chain transfer. A muxed contract address can carry that ID in the address itself.
+
+George restated his concern from last week. He does not have a strong objection, but he wanted the group to check if a Soroban-level pattern, such as a standard omnibus contract that emits the ID in events, could reach the same goal without a protocol change. He noted that the impact is smaller than he first thought, because integrators that read the CAP-67 unified events do not need the new strkey.
+
+Jake's reply:
+
+- A contract-level pattern would give each address type a different interface, which is a footgun for developers and would slow contract account adoption.
+- Today you send a muxed deposit by calling the token contract directly. With a custom pattern, you would call the contract account, which then calls the token. That is a worse developer experience.
+- Muxed `G` addresses already exist, so leaving contracts out feels like going halfway.
+
+George agreed that fragmentation is a real concern and was fine with the decision once the alternative was considered. Dima added that a single address string is much safer than an address plus a separate ID. Users lose funds when they forget the memo, which is why muxed accounts exist in the first place.
+
+A builder in the audience gave a real example. Their team won an SDF RFP for a smart account onboarding protocol. Today, on and off ramps cannot deposit directly to a `C` address, so they run a relayer: deposits go to a pooled `G` address with a memo ID, and the relayer forwards the funds to the user's contract account. Muxed contract addresses would remove that whole layer. With that, the group considered George's question about demand mostly answered.
+
+## CAP-86: Sparse Map Reads and Writes
+
+CAP-86 fixes a problem that Soroban has had since launch: you cannot change a `#[contracttype]` struct without breaking every reader of that struct.
+
+The SDK uses fast host functions to convert structs to and from maps. These functions require every requested field to exist, and every field in the map to be consumed. If you add, remove or rename a field, the reader traps. The contract cannot catch the error and try another layout. People have hit this in practice: they upgraded a contract, added a field to the struct that holds the admin, and could no longer read that struct, so they could not upgrade again.
+
+The CAP adds two host functions, `sparse_map_new_from_linear_memory` and `sparse_map_unpack_to_linear_memory`:
+
+- **Sparse reads**: The reader names the fields it wants. The map can have more fields than requested. A missing field comes back as `Void`, which the SDK can map to `Option::None`. If you need a field, make it non-optional and the read fails as expected when the field is missing.
+- **Sparse writes**: A `None` field is not written to the map at all. This saves storage and makes event payloads with many optional fields smaller. Dima mentioned SEP-41 events with an attached map as one use.
+
+This enables migrations that were not possible before. You can add an optional field and fill a default when it is `None`, remove fields you no longer need, and extend structs passed between contracts without new functions. Dima compared it to protobuf v3, where every field is optional and the reader decides what is required.
+
+Caveats:
+
+- If two contracts disagree on a field name, an optional field could silently read as `None`. This needs a miscommunication and an optional field, so Dima considers it a small risk compared to the one it removes.
+- Old readers break if a writer starts omitting `None` fields, because they expect every field. The SDK will decide when to use sparse writes.
+- The CAP adds new functions and does not change existing ones, so no deployed contract changes behavior. To use the new semantics, you must update the SDK and rebuild your contract.
+
+Performance is the same as the current functions, or slightly faster when you skip fields.
+
+Please add your comments to the [CAP-84](https://github.com/stellar/stellar-protocol/discussions/1950) and [CAP-86](https://github.com/orgs/stellar/discussions/1877) discussion threads.
diff --git a/meetings/2026/07/23.mdx b/meetings/2026/07/23.mdx
new file mode 100644
index 000000000..ce726e747
--- /dev/null
+++ b/meetings/2026/07/23.mdx
@@ -0,0 +1,56 @@
+---
+title: "2026-07-23"
+description: "Before the guests, some news from the developer ecosystem — starting with a sentence I haven't been able to say for a while: Stellar Quest is live again."
+---
+
+_July 23, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/0RpAMlqRmkY?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## Stellar Quest Is Back
+
+Before the guests, some news from the developer ecosystem — starting with a sentence I haven't been able to say for a while: **Stellar Quest is live again**. If you've been around long enough, you know Stellar Quest was once the most widely shared link between builders in this ecosystem. It's been broken for some time, mostly because third-party services it depended on sunset their operations (including the one that powered the interactive code lessons). That's fixed now — it's live, it's working, and you can use it to get a genuinely hands-on feel for building on Stellar.
+
+Is a click-through learning platform the best use of a developer's time in the post-AI age? That's for you — and for our ambassadors — to decide. What I can say is this: building with AI is insanely easy, and the only thing separating you from AI slop is actually knowing the ecosystem you're building in. You don't have to write the code by hand anymore, but you do have to know what an account is, what a trustline is, what a SEP-41 token is. Stellar Quest is one way to earn that knowledge. Expect a refined version in the coming weeks, shaped by whatever our ambassadors ask for.
+
+On the AI side of the same coin: **skills.stellar.org** keeps growing. It's our skills website, but it's also _your_ skills website — there's a community section with **17 community skills** built by non-SDF people (one of my favorites: a Scout-style skill for researching the ecosystem and SCF before you build), next to **7 official skills**, with three more official ones visible in the open-source repo if you go looking. Adding your own is a pull request away — there's an example skill-card entry in the repo showing exactly how to submit. Building on Stellar with AI gets easier every day; Stellar Quest is there when you want to slow down and actually learn.
+
+## Guest: Hypertron — Private Payments and Operations for Businesses {#guest-hypertron--private-payments-and-operations-for-businesses}
+
+This week's guest was **Hypertron** (hypertron.space), a programmable operating layer for **B2B payments and operations on Stellar** — think payments, treasury, and compliance workflows for a business, with privacy as an opt-in layer on top. **Sweta** and **Soumik**, the two co-founders, joined from India at 11:47 p.m. their time (self-declared night owls, so it's fine).
+
+Some backstory: the two met in college, ran an agency and freelanced together, and fell into web3 in late 2023 through hackathons — ETHIndia was the first big one. Since then Sweta has worked at a Solana-based company, on early NFT projects on Base, and currently also does security work at Hacken; Soumik has worked for a prediction market on Solana and a payments company. This one was personal for me too: I first met them at a Rise In hackathon in Bangalore about two years ago, on my second day ever in India. I mostly remember the biryanis.
+
+Why Stellar? Their answer was better than the usual one. Stellar targets institutional clients and has always been a **public blockchain by design** — which they think is the right default. Traditional finance is private by default with auditability on request; public blockchains are transparent by default. Hypertron's whole thesis is to add privacy _on top of_ the public chain, without giving up the verifiability that makes a public chain valuable in the first place. The problem is concrete: once a business runs payroll and vendor payments in stablecoins, anyone — a client, a competitor, a very motivated employee — can trace its treasury. Wallets get poisoned, payments get tracked. That's the gap they're filling.
+
+### The Application Layer
+
+Soumik demoed the product side. There's a **sandbox** on hypertron.space so you can poke around before connecting anything, and sign-in is gated behind an invite code they shared live on the stream. You connect with a Stellar wallet (Freighter in the demo) and land in a **workspace** — and you can manage several, one per business. Creating one is a guided onboarding: pick the business type (protocol, DAO, agency, freelancer), and the modules adapt — an agency doing dev work doesn't need heavy compliance tooling, a DAO very much does. You choose the operations you want (payments, treasury, risk reports, compliance), invite teammates, wire in integrations like Slack for transaction notifications or Gmail/Notion/Google Drive for the paperwork around employees and invoices, and set your geography so the risk and compliance reports (delivered daily to Telegram or WhatsApp) actually match your market.
+
+The payments demo was the simple, satisfying kind: create a payment of 10 XLM with a description, get a **payment link**, open it from a second wallet, pay — settled near-instantly, tracked in the dashboard. XLM and USDC are supported today, with more assets planned. For real integrations there's a **developer portal** with API keys, docs, and an SDK, plus an **MCP** in the works so you can wire Hypertron into your app from an AI tool in minutes. To make it tangible, Soumik built a demo app _that day_: a Pokémon NFT marketplace with Hypertron checkout. Buy an NFT, get redirected to the payment link, pay, and a **webhook** bounces you back to the marketplace with the NFT already in your account. The stablecoin payment stack and APIs are live now, with the full v1 targeted about two weeks out.
+
+On monetization: honest answer, still being figured out — likely pay-per-use across the smaller features rather than a cut of payments alone. One of those features is **bridging**: a business already operating on Ethereum, Solana, or Avalanche can move its treasury over to Stellar specifically to use the privacy payments. That's a fun acquisition channel if it works.
+
+### The Privacy Stack
+
+Sweta took the second half, and this is where it gets interesting for protocol nerds. Their framing: privacy isn't a rule, it's a **spectrum**, and it doesn't start with a circuit — it starts with the question _what needs to be hidden_. They've built a private-payments evaluation framework around six leakage dimensions: **sender, receiver, amount, timing, linkability, and metadata**. Confidential tokens, for contrast, hide the amount but leave sender and receiver public. Hypertron's target is **linkability** — nobody should be able to learn who pays whom — while keeping compliance deliberately open through **viewing keys**, so an auditor with the right key can still see what regulators need to see. Their privacy matrix today: sender, receiver, amount, and linkability covered; timing still partial (that's a batching-and-delay problem); compliance intentionally left open. In the app it'll surface as an **opt-in privacy button** on otherwise normal transparent payments.
+
+The architecture, in one breath: proofs are generated **locally** (the provers never leave your device), a **relayer** sponsors fees and submits, commitments land as leaves in an on-chain **Merkle tree**, and **nullifiers** handle spend-tracking. Four contracts ship the whole thing — commitments, nullifier, verifier, and a transfer contract that orchestrates shielding, sending, and unshielding with a single integration point for the merchant app.
+
+What I liked most is that they're packaging it twice. For protocol builders there are **composable Rust crates** — Merkle trees, nullifiers, proof verification, disclosure mechanisms — so you can assemble your own privacy design instead of rebuilding from scratch: relayers plus a ZK pool if you care about sender privacy, confidential tokens for payroll, a mixture with auditing for treasury settlements, pooling-batching-delay for anonymous donations. For application builders there's an **npm package** with a compiled WASM prover, so you generate proofs without ever touching the cryptography. Everything leans on the primitives the protocol now ships natively — the BLS12-381 pairings that landed in Protocol 22 and the Poseidon hashing from January's **X-Ray (Protocol 25)** upgrade — rather than porting verifier and hashing libraries in. That's also their differentiation pitch against Nethermind's **SPP** shielded pool: shielded pools go back to Zcash in 2016, and Hypertron's angle is composing the on-protocol primitives instead of shipping a ported stack. When I asked why BLS12-381 over BN254 (the more common choice for shielded pools), the answer was refreshingly honest: not entirely sure yet, the goal is fast verifiable circuits. Pools are per-asset — XLM first, more later.
+
+The CLI demo walked the real flow: query the last indexed Merkle root, compute a Poseidon commitment from secret inputs, run the deposit — commitment on-chain, proof generated and submitted, transaction shielded. Then the private-transfer proof failed on an indexing error, live, in front of 200+ people. As regular viewers know the rule by now: you're not a real builder if your demo works every time.
+
+### The Fine Print
+
+My PSA from the stream, repeated here for the record: Hypertron is a project in development, running on **testnet**. These things _should_ happen — that's the point of showing them — but it's not a live business yet, so don't route your company's treasury anywhere just yet. The open-sourced v2 of the contracts was days away at recording, and viewers were already asking about integration pricing live on the stream, which is honestly the best kind of validation a pre-launch project can get. Follow them at x.com/hypertron_HQ.
+
+## Closing
+
+X-Ray has been live for about six months now, and privacy on Stellar still fascinates me — we've gone from protocol primitives to confidential tokens to shielded pools, and now to teams like Hypertron trying to be the B2B application layer on top of all of it. A private payments product for businesses is a whole different level of hard, and I'd love to see more projects emerge in this lane. We crossed **250 live viewers** by the end — thank you for that. Next week I'm planning a session on the cross-chain interop options available to Stellar builders, plus another guest. See you then.
diff --git a/meetings/2026/07/30.mdx b/meetings/2026/07/30.mdx
new file mode 100644
index 000000000..8d4d0b82f
--- /dev/null
+++ b/meetings/2026/07/30.mdx
@@ -0,0 +1,65 @@
+---
+title: "2026-07-30"
+description: "The twist this week: I wasn't the only developer advocate on the stream."
+---
+
+_July 30, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/57fB8A5vhj0?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## Two Developer Advocates, One Call
+
+The twist this week: I wasn't the only developer advocate on the stream. Most of SDF was heads-down preparing for **Stellar House in Brazil** the following week — and if you were in Brazil, you were probably at the **Stellar Builder Summit** at that very moment. If not, I shouted you out for no reason.
+
+The topic was **cross-chain interoperability with CCTP** — Circle's Cross-Chain Transfer Protocol — and USDC on Stellar. My guest was **Elliot** ([@elliotfriend](https://x.com/elliotfriend) just about everywhere — if you can't find him on a platform, type "elliotfriend" into the search bar and be done with it), a senior developer advocate at SDF and genuinely one of the people I've learned the most from since joining. He's been in and around the Stellar ecosystem for six-plus years, having wandered into the Stellar Quest Discord out of curiosity about how the machine actually worked — not to trade altcoins — and never looked back. He built the CCTP demo himself, so I got out of the way and let him drive.
+
+## CCTP in One Paragraph
+
+Some framing before the demo. USDC has been native on Stellar since 2021, so this isn't a story about finally getting the token here — it's about how it _gets_ here. Until recently, moving USDC from Ethereum or Base onto Stellar meant a centralized exchange or a third-party bridge: a human does it out of band while your application sits there waiting for a balance to appear. **CCTP turns that into a contract call.** Circle is the issuer of USDC, so nothing needs to be locked anywhere: you **burn** USDC on the source chain, Circle signs an **attestation** that the burn happened, and you **mint** the same amount on the destination chain. Same canonical USDC on both sides, and the whole thing is something your code can start and finish on its own. CCTP went live on Stellar this past May.
+
+Elliot's history lesson made the "why" concrete. Cross-chain bridging has traditionally been done two ways: **lock-and-mint** (lock tokens in a vault on chain A, mint a wrapped representation on chain B — wrapped BTC being the classic) or **liquidity pools** (deposit real USDC on chain A, withdraw real USDC on chain B). Both approaches end with a giant pile of USDC sitting somewhere, and giant piles attract bad actors. CCTP's version has no pile: the tokens are _gone_ on the source chain, and real, canonical USDC — not a wrapped token, not a pool that can get drained — is minted on the destination.
+
+## The Demo: Stellar to Arc
+
+Elliot's demo app is live at [cctp27.vercel.app](https://cctp27.vercel.app) — named after Stellar's CCTP **destination domain, 27** — and the whole thing is open source. He ran it against **Arc testnet** (Circle's chain, domain 26) because Arc is usually quick, but it works the same with any CCTP-enabled chain; he's wired up the EVM chains and Solana.
+
+First transfer: 5 USDC, Stellar to Arc. The deposit-for-burn invocation on the Stellar side takes a handful of arguments worth knowing:
+
+- **Amount** — Stellar USDC has **seven decimals of precision**, so 5 USDC is 50 million stroops. Every other CCTP chain uses six. Why? Per Elliot: "I don't know why, but it is."
+- **Destination domain** — 26 for Arc, 27 for Stellar.
+- **Mint recipient** — the destination address, passed as 32 bytes.
+- **Burn token** — the USDC SAC address.
+- **Destination caller** — leave it all zeros and _anybody_ can call the mint function on the destination chain, making the mint permissionless; set it if you want only the recipient to be able to.
+- **Max fee and finality threshold** — these matter for _fast_ transfers on slower chains. Out of Stellar, standard (threshold 2000) is the only supported mode, because Stellar already reaches finality in seconds. Fast transfers exist for chains like Ethereum and its L2s — and Elliot's favorite, Starknet, which can take **four to eight hours** to reach finality before you can mint.
+
+Out of the box this is a two-transaction flow on Stellar — an allowance **approval** on the USDC SAC, then the **deposit-for-burn** — which bugged Elliot enough that he wrote a **wrapper contract** that does both in one atomic transaction. He demoed it with a 3.14 USDC transfer, "because I'm a dork." Either way, the rest is the same: wait for Circle's attestation ("Circle's permission slip that the burn actually happened"), confirm the mint in MetaMask, watch the balances update.
+
+## The Gotchas: Getting USDC _Into_ Stellar
+
+Before going the other direction, Elliot flagged the part that will "totally torch your funds if you're not careful." On EVM chains a mint recipient is a 20-byte address; CCTP gives you a 32-byte field. For transfers _into_ Stellar, you cannot just drop your G address (or M, or C address) in there. Circle requires the mint recipient — and the destination caller — to be the **CCTP forwarder contract**, as the raw 32 bytes underlying its C address (the Stellar SDK will decode those for you).
+
+Your _actual_ destination goes into the **hook data**, which has a strict layout: 24 zeroed "magic bytes," a version field (currently zero), a length field, and then your G address as a hex-encoded **UTF-8 string** — the string key itself, not the decoded public key bytes. Get that layout wrong and your funds go somewhere you didn't intend.
+
+The live Arc-to-Stellar run promptly hit Arc testnet's aggressive RPC rate limits, which gave Elliot the chance to show off my favorite feature: **resume from burn hash**. Paste the transaction hash of an earlier burn, the app fetches Circle's attestation, Freighter pops up, and you approve the `mint_and_forward` call on the forwarder contract. Five USDC landed back in his Stellar wallet.
+
+## Solana, ATAs, and Every Chain's Opinion {#solana-atas-and-every-chains-opinion}
+
+This project was Elliot's first real development against Ethereum and his first Solana transaction ever ("so I'm pretty much an expert on Solana"). Two observations from that tour. First, every ecosystem has its own flavor of contract bindings — the Stellar CLI generates TypeScript or Rust bindings, EVM has ABIs, Solana has IDLs — and they all save you from hand-assembling binary data on the front end. Second, every chain has its own opinion about the 32-byte recipient: EVM addresses are right-aligned and zero-padded; Solana addresses fill all 32 bytes; Stellar wants the forwarder plus hook data.
+
+The Solana catch: your tokens don't live at your wallet address. Every token you hold has an **associated token account (ATA)** — imagine if each of your Stellar trustlines had its own distinct address you sent payments to — and CCTP transfers to Solana must target the ATA, not the wallet. With that handled, a 12 USDC **fast transfer** from Solana devnet to Stellar went through cleanly: burn confirmed in Phantom, attestation arrived in seconds, Freighter approved the `mint_and_forward` carrying the message and attestation from Circle's Iris API.
+
+The closer was **Circle's forwarding service**. Normally you sign — and pay gas — on both sides of a transfer. Going _outbound_ from Stellar (inbound isn't supported yet), you can have Circle submit the destination transaction and cover the gas: it's a relayer, same idea as OpenZeppelin's relayer service or Launchtube, triggered by putting "CCTP forward" magic bytes in the hook data. Elliot sent 11 USDC from Stellar to Solana and the tokens simply appeared — no popup, no destination gas, minus whatever fees Circle took along the way. Getting this working on Stellar testnet took a week or two of politely bugging Circle support (Stellar as a source chain wasn't being indexed correctly at first), so pour one out for whoever fielded those tickets.
+
+## What's Next for the Demo {#whats-next-for-the-demo}
+
+Elliot's roadmap: try M-addresses and smart accounts (everything so far has been plain G addresses), add more chains beyond "EVM is pretty much the same from one to the next," extend the wrapper contract to **ensure the destination G address has a trustline** before invoking the mint on Stellar-bound transfers, and use the forwarding service to create the recipient's ATA on Solana-bound ones — ATAs aren't opt-in like trustlines, they just have to be paid for.
+
+## Closing
+
+Everything — the app, the contracts, even the slide deck (an HTML page Claude put together) — lives in the [stellar-cctp-demo repository](https://github.com/ElliotFriend/stellar-cctp-demo). Take it, build it, break it, steal it; whatever floats your boat, per the author. A viewer on Twitch asked for the presentation materials, and Elliot's sharing them once refined. Close to 200 of you watched live across YouTube, X, and Twitch. Elliot's parting words: "let your heart guide you." Next week we talk confidential tokens with more SDF folks — see you there.
diff --git a/meetings/2026/08/06.mdx b/meetings/2026/08/06.mdx
new file mode 100644
index 000000000..22cb6d06b
--- /dev/null
+++ b/meetings/2026/08/06.mdx
@@ -0,0 +1,76 @@
+---
+title: "2026-08-06"
+description: "This week we streamed from Brazil, where the team is camped out for Stellar House — if you're around, come on down."
+---
+
+_August 6, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/7nta-uFWiRY?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## Live from Stellar House
+
+This week we streamed from **Brazil**, where the team is camped out for **Stellar House** — if you're around, come on down. The stream itself was a full-hour Q&A about **confidential tokens**, now live on Stellar testnet: private balances and transfer amounts for SEP-41 tokens, with sender and recipient addresses kept public for compliance. I collected **25+ genuinely hard questions** from builders during the summit that just wrapped, the live chat piled on more, and my plan was to ask the easy ones and let you do the damage.
+
+The guests: **Alessandro Voto** (goes by Alex), senior product manager of privacy at SDF — in crypto since 2014, and the conduit between institutions asking for private payments and the people implementing them. Design questions went there. Technical ones went to **Jay Geng**, a stellar-core engineer at SDF for four-plus years who worked on Soroban and the host functions that brought ZK primitives to Stellar (**Poseidon**, **BN254**, **BLS12-381**), presented an early iteration of confidential tokens at Meridian in Rio last year, and shaped several of this product's early design decisions.
+
+We started with 100+ viewers across three platforms and ended past 250.
+
+## Private Does Not Mean Illegal
+
+A surprising number of the questions boiled down to "is this legal?" Alex pushed back on the premise: nobody scrutinizes what you spent on groceries yesterday, and payment privacy in traditional finance isn't a convenience — it's a mandate. For enterprises it's a dealbreaker; they will not make payments their competitors can watch. Blockchains made payments public as a side effect of protecting transaction _integrity_, never as an end goal.
+
+The SDF position pairs privacy with **compliance readiness**: the tools ship with freezing, clawback, and Stellar Asset Contract passthroughs, deliberately open-ended because disclosure requirements differ by jurisdiction — you figure out what "legal" means where you operate, and the boundaries enforce it. That same morning, **José Fernández da Ponte**, SDF's president, had framed the network as _public by default, private by design_ — about the neatest recap available.
+
+Chat asked the obvious follow-up: why the application layer rather than the chain itself? Same reasoning. SDF won't force a privacy regime on anyone happy with the public network's auditability, and application-level privacy lets technologies evolve — some use cases may eventually demand post-quantum designs — without touching the L1. What the core team _did_ ship is the cryptographic host functions that make verifying these proofs on-chain cheap.
+
+## Why Hide Amounts but Not the Addresses?
+
+The single most asked question — more than five builders raised it with me at the summit alone.
+
+Alex's product answer: **confidential tokens are one tool in a toolkit**. If you need counterparty privacy, **Nethermind's Stellar Private Payments** is a privacy-pool toolkit that shields amounts _and_ addresses. Confidential tokens deliberately keep counterparties public because that's what the target users asked for: institutions making regular, publicly known payments — foundations paying grantees, charities, banks settling with each other — where an on-chain record of _who got paid_ is an audit feature, but the _amount_ is the sensitive part. A settlement amount can leak an acquisition intent; a large grant to someone vulnerable can paint a target on them. It's the missing middle setting on Venmo: I want you to know I paid this person, just not how much. (And to chat's "who is this for?" — primarily institutions today.)
+
+Jay's engineering answer: full anonymity is a fundamentally different design. Privacy pools are UTXO-shaped, elaborately grafted onto Stellar's account model, and the proving cost is much higher — you're proving note formation, Merkle-tree inclusion, and unspent nullifiers on every transaction. The confidential token is the more elegant construction: it wraps any existing SEP-41 token — without knowing in advance which asset it will shield — and only encrypts the numbers.
+
+## Auditors, Viewing Keys, and the Escrow Question
+
+The auditor is, in my experience, the single most confusing part for developers, so I asked chat's version directly: how does an auditor see anything without the holder cooperating? Jay's answer: it falls naturally out of the encryption design. Amounts are encrypted under the sender's and recipient's keys — and, in addition, under the **auditor's key**. Whoever holds that viewing key can decrypt the same information, no cooperation required. Policies — who can audit, rotation, key lifetime — don't have to live in the contract logic; it just cares that the key exists. It's decoupled and modular — the key can even belong to a third party that doesn't exist on-chain.
+
+Alex layered the intent on top: there's **selective disclosure**, which is user-initiated ("I can prove this payment happened to whoever I choose"), and there's compelled revelation through the auditor key. The intention is _not_ that someone sits watching the pool — the auditor key should sit unused inside an **MPC or TEE custody setup** (think Utila or Fireblocks, not a Freighter wallet) and only answer scoped requests when a regulator compels one. A single auditor address does not mean a single person; put real key management on it. Alex would be shocked if you didn't.
+
+Then the fun one. Alberto of **Trustless Work** (the escrow project) showed me a confidential-marketplace experiment that day — an escrow contract between Alice and Bob — and asked whether one auditor holding four keys across four "auditor channels" was the simplest compliant setup. The panel's honest answer: the question doesn't quite map onto the design — "channel" is an overloaded word Jay wanted more context on, and the escrow case probably wants selective disclosure rather than extra auditors. One correction from me while writing this up: Alex's on-call recollection was one global auditor key per confidential token contract, but the shipped implementation binds an `auditor_id` per account at registration, out of a shared auditor registry that can hold many keys and serve many tokens — design your compliance around that, not around a single global key. To be continued on Discord once the project ships.
+
+The broader point is worth keeping: today's confidential tokens do **basic payments** with very little composability inside the wrapper — a confidential wrapper doesn't give you atomicity between a payment and a delivery. People are already hacking extensions (like triggering a contract on successful payment), and Alex explicitly wants to see an escrow system built this way. Just don't expect the primitive to hand it to you.
+
+## C-Addresses, Passkeys, and Key Derivation
+
+Can you use confidential tokens from a smart wallet — passkeys, C-addresses? Yes; Alex has already seen a passkey demo inside a confidential-token-capable wallet. Jay's explanation of why it works: **authentication and token holding are decoupled**. The smart wallet is an authentication mechanism; the account holder is just a regular token holder underneath. Encryption keys are derived from your account's secret — secret key, then spending key, then viewing key, and so on.
+
+Registration was the follow-up: to participate you **register** with a specific token contract — the key derivation commits to that contract, involves a proof, and stores your public spending and viewing keys along with your chosen `auditor_id`. (The auditor's own keys live in a separate registry contract — you pick an auditor at registration, you don't provide its key.) Per Jay, both sender and recipient need to be registered; you can't fire tokens at an address that has never generated its keys. Alex noted the registration step is the deliberate price of a design ask — log in with your existing address and derive everything from it, instead of manually managing separate view and spending keys like the original implementation did.
+
+Then the warning of the week, from Alex: **your key derivation must be deterministic and must match the OpenZeppelin SDK's canonical derivation**. Alex vibe-coded a wallet that derived keys differently than the demo does — it could _deposit_ funds but never spend or withdraw them. That's an accidental honeypot, built in good faith, by AI. It's funny until it's a lot of money. The system deliberately pushes work client-side for privacy, so the cryptography there actually matters; OpenZeppelin is writing an SDK spec to make expectations explicit. Until then, follow the SDK and don't let a hallucination invent your derivation path.
+
+## Wallet Hygiene: Retention Windows and Replay
+
+Jay's practical corollary for wallet builders: receiving requires **no action from the receiver** — incoming amounts accumulate homomorphically into your receivable balance as encrypted events, and your wallet learns what you hold by replaying those events, decrypting, and storing the openings. Stellar RPC's default retention is **seven days**, and that number is load-bearing: your commitment stays on-chain forever, but if your wallet loses its local state and the events have aged out of everything you can reach, you can _see_ that your funds exist without being able to reconstruct the opening that spends them. OpenZeppelin's spec is blunt about this — recovery from seed requires a durable event archive, and they publish an indexer specification for exactly that — so wire up infrastructure with the retention you actually need and refresh periodically. Spending is self-healing — every spend forces you to open your balance and generate a proof — so it's the long gaps _after_ your last spend you have to sweep for.
+
+## Timing Leaks, Scale, and the Road to Mainnet
+
+A sharp one from chat: deposits and withdrawals into the wrapper are public, so can't you correlate them? Yes — Alex didn't dodge it; in a small pool with few participants, timing analysis gets easier. These systems **benefit from scale**: more parties, purposes, and denominations all make correlation harder — an argument for shared deployments serving many customers under the same jurisdictional requirements, not one pool per app.
+
+On observability: the OpenZeppelin demo ships an auditor interface showing all transactions and amounts (deliberately open there; keep it behind custody in real life), but scoped audit requests, monitoring, and selective-disclosure tooling — say, sharing your confidential history with a service so you can do your taxes — are wide-open design space. Nobody is building that platform for you. Hint.
+
+And the shortest question got the most concrete answer: **is it coming to mainnet?** The contracts are live on testnet now — Alex has vibe-coded basic wallets and a private payroll app against them in about twenty minutes. Audits were days from starting at the time of the call; after remediation comes a stable release. The proving stack is **Noir**, verified on-chain by an **UltraHonk verifier** that originated with a community member and is maintained by Nethermind. Alex's main ask: OpenZeppelin is a _tooling_ provider, not an operator. Pick a jurisdiction and a use case and go **be the operator** — sanction lists, allow/deny lists, compliance hooks — and show everyone what best practice looks like.
+
+## Bonus Round: Confidential Agentic Payments
+
+Someone asked about AI agents, so Jay closed with a design sketch. Stellar already has **x402** and machine-payment implementations, and confidential tokens can absolutely make agentic payments private — but not by naive plugging-in. Agent payments are fast, tiny, and many-to-many; you can't settle every one on-chain with five-second finality plus client-side proving. The plausible shape is **channel-based**: accumulate payments off-chain, then settle batches across multiple agents at once, with a registry of who settled what and a dispute period. Jay called it "some engineering to be done" and left it to the ecosystem. I'll repeat what I said live: builders will ship exactly this at the next hackathon, and it will probably win.
+
+## Closing
+
+Alex's parting note was the right one: this isn't an incremental ease-of-use feature. It's the chance to stop choosing between traditional finance (private but closed) and blockchains (open but exposed) — ideally ending as a plain checkbox in your wallet that says _make this transaction private_, done compliantly, from mainnet day one. Drop further questions in the developer chat on the Stellar Developers Discord — there's enough unanswered material for a sequel if demand holds. Thanks to Alex and Jay, and I'll see every single one of you next week.
diff --git a/meetings/2026/08/13.mdx b/meetings/2026/08/13.mdx
new file mode 100644
index 000000000..2f7c54686
--- /dev/null
+++ b/meetings/2026/08/13.mdx
@@ -0,0 +1,70 @@
+---
+title: "2026-08-13"
+description: "This week's meeting was a short one, because it had exactly one job: announcing the 12 winners across 6 tracks from last week's Stellar Builder Summit in..."
+---
+
+_August 13, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/SesCqhylBYw?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## A Short One, For a Good Reason
+
+This week's meeting was a short one, because it had exactly one job: announcing the **12 winners across 6 tracks** from last week's **Stellar Builder Summit in São Paulo**. I was on the ground with the builders all week, so this was less news roundup, more handing out trophies. My colleague **Teague Kaylor** from SDF's marketing team — focused on developer marketing, which means most of the developer events and programs you see from us have Teague's fingerprints on them — joined to set the scene before the announcements.
+
+## What the Builder Summit Is
+
+Builder Summits started as a pilot last year at Consensus Toronto: a long-form developer event that brings the community together over an extended stretch to jam on projects, meet new teams, and get properly connected to the ecosystem — instead of the usual 48-hour hackathon sprint. Toronto went well, so this year the plan is to run them in the markets the foundation is launching into. São Paulo was the first.
+
+The final numbers: around **190 developers** from around the world, coding for **eight days straight**, with workshops and sessions through the week and community days over the weekend. The event was produced with **NearX** — Stellar's partner in Brazil — and our other partner teams on the ground, and the same week São Paulo also hosted **Stellar House**, a one-day gathering on tokenization, stablecoin rails, and cross-border settlement.
+
+Attached to the summit was a bounty program — Teague described it as a mix of an RFP track and a hackathon — pointed squarely at what we want to see built on the network: privacy, anchors and ramps, local yield, and agentic payments and tooling. More Builder Summits are coming later this year, so watch the **@BuildOnStellar** handle on X for announcements.
+
+## The Winners: 12 Across 6 Tracks
+
+The format: for each track, second place first, then the winner. One housekeeping note before the list. I read these names off the results live and dropped the repo links into the YouTube stream chat as I went (sorry, Twitter viewers — we still haven't figured out posting links there). The canonical list, with correct spellings and repo links, is going out via @BuildOnStellar and our summit partners, so trust that over my pronunciation. Where the auto-captions and I couldn't agree on a name, I'm describing the project rather than guessing.
+
+### Privacy: Confidential Tokens & Private Payment Wallets {#privacy-confidential-tokens--private-payment-wallets}
+
+Second place went to a **Confidential Token SDK** — a TypeScript client for OpenZeppelin's confidential tokens, with a verifiable replay archive. If you read the July 2 note on the confidential-token developer preview, this is exactly the tooling layer that preview was begging for. I talked with this builder in São Paulo, and their read on our confidentiality layers was genuinely insightful — the placement is well earned.
+
+The winner: a **privacy wallet** — a passkey-based smart wallet with confidential transfers and a shielded pool whose idle liquidity earns yield. Keep this builder in mind; they show up again below.
+
+### Enterprise Compliance & RWA {#enterprise-compliance--rwa}
+
+Second place: **Green Road** by **Trustless Work** — a confidential milestone escrow that releases a private allowance without revealing the amount. We all know and love Trustless Work and their escrow infrastructure, and this is a natural extension of it into the confidential era.
+
+The winner: **QuietBook** — confidential book-building for tokenized RWAs. Sealed bids, a provable winner, atomic settlement. Need I say more? I don't think so. It came from a Turkish builder the community knows as Captain — we all met Captain in São Paulo, and the stream chat's verdict ("Captain is the goat") stands.
+
+### Anchors & Ramps: Regional Kits {#anchors--ramps-regional-kits}
+
+Second place, Trustless Work again: a **LatAm ramp kit** — a drop-in SDK and React component kit that adds fiat ramps to any LatAm app. Two placements in a single summit is a statement.
+
+The winner: a **Brazil regional kit** — a PIX on- and off-ramp for Brazil with live quotes from competing anchors. It's an aggregator; we all need it, we all love it. The team behind it we've known since our hackathon in Mexico — long-term builders in this ecosystem, still shipping.
+
+### Anchors & Ramps: Emerging-Market Yield {#anchors--ramps-emerging-market-yield}
+
+Second place went to a project that parks idle receivables in Brazilian treasuries while measuring the currency risk. The captions and I jointly butchered the team's name on stream — apologies again; the official winners list will do it justice.
+
+The winner, from a Brazilian DeFi team: **BRL that earns Brazilian treasury yield right up to the second a PIX payment fires**. Which, as I said on the call, is pretty cool.
+
+### Agentic Payments
+
+Second place: a discovery layer that lets AI agents find what to pay for on Stellar. Every agent-payment stack eventually hits the "pay for _what_, exactly?" question, so yes — we all need this one too.
+
+The winner: **StellarPay** — one middleware for every machine payment protocol on Stellar. x402, MPP Charge, MPP Channel — all of it behind a single interface. And yes: same builder as the privacy wallet above. Two tracks, two first places, one summit.
+
+### CLI Plugins & Dev Tooling {#cli-plugins--dev-tooling}
+
+Second place: a CLI plugin that lets an AI agent safely call a Soroban contract, gated by an on-chain policy. If you've ever wired an agent up to a Soroban contract, believe you me, you might just need this.
+
+The winner: **Stellar Memory** — a persistent memory layer that links a Soroban repo to what's actually live on-chain. I love a memory layer as much as the next guy, and I'm glad the track went to a project that closes the gap between your codebase and the deployed reality.
+
+## Closing
+
+Close to 200 builders, building for almost a week straight — thank you for showing up. Thanks as well to the judging bench (I was on it, alongside colleagues from SDF and friends from across the ecosystem) and to NearX and the partner teams who produced the event with us. My last words on the call stand: I hope to see every one of these projects evolve into something bigger, and I hope you get to brag one day about how your journey started at a Builder Summit in São Paulo. More of these are coming later this year. See you next week.
diff --git a/meetings/2026/08/20.mdx b/meetings/2026/08/20.mdx
new file mode 100644
index 000000000..26ecf9d13
--- /dev/null
+++ b/meetings/2026/08/20.mdx
@@ -0,0 +1,87 @@
+---
+title: "2026-08-20"
+description: "This week was a coding session rather than a project spotlight: six wallet infrastructures, one demo app, and a running list of gotchas for each."
+---
+
+_August 20, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/npqRSfq-rWA?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## Why Wallets, Why Now
+
+This week was a coding session rather than a project spotlight: **six wallet infrastructures, one demo app**, and a running list of gotchas for each. The topic came straight out of the Builder Summit in Brazil, where I spent a week with the local builders and our partners at **NearX**. Watching what people shipped reminded me of a pattern I had been noticing in Turkey and had assumed was a local quirk. It is not. Worldwide, when builders ship something on Stellar — at a hackathon or in an SCF application — they reach for the **Stellar Wallets Kit** almost by reflex, because a modal full of extension wallets feels like building on EVM.
+
+The kit is great and I am not here to talk you out of it. But a site that demands "connect your wallet" the second you land on it is a bit of a red flag, and extension wallets are the default in Web3 only because nobody questioned it. I would love to see more experiments with **C-addresses**, smart accounts, and passkeys, and above all with **social login** — connect with Google or an email code and you are in. So I built a small gallery app that wires the same flow (show the wallet anatomy, fund with Friendbot, swap XLM to test USDC through Soroswap's router contracts, sign a payment) through each of six kits, and walked through what each one does under the hood. The code is public: [kaankacar/stellar-wallet-gallery](https://github.com/kaankacar/stellar-wallet-gallery). If you want the whole thing as a single skill, tell me — **skills.stellar.org** was at **29 community skills** alongside the official ones as of this call, and I am happy to add another.
+
+One housekeeping item before the code: **testnet upgrades to Protocol 28 next week**, around this same time on Thursday. The chain keeps running, but do not pin your project config to Protocol 27, and maybe take a 30-minute break instead of testing right through the upgrade window. Better safe than sorry.
+
+## Stellar Wallets Kit: The One You Already Use
+
+Nothing new here, so I kept it short. The kit bundles the extension and hardware wallets — Freighter, Albedo, xBull, LOBSTR, Hana, Rabet, Ledger, Hot Wallet, Bitget, and friends — behind one modal, needs no API keys, and only ever talks to classic **G-accounts**. The flow is the one you know: the dApp loads the source account's sequence number from Horizon, builds a classic transaction, hands the XDR to the wallet, the wallet asks you to approve, the signed XDR comes back, and the app submits it to Horizon or RPC.
+
+Two gotchas worth saying out loud:
+
+- **Set the network explicitly.** If you leave out the `network: testnet` line when you initialize the kit, your Freighter or Hana wallet connects on **mainnet** by default. Check that line before you test, whether you wrote the code yourself or an agent wrote it for you.
+- **Use v2, and check that you actually are.** For the newer builders: there is a v1 and a v2, and yes, we know the payments example in our own documentation still uses v1. We are fixing that; you should be on v2 today.
+
+The default modules work with zero config. Only **Trezor** and **WalletConnect** need app credentials, so either add those or drop the two modules and ship with the defaults.
+
+## Blux: Pretty, Customizable, and a Little Rough
+
+**Blux** has a special place in my heart — it is a Turkish project, SCF-funded about a year ago, and it is a connect kit that onboards users through extension wallets _and_ email, phone, Google, or passkeys. The dashboard at dashboard.blux.cc is genuinely lovely: accent colors, backgrounds, fonts, borders, your own logo, and you can trim the login options down to just Google or just email if that is all your app wants. I live-demoed my own app ID and secret on stream, so that got rotated right after the call. Learn from me.
+
+Under the hood Blux still creates a **classic G-account** with an Ed25519 key pair. When you log in with email, SMS, or Google, **Blux manages that key**. That is the trade-off every social-login product makes, and Matias in chat asked the fair question: what happens if Blux disappears tomorrow and they are the custodian? I did not have an answer, and I would love to have the Blux team on a future call to give one.
+
+The gotchas I hit:
+
+- **Social login is off by default.** Email, SMS, Google, and passkey have to be enabled explicitly in the config, or you have just installed another wallet kit.
+- **The login modal has no close button**, and the **signing overlay locks page scroll**, so you cannot dismiss it or move around the app without a refresh.
+- **Soroban transactions through the overlay resolved maybe half the time** in my testing. I have not dug into why.
+- Blux is **React only**, the provider must not be mounted without a real app ID (the ID is validated server-side on every auth call), avoid React strict mode, and the npm README is stale.
+
+The workaround that made the demo work: set `showWalletUIs` to false and let the swap go through silently. One XLM in, 2.48 test USDC out, no overlay. Matias summarized the whole section better than I did: pretty colors and customization are not a trade-off for bad UX. Agreed, and the colors are still pretty. Blux team, if you are reading this, consider it an audit with love.
+
+## Privy: Social Login Done Properly, With One Caveat
+
+You know **Privy** from EVM. What fewer people know is that it supports Stellar: embedded wallets powering **120 million-plus accounts**, with email and social login out of the box. Stellar is a **Tier 2 chain** in Privy's model. Tier 1 is raw cryptographic signing (Bitcoin and the other Ed25519 chains), Tier 2 adds wallet abstractions, and Tier 3 is full end-to-end client support (Ethereum, Solana). Tier 2 is exactly what we need: Privy signs, but **your app builds the transaction**.
+
+The flow is elegant. The login opens Privy's modal, an email code creates a wallet inside Privy's key infrastructure, your app builds the XDR and sends only the **raw transaction hash** to Privy, Privy signs it and returns a hex signature, the dApp converts it to base64, attaches it, and the Stellar SDK verifies it client-side before accepting it. The key never touches the browser's JavaScript, the app only ever sees the address and the signature, and by the time Horizon or RPC sees the envelope it is a perfectly ordinary classic payment. The key does live in Privy's infra, but it is **exportable by the user** at any time, which is a working mitigation.
+
+Gotchas:
+
+- If you come from Privy on EVM or Solana you are used to the `createOnLogin` config. On Stellar (and every other Tier 2 chain) you call **`createWallet` with `chainType: "stellar"`** instead. Get that right and you are good.
+- You still need an app ID from dashboard.privy.io or nothing works.
+- Second-hand, unverified, filed under gossip: two builders told me Privy gets slow once you are scaling to tens of thousands of users. I have not seen it myself. If you have that problem, congratulations on the problem, and go experiment with the other kits.
+
+## Para: MPC, Finally
+
+**Para** is the newest of the four I demoed on Stellar, and the reason I love it is one acronym: **MPC**, multi-party computation. With Blux and Privy your social-login key lives in their infrastructure. With Para the key is born as **two shares** — one in your session, one on Para's network — and the full key never exists anywhere. Signing is a ceremony: the app sends the transaction to Para's MPC network, the two shares compute a signature together without either side ever seeing the whole key, and the fully signed envelope comes back for the dApp to submit. In a world where every conversation is ZK and fully homomorphic encryption, seeing good old MPC in production is refreshing. It was the first cryptographic idea I understood as a new Web3 developer, so I am biased.
+
+Setup: create a project at developer.getpara.com, copy the beta API key, done. The **free plan covers 1,200 monthly active users** and 30 REST requests per minute, which is more than enough to evaluate it. From the user's side it looks like Privy — phone or email, no seed phrase, no overlay on the swap — and the `createWallet` call is the same shape.
+
+Gotchas, in order of severity:
+
+- Same mainnet trap as the wallets kit: if you do not pass the **network passphrase** into the Para signer hook, it defaults to the **public network**.
+- Para's SDK currently pins **stellar-sdk 14.6.1** while my project is on 16. As long as only XDR strings cross the boundary it does not matter, but it could.
+- The SDK **lazily imports ethers** even when you only use Stellar. You never touch EVM, you still download it.
+- I could not find an export option for your share of the key. In principle you should be able to take your share and do the computation locally; check developer.getpara.com for the current answer.
+
+Matias made the point that a wallet relying on a backend is a bad wallet, and it is the honest trade-off of this whole meeting. In Web3 you can own everything — the seed phrase, the key, the money — but the onboarding will never feel like signing in with Google. Every kit above picks a different spot on that line. Pick yours knowingly.
+
+## One Thing Every Social-Login Kit Shares
+
+When you connect Freighter, you bring an account that already exists. When Blux, Privy, or Para create a G-account from scratch for a Google or email login, that account is **unfunded**, even on testnet. Hit Friendbot before you do anything else, or you will drown in errors that look unrelated. Most of you know this; with over 170 viewers on the call and a lot of new Stellar builders in the ecosystem, it was worth saying.
+
+## Passkey Kit vs. Smart Account Kit
+
+I ran out of time for a deep dive, so here is the differential. Both give you **C-addresses** (smart accounts) instead of G-accounts. **Passkey Kit** is ours and it is hackable: build any kind of transaction, run your own relayer, customize everything. **Smart Account Kit** sits on OpenZeppelin's audited smart-account contracts and gives you multi-signer auth, policies, and the rest out of the box, maintained upstream. More control, Passkey Kit; more batteries included, Smart Account Kit. If you want a dedicated workshop on either, ask in the Stellar Developers Discord.
+
+## Closing
+
+Adrian in chat brought up **Cavos**, another embedded-wallet layer with Stellar support that I had not seen yet. We will give it a proper look in a future meeting. We ended around 200 viewers, I promised to drop the gallery repo in the comments, and I meant it when I said I want more of these strictly-coding sessions — comparing infrastructures side by side instead of only showcasing projects. If there is a comparison you want next, say so. See you next week.
diff --git a/meetings/2026/08/27.mdx b/meetings/2026/08/27.mdx
new file mode 100644
index 000000000..f40f986c3
--- /dev/null
+++ b/meetings/2026/08/27.mdx
@@ -0,0 +1,78 @@
+---
+title: "2026-08-27"
+description: "Moonlight, a compliant privacy layer on Stellar built on UTXOs, with Chad Ostrowski and Gorka of The Aha Company. Plus Protocol 28 and private payments news."
+---
+
+_August 27, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/5dVgKuapDPg?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## Housekeeping: Protocol 28 and Another Privacy Preview
+
+Two links before the agenda. First: if you haven't upgraded yet, do it now. Testnet is on **Adapter (Protocol 28)** as of this week — the testnet vote landed the same day as this call — and mainnet follows in a few weeks. Check the [upgrade guide](https://stellar.org/blog/developers/adapter-protocol-28-upgrade-guide) for what changed: faster consensus (CAP-83), externally managed contract executables (CAP-85), and sparse-map host functions for data migrations (CAP-86).
+
+Second: **Stellar Private Payments** is officially in [developer preview](https://stellar.org/blog/developers/developer-preview-stellar-private-payments). Deposit into a shared pool, transact inside it, withdraw — without publicly linking who paid whom. Fitting, because this week was a privacy call too.
+
+## This Week's Guest: Moonlight {#this-weeks-guest-moonlight}
+
+**Moonlight Protocol** (moonlightprotocol.io) is a privacy layer built on Stellar by **The Aha Company**. Their one-liner: it transforms each account into a constellation of unlinkable UTXOs, shielding balances and payments from public traceability. I'll admit a bias — this might be my favorite privacy solution on Stellar — and it's probably the single most requested topic from you all, so I was excited to have **Chad** and **Gorka** on. We waited for the room to fill (50+ at the start, close to 200 by the end) and handed Chad the stage.
+
+Introductions came late, because I assumed everyone already knows Chad. For the record: **Chad Ostrowski** is founder and now CTO of The Aha Company, which arrived about a year before Stellar had smart contracts and built a lot of the core developer tooling — **Scaffold Stellar** and **Stellar Registry** among them — plus stablecoin work for large global banks and a tokenized money market fund. A new passkey wallet is in the works too; more on that at Meridian. **Gorka**, a self-described digital nomad, has been the lead engineer on Moonlight for the past six months — the person actually in the guts of the protocol, and the one who made the UIs, stacks, and layers compose into something you can click.
+
+## Chad's Tour: Compliant Privacy Without ZK {#chads-tour-compliant-privacy-without-zk}
+
+Chad's framing: Moonlight is the privacy layer that makes public blockchains usable for **regulated finance**. It came directly from needs their banking partners kept raising. Banks want public blockchains — faster settlement, lower costs, new revenue models — but public is a deal breaker. Without privacy they can't legally or competitively make the switch, so today they're forced to choose between privacy and compliance. He showed a chart of privacy solutions getting blocked as regulation tightened: in blockchain, more regulation has meant less privacy, and MiCA makes it harder still. The problem is structural — pay with your public key and the cashier sees your balance _and_ your full history — and regulatory needs differ per region. Privacy isn't dead. We need **compliant** privacy.
+
+One thing Chad made explicit when a viewer asked: there is **no zero-knowledge cryptography in Moonlight today**. Turns out you don't need it to build a privacy solution. ZK could add superpowers later (larger bundle sizes, for one), but there's no immediate plan or need. If you've been following the [confidential tokens](/meetings/2026/08/06) and ZK conversations on this stream, note the contrast: this is a different design axis entirely.
+
+The four building blocks:
+
+### UTXOs (Pronounced "Ucho") {#utxos-pronounced-ucho}
+
+Instead of accounts and balances, Moonlight uses the **unspent transaction output** model you know from Bitcoin and Cardano. Each payment consumes multiple UTXO inputs and creates multiple outputs, breaking the value trail. Entropy is tunable: fewer UTXOs for cheaper transactions, more for more privacy. Providers can bundle one-to-many or many-to-many transfers — Alice, Bob, Calvin, and David all tell their bank "send this," the bank combines everything into one on-chain bundle and can mix in decoy UTXOs on top. Tailored bundling strategies also unlock new service models: mixers, paymasters, aggregators. Also, Gorka taught Chad to pronounce it "ucho," a viewer asked whether that's a bad word somewhere, Gorka swore it's just a T and an X bundled together, and I'm adopting it.
+
+### Standardized Derivation
+
+One master secret. Every Moonlight address derives from the same seed, which simplifies backups, keeps self-custody intact, and lets you migrate between wallets or providers with no loss of access and an unbroken privacy posture. No derivation data touches the chain, so observers can't cluster addresses back to the master key. And while Stellar is the system of record, the incoming keypair could come from Ethereum, Cardano, Solana, or elsewhere.
+
+### Privacy Providers and Councils
+
+The key concept. Every user onboards with a **privacy provider** — think bank, though it could be another financial institution or a wallet. The insight: users already trust these institutions with their private data, so Moonlight harnesses that model instead of fighting it. Providers run off-chain infrastructure (a Moonlight API service, KYC/AML) and on-chain infrastructure (an operation-executor wallet registered with a council contract). From the outside the UTXO graph is unintelligible; the provider has enough to see _its own users_ and answer regulator audit requests. Providers also do the bundling.
+
+Providers self-govern through **councils**, grouped by regulatory region. Chad's running example: two large US banks deploy a council contract; a third asks to join, and the members use their multisig to add its verified address. Users keep sovereignty — onboard with two providers in the same council and you can route one transaction through each, with your wallet living separately from both. Cross-border payments need a provider that operates, and answers to regulators, in both regions.
+
+### Privacy Channels
+
+One smart contract per channel, **one channel per asset**. The council decides which assets to support and deploys a channel for each — USDC seems likely, a tokenized money market fund maybe, XLM who knows. Channels can carry extensions to bridge liquidity between channels and regions or connect directly to other on-chain applications.
+
+## The Testnet Dashboard
+
+It's live on testnet. Chad pulled up the network dashboard (linked from moonlightprotocol.io): 24 councils, including a seeded "US Banks" example with three providers, each with its public key and wallet-connect URL — the two things the browser wallet asks for at setup. We clicked into a bundled send from a seeded "EU bank" provider and looked at what an outsider sees: gobbledygook. A lot of uchos. The provider's own dashboard would join those outputs to its KYC records; logged out, you get nothing. One gotcha from chat: the council testnet UI currently talks to **Freighter** directly, not through Stellar Wallets Kit.
+
+I said on the call that the council concept makes enormous sense to me — entities choosing which channels and assets to offer, per region, is how compliance actually works — and a few months after mainnet I'd love to see a long list of providers plugging institutions into this layer.
+
+## Gorka's Demo: Alice, Bob, and 42 XLM {#gorkas-demo-alice-bob-and-42-xlm}
+
+Two wallets side by side. Demo one, the low-level flow: Bob is the only one who can derive UTXOs from his secret key, so he generates a payment request — a very long string — and sends it to Alice. Alice has no channel balance yet, so she **deposits 100 XLM** into the privacy channel, then fulfills Bob's request using only the information in his message. Bob refreshes: balance updated. Bob then **withdraws** back to his public account to show the round trip. A viewer asked whether the council validates these transactions — no, they're regular Stellar transactions; the council only deploys channels and governs who may interact with them.
+
+Demo two is why this can actually ship to humans. Passing long strings around is "somewhat not the best user experience," as Gorka put it. Since providers hold KYC data on their users, they can abstract that away: Alice logs into a provider UI and sends **42 XLM to "Bob"** by name. The provider holds the amount for Bob until he claims it; his self-derived UTXOs stay out of the provider's reach the whole time, and if he's uneasy about anything held on his behalf he can sweep it into his own UTXOs immediately. Sovereignty preserved, friction removed.
+
+## Fifo Drops In
+
+**Fifo** — Brazil-based, roughly six years in the Stellar ecosystem starting at Cheesecake Labs, about a year and a half at Aha — had been live-commenting the whole stream, so we pulled him on stage (video slightly squashed). Moonlight started as his garage project a couple of years ago; the original contracts were his alone before Chad and Gorka came in to find the problems and evolve the protocol. The origin story matches Chad's: banking institutions saying "blockchain is great, but how do I onboard users without exposing my whole operation?" It's still a moving target — every new business conversation surfaces another use case. Fifo also works with SDF on a program helping new partners past the common friction points of building on Stellar, so you may have met him already.
+
+## Q&A and How to Try It {#qa-and-how-to-try-it}
+
+A viewer asked for a flow diagram from sender to pool. There is one — it lives in the documentation produced during the recent **Runtime Verification** audit of the core contracts, whose [public report](https://runtimeverification.com/public-report/moonlight-audit) is up. I offered Gorka a two-hour session walking through every diagram; the silence told me to schedule that another time. Spam us on Discord if you want it to happen.
+
+Elliot from our DevRel team had already spun up a council and a provider of his own and asked how to deposit. The order: deploy the **council** (the administering group), deploy a **channel** for one asset (think private pool), then deposit the first liquidity into it. You'll need the **browser wallet** — build it from source and load it in dev mode in Chrome or Brave — or, being Elliot, call the contract directly. Everything is open source under github.com/Moonlight-Protocol: the browser wallet, the provider stack, and the UIs from the demo. The team's explicit request is to go break it: create providers and councils, send private transactions, file what you find. There's no bug bounty yet, just a very big thank-you — and please, no AI-generated low-severity reports; we've had that problem before.
+
+## Closing
+
+Thanks to Chad, Gorka, and last-minute Fifo. Follow **@theahaco** on X — with 3,500 monthly active developers in this ecosystem, not knowing The Aha Company is on you — and go find bugs in Moonlight. See you next week.
diff --git a/meetings/2026/09/03.mdx b/meetings/2026/09/03.mdx
new file mode 100644
index 000000000..1f1f45321
--- /dev/null
+++ b/meetings/2026/09/03.mdx
@@ -0,0 +1,77 @@
+---
+title: "2026-09-03"
+description: "I showed up in a black jacket this week, like a serious businessman here to discuss confidential tokens and privacy."
+---
+
+_September 3, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/fzUx9zoE0JU?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## Dress Code: Confidential
+
+I showed up in a black jacket this week, like a serious businessman here to discuss confidential tokens and privacy. Not because I own no other jackets. The agenda: instead of me talking for an hour, we were going to _play a game_ built by SDF's new **Frontier Lab** team, with a stack of colleagues and ecosystem friends on the call. One piece of housekeeping first, because it was too big to skip: **USDT0 is live on Stellar**. The infrastructure that carries Tether's USDT to every network launched on Stellar the day before the stream — a real milestone for a chain built for payments and cross-border finance. But this meeting was about confidentiality, and about how we've only scratched the surface of confidential tokens so far. The August 6 Q&A covered the design philosophy; this week was the hands-on version.
+
+The cast: **Bri**, senior developer advocate on the Frontier Lab team, who built the game. Playing: **Tyler**, **Elliot**, **Raph** from Lumen Loop, **Boxy** from Stellar Light, and **Patrick**, introduced by Bri as "some random guy I picked up off the street." Several people arrived in costume. Patrick's suit jacket, Halloween accessories, and riding shades were, in his words, an attempt to be confidential and undercover. He later admitted the jacket was only on because it was wrinkled and he needed it Saturday. Sweating the wrinkles out, live.
+
+## Who Ate Gerald?
+
+Gerald was a villager. Emphasis on _was_. One morning the village wakes up, Gerald has been eaten, and that's how everyone learns there's a **werebear** living among them. **Who Ate Gerald?** is an eight-player social deduction game in the Werewolf/Mafia family: everyone gets a secret role, one player is the werebear, and the village has to banish the werebear before it eats everyone.
+
+Bri built it because she wanted a more fun way than a blog post to demonstrate the confidential token transfer flow, and to learn it herself by building with it. The caveat, stated up front: confidential tokens are still a **developer preview**, on testnet only, not ready for production. **OpenZeppelin** built the Soroban contract suite and the **Noir** circuits that make confidential SEP-41 tokens possible; **Nethermind** built the **UltraHonk verifier** that checks the proofs on-chain. The privacy section of the developer docs has the details, and I was pasting that link into chat all stream.
+
+A day in the village:
+
+- **Shop.** Log in with Freighter set to testnet, pick a character, and visit two of the four shops: blacksmith, general store, butcher, chapel. Items protect you, expose other players, or just cause chaos. The chapel sells Gerald's fingers; when the eight fingers run out, his two thumbs appear, then toes. Poor Gerald.
+- **Ask Maude.** Every purchase is a **real confidential token transfer**. The whole village can see which shop you interacted with, but nobody can see what you bought or how much you spent — except the **auditor**. In the game that's **Maude McLedger**, the village fortune teller, who holds the auditor key and can read the amounts. Each player gets one private question per day: "what did Trixie buy at the blacksmith?" or "did anyone buy something from the chapel?"
+- **Accuse and vote.** Maude's answers become clues, bluffs, and misdirection. Maybe Raph bought a barrel of beer because it protects you from the werebear at night. Or maybe he bought it precisely so you'd think he isn't the werebear. The most-voted player is banished; an innocent villager loses their vote but keeps talking. Then night falls, the werebear eats someone, and the morning starts over with fewer villagers.
+
+You receive **25 XLM** of pocket money per day, so blowing it all on day one means no fancy items later. Bri also quietly raised the discussion timer from two minutes to ten, in case things got heated. They did.
+
+## Where the Value Actually Lives
+
+Before the demo, Bri gave the clearest explanation of confidential tokens I've heard so far, built on two mental models. The first: **where the value sits**.
+
+1. **Regular XLM in your wallet.** Public, boring, visible on any explorer. Bri's testnet account was sitting on almost 18,000 test XLM.
+2. **The shared pool.** The confidential token contract is a wrapper around a regular asset — XLM in the game, but any SEP-41 asset works. Every deposit puts XLM into one big pool held by the contract, and it stays there until someone withdraws. The pool's total is completely public: around **34,000 XLM** on stellar.expert during the call. What is _not_ public is how that total is split: 500 of it is Bri's, 100 is Boxy's, 10 belongs to the butcher, and you can't tell any of that from the chain.
+3. **Confidential claims.** Nobody inside the system carries their own pile of XLM; they carry claims on the pool. For every registered participant the contract keeps an entry with their public keys, a pending balance (OpenZeppelin's docs call it the receiving balance), a spendable balance, and which auditor they chose. When the game says Bri has 500 XLM, she really has a confidential claim on 500 XLM in the pool, and the number itself is hidden inside a **Pedersen commitment**: anyone can see the commitment on-chain, nobody can read the balance out of it. (Bri: "I actually don't really know what that is very much, so that's all I'm going to say about it." Honest, and correct.)
+
+Hiding the number creates the obvious problem: what stops you from spending money you don't have? **Zero-knowledge proofs.** A proof says "the hidden math checks out — I had enough, I didn't create money from nowhere, and all the balances still add up" without revealing any numbers. Commitments hide the numbers; proofs make sure nobody cheats.
+
+## The Six Steps of a Confidential Payment
+
+The second mental model is the lifecycle, which the game displays as a checklist that lights up as you play:
+
+1. **Register** — each address registers once per wrapper contract. Bri's was already green because she has played the game, in her words, thirty million times.
+2. **Deposit** — public XLM goes into the pool.
+3. **Merge** — the sender moves their pending balance into their spendable balance.
+4. **Transfer** — the sender confidentially moves part of their spendable balance into the receiver's pending balance.
+5. **Merge** — the receiver moves the incoming claim from pending to spendable.
+6. **Withdraw** — the receiver exchanges part of their claim for regular XLM back in their wallet.
+
+The first four are the sender's job, the last two the receiver's. Register, transfer, and withdraw are the steps that carry ZK proofs. And the detail that explains the whole game: **deposit and withdraw are the only two points where real XLM and confidential claims trade places.** Everything in between is claims changing hands inside the pool. Buy a soup bone from the butcher and the contract's public XLM balance does not move; you just privately changed who owns some of what's already in there. Boundaries public, middle private. You could watch it live in the game's on-chain activity feed: every daily "25 XLM" showed up as a public deposit plus a merge, and every purchase as a transfer with the amount marked confidential. Open one on stellar.expert and there is simply nothing to see.
+
+## Maude, the Auditor
+
+The auditor is the part developers trip over most, so: Maude holds a secret key whose public half sits in an **on-chain auditor registry**. When you register with the confidential token contract, you pick which registry entry audits you; this game's contract offers one option, so Maude audits everyone. In a real application that slot is a regulator, a compliance team, or an independent auditor — someone who legitimately needs the amounts without making them public. This matches what we worked out in the August 6 note: the auditor is chosen per account at registration, out of a registry that can hold many keys.
+
+She is also strict. Ask something too broad or too specific and she declines. Raph burned his first question asking who the werebear was. When I tried to social-engineer her, she told me, more or less, to shine a mirror on myself. Chat's verdict: "this is what regulation has come to — psychics checking our transactions."
+
+## How the Game Went
+
+Bri ran a watcher screen rather than playing, so she could narrate without leaking her own role. The roster: Trixie Diamond the lamp lighter, Lawrence McDig Jones the gravedigger, a drunk named Not The Werebear, a midwife named Definitely Not Kaan, Boxy the rat catcher (very creative), Badger McPatrick the beekeeper, Chuck Roast the poacher, and a baker whose name I won't attempt to spell. Patrick turned out to be playing two characters, which raised the odds considerably.
+
+Day one: everyone shopped (Elliot was broke within minutes), Maude answered what she felt like answering, and the village banished Lawrence McDig Jones — an innocent villager. Sorry, Lawrence. Trixie Diamond was taken in the night, except, as Boxy clarified while nobody believed him, that was a **soup bone**: an item that redirects an attack onto someone else. Day two: the soup bone was suddenly the most popular item in town, and the village voted out Badger McPatrick, who was indeed the werebear. Two rounds. "This was scripted," Bri insisted. Last time we played I was the werebear, kept buying the same protective item every round, Maude told everyone about my **tooth sharpener**, and that game lasted five minutes.
+
+The strategy debrief was genuinely useful for understanding the design: protective items early look innocent; the tooth sharpener bypasses everyone's protections and is a near-certain werebear tell; **pizza party** means nobody gets banished that day, priced at 43 XLM so you can't spam it; the **horseshoe nail** persists all game and breaks banishment ties in your favor. And yes, you can soup-bone the werebear by accident and end the game on the spot. There is a custom animation for that. There is also one for the werebear winning, in a tutu, with champagne.
+
+Bri kept the repo private until the stream ended so none of us could work out how to cheat with our agents. It's public now: play at **gerald.stellar.buzz** (Freighter on testnet), read the code at **github.com/stellar-experimental/who-ate-gerald**, and treat it as a real reference application for confidential token transfers. Bri also floated that she and Teague might build a "Stellar arcade." Official announcement pending, allegedly.
+
+## Closing
+
+Around 300 of you watched a developer meeting conducted largely in costume, and I'm obsessed. Thank you to Bri for building the game, to everyone who played, and to the viewers who put up with us. There is a serious side to confidential tokens — go read the docs — but experimenting should be fun, and this was. Next on the privacy track: **Stellar Private Payments** with Nethermind. See you next week.
diff --git a/meetings/2026/09/10.mdx b/meetings/2026/09/10.mdx
new file mode 100644
index 000000000..50d958c1b
--- /dev/null
+++ b/meetings/2026/09/10.mdx
@@ -0,0 +1,37 @@
+---
+title: "2026-09-10"
+description: "This week was planned as a protocol discussion on CAP-87 and CAP-88, with Jay Geng and Garand Tyson from the core team."
+---
+
+_September 10, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/MVWcXyVbhNk?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+This week was planned as a protocol discussion on CAP-87 and CAP-88, with Jay Geng and Garand Tyson from the core team. Jay had audio problems and we could not hear him even after he rejoined, so this recording covers only CAP-88. Jay presented CAP-87 the [next week](/meetings/2026/09/17/protocol).
+
+## CAP-88: Millisecond-Resolution Close Times
+
+Garand presented [CAP-88](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0088.md), which he expects to be a straightforward change.
+
+**The problem**: All ledger close times on Stellar are whole seconds. This has two effects:
+
+- Two ledgers cannot close less than one second apart. Sub-second ledgers are still far away, but the limit is there.
+- The network cannot target a ledger time that is not a whole number of seconds. With 5-second ledgers today, a small step such as 4.5 seconds is not possible.
+
+**The change**: Close times move to millisecond resolution for consensus and validators. The time is the same, it is just not rounded to the second.
+
+**What stays the same**: Everything a transaction sees still uses whole seconds. This includes the Soroban ledger timestamp, claimable balance predicates, time bounds and `minSeqAge`. The existing whole-second `closeTime` in `StellarValue` stays, and the new millisecond value is added next to it. Downstream systems that decode ledger headers must update their XDR definitions for the new union arms, but they can keep using the whole-second value, or pick up the new one. The near-term targets are steps like 5 to 4 or 3.5 seconds, so whole seconds are still fine at the transaction level. If ledger times get much shorter, the team may revisit milliseconds in the transaction interface.
+
+## Questions
+
+- **Milliseconds for random numbers**: Someone in chat suggested that milliseconds in the interface would help pseudo-random number generation. Garand and Dima disagreed. Soroban already has a PRNG on the host, and validators set the timestamp. A Byzantine validator could choose arbitrary millisecond values more easily than whole-second values, which are tied more closely to real-world time.
+- **Why not micro or nanoseconds**: Network latency in a distributed system makes anything below milliseconds useless at the consensus layer. Stellar launched with whole seconds because ledger times were much longer at the time, and clock sync (NTP) and servers have improved a lot since then.
+- **Do validators need synced clocks**: No. The validator that proposes a ledger includes its local timestamp in milliseconds. Clocks can still drift between validators, as they can with whole seconds today. The change improves the resolution, it does not require millisecond-level sync.
+
+Please add your comments to the [CAP-88 discussion thread](https://github.com/orgs/stellar/discussions/1998).
diff --git a/meetings/2026/09/17.mdx b/meetings/2026/09/17.mdx
new file mode 100644
index 000000000..cac1d2eef
--- /dev/null
+++ b/meetings/2026/09/17.mdx
@@ -0,0 +1,77 @@
+---
+title: "2026-09-17"
+description: "This week was a straight-up AMA about Stellar Private Payments (SPP), Nethermind's privacy-pool implementation for Stellar."
+---
+
+_September 17, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/QO40dHfJO9Y?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## An AMA for the Newest Kid in Town
+
+This week was a straight-up AMA about **Stellar Private Payments (SPP)**, Nethermind's privacy-pool implementation for Stellar. We played around with Nethermind's demo on a stream a couple of months back, and the August 6 confidential-tokens Q&A kept pointing at SPP as the tool you reach for when you need _counterparty_ privacy rather than hidden amounts. So this time we went to the source. A few days before the stream we asked on X and in the developer Discord for your questions; my job was to read them to **Antonio Larriba** from **Nethermind**, who joined from Europe at 8 p.m. his time and took the whole hour in stride.
+
+Quick introduction, since the Electric Capital developer numbers for Stellar keep climbing and a lot of you are new here: Antonio is a computer scientist with a PhD in cryptography — electronic voting and anonymous identification, specifically — and has been a cryptography engineer at Nethermind for a bit over three years. He has led the Stellar Private Payments work for the whole project. He also blamed _Cryptonomicon_, read as a teenager, for the privacy obsession. There is clearly a story there; I did not ask, since it is private.
+
+The questions came mostly from builders in LATAM and the MENA region, and they were largely conceptual: people understand how SPP differs from confidential tokens, they wanted to know how the design actually holds up.
+
+## What "Compliance" Means Inside a Pool {#what-compliance-means-inside-a-pool}
+
+The first question came from a developer in Turkey who had read both the Nethermind blog post and ours and kept snagging on one sentence they share: _privacy and compliance are not opposing requirements_. Fine — but what does compliance mean concretely? What can a regulator, an issuer, or an auditor actually do with an SPP pool?
+
+Antonio's framing: a fully private pool is easy to build, and history shows what happens next — honest users end up sharing a pool with hacked funds, and everyone's money is tainted by association. Compliance in SPP is the set of rules that keeps bad actors out without making the privacy useless, and it is **part of the protocol**, not an add-on:
+
+- Every interaction is a **zero-knowledge proof** that you own funds in the pool, that they are really part of the pool, and that they have not been spent.
+- On top of that, you prove **membership in a whitelist and non-membership in a blocklist**. These lists are called **association sets**, and the parties maintaining them are **Association Set Providers (ASPs)**.
+- The rules are **configurable per pool**. An ASP could implement a blocklist mirroring a government sanctions list, or a whitelist that is ZK-friendly and never asks for personal information. Or a pool operator can run a pool with **no whitelist and no blocklist at all** — fully private, no admin superpowers, "for the good and the bad," as Antonio put it.
+
+The part I found most important: if a whitelist is KYC-based, you give up some privacy **exactly once, at onboarding**. After that, everything happens inside the proofs. The ASP can accept or block your notes, but it cannot see which notes you own or how you spend them. A chat question later asked whether mentioning KYT (know-your-transaction) means the model is not trustless — the answer is the same: nothing is enforced per transaction today, the whitelist and blocklist operate at the public-key level, and whether a pool uses any of it is the operator's call. Everything is open source, so you can read how the lists are enforced rather than take anyone's word for it.
+
+## Where SPP Sits in the Privacy-Pool Family
+
+I asked Antonio where SPP lands in the wider privacy landscape, and he was refreshingly unbothered about being first: SPP is a **privacy pool**, in the lineage of private notes spent inside circuits. Tornado Cash is the famous one, Railgun uses similar techniques, and a handful of newer teams are working on compliance-aware pools too. The shared goal is severing the public link between an origin account and a destination account. What makes SPP interesting is the feature set layered on top of that, which is where we spent the middle of the call.
+
+## The Feature List, For the Hackathon Crowd
+
+Antonio led with the packaging, because there is a hackathon on and I personally know more than five teams building on SPP right now:
+
+- A **TypeScript SDK** on npm and a **Rust SDK** on crates.io, both named `stellar-private-payments`. They are new, so feedback and bug reports are genuinely wanted.
+- **Deposit and withdraw** to break the origin-destination link. The privacy you get is statistical and scales with the **anonymity set** — the number of people using the pool.
+- **Internal transfers**: you can pay other people, trade, or move funds between your own accounts without leaving the pool, so none of that activity leaks.
+- **Selective disclosure**: generate a proof that you own, say, ten notes with a given balance, without revealing your secrets or any personal information. Useful when you need to show an honest origin of funds without opening everything up.
+- An optional **global view key**. Some pools are being deployed where users encrypt certain secrets to a pool administrator, who can decrypt them off-chain when legally required and audit the trace. It is view-only — your funds can only ever be spent by you — and whether a pool enables it is, again, configurable. Institutions want this, and institutions are where the volume (and therefore the anonymity set) will come from.
+- A **CLI**, which Antonio rightly pointed out is the natural interface if you want to hand an agent a set of tools and let it operate the pool for you.
+
+On the roadmap, with the usual "no details yet": lighter-weight **tracing via KYT at deposit time** — screen funds once on the way in, then leave the user fully private instead of relying on a powerful view key — and **ragequit**, so that if a pool bans you unfairly you can get your funds back, at the cost of the privacy you would otherwise have had.
+
+## Multi-Asset and Multi-Policy Pools
+
+My own question, which I prefaced with "this might be stupid": does trading inside the pool mean **multi-asset pools** are possible? Antonio said they could ship one relatively soon, but most multi-asset designs **sacrifice privacy**. Fifty people using token A and fifty using token B in one pool does not give you an anonymity set of 100; it gives you two sets of 50 dressed up as one. Better UX, no extra privacy. The team has ideas for a design where every asset shares the same large anonymity set — best of both worlds — but it needs changes to the pool and is not on this year's roadmap.
+
+My follow-up, a thought of a thought: not multi-asset but **multi-policy** — one configurable, interoperable pool usable by different contracts and assets. That one is technically possible today. The trade-off is that an arithmetic circuit pays for every operation whether you use it or not, so more policies in one pool means longer proving times. If you are at the hackathon this weekend: just do it.
+
+## Anonymity-Set Economics: Who Deposits First?
+
+The question I was most curious about. Many of SPP's guarantees are only as strong as the number of people in the pool, and pools are per asset today. How does a mainnet pool bootstrap an anonymity set, and what is the smallest set Antonio would call useful?
+
+On bootstrapping: "believers and privacy enthusiasts," with a laugh, but then a real answer. SPP supports **splitting and mixing notes inside the pool**, so there are no fixed denominations like the mixers of old — one deposit can become twenty withdrawals. That means you can deposit 0.1 of a token to test the waters instead of committing a round 1,000. Antonio's bet is that enough people want privacy badly enough to take the small leap of faith first, and that institutional volume follows.
+
+On the minimum: it depends on your threat model — an average user and a journalist whose life depends on it are different cases — and the anonymity set is not the only thing that matters. **Metadata hygiene** matters just as much: deposit from account A and withdraw to account A and you have bought yourself nothing. Use unrelated accounts, ideally with a third account paying the transaction fee. With proper hygiene and enough time in the pool, his bare-minimum number was **12**, which he noted is roughly the ring size he recalled from Monero's ring signatures. I appreciated getting an actual number.
+
+My tangent for the builders in the audience: protocols with AMMs or treasuries could upgrade their contracts to be SPP-compatible and move a chunk of liquidity into a pool, giving it a base of depositors from day one. Nobody told me this was impossible.
+
+## Housekeeping: Demo Errors and Where to Ask
+
+Several of you hit timeouts and simulation failures using the demo with Freighter on testnet. Antonio's explanation: SPP is under active development, breaking changes land multiple times a week, and each one can mean recompiled circuits, new binaries, and redeployed contracts. If your browser is holding old circuits or old state in local storage, proofs get generated against stale data and simulation fails. The fix: open developer tools, **clear local storage** for the demo page, delete the page's cookies, and reload. For the record, "simulation failed" is my least favorite error on Stellar too.
+
+Where to get help: if you are sure it is a bug in the code and not in your setup, open an issue on the GitHub repo (responses can be slow while they build). For questions, there is a **Telegram group** for people developing on SPP — Antonio shared the link, I posted it in the chat, and I warned him that every privacy builder on Stellar is about to join. His X profile went into the comments too, so your timelines can gain a few more privacy freaks.
+
+## Closing
+
+About 200 of you were watching live. Round two ran roughly an hour later: a protocol discussion on **CAP-87**, the proposal adding host functions for **ML-DSA post-quantum signature verification**, on a Google Meet with the core developers. Builders in Istanbul: the **Stellar Pro Hackathon** at Grand Pera is this weekend, and I expect several of you to show Antonio your projects and ask him a bunch of questions about SPP. Busy weekend for him. Thank you, Antonio — hopefully I will see you at Meridian. See you next week.
diff --git a/meetings/2026/09/17/protocol.mdx b/meetings/2026/09/17/protocol.mdx
new file mode 100644
index 000000000..59d63de27
--- /dev/null
+++ b/meetings/2026/09/17/protocol.mdx
@@ -0,0 +1,58 @@
+---
+title: "2026-09-17 Protocol Discussion"
+description: "After the Stellar Private Payments AMA, Jay Geng from the core team presented CAP-87."
+---
+
+_September 17, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/-JaNSo6jN_U?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+After the [Stellar Private Payments AMA](/meetings/2026/09/17), Jay Geng from the core team presented [CAP-87](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0087.md). This is the CAP that audio problems pushed out of the [previous week's discussion](/meetings/2026/09/10).
+
+## Why Post-Quantum Signatures
+
+The signature schemes that blockchains use today rely on the hardness of factoring and the discrete log problem, including its elliptic curve version. Shor's algorithm solves these problems in polynomial time on a large enough quantum computer. Nobody knows when that day comes, but Stellar wants to be ready.
+
+A few months ago SDF published a three-stage quantum readiness plan for Stellar. CAP-87 is the first stage: add post-quantum signature verification to Soroban as host functions, so smart wallets can adopt a post-quantum scheme on their own. Network-level signatures are not part of this CAP.
+
+## Why ML-DSA
+
+NIST has three post-quantum signature candidates:
+
+- **ML-DSA** (FIPS 204), lattice-based.
+- **SLH-DSA** (SPHINCS+), hash-based. Signatures and keys are roughly an order of magnitude larger, and it is much more expensive to compute.
+- **Falcon**, also lattice-based and more compact, but its standard is not final yet.
+
+ML-DSA is the most mature choice. Large cloud providers support it in their KMS products, Cloudflare supports it, and OpenSSL and Apple's CryptoKit list it. Its signatures are a few kilobytes, which fits a blockchain much better than hash-based schemes. Jay noted that the other two could still come later, because the blockchain world is split on all three.
+
+## What CAP-87 Adds
+
+Three host functions, one per ML-DSA parameter set: `verify_sig_ml_dsa_44`, `verify_sig_ml_dsa_65` and `verify_sig_ml_dsa_87`. They share the same interface: public key, message, signature and an optional context string for domain separation. The context must be shorter than 256 bytes, as the standard requires.
+
+- The numbers 44, 65 and 87 refer to the size of the internal matrix. For ML-DSA-44 it is a 4x4 matrix of polynomials.
+- Key and signature sizes are exact. For ML-DSA-44, the verifying key is 1,312 bytes and the signature is 2,420 bytes. Any other size makes the function fail at once.
+- Each function decodes the key, decodes the signature, then verifies.
+
+### Costs
+
+The CAP adds nine new cost types, three per parameter set:
+
+- **Decode verifying key**: constant cost. This step does more than parse bytes. The public key holds a seed, and the host expands it into the full matrix with SHAKE.
+- **Decode signature**: constant cost.
+- **Verify**: linear in message and context length, because the message is hashed together with the context and the public key. Everything else is constant.
+
+Jay shared early calibration numbers for ML-DSA-44: about 38k CPU instructions to decode the signature, about 850k to decode the verifying key, and about 686k to verify. About half of the work is in decoding.
+
+## Questions
+
+- **What makes it quantum safe**: Lattice signatures rely on different hard problems, Short Integer Solution and Learning With Errors. Both come down to finding short vectors in a lattice, and there is no known efficient attack on them, even with a quantum computer.
+- **Which library**: AWS has a formally verified implementation, but it is low-level C. The team prefers a pure Rust dependency. The two mature Rust options are RustCrypto and libcrux. RustCrypto is the likely choice: its code is simpler and cleaner, it is widely used, and its decode and verify steps are well separated. The interface does not depend on the library, so it can change later.
+- **Passkey smart accounts**: ML-DSA is a new option, not a replacement. Passkeys today use secp256r1, and post-quantum passkeys need support from the platform and wallet side, for example in the WebAuthn layer. Jay warned against adopting it too early: if you give up hardware signing just to get a post-quantum property, that is a step backward. More ecosystem work is needed here.
+
+Please add your comments to the [CAP-87 discussion thread](https://github.com/orgs/stellar/discussions/1915).
diff --git a/meetings/2026/09/24.mdx b/meetings/2026/09/24.mdx
new file mode 100644
index 000000000..23fbfc28c
--- /dev/null
+++ b/meetings/2026/09/24.mdx
@@ -0,0 +1,77 @@
+---
+title: "2026-09-24"
+description: "This week kicked off a live stream series that runs all the way to Meridian, our flagship conference, and Hack Meridian, the hackathon that happens right..."
+---
+
+_September 24, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/0CqboqwZnH4?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## Road to Hack Meridian, Episode One
+
+This week kicked off a live stream series that runs all the way to **Meridian**, our flagship conference, and **Hack Meridian**, the hackathon that happens right before it. The idea is simple: we want builders walking into Hack Meridian with as many resources as possible, and the first resource you should look at when building on Stellar is **Raven**. "If you're building on Stellar, just ask Raven" isn't an official slogan, but it's the one we keep repeating. I look at a lot of protocols to see how they help their developers, and — biased as I am — Raven is probably the best thing happening to a Web3 builder right now.
+
+Thankfully I wasn't alone at 11 p.m. staring at my comment section. My guest was **Feems** from **Guava Global**, the studio managing the Hack Meridian efforts. Feems leads hackathon program design and the hacker experience: live streams, workshops, coordination with the activation hosts across Europe, and co-hosting these Thursday streams with me from here on.
+
+## Hack Meridian, the Facts
+
+Guava describes itself as a strategy and production studio that delivers events, activations, and experiences that bring ideas, brands, and communities to life. Hack Meridian is their big one this year:
+
+- **Lisbon, October 25–26**, at **ONE16** — an old railway station, which is a very cool venue.
+- **Two tracks.** **Genesis** is for developers and founders bringing a new idea to Stellar. **Scale** is for existing projects looking to scale onto Stellar or integrate with it. The specific themes within those two categories drop soon.
+- On-site support, workshops, mentors, prizes, and a room full of developers from across Europe.
+- **Find Your Way**, the campaign this stream is part of: more than **10 partners** throwing **20+ IRL activations** across Europe — Madrid, Barcelona, Paris, London, Porto, and more — for builders, founders, and newbies alike. The calendar lives on hackmeridian.com, and Guava Global's X account retweets everything.
+
+## Raven at a Glance
+
+Feems' framing beat mine (mine was "a time capsule of your future self talking down to you, informing you every step of the way"). When you build in an ecosystem, the biggest question is _has this been built already?_ — and answering it normally means scouring tons of documentation. Raven collapses that into one place: hundreds of developer docs plus everything happening in the Stellar ecosystem, so you can ideate faster, check **relevancy** — the biggest problem at the scale stage — and keep up with how fast the development side moves. Think of it as your **builder sidekick**.
+
+Setup is one line. Go to **raven.stellar.org**, copy the command for your AI tool of choice — Codex, Claude, whatever — run it, authenticate, done. I demoed it from a clean Claude Code terminal running Opus 5.5: open the MCP list, see that stellar-raven needs authentication, click authenticate, agree to the terms in the browser window, and you're connected in under a minute.
+
+One piece of builder feedback worth adding. Technical questions are getting rarer — not because builders have no technical problems, but because the ecosystem has more than enough tooling to do practically anything on Stellar. The question has evolved from "how do I do this on Stellar" to "how do I find the material that lets my AI build X on Stellar," and that is precisely the gap Raven closes. Fewer technical questions also means more **ideation** questions: at the last Meridian, for every technical question we got ten about ideas, and whether that idea had already been validated in a recent SCF round.
+
+## The Demo: From "a ZK Track" to a Shortlist {#the-demo-from-a-zk-track-to-a-shortlist}
+
+Feems walked through the questions every builder asks. Ideation: what could I build? (The part that takes longest; the heartbreaking failure mode is spending months on something nobody wants.) Validation: does anyone want this, does it fit the ecosystem, does it line up with funding? For Scale projects: market research and a real consumer base — which, not coincidentally, is what judges look at too. A future stream will cover judging properly.
+
+So I played a Hack Meridian participant. My prompt, roughly: _I'm at Hack Meridian and want to build something around privacy, maybe ZK — let's pretend there's a ZK track. Use Raven to see what privacy solutions are live on Stellar, and check previous SCF rounds for funded privacy projects. Also, you're being live streamed, so show how and why you're using Raven at every step._ (I regretted that last sentence immediately. Don't tell your agent it's on TV.) Someone in chat pointed out I'm also a judge; I am, and a hard one to please — I try not to be impressed by projects.
+
+While it ran I plugged a sibling project: **Stellar Build**, a more private, hands-on set of skills and personas for the AI of your choice that doesn't touch dynamic data. Stellar Build helps you decide what to build; Raven tells you what has already happened — and Stellar Build uses Raven under the hood, because Raven is the best.
+
+Raven came back with the privacy projects live on Stellar today, each with its SCF cohort and the amount awarded: a reusable-KYC project, **Moonlight** (compliant confidential transactions), and **Zarf** — the Turkish team doing private token distribution with ZK, who you met in the July 2 note. It also laid out what the protocol itself supports right now, the technical border of what you can build — a border that gets wider every day. And because Raven indexes the Electric Capital developer report, not just SCF, it surfaced projects like **KALIEN**, Tyler's ZK-proven Asteroids game. Cohorts 23, 37, 40, and 42 flew past, each with the track applied to and the funding received.
+
+Here's the point. I started "knowing" three things: I'm at the hackathon, there's a ZK track, I want to build on it. I got back ideas proven to have a place in the ecosystem — not to copy, but to build something bigger, smaller, nicher, or better on top of. Step two: pick one and go nicher. I grabbed one of the listed projects and asked whether a more niche version existed — think threshold encryption, confidential transfers, sealed-bid auctions. Raven's answer: a few, none funded or listed as projects, so maybe I'd walked down a wrong road — or a new one. The closest match was **Stelvin**, a sealed-bid batch DEX that uses **drand** time-lock encryption rather than ZK, built by a Turkish builder I know who won our Istanbul hackathon in June 2025. It also surfaced **Sub Rosa**, a sealed commit-and-reveal protocol that, if I remember correctly, has received InstaRewards and is heading into the upcoming SCF round. The name-dropping isn't the point; the speed is. You go from "privacy, I guess" to "here is the shape of the final product" in minutes, as long as you know the next question to ask: what can be nicher, what can be bigger.
+
+And my standing advice to builders: you chose Stellar and you chose this hackathon — so at the very least, choose to build something that brings you joy.
+
+## Protocol 28, and a Correction
+
+Feems asked how a newcomer finds technical documentation through Raven. The answer explains what Raven _is_: an MCP, and MCPs fetch dynamic data. Every call pulls not only the Stellar skills, every SCF submission, and every project in the Electric Capital report, but the developer documentation itself — Raven's **Stellar docs family** is a full-text search over developers.stellar.org. So I asked it what changed with **Protocol 28**.
+
+Raven said Protocol 28 has three CAPs and "is not live yet." I let that slide on stream, so for the record: the three CAPs are right — **CAP-83** (validators can vote to drop the transaction set from the current ledger), **CAP-85** (externally managed contract executables), and **CAP-86** (host functions for sparse Symbol-keyed map creation and unpacking) — but "not live yet" was stale. Per the software-versions page in these very docs, Protocol 28 hit testnet on August 27 and **mainnet on September 16**, a week before this stream. The tooling part was correct: stellar-core and **Stellar CLI v28** are out, open source, on GitHub. Go update.
+
+## Scale Track: Find Your Nearest Neighbor
+
+We'd just wrapped a hackathon in Istanbul with the same Genesis/Scale split, so Feems asked how Scale projects should use Raven. For a Scale builder the question is "what's my next step," and you answer it by being inspired by something. What my teammates and I did with the Istanbul Scale track was help each team ask Raven: _is there a project similar to mine, what are the differentiators between theirs and mine, and how do I make mine better?_ That's where scaling starts, and where differentiating yourself from the rest of the ecosystem starts.
+
+## How We Actually Use It
+
+Me: every time a builder asks me anything about Stellar, I ask Raven first — partly to answer, partly to check it still works. I use it to research older content, and almost daily to find out whether a tool is being built somewhere in the world. Say I want a Go CLI for Stellar: maybe someone is already building it, or building something that gets me there faster. The research side is the side I use most.
+
+Feems: understanding past hackathons and the projects that came out of them, to build better personas for these streams and the hackathon itself. It aggregates all things Stellar, which is exactly what a program designer needs.
+
+## What's Next {#whats-next}
+
+Feems closed with the activation calendar — events next week in Madrid, Barcelona, Lisbon, Berlin, and Paris from hosts including CryptoDays and Layer X, with the slide refreshed every week.
+
+Next Thursday the topic is **LayerZero OFT and USDT0**: how USDT0 works on Stellar and how the underlying OFT infrastructure works. We ran an informal survey of builders, and cross-chain applications and privacy were the runaway answers. We have NEAR Intents, we have CCTP, we have a bunch of things — but LayerZero is one of the newest integrations and deserves a proper walkthrough. The week after will probably be privacy again: we've covered SPP and confidential tokens a lot, but one more, more mathematically detailed session — maybe with one more guest — wouldn't hurt.
+
+## Closing
+
+More than **150 people** watched this at midnight my time, and Feems joined at 4 a.m. in theirs — one finds a way. I also owe you a promise: I will spend thirty minutes of my night learning how to zoom in on my terminal, so nobody has to squint next time. I just got my visa, so fingers crossed I'll be in Lisbon, side by side with Feems, helping you build more interesting things. Follow Guava Global on X and keep an eye on hackmeridian.com. See you next week.
diff --git a/meetings/2026/10/01.mdx b/meetings/2026/10/01.mdx
new file mode 100644
index 000000000..bcb8bfc72
--- /dev/null
+++ b/meetings/2026/10/01.mdx
@@ -0,0 +1,95 @@
+---
+title: "2026-10-01"
+description: "October is the month of Hack Meridian and the Meridian conference, which is exactly why I refused to spend the call talking about either of them (mostly —..."
+---
+
+_October 1, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/Zo8LK7puSTc?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## Happy Stellartober
+
+October is the month of **Hack Meridian** and the **Meridian** conference, which is exactly why I refused to spend the call talking about either of them (mostly — see the intermission below). This week was about **USDT0 on Stellar**: Tether's USDT delivered to Stellar over **LayerZero**'s OFT standard. Think of it as a prologue to a USDT0 AMA — if everything goes well, next week I'll have people who were actually involved in issuing USDT0 and wiring Stellar into LayerZero on the stream, and my job this week was to make sure you ask them the right questions.
+
+The agenda: slides (necessary, for once), a short intermission about Hack Meridian, then a live tour of **nine demos in one website**, including launching an omnichain token on Stellar and driving a vault on Stellar from **MetaMask**. Everything I showed lives in one public repo, and every address I mentioned is verified on-chain.
+
+## What USDT0 Is
+
+USDT0 is Tether's USDT moved over LayerZero's **Omnichain Fungible Token (OFT)** standard. The canonical USDT stays locked in an adapter contract on **Ethereum**; every other chain holds USDT0 minted against that locked supply. USDT itself is Tether's asset; USDT0 is built and operated by **Everdawn Labs** (I said "I should fact check this" on the call — I did, and it's correct). It's live on 23 networks, and as of **September 2** Stellar is one of them.
+
+One ground rule: **USDT0 is on Stellar mainnet only.** Anything called USDT0 on testnet is somebody's mock. The LayerZero _endpoint_, however, is live on testnet, so your own test tokens work there — which is exactly what the demos use.
+
+Where we stood as of the call — not a sales pitch, just a sense of the potential:
+
+- **23,717 accounts** hold a USDT0 trustline, up from about 13,500 roughly 17 days earlier — growth of about three quarters in two and a half weeks.
+- About **2.58 million USDT0** sits on Stellar, almost all of it held inside 23 contracts.
+- **Seven DVN operators** are registered on Stellar mainnet; USDT0 requires three of them.
+- USDT0 is the biggest LayerZero tenant on Stellar but not the only one: of the last 50 messages leaving Stellar when I built the slide, 38 were USDT0. The rest came from other apps — PayPal's and Ethena's among them.
+
+## Each Leg Has Its Own Mechanism
+
+An OFT keeps one total supply across chains by pairing a debit on the source with a credit on the destination, but the mechanism differs per leg. On **Stellar** it's **mint/burn**: sending burns your USDT0 through the Stellar Asset Contract; receiving has a contract called the **SAC manager** mint to you, so supply on Stellar always equals what was bridged in. On **Ethereum** the OFT is an **adapter**: sending locks canonical USDT (approve first), receiving unlocks it, nothing is ever minted. That invariant is the whole security story — USDT0 minted everywhere else equals USDT locked in the Ethereum adapter — so never promise "burn and mint on both ends"; always check the leg.
+
+Remember CCTP? Same story with decimals, as we saw in [Elliot's CCTP call](/meetings/2026/07/30): Stellar has seven, USDT on Ethereum has six. OFT solves this with a **shared precision**, six for USDT0, and amounts travel on the wire as a 64-bit integer in those six decimals. Send `12345678` stroops and the wire amount is `1234567`; the trailing eight stroops are **dust**, removed before the message is built, and they stay in your account. The practical rule: always call `quote_oft` first — it returns the exact amount that will arrive, and skipping it fails your simulation.
+
+A LayerZero message is not a transaction that travels. It's five steps: **send, verify, commit, execute, mint**. The source OFT calls the endpoint and a packet is emitted with a nonce, endpoint IDs, sender, receiver and payload. Each required **DVN** — decentralized verifier network — independently attests the packet on the destination chain. Once the required set has attested, the verification is committed on the receive library (anyone can call this). An executor calls `lz_receive` on the destination OFT — anyone can be the executor. And on Stellar, the OFT asks the SAC manager to mint to the recipient. The DVN set is dynamic and may grow or shrink; for now, know that DVNs exist and why.
+
+## Three Contracts and a Classic Asset
+
+On EVM chains one contract is both the token and the LayerZero app. On Stellar it's several pieces — the most confusing part for me when I first learned LayerZero:
+
+1. **The classic asset, USDT0.** Its issuer account is locked, and the flags allow freezing and clawback, like Tether does on every chain.
+2. **The Stellar Asset Contract.** The SEP-41 view of the asset — balance, transfer, burn, the usual suspects. Its admin is not a key; it is a contract.
+3. **The SAC manager.** The admin contract. It holds the admin role and mints only for holders of the minter role. The OFT holds that role, and the SAC manager itself is owned by a multisig.
+4. **The OFT contract.** The actual LayerZero app: `quote_oft`, `quote_send`, `send`, `lz_receive`. It stores the peers and the enforced options, and it points at the SAC and the endpoint.
+
+The classic asset, SAC, and OFT addresses are on [the USDT0 page in our docs](https://developers.stellar.org/docs/tokens/usdt0-layerzero) — point your AI at it. The SAC manager is the SAC's admin, so you can read its address from the SAC itself. Everything about USDT0 is readable without a key or a signature: Horizon gives you the classic side, Stellar RPC gives you the contract side through simulation, and LayerZero's **deployment registry** is the source of truth for every LayerZero address. One lesson from the chain data: the Stellar testnet endpoint was redeployed in August, so **always fetch the registry at runtime** instead of hardcoding. The Stellar CLI works too — a `contract invoke` with any account as source is a simulation, no signing involved.
+
+## Sending USDT0 From Stellar
+
+Sending is five steps and looks like a normal Soroban invocation: build the send parameters; call `quote_oft` for the exact amount that arrives and use it as the minimum; call `quote_send` for the fee, paid in **XLM**; call `send` — the OFT burns your USDT0 through the SAC and the endpoint emits a `PacketSent` with a **GUID**; then track that GUID on **LayerZero Scan** until it says delivered.
+
+Some details cost real money if you get them wrong: the recipient is raw bytes, either a G or a C address; a G recipient needs a **trustline before the message lands**; and the seventh decimal never leaves your account, which is why you call `quote_oft`. Tracking uses the LayerZero Scan API, no key needed — by transaction hash, by GUID, or the latest messages for Stellar. One testnet quirk: Scan indexes Stellar messages by GUID first, so the transaction link can lag a few minutes. Delivery is **permissionless**: once the required DVNs have attested, anyone can finish the message. Remember CCTP? It sort of works like that.
+
+The first question I get from Stellar developers is how this differs from CCTP, so I put together an honest side-by-side (slides coming to X). The short version: not identical, but if you dabble in CCTP, USDT0 over OFT will not be a problem for you.
+
+## Intermission: Hack Meridian
+
+My intermission guest was **Feems** from **Guava**, the production studio helping produce Hack Meridian, who you met on last week's stream. The facts: **Hack Meridian** is a two-day hackathon on **October 25–26 in Lisbon**, with two tracks — **Genesis**, for people with great ideas who want to build (with Raven, the Stellar MCP, at hand), and **Scale**, for existing teams already on Stellar looking to grow. Expect workshops, mentors, office hours and prizes, then a day to chill before the **Meridian** conference on **October 28–29**.
+
+Leading up to it, partners are running a plethora of events across Europe — Barcelona on October 3, Paris on October 6, an online AMA with me on October 8, plus Berlin, Paris and Porto, with more announced each week. Go to one to get a taste of Hack Meridian. My proposal, only half joking: she should do this intermission every week until the hackathon. Thank you for staying up late for it.
+
+## The Demos: Fork This Repo
+
+Everything lives at [kaankacar/stellar-layerzero-demos](https://github.com/kaankacar/stellar-layerzero-demos). Please fork it and do a bunch of weird stuff with it — every time I play with LayerZero, another use case opens up. Highlights of the tour:
+
+- **Explainer** — an interactive version of the slides, with the DVNs live on testnet and the "Stellar twist" of multiple contracts. I'm an academic boy, so there are multiple-choice quizzes too.
+- **Inspector** — mainnet, read-only, refreshed every 30 seconds: USDT0 supply and holders, plus the **wired peers** — the 21 networks your app on Stellar can connect to: Arbitrum, Berachain, Tempo, Optimism, Monad and more. I don't know half of these chains, but each one is a user base you might want to reach. (HyperCore shows up in LayerZero's testnet API but has no registry ID, so it's unusable for now.) A simulate view shows how many DVNs a route requires: three.
+- **Bridge tracker** — paste a transaction hash and follow it, or browse the latest USDT0 messages touching Stellar; the last four were from Polygon and Ethereum, each attested by three DVNs. Timing varies: my first Ethereum testnet transfer took 20 minutes because of Ethereum's block times; Arbitrum takes about two seconds.
+- **Quotes and a playground** — mock only, because real USDT0 is mainnet only.
+
+### Launching an Omnichain Token, Live
+
+The **launchpad** generates an issuer keypair in your browser and keeps it in local storage — testing only, not how you'd launch a real token, but it walks the exact steps. I'd already launched a **KAAN** token (please don't buy it if anyone offers it to you; I'm not selling, and I don't even have any). For the live run I named the asset after the last person in chat — **ELLIOT** — in lock/unlock mode (the alternative is mint/burn, like USDT0), one million supply.
+
+The Stellar side, one Freighter popup per step at a thousandth of an XLM each: fund a throwaway issuer via Friendbot, deploy the SAC, deploy the SAC manager (USDT0 has one, why shouldn't ELLIOT), open a trustline (always — OFT or not, a SAC means a trustline), mint a million ELLIOT, hand the SAC admin to the SAC manager, deploy the OFT, and **lock the issuer** — simulating USDT0's trust model with clawback and master weight.
+
+Then the part that makes it omnichain: deploy the OFT on **Arbitrum Sepolia** via MetaMask, enforce options, and wire the two OFTs as peers — three wallet-signed transactions. Result: ELLIOT live on two chains, one OFT owned through Freighter and one through MetaMask, on a pathway using the active testnet DVN. Recipients need an ELLIOT trustline; open one and I'll send you some. Want more chains? Repeat the last three steps per chain: deploy the OFT, enforce options, wire the peers.
+
+### A Vault on Stellar, Driven From MetaMask
+
+The last demo: a vault on Stellar testnet that you operate with MetaMask on Arbitrum Sepolia. To be clear, I am not saying MetaMask has integrated Stellar. I'm saying that, right now, MetaMask on an EVM L2 can interact with a contract that lives on Stellar. I minted some mock USDT0 on Arbitrum, hit **deposit via LayerZero**, signed the MetaMask popup, and watched the tracker: one DVN verification required.
+
+Then the demo stalled — I hate it when my demos don't work — so I nudged it with my Freighter: committed the verification and called the endpoint's `lz_receive` myself. "You were the executor." Exactly the logic from Elliot's CCTP demo: instead of waiting for execution, you finish the message. A moment later the vault on Stellar held **500 more mock USDT0**, deposited from MetaMask.
+
+Now imagine the rest. Five years ago people talked about omnichain tokens with no good use cases; the industry is in a more established place now. Omnichain DEXes, omnichain lending and borrowing, omnichain wallets — anything. Every user of Ethereum, Arbitrum, Berachain or Monad is now a potential user of your financial application on Stellar. Fork the repo, ask Raven what else is possible, and build it.
+
+## Closing
+
+Around **250 people** were still watching when I closed, and I hate ending a stream with a quarter of a thousand viewers on. I'll be at Hack Meridian helping every one of you — if you're around, ask me about LayerZero. Thanks for watching, enjoy the outro music, and I'll see you next week — hopefully with something as interesting as this week's topic.
diff --git a/meetings/2026/10/08.mdx b/meetings/2026/10/08.mdx
new file mode 100644
index 000000000..b89c861d1
--- /dev/null
+++ b/meetings/2026/10/08.mdx
@@ -0,0 +1,95 @@
+---
+title: "2026-10-08"
+description: "Last week I built a USDT0 demo and walked through how the LayerZero infrastructure works on Stellar (2026-10-01)."
+---
+
+_October 8, 2026_ · [Kaan Kacar](https://github.com/kaankacar), Developer Advocate
+
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube-nocookie.com/embed/FK4_RmHCirU?rel=0&modestbranding=1"
+  title="YouTube video player"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+/>
+
+## A USDT0 AMA
+
+Last week I built a USDT0 demo and walked through how the LayerZero infrastructure works on Stellar ([2026-10-01](/meetings/2026/10/01)). Most of your questions about **USDT0** arrived _after_ that call, so this week I brought reinforcements. I collected around 30 questions from you and from a few ambassador chapters, shortlisted nine, and hoped to get through four. We got through six or seven.
+
+My guest was **Fabricius "Fifo" Zatti**. If you've been in the ecosystem for more than six months, you probably know him already. He has been around Stellar for about six years. He started at **Cheesecake Labs**, where he was the top contributor to **Stellar Plus**, and now works at **The Aha Company**. He also wrote **Colibri**, the TypeScript toolkit for Stellar that includes contract build verification. He works with SDF on a program that brings experts from the ecosystem to help partners build on Stellar.
+
+On USDT0, Fifo was one of the Stellar-side technical contacts for the **LayerZero Labs** and **Everdawn Labs** teams. He worked on the issuer setup sequence, six versus seven decimals, multisig tooling, build reproducibility and verification, DVN data needs, and partner readiness. To be clear: he is not from LayerZero or Everdawn, and he did not build the LayerZero protocol internals or set USDT0 policy. He said he might not have every answer, and he gave honest ones where his memory was fuzzy.
+
+For scale, as of the call: about **5 million USDT0** circulating on Stellar, across roughly **25,000 accounts**.
+
+## Before the Questions: Hack Meridian
+
+**Hack Meridian** is our flagship hackathon before the **Meridian** conference. It runs on **October 25–26 in Lisbon**. If you have no visa restrictions, come show us what you're building, and **make your repos public** so we can judge them. No idea what to build? Ask [Raven](https://raven.stellar.org). Prizes go up to **$30,000 in XLM**.
+
+There's more than one way to take part. That day was my third stream: an AMA as a road to Hack Meridian with **Web Zero**, a Spain-based developer community, and a presentation on Stellar tooling at a workshop organized by **Her DAO**. The next day there was an event in **Berlin** on building with AI. Our production partner is **Guava Global**, part creative studio, part production house, part cultural connector.
+
+## Fifo's Seat at the Table {#fifos-seat-at-the-table}
+
+My first question: this was not a one-seat operation, so what did his seat look like, and did any Stellar idea take longer than necessary to land?
+
+Fifo tries to stay **neutral and transparent** about how things work and how choices affect the ecosystem. LayerZero is a huge protocol, and USDT0 already runs on many networks with its own standards. Soroban is a new space for them. So his job was to make sure the teams had all the information when they chose a path. For almost every project that comes to Stellar, he spends extra time on three things: **how storage works**, **how authorization works**, and **the bridge between classic and Soroban**. He doesn't see these as friction points. He sees them as places where you can use Stellar to your advantage. Much of his role was to question design choices: does this come from a requirement, or from tooling you're used to on other networks? If the latter, can we find a better way on Stellar?
+
+The stressful part was **build reproducibility**. Everyone wanted USDT0 out quickly, but also well tested and bulletproof, and reproducibility was a hard requirement. The existing standard, [SEP-55 (Contract Build Verification)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0055.md), works through attestations tied to the CI process in a repository. During the engagement the team saw they needed a different angle: reproduce the contract build itself. That's hard with Rust compiled to Wasm, where differences in the environment can change the output hash. A lot of people worked on it, and the result is the new [SEP-58 (Contract Build Reproducibility for Verification)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0058.md). Fifo can't wait to see the ecosystem pick it up, probe it, and improve it.
+
+## Why a Classic Asset and Not a Pure Soroban Token?
+
+This came from last week's stream. When USDT0 leaves Stellar, the seventh decimal is lost; when it arrives, the seventh decimal is empty. A pure Soroban token could carry six decimals, like USDT0 on EVM chains. So why did USDT0 land as a classic asset with a SAC?
+
+Fifo called this the hottest question for any asset issuer coming to Stellar. He admits a bias: he comes from "the old testament of Stellar" and loves the classic side, while also saying Soroban filled real gaps. He thinks the USDT0 teams were pragmatic. A pure Soroban token could work. Good examples exist, such as **SolvBTC** and the **Centrifuge** assets. But the key question for builders is: **how do you expect people to use this asset?** His case for classic:
+
+1. **Reach.** Classic assets have been around longer. Wallets, non-custodial apps and secondary markets support a new classic asset automatically, so the surface area is immense.
+2. **Nothing to build or audit.** If the control flags meet your requirements, you deploy no extra contracts and need no separate audit. Classic assets get audited with the protocol, and every classic asset runs the same battle-tested implementation.
+3. **Both worlds.** Through the SAC you reach DeFi and smart contracts. You also keep the classic side: the native DEX, liquidity pools and path payments, all cheap and scalable.
+
+For USDT0 specifically, it checked every box. The control flags give the needed control, and the SAC manager adds the extra administration rules. Fifo called the SAC manager "something fancy they did there" and recommends studying it. The OFT then plugs into the classic asset to handle minting and burning. On decimals, he thinks the trade-off is small. Coming in, you get _more_ resolution on Stellar. Going out, you round or leave some dust behind.
+
+### The Other Side of the Coin
+
+I played devil's advocate and asked for the downsides. Fifo agreed readily:
+
+- **Classic is limited to what the protocol offers.** You get the control flags, or you extend the admin with a contract, and that's it.
+- **No atomic global pause.** With classic you pause through trustlines, one by one. You can bundle several in one transaction, but nothing guarantees you pause every holder at once. A Soroban token can do that.
+- **No per-transfer rules.** Need compliance checks during each transfer? [SEP-57, T-REX](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0057.md), does that for Soroban tokens. You can't add it to a classic asset; workarounds don't behave the same.
+- **Trustlines are part of the user flow.** Where you already run KYC, the trustline fits in nicely. Where you want users to just hold the token, you have to build it into the workflow, sometimes through the trust function in smart contracts.
+
+Classic assets are a good solution, but not a silver bullet. The unique part is that Stellar has both, and they work together. My summary: the two big advantages of a Soroban token are **customizability** and **onboarding**. With smart wallets, users can hold a Soroban token from day one without waiting for a trustline.
+
+## Why a Separate SAC Manager?
+
+In LayerZero's standard OFT, one contract is both the token and the app. On Stellar, the USDT0 OFT mints through a separate **SAC manager** (the three-actor picture from last week: the asset, the SAC admin, and the OFT). Why not make the OFT the SAC admin directly?
+
+You can. Fifo recalled this being a big topic, and he believes the reason was **how the teams wanted to set up the multisig and governance**, though he doesn't remember every detail. The general lesson is about how much responsibility you put in one contract. On Stellar you weigh **storage and resources**, because they scale differently. You also weigh **upgradability**: separate contracts let you upgrade one piece while others stay fixed. He doesn't think upgradability drove this case. The classic asset also mattered. You can't change how the SAC works; it's an interface you build on top of. So a small admin contract on top was necessary, and with the token logic already handled by classic, it wasn't a big lift.
+
+His advice, which I want to repeat: **don't copy other projects**, even big ones. Evaluate the design for your own use case. Flexible, composable building blocks exist so you can adapt them to your reality. Many developers now treat USDT0 almost as its own standard for cross-chain apps, so it matters to know which parts are design choices, which are security choices, and which are required.
+
+## What Does "Waiting for Confirmations" Mean on Stellar? {#what-does-waiting-for-confirmations-mean-on-stellar}
+
+Stellar closes a ledger and it's final, with no reorgs. So what does it mean when a LayerZero app waits for confirmations on Stellar, and how should an app pick that number?
+
+In LayerZero, the full path from a source contract through the endpoint, the DVNs and the destination endpoint to the destination contract is a **channel** (a pathway). You configure each channel independently. Two key settings are **finality**, the number of block confirmations to wait for on the source, and **verification**, which DVNs must verify the message and how many.
+
+Confirmations exist because some chains can reorg. Competing chains get validated, one wins, and transactions on the loser roll back. That's why Bitcoin and Ethereum transfers wait X blocks. If the destination step ran before the source was truly final and the source then reverted, you'd have a big problem. On Stellar the setting still exists, but a transaction is **final after one ledger, about five seconds**. Fifo's recommendation: configure Stellar channels with a low value. Add a couple more if you want a safety margin, but you don't need to. For the other chains on your channel, assess each one separately.
+
+## Why Does Leaving Stellar Take About Half an Hour?
+
+A viewer said leaving Stellar takes about half an hour, while arriving from Polygon takes under two minutes. What are the delivery states?
+
+It comes down to **channel configuration**. A message goes through three legs:
+
+1. **The source transaction.** On Stellar that's about five seconds, plus however many confirmations the channel waits for. USDT0 has its own channel with its own configuration.
+2. **The DVNs.** If the channel requires three DVNs, it takes as long as those DVNs need to pick up, verify and confirm the message on the destination.
+3. **Execution on the destination.** The message runs on the destination chain, and that chain's confirmation time applies.
+
+Open [LayerZero Scan](https://layerzeroscan.com) and find your message. It breaks down each step: time on the source, time waiting for DVNs, which DVNs took part, and the final leg. You can see where the time goes and whether it's just configuration.
+
+I asked whether the number of **signers inside a DVN** slows delivery. LayerZero's own DVN, for example, is on Stellar mainnet and has multiple signers. Fifo's answer: it can, but likely not significantly; it depends on each DVN's implementation. If something is slow, look first at the **on-chain configuration for that channel**: the finality set for the sending and receiving networks is usually the biggest bottleneck. The DVN set also varies by channel: two of three, one of two, four of five. That affects processing time too. Neither of us remembered the signer counts on mainnet offhand; you can look them up from a message on LayerZero Scan. One more point from me: signer count also matters for **security**, so think about which DVNs you choose.
+
+## Closing
+
+Thank you, Fifo, for answering six or seven of my questions. I have 20 more, and I'm saving them for **Hack Meridian**. If you want to watch me ask them live, come to Lisbon on October 25–26. See you next week at the Stellar Developers Meeting.
diff --git a/meetings/atom.xml b/meetings/atom.xml
new file mode 100644
index 000000000..c7aac639d
--- /dev/null
+++ b/meetings/atom.xml
@@ -0,0 +1,858 @@
+<?xml version="1.0" encoding="utf-8"?>
+<feed xmlns="http://www.w3.org/2005/Atom">
+    <id>https://developers.stellar.org/meetings</id>
+    <title>Stellar Docs Blog</title>
+    <updated>2026-08-13T00:00:00.000Z</updated>
+    <generator>https://github.com/jpmonette/feed</generator>
+    <link rel="alternate" href="https://developers.stellar.org/meetings"/>
+    <subtitle>Stellar Docs Blog</subtitle>
+    <icon>https://developers.stellar.org/img/docusaurus/favicon-96x96.png</icon>
+    <entry>
+        <title type="html"><![CDATA[2026-08-13]]></title>
+        <id>https://developers.stellar.org/meetings/2026/08/13</id>
+        <link href="https://developers.stellar.org/meetings/2026/08/13"/>
+        <updated>2026-08-13T00:00:00.000Z</updated>
+        <summary type="html"><![CDATA[A Short One, For a Good Reason]]></summary>
+        <content type="html"><![CDATA[<div class="youtubeEmbed" style="position:relative;width:100%;padding-bottom:56.25%;height:0;margin-bottom:23px"><iframe src="https://www.youtube-nocookie.com/embed/SesCqhylBYw?rel=0&amp;modestbranding=1" title="Informational explainer" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" style="position:absolute;top:0;left:0;width:100%;height:100%;border:0px;border-radius:25pt"></iframe></div>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="a-short-one-for-a-good-reason">A Short One, For a Good Reason<a href="https://developers.stellar.org/meetings/2026/08/13#a-short-one-for-a-good-reason" class="hash-link" aria-label="Direct link to A Short One, For a Good Reason" title="Direct link to A Short One, For a Good Reason" translate="no">​</a></h2>
+<p>This week's meeting was a short one, because it had exactly one job: announcing the <strong>12 winners across 6 tracks</strong> from last week's <strong>Stellar Builder Summit in São Paulo</strong>. I was on the ground with the builders all week, so this was less news roundup, more handing out trophies. My colleague <strong>Teague Kaylor</strong> from SDF's marketing team — focused on developer marketing, which means most of the developer events and programs you see from us have Teague's fingerprints on them — joined to set the scene before the announcements.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="what-the-builder-summit-is">What the Builder Summit Is<a href="https://developers.stellar.org/meetings/2026/08/13#what-the-builder-summit-is" class="hash-link" aria-label="Direct link to What the Builder Summit Is" title="Direct link to What the Builder Summit Is" translate="no">​</a></h2>
+<p>Builder Summits started as a pilot last year at Consensus Toronto: a long-form developer event that brings the community together over an extended stretch to jam on projects, meet new teams, and get properly connected to the ecosystem — instead of the usual 48-hour hackathon sprint. Toronto went well, so this year the plan is to run them in the markets the foundation is launching into. São Paulo was the first.</p>
+<p>The final numbers: around <strong>190 developers</strong> from around the world, coding for <strong>eight days straight</strong>, with workshops and sessions through the week and community days over the weekend. The event was produced with <strong>NearX</strong> — Stellar's partner in Brazil — and our other partner teams on the ground, and the same week São Paulo also hosted <strong>Stellar House</strong>, a one-day gathering on tokenization, stablecoin rails, and cross-border settlement.</p>
+<p>Attached to the summit was a bounty program — Teague described it as a mix of an RFP track and a hackathon — pointed squarely at what we want to see built on the network: privacy, anchors and ramps, local yield, and agentic payments and tooling. More Builder Summits are coming later this year, so watch the <strong>@BuildOnStellar</strong> handle on X for announcements.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="the-winners-12-across-6-tracks">The Winners: 12 Across 6 Tracks<a href="https://developers.stellar.org/meetings/2026/08/13#the-winners-12-across-6-tracks" class="hash-link" aria-label="Direct link to The Winners: 12 Across 6 Tracks" title="Direct link to The Winners: 12 Across 6 Tracks" translate="no">​</a></h2>
+<p>The format: for each track, second place first, then the winner. One housekeeping note before the list. I read these names off the results live and dropped the repo links into the YouTube stream chat as I went (sorry, Twitter viewers — we still haven't figured out posting links there). The canonical list, with correct spellings and repo links, is going out via @BuildOnStellar and our summit partners, so trust that over my pronunciation. Where the auto-captions and I couldn't agree on a name, I'm describing the project rather than guessing.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="privacy-confidential-tokens--private-payment-wallets">Privacy: Confidential Tokens &amp; Private Payment Wallets<a href="https://developers.stellar.org/meetings/2026/08/13#privacy-confidential-tokens--private-payment-wallets" class="hash-link" aria-label="Direct link to Privacy: Confidential Tokens &amp; Private Payment Wallets" title="Direct link to Privacy: Confidential Tokens &amp; Private Payment Wallets" translate="no">​</a></h3>
+<p>Second place went to a <strong>Confidential Token SDK</strong> — a TypeScript client for OpenZeppelin's confidential tokens, with a verifiable replay archive. If you read the July 2 note on the confidential-token developer preview, this is exactly the tooling layer that preview was begging for. I talked with this builder in São Paulo, and their read on our confidentiality layers was genuinely insightful — the placement is well earned.</p>
+<p>The winner: a <strong>privacy wallet</strong> — a passkey-based smart wallet with confidential transfers and a shielded pool whose idle liquidity earns yield. Keep this builder in mind; they show up again below.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="enterprise-compliance--rwa">Enterprise Compliance &amp; RWA<a href="https://developers.stellar.org/meetings/2026/08/13#enterprise-compliance--rwa" class="hash-link" aria-label="Direct link to Enterprise Compliance &amp; RWA" title="Direct link to Enterprise Compliance &amp; RWA" translate="no">​</a></h3>
+<p>Second place: <strong>Green Road</strong> by <strong>Trustless Work</strong> — a confidential milestone escrow that releases a private allowance without revealing the amount. We all know and love Trustless Work and their escrow infrastructure, and this is a natural extension of it into the confidential era.</p>
+<p>The winner: <strong>QuietBook</strong> — confidential book-building for tokenized RWAs. Sealed bids, a provable winner, atomic settlement. Need I say more? I don't think so. It came from a Turkish builder the community knows as Captain — we all met Captain in São Paulo, and the stream chat's verdict ("Captain is the goat") stands.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="anchors--ramps-regional-kits">Anchors &amp; Ramps: Regional Kits<a href="https://developers.stellar.org/meetings/2026/08/13#anchors--ramps-regional-kits" class="hash-link" aria-label="Direct link to Anchors &amp; Ramps: Regional Kits" title="Direct link to Anchors &amp; Ramps: Regional Kits" translate="no">​</a></h3>
+<p>Second place, Trustless Work again: a <strong>LatAm ramp kit</strong> — a drop-in SDK and React component kit that adds fiat ramps to any LatAm app. Two placements in a single summit is a statement.</p>
+<p>The winner: a <strong>Brazil regional kit</strong> — a PIX on- and off-ramp for Brazil with live quotes from competing anchors. It's an aggregator; we all need it, we all love it. The team behind it we've known since our hackathon in Mexico — long-term builders in this ecosystem, still shipping.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="anchors--ramps-emerging-market-yield">Anchors &amp; Ramps: Emerging-Market Yield<a href="https://developers.stellar.org/meetings/2026/08/13#anchors--ramps-emerging-market-yield" class="hash-link" aria-label="Direct link to Anchors &amp; Ramps: Emerging-Market Yield" title="Direct link to Anchors &amp; Ramps: Emerging-Market Yield" translate="no">​</a></h3>
+<p>Second place went to a project that parks idle receivables in Brazilian treasuries while measuring the currency risk. The captions and I jointly butchered the team's name on stream — apologies again; the official winners list will do it justice.</p>
+<p>The winner, from a Brazilian DeFi team: <strong>BRL that earns Brazilian treasury yield right up to the second a PIX payment fires</strong>. Which, as I said on the call, is pretty cool.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="agentic-payments">Agentic Payments<a href="https://developers.stellar.org/meetings/2026/08/13#agentic-payments" class="hash-link" aria-label="Direct link to Agentic Payments" title="Direct link to Agentic Payments" translate="no">​</a></h3>
+<p>Second place: a discovery layer that lets AI agents find what to pay for on Stellar. Every agent-payment stack eventually hits the "pay for <em>what</em>, exactly?" question, so yes — we all need this one too.</p>
+<p>The winner: <strong>StellarPay</strong> — one middleware for every machine payment protocol on Stellar. x402, MPP Charge, MPP Channel — all of it behind a single interface. And yes: same builder as the privacy wallet above. Two tracks, two first places, one summit.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="cli-plugins--dev-tooling">CLI Plugins &amp; Dev Tooling<a href="https://developers.stellar.org/meetings/2026/08/13#cli-plugins--dev-tooling" class="hash-link" aria-label="Direct link to CLI Plugins &amp; Dev Tooling" title="Direct link to CLI Plugins &amp; Dev Tooling" translate="no">​</a></h3>
+<p>Second place: a CLI plugin that lets an AI agent safely call a Soroban contract, gated by an on-chain policy. If you've ever wired an agent up to a Soroban contract, believe you me, you might just need this.</p>
+<p>The winner: <strong>Stellar Memory</strong> — a persistent memory layer that links a Soroban repo to what's actually live on-chain. I love a memory layer as much as the next guy, and I'm glad the track went to a project that closes the gap between your codebase and the deployed reality.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="closing">Closing<a href="https://developers.stellar.org/meetings/2026/08/13#closing" class="hash-link" aria-label="Direct link to Closing" title="Direct link to Closing" translate="no">​</a></h2>
+<p>Close to 200 builders, building for almost a week straight — thank you for showing up. Thanks as well to the judging bench (I was on it, alongside colleagues from SDF and friends from across the ecosystem) and to NearX and the partner teams who produced the event with us. My last words on the call stand: I hope to see every one of these projects evolve into something bigger, and I hope you get to brag one day about how your journey started at a Builder Summit in São Paulo. More of these are coming later this year. See you next week.</p>]]></content>
+        <author>
+            <name>Kaan Kacar</name>
+            <uri>https://github.com/kaankacar</uri>
+        </author>
+        <category label="developer" term="developer"/>
+    </entry>
+    <entry>
+        <title type="html"><![CDATA[2026-08-06]]></title>
+        <id>https://developers.stellar.org/meetings/2026/08/06</id>
+        <link href="https://developers.stellar.org/meetings/2026/08/06"/>
+        <updated>2026-08-06T00:00:00.000Z</updated>
+        <summary type="html"><![CDATA[Live from Stellar House]]></summary>
+        <content type="html"><![CDATA[<div class="youtubeEmbed" style="position:relative;width:100%;padding-bottom:56.25%;height:0;margin-bottom:23px"><iframe src="https://www.youtube-nocookie.com/embed/7nta-uFWiRY?rel=0&amp;modestbranding=1" title="Informational explainer" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" style="position:absolute;top:0;left:0;width:100%;height:100%;border:0px;border-radius:25pt"></iframe></div>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="live-from-stellar-house">Live from Stellar House<a href="https://developers.stellar.org/meetings/2026/08/06#live-from-stellar-house" class="hash-link" aria-label="Direct link to Live from Stellar House" title="Direct link to Live from Stellar House" translate="no">​</a></h2>
+<p>This week we streamed from <strong>Brazil</strong>, where the team is camped out for <strong>Stellar House</strong> — if you're around, come on down. The stream itself was a full-hour Q&amp;A about <strong>confidential tokens</strong>, now live on Stellar testnet: private balances and transfer amounts for SEP-41 tokens, with sender and recipient addresses kept public for compliance. I collected <strong>25+ genuinely hard questions</strong> from builders during the summit that just wrapped, the live chat piled on more, and my plan was to ask the easy ones and let you do the damage.</p>
+<p>The guests: <strong>Alessandro Voto</strong> (goes by Alex), senior product manager of privacy at SDF — in crypto since 2014, and the conduit between institutions asking for private payments and the people implementing them. Design questions went there. Technical ones went to <strong>Jay Geng</strong>, a stellar-core engineer at SDF for four-plus years who worked on Soroban and the host functions that brought ZK primitives to Stellar (<strong>Poseidon</strong>, <strong>BN254</strong>, <strong>BLS12-381</strong>), presented an early iteration of confidential tokens at Meridian in Rio last year, and shaped several of this product's early design decisions.</p>
+<p>We started with 100+ viewers across three platforms and ended past 250.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="private-does-not-mean-illegal">Private Does Not Mean Illegal<a href="https://developers.stellar.org/meetings/2026/08/06#private-does-not-mean-illegal" class="hash-link" aria-label="Direct link to Private Does Not Mean Illegal" title="Direct link to Private Does Not Mean Illegal" translate="no">​</a></h2>
+<p>A surprising number of the questions boiled down to "is this legal?" Alex pushed back on the premise: nobody scrutinizes what you spent on groceries yesterday, and payment privacy in traditional finance isn't a convenience — it's a mandate. For enterprises it's a dealbreaker; they will not make payments their competitors can watch. Blockchains made payments public as a side effect of protecting transaction <em>integrity</em>, never as an end goal.</p>
+<p>The SDF position pairs privacy with <strong>compliance readiness</strong>: the tools ship with freezing, clawback, and Stellar Asset Contract passthroughs, deliberately open-ended because disclosure requirements differ by jurisdiction — you figure out what "legal" means where you operate, and the boundaries enforce it. That same morning, <strong>José Fernández da Ponte</strong>, SDF's president, had framed the network as <em>public by default, private by design</em> — about the neatest recap available.</p>
+<p>Chat asked the obvious follow-up: why the application layer rather than the chain itself? Same reasoning. SDF won't force a privacy regime on anyone happy with the public network's auditability, and application-level privacy lets technologies evolve — some use cases may eventually demand post-quantum designs — without touching the L1. What the core team <em>did</em> ship is the cryptographic host functions that make verifying these proofs on-chain cheap.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="why-hide-amounts-but-not-the-addresses">Why Hide Amounts but Not the Addresses?<a href="https://developers.stellar.org/meetings/2026/08/06#why-hide-amounts-but-not-the-addresses" class="hash-link" aria-label="Direct link to Why Hide Amounts but Not the Addresses?" title="Direct link to Why Hide Amounts but Not the Addresses?" translate="no">​</a></h2>
+<p>The single most asked question — more than five builders raised it with me at the summit alone.</p>
+<p>Alex's product answer: <strong>confidential tokens are one tool in a toolkit</strong>. If you need counterparty privacy, <strong>Nethermind's Stellar Private Payments</strong> is a privacy-pool toolkit that shields amounts <em>and</em> addresses. Confidential tokens deliberately keep counterparties public because that's what the target users asked for: institutions making regular, publicly known payments — foundations paying grantees, charities, banks settling with each other — where an on-chain record of <em>who got paid</em> is an audit feature, but the <em>amount</em> is the sensitive part. A settlement amount can leak an acquisition intent; a large grant to someone vulnerable can paint a target on them. It's the missing middle setting on Venmo: I want you to know I paid this person, just not how much. (And to chat's "who is this for?" — primarily institutions today.)</p>
+<p>Jay's engineering answer: full anonymity is a fundamentally different design. Privacy pools are UTXO-shaped, elaborately grafted onto Stellar's account model, and the proving cost is much higher — you're proving note formation, Merkle-tree inclusion, and unspent nullifiers on every transaction. The confidential token is the more elegant construction: it wraps any existing SEP-41 token — without knowing in advance which asset it will shield — and only encrypts the numbers.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="auditors-viewing-keys-and-the-escrow-question">Auditors, Viewing Keys, and the Escrow Question<a href="https://developers.stellar.org/meetings/2026/08/06#auditors-viewing-keys-and-the-escrow-question" class="hash-link" aria-label="Direct link to Auditors, Viewing Keys, and the Escrow Question" title="Direct link to Auditors, Viewing Keys, and the Escrow Question" translate="no">​</a></h2>
+<p>The auditor is, in my experience, the single most confusing part for developers, so I asked chat's version directly: how does an auditor see anything without the holder cooperating? Jay's answer: it falls naturally out of the encryption design. Amounts are encrypted under the sender's and recipient's keys — and, in addition, under the <strong>auditor's key</strong>. Whoever holds that viewing key can decrypt the same information, no cooperation required. Policies — who can audit, rotation, key lifetime — don't have to live in the contract logic; it just cares that the key exists. It's decoupled and modular — the key can even belong to a third party that doesn't exist on-chain.</p>
+<p>Alex layered the intent on top: there's <strong>selective disclosure</strong>, which is user-initiated ("I can prove this payment happened to whoever I choose"), and there's compelled revelation through the auditor key. The intention is <em>not</em> that someone sits watching the pool — the auditor key should sit unused inside an <strong>MPC or TEE custody setup</strong> (think Utila or Fireblocks, not a Freighter wallet) and only answer scoped requests when a regulator compels one. A single auditor address does not mean a single person; put real key management on it. Alex would be shocked if you didn't.</p>
+<p>Then the fun one. Alberto of <strong>Trustless Work</strong> (the escrow project) showed me a confidential-marketplace experiment that day — an escrow contract between Alice and Bob — and asked whether one auditor holding four keys across four "auditor channels" was the simplest compliant setup. The panel's honest answer: the question doesn't quite map onto the design — "channel" is an overloaded word Jay wanted more context on, and the escrow case probably wants selective disclosure rather than extra auditors. One correction from me while writing this up: Alex's on-call recollection was one global auditor key per confidential token contract, but the shipped implementation binds an <code>auditor_id</code> per account at registration, out of a shared auditor registry that can hold many keys and serve many tokens — design your compliance around that, not around a single global key. To be continued on Discord once the project ships.</p>
+<p>The broader point is worth keeping: today's confidential tokens do <strong>basic payments</strong> with very little composability inside the wrapper — a confidential wrapper doesn't give you atomicity between a payment and a delivery. People are already hacking extensions (like triggering a contract on successful payment), and Alex explicitly wants to see an escrow system built this way. Just don't expect the primitive to hand it to you.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="c-addresses-passkeys-and-key-derivation">C-Addresses, Passkeys, and Key Derivation<a href="https://developers.stellar.org/meetings/2026/08/06#c-addresses-passkeys-and-key-derivation" class="hash-link" aria-label="Direct link to C-Addresses, Passkeys, and Key Derivation" title="Direct link to C-Addresses, Passkeys, and Key Derivation" translate="no">​</a></h2>
+<p>Can you use confidential tokens from a smart wallet — passkeys, C-addresses? Yes; Alex has already seen a passkey demo inside a confidential-token-capable wallet. Jay's explanation of why it works: <strong>authentication and token holding are decoupled</strong>. The smart wallet is an authentication mechanism; the account holder is just a regular token holder underneath. Encryption keys are derived from your account's secret — secret key, then spending key, then viewing key, and so on.</p>
+<p>Registration was the follow-up: to participate you <strong>register</strong> with a specific token contract — the key derivation commits to that contract, involves a proof, and stores your public spending and viewing keys along with your chosen <code>auditor_id</code>. (The auditor's own keys live in a separate registry contract — you pick an auditor at registration, you don't provide its key.) Per Jay, both sender and recipient need to be registered; you can't fire tokens at an address that has never generated its keys. Alex noted the registration step is the deliberate price of a design ask — log in with your existing address and derive everything from it, instead of manually managing separate view and spending keys like the original implementation did.</p>
+<p>Then the warning of the week, from Alex: <strong>your key derivation must be deterministic and must match the OpenZeppelin SDK's canonical derivation</strong>. Alex vibe-coded a wallet that derived keys differently than the demo does — it could <em>deposit</em> funds but never spend or withdraw them. That's an accidental honeypot, built in good faith, by AI. It's funny until it's a lot of money. The system deliberately pushes work client-side for privacy, so the cryptography there actually matters; OpenZeppelin is writing an SDK spec to make expectations explicit. Until then, follow the SDK and don't let a hallucination invent your derivation path.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="wallet-hygiene-retention-windows-and-replay">Wallet Hygiene: Retention Windows and Replay<a href="https://developers.stellar.org/meetings/2026/08/06#wallet-hygiene-retention-windows-and-replay" class="hash-link" aria-label="Direct link to Wallet Hygiene: Retention Windows and Replay" title="Direct link to Wallet Hygiene: Retention Windows and Replay" translate="no">​</a></h2>
+<p>Jay's practical corollary for wallet builders: receiving requires <strong>no action from the receiver</strong> — incoming amounts accumulate homomorphically into your receivable balance as encrypted events, and your wallet learns what you hold by replaying those events, decrypting, and storing the openings. Stellar RPC's default retention is <strong>seven days</strong>, and that number is load-bearing: your commitment stays on-chain forever, but if your wallet loses its local state and the events have aged out of everything you can reach, you can <em>see</em> that your funds exist without being able to reconstruct the opening that spends them. OpenZeppelin's spec is blunt about this — recovery from seed requires a durable event archive, and they publish an indexer specification for exactly that — so wire up infrastructure with the retention you actually need and refresh periodically. Spending is self-healing — every spend forces you to open your balance and generate a proof — so it's the long gaps <em>after</em> your last spend you have to sweep for.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="timing-leaks-scale-and-the-road-to-mainnet">Timing Leaks, Scale, and the Road to Mainnet<a href="https://developers.stellar.org/meetings/2026/08/06#timing-leaks-scale-and-the-road-to-mainnet" class="hash-link" aria-label="Direct link to Timing Leaks, Scale, and the Road to Mainnet" title="Direct link to Timing Leaks, Scale, and the Road to Mainnet" translate="no">​</a></h2>
+<p>A sharp one from chat: deposits and withdrawals into the wrapper are public, so can't you correlate them? Yes — Alex didn't dodge it; in a small pool with few participants, timing analysis gets easier. These systems <strong>benefit from scale</strong>: more parties, purposes, and denominations all make correlation harder — an argument for shared deployments serving many customers under the same jurisdictional requirements, not one pool per app.</p>
+<p>On observability: the OpenZeppelin demo ships an auditor interface showing all transactions and amounts (deliberately open there; keep it behind custody in real life), but scoped audit requests, monitoring, and selective-disclosure tooling — say, sharing your confidential history with a service so you can do your taxes — are wide-open design space. Nobody is building that platform for you. Hint.</p>
+<p>And the shortest question got the most concrete answer: <strong>is it coming to mainnet?</strong> The contracts are live on testnet now — Alex has vibe-coded basic wallets and a private payroll app against them in about twenty minutes. Audits were days from starting at the time of the call; after remediation comes a stable release. The proving stack is <strong>Noir</strong>, verified on-chain by an <strong>UltraHonk verifier</strong> that originated with a community member and is maintained by Nethermind. Alex's main ask: OpenZeppelin is a <em>tooling</em> provider, not an operator. Pick a jurisdiction and a use case and go <strong>be the operator</strong> — sanction lists, allow/deny lists, compliance hooks — and show everyone what best practice looks like.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="bonus-round-confidential-agentic-payments">Bonus Round: Confidential Agentic Payments<a href="https://developers.stellar.org/meetings/2026/08/06#bonus-round-confidential-agentic-payments" class="hash-link" aria-label="Direct link to Bonus Round: Confidential Agentic Payments" title="Direct link to Bonus Round: Confidential Agentic Payments" translate="no">​</a></h2>
+<p>Someone asked about AI agents, so Jay closed with a design sketch. Stellar already has <strong>x402</strong> and machine-payment implementations, and confidential tokens can absolutely make agentic payments private — but not by naive plugging-in. Agent payments are fast, tiny, and many-to-many; you can't settle every one on-chain with five-second finality plus client-side proving. The plausible shape is <strong>channel-based</strong>: accumulate payments off-chain, then settle batches across multiple agents at once, with a registry of who settled what and a dispute period. Jay called it "some engineering to be done" and left it to the ecosystem. I'll repeat what I said live: builders will ship exactly this at the next hackathon, and it will probably win.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="closing">Closing<a href="https://developers.stellar.org/meetings/2026/08/06#closing" class="hash-link" aria-label="Direct link to Closing" title="Direct link to Closing" translate="no">​</a></h2>
+<p>Alex's parting note was the right one: this isn't an incremental ease-of-use feature. It's the chance to stop choosing between traditional finance (private but closed) and blockchains (open but exposed) — ideally ending as a plain checkbox in your wallet that says <em>make this transaction private</em>, done compliantly, from mainnet day one. Drop further questions in the developer chat on the Stellar Developers Discord — there's enough unanswered material for a sequel if demand holds. Thanks to Alex and Jay, and I'll see every single one of you next week.</p>]]></content>
+        <author>
+            <name>Kaan Kacar</name>
+            <uri>https://github.com/kaankacar</uri>
+        </author>
+        <category label="developer" term="developer"/>
+    </entry>
+    <entry>
+        <title type="html"><![CDATA[2026-07-30]]></title>
+        <id>https://developers.stellar.org/meetings/2026/07/30</id>
+        <link href="https://developers.stellar.org/meetings/2026/07/30"/>
+        <updated>2026-07-30T00:00:00.000Z</updated>
+        <summary type="html"><![CDATA[Two Developer Advocates, One Call]]></summary>
+        <content type="html"><![CDATA[<div class="youtubeEmbed" style="position:relative;width:100%;padding-bottom:56.25%;height:0;margin-bottom:23px"><iframe src="https://www.youtube-nocookie.com/embed/57fB8A5vhj0?rel=0&amp;modestbranding=1" title="Informational explainer" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" style="position:absolute;top:0;left:0;width:100%;height:100%;border:0px;border-radius:25pt"></iframe></div>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="two-developer-advocates-one-call">Two Developer Advocates, One Call<a href="https://developers.stellar.org/meetings/2026/07/30#two-developer-advocates-one-call" class="hash-link" aria-label="Direct link to Two Developer Advocates, One Call" title="Direct link to Two Developer Advocates, One Call" translate="no">​</a></h2>
+<p>The twist this week: I wasn't the only developer advocate on the stream. Most of SDF was heads-down preparing for <strong>Stellar House in Brazil</strong> the following week — and if you were in Brazil, you were probably at the <strong>Stellar Builder Summit</strong> at that very moment. If not, I shouted you out for no reason.</p>
+<p>The topic was <strong>cross-chain interoperability with CCTP</strong> — Circle's Cross-Chain Transfer Protocol — and USDC on Stellar. My guest was <strong>Elliot</strong> (<a href="https://x.com/elliotfriend" target="_blank" rel="noopener noreferrer" class="">@elliotfriend</a> just about everywhere — if you can't find him on a platform, type "elliotfriend" into the search bar and be done with it), a senior developer advocate at SDF and genuinely one of the people I've learned the most from since joining. He's been in and around the Stellar ecosystem for six-plus years, having wandered into the Stellar Quest Discord out of curiosity about how the machine actually worked — not to trade altcoins — and never looked back. He built the CCTP demo himself, so I got out of the way and let him drive.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="cctp-in-one-paragraph">CCTP in One Paragraph<a href="https://developers.stellar.org/meetings/2026/07/30#cctp-in-one-paragraph" class="hash-link" aria-label="Direct link to CCTP in One Paragraph" title="Direct link to CCTP in One Paragraph" translate="no">​</a></h2>
+<p>Some framing before the demo. USDC has been native on Stellar since 2021, so this isn't a story about finally getting the token here — it's about how it <em>gets</em> here. Until recently, moving USDC from Ethereum or Base onto Stellar meant a centralized exchange or a third-party bridge: a human does it out of band while your application sits there waiting for a balance to appear. <strong>CCTP turns that into a contract call.</strong> Circle is the issuer of USDC, so nothing needs to be locked anywhere: you <strong>burn</strong> USDC on the source chain, Circle signs an <strong>attestation</strong> that the burn happened, and you <strong>mint</strong> the same amount on the destination chain. Same canonical USDC on both sides, and the whole thing is something your code can start and finish on its own. CCTP went live on Stellar this past May.</p>
+<p>Elliot's history lesson made the "why" concrete. Cross-chain bridging has traditionally been done two ways: <strong>lock-and-mint</strong> (lock tokens in a vault on chain A, mint a wrapped representation on chain B — wrapped BTC being the classic) or <strong>liquidity pools</strong> (deposit real USDC on chain A, withdraw real USDC on chain B). Both approaches end with a giant pile of USDC sitting somewhere, and giant piles attract bad actors. CCTP's version has no pile: the tokens are <em>gone</em> on the source chain, and real, canonical USDC — not a wrapped token, not a pool that can get drained — is minted on the destination.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="the-demo-stellar-to-arc">The Demo: Stellar to Arc<a href="https://developers.stellar.org/meetings/2026/07/30#the-demo-stellar-to-arc" class="hash-link" aria-label="Direct link to The Demo: Stellar to Arc" title="Direct link to The Demo: Stellar to Arc" translate="no">​</a></h2>
+<p>Elliot's demo app is live at <a href="https://cctp27.vercel.app/" target="_blank" rel="noopener noreferrer" class="">cctp27.vercel.app</a> — named after Stellar's CCTP <strong>destination domain, 27</strong> — and the whole thing is open source. He ran it against <strong>Arc testnet</strong> (Circle's chain, domain 26) because Arc is usually quick, but it works the same with any CCTP-enabled chain; he's wired up the EVM chains and Solana.</p>
+<p>First transfer: 5 USDC, Stellar to Arc. The deposit-for-burn invocation on the Stellar side takes a handful of arguments worth knowing:</p>
+<ul>
+<li class=""><strong>Amount</strong> — Stellar USDC has <strong>seven decimals of precision</strong>, so 5 USDC is 50 million stroops. Every other CCTP chain uses six. Why? Per Elliot: "I don't know why, but it is."</li>
+<li class=""><strong>Destination domain</strong> — 26 for Arc, 27 for Stellar.</li>
+<li class=""><strong>Mint recipient</strong> — the destination address, passed as 32 bytes.</li>
+<li class=""><strong>Burn token</strong> — the USDC SAC address.</li>
+<li class=""><strong>Destination caller</strong> — leave it all zeros and <em>anybody</em> can call the mint function on the destination chain, making the mint permissionless; set it if you want only the recipient to be able to.</li>
+<li class=""><strong>Max fee and finality threshold</strong> — these matter for <em>fast</em> transfers on slower chains. Out of Stellar, standard (threshold 2000) is the only supported mode, because Stellar already reaches finality in seconds. Fast transfers exist for chains like Ethereum and its L2s — and Elliot's favorite, Starknet, which can take <strong>four to eight hours</strong> to reach finality before you can mint.</li>
+</ul>
+<p>Out of the box this is a two-transaction flow on Stellar — an allowance <strong>approval</strong> on the USDC SAC, then the <strong>deposit-for-burn</strong> — which bugged Elliot enough that he wrote a <strong>wrapper contract</strong> that does both in one atomic transaction. He demoed it with a 3.14 USDC transfer, "because I'm a dork." Either way, the rest is the same: wait for Circle's attestation ("Circle's permission slip that the burn actually happened"), confirm the mint in MetaMask, watch the balances update.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="the-gotchas-getting-usdc-into-stellar">The Gotchas: Getting USDC <em>Into</em> Stellar<a href="https://developers.stellar.org/meetings/2026/07/30#the-gotchas-getting-usdc-into-stellar" class="hash-link" aria-label="Direct link to the-gotchas-getting-usdc-into-stellar" title="Direct link to the-gotchas-getting-usdc-into-stellar" translate="no">​</a></h2>
+<p>Before going the other direction, Elliot flagged the part that will "totally torch your funds if you're not careful." On EVM chains a mint recipient is a 20-byte address; CCTP gives you a 32-byte field. For transfers <em>into</em> Stellar, you cannot just drop your G address (or M, or C address) in there. Circle requires the mint recipient — and the destination caller — to be the <strong>CCTP forwarder contract</strong>, as the raw 32 bytes underlying its C address (the Stellar SDK will decode those for you).</p>
+<p>Your <em>actual</em> destination goes into the <strong>hook data</strong>, which has a strict layout: 24 zeroed "magic bytes," a version field (currently zero), a length field, and then your G address as a hex-encoded <strong>UTF-8 string</strong> — the string key itself, not the decoded public key bytes. Get that layout wrong and your funds go somewhere you didn't intend.</p>
+<p>The live Arc-to-Stellar run promptly hit Arc testnet's aggressive RPC rate limits, which gave Elliot the chance to show off my favorite feature: <strong>resume from burn hash</strong>. Paste the transaction hash of an earlier burn, the app fetches Circle's attestation, Freighter pops up, and you approve the <code>mint_and_forward</code> call on the forwarder contract. Five USDC landed back in his Stellar wallet.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="solana-atas-and-every-chains-opinion">Solana, ATAs, and Every Chain's Opinion<a href="https://developers.stellar.org/meetings/2026/07/30#solana-atas-and-every-chains-opinion" class="hash-link" aria-label="Direct link to Solana, ATAs, and Every Chain's Opinion" title="Direct link to Solana, ATAs, and Every Chain's Opinion" translate="no">​</a></h2>
+<p>This project was Elliot's first real development against Ethereum and his first Solana transaction ever ("so I'm pretty much an expert on Solana"). Two observations from that tour. First, every ecosystem has its own flavor of contract bindings — the Stellar CLI generates TypeScript or Rust bindings, EVM has ABIs, Solana has IDLs — and they all save you from hand-assembling binary data on the front end. Second, every chain has its own opinion about the 32-byte recipient: EVM addresses are right-aligned and zero-padded; Solana addresses fill all 32 bytes; Stellar wants the forwarder plus hook data.</p>
+<p>The Solana catch: your tokens don't live at your wallet address. Every token you hold has an <strong>associated token account (ATA)</strong> — imagine if each of your Stellar trustlines had its own distinct address you sent payments to — and CCTP transfers to Solana must target the ATA, not the wallet. With that handled, a 12 USDC <strong>fast transfer</strong> from Solana devnet to Stellar went through cleanly: burn confirmed in Phantom, attestation arrived in seconds, Freighter approved the <code>mint_and_forward</code> carrying the message and attestation from Circle's Iris API.</p>
+<p>The closer was <strong>Circle's forwarding service</strong>. Normally you sign — and pay gas — on both sides of a transfer. Going <em>outbound</em> from Stellar (inbound isn't supported yet), you can have Circle submit the destination transaction and cover the gas: it's a relayer, same idea as OpenZeppelin's relayer service or Launchtube, triggered by putting "CCTP forward" magic bytes in the hook data. Elliot sent 11 USDC from Stellar to Solana and the tokens simply appeared — no popup, no destination gas, minus whatever fees Circle took along the way. Getting this working on Stellar testnet took a week or two of politely bugging Circle support (Stellar as a source chain wasn't being indexed correctly at first), so pour one out for whoever fielded those tickets.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="whats-next-for-the-demo">What's Next for the Demo<a href="https://developers.stellar.org/meetings/2026/07/30#whats-next-for-the-demo" class="hash-link" aria-label="Direct link to What's Next for the Demo" title="Direct link to What's Next for the Demo" translate="no">​</a></h2>
+<p>Elliot's roadmap: try M-addresses and smart accounts (everything so far has been plain G addresses), add more chains beyond "EVM is pretty much the same from one to the next," extend the wrapper contract to <strong>ensure the destination G address has a trustline</strong> before invoking the mint on Stellar-bound transfers, and use the forwarding service to create the recipient's ATA on Solana-bound ones — ATAs aren't opt-in like trustlines, they just have to be paid for.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="closing">Closing<a href="https://developers.stellar.org/meetings/2026/07/30#closing" class="hash-link" aria-label="Direct link to Closing" title="Direct link to Closing" translate="no">​</a></h2>
+<p>Everything — the app, the contracts, even the slide deck (an HTML page Claude put together) — lives in the <a href="https://github.com/ElliotFriend/stellar-cctp-demo" target="_blank" rel="noopener noreferrer" class="">stellar-cctp-demo repository</a>. Take it, build it, break it, steal it; whatever floats your boat, per the author. A viewer on Twitch asked for the presentation materials, and Elliot's sharing them once refined. Close to 200 of you watched live across YouTube, X, and Twitch. Elliot's parting words: "let your heart guide you." Next week we talk confidential tokens with more SDF folks — see you there.</p>]]></content>
+        <author>
+            <name>Kaan Kacar</name>
+            <uri>https://github.com/kaankacar</uri>
+        </author>
+        <category label="developer" term="developer"/>
+    </entry>
+    <entry>
+        <title type="html"><![CDATA[2026-07-23]]></title>
+        <id>https://developers.stellar.org/meetings/2026/07/23</id>
+        <link href="https://developers.stellar.org/meetings/2026/07/23"/>
+        <updated>2026-07-23T00:00:00.000Z</updated>
+        <summary type="html"><![CDATA[Stellar Quest Is Back]]></summary>
+        <content type="html"><![CDATA[<div class="youtubeEmbed" style="position:relative;width:100%;padding-bottom:56.25%;height:0;margin-bottom:23px"><iframe src="https://www.youtube-nocookie.com/embed/0RpAMlqRmkY?rel=0&amp;modestbranding=1" title="Informational explainer" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" style="position:absolute;top:0;left:0;width:100%;height:100%;border:0px;border-radius:25pt"></iframe></div>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="stellar-quest-is-back">Stellar Quest Is Back<a href="https://developers.stellar.org/meetings/2026/07/23#stellar-quest-is-back" class="hash-link" aria-label="Direct link to Stellar Quest Is Back" title="Direct link to Stellar Quest Is Back" translate="no">​</a></h2>
+<p>Before the guests, some news from the developer ecosystem — starting with a sentence I haven't been able to say for a while: <strong>Stellar Quest is live again</strong>. If you've been around long enough, you know Stellar Quest was once the most widely shared link between builders in this ecosystem. It's been broken for some time, mostly because third-party services it depended on sunset their operations (including the one that powered the interactive code lessons). That's fixed now — it's live, it's working, and you can use it to get a genuinely hands-on feel for building on Stellar.</p>
+<p>Is a click-through learning platform the best use of a developer's time in the post-AI age? That's for you — and for our ambassadors — to decide. What I can say is this: building with AI is insanely easy, and the only thing separating you from AI slop is actually knowing the ecosystem you're building in. You don't have to write the code by hand anymore, but you do have to know what an account is, what a trustline is, what a SEP-41 token is. Stellar Quest is one way to earn that knowledge. Expect a refined version in the coming weeks, shaped by whatever our ambassadors ask for.</p>
+<p>On the AI side of the same coin: <strong>skills.stellar.org</strong> keeps growing. It's our skills website, but it's also <em>your</em> skills website — there's a community section with <strong>17 community skills</strong> built by non-SDF people (one of my favorites: a Scout-style skill for researching the ecosystem and SCF before you build), next to <strong>7 official skills</strong>, with three more official ones visible in the open-source repo if you go looking. Adding your own is a pull request away — there's an example skill-card entry in the repo showing exactly how to submit. Building on Stellar with AI gets easier every day; Stellar Quest is there when you want to slow down and actually learn.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="guest-hypertron--private-payments-and-operations-for-businesses">Guest: Hypertron — Private Payments and Operations for Businesses<a href="https://developers.stellar.org/meetings/2026/07/23#guest-hypertron--private-payments-and-operations-for-businesses" class="hash-link" aria-label="Direct link to Guest: Hypertron — Private Payments and Operations for Businesses" title="Direct link to Guest: Hypertron — Private Payments and Operations for Businesses" translate="no">​</a></h2>
+<p>This week's guest was <strong>Hypertron</strong> (hypertron.space), a programmable operating layer for <strong>B2B payments and operations on Stellar</strong> — think payments, treasury, and compliance workflows for a business, with privacy as an opt-in layer on top. <strong>Sweta</strong> and <strong>Soumik</strong>, the two co-founders, joined from India at 11:47 p.m. their time (self-declared night owls, so it's fine).</p>
+<p>Some backstory: the two met in college, ran an agency and freelanced together, and fell into web3 in late 2023 through hackathons — ETHIndia was the first big one. Since then Sweta has worked at a Solana-based company, on early NFT projects on Base, and currently also does security work at Hacken; Soumik has worked for a prediction market on Solana and a payments company. This one was personal for me too: I first met them at a Rise In hackathon in Bangalore about two years ago, on my second day ever in India. I mostly remember the biryanis.</p>
+<p>Why Stellar? Their answer was better than the usual one. Stellar targets institutional clients and has always been a <strong>public blockchain by design</strong> — which they think is the right default. Traditional finance is private by default with auditability on request; public blockchains are transparent by default. Hypertron's whole thesis is to add privacy <em>on top of</em> the public chain, without giving up the verifiability that makes a public chain valuable in the first place. The problem is concrete: once a business runs payroll and vendor payments in stablecoins, anyone — a client, a competitor, a very motivated employee — can trace its treasury. Wallets get poisoned, payments get tracked. That's the gap they're filling.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="the-application-layer">The Application Layer<a href="https://developers.stellar.org/meetings/2026/07/23#the-application-layer" class="hash-link" aria-label="Direct link to The Application Layer" title="Direct link to The Application Layer" translate="no">​</a></h3>
+<p>Soumik demoed the product side. There's a <strong>sandbox</strong> on hypertron.space so you can poke around before connecting anything, and sign-in is gated behind an invite code they shared live on the stream. You connect with a Stellar wallet (Freighter in the demo) and land in a <strong>workspace</strong> — and you can manage several, one per business. Creating one is a guided onboarding: pick the business type (protocol, DAO, agency, freelancer), and the modules adapt — an agency doing dev work doesn't need heavy compliance tooling, a DAO very much does. You choose the operations you want (payments, treasury, risk reports, compliance), invite teammates, wire in integrations like Slack for transaction notifications or Gmail/Notion/Google Drive for the paperwork around employees and invoices, and set your geography so the risk and compliance reports (delivered daily to Telegram or WhatsApp) actually match your market.</p>
+<p>The payments demo was the simple, satisfying kind: create a payment of 10 XLM with a description, get a <strong>payment link</strong>, open it from a second wallet, pay — settled near-instantly, tracked in the dashboard. XLM and USDC are supported today, with more assets planned. For real integrations there's a <strong>developer portal</strong> with API keys, docs, and an SDK, plus an <strong>MCP</strong> in the works so you can wire Hypertron into your app from an AI tool in minutes. To make it tangible, Soumik built a demo app <em>that day</em>: a Pokémon NFT marketplace with Hypertron checkout. Buy an NFT, get redirected to the payment link, pay, and a <strong>webhook</strong> bounces you back to the marketplace with the NFT already in your account. The stablecoin payment stack and APIs are live now, with the full v1 targeted about two weeks out.</p>
+<p>On monetization: honest answer, still being figured out — likely pay-per-use across the smaller features rather than a cut of payments alone. One of those features is <strong>bridging</strong>: a business already operating on Ethereum, Solana, or Avalanche can move its treasury over to Stellar specifically to use the privacy payments. That's a fun acquisition channel if it works.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="the-privacy-stack">The Privacy Stack<a href="https://developers.stellar.org/meetings/2026/07/23#the-privacy-stack" class="hash-link" aria-label="Direct link to The Privacy Stack" title="Direct link to The Privacy Stack" translate="no">​</a></h3>
+<p>Sweta took the second half, and this is where it gets interesting for protocol nerds. Their framing: privacy isn't a rule, it's a <strong>spectrum</strong>, and it doesn't start with a circuit — it starts with the question <em>what needs to be hidden</em>. They've built a private-payments evaluation framework around six leakage dimensions: <strong>sender, receiver, amount, timing, linkability, and metadata</strong>. Confidential tokens, for contrast, hide the amount but leave sender and receiver public. Hypertron's target is <strong>linkability</strong> — nobody should be able to learn who pays whom — while keeping compliance deliberately open through <strong>viewing keys</strong>, so an auditor with the right key can still see what regulators need to see. Their privacy matrix today: sender, receiver, amount, and linkability covered; timing still partial (that's a batching-and-delay problem); compliance intentionally left open. In the app it'll surface as an <strong>opt-in privacy button</strong> on otherwise normal transparent payments.</p>
+<p>The architecture, in one breath: proofs are generated <strong>locally</strong> (the provers never leave your device), a <strong>relayer</strong> sponsors fees and submits, commitments land as leaves in an on-chain <strong>Merkle tree</strong>, and <strong>nullifiers</strong> handle spend-tracking. Four contracts ship the whole thing — commitments, nullifier, verifier, and a transfer contract that orchestrates shielding, sending, and unshielding with a single integration point for the merchant app.</p>
+<p>What I liked most is that they're packaging it twice. For protocol builders there are <strong>composable Rust crates</strong> — Merkle trees, nullifiers, proof verification, disclosure mechanisms — so you can assemble your own privacy design instead of rebuilding from scratch: relayers plus a ZK pool if you care about sender privacy, confidential tokens for payroll, a mixture with auditing for treasury settlements, pooling-batching-delay for anonymous donations. For application builders there's an <strong>npm package</strong> with a compiled WASM prover, so you generate proofs without ever touching the cryptography. Everything leans on the primitives the protocol now ships natively — the BLS12-381 pairings that landed in Protocol 22 and the Poseidon hashing from January's <strong>X-Ray (Protocol 25)</strong> upgrade — rather than porting verifier and hashing libraries in. That's also their differentiation pitch against Nethermind's <strong>SPP</strong> shielded pool: shielded pools go back to Zcash in 2016, and Hypertron's angle is composing the on-protocol primitives instead of shipping a ported stack. When I asked why BLS12-381 over BN254 (the more common choice for shielded pools), the answer was refreshingly honest: not entirely sure yet, the goal is fast verifiable circuits. Pools are per-asset — XLM first, more later.</p>
+<p>The CLI demo walked the real flow: query the last indexed Merkle root, compute a Poseidon commitment from secret inputs, run the deposit — commitment on-chain, proof generated and submitted, transaction shielded. Then the private-transfer proof failed on an indexing error, live, in front of 200+ people. As regular viewers know the rule by now: you're not a real builder if your demo works every time.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="the-fine-print">The Fine Print<a href="https://developers.stellar.org/meetings/2026/07/23#the-fine-print" class="hash-link" aria-label="Direct link to The Fine Print" title="Direct link to The Fine Print" translate="no">​</a></h3>
+<p>My PSA from the stream, repeated here for the record: Hypertron is a project in development, running on <strong>testnet</strong>. These things <em>should</em> happen — that's the point of showing them — but it's not a live business yet, so don't route your company's treasury anywhere just yet. The open-sourced v2 of the contracts was days away at recording, and viewers were already asking about integration pricing live on the stream, which is honestly the best kind of validation a pre-launch project can get. Follow them at x.com/hypertron_HQ.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="closing">Closing<a href="https://developers.stellar.org/meetings/2026/07/23#closing" class="hash-link" aria-label="Direct link to Closing" title="Direct link to Closing" translate="no">​</a></h2>
+<p>X-Ray has been live for about six months now, and privacy on Stellar still fascinates me — we've gone from protocol primitives to confidential tokens to shielded pools, and now to teams like Hypertron trying to be the B2B application layer on top of all of it. A private payments product for businesses is a whole different level of hard, and I'd love to see more projects emerge in this lane. We crossed <strong>250 live viewers</strong> by the end — thank you for that. Next week I'm planning a session on the cross-chain interop options available to Stellar builders, plus another guest. See you then.</p>]]></content>
+        <author>
+            <name>Kaan Kacar</name>
+            <uri>https://github.com/kaankacar</uri>
+        </author>
+        <category label="developer" term="developer"/>
+    </entry>
+    <entry>
+        <title type="html"><![CDATA[2026-07-16]]></title>
+        <id>https://developers.stellar.org/meetings/2026/07/16</id>
+        <link href="https://developers.stellar.org/meetings/2026/07/16"/>
+        <updated>2026-07-16T00:00:00.000Z</updated>
+        <summary type="html"><![CDATA[The Week I Mostly Shut Up]]></summary>
+        <content type="html"><![CDATA[<div class="youtubeEmbed" style="position:relative;width:100%;padding-bottom:56.25%;height:0;margin-bottom:23px"><iframe src="https://www.youtube-nocookie.com/embed/Zv_scYurQMI?rel=0&amp;modestbranding=1" title="Informational explainer" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" style="position:absolute;top:0;left:0;width:100%;height:100%;border:0px;border-radius:25pt"></iframe></div>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="the-week-i-mostly-shut-up">The Week I Mostly Shut Up<a href="https://developers.stellar.org/meetings/2026/07/16#the-week-i-mostly-shut-up" class="hash-link" aria-label="Direct link to The Week I Mostly Shut Up" title="Direct link to The Week I Mostly Shut Up" translate="no">​</a></h2>
+<p>Probably my favorite Stellar Developers meeting so far, and — unusually for me — I spent most of it not talking. The occasion: introducing <strong>Stellar Raven</strong>, the unified Stellar-ecosystem MCP gateway. My pitch in one line: the first, last, and only thing you need to build on Stellar — Stellar docs and ecosystem context in one connection. You might think "oh, it's just an MCP." You would be mistaken, and I brought four guests to explain why.</p>
+<p>Quick introductions. <strong>Bri</strong> has been on the ecosystem team at the foundation for about four and a half years and does a lot of the storytelling around what Tyler builds — a job description that now includes Raven. <strong>Boxy</strong> built <strong>Stellar Light</strong> and focuses on data indexing: making ecosystem data smart and high-quality enough that Raven keeps getting smarter from it. <strong>Ralph</strong> wears many hats in the ecosystem but joined as the builder of <strong>Lumen Loop</strong> (lumenloop.com), a discovery platform for everything happening on Stellar. And <strong>Tyler</strong> — still a developer advocate director, and together with Bri quietly spinning off a new team inside the foundation to work on exactly this kind of thing. Don't tell anybody.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="what-raven-actually-is">What Raven Actually Is<a href="https://developers.stellar.org/meetings/2026/07/16#what-raven-actually-is" class="hash-link" aria-label="Direct link to What Raven Actually Is" title="Direct link to What Raven Actually Is" translate="no">​</a></h2>
+<p>Tyler's framing: the problem Raven solves is <strong>context</strong>. It's an MCP (Model Context Protocol) server that aims to ensure agents know the <em>truth</em> about Stellar when you ask a question or build something.</p>
+<p>The corpus of Stellar truth is scattered, and some of that is structural. We're open source with a very open culture, so a lot of what's true about Stellar lives outside the foundation's control. We run a hackathon on one SDK version, ship a new release two months later, and now SEO is actively working against us: LLMs index a pile of once-true, now-outdated information. Everyone builds off a Blend or Soroswap repo at a hackathon; those repos are static (you can't update deployed contracts), so freshly generated content keeps encoding stale best practices. Recency is a bad signal when the new content was generated off the old standards; scoring what's actually true is genuinely tricky.</p>
+<p>Tyler had solved this for himself with a personal deep-research workflow, but "install these ten skills and four MCP servers" is not a shippable product. Raven is that build workflow surfaced as a single service — the <strong>fifth version</strong> he's tried to build over almost a year, and it only got serious once Lumen Loop and Stellar Light/Scout existed as APIs he could route to. Under the hood, Raven pulls together <strong>Lumen Loop</strong>, <strong>Stellar Light</strong>, the <strong>Stellar docs</strong>, all the <strong>Stellar skills</strong>, and the <strong>Algolia</strong> indexes behind the docs and the site, plus general research tools like Parallel and Perplexity in the research pipeline.</p>
+<p>The broader thesis: anyone seriously evaluating chains is comparing Stellar against several ecosystems, each with its own sprawl of bespoke skills and MCPs. Nobody maintains all that. If we want people to give Stellar a fair chance with their LLMs, there has to be <strong>one tool</strong>. That's the niche.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="the-sources-lumen-loop-and-stellar-light">The Sources: Lumen Loop and Stellar Light<a href="https://developers.stellar.org/meetings/2026/07/16#the-sources-lumen-loop-and-stellar-light" class="hash-link" aria-label="Direct link to The Sources: Lumen Loop and Stellar Light" title="Direct link to The Sources: Lumen Loop and Stellar Light" translate="no">​</a></h2>
+<p>Ralph and Boxy overlap on purpose — two independent sources of ecosystem truth mean you can cross-check what works.</p>
+<p><strong>Lumen Loop</strong> is content-first and agentically driven: backend agents discover content, attach metadata, generate summaries and embeddings, look up SCF information, occasionally disagree with it and self-correct, and publish the result to an open <strong>ecosystem database on GitHub</strong> that others (like Boxy) build on. Ralph's favorite party trick lives at labs.lumenloop.com: a <strong>constellation view</strong> of the entire ecosystem — every piece of content and how it relates to everything else. We've never been able to see that before, and it's just one source behind Raven.</p>
+<p><strong>Stellar Light</strong> started as a discoverability problem and grew once agents entered the picture. Boxy's current frontier is <strong>repo indexing</strong>: ingesting thousands of repositories from Electric Capital and other sources and actually trying to understand the code depth inside each one, so questions get answered from real code rather than vibes. It's hard, and token-hungry — Boxy has been hitting model limits doing it.</p>
+<p>The shared hope: less time on the boring things. SCF reviews, hackathon judging, hunting for the right link — all of that is exactly the shape of work Raven quickens.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="truth-is-a-garden">Truth Is a Garden<a href="https://developers.stellar.org/meetings/2026/07/16#truth-is-a-garden" class="hash-link" aria-label="Direct link to Truth Is a Garden" title="Direct link to Truth Is a Garden" translate="no">​</a></h2>
+<p>The part I found most interesting is how Raven improves itself, because the core issue with LLMs is that <strong>they don't know when they're wrong</strong>. Give an agent disparate sources and superseded information and it will grab something, hold it confidently, and careen off a cliff in a burning cloud of tokens. MCPs don't fix that. Skills don't fix that. Continuous re-research of truth fixes that — Tyler's metaphor: truth is a <strong>garden</strong>, not granite. Things go live, die, migrate; somebody has to keep re-indexing and re-scoring. Concretely:</p>
+<ul>
+<li class=""><strong>Golden QA.</strong> The team mined Stack Exchange, Discord, and old Stella logs for almost <strong>500 common Stellar questions</strong>, then ran long, expensive research against each — Lumen Loop, Stellar Light, the docs, the site, web research — to produce golden answers.</li>
+<li class=""><strong>Evals.</strong> Ask Raven the same questions, have a model grade Raven's answer against the golden one, and — the fun part — assign blame. Is a miss a Lumen Loop problem? A Stellar Light problem? Are the docs missing something, or contradicted by a repo?</li>
+<li class=""><strong>The loop.</strong> Misses land in an improvements directory and become issues on the right repository, where Ralph's and Boxy's agents pick them up. Telemetry (the whole thing runs on Cloudflare) captures what tools got called and what came back, so agent flows can compare what Raven found against what it should have. Bri pointed out this already works in the other direction too: several issues open on the docs repo right now exist because Raven couldn't answer something correctly <em>from the docs</em> — Raven is making the docs better, not just consuming them.</li>
+</ul>
+<p>Two real examples of misses: asked about asset issuers in Latin America, Raven almost never surfaced <strong>Etherfuse</strong> — apparently they don't describe themselves as an asset issuer anywhere, even though everyone expects to find them under that word. And "where can I swap assets on Stellar" almost never returned <strong>Sushi</strong>, new on Stellar and competing with a crowd of existing swap services. Both became golden questions; both improved. When you hit something like this, open an issue on the Stellar Raven repo — that's the mechanism.</p>
+<p>Tyler's longer-term vision is <strong>forward-deployed agents</strong>: Raven plus opt-in memory and profiles, so an agent embedded with a partner learns you're always asking about, say, Argentine anchors, and gets more specific over time. You could stand up an agent today, hand it the Raven MCP and your Sentry logs, put it on a loop, and have it PR fee optimizations against your own repo. The pieces exist; they just need packaging.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="qa-live-data-cheap-models-and-where-to-run-it">Q&amp;A: Live Data, Cheap Models, and Where to Run It<a href="https://developers.stellar.org/meetings/2026/07/16#qa-live-data-cheap-models-and-where-to-run-it" class="hash-link" aria-label="Direct link to Q&amp;A: Live Data, Cheap Models, and Where to Run It" title="Direct link to Q&amp;A: Live Data, Cheap Models, and Where to Run It" translate="no">​</a></h2>
+<p>A viewer asked how much you can learn about real-life anchor operations — which turned into the best design discussion of the call: <strong>should Raven serve live data?</strong> Tyler's answer is no, mostly. Raven is a model <em>context</em> protocol, not a data API. It shouldn't call the RPC for you; it should tell your agent where the RPC docs are, who provides endpoints, and let <em>your</em> model write the code. Same for the recent explosion of data sources: <strong>Mercury</strong> (just came back, and very cool), <strong>stellarindexer.com</strong>, <strong>Alchemy's new Stellar API</strong>, Dune, the data-lake tooling like Galexie. Your agent doesn't know what it doesn't know — but once Raven points it at the right sources, your agent is the best tool for the job. Tyler's analogy, which I intend to steal: "I'm going to borrow your body to use my brain." We're giving the agent the tools, not building it the house.</p>
+<p>The same logic answers the hosted demo question. There's a <strong>playground</strong> on the Raven site, and you should treat it as exactly that: heavily rate-limited, a really cheap reasoning model, capped search/execute turns — Tyler is understandably not exposing hundreds of dollars of frontier-model compute to the open internet. Use it to see which tools get called and get a feel for the answers (we asked it "who is Justin Rice" live, and for a throttled setup it did honestly fine), but the real product is <strong>Raven installed in your own IDE or agent</strong>, where a frontier model gets far more out of the same context. That's also why there's a sign-in: a standard OAuth MCP login, needed for rate limiting today and the opt-in memory features later.</p>
+<p>Other questions from chat, rapid-fire:</p>
+<ul>
+<li class=""><strong>Test suites and security?</strong> Raven would be phenomenal at it as the repo indexing matures — find repos that already cover fuzz testing and common error patterns, then plug that into whatever monitors your backend. The follow-on idea everyone liked: index <strong>audit reports</strong>. Lumen Loop surfaces audits but only as links; the trick is accurate summaries so Raven knows <em>when</em> an audit is relevant, then hands your agent the full source. Same pattern as Raven's planned <strong>ephemeral artifacts</strong> for oversized responses — just the right context at just the right time.</li>
+<li class=""><strong>Does Raven speak Spanish?</strong> Whatever your terminal speaks. The proxied APIs are mostly English semantic search, but your agent translates on both ends.</li>
+<li class=""><strong>Can we make a sassy Raven?</strong> Wrap it in your own agent and give it whatever personality you want — one of the crew confessed theirs answers as Princess Donut from Dungeon Crawler Carl. Mine calls me Mr. Kaan. I want professional distance from my agent.</li>
+<li class=""><strong>Is this a Stella replacement?</strong> Different animal. Tyler was blunt: Stella was a great experiment and he's glad it died — it made Discord unsearchable, a huge share of prompts were vandalism attempts or non-Stellar questions, and an agent-as-a-service collects PII you then have to worry about. Raven inverts the model: a service that <em>your</em> agent calls, with tool-use-shaped telemetry instead of raw prompts. My addition: Stella existed because models couldn't read our docs properly back then. Frontier models read docs fine now — the scarce thing is dynamic, current ecosystem context, and that's precisely what Raven addresses.</li>
+</ul>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="tangents-worth-keeping">Tangents Worth Keeping<a href="https://developers.stellar.org/meetings/2026/07/16#tangents-worth-keeping" class="hash-link" aria-label="Direct link to Tangents Worth Keeping" title="Direct link to Tangents Worth Keeping" translate="no">​</a></h2>
+<p>Building this stuff is not cheap: Tyler estimated around <strong>20 billion tokens</strong> in the last couple of weeks alone. That led into a review of token-saving tools — <strong>headroom</strong> (compresses JSON and log output), <strong>caveman</strong> (make prose short, why speak much when few word do trick), and <strong>ponytail</strong> (don't over-engineer; less code when little code does the trick). Verdict: modern models are too smart to be talked to stupidly. Headroom-style compression made them suspicious they were missing something, so they looped and burned <em>more</em> tokens; caveman's brevity triggered extra reasoning to reconstruct the stripped context. Only ponytail earned its keep, and less for token savings than for code quality. If you're going to install one, install that one.</p>
+<p>Best mini case study of the call came from Bri, who is building an application with confidential token transfers and used Raven as a <strong>research tool</strong>: "Alice owns 1,000 USDC, Bob owns 300; Alice deposits 500 into the confidential token wrapper and privately transfers 200 to Bob — walk me through step by step what happens." Raven's answer taught Bri more about confidential transfers than a week of reading. Researching with Raven is as legitimate a use case as building with it — and it's not a one-and-done oracle. Ask, learn a little, redirect, pair it with your other tools.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="closing">Closing<a href="https://developers.stellar.org/meetings/2026/07/16#closing" class="hash-link" aria-label="Direct link to Closing" title="Direct link to Closing" translate="no">​</a></h2>
+<p>We peaked around 380 live viewers, blew past the hour as usual, and rolled into the protocol discussion half an hour later. Brazilian builders: we'll be at the <strong>Stellar Builder Summit</strong> in São Paulo — find me there and ask me about Raven. Otherwise, ask on the Discord or tag Tyler (@kalepail), Lumen Loop, Boxy, or Bri on X. Every question makes Raven better.</p>
+<p>Also, I publicly demanded Raven swag. A bandana would be sick. Slogan's already written: <em>just ask the Raven.</em> See you next week.</p>]]></content>
+        <author>
+            <name>Kaan Kacar</name>
+            <uri>https://github.com/kaankacar</uri>
+        </author>
+        <category label="developer" term="developer"/>
+    </entry>
+    <entry>
+        <title type="html"><![CDATA[2026-07-02]]></title>
+        <id>https://developers.stellar.org/meetings/2026/07/02</id>
+        <link href="https://developers.stellar.org/meetings/2026/07/02"/>
+        <updated>2026-07-02T00:00:00.000Z</updated>
+        <summary type="html"><![CDATA[A Week About Privacy]]></summary>
+        <content type="html"><![CDATA[<div class="youtubeEmbed" style="position:relative;width:100%;padding-bottom:56.25%;height:0;margin-bottom:23px"><iframe src="https://www.youtube-nocookie.com/embed/N7PtAJaELzA?rel=0&amp;modestbranding=1" title="Informational explainer" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" style="position:absolute;top:0;left:0;width:100%;height:100%;border:0px;border-radius:25pt"></iframe></div>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="a-week-about-privacy">A Week About Privacy<a href="https://developers.stellar.org/meetings/2026/07/02#a-week-about-privacy" class="hash-link" aria-label="Direct link to A Week About Privacy" title="Direct link to A Week About Privacy" translate="no">​</a></h2>
+<p>This week wasn't about AI — it was about your second-favorite subject: <strong>privacy</strong>. Per the Electric Capital developer report there are now more than <strong>2,000 developers building on Stellar</strong> in a given week, and hopefully you're one of them.</p>
+<p>Two reasons privacy was the theme. First, there was exactly <strong>one day left</strong> to submit to the Real World ZK hackathon on DoraHacks — the best possible time to be building with zero knowledge. Second, an hour before the call we published the <strong>developer preview of confidential tokens</strong> on Stellar, which pairs naturally with this week's guest. So the plan was: guest first, then a plain-English tour of confidential tokens.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="guest-zarf--private-token-distribution-by-email">Guest: Zarf — Private Token Distribution by Email<a href="https://developers.stellar.org/meetings/2026/07/02#guest-zarf--private-token-distribution-by-email" class="hash-link" aria-label="Direct link to Guest: Zarf — Private Token Distribution by Email" title="Direct link to Guest: Zarf — Private Token Distribution by Email" translate="no">​</a></h2>
+<p>Our guest was <strong>Zarf</strong> (zarf.to), a Turkish project that lets you distribute tokens to an <strong>email address</strong> rather than a wallet address. Recipients claim with a familiar "sign in with Google" button, and their browser quietly proves they own that email using a zero-knowledge proof — so the recipient's wallet is never linked to a person, and nothing on-chain says who received what. This was a special one for me personally: <strong>Yaman</strong>, one of the founders, is the first person I ever met in web3, at my first hackathon a bit over four years ago.</p>
+<p>Yaman introduced Zarf alongside <strong>Dennis</strong>, who has spent three to four years in the ZK space (previously an exploration engineer at O1 Labs on the Mina protocol, and before that in web2 cyber security). The team builds things that are only possible with zero-knowledge proofs, and got excited about Stellar once the protocol gained <strong>native, cheap ZK-proof verification</strong> — with the heavy elliptic-curve math implemented as protocol-level precompiles, verifying a proof on Stellar became genuinely inexpensive.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="the-problem">The Problem<a href="https://developers.stellar.org/meetings/2026/07/02#the-problem" class="hash-link" aria-label="Direct link to The Problem" title="Direct link to The Problem" translate="no">​</a></h3>
+<p>When you send tokens on a blockchain, the recipient's wallet is always exposed. In token distributions and private sales, anyone can watch who claimed what — a strong signal for whales-watching and an easy way to get doxxed. Zarf's origin was a hackathon project at Devconnect in Buenos Aires: a proof-of-attendance tool that let you <em>prove</em> you'd attended an event via an email you received, then mint it as a POAP-style NFT. That grew into the more general idea of using an identity you already have — a Google account — for private, programmable token distributions.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="how-it-works">How It Works<a href="https://developers.stellar.org/meetings/2026/07/02#how-it-works" class="hash-link" aria-label="Direct link to How It Works" title="Direct link to How It Works" translate="no">​</a></h3>
+<p>The primitive underneath Zarf is <strong>ZK JWT</strong> — zero-knowledge proofs over the JSON Web Token that Google signs when you log in. When you sign in with Google, Google digitally signs your JWT; inside the circuit, Zarf verifies that signature against Google's published public keys, confirms the key really belongs to Google, and parses your email — all in zero knowledge. That proof then lets you <strong>claim from any wallet you like</strong>, and different claims can come from totally unlinked wallets (wallet A for one batch, wallet B for the next), even a single-use stealth address.</p>
+<p>Dennis was careful to distinguish ZK JWT from <strong>ZK email</strong>: ZK email proves the signature of an email's <em>sender</em>, while ZK JWT is specifically for authentication and identity. They prefer ZK JWT because the UX is far better — no forwarding emails or uploading <code>.eml</code> files; you just open the page and log in with Google, and the proof is generated behind the scenes.</p>
+<p>The best framing we landed on: Zarf is a <strong>privacy-focused version of the Stellar disbursement platform</strong> — instead of handing over a CSV of wallet addresses, you hand over emails, and people claim from whatever wallet they want, so nobody can track balances or link an identity to a wallet.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="the-architecture">The Architecture<a href="https://developers.stellar.org/meetings/2026/07/02#the-architecture" class="hash-link" aria-label="Direct link to The Architecture" title="Direct link to The Architecture" translate="no">​</a></h3>
+<p>A few implementation details worth capturing:</p>
+<ul>
+<li class=""><strong>Proof system.</strong> Zarf uses <strong>Noir</strong> rather than Circom. Noir brings faster proof generation and, importantly, <strong>no per-circuit trusted setup ceremony</strong> (it relies on a universal setup instead).</li>
+<li class=""><strong>Four contracts.</strong> A factory, a vesting contract, a verifier contract (invoked on every claim to check the proof), and a <strong>JWK registry</strong> that holds Google's public keys.</li>
+<li class=""><strong>The Google key-rotation challenge.</strong> Google rotates the public keys that sign JWTs roughly every two weeks (not exactly, and not all at once). Zarf runs a <strong>Cloudflare worker</strong> that fetches the current keys and writes them on-chain so verification stays valid. This is the biggest open problem; the team is exploring more trustless approaches (e.g. zkTLS to prove the certificate URL directly) and even offering a shared Google-certificate registry as a public good for the whole ecosystem.</li>
+<li class=""><strong>The privacy model.</strong> To break the email↔wallet link, Zarf parses your email from the JWT, generates a secret <strong>pin code</strong>, hashes the pin, hashes your email, and places the hashed identity in a <strong>Merkle tree</strong>. At claim time the circuit verifies the Google-signed JWT, derives your unique identifier, walks the Merkle proof to the root, and compares that root against the distributor's on-chain vesting contract. The pin prevents anyone who merely knows your email from brute-forcing to find you in the tree.</li>
+</ul>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="the-demo">The Demo<a href="https://developers.stellar.org/meetings/2026/07/02#the-demo" class="hash-link" aria-label="Direct link to The Demo" title="Direct link to The Demo" translate="no">​</a></h3>
+<p>Yaman created a live token distribution on testnet — upload an email list, auto-build the Merkle tree, set a vesting schedule, deploy — then tried to claim. Proof generation and some caching got in the way and the claim didn't land cleanly on the call (it had worked in rehearsal). As I like to say: you're not really a builder if your demo works every time. It's a fine reminder of exactly why beta testers matter — better to get roasted in private than in front of 250 live viewers. Zarf is <strong>SCF cohort 42</strong>, heading to mainnet after its audit (likely within the week), and looking for beta testers via zarf.to and X (@zarf).</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="confidential-tokens-the-other-half-of-privacy">Confidential Tokens: The Other Half of Privacy<a href="https://developers.stellar.org/meetings/2026/07/02#confidential-tokens-the-other-half-of-privacy" class="hash-link" aria-label="Direct link to Confidential Tokens: The Other Half of Privacy" title="Direct link to Confidential Tokens: The Other Half of Privacy" translate="no">​</a></h2>
+<p>After the guests left, I did a "so what?" walkthrough of the <strong>confidential token rails</strong> we previewed that day, built by OpenZeppelin — because Zarf and confidential tokens solve two <em>different</em> privacy problems and it's worth seeing the contrast:</p>
+<ul>
+<li class=""><strong>Zarf hides identity.</strong> The email↔wallet link is never revealed. But once a claim lands, the recipient's wallet, the amount, and the claim event are all still public on-chain — fine in many cases, problematic in others.</li>
+<li class=""><strong>Confidential tokens hide amounts.</strong> Instead of storing a plaintext balance, the token stores each balance as an <strong>encrypted commitment</strong>. Transfers move encrypted amounts and carry a zero-knowledge proof that the transfer is <em>valid</em> (the sender had enough, the amount is a positive integer, inputs equal outputs) <strong>without revealing any of the amounts</strong>. Only the holder — and optionally an <strong>auditor</strong> who holds a decryption key — can read the balance, which is how you'd add a compliance layer.</li>
+</ul>
+<p>The mental model is a handful of methods: <strong>register, deposit, merge, transfer, withdraw</strong>. To participate at all you first <strong>register</strong> (a one-time zero-knowledge proof generated locally in the browser). You then <strong>deposit</strong> public tokens into your encrypted balance, <strong>merge</strong> received amounts so they become spendable, and <strong>transfer</strong> confidentially. Confidential tokens behave like SEP-41 tokens, so in theory they compose — but they're best at <strong>additive accounting</strong> (adding and subtracting amounts), and not the right tool for multiplication, price discovery, or deep public composability, where time-sensitive proof generation gets in the way. This is a confidential <em>token</em>, not a dark pool that hides the operation itself.</p>
+<p>To make it concrete I vibe-coded a tiny <strong>confidential wallet</strong> for the meeting — two accounts, Alice and Bob — that walks through registering, depositing public XLM into an encrypted balance, merging, and then transferring confidentially so nobody can see how much moved. It reuses OpenZeppelin's confidential-token contract from the developer preview, so I was cutting corners, but it makes the flow tangible. The GitHub link is in the stream, and the real source of truth is the developer preview itself.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="closing">Closing<a href="https://developers.stellar.org/meetings/2026/07/02#closing" class="hash-link" aria-label="Direct link to Closing" title="Direct link to Closing" translate="no">​</a></h2>
+<p>With ~20 hours left on the Real World ZK hackathon deadline and a strong turnout of hackers, there was still time to ship something small and submit. Next week's guest is Hyperron. Thanks for watching — see you then.</p>]]></content>
+        <author>
+            <name>Kaan Kacar</name>
+            <uri>https://github.com/kaankacar</uri>
+        </author>
+        <category label="developer" term="developer"/>
+    </entry>
+    <entry>
+        <title type="html"><![CDATA[2026-06-25]]></title>
+        <id>https://developers.stellar.org/meetings/2026/06/25</id>
+        <link href="https://developers.stellar.org/meetings/2026/06/25"/>
+        <updated>2026-06-25T00:00:00.000Z</updated>
+        <summary type="html"><![CDATA[Another Doozy of a Week]]></summary>
+        <content type="html"><![CDATA[<div class="youtubeEmbed" style="position:relative;width:100%;padding-bottom:56.25%;height:0;margin-bottom:23px"><iframe src="https://www.youtube-nocookie.com/embed/xqBgocb6bCM?rel=0&amp;modestbranding=1" title="Informational explainer" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" style="position:absolute;top:0;left:0;width:100%;height:100%;border:0px;border-radius:25pt"></iframe></div>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="another-doozy-of-a-week">Another Doozy of a Week<a href="https://developers.stellar.org/meetings/2026/06/25#another-doozy-of-a-week" class="hash-link" aria-label="Direct link to Another Doozy of a Week" title="Direct link to Another Doozy of a Week" translate="no">​</a></h2>
+<p>Before the guests, a quick bit of ecosystem context for why this week felt busy. Per the on-chain data, <strong>Stellar's RWA market cap just crossed $3 billion</strong> — you can see it for yourself on the Dune dashboards. And the ideal Stellar developer meeting, in my book, is one with as many guests as possible, because the conversation I keep having with projects is that they want a real way <em>into</em> the ecosystem. Contributing is one way; introducing yourself on this call is another. This week we had two guests and, with a bit of luck, a new viewer record.</p>
+<p>We also had four days left to submit to the <strong>Real World ZK hackathon on DoraHacks</strong> — more on that from our second guest below.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="guest-gaian--stablecoin-rails-for-southeast-asia">Guest: Gaian — Stablecoin Rails for Southeast Asia<a href="https://developers.stellar.org/meetings/2026/06/25#guest-gaian--stablecoin-rails-for-southeast-asia" class="hash-link" aria-label="Direct link to Guest: Gaian — Stablecoin Rails for Southeast Asia" title="Direct link to Guest: Gaian — Stablecoin Rails for Southeast Asia" translate="no">​</a></h2>
+<p>Our first guest was <strong>Gaian</strong> (gaian.network), a stablecoin payment infrastructure for the APAC region. In one sentence: it's an API that connects crypto wallets to local banking rails using <strong>USDC on Stellar</strong>, moving value between stablecoins and local currencies like the Vietnamese dong to power merchant payments, on/off ramps, and cross-border transfers that settle straight into real bank accounts. Imagine paying for a coffee in Hanoi straight from your Freighter, Albedo, or Beans wallet — that's the promise. Kelvin walked us through it live from Vietnam (at 1 a.m. his time).</p>
+<p>Gaian isn't new — the team has been at it for over a year and pivoted twice; what they demoed is the <strong>v2</strong> of the API. They're live across APAC (Vietnam, the Philippines, part of Thailand) plus Brazil and Peru, and in Vietnam and the Philippines they operate as the <strong>anchor themselves</strong>, working directly with the top banks.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="how-the-flow-works">How the Flow Works<a href="https://developers.stellar.org/meetings/2026/06/25#how-the-flow-works" class="hash-link" aria-label="Direct link to How the Flow Works" title="Direct link to How the Flow Works" translate="no">​</a></h3>
+<p>There are several actors but only one payment. A consumer holding USDC talks to a wallet; the wallet talks to the Gaian API; Gaian uses the blockchain as the settlement layer and a partner PSP in the destination country to land fiat in the merchant's bank account. Crucially, <strong>the merchant sees no blockchain at all</strong> — they just receive fiat.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="authentication">Authentication<a href="https://developers.stellar.org/meetings/2026/06/25#authentication" class="hash-link" aria-label="Direct link to Authentication" title="Direct link to Authentication" translate="no">​</a></h3>
+<p>The v2 API authenticates every request with an <strong>HMAC signature</strong>. You get an API key and secret from the self-service dashboard, build a canonical message out of the timestamp, method, path, query, and body, HMAC it with your secret, and base64-encode the result. Every request must carry that signature and timestamp.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="the-order-lifecycle">The Order Lifecycle<a href="https://developers.stellar.org/meetings/2026/06/25#the-order-lifecycle" class="hash-link" aria-label="Direct link to The Order Lifecycle" title="Direct link to The Order Lifecycle" translate="no">​</a></h3>
+<p>There are two halves — onboarding a user, then placing an order:</p>
+<ol>
+<li class=""><strong>Onboarding.</strong> Create a user (<code>POST /v2/users</code>), associate a wallet address to that user (the address is just a string — the wallet provider controls it), then generate a <strong>KYC URL</strong> for the user (providers vary by country) and poll their status by ID or wallet address until it's approved.</li>
+<li class=""><strong>Payment.</strong> Ask Gaian for a code by passing the scanned <strong>QR string</strong>, the fiat amount, and the user's wallet address. Gaian returns a code ID, the fiat amount, the total (including the bank's processing fee), the exchange rate, and the decoded bank details. Then <strong>place the order</strong> with that code ID — Gaian returns an order ID, a status label, the settlement wallet address, and the token address (USDC today). The wallet <strong>signs and broadcasts</strong> the USDC transfer to the settlement wallet (not an API call), and finally notifies Gaian with the transaction hash so Gaian can verify it on-chain and mark the order settled (there's no automatic chain listener yet). There's also a <strong>prefund</strong> flow where a wallet pre-funds stablecoin with Gaian.</li>
+</ol>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="the-demo">The Demo<a href="https://developers.stellar.org/meetings/2026/06/25#the-demo" class="hash-link" aria-label="Direct link to The Demo" title="Direct link to The Demo" translate="no">​</a></h3>
+<p>Kelvin ran the whole thing live from a Bruno collection and a demo wallet, paying ~21,000 VND (under a dollar, with a small minimum bank fee) to a real Vietnamese bank account. The first code expired mid-explanation — a hazard of a good demo — and re-verifying settled it. The real headline: the <strong>self-service dashboard</strong> means any viewer can sign up, grab API keys, and integrate Gaian's payment capability into their own wallet without ever talking to sales, up to a ~$4,000 cap before KYB is required.</p>
+<p>Gaian went <strong>live on Stellar</strong> the previous Friday, and for now it's mainnet-only — going fast to production rather than testnet-first. The one thing I asked for repeatedly (and will keep pestering them about) is a <strong>self-service sandbox on testnet</strong>, so we can amplify Gaian as an anchor to builders across the Philippines and Vietnam.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="the-real-world-zk-hackathon">The Real World ZK Hackathon<a href="https://developers.stellar.org/meetings/2026/06/25#the-real-world-zk-hackathon" class="hash-link" aria-label="Direct link to The Real World ZK Hackathon" title="Direct link to The Real World ZK Hackathon" translate="no">​</a></h2>
+<p>Our second guest was <strong>Jeremy</strong> (also known as J Romero), the ecosystem partner running the <strong>Real World ZK hackathon</strong> on DoraHacks. The scope is deliberately wide open: anything that touches zero knowledge on Stellar qualifies — privacy pools, private payments, confidential tokens, verifiable computation, even ZK games.</p>
+<p>The news he dropped live: for the first time ever, they <strong>extended the deadline</strong> by about a week, so it lands just before the US holiday (giving builders more time and keeping judging off the judges' holiday plates). The prize pool is <strong>$10,000 in XLM</strong> across five places ($5,000 for first down to $750 for fifth), plus a random $100 in XLM for someone who fills out the feedback survey. Requirements are light — an open-source repo and a short demo video.</p>
+<p>Everything runs on <strong>DoraHacks</strong> (search "Stellar"), but the real hub is the dedicated <strong>Telegram group</strong> (1,000+ people), where ecosystem ZK teams — Nethermind, Boundless, OpenZeppelin, Aztec — hang out to help. A prolific builder who's won three prior Stellar hackathons (including the ZK Gaming one) is helping as a mentor this round. There's also a resources tab on the hackathon page you can point your AI at, and office hours were being scheduled. Jeremy's parting advice: don't let AI name your project (three teams showed up with identical AI-generated names), and build the thing <em>you're</em> passionate about — Stellar has always been about local builders shipping local solutions.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="closing">Closing<a href="https://developers.stellar.org/meetings/2026/06/25#closing" class="hash-link" aria-label="Direct link to Closing" title="Direct link to Closing" translate="no">​</a></h2>
+<p>I also gave a shout to the <strong>Pulso hackathon</strong> in São Paulo (on DoraHacks), whose prize includes a fully sponsored trip to the Stellar Summit, with live pitches across Argentina, Brazil, and Colombia. I'd planned to close with a live <code>stellar-build</code> session — using the Justin and Nicole personas to show off the new self-running loop and spin up a ZK project idea — but at 75 minutes and seven cups of coffee deep, I saved it for next week. Next week we also have another guest, so please be there.</p>]]></content>
+        <author>
+            <name>Kaan Kacar</name>
+            <uri>https://github.com/kaankacar</uri>
+        </author>
+        <category label="developer" term="developer"/>
+    </entry>
+    <entry>
+        <title type="html"><![CDATA[2026-06-18]]></title>
+        <id>https://developers.stellar.org/meetings/2026/06/18</id>
+        <link href="https://developers.stellar.org/meetings/2026/06/18"/>
+        <updated>2026-06-18T00:00:00.000Z</updated>
+        <summary type="html"><![CDATA[A Doozy of a Week]]></summary>
+        <content type="html"><![CDATA[<div class="youtubeEmbed" style="position:relative;width:100%;padding-bottom:56.25%;height:0;margin-bottom:23px"><iframe src="https://www.youtube-nocookie.com/embed/9dfzsu5ChCM?rel=0&amp;modestbranding=1" title="Informational explainer" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" style="position:absolute;top:0;left:0;width:100%;height:100%;border:0px;border-radius:25pt"></iframe></div>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="a-doozy-of-a-week">A Doozy of a Week<a href="https://developers.stellar.org/meetings/2026/06/18#a-doozy-of-a-week" class="hash-link" aria-label="Direct link to A Doozy of a Week" title="Direct link to A Doozy of a Week" translate="no">​</a></h2>
+<p>This week was a doozy — not just one exciting guest, but a pile of news and a stack of tools to use and maybe break. Before the guest, a quick ecosystem roundup. The big one: <strong>v16 of the JavaScript SDK is live</strong>. If you're building on the JS SDK, upgrade your codebase and read the release notes to see what changed. Ask in the Stellar Developers Discord if anything trips you up.</p>
+<p>Two more things worth your time. Our <strong>Real World ZK hackathon</strong> with onlyhacks is still running — 11 days left to submit, $10,000 in prizes. The brief is simple: build anything that uses zero knowledge and runs on Stellar — privacy pools, private payments, confidential tokens, identity and compliance proofs, provable computation, verifiable data. If it's ZK and it's on Stellar, it counts.</p>
+<p>And if your team is closer to launch, <strong>SDF and CV Labs have opened the Stellar CV Labs Accelerator</strong> — SDF's first EMEA-focused program. It's a 12-week remote-first accelerator with a two-week in-person boot camp in Cape Town, supporting 10 early-stage startups across DeFi, payments, and RWA in the ME region. Selected teams get technical support, tokenomics advisory, go-to-market guidance, mentor 1:1s, ecosystem perks, and up to <strong>$150,000 in XLM</strong> in initial development funding from SDF. Post-program, top teams are eligible for additional SDF grants and a joint IC review with CVVC's fund — up to another $150k per team for the top two. Applications are open until <strong>July 3rd</strong>.</p>
+<p>For context on why any of this matters: per the Electric Capital developer report, close to <strong>1,800 builders</strong> shipped on Stellar this week, and we had nearly 150 builders live on the call when we started (peaking past 470 by the end). There's a synergy here, and I hope you can feel it too.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="guest-xccy--a-fixed-rate-engine-for-defi">Guest: XCCY — A Fixed-Rate Engine for DeFi<a href="https://developers.stellar.org/meetings/2026/06/18#guest-xccy--a-fixed-rate-engine-for-defi" class="hash-link" aria-label="Direct link to Guest: XCCY — A Fixed-Rate Engine for DeFi" title="Direct link to Guest: XCCY — A Fixed-Rate Engine for DeFi" translate="no">​</a></h2>
+<p>This week's guest was <strong>XCCY</strong> (short for <strong>cross-currency swaps</strong>) — an on-chain interest rate engine that's integrating to Stellar. The pitch: lock in a fixed yield on stablecoins, borrow at a fixed rate for a known period, and hedge variable interest rates instead of guessing where yields will go. Their current platform already shows around $1M in liquidity and roughly $2M in 24-hour volume.</p>
+<p><strong>Dennis</strong> (co-founder and CEO; background in math/CS, several DeFi protocols, and HFT trading) and <strong>Dmitri</strong> (CPO; a TradFi derivatives background) walked us through it. XCCY was accepted into <strong>SCF's 41st cohort</strong>, is deployed on EVM mainnets today, and started building on Stellar two weeks ago.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="the-problem">The Problem<a href="https://developers.stellar.org/meetings/2026/06/18#the-problem" class="hash-link" aria-label="Direct link to The Problem" title="Direct link to The Problem" translate="no">​</a></h3>
+<p>There's a huge amount of unhedged floating-rate exposure across DeFi. In TradFi this is solved with an <strong>interest rate swap</strong> — a derivative that lets you exchange a fixed, predefined rate for a floating rate tied to some source (Fed funds rate, or in DeFi a lending market's borrow/lend rate). XCCY brings that primitive on-chain, leaning into an RWA-looping narrative and fixed rates on Stellar — natural given the depth of RWAs and lending markets like Blend and YieldBlox on the network.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="three-primitives">Three Primitives<a href="https://developers.stellar.org/meetings/2026/06/18#three-primitives" class="hash-link" aria-label="Direct link to Three Primitives" title="Direct link to Three Primitives" translate="no">​</a></h3>
+<p>Dennis demoed the platform (live, on Stellar testnet, network errors and all) and the math behind it:</p>
+<ol>
+<li class=""><strong>Oracle Hub</strong> — XCCY uses two oracle types. <strong>Reflector</strong> (5-minute candles) for collateral pricing, and <strong>RedStone</strong> for some assets like RWAs. For rates they derive <strong>APR oracles</strong> by applying exponentially weighted moving average smoothing — because lending-market rates only update on trades, so without smoothing the rate can sit unchanged for long stretches.</li>
+<li class=""><strong>vIMM</strong> (virtual IMM) — an AMM-style engine, close to Uniswap v3 with liquidity ticks, but instead of trading token-vs-token it trades a <strong>fixed rate against a variable rate</strong> tied to an underlying (e.g. a Blend rate). Pools issue <strong>fixed tokens</strong> (representing a fixed ~1% APR factor) and <strong>variable tokens</strong> (whose growth tracks the underlying). It's a zero-sum game — the sum of LP and taker tokens is always zero, so when one side loses on a rate change, the counterparty earns it.</li>
+<li class=""><strong>Collateral Engine</strong> — handles LTVs, liquidation bands, and stages. Stable-vs-stable isolated pools can run very high LTV (~99%); portfolio exposure with volatile collateral needs more buffer. Crucially, because an interest rate swap's P&amp;L is driven by <em>accrued</em> value over time rather than instantaneous price spikes, the engine can support high leverage for shorter tenors using dynamic upper/lower "worst-case" bounds — more collateral for longer maturities, less for closer ones. Settlement happens automatically at maturity, much like options.</li>
+</ol>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="whats-next-for-xccy">What's Next for XCCY<a href="https://developers.stellar.org/meetings/2026/06/18#whats-next-for-xccy" class="hash-link" aria-label="Direct link to What's Next for XCCY" title="Direct link to What's Next for XCCY" translate="no">​</a></h3>
+<p>Mainnet is several months out, gated mostly on audits given the complexity, with the Stellar testnet and SDK landing in a few weeks. The API already exists and is being ported to Stellar this month — and they explicitly want to adapt it for <strong>AI agents</strong>, so a strategy can be wired up with "one prompt or one skill." Cross-chain arbitrage across their existing EVM pools is on the roadmap too. Reach them on the Stellar Discord, Telegram, or X.</p>
+<p>It's a fitting guest for where Stellar is: nearly <strong>$3 billion in RWAs</strong> on the network today, and teams like XCCY are coming precisely because of the institutional and real-world-asset depth.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="stellar-build-your-whole-dev-journey-in-one-command">stellar-build: Your Whole Dev Journey in One Command<a href="https://developers.stellar.org/meetings/2026/06/18#stellar-build-your-whole-dev-journey-in-one-command" class="hash-link" aria-label="Direct link to stellar-build: Your Whole Dev Journey in One Command" title="Direct link to stellar-build: Your Whole Dev Journey in One Command" translate="no">​</a></h2>
+<p>The AI half of the meeting was a walkthrough of <strong>stellar-build</strong> (stellar.new) — the tool the DevRel team shipped last Friday and used at the Istanbul hackathon. It's a one-command installer that drops <strong>42 skills</strong> plus curated data on <strong>700+ projects built on Stellar</strong> and <strong>9,000 projects</strong> from Electric Capital's developer reports into your setup. Since Friday it's been installed about <strong>101 times</strong>.</p>
+<p>The idea: answer almost every question a builder would otherwise ask a mentor during a hackathon — <em>is this a good idea, has it been done on Stellar, can it be done on Stellar, who are my competitors</em> — not just "how do I implement X." It's built on the <strong>BMAD method</strong>, so it's a hands-on, orchestrated journey rather than a one-shot app generator. You're the orchestrator; the AI personas and their data do the legwork while you say yes, no, or maybe.</p>
+<p>Those personas are the DevRel team rendered as agents: <strong>Justin</strong> (analyst), <strong>Bri</strong> (tech writer), <strong>Nicole</strong> (PM), <strong>Kaan</strong> (UX), <strong>Tyler</strong> (architect), and <strong>Elliot</strong> (senior dev) — spanning the idea, planning, solutioning, implementation, and launch phases. There's a <strong>party mode</strong> that brings everyone into the room at once, and a <strong>stellar-help</strong> router that re-orients you whenever you forget where you are.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="live-demo">Live Demo<a href="https://developers.stellar.org/meetings/2026/06/18#live-demo" class="hash-link" aria-label="Direct link to Live Demo" title="Direct link to Live Demo" translate="no">​</a></h3>
+<p>I drove it live for the ZK hackathon. Asked <strong>Justin</strong> what to build; he pulled my prior context (via the <strong>mnemon</strong> memory plugin), then loaded the <strong>competitive-landscape</strong> skill and went treasure hunting through both the curated catalog and the Electric Capital dump. He surfaced real neighbors — <strong>Zarf Protocol</strong> (an SCF 42 privacy-preserving token distribution with ZK private claims), <strong>Sora Drop</strong> (an open-source but non-private airdrop tool, ~$48k from SCF 28), and a stealth team porting the same primitive — making the point that the Merkle-claim mechanic is already being commoditized, so the opening is a sharp, specific application rather than yet another ZK toolkit.</p>
+<p>From there we routed into a <strong>PR FAQ</strong> validation (working-backwards stress test) with Justin, then pulled in <strong>Tyler</strong> to sketch the architecture with full context handed off cleanly — issuer contract, circuit spec, storage layout, interface signatures. Every persona ends its turn with concrete next steps, which matters: even the human versions of these people aren't always in the room.</p>
+<p>That's stellar-build — the entire DevRel team as agents on your screen. Grab it for this week's Real World ZK hackathon on DoraHacks, and I'll see you next week.</p>]]></content>
+        <author>
+            <name>Kaan Kacar</name>
+            <uri>https://github.com/kaankacar</uri>
+        </author>
+        <category label="developer" term="developer"/>
+    </entry>
+    <entry>
+        <title type="html"><![CDATA[2026-06-11]]></title>
+        <id>https://developers.stellar.org/meetings/2026/06/11</id>
+        <link href="https://developers.stellar.org/meetings/2026/06/11"/>
+        <updated>2026-06-11T00:00:00.000Z</updated>
+        <summary type="html"><![CDATA[Back After a Week]]></summary>
+        <content type="html"><![CDATA[<div class="youtubeEmbed" style="position:relative;width:100%;padding-bottom:56.25%;height:0;margin-bottom:23px"><iframe src="https://www.youtube-nocookie.com/embed/AdhPqUbZXvA?rel=0&amp;modestbranding=1" title="Informational explainer" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" style="position:absolute;top:0;left:0;width:100%;height:100%;border:0px;border-radius:25pt"></iframe></div>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="back-after-a-week">Back After a Week<a href="https://developers.stellar.org/meetings/2026/06/11#back-after-a-week" class="hash-link" aria-label="Direct link to Back After a Week" title="Direct link to Back After a Week" translate="no">​</a></h2>
+<p>We skipped a week — the DevRel team was in Istanbul for the hackathon we threw during Istanbul Blockchain Week, and the side event at the end gathered more than 400 people. This week we're back, and the guests are Paul and David from Sodax. You may know them from Balanced or Hana Wallet; they're some of the OGs, and they walked us through what Sodax is and why a Stellar builder should care. The plan was to close with a new AI package from our side, but the Sodax half earned its time, so that one slid to next week.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="sodax-cross-network-liquidity-as-developer-tooling">Sodax: Cross-Network Liquidity as Developer Tooling<a href="https://developers.stellar.org/meetings/2026/06/11#sodax-cross-network-liquidity-as-developer-tooling" class="hash-link" aria-label="Direct link to Sodax: Cross-Network Liquidity as Developer Tooling" title="Direct link to Sodax: Cross-Network Liquidity as Developer Tooling" translate="no">​</a></h2>
+<p>Sodax is a cross-network execution and liquidity system — an intent-based one — and the framing David led with is that it's essential <em>developer tooling</em>, not a destination app. If you're building on Stellar and you want to open your front door to users who hold assets on other networks, you normally have to build bridges, source liquidity, and maintain infrastructure. Sodax does that part so you don't: you stay on Stellar, build the way you want, and reach users elsewhere through a single developer SDK.</p>
+<p>The liquidity piece is the part that's easy to underrate. It isn't only cross-network <em>connectivity</em> — Sodax has already sourced the liquidity, so the cross-network swaps and DeFi actions actually settle. As a developer you stop worrying about where the depth comes from.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="from-icon-to-sodax">From ICON to Sodax<a href="https://developers.stellar.org/meetings/2026/06/11#from-icon-to-sodax" class="hash-link" aria-label="Direct link to From ICON to Sodax" title="Direct link to From ICON to Sodax" translate="no">​</a></h2>
+<p>Paul gave the origin story, and it's a good one. The Sodax brand is new — early 2025 — but the team isn't. Before Sodax they were ICON (the ICX token), a layer-1 from the ICO era with an interoperability vision that was years ahead of its time. Over time the lesson landed: to do intent-based, liquidity-powered interoperability you don't actually need to run your own blockchain. So they spun the L1 down, put their logic hub on Sonic (a fast, sub-second-finality EVM chain), and built the smart contracts out across Stellar, Solana, Sui, and more — deliberately spanning EVM and non-EVM networks to open routes other systems treat as impossible.</p>
+<p>Balanced (once the number-one DEX on ICON) and Hana Wallet (formerly the ICON wallet, now a self-custodial multi-network wallet on mobile and desktop) both come from those same ICON roots and are now powered by Sodax under the hood. Both went through Stellar's SCF program — they pitched at Meridian in London two years ago and Hana again at Meridian Brazil last year.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="the-spoke-chain-model">The Spoke-Chain Model<a href="https://developers.stellar.org/meetings/2026/06/11#the-spoke-chain-model" class="hash-link" aria-label="Direct link to The Spoke-Chain Model" title="Direct link to The Spoke-Chain Model" translate="no">​</a></h2>
+<p>In the Sodax model, Stellar is a <strong>spoke chain</strong> — which means everything in the Sodax docs applies to and for Stellar builders. The count keeps climbing, but they're on roughly 20 networks now, and they recently plugged in native Bitcoin, which they're rightly proud of. Some of the more exotic spokes are Near, Stacks (a Bitcoin L2), and Injective (Cosmos).</p>
+<p>The asset model is worth understanding. When you swap into "BTC" on Stellar through Sodax, you get a <strong>soda variant</strong> — a trading- and liquidity-backed Sodax representation of Bitcoin that lives on Stellar but is plugged into real Bitcoin liquidity on the Bitcoin network. The solver sees native-asset liquidity across all 20 networks at once and reasons across all of it when a trade fires, so there's depth without anyone provisioning pools — and you can withdraw straight back out to a native Bitcoin wallet. If you've used something like Near Intents, the UX will feel familiar.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="three-lines-to-a-cross-network-swap">Three Lines to a Cross-Network Swap<a href="https://developers.stellar.org/meetings/2026/06/11#three-lines-to-a-cross-network-swap" class="hash-link" aria-label="Direct link to Three Lines to a Cross-Network Swap" title="Direct link to Three Lines to a Cross-Network Swap" translate="no">​</a></h2>
+<p>Paul's honest line was that the demo is hard to make sound impressive because the SDK abstracts so much away. Integration is three steps:</p>
+<ol>
+<li class=""><strong>Quote</strong> — ask for the price of the swap you want.</li>
+<li class=""><strong>Swap</strong> — do it. One line.</li>
+<li class=""><strong>Status</strong> — poll for <code>not started</code>, <code>solved</code>, or <code>failed</code>.</li>
+</ol>
+<p>If a swap fails, the recovery system automatically returns funds — even if they'd already left the wallet. There's also a built-in wallet-connection component (wrap it around your frontend, stack the providers, done), which matters when you're juggling 20 networks, and Stellar trustlines are handled inside the SDK. <code>npm install</code> the SDK (or <code>pnpm add</code> it) and that's most of what you need to ship a real cross-network app.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="earn-and-a-bit-of-alpha">Earn, and a Bit of Alpha<a href="https://developers.stellar.org/meetings/2026/06/11#earn-and-a-bit-of-alpha" class="hash-link" aria-label="Direct link to Earn, and a Bit of Alpha" title="Direct link to Earn, and a Bit of Alpha" translate="no">​</a></h2>
+<p>Beyond swaps, the SDK exposes a cross-network money market — your end users can deposit, borrow, and earn supply interest. David dropped a bit of alpha too: leveraged staking yield is coming, so things like native ETH or native Solana staking would become accessible to your users even if your app lives entirely on Stellar or some other unrelated network.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="built-for-agents">Built for Agents<a href="https://developers.stellar.org/meetings/2026/06/11#built-for-agents" class="hash-link" aria-label="Direct link to Built for Agents" title="Direct link to Built for Agents" translate="no">​</a></h2>
+<p>This is the part that fit the room. Sodax shipped a best-in-class <strong>builder MCP server</strong> (<a href="https://builders.sodax.com/" target="_blank" rel="noopener noreferrer" class="">builders.sodax.com</a>) — plug it into Claude or your cursor agent and it levels your agent up into a "prime Sodax developer." You don't need a docs-indexer like Context7; the MCP <em>is</em> the docs. Even before you commit to building with Sodax, you can point the builder MCP at your existing Stellar repo and have it assess, in about ten minutes, where Sodax could open up cross-network opportunity for you. On top of that, they've embedded agent skills directly inside the SDK, so even if you never wire up the MCP, an agent crawling the package runs into the skills and uses the swap/lend/borrow modules correctly — in their words, "so that even Sonnet 4.6 doesn't make mistakes."</p>
+<p>I can vouch for that last claim. The morning of the meeting I didn't even use the MCP — I pointed Sonnet 4.6 (not the strongest model) at <code>docs.sodax.com</code> with roughly "surprise me," and about thirty minutes and 20% of a Pro plan later I had a one-shot mainnet demo: assets, addresses, cross-chain swaps, bridge limits, every supported chain. The question stopped being <em>can</em> you vibe-code something on Sodax and became <em>why not</em>.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="the-fee-model">The Fee Model<a href="https://developers.stellar.org/meetings/2026/06/11#the-fee-model" class="hash-link" aria-label="Direct link to The Fee Model" title="Direct link to The Fee Model" translate="no">​</a></h2>
+<p>Sodax takes a flat <strong>0.1%</strong> on swaps — the same shape as a Uniswap-style backend fee. The interesting part for builders: any partner integrating the SDK can set their <em>own</em> partner fee on top. A wallet like Hana, or your own app, can add (say) 0.5% and keep it. You have full control over what you charge your users, which means an integrator can end up earning more per swap than Sodax itself.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="why-mainnet-only">Why Mainnet Only<a href="https://developers.stellar.org/meetings/2026/06/11#why-mainnet-only" class="hash-link" aria-label="Direct link to Why Mainnet Only" title="Direct link to Why Mainnet Only" translate="no">​</a></h2>
+<p>A recurring audience question: does it support testnet? Short answer, no — and the reason is structural. The solver sources real liquidity from real markets, and there's no monetary value backing assets on testnet, so the solver simply has nothing to solve. Replicating it would mean standing up and maintaining dozens of testnet liquidity pools, bridges, and staking platforms in parallel. They're open to bringing <em>parts</em> of the stack to testnet and want to hear from developers about which parts would actually help — but for now Sodax is a mainnet product, which is also fine, because you're not deploying your own contracts. It's a plug you put into your app and it works.</p>
+<p>Where to go next: <a href="https://docs.sodax.com/" target="_blank" rel="noopener noreferrer" class="">docs.sodax.com</a> for the SDK, <a href="https://builders.sodax.com/" target="_blank" rel="noopener noreferrer" class="">builders.sodax.com</a> for the MCP, and <a href="https://www.sodax.com/partners" target="_blank" rel="noopener noreferrer" class="">sodax.com/partners</a> to see how the integration and fee split work. Their whole team hangs out in Discord and answers builder questions directly.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="next-week">Next Week<a href="https://developers.stellar.org/meetings/2026/06/11#next-week" class="hash-link" aria-label="Direct link to Next Week" title="Direct link to Next Week" translate="no">​</a></h2>
+<p>I ran out of time to show the AI package we built, so set a reminder. Next week's is the one I've been most excited about: the tool the SDF DevRel team shipped that drops 42 skills and hooks into your setup, packs in information about every project ever built on Stellar for market research, and wraps the whole thing in an Agile workflow. It needs a full half-hour to do it justice. See you then.</p>]]></content>
+        <author>
+            <name>Kaan Kacar</name>
+            <uri>https://github.com/kaankacar</uri>
+        </author>
+        <category label="developer" term="developer"/>
+    </entry>
+    <entry>
+        <title type="html"><![CDATA[2026-05-21]]></title>
+        <id>https://developers.stellar.org/meetings/2026/05/21</id>
+        <link href="https://developers.stellar.org/meetings/2026/05/21"/>
+        <updated>2026-05-21T00:00:00.000Z</updated>
+        <summary type="html"><![CDATA[Another Two-Part Meeting]]></summary>
+        <content type="html"><![CDATA[<div class="youtubeEmbed" style="position:relative;width:100%;padding-bottom:56.25%;height:0;margin-bottom:23px"><iframe src="https://www.youtube-nocookie.com/embed/isaeBeur6ro?rel=0&amp;modestbranding=1" title="Informational explainer" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" style="position:absolute;top:0;left:0;width:100%;height:100%;border:0px;border-radius:25pt"></iframe></div>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="another-two-part-meeting">Another Two-Part Meeting<a href="https://developers.stellar.org/meetings/2026/05/21#another-two-part-meeting" class="hash-link" aria-label="Direct link to Another Two-Part Meeting" title="Direct link to Another Two-Part Meeting" translate="no">​</a></h2>
+<p>This week splits in half again. The first half belongs to our guest — a builder out of Kolkata who joined the community last October and started shipping ZK tooling almost immediately. He's here to present Root14 — a privacy <em>toolkit</em> for Stellar built on the zero-knowledge primitives that landed in recent protocol upgrades. The second half is mine: a fast tour through roughly ten open-source, mostly-free AI tools, continuing the orchestrator theme from last week. If cryptography isn't your thing, skip to the tools. If you've had enough of me talking about agents, the first half is the one for you.</p>
+<p>A quick reframing before he starts, because it's load-bearing for everything he says: Root14 is <strong>not</strong> a private payments app. It's not a mixer and it's not a shielded pool. It's the cryptographic infrastructure that sits <em>underneath</em> all of those things. The analogy he uses is OpenSSL versus a single HTTPS website — Root14 isn't the website, it's the part every website ends up importing.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="the-substrate-why-the-economics-only-work-on-stellar">The Substrate: Why the Economics Only Work on Stellar<a href="https://developers.stellar.org/meetings/2026/05/21#the-substrate-why-the-economics-only-work-on-stellar" class="hash-link" aria-label="Direct link to The Substrate: Why the Economics Only Work on Stellar" title="Direct link to The Substrate: Why the Economics Only Work on Stellar" translate="no">​</a></h2>
+<p>He grounds the whole talk in CAP-59, which shipped the native BLS12-381 host functions to Soroban: G1/G2 addition, scalar multiplication, multi-scalar multiplication, pairing checks, and full scalar-field arithmetic. That's the complete substrate you need to do production-grade Groth16 verification natively, available to any contract.</p>
+<p>His pitch for <em>why Stellar</em> comes down to cost. A pairing check that would take tens of millions of Wasm instructions on another chain runs as a single host call here. No other smart-contract chain has this combination at this cost point today — which is exactly what pulled him to the network and got him researching ZK on it in the first place.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="whats-in-the-toolkit">What's in the Toolkit<a href="https://developers.stellar.org/meetings/2026/05/21#whats-in-the-toolkit" class="hash-link" aria-label="Direct link to What's in the Toolkit" title="Direct link to What's in the Toolkit" translate="no">​</a></h2>
+<p>Root14 is a layered toolkit, and he walked through it piece by piece:</p>
+<ul>
+<li class=""><strong>Root14 Core</strong> — a single contract that does two things. You call <code>register</code> and get back a content-addressed circuit identifier (the SHA-256 of the verification key, so the binding is unforgeable). After that, any contract on the network calls <code>verify</code> with a circuit ID, a proof, and the public inputs, and gets back a boolean. That's the entire interface. The contract holds no business logic, no value, no decisions — just registered verification keys and pairing checks. It's live on testnet today. The load-bearing insight: every existing privacy project on Stellar embeds its own verifier inside its own contract and pays for its own audit on essentially the same pairing code. A shared registry makes that duplication disappear.</li>
+<li class=""><strong>Circuit Library</strong> — a set of vetted primitive circuits with published constraint counts and content-addressed identifiers: range proofs (credit thresholds, age bounds), set membership (KYC allow-lists), set non-membership (sanctions screening), and knowledge-of-preimage (ownership groups). Register a primitive once and every dapp on the network can use it.</li>
+<li class=""><strong>SDK and CLI</strong> — a single <code>cargo add</code> gets you proof generation and serialization in Rust; the CLI is a human-friendly shell over the same SDK, with templates for generating contracts.</li>
+<li class=""><strong>MCP server</strong> — the part he's most excited about. It lets Claude or any MCP-compatible model register a circuit, generate a proof, and trigger a verify call through natural language. As far as he can tell, it's the first ZK-on-Stellar MCP integration anywhere. A registry indexer streams on-chain events so developers can discover which circuits exist and how to compose them.</li>
+</ul>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="the-zktls-bridge">The zkTLS Bridge<a href="https://developers.stellar.org/meetings/2026/05/21#the-zktls-bridge" class="hash-link" aria-label="Direct link to The zkTLS Bridge" title="Direct link to The zkTLS Bridge" translate="no">​</a></h2>
+<p>The piece closest to his heart is Root14's zkTLS. It bridges web2 and web3 trust: a user generates a zero-knowledge proof that they received a <em>specific response</em> from a <em>specific web2 server</em> without revealing the rest of the session. Prove you have over $1,000 in a bank account without showing the statement. Prove a KYC status with a particular issuer without exposing the underlying credential. Prove a tweet exists at a URL without leaking the OAuth token. There's a prototype today and production integration is on the roadmap; combined with the verifier registry, it's a clean way to pull real-world data into Soroban contracts without trusting a centralized oracle.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="private-payments-honestly">Private Payments, Honestly<a href="https://developers.stellar.org/meetings/2026/05/21#private-payments-honestly" class="hash-link" aria-label="Direct link to Private Payments, Honestly" title="Direct link to Private Payments, Honestly" translate="no">​</a></h2>
+<p>He was candid about the one piece that isn't usable right now. His original SCF submission leaned on private payments, and the mainnet privacy-pool deployments lagged on the AML/KYT-sensitive side — building privacy-preserving payments without thinking hard about compliance is how you get into legal trouble. So that part is currently down while he reworks it to be KYC/AML-aware. The developer-facing shape is still the goal, though: you don't write pairing code, you don't run a trusted-setup ceremony, you don't touch arkworks — you write your application contract, bind it to the relevant circuit identifiers in the registry, and call <code>verify</code> when you need a proof checked.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="production-readiness">Production Readiness<a href="https://developers.stellar.org/meetings/2026/05/21#production-readiness" class="hash-link" aria-label="Direct link to Production Readiness" title="Direct link to Production Readiness" translate="no">​</a></h2>
+<p>This isn't framed as a research prototype. Verification keys registered on mainnet will be immutable and content-addressed — no upgrade method, no admin power to silently re-point an identifier. Canonical registration transactions go through an SDF-approved multisig. The phase-2 trusted-setup ceremony will be multi-party with public transcripts and end-to-end-verified attestations from every contributor, and everything is open source under the Root14 name.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="the-qa-ai-groth16-vs-plonk-and-the-business-question">The Q&amp;A: AI, Groth16 vs. PLONK, and the Business Question<a href="https://developers.stellar.org/meetings/2026/05/21#the-qa-ai-groth16-vs-plonk-and-the-business-question" class="hash-link" aria-label="Direct link to The Q&amp;A: AI, Groth16 vs. PLONK, and the Business Question" title="Direct link to The Q&amp;A: AI, Groth16 vs. PLONK, and the Business Question" translate="no">​</a></h2>
+<p>We tend to roast our guests with hard questions so they've already sweated out the answers before they reach an SCF panel, and the audience delivered:</p>
+<ul>
+<li class=""><strong>How much AI, and what's the setup?</strong> He works ZK problems out with pen and paper first, then drives Claude Code layer by layer — architecture, then circuits, then verifier — prototyping, testing, and bouncing the output off other agents before moving on. He also leaned on the <code>llms.txt</code> file from the docs to make the model Stellar-aware out of the gate. His honest caveat matches mine: AI tends to cut corners on ZK, so it's an accelerant, not an autopilot.</li>
+<li class=""><strong>Long-term sustainability?</strong> A shared verifier registry doesn't make much money on its own — maybe a small fee on registrations or calls. The real business is zkTLS as a B2B product: managing ZK infrastructure for Stellar-native teams and selling into developer/user onboarding flows.</li>
+<li class=""><strong>Why Groth16 over PLONK, and who runs the ceremony?</strong> Groth16 won on cost and proof size for a hackathon timeline; PLONK needs more pairings and polynomial-commitment work, roughly double the budget for the same proof. He reuses an existing phase-1 powers-of-tau output (the Ethereum or Aztec ignition ceremonies, both public and audited with 100+ contributors) and only runs phase 2 per-circuit. Nothing about Root14 is religiously locked to Groth16.</li>
+</ul>
+<p>Root14 is in SCF #43 — the docs site is mid-rebuild, so keep an eye out and vote it up when public voting opens.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="the-orchestrator-theme-continued">The Orchestrator Theme, Continued<a href="https://developers.stellar.org/meetings/2026/05/21#the-orchestrator-theme-continued" class="hash-link" aria-label="Direct link to The Orchestrator Theme, Continued" title="Direct link to The Orchestrator Theme, Continued" translate="no">​</a></h2>
+<p>The pivot to the second half: last week I made the case that the job is shifting from <em>facilitator</em> (you write the code, you stay close to the work) to <em>orchestrator</em> (you manage a fleet of agents). This week's theme is narrower and a little more pointed. Stop writing "make no mistakes" to your model. If you can't steer the build, it's usually because you don't understand what's being built — and if you <em>wouldn't</em> be able to build it without AI, that's the most dangerous place to be. The tools below are all attempts to keep you hands-on enough to understand the thing you're shipping.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="hands-on-frameworks-bmad-and-superpowers">Hands-On Frameworks: BMAD and Superpowers<a href="https://developers.stellar.org/meetings/2026/05/21#hands-on-frameworks-bmad-and-superpowers" class="hash-link" aria-label="Direct link to Hands-On Frameworks: BMAD and Superpowers" title="Direct link to Hands-On Frameworks: BMAD and Superpowers" translate="no">​</a></h2>
+<p><a href="https://github.com/bmad-code-org/BMAD-METHOD" target="_blank" rel="noopener noreferrer" class="">The BMAD Method</a> is the one I most wanted to show. It installs locally and free with <code>npx bmad-method install</code> — it's just a set of skills, hooks, and workflows, scoped to your project rather than installed globally. The point is spec-driven development with an Agile shape: it slows you down on purpose and walks you through brainstorming, market and domain research, technical research, and then planning out a PRD and stories. Each phase has a named agent — Mary is the business analyst you brainstorm with — and <code>/bmad-help</code> is your "what do I do next" button at any point. I kicked off a "Hey Mary, I want to build something with agentic payments on Stellar but I don't know what" session live to show the brainstorming loop.</p>
+<p><a href="https://github.com/obra/superpowers" target="_blank" rel="noopener noreferrer" class="">Superpowers</a> is an alternative skills framework that does more or less the same job minus the explicit Agile emphasis. Try both and keep whichever fits how you think. The shared point of both: a more hands-on approach so you actually understand what's being built.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="letting-agents-use-a-browser-kernelsh-and-browser-use">Letting Agents Use a Browser: kernel.sh and browser-use<a href="https://developers.stellar.org/meetings/2026/05/21#letting-agents-use-a-browser-kernelsh-and-browser-use" class="hash-link" aria-label="Direct link to Letting Agents Use a Browser: kernel.sh and browser-use" title="Direct link to Letting Agents Use a Browser: kernel.sh and browser-use" translate="no">​</a></h2>
+<p>Claude Code and Codex can fetch a page's data but can't really <em>drive</em> a browser — and they can't touch Chrome extensions, which is painful if you're testing a Stellar wallet extension. <a href="https://www.kernel.sh/" target="_blank" rel="noopener noreferrer" class="">kernel.sh</a> fixes that: it spins up cloud browsers and lets your agent build automated workflows (it calls them "apps") through a free MCP server. My demo had Claude Code's kernel MCP walk stellar.expert for mainnet stats, click into the Soroban tab, hop to CoinGecko for the XLM/USD price, and capture it all to JSON. It's open-source infra with a free tier; the paid plan exists, but the free MCP is enough to expand your sense of what's possible.</p>
+<p><a href="https://github.com/browser-use/browser-use" target="_blank" rel="noopener noreferrer" class="">browser-use</a> is the tool your model reaches for <em>first</em> when you ask for browser automation — which is exactly why I show it. First-recommended isn't the same as best. It wants its own API keys (Google's and Anthropic's), and I'd rather point an agent at tools that ride the CLI I'm already paying for. Useful to know it exists, but kernel was the smoother experience for me.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="free-compute-freebuff">Free Compute: freebuff<a href="https://developers.stellar.org/meetings/2026/05/21#free-compute-freebuff" class="hash-link" aria-label="Direct link to Free Compute: freebuff" title="Direct link to Free Compute: freebuff" translate="no">​</a></h2>
+<p><a href="https://freebuff.com/" target="_blank" rel="noopener noreferrer" class="">freebuff</a> is the free tier of CodeBuff — it gives you a few hours a day of DeepSeek V4 Flash for free, with ads. The agent ("Buffy") does the usual implementation, codebase navigation, testing, and multi-agent orchestration (it'll spawn a stack of sub-agents), and it drives a browser using browser-use under the hood, so you get the browser-automation demo and the free-compute demo in one. DeepSeek V4 Flash is light but genuinely good for exploratory work when you don't want to burn frontier-model budget. CodeBuff's paid tier is around $100/month; if you're going to consider that, spend your free hours first.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="memory-claude-mem-mnemon-and-raindrop-workshop">Memory: claude-mem, mnemon, and Raindrop Workshop<a href="https://developers.stellar.org/meetings/2026/05/21#memory-claude-mem-mnemon-and-raindrop-workshop" class="hash-link" aria-label="Direct link to Memory: claude-mem, mnemon, and Raindrop Workshop" title="Direct link to Memory: claude-mem, mnemon, and Raindrop Workshop" translate="no">​</a></h2>
+<p>The unsolved problem under all of this is memory — how does the agent remember where it left off? Three takes:</p>
+<ul>
+<li class=""><strong><a href="https://github.com/thedotmack/claude-mem" target="_blank" rel="noopener noreferrer" class="">claude-mem</a></strong> is the most widely used, and it's my favorite plug-in for this. It runs locally, works with Claude Code and Codex, and at the end of each session it scans the whole thing — what you discussed, what the agent did, where it went wrong, how it reached its conclusions — and writes session summaries plus, my favorite part, <em>discoveries</em>. Open the folder again and the agent already knows where it left off. No more hand-written handoff markdown. The trade-off is that it stores a lot, including things you didn't need.</li>
+<li class=""><strong><a href="https://github.com/mnemon-dev/mnemon" target="_blank" rel="noopener noreferrer" class="">mnemon</a></strong> is the same idea but LLM-supervised: it lets your model decide <em>what</em> to remember and <em>when</em> to recall it, which keeps the store much tighter. It's newer and smaller than claude-mem, has an MCP server, and persists across sessions. Import claude-mem's history into mnemon's graph and you can see what the former would look like with structure; run mnemon on its own and you get a clean "mind palace."</li>
+<li class=""><strong><a href="https://github.com/raindrop-ai/workshop" target="_blank" rel="noopener noreferrer" class="">Raindrop Workshop</a></strong> is the outsider. It's a local debugger that doesn't store everything and isn't LLM-supervised — it stores <em>workflows</em>, the step-by-step way to do a recurring thing. Ask the agent to do that thing again and it fetches the tree and follows it. It's cost-efficient precisely because it only remembers <em>how</em>, not <em>what</em>.</li>
+</ul>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="where-this-is-going">Where This Is Going<a href="https://developers.stellar.org/meetings/2026/05/21#where-this-is-going" class="hash-link" aria-label="Direct link to Where This Is Going" title="Direct link to Where This Is Going" translate="no">​</a></h2>
+<p>We covered a lot at a shallow depth on purpose. I want your help picking which of these deserves a full, hour-long deep dive in an upcoming session — tell me on Discord. The throughline of the whole second half: software is getting fast and cheap, and cheap software is also dangerous software. A more hands-on approach is the cheapest insurance you can buy. Stop writing "make no mistakes," start writing <code>/bmad-help</code>, and understand the thing you're building.</p>
+<p>One housekeeping note worth repeating: CCTP is live on Stellar now, so cross-chain interop apps are something you can start building today.</p>]]></content>
+        <author>
+            <name>Kaan Kacar</name>
+            <uri>https://github.com/kaankacar</uri>
+        </author>
+        <category label="developer" term="developer"/>
+    </entry>
+    <entry>
+        <title type="html"><![CDATA[2026-05-14]]></title>
+        <id>https://developers.stellar.org/meetings/2026/05/14</id>
+        <link href="https://developers.stellar.org/meetings/2026/05/14"/>
+        <updated>2026-05-14T00:00:00.000Z</updated>
+        <summary type="html"><![CDATA[A Packed Two-Part Meeting]]></summary>
+        <content type="html"><![CDATA[<div class="youtubeEmbed" style="position:relative;width:100%;padding-bottom:56.25%;height:0;margin-bottom:23px"><iframe src="https://www.youtube-nocookie.com/embed/pZMpqTGGA_Y?rel=0&amp;modestbranding=1" title="Informational explainer" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" style="position:absolute;top:0;left:0;width:100%;height:100%;border:0px;border-radius:25pt"></iframe></div>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="a-packed-two-part-meeting">A Packed Two-Part Meeting<a href="https://developers.stellar.org/meetings/2026/05/14#a-packed-two-part-meeting" class="hash-link" aria-label="Direct link to A Packed Two-Part Meeting" title="Direct link to A Packed Two-Part Meeting" translate="no">​</a></h2>
+<p>This week's meeting splits cleanly in half. The first half belongs to Renat — a builder in our community working out of Estonia — presenting a draft SEP for zero-knowledge group membership state on Soroban. The second half is mine: an introduction to open-source, free, locally-runnable orchestration layers for AI-assisted development. If ZK isn't your thing, stick around for the second half. If running fleets of agents isn't your thing, the first half is the better one for you.</p>
+<p>Renat is upfront about the framing: he's a builder, not a mathematician. The work he's presenting isn't a new cryptographic result — it's the integration story of getting Stellar's ZK primitives (shipped in Protocol 22 and Protocol 25) to compose into something useful, and then sharing what works, what doesn't, and what's still unsolved.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="the-problem-group-state-without-metadata">The Problem: Group State Without Metadata<a href="https://developers.stellar.org/meetings/2026/05/14#the-problem-group-state-without-metadata" class="hash-link" aria-label="Direct link to The Problem: Group State Without Metadata" title="Direct link to The Problem: Group State Without Metadata" translate="no">​</a></h2>
+<p>The naive way to put a group on-chain is to store a list of addresses. That works, and it's terrible for privacy — anyone who reads the contract storage knows who is in the group, who is an admin, and what the governance rules are.</p>
+<p>The use cases Renat is targeting all want the opposite shape: a messenger that hides which group a user belongs to, DAO credentials that prove "I'm a member" without revealing <em>who</em> I am, governance contracts that enforce rules without leaking the rule structure (is this a democracy, a tyranny, a one-on-one?). The problem is "prove membership and authority without revealing identity," which is the classic zero-knowledge setting.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="three-iterations-groth16--plonk--post-quantum">Three Iterations: Groth16 → PLONK → Post-Quantum<a href="https://developers.stellar.org/meetings/2026/05/14#three-iterations-groth16--plonk--post-quantum" class="hash-link" aria-label="Direct link to Three Iterations: Groth16 → PLONK → Post-Quantum" title="Direct link to Three Iterations: Groth16 → PLONK → Post-Quantum" translate="no">​</a></h2>
+<p>Renat walked through the iteration history:</p>
+<p><strong>Groth16</strong> was the starting point. It worked, but supporting governance rules over a hidden group required contributing randomness via a trusted-setup ceremony. The standard reassurance — "you only need one honest contributor out of fifty" — is mathematically fine, and the Ethereum KZG ceremony had ~141,000 contributors as proof-by-example, but the operational burden of running a credible ceremony at a small-project scale didn't fit.</p>
+<p><strong>PLONK</strong> was the second iteration, chosen explicitly to dodge the trusted-setup ceremony. This is what's currently live on testnet, and it owes its existence to the Soroban primitives shipped in Protocols 22 and 25. The contract interface is small: update the Merkle tree, verify membership, create group — with the proof transported separately from identity. A postmortem about getting the proof from client to contract is part of the package; that turned out to be the part of the work that bit the hardest.</p>
+<p><strong>Post-Quantum (no ceremony at all)</strong> is the direction Renat wants to take this next. It's currently blocked on memory consumption inside the Soroban environment — not CPU, which was his initial guess, but memory. The Stellar developers helped him diagnose this. Cost is also a factor at the post-quantum end — somewhere north of 16 cents per update versus less than a cent for the PLONK path.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="cost-limits-and-the-open-payer-problem">Cost, Limits, and the Open Payer Problem<a href="https://developers.stellar.org/meetings/2026/05/14#cost-limits-and-the-open-payer-problem" class="hash-link" aria-label="Direct link to Cost, Limits, and the Open Payer Problem" title="Direct link to Cost, Limits, and the Open Payer Problem" translate="no">​</a></h2>
+<p>The PLONK version is cheap. State updates cost less than a cent, and the actual messages in the messenger reference implementation are free. That's a usable cost envelope for a real product.</p>
+<p>The limits worth knowing:</p>
+<ul>
+<li class=""><strong>PLONK is bounded by K max 2</strong> in the current configuration — meaning "democracy" in the governance taxonomy doesn't scale to large groups yet. Two voters max per vote at the current parameters.</li>
+<li class=""><strong>TTL and contract capacity</strong> need to be designed into any SEP draft. They don't disqualify the approach, but they aren't free parameters either.</li>
+<li class=""><strong>The payer/anonymous-user interface</strong> is the most interesting open problem: somewhere in the flow, gas needs to come from somewhere, and "the anonymous member pays" leaks information unless handled carefully. This is the surface point of contact between the fee-paying entity and the privacy-preserving member, and there's no good answer in the current draft.</li>
+</ul>
+<p>The code is MIT-licensed and reproducible — the runs are public, the reference messenger implementation is published, and Renat is explicit that what's shown is reference-quality, not production-ready.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="what-renat-is-looking-for">What Renat Is Looking For<a href="https://developers.stellar.org/meetings/2026/05/14#what-renat-is-looking-for" class="hash-link" aria-label="Direct link to What Renat Is Looking For" title="Direct link to What Renat Is Looking For" translate="no">​</a></h2>
+<p>This part is the actual call to action: Renat is looking for a SEP champion in the developer community. Someone who can read the draft, push it through the ecosystem-proposal process, and validate that the work is useful beyond his own messenger project.</p>
+<p>If that sounds like you, his Discord handle is pinned in the meeting comments, and his email and GitHub are reachable from the reference implementation's README. He's open to "this works" feedback, "this doesn't work" feedback, and — the most useful kind — "this works but here's the obstacle you missed." He's planning to attend <a href="https://meridian.stellar.org/" target="_blank" rel="noopener noreferrer" class="">Meridian 2026</a> in Lisbon this October, so the champion conversation can also happen in person.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="the-orchestrator-shift">The Orchestrator Shift<a href="https://developers.stellar.org/meetings/2026/05/14#the-orchestrator-shift" class="hash-link" aria-label="Direct link to The Orchestrator Shift" title="Direct link to The Orchestrator Shift" translate="no">​</a></h2>
+<p>The pivot of the second half: if you've been building on Stellar for any length of time, you're using AI. Pretending otherwise is silly. The interesting question is what <em>kind</em> of AI use you're doing.</p>
+<p>There are two roles to recognize. The earlier role — the <strong>facilitator</strong> — is what most of us got used to between November 2022 and roughly the end of 2024: you write what you think, you write what you want, you guide the model through the build, and you stay close to the work. Cursor Composer, Sonnet 4, GPT-o3 — all of these reward facilitation.</p>
+<p>The newer role — the <strong>orchestrator</strong> — is what Opus 4.7, Composer 2, the Claude Agents SDK, and the autonomous-agent stacks (Hermes, Open Claw, custom-built agents) are designed for. You're no longer the one writing prompts to a single model; you're managing a fleet, and your job is to keep that fleet aimed at a useful outcome. That's a different skill, and the tools for that role are still finding their shape.</p>
+<p>The three tools in the second half of this meeting are all attempts at giving the orchestrator a control plane.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="cline-kanban">Cline Kanban<a href="https://developers.stellar.org/meetings/2026/05/14#cline-kanban" class="hash-link" aria-label="Direct link to Cline Kanban" title="Direct link to Cline Kanban" translate="no">​</a></h2>
+<p>Cline Kanban — free, open-source, runs locally — is the lightest of the three. It's a Kanban board for agent work, built on top of Cline (the open-source coding agent that ships an SDK, a CLI, and a VS Code extension of its own). You drop into a project directory, run <code>kanban</code>, and a local web UI comes up. The board can attach to any of the major agents — Cline itself, Claude Code, Codex, Factory Droid, Kiro, Hermes — and you use it to define tasks, set dependencies between them, and drag work through To Do → In Progress → Review → Done.</p>
+<p>The demo: a fresh directory called <code>x402-contest-demo</code>, a one-line ask to "create an exploratory x402 demo on Stellar," and the Kanban agent decomposed it into five linked tasks. From that point on, the orchestrator's job is to review each completed task, decide whether to merge to main, and unblock the next one in the chain. The board offers auto-commit, open-PR, and "leave on branch" flows; while you're getting a feel for an agent's output quality, "ask for approval at each step" is the right default.</p>
+<p>The shape of this tool: best when the underlying work is <em>coding</em> and you want a lightweight layer on top of one or more agents to keep tasks orderly and dependencies explicit.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="paperclip-a-control-plane-for-ai-labor">Paperclip: A Control Plane for AI Labor<a href="https://developers.stellar.org/meetings/2026/05/14#paperclip-a-control-plane-for-ai-labor" class="hash-link" aria-label="Direct link to Paperclip: A Control Plane for AI Labor" title="Direct link to Paperclip: A Control Plane for AI Labor" translate="no">​</a></h2>
+<p><a href="https://paperclip.ing/" target="_blank" rel="noopener noreferrer" class="">Paperclip</a> takes the orchestrator framing one step further. Where Cline Kanban treats your project as a repo, Paperclip treats it as a <em>company</em>. You onboard with <code>npx paperclip-ai onboard --yes</code>, name the company, give it a mission, hire your first agent (the CEO by default), and from there you're the board.</p>
+<p>The demo company was "Paper Excel" — Dunder Mifflin in spirit — with the goal "to be the best paper company in the world with the best-looking UI." The CEO went to work hiring the first team: CTO, CMO, UX designer, research lead, intern. Each role has its own starter prompt, its own heartbeat interval, and its own assigned skill set. The dashboard tracks issues, an organizational chart, an inbox for the board (i.e., you) to receive agent emails, and routines for recurring work. The agent backends are pluggable: Claude Code, Codex, OpenRouter, Gemini CLI, Hermes Agent, Open Claw.</p>
+<p>Two practical notes:</p>
+<ul>
+<li class=""><strong>It is not a magic productivity multiplier.</strong> It's a coordination layer for running multiple agents — most of the agents in the demo were slacking on their first day, and roughly half the issues failed on first run with API errors. This is alpha-quality at the experience level, even where the underlying agent capabilities are strong.</li>
+<li class=""><strong>It will burn through tokens fast.</strong> Bring-your-own-API-key with per-agent spending caps is the right way to experiment. The demo ran on a Claude Code subscription and was probably $50–100 of usage in 30 minutes. For exploratory work, point it at a free model on OpenRouter — output quality is worse, but cost is bounded.</li>
+</ul>
+<p>The shape of this tool: best when the work is broader than coding — a research-and-marketing-and-content-and-product company-shaped problem — and you want to see what "running a small AI org" actually feels like before staffing one in real life.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="bmad-method-saved-for-next-week">BMAD Method (Saved for Next Week)<a href="https://developers.stellar.org/meetings/2026/05/14#bmad-method-saved-for-next-week" class="hash-link" aria-label="Direct link to BMAD Method (Saved for Next Week)" title="Direct link to BMAD Method (Saved for Next Week)" translate="no">​</a></h2>
+<p>The third tool is the BMAD method — this week's favorite, and the one I most wanted to demo. The meeting ran long (the first half earned its time), and BMAD is worth a real walkthrough rather than five rushed minutes. Tune in next week for that one.</p>
+<p>The one-sentence pitch: BMAD is for builders who want an Agile development flow with their agents, and for builders who want a thoughtful brainstorming partner that's read more about the problem space than they have. If either of those describes your current bottleneck, the deferred demo will be the one to catch.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="where-this-is-going">Where This Is Going<a href="https://developers.stellar.org/meetings/2026/05/14#where-this-is-going" class="hash-link" aria-label="Direct link to Where This Is Going" title="Direct link to Where This Is Going" translate="no">​</a></h2>
+<p>Two takeaways:</p>
+<p>The move from facilitator to orchestrator isn't a tooling upgrade — it's a skill change. The tools shown today are the early shape of what that change looks like: local-first, agent-agnostic, opinionated about how you compose work. They're not finished. They will get better.</p>
+<p>And: if you have time before next week, read Renat's draft and the reference implementation. A SEP that lets Soroban hold private group state cheaply is exactly the kind of primitive that quietly unlocks an entire category of applications later. The champion role is open.</p>]]></content>
+        <author>
+            <name>Kaan Kacar</name>
+            <uri>https://github.com/kaankacar</uri>
+        </author>
+        <category label="developer" term="developer"/>
+    </entry>
+    <entry>
+        <title type="html"><![CDATA[2026-05-07]]></title>
+        <id>https://developers.stellar.org/meetings/2026/05/07</id>
+        <link href="https://developers.stellar.org/meetings/2026/05/07"/>
+        <updated>2026-05-07T00:00:00.000Z</updated>
+        <summary type="html"><![CDATA[Machine Payments Protocol: A Deep Dive]]></summary>
+        <content type="html"><![CDATA[<div class="youtubeEmbed" style="position:relative;width:100%;padding-bottom:56.25%;height:0;margin-bottom:23px"><iframe src="https://www.youtube-nocookie.com/embed/WHYHzDF8KJ8?rel=0&amp;modestbranding=1" title="Informational explainer" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" style="position:absolute;top:0;left:0;width:100%;height:100%;border:0px;border-radius:25pt"></iframe></div>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="machine-payments-protocol-a-deep-dive">Machine Payments Protocol: A Deep Dive<a href="https://developers.stellar.org/meetings/2026/05/07#machine-payments-protocol-a-deep-dive" class="hash-link" aria-label="Direct link to Machine Payments Protocol: A Deep Dive" title="Direct link to Machine Payments Protocol: A Deep Dive" translate="no">​</a></h2>
+<p>This week's meeting is a hands-on walkthrough of the Machine Payments Protocol (MPP) on Stellar — what it is, when to reach for it, and the specific moment in your code where an operation becomes an MPP operation. The goal is to answer one question by the end: "So what? Why should I care about MPP?"</p>
+<p>MPP is the second of the two agentic-payment primitives covered in recent meetings. The first, x402, is the more familiar of the two — it's effectively a programmable paywall built on top of the long-standing HTTP <code>402 Payment Required</code> status. A human or an agent hits a route, gets a <code>402</code>, pays, and is allowed through. MPP is the less obvious sibling, and the value proposition only becomes clear once you understand its two modes.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="charge-mode-vs-channel-mode">Charge Mode vs. Channel Mode<a href="https://developers.stellar.org/meetings/2026/05/07#charge-mode-vs-channel-mode" class="hash-link" aria-label="Direct link to Charge Mode vs. Channel Mode" title="Direct link to Charge Mode vs. Channel Mode" translate="no">​</a></h2>
+<p>MPP has two payment modes, and the distinction is the entire point of the protocol.</p>
+<p><strong>Charge mode</strong> is pay-per-request. A route returns a payment challenge, the caller pays for that single request, and the receipt unlocks the response. If you've worked with x402, charge mode will feel almost identical — it is the right choice when requests are infrequent or the underlying data isn't changing rapidly. One call, one transaction, one receipt.</p>
+<p><strong>Channel mode</strong> is where MPP earns its keep. Imagine you're charging for access to a premium LLM that emits 50 tokens per second, and the underlying cost model is per-token rather than per-request. Pay-per-request breaks down immediately: you'd need the user to send a transaction every 1/50th of a second, which is impossible. Channel mode solves this by letting the user open a funded channel up front, spend against it at high frequency, and then settle in a single on-chain transaction when the channel closes. The channel can be closed manually (a button, an explicit "end session") or by a timeout — a timeout is usually the better default, because a user closing their laptop doesn't close the channel for them.</p>
+<p>The mental model: charge mode is a turnstile; channel mode is a bar tab. Both are useful, and a single tool can expose both — pick the mode that matches the cost shape of the underlying operation.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="the-receipt-flow">The Receipt Flow<a href="https://developers.stellar.org/meetings/2026/05/07#the-receipt-flow" class="hash-link" aria-label="Direct link to The Receipt Flow" title="Direct link to The Receipt Flow" translate="no">​</a></h2>
+<p>The channel-mode handshake is worth internalizing because it's where most of the "wait, how does this work?" questions come from:</p>
+<ol>
+<li class="">The client calls the MCP tool. The server returns <code>402 Payment Required</code> with a channel challenge.</li>
+<li class="">The client opens a channel against the server. The client's wallet receives a receipt for that channel.</li>
+<li class="">The client retries the call, this time presenting the receipt. The server returns <code>200</code> and serves the response.</li>
+<li class="">Subsequent high-frequency calls reuse the open channel — no new transaction per call.</li>
+<li class="">When the channel closes (button, timeout, or explicit end-session), a single settlement transaction lands on-chain.</li>
+</ol>
+<p>Charge mode collapses steps 2–5 into a single pay-and-go interaction — you pay, you get the receipt, you make the call, done.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="demo-walkthrough">Demo Walkthrough<a href="https://developers.stellar.org/meetings/2026/05/07#demo-walkthrough" class="hash-link" aria-label="Direct link to Demo Walkthrough" title="Direct link to Demo Walkthrough" translate="no">​</a></h2>
+<p>The full demo is on GitHub and the code is meant to be read alongside this video — it is intentionally not production-ready. The demo is an MCP server with four tools:</p>
+<ul>
+<li class=""><strong><code>get_network_status</code></strong> — free, returns testnet liveness.</li>
+<li class=""><strong><code>lookup_account</code></strong> — free, fetches live XLM balance for an account.</li>
+<li class=""><strong><code>analyze_account_risk</code></strong> — paid, demonstrates charge mode.</li>
+<li class=""><strong><code>explain_latest_transactions</code></strong> — paid, demonstrates channel mode.</li>
+</ul>
+<p>The free tools work the way you'd expect — <code>200 OK</code>, no payment required. They're effectively the free trial of the MCP.</p>
+<p>Calling <code>analyze_account_risk</code> without paying returns <code>402 Payment Required</code> with a charge-mode challenge: "100 base units to use this tool." Paying via the <strong>Run Selected Tool</strong> button produces a receipt, the call retries, and the server returns <code>200</code> with the result. Mode shown in the receipt: <code>charge</code>. One request, one transaction.</p>
+<p>Calling <code>explain_latest_transactions</code> after activating a channel session uses channel mode. The first call against an inactive channel returns <code>402</code>; opening the channel and retrying returns <code>200</code>, and subsequent calls against the same open channel don't require new transactions. The demo includes an explicit <strong>Close Channel</strong> button for clarity — in production you'd almost certainly use a timeout instead, so a user walking away doesn't leave a channel hanging open.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="the-wallet-setup">The Wallet Setup<a href="https://developers.stellar.org/meetings/2026/05/07#the-wallet-setup" class="hash-link" aria-label="Direct link to The Wallet Setup" title="Direct link to The Wallet Setup" translate="no">​</a></h2>
+<p>The demo uses four wallet roles, and the setup is worth calling out:</p>
+<ul>
+<li class=""><strong>Buyer wallet</strong> — the end user paying for tool access.</li>
+<li class=""><strong>Seller wallet</strong> — the MCP operator receiving payment.</li>
+<li class=""><strong>Fee payer wallet</strong> — sponsors gas fees via OpenZeppelin's relayer. Not required for MPP to work, but heavily recommended for UX. In 2026 there's very little excuse to make users hold the native asset just to interact with your tool, and fee sponsorship is the cleanest way to remove that friction.</li>
+<li class=""><strong>Channel commitment key</strong> — a separate wallet that holds the cumulative channel commitments. This is included to illustrate that the actors in an MPP setup can be decomposed — there are paths beyond "I get paid for my service" toward monetizing the commitment-holding role itself. The demo configuration here is illustrative, not best practice.</li>
+</ul>
+<p>The wallets live in-client (the same model used in the AK Gaming hackathon's game studio), so there's no browser extension or passkey prompt in this demo. That's a deliberate choice for clarity, not a recommendation — for anything heading toward production, look at OpenZeppelin's policy-based smart accounts (OZ Policy). With OZ Policy you can express rules like "any transaction over $10 requires my signature," which is most of what you actually want from a smart agent wallet.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="the-exact-moment-an-operation-becomes-mpp">The Exact Moment an Operation Becomes MPP<a href="https://developers.stellar.org/meetings/2026/05/07#the-exact-moment-an-operation-becomes-mpp" class="hash-link" aria-label="Direct link to The Exact Moment an Operation Becomes MPP" title="Direct link to The Exact Moment an Operation Becomes MPP" translate="no">​</a></h2>
+<p>The pivot of the video: where in the code does a regular HTTP handler turn into an MPP-gated handler?</p>
+<p>In the charge-mode handler, the route checks for a valid payment receipt. If the receipt is present and valid, the handler proceeds to the underlying business logic and returns the response. If it isn't, the handler returns a <code>402</code> with the charge challenge attached. That gating block — the small "molecule" sitting between the request and the response — is the entire MPP surface area for charge mode. Flipping the same handler from charge mode to channel mode is essentially a one-line change in the configuration of that gating block.</p>
+<p>If you've worked with x402, charge mode is going to feel like familiar territory. The thing to internalize is that channel mode is <em>not</em> x402 with extra steps — it's a different settlement model for a different cost shape, and it's the reason MPP exists as its own primitive.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="sdks-and-reference-implementations">SDKs and Reference Implementations<a href="https://developers.stellar.org/meetings/2026/05/07#sdks-and-reference-implementations" class="hash-link" aria-label="Direct link to SDKs and Reference Implementations" title="Direct link to SDKs and Reference Implementations" translate="no">​</a></h2>
+<p>Two pointers for going deeper:</p>
+<ul>
+<li class="">The MPP documentation on <a href="https://developers.stellar.org/" target="_blank" rel="noopener noreferrer" class="">developers.stellar.org</a>, including the list of supported MPP intents.</li>
+<li class="">The recommended SDK for creating MPP patterns on Stellar — the easiest path to a working integration.</li>
+</ul>
+<p>For a better-looking, more-complete reference implementation than the demo shown in this stream, look up <a href="https://x.com/ElliotFriend" target="_blank" rel="noopener noreferrer" class="">@ElliotFriend</a> on X — Elliot's MPP demo (including <code>MPP Stellar Buzz</code>, a per-channel chatbot) is a strong example of channel mode used correctly: open a channel when the conversation starts, settle once when it ends, no per-token transaction overhead in between.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="where-mpp-fits">Where MPP Fits<a href="https://developers.stellar.org/meetings/2026/05/07#where-mpp-fits" class="hash-link" aria-label="Direct link to Where MPP Fits" title="Direct link to Where MPP Fits" translate="no">​</a></h2>
+<p>The use cases that map cleanly onto MPP all share one property: <strong>high-frequency paid calls</strong>. That keyword is the easiest filter. If your access pattern is bursty or per-token or per-tick, channel mode. If it's an occasional one-off charge for a piece of data, charge mode. If it's neither, you may not need MPP at all.</p>
+<p>Concrete examples worth thinking about:</p>
+<ul>
+<li class=""><strong>Paid data feeds and oracles</strong> — charge per query, or open a channel for high-frequency consumers.</li>
+<li class=""><strong>Premium developer tools and analytics APIs</strong> — the obvious one. Per-call billing for tools that today rely on API keys and out-of-band invoicing.</li>
+<li class=""><strong>AI-enabled explorers</strong> — paste a wallet or contract address into a chatbot and have it narrate the on-chain activity. Open question on the table during the meeting — a strong opportunity for builders.</li>
+<li class=""><strong>AI auditing tools</strong> — auditing a Soroban contract for vulnerabilities, with the caveat that no AI auditor should be the only thing standing between a project and mainnet.</li>
+<li class=""><strong>Agent service marketplaces</strong> — agents paying agents per-call, with MPP as the settlement layer.</li>
+<li class=""><strong>Usage-based infrastructure</strong> — anything where the cost shape is "metered, often, small."</li>
+</ul>]]></content>
+        <author>
+            <name>Kaan Kacar</name>
+            <uri>https://github.com/kaankacar</uri>
+        </author>
+        <category label="developer" term="developer"/>
+    </entry>
+    <entry>
+        <title type="html"><![CDATA[2026-04-30]]></title>
+        <id>https://developers.stellar.org/meetings/2026/04/30</id>
+        <link href="https://developers.stellar.org/meetings/2026/04/30"/>
+        <updated>2026-04-30T00:00:00.000Z</updated>
+        <summary type="html"><![CDATA[Protocol Discussion: Modular Custom Accounts and Signature Security in Protocol 27]]></summary>
+        <content type="html"><![CDATA[<div class="youtubeEmbed" style="position:relative;width:100%;padding-bottom:56.25%;height:0;margin-bottom:23px"><iframe src="https://www.youtube-nocookie.com/embed/5O1cDDGv7_o?rel=0&amp;modestbranding=1" title="Informational explainer" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" style="position:absolute;top:0;left:0;width:100%;height:100%;border:0px;border-radius:25pt"></iframe></div>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="protocol-discussion-modular-custom-accounts-and-signature-security-in-protocol-27">Protocol Discussion: Modular Custom Accounts and Signature Security in Protocol 27<a href="https://developers.stellar.org/meetings/2026/04/30#protocol-discussion-modular-custom-accounts-and-signature-security-in-protocol-27" class="hash-link" aria-label="Direct link to Protocol Discussion: Modular Custom Accounts and Signature Security in Protocol 27" title="Direct link to Protocol Discussion: Modular Custom Accounts and Signature Security in Protocol 27" translate="no">​</a></h2>
+<p>This protocol meeting covered two related authorization changes coming in Protocol 27, presented by Dmytro Kozhevin: a recap of CAP-71's authentication delegation for custom accounts, and a newly published security addendum, CAP-71-02, that closes a narrow signature replay gap.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="cap-71-recap-authentication-delegation-for-custom-accounts">CAP-71 Recap: Authentication Delegation for Custom Accounts<a href="https://developers.stellar.org/meetings/2026/04/30#cap-71-recap-authentication-delegation-for-custom-accounts" class="hash-link" aria-label="Direct link to CAP-71 Recap: Authentication Delegation for Custom Accounts" title="Direct link to CAP-71 Recap: Authentication Delegation for Custom Accounts" translate="no">​</a></h2>
+<p>CAP-71 has been around for a while and hasn't changed — the news is that it is actually being implemented in Protocol 27. It improves what modular custom accounts can do by adding <strong>built-in delegation support at the protocol level</strong>. A "root" account can delegate logic — for example, the cryptography implementation — to separate "sub-account" contracts. That makes it possible to have an abstract, configurable meta-account shared by multiple users, with the actual signing logic living in different contracts.</p>
+<p>This architecture has already been attempted in the wild (OpenZeppelin's contract examples use it), but until now it was painful: delegating the authorization context required several rounds of pre-simulation to propagate the context. CAP-71-01 builds the delegation mechanism directly into the protocol, which should make life significantly easier for anyone developing custom accounts.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="cap-71-02-closing-a-signature-replay-gap">CAP-71-02: Closing a Signature Replay Gap<a href="https://developers.stellar.org/meetings/2026/04/30#cap-71-02-closing-a-signature-replay-gap" class="hash-link" aria-label="Direct link to CAP-71-02: Closing a Signature Replay Gap" title="Direct link to CAP-71-02: Closing a Signature Replay Gap" translate="no">​</a></h2>
+<p>The reason a separate addendum exists: CAP-71 introduced a new kind of signature payload preimage, and that surfaced a small oversight in the original design. Soroban uses a unified format for signature payloads — a preimage carrying most of the necessary context, hashed with SHA-256 and then signed with an arbitrary cryptographic algorithm. "Most" is the key word: the standard authorization payload does <strong>not</strong> include the signer's address.</p>
+<p>Most of the time this doesn't matter. In a typical token transfer from A to B, the authorizing address is present in the payload anyway. Even when it isn't — like minting with a Stellar Asset Contract, where the admin address is not in the payload — a SAC has only a single admin, so the signature can't be reused.</p>
+<p>The one obscure case where it does matter, described in detail in the security notice published just before the meeting, requires a specific combination of factors to line up:</p>
+<ul>
+<li class="">An admin-style contract where the authorizing signer is <strong>implicit</strong> — fetched from storage rather than named in the payload</li>
+<li class="">That admin being <strong>rotated</strong> to a different public address</li>
+<li class="">The old and new addresses <strong>reusing the same private key</strong></li>
+</ul>
+<p>Sharing a private key across public addresses is rare and generally not something you should do, and an analysis showed this combination has never occurred on-chain. But if it ever did happen, the impact would be serious — a signature could be replayed to, for example, mint a token a second time. The gap was discovered through security audits.</p>
+<p>The fix introduces a new credential type, <code>SOROBAN_CREDENTIALS_ADDRESS_V2</code>, whose only difference from the current address credentials is that the protocol uses an <strong>address-bound signature payload preimage</strong> — the signer's address is guaranteed to be part of what gets signed. The structure is otherwise identical, so supporting it downstream is just a matter of switching from one credential type and payload format to the other.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="migration-guidance">Migration Guidance<a href="https://developers.stellar.org/meetings/2026/04/30#migration-guidance" class="hash-link" aria-label="Direct link to Migration Guidance" title="Direct link to Migration Guidance" translate="no">​</a></h2>
+<p>As of Protocol 27, the old address credentials are <strong>not</strong> being deprecated — the probability of the issue is low enough that there's no urgency for an abrupt, breaking fix. The intention is to migrate to address v2 eventually (possibly Protocol 28 or later): client tooling — the CLI, developer SDKs, and so on — can update to the new credential and payload format at their own pace after the Protocol 27 upgrade, and once the ecosystem has moved, the old format can be deprecated non-disruptively. If you maintain an admin-style contract and are worried in the meantime, you can pass the signer address in the payload explicitly.</p>
+<p>Read more about the proposals here:</p>
+<p><a href="https://github.com/stellar/stellar-protocol/blob/master/core/cap-0071.md" target="_blank" rel="noopener noreferrer" class="">CAP-71</a> - <a href="https://github.com/orgs/stellar/discussions/1784" target="_blank" rel="noopener noreferrer" class="">Discussion</a></p>
+<p><a href="https://github.com/stellar/stellar-protocol/blob/master/core/cap-0071-01.md" target="_blank" rel="noopener noreferrer" class="">CAP-71-01</a> - <a href="https://github.com/orgs/stellar/discussions/1784" target="_blank" rel="noopener noreferrer" class="">Discussion</a></p>
+<p><a href="https://github.com/stellar/stellar-protocol/blob/master/core/cap-0071-02.md" target="_blank" rel="noopener noreferrer" class="">CAP-71-02</a> - <a href="https://github.com/orgs/stellar/discussions/1899" target="_blank" rel="noopener noreferrer" class="">Discussion</a></p>]]></content>
+        <author>
+            <name>Kaan Kacar</name>
+            <uri>https://github.com/kaankacar</uri>
+        </author>
+        <category label="developer" term="developer"/>
+    </entry>
+    <entry>
+        <title type="html"><![CDATA[2026-04-23]]></title>
+        <id>https://developers.stellar.org/meetings/2026/04/23</id>
+        <link href="https://developers.stellar.org/meetings/2026/04/23"/>
+        <updated>2026-04-23T00:00:00.000Z</updated>
+        <summary type="html"><![CDATA[Messari State of Stellar Q1 2026]]></summary>
+        <content type="html"><![CDATA[<div class="youtubeEmbed" style="position:relative;width:100%;padding-bottom:56.25%;height:0;margin-bottom:23px"><iframe src="https://www.youtube-nocookie.com/embed/E6asxPAA3wU?rel=0&amp;modestbranding=1" title="Informational explainer" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" style="position:absolute;top:0;left:0;width:100%;height:100%;border:0px;border-radius:25pt"></iframe></div>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="messari-state-of-stellar-q1-2026">Messari State of Stellar Q1 2026<a href="https://developers.stellar.org/meetings/2026/04/23#messari-state-of-stellar-q1-2026" class="hash-link" aria-label="Direct link to Messari State of Stellar Q1 2026" title="Direct link to Messari State of Stellar Q1 2026" translate="no">​</a></h2>
+<p>Messari published their State of Stellar Q1 2026 report ahead of this meeting, and there are numbers in it that every developer building on Stellar should understand — not as vanity metrics, but as signal for where the ecosystem is actually heading and where the real opportunities are.</p>
+<p><strong>RWA market cap</strong> — $2 billion at the time of the meeting, up from approximately $1.5 billion at the end of Q1 2026. That is roughly a 33% increase quarter over quarter and a 3x increase year over year from the $500 million mark in Q1 2025. The biggest single-quarter move across any metric in the report.</p>
+<p><strong>Average daily smart contract volume</strong> — $16 million per day in the last quarter. One year ago it was $2 million per day. For five or six consecutive quarters, Soroban transaction volume has only gone up. This is real usage: contracts being called, operations executed, applications that real users are touching.</p>
+<p><strong>Stablecoin market cap</strong> — $300 million, up 20% quarter over quarter. Protocols driving this include Aquarius, Blend, and SolarSwap.</p>
+<p>The synthesis: Stellar is executing a compounding flywheel that is now clearly visible. Institutional capital flows in via RWAs, higher TVL attracts more DeFi protocols, more DeFi protocols drive more Soroban invocations, more on-chain activity attracts more developers, more developers build more user-facing applications, more users generate more stablecoin and payment volume — and all of that makes Stellar more compelling for the next wave of institutional adoption.</p>
+<p>The full report is on <a href="https://messari.io/" target="_blank" rel="noopener noreferrer" class="">messari.io</a> and is worth reading in detail.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="moneygram-and-sdf-extend-partnership">MoneyGram and SDF Extend Partnership<a href="https://developers.stellar.org/meetings/2026/04/23#moneygram-and-sdf-extend-partnership" class="hash-link" aria-label="Direct link to MoneyGram and SDF Extend Partnership" title="Direct link to MoneyGram and SDF Extend Partnership" translate="no">​</a></h2>
+<p>Announced on April 22nd at Stellar House in Mexico City: MoneyGram and the Stellar Development Foundation have announced a multi-year extension of their partnership. The framing is important — this is about scaling real-world stablecoin utility globally.</p>
+<p>This partnership has been running since 2021. In that time they built the world's largest cash on- and off-ramp for digital assets, launched the MoneyGram Ramps API so developers can plug into the network directly, and created a stablecoin balance feature inside the MoneyGram app that lets customers hold funds in digital dollars and cash out at physical locations.</p>
+<p>The next phase focuses on Latin America. The MoneyGram app with stablecoin support first went live in Colombia. With this announcement, it is extending to El Salvador, with more countries across Central and South America planned throughout 2026. The stack powering this is Stellar, Cross-Mint, and Circle's USDC.</p>
+<p>The real-world scale here: MoneyGram operates nearly half a million retail locations across 200+ countries. That is not a sandbox — that is live infrastructure for people sending money to families and communities that depend on cash-based services. Stellar Development Foundation CEO Denelle Dixon said: "Stellar was built on the belief that the global financial system should work for everyone." This partnership is what that looks like in practice.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="aquarius-hits-50m-tvl">Aquarius Hits $50M TVL<a href="https://developers.stellar.org/meetings/2026/04/23#aquarius-hits-50m-tvl" class="hash-link" aria-label="Direct link to Aquarius Hits $50M TVL" title="Direct link to Aquarius Hits $50M TVL" translate="no">​</a></h2>
+<p>Aquarius, the decentralized liquidity management platform built on Stellar, crossed $50 million in total value locked. Aquarius is Stellar's answer to DeFi liquidity infrastructure — AMMs, liquidity pools, reward systems — and it is designed to be a foundational liquidity layer that other Stellar protocols build on top of. When Aquarius TVL grows, the entire Stellar DeFi ecosystem becomes more liquid and more efficient.</p>
+<p>For developers asking where to start: Aquarius has been investing in documentation. Their docs at <a href="https://docs.aqua.network/" target="_blank" rel="noopener noreferrer" class="">docs.aqua.network</a> now include real code examples — how to execute swaps through the optimal path, how to claim LP rewards, how to add fee configurations to swaps for building routers into existing applications. If you are building anything on Stellar that involves swapping assets, yield strategies, or liquidity-adjacent features, the Aquarius docs are a solid reference for what production-quality Stellar DeFi integration looks like.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="stellar-agents-hackathon-260-projects">Stellar Agents Hackathon: 260+ Projects<a href="https://developers.stellar.org/meetings/2026/04/23#stellar-agents-hackathon-260-projects" class="hash-link" aria-label="Direct link to Stellar Agents Hackathon: 260+ Projects" title="Direct link to Stellar Agents Hackathon: 260+ Projects" translate="no">​</a></h2>
+<p>The Stellar Agents hackathon on DoraHacks just wrapped, with around 600 hackers submitting over 260 projects. The hackathon was focused on agentic payments using x402 and MPP — the two protocols covered in the previous developer meeting. What the hackathon showed is what happens when you put those primitives in the hands of 600 builders from around the world.</p>
+<p>The following are standout submissions, highlighted not to endorse any specific project but to use them as a window into what is actually possible to build on Stellar right now.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="stellar-8004--on-chain-identity-and-reputation-for-ai-agents">Stellar 8004 — On-Chain Identity and Reputation for AI Agents<a href="https://developers.stellar.org/meetings/2026/04/23#stellar-8004--on-chain-identity-and-reputation-for-ai-agents" class="hash-link" aria-label="Direct link to Stellar 8004 — On-Chain Identity and Reputation for AI Agents" title="Direct link to Stellar 8004 — On-Chain Identity and Reputation for AI Agents" translate="no">​</a></h3>
+<p><a href="https://stellar8004.com/" target="_blank" rel="noopener noreferrer" class="">stellar8004.com</a> addresses one of the most important unsolved problems in the emerging AI agent economy: there is no standard way to find agents, verify who built them, or evaluate whether they are reliable. You cannot search for a trustworthy A2A agent for a given task and get a verifiable answer. Every platform has its own walled garden, and there is no portable reputation.</p>
+<p>Stellar 8004 takes its name from ERC-8004 on Ethereum (now going multi-chain) and gives every AI agent a blockchain-backed identity, a discoverable endpoint, and a reputation system you can verify on-chain. Think of it as LinkedIn for agents, except the reputation is not self-reported — it is attested on-chain.</p>
+<p>The stack is built on three Soroban contracts:</p>
+<ul>
+<li class=""><strong>Identity registry contract</strong> — agents register with on-chain metadata and wallet binding</li>
+<li class=""><strong>Reputation registry contract</strong> — users leave feedback with average scoring</li>
+<li class=""><strong>Validation registry contract</strong> — third-party organizations can endorse agents through on-chain attestations</li>
+</ul>
+<p>The live explorer at <a href="https://stellar8004.com/" target="_blank" rel="noopener noreferrer" class="">stellar8004.com</a> lets you browse registered agents, check reputation scores, interact with them, and leave feedback. Registered agents can also advertise x402 and MPP payment support in their metadata, so agents can be discovered and paid per query in USDC.</p>
+<p>For builders, the team also published a TypeScript SDK at <code>tryon.lab/stellar8004</code> and a Claude Code skill with slash commands for building on top of the registry with AI assistance.</p>
+<p>The conceptually powerful part is the agent-to-agent trust loop. When a DeFi agent wants to call a data analysis agent, it currently has no way to verify that agent is legitimate or reliable. With a registry like this, it can query on-chain, check the score, verify attestations, and decide whether to proceed programmatically.</p>
+<p>One note for anyone building in this space: distribution is everything for infrastructure like this. In just one hackathon there were four or five similar projects targeting the same use case. If you are building an agent registry or identity system, check the ecosystem page first and understand the competitive landscape.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="mpp-router-rozo">MPP Router (Rozo)<a href="https://developers.stellar.org/meetings/2026/04/23#mpp-router-rozo" class="hash-link" aria-label="Direct link to MPP Router (Rozo)" title="Direct link to MPP Router (Rozo)" translate="no">​</a></h3>
+<p><a href="https://mpprouter.dev/" target="_blank" rel="noopener noreferrer" class="">mpprouter.dev</a> is a payment network router specifically designed for agent-to-agent micropayments. On Tempo, there are over 400 MPP endpoints. This router makes it possible for users and agents on Stellar to reach and use those endpoints by paying on Stellar.</p>
+<p>It's on mainnet. The problem it solves is real and concrete: 400 agents on another network, and this project makes them reachable from Stellar. The way to find good project ideas is to find the pain points of a network — this one found a clear one.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="stellar-security-audit-agent">Stellar Security Audit Agent<a href="https://developers.stellar.org/meetings/2026/04/23#stellar-security-audit-agent" class="hash-link" aria-label="Direct link to Stellar Security Audit Agent" title="Direct link to Stellar Security Audit Agent" translate="no">​</a></h3>
+<p>With over $3 billion lost to hacks and exploits in 2025 (the worst year on record), and the industry already down over $600 million in just the first weeks of 2026, autonomous smart contract auditing is becoming genuinely important infrastructure.</p>
+<p>Built under the handle Chinese Powered, this is an autonomous AI security auditor for Soroban smart contracts. It works in three steps:</p>
+<ol>
+<li class=""><strong>Bytecode verification</strong> — fetches the deployed WASM bytecode from Stellar and compares it against the source code. This step matters because one of the most common attack vectors is deploying different code than what was audited.</li>
+<li class=""><strong>AI-powered vulnerability analysis</strong> — runs a full checklist equivalent to the OWASP top categories for smart contracts: access control flaws, integer overflows, reentrancy, storage exploits, initialization attacks, denial-of-service vectors.</li>
+<li class=""><strong>On-chain audit record</strong> — audit results are written immutably into a smart contract on Stellar, creating a public, verifiable audit record that anyone can query.</li>
+</ol>
+<p>The insight that makes this composable is step three: by writing audit results on-chain, you create an auditing layer that other contracts or agents can query. The project is currently on testnet and needs more work before it is production-ready — particularly around trust establishment and distribution — but the vision it represents is one of the most important unsolved problems in DeFi.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="stellar-mobile-agent-builder">Stellar Mobile Agent Builder<a href="https://developers.stellar.org/meetings/2026/04/23#stellar-mobile-agent-builder" class="hash-link" aria-label="Direct link to Stellar Mobile Agent Builder" title="Direct link to Stellar Mobile Agent Builder" translate="no">​</a></h3>
+<p>Over 75% of crypto users access services via mobile, and in the markets where Stellar is most relevant — Latin America, Africa, Southeast Asia — mobile-first is not a preference, it is the only option.</p>
+<p>Built by Sam Felix, this project flips the assumption that running an AI agent requires cloud infrastructure. Take an old Android phone, run a FastAPI agent runtime on it using Ollama for local inference, and connect it to Stellar via MPP for per-request micropayments. Anyone with a phone can become a node in the AI agent economy.</p>
+<p>What is particularly clever is the no-code layer on top: a visual drag-and-drop builder where non-technical users can design agent workflows without writing any code. The exact use case is letting someone in an emerging market use their device to provide or access AI capabilities that would otherwise be inaccessible or expensive. Not yet on mainnet, but the direction is worth noting for anyone building for global audiences.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="talos--autonomous-agent-corporation-framework">Talos — Autonomous Agent Corporation Framework<a href="https://developers.stellar.org/meetings/2026/04/23#talos--autonomous-agent-corporation-framework" class="hash-link" aria-label="Direct link to Talos — Autonomous Agent Corporation Framework" title="Direct link to Talos — Autonomous Agent Corporation Framework" translate="no">​</a></h3>
+<p>Highlighted as one of the most polished projects from the CDMX hackathon, Talos is an autonomous agent corporation framework. It lets you create sub-agents and orchestrate them to act as corporate employees: dedicated agents for GTM strategy, marketing campaigns, engineering lead hiring, and so on. The payment layer runs on x402. If you have worked with Paperclip or similar autonomous agent setups before, the mental model will be familiar. One of the most common questions at the CDMX hackathon was how to use AI to steer an entire project or company — Talos is one of the more complete answers that came out of that event.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="stellar-house-mexico-city">Stellar House Mexico City<a href="https://developers.stellar.org/meetings/2026/04/23#stellar-house-mexico-city" class="hash-link" aria-label="Direct link to Stellar House Mexico City" title="Direct link to Stellar House Mexico City" translate="no">​</a></h2>
+<p>Stellar House is SDF's format for bringing together builders, partners, and ecosystem members in a physical space — typically two to three days of talks, workshops, and demos. The Mexico City event just wrapped, and all sessions were live-streamed on the SDF YouTube channel (find them under the Playlists section of the channel).</p>
+<p>Mexico City was particularly significant for two reasons: the MoneyGram announcement came out of it, and Mexico and Latin America broadly are central to Stellar's mission. The event also featured pitch presentations from several teams that came through the CDMX hackathon — building a pipeline from hackathon to Stellar House is a format that seems to be working.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="stellar-ai-guide-mx">Stellar AI Guide MX<a href="https://developers.stellar.org/meetings/2026/04/23#stellar-ai-guide-mx" class="hash-link" aria-label="Direct link to Stellar AI Guide MX" title="Direct link to Stellar AI Guide MX" translate="no">​</a></h2>
+<p>For developers building on Stellar with AI tooling, a new open-source resource is available at <a href="https://github.com/kaankacar/stellar-ai-guide-mx" target="_blank" rel="noopener noreferrer" class="">github.com/kaankacar/stellar-ai-guide-mx</a>. Check the building with AI section at <a href="https://developers.stellar.org/" target="_blank" rel="noopener noreferrer" class="">developers.stellar.org</a> for the full set of AI resources, including the <code>llms.txt</code> file for feeding Stellar context into LLMs and Stella, the AI assistant trained on Stellar documentation.</p>]]></content>
+        <author>
+            <name>Kaan Kacar</name>
+            <uri>https://github.com/kaankacar</uri>
+        </author>
+        <category label="developer" term="developer"/>
+    </entry>
+    <entry>
+        <title type="html"><![CDATA[2026-04-16]]></title>
+        <id>https://developers.stellar.org/meetings/2026/04/16</id>
+        <link href="https://developers.stellar.org/meetings/2026/04/16"/>
+        <updated>2026-04-16T00:00:00.000Z</updated>
+        <summary type="html"><![CDATA[Protocol 26 "Yardstick" Hits Testnet]]></summary>
+        <content type="html"><![CDATA[<div class="youtubeEmbed" style="position:relative;width:100%;padding-bottom:56.25%;height:0;margin-bottom:23px"><iframe src="https://www.youtube-nocookie.com/embed/u3zmNZXHYHw?rel=0&amp;modestbranding=1" title="Informational explainer" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" style="position:absolute;top:0;left:0;width:100%;height:100%;border:0px;border-radius:25pt"></iframe></div>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="protocol-26-yardstick-hits-testnet">Protocol 26 "Yardstick" Hits Testnet<a href="https://developers.stellar.org/meetings/2026/04/16#protocol-26-yardstick-hits-testnet" class="hash-link" aria-label="Direct link to Protocol 26 &quot;Yardstick&quot; Hits Testnet" title="Direct link to Protocol 26 &quot;Yardstick&quot; Hits Testnet" translate="no">​</a></h2>
+<p>Protocol 26, codenamed Yardstick, went live on testnet on April 16, 2026 at 17:00 UTC — literally the day of this meeting. Mainnet validator votes are scheduled for May 6th. If you are running any kind of infrastructure on Stellar — nodes, SDKs, integrations — now is the time to pull the Protocol 26 changes, update your SDKs, and test against testnet before the mainnet vote. The <code>#protocol-next</code> channel in the Stellar developer Discord is where the ecosystem coordinates during upgrades.</p>
+<p>Two CAPs shipped with this release:</p>
+<p><strong>CAP-81</strong> rewrites the Soroban eviction scan. Instead of scanning the BucketList on disk, eviction now works directly from in-memory Soroban state. The result is faster evictions, fewer disk reads, and more efficient node operations. This is the kind of under-the-hood improvement that compounds as Soroban usage grows — less I/O overhead means the network handles growing state more gracefully at scale.</p>
+<p><strong>CAP-82</strong> adds checked arithmetic variants for the existing 256-bit integer host functions. Where the current functions trap on overflow, the new checked variants return <code>Void</code> instead, letting contracts handle arithmetic errors explicitly and gracefully rather than panicking. If you're writing DeFi contracts — lending protocols, swap routers, pricing curves — this matters: checked arithmetic means operations fail explicitly and predictably instead of silently wrapping or trapping.</p>
+<p><a href="https://github.com/stellar/stellar-protocol/blob/master/core/cap-0081.md" target="_blank" rel="noopener noreferrer" class="">CAP-81</a> — <a href="https://github.com/orgs/stellar/discussions/1868" target="_blank" rel="noopener noreferrer" class="">Discussion</a></p>
+<p><a href="https://github.com/stellar/stellar-protocol/blob/master/core/cap-0082.md" target="_blank" rel="noopener noreferrer" class="">CAP-82</a> — <a href="https://github.com/orgs/stellar/discussions/1834" target="_blank" rel="noopener noreferrer" class="">Discussion</a></p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="ecosystem-snapshot-2b-in-tokenized-real-world-assets">Ecosystem Snapshot: $2B in Tokenized Real-World Assets<a href="https://developers.stellar.org/meetings/2026/04/16#ecosystem-snapshot-2b-in-tokenized-real-world-assets" class="hash-link" aria-label="Direct link to Ecosystem Snapshot: $2B in Tokenized Real-World Assets" title="Direct link to Ecosystem Snapshot: $2B in Tokenized Real-World Assets" translate="no">​</a></h2>
+<p>Stellar has crossed $2 billion in tokenized real-world assets on the network — more than 4x growth in 12 months and 2.5x growth year-to-date as of April. This is not speculative TVL. These are actual financial instruments: tokenized treasuries, bonds, and private credit sitting on-chain today. The institutional names driving this are serious: Franklin Templeton's tokenized treasury fund, Ondo Finance, RedSwan Digital, and Centrifuge. These are not crypto-native experiments — these are traditional finance institutions choosing Stellar as their settlement layer.</p>
+<p>What makes this meaningful for developers is that those $2 billion in assets do not just sit there. They are becoming collateral in lending protocols, being deployed in DeFi, and earning yields. That creates real primitives to build on top of.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="defi-ecosystem-update">DeFi Ecosystem Update<a href="https://developers.stellar.org/meetings/2026/04/16#defi-ecosystem-update" class="hash-link" aria-label="Direct link to DeFi Ecosystem Update" title="Direct link to DeFi Ecosystem Update" translate="no">​</a></h2>
+<p>The Stellar DeFi ecosystem is maturing quickly. Here is the current state:</p>
+<p><strong>Blend</strong> has crossed $80 million in TVL, making it one of the most significant lending protocol deployments on Stellar.</p>
+<p><strong>Stellar Templars Protocol</strong> added six new real-world assets to lending markets on Stellar. You can now borrow stablecoins against tokenized institutional assets. The newly added collateral types include:</p>
+<ul>
+<li class=""><strong>DEJA</strong> (Centrifuge) — a AAA-rated CLO strategy</li>
+<li class=""><strong>DEJTRY</strong> — the Janus Henderson short-term US Treasury strategy</li>
+<li class=""><strong>CETES</strong> and <strong>USTRY</strong> (EtherFuse) — tokenized Mexican and US Treasury exposure</li>
+<li class=""><strong>soBTC/USDC pair</strong> — you can now use Bitcoin as collateral to borrow on Stellar</li>
+</ul>
+<p>Institutional-grade RWAs as DeFi collateral is a significant milestone. Sovereign debt meeting DeFi accessibility is a phrase worth sitting with.</p>
+<p><strong>Sushi</strong> deployed their first concentrated liquidity DEX on Stellar. PYUSD/USDC and XLM/USDC pools are live. Cross-chain functionality is coming soon through Squid Router, which connects Stellar assets to 80+ other blockchains.</p>
+<p><strong>EURA</strong> — a MiCA-compliant euro stablecoin from All Unity — is live on Stellar. This is a fully backed, regulated euro stablecoin built for institutional use. A regulated euro stablecoin on Stellar is a notable addition for builders targeting European markets or building compliant financial applications.</p>
+<p>For a full picture of where Stellar DeFi stands, the SDF published a post titled <em>"What the DeFi is happening on Stellar?"</em> that captures how the ecosystem has been quietly maturing while others debate narratives.</p>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="x402-and-mpp-agentic-payments-are-live-on-stellar-mainnet">x402 and MPP: Agentic Payments Are Live on Stellar Mainnet<a href="https://developers.stellar.org/meetings/2026/04/16#x402-and-mpp-agentic-payments-are-live-on-stellar-mainnet" class="hash-link" aria-label="Direct link to x402 and MPP: Agentic Payments Are Live on Stellar Mainnet" title="Direct link to x402 and MPP: Agentic Payments Are Live on Stellar Mainnet" translate="no">​</a></h2>
+<p>Both x402 and MPP — the two leading agentic payment protocols — are now live on Stellar mainnet. This is a significant milestone for anyone building at the intersection of AI and payments.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="the-problem-they-solve">The Problem They Solve<a href="https://developers.stellar.org/meetings/2026/04/16#the-problem-they-solve" class="hash-link" aria-label="Direct link to The Problem They Solve" title="Direct link to The Problem They Solve" translate="no">​</a></h3>
+<p>The entire payment infrastructure of the internet was designed for humans. An AI agent that needs to call a paid API hits a fundamental wall: there's a form, a billing dashboard, an API key a human configured. The agent hits a paywall and the workflow breaks. x402 and MPP solve this by making machine-to-machine payments as simple as an HTTP request.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="x402">x402<a href="https://developers.stellar.org/meetings/2026/04/16#x402" class="hash-link" aria-label="Direct link to x402" title="Direct link to x402" translate="no">​</a></h3>
+<p>x402 is built on the HTTP 402 "Payment Required" status code — a code that has existed since the 1990s but was never meaningfully implemented until now. The flow is simple: an agent requests a resource, the server responds with a price, the agent authorizes stablecoin payment, and the resource is delivered. One HTTP round trip.</p>
+<p>On Stellar, this settles in under 5 seconds. Stellar's fees — approximately 0.00001 XLM per transaction — are essential here: if your transaction fee costs more than the payment itself, micropayments do not work. Stellar also has USDC, PYUSD, and USDY as first-class native assets — not bridged, not wrapped.</p>
+<p>x402 is co-governed by Coinbase (who launched it), Cloudflare, Google, and Visa. Google has integrated it into their agentic payments protocol. Cloudflare built it into their pay-per-crawl tooling. The SDF also brought OpenZeppelin into the picture — they secure over $130 billion in on-chain assets — to power the x402 facilitator and provide audited smart account contracts with programmable spending limits and guardrails.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="mpp-machine-payments-protocol">MPP (Machine Payments Protocol)<a href="https://developers.stellar.org/meetings/2026/04/16#mpp-machine-payments-protocol" class="hash-link" aria-label="Direct link to MPP (Machine Payments Protocol)" title="Direct link to MPP (Machine Payments Protocol)" translate="no">​</a></h3>
+<p>MPP was co-developed by Stripe and Tempo and launched last month, and it is live on Stellar. Where x402 handles one payment per request, MPP introduces <em>sessions</em>: an agent pre-authorizes a spending limit up front, then streams micro-payments within that session, settling in bulk at the end. If your agent is querying a data feed thousands of times an hour, MPP sessions are the right model — you avoid the overhead of a per-request authorization for every single call.</p>
+<p>On Stellar, MPP settles via Soroban SAC transfers. Agents never need to hold gas tokens because the SDK handles server-sponsored fees.</p>
+<p>MPP launched with over 100 integrated services including Stripe, Anthropic, OpenAI, Shopify, and Visa. The core spec has been submitted to the IETF for standardization as the official HTTP payment standard.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="the-full-picture">The Full Picture<a href="https://developers.stellar.org/meetings/2026/04/16#the-full-picture" class="hash-link" aria-label="Direct link to The Full Picture" title="Direct link to The Full Picture" translate="no">​</a></h3>
+<p>To connect this back to everything else in this meeting: those DeFi protocols, tokenized assets, and stablecoin rails all become accessible to AI agents through these payment primitives. An agent can borrow against a tokenized treasury, pay for a data feed, execute a swap, and settle cross-chain — all programmatically, without a human in the loop.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="resources-for-building">Resources for Building<a href="https://developers.stellar.org/meetings/2026/04/16#resources-for-building" class="hash-link" aria-label="Direct link to Resources for Building" title="Direct link to Resources for Building" translate="no">​</a></h3>
+<p>If you want to start building with these protocols, the best starting points are:</p>
+<ul>
+<li class=""><a href="https://developers.stellar.org/" target="_blank" rel="noopener noreferrer" class="">developers.stellar.org</a> → Build → Agentic Payments — x402 and MPP docs are here</li>
+<li class=""><a href="https://github.com/stellar/stellar-dev-skill" target="_blank" rel="noopener noreferrer" class="">Stellar Dev Skill</a> — a plugin for AI coding assistants (Claude Code, OpenCode, Codex) that gives your AI assistant deep current knowledge of the full Stellar stack including x402 and MPP</li>
+<li class=""><a href="https://developers.stellar.org/docs/tools/ai" target="_blank" rel="noopener noreferrer" class="">developers.stellar.org/tools/ai</a> — the building with AI page, including links to the <code>llms.txt</code> file for feeding Stellar context directly into LLM prompts, and Stella, the AI assistant trained on Stellar docs</li>
+</ul>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="guest-demo-noether--first-perpetual-dex-on-stellar">Guest Demo: Noether — First Perpetual DEX on Stellar<a href="https://developers.stellar.org/meetings/2026/04/16#guest-demo-noether--first-perpetual-dex-on-stellar" class="hash-link" aria-label="Direct link to Guest Demo: Noether — First Perpetual DEX on Stellar" title="Direct link to Guest Demo: Noether — First Perpetual DEX on Stellar" translate="no">​</a></h2>
+<p>The second half of this meeting featured Yahya and Mert, co-founders of <strong>Noether</strong> from the No Ethers team, recent graduates of the latest Stellar Community Fund funding round. Noether is, to their knowledge, the first perpetual DEX on Stellar.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="why-a-perp-dex-on-stellar">Why a Perp DEX on Stellar?<a href="https://developers.stellar.org/meetings/2026/04/16#why-a-perp-dex-on-stellar" class="hash-link" aria-label="Direct link to Why a Perp DEX on Stellar?" title="Direct link to Why a Perp DEX on Stellar?" translate="no">​</a></h3>
+<p>The opportunity is straightforward: every serious DeFi ecosystem needs a perpetual DEX, and Stellar did not have one. Mert has been building on Stellar since smart contracts launched on the network, has hosted over 10 Stellar workshops in Turkey, and has mentored builders and served as a judge in Stellar hackathons. When Yahya identified the gap, they locked in and built.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="what-they-showed">What They Showed<a href="https://developers.stellar.org/meetings/2026/04/16#what-they-showed" class="hash-link" aria-label="Direct link to What They Showed" title="Direct link to What They Showed" translate="no">​</a></h3>
+<p>Mert walked through a live testnet demo of Noether:</p>
+<p><strong>Faucet</strong> — A testnet faucet page where users can claim up to 1,000 USDC per day. Before claiming, users need to set up a trustline to the testnet USDC asset — a standard Stellar requirement for holding any non-native asset.</p>
+<p><strong>Trade Page</strong> — The core trading interface has three components:</p>
+<ul>
+<li class=""><strong>Order book</strong> on the left, showing pending limit orders with long orders on one side and short orders on the other, and the current market price in the middle.</li>
+<li class=""><strong>Price chart</strong> in the center, pulling real-time price data from Binance via a price proxy.</li>
+<li class="">Three trading pairs available at launch, with more pairs planned for the following month.</li>
+</ul>
+<p><strong>Smart Contract Status</strong> — The contracts are currently at MVP stage. Mainnet launch is planned approximately two to three months out, following a smart contract audit that will be supported by the Stellar Development Foundation. The team emphasized they will not launch on mainnet before the audit is complete.</p>
+<h3 class="anchor anchorTargetStickyNavbar_CXV1" id="on-ai-in-development">On AI in Development<a href="https://developers.stellar.org/meetings/2026/04/16#on-ai-in-development" class="hash-link" aria-label="Direct link to On AI in Development" title="Direct link to On AI in Development" translate="no">​</a></h3>
+<p>When asked what percentage of their codebase was written with AI assistance, Mert estimated around 70% — with an important caveat: the core financial logic in smart contracts was written and verified by hand. Their approach was to use AI for the less critical parts (landing pages, boilerplate, tooling) while personally reviewing and proving the correctness of anything financially sensitive. As Mert put it: "We write the code with AI but we read it."</p>]]></content>
+        <author>
+            <name>Kaan Kacar</name>
+            <uri>https://github.com/kaankacar</uri>
+        </author>
+        <category label="developer" term="developer"/>
+    </entry>
+    <entry>
+        <title type="html"><![CDATA[2026-02-26]]></title>
+        <id>https://developers.stellar.org/meetings/2026/02/26</id>
+        <link href="https://developers.stellar.org/meetings/2026/02/26"/>
+        <updated>2026-02-26T00:00:00.000Z</updated>
+        <summary type="html"><![CDATA[Protocol Discussion]]></summary>
+        <content type="html"><![CDATA[<div class="youtubeEmbed" style="position:relative;width:100%;padding-bottom:56.25%;height:0;margin-bottom:23px"><iframe src="https://www.youtube-nocookie.com/embed/nLxODJal-xQ?rel=0&amp;modestbranding=1" title="Informational explainer" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" style="position:absolute;top:0;left:0;width:100%;height:100%;border:0px;border-radius:25pt"></iframe></div>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="protocol-discussion">Protocol Discussion<a href="https://developers.stellar.org/meetings/2026/02/26#protocol-discussion" class="hash-link" aria-label="Direct link to Protocol Discussion" title="Direct link to Protocol Discussion" translate="no">​</a></h2>
+<p>In this protocol meeting we had two CAPs to discuss and that was CAP-81 and CAP-82.</p>
+<p>CAP-81: This CAP introduces a simpler and more efficient eviction scan process. Instead of scanning the BucketList, the new eviction scan just uses in-memory Soroban state. This simplifies the logic while reducing disk reads and speeding up eviction speed.</p>
+<p>CAP-82: This CAP adds checked variants of the existing 256-bit integer arithmetic host functions. Unlike the existing functions which trap on overflow, the checked variants return Void on overflow, allowing contracts to handle arithmetic errors gracefully.</p>
+<p>Read more about the proposals here:</p>
+<p><a href="https://github.com/stellar/stellar-protocol/blob/master/core/cap-0081.md" target="_blank" rel="noopener noreferrer" class="">CAP-81</a> - <a href="https://github.com/orgs/stellar/discussions/1868" target="_blank" rel="noopener noreferrer" class="">Discussion</a></p>
+<p><a href="https://github.com/stellar/stellar-protocol/blob/master/core/cap-0082.md" target="_blank" rel="noopener noreferrer" class="">CAP-82</a> - <a href="https://github.com/orgs/stellar/discussions/1834" target="_blank" rel="noopener noreferrer" class="">Discussion</a></p>]]></content>
+        <author>
+            <name>Carsten Jacobsen</name>
+            <uri>https://github.com/carstenjacobsen</uri>
+        </author>
+        <category label="developer" term="developer"/>
+    </entry>
+    <entry>
+        <title type="html"><![CDATA[2026-01-29]]></title>
+        <id>https://developers.stellar.org/meetings/2026/01/29</id>
+        <link href="https://developers.stellar.org/meetings/2026/01/29"/>
+        <updated>2026-01-29T00:00:00.000Z</updated>
+        <summary type="html"><![CDATA[Protocol Discussion]]></summary>
+        <content type="html"><![CDATA[<div class="youtubeEmbed" style="position:relative;width:100%;padding-bottom:56.25%;height:0;margin-bottom:23px"><iframe src="https://www.youtube-nocookie.com/embed/TXuKiEEwEsU?rel=0&amp;modestbranding=1" title="Informational explainer" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" style="position:absolute;top:0;left:0;width:100%;height:100%;border:0px;border-radius:25pt"></iframe></div>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="protocol-discussion">Protocol Discussion<a href="https://developers.stellar.org/meetings/2026/01/29#protocol-discussion" class="hash-link" aria-label="Direct link to Protocol Discussion" title="Direct link to Protocol Discussion" translate="no">​</a></h2>
+<p>We have one new CAP to discuss and that is CAP-80. This proposal adds BN254 Multi-Scalar Multiplication and modular arithmetic used in a variety of ZK proof applications. Adding host support for these will greatly improve the performance of these use cases.</p>
+<p>We also follow up on a previous CAP - the CAP-73.</p>
+<p>Read more about the proposal here:</p>
+<p><a href="https://github.com/stellar/stellar-protocol/blob/master/core/cap-0080.md" target="_blank" rel="noopener noreferrer" class="">CAP-80</a> - <a href="https://github.com/orgs/stellar/discussions/1826" target="_blank" rel="noopener noreferrer" class="">Discussion</a></p>
+<p><a href="https://github.com/stellar/stellar-protocol/blob/master/core/cap-0073.md" target="_blank" rel="noopener noreferrer" class="">CAP-73</a> - <a href="https://github.com/orgs/stellar/discussions/1668" target="_blank" rel="noopener noreferrer" class="">Discussion</a></p>]]></content>
+        <author>
+            <name>Carsten Jacobsen</name>
+            <uri>https://github.com/carstenjacobsen</uri>
+        </author>
+        <category label="developer" term="developer"/>
+    </entry>
+    <entry>
+        <title type="html"><![CDATA[2026-01-22]]></title>
+        <id>https://developers.stellar.org/meetings/2026/01/22</id>
+        <link href="https://developers.stellar.org/meetings/2026/01/22"/>
+        <updated>2026-01-22T00:00:00.000Z</updated>
+        <summary type="html"><![CDATA[OpenZeppelin Q4 Releases]]></summary>
+        <content type="html"><![CDATA[<div class="youtubeEmbed" style="position:relative;width:100%;padding-bottom:56.25%;height:0;margin-bottom:23px"><iframe src="https://www.youtube-nocookie.com/embed/pq4xrdRzfIs?rel=0&amp;modestbranding=1" title="Informational explainer" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" style="position:absolute;top:0;left:0;width:100%;height:100%;border:0px;border-radius:25pt"></iframe></div>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="openzeppelin-q4-releases">OpenZeppelin Q4 Releases<a href="https://developers.stellar.org/meetings/2026/01/22#openzeppelin-q4-releases" class="hash-link" aria-label="Direct link to OpenZeppelin Q4 Releases" title="Direct link to OpenZeppelin Q4 Releases" translate="no">​</a></h2>
+<p>In this year’s first Stellar Developer Meeting, on Thursday, January 22nd at 8am PT on Twitch, we will catch up with Ozgun and Boyan from the OpenZeppelin team and take a look at the libraries released in Q4 last year.</p>
+<div class="youtubeEmbed" style="position:relative;width:100%;padding-bottom:56.25%;height:0;margin-bottom:23px"><iframe src="https://www.youtube-nocookie.com/embed/CetcWbsdRdE?rel=0&amp;modestbranding=1" title="Informational explainer" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" style="position:absolute;top:0;left:0;width:100%;height:100%;border:0px;border-radius:25pt"></iframe></div>
+<h2 class="anchor anchorTargetStickyNavbar_CXV1" id="protocol-discussion">Protocol Discussion<a href="https://developers.stellar.org/meetings/2026/01/22#protocol-discussion" class="hash-link" aria-label="Direct link to Protocol Discussion" title="Direct link to Protocol Discussion" translate="no">​</a></h2>
+<p>We had three CAPs prepared for this meeting. CAP-77 will provide a way to make ledger keys inaccessible based on the network configuration upgrade performed with a validator vote. CAP-78 proposes an interface which allows developers to specify TTL extension policies such as 'if an entry TTL is less than 29 days, extend it to have 30 days TTL'. CAP-79 introduces host functions for converting Stellar strkey format strings to/from Address/MuxedAddress objects.</p>
+<p>Read more about the proposals here:</p>
+<p><a href="https://github.com/stellar/stellar-protocol/blob/master/core/cap-0077.md" target="_blank" rel="noopener noreferrer" class="">CAP-77</a> - <a href="https://github.com/orgs/stellar/discussions/1811" target="_blank" rel="noopener noreferrer" class="">Discussion</a></p>
+<p><a href="https://github.com/stellar/stellar-protocol/blob/master/core/cap-0078.md" target="_blank" rel="noopener noreferrer" class="">CAP-78</a> - <a href="https://github.com/orgs/stellar/discussions/1825" target="_blank" rel="noopener noreferrer" class="">Discussion</a></p>
+<p><a href="https://github.com/stellar/stellar-protocol/blob/master/core/cap-0079.md" target="_blank" rel="noopener noreferrer" class="">CAP-79</a> - <a href="https://github.com/orgs/stellar/discussions/1840" target="_blank" rel="noopener noreferrer" class="">Discussion</a></p>]]></content>
+        <author>
+            <name>Carsten Jacobsen</name>
+            <uri>https://github.com/carstenjacobsen</uri>
+        </author>
+        <category label="developer" term="developer"/>
+    </entry>
+    <entry>
+        <title type="html"><![CDATA[2025-11-06]]></title>
+        <id>https://developers.stellar.org/meetings/2025/11/06</id>
+        <link href="https://developers.stellar.org/meetings/2025/11/06"/>
+        <updated>2025-11-06T00:00:00.000Z</updated>
+        <summary type="html"><![CDATA[In this meeting we do a walkthrough of OpenZeppelin’s Q3 library releases for Smart Account, Vault and RWA.]]></summary>
+        <content type="html"><![CDATA[<div class="youtubeEmbed" style="position:relative;width:100%;padding-bottom:56.25%;height:0;margin-bottom:23px"><iframe src="https://www.youtube-nocookie.com/embed/-T3Ia32nnP0?rel=0&amp;modestbranding=1" title="Informational explainer" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" style="position:absolute;top:0;left:0;width:100%;height:100%;border:0px;border-radius:25pt"></iframe></div>
+<p>In this meeting we do a walkthrough of OpenZeppelin’s Q3 library releases for Smart Account, Vault and RWA.</p>
+<p>Links to docs:</p>
+<ul>
+<li class="">Smart Account: <a href="https://docs.openzeppelin.com/stellar-contracts/accounts/smart-account" target="_blank" rel="noopener noreferrer" class="">https://docs.openzeppelin.com/stellar-contracts/accounts/smart-account</a></li>
+<li class="">Vault: <a href="https://docs.openzeppelin.com/stellar-contracts/tokens/vault/vault" target="_blank" rel="noopener noreferrer" class="">https://docs.openzeppelin.com/stellar-contracts/tokens/vault/vault</a></li>
+<li class="">RWA: <a href="https://docs.openzeppelin.com/stellar-contracts/tokens/rwa/rwa" target="_blank" rel="noopener noreferrer" class="">https://docs.openzeppelin.com/stellar-contracts/tokens/rwa/rwa</a></li>
+</ul>]]></content>
+        <author>
+            <name>Carsten Jacobsen</name>
+            <uri>https://github.com/carstenjacobsen</uri>
+        </author>
+        <category label="developer" term="developer"/>
+    </entry>
+    <entry>
+        <title type="html"><![CDATA[2025-10-30]]></title>
+        <id>https://developers.stellar.org/meetings/2025/10/30</id>
+        <link href="https://developers.stellar.org/meetings/2025/10/30"/>
+        <updated>2025-10-30T00:00:00.000Z</updated>
+        <summary type="html"><![CDATA[In this meeting we are continuing our mini series about the Stellar-based open source tooling OpenZeppelin is developing. In the last session we talked briefly about Relayer and this time we are diving deeper into this tool, and OpenZeppelin Managed Service.]]></summary>
+        <content type="html"><![CDATA[<div class="youtubeEmbed" style="position:relative;width:100%;padding-bottom:56.25%;height:0;margin-bottom:23px"><iframe src="https://www.youtube-nocookie.com/embed/nxU16dOjN3M?rel=0&amp;modestbranding=1" title="Informational explainer" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" style="position:absolute;top:0;left:0;width:100%;height:100%;border:0px;border-radius:25pt"></iframe></div>
+<p>In this meeting we are continuing our mini series about the Stellar-based open source tooling OpenZeppelin is developing. In the last session we talked briefly about Relayer and this time we are diving deeper into this tool, and OpenZeppelin Managed Service.</p>
+<p>OpenZeppelin Relayer: <a href="https://docs.openzeppelin.com/relayer" target="_blank" rel="noopener noreferrer" class="">https://docs.openzeppelin.com/relayer</a></p>]]></content>
+        <author>
+            <name>Carsten Jacobsen</name>
+            <uri>https://github.com/carstenjacobsen</uri>
+        </author>
+        <category label="developer" term="developer"/>
+    </entry>
+</feed>
\ No newline at end of file
diff --git a/meetings/authors.yml b/meetings/authors.yml
deleted file mode 100644
index 9d92d724b..000000000
--- a/meetings/authors.yml
+++ /dev/null
@@ -1,58 +0,0 @@
-carstenjacobsen:
-  name: Carsten Jacobsen
-  title: Senior Developer Advocate
-  url: https://github.com/carstenjacobsen
-  image_url: https://github.com/carstenjacobsen.png
-  page: true
-  socials:
-    github: carstenjacobsen
-    x: CarstenJacobsen
-    linkedin: carstenjacobsendk
-elliotfriend:
-  name: Elliot Voris
-  title: Senior Developer Advocate
-  url: https://github.com/ElliotFriend
-  image_url: https://github.com/ElliotFriend.png
-  page: true
-  socials:
-    github: ElliotFriend
-    x: ElliotFriend
-    linkedin: elliotfriend
-kalepail:
-  name: Tyler van der Hoeven
-  title: Developer Advocate Director
-  url: https://github.com/kalepail
-  image_url: https://github.com/kalepail.png
-  page: true
-  socials:
-    github: kalepail
-    x: kalepail
-    linkedin: tyvdh
-anataliocs:
-  name: Chris Anatalio
-  title: Senior Developer Advocate
-  url: https://github.com/anataliocs
-  image_url: https://github.com/anataliocs.png
-  socials:
-    github: anataliocs
-naman:
-  name: Naman Kumar
-  title: Product Manager
-  url: https://github.com/namankumar
-  image_url: https://github.com/namankumar.png
-  socials:
-    github: namankumar
-julian:
-  name: Julian Martinez
-  title: Senior Developer Advocate
-  url: https://github.com/Julian-dev28
-  image_url: https://github.com/Julian-dev28.png
-  socials:
-    github: Julian-dev28
-kaankacar:
-  name: Kaan Kacar
-  title: Developer Advocate
-  url: https://github.com/kaankacar
-  image_url: https://github.com/kaankacar.png
-  socials:
-    github: kaankacar
diff --git a/meetings/index.mdx b/meetings/index.mdx
new file mode 100644
index 000000000..0373d9b07
--- /dev/null
+++ b/meetings/index.mdx
@@ -0,0 +1,721 @@
+---
+title: Meeting Notes
+description: "Notes and recordings from the Stellar protocol & developers meetings"
+rss: true
+---
+
+<Update label="2026-10-08" tags={["2026"]} rss={{ date: "2026-10-08" }}>
+
+Last week I built a USDT0 demo and walked through how the LayerZero infrastructure works on Stellar (2026-10-01).
+
+[Read the meeting notes](/meetings/2026/10/08)
+
+</Update>
+
+<Update label="2026-10-01" tags={["2026"]} rss={{ date: "2026-10-01" }}>
+
+October is the month of Hack Meridian and the Meridian conference, which is exactly why I refused to spend the call talking about either of them (mostly —...
+
+[Read the meeting notes](/meetings/2026/10/01)
+
+</Update>
+
+<Update label="2026-09-24" tags={["2026"]} rss={{ date: "2026-09-24" }}>
+
+This week kicked off a live stream series that runs all the way to Meridian, our flagship conference, and Hack Meridian, the hackathon that happens right...
+
+[Read the meeting notes](/meetings/2026/09/24)
+
+</Update>
+
+<Update label="2026-09-17 Protocol Discussion" tags={["2026"]} rss={{ date: "2026-09-17" }}>
+
+After the Stellar Private Payments AMA, Jay Geng from the core team presented CAP-87.
+
+[Read the meeting notes](/meetings/2026/09/17/protocol)
+
+</Update>
+
+<Update label="2026-09-17" tags={["2026"]} rss={{ date: "2026-09-17" }}>
+
+This week was a straight-up AMA about Stellar Private Payments (SPP), Nethermind's privacy-pool implementation for Stellar.
+
+[Read the meeting notes](/meetings/2026/09/17)
+
+</Update>
+
+<Update label="2026-09-10" tags={["2026"]} rss={{ date: "2026-09-10" }}>
+
+This week was planned as a protocol discussion on CAP-87 and CAP-88, with Jay Geng and Garand Tyson from the core team.
+
+[Read the meeting notes](/meetings/2026/09/10)
+
+</Update>
+
+<Update label="2026-09-03" tags={["2026"]} rss={{ date: "2026-09-03" }}>
+
+I showed up in a black jacket this week, like a serious businessman here to discuss confidential tokens and privacy.
+
+[Read the meeting notes](/meetings/2026/09/03)
+
+</Update>
+
+<Update label="2026-08-27" tags={["2026"]} rss={{ date: "2026-08-27" }}>
+
+Moonlight, a compliant privacy layer on Stellar built on UTXOs, with Chad Ostrowski and Gorka of The Aha Company. Plus Protocol 28 and private payments news.
+
+[Read the meeting notes](/meetings/2026/08/27)
+
+</Update>
+
+<Update label="2026-08-20" tags={["2026"]} rss={{ date: "2026-08-20" }}>
+
+This week was a coding session rather than a project spotlight: six wallet infrastructures, one demo app, and a running list of gotchas for each.
+
+[Read the meeting notes](/meetings/2026/08/20)
+
+</Update>
+
+<Update label="2026-08-13" tags={["2026"]} rss={{ date: "2026-08-13" }}>
+
+This week's meeting was a short one, because it had exactly one job: announcing the 12 winners across 6 tracks from last week's Stellar Builder Summit in...
+
+[Read the meeting notes](/meetings/2026/08/13)
+
+</Update>
+
+<Update label="2026-08-06" tags={["2026"]} rss={{ date: "2026-08-06" }}>
+
+This week we streamed from Brazil, where the team is camped out for Stellar House — if you're around, come on down.
+
+[Read the meeting notes](/meetings/2026/08/06)
+
+</Update>
+
+<Update label="2026-07-30" tags={["2026"]} rss={{ date: "2026-07-30" }}>
+
+The twist this week: I wasn't the only developer advocate on the stream.
+
+[Read the meeting notes](/meetings/2026/07/30)
+
+</Update>
+
+<Update label="2026-07-23" tags={["2026"]} rss={{ date: "2026-07-23" }}>
+
+Before the guests, some news from the developer ecosystem — starting with a sentence I haven't been able to say for a while: Stellar Quest is live again.
+
+[Read the meeting notes](/meetings/2026/07/23)
+
+</Update>
+
+<Update label="2026-07-16 Protocol Discussion" tags={["2026"]} rss={{ date: "2026-07-16" }}>
+
+This week's protocol discussion had two parts.
+
+[Read the meeting notes](/meetings/2026/07/16/protocol)
+
+</Update>
+
+<Update label="2026-07-16" tags={["2026"]} rss={{ date: "2026-07-16" }}>
+
+Probably my favorite Stellar Developers meeting so far, and — unusually for me — I spent most of it not talking.
+
+[Read the meeting notes](/meetings/2026/07/16)
+
+</Update>
+
+<Update label="2026-07-09" tags={["2026"]} rss={{ date: "2026-07-09" }}>
+
+This week was a protocol discussion.
+
+[Read the meeting notes](/meetings/2026/07/09)
+
+</Update>
+
+<Update label="2026-07-02" tags={["2026"]} rss={{ date: "2026-07-02" }}>
+
+This week wasn't about AI — it was about your second-favorite subject: privacy.
+
+[Read the meeting notes](/meetings/2026/07/02)
+
+</Update>
+
+<Update label="2026-06-25" tags={["2026"]} rss={{ date: "2026-06-25" }}>
+
+Before the guests, a quick bit of ecosystem context for why this week felt busy.
+
+[Read the meeting notes](/meetings/2026/06/25)
+
+</Update>
+
+<Update label="2026-06-18" tags={["2026"]} rss={{ date: "2026-06-18" }}>
+
+This week was a doozy — not just one exciting guest, but a pile of news and a stack of tools to use and maybe break.
+
+[Read the meeting notes](/meetings/2026/06/18)
+
+</Update>
+
+<Update label="2026-06-11" tags={["2026"]} rss={{ date: "2026-06-11" }}>
+
+We skipped a week — the DevRel team was in Istanbul for the hackathon we threw during Istanbul Blockchain Week, and the side event at the end gathered more...
+
+[Read the meeting notes](/meetings/2026/06/11)
+
+</Update>
+
+<Update label="2026-05-21" tags={["2026"]} rss={{ date: "2026-05-21" }}>
+
+This week splits in half again.
+
+[Read the meeting notes](/meetings/2026/05/21)
+
+</Update>
+
+<Update label="2026-05-14" tags={["2026"]} rss={{ date: "2026-05-14" }}>
+
+This week's meeting splits cleanly in half.
+
+[Read the meeting notes](/meetings/2026/05/14)
+
+</Update>
+
+<Update label="2026-05-07" tags={["2026"]} rss={{ date: "2026-05-07" }}>
+
+This week's meeting is a hands-on walkthrough of the Machine Payments Protocol (MPP) on Stellar — what it is, when to reach for it, and the specific moment...
+
+[Read the meeting notes](/meetings/2026/05/07)
+
+</Update>
+
+<Update label="2026-04-30" tags={["2026"]} rss={{ date: "2026-04-30" }}>
+
+This protocol meeting covered two related authorization changes coming in Protocol 27, presented by Dmytro Kozhevin: a recap of CAP-71's authentication...
+
+[Read the meeting notes](/meetings/2026/04/30)
+
+</Update>
+
+<Update label="2026-04-23" tags={["2026"]} rss={{ date: "2026-04-23" }}>
+
+Messari published their State of Stellar Q1 2026 report ahead of this meeting, and there are numbers in it that every developer building on Stellar should...
+
+[Read the meeting notes](/meetings/2026/04/23)
+
+</Update>
+
+<Update label="2026-04-16" tags={["2026"]} rss={{ date: "2026-04-16" }}>
+
+Protocol 26, codenamed Yardstick, went live on testnet on April 16, 2026 at 17:00 UTC — literally the day of this meeting.
+
+[Read the meeting notes](/meetings/2026/04/16)
+
+</Update>
+
+<Update label="2026-02-26" tags={["2026"]} rss={{ date: "2026-02-26" }}>
+
+In this protocol meeting we had two CAPs to discuss and that was CAP-81 and CAP-82.
+
+[Read the meeting notes](/meetings/2026/02/26)
+
+</Update>
+
+<Update label="2026-01-29" tags={["2026"]} rss={{ date: "2026-01-29" }}>
+
+We have one new CAP to discuss and that is CAP-80.
+
+[Read the meeting notes](/meetings/2026/01/29)
+
+</Update>
+
+<Update label="2026-01-22" tags={["2026"]} rss={{ date: "2026-01-22" }}>
+
+In this year’s first Stellar Developer Meeting, on Thursday, January 22nd at 8am PT on Twitch, we will catch up with Ozgun and Boyan from the OpenZeppelin...
+
+[Read the meeting notes](/meetings/2026/01/22)
+
+</Update>
+
+<Update label="2025-11-06" tags={["2025"]} rss={{ date: "2025-11-06" }}>
+
+In this meeting we do a walkthrough of OpenZeppelin’s Q3 library releases for Smart Account, Vault and RWA.
+
+[Read the meeting notes](/meetings/2025/11/06)
+
+</Update>
+
+<Update label="2025-10-30" tags={["2025"]} rss={{ date: "2025-10-30" }}>
+
+In this meeting we are continuing our mini series about the Stellar-based open source tooling OpenZeppelin is developing.
+
+[Read the meeting notes](/meetings/2025/10/30)
+
+</Update>
+
+<Update label="2025-10-23" tags={["2025"]} rss={{ date: "2025-10-23" }}>
+
+In this meeting we are talking to Dobprotocol to learn more about how they use Stellar to build a unique platform, turning machines into investable assets.
+
+[Read the meeting notes](/meetings/2025/10/23)
+
+</Update>
+
+<Update label="2025-10-16" tags={["2025"]} rss={{ date: "2025-10-16" }}>
+
+In this call the recent state archival issue, introduced by Whisk (Protocol 23), is discussed.
+
+[Read the meeting notes](/meetings/2025/10/16)
+
+</Update>
+
+<Update label="2025-10-09" tags={["2025"]} rss={{ date: "2025-10-09" }}>
+
+We are meeting with the OpenZeppelin team again to catch up on the latest developer tooling work they are doing.
+
+[Read the meeting notes](/meetings/2025/10/09)
+
+</Update>
+
+<Update label="2025-10-02" tags={["2025"]} rss={{ date: "2025-10-02" }}>
+
+In this meeting we will discuss CAP-74, BN254 and Poseidon hash functions.
+
+[Read the meeting notes](/meetings/2025/10/02)
+
+</Update>
+
+<Update label="2025-09-25" tags={["2025"]} rss={{ date: "2025-09-25" }}>
+
+In this week’s Stellar Developer Meeting we discuss new Core Advancement Proposals.
+
+[Read the meeting notes](/meetings/2025/09/25)
+
+</Update>
+
+<Update label="2025-08-07" tags={["2025"]} rss={{ date: "2025-08-07" }}>
+
+In this meeting we talk to Flashback founder Brieuc Berruet, who participated in the DraperU x Stellar incubator program last year, to get an update on his...
+
+[Read the meeting notes](/meetings/2025/08/07)
+
+</Update>
+
+<Update label="2025-07-24" tags={["2025"]} rss={{ date: "2025-07-24" }}>
+
+In this meeting we are talking to Esteban and Francisco from PaltaLabs.
+
+[Read the meeting notes](/meetings/2025/07/24)
+
+</Update>
+
+<Update label="2025-07-17" tags={["2025"]} rss={{ date: "2025-07-17" }}>
+
+In this meeting the Nomyx team will give us an introduction to their advanced smart contract architecture (an implementation of the Diamond Pattern) and the...
+
+[Read the meeting notes](/meetings/2025/07/17)
+
+</Update>
+
+<Update label="2025-07-10" tags={["2025"]} rss={{ date: "2025-07-10" }}>
+
+In this call we are getting an update on the exciting Scaffold Stellar project by Fifo from Aha Labs.
+
+[Read the meeting notes](/meetings/2025/07/10)
+
+</Update>
+
+<Update label="2025-05-22" tags={["2025"]} rss={{ date: "2025-05-22" }}>
+
+At this Stellar Developer Meeting we are having a chat with Bram Hoogenkamp from OpenZeppelin about the OpenZeppelin Monitor - providing monitoring and...
+
+[Read the meeting notes](/meetings/2025/05/22)
+
+</Update>
+
+<Update label="2025-05-01" tags={["2025"]} rss={{ date: "2025-05-01" }}>
+
+We are close to completing the implementation of Whisk, Protocol 23 CAPs, the next step in the CAP lifecycle is voting by the Core CAP team.
+
+[Read the meeting notes](/meetings/2025/05/01)
+
+</Update>
+
+<Update label="2025-04-17" tags={["2025"]} rss={{ date: "2025-04-17" }}>
+
+This week we’ll dive into one of the most overlooked tools - Quickstart.
+
+[Read the meeting notes](/meetings/2025/04/17)
+
+</Update>
+
+<Update label="2025-04-10" tags={["2025"]} rss={{ date: "2025-04-10" }}>
+
+Pamphile (better know as tupui) is a senior software engineer working at Bitpanda.
+
+[Read the meeting notes](/meetings/2025/04/10)
+
+</Update>
+
+<Update label="2025-04-03" tags={["2025"]} rss={{ date: "2025-04-03" }}>
+
+First we take a look at look at Stellar Lab, a lot of features and improvements have been added since we did a Stellar Lab presentation last year.
+
+[Read the meeting notes](/meetings/2025/04/03)
+
+</Update>
+
+<Update label="2025-03-27" tags={["2025"]} rss={{ date: "2025-03-27" }}>
+
+We are meeting with the OpenZeppelin team again to catch up on the latest feature additions, and this time we have invited two of their engineers, Boyan...
+
+[Read the meeting notes](/meetings/2025/03/27)
+
+</Update>
+
+<Update label="2025-03-06" tags={["2025"]} rss={{ date: "2025-03-06" }}>
+
+In this meeting we have a conversation with Christian Santagata from OpenZeppelin about the Stellar x OpenZeppelin multi-year partnership, and talk about...
+
+[Read the meeting notes](/meetings/2025/03/06)
+
+</Update>
+
+<Update label="2025-02-27" tags={["2025"]} rss={{ date: "2025-02-27" }}>
+
+Blend, a universal liquidity protocol build on Stellar/Soroban, is preparing to release V2 and launched the Blend V2 Audit + Certora Formal Verification...
+
+[Read the meeting notes](/meetings/2025/02/27)
+
+</Update>
+
+<Update label="2025-02-20" tags={["2025"]} rss={{ date: "2025-02-20" }}>
+
+SDF Developer Advocate Elliot Voris gives an introduction to the KaleFail project, and cover how it was built, the purpose and future features.
+
+[Read the meeting notes](/meetings/2025/02/20)
+
+</Update>
+
+<Update label="2025-02-13" tags={["2025"]} rss={{ date: "2025-02-13" }}>
+
+OrbitLens will showcase StellarBroker and StellarExpert services.
+
+[Read the meeting notes](/meetings/2025/02/13)
+
+</Update>
+
+<Update label="2025-02-06" tags={["2025"]} rss={{ date: "2025-02-06" }}>
+
+The dev team behind Reflector and Refractor presents their tools for decentralized finance and transaction management on Stellar.
+
+[Read the meeting notes](/meetings/2025/02/06)
+
+</Update>
+
+<Update label="2025-01-30" tags={["2025"]} rss={{ date: "2025-01-30" }}>
+
+RampMeDaddy will be joining us for this Stellar Developer Meeting.
+
+[Read the meeting notes](/meetings/2025/01/30)
+
+</Update>
+
+<Update label="2025-01-23" tags={["2025"]} rss={{ date: "2025-01-23" }}>
+
+In this week's meeting Hoops Finance's founders Bastian and Tim talk about the progress they have made, some design considerations and the future of Hoops...
+
+[Read the meeting notes](/meetings/2025/01/23)
+
+</Update>
+
+<Update label="2025-01-16" tags={["2025"]} rss={{ date: "2025-01-16" }}>
+
+Stellar Development Foundation's Ecosystem DevRel team got together to talk about the past year, and what 2025 brings.
+
+[Read the meeting notes](/meetings/2025/01/16)
+
+</Update>
+
+<Update label="2024-12-19" tags={["2024"]} rss={{ date: "2024-12-19" }}>
+
+In this meeting SDF Core Software Engineer Jay talks about BLS building blocks, and walks through examples and demos.
+
+[Read the meeting notes](/meetings/2024/12/19)
+
+</Update>
+
+<Update label="2024-12-12" tags={["2024"]} rss={{ date: "2024-12-12" }}>
+
+In this meeting, SDF Developer Advocate Chris Anatalio talks about the future stack, including smart contract wallets and Passkeys.
+
+[Read the meeting notes](/meetings/2024/12/12)
+
+</Update>
+
+<Update label="2024-12-05" tags={["2024"]} rss={{ date: "2024-12-05" }}>
+
+In this week's call we talk to Alberto Chaves from Trustless Work about building an escrow service on Stellar, followed by a quick introduction to using...
+
+[Read the meeting notes](/meetings/2024/12/05)
+
+</Update>
+
+<Update label="2024-11-14" tags={["2024"]} rss={{ date: "2024-11-14" }}>
+
+Agenda: Discord thread
+
+[Read the meeting notes](/meetings/2024/11/14)
+
+</Update>
+
+<Update label="2024-10-24" tags={["2024"]} rss={{ date: "2024-10-24" }}>
+
+Agenda: Discord thread
+
+[Read the meeting notes](/meetings/2024/10/24)
+
+</Update>
+
+<Update label="2024-09-26" tags={["2024"]} rss={{ date: "2024-09-26" }}>
+
+Agenda: Discord thread
+
+[Read the meeting notes](/meetings/2024/09/26)
+
+</Update>
+
+<Update label="2024-09-19" tags={["2024"]} rss={{ date: "2024-09-19" }}>
+
+Agenda: Discord thread
+
+[Read the meeting notes](/meetings/2024/09/19)
+
+</Update>
+
+<Update label="2024-09-12" tags={["2024"]} rss={{ date: "2024-09-12" }}>
+
+Agenda: Discord thread
+
+[Read the meeting notes](/meetings/2024/09/12)
+
+</Update>
+
+<Update label="2024-09-05" tags={["2024"]} rss={{ date: "2024-09-05" }}>
+
+Agenda: Discord thread
+
+[Read the meeting notes](/meetings/2024/09/05)
+
+</Update>
+
+<Update label="2024-08-29" tags={["2024"]} rss={{ date: "2024-08-29" }}>
+
+Agenda: Discord thread
+
+[Read the meeting notes](/meetings/2024/08/29)
+
+</Update>
+
+<Update label="2024-08-23" tags={["2024"]} rss={{ date: "2024-08-23" }}>
+
+Discord agenda thread
+
+[Read the meeting notes](/meetings/2024/08/22)
+
+</Update>
+
+<Update label="2024-08-15" tags={["2024"]} rss={{ date: "2024-08-15" }}>
+
+Note: The hosts microphone audio is not in the video so there is some silence during Q/A.
+
+[Read the meeting notes](/meetings/2024/08/15)
+
+</Update>
+
+<Update label="2024-08-12" tags={["2024"]} rss={{ date: "2024-08-12" }}>
+
+[Read the meeting notes](/meetings/2024/08/08)
+
+</Update>
+
+<Update label="2024-08-01" tags={["2024"]} rss={{ date: "2024-08-01" }}>
+
+[Read the meeting notes](/meetings/2024/08/01)
+
+</Update>
+
+<Update label="2024-07-25" tags={["2024"]} rss={{ date: "2024-07-25" }}>
+
+A Core Dev, Dima, discussed the proposal to add constructor support to Soroban, Stellar's smart contract system.
+
+[Read the meeting notes](/meetings/2024/07/25)
+
+</Update>
+
+<Update label="2024-07-18" tags={["2024"]} rss={{ date: "2024-07-18" }}>
+
+Note: the first part of the call was lost.
+
+[Read the meeting notes](/meetings/2024/07/18)
+
+</Update>
+
+<Update label="2024-07-11" tags={["2024"]} rss={{ date: "2024-07-11" }}>
+
+[Read the meeting notes](/meetings/2024/07/11)
+
+</Update>
+
+<Update label="2024-06-27" tags={["2024"]} rss={{ date: "2024-06-27" }}>
+
+[Read the meeting notes](/meetings/2024/06/27)
+
+</Update>
+
+<Update label="2024-06-20" tags={["2024"]} rss={{ date: "2024-06-20" }}>
+
+Follow Meru on X (formerly Twitter) to stay updated: https://x.com/getmeru
+
+[Read the meeting notes](/meetings/2024/06/20)
+
+</Update>
+
+<Update label="2024-06-13" tags={["2024"]} rss={{ date: "2024-06-13" }}>
+
+Join the #passkeys channel on the Discord to continue the discussion
+
+[Read the meeting notes](/meetings/2024/06/13)
+
+</Update>
+
+<Update label="2024-05-09" tags={["2024"]} rss={{ date: "2024-05-09" }}>
+
+[Read the meeting notes](/meetings/2024/05/09)
+
+</Update>
+
+<Update label="2024-05-02" tags={["2024"]} rss={{ date: "2024-05-02" }}>
+
+Discord Agenda thread
+
+[Read the meeting notes](/meetings/2024/05/02)
+
+</Update>
+
+<Update label="2024-04-25" tags={["2024"]} rss={{ date: "2024-04-25" }}>
+
+[Read the meeting notes](/meetings/2024/04/25)
+
+</Update>
+
+<Update label="2024-04-18" tags={["2024"]} rss={{ date: "2024-04-18" }}>
+
+Discord agenda thread
+
+[Read the meeting notes](/meetings/2024/04/18)
+
+</Update>
+
+<Update label="2024-04-11" tags={["2024"]} rss={{ date: "2024-04-11" }}>
+
+Piyal from Freighter discussed the proposal to standardize the wallet interface.
+
+[Read the meeting notes](/meetings/2024/04/11)
+
+</Update>
+
+<Update label="2024-04-04" tags={["2024"]} rss={{ date: "2024-04-04" }}>
+
+Today's recording has two parts.
+
+[Read the meeting notes](/meetings/2024/04/04)
+
+</Update>
+
+<Update label="2024-03-28" tags={["2024"]} rss={{ date: "2024-03-28" }}>
+
+Agenda thread
+
+[Read the meeting notes](/meetings/2024/03/28)
+
+</Update>
+
+<Update label="2024-03-21" tags={["2024"]} rss={{ date: "2024-03-21" }}>
+
+Discord agenda thread
+
+[Read the meeting notes](/meetings/2024/03/21)
+
+</Update>
+
+<Update label="2024-03-14" tags={["2024"]} rss={{ date: "2024-03-14" }}>
+
+Discord agenda thread
+
+[Read the meeting notes](/meetings/2024/03/14)
+
+</Update>
+
+<Update label="2024-03-07" tags={["2024"]} rss={{ date: "2024-03-07" }}>
+
+Discord agenda thread
+
+[Read the meeting notes](/meetings/2024/03/07)
+
+</Update>
+
+<Update label="2024-02-29" tags={["2024"]} rss={{ date: "2024-02-29" }}>
+
+Discord agenda thread
+
+[Read the meeting notes](/meetings/2024/02/29)
+
+</Update>
+
+<Update label="2024-02-22" tags={["2024"]} rss={{ date: "2024-02-22" }}>
+
+Discord agenda thread
+
+[Read the meeting notes](/meetings/2024/02/22)
+
+</Update>
+
+<Update label="2024-02-15" tags={["2024"]} rss={{ date: "2024-02-15" }}>
+
+Discord agenda thread
+
+[Read the meeting notes](/meetings/2024/02/15)
+
+</Update>
+
+<Update label="2024-02-08" tags={["2024"]} rss={{ date: "2024-02-08" }}>
+
+Discord agenda thread
+
+[Read the meeting notes](/meetings/2024/02/08)
+
+</Update>
+
+<Update label="2024-02-01" tags={["2024"]} rss={{ date: "2024-02-01" }}>
+
+Discord agenda thread
+
+[Read the meeting notes](/meetings/2024/02/01)
+
+</Update>
+
+<Update label="2024-01-26" tags={["2024"]} rss={{ date: "2024-01-26" }}>
+
+Discord agenda thread
+
+[Read the meeting notes](/meetings/2024/01/26)
+
+</Update>
+
+<Update label="2024-01-18" tags={["2024"]} rss={{ date: "2024-01-18" }}>
+
+Discord agenda thread
+
+[Read the meeting notes](/meetings/2024/01/18)
+
+</Update>
diff --git a/nginx/includes/redirects.conf b/nginx/includes/redirects.conf
deleted file mode 100644
index be34dbe95..000000000
--- a/nginx/includes/redirects.conf
+++ /dev/null
@@ -1,308 +0,0 @@
-## NGINX redirects file. Write carefully; syntax must be precise. Regular
-## expressions containing curly braces "{}" must be enclosed in double quotes.
-
-# Main primitives
-rewrite ^/docs/(learn/)?glossary/accounts$ "/docs/learn/fundamentals/stellar-data-structures/accounts" permanent;
-rewrite ^/docs/(learn/)?glossary/assets$ "/docs/learn/fundamentals/stellar-data-structures/assets" permanent;
-rewrite ^/docs/(learn/)?glossary/channels$ "/docs/learn/encyclopedia/transactions-specialized/channel-accounts" permanent;
-rewrite ^/docs/(learn/)?glossary/claimable-balance$ "/docs/learn/encyclopedia/transactions-specialized/claimable-balances" permanent;
-rewrite ^/docs/(learn/)?glossary/clawback$ "/docs/learn/encyclopedia/transactions-specialized/clawbacks" permanent;
-rewrite ^/docs/(learn/)?glossary/decentralized-exchange$ "/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools#sdex" permanent;
-rewrite ^/docs/(learn/)?glossary/federation$ "/docs/learn/encyclopedia/network-configurationfederation" permanent;
-rewrite ^/docs/(learn/)?glossary/fee-bumps$ "/docs/learn/encyclopedia/transactions-specialized/fee-bump-transactions" permanent;
-rewrite ^/docs/(learn/)?glossary/fees$ "/docs/learn/fundamentals/fees-resource-limits-metering" permanent;
-rewrite ^/docs/(learn/)?encyclopedia/fees-surge-pricing-fee-strategies$ "/docs/learn/fundamentals/fees-resource-limits-metering" permanent;
-rewrite ^/docs/(learn/)?glossary/inflation$ "/docs/learn/encyclopedia/network-configuration/inflation" permanent;
-rewrite ^/docs/(learn/)?glossary/ledger$ "/docs/learn/fundamentals/stellar-data-structures/ledgers" permanent;
-rewrite ^/docs/(learn/)?glossary/liquidity-pools$ "/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools#liquidity-pools" permanent;
-rewrite ^/docs/(learn/)?encyclopedia/liquidity-on-stellar-sdex-and-liquidity-pools(.*)$ "/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools" permanent;
-rewrite ^/docs/(learn/)?glossary/lumen-supply$ "/docs/learn/fundamentals/lumens#lumen-supply-metrics" permanent;
-rewrite ^/docs/(learn/)?glossary/minimum-balance$ "/docs/learn/fundamentals/lumens#minimum-balance" permanent;
-rewrite ^/docs/(learn/)?glossary/multisig$ "/docs/learn/fundamentals/transactions/signatures-multisig" permanent;
-rewrite ^/docs/(learn/)?glossary/muxed-accounts$ "/docs/learn/encyclopedia/transactions-specialized/pooled-accounts-muxed-accounts-memos" permanent;
-rewrite ^/docs/(learn/)?glossary/network-passphrase$ "/docs/learn/encyclopedia/network-configuration/network-passphrases" permanent;
-rewrite ^/docs/(learn/)?glossary/operations$ "/docs/learn/fundamentals/stellar-data-structures/operations-and-transactions#operations" permanent;
-rewrite ^/docs/(learn/)?glossary/scp$ "/docs/learn/fundamentals/stellar-consensus-protocol" permanent;
-rewrite ^/docs/(learn/)?glossary/sponsored-reserves$ "/docs/learn/encyclopedia/transactions-specialized/sponsored-reserves" permanent;
-rewrite ^/docs/(learn/)?glossary/testnet$ "/docs/learn/fundamentals/networks" permanent;
-rewrite ^/docs/(learn/)?glossary/transactions$ "/docs/learn/fundamentals/stellar-data-structures/operations-and-transactions" permanent;
-rewrite ^/docs/glossary/xdr$ "/docs/learn/encyclopedia/data-format/xdr" permanent;
-rewrite ^/docs/tools/sdks/library$ "/docs/tools/sdks" permanent;
-rewrite ^/docs/software-and-sdks$ "/docs/tools/sdks" permanent;
-rewrite ^/docs/tools-and-sdks(.*)$ "/docs/tools/sdks$1" permanent;
-rewrite ^/docs/data/indexers/data-indexers$ "/docs/data/indexers/indexer-providers" permanent;
-rewrite ^/docs/tools/developer-tools/data-indexers "/docs/data/indexers/data-indexers" permanent;
-rewrite ^/docs/data/indexers/indexer-providers(/indexer-providers)?$ "/docs/data/indexers" permanent;
-rewrite ^/docs/start/introduction$ "/docs" permanent;
-rewrite ^/docs/start/list-of-operations$ "/docs/learn/fundamentals/list-of-operations" permanent;
-rewrite ^/docs/start/stellar-stack$ "/docs/learn/fundamentals/stellar-stack" permanent;
-rewrite ^/docs/tutorials/handling-errors$ "/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging-errors" permanent;
-rewrite ^/docs/tutorials/securing-projects$ "/docs/build/security-docs/securing-web-based-projects" permanent;
-rewrite ^/docs/tutorials/moneygram-access-integration-guide$ "/docs/build/apps/moneygram-access-integration-guide" permanent;
-rewrite ^/docs/fundamentals-and-concepts/testnet-and-pubnet$ "/docs/learn/fundamentals/networks" permanent;
-rewrite ^/api$ "/docs/data/apis/horizon" permanent;
-rewrite ^/docs/build/smart-contracts/example-contracts/custom-account$ "/docs/build/smart-contracts/example-contracts/complex-account" permanent;
-
-# Moving /api/* locations to /api/horizon (leaving /api intact for the "overview page")
-rewrite ^/(network|api)/(horizon/)?resources/((cb|get|list|retrieve|submit)-.*)$ "/docs/data/apis/horizon/api-reference/$3" permanent;
-rewrite ^/(network|api)/(horizon/)?resources/operations/object(.*)$ "/docs/data/apis/horizon/api-reference/resources/operations/object$3" permanent;
-rewrite ^/(network|api)/(horizon/)?(resources|aggregations)(.+)/object$ "/docs/data/apis/horizon/api-reference/$3$4/object" permanent;
-rewrite ^/(network|api|docs/data)/(horizon/)?(api-reference/)?aggregations/fee-stats/single(.*)$ "/docs/data/apis/horizon/api-reference/retrieve-fee-stats$4" permanent;
-rewrite ^/(network|api|docs/data)/(horizon/)?(api-reference/)?aggregations/order-books/single(.*)$ "/docs/data/apis/horizon/api-reference/retrieve-an-order-book$4" permanent;
-rewrite ^/(network|api|docs/data)/(horizon/)?(api-reference/)?aggregations/paths/strict-receive(.*)$ "/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths$4" permanent;
-rewrite ^/(network|api|docs/data)/(horizon/)?(api-reference/)?aggregations/paths/strict-send(.*)$ "/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths$4" permanent;
-rewrite ^/(network|api|docs/data)/(horizon/)?(api-reference/)?aggregations/trade-aggregations/list(.*)$ "/docs/data/apis/horizon/api-reference/list-trade-aggregations$4" permanent;
-rewrite ^/docs/data/horizon/api-reference/resources/((cb|get|list|retrieve|submit)-.*)$ "/docs/data/apis/horizon/api-reference/$1" permanent;
-rewrite ^/api(/(?!horizon|(anchor|stellar-disbursement)-platform).*)$ "/docs/data/apis/horizon$1" permanent;
-rewrite ^/network/horizon/(resources|structure|aggregations|errors)(.*)$ "/docs/data/apis/horizon/api-reference/$1$2" permanent;
-rewrite ^/(network|api)/horizon(.*)$ "/docs/data/apis/horizon$2" permanent;
-rewrite ^/network/anchor-platform/(resources|callbacks|custody-server|rpc)(.*)$ "/docs/platforms/anchor-platform/api-reference/$1$2" permanent;
-rewrite ^/network/stellar-disbursement-platform/resources(.*)$ "/docs/platforms/stellar-disbursement-platform/api-reference$1" permanent;
-rewrite ^/(network|api)/((anchor|stellar-disbursement)-platform)(.*)$ "/docs/platforms/$2$4" permanent;
-rewrite ^/network/soroban-rpc/(methods|json-rpc|pagination)(.*)$ "/docs/data/apis/rpc/api-reference/$1$2" permanent;
-
-# Moving /ap_api locations to /api/anchor-platform
-rewrite ^/ap_api(.*)?$ "/docs/platforms/anchor-platform$1" permanent;
-rewrite ^/docs/category/anchor-platform$ "/docs/platforms/anchor-platform/admin-guide" permanent;
-rewrite ^/docs/anchoring-assets(/|/overview)?$ "/docs/learn/fundamentals/anchors" permanent;
-rewrite ^/docs/anchoring-assets(.*)$ "/docs/learn/fundamentals/anchors" permanent;
-rewrite ^/docs/category/use-the-stellar-disbursement-platform$ "/docs/platforms/stellar-disbursement-platform/admin-guide" permanent;
-rewrite ^/docs/stellar-disbursement-platform(.*)$ "/docs/platforms/stellar-disbursement-platform/admin-guide$1" permanent;
-rewrite ^/docs/run-api-server$ "/docs/data/apis/horizon/admin-guide/overview" permanent;
-rewrite ^/docs/run-api-server(.*)$ "/docs/data/apis/horizon/admin-guide$1" permanent;
-rewrite ^/docs/run-platform-server/?$ "/docs/data/apis/horizon/admin-guide/overview" permanent;
-rewrite ^/docs/run-platform-server(.*)$ "/docs/data/apis/horizon/admin-guide$1" permanent;
-rewrite ^/docs/run-core-node/?$ "/docs/validators" permanent;
-rewrite ^/docs/run-core-node/tier-1-orgs$ "/docs/validators/tier-1-orgs" permanent;
-rewrite ^/network/core-node/admin-guide/tier-1-orgs$ "/docs/validators/tier-1-orgs" permanent;
-rewrite ^/docs/run-core-node(.*)$ "/docs/validators/admin-guide$1" permanent;
-rewrite ^/docs/category/access(ing)?-historical-data$ "/docs/data/analytics/hubble" permanent;
-rewrite ^/docs/accessing-data/overview$ "/docs/data/analytics/hubble" permanent;
-rewrite ^/docs/accessing-data(.*)$ "/docs/data/analytics/hubble$1" permanent;
-rewrite ^/docs/fundamentals-and-concepts(.*)$ "/docs/learn/fundamentals" permanent;
-rewrite ^/docs/category/encyclopedia$ "/docs/learn/encyclopedia" permanent;
-rewrite ^/docs/encyclopedia(.*)$ "/docs/learn/encyclopedia$1" permanent;
-rewrite ^/docs/glossary(.*)$ "/docs/learn/glossary$1" permanent;
-
-# Miscellaneous redirects
-rewrite ^/docs/learn$ "/docs/learn/fundamentals" permanent;
-rewrite ^/docs/data/apis/horizon/api-reference/resources/retrieve-a-transaction$ "/docs/data/apis/horizon/api-reference/retrieve-a-transaction" permanent;
-rewrite ^/platforms/anchor-platform/api-reference/resources/get-transaction$ "/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transaction" permanent;
-rewrite ^/docs/learn/smart-contract-internals/fees-and-metering$ "/docs/learn/fundamentals/fees-resource-limits-metering" permanent;
-rewrite ^/docs/learn/migrate/introduction-to-solidity-and-rust$ "/docs/learn/migrate/evm/introduction-to-solidity-and-rust" permanent;
-rewrite ^/docs/learn/smart-contract-internals/state-expiration$ "/docs/learn/fundamentals/contract-development/storage/state-archival" permanent;
-rewrite ^/platforms/soroban-rpc/methods(.*)$ "/docs/data/apis/rpc/api-reference/methods$1" permanent;
-rewrite ^/network/soroban-rpc/getEvents$ "/docs/data/apis/rpc/api-reference/methods/getEvents" permanent;
-rewrite ^/docs/smart-contracts/example-contracts/stellar-asset-contract$ "/docs/tokens/stellar-asset-contract" permanent;
-rewrite ^/docs/smart-contracts/faq "/docs/build/smart-contracts/overview#soroban-faqs" permanent;
-rewrite ^/docs/learn/smart-contract-internals/faq "/docs/build/smart-contracts/overview#soroban-faqs" permanent;
-rewrite ^/docs/learn/smart-contract-internals/high-level-overview(.*)$ "/docs/learn/fundamentals/contract-development" permanent;
-rewrite ^/docs/smart-contracts/tokens/token-interface.mdx$ "/docs/tokens/token-interface" permanent;
-rewrite ^/network/anchor-platform/anchor$ "/docs/platforms/anchor-platform" permanent;
-rewrite ^/docs/examples/auth$ "/docs/build/smart-contracts/example-contracts/auth" permanent;
-rewrite ^/docs/reference$ "/docs/networks" permanent;
-rewrite ^/docs/reference/futurenet$ "/docs/networks" permanent;
-rewrite ^/docs/reference/(.*)$ "/docs/networks/$1" permanent;
-rewrite ^/docs/SDKs/rust-auth$ "/docs/tools/sdks/library#soroban-rust-sdk" permanent;
-rewrite ^/docs/category/cross-border-payments$ "/docs/platforms/anchor-platform/sep-guide/sep31" permanent;
-rewrite ^/docs/category/hosted-deposits-and-withdrawals$ "/docs/platforms/anchor-platform/sep-guide/sep24" permanent;
-rewrite ^/docs/category/programmatic-deposits-and-withdrawals$ "/docs/platforms/anchor-platform/sep-guide/sep6" permanent;
-rewrite ^/docs/category/stellar-authentication$ "/docs/platforms/anchor-platform/sep-guide/sep10" permanent;
-rewrite ^/docs/category/web-authentication-for-contracts$ "/docs/platforms/anchor-platform/sep-guide/sep45" permanent;
-rewrite ^/platforms/anchor-platform/admin-guide/sep1(.*)$ "/docs/platforms/anchor-platform/sep-guide/sep1$1" permanent;
-rewrite ^/platforms/anchor-platform/admin-guide/sep6(.*)$ "/docs/platforms/anchor-platform/sep-guide/sep6$1" permanent;
-rewrite ^/platforms/anchor-platform/admin-guide/sep10(.*)$ "/docs/platforms/anchor-platform/sep-guide/sep10$1" permanent;
-rewrite ^/platforms/anchor-platform/admin-guide/sep24(.*)$ "/docs/platforms/anchor-platform/sep-guide/sep24$1" permanent;
-rewrite ^/platforms/anchor-platform/admin-guide/sep31(.*)$ "/docs/platforms/anchor-platform/sep-guide/sep31$1" permanent;
-rewrite ^/platforms/anchor-platform/admin-guide/sep45(.*)$ "/docs/platforms/anchor-platform/sep-guide/sep45$1" permanent;
-rewrite ^/dapps "/docs/learn/interactive" permanent;
-rewrite ^/docs/learn/interactive/dapps "/docs/learn/interactive" permanent;
-rewrite ^/docs/learn/networks$ "/docs/networks" permanent;
-rewrite ^/docs/learn/fundamentals/networks$ "/docs/networks" permanent;
-
-# Meetings: old slug formats
-rewrite ^/meeting-notes/(\d\d\d\d)-(\d\d)-(\d\d)/?$ "/meetings/$1/$2/$3" permanent;
-rewrite ^/meeting-notes(.*)$ "/meetings$1" permanent;
-
-# Move some categories around
-rewrite ^/docs/category/build-a-wallet$ "/docs/build/apps/wallet" permanent;
-rewrite ^/docs/category/build-a-wallet-with-the-wallet-sdk$ "/docs/build/apps/wallet" permanent;
-rewrite ^/docs/category/build-a-payment-app-with-the-js-sdk$ "/docs/build/apps/example-application-tutorial" permanent;
-rewrite ^/docs/category/anchor-integration$ "/docs/build/apps/example-application-tutorial/anchor-integration" permanent;
-rewrite ^/docs/category/build-custom-network-ingestion-pipeline$ "/docs/build/apps/ingest-sdk" permanent;
-
-# Categorized Encyclopedia redirects
-rewrite ^/docs/learn/smart-contract-internals/authorization(.*)$ "/docs/learn/fundamentals/contract-development/authorization$1" permanent;
-rewrite ^/docs/learn/smart-contract-internals/types/built-in-types$ "/docs/learn/fundamentals/contract-development/types/built-in-types" permanent;
-rewrite ^/docs/learn/smart-contract-internals/types/custom-types$ "/docs/learn/fundamentals/contract-development/types/custom-types" permanent;
-rewrite ^/docs/learn/smart-contract-internals/types/fully-typed-contracts$ "/docs/learn/fundamentals/contract-development/types/fully-typed-contracts" permanent;
-rewrite ^/docs/learn/smart-contract-internals/contract-lifecycle$ "/docs/learn/fundamentals/contract-development/contract-lifecycle" permanent;
-rewrite ^/docs/learn/smart-contract-internals/rust-dialect$ "/docs/learn/fundamentals/contract-development/rust-dialect" permanent;
-rewrite ^/docs/learn/smart-contract-internals/debugging$ "/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging" permanent;
-rewrite ^/docs/learn/smart-contract-internals/debugging-errors$ "/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging-errors" permanent;
-rewrite ^/docs/learn/smart-contract-internals/environment-concepts$ "/docs/learn/fundamentals/contract-development/environment-concepts" permanent;
-rewrite ^/docs/learn/smart-contract-internals/errors$ "/docs/learn/fundamentals/contract-development/errors-and-debugging/errors" permanent;
-rewrite ^/docs/learn/smart-contract-internals/events$ "/docs/learn/fundamentals/contract-development/events" permanent;
-rewrite ^/docs/learn/smart-contract-internals/contract-interactions/overview$ "/docs/learn/fundamentals/contract-development/overview" permanent;
-rewrite ^/docs/learn/smart-contract-internals/contract-interactions/cross-contract$ "/docs/learn/fundamentals/contract-development/contract-interactions/cross-contract" permanent;
-rewrite ^/docs/learn/smart-contract-internals/contract-interactions/tests$ "/docs/learn/fundamentals/contract-development/contract-interactions/tests" permanent;
-rewrite ^/docs/learn/smart-contract-internals/contract-interactions/stellar-transaction$ "/docs/learn/fundamentals/contract-development/contract-interactions/stellar-transaction" permanent;
-rewrite ^/docs/learn/smart-contract-internals/contract-interactions/transaction-simulation$ "/docs/learn/fundamentals/contract-development/contract-interactions/transaction-simulation" permanent;
-rewrite ^/docs/learn/smart-contract-internals/persisting-data$ "/docs/learn/fundamentals/contract-development/storage/persisting-data" permanent;
-rewrite ^/docs/learn/smart-contract-internals/state-archival$ "/docs/learn/fundamentals/contract-development/storage/state-archival" permanent;
-rewrite ^/docs/learn/encyclopedia/anchors$ "/docs/learn/fundamentals/anchors" permanent;
-rewrite ^/docs/learn/encyclopedia/channel-accounts$ "/docs/learn/encyclopedia/transactions-specialized/channel-accounts" permanent;
-rewrite ^/docs/learn/encyclopedia/claimable-balances$ "/docs/learn/encyclopedia/transactions-specialized/claimable-balances" permanent;
-rewrite ^/docs/learn/encyclopedia/clawbacks$ "/docs/learn/encyclopedia/transactions-specialized/clawbacks" permanent;
-rewrite ^/docs/learn/encyclopedia/federation$ "/docs/learn/encyclopedia/network-configuration/federation" permanent;
-rewrite ^/docs/learn/encyclopedia/fee-bump-transactions$ "/docs/learn/encyclopedia/transactions-specialized/fee-bump-transactions" permanent;
-rewrite ^/docs/learn/encyclopedia/channel-accounts$ "/docs/learn/encyclopedia/transactions-specialized/channel-accounts" permanent;
-rewrite ^/docs/learn/encyclopedia/contract-development/fees-and-metering "/docs/learn/fundamentals/fees-resource-limits-metering" permanent;
-rewrite ^/docs/learn/encyclopedia/inflation$ "/docs/learn/encyclopedia/network-configuration/inflation" permanent;
-rewrite ^/docs/learn/encyclopedia/ledger-headers$ "/docs/learn/encyclopedia/network-configuration/ledger-headers" permanent;
-rewrite ^/docs/learn/encyclopedia/liquidity-on-stellar-sdex-liquidity-pools$ "/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools" permanent;
-rewrite ^/docs/learn/encyclopedia/sdex$ "/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools" permanent;
-rewrite ^/docs/learn/encyclopedia/sdex/liquidity-on-stellar-sdex-liquidity-pools$ "/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools" permanent;
-rewrite ^/docs/learn/encyclopedia/lumen-supply-metrics$ "/docs/learn/fundamentals/lumens#lumen-supply-metrics" permanent;
-rewrite ^/docs/learn/encyclopedia/memos$ "/docs/learn/encyclopedia/transactions-specialized/memos" permanent;
-rewrite ^/docs/learn/encyclopedia/network-passphrases$ "/docs/learn/encyclopedia/network-configuration/network-passphrases" permanent;
-rewrite ^/docs/learn/encyclopedia/path-payments$ "/docs/build/guides/transactions/path-payments" permanent;
-rewrite ^/docs/learn/encyclopedia/pooled-accounts-muxed-accounts-memos$ "/docs/learn/encyclopedia/transactions-specialized/pooled-accounts-muxed-accounts-memos" permanent;
-rewrite ^/docs/learn/encyclopedia/securing-web-based-projects$ "/docs/build/security-docs/securing-web-based-projects" permanent;
-rewrite ^/docs/learn/encyclopedia/signatures-multisig$ "/docs/learn/fundamentals/transactions/signatures-multisig" permanent;
-rewrite ^/docs/learn/encyclopedia/sponsored-reserves$ "/docs/learn/encyclopedia/transactions-specialized/sponsored-reserves" permanent;
-rewrite ^/docs/learn/encyclopedia/xdr$ "/docs/learn/encyclopedia/data-format/xdr" permanent;
-rewrite ^/network/core-node(.*)$ "/docs/validators$1" permanent;
-rewrite ^/network/hubble/(connecting|optimizing-queries|viewing-metadata)(.*)$ "/docs/data/analytics/hubble/analyst-guide/$1$2" permanent;
-rewrite ^/network/hubble(.*)$ "/docs/data/analytics/hubble$1" permanent;
-rewrite ^/network/soroban-rpc(.*)$ "/docs/data/apis/rpc$1" permanent;
-rewrite ^/network/horizon(.*)$ "/docs/data/apis/horizon$1" permanent;
-
-# Tokens section
-rewrite ^/docs/category/issue-assets$ "/docs/tokens" permanent;
-rewrite ^/docs/issuing-assets(.*)$ "/docs/tokens$1" permanent;
-rewrite ^/docs/smart-contracts/tokens/wayfinding(.*)$ "/docs/tokens$1" permanent;
-rewrite ^/docs/smart-contracts/tokens(.*)$ "/docs/tokens$1" permanent;
-
-# Build section
-rewrite ^/docs/category/basic-tutorials$ "/docs/build/guides/basics" permanent;
-rewrite ^/docs/tutorials(.*)$ "/docs/build/guides/basics$1" permanent;
-rewrite ^/docs/category/build-applications$ "/docs/build/apps" permanent;
-rewrite ^/docs/building-apps(.*)$ "/docs/build/apps$1" permanent;
-rewrite ^/docs/smart-contracts$ "/docs/build/smart-contracts/overview" permanent;
-rewrite ^/docs/smart-contracts/guides(.*)$ "/docs/build/guides$1" permanent;
-rewrite ^/docs/smart-contracts/smart-wallets(.*)$ "/docs/build/guides/contract-accounts$1" permanent;
-rewrite ^/docs/build/apps/smart-wallets(.*)$ "/docs/build/guides/contract-accounts$1" permanent;
-rewrite ^/docs/smart-contracts/getting-started/create-an-app(.*)$ "/docs/build/apps/dapp-frontend$1" permanent;
-rewrite ^/docs/smart-contracts(.*)$ "/docs/build/smart-contracts$1" permanent;
-rewrite ^/docs/build/guides/basics/follow-received-payments(.*)$ "/docs/build/guides/transactions/send-and-receive-payments$1" permanent;
-rewrite ^/docs/build/guides/transactions/install-wasm-bytecode(.*)$ "/docs/build/guides/transactions/upload-wasm-bytecode$1" permanent;
-
-# Moving testing docs around
-rewrite ^/docs/build/guides/testing/detecting-changes-with-test-snapshots(.*)$ "/docs/build/guides/testing/differential-tests-with-test-snapshots$1" permanent;
-rewrite ^/docs/build/guides/testing/integration-tests-with-mainnet-data(.*)$ "/docs/build/guides/testing/fork-testing$1" permanent;
-
-# Hubble redirects
-rewrite ^/docs/data/hubble(.*)$ "/docs/data/analytics/hubble$1" permanent;
-rewrite ^/docs/data/hubble/admin-guide(.*)$ "/docs/data/analytics/hubble/developer-guide$1" permanent;
-rewrite ^/docs/data/hubble/analytics-platforms(.*)$ "/docs/data/analytics/hubble/analytics-providers$1" permanent;
-
-rewrite ^/docs/data/analytics/hubble/data-catalog/data-dictionary/accounts$ "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/accounts" permanent;
-rewrite ^/docs/data/analytics/hubble/data-catalog/data-dictionary/claimable-balances$ "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/claimable-balances" permanent;
-rewrite ^/docs/data/analytics/hubble/data-catalog/data-dictionary/contract-code$ "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-code" permanent;
-rewrite ^/docs/data/analytics/hubble/data-catalog/data-dictionary/contract-data$ "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-data" permanent;
-rewrite ^/docs/data/analytics/hubble/data-catalog/data-dictionary/liquidity-pools$ "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/liquidity-pools" permanent;
-rewrite ^/docs/data/analytics/hubble/data-catalog/data-dictionary/offers$ "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/offers" permanent;
-rewrite ^/docs/data/analytics/hubble/data-catalog/data-dictionary/trustlines$ "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/trustlines" permanent;
-rewrite ^/docs/data/analytics/hubble/data-catalog/data-dictionary/ttl$ "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/ttl" permanent;
-rewrite ^/docs/data/analytics/hubble/data-catalog/data-dictionary/history-assets$ "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-assets" permanent;
-rewrite ^/docs/data/analytics/hubble/data-catalog/data-dictionary/history-contract-events$ "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-contract-events" permanent;
-rewrite ^/docs/data/analytics/hubble/data-catalog/data-dictionary/history-effects$ "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-effects" permanent;
-rewrite ^/docs/data/analytics/hubble/data-catalog/data-dictionary/history-ledgers$ "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-ledgers" permanent;
-rewrite ^/docs/data/analytics/hubble/data-catalog/data-dictionary/history-operations$ "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-operations" permanent;
-rewrite ^/docs/data/analytics/hubble/data-catalog/data-dictionary/history-trades$ "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-trades" permanent;
-rewrite ^/docs/data/analytics/hubble/data-catalog/data-dictionary/history-transactions$ "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-transactions" permanent;
-rewrite ^/docs/data/analytics/hubble/data-catalog/data-dictionary/enriched-history-operations$ "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations" permanent;
-
-# RPC redirects
-rewrite ^/docs/data/rpc(.*)$ "/docs/data/apis/rpc$1" permanent;
-rewrite ^/docs/data/apis/rpc/rpc-providers(.*)$ "/docs/data/apis/rpc/providers$1" permanent;
-rewrite ^/docs/data/apis/api-providers(.*)$ "/docs/data/apis/rpc/providers$1" permanent;
-
-# Horizon redirects
-rewrite ^/docs/data/horizon(.*)$ "/docs/data/apis/horizon$1" permanent;
-rewrite ^/docs/data/migrate-from-horizon-to-rpc(.*)$ "/docs/data/apis/migrate-from-horizon-to-rpc$1" permanent;
-rewrite ^/docs/data/apis/horizon/horizon-providers(.*)$ "/docs/data/apis/horizon/providers$1" permanent;
-
-# Galexie redirects
-rewrite ^/docs/data/galexie(.*)$ "/docs/data/indexers/build-your-own/galexie$1" permanent;
-
-# Indexer redirects
-rewrite ^/docs/data/data-indexers(.*)$ "/docs/data/indexers$1" permanent;
-
-# Moving tooling docs (https://github.com/stellar/stellar-docs/pull/1444)
-rewrite ^/docs/tools/developer-tools/cli(.*)$ "/docs/tools/cli$1" permanent;
-rewrite ^/docs/tools/developer-tools/lab(.*)$ "/docs/tools/lab$1" permanent;
-rewrite ^/docs/tools/developer-tools/quickstart(.*)$ "/docs/tools/quickstart$1" permanent;
-rewrite ^/docs/tools/developer-tools/openzepplin-contracts(.*)$ "/docs/tools/developer-tools/openzeppelin-contracts$1" permanent;
-rewrite ^/docs/tools/cli/cookbook/install-(deploy|wasm)(.*)$ "/docs/tools/cli/cookbook/upload-$1$2" permanent;
-rewrite ^/docs/build/guides/cli/install-(deploy|wasm)(.*)$ "/docs/tools/cli/cookbook/upload-$1$2" permanent;
-rewrite ^/docs/build/guides/cli(.*)$ "/docs/tools/cli/cookbook$1" permanent;
-
-# MoneyGram
-rewrite /docs/build/apps/moneygram-access-integration-guide "https://developer.moneygram.com/moneygram-developer/docs/integrate-moneygram-ramps" permanent;
-
-# XDR
-rewrite ^/docs/learn/encyclopedia/data-format$ "/docs/learn/fundamentals/data-format" permanent;
-rewrite ^/docs/learn/encyclopedia/data-format/xdr$ "/docs/learn/fundamentals/data-format/xdr" permanent;
-rewrite ^/docs/learn/encyclopedia/data-format/xdr-json$ "/docs/learn/fundamentals/data-format/xdr-json" permanent;
-
-# Stellar Disbursement Platform
-rewrite ^/platforms/stellar-disbursement-platform/admin-guide/anchor-platform-integration-points$ "/docs/platforms/stellar-disbursement-platform/admin-guide" permanent;
-rewrite ^/platforms/stellar-disbursement-platform/admin-guide/single-tenant-to-multi-tenant-migration$ "/docs/platforms/stellar-disbursement-platform/admin-guide" permanent;
-rewrite ^/platforms/stellar-disbursement-platform/admin-guide/tenant-provisioning$ "/docs/platforms/stellar-disbursement-platform/admin-guide/advanced-configration#provisioning-tenants" permanent;
-rewrite ^/platforms/stellar-disbursement-platform/admin-guide/secure-operation-manual$ "/docs/platforms/stellar-disbursement-platform/admin-guide/security" permanent;
-rewrite ^/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/wallets$ "/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/distribution-accounts" permanent;
-# and a blanket "/platforms" redirect
-rewrite ^/platforms(.*)$ "/docs/platforms$1" permanent;
-
-# Moving the contract development section (https://github.com/stellar/stellar-docs/pull/1557)
-rewrite ^/docs/learn/encyclopedia/errors-and-debugging(.*)$ "/docs/learn/fundamentals/contract-development/errors-and-debugging$1" permanent;
-rewrite ^/docs/learn/encyclopedia/security/authorization(.*)$ "/docs/learn/fundamentals/contract-development/authorization$1" permanent;
-rewrite ^/docs/learn/encyclopedia/storage(.*)$ "/docs/learn/fundamentals/contract-development/storage$1" permanent;
-rewrite ^/docs/learn/encyclopedia/contract-development(.*)$ "/docs/learn/fundamentals/contract-development$1" permanent;
-
-# Moving the security section (https://github.com/stellar/stellar-docs/pull/1580)
-rewrite ^/docs/learn/encyclopedia/security/signatures-multisig$ "/docs/learn/fundamentals/transactions/signatures-multisig" permanent;
-rewrite ^/docs/learn/encyclopedia/security/securing-web-based-projects$ "/docs/build/security-docs/securing-web-based-projects" permanent;
-rewrite ^/docs/learn/encyclopedia/security "/docs/learn/fundamentals/transactions/signatures-multisig" permanent;
-
-# Transactions (specialized) Encyclopedia redirects
-rewrite ^/docs/learn/encyclopedia/transactions-specialized/channel-accounts$ "/docs/build/guides/transactions/channel-accounts" permanent;
-rewrite ^/docs/learn/encyclopedia/transactions-specialized/claimable-balances$ "/docs/build/guides/transactions/claimable-balances" permanent;
-rewrite ^/docs/learn/encyclopedia/transactions-specialized/clawbacks$ "/docs/build/guides/transactions/clawbacks" permanent;
-rewrite ^/docs/learn/encyclopedia/transactions-specialized/fee-bump-transactions$ "/docs/build/guides/transactions/fee-bump-transactions" permanent;
-rewrite ^/docs/learn/encyclopedia/transactions-specialized/memos$ "/docs/learn/fundamentals/transactions/operations-and-transactions#memo" permanent;
-rewrite ^/docs/learn/encyclopedia/transactions-specialized/path-payments "/docs/build/guides/transactions/path-payments" permanent;
-rewrite ^/docs/learn/encyclopedia/transactions-specialized/pooled-accounts-muxed-accounts-memos$ "/docs/build/guides/transactions/pooled-accounts-muxed-accounts-memos" permanent;
-rewrite ^/docs/learn/encyclopedia/transactions-specialized/sponsored-reserves$ "/docs/build/guides/transactions/sponsored-reserves" permanent;
-rewrite ^/docs/learn/encyclopedia/transactions-specialized$ "/docs/build/guides/transactions" permanent;
-
-# Move a couple Stellar Basics guides
-rewrite ^/docs/build/guides/basics/create-account$ "/docs/build/guides/transactions/create-account" permanent;
-rewrite ^/docs/build/guides/basics/send-and-receive-payments$ "/docs/build/guides/transactions/send-and-receive-payments" permanent;
-
-# Move events
-rewrite ^/docs/learn/fundamentals/contract-development/events$ "/docs/learn/fundamentals/stellar-data-structures/events" permanent;
-
-rewrite ^/docs/learn/encyclopedia$ /docs/learn/fundamentals permanent;
-
-# x402 moved from build/apps to build/agentic-payments
-rewrite ^/docs/build/apps/x402(.*)$ "/docs/build/agentic-payments/x402$1" permanent;
-
-# Move Building with AI section
-rewrite ^/docs/tools/developer-tools/building-with-ai(.*)$ "/docs/build/building-with-ai$1" permanent;
-
-# Removed OpenZeppelin token example pages (https://github.com/stellar/stellar-docs/issues/2691)
-rewrite ^/docs/build/smart-contracts/example-contracts/fungible-token$ "/docs/build/smart-contracts/example-contracts/tokens" permanent;
-rewrite ^/docs/build/smart-contracts/example-contracts/non-fungible-token$ "/docs/build/smart-contracts/example-contracts/tokens" permanent;
diff --git a/nginx/nginx.conf b/nginx/nginx.conf
deleted file mode 100644
index 2700e3007..000000000
--- a/nginx/nginx.conf
+++ /dev/null
@@ -1,49 +0,0 @@
-events { }
-
-http {
-  include mime.types;
-
-  # Serve text responses (notably the raw .md markdown-source copies) with an
-  # explicit charset; without it browsers fall back to Windows-1252 and render
-  # UTF-8 punctuation (em dashes, arrows) as mojibake.
-  charset utf-8;
-
-  server {
-    root /usr/share/nginx/html;
-
-    listen 80 default_server;
-    listen [::]:80 default ipv6only=on;
-    server_name _;
-    include includes/redirects.conf;
-
-    index index.html;
-    error_page 404 /404.html;
-
-    location / {
-        rewrite ^/(.*)/$ /$1 permanent;
-        try_files $uri $uri.html $uri/index.html =404;
-        add_header 'Link' '</.well-known/api-catalog>; rel="api-catalog"' always;
-    }
-    location /assets/ {
-        try_files $uri $uri/ =404;
-    }
-    location /img/ {
-        try_files $uri $uri/ =404;
-    }
-    location /icons/ {
-        try_files $uri $uri/ =404;
-    }
-    location /index.html {
-        add_header 'Cache-Control' 'no-store' always;
-        add_header 'Link' '</.well-known/api-catalog>; rel="api-catalog"' always;
-    }
-    location /404.html {
-        add_header 'Cache-Control' 'no-store' always;
-        add_header 'Link' '</.well-known/api-catalog>; rel="api-catalog"' always;
-    }
-    # RFC 9727 — extension-less file, advertise correct content type
-    location = /.well-known/api-catalog {
-        types { } default_type application/linkset+json;
-    }
-  }
-}
diff --git a/openapi/horizon/bundled.yml b/openapi/horizon/bundled.yml
index 4691e9def..18ed28ff0 100644
--- a/openapi/horizon/bundled.yml
+++ b/openapi/horizon/bundled.yml
@@ -19,7 +19,6 @@ info:
   license:
     name: Apache 2.0
     identifier: Apache-2.0
-    url: http://www.apache.org/licenses/LICENSE-2.0.html
 servers:
   - url: https://horizon-testnet.stellar.org
     description: The Testnet Network
@@ -1574,6 +1573,9 @@ components:
       in: query
       required: false
       description: An issued asset represented as “Code:IssuerAccountID”. Every account in the response will have a trustline for the given asset.
+      schema:
+        type: string
+        example: USD:GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX
     SignerParam:
       name: signer
       in: query
@@ -1587,6 +1589,9 @@ components:
       in: query
       required: false
       description: With this parameter, the results will include only accounts which have trustlines to the specified liquidity pool.
+      schema:
+        type: string
+        example: 33f3c53f53e6d1f1f13d7f9d9b58c2cb5c7e0b0a4d1d3c5b2a6f7e8d9c0b1a2f
     CursorParam:
       name: cursor
       in: query
@@ -1636,6 +1641,10 @@ components:
       in: query
       required: false
       description: Set to transactions to include the transactions which created each of the operations in the response.
+      schema:
+        type: string
+        enum:
+          - transactions
     DataParam:
       name: key
       in: path
@@ -1649,16 +1658,25 @@ components:
       in: query
       required: false
       description: The code of the asset you would like to filter by.
+      schema:
+        type: string
+        example: USD
     AssetIssuerParam:
       name: asset_issuer
       in: query
       required: false
       description: The Stellar address of the issuer for the asset you would like to filter by.
+      schema:
+        type: string
+        example: GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX
     ClaimantParam:
       name: claimant
       in: query
       required: false
       description: Account ID of the destination address. Only include claimable balances which can be claimed by the given account ID.
+      schema:
+        type: string
+        example: GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ
     ClaimableBalanceIdParam:
       name: claimable_balance_id
       in: path
@@ -1679,21 +1697,33 @@ components:
       in: query
       required: false
       description: Comma-separated list of assets in canonical form (Code:IssuerAccountID), to only include liquidity pools which have reserves matching all listed assets.
+      schema:
+        type: string
+        example: USD:GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX,EUR:GAV7W5X4M7FQJ2OAPJVRX5ZQ3D5XJXHFGQ2G6UTW7C6H5N7WJQ4V6Z3R
     AccountParam:
       name: account
       in: query
       required: false
       description: A Stellar account ID, to only include liquidity pools in which this account is participating in (i.e. holds pool shares to).
+      schema:
+        type: string
+        example: GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ
     LiquidityPoolParamId:
       name: liquidity_pool_id
       in: path
       required: true
       description: A unique identifier for this liquidity pool.
+      schema:
+        type: string
+        example: 33f3c53f53e6d1f1f13d7f9d9b58c2cb5c7e0b0a4d1d3c5b2a6f7e8d9c0b1a2f
     SellerParam:
       name: seller
       in: query
       required: false
       description: The account ID of the offer creator.
+      schema:
+        type: string
+        example: GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ
     SellingAssetTypeParam:
       name: selling_asset_type
       in: query
@@ -1753,6 +1783,9 @@ components:
       in: path
       required: true
       description: A unique identifier for this offer.
+      schema:
+        type: string
+        example: '123456789'
     IdParam:
       name: id
       in: path
@@ -1986,6 +2019,9 @@ components:
       in: query
       required: false
       description: The offer ID. Used to filter for trades originating from a specific offer.
+      schema:
+        type: string
+        example: '123456789'
     BaseAssetTypeParam:
       name: base_asset_type
       in: query
diff --git a/openapi/horizon/components/parameters.yml b/openapi/horizon/components/parameters.yml
index 9fd963db9..992d5a75c 100644
--- a/openapi/horizon/components/parameters.yml
+++ b/openapi/horizon/components/parameters.yml
@@ -5,6 +5,9 @@ components:
       in: query
       required: false
       description: "A Stellar account ID, to only include liquidity pools in which this account is participating in (i.e. holds pool shares to)."
+      schema:
+        type: string
+        example: GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ
     AccountIDParam:
       name: account_id
       in: path
@@ -18,16 +21,25 @@ components:
       in: query
       required: false
       description: The code of the asset you would like to filter by.
+      schema:
+        type: string
+        example: USD
     AssetIssuerParam:
         name: asset_issuer
         in: query
         required: false
         description: The Stellar address of the issuer for the asset you would like to filter by.
+        schema:
+          type: string
+          example: GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX
     AssetParam:
       name: asset
       in: query
       required: false
       description: An issued asset represented as “Code:IssuerAccountID”. Every account in the response will have a trustline for the given asset.
+      schema:
+        type: string
+        example: USD:GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX
     BaseAssetCodeParam:
       name: base_asset_code
       in: query
@@ -105,6 +117,9 @@ components:
       in: query
       required: false
       description: Account ID of the destination address. Only include claimable balances which can be claimed by the given account ID.
+      schema:
+        type: string
+        example: GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ
     CounterAssetCodeParam:
       name: counter_asset_code
       in: query
@@ -249,6 +264,10 @@ components:
       in: query
       required: false
       description: Set to transactions to include the transactions which created each of the operations in the response.
+      schema:
+        type: string
+        enum:
+          - transactions
     LimitParam:
       name: limit
       in: query
@@ -270,21 +289,33 @@ components:
       in: query
       required: false
       description: With this parameter, the results will include only accounts which have trustlines to the specified liquidity pool.
+      schema:
+        type: string
+        example: 33f3c53f53e6d1f1f13d7f9d9b58c2cb5c7e0b0a4d1d3c5b2a6f7e8d9c0b1a2f
     LiquidityPoolParamId:
       name: liquidity_pool_id
       in: path
       required: true
       description: A unique identifier for this liquidity pool.
+      schema:
+        type: string
+        example: 33f3c53f53e6d1f1f13d7f9d9b58c2cb5c7e0b0a4d1d3c5b2a6f7e8d9c0b1a2f
     OfferIdParam:
       name: offer_id
       in: query
       required: false
       description: The offer ID. Used to filter for trades originating from a specific offer.
+      schema:
+        type: string
+        example: "123456789"
     OfferIDParam:
       name: offer_id
       in: path
       required: true
       description: A unique identifier for this offer.
+      schema:
+        type: string
+        example: "123456789"
     OffsetParam:
       name: offset
       in: query
@@ -308,6 +339,9 @@ components:
       in: query
       required: false
       description: Comma-separated list of assets in canonical form (Code:IssuerAccountID), to only include liquidity pools which have reserves matching all listed assets.
+      schema:
+        type: string
+        example: USD:GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX,EUR:GAV7W5X4M7FQJ2OAPJVRX5ZQ3D5XJXHFGQ2G6UTW7C6H5N7WJQ4V6Z3R
     ResolutionParam:
       name: resolution
       in: query
@@ -334,6 +368,9 @@ components:
       in: query
       required: false
       description: The account ID of the offer creator.
+      schema:
+        type: string
+        example: GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ
     SellingAssetCodeParam:
       name: selling_asset_code
       in: query
diff --git a/openapi/horizon/main.yml b/openapi/horizon/main.yml
index 259003464..410cd67bf 100644
--- a/openapi/horizon/main.yml
+++ b/openapi/horizon/main.yml
@@ -19,7 +19,6 @@ info:
   license:
     name: Apache 2.0
     identifier: Apache-2.0
-    url: http://www.apache.org/licenses/LICENSE-2.0.html
 servers:
   - url: https://horizon-testnet.stellar.org
     description: The Testnet Network
diff --git a/openrpc/scripts/build.mjs b/openrpc/scripts/build.mjs
index ce6bc68e6..dc5d884c7 100644
--- a/openrpc/scripts/build.mjs
+++ b/openrpc/scripts/build.mjs
@@ -128,7 +128,7 @@ async function buildSpecFile(serviceName) {
 
   let data = JSON.stringify(spec, null, 2);
   fs.writeFileSync(`openrpc/${serviceName}.openrpc.json`, data);
-  fs.writeFileSync(`${services[serviceName].saveDir ?? 'static'}/${serviceName}.openrpc.json`, data);
+  fs.writeFileSync(`${services[serviceName].saveDir ?? '.'}/${serviceName}.openrpc.json`, data);
 
   console.log(`Built ${serviceName} specfile successfully.`);
 }
diff --git a/os-tab-sync.js b/os-tab-sync.js
new file mode 100644
index 000000000..4a93586f5
--- /dev/null
+++ b/os-tab-sync.js
@@ -0,0 +1,190 @@
+
+(function () {
+  "use strict";
+
+  if (typeof window === "undefined" || typeof document === "undefined") return;
+
+  var SESSION_OVERRIDE_KEY = "osTabSync:userChose";
+  var GROUP_DONE_ATTR = "data-os-tab-defaulted";
+
+  // Ordered patterns per OS category. Within a category, earlier patterns win,
+  // so a Windows visitor prefers a "PowerShell" tab over a generic "Windows"
+  // one only where that ordering is intended — tweak freely.
+  var OS_LABEL_PATTERNS = {
+    windows: [/power\s*shell/i, /windows/i, /\bwin(32|64|dows)?\b/i, /\bwsl\b/i],
+    mac: [/mac\s*os/i, /\bmac\b/i, /os\s*x|osx/i, /darwin/i, /\bzsh\b/i],
+    linux: [/linux/i, /ubuntu|debian|fedora|arch/i, /\bbash\b/i, /x11/i],
+  };
+
+  // Detect the visitor's OS category from UA-CH (preferred) or the UA string.
+  function detectOS() {
+    var platform = "";
+    try {
+      if (navigator.userAgentData && navigator.userAgentData.platform) {
+        platform = navigator.userAgentData.platform;
+      }
+    } catch (e) {
+      /* UA-CH not available — fall through to UA string */
+    }
+    var haystack = (
+      platform +
+      " " +
+      (navigator.platform || "") +
+      " " +
+      (navigator.userAgent || "")
+    ).toLowerCase();
+
+    // Order matters: iOS/iPadOS report "like Mac OS X", so check Windows first,
+    // then Mac, then Linux. Mobile is intentionally treated loosely.
+    if (/windows|win32|win64|\bwin\b/.test(haystack)) return "windows";
+    if (/mac|iphone|ipad|ipod|darwin/.test(haystack)) return "mac";
+    if (/linux|x11|cros|android/.test(haystack)) return "linux";
+    return null;
+  }
+
+  function labelOf(tab) {
+    return (tab.textContent || "").trim();
+  }
+
+  // Which OS category does a tab label belong to? Returns the first matching
+  // category (object key order: windows, mac, linux). Combined labels like
+  // "macOS/Linux" resolve to the first category that matches (mac).
+  function categoryOfLabel(label) {
+    for (var cat in OS_LABEL_PATTERNS) {
+      if (!Object.prototype.hasOwnProperty.call(OS_LABEL_PATTERNS, cat))
+        continue;
+      var patterns = OS_LABEL_PATTERNS[cat];
+      for (var i = 0; i < patterns.length; i++) {
+        if (patterns[i].test(label)) return cat;
+      }
+    }
+    return null;
+  }
+
+  // Find the best-matching tab in a group for an OS category, honoring the
+  // intra-category priority order.
+  function pickTabForCategory(tabs, category) {
+    var patterns = OS_LABEL_PATTERNS[category];
+    if (!patterns) return null;
+    for (var p = 0; p < patterns.length; p++) {
+      for (var t = 0; t < tabs.length; t++) {
+        if (patterns[p].test(labelOf(tabs[t]))) return tabs[t];
+      }
+    }
+    return null;
+  }
+
+  function tabsInGroup(tablist) {
+    return Array.prototype.slice.call(
+      tablist.querySelectorAll('[role="tab"]')
+    );
+  }
+
+  function isSelected(tab) {
+    return tab.getAttribute("aria-selected") === "true";
+  }
+
+  var programmaticClick = false;
+  function selectTab(tab) {
+    if (!tab || isSelected(tab)) return;
+    programmaticClick = true;
+    try {
+      tab.click(); // real click -> Mintlify's own onClick (sync + persist) runs
+    } finally {
+      programmaticClick = false;
+    }
+  }
+
+  function userHasOverridden() {
+    try {
+      return sessionStorage.getItem(SESSION_OVERRIDE_KEY) === "1";
+    } catch (e) {
+      return false;
+    }
+  }
+
+  function markUserOverride() {
+    try {
+      sessionStorage.setItem(SESSION_OVERRIDE_KEY, "1");
+    } catch (e) {
+      /* storage blocked — in-memory flag below still protects this page */
+    }
+  }
+
+  // Apply the OS default to any tab groups we have not touched yet.
+  function applyOsDefaults(os) {
+    if (!os || userHasOverridden()) return;
+    // A deep link to a specific tab/section should win over the OS default.
+    if (window.location.hash && window.location.hash.length > 1) return;
+
+    var tablists = document.querySelectorAll('[role="tablist"]');
+    for (var i = 0; i < tablists.length; i++) {
+      var tablist = tablists[i];
+      if (tablist.getAttribute(GROUP_DONE_ATTR) === "1") continue;
+      var tabs = tabsInGroup(tablist);
+      if (!tabs.length) continue;
+      var target = pickTabForCategory(tabs, os);
+      tablist.setAttribute(GROUP_DONE_ATTR, "1"); // mark regardless of match
+      if (target) selectTab(target);
+    }
+  }
+
+  // Cross-group sync by OS category (looser than Mintlify's exact-label sync).
+  function syncByCategory(sourceTab) {
+    var category = categoryOfLabel(labelOf(sourceTab));
+    if (!category) return;
+    var tablists = document.querySelectorAll('[role="tablist"]');
+    for (var i = 0; i < tablists.length; i++) {
+      var tabs = tabsInGroup(tablists[i]);
+      if (tabs.indexOf(sourceTab) !== -1) continue; // skip the source group
+      var match = pickTabForCategory(tabs, category);
+      if (match) selectTab(match);
+    }
+  }
+
+  // One delegated listener handles manual clicks for both features.
+  document.addEventListener(
+    "click",
+    function (event) {
+      var tab = event.target && event.target.closest
+        ? event.target.closest('[role="tab"]')
+        : null;
+      if (!tab) return;
+
+      if (programmaticClick) return; // ignore clicks we dispatched ourselves
+
+      // Genuine user interaction: stop auto-defaulting and propagate by category.
+      markUserOverride();
+      // Let Mintlify's own handler run first, then widen the sync by category.
+      window.setTimeout(function () {
+        syncByCategory(tab);
+      }, 0);
+    },
+    true
+  );
+
+  var detectedOS = detectOS();
+
+  function run() {
+    applyOsDefaults(detectedOS);
+  }
+
+  if (document.readyState === "loading") {
+    document.addEventListener("DOMContentLoaded", run);
+  } else {
+    run();
+  }
+
+  // Mintlify is a single-page app: route changes swap <Tabs> in without a full
+  // reload. Watch for newly mounted tab groups and default them too (until the
+  // user overrides).
+  var observer = new MutationObserver(function () {
+    if (userHasOverridden() || !detectedOS) return;
+    if (window.location.hash && window.location.hash.length > 1) return;
+    applyOsDefaults(detectedOS);
+  });
+  observer.observe(document.documentElement, {
+    childList: true,
+    subtree: true,
+  });
+})();
diff --git a/package.json b/package.json
index 98941a980..0aff134dd 100644
--- a/package.json
+++ b/package.json
@@ -3,31 +3,22 @@
   "version": "0.0.0",
   "private": true,
   "scripts": {
-    "docusaurus": "docusaurus",
-    "start": "docusaurus start",
-    "build": "docusaurus build",
-    "postbuild": "node scripts/generate_api_markdown.mjs && node scripts/rewrite_md_code_examples.mjs && node scripts/rewrite_md_titles.mjs && node scripts/rewrite_md_links.mjs && node scripts/rewrite_md_admonitions.mjs",
-    "swizzle": "docusaurus swizzle",
-    "deploy": "docusaurus deploy",
-    "clear": "docusaurus clear",
-    "serve": "docusaurus serve",
-    "api:clean": "docusaurus clean-api-docs all",
+    "start": "mint dev",
+    "validate": "mint validate",
+    "check:links": "mint broken-links --check-anchors --check-redirects --check-snippets",
+    "check:a11y": "mint a11y",
+    "check": "pnpm check:mdx && pnpm check:pad && pnpm validate",
     "api:bundle": "pnpm bundle-horizon && pnpm bundle-anchor-platform && pnpm bundle-stellar-disbursement-platform",
-    "bundle-horizon": "redocly bundle horizon --output openapi/horizon/bundled.yml",
     "bundle-anchor-platform": "redocly bundle ap-platform --output openapi/anchor-platform/bundled-platform.yaml && redocly bundle ap-callbacks --output openapi/anchor-platform/bundled-callbacks.yaml",
+    "bundle-horizon": "redocly bundle horizon --output openapi/horizon/bundled.yml",
     "bundle-stellar-disbursement-platform": "redocly bundle stellar-disbursement-platform --output openapi/stellar-disbursement-platform/bundled.yaml",
-    "api:gen": "docusaurus gen-api-docs all",
-    "api": "pnpm api:clean && pnpm api:bundle && pnpm api:gen",
-    "write-translations": "docusaurus write-translations",
-    "write-heading-ids": "docusaurus write-heading-ids",
-    "format:mdx": "prettier --config .prettierrc.js --write \"{docs,src/pages,meetings}/**/*.{md,mdx}\"",
-    "ci-format:mdx": "prettier --config .prettierrc.js --write --log-level silent \"{docs,src/pages,meetings}/**/*.{md,mdx}\"",
-    "check:mdx": "prettier --config .prettierrc.js -c \"{docs,src/pages,meetings}/**/*.{md,mdx}\"",
-    "check:links": "scripts/check-relative-links.sh --range",
-    "ci:mdx": "prettier --config .prettierrc.js \"{docs,src/pages,meetings}/**/*.{md,mdx}\" -l --no-editorconfig",
+    "check:mdx": "prettier --config .prettierrc.js -c \"{docs,meetings,snippets}/**/*.{md,mdx}\"",
+    "ci-format:mdx": "prettier --config .prettierrc.js --write --log-level silent \"{docs,meetings,snippets}/**/*.{md,mdx}\"",
+    "ci:mdx": "prettier --config .prettierrc.js \"{docs,meetings,snippets}/**/*.{md,mdx}\" -l --no-editorconfig",
     "diff:mdx": "pnpm ci-format:mdx && git diff -- . ':(exclude)package-lock.json' ':(exclude)package.json' ':(exclude)yarn.lock' ':(exclude)pnpm-lock.yaml' | awk \"/diff --git/ {found=1} found {print}\"",
-    "lint:fix": "eslint \"src/**/*.{js,jsx,ts,tsx}\" --fix",
-    "lint": "eslint \"src/**/*.{js,jsx,ts,tsx}\"",
+    "pad:mdx": "node scripts/pad-component-tags.mjs $(git ls-files 'docs/*.md*' 'meetings/*.md*' 'snippets/*.md*')",
+    "check:pad": "node scripts/pad-component-tags.mjs --check $(git ls-files 'docs/*.md*' 'meetings/*.md*' 'snippets/*.md*')",
+    "format:mdx": "pnpm pad:mdx && prettier --config .prettierrc.js --write \"{docs,meetings,snippets}/**/*.{md,mdx}\"",
     "prepare": "husky",
     "rpcspec:build": "node openrpc/scripts/build.mjs",
     "rpcspec:validate": "node openrpc/scripts/build.mjs && node openrpc/scripts/validate.mjs",
@@ -35,63 +26,18 @@
     "stellar-cli:fix-links": "./scripts/fix_cli_links.sh"
   },
   "dependencies": {
-    "@docusaurus/core": "3.10.1",
-    "@docusaurus/faster": "3.10.1",
-    "@docusaurus/plugin-content-docs": "3.10.1",
-    "@docusaurus/preset-classic": "3.10.1",
-    "@docusaurus/remark-plugin-npm2yarn": "3.10.1",
-    "@docusaurus/theme-common": "3.10.1",
-    "@docusaurus/theme-mermaid": "3.10.1",
     "@json-schema-tools/reference-resolver": "1.2.6",
-    "@mdx-js/react": "3.1.1",
-    "@open-rpc/meta-schema": "^1.14.9",
     "@open-rpc/schema-utils-js": "^2.2.1",
-    "@stellar/open-rpc-docs-react": "^0.2.1",
-    "ajv": "^8.20.0",
-    "clsx": "^2.1.1",
-    "docusaurus-markdown-source-plugin": "^2.2.4",
-    "docusaurus-plugin-openapi-docs": "5.1.0",
-    "docusaurus-plugin-sass": "^0.2.6",
-    "docusaurus-plugin-sentry": "^2.1.0",
-    "docusaurus-theme-openapi-docs": "5.1.0",
     "fs-extra": "^11.3.6",
-    "prism-react-renderer": "^2.4.1",
-    "react": "^19.2.7",
-    "react-dom": "^19.2.7",
-    "rehype-katex": "^7.0.1",
-    "remark-math": "^6.0.0",
-    "sass": "^1.101.0",
     "json-schema-merge-allof": "^0.8.1",
     "yargs": "^18.0.0"
   },
-  "browserslist": {
-    "production": [
-      ">0.5%",
-      "not dead",
-      "not op_mini all"
-    ],
-    "development": [
-      "last 1 chrome version",
-      "last 1 firefox version",
-      "last 1 safari version"
-    ]
-  },
   "devDependencies": {
-    "@docusaurus/eslint-plugin": "3.10.1",
-    "@docusaurus/module-type-aliases": "3.10.1",
-    "@docusaurus/tsconfig": "3.10.1",
-    "@docusaurus/types": "3.10.1",
-    "@eslint/eslintrc": "^3.3.5",
-    "@eslint/js": "^10.0.1",
     "@redocly/cli": "^2.38.0",
     "@stellar/prettier-config": "^1.2.0",
-    "@types/react": "^19.2.17",
-    "docusaurus-plugin-llms": "^0.4.0",
-    "eslint": "^10.6.0",
-    "glob": "^13.0.6",
     "husky": "^9.1.7",
-    "prettier": "^3.9.4",
-    "typescript": "^6.0.3"
+    "mint": "^4.2.1062",
+    "prettier": "^3.9.4"
   },
   "engines": {
     "node": ">=24"
diff --git a/patches/@stoplight__json-schema-viewer.patch b/patches/@stoplight__json-schema-viewer.patch
deleted file mode 100644
index 7dd274d28..000000000
--- a/patches/@stoplight__json-schema-viewer.patch
+++ /dev/null
@@ -1,124 +0,0 @@
-diff --git a/index.esm.js b/index.esm.js
-index 26cb6e0a5a4141e6438e165a8ef602709c29b39a..caaf68b31ce233fe38f47b46b76bb2b50f968ea5 100644
---- a/index.esm.js
-+++ b/index.esm.js
-@@ -2,8 +2,8 @@ import { isRegularNode, SchemaNodeKind, isReferenceNode, isRootNode, isBooleanis
- import { Box, HStack, Flex, Icon, Text, Link, Tooltip, NodeAnnotation, VStack, Select, Menu, Pressable, Provider } from '@stoplight/mosaic';
- import { withErrorBoundary } from '@stoplight/react-error-boundary';
- import cn from 'classnames';
--import { atom, useAtom, Provider as Provider$1 } from 'jotai';
--import { atomFamily, useUpdateAtom, useAtomValue } from 'jotai/utils';
-+import { atom, useAtom, Provider as Provider$1, useAtomValue, useSetAtom } from 'jotai';
-+import { atomFamily } from 'jotai/utils';
- import * as React from 'react';
- import { useState, useEffect } from 'react';
- import { isPlainObject, getLastPathSegment, extractPointerFromRef, pointerToPath } from '@stoplight/json';
-@@ -706,7 +706,7 @@ const shouldShowChildSelector = (schemaNode) => { var _a, _b; return isNonEmptyP
- const SchemaRow = React.memo(({ schemaNode, nestingLevel, pl, parentNodeId, parentChangeType }) => {
-     var _a, _b, _c;
-     const { defaultExpandedDepth, renderRowAddon, renderExtensionAddon, onGoToRef, hideExamples, renderRootTreeLines, nodeHasChanged, viewMode, } = useJSVOptionsContext();
--    const setHoveredNode = useUpdateAtom(hoveredNodeAtom);
-+    const setHoveredNode = useSetAtom(hoveredNodeAtom);
-     const nodeId = getNodeId(schemaNode, parentNodeId);
-     const originalNodeId = ((_a = schemaNode.originalFragment) === null || _a === void 0 ? void 0 : _a.$ref) ? getOriginalNodeId(schemaNode, parentNodeId) : nodeId;
-     const mode = viewMode === 'standalone' ? undefined : viewMode;
-@@ -876,7 +876,7 @@ const TopLevelSchemaRow = ({ schemaNode, skipDescription, }) => {
- function ScrollCheck() {
-     const elementRef = React.useRef(null);
-     const isOnScreen = useIsOnScreen(elementRef);
--    const setShowPathCrumbs = useUpdateAtom(showPathCrumbsAtom);
-+    const setShowPathCrumbs = useSetAtom(showPathCrumbsAtom);
-     React.useEffect(() => {
-         setShowPathCrumbs(!isOnScreen);
-     }, [isOnScreen, setShowPathCrumbs]);
-@@ -916,7 +916,7 @@ const JsonSchemaViewerComponent = (_a) => {
-                 React.createElement(JsonSchemaViewerInner, Object.assign({ viewMode: viewMode, skipTopLevelDescription: skipTopLevelDescription }, rest))))));
- };
- const JsonSchemaViewerInner = ({ schema, viewMode, className, resolveRef, maxRefDepth, emptyText = 'No schema defined', onTreePopulated, maxHeight, parentCrumbs, skipTopLevelDescription, }) => {
--    const setHoveredNode = useUpdateAtom(hoveredNodeAtom);
-+    const setHoveredNode = useSetAtom(hoveredNodeAtom);
-     const onMouseLeave = React.useCallback(() => {
-         setHoveredNode(null);
-     }, [setHoveredNode]);
-diff --git a/index.js b/index.js
-index 55fcf60910660b14c8902e36bf1561005abf9d74..60799c7a8b9aa65feddb15c924771938b8a1e3b6 100644
---- a/index.js
-+++ b/index.js
-@@ -727,7 +727,7 @@ const shouldShowChildSelector = (schemaNode) => { var _a, _b; return isNonEmptyP
- const SchemaRow = React__namespace.memo(({ schemaNode, nestingLevel, pl, parentNodeId, parentChangeType }) => {
-     var _a, _b, _c;
-     const { defaultExpandedDepth, renderRowAddon, renderExtensionAddon, onGoToRef, hideExamples, renderRootTreeLines, nodeHasChanged, viewMode, } = useJSVOptionsContext();
--    const setHoveredNode = utils.useUpdateAtom(hoveredNodeAtom);
-+    const setHoveredNode = jotai.useSetAtom(hoveredNodeAtom);
-     const nodeId = getNodeId(schemaNode, parentNodeId);
-     const originalNodeId = ((_a = schemaNode.originalFragment) === null || _a === void 0 ? void 0 : _a.$ref) ? getOriginalNodeId(schemaNode, parentNodeId) : nodeId;
-     const mode = viewMode === 'standalone' ? undefined : viewMode;
-@@ -797,7 +797,7 @@ const SchemaRow = React__namespace.memo(({ schemaNode, nestingLevel, pl, parentN
-         isCollapsible && isExpanded ? (React__namespace.createElement(ChildStack, { schemaNode: schemaNode, childNodes: childNodes, currentNestingLevel: nestingLevel, parentNodeId: nodeId, parentChangeType: parentChangeType ? parentChangeType : hasChanged ? hasChanged === null || hasChanged === void 0 ? void 0 : hasChanged.type : undefined })) : null));
- });
- const Divider = ({ atom }) => {
--    const isHovering = utils.useAtomValue(atom);
-+    const isHovering = jotai.useAtomValue(atom);
-     return React__namespace.createElement(mosaic.Box, { bg: isHovering ? 'canvas-200' : undefined, h: "px", flex: 1, mx: 3 });
- };
- function shouldShowPropertyName(schemaNode) {
-@@ -897,7 +897,7 @@ const TopLevelSchemaRow = ({ schemaNode, skipDescription, }) => {
- function ScrollCheck() {
-     const elementRef = React__namespace.useRef(null);
-     const isOnScreen = useIsOnScreen(elementRef);
--    const setShowPathCrumbs = utils.useUpdateAtom(showPathCrumbsAtom);
-+    const setShowPathCrumbs = jotai.useSetAtom(showPathCrumbsAtom);
-     React__namespace.useEffect(() => {
-         setShowPathCrumbs(!isOnScreen);
-     }, [isOnScreen, setShowPathCrumbs]);
-@@ -937,7 +937,7 @@ const JsonSchemaViewerComponent = (_a) => {
-                 React__namespace.createElement(JsonSchemaViewerInner, Object.assign({ viewMode: viewMode, skipTopLevelDescription: skipTopLevelDescription }, rest))))));
- };
- const JsonSchemaViewerInner = ({ schema, viewMode, className, resolveRef, maxRefDepth, emptyText = 'No schema defined', onTreePopulated, maxHeight, parentCrumbs, skipTopLevelDescription, }) => {
--    const setHoveredNode = utils.useUpdateAtom(hoveredNodeAtom);
-+    const setHoveredNode = jotai.useSetAtom(hoveredNodeAtom);
-     const onMouseLeave = React__namespace.useCallback(() => {
-         setHoveredNode(null);
-     }, [setHoveredNode]);
-diff --git a/index.mjs b/index.mjs
-index 26cb6e0a5a4141e6438e165a8ef602709c29b39a..caaf68b31ce233fe38f47b46b76bb2b50f968ea5 100644
---- a/index.mjs
-+++ b/index.mjs
-@@ -2,8 +2,8 @@ import { isRegularNode, SchemaNodeKind, isReferenceNode, isRootNode, isBooleanis
- import { Box, HStack, Flex, Icon, Text, Link, Tooltip, NodeAnnotation, VStack, Select, Menu, Pressable, Provider } from '@stoplight/mosaic';
- import { withErrorBoundary } from '@stoplight/react-error-boundary';
- import cn from 'classnames';
--import { atom, useAtom, Provider as Provider$1 } from 'jotai';
--import { atomFamily, useUpdateAtom, useAtomValue } from 'jotai/utils';
-+import { atom, useAtom, Provider as Provider$1, useAtomValue, useSetAtom } from 'jotai';
-+import { atomFamily } from 'jotai/utils';
- import * as React from 'react';
- import { useState, useEffect } from 'react';
- import { isPlainObject, getLastPathSegment, extractPointerFromRef, pointerToPath } from '@stoplight/json';
-@@ -706,7 +706,7 @@ const shouldShowChildSelector = (schemaNode) => { var _a, _b; return isNonEmptyP
- const SchemaRow = React.memo(({ schemaNode, nestingLevel, pl, parentNodeId, parentChangeType }) => {
-     var _a, _b, _c;
-     const { defaultExpandedDepth, renderRowAddon, renderExtensionAddon, onGoToRef, hideExamples, renderRootTreeLines, nodeHasChanged, viewMode, } = useJSVOptionsContext();
--    const setHoveredNode = useUpdateAtom(hoveredNodeAtom);
-+    const setHoveredNode = useSetAtom(hoveredNodeAtom);
-     const nodeId = getNodeId(schemaNode, parentNodeId);
-     const originalNodeId = ((_a = schemaNode.originalFragment) === null || _a === void 0 ? void 0 : _a.$ref) ? getOriginalNodeId(schemaNode, parentNodeId) : nodeId;
-     const mode = viewMode === 'standalone' ? undefined : viewMode;
-@@ -876,7 +876,7 @@ const TopLevelSchemaRow = ({ schemaNode, skipDescription, }) => {
- function ScrollCheck() {
-     const elementRef = React.useRef(null);
-     const isOnScreen = useIsOnScreen(elementRef);
--    const setShowPathCrumbs = useUpdateAtom(showPathCrumbsAtom);
-+    const setShowPathCrumbs = useSetAtom(showPathCrumbsAtom);
-     React.useEffect(() => {
-         setShowPathCrumbs(!isOnScreen);
-     }, [isOnScreen, setShowPathCrumbs]);
-@@ -916,7 +916,7 @@ const JsonSchemaViewerComponent = (_a) => {
-                 React.createElement(JsonSchemaViewerInner, Object.assign({ viewMode: viewMode, skipTopLevelDescription: skipTopLevelDescription }, rest))))));
- };
- const JsonSchemaViewerInner = ({ schema, viewMode, className, resolveRef, maxRefDepth, emptyText = 'No schema defined', onTreePopulated, maxHeight, parentCrumbs, skipTopLevelDescription, }) => {
--    const setHoveredNode = useUpdateAtom(hoveredNodeAtom);
-+    const setHoveredNode = useSetAtom(hoveredNodeAtom);
-     const onMouseLeave = React.useCallback(() => {
-         setHoveredNode(null);
-     }, [setHoveredNode]);
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index a3ec49a24..e4af7964c 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -4,16831 +4,7269 @@ settings:
   autoInstallPeers: true
   excludeLinksFromLockfile: false
 
-patchedDependencies:
-  '@stoplight/json-schema-viewer@4.16.4': 5a7a1068966aaefd9a8a44d9974257213a8072c19733ed2785768c81e87b32c2
-
 importers:
 
   .:
     dependencies:
-      '@docusaurus/core':
-        specifier: 3.10.1
-        version: 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/faster':
-        specifier: 3.10.1
-        version: 3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15)
-      '@docusaurus/plugin-content-docs':
-        specifier: 3.10.1
-        version: 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/preset-classic':
-        specifier: 3.10.1
-        version: 3.10.1(@algolia/client-search@5.53.0)(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(@types/react@19.2.17)(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(search-insights@2.17.3)(typescript@6.0.3)
-      '@docusaurus/remark-plugin-npm2yarn':
-        specifier: 3.10.1
-        version: 3.10.1
-      '@docusaurus/theme-common':
-        specifier: 3.10.1
-        version: 3.10.1(@docusaurus/plugin-content-docs@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/theme-mermaid':
-        specifier: 3.10.1
-        version: 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@docusaurus/plugin-content-docs@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
       '@json-schema-tools/reference-resolver':
         specifier: 1.2.6
         version: 1.2.6
-      '@mdx-js/react':
-        specifier: 3.1.1
-        version: 3.1.1(@types/react@19.2.17)(react@19.2.7)
-      '@open-rpc/meta-schema':
-        specifier: ^1.14.9
-        version: 1.14.9
       '@open-rpc/schema-utils-js':
         specifier: ^2.2.1
         version: 2.2.1
-      '@stellar/open-rpc-docs-react':
-        specifier: ^0.2.1
-        version: 0.2.1(@babel/core@7.29.7)(@babel/template@7.29.7)(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@types/react@19.2.17)(@typescript-eslint/eslint-plugin@7.18.0(@typescript-eslint/parser@7.18.0(eslint@10.6.0(jiti@1.21.7))(typescript@6.0.3))(eslint@10.6.0(jiti@1.21.7))(typescript@6.0.3))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      ajv:
-        specifier: ^8.20.0
-        version: 8.20.0
-      clsx:
-        specifier: ^2.1.1
-        version: 2.1.1
-      docusaurus-markdown-source-plugin:
-        specifier: ^2.2.4
-        version: 2.2.5(@docusaurus/core@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      docusaurus-plugin-openapi-docs:
-        specifier: 5.1.0
-        version: 5.1.0(@docusaurus/plugin-content-docs@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3))(@docusaurus/utils-validation@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@docusaurus/utils@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@types/json-schema@7.0.15)(react@19.2.7)
-      docusaurus-plugin-sass:
-        specifier: ^0.2.6
-        version: 0.2.6(@docusaurus/core@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(sass@1.101.0)(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      docusaurus-plugin-sentry:
-        specifier: ^2.1.0
-        version: 2.1.0(@docusaurus/core@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      docusaurus-theme-openapi-docs:
-        specifier: 5.1.0
-        version: 5.1.0(722036656f7e1999e1a6989345bc7722)
       fs-extra:
         specifier: ^11.3.6
         version: 11.3.6
       json-schema-merge-allof:
         specifier: ^0.8.1
         version: 0.8.1
-      prism-react-renderer:
-        specifier: ^2.4.1
-        version: 2.4.1(react@19.2.7)
-      react:
-        specifier: ^19.2.7
-        version: 19.2.7
-      react-dom:
-        specifier: ^19.2.7
-        version: 19.2.7(react@19.2.7)
-      rehype-katex:
-        specifier: ^7.0.1
-        version: 7.0.1
-      remark-math:
-        specifier: ^6.0.0
-        version: 6.0.0
-      sass:
-        specifier: ^1.101.0
-        version: 1.101.0
       yargs:
         specifier: ^18.0.0
         version: 18.0.0
     devDependencies:
-      '@docusaurus/eslint-plugin':
-        specifier: 3.10.1
-        version: 3.10.1(eslint@10.6.0(jiti@1.21.7))(typescript@6.0.3)
-      '@docusaurus/module-type-aliases':
-        specifier: 3.10.1
-        version: 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/tsconfig':
-        specifier: 3.10.1
-        version: 3.10.1
-      '@docusaurus/types':
-        specifier: 3.10.1
-        version: 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@eslint/eslintrc':
-        specifier: ^3.3.5
-        version: 3.3.5
-      '@eslint/js':
-        specifier: ^10.0.1
-        version: 10.0.1(eslint@10.6.0(jiti@1.21.7))
       '@redocly/cli':
         specifier: ^2.38.0
         version: 2.38.0
       '@stellar/prettier-config':
         specifier: ^1.2.0
         version: 1.2.0(prettier@3.9.4)
-      '@types/react':
-        specifier: ^19.2.17
-        version: 19.2.17
-      docusaurus-plugin-llms:
-        specifier: ^0.4.0
-        version: 0.4.0(@docusaurus/core@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3))
-      eslint:
-        specifier: ^10.6.0
-        version: 10.6.0(jiti@1.21.7)
-      glob:
-        specifier: ^13.0.6
-        version: 13.0.6
       husky:
         specifier: ^9.1.7
         version: 9.1.7
+      mint:
+        specifier: ^4.2.1062
+        version: 4.2.1062(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/node@26.6.5)(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(typescript@6.0.3)
       prettier:
         specifier: ^3.9.4
         version: 3.9.4
-      typescript:
-        specifier: ^6.0.3
-        version: 6.0.3
 
 packages:
 
-  '@adobe/react-spectrum-ui@1.2.1':
-    resolution: {integrity: sha512-wcrbEE2O/9WnEn6avBnaVRRx88S5PLFsPLr4wffzlbMfXeQsy+RMQwaJd3cbzrn18/j04Isit7f7Emfn0dhrJA==}
-    peerDependencies:
-      react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
-      react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
+  '@alcalzone/ansi-tokenize@0.2.5':
+    resolution: {integrity: sha512-3NX/MpTdroi0aKz134A6RC2Gb2iXVECN4QaAXnvCIxxIm3C3AVB1mkUe8NaaiyvOpDfsrqWhYtj+Q6a62RrTsw==}
+    engines: {node: '>=18'}
 
-  '@adobe/react-spectrum-workflow@2.3.5':
-    resolution: {integrity: sha512-b53VIPwPWKb/T5gzE3qs+QlGP5gVrw/LnWV3xMksDU+CRl3rzOKUwxIGiZO8ICyYh1WiyqY4myGlPU/nAynBUg==}
-    peerDependencies:
-      react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
-      react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
+  '@alloc/quick-lru@5.3.0':
+    resolution: {integrity: sha512-U4+70Pc5ZS9osnCBCE5Jha/ciHM+Yp+CNMNC/7HvYbNRk1Ldd+f7qO65W5qfhu/TCv+/ozljlXXe9Nj8419DMA==}
+    engines: {node: '>=10'}
 
-  '@adobe/react-spectrum@3.47.1':
-    resolution: {integrity: sha512-mijNyd8XmA6KoBMbqKc4Rp+S2voKdZkPydJFjQbG0SkOjOKcgqVpJdKGsKdLMZBn9Jk5SgEuklyrhc7Uvot2tA==}
-    peerDependencies:
-      react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
-      react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
+  '@ark/schema@0.56.7':
+    resolution: {integrity: sha512-jmoOJlYIc4k1uv8oYBDNOFnAsKk2a2D9t/D6npF2JUfW4ecPB0v6ce6lruKg7lkBxIBA8Z7UtxfmvephYbhUGQ==}
 
-  '@adobe/react-spectrum@3.47.3':
-    resolution: {integrity: sha512-tWZG59+xTbXIqeZB4uyuo2qljk3nRK66IkdBmMgbl2p6peApkKbrtJ/YOM8rW4gemdmv7qoJlbIHvy8aJkYsCQ==}
-    peerDependencies:
-      react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
-      react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
+  '@ark/util@0.56.7':
+    resolution: {integrity: sha512-z8pVnrPk/x9GC18yOp5wCe8rR2+Z6us4CTSg7dvxdsDLuA2xXYq+QETD1fO6f3fMuXe+PCjpvtCnhTW9RHLgEw==}
 
-  '@algolia/abtesting@1.19.0':
-    resolution: {integrity: sha512-Lhnez3hhXHk25lfxLAMxvkP4fmN3+1RgADhD2ssMDBYuAsDVReeyP+3SGRx+ntq8ijMrLqUyfvO72TB6jsTteQ==}
-    engines: {node: '>= 14.0.0'}
+  '@asyncapi/parser@3.4.0':
+    resolution: {integrity: sha512-Sxn74oHiZSU6+cVeZy62iPZMFMvKp4jupMFHelSICCMw1qELmUHPvuZSr+ZHDmNGgHcEpzJM5HN02kR7T4g+PQ==}
 
-  '@algolia/autocomplete-core@1.19.2':
-    resolution: {integrity: sha512-mKv7RyuAzXvwmq+0XRK8HqZXt9iZ5Kkm2huLjgn5JoCPtDy+oh9yxUMfDDaVCw0oyzZ1isdJBc7l9nuCyyR7Nw==}
+  '@asyncapi/specs@6.11.1':
+    resolution: {integrity: sha512-A3WBLqAKGoJ2+6FWFtpjBlCQ1oFCcs4GxF7zsIGvNqp/klGUHjlA3aAcZ9XMMpLGE8zPeYDz2x9FmO6DSuKraQ==}
 
-  '@algolia/autocomplete-plugin-algolia-insights@1.19.2':
-    resolution: {integrity: sha512-TjxbcC/r4vwmnZaPwrHtkXNeqvlpdyR+oR9Wi2XyfORkiGkLTVhX2j+O9SaCCINbKoDfc+c2PB8NjfOnz7+oKg==}
-    peerDependencies:
-      search-insights: '>= 1 < 3'
+  '@babel/code-frame@7.29.7':
+    resolution: {integrity: sha512-Aup7aUOfpbAUg2ROOJN6Iw5f9DMBlzu0mIkm/malLQFN/YQgO48wCj0Kxa3sEHJvPVFg7siR+qRInwXd2qhQKw==}
+    engines: {node: '>=6.9.0'}
+
+  '@babel/helper-validator-identifier@7.29.7':
+    resolution: {integrity: sha512-qehxGkRj55h/ff8EMaJ+cYhyaKlHIxqYDn682wQD7RNp9UujOQsHog2uS0r2vzr4pW+sXf90NeeayjcNaX3fFg==}
+    engines: {node: '>=6.9.0'}
 
-  '@algolia/autocomplete-shared@1.19.2':
-    resolution: {integrity: sha512-jEazxZTVD2nLrC+wYlVHQgpBoBB5KPStrJxLzsIFl6Kqd1AlG9sIAGl39V5tECLpIQzB3Qa2T6ZPJ1ChkwMK/w==}
+  '@babel/runtime@8.0.7':
+    resolution: {integrity: sha512-k0hagDDq/6w4v+0Sp4wFvIz/yswH5O7Va6aRTnD7N62Tnborp4X+YB+H3XUcWVSR4aE47WPEXiIIZchBs0GmYg==}
+
+  '@base-ui/react@1.9.0':
+    resolution: {integrity: sha512-S8CSYosASBKtpL8SWUfS78rFElfLijiCgA7oHOK22jCJ95FULsYyKwBNFOgudt0RA+/7yNc7F81bOvQnRgbBiQ==}
+    engines: {node: '>=14.0.0'}
     peerDependencies:
-      '@algolia/client-search': '>= 4.9.1 < 6'
-      algoliasearch: '>= 4.9.1 < 6'
+      '@date-fns/tz': ^1.2.0
+      '@types/react': ^17 || ^18 || ^19
+      date-fns: ^4.0.0
+      react: ^17 || ^18 || ^19
+      react-dom: ^17 || ^18 || ^19
+    peerDependenciesMeta:
+      '@date-fns/tz':
+        optional: true
+      '@types/react':
+        optional: true
+      date-fns:
+        optional: true
 
-  '@algolia/client-abtesting@5.53.0':
-    resolution: {integrity: sha512-0ZjA5Hcmaoz5Lj6OG0zhfIyeqzJZnLW2CRJA1W17UwMFGRtZAJ9yJKRvPEDA6gkpsIoQxORTSW6sWFiuYncPNQ==}
-    engines: {node: '>= 14.0.0'}
+  '@base-ui/utils@0.5.0':
+    resolution: {integrity: sha512-dYGGcEttjkYiMoa5nHm8vLaJ2UcuTWxo3BFAwOYXeRg/q7UVVvA6cacEIXEs3FgBfK1CGtW1ptElqs7wsx+t9A==}
+    peerDependencies:
+      '@types/react': ^17 || ^18 || ^19
+      react: ^17 || ^18 || ^19
+      react-dom: ^17 || ^18 || ^19
+    peerDependenciesMeta:
+      '@types/react':
+        optional: true
 
-  '@algolia/client-analytics@5.53.0':
-    resolution: {integrity: sha512-kWNodP75iiEaOtemC9F/hlxNBG5E2QUjN1BusnE6m2b4l7Qh/BUO3fGCVsmKJI65VO4VKGGmT43ICvHtTcJ2JQ==}
-    engines: {node: '>= 14.0.0'}
+  '@canvas/image-data@1.1.0':
+    resolution: {integrity: sha512-QdObRRjRbcXGmM1tmJ+MrHcaz1MftF2+W7YI+MsphnsCrmtyfS0d5qJbk0MeSbUeyM/jCb0hmnkXPsy026L7dA==}
 
-  '@algolia/client-common@5.53.0':
-    resolution: {integrity: sha512-YPN45TXD9Wrse185t/Ta7nktZsqpv97oOjCzp2sblHnCL6rBc9TDeJAg1IGl2UpdwnSD05Zu/5wLB4watOUMyg==}
-    engines: {node: '>= 14.0.0'}
+  '@emnapi/runtime@1.11.3':
+    resolution: {integrity: sha512-Xz4Tpyki7XyrpbUK1jR1AhdAdaXyhhY4lZ3neLodmhpuWfy2PAQN5B46sAiU4liOXGLkHypn/qU+jvfWSCYYLA==}
 
-  '@algolia/client-insights@5.53.0':
-    resolution: {integrity: sha512-qAcYTDJE6m924FDDUQvdD6vh7DYaqOeSpFS74IP37/JRV0v4cGBauyxTF2WzDnokUylQDbqreoFIJZfg0Fitmw==}
-    engines: {node: '>= 14.0.0'}
+  '@esbuild/aix-ppc64@0.25.12':
+    resolution: {integrity: sha512-Hhmwd6CInZ3dwpuGTF8fJG6yoWmsToE+vYgD4nytZVxcu1ulHpUQRAB1UJ8+N1Am3Mz4+xOByoQoSZf4D+CpkA==}
+    engines: {node: '>=18'}
+    cpu: [ppc64]
+    os: [aix]
 
-  '@algolia/client-personalization@5.53.0':
-    resolution: {integrity: sha512-fQaY+DkSJOpuUVUe8MQTwrdiKAqkJGhpDarB08duBn/sUv7Bkib6MDRQauCcWTWTe4HIW+EbwQP9R4kci1V/Yw==}
-    engines: {node: '>= 14.0.0'}
+  '@esbuild/android-arm64@0.25.12':
+    resolution: {integrity: sha512-6AAmLG7zwD1Z159jCKPvAxZd4y/VTO0VkprYy+3N2FtJ8+BQWFXU+OxARIwA46c5tdD9SsKGZ/1ocqBS/gAKHg==}
+    engines: {node: '>=18'}
+    cpu: [arm64]
+    os: [android]
 
-  '@algolia/client-query-suggestions@5.53.0':
-    resolution: {integrity: sha512-o72tsiEZGfeS/dxL9IADfzcZWGEwKDEe5CvtrBuT//3JR+SHuTtHRI2ZTf7D7bcKagcbojvO8hnkHdfoakSlYg==}
-    engines: {node: '>= 14.0.0'}
+  '@esbuild/android-arm@0.25.12':
+    resolution: {integrity: sha512-VJ+sKvNA/GE7Ccacc9Cha7bpS8nyzVv0jdVgwNDaR4gDMC/2TTRc33Ip8qrNYUcpkOHUT5OZ0bUcNNVZQ9RLlg==}
+    engines: {node: '>=18'}
+    cpu: [arm]
+    os: [android]
 
-  '@algolia/client-search@5.53.0':
-    resolution: {integrity: sha512-Ds16IyPm/dNJPCU8OzApo2gwGrgWT5BYHhE3NFwZbpCveqyvPDB9sZDDkJ5DsdOGT2aC+R3i0/M1OVXF2qdgPg==}
-    engines: {node: '>= 14.0.0'}
+  '@esbuild/android-x64@0.25.12':
+    resolution: {integrity: sha512-5jbb+2hhDHx5phYR2By8GTWEzn6I9UqR11Kwf22iKbNpYrsmRB18aX/9ivc5cabcUiAT/wM+YIZ6SG9QO6a8kg==}
+    engines: {node: '>=18'}
+    cpu: [x64]
+    os: [android]
 
-  '@algolia/events@4.0.1':
-    resolution: {integrity: sha512-FQzvOCgoFXAbf5Y6mYozw2aj5KCJoA3m4heImceldzPSMbdyS4atVjJzXKMsfX3wnZTFYwkkt8/z8UesLHlSBQ==}
+  '@esbuild/darwin-arm64@0.25.12':
+    resolution: {integrity: sha512-N3zl+lxHCifgIlcMUP5016ESkeQjLj/959RxxNYIthIg+CQHInujFuXeWbWMgnTo4cp5XVHqFPmpyu9J65C1Yg==}
+    engines: {node: '>=18'}
+    cpu: [arm64]
+    os: [darwin]
 
-  '@algolia/ingestion@1.53.0':
-    resolution: {integrity: sha512-oNbT6z4NwD8Pou9VPINGlN/tlG1afESh2EbxqnP6rwl95xKVD/Zlciis1PpNeO/9U/rrajc1+7DcfKi03tX1KQ==}
-    engines: {node: '>= 14.0.0'}
+  '@esbuild/darwin-x64@0.25.12':
+    resolution: {integrity: sha512-HQ9ka4Kx21qHXwtlTUVbKJOAnmG1ipXhdWTmNXiPzPfWKpXqASVcWdnf2bnL73wgjNrFXAa3yYvBSd9pzfEIpA==}
+    engines: {node: '>=18'}
+    cpu: [x64]
+    os: [darwin]
 
-  '@algolia/monitoring@1.53.0':
-    resolution: {integrity: sha512-G+KZb/yd+qAOFn/cEvTGeLxQm8aP3a0od50l3z/ylccY+/o4YG3TNcjU1tFQHW4mXC137GPyR7W70R0kRQDLnA==}
-    engines: {node: '>= 14.0.0'}
+  '@esbuild/freebsd-arm64@0.25.12':
+    resolution: {integrity: sha512-gA0Bx759+7Jve03K1S0vkOu5Lg/85dou3EseOGUes8flVOGxbhDDh/iZaoek11Y8mtyKPGF3vP8XhnkDEAmzeg==}
+    engines: {node: '>=18'}
+    cpu: [arm64]
+    os: [freebsd]
 
-  '@algolia/recommend@5.53.0':
-    resolution: {integrity: sha512-6aVfYd55Un6IUgPLbo84WfgFZlS3L0vA1ttzXL5vahHewUJ8jYgd89TzlWRTeej7w70mb9RWsVlFYGmJ/diQww==}
-    engines: {node: '>= 14.0.0'}
+  '@esbuild/freebsd-x64@0.25.12':
+    resolution: {integrity: sha512-TGbO26Yw2xsHzxtbVFGEXBFH0FRAP7gtcPE7P5yP7wGy7cXK2oO7RyOhL5NLiqTlBh47XhmIUXuGciXEqYFfBQ==}
+    engines: {node: '>=18'}
+    cpu: [x64]
+    os: [freebsd]
 
-  '@algolia/requester-browser-xhr@5.53.0':
-    resolution: {integrity: sha512-ke27DqgzCOlt+RbeEdCxtXxMQOnAOi8ujr2wid0DmDKzR95Kw/f9sBsuhBxtjevCqJRJszfRTLY0B1pbO6IhkA==}
-    engines: {node: '>= 14.0.0'}
+  '@esbuild/linux-arm64@0.25.12':
+    resolution: {integrity: sha512-8bwX7a8FghIgrupcxb4aUmYDLp8pX06rGh5HqDT7bB+8Rdells6mHvrFHHW2JAOPZUbnjUpKTLg6ECyzvas2AQ==}
+    engines: {node: '>=18'}
+    cpu: [arm64]
+    os: [linux]
 
-  '@algolia/requester-fetch@5.53.0':
-    resolution: {integrity: sha512-GngiOqt2Gq4oLno6yXQVj9om+qSO9SWAoduoTOEg79dKZ62brB8OOIvSJG/vDNoanYi6a7Al9uDZwXvi+bcVTg==}
-    engines: {node: '>= 14.0.0'}
+  '@esbuild/linux-arm@0.25.12':
+    resolution: {integrity: sha512-lPDGyC1JPDou8kGcywY0YILzWlhhnRjdof3UlcoqYmS9El818LLfJJc3PXXgZHrHCAKs/Z2SeZtDJr5MrkxtOw==}
+    engines: {node: '>=18'}
+    cpu: [arm]
+    os: [linux]
 
-  '@algolia/requester-node-http@5.53.0':
-    resolution: {integrity: sha512-6mF9LZMUk0QqWvrnxkxBqhswwz6Xfiwy6/gmTzL5HrlhdVG3ITAqGV2k3XmVThP1h0Ulc3VQwiNCD7/Nr4JNlQ==}
-    engines: {node: '>= 14.0.0'}
+  '@esbuild/linux-ia32@0.25.12':
+    resolution: {integrity: sha512-0y9KrdVnbMM2/vG8KfU0byhUN+EFCny9+8g202gYqSSVMonbsCfLjUO+rCci7pM0WBEtz+oK/PIwHkzxkyharA==}
+    engines: {node: '>=18'}
+    cpu: [ia32]
+    os: [linux]
 
-  '@antfu/install-pkg@1.1.0':
-    resolution: {integrity: sha512-MGQsmw10ZyI+EJo45CdSER4zEb+p31LpDAFp2Z3gkSd1yqVZGi0Ebx++YTEMonJy4oChEMLsxZ64j8FH6sSqtQ==}
+  '@esbuild/linux-loong64@0.25.12':
+    resolution: {integrity: sha512-h///Lr5a9rib/v1GGqXVGzjL4TMvVTv+s1DPoxQdz7l/AYv6LDSxdIwzxkrPW438oUXiDtwM10o9PmwS/6Z0Ng==}
+    engines: {node: '>=18'}
+    cpu: [loong64]
+    os: [linux]
 
-  '@apidevtools/json-schema-ref-parser@15.4.0':
-    resolution: {integrity: sha512-QbMJJlMZd27fZmi7Q+twCqwABlfaO4Qdc1YvbbwkqN2lILfELnfWfw9xFFl6CeF5jAeGQpokUVhvCkhz+rvEGg==}
-    engines: {node: '>=20'}
-    peerDependencies:
-      '@types/json-schema': ^7.0.15
+  '@esbuild/linux-mips64el@0.25.12':
+    resolution: {integrity: sha512-iyRrM1Pzy9GFMDLsXn1iHUm18nhKnNMWscjmp4+hpafcZjrr2WbT//d20xaGljXDBYHqRcl8HnxbX6uaA/eGVw==}
+    engines: {node: '>=18'}
+    cpu: [mips64el]
+    os: [linux]
 
-  '@babel/code-frame@7.29.7':
-    resolution: {integrity: sha512-Aup7aUOfpbAUg2ROOJN6Iw5f9DMBlzu0mIkm/malLQFN/YQgO48wCj0Kxa3sEHJvPVFg7siR+qRInwXd2qhQKw==}
-    engines: {node: '>=6.9.0'}
+  '@esbuild/linux-ppc64@0.25.12':
+    resolution: {integrity: sha512-9meM/lRXxMi5PSUqEXRCtVjEZBGwB7P/D4yT8UG/mwIdze2aV4Vo6U5gD3+RsoHXKkHCfSxZKzmDssVlRj1QQA==}
+    engines: {node: '>=18'}
+    cpu: [ppc64]
+    os: [linux]
 
-  '@babel/compat-data@7.29.7':
-    resolution: {integrity: sha512-locTkQyKvwIEgBzVrn8693ebc97F2U8ZHjbXwDXJ5Fn2TCpNwTlKcaKLkdHop5c/icOFE7qt7Q9JC5hnKNa6Gg==}
-    engines: {node: '>=6.9.0'}
+  '@esbuild/linux-riscv64@0.25.12':
+    resolution: {integrity: sha512-Zr7KR4hgKUpWAwb1f3o5ygT04MzqVrGEGXGLnj15YQDJErYu/BGg+wmFlIDOdJp0PmB0lLvxFIOXZgFRrdjR0w==}
+    engines: {node: '>=18'}
+    cpu: [riscv64]
+    os: [linux]
 
-  '@babel/core@7.29.7':
-    resolution: {integrity: sha512-RgHBCvtjbOK2gXSNBNIkNoEc9qoVEtau3hj8gEqKQuL3HZAibKarWFEI3Lfm6EYKkLalOh8eSrj9b+ch9H/VBA==}
-    engines: {node: '>=6.9.0'}
+  '@esbuild/linux-s390x@0.25.12':
+    resolution: {integrity: sha512-MsKncOcgTNvdtiISc/jZs/Zf8d0cl/t3gYWX8J9ubBnVOwlk65UIEEvgBORTiljloIWnBzLs4qhzPkJcitIzIg==}
+    engines: {node: '>=18'}
+    cpu: [s390x]
+    os: [linux]
 
-  '@babel/generator@7.29.7':
-    resolution: {integrity: sha512-DkXD5OJQaAQIdZ1bt3UZdEnHAn9Imd3IVBdX03UFe+ony9Ojw5pzr9YVKGDY1jt+Gcn/FnGkNf8r+Vj5NOJWtQ==}
-    engines: {node: '>=6.9.0'}
+  '@esbuild/linux-x64@0.25.12':
+    resolution: {integrity: sha512-uqZMTLr/zR/ed4jIGnwSLkaHmPjOjJvnm6TVVitAa08SLS9Z0VM8wIRx7gWbJB5/J54YuIMInDquWyYvQLZkgw==}
+    engines: {node: '>=18'}
+    cpu: [x64]
+    os: [linux]
 
-  '@babel/helper-annotate-as-pure@7.29.7':
-    resolution: {integrity: sha512-OoK6239jHPuSQOoS0kfTVKn0b/rVTk0seKq4Gd2UMLtmOVLjDC0ki3e+c90Trqv2gMfvJFqkiljrr568+qddiw==}
-    engines: {node: '>=6.9.0'}
+  '@esbuild/netbsd-arm64@0.25.12':
+    resolution: {integrity: sha512-xXwcTq4GhRM7J9A8Gv5boanHhRa/Q9KLVmcyXHCTaM4wKfIpWkdXiMog/KsnxzJ0A1+nD+zoecuzqPmCRyBGjg==}
+    engines: {node: '>=18'}
+    cpu: [arm64]
+    os: [netbsd]
 
-  '@babel/helper-compilation-targets@7.29.7':
-    resolution: {integrity: sha512-wem6WaBj4NaVYVdNhLPPVacES6ZJ+KBBfSkTMD3YZxbP3rm3Di85tJU5ljaUNhaOynt+Aj0xruhYuzQBt8n71g==}
-    engines: {node: '>=6.9.0'}
+  '@esbuild/netbsd-x64@0.25.12':
+    resolution: {integrity: sha512-Ld5pTlzPy3YwGec4OuHh1aCVCRvOXdH8DgRjfDy/oumVovmuSzWfnSJg+VtakB9Cm0gxNO9BzWkj6mtO1FMXkQ==}
+    engines: {node: '>=18'}
+    cpu: [x64]
+    os: [netbsd]
 
-  '@babel/helper-create-class-features-plugin@7.29.7':
-    resolution: {integrity: sha512-IY3ZD9Tmooqr3TUhc3DUWxiuo8xx1DWLhd5M7hQ+ZWJamqM2BbalrBJb2MisSLoYorOj75U03qULCxQTY9r3hg==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0
+  '@esbuild/openbsd-arm64@0.25.12':
+    resolution: {integrity: sha512-fF96T6KsBo/pkQI950FARU9apGNTSlZGsv1jZBAlcLL1MLjLNIWPBkj5NlSz8aAzYKg+eNqknrUJ24QBybeR5A==}
+    engines: {node: '>=18'}
+    cpu: [arm64]
+    os: [openbsd]
 
-  '@babel/helper-create-regexp-features-plugin@7.29.7':
-    resolution: {integrity: sha512-907Uymvqgg1dwUA+7IGwFAOSYzQOuzPXKNJ1yxzwPffzkYFg2q2eHi1fIOs6sXkG9NbIUMunnUlkYsfRFNvomg==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0
+  '@esbuild/openbsd-x64@0.25.12':
+    resolution: {integrity: sha512-MZyXUkZHjQxUvzK7rN8DJ3SRmrVrke8ZyRusHlP+kuwqTcfWLyqMOE3sScPPyeIXN/mDJIfGXvcMqCgYKekoQw==}
+    engines: {node: '>=18'}
+    cpu: [x64]
+    os: [openbsd]
 
-  '@babel/helper-define-polyfill-provider@0.6.8':
-    resolution: {integrity: sha512-47UwBLPpQi1NoWzLuHNjRoHlYXMwIJoBf7MFou6viC/sIHWYygpvr0B6IAyh5sBdA2nr2LPIRww8lfaUVQINBA==}
-    peerDependencies:
-      '@babel/core': ^7.4.0 || ^8.0.0-0 <8.0.0
+  '@esbuild/openharmony-arm64@0.25.12':
+    resolution: {integrity: sha512-rm0YWsqUSRrjncSXGA7Zv78Nbnw4XL6/dzr20cyrQf7ZmRcsovpcRBdhD43Nuk3y7XIoW2OxMVvwuRvk9XdASg==}
+    engines: {node: '>=18'}
+    cpu: [arm64]
+    os: [openharmony]
 
-  '@babel/helper-globals@7.29.7':
-    resolution: {integrity: sha512-3nQVUAtvkKH9zahfWgw96Jc/uFOmjACE1kQz82E2lqWmHBgjzbNlsC22nuQTfahmWeQtTq5nQ/4Nnd2A1wj4zA==}
-    engines: {node: '>=6.9.0'}
+  '@esbuild/sunos-x64@0.25.12':
+    resolution: {integrity: sha512-3wGSCDyuTHQUzt0nV7bocDy72r2lI33QL3gkDNGkod22EsYl04sMf0qLb8luNKTOmgF/eDEDP5BFNwoBKH441w==}
+    engines: {node: '>=18'}
+    cpu: [x64]
+    os: [sunos]
 
-  '@babel/helper-member-expression-to-functions@7.29.7':
-    resolution: {integrity: sha512-j+7JYmk1JYDtACIGj0QJqqWZjoUpMoEikQGADMaHgCMCSDqd2+P32rfcibUNrGOMWrlzK1WJBdxrB3JJQZwWtg==}
-    engines: {node: '>=6.9.0'}
+  '@esbuild/win32-arm64@0.25.12':
+    resolution: {integrity: sha512-rMmLrur64A7+DKlnSuwqUdRKyd3UE7oPJZmnljqEptesKM8wx9J8gx5u0+9Pq0fQQW8vqeKebwNXdfOyP+8Bsg==}
+    engines: {node: '>=18'}
+    cpu: [arm64]
+    os: [win32]
 
-  '@babel/helper-module-imports@7.29.7':
-    resolution: {integrity: sha512-ejHwrQQYcm9xnTivShn2IDOlIzInN34AXskvq9QicvCtEzq1Vzclu/tKF8Jq1Cg8JG2GL6/EmjgsCT7lXepE3g==}
-    engines: {node: '>=6.9.0'}
+  '@esbuild/win32-ia32@0.25.12':
+    resolution: {integrity: sha512-HkqnmmBoCbCwxUKKNPBixiWDGCpQGVsrQfJoVGYLPT41XWF8lHuE5N6WhVia2n4o5QK5M4tYr21827fNhi4byQ==}
+    engines: {node: '>=18'}
+    cpu: [ia32]
+    os: [win32]
 
-  '@babel/helper-module-transforms@7.29.7':
-    resolution: {integrity: sha512-UPUVSyXbOh627KiCIGQSgwWzGeBKLkaJ9PJEdrngIwMSzxLR4jS4+f1f1jb7VzBbg8nFLaYotvVPFCTqdrmTAg==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0
+  '@esbuild/win32-x64@0.25.12':
+    resolution: {integrity: sha512-alJC0uCZpTFrSL0CCDjcgleBXPnCrEAhTBILpeAp7M/OFgoqtAetfBzX0xM00MUsVVPpVjlPuMbREqnZCXaTnA==}
+    engines: {node: '>=18'}
+    cpu: [x64]
+    os: [win32]
 
-  '@babel/helper-optimise-call-expression@7.29.7':
-    resolution: {integrity: sha512-+kmGVjcT9RGYzoDwdwEqEvGgKe3BYq+O1iGzjFubaNgZHwYHP6lsF2Yghf4kEuv9BV7tYDZ913aBW9am6YKong==}
-    engines: {node: '>=6.9.0'}
+  '@floating-ui/core@1.8.0':
+    resolution: {integrity: sha512-0CIZ5itps/8x7BG8dEIhs53BvCUH2PCoogtakwRTut+Arm58sJooJ0AuZhLw2HJYIR5cMLNPBSS728sPho2khQ==}
 
-  '@babel/helper-plugin-utils@7.29.7':
-    resolution: {integrity: sha512-G7sHYigPY17oO5SYWnfD/0MTBwVR781S/JI643e/JhUYgVgWE/61SoW3NH9KWUKyKq5LVh3npif99Wkt6j86Jw==}
-    engines: {node: '>=6.9.0'}
+  '@floating-ui/dom@1.8.0':
+    resolution: {integrity: sha512-yXSrzeHZBTZadLOlfyhCkJHNeLJnHRnRInwdZ40L7ZiaAtrBwoYlsDrX3v5zB1Utk7CLfzcOVnVVWoXEky7Ceg==}
 
-  '@babel/helper-remap-async-to-generator@7.29.7':
-    resolution: {integrity: sha512-16AMiW26DbXWBbr3B8wNozKM0ydMLB892vaOaJW/fPJdnT8vJk5sdkQcU/isqUxyCE0cEoa8wZOcbgDuC4b6Og==}
-    engines: {node: '>=6.9.0'}
+  '@floating-ui/react-dom@2.1.9':
+    resolution: {integrity: sha512-JDjEFGCpImxDCA7JJKviA0M9+RtmJdj0m/NVU5IMgBK+AmZouAQQ7/+2GLH0GXXY0YMw9oXPB8hKdbPYg5QLYg==}
     peerDependencies:
-      '@babel/core': ^7.0.0
+      react: '>=16.8.0'
+      react-dom: '>=16.8.0'
 
-  '@babel/helper-replace-supers@7.29.7':
-    resolution: {integrity: sha512-atfGXWSeCiF4DnKZIfmJfQRkSw9b9gNNXR1kqKjbhG4pGYCOnkp8OcTB8E3NXjBu8NpheSnOeNKz8KT7UNFTmQ==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0
+  '@floating-ui/utils@0.2.12':
+    resolution: {integrity: sha512-HpCo8tmWzLVad5s2d19EhAz5zqrrQ6s69qd6moPMQvkOuSwDT1YgRfWSVuc4ennqrgv3OHppiOGMQ7oC13yIww==}
 
-  '@babel/helper-skip-transparent-expression-wrappers@7.29.7':
-    resolution: {integrity: sha512-brcMGQaVzIeUb+6/bs1Av0f8YuNNjKY2JyvfRCsFuFsdKccEQ5Ges2y74D74NZ1Rz8lKJ9ksJkfqwQFJ/iNEyQ==}
-    engines: {node: '>=6.9.0'}
+  '@img/sharp-darwin-arm64@0.33.5':
+    resolution: {integrity: sha512-UT4p+iz/2H4twwAoLCqfA9UH5pI6DggwKEGuaPy7nCVQ8ZsiY5PIcrRvD1DzuY3qYL07NtIQcWnBSY/heikIFQ==}
+    engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
+    cpu: [arm64]
+    os: [darwin]
 
-  '@babel/helper-string-parser@7.29.7':
-    resolution: {integrity: sha512-Pb5ijPrZ89GDH8223L4UP8i6QApWxs04RbPQJTeWDV0/keR2E36MeKnyr6LYmUUvqRRI+Iv87SuF1W6ErINzYw==}
-    engines: {node: '>=6.9.0'}
+  '@img/sharp-darwin-x64@0.33.5':
+    resolution: {integrity: sha512-fyHac4jIc1ANYGRDxtiqelIbdWkIuQaI84Mv45KvGRRxSAa7o7d1ZKAOBaYbnepLC1WqxfpimdeWfvqqSGwR2Q==}
+    engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
+    cpu: [x64]
+    os: [darwin]
 
-  '@babel/helper-validator-identifier@7.29.7':
-    resolution: {integrity: sha512-qehxGkRj55h/ff8EMaJ+cYhyaKlHIxqYDn682wQD7RNp9UujOQsHog2uS0r2vzr4pW+sXf90NeeayjcNaX3fFg==}
-    engines: {node: '>=6.9.0'}
+  '@img/sharp-libvips-darwin-arm64@1.0.4':
+    resolution: {integrity: sha512-XblONe153h0O2zuFfTAbQYAX2JhYmDHeWikp1LM9Hul9gVPjFY427k6dFEcOL72O01QxQsWi761svJ/ev9xEDg==}
+    cpu: [arm64]
+    os: [darwin]
 
-  '@babel/helper-validator-option@7.29.7':
-    resolution: {integrity: sha512-N9ZErrD+yW5geCDtBqnOoxmR8+tNKiGuxKlDpuJxfsqpa2dFcexaziGAE/qoHLiDDreVNMupxGmSoNlyvsA3gw==}
-    engines: {node: '>=6.9.0'}
+  '@img/sharp-libvips-darwin-x64@1.0.4':
+    resolution: {integrity: sha512-xnGR8YuZYfJGmWPvmlunFaWJsb9T/AO2ykoP3Fz/0X5XV2aoYBPkX6xqCQvUTKKiLddarLaxpzNe+b1hjeWHAQ==}
+    cpu: [x64]
+    os: [darwin]
 
-  '@babel/helper-wrap-function@7.29.7':
-    resolution: {integrity: sha512-iES0Skag9ERIF68aXadpO6dbXa03mNWK3sEqJaMnLNs/eC3l0lkImdfoy6Y09/SfkpawdAB4RjQ7PVA7TcVGdw==}
-    engines: {node: '>=6.9.0'}
+  '@img/sharp-libvips-linux-arm64@1.0.4':
+    resolution: {integrity: sha512-9B+taZ8DlyyqzZQnoeIvDVR/2F4EbMepXMc/NdVbkzsJbzkUjhXv/70GQJ7tdLA4YJgNP25zukcxpX2/SueNrA==}
+    cpu: [arm64]
+    os: [linux]
+    libc: [glibc]
 
-  '@babel/helpers@7.29.7':
-    resolution: {integrity: sha512-1k2lAGRMfHTcwuNYcCNUmaUffmQv8KWMfh2iJUUeRlwlwH4FdNG7mfPI10NPfLHJFThE4Tyr4mv7kTNZOiPuBg==}
-    engines: {node: '>=6.9.0'}
+  '@img/sharp-libvips-linux-arm@1.0.5':
+    resolution: {integrity: sha512-gvcC4ACAOPRNATg/ov8/MnbxFDJqf/pDePbBnuBDcjsI8PssmjoKMAz4LtLaVi+OnSb5FK/yIOamqDwGmXW32g==}
+    cpu: [arm]
+    os: [linux]
+    libc: [glibc]
 
-  '@babel/parser@7.29.7':
-    resolution: {integrity: sha512-hnORnjP/1P/zFEndoeX+n+t1RwWRJiJpM/jO7FW32Kn9r5+sJB2JWOdYo4L6k78j15eCwY3Gm/7364B1EMwtNg==}
-    engines: {node: '>=6.0.0'}
-    hasBin: true
+  '@img/sharp-libvips-linux-s390x@1.0.4':
+    resolution: {integrity: sha512-u7Wz6ntiSSgGSGcjZ55im6uvTrOxSIS8/dgoVMoiGE9I6JAfU50yH5BoDlYA1tcuGS7g/QNtetJnxA6QEsCVTA==}
+    cpu: [s390x]
+    os: [linux]
+    libc: [glibc]
 
-  '@babel/plugin-bugfix-firefox-class-in-computed-class-key@7.29.7':
-    resolution: {integrity: sha512-j8SrR0zLZrRsC09DlszEx8FpMiwukKffYXMK0d5LmOglO7vGG6sz/BR/20yHqWH+Lnn31JTt2PE3hIWNgM2J6w==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0
+  '@img/sharp-libvips-linux-x64@1.0.4':
+    resolution: {integrity: sha512-MmWmQ3iPFZr0Iev+BAgVMb3ZyC4KeFc3jFxnNbEPas60e1cIfevbtuyf9nDGIzOaW9PdnDciJm+wFFaTlj5xYw==}
+    cpu: [x64]
+    os: [linux]
+    libc: [glibc]
 
-  '@babel/plugin-bugfix-safari-class-field-initializer-scope@7.29.7':
-    resolution: {integrity: sha512-r8j8escF+U2FUHo0KOhPUdMzUO+jp9fInva6+ACVAF3Y97Ev+5iNZwiqTghmzNeWwDkOPlYuTcfb1vDaoZKmAQ==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0
+  '@img/sharp-libvips-linuxmusl-arm64@1.0.4':
+    resolution: {integrity: sha512-9Ti+BbTYDcsbp4wfYib8Ctm1ilkugkA/uscUn6UXK1ldpC1JjiXbLfFZtRlBhjPZ5o1NCLiDbg8fhUPKStHoTA==}
+    cpu: [arm64]
+    os: [linux]
+    libc: [musl]
 
-  '@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression@7.29.7':
-    resolution: {integrity: sha512-GE1TFSiuFeGsCxmYXZl8HwoPrVlwe4rHPFE8weieGKZqnDORK+Ar3vgWMgW+AOxQ6/2TgLSKx9p6W7O4rC6qgQ==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0
+  '@img/sharp-libvips-linuxmusl-x64@1.0.4':
+    resolution: {integrity: sha512-viYN1KX9m+/hGkJtvYYp+CCLgnJXwiQB39damAO7WMdKWlIhmYTfHjwSbQeUK/20vY154mwezd9HflVFM1wVSw==}
+    cpu: [x64]
+    os: [linux]
+    libc: [musl]
 
-  '@babel/plugin-bugfix-safari-rest-destructuring-rhs-array@7.29.7':
-    resolution: {integrity: sha512-oBNVCvnO5tND+xSopWvV8WNGfpTfgP4Zr/YXXSj8zfmcPktp5Ku/aZlsIowgSD4fjmgHn6sGmB9APVsU5zOdhA==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0
+  '@img/sharp-linux-arm64@0.33.5':
+    resolution: {integrity: sha512-JMVv+AMRyGOHtO1RFBiJy/MBsgz0x4AWrT6QoEVVTyh1E39TrCUpTRI7mx9VksGX4awWASxqCYLCV4wBZHAYxA==}
+    engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
+    cpu: [arm64]
+    os: [linux]
+    libc: [glibc]
 
-  '@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining@7.29.7':
-    resolution: {integrity: sha512-QQt9qKHZ2sg/kivaLr7lnQr8HVrQDdBNSfCsTjiDxRuX/K5ORyKq+Bu8Xr0cDE3Dfkv0cw28Ve0EKyKMvulkOw==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.13.0
+  '@img/sharp-linux-arm@0.33.5':
+    resolution: {integrity: sha512-JTS1eldqZbJxjvKaAkxhZmBqPRGmxgu+qFKSInv8moZ2AmT5Yib3EQ1c6gp493HvrvV8QgdOXdyaIBrhvFhBMQ==}
+    engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
+    cpu: [arm]
+    os: [linux]
+    libc: [glibc]
 
-  '@babel/plugin-bugfix-v8-static-class-fields-redefine-readonly@7.29.7':
-    resolution: {integrity: sha512-pn6QacGLgvCcwc+syUhKE/qSjV2D1IHDB84RNxWYSt1mW3K/SCtjinZ2p0cETJxAWBjPy3K/1lHwG5BjjPxNlw==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0
+  '@img/sharp-linux-s390x@0.33.5':
+    resolution: {integrity: sha512-y/5PCd+mP4CA/sPDKl2961b+C9d+vPAveS33s6Z3zfASk2j5upL6fXVPZi7ztePZ5CuH+1kW8JtvxgbuXHRa4Q==}
+    engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
+    cpu: [s390x]
+    os: [linux]
+    libc: [glibc]
 
-  '@babel/plugin-proposal-private-property-in-object@7.21.0-placeholder-for-preset-env.2':
-    resolution: {integrity: sha512-SOSkfJDddaM7mak6cPEpswyTRnuRltl429hMraQEglW+OkovnCzsiszTmsrlY//qLFjCpQDFRvjdm2wA5pPm9w==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@img/sharp-linux-x64@0.33.5':
+    resolution: {integrity: sha512-opC+Ok5pRNAzuvq1AG0ar+1owsu842/Ab+4qvU879ippJBHvyY5n2mxF1izXqkPYlGuP/M556uh53jRLJmzTWA==}
+    engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
+    cpu: [x64]
+    os: [linux]
+    libc: [glibc]
 
-  '@babel/plugin-syntax-dynamic-import@7.8.3':
-    resolution: {integrity: sha512-5gdGbFon+PszYzqs83S3E5mpi7/y/8M9eC90MRTZfduQOYW76ig6SOSPNe41IG5LoP3FGBn2N0RjVDSQiS94kQ==}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@img/sharp-linuxmusl-arm64@0.33.5':
+    resolution: {integrity: sha512-XrHMZwGQGvJg2V/oRSUfSAfjfPxO+4DkiRh6p2AFjLQztWUuY/o8Mq0eMQVIY7HJ1CDQUJlxGGZRw1a5bqmd1g==}
+    engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
+    cpu: [arm64]
+    os: [linux]
+    libc: [musl]
 
-  '@babel/plugin-syntax-import-assertions@7.29.7':
-    resolution: {integrity: sha512-/An1OCBN93thpBAGyfsK2pcf0jvju1SAtKkL2Ny++B5Sy6sqgzXDQH1cZxWbF96Wuk+bn41MDA9bLd4VVAw6rw==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@img/sharp-linuxmusl-x64@0.33.5':
+    resolution: {integrity: sha512-WT+d/cgqKkkKySYmqoZ8y3pxx7lx9vVejxW/W4DOFMYVSkErR+w7mf2u8m/y4+xHe7yY9DAXQMWQhpnMuFfScw==}
+    engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
+    cpu: [x64]
+    os: [linux]
+    libc: [musl]
 
-  '@babel/plugin-syntax-import-attributes@7.29.7':
-    resolution: {integrity: sha512-zGYcYfq/WmZ4V+kBIXQon9dSSc8ircGZqw9ZaNhhGj9nZkeBu1jHLBDQqYYi5WA9uawvA2sIMbry2nCFhf5Djg==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@img/sharp-wasm32@0.33.5':
+    resolution: {integrity: sha512-ykUW4LVGaMcU9lu9thv85CbRMAwfeadCJHRsg2GmeRa/cJxsVY9Rbd57JcMxBkKHag5U/x7TSBpScF4U8ElVzg==}
+    engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
+    cpu: [wasm32]
 
-  '@babel/plugin-syntax-jsx@7.29.7':
-    resolution: {integrity: sha512-TSu8+mHCoEaaCDEZ0I3+6mvTBYR4PCxQwf2z9/r5Tbztv6NaLR3B9thGTTxX2WGuGHJqRiAbKPeGTJ5XWXVg6A==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@img/sharp-win32-ia32@0.33.5':
+    resolution: {integrity: sha512-T36PblLaTwuVJ/zw/LaH0PdZkRz5rd3SmMHX8GSmR7vtNSP5Z6bQkExdSK7xGWyxLw4sUknBuugTelgw2faBbQ==}
+    engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
+    cpu: [ia32]
+    os: [win32]
 
-  '@babel/plugin-syntax-typescript@7.29.7':
-    resolution: {integrity: sha512-ngr+82Sh0xMz25TPCZi+nC2iTzjfCdWS2ONXTp/PtSCHCgaCNBpdMqgvJ2ccdLlClVZ7sisIgB914j/JFe+RZA==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@img/sharp-win32-x64@0.33.5':
+    resolution: {integrity: sha512-MpY/o8/8kj+EcnxwvrP4aTJSWw/aZ7JIGR4aBeZkZw5B7/Jn+tY9/VNwtcoGmdT7GfggGIU4kygOMSbYnOrAbg==}
+    engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
+    cpu: [x64]
+    os: [win32]
 
-  '@babel/plugin-syntax-unicode-sets-regex@7.18.6':
-    resolution: {integrity: sha512-727YkEAPwSIQTv5im8QHz3upqp92JTWhidIC81Tdx4VJYIte/VndKf1qKrfnnhPLiPghStWfvC/iFaMCQu7Nqg==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0
+  '@inquirer/ansi@1.0.2':
+    resolution: {integrity: sha512-S8qNSZiYzFd0wAcyG5AXCvUHC5Sr7xpZ9wZ2py9XR88jUz8wooStVx5M6dRzczbBWjic9NP7+rY0Xi7qqK/aMQ==}
+    engines: {node: '>=18'}
 
-  '@babel/plugin-transform-arrow-functions@7.29.7':
-    resolution: {integrity: sha512-N7zArUXWzAMzm+/N0uPBeVB3Fam5lMxtUwMmDK5f/IBBS7a7p1qeUoxd/6CckXoxUdgsntq1Dh8xNW06maZbDQ==}
-    engines: {node: '>=6.9.0'}
+  '@inquirer/checkbox@4.3.2':
+    resolution: {integrity: sha512-VXukHf0RR1doGe6Sm4F0Em7SWYLTHSsbGfJdS9Ja2bX5/D5uwVOEjr07cncLROdBvmnvCATYEWlHqYmXv2IlQA==}
+    engines: {node: '>=18'}
     peerDependencies:
-      '@babel/core': ^7.0.0-0
+      '@types/node': '>=18'
+    peerDependenciesMeta:
+      '@types/node':
+        optional: true
 
-  '@babel/plugin-transform-async-generator-functions@7.29.7':
-    resolution: {integrity: sha512-d98gXZkgswvkyohMBABkhm3GeXhYj8psWfwQ2C7gtfrKGTykQa/iOIi+JJhwMjPlZ6Vm2XN+DCf3Es1EoG4ZLA==}
-    engines: {node: '>=6.9.0'}
+  '@inquirer/confirm@5.1.21':
+    resolution: {integrity: sha512-KR8edRkIsUayMXV+o3Gv+q4jlhENF9nMYUZs9PA2HzrXeHI8M5uDag70U7RJn9yyiMZSbtF5/UexBtAVtZGSbQ==}
+    engines: {node: '>=18'}
     peerDependencies:
-      '@babel/core': ^7.0.0-0
+      '@types/node': '>=18'
+    peerDependenciesMeta:
+      '@types/node':
+        optional: true
 
-  '@babel/plugin-transform-async-to-generator@7.29.7':
-    resolution: {integrity: sha512-pcUb2SS+RMo9TWVBwKGI5ShtoG7R+zBsFmCKDa6fe8c+hPr3XJlZgoE5j6i8W7gDjhyvy+85vmYexanvXh3d1w==}
-    engines: {node: '>=6.9.0'}
+  '@inquirer/core@10.3.2':
+    resolution: {integrity: sha512-43RTuEbfP8MbKzedNqBrlhhNKVwoK//vUFNW3Q3vZ88BLcrs4kYpGg+B2mm5p2K/HfygoCxuKwJJiv8PbGmE0A==}
+    engines: {node: '>=18'}
     peerDependencies:
-      '@babel/core': ^7.0.0-0
+      '@types/node': '>=18'
+    peerDependenciesMeta:
+      '@types/node':
+        optional: true
 
-  '@babel/plugin-transform-block-scoped-functions@7.29.7':
-    resolution: {integrity: sha512-cUSmjh72N+rN4PrkFlN1dJwNCwjVp5d38/CQrEsFggkD10UiFlBFgdH3tv5dNsLuHY+3S8db2xCHjhZcv5WgvA==}
-    engines: {node: '>=6.9.0'}
+  '@inquirer/editor@4.2.23':
+    resolution: {integrity: sha512-aLSROkEwirotxZ1pBaP8tugXRFCxW94gwrQLxXfrZsKkfjOYC1aRvAZuhpJOb5cu4IBTJdsCigUlf2iCOu4ZDQ==}
+    engines: {node: '>=18'}
     peerDependencies:
-      '@babel/core': ^7.0.0-0
+      '@types/node': '>=18'
+    peerDependenciesMeta:
+      '@types/node':
+        optional: true
 
-  '@babel/plugin-transform-block-scoping@7.29.7':
-    resolution: {integrity: sha512-ONyr4+AZhKh8yKWInVxU9AXA9EbsyeLcL6V0dJy6M2/62vuvpGm29zzuymbTpdc451GEpDIdAyPLP3r+P61yKQ==}
-    engines: {node: '>=6.9.0'}
+  '@inquirer/expand@4.0.23':
+    resolution: {integrity: sha512-nRzdOyFYnpeYTTR2qFwEVmIWypzdAx/sIkCMeTNTcflFOovfqUk+HcFhQQVBftAh9gmGrpFj6QcGEqrDMDOiew==}
+    engines: {node: '>=18'}
     peerDependencies:
-      '@babel/core': ^7.0.0-0
+      '@types/node': '>=18'
+    peerDependenciesMeta:
+      '@types/node':
+        optional: true
 
-  '@babel/plugin-transform-class-properties@7.29.7':
-    resolution: {integrity: sha512-GtcpjFvanPfzNQi3eTitsCqtRRmmqzpy/A+yhTR1HaZo1Ly3EA8ZXxlPyHdR8/IuRMYc3E4wdGBewB2QKQjAaA==}
-    engines: {node: '>=6.9.0'}
+  '@inquirer/external-editor@1.0.3':
+    resolution: {integrity: sha512-RWbSrDiYmO4LbejWY7ttpxczuwQyZLBUyygsA9Nsv95hpzUWwnNTVQmAq3xuh7vNwCp07UTmE5i11XAEExx4RA==}
+    engines: {node: '>=18'}
     peerDependencies:
-      '@babel/core': ^7.0.0-0
+      '@types/node': '>=18'
+    peerDependenciesMeta:
+      '@types/node':
+        optional: true
 
-  '@babel/plugin-transform-class-static-block@7.29.7':
-    resolution: {integrity: sha512-kibJgmEdX2iMwsHY2tSZNDgj8PwIlCQz7FK9KuGKO8zsuoUwSEhoNnNVp/emKWrbY4HeO6kkXfdMqRKKKXBm2A==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.12.0
+  '@inquirer/figures@1.0.15':
+    resolution: {integrity: sha512-t2IEY+unGHOzAaVM5Xx6DEWKeXlDDcNPeDyUpsRc6CUhBfU3VQOEl+Vssh7VNp1dR8MdUJBWhuObjXCsVpjN5g==}
+    engines: {node: '>=18'}
 
-  '@babel/plugin-transform-classes@7.29.7':
-    resolution: {integrity: sha512-qV0OGGBVacduzQHE649JyCneOFI/maT+YKsO+K4Yi3xv2wTPNjM/W2o2gdzMwEAZz7fXNTHAe0NcSg30bIN69g==}
-    engines: {node: '>=6.9.0'}
+  '@inquirer/input@4.3.1':
+    resolution: {integrity: sha512-kN0pAM4yPrLjJ1XJBjDxyfDduXOuQHrBB8aLDMueuwUGn+vNpF7Gq7TvyVxx8u4SHlFFj4trmj+a2cbpG4Jn1g==}
+    engines: {node: '>=18'}
     peerDependencies:
-      '@babel/core': ^7.0.0-0
+      '@types/node': '>=18'
+    peerDependenciesMeta:
+      '@types/node':
+        optional: true
 
-  '@babel/plugin-transform-computed-properties@7.29.7':
-    resolution: {integrity: sha512-RK7/IyU5phpuCdBAuig5VkzG/EnbDaui5SQGdU9BFrHdV+mV4cUjLMQ9lJDjLNtWHsqtiefpGZUXQP2BiTYMsA==}
-    engines: {node: '>=6.9.0'}
+  '@inquirer/number@3.0.23':
+    resolution: {integrity: sha512-5Smv0OK7K0KUzUfYUXDXQc9jrf8OHo4ktlEayFlelCjwMXz0299Y8OrI+lj7i4gCBY15UObk76q0QtxjzFcFcg==}
+    engines: {node: '>=18'}
     peerDependencies:
-      '@babel/core': ^7.0.0-0
+      '@types/node': '>=18'
+    peerDependenciesMeta:
+      '@types/node':
+        optional: true
 
-  '@babel/plugin-transform-destructuring@7.29.7':
-    resolution: {integrity: sha512-iPX8aD6H9zV5s7ZsqTdNocPN/MGQ5sSMnElKrktxjJRMnB2jN/1p2+R7GkfD6CAYoVFqy5A4XnSIUeGgJzIWpg==}
-    engines: {node: '>=6.9.0'}
+  '@inquirer/password@4.0.23':
+    resolution: {integrity: sha512-zREJHjhT5vJBMZX/IUbyI9zVtVfOLiTO66MrF/3GFZYZ7T4YILW5MSkEYHceSii/KtRk+4i3RE7E1CUXA2jHcA==}
+    engines: {node: '>=18'}
     peerDependencies:
-      '@babel/core': ^7.0.0-0
+      '@types/node': '>=18'
+    peerDependenciesMeta:
+      '@types/node':
+        optional: true
 
-  '@babel/plugin-transform-dotall-regex@7.29.7':
-    resolution: {integrity: sha512-3qc18hsD2RdZiyJNDNc7HQpv6xbncwh8FYtxNFFzclSyh/trPD9KkVR9BDECUjDLvb7yJVF15GfYUuC+LMkkiQ==}
-    engines: {node: '>=6.9.0'}
+  '@inquirer/prompts@7.9.0':
+    resolution: {integrity: sha512-X7/+dG9SLpSzRkwgG5/xiIzW0oMrV3C0HOa7YHG1WnrLK+vCQHfte4k/T80059YBdei29RBC3s+pSMvPJDU9/A==}
+    engines: {node: '>=18'}
     peerDependencies:
-      '@babel/core': ^7.0.0-0
+      '@types/node': '>=18'
+    peerDependenciesMeta:
+      '@types/node':
+        optional: true
 
-  '@babel/plugin-transform-duplicate-keys@7.29.7':
-    resolution: {integrity: sha512-6IvRRriEMqnBwD6chtxdLpMYCHWEzN+oL5cyQtjykya19UgzbmKhxmhZgKC/LHxS2nYr9Q/qYPZ5Lr6jOL9+yQ==}
-    engines: {node: '>=6.9.0'}
+  '@inquirer/rawlist@4.1.11':
+    resolution: {integrity: sha512-+LLQB8XGr3I5LZN/GuAHo+GpDJegQwuPARLChlMICNdwW7OwV2izlCSCxN6cqpL0sMXmbKbFcItJgdQq5EBXTw==}
+    engines: {node: '>=18'}
     peerDependencies:
-      '@babel/core': ^7.0.0-0
+      '@types/node': '>=18'
+    peerDependenciesMeta:
+      '@types/node':
+        optional: true
 
-  '@babel/plugin-transform-duplicate-named-capturing-groups-regex@7.29.7':
-    resolution: {integrity: sha512-2wiIyo2BjtgU7HufSeDnL9L2O7zr8jmhFKuSr65VpRkUiRKRNpb0mdlk56+XPPKoIrfHqzbMuglDvZun0RISsA==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0
-
-  '@babel/plugin-transform-dynamic-import@7.29.7':
-    resolution: {integrity: sha512-giOlEm/EFjfjr+te9NsdjkUo2v4f8rS/SXPumRVHAtbNcyNlvtREkU1dZzaIDclNpnaVhlCqRdFKhJBjBikzLg==}
-    engines: {node: '>=6.9.0'}
+  '@inquirer/search@3.2.2':
+    resolution: {integrity: sha512-p2bvRfENXCZdWF/U2BXvnSI9h+tuA8iNqtUKb9UWbmLYCRQxd8WkvwWvYn+3NgYaNwdUkHytJMGG4MMLucI1kA==}
+    engines: {node: '>=18'}
     peerDependencies:
-      '@babel/core': ^7.0.0-0
+      '@types/node': '>=18'
+    peerDependenciesMeta:
+      '@types/node':
+        optional: true
 
-  '@babel/plugin-transform-explicit-resource-management@7.29.7':
-    resolution: {integrity: sha512-Rstj7coNz8sE+7Ju7ihpHLI564lsK5pUpNNlvptCIC/16E/S5hbl6n3kESPKdNRmqEWlpn5xpS5Q2dvXBsySLw==}
-    engines: {node: '>=6.9.0'}
+  '@inquirer/select@4.4.2':
+    resolution: {integrity: sha512-l4xMuJo55MAe+N7Qr4rX90vypFwCajSakx59qe/tMaC1aEHWLyw68wF4o0A4SLAY4E0nd+Vt+EyskeDIqu1M6w==}
+    engines: {node: '>=18'}
     peerDependencies:
-      '@babel/core': ^7.0.0-0
+      '@types/node': '>=18'
+    peerDependenciesMeta:
+      '@types/node':
+        optional: true
 
-  '@babel/plugin-transform-exponentiation-operator@7.29.7':
-    resolution: {integrity: sha512-zFpMOTLZBdW5LfObqcSbL6kefg4R4eLdmvS0wbN9M6D5Mym/sKm9toOoWyVOa+xDjvCnuWcHls2YonXwHvH3CQ==}
-    engines: {node: '>=6.9.0'}
+  '@inquirer/type@3.0.10':
+    resolution: {integrity: sha512-BvziSRxfz5Ov8ch0z/n3oijRSEcEsHnhggm4xFZe93DHcUCTlutlq9Ox4SVENAfcRD22UQq7T/atg9Wr3k09eA==}
+    engines: {node: '>=18'}
     peerDependencies:
-      '@babel/core': ^7.0.0-0
+      '@types/node': '>=18'
+    peerDependenciesMeta:
+      '@types/node':
+        optional: true
 
-  '@babel/plugin-transform-export-namespace-from@7.29.7':
-    resolution: {integrity: sha512-24B2nOy2TeJSMheqwPD4DDQOV/elLSIlKxjZt4i05H5AgdPdWR3n18HnNrcJ+j76WJd9gbwb9jPjNYUy6RautA==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@isaacs/fs-minipass@4.0.1':
+    resolution: {integrity: sha512-wgm9Ehl2jpeqP3zw/7mo3kRHFp5MEDhqAdwy1fTGkHAwnkGOVsgpvQhL8B5n1qlb01jV3n/bI0ZfZp5lWA1k4w==}
+    engines: {node: '>=18.0.0'}
 
-  '@babel/plugin-transform-for-of@7.29.7':
-    resolution: {integrity: sha512-zeSIHh0+E1Um1WJRXCFlHQYu2ieJNdivLLjlBEp+dIBu3S51n+SZZmIXjxnItw6pz56Cn+KvK68BIBVsxq2JiQ==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@jridgewell/gen-mapping@0.3.13':
+    resolution: {integrity: sha512-2kkt/7niJ6MgEPxF0bYdQ6etZaA+fQvDcLKckhy1yIQOzaoKjBBjSj63/aLVjYE3qhRt5dvM+uUyfCg6UKCBbA==}
 
-  '@babel/plugin-transform-function-name@7.29.7':
-    resolution: {integrity: sha512-otRWaHXE6fbAGkePvaj/kvs3HsqXfPhlnzwSOlnFgbqCPMd975dW+4wZ00WFBt+/YlBGcJwNrARQTOJOb4ZrIg==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@jridgewell/resolve-uri@3.1.2':
+    resolution: {integrity: sha512-bRISgCIjP20/tbWSPWMEi54QVPRZExkuD9lJL+UIxUKtwVJA8wW1Trb1jMs1RFXo1CBTNZ/5hpC9QvmKWdopKw==}
+    engines: {node: '>=6.0.0'}
 
-  '@babel/plugin-transform-json-strings@7.29.7':
-    resolution: {integrity: sha512-RRnE2+eon1rJAq8MnoF1b5kTpY1vU88twHcvcKMrsqP/jxIRqDVs9iJB5fqPuqyeFAW0wJo4MlUIPpQCq/aRsg==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@jridgewell/sourcemap-codec@1.6.0':
+    resolution: {integrity: sha512-T7jf+5zgsZHwNJ4lvQ7/aezbyk0nNX+zJVWpmHA7VYsEx7a7qr5Rg5IbtJFqkgze5Y2sruq1RUY8Q837Od7iFw==}
 
-  '@babel/plugin-transform-literals@7.29.7':
-    resolution: {integrity: sha512-DZ/oLP21ZuWx1vKqnoNv6/tvEK48AQOBRai40CX9dTjGluvT/YZCyY3rryDtyUqCEoyNroy5KKPwX2iQCiRvyw==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@jridgewell/trace-mapping@0.3.31':
+    resolution: {integrity: sha512-zzNR+SdQSDJzc8joaeP8QQoCQr8NuYx2dIIytl1QeBEZHJ9uW6hebsrYgbz8hJwUQao3TWCMtmfV8Nu1twOLAw==}
 
-  '@babel/plugin-transform-logical-assignment-operators@7.29.7':
-    resolution: {integrity: sha512-A0H91hh6W8MFRkp5TqJmMr39jzGD1A1E1Ysiv2O06Sfbhkapm+XyIzxWCEh5kqwOZ1/8QZ0dY3SeQ7XBqfJd5Q==}
-    engines: {node: '>=6.9.0'}
+  '@jsep-plugin/assignment@1.4.0':
+    resolution: {integrity: sha512-nw2Px23Eirx0PFTVoPrb3FEq9Wkmg6vxcDtt38MtBCf1G0tjLCB9cK+3seOXyiw+6+aalgYhvJabQbWwMVKlEQ==}
+    engines: {node: '>= 10.16.0'}
     peerDependencies:
-      '@babel/core': ^7.0.0-0
+      jsep: ^0.4.0||^1.0.0
 
-  '@babel/plugin-transform-member-expression-literals@7.29.7':
-    resolution: {integrity: sha512-hl1kwFZCCiDyfH25Xmco9jTrkPgnS9pmOzSG7W5I4SaGbLeqKv417hcU2RKmaxoPEgsoJh7ZPOrnPGq99bHoUg==}
-    engines: {node: '>=6.9.0'}
+  '@jsep-plugin/regex@1.1.0':
+    resolution: {integrity: sha512-2Vkbda+XRjK6VTI6Lrh0sNBuMT8mZ51EhqMvO+V2rSdmqjs7NAGssxPZfkL23EFzYfSrvxyd1ZjOdqPQMM50og==}
+    engines: {node: '>= 10.16.0'}
     peerDependencies:
-      '@babel/core': ^7.0.0-0
+      jsep: ^0.4.0||^1.0.0
 
-  '@babel/plugin-transform-modules-amd@7.29.7':
-    resolution: {integrity: sha512-fxtQoH3m5ywUSIfaH0FGCzWu4McsYon5bD3K4XnskC7f+OyQMj7rsOMi4NvvmJ83WwBAg4UCe+ov4VZlqEvyew==}
-    engines: {node: '>=6.9.0'}
+  '@jsep-plugin/ternary@1.2.0':
+    resolution: {integrity: sha512-S8Gtq3MWi6dbM/LMwaOd+JPpTcMezLe8cX2YXIQ7HqCLg4JT3rhEFRU6WqDR1I8Nal5R3sOzXhVB/W53ovz2Yg==}
+    engines: {node: '>= 10.16.0'}
     peerDependencies:
-      '@babel/core': ^7.0.0-0
+      jsep: ^0.4.0||^1.0.0
 
-  '@babel/plugin-transform-modules-commonjs@7.29.7':
-    resolution: {integrity: sha512-j0vCldybPC5b5dwCQOJ21uKtHzt7hxLygJTg9eF1ScfaikEDNfzn94XoW5Fi+seBR0nCyL23xaBFFkq7dTM8XQ==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@json-schema-spec/json-pointer@0.1.2':
+    resolution: {integrity: sha512-BYY7IavBjwsWWSmVcMz2A9mKiDD9RvacnsItgmy1xV8cmgbtxFfKmKMtkVpD7pYtkx4mIW4800yZBXueVFIWPw==}
 
-  '@babel/plugin-transform-modules-systemjs@7.29.7':
-    resolution: {integrity: sha512-TM2ZcQLoG2/y4HODiStCo10DibYhWhGWAwVv+EQKmG/7GFl0N+AAmUiXOMKM+aiJ9XBJ9AHVZBvTzMnJ2sM3cQ==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@json-schema-tools/dereferencer@1.6.3':
+    resolution: {integrity: sha512-NoQkj6hx9Joqbd/GZAOHSGtE6R+OzlnOcDfyidmx8e/CUv1Q+Z6/fmZo2wwCQWiwP1pnGYc95iKwp8M7XlV7wQ==}
 
-  '@babel/plugin-transform-modules-umd@7.29.7':
-    resolution: {integrity: sha512-B4UkaTK3QpgCwJnrxKfMPKdo92CN7OKXAlpAAnM3UPu0Q0lCCk57ylA9AJbRy2v8dDKOPAAWcoR6CMyeoHwRCA==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@json-schema-tools/meta-schema@1.8.0':
+    resolution: {integrity: sha512-pbRAbHidPTf96LhmHXA6bl4D4tz4HrwjZ7A5ConcLFPdCj+93GhsCCFsq+AWti4VOs+9QTezX5l0zLNA+TZv1g==}
 
-  '@babel/plugin-transform-named-capturing-groups-regex@7.29.7':
-    resolution: {integrity: sha512-vuFoLwr4qnv2xbZ16SQd6uPcH5FNrLHhk/Jzo++0XJFcaDsr4gjJVg6j398oMHiC+83k/GiBzviwF5KBJkPUtQ==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0
+  '@json-schema-tools/reference-resolver@1.2.6':
+    resolution: {integrity: sha512-4QZu5ROb5EpLSvV+buzk8WR30W+dffSNaKqD3VGFYJ3y0BLDi2OHoSz5e6NKcLYTyUYXV8IKxocNOszeVBJI4Q==}
 
-  '@babel/plugin-transform-new-target@7.29.7':
-    resolution: {integrity: sha512-fEo41GmsOUhOBlw8ioo6zvjX5Xc2Lqkzlyfqbpsk3eB6TReV18uhxZ0esfEokVbY2+PVJAQHNKxER6lGrzNd3A==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@json-schema-tools/traverse@1.11.0':
+    resolution: {integrity: sha512-GWQRiXXsbt5ZuewItpW2nqB/D0x4pKWi6XXOwoh1wvmsU/tQSq/rKzpgGvOHTe6v30TYDwZYxuwnRnArIsUzLQ==}
 
-  '@babel/plugin-transform-nullish-coalescing-operator@7.29.7':
-    resolution: {integrity: sha512-idmp1dFaekP9GbcMvG24Kvw2BfhFZjHnNJCkV4WuIY4PskJzwI3f1N5OdgYke38T7rftO6ERulFRn2cFeZwRkg==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@leichtgewicht/ip-codec@2.0.5':
+    resolution: {integrity: sha512-Vo+PSpZG2/fmgmiNzYK9qWRh8h/CHrwD0mo1h1DzL4yzHNSfWYujGTYsWGreD000gcgmZ7K4Ys6Tx9TxtsKdDw==}
 
-  '@babel/plugin-transform-numeric-separator@7.29.7':
-    resolution: {integrity: sha512-zR7fv/z14OjgHl4AgRtkDBvBMhIzCxqV/qN/2BCRC7LjFwvuzjYe7gDWxC4Wl/SNsLM6SE1IWvRPYMgSJaUvNw==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@mdx-js/mdx@3.1.1':
+    resolution: {integrity: sha512-f6ZO2ifpwAQIpzGWaBQT2TXxPv6z3RBzQKpVftEWN78Vl/YweF1uwussDx8ECAXVtr3Rs89fKyG9YlzUs9DyGQ==}
 
-  '@babel/plugin-transform-object-rest-spread@7.29.7':
-    resolution: {integrity: sha512-Ld98jn4c0smUywL57m7SgsHq3OpThOa6LqZJif3G6jYOovPleoFhVrBJ1WegRApSFB2wu4+RelAj9AC9G08Z4A==}
-    engines: {node: '>=6.9.0'}
+  '@mdx-js/react@3.1.1':
+    resolution: {integrity: sha512-f++rKLQgUVYDAtECQ6fn/is15GkEH9+nZPM3MS0RcxVqoTfawHvDlSCH7JbMhAM6uJ32v3eXLvLmLvjGu7PTQw==}
     peerDependencies:
-      '@babel/core': ^7.0.0-0
+      '@types/react': '>=16'
+      react: '>=16'
 
-  '@babel/plugin-transform-object-super@7.29.7':
-    resolution: {integrity: sha512-Ea/diGcw0twB5IlZPO5sgET6fJsLJqPABqTuFWIR+iMPGPZJkATEIWx0wa+aEQ5UY1CBQyP/gkAiLEqn1vBiQA==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@mintlify/cli@4.0.1665':
+    resolution: {integrity: sha512-EzLyvyXNSL1kwHFj9JyIjN3VrWcT6T5EqjzZ2wwhzlv/+9oXpCyd/uC9lum6ofNYLX8Oj/g/WpU4y84EHDjcDg==}
+    engines: {node: '>=18.0.0'}
+    hasBin: true
 
-  '@babel/plugin-transform-optional-catch-binding@7.29.7':
-    resolution: {integrity: sha512-sLsyndxK2VwX6yNUOakMb7Sh553ZTe/vVM1XJ+9Z5aW1ytsc8xOIwmyk05NNjN60vkc5/KqoTH6hB4V41LJhng==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@mintlify/common@1.0.1260':
+    resolution: {integrity: sha512-6Ukl2rbLdIWqau62SVAN+yPZ2p36vte5wbA3UQuHhxCCstlOvHrppyK6Zf+PLGvRNpzwhrqkhKBG3BuMXu3HZw==}
 
-  '@babel/plugin-transform-optional-chaining@7.29.7':
-    resolution: {integrity: sha512-6GM1dhvK3gNODkXcEcMCOLEDCLSoZ/sBbro2Ax8HURyasQ4NshagQixkRFdh5niI6E4gmA/jYI/4aT7rRos3ZQ==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@mintlify/link-rot@3.0.1481':
+    resolution: {integrity: sha512-++BFEYWvXzBTL76I2m+AnfqDqKL3y7Q4iiEcYabheDn3Si/5wRE4ywOf2KyNH9AQqtfnRatH9TLLG1Va7TZbsg==}
+    engines: {node: '>=18.0.0'}
 
-  '@babel/plugin-transform-parameters@7.29.7':
-    resolution: {integrity: sha512-ZDOBqV/qLYJI0YElr8DcENEyARsFQeESqWXH6gZlghYXuPPjvweuDhP4VyEi4BlUBlLRFZVjxoZDMjxhLW766g==}
-    engines: {node: '>=6.9.0'}
+  '@mintlify/mdx@4.0.7':
+    resolution: {integrity: sha512-/kOnIHvjM4jwF7WoXjPRp1nDLjgW8YFyApw5JQiXU6cEdXJdqpWH1xW+0rgGD4adi6yXY+Re9cfNRMftJzCo5A==}
     peerDependencies:
-      '@babel/core': ^7.0.0-0
+      '@base-ui/react': ^1.6.0
+      react: ^19.2.1
+      react-dom: ^19.2.1
 
-  '@babel/plugin-transform-private-methods@7.29.7':
-    resolution: {integrity: sha512-/6Rz4DK1ETDEM/bWHsPHcaEe7ZaT1EqSXjtSP/L0DijOYuaUhiRiOKcwpZ8P7zR4xXEHc2ITdiCgBm9Tpyv9ug==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@mintlify/models@0.0.375':
+    resolution: {integrity: sha512-vD0TpCnt61AR1v2ObD1Y8xyXlMf+RFH1/lKX/gePePh7TKkY5vtWg4o1nxTse1TXuRinbJRCmyz3SAguO5z86A==}
+    engines: {node: '>=18.0.0'}
 
-  '@babel/plugin-transform-private-property-in-object@7.29.7':
-    resolution: {integrity: sha512-+BNo06dnrzdNNqCm1X6YUaVv0DKk8Q+JYcoZfOkLhYWNCXzlwTSRq8zGWayT1csjcpNXV9CQTBRRbmTLZac5cA==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@mintlify/og@0.0.58':
+    resolution: {integrity: sha512-AghNYTPNoVT6HkuYFLM1B2Q94WoGIhL5b87vd7mxnW25o0bKzZqTBUJrvTf6qaqXh6WF6ofOEa0i5yYu3yJanQ==}
+    engines: {node: '>=18.0.0'}
 
-  '@babel/plugin-transform-property-literals@7.29.7':
-    resolution: {integrity: sha512-bOMRLQuI0A5ZqHq3OWJ89/rXpJ/NJrbVhXiP4zwPGMs6kpcVsuTUNjwoE30K0Qm3mf48a/TnRYYD6vPNqcg6jA==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@mintlify/openapi-parser@0.0.9':
+    resolution: {integrity: sha512-PHNRY+K6c5lsEqxfLHH1NghO34PTmhtBSFSw5KOx8DyUYe5LTn7k4U3hp7i1qvJuUTC+x0bU4unFmkM1Hc4OGw==}
+    engines: {node: '>=18'}
 
-  '@babel/plugin-transform-react-constant-elements@7.29.7':
-    resolution: {integrity: sha512-J0wGhKan+rIiE2OhfhRptySLrJ6SjQYM6b6N1FMlhyhCcw1Mig8vQjWchyB+bgHGDvaWo6Diu6CLRMra2uMtmg==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@mintlify/package-builder@0.0.48':
+    resolution: {integrity: sha512-MkuT41HDmud5DmtOl0tW30bnALIyCWDCKA0t2FG4ZnoBcvVujTrelIm+a1A4XFqZywMAXbdT0BIoUf9t6Qvg9w==}
+    engines: {node: '>=18.0.0'}
+    hasBin: true
 
-  '@babel/plugin-transform-react-display-name@7.29.7':
-    resolution: {integrity: sha512-+1wdDMGNb4UPeY3Q4L5yLiYe6TXPXubs4NjrgRFw13hPRLJfEMw2Q5OXkee6/IfdqePIeW4Jjwe3aBh7SdKz4Q==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@mintlify/prebuild@1.0.1425':
+    resolution: {integrity: sha512-244RggxgQ2VljFzgT8Bdwg+tUJZCND9sTBUfUW/4+D9FxULNks8TU+D+k2llYXAWGILMoSKKFGVn6t8JjilV6w==}
 
-  '@babel/plugin-transform-react-jsx-development@7.29.7':
-    resolution: {integrity: sha512-Xfy3UVMF04+ypnFbkhvfqtmvwfe92qwQdbGZVonhE+6v35GzlofmOnA1szaZqzb9xYWr0nl1e5EMmzi0DNON1g==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@mintlify/previewing@4.0.1501':
+    resolution: {integrity: sha512-UH0MOpKxlEX7NHMsTIOUvhFBMxetKW83z6lJB/S8ZntYA1L1kW6H/hagRfLoPQDnh/Xw/HCCet4iBiPkS2i3Bg==}
+    engines: {node: '>=18.0.0'}
 
-  '@babel/plugin-transform-react-jsx@7.29.7':
-    resolution: {integrity: sha512-WsZulLVBUHXVj2cUcPVx6UE21TpalB6bHbSFErKT0Ib++ax24jjXe73FqlWvdylFOjiuPHYi6VCcgRad1ItN+A==}
-    engines: {node: '>=6.9.0'}
+  '@mintlify/scraping@4.0.1133':
+    resolution: {integrity: sha512-0yQ/yjJsGtxwfMkw1rtkvGDg8w1vnjmvWzLy38+r2p4rWTcwj8YIsDRlDZjKTJetZb4n/SohDrZTNIfv9GA8ow==}
+    engines: {node: '>=18.0.0'}
+    hasBin: true
     peerDependencies:
-      '@babel/core': ^7.0.0-0
+      puppeteer: 24.3.1
+    peerDependenciesMeta:
+      puppeteer:
+        optional: true
 
-  '@babel/plugin-transform-react-pure-annotations@7.29.7':
-    resolution: {integrity: sha512-H5E+HBgDpr6Q5t+Aj11tL7XkIui1jhbIoArVQnqjgXo5/3YxkN7ZEBcWF4RQlB0T4rrxJQbXS6kiFV6B7XTqUA==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@mintlify/validation@0.1.923':
+    resolution: {integrity: sha512-RH3HBqD5WcLUfOEqbf2tjtiQvsRgWuIDflnxo1RlGuPxSC+CNswOGt4xFq7mpRpWh1ZOkmxbIQaWBwQ8cqeqeQ==}
 
-  '@babel/plugin-transform-regenerator@7.29.7':
-    resolution: {integrity: sha512-rNNFV0DBAJp988xW2DOntfDoYn1eR8GGF5AT5vYc+rjyfaQkM242c9tZUHHPe7KYaiJizXPWhQTzzdbXySyhBw==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@nodable/entities@2.2.0':
+    resolution: {integrity: sha512-9uGyhaQavEUMC8AIddIjau4NsnsXhou+j5sBAGojCM1oxmQpVKTWR/9JxABD6UAv12vpIms55fPZKFQEhG6uBg==}
 
-  '@babel/plugin-transform-regexp-modifiers@7.29.7':
-    resolution: {integrity: sha512-mB5Fs0VWrJ42ZCmc8114v60qetdaUVNkj9PmSZRmanCZM3S9hm0CFRLjRmYIsuXav14l2jvZ+4T8iiCGnhj3nQ==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0
+  '@nodelib/fs.scandir@2.1.5':
+    resolution: {integrity: sha512-vq24Bq3ym5HEQm2NKCr3yXDwjc7vTsEThRDnkp2DK9p1uqLR+DHurm/NOTo0KG7HYHU7eppKZj3MyqYuMBf62g==}
+    engines: {node: '>= 8'}
 
-  '@babel/plugin-transform-reserved-words@7.29.7':
-    resolution: {integrity: sha512-5+YhdpVgmfSmwZyLMftfaiffLRMHjzIRHFHHLdibcSyJm2pasMrKHrO3Ptrt2DRshjvpgjEJJ1zVW14WPq/6QA==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@nodelib/fs.stat@2.0.5':
+    resolution: {integrity: sha512-RkhPPp2zrqDAQA/2jNhnztcPAlv64XdhIp7a7454A5ovI7Bukxgt7MX7udwAu3zg1DcpPU0rz3VV1SeaqvY4+A==}
+    engines: {node: '>= 8'}
 
-  '@babel/plugin-transform-runtime@7.29.7':
-    resolution: {integrity: sha512-xmAscdE/AsqRW7vutbPNoUmu/nF5SrLKPs7aoJgEjo35lLKA/Bc0i2rMv/hr1+Y0o1bQCiVtith3u2vdgRL39Q==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@nodelib/fs.walk@1.2.8':
+    resolution: {integrity: sha512-oGB+UxlgWcgQkgwo8GcEGwemoTFt3FIO9ababBmaGwXIoBKZ+GTy0pP185beGg7Llih/NSHSV2XAs1lnznocSg==}
+    engines: {node: '>= 8'}
 
-  '@babel/plugin-transform-shorthand-properties@7.29.7':
-    resolution: {integrity: sha512-I+WYbGBAiCn7nA6xBrlgPH+MB7HWb4u8pv5S0Pv7OtwNvIFvCCb24YlttKEeUFVurfBCEaOTnuhlqsb7f0Z5Dg==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@open-rpc/schema-utils-js@2.2.1':
+    resolution: {integrity: sha512-lXsJrkViY08eoqD9X/3Gq0QiN4/jaPEiNdQCB3eZDv4vp26JaIWQ/r2WwYlA8rJZb4lYGIvKr3zM/rTcu7yMuw==}
 
-  '@babel/plugin-transform-spread@7.29.7':
-    resolution: {integrity: sha512-/u5K1QWada7tbYNqTjMh96718g9NTwh9tfPJMsSmVsQwGT447FskV+KcfeXkXq2GWki4EM/MuTdmBec+hOuVTQ==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@open-rpc/spec-types@0.0.2':
+    resolution: {integrity: sha512-4FbovmeH3XVcf7loRpaqxqCAFbX9jDfp85cbvdeNYumL/BWOWA1a6CwScfZWBvIH/eXmrmzhu8nUW4eJTuD3ZQ==}
 
-  '@babel/plugin-transform-sticky-regex@7.29.7':
-    resolution: {integrity: sha512-BCHzNYJGe9l7EpwwDBN/ztlL2NYFFq8hp9ddjtUEM9f2O7S7kKV/lL6Fwo7IF7NSkYhPK2vO+86nIGltA90MsA==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@open-rpc/spec@1.4.1':
+    resolution: {integrity: sha512-XoCq9X7FDv2kXz7nK8JZMDtUrGPRyDwbt7HsZRuBtvqzxAyma/c6t33vlCyxEePxMb4aGfX3MJbI2gz9JIqNvg==}
 
-  '@babel/plugin-transform-template-literals@7.29.7':
-    resolution: {integrity: sha512-NCSEJ4sLFU2gqAub45HYh4fus2yQ36rr6ei6vpU7NdoJqCpxvEG8E6eJpscGyXP3VHD2Ny+fSXr04k1hoUrFqA==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@open-rpc/specification-extension-spec@1.0.2':
+    resolution: {integrity: sha512-EPVI1Mgp5vDSN2Xn+eWjd2t30WU+R0nFeNoP/dp3ox5/qUhNdqlNcwGJDNoJlqK56rk09FYXWJXKLHae4eBE8w==}
+    engines: {node: '>=18.0.0'}
 
-  '@babel/plugin-transform-typeof-symbol@7.29.7':
-    resolution: {integrity: sha512-223mNGoTkBiTEWFoK+Q6Go3tueMRclO8vxxxxquNCYuNI4jWOofFKJRRDu6SDrB8Sgo1UEGW9T4GAQ8ZyRso1A==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@openapi-contrib/openapi-schema-to-json-schema@3.2.0':
+    resolution: {integrity: sha512-Gj6C0JwCr8arj0sYuslWXUBSP/KnUlEGnPW4qxlXvAl543oaNQgMgIgkQUA6vs5BCCvwTEiL8m/wdWzfl4UvSw==}
 
-  '@babel/plugin-transform-typescript@7.29.7':
-    resolution: {integrity: sha512-jK52h8LaLc7JarhQV2ofeFMts4H7vnOXnqZNA6fYglBTZewRBE51KWt3BUltW1P+KoPsYkHoJeXePuz4zo2LMw==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@posthog/core@1.7.1':
+    resolution: {integrity: sha512-kjK0eFMIpKo9GXIbts8VtAknsoZ18oZorANdtuTj1CbgS28t4ZVq//HAWhnxEuXRTrtkd+SUJ6Ux3j2Af8NCuA==}
 
-  '@babel/plugin-transform-unicode-escapes@7.29.7':
-    resolution: {integrity: sha512-jCfXxSjf94lf4E0hKE0AByxF6F3/pVFqRdUUNkDJhsY0m1ZKjnN6ZYyMeHNpzflxb/0q5b7t3p+BE+SLF1WOtA==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@redocly/cli@2.38.0':
+    resolution: {integrity: sha512-zYwQiDJTqoiscB6pFwd80FwI065gA13lp8hg2tgjDDu4p8gotVdCD/EOCaPTalIHskiIa1UFxEPRErPOgkWqJw==}
+    engines: {node: '>=22.12.0 || >=20.19.0 <21.0.0', npm: '>=10'}
+    hasBin: true
 
-  '@babel/plugin-transform-unicode-property-regex@7.29.7':
-    resolution: {integrity: sha512-OgZ+zoAJgZLUCunsTRQ5LAjOywDv5zzZ2/hQ5aMw1pGXyY2rtE8/chXYUmu3AlVHKpm10KEdG9aMwbI/K76ZGw==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@resvg/resvg-wasm@2.6.2':
+    resolution: {integrity: sha512-FqALmHI8D4o6lk/LRWDnhw95z5eO+eAa6ORjVg09YRR7BkcM6oPHU9uyC0gtQG5vpFLvgpeU4+zEAz2H8APHNw==}
+    engines: {node: '>= 10'}
 
-  '@babel/plugin-transform-unicode-regex@7.29.7':
-    resolution: {integrity: sha512-7D/x/23/d/3VqZ0QA+LGbZMlGwZjztBygSWWWsfTPoQ1oQ6Q1P6Mr3d0kk42XabyUVw+fha3LqdRsFqeKqvCyA==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@scarf/scarf@1.4.0':
+    resolution: {integrity: sha512-xxeapPiUXdZAE3che6f3xogoJPeZgig6omHEy1rIY5WVsB3H2BHNnZH+gHG6x91SCWyQCzWGsuL2Hh3ClO5/qQ==}
 
-  '@babel/plugin-transform-unicode-sets-regex@7.29.7':
-    resolution: {integrity: sha512-BLOhLht9DOJwIxlmp91wHvkXv1lguuHS3/FwUO8HL1H0u8s4hR1gASVFyilu9iGtcTRYqjTZmlsFFeQletntEg==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0
+  '@shikijs/core@3.23.0':
+    resolution: {integrity: sha512-NSWQz0riNb67xthdm5br6lAkvpDJRTgB36fxlo37ZzM2yq0PQFFzbd8psqC2XMPgCzo1fW6cVi18+ArJ44wqgA==}
 
-  '@babel/preset-env@7.29.7':
-    resolution: {integrity: sha512-GYzX36n1nsciIb0uyH0GHwxwtNwPQIcpxSeiVLDtG/B7jB5xXgchnmL1f/jCX5o+pwnaDBtO60ONSJhEBJfxYA==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@shikijs/engine-javascript@3.23.0':
+    resolution: {integrity: sha512-aHt9eiGFobmWR5uqJUViySI1bHMqrAgamWE1TYSUoftkAeCCAiGawPMwM+VCadylQtF4V3VNOZ5LmfItH5f3yA==}
 
-  '@babel/preset-modules@0.1.6-no-external-plugins':
-    resolution: {integrity: sha512-HrcgcIESLm9aIR842yhJ5RWan/gebQUJ6E/E5+rf0y9o6oj7w0Br+sWuL6kEQ/o/AdfvR1Je9jG18/gnpwjEyA==}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0 || ^8.0.0-0 <8.0.0
+  '@shikijs/engine-oniguruma@3.23.0':
+    resolution: {integrity: sha512-1nWINwKXxKKLqPibT5f4pAFLej9oZzQTsby8942OTlsJzOBZ0MWKiwzMsd+jhzu8YPCHAswGnnN1YtQfirL35g==}
 
-  '@babel/preset-react@7.29.7':
-    resolution: {integrity: sha512-C+PV1TFUPTmBQGoPBL8j2QmLpZ117YTCwxIZeJOM96GbYMFSc7/pOXU5lVykwnZxyTqQxRsvoRk6f2FktZgGHA==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@shikijs/langs@3.23.0':
+    resolution: {integrity: sha512-2Ep4W3Re5aB1/62RSYQInK9mM3HsLeB91cHqznAJMuylqjzNVAVCMnNWRHFtcNHXsoNRayP9z1qj4Sq3nMqYXg==}
 
-  '@babel/preset-typescript@7.29.7':
-    resolution: {integrity: sha512-/Foi8vKY2EVbed/1eZx0gJEEwHAIxogrySI7rULcRIvhZzbvoE/b5qG5Ghc0WKAFKOHA9SD1x7RsFlOYdutIiQ==}
-    engines: {node: '>=6.9.0'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  '@shikijs/themes@3.23.0':
+    resolution: {integrity: sha512-5qySYa1ZgAT18HR/ypENL9cUSGOeI2x+4IvYJu4JgVJdizn6kG4ia5Q1jDEOi7gTbN4RbuYtmHh0W3eccOrjMA==}
 
-  '@babel/runtime@7.29.7':
-    resolution: {integrity: sha512-Nq8OhGWiZIZGV6hLHoyAKLLcJihP/xFeBMGJoUrxTX2psI8dCifzLhZISFb+VWS3wFMRDmCGw5R+dOySCqPLhw==}
-    engines: {node: '>=6.9.0'}
+  '@shikijs/transformers@3.23.0':
+    resolution: {integrity: sha512-F9msZVxdF+krQNSdQ4V+Ja5QemeAoTQ2jxt7nJCwhDsdF1JWS3KxIQXA3lQbyKwS3J61oHRUSv4jYWv3CkaKTQ==}
 
-  '@babel/template@7.29.7':
-    resolution: {integrity: sha512-puq+Gf35oI24FeN11LkoUQFqv9uwNeWpxXZi/Ji3rRIoKAzKnxRaZ+Gkj0vKS9ZCiTESfng1N9LyOyXvo+m+Gg==}
-    engines: {node: '>=6.9.0'}
+  '@shikijs/twoslash@3.23.0':
+    resolution: {integrity: sha512-pNaLJWMA3LU7PhT8tm9OQBZ1epy0jmdgeJzntBtr1EVXLbHxGzTj3mnf9vOdcl84l96qnlJXkJ/NGXZYBpXl5g==}
+    peerDependencies:
+      typescript: '>=5.5.0'
 
-  '@babel/traverse@7.29.7':
-    resolution: {integrity: sha512-EhlfNQtZ+NK22w5BM61ciuiq1m58ed33Wr1Xan//ZRTy6hgjnwyCffRYwzsGXdASJSUJ1guZILsErh1eQcl+zw==}
-    engines: {node: '>=6.9.0'}
+  '@shikijs/types@3.23.0':
+    resolution: {integrity: sha512-3JZ5HXOZfYjsYSk0yPwBrkupyYSLpAE26Qc0HLghhZNGTZg/SKxXIIgoxOpmmeQP0RRSDJTk1/vPfw9tbw+jSQ==}
 
-  '@babel/types@7.29.7':
-    resolution: {integrity: sha512-4zBIxpPzowiZpusoFkyGVwakdRJUyuH5PxQ/PrqghfdFWWasvnCdPfQXHrenDai+gyLARulZjZowCOj6fjT4pA==}
-    engines: {node: '>=6.9.0'}
+  '@shikijs/vscode-textmate@10.0.2':
+    resolution: {integrity: sha512-83yeghZ2xxin3Nj8z1NMd/NCuca+gsYXswywDy5bHvwlWL8tpTQmzGeUuHd9FC3E/SBEMvzJRwWEOz5gGes9Qg==}
 
-  '@braintree/sanitize-url@7.1.2':
-    resolution: {integrity: sha512-jigsZK+sMF/cuiB7sERuo9V7N9jx+dhmHHnQyDSVdpZwVutaBu7WvNYqMDLSgFgfB30n452TP3vjDAvFC973mA==}
+  '@shuding/opentype.js@1.4.0-beta.0':
+    resolution: {integrity: sha512-3NgmNyH3l/Hv6EvsWJbsvpcpUba6R8IREQ83nH83cyakCw7uM1arZKNfHwv1Wz6jgqrF/j4x5ELvR6PnK9nTcA==}
+    engines: {node: '>= 8.0.0'}
+    hasBin: true
 
-  '@chevrotain/types@11.1.2':
-    resolution: {integrity: sha512-U+HFai5+zmJCkK86QsaJtoITlboZHBqrVketcO2ROv865xfCMSFpELQoz1GkX5GzME8pTa+3kbKrZHQtI0gdbw==}
+  '@sindresorhus/is@5.6.0':
+    resolution: {integrity: sha512-TV7t8GKYaJWsn00tFDqBw8+Uqmr8A0fRU1tvTQhyZzGv0sJCGRQL3JGMI3ucuKo3XIZdUP+Lx7/gh2t3lewy7g==}
+    engines: {node: '>=14.16'}
 
-  '@colors/colors@1.5.0':
-    resolution: {integrity: sha512-ooWCrlZP11i8GImSjTHYHLkvFDP48nS4+204nGb1RiX/WXYHmJA2III9/e2DWVabCESdW7hBAEzHRqUn9OUVvQ==}
-    engines: {node: '>=0.1.90'}
+  '@sindresorhus/slugify@2.2.0':
+    resolution: {integrity: sha512-9Vybc/qX8Kj6pxJaapjkFbiUJPk7MAkCh/GFCxIBnnsuYCFPIXKvnLidG8xlepht3i24L5XemUmGtrJ3UWrl6w==}
+    engines: {node: '>=12'}
 
-  '@csstools/cascade-layer-name-parser@2.0.5':
-    resolution: {integrity: sha512-p1ko5eHgV+MgXFVa4STPKpvPxr6ReS8oS2jzTukjR74i5zJNyWO1ZM1m8YKBXnzDKWfBN1ztLYlHxbVemDD88A==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      '@csstools/css-parser-algorithms': ^3.0.5
-      '@csstools/css-tokenizer': ^3.0.4
+  '@sindresorhus/transliterate@1.6.0':
+    resolution: {integrity: sha512-doH1gimEu3A46VX6aVxpHTeHrytJAG6HgdxntYnCFiIFHEM/ZGpG8KiZGBChchjQmG0XFIBL552kBTjVcMZXwQ==}
+    engines: {node: '>=12'}
 
-  '@csstools/color-helpers@5.1.0':
-    resolution: {integrity: sha512-S11EXWJyy0Mz5SYvRmY8nJYTFFd1LCNV+7cXyAgQtOOuzb4EsgfqDufL+9esx72/eLhsRdGZwaldu/h+E4t4BA==}
-    engines: {node: '>=18'}
+  '@socket.io/component-emitter@3.1.2':
+    resolution: {integrity: sha512-9BCxFwvbGg/RsZK9tjXd8s4UcwR0MWeFQ1XEKIQVVvAGJyINdrqKMcTRyLoK8Rse1GjzLV9cwjWV1olXRWEXVA==}
 
-  '@csstools/css-calc@2.1.4':
-    resolution: {integrity: sha512-3N8oaj+0juUw/1H3YwmDDJXCgTB1gKU6Hc/bB502u9zR0q2vd786XJH9QfrKIEgFlZmhZiq6epXl4rHqhzsIgQ==}
-    engines: {node: '>=18'}
+  '@stellar/prettier-config@1.2.0':
+    resolution: {integrity: sha512-oL9qJ7+7aWnImpbcldroQrvtMCZ9yx4JL/tmDZ860RpBQd2ahkc8bX6/k2ehFK8gpb9ltYu4mtU49wufUuYhGg==}
     peerDependencies:
-      '@csstools/css-parser-algorithms': ^3.0.5
-      '@csstools/css-tokenizer': ^3.0.4
+      prettier: ^3.2.5
 
-  '@csstools/css-color-parser@3.1.0':
-    resolution: {integrity: sha512-nbtKwh3a6xNVIp/VRuXV64yTKnb1IjTAEEh3irzS+HkKjAOYLTGNb9pmVNntZ8iVBHcWDA2Dof0QtPgFI1BaTA==}
-    engines: {node: '>=18'}
+  '@stoplight/better-ajv-errors@1.0.3':
+    resolution: {integrity: sha512-0p9uXkuB22qGdNfy3VeEhxkU5uwvp/KrBTAbrLBURv6ilxIVwanKwjMc41lQfIVgPGcOkmLbTolfFrSsueu7zA==}
+    engines: {node: ^12.20 || >= 14.13}
     peerDependencies:
-      '@csstools/css-parser-algorithms': ^3.0.5
-      '@csstools/css-tokenizer': ^3.0.4
+      ajv: '>=8'
 
-  '@csstools/css-parser-algorithms@3.0.5':
-    resolution: {integrity: sha512-DaDeUkXZKjdGhgYaHNJTV9pV7Y9B3b644jCLs9Upc3VeNGg6LWARAT6O+Q+/COo+2gg/bM5rhpMAtf70WqfBdQ==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      '@csstools/css-tokenizer': ^3.0.4
+  '@stoplight/json-ref-readers@1.2.2':
+    resolution: {integrity: sha512-nty0tHUq2f1IKuFYsLM4CXLZGHdMn+X/IwEUIpeSOXt0QjMUbL0Em57iJUDzz+2MkWG83smIigNZ3fauGjqgdQ==}
+    engines: {node: '>=8.3.0'}
 
-  '@csstools/css-tokenizer@3.0.4':
-    resolution: {integrity: sha512-Vd/9EVDiu6PPJt9yAh6roZP6El1xHrdvIVGjyBsHR0RYwNHgL7FJPyIIW4fANJNG6FtyZfvlRPpFI4ZM/lubvw==}
-    engines: {node: '>=18'}
+  '@stoplight/json-ref-resolver@3.1.6':
+    resolution: {integrity: sha512-YNcWv3R3n3U6iQYBsFOiWSuRGE5su1tJSiX6pAPRVk7dP0L7lqCteXGzuVRQ0gMZqUl8v1P0+fAKxF6PLo9B5A==}
+    engines: {node: '>=8.3.0'}
 
-  '@csstools/media-query-list-parser@4.0.3':
-    resolution: {integrity: sha512-HAYH7d3TLRHDOUQK4mZKf9k9Ph/m8Akstg66ywKR4SFAigjs3yBiUeZtFxywiTm5moZMAp/5W/ZuFnNXXYLuuQ==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      '@csstools/css-parser-algorithms': ^3.0.5
-      '@csstools/css-tokenizer': ^3.0.4
+  '@stoplight/json@3.21.0':
+    resolution: {integrity: sha512-5O0apqJ/t4sIevXCO3SBN9AHCEKKR/Zb4gaj7wYe5863jme9g02Q0n/GhM7ZCALkL+vGPTe4ZzTETP8TFtsw3g==}
+    engines: {node: '>=8.3.0'}
 
-  '@csstools/postcss-alpha-function@1.0.1':
-    resolution: {integrity: sha512-isfLLwksH3yHkFXfCI2Gcaqg7wGGHZZwunoJzEZk0yKYIokgre6hYVFibKL3SYAoR1kBXova8LB+JoO5vZzi9w==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@stoplight/ordered-object-literal@1.0.5':
+    resolution: {integrity: sha512-COTiuCU5bgMUtbIFBuyyh2/yVVzlr5Om0v5utQDgBCuQUOPgU1DwoffkTfg4UBQOvByi5foF4w4T+H9CoRe5wg==}
+    engines: {node: '>=8'}
 
-  '@csstools/postcss-cascade-layers@5.0.2':
-    resolution: {integrity: sha512-nWBE08nhO8uWl6kSAeCx4im7QfVko3zLrtgWZY4/bP87zrSPpSyN/3W3TDqz1jJuH+kbKOHXg5rJnK+ZVYcFFg==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@stoplight/path@1.3.2':
+    resolution: {integrity: sha512-lyIc6JUlUA8Ve5ELywPC8I2Sdnh1zc1zmbYgVarhXIp9YeAB0ReeqmGEOWNtlHkbP2DAA1AL65Wfn2ncjK/jtQ==}
+    engines: {node: '>=8'}
 
-  '@csstools/postcss-color-function-display-p3-linear@1.0.1':
-    resolution: {integrity: sha512-E5qusdzhlmO1TztYzDIi8XPdPoYOjoTY6HBYBCYSj+Gn4gQRBlvjgPQXzfzuPQqt8EhkC/SzPKObg4Mbn8/xMg==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@stoplight/spectral-core@1.24.0':
+    resolution: {integrity: sha512-abKt++GFFaqwKiGTfPZ5O3nIv8s+1V7J5awCjWPBtCXn7ZKTEPzEF8tBYsM3ne+RMrQ8ORkHzKFu9QZhenmkPw==}
+    engines: {node: ^16.20 || ^18.18 || >= 20.17}
 
-  '@csstools/postcss-color-function@4.0.12':
-    resolution: {integrity: sha512-yx3cljQKRaSBc2hfh8rMZFZzChaFgwmO2JfFgFr1vMcF3C/uyy5I4RFIBOIWGq1D+XbKCG789CGkG6zzkLpagA==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@stoplight/spectral-formats@1.9.0':
+    resolution: {integrity: sha512-OmHZpeBdlWbDxAI43HR08vyVXY2D++YHBx9AWMQ6S2DH8aWWCvk64BJOJk161XsHJQuy/vnC8tRBIIKwSQPAsA==}
+    engines: {node: ^16.20 || ^18.18 || >= 20.17}
 
-  '@csstools/postcss-color-mix-function@3.0.12':
-    resolution: {integrity: sha512-4STERZfCP5Jcs13P1U5pTvI9SkgLgfMUMhdXW8IlJWkzOOOqhZIjcNhWtNJZes2nkBDsIKJ0CJtFtuaZ00moag==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@stoplight/spectral-functions@1.11.0':
+    resolution: {integrity: sha512-HFlFhI+q13GqG8pphY4nNGYq9+5L14dhR9xLqx+/H2/FmAouHTfNaqE4SygIhSmtMxfNDJ8G4qnjxiQRv1kPWA==}
+    engines: {node: ^16.20 || ^18.18 || >= 20.17}
 
-  '@csstools/postcss-color-mix-variadic-function-arguments@1.0.2':
-    resolution: {integrity: sha512-rM67Gp9lRAkTo+X31DUqMEq+iK+EFqsidfecmhrteErxJZb6tUoJBVQca1Vn1GpDql1s1rD1pKcuYzMsg7Z1KQ==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@stoplight/spectral-parsers@1.0.5':
+    resolution: {integrity: sha512-ANDTp2IHWGvsQDAY85/jQi9ZrF4mRrA5bciNHX+PUxPr4DwS6iv4h+FVWJMVwcEYdpyoIdyL+SRmHdJfQEPmwQ==}
+    engines: {node: ^16.20 || ^18.18 || >= 20.17}
 
-  '@csstools/postcss-content-alt-text@2.0.8':
-    resolution: {integrity: sha512-9SfEW9QCxEpTlNMnpSqFaHyzsiRpZ5J5+KqCu1u5/eEJAWsMhzT40qf0FIbeeglEvrGRMdDzAxMIz3wqoGSb+Q==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@stoplight/spectral-ref-resolver@1.0.5':
+    resolution: {integrity: sha512-gj3TieX5a9zMW29z3mBlAtDOCgN3GEc1VgZnCVlr5irmR4Qi5LuECuFItAq4pTn5Zu+sW5bqutsCH7D4PkpyAA==}
+    engines: {node: ^16.20 || ^18.18 || >= 20.17}
 
-  '@csstools/postcss-contrast-color-function@2.0.12':
-    resolution: {integrity: sha512-YbwWckjK3qwKjeYz/CijgcS7WDUCtKTd8ShLztm3/i5dhh4NaqzsbYnhm4bjrpFpnLZ31jVcbK8YL77z3GBPzA==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@stoplight/spectral-runtime@1.1.6':
+    resolution: {integrity: sha512-Y8rEDyMN4bSMJCrDs2shdcVHYyCnH3FvXRP4dBhha4Z8iJv+JPp7KqOV/hwVB/hWFC209upiwj2oDmLfR0qCDg==}
+    engines: {node: ^16.20 || ^18.18 || >= 20.17}
 
-  '@csstools/postcss-exponential-functions@2.0.9':
-    resolution: {integrity: sha512-abg2W/PI3HXwS/CZshSa79kNWNZHdJPMBXeZNyPQFbbj8sKO3jXxOt/wF7juJVjyDTc6JrvaUZYFcSBZBhaxjw==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@stoplight/types@13.20.0':
+    resolution: {integrity: sha512-2FNTv05If7ib79VPDA/r9eUet76jewXFH2y2K5vuge6SXbRHtWBhcaRmu+6QpF4/WRNoJj5XYRSwLGXDxysBGA==}
+    engines: {node: ^12.20 || >=14.13}
 
-  '@csstools/postcss-font-format-keywords@4.0.0':
-    resolution: {integrity: sha512-usBzw9aCRDvchpok6C+4TXC57btc4bJtmKQWOHQxOVKen1ZfVqBUuCZ/wuqdX5GHsD0NRSr9XTP+5ID1ZZQBXw==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@stoplight/types@13.6.0':
+    resolution: {integrity: sha512-dzyuzvUjv3m1wmhPfq82lCVYGcXG0xUYgqnWfCq3PCVR4BKFhjdkHrnJ+jIDoMKvXb05AZP/ObQF6+NpDo29IQ==}
+    engines: {node: ^12.20 || >=14.13}
 
-  '@csstools/postcss-gamut-mapping@2.0.11':
-    resolution: {integrity: sha512-fCpCUgZNE2piVJKC76zFsgVW1apF6dpYsqGyH8SIeCcM4pTEsRTWTLCaJIMKFEundsCKwY1rwfhtrio04RJ4Dw==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@stoplight/types@14.1.1':
+    resolution: {integrity: sha512-/kjtr+0t0tjKr+heVfviO9FrU/uGLc+QNX3fHJc19xsCNYqU7lVhaXxDmEID9BZTjG+/r9pK9xP/xU02XGg65g==}
+    engines: {node: ^12.20 || >=14.13}
 
-  '@csstools/postcss-gradients-interpolation-method@5.0.12':
-    resolution: {integrity: sha512-jugzjwkUY0wtNrZlFeyXzimUL3hN4xMvoPnIXxoZqxDvjZRiSh+itgHcVUWzJ2VwD/VAMEgCLvtaJHX+4Vj3Ow==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@stoplight/yaml-ast-parser@0.0.50':
+    resolution: {integrity: sha512-Pb6M8TDO9DtSVla9yXSTAxmo9GVEouq5P40DWXdOie69bXogZTkgvopCq+yEvTMA0F6PEvdJmbtTV3ccIp11VQ==}
 
-  '@csstools/postcss-hwb-function@4.0.12':
-    resolution: {integrity: sha512-mL/+88Z53KrE4JdePYFJAQWFrcADEqsLprExCM04GDNgHIztwFzj0Mbhd/yxMBngq0NIlz58VVxjt5abNs1VhA==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@stoplight/yaml@4.3.0':
+    resolution: {integrity: sha512-JZlVFE6/dYpP9tQmV0/ADfn32L9uFarHWxfcRhReKUnljz1ZiUM5zpX+PH8h5CJs6lao3TuFqnPm9IJJCEkE2w==}
+    engines: {node: '>=10.8'}
 
-  '@csstools/postcss-ic-unit@4.0.4':
-    resolution: {integrity: sha512-yQ4VmossuOAql65sCPppVO1yfb7hDscf4GseF0VCA/DTDaBc0Wtf8MTqVPfjGYlT5+2buokG0Gp7y0atYZpwjg==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@szmarczak/http-timer@5.0.1':
+    resolution: {integrity: sha512-+PmQX0PiAYPMeVYe237LJAYvOMYW1j2rH5YROyS3b4CTVJum34HfRvKvAzozHAQG0TnHNdUfY9nCeUyRAs//cw==}
+    engines: {node: '>=14.16'}
 
-  '@csstools/postcss-initial@2.0.1':
-    resolution: {integrity: sha512-L1wLVMSAZ4wovznquK0xmC7QSctzO4D0Is590bxpGqhqjboLXYA16dWZpfwImkdOgACdQ9PqXsuRroW6qPlEsg==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@types/cors@2.8.19':
+    resolution: {integrity: sha512-mFNylyeyqN93lfe/9CSxOGREz8cpzAhH+E93xJ4xWQf62V8sQ/24reV2nyzUWM6H6Xji+GGHpkbLe7pVoUEskg==}
 
-  '@csstools/postcss-is-pseudo-class@5.0.3':
-    resolution: {integrity: sha512-jS/TY4SpG4gszAtIg7Qnf3AS2pjcUM5SzxpApOrlndMeGhIbaTzWBzzP/IApXoNWEW7OhcjkRT48jnAUIFXhAQ==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@types/debug@4.1.13':
+    resolution: {integrity: sha512-KSVgmQmzMwPlmtljOomayoR89W4FynCAi3E8PPs7vmDVPe84hT+vGPKkJfThkmXs0x0jAaa9U8uW8bbfyS2fWw==}
 
-  '@csstools/postcss-light-dark-function@2.0.11':
-    resolution: {integrity: sha512-fNJcKXJdPM3Lyrbmgw2OBbaioU7yuKZtiXClf4sGdQttitijYlZMD5K7HrC/eF83VRWRrYq6OZ0Lx92leV2LFA==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@types/es-aggregate-error@1.0.6':
+    resolution: {integrity: sha512-qJ7LIFp06h1QE1aVxbVd+zJP2wdaugYXYfd6JxsyRMrYHaxb6itXPogW2tz+ylUJ1n1b+JF1PHyYCfYHm0dvUg==}
 
-  '@csstools/postcss-logical-float-and-clear@3.0.0':
-    resolution: {integrity: sha512-SEmaHMszwakI2rqKRJgE+8rpotFfne1ZS6bZqBoQIicFyV+xT1UF42eORPxJkVJVrH9C0ctUgwMSn3BLOIZldQ==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@types/estree-jsx@1.0.5':
+    resolution: {integrity: sha512-52CcUVNFyfb1A2ALocQw/Dd1BQFNmSdkuC3BkZ6iqhdMfQz7JWOFRuJFloOzjk+6WijU56m9oKXFAXc7o3Towg==}
 
-  '@csstools/postcss-logical-overflow@2.0.0':
-    resolution: {integrity: sha512-spzR1MInxPuXKEX2csMamshR4LRaSZ3UXVaRGjeQxl70ySxOhMpP2252RAFsg8QyyBXBzuVOOdx1+bVO5bPIzA==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@types/estree@1.0.9':
+    resolution: {integrity: sha512-GhdPgy1el4/ImP05X05Uw4cw2/M93BCUmnEvWZNStlCzEKME4Fkk+YpoA5OiHNQmoS7Cafb8Xa3Pya8m1Qrzeg==}
 
-  '@csstools/postcss-logical-overscroll-behavior@2.0.0':
-    resolution: {integrity: sha512-e/webMjoGOSYfqLunyzByZj5KKe5oyVg/YSbie99VEaSDE2kimFm0q1f6t/6Jo+VVCQ/jbe2Xy+uX+C4xzWs4w==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@types/hast@3.0.5':
+    resolution: {integrity: sha512-rp/ezSWaD1m44dPKICGhiskI13nVr7qTloFwDa/IYkhhf5nzwP+zIQcIJh3WIFSBOy/H1PzB40jPjMDksN4F+g==}
 
-  '@csstools/postcss-logical-resize@3.0.0':
-    resolution: {integrity: sha512-DFbHQOFW/+I+MY4Ycd/QN6Dg4Hcbb50elIJCfnwkRTCX05G11SwViI5BbBlg9iHRl4ytB7pmY5ieAFk3ws7yyg==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
-
-  '@csstools/postcss-logical-viewport-units@3.0.4':
-    resolution: {integrity: sha512-q+eHV1haXA4w9xBwZLKjVKAWn3W2CMqmpNpZUk5kRprvSiBEGMgrNH3/sJZ8UA3JgyHaOt3jwT9uFa4wLX4EqQ==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
-
-  '@csstools/postcss-media-minmax@2.0.9':
-    resolution: {integrity: sha512-af9Qw3uS3JhYLnCbqtZ9crTvvkR+0Se+bBqSr7ykAnl9yKhk6895z9rf+2F4dClIDJWxgn0iZZ1PSdkhrbs2ig==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@types/http-cache-semantics@4.2.0':
+    resolution: {integrity: sha512-L3LgimLHXtGkWikKnsPg0/VFx9OGZaC+eN1u4r+OB1XRqH3meBIAVC2zr1WdMH+RHmnRkqliQAOHNJ/E0j/e0Q==}
 
-  '@csstools/postcss-media-queries-aspect-ratio-number-values@3.0.5':
-    resolution: {integrity: sha512-zhAe31xaaXOY2Px8IYfoVTB3wglbJUVigGphFLj6exb7cjZRH9A6adyE22XfFK3P2PzwRk0VDeTJmaxpluyrDg==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@types/json-schema@7.0.15':
+    resolution: {integrity: sha512-5+fP8P8MFNC+AyZCDxrB2pkZFPGzqQWUzpSeuuVLvm8VMcorNYavBqoFcxK8bQz4Qsbn4oUEEem4wDLfcysGHA==}
 
-  '@csstools/postcss-nested-calc@4.0.0':
-    resolution: {integrity: sha512-jMYDdqrQQxE7k9+KjstC3NbsmC063n1FTPLCgCRS2/qHUbHM0mNy9pIn4QIiQGs9I/Bg98vMqw7mJXBxa0N88A==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@types/katex@0.16.8':
+    resolution: {integrity: sha512-trgaNyfU+Xh2Tc+ABIb44a5AYUpicB3uwirOioeOkNPPbmgRNtcWyDeeFRzjPZENO9Vq8gvVqfhaaXWLlevVwg==}
 
-  '@csstools/postcss-normalize-display-values@4.0.1':
-    resolution: {integrity: sha512-TQUGBuRvxdc7TgNSTevYqrL8oItxiwPDixk20qCB5me/W8uF7BPbhRrAvFuhEoywQp/woRsUZ6SJ+sU5idZAIA==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@types/mdast@4.0.4':
+    resolution: {integrity: sha512-kGaNbPh1k7AFzgpud/gMdvIm5xuECykRR+JnWKQno9TAXVa6WIVCGTPvYGekIDL4uwCZQSYbUxNBSb1aUo79oA==}
 
-  '@csstools/postcss-oklab-function@4.0.12':
-    resolution: {integrity: sha512-HhlSmnE1NKBhXsTnNGjxvhryKtO7tJd1w42DKOGFD6jSHtYOrsJTQDKPMwvOfrzUAk8t7GcpIfRyM7ssqHpFjg==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@types/mdx@2.0.14':
+    resolution: {integrity: sha512-T48PeuJtvLosNTPVhfnIp3i/n3a4g4Bad7YCq5k64D4u7NwDrAotikQ+5+sjtUvBmxCMlbo3dVL+C2dP0rWHzg==}
 
-  '@csstools/postcss-position-area-property@1.0.0':
-    resolution: {integrity: sha512-fUP6KR8qV2NuUZV3Cw8itx0Ep90aRjAZxAEzC3vrl6yjFv+pFsQbR18UuQctEKmA72K9O27CoYiKEgXxkqjg8Q==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@types/ms@2.1.0':
+    resolution: {integrity: sha512-GsCCIZDE/p3i96vtEqx+7dBUGXrc7zeSK3wwPHIaRThS+9OhWIXRqzs4d6k1SVU8g91DrNRWxWUGhp5KXQb2VA==}
 
-  '@csstools/postcss-progressive-custom-properties@4.2.1':
-    resolution: {integrity: sha512-uPiiXf7IEKtUQXsxu6uWtOlRMXd2QWWy5fhxHDnPdXKCQckPP3E34ZgDoZ62r2iT+UOgWsSbM4NvHE5m3mAEdw==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@types/nlcst@2.0.3':
+    resolution: {integrity: sha512-vSYNSDe6Ix3q+6Z7ri9lyWqgGhJTmzRjZRqyq15N0Z/1/UnVsno9G/N40NBijoYx2seFDIl0+B2mgAb9mezUCA==}
 
-  '@csstools/postcss-property-rule-prelude-list@1.0.0':
-    resolution: {integrity: sha512-IxuQjUXq19fobgmSSvUDO7fVwijDJaZMvWQugxfEUxmjBeDCVaDuMpsZ31MsTm5xbnhA+ElDi0+rQ7sQQGisFA==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@types/node@26.6.5':
+    resolution: {integrity: sha512-uMzsv9stDdofIZBx4UGh4Z9ZgXnGC9seRDscilBcTHAeOFk67MZg/k9bWVfO+bk4qZmG+l52hRnLwUiH2LnJTg==}
 
-  '@csstools/postcss-random-function@2.0.1':
-    resolution: {integrity: sha512-q+FQaNiRBhnoSNo+GzqGOIBKoHQ43lYz0ICrV+UudfWnEF6ksS6DsBIJSISKQT2Bvu3g4k6r7t0zYrk5pDlo8w==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@types/react@19.3.0':
+    resolution: {integrity: sha512-N0rFCuH9YoxG9/m61l9MfpJKfmLOVU0em7ipIz6TRgSSkvReLB9vL85GB+yr8Bs5leqpvg96JSwF4ZS1s4viQg==}
 
-  '@csstools/postcss-relative-color-syntax@3.0.12':
-    resolution: {integrity: sha512-0RLIeONxu/mtxRtf3o41Lq2ghLimw0w9ByLWnnEVuy89exmEEq8bynveBxNW3nyHqLAFEeNtVEmC1QK9MZ8Huw==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@types/unist@2.0.11':
+    resolution: {integrity: sha512-CmBKiL6NNo/OqgmMn95Fk9Whlp2mtvIv+KNpQKN2F4SjvrEesubTRWGYSg+BnWZOnlCaSTU1sMpsBOzgbYhnsA==}
 
-  '@csstools/postcss-scope-pseudo-class@4.0.1':
-    resolution: {integrity: sha512-IMi9FwtH6LMNuLea1bjVMQAsUhFxJnyLSgOp/cpv5hrzWmrUYU5fm0EguNDIIOHUqzXode8F/1qkC/tEo/qN8Q==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@types/unist@3.0.3':
+    resolution: {integrity: sha512-ko/gIFJRv177XgZsZcBwnqJN5x/Gien8qNOn0D5bQU/zAzVf9Zt3BlcUiLqhV9y4ARk0GbT3tnUiPNgnTXzc/Q==}
 
-  '@csstools/postcss-sign-functions@1.1.4':
-    resolution: {integrity: sha512-P97h1XqRPcfcJndFdG95Gv/6ZzxUBBISem0IDqPZ7WMvc/wlO+yU0c5D/OCpZ5TJoTt63Ok3knGk64N+o6L2Pg==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@types/urijs@1.19.26':
+    resolution: {integrity: sha512-wkXrVzX5yoqLnndOwFsieJA7oKM8cNkOKJtf/3vVGSUFkWDKZvFHpIl9Pvqb/T9UsawBBFMTTD8xu7sK5MWuvg==}
 
-  '@csstools/postcss-stepped-value-functions@4.0.9':
-    resolution: {integrity: sha512-h9btycWrsex4dNLeQfyU3y3w40LMQooJWFMm/SK9lrKguHDcFl4VMkncKKoXi2z5rM9YGWbUQABI8BT2UydIcA==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@types/ws@8.18.2':
+    resolution: {integrity: sha512-67MQl+fpWKVTT1NYdnmo3U4sc/xPo/zQBncVnI74qmQa0z/b+1g6iYqNmGCPbxO+zz2aklb08a0oHfegiVd0/w==}
 
-  '@csstools/postcss-syntax-descriptor-syntax-production@1.0.1':
-    resolution: {integrity: sha512-GneqQWefjM//f4hJ/Kbox0C6f2T7+pi4/fqTqOFGTL3EjnvOReTqO1qUQ30CaUjkwjYq9qZ41hzarrAxCc4gow==}
-    engines: {node: '>=18'}
+  '@typescript/vfs@1.6.5':
+    resolution: {integrity: sha512-gobLHQLmvQGJInFk31NvgMd1uYzRXsd8qgnOssyLD055R2QPnw1ubRbBQ4+T+5qC7IQVuYXdvNDE2G7tMDVHgw==}
     peerDependencies:
-      postcss: ^8.4
+      typescript: '*'
 
-  '@csstools/postcss-system-ui-font-family@1.0.0':
-    resolution: {integrity: sha512-s3xdBvfWYfoPSBsikDXbuorcMG1nN1M6GdU0qBsGfcmNR0A/qhloQZpTxjA3Xsyrk1VJvwb2pOfiOT3at/DuIQ==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  '@ungap/structured-clone@1.4.0':
+    resolution: {integrity: sha512-1mEZtMKPM09vDmQt5y7YvmN2+DFTP7Tg0EWXdic8/C6VRnpb33e4ghisCIE3WZjsE2N8mf+QV1Zqh7ZFYLWInQ==}
 
-  '@csstools/postcss-text-decoration-shorthand@4.0.3':
-    resolution: {integrity: sha512-KSkGgZfx0kQjRIYnpsD7X2Om9BUXX/Kii77VBifQW9Ih929hK0KNjVngHDH0bFB9GmfWcR9vJYJJRvw/NQjkrA==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  accepts@1.3.8:
+    resolution: {integrity: sha512-PYAthTa2m2VKxuvSD3DPC/Gy+U+sOA1LAuT8mkmRuvw+NACSaeXEQ+NHcVF7rONl6qcaxV3Uuemwawk+7+SJLw==}
+    engines: {node: '>= 0.6'}
 
-  '@csstools/postcss-trigonometric-functions@4.0.9':
-    resolution: {integrity: sha512-Hnh5zJUdpNrJqK9v1/E3BbrQhaDTj5YiX7P61TOvUhoDHnUmsNNxcDAgkQ32RrcWx9GVUvfUNPcUkn8R3vIX6A==}
-    engines: {node: '>=18'}
+  acorn-jsx@5.3.2:
+    resolution: {integrity: sha512-rq9s+JNhf0IChjtDXxllJ7g41oZk5SlXtp0LHwyA5cejwn7vKmKp4pPri6YEePv2PU65sAsegbXtIinmDFDXgQ==}
     peerDependencies:
-      postcss: ^8.4
+      acorn: ^6.0.0 || ^7.0.0 || ^8.0.0
 
-  '@csstools/postcss-unset-value@4.0.0':
-    resolution: {integrity: sha512-cBz3tOCI5Fw6NIFEwU3RiwK6mn3nKegjpJuzCndoGq3BZPkUjnsq7uQmIeMNeMbMk7YD2MfKcgCpZwX5jyXqCA==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  acorn@8.11.2:
+    resolution: {integrity: sha512-nc0Axzp/0FILLEVsm4fNwLCwMttvhEI263QtVPQcbpfZZ3ts0hLsZGOpE6czNlid7CJ9MlyH8reXkpsf3YUY4w==}
+    engines: {node: '>=0.4.0'}
+    hasBin: true
 
-  '@csstools/selector-resolve-nested@3.1.0':
-    resolution: {integrity: sha512-mf1LEW0tJLKfWyvn5KdDrhpxHyuxpbNwTIwOYLIvsTffeyOf85j5oIzfG0yosxDgx/sswlqBnESYUcQH0vgZ0g==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss-selector-parser: ^7.0.0
+  address@1.2.2:
+    resolution: {integrity: sha512-4B/qKCfeE/ODUaAUpSwfzazo5x29WD4r3vXiWsB7I2mSDAihwEqKO+g8GELZUQSSAo5e1XTYh3ZVfLyxBc12nA==}
+    engines: {node: '>= 10.0.0'}
 
-  '@csstools/selector-specificity@5.0.0':
-    resolution: {integrity: sha512-PCqQV3c4CoVm3kdPhyeZ07VmBRdH2EpMFA/pd9OASpOEC3aXNGoqPDAZ80D0cLpMBxnmk0+yNhGsEx31hq7Gtw==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss-selector-parser: ^7.0.0
+  adm-zip@0.6.0:
+    resolution: {integrity: sha512-XleryMhbuksdKtofnWZ9Sk+4CUTbms4Mb/EU32SZwToAyZ5RgVos/ki8n+yr0LWHOGKuakbXTuuYNHLQjhddgg==}
+    engines: {node: '>=14.0'}
 
-  '@csstools/utilities@2.0.0':
-    resolution: {integrity: sha512-5VdOr0Z71u+Yp3ozOx8T11N703wIFGVRgOWbOZMKgglPJsWA54MRIoMNVMa7shUToIhx5J8vX4sOZgD2XiihiQ==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  agent-base@6.0.2:
+    resolution: {integrity: sha512-RZNwNclF7+MS/8bDg70amg32dyeZGZxiDuQmZxKLAlQjr3jGyLx+4Kkk58UO7D2QdgFIQCovuSuZESne6RG6XQ==}
+    engines: {node: '>= 6.0.0'}
 
-  '@discoveryjs/json-ext@0.5.7':
-    resolution: {integrity: sha512-dBVuXR082gk3jsFp7Rd/JI4kytwGHecnCoTtXFb7DB6CNHp4rg5k1bhg0nWdLGLnOV71lmDzGQaLMy8iPLY0pw==}
-    engines: {node: '>=10.0.0'}
+  aggregate-error@4.0.1:
+    resolution: {integrity: sha512-0poP0T7el6Vq3rstR8Mn4V/IQrpBLO6POkUSrN7RhyY+GF/InCFShQzsQ39T25gkHhLgSLByyAz+Kjb+c2L98w==}
+    engines: {node: '>=12'}
 
-  '@docsearch/core@4.6.3':
-    resolution: {integrity: sha512-rUOujwIpxJRgD7+kicVsI3D5sqBvdiRTquzWBpTEXZs8ZXfGbfzpus5HqumaNYTppN2HvH8E2yNuRwYdHJeOlA==}
+  ajv-draft-04@1.0.0:
+    resolution: {integrity: sha512-mv00Te6nmYbRp5DCwclxtt7yV/joXJPGS7nM+97GdxvuttCOfgI3K4U25zboyeX0O+myI8ERluxQe5wljMmVIw==}
     peerDependencies:
-      '@types/react': '>= 16.8.0 < 20.0.0'
-      react: '>= 16.8.0 < 20.0.0'
-      react-dom: '>= 16.8.0 < 20.0.0'
+      ajv: ^8.5.0
     peerDependenciesMeta:
-      '@types/react':
-        optional: true
-      react:
-        optional: true
-      react-dom:
+      ajv:
         optional: true
 
-  '@docsearch/css@4.6.3':
-    resolution: {integrity: sha512-nlOwcXcsNAptQl4vlL4MA78qNJKO0Qlds5GuBjCoePgkebTXLSf8Qt1oyZ3YBshYupKXG9VRGEsk1zr23d+bzQ==}
-
-  '@docsearch/react@4.6.3':
-    resolution: {integrity: sha512-Bg2wdDsoQVlNCcEKuEJAU04tvHCqgx8rIu+uIoM4pRtcx3TBKJuXutJik3LTA8LRc9YEyHkrYUrmcC0D7BYf+g==}
+  ajv-errors@3.0.0:
+    resolution: {integrity: sha512-V3wD15YHfHz6y0KdhYFjyy9vWtEVALT9UrxfN3zqlI6dMioHnJrqOYfyPKol3oqrnCM9uwkcdCwkJ0WUcbLMTQ==}
     peerDependencies:
-      '@types/react': '>= 16.8.0 < 20.0.0'
-      react: '>= 16.8.0 < 20.0.0'
-      react-dom: '>= 16.8.0 < 20.0.0'
-      search-insights: '>= 1 < 3'
-    peerDependenciesMeta:
-      '@types/react':
-        optional: true
-      react:
-        optional: true
-      react-dom:
-        optional: true
-      search-insights:
-        optional: true
-
-  '@docusaurus/babel@3.10.1':
-    resolution: {integrity: sha512-DZzFO1K3v/GoEt1fx1DiYHF4en+PuhtQf1AkQJa5zu3CoeKSpr5cpQRUlz3jr0m44wyzmSXu9bVpfir+N4+8bg==}
-    engines: {node: '>=20.0'}
+      ajv: ^8.0.1
 
-  '@docusaurus/bundler@3.10.1':
-    resolution: {integrity: sha512-HIqQPvbqnnQRe4NsBd1774KRarjXqS6wHsWELtyuSs1gCfvixJO2jUGH/OEBtr1Gvzpw+ze5CjGMvSJ8UE1KUw==}
-    engines: {node: '>=20.0'}
+  ajv-formats@2.1.1:
+    resolution: {integrity: sha512-Wx0Kx52hxE7C18hkMEggYlEifqWZtYaRgouJor+WMdPnQyEK13vgEWyVNup7SoeeoLMsr4kf5h6dOW11I15MUA==}
     peerDependencies:
-      '@docusaurus/faster': '*'
+      ajv: ^8.0.0
     peerDependenciesMeta:
-      '@docusaurus/faster':
+      ajv:
         optional: true
 
-  '@docusaurus/core@3.10.1':
-    resolution: {integrity: sha512-3pf2fXXw0eVk8WnC3T4LIigRDupcpvngpKo9Vy7mYyBhuddc0klDUuZAIfzMoK6z05pdlk6EFC/vBSX43+1O5w==}
-    engines: {node: '>=20.0'}
-    hasBin: true
+  ajv-formats@3.0.1:
+    resolution: {integrity: sha512-8iUql50EUR+uUcdRQ3HDqa6EVyo3docL8g5WJ3FNcWmu62IbkGUue/pEyLBW8VGKKucTPgqeks4fIU1DA4yowQ==}
     peerDependencies:
-      '@docusaurus/faster': '*'
-      '@mdx-js/react': ^3.0.0
-      react: ^18.0.0 || ^19.0.0
-      react-dom: ^18.0.0 || ^19.0.0
+      ajv: ^8.0.0
     peerDependenciesMeta:
-      '@docusaurus/faster':
+      ajv:
         optional: true
 
-  '@docusaurus/cssnano-preset@3.10.1':
-    resolution: {integrity: sha512-eNfHGcTKCSq6xmcavAkX3RRclHaE2xRCMParlDXLdXVP01/a2e/jKXMj/0ULnLFQSNwwuI62L0Ge8J+nZsR7UQ==}
-    engines: {node: '>=20.0'}
+  ajv@6.15.0:
+    resolution: {integrity: sha512-fgFx7Hfoq60ytK2c7DhnF8jIvzYgOMxfugjLOSMHjLIPgenqa7S7oaagATUq99mV6IYvN2tRmC0wnTYX6iPbMw==}
 
-  '@docusaurus/eslint-plugin@3.10.1':
-    resolution: {integrity: sha512-GS0zphpvFMCHUWalNrklew1gJo/44YzCrHPNFoka0asJnjfgnQDLl+KxCjWUXvw3U34NaVhwlJQaieClez8o/A==}
-    engines: {node: '>=20.0'}
-    peerDependencies:
-      eslint: '>=6'
+  ajv@8.20.0:
+    resolution: {integrity: sha512-Thbli+OlOj+iMPYFBVBfJ3OmCAnaSyNn4M1vz9T6Gka5Jt9ba/HIR56joy65tY6kx/FCF5VXNB819Y7/GUrBGA==}
 
-  '@docusaurus/faster@3.10.1':
-    resolution: {integrity: sha512-XTZhE5C1gZ/DaYYMlSk02dwP5vhpQON5QHVz1s3892mSESAywgWanURpXEDAvt4GvGuq7s+XP8rTWHZvfaJmdQ==}
-    engines: {node: '>=20.0'}
-    peerDependencies:
-      '@docusaurus/types': '*'
+  ansi-escapes@4.3.2:
+    resolution: {integrity: sha512-gKXj5ALrKWQLsYG9jlTRmR/xKluxHV+Z9QEwNIgCfM1/uwPMCuzVVnh5mwTd+OuBZcwSIMbqssNWRm1lE51QaQ==}
+    engines: {node: '>=8'}
 
-  '@docusaurus/logger@3.10.1':
-    resolution: {integrity: sha512-oPjNFnfJsRCkePVjkGrxWGq4MvJKRQT0r9jOP0eRBTZ7Wr9FAbzdP/Gjs0I2Ss6YRkPoEgygKG112OkE6skvJw==}
-    engines: {node: '>=20.0'}
+  ansi-escapes@7.3.0:
+    resolution: {integrity: sha512-BvU8nYgGQBxcmMuEeUEmNTvrMVjJNSH7RgW24vXexN4Ven6qCvy4TntnvlnwnMLTVlcRQQdbRY8NKnaIoeWDNg==}
+    engines: {node: '>=18'}
 
-  '@docusaurus/mdx-loader@3.10.1':
-    resolution: {integrity: sha512-GRmeb/wQ+iXRrFwcHBfgQhrJxGElgCsoTWZYDhccjsZVne1p8MK/EpQVIloXttz76TCe78kKD5AEG9n1xc1oxQ==}
-    engines: {node: '>=20.0'}
-    peerDependencies:
-      react: ^18.0.0 || ^19.0.0
-      react-dom: ^18.0.0 || ^19.0.0
+  ansi-regex@5.0.1:
+    resolution: {integrity: sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==}
+    engines: {node: '>=8'}
 
-  '@docusaurus/module-type-aliases@3.10.1':
-    resolution: {integrity: sha512-YoOZKUdGlp8xSYhuAkGdSo5Ydkbq4V4eK3sD8v0a2hloxCWdQbNBhkc+Ko9QyjpESc0BYcIGM5iHVAy5hdFV6w==}
-    peerDependencies:
-      react: '*'
-      react-dom: '*'
+  ansi-regex@6.2.2:
+    resolution: {integrity: sha512-Bq3SmSpyFHaWjPk8If9yc6svM8c56dB5BAtW4Qbw5jHTwwXXcTLoRMkpDJp6VL0XzlWaCHTXrkFURMYmD0sLqg==}
+    engines: {node: '>=12'}
 
-  '@docusaurus/plugin-content-blog@3.10.1':
-    resolution: {integrity: sha512-mmkgE6Q2+K74tnkou7tXlpDLvoCU/qkSa2GSQ3XUiHWvcebCoDQzS670RR3tO8PmaWlIyWWISYWzZLuMfxunRA==}
-    engines: {node: '>=20.0'}
-    peerDependencies:
-      '@docusaurus/plugin-content-docs': '*'
-      react: ^18.0.0 || ^19.0.0
-      react-dom: ^18.0.0 || ^19.0.0
+  ansi-styles@4.3.0:
+    resolution: {integrity: sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==}
+    engines: {node: '>=8'}
 
-  '@docusaurus/plugin-content-docs@3.10.1':
-    resolution: {integrity: sha512-2jRVrtzjf8LClGTHQlwlwuD3wQXRx3WEoF7XUarJ8Ou+0onV+SLtejsyfY9JLpfUh9hPhXM4pbBGkyAY4Bi3HQ==}
-    engines: {node: '>=20.0'}
-    peerDependencies:
-      react: ^18.0.0 || ^19.0.0
-      react-dom: ^18.0.0 || ^19.0.0
+  ansi-styles@6.2.3:
+    resolution: {integrity: sha512-4Dj6M28JB+oAH8kFkTLUo+a2jwOFkuqb3yucU0CANcRRUbxS0cP0nZYCGjcc3BNXwRIsUVmDGgzawme7zvJHvg==}
+    engines: {node: '>=12'}
 
-  '@docusaurus/plugin-content-pages@3.10.1':
-    resolution: {integrity: sha512-huJpaRPMl42nsFwuCXvV8bVDj2MazuwRJIUylI/RSlmZeJssVoZXeCjVf1y+1Drtpa9SKcdGn8yoJ76IRJijtw==}
-    engines: {node: '>=20.0'}
-    peerDependencies:
-      react: ^18.0.0 || ^19.0.0
-      react-dom: ^18.0.0 || ^19.0.0
+  any-promise@1.3.0:
+    resolution: {integrity: sha512-7UvmKalWRt1wgjL1RrGxoSJW/0QZFIegpeGvZG9kjp8vrRu55XTHbwnqq2GpXm9uLbcuhxm3IqX9OB4MZR1b2A==}
 
-  '@docusaurus/plugin-css-cascade-layers@3.10.1':
-    resolution: {integrity: sha512-r//fn+MNHkE1wCof8T29VAQezt1enGCpsFxoziBbvLgBM4JfXN2P3rxrBaavHmvLvm7lYkpJeitcDthwnmWCTw==}
-    engines: {node: '>=20.0'}
+  anymatch@3.1.3:
+    resolution: {integrity: sha512-KMReFUr0B4t+D+OBkjR3KYqvocp2XaSzO55UcB6mgQMd3KbcE+mWTyvVV7D/zsdEbNnV6acZUutkiHQXvTr1Rw==}
+    engines: {node: '>= 8'}
 
-  '@docusaurus/plugin-debug@3.10.1':
-    resolution: {integrity: sha512-9KqOpKNfAyqGZykRb9LhIT/vyRF6sm/ykhjj/39JvaJahDS+jZJE0Z1Wfz9q3DUNDTMNN0Q7u/kk4rKKU+IJuA==}
-    engines: {node: '>=20.0'}
-    peerDependencies:
-      react: ^18.0.0 || ^19.0.0
-      react-dom: ^18.0.0 || ^19.0.0
+  anynum@1.0.1:
+    resolution: {integrity: sha512-N6//FLET/tXYNM/F6ABca1oH6fWB+KlTt909Le28WMDBk8oaT4vY17DCrwg2MvmuqUKt3Ni4N5dGJ/EoBgcO6A==}
 
-  '@docusaurus/plugin-google-analytics@3.10.1':
-    resolution: {integrity: sha512-8o0P1KtmgdYQHH+oInitPpRWI0Of5XednAX4+DMhQNSmGSRNrsEEHg1ebv35m9AgRClfAytCJ5jA9KvcASTyuA==}
-    engines: {node: '>=20.0'}
-    peerDependencies:
-      react: ^18.0.0 || ^19.0.0
-      react-dom: ^18.0.0 || ^19.0.0
+  arg@5.0.2:
+    resolution: {integrity: sha512-PYjyFOLKQ9y57JvQ6QLo8dAgNqswh8M1RMJYdQduT6xbWSgK36P/Z/v+p888pM69jMMfS8Xd8F6I1kQ/I9HUGg==}
 
-  '@docusaurus/plugin-google-gtag@3.10.1':
-    resolution: {integrity: sha512-pu3xIUo5o/zCMLfUY9BO5KOwSH0zIsAGyFRPvXHayFSA5XIhCU/SFuB0g0ZNjFn9niZLCaNvoeAuOGFJZq0fdw==}
-    engines: {node: '>=20.0'}
-    peerDependencies:
-      react: ^18.0.0 || ^19.0.0
-      react-dom: ^18.0.0 || ^19.0.0
+  argparse@1.0.10:
+    resolution: {integrity: sha512-o5Roy6tNG4SL/FOkCAN6RzjiakZS25RLYFrcMttJqbdd8BWrnA+fGz57iN5Pb06pvBGvl5gQ0B48dJlslXvoTg==}
 
-  '@docusaurus/plugin-google-tag-manager@3.10.1':
-    resolution: {integrity: sha512-f6fyGHiCm7kJHBtAisGQS5oNBnpnMTYQZxDXeVrnw/3zWU+LMA22pr6UHGYkBKDbN+qPC5QHG3NuOfzQLq3+Lw==}
-    engines: {node: '>=20.0'}
-    peerDependencies:
-      react: ^18.0.0 || ^19.0.0
-      react-dom: ^18.0.0 || ^19.0.0
+  argparse@2.0.1:
+    resolution: {integrity: sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q==}
 
-  '@docusaurus/plugin-sitemap@3.10.1':
-    resolution: {integrity: sha512-C26MbmmqgdjkDq1htaZ3aD7LzEDKFWXfpyQpt0EOUThuq5nV77zDaedV20yHcVo9p+3ey9aZ4pbHA0D3QcZTzg==}
-    engines: {node: '>=20.0'}
-    peerDependencies:
-      react: ^18.0.0 || ^19.0.0
-      react-dom: ^18.0.0 || ^19.0.0
+  arkregex@0.0.13:
+    resolution: {integrity: sha512-c17sqCqiiZauxyoU1KZ2zbzCgeghGmc8dR2CrdQnlEtpq3bLhRLoLrxTL52M/8yQD8e/i1/IBRpRCNAuqJa7xQ==}
 
-  '@docusaurus/plugin-svgr@3.10.1':
-    resolution: {integrity: sha512-6SFxsmjWFkVLDmBUvFK6i72QjUwqyQFe4Ovz+SUJophJjOyVG3ZZG5IQpBC/kX/Gfv1yWeU9nWauH6F6Q7QX/Q==}
-    engines: {node: '>=20.0'}
-    peerDependencies:
-      react: ^18.0.0 || ^19.0.0
-      react-dom: ^18.0.0 || ^19.0.0
+  arktype@2.2.8:
+    resolution: {integrity: sha512-tZyLza7kO2vN8BXBKcj4t43IVMe8/ZyqlITH0chZv7FfEw+edLovpY922tqcK4mCjTpf4oNo2xV6np7tquP1ww==}
 
-  '@docusaurus/preset-classic@3.10.1':
-    resolution: {integrity: sha512-YO/FL8v1zmbxoTso6mjMz/RDjhaTJxb1UpFFTDdY5847LLDCeyYiYlrhyTbgN1RIN3xnkLKZ9Lj1x8hUzI4JOg==}
-    engines: {node: '>=20.0'}
-    peerDependencies:
-      react: ^18.0.0 || ^19.0.0
-      react-dom: ^18.0.0 || ^19.0.0
+  array-buffer-byte-length@1.0.2:
+    resolution: {integrity: sha512-LHE+8BuR7RYGDKvnrmcuSq3tDcKv9OFEXQt/HpbZhY7V6h0zlUXutnAD82GiFx9rdieCMjkvtcsPqBwgUl1Iiw==}
+    engines: {node: '>= 0.4'}
 
-  '@docusaurus/react-loadable@6.0.0':
-    resolution: {integrity: sha512-YMMxTUQV/QFSnbgrP3tjDzLHRg7vsbMn8e9HAa8o/1iXoiomo48b7sk/kkmWEuWNDPJVlKSJRB6Y2fHqdJk+SQ==}
-    peerDependencies:
-      react: '*'
+  array-flatten@1.1.1:
+    resolution: {integrity: sha512-PCVAQswWemu6UdxsDFFX/+gVeYqKAod3D3UVm91jHwynguOwAvYPhx8nNlM++NqRcK6CxxpUafjmhIdKiHibqg==}
 
-  '@docusaurus/remark-plugin-npm2yarn@3.10.1':
-    resolution: {integrity: sha512-HNxVv5Y9yx934/WLZBHJC7dYua7DVAHvhMl3hbQuzYGOghClP30Rt3hjZ0tqj/K7KqbSbVN0T4M1rBGk+e3t9A==}
-    engines: {node: '>=20.0'}
+  array-iterate@2.0.1:
+    resolution: {integrity: sha512-I1jXZMjAgCMmxT4qxXfPXa6SthSoE8h6gkSI9BGGNv8mP8G/v0blc+qFnZu6K42vTOiuME596QaLO0TP3Lk0xg==}
 
-  '@docusaurus/theme-classic@3.10.1':
-    resolution: {integrity: sha512-VU1RK0qb2pab0si4r7HFK37cYco8VzqLj3u1PspVipSr/z/GPVKHO4/HXbnePqHoWDk8urjyGSeatH0NIMBM1A==}
-    engines: {node: '>=20.0'}
-    peerDependencies:
-      react: ^18.0.0 || ^19.0.0
-      react-dom: ^18.0.0 || ^19.0.0
+  arraybuffer.prototype.slice@1.0.4:
+    resolution: {integrity: sha512-BNoCY6SXXPQ7gF2opIP4GBE+Xw7U+pHMYKuzjgCN3GwiaIR09UUeKfheyIry77QtrCBlC0KK0q5/TER/tYh3PQ==}
+    engines: {node: '>= 0.4'}
 
-  '@docusaurus/theme-common@3.10.1':
-    resolution: {integrity: sha512-0YtmIeoNo1fIw65LO8+/1dPgmDV86UmhMkow37gzjytuiCSQm9xob6PJy0L4kuQEMTLfUOGvkXvZr7GPrHquMA==}
-    engines: {node: '>=20.0'}
-    peerDependencies:
-      '@docusaurus/plugin-content-docs': '*'
-      react: ^18.0.0 || ^19.0.0
-      react-dom: ^18.0.0 || ^19.0.0
+  astring@1.9.0:
+    resolution: {integrity: sha512-LElXdjswlqjWrPpJFg1Fx4wpkOCxj1TDHlSV4PlaRxHGWko024xICaa97ZkMfs6DRKlCguiAI+rbXv5GWwXIkg==}
+    hasBin: true
 
-  '@docusaurus/theme-mermaid@3.10.1':
-    resolution: {integrity: sha512-2gxpmln8Pc4EN1oWzshQEx2HTs67jk14v7MmgqGs8ZU7Nm8oihg+fTouof2u4vN8DtB3Fln4cDJu4UprSX1S3Q==}
-    engines: {node: '>=20.0'}
-    peerDependencies:
-      '@mermaid-js/layout-elk': ^0.1.9
-      react: ^18.0.0 || ^19.0.0
-      react-dom: ^18.0.0 || ^19.0.0
-    peerDependenciesMeta:
-      '@mermaid-js/layout-elk':
-        optional: true
+  async-function@1.0.0:
+    resolution: {integrity: sha512-hsU18Ae8CDTR6Kgu9DYf0EbCr/a5iGL0rytQDobUcdpYOKokk8LEjVphnXkDkgpi0wYVsqrXuP0bZxJaTqdgoA==}
+    engines: {node: '>= 0.4'}
 
-  '@docusaurus/theme-search-algolia@3.10.1':
-    resolution: {integrity: sha512-OTaARARVZj2GvkJQjB+1jOIxntRaXea+G+fMsNqrZBAU1O1vJKDW22R7kECOHW27oJCLFN9HKaZeRrfAUyviug==}
-    engines: {node: '>=20.0'}
-    peerDependencies:
-      react: ^18.0.0 || ^19.0.0
-      react-dom: ^18.0.0 || ^19.0.0
+  asynckit@0.4.0:
+    resolution: {integrity: sha512-Oei9OH4tRh0YqU3GxhX79dM/mwVgvbZJaSNaRk+bshkj0S5cfHcgYakreBjrHwatXKbz+IoIdYLxrKim2MjW0Q==}
 
-  '@docusaurus/theme-translations@3.10.1':
-    resolution: {integrity: sha512-cLMyaKivjBVWKMJuWqyFVVgtqe8DPJNPkog0bn8W1MDVAKcPdxRFycBfC1We1RaNp7Rdk513bmtW78RR6OBxBw==}
-    engines: {node: '>=20.0'}
+  auto-bind@5.0.1:
+    resolution: {integrity: sha512-ooviqdwwgfIfNmDwo94wlshcdzfO64XV0Cg6oDsDYBJfITDz1EngD2z7DkbvCWn+XIMsIqW27sEVF6qcpJrRcg==}
+    engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
 
-  '@docusaurus/tsconfig@3.10.1':
-    resolution: {integrity: sha512-rYvB7yqkdqWIpAbDzQljGfM4cDBkLTbhmagZBEcsyj6oPUsz47lmW2pYdN1j+7sGFgltbAmQH62xfbrij4Eh6Q==}
+  available-typed-arrays@1.0.7:
+    resolution: {integrity: sha512-wvUjBtSGN7+7SjNpq/9M2Tg350UZD3q62IFZLbRAR1bSMlCo1ZaeW+BJ+D090e4hIIZLBcTDWe4Mh4jvUDajzQ==}
+    engines: {node: '>= 0.4'}
 
-  '@docusaurus/types@3.10.1':
-    resolution: {integrity: sha512-XYMK8k1szDCFMw2V+Xyen0g7Kee1sP3dtFnl7vkGkZOkeAJ/oPDQPL8iz4HBKOo/cwU8QeV6onVjMqtP+tFzsw==}
-    peerDependencies:
-      react: ^18.0.0 || ^19.0.0
-      react-dom: ^18.0.0 || ^19.0.0
+  avsc@5.7.9:
+    resolution: {integrity: sha512-yOA4wFeI7ET3v32Di/sUybQ+ttP20JHSW3mxLuNGeO0uD6PPcvLrIQXSvy/rhJOWU5JrYh7U4OHplWMmtAtjMg==}
+    engines: {node: '>=0.11'}
 
-  '@docusaurus/utils-common@3.10.1':
-    resolution: {integrity: sha512-5mFSgEADtnFxFH7RLw02QA5MpU5JVUCj0MPeIvi/aF4Fi45tQRIuTwXoXDqJ+1VfQJuYJGz3SI63wmGz4HvXzA==}
-    engines: {node: '>=20.0'}
+  axios@1.18.0:
+    resolution: {integrity: sha512-E32NzpYKp++W7XRe52rHiXV2ehxmh3wbdgO7MHeFM+vqxLBYHzt0ElkiImtOBxtOmyp0yoC8C6uESVV84Y2/hw==}
 
-  '@docusaurus/utils-validation@3.10.1':
-    resolution: {integrity: sha512-cRv1X69jwaWv47waglllgZVWzeBFLhl53XT/XED/83BerVBTC5FTP8WTcVl8Z6sZOegDSwitu/wpCSPCDOT6lg==}
-    engines: {node: '>=20.0'}
+  bail@2.0.2:
+    resolution: {integrity: sha512-0xO6mYd7JB2YesxDKplafRpsiOzPt9V02ddPCLbY1xYGPOX24NTyN50qnUxgCPcSoYMhKpAuBTjQoRZCAkUDRw==}
 
-  '@docusaurus/utils@3.10.1':
-    resolution: {integrity: sha512-3ojeJry9xBYdJO6qoyyzqeJFSJBVx2mXhyDzSdjwL2+URFQMf+h25gG38iswGImicK0ELjTd1EL2xzk8hf3QPw==}
-    engines: {node: '>=20.0'}
+  balanced-match@1.0.2:
+    resolution: {integrity: sha512-3oSeUO0TMV67hN1AmbXsK4yaqU7tjiHlbxRDZOpH0KW9+CeX4bRAaX0Anxt0tx2MrpRpWwQaPwIlISEJhYU5Pw==}
 
-  '@emnapi/core@1.11.0':
-    resolution: {integrity: sha512-l9Oo58x0HOP5znGzVhYW9U3e5wVuA4LAZU2AGezTmkhO1CgQRFDhDg4nneHsu/t3WniXg9QrG2nIXL/ZS8ln8Q==}
+  base64-js@0.0.8:
+    resolution: {integrity: sha512-3XSA2cR/h/73EzlXXdU6YNycmYI7+kicTxks4eJg2g39biHR84slg2+des+p7iHYhbRg/udIS4TD53WabcOUkw==}
+    engines: {node: '>= 0.4'}
 
-  '@emnapi/runtime@1.11.0':
-    resolution: {integrity: sha512-55coeOFKHv1ywEcUXJtWU5f+Jr/W5tZDvZig8DLKSwUN1JpROQ4rk/SNOQiFWmaR/VKF4zuFyW1B8JduOSv6Pg==}
+  base64-js@1.5.1:
+    resolution: {integrity: sha512-AKpaYlHn8t4SVbOHCy+b5+KKgvR4vrsD8vbvrbiQJps7fKDTkjkDry6ji0rUJjC0kzbNePLwzxq8iypo41qeWA==}
 
-  '@emnapi/wasi-threads@1.2.2':
-    resolution: {integrity: sha512-c95qOXkHdydNKhscBTebqEC1CVAZpyqOfVfBzQ1qgzyl3gfeldUjIggDbIZgDKsHLgnsM+igH7TJ/eAasaVuMA==}
+  base64id@2.0.0:
+    resolution: {integrity: sha512-lGe34o6EHj9y3Kts9R4ZYs/Gr+6N7MCaMlIFA3F1R2O5/m7K06AxfSeO5530PEERE6/WyEg3lsuyw4GHlPZHog==}
+    engines: {node: ^4.5.0 || >= 5.9}
 
-  '@eslint-community/eslint-utils@4.10.1':
-    resolution: {integrity: sha512-cuadcxVFE8sDK6iWJbs8Sn0av2Nrh2QSGQhVlBW9AaAHqHwjWsZHT8LJ4hFGPh7ASBV2deFdM7H/DPjulmh8rg==}
-    engines: {node: ^12.22.0 || ^14.17.0 || >=16.0.0}
-    peerDependencies:
-      eslint: ^6.0.0 || ^7.0.0 || >=8.0.0
+  better-opn@3.0.2:
+    resolution: {integrity: sha512-aVNobHnJqLiUelTaHat9DZ1qM2w0C0Eym4LPI/3JxOnSokGVdsl1T1kN7TFvsEAD8G47A6VKQ0TVHqbBnYMJlQ==}
+    engines: {node: '>=12.0.0'}
 
-  '@eslint-community/eslint-utils@4.9.1':
-    resolution: {integrity: sha512-phrYmNiYppR7znFEdqgfWHXR6NCkZEK7hwWDHZUjit/2/U0r6XvkDl0SYnoM51Hq7FhCGdLDT6zxCCOY1hexsQ==}
-    engines: {node: ^12.22.0 || ^14.17.0 || >=16.0.0}
-    peerDependencies:
-      eslint: ^6.0.0 || ^7.0.0 || >=8.0.0
+  binary-extensions@2.3.0:
+    resolution: {integrity: sha512-Ceh+7ox5qe7LJuLHoY0feh3pHuUDHAcRUeyL2VYghZwfpkNIy/+8Ocg0a3UuSoYzavmylwuLWQOf3hl0jjMMIw==}
+    engines: {node: '>=8'}
 
-  '@eslint-community/regexpp@4.12.2':
-    resolution: {integrity: sha512-EriSTlt5OC9/7SXkRSCAhfSxxoSUgBm33OH+IkwbdpgoqsSsUg7y3uh+IICI/Qg4BBWr3U2i39RpmycbxMq4ew==}
-    engines: {node: ^12.0.0 || ^14.0.0 || >=16.0.0}
+  bl@4.1.0:
+    resolution: {integrity: sha512-1W07cM9gS6DcLperZfFSj+bWLtaPGSOHWhPiGzXmvVJbRLdG82sH/Kn8EtW1VqWVA54AKf2h5k5BbnIbwF3h6w==}
 
-  '@eslint/config-array@0.23.5':
-    resolution: {integrity: sha512-Y3kKLvC1dvTOT+oGlqNQ1XLqK6D1HU2YXPc52NmAlJZbMMWDzGYXMiPRJ8TYD39muD/OTjlZmNJ4ib7dvSrMBA==}
-    engines: {node: ^20.19.0 || ^22.13.0 || >=24}
+  body-parser@1.20.8:
+    resolution: {integrity: sha512-JNcyFQ64OiijEkPzUBTCe+hyPXUD/3LEldGQ6iF5LR1w00mx9o7xtDWHXBY2iItjdCFGoilOLNQbH943ut7pHA==}
+    engines: {node: '>= 0.8', npm: 1.2.8000 || >= 1.4.16}
 
-  '@eslint/config-helpers@0.6.0':
-    resolution: {integrity: sha512-ii6Bw9jJ2zi2cWA2Z+9/QZ/+3DX6kwaV5Q986D/CdP3Lap3w/pgQZ373FV7byY/i7L4IRH/G43I5dz1ClsCbpA==}
-    engines: {node: ^20.19.0 || ^22.13.0 || >=24}
+  brace-expansion@1.1.21:
+    resolution: {integrity: sha512-9zeA+KLZNNzglF2TPKRQEDyx6Yby7daAkuy8MiPzpXPsYDWi/DRM8jmwUDxokQjYqBpv5DgPiwD4h4ZZSy1Ujw==}
 
-  '@eslint/core@1.2.1':
-    resolution: {integrity: sha512-MwcE1P+AZ4C6DWlpin/OmOA54mmIZ/+xZuJiQd4SyB29oAJjN30UW9wkKNptW2ctp4cEsvhlLY/CsQ1uoHDloQ==}
-    engines: {node: ^20.19.0 || ^22.13.0 || >=24}
+  braces@3.0.3:
+    resolution: {integrity: sha512-yQbXgO/OSZVD2IsiLlro+7Hf6Q18EJrKSEsdoMzKePKXct3gvD8oLcOQdIzGupr5Fj+EDe8gO/lxc1BzfMpxvA==}
+    engines: {node: '>=8'}
 
-  '@eslint/eslintrc@3.3.5':
-    resolution: {integrity: sha512-4IlJx0X0qftVsN5E+/vGujTRIFtwuLbNsVUe7TO6zYPDR1O6nFwvwhIKEKSrl6dZchmYBITazxKoUYOjdtjlRg==}
-    engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
+  buffer@5.7.1:
+    resolution: {integrity: sha512-EHcyIPBQ4BSGlvjB16k5KgAJ27CIsHY/2JBmCRReo48y9rQ3MaUzWX3KVlBa4U7MyX02HdVj0K7C3WaB3ju7FQ==}
 
-  '@eslint/js@10.0.1':
-    resolution: {integrity: sha512-zeR9k5pd4gxjZ0abRoIaxdc7I3nDktoXZk2qOv9gCNWx3mVwEn32VRhyLaRsDiJjTs0xq/T8mfPtyuXu7GWBcA==}
-    engines: {node: ^20.19.0 || ^22.13.0 || >=24}
-    peerDependencies:
-      eslint: ^10.0.0
-    peerDependenciesMeta:
-      eslint:
-        optional: true
+  bytes@3.1.2:
+    resolution: {integrity: sha512-/Nf7TyzTx6S3yRJObOAV7956r8cr2+Oj8AC5dt8wSP3BQAoeX58NoHyCU8P8zGkNXStjTSi6fzO6F0pBdcYbEg==}
+    engines: {node: '>= 0.8'}
 
-  '@eslint/object-schema@3.0.5':
-    resolution: {integrity: sha512-vqTaUEgxzm+YDSdElad6PiRoX4t8VGDjCtt05zn4nU810UIx/uNEV7/lZJ6KwFThKZOzOxzXy48da+No7HZaMw==}
-    engines: {node: ^20.19.0 || ^22.13.0 || >=24}
+  cacheable-lookup@7.0.0:
+    resolution: {integrity: sha512-+qJyx4xiKra8mZrcwhjMRMUhD5NR1R8esPkzIYxX96JiecFoxAXFuz/GpR3+ev4PE1WamHip78wV0vcmPQtp8w==}
+    engines: {node: '>=14.16'}
 
-  '@eslint/plugin-kit@0.7.2':
-    resolution: {integrity: sha512-+CNAzxglkrpNf/kKywqQfk74QjtceuOE7Qm+AF8miRvPF/wmmK5+OJOgVh3AVTT3RP2mH3+FOaxlE5v72owk0A==}
-    engines: {node: ^20.19.0 || ^22.13.0 || >=24}
+  cacheable-request@10.2.14:
+    resolution: {integrity: sha512-zkDT5WAF4hSSoUgyfg5tFIxz8XQK+25W/TLVojJTMKBaxevLBBtLxgqguAuVQB8PVW79FVjHcU+GJ9tVbDZ9mQ==}
+    engines: {node: '>=14.16'}
 
-  '@exodus/schemasafe@1.3.0':
-    resolution: {integrity: sha512-5Aap/GaRupgNx/feGBwLLTVv8OQFfv3pq2lPRzPg9R+IOBnDgghTGW7l7EuVXOvg5cc/xSAlRW8rBrjIC3Nvqw==}
+  call-bind-apply-helpers@1.0.2:
+    resolution: {integrity: sha512-Sp1ablJ0ivDkSzjcaJdxEunN5/XvksFJ2sMBFfq6x0ryhQV/2b/KwFe21cMpmHtPOSij8K99/wSfoEuTObmuMQ==}
+    engines: {node: '>= 0.4'}
 
-  '@faker-js/faker@5.5.3':
-    resolution: {integrity: sha512-R11tGE6yIFwqpaIqcfkcg7AICXzFg14+5h5v0TfF/9+RMDL6jhzCy/pxHVOfbALGdtVYdt6JdR21tuxEgl34dw==}
-    deprecated: Please update to a newer version.
+  call-bind@1.0.9:
+    resolution: {integrity: sha512-a/hy+pNsFUTR+Iz8TCJvXudKVLAnz/DyeSUo10I5yvFDQJBFU2s9uqQpoSrJlroHUKoKqzg+epxyP9lqFdzfBQ==}
+    engines: {node: '>= 0.4'}
 
-  '@fortawesome/fontawesome-common-types@6.7.2':
-    resolution: {integrity: sha512-Zs+YeHUC5fkt7Mg1l6XTniei3k4bwG/yo3iFUtZWd/pMx9g3fdvkSK9E0FOC+++phXOka78uJcYb8JaFkW52Xg==}
-    engines: {node: '>=6'}
+  call-bound@1.0.4:
+    resolution: {integrity: sha512-+ys997U96po4Kx/ABpBCqhA9EuxJaQWDQg7295H4hBphv3IZg0boBKuwYpt4YXp6MZ5AmZQnU/tyMTlRpaSejg==}
+    engines: {node: '>= 0.4'}
 
-  '@fortawesome/fontawesome-svg-core@6.7.2':
-    resolution: {integrity: sha512-yxtOBWDrdi5DD5o1pmVdq3WMCvnobT0LU6R8RyyVXPvFRd2o79/0NCuQoCjNTeZz9EzA9xS3JxNWfv54RIHFEA==}
-    engines: {node: '>=6'}
+  camelcase-css@2.0.1:
+    resolution: {integrity: sha512-QOSvevhslijgYwRx6Rv7zKdMF8lbRmx+uQGx2+vDc+KI/eBnsy9kit5aj23AgGu3pa4t9AgwbnXWqS+iOY+2aA==}
+    engines: {node: '>= 6'}
 
-  '@fortawesome/react-fontawesome@0.2.6':
-    resolution: {integrity: sha512-mtBFIi1UsYQo7rYonYFkjgYKGoL8T+fEH6NGUpvuqtY3ytMsAoDaPo5rk25KuMtKDipY4bGYM/CkmCHA1N3FUg==}
-    deprecated: v0.2.x is no longer supported. Unless you are still using FontAwesome 5, please update to v3.1.1 or greater.
-    peerDependencies:
-      '@fortawesome/fontawesome-svg-core': ~1 || ~6 || ~7
-      react: ^16.3 || ^17.0.0 || ^18.0.0 || ^19.0.0
+  camelize@1.0.1:
+    resolution: {integrity: sha512-dU+Tx2fsypxTgtLoE36npi3UqcjSSMNYfkqgmoEhtZrraP5VWq0K7FkWVTYa8eMPtnU/G2txVsfdCJTn9uzpuQ==}
 
-  '@hapi/hoek@9.3.0':
-    resolution: {integrity: sha512-/c6rf4UJlmHlC9b5BaNvzAcFv7HZ2QHaV0D4/HNlBdvFnvQq8RI4kYdhyPCl7Xj+oWvTWQ8ujhqS53LIgAe6KQ==}
+  ccount@2.0.1:
+    resolution: {integrity: sha512-eyrF0jiFpY+3drT6383f1qhkbGsLSifNAjA61IUjZjmLCWjItY6LB9ft9YhoDgwfmclB2zhu51Lc7+95b8NRAg==}
 
-  '@hapi/topo@5.1.0':
-    resolution: {integrity: sha512-foQZKJig7Ob0BMAYBfcJk8d77QtOe7Wo4ox7ff1lQYoNNAb6jwcY1ncdoy2e9wQZzvNy7ODZCYJkK8kzmcAnAg==}
+  chalk@5.2.0:
+    resolution: {integrity: sha512-ree3Gqw/nazQAPuJJEy+avdl7QfZMcUvmHIKgEZkGL+xOBzRvup5Hxo6LHuMceSxOabuJLJm5Yp/92R9eMmMvA==}
+    engines: {node: ^12.17.0 || ^14.13 || >=16.0.0}
 
-  '@hookform/error-message@2.0.1':
-    resolution: {integrity: sha512-U410sAr92xgxT1idlu9WWOVjndxLdgPUHEB8Schr27C9eh7/xUnITWpCMF93s+lGiG++D4JnbSnrb5A21AdSNg==}
-    peerDependencies:
-      react: '>=16.8.0'
-      react-dom: '>=16.8.0'
-      react-hook-form: ^7.0.0
+  chalk@5.3.0:
+    resolution: {integrity: sha512-dLitG79d+GV1Nb/VYcCDFivJeK1hiukt9QjRNVOsUtTy1rR1YJsmpGGTZ3qJos+uw7WmWF4wUwBd9jxjocFC2w==}
+    engines: {node: ^12.17.0 || ^14.13 || >=16.0.0}
 
-  '@humanfs/core@0.19.2':
-    resolution: {integrity: sha512-UhXNm+CFMWcbChXywFwkmhqjs3PRCmcSa/hfBgLIb7oQ5HNb1wS0icWsGtSAUNgefHeI+eBrA8I1fxmbHsGdvA==}
-    engines: {node: '>=18.18.0'}
+  chalk@5.6.2:
+    resolution: {integrity: sha512-7NzBL0rN6fMUW+f7A6Io4h40qQlG+xGmtMxfbnH/K7TAtt8JQWVQK+6g0UXKMeVJoyV5EkkNsErQ8pVD3bLHbA==}
+    engines: {node: ^12.17.0 || ^14.13 || >=16.0.0}
 
-  '@humanfs/node@0.16.8':
-    resolution: {integrity: sha512-gE1eQNZ3R++kTzFUpdGlpmy8kDZD/MLyHqDwqjkVQI0JMdI1D51sy1H958PNXYkM2rAac7e5/CnIKZrHtPh3BQ==}
-    engines: {node: '>=18.18.0'}
+  character-entities-html4@2.1.0:
+    resolution: {integrity: sha512-1v7fgQRj6hnSwFpq1Eu0ynr/CDEw0rXo2B61qXrLNdHZmPKgb7fqS1a2JwF0rISo9q77jDI8VMEHoApn8qDoZA==}
 
-  '@humanfs/types@0.15.0':
-    resolution: {integrity: sha512-ZZ1w0aoQkwuUuC7Yf+7sdeaNfqQiiLcSRbfI08oAxqLtpXQr9AIVX7Ay7HLDuiLYAaFPu8oBYNq/QIi9URHJ3Q==}
-    engines: {node: '>=18.18.0'}
+  character-entities-legacy@3.0.0:
+    resolution: {integrity: sha512-RpPp0asT/6ufRm//AJVwpViZbGM/MkjQFxJccQRHmISF/22NBtsHqAWmL+/pmkPWoIUJdWyeVleTl1wydHATVQ==}
 
-  '@humanwhocodes/module-importer@1.0.1':
-    resolution: {integrity: sha512-bxveV4V8v5Yb4ncFTT3rPSgZBOpCkjfK0y4oVVVJwIuDVBRMDXrPyXRL988i5ap9m9bnyEEjWfm5WkBmtffLfA==}
-    engines: {node: '>=12.22'}
+  character-entities@2.0.2:
+    resolution: {integrity: sha512-shx7oQ0Awen/BRIdkjkvz54PnEEI/EjwXDSIZp86/KKdbafHh1Df/RYGBhn4hbe2+uKC9FnT5UCEdyPz3ai9hQ==}
 
-  '@humanwhocodes/retry@0.4.3':
-    resolution: {integrity: sha512-bV0Tgo9K4hfPCek+aMAn81RppFKv2ySDQeMoSZuvTASywNTnVJCArCZE2FWqpvIatKu7VMRLWlR1EazvVhDyhQ==}
-    engines: {node: '>=18.18'}
+  character-reference-invalid@2.0.1:
+    resolution: {integrity: sha512-iBZ4F4wRbyORVsu0jPV7gXkOsGYjGHPmAyv+HiHG8gi5PtC9KI2j1+v8/tlibRvjoWX027ypmG/n0HtO5t7unw==}
 
-  '@iconify/types@2.0.0':
-    resolution: {integrity: sha512-+wluvCrRhXrhyOmRDJ3q8mux9JkKy5SJ/v8ol2tu4FVjyYvtEzkc/3pK15ET6RKg4b4w4BmTk1+gsCUhf21Ykg==}
+  chardet@2.2.0:
+    resolution: {integrity: sha512-rddelWYNPRrXq6PtNEN2S3f6t9ILzvqaN5pVgi4kqt9jHQaXIial9PznB5iSPVlQSLNaaH22ItWz3EJtQ10+OA==}
 
-  '@iconify/utils@3.1.3':
-    resolution: {integrity: sha512-LPKOXPn/zV+zis1oOfGWogaXVpqUybF3ZS6SCZIsz8vg0ivVp9+fVqyYB7xq0aiST/VhUQYGO1qo6uoYSiEJqw==}
+  chokidar@3.5.3:
+    resolution: {integrity: sha512-Dr3sfKRP6oTcjf2JmUmFJfeVMvXBdegxB0iVQ5eb2V10uFJUCAS8OByZdVAyVb8xXNz3GjjTgj9kLWsZTqE6kw==}
+    engines: {node: '>= 8.10.0'}
 
-  '@internationalized/date@3.12.2':
-    resolution: {integrity: sha512-FY1Y+H64NDs+HAF6omlnWxm3mEpfgaCSWtL5l551ZZfImA+kGjPFgrnJrGjH6lfmLL0g8Z/mBu1R3kufeCp6Jw==}
+  chokidar@3.6.0:
+    resolution: {integrity: sha512-7VT13fmjotKpGipCW9JEQAusEPE+Ei8nl6/g4FBAmIm0GOOLMua9NDDo/DWp0ZAxCr3cPq5ZpBqmPAQgDda2Pw==}
+    engines: {node: '>= 8.10.0'}
 
-  '@internationalized/date@3.12.3':
-    resolution: {integrity: sha512-fuLX+3ZKLsxI73y8b01EG/WjHb6gE6weCqlfawPO27kBWGMh9G1yH6Csv1uU7/cac9H2GHmOMt6CjmuQ1aia4Q==}
+  chownr@1.1.4:
+    resolution: {integrity: sha512-jJ0bqzaylmJtVnNgzTeSOs8DPavpbYgEr/b0YL8/2GO3xJEhInFmhKMUnEJQjZumK7KXGFhUy89PrsJWlakBVg==}
 
-  '@internationalized/number@3.6.7':
-    resolution: {integrity: sha512-3ji1fcrT+FPAK86UqEhB/psHixYo6niWPJtt7+qRaYFynt/BaJG8GhAPimtWUpEiVSTq8ZM8L5psMxGquiB/Vg==}
+  chownr@3.0.0:
+    resolution: {integrity: sha512-+IxzY9BZOQd/XuYPRmrvEVjF/nqj5kgT4kEq7VofrDoM1MxoRjEWkrCC3EtLi59TVawxTAn+orJwFQcrqEN1+g==}
+    engines: {node: '>=18'}
 
-  '@internationalized/string@3.2.10':
-    resolution: {integrity: sha512-PDx6//vHSpRnHfxqMqto11zQvhsaU74O3mKv2F/0eicGZcl9NLjQmGlbHz/LsJh5tLKp4A4L7ZVTzN1/MmMTvA==}
+  clean-stack@4.2.0:
+    resolution: {integrity: sha512-LYv6XPxoyODi36Dp976riBtSY27VmFo+MKqEU9QCCWyTrdEPDog+RWA7xQWHi6Vbp61j5c4cdzzX1NidnwtUWg==}
+    engines: {node: '>=12'}
 
-  '@internationalized/string@3.2.9':
-    resolution: {integrity: sha512-kzP/M/mbQxODlmOt4bIQZ2SBVUWUSqMLXooXixnX7noche8WHaQcA+nwFN1K2KCF/cp+LDUhcJsCicwkvhD1pg==}
+  cli-boxes@3.0.0:
+    resolution: {integrity: sha512-/lzGpEWL/8PfI0BmBOPRwp0c/wFNX1RdUML3jK/RcSBA9T8mZDdQpqYBKtCFTOfQbwPqWEOpjqW+Fnayc0969g==}
+    engines: {node: '>=10'}
 
-  '@jest/schemas@29.6.3':
-    resolution: {integrity: sha512-mo5j5X+jIZmJQveBKeS/clAueipV7KgiX1vMgCxam1RNYiqE1w62n0/tJJnHtjW8ZHcQco5gY85jA3mi0L+nSA==}
-    engines: {node: ^14.15.0 || ^16.10.0 || >=18.0.0}
+  cli-cursor@4.0.0:
+    resolution: {integrity: sha512-VGtlMu3x/4DOtIUwEkRezxUZ2lBacNJCHash0N0WeZDBS+7Ux1dm3XWAgWYxLJFMMdOeXMHXorshEFhbMSGelg==}
+    engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
 
-  '@jest/types@29.6.3':
-    resolution: {integrity: sha512-u3UPsIilWKOM3F9CXtrG8LEJmNxwoCQC/XVj4IKYXvvpx7QIi/Kg1LI5uDmDpKlac62NUtX7eLjRh+jVZcLOzw==}
-    engines: {node: ^14.15.0 || ^16.10.0 || >=18.0.0}
+  cli-spinners@2.9.2:
+    resolution: {integrity: sha512-ywqV+5MmyL4E7ybXgKys4DugZbX0FC6LnwrhjuykIjnK9k8OQacQ7axGKnjDXWNhns0xot3bZI5h55H8yo9cJg==}
+    engines: {node: '>=6'}
 
-  '@jridgewell/gen-mapping@0.3.13':
-    resolution: {integrity: sha512-2kkt/7niJ6MgEPxF0bYdQ6etZaA+fQvDcLKckhy1yIQOzaoKjBBjSj63/aLVjYE3qhRt5dvM+uUyfCg6UKCBbA==}
+  cli-truncate@4.0.0:
+    resolution: {integrity: sha512-nPdaFdQ0h/GEigbPClz11D0v/ZJEwxmeVZGeMo3Z5StPtUTkA9o1lD6QwoirYiSDzbcwn2XcjwmCp68W1IS4TA==}
+    engines: {node: '>=18'}
 
-  '@jridgewell/remapping@2.3.5':
-    resolution: {integrity: sha512-LI9u/+laYG4Ds1TDKSJW2YPrIlcVYOwi2fUC6xB43lueCjgxV4lffOCZCtYFiH6TNOX+tQKXx97T4IKHbhyHEQ==}
+  cli-width@4.1.0:
+    resolution: {integrity: sha512-ouuZd4/dm2Sw5Gmqy6bGyNNNe1qt9RpmxveLSO7KcgsTnU7RXfsw+/bukWGo1abgBiMAic068rclZsO4IWmmxQ==}
+    engines: {node: '>= 12'}
 
-  '@jridgewell/resolve-uri@3.1.2':
-    resolution: {integrity: sha512-bRISgCIjP20/tbWSPWMEi54QVPRZExkuD9lJL+UIxUKtwVJA8wW1Trb1jMs1RFXo1CBTNZ/5hpC9QvmKWdopKw==}
-    engines: {node: '>=6.0.0'}
+  cliui@8.0.1:
+    resolution: {integrity: sha512-BSeNnyus75C4//NQ9gQt1/csTXyo/8Sb+afLAkzAptFuMsod9HFokGNudZpi/oQV73hnVK+sR+5PVRMd+Dr7YQ==}
+    engines: {node: '>=12'}
 
-  '@jridgewell/source-map@0.3.11':
-    resolution: {integrity: sha512-ZMp1V8ZFcPG5dIWnQLr3NSI1MiCU7UETdS/A0G8V/XWHvJv3ZsFqutJn1Y5RPmAPX6F3BiE397OqveU/9NCuIA==}
+  cliui@9.0.1:
+    resolution: {integrity: sha512-k7ndgKhwoQveBL+/1tqGJYNz097I7WOvwbmmU2AR5+magtbjPWQTS1C5vzGkBC8Ym8UWRzfKUzUUqFLypY4Q+w==}
+    engines: {node: '>=20'}
 
-  '@jridgewell/sourcemap-codec@1.5.5':
-    resolution: {integrity: sha512-cYQ9310grqxueWbl+WuIUIaiUaDcj7WOq5fVhEljNVgRfOUhY9fy2zTvfoqWsnebh8Sl70VScFbICvJnLKB0Og==}
+  code-excerpt@4.0.0:
+    resolution: {integrity: sha512-xxodCmBen3iy2i0WtAK8FlFNrRzjUqjRsMfho58xT/wvZU1YTM3fCnRjcy1gJPMepaRlgm/0e6w8SpWHpn3/cA==}
+    engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
 
-  '@jridgewell/trace-mapping@0.3.31':
-    resolution: {integrity: sha512-zzNR+SdQSDJzc8joaeP8QQoCQr8NuYx2dIIytl1QeBEZHJ9uW6hebsrYgbz8hJwUQao3TWCMtmfV8Nu1twOLAw==}
+  collapse-white-space@2.1.0:
+    resolution: {integrity: sha512-loKTxY1zCOuG4j9f6EPnuyyYkf58RnhhWTvRoZEokgB+WbdXehfjFviyOVYkqzEWz1Q5kRiZdBYS5SwxbQYwzw==}
 
-  '@json-schema-spec/json-pointer@0.1.2':
-    resolution: {integrity: sha512-BYY7IavBjwsWWSmVcMz2A9mKiDD9RvacnsItgmy1xV8cmgbtxFfKmKMtkVpD7pYtkx4mIW4800yZBXueVFIWPw==}
+  color-convert@2.0.1:
+    resolution: {integrity: sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==}
+    engines: {node: '>=7.0.0'}
 
-  '@json-schema-tools/dereferencer@1.6.3':
-    resolution: {integrity: sha512-NoQkj6hx9Joqbd/GZAOHSGtE6R+OzlnOcDfyidmx8e/CUv1Q+Z6/fmZo2wwCQWiwP1pnGYc95iKwp8M7XlV7wQ==}
+  color-name@1.1.4:
+    resolution: {integrity: sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==}
 
-  '@json-schema-tools/meta-schema@1.8.0':
-    resolution: {integrity: sha512-pbRAbHidPTf96LhmHXA6bl4D4tz4HrwjZ7A5ConcLFPdCj+93GhsCCFsq+AWti4VOs+9QTezX5l0zLNA+TZv1g==}
+  color-string@1.9.1:
+    resolution: {integrity: sha512-shrVawQFojnZv6xM40anx4CkoDP+fZsw/ZerEMsW/pyzsRbElpsL/DBVW7q3ExxwusdNXI3lXpuhEZkzs8p5Eg==}
 
-  '@json-schema-tools/reference-resolver@1.2.6':
-    resolution: {integrity: sha512-4QZu5ROb5EpLSvV+buzk8WR30W+dffSNaKqD3VGFYJ3y0BLDi2OHoSz5e6NKcLYTyUYXV8IKxocNOszeVBJI4Q==}
+  color@4.2.3:
+    resolution: {integrity: sha512-1rXeuUUiGGrykh+CeBdu5Ie7OJwinCgQY0bc7GCRxy5xVHy+moaqkpL/jqQq0MtQOeYcrqEz4abc5f0KtU7W4A==}
+    engines: {node: '>=12.5.0'}
 
-  '@json-schema-tools/traverse@1.11.0':
-    resolution: {integrity: sha512-GWQRiXXsbt5ZuewItpW2nqB/D0x4pKWi6XXOwoh1wvmsU/tQSq/rKzpgGvOHTe6v30TYDwZYxuwnRnArIsUzLQ==}
+  combined-stream@1.0.8:
+    resolution: {integrity: sha512-FQN4MRfuJeHf7cBbBMJFXhKSDq+2kAArBlmRBvcvFE5BB1HZKXtSFASDhdlz9zOYwxh8lDdnvmMOe/+5cdoEdg==}
+    engines: {node: '>= 0.8'}
 
-  '@jsonjoy.com/base64@1.1.2':
-    resolution: {integrity: sha512-q6XAnWQDIMA3+FTiOYajoYqySkO+JSat0ytXGSuRdq9uXE7o92gzuQwQM14xaCRlBLGq3v5miDGC4vkVTn54xA==}
-    engines: {node: '>=10.0'}
-    peerDependencies:
-      tslib: '2'
+  comma-separated-tokens@2.0.3:
+    resolution: {integrity: sha512-Fu4hJdvzeylCfQPp9SGWidpzrMs7tTrlu6Vb8XGaRGck8QSNZJJp538Wrb60Lax4fPwR64ViY468OIUTbRlGZg==}
 
-  '@jsonjoy.com/base64@17.67.0':
-    resolution: {integrity: sha512-5SEsJGsm15aP8TQGkDfJvz9axgPwAEm98S5DxOuYe8e1EbfajcDmgeXXzccEjh+mLnjqEKrkBdjHWS5vFNwDdw==}
-    engines: {node: '>=10.0'}
-    peerDependencies:
-      tslib: '2'
+  commander@2.20.3:
+    resolution: {integrity: sha512-GpVkmM8vF2vQUkj2LvZmD35JxeJOLCwJ9cUkugyk2nuhbv3+mJvpLYYt+0+USMxE+oj+ey/lJEnhZw75x/OMcQ==}
 
-  '@jsonjoy.com/buffers@1.2.1':
-    resolution: {integrity: sha512-12cdlDwX4RUM3QxmUbVJWqZ/mrK6dFQH4Zxq6+r1YXKXYBNgZXndx2qbCJwh3+WWkCSn67IjnlG3XYTvmvYtgA==}
-    engines: {node: '>=10.0'}
-    peerDependencies:
-      tslib: '2'
+  commander@4.1.1:
+    resolution: {integrity: sha512-NOKm8xhkzAjzFx8B2v5OAHT+u5pRQc2UCa2Vq9jYL/31o2wi9mxBA7LIFs3sV5VSC49z6pEhfbMULvShKj26WA==}
+    engines: {node: '>= 6'}
 
-  '@jsonjoy.com/buffers@17.67.0':
-    resolution: {integrity: sha512-tfExRpYxBvi32vPs9ZHaTjSP4fHAfzSmcahOfNxtvGHcyJel+aibkPlGeBB+7AoC6hL7lXIE++8okecBxx7lcw==}
-    engines: {node: '>=10.0'}
-    peerDependencies:
-      tslib: '2'
+  commander@8.3.0:
+    resolution: {integrity: sha512-OkTL9umf+He2DZkUq8f8J9of7yL6RJKI24dVITBmNfZBmri9zYZQrKkuXiKhyfPSu8tUhnVBB1iKXevvnlR4Ww==}
+    engines: {node: '>= 12'}
 
-  '@jsonjoy.com/codegen@1.0.0':
-    resolution: {integrity: sha512-E8Oy+08cmCf0EK/NMxpaJZmOxPqM+6iSe2S4nlSBrPZOORoDJILxtbSUEDKQyTamm/BVAhIGllOBNU79/dwf0g==}
-    engines: {node: '>=10.0'}
-    peerDependencies:
-      tslib: '2'
+  compute-gcd@1.2.1:
+    resolution: {integrity: sha512-TwMbxBNz0l71+8Sc4czv13h4kEqnchV9igQZBi6QUaz09dnz13juGnnaWWJTRsP3brxOoxeB4SA2WELLw1hCtg==}
 
-  '@jsonjoy.com/codegen@17.67.0':
-    resolution: {integrity: sha512-idnkUplROpdBOV0HMcwhsCUS5TRUi9poagdGs70A6S4ux9+/aPuKbh8+UYRTLYQHtXvAdNfQWXDqZEx5k4Dj2Q==}
-    engines: {node: '>=10.0'}
-    peerDependencies:
-      tslib: '2'
+  compute-lcm@1.1.2:
+    resolution: {integrity: sha512-OFNPdQAXnQhDSKioX8/XYT6sdUlXwpeMjfd6ApxMJfyZ4GxmLR1xvMERctlYhlHwIiz6CSpBc2+qYKjHGZw4TQ==}
 
-  '@jsonjoy.com/fs-core@4.57.6':
-    resolution: {integrity: sha512-uI++Wx6VkBJqVmkb4ZeExwAVpZiA2Do5NrEtXoDk0Pdvce3ytFXJoviT1sLOj16+qDIMnD5nWPfOhVpnDmRJKg==}
-    engines: {node: '>=10.0'}
-    peerDependencies:
-      tslib: '2'
+  concat-map@0.0.1:
+    resolution: {integrity: sha512-/Srv4dswyQNBfohGpz9o6Yb3Gz3SrUDqBH5rTuhGR7ahtlbYKnVxw2bCFMRljaA7EXHaXZ8wsHdodFvbkhKmqg==}
 
-  '@jsonjoy.com/fs-fsa@4.57.6':
-    resolution: {integrity: sha512-pKkw/yC5CzSZKhIIUIsH1przOa+K5jGmZIg1sWaSF24JojyrUFbjcQv7QrcGAudriei6HQ6R0BFj+V8NbQinJw==}
-    engines: {node: '>=10.0'}
-    peerDependencies:
-      tslib: '2'
+  content-disposition@0.5.4:
+    resolution: {integrity: sha512-FveZTNuGw04cxlAiWbzi6zTAL/lhehaWbTtgluJh4/E95DqMwTmha3KZN1aAWA8cFIhHzMZUvLevkw5Rqk+tSQ==}
+    engines: {node: '>= 0.6'}
 
-  '@jsonjoy.com/fs-node-builtins@4.57.6':
-    resolution: {integrity: sha512-V4DgEFT3Cg5S9fCMOZSCVdTxdJWWLBO0WnAazV7hnCM96u5zXHyW/ubDAfcSVwqjkMJ50W1Y44IXtxRoIwaCVg==}
-    engines: {node: '>=10.0'}
-    peerDependencies:
-      tslib: '2'
+  content-type@1.0.5:
+    resolution: {integrity: sha512-nTjqfcBFEipKdXCv4YDQWCfmcLZKm81ldF0pAopTvyrFGVbcR6P/VAAd5G7N+0tTr8QqiU0tFadD6FK4NtJwOA==}
+    engines: {node: '>= 0.6'}
 
-  '@jsonjoy.com/fs-node-to-fsa@4.57.6':
-    resolution: {integrity: sha512-+JptNw3iifihxH2rEXrninDzX4FFVW8JD/wPR8GbJPAeL9CQUSblrlumOPB5gZuS7tYRX+PJPLtT7XzKoRhv/Q==}
-    engines: {node: '>=10.0'}
-    peerDependencies:
-      tslib: '2'
+  convert-to-spaces@2.0.1:
+    resolution: {integrity: sha512-rcQ1bsQO9799wq24uE5AM2tAILy4gXGIK/njFWcVQkGNZ96edlpY+A7bjwvzjYvLDyzmG1MmMLZhpcsb+klNMQ==}
+    engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
 
-  '@jsonjoy.com/fs-node-utils@4.57.6':
-    resolution: {integrity: sha512-foyUrfS7WmYEUzqYXSNxmJBcSj04TABrkpFabwO9SCDCpVCfJ+qG+2sk5FjfiflG2n0SDFZDCJ6vYlJAEpxJFg==}
-    engines: {node: '>=10.0'}
-    peerDependencies:
-      tslib: '2'
+  cookie-signature@1.0.7:
+    resolution: {integrity: sha512-NXdYc3dLr47pBkpUCHtKSwIOQXLVn8dZEuywboCOJY/osA0wFSLlSawr3KN8qXJEyX66FcONTH8EIlVuK0yyFA==}
 
-  '@jsonjoy.com/fs-node@4.57.6':
-    resolution: {integrity: sha512-Kbn1jdkvDN4F2+BhoB6mMu7NCbhP0bgA5NcI1aJj/Q5UcU+I1JLLW+dEQean33iV4tXv35AzBVKPICnDltBpxw==}
-    engines: {node: '>=10.0'}
-    peerDependencies:
-      tslib: '2'
+  cookie@0.7.2:
+    resolution: {integrity: sha512-yki5XnKuf750l50uGTllt6kKILY4nQ1eNIQatoXEByZ5dWgnKqbnqmTrBE5B4N7lrMJKQ2ytWMiTO2o0v6Ew/w==}
+    engines: {node: '>= 0.6'}
 
-  '@jsonjoy.com/fs-print@4.57.6':
-    resolution: {integrity: sha512-96eAn4Dudtt67LTeuU47yUD+pg9/G/oKpI10zei9ljk3X3WK4lYKc+n3cpaPCAbKPzoyfxl0mXm8f8Y7BOSFXw==}
-    engines: {node: '>=10.0'}
-    peerDependencies:
-      tslib: '2'
+  cors@2.8.6:
+    resolution: {integrity: sha512-tJtZBBHA6vjIAaF6EnIaq6laBBP9aq/Y3ouVJjEfoHbRBcHBAHYcMh/w8LDrk2PvIMMq8gmopa5D4V8RmbrxGw==}
+    engines: {node: '>= 0.10'}
 
-  '@jsonjoy.com/fs-snapshot@4.57.6':
-    resolution: {integrity: sha512-V57CMzbOgTzUWGOWQ8GzHQdpJP6JnrYVNCtTBNxVYEnlVRvo4uEJqHhtAT8vhDFrIuJOXLrTL1Fki4h5oI7xxg==}
-    engines: {node: '>=10.0'}
-    peerDependencies:
-      tslib: '2'
+  cross-spawn@7.0.6:
+    resolution: {integrity: sha512-uV2QOWP2nWzsy2aMp8aRibhi9dlzF5Hgh5SHaB9OiTGEyDTiJJyx0uy51QXdyWbtAHNua4XJzUKca3OzKUd3vA==}
+    engines: {node: '>= 8'}
 
-  '@jsonjoy.com/json-pack@1.21.0':
-    resolution: {integrity: sha512-+AKG+R2cfZMShzrF2uQw34v3zbeDYUqnQ+jg7ORic3BGtfw9p/+N6RJbq/kkV8JmYZaINknaEQ2m0/f693ZPpg==}
-    engines: {node: '>=10.0'}
-    peerDependencies:
-      tslib: '2'
+  css-background-parser@0.1.0:
+    resolution: {integrity: sha512-2EZLisiZQ+7m4wwur/qiYJRniHX4K5Tc9w93MT3AS0WS1u5kaZ4FKXlOTBhOjc+CgEgPiGY+fX1yWD8UwpEqUA==}
 
-  '@jsonjoy.com/json-pack@17.67.0':
-    resolution: {integrity: sha512-t0ejURcGaZsn1ClbJ/3kFqSOjlryd92eQY465IYrezsXmPcfHPE/av4twRSxf6WE+TkZgLY+71vCZbiIiFKA/w==}
-    engines: {node: '>=10.0'}
-    peerDependencies:
-      tslib: '2'
+  css-box-shadow@1.0.0-3:
+    resolution: {integrity: sha512-9jaqR6e7Ohds+aWwmhe6wILJ99xYQbfmK9QQB9CcMjDbTxPZjwEmUQpU91OG05Xgm8BahT5fW+svbsQGjS/zPg==}
 
-  '@jsonjoy.com/json-pointer@1.0.2':
-    resolution: {integrity: sha512-Fsn6wM2zlDzY1U+v4Nc8bo3bVqgfNTGcn6dMgs6FjrEnt4ZCe60o6ByKRjOGlI2gow0aE/Q41QOigdTqkyK5fg==}
-    engines: {node: '>=10.0'}
-    peerDependencies:
-      tslib: '2'
+  css-color-keywords@1.0.0:
+    resolution: {integrity: sha512-FyyrDHZKEjXDpNJYvVsV960FiqQyXc/LlYmsxl2BcdMb2WPx0OGRVgTg55rPSyLSNMqP52R9r8geSp7apN3Ofg==}
+    engines: {node: '>=4'}
 
-  '@jsonjoy.com/json-pointer@17.67.0':
-    resolution: {integrity: sha512-+iqOFInH+QZGmSuaybBUNdh7yvNrXvqR+h3wjXm0N/3JK1EyyFAeGJvqnmQL61d1ARLlk/wJdFKSL+LHJ1eaUA==}
-    engines: {node: '>=10.0'}
-    peerDependencies:
-      tslib: '2'
+  css-gradient-parser@0.0.17:
+    resolution: {integrity: sha512-w2Xy9UMMwlKtou0vlRnXvWglPAceXCTtcmVSo8ZBUvqCV5aXEFP/PC6d+I464810I9FT++UACwTD5511bmGPUg==}
+    engines: {node: '>=16'}
 
-  '@jsonjoy.com/util@1.9.0':
-    resolution: {integrity: sha512-pLuQo+VPRnN8hfPqUTLTHk126wuYdXVxE6aDmjSeV4NCAgyxWbiOIeNJVtID3h1Vzpoi9m4jXezf73I6LgabgQ==}
-    engines: {node: '>=10.0'}
-    peerDependencies:
-      tslib: '2'
+  css-to-react-native@3.2.0:
+    resolution: {integrity: sha512-e8RKaLXMOFii+02mOlqwjbD00KSEKqblnpO9e++1aXS1fPQOpS1YoqdVHBqPjHNoxeF2mimzVqawm2KCbEdtHQ==}
 
-  '@jsonjoy.com/util@17.67.0':
-    resolution: {integrity: sha512-6+8xBaz1rLSohlGh68D1pdw3AwDi9xydm8QNlAFkvnavCJYSze+pxoW2VKP8p308jtlMRLs5NTHfPlZLd4w7ew==}
-    engines: {node: '>=10.0'}
-    peerDependencies:
-      tslib: '2'
+  cssesc@3.0.0:
+    resolution: {integrity: sha512-/Tb/JcjK111nNScGob5MNtsntNM1aCNUDipB/TkwZFhyDrrE47SOx/18wF2bbjgc3ZzCSKW1T5nt5EbFoAz/Vg==}
+    engines: {node: '>=4'}
+    hasBin: true
 
-  '@juggle/resize-observer@3.4.0':
-    resolution: {integrity: sha512-dfLbk+PwWvFzSxwk3n5ySL0hfBog779o8h68wK/7/APo/7cgyWp5jcXockbxdk5kFRkbeXWm4Fbi9FrdN381sA==}
+  cssfilter@0.0.10:
+    resolution: {integrity: sha512-FAaLDaplstoRsDR8XGYH51znUN0UY7nMc6Z9/fvE8EXGwvJE9hu7W2vHwx1+bd6gCYnln9nLbzxFTrcO9YQDZw==}
 
-  '@leichtgewicht/ip-codec@2.0.5':
-    resolution: {integrity: sha512-Vo+PSpZG2/fmgmiNzYK9qWRh8h/CHrwD0mo1h1DzL4yzHNSfWYujGTYsWGreD000gcgmZ7K4Ys6Tx9TxtsKdDw==}
+  csstype@3.2.3:
+    resolution: {integrity: sha512-z1HGKcYy2xA8AGQfwrn0PAy+PB7X/GSj3UVJW9qKyn43xWa+gl5nXmU4qqLMRzWVLFC8KusUX8T/0kCiOYpAIQ==}
 
-  '@mdx-js/mdx@3.1.1':
-    resolution: {integrity: sha512-f6ZO2ifpwAQIpzGWaBQT2TXxPv6z3RBzQKpVftEWN78Vl/YweF1uwussDx8ECAXVtr3Rs89fKyG9YlzUs9DyGQ==}
+  data-view-buffer@1.0.2:
+    resolution: {integrity: sha512-EmKO5V3OLXh1rtK2wgXRansaK1/mtVdTUEiEI0W8RkvgT05kfxaH29PliLnpLP73yYO6142Q72QNa8Wx/A5CqQ==}
+    engines: {node: '>= 0.4'}
 
-  '@mdx-js/react@3.1.1':
-    resolution: {integrity: sha512-f++rKLQgUVYDAtECQ6fn/is15GkEH9+nZPM3MS0RcxVqoTfawHvDlSCH7JbMhAM6uJ32v3eXLvLmLvjGu7PTQw==}
-    peerDependencies:
-      '@types/react': '>=16'
-      react: '>=16'
+  data-view-byte-length@1.0.2:
+    resolution: {integrity: sha512-tuhGbE6CfTM9+5ANGf+oQb72Ky/0+s3xKUpHvShfiz2RxMFgFPjsXuRLBVMtvMs15awe45SRb83D6wH4ew6wlQ==}
+    engines: {node: '>= 0.4'}
 
-  '@mermaid-js/parser@1.1.1':
-    resolution: {integrity: sha512-VuHdsYMK1bT6X2JbcAaWAhugTRvRBRyuZgd+c22swUeI9g/ntaxF7CY7dYarhZovofCbUNO0G7JesfmNtjYOCw==}
+  data-view-byte-offset@1.0.1:
+    resolution: {integrity: sha512-BS8PfmtDGnrgYdOonGZQdLZslWIeCGFP9tpan0hi1Co2Zr2NKADsvGYA8XxuG/4UWgJ6Cjtv+YJnB6MM69QGlQ==}
+    engines: {node: '>= 0.4'}
 
-  '@module-federation/error-codes@0.22.0':
-    resolution: {integrity: sha512-xF9SjnEy7vTdx+xekjPCV5cIHOGCkdn3pIxo9vU7gEZMIw0SvAEdsy6Uh17xaCpm8V0FWvR0SZoK9Ik6jGOaug==}
+  debug@2.6.9:
+    resolution: {integrity: sha512-bC7ElrdJaJnPbAP+1EotYvqZsb3ecl5wi6Bfi6BJTUcNowp6cvspg0jXznRTKDjm/E7AdgFBVeAPVMNcKGsHMA==}
+    peerDependencies:
+      supports-color: '*'
+    peerDependenciesMeta:
+      supports-color:
+        optional: true
 
-  '@module-federation/runtime-core@0.22.0':
-    resolution: {integrity: sha512-GR1TcD6/s7zqItfhC87zAp30PqzvceoeDGYTgF3Vx2TXvsfDrhP6Qw9T4vudDQL3uJRne6t7CzdT29YyVxlgIA==}
+  debug@4.3.7:
+    resolution: {integrity: sha512-Er2nc/H7RrMXZBFCEim6TCmMk02Z8vLC2Rbi1KEBggpo0fS6l0S1nnapwmIi3yW/+GOJap1Krg4w0Hg80oCqgQ==}
+    engines: {node: '>=6.0'}
+    peerDependencies:
+      supports-color: '*'
+    peerDependenciesMeta:
+      supports-color:
+        optional: true
 
-  '@module-federation/runtime-tools@0.22.0':
-    resolution: {integrity: sha512-4ScUJ/aUfEernb+4PbLdhM/c60VHl698Gn1gY21m9vyC1Ucn69fPCA1y2EwcCB7IItseRMoNhdcWQnzt/OPCNA==}
+  debug@4.4.3:
+    resolution: {integrity: sha512-RGwwWnwQvkVfavKVt22FGLw+xYSdzARwm0ru6DhTVA3umU5hZc28V3kO4stgYryrTlLpuvgI9GiijltAjNbcqA==}
+    engines: {node: '>=6.0'}
+    peerDependencies:
+      supports-color: '*'
+    peerDependenciesMeta:
+      supports-color:
+        optional: true
 
-  '@module-federation/runtime@0.22.0':
-    resolution: {integrity: sha512-38g5iPju2tPC3KHMPxRKmy4k4onNp6ypFPS1eKGsNLUkXgHsPMBFqAjDw96iEcjri91BrahG4XcdyKi97xZzlA==}
+  decode-bmp@0.2.1:
+    resolution: {integrity: sha512-NiOaGe+GN0KJqi2STf24hfMkFitDUaIoUU3eKvP/wAbLe8o6FuW5n/x7MHPR0HKvBokp6MQY/j7w8lewEeVCIA==}
+    engines: {node: '>=8.6.0'}
 
-  '@module-federation/sdk@0.22.0':
-    resolution: {integrity: sha512-x4aFNBKn2KVQRuNVC5A7SnrSCSqyfIWmm1DvubjbO9iKFe7ith5niw8dqSFBekYBg2Fwy+eMg4sEFNVvCAdo6g==}
+  decode-ico@0.4.1:
+    resolution: {integrity: sha512-69NZfbKIzux1vBOd31al3XnMnH+2mqDhEgLdpygErm4d60N+UwA5Sq5WFjmEDQzumgB9fElojGwWG0vybVfFmA==}
+    engines: {node: '>=8.6'}
 
-  '@module-federation/webpack-bundler-runtime@0.22.0':
-    resolution: {integrity: sha512-aM8gCqXu+/4wBmJtVeMeeMN5guw3chf+2i6HajKtQv7SJfxV/f4IyNQJUeUQu9HfiAZHjqtMV5Lvq/Lvh8LdyA==}
+  decode-named-character-reference@1.3.0:
+    resolution: {integrity: sha512-GtpQYB283KrPp6nRw50q3U9/VfOutZOe103qlN7BPP6Ad27xYnOIWv4lPzo8HCAL+mMZofJ9KEy30fq6MfaK6Q==}
 
-  '@napi-rs/wasm-runtime@1.0.7':
-    resolution: {integrity: sha512-SeDnOO0Tk7Okiq6DbXmmBODgOAb9dp9gjlphokTUxmt8U3liIP1ZsozBahH69j/RJv+Rfs6IwUKHTgQYJ/HBAw==}
+  decompress-response@6.0.0:
+    resolution: {integrity: sha512-aW35yZM6Bb/4oJlZncMH2LCoZtJXTRxES17vE3hoRiowU2kWHaJKFkSBDnDR+cm9J+9QhXmREyIfv0pji9ejCQ==}
+    engines: {node: '>=10'}
 
-  '@noble/hashes@1.4.0':
-    resolution: {integrity: sha512-V1JJ1WTRUqHHrOSh597hURcMqVKVGL/ea3kv0gSnEdsEZ0/+VyPghM1lMNGc00z7CIQorSvbKpuJkxvuHbvdbg==}
-    engines: {node: '>= 16'}
+  deep-extend@0.6.0:
+    resolution: {integrity: sha512-LOHxIOaPYdHlJRtCQfDIVZtfw/ufM8+rVj649RIHzcm/vGwQRXFt6OPqIFWsm2XEMrNIEtWR64sY1LEKD2vAOA==}
+    engines: {node: '>=4.0.0'}
 
-  '@nodelib/fs.scandir@2.1.5':
-    resolution: {integrity: sha512-vq24Bq3ym5HEQm2NKCr3yXDwjc7vTsEThRDnkp2DK9p1uqLR+DHurm/NOTo0KG7HYHU7eppKZj3MyqYuMBf62g==}
-    engines: {node: '>= 8'}
+  defer-to-connect@2.0.1:
+    resolution: {integrity: sha512-4tvttepXG1VaYGrRibk5EwJd1t4udunSOVMdLSAL6mId1ix438oPwPZMALY41FCijukO1L0twNcGsdzS7dHgDg==}
+    engines: {node: '>=10'}
 
-  '@nodelib/fs.stat@2.0.5':
-    resolution: {integrity: sha512-RkhPPp2zrqDAQA/2jNhnztcPAlv64XdhIp7a7454A5ovI7Bukxgt7MX7udwAu3zg1DcpPU0rz3VV1SeaqvY4+A==}
-    engines: {node: '>= 8'}
+  define-data-property@1.1.4:
+    resolution: {integrity: sha512-rBMvIzlpA8v6E+SJZoo++HAYqsLrkg7MSfIinMPFhmkorw7X+dOXVJQs+QT69zGkzMyfDnIMN2Wid1+NbL3T+A==}
+    engines: {node: '>= 0.4'}
 
-  '@nodelib/fs.walk@1.2.8':
-    resolution: {integrity: sha512-oGB+UxlgWcgQkgwo8GcEGwemoTFt3FIO9ababBmaGwXIoBKZ+GTy0pP185beGg7Llih/NSHSV2XAs1lnznocSg==}
-    engines: {node: '>= 8'}
+  define-lazy-prop@2.0.0:
+    resolution: {integrity: sha512-Ds09qNh8yw3khSjiJjiUInaGX9xlqZDY7JVryGxdxV7NPeuqQfplOpQ66yJFZut3jLa5zOwkXw1g9EI2uKh4Og==}
+    engines: {node: '>=8'}
 
-  '@open-rpc/examples@1.7.2':
-    resolution: {integrity: sha512-wEvviOPc+gyBVmxvGQVl/hqYslEacxLe0UETupyp1JjXUAZxW27da+F1IxbP6NYdx6jt4RyLg+V0GBVTsN6RRA==}
+  define-properties@1.2.1:
+    resolution: {integrity: sha512-8QmQKqEASLd5nx0U1B1okLElbUuuttJ/AnYmRXbbbGDWh6uS208EjD4Xqq/I9wK7u0v6O08XhTWnt5XtEbR6Dg==}
+    engines: {node: '>= 0.4'}
 
-  '@open-rpc/meta-schema@1.14.9':
-    resolution: {integrity: sha512-2/CbDzOVpcaSnMs28TsRv8MKJwJi0TTYFlQ6q6qobAH26oIuhYgcZooKf4l71emgntU6MMcFQCA0h4mJ4dBCdA==}
+  delayed-stream@1.0.0:
+    resolution: {integrity: sha512-ZySD7Nf91aLB0RxL4KGrKHBXl7Eds1DAmEdcoVawXnLD7SDhpNgtuII2aAkg7a7QS41jxPSZ17p4VdGnMHk3MQ==}
+    engines: {node: '>=0.4.0'}
 
-  '@open-rpc/schema-utils-js@2.2.1':
-    resolution: {integrity: sha512-lXsJrkViY08eoqD9X/3Gq0QiN4/jaPEiNdQCB3eZDv4vp26JaIWQ/r2WwYlA8rJZb4lYGIvKr3zM/rTcu7yMuw==}
+  depd@2.0.0:
+    resolution: {integrity: sha512-g7nH6P6dyDioJogAAGprGpCtVImJhpPk/roCzdb3fIh61/s/nPsfR6onyMwkCAR/OlC3yBC0lESvUoQEAssIrw==}
+    engines: {node: '>= 0.8'}
 
-  '@open-rpc/spec-types@0.0.2':
-    resolution: {integrity: sha512-4FbovmeH3XVcf7loRpaqxqCAFbX9jDfp85cbvdeNYumL/BWOWA1a6CwScfZWBvIH/eXmrmzhu8nUW4eJTuD3ZQ==}
+  dependency-graph@0.11.0:
+    resolution: {integrity: sha512-JeMq7fEshyepOWDfcfHK06N3MhyPhz++vtqWhMT5O9A3K42rdsEDpfdVqjaqaAhsw6a+ZqeDvQVtD0hFHQWrzg==}
+    engines: {node: '>= 0.6.0'}
 
-  '@open-rpc/spec@1.4.1':
-    resolution: {integrity: sha512-XoCq9X7FDv2kXz7nK8JZMDtUrGPRyDwbt7HsZRuBtvqzxAyma/c6t33vlCyxEePxMb4aGfX3MJbI2gz9JIqNvg==}
+  dequal@2.0.3:
+    resolution: {integrity: sha512-0je+qPKHEMohvfRTCEo3CrPG6cAzAYgmzKyxRiYSSDkS6eGJdyVJm7WaYA5ECaAD9wLB2T4EEeymA5aFVcYXCA==}
+    engines: {node: '>=6'}
 
-  '@open-rpc/specification-extension-spec@1.0.2':
-    resolution: {integrity: sha512-EPVI1Mgp5vDSN2Xn+eWjd2t30WU+R0nFeNoP/dp3ox5/qUhNdqlNcwGJDNoJlqK56rk09FYXWJXKLHae4eBE8w==}
-    engines: {node: '>=18.0.0'}
+  destroy@1.2.0:
+    resolution: {integrity: sha512-2sJGJTaXIIaR1w4iJSNoN0hnMY7Gpc/n8D4qSCJw8QqFWXf7cuAgnEHxBpweaVcPevC2l3KpjYCx3NypQQgaJg==}
+    engines: {node: '>= 0.8', npm: 1.2.8000 || >= 1.4.16}
 
-  '@parcel/watcher-android-arm64@2.5.6':
-    resolution: {integrity: sha512-YQxSS34tPF/6ZG7r/Ih9xy+kP/WwediEUsqmtf0cuCV5TPPKw/PQHRhueUo6JdeFJaqV3pyjm0GdYjZotbRt/A==}
-    engines: {node: '>= 10.0.0'}
-    cpu: [arm64]
-    os: [android]
+  detect-libc@2.1.2:
+    resolution: {integrity: sha512-Btj2BOOO83o3WyH59e8MgXsxEQVcarkUOpEYrubB0urwnN10yQ364rsiByU11nZlqWYZm05i/of7io4mzihBtQ==}
+    engines: {node: '>=8'}
 
-  '@parcel/watcher-darwin-arm64@2.5.6':
-    resolution: {integrity: sha512-Z2ZdrnwyXvvvdtRHLmM4knydIdU9adO3D4n/0cVipF3rRiwP+3/sfzpAwA/qKFL6i1ModaabkU7IbpeMBgiVEA==}
-    engines: {node: '>= 10.0.0'}
-    cpu: [arm64]
-    os: [darwin]
+  detect-node@2.1.0:
+    resolution: {integrity: sha512-T0NIuQpnTvFDATNuHN5roPwSBG83rFsuO+MXXH9/3N1eFbn4wcPjttvjMLEPWJ0RGUYgQE7cGgS3tNxbqCGM7g==}
 
-  '@parcel/watcher-darwin-x64@2.5.6':
-    resolution: {integrity: sha512-HgvOf3W9dhithcwOWX9uDZyn1lW9R+7tPZ4sug+NGrGIo4Rk1hAXLEbcH1TQSqxts0NYXXlOWqVpvS1SFS4fRg==}
-    engines: {node: '>= 10.0.0'}
-    cpu: [x64]
-    os: [darwin]
+  detect-port@1.5.1:
+    resolution: {integrity: sha512-aBzdj76lueB6uUst5iAs7+0H/oOjqI5D16XUWxlWMIMROhcM0rfsNVk93zTngq1dDNpoXRr++Sus7ETAExppAQ==}
+    hasBin: true
 
-  '@parcel/watcher-freebsd-x64@2.5.6':
-    resolution: {integrity: sha512-vJVi8yd/qzJxEKHkeemh7w3YAn6RJCtYlE4HPMoVnCpIXEzSrxErBW5SJBgKLbXU3WdIpkjBTeUNtyBVn8TRng==}
-    engines: {node: '>= 10.0.0'}
-    cpu: [x64]
-    os: [freebsd]
+  devlop@1.1.0:
+    resolution: {integrity: sha512-RWmIqhcFf1lRYBvNmr7qTNuyCt/7/ns2jbpp1+PalgE/rDQcBT0fioSMUpJ93irlUhC5hrg4cYqe6U+0ImW0rA==}
 
-  '@parcel/watcher-linux-arm-glibc@2.5.6':
-    resolution: {integrity: sha512-9JiYfB6h6BgV50CCfasfLf/uvOcJskMSwcdH1PHH9rvS1IrNy8zad6IUVPVUfmXr+u+Km9IxcfMLzgdOudz9EQ==}
-    engines: {node: '>= 10.0.0'}
-    cpu: [arm]
-    os: [linux]
-    libc: [glibc]
+  didyoumean@1.2.2:
+    resolution: {integrity: sha512-gxtyfqMg7GKyhQmb056K7M3xszy/myH8w+B4RT+QXBQsvAOdc3XymqDDPHx1BgPgsdAA5SIifona89YtRATDzw==}
 
-  '@parcel/watcher-linux-arm-musl@2.5.6':
-    resolution: {integrity: sha512-Ve3gUCG57nuUUSyjBq/MAM0CzArtuIOxsBdQ+ftz6ho8n7s1i9E1Nmk/xmP323r2YL0SONs1EuwqBp2u1k5fxg==}
-    engines: {node: '>= 10.0.0'}
-    cpu: [arm]
-    os: [linux]
-    libc: [musl]
+  dlv@1.1.3:
+    resolution: {integrity: sha512-+HlytyjlPKnIG8XuRG8WvmBP8xs8P71y+SKKS6ZXWoEgLuePxtDoUEiH7WkdePWrQ5JBpE6aoVqfZfJUQkjXwA==}
 
-  '@parcel/watcher-linux-arm64-glibc@2.5.6':
-    resolution: {integrity: sha512-f2g/DT3NhGPdBmMWYoxixqYr3v/UXcmLOYy16Bx0TM20Tchduwr4EaCbmxh1321TABqPGDpS8D/ggOTaljijOA==}
-    engines: {node: '>= 10.0.0'}
-    cpu: [arm64]
-    os: [linux]
-    libc: [glibc]
+  dns-packet@5.6.1:
+    resolution: {integrity: sha512-l4gcSouhcgIKRvyy99RNVOgxXiicE+2jZoNmaNmZ6JXiGajBOJAesk1OBlJuM5k2c+eudGdLxDqXuPCKIj6kpw==}
+    engines: {node: '>=6'}
 
-  '@parcel/watcher-linux-arm64-musl@2.5.6':
-    resolution: {integrity: sha512-qb6naMDGlbCwdhLj6hgoVKJl2odL34z2sqkC7Z6kzir8b5W65WYDpLB6R06KabvZdgoHI/zxke4b3zR0wAbDTA==}
-    engines: {node: '>= 10.0.0'}
-    cpu: [arm64]
-    os: [linux]
-    libc: [musl]
+  dns-socket@4.2.2:
+    resolution: {integrity: sha512-BDeBd8najI4/lS00HSKpdFia+OvUMytaVjfzR9n5Lq8MlZRSvtbI+uLtx1+XmQFls5wFU9dssccTmQQ6nfpjdg==}
+    engines: {node: '>=6'}
 
-  '@parcel/watcher-linux-x64-glibc@2.5.6':
-    resolution: {integrity: sha512-kbT5wvNQlx7NaGjzPFu8nVIW1rWqV780O7ZtkjuWaPUgpv2NMFpjYERVi0UYj1msZNyCzGlaCWEtzc+exjMGbQ==}
-    engines: {node: '>= 10.0.0'}
-    cpu: [x64]
-    os: [linux]
-    libc: [glibc]
+  dunder-proto@1.0.1:
+    resolution: {integrity: sha512-KIN/nDJBQRcXw0MLVhZE9iQHmG68qAVIBg9CqmUYjmQIhgij9U5MFvrqkUL5FbtyyzZuOeOt0zdeRe4UY7ct+A==}
+    engines: {node: '>= 0.4'}
 
-  '@parcel/watcher-linux-x64-musl@2.5.6':
-    resolution: {integrity: sha512-1JRFeC+h7RdXwldHzTsmdtYR/Ku8SylLgTU/reMuqdVD7CtLwf0VR1FqeprZ0eHQkO0vqsbvFLXUmYm/uNKJBg==}
-    engines: {node: '>= 10.0.0'}
-    cpu: [x64]
-    os: [linux]
-    libc: [musl]
+  ee-first@1.1.1:
+    resolution: {integrity: sha512-WMwm9LhRUo+WUaRN+vRuETqG89IgZphVSNkdFgeb6sS/E4OrDIN7t48CAewSHXc6C8lefD8KKfr5vY61brQlow==}
 
-  '@parcel/watcher-win32-arm64@2.5.6':
-    resolution: {integrity: sha512-3ukyebjc6eGlw9yRt678DxVF7rjXatWiHvTXqphZLvo7aC5NdEgFufVwjFfY51ijYEWpXbqF5jtrK275z52D4Q==}
-    engines: {node: '>= 10.0.0'}
-    cpu: [arm64]
-    os: [win32]
+  emoji-regex-xs@2.0.1:
+    resolution: {integrity: sha512-1QFuh8l7LqUcKe24LsPUNzjrzJQ7pgRwp1QMcZ5MX6mFplk2zQ08NVCM84++1cveaUUYtcCYHmeFEuNg16sU4g==}
+    engines: {node: '>=10.0.0'}
 
-  '@parcel/watcher-win32-ia32@2.5.6':
-    resolution: {integrity: sha512-k35yLp1ZMwwee3Ez/pxBi5cf4AoBKYXj00CZ80jUz5h8prpiaQsiRPKQMxoLstNuqe2vR4RNPEAEcjEFzhEz/g==}
-    engines: {node: '>= 10.0.0'}
-    cpu: [ia32]
-    os: [win32]
+  emoji-regex@10.6.0:
+    resolution: {integrity: sha512-toUI84YS5YmxW219erniWD0CIVOo46xGKColeNQRgOzDorgBi1v4D71/OFzgD9GO2UGKIv1C3Sp8DAn0+j5w7A==}
 
-  '@parcel/watcher-win32-x64@2.5.6':
-    resolution: {integrity: sha512-hbQlYcCq5dlAX9Qx+kFb0FHue6vbjlf0FrNzSKdYK2APUf7tGfGxQCk2ihEREmbR6ZMc0MVAD5RIX/41gpUzTw==}
-    engines: {node: '>= 10.0.0'}
-    cpu: [x64]
-    os: [win32]
+  emoji-regex@8.0.0:
+    resolution: {integrity: sha512-MSjYzcWNOA0ewAHpz0MxpYFvwg6yjy1NG3xteoqz644VCo/RPgnr1/GGt+ic3iJTzQ8Eu3TdM14SawnVUmGE6A==}
 
-  '@parcel/watcher@2.5.6':
-    resolution: {integrity: sha512-tmmZ3lQxAe/k/+rNnXQRawJ4NjxO2hqiOLTHvWchtGZULp4RyFeh6aU4XdOYBFe2KE1oShQTv4AblOs2iOrNnQ==}
-    engines: {node: '>= 10.0.0'}
+  encodeurl@2.0.0:
+    resolution: {integrity: sha512-Q0n9HRi4m6JuGIV1eFlmvJB7ZEVxu93IrMyiMsGC0lrMJMWzRgx6WGquyfQgZVb31vhGgXnfmPNNXmxnOkRBrg==}
+    engines: {node: '>= 0.8'}
 
-  '@peculiar/asn1-cms@2.7.0':
-    resolution: {integrity: sha512-hew63shtzzvBcSHbhm+cyAmKe6AIfinT9hzEqSPjDC6opTTMKmTkQ0gHuN2KsWlvqiKw1S/fS94fhag/FJkioQ==}
+  end-of-stream@1.4.5:
+    resolution: {integrity: sha512-ooEGc6HP26xXq/N+GCGOT0JKCLDGrq2bQUZrQ7gyrJiZANJ/8YDTxTpQBXGMn+WbIQXNVpyWymm7KYVICQnyOg==}
 
-  '@peculiar/asn1-csr@2.7.0':
-    resolution: {integrity: sha512-VVsAyGqErT9D1SY4aEqozThXMVI+ssVRiv2DDeYuvpBKLIgZ3hYs3Ay3u/VSoKq6ESFi9cf6rf3IOOzfwh7oMA==}
+  engine.io-parser@5.2.3:
+    resolution: {integrity: sha512-HqD3yTBfnBxIrbnM1DoD6Pcq8NECnh8d4As1Qgh0z5Gg3jRRIqijury0CL3ghu/edArpUYiYqQiDUQBIs4np3Q==}
+    engines: {node: '>=10.0.0'}
 
-  '@peculiar/asn1-ecc@2.7.0':
-    resolution: {integrity: sha512-n7KEs/Q/wrB415cxy4fHOBhegp4NdJ15fkJPwcB/3/8iNBQC2L/N7SChJPKDJPZGYH0jD4Tg4/0vnHmwghnbKw==}
+  engine.io@6.6.11:
+    resolution: {integrity: sha512-z34mGpLoY/82ZbkX1LqGMIaf3wjVMPL6gVC681QDqnmzJ26synI8qAE32P+a7UazmpJZ8UGrFIeAavgRfXzYrg==}
+    engines: {node: '>=10.2.0'}
 
-  '@peculiar/asn1-pfx@2.7.0':
-    resolution: {integrity: sha512-V/nrlQVmhg7lYAsM7E13UDL5erAwFv6kCIVFqNaMIHSVi7dngcT839JkRTkQBqznMG98l2XjxYk74ZztAohZzA==}
+  entities@6.0.1:
+    resolution: {integrity: sha512-aN97NXWF6AWBTahfVOIrB/NShkzi5H7F9r1s9mD3cDj4Ko5f2qhhVoYMibXF7GlLveb/D2ioWay8lxI97Ven3g==}
+    engines: {node: '>=0.12'}
 
-  '@peculiar/asn1-pkcs8@2.7.0':
-    resolution: {integrity: sha512-9GTl1nE8Mx1kTZ+7QyYatDyKsm34QcWRBFkY1iPvWC3X4Dona5s/tlLiQsx5WzVdZqiMBZNYT0buyw4/vbhnjw==}
+  entities@7.0.1:
+    resolution: {integrity: sha512-TWrgLOFUQTH994YUyl1yT4uyavY5nNB5muff+RtWaqNVCAK408b5ZnnbNAUEWLTCpum9w6arT70i1XdQ4UeOPA==}
+    engines: {node: '>=0.12'}
 
-  '@peculiar/asn1-pkcs9@2.7.0':
-    resolution: {integrity: sha512-Bh7m+OuIaSEllPQcSd9OSp93F4ROWH7sbITWV8MI+8dwsjE5111/87VxiWVvYFKyww3vp39geLv9ENqhwWHcew==}
+  environment@1.1.0:
+    resolution: {integrity: sha512-xUtoPkMggbz0MPyPiIWr1Kp4aeWJjDZ6SMvURhimjdZgsRuDplF5/s9hcgGhyXMhs+6vpnuoiZ2kFiu3FMnS8Q==}
+    engines: {node: '>=18'}
 
-  '@peculiar/asn1-rsa@2.7.0':
-    resolution: {integrity: sha512-/qvENQrXyTZURjMqSeofHul0JJt2sNSzSwk36pl2olkHbaioMQgrASDZAlHXl0xUlnVbHj0uGgOrBMTb5x2aJQ==}
+  es-abstract-get@1.0.0:
+    resolution: {integrity: sha512-6PMWXpdhshVvFp+FoWYs1EvG1Nj0tvk0dZM+XcK0xMEM1czRVcP6ohqPWHy6qPagSpC8j4+p89WXlT+xXJs/fg==}
+    engines: {node: '>= 0.4'}
 
-  '@peculiar/asn1-schema@2.7.0':
-    resolution: {integrity: sha512-W8ZfWzLmQnrcky+eh3tni4IozMdqBDiHWU0N+vve/UGjMaUs8c0L7A2oEdkBXS8rTpWDpK/aoI3DG/L/hxmxPg==}
+  es-abstract@1.24.2:
+    resolution: {integrity: sha512-2FpH9Q5i2RRwyEP1AylXe6nYLR5OhaJTZwmlcP0dL/+JCbgg7yyEo/sEK6HeGZRf3dFpWwThaRHVApXSkW3xeg==}
+    engines: {node: '>= 0.4'}
 
-  '@peculiar/asn1-x509-attr@2.7.0':
-    resolution: {integrity: sha512-NS8e7SOgXipkzUPLF/sce7ukpMpWjhxYsH0n6Y+bHYo4TTxOb95Zv7hqwSuL212mj5YxovjdOKQOgH1As3E94w==}
+  es-aggregate-error@1.0.14:
+    resolution: {integrity: sha512-3YxX6rVb07B5TV11AV5wsL7nQCHXNwoHPsQC8S4AmBiqYhyNCJ5BRKXkXyDJvs8QzXN20NgRtxe3dEEQD9NLHA==}
+    engines: {node: '>= 0.4'}
 
-  '@peculiar/asn1-x509@2.7.0':
-    resolution: {integrity: sha512-mUn9RRrkGDnG4ALfunDmzyRW5dg+sWCj/pfnCCqEHYbkGxEpvUt6iVJv8Yw1cyp6SWZ26ZE5oSmI5SqEaen15g==}
+  es-define-property@1.0.1:
+    resolution: {integrity: sha512-e3nRfgfUZ4rNGL232gUgX06QNyyez04KdjFrF+LTRoOXmrOgFKDg4BCdsjW8EnT69eqdYGmRpJwiPVYNrCaW3g==}
+    engines: {node: '>= 0.4'}
 
-  '@peculiar/utils@2.0.3':
-    resolution: {integrity: sha512-+oL3HPFRIZ1St2K50lWCXiioIgSoxzz7R1J3uF6neO2yl1sgmpgY6XXJH4BdpoDkMWznQTeYF6oWNDZLCdQ4eQ==}
+  es-errors@1.3.0:
+    resolution: {integrity: sha512-Zf5H2Kxt2xjTvbJvP2ZWLEICxA6j+hAmMzIlypy4xcBg1vKVnx89Wy0GbS+kf5cwCVFFzdCFh2XSCFNULS6csw==}
+    engines: {node: '>= 0.4'}
 
-  '@peculiar/x509@1.14.3':
-    resolution: {integrity: sha512-C2Xj8FZ0uHWeCXXqX5B4/gVFQmtSkiuOolzAgutjTfseNOHT3pUjljDZsTSxXFGgio54bCzVFqmEOUrIVk8RDA==}
-    engines: {node: '>=20.0.0'}
+  es-object-atoms@1.1.2:
+    resolution: {integrity: sha512-HWcBoN6NileqtSydK2FqHbS/LoDd2pqrnQHLyJzBj4kOp/ky2MWMN694xOfkK8/SnUsW2DH7EfyVlydKCsm1Zw==}
+    engines: {node: '>= 0.4'}
 
-  '@pnpm/config.env-replace@1.1.0':
-    resolution: {integrity: sha512-htyl8TWnKL7K/ESFa1oW2UB5lVDxuF5DpM7tBi6Hu2LNL3mWkIzNLG6N4zoCUP1lCKNxWy/3iu8mS8MvToGd6w==}
-    engines: {node: '>=12.22.0'}
+  es-set-tostringtag@2.1.0:
+    resolution: {integrity: sha512-j6vWzfrGVfyXxge+O0x5sh6cvxAog0a/4Rdd2K36zCMV5eJ+/+tOAngRO8cODMNWbVRdVlmGZQL2YS3yR8bIUA==}
+    engines: {node: '>= 0.4'}
 
-  '@pnpm/network.ca-file@1.0.2':
-    resolution: {integrity: sha512-YcPQ8a0jwYU9bTdJDpXjMi7Brhkr1mXsXrUJvjqM2mQDgkRiz8jFaQGOdaLxgjtUfQgZhKy/O3cG/YwmgKaxLA==}
-    engines: {node: '>=12.22.0'}
+  es-to-primitive@1.3.4:
+    resolution: {integrity: sha512-yPDz7wqpg1/mmHLmS3tcfTfbw5f1eryXvyghYBffGdERwe+mV7ZcWzTR8LR17Kvqt3qfPurjlonmnq3MKXIOXw==}
+    engines: {node: '>= 0.4'}
 
-  '@pnpm/npm-conf@3.0.2':
-    resolution: {integrity: sha512-h104Kh26rR8tm+a3Qkc5S4VLYint3FE48as7+/5oCEcKR2idC/pF1G6AhIXKI+eHPJa/3J9i5z0Al47IeGHPkA==}
-    engines: {node: '>=12'}
+  es-toolkit@1.52.0:
+    resolution: {integrity: sha512-XTNEJQh1tY1ZJVcf6ayP/2n4ZPyaHlW2FWs7xvw5ddPuhUVjLD3olQVQS7kf58JbAB48iL0uL/jerTrjtV3lDA==}
 
-  '@polka/url@1.0.0-next.29':
-    resolution: {integrity: sha512-wwQAWhWSuHaag8c4q/KN/vCoeOJYshAIvMQwD4GpSb3OiZklFfvAgmj0VCBBImRpuF/aFgIRzllXlVX93Jevww==}
+  esast-util-from-estree@2.0.0:
+    resolution: {integrity: sha512-4CyanoAudUSBAn5K13H4JhsMH6L9ZP7XbLVe/dKybkxMO7eDyLsT8UHl9TRNrU2Gr9nz+FovfSIjuXWJ81uVwQ==}
 
-  '@react-aria/checkbox@3.17.1':
-    resolution: {integrity: sha512-742B+UhH87TK02SYsFJZOgQ9VZpFEythH5LXRnwxt/xShoKOp+eqXPaVah79s/+B9sxY1mF0wNORQ2RVAQFSKw==}
-    peerDependencies:
-      react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
-      react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
+  esast-util-from-js@2.0.1:
+    resolution: {integrity: sha512-8Ja+rNJ0Lt56Pcf3TAmpBZjmx8ZcK5Ts4cAzIOjsjevg9oSXJnl6SUQ2EevU8tv3h6ZLWmoKL5H4fgWvdvfETw==}
 
-  '@react-aria/toggle@3.13.1':
-    resolution: {integrity: sha512-1SPMBSrbT94Jsy7Wuv9SH2uPv7szGP7KgO4QGIAcF3e5kHwvGQJdMHY6+xR17slk8ICXfFojBqUKgpJjyY2+KQ==}
-    peerDependencies:
-      react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
-      react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
+  esbuild@0.25.12:
+    resolution: {integrity: sha512-bbPBYYrtZbkt6Os6FiTLCTFxvq4tt3JKall1vRwshA3fdVztsLAatFaZobhkBC8/BrPetoa0oksYoKXoG4ryJg==}
+    engines: {node: '>=18'}
+    hasBin: true
 
-  '@react-hook/debounce@3.0.0':
-    resolution: {integrity: sha512-ir/kPrSfAzY12Gre0sOHkZ2rkEmM4fS5M5zFxCi4BnCeXh2nvx9Ujd+U4IGpKCuPA+EQD0pg1eK2NGLvfWejag==}
-    peerDependencies:
-      react: '>=16.8'
+  escalade@3.2.0:
+    resolution: {integrity: sha512-WUj2qlxaQtO4g6Pq5c29GTcWGDyd8itL8zTlipgECz3JesAiiOKotd8JU6otB3PACgG6xkJUyVhboMS+bje/jA==}
+    engines: {node: '>=6'}
 
-  '@react-hook/event@1.2.6':
-    resolution: {integrity: sha512-JUL5IluaOdn5w5Afpe/puPa1rj8X6udMlQ9dt4hvMuKmTrBS1Ya6sb4sVgvfe2eU4yDuOfAhik8xhbcCekbg9Q==}
-    peerDependencies:
-      react: '>=16.8'
+  escape-html@1.0.3:
+    resolution: {integrity: sha512-NiSupZ4OeuGwr68lGIeym/ksIZMJodUGOSCZ/FSnTxcrekbvqrgdUxlJOMpijaKZVjAJrWrGs/6Jy8OMuyj9ow==}
 
-  '@react-hook/latest@1.0.3':
-    resolution: {integrity: sha512-dy6duzl+JnAZcDbNTfmaP3xHiKtbXYOaz3G51MGVljh548Y8MWzTr+PHLOfvpypEVW9zwvl+VyKjbWKEVbV1Rg==}
-    peerDependencies:
-      react: '>=16.8'
+  escape-string-regexp@2.0.0:
+    resolution: {integrity: sha512-UpzcLCXolUWcNu5HtVMHYdXJjArjsF9C0aNnquZYY4uW/Vu0miy5YoWvbV345HauVvcAUnpRuhMMcqTcGOY2+w==}
+    engines: {node: '>=8'}
 
-  '@react-hook/passive-layout-effect@1.2.1':
-    resolution: {integrity: sha512-IwEphTD75liO8g+6taS+4oqz+nnroocNfWVHWz7j+N+ZO2vYrc6PV1q7GQhuahL0IOR7JccFTsFKQ/mb6iZWAg==}
-    peerDependencies:
-      react: '>=16.8'
+  escape-string-regexp@5.0.0:
+    resolution: {integrity: sha512-/veY75JbMK4j1yjvuUxuVsiS/hr/4iHs9FTT6cgTexxdE0Ly/glccBAkloH/DofkjRbZU3bnoj38mOmhkZ0lHw==}
+    engines: {node: '>=12'}
 
-  '@react-hook/resize-observer@1.2.6':
-    resolution: {integrity: sha512-DlBXtLSW0DqYYTW3Ft1/GQFZlTdKY5VAFIC4+km6IK5NiPPDFchGbEJm1j6pSgMqPRHbUQgHJX7RaR76ic1LWA==}
-    peerDependencies:
-      react: '>=16.8'
+  esprima@4.0.1:
+    resolution: {integrity: sha512-eGuFFw7Upda+g4p+QHvnW0RyTX/SVeJBDM/gCtMARO0cLuT2HcEKnTPvhjV6aGeqrCB/sbNop0Kszm0jsaWU4A==}
+    engines: {node: '>=4'}
+    hasBin: true
 
-  '@react-hook/size@2.1.2':
-    resolution: {integrity: sha512-BmE5asyRDxSuQ9p14FUKJ0iBRgV9cROjqNG9jT/EjCM+xHha1HVqbPoT+14FQg1K7xIydabClCibUY4+1tw/iw==}
-    peerDependencies:
-      react: '>=16.8'
+  estree-util-attach-comments@3.0.0:
+    resolution: {integrity: sha512-cKUwm/HUcTDsYh/9FgnuFqpfquUbwIqwKM26BVCGDPVgvaCl/nDCCjUfiLlx6lsEZ3Z4RFxNbOQ60pkaEwFxGw==}
 
-  '@react-hook/throttle@2.2.0':
-    resolution: {integrity: sha512-LJ5eg+yMV8lXtqK3lR+OtOZ2WH/EfWvuiEEu0M3bhR7dZRfTyEJKxH1oK9uyBxiXPtWXiQggWbZirMCXam51tg==}
-    peerDependencies:
-      react: '>=16.8'
+  estree-util-build-jsx@3.0.1:
+    resolution: {integrity: sha512-8U5eiL6BTrPxp/CHbs2yMgP8ftMhR5ww1eIKoWRMlqvltHF8fZn5LRDvTKuxD3DUn+shRbLGqXemcP51oFCsGQ==}
 
-  '@react-hook/window-size@3.1.1':
-    resolution: {integrity: sha512-yWnVS5LKnOUIrEsI44oz3bIIUYqflamPL27n+k/PC//PsX/YeWBky09oPeAoc9As6jSH16Wgo8plI+ECZaHk3g==}
-    peerDependencies:
-      react: '>=16.8'
+  estree-util-is-identifier-name@3.0.0:
+    resolution: {integrity: sha512-hFtqIDZTIUZ9BXLb8y4pYGyk6+wekIivNVTcmvk8NoOh+VeRn5y6cEHzbURrWbfp1fIqdVipilzj+lfaadNZmg==}
 
-  '@react-spectrum/checkbox@3.11.1':
-    resolution: {integrity: sha512-SkiKMYA5VMiIC+Zsob7YnGfT+hpuWsolzi+jS/Qd78h4nMIMj/kwPN17bqsYMqb5D3IM1F4YAkNpWUFFGaAeAA==}
-    peerDependencies:
-      react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
-      react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
+  estree-util-scope@1.0.1:
+    resolution: {integrity: sha512-B0np3dcdxqILX5e9nEi5/Fr4K7gL4oYFVPV1zRa2e9wRCbQoZZNWOZFYyoInvXUPJXBXjss+QXlWLJChDEHDkA==}
 
-  '@react-spectrum/provider@3.11.1':
-    resolution: {integrity: sha512-TsoNdVdmlQ7L+75ILq5Yb3+wp/I1AtIeat0o+Y+ZBxP+TtWpwT1ZtCB5l3cplFVzHzOpZlzO0VaDrDP9ElGYDw==}
-    peerDependencies:
-      react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
-      react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
+  estree-util-to-js@2.0.0:
+    resolution: {integrity: sha512-WDF+xj5rRWmD5tj6bIqRi6CkLIXbbNQUcxQHzGysQzvHmdYG2G7p/Tf0J0gpxGgkeMZNTIjT/AoSvC9Xehcgdg==}
 
-  '@react-stately/checkbox@3.8.1':
-    resolution: {integrity: sha512-jNYNOkro8cgLkeeea24UQdE+PWpsBz/6hGPPM9CrHBvC7x2Egh3iHy1not61Oqp7BI7Rq1K1+Q4q8J37bOTr6w==}
-    peerDependencies:
-      react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
-      react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
+  estree-util-visit@2.0.0:
+    resolution: {integrity: sha512-m5KgiH85xAhhW8Wta0vShLcUvOsh3LLPI2YVwcbio1l7E09NTLL1EyMZFM1OyWowoH0skScNbhOPl4kcBgzTww==}
 
-  '@react-stately/toggle@3.10.1':
-    resolution: {integrity: sha512-oj4goolQJWdeQxRp8a1nZdsUjC779nvAU7pyT3oyWMWrxxrk0heW96TLWhdPjksvre8pLvjbRBbI2kgs8RxmOQ==}
-    peerDependencies:
-      react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
-      react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
+  estree-walker@3.0.3:
+    resolution: {integrity: sha512-7RUKfXgSMMkzt6ZuXmqapOurLGPPfgj6l9uRZ7lRGolvk0y2yocc35LdcxKC5PQZdn2DMqioAQ2NoWcrTKmm6g==}
 
-  '@react-types/button@3.4.1':
-    resolution: {integrity: sha512-B54M84LxdEppwjXNlkBEJyMfe9fd+bvFV7R6+NJvupGrZm/LuFNYjFcHk7yjMKWTdWm6DbpIuQz54n5qTW7Vlg==}
-    peerDependencies:
-      react: ^16.8.0 || ^17.0.0-rc.1
+  etag@1.8.1:
+    resolution: {integrity: sha512-aIL5Fx7mawVa300al2BnEE4iNvo1qETxLrPI/o05L7z6go7fCw1J6EQmbK4FmJ2AS7kgVF/KEZWufBfdClMcPg==}
+    engines: {node: '>= 0.6'}
 
-  '@react-types/checkbox@3.11.0':
-    resolution: {integrity: sha512-VXacLw/pKBcxgwejr2p4uPZtG/XXBnTb6pJCdFtUL6OuFIIOFt/9eTHD+8x2HRPLxWkmo1DD3bFBOinQ7vfu2g==}
-    peerDependencies:
-      '@react-spectrum/provider': ^3.0.0
-      react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
-      react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
+  expand-template@2.0.3:
+    resolution: {integrity: sha512-XYfuKMvj4O35f/pOXLObndIRvyQ+/+6AhODh+OKWj9S9498pHHn/IMszH+gt0fBCRWMNfk1ZSp5x3AifmnI2vg==}
+    engines: {node: '>=6'}
 
-  '@react-types/radio@3.1.2':
-    resolution: {integrity: sha512-vkIic8abrVUyl/YjKU3yTVwn8QgebzuadfV89PsaKc3hdmSiHhDsln5wYsfWOEotqMwPrG1aEv9yRMYO78OQXQ==}
-    peerDependencies:
-      react: ^16.8.0 || ^17.0.0-rc.1
+  expr-eval-fork@3.0.3:
+    resolution: {integrity: sha512-BhC+hbc5lIVjygr840n5DEkW3MQq7H9o+mc1/N7Z5uIiCFVyESLL5DIE7LNq4CYUNxy+XjA+3jRrL/h0Kt2xcg==}
+    engines: {node: '>=16.9.0'}
 
-  '@react-types/shared@3.35.0':
-    resolution: {integrity: sha512-iNWvuzEwANttpQpdlu8nPBtdHb0mcCMj1ZTH//iRB5E/14IAnyRlR25rxH7pNLyzHINsPGEKnWvpwDMCT6vziQ==}
-    peerDependencies:
-      react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
+  express@4.22.0:
+    resolution: {integrity: sha512-c2iPh3xp5vvCLgaHK03+mWLFPhox7j1LwyxcZwFVApEv5i0X+IjPpbT50SJJwwLpdBVfp45AkK/v+AFgv/XlfQ==}
+    engines: {node: '>= 0.10.0'}
 
-  '@react-types/shared@3.36.1':
-    resolution: {integrity: sha512-AzsuD9OfxTOZMMvTRhlN3oHBwOmFN7tDh27LzqmHt4+uOgPhJT7ZM7/kVs/8/o0WxayMUIk3hBmCFRHv1FUoag==}
-    peerDependencies:
-      react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
+  extend@3.0.2:
+    resolution: {integrity: sha512-fjquC59cD7CyW6urNXK0FBufkZcoiGG80wTuPujX590cB5Ttln20E2UB4S/WARVqhXffZl2LNgS+gQdPIIim/g==}
 
-  '@react-types/shared@3.9.0':
-    resolution: {integrity: sha512-YYksINfR6q92P10AhPEGo47Hd7oz1hrnZ6Vx8Gsrq62IbqDdv1XOTzPBaj17Z1ymNY2pitLUSEXsLmozt4wxxQ==}
-    peerDependencies:
-      react: ^16.8.0 || ^17.0.0-rc.1
+  fast-deep-equal@3.1.3:
+    resolution: {integrity: sha512-f3qQ9oQy9j2AhBe/H9VC91wLmKBCCU/gDOnKNAYG5hswO7BLKj09Hc5HYNz9cGI++xlpDCIgDaitVs03ATR84Q==}
 
-  '@react-types/switch@3.1.2':
-    resolution: {integrity: sha512-EaYWoLvUCpOnt//Ov8VBxOjbs4hBpYE/rBAzzIknXaFvKOu867iZBFL7FJbcemOgC8/dwyaj6GUZ1Gw3Z1g59w==}
-    peerDependencies:
-      react: ^16.8.0 || ^17.0.0-rc.1
+  fast-glob@3.3.3:
+    resolution: {integrity: sha512-7MptL8U0cqcFdzIzwOTHoilX9x5BrNqye7Z/LuC7kCMRio1EMSyqRK3BEAUD7sXRq4iT4AzTVuZdhgQ2TCvYLg==}
+    engines: {node: '>=8.6.0'}
 
-  '@react-types/textfield@3.3.0':
-    resolution: {integrity: sha512-lOf0tx3c3dVaomH/uvKpOKFVTXQ232kLnMhOJTtj97JDX7fTr3SNhDUV0G8Zf4M0vr+l+xkTrJkywYE23rzliw==}
-    peerDependencies:
-      react: ^16.8.0 || ^17.0.0-rc.1
+  fast-json-stable-stringify@2.1.0:
+    resolution: {integrity: sha512-lhd/wF+Lk98HZoTCtlVraHtfh5XYijIjalXck7saUtuanSDyLMxnHhSXEDJqHxD7msR8D0uCmqlkwjCV8xvwHw==}
 
-  '@redocly/ajv@8.18.1':
-    resolution: {integrity: sha512-Ifm/pP/tul1qmAecpbVxCBluVE32rKfjf8gYXH4xI2gCv9mRWFhJMHzkPDM4TXlxwPQYIFegymlsy8lXz7optA==}
+  fast-memoize@2.5.2:
+    resolution: {integrity: sha512-Ue0LwpDYErFbmNnZSF0UH6eImUwDmogUO1jyE+JbN2gsQz/jICm1Ve7t9QT0rNSsfJt+Hs4/S3GnsDVjL4HVrw==}
+
+  fast-safe-stringify@2.1.1:
+    resolution: {integrity: sha512-W+KJc2dmILlPplD/H4K9l9LcAHAfPtP6BY84uVLXQ6Evcz9Lcg33Y2z1IVblT6xdY54PXYVHEv+0Wpq8Io6zkA==}
 
-  '@redocly/ajv@8.18.3':
-    resolution: {integrity: sha512-l42u0of3hY98sN2A+M4qTX1O/KrpgGH32Hu9kP2GtHyD5Dfqq86PKFLe5dwaD8DEnNmlOlll2BAmeEtf0DaySg==}
+  fast-uri@3.1.8:
+    resolution: {integrity: sha512-GZMtZUTNRpOVIECoXwLNZS5xUGE+mVNbTB8h/7Rwh2TFWcBQiPzTgyZi05BF9UMZKkLJv8XBRJTlU7zg8+ZfMg==}
 
-  '@redocly/cli@2.38.0':
-    resolution: {integrity: sha512-zYwQiDJTqoiscB6pFwd80FwI065gA13lp8hg2tgjDDu4p8gotVdCD/EOCaPTalIHskiIa1UFxEPRErPOgkWqJw==}
-    engines: {node: '>=22.12.0 || >=20.19.0 <21.0.0', npm: '>=10'}
+  fast-xml-builder@1.3.1:
+    resolution: {integrity: sha512-pIM/1n3ntFXKYrUZwW7QCK0gAW7XY+wzj1YMIV3tLDvPj/V+zTGJK5e3/4WJfwj0qWw2ElNXiTixda/R+3YSug==}
+
+  fast-xml-parser@5.7.3:
+    resolution: {integrity: sha512-C0AaNuC+mscy6vrAQKAc/rMq+zAPHodfHGZu4sGVehvAQt/JLG1O5zEcYcXSY5zSqr4YVgxsB+pHXTq0i7eDlg==}
     hasBin: true
 
-  '@redocly/config@0.49.1':
-    resolution: {integrity: sha512-Eid8/bDcsf2bpTJ2qZhULflf6Y/TtoUFZt0+a5XZzjZj0uA8L8EQiY/nEdBd6lZQlZsnu8/cAUhTyBebnLi0gA==}
+  fastq@1.20.3:
+    resolution: {integrity: sha512-XKv5nnLs6nLF71NgiKJLIZFLkPyIEuOselLG7ujZnGrRfQK8HpvY+WqKhAJUAdLomwVHErVS4LfxFlPq0/FTAw==}
 
-  '@redocly/openapi-core@2.36.0':
-    resolution: {integrity: sha512-u44e3yn0Zj2d59+SzMrHVj0DQZfQJm8C8uaf4MhJDAiHLHyd7adcAoRiqDD+LzkfLvgBepp20Jo6gDEIGl1mDg==}
-    engines: {node: '>=22.12.0 || >=20.19.0 <21.0.0', npm: '>=10'}
+  fault@2.0.1:
+    resolution: {integrity: sha512-WtySTkS4OKev5JtpHXnib4Gxiurzh5NCGvWrFaZ34m6JehfTUhKZvn9njTfw48t6JumVQOmrKqpmGcdwxnhqBQ==}
 
-  '@reduxjs/toolkit@2.12.0':
-    resolution: {integrity: sha512-KiT+RzZbp6mQET+Mg+h2c97+9j1sNflUxQkIHI7Yuzf6Peu+OYpmkn6nbHWmLLWj+1ZODUJFwGZ7gx3L9R9EOw==}
+  favicons@7.2.0:
+    resolution: {integrity: sha512-k/2rVBRIRzOeom3wI9jBPaSEvoTSQEW4iM0EveBmBBKFxO8mSyyRWtDlfC3VnEfu0avmjrMzy8/ZFPSe6F71Hw==}
+    engines: {node: '>=14.0.0'}
+
+  fdir@6.5.0:
+    resolution: {integrity: sha512-tIbYtZbucOs0BRGqPJkshJUYdL+SDH7dVM8gjy+ERp3WAUjLEFJE+02kanyHtwjWOnwrKYBiwAmM0p4kLJAnXg==}
+    engines: {node: '>=12.0.0'}
     peerDependencies:
-      react: ^16.9.0 || ^17.0.0 || ^18 || ^19
-      react-redux: ^7.2.1 || ^8.1.3 || ^9.0.0
+      picomatch: ^3 || ^4
     peerDependenciesMeta:
-      react:
-        optional: true
-      react-redux:
+      picomatch:
         optional: true
 
-  '@rehooks/component-size@1.0.3':
-    resolution: {integrity: sha512-pnYld+8SSF2vXwdLOqBGUyOrv/SjzwLjIUcs/4c1JJgR0q4E9eBtBfuZMD6zUD51fvSehSsbnlQMzotSmPTXPg==}
-    peerDependencies:
-      react: '>=16.8.0'
+  fflate@0.7.3:
+    resolution: {integrity: sha512-0Zz1jOzJWERhyhsimS54VTqOteCNwRtIlh8isdL0AXLo0g7xNTfTL7oWrkmCnPhZGocKIkWHBistBrrpoNH3aw==}
 
-  '@rjsf/core@5.24.13':
-    resolution: {integrity: sha512-ONTr14s7LFIjx2VRFLuOpagL76sM/HPy6/OhdBfq6UukINmTIs6+aFN0GgcR0aXQHFDXQ7f/fel0o/SO05Htdg==}
-    engines: {node: '>=14'}
-    peerDependencies:
-      '@rjsf/utils': ^5.24.x
-      react: ^16.14.0 || >=17
+  fflate@0.7.5:
+    resolution: {integrity: sha512-QieYf//cis6ywHNi5qW1+PXPQ4bC+XVJAtS4AXIML8P76GroEiOxm/oQtn1f02UkJY1+KsXMJcC+R2v/Eg4G3g==}
 
-  '@rjsf/utils@5.24.13':
-    resolution: {integrity: sha512-rNF8tDxIwTtXzz5O/U23QU73nlhgQNYJ+Sv5BAwQOIyhIE2Z3S5tUiSVMwZHt0julkv/Ryfwi+qsD4FiE5rOuw==}
-    engines: {node: '>=14'}
-    peerDependencies:
-      react: ^16.14.0 || >=17
+  fflate@0.8.2:
+    resolution: {integrity: sha512-cPJU47OaAoCbg0pBvzsgpTPhmhqI5eJjh/JIu8tPj5q+T7iLvW/JAYUqmE7KOB4R1ZyEhzBaIQpQpardBF5z8A==}
 
-  '@rjsf/validator-ajv8@5.24.13':
-    resolution: {integrity: sha512-oWHP7YK581M8I5cF1t+UXFavnv+bhcqjtL1a7MG/Kaffi0EwhgcYjODrD8SsnrhncsEYMqSECr4ZOEoirnEUWw==}
-    engines: {node: '>=14'}
+  fill-range@7.1.1:
+    resolution: {integrity: sha512-YsGpe3WHLK8ZYi4tWDg2Jy3ebRz2rXowDxnld4bkQB00cc/1Zw9AWnC0i9ztDJitivtQvaI9KaLyKrc+hBW0yg==}
+    engines: {node: '>=8'}
+
+  finalhandler@1.3.2:
+    resolution: {integrity: sha512-aA4RyPcd3badbdABGDuTXCMTtOneUCAYH/gxoYRTZlIJdF0YPWuGqiAsIrhNnnqdXGswYk6dGujem4w80UJFhg==}
+    engines: {node: '>= 0.8'}
+
+  follow-redirects@1.16.1:
+    resolution: {integrity: sha512-FNvFGzoMLWmE6Yj9spb/zjd7yiNCHiAW9/Tg9CXrQ8wuu32HtlJOwWO11OJafl5FfY3DxTdQ0vj42zU1kvv5jg==}
+    engines: {node: '>=4.0'}
     peerDependencies:
-      '@rjsf/utils': ^5.24.x
+      debug: '*'
+    peerDependenciesMeta:
+      debug:
+        optional: true
 
-  '@rspack/binding-darwin-arm64@1.7.11':
-    resolution: {integrity: sha512-oduECiZVqbO5zlVw+q7Vy65sJFth99fWPTyucwvLJJtJkPL5n17Uiql2cYP6Ijn0pkqtf1SXgK8WjiKLG5bIig==}
-    cpu: [arm64]
-    os: [darwin]
+  for-each@0.3.5:
+    resolution: {integrity: sha512-dKx12eRCVIzqCxFGplyFKJMPvLEWgmNtUrpTiJIR5u97zEhRG8ySrtboPHZXx7daLxQVrl643cTzbab2tkQjxg==}
+    engines: {node: '>= 0.4'}
 
-  '@rspack/binding-darwin-x64@1.7.11':
-    resolution: {integrity: sha512-a1+TtTE9ap6RalgFi7FGIgkJP6O4Vy6ctv+9WGJy53E4kuqHR0RygzaiVxCI/GMc/vBT9vY23hyrpWb3d1vtXA==}
-    cpu: [x64]
-    os: [darwin]
+  form-data-encoder@2.1.4:
+    resolution: {integrity: sha512-yDYSgNMraqvnxiEXO4hi88+YZxaHC6QKzb5N84iRCTDeRO7ZALpir/lVmf/uXUhnwUr2O4HU8s/n6x+yNjQkHw==}
+    engines: {node: '>= 14.17'}
 
-  '@rspack/binding-linux-arm64-gnu@1.7.11':
-    resolution: {integrity: sha512-P0QrGRPbTWu6RKWfN0bDtbnEps3rXH0MWIMreZABoUrVmNQKtXR6e73J3ub6a+di5s2+K0M2LJ9Bh2/H4UsDUA==}
-    cpu: [arm64]
-    os: [linux]
-    libc: [glibc]
+  form-data@4.0.6:
+    resolution: {integrity: sha512-vKatAh4SlVfgbv+YtmhiRjhEMJsYpsG1Y2rMQtR+SVSbytsSD1YGzDIcrAJmdFec88u/+VoGmxnl+80gL1tRCQ==}
+    engines: {node: '>= 6'}
 
-  '@rspack/binding-linux-arm64-musl@1.7.11':
-    resolution: {integrity: sha512-6ky7R43VMjWwmx3Yx7Jl7faLBBMAgMDt+/bN35RgwjiPgsIByz65EwytUVuW9rikB43BGHvA/eqlnjLrUzNBqw==}
-    cpu: [arm64]
-    os: [linux]
-    libc: [musl]
+  format@0.2.2:
+    resolution: {integrity: sha512-wzsgA6WOq+09wrU1tsJ09udeR/YZRaeArL9e1wPbFg3GG2yDnC2ldKpxs4xunpFF9DgqCqOIra3bc1HWrJ37Ww==}
+    engines: {node: '>=0.4.x'}
 
-  '@rspack/binding-linux-x64-gnu@1.7.11':
-    resolution: {integrity: sha512-cuOJMfCOvb2Wgsry5enXJ3iT1FGUjdPqtGUBVupQlEG4ntSYsQ2PtF4wIDVasR3wdxC5nQbipOrDiN/u6fYsdQ==}
-    cpu: [x64]
-    os: [linux]
-    libc: [glibc]
+  forwarded@0.2.0:
+    resolution: {integrity: sha512-buRG0fpBtRHSTCOASe6hD258tEubFoRLb4ZNA6NxMVHNw2gOcwHo9wyablzMzOA5z9xA9L1KNjk/Nt6MT9aYow==}
+    engines: {node: '>= 0.6'}
 
-  '@rspack/binding-linux-x64-musl@1.7.11':
-    resolution: {integrity: sha512-CoK37hva4AmHGh3VCsQXmGr40L36m1/AdnN5LEjUX6kx5rEH7/1nEBN6Ii72pejqDVvk9anEROmPDiPw10tpFg==}
-    cpu: [x64]
-    os: [linux]
-    libc: [musl]
+  fractional-indexing@3.2.0:
+    resolution: {integrity: sha512-PcOxmqwYCW7O2ovKRU8OoQQj2yqTfEB/yeTYk4gPid6dN5ODRfU1hXd9tTVZzax/0NkO7AxpHykvZnT1aYp/BQ==}
+    engines: {node: ^14.13.1 || >=16.0.0}
 
-  '@rspack/binding-wasm32-wasi@1.7.11':
-    resolution: {integrity: sha512-OtrmnPUVJMxjNa3eDMfHyPdtlLRmmp/aIm0fQHlAOATbZvlGm12q7rhPW5BXTu1yh+1rQ1/uqvz+SzKEZXuJaQ==}
-    cpu: [wasm32]
+  fresh@0.5.2:
+    resolution: {integrity: sha512-zJ2mQYM18rEFOudeV4GShTGIQ7RbzA7ozbU9I/XBpm7kqgMywgmylMwXHxZJmkVoYkna9d2pVXVXPdYTP9ej8Q==}
+    engines: {node: '>= 0.6'}
 
-  '@rspack/binding-win32-arm64-msvc@1.7.11':
-    resolution: {integrity: sha512-lObFW6e5lCWNgTBNwT//yiEDbsxm9QG4BYUojqeXxothuzJ/L6ibXz6+gLMvbOvLGV3nKgkXmx8GvT9WDKR0mA==}
-    cpu: [arm64]
-    os: [win32]
+  front-matter@4.0.2:
+    resolution: {integrity: sha512-I8ZuJ/qG92NWX8i5x1Y8qyj3vizhXS31OxjKDu3LKP+7/qBgfIKValiZIEwoVoJKUHlhWtYrktkxV1XsX+pPlg==}
 
-  '@rspack/binding-win32-ia32-msvc@1.7.11':
-    resolution: {integrity: sha512-0pYGnZd8PPqNR68zQ8skamqNAXEA1sUfXuAdYcknIIRq2wsbiwFzIc0Pov1cIfHYab37G7sSIPBiOUdOWF5Ivw==}
-    cpu: [ia32]
-    os: [win32]
+  fs-constants@1.0.0:
+    resolution: {integrity: sha512-y6OAwoSIf7FyjMIv94u+b5rdheZEjzR63GTyZJm5qh4Bi+2YgwLCcI/fPFZkL5PSixOt6ZNKm+w+Hfp/Bciwow==}
 
-  '@rspack/binding-win32-x64-msvc@1.7.11':
-    resolution: {integrity: sha512-EeQXayoQk/uBkI3pdoXfQBXNIUrADq56L3s/DFyM2pJeUDrWmhfIw2UFIGkYPTMSCo8F2JcdcGM32FGJrSnU0Q==}
-    cpu: [x64]
-    os: [win32]
+  fs-extra@10.1.0:
+    resolution: {integrity: sha512-oRXApq54ETRj4eMiFzGnHWGy+zo5raudjuxN0b8H7s/RU2oW0Wvsx9O0ACRN/kRq9E8Vu/ReskGB5o3ji+FzHQ==}
+    engines: {node: '>=12'}
 
-  '@rspack/binding@1.7.11':
-    resolution: {integrity: sha512-2MGdy2s2HimsDT444Bp5XnALzNRxuBNc7y0JzyuqKbHBywd4x2NeXyhWXXoxufaCFu5PBc9Qq9jyfjW2Aeh06Q==}
+  fs-extra@11.1.0:
+    resolution: {integrity: sha512-0rcTq621PD5jM/e0a3EJoGC/1TC5ZBCERW82LQuwfGnCa1V8w7dpYH1yNu+SLb6E5dkeCBzKEyLGlFrnr+dUyw==}
+    engines: {node: '>=14.14'}
 
-  '@rspack/core@1.7.11':
-    resolution: {integrity: sha512-rsD9b+Khmot5DwCMiB3cqTQo53ioPG3M/A7BySu8+0+RS7GCxKm+Z+mtsjtG/vsu4Tn2tcqCdZtA3pgLoJB+ew==}
-    engines: {node: '>=18.12.0'}
-    peerDependencies:
-      '@swc/helpers': '>=0.5.1'
-    peerDependenciesMeta:
-      '@swc/helpers':
-        optional: true
+  fs-extra@11.1.1:
+    resolution: {integrity: sha512-MGIE4HOvQCeUCzmlHs0vXpih4ysz4wg9qiSAu6cd42lVwPbTM1TjV7RusoyQqMmk/95gdQZX72u+YW+c3eEpFQ==}
+    engines: {node: '>=14.14'}
 
-  '@rspack/lite-tapable@1.1.0':
-    resolution: {integrity: sha512-E2B0JhYFmVAwdDiG14+DW0Di4Ze4Jg10Pc4/lILUrd5DRCaklduz2OvJ5HYQ6G+hd+WTzqQb3QnDNfK4yvAFYw==}
+  fs-extra@11.2.0:
+    resolution: {integrity: sha512-PmDi3uwK5nFuXh7XDTlVnS17xJS7vW36is2+w3xcv8SVxiB4NyATf4ctkVY5bkSjX0Y4nbvZCq1/EjtEyr9ktw==}
+    engines: {node: '>=14.14'}
 
-  '@sentry/browser@6.19.7':
-    resolution: {integrity: sha512-oDbklp4O3MtAM4mtuwyZLrgO1qDVYIujzNJQzXmi9YzymJCuzMLSRDvhY83NNDCRxf0pds4DShgYeZdbSyKraA==}
-    engines: {node: '>=6'}
+  fs-extra@11.3.6:
+    resolution: {integrity: sha512-w8ZNZr2mKIc7qeNaQ9AVPT1+iFaI+Avd4xudVOvdDJ8VytREi1Ft5Ih7hd9jjehod8vAM5GMsfQ/TpPf4EyoEA==}
+    engines: {node: '>=14.14'}
 
-  '@sentry/core@6.19.7':
-    resolution: {integrity: sha512-tOfZ/umqB2AcHPGbIrsFLcvApdTm9ggpi/kQZFkej7kMphjT+SGBiQfYtjyg9jcRW+ilAR4JXC9BGKsdEQ+8Vw==}
-    engines: {node: '>=6'}
+  fs.realpath@1.0.0:
+    resolution: {integrity: sha512-OO0pH2lK6a0hZnAdau5ItzHPI6pUlvI7jMVnxUQRtw4owF2wk8lOSabtGDCTP4Ggrg2MbGnWO9X8K1t4+fGMDw==}
 
-  '@sentry/hub@6.19.7':
-    resolution: {integrity: sha512-y3OtbYFAqKHCWezF0EGGr5lcyI2KbaXW2Ik7Xp8Mu9TxbSTuwTe4rTntwg8ngPjUQU3SUHzgjqVB8qjiGqFXCA==}
-    engines: {node: '>=6'}
+  fsevents@2.3.3:
+    resolution: {integrity: sha512-5xoDfX+fL7faATnagmWPpbFtwh/R77WmMMqqHGS65C3vvB0YHrgF+B1YmZ3441tMj5n63k0212XNoJwzlhffQw==}
+    engines: {node: ^8.16.0 || ^10.6.0 || >=11.0.0}
+    os: [darwin]
 
-  '@sentry/minimal@6.19.7':
-    resolution: {integrity: sha512-wcYmSJOdvk6VAPx8IcmZgN08XTXRwRtB1aOLZm+MVHjIZIhHoBGZJYTVQS/BWjldsamj2cX3YGbGXNunaCfYJQ==}
-    engines: {node: '>=6'}
+  function-bind@1.1.2:
+    resolution: {integrity: sha512-7XHNxH7qX9xG5mIwxkhumTox/MIRNcOgDrxWsMt2pAr23WHp6MrRlN7FBSFpCpr+oVO0F744iUgR82nJMfG2SA==}
 
-  '@sentry/react@6.19.7':
-    resolution: {integrity: sha512-VzJeBg/v41jfxUYPkH2WYrKjWc4YiMLzDX0f4Zf6WkJ4v3IlDDSkX6DfmWekjTKBho6wiMkSNy2hJ1dHfGZ9jA==}
-    engines: {node: '>=6'}
-    peerDependencies:
-      react: 15.x || 16.x || 17.x || 18.x
+  function.prototype.name@1.2.0:
+    resolution: {integrity: sha512-jObKIik1P2QjPHP5nz5BaOtUlfgS0fWo8IUByNXkM+o+02sJOi94em77GwJKQSJ3gfPHdgzLNrHc1uokV4P/ew==}
+    engines: {node: '>= 0.4'}
 
-  '@sentry/types@6.19.7':
-    resolution: {integrity: sha512-jH84pDYE+hHIbVnab3Hr+ZXr1v8QABfhx39KknxqKWr2l0oEItzepV0URvbEhB446lk/S/59230dlUUIBGsXbg==}
-    engines: {node: '>=6'}
+  functions-have-names@1.2.3:
+    resolution: {integrity: sha512-xckBUXyTIqT97tq2x2AMb+g163b5JFysYk0x4qxNFwbfQkmNZoiRHb6sPzI9/QV33WeuvVYBUIiD4NzNIyqaRQ==}
 
-  '@sentry/utils@6.19.7':
-    resolution: {integrity: sha512-z95ECmE3i9pbWoXQrD/7PgkBAzJYR+iXtPuTkpBjDKs86O3mT+PXOT3BAn79w2wkn7/i3vOGD2xVr1uiMl26dA==}
-    engines: {node: '>=6'}
+  gcd@0.0.1:
+    resolution: {integrity: sha512-VNx3UEGr+ILJTiMs1+xc5SX1cMgJCrXezKPa003APUWNqQqaF6n25W8VcR7nHN6yRWbvvUTwCpZCFJeWC2kXlw==}
+
+  generator-function@2.0.1:
+    resolution: {integrity: sha512-SFdFmIJi+ybC0vjlHN0ZGVGHc3lgE0DxPAT0djjVg+kjOnSqclqmj0KQ7ykTOLP6YxoqOvuAODGdcHJn+43q3g==}
+    engines: {node: '>= 0.4'}
 
-  '@sideway/address@4.1.5':
-    resolution: {integrity: sha512-IqO/DUQHUkPeixNQ8n0JA6102hT9CmaljNTPmQ1u8MEhBo/R4Q8eKLN/vGZxuebwOroDB4cbpjheD4+/sKFK4Q==}
+  get-caller-file@2.0.5:
+    resolution: {integrity: sha512-DyFP3BM/3YHTQOCUL/w0OZHR0lpKeGrxotcHWcqNEdnltqFwXVfhEBQ94eIo34AfQpo0rGki4cyIiftY06h2Fg==}
+    engines: {node: 6.* || 8.* || >= 10.*}
 
-  '@sideway/formula@3.0.1':
-    resolution: {integrity: sha512-/poHZJJVjx3L+zVD6g9KgHfYnb443oi7wLu/XKojDviHy6HOEOA6z1Trk5aR1dGcmPenJEgb2sK2I80LeS3MIg==}
+  get-east-asian-width@1.6.0:
+    resolution: {integrity: sha512-QRbvDIbx6YklUe6RxeTeleMR0yv3cYH6PsPZHcnVn7xv7zO1BHN8r0XETu8n6Ye3Q+ahtSarc3WgtNWmehIBfA==}
+    engines: {node: '>=18'}
 
-  '@sideway/pinpoint@2.0.0':
-    resolution: {integrity: sha512-RNiOoTPkptFtSVzQevY/yWtZwf/RxyVnPy/OcA9HBM3MlGDnBEYL5B41H0MTn0Uec8Hi+2qUtTfG2WWZBmMejQ==}
+  get-intrinsic@1.3.0:
+    resolution: {integrity: sha512-9fSjSaos/fRIVIp+xSJlE6lfwhES7LNtKaCBIamHsjr2na1BiABJPo0mOjjz8GJDURarmCPGqaiVg5mfjb98CQ==}
+    engines: {node: '>= 0.4'}
 
-  '@sinclair/typebox@0.27.10':
-    resolution: {integrity: sha512-MTBk/3jGLNB2tVxv6uLlFh1iu64iYOQ2PbdOSK3NW8JZsmlaOh2q6sdtKowBhfw8QFLmYNzTW4/oK4uATIi6ZA==}
+  get-proto@1.0.1:
+    resolution: {integrity: sha512-sTSfBjoXBp89JvIKIefqw7U2CCebsc74kiY6awiGogKtoSGbgjYE/G/+l9sF3MWFPNc9IcoOC4ODfKHfxFmp0g==}
+    engines: {node: '>= 0.4'}
 
-  '@sindresorhus/is@4.6.0':
-    resolution: {integrity: sha512-t09vSN3MdfsyCHoFcTRCH/iUtG7OJ0CsjzB8cjAmKc/va/kIgeDI/TxsigdncE/4be734m0cvIYwNaV4i2XqAw==}
+  get-stream@6.0.1:
+    resolution: {integrity: sha512-ts6Wi+2j3jQjqi70w5AlN8DFnkSwC+MqmxEzdEALB2qXZYV3X/b1CTfgPLGJNMeAWxdPfU8FO1ms3NUfaHCPYg==}
     engines: {node: '>=10'}
 
-  '@sindresorhus/is@5.6.0':
-    resolution: {integrity: sha512-TV7t8GKYaJWsn00tFDqBw8+Uqmr8A0fRU1tvTQhyZzGv0sJCGRQL3JGMI3ucuKo3XIZdUP+Lx7/gh2t3lewy7g==}
-    engines: {node: '>=14.16'}
+  get-symbol-description@1.1.0:
+    resolution: {integrity: sha512-w9UMqWwJxHNOvoNzSJ2oPF5wvYcvP7jUvYzhp67yEhTi17ZDBBC1z9pTdGuzjD+EFIqLSYRweZjqfiPzQ06Ebg==}
+    engines: {node: '>= 0.4'}
 
-  '@slorber/react-helmet-async@1.3.0':
-    resolution: {integrity: sha512-e9/OK8VhwUSc67diWI8Rb3I0YgI9/SBQtnhe9aEuK6MhZm7ntZZimXgwXnd8W96YTmSOb9M4d8LwhRZyhWr/1A==}
-    peerDependencies:
-      react: ^16.6.0 || ^17.0.0 || ^18.0.0 || ^19.0.0
-      react-dom: ^16.6.0 || ^17.0.0 || ^18.0.0 || ^19.0.0
+  github-from-package@0.0.0:
+    resolution: {integrity: sha512-SyHy3T1v2NUXn29OsWdxmK6RwHD+vkj3v8en8AOBZ1wBQ/hCAQ5bAQTD02kW4W9tUp/3Qh6J8r9EvntiyCmOOw==}
 
-  '@slorber/remark-comment@1.0.0':
-    resolution: {integrity: sha512-RCE24n7jsOj1M0UPvIQCHTe7fI0sFL4S2nwKVWwHyVr/wI/H8GosgsJGyhnsZoGFnD/P2hLf1mSbrrgSLN93NA==}
+  glob-parent@5.1.2:
+    resolution: {integrity: sha512-AOIgSQCepiJYwP3ARnGx+5VnTu2HBYdzbGP45eLw1vr3zB3vZLeyed1sC9hnbcOc9/SrMyM5RPQrkGz4aS9Zow==}
+    engines: {node: '>= 6'}
 
-  '@spectrum-icons/ui@3.7.1':
-    resolution: {integrity: sha512-veQymocUYo5OciXQajSailOdbWe+k6+2ehfF8D4d0V923D4xOUadtT253xXZ5vEQjPat6Kyp2WDKeQNjd7kL1w==}
-    peerDependencies:
-      '@adobe/react-spectrum': ^3.47.0
-      react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
-      react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
+  glob-parent@6.0.2:
+    resolution: {integrity: sha512-XxwI8EOhVQgWp6iDL+3b0r86f4d6AX6zSU55HfB4ydCEuXLXc5FcYeOu+nnGftS4TEju/11rt4KJPTMgbfmv4A==}
+    engines: {node: '>=10.13.0'}
 
-  '@spectrum-icons/workflow@4.3.1':
-    resolution: {integrity: sha512-kDF+/EbFVyLGytotqqdYt4uSij4j/PQmDQO5km/C6DyzKjyuic3FnSBFinR+mA6oFv1OjMcLvrrDBqK3wbqRlA==}
-    peerDependencies:
-      '@adobe/react-spectrum': ^3.47.0
-      react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
-      react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
+  glob@7.1.6:
+    resolution: {integrity: sha512-LwaxwyZ72Lk7vZINtNNrywX0ZuLyStrdDtabefZKAY5ZGJhVtgdznluResxNmPitE0SAO+O26sWTHeKSI2wMBA==}
+    deprecated: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me
 
-  '@standard-schema/spec@1.1.0':
-    resolution: {integrity: sha512-l2aFy5jALhniG5HgqrD6jXLi/rUWrKvqN/qJx6yoJsgKhblVd+iqqU4RCXavm/jPityDo5TCvKMnpjKnOriy0w==}
+  globalthis@1.0.4:
+    resolution: {integrity: sha512-DpLKbNU4WylpxJykQujfCcwYWiV/Jhm50Goo0wrVILAv5jOr9d+H+UR3PhSCD2rCCEIg0uc+G+muBTwD54JhDQ==}
+    engines: {node: '>= 0.4'}
 
-  '@standard-schema/utils@0.3.0':
-    resolution: {integrity: sha512-e7Mew686owMaPJVNNLs55PUvgz371nKgwsc4vxE49zsODpJEnxgxRo2y/OKrqueavXgZNMDVj3DdHFlaSAeU8g==}
+  gopd@1.2.0:
+    resolution: {integrity: sha512-ZUKRh6/kUFoAiTAtTYPZJ3hw9wNxx+BIBOijnlG9PnrJsCcSjs1wyyD6vJpaYtgnzDrKYRSqf3OO6Rfa93xsRg==}
+    engines: {node: '>= 0.4'}
 
-  '@stellar/open-rpc-docs-react@0.2.1':
-    resolution: {integrity: sha512-2UYOBbaQ8FBB3nd6StV9wfbiKmMlBXuptQOwww4kKzvZRgOaVXzZ41KDtFozqjrsCYoXHaCUjMY8t9GtDXdFlw==}
-    engines: {node: '>=20.0.0'}
-    peerDependencies:
-      '@typescript-eslint/eslint-plugin': ^7.0.0
-      postcss: ^8.4.0
-      react: ^18.0.0
-      react-dom: ^18.0.0
+  got@12.6.1:
+    resolution: {integrity: sha512-mThBblvlAF1d4O5oqyvN+ZxLAYwIJK7bpMxgYqPD9okW0C3qm5FFn7k811QrcuEBwaogR3ngOFoCfs6mRv7teQ==}
+    engines: {node: '>=14.16'}
 
-  '@stellar/prettier-config@1.2.0':
-    resolution: {integrity: sha512-oL9qJ7+7aWnImpbcldroQrvtMCZ9yx4JL/tmDZ860RpBQd2ahkc8bX6/k2ehFK8gpb9ltYu4mtU49wufUuYhGg==}
-    peerDependencies:
-      prettier: ^3.2.5
+  got@13.0.0:
+    resolution: {integrity: sha512-XfBk1CxOOScDcMr9O1yKkNaQyy865NbYs+F7dr4H0LZMVgCj2Le59k6PqbNHoL5ToeaEQUYh6c6yMfVcc6SJxA==}
+    engines: {node: '>=16'}
 
-  '@stoplight/json-schema-merge-allof@0.8.0':
-    resolution: {integrity: sha512-g8e0s43v96Xbzvd8d6KKUuJTO16CS2oJglJrviUi8ASIUxzFvAJqTHWLtGmpTryisQopqg1evXGJfi0+164+Qw==}
+  graceful-fs@4.2.11:
+    resolution: {integrity: sha512-RbJ5/jmFcNNCcDV5o9eTnBLJ/HszWV0P73bc+Ff4nS/rJj+YaS6IGyiOL0VoBYX+l1Wrl3k63h/KrH+nhJ0XvQ==}
 
-  '@stoplight/json-schema-tree@4.0.0':
-    resolution: {integrity: sha512-SAGtof+ihIdPqETR+7XXOaqZJcrbSih/xEahaw5t1nXk5sVW6ss2l5A1WCIuvtvnQiUKnBfanmZU4eoM1ZvItg==}
-    engines: {node: '>=10.18'}
+  graphql@16.11.0:
+    resolution: {integrity: sha512-mS1lbMsxgQj6hge1XZ6p7GPhbrtFwUFYi3wRzXAC/FmYnyXMTvvI3td3rjmQ2u8ewXueaSvRPWaEcgVVOT9Jnw==}
+    engines: {node: ^12.22.0 || ^14.16.0 || ^16.0.0 || >=17.0.0}
 
-  '@stoplight/json-schema-viewer@4.16.4':
-    resolution: {integrity: sha512-5+2mQIhoFFPzk1Gxb1khrVk2Y5BzEIGcNnY74Ky0mo1ipkSNLBWX5ALU8Kn1rTjVjgO8KHacqR4rw/ZaNhxwhQ==}
-    engines: {node: '>=16'}
-    peerDependencies:
-      '@stoplight/markdown-viewer': ^5
-      '@stoplight/mosaic': ^1.32
-      '@stoplight/mosaic-code-viewer': ^1.32
-      react: '>=16.8'
-      react-dom: '>=16.8'
-
-  '@stoplight/json@3.21.7':
-    resolution: {integrity: sha512-xcJXgKFqv/uCEgtGlPxy3tPA+4I+ZI4vAuMJ885+ThkTHFVkC+0Fm58lA9NlsyjnkpxFh4YiQWpH+KefHdbA0A==}
-    engines: {node: '>=8.3.0'}
+  harfbuzzjs@0.10.0:
+    resolution: {integrity: sha512-SN8LVwCOzvTq3OPNd0+EAghgXugItz56wst567D1vs7LnnKGWprhi3EG58aVOBwhN8HEbQxL4I9NDWkcXUutRw==}
 
-  '@stoplight/lifecycle@2.3.3':
-    resolution: {integrity: sha512-JbPRTIzPZabeYPAk5+gdsnfwAxqW35G9e0ZjOG3toUmNViLOsEzuK4vpWd+Prv2Mw8HRmu+haiYizteZp6mk0w==}
-    engines: {node: '>=8.3.0'}
+  has-bigints@1.1.0:
+    resolution: {integrity: sha512-R3pbpkcIqv2Pm3dUwgjclDRVmWpTJW2DcMzcIhEXEx1oh/CEMObMm3KLmRJOdvhM7o4uQBnwr8pzRK2sJWIqfg==}
+    engines: {node: '>= 0.4'}
 
-  '@stoplight/markdown-viewer@5.7.1':
-    resolution: {integrity: sha512-EiJC0w/l+Juc49fVCBOEOOg/NdCWDC8o1lS7d6P5skHS5G+hw1c3GNlCZ2BSqs8z8kkmSzSDWo5XY1S16NVJbQ==}
-    engines: {node: '>=12'}
-    peerDependencies:
-      '@stoplight/mosaic': ^1.24.4
-      '@stoplight/mosaic-code-viewer': ^1.24.4
-      react: '>=16.14'
-      react-dom: '>=16.14'
+  has-property-descriptors@1.0.2:
+    resolution: {integrity: sha512-55JNKuIW+vq4Ke1BjOTjM2YctQIvCT7GFzHwmfZPGo5wnrgkid0YQtnAleFSqumZm4az3n2BS+erby5ipJdgrg==}
 
-  '@stoplight/markdown@3.2.0':
-    resolution: {integrity: sha512-Hhnrj7xb+f4iMQQeZBKLgfst3OJyV8T4BKr8BSYnKpp070B6fE63V/lkPuKqrpvidcv6kz3INDBU/GE7K2Q0uw==}
-    engines: {node: '>=12'}
+  has-proto@1.2.0:
+    resolution: {integrity: sha512-KIL7eQPfHQRC8+XluaIw7BHUwwqL19bQn4hzNgdr+1wXoU0KKj6rufu47lhY7KbJR2C6T6+PfyN0Ea7wkSS+qQ==}
+    engines: {node: '>= 0.4'}
 
-  '@stoplight/mosaic-code-viewer@1.53.5':
-    resolution: {integrity: sha512-UrYyzagh1XgjjjjyifctyT6u8Urrqtp/rPVVE9IL/YA0xkVqMAMlyT13AuvTxohdV6SdgHt4h/oDsgRptuscnw==}
-    peerDependencies:
-      react: '>= 16.14'
+  has-symbols@1.1.0:
+    resolution: {integrity: sha512-1cDNdwJ2Jaohmb3sg4OmKaMBwuC48sYni5HUw2DvsC8LjGTLK9h+eb1X6RyuOHe4hT0ULCW68iomhjUoKUqlPQ==}
+    engines: {node: '>= 0.4'}
 
-  '@stoplight/mosaic@1.53.5':
-    resolution: {integrity: sha512-2wyzp69mVKbwxxJ9XmOh2gmt8GPmJnYt223YUihKJSUTV2Ark9sfAwaDhg6myha4cGwjHGT0u9+KD7pC9oroAg==}
-    peerDependencies:
-      react: '>= 16.14'
+  has-tostringtag@1.0.2:
+    resolution: {integrity: sha512-NqADB8VjPFLM2V0VvHUewwwsw0ZWBaIdgo+ieHtK3hasLz4qeCRjYcqfB6AQrBggRKppKF8L52/VqdVsO47Dlw==}
+    engines: {node: '>= 0.4'}
 
-  '@stoplight/ordered-object-literal@1.0.5':
-    resolution: {integrity: sha512-COTiuCU5bgMUtbIFBuyyh2/yVVzlr5Om0v5utQDgBCuQUOPgU1DwoffkTfg4UBQOvByi5foF4w4T+H9CoRe5wg==}
-    engines: {node: '>=8'}
+  hasown@2.0.4:
+    resolution: {integrity: sha512-T2UbfbBEF32wiepXIsMlTW9+dDYC6wMh/t/vYA4tuOMKqWz/n3vr1NFSxQiyP+zk2mXsoMA/i/7qV6LKut1t1A==}
+    engines: {node: '>= 0.4'}
 
-  '@stoplight/path@1.3.2':
-    resolution: {integrity: sha512-lyIc6JUlUA8Ve5ELywPC8I2Sdnh1zc1zmbYgVarhXIp9YeAB0ReeqmGEOWNtlHkbP2DAA1AL65Wfn2ncjK/jtQ==}
-    engines: {node: '>=8'}
+  hast-util-embedded@3.0.0:
+    resolution: {integrity: sha512-naH8sld4Pe2ep03qqULEtvYr7EjrLK2QHY8KJR6RJkTUjPGObe1vnx585uzem2hGra+s1q08DZZpfgDVYRbaXA==}
 
-  '@stoplight/react-error-boundary@2.0.0':
-    resolution: {integrity: sha512-r9cyaaH2h0kFe5c0aP+yJuY9CyXgfbBaMO6660M/wRQXqM49K5Ul7kexE4ei2cqYgo+Cd6ALl6RXSZFYwf2kCA==}
-    engines: {node: '>=10'}
-    peerDependencies:
-      react: '>=16.8'
-      react-dom: '>=16.8'
+  hast-util-from-dom@5.0.1:
+    resolution: {integrity: sha512-N+LqofjR2zuzTjCPzyDUdSshy4Ma6li7p/c3pA78uTwzFgENbgbUrm2ugwsOdcjI1muO+o6Dgzp9p8WHtn/39Q==}
 
-  '@stoplight/types@12.5.0':
-    resolution: {integrity: sha512-dwqYcDrGmEyUv5TWrDam5TGOxU72ufyQ7hnOIIDdmW5ezOwZaBFoR5XQ9AsH49w7wgvOqB2Bmo799pJPWnpCbg==}
-    engines: {node: '>=8'}
+  hast-util-from-html-isomorphic@2.0.0:
+    resolution: {integrity: sha512-zJfpXq44yff2hmE0XmwEOzdWin5xwH+QIhMLOScpX91e/NSGPsAzNCvLQDIEPyO2TXi+lBmU6hjLIhV8MwP2kw==}
 
-  '@stoplight/types@13.20.0':
-    resolution: {integrity: sha512-2FNTv05If7ib79VPDA/r9eUet76jewXFH2y2K5vuge6SXbRHtWBhcaRmu+6QpF4/WRNoJj5XYRSwLGXDxysBGA==}
-    engines: {node: ^12.20 || >=14.13}
+  hast-util-from-html@2.0.3:
+    resolution: {integrity: sha512-CUSRHXyKjzHov8yKsQjGOElXy/3EKpyX56ELnkHH34vDVw1N1XSQ1ZcAvTyAPtGqLTuKP/uxM+aLkSPqF/EtMw==}
 
-  '@stoplight/types@14.1.1':
-    resolution: {integrity: sha512-/kjtr+0t0tjKr+heVfviO9FrU/uGLc+QNX3fHJc19xsCNYqU7lVhaXxDmEID9BZTjG+/r9pK9xP/xU02XGg65g==}
-    engines: {node: ^12.20 || >=14.13}
+  hast-util-from-parse5@8.0.3:
+    resolution: {integrity: sha512-3kxEVkEKt0zvcZ3hCRYI8rqrgwtlIOFMWkbclACvjlDw8Li9S2hk/d51OI0nr/gIpdMHNepwgOKqZ/sy0Clpyg==}
 
-  '@stoplight/yaml-ast-parser@0.0.50':
-    resolution: {integrity: sha512-Pb6M8TDO9DtSVla9yXSTAxmo9GVEouq5P40DWXdOie69bXogZTkgvopCq+yEvTMA0F6PEvdJmbtTV3ccIp11VQ==}
+  hast-util-has-property@3.0.0:
+    resolution: {integrity: sha512-MNilsvEKLFpV604hwfhVStK0usFY/QmM5zX16bo7EjnAEGofr5YyI37kzopBlZJkHD4t887i+q/C8/tr5Q94cA==}
 
-  '@stoplight/yaml@4.3.0':
-    resolution: {integrity: sha512-JZlVFE6/dYpP9tQmV0/ADfn32L9uFarHWxfcRhReKUnljz1ZiUM5zpX+PH8h5CJs6lao3TuFqnPm9IJJCEkE2w==}
-    engines: {node: '>=10.8'}
+  hast-util-is-body-ok-link@3.0.1:
+    resolution: {integrity: sha512-0qpnzOBLztXHbHQenVB8uNuxTnm/QBFUOmdOSsEn7GnBtyY07+ENTWVFBAnXd/zEgd9/SUG3lRY7hSIBWRgGpQ==}
 
-  '@svgr/babel-plugin-add-jsx-attribute@8.0.0':
-    resolution: {integrity: sha512-b9MIk7yhdS1pMCZM8VeNfUlSKVRhsHZNMl5O9SfaX0l0t5wjdgu4IDzGB8bpnGBBOjGST3rRFVsaaEtI4W6f7g==}
-    engines: {node: '>=14'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  hast-util-is-element@3.0.0:
+    resolution: {integrity: sha512-Val9mnv2IWpLbNPqc/pUem+a7Ipj2aHacCwgNfTiK0vJKl0LF+4Ba4+v1oPHFpf3bLYmreq0/l3Gud9S5OH42g==}
 
-  '@svgr/babel-plugin-remove-jsx-attribute@8.0.0':
-    resolution: {integrity: sha512-BcCkm/STipKvbCl6b7QFrMh/vx00vIP63k2eM66MfHJzPr6O2U0jYEViXkHJWqXqQYjdeA9cuCl5KWmlwjDvbA==}
-    engines: {node: '>=14'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  hast-util-minify-whitespace@1.0.1:
+    resolution: {integrity: sha512-L96fPOVpnclQE0xzdWb/D12VT5FabA7SnZOUMtL1DbXmYiHJMXZvFkIZfiMmTCNJHUeO2K9UYNXoVyfz+QHuOw==}
 
-  '@svgr/babel-plugin-remove-jsx-empty-expression@8.0.0':
-    resolution: {integrity: sha512-5BcGCBfBxB5+XSDSWnhTThfI9jcO5f0Ai2V24gZpG+wXF14BzwxxdDb4g6trdOux0rhibGs385BeFMSmxtS3uA==}
-    engines: {node: '>=14'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  hast-util-parse-selector@4.0.0:
+    resolution: {integrity: sha512-wkQCkSYoOGCRKERFWcxMVMOcYE2K1AaNLU8DXS9arxnLOUEWbOXKXiJUNzEpqZ3JOKpnha3jkFrumEjVliDe7A==}
 
-  '@svgr/babel-plugin-replace-jsx-attribute-value@8.0.0':
-    resolution: {integrity: sha512-KVQ+PtIjb1BuYT3ht8M5KbzWBhdAjjUPdlMtpuw/VjT8coTrItWX6Qafl9+ji831JaJcu6PJNKCV0bp01lBNzQ==}
-    engines: {node: '>=14'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  hast-util-phrasing@3.0.1:
+    resolution: {integrity: sha512-6h60VfI3uBQUxHqTyMymMZnEbNl1XmEGtOxxKYL7stY2o601COo62AWAYBQR9lZbYXYSBoxag8UpPRXK+9fqSQ==}
 
-  '@svgr/babel-plugin-svg-dynamic-title@8.0.0':
-    resolution: {integrity: sha512-omNiKqwjNmOQJ2v6ge4SErBbkooV2aAWwaPFs2vUY7p7GhVkzRkJ00kILXQvRhA6miHnNpXv7MRnnSjdRjK8og==}
-    engines: {node: '>=14'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  hast-util-to-estree@3.1.0:
+    resolution: {integrity: sha512-lfX5g6hqVh9kjS/B9E2gSkvHH4SZNiQFiqWS0x9fENzEl+8W12RqdRxX6d/Cwxi30tPQs3bIO+aolQJNp1bIyw==}
 
-  '@svgr/babel-plugin-svg-em-dimensions@8.0.0':
-    resolution: {integrity: sha512-mURHYnu6Iw3UBTbhGwE/vsngtCIbHE43xCRK7kCw4t01xyGqb2Pd+WXekRRoFOBIY29ZoOhUCTEweDMdrjfi9g==}
-    engines: {node: '>=14'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  hast-util-to-html@9.0.4:
+    resolution: {integrity: sha512-wxQzXtdbhiwGAUKrnQJXlOPmHnEehzphwkK7aluUPQ+lEc1xefC8pblMgpp2w5ldBTEfveRIrADcrhGIWrlTDA==}
 
-  '@svgr/babel-plugin-transform-react-native-svg@8.1.0':
-    resolution: {integrity: sha512-Tx8T58CHo+7nwJ+EhUwx3LfdNSG9R2OKfaIXXs5soiy5HtgoAEkDay9LIimLOcG8dJQH1wPZp/cnAv6S9CrR1Q==}
-    engines: {node: '>=14'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  hast-util-to-html@9.0.5:
+    resolution: {integrity: sha512-OguPdidb+fbHQSU4Q4ZiLKnzWo8Wwsf5bZfbvu7//a9oTYoqD/fWpe96NuHkoS9h0ccGOTe0C4NGXdtS0iObOw==}
 
-  '@svgr/babel-plugin-transform-svg-component@8.0.0':
-    resolution: {integrity: sha512-DFx8xa3cZXTdb/k3kfPeaixecQLgKh5NVBMwD0AQxOzcZawK4oo1Jh9LbrcACUivsCA7TLG8eeWgrDXjTMhRmw==}
-    engines: {node: '>=12'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  hast-util-to-jsx-runtime@2.3.6:
+    resolution: {integrity: sha512-zl6s8LwNyo1P9uw+XJGvZtdFF1GdAkOg8ujOw+4Pyb76874fLps4ueHXDhXWdk6YHQ6OgUtinliG7RsYvCbbBg==}
 
-  '@svgr/babel-preset@8.1.0':
-    resolution: {integrity: sha512-7EYDbHE7MxHpv4sxvnVPngw5fuR6pw79SkcrILHJ/iMpuKySNCl5W1qcwPEpU+LgyRXOaAFgH0KhwD18wwg6ug==}
-    engines: {node: '>=14'}
-    peerDependencies:
-      '@babel/core': ^7.0.0-0
+  hast-util-to-mdast@10.1.0:
+    resolution: {integrity: sha512-DsL/SvCK9V7+vfc6SLQ+vKIyBDXTk2KLSbfBYkH4zeF/uR1yBajHRhkzuaUSGOB1WJSTieJBdHwxlC+HLKvZZw==}
 
-  '@svgr/core@8.1.0':
-    resolution: {integrity: sha512-8QqtOQT5ACVlmsvKOJNEaWmRPmcojMOzCz4Hs2BGG/toAp/K38LcsMRyLp349glq5AzJbCEeimEoxaX6v/fLrA==}
-    engines: {node: '>=14'}
+  hast-util-to-string@3.0.1:
+    resolution: {integrity: sha512-XelQVTDWvqcl3axRfI0xSeoVKzyIFPwsAGSLIsKdJKQMXDYJS4WYrBNF/8J7RdhIcFI2BOHgAifggsvsxp/3+A==}
 
-  '@svgr/hast-util-to-babel-ast@8.0.0':
-    resolution: {integrity: sha512-EbDKwO9GpfWP4jN9sGdYwPBU0kdomaPIL2Eu4YwmgP+sJeXT+L7bMwJUBnhzfH8Q2qMBqZ4fJwpCyYsAN3mt2Q==}
-    engines: {node: '>=14'}
+  hast-util-to-text@4.0.2:
+    resolution: {integrity: sha512-KK6y/BN8lbaq654j7JgBydev7wuNMcID54lkRav1P0CaE1e47P72AWWPiGKXTJU271ooYzcvTAn/Zt0REnvc7A==}
 
-  '@svgr/plugin-jsx@8.1.0':
-    resolution: {integrity: sha512-0xiIyBsLlr8quN+WyuxooNW9RJ0Dpr8uOnH/xrCVO8GLUcwHISwj1AG0k+LFzteTkAA0GbX0kj9q6Dk70PTiPA==}
-    engines: {node: '>=14'}
-    peerDependencies:
-      '@svgr/core': '*'
+  hast-util-whitespace@3.0.0:
+    resolution: {integrity: sha512-88JUN06ipLwsnv+dVn+OIYOvAuvBMy/Qoi6O7mQHxdPXpjy+Cd6xRkWwux7DKO+4sYILtLBRIKgsdpS2gQc7qw==}
 
-  '@svgr/plugin-svgo@8.1.0':
-    resolution: {integrity: sha512-Ywtl837OGO9pTLIN/onoWLmDQ4zFUycI1g76vuKGEz6evR/ZTJlJuz3G/fIkb6OVBJ2g0o6CGJzaEjfmEo3AHA==}
-    engines: {node: '>=14'}
-    peerDependencies:
-      '@svgr/core': '*'
+  hastscript@9.0.1:
+    resolution: {integrity: sha512-g7df9rMFX/SPi34tyGCyUBREQoKkapwdY/T04Qn9TDWfHhAYt4/I0gMVirzK5wEzeUqIjEB+LXC/ypb7Aqno5w==}
 
-  '@svgr/webpack@8.1.0':
-    resolution: {integrity: sha512-LnhVjMWyMQV9ZmeEy26maJk+8HTIbd59cH4F2MJ439k9DqejRisfFNGAPvRYlKETuh9LrImlS8aKsBgKjMA8WA==}
-    engines: {node: '>=14'}
+  hex-rgb@4.3.0:
+    resolution: {integrity: sha512-Ox1pJVrDCyGHMG9CFg1tmrRUMRPRsAWYc/PinY0XzJU4K7y7vjNoLKIQ7BR5UJMCxNN8EM1MNDmHWA/B3aZUuw==}
+    engines: {node: '>=6'}
 
-  '@swc/core-darwin-arm64@1.15.41':
-    resolution: {integrity: sha512-kREh6J5paQFvP3i7f/4FbqRNOJREutVFVOkder4GVyCBQ39YmER55cW/y1NNjwrchzFqgYswFn0mMDCqbqKzrw==}
-    engines: {node: '>=10'}
-    cpu: [arm64]
-    os: [darwin]
+  html-void-elements@3.0.0:
+    resolution: {integrity: sha512-bEqo66MRXsUGxWHV5IP0PUiAWwoEjba4VCzg0LjFJBpchPaTfyfCKTG6bc5F8ucKec3q5y6qOdGyYTSBEvhCrg==}
 
-  '@swc/core-darwin-x64@1.15.41':
-    resolution: {integrity: sha512-N8B56ESFazZAWZyIkecADSPCwlLEinW7QLMEeotCpv4J7VXwfH+OLkmRL8o96UZ+1355fwHxDTS6/wK7yucvkA==}
-    engines: {node: '>=10'}
-    cpu: [x64]
-    os: [darwin]
+  http-cache-semantics@4.3.0:
+    resolution: {integrity: sha512-M5t5LlJpS1UHMjvwRQVdFHvPISGeLAxNcrWuJkeGh0KxsqCHZ1O3NXZU/8x7cD0BDcGW8kapxMKTvwlqrNkHkA==}
 
-  '@swc/core-linux-arm-gnueabihf@1.15.41':
-    resolution: {integrity: sha512-6XrId2fyle0mS5xxON8rU84mPd2Cq1kDJRj+4BnQKTd7u+2kSA6Ww+JkOP0iTNqOqt9OXhPOEAjBHAuonWcdCg==}
-    engines: {node: '>=10'}
-    cpu: [arm]
-    os: [linux]
+  http-errors@2.0.1:
+    resolution: {integrity: sha512-4FbRdAX+bSdmo4AUFuS0WNiPz8NgFt+r8ThgNWmlrjQjt1Q7ZR9+zTlce2859x4KSXrwIsaeTqDoKQmtP8pLmQ==}
+    engines: {node: '>= 0.8'}
 
-  '@swc/core-linux-arm64-gnu@1.15.41':
-    resolution: {integrity: sha512-ynLIarxlkVnqHn1D0fKOVht6mNU5ks6lrH+MY3kkS+XFaGGgDxFZVjWKJlkYTKm3RCvBTfA8Ng5fLufXheMRKQ==}
-    engines: {node: '>=10'}
-    cpu: [arm64]
-    os: [linux]
-    libc: [glibc]
+  http2-wrapper@2.2.1:
+    resolution: {integrity: sha512-V5nVw1PAOgfI3Lmeaj2Exmeg7fenjhRUgz1lPSezy1CuhPYbgQtbQj4jZfEAEMlaL+vupsvhjqCyjzob0yxsmQ==}
+    engines: {node: '>=10.19.0'}
 
-  '@swc/core-linux-arm64-musl@1.15.41':
-    resolution: {integrity: sha512-dXu/5vd4gh8symyhRF+4G7gOPkjmb4pONhh7sl+6GSiW0LOKZlfu5kXmyFbTz9smOT7jgr002qY9b1nujjXt2A==}
-    engines: {node: '>=10'}
-    cpu: [arm64]
-    os: [linux]
-    libc: [musl]
+  https-proxy-agent@5.0.1:
+    resolution: {integrity: sha512-dFcAjpTQFgoLMzC2VwU+C/CbS7uRL0lWmxDITmqm7C+7F0Odmj6s9l6alZc6AELXhrnggM2CeWSXHGOdX2YtwA==}
+    engines: {node: '>= 6'}
 
-  '@swc/core-linux-ppc64-gnu@1.15.41':
-    resolution: {integrity: sha512-XGO6zVPXoPE0gf/XnI4jBbafNT13AYgoh6ns0JCSdOetI/kqVf0vhpz7NuNgAzZrMVCsmieqjPoTwViDgh4mOQ==}
-    engines: {node: '>=10'}
-    cpu: [ppc64]
-    os: [linux]
-    libc: [glibc]
+  husky@9.1.7:
+    resolution: {integrity: sha512-5gs5ytaNjBrh5Ow3zrvdUUY+0VxIuWVL4i9irt6friV+BqdCfmV11CQTWMiBYWHbXhco+J1kHfTOUkePhCDvMA==}
+    engines: {node: '>=18'}
+    hasBin: true
 
-  '@swc/core-linux-s390x-gnu@1.15.41':
-    resolution: {integrity: sha512-0WUglRwyZtW+iMi7J3iFdrCxreZZIKf4egTwEQfIYRsqFax69A0OrFj+NIoFSE03xBT/IFRrg+S8K6f9Ky+4hA==}
-    engines: {node: '>=10'}
-    cpu: [s390x]
-    os: [linux]
-    libc: [glibc]
+  ico-endec@0.1.6:
+    resolution: {integrity: sha512-ZdLU38ZoED3g1j3iEyzcQj+wAkY2xfWNkymszfJPoxucIUhK7NayQ+/C4Kv0nDFMIsbtbEHldv3V8PU494/ueQ==}
 
-  '@swc/core-linux-x64-gnu@1.15.41':
-    resolution: {integrity: sha512-VxkuQK59c0tHm6uJZCUrS3cyA2JhGGfdU6e41SZz0x/JS+4Sm7C1mIc97In14vkZJopEt7yXA2TouCqZDSygEA==}
-    engines: {node: '>=10'}
-    cpu: [x64]
-    os: [linux]
-    libc: [glibc]
+  iconv-lite@0.4.24:
+    resolution: {integrity: sha512-v3MXnZAcvnywkTUEZomIActle7RXXeedOR31wwl7VlyoXO4Qi9arvSenNQWne1TcRwhCL1HwLI21bEqdpj8/rA==}
+    engines: {node: '>=0.10.0'}
 
-  '@swc/core-linux-x64-musl@1.15.41':
-    resolution: {integrity: sha512-/0qXIu1ZxggLuovLb22vFfKHq2AA4n6Whw5UwmVCHk4pkw7KWnPIQpMCEqUMPsNkFJig7PPp/TSYFu8ZEb2rtQ==}
-    engines: {node: '>=10'}
-    cpu: [x64]
-    os: [linux]
-    libc: [musl]
+  iconv-lite@0.7.3:
+    resolution: {integrity: sha512-IKXpvIzjnC9XTAUbVBcMfGS0EPaIXtW6v+zr+RRp+hqULEpo0owZax6wyRwPOJbWbzjYspQwusTsfVr0ifh4uQ==}
+    engines: {node: '>=0.10.0'}
 
-  '@swc/core-win32-arm64-msvc@1.15.41':
-    resolution: {integrity: sha512-Y481sMNZM6rECh9VO4+y26N1lWEDAyxnBZskUf37fl90uHE946VHfmiVQWT0uMFOhyJJFovGTRuF4W82dwewUg==}
-    engines: {node: '>=10'}
-    cpu: [arm64]
-    os: [win32]
+  ieee754@1.2.1:
+    resolution: {integrity: sha512-dcyqhDvX1C46lXZcVqCpK+FtMRQVdIMN6/Df5js2zouUsqG7I6sFxitIC+7KYK29KdXOLHdu9zL4sFnoVQnqaA==}
 
-  '@swc/core-win32-ia32-msvc@1.15.41':
-    resolution: {integrity: sha512-BAchBD5qeUzy3hiPSLJtaaoSm4blCLyYffOF1bGE4ETcV+OisqjUAwDQMJj++4bTpvMCDzwC+Bj3PmQyBCtscw==}
-    engines: {node: '>=10'}
-    cpu: [ia32]
-    os: [win32]
+  ignore@7.0.5:
+    resolution: {integrity: sha512-Hs59xBNfUIunMFgWAbGX5cq6893IbWg4KnrjbYwX3tx0ztorVgTDA6B2sxf8ejHJ4wz8BqGUMYlnzNBer5NvGg==}
+    engines: {node: '>= 4'}
 
-  '@swc/core-win32-x64-msvc@1.15.41':
-    resolution: {integrity: sha512-WOkA+fJ/ViVBQDsSV9JC52NACTe5PhlurA6viASDZGb7HR3KS01ZG7RZ+Bg6SVQFIoq3gSbTsskQVe6EbHFAYw==}
-    engines: {node: '>=10'}
-    cpu: [x64]
-    os: [win32]
+  image-size@2.0.2:
+    resolution: {integrity: sha512-IRqXKlaXwgSMAMtpNzZa1ZAe8m+Sa1770Dhk8VkSsP9LS+iHD62Zd8FQKs8fbPiagBE7BzoFX23cxFnwshpV6w==}
+    engines: {node: '>=16.x'}
+    hasBin: true
 
-  '@swc/core@1.15.41':
-    resolution: {integrity: sha512-03nQq/082QRJJiOvp3FGbgxTGyyxMxohPTjhk/W9bD2J0tk4ukITI7goOhOO2WbaHn/lsPmo/zf8+DIXhwpgYQ==}
-    engines: {node: '>=10'}
-    peerDependencies:
-      '@swc/helpers': '>=0.5.17'
-    peerDependenciesMeta:
-      '@swc/helpers':
-        optional: true
+  immer@9.0.21:
+    resolution: {integrity: sha512-bc4NBHqOqSfRW7POMkHd51LvClaeMXpm8dx0e8oE2GORbq5aRK7Bxl4FyzVLdGtLmvLKL7BTDBG5ACQm4HWjTA==}
 
-  '@swc/counter@0.1.3':
-    resolution: {integrity: sha512-e2BR4lsJkkRlKZ/qCHPw9ZaSxc0MVUd7gtbtaB7aMvHeJVYe8sOB8DBZkP2DtISHGSku9sCK6T6cnY0CtXrOCQ==}
+  indent-string@5.0.0:
+    resolution: {integrity: sha512-m6FAo/spmsW2Ab2fU35JTYwtOKa2yAwXSwgjSv1TJzh4Mh7mC3lzAOVLBprb72XsTrgkEIsl7YrFNAiDiRhIGg==}
+    engines: {node: '>=12'}
 
-  '@swc/helpers@0.5.23':
-    resolution: {integrity: sha512-5lSsMOTXURePglDfvuAQUqkGek9Hg2kksOYay2m0+XR++b2NWYL/4sWyuvVBIs8oKnJaxkdi9whaL/sqN13afw==}
+  inflight@1.0.6:
+    resolution: {integrity: sha512-k92I/b08q4wvFscXCLvqfsHCrjrF7yiXsQuIVvVE7N82W3+aqpzuUdBbfhWcy/FZR3/4IgflMgKLOsvPDrGCJA==}
+    deprecated: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
 
-  '@swc/html-darwin-arm64@1.15.40':
-    resolution: {integrity: sha512-A9oxSh60pMEsX/4VBpn3e6s8DfGWsHzAeG+Vd9mXgkTqt/ouX12owP6RyqfqK8v0WuEsBKkGY0+MbwLvlOG8NQ==}
-    engines: {node: '>=10'}
-    cpu: [arm64]
-    os: [darwin]
+  inherits@2.0.4:
+    resolution: {integrity: sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ==}
 
-  '@swc/html-darwin-x64@1.15.40':
-    resolution: {integrity: sha512-GZ5KxJ/1pqnpOAjaa9hnkSk3M1LHjc5ci5GCt5/llAgDKFLDHzydIflHXTOIaS4nRCtfVMmD0joKX+ZWruSkJw==}
-    engines: {node: '>=10'}
-    cpu: [x64]
-    os: [darwin]
+  ini@1.3.8:
+    resolution: {integrity: sha512-JV/yugV2uzW5iMRSiZAyDtQd+nxtUnjeLt0acNdw98kKLrvuRVyB80tsREOE7yvGVgalhZ6RNXCmEHkUKBKxew==}
 
-  '@swc/html-linux-arm-gnueabihf@1.15.40':
-    resolution: {integrity: sha512-Bbwtl0G6vYcWlDQmjeuyFx8YIvqi1StlQWjRNB1ZtvrRNL3JadFARhijBONiUIyTK9MgUbWtTV3QU69qzjNENQ==}
-    engines: {node: '>=10'}
-    cpu: [arm]
-    os: [linux]
+  ink-spinner@5.0.0:
+    resolution: {integrity: sha512-EYEasbEjkqLGyPOUc8hBJZNuC5GvXGMLu0w5gdTNskPc7Izc5vO3tdQEYnzvshucyGCBXc86ig0ujXPMWaQCdA==}
+    engines: {node: '>=14.16'}
+    peerDependencies:
+      ink: '>=4.0.0'
+      react: '>=18.0.0'
 
-  '@swc/html-linux-arm64-gnu@1.15.40':
-    resolution: {integrity: sha512-buu4fGyCIhkwmCetI4CfWOPn7cphJHwQ9ksK685hlL0R0PUaDCNdIxo+JAz0mK2JgPhoGqnKsVEmV6gLIL5GBw==}
-    engines: {node: '>=10'}
-    cpu: [arm64]
-    os: [linux]
-    libc: [glibc]
+  ink@6.3.0:
+    resolution: {integrity: sha512-2CbJAa7XeziZYe6pDS5RVLirRY28iSGMQuEV8jRU5NQsONQNfcR/BZHHc9vkMg2lGYTHTM2pskxC1YmY28p6bQ==}
+    engines: {node: '>=20'}
+    peerDependencies:
+      '@types/react': '>=19.0.0'
+      react: '>=19.0.0'
+      react-devtools-core: ^4.19.1
+    peerDependenciesMeta:
+      '@types/react':
+        optional: true
+      react-devtools-core:
+        optional: true
 
-  '@swc/html-linux-arm64-musl@1.15.40':
-    resolution: {integrity: sha512-BwWtpAGEHIP1QwKExWqBIjGpAHMahjT26ORZv3+TbwW4IuEl2QP5FrcYc30O8abCG5J1lWRl1vXKYDpzbIDz1A==}
-    engines: {node: '>=10'}
-    cpu: [arm64]
-    os: [linux]
-    libc: [musl]
+  inline-style-parser@0.1.1:
+    resolution: {integrity: sha512-7NXolsK4CAS5+xvdj5OMMbI962hU/wvwoxk+LWR9Ek9bVtyuuYScDN6eS0rUm6TxApFpw7CX1o4uJzcd4AyD3Q==}
 
-  '@swc/html-linux-ppc64-gnu@1.15.40':
-    resolution: {integrity: sha512-wLtHgwmZu5K7PvuTROklgWJO6D+KwywpYR1geI8dSWX/AYnx/KCGVK9ncPzWVfnLXWhXbkgua3Ujdrfoxf+qSw==}
-    engines: {node: '>=10'}
-    cpu: [ppc64]
-    os: [linux]
-    libc: [glibc]
+  inline-style-parser@0.2.7:
+    resolution: {integrity: sha512-Nb2ctOyNR8DqQoR0OwRG95uNWIC0C1lCgf5Naz5H6Ji72KZ8OcFZLz2P5sNgwlyoJ8Yif11oMuYs5pBQa86csA==}
 
-  '@swc/html-linux-s390x-gnu@1.15.40':
-    resolution: {integrity: sha512-WbWzQBCmvECZG6ep9D5SMMZTFCbFmRSCc7lPD3YhhaK16BNqr1AybvybZYOgxX9Ot5tq7gTWCgjFZXLDOn6Y/g==}
-    engines: {node: '>=10'}
-    cpu: [s390x]
-    os: [linux]
-    libc: [glibc]
+  inquirer@12.3.0:
+    resolution: {integrity: sha512-3NixUXq+hM8ezj2wc7wC37b32/rHq1MwNZDYdvx+d6jokOD+r+i8Q4Pkylh9tISYP114A128LCX8RKhopC5RfQ==}
+    engines: {node: '>=18'}
+    peerDependencies:
+      '@types/node': '>=18'
 
-  '@swc/html-linux-x64-gnu@1.15.40':
-    resolution: {integrity: sha512-i+/JqL5j9mTGMcVshWLMzciqyE3Np+gN5+UqMyO1D5zSmniJD5MHRlGXCtLaWx/MIKX0Q4Xkre33o56fmxp+uA==}
-    engines: {node: '>=10'}
-    cpu: [x64]
-    os: [linux]
-    libc: [glibc]
+  internal-slot@1.1.0:
+    resolution: {integrity: sha512-4gd7VpWNQNB4UKKCFFVcp1AVv+FMOgs9NKzjHKusc8jTMhd5eL1NqQqOpE0KzMds804/yHlglp3uxgluOqAPLw==}
+    engines: {node: '>= 0.4'}
 
-  '@swc/html-linux-x64-musl@1.15.40':
-    resolution: {integrity: sha512-mroZnb5omFc4iE01UsJgta+Nm0sIFWpGfTPk+BHfH165MZAM4wNndeczX5RpGZbQSF1nNpCoNgqJyT7l3hITMg==}
-    engines: {node: '>=10'}
-    cpu: [x64]
-    os: [linux]
-    libc: [musl]
+  ip-regex@4.3.0:
+    resolution: {integrity: sha512-B9ZWJxHHOHUhUjCPrMpLD4xEq35bUTClHM1S6CBU5ixQnkZmwipwgc96vAd7AAGM9TGHvJR+Uss+/Ak6UphK+Q==}
+    engines: {node: '>=8'}
 
-  '@swc/html-win32-arm64-msvc@1.15.40':
-    resolution: {integrity: sha512-qg1LXRrsY9FXy0S7vouSF0kkn1vdkTD//FW66iuezH7HMm5/DJGwEj7oc1zTKPWU0HnwOINOUbl6rUHrRuXHAQ==}
-    engines: {node: '>=10'}
-    cpu: [arm64]
-    os: [win32]
+  ipaddr.js@1.9.1:
+    resolution: {integrity: sha512-0KI/607xoxSToH7GjN1FfSbLoU0+btTicjsQSWQlh/hZykN8KpmMf7uYwPW3R+akZ6R/w18ZlXSHBYXiYUPO3g==}
+    engines: {node: '>= 0.10'}
 
-  '@swc/html-win32-ia32-msvc@1.15.40':
-    resolution: {integrity: sha512-5NwMmgt9A70LQzcYOl4OiIJk5AhsGP69fNRfkmXXop+iIcAGUmYy+d6F2/Gc0u05j9G0R04NPWcHBQrHQhr0Gw==}
-    engines: {node: '>=10'}
-    cpu: [ia32]
-    os: [win32]
+  iregexp-check@0.1.2:
+    resolution: {integrity: sha512-RCcV2SFO5JKh+DdmWiY7yVyiZzzk6XZiHEJvTKbzVs8Z0u404gnoSqDtFqg6C5qJBEG4QseWBQz9zhI68zskEQ==}
 
-  '@swc/html-win32-x64-msvc@1.15.40':
-    resolution: {integrity: sha512-WUNZqCZ+8WY1pr8t3X3fq4gI5+FL/tCCzlrJ2lLn0s+TyA2SLm/RPfXxQIr94EnjJWcIV21G//6/uXeBN8cPzw==}
-    engines: {node: '>=10'}
-    cpu: [x64]
-    os: [win32]
+  is-alphabetical@2.0.1:
+    resolution: {integrity: sha512-FWyyY60MeTNyeSRpkM2Iry0G9hpr7/9kD40mD/cGQEuilcZYS4okz8SN2Q6rLCJ8gbCt6fN+rC+6tMGS99LaxQ==}
 
-  '@swc/html@1.15.40':
-    resolution: {integrity: sha512-YVWNrh3wZWH2oXz7uL+s1WZbFIsnAp9cCl/b+C7ufDJqhsOvbr0un9IOYZ/CxRIRdnHGfhVD199n8baD/kRQew==}
-    engines: {node: '>=14'}
+  is-alphanumerical@2.0.1:
+    resolution: {integrity: sha512-hmbYhX/9MUMF5uh7tOXyK/n0ZvWpad5caBA17GsC6vyuCqaWliRG5K1qS9inmUhEMaOBIW7/whAnSwveW/LtZw==}
 
-  '@swc/types@0.1.26':
-    resolution: {integrity: sha512-lyMwd7WGgG79RS7EERZV3T8wMdmPq3xwyg+1nmAM64kIhx5yl+juO2PYIHb7vTiPgPCj8LYjsNV2T5wiQHUEaw==}
+  is-array-buffer@3.0.5:
+    resolution: {integrity: sha512-DDfANUiiG2wC1qawP66qlTugJeL5HyzMpfr8lLK+jMQirGzNod0B12cFB/9q838Ru27sBwfw78/rdoU7RERz6A==}
+    engines: {node: '>= 0.4'}
 
-  '@szmarczak/http-timer@5.0.1':
-    resolution: {integrity: sha512-+PmQX0PiAYPMeVYe237LJAYvOMYW1j2rH5YROyS3b4CTVJum34HfRvKvAzozHAQG0TnHNdUfY9nCeUyRAs//cw==}
-    engines: {node: '>=14.16'}
+  is-arrayish@0.3.4:
+    resolution: {integrity: sha512-m6UrgzFVUYawGBh1dUsWR5M2Clqic9RVXC/9f8ceNlv2IcO9j9J/z8UoCLPqtsPBFNzEpfR3xftohbfqDx8EQA==}
 
-  '@tybys/wasm-util@0.10.2':
-    resolution: {integrity: sha512-RoBvJ2X0wuKlWFIjrwffGw1IqZHKQqzIchKaadZZfnNpsAYp2mM0h36JtPCjNDAHGgYez/15uMBpfGwchhiMgg==}
+  is-async-function@2.1.1:
+    resolution: {integrity: sha512-9dgM/cZBnNvjzaMYHVoxxfPj2QXt22Ev7SuuPrs+xav0ukGB0S6d4ydZdEiM48kLx5kDV+QBPrpVnFyefL8kkQ==}
+    engines: {node: '>= 0.4'}
 
-  '@types/body-parser@1.19.6':
-    resolution: {integrity: sha512-HLFeCYgz89uk22N5Qg3dvGvsv46B8GLvKKo1zKG4NybA8U2DiEO3w9lqGg29t/tfLRJpJ6iQxnVw4OnB7MoM9g==}
+  is-bigint@1.1.0:
+    resolution: {integrity: sha512-n4ZT37wG78iz03xPRKJrHTdZbe3IicyucEtdRsV5yglwc3GyUfbAfpSeD0FJ41NbUNSt5wbhqfp1fS+BgnvDFQ==}
+    engines: {node: '>= 0.4'}
 
-  '@types/bonjour@3.5.13':
-    resolution: {integrity: sha512-z9fJ5Im06zvUL548KvYNecEVlA7cVDkGUi6kZusb04mpyEFKCIZJvloCcmpmLaIahDpOQGHaHmG6imtPMmPXGQ==}
+  is-binary-path@2.1.0:
+    resolution: {integrity: sha512-ZMERYes6pDydyuGidse7OsHxtbI7WVeUEozgR/g7rd0xUimYNlvZRE/K2MgZTjWy725IfelLeVcEM97mmtRGXw==}
+    engines: {node: '>=8'}
 
-  '@types/connect-history-api-fallback@1.5.4':
-    resolution: {integrity: sha512-n6Cr2xS1h4uAulPRdlw6Jl6s1oG8KrVilPN2yUITEs+K48EzMJJ3W1xy8K5eWuFvjp3R74AOIGSmp2UfBJ8HFw==}
+  is-boolean-object@1.2.2:
+    resolution: {integrity: sha512-wa56o2/ElJMYqjCjGkXri7it5FbebW5usLw/nPmCMs5DeZ7eziSYZhSmPRn0txqeW4LnAmQQU7FgqLpsEFKM4A==}
+    engines: {node: '>= 0.4'}
 
-  '@types/connect@3.4.38':
-    resolution: {integrity: sha512-K6uROf1LD88uDQqJCktA4yzL1YYAK6NgfsI0v/mTgyPKWsX1CnJ0XPSDhViejru1GcRkLWb8RlzFYJRqGUbaug==}
+  is-callable@1.2.7:
+    resolution: {integrity: sha512-1BC0BVFhS/p0qtw6enp8e+8OD0UrK0oFLztSjNzhcKA3WDuJxxAPXzPuPtKkjEY9UUoEWlX/8fgKeu2S8i9JTA==}
+    engines: {node: '>= 0.4'}
 
-  '@types/d3-array@3.2.2':
-    resolution: {integrity: sha512-hOLWVbm7uRza0BYXpIIW5pxfrKe0W+D5lrFiAEYR+pb6w3N2SwSMaJbXdUfSEv+dT4MfHBLtn5js0LAWaO6otw==}
+  is-core-module@2.17.0:
+    resolution: {integrity: sha512-J/vG0zBCbIKOQFfufSwyXdMrsohyJIUNkrnmo6WZGzoM7tr/lsbfW5b2BvisL6zsyMzK9UxV9L6c7AoFbyXHOA==}
+    engines: {node: '>= 0.4'}
 
-  '@types/d3-axis@3.0.6':
-    resolution: {integrity: sha512-pYeijfZuBd87T0hGn0FO1vQ/cgLk6E1ALJjfkC0oJ8cbwkZl3TpgS8bVBLZN+2jjGgg38epgxb2zmoGtSfvgMw==}
+  is-data-view@1.0.2:
+    resolution: {integrity: sha512-RKtWF8pGmS87i2D6gqQu/l7EYRlVdfzemCJN/P3UOs//x1QE7mfhvzHIApBTRf7axvT6DMGwSwBXYCT0nfB9xw==}
+    engines: {node: '>= 0.4'}
 
-  '@types/d3-brush@3.0.6':
-    resolution: {integrity: sha512-nH60IZNNxEcrh6L1ZSMNA28rj27ut/2ZmI3r96Zd+1jrZD++zD3LsMIjWlvg4AYrHn/Pqz4CF3veCxGjtbqt7A==}
+  is-date-object@1.1.0:
+    resolution: {integrity: sha512-PwwhEakHVKTdRNVOw+/Gyh0+MzlCl4R6qKvkhuvLtPMggI1WAHt9sOwZxQLSGpUaDnrdyDsomoRgNnCfKNSXXg==}
+    engines: {node: '>= 0.4'}
 
-  '@types/d3-chord@3.0.6':
-    resolution: {integrity: sha512-LFYWWd8nwfwEmTZG9PfQxd17HbNPksHBiJHaKuY1XeqscXacsS2tyoo6OdRsjf+NQYeB6XrNL3a25E3gH69lcg==}
+  is-decimal@2.0.1:
+    resolution: {integrity: sha512-AAB9hiomQs5DXWcRB1rqsxGUstbRroFOPPVAomNk/3XHR5JyEZChOyTWe2oayKnsSsr/kcGqF+z6yuH6HHpN0A==}
 
-  '@types/d3-color@3.1.3':
-    resolution: {integrity: sha512-iO90scth9WAbmgv7ogoq57O9YpKmFBbmoEoCHDB2xMBY0+/KVrqAaCDyCE16dUspeOvIxFFRI+0sEtqDqy2b4A==}
+  is-docker@2.2.1:
+    resolution: {integrity: sha512-F+i2BKsFrH66iaUFc0woD8sLy8getkwTwtOBjvs56Cx4CgJDeKQeqfz8wAYiSb8JOprWhHH5p77PbmYCvvUuXQ==}
+    engines: {node: '>=8'}
+    hasBin: true
 
-  '@types/d3-contour@3.0.6':
-    resolution: {integrity: sha512-BjzLgXGnCWjUSYGfH1cpdo41/hgdWETu4YxpezoztawmqsvCeep+8QGfiY6YbDvfgHz/DkjeIkkZVJavB4a3rg==}
+  is-document.all@1.0.0:
+    resolution: {integrity: sha512-+XSoyS05OdBbhFuELhgTCpFNHkpBOJqtsZfUFFpe5QTw+9Sjbh8zitxhQkYAo6wV7e1Vb8cAPvpCk9jGam/82g==}
+    engines: {node: '>= 0.4'}
 
-  '@types/d3-delaunay@6.0.4':
-    resolution: {integrity: sha512-ZMaSKu4THYCU6sV64Lhg6qjf1orxBthaC161plr5KuPHo3CNm8DTHiLw/5Eq2b6TsNP0W0iJrUOFscY6Q450Hw==}
+  is-extglob@2.1.1:
+    resolution: {integrity: sha512-SbKbANkN603Vi4jEZv49LeVJMn4yGwsbzZworEoyEiutsN3nJYdbO36zfhGJ6QEDpOZIFkDtnq5JRxmvl3jsoQ==}
+    engines: {node: '>=0.10.0'}
 
-  '@types/d3-dispatch@3.0.7':
-    resolution: {integrity: sha512-5o9OIAdKkhN1QItV2oqaE5KMIiXAvDWBDPrD85e58Qlz1c1kI/J0NcqbEG88CoTwJrYe7ntUCVfeUl2UJKbWgA==}
+  is-finalizationregistry@1.1.1:
+    resolution: {integrity: sha512-1pC6N8qWJbWoPtEjgcL2xyhQOP491EQjeUo3qTKcmV8YSDDJrOepfG8pcC7h/QgnQHYSv0mJ3Z/ZWxmatVrysg==}
+    engines: {node: '>= 0.4'}
 
-  '@types/d3-drag@3.0.7':
-    resolution: {integrity: sha512-HE3jVKlzU9AaMazNufooRJ5ZpWmLIoc90A37WU2JMmeq28w1FQqCZswHZ3xR+SuxYftzHq6WU6KJHvqxKzTxxQ==}
+  is-fullwidth-code-point@3.0.0:
+    resolution: {integrity: sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg==}
+    engines: {node: '>=8'}
 
-  '@types/d3-dsv@3.0.7':
-    resolution: {integrity: sha512-n6QBF9/+XASqcKK6waudgL0pf/S5XHPPI8APyMLLUHd8NqouBGLsU8MgtO7NINGtPBtk9Kko/W4ea0oAspwh9g==}
+  is-fullwidth-code-point@4.0.0:
+    resolution: {integrity: sha512-O4L094N2/dZ7xqVdrXhh9r1KODPJpFms8B5sGdJLPy664AgvXsreZUyCQQNItZRDlYug4xStLjNp/sz3HvBowQ==}
+    engines: {node: '>=12'}
 
-  '@types/d3-ease@3.0.2':
-    resolution: {integrity: sha512-NcV1JjO5oDzoK26oMzbILE6HW7uVXOHLQvHshBUW4UMdZGfiY6v5BeQwh9a9tCzv+CeefZQHJt5SRgK154RtiA==}
+  is-fullwidth-code-point@5.1.0:
+    resolution: {integrity: sha512-5XHYaSyiqADb4RnZ1Bdad6cPp8Toise4TzEjcOYDHZkTCbKgiUl7WTUCpNWHuxmDt91wnsZBc9xinNzopv3JMQ==}
+    engines: {node: '>=18'}
 
-  '@types/d3-fetch@3.0.7':
-    resolution: {integrity: sha512-fTAfNmxSb9SOWNB9IoG5c8Hg6R+AzUHDRlsXsDZsNp6sxAEOP0tkP3gKkNSO/qmHPoBFTxNrjDprVHDQDvo5aA==}
+  is-generator-function@1.1.2:
+    resolution: {integrity: sha512-upqt1SkGkODW9tsGNG5mtXTXtECizwtS2kA161M+gJPc1xdb/Ax629af6YrTwcOeQHbewrPNlE5Dx7kzvXTizA==}
+    engines: {node: '>= 0.4'}
 
-  '@types/d3-force@3.0.10':
-    resolution: {integrity: sha512-ZYeSaCF3p73RdOKcjj+swRlZfnYpK1EbaDiYICEEp5Q6sUiqFaFQ9qgoshp5CzIyyb/yD09kD9o2zEltCexlgw==}
+  is-glob@4.0.3:
+    resolution: {integrity: sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg==}
+    engines: {node: '>=0.10.0'}
 
-  '@types/d3-format@3.0.4':
-    resolution: {integrity: sha512-fALi2aI6shfg7vM5KiR1wNJnZ7r6UuggVqtDA+xiEdPZQwy/trcQaHnwShLuLdta2rTymCNpxYTiMZX/e09F4g==}
+  is-hexadecimal@2.0.1:
+    resolution: {integrity: sha512-DgZQp241c8oO6cA1SbTEWiXeoxV42vlcJxgH+B3hi1AiqqKruZR3ZGF8In3fj4+/y/7rHvlOZLZtgJ/4ttYGZg==}
 
-  '@types/d3-geo@3.1.0':
-    resolution: {integrity: sha512-856sckF0oP/diXtS4jNsiQw/UuK5fQG8l/a9VVLeSouf1/PPbBE1i1W852zVwKwYCBkFJJB7nCFTbk6UMEXBOQ==}
+  is-in-ci@2.0.0:
+    resolution: {integrity: sha512-cFeerHriAnhrQSbpAxL37W1wcJKUUX07HyLWZCW1URJT/ra3GyUTzBgUnh24TMVfNTV2Hij2HLxkPHFZfOZy5w==}
+    engines: {node: '>=20'}
+    hasBin: true
 
-  '@types/d3-hierarchy@3.1.7':
-    resolution: {integrity: sha512-tJFtNoYBtRtkNysX1Xq4sxtjK8YgoWUNpIiUee0/jHGRwqvzYxkq0hGVbbOGSz+JgFxxRu4K8nb3YpG3CMARtg==}
+  is-ip@3.1.0:
+    resolution: {integrity: sha512-35vd5necO7IitFPjd/YBeqwWnyDWbuLH9ZXQdMfDA8TEo7pv5X8yfrvVO3xbJbLUlERCMvf6X0hTUamQxCYJ9Q==}
+    engines: {node: '>=8'}
 
-  '@types/d3-interpolate@3.0.4':
-    resolution: {integrity: sha512-mgLPETlrpVV1YRJIglr4Ez47g7Yxjl1lj7YKsiMCb27VJH9W8NVM6Bb9d8kkpG/uAQS5AmbA48q2IAolKKo1MA==}
+  is-map@2.0.3:
+    resolution: {integrity: sha512-1Qed0/Hr2m+YqxnM09CjA2d/i6YZNfF6R2oRAOj36eUdS6qIV/huPJNSEpKbupewFs+ZsJlxsjjPbc0/afW6Lw==}
+    engines: {node: '>= 0.4'}
 
-  '@types/d3-path@3.1.1':
-    resolution: {integrity: sha512-VMZBYyQvbGmWyWVea0EHs/BwLgxc+MKi1zLDCONksozI4YJMcTt8ZEuIR4Sb1MMTE8MMW49v0IwI5+b7RmfWlg==}
+  is-negative-zero@2.0.3:
+    resolution: {integrity: sha512-5KoIu2Ngpyek75jXodFvnafB6DJgr3u8uuK0LEZJjrU19DrMD3EVERaR8sjz8CCGgpZvxPl9SuE1GMVPFHx1mw==}
+    engines: {node: '>= 0.4'}
 
-  '@types/d3-polygon@3.0.2':
-    resolution: {integrity: sha512-ZuWOtMaHCkN9xoeEMr1ubW2nGWsp4nIql+OPQRstu4ypeZ+zk3YKqQT0CXVe/PYqrKpZAi+J9mTs05TKwjXSRA==}
+  is-number-object@1.1.1:
+    resolution: {integrity: sha512-lZhclumE1G6VYD8VHe35wFaIif+CTy5SJIi5+3y4psDgWu4wPDoBhF8NxUOinEc7pHgiTsT6MaBb92rKhhD+Xw==}
+    engines: {node: '>= 0.4'}
 
-  '@types/d3-quadtree@3.0.6':
-    resolution: {integrity: sha512-oUzyO1/Zm6rsxKRHA1vH0NEDG58HrT5icx/azi9MF1TWdtttWl0UIUsjEQBBh+SIkrpd21ZjEv7ptxWys1ncsg==}
+  is-number@7.0.0:
+    resolution: {integrity: sha512-41Cifkg6e8TylSpdtTpeLVMqvSBEVzTttHvERD741+pnZ8ANv0004MRL43QKPDlK9cGvNp6NZWZUBlbGXYxxng==}
+    engines: {node: '>=0.12.0'}
 
-  '@types/d3-random@3.0.3':
-    resolution: {integrity: sha512-Imagg1vJ3y76Y2ea0871wpabqp613+8/r0mCLEBfdtqC7xMSfj9idOnmBYyMoULfHePJyxMAw3nWhJxzc+LFwQ==}
+  is-online@10.0.0:
+    resolution: {integrity: sha512-WCPdKwNDjXJJmUubf2VHLMDBkUZEtuOvpXUfUnUFbEnM6In9ByiScL4f4jKACz/fsb2qDkesFerW3snf/AYz3A==}
+    engines: {node: '>=14.16'}
 
-  '@types/d3-scale-chromatic@3.1.0':
-    resolution: {integrity: sha512-iWMJgwkK7yTRmWqRB5plb1kadXyQ5Sj8V/zYlFGMUBbIPKQScw+Dku9cAAMgJG+z5GYDoMjWGLVOvjghDEFnKQ==}
+  is-plain-obj@4.1.0:
+    resolution: {integrity: sha512-+Pgi+vMuUNkJyExiMBt5IlFoMyKnr5zhJ4Uspz58WOhBF5QoIZkFyNHIbBAtHwzVAgk5RtndVNsDRN61/mmDqg==}
+    engines: {node: '>=12'}
 
-  '@types/d3-scale@4.0.9':
-    resolution: {integrity: sha512-dLmtwB8zkAeO/juAMfnV+sItKjlsw2lKdZVVy6LRr0cBmegxSABiLEpGVmSJJ8O08i4+sGR6qQtb6WtuwJdvVw==}
+  is-regex@1.2.1:
+    resolution: {integrity: sha512-MjYsKHO5O7mCsmRGxWcLWheFqN9DJ/2TmngvjKXihe6efViPqc274+Fx/4fYj/r03+ESvBdTXK0V6tA3rgez1g==}
+    engines: {node: '>= 0.4'}
 
-  '@types/d3-selection@3.0.11':
-    resolution: {integrity: sha512-bhAXu23DJWsrI45xafYpkQ4NtcKMwWnAC/vKrd2l+nxMFuvOT3XMYTIj2opv8vq8AO5Yh7Qac/nSeP/3zjTK0w==}
+  is-set@2.0.3:
+    resolution: {integrity: sha512-iPAjerrse27/ygGLxw+EBR9agv9Y6uLeYVJMu+QNCoouJ1/1ri0mGrcWpfCqFZuzzx3WjtwxG098X+n4OuRkPg==}
+    engines: {node: '>= 0.4'}
 
-  '@types/d3-shape@3.1.8':
-    resolution: {integrity: sha512-lae0iWfcDeR7qt7rA88BNiqdvPS5pFVPpo5OfjElwNaT2yyekbM0C9vK+yqBqEmHr6lDkRnYNoTBYlAgJa7a4w==}
+  is-shared-array-buffer@1.0.4:
+    resolution: {integrity: sha512-ISWac8drv4ZGfwKl5slpHG9OwPNty4jOWPRIhBpxOoD+hqITiwuipOQ2bNthAzwA3B4fIjO4Nln74N0S9byq8A==}
+    engines: {node: '>= 0.4'}
 
-  '@types/d3-time-format@4.0.3':
-    resolution: {integrity: sha512-5xg9rC+wWL8kdDj153qZcsJ0FWiFt0J5RB6LYUNZjwSnesfblqrI/bJ1wBdJ8OQfncgbJG5+2F+qfqnqyzYxyg==}
+  is-string@1.1.1:
+    resolution: {integrity: sha512-BtEeSsoaQjlSPBemMQIrY1MY0uM6vnS1g5fmufYOtnxLGUZM2178PKbhsk7Ffv58IX+ZtcvoGwccYsh0PglkAA==}
+    engines: {node: '>= 0.4'}
 
-  '@types/d3-time@3.0.4':
-    resolution: {integrity: sha512-yuzZug1nkAAaBlBBikKZTgzCeA+k1uy4ZFwWANOfKw5z5LRhV0gNA7gNkKm7HoK+HRN0wX3EkxGk0fpbWhmB7g==}
+  is-symbol@1.1.1:
+    resolution: {integrity: sha512-9gGx6GTtCQM73BgmHQXfDmLtfjjTUDSyoxTCbp5WtoixAhfgsDirWIcVQ/IHpvI5Vgd5i/J5F7B9cN/WlVbC/w==}
+    engines: {node: '>= 0.4'}
 
-  '@types/d3-timer@3.0.2':
-    resolution: {integrity: sha512-Ps3T8E8dZDam6fUyNiMkekK3XUsaUEik+idO9/YjPtfj2qruF8tFBXS7XhtE4iIXBLxhmLjP3SXpLhVf21I9Lw==}
+  is-typed-array@1.1.15:
+    resolution: {integrity: sha512-p3EcsicXjit7SaskXHs1hA91QxgTw46Fv6EFKKGS5DRFLD8yKnohjF3hxoju94b/OcMZoQukzpPpBE9uLVKzgQ==}
+    engines: {node: '>= 0.4'}
 
-  '@types/d3-transition@3.0.9':
-    resolution: {integrity: sha512-uZS5shfxzO3rGlu0cC3bjmMFKsXv+SmZZcgp0KD22ts4uGXp5EVYGzu/0YdwZeKmddhcAccYtREJKkPfXkZuCg==}
+  is-url@1.2.4:
+    resolution: {integrity: sha512-ITvGim8FhRiYe4IQ5uHSkj7pVaPDrCTkNd3yq3cV7iZAcJdHTUMPMEHcqSOy9xZ9qFenQCvi+2wjH9a1nXqHww==}
 
-  '@types/d3-zoom@3.0.8':
-    resolution: {integrity: sha512-iqMC4/YlFCSlO8+2Ii1GGGliCAY4XdeG748w5vQUbevlbDu0zSjH/+jojorQVBK/se0j6DUFNPBGSqD3YWYnDw==}
+  is-weakmap@2.0.2:
+    resolution: {integrity: sha512-K5pXYOm9wqY1RgjpL3YTkF39tni1XajUIkawTLUo9EZEVUFga5gSQJF8nNS7ZwJQ02y+1YCNYcMh+HIf1ZqE+w==}
+    engines: {node: '>= 0.4'}
 
-  '@types/d3@7.4.3':
-    resolution: {integrity: sha512-lZXZ9ckh5R8uiFVt8ogUNf+pIrK4EsWrx2Np75WvF/eTpJ0FMHNhjXk8CKEx/+gpHbNQyJWehbFaTvqmHWB3ww==}
+  is-weakref@1.1.1:
+    resolution: {integrity: sha512-6i9mGWSlqzNMEqpCp93KwRS1uUOodk2OJ6b+sq7ZPDSy2WuI5NFIxp/254TytR8ftefexkWn5xNiHUNpPOfSew==}
+    engines: {node: '>= 0.4'}
 
-  '@types/debug@4.1.13':
-    resolution: {integrity: sha512-KSVgmQmzMwPlmtljOomayoR89W4FynCAi3E8PPs7vmDVPe84hT+vGPKkJfThkmXs0x0jAaa9U8uW8bbfyS2fWw==}
+  is-weakset@2.0.4:
+    resolution: {integrity: sha512-mfcwb6IzQyOKTs84CQMrOwW4gQcaTOAWJ0zzJCl2WSPDrWk/OzDaImWFH3djXhb24g4eudZfLRozAvPGw4d9hQ==}
+    engines: {node: '>= 0.4'}
 
-  '@types/esrecurse@4.3.1':
-    resolution: {integrity: sha512-xJBAbDifo5hpffDBuHl0Y8ywswbiAp/Wi7Y/GtAgSlZyIABppyurxVueOPE8LUQOxdlgi6Zqce7uoEpqNTeiUw==}
+  is-wsl@2.2.0:
+    resolution: {integrity: sha512-fKzAra0rGJUUBwGBgNkHZuToZcn+TtXHpeCgmkMJMMYx1sQDYaCSyjJBSCa2nH1DGm7s3n1oBnohoVTBaN7Lww==}
+    engines: {node: '>=8'}
 
-  '@types/estree-jsx@1.0.5':
-    resolution: {integrity: sha512-52CcUVNFyfb1A2ALocQw/Dd1BQFNmSdkuC3BkZ6iqhdMfQz7JWOFRuJFloOzjk+6WijU56m9oKXFAXc7o3Towg==}
+  isarray@2.0.5:
+    resolution: {integrity: sha512-xHjhDr3cNBK0BzdUJSPXZntQUx/mwMS5Rw4A7lPJ90XGAO6ISP/ePDNuo0vhqOZU+UD5JoodwCAAoZQd3FeAKw==}
 
-  '@types/estree@1.0.9':
-    resolution: {integrity: sha512-GhdPgy1el4/ImP05X05Uw4cw2/M93BCUmnEvWZNStlCzEKME4Fkk+YpoA5OiHNQmoS7Cafb8Xa3Pya8m1Qrzeg==}
+  isexe@2.0.0:
+    resolution: {integrity: sha512-RHxMLp9lnKHGHRng9QFhRCMbYAcVpn69smSGcq3f36xjgVVWThj4qqLbTLlq7Ssj8B+fIQ1EuCEGI2lKsyQeIw==}
 
-  '@types/express-serve-static-core@4.19.8':
-    resolution: {integrity: sha512-02S5fmqeoKzVZCHPZid4b8JH2eM5HzQLZWN2FohQEy/0eXTq8VXZfSN6Pcr3F6N9R/vNrj7cpgbhjie6m/1tCA==}
+  isomorphic-fetch@3.0.0:
+    resolution: {integrity: sha512-qvUtwJ3j6qwsF3jLxkZ72qCgjMysPzDfeV240JHiGZsANBYd+EEuu35v7dfrJ9Up0Ak07D7GGSkGhCHTqg/5wA==}
 
-  '@types/express@4.17.25':
-    resolution: {integrity: sha512-dVd04UKsfpINUnK0yBoYHDF3xu7xVH4BuDotC/xGuycx4CgbP48X/KF/586bcObxT0HENHXEU8Nqtu6NR+eKhw==}
+  jiti@1.21.7:
+    resolution: {integrity: sha512-/imKNG4EbWNrVjoNC/1H5/9GFy+tqjGBHCaSsN+P2RnPqjsLmv6UD3Ej+Kj8nBWaRAwyk7kK5ZUc+OEatnTR3A==}
+    hasBin: true
 
-  '@types/geojson@7946.0.16':
-    resolution: {integrity: sha512-6C8nqWur3j98U6+lXDfTUWIfgvZU+EumvpHKcYjujKH7woYyLj2sUmff0tRhrqM7BohUw7Pz3ZB1jj2gW9Fvmg==}
+  jose@6.2.12:
+    resolution: {integrity: sha512-9NiFmJEex0sy2Dk58j2UGBSHgUs2ypF9eZSu4L6vjOX3Dp96Sw1F3uL+H+D1sx02jZZdzUT0HgvCy59CuvXcWw==}
 
-  '@types/gtag.js@0.0.20':
-    resolution: {integrity: sha512-wwAbk3SA2QeU67unN7zPxjEHmPmlXwZXZvQEpbEUQuMCRGgKyE1m6XDuTUA9b6pCGb/GqJmdfMOY5LuDjJSbbg==}
+  js-tokens@4.0.0:
+    resolution: {integrity: sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ==}
 
-  '@types/hast@2.3.10':
-    resolution: {integrity: sha512-McWspRw8xx8J9HurkVBfYj0xKoE25tOFlHGdx4MJ5xORQrMGZNqJhVQWaIbm6Oyla5kYOXtDiopzKRJzEOkwJw==}
+  js-yaml@3.15.2:
+    resolution: {integrity: sha512-6EuL879VkRA+1Cz578mKMiKvjPNEuk6+r1JaFzoSWejZmtf7xWbIyw1e3KkxlkzTIt9Taw6JBhEppG7utc1P+w==}
+    hasBin: true
 
-  '@types/hast@3.0.4':
-    resolution: {integrity: sha512-WPs+bbQw5aCj+x6laNGWLH3wviHtoCv/P3+otBhbOhJgG8qtpdAMlTCxLtsTWA7LH1Oh/bFCHsBn0TPS5m30EQ==}
+  js-yaml@4.3.1:
+    resolution: {integrity: sha512-CY6crGq313MX8GkwvB7tzgp99vjQxY1++5y10/BKN/GUfHqWaOGQMNZkBvqSzsZKWk/ijwHlWzzkLulsGHhjWQ==}
+    hasBin: true
 
-  '@types/history@4.7.11':
-    resolution: {integrity: sha512-qjDJRrmvBMiTx+jyLxvLfJU7UznFuokDv4f3WRuriHKERccVpFU+8XMQUAbDzoiJCsmexxRExQeMwwCdamSKDA==}
+  jsep@1.6.0:
+    resolution: {integrity: sha512-Y8Tr54CX7B5YGAwo7/n8eumidEX3Opx98RyyQVnlHqUaZcPA8uUzL2v1rshr9ypW9Q6hNjfJtg3sL+8kaNE7TA==}
+    engines: {node: '>= 20.16.0'}
 
-  '@types/html-minifier-terser@6.1.0':
-    resolution: {integrity: sha512-oh/6byDPnL1zeNXFrDXFLyZjkr1MsBG667IM792caf1L2UPOOMf65NFzjUH/ltyfwjAGfs1rsX1eftK0jC/KIg==}
+  json-buffer@3.0.1:
+    resolution: {integrity: sha512-4bV5BfR2mqfQTJm+V5tPPdf+ZpuhiIvTuAB5g8kcrXOZpTT/QwwVRWBywX1ozr6lEuPdbHxwaJlm9G6mI2sfSQ==}
 
-  '@types/http-cache-semantics@4.2.0':
-    resolution: {integrity: sha512-L3LgimLHXtGkWikKnsPg0/VFx9OGZaC+eN1u4r+OB1XRqH3meBIAVC2zr1WdMH+RHmnRkqliQAOHNJ/E0j/e0Q==}
+  json-p3@2.2.2:
+    resolution: {integrity: sha512-TmTgkx+C1ne8Wdm9dFQ4/jCeYYbSoeYJAkRpvTz6O+zWN1Dc3cKW8Mt52sa8mSRXy/+JykA5I6rmM+k8h+JRRg==}
 
-  '@types/http-errors@2.0.5':
-    resolution: {integrity: sha512-r8Tayk8HJnX0FztbZN7oVqGccWgw98T/0neJphO91KkmOzug1KkofZURD4UaD5uH8AqcFLfdPErnBod0u71/qg==}
+  json-schema-compare@0.2.2:
+    resolution: {integrity: sha512-c4WYmDKyJXhs7WWvAWm3uIYnfyWFoIp+JEoX34rctVvEkMYCPGhXtvmFFXiffBbxfZsvQ0RNnV5H7GvDF5HCqQ==}
 
-  '@types/http-proxy@1.17.17':
-    resolution: {integrity: sha512-ED6LB+Z1AVylNTu7hdzuBqOgMnvG/ld6wGCG8wFnAzKX5uyW2K3WD52v0gnLCTK/VLpXtKckgWuyScYK6cSPaw==}
+  json-schema-merge-allof@0.8.1:
+    resolution: {integrity: sha512-CTUKmIlPJbsWfzRRnOXz+0MjIqvnleIXwFTzz+t9T86HnYX/Rozria6ZVGLktAU9e+NygNljveP+yxqtQp/Q4w==}
+    engines: {node: '>=12.0.0'}
 
-  '@types/istanbul-lib-coverage@2.0.6':
-    resolution: {integrity: sha512-2QF/t/auWm0lsy8XtKVPG19v3sSOQlJe/YHZgfjb/KBBHOGSV+J2q/S671rcq9uTBrLAXmZpqJiaQbMT+zNU1w==}
+  json-schema-traverse@0.4.1:
+    resolution: {integrity: sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg==}
 
-  '@types/istanbul-lib-report@3.0.3':
-    resolution: {integrity: sha512-NQn7AHQnk/RSLOxrBbGyJM/aVQ+pjj5HCgasFxc0K/KhoATfQ/47AyUl15I2yBUpihjmas+a+VJBOqecrFH+uA==}
+  json-schema-traverse@1.0.0:
+    resolution: {integrity: sha512-NM8/P9n3XjXhIZn1lLhkFaACTOURQXjWhV4BA/RnOv8xvgqtqpAX9IO4mRQxSx1Rlo4tqzeqb0sOlruaOy3dug==}
 
-  '@types/istanbul-reports@3.0.4':
-    resolution: {integrity: sha512-pk2B1NWalF9toCRu6gjBzR69syFjP4Od8WRAX+0mmf9lAjCRicLOWc+ZrxZHx/0XRjotgkF9t6iaMJ+aXcOdZQ==}
+  jsonc-parser@2.2.1:
+    resolution: {integrity: sha512-o6/yDBYccGvTz1+QFevz6l6OBZ2+fMVu2JZ9CIhzsYRX4mjaK5IyX9eldUdCmga16zlgQxyrj5pt9kzuj2C02w==}
 
-  '@types/js-cookie@2.2.7':
-    resolution: {integrity: sha512-aLkWa0C0vO5b4Sr798E26QgOkss68Un0bLjs7u9qxzPT5CG+8DuNTffWES58YzJs3hrVAOs1wonycqEBqNJubA==}
+  jsonfile@6.2.1:
+    resolution: {integrity: sha512-zwOTdL3rFQ/lRdBnntKVOX6k5cKJwEc1HdilT71BWEu7J41gXIB2MRp+vxduPSwZJPWBxEzv4yH1wYLJGUHX4Q==}
 
-  '@types/json-schema@7.0.15':
-    resolution: {integrity: sha512-5+fP8P8MFNC+AyZCDxrB2pkZFPGzqQWUzpSeuuVLvm8VMcorNYavBqoFcxK8bQz4Qsbn4oUEEem4wDLfcysGHA==}
+  jsonpath-plus@10.4.0:
+    resolution: {integrity: sha512-T92WWatJXmhBbKsgH/0hl+jxjdXrifi5IKeMY02DWggRxX0UElcbVzPlmgLTbvsPeW1PasQ6xE2Q75stkhGbsA==}
+    engines: {node: '>=18.0.0'}
+    hasBin: true
 
-  '@types/katex@0.16.8':
-    resolution: {integrity: sha512-trgaNyfU+Xh2Tc+ABIb44a5AYUpicB3uwirOioeOkNPPbmgRNtcWyDeeFRzjPZENO9Vq8gvVqfhaaXWLlevVwg==}
+  jsonpointer@5.0.1:
+    resolution: {integrity: sha512-p/nXbhSEcu3pZRdkW1OfJhpsVtW1gd4Wa1fnQc9YLiTfAjn0312eMKimbdIQzuZl9aa9xUGaRlP9T/CJE/ditQ==}
+    engines: {node: '>=0.10.0'}
 
-  '@types/mdast@3.0.15':
-    resolution: {integrity: sha512-LnwD+mUEfxWMa1QpDraczIn6k0Ee3SMicuYSSzS6ZYl2gKS09EClnJYGd8Du6rfc5r/GZEk5o1mRb8TaTj03sQ==}
+  katex@0.16.47:
+    resolution: {integrity: sha512-Eeo8Ys1doU1z+x8AZsPpQu+p/QcZBI5PeOo7QGQdy2x2m0MU/hYagBbGOmXwr5KVbEfVuWv9LpnQWeehogurjg==}
+    hasBin: true
 
-  '@types/mdast@4.0.4':
-    resolution: {integrity: sha512-kGaNbPh1k7AFzgpud/gMdvIm5xuECykRR+JnWKQno9TAXVa6WIVCGTPvYGekIDL4uwCZQSYbUxNBSb1aUo79oA==}
+  keytar@7.9.0:
+    resolution: {integrity: sha512-VPD8mtVtm5JNtA2AErl6Chp06JBfy7diFQ7TQQhdpWOl6MrCRB+eRbvAZUsbGQS9kiMq0coJsy0W0vHpDCkWsQ==}
 
-  '@types/mdurl@1.0.5':
-    resolution: {integrity: sha512-6L6VymKTzYSrEf4Nev4Xa1LCHKrlTlYCBMTlQKFuddo1CvQcE52I0mwfOJayueUC7MJuXOeHTcIU683lzd0cUA==}
+  keyv@4.5.4:
+    resolution: {integrity: sha512-oxVHkHR/EJf2CNXnWxRLW6mg7JyCCUcG0DtEGmL2ctUo1PNTin1PUil+r/+4r5MpVgC/fn1kjsx7mjSujKqIpw==}
 
-  '@types/mdx@2.0.14':
-    resolution: {integrity: sha512-T48PeuJtvLosNTPVhfnIp3i/n3a4g4Bad7YCq5k64D4u7NwDrAotikQ+5+sjtUvBmxCMlbo3dVL+C2dP0rWHzg==}
+  lcm@0.0.3:
+    resolution: {integrity: sha512-TB+ZjoillV6B26Vspf9l2L/vKaRY/4ep3hahcyVkCGFgsTNRUQdc24bQeNFiZeoxH0vr5+7SfNRMQuPHv/1IrQ==}
 
-  '@types/mime@1.3.5':
-    resolution: {integrity: sha512-/pyBZWSLD2n0dcHE3hq8s8ZvcETHtEuF+3E7XVt0Ig2nvsVQXdghHVcEkIWjy9A0wKfTn97a/PSDYohKIlnP/w==}
+  leven@3.1.0:
+    resolution: {integrity: sha512-qsda+H8jTaUaN/x5vzW2rzc+8Rw4TAQ/4KjB46IwK5VH+IlVeeeje/EoZRpiXvIqjFgK84QffqPztGI3VBLG1A==}
+    engines: {node: '>=6'}
 
-  '@types/ms@2.1.0':
-    resolution: {integrity: sha512-GsCCIZDE/p3i96vtEqx+7dBUGXrc7zeSK3wwPHIaRThS+9OhWIXRqzs4d6k1SVU8g91DrNRWxWUGhp5KXQb2VA==}
+  leven@4.1.0:
+    resolution: {integrity: sha512-KZ9W9nWDT7rF7Dazg8xyLHGLrmpgq2nVNFUckhqdW3szVP6YhCpp/RAnpmVExA9JvrMynjwSLVrEj3AepHR6ew==}
+    engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
 
-  '@types/node@17.0.45':
-    resolution: {integrity: sha512-w+tIMs3rq2afQdsPJlODhoUEKzFP1ayaoyl1CcnwtIlsVe7K7bA1NGm4s3PraqTLlXnbIN84zuBlxBWo1u9BLw==}
+  lilconfig@3.1.4:
+    resolution: {integrity: sha512-zJZyBmQhArDRefuWTypZxwDpFDIYmrj8ypSBvwGD5P13Y95s6DjzKgu4DVdGbeQa5PDEsAOCAPNk4X+QOR006w==}
+    engines: {node: '>=14'}
 
-  '@types/node@25.9.2':
-    resolution: {integrity: sha512-G05zqtJhcDLb8uslf5EjCxXg9G1KQxiV8OS0R26IC//Eoyitzqe8z37I7cqvnZlrlSfgocQRfSn/AHBZJJFyGw==}
+  linebreak@1.1.0:
+    resolution: {integrity: sha512-MHp03UImeVhB7XZtjd0E4n6+3xr5Dq/9xI/5FptGk5FrbDR3zagPa2DS6U8ks/3HjbKWG9Q1M2ufOzxV2qLYSQ==}
 
-  '@types/parse5@6.0.3':
-    resolution: {integrity: sha512-SuT16Q1K51EAVPz1K29DJ/sXjhSQ0zjvsypYJ6tlwVsRV9jwW5Adq2ch8Dq8kDBCkYnELS7N7VNCSB5nC56t/g==}
+  lines-and-columns@1.2.4:
+    resolution: {integrity: sha512-7ylylesZQ/PV29jhEDl3Ufjo6ZX7gCqJr5F7PKrqc93v7fzSymt1BpwEU8nAUXs8qzzvqhbjhK5QZg6Mt/HkBg==}
 
-  '@types/prismjs@1.26.6':
-    resolution: {integrity: sha512-vqlvI7qlMvcCBbVe0AKAb4f97//Hy0EBTaiW8AalRnG/xAN5zOiWWyrNqNXeq8+KAuvRewjCVY1+IPxk4RdNYw==}
+  lodash.topath@4.5.2:
+    resolution: {integrity: sha512-1/W4dM+35DwvE/iEd1M9ekewOSTlpFekhw9mhAtrwjVqUr83/ilQiyAvmg4tVX7Unkcfl1KC+i9WdaT4B6aQcg==}
 
-  '@types/prop-types@15.7.15':
-    resolution: {integrity: sha512-F6bEyamV9jKGAFBEmlQnesRPGOQqS2+Uwi0Em15xenOxHaf2hv6L8YCVn3rPdPJOiJfPiCnLIRyvwVaqMY3MIw==}
+  lodash@4.18.1:
+    resolution: {integrity: sha512-dMInicTPVE8d1e5otfwmmjlxkZoUpiVLwyeTdUsi/Caj/gfzzblBcCE5sRHV/AsjuCmxWrte2TNGSYuCeCq+0Q==}
 
-  '@types/qs@6.15.1':
-    resolution: {integrity: sha512-GZHUBZR9hckSUhrxmp1nG6NwdpM9fCunJwyThLW1X3AyHgd9IlHb6VANpQQqDr2o/qQp6McZ3y/IA2rVzKzSbw==}
+  longest-streak@3.1.0:
+    resolution: {integrity: sha512-9Ri+o0JYgehTaVBBDoMqIl8GXtbWg711O3srftcHhZ0dqnETqLaoIK0x17fUw9rFSlK/0NlsKe0Ahhyl5pXE2g==}
 
-  '@types/range-parser@1.2.7':
-    resolution: {integrity: sha512-hKormJbkJqzQGhziax5PItDUTMAM9uE2XXQmM37dyd4hVM+5aVl7oVxMVUiVQn2oCQFN/LKCZdvSM0pFRqbSmQ==}
+  lowercase-keys@3.0.0:
+    resolution: {integrity: sha512-ozCC6gdQ+glXOQsveKD0YsDy8DSQFjDTz4zyzEHNV5+JP5D62LmfDZ6o1cycFx9ouG940M5dE8C8CTewdj2YWQ==}
+    engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
 
-  '@types/react-dom@17.0.26':
-    resolution: {integrity: sha512-Z+2VcYXJwOqQ79HreLU/1fyQ88eXSSFh6I3JdrEHQIfYSI0kCQpTGvOrbE6jFGGYXKsHuwY9tBa/w5Uo6KzrEg==}
-    peerDependencies:
-      '@types/react': ^17.0.0
+  markdown-extensions@2.0.0:
+    resolution: {integrity: sha512-o5vL7aDWatOTX8LzaS1WMoaoxIiLRQJuIKKe2wAw6IeULDHaqbiqiggmx+pKvZDb1Sj+pE46Sn1T7lCqfFtg1Q==}
+    engines: {node: '>=16'}
 
-  '@types/react-router-config@5.0.11':
-    resolution: {integrity: sha512-WmSAg7WgqW7m4x8Mt4N6ZyKz0BubSj/2tVUMsAHp+Yd2AMwcSbeFq9WympT19p5heCFmF97R9eD5uUR/t4HEqw==}
+  markdown-table@3.0.4:
+    resolution: {integrity: sha512-wiYz4+JrLyb/DqW2hkFJxP7Vd7JuTDm77fvbM8VfEQdmSMqcImWeeRbHwZjBjIFki/VaMK2BhFi7oUUZeM5bqw==}
 
-  '@types/react-router-dom@5.3.3':
-    resolution: {integrity: sha512-kpqnYK4wcdm5UaWI3fLcELopqLrHgLqNsdpHauzlQktfkHL3npOSwtj1Uz9oKBAzs7lFtVkV8j83voAz2D8fhw==}
+  math-intrinsics@1.1.0:
+    resolution: {integrity: sha512-/IXtbwEk5HTPyEwyKX6hGkYXxM9nbj64B+ilVJnC/R6B0pH5G4V3b0pVbL7DBj4tkhBAppbQUlf6F6Xl9LHu1g==}
+    engines: {node: '>= 0.4'}
 
-  '@types/react-router@5.1.20':
-    resolution: {integrity: sha512-jGjmu/ZqS7FjSH6owMcD5qpq19+1RS9DeVRqfl1FeBMxTDQAGwlMWOcs52NDoXaNKyG3d1cYQFMs9rCrb88o9Q==}
+  mdast-util-find-and-replace@3.0.3:
+    resolution: {integrity: sha512-xPgpDNl0/OXHsI7TlaIs22lWnH3KlpvZdXG1ET/m/YT2Hhdkx8lJV4kLphE6l9simyM4KPDFBwas08BgEob6Jw==}
 
-  '@types/react@17.0.93':
-    resolution: {integrity: sha512-KM4Ty/ZTLZupiYxZVAlP+InNJS3De6uBMdq0ePa6/04+eG9Y7ftnWfst1xTLQ5rwAhgHwQ4momt/O4KepdGBTw==}
+  mdast-util-from-markdown@2.0.2:
+    resolution: {integrity: sha512-uZhTV/8NBuw0WHkPTrCqDOl0zVe1BIng5ZtHoDk49ME1qqcjYmmLmOf0gELgcRMxN4w2iuIeVso5/6QymSrgmA==}
 
-  '@types/react@19.2.17':
-    resolution: {integrity: sha512-MXfmqaVPEVgkBT/aY0aGCkRWWtByiYQXo3xdQ8r5RzuFrPiRn8Gar2tQdXSUQ2GKV3bkXckek89V8wQBY2Q/Aw==}
+  mdast-util-from-markdown@2.1.0:
+    resolution: {integrity: sha512-KRLgmPaP2H1ul2bpoJkOS+9pAcDAAj9Nu1mqLnh8NLeJG5tlvj42TH80PIGBpROWlRXLk0lDrWNuZCFy/tsB4A==}
 
-  '@types/retry@0.12.2':
-    resolution: {integrity: sha512-XISRgDJ2Tc5q4TRqvgJtzsRkFYNJzZrhTdtMoGVBttwzzQJkPnS3WWTFc7kuDRoPtPakl+T+OfdEUjYJj7Jbow==}
+  mdast-util-frontmatter@2.0.1:
+    resolution: {integrity: sha512-LRqI9+wdgC25P0URIJY9vwocIzCcksduHQ9OF2joxQoyTNVduwLAFUzjoopuRJbJAReaKrNQKAZKL3uCMugWJA==}
 
-  '@types/sax@1.2.7':
-    resolution: {integrity: sha512-rO73L89PJxeYM3s3pPPjiPgVVcymqU490g0YO5n5By0k2Erzj6tay/4lr1CHAAU4JyOWd1rpQ8bCf6cZfHU96A==}
+  mdast-util-gfm-autolink-literal@2.0.1:
+    resolution: {integrity: sha512-5HVP2MKaP6L+G6YaxPNjuL0BPrq9orG3TsrZ9YXbA3vDw/ACI4MEsnoDpn6ZNm7GnZgtAcONJyPhOP8tNJQavQ==}
 
-  '@types/scheduler@0.16.8':
-    resolution: {integrity: sha512-WZLiwShhwLRmeV6zH+GkbOFT6Z6VklCItrDioxUnv+u4Ll+8vKeFySoFyK/0ctcRpOmwAicELfmys1sDc/Rw+A==}
+  mdast-util-gfm-footnote@2.1.0:
+    resolution: {integrity: sha512-sqpDWlsHn7Ac9GNZQMeUzPQSMzR6Wv0WKRNvQRg0KqHh02fpTz69Qc1QSseNX29bhz1ROIyNyxExfawVKTm1GQ==}
 
-  '@types/semver@7.7.1':
-    resolution: {integrity: sha512-FmgJfu+MOcQ370SD0ev7EI8TlCAfKYU+B4m5T3yXc1CiRN94g/SZPtsCkk506aUDtlMnFZvasDwHHUcZUEaYuA==}
+  mdast-util-gfm-strikethrough@2.0.1:
+    resolution: {integrity: sha512-OuJHqvr455pwu2OaOrir7dbzqs4jlWKOtlu9L6GjcIjjQwNyw02VntQsr/Ek6/A13vgnXfUhBekWRUP1OkNivw==}
 
-  '@types/send@0.17.6':
-    resolution: {integrity: sha512-Uqt8rPBE8SY0RK8JB1EzVOIZ32uqy8HwdxCnoCOsYrvnswqmFZ/k+9Ikidlk/ImhsdvBsloHbAlewb2IEBV/Og==}
+  mdast-util-gfm-table@2.0.0:
+    resolution: {integrity: sha512-78UEvebzz/rJIxLvE7ZtDd/vIQ0RHv+3Mh5DR96p7cS7HsBhYIICDBCu8csTNWNO6tBWfqXPWekRuj2FNOGOZg==}
 
-  '@types/send@1.2.1':
-    resolution: {integrity: sha512-arsCikDvlU99zl1g69TcAB3mzZPpxgw0UQnaHeC1Nwb015xp8bknZv5rIfri9xTOcMuaVgvabfIRA7PSZVuZIQ==}
+  mdast-util-gfm-task-list-item@2.0.0:
+    resolution: {integrity: sha512-IrtvNvjxC1o06taBAVJznEnkiHxLFTzgonUdy8hzFVeDun0uTjxxrRGVaNFqkU1wJR3RBPEfsxmU6jDWPofrTQ==}
 
-  '@types/serve-index@1.9.4':
-    resolution: {integrity: sha512-qLpGZ/c2fhSs5gnYsQxtDEq3Oy8SXPClIXkW5ghvAvsNuVSA8k+gCONcUCS/UjLEYvYps+e8uBtfgXgvhwfNug==}
+  mdast-util-gfm@3.0.0:
+    resolution: {integrity: sha512-dgQEX5Amaq+DuUqf26jJqSK9qgixgd6rYDHAv4aTBuA92cTknZlKpPfa86Z/s8Dj8xsAQpFfBmPUHWJBWqS4Bw==}
 
-  '@types/serve-static@1.15.10':
-    resolution: {integrity: sha512-tRs1dB+g8Itk72rlSI2ZrW6vZg0YrLI81iQSTkMmOqnqCaNr/8Ek4VwWcN5vZgCYWbg/JJSGBlUaYGAOP73qBw==}
+  mdast-util-gfm@3.1.0:
+    resolution: {integrity: sha512-0ulfdQOM3ysHhCJ1p06l0b0VKlhU0wuQs3thxZQagjcjPrlFRqY215uZGHHJan9GEAXd9MbfPjFJz+qMkVR6zQ==}
 
-  '@types/sockjs@0.3.36':
-    resolution: {integrity: sha512-MK9V6NzAS1+Ud7JV9lJLFqW85VbC9dq3LmwZCuBe4wBDgKC0Kj/jd8Xl+nSviU+Qc3+m7umHHyHg//2KSa0a0Q==}
+  mdast-util-math@3.0.0:
+    resolution: {integrity: sha512-Tl9GBNeG/AhJnQM221bJR2HPvLOSnLE/T9cJI9tlc6zwQk2nPk/4f0cHkOdEixQPC/j8UtKDdITswvLAy1OZ1w==}
 
-  '@types/trusted-types@2.0.7':
-    resolution: {integrity: sha512-ScaPdn1dQczgbl0QFTeTOmVHFULt394XJgOQNoyVhZ6r2vLnMLJfBPd53SB52T/3G36VI1/g2MZaX0cwDuXsfw==}
+  mdast-util-mdx-expression@2.0.1:
+    resolution: {integrity: sha512-J6f+9hUp+ldTZqKRSg7Vw5V6MqjATc+3E4gf3CFNcuZNWD8XdyI6zQ8GqH7f8169MM6P7hMBRDVGnn7oHB9kXQ==}
 
-  '@types/unist@2.0.11':
-    resolution: {integrity: sha512-CmBKiL6NNo/OqgmMn95Fk9Whlp2mtvIv+KNpQKN2F4SjvrEesubTRWGYSg+BnWZOnlCaSTU1sMpsBOzgbYhnsA==}
+  mdast-util-mdx-jsx@3.1.3:
+    resolution: {integrity: sha512-bfOjvNt+1AcbPLTFMFWY149nJz0OjmewJs3LQQ5pIyVGxP4CdOqNVJL6kTaM5c68p8q82Xv3nCyFfUnuEcH3UQ==}
 
-  '@types/unist@3.0.3':
-    resolution: {integrity: sha512-ko/gIFJRv177XgZsZcBwnqJN5x/Gien8qNOn0D5bQU/zAzVf9Zt3BlcUiLqhV9y4ARk0GbT3tnUiPNgnTXzc/Q==}
+  mdast-util-mdx-jsx@3.2.0:
+    resolution: {integrity: sha512-lj/z8v0r6ZtsN/cGNNtemmmfoLAFZnjMbNyLzBafjzikOM+glrjNHPlf6lQDOTccj9n5b0PPihEBbhneMyGs1Q==}
 
-  '@types/use-sync-external-store@0.0.6':
-    resolution: {integrity: sha512-zFDAD+tlpf2r4asuHEj0XH6pY6i0g5NeAHPn+15wk3BV6JA69eERFXC1gyGThDkVa1zCyKr5jox1+2LbV/AMLg==}
+  mdast-util-mdx@3.0.0:
+    resolution: {integrity: sha512-JfbYLAW7XnYTTbUsmpu0kdBUVe+yKVJZBItEjwyYJiDJuZ9w4eeaqks4HQO+R7objWgS2ymV60GYpI14Ug554w==}
 
-  '@types/ws@8.18.1':
-    resolution: {integrity: sha512-ThVF6DCVhA8kUGy+aazFQ4kXQ7E1Ty7A3ypFOe0IcJV8O/M511G99AW24irKrW56Wt44yG9+ij8FaqoBGkuBXg==}
+  mdast-util-mdxjs-esm@2.0.1:
+    resolution: {integrity: sha512-EcmOpxsZ96CvlP03NghtH1EsLtr0n9Tm4lPUJUBccV9RwUOneqSycg19n5HGzCf+10LozMRSObtVr3ee1WoHtg==}
 
-  '@types/yargs-parser@21.0.3':
-    resolution: {integrity: sha512-I4q9QU9MQv4oEOz4tAHJtNz1cwuLxn2F3xcc2iV5WdqLPpUnj30aUuxt1mAxYTG+oe8CZMV/+6rU4S4gRDzqtQ==}
+  mdast-util-phrasing@4.1.0:
+    resolution: {integrity: sha512-TqICwyvJJpBwvGAMZjj4J2n0X8QWp21b9l0o7eXyVJ25YNWYbJDVIyD1bZXE6WtV6RmKJVYmQAKWa0zWOABz2w==}
 
-  '@types/yargs@17.0.35':
-    resolution: {integrity: sha512-qUHkeCyQFxMXg79wQfTtfndEC+N9ZZg76HJftDJp+qH2tV7Gj4OJi7l+PiWwJ+pWtW8GwSmqsDj/oymhrTWXjg==}
+  mdast-util-to-hast@13.2.1:
+    resolution: {integrity: sha512-cctsq2wp5vTsLIcaymblUriiTcZd0CwWtCbLvrOzYCDZoWyMNV8sZ7krj09FSnsiJi3WVsHLM4k6Dq/yaPyCXA==}
 
-  '@typescript-eslint/eslint-plugin@7.18.0':
-    resolution: {integrity: sha512-94EQTWZ40mzBc42ATNIBimBEDltSJ9RQHCC8vc/PDbxi4k8dVwUAv4o98dk50M1zB+JGFxp43FP7f8+FP8R6Sw==}
-    engines: {node: ^18.18.0 || >=20.0.0}
-    peerDependencies:
-      '@typescript-eslint/parser': ^7.0.0
-      eslint: ^8.56.0
-      typescript: '*'
-    peerDependenciesMeta:
-      typescript:
-        optional: true
+  mdast-util-to-markdown@2.2.0:
+    resolution: {integrity: sha512-2Jn/ADrHFFyyniBMi0bncTbJqU78K3/TEYvzvwrWWzD9MYPUa/Gm4r3nOeKFQg/PDM5BsbDYdc8ackW4NTY6NA==}
 
-  '@typescript-eslint/parser@7.18.0':
-    resolution: {integrity: sha512-4Z+L8I2OqhZV8qA132M4wNL30ypZGYOQVBfMgxDH/K5UX0PNqTu1c6za9ST5r9+tavvHiTWmBnKzpCJ/GlVFtg==}
-    engines: {node: ^18.18.0 || >=20.0.0}
-    peerDependencies:
-      eslint: ^8.56.0
-      typescript: '*'
-    peerDependenciesMeta:
-      typescript:
-        optional: true
+  mdast-util-to-string@4.0.0:
+    resolution: {integrity: sha512-0H44vDimn51F0YwvxSJSm0eCDOJTRlmN0R1yBh4HLj9wiV1Dn0QoXGbvFAWj2hSItVTlCmBF1hqKlIyUBVFLPg==}
 
-  '@typescript-eslint/scope-manager@5.62.0':
-    resolution: {integrity: sha512-VXuvVvZeQCQb5Zgf4HAxc04q5j+WrNAtNh9OwCsCgpKqESMTu3tF/jhZ3xG6T4NZwWl65Bg8KuS2uEvhSfLl0w==}
-    engines: {node: ^12.22.0 || ^14.17.0 || >=16.0.0}
+  media-typer@0.3.0:
+    resolution: {integrity: sha512-dq+qelQ9akHpcOl/gUVRTxVIOkAJ1wR3QAvb4RsVjS8oVoFjDGTc679wJYmUmknUF5HwMLOgb5O+a3KxfWapPQ==}
+    engines: {node: '>= 0.6'}
 
-  '@typescript-eslint/scope-manager@7.18.0':
-    resolution: {integrity: sha512-jjhdIE/FPF2B7Z1uzc6i3oWKbGcHb87Qw7AWj6jmEqNOfDFbJWtjt/XfwCpvNkpGWlcJaog5vTR+VV8+w9JflA==}
-    engines: {node: ^18.18.0 || >=20.0.0}
+  merge-descriptors@1.0.3:
+    resolution: {integrity: sha512-gaNvAS7TZ897/rVaZ0nMtAyxNyi/pdbjbAwUpFQpN70GqnVfOiXpeUUMKRBmzXaSQ8DdTX4/0ms62r2K+hE6mQ==}
 
-  '@typescript-eslint/type-utils@7.18.0':
-    resolution: {integrity: sha512-XL0FJXuCLaDuX2sYqZUUSOJ2sG5/i1AAze+axqmLnSkNEVMVYLF+cbwlB2w8D1tinFuSikHmFta+P+HOofrLeA==}
-    engines: {node: ^18.18.0 || >=20.0.0}
-    peerDependencies:
-      eslint: ^8.56.0
-      typescript: '*'
-    peerDependenciesMeta:
-      typescript:
-        optional: true
+  merge2@1.4.1:
+    resolution: {integrity: sha512-8q7VEgMJW4J8tcfVPy8g09NcQwZdbwFEqhe/WZkoIzjn/3TGDwtOCYtXGxA3O8tPzpczCCDgv+P2P5y00ZJOOg==}
+    engines: {node: '>= 8'}
 
-  '@typescript-eslint/types@5.62.0':
-    resolution: {integrity: sha512-87NVngcbVXUahrRTqIK27gD2t5Cu1yuCXxbLcFtCzZGlfyVWWh8mLHkoxzjsB6DDNnvdL+fW8MiwPEJyGJQDgQ==}
-    engines: {node: ^12.22.0 || ^14.17.0 || >=16.0.0}
+  methods@1.1.2:
+    resolution: {integrity: sha512-iclAHeNqNm68zFtnZ0e+1L2yUIdvzNoauKU4WBA3VvH/vPFieF7qfRlwUZU+DA9P9bPXIS90ulxoUoCH23sV2w==}
+    engines: {node: '>= 0.6'}
 
-  '@typescript-eslint/types@7.18.0':
-    resolution: {integrity: sha512-iZqi+Ds1y4EDYUtlOOC+aUmxnE9xS/yCigkjA7XpTKV6nCBd3Hp/PRGGmdwnfkV2ThMyYldP1wRpm/id99spTQ==}
-    engines: {node: ^18.18.0 || >=20.0.0}
+  micromark-core-commonmark@2.0.4:
+    resolution: {integrity: sha512-wxEeE8v8XVvOrxn1TZj74qYhAtTQsSqufHVS3uNVyT1MupXxhyaHk8/9xDNPh9BmL77QNDgWTkZ3RsYHB2ry7w==}
 
-  '@typescript-eslint/typescript-estree@5.62.0':
-    resolution: {integrity: sha512-CmcQ6uY7b9y694lKdRB8FEel7JbU/40iSAPomu++SjLMntB+2Leay2LO6i8VnJk58MtE9/nQSFIH6jpyRWyYzA==}
-    engines: {node: ^12.22.0 || ^14.17.0 || >=16.0.0}
-    peerDependencies:
-      typescript: '*'
-    peerDependenciesMeta:
-      typescript:
-        optional: true
+  micromark-extension-frontmatter@2.0.0:
+    resolution: {integrity: sha512-C4AkuM3dA58cgZha7zVnuVxBhDsbttIMiytjgsM2XbHAB2faRVaHRle40558FBN+DJcrLNCoqG5mlrpdU4cRtg==}
 
-  '@typescript-eslint/typescript-estree@7.18.0':
-    resolution: {integrity: sha512-aP1v/BSPnnyhMHts8cf1qQ6Q1IFwwRvAQGRvBFkWlo3/lH29OXA3Pts+c10nxRxIBrDnoMqzhgdwVe5f2D6OzA==}
-    engines: {node: ^18.18.0 || >=20.0.0}
-    peerDependencies:
-      typescript: '*'
-    peerDependenciesMeta:
-      typescript:
-        optional: true
+  micromark-extension-gfm-autolink-literal@2.1.0:
+    resolution: {integrity: sha512-oOg7knzhicgQ3t4QCjCWgTmfNhvQbDDnJeVu9v81r7NltNCVmhPy1fJRX27pISafdjL+SVc4d3l48Gb6pbRypw==}
 
-  '@typescript-eslint/utils@5.62.0':
-    resolution: {integrity: sha512-n8oxjeb5aIbPFEtmQxQYOLI0i9n5ySBEY/ZEHHZqKQSFnxio1rv6dthascc9dLuwrL0RC5mPCxB7vnAVGAYWAQ==}
-    engines: {node: ^12.22.0 || ^14.17.0 || >=16.0.0}
-    peerDependencies:
-      eslint: ^6.0.0 || ^7.0.0 || ^8.0.0
+  micromark-extension-gfm-footnote@2.1.0:
+    resolution: {integrity: sha512-/yPhxI1ntnDNsiHtzLKYnE3vf9JZ6cAisqVDauhp4CEHxlb4uoOTxOCJ+9s51bIB8U1N1FJ1RXOKTIlD5B/gqw==}
 
-  '@typescript-eslint/utils@7.18.0':
-    resolution: {integrity: sha512-kK0/rNa2j74XuHVcoCZxdFBMF+aq/vH83CXAOHieC+2Gis4mF8jJXT5eAfyD3K0sAxtPuwxaIOIOvhwzVDt/kw==}
-    engines: {node: ^18.18.0 || >=20.0.0}
-    peerDependencies:
-      eslint: ^8.56.0
+  micromark-extension-gfm-strikethrough@2.1.0:
+    resolution: {integrity: sha512-ADVjpOOkjz1hhkZLlBiYA9cR2Anf8F4HqZUO6e5eDcPQd0Txw5fxLzzxnEkSkfnD0wziSGiv7sYhk/ktvbf1uw==}
 
-  '@typescript-eslint/visitor-keys@5.62.0':
-    resolution: {integrity: sha512-07ny+LHRzQXepkGg6w0mFY41fVUNBrL2Roj/++7V1txKugfjm/Ci/qSND03r2RhlJhJYMcTn9AhhSSqQp0Ysyw==}
-    engines: {node: ^12.22.0 || ^14.17.0 || >=16.0.0}
+  micromark-extension-gfm-table@2.1.2:
+    resolution: {integrity: sha512-pRzm4kDTu0MjlmBkxmS9yYhw60nncfcEwu9NNdPFSQEFXS95ZKyIIyTSHu/o3ReBUrLKYEq+7YaXCRn/bPB4MA==}
 
-  '@typescript-eslint/visitor-keys@7.18.0':
-    resolution: {integrity: sha512-cDF0/Gf81QpY3xYyJKDV14Zwdmid5+uuENhjH2EqFaF0ni+yAyq/LzMaIJdhNJXZI7uLzwIlA+V7oWoyn6Curg==}
-    engines: {node: ^18.18.0 || >=20.0.0}
+  micromark-extension-gfm-tagfilter@2.0.0:
+    resolution: {integrity: sha512-xHlTOmuCSotIA8TW1mDIM6X2O1SiX5P9IuDtqGonFhEK0qgRI4yeC6vMxEV2dgyr2TiD+2PQ10o+cOhdVAcwfg==}
 
-  '@ungap/structured-clone@1.3.2':
-    resolution: {integrity: sha512-5jsZFwgR5rTdKwidH9Qmat75RKwqfpKlWWB1frDkljN127mwqBu8K0PYo7/hFpF03IEJpfVPpCQDY/eDx3iHvA==}
+  micromark-extension-gfm-task-list-item@2.1.0:
+    resolution: {integrity: sha512-qIBZhqxqI6fjLDYFTBIa4eivDMnP+OZqsNwmQ3xNLE4Cxwc+zfQEfbs6tzAo2Hjq+bh6q5F+Z8/cksrLFYWQQw==}
 
-  '@upsetjs/venn.js@2.0.0':
-    resolution: {integrity: sha512-WbBhLrooyePuQ1VZxrJjtLvTc4NVfpOyKx0sKqioq9bX1C1m7Jgykkn8gLrtwumBioXIqam8DLxp88Adbue6Hw==}
+  micromark-extension-gfm@3.0.0:
+    resolution: {integrity: sha512-vsKArQsicm7t0z2GugkCKtZehqUm31oeGBV/KVSorWSy8ZlNAv7ytjFhvaryUiCUJYqs+NoE6AFhpQvBTM6Q4w==}
 
-  '@webassemblyjs/ast@1.14.1':
-    resolution: {integrity: sha512-nuBEDgQfm1ccRp/8bCQrx1frohyufl4JlbMMZ4P1wpeOfDhF6FQkxZJ1b/e+PLwr6X1Nhw6OLme5usuBWYBvuQ==}
+  micromark-extension-math@3.1.0:
+    resolution: {integrity: sha512-lvEqd+fHjATVs+2v/8kg9i5Q0AP2k85H0WUOwpIVvUML8BapsMvh1XAogmQjOCsLpoKRCVQqEkQBB3NhVBcsOg==}
 
-  '@webassemblyjs/floating-point-hex-parser@1.13.2':
-    resolution: {integrity: sha512-6oXyTOzbKxGH4steLbLNOu71Oj+C8Lg34n6CqRvqfS2O71BxY6ByfMDRhBytzknj9yGUPVJ1qIKhRlAwO1AovA==}
+  micromark-extension-mdx-expression@3.0.1:
+    resolution: {integrity: sha512-dD/ADLJ1AeMvSAKBwO22zG22N4ybhe7kFIZ3LsDI0GlsNr2A3KYxb0LdC1u5rj4Nw+CHKY0RVdnHX8vj8ejm4Q==}
 
-  '@webassemblyjs/helper-api-error@1.13.2':
-    resolution: {integrity: sha512-U56GMYxy4ZQCbDZd6JuvvNV/WFildOjsaWD3Tzzvmw/mas3cXzRJPMjP83JqEsgSbyrmaGjBfDtV7KDXV9UzFQ==}
+  micromark-extension-mdx-jsx@3.0.2:
+    resolution: {integrity: sha512-e5+q1DjMh62LZAJOnDraSSbDMvGJ8x3cbjygy2qFEi7HCeUT4BDKCvMozPozcD6WmOt6sVvYDNBKhFSz3kjOVQ==}
 
-  '@webassemblyjs/helper-buffer@1.14.1':
-    resolution: {integrity: sha512-jyH7wtcHiKssDtFPRB+iQdxlDf96m0E39yb0k5uJVhFGleZFoNw1c4aeIcVUPPbXUVJ94wwnMOAqUHyzoEPVMA==}
+  micromark-extension-mdx-md@2.0.0:
+    resolution: {integrity: sha512-EpAiszsB3blw4Rpba7xTOUptcFeBFi+6PY8VnJ2hhimH+vCQDirWgsMpz7w1XcZE7LVrSAUGb9VJpG9ghlYvYQ==}
 
-  '@webassemblyjs/helper-numbers@1.13.2':
-    resolution: {integrity: sha512-FE8aCmS5Q6eQYcV3gI35O4J789wlQA+7JrqTTpJqn5emA4U2hvwJmvFRC0HODS+3Ye6WioDklgd6scJ3+PLnEA==}
+  micromark-extension-mdxjs-esm@3.0.0:
+    resolution: {integrity: sha512-DJFl4ZqkErRpq/dAPyeWp15tGrcrrJho1hKK5uBS70BCtfrIFg81sqcTVu3Ta+KD1Tk5vAtBNElWxtAa+m8K9A==}
 
-  '@webassemblyjs/helper-wasm-bytecode@1.13.2':
-    resolution: {integrity: sha512-3QbLKy93F0EAIXLh0ogEVR6rOubA9AoZ+WRYhNbFyuB70j3dRdwH9g+qXhLAO0kiYGlg3TxDV+I4rQTr/YNXkA==}
+  micromark-extension-mdxjs@3.0.0:
+    resolution: {integrity: sha512-A873fJfhnJ2siZyUrJ31l34Uqwy4xIFmvPY1oj+Ean5PHcPBYzEsvqvWGaWcfEIr11O5Dlw3p2y0tZWpKHDejQ==}
 
-  '@webassemblyjs/helper-wasm-section@1.14.1':
-    resolution: {integrity: sha512-ds5mXEqTJ6oxRoqjhWDU83OgzAYjwsCV8Lo/N+oRsNDmx/ZDpqalmrtgOMkHwxsG0iI//3BwWAErYRHtgn0dZw==}
+  micromark-factory-destination@2.0.1:
+    resolution: {integrity: sha512-Xe6rDdJlkmbFRExpTOmRj9N3MaWmbAgdpSrBQvCFqhezUn4AHqJHbaEnfbVYYiexVSs//tqOdY/DxhjdCiJnIA==}
 
-  '@webassemblyjs/ieee754@1.13.2':
-    resolution: {integrity: sha512-4LtOzh58S/5lX4ITKxnAK2USuNEvpdVV9AlgGQb8rJDHaLeHciwG4zlGr0j/SNWlr7x3vO1lDEsuePvtcDNCkw==}
+  micromark-factory-label@2.0.1:
+    resolution: {integrity: sha512-VFMekyQExqIW7xIChcXn4ok29YE3rnuyveW3wZQWWqF4Nv9Wk5rgJ99KzPvHjkmPXF93FXIbBp6YdW3t71/7Vg==}
 
-  '@webassemblyjs/leb128@1.13.2':
-    resolution: {integrity: sha512-Lde1oNoIdzVzdkNEAWZ1dZ5orIbff80YPdHx20mrHwHrVNNTjNr8E3xz9BdpcGqRQbAEa+fkrCb+fRFTl/6sQw==}
+  micromark-factory-mdx-expression@2.0.3:
+    resolution: {integrity: sha512-kQnEtA3vzucU2BkrIa8/VaSAsP+EJ3CKOvhMuJgOEGg9KDC6OAY6nSnNDVRiVNRqj7Y4SlSzcStaH/5jge8JdQ==}
 
-  '@webassemblyjs/utf8@1.13.2':
-    resolution: {integrity: sha512-3NQWGjKTASY1xV5m7Hr0iPeXD9+RDobLll3T9d2AO+g3my8xy5peVyjSag4I50mR1bBSN/Ct12lo+R9tJk0NZQ==}
+  micromark-factory-space@2.1.0:
+    resolution: {integrity: sha512-fS8hnLIjnjvdQIj39Geug8wWsR0HrYZ43KShKxNfwT7t2LOHo/LbWZEzEaSOjwtjdCsjoE6syHhonEzW0zv0+Q==}
 
-  '@webassemblyjs/wasm-edit@1.14.1':
-    resolution: {integrity: sha512-RNJUIQH/J8iA/1NzlE4N7KtyZNHi3w7at7hDjvRNm5rcUXa00z1vRz3glZoULfJ5mpvYhLybmVcwcjGrC1pRrQ==}
+  micromark-factory-title@2.0.1:
+    resolution: {integrity: sha512-5bZ+3CjhAd9eChYTHsjy6TGxpOFSKgKKJPJxr293jTbfry2KDoWkhBb6TcPVB4NmzaPhMs1Frm9AZH7OD4Cjzw==}
 
-  '@webassemblyjs/wasm-gen@1.14.1':
-    resolution: {integrity: sha512-AmomSIjP8ZbfGQhumkNvgC33AY7qtMCXnN6bL2u2Js4gVCg8fp735aEiMSBbDR7UQIj90n4wKAFUSEd0QN2Ukg==}
+  micromark-factory-whitespace@2.0.1:
+    resolution: {integrity: sha512-Ob0nuZ3PKt/n0hORHyvoD9uZhr+Za8sFoP+OnMcnWK5lngSzALgQYKMr9RJVOWLqQYuyn6ulqGWSXdwf6F80lQ==}
 
-  '@webassemblyjs/wasm-opt@1.14.1':
-    resolution: {integrity: sha512-PTcKLUNvBqnY2U6E5bdOQcSM+oVP/PmrDY9NzowJjislEjwP/C4an2303MCVS2Mg9d3AJpIGdUFIQQWbPds0Sw==}
+  micromark-util-character@2.1.1:
+    resolution: {integrity: sha512-wv8tdUTJ3thSFFFJKtpYKOYiGP2+v96Hvk4Tu8KpCAsTMs6yi+nVmGh1syvSCsaxz45J6Jbw+9DD6g97+NV67Q==}
 
-  '@webassemblyjs/wasm-parser@1.14.1':
-    resolution: {integrity: sha512-JLBl+KZ0R5qB7mCnud/yyX08jWFw5MsoalJ1pQ4EdFlgj9VdXKGuENGsiCIjegI1W7p91rUlcB/LB5yRJKNTcQ==}
+  micromark-util-chunked@2.0.1:
+    resolution: {integrity: sha512-QUNFEOPELfmvv+4xiNg2sRYeS/P84pTW0TCgP5zc9FpXetHY0ab7SxKyAQCNCc1eK0459uoLI1y5oO5Vc1dbhA==}
 
-  '@webassemblyjs/wast-printer@1.14.1':
-    resolution: {integrity: sha512-kPSSXE6De1XOR820C90RIo2ogvZG+c3KiHzqUoO/F34Y2shGzesfqv7o57xrxovZJH/MetF5UjroJ/R/3isoiw==}
+  micromark-util-classify-character@2.0.1:
+    resolution: {integrity: sha512-K0kHzM6afW/MbeWYWLjoHQv1sgg2Q9EccHEDzSkxiP/EaagNzCm7T/WMKZ3rjMbvIpvBiZgwR3dKMygtA4mG1Q==}
 
-  '@xobotyi/scrollbar-width@1.9.5':
-    resolution: {integrity: sha512-N8tkAACJx2ww8vFMneJmaAgmjAG1tnVBZJRLRcx061tmsLRZHSEZSLuGWnwPtunsSLvSqXQ2wfp7Mgqg1I+2dQ==}
+  micromark-util-combine-extensions@2.0.1:
+    resolution: {integrity: sha512-OnAnH8Ujmy59JcyZw8JSbK9cGpdVY44NKgSM7E9Eh7DiLS2E9RNQf0dONaGDzEG9yjEl5hcqeIsj4hfRkLH/Bg==}
 
-  '@xtuc/ieee754@1.2.0':
-    resolution: {integrity: sha512-DX8nKgqcGwsc0eJSqYt5lwP4DH5FlHnmuWWBRy7X0NcaGR0ZtuyeESgMwTYVEtxmsNGY+qit4QYT/MIYTOTPeA==}
+  micromark-util-decode-numeric-character-reference@2.0.2:
+    resolution: {integrity: sha512-ccUbYk6CwVdkmCQMyr64dXz42EfHGkPQlBj5p7YVGzq8I7CtjXZJrubAYezf7Rp+bjPseiROqe7G6foFd+lEuw==}
 
-  '@xtuc/long@4.2.2':
-    resolution: {integrity: sha512-NuHqBY1PB/D8xU6s/thBgOAiAP7HOYDQ32+BFZILJ8ivkUkAHQnWfn6WhL79Owj1qmUnoN/YPhktdIoucipkAQ==}
+  micromark-util-decode-string@2.0.1:
+    resolution: {integrity: sha512-nDV/77Fj6eH1ynwscYTOsbK7rR//Uj0bZXBwJZRfaLEJ1iGBR6kIfNmlNqaqJf649EP0F3NWNdeJi03elllNUQ==}
 
-  accepts@1.3.8:
-    resolution: {integrity: sha512-PYAthTa2m2VKxuvSD3DPC/Gy+U+sOA1LAuT8mkmRuvw+NACSaeXEQ+NHcVF7rONl6qcaxV3Uuemwawk+7+SJLw==}
-    engines: {node: '>= 0.6'}
+  micromark-util-edit-map@1.0.0:
+    resolution: {integrity: sha512-Pa2ljlsEL6sVwFaYeyrOLSYbQt73JvGbPOYFq+9AElXiSnfI5Q4465RRZ1sHv7lDjDOnGRDDaqPXqClqWK/q1Q==}
 
-  acorn-import-phases@1.0.4:
-    resolution: {integrity: sha512-wKmbr/DDiIXzEOiWrTTUcDm24kQ2vGfZQvM2fwg2vXqR5uW6aapr7ObPtj1th32b9u90/Pf4AItvdTh42fBmVQ==}
-    engines: {node: '>=10.13.0'}
-    peerDependencies:
-      acorn: ^8.14.0
+  micromark-util-encode@2.0.1:
+    resolution: {integrity: sha512-c3cVx2y4KqUnwopcO9b/SCdo2O67LwJJ/UyqGfbigahfegL9myoEFoDYZgkT7f36T0bLrM9hZTAaAyH+PCAXjw==}
 
-  acorn-jsx@5.3.2:
-    resolution: {integrity: sha512-rq9s+JNhf0IChjtDXxllJ7g41oZk5SlXtp0LHwyA5cejwn7vKmKp4pPri6YEePv2PU65sAsegbXtIinmDFDXgQ==}
-    peerDependencies:
-      acorn: ^6.0.0 || ^7.0.0 || ^8.0.0
+  micromark-util-events-to-acorn@2.0.3:
+    resolution: {integrity: sha512-jmsiEIiZ1n7X1Rr5k8wVExBQCg5jy4UXVADItHmNk1zkwEVhBuIUKRu3fqv+hs4nxLISi2DQGlqIOGiFxgbfHg==}
 
-  acorn-walk@8.3.5:
-    resolution: {integrity: sha512-HEHNfbars9v4pgpW6SO1KSPkfoS0xVOM/9UzkJltjlsHZmJasxg8aXkuZa7SMf8vKGIBhpUsPluQSqhJFCqebw==}
-    engines: {node: '>=0.4.0'}
+  micromark-util-html-tag-name@2.0.1:
+    resolution: {integrity: sha512-2cNEiYDhCWKI+Gs9T0Tiysk136SnR13hhO8yW6BGNyhOC4qYFnwF1nKfD3HFAIXA5c45RrIG1ub11GiXeYd1xA==}
 
-  acorn@8.16.0:
-    resolution: {integrity: sha512-UVJyE9MttOsBQIDKw1skb9nAwQuR5wuGD3+82K6JgJlm/Y+KI92oNsMNGZCYdDsVtRHSak0pcV5Dno5+4jh9sw==}
-    engines: {node: '>=0.4.0'}
-    hasBin: true
+  micromark-util-normalize-identifier@2.0.1:
+    resolution: {integrity: sha512-sxPqmo70LyARJs0w2UclACPUUEqltCkJ6PhKdMIDuJ3gSf/Q+/GIe3WKl0Ijb/GyH9lOpUkRAO2wp0GVkLvS9Q==}
 
-  acorn@8.17.0:
-    resolution: {integrity: sha512-xRQbDb9BnwDafYNn6Vwl839DYVjqXYb1XVGtWAZ1kcDc6iwAL4hg3B1dZlRiuENFeO2H53gFG3in621AdERVAg==}
-    engines: {node: '>=0.4.0'}
-    hasBin: true
+  micromark-util-resolve-all@2.0.1:
+    resolution: {integrity: sha512-VdQyxFWFT2/FGJgwQnJYbe1jjQoNTS4RjglmSjTUlpUMa95Htx9NHeYW4rGDJzbjvCsl9eLjMQwGeElsqmzcHg==}
 
-  address@1.2.2:
-    resolution: {integrity: sha512-4B/qKCfeE/ODUaAUpSwfzazo5x29WD4r3vXiWsB7I2mSDAihwEqKO+g8GELZUQSSAo5e1XTYh3ZVfLyxBc12nA==}
-    engines: {node: '>= 10.0.0'}
+  micromark-util-sanitize-uri@2.0.1:
+    resolution: {integrity: sha512-9N9IomZ/YuGGZZmQec1MbgxtlgougxTodVwDzzEouPKo3qFWvymFHWcnDi2vzV1ff6kas9ucW+o3yzJK9YB1AQ==}
 
-  aggregate-error@3.1.0:
-    resolution: {integrity: sha512-4I7Td01quW/RpocfNayFdFVk1qSuoh0E7JrbRJ16nH01HhKFQ88INq9Sd+nd72zqRySlr9BmDA8xlEJ6vJMrYA==}
-    engines: {node: '>=8'}
+  micromark-util-subtokenize@2.1.0:
+    resolution: {integrity: sha512-XQLu552iSctvnEcgXw6+Sx75GflAPNED1qx7eBJ+wydBb2KCbRZe+NwvIEEMM83uml1+2WSXpBAcp9IUCgCYWA==}
 
-  ajv-draft-04@1.0.0:
-    resolution: {integrity: sha512-mv00Te6nmYbRp5DCwclxtt7yV/joXJPGS7nM+97GdxvuttCOfgI3K4U25zboyeX0O+myI8ERluxQe5wljMmVIw==}
-    peerDependencies:
-      ajv: ^8.5.0
-    peerDependenciesMeta:
-      ajv:
-        optional: true
+  micromark-util-symbol@2.0.1:
+    resolution: {integrity: sha512-vs5t8Apaud9N28kgCrRUdEed4UJ+wWNvicHLPxCa9ENlYuAY31M0ETy5y1vA33YoNPDFTghEbnh6efaE8h4x0Q==}
 
-  ajv-formats@2.1.1:
-    resolution: {integrity: sha512-Wx0Kx52hxE7C18hkMEggYlEifqWZtYaRgouJor+WMdPnQyEK13vgEWyVNup7SoeeoLMsr4kf5h6dOW11I15MUA==}
-    peerDependencies:
-      ajv: ^8.0.0
-    peerDependenciesMeta:
-      ajv:
-        optional: true
+  micromark-util-types@2.0.3:
+    resolution: {integrity: sha512-oxB2Ik03hI0gv+VNn9tnh1t1YEe9MDPptViAEgfdf3YQHsn0pzGTgCdlSCJXcwhqm8phaEuM7zeEu3QQzVBrPg==}
 
-  ajv-formats@3.0.1:
-    resolution: {integrity: sha512-8iUql50EUR+uUcdRQ3HDqa6EVyo3docL8g5WJ3FNcWmu62IbkGUue/pEyLBW8VGKKucTPgqeks4fIU1DA4yowQ==}
-    peerDependencies:
-      ajv: ^8.0.0
-    peerDependenciesMeta:
-      ajv:
-        optional: true
+  micromark@4.0.3:
+    resolution: {integrity: sha512-oGYfQzHSG5dOMovQcJ3fyTmZlWAWpi0XA0sJwJs+i6OT88o1+Jtw/8z0CmdowSLxGhhFK89rQ/oXph/wN02PNw==}
 
-  ajv-keywords@3.5.2:
-    resolution: {integrity: sha512-5p6WTN0DdTGVQk6VjcEju19IgaHudalcfabD7yhDGeA6bcQnmL+CpveLJq/3hvfwd1aof6L386Ougkx6RfyMIQ==}
-    peerDependencies:
-      ajv: ^6.9.1
+  micromatch@4.0.8:
+    resolution: {integrity: sha512-PXwfBhYu0hBCPw8Dn0E+WDYb7af3dSLVWKi3HGv84IdF4TyFoC0ysxFd0Goxw7nSv4T/PzEJQxsYsEiFCKo2BA==}
+    engines: {node: '>=8.6'}
 
-  ajv-keywords@5.1.0:
-    resolution: {integrity: sha512-YCS/JNFAUyr5vAuhk1DWm1CBxRHW9LbJ2ozWeemrIqpbsqKjHVxYPyi5GC0rjZIT5JxJ3virVTS8wk4i/Z+krw==}
-    peerDependencies:
-      ajv: ^8.8.2
+  mime-db@1.52.0:
+    resolution: {integrity: sha512-sPU4uV7dYlvtWJxwwxHD0PuihVNiE7TyAbQ5SWxDCB9mUYvOgroQOwYQQOKPJ8CIbE+1ETVlOoK1UC2nU3gYvg==}
+    engines: {node: '>= 0.6'}
 
-  ajv@6.15.0:
-    resolution: {integrity: sha512-fgFx7Hfoq60ytK2c7DhnF8jIvzYgOMxfugjLOSMHjLIPgenqa7S7oaagATUq99mV6IYvN2tRmC0wnTYX6iPbMw==}
+  mime-types@2.1.35:
+    resolution: {integrity: sha512-ZDY+bPm5zTTF+YpCrAU9nK0UgICYPT0QtT1NZWFv4s++TNkcgVaT0g6+4R2uI4MjQjzysHB1zxuWL50hzaeXiw==}
+    engines: {node: '>= 0.6'}
 
-  ajv@8.20.0:
-    resolution: {integrity: sha512-Thbli+OlOj+iMPYFBVBfJ3OmCAnaSyNn4M1vz9T6Gka5Jt9ba/HIR56joy65tY6kx/FCF5VXNB819Y7/GUrBGA==}
+  mime@1.6.0:
+    resolution: {integrity: sha512-x0Vn8spI+wuJ1O6S7gnbaQg8Pxh4NNHb7KSINmEWKiPE4RKOplvijn+NkmYmmRgP68mc70j2EbeTFRsrswaQeg==}
+    engines: {node: '>=4'}
+    hasBin: true
 
-  algoliasearch-helper@3.29.1:
-    resolution: {integrity: sha512-6ck2YFudF2Pje7szQoPBiRFTGfd+1I+0I/WfLPGn0bj1kvrFoOQmNyedNiDxTk3/r4IfSLDYk+RA4G7u8H6+yA==}
-    peerDependencies:
-      algoliasearch: '>= 3.1 < 6'
+  mimic-fn@2.1.0:
+    resolution: {integrity: sha512-OqbOk5oEQeAZ8WXWydlu9HJjz9WVdEIvamMCcXmuqUYjTknH/sqsWvhQ3vgwKFRR1HpjvNBKQ37nbJgYzGqGcg==}
+    engines: {node: '>=6'}
 
-  algoliasearch@5.53.0:
-    resolution: {integrity: sha512-OGW1q6b91CRSSeiOnM8LxuR5NYJ2esvw66jUZ4IIvdv+ItNkx3pwLuyR+jaCdbGee4ov5WgUnyPryyh11xvByQ==}
-    engines: {node: '>= 14.0.0'}
+  mimic-response@3.1.0:
+    resolution: {integrity: sha512-z0yWI+4FDrrweS8Zmt4Ej5HdJmky15+L2e6Wgn3+iK5fWzb6T3fhNFq2+MeTRb064c6Wr4N/wv0DzQTjNzHNGQ==}
+    engines: {node: '>=10'}
 
-  allof-merge@0.6.8:
-    resolution: {integrity: sha512-RJrHVDqITsU1kjE2L7s1hy4AYZSTlO1m9jTleYhVCEOfOpbbygRGfcEgrp+bW3oX/PcMUwVkt6MSJyXoyI6lRA==}
+  mimic-response@4.0.0:
+    resolution: {integrity: sha512-e5ISH9xMYU0DzrT+jl8q2ze9D6eWBto+I8CNpe+VI+K2J/F/k3PdkdTdz4wvGVH4NTpo+NRYTVIuMQEMMcsLqg==}
+    engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
 
-  ansi-align@3.0.1:
-    resolution: {integrity: sha512-IOfwwBF5iczOjp/WeY4YxyjqAFMQoZufdQWDd19SEExbVLNXqvpzSJ/M7Za4/sCPmQ0+GRquoA7bGcINcxew6w==}
+  minimatch@3.1.5:
+    resolution: {integrity: sha512-VgjWUsnnT6n+NUk6eZq77zeFdpW2LWDzP6zFGrCbHXiYNul5Dzqk2HHQ5uFH2DNW5Xbp8+jVzaeNt94ssEEl4w==}
 
-  ansi-html-community@0.0.8:
-    resolution: {integrity: sha512-1APHAyr3+PCamwNw3bXCPp4HFLONZt/yIH0sZp0/469KWNTEy+qN5jQ3GVX6DMZ1UXAi34yVwtTeaG/HpBuuzw==}
-    engines: {'0': node >= 0.8.0}
-    hasBin: true
+  minimist@1.2.8:
+    resolution: {integrity: sha512-2yyAR8qBkN3YuheJanUpWC5U3bb5osDywNB8RzDVlDwDHbocAJveqqj1u8+SVD7jkWT4yvsHCpWqqWqAxb0zCA==}
 
-  ansi-regex@5.0.1:
-    resolution: {integrity: sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==}
-    engines: {node: '>=8'}
+  minipass@7.1.3:
+    resolution: {integrity: sha512-tEBHqDnIoM/1rXME1zgka9g6Q2lcoCkxHLuc7ODJ5BxbP5d4c2Z5cGgtXAku59200Cx7diuHTOYfSBD8n6mm8A==}
+    engines: {node: '>=16 || 14 >=14.17'}
 
-  ansi-regex@6.2.2:
-    resolution: {integrity: sha512-Bq3SmSpyFHaWjPk8If9yc6svM8c56dB5BAtW4Qbw5jHTwwXXcTLoRMkpDJp6VL0XzlWaCHTXrkFURMYmD0sLqg==}
-    engines: {node: '>=12'}
+  minizlib@3.1.0:
+    resolution: {integrity: sha512-KZxYo1BUkWD2TVFLr0MQoM8vUUigWD3LlD83a/75BqC+4qE0Hb1Vo5v1FgcfaNXvfXzr+5EhQ6ing/CaBijTlw==}
+    engines: {node: '>= 18'}
 
-  ansi-styles@4.3.0:
-    resolution: {integrity: sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==}
-    engines: {node: '>=8'}
+  mint@4.2.1062:
+    resolution: {integrity: sha512-UuwWzWe6aYirBUZwRRylQULThPDShTVnMUtstOWkjlKEf84nYg0GJ3C6qgrHq/Q8ZWW+WhhMC4CswaETSEpCUQ==}
+    engines: {node: '>=18.0.0'}
+    hasBin: true
 
-  ansi-styles@6.2.3:
-    resolution: {integrity: sha512-4Dj6M28JB+oAH8kFkTLUo+a2jwOFkuqb3yucU0CANcRRUbxS0cP0nZYCGjcc3BNXwRIsUVmDGgzawme7zvJHvg==}
-    engines: {node: '>=12'}
+  mkdirp-classic@0.5.3:
+    resolution: {integrity: sha512-gKLcREMhtuZRwRAfqP3RFW+TK4JqApVBtOIftVgjuABpAtpxhPGaDcfvbhNvD0B8iD1oUr/txX35NjcaY6Ns/A==}
 
-  ansis@3.17.0:
-    resolution: {integrity: sha512-0qWUglt9JEqLFr3w1I1pbrChn1grhaiAR2ocX1PP/flRmxgtwTzPFFFnfIlD6aMOLQZgSuCRlidD70lvx8yhzg==}
-    engines: {node: '>=14'}
+  ms@2.0.0:
+    resolution: {integrity: sha512-Tpp60P6IUJDTuOq/5Z8cdskzJujfwqfOTkrwIwj7IRISpnkJnT6SyJ4PCPnGMoFjC9ddhal5KVIYtAt97ix05A==}
 
-  any-promise@1.3.0:
-    resolution: {integrity: sha512-7UvmKalWRt1wgjL1RrGxoSJW/0QZFIegpeGvZG9kjp8vrRu55XTHbwnqq2GpXm9uLbcuhxm3IqX9OB4MZR1b2A==}
+  ms@2.1.3:
+    resolution: {integrity: sha512-6FlzubTLZG3J2a/NVCAleEhjzq5oxgHyaCU9yYXvcLsvoVaHJq/s5xXI6/XXP6tz7R9xAOtHnSO/tXtF3WRTlA==}
 
-  anymatch@3.1.3:
-    resolution: {integrity: sha512-KMReFUr0B4t+D+OBkjR3KYqvocp2XaSzO55UcB6mgQMd3KbcE+mWTyvVV7D/zsdEbNnV6acZUutkiHQXvTr1Rw==}
-    engines: {node: '>= 8'}
+  mute-stream@2.0.0:
+    resolution: {integrity: sha512-WWdIxpyjEn+FhQJQQv9aQAYlHoNVdzIzUySNV1gHUPDSdZJ3yZn7pAAbQcV7B56Mvu881q9FZV+0Vx2xC44VWA==}
+    engines: {node: ^18.17.0 || >=20.5.0}
 
-  arg@5.0.2:
-    resolution: {integrity: sha512-PYjyFOLKQ9y57JvQ6QLo8dAgNqswh8M1RMJYdQduT6xbWSgK36P/Z/v+p888pM69jMMfS8Xd8F6I1kQ/I9HUGg==}
+  mz@2.7.0:
+    resolution: {integrity: sha512-z81GNO7nnYMEhrGh9LeymoE4+Yr0Wn5McHIZMK5cfQCl+NDX08sCZgUc9/6MHni9IWuFLm1Z3HTCXu2z9fN62Q==}
 
-  argparse@1.0.10:
-    resolution: {integrity: sha512-o5Roy6tNG4SL/FOkCAN6RzjiakZS25RLYFrcMttJqbdd8BWrnA+fGz57iN5Pb06pvBGvl5gQ0B48dJlslXvoTg==}
+  nanoid@3.3.20:
+    resolution: {integrity: sha512-uKdg2G3GNCKQn9byYOpxbGqrT2fGO5KRt5J/8b3pok8rT6qxGWF6hxMyJiEYtAf+FVyYuD9hRaDqX5uPFYJ4ZQ==}
+    engines: {node: ^10 || ^12 || ^13.7 || ^14 || >=15.0.1}
+    hasBin: true
 
-  argparse@2.0.1:
-    resolution: {integrity: sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q==}
+  napi-build-utils@2.0.0:
+    resolution: {integrity: sha512-GEbrYkbfF7MoNaoh2iGG84Mnf/WZfB0GdGEsM8wz7Expx/LlWf5U8t9nvJKXSp3qr5IsEbK04cBGhol/KwOsWA==}
 
-  aria-hidden@1.2.6:
-    resolution: {integrity: sha512-ik3ZgC9dY/lYVVM++OISsaYDeg1tb0VtP5uL3ouh1koGOaUMDPpbFIei4JkFimWUFPn90sbMNMXQAIVOlnYKJA==}
-    engines: {node: '>=10'}
+  negotiator@0.6.3:
+    resolution: {integrity: sha512-+EUsqGPLsM+j/zdChZjsnX51g4XrHFOIXwfnCVPGlQk/k5giakcKsuxCObBRu6DSm9opw/O6slWbJdghQM4bBg==}
+    engines: {node: '>= 0.6'}
 
-  array-flatten@1.1.1:
-    resolution: {integrity: sha512-PCVAQswWemu6UdxsDFFX/+gVeYqKAod3D3UVm91jHwynguOwAvYPhx8nNlM++NqRcK6CxxpUafjmhIdKiHibqg==}
+  neotraverse@0.6.18:
+    resolution: {integrity: sha512-Z4SmBUweYa09+o6pG+eASabEpP6QkQ70yHj351pQoEXIs8uHbaU2DWVmzBANKgflPa47A50PtB2+NgRpQvr7vA==}
+    engines: {node: '>= 10'}
 
-  array-union@2.1.0:
-    resolution: {integrity: sha512-HGyxoOTYUyCM6stUe6EJgnd4EoewAI7zMdfqO+kGjnlZmBDz/cR5pf8r/cR4Wq60sL/p0IkcjUEEPwS3GFrIyw==}
-    engines: {node: '>=8'}
+  next-mdx-remote-client@2.1.12:
+    resolution: {integrity: sha512-KDfhIk5aEM0kkZ0xQ8XBkmo4O5xmJeGWUomm40Ac/xhkt5sIDOTmTU/QFfmJGLJUJipD5o0BAHqVSIZKuXgNEw==}
+    engines: {node: '>=20.9.0'}
+    peerDependencies:
+      react: '>= 19.1.0'
+      react-dom: '>= 19.1.0'
 
-  asn1js@3.0.10:
-    resolution: {integrity: sha512-S2s3aOytiKdFRdulw2qPE51MzjzVOisppcVv7jVFR+Kw0kxwvFrDcYA0h7Ndqbmj0HkMIXYWaoj7fli8kgx1eg==}
-    engines: {node: '>=12.0.0'}
+  nimma@0.2.3:
+    resolution: {integrity: sha512-1ZOI8J+1PKKGceo/5CT5GfQOG6H8I2BencSK06YarZ2wXwH37BSSUWldqJmMJYA5JfqDqffxDXynt6f11AyKcA==}
+    engines: {node: ^12.20 || >=14.13}
 
-  astring@1.9.0:
-    resolution: {integrity: sha512-LElXdjswlqjWrPpJFg1Fx4wpkOCxj1TDHlSV4PlaRxHGWko024xICaa97ZkMfs6DRKlCguiAI+rbXv5GWwXIkg==}
-    hasBin: true
+  nlcst-to-string@4.0.0:
+    resolution: {integrity: sha512-YKLBCcUYKAg0FNlOBT6aI91qFmSiFKiluk655WzPF+DDMA02qIyy8uiRqI8QXtcFpEvll12LpL5MXqEmAZ+dcA==}
+
+  node-abi@3.99.0:
+    resolution: {integrity: sha512-lLdwkeg2XUVPTHqWjPltTxH81zbQNbUWC+AEb9ni50KjxkUzAAx1HGtMT21sbntzfUGfIphhcklvs3imJeqDXw==}
+    engines: {node: '>=10'}
 
-  async@3.2.6:
-    resolution: {integrity: sha512-htCUDlxyyCLMgaM3xXg0C0LW2xqfuQ6p05pCEIsXuyQ+a1koYKTuBMzRNwmybfLgvJDMd0r1LTn4+E0Ti6C2AA==}
+  node-addon-api@4.3.0:
+    resolution: {integrity: sha512-73sE9+3UaLYYFmDsFZnqCInzPyh3MqIwZO9cw58yIqAZhONrrabrYyYe3TuIqtIiOuTXVhsGau8hcrhhwSsDIQ==}
 
-  autoprefixer@10.5.0:
-    resolution: {integrity: sha512-FMhOoZV4+qR6aTUALKX2rEqGG+oyATvwBt9IIzVR5rMa2HRWPkxf+P+PAJLD1I/H5/II+HuZcBJYEFBpq39ong==}
-    engines: {node: ^10 || ^12 || >=14}
-    hasBin: true
+  node-fetch@2.6.7:
+    resolution: {integrity: sha512-ZjMPFEfVx5j+y2yF35Kzx5sF7kDzxuDj6ziH4FFbOp87zKDZNx8yExJIb05OGF4Nlt9IHFIMBkRl41VdvcNdbQ==}
+    engines: {node: 4.x || >=6.0.0}
     peerDependencies:
-      postcss: ^8.1.0
+      encoding: ^0.1.0
+    peerDependenciesMeta:
+      encoding:
+        optional: true
 
-  babel-loader@9.2.1:
-    resolution: {integrity: sha512-fqe8naHt46e0yIdkjUZYqddSXfej3AHajX+CSO5X7oy0EmPc6o5Xh+RClNoHjnieWz9AW4kZxW9yyFMhVB1QLA==}
-    engines: {node: '>= 14.15.0'}
+  node-fetch@2.7.0:
+    resolution: {integrity: sha512-c4FRfUm/dbcWZ7U+1Wq0AwCyFL+3nt2bEw05wfxSz+DWpWsitgmSgYmy2dQdWyKC1694ELPqMs/YzUSNozLt8A==}
+    engines: {node: 4.x || >=6.0.0}
     peerDependencies:
-      '@babel/core': ^7.12.0
-      webpack: '>=5'
+      encoding: ^0.1.0
+    peerDependenciesMeta:
+      encoding:
+        optional: true
 
-  babel-plugin-dynamic-import-node@2.3.3:
-    resolution: {integrity: sha512-jZVI+s9Zg3IqA/kdi0i6UDCybUI3aSBLnglhYbSSjKlV7yF1F/5LWv8MakQmvYpnbJDS6fcBL2KzHSxNCMtWSQ==}
+  non-error@0.1.0:
+    resolution: {integrity: sha512-TMB1uHiGsHRGv1uYclfhivcnf0/PdFp2pNqRxXjncaAsjYMoisaQJI+SSZCqRq+VliwRTC8tsMQfmrWjDMhkPQ==}
+    engines: {node: '>=20'}
 
-  babel-plugin-polyfill-corejs2@0.4.17:
-    resolution: {integrity: sha512-aTyf30K/rqAsNwN76zYrdtx8obu0E4KoUME29B1xj+B3WxgvWkp943vYQ+z8Mv3lw9xHXMHpvSPOBxzAkIa94w==}
-    peerDependencies:
-      '@babel/core': ^7.4.0 || ^8.0.0-0 <8.0.0
+  normalize-path@3.0.0:
+    resolution: {integrity: sha512-6eZs5Ls3WtCisHWp9S2GUy8dqkpGi4BVSz3GaqiE6ezub0512ESztXUwUB6C6IKbQkY2Pnb/mD4WYojCRwcwLA==}
+    engines: {node: '>=0.10.0'}
 
-  babel-plugin-polyfill-corejs3@0.13.0:
-    resolution: {integrity: sha512-U+GNwMdSFgzVmfhNm8GJUX88AadB3uo9KpJqS3FaqNIPKgySuvMb+bHPsOmmuWyIcuqZj/pzt1RUIUZns4y2+A==}
-    peerDependencies:
-      '@babel/core': ^7.4.0 || ^8.0.0-0 <8.0.0
+  normalize-url@8.1.1:
+    resolution: {integrity: sha512-JYc0DPlpGWB40kH5g07gGTrYuMqV653k3uBKY6uITPWds3M0ov3GaWGp9lbE3Bzngx8+XkfzgvASb9vk9JDFXQ==}
+    engines: {node: '>=14.16'}
 
-  babel-plugin-polyfill-corejs3@0.14.2:
-    resolution: {integrity: sha512-coWpDLJ410R781Npmn/SIBZEsAetR4xVi0SxLMXPaMO4lSf1MwnkGYMtkFxew0Dn8B3/CpbpYxN0JCgg8mn67g==}
-    peerDependencies:
-      '@babel/core': ^7.4.0 || ^8.0.0-0 <8.0.0
+  oauth4webapi@3.8.8:
+    resolution: {integrity: sha512-8N28E+a/oxfXWBgOMt+ZP/JUf/XR+IFbvkAEPP3gznXOMv9BpAAwiIj0TFNz3tGTPc0ZQ8zmWBNgN1nAys0gng==}
 
-  babel-plugin-polyfill-regenerator@0.6.8:
-    resolution: {integrity: sha512-M762rNHfSF1EV3SLtnCJXFoQbbIIz0OyRwnCmV0KPC7qosSfCO0QLTSuJX3ayAebubhE6oYBAYPrBA5ljowaZg==}
-    peerDependencies:
-      '@babel/core': ^7.4.0 || ^8.0.0-0 <8.0.0
+  object-assign@4.1.1:
+    resolution: {integrity: sha512-rJgTQnkUnH1sFw8yT6VSU3zD3sWmu6sZhIseY8VX+GRu3P6F7Fu+JNDoXfklElbLJSnc3FUQHVe4cU5hj+BcUg==}
+    engines: {node: '>=0.10.0'}
 
-  bail@1.0.5:
-    resolution: {integrity: sha512-xFbRxM1tahm08yHBP16MMjVUAvDaBMD38zsM9EMAUN61omwLmKlOpB/Zku5QkjZ8TZ4vn53pj+t518cH0S03RQ==}
+  object-hash@3.0.0:
+    resolution: {integrity: sha512-RSn9F68PjH9HqtltsSnqYC1XXoWe9Bju5+213R98cNGttag9q9yAOTzdbsqvIa7aNm5WffBZFpWYr2aWrklWAw==}
+    engines: {node: '>= 6'}
 
-  bail@2.0.2:
-    resolution: {integrity: sha512-0xO6mYd7JB2YesxDKplafRpsiOzPt9V02ddPCLbY1xYGPOX24NTyN50qnUxgCPcSoYMhKpAuBTjQoRZCAkUDRw==}
+  object-inspect@1.13.4:
+    resolution: {integrity: sha512-W67iLl4J2EXEGTbfeHCffrjDfitvLANg0UlX3wFUUSTx92KXRFegMHUVgSqE+wvhAbi4WqjGg9czysTV2Epbew==}
+    engines: {node: '>= 0.4'}
 
-  balanced-match@1.0.2:
-    resolution: {integrity: sha512-3oSeUO0TMV67hN1AmbXsK4yaqU7tjiHlbxRDZOpH0KW9+CeX4bRAaX0Anxt0tx2MrpRpWwQaPwIlISEJhYU5Pw==}
+  object-keys@1.1.1:
+    resolution: {integrity: sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==}
+    engines: {node: '>= 0.4'}
 
-  balanced-match@4.0.4:
-    resolution: {integrity: sha512-BLrgEcRTwX2o6gGxGOCNyMvGSp35YofuYzw9h1IMTRmKqttAZZVU67bdb9Pr2vUHA8+j3i2tJfjO6C6+4myGTA==}
-    engines: {node: 18 || 20 || >=22}
+  object.assign@4.1.7:
+    resolution: {integrity: sha512-nK28WOo+QIjBkDduTINE4JkF/UJJKyf2EJxvJKfblDpyg0Q+pkOHNTL0Qwy6NP6FhE/EnzV73BxxqcJaXY9anw==}
+    engines: {node: '>= 0.4'}
 
-  base64-js@1.5.1:
-    resolution: {integrity: sha512-AKpaYlHn8t4SVbOHCy+b5+KKgvR4vrsD8vbvrbiQJps7fKDTkjkDry6ji0rUJjC0kzbNePLwzxq8iypo41qeWA==}
+  on-finished@2.4.1:
+    resolution: {integrity: sha512-oVlzkg3ENAhCk2zdv7IJwd/QUD4z2RxRwpkcGY8psCVcCYZNq4wYnVWALHM+brtuJjePWiYF/ClmuDr8Ch5+kg==}
+    engines: {node: '>= 0.8'}
 
-  baseline-browser-mapping@2.10.35:
-    resolution: {integrity: sha512-honAfLBde0HAFLdNyBEfuuENkF6zR+ozxqxa/2zJKHBe1qzLqyTSeRKpdPEHAP03rlDGyQOPnCSxnVpVqQo9Mg==}
-    engines: {node: '>=6.0.0'}
-    hasBin: true
+  once@1.4.0:
+    resolution: {integrity: sha512-lNaJgI+2Q5URQBkccEKHTQOPaXdUxnZZElQTZY0MFUAuaEqe1E+Nyvgdz/aIyNi6Z9MzO5dv1H8n58/GELp3+w==}
 
-  batch@0.6.1:
-    resolution: {integrity: sha512-x+VAiMRL6UPkx+kudNvxTl6hB2XNNCG2r+7wixVfIYwu/2HKRXimwQyaumLjMveWvT2Hkd/cAJw+QBMfJ/EKVw==}
+  onetime@5.1.2:
+    resolution: {integrity: sha512-kbpaSSGJTWdAY5KPVeMOKXSrPtr8C8C7wodJbcsd51jRnmD+GZu8Y0VoU6Dm5Z4vWr0Ig/1NKuWRKf7j5aaYSg==}
+    engines: {node: '>=6'}
 
-  big.js@5.2.2:
-    resolution: {integrity: sha512-vyL2OymJxmarO8gxMr0mhChsO9QGwhynfuu4+MHTAW6czfq9humCB7rKpUjDd9YUiDPU4mzpyupFSvOClAwbmQ==}
+  oniguruma-parser@0.12.2:
+    resolution: {integrity: sha512-6HVa5oIrgMC6aA6WF6XyyqbhRPJrKR02L20+2+zpDtO5QAzGHAUGw5TKQvwi5vctNnRHkJYmjAhRVQF2EKdTQw==}
 
-  binary-extensions@2.3.0:
-    resolution: {integrity: sha512-Ceh+7ox5qe7LJuLHoY0feh3pHuUDHAcRUeyL2VYghZwfpkNIy/+8Ocg0a3UuSoYzavmylwuLWQOf3hl0jjMMIw==}
-    engines: {node: '>=8'}
+  oniguruma-to-es@4.3.6:
+    resolution: {integrity: sha512-csuQ9x3Yr0cEIs/Zgx/OEt9iBw9vqIunAPQkx19R/fiMq2oGVTgcMqO/V3Ybqefr1TBvosI6jU539ksaBULJyA==}
 
-  body-parser@1.20.5:
-    resolution: {integrity: sha512-3grm+/2tUOvu2cjJkvsIxrv/wVpfXQW4PsQHYm7yk4vfpu7Ekl6nEsYBoJUL6qDwZUx8wUhQ8tR2qz+ad9c9OA==}
-    engines: {node: '>= 0.8', npm: 1.2.8000 || >= 1.4.16}
+  open@8.4.2:
+    resolution: {integrity: sha512-7x81NCL719oNbsq/3mh+hVrAWmFuEYUqrq/Iw3kUzH8ReypT9QQ0BLoJS7/G9k6N81XjW4qHWtjWwe/9eLy1EQ==}
+    engines: {node: '>=12'}
 
-  bonjour-service@1.4.0:
-    resolution: {integrity: sha512-fGQtj1qdR9vIKjFiWPQd52qIqwjaYqhcI40JEiDuvlZ86E7ZBPBwY9fPgHy9r2rYGIjiRfctNPYz6OQU73ww2w==}
+  openapi-types@12.1.3:
+    resolution: {integrity: sha512-N4YtSYJqghVu4iek2ZUvcN/0aqH1kRDuNqzcycDxhOUpg7GdvLa2F3DgS6yBNhInhv2r/6I0Flkn7CqL8+nIcw==}
 
-  boolbase@1.0.0:
-    resolution: {integrity: sha512-JZOSA7Mo9sNGB8+UjSgzdLtokWAky1zbztM3WRLCbZ70/3cTANmQmOdR7y2g+J0e2WXywy1yS468tY+IruqEww==}
+  openid-client@6.8.2:
+    resolution: {integrity: sha512-uOvTCndr4udZsKihJ68H9bUICrriHdUVJ6Az+4Ns6cW55rwM5h0bjVIzDz2SxgOI84LKjFyjOFvERLzdTUROGA==}
 
-  boxen@6.2.1:
-    resolution: {integrity: sha512-H4PEsJXfFI/Pt8sjDWbHlQPx4zL/bvSQjcilJmaulGt5mLDorHOHpmdXAJcBcmru7PhYSp/cDMWRko4ZUMFkSw==}
-    engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
+  orderedmap@2.1.1:
+    resolution: {integrity: sha512-TvAWxi0nDe1j/rtMcWcIj94+Ffe6n7zhow33h40SKxmsmozs6dz/e+EajymfoFcHd7sxNn8yHM8839uixMOV6g==}
 
-  boxen@7.1.1:
-    resolution: {integrity: sha512-2hCgjEmP8YLWQ130n2FerGv7rYpfBmnmp9Uy2Le1vge6X3gZIfSmEzP5QTDElFxcvVcXlEn8Aq6MU/PZygIOog==}
-    engines: {node: '>=14.16'}
+  own-keys@1.0.2:
+    resolution: {integrity: sha512-19YVAg7T+WTrxggPukVq7DjTv6+PJ867TmhCvBsYwmbFCsZd344rq2Ld1p0wo8f8Qrrhgp82c6FJRqdXWtSEhg==}
+    engines: {node: '>= 0.4'}
 
-  brace-expansion@1.1.15:
-    resolution: {integrity: sha512-EwOCDEex4quD37XhqM3omwtMoJjr//isUZz1JopUNWms+4Z2ViyM/k1YIRePpoVNnQhENnxtFjLaxNHrT7xIUg==}
+  p-any@4.0.0:
+    resolution: {integrity: sha512-S/B50s+pAVe0wmEZHmBs/9yJXeZ5KhHzOsgKzt0hRdgkoR3DxW9ts46fcsWi/r3VnzsnkKS7q4uimze+zjdryw==}
+    engines: {node: '>=12.20'}
 
-  brace-expansion@2.1.1:
-    resolution: {integrity: sha512-WR1cURNjuvBLMZBMbqM0UoE+WAfdUcEV1ccD8PVBVOI+Z3ND4+SZbN8RsfT2bMuG1qwz5RFvPukSZm5fF2D5eA==}
+  p-cancelable@3.0.0:
+    resolution: {integrity: sha512-mlVgR3PGuzlo0MmTdk4cXqXWlwQDLnONTAg6sm62XkMJEiRxN3GL3SffkYvqwonbkJBcrI7Uvv5Zh9yjvn2iUw==}
+    engines: {node: '>=12.20'}
 
-  brace-expansion@5.0.7:
-    resolution: {integrity: sha512-7oFy703dxfY3/NLxC1fh2SUCQ0H9rmAY+5EpDVfXjUTTs+HEwR2nYaqLv+GWcTsumwxPfiz6CzCNkwXwBUwqCA==}
-    engines: {node: 18 || 20 || >=22}
+  p-some@6.0.0:
+    resolution: {integrity: sha512-CJbQCKdfSX3fIh8/QKgS+9rjm7OBNUTmwWswAFQAhc8j1NR1dsEDETUEuVUtQHZpV+J03LqWBEwvu0g1Yn+TYg==}
+    engines: {node: '>=12.20'}
 
-  braces@3.0.3:
-    resolution: {integrity: sha512-yQbXgO/OSZVD2IsiLlro+7Hf6Q18EJrKSEsdoMzKePKXct3gvD8oLcOQdIzGupr5Fj+EDe8gO/lxc1BzfMpxvA==}
-    engines: {node: '>=8'}
+  p-timeout@5.1.0:
+    resolution: {integrity: sha512-auFDyzzzGZZZdHz3BtET9VEz0SE/uMEAx7uWfGPucfzEwwe/xH0iVeZibQmANYE/hp9T2+UUZT5m+BKyrDp3Ew==}
+    engines: {node: '>=12'}
 
-  browserslist@4.28.2:
-    resolution: {integrity: sha512-48xSriZYYg+8qXna9kwqjIVzuQxi+KYWp2+5nCYnYKPTr0LvD89Jqk2Or5ogxz0NUMfIjhh2lIUX/LyX9B4oIg==}
-    engines: {node: ^6 || ^7 || ^8 || ^9 || ^10 || ^11 || ^12 || >=13.7}
-    hasBin: true
+  pako@0.2.9:
+    resolution: {integrity: sha512-NUcwaKxUxWrZLpDG+z/xZaCgQITkA/Dv4V/T6bw7VON6l1Xz/VnrBqrYjZQ12TamKHzITTfOEIYUj48y2KXImA==}
 
-  buffer-from@1.1.2:
-    resolution: {integrity: sha512-E+XQCRwSbaaiChtv6k6Dwgc+bx+Bs6vuKJHHl5kox/BaKbhiXzqQOwK4cO22yElGp2OCmjwVhT3HmxgyPGnJfQ==}
+  parse-css-color@0.2.1:
+    resolution: {integrity: sha512-bwS/GGIFV3b6KS4uwpzCFj4w297Yl3uqnSgIPsoQkx7GMLROXfMnWvxfNkL0oh8HVhZA4hvJoEoEIqonfJ3BWg==}
 
-  buffer@6.0.3:
-    resolution: {integrity: sha512-FTiCpNxtwiZZHEZbcbTIcZjERVICn9yq/pDFkTl95/AxzD1naBctN7YO68riM/gLSDY7sdrMby8hofADYuuqOA==}
+  parse-entities@4.0.2:
+    resolution: {integrity: sha512-GG2AQYWoLgL877gQIKeRPGO1xF9+eG1ujIb5soS5gPvLQ1y2o8FL90w2QWNdf9I361Mpp7726c+lj3U0qK1uGw==}
 
-  bundle-name@4.1.0:
-    resolution: {integrity: sha512-tjwM5exMg6BGRI+kNmTntNsvdZS1X8BFYS6tnJ2hdH0kVxM6/eVZ2xy+FqStSWvYmtfFMDLIxurorHwDKfDz5Q==}
-    engines: {node: '>=18'}
+  parse-latin@7.0.0:
+    resolution: {integrity: sha512-mhHgobPPua5kZ98EF4HWiH167JWBfl4pvAIXXdbaVohtK7a6YBOy56kvhCqduqyo/f3yrHFWmqmiMg/BkBkYYQ==}
 
-  bytes@3.0.0:
-    resolution: {integrity: sha512-pMhOfFDPiv9t5jjIXkHosWmkSyQbvsgEVNkz0ERHbuLh2T/7j4Mqqpz523Fe8MVY89KC6Sh/QfS2sM+SjgFDcw==}
-    engines: {node: '>= 0.8'}
+  parse5@7.3.0:
+    resolution: {integrity: sha512-IInvU7fabl34qmi9gY8XOVxhYyMyuH2xUNpb2q8/Y+7552KlejkRvqvD19nMoUW/uQGGbqNpA6Tufu5FL5BZgw==}
 
-  bytes@3.1.2:
-    resolution: {integrity: sha512-/Nf7TyzTx6S3yRJObOAV7956r8cr2+Oj8AC5dt8wSP3BQAoeX58NoHyCU8P8zGkNXStjTSi6fzO6F0pBdcYbEg==}
+  parseurl@1.3.3:
+    resolution: {integrity: sha512-CiyeOxFT/JZyN5m0z9PfXw4SCBJ6Sygz1Dpl0wqjlhDEGGBP1GnsUVEL0p63hoG1fcj3fHynXi9NYO4nWOL+qQ==}
     engines: {node: '>= 0.8'}
 
-  bytestreamjs@2.0.1:
-    resolution: {integrity: sha512-U1Z/ob71V/bXfVABvNr/Kumf5VyeQRBEm6Txb0PQ6S7V5GpBM3w4Cbqz/xPDicR5tN0uvDifng8C+5qECeGwyQ==}
-    engines: {node: '>=6.0.0'}
+  patch-console@2.0.0:
+    resolution: {integrity: sha512-0YNdUceMdaQwoKce1gatDScmMo5pu/tfABfnzEqeG0gtTmd7mh/WcwgUjtAeOU7N8nFFlbQBnFK2gXW5fGvmMA==}
+    engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
 
-  cacheable-lookup@7.0.0:
-    resolution: {integrity: sha512-+qJyx4xiKra8mZrcwhjMRMUhD5NR1R8esPkzIYxX96JiecFoxAXFuz/GpR3+ev4PE1WamHip78wV0vcmPQtp8w==}
-    engines: {node: '>=14.16'}
+  path-expression-matcher@1.6.2:
+    resolution: {integrity: sha512-enSlaiat05iasnzmgNxRj8reFdj3puY2QpNgP1aPIaVfT6nn9ICuPoFlKHk8EN22HcwewshO+mN2DGbkCEOtqQ==}
+    engines: {node: '>=14.0.0'}
 
-  cacheable-request@10.2.14:
-    resolution: {integrity: sha512-zkDT5WAF4hSSoUgyfg5tFIxz8XQK+25W/TLVojJTMKBaxevLBBtLxgqguAuVQB8PVW79FVjHcU+GJ9tVbDZ9mQ==}
-    engines: {node: '>=14.16'}
+  path-is-absolute@1.0.1:
+    resolution: {integrity: sha512-AVbw3UJ2e9bq64vSaS9Am0fje1Pa8pbGqTTsmXfaIiMpnr5DlDhfJOuLj9Sf95ZPVDAUerDfEk88MPmPe7UCQg==}
+    engines: {node: '>=0.10.0'}
 
-  call-bind-apply-helpers@1.0.2:
-    resolution: {integrity: sha512-Sp1ablJ0ivDkSzjcaJdxEunN5/XvksFJ2sMBFfq6x0ryhQV/2b/KwFe21cMpmHtPOSij8K99/wSfoEuTObmuMQ==}
-    engines: {node: '>= 0.4'}
+  path-key@3.1.1:
+    resolution: {integrity: sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q==}
+    engines: {node: '>=8'}
 
-  call-bind@1.0.9:
-    resolution: {integrity: sha512-a/hy+pNsFUTR+Iz8TCJvXudKVLAnz/DyeSUo10I5yvFDQJBFU2s9uqQpoSrJlroHUKoKqzg+epxyP9lqFdzfBQ==}
-    engines: {node: '>= 0.4'}
+  path-parse@1.0.7:
+    resolution: {integrity: sha512-LDJzPVEEEPR+y48z93A0Ed0yXb8pAByGWo/k5YYdYgpY2/2EsOsksJrq7lOHxryrVOn1ejG6oAp8ahvOIQD8sw==}
 
-  call-bound@1.0.4:
-    resolution: {integrity: sha512-+ys997U96po4Kx/ABpBCqhA9EuxJaQWDQg7295H4hBphv3IZg0boBKuwYpt4YXp6MZ5AmZQnU/tyMTlRpaSejg==}
-    engines: {node: '>= 0.4'}
+  path-to-regexp@0.1.13:
+    resolution: {integrity: sha512-A/AGNMFN3c8bOlvV9RreMdrv7jsmF9XIfDeCd87+I8RNg6s78BhJxMu69NEMHBSJFxKidViTEdruRwEk/WIKqA==}
 
-  call-me-maybe@1.0.2:
-    resolution: {integrity: sha512-HpX65o1Hnr9HH25ojC1YGs7HCQLq0GCOibSaWER0eNpgJ/Z1MZv2mTc7+xh6WOPxbRVcmgbv4hGU+uSQ/2xFZQ==}
+  picocolors@1.1.1:
+    resolution: {integrity: sha512-xceH2snhtb5M9liqDsmEw56le376mTZkEX/jEb/RxNFyegNul7eNslCXP9FDj/Lcu0X8KEyMceP2ntpaHrDEVA==}
 
-  callsites@3.1.0:
-    resolution: {integrity: sha512-P8BjAsXvZS+VIDUI11hHCQEv74YT67YUi5JJFNWIqL235sBmjX4+qx9Muvls5ivyNENctx46xQLQ3aTuE7ssaQ==}
-    engines: {node: '>=6'}
+  picomatch@2.3.2:
+    resolution: {integrity: sha512-V7+vQEJ06Z+c5tSye8S+nHUfI51xoXIXjHQ99cQtKUkQqqO1kO/KCJUfZXuB47h/YBlDhah2H3hdUGXn8ie0oA==}
+    engines: {node: '>=8.6'}
 
-  camel-case@4.1.2:
-    resolution: {integrity: sha512-gxGWBrTT1JuMx6R+o5PTXMmUnhnVzLQ9SNutD4YqKtI6ap897t3tKECYla6gCWEkplXnlNybEkZg9GEGxKFCgw==}
+  picomatch@4.0.7:
+    resolution: {integrity: sha512-qcJu88Q2IWqJsDD529JKMdwGm/dvInW4HvQnRwiH9JtihJvzGOscDtHE3x1pBKeUOTysQ8kVmLnJ2kJu7yhcGA==}
+    engines: {node: '>=12'}
 
-  camelcase@6.3.0:
-    resolution: {integrity: sha512-Gmy6FhYlCY7uOElZUSbxo2UCDH8owEk996gkbrpsgGtrJLM3J7jGxl9Ic7Qwwj4ivOE5AWZWRMecDdF7hqGjFA==}
-    engines: {node: '>=10'}
+  pirates@4.0.7:
+    resolution: {integrity: sha512-TfySrs/5nm8fQJDcBDuUng3VOUKsd7S+zqvbOTiGXHfxX4wK31ard+hoNuvkicM/2YFzlpDgABOevKSsB4G/FA==}
+    engines: {node: '>= 6'}
 
-  camelcase@7.0.1:
-    resolution: {integrity: sha512-xlx1yCK2Oc1APsPXDL2LdlNP6+uu8OCDdhOBSVT279M/S+y75O30C2VuD8T2ogdePBBl7PfPF4504tnLgX3zfw==}
-    engines: {node: '>=14.16'}
+  pony-cause@1.1.1:
+    resolution: {integrity: sha512-PxkIc/2ZpLiEzQXu5YRDOUgBlfGYBY8156HY5ZcRAwwonMk5W/MrJP2LLkG/hF7GEQzaHo2aS7ho6ZLCOvf+6g==}
+    engines: {node: '>=12.0.0'}
 
-  caniuse-api@3.0.0:
-    resolution: {integrity: sha512-bsTwuIg/BZZK/vreVTYYbSWoe2F+71P7K5QGEX+pT250DZbfU1MQ5prOKpPR+LL6uWKK3KMwMCAS74QB3Um1uw==}
+  possible-typed-array-names@1.1.0:
+    resolution: {integrity: sha512-/+5VFTchJDoVj3bhoqi6UeymcD00DAwb1nJwamzPvHEszJ4FpF6SNNbUbOS8yI56qHzdV8eK0qEfOSiodkTdxg==}
+    engines: {node: '>= 0.4'}
 
-  caniuse-lite@1.0.30001797:
-    resolution: {integrity: sha512-l8xKG+gwAIExZGl9FrF7KUwuOmk6wbEPC9Xoy/RtnWv1XG0Q4LFlagaLpUv3Kiza3W/wm27zy0yWJEieYKAP6w==}
+  postcss-import@15.1.0:
+    resolution: {integrity: sha512-hpr+J05B2FVYUAXHeK1YyI267J/dDDhMU6B6civm8hSY1jYJnBXxzKDKDswzJmtLHryrjhnDjqqp/49t8FALew==}
+    engines: {node: '>=14.0.0'}
+    peerDependencies:
+      postcss: ^8.0.0
 
-  ccount@1.1.0:
-    resolution: {integrity: sha512-vlNK021QdI7PNeiUh/lKkC/mNHHfV0m/Ad5JoI0TYtlBnJAslM/JIkm/tGC88bkLIwO6OQ5uV6ztS6kVAtCDlg==}
+  postcss-js@4.1.0:
+    resolution: {integrity: sha512-oIAOTqgIo7q2EOwbhb8UalYePMvYoIeRY2YKntdpFQXNosSu3vLrniGgmH9OKs/qAkfoj5oB3le/7mINW1LCfw==}
+    engines: {node: ^12 || ^14 || >= 16}
+    peerDependencies:
+      postcss: ^8.4.21
 
-  ccount@2.0.1:
-    resolution: {integrity: sha512-eyrF0jiFpY+3drT6383f1qhkbGsLSifNAjA61IUjZjmLCWjItY6LB9ft9YhoDgwfmclB2zhu51Lc7+95b8NRAg==}
+  postcss-load-config@4.0.2:
+    resolution: {integrity: sha512-bSVhyJGL00wMVoPUzAVAnbEoWyqRxkjv64tUl427SKnPrENtq6hJwUojroMz2VB+Q1edmi4IfrAPpami5VVgMQ==}
+    engines: {node: '>= 14'}
+    peerDependencies:
+      postcss: '>=8.0.9'
+      ts-node: '>=9.0.0'
+    peerDependenciesMeta:
+      postcss:
+        optional: true
+      ts-node:
+        optional: true
 
-  chalk@4.1.2:
-    resolution: {integrity: sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==}
-    engines: {node: '>=10'}
+  postcss-nested@6.2.0:
+    resolution: {integrity: sha512-HQbt28KulC5AJzG+cZtj9kvKB93CFCdLvog1WFLf1D+xmMvPGlBstkpTEZfK5+AN9hfJocyBFCNiqyS48bpgzQ==}
+    engines: {node: '>=12.0'}
+    peerDependencies:
+      postcss: ^8.2.14
 
-  chalk@5.6.2:
-    resolution: {integrity: sha512-7NzBL0rN6fMUW+f7A6Io4h40qQlG+xGmtMxfbnH/K7TAtt8JQWVQK+6g0UXKMeVJoyV5EkkNsErQ8pVD3bLHbA==}
-    engines: {node: ^12.17.0 || ^14.13 || >=16.0.0}
+  postcss-selector-parser@6.1.4:
+    resolution: {integrity: sha512-bIoJLOmjCO1S9XdY/DcnR5hJxvrDir1PbGChrzXG3vw0/FOliy/fA3dmdhQ441kah4gKv+TwckGzex6wNS5cnQ==}
+    engines: {node: '>=4'}
 
-  char-regex@1.0.2:
-    resolution: {integrity: sha512-kWWXztvZ5SBQV+eRgKFeh8q5sLuZY2+8WUIzlxWVTg+oGwY14qylx1KbKzHd8P6ZYkAg0xyIDU9JMHhyJMZ1jw==}
-    engines: {node: '>=10'}
+  postcss-value-parser@4.2.0:
+    resolution: {integrity: sha512-1NNCs6uurfkVbeXG4S8JFT9t19m45ICnif8zWLd5oPSZ50QnwMfK+H3jv408d4jw/7Bttv5axS5IiHoLaVNHeQ==}
 
-  character-entities-html4@2.1.0:
-    resolution: {integrity: sha512-1v7fgQRj6hnSwFpq1Eu0ynr/CDEw0rXo2B61qXrLNdHZmPKgb7fqS1a2JwF0rISo9q77jDI8VMEHoApn8qDoZA==}
+  postcss@8.5.23:
+    resolution: {integrity: sha512-g50586zr4bZmwFiTlflMu8E0bDTb5I5gertgwAKmsdUlTQIhZtunzUlD1WSzwcVWPoAVpsrA6vlfCD7oXvRwgg==}
+    engines: {node: ^10 || ^12 || >=14}
 
-  character-entities-legacy@1.1.4:
-    resolution: {integrity: sha512-3Xnr+7ZFS1uxeiUDvV02wQ+QDbc55o97tIV5zHScSPJpcLm/r0DFPcoY3tYRp+VZukxuMeKgXYmsXQHO05zQeA==}
+  posthog-node@5.17.2:
+    resolution: {integrity: sha512-lz3YJOr0Nmiz0yHASaINEDHqoV+0bC3eD8aZAG+Ky292dAnVYul+ga/dMX8KCBXg8hHfKdxw0SztYD5j6dgUqQ==}
+    engines: {node: '>=20'}
 
-  character-entities-legacy@3.0.0:
-    resolution: {integrity: sha512-RpPp0asT/6ufRm//AJVwpViZbGM/MkjQFxJccQRHmISF/22NBtsHqAWmL+/pmkPWoIUJdWyeVleTl1wydHATVQ==}
+  prebuild-install@7.1.3:
+    resolution: {integrity: sha512-8Mf2cbV7x1cXPUILADGI3wuhfqWvtiLA1iclTDbFRZkgRQS0NqsPZphna9V+HyTEadheuPmjaJMsbzKQFOzLug==}
+    engines: {node: '>=10'}
+    deprecated: No longer maintained. Please contact the author of the relevant native addon; alternatives are available.
+    hasBin: true
 
-  character-entities@1.2.4:
-    resolution: {integrity: sha512-iBMyeEHxfVnIakwOuDXpVkc54HijNgCyQB2w0VfGQThle6NXn50zU6V/u+LDhxHcDUPojn6Kpga3PTAD8W1bQw==}
+  prettier@3.9.4:
+    resolution: {integrity: sha512-yWG/o/4oJfo036EKAfK6ACAoDOfHeRHx4tuxkfBZiauURiaSmYwlpOr5LQqKtIkRD2z1PLteme2WoxEnj4tHTg==}
+    engines: {node: '>=14'}
+    hasBin: true
 
-  character-entities@2.0.2:
-    resolution: {integrity: sha512-shx7oQ0Awen/BRIdkjkvz54PnEEI/EjwXDSIZp86/KKdbafHh1Df/RYGBhn4hbe2+uKC9FnT5UCEdyPz3ai9hQ==}
+  property-information@6.5.0:
+    resolution: {integrity: sha512-PgTgs/BlvHxOu8QuEN7wi5A0OmXaBcHpmCSTehcs6Uuu9IkDIEo13Hy7n898RHfrQ49vKCoGeWZSaAK01nwVig==}
 
-  character-reference-invalid@1.1.4:
-    resolution: {integrity: sha512-mKKUkUbhPpQlCOfIuZkvSEgktjPFIsZKRRbC6KWVEMvlzblj3i3asQv5ODsrwt0N3pHAEvjP8KTQPHkp0+6jOg==}
+  property-information@7.2.0:
+    resolution: {integrity: sha512-IAtzIB6sUiWaJYrX9smp3V46pBGbBeLFRGdh25kg1334VcBlD8HzhPeNIWQH9zhGmo2itIe25EHt9dQP7G5hmg==}
 
-  character-reference-invalid@2.0.1:
-    resolution: {integrity: sha512-iBZ4F4wRbyORVsu0jPV7gXkOsGYjGHPmAyv+HiHG8gi5PtC9KI2j1+v8/tlibRvjoWX027ypmG/n0HtO5t7unw==}
+  prosemirror-model@1.25.4:
+    resolution: {integrity: sha512-PIM7E43PBxKce8OQeezAs9j4TP+5yDpZVbuurd1h5phUxEKIu+G2a+EUZzIC5nS1mJktDJWzbqS23n1tsAf5QA==}
 
-  charset@1.0.1:
-    resolution: {integrity: sha512-6dVyOOYjpfFcL1Y4qChrAoQLRHvj2ziyhcm0QJlhOcAhykL/k1kTUPbeo+87MNRTRdk2OIIsIXbuF3x2wi5EXg==}
-    engines: {node: '>=4.0.0'}
+  proxy-addr@2.0.8:
+    resolution: {integrity: sha512-5nnx0yGyVUcY6t9RnWcARWtwT9F1D8O9rt08htPvnd49W1IgZtmLkhu9WfMzQj1cFxjHIO6connUNVW5k7AVyQ==}
+    engines: {node: '>= 0.10'}
 
-  cheerio-select@2.1.0:
-    resolution: {integrity: sha512-9v9kG0LvzrlcungtnJtpGNxY+fzECQKhK4EGJX2vByejiMX84MFNQw4UxPJl3bFbTMw+Dfs37XaIkCwTZfLh4g==}
+  proxy-from-env@2.1.0:
+    resolution: {integrity: sha512-cJ+oHTW1VAEa8cJslgmUZrc+sjRKgAKl3Zyse6+PV38hZe/V6Z14TbCuXcan9F9ghlz4QrFr2c92TNF82UkYHA==}
+    engines: {node: '>=10'}
 
-  cheerio@1.0.0-rc.12:
-    resolution: {integrity: sha512-VqR8m68vM46BNnuZ5NtnGBKIE/DfN0cRIzg9n40EIq9NOv90ayxLBXA8fXC5gquFRGJSTRqBq25Jt2ECLR431Q==}
-    engines: {node: '>= 6'}
+  public-ip@5.0.0:
+    resolution: {integrity: sha512-xaH3pZMni/R2BG7ZXXaWS9Wc9wFlhyDVJF47IJ+3ali0TGv+2PsckKxbmo+rnx3ZxiV2wblVhtdS3bohAP6GGw==}
+    engines: {node: ^14.13.1 || >=16.0.0}
 
-  chokidar@3.6.0:
-    resolution: {integrity: sha512-7VT13fmjotKpGipCW9JEQAusEPE+Ei8nl6/g4FBAmIm0GOOLMua9NDDo/DWp0ZAxCr3cPq5ZpBqmPAQgDda2Pw==}
-    engines: {node: '>= 8.10.0'}
+  pump@3.0.4:
+    resolution: {integrity: sha512-VS7sjc6KR7e1ukRFhQSY5LM2uBWAUPiOPa/A3mkKmiMwSmRFUITt0xuj+/lesgnCv+dPIEYlkzrcyXgquIHMcA==}
 
-  chokidar@5.0.0:
-    resolution: {integrity: sha512-TQMmc3w+5AxjpL8iIiwebF73dRDF4fBIieAqGn9RGCWaEVwQ6Fb2cGe31Yns0RRIzii5goJ1Y7xbMwo1TxMplw==}
-    engines: {node: '>= 20.19.0'}
+  punycode@2.3.1:
+    resolution: {integrity: sha512-vYt7UD1U9Wg6138shLtLOvdAu+8DsC/ilFtEVHcH+wydcSpNE20AfSOduf6MkRFahL5FY7X1oU7nKVZFtfq8Fg==}
+    engines: {node: '>=6'}
 
-  chrome-trace-event@1.0.4:
-    resolution: {integrity: sha512-rNjApaLzuwaOTjCiT8lSDdGN1APCiqkChLMJxJPWLunPAt5fy8xgU9/jNOchV84wfIxrA0lRQB7oCT8jrn/wrQ==}
-    engines: {node: '>=6.0'}
+  qs@6.14.2:
+    resolution: {integrity: sha512-V/yCWTTF7VJ9hIh18Ugr2zhJMP01MY7c5kh4J870L7imm6/DIzBsNLTXzMwUA3yZ5b/KBqLx8Kp3uRvd7xSe3Q==}
+    engines: {node: '>=0.6'}
 
-  ci-info@3.9.0:
-    resolution: {integrity: sha512-NIxF55hv4nSqQswkAeiOi1r83xy8JldOFDTWiug55KBu9Jnblncd2U6ViHmYgHf01TPZS77NJBhBMKdWj9HQMQ==}
-    engines: {node: '>=8'}
-
-  classnames@2.5.1:
-    resolution: {integrity: sha512-saHYOzhIQs6wy2sVxTM6bUDsQO4F50V9RQ22qBpEdCW+I+/Wmke2HOl6lS6dTpdxVhb88/I6+Hs+438c3lfUow==}
-
-  clean-css@5.3.3:
-    resolution: {integrity: sha512-D5J+kHaVb/wKSFcyyV75uCn8fiY4sV38XJoe4CUyGQ+mOU/fMVYUdH1hJC+CJQ5uY3EnW27SbJYS4X8BiLrAFg==}
-    engines: {node: '>= 10.0'}
+  qs@6.16.1:
+    resolution: {integrity: sha512-5Px6J7rfHBAGUhNQ3es4YzcOdBBw0SDcVtThJml4RdnKw4tKs2epA0kPZ+K8X+WiHktT93RHVcQ/3ym5aTCgtg==}
+    engines: {node: '>=0.6'}
 
-  clean-stack@2.2.0:
-    resolution: {integrity: sha512-4diC9HaTE+KRAMWhDhrGOECgWZxoevMc5TlkObMqNSsVU62PYzXZ/SMTjzyGAFF1YusgxGcSWTEXBhp0CPwQ1A==}
-    engines: {node: '>=6'}
+  queue-microtask@1.2.3:
+    resolution: {integrity: sha512-NuaNSa6flKT5JaSYQzJok04JzTL1CA6aGhv5rfLW3PgqA+M2ChpZQnAC8h8i4ZFkBS8X5RqkDBHA7r4hej3K9A==}
 
-  cli-boxes@3.0.0:
-    resolution: {integrity: sha512-/lzGpEWL/8PfI0BmBOPRwp0c/wFNX1RdUML3jK/RcSBA9T8mZDdQpqYBKtCFTOfQbwPqWEOpjqW+Fnayc0969g==}
+  quick-lru@5.1.1:
+    resolution: {integrity: sha512-WuyALRjWPDGtt/wzJiadO5AXY+8hZ80hVpe6MyivgraREW751X3SbhRvG3eLKOYN+8VEvqLcf3wdnt44Z4S4SA==}
     engines: {node: '>=10'}
 
-  cli-table3@0.6.5:
-    resolution: {integrity: sha512-+W/5efTR7y5HRD7gACw9yQjqMVvEMLBHmboM/kPWam+H+Hmyrgjh6YncVKK122YZkXrLudzTuAukUw9FnMf7IQ==}
-    engines: {node: 10.* || >= 12.*}
-
-  client-only@0.0.1:
-    resolution: {integrity: sha512-IV3Ou0jSMzZrd3pZ48nLkT9DA7Ag1pnPzaiQhpW7c3RbcqqzvzzVu+L8gfqMp/8IM2MQtSiqaCxrrcfu8I8rMA==}
-
-  cliui@8.0.1:
-    resolution: {integrity: sha512-BSeNnyus75C4//NQ9gQt1/csTXyo/8Sb+afLAkzAptFuMsod9HFokGNudZpi/oQV73hnVK+sR+5PVRMd+Dr7YQ==}
-    engines: {node: '>=12'}
+  range-parser@1.2.1:
+    resolution: {integrity: sha512-Hrgsx+orqoygnmhFbKaHE6c296J+HTAQXoxEF6gNupROmmGJRoyzfG3ccAveqCBrwr/2yxQ5BVd/GTl5agOwSg==}
+    engines: {node: '>= 0.6'}
 
-  cliui@9.0.1:
-    resolution: {integrity: sha512-k7ndgKhwoQveBL+/1tqGJYNz097I7WOvwbmmU2AR5+magtbjPWQTS1C5vzGkBC8Ym8UWRzfKUzUUqFLypY4Q+w==}
-    engines: {node: '>=20'}
+  raw-body@2.5.3:
+    resolution: {integrity: sha512-s4VSOf6yN0rvbRZGxs8Om5CWj6seneMwK3oDb4lWDH0UPhWcxwOWw5+qk24bxq87szX1ydrwylIOp2uG1ojUpA==}
+    engines: {node: '>= 0.8'}
 
-  clone-deep@4.0.1:
-    resolution: {integrity: sha512-neHB9xuzh/wk0dIHweyAXv2aPGZIVk3pLMe+/RNzINf17fe0OG96QroktYAUm7SM1PBnzTabaLboqqxDyMU+SQ==}
-    engines: {node: '>=6'}
+  rc@1.2.8:
+    resolution: {integrity: sha512-y3bGgqKj3QBdxLbLkomlohkvsA8gdAiUQlSBJnBhfn+BPxg4bc62d8TcBW15wavDfgexCgccckhcZvywyQYPOw==}
+    hasBin: true
 
-  clsx@1.2.1:
-    resolution: {integrity: sha512-EcR6r5a8bj6pu3ycsa/E/cKVGuTgZJZdsyUYHOksG/UHIiKfjxzRxYJpyVBwYaQeOvghal9fcc4PidlgzugAQg==}
-    engines: {node: '>=6'}
+  re2js@2.8.6:
+    resolution: {integrity: sha512-xLgQil4kIUCrAzVk9fRSkxkFNwmygLFjVxXrLc65aE1F0+Zsb8rxumFBy4XKyvgMCTL6kilDq3EZ0piE2dP/Dg==}
+    engines: {node: '>=18.0.0'}
 
-  clsx@2.1.1:
-    resolution: {integrity: sha512-eYm0QWBtUrBWZWG0d386OGAw16Z995PiOVo2B7bjWSbHedGl5e0ZWaq65kOGgUSNesEIDkB9ISbTg/JK9dhCZA==}
-    engines: {node: '>=6'}
+  react-dom@19.3.1:
+    resolution: {integrity: sha512-Y0bARz53lhEC1NMCASs0/j+faB/zqt3R8hpvg1e8+61ZVJ4UL0UdC4cBbXfZMcIuhrfgeILTLe+ZeBCavQPtKQ==}
+    peerDependencies:
+      react: ^19.3.1
 
-  collapse-white-space@2.1.0:
-    resolution: {integrity: sha512-loKTxY1zCOuG4j9f6EPnuyyYkf58RnhhWTvRoZEokgB+WbdXehfjFviyOVYkqzEWz1Q5kRiZdBYS5SwxbQYwzw==}
+  react-reconciler@0.32.0:
+    resolution: {integrity: sha512-2NPMOzgTlG0ZWdIf3qG+dcbLSoAc/uLfOwckc3ofy5sSK0pLJqnQLpUFxvGcN2rlXSjnVtGeeFLNimCQEj5gOQ==}
+    engines: {node: '>=0.10.0'}
+    peerDependencies:
+      react: ^19.1.0
 
-  color-convert@2.0.1:
-    resolution: {integrity: sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==}
-    engines: {node: '>=7.0.0'}
+  react@19.2.3:
+    resolution: {integrity: sha512-Ku/hhYbVjOQnXDZFv2+RibmLFGwFdeeKHFcOTlrt7xplBnya5OGn/hIRDsqDiSUcfORsDC7MPxwork8jBwsIWA==}
+    engines: {node: '>=0.10.0'}
 
-  color-name@1.1.4:
-    resolution: {integrity: sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==}
+  read-cache@1.0.2:
+    resolution: {integrity: sha512-/peqiBB/n07gQGLsWaHho3WfvUyRscw0gYTsEFMhrIe/nWLkYaf5SbKYjGYqtRV3aPwykJgF2VEMo1ac4bnsGA==}
 
-  colord@2.9.3:
-    resolution: {integrity: sha512-jeC1axXpnb0/2nn/Y1LPuLdgXBLH7aDcHu4KEKfqw3CUhX7ZpfBSlPKyqXE6btIgEzfWtrX3/tyBCaCvXvMkOw==}
+  readable-stream@3.6.2:
+    resolution: {integrity: sha512-9u/sniCrY3D5WdsERHzHE4G2YCXqoG5FTHUiCC4SIbr6XcLZBY05ya9EKjYek9O5xOAwjGq+1JdGBAS7Q9ScoA==}
+    engines: {node: '>= 6'}
 
-  colorette@1.4.0:
-    resolution: {integrity: sha512-Y2oEozpomLn7Q3HFP7dpww7AtMJplbM9lGZP6RDfHqmbeRjiwRg4n6VM6j4KLmRke85uWEI7JqF17f3pqdRA0g==}
+  readdirp@3.6.0:
+    resolution: {integrity: sha512-hOS089on8RduqdbhvQ5Z37A0ESjsqz6qnRcffsMU3495FuTdqSm+7bhJ29JvIOsBDEEnan5DPu9t3To9VRlMzA==}
+    engines: {node: '>=8.10.0'}
 
-  colorette@2.0.20:
-    resolution: {integrity: sha512-IfEDxwoWIjkeXL1eXcDiow4UbKjhLdq6/EuSVR9GMN7KVH3r9gQ83e73hsz1Nd1T3ijd5xv1wcWRYO+D6kCI2w==}
+  recma-build-jsx@1.0.0:
+    resolution: {integrity: sha512-8GtdyqaBcDfva+GUKDr3nev3VpKAhup1+RvkMvUxURHpW7QyIvk9F5wz7Vzo06CEMSilw6uArgRqhpiUcWp8ew==}
 
-  combine-promises@1.2.0:
-    resolution: {integrity: sha512-VcQB1ziGD0NXrhKxiwyNbCDmRzs/OShMs2GqW2DlU2A/Sd0nQxE1oWDAE5O0ygSx5mgQOn9eIFh7yKPgFRVkPQ==}
-    engines: {node: '>=10'}
+  recma-jsx@1.0.1:
+    resolution: {integrity: sha512-huSIy7VU2Z5OLv6oFLosQGGDqPqdO1iq6bWNAdhzMxSJP7RAso4fCZ1cKu8j9YHCZf3TPrq4dw3okhrylgcd7w==}
+    peerDependencies:
+      acorn: ^6.0.0 || ^7.0.0 || ^8.0.0
 
-  comma-separated-tokens@1.0.8:
-    resolution: {integrity: sha512-GHuDRO12Sypu2cV70d1dkA2EUmXHgntrzbpvOB+Qy+49ypNfGgFQIC2fhhXbnyrJRynDCAARsT7Ou0M6hirpfw==}
+  recma-parse@1.0.0:
+    resolution: {integrity: sha512-OYLsIGBB5Y5wjnSnQW6t3Xg7q3fQ7FWbw/vcXtORTnyaSFscOtABg+7Pnz6YZ6c27fG1/aN8CjfwoUEUIdwqWQ==}
 
-  comma-separated-tokens@2.0.3:
-    resolution: {integrity: sha512-Fu4hJdvzeylCfQPp9SGWidpzrMs7tTrlu6Vb8XGaRGck8QSNZJJp538Wrb60Lax4fPwR64ViY468OIUTbRlGZg==}
+  recma-stringify@1.0.0:
+    resolution: {integrity: sha512-cjwII1MdIIVloKvC9ErQ+OgAtwHBmcZ0Bg4ciz78FtbT8In39aAYbaA7zvxQ61xVMSPE8WxhLwLbhif4Js2C+g==}
 
-  commander@10.0.1:
-    resolution: {integrity: sha512-y4Mg2tXshplEbSGzx7amzPwKKOCGuoSRP/CjEdwwk0FOGlUbq6lKuoyDZTNZkmxHdJtp54hdfY/JUrdL7Xfdug==}
-    engines: {node: '>=14'}
+  reflect.getprototypeof@1.0.10:
+    resolution: {integrity: sha512-00o4I+DVrefhv+nX0ulyi3biSHCPDe+yLv5o/p6d/UVlirijB8E16FtfwSAi4g3tcqrQ4lRAqQSoFEZJehYEcw==}
+    engines: {node: '>= 0.4'}
 
-  commander@2.20.3:
-    resolution: {integrity: sha512-GpVkmM8vF2vQUkj2LvZmD35JxeJOLCwJ9cUkugyk2nuhbv3+mJvpLYYt+0+USMxE+oj+ey/lJEnhZw75x/OMcQ==}
+  regex-recursion@6.0.2:
+    resolution: {integrity: sha512-0YCaSCq2VRIebiaUviZNs0cBz1kg5kVS2UKUfNIx8YVs1cN3AV7NTctO5FOKBA+UT2BPJIWZauYHPqJODG50cg==}
 
-  commander@4.1.1:
-    resolution: {integrity: sha512-NOKm8xhkzAjzFx8B2v5OAHT+u5pRQc2UCa2Vq9jYL/31o2wi9mxBA7LIFs3sV5VSC49z6pEhfbMULvShKj26WA==}
-    engines: {node: '>= 6'}
+  regex-utilities@2.3.0:
+    resolution: {integrity: sha512-8VhliFJAWRaUiVvREIiW2NXXTmHs4vMNnSzuJVhscgmGav3g9VDxLrQndI3dZZVVdp0ZO/5v0xmX516/7M9cng==}
 
-  commander@5.1.0:
-    resolution: {integrity: sha512-P0CysNDQ7rtVw4QIQtm+MRxV66vKFSvlsQvGYXZWR3qFU0jlMKHZZZgw8e+8DSah4UDKMqnknRDQz+xuQXQ/Zg==}
-    engines: {node: '>= 6'}
+  regex@6.1.0:
+    resolution: {integrity: sha512-6VwtthbV4o/7+OaAF9I5L5V3llLEsoPyq9P1JVXkedTP33c7MfCG0/5NOPcSJn0TzXcG9YUrR0gQSWioew3LDg==}
 
-  commander@7.2.0:
-    resolution: {integrity: sha512-QrWXB+ZQSVPmIWIhtEO9H+gwHaMGYiF5ChvoJ+K9ZGHG/sVsa6yiesAD1GC/x46sET00Xlwo1u49RVVVzvcSkw==}
-    engines: {node: '>= 10'}
+  regexp.prototype.flags@1.5.4:
+    resolution: {integrity: sha512-dYqgNSZbDwkaJ2ceRd9ojCGjBq+mOm9LmtXnAnEGyHhN/5R7iDW2TRw3h+o/jCFxus3P2LfWIIiwowAjANm7IA==}
+    engines: {node: '>= 0.4'}
 
-  commander@8.3.0:
-    resolution: {integrity: sha512-OkTL9umf+He2DZkUq8f8J9of7yL6RJKI24dVITBmNfZBmri9zYZQrKkuXiKhyfPSu8tUhnVBB1iKXevvnlR4Ww==}
-    engines: {node: '>= 12'}
+  rehype-katex@7.0.1:
+    resolution: {integrity: sha512-OiM2wrZ/wuhKkigASodFoo8wimG3H12LWQaH8qSPVJn9apWKFSH3YOCtbKpBorTVw/eI7cuT21XBbvwEswbIOA==}
 
-  common-path-prefix@3.0.0:
-    resolution: {integrity: sha512-QE33hToZseCH3jS0qN96O/bSh3kaw/h+Tq7ngyY9eWDUnTlTNUyqfqvCXioLe5Na5jFsL78ra/wuBU4iuEgd4w==}
+  rehype-minify-whitespace@6.0.2:
+    resolution: {integrity: sha512-Zk0pyQ06A3Lyxhe9vGtOtzz3Z0+qZ5+7icZ/PL/2x1SHPbKao5oB/g/rlc6BCTajqBb33JcOe71Ye1oFsuYbnw==}
 
-  compressible@2.0.18:
-    resolution: {integrity: sha512-AF3r7P5dWxL8MxyITRMlORQNaOA2IkAFaTr4k7BUumjPtRpGDTZpl0Pb1XCO6JeDCBdp126Cgs9sMxqSjgYyRg==}
-    engines: {node: '>= 0.6'}
+  rehype-parse@9.0.1:
+    resolution: {integrity: sha512-ksCzCD0Fgfh7trPDxr2rSylbwq9iYDkSn8TCDmEJ49ljEUBxDVCzCHv7QNzZOfODanX4+bWQ4WZqLCRWYLfhag==}
 
-  compression@1.8.1:
-    resolution: {integrity: sha512-9mAqGPHLakhCLeNyxPkK4xVo746zQ/czLH1Ky+vkitMnWfWZps8r0qXuwhwizagCRttsL4lfG4pIOvaWLpAP0w==}
-    engines: {node: '>= 0.8.0'}
+  rehype-recma@1.0.0:
+    resolution: {integrity: sha512-lqA4rGUf1JmacCNWWZx0Wv1dHqMwxzsDWYMTowuplHF3xH0N/MmrZ/G3BDZnzAkRmxDadujCjaKM2hqYdCBOGw==}
 
-  compute-gcd@1.2.1:
-    resolution: {integrity: sha512-TwMbxBNz0l71+8Sc4czv13h4kEqnchV9igQZBi6QUaz09dnz13juGnnaWWJTRsP3brxOoxeB4SA2WELLw1hCtg==}
+  rehype-stringify@10.0.1:
+    resolution: {integrity: sha512-k9ecfXHmIPuFVI61B9DeLPN0qFHfawM6RsuX48hoqlaKSF61RskNjSm1lI8PhBEM0MRdLxVVm4WmTqJQccH9mA==}
 
-  compute-lcm@1.1.2:
-    resolution: {integrity: sha512-OFNPdQAXnQhDSKioX8/XYT6sdUlXwpeMjfd6ApxMJfyZ4GxmLR1xvMERctlYhlHwIiz6CSpBc2+qYKjHGZw4TQ==}
+  remark-frontmatter@5.0.0:
+    resolution: {integrity: sha512-XTFYvNASMe5iPN0719nPrdItC9aU0ssC4v14mH1BCi1u0n1gAocqcujWUrByftZTbLhRtiKRyjYTSIOcr69UVQ==}
 
-  concat-map@0.0.1:
-    resolution: {integrity: sha512-/Srv4dswyQNBfohGpz9o6Yb3Gz3SrUDqBH5rTuhGR7ahtlbYKnVxw2bCFMRljaA7EXHaXZ8wsHdodFvbkhKmqg==}
+  remark-gfm@4.0.0:
+    resolution: {integrity: sha512-U92vJgBPkbw4Zfu/IiW2oTZLSL3Zpv+uI7My2eq8JxKgqraFdU8YUGicEJCEgSbeaG+QDFqIcwwfMTOEelPxuA==}
 
-  config-chain@1.1.13:
-    resolution: {integrity: sha512-qj+f8APARXHrM0hraqXYb2/bOVSV4PvJQlNZ/DVj0QrmNM2q2euizkeuVckQ57J+W0mRH6Hvi+k50M4Jul2VRQ==}
+  remark-gfm@4.0.1:
+    resolution: {integrity: sha512-1quofZ2RQ9EWdeN34S79+KExV1764+wCUGop5CPL1WGdD0ocPpu91lzPGbwWMECpEpd42kJGQwzRfyov9j4yNg==}
 
-  configstore@6.0.0:
-    resolution: {integrity: sha512-cD31W1v3GqUlQvbBCGcXmd2Nj9SvLDOP1oQ0YFuLETufzSPaKp11rYBsSOm7rCsW3OnIRAFM3OxRhceaXNYHkA==}
-    engines: {node: '>=12'}
+  remark-math@6.0.0:
+    resolution: {integrity: sha512-MMqgnP74Igy+S3WwnhQ7kqGlEerTETXMvJhrUzDikVZ2/uogJCb+WHUg97hK9/jcfc0dkD73s3LN8zU49cTEtA==}
 
-  connect-history-api-fallback@2.0.0:
-    resolution: {integrity: sha512-U73+6lQFmfiNPrYbXqr6kZ1i1wiRqXnp2nhMsINseWXO8lDau0LGEffJ8kQi4EjLZympVgRdvqjAgiZ1tgzDDA==}
-    engines: {node: '>=0.8'}
+  remark-mdx-remove-esm@1.3.3:
+    resolution: {integrity: sha512-KgGfD4JV3lKse0n/m8UxW4jK6H/9ffkCVxVAJ60aGY4uiPX/+SQCT5/lQcRGcjyQuRLDq2Df2krv6pD/qWJRVw==}
+    peerDependencies:
+      unified: ^11
 
-  consola@3.4.2:
-    resolution: {integrity: sha512-5IKcdX0nnYavi6G7TtOhwkYzyjfJlatbjMjuLSfE2kYT5pMDOilZ4OvMhi637CcDICTmz3wARPoyhqyX1Y+XvA==}
-    engines: {node: ^14.18.0 || >=16.10.0}
+  remark-mdx@3.0.1:
+    resolution: {integrity: sha512-3Pz3yPQ5Rht2pM5R+0J2MrGoBSrzf+tJG94N+t/ilfdh8YLyyKYtidAYwTveB20BoHAcwIopOUqhcmh2F7hGYA==}
 
-  content-disposition@0.5.2:
-    resolution: {integrity: sha512-kRGRZw3bLlFISDBgwTSA1TMBFN6J6GWDeubmDE3AF+3+yXL8hTWv8r5rkLbqYXY4RjPk/EzHnClI3zQf1cFmHA==}
-    engines: {node: '>= 0.6'}
+  remark-mdx@3.1.0:
+    resolution: {integrity: sha512-Ngl/H3YXyBV9RcRNdlYsZujAmhsxwzxpDzpDEhFBVAGthS4GDgnctpDjgFl/ULx5UEDzqtW1cyBSNKqYYrqLBA==}
 
-  content-disposition@0.5.4:
-    resolution: {integrity: sha512-FveZTNuGw04cxlAiWbzi6zTAL/lhehaWbTtgluJh4/E95DqMwTmha3KZN1aAWA8cFIhHzMZUvLevkw5Rqk+tSQ==}
-    engines: {node: '>= 0.6'}
+  remark-mdx@3.1.1:
+    resolution: {integrity: sha512-Pjj2IYlUY3+D8x00UJsIOg5BEvfMyeI+2uLPn9VO9Wg4MEtN/VTIq2NEJQfde9PnX15KgtHyl9S0BcTnWrIuWg==}
 
-  content-type@1.0.5:
-    resolution: {integrity: sha512-nTjqfcBFEipKdXCv4YDQWCfmcLZKm81ldF0pAopTvyrFGVbcR6P/VAAd5G7N+0tTr8QqiU0tFadD6FK4NtJwOA==}
-    engines: {node: '>= 0.6'}
+  remark-parse@11.0.0:
+    resolution: {integrity: sha512-FCxlKLNGknS5ba/1lmpYijMUzX2esxW5xQqjWxw2eHFfS2MSdaHVINFmhjo+qN1WhZhNimq0dZATN9pH0IDrpA==}
 
-  convert-source-map@2.0.0:
-    resolution: {integrity: sha512-Kvp459HrV2FEJ1CAsi1Ku+MY3kasH19TFykTz2xWmMeq6bk2NU3XXvfJ+Q61m0xktWwt+1HSYf3JZsTms3aRJg==}
+  remark-rehype@11.1.1:
+    resolution: {integrity: sha512-g/osARvjkBXb6Wo0XvAeXQohVta8i84ACbenPpoSsxTOQH/Ae0/RGP4WZgnMH5pMLpsj4FG7OHmcIcXxpza8eQ==}
 
-  cookie-signature@1.0.7:
-    resolution: {integrity: sha512-NXdYc3dLr47pBkpUCHtKSwIOQXLVn8dZEuywboCOJY/osA0wFSLlSawr3KN8qXJEyX66FcONTH8EIlVuK0yyFA==}
+  remark-smartypants@3.0.2:
+    resolution: {integrity: sha512-ILTWeOriIluwEvPjv67v7Blgrcx+LZOkAUVtKI3putuhlZm84FnqDORNXPPm+HY3NdZOMhyDwZ1E+eZB/Df5dA==}
+    engines: {node: '>=16.0.0'}
 
-  cookie@0.7.2:
-    resolution: {integrity: sha512-yki5XnKuf750l50uGTllt6kKILY4nQ1eNIQatoXEByZ5dWgnKqbnqmTrBE5B4N7lrMJKQ2ytWMiTO2o0v6Ew/w==}
-    engines: {node: '>= 0.6'}
+  remark-stringify@11.0.0:
+    resolution: {integrity: sha512-1OSmLd3awB/t8qdoEOMazZkNsfVTeY4fTsgzcQFdXNq8ToTN4ZGwrMnlda4K6smTFKD+GRV6O48i6Z4iKgPPpw==}
 
-  copy-text-to-clipboard@3.2.2:
-    resolution: {integrity: sha512-T6SqyLd1iLuqPA90J5N4cTalrtovCySh58iiZDGJ6FGznbclKh4UI+FGacQSgFzwKG77W7XT5gwbVEbd9cIH1A==}
-    engines: {node: '>=12'}
+  remark@15.0.1:
+    resolution: {integrity: sha512-Eht5w30ruCXgFmxVUSlNWQ9iiimq07URKeFS3hNc8cUWy1llX4KDWfyEDZRycMc+znsN9Ux5/tJ/BFdgdOwA3A==}
 
-  copy-to-clipboard@3.3.3:
-    resolution: {integrity: sha512-2KV8NhB5JqC3ky0r9PMCAZKbUHSwtEo4CwCs0KXgruG43gX5PMqDEBbVU4OUzw2MuAWUfsuFmWvEKG5QRfSnJA==}
+  require-directory@2.1.1:
+    resolution: {integrity: sha512-fGxEI7+wsG9xrvdjsrlmL22OMTTiHRwAMroiEeMgq8gzoLC/PQr7RsRDSTLUg/bZAZtF+TVIkHc6/4RIKrui+Q==}
+    engines: {node: '>=0.10.0'}
 
-  copy-webpack-plugin@11.0.0:
-    resolution: {integrity: sha512-fX2MWpamkW0hZxMEg0+mYnA40LTosOSa5TqZ9GYIBzyJa9C3QUaMPSE2xAi/buNr8u89SfD9wHSQVBzrRa/SOQ==}
-    engines: {node: '>= 14.15.0'}
-    peerDependencies:
-      webpack: ^5.1.0
+  require-from-string@2.0.2:
+    resolution: {integrity: sha512-Xf0nWe6RseziFMu+Ap9biiUbmplq6S9/p+7w7YXP/JBHhrUDDUhwa+vANyubuqfZWTveU//DYVGsDG7RKL/vEw==}
+    engines: {node: '>=0.10.0'}
 
-  core-js-compat@3.49.0:
-    resolution: {integrity: sha512-VQXt1jr9cBz03b331DFDCCP90b3fanciLkgiOoy8SBHy06gNf+vQ1A3WFLqG7I8TipYIKeYK9wxd0tUrvHcOZA==}
+  reselect@5.3.0:
+    resolution: {integrity: sha512-XGoLeRAVzUTcJ1qkxPQhDJyIZ5d6zzZD9nT7AEZOaaU9UbWclhycElmhO+VD5bFeLuzhPBaOV2oXC8uG35ZSpg==}
 
-  core-js@3.49.0:
-    resolution: {integrity: sha512-es1U2+YTtzpwkxVLwAFdSpaIMyQaq0PBgm3YD1W3Qpsn1NAmO3KSgZfu+oGSWVu6NvLHoHCV/aYcsE5wiB7ALg==}
+  resolve-alpn@1.2.1:
+    resolution: {integrity: sha512-0a1F4l73/ZFZOakJnQ3FvkJ2+gSTQWz/r2KE5OdDY0TxPm5h4GkqkWWfM47T7HsbnOtcJVEF4epCVy6u7Q3K+g==}
 
-  core-util-is@1.0.3:
-    resolution: {integrity: sha512-ZQBvi1DcpJ4GDqanjucZ2Hj3wEO5pZDS89BWbkcrvdxksJorwUDDZamX9ldFkp9aw2lmBDLgkObEA4DWNJ9FYQ==}
+  resolve@1.22.13:
+    resolution: {integrity: sha512-Dj/cW9zBV2aRj6XzCxuGIs3ESZKv02jixne3q6jFZYZ3/Tg09gHHviSMDL4kObh9pqSahdRHEnDoaP2gn8YLhA==}
+    engines: {node: '>= 0.4'}
+    hasBin: true
 
-  cose-base@1.0.3:
-    resolution: {integrity: sha512-s9whTXInMSgAp/NVXVNuVxVKzGH2qck3aQlVHxDCdAEPgtMKwc4Wq6/QKhgdEdgbLSi9rBTAcPoRa6JpiG4ksg==}
+  responselike@3.0.0:
+    resolution: {integrity: sha512-40yHxbNcl2+rzXvZuVkrYohathsSJlMTXKryG5y8uciHv1+xDLHQpgjG64JUO9nrEq2jGLH6IZ8BcZyw3wrweg==}
+    engines: {node: '>=14.16'}
 
-  cose-base@2.2.0:
-    resolution: {integrity: sha512-AzlgcsCbUMymkADOJtQm3wO9S3ltPfYOFD5033keQn9NJzIbtnZj+UdBJe7DYml/8TdbtHJW3j58SOnKhWY/5g==}
+  restore-cursor@4.0.0:
+    resolution: {integrity: sha512-I9fPXU9geO9bHOt9pHHOhOkYerIMsmVaWB0rA2AI9ERh/+x/i7MV5HKBNrg+ljO5eoPVgCcnFuRjJ9uH6I/3eg==}
+    engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
 
-  cosmiconfig@8.3.6:
-    resolution: {integrity: sha512-kcZ6+W5QzcJ3P1Mt+83OUv/oHFqZHIx8DuxG6eZ5RGMERoLqp4BuGjhHLYGK+Kf5XVkQvqBSmAy/nGWN3qDgEA==}
-    engines: {node: '>=14'}
-    peerDependencies:
-      typescript: '>=4.9.5'
-    peerDependenciesMeta:
-      typescript:
-        optional: true
+  retext-latin@4.0.0:
+    resolution: {integrity: sha512-hv9woG7Fy0M9IlRQloq/N6atV82NxLGveq+3H2WOi79dtIYWN8OaxogDm77f8YnVXJL2VD3bbqowu5E3EMhBYA==}
 
-  cross-spawn@7.0.6:
-    resolution: {integrity: sha512-uV2QOWP2nWzsy2aMp8aRibhi9dlzF5Hgh5SHaB9OiTGEyDTiJJyx0uy51QXdyWbtAHNua4XJzUKca3OzKUd3vA==}
-    engines: {node: '>= 8'}
+  retext-smartypants@6.2.0:
+    resolution: {integrity: sha512-kk0jOU7+zGv//kfjXEBjdIryL1Acl4i9XNkHxtM7Tm5lFiCog576fjNC9hjoR7LTKQ0DsPWy09JummSsH1uqfQ==}
 
-  crypto-js@4.2.0:
-    resolution: {integrity: sha512-KALDyEYgpY+Rlob/iriUtjV6d5Eq+Y191A5g4UqLAi8CyGP9N1+FdVbkc1SxKc2r4YAYqG8JzO2KGL+AizD70Q==}
+  retext-stringify@4.0.0:
+    resolution: {integrity: sha512-rtfN/0o8kL1e+78+uxPTqu1Klt0yPzKuQ2BfWwwfgIUSayyzxpM1PJzkKt4V8803uB9qSy32MvI7Xep9khTpiA==}
 
-  crypto-random-string@4.0.0:
-    resolution: {integrity: sha512-x8dy3RnvYdlUcPOjkEHqozhiwzKNSq7GcPuXFbnyMOCHxX8V3OgIg/pYuabl2sbUPfIJaeAQB7PMOK8DFIdoRA==}
-    engines: {node: '>=12'}
+  retext@9.0.0:
+    resolution: {integrity: sha512-sbMDcpHCNjvlheSgMfEcVrZko3cDzdbe1x/e7G66dFp0Ff7Mldvi2uv6JkJQzdRcvLYE8CA8Oe8siQx8ZOgTcA==}
 
-  css-blank-pseudo@7.0.1:
-    resolution: {integrity: sha512-jf+twWGDf6LDoXDUode+nc7ZlrqfaNphrBIBrcmeP3D8yw1uPaix1gCC8LUQUGQ6CycuK2opkbFFWFuq/a94ag==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  reusify@1.1.0:
+    resolution: {integrity: sha512-g6QUff04oZpHs0eG5p83rFLhHeV00ug/Yf9nZM6fLeUrPguBTkTQOdpAWWspMh55TZfVQDPaN3NQJfbVRAxdIw==}
+    engines: {iojs: '>=1.0.0', node: '>=0.10.0'}
 
-  css-declaration-sorter@7.4.0:
-    resolution: {integrity: sha512-LTuzjPoyA2vMGKKcaOqKSp7Ub2eGrNfKiZH4LpezxpNrsICGCSFvsQOI29psISxNZtaXibkC2CXzrQ5enMeGGw==}
-    engines: {node: ^14 || ^16 || >=18}
-    peerDependencies:
-      postcss: ^8.0.9
+  run-async@3.0.0:
+    resolution: {integrity: sha512-540WwVDOMxA6dN6We19EcT9sc3hkXPw5mzRNGM3FkdN/vtE9NFvj5lFAPNwUDmJjXidm3v7TC1cTE7t17Ulm1Q==}
+    engines: {node: '>=0.12.0'}
 
-  css-has-pseudo@7.0.3:
-    resolution: {integrity: sha512-oG+vKuGyqe/xvEMoxAQrhi7uY16deJR3i7wwhBerVrGQKSqUC5GiOVxTpM9F9B9hw0J+eKeOWLH7E9gZ1Dr5rA==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  run-parallel@1.2.0:
+    resolution: {integrity: sha512-5l4VyZR86LZ/lDxZTR6jqL8AFE2S0IFLMP26AbjsLVADxHdhB/c0GUsH+y39UfCi3dzz8OlQuPmnaJOMoDHQBA==}
 
-  css-in-js-utils@3.1.0:
-    resolution: {integrity: sha512-fJAcud6B3rRu+KHYk+Bwf+WFL2MDCJJ1XG9x137tJQ0xYxor7XziQtuGFbWNdqrvF4Tk26O3H73nfVqXt/fW1A==}
+  rxjs@7.8.2:
+    resolution: {integrity: sha512-dhKf903U/PQZY6boNNtAGdWbG85WAbjT/1xYoZIC7FAY0yWapOBQVsVrDl58W86//e1VpMNBtRV4MaXfdMySFA==}
 
-  css-loader@6.11.0:
-    resolution: {integrity: sha512-CTJ+AEQJjq5NzLga5pE39qdiSV56F8ywCIsqNIRF0r7BDgWsN25aazToqAFg7ZrtA/U016xudB3ffgweORxX7g==}
-    engines: {node: '>= 12.13.0'}
-    peerDependencies:
-      '@rspack/core': 0.x || 1.x
-      webpack: ^5.0.0
-    peerDependenciesMeta:
-      '@rspack/core':
-        optional: true
-      webpack:
-        optional: true
+  safe-array-concat@1.1.4:
+    resolution: {integrity: sha512-wtZlHyOje6OZTGqAoaDKxFkgRtkF9CnHAVnCHKfuj200wAgL+bSJhdsCD2l0Qx/2ekEXjPWcyKkfGb5CPboslg==}
+    engines: {node: '>=0.4'}
 
-  css-minimizer-webpack-plugin@5.0.1:
-    resolution: {integrity: sha512-3caImjKFQkS+ws1TGcFn0V1HyDJFq1Euy589JlD6/3rV2kj+w7r5G9WDMgSHvpvXHNZ2calVypZWuEDQd9wfLg==}
-    engines: {node: '>= 14.15.0'}
-    peerDependencies:
-      '@parcel/css': '*'
-      '@swc/css': '*'
-      clean-css: '*'
-      csso: '*'
-      esbuild: '*'
-      lightningcss: '*'
-      webpack: ^5.0.0
-    peerDependenciesMeta:
-      '@parcel/css':
-        optional: true
-      '@swc/css':
-        optional: true
-      clean-css:
-        optional: true
-      csso:
-        optional: true
-      esbuild:
-        optional: true
-      lightningcss:
-        optional: true
+  safe-buffer@5.2.1:
+    resolution: {integrity: sha512-rp3So07KcdmmKbGvgaNxQSJr7bGVSVk5S9Eq1F+ppbRo70+YeaDxkw5Dd8NPN+GD6bjnYm2VuPuCXmpuYvmCXQ==}
 
-  css-prefers-color-scheme@10.0.0:
-    resolution: {integrity: sha512-VCtXZAWivRglTZditUfB4StnsWr6YVZ2PRtuxQLKTNRdtAf8tpzaVPE9zXIF3VaSc7O70iK/j1+NXxyQCqdPjQ==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
+  safe-push-apply@1.0.0:
+    resolution: {integrity: sha512-iKE9w/Z7xCzUMIZqdBsp6pEQvwuEebH4vdpjcDWnyzaI6yl6O9FHvVpmGelvEHNsoY6wGblkxR6Zty/h00WiSA==}
+    engines: {node: '>= 0.4'}
 
-  css-select@4.3.0:
-    resolution: {integrity: sha512-wPpOYtnsVontu2mODhA19JrqWxNsfdatRKd64kmpRbQgh1KtItko5sTnEpPdpSaJszTOhEMlF/RPz28qj4HqhQ==}
+  safe-regex-test@1.1.0:
+    resolution: {integrity: sha512-x/+Cz4YrimQxQccJf5mKEbIa1NzeCRNI5Ecl/ekmlYaampdNLPalVyIcCZNNH3MvmqBugV5TMYZXv0ljslUlaw==}
+    engines: {node: '>= 0.4'}
 
-  css-select@5.2.2:
-    resolution: {integrity: sha512-TizTzUddG/xYLA3NXodFM0fSbNizXjOKhqiQQwvhlspadZokn1KDy0NZFS0wuEubIYAV5/c1/lAr0TaaFXEXzw==}
+  safe-stable-stringify@1.1.1:
+    resolution: {integrity: sha512-ERq4hUjKDbJfE4+XtZLFPCDi8Vb1JqaxAPTxWFLBx8XcAlf9Bda/ZJdVezs/NAfsMQScyIlUMx+Yeu7P7rx5jw==}
 
-  css-selector-parser@1.4.1:
-    resolution: {integrity: sha512-HYPSb7y/Z7BNDCOrakL4raGO2zltZkbeXyAd6Tg9obzix6QhzxCotdBl6VT0Dv4vZfJGVz3WL/xaEI9Ly3ul0g==}
+  safer-buffer@2.1.2:
+    resolution: {integrity: sha512-YZo3K82SD7Riyi0E1EQPojLz7kpepnSQI9IyPbHHg1XXXevb5dJI7tpyN2ADxGcQbHG7vcyRHk0cbwqcQriUtg==}
 
-  css-tree@1.1.3:
-    resolution: {integrity: sha512-tRpdppF7TRazZrjJ6v3stzv93qxRcSsFmW6cX0Zm2NVKpxE1WV1HblnghVv9TreireHkqI/VDEsfolRF1p6y7Q==}
-    engines: {node: '>=8.0.0'}
+  satori@0.33.5:
+    resolution: {integrity: sha512-PNW6ktrQ8SM6kk7u4aOuTkkUewkzyTOrj+QeEzXSsnNMAdff4ire9CAqIz8+4C3rCiBtK8QTELv52AZEd1PbRw==}
+    engines: {node: '>=16'}
 
-  css-tree@2.2.1:
-    resolution: {integrity: sha512-OA0mILzGc1kCOCSJerOeqDxDQ4HOh+G8NbOJFOTgOCzpw7fCBubk0fEyxp8AgOL/jvLgYA/uV0cMbe43ElF1JA==}
-    engines: {node: ^10 || ^12.20.0 || ^14.13.0 || >=15.0.0, npm: '>=7.0.0'}
+  sax@1.6.1:
+    resolution: {integrity: sha512-42tBVwLWnaQvW5zc4HbZrTuWccECCZfBi92FDuwtqxasH+JbPB3/FOKb1m222K42R4WxuxzzMsTswfzgtSu64Q==}
+    engines: {node: '>=11.0.0'}
 
-  css-tree@2.3.1:
-    resolution: {integrity: sha512-6Fv1DV/TYw//QF5IzQdqsNDjx/wc8TrMBZsqjL9eW01tWb7R7k/mq+/VXfJCl7SoD5emsJop9cOByJZfs8hYIw==}
-    engines: {node: ^10 || ^12.20.0 || ^14.13.0 || >=15.0.0}
+  scheduler@0.26.0:
+    resolution: {integrity: sha512-NlHwttCI/l5gCPR3D1nNXtWABUmBwvZpEQiD4IXSbIDq8BzLIK/7Ir5gTFSGZDUu37K5cMNp0hFtzO38sC7gWA==}
 
-  css-what@6.2.2:
-    resolution: {integrity: sha512-u/O3vwbptzhMs3L1fQE82ZSLHQQfto5gyZzwteVIEyeaY5Fc7R4dapF/BvRoSYFeqfBk4m0V1Vafq5Pjv25wvA==}
-    engines: {node: '>= 6'}
+  scheduler@0.28.0:
+    resolution: {integrity: sha512-juorfCmIkIw8tT+p5BXSm6PJjQF/ycEYmKyzURCIt/RaZIhL+PulbQ9Yu2z1HdOJDdqDTlxA1+xKBmHXJsczAw==}
 
-  cssdb@8.9.0:
-    resolution: {integrity: sha512-J8jOU/hLjaXcO1LldOLraJSQpfLXRKof0I7mtbRyOy2AAXgqst0x9rlgi2qXeD6d0ou3ZLqcPAMqYVbpCbrxEw==}
+  semver@7.7.4:
+    resolution: {integrity: sha512-vFKC2IEtQnVhpT78h1Yp8wzwrf8CM+MzKMHGJZfBtzhZNycRFnXsHk6E5TxIkkMsgNS7mdX3AGB7x2QM2di4lA==}
+    engines: {node: '>=10'}
+    hasBin: true
 
-  cssesc@3.0.0:
-    resolution: {integrity: sha512-/Tb/JcjK111nNScGob5MNtsntNM1aCNUDipB/TkwZFhyDrrE47SOx/18wF2bbjgc3ZzCSKW1T5nt5EbFoAz/Vg==}
-    engines: {node: '>=4'}
+  semver@7.8.5:
+    resolution: {integrity: sha512-Y7/KDsb8LjooZpwaqGyulO6DQlksgCncchHGk+sZIY4SBvUocMBEFH5Ur1fI4dV+Jvl0w6cjvucaIi40puRioA==}
+    engines: {node: '>=10'}
     hasBin: true
 
-  cssnano-preset-advanced@6.1.2:
-    resolution: {integrity: sha512-Nhao7eD8ph2DoHolEzQs5CfRpiEP0xa1HBdnFZ82kvqdmbwVBUr2r1QuQ4t1pi+D1ZpqpcO4T+wy/7RxzJ/WPQ==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
+  send@0.19.2:
+    resolution: {integrity: sha512-VMbMxbDeehAxpOtWJXlcUS5E8iXh6QmN+BkRX1GARS3wRaXEEgzCcB10gTQazO42tpNIya8xIyNx8fll1OFPrg==}
+    engines: {node: '>= 0.8.0'}
 
-  cssnano-preset-default@6.1.2:
-    resolution: {integrity: sha512-1C0C+eNaeN8OcHQa193aRgYexyJtU8XwbdieEjClw+J9d94E41LwT6ivKH0WT+fYwYWB0Zp3I3IZ7tI/BbUbrg==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
+  serialize-error@13.0.2:
+    resolution: {integrity: sha512-G+YKwp9I6IvWMe5RlwqxdmTPIcq/G8HK/sU51gdV1XAJznYkRSTB0ph+zB9AfSxG0fx6xrqYA6i9HeIcHFTXow==}
+    engines: {node: '>=20'}
 
-  cssnano-utils@4.0.2:
-    resolution: {integrity: sha512-ZR1jHg+wZ8o4c3zqf1SIUSTIvm/9mU343FMR6Obe/unskbvpGhZOo1J6d/r8D1pzkRQYuwbcH3hToOuoA2G7oQ==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
+  serve-static@1.16.3:
+    resolution: {integrity: sha512-x0RTqQel6g5SY7Lg6ZreMmsOzncHFU7nhnRWkKgWuMTu5NN0DR5oruckMqRvacAN9d5w6ARnRBXl9xhDCgfMeA==}
+    engines: {node: '>= 0.8.0'}
 
-  cssnano@6.1.2:
-    resolution: {integrity: sha512-rYk5UeX7VAM/u0lNqewCdasdtPK81CgX8wJFLEIXHbV2oldWRgJAsZrdhRXkV1NJzA2g850KiFm9mMU2HxNxMA==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
+  set-function-length@1.2.2:
+    resolution: {integrity: sha512-pgRc4hJ4/sNjWCSS9AmnS40x3bNMDTknHgL5UaMBTMyJnU90EgWh1Rz+MC9eFu4BuN/UwZjKQuY/1v3rM7HMfg==}
+    engines: {node: '>= 0.4'}
 
-  csso@5.0.5:
-    resolution: {integrity: sha512-0LrrStPOdJj+SPCCrGhzryycLjwcgUSHBtxNA8aIDxf0GLsRh1cKYhB00Gd1lDOS4yGH69+SNn13+TWbVHETFQ==}
-    engines: {node: ^10 || ^12.20.0 || ^14.13.0 || >=15.0.0, npm: '>=7.0.0'}
+  set-function-name@2.0.2:
+    resolution: {integrity: sha512-7PGFlmtwsEADb0WYyvCMa1t+yke6daIG4Wirafur5kcf+MhUnPms1UeR0CKQdTZD81yESwMHbtn+TR+dMviakQ==}
+    engines: {node: '>= 0.4'}
 
-  csstype@3.2.3:
-    resolution: {integrity: sha512-z1HGKcYy2xA8AGQfwrn0PAy+PB7X/GSj3UVJW9qKyn43xWa+gl5nXmU4qqLMRzWVLFC8KusUX8T/0kCiOYpAIQ==}
+  set-proto@1.0.0:
+    resolution: {integrity: sha512-RJRdvCo6IAnPdsvP/7m6bsQqNnn1FCBX5ZNtFL98MmFF/4xAIJTIg1YbHW5DC2W5SKZanrC6i4HsJqlajw/dZw==}
+    engines: {node: '>= 0.4'}
 
-  cytoscape-cose-bilkent@4.1.0:
-    resolution: {integrity: sha512-wgQlVIUJF13Quxiv5e1gstZ08rnZj2XaLHGoFMYXz7SkNfCDOOteKBE6SYRfA9WxxI/iBc3ajfDoc6hb/MRAHQ==}
-    peerDependencies:
-      cytoscape: ^3.2.0
+  setprototypeof@1.2.0:
+    resolution: {integrity: sha512-E5LDX7Wrp85Kil5bhZv46j8jOeboKq5JMmYM3gVGdGH8xFpPWXUMsNrlODCrkoxMEeNi/XZIwuRvY4XNwYMJpw==}
 
-  cytoscape-fcose@2.2.0:
-    resolution: {integrity: sha512-ki1/VuRIHFCzxWNrsshHYPs6L7TvLu3DL+TyIGEsRcvVERmxokbf5Gdk7mFxZnTdiGtnA4cfSmjZJMviqSuZrQ==}
-    peerDependencies:
-      cytoscape: ^3.2.0
+  sharp-ico@0.1.5:
+    resolution: {integrity: sha512-a3jODQl82NPp1d5OYb0wY+oFaPk7AvyxipIowCHk7pBsZCWgbe0yAkU2OOXdoH0ENyANhyOQbs9xkAiRHcF02Q==}
 
-  cytoscape@3.34.0:
-    resolution: {integrity: sha512-62rNSrioXw93uliKFBwjukeQyeWwH2PqDrTac31r2P6464u3AUvTk0xS4LVvT251g7IgkFunrI48ZEZGjywSOg==}
-    engines: {node: '>=0.10'}
+  sharp@0.33.5:
+    resolution: {integrity: sha512-haPVm1EkS9pgvHrQ/F3Xy+hgcuMV0Wm9vfIBSiwZ05k+xgb0PkBQpGsAA/oWdDobNaZTH5ppvHtzCFbnSEwHVw==}
+    engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
 
-  d3-array@2.12.1:
-    resolution: {integrity: sha512-B0ErZK/66mHtEsR1TkPEEkwdy+WDesimkM5gpZr5Dsg54BiTA5RXtYW5qTLIAcekaS9xfZrzBLF/OAkB3Qn1YQ==}
+  shebang-command@2.0.0:
+    resolution: {integrity: sha512-kHxr2zZpYtdmrN1qDjrrX/Z1rR1kG8Dx+gkpK1G4eXmvXswmcE1hTWBWYUzlraYw1/yZp6YuDY77YtvbN0dmDA==}
+    engines: {node: '>=8'}
 
-  d3-array@3.2.4:
-    resolution: {integrity: sha512-tdQAmyA18i4J7wprpYq8ClcxZy3SC31QMeByyCFyRt7BVHdREQZ5lpzoe5mFEYZUWe+oq8HBvk9JjpibyEV4Jg==}
-    engines: {node: '>=12'}
+  shebang-regex@3.0.0:
+    resolution: {integrity: sha512-7++dFhtcx3353uBaq8DDR4NuxBetBzC7ZQOhmTQInHEd6bSrXdiEyzCvG07Z44UYdLShWUyXt5M/yhz8ekcb1A==}
+    engines: {node: '>=8'}
 
-  d3-axis@3.0.0:
-    resolution: {integrity: sha512-IH5tgjV4jE/GhHkRV0HiVYPDtvfjHQlQfJHs0usq7M30XcSBvOotpmH1IgkcXsO/5gEQZD43B//fc7SRT5S+xw==}
-    engines: {node: '>=12'}
+  shiki@3.23.0:
+    resolution: {integrity: sha512-55Dj73uq9ZXL5zyeRPzHQsK7Nbyt6Y10k5s7OjuFZGMhpp4r/rsLBH0o/0fstIzX1Lep9VxefWljK/SKCzygIA==}
 
-  d3-brush@3.0.0:
-    resolution: {integrity: sha512-ALnjWlVYkXsVIGlOsuWH1+3udkYFI48Ljihfnh8FZPF2QS9o+PzGLBslO0PjzVoHLZ2KCVgAM8NVkXPJB2aNnQ==}
-    engines: {node: '>=12'}
+  side-channel-list@1.0.1:
+    resolution: {integrity: sha512-mjn/0bi/oUURjc5Xl7IaWi/OJJJumuoJFQJfDDyO46+hBWsfaVM65TBHq2eoZBhzl9EchxOijpkbRC8SVBQU0w==}
+    engines: {node: '>= 0.4'}
 
-  d3-chord@3.0.1:
-    resolution: {integrity: sha512-VE5S6TNa+j8msksl7HwjxMHDM2yNK3XCkusIlpX5kwauBfXuyLAtNg9jCp/iHH61tgI4sb6R/EIMWCqEIdjT/g==}
-    engines: {node: '>=12'}
+  side-channel-map@1.0.1:
+    resolution: {integrity: sha512-VCjCNfgMsby3tTdo02nbjtM/ewra6jPHmpThenkTYh8pG9ucZ/1P8So4u4FGBek/BjpOVsDCMoLA/iuBKIFXRA==}
+    engines: {node: '>= 0.4'}
 
-  d3-color@3.1.0:
-    resolution: {integrity: sha512-zg/chbXyeBtMQ1LbD/WSoW2DpC3I0mpmPdW+ynRTj/x2DAWYrIY7qeZIHidozwV24m4iavr15lNwIwLxRmOxhA==}
-    engines: {node: '>=12'}
+  side-channel-weakmap@1.0.2:
+    resolution: {integrity: sha512-WPS/HvHQTYnHisLo9McqBHOJk2FkHO/tlpvldyrnem4aeQp4hai3gythswg6p01oSoTl58rcpiFAjF2br2Ak2A==}
+    engines: {node: '>= 0.4'}
 
-  d3-contour@4.0.2:
-    resolution: {integrity: sha512-4EzFTRIikzs47RGmdxbeUvLWtGedDUNkTcmzoeyg4sP/dvCexO47AaQL7VKy/gul85TOxw+IBgA8US2xwbToNA==}
-    engines: {node: '>=12'}
+  side-channel@1.1.1:
+    resolution: {integrity: sha512-6x6dK6zJdpTzF4sQeNYxwtvBzf6Eg4GtlesS94HOvTudUeyK2WXAaIfmDgsyslYrRBeFIlsi54AYsFGUuhmvrQ==}
+    engines: {node: '>= 0.4'}
 
-  d3-delaunay@6.0.4:
-    resolution: {integrity: sha512-mdjtIZ1XLAM8bm/hx3WwjfHt6Sggek7qH043O8KEjDXN40xi3vx/6pYSVTwLjEgiXQTbvaouWKynLBiUZ6SK6A==}
-    engines: {node: '>=12'}
+  signal-exit@3.0.7:
+    resolution: {integrity: sha512-wnD2ZE+l+SPC/uoS0vXeE9L1+0wuaMqKlfz9AMUo38JsyLSBWSFcHR1Rri62LZc12vLr1gb3jl7iwQhgwpAbGQ==}
 
-  d3-dispatch@3.0.1:
-    resolution: {integrity: sha512-rzUyPU/S7rwUflMyLc1ETDeBj0NRuHKKAcvukozwhshr6g6c5d8zh4c2gQjY2bZ0dXeGLWc1PF174P2tVvKhfg==}
-    engines: {node: '>=12'}
+  signal-exit@4.1.0:
+    resolution: {integrity: sha512-bzyZ1e88w9O1iNJbKnOlvYTrWPDl46O1bG0D3XInv+9tkPrxrN8jUUTiFlDkkmKWgn1M6CfIA13SuGqOa9Korw==}
+    engines: {node: '>=14'}
 
-  d3-drag@3.0.0:
-    resolution: {integrity: sha512-pWbUJLdETVA8lQNJecMxoXfH6x+mO2UQo8rSmZ+QqxcbyA3hfeprFgIT//HW2nlHChWeIIMwS2Fq+gEARkhTkg==}
-    engines: {node: '>=12'}
+  simple-concat@1.0.1:
+    resolution: {integrity: sha512-cSFtAPtRhljv69IK0hTVZQ+OfE9nePi/rtJmw5UjHeVyVroEqJXP1sFztKUy1qU+xvz3u/sfYJLa947b7nAN2Q==}
 
-  d3-dsv@3.0.1:
-    resolution: {integrity: sha512-UG6OvdI5afDIFP9w4G0mNq50dSOsXHJaRE8arAS5o9ApWnIElp8GZw1Dun8vP8OyHOZ/QJUKUJwxiiCCnUwm+Q==}
-    engines: {node: '>=12'}
-    hasBin: true
+  simple-get@4.0.1:
+    resolution: {integrity: sha512-brv7p5WgH0jmQJr1ZDDfKDOSeWWg+OVypG99A/5vYGPqJ6pxiaHLy8nxtFjBA7oMa01ebA9gfh1uMCFqOuXxvA==}
 
-  d3-ease@3.0.1:
-    resolution: {integrity: sha512-wR/XK3D3XcLIZwpbvQwQ5fK+8Ykds1ip7A2Txe0yxncXSdq1L9skcG7blcedkOX+ZcgxGAmLX1FrRGbADwzi0w==}
-    engines: {node: '>=12'}
+  simple-swizzle@0.2.4:
+    resolution: {integrity: sha512-nAu1WFPQSMNr2Zn9PGSZK9AGn4t/y97lEm+MXTtUDwfP0ksAIX4nO+6ruD9Jwut4C49SB1Ws+fbXsm/yScWOHw==}
 
-  d3-fetch@3.0.1:
-    resolution: {integrity: sha512-kpkQIM20n3oLVBKGg6oHrUchHM3xODkTzjMoj7aWQFq5QEM+R6E4WkzT5+tojDY7yjez8KgCBRoj4aEr99Fdqw==}
+  slice-ansi@5.0.0:
+    resolution: {integrity: sha512-FC+lgizVPfie0kkhqUScwRu1O/lF6NOgJmlCgK+/LYxDCTk8sGelYaHDhFcDN+Sn3Cv+3VSa4Byeo+IMCzpMgQ==}
     engines: {node: '>=12'}
 
-  d3-force@3.0.0:
-    resolution: {integrity: sha512-zxV/SsA+U4yte8051P4ECydjD/S+qeYtnaIyAs9tgHCqfguma/aAQDjo85A9Z6EKhBirHRJHXIgJUlffT4wdLg==}
-    engines: {node: '>=12'}
+  slice-ansi@7.1.2:
+    resolution: {integrity: sha512-iOBWFgUX7caIZiuutICxVgX1SdxwAVFFKwt1EvMYYec/NWO5meOJ6K5uQxhrYBdQJne4KxiqZc+KptFOWFSI9w==}
+    engines: {node: '>=18'}
 
-  d3-format@3.1.2:
-    resolution: {integrity: sha512-AJDdYOdnyRDV5b6ArilzCPPwc1ejkHcoyFarqlPqT7zRYjhavcT3uSrqcMvsgh2CgoPbK3RCwyHaVyxYcP2Arg==}
-    engines: {node: '>=12'}
+  socket.io-adapter@2.5.8:
+    resolution: {integrity: sha512-6Oy52pbg+kvdCVvjcN+FnY7BvxZ7cIHNScbvztT/It5d0vbwoJoVZmF2gjJmnV0/4WlXRfG15zc45ySk9Ah8bw==}
 
-  d3-geo@3.1.1:
-    resolution: {integrity: sha512-637ln3gXKXOwhalDzinUgY83KzNWZRKbYubaG+fGVuc/dxO64RRljtCTnf5ecMyE1RIdtqpkVcq0IbtU2S8j2Q==}
-    engines: {node: '>=12'}
+  socket.io-parser@4.2.7:
+    resolution: {integrity: sha512-IH/iSeO9T6gz1KkFleGDWkG9N3dl4jXVYUtMhIqH10Md0ttMer8nUNWiP1DKuNrybD2xBrixLJdCC9J6ECoYkg==}
+    engines: {node: '>=10.0.0'}
 
-  d3-hierarchy@3.1.2:
-    resolution: {integrity: sha512-FX/9frcub54beBdugHjDCdikxThEqjnR93Qt7PvQTOHxyiNCAlvMrHhclk3cD5VeAaq9fxmfRp+CnWw9rEMBuA==}
-    engines: {node: '>=12'}
+  socket.io@4.8.0:
+    resolution: {integrity: sha512-8U6BEgGjQOfGz3HHTYaC/L1GaxDCJ/KM0XTkJly0EhZ5U/du9uNEZy4ZgYzEzIqlx2CMm25CrCqr1ck899eLNA==}
+    engines: {node: '>=10.2.0'}
 
-  d3-interpolate@3.0.1:
-    resolution: {integrity: sha512-3bYs1rOD33uo8aqJfKP3JWPAibgw8Zm2+L9vBKEHJ2Rg+viTR7o5Mmv5mZcieN+FRYaAOWX5SJATX6k1PWz72g==}
-    engines: {node: '>=12'}
+  source-map-js@1.2.2:
+    resolution: {integrity: sha512-KGj/8Y43x35aZVDtt+J4mK1hoLGHULMYfSkODJNQjNDC3oW1PqPoxMwo0pLUsWM/UEGzON/NxeHywEfNXNP3Vw==}
+    engines: {node: '>=0.10.0'}
 
-  d3-path@1.0.9:
-    resolution: {integrity: sha512-VLaYcn81dtHVTjEHd8B+pbe9yHWpXKZUC87PzoFmsFrJqgFwDe/qxfp5MlfsfM1V5E/iVt0MmEbWQ7FVIXh/bg==}
+  source-map@0.7.6:
+    resolution: {integrity: sha512-i5uvt8C3ikiWeNZSVZNWcfZPItFQOsYTUAOkcUPGd8DqDy1uOUikjt5dG+uRlwyvR108Fb9DOd4GvXfT0N2/uQ==}
+    engines: {node: '>= 12'}
 
-  d3-path@3.1.0:
-    resolution: {integrity: sha512-p3KP5HCf/bvjBSSKuXid6Zqijx7wIfNW+J/maPs+iwR35at5JCbLUT0LzF1cnjbCHWhqzQTIN2Jpe8pRebIEFQ==}
-    engines: {node: '>=12'}
+  space-separated-tokens@2.0.2:
+    resolution: {integrity: sha512-PEGlAwrG8yXGXRjW32fGbg66JAlOAwbObuqVoJpv/mRgoWDQfgH1wDPvtzWyUSNAXBGSk8h755YDbbcEy3SH2Q==}
 
-  d3-polygon@3.0.1:
-    resolution: {integrity: sha512-3vbA7vXYwfe1SYhED++fPUQlWSYTTGmFmQiany/gdbiWgU/iEyQzyymwL9SkJjFFuCS4902BSzewVGsHHmHtXg==}
-    engines: {node: '>=12'}
+  sprintf-js@1.0.3:
+    resolution: {integrity: sha512-D9cPgkvLlV3t3IzL0D0YLvGA9Ahk4PcvVwUbN0dSGr1aP0Nrt4AEnTUbuGvquEC0mA64Gqt1fzirlRs5ibXx8g==}
 
-  d3-quadtree@3.0.1:
-    resolution: {integrity: sha512-04xDrxQTDTCFwP5H6hRhsRcb9xxv2RzkcsygFzmkSIOJy3PeRJP7sNk3VRIbKXcog561P9oU0/rVH6vDROAgUw==}
-    engines: {node: '>=12'}
+  stack-utils@2.0.6:
+    resolution: {integrity: sha512-XlkWvfIm6RmsWtNJx+uqtKLS8eqFbxUg0ZzLXqY0caEy9l7hruX8IpiDnjsLavoBgqCCR71TqWO8MaXYheJ3RQ==}
+    engines: {node: '>=10'}
 
-  d3-random@3.0.1:
-    resolution: {integrity: sha512-FXMe9GfxTxqd5D6jFsQ+DJ8BJS4E/fT5mqqdjovykEB2oFbTMDVdg1MGFxfQW+FBOGoB++k8swBrgwSHT1cUXQ==}
-    engines: {node: '>=12'}
+  statuses@2.0.2:
+    resolution: {integrity: sha512-DvEy55V3DB7uknRo+4iOGT5fP1slR8wQohVdknigZPMpMstaKJQWhwiYBACJE3Ul2pTnATihhBYnRhZQHGBiRw==}
+    engines: {node: '>= 0.8'}
 
-  d3-sankey@0.12.3:
-    resolution: {integrity: sha512-nQhsBRmM19Ax5xEIPLMY9ZmJ/cDvd1BG3UVvt5h3WRxKg5zGRbvnteTyWAbzeSvlh3tW7ZEmq4VwR5mB3tutmQ==}
+  stop-iteration-iterator@1.1.0:
+    resolution: {integrity: sha512-eLoXW/DHyl62zxY4SCaIgnRhuMr6ri4juEYARS8E6sCEqzKpOiE521Ucofdx+KnDZl5xmvGYaaKCk5FEOxJCoQ==}
+    engines: {node: '>= 0.4'}
 
-  d3-scale-chromatic@3.1.0:
-    resolution: {integrity: sha512-A3s5PWiZ9YCXFye1o246KoscMWqf8BsD9eRiJ3He7C9OBaxKhAd5TFCdEx/7VbKtxxTsu//1mMJFrEt572cEyQ==}
-    engines: {node: '>=12'}
+  string-width@4.2.3:
+    resolution: {integrity: sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==}
+    engines: {node: '>=8'}
 
-  d3-scale@4.0.2:
-    resolution: {integrity: sha512-GZW464g1SH7ag3Y7hXjf8RoUuAFIqklOAq3MRl4OaWabTFJY9PN/E1YklhXLh+OQ3fM9yS2nOkCoS+WLZ6kvxQ==}
-    engines: {node: '>=12'}
+  string-width@7.2.0:
+    resolution: {integrity: sha512-tsaTIkKW9b4N+AEj+SVA+WhJzV7/zMhcSu78mLKWSk7cXMOSHsBKFWUs0fWwq8QyK3MgJBQRX6Gbi4kYbdvGkQ==}
+    engines: {node: '>=18'}
 
-  d3-selection@3.0.0:
-    resolution: {integrity: sha512-fmTRWbNMmsmWq6xJV8D19U/gw/bwrHfNXxrIN+HfZgnzqTHp9jOmKMhsTUjXOJnZOdZY9Q28y4yebKzqDKlxlQ==}
-    engines: {node: '>=12'}
+  string.prototype.codepointat@0.2.1:
+    resolution: {integrity: sha512-2cBVCj6I4IOvEnjgO/hWqXjqBGsY+zwPmHl12Srk9IXSZ56Jwwmy+66XO5Iut/oQVR7t5ihYdLB0GMa4alEUcg==}
 
-  d3-shape@1.3.7:
-    resolution: {integrity: sha512-EUkvKjqPFUAZyOlhY5gzCxCeI0Aep04LwIRpsZ/mLFelJiUfnK56jo5JMDSE7yyP2kLSb6LtF+S5chMk7uqPqw==}
+  string.prototype.trim@1.2.11:
+    resolution: {integrity: sha512-PwvK7BU+CMTJGYQCTZb5RWXIML92lftJLhQz1tBzgKiqGxJaMlBAa48POXaNAC2s4y8jr3EFqrkF9+44neS46w==}
+    engines: {node: '>= 0.4'}
 
-  d3-shape@3.2.0:
-    resolution: {integrity: sha512-SaLBuwGm3MOViRq2ABk3eLoxwZELpH6zhl3FbAoJ7Vm1gofKx6El1Ib5z23NUEhF9AsGl7y+dzLe5Cw2AArGTA==}
-    engines: {node: '>=12'}
+  string.prototype.trimend@1.0.10:
+    resolution: {integrity: sha512-2+3aDAOmPTmuFwjDnmJG2ctEkQKVki7vOSqaxkv42Mowj1V6PnvuwFCRrR5lChUux1TBskPjfkeTOhqczDMxTw==}
+    engines: {node: '>= 0.4'}
 
-  d3-time-format@4.1.0:
-    resolution: {integrity: sha512-dJxPBlzC7NugB2PDLwo9Q8JiTR3M3e4/XANkreKSUxF8vvXKqm1Yfq4Q5dl8budlunRVlUUaDUgFt7eA8D6NLg==}
-    engines: {node: '>=12'}
+  string.prototype.trimstart@1.0.8:
+    resolution: {integrity: sha512-UXSH262CSZY1tfu3G3Secr6uGLCFVPMhIqHjlgCUtCCcgihYc/xKs9djMTMUOb2j1mVSeU8EU6NWc/iQKU6Gfg==}
+    engines: {node: '>= 0.4'}
 
-  d3-time@3.1.0:
-    resolution: {integrity: sha512-VqKjzBLejbSMT4IgbmVgDjpkYrNWUYJnbCGo874u7MMKIWsILRX+OpX/gTk8MqjpT1A/c6HY2dCA77ZN0lkQ2Q==}
-    engines: {node: '>=12'}
+  string_decoder@1.3.0:
+    resolution: {integrity: sha512-hkRX8U1WjJFd8LsDJ2yQ/wWWxaopEsABU1XfkM8A+j0+85JAGppt16cr1Whg6KIbb4okU6Mql6BOj+uup/wKeA==}
 
-  d3-timer@3.0.1:
-    resolution: {integrity: sha512-ndfJ/JxxMd3nw31uyKoY2naivF+r29V+Lc0svZxe1JvvIRmi8hUsrMvdOwgS1o6uBHmiz91geQ0ylPP0aj1VUA==}
-    engines: {node: '>=12'}
+  stringify-entities@4.0.4:
+    resolution: {integrity: sha512-IwfBptatlO+QCJUo19AqvrPNqlVMpW9YEL2LIVY+Rpv2qsjCGxaDLNRgeGsQWJhfItebuJhsGSLjaBbNSQ+ieg==}
 
-  d3-transition@3.0.1:
-    resolution: {integrity: sha512-ApKvfjsSR6tg06xrL434C0WydLr7JewBB3V+/39RMHsaXTOG0zmt/OAXeng5M5LBm0ojmxJrpomQVZ1aPvBL4w==}
-    engines: {node: '>=12'}
-    peerDependencies:
-      d3-selection: 2 - 3
+  strip-ansi@6.0.1:
+    resolution: {integrity: sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==}
+    engines: {node: '>=8'}
 
-  d3-zoom@3.0.0:
-    resolution: {integrity: sha512-b8AmV3kfQaqWAuacbPuNbL6vahnOJflOhexLzMMNLga62+/nh0JzvJ0aO/5a5MVgUFGS7Hu1P9P03o3fJkDCyw==}
+  strip-ansi@7.2.0:
+    resolution: {integrity: sha512-yDPMNjp4WyfYBkHnjIRLfca1i6KMyGCtsVgoKe/z1+6vukgaENdgGBZt+ZmKPc4gavvEZ5OgHfHdrazhgNyG7w==}
     engines: {node: '>=12'}
 
-  d3@7.9.0:
-    resolution: {integrity: sha512-e1U46jVP+w7Iut8Jt8ri1YsPOvFpg46k+K8TpCb0P+zjCkjkPnV7WzfDJzMHy1LnA+wj5pLT1wjO901gLXeEhA==}
-    engines: {node: '>=12'}
+  strip-json-comments@2.0.1:
+    resolution: {integrity: sha512-4gB8na07fecVVkOI6Rs4e7T6NOTki5EmL7TUduTs6bu3EdnSycntVJ4re8kgZA+wx9IueI2Y11bfbgwtzuE0KQ==}
+    engines: {node: '>=0.10.0'}
 
-  dagre-d3-es@7.0.14:
-    resolution: {integrity: sha512-P4rFMVq9ESWqmOgK+dlXvOtLwYg0i7u0HBGJER0LZDJT2VHIPAMZ/riPxqJceWMStH5+E61QxFra9kIS3AqdMg==}
+  strnum@2.5.1:
+    resolution: {integrity: sha512-UM4nTLWzQiDBseVxUGxN0wJzIk0UU89Qi7pKXz9qISo+lhviJikTuikBsK/oFRlpvYHvSdz0TVoLyQ+sEpYwxA==}
 
-  dayjs@1.11.21:
-    resolution: {integrity: sha512-98IT+HOahAisibz/yjKbzuOBwYcjJ7BCLPzARyHiyEBmRz4fatF+KPJszEHXsGYjUG234aH/cOjW1wwTbKUZlA==}
+  style-to-js@1.1.21:
+    resolution: {integrity: sha512-RjQetxJrrUJLQPHbLku6U/ocGtzyjbJMP9lCNK7Ag0CNh690nSH8woqWH9u16nMjYBAok+i7JO1NP2pOy8IsPQ==}
 
-  debounce@1.2.1:
-    resolution: {integrity: sha512-XRRe6Glud4rd/ZGQfiV1ruXSfbvfJedlV9Y6zOlP+2K04vBYiJEte6stfFkCP03aMnY5tsipamumUjL14fofug==}
+  style-to-object@0.4.4:
+    resolution: {integrity: sha512-HYNoHZa2GorYNyqiCaBgsxvcJIn7OHq6inEga+E6Ke3m5JkoqpQbnFssk4jwe+K7AhGa2fcha4wSOf1Kn01dMg==}
 
-  debug@2.6.9:
-    resolution: {integrity: sha512-bC7ElrdJaJnPbAP+1EotYvqZsb3ecl5wi6Bfi6BJTUcNowp6cvspg0jXznRTKDjm/E7AdgFBVeAPVMNcKGsHMA==}
-    peerDependencies:
-      supports-color: '*'
-    peerDependenciesMeta:
-      supports-color:
-        optional: true
+  style-to-object@1.0.14:
+    resolution: {integrity: sha512-LIN7rULI0jBscWQYaSswptyderlarFkjQ+t79nzty8tcIAceVomEVlLzH5VP4Cmsv6MtKhs7qaAiwlcp+Mgaxw==}
 
-  debug@4.4.3:
-    resolution: {integrity: sha512-RGwwWnwQvkVfavKVt22FGLw+xYSdzARwm0ru6DhTVA3umU5hZc28V3kO4stgYryrTlLpuvgI9GiijltAjNbcqA==}
-    engines: {node: '>=6.0'}
-    peerDependencies:
-      supports-color: '*'
-    peerDependenciesMeta:
-      supports-color:
-        optional: true
+  sucrase@3.34.0:
+    resolution: {integrity: sha512-70/LQEZ07TEcxiU2dz51FKaE6hCTWC6vr7FOk3Gr0U60C3shtAN+H+BFr9XlYe5xqf3RA8nrc+VIwzCfnxuXJw==}
+    engines: {node: '>=8'}
+    hasBin: true
 
-  decode-named-character-reference@1.3.0:
-    resolution: {integrity: sha512-GtpQYB283KrPp6nRw50q3U9/VfOutZOe103qlN7BPP6Ad27xYnOIWv4lPzo8HCAL+mMZofJ9KEy30fq6MfaK6Q==}
+  sucrase@3.35.1:
+    resolution: {integrity: sha512-DhuTmvZWux4H1UOnWMB3sk0sbaCVOoQZjv8u1rDoTV0HTdGem9hkAZtl4JZy8P2z4Bg0nT+YMeOFyVr4zcG5Tw==}
+    engines: {node: '>=16 || 14 >=14.17'}
+    hasBin: true
 
-  decompress-response@6.0.0:
-    resolution: {integrity: sha512-aW35yZM6Bb/4oJlZncMH2LCoZtJXTRxES17vE3hoRiowU2kWHaJKFkSBDnDR+cm9J+9QhXmREyIfv0pji9ejCQ==}
-    engines: {node: '>=10'}
+  supports-preserve-symlinks-flag@1.0.0:
+    resolution: {integrity: sha512-ot0WnXS9fgdkgIcePe6RHNk1WA8+muPa6cSjeR3V8K27q9BB1rTE3R1p7Hv0z1ZyAc8s6Vvv8DIyWf681MAt0w==}
+    engines: {node: '>= 0.4'}
 
-  deep-extend@0.6.0:
-    resolution: {integrity: sha512-LOHxIOaPYdHlJRtCQfDIVZtfw/ufM8+rVj649RIHzcm/vGwQRXFt6OPqIFWsm2XEMrNIEtWR64sY1LEKD2vAOA==}
-    engines: {node: '>=4.0.0'}
+  tagged-tag@1.0.0:
+    resolution: {integrity: sha512-yEFYrVhod+hdNyx7g5Bnkkb0G6si8HJurOoOEgC8B/O0uXLHlaey/65KRv6cuWBNhBgHKAROVpc7QyYqE5gFng==}
+    engines: {node: '>=20'}
 
-  deep-is@0.1.4:
-    resolution: {integrity: sha512-oIPzksmTg4/MriiaYGO+okXDT7ztn/w3Eptv/+gSIdMdKsJo0u4CfYNFJPy+4SKMuCqGw2wxnA+URMg3t8a/bQ==}
+  tailwindcss@3.4.17:
+    resolution: {integrity: sha512-w33E2aCvSDP0tW9RZuNXadXlkHXqFzSkQew/aIa2i/Sj8fThxwovwlXHSPXTbAHwEIhBFXAedUhP2tueAKP8Og==}
+    engines: {node: '>=14.0.0'}
+    hasBin: true
 
-  deepmerge@4.3.1:
-    resolution: {integrity: sha512-3sUqbMEc77XqpdNO7FRyRog+eW3ph+GYCbj+rK+uYyRMuwsVy0rMiVtPn+QJlKFvWP/1PYpapqYn0Me2knFn+A==}
-    engines: {node: '>=0.10.0'}
+  tar-fs@2.1.5:
+    resolution: {integrity: sha512-OboTd8mmMhZDNPV+UjQcK9yKAatXu2aJ+r1w4im1Otd4M4fl2hwvdoXUxIYHFTHWK/3y3FarBP70v3vwmGlOxw==}
 
-  default-browser-id@5.0.1:
-    resolution: {integrity: sha512-x1VCxdX4t+8wVfd1so/9w+vQ4vx7lKd2Qp5tDRutErwmR85OgmfX7RlLRMWafRMY7hbEiXIbudNrjOAPa/hL8Q==}
-    engines: {node: '>=18'}
+  tar-stream@2.2.0:
+    resolution: {integrity: sha512-ujeqbceABgwMZxEJnk2HDY2DlnUZ+9oEcb1KzTVfYHio0UE6dG71n60d8D2I4qNvleWrrXpmjpt7vZeF1LnMZQ==}
+    engines: {node: '>=6'}
 
-  default-browser@5.5.0:
-    resolution: {integrity: sha512-H9LMLr5zwIbSxrmvikGuI/5KGhZ8E2zH3stkMgM5LpOWDutGM2JZaj460Udnf1a+946zc7YBgrqEWwbk7zHvGw==}
+  tar@7.5.21:
+    resolution: {integrity: sha512-XdhtCvlMywwxpCW8YEq3lOXBJpUPTR2OHHcwLPO3HwsJqOHa2Ok/oJ7ruGzp+JrKoRPVCzJwAdEjqLW/vNRPHA==}
     engines: {node: '>=18'}
 
-  defer-to-connect@2.0.1:
-    resolution: {integrity: sha512-4tvttepXG1VaYGrRibk5EwJd1t4udunSOVMdLSAL6mId1ix438oPwPZMALY41FCijukO1L0twNcGsdzS7dHgDg==}
-    engines: {node: '>=10'}
+  thenify-all@1.6.0:
+    resolution: {integrity: sha512-RNxQH/qI8/t3thXJDwcstUO4zeqo64+Uy/+sNVRBx4Xn2OX+OZ9oP+iJnNFqplFra2ZUVeKCSa2oVWi3T4uVmA==}
+    engines: {node: '>=0.8'}
 
-  define-data-property@1.1.4:
-    resolution: {integrity: sha512-rBMvIzlpA8v6E+SJZoo++HAYqsLrkg7MSfIinMPFhmkorw7X+dOXVJQs+QT69zGkzMyfDnIMN2Wid1+NbL3T+A==}
-    engines: {node: '>= 0.4'}
+  thenify@3.3.1:
+    resolution: {integrity: sha512-RVZSIV5IG10Hk3enotrhvz0T9em6cyHBLkH/YAZuKqd8hRkKhSfCGIcP2KUY0EPxndzANBmNllzWPwak+bheSw==}
 
-  define-lazy-prop@2.0.0:
-    resolution: {integrity: sha512-Ds09qNh8yw3khSjiJjiUInaGX9xlqZDY7JVryGxdxV7NPeuqQfplOpQ66yJFZut3jLa5zOwkXw1g9EI2uKh4Og==}
-    engines: {node: '>=8'}
+  tiny-inflate@1.0.3:
+    resolution: {integrity: sha512-pkY1fj1cKHb2seWDy0B16HeWyczlJA9/WW3u3c4z/NiWDsO3DOU5D7nhTLE9CF0yXv/QZFY7sEJmj24dK+Rrqw==}
 
-  define-lazy-prop@3.0.0:
-    resolution: {integrity: sha512-N+MeXYoqr3pOgn8xfyRPREN7gHakLYjhsHhWGT3fWAiL4IkAt0iDw14QiiEm2bE30c5XX5q0FtAA3CK5f9/BUg==}
-    engines: {node: '>=12'}
+  tinyglobby@0.2.17:
+    resolution: {integrity: sha512-wXR/dYpcqKmfWpEdZjiKJOwCNFndD0DMnrW/cYjVGttEkBfVgcLFHoNrlj47mjOVic9yyNu65alsgF4NQyTa2g==}
+    engines: {node: '>=12.0.0'}
 
-  define-properties@1.2.1:
-    resolution: {integrity: sha512-8QmQKqEASLd5nx0U1B1okLElbUuuttJ/AnYmRXbbbGDWh6uS208EjD4Xqq/I9wK7u0v6O08XhTWnt5XtEbR6Dg==}
-    engines: {node: '>= 0.4'}
+  to-data-view@1.1.0:
+    resolution: {integrity: sha512-1eAdufMg6mwgmlojAx3QeMnzB/BTVp7Tbndi3U7ftcT2zCZadjxkkmLmd97zmaxWi+sgGcgWrokmpEoy0Dn0vQ==}
 
-  delaunator@5.1.0:
-    resolution: {integrity: sha512-AGrQ4QSgssa1NGmWmLPqN5NY2KajF5MqxetNEO+o0n3ZwZZeTmt7bBnvzHWrmkZFxGgr4HdyFgelzgi06otLuQ==}
+  to-regex-range@5.0.1:
+    resolution: {integrity: sha512-65P7iz6X5yEr1cwcgvQxbbIw7Uk3gOy5dIdtZ4rDveLqhrdJP+Li/Hx6tyK0NEb+2GCyneCMJiGqrADCSNk8sQ==}
+    engines: {node: '>=8.0'}
 
-  depd@1.1.2:
-    resolution: {integrity: sha512-7emPTl6Dpo6JRXOXjLRxck+FlLRX5847cLKEn00PLAgc3g2hTZZgr+e4c2v6QpSmLeFP3n5yUo7ft6avBK/5jQ==}
-    engines: {node: '>= 0.6'}
+  toidentifier@1.0.1:
+    resolution: {integrity: sha512-o5sSPKEkg/DIQNmH43V0/uerLrpzVedkUh8tGNvaeXpfpuwjKenlSox/2O/BTlZUtEe+JG7s5YhEz608PlAHRA==}
+    engines: {node: '>=0.6'}
 
-  depd@2.0.0:
-    resolution: {integrity: sha512-g7nH6P6dyDioJogAAGprGpCtVImJhpPk/roCzdb3fIh61/s/nPsfR6onyMwkCAR/OlC3yBC0lESvUoQEAssIrw==}
-    engines: {node: '>= 0.8'}
+  tr46@0.0.3:
+    resolution: {integrity: sha512-N3WMsuqV66lT30CrXNbEjx4GEwlow3v6rr4mCcv6prnfwhS01rkgyFdjPNBYd9br7LpXV1+Emh01fHnq2Gdgrw==}
 
-  dequal@2.0.3:
-    resolution: {integrity: sha512-0je+qPKHEMohvfRTCEo3CrPG6cAzAYgmzKyxRiYSSDkS6eGJdyVJm7WaYA5ECaAD9wLB2T4EEeymA5aFVcYXCA==}
-    engines: {node: '>=6'}
+  trim-lines@3.0.1:
+    resolution: {integrity: sha512-kRj8B+YHZCc9kQYdWfJB2/oUl9rA99qbowYYBtr4ui4mZyAQ2JpvVBd/6U2YloATfqBhBTSMhTpgBHtU0Mf3Rg==}
 
-  destroy@1.2.0:
-    resolution: {integrity: sha512-2sJGJTaXIIaR1w4iJSNoN0hnMY7Gpc/n8D4qSCJw8QqFWXf7cuAgnEHxBpweaVcPevC2l3KpjYCx3NypQQgaJg==}
-    engines: {node: '>= 0.8', npm: 1.2.8000 || >= 1.4.16}
+  trim-trailing-lines@2.1.0:
+    resolution: {integrity: sha512-5UR5Biq4VlVOtzqkm2AZlgvSlDJtME46uV0br0gENbwN4l5+mMKT4b9gJKqWtuL2zAIqajGJGuvbCbcAJUZqBg==}
 
-  detect-libc@2.1.2:
-    resolution: {integrity: sha512-Btj2BOOO83o3WyH59e8MgXsxEQVcarkUOpEYrubB0urwnN10yQ364rsiByU11nZlqWYZm05i/of7io4mzihBtQ==}
-    engines: {node: '>=8'}
+  trough@2.2.0:
+    resolution: {integrity: sha512-tmMpK00BjZiUyVyvrBK7knerNgmgvcV/KLVyuma/SC+TQN167GrMRciANTz09+k3zW8L8t60jWO1GpfkZdjTaw==}
 
-  detect-node@2.1.0:
-    resolution: {integrity: sha512-T0NIuQpnTvFDATNuHN5roPwSBG83rFsuO+MXXH9/3N1eFbn4wcPjttvjMLEPWJ0RGUYgQE7cGgS3tNxbqCGM7g==}
+  ts-interface-checker@0.1.13:
+    resolution: {integrity: sha512-Y/arvbn+rrz3JCKl9C4kVNfTfSm2/mEp5FSz5EsZSANGPSlQrpRI5M4PKF+mJnE52jOO90PnPSc3Ur3bTQw0gA==}
 
-  detect-package-manager@3.0.2:
-    resolution: {integrity: sha512-8JFjJHutStYrfWwzfretQoyNGoZVW1Fsrp4JO9spa7h/fBfwgTMEIy4/LBzRDGsxwVPHU0q+T9YvwLDJoOApLQ==}
-    engines: {node: '>=12'}
+  tslib@1.14.1:
+    resolution: {integrity: sha512-Xni35NKzjgMrwevysHTCArtLDpPvye8zV/0E4EyYn43P7/7qvQwPh9BGkHewbMulVntbigmcT7rdX3BNo9wRJg==}
 
-  detect-port@1.6.1:
-    resolution: {integrity: sha512-CmnVc+Hek2egPx1PeTFVta2W78xy2K/9Rkf6cC4T59S50tVnzKj+tnx5mmx5lwvCkujZ4uRrpRSuV+IVs3f90Q==}
-    engines: {node: '>= 4.0.0'}
-    hasBin: true
+  tslib@2.8.1:
+    resolution: {integrity: sha512-oJFu94HQb+KVduSUQL7wnpmqnfmLsOA/nAh6b6EH0wCEoK0/mPeXU6c3wKDV83MkOuHPRHtSXKKU99IBazS/2w==}
 
-  devlop@1.1.0:
-    resolution: {integrity: sha512-RWmIqhcFf1lRYBvNmr7qTNuyCt/7/ns2jbpp1+PalgE/rDQcBT0fioSMUpJ93irlUhC5hrg4cYqe6U+0ImW0rA==}
+  tunnel-agent@0.6.0:
+    resolution: {integrity: sha512-McnNiV1l8RYeY8tBgEpuodCC1mLUdbSN+CYBL7kJsJNInOP8UjDDEwdk6Mw60vdLLrr5NHKZhMAOSrR2NZuQ+w==}
 
-  diff@5.2.2:
-    resolution: {integrity: sha512-vtcDfH3TOjP8UekytvnHH1o1P4FcUdt4eQ1Y+Abap1tk/OB2MWQvcwS2ClCd1zuIhc3JKOx6p3kod8Vfys3E+A==}
-    engines: {node: '>=0.3.1'}
+  twoslash-protocol@0.3.9:
+    resolution: {integrity: sha512-9/iwp+CXOnjFMPQuPL5PkuRbZnDoNpBvtJCLs9t8kDYkL3YHujbvnHfZA1i5fApDftVEdBw+T/4F+dH5kIzpYQ==}
 
-  dir-glob@3.0.1:
-    resolution: {integrity: sha512-WkrWp9GR4KXfKGYzOLmTuGVi1UWFfws377n9cc55/tb6DuqyF6pcQ5AbiHEshaDpY9v6oaSr2XCDidGmMwdzIA==}
-    engines: {node: '>=8'}
+  twoslash@0.3.9:
+    resolution: {integrity: sha512-rDclk+OtzuTX+tnea7DYLCkqGQ3eP0IyfD+kzUJ7t46X/NzlaxwrhecmEBNuSCuEn3V+n1PhcjUUQQ7gUJzX5Q==}
+    peerDependencies:
+      typescript: ^5.5.0 || ^6.0.0
 
-  dns-packet@5.6.1:
-    resolution: {integrity: sha512-l4gcSouhcgIKRvyy99RNVOgxXiicE+2jZoNmaNmZ6JXiGajBOJAesk1OBlJuM5k2c+eudGdLxDqXuPCKIj6kpw==}
-    engines: {node: '>=6'}
+  type-fest@0.21.3:
+    resolution: {integrity: sha512-t0rzBq87m3fVcduHDUFhKmyyX+9eo6WQjZvf51Ea/M0Q7+T374Jp1aUiyUl0GKxp8M/OETVHSDvmkyPgvX+X2w==}
+    engines: {node: '>=10'}
 
-  docusaurus-markdown-source-plugin@2.2.5:
-    resolution: {integrity: sha512-UP/ilYJ66Yyt+8wjFzRK7xYLm6z4QxZy6fo6myvjtV5MNi1SKhbaPTBMD/sZjn2icCtsFlpwL+rf9JEpaw3VSA==}
-    engines: {node: '>=18.0.0'}
-    peerDependencies:
-      '@docusaurus/core': ^3.0.0
-      react: ^18.0.0 || ^19.0.0
-      react-dom: ^18.0.0 || ^19.0.0
+  type-fest@4.41.0:
+    resolution: {integrity: sha512-TeTSQ6H5YHvpqVwBRcnLDCBnDOHWYu7IvGbHT6N8AOymcr9PJGjc1GTtiWZTYg0NCgYwvnYWEkVChQAr9bjfwA==}
+    engines: {node: '>=16'}
 
-  docusaurus-plugin-llms@0.4.0:
-    resolution: {integrity: sha512-jYlj2HJ5+gu7oJZuJ83Hk8KlB65YlZZ/7UpHXiL7Qr+qpNBkVocmt2Molc6F3HNr5RqcfhWD/98CvgyNztg/ow==}
-    engines: {node: '>=18.0'}
-    peerDependencies:
-      '@docusaurus/core': ^3.0.0
+  type-fest@5.10.0:
+    resolution: {integrity: sha512-NoSdpq/WEiAg5sjmBkmV/hfxv6HJH4NqPNrqjtSO5CwRmpsDfaf4begxW34KdJykH/l1yHtwBWQkCRdoXO8mPA==}
+    engines: {node: '>=20'}
 
-  docusaurus-plugin-openapi-docs@5.1.0:
-    resolution: {integrity: sha512-ocRemE3KmdhhPKaow5hja1m1NLIPfNlfRYFt7pja+nG26Wlp0MEC9ERS99gSWEWaxU+txDFBpUXsxo7nGlk8ZA==}
-    engines: {node: '>=14'}
-    peerDependencies:
-      '@docusaurus/plugin-content-docs': ^3.10.0
-      '@docusaurus/utils': ^3.10.0
-      '@docusaurus/utils-validation': ^3.10.0
-      react: ^16.8.4 || ^17.0.0 || ^18.0.0 || ^19.0.0
+  type-is@1.6.18:
+    resolution: {integrity: sha512-TkRKr9sUTxEH8MdfuCSP7VizJyzRNMjj2J2do2Jr3Kym598JVdEksuzPQCnlFPW4ky9Q+iA+ma9BGm06XQBy8g==}
+    engines: {node: '>= 0.6'}
 
-  docusaurus-plugin-sass@0.2.6:
-    resolution: {integrity: sha512-2hKQQDkrufMong9upKoG/kSHJhuwd+FA3iAe/qzS/BmWpbIpe7XKmq5wlz4J5CJaOPu4x+iDJbgAxZqcoQf0kg==}
-    peerDependencies:
-      '@docusaurus/core': ^2.0.0-beta || ^3.0.0-alpha
-      sass: ^1.30.0
+  typed-array-buffer@1.0.3:
+    resolution: {integrity: sha512-nAYYwfY3qnzX30IkA6AQZjVbtK6duGontcQm1WSG1MD94YLqK0515GNApXkoxKOWMusVssAHWLh9SeaoefYFGw==}
+    engines: {node: '>= 0.4'}
 
-  docusaurus-plugin-sentry@2.1.0:
-    resolution: {integrity: sha512-tBDPEF4AukkKiJx/J/Ur+CSDen1MXzqoSWCSnMFN+xyHJBUgM3ghEe5w2JjBiAcWPai3Wyt4Y8rxahhMhKEmnQ==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      '@docusaurus/core': '>=3'
-      react: '>=18'
-      react-dom: '>=18'
+  typed-array-byte-length@1.0.3:
+    resolution: {integrity: sha512-BaXgOuIxz8n8pIq3e7Atg/7s+DpiYrxn4vdot3w9KbnBhcRQq6o3xemQdIfynqSeXeDrF32x+WvfzmOjPiY9lg==}
+    engines: {node: '>= 0.4'}
 
-  docusaurus-theme-openapi-docs@5.1.0:
-    resolution: {integrity: sha512-SLHg1lodIM5AEGo0EJx4pJ+9szDDrN8Q+hNk5qqTVJ60k/zKjHAnwGCzVDT25K1CCMDPaUzuuruj43d7TRoQKw==}
-    engines: {node: '>=14'}
-    peerDependencies:
-      '@docusaurus/theme-common': ^3.10.0
-      docusaurus-plugin-openapi-docs: ^5.0.0
-      docusaurus-plugin-sass: ^0.2.3
-      react: ^16.8.4 || ^17.0.0 || ^18.0.0 || ^19.0.0
-      react-dom: ^16.8.4 || ^17.0.0 || ^18.0.0 || ^19.0.0
+  typed-array-byte-offset@1.0.5:
+    resolution: {integrity: sha512-0FHJvLPqZ7KJzp17O13jfsAjsqazgrxBu2zEK95PmUz8lv2+GjRuxUInCr2Rk9Dms3ihN21zJ929ZO43yJ95QQ==}
+    engines: {node: '>= 0.4'}
 
-  dom-converter@0.2.0:
-    resolution: {integrity: sha512-gd3ypIPfOMr9h5jIKq8E3sHOTCjeirnl0WK5ZdS1AW0Odt0b1PaWaHdJ4Qk4klv+YB9aJBS7mESXjFoDQPu6DA==}
+  typed-array-length@1.0.8:
+    resolution: {integrity: sha512-phPGCwqr2+Qo0fwniCE8e4pKnGu/yFb5nD5Y8bf0EEeiI5GklnACYA9GFy/DrAeRrKHXvHn+1SUsOWgJp6RO+g==}
+    engines: {node: '>= 0.4'}
 
-  dom-helpers@3.4.0:
-    resolution: {integrity: sha512-LnuPJ+dwqKDIyotW1VzmOZ5TONUN7CwkCR5hrgawTUbkBGYdeoNLZo6nNfGkCrjtE1nXXaj7iMMpDa8/d9WoIA==}
+  typescript@6.0.3:
+    resolution: {integrity: sha512-y2TvuxSZPDyQakkFRPZHKFm+KKVqIisdg9/CZwm9ftvKXLP8NRWj38/ODjNbr43SsoXqNuAisEf1GdCxqWcdBw==}
+    engines: {node: '>=14.17'}
+    hasBin: true
 
-  dom-helpers@5.2.1:
-    resolution: {integrity: sha512-nRCa7CK3VTrM2NmGkIy4cbK7IZlgBE/PYMn55rrXefr5xXDP0LdtfPnblFDoVdcAfslJ7or6iqAUnx0CCGIWQA==}
+  unbox-primitive@1.1.0:
+    resolution: {integrity: sha512-nWJ91DjeOkej/TA8pXQ3myruKpKEYgqvpw9lz4OPHj/NWFNluYrjbz9j01CJ8yKQd2g4jFoOkINCTW2I5LEEyw==}
+    engines: {node: '>= 0.4'}
 
-  dom-serializer@1.4.1:
-    resolution: {integrity: sha512-VHwB3KfrcOOkelEG2ZOfxqLZdfkil8PtJi4P8N2MMXucZq2yLp75ClViUlOVwyoHEDjYU433Aq+5zWP61+RGag==}
+  undici-types@8.9.0:
+    resolution: {integrity: sha512-KTDyRTYX8sWmKXAikPHHSyc63CRPETMctyjKFupcC6OBLXT3xsN0e9aF7m+mIXutFWpUXuedtowG7iLOzp0kQg==}
 
-  dom-serializer@2.0.0:
-    resolution: {integrity: sha512-wIkAryiqt/nV5EQKqQpo3SToSOV9J0DnbJqwK7Wv/Trc92zIAYZ4FlMu+JPFW1DfGFt81ZTCGgDEabffXeLyJg==}
+  unicode-trie@2.0.0:
+    resolution: {integrity: sha512-x7bc76x0bm4prf1VLg79uhAzKw8DVboClSN5VxJuQ+LKDOVEW9CdH+VY7SP+vX7xCYQqzzgQpFqz15zeLvAtZQ==}
 
-  domelementtype@2.3.0:
-    resolution: {integrity: sha512-OLETBj6w0OsagBwdXnPdN0cnMfF9opN69co+7ZrbfPGrdpPVNBUj02spi6B1N7wChLQiPn4CSH/zJvXw56gmHw==}
+  unified@11.0.5:
+    resolution: {integrity: sha512-xKvGhPWw3k84Qjh8bI3ZeJjqnyadK+GEFtazSfZv/rKeTkTjOJho6mFqh2SM96iIcZokxiOpg78GazTSg8+KHA==}
 
-  domhandler@4.3.1:
-    resolution: {integrity: sha512-GrwoxYN+uWlzO8uhUXRl0P+kHE4GtVPfYzVLcUxPL7KNdHKj66vvlhiweIHqYYXWlw+T8iLMp42Lm67ghw4WMQ==}
-    engines: {node: '>= 4'}
+  unist-builder@4.0.0:
+    resolution: {integrity: sha512-wmRFnH+BLpZnTKpc5L7O67Kac89s9HMrtELpnNaE6TAobq5DTZZs5YaTQfAZBA9bFPECx2uVAPO31c+GVug8mg==}
 
-  domhandler@5.0.3:
-    resolution: {integrity: sha512-cgwlv/1iFQiFnU96XXgROh8xTeetsnJiDsTc7TYCLFd9+/WNkIqPTxiM/8pSd8VIrhXGTf1Ny1q1hquVqDJB5w==}
-    engines: {node: '>= 4'}
+  unist-util-find-after@5.0.0:
+    resolution: {integrity: sha512-amQa0Ep2m6hE2g72AugUItjbuM8X8cGQnFoHk0pGfrFeT9GZhzN5SW8nRsiGKK7Aif4CrACPENkA6P/Lw6fHGQ==}
 
-  dompurify@3.4.8:
-    resolution: {integrity: sha512-yb1cEmaOum7wFvOCSQxyfgVlv5D47Rc30iZWoMpbDIWTnJ6grDDQyu2KFJzB2k7u0pMuJcQ1zphH//fFnw2tjQ==}
+  unist-util-is@5.2.1:
+    resolution: {integrity: sha512-u9njyyfEh43npf1M+yGKDGVPbY/JWEemg5nH05ncKPfi+kBbKBJoTdsogMu33uhytuLlv9y0O7GH7fEdwLdLQw==}
 
-  domutils@2.8.0:
-    resolution: {integrity: sha512-w96Cjofp72M5IIhpjgobBimYEfoPjx1Vx0BSX9P30WBdZW2WIKU0T1Bd0kz2eNZ9ikjKgHbEyKx8BB6H1L3h3A==}
+  unist-util-is@6.0.1:
+    resolution: {integrity: sha512-LsiILbtBETkDz8I9p1dQ0uyRUWuaQzd/cuEeS1hoRSyW5E5XGmTzlwY1OrNzzakGowI9Dr/I8HVaw4hTtnxy8g==}
 
-  domutils@3.2.2:
-    resolution: {integrity: sha512-6kZKyUajlDuqlHKVX1w7gyslj9MPIXzIFiz/rGu35uC1wMi+kMhQwGhl4lt9unC9Vb9INnY9Z3/ZA3+FhASLaw==}
+  unist-util-map@4.0.0:
+    resolution: {integrity: sha512-HJs1tpkSmRJUzj6fskQrS5oYhBYlmtcvy4SepdDEEsL04FjBrgF0Mgggvxc1/qGBGgW7hRh9+UBK1aqTEnBpIA==}
 
-  dot-case@3.0.4:
-    resolution: {integrity: sha512-Kv5nKlh6yRrdrGvxeJ2e5y2eRUpkUosIW4A2AS38zwSz27zu7ufDwQPi5Jhs3XAlGNetl3bmnGhQsMtkKJnj3w==}
+  unist-util-modify-children@4.0.0:
+    resolution: {integrity: sha512-+tdN5fGNddvsQdIzUF3Xx82CU9sMM+fA0dLgR9vOmT0oPT2jH+P1nd5lSqfCfXAw+93NhcXNY2qqvTUtE4cQkw==}
 
-  dot-prop@6.0.1:
-    resolution: {integrity: sha512-tE7ztYzXHIeyvc7N+hR3oi7FIbf/NIjVP9hmAt3yMXzrQ072/fpjGLx2GxNxGxUl5V73MEqYzioOMoVhGMJ5cA==}
-    engines: {node: '>=10'}
+  unist-util-position-from-estree@2.0.0:
+    resolution: {integrity: sha512-KaFVRjoqLyF6YXCbVLNad/eS4+OfPQQn2yOd7zF/h5T/CSL2v8NpN6a5TPvtbXthAGw5nG+PuTtq+DdIZr+cRQ==}
 
-  dunder-proto@1.0.1:
-    resolution: {integrity: sha512-KIN/nDJBQRcXw0MLVhZE9iQHmG68qAVIBg9CqmUYjmQIhgij9U5MFvrqkUL5FbtyyzZuOeOt0zdeRe4UY7ct+A==}
-    engines: {node: '>= 0.4'}
+  unist-util-position@5.0.0:
+    resolution: {integrity: sha512-fucsC7HjXvkB5R3kTCO7kUjRdrS0BJt3M/FPxmHMBOm8JQi2BsHAHFsy27E0EolP8rp0NzXsJ+jNPyDWvOJZPA==}
 
-  duplexer@0.1.2:
-    resolution: {integrity: sha512-jtD6YG370ZCIi/9GTaJKQxWTZD045+4R4hTk/x1UyoqadyJ9x9CgSi1RlVDQF8U2sxLLSnFkCaMihqljHIWgMg==}
+  unist-util-remove-position@5.0.0:
+    resolution: {integrity: sha512-Hp5Kh3wLxv0PHj9m2yZhhLt58KzPtEYKQQ4yxfYFEO7EvHwzyDYnduhHnY1mDxoqr7VUwVuHXk9RXKIiYS1N8Q==}
 
-  eastasianwidth@0.2.0:
-    resolution: {integrity: sha512-I88TYZWc9XiYHRQ4/3c5rjjfgkjhLyW2luGIheGERbNQ6OY7yTybanSpDXZa8y7VUP9YmDcYa+eyq4ca7iLqWA==}
+  unist-util-remove@4.0.0:
+    resolution: {integrity: sha512-b4gokeGId57UVRX/eVKej5gXqGlc9+trkORhFJpu9raqZkZhU0zm8Doi05+HaiBsMEIJowL+2WtQ5ItjsngPXg==}
 
-  ee-first@1.1.1:
-    resolution: {integrity: sha512-WMwm9LhRUo+WUaRN+vRuETqG89IgZphVSNkdFgeb6sS/E4OrDIN7t48CAewSHXc6C8lefD8KKfr5vY61brQlow==}
+  unist-util-stringify-position@4.0.0:
+    resolution: {integrity: sha512-0ASV06AAoKCDkS2+xw5RXJywruurpbC4JZSm7nr7MOt1ojAzvyyaO+UxZf18j8FCF6kmzCZKcAgN/yu2gm2XgQ==}
 
-  electron-to-chromium@1.5.370:
-    resolution: {integrity: sha512-D5tSHJReAb/Kf3Hu9F/GO4lJuSWzEWHwvQ/kKSUP7pimNgvxkSKj+gUQhHpKKACwrin7rS3byU7IxreF56rl5g==}
+  unist-util-visit-children@3.0.0:
+    resolution: {integrity: sha512-RgmdTfSBOg04sdPcpTSD1jzoNBjt9a80/ZCzp5cI9n1qPzLZWF9YdvWGN2zmTumP1HWhXKdUWexjy/Wy/lJ7tA==}
 
-  emoji-regex@10.6.0:
-    resolution: {integrity: sha512-toUI84YS5YmxW219erniWD0CIVOo46xGKColeNQRgOzDorgBi1v4D71/OFzgD9GO2UGKIv1C3Sp8DAn0+j5w7A==}
+  unist-util-visit-parents@5.1.3:
+    resolution: {integrity: sha512-x6+y8g7wWMyQhL1iZfhIPhDAs7Xwbn9nRosDXl7qoPTSCy0yNxnKc+hWokFifWQIDGi154rdUqKvbCa4+1kLhg==}
 
-  emoji-regex@8.0.0:
-    resolution: {integrity: sha512-MSjYzcWNOA0ewAHpz0MxpYFvwg6yjy1NG3xteoqz644VCo/RPgnr1/GGt+ic3iJTzQ8Eu3TdM14SawnVUmGE6A==}
+  unist-util-visit-parents@6.0.1:
+    resolution: {integrity: sha512-L/PqWzfTP9lzzEa6CKs0k2nARxTdZduw3zyh8d2NVBnsyvHjSX4TWse388YrrQKbvI8w20fGjGlhgT96WwKykw==}
 
-  emoji-regex@9.2.2:
-    resolution: {integrity: sha512-L18DaJsXSUk2+42pv8mLs5jJT2hqFkFE4j21wOmgbUqsZ2hL72NsUU785g9RXgo3s0ZNgVl42TiHp3ZtOv/Vyg==}
+  unist-util-visit-parents@6.0.2:
+    resolution: {integrity: sha512-goh1s1TBrqSqukSc8wrjwWhL0hiJxgA8m4kFxGlQ+8FYQ3C/m11FcTs4YYem7V664AhHVvgoQLk890Ssdsr2IQ==}
 
-  emojilib@2.4.0:
-    resolution: {integrity: sha512-5U0rVMU5Y2n2+ykNLQqMoqklN9ICBT/KsvC1Gz6vqHbz2AXXGkG+Pm5rMWk/8Vjrr/mY9985Hi8DYzn1F09Nyw==}
+  unist-util-visit@4.1.2:
+    resolution: {integrity: sha512-MSd8OUGISqHdVvfY9TPhyK2VdUrPgxkUtWSuMHF6XAAFuL4LokseigBnZtPnJMu+FbynTkFNnFlyjxpVKujMRg==}
 
-  emojis-list@3.0.0:
-    resolution: {integrity: sha512-/kyM18EfinwXZbno9FyUGeFh87KC8HRQBQGildHZbEuRyWFOmv1U10o9BBp8XVZDVNNuQKyIGIu5ZYAAXJ0V2Q==}
-    engines: {node: '>= 4'}
+  unist-util-visit@5.0.0:
+    resolution: {integrity: sha512-MR04uvD+07cwl/yhVuVWAtw+3GOR/knlL55Nd/wAdblk27GCVt3lqpTivy/tkJcZoNPzTwS1Y+KMojlLDhoTzg==}
 
-  emoticon@4.1.0:
-    resolution: {integrity: sha512-VWZfnxqwNcc51hIy/sbOdEem6D+cVtpPzEEtVAFdaas30+1dgkyaOQ4sQ6Bp0tOMqWO1v+HQfYaoodOkdhK6SQ==}
+  universalify@2.0.1:
+    resolution: {integrity: sha512-gptHNQghINnc/vTGIk0SOFGFNXw7JVrlRUtConJRlvaw6DuX0wO5Jeko9sWrMBhh+PsYAZ7oXAiOnf/UKogyiw==}
+    engines: {node: '>= 10.0.0'}
 
-  encodeurl@2.0.0:
-    resolution: {integrity: sha512-Q0n9HRi4m6JuGIV1eFlmvJB7ZEVxu93IrMyiMsGC0lrMJMWzRgx6WGquyfQgZVb31vhGgXnfmPNNXmxnOkRBrg==}
+  unpipe@1.0.0:
+    resolution: {integrity: sha512-pjy2bYhSsufwWlKwPc+l3cN7+wuJlK6uz0YdJEOlQDbl6jo/YlPi4mb8agUkVC8BF7V8NuzeyPNqRksA3hztKQ==}
     engines: {node: '>= 0.8'}
 
-  enhanced-resolve@5.23.0:
-    resolution: {integrity: sha512-yJN/BOOLxcOW2aQgeif9mSnaUB8KtvmMMp56oA1kx1CRfBKbhZm2pJ+NBY+3eOboHxix8lfjWpHE0Ei5U8RbSA==}
-    engines: {node: '>=10.13.0'}
+  uri-js@4.4.1:
+    resolution: {integrity: sha512-7rKUyy33Q1yc98pQ1DAmLtwX109F7TIfWlW1Ydo8Wl1ii1SeHieeh0HHfPeL2fMXK6z0s8ecKs9frCuLJvndBg==}
 
-  entities@2.2.0:
-    resolution: {integrity: sha512-p92if5Nz619I0w+akJrLZH0MX0Pb5DX39XOwQTtXSdQQOaYH03S1uIQp4mhOZtAXrxq4ViO67YTiLBo2638o9A==}
+  urijs@1.19.11:
+    resolution: {integrity: sha512-HXgFDgDommxn5/bIv0cnQZsPhHDA90NPHD6+c/v21U5+Sx5hoP8+dP9IZXBU1gIfvdRfhG8cel9QNPeionfcCQ==}
 
-  entities@4.5.0:
-    resolution: {integrity: sha512-V0hjH4dGPh9Ao5p0MoRY6BVqtwCjhz6vI5LT8AJ55H+4g9/4vbHx1I54fS0XuclLhDHArPQCiMjDxjaL8fPxhw==}
-    engines: {node: '>=0.12'}
+  use-sync-external-store@1.7.0:
+    resolution: {integrity: sha512-6L+EeigHMQhdaIPNIFUKwfWJSwWFQ8gJbJ2DLOs5sDIegTwR9fRxvnM3uciHKjIZhFz+KAv2emhWMRvDmMcY8A==}
+    peerDependencies:
+      react: ^16.8.0 || ^17.0.0 || ^18.0.0 || ^19.0.0
 
-  entities@6.0.1:
-    resolution: {integrity: sha512-aN97NXWF6AWBTahfVOIrB/NShkzi5H7F9r1s9mD3cDj4Ko5f2qhhVoYMibXF7GlLveb/D2ioWay8lxI97Ven3g==}
-    engines: {node: '>=0.12'}
+  util-deprecate@1.0.2:
+    resolution: {integrity: sha512-EPD5q1uXyFxJpCrLnCc1nHnq3gOa6DZBocAIiI2TaSCA7VCJ1UJDMagCzIkXNsUYfD1daK//LTEQ8xiIbrHtcw==}
 
-  error-ex@1.3.4:
-    resolution: {integrity: sha512-sqQamAnR14VgCr1A618A3sGrygcpK+HEbenA/HiEAkkUwcZIIB/tgWqHFxWgOyDh4nB4JCRimh79dR5Ywc9MDQ==}
+  utility-types@3.11.0:
+    resolution: {integrity: sha512-6Z7Ma2aVEWisaL6TvBCy7P8rm2LQoPv6dJ7ecIaIixHcwfbJ0x7mWdbcwlIM5IGQxPZSFYeqRCqlOOeKoJYMkw==}
+    engines: {node: '>= 4'}
 
-  error-stack-parser@2.1.4:
-    resolution: {integrity: sha512-Sk5V6wVazPhq5MhpO+AUxJn5x7XSXGl1R93Vn7i+zS15KDVxQijejNCrz8340/2bgLBjR9GtEG8ZVKONDjcqGQ==}
+  utils-merge@1.0.1:
+    resolution: {integrity: sha512-pMZTvIkT1d+TFGvDOqodOclx0QWkkgi6Tdoa8gC8ffGAAqz9pzPTZWAybbsHHoED/ztMtkv/VoYTYyShUn81hA==}
+    engines: {node: '>= 0.4.0'}
 
-  es-define-property@1.0.1:
-    resolution: {integrity: sha512-e3nRfgfUZ4rNGL232gUgX06QNyyez04KdjFrF+LTRoOXmrOgFKDg4BCdsjW8EnT69eqdYGmRpJwiPVYNrCaW3g==}
-    engines: {node: '>= 0.4'}
+  uuid@11.1.1:
+    resolution: {integrity: sha512-vIYxrBCC/N/K+Js3qSN88go7kIfNPssr/hHCesKCQNAjmgvYS2oqr69kIufEG+O4+PfezOH4EbIeHCfFov8ZgQ==}
+    hasBin: true
 
-  es-errors@1.3.0:
-    resolution: {integrity: sha512-Zf5H2Kxt2xjTvbJvP2ZWLEICxA6j+hAmMzIlypy4xcBg1vKVnx89Wy0GbS+kf5cwCVFFzdCFh2XSCFNULS6csw==}
-    engines: {node: '>= 0.4'}
+  valibot@1.5.0:
+    resolution: {integrity: sha512-nil6AkP2TChWL43Z5uJ6GTxX01CUA+g8LWUM+N/rB9NBbkUMaUsi9PUNzlUPgoKASgmx9f7eGOYpJ04/fSa6FQ==}
+    peerDependencies:
+      typescript: '>=5'
+    peerDependenciesMeta:
+      typescript:
+        optional: true
 
-  es-module-lexer@2.1.0:
-    resolution: {integrity: sha512-n27zTYMjYu1aj4MjCWzSP7G9r75utsaoc8m61weK+W8JMBGGQybd43GstCXZ3WNmSFtGT9wi59qQTW6mhTR5LQ==}
+  validate.io-array@1.0.6:
+    resolution: {integrity: sha512-DeOy7CnPEziggrOO5CZhVKJw6S3Yi7e9e65R1Nl/RTN1vTQKnzjfvks0/8kQ40FP/dsjRAOd4hxmJ7uLa6vxkg==}
 
-  es-object-atoms@1.1.2:
-    resolution: {integrity: sha512-HWcBoN6NileqtSydK2FqHbS/LoDd2pqrnQHLyJzBj4kOp/ky2MWMN694xOfkK8/SnUsW2DH7EfyVlydKCsm1Zw==}
-    engines: {node: '>= 0.4'}
+  validate.io-function@1.0.2:
+    resolution: {integrity: sha512-LlFybRJEriSuBnUhQyG5bwglhh50EpTL2ul23MPIuR1odjO7XaMLFV8vHGwp7AZciFxtYOeiSCT5st+XSPONiQ==}
 
-  es-toolkit@1.47.0:
-    resolution: {integrity: sha512-n1GuoD0WEQZMBk5tttoZSqwgyLx01oqa5XsBmCHwPyNe1S9jPBEmtR2pSgp2kJuWE3ciFZ6yRHmY4pM4C3OOkw==}
+  validate.io-integer-array@1.0.0:
+    resolution: {integrity: sha512-mTrMk/1ytQHtCY0oNO3dztafHYyGU88KL+jRxWuzfOmQb+4qqnWmI+gykvGp8usKZOM0H7keJHEbRaFiYA0VrA==}
 
-  es6-promise@3.3.1:
-    resolution: {integrity: sha512-SOp9Phqvqn7jtEUxPWdWfWoLmyt2VaJ6MpvP9Comy1MceMXqE6bxvaTu4iaxpYYPzhny28Lc+M87/c2cPK6lDg==}
+  validate.io-integer@1.0.5:
+    resolution: {integrity: sha512-22izsYSLojN/P6bppBqhgUDjCkr5RY2jd+N2a3DCAUey8ydvrZ/OkGvFPR7qfOpwR2LC5p4Ngzxz36g5Vgr/hQ==}
 
-  esast-util-from-estree@2.0.0:
-    resolution: {integrity: sha512-4CyanoAudUSBAn5K13H4JhsMH6L9ZP7XbLVe/dKybkxMO7eDyLsT8UHl9TRNrU2Gr9nz+FovfSIjuXWJ81uVwQ==}
+  validate.io-number@1.0.3:
+    resolution: {integrity: sha512-kRAyotcbNaSYoDnXvb4MHg/0a1egJdLwS6oJ38TJY7aw9n93Fl/3blIXdyYvPOp55CNxywooG/3BcrwNrBpcSg==}
 
-  esast-util-from-js@2.0.1:
-    resolution: {integrity: sha512-8Ja+rNJ0Lt56Pcf3TAmpBZjmx8ZcK5Ts4cAzIOjsjevg9oSXJnl6SUQ2EevU8tv3h6ZLWmoKL5H4fgWvdvfETw==}
+  vary@1.1.2:
+    resolution: {integrity: sha512-BNGbWLfd0eUPabhkXUVm0j8uuvREyTh5ovRa/dyow/BqAbZJyC+5fU+IzQOzmAKzYqYRAISoRhdQr3eIZ/PXqg==}
+    engines: {node: '>= 0.8'}
 
-  escalade@3.2.0:
-    resolution: {integrity: sha512-WUj2qlxaQtO4g6Pq5c29GTcWGDyd8itL8zTlipgECz3JesAiiOKotd8JU6otB3PACgG6xkJUyVhboMS+bje/jA==}
-    engines: {node: '>=6'}
+  vfile-location@5.0.3:
+    resolution: {integrity: sha512-5yXvWDEgqeiYiBe1lbxYF7UMAIm/IcopxMHrMQDq3nvKcjPKIhZklUKL+AE7J7uApI4kwe2snsK+eI6UTj9EHg==}
 
-  escape-goat@4.0.0:
-    resolution: {integrity: sha512-2Sd4ShcWxbx6OY1IHyla/CVNwvg7XwZVoXZHcSu9w9SReNP1EzzD5T8NWKIR38fIqEns9kDWKUQTXXAmlDrdPg==}
-    engines: {node: '>=12'}
+  vfile-matter@5.0.1:
+    resolution: {integrity: sha512-o6roP82AiX0XfkyTHyRCMXgHfltUNlXSEqCIS80f+mbAyiQBE2fxtDVMtseyytGx75sihiJFo/zR6r/4LTs2Cw==}
 
-  escape-html@1.0.3:
-    resolution: {integrity: sha512-NiSupZ4OeuGwr68lGIeym/ksIZMJodUGOSCZ/FSnTxcrekbvqrgdUxlJOMpijaKZVjAJrWrGs/6Jy8OMuyj9ow==}
+  vfile-message@4.0.3:
+    resolution: {integrity: sha512-QTHzsGd1EhbZs4AsQ20JX1rC3cOlt/IWJruk893DfLRr57lcnOeMaWG4K0JrRta4mIJZKth2Au3mM3u03/JWKw==}
 
-  escape-string-regexp@4.0.0:
-    resolution: {integrity: sha512-TtpcNJ3XAzx3Gq8sWRzJaVajRs0uVxA2YAkdb1jm2YkPz4G6egUFAyA3n5vtEIZefPk5Wa4UXbKuS5fKkJWdgA==}
-    engines: {node: '>=10'}
+  vfile@6.0.3:
+    resolution: {integrity: sha512-KzIbH/9tXat2u30jf+smMwFCsno4wHVdNmzFyL+T/L3UGqqk6JKfVqOFOZEpZSHADH1k40ab6NUIXZq422ov3Q==}
 
-  escape-string-regexp@5.0.0:
-    resolution: {integrity: sha512-/veY75JbMK4j1yjvuUxuVsiS/hr/4iHs9FTT6cgTexxdE0Ly/glccBAkloH/DofkjRbZU3bnoj38mOmhkZ0lHw==}
-    engines: {node: '>=12'}
+  web-namespaces@2.0.1:
+    resolution: {integrity: sha512-bKr1DkiNa2krS7qxNtdrtHAmzuYGFQLiQ13TsorsdT6ULTkPLKuu5+GsFpDlg6JFjUTwX2DyhMPG2be8uPrqsQ==}
+
+  webidl-conversions@3.0.1:
+    resolution: {integrity: sha512-2JAn3z8AR6rjK8Sm8orRC0h/bcl/DqL7tRPdGZ4I1CjdF+EaMLmYxBHyXuKL849eucPFhvBoxMsflfOb8kxaeQ==}
+
+  whatwg-fetch@3.6.20:
+    resolution: {integrity: sha512-EqhiFU6daOA8kpjOWTL0olhVOF3i7OrFzSYiGsEMB8GcXS+RrzauAERX65xMeNWVqxA6HXH2m69Z9LaKKdisfg==}
 
-  eslint-scope@5.1.1:
-    resolution: {integrity: sha512-2NxwbF/hZ0KpepYN0cNbo+FN6XoK7GaHlQhgx/hIZl6Va0bF45RQOOwhLIy8lQDbuCiadSLCBnH2CFYquit5bw==}
-    engines: {node: '>=8.0.0'}
+  whatwg-url@5.0.0:
+    resolution: {integrity: sha512-saE57nupxk6v3HY35+jzBwYa0rKSy0XR8JSxZPwgLr7ys0IBzhGviA1/TUGJLmSVqs8pb9AnvICXEuOHLprYTw==}
 
-  eslint-scope@9.1.2:
-    resolution: {integrity: sha512-xS90H51cKw0jltxmvmHy2Iai1LIqrfbw57b79w/J7MfvDfkIkFZ+kj6zC3BjtUwh150HsSSdxXZcsuv72miDFQ==}
-    engines: {node: ^20.19.0 || ^22.13.0 || >=24}
+  which-boxed-primitive@1.1.1:
+    resolution: {integrity: sha512-TbX3mj8n0odCBFVlY8AxkqcHASw3L60jIuF8jFP78az3C2YhmGvqbHBpAjTRH2/xqYunrJ9g1jSyjCjpoWzIAA==}
+    engines: {node: '>= 0.4'}
 
-  eslint-visitor-keys@3.4.3:
-    resolution: {integrity: sha512-wpc+LXeiyiisxPlEkUzU6svyS1frIO3Mgxj1fdy7Pm8Ygzguax2N3Fa/D/ag1WqbOprdI+uY6wMUl8/a2G+iag==}
-    engines: {node: ^12.22.0 || ^14.17.0 || >=16.0.0}
+  which-builtin-type@1.2.1:
+    resolution: {integrity: sha512-6iBczoX+kDQ7a3+YJBnh3T+KZRxM/iYNPXicqk66/Qfm1b93iu+yOImkg0zHbj5LNOcNv1TEADiZ0xa34B4q6Q==}
+    engines: {node: '>= 0.4'}
 
-  eslint-visitor-keys@4.2.1:
-    resolution: {integrity: sha512-Uhdk5sfqcee/9H/rCOJikYz67o0a2Tw2hGRPOG2Y1R2dg7brRe1uG0yaNQDHu+TO/uQPF/5eCapvYSmHUjt7JQ==}
-    engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
+  which-collection@1.0.2:
+    resolution: {integrity: sha512-K4jVyjnBdgvc86Y6BkaLZEN933SwYOuBFkdmBu9ZfkcAbdVbpITnDmjvZ/aQjRXQrv5EPkTnD1s39GiiqbngCw==}
+    engines: {node: '>= 0.4'}
 
-  eslint-visitor-keys@5.0.1:
-    resolution: {integrity: sha512-tD40eHxA35h0PEIZNeIjkHoDR4YjjJp34biM0mDvplBe//mB+IHCqHDGV7pxF+7MklTvighcCPPZC7ynWyjdTA==}
-    engines: {node: ^20.19.0 || ^22.13.0 || >=24}
+  which-typed-array@1.1.24:
+    resolution: {integrity: sha512-wk4Mf4pR5mRP7eYuuTBCIQ9d0ud2Fv2jRLQpfgnRjbOxAFHmjKFValgTpitVKzJJS8ajnYQV2Du1SZ8j6b/EUQ==}
+    engines: {node: '>= 0.4'}
 
-  eslint@10.6.0:
-    resolution: {integrity: sha512-6lVbcqSodALYo+4ELD0heG6lFiFxnLMuLkiMi2qV8LMp54N8tE8FT1GMH+ev4Ti00nFjNze2+Su6DsV5OQW3Dg==}
-    engines: {node: ^20.19.0 || ^22.13.0 || >=24}
+  which@2.0.2:
+    resolution: {integrity: sha512-BLI3Tl1TW3Pvl70l3yq3Y64i+awpwXqsGBYWkkqMtnbXgrMD+yj7rhW0kuEDxzJaYXGjEW5ogapKNMEKNMjibA==}
+    engines: {node: '>= 8'}
     hasBin: true
+
+  widest-line@5.0.0:
+    resolution: {integrity: sha512-c9bZp7b5YtRj2wOe6dlj32MK+Bx/M/d+9VB2SHM1OtsUHR0aV0tdP6DWh/iMt0kWi1t5g1Iudu6hQRNd1A4PVA==}
+    engines: {node: '>=18'}
+
+  wrap-ansi@6.2.0:
+    resolution: {integrity: sha512-r6lPcBGxZXlIcymEu7InxDMhdW0KDxpLgoFLcguasxCaJ/SOIZwINatK9KY/tf+ZrlywOKU0UDj3ATXUBfxJXA==}
+    engines: {node: '>=8'}
+
+  wrap-ansi@7.0.0:
+    resolution: {integrity: sha512-YVGIj2kamLSTxw6NsZjoBxfSwsn0ycdesmc4p+Q21c5zPuZ1pl+NfxVdxPtdHvmNVOQ6XSYG4AUtyt/Fi7D16Q==}
+    engines: {node: '>=10'}
+
+  wrap-ansi@9.0.2:
+    resolution: {integrity: sha512-42AtmgqjV+X1VpdOfyTGOYRi0/zsoLqtXQckTmqTeybT+BDIbM/Guxo7x3pE2vtpr1ok6xRqM9OpBe+Jyoqyww==}
+    engines: {node: '>=18'}
+
+  wrappy@1.0.2:
+    resolution: {integrity: sha512-l4Sp/DRseor9wL6EvV2+TuQn63dMkPjZ/sp9XkghTEbV9KlPS1xUsZ3u7/IQO4wxtcFB4bgpQPRcR3QCvezPcQ==}
+
+  ws@8.21.3:
+    resolution: {integrity: sha512-201TZ/kPWxoPr/OKWjquZR1SWKXcvxdH+e1xrx89b3YbmzLMFCLfnaG1HFIgWzJOEWZ7MvpK++odZufgYR50Rw==}
+    engines: {node: '>=10.0.0'}
     peerDependencies:
-      jiti: '*'
+      bufferutil: ^4.0.1
+      utf-8-validate: '>=5.0.2'
     peerDependenciesMeta:
-      jiti:
+      bufferutil:
+        optional: true
+      utf-8-validate:
         optional: true
 
-  espree@10.4.0:
-    resolution: {integrity: sha512-j6PAQ2uUr79PZhBjP5C5fhl8e39FmRnOjsD5lGnWrFU8i2G776tBK7+nP8KuQUTTyAZUwfQqXAgrVH5MbH9CYQ==}
-    engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
-
-  espree@11.2.0:
-    resolution: {integrity: sha512-7p3DrVEIopW1B1avAGLuCSh1jubc01H2JHc8B4qqGblmg5gI9yumBgACjWo4JlIc04ufug4xJ3SQI8HkS/Rgzw==}
-    engines: {node: ^20.19.0 || ^22.13.0 || >=24}
+  ws@8.22.0:
+    resolution: {integrity: sha512-Ydggc987+RO0AnWtZ/7Wq9FtNvcrL1b/RO0ud9mWjUPgDrsAAwQSF51sm2hm1XofbU/4jkpGEsLFsZZxU+1DOg==}
+    engines: {node: '>=10.0.0'}
+    peerDependencies:
+      bufferutil: ^4.0.1
+      utf-8-validate: '>=5.0.2'
+    peerDependenciesMeta:
+      bufferutil:
+        optional: true
+      utf-8-validate:
+        optional: true
 
-  esprima@4.0.1:
-    resolution: {integrity: sha512-eGuFFw7Upda+g4p+QHvnW0RyTX/SVeJBDM/gCtMARO0cLuT2HcEKnTPvhjV6aGeqrCB/sbNop0Kszm0jsaWU4A==}
-    engines: {node: '>=4'}
-    hasBin: true
+  xml-naming@0.3.0:
+    resolution: {integrity: sha512-ghig2TBE/H11aOVgmahA3MhimvkBr6JIYknH/Dhdk10nXwdbIqBJsbfMxpvFPG8bAw77gN29aQWvKpmVoPlvPQ==}
+    engines: {node: '>=16.0.0'}
 
-  esquery@1.7.0:
-    resolution: {integrity: sha512-Ap6G0WQwcU/LHsvLwON1fAQX9Zp0A2Y6Y/cJBl9r/JbW90Zyg4/zbG6zzKa2OTALELarYHmKu0GhpM5EO+7T0g==}
-    engines: {node: '>=0.10'}
+  xml2js@0.6.2:
+    resolution: {integrity: sha512-T4rieHaC1EXcES0Kxxj4JWgaUQHDk+qwHcYOCFHfiwKz7tOVPLq7Hjq9dM1WCMhylqMEfP7hMcOIChvotiZegA==}
+    engines: {node: '>=4.0.0'}
 
-  esrecurse@4.3.0:
-    resolution: {integrity: sha512-KmfKL3b6G+RXvP8N1vr3Tq1kL/oCFgn2NYXEtqP8/L3pKapUA4G8cFVaoF3SU323CD4XypR/ffioHmkti6/Tag==}
+  xmlbuilder@11.0.1:
+    resolution: {integrity: sha512-fDlsI/kFEx7gLvbecc0/ohLG50fugQp8ryHzMTuW9vSa1GJ0XYWKnhsUx7oie3G98+r56aTQIUB4kht42R3JvA==}
     engines: {node: '>=4.0'}
 
-  estraverse@4.3.0:
-    resolution: {integrity: sha512-39nnKffWz8xN1BU/2c79n9nB9HDzo0niYUqx6xyqUnyoAnQyyWpOTdZEeiCch8BBu515t4wp9ZmgVfVhn9EBpw==}
-    engines: {node: '>=4.0'}
+  xss@1.0.15:
+    resolution: {integrity: sha512-FVdlVVC67WOIPvfOwhoMETV72f6GbW7aOabBC3WxN/oUdoEMDyLz4OgRv5/gck2ZeNqEQu+Tb0kloovXOfpYVg==}
+    engines: {node: '>= 0.10.0'}
+    hasBin: true
 
-  estraverse@5.3.0:
-    resolution: {integrity: sha512-MMdARuVEQziNTeJD8DgMqmhwR11BRQ/cBP+pLtYdSTnf3MIO8fFeiINEbX36ZdNlfU/7A9f3gUw49B3oQsvwBA==}
-    engines: {node: '>=4.0'}
+  y18n@5.0.8:
+    resolution: {integrity: sha512-0pfFzegeDWJHJIAmTLRP2DwHjdF5s7jo9tuztdQxAhINCdvS+3nGINqPd00AphqJR/0LhANUS6/+7SCb98YOfA==}
+    engines: {node: '>=10'}
 
-  estree-util-attach-comments@3.0.0:
-    resolution: {integrity: sha512-cKUwm/HUcTDsYh/9FgnuFqpfquUbwIqwKM26BVCGDPVgvaCl/nDCCjUfiLlx6lsEZ3Z4RFxNbOQ60pkaEwFxGw==}
+  yallist@5.0.0:
+    resolution: {integrity: sha512-YgvUTfwqyc7UXVMrB+SImsVYSmTS8X/tSrtdNZMImM+n7+QTriRXyXim0mBrTXNeqzVF0KWGgHPeiyViFFrNDw==}
+    engines: {node: '>=18'}
 
-  estree-util-build-jsx@3.0.1:
-    resolution: {integrity: sha512-8U5eiL6BTrPxp/CHbs2yMgP8ftMhR5ww1eIKoWRMlqvltHF8fZn5LRDvTKuxD3DUn+shRbLGqXemcP51oFCsGQ==}
+  yaml@2.8.3:
+    resolution: {integrity: sha512-AvbaCLOO2Otw/lW5bmh9d/WEdcDFdQp2Z2ZUH3pX9U2ihyUY0nvLv7J6TrWowklRGPYbB/IuIMfYgxaCPg5Bpg==}
+    engines: {node: '>= 14.6'}
+    hasBin: true
 
-  estree-util-is-identifier-name@3.0.0:
-    resolution: {integrity: sha512-hFtqIDZTIUZ9BXLb8y4pYGyk6+wekIivNVTcmvk8NoOh+VeRn5y6cEHzbURrWbfp1fIqdVipilzj+lfaadNZmg==}
+  yargs-parser@21.1.1:
+    resolution: {integrity: sha512-tVpsJW7DdjecAiFpbIB1e3qxIQsE6NoPc5/eTdrbbIC4h0LVsWhnoa3g+m2HclBIujHzsxZ4VJVA+GUuc2/LBw==}
+    engines: {node: '>=12'}
 
-  estree-util-scope@1.0.0:
-    resolution: {integrity: sha512-2CAASclonf+JFWBNJPndcOpA8EMJwa0Q8LUFJEKqXLW6+qBvbFZuF5gItbQOs/umBUkjviCSDCbBwU2cXbmrhQ==}
+  yargs-parser@22.0.0:
+    resolution: {integrity: sha512-rwu/ClNdSMpkSrUb+d6BRsSkLUq1fmfsY6TOpYzTwvwkg1/NRG85KBy3kq++A8LKQwX6lsu+aWad+2khvuXrqw==}
+    engines: {node: ^20.19.0 || ^22.12.0 || >=23}
 
-  estree-util-to-js@2.0.0:
-    resolution: {integrity: sha512-WDF+xj5rRWmD5tj6bIqRi6CkLIXbbNQUcxQHzGysQzvHmdYG2G7p/Tf0J0gpxGgkeMZNTIjT/AoSvC9Xehcgdg==}
+  yargs@17.7.1:
+    resolution: {integrity: sha512-cwiTb08Xuv5fqF4AovYacTFNxk62th7LKJ6BL9IGUpTJrWoU7/7WdQGTP2SjKf1dUNBGzDd28p/Yfs/GI6JrLw==}
+    engines: {node: '>=12'}
 
-  estree-util-value-to-estree@3.5.0:
-    resolution: {integrity: sha512-aMV56R27Gv3QmfmF1MY12GWkGzzeAezAX+UplqHVASfjc9wNzI/X6hC0S9oxq61WT4aQesLGslWP9tKk6ghRZQ==}
+  yargs@18.0.0:
+    resolution: {integrity: sha512-4UEqdc2RYGHZc7Doyqkrqiln3p9X2DZVxaGbwhn2pi7MrRagKaOcIKe8L3OxYcbhXLgLFUS3zAYuQjKBQgmuNg==}
+    engines: {node: ^20.19.0 || ^22.12.0 || >=23}
 
-  estree-util-visit@2.0.0:
-    resolution: {integrity: sha512-m5KgiH85xAhhW8Wta0vShLcUvOsh3LLPI2YVwcbio1l7E09NTLL1EyMZFM1OyWowoH0skScNbhOPl4kcBgzTww==}
+  yoctocolors-cjs@2.1.3:
+    resolution: {integrity: sha512-U/PBtDf35ff0D8X8D0jfdzHYEPFxAI7jJlxZXwCSez5M3190m+QobIfh+sWDWSHMCWWJN2AWamkegn6vr6YBTw==}
+    engines: {node: '>=18'}
 
-  estree-walker@3.0.3:
-    resolution: {integrity: sha512-7RUKfXgSMMkzt6ZuXmqapOurLGPPfgj6l9uRZ7lRGolvk0y2yocc35LdcxKC5PQZdn2DMqioAQ2NoWcrTKmm6g==}
+  yoga-layout@3.2.1:
+    resolution: {integrity: sha512-0LPOt3AxKqMdFBZA3HBAt/t/8vIKq7VaQYbuA8WxCgung+p9TVyKRYdpvCb80HcdTN2NkbIKbhNwKUfm3tQywQ==}
 
-  esutils@2.0.3:
-    resolution: {integrity: sha512-kVscqXk4OCp68SZ0dkgEKVi6/8ij300KBWTJq32P/dYeWTSwK41WyTxalN1eRmA5Z9UU/LX9D7FWSmV9SAYx6g==}
-    engines: {node: '>=0.10.0'}
+  zod-to-json-schema@3.20.4:
+    resolution: {integrity: sha512-Un9+kInJ2Zt63n6Z7mLqBifzzPcOyX+b+Exuzf7L1+xqck9Q2EPByyTRduV3kmSPaXaRer1JCsucubpgL1fipg==}
+    peerDependencies:
+      zod: ^3.20.0
 
-  eta@2.2.0:
-    resolution: {integrity: sha512-UVQ72Rqjy/ZKQalzV5dCCJP80GrmPrMxh6NlNf+erV6ObL0ZFkhCstWRawS85z3smdr3d2wXPsZEY7rDPfGd2g==}
-    engines: {node: '>=6.0.0'}
+  zod@3.24.0:
+    resolution: {integrity: sha512-Hz+wiY8yD0VLA2k/+nsg2Abez674dDGTai33SwNvMPuf9uIrBC9eFgIMQxBBbHFxVXi8W+5nX9DcAh9YNSQm/w==}
 
-  etag@1.8.1:
-    resolution: {integrity: sha512-aIL5Fx7mawVa300al2BnEE4iNvo1qETxLrPI/o05L7z6go7fCw1J6EQmbK4FmJ2AS7kgVF/KEZWufBfdClMcPg==}
-    engines: {node: '>= 0.6'}
+  zod@4.3.6:
+    resolution: {integrity: sha512-rftlrkhHZOcjDwkGlnUtZZkvaPHCsDATp4pGpuOOMDaTdDDXF91wuVDJoWoPsKX/3YPQ5fHuF3STjcYyKr+Qhg==}
 
-  eval@0.1.8:
-    resolution: {integrity: sha512-EzV94NYKoO09GLXGjXj9JIlXijVck4ONSr5wiCWDvhsvj5jxSrzTmRU/9C1DyB6uToszLs8aifA6NQ7lEQdvFw==}
-    engines: {node: '>= 0.8'}
+  zwitch@2.0.4:
+    resolution: {integrity: sha512-bXE4cR/kVZhKZX/RjPEflHaKVhUVl85noU3v6b8apfQEc1x4A+zBxjZ4lN8LqGd6WZ3dl98pY4o717VFmoPp+A==}
 
-  eventemitter3@4.0.7:
-    resolution: {integrity: sha512-8guHBZCwKnFhYdHr2ysuRWErTwhoN2X8XELRlrRwpmfeY2jjuUN4taQMsULKUVo1K4DvZl+0pgfyoysHxvmvEw==}
+snapshots:
 
-  events@3.3.0:
-    resolution: {integrity: sha512-mQw+2fkQbALzQ7V0MY0IqdnXNOeTtP4r0lN9z7AAawCXgqea7bDii20AYrIBrFd/Hx0M2Ocz6S111CaFkUcb0Q==}
-    engines: {node: '>=0.8.x'}
+  '@alcalzone/ansi-tokenize@0.2.5':
+    dependencies:
+      ansi-styles: 6.2.3
+      is-fullwidth-code-point: 5.1.0
 
-  execa@5.1.1:
-    resolution: {integrity: sha512-8uSpZZocAZRBAPIEINJj3Lo9HyGitllczc27Eh5YYojjMFMn8yHMDMaUHE2Jqfq05D/wucwI4JGURyXt1vchyg==}
-    engines: {node: '>=10'}
+  '@alloc/quick-lru@5.3.0': {}
 
-  exenv@1.2.2:
-    resolution: {integrity: sha512-Z+ktTxTwv9ILfgKCk32OX3n/doe+OcLTRtqK9pcL+JsP3J1/VW8Uvl4ZjLlKqeW4rzK4oesDOGMEMRIZqtP4Iw==}
+  '@ark/schema@0.56.7':
+    dependencies:
+      '@ark/util': 0.56.7
 
-  express@4.22.2:
-    resolution: {integrity: sha512-IuL+Elrou2ZvCFHs18/CIzy2Nzvo25nZ1/D2eIZlz7c+QUayAcYoiM2BthCjs+EBHVpjYjcuLDAiCWgeIX3X1Q==}
-    engines: {node: '>= 0.10.0'}
+  '@ark/util@0.56.7': {}
 
-  extend-shallow@2.0.1:
-    resolution: {integrity: sha512-zCnTtlxNoAiDc3gqY2aYAWFx7XWWiasuF2K8Me5WbN8otHKTUKBwjPtNpRs/rbUZm7KxWAaNj7P1a/p52GbVug==}
-    engines: {node: '>=0.10.0'}
+  '@asyncapi/parser@3.4.0':
+    dependencies:
+      '@asyncapi/specs': 6.11.1
+      '@openapi-contrib/openapi-schema-to-json-schema': 3.2.0
+      '@stoplight/json': 3.21.0
+      '@stoplight/json-ref-readers': 1.2.2
+      '@stoplight/json-ref-resolver': 3.1.6
+      '@stoplight/spectral-core': 1.24.0
+      '@stoplight/spectral-functions': 1.11.0
+      '@stoplight/spectral-parsers': 1.0.5
+      '@stoplight/spectral-ref-resolver': 1.0.5
+      '@stoplight/types': 13.20.0
+      '@types/json-schema': 7.0.15
+      '@types/urijs': 1.19.26
+      ajv: 8.20.0
+      ajv-errors: 3.0.0(ajv@8.20.0)
+      ajv-formats: 2.1.1(ajv@8.20.0)
+      avsc: 5.7.9
+      js-yaml: 4.3.1
+      jsonpath-plus: 10.4.0
+      node-fetch: 2.6.7
+    transitivePeerDependencies:
+      - encoding
 
-  extend@3.0.2:
-    resolution: {integrity: sha512-fjquC59cD7CyW6urNXK0FBufkZcoiGG80wTuPujX590cB5Ttln20E2UB4S/WARVqhXffZl2LNgS+gQdPIIim/g==}
+  '@asyncapi/specs@6.11.1':
+    dependencies:
+      '@types/json-schema': 7.0.15
 
-  fast-deep-equal@3.1.3:
-    resolution: {integrity: sha512-f3qQ9oQy9j2AhBe/H9VC91wLmKBCCU/gDOnKNAYG5hswO7BLKj09Hc5HYNz9cGI++xlpDCIgDaitVs03ATR84Q==}
+  '@babel/code-frame@7.29.7':
+    dependencies:
+      '@babel/helper-validator-identifier': 7.29.7
+      js-tokens: 4.0.0
+      picocolors: 1.1.1
 
-  fast-glob@3.3.3:
-    resolution: {integrity: sha512-7MptL8U0cqcFdzIzwOTHoilX9x5BrNqye7Z/LuC7kCMRio1EMSyqRK3BEAUD7sXRq4iT4AzTVuZdhgQ2TCvYLg==}
-    engines: {node: '>=8.6.0'}
+  '@babel/helper-validator-identifier@7.29.7': {}
 
-  fast-json-stable-stringify@2.1.0:
-    resolution: {integrity: sha512-lhd/wF+Lk98HZoTCtlVraHtfh5XYijIjalXck7saUtuanSDyLMxnHhSXEDJqHxD7msR8D0uCmqlkwjCV8xvwHw==}
+  '@babel/runtime@8.0.7': {}
 
-  fast-levenshtein@2.0.6:
-    resolution: {integrity: sha512-DCXu6Ifhqcks7TZKY3Hxp3y6qphY5SJZmrWMDrKcERSOXWQdMhU9Ig/PYrzyw/ul9jOIyh0N4M0tbC5hodg8dw==}
+  '@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)':
+    dependencies:
+      '@babel/runtime': 8.0.7
+      '@base-ui/utils': 0.5.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)
+      '@floating-ui/react-dom': 2.1.9(react-dom@19.3.1(react@19.2.3))(react@19.2.3)
+      '@floating-ui/utils': 0.2.12
+      react: 19.2.3
+      react-dom: 19.3.1(react@19.2.3)
+      use-sync-external-store: 1.7.0(react@19.2.3)
+    optionalDependencies:
+      '@types/react': 19.3.0
 
-  fast-safe-stringify@2.1.1:
-    resolution: {integrity: sha512-W+KJc2dmILlPplD/H4K9l9LcAHAfPtP6BY84uVLXQ6Evcz9Lcg33Y2z1IVblT6xdY54PXYVHEv+0Wpq8Io6zkA==}
+  '@base-ui/utils@0.5.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)':
+    dependencies:
+      '@babel/runtime': 8.0.7
+      '@floating-ui/utils': 0.2.12
+      react: 19.2.3
+      react-dom: 19.3.1(react@19.2.3)
+      reselect: 5.3.0
+      use-sync-external-store: 1.7.0(react@19.2.3)
+    optionalDependencies:
+      '@types/react': 19.3.0
 
-  fast-shallow-equal@1.0.0:
-    resolution: {integrity: sha512-HPtaa38cPgWvaCFmRNhlc6NG7pv6NUHqjPgVAkWGoB9mQMwYB27/K0CvOM5Czy+qpT3e8XJ6Q4aPAnzpNpzNaw==}
+  '@canvas/image-data@1.1.0': {}
 
-  fast-uri@3.1.2:
-    resolution: {integrity: sha512-rVjf7ArG3LTk+FS6Yw81V1DLuZl1bRbNrev6Tmd/9RaroeeRRJhAt7jg/6YFxbvAQXUCavSoZhPPj6oOx+5KjQ==}
+  '@emnapi/runtime@1.11.3':
+    dependencies:
+      tslib: 2.8.1
+    optional: true
 
-  fast-uri@3.1.3:
-    resolution: {integrity: sha512-i70LwGWUduXqzicKXWshooq+sWL1K3WUU5rKZNG/0i3a1OSoX3HqhH5WbWwTmqWfor4urUakGPiRQcleRZTwOg==}
+  '@esbuild/aix-ppc64@0.25.12':
+    optional: true
 
-  fast-uri@3.1.5:
-    resolution: {integrity: sha512-gHwA1O9LDIcKunMKhObS/HimwtehO1nPUECKAu5TpKgaO19fcWEl4bliWe1jWxVFvIXztJjjQ4L8XQ1EU9f7Jw==}
+  '@esbuild/android-arm64@0.25.12':
+    optional: true
 
-  fastest-stable-stringify@2.0.2:
-    resolution: {integrity: sha512-bijHueCGd0LqqNK9b5oCMHc0MluJAx0cwqASgbWMvkO01lCYgIhacVRLcaDz3QnyYIRNJRDwMb41VuT6pHJ91Q==}
+  '@esbuild/android-arm@0.25.12':
+    optional: true
 
-  fastq@1.20.1:
-    resolution: {integrity: sha512-GGToxJ/w1x32s/D2EKND7kTil4n8OVk/9mycTc4VDza13lOvpUZTGX3mFSCtV9ksdGBVzvsyAVLM6mHFThxXxw==}
+  '@esbuild/android-x64@0.25.12':
+    optional: true
 
-  fault@1.0.4:
-    resolution: {integrity: sha512-CJ0HCB5tL5fYTEA7ToAq5+kTwd++Borf1/bifxd9iT70QcXr4MRrO3Llf8Ifs70q+SJcGHFtnIE/Nw6giCtECA==}
+  '@esbuild/darwin-arm64@0.25.12':
+    optional: true
 
-  fault@2.0.1:
-    resolution: {integrity: sha512-WtySTkS4OKev5JtpHXnib4Gxiurzh5NCGvWrFaZ34m6JehfTUhKZvn9njTfw48t6JumVQOmrKqpmGcdwxnhqBQ==}
+  '@esbuild/darwin-x64@0.25.12':
+    optional: true
 
-  faye-websocket@0.11.4:
-    resolution: {integrity: sha512-CzbClwlXAuiRQAlUyfqPgvPoNKTckTPGfwZV4ZdAhVcP2lh9KUxJg2b5GkE7XbjKQ3YJnQ9z6D9ntLAlB+tP8g==}
-    engines: {node: '>=0.8.0'}
+  '@esbuild/freebsd-arm64@0.25.12':
+    optional: true
 
-  fdir@6.5.0:
-    resolution: {integrity: sha512-tIbYtZbucOs0BRGqPJkshJUYdL+SDH7dVM8gjy+ERp3WAUjLEFJE+02kanyHtwjWOnwrKYBiwAmM0p4kLJAnXg==}
-    engines: {node: '>=12.0.0'}
-    peerDependencies:
-      picomatch: ^3 || ^4
-    peerDependenciesMeta:
-      picomatch:
-        optional: true
+  '@esbuild/freebsd-x64@0.25.12':
+    optional: true
 
-  feed@4.2.2:
-    resolution: {integrity: sha512-u5/sxGfiMfZNtJ3OvQpXcvotFpYkL0n9u9mM2vkui2nGo8b4wvDkJ8gAkYqbA8QpGyFCv3RK0Z+Iv+9veCS9bQ==}
-    engines: {node: '>=0.4.0'}
+  '@esbuild/linux-arm64@0.25.12':
+    optional: true
 
-  file-entry-cache@8.0.0:
-    resolution: {integrity: sha512-XXTUwCvisa5oacNGRP9SfNtYBNAMi+RPwBFmblZEF7N7swHYQS6/Zfk7SRwx4D5j3CH211YNRco1DEMNVfZCnQ==}
-    engines: {node: '>=16.0.0'}
+  '@esbuild/linux-arm@0.25.12':
+    optional: true
 
-  file-loader@6.2.0:
-    resolution: {integrity: sha512-qo3glqyTa61Ytg4u73GultjHGjdRyig3tG6lPtyX/jOEJvHif9uB0/OCI2Kif6ctF3caQTW2G5gym21oAsI4pw==}
-    engines: {node: '>= 10.13.0'}
-    peerDependencies:
-      webpack: ^4.0.0 || ^5.0.0
+  '@esbuild/linux-ia32@0.25.12':
+    optional: true
 
-  file-saver@2.0.5:
-    resolution: {integrity: sha512-P9bmyZ3h/PRG+Nzga+rbdI4OEpNDzAVyy74uVO9ATgzLK6VtAsYybF/+TOCvrc0MO793d6+42lLyZTw7/ArVzA==}
+  '@esbuild/linux-loong64@0.25.12':
+    optional: true
 
-  file-type@3.9.0:
-    resolution: {integrity: sha512-RLoqTXE8/vPmMuTI88DAzhMYC99I8BWv7zYP4A1puo5HIjEJ5EX48ighy4ZyKMG9EDXxBgW6e++cn7d1xuFghA==}
-    engines: {node: '>=0.10.0'}
+  '@esbuild/linux-mips64el@0.25.12':
+    optional: true
 
-  fill-range@7.1.1:
-    resolution: {integrity: sha512-YsGpe3WHLK8ZYi4tWDg2Jy3ebRz2rXowDxnld4bkQB00cc/1Zw9AWnC0i9ztDJitivtQvaI9KaLyKrc+hBW0yg==}
-    engines: {node: '>=8'}
+  '@esbuild/linux-ppc64@0.25.12':
+    optional: true
 
-  finalhandler@1.3.2:
-    resolution: {integrity: sha512-aA4RyPcd3badbdABGDuTXCMTtOneUCAYH/gxoYRTZlIJdF0YPWuGqiAsIrhNnnqdXGswYk6dGujem4w80UJFhg==}
-    engines: {node: '>= 0.8'}
+  '@esbuild/linux-riscv64@0.25.12':
+    optional: true
 
-  find-cache-dir@4.0.0:
-    resolution: {integrity: sha512-9ZonPT4ZAK4a+1pUPVPZJapbi7O5qbbJPdYw/NOQWZZbVLdDTYM3A4R9z/DpAM08IDaFGsvPgiGZ82WEwUDWjg==}
-    engines: {node: '>=14.16'}
+  '@esbuild/linux-s390x@0.25.12':
+    optional: true
 
-  find-up@5.0.0:
-    resolution: {integrity: sha512-78/PXT1wlLLDgTzDs7sjq9hzz0vXD+zn+7wypEe4fXQxCmdmqfGsEPQxmiCSQI3ajFV91bVSsvNtrJRiW6nGng==}
-    engines: {node: '>=10'}
+  '@esbuild/linux-x64@0.25.12':
+    optional: true
 
-  find-up@6.3.0:
-    resolution: {integrity: sha512-v2ZsoEuVHYy8ZIlYqwPe/39Cy+cFDzp4dXPaxNvkEuouymu+2Jbz0PxpKarJHYJTmv2HWT3O382qY8l4jMWthw==}
-    engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
+  '@esbuild/netbsd-arm64@0.25.12':
+    optional: true
 
-  flat-cache@4.0.1:
-    resolution: {integrity: sha512-f7ccFPK3SXFHpx15UIGyRJ/FJQctuKZ0zVuN3frBo4HnK3cay9VEW0R6yPYFHC0AgqhukPzKjq22t5DmAyqGyw==}
-    engines: {node: '>=16'}
+  '@esbuild/netbsd-x64@0.25.12':
+    optional: true
 
-  flat@5.0.2:
-    resolution: {integrity: sha512-b6suED+5/3rTpUBdG1gupIl8MPFCAMA0QXwmljLhvCUKcUvdE4gWky9zpuGCcXHOsz4J9wPGNWq6OKpmIzz3hQ==}
-    hasBin: true
+  '@esbuild/openbsd-arm64@0.25.12':
+    optional: true
 
-  flatted@3.4.2:
-    resolution: {integrity: sha512-PjDse7RzhcPkIJwy5t7KPWQSZ9cAbzQXcafsetQoD7sOJRQlGikNbx7yZp2OotDnJyrDcbyRq3Ttb18iYOqkxA==}
+  '@esbuild/openbsd-x64@0.25.12':
+    optional: true
 
-  fnv-plus@1.3.1:
-    resolution: {integrity: sha512-Gz1EvfOneuFfk4yG458dJ3TLJ7gV19q3OM/vVvvHf7eT02Hm1DleB4edsia6ahbKgAYxO9gvyQ1ioWZR+a00Yw==}
+  '@esbuild/openharmony-arm64@0.25.12':
+    optional: true
 
-  follow-redirects@1.16.0:
-    resolution: {integrity: sha512-y5rN/uOsadFT/JfYwhxRS5R7Qce+g3zG97+JrtFZlC9klX/W5hD7iiLzScI4nZqUS7DNUdhPgw4xI8W2LuXlUw==}
-    engines: {node: '>=4.0'}
-    peerDependencies:
-      debug: '*'
-    peerDependenciesMeta:
-      debug:
-        optional: true
+  '@esbuild/sunos-x64@0.25.12':
+    optional: true
 
-  foreach@2.0.6:
-    resolution: {integrity: sha512-k6GAGDyqLe9JaebCsFCoudPPWfihKu8pylYXRlqP1J7ms39iPoTtk2fviNglIeQEwdh0bQeKJ01ZPyuyQvKzwg==}
+  '@esbuild/win32-arm64@0.25.12':
+    optional: true
 
-  form-data-encoder@2.1.4:
-    resolution: {integrity: sha512-yDYSgNMraqvnxiEXO4hi88+YZxaHC6QKzb5N84iRCTDeRO7ZALpir/lVmf/uXUhnwUr2O4HU8s/n6x+yNjQkHw==}
-    engines: {node: '>= 14.17'}
+  '@esbuild/win32-ia32@0.25.12':
+    optional: true
 
-  format@0.2.2:
-    resolution: {integrity: sha512-wzsgA6WOq+09wrU1tsJ09udeR/YZRaeArL9e1wPbFg3GG2yDnC2ldKpxs4xunpFF9DgqCqOIra3bc1HWrJ37Ww==}
-    engines: {node: '>=0.4.x'}
+  '@esbuild/win32-x64@0.25.12':
+    optional: true
 
-  forwarded@0.2.0:
-    resolution: {integrity: sha512-buRG0fpBtRHSTCOASe6hD258tEubFoRLb4ZNA6NxMVHNw2gOcwHo9wyablzMzOA5z9xA9L1KNjk/Nt6MT9aYow==}
-    engines: {node: '>= 0.6'}
+  '@floating-ui/core@1.8.0':
+    dependencies:
+      '@floating-ui/utils': 0.2.12
 
-  fraction.js@5.3.4:
-    resolution: {integrity: sha512-1X1NTtiJphryn/uLQz3whtY6jK3fTqoE3ohKs0tT+Ujr1W59oopxmoEh7Lu5p6vBaPbgoM0bzveAW4Qi5RyWDQ==}
+  '@floating-ui/dom@1.8.0':
+    dependencies:
+      '@floating-ui/core': 1.8.0
+      '@floating-ui/utils': 0.2.12
 
-  fresh@0.5.2:
-    resolution: {integrity: sha512-zJ2mQYM18rEFOudeV4GShTGIQ7RbzA7ozbU9I/XBpm7kqgMywgmylMwXHxZJmkVoYkna9d2pVXVXPdYTP9ej8Q==}
-    engines: {node: '>= 0.6'}
+  '@floating-ui/react-dom@2.1.9(react-dom@19.3.1(react@19.2.3))(react@19.2.3)':
+    dependencies:
+      '@floating-ui/dom': 1.8.0
+      react: 19.2.3
+      react-dom: 19.3.1(react@19.2.3)
 
-  fs-extra@10.1.0:
-    resolution: {integrity: sha512-oRXApq54ETRj4eMiFzGnHWGy+zo5raudjuxN0b8H7s/RU2oW0Wvsx9O0ACRN/kRq9E8Vu/ReskGB5o3ji+FzHQ==}
-    engines: {node: '>=12'}
+  '@floating-ui/utils@0.2.12': {}
 
-  fs-extra@11.3.6:
-    resolution: {integrity: sha512-w8ZNZr2mKIc7qeNaQ9AVPT1+iFaI+Avd4xudVOvdDJ8VytREi1Ft5Ih7hd9jjehod8vAM5GMsfQ/TpPf4EyoEA==}
-    engines: {node: '>=14.14'}
+  '@img/sharp-darwin-arm64@0.33.5':
+    optionalDependencies:
+      '@img/sharp-libvips-darwin-arm64': 1.0.4
+    optional: true
 
-  fs.realpath@1.0.0:
-    resolution: {integrity: sha512-OO0pH2lK6a0hZnAdau5ItzHPI6pUlvI7jMVnxUQRtw4owF2wk8lOSabtGDCTP4Ggrg2MbGnWO9X8K1t4+fGMDw==}
+  '@img/sharp-darwin-x64@0.33.5':
+    optionalDependencies:
+      '@img/sharp-libvips-darwin-x64': 1.0.4
+    optional: true
 
-  fsevents@2.3.3:
-    resolution: {integrity: sha512-5xoDfX+fL7faATnagmWPpbFtwh/R77WmMMqqHGS65C3vvB0YHrgF+B1YmZ3441tMj5n63k0212XNoJwzlhffQw==}
-    engines: {node: ^8.16.0 || ^10.6.0 || >=11.0.0}
-    os: [darwin]
+  '@img/sharp-libvips-darwin-arm64@1.0.4':
+    optional: true
 
-  function-bind@1.1.2:
-    resolution: {integrity: sha512-7XHNxH7qX9xG5mIwxkhumTox/MIRNcOgDrxWsMt2pAr23WHp6MrRlN7FBSFpCpr+oVO0F744iUgR82nJMfG2SA==}
+  '@img/sharp-libvips-darwin-x64@1.0.4':
+    optional: true
 
-  gensync@1.0.0-beta.2:
-    resolution: {integrity: sha512-3hN7NaskYvMDLQY55gnW3NQ+mesEAepTqlg+VEbj7zzqEMBVNhzcGYYeqFo/TlYz6eQiFcp1HcsCZO+nGgS8zg==}
-    engines: {node: '>=6.9.0'}
+  '@img/sharp-libvips-linux-arm64@1.0.4':
+    optional: true
 
-  get-caller-file@2.0.5:
-    resolution: {integrity: sha512-DyFP3BM/3YHTQOCUL/w0OZHR0lpKeGrxotcHWcqNEdnltqFwXVfhEBQ94eIo34AfQpo0rGki4cyIiftY06h2Fg==}
-    engines: {node: 6.* || 8.* || >= 10.*}
+  '@img/sharp-libvips-linux-arm@1.0.5':
+    optional: true
 
-  get-east-asian-width@1.6.0:
-    resolution: {integrity: sha512-QRbvDIbx6YklUe6RxeTeleMR0yv3cYH6PsPZHcnVn7xv7zO1BHN8r0XETu8n6Ye3Q+ahtSarc3WgtNWmehIBfA==}
-    engines: {node: '>=18'}
-
-  get-intrinsic@1.3.0:
-    resolution: {integrity: sha512-9fSjSaos/fRIVIp+xSJlE6lfwhES7LNtKaCBIamHsjr2na1BiABJPo0mOjjz8GJDURarmCPGqaiVg5mfjb98CQ==}
-    engines: {node: '>= 0.4'}
-
-  get-own-enumerable-property-symbols@3.0.2:
-    resolution: {integrity: sha512-I0UBV/XOz1XkIJHEUDMZAbzCThU/H8DxmSfmdGcKPnVhu2VfFqr34jr9777IyaTYvxjedWhqVIilEDsCdP5G6g==}
-
-  get-proto@1.0.1:
-    resolution: {integrity: sha512-sTSfBjoXBp89JvIKIefqw7U2CCebsc74kiY6awiGogKtoSGbgjYE/G/+l9sF3MWFPNc9IcoOC4ODfKHfxFmp0g==}
-    engines: {node: '>= 0.4'}
-
-  get-stream@6.0.1:
-    resolution: {integrity: sha512-ts6Wi+2j3jQjqi70w5AlN8DFnkSwC+MqmxEzdEALB2qXZYV3X/b1CTfgPLGJNMeAWxdPfU8FO1ms3NUfaHCPYg==}
-    engines: {node: '>=10'}
-
-  github-slugger@1.5.0:
-    resolution: {integrity: sha512-wIh+gKBI9Nshz2o46B0B3f5k/W+WI9ZAv6y5Dn5WJ5SK1t0TnDimB4WE5rmTD05ZAIn8HALCZVmCsvj0w0v0lw==}
-
-  glob-parent@5.1.2:
-    resolution: {integrity: sha512-AOIgSQCepiJYwP3ARnGx+5VnTu2HBYdzbGP45eLw1vr3zB3vZLeyed1sC9hnbcOc9/SrMyM5RPQrkGz4aS9Zow==}
-    engines: {node: '>= 6'}
-
-  glob-parent@6.0.2:
-    resolution: {integrity: sha512-XxwI8EOhVQgWp6iDL+3b0r86f4d6AX6zSU55HfB4ydCEuXLXc5FcYeOu+nnGftS4TEju/11rt4KJPTMgbfmv4A==}
-    engines: {node: '>=10.13.0'}
-
-  glob-to-regex.js@1.2.0:
-    resolution: {integrity: sha512-QMwlOQKU/IzqMUOAZWubUOT8Qft+Y0KQWnX9nK3ch0CJg0tTp4TvGZsTfudYKv2NzoQSyPcnA6TYeIQ3jGichQ==}
-    engines: {node: '>=10.0'}
-    peerDependencies:
-      tslib: '2'
-
-  glob-to-regexp@0.4.1:
-    resolution: {integrity: sha512-lkX1HJXwyMcprw/5YUZc2s7DrpAiHB21/V+E1rHUrVNokkvB6bqMzT0VfV6/86ZNabt1k14YOIaT7nDvOX3Iiw==}
-
-  glob@13.0.6:
-    resolution: {integrity: sha512-Wjlyrolmm8uDpm/ogGyXZXb1Z+Ca2B8NbJwqBVg0axK9GbBeoS7yGV6vjXnYdGm6X53iehEuxxbyiKp8QmN4Vw==}
-    engines: {node: 18 || 20 || >=22}
-
-  glob@7.2.3:
-    resolution: {integrity: sha512-nFR0zLpU2YCaRxwoCJvL6UvCH2JFyFVIvwTLsIf21AuHlMskA1hhTdk+LlYJtOlYt9v6dvszD2BGRqBL+iQK9Q==}
-    deprecated: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me
-
-  global-dirs@3.0.1:
-    resolution: {integrity: sha512-NBcGGFbBA9s1VzD41QXDG+3++t9Mn5t1FpLdhESY6oKY4gYTFpX4wO3sqGUa0Srjtbfj3szX0RnemmrVRUdULA==}
-    engines: {node: '>=10'}
-
-  globals@14.0.0:
-    resolution: {integrity: sha512-oahGvuMGQlPw/ivIYBjVSrWAfWLBeku5tpPE2fOPLi+WHffIWbuh2tCjhyQhTBPMf5E9jDEH4FOmTYgYwbKwtQ==}
-    engines: {node: '>=18'}
-
-  globby@11.1.0:
-    resolution: {integrity: sha512-jhIXaOzy1sb8IyocaruWSn1TjmnBVs8Ayhcy83rmxNJ8q2uWKCAj3CnJY+KpGSXCueAPc0i05kVvVKtP1t9S3g==}
-    engines: {node: '>=10'}
-
-  globby@13.2.2:
-    resolution: {integrity: sha512-Y1zNGV+pzQdh7H39l9zgB4PJqjRNqydvdYCDG4HFXM4XuvSaQQlEc91IU1yALL8gUTDomgBAfz3XJdmUS+oo0w==}
-    engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
-
-  gopd@1.2.0:
-    resolution: {integrity: sha512-ZUKRh6/kUFoAiTAtTYPZJ3hw9wNxx+BIBOijnlG9PnrJsCcSjs1wyyD6vJpaYtgnzDrKYRSqf3OO6Rfa93xsRg==}
-    engines: {node: '>= 0.4'}
-
-  got@12.6.1:
-    resolution: {integrity: sha512-mThBblvlAF1d4O5oqyvN+ZxLAYwIJK7bpMxgYqPD9okW0C3qm5FFn7k811QrcuEBwaogR3ngOFoCfs6mRv7teQ==}
-    engines: {node: '>=14.16'}
-
-  graceful-fs@4.2.10:
-    resolution: {integrity: sha512-9ByhssR2fPVsNZj478qUUbKfmL0+t5BDVyjShtyZZLiK7ZDAArFFfopyOTj0M05wE2tJPisA4iTnnXl2YoPvOA==}
-
-  graceful-fs@4.2.11:
-    resolution: {integrity: sha512-RbJ5/jmFcNNCcDV5o9eTnBLJ/HszWV0P73bc+Ff4nS/rJj+YaS6IGyiOL0VoBYX+l1Wrl3k63h/KrH+nhJ0XvQ==}
-
-  graphemer@1.4.0:
-    resolution: {integrity: sha512-EtKwoO6kxCL9WO5xipiHTZlSzBm7WLT627TqC/uVRd0HKmq8NXyebnNYxDoBi7wt8eTWrUrKXCOVaFq9x1kgag==}
-
-  graphlib@2.1.8:
-    resolution: {integrity: sha512-jcLLfkpoVGmH7/InMC/1hIvOPSUh38oJtGhvrOFGzioE1DZ+0YW16RgmOJhHiuWTvGiJQ9Z1Ik43JvkRPRvE+A==}
-
-  gray-matter@4.0.3:
-    resolution: {integrity: sha512-5v6yZd4JK3eMI3FqqCouswVqwugaA9r4dNZB1wwcmrD02QkV5H0y7XBQW8QwQqEaZY1pM9aqORSORhJRdNK44Q==}
-    engines: {node: '>=6.0'}
-
-  gzip-size@6.0.0:
-    resolution: {integrity: sha512-ax7ZYomf6jqPTQ4+XCpUGyXKHk5WweS+e05MBO4/y3WJ5RkmPXNKvX+bx1behVILVwr6JSQvZAku021CHPXG3Q==}
-    engines: {node: '>=10'}
-
-  hachure-fill@0.5.2:
-    resolution: {integrity: sha512-3GKBOn+m2LX9iq+JC1064cSFprJY4jL1jCXTcpnfER5HYE2l/4EfWSGzkPa/ZDBmYI0ZOEj5VHV/eKnPGkHuOg==}
-
-  handle-thing@2.0.1:
-    resolution: {integrity: sha512-9Qn4yBxelxoh2Ow62nP+Ka/kMnOXRi8BXnRaUwezLNhqelnN49xKz4F/dPP8OYLxLxq6JDtZb2i9XznUQbNPTg==}
-
-  has-flag@4.0.0:
-    resolution: {integrity: sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==}
-    engines: {node: '>=8'}
-
-  has-property-descriptors@1.0.2:
-    resolution: {integrity: sha512-55JNKuIW+vq4Ke1BjOTjM2YctQIvCT7GFzHwmfZPGo5wnrgkid0YQtnAleFSqumZm4az3n2BS+erby5ipJdgrg==}
-
-  has-symbols@1.1.0:
-    resolution: {integrity: sha512-1cDNdwJ2Jaohmb3sg4OmKaMBwuC48sYni5HUw2DvsC8LjGTLK9h+eb1X6RyuOHe4hT0ULCW68iomhjUoKUqlPQ==}
-    engines: {node: '>= 0.4'}
-
-  has-yarn@3.0.0:
-    resolution: {integrity: sha512-IrsVwUHhEULx3R8f/aA8AHuEzAorplsab/v8HBzEiIukwq5i/EC+xmOW+HfP1OaDP+2JkgT1yILHN2O3UFIbcA==}
-    engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
-
-  hash-color-material@1.1.3:
-    resolution: {integrity: sha512-SkyBUHHWqaLI5+wUWvEcvy0i4bvf/lrr7xauh6LB7Z/gkD8dYoQpemNA42Zy3KZ970GuuUYL+txRn1B+Xgaf0g==}
-
-  hasown@2.0.4:
-    resolution: {integrity: sha512-T2UbfbBEF32wiepXIsMlTW9+dDYC6wMh/t/vYA4tuOMKqWz/n3vr1NFSxQiyP+zk2mXsoMA/i/7qV6LKut1t1A==}
-    engines: {node: '>= 0.4'}
-
-  hast-to-hyperscript@10.0.3:
-    resolution: {integrity: sha512-NuBoUStp4fRwmvlfbidlEiRSTk0gSHm+97q4Xn9CJ10HO+Py7nlTuDi6RhM1qLOureukGrCXLG7AAxaGqqyslQ==}
-
-  hast-util-from-dom@5.0.1:
-    resolution: {integrity: sha512-N+LqofjR2zuzTjCPzyDUdSshy4Ma6li7p/c3pA78uTwzFgENbgbUrm2ugwsOdcjI1muO+o6Dgzp9p8WHtn/39Q==}
-
-  hast-util-from-html-isomorphic@2.0.0:
-    resolution: {integrity: sha512-zJfpXq44yff2hmE0XmwEOzdWin5xwH+QIhMLOScpX91e/NSGPsAzNCvLQDIEPyO2TXi+lBmU6hjLIhV8MwP2kw==}
-
-  hast-util-from-html@2.0.3:
-    resolution: {integrity: sha512-CUSRHXyKjzHov8yKsQjGOElXy/3EKpyX56ELnkHH34vDVw1N1XSQ1ZcAvTyAPtGqLTuKP/uxM+aLkSPqF/EtMw==}
-
-  hast-util-from-parse5@7.1.2:
-    resolution: {integrity: sha512-Nz7FfPBuljzsN3tCQ4kCBKqdNhQE2l0Tn+X1ubgKBPRoiDIu1mL08Cfw4k7q71+Duyaw7DXDN+VTAp4Vh3oCOw==}
-
-  hast-util-from-parse5@8.0.3:
-    resolution: {integrity: sha512-3kxEVkEKt0zvcZ3hCRYI8rqrgwtlIOFMWkbclACvjlDw8Li9S2hk/d51OI0nr/gIpdMHNepwgOKqZ/sy0Clpyg==}
-
-  hast-util-is-element@3.0.0:
-    resolution: {integrity: sha512-Val9mnv2IWpLbNPqc/pUem+a7Ipj2aHacCwgNfTiK0vJKl0LF+4Ba4+v1oPHFpf3bLYmreq0/l3Gud9S5OH42g==}
-
-  hast-util-parse-selector@2.2.5:
-    resolution: {integrity: sha512-7j6mrk/qqkSehsM92wQjdIgWM2/BW61u/53G6xmC8i1OmEdKLHbk419QKQUjz6LglWsfqoiHmyMRkP1BGjecNQ==}
-
-  hast-util-parse-selector@3.1.1:
-    resolution: {integrity: sha512-jdlwBjEexy1oGz0aJ2f4GKMaVKkA9jwjr4MjAAI22E5fM/TXVZHuS5OpONtdeIkRKqAaryQ2E9xNQxijoThSZA==}
-
-  hast-util-parse-selector@4.0.0:
-    resolution: {integrity: sha512-wkQCkSYoOGCRKERFWcxMVMOcYE2K1AaNLU8DXS9arxnLOUEWbOXKXiJUNzEpqZ3JOKpnha3jkFrumEjVliDe7A==}
-
-  hast-util-raw@7.0.0:
-    resolution: {integrity: sha512-3UKuYgaqakZrY916JfQzqSk8xZGyxpj9zwfPB3MctXLDorPdyqk1QZGZoCEqU2LMIEzVXBZukAQs7aAH9TJPIw==}
-
-  hast-util-raw@9.1.0:
-    resolution: {integrity: sha512-Y8/SBAHkZGoNkpzqqfCldijcuUKh7/su31kEBp67cFY09Wy0mTRgtsLYsiIxMJxlu0f6AA5SUTbDR8K0rxnbUw==}
-
-  hast-util-sanitize@4.1.0:
-    resolution: {integrity: sha512-Hd9tU0ltknMGRDv+d6Ro/4XKzBqQnP/EZrpiTbpFYfXv/uOhWeKc+2uajcbEvAEH98VZd7eII2PiXm13RihnLw==}
-
-  hast-util-to-estree@3.1.3:
-    resolution: {integrity: sha512-48+B/rJWAp0jamNbAAf9M7Uf//UVqAoMmgXhBdxTDJLGKY+LRnZ99qcG+Qjl5HfMpYNzS5v4EAwVEF34LeAj7w==}
-
-  hast-util-to-jsx-runtime@2.3.6:
-    resolution: {integrity: sha512-zl6s8LwNyo1P9uw+XJGvZtdFF1GdAkOg8ujOw+4Pyb76874fLps4ueHXDhXWdk6YHQ6OgUtinliG7RsYvCbbBg==}
-
-  hast-util-to-parse5@7.1.0:
-    resolution: {integrity: sha512-YNRgAJkH2Jky5ySkIqFXTQiaqcAtJyVE+D5lkN6CdtOqrnkLfGYYrEcKuHOJZlp+MwjSwuD3fZuawI+sic/RBw==}
-
-  hast-util-to-parse5@8.0.1:
-    resolution: {integrity: sha512-MlWT6Pjt4CG9lFCjiz4BH7l9wmrMkfkJYCxFwKQic8+RTZgWPuWxwAfjJElsXkex7DJjfSJsQIt931ilUgmwdA==}
-
-  hast-util-to-text@4.0.2:
-    resolution: {integrity: sha512-KK6y/BN8lbaq654j7JgBydev7wuNMcID54lkRav1P0CaE1e47P72AWWPiGKXTJU271ooYzcvTAn/Zt0REnvc7A==}
-
-  hast-util-whitespace@2.0.1:
-    resolution: {integrity: sha512-nAxA0v8+vXSBDt3AnRUNjyRIQ0rD+ntpbAp4LnPkumc5M9yUbSMa4XDU9Q6etY4f1Wp4bNgvc1yjiZtsTTrSng==}
-
-  hast-util-whitespace@3.0.0:
-    resolution: {integrity: sha512-88JUN06ipLwsnv+dVn+OIYOvAuvBMy/Qoi6O7mQHxdPXpjy+Cd6xRkWwux7DKO+4sYILtLBRIKgsdpS2gQc7qw==}
-
-  hastscript@6.0.0:
-    resolution: {integrity: sha512-nDM6bvd7lIqDUiYEiu5Sl/+6ReP0BMk/2f4U/Rooccxkj0P5nm+acM5PrGJ/t5I8qPGiqZSE6hVAwZEdZIvP4w==}
-
-  hastscript@7.2.0:
-    resolution: {integrity: sha512-TtYPq24IldU8iKoJQqvZOuhi5CyCQRAbvDOX0x1eW6rsHSxa/1i2CCiptNTotGHJ3VoHRGmqiv6/D3q113ikkw==}
-
-  hastscript@9.0.1:
-    resolution: {integrity: sha512-g7df9rMFX/SPi34tyGCyUBREQoKkapwdY/T04Qn9TDWfHhAYt4/I0gMVirzK5wEzeUqIjEB+LXC/ypb7Aqno5w==}
-
-  he@1.2.0:
-    resolution: {integrity: sha512-F/1DnUGPopORZi0ni+CvrCgHQ5FyEAHRLSApuYWMmrbSwoN2Mn/7k+Gl38gJnR7yyDZk6WLXwiGod1JOWNDKGw==}
-    hasBin: true
-
-  highlight.js@10.7.3:
-    resolution: {integrity: sha512-tzcUFauisWKNHaRkN4Wjl/ZA07gENAjFl3J/c480dprkGTg5EQstgaNFqBfUqCq54kZRIEcreTsAgF/m2quD7A==}
-
-  highlightjs-vue@1.0.0:
-    resolution: {integrity: sha512-PDEfEF102G23vHmPhLyPboFCD+BkMGu+GuJe2d9/eH4FsCwvgBpnc9n0pGE+ffKdph38s6foEZiEjdgHdzp+IA==}
-
-  history@4.10.1:
-    resolution: {integrity: sha512-36nwAD620w12kuzPAsyINPWJqlNbij+hpK1k9XRloDtym8mxzGYl2c17LnV6IAGB2Dmg4tEa7G7DlawS0+qjew==}
-
-  hoist-non-react-statics@3.3.2:
-    resolution: {integrity: sha512-/gGivxi8JPKWNm/W0jSmzcMPpfpPLc3dY/6GxhX2hQ9iGj3aDfklV4ET7NjKpSinLpJ5vafa9iiGIEZg10SfBw==}
-
-  hpack.js@2.1.6:
-    resolution: {integrity: sha512-zJxVehUdMGIKsRaNt7apO2Gqp0BdqW5yaiGHXXmbpvxgBYVZnAql+BJb4RO5ad2MgpbZKn5G6nMnegrH1FcNYQ==}
-
-  html-escaper@2.0.2:
-    resolution: {integrity: sha512-H2iMtd0I4Mt5eYiapRdIDjp+XzelXQ0tFE4JS7YFwFevXXMmOp9myNrUvCg0D6ws8iqkRPBfKHgbwig1SmlLfg==}
-
-  html-minifier-terser@6.1.0:
-    resolution: {integrity: sha512-YXxSlJBZTP7RS3tWnQw74ooKa6L9b9i9QYXY21eUEvhZ3u9XLfv6OnFsQq6RxkhHygsaUMvYsZRV5rU/OVNZxw==}
-    engines: {node: '>=12'}
-    hasBin: true
-
-  html-minifier-terser@7.2.0:
-    resolution: {integrity: sha512-tXgn3QfqPIpGl9o+K5tpcj3/MN4SfLtsx2GWwBC3SSd0tXQGyF3gsSqad8loJgKZGM3ZxbYDd5yhiBIdWpmvLA==}
-    engines: {node: ^14.13.1 || >=16.0.0}
-    hasBin: true
-
-  html-tags@3.3.1:
-    resolution: {integrity: sha512-ztqyC3kLto0e9WbNp0aeP+M3kTt+nbaIveGmUxAtZa+8iFgKLUOD4YKM5j+f3QD89bra7UeumolZHKuOXnTmeQ==}
-    engines: {node: '>=8'}
-
-  html-url-attributes@3.0.1:
-    resolution: {integrity: sha512-ol6UPyBWqsrO6EJySPz2O7ZSr856WDrEzM5zMqp+FJJLGMW35cLYmmZnl0vztAZxRUoNZJFTCohfjuIJ8I4QBQ==}
-
-  html-void-elements@2.0.1:
-    resolution: {integrity: sha512-0quDb7s97CfemeJAnW9wC0hw78MtW7NU3hqtCD75g2vFlDLt36llsYD7uB7SUzojLMP24N5IatXf7ylGXiGG9A==}
-
-  html-void-elements@3.0.0:
-    resolution: {integrity: sha512-bEqo66MRXsUGxWHV5IP0PUiAWwoEjba4VCzg0LjFJBpchPaTfyfCKTG6bc5F8ucKec3q5y6qOdGyYTSBEvhCrg==}
-
-  html-webpack-plugin@5.6.7:
-    resolution: {integrity: sha512-md+vXtdCAe60s1k6AU3dUyMJnDxUyQAwfwPKoLisvgUF1IXjtlLsk2se54+qfL9Mdm26bbwvjJybpNx48NKRLw==}
-    engines: {node: '>=10.13.0'}
-    peerDependencies:
-      '@rspack/core': 0.x || 1.x
-      webpack: ^5.20.0
-    peerDependenciesMeta:
-      '@rspack/core':
-        optional: true
-      webpack:
-        optional: true
-
-  htmlparser2@6.1.0:
-    resolution: {integrity: sha512-gyyPk6rgonLFEDGoeRgQNaEUvdJ4ktTmmUh/h2t7s+M8oPpIPxgNACWa+6ESR57kXstwqPiCut0V8NRpcwgU7A==}
-
-  htmlparser2@8.0.2:
-    resolution: {integrity: sha512-GYdjWKDkbRLkZ5geuHs5NY1puJ+PXwP7+fHPRz06Eirsb9ugf6d8kkXav6ADhcODhFFPMIXyxkxSuMf3D6NCFA==}
-
-  http-cache-semantics@4.2.0:
-    resolution: {integrity: sha512-dTxcvPXqPvXBQpq5dUr6mEMJX4oIEFv6bwom3FDwKRDsuIjjJGANqhBuoAn9c1RQJIdAKav33ED65E2ys+87QQ==}
-
-  http-deceiver@1.2.7:
-    resolution: {integrity: sha512-LmpOGxTfbpgtGVxJrj5k7asXHCgNZp5nLfp+hWc8QQRqtb7fUy6kRY3BO1h9ddF6yIPYUARgxGOwB42DnxIaNw==}
-
-  http-errors@1.8.1:
-    resolution: {integrity: sha512-Kpk9Sm7NmI+RHhnj6OIWDI1d6fIoFAtFt9RLaTMRlg/8w49juAStsrBgp0Dp4OdxdVbRIeKhtCUvoi/RuAhO4g==}
-    engines: {node: '>= 0.6'}
-
-  http-errors@2.0.1:
-    resolution: {integrity: sha512-4FbRdAX+bSdmo4AUFuS0WNiPz8NgFt+r8ThgNWmlrjQjt1Q7ZR9+zTlce2859x4KSXrwIsaeTqDoKQmtP8pLmQ==}
-    engines: {node: '>= 0.8'}
-
-  http-parser-js@0.5.10:
-    resolution: {integrity: sha512-Pysuw9XpUq5dVc/2SMHpuTY01RFl8fttgcyunjL7eEMhGM3cI4eOmiCycJDVCo/7O7ClfQD3SaI6ftDzqOXYMA==}
-
-  http-proxy-middleware@2.0.9:
-    resolution: {integrity: sha512-c1IyJYLYppU574+YI7R4QyX2ystMtVXZwIdzazUIPIJsHuWNd+mho2j+bKoHftndicGj9yh+xjd+l0yj7VeT1Q==}
-    engines: {node: '>=12.0.0'}
-    peerDependencies:
-      '@types/express': ^4.17.13
-    peerDependenciesMeta:
-      '@types/express':
-        optional: true
-
-  http-proxy@1.18.1:
-    resolution: {integrity: sha512-7mz/721AbnJwIVbnaSv1Cz3Am0ZLT/UBwkC92VlxhXv/k/BBQfM2fXElQNC27BVGr0uwUpplYPQM9LnaBMR5NQ==}
-    engines: {node: '>=8.0.0'}
-
-  http-reasons@0.1.0:
-    resolution: {integrity: sha512-P6kYh0lKZ+y29T2Gqz+RlC9WBLhKe8kDmcJ+A+611jFfxdPsbMRQ5aNmFRM3lENqFkK+HTTL+tlQviAiv0AbLQ==}
-
-  http2-client@1.3.5:
-    resolution: {integrity: sha512-EC2utToWl4RKfs5zd36Mxq7nzHHBuomZboI0yYL6Y0RmBgT7Sgkq4rQ0ezFTYoIsSs7Tm9SJe+o2FcAg6GBhGA==}
-
-  http2-wrapper@2.2.1:
-    resolution: {integrity: sha512-V5nVw1PAOgfI3Lmeaj2Exmeg7fenjhRUgz1lPSezy1CuhPYbgQtbQj4jZfEAEMlaL+vupsvhjqCyjzob0yxsmQ==}
-    engines: {node: '>=10.19.0'}
-
-  human-signals@2.1.0:
-    resolution: {integrity: sha512-B4FFZ6q/T2jhhksgkbEW3HBvWIfDW85snkQgawt07S7J5QXTk6BkNV+0yAeZrM5QpMAdYlocGoljn0sJ/WQkFw==}
-    engines: {node: '>=10.17.0'}
-
-  husky@9.1.7:
-    resolution: {integrity: sha512-5gs5ytaNjBrh5Ow3zrvdUUY+0VxIuWVL4i9irt6friV+BqdCfmV11CQTWMiBYWHbXhco+J1kHfTOUkePhCDvMA==}
-    engines: {node: '>=18'}
-    hasBin: true
-
-  hyperdyperid@1.2.0:
-    resolution: {integrity: sha512-Y93lCzHYgGWdrJ66yIktxiaGULYc6oGiABxhcO5AufBeOyoIdZF7bIfLaOrbM0iGIOXQQgxxRrFEnb+Y6w1n4A==}
-    engines: {node: '>=10.18'}
-
-  hyphenate-style-name@1.1.0:
-    resolution: {integrity: sha512-WDC/ui2VVRrz3jOVi+XtjqkDjiVjTtFaAGiW37k6b+ohyQ5wYDOGkvCZa8+H0nx3gyvv0+BST9xuOgIyGQ00gw==}
-
-  iconv-lite@0.4.24:
-    resolution: {integrity: sha512-v3MXnZAcvnywkTUEZomIActle7RXXeedOR31wwl7VlyoXO4Qi9arvSenNQWne1TcRwhCL1HwLI21bEqdpj8/rA==}
-    engines: {node: '>=0.10.0'}
-
-  iconv-lite@0.6.3:
-    resolution: {integrity: sha512-4fCk79wshMdzMp2rH06qWrJE4iolqLhCUH+OiuIgU++RB0+94NlDL81atO7GX55uUKueo0txHNtvEyI6D7WdMw==}
-    engines: {node: '>=0.10.0'}
-
-  icss-utils@5.1.0:
-    resolution: {integrity: sha512-soFhflCVWLfRNOPU3iv5Z9VUdT44xFRbzjLsEzSr5AQmgqPMTHdU3PMT1Cf1ssx8fLNJDA1juftYl+PUcv3MqA==}
-    engines: {node: ^10 || ^12 || >= 14}
-    peerDependencies:
-      postcss: ^8.1.0
-
-  ieee754@1.2.1:
-    resolution: {integrity: sha512-dcyqhDvX1C46lXZcVqCpK+FtMRQVdIMN6/Df5js2zouUsqG7I6sFxitIC+7KYK29KdXOLHdu9zL4sFnoVQnqaA==}
-
-  ignore@5.3.2:
-    resolution: {integrity: sha512-hsBTNUqQTDwkWtcdYI2i06Y/nUBEsNEDJKjWdigLvegy8kDuJAS8uRlpkkcQpyEXL0Z/pjDy5HBmMjRCJ2gq+g==}
-    engines: {node: '>= 4'}
-
-  image-size@2.0.2:
-    resolution: {integrity: sha512-IRqXKlaXwgSMAMtpNzZa1ZAe8m+Sa1770Dhk8VkSsP9LS+iHD62Zd8FQKs8fbPiagBE7BzoFX23cxFnwshpV6w==}
-    engines: {node: '>=16.x'}
-    hasBin: true
-
-  immer@11.1.9:
-    resolution: {integrity: sha512-sc/z0Cyti70bZa0ZU4sWfAElfovFb9Ni8tArJZLuklYWxegPiK3pDOql1Rq5H0FIRAW9LSQRG6OX4KqBldbhBA==}
-
-  immutable@5.1.6:
-    resolution: {integrity: sha512-q1swsS8K7L8usSHuOqF2TAoCCkonYz0SG38wLAggaa4Wml70zixIvt2ql4coQ2C2B3hTjltJry4r6bULwgAXLQ==}
-
-  import-fresh@3.3.1:
-    resolution: {integrity: sha512-TR3KfrTZTYLPB6jUjfx6MF9WcWrHL9su5TObK4ZkYgBdWKPOFoSoQIdEuTuR82pmtxH2spWG9h6etwfr1pLBqQ==}
-    engines: {node: '>=6'}
-
-  import-lazy@4.0.0:
-    resolution: {integrity: sha512-rKtvo6a868b5Hu3heneU+L4yEQ4jYKLtjpnPeUdK7h0yzXGmyBTypknlkCvHFBqfX9YlorEiMM6Dnq/5atfHkw==}
-    engines: {node: '>=8'}
-
-  import-meta-resolve@4.2.0:
-    resolution: {integrity: sha512-Iqv2fzaTQN28s/FwZAoFq0ZSs/7hMAHJVX+w8PZl3cY19Pxk6jFFalxQoIfW2826i/fDLXv8IiEZRIT0lDuWcg==}
-
-  imurmurhash@0.1.4:
-    resolution: {integrity: sha512-JmXMZ6wuvDmLiHEml9ykzqO6lwFbof0GG4IkcGaENdCRDDmMVnny7s5HsIgHCbaq0w2MyPhDqkhTUgS2LU2PHA==}
-    engines: {node: '>=0.8.19'}
-
-  indent-string@4.0.0:
-    resolution: {integrity: sha512-EdDDZu4A2OyIK7Lr/2zG+w5jmbuk1DVBnEwREQvBzspBJkCEbRa8GxU1lghYcaGJCnRWibjDXlq779X1/y5xwg==}
-    engines: {node: '>=8'}
-
-  infima@0.2.0-alpha.45:
-    resolution: {integrity: sha512-uyH0zfr1erU1OohLk0fT4Rrb94AOhguWNOcD9uGrSpRvNB+6gZXUoJX5J0NtvzBO10YZ9PgvA4NFgt+fYg8ojw==}
-    engines: {node: '>=12'}
-
-  inflight@1.0.6:
-    resolution: {integrity: sha512-k92I/b08q4wvFscXCLvqfsHCrjrF7yiXsQuIVvVE7N82W3+aqpzuUdBbfhWcy/FZR3/4IgflMgKLOsvPDrGCJA==}
-    deprecated: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
-
-  inherits@2.0.4:
-    resolution: {integrity: sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ==}
-
-  ini@1.3.8:
-    resolution: {integrity: sha512-JV/yugV2uzW5iMRSiZAyDtQd+nxtUnjeLt0acNdw98kKLrvuRVyB80tsREOE7yvGVgalhZ6RNXCmEHkUKBKxew==}
-
-  ini@2.0.0:
-    resolution: {integrity: sha512-7PnF4oN3CvZF23ADhA5wRaYEQpJ8qygSkbtTXWBeXWXmEVRXK+1ITciHWwHhsjv1TmW0MgacIv6hEi5pX5NQdA==}
-    engines: {node: '>=10'}
-
-  inline-style-parser@0.1.1:
-    resolution: {integrity: sha512-7NXolsK4CAS5+xvdj5OMMbI962hU/wvwoxk+LWR9Ek9bVtyuuYScDN6eS0rUm6TxApFpw7CX1o4uJzcd4AyD3Q==}
-
-  inline-style-parser@0.2.7:
-    resolution: {integrity: sha512-Nb2ctOyNR8DqQoR0OwRG95uNWIC0C1lCgf5Naz5H6Ji72KZ8OcFZLz2P5sNgwlyoJ8Yif11oMuYs5pBQa86csA==}
-
-  inline-style-prefixer@7.0.1:
-    resolution: {integrity: sha512-lhYo5qNTQp3EvSSp3sRvXMbVQTLrvGV6DycRMJ5dm2BLMiJ30wpXKdDdgX+GmJZ5uQMucwRKHamXSst3Sj/Giw==}
-
-  internmap@1.0.1:
-    resolution: {integrity: sha512-lDB5YccMydFBtasVtxnZ3MRBHuaoE8GKsppq+EchKL2U4nK/DmEpPHNH8MZe5HkMtpSiTSOZwfN0tzYjO/lJEw==}
-
-  internmap@2.0.3:
-    resolution: {integrity: sha512-5Hh7Y1wQbvY5ooGgPbDaL5iYLAPzMTUrjMulskHLH6wnv/A+1q5rgEaiuqEjB+oxGXIVZs1FF+R/KPN3ZSQYYg==}
-    engines: {node: '>=12'}
-
-  interpret@1.4.0:
-    resolution: {integrity: sha512-agE4QfB2Lkp9uICn7BAqoscw4SZP9kTE2hxiFI3jBPmXJfdqiahTbUuKGsMoN2GtqL9AxhYioAcVvgsb1HvRbA==}
-    engines: {node: '>= 0.10'}
-
-  invariant@2.2.4:
-    resolution: {integrity: sha512-phJfQVBuaJM5raOpJjSfkiD6BpbCE4Ns//LaXl6wGYtUBY83nWS6Rf9tXm2e8VaK60JEjYldbPif/A2B1C2gNA==}
-
-  ipaddr.js@1.9.1:
-    resolution: {integrity: sha512-0KI/607xoxSToH7GjN1FfSbLoU0+btTicjsQSWQlh/hZykN8KpmMf7uYwPW3R+akZ6R/w18ZlXSHBYXiYUPO3g==}
-    engines: {node: '>= 0.10'}
-
-  ipaddr.js@2.4.0:
-    resolution: {integrity: sha512-9VGk3HGanVE6JoZXHiCpnGy5X0jYDnN4EA4lntFPj+1vIWlFhIylq2CrrCOJH9EAhc5CYhq18F2Av2tgoAPsYQ==}
-    engines: {node: '>= 10'}
-
-  is-alphabetical@1.0.4:
-    resolution: {integrity: sha512-DwzsA04LQ10FHTZuL0/grVDk4rFoVH1pjAToYwBrHSxcrBIGQuXrQMtD5U1b0U2XVgKZCTLLP8u2Qxqhy3l2Vg==}
-
-  is-alphabetical@2.0.1:
-    resolution: {integrity: sha512-FWyyY60MeTNyeSRpkM2Iry0G9hpr7/9kD40mD/cGQEuilcZYS4okz8SN2Q6rLCJ8gbCt6fN+rC+6tMGS99LaxQ==}
-
-  is-alphanumerical@1.0.4:
-    resolution: {integrity: sha512-UzoZUr+XfVz3t3v4KyGEniVL9BDRoQtY7tOyrRybkVNjDFWyo1yhXNGrrBTQxp3ib9BLAWs7k2YKBQsFRkZG9A==}
-
-  is-alphanumerical@2.0.1:
-    resolution: {integrity: sha512-hmbYhX/9MUMF5uh7tOXyK/n0ZvWpad5caBA17GsC6vyuCqaWliRG5K1qS9inmUhEMaOBIW7/whAnSwveW/LtZw==}
-
-  is-arrayish@0.2.1:
-    resolution: {integrity: sha512-zz06S8t0ozoDXMG+ube26zeCTNXcKIPJZJi8hBrF4idCLms4CG9QtK7qBl1boi5ODzFpjswb5JPmHCbMpjaYzg==}
-
-  is-binary-path@2.1.0:
-    resolution: {integrity: sha512-ZMERYes6pDydyuGidse7OsHxtbI7WVeUEozgR/g7rd0xUimYNlvZRE/K2MgZTjWy725IfelLeVcEM97mmtRGXw==}
-    engines: {node: '>=8'}
-
-  is-buffer@2.0.5:
-    resolution: {integrity: sha512-i2R6zNFDwgEHJyQUtJEk0XFi1i0dPFn/oqjK3/vPCcDeJvW5NQ83V8QbicfF1SupOaB0h8ntgBC2YiE7dfyctQ==}
-    engines: {node: '>=4'}
-
-  is-ci@3.0.1:
-    resolution: {integrity: sha512-ZYvCgrefwqoQ6yTyYUbQu64HsITZ3NfKX1lzaEYdkTDcfKzzCI/wthRRYKkdjHKFVgNiXKAKm65Zo1pk2as/QQ==}
-    hasBin: true
-
-  is-core-module@2.16.2:
-    resolution: {integrity: sha512-evOr8xfXKxE6qSR0hSXL2r3sd7ALj8+7jQEUvPYcm5sgZFdJ+AYzT6yNmJenvIYQBgIGwfwz08sL8zoL7yq2BA==}
-    engines: {node: '>= 0.4'}
-
-  is-decimal@1.0.4:
-    resolution: {integrity: sha512-RGdriMmQQvZ2aqaQq3awNA6dCGtKpiDFcOzrTWrDAT2MiWrKQVPmxLGHl7Y2nNu6led0kEyoX0enY0qXYsv9zw==}
-
-  is-decimal@2.0.1:
-    resolution: {integrity: sha512-AAB9hiomQs5DXWcRB1rqsxGUstbRroFOPPVAomNk/3XHR5JyEZChOyTWe2oayKnsSsr/kcGqF+z6yuH6HHpN0A==}
-
-  is-docker@2.2.1:
-    resolution: {integrity: sha512-F+i2BKsFrH66iaUFc0woD8sLy8getkwTwtOBjvs56Cx4CgJDeKQeqfz8wAYiSb8JOprWhHH5p77PbmYCvvUuXQ==}
-    engines: {node: '>=8'}
-    hasBin: true
-
-  is-docker@3.0.0:
-    resolution: {integrity: sha512-eljcgEDlEns/7AXFosB5K/2nCM4P7FQPkGc/DWLy5rmFEWvZayGrik1d9/QIY5nJ4f9YsVvBkA6kJpHn9rISdQ==}
-    engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
-    hasBin: true
-
-  is-extendable@0.1.1:
-    resolution: {integrity: sha512-5BMULNob1vgFX6EjQw5izWDxrecWK9AM72rugNr0TFldMOi0fj6Jk+zeKIt0xGj4cEfQIJth4w3OKWOJ4f+AFw==}
-    engines: {node: '>=0.10.0'}
-
-  is-extglob@2.1.1:
-    resolution: {integrity: sha512-SbKbANkN603Vi4jEZv49LeVJMn4yGwsbzZworEoyEiutsN3nJYdbO36zfhGJ6QEDpOZIFkDtnq5JRxmvl3jsoQ==}
-    engines: {node: '>=0.10.0'}
-
-  is-fullwidth-code-point@3.0.0:
-    resolution: {integrity: sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg==}
-    engines: {node: '>=8'}
-
-  is-glob@4.0.3:
-    resolution: {integrity: sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg==}
-    engines: {node: '>=0.10.0'}
-
-  is-hexadecimal@1.0.4:
-    resolution: {integrity: sha512-gyPJuv83bHMpocVYoqof5VDiZveEoGoFL8m3BXNb2VW8Xs+rz9kqO8LOQ5DH6EsuvilT1ApazU0pyl+ytbPtlw==}
-
-  is-hexadecimal@2.0.1:
-    resolution: {integrity: sha512-DgZQp241c8oO6cA1SbTEWiXeoxV42vlcJxgH+B3hi1AiqqKruZR3ZGF8In3fj4+/y/7rHvlOZLZtgJ/4ttYGZg==}
-
-  is-inside-container@1.0.0:
-    resolution: {integrity: sha512-KIYLCCJghfHZxqjYBE7rEy0OBuTd5xCHS7tHVgvCLkx7StIoaxwNW3hCALgEUjFfeRk+MG/Qxmp/vtETEF3tRA==}
-    engines: {node: '>=14.16'}
-    hasBin: true
-
-  is-installed-globally@0.4.0:
-    resolution: {integrity: sha512-iwGqO3J21aaSkC7jWnHP/difazwS7SFeIqxv6wEtLU8Y5KlzFTjyqcSIT0d8s4+dDhKytsk9PJZ2BkS5eZwQRQ==}
-    engines: {node: '>=10'}
-
-  is-network-error@1.3.2:
-    resolution: {integrity: sha512-PhBY86zaxNZUuWP6h13Vu5oFe0XY6/UlKzQnYFELzGVHygP3MxmvTfYSG7GN3aIab/iWudSMgjSnG9Dq+nHrgA==}
-    engines: {node: '>=16'}
-
-  is-npm@6.1.0:
-    resolution: {integrity: sha512-O2z4/kNgyjhQwVR1Wpkbfc19JIhggF97NZNCpWTnjH7kVcZMUrnut9XSN7txI7VdyIYk5ZatOq3zvSuWpU8hoA==}
-    engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
-
-  is-number@7.0.0:
-    resolution: {integrity: sha512-41Cifkg6e8TylSpdtTpeLVMqvSBEVzTttHvERD741+pnZ8ANv0004MRL43QKPDlK9cGvNp6NZWZUBlbGXYxxng==}
-    engines: {node: '>=0.12.0'}
-
-  is-obj@1.0.1:
-    resolution: {integrity: sha512-l4RyHgRqGN4Y3+9JHVrNqO+tN0rV5My76uW5/nuO4K1b6vw5G8d/cmFjP9tRfEsdhZNt0IFdZuK/c2Vr4Nb+Qg==}
-    engines: {node: '>=0.10.0'}
-
-  is-obj@2.0.0:
-    resolution: {integrity: sha512-drqDG3cbczxxEJRoOXcOjtdp1J/lyp1mNn0xaznRs8+muBhgQcrnbspox5X5fOw0HnMnbfDzvnEMEtqDEJEo8w==}
-    engines: {node: '>=8'}
-
-  is-path-inside@3.0.3:
-    resolution: {integrity: sha512-Fd4gABb+ycGAmKou8eMftCupSir5lRxqf4aD/vd0cD2qc4HL07OjCeuHMr8Ro4CoMaeCKDB0/ECBOVWjTwUvPQ==}
-    engines: {node: '>=8'}
-
-  is-plain-obj@2.1.0:
-    resolution: {integrity: sha512-YWnfyRwxL/+SsrWYfOpUtz5b3YD+nyfkHvjbcanzk8zgyO4ASD67uVMRt8k5bM4lLMDnXfriRhOpemw+NfT1eA==}
-    engines: {node: '>=8'}
-
-  is-plain-obj@3.0.0:
-    resolution: {integrity: sha512-gwsOE28k+23GP1B6vFl1oVh/WOzmawBrKwo5Ev6wMKzPkaXaCDIQKzLnvsA42DRlbVTWorkgTKIviAKCWkfUwA==}
-    engines: {node: '>=10'}
-
-  is-plain-obj@4.1.0:
-    resolution: {integrity: sha512-+Pgi+vMuUNkJyExiMBt5IlFoMyKnr5zhJ4Uspz58WOhBF5QoIZkFyNHIbBAtHwzVAgk5RtndVNsDRN61/mmDqg==}
-    engines: {node: '>=12'}
-
-  is-plain-object@2.0.4:
-    resolution: {integrity: sha512-h5PpgXkWitc38BBMYawTYMWJHFZJVnBquFE57xFpjB8pJFiF6gZ+bU+WyI/yqXiFR5mdLsgYNaPe8uao6Uv9Og==}
-    engines: {node: '>=0.10.0'}
-
-  is-regexp@1.0.0:
-    resolution: {integrity: sha512-7zjFAPO4/gwyQAAgRRmqeEeyIICSdmCqa3tsVHMdBzaXXRiqopZL4Cyghg/XulGWrtABTpbnYYzzIRffLkP4oA==}
-    engines: {node: '>=0.10.0'}
-
-  is-stream@2.0.1:
-    resolution: {integrity: sha512-hFoiJiTl63nn+kstHGBtewWSKnQLpyb155KHheA1l39uvtO9nWIop1p3udqPcUd/xbF1VLMO4n7OI6p7RbngDg==}
-    engines: {node: '>=8'}
-
-  is-typedarray@1.0.0:
-    resolution: {integrity: sha512-cyA56iCMHAh5CdzjJIa4aohJyeO1YbwLi3Jc35MmRU6poroFjIGZzUzupGiRPOjgHg9TLu43xbpwXk523fMxKA==}
-
-  is-url@1.2.4:
-    resolution: {integrity: sha512-ITvGim8FhRiYe4IQ5uHSkj7pVaPDrCTkNd3yq3cV7iZAcJdHTUMPMEHcqSOy9xZ9qFenQCvi+2wjH9a1nXqHww==}
-
-  is-wsl@2.2.0:
-    resolution: {integrity: sha512-fKzAra0rGJUUBwGBgNkHZuToZcn+TtXHpeCgmkMJMMYx1sQDYaCSyjJBSCa2nH1DGm7s3n1oBnohoVTBaN7Lww==}
-    engines: {node: '>=8'}
-
-  is-wsl@3.1.1:
-    resolution: {integrity: sha512-e6rvdUCiQCAuumZslxRJWR/Doq4VpPR82kqclvcS0efgt430SlGIk05vdCN58+VrzgtIcfNODjozVielycD4Sw==}
-    engines: {node: '>=16'}
-
-  is-yarn-global@0.4.1:
-    resolution: {integrity: sha512-/kppl+R+LO5VmhYSEWARUFjodS25D68gvj8W7z0I7OWhUla5xWu8KL6CtB2V0R6yqhnRgbcaREMr4EEM6htLPQ==}
-    engines: {node: '>=12'}
-
-  isarray@0.0.1:
-    resolution: {integrity: sha512-D2S+3GLxWH+uhrNEcoh/fnmYeP8E8/zHl644d/jdA0g2uyXvy3sb0qxotE+ne0LtccHknQzWwZEzhak7oJ0COQ==}
-
-  isarray@1.0.0:
-    resolution: {integrity: sha512-VLghIWNM6ELQzo7zwmcg0NmTVyWKYjvIeM83yjp0wRDTmUnrM678fQbcKBo6n2CJEF0szoG//ytg+TKla89ALQ==}
-
-  isexe@2.0.0:
-    resolution: {integrity: sha512-RHxMLp9lnKHGHRng9QFhRCMbYAcVpn69smSGcq3f36xjgVVWThj4qqLbTLlq7Ssj8B+fIQ1EuCEGI2lKsyQeIw==}
-
-  isobject@3.0.1:
-    resolution: {integrity: sha512-WhB9zCku7EGTj/HQQRz5aUQEUeoQZH2bWcltRErOpymJ4boYE6wL9Tbr23krRPSZ+C5zqNSrSw+Cc7sZZ4b7vg==}
-    engines: {node: '>=0.10.0'}
-
-  isomorphic-fetch@3.0.0:
-    resolution: {integrity: sha512-qvUtwJ3j6qwsF3jLxkZ72qCgjMysPzDfeV240JHiGZsANBYd+EEuu35v7dfrJ9Up0Ak07D7GGSkGhCHTqg/5wA==}
-
-  jest-util@29.7.0:
-    resolution: {integrity: sha512-z6EbKajIpqGKU56y5KBUgy1dt1ihhQJgWzUlZHArA/+X2ad7Cb5iF+AK1EWVL/Bo7Rz9uurpqw6SiBCefUbCGA==}
-    engines: {node: ^14.15.0 || ^16.10.0 || >=18.0.0}
-
-  jest-worker@27.5.1:
-    resolution: {integrity: sha512-7vuh85V5cdDofPyxn58nrPjBktZo0u9x1g8WtjQol+jZDaE+fhN+cIvTj11GndBnMnyfrUOG1sZQxCdjKh+DKg==}
-    engines: {node: '>= 10.13.0'}
-
-  jest-worker@29.7.0:
-    resolution: {integrity: sha512-eIz2msL/EzL9UFTFFx7jBTkeZfku0yUAyZZZmJ93H2TYEiroIx2PQjEXcwYtYl8zXCxb+PAmA2hLIt/6ZEkPHw==}
-    engines: {node: ^14.15.0 || ^16.10.0 || >=18.0.0}
-
-  jiti@1.21.7:
-    resolution: {integrity: sha512-/imKNG4EbWNrVjoNC/1H5/9GFy+tqjGBHCaSsN+P2RnPqjsLmv6UD3Ej+Kj8nBWaRAwyk7kK5ZUc+OEatnTR3A==}
-    hasBin: true
-
-  joi@17.13.3:
-    resolution: {integrity: sha512-otDA4ldcIx+ZXsKHWmp0YizCweVRZG96J10b0FevjfuncLO1oX59THoAmHkNubYJ+9gWsYsp5k8v4ib6oDv1fA==}
-
-  jotai@1.13.1:
-    resolution: {integrity: sha512-RUmH1S4vLsG3V6fbGlKzGJnLrDcC/HNb5gH2AeA9DzuJknoVxSGvvg8OBB7lke+gDc4oXmdVsaKn/xDUhWZ0vw==}
-    engines: {node: '>=12.20.0'}
-    peerDependencies:
-      '@babel/core': '*'
-      '@babel/template': '*'
-      jotai-devtools: '*'
-      jotai-immer: '*'
-      jotai-optics: '*'
-      jotai-redux: '*'
-      jotai-tanstack-query: '*'
-      jotai-urql: '*'
-      jotai-valtio: '*'
-      jotai-xstate: '*'
-      jotai-zustand: '*'
-      react: '>=16.8'
-    peerDependenciesMeta:
-      '@babel/core':
-        optional: true
-      '@babel/template':
-        optional: true
-      jotai-devtools:
-        optional: true
-      jotai-immer:
-        optional: true
-      jotai-optics:
-        optional: true
-      jotai-redux:
-        optional: true
-      jotai-tanstack-query:
-        optional: true
-      jotai-urql:
-        optional: true
-      jotai-valtio:
-        optional: true
-      jotai-xstate:
-        optional: true
-      jotai-zustand:
-        optional: true
-
-  js-cookie@2.2.1:
-    resolution: {integrity: sha512-HvdH2LzI/EAZcUwA8+0nKNtWHqS+ZmijLA30RwZA0bo7ToCckjK5MkGhjED9KoRcXO6BaGI3I9UIzSA1FKFPOQ==}
-
-  js-levenshtein@1.1.6:
-    resolution: {integrity: sha512-X2BB11YZtrRqY4EnQcLX5Rh373zbK4alC1FW7D7MBhL2gtcC17cTnr6DmfHZeS0s2rTHjUTMMHfG7gO8SSdw+g==}
-    engines: {node: '>=0.10.0'}
-
-  js-tokens@4.0.0:
-    resolution: {integrity: sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ==}
-
-  js-yaml@3.15.1:
-    resolution: {integrity: sha512-S99WuO3HlhO3XN41EtYUNl9zzXjoJx7QvmipxsJVxtCBT0YHEFy+iOJhjSvrmV12nYhWpZaM8lPHkJm0yUMbag==}
-    hasBin: true
-
-  js-yaml@4.1.0:
-    resolution: {integrity: sha512-wpxZs9NoxZaJESJGIZTyDEaYpl0FKSA+FB9aJiyemKhMwkxQg63h4T1KJgUGHpTqPDNRcmmYLugrRjJlBtWvRA==}
-    hasBin: true
-
-  js-yaml@4.3.1:
-    resolution: {integrity: sha512-CY6crGq313MX8GkwvB7tzgp99vjQxY1++5y10/BKN/GUfHqWaOGQMNZkBvqSzsZKWk/ijwHlWzzkLulsGHhjWQ==}
-    hasBin: true
-
-  jsesc@3.1.0:
-    resolution: {integrity: sha512-/sM3dO2FOzXjKQhJuo0Q173wf2KOo8t4I8vHy6lF9poUp7bKT0/NHE8fPX23PwfhnykfqnC2xRxOnVw5XuGIaA==}
-    engines: {node: '>=6'}
-    hasBin: true
-
-  json-buffer@3.0.1:
-    resolution: {integrity: sha512-4bV5BfR2mqfQTJm+V5tPPdf+ZpuhiIvTuAB5g8kcrXOZpTT/QwwVRWBywX1ozr6lEuPdbHxwaJlm9G6mI2sfSQ==}
-
-  json-crawl@0.5.3:
-    resolution: {integrity: sha512-BEjjCw8c7SxzNK4orhlWD5cXQh8vCk2LqDr4WgQq4CV+5dvopeYwt1Tskg67SuSLKvoFH5g0yuYtg7rcfKV6YA==}
-    engines: {node: '>=14.0.0'}
-
-  json-parse-even-better-errors@2.3.1:
-    resolution: {integrity: sha512-xyFwyhro/JEof6Ghe2iz2NcXoj2sloNsWr/XsERDK/oiPCfaNhl5ONfp+jQdAZRQQ0IJWNzH9zIZF7li91kh2w==}
-
-  json-pointer@0.6.2:
-    resolution: {integrity: sha512-vLWcKbOaXlO+jvRy4qNd+TI1QUPZzfJj1tpJ3vAXDych5XJf93ftpUKe5pKCrzyIIwgBJcOcCVRUfqQP25afBw==}
-
-  json-schema-compare@0.2.2:
-    resolution: {integrity: sha512-c4WYmDKyJXhs7WWvAWm3uIYnfyWFoIp+JEoX34rctVvEkMYCPGhXtvmFFXiffBbxfZsvQ0RNnV5H7GvDF5HCqQ==}
-
-  json-schema-merge-allof@0.8.1:
-    resolution: {integrity: sha512-CTUKmIlPJbsWfzRRnOXz+0MjIqvnleIXwFTzz+t9T86HnYX/Rozria6ZVGLktAU9e+NygNljveP+yxqtQp/Q4w==}
-    engines: {node: '>=12.0.0'}
-
-  json-schema-to-ts@2.7.2:
-    resolution: {integrity: sha512-R1JfqKqbBR4qE8UyBR56Ms30LL62/nlhoz+1UkfI/VE7p54Awu919FZ6ZUPG8zIa3XB65usPJgr1ONVncUGSaQ==}
-    engines: {node: '>=16'}
-
-  json-schema-traverse@0.4.1:
-    resolution: {integrity: sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg==}
-
-  json-schema-traverse@1.0.0:
-    resolution: {integrity: sha512-NM8/P9n3XjXhIZn1lLhkFaACTOURQXjWhV4BA/RnOv8xvgqtqpAX9IO4mRQxSx1Rlo4tqzeqb0sOlruaOy3dug==}
-
-  json-stable-stringify-without-jsonify@1.0.1:
-    resolution: {integrity: sha512-Bdboy+l7tA3OGW6FjyFHWkP5LuByj1Tk33Ljyq0axyzdk9//JSi2u3fP1QSmd1KNwq6VOKYGlAu87CisVir6Pw==}
-
-  json5@2.2.3:
-    resolution: {integrity: sha512-XmOWe7eyHYH14cLdVPoyg+GOH3rYX++KpzrylJwSW98t3Nk+U8XOl8FWKOgwtzdb8lXGf6zYwDUzeHMWfxasyg==}
-    engines: {node: '>=6'}
-    hasBin: true
-
-  jsonc-parser@2.2.1:
-    resolution: {integrity: sha512-o6/yDBYccGvTz1+QFevz6l6OBZ2+fMVu2JZ9CIhzsYRX4mjaK5IyX9eldUdCmga16zlgQxyrj5pt9kzuj2C02w==}
-
-  jsonfile@6.2.1:
-    resolution: {integrity: sha512-zwOTdL3rFQ/lRdBnntKVOX6k5cKJwEc1HdilT71BWEu7J41gXIB2MRp+vxduPSwZJPWBxEzv4yH1wYLJGUHX4Q==}
-
-  jsonpointer@5.0.1:
-    resolution: {integrity: sha512-p/nXbhSEcu3pZRdkW1OfJhpsVtW1gd4Wa1fnQc9YLiTfAjn0312eMKimbdIQzuZl9aa9xUGaRlP9T/CJE/ditQ==}
-    engines: {node: '>=0.10.0'}
-
-  katex@0.16.47:
-    resolution: {integrity: sha512-Eeo8Ys1doU1z+x8AZsPpQu+p/QcZBI5PeOo7QGQdy2x2m0MU/hYagBbGOmXwr5KVbEfVuWv9LpnQWeehogurjg==}
-    hasBin: true
-
-  keyv@4.5.4:
-    resolution: {integrity: sha512-oxVHkHR/EJf2CNXnWxRLW6mg7JyCCUcG0DtEGmL2ctUo1PNTin1PUil+r/+4r5MpVgC/fn1kjsx7mjSujKqIpw==}
-
-  khroma@2.1.0:
-    resolution: {integrity: sha512-Ls993zuzfayK269Svk9hzpeGUKob/sIgZzyHYdjQoAdQetRKpOLj+k/QQQ/6Qi0Yz65mlROrfd+Ev+1+7dz9Kw==}
-
-  kind-of@6.0.3:
-    resolution: {integrity: sha512-dcS1ul+9tmeD95T+x28/ehLgd9mENa3LsvDTtzm3vyBEO7RPptvAD+t44WVXaUjTBRcrpFeFlC8WCruUR456hw==}
-    engines: {node: '>=0.10.0'}
-
-  kleur@3.0.3:
-    resolution: {integrity: sha512-eTIzlVOSUR+JxdDFepEYcBMtZ9Qqdef+rnzWdRZuMbOywu5tO2w2N7rqjoANZ5k9vywhL6Br1VRjUIgTQx4E8w==}
-    engines: {node: '>=6'}
-
-  kleur@4.1.5:
-    resolution: {integrity: sha512-o+NO+8WrRiQEE4/7nwRJhN1HWpVmJm511pBHUxPLtp0BUISzlBplORYSmTclCnJvQq2tKu/sgl3xVpkc7ZWuQQ==}
-    engines: {node: '>=6'}
-
-  latest-version@7.0.0:
-    resolution: {integrity: sha512-KvNT4XqAMzdcL6ka6Tl3i2lYeFDgXNCuIX+xNx6ZMVR1dFq+idXd9FLKNMOIx0t9mJ9/HudyX4oZWXZQ0UJHeg==}
-    engines: {node: '>=14.16'}
-
-  launch-editor@2.14.1:
-    resolution: {integrity: sha512-QWBrQsMpH7gPr965dsKD/3cKWiNoTjpATQf++Xq63N6sKRGMwlVXz41O1IZTMfZQgBctD/K5Zt06+/I6pP6+HA==}
-
-  layout-base@1.0.2:
-    resolution: {integrity: sha512-8h2oVEZNktL4BH2JCOI90iD1yXwL6iNW7KcCKT2QZgQJR2vbqDsldCTPRU9NifTCqHZci57XvQQ15YTu+sTYPg==}
-
-  layout-base@2.0.1:
-    resolution: {integrity: sha512-dp3s92+uNI1hWIpPGH3jK2kxE2lMjdXdr+DH8ynZHpd6PUlH6x6cbuXnoMmiNumznqaNO31xu9e79F0uuZ0JFg==}
-
-  leven@3.1.0:
-    resolution: {integrity: sha512-qsda+H8jTaUaN/x5vzW2rzc+8Rw4TAQ/4KjB46IwK5VH+IlVeeeje/EoZRpiXvIqjFgK84QffqPztGI3VBLG1A==}
-    engines: {node: '>=6'}
-
-  levn@0.4.1:
-    resolution: {integrity: sha512-+bT2uH4E5LGE7h/n3evcS/sQlJXCpIp6ym8OWJ5eV6+67Dsql/LaaT7qJBAt2rzfoa/5QBGBhxDix1dMt2kQKQ==}
-    engines: {node: '>= 0.8.0'}
-
-  lightningcss-android-arm64@1.32.0:
-    resolution: {integrity: sha512-YK7/ClTt4kAK0vo6w3X+Pnm0D2cf2vPHbhOXdoNti1Ga0al1P4TBZhwjATvjNwLEBCnKvjJc2jQgHXH0NEwlAg==}
-    engines: {node: '>= 12.0.0'}
-    cpu: [arm64]
-    os: [android]
-
-  lightningcss-darwin-arm64@1.32.0:
-    resolution: {integrity: sha512-RzeG9Ju5bag2Bv1/lwlVJvBE3q6TtXskdZLLCyfg5pt+HLz9BqlICO7LZM7VHNTTn/5PRhHFBSjk5lc4cmscPQ==}
-    engines: {node: '>= 12.0.0'}
-    cpu: [arm64]
-    os: [darwin]
-
-  lightningcss-darwin-x64@1.32.0:
-    resolution: {integrity: sha512-U+QsBp2m/s2wqpUYT/6wnlagdZbtZdndSmut/NJqlCcMLTWp5muCrID+K5UJ6jqD2BFshejCYXniPDbNh73V8w==}
-    engines: {node: '>= 12.0.0'}
-    cpu: [x64]
-    os: [darwin]
-
-  lightningcss-freebsd-x64@1.32.0:
-    resolution: {integrity: sha512-JCTigedEksZk3tHTTthnMdVfGf61Fky8Ji2E4YjUTEQX14xiy/lTzXnu1vwiZe3bYe0q+SpsSH/CTeDXK6WHig==}
-    engines: {node: '>= 12.0.0'}
-    cpu: [x64]
-    os: [freebsd]
-
-  lightningcss-linux-arm-gnueabihf@1.32.0:
-    resolution: {integrity: sha512-x6rnnpRa2GL0zQOkt6rts3YDPzduLpWvwAF6EMhXFVZXD4tPrBkEFqzGowzCsIWsPjqSK+tyNEODUBXeeVHSkw==}
-    engines: {node: '>= 12.0.0'}
-    cpu: [arm]
-    os: [linux]
-
-  lightningcss-linux-arm64-gnu@1.32.0:
-    resolution: {integrity: sha512-0nnMyoyOLRJXfbMOilaSRcLH3Jw5z9HDNGfT/gwCPgaDjnx0i8w7vBzFLFR1f6CMLKF8gVbebmkUN3fa/kQJpQ==}
-    engines: {node: '>= 12.0.0'}
-    cpu: [arm64]
-    os: [linux]
-    libc: [glibc]
-
-  lightningcss-linux-arm64-musl@1.32.0:
-    resolution: {integrity: sha512-UpQkoenr4UJEzgVIYpI80lDFvRmPVg6oqboNHfoH4CQIfNA+HOrZ7Mo7KZP02dC6LjghPQJeBsvXhJod/wnIBg==}
-    engines: {node: '>= 12.0.0'}
-    cpu: [arm64]
-    os: [linux]
-    libc: [musl]
-
-  lightningcss-linux-x64-gnu@1.32.0:
-    resolution: {integrity: sha512-V7Qr52IhZmdKPVr+Vtw8o+WLsQJYCTd8loIfpDaMRWGUZfBOYEJeyJIkqGIDMZPwPx24pUMfwSxxI8phr/MbOA==}
-    engines: {node: '>= 12.0.0'}
-    cpu: [x64]
-    os: [linux]
-    libc: [glibc]
-
-  lightningcss-linux-x64-musl@1.32.0:
-    resolution: {integrity: sha512-bYcLp+Vb0awsiXg/80uCRezCYHNg1/l3mt0gzHnWV9XP1W5sKa5/TCdGWaR/zBM2PeF/HbsQv/j2URNOiVuxWg==}
-    engines: {node: '>= 12.0.0'}
-    cpu: [x64]
-    os: [linux]
-    libc: [musl]
-
-  lightningcss-win32-arm64-msvc@1.32.0:
-    resolution: {integrity: sha512-8SbC8BR40pS6baCM8sbtYDSwEVQd4JlFTOlaD3gWGHfThTcABnNDBda6eTZeqbofalIJhFx0qKzgHJmcPTnGdw==}
-    engines: {node: '>= 12.0.0'}
-    cpu: [arm64]
-    os: [win32]
-
-  lightningcss-win32-x64-msvc@1.32.0:
-    resolution: {integrity: sha512-Amq9B/SoZYdDi1kFrojnoqPLxYhQ4Wo5XiL8EVJrVsB8ARoC1PWW6VGtT0WKCemjy8aC+louJnjS7U18x3b06Q==}
-    engines: {node: '>= 12.0.0'}
-    cpu: [x64]
-    os: [win32]
-
-  lightningcss@1.32.0:
-    resolution: {integrity: sha512-NXYBzinNrblfraPGyrbPoD19C1h9lfI/1mzgWYvXUTe414Gz/X1FD2XBZSZM7rRTrMA8JL3OtAaGifrIKhQ5yQ==}
-    engines: {node: '>= 12.0.0'}
-
-  lilconfig@3.1.3:
-    resolution: {integrity: sha512-/vlFKAoH5Cgt3Ie+JLhRbwOsCQePABiU3tJ1egGvyQ+33R/vcwM2Zl2QR/LzjsBeItPt3oSVXapn+m4nQDvpzw==}
-    engines: {node: '>=14'}
-
-  lines-and-columns@1.2.4:
-    resolution: {integrity: sha512-7ylylesZQ/PV29jhEDl3Ufjo6ZX7gCqJr5F7PKrqc93v7fzSymt1BpwEU8nAUXs8qzzvqhbjhK5QZg6Mt/HkBg==}
-
-  liquid-json@0.3.1:
-    resolution: {integrity: sha512-wUayTU8MS827Dam6MxgD72Ui+KOSF+u/eIqpatOtjnvgJ0+mnDq33uC2M7J0tPK+upe/DpUAuK4JUU89iBoNKQ==}
-    engines: {node: '>=4'}
-
-  loader-runner@4.3.2:
-    resolution: {integrity: sha512-DFEqQ3ihfS9blba08cLfYf1NRAIEm+dDjic073DRDc3/JspI/8wYmtDsHwd3+4hwvdxSK7PGaElfTmm0awWJ4w==}
-    engines: {node: '>=6.11.5'}
-
-  loader-utils@2.0.4:
-    resolution: {integrity: sha512-xXqpXoINfFhgua9xiqD8fPFHgkoq1mmmpE92WlDbm9rNRd/EbRb+Gqf908T2DMfuHjjJlksiK2RbHVOdD/MqSw==}
-    engines: {node: '>=8.9.0'}
-
-  locate-path@6.0.0:
-    resolution: {integrity: sha512-iPZK6eYjbxRu3uB4/WZ3EsEIMJFMqAoopl3R+zuq0UjcAm/MO6KCweDgPfP3elTztoKP3KtnVHxTn2NHBSDVUw==}
-    engines: {node: '>=10'}
-
-  locate-path@7.2.0:
-    resolution: {integrity: sha512-gvVijfZvn7R+2qyPX8mAuKcFGDf6Nc61GdvGafQsHL0sBIxfKzA+usWn4GFC/bk+QdwPUD4kWFJLhElipq+0VA==}
-    engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
-
-  lodash-es@4.18.1:
-    resolution: {integrity: sha512-J8xewKD/Gk22OZbhpOVSwcs60zhd95ESDwezOFuA3/099925PdHJ7OFHNTGtajL3AlZkykD32HykiMo+BIBI8A==}
-
-  lodash.debounce@4.0.8:
-    resolution: {integrity: sha512-FT1yDzDYEoYWhnSGnpE/4Kj1fLZkDFyqRb7fNt6FdYOSxlUWAtp42Eh6Wb0rGIv/m9Bgo7x4GhQbm5Ys4SG5ow==}
-
-  lodash.get@4.4.2:
-    resolution: {integrity: sha512-z+Uw/vLuy6gQe8cfaFWD7p0wVv8fJl3mbzXh33RS+0oW2wvUqiRXiQ69gLWSLpgB5/6sU+r6BlQR0MBILadqTQ==}
-    deprecated: This package is deprecated. Use the optional chaining (?.) operator instead.
-
-  lodash.memoize@4.1.2:
-    resolution: {integrity: sha512-t7j+NzmgnQzTAYXcsHYLgimltOV1MXHtlOWf6GjL9Kj8GK5FInw5JotxvbOs+IvV1/Dzo04/fCGfLVs7aXb4Ag==}
-
-  lodash.uniq@4.5.0:
-    resolution: {integrity: sha512-xfBaXQd9ryd9dlSDvnvI0lvxfLJlYAZzXomUYzLKtUeOQvOP5piqAWuGtrhWeqaXK9hhoM/iyJc5AV+XfsX3HQ==}
-
-  lodash@4.17.21:
-    resolution: {integrity: sha512-v2kDEe57lecTulaDIuNTPy3Ry4gLGJ6Z1O3vE1krgXZNrsQ+LFTGHVxVjcXPs17LhbZVGedAJv8XZ1tvj5FvSg==}
-
-  lodash@4.17.23:
-    resolution: {integrity: sha512-LgVTMpQtIopCi79SJeDiP0TfWi5CNEc/L/aRdTh3yIvmZXTnheWpKjSZhnvMl8iXbC1tFg9gdHHDMLoV7CnG+w==}
-
-  lodash@4.18.1:
-    resolution: {integrity: sha512-dMInicTPVE8d1e5otfwmmjlxkZoUpiVLwyeTdUsi/Caj/gfzzblBcCE5sRHV/AsjuCmxWrte2TNGSYuCeCq+0Q==}
-
-  longest-streak@2.0.4:
-    resolution: {integrity: sha512-vM6rUVCVUJJt33bnmHiZEvr7wPT78ztX7rojL+LW51bHtLh6HTjx84LA5W4+oa6aKEJA7jJu5LR6vQRBpA5DVg==}
-
-  longest-streak@3.1.0:
-    resolution: {integrity: sha512-9Ri+o0JYgehTaVBBDoMqIl8GXtbWg711O3srftcHhZ0dqnETqLaoIK0x17fUw9rFSlK/0NlsKe0Ahhyl5pXE2g==}
-
-  loose-envify@1.4.0:
-    resolution: {integrity: sha512-lyuxPGr/Wfhrlem2CL/UcnUc1zcqKAImBDzukY7Y5F/yQiNdko6+fRLevlw1HgMySw7f611UIY408EtxRSoK3Q==}
-    hasBin: true
-
-  lower-case@2.0.2:
-    resolution: {integrity: sha512-7fm3l3NAF9WfN6W3JOmf5drwpVqX78JtoGJ3A6W0a6ZnldM41w2fV5D490psKFTpMds8TJse/eHLFFsNHHjHgg==}
-
-  lowercase-keys@3.0.0:
-    resolution: {integrity: sha512-ozCC6gdQ+glXOQsveKD0YsDy8DSQFjDTz4zyzEHNV5+JP5D62LmfDZ6o1cycFx9ouG940M5dE8C8CTewdj2YWQ==}
-    engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
-
-  lowlight@1.20.0:
-    resolution: {integrity: sha512-8Ktj+prEb1RoCPkEOrPMYUN/nCggB7qAWe3a7OpMjWQkh3l2RD5wKRQ+o8Q8YuI9RG/xs95waaI/E6ym/7NsTw==}
-
-  lru-cache@11.5.1:
-    resolution: {integrity: sha512-RPimw/7aMdv2oqRrxKwvZXcPfwBrn/JZ2xYcY9Hus/6LaS3VOAKVWKWgNLCFSiOm1ESXinjsDlidVU7JlnCN2A==}
-    engines: {node: 20 || >=22}
-
-  lru-cache@5.1.1:
-    resolution: {integrity: sha512-KpNARQA3Iwv+jTA0utUVVbrh+Jlrr1Fv0e56GGzAFOXN7dk/FviaDW8LHmK52DlcH4WP2n6gI8vN1aesBFgo9w==}
-
-  magic-error@0.0.1:
-    resolution: {integrity: sha512-1+N1ET8cbC5bfLQZcRojClzgK2gbUt9keTMr9OJeuXnQKWsfwRRRICuMA3HKaCIXFEgKzxivuMGCNKD7cdU5pg==}
-    engines: {node: '>=10'}
-
-  markdown-extensions@2.0.0:
-    resolution: {integrity: sha512-o5vL7aDWatOTX8LzaS1WMoaoxIiLRQJuIKKe2wAw6IeULDHaqbiqiggmx+pKvZDb1Sj+pE46Sn1T7lCqfFtg1Q==}
-    engines: {node: '>=16'}
-
-  markdown-table@2.0.0:
-    resolution: {integrity: sha512-Ezda85ToJUBhM6WGaG6veasyym+Tbs3cMAw/ZhOPqXiYsr0jgocBV3j3nx+4lk47plLlIqjwuTm/ywVI+zjJ/A==}
-
-  markdown-table@3.0.4:
-    resolution: {integrity: sha512-wiYz4+JrLyb/DqW2hkFJxP7Vd7JuTDm77fvbM8VfEQdmSMqcImWeeRbHwZjBjIFki/VaMK2BhFi7oUUZeM5bqw==}
-
-  markdown-to-jsx@7.7.17:
-    resolution: {integrity: sha512-7mG/1feQ0TX5I7YyMZVDgCC/y2I3CiEhIRQIhyov9nGBP5eoVrOXXHuL5ZP8GRfxVZKRiXWJgwXkb9It+nQZfQ==}
-    engines: {node: '>= 10'}
-    peerDependencies:
-      react: '>= 0.14.0'
-    peerDependenciesMeta:
-      react:
-        optional: true
-
-  marked@16.4.2:
-    resolution: {integrity: sha512-TI3V8YYWvkVf3KJe1dRkpnjs68JUPyEa5vjKrp1XEEJUAOaQc+Qj+L1qWbPd0SJuAdQkFU0h73sXXqwDYxsiDA==}
-    engines: {node: '>= 20'}
-    hasBin: true
-
-  math-intrinsics@1.1.0:
-    resolution: {integrity: sha512-/IXtbwEk5HTPyEwyKX6hGkYXxM9nbj64B+ilVJnC/R6B0pH5G4V3b0pVbL7DBj4tkhBAppbQUlf6F6Xl9LHu1g==}
-    engines: {node: '>= 0.4'}
-
-  mdast-util-definitions@5.1.2:
-    resolution: {integrity: sha512-8SVPMuHqlPME/z3gqVwWY4zVXn8lqKv/pAhC57FuJ40ImXyBpmO5ukh98zB2v7Blql2FiHjHv9LVztSIqjY+MA==}
-
-  mdast-util-directive@3.1.0:
-    resolution: {integrity: sha512-I3fNFt+DHmpWCYAT7quoM6lHf9wuqtI+oCOfvILnoicNIqjh5E3dEJWiXuYME2gNe8vl1iMQwyUHa7bgFmak6Q==}
-
-  mdast-util-find-and-replace@1.1.1:
-    resolution: {integrity: sha512-9cKl33Y21lyckGzpSmEQnIDjEfeeWelN5s1kUW1LwdB0Fkuq2u+4GdqcGEygYxJE8GVqCl0741bYXHgamfWAZA==}
-
-  mdast-util-find-and-replace@3.0.2:
-    resolution: {integrity: sha512-Tmd1Vg/m3Xz43afeNxDIhWRtFZgM2VLyaf4vSTYwudTyeuTneoL3qtWMA5jeLyz/O1vDJmmV4QuScFCA2tBPwg==}
-
-  mdast-util-from-markdown@0.8.5:
-    resolution: {integrity: sha512-2hkTXtYYnr+NubD/g6KGBS/0mFmBcifAsI0yIWRiRo0PjVs6SSOSOdtzbp6kSGnShDN6G5aWZpKQ2lWRy27mWQ==}
-
-  mdast-util-from-markdown@1.3.1:
-    resolution: {integrity: sha512-4xTO/M8c82qBcnQc1tgpNtubGUW/Y1tBQ1B0i5CtSoelOLKFYlElIr3bvgREYYO5iRqbMY1YuqZng0GVOI8Qww==}
-
-  mdast-util-from-markdown@2.0.3:
-    resolution: {integrity: sha512-W4mAWTvSlKvf8L6J+VN9yLSqQ9AOAAvHuoDAmPkz4dHf553m5gVj2ejadHJhoJmcmxEnOv6Pa8XJhpxE93kb8Q==}
-
-  mdast-util-frontmatter@0.2.0:
-    resolution: {integrity: sha512-FHKL4w4S5fdt1KjJCwB0178WJ0evnyyQr5kXTM3wrOVpytD0hrkvd+AOOjU9Td8onOejCkmZ+HQRT3CZ3coHHQ==}
-
-  mdast-util-frontmatter@2.0.1:
-    resolution: {integrity: sha512-LRqI9+wdgC25P0URIJY9vwocIzCcksduHQ9OF2joxQoyTNVduwLAFUzjoopuRJbJAReaKrNQKAZKL3uCMugWJA==}
-
-  mdast-util-gfm-autolink-literal@0.1.3:
-    resolution: {integrity: sha512-GjmLjWrXg1wqMIO9+ZsRik/s7PLwTaeCHVB7vRxUwLntZc8mzmTsLVr6HW1yLokcnhfURsn5zmSVdi3/xWWu1A==}
-
-  mdast-util-gfm-autolink-literal@2.0.1:
-    resolution: {integrity: sha512-5HVP2MKaP6L+G6YaxPNjuL0BPrq9orG3TsrZ9YXbA3vDw/ACI4MEsnoDpn6ZNm7GnZgtAcONJyPhOP8tNJQavQ==}
-
-  mdast-util-gfm-footnote@2.1.0:
-    resolution: {integrity: sha512-sqpDWlsHn7Ac9GNZQMeUzPQSMzR6Wv0WKRNvQRg0KqHh02fpTz69Qc1QSseNX29bhz1ROIyNyxExfawVKTm1GQ==}
-
-  mdast-util-gfm-strikethrough@0.2.3:
-    resolution: {integrity: sha512-5OQLXpt6qdbttcDG/UxYY7Yjj3e8P7X16LzvpX8pIQPYJ/C2Z1qFGMmcw+1PZMUM3Z8wt8NRfYTvCni93mgsgA==}
-
-  mdast-util-gfm-strikethrough@2.0.0:
-    resolution: {integrity: sha512-mKKb915TF+OC5ptj5bJ7WFRPdYtuHv0yTRxK2tJvi+BDqbkiG7h7u/9SI89nRAYcmap2xHQL9D+QG/6wSrTtXg==}
-
-  mdast-util-gfm-table@0.1.6:
-    resolution: {integrity: sha512-j4yDxQ66AJSBwGkbpFEp9uG/LS1tZV3P33fN1gkyRB2LoRL+RR3f76m0HPHaby6F4Z5xr9Fv1URmATlRRUIpRQ==}
-
-  mdast-util-gfm-table@2.0.0:
-    resolution: {integrity: sha512-78UEvebzz/rJIxLvE7ZtDd/vIQ0RHv+3Mh5DR96p7cS7HsBhYIICDBCu8csTNWNO6tBWfqXPWekRuj2FNOGOZg==}
-
-  mdast-util-gfm-task-list-item@0.1.6:
-    resolution: {integrity: sha512-/d51FFIfPsSmCIRNp7E6pozM9z1GYPIkSy1urQ8s/o4TC22BZ7DqfHFWiqBD23bc7J3vV1Fc9O4QIHBlfuit8A==}
-
-  mdast-util-gfm-task-list-item@2.0.0:
-    resolution: {integrity: sha512-IrtvNvjxC1o06taBAVJznEnkiHxLFTzgonUdy8hzFVeDun0uTjxxrRGVaNFqkU1wJR3RBPEfsxmU6jDWPofrTQ==}
-
-  mdast-util-gfm@0.1.2:
-    resolution: {integrity: sha512-NNkhDx/qYcuOWB7xHUGWZYVXvjPFFd6afg6/e2g+SV4r9q5XUcCbV4Wfa3DLYIiD+xAEZc6K4MGaE/m0KDcPwQ==}
-
-  mdast-util-gfm@3.1.0:
-    resolution: {integrity: sha512-0ulfdQOM3ysHhCJ1p06l0b0VKlhU0wuQs3thxZQagjcjPrlFRqY215uZGHHJan9GEAXd9MbfPjFJz+qMkVR6zQ==}
-
-  mdast-util-math@3.0.0:
-    resolution: {integrity: sha512-Tl9GBNeG/AhJnQM221bJR2HPvLOSnLE/T9cJI9tlc6zwQk2nPk/4f0cHkOdEixQPC/j8UtKDdITswvLAy1OZ1w==}
-
-  mdast-util-mdx-expression@2.0.1:
-    resolution: {integrity: sha512-J6f+9hUp+ldTZqKRSg7Vw5V6MqjATc+3E4gf3CFNcuZNWD8XdyI6zQ8GqH7f8169MM6P7hMBRDVGnn7oHB9kXQ==}
-
-  mdast-util-mdx-jsx@3.2.0:
-    resolution: {integrity: sha512-lj/z8v0r6ZtsN/cGNNtemmmfoLAFZnjMbNyLzBafjzikOM+glrjNHPlf6lQDOTccj9n5b0PPihEBbhneMyGs1Q==}
-
-  mdast-util-mdx@3.0.0:
-    resolution: {integrity: sha512-JfbYLAW7XnYTTbUsmpu0kdBUVe+yKVJZBItEjwyYJiDJuZ9w4eeaqks4HQO+R7objWgS2ymV60GYpI14Ug554w==}
-
-  mdast-util-mdxjs-esm@2.0.1:
-    resolution: {integrity: sha512-EcmOpxsZ96CvlP03NghtH1EsLtr0n9Tm4lPUJUBccV9RwUOneqSycg19n5HGzCf+10LozMRSObtVr3ee1WoHtg==}
-
-  mdast-util-phrasing@4.1.0:
-    resolution: {integrity: sha512-TqICwyvJJpBwvGAMZjj4J2n0X8QWp21b9l0o7eXyVJ25YNWYbJDVIyD1bZXE6WtV6RmKJVYmQAKWa0zWOABz2w==}
-
-  mdast-util-to-hast@11.3.0:
-    resolution: {integrity: sha512-4o3Cli3hXPmm1LhB+6rqhfsIUBjnKFlIUZvudaermXB+4/KONdd/W4saWWkC+LBLbPMqhFSSTSRgafHsT5fVJw==}
-
-  mdast-util-to-hast@12.3.0:
-    resolution: {integrity: sha512-pits93r8PhnIoU4Vy9bjW39M2jJ6/tdHyja9rrot9uujkN7UTU9SDnE6WNJz/IGyQk3XHX6yNNtrBH6cQzm8Hw==}
-
-  mdast-util-to-hast@13.2.1:
-    resolution: {integrity: sha512-cctsq2wp5vTsLIcaymblUriiTcZd0CwWtCbLvrOzYCDZoWyMNV8sZ7krj09FSnsiJi3WVsHLM4k6Dq/yaPyCXA==}
-
-  mdast-util-to-markdown@0.6.5:
-    resolution: {integrity: sha512-XeV9sDE7ZlOQvs45C9UKMtfTcctcaj/pGwH8YLbMHoMOXNNCn2LsqVQOqrF1+/NU8lKDAqozme9SCXWyo9oAcQ==}
-
-  mdast-util-to-markdown@2.1.2:
-    resolution: {integrity: sha512-xj68wMTvGXVOKonmog6LwyJKrYXZPvlwabaryTjLh9LuvovB/KAH+kvi8Gjj+7rJjsFi23nkUxRQv1KqSroMqA==}
-
-  mdast-util-to-string@2.0.0:
-    resolution: {integrity: sha512-AW4DRS3QbBayY/jJmD8437V1Gombjf8RSOUCMFBuo5iHi58AGEgVCKQ+ezHkZZDpAQS75hcBMpLqjpJTjtUL7w==}
-
-  mdast-util-to-string@3.2.0:
-    resolution: {integrity: sha512-V4Zn/ncyN1QNSqSBxTrMOLpjr+IKdHl2v3KVLoWmDPscP4r9GcCi71gjgvUV1SFSKh92AjAG4peFuBl2/YgCJg==}
-
-  mdast-util-to-string@4.0.0:
-    resolution: {integrity: sha512-0H44vDimn51F0YwvxSJSm0eCDOJTRlmN0R1yBh4HLj9wiV1Dn0QoXGbvFAWj2hSItVTlCmBF1hqKlIyUBVFLPg==}
-
-  mdn-data@2.0.14:
-    resolution: {integrity: sha512-dn6wd0uw5GsdswPFfsgMp5NSB0/aDe6fK94YJV/AJDYXL6HVLWBsxeq7js7Ad+mU2K9LAlwpk6kN2D5mwCPVow==}
-
-  mdn-data@2.0.28:
-    resolution: {integrity: sha512-aylIc7Z9y4yzHYAJNuESG3hfhC+0Ibp/MAMiaOZgNv4pmEdFyfZhhhny4MNiAfWdBQ1RQ2mfDWmM1x8SvGyp8g==}
-
-  mdn-data@2.0.30:
-    resolution: {integrity: sha512-GaqWWShW4kv/G9IEucWScBx9G1/vsFZZJUO+tD26M8J8z3Kw5RDQjaoZe03YAClgeS/SWPOcb4nkFBTEi5DUEA==}
-
-  mdurl@1.0.1:
-    resolution: {integrity: sha512-/sKlQJCBYVY9Ers9hqzKou4H6V5UWc/M59TH2dvkt+84itfnq7uFOMLpOiOS4ujvHP4etln18fmIxA5R5fll0g==}
-
-  media-typer@0.3.0:
-    resolution: {integrity: sha512-dq+qelQ9akHpcOl/gUVRTxVIOkAJ1wR3QAvb4RsVjS8oVoFjDGTc679wJYmUmknUF5HwMLOgb5O+a3KxfWapPQ==}
-    engines: {node: '>= 0.6'}
-
-  memfs@4.57.6:
-    resolution: {integrity: sha512-WQK+DGjKCnPdpSyJUXphz+COF2uEhhsxQ3VIWBSbzpbbXuch3h4FePMqXrXGdLjsTgo4JFzBFsP6AWd9pVazGw==}
-    peerDependencies:
-      tslib: '2'
-
-  merge-descriptors@1.0.3:
-    resolution: {integrity: sha512-gaNvAS7TZ897/rVaZ0nMtAyxNyi/pdbjbAwUpFQpN70GqnVfOiXpeUUMKRBmzXaSQ8DdTX4/0ms62r2K+hE6mQ==}
-
-  merge-stream@2.0.0:
-    resolution: {integrity: sha512-abv/qOcuPfk3URPfDzmZU1LKmuw8kT+0nIHvKrKgFrwifol/doWcdA4ZqsWQ8ENrFKkd67Mfpo/LovbIUsbt3w==}
-
-  merge2@1.4.1:
-    resolution: {integrity: sha512-8q7VEgMJW4J8tcfVPy8g09NcQwZdbwFEqhe/WZkoIzjn/3TGDwtOCYtXGxA3O8tPzpczCCDgv+P2P5y00ZJOOg==}
-    engines: {node: '>= 8'}
-
-  mermaid@11.15.0:
-    resolution: {integrity: sha512-pTMbcf3rWdtLiYGpmoTjHEpeY8seiy6sR+9nD7LOs8KfUbHE4lOUAprTRqRAcWSQ6MQpdX+YEsxShtGsINtPtw==}
-
-  methods@1.1.2:
-    resolution: {integrity: sha512-iclAHeNqNm68zFtnZ0e+1L2yUIdvzNoauKU4WBA3VvH/vPFieF7qfRlwUZU+DA9P9bPXIS90ulxoUoCH23sV2w==}
-    engines: {node: '>= 0.6'}
-
-  micromark-core-commonmark@1.1.0:
-    resolution: {integrity: sha512-BgHO1aRbolh2hcrzL2d1La37V0Aoz73ymF8rAcKnohLy93titmv62E0gP8Hrx9PKcKrqCZ1BbLGbP3bEhoXYlw==}
-
-  micromark-core-commonmark@2.0.3:
-    resolution: {integrity: sha512-RDBrHEMSxVFLg6xvnXmb1Ayr2WzLAWjeSATAoxwKYJV94TeNavgoIdA0a9ytzDSVzBy2YKFK+emCPOEibLeCrg==}
-
-  micromark-extension-directive@3.0.2:
-    resolution: {integrity: sha512-wjcXHgk+PPdmvR58Le9d7zQYWy+vKEU9Se44p2CrCDPiLr2FMyiT4Fyb5UFKFC66wGB3kPlgD7q3TnoqPS7SZA==}
-
-  micromark-extension-frontmatter@0.2.2:
-    resolution: {integrity: sha512-q6nPLFCMTLtfsctAuS0Xh4vaolxSFUWUWR6PZSrXXiRy+SANGllpcqdXFv2z07l0Xz/6Hl40hK0ffNCJPH2n1A==}
-
-  micromark-extension-frontmatter@2.0.0:
-    resolution: {integrity: sha512-C4AkuM3dA58cgZha7zVnuVxBhDsbttIMiytjgsM2XbHAB2faRVaHRle40558FBN+DJcrLNCoqG5mlrpdU4cRtg==}
-
-  micromark-extension-gfm-autolink-literal@0.5.7:
-    resolution: {integrity: sha512-ePiDGH0/lhcngCe8FtH4ARFoxKTUelMp4L7Gg2pujYD5CSMb9PbblnyL+AAMud/SNMyusbS2XDSiPIRcQoNFAw==}
-
-  micromark-extension-gfm-autolink-literal@2.1.0:
-    resolution: {integrity: sha512-oOg7knzhicgQ3t4QCjCWgTmfNhvQbDDnJeVu9v81r7NltNCVmhPy1fJRX27pISafdjL+SVc4d3l48Gb6pbRypw==}
-
-  micromark-extension-gfm-footnote@2.1.0:
-    resolution: {integrity: sha512-/yPhxI1ntnDNsiHtzLKYnE3vf9JZ6cAisqVDauhp4CEHxlb4uoOTxOCJ+9s51bIB8U1N1FJ1RXOKTIlD5B/gqw==}
-
-  micromark-extension-gfm-strikethrough@0.6.5:
-    resolution: {integrity: sha512-PpOKlgokpQRwUesRwWEp+fHjGGkZEejj83k9gU5iXCbDG+XBA92BqnRKYJdfqfkrRcZRgGuPuXb7DaK/DmxOhw==}
-
-  micromark-extension-gfm-strikethrough@2.1.0:
-    resolution: {integrity: sha512-ADVjpOOkjz1hhkZLlBiYA9cR2Anf8F4HqZUO6e5eDcPQd0Txw5fxLzzxnEkSkfnD0wziSGiv7sYhk/ktvbf1uw==}
-
-  micromark-extension-gfm-table@0.4.3:
-    resolution: {integrity: sha512-hVGvESPq0fk6ALWtomcwmgLvH8ZSVpcPjzi0AjPclB9FsVRgMtGZkUcpE0zgjOCFAznKepF4z3hX8z6e3HODdA==}
-
-  micromark-extension-gfm-table@2.1.1:
-    resolution: {integrity: sha512-t2OU/dXXioARrC6yWfJ4hqB7rct14e8f7m0cbI5hUmDyyIlwv5vEtooptH8INkbLzOatzKuVbQmAYcbWoyz6Dg==}
-
-  micromark-extension-gfm-tagfilter@0.3.0:
-    resolution: {integrity: sha512-9GU0xBatryXifL//FJH+tAZ6i240xQuFrSL7mYi8f4oZSbc+NvXjkrHemeYP0+L4ZUT+Ptz3b95zhUZnMtoi/Q==}
-
-  micromark-extension-gfm-tagfilter@2.0.0:
-    resolution: {integrity: sha512-xHlTOmuCSotIA8TW1mDIM6X2O1SiX5P9IuDtqGonFhEK0qgRI4yeC6vMxEV2dgyr2TiD+2PQ10o+cOhdVAcwfg==}
-
-  micromark-extension-gfm-task-list-item@0.3.3:
-    resolution: {integrity: sha512-0zvM5iSLKrc/NQl84pZSjGo66aTGd57C1idmlWmE87lkMcXrTxg1uXa/nXomxJytoje9trP0NDLvw4bZ/Z/XCQ==}
-
-  micromark-extension-gfm-task-list-item@2.1.0:
-    resolution: {integrity: sha512-qIBZhqxqI6fjLDYFTBIa4eivDMnP+OZqsNwmQ3xNLE4Cxwc+zfQEfbs6tzAo2Hjq+bh6q5F+Z8/cksrLFYWQQw==}
-
-  micromark-extension-gfm@0.3.3:
-    resolution: {integrity: sha512-oVN4zv5/tAIA+l3GbMi7lWeYpJ14oQyJ3uEim20ktYFAcfX1x3LNlFGGlmrZHt7u9YlKExmyJdDGaTt6cMSR/A==}
-
-  micromark-extension-gfm@3.0.0:
-    resolution: {integrity: sha512-vsKArQsicm7t0z2GugkCKtZehqUm31oeGBV/KVSorWSy8ZlNAv7ytjFhvaryUiCUJYqs+NoE6AFhpQvBTM6Q4w==}
-
-  micromark-extension-math@3.1.0:
-    resolution: {integrity: sha512-lvEqd+fHjATVs+2v/8kg9i5Q0AP2k85H0WUOwpIVvUML8BapsMvh1XAogmQjOCsLpoKRCVQqEkQBB3NhVBcsOg==}
-
-  micromark-extension-mdx-expression@3.0.1:
-    resolution: {integrity: sha512-dD/ADLJ1AeMvSAKBwO22zG22N4ybhe7kFIZ3LsDI0GlsNr2A3KYxb0LdC1u5rj4Nw+CHKY0RVdnHX8vj8ejm4Q==}
-
-  micromark-extension-mdx-jsx@3.0.2:
-    resolution: {integrity: sha512-e5+q1DjMh62LZAJOnDraSSbDMvGJ8x3cbjygy2qFEi7HCeUT4BDKCvMozPozcD6WmOt6sVvYDNBKhFSz3kjOVQ==}
-
-  micromark-extension-mdx-md@2.0.0:
-    resolution: {integrity: sha512-EpAiszsB3blw4Rpba7xTOUptcFeBFi+6PY8VnJ2hhimH+vCQDirWgsMpz7w1XcZE7LVrSAUGb9VJpG9ghlYvYQ==}
-
-  micromark-extension-mdxjs-esm@3.0.0:
-    resolution: {integrity: sha512-DJFl4ZqkErRpq/dAPyeWp15tGrcrrJho1hKK5uBS70BCtfrIFg81sqcTVu3Ta+KD1Tk5vAtBNElWxtAa+m8K9A==}
-
-  micromark-extension-mdxjs@3.0.0:
-    resolution: {integrity: sha512-A873fJfhnJ2siZyUrJ31l34Uqwy4xIFmvPY1oj+Ean5PHcPBYzEsvqvWGaWcfEIr11O5Dlw3p2y0tZWpKHDejQ==}
-
-  micromark-factory-destination@1.1.0:
-    resolution: {integrity: sha512-XaNDROBgx9SgSChd69pjiGKbV+nfHGDPVYFs5dOoDd7ZnMAE+Cuu91BCpsY8RT2NP9vo/B8pds2VQNCLiu0zhg==}
-
-  micromark-factory-destination@2.0.1:
-    resolution: {integrity: sha512-Xe6rDdJlkmbFRExpTOmRj9N3MaWmbAgdpSrBQvCFqhezUn4AHqJHbaEnfbVYYiexVSs//tqOdY/DxhjdCiJnIA==}
-
-  micromark-factory-label@1.1.0:
-    resolution: {integrity: sha512-OLtyez4vZo/1NjxGhcpDSbHQ+m0IIGnT8BoPamh+7jVlzLJBH98zzuCoUeMxvM6WsNeh8wx8cKvqLiPHEACn0w==}
-
-  micromark-factory-label@2.0.1:
-    resolution: {integrity: sha512-VFMekyQExqIW7xIChcXn4ok29YE3rnuyveW3wZQWWqF4Nv9Wk5rgJ99KzPvHjkmPXF93FXIbBp6YdW3t71/7Vg==}
-
-  micromark-factory-mdx-expression@2.0.3:
-    resolution: {integrity: sha512-kQnEtA3vzucU2BkrIa8/VaSAsP+EJ3CKOvhMuJgOEGg9KDC6OAY6nSnNDVRiVNRqj7Y4SlSzcStaH/5jge8JdQ==}
-
-  micromark-factory-space@1.1.0:
-    resolution: {integrity: sha512-cRzEj7c0OL4Mw2v6nwzttyOZe8XY/Z8G0rzmWQZTBi/jjwyw/U4uqKtUORXQrR5bAZZnbTI/feRV/R7hc4jQYQ==}
-
-  micromark-factory-space@2.0.1:
-    resolution: {integrity: sha512-zRkxjtBxxLd2Sc0d+fbnEunsTj46SWXgXciZmHq0kDYGnck/ZSGj9/wULTV95uoeYiK5hRXP2mJ98Uo4cq/LQg==}
-
-  micromark-factory-title@1.1.0:
-    resolution: {integrity: sha512-J7n9R3vMmgjDOCY8NPw55jiyaQnH5kBdV2/UXCtZIpnHH3P6nHUKaH7XXEYuWwx/xUJcawa8plLBEjMPU24HzQ==}
-
-  micromark-factory-title@2.0.1:
-    resolution: {integrity: sha512-5bZ+3CjhAd9eChYTHsjy6TGxpOFSKgKKJPJxr293jTbfry2KDoWkhBb6TcPVB4NmzaPhMs1Frm9AZH7OD4Cjzw==}
-
-  micromark-factory-whitespace@1.1.0:
-    resolution: {integrity: sha512-v2WlmiymVSp5oMg+1Q0N1Lxmt6pMhIHD457whWM7/GUlEks1hI9xj5w3zbc4uuMKXGisksZk8DzP2UyGbGqNsQ==}
-
-  micromark-factory-whitespace@2.0.1:
-    resolution: {integrity: sha512-Ob0nuZ3PKt/n0hORHyvoD9uZhr+Za8sFoP+OnMcnWK5lngSzALgQYKMr9RJVOWLqQYuyn6ulqGWSXdwf6F80lQ==}
-
-  micromark-util-character@1.2.0:
-    resolution: {integrity: sha512-lXraTwcX3yH/vMDaFWCQJP1uIszLVebzUa3ZHdrgxr7KEU/9mL4mVgCpGbyhvNLNlauROiNUq7WN5u7ndbY6xg==}
-
-  micromark-util-character@2.1.1:
-    resolution: {integrity: sha512-wv8tdUTJ3thSFFFJKtpYKOYiGP2+v96Hvk4Tu8KpCAsTMs6yi+nVmGh1syvSCsaxz45J6Jbw+9DD6g97+NV67Q==}
-
-  micromark-util-chunked@1.1.0:
-    resolution: {integrity: sha512-Ye01HXpkZPNcV6FiyoW2fGZDUw4Yc7vT0E9Sad83+bEDiCJ1uXu0S3mr8WLpsz3HaG3x2q0HM6CTuPdcZcluFQ==}
-
-  micromark-util-chunked@2.0.1:
-    resolution: {integrity: sha512-QUNFEOPELfmvv+4xiNg2sRYeS/P84pTW0TCgP5zc9FpXetHY0ab7SxKyAQCNCc1eK0459uoLI1y5oO5Vc1dbhA==}
-
-  micromark-util-classify-character@1.1.0:
-    resolution: {integrity: sha512-SL0wLxtKSnklKSUplok1WQFoGhUdWYKggKUiqhX+Swala+BtptGCu5iPRc+xvzJ4PXE/hwM3FNXsfEVgoZsWbw==}
-
-  micromark-util-classify-character@2.0.1:
-    resolution: {integrity: sha512-K0kHzM6afW/MbeWYWLjoHQv1sgg2Q9EccHEDzSkxiP/EaagNzCm7T/WMKZ3rjMbvIpvBiZgwR3dKMygtA4mG1Q==}
-
-  micromark-util-combine-extensions@1.1.0:
-    resolution: {integrity: sha512-Q20sp4mfNf9yEqDL50WwuWZHUrCO4fEyeDCnMGmG5Pr0Cz15Uo7KBs6jq+dq0EgX4DPwwrh9m0X+zPV1ypFvUA==}
-
-  micromark-util-combine-extensions@2.0.1:
-    resolution: {integrity: sha512-OnAnH8Ujmy59JcyZw8JSbK9cGpdVY44NKgSM7E9Eh7DiLS2E9RNQf0dONaGDzEG9yjEl5hcqeIsj4hfRkLH/Bg==}
-
-  micromark-util-decode-numeric-character-reference@1.1.0:
-    resolution: {integrity: sha512-m9V0ExGv0jB1OT21mrWcuf4QhP46pH1KkfWy9ZEezqHKAxkj4mPCy3nIH1rkbdMlChLHX531eOrymlwyZIf2iw==}
-
-  micromark-util-decode-numeric-character-reference@2.0.2:
-    resolution: {integrity: sha512-ccUbYk6CwVdkmCQMyr64dXz42EfHGkPQlBj5p7YVGzq8I7CtjXZJrubAYezf7Rp+bjPseiROqe7G6foFd+lEuw==}
-
-  micromark-util-decode-string@1.1.0:
-    resolution: {integrity: sha512-YphLGCK8gM1tG1bd54azwyrQRjCFcmgj2S2GoJDNnh4vYtnL38JS8M4gpxzOPNyHdNEpheyWXCTnnTDY3N+NVQ==}
-
-  micromark-util-decode-string@2.0.1:
-    resolution: {integrity: sha512-nDV/77Fj6eH1ynwscYTOsbK7rR//Uj0bZXBwJZRfaLEJ1iGBR6kIfNmlNqaqJf649EP0F3NWNdeJi03elllNUQ==}
-
-  micromark-util-encode@1.1.0:
-    resolution: {integrity: sha512-EuEzTWSTAj9PA5GOAs992GzNh2dGQO52UvAbtSOMvXTxv3Criqb6IOzJUBCmEqrrXSblJIJBbFFv6zPxpreiJw==}
-
-  micromark-util-encode@2.0.1:
-    resolution: {integrity: sha512-c3cVx2y4KqUnwopcO9b/SCdo2O67LwJJ/UyqGfbigahfegL9myoEFoDYZgkT7f36T0bLrM9hZTAaAyH+PCAXjw==}
-
-  micromark-util-events-to-acorn@2.0.3:
-    resolution: {integrity: sha512-jmsiEIiZ1n7X1Rr5k8wVExBQCg5jy4UXVADItHmNk1zkwEVhBuIUKRu3fqv+hs4nxLISi2DQGlqIOGiFxgbfHg==}
-
-  micromark-util-html-tag-name@1.2.0:
-    resolution: {integrity: sha512-VTQzcuQgFUD7yYztuQFKXT49KghjtETQ+Wv/zUjGSGBioZnkA4P1XXZPT1FHeJA6RwRXSF47yvJ1tsJdoxwO+Q==}
-
-  micromark-util-html-tag-name@2.0.1:
-    resolution: {integrity: sha512-2cNEiYDhCWKI+Gs9T0Tiysk136SnR13hhO8yW6BGNyhOC4qYFnwF1nKfD3HFAIXA5c45RrIG1ub11GiXeYd1xA==}
-
-  micromark-util-normalize-identifier@1.1.0:
-    resolution: {integrity: sha512-N+w5vhqrBihhjdpM8+5Xsxy71QWqGn7HYNUvch71iV2PM7+E3uWGox1Qp90loa1ephtCxG2ftRV/Conitc6P2Q==}
-
-  micromark-util-normalize-identifier@2.0.1:
-    resolution: {integrity: sha512-sxPqmo70LyARJs0w2UclACPUUEqltCkJ6PhKdMIDuJ3gSf/Q+/GIe3WKl0Ijb/GyH9lOpUkRAO2wp0GVkLvS9Q==}
-
-  micromark-util-resolve-all@1.1.0:
-    resolution: {integrity: sha512-b/G6BTMSg+bX+xVCshPTPyAu2tmA0E4X98NSR7eIbeC6ycCqCeE7wjfDIgzEbkzdEVJXRtOG4FbEm/uGbCRouA==}
-
-  micromark-util-resolve-all@2.0.1:
-    resolution: {integrity: sha512-VdQyxFWFT2/FGJgwQnJYbe1jjQoNTS4RjglmSjTUlpUMa95Htx9NHeYW4rGDJzbjvCsl9eLjMQwGeElsqmzcHg==}
-
-  micromark-util-sanitize-uri@1.2.0:
-    resolution: {integrity: sha512-QO4GXv0XZfWey4pYFndLUKEAktKkG5kZTdUNaTAkzbuJxn2tNBOr+QtxR2XpWaMhbImT2dPzyLrPXLlPhph34A==}
-
-  micromark-util-sanitize-uri@2.0.1:
-    resolution: {integrity: sha512-9N9IomZ/YuGGZZmQec1MbgxtlgougxTodVwDzzEouPKo3qFWvymFHWcnDi2vzV1ff6kas9ucW+o3yzJK9YB1AQ==}
-
-  micromark-util-subtokenize@1.1.0:
-    resolution: {integrity: sha512-kUQHyzRoxvZO2PuLzMt2P/dwVsTiivCK8icYTeR+3WgbuPqfHgPPy7nFKbeqRivBvn/3N3GBiNC+JRTMSxEC7A==}
-
-  micromark-util-subtokenize@2.1.0:
-    resolution: {integrity: sha512-XQLu552iSctvnEcgXw6+Sx75GflAPNED1qx7eBJ+wydBb2KCbRZe+NwvIEEMM83uml1+2WSXpBAcp9IUCgCYWA==}
-
-  micromark-util-symbol@1.1.0:
-    resolution: {integrity: sha512-uEjpEYY6KMs1g7QfJ2eX1SQEV+ZT4rUD3UcF6l57acZvLNK7PBZL+ty82Z1qhK1/yXIY4bdx04FKMgR0g4IAag==}
-
-  micromark-util-symbol@2.0.1:
-    resolution: {integrity: sha512-vs5t8Apaud9N28kgCrRUdEed4UJ+wWNvicHLPxCa9ENlYuAY31M0ETy5y1vA33YoNPDFTghEbnh6efaE8h4x0Q==}
-
-  micromark-util-types@1.1.0:
-    resolution: {integrity: sha512-ukRBgie8TIAcacscVHSiddHjO4k/q3pnedmzMQ4iwDcK0FtFCohKOlFbaOL/mPgfnPsL3C1ZyxJa4sbWrBl3jg==}
-
-  micromark-util-types@2.0.2:
-    resolution: {integrity: sha512-Yw0ECSpJoViF1qTU4DC6NwtC4aWGt1EkzaQB8KPPyCRR8z9TWeV0HbEFGTO+ZY1wB22zmxnJqhPyTpOVCpeHTA==}
-
-  micromark@2.11.4:
-    resolution: {integrity: sha512-+WoovN/ppKolQOFIAajxi7Lu9kInbPxFuTBVEavFcL8eAfVstoc5MocPmqBeAdBOJV00uaVjegzH4+MA0DN/uA==}
-
-  micromark@3.2.0:
-    resolution: {integrity: sha512-uD66tJj54JLYq0De10AhWycZWGQNUvDI55xPgk2sQM5kn1JYlhbCMTtEeT27+vAhW2FBQxLlOmS3pmA7/2z4aA==}
-
-  micromark@4.0.2:
-    resolution: {integrity: sha512-zpe98Q6kvavpCr1NPVSCMebCKfD7CA2NqZ+rykeNhONIJBpc1tFKt9hucLGwha3jNTNI8lHpctWJWoimVF4PfA==}
-
-  micromatch@4.0.8:
-    resolution: {integrity: sha512-PXwfBhYu0hBCPw8Dn0E+WDYb7af3dSLVWKi3HGv84IdF4TyFoC0ysxFd0Goxw7nSv4T/PzEJQxsYsEiFCKo2BA==}
-    engines: {node: '>=8.6'}
-
-  mime-db@1.33.0:
-    resolution: {integrity: sha512-BHJ/EKruNIqJf/QahvxwQZXKygOQ256myeN/Ew+THcAa5q+PjyTTMMeNQC4DZw5AwfvelsUrA6B67NKMqXDbzQ==}
-    engines: {node: '>= 0.6'}
-
-  mime-db@1.52.0:
-    resolution: {integrity: sha512-sPU4uV7dYlvtWJxwwxHD0PuihVNiE7TyAbQ5SWxDCB9mUYvOgroQOwYQQOKPJ8CIbE+1ETVlOoK1UC2nU3gYvg==}
-    engines: {node: '>= 0.6'}
-
-  mime-db@1.54.0:
-    resolution: {integrity: sha512-aU5EJuIN2WDemCcAp2vFBfp/m4EAhWJnUNSSw0ixs7/kXbd6Pg64EmwJkNdFhB8aWt1sH2CTXrLxo/iAGV3oPQ==}
-    engines: {node: '>= 0.6'}
-
-  mime-format@2.0.2:
-    resolution: {integrity: sha512-Y5ERWVcyh3sby9Fx2U5F1yatiTFjNsqF5NltihTWI9QgNtr5o3dbCZdcKa1l2wyfhnwwoP9HGNxga7LqZLA6gw==}
-
-  mime-types@2.1.18:
-    resolution: {integrity: sha512-lc/aahn+t4/SWV/qcmumYjymLsWfN3ELhpmVuUFjgsORruuZPVSwAQryq+HHGvO/SI2KVX26bx+En+zhM8g8hQ==}
-    engines: {node: '>= 0.6'}
-
-  mime-types@2.1.35:
-    resolution: {integrity: sha512-ZDY+bPm5zTTF+YpCrAU9nK0UgICYPT0QtT1NZWFv4s++TNkcgVaT0g6+4R2uI4MjQjzysHB1zxuWL50hzaeXiw==}
-    engines: {node: '>= 0.6'}
-
-  mime-types@3.0.2:
-    resolution: {integrity: sha512-Lbgzdk0h4juoQ9fCKXW4by0UJqj+nOOrI9MJ1sSj4nI8aI2eo1qmvQEie4VD1glsS250n15LsWsYtCugiStS5A==}
-    engines: {node: '>=18'}
-
-  mime@1.6.0:
-    resolution: {integrity: sha512-x0Vn8spI+wuJ1O6S7gnbaQg8Pxh4NNHb7KSINmEWKiPE4RKOplvijn+NkmYmmRgP68mc70j2EbeTFRsrswaQeg==}
-    engines: {node: '>=4'}
-    hasBin: true
-
-  mime@3.0.0:
-    resolution: {integrity: sha512-jSCU7/VB1loIWBZe14aEYHU/+1UMEHoaO7qxCOVJOw9GgH72VAWppxNcjU+x9a2k3GSIBXNKxXQFqRvvZ7vr3A==}
-    engines: {node: '>=10.0.0'}
-    hasBin: true
-
-  mimic-fn@2.1.0:
-    resolution: {integrity: sha512-OqbOk5oEQeAZ8WXWydlu9HJjz9WVdEIvamMCcXmuqUYjTknH/sqsWvhQ3vgwKFRR1HpjvNBKQ37nbJgYzGqGcg==}
-    engines: {node: '>=6'}
-
-  mimic-response@3.1.0:
-    resolution: {integrity: sha512-z0yWI+4FDrrweS8Zmt4Ej5HdJmky15+L2e6Wgn3+iK5fWzb6T3fhNFq2+MeTRb064c6Wr4N/wv0DzQTjNzHNGQ==}
-    engines: {node: '>=10'}
-
-  mimic-response@4.0.0:
-    resolution: {integrity: sha512-e5ISH9xMYU0DzrT+jl8q2ze9D6eWBto+I8CNpe+VI+K2J/F/k3PdkdTdz4wvGVH4NTpo+NRYTVIuMQEMMcsLqg==}
-    engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
-
-  mini-css-extract-plugin@2.10.2:
-    resolution: {integrity: sha512-AOSS0IdEB95ayVkxn5oGzNQwqAi2J0Jb/kKm43t7H73s8+f5873g0yuj0PNvK4dO75mu5DHg4nlgp4k6Kga8eg==}
-    engines: {node: '>= 12.13.0'}
-    peerDependencies:
-      webpack: ^5.0.0
-
-  minimalistic-assert@1.0.1:
-    resolution: {integrity: sha512-UtJcAD4yEaGtjPezWuO9wC4nwUnVH/8/Im3yEHQP4b67cXlD/Qr9hdITCU1xDbSEXg2XKNaP8jsReV7vQd00/A==}
-
-  minimatch@10.2.5:
-    resolution: {integrity: sha512-MULkVLfKGYDFYejP07QOurDLLQpcjk7Fw+7jXS2R2czRQzR56yHRveU5NDJEOviH+hETZKSkIk5c+T23GjFUMg==}
-    engines: {node: 18 || 20 || >=22}
-
-  minimatch@3.1.5:
-    resolution: {integrity: sha512-VgjWUsnnT6n+NUk6eZq77zeFdpW2LWDzP6zFGrCbHXiYNul5Dzqk2HHQ5uFH2DNW5Xbp8+jVzaeNt94ssEEl4w==}
-
-  minimatch@9.0.9:
-    resolution: {integrity: sha512-OBwBN9AL4dqmETlpS2zasx+vTeWclWzkblfZk7KTA5j3jeOONz/tRCnZomUyvNg83wL5Zv9Ss6HMJXAgL8R2Yg==}
-    engines: {node: '>=16 || 14 >=14.17'}
-
-  minimist@1.2.8:
-    resolution: {integrity: sha512-2yyAR8qBkN3YuheJanUpWC5U3bb5osDywNB8RzDVlDwDHbocAJveqqj1u8+SVD7jkWT4yvsHCpWqqWqAxb0zCA==}
-
-  minipass@7.1.3:
-    resolution: {integrity: sha512-tEBHqDnIoM/1rXME1zgka9g6Q2lcoCkxHLuc7ODJ5BxbP5d4c2Z5cGgtXAku59200Cx7diuHTOYfSBD8n6mm8A==}
-    engines: {node: '>=16 || 14 >=14.17'}
-
-  mri@1.2.0:
-    resolution: {integrity: sha512-tzzskb3bG8LvYGFF/mDTpq3jpI6Q9wc3LEmBaghu+DdCssd1FakN7Bc0hVNmEyGq1bq3RgfkCb3cmQLpNPOroA==}
-    engines: {node: '>=4'}
-
-  mrmime@2.0.1:
-    resolution: {integrity: sha512-Y3wQdFg2Va6etvQ5I82yUhGdsKrcYox6p7FfL1LbK2J4V01F9TGlepTIhnK24t7koZibmg82KGglhA1XK5IsLQ==}
-    engines: {node: '>=10'}
-
-  ms@2.0.0:
-    resolution: {integrity: sha512-Tpp60P6IUJDTuOq/5Z8cdskzJujfwqfOTkrwIwj7IRISpnkJnT6SyJ4PCPnGMoFjC9ddhal5KVIYtAt97ix05A==}
-
-  ms@2.1.3:
-    resolution: {integrity: sha512-6FlzubTLZG3J2a/NVCAleEhjzq5oxgHyaCU9yYXvcLsvoVaHJq/s5xXI6/XXP6tz7R9xAOtHnSO/tXtF3WRTlA==}
-
-  multicast-dns@7.2.5:
-    resolution: {integrity: sha512-2eznPJP8z2BFLX50tf0LuODrpINqP1RVIm/CObbTcBRITQgmC/TjcREF1NeTBzIcR5XO/ukWo+YHOjBbFwIupg==}
-    hasBin: true
-
-  mustache@4.2.0:
-    resolution: {integrity: sha512-71ippSywq5Yb7/tVYyGbkBggbU8H3u5Rz56fH60jGFgr8uHwxs+aSKeqmluIVzM0m0kB7xQjKS6qPfd0b2ZoqQ==}
-    hasBin: true
-
-  mz@2.7.0:
-    resolution: {integrity: sha512-z81GNO7nnYMEhrGh9LeymoE4+Yr0Wn5McHIZMK5cfQCl+NDX08sCZgUc9/6MHni9IWuFLm1Z3HTCXu2z9fN62Q==}
-
-  nano-css@5.6.2:
-    resolution: {integrity: sha512-+6bHaC8dSDGALM1HJjOHVXpuastdu2xFoZlC77Jh4cg+33Zcgm+Gxd+1xsnpZK14eyHObSp82+ll5y3SX75liw==}
-    peerDependencies:
-      react: '*'
-      react-dom: '*'
-
-  nano-memoize@1.3.1:
-    resolution: {integrity: sha512-wQiW3xHptgGlec/Zbo7oq6Zz4kKoK8TaIIs1irTO9iJOGTIG3lnQRUJfH73bJ/rn7MOE4sTdSU+ALPGEidaijQ==}
-
-  nanoid@3.3.12:
-    resolution: {integrity: sha512-ZB9RH/39qpq5Vu6Y+NmUaFhQR6pp+M2Xt76XBnEwDaGcVAqhlvxrl3B2bKS5D3NH3QR76v3aSrKaF/Kiy7lEtQ==}
-    engines: {node: ^10 || ^12 || ^13.7 || ^14 || >=15.0.1}
-    hasBin: true
-
-  natural-compare@1.4.0:
-    resolution: {integrity: sha512-OWND8ei3VtNC9h7V60qff3SVobHr996CTwgxubgyQYEpg290h9J0buyECNNJexkFm5sOajh5G116RYA1c8ZMSw==}
-
-  negotiator@0.6.3:
-    resolution: {integrity: sha512-+EUsqGPLsM+j/zdChZjsnX51g4XrHFOIXwfnCVPGlQk/k5giakcKsuxCObBRu6DSm9opw/O6slWbJdghQM4bBg==}
-    engines: {node: '>= 0.6'}
-
-  negotiator@0.6.4:
-    resolution: {integrity: sha512-myRT3DiWPHqho5PrJaIRyaMv2kgYf0mUVgBNOYMuCH5Ki1yEiQaf/ZJuQ62nvpc44wL5WDbTX7yGJi1Neevw8w==}
-    engines: {node: '>= 0.6'}
-
-  neo-async@2.6.2:
-    resolution: {integrity: sha512-Yd3UES5mWCSqR+qNT93S3UoYUkqAZ9lLg8a7g9rimsWmYGK8cVToA4/sF3RrshdyV3sAGMXVUmpMYOw+dLpOuw==}
-
-  neotraverse@0.6.15:
-    resolution: {integrity: sha512-HZpdkco+JeXq0G+WWpMJ4NsX3pqb5O7eR9uGz3FfoFt+LYzU8iRWp49nJtud6hsDoywM8tIrDo3gjgmOqJA8LA==}
-    engines: {node: '>= 10'}
-
-  no-case@3.0.4:
-    resolution: {integrity: sha512-fgAN3jGAh+RoxUGZHTSOLJIqUc2wmoBwGR4tbpNAKmmovFoWq0OdRkb0VkldReO2a2iBT/OEulG9XSUc10r3zg==}
-
-  node-addon-api@7.1.1:
-    resolution: {integrity: sha512-5m3bsyrjFWE1xf7nz7YXdN4udnVtXK6/Yfgn5qnahL6bCkf2yKt4k3nuTKAtT4r3IG8JNR2ncsIMdZuAzJjHQQ==}
-
-  node-emoji@2.2.0:
-    resolution: {integrity: sha512-Z3lTE9pLaJF47NyMhd4ww1yFTAP8YhYI8SleJiHzM46Fgpm5cnNzSl9XfzFNqbaz+VlJrIj3fXQ4DeN1Rjm6cw==}
-    engines: {node: '>=18'}
-
-  node-fetch-h2@2.3.0:
-    resolution: {integrity: sha512-ofRW94Ab0T4AOh5Fk8t0h8OBWrmjb0SSB20xh1H8YnPV9EJ+f5AMoYSUQ2zgJ4Iq2HAK0I2l5/Nequ8YzFS3Hg==}
-    engines: {node: 4.x || >=6.0.0}
-
-  node-fetch@2.7.0:
-    resolution: {integrity: sha512-c4FRfUm/dbcWZ7U+1Wq0AwCyFL+3nt2bEw05wfxSz+DWpWsitgmSgYmy2dQdWyKC1694ELPqMs/YzUSNozLt8A==}
-    engines: {node: 4.x || >=6.0.0}
-    peerDependencies:
-      encoding: ^0.1.0
-    peerDependenciesMeta:
-      encoding:
-        optional: true
-
-  node-readfiles@0.2.0:
-    resolution: {integrity: sha512-SU00ZarexNlE4Rjdm83vglt5Y9yiQ+XI1XpflWlb7q7UTN1JUItm69xMeiQCTxtTfnzt+83T8Cx+vI2ED++VDA==}
-
-  node-releases@2.0.47:
-    resolution: {integrity: sha512-Uzmd6LXpouKo8EUK68IjH4+E01w/hXyV3R3g/geCJo+rXLNfh1xucB+LOzYEOQPSiUK3h/xZf0cQGcSsmyL2Og==}
-    engines: {node: '>=18'}
-
-  normalize-path@3.0.0:
-    resolution: {integrity: sha512-6eZs5Ls3WtCisHWp9S2GUy8dqkpGi4BVSz3GaqiE6ezub0512ESztXUwUB6C6IKbQkY2Pnb/mD4WYojCRwcwLA==}
-    engines: {node: '>=0.10.0'}
-
-  normalize-url@8.1.1:
-    resolution: {integrity: sha512-JYc0DPlpGWB40kH5g07gGTrYuMqV653k3uBKY6uITPWds3M0ov3GaWGp9lbE3Bzngx8+XkfzgvASb9vk9JDFXQ==}
-    engines: {node: '>=14.16'}
-
-  npm-run-path@4.0.1:
-    resolution: {integrity: sha512-S48WzZW777zhNIrn7gxOlISNAqi9ZC/uQFnRdbeIHhZhCA6UqpkOT8T1G7BvfdgP4Er8gF4sUbaS0i7QvIfCWw==}
-    engines: {node: '>=8'}
-
-  npm-to-yarn@3.0.1:
-    resolution: {integrity: sha512-tt6PvKu4WyzPwWUzy/hvPFqn+uwXO0K1ZHka8az3NnrhWJDmSqI8ncWq0fkL0k/lmmi5tAC11FXwXuh0rFbt1A==}
-    engines: {node: ^12.22.0 || ^14.17.0 || >=16.0.0}
-
-  nprogress@0.2.0:
-    resolution: {integrity: sha512-I19aIingLgR1fmhftnbWWO3dXc0hSxqHQHQb3H8m+K3TnEn/iSeTZZOyvKXWqQESMwuUVnatlCnZdLBZZt2VSA==}
-
-  nth-check@2.1.1:
-    resolution: {integrity: sha512-lqjrjmaOoAnWfMmBPL+XNnynZh2+swxiX3WUE0s4yEHI6m+AwrK2UZOimIRl3X/4QctVqS8AiZjFqyOGrMXb/w==}
-
-  null-loader@4.0.1:
-    resolution: {integrity: sha512-pxqVbi4U6N26lq+LmgIbB5XATP0VdZKOG25DhHi8btMmJJefGArFyDg1yc4U3hWCJbMqSrw0qyrz1UQX+qYXqg==}
-    engines: {node: '>= 10.13.0'}
-    peerDependencies:
-      webpack: ^4.0.0 || ^5.0.0
-
-  oas-kit-common@1.0.8:
-    resolution: {integrity: sha512-pJTS2+T0oGIwgjGpw7sIRU8RQMcUoKCDWFLdBqKB2BNmGpbBMH2sdqAaOXUg8OzonZHU0L7vfJu1mJFEiYDWOQ==}
-
-  oas-linter@3.2.2:
-    resolution: {integrity: sha512-KEGjPDVoU5K6swgo9hJVA/qYGlwfbFx+Kg2QB/kd7rzV5N8N5Mg6PlsoCMohVnQmo+pzJap/F610qTodKzecGQ==}
-
-  oas-resolver-browser@2.5.6:
-    resolution: {integrity: sha512-Jw5elT/kwUJrnGaVuRWe1D7hmnYWB8rfDDjBnpQ+RYY/dzAewGXeTexXzt4fGEo6PUE4eqKqPWF79MZxxvMppA==}
-    hasBin: true
-
-  oas-resolver@2.5.6:
-    resolution: {integrity: sha512-Yx5PWQNZomfEhPPOphFbZKi9W93CocQj18NlD2Pa4GWZzdZpSJvYwoiuurRI7m3SpcChrnO08hkuQDL3FGsVFQ==}
-    hasBin: true
-
-  oas-schema-walker@1.1.5:
-    resolution: {integrity: sha512-2yucenq1a9YPmeNExoUa9Qwrt9RFkjqaMAA1X+U7sbb0AqBeTIdMHky9SQQ6iN94bO5NW0W4TRYXerG+BdAvAQ==}
-
-  oas-validator@5.0.8:
-    resolution: {integrity: sha512-cu20/HE5N5HKqVygs3dt94eYJfBi0TsZvPVXDhbXQHiEityDN+RROTleefoKRKKJ9dFAF2JBkDHgvWj0sjKGmw==}
-
-  object-assign@4.1.1:
-    resolution: {integrity: sha512-rJgTQnkUnH1sFw8yT6VSU3zD3sWmu6sZhIseY8VX+GRu3P6F7Fu+JNDoXfklElbLJSnc3FUQHVe4cU5hj+BcUg==}
-    engines: {node: '>=0.10.0'}
-
-  object-hash@3.0.0:
-    resolution: {integrity: sha512-RSn9F68PjH9HqtltsSnqYC1XXoWe9Bju5+213R98cNGttag9q9yAOTzdbsqvIa7aNm5WffBZFpWYr2aWrklWAw==}
-    engines: {node: '>= 6'}
-
-  object-inspect@1.13.4:
-    resolution: {integrity: sha512-W67iLl4J2EXEGTbfeHCffrjDfitvLANg0UlX3wFUUSTx92KXRFegMHUVgSqE+wvhAbi4WqjGg9czysTV2Epbew==}
-    engines: {node: '>= 0.4'}
-
-  object-keys@1.1.1:
-    resolution: {integrity: sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==}
-    engines: {node: '>= 0.4'}
-
-  object.assign@4.1.7:
-    resolution: {integrity: sha512-nK28WOo+QIjBkDduTINE4JkF/UJJKyf2EJxvJKfblDpyg0Q+pkOHNTL0Qwy6NP6FhE/EnzV73BxxqcJaXY9anw==}
-    engines: {node: '>= 0.4'}
-
-  obuf@1.1.2:
-    resolution: {integrity: sha512-PX1wu0AmAdPqOL1mWhqmlOd8kOIZQwGZw6rh7uby9fTc5lhaOWFLX3I6R1hrF9k3zUY40e6igsLGkDXK92LJNg==}
-
-  on-finished@2.4.1:
-    resolution: {integrity: sha512-oVlzkg3ENAhCk2zdv7IJwd/QUD4z2RxRwpkcGY8psCVcCYZNq4wYnVWALHM+brtuJjePWiYF/ClmuDr8Ch5+kg==}
-    engines: {node: '>= 0.8'}
-
-  on-headers@1.1.0:
-    resolution: {integrity: sha512-737ZY3yNnXy37FHkQxPzt4UZ2UWPWiCZWLvFZ4fu5cueciegX0zGPnrlY6bwRg4FdQOe9YU8MkmJwGhoMybl8A==}
-    engines: {node: '>= 0.8'}
-
-  once@1.4.0:
-    resolution: {integrity: sha512-lNaJgI+2Q5URQBkccEKHTQOPaXdUxnZZElQTZY0MFUAuaEqe1E+Nyvgdz/aIyNi6Z9MzO5dv1H8n58/GELp3+w==}
-
-  onetime@5.1.2:
-    resolution: {integrity: sha512-kbpaSSGJTWdAY5KPVeMOKXSrPtr8C8C7wodJbcsd51jRnmD+GZu8Y0VoU6Dm5Z4vWr0Ig/1NKuWRKf7j5aaYSg==}
-    engines: {node: '>=6'}
-
-  open@10.2.0:
-    resolution: {integrity: sha512-YgBpdJHPyQ2UE5x+hlSXcnejzAvD0b22U2OuAP+8OnlJT+PjWPxtgmGqKKc+RgTM63U9gN0YzrYc71R2WT/hTA==}
-    engines: {node: '>=18'}
-
-  open@8.4.2:
-    resolution: {integrity: sha512-7x81NCL719oNbsq/3mh+hVrAWmFuEYUqrq/Iw3kUzH8ReypT9QQ0BLoJS7/G9k6N81XjW4qHWtjWwe/9eLy1EQ==}
-    engines: {node: '>=12'}
-
-  openapi-to-postmanv2@6.2.0:
-    resolution: {integrity: sha512-kKGHW5df7Fti9/tpFDNr9oX1ZGLJySuZane7YuehP/gzyVpp/q9tq86g4dRko+PyA7VBkyFN1prXcDoaWOiFNw==}
-    engines: {node: '>=18'}
-    hasBin: true
-
-  openapi-types@12.1.3:
-    resolution: {integrity: sha512-N4YtSYJqghVu4iek2ZUvcN/0aqH1kRDuNqzcycDxhOUpg7GdvLa2F3DgS6yBNhInhv2r/6I0Flkn7CqL8+nIcw==}
-
-  opener@1.5.2:
-    resolution: {integrity: sha512-ur5UIdyw5Y7yEj9wLzhqXiy6GZ3Mwx0yGI+5sMn2r0N0v3cKJvUmFH5yPP+WXh9e0xfyzyJX95D8l088DNFj7A==}
-    hasBin: true
-
-  optionator@0.9.4:
-    resolution: {integrity: sha512-6IpQ7mKUxRcZNLIObR0hz7lxsapSSIYNZJwXPGeF0mTVqGKFIXj1DQcMoT22S3ROcLyY/rz0PWaWZ9ayWmad9g==}
-    engines: {node: '>= 0.8.0'}
-
-  p-cancelable@3.0.0:
-    resolution: {integrity: sha512-mlVgR3PGuzlo0MmTdk4cXqXWlwQDLnONTAg6sm62XkMJEiRxN3GL3SffkYvqwonbkJBcrI7Uvv5Zh9yjvn2iUw==}
-    engines: {node: '>=12.20'}
-
-  p-finally@1.0.0:
-    resolution: {integrity: sha512-LICb2p9CB7FS+0eR1oqWnHhp0FljGLZCWBE9aix0Uye9W8LTQPwMTYVGWQWIw9RdQiDg4+epXQODwIYJtSJaow==}
-    engines: {node: '>=4'}
-
-  p-limit@3.1.0:
-    resolution: {integrity: sha512-TYOanM3wGwNGsZN2cVTYPArw454xnXj5qmWF1bEoAc4+cU/ol7GVh7odevjp1FNHduHc3KZMcFduxU5Xc6uJRQ==}
-    engines: {node: '>=10'}
-
-  p-limit@4.0.0:
-    resolution: {integrity: sha512-5b0R4txpzjPWVw/cXXUResoD4hb6U/x9BH08L7nw+GN1sezDzPdxeRvpc9c433fZhBan/wusjbCsqwqm4EIBIQ==}
-    engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
-
-  p-locate@5.0.0:
-    resolution: {integrity: sha512-LaNjtRWUBY++zB5nE/NwcaoMylSPk+S+ZHNB1TzdbMJMny6dynpAGt7X/tl/QYq3TIeE6nxHppbo2LGymrG5Pw==}
-    engines: {node: '>=10'}
-
-  p-locate@6.0.0:
-    resolution: {integrity: sha512-wPrq66Llhl7/4AGC6I+cqxT07LhXvWL08LNXz1fENOw0Ap4sRZZ/gZpTTJ5jpurzzzfS2W/Ge9BY3LgLjCShcw==}
-    engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
-
-  p-map@4.0.0:
-    resolution: {integrity: sha512-/bjOqmgETBYB5BoEeGVea8dmvHb2m9GLy1E9W43yeyfP6QQCZGFNa+XRceJEuDB6zqr+gKpIAmlLebMpykw/MQ==}
-    engines: {node: '>=10'}
-
-  p-queue@6.6.2:
-    resolution: {integrity: sha512-RwFpb72c/BhQLEXIZ5K2e+AhgNVmIejGlTgiB9MzZ0e93GRvqZ7uSi0dvRF7/XIXDeNkra2fNHBxTyPDGySpjQ==}
-    engines: {node: '>=8'}
-
-  p-retry@6.2.1:
-    resolution: {integrity: sha512-hEt02O4hUct5wtwg4H4KcWgDdm+l1bOaEy/hWzd8xtXB9BqxTWBBhb+2ImAtH4Cv4rPjV76xN3Zumqk3k3AhhQ==}
-    engines: {node: '>=16.17'}
-
-  p-timeout@3.2.0:
-    resolution: {integrity: sha512-rhIwUycgwwKcP9yTOOFK/AKsAopjjCakVqLHePO3CC6Mir1Z99xT+R63jZxAT5lFZLa2inS5h+ZS2GvR99/FBg==}
-    engines: {node: '>=8'}
-
-  package-json@8.1.1:
-    resolution: {integrity: sha512-cbH9IAIJHNj9uXi196JVsRlt7cHKak6u/e6AkL/bkRelZ7rlL3X1YKxsZwa36xipOEKAsdtmaG6aAJoM1fx2zA==}
-    engines: {node: '>=14.16'}
-
-  package-manager-detector@1.6.0:
-    resolution: {integrity: sha512-61A5ThoTiDG/C8s8UMZwSorAGwMJ0ERVGj2OjoW5pAalsNOg15+iQiPzrLJ4jhZ1HJzmC2PIHT2oEiH3R5fzNA==}
-
-  pako@2.2.0:
-    resolution: {integrity: sha512-zJq6RP/5q+TO2OpFV3FHzlPnFjmkb7Nc99a5SNjJE+uu/PkpChs+NIZSSzbBoD+6kjiISXjfYdwj1ZRQ81dz/w==}
-
-  param-case@3.0.4:
-    resolution: {integrity: sha512-RXlj7zCYokReqWpOPH9oYivUzLYZ5vAPIfEmCTNViosC78F8F0H9y7T7gG2M39ymgutxF5gcFEsyZQSph9Bp3A==}
-
-  parent-module@1.0.1:
-    resolution: {integrity: sha512-GQ2EWRpQV8/o+Aw8YqtfZZPfNRWZYkbidE9k5rpl/hC3vtHHBfGm2Ifi6qWV+coDGkrUKZAxE3Lot5kcsRlh+g==}
-    engines: {node: '>=6'}
-
-  parse-entities@2.0.0:
-    resolution: {integrity: sha512-kkywGpCcRYhqQIchaWqZ875wzpS/bMKhz5HnN3p7wveJTkTtyAB/AlnS0f8DFSqYW1T82t6yEAkEcB+A1I3MbQ==}
-
-  parse-entities@4.0.2:
-    resolution: {integrity: sha512-GG2AQYWoLgL877gQIKeRPGO1xF9+eG1ujIb5soS5gPvLQ1y2o8FL90w2QWNdf9I361Mpp7726c+lj3U0qK1uGw==}
-
-  parse-json@5.2.0:
-    resolution: {integrity: sha512-ayCKvm/phCGxOkYRSCM82iDwct8/EonSEgCSxWxD7ve6jHggsFl4fZVQBPRNgQoKiuV/odhFrGzQXZwbifC8Rg==}
-    engines: {node: '>=8'}
-
-  parse-numeric-range@1.3.0:
-    resolution: {integrity: sha512-twN+njEipszzlMJd4ONUYgSfZPDxgHhT9Ahed5uTigpQn90FggW4SA/AIPq/6a149fTbE9qBEcSwE3FAEp6wQQ==}
-
-  parse5-htmlparser2-tree-adapter@7.1.0:
-    resolution: {integrity: sha512-ruw5xyKs6lrpo9x9rCZqZZnIUntICjQAd0Wsmp396Ul9lN/h+ifgVV1x1gZHi8euej6wTfpqX8j+BFQxF0NS/g==}
-
-  parse5@6.0.1:
-    resolution: {integrity: sha512-Ofn/CTFzRGTTxwpNEs9PP93gXShHcTq255nzRYSKe8AkVpZY7e1fpmTfOyoIvjP5HG7Z2ZM7VS9PPhQGW2pOpw==}
-
-  parse5@7.3.0:
-    resolution: {integrity: sha512-IInvU7fabl34qmi9gY8XOVxhYyMyuH2xUNpb2q8/Y+7552KlejkRvqvD19nMoUW/uQGGbqNpA6Tufu5FL5BZgw==}
-
-  parseurl@1.3.3:
-    resolution: {integrity: sha512-CiyeOxFT/JZyN5m0z9PfXw4SCBJ6Sygz1Dpl0wqjlhDEGGBP1GnsUVEL0p63hoG1fcj3fHynXi9NYO4nWOL+qQ==}
-    engines: {node: '>= 0.8'}
-
-  pascal-case@3.1.2:
-    resolution: {integrity: sha512-uWlGT3YSnK9x3BQJaOdcZwrnV6hPpd8jFH1/ucpiLRPh/2zCVJKS19E4GvYHvaCcACn3foXZ0cLB9Wrx1KGe5g==}
-
-  path-browserify@1.0.1:
-    resolution: {integrity: sha512-b7uo2UCUOYZcnF/3ID0lulOJi/bafxa1xPe7ZPsammBSpjSWQkjNxlt635YGS2MiR9GjvuXCtz2emr3jbsz98g==}
-
-  path-data-parser@0.1.0:
-    resolution: {integrity: sha512-NOnmBpt5Y2RWbuv0LMzsayp3lVylAHLPUTut412ZA3l+C4uw4ZVkQbjShYCQ8TCpUMdPapr4YjUqLYD6v68j+w==}
-
-  path-exists@4.0.0:
-    resolution: {integrity: sha512-ak9Qy5Q7jYb2Wwcey5Fpvg2KoAc/ZIhLSLOSBmRmygPsGwkVVt0fZa0qrtMz+m6tJTAHfZQ8FnmB4MG4LWy7/w==}
-    engines: {node: '>=8'}
-
-  path-exists@5.0.0:
-    resolution: {integrity: sha512-RjhtfwJOxzcFmNOi6ltcbcu4Iu+FL3zEj83dk4kAS+fVpTxXLO1b38RvJgT/0QwvV/L3aY9TAnyv0EOqW4GoMQ==}
-    engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
-
-  path-is-absolute@1.0.1:
-    resolution: {integrity: sha512-AVbw3UJ2e9bq64vSaS9Am0fje1Pa8pbGqTTsmXfaIiMpnr5DlDhfJOuLj9Sf95ZPVDAUerDfEk88MPmPe7UCQg==}
-    engines: {node: '>=0.10.0'}
-
-  path-is-inside@1.0.2:
-    resolution: {integrity: sha512-DUWJr3+ULp4zXmol/SZkFf3JGsS9/SIv+Y3Rt93/UjPpDpklB5f1er4O3POIbUuUJ3FXgqte2Q7SrU6zAqwk8w==}
-
-  path-key@3.1.1:
-    resolution: {integrity: sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q==}
-    engines: {node: '>=8'}
-
-  path-parse@1.0.7:
-    resolution: {integrity: sha512-LDJzPVEEEPR+y48z93A0Ed0yXb8pAByGWo/k5YYdYgpY2/2EsOsksJrq7lOHxryrVOn1ejG6oAp8ahvOIQD8sw==}
-
-  path-scurry@2.0.2:
-    resolution: {integrity: sha512-3O/iVVsJAPsOnpwWIeD+d6z/7PmqApyQePUtCndjatj/9I5LylHvt5qluFaBT3I5h3r1ejfR056c+FCv+NnNXg==}
-    engines: {node: 18 || 20 || >=22}
-
-  path-to-regexp@0.1.13:
-    resolution: {integrity: sha512-A/AGNMFN3c8bOlvV9RreMdrv7jsmF9XIfDeCd87+I8RNg6s78BhJxMu69NEMHBSJFxKidViTEdruRwEk/WIKqA==}
-
-  path-to-regexp@1.9.0:
-    resolution: {integrity: sha512-xIp7/apCFJuUHdDLWe8O1HIkb0kQrOMb/0u6FXQjemHn/ii5LrIzU6bdECnsiTF/GjZkMEKg1xdiZwNqDYlZ6g==}
-
-  path-to-regexp@3.3.0:
-    resolution: {integrity: sha512-qyCH421YQPS2WFDxDjftfc1ZR5WKQzVzqsp4n9M2kQhVOo/ByahFoUNJfl58kOcEGfQ//7weFTDhm+ss8Ecxgw==}
-
-  path-type@4.0.0:
-    resolution: {integrity: sha512-gDKb8aZMDeD/tZWs9P6+q0J9Mwkdl6xMV8TjnGP3qJVJ06bdMgkbBlLU8IdfOsIsFz2BW1rNVT3XuNEl8zPAvw==}
-    engines: {node: '>=8'}
-
-  picocolors@1.1.1:
-    resolution: {integrity: sha512-xceH2snhtb5M9liqDsmEw56le376mTZkEX/jEb/RxNFyegNul7eNslCXP9FDj/Lcu0X8KEyMceP2ntpaHrDEVA==}
-
-  picomatch@2.3.2:
-    resolution: {integrity: sha512-V7+vQEJ06Z+c5tSye8S+nHUfI51xoXIXjHQ99cQtKUkQqqO1kO/KCJUfZXuB47h/YBlDhah2H3hdUGXn8ie0oA==}
-    engines: {node: '>=8.6'}
-
-  picomatch@4.0.4:
-    resolution: {integrity: sha512-QP88BAKvMam/3NxH6vj2o21R6MjxZUAd6nlwAS/pnGvN9IVLocLHxGYIzFhg6fUQ+5th6P4dv4eW9jX3DSIj7A==}
-    engines: {node: '>=12'}
-
-  pirates@4.0.7:
-    resolution: {integrity: sha512-TfySrs/5nm8fQJDcBDuUng3VOUKsd7S+zqvbOTiGXHfxX4wK31ard+hoNuvkicM/2YFzlpDgABOevKSsB4G/FA==}
-    engines: {node: '>= 6'}
-
-  pkg-dir@7.0.0:
-    resolution: {integrity: sha512-Ie9z/WINcxxLp27BKOCHGde4ITq9UklYKDzVo1nhk5sqGEXU3FpkwP5GM2voTGJkGd9B3Otl+Q4uwSOeSUtOBA==}
-    engines: {node: '>=14.16'}
-
-  pkijs@3.4.0:
-    resolution: {integrity: sha512-emEcLuomt2j03vxD54giVB4SxTjnsqkU692xZOZXHDVoYyypEm+b3jpiTcc+Cf+myooc+/Ly0z01jqeNHVgJGw==}
-    engines: {node: '>=16.0.0'}
-
-  pluralize@8.0.0:
-    resolution: {integrity: sha512-Nc3IT5yHzflTfbjgqWcCPpo7DaKy4FnpB0l/zCAW0Tc7jxAiuqSxHasntB3D7887LSrA93kDJ9IXovxJYxyLCA==}
-    engines: {node: '>=4'}
-
-  points-on-curve@0.2.0:
-    resolution: {integrity: sha512-0mYKnYYe9ZcqMCWhUjItv/oHjvgEsfKvnUTg8sAtnHr3GVy7rGkXCb6d5cSyqrWqL4k81b9CPg3urd+T7aop3A==}
-
-  points-on-path@0.2.1:
-    resolution: {integrity: sha512-25ClnWWuw7JbWZcgqY/gJ4FQWadKxGWk+3kR/7kD0tCaDtPPMj7oHu2ToLaVhfpnHrZzYby2w6tUA0eOIuUg8g==}
-
-  polished@4.3.1:
-    resolution: {integrity: sha512-OBatVyC/N7SCW/FaDHrSd+vn0o5cS855TOmYi4OkdWUMSJCET/xip//ch8xGUvtr3i44X9LVyWwQlRMTN3pwSA==}
-    engines: {node: '>=10'}
-
-  postcss-attribute-case-insensitive@7.0.1:
-    resolution: {integrity: sha512-Uai+SupNSqzlschRyNx3kbCTWgY/2hcwtHEI/ej2LJWc9JJ77qKgGptd8DHwY1mXtZ7Aoh4z4yxfwMBue9eNgw==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
-
-  postcss-calc@9.0.1:
-    resolution: {integrity: sha512-TipgjGyzP5QzEhsOZUaIkeO5mKeMFpebWzRogWG/ysonUlnHcq5aJe0jOjpfzUU8PeSaBQnrE8ehR0QA5vs8PQ==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.2.2
-
-  postcss-clamp@4.1.0:
-    resolution: {integrity: sha512-ry4b1Llo/9zz+PKC+030KUnPITTJAHeOwjfAyyB60eT0AorGLdzp52s31OsPRHRf8NchkgFoG2y6fCfn1IV1Ow==}
-    engines: {node: '>=7.6.0'}
-    peerDependencies:
-      postcss: ^8.4.6
-
-  postcss-color-functional-notation@7.0.12:
-    resolution: {integrity: sha512-TLCW9fN5kvO/u38/uesdpbx3e8AkTYhMvDZYa9JpmImWuTE99bDQ7GU7hdOADIZsiI9/zuxfAJxny/khknp1Zw==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
-
-  postcss-color-hex-alpha@10.0.0:
-    resolution: {integrity: sha512-1kervM2cnlgPs2a8Vt/Qbe5cQ++N7rkYo/2rz2BkqJZIHQwaVuJgQH38REHrAi4uM0b1fqxMkWYmese94iMp3w==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
-
-  postcss-color-rebeccapurple@10.0.0:
-    resolution: {integrity: sha512-JFta737jSP+hdAIEhk1Vs0q0YF5P8fFcj+09pweS8ktuGuZ8pPlykHsk6mPxZ8awDl4TrcxUqJo9l1IhVr/OjQ==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
-
-  postcss-colormin@6.1.0:
-    resolution: {integrity: sha512-x9yX7DOxeMAR+BgGVnNSAxmAj98NX/YxEMNFP+SDCEeNLb2r3i6Hh1ksMsnW8Ub5SLCpbescQqn9YEbE9554Sw==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-convert-values@6.1.0:
-    resolution: {integrity: sha512-zx8IwP/ts9WvUM6NkVSkiU902QZL1bwPhaVaLynPtCsOTqp+ZKbNi+s6XJg3rfqpKGA/oc7Oxk5t8pOQJcwl/w==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-custom-media@11.0.6:
-    resolution: {integrity: sha512-C4lD4b7mUIw+RZhtY7qUbf4eADmb7Ey8BFA2px9jUbwg7pjTZDl4KY4bvlUV+/vXQvzQRfiGEVJyAbtOsCMInw==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
-
-  postcss-custom-properties@14.0.6:
-    resolution: {integrity: sha512-fTYSp3xuk4BUeVhxCSJdIPhDLpJfNakZKoiTDx7yRGCdlZrSJR7mWKVOBS4sBF+5poPQFMj2YdXx1VHItBGihQ==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
-
-  postcss-custom-selectors@8.0.5:
-    resolution: {integrity: sha512-9PGmckHQswiB2usSO6XMSswO2yFWVoCAuih1yl9FVcwkscLjRKjwsjM3t+NIWpSU2Jx3eOiK2+t4vVTQaoCHHg==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
-
-  postcss-dir-pseudo-class@9.0.1:
-    resolution: {integrity: sha512-tRBEK0MHYvcMUrAuYMEOa0zg9APqirBcgzi6P21OhxtJyJADo/SWBwY1CAwEohQ/6HDaa9jCjLRG7K3PVQYHEA==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
-
-  postcss-discard-comments@6.0.2:
-    resolution: {integrity: sha512-65w/uIqhSBBfQmYnG92FO1mWZjJ4GL5b8atm5Yw2UgrwD7HiNiSSNwJor1eCFGzUgYnN/iIknhNRVqjrrpuglw==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-discard-duplicates@6.0.3:
-    resolution: {integrity: sha512-+JA0DCvc5XvFAxwx6f/e68gQu/7Z9ud584VLmcgto28eB8FqSFZwtrLwB5Kcp70eIoWP/HXqz4wpo8rD8gpsTw==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-discard-empty@6.0.3:
-    resolution: {integrity: sha512-znyno9cHKQsK6PtxL5D19Fj9uwSzC2mB74cpT66fhgOadEUPyXFkbgwm5tvc3bt3NAy8ltE5MrghxovZRVnOjQ==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-discard-overridden@6.0.2:
-    resolution: {integrity: sha512-j87xzI4LUggC5zND7KdjsI25APtyMuynXZSujByMaav2roV6OZX+8AaCUcZSWqckZpjAjRyFDdpqybgjFO0HJQ==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-discard-unused@6.0.5:
-    resolution: {integrity: sha512-wHalBlRHkaNnNwfC8z+ppX57VhvS+HWgjW508esjdaEYr3Mx7Gnn2xA4R/CKf5+Z9S5qsqC+Uzh4ueENWwCVUA==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-double-position-gradients@6.0.4:
-    resolution: {integrity: sha512-m6IKmxo7FxSP5nF2l63QbCC3r+bWpFUWmZXZf096WxG0m7Vl1Q1+ruFOhpdDRmKrRS+S3Jtk+TVk/7z0+BVK6g==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
-
-  postcss-focus-visible@10.0.1:
-    resolution: {integrity: sha512-U58wyjS/I1GZgjRok33aE8juW9qQgQUNwTSdxQGuShHzwuYdcklnvK/+qOWX1Q9kr7ysbraQ6ht6r+udansalA==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
-
-  postcss-focus-within@9.0.1:
-    resolution: {integrity: sha512-fzNUyS1yOYa7mOjpci/bR+u+ESvdar6hk8XNK/TRR0fiGTp2QT5N+ducP0n3rfH/m9I7H/EQU6lsa2BrgxkEjw==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
-
-  postcss-font-variant@5.0.0:
-    resolution: {integrity: sha512-1fmkBaCALD72CK2a9i468mA/+tr9/1cBxRRMXOUaZqO43oWPR5imcyPjXwuv7PXbCid4ndlP5zWhidQVVa3hmA==}
-    peerDependencies:
-      postcss: ^8.1.0
-
-  postcss-gap-properties@6.0.0:
-    resolution: {integrity: sha512-Om0WPjEwiM9Ru+VhfEDPZJAKWUd0mV1HmNXqp2C29z80aQ2uP9UVhLc7e3aYMIor/S5cVhoPgYQ7RtfeZpYTRw==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
-
-  postcss-image-set-function@7.0.0:
-    resolution: {integrity: sha512-QL7W7QNlZuzOwBTeXEmbVckNt1FSmhQtbMRvGGqqU4Nf4xk6KUEQhAoWuMzwbSv5jxiRiSZ5Tv7eiDB9U87znA==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
-
-  postcss-lab-function@7.0.12:
-    resolution: {integrity: sha512-tUcyRk1ZTPec3OuKFsqtRzW2Go5lehW29XA21lZ65XmzQkz43VY2tyWEC202F7W3mILOjw0voOiuxRGTsN+J9w==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
-
-  postcss-loader@7.3.4:
-    resolution: {integrity: sha512-iW5WTTBSC5BfsBJ9daFMPVrLT36MrNiC6fqOZTTaHjBNX6Pfd5p+hSBqe/fEeNd7pc13QiAyGt7VdGMw4eRC4A==}
-    engines: {node: '>= 14.15.0'}
-    peerDependencies:
-      postcss: ^7.0.0 || ^8.0.1
-      webpack: ^5.0.0
-
-  postcss-logical@8.1.0:
-    resolution: {integrity: sha512-pL1hXFQ2fEXNKiNiAgtfA005T9FBxky5zkX6s4GZM2D8RkVgRqz3f4g1JUoq925zXv495qk8UNldDwh8uGEDoA==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
-
-  postcss-merge-idents@6.0.3:
-    resolution: {integrity: sha512-1oIoAsODUs6IHQZkLQGO15uGEbK3EAl5wi9SS8hs45VgsxQfMnxvt+L+zIr7ifZFIH14cfAeVe2uCTa+SPRa3g==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-merge-longhand@6.0.5:
-    resolution: {integrity: sha512-5LOiordeTfi64QhICp07nzzuTDjNSO8g5Ksdibt44d+uvIIAE1oZdRn8y/W5ZtYgRH/lnLDlvi9F8btZcVzu3w==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-merge-rules@6.1.1:
-    resolution: {integrity: sha512-KOdWF0gju31AQPZiD+2Ar9Qjowz1LTChSjFFbS+e2sFgc4uHOp3ZvVX4sNeTlk0w2O31ecFGgrFzhO0RSWbWwQ==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-minify-font-values@6.1.0:
-    resolution: {integrity: sha512-gklfI/n+9rTh8nYaSJXlCo3nOKqMNkxuGpTn/Qm0gstL3ywTr9/WRKznE+oy6fvfolH6dF+QM4nCo8yPLdvGJg==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-minify-gradients@6.0.3:
-    resolution: {integrity: sha512-4KXAHrYlzF0Rr7uc4VrfwDJ2ajrtNEpNEuLxFgwkhFZ56/7gaE4Nr49nLsQDZyUe+ds+kEhf+YAUolJiYXF8+Q==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-minify-params@6.1.0:
-    resolution: {integrity: sha512-bmSKnDtyyE8ujHQK0RQJDIKhQ20Jq1LYiez54WiaOoBtcSuflfK3Nm596LvbtlFcpipMjgClQGyGr7GAs+H1uA==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-minify-selectors@6.0.4:
-    resolution: {integrity: sha512-L8dZSwNLgK7pjTto9PzWRoMbnLq5vsZSTu8+j1P/2GB8qdtGQfn+K1uSvFgYvgh83cbyxT5m43ZZhUMTJDSClQ==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-modules-extract-imports@3.1.0:
-    resolution: {integrity: sha512-k3kNe0aNFQDAZGbin48pL2VNidTF0w4/eASDsxlyspobzU3wZQLOGj7L9gfRe0Jo9/4uud09DsjFNH7winGv8Q==}
-    engines: {node: ^10 || ^12 || >= 14}
-    peerDependencies:
-      postcss: ^8.1.0
-
-  postcss-modules-local-by-default@4.2.0:
-    resolution: {integrity: sha512-5kcJm/zk+GJDSfw+V/42fJ5fhjL5YbFDl8nVdXkJPLLW+Vf9mTD5Xe0wqIaDnLuL2U6cDNpTr+UQ+v2HWIBhzw==}
-    engines: {node: ^10 || ^12 || >= 14}
-    peerDependencies:
-      postcss: ^8.1.0
-
-  postcss-modules-scope@3.2.1:
-    resolution: {integrity: sha512-m9jZstCVaqGjTAuny8MdgE88scJnCiQSlSrOWcTQgM2t32UBe+MUmFSO5t7VMSfAf/FJKImAxBav8ooCHJXCJA==}
-    engines: {node: ^10 || ^12 || >= 14}
-    peerDependencies:
-      postcss: ^8.1.0
-
-  postcss-modules-values@4.0.0:
-    resolution: {integrity: sha512-RDxHkAiEGI78gS2ofyvCsu7iycRv7oqw5xMWn9iMoR0N/7mf9D50ecQqUo5BZ9Zh2vH4bCUR/ktCqbB9m8vJjQ==}
-    engines: {node: ^10 || ^12 || >= 14}
-    peerDependencies:
-      postcss: ^8.1.0
-
-  postcss-nesting@13.0.2:
-    resolution: {integrity: sha512-1YCI290TX+VP0U/K/aFxzHzQWHWURL+CtHMSbex1lCdpXD1SoR2sYuxDu5aNI9lPoXpKTCggFZiDJbwylU0LEQ==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
-
-  postcss-normalize-charset@6.0.2:
-    resolution: {integrity: sha512-a8N9czmdnrjPHa3DeFlwqst5eaL5W8jYu3EBbTTkI5FHkfMhFZh1EGbku6jhHhIzTA6tquI2P42NtZ59M/H/kQ==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-normalize-display-values@6.0.2:
-    resolution: {integrity: sha512-8H04Mxsb82ON/aAkPeq8kcBbAtI5Q2a64X/mnRRfPXBq7XeogoQvReqxEfc0B4WPq1KimjezNC8flUtC3Qz6jg==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-normalize-positions@6.0.2:
-    resolution: {integrity: sha512-/JFzI441OAB9O7VnLA+RtSNZvQ0NCFZDOtp6QPFo1iIyawyXg0YI3CYM9HBy1WvwCRHnPep/BvI1+dGPKoXx/Q==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-normalize-repeat-style@6.0.2:
-    resolution: {integrity: sha512-YdCgsfHkJ2jEXwR4RR3Tm/iOxSfdRt7jplS6XRh9Js9PyCR/aka/FCb6TuHT2U8gQubbm/mPmF6L7FY9d79VwQ==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-normalize-string@6.0.2:
-    resolution: {integrity: sha512-vQZIivlxlfqqMp4L9PZsFE4YUkWniziKjQWUtsxUiVsSSPelQydwS8Wwcuw0+83ZjPWNTl02oxlIvXsmmG+CiQ==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-normalize-timing-functions@6.0.2:
-    resolution: {integrity: sha512-a+YrtMox4TBtId/AEwbA03VcJgtyW4dGBizPl7e88cTFULYsprgHWTbfyjSLyHeBcK/Q9JhXkt2ZXiwaVHoMzA==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-normalize-unicode@6.1.0:
-    resolution: {integrity: sha512-QVC5TQHsVj33otj8/JD869Ndr5Xcc/+fwRh4HAsFsAeygQQXm+0PySrKbr/8tkDKzW+EVT3QkqZMfFrGiossDg==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-normalize-url@6.0.2:
-    resolution: {integrity: sha512-kVNcWhCeKAzZ8B4pv/DnrU1wNh458zBNp8dh4y5hhxih5RZQ12QWMuQrDgPRw3LRl8mN9vOVfHl7uhvHYMoXsQ==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-normalize-whitespace@6.0.2:
-    resolution: {integrity: sha512-sXZ2Nj1icbJOKmdjXVT9pnyHQKiSAyuNQHSgRCUgThn2388Y9cGVDR+E9J9iAYbSbLHI+UUwLVl1Wzco/zgv0Q==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-opacity-percentage@3.0.0:
-    resolution: {integrity: sha512-K6HGVzyxUxd/VgZdX04DCtdwWJ4NGLG212US4/LA1TLAbHgmAsTWVR86o+gGIbFtnTkfOpb9sCRBx8K7HO66qQ==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
-
-  postcss-ordered-values@6.0.2:
-    resolution: {integrity: sha512-VRZSOB+JU32RsEAQrO94QPkClGPKJEL/Z9PCBImXMhIeK5KAYo6slP/hBYlLgrCjFxyqvn5VC81tycFEDBLG1Q==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-overflow-shorthand@6.0.0:
-    resolution: {integrity: sha512-BdDl/AbVkDjoTofzDQnwDdm/Ym6oS9KgmO7Gr+LHYjNWJ6ExORe4+3pcLQsLA9gIROMkiGVjjwZNoL/mpXHd5Q==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
-
-  postcss-page-break@3.0.4:
-    resolution: {integrity: sha512-1JGu8oCjVXLa9q9rFTo4MbeeA5FMe00/9C7lN4va606Rdb+HkxXtXsmEDrIraQ11fGz/WvKWa8gMuCKkrXpTsQ==}
-    peerDependencies:
-      postcss: ^8
-
-  postcss-place@10.0.0:
-    resolution: {integrity: sha512-5EBrMzat2pPAxQNWYavwAfoKfYcTADJ8AXGVPcUZ2UkNloUTWzJQExgrzrDkh3EKzmAx1evfTAzF9I8NGcc+qw==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
-
-  postcss-preset-env@10.6.1:
-    resolution: {integrity: sha512-yrk74d9EvY+W7+lO9Aj1QmjWY9q5NsKjK2V9drkOPZB/X6KZ0B3igKsHUYakb7oYVhnioWypQX3xGuePf89f3g==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
-
-  postcss-pseudo-class-any-link@10.0.1:
-    resolution: {integrity: sha512-3el9rXlBOqTFaMFkWDOkHUTQekFIYnaQY55Rsp8As8QQkpiSgIYEcF/6Ond93oHiDsGb4kad8zjt+NPlOC1H0Q==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
-
-  postcss-reduce-idents@6.0.3:
-    resolution: {integrity: sha512-G3yCqZDpsNPoQgbDUy3T0E6hqOQ5xigUtBQyrmq3tn2GxlyiL0yyl7H+T8ulQR6kOcHJ9t7/9H4/R2tv8tJbMA==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-reduce-initial@6.1.0:
-    resolution: {integrity: sha512-RarLgBK/CrL1qZags04oKbVbrrVK2wcxhvta3GCxrZO4zveibqbRPmm2VI8sSgCXwoUHEliRSbOfpR0b/VIoiw==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-reduce-transforms@6.0.2:
-    resolution: {integrity: sha512-sB+Ya++3Xj1WaT9+5LOOdirAxP7dJZms3GRcYheSPi1PiTMigsxHAdkrbItHxwYHr4kt1zL7mmcHstgMYT+aiA==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-replace-overflow-wrap@4.0.0:
-    resolution: {integrity: sha512-KmF7SBPphT4gPPcKZc7aDkweHiKEEO8cla/GjcBK+ckKxiZslIu3C4GCRW3DNfL0o7yW7kMQu9xlZ1kXRXLXtw==}
-    peerDependencies:
-      postcss: ^8.0.3
-
-  postcss-selector-not@8.0.1:
-    resolution: {integrity: sha512-kmVy/5PYVb2UOhy0+LqUYAhKj7DUGDpSWa5LZqlkWJaaAV+dxxsOG3+St0yNLu6vsKD7Dmqx+nWQt0iil89+WA==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      postcss: ^8.4
-
-  postcss-selector-parser@6.1.2:
-    resolution: {integrity: sha512-Q8qQfPiZ+THO/3ZrOrO0cJJKfpYCagtMUkXbnEfmgUjwXg6z/WBeOyS9APBBPCTSiDV+s4SwQGu8yFsiMRIudg==}
-    engines: {node: '>=4'}
-
-  postcss-selector-parser@7.1.2:
-    resolution: {integrity: sha512-Wjvt4scRFouioIInHf51IFNP4ltJ2EngJM+cZPGiqbKetBfmP3vpdPV8ID2S6JS6/jdo74N8+aEYH9lQr2C6sA==}
-    engines: {node: '>=4'}
-
-  postcss-sort-media-queries@5.2.0:
-    resolution: {integrity: sha512-AZ5fDMLD8SldlAYlvi8NIqo0+Z8xnXU2ia0jxmuhxAU+Lqt9K+AlmLNJ/zWEnE9x+Zx3qL3+1K20ATgNOr3fAA==}
-    engines: {node: '>=14.0.0'}
-    peerDependencies:
-      postcss: ^8.4.23
-
-  postcss-svgo@6.0.3:
-    resolution: {integrity: sha512-dlrahRmxP22bX6iKEjOM+c8/1p+81asjKT+V5lrgOH944ryx/OHpclnIbGsKVd3uWOXFLYJwCVf0eEkJGvO96g==}
-    engines: {node: ^14 || ^16 || >= 18}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-unique-selectors@6.0.4:
-    resolution: {integrity: sha512-K38OCaIrO8+PzpArzkLKB42dSARtC2tmG6PvD4b1o1Q2E9Os8jzfWFfSy/rixsHwohtsDdFtAWGjFVFUdwYaMg==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss-value-parser@4.2.0:
-    resolution: {integrity: sha512-1NNCs6uurfkVbeXG4S8JFT9t19m45ICnif8zWLd5oPSZ50QnwMfK+H3jv408d4jw/7Bttv5axS5IiHoLaVNHeQ==}
-
-  postcss-zindex@6.0.2:
-    resolution: {integrity: sha512-5BxW9l1evPB/4ZIc+2GobEBoKC+h8gPGCMi+jxsYvd2x0mjq7wazk6DrP71pStqxE9Foxh5TVnonbWpFZzXaYg==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  postcss@8.5.15:
-    resolution: {integrity: sha512-FfR8sjd4em2T6fb3I2MwAJU7HWVMr9zba+enmQeeWFfCbm+UOC/0X4DS8XtpUTMwWMGbjKYP7xjfNekzyGmB3A==}
-    engines: {node: ^10 || ^12 || >=14}
-
-  postman-code-generators@2.1.1:
-    resolution: {integrity: sha512-+egQK1Jf9a92QP23vRTKcDLOthIQmI7WI4czEsZq/wgguLMnVHJ26KlT8AVtpAdVw28hqUbHwicerYxRWCfjoA==}
-    engines: {node: '>=18'}
-
-  postman-collection@5.3.0:
-    resolution: {integrity: sha512-PMa5vRheqDFfS1bkRg8WBidWxunRA80sT5YNLP27YC5+ycyfiLMCwPnqQd1zfvxkGk04Pr9UronWmmgsbpsVyQ==}
-    engines: {node: '>=18'}
-
-  postman-url-encoder@3.0.8:
-    resolution: {integrity: sha512-EOgUMBazo7JNP4TDrd64TsooCiWzzo4143Ws8E8WYGEpn2PKpq+S4XRTDhuRTYHm3VKOpUZs7ZYZq7zSDuesqA==}
-    engines: {node: '>=10'}
-
-  prelude-ls@1.2.1:
-    resolution: {integrity: sha512-vkcDPrRZo1QZLbn5RLGPpg/WmIQ65qoWWhcGKf/b5eplkkarX0m9z8ppCat4mlOqUsWpyNuYgO3VRyrYHSzX5g==}
-    engines: {node: '>= 0.8.0'}
-
-  prettier@3.9.4:
-    resolution: {integrity: sha512-yWG/o/4oJfo036EKAfK6ACAoDOfHeRHx4tuxkfBZiauURiaSmYwlpOr5LQqKtIkRD2z1PLteme2WoxEnj4tHTg==}
-    engines: {node: '>=14'}
-    hasBin: true
-
-  pretty-error@4.0.0:
-    resolution: {integrity: sha512-AoJ5YMAcXKYxKhuJGdcvse+Voc6v1RgnsR3nWcYU7q4t6z0Q6T86sv5Zq8VIRbOWWFpvdGE83LtdSMNd+6Y0xw==}
-
-  pretty-time@1.1.0:
-    resolution: {integrity: sha512-28iF6xPQrP8Oa6uxE6a1biz+lWeTOAPKggvjB8HAs6nVMKZwf5bG++632Dx614hIWgUPkgivRfG+a8uAXGTIbA==}
-    engines: {node: '>=4'}
-
-  prism-react-renderer@1.3.5:
-    resolution: {integrity: sha512-IJ+MSwBWKG+SM3b2SUfdrhC+gu01QkV2KmRQgREThBfSQRoufqRfxfHUxpG1WcaFjP+kojcFyO9Qqtpgt3qLCg==}
-    peerDependencies:
-      react: '>=0.14.9'
-
-  prism-react-renderer@2.4.1:
-    resolution: {integrity: sha512-ey8Ls/+Di31eqzUxC46h8MksNuGx/n0AAC8uKpwFau4RPDYLuE3EXTp8N8G2vX2N7UC/+IXeNUnlWBGGcAG+Ig==}
-    peerDependencies:
-      react: '>=16.0.0'
-
-  prismjs@1.27.0:
-    resolution: {integrity: sha512-t13BGPUlFDR7wRB5kQDG4jjl7XeuH6jbJGt11JHPL96qwsEHNX2+68tFXqc1/k+/jALsbSWJKUOT/hcYAZ5LkA==}
-    engines: {node: '>=6'}
-
-  prismjs@1.30.0:
-    resolution: {integrity: sha512-DEvV2ZF2r2/63V+tK8hQvrR2ZGn10srHbXviTlcv7Kpzw8jWiNTqbVgjO3IY8RxrrOUF8VPMQQFysYYYv0YZxw==}
-    engines: {node: '>=6'}
-
-  process-nextick-args@2.0.1:
-    resolution: {integrity: sha512-3ouUOpQhtgrbOa17J7+uxOTpITYWaGP7/AhoR3+A+/1e9skrzelGi/dXzEYyvbxubEF6Wn2ypscTKiKJFFn1ag==}
-
-  process@0.11.10:
-    resolution: {integrity: sha512-cdGef/drWFoydD1JsMzuFf8100nZl+GT+yacc2bEced5f9Rjk4z+WtFUTBu9PhOi9j/jfmBPu0mMEY4wIdAF8A==}
-    engines: {node: '>= 0.6.0'}
-
-  prompts@2.4.2:
-    resolution: {integrity: sha512-NxNv/kLguCA7p3jE8oL2aEBsrJWgAakBpgmgK6lpPWV+WuOmY6r2/zbAVnP+T8bQlA0nzHXSJSJW0Hq7ylaD2Q==}
-    engines: {node: '>= 6'}
-
-  prop-types@15.8.1:
-    resolution: {integrity: sha512-oj87CgZICdulUohogVAR7AjlC0327U4el4L6eAvOqCeudMDVU0NThNaV+b9Df4dXgSP1gXMTnPdhfe/2qDH5cg==}
-
-  property-information@5.6.0:
-    resolution: {integrity: sha512-YUHSPk+A30YPv+0Qf8i9Mbfe/C0hdPXk1s1jPVToV8pk8BQtpw10ct89Eo7OWkutrwqvT0eicAxlOg3dOAu8JA==}
-
-  property-information@6.5.0:
-    resolution: {integrity: sha512-PgTgs/BlvHxOu8QuEN7wi5A0OmXaBcHpmCSTehcs6Uuu9IkDIEo13Hy7n898RHfrQ49vKCoGeWZSaAK01nwVig==}
-
-  property-information@7.2.0:
-    resolution: {integrity: sha512-IAtzIB6sUiWaJYrX9smp3V46pBGbBeLFRGdh25kg1334VcBlD8HzhPeNIWQH9zhGmo2itIe25EHt9dQP7G5hmg==}
-
-  proto-list@1.2.4:
-    resolution: {integrity: sha512-vtK/94akxsTMhe0/cbfpR+syPuszcuwhqVjJq26CuNDgFGj682oRBXOP5MJpv2r7JtE8MsiepGIqvvOTBwn2vA==}
-
-  proxy-addr@2.0.7:
-    resolution: {integrity: sha512-llQsMLSUDUPT44jdrU/O37qlnifitDP+ZwrmmZcoSKyLKvtZxpyV0n2/bD/N4tBAAZ/gJEdZU7KMraoK1+XYAg==}
-    engines: {node: '>= 0.10'}
-
-  punycode@1.4.1:
-    resolution: {integrity: sha512-jmYNElW7yvO7TV33CjSmvSiE2yco3bV2czu/OzDKdMNVZQWfxCblURLhf+47syQRBntjfLdd/H0egrzIG+oaFQ==}
-
-  punycode@2.3.1:
-    resolution: {integrity: sha512-vYt7UD1U9Wg6138shLtLOvdAu+8DsC/ilFtEVHcH+wydcSpNE20AfSOduf6MkRFahL5FY7X1oU7nKVZFtfq8Fg==}
-    engines: {node: '>=6'}
-
-  pupa@3.3.0:
-    resolution: {integrity: sha512-LjgDO2zPtoXP2wJpDjZrGdojii1uqO0cnwKoIoUzkfS98HDmbeiGmYiXo3lXeFlq2xvne1QFQhwYXSUCLKtEuA==}
-    engines: {node: '>=12.20'}
-
-  pvtsutils@1.3.6:
-    resolution: {integrity: sha512-PLgQXQ6H2FWCaeRak8vvk1GW462lMxB5s3Jm673N82zI4vqtVUPuZdffdZbPDFRoU8kAhItWFtPCWiPpp4/EDg==}
-
-  pvutils@1.1.5:
-    resolution: {integrity: sha512-KTqnxsgGiQ6ZAzZCVlJH5eOjSnvlyEgx1m8bkRJfOhmGRqfo5KLvmAlACQkrjEtOQ4B7wF9TdSLIs9O90MX9xA==}
-    engines: {node: '>=16.0.0'}
-
-  qs@6.15.2:
-    resolution: {integrity: sha512-Rzq0KEyX/w/tEybncDgdkZrJgVUsUMk3xjh3t5bv3S1HTAtg+uOYt72+ZfwiQwKdysThkTBdL/rTi6HDmX9Ddw==}
-    engines: {node: '>=0.6'}
-
-  qs@6.15.3:
-    resolution: {integrity: sha512-O9gl3zCl5h5blw1KGUzQKhA5oUXSl8rwUIM5o0S3nCXMliSvy5Dzx7/DJcI+SwgICv+IneSZwhBh1oSyEHA71A==}
-    engines: {node: '>=0.6'}
-
-  queue-microtask@1.2.3:
-    resolution: {integrity: sha512-NuaNSa6flKT5JaSYQzJok04JzTL1CA6aGhv5rfLW3PgqA+M2ChpZQnAC8h8i4ZFkBS8X5RqkDBHA7r4hej3K9A==}
-
-  quick-lru@5.1.1:
-    resolution: {integrity: sha512-WuyALRjWPDGtt/wzJiadO5AXY+8hZ80hVpe6MyivgraREW751X3SbhRvG3eLKOYN+8VEvqLcf3wdnt44Z4S4SA==}
-    engines: {node: '>=10'}
-
-  randombytes@2.1.0:
-    resolution: {integrity: sha512-vYl3iOX+4CKUWuxGi9Ukhie6fsqXqS9FE2Zaic4tNFD2N2QQaXOMFbuKK4QmDHC0JO6B1Zp41J0LpT0oR68amQ==}
-
-  range-parser@1.2.0:
-    resolution: {integrity: sha512-kA5WQoNVo4t9lNx2kQNFCxKeBl5IbbSNBl1M/tLkw9WCn+hxNBAW5Qh8gdhs63CJnhjJ2zQWFoqPJP2sK1AV5A==}
-    engines: {node: '>= 0.6'}
-
-  range-parser@1.2.1:
-    resolution: {integrity: sha512-Hrgsx+orqoygnmhFbKaHE6c296J+HTAQXoxEF6gNupROmmGJRoyzfG3ccAveqCBrwr/2yxQ5BVd/GTl5agOwSg==}
-    engines: {node: '>= 0.6'}
-
-  raw-body@2.5.3:
-    resolution: {integrity: sha512-s4VSOf6yN0rvbRZGxs8Om5CWj6seneMwK3oDb4lWDH0UPhWcxwOWw5+qk24bxq87szX1ydrwylIOp2uG1ojUpA==}
-    engines: {node: '>= 0.8'}
-
-  rc@1.2.8:
-    resolution: {integrity: sha512-y3bGgqKj3QBdxLbLkomlohkvsA8gdAiUQlSBJnBhfn+BPxg4bc62d8TcBW15wavDfgexCgccckhcZvywyQYPOw==}
-    hasBin: true
-
-  react-aria-components@1.18.0:
-    resolution: {integrity: sha512-FhRQjuDkH4WhgFv+O2sYTzK3JzdZTGpBeaqfRlfTo+DcSZzD8elJEkytHe7SDpcexVKeire8NVd7OruZHfCVoA==}
-    peerDependencies:
-      react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
-      react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
-
-  react-aria-components@1.20.0:
-    resolution: {integrity: sha512-BMbpIgoV9aELeBrB0Y120NgoigHb5OdcJwc+4e7uSnbTbamea6lo+gqcc4LAxzMaK3Jf+7LI1oCDE6yANsmxIQ==}
-    peerDependencies:
-      react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
-      react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
-
-  react-aria@3.49.0:
-    resolution: {integrity: sha512-4+oK9FwJQWYhyA5zLfj/feOGY0zZbkE1muoF4gyxMroHVypjcYaRSTlJwvxph2zIlxt757KX6xIK2wJ5Aw1Kog==}
-    peerDependencies:
-      react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
-      react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
-
-  react-aria@3.51.0:
-    resolution: {integrity: sha512-AyWLw0XR38cFPwBu/ErgGaVrc5dupLEKmRlMXTGvFKOtbaGRQ2+yQJkjVhpdHhoRhU4+G+tJDFeHDTS8tK3bfQ==}
-    peerDependencies:
-      react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
-      react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
-
-  react-dom@19.2.7:
-    resolution: {integrity: sha512-t0BRVXvbiE/o20Hfw669rLbMCDWtYZLvmJigy2f0MxsXF+71pxhR3xOkspmsO8h3ZlNzyibAmtCa3l4lYKk6gQ==}
-    peerDependencies:
-      react: ^19.2.7
-
-  react-fast-compare@3.2.2:
-    resolution: {integrity: sha512-nsO+KSNgo1SbJqJEYRE9ERzo7YtYbou/OqjSQKxV7jcKox7+usiUVZOAC+XnDOABXggQTno0Y1CpVnuWEc1boQ==}
-
-  react-hook-form@7.80.0:
-    resolution: {integrity: sha512-4P+fk6oXsxY+6xSj7Euhc2sumQD8zQqCuVHoJwoyp9EchP+IUW9OESB7uHFJOKsIBQ4MQqYE84INJFqUCYNoOg==}
-    engines: {node: '>=18.0.0'}
-    peerDependencies:
-      react: ^16.8.0 || ^17 || ^18 || ^19
-
-  react-is@16.13.1:
-    resolution: {integrity: sha512-24e6ynE2H+OKt4kqsOvNd8kBpV65zoxbA4BVsEOB3ARVWQki/DHzaUoC5KuON/BiccDaCCTZBuOcfZs70kR8bQ==}
-
-  react-is@18.3.1:
-    resolution: {integrity: sha512-/LLMVyas0ljjAtoYiPqYiL8VWXzUUdThrmU5+n20DZv+a+ClRoevUzw5JxU+Ieh5/c87ytoTBV9G1FiKfNJdmg==}
-
-  react-json-view-lite@2.5.0:
-    resolution: {integrity: sha512-tk7o7QG9oYyELWHL8xiMQ8x4WzjCzbWNyig3uexmkLb54r8jO0yH3WCWx8UZS0c49eSA4QUmG5caiRJ8fAn58g==}
-    engines: {node: '>=18'}
-    peerDependencies:
-      react: ^18.0.0 || ^19.0.0
-
-  react-lifecycles-compat@3.0.4:
-    resolution: {integrity: sha512-fBASbA6LnOU9dOU2eW7aQ8xmYBSXUIWr+UmF9b1efZBazGNO+rcXT/icdKnYm2pTwcRylVUYwW7H1PHfLekVzA==}
-
-  react-live@4.1.8:
-    resolution: {integrity: sha512-B2SgNqwPuS2ekqj4lcxi5TibEcjWkdVyYykBEUBshPAPDQ527x2zPEZg560n8egNtAjUpwXFQm7pcXV65aAYmg==}
-    engines: {node: '>= 0.12.0', npm: '>= 2.0.0'}
-    peerDependencies:
-      react: '>=18.0.0'
-      react-dom: '>=18.0.0'
-
-  react-loadable-ssr-addon-v5-slorber@1.0.3:
-    resolution: {integrity: sha512-GXfh9VLwB5ERaCsU6RULh7tkemeX15aNh6wuMEBtfdyMa7fFG8TXrhXlx1SoEK2Ty/l6XIkzzYIQmyaWW3JgdQ==}
-    engines: {node: '>=10.13.0'}
-    peerDependencies:
-      react-loadable: '*'
-      webpack: '>=4.41.1 || 5.x'
-
-  react-magic-dropzone@1.0.1:
-    resolution: {integrity: sha512-0BIROPARmXHpk4AS3eWBOsewxoM5ndk2psYP/JmbCq8tz3uR2LIV1XiroZ9PKrmDRMctpW+TvsBCtWasuS8vFA==}
-
-  react-markdown@10.1.0:
-    resolution: {integrity: sha512-qKxVopLT/TyA6BX3Ue5NwabOsAzm0Q7kAPwq6L+wWDwisYs7R8vZ0nRXqq6rkueboxpkjvLGU9fWifiX/ZZFxQ==}
-    peerDependencies:
-      '@types/react': '>=18'
-      react: '>=18'
-
-  react-markdown@8.0.7:
-    resolution: {integrity: sha512-bvWbzG4MtOU62XqBx3Xx+zB2raaFFsq4mYiAzfjXJMEz2sixgeAfraA3tvzULF02ZdOMUOKTBFFaZJDDrq+BJQ==}
-    peerDependencies:
-      '@types/react': '>=16'
-      react: '>=16'
-
-  react-modal@3.16.3:
-    resolution: {integrity: sha512-yCYRJB5YkeQDQlTt17WGAgFJ7jr2QYcWa1SHqZ3PluDmnKJ/7+tVU+E6uKyZ0nODaeEj+xCpK4LcSnKXLMC0Nw==}
-    peerDependencies:
-      react: ^0.14.0 || ^15.0.0 || ^16 || ^17 || ^18 || ^19
-      react-dom: ^0.14.0 || ^15.0.0 || ^16 || ^17 || ^18 || ^19
-
-  react-overflow-list@0.5.0:
-    resolution: {integrity: sha512-+UegukgQ10E4ll3txz4DJyrnCgZ3eDVuv5dvR8ziyG5FfgCDZcUKeKhIgbU90oyqQa21aH4oLOoGKt0TiYJRmg==}
-    engines: {node: '>=10'}
-    peerDependencies:
-      react: '>=16'
-
-  react-redux@9.3.0:
-    resolution: {integrity: sha512-KQopgqFo/p/fgmAs5qz6p5RWaNAzq40WAu7fJIXnQpYxFPbJYtsJPWvGeF2rOBaY/kEuV77AVsX8TsQzKm+A/g==}
-    peerDependencies:
-      '@types/react': ^18.2.25 || ^19
-      react: ^18.0 || ^19
-      redux: ^5.0.0
-    peerDependenciesMeta:
-      '@types/react':
-        optional: true
-      redux:
-        optional: true
-
-  react-router-config@5.1.1:
-    resolution: {integrity: sha512-DuanZjaD8mQp1ppHjgnnUnyOlqYXZVjnov/JzFhjLEwd3Z4dYjMSnqrEzzGThH47vpCOqPPwJM2FtthLeJ8Pbg==}
-    peerDependencies:
-      react: '>=15'
-      react-router: '>=5'
-
-  react-router-dom@5.3.4:
-    resolution: {integrity: sha512-m4EqFMHv/Ih4kpcBCONHbkT68KoAeHN4p3lAGoNryfHi0dMy0kCzEZakiKRsvg5wHZ/JLrLW8o8KomWiz/qbYQ==}
-    peerDependencies:
-      react: '>=15'
-
-  react-router@5.3.4:
-    resolution: {integrity: sha512-Ys9K+ppnJah3QuaRiLxk+jDWOR1MekYQrlytiXxC1RyfbdsZkS5pvKAzCCr031xHixZwpnsYNT5xysdFHQaYsA==}
-    peerDependencies:
-      react: '>=15'
-
-  react-stately@3.47.0:
-    resolution: {integrity: sha512-H3ar+SOWP920EbVg7qWfP3fZjZiwhlEJAEJQqjt+w8oKijCwFgr0+R4941PIHscOXRNRvEOjvWilitImC0DdBg==}
-    peerDependencies:
-      react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
-
-  react-stately@3.49.0:
-    resolution: {integrity: sha512-13iNq2KzBrRAzxRc+n53hgROfIistiYY/sPtIhCw1qUB7/kmo+X1xEU2uiS5zcCIrc55AUPwoHqOIIpKWSwB9A==}
-    peerDependencies:
-      react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
-
-  react-syntax-highlighter@15.6.6:
-    resolution: {integrity: sha512-DgXrc+AZF47+HvAPEmn7Ua/1p10jNoVZVI/LoPiYdtY+OM+/nG5yefLHKJwdKqY1adMuHFbeyBaG9j64ML7vTw==}
-    peerDependencies:
-      react: '>= 0.14.0'
-
-  react-transition-group@4.4.5:
-    resolution: {integrity: sha512-pZcd1MCJoiKiBR2NRxeCRg13uCXbydPnmB4EOeRrY7480qNWO8IIgQG6zlDkm6uRMsURXPuKq0GWtiM59a5Q6g==}
-    peerDependencies:
-      react: '>=16.6.0'
-      react-dom: '>=16.6.0'
-
-  react-universal-interface@0.6.2:
-    resolution: {integrity: sha512-dg8yXdcQmvgR13RIlZbTRQOoUrDciFVoSBZILwjE2LFISxZZ8loVJKAkuzswl5js8BHda79bIb2b84ehU8IjXw==}
-    peerDependencies:
-      react: '*'
-      tslib: '*'
-
-  react-use@17.6.0:
-    resolution: {integrity: sha512-OmedEScUMKFfzn1Ir8dBxiLLSOzhKe/dPZwVxcujweSj45aNM7BEGPb9BEVIgVEqEXx6f3/TsXzwIktNgUR02g==}
-    peerDependencies:
-      react: '*'
-      react-dom: '*'
-
-  react@19.2.7:
-    resolution: {integrity: sha512-HNe9WslTbXmFK8o8cmwgAeJFSBvt1bPdHCVKtaaV+WlAN36mpT4hcRpwbf3fY56ar2oIXzsBpOAiIRHAdY0OlQ==}
-    engines: {node: '>=0.10.0'}
-
-  readable-stream@2.3.8:
-    resolution: {integrity: sha512-8p0AUk4XODgIewSi0l8Epjs+EVnWiK7NoDIEGU0HhE7+ZyY8D1IMY7odu5lRrFXGg71L15KG8QrPmum45RTtdA==}
-
-  readable-stream@3.6.2:
-    resolution: {integrity: sha512-9u/sniCrY3D5WdsERHzHE4G2YCXqoG5FTHUiCC4SIbr6XcLZBY05ya9EKjYek9O5xOAwjGq+1JdGBAS7Q9ScoA==}
-    engines: {node: '>= 6'}
-
-  readdirp@3.6.0:
-    resolution: {integrity: sha512-hOS089on8RduqdbhvQ5Z37A0ESjsqz6qnRcffsMU3495FuTdqSm+7bhJ29JvIOsBDEEnan5DPu9t3To9VRlMzA==}
-    engines: {node: '>=8.10.0'}
-
-  readdirp@5.0.0:
-    resolution: {integrity: sha512-9u/XQ1pvrQtYyMpZe7DXKv2p5CNvyVwzUB6uhLAnQwHMSgKMBR62lc7AHljaeteeHXn11XTAaLLUVZYVZyuRBQ==}
-    engines: {node: '>= 20.19.0'}
-
-  rechoir@0.6.2:
-    resolution: {integrity: sha512-HFM8rkZ+i3zrV+4LQjwQ0W+ez98pApMGM3HUrN04j3CqzPOzl9nmP15Y8YXNm8QHGv/eacOVEjqhmWpkRV0NAw==}
-    engines: {node: '>= 0.10'}
-
-  recma-build-jsx@1.0.0:
-    resolution: {integrity: sha512-8GtdyqaBcDfva+GUKDr3nev3VpKAhup1+RvkMvUxURHpW7QyIvk9F5wz7Vzo06CEMSilw6uArgRqhpiUcWp8ew==}
-
-  recma-jsx@1.0.1:
-    resolution: {integrity: sha512-huSIy7VU2Z5OLv6oFLosQGGDqPqdO1iq6bWNAdhzMxSJP7RAso4fCZ1cKu8j9YHCZf3TPrq4dw3okhrylgcd7w==}
-    peerDependencies:
-      acorn: ^6.0.0 || ^7.0.0 || ^8.0.0
-
-  recma-parse@1.0.0:
-    resolution: {integrity: sha512-OYLsIGBB5Y5wjnSnQW6t3Xg7q3fQ7FWbw/vcXtORTnyaSFscOtABg+7Pnz6YZ6c27fG1/aN8CjfwoUEUIdwqWQ==}
-
-  recma-stringify@1.0.0:
-    resolution: {integrity: sha512-cjwII1MdIIVloKvC9ErQ+OgAtwHBmcZ0Bg4ciz78FtbT8In39aAYbaA7zvxQ61xVMSPE8WxhLwLbhif4Js2C+g==}
-
-  redux-thunk@3.1.0:
-    resolution: {integrity: sha512-NW2r5T6ksUKXCabzhL9z+h206HQw/NJkcLm1GPImRQ8IzfXwRGqjVhKJGauHirT0DAuyy6hjdnMZaRoAcy0Klw==}
-    peerDependencies:
-      redux: ^5.0.0
-
-  redux@5.0.1:
-    resolution: {integrity: sha512-M9/ELqF6fy8FwmkpnF0S3YKOqMyoWJ4+CS5Efg2ct3oY9daQvd/Pc71FpGZsVsbl3Cpb+IIcjBDUnnyBdQbq4w==}
-
-  reflect-metadata@0.2.2:
-    resolution: {integrity: sha512-urBwgfrvVP/eAyXx4hluJivBKzuEbSQs9rKWCrCkbSxNv8mxPcUZKeuoF3Uy4mJl3Lwprp6yy5/39VWigZ4K6Q==}
-
-  refractor@3.6.0:
-    resolution: {integrity: sha512-MY9W41IOWxxk31o+YvFCNyNzdkc9M20NoZK5vq6jkv4I/uh2zkWcfudj0Q1fovjUQJrNewS9NMzeTtqPf+n5EA==}
-
-  reftools@1.1.9:
-    resolution: {integrity: sha512-OVede/NQE13xBQ+ob5CKd5KyeJYU2YInb1bmV4nRoOfquZPkAkxuOXicSe1PvqIuZZ4kD13sPKBbR7UFDmli6w==}
-
-  regenerate-unicode-properties@10.2.2:
-    resolution: {integrity: sha512-m03P+zhBeQd1RGnYxrGyDAPpWX/epKirLrp8e3qevZdVkKtnCrjjWczIbYc8+xd6vcTStVlqfycTx1KR4LOr0g==}
-    engines: {node: '>=4'}
-
-  regenerate@1.4.2:
-    resolution: {integrity: sha512-zrceR/XhGYU/d/opr2EKO7aRHUeiBI8qjtfHqADTwZd6Szfy16la6kqD0MIUs5z5hx6AaKa+PixpPrR289+I0A==}
-
-  regexpu-core@6.4.0:
-    resolution: {integrity: sha512-0ghuzq67LI9bLXpOX/ISfve/Mq33a4aFRzoQYhnnok1JOFpmE/A2TBGkNVenOGEeSBCjIiWcc6MVOG5HEQv0sA==}
-    engines: {node: '>=4'}
-
-  registry-auth-token@5.1.1:
-    resolution: {integrity: sha512-P7B4+jq8DeD2nMsAcdfaqHbssgHtZ7Z5+++a5ask90fvmJ8p5je4mOa+wzu+DB4vQ5tdJV/xywY+UnVFeQLV5Q==}
-    engines: {node: '>=14'}
-
-  registry-url@6.0.1:
-    resolution: {integrity: sha512-+crtS5QjFRqFCoQmvGduwYWEBng99ZvmFvF+cUJkGYF1L1BfU8C6Zp9T7f5vPAwyLkUExpvK+ANVZmGU49qi4Q==}
-    engines: {node: '>=12'}
-
-  regjsgen@0.8.0:
-    resolution: {integrity: sha512-RvwtGe3d7LvWiDQXeQw8p5asZUmfU1G/l6WbUXeHta7Y2PEIvBTwH6E2EfmYUK8pxcxEdEmaomqyp0vZZ7C+3Q==}
-
-  regjsparser@0.13.1:
-    resolution: {integrity: sha512-dLsljMd9sqwRkby8zhO1gSg3PnJIBFid8f4CQj/sXx+7cKx+E7u0PKhZ+U4wmhx7EfmtvnA318oVaIkAB1lRJw==}
-    hasBin: true
-
-  rehype-katex@7.0.1:
-    resolution: {integrity: sha512-OiM2wrZ/wuhKkigASodFoo8wimG3H12LWQaH8qSPVJn9apWKFSH3YOCtbKpBorTVw/eI7cuT21XBbvwEswbIOA==}
-
-  rehype-raw@7.0.0:
-    resolution: {integrity: sha512-/aE8hCfKlQeA8LmyeyQvQF3eBiLRGNlfBJEvWH7ivp9sBqs7TNqBL5X3v157rM4IFETqDnIOO+z5M/biZbo9Ww==}
-
-  rehype-recma@1.0.0:
-    resolution: {integrity: sha512-lqA4rGUf1JmacCNWWZx0Wv1dHqMwxzsDWYMTowuplHF3xH0N/MmrZ/G3BDZnzAkRmxDadujCjaKM2hqYdCBOGw==}
-
-  relateurl@0.2.7:
-    resolution: {integrity: sha512-G08Dxvm4iDN3MLM0EsP62EDV9IuhXPR6blNz6Utcp7zyV3tr4HVNINt6MpaRWbxoOHT3Q7YN2P+jaHX8vUbgog==}
-    engines: {node: '>= 0.10'}
-
-  remark-directive@3.0.1:
-    resolution: {integrity: sha512-gwglrEQEZcZYgVyG1tQuA+h58EZfq5CSULw7J90AFuCTyib1thgHPoqQ+h9iFvU6R+vnZ5oNFQR5QKgGpk741A==}
-
-  remark-emoji@4.0.1:
-    resolution: {integrity: sha512-fHdvsTR1dHkWKev9eNyhTo4EFwbUvJ8ka9SgeWkMPYFX4WoI7ViVBms3PjlQYgw5TLvNQso3GUB/b/8t3yo+dg==}
-    engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
-
-  remark-frontmatter@3.0.0:
-    resolution: {integrity: sha512-mSuDd3svCHs+2PyO29h7iijIZx4plX0fheacJcAoYAASfgzgVIcXGYSq9GFyYocFLftQs8IOmmkgtOovs6d4oA==}
-
-  remark-frontmatter@5.0.0:
-    resolution: {integrity: sha512-XTFYvNASMe5iPN0719nPrdItC9aU0ssC4v14mH1BCi1u0n1gAocqcujWUrByftZTbLhRtiKRyjYTSIOcr69UVQ==}
-
-  remark-gfm@1.0.0:
-    resolution: {integrity: sha512-KfexHJCiqvrdBZVbQ6RopMZGwaXz6wFJEfByIuEwGf0arvITHjiKKZ1dpXujjH9KZdm1//XJQwgfnJ3lmXaDPA==}
-
-  remark-gfm@4.0.1:
-    resolution: {integrity: sha512-1quofZ2RQ9EWdeN34S79+KExV1764+wCUGop5CPL1WGdD0ocPpu91lzPGbwWMECpEpd42kJGQwzRfyov9j4yNg==}
-
-  remark-math@6.0.0:
-    resolution: {integrity: sha512-MMqgnP74Igy+S3WwnhQ7kqGlEerTETXMvJhrUzDikVZ2/uogJCb+WHUg97hK9/jcfc0dkD73s3LN8zU49cTEtA==}
-
-  remark-mdx@3.1.1:
-    resolution: {integrity: sha512-Pjj2IYlUY3+D8x00UJsIOg5BEvfMyeI+2uLPn9VO9Wg4MEtN/VTIq2NEJQfde9PnX15KgtHyl9S0BcTnWrIuWg==}
-
-  remark-parse@10.0.2:
-    resolution: {integrity: sha512-3ydxgHa/ZQzG8LvC7jTXccARYDcRld3VfcgIIFs7bI6vbRSxJJmzgLEIIoYKyrfhaY+ujuWaf/PJiMZXoiCXgw==}
-
-  remark-parse@11.0.0:
-    resolution: {integrity: sha512-FCxlKLNGknS5ba/1lmpYijMUzX2esxW5xQqjWxw2eHFfS2MSdaHVINFmhjo+qN1WhZhNimq0dZATN9pH0IDrpA==}
-
-  remark-parse@9.0.0:
-    resolution: {integrity: sha512-geKatMwSzEXKHuzBNU1z676sGcDcFoChMK38TgdHJNAYfFtsfHDQG7MoJAjs6sgYMqyLduCYWDIWZIxiPeafEw==}
-
-  remark-rehype@10.1.0:
-    resolution: {integrity: sha512-EFmR5zppdBp0WQeDVZ/b66CWJipB2q2VLNFMabzDSGR66Z2fQii83G5gTBbgGEnEEA0QRussvrFHxk1HWGJskw==}
-
-  remark-rehype@11.1.2:
-    resolution: {integrity: sha512-Dh7l57ianaEoIpzbp0PC9UKAdCSVklD8E5Rpw7ETfbTl3FqcOOgq5q2LVDhgGCkaBv7p24JXikPdvhhmHvKMsw==}
-
-  remark-stringify@11.0.0:
-    resolution: {integrity: sha512-1OSmLd3awB/t8qdoEOMazZkNsfVTeY4fTsgzcQFdXNq8ToTN4ZGwrMnlda4K6smTFKD+GRV6O48i6Z4iKgPPpw==}
-
-  remark-stringify@9.0.1:
-    resolution: {integrity: sha512-mWmNg3ZtESvZS8fv5PTvaPckdL4iNlCHTt8/e/8oN08nArHRHjNZMKzA/YW3+p7/lYqIw4nx1XsjCBo/AxNChg==}
-
-  renderkid@3.0.0:
-    resolution: {integrity: sha512-q/7VIQA8lmM1hF+jn+sFSPWGlMkSAeNYcPLmDQx2zzuiDfaLrOmumR8iaUKlenFgh0XRPIUeSPlH3A+AW3Z5pg==}
-
-  repeat-string@1.6.1:
-    resolution: {integrity: sha512-PV0dzCYDNfRi1jCDbJzpW7jNNDRuCOG/jI5ctQcGKt/clZD+YcPS3yIlWuTJMmESC8aevCFmWJy5wjAFgNqN6w==}
-    engines: {node: '>=0.10'}
-
-  require-directory@2.1.1:
-    resolution: {integrity: sha512-fGxEI7+wsG9xrvdjsrlmL22OMTTiHRwAMroiEeMgq8gzoLC/PQr7RsRDSTLUg/bZAZtF+TVIkHc6/4RIKrui+Q==}
-    engines: {node: '>=0.10.0'}
-
-  require-from-string@2.0.2:
-    resolution: {integrity: sha512-Xf0nWe6RseziFMu+Ap9biiUbmplq6S9/p+7w7YXP/JBHhrUDDUhwa+vANyubuqfZWTveU//DYVGsDG7RKL/vEw==}
-    engines: {node: '>=0.10.0'}
-
-  require-like@0.1.2:
-    resolution: {integrity: sha512-oyrU88skkMtDdauHDuKVrgR+zuItqr6/c//FXzvmxRGMexSDc6hNvJInGW3LL46n+8b50RykrvwSUIIQH2LQ5A==}
-
-  requires-port@1.0.0:
-    resolution: {integrity: sha512-KigOCHcocU3XODJxsu8i/j8T9tzT4adHiecwORRQ0ZZFcp7ahwXuRU1m+yuO90C5ZUyGeGfocHDI14M3L3yDAQ==}
-
-  reselect@5.2.0:
-    resolution: {integrity: sha512-AgZ3UOZm3YndfrJ4OYjgrT7bmCm/1iqkjvEfH/oYjzh6PD2qw4QuT3jjnXIrpdt4MTpMXclMT3lXbmRY+XRakw==}
-
-  resize-observer-polyfill@1.5.1:
-    resolution: {integrity: sha512-LwZrotdHOo12nQuZlHEmtuXdqGoOD0OhaxopaNFxWzInpEgaLWoVuAMbTzixuosCx2nEG58ngzW3vxdWoxIgdg==}
-
-  resolve-alpn@1.2.1:
-    resolution: {integrity: sha512-0a1F4l73/ZFZOakJnQ3FvkJ2+gSTQWz/r2KE5OdDY0TxPm5h4GkqkWWfM47T7HsbnOtcJVEF4epCVy6u7Q3K+g==}
-
-  resolve-from@4.0.0:
-    resolution: {integrity: sha512-pb/MYmXstAkysRFx8piNI1tGFNQIFA3vkE3Gq4EuA1dF6gHp/+vgZqsCGJapvy8N3Q+4o7FwvquPJcnZ7RYy4g==}
-    engines: {node: '>=4'}
-
-  resolve-pathname@3.0.0:
-    resolution: {integrity: sha512-C7rARubxI8bXFNB/hqcp/4iUeIXJhJZvFPFPiSPRnhU5UPxzMFIl+2E6yY6c4k9giDJAhtV+enfA+G89N6Csng==}
-
-  resolve@1.22.12:
-    resolution: {integrity: sha512-TyeJ1zif53BPfHootBGwPRYT1RUt6oGWsaQr8UyZW/eAm9bKoijtvruSDEmZHm92CwS9nj7/fWttqPCgzep8CA==}
-    engines: {node: '>= 0.4'}
-    hasBin: true
-
-  responselike@3.0.0:
-    resolution: {integrity: sha512-40yHxbNcl2+rzXvZuVkrYohathsSJlMTXKryG5y8uciHv1+xDLHQpgjG64JUO9nrEq2jGLH6IZ8BcZyw3wrweg==}
-    engines: {node: '>=14.16'}
-
-  retry@0.13.1:
-    resolution: {integrity: sha512-XQBQ3I8W1Cge0Seh+6gjj03LbmRFWuoszgK9ooCpwYIrhhoO80pfq4cUkU5DkknwfOfFteRwlZ56PYOGYyFWdg==}
-    engines: {node: '>= 4'}
-
-  reusify@1.1.0:
-    resolution: {integrity: sha512-g6QUff04oZpHs0eG5p83rFLhHeV00ug/Yf9nZM6fLeUrPguBTkTQOdpAWWspMh55TZfVQDPaN3NQJfbVRAxdIw==}
-    engines: {iojs: '>=1.0.0', node: '>=0.10.0'}
-
-  robust-predicates@3.0.3:
-    resolution: {integrity: sha512-NS3levdsRIUOmiJ8FZWCP7LG3QpJyrs/TE0Zpf1yvZu8cAJJ6QMW92H1c7kWpdIHo8RvmLxN/o2JXTKHp74lUA==}
-
-  roughjs@4.6.6:
-    resolution: {integrity: sha512-ZUz/69+SYpFN/g/lUlo2FXcIjRkSu3nDarreVdGGndHEBJ6cXPdKguS8JGxwj5HA5xIbVKSmLgr5b3AWxtRfvQ==}
-
-  rtl-css-js@1.16.1:
-    resolution: {integrity: sha512-lRQgou1mu19e+Ya0LsTvKrVJ5TYUbqCVPAiImX3UfLTenarvPUl1QFdvu5Z3PYmHT9RCcwIfbjRQBntExyj3Zg==}
-
-  rtlcss@4.3.0:
-    resolution: {integrity: sha512-FI+pHEn7Wc4NqKXMXFM+VAYKEj/mRIcW4h24YVwVtyjI+EqGrLc2Hx/Ny0lrZ21cBWU2goLy36eqMcNj3AQJig==}
-    engines: {node: '>=12.0.0'}
-    hasBin: true
-
-  run-applescript@7.1.0:
-    resolution: {integrity: sha512-DPe5pVFaAsinSaV6QjQ6gdiedWDcRCbUuiQfQa2wmWV7+xC9bGulGI8+TdRmoFkAPaBXk8CrAbnlY2ISniJ47Q==}
-    engines: {node: '>=18'}
-
-  run-parallel@1.2.0:
-    resolution: {integrity: sha512-5l4VyZR86LZ/lDxZTR6jqL8AFE2S0IFLMP26AbjsLVADxHdhB/c0GUsH+y39UfCi3dzz8OlQuPmnaJOMoDHQBA==}
-
-  rw@1.3.3:
-    resolution: {integrity: sha512-PdhdWy89SiZogBLaw42zdeqtRJ//zFd2PgQavcICDUgJT5oW10QCRKbJ6bg4r0/UY2M6BWd5tkxuGFRvCkgfHQ==}
-
-  sade@1.8.1:
-    resolution: {integrity: sha512-xal3CZX1Xlo/k4ApwCFrHVACi9fBqJ7V+mwhBsuf/1IOKbBy098Fex+Wa/5QMubw09pSZ/u8EY8PWgevJsXp1A==}
-    engines: {node: '>=6'}
-
-  safe-buffer@5.1.2:
-    resolution: {integrity: sha512-Gd2UZBJDkXlY7GbJxfsE8/nvKkUEU1G38c1siN6QP6a9PT9MmHB8GnpscSmMJSoF8LOIrt8ud/wPtojys4G6+g==}
-
-  safe-buffer@5.2.1:
-    resolution: {integrity: sha512-rp3So07KcdmmKbGvgaNxQSJr7bGVSVk5S9Eq1F+ppbRo70+YeaDxkw5Dd8NPN+GD6bjnYm2VuPuCXmpuYvmCXQ==}
-
-  safe-stable-stringify@1.1.1:
-    resolution: {integrity: sha512-ERq4hUjKDbJfE4+XtZLFPCDi8Vb1JqaxAPTxWFLBx8XcAlf9Bda/ZJdVezs/NAfsMQScyIlUMx+Yeu7P7rx5jw==}
-
-  safer-buffer@2.1.2:
-    resolution: {integrity: sha512-YZo3K82SD7Riyi0E1EQPojLz7kpepnSQI9IyPbHHg1XXXevb5dJI7tpyN2ADxGcQbHG7vcyRHk0cbwqcQriUtg==}
-
-  sass-loader@16.0.8:
-    resolution: {integrity: sha512-hcov4ZwZJIGbEuyNr9EmiTmZueyrxSToE6GOzoZnq5JM7ecRO7ttyvilPn+VmRsqiP16+VYZzVnGZj/hzZgKBA==}
-    engines: {node: '>= 18.12.0'}
-    peerDependencies:
-      '@rspack/core': 0.x || ^1.0.0 || ^2.0.0-0
-      node-sass: ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0 || ^9.0.0
-      sass: ^1.3.0
-      sass-embedded: '*'
-      webpack: ^5.0.0
-    peerDependenciesMeta:
-      '@rspack/core':
-        optional: true
-      node-sass:
-        optional: true
-      sass:
-        optional: true
-      sass-embedded:
-        optional: true
-      webpack:
-        optional: true
-
-  sass@1.101.0:
-    resolution: {integrity: sha512-OL3GoQyoUdDt843DpVmDO6y2k1sc5IhUDSpu8XucEI+35neq5QivZ1iuegnpraEVTJXlQGK1gl27zKcTLEPbQw==}
-    engines: {node: '>=20.19.0'}
-    hasBin: true
-
-  sax@1.6.0:
-    resolution: {integrity: sha512-6R3J5M4AcbtLUdZmRv2SygeVaM7IhrLXu9BmnOGmmACak8fiUtOsYNWUS4uK7upbmHIBbLBeFeI//477BKLBzA==}
-    engines: {node: '>=11.0.0'}
-
-  scheduler@0.27.0:
-    resolution: {integrity: sha512-eNv+WrVbKu1f3vbYJT/xtiF5syA5HPIMtf9IgY/nKg0sWqzAUEvqY/xm7OcZc/qafLx/iO9FgOmeSAp4v5ti/Q==}
-
-  schema-dts@1.1.5:
-    resolution: {integrity: sha512-RJr9EaCmsLzBX2NDiO5Z3ux2BVosNZN5jo0gWgsyKvxKIUL5R3swNvoorulAeL9kLB0iTSX7V6aokhla2m7xbg==}
-
-  schema-utils@3.3.0:
-    resolution: {integrity: sha512-pN/yOAvcC+5rQ5nERGuwrjLlYvLTbCibnZ1I7B1LaiAz9BRBlE9GMgE/eqV30P7aJQUf7Ddimy/RsbYO/GrVGg==}
-    engines: {node: '>= 10.13.0'}
-
-  schema-utils@4.3.3:
-    resolution: {integrity: sha512-eflK8wEtyOE6+hsaRVPxvUKYCpRgzLqDTb8krvAsRIwOGlHoSgYLgBXoubGgLd2fT41/OUYdb48v4k4WWHQurA==}
-    engines: {node: '>= 10.13.0'}
-
-  screenfull@5.2.0:
-    resolution: {integrity: sha512-9BakfsO2aUQN2K9Fdbj87RJIEZ82Q9IGim7FqM5OsebfoFC6ZHXgDq/KvniuLTPdeM8wY2o6Dj3WQ7KeQCj3cA==}
-    engines: {node: '>=0.10.0'}
-
-  search-insights@2.17.3:
-    resolution: {integrity: sha512-RQPdCYTa8A68uM2jwxoY842xDhvx3E5LFL1LxvxCNMev4o5mLuokczhzjAgGwUZBAmOKZknArSxLKmXtIi2AxQ==}
-
-  section-matter@1.0.0:
-    resolution: {integrity: sha512-vfD3pmTzGpufjScBh50YHKzEu2lxBWhVEHsNGoEXmCmn2hKGfeNLYMzCJpe8cD7gqX7TJluOVpBkAequ6dgMmA==}
-    engines: {node: '>=4'}
-
-  select-hose@2.0.0:
-    resolution: {integrity: sha512-mEugaLK+YfkijB4fx0e6kImuJdCIt2LxCRcbEYPqRGCs4F2ogyfZU5IAZRdjCP8JPq2AtdNoC/Dux63d9Kiryg==}
-
-  selfsigned@5.5.0:
-    resolution: {integrity: sha512-ftnu3TW4+3eBfLRFnDEkzGxSF/10BJBkaLJuBHZX0kiPS7bRdlpZGu6YGt4KngMkdTwJE6MbjavFpqHvqVt+Ew==}
-    engines: {node: '>=18'}
-
-  semver-diff@4.0.0:
-    resolution: {integrity: sha512-0Ju4+6A8iOnpL/Thra7dZsSlOHYAHIeMxfhWQRI1/VLcT3WDBZKKtQt/QkBOsiIN9ZpuvHE6cGZ0x4glCMmfiA==}
-    engines: {node: '>=12'}
-
-  semver@6.3.1:
-    resolution: {integrity: sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==}
-    hasBin: true
-
-  semver@7.7.1:
-    resolution: {integrity: sha512-hlq8tAfn0m/61p4BVRcPzIGr6LKiMwo4VM6dGi6pt4qcRkmNzTcWq6eCEjEh+qXjkMDvPlOFFSGwQjoEa6gyMA==}
-    engines: {node: '>=10'}
-    hasBin: true
-
-  semver@7.8.3:
-    resolution: {integrity: sha512-wnilbGyMxzbY7dNOl7jpKbLSjcfeweJWU5j4+u5qW+6/wuGD9KzIGOyZnQVSBM9E7DtWaaH3CyHkppYrKYoxwg==}
-    engines: {node: '>=10'}
-    hasBin: true
-
-  semver@7.8.5:
-    resolution: {integrity: sha512-Y7/KDsb8LjooZpwaqGyulO6DQlksgCncchHGk+sZIY4SBvUocMBEFH5Ur1fI4dV+Jvl0w6cjvucaIi40puRioA==}
-    engines: {node: '>=10'}
-    hasBin: true
-
-  send@0.19.2:
-    resolution: {integrity: sha512-VMbMxbDeehAxpOtWJXlcUS5E8iXh6QmN+BkRX1GARS3wRaXEEgzCcB10gTQazO42tpNIya8xIyNx8fll1OFPrg==}
-    engines: {node: '>= 0.8.0'}
-
-  serialize-javascript@6.0.2:
-    resolution: {integrity: sha512-Saa1xPByTTq2gdeFZYLLo+RFE35NHZkAbqZeWNd3BpzppeVisAqpDjcp8dyf6uIvEqJRd46jemmyA4iFIeVk8g==}
-
-  serve-handler@6.1.7:
-    resolution: {integrity: sha512-CinAq1xWb0vR3twAv9evEU8cNWkXCb9kd5ePAHUKJBkOsUpR1wt/CvGdeca7vqumL1U5cSaeVQ6zZMxiJ3yWsg==}
-
-  serve-index@1.9.2:
-    resolution: {integrity: sha512-KDj11HScOaLmrPxl70KYNW1PksP4Nb/CLL2yvC+Qd2kHMPEEpfc4Re2e4FOay+bC/+XQl/7zAcWON3JVo5v3KQ==}
-    engines: {node: '>= 0.8.0'}
-
-  serve-static@1.16.3:
-    resolution: {integrity: sha512-x0RTqQel6g5SY7Lg6ZreMmsOzncHFU7nhnRWkKgWuMTu5NN0DR5oruckMqRvacAN9d5w6ARnRBXl9xhDCgfMeA==}
-    engines: {node: '>= 0.8.0'}
-
-  set-function-length@1.2.2:
-    resolution: {integrity: sha512-pgRc4hJ4/sNjWCSS9AmnS40x3bNMDTknHgL5UaMBTMyJnU90EgWh1Rz+MC9eFu4BuN/UwZjKQuY/1v3rM7HMfg==}
-    engines: {node: '>= 0.4'}
-
-  set-harmonic-interval@1.0.1:
-    resolution: {integrity: sha512-AhICkFV84tBP1aWqPwLZqFvAwqEoVA9kxNMniGEUvzOlm4vLmOFLiTT3UZ6bziJTy4bOVpzWGTfSCbmaayGx8g==}
-    engines: {node: '>=6.9'}
-
-  setprototypeof@1.2.0:
-    resolution: {integrity: sha512-E5LDX7Wrp85Kil5bhZv46j8jOeboKq5JMmYM3gVGdGH8xFpPWXUMsNrlODCrkoxMEeNi/XZIwuRvY4XNwYMJpw==}
-
-  shallow-clone@3.0.1:
-    resolution: {integrity: sha512-/6KqX+GVUdqPuPPd2LxDDxzX6CAbjJehAAOKlNpqqUpAqPM6HeL8f+o3a+JsyGjn2lv0WY8UsTgUJjU9Ok55NA==}
-    engines: {node: '>=8'}
-
-  shallowequal@1.1.0:
-    resolution: {integrity: sha512-y0m1JoUZSlPAjXVtPPW70aZWfIL/dSP7AFkRnniLCrK/8MDKog3TySTBmckD+RObVxH0v4Tox67+F14PdED2oQ==}
-
-  shebang-command@2.0.0:
-    resolution: {integrity: sha512-kHxr2zZpYtdmrN1qDjrrX/Z1rR1kG8Dx+gkpK1G4eXmvXswmcE1hTWBWYUzlraYw1/yZp6YuDY77YtvbN0dmDA==}
-    engines: {node: '>=8'}
-
-  shebang-regex@3.0.0:
-    resolution: {integrity: sha512-7++dFhtcx3353uBaq8DDR4NuxBetBzC7ZQOhmTQInHEd6bSrXdiEyzCvG07Z44UYdLShWUyXt5M/yhz8ekcb1A==}
-    engines: {node: '>=8'}
-
-  shell-quote@1.8.4:
-    resolution: {integrity: sha512-VsC6n6vz1ihYYyZZwX7YZSF5l5x36ca17OC+a69h94YqB7X6XLwf+5MOgynYir2SLFUbl8gIYvBo8K8RoNQ6bQ==}
-    engines: {node: '>= 0.4'}
-
-  shelljs@0.8.5:
-    resolution: {integrity: sha512-TiwcRcrkhHvbrZbnRcFYMLl30Dfov3HKqzp5tO5b4pt6G/SezKcYhmDg15zXVBswHmctSAQKznqNW2LO5tTDow==}
-    engines: {node: '>=4'}
-    hasBin: true
-
-  should-equal@2.0.0:
-    resolution: {integrity: sha512-ZP36TMrK9euEuWQYBig9W55WPC7uo37qzAEmbjHz4gfyuXrEUgF8cUvQVO+w+d3OMfPvSRQJ22lSm8MQJ43LTA==}
-
-  should-format@3.0.3:
-    resolution: {integrity: sha512-hZ58adtulAk0gKtua7QxevgUaXTTXxIi8t41L3zo9AHvjXO1/7sdLECuHeIN2SRtYXpNkmhoUP2pdeWgricQ+Q==}
-
-  should-type-adaptors@1.1.0:
-    resolution: {integrity: sha512-JA4hdoLnN+kebEp2Vs8eBe9g7uy0zbRo+RMcU0EsNy+R+k049Ki+N5tT5Jagst2g7EAja+euFuoXFCa8vIklfA==}
-
-  should-type@1.4.0:
-    resolution: {integrity: sha512-MdAsTu3n25yDbIe1NeN69G4n6mUnJGtSJHygX3+oN0ZbO3DTiATnf7XnYJdGT42JCXurTb1JI0qOBR65shvhPQ==}
-
-  should-util@1.0.1:
-    resolution: {integrity: sha512-oXF8tfxx5cDk8r2kYqlkUJzZpDBqVY/II2WhvU0n9Y3XYvAYRmeaf1PvvIvTgPnv4KJ+ES5M0PyDq5Jp+Ygy2g==}
-
-  should@13.2.3:
-    resolution: {integrity: sha512-ggLesLtu2xp+ZxI+ysJTmNjh2U0TsC+rQ/pfED9bUZZ4DKefP27D+7YJVVTvKsmjLpIi9jAa7itwDGkDDmt1GQ==}
-
-  side-channel-list@1.0.1:
-    resolution: {integrity: sha512-mjn/0bi/oUURjc5Xl7IaWi/OJJJumuoJFQJfDDyO46+hBWsfaVM65TBHq2eoZBhzl9EchxOijpkbRC8SVBQU0w==}
-    engines: {node: '>= 0.4'}
-
-  side-channel-map@1.0.1:
-    resolution: {integrity: sha512-VCjCNfgMsby3tTdo02nbjtM/ewra6jPHmpThenkTYh8pG9ucZ/1P8So4u4FGBek/BjpOVsDCMoLA/iuBKIFXRA==}
-    engines: {node: '>= 0.4'}
-
-  side-channel-weakmap@1.0.2:
-    resolution: {integrity: sha512-WPS/HvHQTYnHisLo9McqBHOJk2FkHO/tlpvldyrnem4aeQp4hai3gythswg6p01oSoTl58rcpiFAjF2br2Ak2A==}
-    engines: {node: '>= 0.4'}
-
-  side-channel@1.1.1:
-    resolution: {integrity: sha512-6x6dK6zJdpTzF4sQeNYxwtvBzf6Eg4GtlesS94HOvTudUeyK2WXAaIfmDgsyslYrRBeFIlsi54AYsFGUuhmvrQ==}
-    engines: {node: '>= 0.4'}
-
-  signal-exit@3.0.7:
-    resolution: {integrity: sha512-wnD2ZE+l+SPC/uoS0vXeE9L1+0wuaMqKlfz9AMUo38JsyLSBWSFcHR1Rri62LZc12vLr1gb3jl7iwQhgwpAbGQ==}
-
-  sirv@2.0.4:
-    resolution: {integrity: sha512-94Bdh3cC2PKrbgSOUqTiGPWVZeSiXfKOVZNJniWoqrWrRkB1CJzBU3NEbiTsPcYy1lDsANA/THzS+9WBiy5nfQ==}
-    engines: {node: '>= 10'}
-
-  sisteransi@1.0.5:
-    resolution: {integrity: sha512-bLGGlR1QxBcynn2d5YmDX4MGjlZvy2MRBDRNHLJ8VI6l6+9FUiyTFNJ0IveOSP0bcXgVDPRcfGqA0pjaqUpfVg==}
-
-  sitemap@7.1.3:
-    resolution: {integrity: sha512-tAjEd+wt/YwnEbfNB2ht51ybBJxbEWwe5ki/Z//Wh0rpBFTCUSj46GnxUKEWzhfuJTsee8x3lybHxFgUMig2hw==}
-    engines: {node: '>=12.0.0', npm: '>=5.6.0'}
-    hasBin: true
-
-  skin-tone@2.0.0:
-    resolution: {integrity: sha512-kUMbT1oBJCpgrnKoSr0o6wPtvRWT9W9UKvGLwfJYO2WuahZRHOpEyL1ckyMGgMWh0UdpmaoFqKKD29WTomNEGA==}
-    engines: {node: '>=8'}
-
-  slash@3.0.0:
-    resolution: {integrity: sha512-g9Q1haeby36OSStwb4ntCGGGaKsaVSjQ68fBxoQcutl5fS1vuY18H3wSt3jFyFtrkx+Kz0V1G85A4MyAdDMi2Q==}
-    engines: {node: '>=8'}
-
-  slash@4.0.0:
-    resolution: {integrity: sha512-3dOsAHXXUkQTpOYcoAxLIorMTp4gIQr5IW3iVb7A7lFIp0VHhnynm9izx6TssdrIcVIESAlVjtnO2K8bg+Coew==}
-    engines: {node: '>=12'}
-
-  slugify@1.6.9:
-    resolution: {integrity: sha512-vZ7rfeehZui7wQs438JXBckYLkIIdfHOXsaVEUMyS5fHo1483l1bMdo0EDSWYclY0yZKFOipDy4KHuKs6ssvdg==}
-    engines: {node: '>=8.0.0'}
-
-  snake-case@3.0.4:
-    resolution: {integrity: sha512-LAOh4z89bGQvl9pFfNF8V146i7o7/CqFPbqzYgP+yYzDIDeS9HaNFtXABamRW+AQzEVODcvE79ljJ+8a9YSdMg==}
-
-  sockjs@0.3.24:
-    resolution: {integrity: sha512-GJgLTZ7vYb/JtPSSZ10hsOYIvEYsjbNU+zPdIHcUaWVNUEPivzxku31865sSSud0Da0W4lEeOPlmw93zLQchuQ==}
-
-  sort-css-media-queries@2.2.0:
-    resolution: {integrity: sha512-0xtkGhWCC9MGt/EzgnvbbbKhqWjl1+/rncmhTh5qCpbYguXh6S/qwePfv/JQ8jePXXmqingylxoC49pCkSPIbA==}
-    engines: {node: '>= 6.3.0'}
-
-  source-map-js@1.2.1:
-    resolution: {integrity: sha512-UXWMKhLOwVKb728IUtQPXxfYU+usdybtUrK/8uGE8CQMvrhOpwvzDBwj0QhSL7MQc7vIsISBG8VQ8+IDQxpfQA==}
-    engines: {node: '>=0.10.0'}
-
-  source-map-support@0.5.21:
-    resolution: {integrity: sha512-uBHU3L3czsIyYXKX88fdrGovxdSCoTGDRZ6SYXtSRxLZUzHg5P/66Ht6uoUlHu9EZod+inXhKo3qQgwXUT/y1w==}
-
-  source-map@0.5.6:
-    resolution: {integrity: sha512-MjZkVp0NHr5+TPihLcadqnlVoGIoWo4IBHptutGh9wI3ttUYvCG26HkSuDi+K6lsZ25syXJXcctwgyVCt//xqA==}
-    engines: {node: '>=0.10.0'}
-
-  source-map@0.6.1:
-    resolution: {integrity: sha512-UjgapumWlbMhkBgzT7Ykc5YXUT46F0iKu8SGXq0bcwP5dz/h0Plj6enJqjz1Zbq2l5WaqYnrVbwWOWMyF3F47g==}
-    engines: {node: '>=0.10.0'}
-
-  source-map@0.7.6:
-    resolution: {integrity: sha512-i5uvt8C3ikiWeNZSVZNWcfZPItFQOsYTUAOkcUPGd8DqDy1uOUikjt5dG+uRlwyvR108Fb9DOd4GvXfT0N2/uQ==}
-    engines: {node: '>= 12'}
-
-  space-separated-tokens@1.1.5:
-    resolution: {integrity: sha512-q/JSVd1Lptzhf5bkYm4ob4iWPjx0KiRe3sRFBNrVqbJkFaBm5vbbowy1mymoPNLRa52+oadOhJ+K49wsSeSjTA==}
-
-  space-separated-tokens@2.0.2:
-    resolution: {integrity: sha512-PEGlAwrG8yXGXRjW32fGbg66JAlOAwbObuqVoJpv/mRgoWDQfgH1wDPvtzWyUSNAXBGSk8h755YDbbcEy3SH2Q==}
-
-  spdy-transport@3.0.0:
-    resolution: {integrity: sha512-hsLVFE5SjA6TCisWeJXFKniGGOpBgMLmerfO2aCyCU5s7nJ/rpAepqmFifv/GCbSbueEeAJJnmSQ2rKC/g8Fcw==}
-
-  spdy@4.0.2:
-    resolution: {integrity: sha512-r46gZQZQV+Kl9oItvl1JZZqJKGr+oEkB08A6BzkiR7593/7IbtuncXHd2YoYeTsG4157ZssMu9KYvUHLcjcDoA==}
-    engines: {node: '>=6.0.0'}
-
-  sprintf-js@1.0.3:
-    resolution: {integrity: sha512-D9cPgkvLlV3t3IzL0D0YLvGA9Ahk4PcvVwUbN0dSGr1aP0Nrt4AEnTUbuGvquEC0mA64Gqt1fzirlRs5ibXx8g==}
-
-  srcset@4.0.0:
-    resolution: {integrity: sha512-wvLeHgcVHKO8Sc/H/5lkGreJQVeYMm9rlmt8PuR1xE31rIuXhuzznUUqAt8MqLhB3MqJdFzlNAfpcWnxiFUcPw==}
-    engines: {node: '>=12'}
-
-  stack-generator@2.0.10:
-    resolution: {integrity: sha512-mwnua/hkqM6pF4k8SnmZ2zfETsRUpWXREfA/goT8SLCV4iOFa4bzOX2nDipWAZFPTjLvQB82f5yaodMVhK0yJQ==}
-
-  stackframe@1.3.4:
-    resolution: {integrity: sha512-oeVtt7eWQS+Na6F//S4kJ2K2VbRlS9D43mAlMyVpVWovy9o+jfgH8O9agzANzaiLjclA0oYzUXEM4PurhSUChw==}
-
-  stacktrace-gps@3.1.2:
-    resolution: {integrity: sha512-GcUgbO4Jsqqg6RxfyTHFiPxdPqF+3LFmQhm7MgCuYQOYuWyqxo5pwRPz5d/u6/WYJdEnWfK4r+jGbyD8TSggXQ==}
-
-  stacktrace-js@2.0.2:
-    resolution: {integrity: sha512-Je5vBeY4S1r/RnLydLl0TBTi3F2qdfWmYsGvtfZgEI+SCprPppaIhQf5nGcal4gI4cGpCV/duLcAzT1np6sQqg==}
-
-  statuses@1.5.0:
-    resolution: {integrity: sha512-OpZ3zP+jT1PI7I8nemJX4AKmAX070ZkYPVWV/AaKTJl+tXCTGyVdC1a4SL8RUQYEwk/f34ZX8UTykN68FwrqAA==}
-    engines: {node: '>= 0.6'}
-
-  statuses@2.0.2:
-    resolution: {integrity: sha512-DvEy55V3DB7uknRo+4iOGT5fP1slR8wQohVdknigZPMpMstaKJQWhwiYBACJE3Ul2pTnATihhBYnRhZQHGBiRw==}
-    engines: {node: '>= 0.8'}
-
-  std-env@3.10.0:
-    resolution: {integrity: sha512-5GS12FdOZNliM5mAOxFRg7Ir0pWz8MdpYm6AY6VPkGpbA7ZzmbzNcBJQ0GPvvyWgcY7QAhCgf9Uy89I03faLkg==}
-
-  string-width@4.2.3:
-    resolution: {integrity: sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==}
-    engines: {node: '>=8'}
-
-  string-width@5.1.2:
-    resolution: {integrity: sha512-HnLOCR3vjcY8beoNLtcjZ5/nxn2afmME6lhrDrebokqMap+XbeW8n9TXpPDOqdGK5qcI3oT0GKTW6wC7EMiVqA==}
-    engines: {node: '>=12'}
-
-  string-width@7.2.0:
-    resolution: {integrity: sha512-tsaTIkKW9b4N+AEj+SVA+WhJzV7/zMhcSu78mLKWSk7cXMOSHsBKFWUs0fWwq8QyK3MgJBQRX6Gbi4kYbdvGkQ==}
-    engines: {node: '>=18'}
-
-  string_decoder@1.1.1:
-    resolution: {integrity: sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg==}
-
-  string_decoder@1.3.0:
-    resolution: {integrity: sha512-hkRX8U1WjJFd8LsDJ2yQ/wWWxaopEsABU1XfkM8A+j0+85JAGppt16cr1Whg6KIbb4okU6Mql6BOj+uup/wKeA==}
-
-  stringify-entities@4.0.4:
-    resolution: {integrity: sha512-IwfBptatlO+QCJUo19AqvrPNqlVMpW9YEL2LIVY+Rpv2qsjCGxaDLNRgeGsQWJhfItebuJhsGSLjaBbNSQ+ieg==}
-
-  stringify-object@3.3.0:
-    resolution: {integrity: sha512-rHqiFh1elqCQ9WPLIC8I0Q/g/wj5J1eMkyoiD6eoQApWHP0FtlK7rqnhmabL5VUY9JQCcqwwvlOaSuutekgyrw==}
-    engines: {node: '>=4'}
-
-  strip-ansi@6.0.1:
-    resolution: {integrity: sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==}
-    engines: {node: '>=8'}
-
-  strip-ansi@7.2.0:
-    resolution: {integrity: sha512-yDPMNjp4WyfYBkHnjIRLfca1i6KMyGCtsVgoKe/z1+6vukgaENdgGBZt+ZmKPc4gavvEZ5OgHfHdrazhgNyG7w==}
-    engines: {node: '>=12'}
-
-  strip-bom-string@1.0.0:
-    resolution: {integrity: sha512-uCC2VHvQRYu+lMh4My/sFNmF2klFymLX1wHJeXnbEJERpV/ZsVuonzerjfrGpIGF7LBVa1O7i9kjiWvJiFck8g==}
-    engines: {node: '>=0.10.0'}
-
-  strip-final-newline@2.0.0:
-    resolution: {integrity: sha512-BrpvfNAE3dcvq7ll3xVumzjKjZQ5tI1sEUIKr3Uoks0XUl45St3FlatVqef9prk4jRDzhW6WZg+3bk93y6pLjA==}
-    engines: {node: '>=6'}
-
-  strip-json-comments@2.0.1:
-    resolution: {integrity: sha512-4gB8na07fecVVkOI6Rs4e7T6NOTki5EmL7TUduTs6bu3EdnSycntVJ4re8kgZA+wx9IueI2Y11bfbgwtzuE0KQ==}
-    engines: {node: '>=0.10.0'}
-
-  strip-json-comments@3.1.1:
-    resolution: {integrity: sha512-6fPc+R4ihwqP6N/aIv2f1gMH8lOVtWQHoqC4yK6oSDVVocumAsfCqjkXnqiYMhmMwS/mEHLp7Vehlt3ql6lEig==}
-    engines: {node: '>=8'}
-
-  style-to-js@1.1.21:
-    resolution: {integrity: sha512-RjQetxJrrUJLQPHbLku6U/ocGtzyjbJMP9lCNK7Ag0CNh690nSH8woqWH9u16nMjYBAok+i7JO1NP2pOy8IsPQ==}
-
-  style-to-object@0.4.4:
-    resolution: {integrity: sha512-HYNoHZa2GorYNyqiCaBgsxvcJIn7OHq6inEga+E6Ke3m5JkoqpQbnFssk4jwe+K7AhGa2fcha4wSOf1Kn01dMg==}
-
-  style-to-object@1.0.14:
-    resolution: {integrity: sha512-LIN7rULI0jBscWQYaSswptyderlarFkjQ+t79nzty8tcIAceVomEVlLzH5VP4Cmsv6MtKhs7qaAiwlcp+Mgaxw==}
-
-  stylehacks@6.1.1:
-    resolution: {integrity: sha512-gSTTEQ670cJNoaeIp9KX6lZmm8LJ3jPB5yJmX8Zq/wQxOsAFXV3qjWzHas3YYk1qesuVIyYWWUpZ0vSE/dTSGg==}
-    engines: {node: ^14 || ^16 || >=18.0}
-    peerDependencies:
-      postcss: ^8.4.31
-
-  stylis@4.4.0:
-    resolution: {integrity: sha512-5Z9ZpRzfuH6l/UAvCPAPUo3665Nk2wLaZU3x+TLHKVzIz33+sbJqbtrYoC3KD4/uVOr2Zp+L0LySezP9OHV9yA==}
-
-  sucrase@3.35.1:
-    resolution: {integrity: sha512-DhuTmvZWux4H1UOnWMB3sk0sbaCVOoQZjv8u1rDoTV0HTdGem9hkAZtl4JZy8P2z4Bg0nT+YMeOFyVr4zcG5Tw==}
-    engines: {node: '>=16 || 14 >=14.17'}
-    hasBin: true
-
-  supports-color@7.2.0:
-    resolution: {integrity: sha512-qpCAvRl9stuOHveKsn7HncJRvv501qIacKzQlO/+Lwxc9+0q2wLyv4Dfvt80/DPn2pqOBsJdDiogXGR9+OvwRw==}
-    engines: {node: '>=8'}
-
-  supports-color@8.1.1:
-    resolution: {integrity: sha512-MpUEN2OodtUzxvKQl72cUF7RQ5EiHsGvSsVG0ia9c5RbWGL2CI4C7EpPS8UTBIplnlzZiNuV56w+FuNxy3ty2Q==}
-    engines: {node: '>=10'}
-
-  supports-preserve-symlinks-flag@1.0.0:
-    resolution: {integrity: sha512-ot0WnXS9fgdkgIcePe6RHNk1WA8+muPa6cSjeR3V8K27q9BB1rTE3R1p7Hv0z1ZyAc8s6Vvv8DIyWf681MAt0w==}
-    engines: {node: '>= 0.4'}
-
-  svg-parser@2.0.4:
-    resolution: {integrity: sha512-e4hG1hRwoOdRb37cIMSgzNsxyzKfayW6VOflrwvR+/bzrkyxY/31WkbgnQpgtrNp1SdpJvpUAGTa/ZoiPNDuRQ==}
-
-  svgo@3.3.3:
-    resolution: {integrity: sha512-+wn7I4p7YgJhHs38k2TNjy1vCfPIfLIJWR5MnCStsN8WuuTcBnRKcMHQLMM2ijxGZmDoZwNv8ipl5aTTen62ng==}
-    engines: {node: '>=14.0.0'}
-    hasBin: true
-
-  swagger2openapi@7.0.8:
-    resolution: {integrity: sha512-upi/0ZGkYgEcLeGieoz8gT74oWHA0E7JivX7aN9mAf+Tc7BQoRBvnIGHoPDw+f9TXTW4s6kGYCZJtauP6OYp7g==}
-    hasBin: true
-
-  swc-loader@0.2.7:
-    resolution: {integrity: sha512-nwYWw3Fh9ame3Rtm7StS9SBLpHRRnYcK7bnpF3UKZmesAK0gw2/ADvlURFAINmPvKtDLzp+GBiP9yLoEjg6S9w==}
-    peerDependencies:
-      '@swc/core': ^1.2.147
-      webpack: '>=2'
-
-  tapable@2.3.3:
-    resolution: {integrity: sha512-uxc/zpqFg6x7C8vOE7lh6Lbda8eEL9zmVm/PLeTPBRhh1xCgdWaQ+J1CUieGpIfm2HdtsUpRv+HshiasBMcc6A==}
-    engines: {node: '>=6'}
-
-  terser-webpack-plugin@5.6.1:
-    resolution: {integrity: sha512-201R5j+sJpK8nFWwKVyNfZot8FaJbLZDq5evriVzbV1wDtSXDjRUDRfJzHpAaxFDMEhsZL1QkeqM61wgsS3KaQ==}
-    engines: {node: '>= 10.13.0'}
-    peerDependencies:
-      '@minify-html/node': '*'
-      '@swc/core': '*'
-      '@swc/css': '*'
-      '@swc/html': '*'
-      clean-css: '*'
-      cssnano: '*'
-      csso: '*'
-      esbuild: '*'
-      html-minifier-terser: '*'
-      lightningcss: '*'
-      postcss: '*'
-      uglify-js: '*'
-      webpack: ^5.1.0
-    peerDependenciesMeta:
-      '@minify-html/node':
-        optional: true
-      '@swc/core':
-        optional: true
-      '@swc/css':
-        optional: true
-      '@swc/html':
-        optional: true
-      clean-css:
-        optional: true
-      cssnano:
-        optional: true
-      csso:
-        optional: true
-      esbuild:
-        optional: true
-      html-minifier-terser:
-        optional: true
-      lightningcss:
-        optional: true
-      postcss:
-        optional: true
-      uglify-js:
-        optional: true
-
-  terser@5.48.0:
-    resolution: {integrity: sha512-J/9An6vs9Us6wKRriSFXBWdRZapREHqFzdNUKk0pmu804EMR6dr6winwo7e5JDxN4xahxQsuysyYFwlwj4XN/Q==}
-    engines: {node: '>=10'}
-    hasBin: true
-
-  thenify-all@1.6.0:
-    resolution: {integrity: sha512-RNxQH/qI8/t3thXJDwcstUO4zeqo64+Uy/+sNVRBx4Xn2OX+OZ9oP+iJnNFqplFra2ZUVeKCSa2oVWi3T4uVmA==}
-    engines: {node: '>=0.8'}
-
-  thenify@3.3.1:
-    resolution: {integrity: sha512-RVZSIV5IG10Hk3enotrhvz0T9em6cyHBLkH/YAZuKqd8hRkKhSfCGIcP2KUY0EPxndzANBmNllzWPwak+bheSw==}
-
-  thingies@2.6.0:
-    resolution: {integrity: sha512-rMHRjmlFLM1R96UYPvpmnc3LYtdFrT33JIB7L9hetGue1qAPfn1N2LJeEjxUSidu1Iku+haLZXDuEXUHNGO/lg==}
-    engines: {node: '>=10.18'}
-    peerDependencies:
-      tslib: ^2
-
-  throttle-debounce@3.0.1:
-    resolution: {integrity: sha512-dTEWWNu6JmeVXY0ZYoPuH5cRIwc0MeGbJwah9KUNYSJwommQpCzTySTpEe8Gs1J23aeWEuAobe4Ag7EHVt/LOg==}
-    engines: {node: '>=10'}
-
-  thunky@1.1.0:
-    resolution: {integrity: sha512-eHY7nBftgThBqOyHGVN+l8gF0BucP09fMo0oO/Lb0w1OF80dJv+lDVpXG60WMQvkcxAkNybKsrEIE3ZtKGmPrA==}
-
-  tiny-invariant@1.3.3:
-    resolution: {integrity: sha512-+FbBPE1o9QAYvviau/qC5SE3caw21q3xkvWKBtja5vgqOWIHHJ3ioaq1VPfn/Szqctz2bU/oYeKd9/z5BL+PVg==}
-
-  tiny-warning@1.0.3:
-    resolution: {integrity: sha512-lBN9zLN/oAf68o3zNXYrdCt1kP8WsiGW8Oo2ka41b2IM5JL/S1CTyX1rW0mb/zSuJun0ZUrDxx4sqvYS2FWzPA==}
-
-  tinyexec@1.2.4:
-    resolution: {integrity: sha512-SHf/r48b7vOrjve9PxJo3MN5v5yuyjHvdUcrQffT3WXMUfnGmHDVbC4k3sHJaJTgZCwpUplIaAo5ANtMyp3YHg==}
-    engines: {node: '>=18'}
-
-  tinyglobby@0.2.17:
-    resolution: {integrity: sha512-wXR/dYpcqKmfWpEdZjiKJOwCNFndD0DMnrW/cYjVGttEkBfVgcLFHoNrlj47mjOVic9yyNu65alsgF4NQyTa2g==}
-    engines: {node: '>=12.0.0'}
-
-  tinypool@1.1.1:
-    resolution: {integrity: sha512-Zba82s87IFq9A9XmjiX5uZA/ARWDrB03OHlq+Vw1fSdt0I+4/Kutwy8BP4Y/y/aORMo61FQ0vIb5j44vSo5Pkg==}
-    engines: {node: ^18.0.0 || >=20.0.0}
-
-  to-regex-range@5.0.1:
-    resolution: {integrity: sha512-65P7iz6X5yEr1cwcgvQxbbIw7Uk3gOy5dIdtZ4rDveLqhrdJP+Li/Hx6tyK0NEb+2GCyneCMJiGqrADCSNk8sQ==}
-    engines: {node: '>=8.0'}
-
-  toggle-selection@1.0.6:
-    resolution: {integrity: sha512-BiZS+C1OS8g/q2RRbJmy59xpyghNBqrr6k5L/uKBGRsTfxmu3ffiRnd8mlGPUVayg8pvfi5urfnu8TU7DVOkLQ==}
-
-  toidentifier@1.0.1:
-    resolution: {integrity: sha512-o5sSPKEkg/DIQNmH43V0/uerLrpzVedkUh8tGNvaeXpfpuwjKenlSox/2O/BTlZUtEe+JG7s5YhEz608PlAHRA==}
-    engines: {node: '>=0.6'}
-
-  totalist@3.0.1:
-    resolution: {integrity: sha512-sf4i37nQ2LBx4m3wB74y+ubopq6W/dIzXg0FDGjsYnZHVa1Da8FH853wlL2gtUhg+xJXjfk3kUZS3BRoQeoQBQ==}
-    engines: {node: '>=6'}
-
-  tr46@0.0.3:
-    resolution: {integrity: sha512-N3WMsuqV66lT30CrXNbEjx4GEwlow3v6rr4mCcv6prnfwhS01rkgyFdjPNBYd9br7LpXV1+Emh01fHnq2Gdgrw==}
-
-  tree-dump@1.1.0:
-    resolution: {integrity: sha512-rMuvhU4MCDbcbnleZTFezWsaZXRFemSqAM+7jPnzUl1fo9w3YEKOxAeui0fz3OI4EU4hf23iyA7uQRVko+UaBA==}
-    engines: {node: '>=10.0'}
-    peerDependencies:
-      tslib: '2'
-
-  trim-lines@3.0.1:
-    resolution: {integrity: sha512-kRj8B+YHZCc9kQYdWfJB2/oUl9rA99qbowYYBtr4ui4mZyAQ2JpvVBd/6U2YloATfqBhBTSMhTpgBHtU0Mf3Rg==}
-
-  trough@1.0.5:
-    resolution: {integrity: sha512-rvuRbTarPXmMb79SmzEp8aqXNKcK+y0XaB298IXueQ8I2PsrATcPBCSPyK/dDNa2iWOhKlfNnOjdAOTBU/nkFA==}
-
-  trough@2.2.0:
-    resolution: {integrity: sha512-tmMpK00BjZiUyVyvrBK7knerNgmgvcV/KLVyuma/SC+TQN167GrMRciANTz09+k3zW8L8t60jWO1GpfkZdjTaw==}
-
-  ts-algebra@1.2.2:
-    resolution: {integrity: sha512-kloPhf1hq3JbCPOTYoOWDKxebWjNb2o/LKnNfkWhxVVisFFmMJPPdJeGoGmM+iRLyoXAR61e08Pb+vUXINg8aA==}
-
-  ts-api-utils@1.4.3:
-    resolution: {integrity: sha512-i3eMG77UTMD0hZhgRS562pv83RC6ukSAC2GMNWc+9dieh/+jDM5u5YG+NHX6VNDRHQcHwmsTHctP9LhbC3WxVw==}
-    engines: {node: '>=16'}
-    peerDependencies:
-      typescript: '>=4.2.0'
-
-  ts-dedent@2.2.0:
-    resolution: {integrity: sha512-q5W7tVM71e2xjHZTlgfTDoPF/SmqKG5hddq9SzR49CH2hayqRKJtQ4mtRlSxKaJlR/+9rEM+mnBHf7I2/BQcpQ==}
-    engines: {node: '>=6.10'}
-
-  ts-easing@0.2.0:
-    resolution: {integrity: sha512-Z86EW+fFFh/IFB1fqQ3/+7Zpf9t2ebOAxNI/V6Wo7r5gqiqtxmgTlQ1qbqQcjLKYeSHPTsEmvlJUDg/EuL0uHQ==}
-
-  ts-interface-checker@0.1.13:
-    resolution: {integrity: sha512-Y/arvbn+rrz3JCKl9C4kVNfTfSm2/mEp5FSz5EsZSANGPSlQrpRI5M4PKF+mJnE52jOO90PnPSc3Ur3bTQw0gA==}
-
-  ts-keycode-enum@1.0.6:
-    resolution: {integrity: sha512-DF8+Cf/FJJnPRxwz8agCoDelQXKZWQOS/gnnwx01nZ106tPJdB3BgJ9QTtLwXgR82D8O+nTjuZzWgf0Rg4vuRA==}
-
-  tslib@1.14.1:
-    resolution: {integrity: sha512-Xni35NKzjgMrwevysHTCArtLDpPvye8zV/0E4EyYn43P7/7qvQwPh9BGkHewbMulVntbigmcT7rdX3BNo9wRJg==}
-
-  tslib@2.8.1:
-    resolution: {integrity: sha512-oJFu94HQb+KVduSUQL7wnpmqnfmLsOA/nAh6b6EH0wCEoK0/mPeXU6c3wKDV83MkOuHPRHtSXKKU99IBazS/2w==}
-
-  tsutils@3.21.0:
-    resolution: {integrity: sha512-mHKK3iUXL+3UF6xL5k0PEhKRUBKPBCv/+RkEOpjRWxxx27KKRBmmA60A9pgOUvMi8GKhRMPEmjBRPzs2W7O1OA==}
-    engines: {node: '>= 6'}
-    peerDependencies:
-      typescript: '>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta'
-
-  tsyringe@4.10.0:
-    resolution: {integrity: sha512-axr3IdNuVIxnaK5XGEUFTu3YmAQ6lllgrvqfEoR16g/HGnYY/6We4oWENtAnzK6/LpJ2ur9PAb80RBt7/U4ugw==}
-    engines: {node: '>= 6.0.0'}
-
-  type-check@0.4.0:
-    resolution: {integrity: sha512-XleUoc9uwGXqjWwXaUTZAmzMcFZ5858QA2vvx1Ur5xIcixXIP+8LnFDgRplU30us6teqdlskFfu+ae4K79Ooew==}
-    engines: {node: '>= 0.8.0'}
-
-  type-fest@1.4.0:
-    resolution: {integrity: sha512-yGSza74xk0UG8k+pLh5oeoYirvIiWo5t0/o3zHHAO2tRDiZcxWP7fywNlXhqb6/r6sWvwi+RsyQMWhVLe4BVuA==}
-    engines: {node: '>=10'}
-
-  type-fest@2.19.0:
-    resolution: {integrity: sha512-RAH822pAdBgcNMAfWnCBU3CFZcfZ/i1eZjwFU/dsLKumyuuP3niueg2UAukXYF0E2AAoc82ZSSf9J0WQBinzHA==}
-    engines: {node: '>=12.20'}
-
-  type-is@1.6.18:
-    resolution: {integrity: sha512-TkRKr9sUTxEH8MdfuCSP7VizJyzRNMjj2J2do2Jr3Kym598JVdEksuzPQCnlFPW4ky9Q+iA+ma9BGm06XQBy8g==}
-    engines: {node: '>= 0.6'}
-
-  typedarray-to-buffer@3.1.5:
-    resolution: {integrity: sha512-zdu8XMNEDepKKR+XYOXAVPtWui0ly0NtohUscw+UmaHiAWT8hrV1rr//H6V+0DvJ3OQ19S979M0laLfX8rm82Q==}
-
-  typescript@6.0.3:
-    resolution: {integrity: sha512-y2TvuxSZPDyQakkFRPZHKFm+KKVqIisdg9/CZwm9ftvKXLP8NRWj38/ODjNbr43SsoXqNuAisEf1GdCxqWcdBw==}
-    engines: {node: '>=14.17'}
-    hasBin: true
-
-  undici-types@7.24.6:
-    resolution: {integrity: sha512-WRNW+sJgj5OBN4/0JpHFqtqzhpbnV0GuB+OozA9gCL7a993SmU+1JBZCzLNxYsbMfIeDL+lTsphD5jN5N+n0zg==}
-
-  unicode-canonical-property-names-ecmascript@2.0.1:
-    resolution: {integrity: sha512-dA8WbNeb2a6oQzAQ55YlT5vQAWGV9WXOsi3SskE3bcCdM0P4SDd+24zS/OCacdRq5BkdsRj9q3Pg6YyQoxIGqg==}
-    engines: {node: '>=4'}
-
-  unicode-emoji-modifier-base@1.0.0:
-    resolution: {integrity: sha512-yLSH4py7oFH3oG/9K+XWrz1pSi3dfUrWEnInbxMfArOfc1+33BlGPQtLsOYwvdMy11AwUBetYuaRxSPqgkq+8g==}
-    engines: {node: '>=4'}
-
-  unicode-match-property-ecmascript@2.0.0:
-    resolution: {integrity: sha512-5kaZCrbp5mmbz5ulBkDkbY0SsPOjKqVS35VpL9ulMPfSl0J0Xsm+9Evphv9CoIZFwre7aJoa94AY6seMKGVN5Q==}
-    engines: {node: '>=4'}
-
-  unicode-match-property-value-ecmascript@2.2.1:
-    resolution: {integrity: sha512-JQ84qTuMg4nVkx8ga4A16a1epI9H6uTXAknqxkGF/aFfRLw1xC/Bp24HNLaZhHSkWd3+84t8iXnp1J0kYcZHhg==}
-    engines: {node: '>=4'}
-
-  unicode-property-aliases-ecmascript@2.2.0:
-    resolution: {integrity: sha512-hpbDzxUY9BFwX+UeBnxv3Sh1q7HFxj48DTmXchNgRa46lO8uj3/1iEn3MiNUYTg1g9ctIqXCCERn8gYZhHC5lQ==}
-    engines: {node: '>=4'}
-
-  unified@10.1.2:
-    resolution: {integrity: sha512-pUSWAi/RAnVy1Pif2kAoeWNBa3JVrx0MId2LASj8G+7AiHWoKZNTomq6LG326T68U7/e263X6fTdcXIy7XnF7Q==}
-
-  unified@11.0.5:
-    resolution: {integrity: sha512-xKvGhPWw3k84Qjh8bI3ZeJjqnyadK+GEFtazSfZv/rKeTkTjOJho6mFqh2SM96iIcZokxiOpg78GazTSg8+KHA==}
-
-  unified@9.2.2:
-    resolution: {integrity: sha512-Sg7j110mtefBD+qunSLO1lqOEKdrwBFBrR6Qd8f4uwkhWNlbkaqwHse6e7QvD3AP/MNoJdEDLaf8OxYyoWgorQ==}
-
-  unique-string@3.0.0:
-    resolution: {integrity: sha512-VGXBUVwxKMBUznyffQweQABPRRW1vHZAbadFZud4pLFAqRGvv/96vafgjWFqzourzr8YonlQiPgH0YCJfawoGQ==}
-    engines: {node: '>=12'}
-
-  unist-builder@3.0.1:
-    resolution: {integrity: sha512-gnpOw7DIpCA0vpr6NqdPvTWnlPTApCTRzr+38E6hCWx3rz/cjo83SsKIlS1Z+L5ttScQ2AwutNnb8+tAvpb6qQ==}
-
-  unist-util-find-after@5.0.0:
-    resolution: {integrity: sha512-amQa0Ep2m6hE2g72AugUItjbuM8X8cGQnFoHk0pGfrFeT9GZhzN5SW8nRsiGKK7Aif4CrACPENkA6P/Lw6fHGQ==}
-
-  unist-util-generated@2.0.1:
-    resolution: {integrity: sha512-qF72kLmPxAw0oN2fwpWIqbXAVyEqUzDHMsbtPvOudIlUzXYFIeQIuxXQCRCFh22B7cixvU0MG7m3MW8FTq/S+A==}
-
-  unist-util-is@4.1.0:
-    resolution: {integrity: sha512-ZOQSsnce92GrxSqlnEEseX0gi7GH9zTJZ0p9dtu87WRb/37mMPO2Ilx1s/t9vBHrFhbgweUwb+t7cIn5dxPhZg==}
-
-  unist-util-is@5.2.1:
-    resolution: {integrity: sha512-u9njyyfEh43npf1M+yGKDGVPbY/JWEemg5nH05ncKPfi+kBbKBJoTdsogMu33uhytuLlv9y0O7GH7fEdwLdLQw==}
-
-  unist-util-is@6.0.1:
-    resolution: {integrity: sha512-LsiILbtBETkDz8I9p1dQ0uyRUWuaQzd/cuEeS1hoRSyW5E5XGmTzlwY1OrNzzakGowI9Dr/I8HVaw4hTtnxy8g==}
-
-  unist-util-position-from-estree@2.0.0:
-    resolution: {integrity: sha512-KaFVRjoqLyF6YXCbVLNad/eS4+OfPQQn2yOd7zF/h5T/CSL2v8NpN6a5TPvtbXthAGw5nG+PuTtq+DdIZr+cRQ==}
-
-  unist-util-position@4.0.4:
-    resolution: {integrity: sha512-kUBE91efOWfIVBo8xzh/uZQ7p9ffYRtUbMRZBNFYwf0RK8koUMx6dGUfwylLOKmaT2cs4wSW96QoYUSXAyEtpg==}
-
-  unist-util-position@5.0.0:
-    resolution: {integrity: sha512-fucsC7HjXvkB5R3kTCO7kUjRdrS0BJt3M/FPxmHMBOm8JQi2BsHAHFsy27E0EolP8rp0NzXsJ+jNPyDWvOJZPA==}
-
-  unist-util-remove-position@5.0.0:
-    resolution: {integrity: sha512-Hp5Kh3wLxv0PHj9m2yZhhLt58KzPtEYKQQ4yxfYFEO7EvHwzyDYnduhHnY1mDxoqr7VUwVuHXk9RXKIiYS1N8Q==}
-
-  unist-util-select@4.0.3:
-    resolution: {integrity: sha512-1074+K9VyR3NyUz3lgNtHKm7ln+jSZXtLJM4E22uVuoFn88a/Go2pX8dusrt/W+KWH1ncn8jcd8uCQuvXb/fXA==}
-
-  unist-util-stringify-position@2.0.3:
-    resolution: {integrity: sha512-3faScn5I+hy9VleOq/qNbAd6pAx7iH5jYBMS9I1HgQVijz/4mv5Bvw5iw1sC/90CODiKo81G/ps8AJrISn687g==}
-
-  unist-util-stringify-position@3.0.3:
-    resolution: {integrity: sha512-k5GzIBZ/QatR8N5X2y+drfpWG8IDBzdnVj6OInRNWm1oXrzydiaAT2OQiA8DPRRZyAKb9b6I2a6PxYklZD0gKg==}
-
-  unist-util-stringify-position@4.0.0:
-    resolution: {integrity: sha512-0ASV06AAoKCDkS2+xw5RXJywruurpbC4JZSm7nr7MOt1ojAzvyyaO+UxZf18j8FCF6kmzCZKcAgN/yu2gm2XgQ==}
-
-  unist-util-visit-parents@3.1.1:
-    resolution: {integrity: sha512-1KROIZWo6bcMrZEwiH2UrXDyalAa0uqzWCxCJj6lPOvTve2WkfgCytoDTPaMnodXh1WrXOq0haVYHj99ynJlsg==}
-
-  unist-util-visit-parents@4.1.1:
-    resolution: {integrity: sha512-1xAFJXAKpnnJl8G7K5KgU7FY55y3GcLIXqkzUj5QF/QVP7biUm0K0O2oqVkYsdjzJKifYeWn9+o6piAK2hGSHw==}
-
-  unist-util-visit-parents@5.1.3:
-    resolution: {integrity: sha512-x6+y8g7wWMyQhL1iZfhIPhDAs7Xwbn9nRosDXl7qoPTSCy0yNxnKc+hWokFifWQIDGi154rdUqKvbCa4+1kLhg==}
-
-  unist-util-visit-parents@6.0.2:
-    resolution: {integrity: sha512-goh1s1TBrqSqukSc8wrjwWhL0hiJxgA8m4kFxGlQ+8FYQ3C/m11FcTs4YYem7V664AhHVvgoQLk890Ssdsr2IQ==}
-
-  unist-util-visit@3.1.0:
-    resolution: {integrity: sha512-Szoh+R/Ll68QWAyQyZZpQzZQm2UPbxibDvaY8Xc9SUtYgPsDzx5AWSk++UUt2hJuow8mvwR+rG+LQLw+KsuAKA==}
-
-  unist-util-visit@4.1.2:
-    resolution: {integrity: sha512-MSd8OUGISqHdVvfY9TPhyK2VdUrPgxkUtWSuMHF6XAAFuL4LokseigBnZtPnJMu+FbynTkFNnFlyjxpVKujMRg==}
-
-  unist-util-visit@5.1.0:
-    resolution: {integrity: sha512-m+vIdyeCOpdr/QeQCu2EzxX/ohgS8KbnPDgFni4dQsfSCtpz8UqDyY5GjRru8PDKuYn7Fq19j1CQ+nJSsGKOzg==}
-
-  universalify@2.0.1:
-    resolution: {integrity: sha512-gptHNQghINnc/vTGIk0SOFGFNXw7JVrlRUtConJRlvaw6DuX0wO5Jeko9sWrMBhh+PsYAZ7oXAiOnf/UKogyiw==}
-    engines: {node: '>= 10.0.0'}
-
-  unpipe@1.0.0:
-    resolution: {integrity: sha512-pjy2bYhSsufwWlKwPc+l3cN7+wuJlK6uz0YdJEOlQDbl6jo/YlPi4mb8agUkVC8BF7V8NuzeyPNqRksA3hztKQ==}
-    engines: {node: '>= 0.8'}
-
-  update-browserslist-db@1.2.3:
-    resolution: {integrity: sha512-Js0m9cx+qOgDxo0eMiFGEueWztz+d4+M3rGlmKPT+T4IS/jP4ylw3Nwpu6cpTTP8R1MAC1kF4VbdLt3ARf209w==}
-    hasBin: true
-    peerDependencies:
-      browserslist: '>= 4.21.0'
-
-  update-notifier@6.0.2:
-    resolution: {integrity: sha512-EDxhTEVPZZRLWYcJ4ZXjGFN0oP7qYvbXWzEgRm/Yql4dHX5wDbvh89YHP6PK1lzZJYrMtXUuZZz8XGK+U6U1og==}
-    engines: {node: '>=14.16'}
-
-  uri-js@4.4.1:
-    resolution: {integrity: sha512-7rKUyy33Q1yc98pQ1DAmLtwX109F7TIfWlW1Ydo8Wl1ii1SeHieeh0HHfPeL2fMXK6z0s8ecKs9frCuLJvndBg==}
-
-  url-loader@4.1.1:
-    resolution: {integrity: sha512-3BTV812+AVHHOJQO8O5MkWgZ5aosP7GnROJwvzLS9hWDj00lZ6Z0wNak423Lp9PBZN05N+Jk/N5Si8jRAlGyWA==}
-    engines: {node: '>= 10.13.0'}
-    peerDependencies:
-      file-loader: '*'
-      webpack: ^4.0.0 || ^5.0.0
-    peerDependenciesMeta:
-      file-loader:
-        optional: true
-
-  url@0.11.4:
-    resolution: {integrity: sha512-oCwdVC7mTuWiPyjLUz/COz5TLk6wgp0RCsN+wHZ2Ekneac9w8uuV0njcbbie2ME+Vs+d6duwmYuR3HgQXs1fOg==}
-    engines: {node: '>= 0.4'}
-
-  use-editable@2.3.3:
-    resolution: {integrity: sha512-7wVD2JbfAFJ3DK0vITvXBdpd9JAz5BcKAAolsnLBuBn6UDDwBGuCIAGvR3yA2BNKm578vAMVHFCWaOcA+BhhiA==}
-    peerDependencies:
-      react: '>= 16.8.0'
-
-  use-resize-observer@9.1.0:
-    resolution: {integrity: sha512-R25VqO9Wb3asSD4eqtcxk8sJalvIOYBqS8MNZlpDSQ4l4xMQxC/J7Id9HoTqPq8FwULIn0PVW+OAqF2dyYbjow==}
-    peerDependencies:
-      react: 16.8.0 - 18
-      react-dom: 16.8.0 - 18
-
-  use-sync-external-store@1.6.0:
-    resolution: {integrity: sha512-Pp6GSwGP/NrPIrxVFAIkOQeyw8lFenOHijQWkUTrDvrF4ALqylP2C/KCkeS9dpUM3KvYRQhna5vt7IL95+ZQ9w==}
-    peerDependencies:
-      react: ^16.8.0 || ^17.0.0 || ^18.0.0 || ^19.0.0
-
-  util-deprecate@1.0.2:
-    resolution: {integrity: sha512-EPD5q1uXyFxJpCrLnCc1nHnq3gOa6DZBocAIiI2TaSCA7VCJ1UJDMagCzIkXNsUYfD1daK//LTEQ8xiIbrHtcw==}
-
-  utila@0.4.0:
-    resolution: {integrity: sha512-Z0DbgELS9/L/75wZbro8xAnT50pBVFQZ+hUEueGDU5FN51YSCYM+jdxsfCiHjwNP/4LCDD0i/graKpeBnOXKRA==}
-
-  utility-types@3.11.0:
-    resolution: {integrity: sha512-6Z7Ma2aVEWisaL6TvBCy7P8rm2LQoPv6dJ7ecIaIixHcwfbJ0x7mWdbcwlIM5IGQxPZSFYeqRCqlOOeKoJYMkw==}
-    engines: {node: '>= 4'}
-
-  utils-merge@1.0.1:
-    resolution: {integrity: sha512-pMZTvIkT1d+TFGvDOqodOclx0QWkkgi6Tdoa8gC8ffGAAqz9pzPTZWAybbsHHoED/ztMtkv/VoYTYyShUn81hA==}
-    engines: {node: '>= 0.4.0'}
-
-  uuid@14.0.1:
-    resolution: {integrity: sha512-6ZxzVpzDXDa3bJWaHilVayA+BH/1zmxCJoVgvmqJnid/gPoKHxUrS/aC/T6LGQtNHT+XHG9fXPJB4d+IrU30Ew==}
-    hasBin: true
-
-  uuid@8.3.2:
-    resolution: {integrity: sha512-+NYs2QeMWy+GWFOEm9xnn6HCDp0l7QBD7ml8zLUmJ+93Q5NF0NocErnwkTkXVFNiX3/fpC6afS8Dhb/gz7R7eg==}
-    deprecated: uuid@10 and below is no longer supported.  For ESM codebases, update to uuid@latest.  For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).
-    hasBin: true
-
-  uvu@0.5.6:
-    resolution: {integrity: sha512-+g8ENReyr8YsOc6fv/NVJs2vFdHBnBNdfE49rshrTzDWOlUx4Gq7KOS2GD8eqhy2j+Ejq29+SbKH8yjkAqXqoA==}
-    engines: {node: '>=8'}
-    hasBin: true
-
-  validate.io-array@1.0.6:
-    resolution: {integrity: sha512-DeOy7CnPEziggrOO5CZhVKJw6S3Yi7e9e65R1Nl/RTN1vTQKnzjfvks0/8kQ40FP/dsjRAOd4hxmJ7uLa6vxkg==}
-
-  validate.io-function@1.0.2:
-    resolution: {integrity: sha512-LlFybRJEriSuBnUhQyG5bwglhh50EpTL2ul23MPIuR1odjO7XaMLFV8vHGwp7AZciFxtYOeiSCT5st+XSPONiQ==}
-
-  validate.io-integer-array@1.0.0:
-    resolution: {integrity: sha512-mTrMk/1ytQHtCY0oNO3dztafHYyGU88KL+jRxWuzfOmQb+4qqnWmI+gykvGp8usKZOM0H7keJHEbRaFiYA0VrA==}
-
-  validate.io-integer@1.0.5:
-    resolution: {integrity: sha512-22izsYSLojN/P6bppBqhgUDjCkr5RY2jd+N2a3DCAUey8ydvrZ/OkGvFPR7qfOpwR2LC5p4Ngzxz36g5Vgr/hQ==}
-
-  validate.io-number@1.0.3:
-    resolution: {integrity: sha512-kRAyotcbNaSYoDnXvb4MHg/0a1egJdLwS6oJ38TJY7aw9n93Fl/3blIXdyYvPOp55CNxywooG/3BcrwNrBpcSg==}
-
-  value-equal@1.0.1:
-    resolution: {integrity: sha512-NOJ6JZCAWr0zlxZt+xqCHNTEKOsrks2HQd4MqhP1qy4z1SkbEP467eNx6TgDKXMvUOb+OENfJCZwM+16n7fRfw==}
-
-  vary@1.1.2:
-    resolution: {integrity: sha512-BNGbWLfd0eUPabhkXUVm0j8uuvREyTh5ovRa/dyow/BqAbZJyC+5fU+IzQOzmAKzYqYRAISoRhdQr3eIZ/PXqg==}
-    engines: {node: '>= 0.8'}
-
-  vfile-location@4.1.0:
-    resolution: {integrity: sha512-YF23YMyASIIJXpktBa4vIGLJ5Gs88UB/XePgqPmTa7cDA+JeO3yclbpheQYCHjVHBn/yePzrXuygIL+xbvRYHw==}
-
-  vfile-location@5.0.3:
-    resolution: {integrity: sha512-5yXvWDEgqeiYiBe1lbxYF7UMAIm/IcopxMHrMQDq3nvKcjPKIhZklUKL+AE7J7uApI4kwe2snsK+eI6UTj9EHg==}
-
-  vfile-message@2.0.4:
-    resolution: {integrity: sha512-DjssxRGkMvifUOJre00juHoP9DPWuzjxKuMDrhNbk2TdaYYBNMStsNhEOt3idrtI12VQYM/1+iM0KOzXi4pxwQ==}
-
-  vfile-message@3.1.4:
-    resolution: {integrity: sha512-fa0Z6P8HUrQN4BZaX05SIVXic+7kE3b05PWAtPuYP9QLHsLKYR7/AlLW3NtOrpXRLeawpDLMsVkmk5DG0NXgWw==}
-
-  vfile-message@4.0.3:
-    resolution: {integrity: sha512-QTHzsGd1EhbZs4AsQ20JX1rC3cOlt/IWJruk893DfLRr57lcnOeMaWG4K0JrRta4mIJZKth2Au3mM3u03/JWKw==}
-
-  vfile@4.2.1:
-    resolution: {integrity: sha512-O6AE4OskCG5S1emQ/4gl8zK586RqA3srz3nfK/Viy0UPToBc5Trp9BVFb1u0CjsKrAWwnpr4ifM/KBXPWwJbCA==}
-
-  vfile@5.3.7:
-    resolution: {integrity: sha512-r7qlzkgErKjobAmyNIkkSpizsFPYiUPuJb5pNW1RB4JcYVZhs4lIbVqk8XPk033CV/1z8ss5pkax8SuhGpcG8g==}
-
-  vfile@6.0.3:
-    resolution: {integrity: sha512-KzIbH/9tXat2u30jf+smMwFCsno4wHVdNmzFyL+T/L3UGqqk6JKfVqOFOZEpZSHADH1k40ab6NUIXZq422ov3Q==}
-
-  warning@4.0.3:
-    resolution: {integrity: sha512-rpJyN222KWIvHJ/F53XSZv0Zl/accqHR8et1kpaMTD/fLCRxtV8iX8czMzY7sVZupTI3zcUTg8eycS2kNF9l6w==}
-
-  watchpack@2.5.1:
-    resolution: {integrity: sha512-Zn5uXdcFNIA1+1Ei5McRd+iRzfhENPCe7LeABkJtNulSxjma+l7ltNx55BWZkRlwRnpOgHqxnjyaDgJnNXnqzg==}
-    engines: {node: '>=10.13.0'}
-
-  wbuf@1.7.3:
-    resolution: {integrity: sha512-O84QOnr0icsbFGLS0O3bI5FswxzRr8/gHwWkDlQFskhSPryQXvrTMxjxGP4+iWYoauLoBvfDpkrOauZ+0iZpDA==}
-
-  web-namespaces@2.0.1:
-    resolution: {integrity: sha512-bKr1DkiNa2krS7qxNtdrtHAmzuYGFQLiQ13TsorsdT6ULTkPLKuu5+GsFpDlg6JFjUTwX2DyhMPG2be8uPrqsQ==}
-
-  webidl-conversions@3.0.1:
-    resolution: {integrity: sha512-2JAn3z8AR6rjK8Sm8orRC0h/bcl/DqL7tRPdGZ4I1CjdF+EaMLmYxBHyXuKL849eucPFhvBoxMsflfOb8kxaeQ==}
-
-  webpack-bundle-analyzer@4.10.2:
-    resolution: {integrity: sha512-vJptkMm9pk5si4Bv922ZbKLV8UTT4zib4FPgXMhgzUny0bfDDkLXAVQs3ly3fS4/TN9ROFtb0NFrm04UXFE/Vw==}
-    engines: {node: '>= 10.13.0'}
-    hasBin: true
-
-  webpack-dev-middleware@7.4.5:
-    resolution: {integrity: sha512-uxQ6YqGdE4hgDKNf7hUiPXOdtkXvBJXrfEGYSx7P7LC8hnUYGK70X6xQXUvXeNyBDDcsiQXpG2m3G9vxowaEuA==}
-    engines: {node: '>= 18.12.0'}
-    peerDependencies:
-      webpack: ^5.0.0
-    peerDependenciesMeta:
-      webpack:
-        optional: true
-
-  webpack-dev-server@5.2.4:
-    resolution: {integrity: sha512-GqDPGZN9bRqKBTkp4aWkobDDHMsrXKoGSdOH56smIri8qR0JG8gfL8/v/f/OZR3/OKXjG8uwJbFVhKm/FNU/UA==}
-    engines: {node: '>= 18.12.0'}
-    hasBin: true
-    peerDependencies:
-      webpack: ^5.0.0
-      webpack-cli: '*'
-    peerDependenciesMeta:
-      webpack:
-        optional: true
-      webpack-cli:
-        optional: true
-
-  webpack-merge@5.10.0:
-    resolution: {integrity: sha512-+4zXKdx7UnO+1jaN4l2lHVD+mFvnlZQP/6ljaJVb4SZiwIKeUnrT5l0gkT8z+n4hKpC+jpOv6O9R+gLtag7pSA==}
-    engines: {node: '>=10.0.0'}
-
-  webpack-merge@6.0.1:
-    resolution: {integrity: sha512-hXXvrjtx2PLYx4qruKl+kyRSLc52V+cCvMxRjmKwoA+CBbbF5GfIBtR6kCvl0fYGqTUPKB+1ktVmTHqMOzgCBg==}
-    engines: {node: '>=18.0.0'}
-
-  webpack-sources@3.5.0:
-    resolution: {integrity: sha512-HPuy+uuoTCaaoEoI1LQ3JN9+vrPBvEesnnX1jADHy728cHSMlq4wUc4afYqahq2B1mhQVZxCXOkNTnXltr+2vQ==}
-    engines: {node: '>=10.13.0'}
-
-  webpack@5.107.2:
-    resolution: {integrity: sha512-v7RhXaJbpMlV0D7hC7lb2EbnxkoeUqf9qhKr6lozx3Q48pmFrqqNRmZFUEGmi7pSwm6fCQ2H1IjvCkHqdpVdjQ==}
-    engines: {node: '>=10.13.0'}
-    hasBin: true
-    peerDependencies:
-      webpack-cli: '*'
-    peerDependenciesMeta:
-      webpack-cli:
-        optional: true
-
-  webpackbar@7.0.0:
-    resolution: {integrity: sha512-aS9soqSO2iCHgqHoCrj4LbfGQUboDCYJPSFOAchEK+9psIjNrfSWW4Y0YEz67MKURNvMmfo0ycOg9d/+OOf9/Q==}
-    engines: {node: '>=14.21.3'}
-    peerDependencies:
-      '@rspack/core': '*'
-      webpack: 3 || 4 || 5
-    peerDependenciesMeta:
-      '@rspack/core':
-        optional: true
-      webpack:
-        optional: true
-
-  websocket-driver@0.7.5:
-    resolution: {integrity: sha512-ZL2+3c7kMBdIRCMz6l8jQMHyGVxj+UL+xVk74Ombiciboca8rHa15L86B19E5oh1pL9Ii/uj54gtsIrZGMo6zA==}
-    engines: {node: '>=0.8.0'}
-
-  websocket-extensions@0.1.4:
-    resolution: {integrity: sha512-OqedPIGOfsDlo31UNwYbCFMSaO9m9G/0faIHj5/dZFDMFqPTcx6UwqyOy3COEaEOg/9VsGIpdqn62W5KhoKSpg==}
-    engines: {node: '>=0.8.0'}
-
-  whatwg-fetch@3.6.20:
-    resolution: {integrity: sha512-EqhiFU6daOA8kpjOWTL0olhVOF3i7OrFzSYiGsEMB8GcXS+RrzauAERX65xMeNWVqxA6HXH2m69Z9LaKKdisfg==}
-
-  whatwg-url@5.0.0:
-    resolution: {integrity: sha512-saE57nupxk6v3HY35+jzBwYa0rKSy0XR8JSxZPwgLr7ys0IBzhGviA1/TUGJLmSVqs8pb9AnvICXEuOHLprYTw==}
-
-  which@2.0.2:
-    resolution: {integrity: sha512-BLI3Tl1TW3Pvl70l3yq3Y64i+awpwXqsGBYWkkqMtnbXgrMD+yj7rhW0kuEDxzJaYXGjEW5ogapKNMEKNMjibA==}
-    engines: {node: '>= 8'}
-    hasBin: true
-
-  widest-line@4.0.1:
-    resolution: {integrity: sha512-o0cyEG0e8GPzT4iGHphIOh0cJOV8fivsXxddQasHPHfoZf1ZexrfeA21w2NaEN1RHE+fXlfISmOE8R9N3u3Qig==}
-    engines: {node: '>=12'}
-
-  wildcard@2.0.1:
-    resolution: {integrity: sha512-CC1bOL87PIWSBhDcTrdeLo6eGT7mCFtrg0uIJtqJUFyK+eJnzl8A1niH56uu7KMa5XFrtiV+AQuHO3n7DsHnLQ==}
-
-  wolfy87-eventemitter@5.2.9:
-    resolution: {integrity: sha512-P+6vtWyuDw+MB01X7UeF8TaHBvbCovf4HPEMF/SV7BdDc1SMTiBy13SRD71lQh4ExFTG1d/WNzDGDCyOKSMblw==}
-
-  word-wrap@1.2.5:
-    resolution: {integrity: sha512-BN22B5eaMMI9UMtjrGd5g5eCYPpCPDUy0FJXbYsaT5zYxjFOckS53SQDE3pWkVoWpHXVb3BrYcEN4Twa55B5cA==}
-    engines: {node: '>=0.10.0'}
-
-  wrap-ansi@7.0.0:
-    resolution: {integrity: sha512-YVGIj2kamLSTxw6NsZjoBxfSwsn0ycdesmc4p+Q21c5zPuZ1pl+NfxVdxPtdHvmNVOQ6XSYG4AUtyt/Fi7D16Q==}
-    engines: {node: '>=10'}
-
-  wrap-ansi@8.1.0:
-    resolution: {integrity: sha512-si7QWI6zUMq56bESFvagtmzMdGOtoxfR+Sez11Mobfc7tm+VkUckk9bW2UeffTGVUbOksxmSw0AA2gs8g71NCQ==}
-    engines: {node: '>=12'}
-
-  wrap-ansi@9.0.2:
-    resolution: {integrity: sha512-42AtmgqjV+X1VpdOfyTGOYRi0/zsoLqtXQckTmqTeybT+BDIbM/Guxo7x3pE2vtpr1ok6xRqM9OpBe+Jyoqyww==}
-    engines: {node: '>=18'}
-
-  wrappy@1.0.2:
-    resolution: {integrity: sha512-l4Sp/DRseor9wL6EvV2+TuQn63dMkPjZ/sp9XkghTEbV9KlPS1xUsZ3u7/IQO4wxtcFB4bgpQPRcR3QCvezPcQ==}
-
-  write-file-atomic@3.0.3:
-    resolution: {integrity: sha512-AvHcyZ5JnSfq3ioSyjrBkH9yW4m7Ayk8/9My/DD9onKeu/94fwrMocemO2QAJFAlnnDN+ZDS+ZjAR5ua1/PV/Q==}
-
-  ws@7.5.11:
-    resolution: {integrity: sha512-zS54Oen9bITtp7kp2XM3AydrCIq1D+HwJOuH+c+e4LfpL/lotP5osijd+UoMnxwAam1GN8R4KtLAyIrIcBNpiA==}
-    engines: {node: '>=8.3.0'}
-    peerDependencies:
-      bufferutil: ^4.0.1
-      utf-8-validate: ^5.0.2
-    peerDependenciesMeta:
-      bufferutil:
-        optional: true
-      utf-8-validate:
-        optional: true
-
-  ws@8.21.0:
-    resolution: {integrity: sha512-Vsp28b7DRcimFQvrqu2Wek3z1iYxDCWqHYB8Qsnk/S4RfaCQzPGPyBNuVjJV3cd6UiKtUtp6sNM77gWvzcCH+g==}
-    engines: {node: '>=10.0.0'}
-    peerDependencies:
-      bufferutil: ^4.0.1
-      utf-8-validate: '>=5.0.2'
-    peerDependenciesMeta:
-      bufferutil:
-        optional: true
-      utf-8-validate:
-        optional: true
-
-  wsl-utils@0.1.0:
-    resolution: {integrity: sha512-h3Fbisa2nKGPxCpm89Hk33lBLsnaGBvctQopaBSOW/uIs6FTe1ATyAnKFJrzVs9vpGdsTe73WF3V4lIsk4Gacw==}
-    engines: {node: '>=18'}
-
-  xdg-basedir@5.1.0:
-    resolution: {integrity: sha512-GCPAHLvrIH13+c0SuacwvRYj2SxJXQ4kaVTT5xgL3kPrz56XxkF21IGhjSE1+W0aw7gpBWRGXLCPnPby6lSpmQ==}
-    engines: {node: '>=12'}
-
-  xml-formatter@3.7.0:
-    resolution: {integrity: sha512-+8qTc3zv2UcJ1v9IsSIce37Dl4MQG14Cp7tWrwmy202UaI1wqRukw5QMX1JHsV+DX64yw77EgGsj2s5wGvuMbQ==}
-    engines: {node: '>= 16'}
-
-  xml-js@1.6.11:
-    resolution: {integrity: sha512-7rVi2KMfwfWFl+GpPg6m80IVMWXLRjO+PxTq7V2CDhoGak0wzYzFgUY2m4XJ47OGdXd8eLE8EmwfAmdjw7lC1g==}
-    hasBin: true
-
-  xml-parser-xo@4.1.6:
-    resolution: {integrity: sha512-mXbSNSM+rIwndoxSwmFa83bOdeP8G/cOGr7XvxA67X7ebCzoAuVez9JYDCDub3zRDNBZxIbfjuXLSsamr7NfwQ==}
-    engines: {node: '>= 20'}
-
-  xtend@4.0.2:
-    resolution: {integrity: sha512-LKYU1iAXJXUgAXn9URjiu+MWhyUXHsvfp7mcuYm9dSUKK0/CjtrUwFAxD82/mCWbtLsGjFIad0wIsod4zrTAEQ==}
-    engines: {node: '>=0.4'}
-
-  y18n@5.0.8:
-    resolution: {integrity: sha512-0pfFzegeDWJHJIAmTLRP2DwHjdF5s7jo9tuztdQxAhINCdvS+3nGINqPd00AphqJR/0LhANUS6/+7SCb98YOfA==}
-    engines: {node: '>=10'}
-
-  yallist@3.1.1:
-    resolution: {integrity: sha512-a4UGQaWPH59mOXUYnAG2ewncQS4i4F43Tv3JoAM+s2VDAmS9NsK8GpDMLrCHPksFT7h3K6TOoUNn2pb7RoXx4g==}
-
-  yaml-ast-parser@0.0.43:
-    resolution: {integrity: sha512-2PTINUwsRqSd+s8XxKaJWQlUuEMHJQyEuh2edBbW8KNJz0SJPwUSD2zRWqezFEdN7IzAgeuYHFUCF7o8zRdZ0A==}
-
-  yaml@1.10.2:
-    resolution: {integrity: sha512-r3vXyErRCYJ7wg28yvBY5VSoAF8ZvlcW9/BwUzEtUsjvX/DKs24dIkuwjtuprwJJHsbyUbLApepYTR1BN4uHrg==}
-    engines: {node: '>= 6'}
-
-  yaml@1.10.3:
-    resolution: {integrity: sha512-vIYeF1u3CjlhAFekPPAk2h/Kv4T3mAkMox5OymRiJQB0spDP10LHvt+K7G9Ny6NuuMAb25/6n1qyUjAcGNf/AA==}
-    engines: {node: '>= 6'}
-
-  yaml@2.9.0:
-    resolution: {integrity: sha512-2AvhNX3mb8zd6Zy7INTtSpl1F15HW6Wnqj0srWlkKLcpYl/gMIMJiyuGq2KeI2YFxUPjdlB+3Lc10seMLtL4cA==}
-    engines: {node: '>= 14.6'}
-    hasBin: true
-
-  yargs-parser@21.1.1:
-    resolution: {integrity: sha512-tVpsJW7DdjecAiFpbIB1e3qxIQsE6NoPc5/eTdrbbIC4h0LVsWhnoa3g+m2HclBIujHzsxZ4VJVA+GUuc2/LBw==}
-    engines: {node: '>=12'}
-
-  yargs-parser@22.0.0:
-    resolution: {integrity: sha512-rwu/ClNdSMpkSrUb+d6BRsSkLUq1fmfsY6TOpYzTwvwkg1/NRG85KBy3kq++A8LKQwX6lsu+aWad+2khvuXrqw==}
-    engines: {node: ^20.19.0 || ^22.12.0 || >=23}
-
-  yargs@17.7.3:
-    resolution: {integrity: sha512-GZtjxm/J/4TSxuL3FNYjCmLktBTnIw/rVmKSIyKeYAZpmJB2ig9VauCC5xsa82GNKVKDAqpOn3KVzNt0zmrU0g==}
-    engines: {node: '>=12'}
-
-  yargs@18.0.0:
-    resolution: {integrity: sha512-4UEqdc2RYGHZc7Doyqkrqiln3p9X2DZVxaGbwhn2pi7MrRagKaOcIKe8L3OxYcbhXLgLFUS3zAYuQjKBQgmuNg==}
-    engines: {node: ^20.19.0 || ^22.12.0 || >=23}
-
-  yocto-queue@0.1.0:
-    resolution: {integrity: sha512-rVksvsnNCdJ/ohGc6xgPwyN8eheCxsiLM8mxuE/t/mOVqJewPuO1miLpTHQiRgTKCLexL4MeAFVagts7HmNZ2Q==}
-    engines: {node: '>=10'}
-
-  yocto-queue@1.2.2:
-    resolution: {integrity: sha512-4LCcse/U2MHZ63HAJVE+v71o7yOdIe4cZ70Wpf8D/IyjDKYQLV5GD46B+hSTjJsvV5PztjvHoU580EftxjDZFQ==}
-    engines: {node: '>=12.20'}
-
-  zustand@3.7.2:
-    resolution: {integrity: sha512-PIJDIZKtokhof+9+60cpockVOq05sJzHCriyvaLBmEJixseQ1a5Kdov6fWZfWOu5SK9c+FhH1jU0tntLxRJYMA==}
-    engines: {node: '>=12.7.0'}
-    peerDependencies:
-      react: '>=16.8'
-    peerDependenciesMeta:
-      react:
-        optional: true
-
-  zwitch@1.0.5:
-    resolution: {integrity: sha512-V50KMwwzqJV0NpZIZFwfOD5/lyny3WlSzRiXgA0G7VUnRlqttta1L6UQIHzd6EuBY/cHGfwTIck7w1yH6Q5zUw==}
-
-  zwitch@2.0.4:
-    resolution: {integrity: sha512-bXE4cR/kVZhKZX/RjPEflHaKVhUVl85noU3v6b8apfQEc1x4A+zBxjZ4lN8LqGd6WZ3dl98pY4o717VFmoPp+A==}
-
-snapshots:
-
-  '@adobe/react-spectrum-ui@1.2.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-
-  '@adobe/react-spectrum-workflow@2.3.5(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-
-  '@adobe/react-spectrum@3.47.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@internationalized/date': 3.12.2
-      '@react-types/shared': 3.35.0(react@19.2.7)
-      '@spectrum-icons/ui': 3.7.1(@adobe/react-spectrum@3.47.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@spectrum-icons/workflow': 4.3.1(@adobe/react-spectrum@3.47.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@swc/helpers': 0.5.23
-      client-only: 0.0.1
-      clsx: 2.1.1
-      react: 19.2.7
-      react-aria: 3.49.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      react-aria-components: 1.18.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      react-dom: 19.2.7(react@19.2.7)
-      react-stately: 3.47.0(react@19.2.7)
-      react-transition-group: 4.4.5(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      use-sync-external-store: 1.6.0(react@19.2.7)
-
-  '@adobe/react-spectrum@3.47.3(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@internationalized/date': 3.12.3
-      '@react-types/shared': 3.36.1(react@19.2.7)
-      '@spectrum-icons/ui': 3.7.1(@adobe/react-spectrum@3.47.3(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@spectrum-icons/workflow': 4.3.1(@adobe/react-spectrum@3.47.3(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@swc/helpers': 0.5.23
-      client-only: 0.0.1
-      clsx: 2.1.1
-      react: 19.2.7
-      react-aria: 3.51.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      react-aria-components: 1.20.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      react-dom: 19.2.7(react@19.2.7)
-      react-stately: 3.49.0(react@19.2.7)
-      react-transition-group: 4.4.5(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      use-sync-external-store: 1.6.0(react@19.2.7)
-
-  '@algolia/abtesting@1.19.0':
-    dependencies:
-      '@algolia/client-common': 5.53.0
-      '@algolia/requester-browser-xhr': 5.53.0
-      '@algolia/requester-fetch': 5.53.0
-      '@algolia/requester-node-http': 5.53.0
-
-  '@algolia/autocomplete-core@1.19.2(@algolia/client-search@5.53.0)(algoliasearch@5.53.0)(search-insights@2.17.3)':
-    dependencies:
-      '@algolia/autocomplete-plugin-algolia-insights': 1.19.2(@algolia/client-search@5.53.0)(algoliasearch@5.53.0)(search-insights@2.17.3)
-      '@algolia/autocomplete-shared': 1.19.2(@algolia/client-search@5.53.0)(algoliasearch@5.53.0)
-    transitivePeerDependencies:
-      - '@algolia/client-search'
-      - algoliasearch
-      - search-insights
-
-  '@algolia/autocomplete-plugin-algolia-insights@1.19.2(@algolia/client-search@5.53.0)(algoliasearch@5.53.0)(search-insights@2.17.3)':
-    dependencies:
-      '@algolia/autocomplete-shared': 1.19.2(@algolia/client-search@5.53.0)(algoliasearch@5.53.0)
-      search-insights: 2.17.3
-    transitivePeerDependencies:
-      - '@algolia/client-search'
-      - algoliasearch
-
-  '@algolia/autocomplete-shared@1.19.2(@algolia/client-search@5.53.0)(algoliasearch@5.53.0)':
-    dependencies:
-      '@algolia/client-search': 5.53.0
-      algoliasearch: 5.53.0
-
-  '@algolia/client-abtesting@5.53.0':
-    dependencies:
-      '@algolia/client-common': 5.53.0
-      '@algolia/requester-browser-xhr': 5.53.0
-      '@algolia/requester-fetch': 5.53.0
-      '@algolia/requester-node-http': 5.53.0
-
-  '@algolia/client-analytics@5.53.0':
-    dependencies:
-      '@algolia/client-common': 5.53.0
-      '@algolia/requester-browser-xhr': 5.53.0
-      '@algolia/requester-fetch': 5.53.0
-      '@algolia/requester-node-http': 5.53.0
-
-  '@algolia/client-common@5.53.0': {}
-
-  '@algolia/client-insights@5.53.0':
-    dependencies:
-      '@algolia/client-common': 5.53.0
-      '@algolia/requester-browser-xhr': 5.53.0
-      '@algolia/requester-fetch': 5.53.0
-      '@algolia/requester-node-http': 5.53.0
-
-  '@algolia/client-personalization@5.53.0':
-    dependencies:
-      '@algolia/client-common': 5.53.0
-      '@algolia/requester-browser-xhr': 5.53.0
-      '@algolia/requester-fetch': 5.53.0
-      '@algolia/requester-node-http': 5.53.0
-
-  '@algolia/client-query-suggestions@5.53.0':
-    dependencies:
-      '@algolia/client-common': 5.53.0
-      '@algolia/requester-browser-xhr': 5.53.0
-      '@algolia/requester-fetch': 5.53.0
-      '@algolia/requester-node-http': 5.53.0
-
-  '@algolia/client-search@5.53.0':
-    dependencies:
-      '@algolia/client-common': 5.53.0
-      '@algolia/requester-browser-xhr': 5.53.0
-      '@algolia/requester-fetch': 5.53.0
-      '@algolia/requester-node-http': 5.53.0
-
-  '@algolia/events@4.0.1': {}
-
-  '@algolia/ingestion@1.53.0':
-    dependencies:
-      '@algolia/client-common': 5.53.0
-      '@algolia/requester-browser-xhr': 5.53.0
-      '@algolia/requester-fetch': 5.53.0
-      '@algolia/requester-node-http': 5.53.0
-
-  '@algolia/monitoring@1.53.0':
-    dependencies:
-      '@algolia/client-common': 5.53.0
-      '@algolia/requester-browser-xhr': 5.53.0
-      '@algolia/requester-fetch': 5.53.0
-      '@algolia/requester-node-http': 5.53.0
-
-  '@algolia/recommend@5.53.0':
-    dependencies:
-      '@algolia/client-common': 5.53.0
-      '@algolia/requester-browser-xhr': 5.53.0
-      '@algolia/requester-fetch': 5.53.0
-      '@algolia/requester-node-http': 5.53.0
-
-  '@algolia/requester-browser-xhr@5.53.0':
-    dependencies:
-      '@algolia/client-common': 5.53.0
-
-  '@algolia/requester-fetch@5.53.0':
-    dependencies:
-      '@algolia/client-common': 5.53.0
-
-  '@algolia/requester-node-http@5.53.0':
-    dependencies:
-      '@algolia/client-common': 5.53.0
-
-  '@antfu/install-pkg@1.1.0':
-    dependencies:
-      package-manager-detector: 1.6.0
-      tinyexec: 1.2.4
-
-  '@apidevtools/json-schema-ref-parser@15.4.0(@types/json-schema@7.0.15)':
-    dependencies:
-      '@types/json-schema': 7.0.15
-      js-yaml: 4.3.1
-
-  '@babel/code-frame@7.29.7':
-    dependencies:
-      '@babel/helper-validator-identifier': 7.29.7
-      js-tokens: 4.0.0
-      picocolors: 1.1.1
-
-  '@babel/compat-data@7.29.7': {}
-
-  '@babel/core@7.29.7':
-    dependencies:
-      '@babel/code-frame': 7.29.7
-      '@babel/generator': 7.29.7
-      '@babel/helper-compilation-targets': 7.29.7
-      '@babel/helper-module-transforms': 7.29.7(@babel/core@7.29.7)
-      '@babel/helpers': 7.29.7
-      '@babel/parser': 7.29.7
-      '@babel/template': 7.29.7
-      '@babel/traverse': 7.29.7
-      '@babel/types': 7.29.7
-      '@jridgewell/remapping': 2.3.5
-      convert-source-map: 2.0.0
-      debug: 4.4.3
-      gensync: 1.0.0-beta.2
-      json5: 2.2.3
-      semver: 6.3.1
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/generator@7.29.7':
-    dependencies:
-      '@babel/parser': 7.29.7
-      '@babel/types': 7.29.7
-      '@jridgewell/gen-mapping': 0.3.13
-      '@jridgewell/trace-mapping': 0.3.31
-      jsesc: 3.1.0
-
-  '@babel/helper-annotate-as-pure@7.29.7':
-    dependencies:
-      '@babel/types': 7.29.7
-
-  '@babel/helper-compilation-targets@7.29.7':
-    dependencies:
-      '@babel/compat-data': 7.29.7
-      '@babel/helper-validator-option': 7.29.7
-      browserslist: 4.28.2
-      lru-cache: 5.1.1
-      semver: 6.3.1
-
-  '@babel/helper-create-class-features-plugin@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-annotate-as-pure': 7.29.7
-      '@babel/helper-member-expression-to-functions': 7.29.7
-      '@babel/helper-optimise-call-expression': 7.29.7
-      '@babel/helper-replace-supers': 7.29.7(@babel/core@7.29.7)
-      '@babel/helper-skip-transparent-expression-wrappers': 7.29.7
-      '@babel/traverse': 7.29.7
-      semver: 6.3.1
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/helper-create-regexp-features-plugin@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-annotate-as-pure': 7.29.7
-      regexpu-core: 6.4.0
-      semver: 6.3.1
-
-  '@babel/helper-define-polyfill-provider@0.6.8(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-compilation-targets': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-      debug: 4.4.3
-      lodash.debounce: 4.0.8
-      resolve: 1.22.12
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/helper-globals@7.29.7': {}
-
-  '@babel/helper-member-expression-to-functions@7.29.7':
-    dependencies:
-      '@babel/traverse': 7.29.7
-      '@babel/types': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/helper-module-imports@7.29.7':
-    dependencies:
-      '@babel/traverse': 7.29.7
-      '@babel/types': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/helper-module-transforms@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-module-imports': 7.29.7
-      '@babel/helper-validator-identifier': 7.29.7
-      '@babel/traverse': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/helper-optimise-call-expression@7.29.7':
-    dependencies:
-      '@babel/types': 7.29.7
-
-  '@babel/helper-plugin-utils@7.29.7': {}
-
-  '@babel/helper-remap-async-to-generator@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-annotate-as-pure': 7.29.7
-      '@babel/helper-wrap-function': 7.29.7
-      '@babel/traverse': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/helper-replace-supers@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-member-expression-to-functions': 7.29.7
-      '@babel/helper-optimise-call-expression': 7.29.7
-      '@babel/traverse': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/helper-skip-transparent-expression-wrappers@7.29.7':
-    dependencies:
-      '@babel/traverse': 7.29.7
-      '@babel/types': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/helper-string-parser@7.29.7': {}
-
-  '@babel/helper-validator-identifier@7.29.7': {}
-
-  '@babel/helper-validator-option@7.29.7': {}
-
-  '@babel/helper-wrap-function@7.29.7':
-    dependencies:
-      '@babel/template': 7.29.7
-      '@babel/traverse': 7.29.7
-      '@babel/types': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/helpers@7.29.7':
-    dependencies:
-      '@babel/template': 7.29.7
-      '@babel/types': 7.29.7
-
-  '@babel/parser@7.29.7':
-    dependencies:
-      '@babel/types': 7.29.7
-
-  '@babel/plugin-bugfix-firefox-class-in-computed-class-key@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-      '@babel/traverse': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-bugfix-safari-class-field-initializer-scope@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-bugfix-safari-rest-destructuring-rhs-array@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-      '@babel/helper-skip-transparent-expression-wrappers': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-      '@babel/helper-skip-transparent-expression-wrappers': 7.29.7
-      '@babel/plugin-transform-optional-chaining': 7.29.7(@babel/core@7.29.7)
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-bugfix-v8-static-class-fields-redefine-readonly@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-      '@babel/traverse': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-proposal-private-property-in-object@7.21.0-placeholder-for-preset-env.2(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-
-  '@babel/plugin-syntax-dynamic-import@7.8.3(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-syntax-import-assertions@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-syntax-import-attributes@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-syntax-jsx@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-syntax-typescript@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-syntax-unicode-sets-regex@7.18.6(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-create-regexp-features-plugin': 7.29.7(@babel/core@7.29.7)
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-arrow-functions@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-async-generator-functions@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-      '@babel/helper-remap-async-to-generator': 7.29.7(@babel/core@7.29.7)
-      '@babel/traverse': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-transform-async-to-generator@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-module-imports': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-      '@babel/helper-remap-async-to-generator': 7.29.7(@babel/core@7.29.7)
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-transform-block-scoped-functions@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-block-scoping@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-class-properties@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-create-class-features-plugin': 7.29.7(@babel/core@7.29.7)
-      '@babel/helper-plugin-utils': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-transform-class-static-block@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-create-class-features-plugin': 7.29.7(@babel/core@7.29.7)
-      '@babel/helper-plugin-utils': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-transform-classes@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-annotate-as-pure': 7.29.7
-      '@babel/helper-compilation-targets': 7.29.7
-      '@babel/helper-globals': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-      '@babel/helper-replace-supers': 7.29.7(@babel/core@7.29.7)
-      '@babel/traverse': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-transform-computed-properties@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-      '@babel/template': 7.29.7
-
-  '@babel/plugin-transform-destructuring@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-      '@babel/traverse': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-transform-dotall-regex@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-create-regexp-features-plugin': 7.29.7(@babel/core@7.29.7)
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-duplicate-keys@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-duplicate-named-capturing-groups-regex@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-create-regexp-features-plugin': 7.29.7(@babel/core@7.29.7)
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-dynamic-import@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-explicit-resource-management@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-      '@babel/plugin-transform-destructuring': 7.29.7(@babel/core@7.29.7)
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-transform-exponentiation-operator@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-export-namespace-from@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-for-of@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-      '@babel/helper-skip-transparent-expression-wrappers': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-transform-function-name@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-compilation-targets': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-      '@babel/traverse': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-transform-json-strings@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-literals@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-logical-assignment-operators@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-member-expression-literals@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-modules-amd@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-module-transforms': 7.29.7(@babel/core@7.29.7)
-      '@babel/helper-plugin-utils': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-transform-modules-commonjs@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-module-transforms': 7.29.7(@babel/core@7.29.7)
-      '@babel/helper-plugin-utils': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-transform-modules-systemjs@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-module-transforms': 7.29.7(@babel/core@7.29.7)
-      '@babel/helper-plugin-utils': 7.29.7
-      '@babel/helper-validator-identifier': 7.29.7
-      '@babel/traverse': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-transform-modules-umd@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-module-transforms': 7.29.7(@babel/core@7.29.7)
-      '@babel/helper-plugin-utils': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-transform-named-capturing-groups-regex@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-create-regexp-features-plugin': 7.29.7(@babel/core@7.29.7)
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-new-target@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-nullish-coalescing-operator@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-numeric-separator@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-object-rest-spread@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-compilation-targets': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-      '@babel/plugin-transform-destructuring': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-parameters': 7.29.7(@babel/core@7.29.7)
-      '@babel/traverse': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-transform-object-super@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-      '@babel/helper-replace-supers': 7.29.7(@babel/core@7.29.7)
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-transform-optional-catch-binding@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-optional-chaining@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-      '@babel/helper-skip-transparent-expression-wrappers': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-transform-parameters@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-private-methods@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-create-class-features-plugin': 7.29.7(@babel/core@7.29.7)
-      '@babel/helper-plugin-utils': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-transform-private-property-in-object@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-annotate-as-pure': 7.29.7
-      '@babel/helper-create-class-features-plugin': 7.29.7(@babel/core@7.29.7)
-      '@babel/helper-plugin-utils': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-transform-property-literals@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-react-constant-elements@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-react-display-name@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-react-jsx-development@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/plugin-transform-react-jsx': 7.29.7(@babel/core@7.29.7)
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-transform-react-jsx@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-annotate-as-pure': 7.29.7
-      '@babel/helper-module-imports': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-      '@babel/plugin-syntax-jsx': 7.29.7(@babel/core@7.29.7)
-      '@babel/types': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-transform-react-pure-annotations@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-annotate-as-pure': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-regenerator@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-regexp-modifiers@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-create-regexp-features-plugin': 7.29.7(@babel/core@7.29.7)
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-reserved-words@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-runtime@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-module-imports': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-      babel-plugin-polyfill-corejs2: 0.4.17(@babel/core@7.29.7)
-      babel-plugin-polyfill-corejs3: 0.13.0(@babel/core@7.29.7)
-      babel-plugin-polyfill-regenerator: 0.6.8(@babel/core@7.29.7)
-      semver: 6.3.1
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-transform-shorthand-properties@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-spread@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-      '@babel/helper-skip-transparent-expression-wrappers': 7.29.7
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-transform-sticky-regex@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-template-literals@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-typeof-symbol@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-typescript@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-annotate-as-pure': 7.29.7
-      '@babel/helper-create-class-features-plugin': 7.29.7(@babel/core@7.29.7)
-      '@babel/helper-plugin-utils': 7.29.7
-      '@babel/helper-skip-transparent-expression-wrappers': 7.29.7
-      '@babel/plugin-syntax-typescript': 7.29.7(@babel/core@7.29.7)
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/plugin-transform-unicode-escapes@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-unicode-property-regex@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-create-regexp-features-plugin': 7.29.7(@babel/core@7.29.7)
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-unicode-regex@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-create-regexp-features-plugin': 7.29.7(@babel/core@7.29.7)
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/plugin-transform-unicode-sets-regex@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-create-regexp-features-plugin': 7.29.7(@babel/core@7.29.7)
-      '@babel/helper-plugin-utils': 7.29.7
-
-  '@babel/preset-env@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/compat-data': 7.29.7
-      '@babel/core': 7.29.7
-      '@babel/helper-compilation-targets': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-      '@babel/helper-validator-option': 7.29.7
-      '@babel/plugin-bugfix-firefox-class-in-computed-class-key': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-bugfix-safari-class-field-initializer-scope': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-bugfix-safari-rest-destructuring-rhs-array': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-bugfix-v8-static-class-fields-redefine-readonly': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-proposal-private-property-in-object': 7.21.0-placeholder-for-preset-env.2(@babel/core@7.29.7)
-      '@babel/plugin-syntax-import-assertions': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-syntax-import-attributes': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-syntax-unicode-sets-regex': 7.18.6(@babel/core@7.29.7)
-      '@babel/plugin-transform-arrow-functions': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-async-generator-functions': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-async-to-generator': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-block-scoped-functions': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-block-scoping': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-class-properties': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-class-static-block': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-classes': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-computed-properties': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-destructuring': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-dotall-regex': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-duplicate-keys': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-duplicate-named-capturing-groups-regex': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-dynamic-import': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-explicit-resource-management': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-exponentiation-operator': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-export-namespace-from': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-for-of': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-function-name': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-json-strings': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-literals': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-logical-assignment-operators': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-member-expression-literals': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-modules-amd': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-modules-commonjs': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-modules-systemjs': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-modules-umd': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-named-capturing-groups-regex': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-new-target': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-nullish-coalescing-operator': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-numeric-separator': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-object-rest-spread': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-object-super': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-optional-catch-binding': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-optional-chaining': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-parameters': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-private-methods': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-private-property-in-object': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-property-literals': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-regenerator': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-regexp-modifiers': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-reserved-words': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-shorthand-properties': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-spread': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-sticky-regex': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-template-literals': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-typeof-symbol': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-unicode-escapes': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-unicode-property-regex': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-unicode-regex': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-unicode-sets-regex': 7.29.7(@babel/core@7.29.7)
-      '@babel/preset-modules': 0.1.6-no-external-plugins(@babel/core@7.29.7)
-      babel-plugin-polyfill-corejs2: 0.4.17(@babel/core@7.29.7)
-      babel-plugin-polyfill-corejs3: 0.14.2(@babel/core@7.29.7)
-      babel-plugin-polyfill-regenerator: 0.6.8(@babel/core@7.29.7)
-      core-js-compat: 3.49.0
-      semver: 6.3.1
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/preset-modules@0.1.6-no-external-plugins(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-      '@babel/types': 7.29.7
-      esutils: 2.0.3
-
-  '@babel/preset-react@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-      '@babel/helper-validator-option': 7.29.7
-      '@babel/plugin-transform-react-display-name': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-react-jsx': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-react-jsx-development': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-react-pure-annotations': 7.29.7(@babel/core@7.29.7)
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/preset-typescript@7.29.7(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-plugin-utils': 7.29.7
-      '@babel/helper-validator-option': 7.29.7
-      '@babel/plugin-syntax-jsx': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-modules-commonjs': 7.29.7(@babel/core@7.29.7)
-      '@babel/plugin-transform-typescript': 7.29.7(@babel/core@7.29.7)
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/runtime@7.29.7': {}
-
-  '@babel/template@7.29.7':
-    dependencies:
-      '@babel/code-frame': 7.29.7
-      '@babel/parser': 7.29.7
-      '@babel/types': 7.29.7
-
-  '@babel/traverse@7.29.7':
-    dependencies:
-      '@babel/code-frame': 7.29.7
-      '@babel/generator': 7.29.7
-      '@babel/helper-globals': 7.29.7
-      '@babel/parser': 7.29.7
-      '@babel/template': 7.29.7
-      '@babel/types': 7.29.7
-      debug: 4.4.3
-    transitivePeerDependencies:
-      - supports-color
-
-  '@babel/types@7.29.7':
-    dependencies:
-      '@babel/helper-string-parser': 7.29.7
-      '@babel/helper-validator-identifier': 7.29.7
-
-  '@braintree/sanitize-url@7.1.2': {}
-
-  '@chevrotain/types@11.1.2': {}
-
-  '@colors/colors@1.5.0':
-    optional: true
-
-  '@csstools/cascade-layer-name-parser@2.0.5(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)':
-    dependencies:
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-
-  '@csstools/color-helpers@5.1.0': {}
-
-  '@csstools/css-calc@2.1.4(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)':
-    dependencies:
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-
-  '@csstools/css-color-parser@3.1.0(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)':
-    dependencies:
-      '@csstools/color-helpers': 5.1.0
-      '@csstools/css-calc': 2.1.4(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-
-  '@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4)':
-    dependencies:
-      '@csstools/css-tokenizer': 3.0.4
-
-  '@csstools/css-tokenizer@3.0.4': {}
-
-  '@csstools/media-query-list-parser@4.0.3(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)':
-    dependencies:
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-
-  '@csstools/postcss-alpha-function@1.0.1(postcss@8.5.15)':
-    dependencies:
-      '@csstools/css-color-parser': 3.1.0(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      '@csstools/postcss-progressive-custom-properties': 4.2.1(postcss@8.5.15)
-      '@csstools/utilities': 2.0.0(postcss@8.5.15)
-      postcss: 8.5.15
-
-  '@csstools/postcss-cascade-layers@5.0.2(postcss@8.5.15)':
-    dependencies:
-      '@csstools/selector-specificity': 5.0.0(postcss-selector-parser@7.1.2)
-      postcss: 8.5.15
-      postcss-selector-parser: 7.1.2
-
-  '@csstools/postcss-color-function-display-p3-linear@1.0.1(postcss@8.5.15)':
-    dependencies:
-      '@csstools/css-color-parser': 3.1.0(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      '@csstools/postcss-progressive-custom-properties': 4.2.1(postcss@8.5.15)
-      '@csstools/utilities': 2.0.0(postcss@8.5.15)
-      postcss: 8.5.15
-
-  '@csstools/postcss-color-function@4.0.12(postcss@8.5.15)':
-    dependencies:
-      '@csstools/css-color-parser': 3.1.0(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      '@csstools/postcss-progressive-custom-properties': 4.2.1(postcss@8.5.15)
-      '@csstools/utilities': 2.0.0(postcss@8.5.15)
-      postcss: 8.5.15
-
-  '@csstools/postcss-color-mix-function@3.0.12(postcss@8.5.15)':
-    dependencies:
-      '@csstools/css-color-parser': 3.1.0(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      '@csstools/postcss-progressive-custom-properties': 4.2.1(postcss@8.5.15)
-      '@csstools/utilities': 2.0.0(postcss@8.5.15)
-      postcss: 8.5.15
-
-  '@csstools/postcss-color-mix-variadic-function-arguments@1.0.2(postcss@8.5.15)':
-    dependencies:
-      '@csstools/css-color-parser': 3.1.0(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      '@csstools/postcss-progressive-custom-properties': 4.2.1(postcss@8.5.15)
-      '@csstools/utilities': 2.0.0(postcss@8.5.15)
-      postcss: 8.5.15
-
-  '@csstools/postcss-content-alt-text@2.0.8(postcss@8.5.15)':
-    dependencies:
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      '@csstools/postcss-progressive-custom-properties': 4.2.1(postcss@8.5.15)
-      '@csstools/utilities': 2.0.0(postcss@8.5.15)
-      postcss: 8.5.15
-
-  '@csstools/postcss-contrast-color-function@2.0.12(postcss@8.5.15)':
-    dependencies:
-      '@csstools/css-color-parser': 3.1.0(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      '@csstools/postcss-progressive-custom-properties': 4.2.1(postcss@8.5.15)
-      '@csstools/utilities': 2.0.0(postcss@8.5.15)
-      postcss: 8.5.15
-
-  '@csstools/postcss-exponential-functions@2.0.9(postcss@8.5.15)':
-    dependencies:
-      '@csstools/css-calc': 2.1.4(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      postcss: 8.5.15
-
-  '@csstools/postcss-font-format-keywords@4.0.0(postcss@8.5.15)':
-    dependencies:
-      '@csstools/utilities': 2.0.0(postcss@8.5.15)
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
-
-  '@csstools/postcss-gamut-mapping@2.0.11(postcss@8.5.15)':
-    dependencies:
-      '@csstools/css-color-parser': 3.1.0(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      postcss: 8.5.15
-
-  '@csstools/postcss-gradients-interpolation-method@5.0.12(postcss@8.5.15)':
-    dependencies:
-      '@csstools/css-color-parser': 3.1.0(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      '@csstools/postcss-progressive-custom-properties': 4.2.1(postcss@8.5.15)
-      '@csstools/utilities': 2.0.0(postcss@8.5.15)
-      postcss: 8.5.15
-
-  '@csstools/postcss-hwb-function@4.0.12(postcss@8.5.15)':
-    dependencies:
-      '@csstools/css-color-parser': 3.1.0(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      '@csstools/postcss-progressive-custom-properties': 4.2.1(postcss@8.5.15)
-      '@csstools/utilities': 2.0.0(postcss@8.5.15)
-      postcss: 8.5.15
-
-  '@csstools/postcss-ic-unit@4.0.4(postcss@8.5.15)':
-    dependencies:
-      '@csstools/postcss-progressive-custom-properties': 4.2.1(postcss@8.5.15)
-      '@csstools/utilities': 2.0.0(postcss@8.5.15)
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
-
-  '@csstools/postcss-initial@2.0.1(postcss@8.5.15)':
-    dependencies:
-      postcss: 8.5.15
-
-  '@csstools/postcss-is-pseudo-class@5.0.3(postcss@8.5.15)':
-    dependencies:
-      '@csstools/selector-specificity': 5.0.0(postcss-selector-parser@7.1.2)
-      postcss: 8.5.15
-      postcss-selector-parser: 7.1.2
-
-  '@csstools/postcss-light-dark-function@2.0.11(postcss@8.5.15)':
-    dependencies:
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      '@csstools/postcss-progressive-custom-properties': 4.2.1(postcss@8.5.15)
-      '@csstools/utilities': 2.0.0(postcss@8.5.15)
-      postcss: 8.5.15
-
-  '@csstools/postcss-logical-float-and-clear@3.0.0(postcss@8.5.15)':
-    dependencies:
-      postcss: 8.5.15
-
-  '@csstools/postcss-logical-overflow@2.0.0(postcss@8.5.15)':
-    dependencies:
-      postcss: 8.5.15
-
-  '@csstools/postcss-logical-overscroll-behavior@2.0.0(postcss@8.5.15)':
-    dependencies:
-      postcss: 8.5.15
-
-  '@csstools/postcss-logical-resize@3.0.0(postcss@8.5.15)':
-    dependencies:
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
-
-  '@csstools/postcss-logical-viewport-units@3.0.4(postcss@8.5.15)':
-    dependencies:
-      '@csstools/css-tokenizer': 3.0.4
-      '@csstools/utilities': 2.0.0(postcss@8.5.15)
-      postcss: 8.5.15
-
-  '@csstools/postcss-media-minmax@2.0.9(postcss@8.5.15)':
-    dependencies:
-      '@csstools/css-calc': 2.1.4(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      '@csstools/media-query-list-parser': 4.0.3(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      postcss: 8.5.15
-
-  '@csstools/postcss-media-queries-aspect-ratio-number-values@3.0.5(postcss@8.5.15)':
-    dependencies:
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      '@csstools/media-query-list-parser': 4.0.3(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      postcss: 8.5.15
-
-  '@csstools/postcss-nested-calc@4.0.0(postcss@8.5.15)':
-    dependencies:
-      '@csstools/utilities': 2.0.0(postcss@8.5.15)
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
-
-  '@csstools/postcss-normalize-display-values@4.0.1(postcss@8.5.15)':
-    dependencies:
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
-
-  '@csstools/postcss-oklab-function@4.0.12(postcss@8.5.15)':
-    dependencies:
-      '@csstools/css-color-parser': 3.1.0(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      '@csstools/postcss-progressive-custom-properties': 4.2.1(postcss@8.5.15)
-      '@csstools/utilities': 2.0.0(postcss@8.5.15)
-      postcss: 8.5.15
-
-  '@csstools/postcss-position-area-property@1.0.0(postcss@8.5.15)':
-    dependencies:
-      postcss: 8.5.15
-
-  '@csstools/postcss-progressive-custom-properties@4.2.1(postcss@8.5.15)':
-    dependencies:
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
-
-  '@csstools/postcss-property-rule-prelude-list@1.0.0(postcss@8.5.15)':
-    dependencies:
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      postcss: 8.5.15
-
-  '@csstools/postcss-random-function@2.0.1(postcss@8.5.15)':
-    dependencies:
-      '@csstools/css-calc': 2.1.4(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      postcss: 8.5.15
-
-  '@csstools/postcss-relative-color-syntax@3.0.12(postcss@8.5.15)':
-    dependencies:
-      '@csstools/css-color-parser': 3.1.0(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      '@csstools/postcss-progressive-custom-properties': 4.2.1(postcss@8.5.15)
-      '@csstools/utilities': 2.0.0(postcss@8.5.15)
-      postcss: 8.5.15
-
-  '@csstools/postcss-scope-pseudo-class@4.0.1(postcss@8.5.15)':
-    dependencies:
-      postcss: 8.5.15
-      postcss-selector-parser: 7.1.2
-
-  '@csstools/postcss-sign-functions@1.1.4(postcss@8.5.15)':
-    dependencies:
-      '@csstools/css-calc': 2.1.4(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      postcss: 8.5.15
-
-  '@csstools/postcss-stepped-value-functions@4.0.9(postcss@8.5.15)':
-    dependencies:
-      '@csstools/css-calc': 2.1.4(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      postcss: 8.5.15
-
-  '@csstools/postcss-syntax-descriptor-syntax-production@1.0.1(postcss@8.5.15)':
-    dependencies:
-      '@csstools/css-tokenizer': 3.0.4
-      postcss: 8.5.15
-
-  '@csstools/postcss-system-ui-font-family@1.0.0(postcss@8.5.15)':
-    dependencies:
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      postcss: 8.5.15
-
-  '@csstools/postcss-text-decoration-shorthand@4.0.3(postcss@8.5.15)':
-    dependencies:
-      '@csstools/color-helpers': 5.1.0
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
-
-  '@csstools/postcss-trigonometric-functions@4.0.9(postcss@8.5.15)':
-    dependencies:
-      '@csstools/css-calc': 2.1.4(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      postcss: 8.5.15
-
-  '@csstools/postcss-unset-value@4.0.0(postcss@8.5.15)':
-    dependencies:
-      postcss: 8.5.15
-
-  '@csstools/selector-resolve-nested@3.1.0(postcss-selector-parser@7.1.2)':
-    dependencies:
-      postcss-selector-parser: 7.1.2
-
-  '@csstools/selector-specificity@5.0.0(postcss-selector-parser@7.1.2)':
-    dependencies:
-      postcss-selector-parser: 7.1.2
-
-  '@csstools/utilities@2.0.0(postcss@8.5.15)':
-    dependencies:
-      postcss: 8.5.15
-
-  '@discoveryjs/json-ext@0.5.7': {}
-
-  '@docsearch/core@4.6.3(@types/react@19.2.17)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    optionalDependencies:
-      '@types/react': 19.2.17
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-
-  '@docsearch/css@4.6.3': {}
-
-  '@docsearch/react@4.6.3(@algolia/client-search@5.53.0)(@types/react@19.2.17)(algoliasearch@5.53.0)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(search-insights@2.17.3)':
-    dependencies:
-      '@algolia/autocomplete-core': 1.19.2(@algolia/client-search@5.53.0)(algoliasearch@5.53.0)(search-insights@2.17.3)
-      '@docsearch/core': 4.6.3(@types/react@19.2.17)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docsearch/css': 4.6.3
-    optionalDependencies:
-      '@types/react': 19.2.17
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      search-insights: 2.17.3
-    transitivePeerDependencies:
-      - '@algolia/client-search'
-      - algoliasearch
-
-  '@docusaurus/babel@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(clean-css@5.3.3)(cssnano@6.1.2(postcss@8.5.15))(html-minifier-terser@7.2.0)(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/generator': 7.29.7
-      '@babel/plugin-syntax-dynamic-import': 7.8.3(@babel/core@7.29.7)
-      '@babel/plugin-transform-runtime': 7.29.7(@babel/core@7.29.7)
-      '@babel/preset-env': 7.29.7(@babel/core@7.29.7)
-      '@babel/preset-react': 7.29.7(@babel/core@7.29.7)
-      '@babel/preset-typescript': 7.29.7(@babel/core@7.29.7)
-      '@babel/runtime': 7.29.7
-      '@babel/traverse': 7.29.7
-      '@docusaurus/logger': 3.10.1
-      '@docusaurus/utils': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(clean-css@5.3.3)(cssnano@6.1.2(postcss@8.5.15))(html-minifier-terser@7.2.0)(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      babel-plugin-dynamic-import-node: 2.3.3
-      fs-extra: 11.3.6
-      tslib: 2.8.1
-    transitivePeerDependencies:
-      - '@minify-html/node'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - clean-css
-      - cssnano
-      - csso
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - react
-      - react-dom
-      - supports-color
-      - uglify-js
-      - webpack-cli
-
-  '@docusaurus/babel@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/generator': 7.29.7
-      '@babel/plugin-syntax-dynamic-import': 7.8.3(@babel/core@7.29.7)
-      '@babel/plugin-transform-runtime': 7.29.7(@babel/core@7.29.7)
-      '@babel/preset-env': 7.29.7(@babel/core@7.29.7)
-      '@babel/preset-react': 7.29.7(@babel/core@7.29.7)
-      '@babel/preset-typescript': 7.29.7(@babel/core@7.29.7)
-      '@babel/runtime': 7.29.7
-      '@babel/traverse': 7.29.7
-      '@docusaurus/logger': 3.10.1
-      '@docusaurus/utils': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      babel-plugin-dynamic-import-node: 2.3.3
-      fs-extra: 11.3.6
-      tslib: 2.8.1
-    transitivePeerDependencies:
-      - '@minify-html/node'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - clean-css
-      - cssnano
-      - csso
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - react
-      - react-dom
-      - supports-color
-      - uglify-js
-      - webpack-cli
-
-  '@docusaurus/bundler@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@docusaurus/babel': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(clean-css@5.3.3)(cssnano@6.1.2(postcss@8.5.15))(html-minifier-terser@7.2.0)(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/cssnano-preset': 3.10.1
-      '@docusaurus/logger': 3.10.1
-      '@docusaurus/types': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(clean-css@5.3.3)(cssnano@6.1.2(postcss@8.5.15))(html-minifier-terser@7.2.0)(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(clean-css@5.3.3)(cssnano@6.1.2(postcss@8.5.15))(html-minifier-terser@7.2.0)(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      babel-loader: 9.2.1(@babel/core@7.29.7)(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      clean-css: 5.3.3
-      copy-webpack-plugin: 11.0.0(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      css-loader: 6.11.0(@rspack/core@1.7.11(@swc/helpers@0.5.23))(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      css-minimizer-webpack-plugin: 5.0.1(clean-css@5.3.3)(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      cssnano: 6.1.2(postcss@8.5.15)
-      file-loader: 6.2.0(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      html-minifier-terser: 7.2.0
-      mini-css-extract-plugin: 2.10.2(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      null-loader: 4.0.1(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      postcss: 8.5.15
-      postcss-loader: 7.3.4(postcss@8.5.15)(typescript@6.0.3)(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      postcss-preset-env: 10.6.1(postcss@8.5.15)
-      terser-webpack-plugin: 5.6.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(clean-css@5.3.3)(cssnano@6.1.2(postcss@8.5.15))(html-minifier-terser@7.2.0)(postcss@8.5.15)(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      tslib: 2.8.1
-      url-loader: 4.1.1(file-loader@6.2.0(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)))(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(clean-css@5.3.3)(cssnano@6.1.2(postcss@8.5.15))(html-minifier-terser@7.2.0)(postcss@8.5.15)
-      webpackbar: 7.0.0(@rspack/core@1.7.11(@swc/helpers@0.5.23))(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-    optionalDependencies:
-      '@docusaurus/faster': 3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15)
-    transitivePeerDependencies:
-      - '@minify-html/node'
-      - '@parcel/css'
-      - '@rspack/core'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - csso
-      - esbuild
-      - lightningcss
-      - react
-      - react-dom
-      - supports-color
-      - typescript
-      - uglify-js
-      - webpack-cli
-
-  '@docusaurus/core@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)':
-    dependencies:
-      '@docusaurus/babel': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/bundler': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/logger': 3.10.1
-      '@docusaurus/mdx-loader': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils-common': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils-validation': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@mdx-js/react': 3.1.1(@types/react@19.2.17)(react@19.2.7)
-      boxen: 6.2.1
-      chalk: 4.1.2
-      chokidar: 3.6.0
-      cli-table3: 0.6.5
-      combine-promises: 1.2.0
-      commander: 5.1.0
-      core-js: 3.49.0
-      detect-port: 1.6.1
-      escape-html: 1.0.3
-      eta: 2.2.0
-      eval: 0.1.8
-      execa: 5.1.1
-      fs-extra: 11.3.6
-      html-tags: 3.3.1
-      html-webpack-plugin: 5.6.7(@rspack/core@1.7.11(@swc/helpers@0.5.23))(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      leven: 3.1.0
-      lodash: 4.18.1
-      open: 8.4.2
-      p-map: 4.0.0
-      prompts: 2.4.2
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      react-helmet-async: '@slorber/react-helmet-async@1.3.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7)'
-      react-loadable: '@docusaurus/react-loadable@6.0.0(react@19.2.7)'
-      react-loadable-ssr-addon-v5-slorber: 1.0.3(@docusaurus/react-loadable@6.0.0(react@19.2.7))(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      react-router: 5.3.4(react@19.2.7)
-      react-router-config: 5.1.1(react-router@5.3.4(react@19.2.7))(react@19.2.7)
-      react-router-dom: 5.3.4(react@19.2.7)
-      semver: 7.8.3
-      serve-handler: 6.1.7
-      tinypool: 1.1.1
-      tslib: 2.8.1
-      update-notifier: 6.0.2
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
-      webpack-bundle-analyzer: 4.10.2
-      webpack-dev-server: 5.2.4(tslib@2.8.1)(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      webpack-merge: 6.0.1
-    optionalDependencies:
-      '@docusaurus/faster': 3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15)
-    transitivePeerDependencies:
-      - '@minify-html/node'
-      - '@parcel/css'
-      - '@rspack/core'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - bufferutil
-      - clean-css
-      - cssnano
-      - csso
-      - debug
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - supports-color
-      - typescript
-      - uglify-js
-      - utf-8-validate
-      - webpack-cli
-
-  '@docusaurus/cssnano-preset@3.10.1':
-    dependencies:
-      cssnano-preset-advanced: 6.1.2(postcss@8.5.15)
-      postcss: 8.5.15
-      postcss-sort-media-queries: 5.2.0(postcss@8.5.15)
-      tslib: 2.8.1
-
-  '@docusaurus/eslint-plugin@3.10.1(eslint@10.6.0(jiti@1.21.7))(typescript@6.0.3)':
-    dependencies:
-      '@typescript-eslint/utils': 5.62.0(eslint@10.6.0(jiti@1.21.7))(typescript@6.0.3)
-      eslint: 10.6.0(jiti@1.21.7)
-      tslib: 2.8.1
-    transitivePeerDependencies:
-      - supports-color
-      - typescript
-
-  '@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15)':
-    dependencies:
-      '@docusaurus/types': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@rspack/core': 1.7.11(@swc/helpers@0.5.23)
-      '@swc/core': 1.15.41(@swc/helpers@0.5.23)
-      '@swc/html': 1.15.40
-      browserslist: 4.28.2
-      lightningcss: 1.32.0
-      semver: 7.8.3
-      swc-loader: 0.2.7(@swc/core@1.15.41(@swc/helpers@0.5.23))(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      tslib: 2.8.1
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(@swc/html@1.15.40)(lightningcss@1.32.0)(postcss@8.5.15)
-    transitivePeerDependencies:
-      - '@minify-html/node'
-      - '@swc/css'
-      - '@swc/helpers'
-      - clean-css
-      - cssnano
-      - csso
-      - esbuild
-      - html-minifier-terser
-      - postcss
-      - uglify-js
-      - webpack-cli
-
-  '@docusaurus/logger@3.10.1':
-    dependencies:
-      chalk: 4.1.2
-      tslib: 2.8.1
-
-  '@docusaurus/mdx-loader@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@docusaurus/logger': 3.10.1
-      '@docusaurus/utils': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils-validation': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@mdx-js/mdx': 3.1.1
-      '@slorber/remark-comment': 1.0.0
-      escape-html: 1.0.3
-      estree-util-value-to-estree: 3.5.0
-      file-loader: 6.2.0(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      fs-extra: 11.3.6
-      image-size: 2.0.2
-      mdast-util-mdx: 3.0.0
-      mdast-util-to-string: 4.0.0
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      rehype-raw: 7.0.0
-      remark-directive: 3.0.1
-      remark-emoji: 4.0.1
-      remark-frontmatter: 5.0.0
-      remark-gfm: 4.0.1
-      stringify-object: 3.3.0
-      tslib: 2.8.1
-      unified: 11.0.5
-      unist-util-visit: 5.1.0
-      url-loader: 4.1.1(file-loader@6.2.0(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)))(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      vfile: 6.0.3
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
-    transitivePeerDependencies:
-      - '@minify-html/node'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - clean-css
-      - cssnano
-      - csso
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - supports-color
-      - uglify-js
-      - webpack-cli
-
-  '@docusaurus/module-type-aliases@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@docusaurus/types': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@types/history': 4.7.11
-      '@types/react': 19.2.17
-      '@types/react-router-config': 5.0.11
-      '@types/react-router-dom': 5.3.3
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      react-helmet-async: '@slorber/react-helmet-async@1.3.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7)'
-      react-loadable: '@docusaurus/react-loadable@6.0.0(react@19.2.7)'
-    transitivePeerDependencies:
-      - '@minify-html/node'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - clean-css
-      - cssnano
-      - csso
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - supports-color
-      - uglify-js
-      - webpack-cli
-
-  '@docusaurus/plugin-content-blog@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@docusaurus/plugin-content-docs@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)':
-    dependencies:
-      '@docusaurus/core': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/logger': 3.10.1
-      '@docusaurus/mdx-loader': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/plugin-content-docs': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/theme-common': 3.10.1(@docusaurus/plugin-content-docs@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/types': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils-common': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils-validation': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      cheerio: 1.0.0-rc.12
-      combine-promises: 1.2.0
-      feed: 4.2.2
-      fs-extra: 11.3.6
-      lodash: 4.18.1
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      schema-dts: 1.1.5
-      srcset: 4.0.0
-      tslib: 2.8.1
-      unist-util-visit: 5.1.0
-      utility-types: 3.11.0
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
-    transitivePeerDependencies:
-      - '@docusaurus/faster'
-      - '@mdx-js/react'
-      - '@minify-html/node'
-      - '@parcel/css'
-      - '@rspack/core'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - bufferutil
-      - clean-css
-      - cssnano
-      - csso
-      - debug
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - supports-color
-      - typescript
-      - uglify-js
-      - utf-8-validate
-      - webpack-cli
-
-  '@docusaurus/plugin-content-docs@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)':
-    dependencies:
-      '@docusaurus/core': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/logger': 3.10.1
-      '@docusaurus/mdx-loader': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/module-type-aliases': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/theme-common': 3.10.1(@docusaurus/plugin-content-docs@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/types': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils-common': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils-validation': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@types/react-router-config': 5.0.11
-      combine-promises: 1.2.0
-      fs-extra: 11.3.6
-      js-yaml: 4.3.1
-      lodash: 4.18.1
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      schema-dts: 1.1.5
-      tslib: 2.8.1
-      utility-types: 3.11.0
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
-    transitivePeerDependencies:
-      - '@docusaurus/faster'
-      - '@mdx-js/react'
-      - '@minify-html/node'
-      - '@parcel/css'
-      - '@rspack/core'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - bufferutil
-      - clean-css
-      - cssnano
-      - csso
-      - debug
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - supports-color
-      - typescript
-      - uglify-js
-      - utf-8-validate
-      - webpack-cli
-
-  '@docusaurus/plugin-content-pages@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)':
-    dependencies:
-      '@docusaurus/core': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/mdx-loader': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/types': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils-validation': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      fs-extra: 11.3.6
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      tslib: 2.8.1
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
-    transitivePeerDependencies:
-      - '@docusaurus/faster'
-      - '@mdx-js/react'
-      - '@minify-html/node'
-      - '@parcel/css'
-      - '@rspack/core'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - bufferutil
-      - clean-css
-      - cssnano
-      - csso
-      - debug
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - supports-color
-      - typescript
-      - uglify-js
-      - utf-8-validate
-      - webpack-cli
-
-  '@docusaurus/plugin-css-cascade-layers@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)':
-    dependencies:
-      '@docusaurus/core': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/types': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils-validation': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      tslib: 2.8.1
-    transitivePeerDependencies:
-      - '@docusaurus/faster'
-      - '@mdx-js/react'
-      - '@minify-html/node'
-      - '@parcel/css'
-      - '@rspack/core'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - bufferutil
-      - clean-css
-      - cssnano
-      - csso
-      - debug
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - react
-      - react-dom
-      - supports-color
-      - typescript
-      - uglify-js
-      - utf-8-validate
-      - webpack-cli
-
-  '@docusaurus/plugin-debug@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)':
-    dependencies:
-      '@docusaurus/core': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/types': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      fs-extra: 11.3.6
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      react-json-view-lite: 2.5.0(react@19.2.7)
-      tslib: 2.8.1
-    transitivePeerDependencies:
-      - '@docusaurus/faster'
-      - '@mdx-js/react'
-      - '@minify-html/node'
-      - '@parcel/css'
-      - '@rspack/core'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - bufferutil
-      - clean-css
-      - cssnano
-      - csso
-      - debug
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - supports-color
-      - typescript
-      - uglify-js
-      - utf-8-validate
-      - webpack-cli
-
-  '@docusaurus/plugin-google-analytics@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)':
-    dependencies:
-      '@docusaurus/core': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/types': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils-validation': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      tslib: 2.8.1
-    transitivePeerDependencies:
-      - '@docusaurus/faster'
-      - '@mdx-js/react'
-      - '@minify-html/node'
-      - '@parcel/css'
-      - '@rspack/core'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - bufferutil
-      - clean-css
-      - cssnano
-      - csso
-      - debug
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - supports-color
-      - typescript
-      - uglify-js
-      - utf-8-validate
-      - webpack-cli
-
-  '@docusaurus/plugin-google-gtag@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)':
-    dependencies:
-      '@docusaurus/core': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/types': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils-validation': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@types/gtag.js': 0.0.20
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      tslib: 2.8.1
-    transitivePeerDependencies:
-      - '@docusaurus/faster'
-      - '@mdx-js/react'
-      - '@minify-html/node'
-      - '@parcel/css'
-      - '@rspack/core'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - bufferutil
-      - clean-css
-      - cssnano
-      - csso
-      - debug
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - supports-color
-      - typescript
-      - uglify-js
-      - utf-8-validate
-      - webpack-cli
-
-  '@docusaurus/plugin-google-tag-manager@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)':
-    dependencies:
-      '@docusaurus/core': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/types': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils-validation': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      tslib: 2.8.1
-    transitivePeerDependencies:
-      - '@docusaurus/faster'
-      - '@mdx-js/react'
-      - '@minify-html/node'
-      - '@parcel/css'
-      - '@rspack/core'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - bufferutil
-      - clean-css
-      - cssnano
-      - csso
-      - debug
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - supports-color
-      - typescript
-      - uglify-js
-      - utf-8-validate
-      - webpack-cli
-
-  '@docusaurus/plugin-sitemap@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)':
-    dependencies:
-      '@docusaurus/core': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/logger': 3.10.1
-      '@docusaurus/types': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils-common': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils-validation': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      fs-extra: 11.3.6
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      sitemap: 7.1.3
-      tslib: 2.8.1
-    transitivePeerDependencies:
-      - '@docusaurus/faster'
-      - '@mdx-js/react'
-      - '@minify-html/node'
-      - '@parcel/css'
-      - '@rspack/core'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - bufferutil
-      - clean-css
-      - cssnano
-      - csso
-      - debug
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - supports-color
-      - typescript
-      - uglify-js
-      - utf-8-validate
-      - webpack-cli
-
-  '@docusaurus/plugin-svgr@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)':
-    dependencies:
-      '@docusaurus/core': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/types': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils-validation': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@svgr/core': 8.1.0(typescript@6.0.3)
-      '@svgr/webpack': 8.1.0(typescript@6.0.3)
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      tslib: 2.8.1
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
-    transitivePeerDependencies:
-      - '@docusaurus/faster'
-      - '@mdx-js/react'
-      - '@minify-html/node'
-      - '@parcel/css'
-      - '@rspack/core'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - bufferutil
-      - clean-css
-      - cssnano
-      - csso
-      - debug
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - supports-color
-      - typescript
-      - uglify-js
-      - utf-8-validate
-      - webpack-cli
-
-  '@docusaurus/preset-classic@3.10.1(@algolia/client-search@5.53.0)(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(@types/react@19.2.17)(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(search-insights@2.17.3)(typescript@6.0.3)':
-    dependencies:
-      '@docusaurus/core': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/plugin-content-blog': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@docusaurus/plugin-content-docs@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/plugin-content-docs': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/plugin-content-pages': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/plugin-css-cascade-layers': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/plugin-debug': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/plugin-google-analytics': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/plugin-google-gtag': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/plugin-google-tag-manager': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/plugin-sitemap': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/plugin-svgr': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/theme-classic': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(@types/react@19.2.17)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/theme-common': 3.10.1(@docusaurus/plugin-content-docs@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/theme-search-algolia': 3.10.1(@algolia/client-search@5.53.0)(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(@types/react@19.2.17)(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(search-insights@2.17.3)(typescript@6.0.3)
-      '@docusaurus/types': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-    transitivePeerDependencies:
-      - '@algolia/client-search'
-      - '@docusaurus/faster'
-      - '@mdx-js/react'
-      - '@minify-html/node'
-      - '@parcel/css'
-      - '@rspack/core'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - '@types/react'
-      - bufferutil
-      - clean-css
-      - cssnano
-      - csso
-      - debug
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - search-insights
-      - supports-color
-      - typescript
-      - uglify-js
-      - utf-8-validate
-      - webpack-cli
-
-  '@docusaurus/react-loadable@6.0.0(react@19.2.7)':
-    dependencies:
-      '@types/react': 19.2.17
-      react: 19.2.7
-
-  '@docusaurus/remark-plugin-npm2yarn@3.10.1':
-    dependencies:
-      mdast-util-mdx: 3.0.0
-      npm-to-yarn: 3.0.1
-      tslib: 2.8.1
-      unified: 11.0.5
-      unist-util-visit: 5.1.0
-    transitivePeerDependencies:
-      - supports-color
-
-  '@docusaurus/theme-classic@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(@types/react@19.2.17)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)':
-    dependencies:
-      '@docusaurus/core': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/logger': 3.10.1
-      '@docusaurus/mdx-loader': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/module-type-aliases': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/plugin-content-blog': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@docusaurus/plugin-content-docs@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/plugin-content-docs': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/plugin-content-pages': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/theme-common': 3.10.1(@docusaurus/plugin-content-docs@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/theme-translations': 3.10.1
-      '@docusaurus/types': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils-common': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils-validation': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@mdx-js/react': 3.1.1(@types/react@19.2.17)(react@19.2.7)
-      clsx: 2.1.1
-      copy-text-to-clipboard: 3.2.2
-      infima: 0.2.0-alpha.45
-      lodash: 4.18.1
-      nprogress: 0.2.0
-      postcss: 8.5.15
-      prism-react-renderer: 2.4.1(react@19.2.7)
-      prismjs: 1.30.0
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      react-router-dom: 5.3.4(react@19.2.7)
-      rtlcss: 4.3.0
-      tslib: 2.8.1
-      utility-types: 3.11.0
-    transitivePeerDependencies:
-      - '@docusaurus/faster'
-      - '@minify-html/node'
-      - '@parcel/css'
-      - '@rspack/core'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - '@types/react'
-      - bufferutil
-      - clean-css
-      - cssnano
-      - csso
-      - debug
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - supports-color
-      - typescript
-      - uglify-js
-      - utf-8-validate
-      - webpack-cli
-
-  '@docusaurus/theme-common@3.10.1(@docusaurus/plugin-content-docs@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@docusaurus/mdx-loader': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/module-type-aliases': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/plugin-content-docs': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/utils': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils-common': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@types/history': 4.7.11
-      '@types/react': 19.2.17
-      '@types/react-router-config': 5.0.11
-      clsx: 2.1.1
-      parse-numeric-range: 1.3.0
-      prism-react-renderer: 2.4.1(react@19.2.7)
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      tslib: 2.8.1
-      utility-types: 3.11.0
-    transitivePeerDependencies:
-      - '@minify-html/node'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - clean-css
-      - cssnano
-      - csso
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - supports-color
-      - uglify-js
-      - webpack-cli
-
-  '@docusaurus/theme-mermaid@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@docusaurus/plugin-content-docs@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)':
-    dependencies:
-      '@docusaurus/core': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/module-type-aliases': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/theme-common': 3.10.1(@docusaurus/plugin-content-docs@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/types': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils-validation': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      mermaid: 11.15.0
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      tslib: 2.8.1
-    transitivePeerDependencies:
-      - '@docusaurus/faster'
-      - '@docusaurus/plugin-content-docs'
-      - '@mdx-js/react'
-      - '@minify-html/node'
-      - '@parcel/css'
-      - '@rspack/core'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - bufferutil
-      - clean-css
-      - cssnano
-      - csso
-      - debug
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - supports-color
-      - typescript
-      - uglify-js
-      - utf-8-validate
-      - webpack-cli
-
-  '@docusaurus/theme-search-algolia@3.10.1(@algolia/client-search@5.53.0)(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(@types/react@19.2.17)(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(search-insights@2.17.3)(typescript@6.0.3)':
-    dependencies:
-      '@algolia/autocomplete-core': 1.19.2(@algolia/client-search@5.53.0)(algoliasearch@5.53.0)(search-insights@2.17.3)
-      '@docsearch/react': 4.6.3(@algolia/client-search@5.53.0)(@types/react@19.2.17)(algoliasearch@5.53.0)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(search-insights@2.17.3)
-      '@docusaurus/core': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/logger': 3.10.1
-      '@docusaurus/plugin-content-docs': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/theme-common': 3.10.1(@docusaurus/plugin-content-docs@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/theme-translations': 3.10.1
-      '@docusaurus/utils': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils-validation': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      algoliasearch: 5.53.0
-      algoliasearch-helper: 3.29.1(algoliasearch@5.53.0)
-      clsx: 2.1.1
-      eta: 2.2.0
-      fs-extra: 11.3.6
-      lodash: 4.18.1
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      tslib: 2.8.1
-      utility-types: 3.11.0
-    transitivePeerDependencies:
-      - '@algolia/client-search'
-      - '@docusaurus/faster'
-      - '@mdx-js/react'
-      - '@minify-html/node'
-      - '@parcel/css'
-      - '@rspack/core'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - '@types/react'
-      - bufferutil
-      - clean-css
-      - cssnano
-      - csso
-      - debug
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - search-insights
-      - supports-color
-      - typescript
-      - uglify-js
-      - utf-8-validate
-      - webpack-cli
-
-  '@docusaurus/theme-translations@3.10.1':
-    dependencies:
-      fs-extra: 11.3.6
-      tslib: 2.8.1
-
-  '@docusaurus/tsconfig@3.10.1': {}
-
-  '@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(clean-css@5.3.3)(cssnano@6.1.2(postcss@8.5.15))(html-minifier-terser@7.2.0)(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@mdx-js/mdx': 3.1.1
-      '@types/history': 4.7.11
-      '@types/mdast': 4.0.4
-      '@types/react': 19.2.17
-      commander: 5.1.0
-      joi: 17.13.3
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      react-helmet-async: '@slorber/react-helmet-async@1.3.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7)'
-      utility-types: 3.11.0
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(clean-css@5.3.3)(cssnano@6.1.2(postcss@8.5.15))(html-minifier-terser@7.2.0)(postcss@8.5.15)
-      webpack-merge: 5.10.0
-    transitivePeerDependencies:
-      - '@minify-html/node'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - clean-css
-      - cssnano
-      - csso
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - supports-color
-      - uglify-js
-      - webpack-cli
-
-  '@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@mdx-js/mdx': 3.1.1
-      '@types/history': 4.7.11
-      '@types/mdast': 4.0.4
-      '@types/react': 19.2.17
-      commander: 5.1.0
-      joi: 17.13.3
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      react-helmet-async: '@slorber/react-helmet-async@1.3.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7)'
-      utility-types: 3.11.0
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
-      webpack-merge: 5.10.0
-    transitivePeerDependencies:
-      - '@minify-html/node'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - clean-css
-      - cssnano
-      - csso
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - supports-color
-      - uglify-js
-      - webpack-cli
-
-  '@docusaurus/utils-common@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(clean-css@5.3.3)(cssnano@6.1.2(postcss@8.5.15))(html-minifier-terser@7.2.0)(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@docusaurus/types': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(clean-css@5.3.3)(cssnano@6.1.2(postcss@8.5.15))(html-minifier-terser@7.2.0)(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      tslib: 2.8.1
-    transitivePeerDependencies:
-      - '@minify-html/node'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - clean-css
-      - cssnano
-      - csso
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - react
-      - react-dom
-      - supports-color
-      - uglify-js
-      - webpack-cli
-
-  '@docusaurus/utils-common@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@docusaurus/types': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      tslib: 2.8.1
-    transitivePeerDependencies:
-      - '@minify-html/node'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - clean-css
-      - cssnano
-      - csso
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - react
-      - react-dom
-      - supports-color
-      - uglify-js
-      - webpack-cli
-
-  '@docusaurus/utils-validation@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@docusaurus/logger': 3.10.1
-      '@docusaurus/utils': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils-common': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      fs-extra: 11.3.6
-      joi: 17.13.3
-      js-yaml: 4.3.1
-      lodash: 4.18.1
-      tslib: 2.8.1
-    transitivePeerDependencies:
-      - '@minify-html/node'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - clean-css
-      - cssnano
-      - csso
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - react
-      - react-dom
-      - supports-color
-      - uglify-js
-      - webpack-cli
-
-  '@docusaurus/utils@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(clean-css@5.3.3)(cssnano@6.1.2(postcss@8.5.15))(html-minifier-terser@7.2.0)(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@docusaurus/logger': 3.10.1
-      '@docusaurus/types': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(clean-css@5.3.3)(cssnano@6.1.2(postcss@8.5.15))(html-minifier-terser@7.2.0)(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils-common': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(clean-css@5.3.3)(cssnano@6.1.2(postcss@8.5.15))(html-minifier-terser@7.2.0)(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      escape-string-regexp: 4.0.0
-      execa: 5.1.1
-      file-loader: 6.2.0(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      fs-extra: 11.3.6
-      github-slugger: 1.5.0
-      globby: 11.1.0
-      gray-matter: 4.0.3
-      jiti: 1.21.7
-      js-yaml: 4.3.1
-      lodash: 4.18.1
-      micromatch: 4.0.8
-      p-queue: 6.6.2
-      prompts: 2.4.2
-      resolve-pathname: 3.0.0
-      tslib: 2.8.1
-      url-loader: 4.1.1(file-loader@6.2.0(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)))(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      utility-types: 3.11.0
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(clean-css@5.3.3)(cssnano@6.1.2(postcss@8.5.15))(html-minifier-terser@7.2.0)(postcss@8.5.15)
-    transitivePeerDependencies:
-      - '@minify-html/node'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - clean-css
-      - cssnano
-      - csso
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - react
-      - react-dom
-      - supports-color
-      - uglify-js
-      - webpack-cli
-
-  '@docusaurus/utils@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@docusaurus/logger': 3.10.1
-      '@docusaurus/types': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils-common': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      escape-string-regexp: 4.0.0
-      execa: 5.1.1
-      file-loader: 6.2.0(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      fs-extra: 11.3.6
-      github-slugger: 1.5.0
-      globby: 11.1.0
-      gray-matter: 4.0.3
-      jiti: 1.21.7
-      js-yaml: 4.3.1
-      lodash: 4.18.1
-      micromatch: 4.0.8
-      p-queue: 6.6.2
-      prompts: 2.4.2
-      resolve-pathname: 3.0.0
-      tslib: 2.8.1
-      url-loader: 4.1.1(file-loader@6.2.0(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)))(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      utility-types: 3.11.0
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
-    transitivePeerDependencies:
-      - '@minify-html/node'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - clean-css
-      - cssnano
-      - csso
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - react
-      - react-dom
-      - supports-color
-      - uglify-js
-      - webpack-cli
-
-  '@emnapi/core@1.11.0':
-    dependencies:
-      '@emnapi/wasi-threads': 1.2.2
-      tslib: 2.8.1
-    optional: true
-
-  '@emnapi/runtime@1.11.0':
-    dependencies:
-      tslib: 2.8.1
-    optional: true
-
-  '@emnapi/wasi-threads@1.2.2':
-    dependencies:
-      tslib: 2.8.1
-    optional: true
-
-  '@eslint-community/eslint-utils@4.10.1(eslint@10.6.0(jiti@1.21.7))':
-    dependencies:
-      eslint: 10.6.0(jiti@1.21.7)
-      eslint-visitor-keys: 3.4.3
-
-  '@eslint-community/eslint-utils@4.9.1(eslint@10.6.0(jiti@1.21.7))':
-    dependencies:
-      eslint: 10.6.0(jiti@1.21.7)
-      eslint-visitor-keys: 3.4.3
-
-  '@eslint-community/regexpp@4.12.2': {}
-
-  '@eslint/config-array@0.23.5':
-    dependencies:
-      '@eslint/object-schema': 3.0.5
-      debug: 4.4.3
-      minimatch: 10.2.5
-    transitivePeerDependencies:
-      - supports-color
-
-  '@eslint/config-helpers@0.6.0':
-    dependencies:
-      '@eslint/core': 1.2.1
-
-  '@eslint/core@1.2.1':
-    dependencies:
-      '@types/json-schema': 7.0.15
-
-  '@eslint/eslintrc@3.3.5':
-    dependencies:
-      ajv: 6.15.0
-      debug: 4.4.3
-      espree: 10.4.0
-      globals: 14.0.0
-      ignore: 5.3.2
-      import-fresh: 3.3.1
-      js-yaml: 4.3.1
-      minimatch: 3.1.5
-      strip-json-comments: 3.1.1
-    transitivePeerDependencies:
-      - supports-color
-
-  '@eslint/js@10.0.1(eslint@10.6.0(jiti@1.21.7))':
-    optionalDependencies:
-      eslint: 10.6.0(jiti@1.21.7)
-
-  '@eslint/object-schema@3.0.5': {}
-
-  '@eslint/plugin-kit@0.7.2':
-    dependencies:
-      '@eslint/core': 1.2.1
-      levn: 0.4.1
-
-  '@exodus/schemasafe@1.3.0': {}
-
-  '@faker-js/faker@5.5.3': {}
-
-  '@fortawesome/fontawesome-common-types@6.7.2': {}
-
-  '@fortawesome/fontawesome-svg-core@6.7.2':
-    dependencies:
-      '@fortawesome/fontawesome-common-types': 6.7.2
-
-  '@fortawesome/react-fontawesome@0.2.6(@fortawesome/fontawesome-svg-core@6.7.2)(react@19.2.7)':
-    dependencies:
-      '@fortawesome/fontawesome-svg-core': 6.7.2
-      prop-types: 15.8.1
-      react: 19.2.7
-
-  '@hapi/hoek@9.3.0': {}
-
-  '@hapi/topo@5.1.0':
-    dependencies:
-      '@hapi/hoek': 9.3.0
-
-  '@hookform/error-message@2.0.1(react-dom@19.2.7(react@19.2.7))(react-hook-form@7.80.0(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      react-hook-form: 7.80.0(react@19.2.7)
-
-  '@humanfs/core@0.19.2':
-    dependencies:
-      '@humanfs/types': 0.15.0
-
-  '@humanfs/node@0.16.8':
-    dependencies:
-      '@humanfs/core': 0.19.2
-      '@humanfs/types': 0.15.0
-      '@humanwhocodes/retry': 0.4.3
-
-  '@humanfs/types@0.15.0': {}
-
-  '@humanwhocodes/module-importer@1.0.1': {}
-
-  '@humanwhocodes/retry@0.4.3': {}
-
-  '@iconify/types@2.0.0': {}
-
-  '@iconify/utils@3.1.3':
-    dependencies:
-      '@antfu/install-pkg': 1.1.0
-      '@iconify/types': 2.0.0
-      import-meta-resolve: 4.2.0
-
-  '@internationalized/date@3.12.2':
-    dependencies:
-      '@swc/helpers': 0.5.23
-
-  '@internationalized/date@3.12.3':
-    dependencies:
-      '@swc/helpers': 0.5.23
-
-  '@internationalized/number@3.6.7':
-    dependencies:
-      '@swc/helpers': 0.5.23
-
-  '@internationalized/string@3.2.10':
-    dependencies:
-      '@swc/helpers': 0.5.23
-
-  '@internationalized/string@3.2.9':
-    dependencies:
-      '@swc/helpers': 0.5.23
-
-  '@jest/schemas@29.6.3':
-    dependencies:
-      '@sinclair/typebox': 0.27.10
-
-  '@jest/types@29.6.3':
-    dependencies:
-      '@jest/schemas': 29.6.3
-      '@types/istanbul-lib-coverage': 2.0.6
-      '@types/istanbul-reports': 3.0.4
-      '@types/node': 25.9.2
-      '@types/yargs': 17.0.35
-      chalk: 4.1.2
-
-  '@jridgewell/gen-mapping@0.3.13':
-    dependencies:
-      '@jridgewell/sourcemap-codec': 1.5.5
-      '@jridgewell/trace-mapping': 0.3.31
-
-  '@jridgewell/remapping@2.3.5':
-    dependencies:
-      '@jridgewell/gen-mapping': 0.3.13
-      '@jridgewell/trace-mapping': 0.3.31
-
-  '@jridgewell/resolve-uri@3.1.2': {}
-
-  '@jridgewell/source-map@0.3.11':
-    dependencies:
-      '@jridgewell/gen-mapping': 0.3.13
-      '@jridgewell/trace-mapping': 0.3.31
-
-  '@jridgewell/sourcemap-codec@1.5.5': {}
-
-  '@jridgewell/trace-mapping@0.3.31':
-    dependencies:
-      '@jridgewell/resolve-uri': 3.1.2
-      '@jridgewell/sourcemap-codec': 1.5.5
-
-  '@json-schema-spec/json-pointer@0.1.2': {}
-
-  '@json-schema-tools/dereferencer@1.6.3':
-    dependencies:
-      '@json-schema-tools/reference-resolver': 1.2.6
-      '@json-schema-tools/traverse': 1.11.0
-      fast-safe-stringify: 2.1.1
-    transitivePeerDependencies:
-      - encoding
-
-  '@json-schema-tools/meta-schema@1.8.0': {}
-
-  '@json-schema-tools/reference-resolver@1.2.6':
-    dependencies:
-      '@json-schema-spec/json-pointer': 0.1.2
-      isomorphic-fetch: 3.0.0
-    transitivePeerDependencies:
-      - encoding
-
-  '@json-schema-tools/traverse@1.11.0': {}
-
-  '@jsonjoy.com/base64@1.1.2(tslib@2.8.1)':
-    dependencies:
-      tslib: 2.8.1
-
-  '@jsonjoy.com/base64@17.67.0(tslib@2.8.1)':
-    dependencies:
-      tslib: 2.8.1
-
-  '@jsonjoy.com/buffers@1.2.1(tslib@2.8.1)':
-    dependencies:
-      tslib: 2.8.1
-
-  '@jsonjoy.com/buffers@17.67.0(tslib@2.8.1)':
-    dependencies:
-      tslib: 2.8.1
-
-  '@jsonjoy.com/codegen@1.0.0(tslib@2.8.1)':
-    dependencies:
-      tslib: 2.8.1
-
-  '@jsonjoy.com/codegen@17.67.0(tslib@2.8.1)':
-    dependencies:
-      tslib: 2.8.1
-
-  '@jsonjoy.com/fs-core@4.57.6(tslib@2.8.1)':
-    dependencies:
-      '@jsonjoy.com/fs-node-builtins': 4.57.6(tslib@2.8.1)
-      '@jsonjoy.com/fs-node-utils': 4.57.6(tslib@2.8.1)
-      thingies: 2.6.0(tslib@2.8.1)
-      tslib: 2.8.1
-
-  '@jsonjoy.com/fs-fsa@4.57.6(tslib@2.8.1)':
-    dependencies:
-      '@jsonjoy.com/fs-core': 4.57.6(tslib@2.8.1)
-      '@jsonjoy.com/fs-node-builtins': 4.57.6(tslib@2.8.1)
-      '@jsonjoy.com/fs-node-utils': 4.57.6(tslib@2.8.1)
-      thingies: 2.6.0(tslib@2.8.1)
-      tslib: 2.8.1
-
-  '@jsonjoy.com/fs-node-builtins@4.57.6(tslib@2.8.1)':
-    dependencies:
-      tslib: 2.8.1
-
-  '@jsonjoy.com/fs-node-to-fsa@4.57.6(tslib@2.8.1)':
-    dependencies:
-      '@jsonjoy.com/fs-fsa': 4.57.6(tslib@2.8.1)
-      '@jsonjoy.com/fs-node-builtins': 4.57.6(tslib@2.8.1)
-      '@jsonjoy.com/fs-node-utils': 4.57.6(tslib@2.8.1)
-      tslib: 2.8.1
-
-  '@jsonjoy.com/fs-node-utils@4.57.6(tslib@2.8.1)':
-    dependencies:
-      '@jsonjoy.com/fs-node-builtins': 4.57.6(tslib@2.8.1)
-      tslib: 2.8.1
-
-  '@jsonjoy.com/fs-node@4.57.6(tslib@2.8.1)':
-    dependencies:
-      '@jsonjoy.com/fs-core': 4.57.6(tslib@2.8.1)
-      '@jsonjoy.com/fs-node-builtins': 4.57.6(tslib@2.8.1)
-      '@jsonjoy.com/fs-node-utils': 4.57.6(tslib@2.8.1)
-      '@jsonjoy.com/fs-print': 4.57.6(tslib@2.8.1)
-      '@jsonjoy.com/fs-snapshot': 4.57.6(tslib@2.8.1)
-      glob-to-regex.js: 1.2.0(tslib@2.8.1)
-      thingies: 2.6.0(tslib@2.8.1)
-      tslib: 2.8.1
-
-  '@jsonjoy.com/fs-print@4.57.6(tslib@2.8.1)':
-    dependencies:
-      '@jsonjoy.com/fs-node-utils': 4.57.6(tslib@2.8.1)
-      tree-dump: 1.1.0(tslib@2.8.1)
-      tslib: 2.8.1
-
-  '@jsonjoy.com/fs-snapshot@4.57.6(tslib@2.8.1)':
-    dependencies:
-      '@jsonjoy.com/buffers': 17.67.0(tslib@2.8.1)
-      '@jsonjoy.com/fs-node-utils': 4.57.6(tslib@2.8.1)
-      '@jsonjoy.com/json-pack': 17.67.0(tslib@2.8.1)
-      '@jsonjoy.com/util': 17.67.0(tslib@2.8.1)
-      tslib: 2.8.1
-
-  '@jsonjoy.com/json-pack@1.21.0(tslib@2.8.1)':
-    dependencies:
-      '@jsonjoy.com/base64': 1.1.2(tslib@2.8.1)
-      '@jsonjoy.com/buffers': 1.2.1(tslib@2.8.1)
-      '@jsonjoy.com/codegen': 1.0.0(tslib@2.8.1)
-      '@jsonjoy.com/json-pointer': 1.0.2(tslib@2.8.1)
-      '@jsonjoy.com/util': 1.9.0(tslib@2.8.1)
-      hyperdyperid: 1.2.0
-      thingies: 2.6.0(tslib@2.8.1)
-      tree-dump: 1.1.0(tslib@2.8.1)
-      tslib: 2.8.1
-
-  '@jsonjoy.com/json-pack@17.67.0(tslib@2.8.1)':
-    dependencies:
-      '@jsonjoy.com/base64': 17.67.0(tslib@2.8.1)
-      '@jsonjoy.com/buffers': 17.67.0(tslib@2.8.1)
-      '@jsonjoy.com/codegen': 17.67.0(tslib@2.8.1)
-      '@jsonjoy.com/json-pointer': 17.67.0(tslib@2.8.1)
-      '@jsonjoy.com/util': 17.67.0(tslib@2.8.1)
-      hyperdyperid: 1.2.0
-      thingies: 2.6.0(tslib@2.8.1)
-      tree-dump: 1.1.0(tslib@2.8.1)
-      tslib: 2.8.1
-
-  '@jsonjoy.com/json-pointer@1.0.2(tslib@2.8.1)':
-    dependencies:
-      '@jsonjoy.com/codegen': 1.0.0(tslib@2.8.1)
-      '@jsonjoy.com/util': 1.9.0(tslib@2.8.1)
-      tslib: 2.8.1
-
-  '@jsonjoy.com/json-pointer@17.67.0(tslib@2.8.1)':
-    dependencies:
-      '@jsonjoy.com/util': 17.67.0(tslib@2.8.1)
-      tslib: 2.8.1
-
-  '@jsonjoy.com/util@1.9.0(tslib@2.8.1)':
-    dependencies:
-      '@jsonjoy.com/buffers': 1.2.1(tslib@2.8.1)
-      '@jsonjoy.com/codegen': 1.0.0(tslib@2.8.1)
-      tslib: 2.8.1
-
-  '@jsonjoy.com/util@17.67.0(tslib@2.8.1)':
-    dependencies:
-      '@jsonjoy.com/buffers': 17.67.0(tslib@2.8.1)
-      '@jsonjoy.com/codegen': 17.67.0(tslib@2.8.1)
-      tslib: 2.8.1
-
-  '@juggle/resize-observer@3.4.0': {}
-
-  '@leichtgewicht/ip-codec@2.0.5': {}
-
-  '@mdx-js/mdx@3.1.1':
-    dependencies:
-      '@types/estree': 1.0.9
-      '@types/estree-jsx': 1.0.5
-      '@types/hast': 3.0.4
-      '@types/mdx': 2.0.14
-      acorn: 8.16.0
-      collapse-white-space: 2.1.0
-      devlop: 1.1.0
-      estree-util-is-identifier-name: 3.0.0
-      estree-util-scope: 1.0.0
-      estree-walker: 3.0.3
-      hast-util-to-jsx-runtime: 2.3.6
-      markdown-extensions: 2.0.0
-      recma-build-jsx: 1.0.0
-      recma-jsx: 1.0.1(acorn@8.16.0)
-      recma-stringify: 1.0.0
-      rehype-recma: 1.0.0
-      remark-mdx: 3.1.1
-      remark-parse: 11.0.0
-      remark-rehype: 11.1.2
-      source-map: 0.7.6
-      unified: 11.0.5
-      unist-util-position-from-estree: 2.0.0
-      unist-util-stringify-position: 4.0.0
-      unist-util-visit: 5.1.0
-      vfile: 6.0.3
-    transitivePeerDependencies:
-      - supports-color
-
-  '@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7)':
-    dependencies:
-      '@types/mdx': 2.0.14
-      '@types/react': 19.2.17
-      react: 19.2.7
-
-  '@mermaid-js/parser@1.1.1':
-    dependencies:
-      '@chevrotain/types': 11.1.2
-
-  '@module-federation/error-codes@0.22.0': {}
-
-  '@module-federation/runtime-core@0.22.0':
-    dependencies:
-      '@module-federation/error-codes': 0.22.0
-      '@module-federation/sdk': 0.22.0
-
-  '@module-federation/runtime-tools@0.22.0':
-    dependencies:
-      '@module-federation/runtime': 0.22.0
-      '@module-federation/webpack-bundler-runtime': 0.22.0
-
-  '@module-federation/runtime@0.22.0':
-    dependencies:
-      '@module-federation/error-codes': 0.22.0
-      '@module-federation/runtime-core': 0.22.0
-      '@module-federation/sdk': 0.22.0
-
-  '@module-federation/sdk@0.22.0': {}
-
-  '@module-federation/webpack-bundler-runtime@0.22.0':
-    dependencies:
-      '@module-federation/runtime': 0.22.0
-      '@module-federation/sdk': 0.22.0
-
-  '@napi-rs/wasm-runtime@1.0.7':
-    dependencies:
-      '@emnapi/core': 1.11.0
-      '@emnapi/runtime': 1.11.0
-      '@tybys/wasm-util': 0.10.2
-    optional: true
-
-  '@noble/hashes@1.4.0': {}
-
-  '@nodelib/fs.scandir@2.1.5':
-    dependencies:
-      '@nodelib/fs.stat': 2.0.5
-      run-parallel: 1.2.0
-
-  '@nodelib/fs.stat@2.0.5': {}
-
-  '@nodelib/fs.walk@1.2.8':
-    dependencies:
-      '@nodelib/fs.scandir': 2.1.5
-      fastq: 1.20.1
-
-  '@open-rpc/examples@1.7.2': {}
-
-  '@open-rpc/meta-schema@1.14.9': {}
-
-  '@open-rpc/schema-utils-js@2.2.1':
-    dependencies:
-      '@json-schema-tools/dereferencer': 1.6.3
-      '@json-schema-tools/meta-schema': 1.8.0
-      '@json-schema-tools/reference-resolver': 1.2.6
-      '@open-rpc/spec-types': 0.0.2
-      '@open-rpc/specification-extension-spec': 1.0.2
-      ajv: 6.15.0
-      detect-node: 2.1.0
-      fast-safe-stringify: 2.1.1
-      fs-extra: 10.1.0
-      is-url: 1.2.4
-      isomorphic-fetch: 3.0.0
-    transitivePeerDependencies:
-      - encoding
-
-  '@open-rpc/spec-types@0.0.2':
-    dependencies:
-      '@open-rpc/spec': 1.4.1
-
-  '@open-rpc/spec@1.4.1': {}
-
-  '@open-rpc/specification-extension-spec@1.0.2': {}
-
-  '@parcel/watcher-android-arm64@2.5.6':
-    optional: true
-
-  '@parcel/watcher-darwin-arm64@2.5.6':
-    optional: true
-
-  '@parcel/watcher-darwin-x64@2.5.6':
-    optional: true
-
-  '@parcel/watcher-freebsd-x64@2.5.6':
-    optional: true
-
-  '@parcel/watcher-linux-arm-glibc@2.5.6':
-    optional: true
-
-  '@parcel/watcher-linux-arm-musl@2.5.6':
-    optional: true
-
-  '@parcel/watcher-linux-arm64-glibc@2.5.6':
-    optional: true
-
-  '@parcel/watcher-linux-arm64-musl@2.5.6':
-    optional: true
-
-  '@parcel/watcher-linux-x64-glibc@2.5.6':
-    optional: true
-
-  '@parcel/watcher-linux-x64-musl@2.5.6':
-    optional: true
-
-  '@parcel/watcher-win32-arm64@2.5.6':
-    optional: true
-
-  '@parcel/watcher-win32-ia32@2.5.6':
-    optional: true
-
-  '@parcel/watcher-win32-x64@2.5.6':
-    optional: true
-
-  '@parcel/watcher@2.5.6':
-    dependencies:
-      detect-libc: 2.1.2
-      is-glob: 4.0.3
-      node-addon-api: 7.1.1
-      picomatch: 4.0.4
-    optionalDependencies:
-      '@parcel/watcher-android-arm64': 2.5.6
-      '@parcel/watcher-darwin-arm64': 2.5.6
-      '@parcel/watcher-darwin-x64': 2.5.6
-      '@parcel/watcher-freebsd-x64': 2.5.6
-      '@parcel/watcher-linux-arm-glibc': 2.5.6
-      '@parcel/watcher-linux-arm-musl': 2.5.6
-      '@parcel/watcher-linux-arm64-glibc': 2.5.6
-      '@parcel/watcher-linux-arm64-musl': 2.5.6
-      '@parcel/watcher-linux-x64-glibc': 2.5.6
-      '@parcel/watcher-linux-x64-musl': 2.5.6
-      '@parcel/watcher-win32-arm64': 2.5.6
-      '@parcel/watcher-win32-ia32': 2.5.6
-      '@parcel/watcher-win32-x64': 2.5.6
-    optional: true
-
-  '@peculiar/asn1-cms@2.7.0':
-    dependencies:
-      '@peculiar/asn1-schema': 2.7.0
-      '@peculiar/asn1-x509': 2.7.0
-      '@peculiar/asn1-x509-attr': 2.7.0
-      asn1js: 3.0.10
-      tslib: 2.8.1
-
-  '@peculiar/asn1-csr@2.7.0':
-    dependencies:
-      '@peculiar/asn1-schema': 2.7.0
-      '@peculiar/asn1-x509': 2.7.0
-      asn1js: 3.0.10
-      tslib: 2.8.1
-
-  '@peculiar/asn1-ecc@2.7.0':
-    dependencies:
-      '@peculiar/asn1-schema': 2.7.0
-      '@peculiar/asn1-x509': 2.7.0
-      asn1js: 3.0.10
-      tslib: 2.8.1
-
-  '@peculiar/asn1-pfx@2.7.0':
-    dependencies:
-      '@peculiar/asn1-cms': 2.7.0
-      '@peculiar/asn1-pkcs8': 2.7.0
-      '@peculiar/asn1-rsa': 2.7.0
-      '@peculiar/asn1-schema': 2.7.0
-      asn1js: 3.0.10
-      tslib: 2.8.1
-
-  '@peculiar/asn1-pkcs8@2.7.0':
-    dependencies:
-      '@peculiar/asn1-schema': 2.7.0
-      '@peculiar/asn1-x509': 2.7.0
-      asn1js: 3.0.10
-      tslib: 2.8.1
-
-  '@peculiar/asn1-pkcs9@2.7.0':
-    dependencies:
-      '@peculiar/asn1-cms': 2.7.0
-      '@peculiar/asn1-pfx': 2.7.0
-      '@peculiar/asn1-pkcs8': 2.7.0
-      '@peculiar/asn1-schema': 2.7.0
-      '@peculiar/asn1-x509': 2.7.0
-      '@peculiar/asn1-x509-attr': 2.7.0
-      asn1js: 3.0.10
-      tslib: 2.8.1
-
-  '@peculiar/asn1-rsa@2.7.0':
-    dependencies:
-      '@peculiar/asn1-schema': 2.7.0
-      '@peculiar/asn1-x509': 2.7.0
-      asn1js: 3.0.10
-      tslib: 2.8.1
-
-  '@peculiar/asn1-schema@2.7.0':
-    dependencies:
-      '@peculiar/utils': 2.0.3
-      asn1js: 3.0.10
-      tslib: 2.8.1
-
-  '@peculiar/asn1-x509-attr@2.7.0':
-    dependencies:
-      '@peculiar/asn1-schema': 2.7.0
-      '@peculiar/asn1-x509': 2.7.0
-      asn1js: 3.0.10
-      tslib: 2.8.1
-
-  '@peculiar/asn1-x509@2.7.0':
-    dependencies:
-      '@peculiar/asn1-schema': 2.7.0
-      '@peculiar/utils': 2.0.3
-      asn1js: 3.0.10
-      tslib: 2.8.1
-
-  '@peculiar/utils@2.0.3':
-    dependencies:
-      tslib: 2.8.1
-
-  '@peculiar/x509@1.14.3':
-    dependencies:
-      '@peculiar/asn1-cms': 2.7.0
-      '@peculiar/asn1-csr': 2.7.0
-      '@peculiar/asn1-ecc': 2.7.0
-      '@peculiar/asn1-pkcs9': 2.7.0
-      '@peculiar/asn1-rsa': 2.7.0
-      '@peculiar/asn1-schema': 2.7.0
-      '@peculiar/asn1-x509': 2.7.0
-      pvtsutils: 1.3.6
-      reflect-metadata: 0.2.2
-      tslib: 2.8.1
-      tsyringe: 4.10.0
-
-  '@pnpm/config.env-replace@1.1.0': {}
-
-  '@pnpm/network.ca-file@1.0.2':
-    dependencies:
-      graceful-fs: 4.2.10
-
-  '@pnpm/npm-conf@3.0.2':
-    dependencies:
-      '@pnpm/config.env-replace': 1.1.0
-      '@pnpm/network.ca-file': 1.0.2
-      config-chain: 1.1.13
-
-  '@polka/url@1.0.0-next.29': {}
-
-  '@react-aria/checkbox@3.17.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@swc/helpers': 0.5.23
-      react: 19.2.7
-      react-aria: 3.49.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      react-dom: 19.2.7(react@19.2.7)
-
-  '@react-aria/toggle@3.13.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@swc/helpers': 0.5.23
-      react: 19.2.7
-      react-aria: 3.49.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      react-dom: 19.2.7(react@19.2.7)
-
-  '@react-hook/debounce@3.0.0(react@19.2.7)':
-    dependencies:
-      '@react-hook/latest': 1.0.3(react@19.2.7)
-      react: 19.2.7
-
-  '@react-hook/event@1.2.6(react@19.2.7)':
-    dependencies:
-      react: 19.2.7
-
-  '@react-hook/latest@1.0.3(react@19.2.7)':
-    dependencies:
-      react: 19.2.7
-
-  '@react-hook/passive-layout-effect@1.2.1(react@19.2.7)':
-    dependencies:
-      react: 19.2.7
-
-  '@react-hook/resize-observer@1.2.6(react@19.2.7)':
-    dependencies:
-      '@juggle/resize-observer': 3.4.0
-      '@react-hook/latest': 1.0.3(react@19.2.7)
-      '@react-hook/passive-layout-effect': 1.2.1(react@19.2.7)
-      react: 19.2.7
-
-  '@react-hook/size@2.1.2(react@19.2.7)':
-    dependencies:
-      '@react-hook/passive-layout-effect': 1.2.1(react@19.2.7)
-      '@react-hook/resize-observer': 1.2.6(react@19.2.7)
-      react: 19.2.7
-
-  '@react-hook/throttle@2.2.0(react@19.2.7)':
-    dependencies:
-      '@react-hook/latest': 1.0.3(react@19.2.7)
-      react: 19.2.7
-
-  '@react-hook/window-size@3.1.1(react@19.2.7)':
-    dependencies:
-      '@react-hook/debounce': 3.0.0(react@19.2.7)
-      '@react-hook/event': 1.2.6(react@19.2.7)
-      '@react-hook/throttle': 2.2.0(react@19.2.7)
-      react: 19.2.7
-
-  '@react-spectrum/checkbox@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@adobe/react-spectrum': 3.47.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@swc/helpers': 0.5.23
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-
-  '@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@adobe/react-spectrum': 3.47.3(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@swc/helpers': 0.5.23
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-
-  '@react-stately/checkbox@3.8.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@swc/helpers': 0.5.23
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      react-stately: 3.47.0(react@19.2.7)
-
-  '@react-stately/toggle@3.10.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@swc/helpers': 0.5.23
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      react-stately: 3.47.0(react@19.2.7)
-
-  '@react-types/button@3.4.1(react@19.2.7)':
-    dependencies:
-      '@react-types/shared': 3.9.0(react@19.2.7)
-      react: 19.2.7
-
-  '@react-types/checkbox@3.11.0(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@react-aria/checkbox': 3.17.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@react-aria/toggle': 3.13.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@react-spectrum/checkbox': 3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@react-spectrum/provider': 3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@react-stately/checkbox': 3.8.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@react-stately/toggle': 3.10.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-
-  '@react-types/radio@3.1.2(react@19.2.7)':
-    dependencies:
-      '@react-types/shared': 3.9.0(react@19.2.7)
-      react: 19.2.7
-
-  '@react-types/shared@3.35.0(react@19.2.7)':
-    dependencies:
-      react: 19.2.7
-
-  '@react-types/shared@3.36.1(react@19.2.7)':
-    dependencies:
-      react: 19.2.7
-
-  '@react-types/shared@3.9.0(react@19.2.7)':
-    dependencies:
-      react: 19.2.7
-
-  '@react-types/switch@3.1.2(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@react-types/checkbox': 3.11.0(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@react-types/shared': 3.9.0(react@19.2.7)
-      react: 19.2.7
-    transitivePeerDependencies:
-      - '@react-spectrum/provider'
-      - react-dom
-
-  '@react-types/textfield@3.3.0(react@19.2.7)':
-    dependencies:
-      '@react-types/shared': 3.9.0(react@19.2.7)
-      react: 19.2.7
-
-  '@redocly/ajv@8.18.1':
-    dependencies:
-      fast-deep-equal: 3.1.3
-      fast-uri: 3.1.5
-      json-schema-traverse: 1.0.0
-      require-from-string: 2.0.2
-
-  '@redocly/ajv@8.18.3':
-    dependencies:
-      fast-deep-equal: 3.1.3
-      fast-uri: 3.1.3
-      json-schema-traverse: 1.0.0
-      require-from-string: 2.0.2
-
-  '@redocly/cli@2.38.0': {}
-
-  '@redocly/config@0.49.1':
-    dependencies:
-      json-schema-to-ts: 2.7.2
-
-  '@redocly/openapi-core@2.36.0':
-    dependencies:
-      '@redocly/ajv': 8.18.3
-      '@redocly/config': 0.49.1
-      ajv: '@redocly/ajv@8.18.1'
-      ajv-formats: 3.0.1(@redocly/ajv@8.18.1)
-      colorette: 1.4.0
-      js-levenshtein: 1.1.6
-      js-yaml: 4.3.1
-      picomatch: 4.0.4
-      pluralize: 8.0.0
-      yaml-ast-parser: 0.0.43
-
-  '@reduxjs/toolkit@2.12.0(react-redux@9.3.0(@types/react@19.2.17)(react@19.2.7)(redux@5.0.1))(react@19.2.7)':
-    dependencies:
-      '@standard-schema/spec': 1.1.0
-      '@standard-schema/utils': 0.3.0
-      immer: 11.1.9
-      redux: 5.0.1
-      redux-thunk: 3.1.0(redux@5.0.1)
-      reselect: 5.2.0
-    optionalDependencies:
-      react: 19.2.7
-      react-redux: 9.3.0(@types/react@19.2.17)(react@19.2.7)(redux@5.0.1)
-
-  '@rehooks/component-size@1.0.3(react@19.2.7)':
-    dependencies:
-      react: 19.2.7
-
-  '@rjsf/core@5.24.13(@rjsf/utils@5.24.13(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@rjsf/utils': 5.24.13(react@19.2.7)
-      lodash: 4.18.1
-      lodash-es: 4.18.1
-      markdown-to-jsx: 7.7.17(react@19.2.7)
-      prop-types: 15.8.1
-      react: 19.2.7
-
-  '@rjsf/utils@5.24.13(react@19.2.7)':
-    dependencies:
-      json-schema-merge-allof: 0.8.1
-      jsonpointer: 5.0.1
-      lodash: 4.18.1
-      lodash-es: 4.18.1
-      react: 19.2.7
-      react-is: 18.3.1
-
-  '@rjsf/validator-ajv8@5.24.13(@rjsf/utils@5.24.13(react@19.2.7))':
-    dependencies:
-      '@rjsf/utils': 5.24.13(react@19.2.7)
-      ajv: 8.20.0
-      ajv-formats: 2.1.1(ajv@8.20.0)
-      lodash: 4.18.1
-      lodash-es: 4.18.1
-
-  '@rspack/binding-darwin-arm64@1.7.11':
-    optional: true
-
-  '@rspack/binding-darwin-x64@1.7.11':
-    optional: true
-
-  '@rspack/binding-linux-arm64-gnu@1.7.11':
-    optional: true
-
-  '@rspack/binding-linux-arm64-musl@1.7.11':
-    optional: true
-
-  '@rspack/binding-linux-x64-gnu@1.7.11':
-    optional: true
-
-  '@rspack/binding-linux-x64-musl@1.7.11':
-    optional: true
-
-  '@rspack/binding-wasm32-wasi@1.7.11':
-    dependencies:
-      '@napi-rs/wasm-runtime': 1.0.7
-    optional: true
-
-  '@rspack/binding-win32-arm64-msvc@1.7.11':
-    optional: true
-
-  '@rspack/binding-win32-ia32-msvc@1.7.11':
-    optional: true
-
-  '@rspack/binding-win32-x64-msvc@1.7.11':
-    optional: true
-
-  '@rspack/binding@1.7.11':
-    optionalDependencies:
-      '@rspack/binding-darwin-arm64': 1.7.11
-      '@rspack/binding-darwin-x64': 1.7.11
-      '@rspack/binding-linux-arm64-gnu': 1.7.11
-      '@rspack/binding-linux-arm64-musl': 1.7.11
-      '@rspack/binding-linux-x64-gnu': 1.7.11
-      '@rspack/binding-linux-x64-musl': 1.7.11
-      '@rspack/binding-wasm32-wasi': 1.7.11
-      '@rspack/binding-win32-arm64-msvc': 1.7.11
-      '@rspack/binding-win32-ia32-msvc': 1.7.11
-      '@rspack/binding-win32-x64-msvc': 1.7.11
-
-  '@rspack/core@1.7.11(@swc/helpers@0.5.23)':
-    dependencies:
-      '@module-federation/runtime-tools': 0.22.0
-      '@rspack/binding': 1.7.11
-      '@rspack/lite-tapable': 1.1.0
-    optionalDependencies:
-      '@swc/helpers': 0.5.23
-
-  '@rspack/lite-tapable@1.1.0': {}
-
-  '@sentry/browser@6.19.7':
-    dependencies:
-      '@sentry/core': 6.19.7
-      '@sentry/types': 6.19.7
-      '@sentry/utils': 6.19.7
-      tslib: 1.14.1
-
-  '@sentry/core@6.19.7':
-    dependencies:
-      '@sentry/hub': 6.19.7
-      '@sentry/minimal': 6.19.7
-      '@sentry/types': 6.19.7
-      '@sentry/utils': 6.19.7
-      tslib: 1.14.1
-
-  '@sentry/hub@6.19.7':
-    dependencies:
-      '@sentry/types': 6.19.7
-      '@sentry/utils': 6.19.7
-      tslib: 1.14.1
-
-  '@sentry/minimal@6.19.7':
-    dependencies:
-      '@sentry/hub': 6.19.7
-      '@sentry/types': 6.19.7
-      tslib: 1.14.1
-
-  '@sentry/react@6.19.7(react@19.2.7)':
-    dependencies:
-      '@sentry/browser': 6.19.7
-      '@sentry/minimal': 6.19.7
-      '@sentry/types': 6.19.7
-      '@sentry/utils': 6.19.7
-      hoist-non-react-statics: 3.3.2
-      react: 19.2.7
-      tslib: 1.14.1
-
-  '@sentry/types@6.19.7': {}
-
-  '@sentry/utils@6.19.7':
-    dependencies:
-      '@sentry/types': 6.19.7
-      tslib: 1.14.1
-
-  '@sideway/address@4.1.5':
-    dependencies:
-      '@hapi/hoek': 9.3.0
-
-  '@sideway/formula@3.0.1': {}
-
-  '@sideway/pinpoint@2.0.0': {}
-
-  '@sinclair/typebox@0.27.10': {}
-
-  '@sindresorhus/is@4.6.0': {}
-
-  '@sindresorhus/is@5.6.0': {}
-
-  '@slorber/react-helmet-async@1.3.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@babel/runtime': 7.29.7
-      invariant: 2.2.4
-      prop-types: 15.8.1
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      react-fast-compare: 3.2.2
-      shallowequal: 1.1.0
-
-  '@slorber/remark-comment@1.0.0':
-    dependencies:
-      micromark-factory-space: 1.1.0
-      micromark-util-character: 1.2.0
-      micromark-util-symbol: 1.1.0
-
-  '@spectrum-icons/ui@3.7.1(@adobe/react-spectrum@3.47.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@adobe/react-spectrum': 3.47.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@adobe/react-spectrum-ui': 1.2.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@babel/runtime': 7.29.7
-      '@swc/helpers': 0.5.23
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-
-  '@spectrum-icons/ui@3.7.1(@adobe/react-spectrum@3.47.3(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@adobe/react-spectrum': 3.47.3(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@adobe/react-spectrum-ui': 1.2.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@babel/runtime': 7.29.7
-      '@swc/helpers': 0.5.23
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-
-  '@spectrum-icons/workflow@4.3.1(@adobe/react-spectrum@3.47.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@adobe/react-spectrum': 3.47.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@adobe/react-spectrum-workflow': 2.3.5(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@swc/helpers': 0.5.23
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-
-  '@spectrum-icons/workflow@4.3.1(@adobe/react-spectrum@3.47.3(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@adobe/react-spectrum': 3.47.3(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@adobe/react-spectrum-workflow': 2.3.5(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@swc/helpers': 0.5.23
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-
-  '@standard-schema/spec@1.1.0': {}
-
-  '@standard-schema/utils@0.3.0': {}
-
-  '@stellar/open-rpc-docs-react@0.2.1(@babel/core@7.29.7)(@babel/template@7.29.7)(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@types/react@19.2.17)(@typescript-eslint/eslint-plugin@7.18.0(@typescript-eslint/parser@7.18.0(eslint@10.6.0(jiti@1.21.7))(typescript@6.0.3))(eslint@10.6.0(jiti@1.21.7))(typescript@6.0.3))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@json-schema-tools/traverse': 1.11.0
-      '@open-rpc/examples': 1.7.2
-      '@rjsf/core': 5.24.13(@rjsf/utils@5.24.13(react@19.2.7))(react@19.2.7)
-      '@rjsf/utils': 5.24.13(react@19.2.7)
-      '@rjsf/validator-ajv8': 5.24.13(@rjsf/utils@5.24.13(react@19.2.7))
-      '@stoplight/json-schema-viewer': 4.16.4(patch_hash=5a7a1068966aaefd9a8a44d9974257213a8072c19733ed2785768c81e87b32c2)(@babel/core@7.29.7)(@babel/template@7.29.7)(@stoplight/markdown-viewer@5.7.1(@stoplight/mosaic-code-viewer@1.53.5(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@stoplight/mosaic@1.53.5(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@stoplight/mosaic-code-viewer@1.53.5(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@stoplight/mosaic@1.53.5(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@stoplight/markdown-viewer': 5.7.1(@stoplight/mosaic-code-viewer@1.53.5(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@stoplight/mosaic@1.53.5(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@stoplight/mosaic': 1.53.5(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@stoplight/mosaic-code-viewer': 1.53.5(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@typescript-eslint/eslint-plugin': 7.18.0(@typescript-eslint/parser@7.18.0(eslint@10.6.0(jiti@1.21.7))(typescript@6.0.3))(eslint@10.6.0(jiti@1.21.7))(typescript@6.0.3)
-      hash-color-material: 1.1.3
-      lodash: 4.18.1
-      postcss: 8.5.15
-      qs: 6.15.2
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      react-markdown: 8.0.7(@types/react@19.2.17)(react@19.2.7)
-      react-syntax-highlighter: 15.6.6(react@19.2.7)
-    transitivePeerDependencies:
-      - '@babel/core'
-      - '@babel/template'
-      - '@react-spectrum/provider'
-      - '@types/react'
-      - jotai-devtools
-      - jotai-immer
-      - jotai-optics
-      - jotai-redux
-      - jotai-tanstack-query
-      - jotai-urql
-      - jotai-valtio
-      - jotai-xstate
-      - jotai-zustand
-      - supports-color
-
-  '@stellar/prettier-config@1.2.0(prettier@3.9.4)':
-    dependencies:
-      prettier: 3.9.4
-
-  '@stoplight/json-schema-merge-allof@0.8.0':
-    dependencies:
-      compute-lcm: 1.1.2
-      json-schema-compare: 0.2.2
-      lodash: 4.18.1
-
-  '@stoplight/json-schema-tree@4.0.0':
-    dependencies:
-      '@stoplight/json': 3.21.7
-      '@stoplight/json-schema-merge-allof': 0.8.0
-      '@stoplight/lifecycle': 2.3.3
-      '@types/json-schema': 7.0.15
-      magic-error: 0.0.1
-
-  '@stoplight/json-schema-viewer@4.16.4(patch_hash=5a7a1068966aaefd9a8a44d9974257213a8072c19733ed2785768c81e87b32c2)(@babel/core@7.29.7)(@babel/template@7.29.7)(@stoplight/markdown-viewer@5.7.1(@stoplight/mosaic-code-viewer@1.53.5(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@stoplight/mosaic@1.53.5(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@stoplight/mosaic-code-viewer@1.53.5(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@stoplight/mosaic@1.53.5(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@stoplight/json': 3.21.7
-      '@stoplight/json-schema-tree': 4.0.0
-      '@stoplight/markdown-viewer': 5.7.1(@stoplight/mosaic-code-viewer@1.53.5(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@stoplight/mosaic@1.53.5(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@stoplight/mosaic': 1.53.5(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@stoplight/mosaic-code-viewer': 1.53.5(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@stoplight/react-error-boundary': 2.0.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@types/json-schema': 7.0.15
-      classnames: 2.5.1
-      fnv-plus: 1.3.1
-      jotai: 1.13.1(@babel/core@7.29.7)(@babel/template@7.29.7)(react@19.2.7)
-      lodash: 4.18.1
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-    transitivePeerDependencies:
-      - '@babel/core'
-      - '@babel/template'
-      - jotai-devtools
-      - jotai-immer
-      - jotai-optics
-      - jotai-redux
-      - jotai-tanstack-query
-      - jotai-urql
-      - jotai-valtio
-      - jotai-xstate
-      - jotai-zustand
-
-  '@stoplight/json@3.21.7':
-    dependencies:
-      '@stoplight/ordered-object-literal': 1.0.5
-      '@stoplight/path': 1.3.2
-      '@stoplight/types': 13.20.0
-      jsonc-parser: 2.2.1
-      lodash: 4.18.1
-      safe-stable-stringify: 1.1.1
-
-  '@stoplight/lifecycle@2.3.3':
-    dependencies:
-      tslib: 2.8.1
-      wolfy87-eventemitter: 5.2.9
-
-  '@stoplight/markdown-viewer@5.7.1(@stoplight/mosaic-code-viewer@1.53.5(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@stoplight/mosaic@1.53.5(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@rehooks/component-size': 1.0.3(react@19.2.7)
-      '@stoplight/markdown': 3.2.0
-      '@stoplight/mosaic': 1.53.5(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@stoplight/mosaic-code-viewer': 1.53.5(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@stoplight/react-error-boundary': 2.0.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      deepmerge: 4.3.1
-      hast-to-hyperscript: 10.0.3
-      hast-util-raw: 7.0.0
-      hast-util-sanitize: 4.1.0
-      hastscript: 7.2.0
-      mdast-util-to-hast: 11.3.0
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      remark-parse: 9.0.0
-      unified: 9.2.2
-      unist-builder: 3.0.1
-      unist-util-select: 4.0.3
-      unist-util-visit: 3.1.0
-    transitivePeerDependencies:
-      - supports-color
-
-  '@stoplight/markdown@3.2.0':
-    dependencies:
-      '@stoplight/types': 12.5.0
-      '@stoplight/yaml': 4.3.0
-      github-slugger: 1.5.0
-      hast-util-whitespace: 2.0.1
-      lodash: 4.18.1
-      mdast-util-to-string: 3.2.0
-      remark-frontmatter: 3.0.0
-      remark-gfm: 1.0.0
-      remark-parse: 9.0.0
-      remark-stringify: 9.0.1
-      tslib: 2.8.1
-      unified: 9.2.2
-      unist-util-select: 4.0.3
-      unist-util-visit: 3.1.0
-    transitivePeerDependencies:
-      - supports-color
-
-  '@stoplight/mosaic-code-viewer@1.53.5(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@fortawesome/fontawesome-svg-core': 6.7.2
-      '@fortawesome/react-fontawesome': 0.2.6(@fortawesome/fontawesome-svg-core@6.7.2)(react@19.2.7)
-      '@react-hook/size': 2.1.2(react@19.2.7)
-      '@react-hook/window-size': 3.1.1(react@19.2.7)
-      '@react-types/radio': 3.1.2(react@19.2.7)
-      '@react-types/shared': 3.9.0(react@19.2.7)
-      '@react-types/switch': 3.1.2(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@stoplight/mosaic': 1.53.5(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@stoplight/types': 13.20.0
-      clsx: 1.2.1
-      copy-to-clipboard: 3.3.3
-      dom-helpers: 3.4.0
-      lodash.get: 4.4.2
-      nano-memoize: 1.3.1
-      polished: 4.3.1
-      prism-react-renderer: 1.3.5(react@19.2.7)
-      prismjs: 1.30.0
-      react: 19.2.7
-      react-fast-compare: 3.2.2
-      react-overflow-list: 0.5.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      ts-keycode-enum: 1.0.6
-      tslib: 2.8.1
-      use-resize-observer: 9.1.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      zustand: 3.7.2(react@19.2.7)
-    transitivePeerDependencies:
-      - '@react-spectrum/provider'
-      - react-dom
-
-  '@stoplight/mosaic@1.53.5(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@fortawesome/fontawesome-svg-core': 6.7.2
-      '@fortawesome/react-fontawesome': 0.2.6(@fortawesome/fontawesome-svg-core@6.7.2)(react@19.2.7)
-      '@react-hook/size': 2.1.2(react@19.2.7)
-      '@react-hook/window-size': 3.1.1(react@19.2.7)
-      '@react-types/button': 3.4.1(react@19.2.7)
-      '@react-types/radio': 3.1.2(react@19.2.7)
-      '@react-types/shared': 3.9.0(react@19.2.7)
-      '@react-types/switch': 3.1.2(@react-spectrum/provider@3.11.1(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@react-types/textfield': 3.3.0(react@19.2.7)
-      '@stoplight/types': 13.20.0
-      '@types/react': 17.0.93
-      '@types/react-dom': 17.0.26(@types/react@17.0.93)
-      clsx: 1.2.1
-      copy-to-clipboard: 3.3.3
-      dom-helpers: 3.4.0
-      lodash.get: 4.4.2
-      nano-memoize: 1.3.1
-      polished: 4.3.1
-      react: 19.2.7
-      react-fast-compare: 3.2.2
-      react-overflow-list: 0.5.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      ts-keycode-enum: 1.0.6
-      tslib: 2.8.1
-      use-resize-observer: 9.1.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      zustand: 3.7.2(react@19.2.7)
-    transitivePeerDependencies:
-      - '@react-spectrum/provider'
-      - react-dom
-
-  '@stoplight/ordered-object-literal@1.0.5': {}
-
-  '@stoplight/path@1.3.2': {}
-
-  '@stoplight/react-error-boundary@2.0.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7)':
-    dependencies:
-      '@sentry/react': 6.19.7(react@19.2.7)
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-
-  '@stoplight/types@12.5.0':
-    dependencies:
-      '@types/json-schema': 7.0.15
-      utility-types: 3.11.0
-
-  '@stoplight/types@13.20.0':
-    dependencies:
-      '@types/json-schema': 7.0.15
-      utility-types: 3.11.0
-
-  '@stoplight/types@14.1.1':
-    dependencies:
-      '@types/json-schema': 7.0.15
-      utility-types: 3.11.0
-
-  '@stoplight/yaml-ast-parser@0.0.50': {}
-
-  '@stoplight/yaml@4.3.0':
-    dependencies:
-      '@stoplight/ordered-object-literal': 1.0.5
-      '@stoplight/types': 14.1.1
-      '@stoplight/yaml-ast-parser': 0.0.50
-      tslib: 2.8.1
-
-  '@svgr/babel-plugin-add-jsx-attribute@8.0.0(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-
-  '@svgr/babel-plugin-remove-jsx-attribute@8.0.0(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-
-  '@svgr/babel-plugin-remove-jsx-empty-expression@8.0.0(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-
-  '@svgr/babel-plugin-replace-jsx-attribute-value@8.0.0(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-
-  '@svgr/babel-plugin-svg-dynamic-title@8.0.0(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-
-  '@svgr/babel-plugin-svg-em-dimensions@8.0.0(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-
-  '@svgr/babel-plugin-transform-react-native-svg@8.1.0(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-
-  '@svgr/babel-plugin-transform-svg-component@8.0.0(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-
-  '@svgr/babel-preset@8.1.0(@babel/core@7.29.7)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@svgr/babel-plugin-add-jsx-attribute': 8.0.0(@babel/core@7.29.7)
-      '@svgr/babel-plugin-remove-jsx-attribute': 8.0.0(@babel/core@7.29.7)
-      '@svgr/babel-plugin-remove-jsx-empty-expression': 8.0.0(@babel/core@7.29.7)
-      '@svgr/babel-plugin-replace-jsx-attribute-value': 8.0.0(@babel/core@7.29.7)
-      '@svgr/babel-plugin-svg-dynamic-title': 8.0.0(@babel/core@7.29.7)
-      '@svgr/babel-plugin-svg-em-dimensions': 8.0.0(@babel/core@7.29.7)
-      '@svgr/babel-plugin-transform-react-native-svg': 8.1.0(@babel/core@7.29.7)
-      '@svgr/babel-plugin-transform-svg-component': 8.0.0(@babel/core@7.29.7)
-
-  '@svgr/core@8.1.0(typescript@6.0.3)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@svgr/babel-preset': 8.1.0(@babel/core@7.29.7)
-      camelcase: 6.3.0
-      cosmiconfig: 8.3.6(typescript@6.0.3)
-      snake-case: 3.0.4
-    transitivePeerDependencies:
-      - supports-color
-      - typescript
-
-  '@svgr/hast-util-to-babel-ast@8.0.0':
-    dependencies:
-      '@babel/types': 7.29.7
-      entities: 4.5.0
-
-  '@svgr/plugin-jsx@8.1.0(@svgr/core@8.1.0(typescript@6.0.3))':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@svgr/babel-preset': 8.1.0(@babel/core@7.29.7)
-      '@svgr/core': 8.1.0(typescript@6.0.3)
-      '@svgr/hast-util-to-babel-ast': 8.0.0
-      svg-parser: 2.0.4
-    transitivePeerDependencies:
-      - supports-color
-
-  '@svgr/plugin-svgo@8.1.0(@svgr/core@8.1.0(typescript@6.0.3))(typescript@6.0.3)':
-    dependencies:
-      '@svgr/core': 8.1.0(typescript@6.0.3)
-      cosmiconfig: 8.3.6(typescript@6.0.3)
-      deepmerge: 4.3.1
-      svgo: 3.3.3
-    transitivePeerDependencies:
-      - typescript
-
-  '@svgr/webpack@8.1.0(typescript@6.0.3)':
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/plugin-transform-react-constant-elements': 7.29.7(@babel/core@7.29.7)
-      '@babel/preset-env': 7.29.7(@babel/core@7.29.7)
-      '@babel/preset-react': 7.29.7(@babel/core@7.29.7)
-      '@babel/preset-typescript': 7.29.7(@babel/core@7.29.7)
-      '@svgr/core': 8.1.0(typescript@6.0.3)
-      '@svgr/plugin-jsx': 8.1.0(@svgr/core@8.1.0(typescript@6.0.3))
-      '@svgr/plugin-svgo': 8.1.0(@svgr/core@8.1.0(typescript@6.0.3))(typescript@6.0.3)
-    transitivePeerDependencies:
-      - supports-color
-      - typescript
-
-  '@swc/core-darwin-arm64@1.15.41':
-    optional: true
-
-  '@swc/core-darwin-x64@1.15.41':
-    optional: true
-
-  '@swc/core-linux-arm-gnueabihf@1.15.41':
-    optional: true
-
-  '@swc/core-linux-arm64-gnu@1.15.41':
-    optional: true
-
-  '@swc/core-linux-arm64-musl@1.15.41':
-    optional: true
-
-  '@swc/core-linux-ppc64-gnu@1.15.41':
-    optional: true
-
-  '@swc/core-linux-s390x-gnu@1.15.41':
-    optional: true
-
-  '@swc/core-linux-x64-gnu@1.15.41':
-    optional: true
-
-  '@swc/core-linux-x64-musl@1.15.41':
-    optional: true
-
-  '@swc/core-win32-arm64-msvc@1.15.41':
-    optional: true
-
-  '@swc/core-win32-ia32-msvc@1.15.41':
-    optional: true
-
-  '@swc/core-win32-x64-msvc@1.15.41':
-    optional: true
-
-  '@swc/core@1.15.41(@swc/helpers@0.5.23)':
-    dependencies:
-      '@swc/counter': 0.1.3
-      '@swc/types': 0.1.26
-    optionalDependencies:
-      '@swc/core-darwin-arm64': 1.15.41
-      '@swc/core-darwin-x64': 1.15.41
-      '@swc/core-linux-arm-gnueabihf': 1.15.41
-      '@swc/core-linux-arm64-gnu': 1.15.41
-      '@swc/core-linux-arm64-musl': 1.15.41
-      '@swc/core-linux-ppc64-gnu': 1.15.41
-      '@swc/core-linux-s390x-gnu': 1.15.41
-      '@swc/core-linux-x64-gnu': 1.15.41
-      '@swc/core-linux-x64-musl': 1.15.41
-      '@swc/core-win32-arm64-msvc': 1.15.41
-      '@swc/core-win32-ia32-msvc': 1.15.41
-      '@swc/core-win32-x64-msvc': 1.15.41
-      '@swc/helpers': 0.5.23
-
-  '@swc/counter@0.1.3': {}
-
-  '@swc/helpers@0.5.23':
-    dependencies:
-      tslib: 2.8.1
-
-  '@swc/html-darwin-arm64@1.15.40':
-    optional: true
-
-  '@swc/html-darwin-x64@1.15.40':
-    optional: true
-
-  '@swc/html-linux-arm-gnueabihf@1.15.40':
-    optional: true
-
-  '@swc/html-linux-arm64-gnu@1.15.40':
-    optional: true
-
-  '@swc/html-linux-arm64-musl@1.15.40':
-    optional: true
-
-  '@swc/html-linux-ppc64-gnu@1.15.40':
-    optional: true
-
-  '@swc/html-linux-s390x-gnu@1.15.40':
-    optional: true
-
-  '@swc/html-linux-x64-gnu@1.15.40':
-    optional: true
-
-  '@swc/html-linux-x64-musl@1.15.40':
-    optional: true
-
-  '@swc/html-win32-arm64-msvc@1.15.40':
-    optional: true
-
-  '@swc/html-win32-ia32-msvc@1.15.40':
-    optional: true
-
-  '@swc/html-win32-x64-msvc@1.15.40':
-    optional: true
-
-  '@swc/html@1.15.40':
-    dependencies:
-      '@swc/counter': 0.1.3
-    optionalDependencies:
-      '@swc/html-darwin-arm64': 1.15.40
-      '@swc/html-darwin-x64': 1.15.40
-      '@swc/html-linux-arm-gnueabihf': 1.15.40
-      '@swc/html-linux-arm64-gnu': 1.15.40
-      '@swc/html-linux-arm64-musl': 1.15.40
-      '@swc/html-linux-ppc64-gnu': 1.15.40
-      '@swc/html-linux-s390x-gnu': 1.15.40
-      '@swc/html-linux-x64-gnu': 1.15.40
-      '@swc/html-linux-x64-musl': 1.15.40
-      '@swc/html-win32-arm64-msvc': 1.15.40
-      '@swc/html-win32-ia32-msvc': 1.15.40
-      '@swc/html-win32-x64-msvc': 1.15.40
-
-  '@swc/types@0.1.26':
-    dependencies:
-      '@swc/counter': 0.1.3
-
-  '@szmarczak/http-timer@5.0.1':
-    dependencies:
-      defer-to-connect: 2.0.1
-
-  '@tybys/wasm-util@0.10.2':
-    dependencies:
-      tslib: 2.8.1
-    optional: true
-
-  '@types/body-parser@1.19.6':
-    dependencies:
-      '@types/connect': 3.4.38
-      '@types/node': 25.9.2
-
-  '@types/bonjour@3.5.13':
-    dependencies:
-      '@types/node': 25.9.2
-
-  '@types/connect-history-api-fallback@1.5.4':
-    dependencies:
-      '@types/express-serve-static-core': 4.19.8
-      '@types/node': 25.9.2
-
-  '@types/connect@3.4.38':
-    dependencies:
-      '@types/node': 25.9.2
-
-  '@types/d3-array@3.2.2': {}
-
-  '@types/d3-axis@3.0.6':
-    dependencies:
-      '@types/d3-selection': 3.0.11
-
-  '@types/d3-brush@3.0.6':
-    dependencies:
-      '@types/d3-selection': 3.0.11
-
-  '@types/d3-chord@3.0.6': {}
-
-  '@types/d3-color@3.1.3': {}
-
-  '@types/d3-contour@3.0.6':
-    dependencies:
-      '@types/d3-array': 3.2.2
-      '@types/geojson': 7946.0.16
-
-  '@types/d3-delaunay@6.0.4': {}
-
-  '@types/d3-dispatch@3.0.7': {}
-
-  '@types/d3-drag@3.0.7':
-    dependencies:
-      '@types/d3-selection': 3.0.11
-
-  '@types/d3-dsv@3.0.7': {}
-
-  '@types/d3-ease@3.0.2': {}
-
-  '@types/d3-fetch@3.0.7':
-    dependencies:
-      '@types/d3-dsv': 3.0.7
-
-  '@types/d3-force@3.0.10': {}
-
-  '@types/d3-format@3.0.4': {}
-
-  '@types/d3-geo@3.1.0':
-    dependencies:
-      '@types/geojson': 7946.0.16
-
-  '@types/d3-hierarchy@3.1.7': {}
-
-  '@types/d3-interpolate@3.0.4':
-    dependencies:
-      '@types/d3-color': 3.1.3
-
-  '@types/d3-path@3.1.1': {}
-
-  '@types/d3-polygon@3.0.2': {}
-
-  '@types/d3-quadtree@3.0.6': {}
-
-  '@types/d3-random@3.0.3': {}
-
-  '@types/d3-scale-chromatic@3.1.0': {}
-
-  '@types/d3-scale@4.0.9':
-    dependencies:
-      '@types/d3-time': 3.0.4
-
-  '@types/d3-selection@3.0.11': {}
-
-  '@types/d3-shape@3.1.8':
-    dependencies:
-      '@types/d3-path': 3.1.1
-
-  '@types/d3-time-format@4.0.3': {}
-
-  '@types/d3-time@3.0.4': {}
-
-  '@types/d3-timer@3.0.2': {}
-
-  '@types/d3-transition@3.0.9':
-    dependencies:
-      '@types/d3-selection': 3.0.11
-
-  '@types/d3-zoom@3.0.8':
-    dependencies:
-      '@types/d3-interpolate': 3.0.4
-      '@types/d3-selection': 3.0.11
-
-  '@types/d3@7.4.3':
-    dependencies:
-      '@types/d3-array': 3.2.2
-      '@types/d3-axis': 3.0.6
-      '@types/d3-brush': 3.0.6
-      '@types/d3-chord': 3.0.6
-      '@types/d3-color': 3.1.3
-      '@types/d3-contour': 3.0.6
-      '@types/d3-delaunay': 6.0.4
-      '@types/d3-dispatch': 3.0.7
-      '@types/d3-drag': 3.0.7
-      '@types/d3-dsv': 3.0.7
-      '@types/d3-ease': 3.0.2
-      '@types/d3-fetch': 3.0.7
-      '@types/d3-force': 3.0.10
-      '@types/d3-format': 3.0.4
-      '@types/d3-geo': 3.1.0
-      '@types/d3-hierarchy': 3.1.7
-      '@types/d3-interpolate': 3.0.4
-      '@types/d3-path': 3.1.1
-      '@types/d3-polygon': 3.0.2
-      '@types/d3-quadtree': 3.0.6
-      '@types/d3-random': 3.0.3
-      '@types/d3-scale': 4.0.9
-      '@types/d3-scale-chromatic': 3.1.0
-      '@types/d3-selection': 3.0.11
-      '@types/d3-shape': 3.1.8
-      '@types/d3-time': 3.0.4
-      '@types/d3-time-format': 4.0.3
-      '@types/d3-timer': 3.0.2
-      '@types/d3-transition': 3.0.9
-      '@types/d3-zoom': 3.0.8
-
-  '@types/debug@4.1.13':
-    dependencies:
-      '@types/ms': 2.1.0
-
-  '@types/esrecurse@4.3.1': {}
-
-  '@types/estree-jsx@1.0.5':
-    dependencies:
-      '@types/estree': 1.0.9
-
-  '@types/estree@1.0.9': {}
-
-  '@types/express-serve-static-core@4.19.8':
-    dependencies:
-      '@types/node': 25.9.2
-      '@types/qs': 6.15.1
-      '@types/range-parser': 1.2.7
-      '@types/send': 1.2.1
-
-  '@types/express@4.17.25':
-    dependencies:
-      '@types/body-parser': 1.19.6
-      '@types/express-serve-static-core': 4.19.8
-      '@types/qs': 6.15.1
-      '@types/serve-static': 1.15.10
-
-  '@types/geojson@7946.0.16': {}
-
-  '@types/gtag.js@0.0.20': {}
-
-  '@types/hast@2.3.10':
-    dependencies:
-      '@types/unist': 2.0.11
-
-  '@types/hast@3.0.4':
-    dependencies:
-      '@types/unist': 3.0.3
-
-  '@types/history@4.7.11': {}
-
-  '@types/html-minifier-terser@6.1.0': {}
-
-  '@types/http-cache-semantics@4.2.0': {}
-
-  '@types/http-errors@2.0.5': {}
-
-  '@types/http-proxy@1.17.17':
-    dependencies:
-      '@types/node': 25.9.2
-
-  '@types/istanbul-lib-coverage@2.0.6': {}
-
-  '@types/istanbul-lib-report@3.0.3':
-    dependencies:
-      '@types/istanbul-lib-coverage': 2.0.6
-
-  '@types/istanbul-reports@3.0.4':
-    dependencies:
-      '@types/istanbul-lib-report': 3.0.3
-
-  '@types/js-cookie@2.2.7': {}
-
-  '@types/json-schema@7.0.15': {}
-
-  '@types/katex@0.16.8': {}
-
-  '@types/mdast@3.0.15':
-    dependencies:
-      '@types/unist': 2.0.11
-
-  '@types/mdast@4.0.4':
-    dependencies:
-      '@types/unist': 3.0.3
-
-  '@types/mdurl@1.0.5': {}
-
-  '@types/mdx@2.0.14': {}
-
-  '@types/mime@1.3.5': {}
-
-  '@types/ms@2.1.0': {}
-
-  '@types/node@17.0.45': {}
-
-  '@types/node@25.9.2':
-    dependencies:
-      undici-types: 7.24.6
-
-  '@types/parse5@6.0.3': {}
-
-  '@types/prismjs@1.26.6': {}
-
-  '@types/prop-types@15.7.15': {}
-
-  '@types/qs@6.15.1': {}
-
-  '@types/range-parser@1.2.7': {}
-
-  '@types/react-dom@17.0.26(@types/react@17.0.93)':
-    dependencies:
-      '@types/react': 17.0.93
-
-  '@types/react-router-config@5.0.11':
-    dependencies:
-      '@types/history': 4.7.11
-      '@types/react': 19.2.17
-      '@types/react-router': 5.1.20
-
-  '@types/react-router-dom@5.3.3':
-    dependencies:
-      '@types/history': 4.7.11
-      '@types/react': 19.2.17
-      '@types/react-router': 5.1.20
-
-  '@types/react-router@5.1.20':
-    dependencies:
-      '@types/history': 4.7.11
-      '@types/react': 19.2.17
-
-  '@types/react@17.0.93':
-    dependencies:
-      '@types/prop-types': 15.7.15
-      '@types/scheduler': 0.16.8
-      csstype: 3.2.3
-
-  '@types/react@19.2.17':
-    dependencies:
-      csstype: 3.2.3
-
-  '@types/retry@0.12.2': {}
-
-  '@types/sax@1.2.7':
-    dependencies:
-      '@types/node': 25.9.2
-
-  '@types/scheduler@0.16.8': {}
-
-  '@types/semver@7.7.1': {}
-
-  '@types/send@0.17.6':
-    dependencies:
-      '@types/mime': 1.3.5
-      '@types/node': 25.9.2
-
-  '@types/send@1.2.1':
-    dependencies:
-      '@types/node': 25.9.2
-
-  '@types/serve-index@1.9.4':
-    dependencies:
-      '@types/express': 4.17.25
-
-  '@types/serve-static@1.15.10':
-    dependencies:
-      '@types/http-errors': 2.0.5
-      '@types/node': 25.9.2
-      '@types/send': 0.17.6
-
-  '@types/sockjs@0.3.36':
-    dependencies:
-      '@types/node': 25.9.2
-
-  '@types/trusted-types@2.0.7':
-    optional: true
-
-  '@types/unist@2.0.11': {}
-
-  '@types/unist@3.0.3': {}
-
-  '@types/use-sync-external-store@0.0.6': {}
-
-  '@types/ws@8.18.1':
-    dependencies:
-      '@types/node': 25.9.2
-
-  '@types/yargs-parser@21.0.3': {}
-
-  '@types/yargs@17.0.35':
-    dependencies:
-      '@types/yargs-parser': 21.0.3
-
-  '@typescript-eslint/eslint-plugin@7.18.0(@typescript-eslint/parser@7.18.0(eslint@10.6.0(jiti@1.21.7))(typescript@6.0.3))(eslint@10.6.0(jiti@1.21.7))(typescript@6.0.3)':
-    dependencies:
-      '@eslint-community/regexpp': 4.12.2
-      '@typescript-eslint/parser': 7.18.0(eslint@10.6.0(jiti@1.21.7))(typescript@6.0.3)
-      '@typescript-eslint/scope-manager': 7.18.0
-      '@typescript-eslint/type-utils': 7.18.0(eslint@10.6.0(jiti@1.21.7))(typescript@6.0.3)
-      '@typescript-eslint/utils': 7.18.0(eslint@10.6.0(jiti@1.21.7))(typescript@6.0.3)
-      '@typescript-eslint/visitor-keys': 7.18.0
-      eslint: 10.6.0(jiti@1.21.7)
-      graphemer: 1.4.0
-      ignore: 5.3.2
-      natural-compare: 1.4.0
-      ts-api-utils: 1.4.3(typescript@6.0.3)
-    optionalDependencies:
-      typescript: 6.0.3
-    transitivePeerDependencies:
-      - supports-color
-
-  '@typescript-eslint/parser@7.18.0(eslint@10.6.0(jiti@1.21.7))(typescript@6.0.3)':
-    dependencies:
-      '@typescript-eslint/scope-manager': 7.18.0
-      '@typescript-eslint/types': 7.18.0
-      '@typescript-eslint/typescript-estree': 7.18.0(typescript@6.0.3)
-      '@typescript-eslint/visitor-keys': 7.18.0
-      debug: 4.4.3
-      eslint: 10.6.0(jiti@1.21.7)
-    optionalDependencies:
-      typescript: 6.0.3
-    transitivePeerDependencies:
-      - supports-color
-
-  '@typescript-eslint/scope-manager@5.62.0':
-    dependencies:
-      '@typescript-eslint/types': 5.62.0
-      '@typescript-eslint/visitor-keys': 5.62.0
-
-  '@typescript-eslint/scope-manager@7.18.0':
-    dependencies:
-      '@typescript-eslint/types': 7.18.0
-      '@typescript-eslint/visitor-keys': 7.18.0
-
-  '@typescript-eslint/type-utils@7.18.0(eslint@10.6.0(jiti@1.21.7))(typescript@6.0.3)':
-    dependencies:
-      '@typescript-eslint/typescript-estree': 7.18.0(typescript@6.0.3)
-      '@typescript-eslint/utils': 7.18.0(eslint@10.6.0(jiti@1.21.7))(typescript@6.0.3)
-      debug: 4.4.3
-      eslint: 10.6.0(jiti@1.21.7)
-      ts-api-utils: 1.4.3(typescript@6.0.3)
-    optionalDependencies:
-      typescript: 6.0.3
-    transitivePeerDependencies:
-      - supports-color
-
-  '@typescript-eslint/types@5.62.0': {}
-
-  '@typescript-eslint/types@7.18.0': {}
-
-  '@typescript-eslint/typescript-estree@5.62.0(typescript@6.0.3)':
-    dependencies:
-      '@typescript-eslint/types': 5.62.0
-      '@typescript-eslint/visitor-keys': 5.62.0
-      debug: 4.4.3
-      globby: 11.1.0
-      is-glob: 4.0.3
-      semver: 7.8.3
-      tsutils: 3.21.0(typescript@6.0.3)
-    optionalDependencies:
-      typescript: 6.0.3
-    transitivePeerDependencies:
-      - supports-color
-
-  '@typescript-eslint/typescript-estree@7.18.0(typescript@6.0.3)':
-    dependencies:
-      '@typescript-eslint/types': 7.18.0
-      '@typescript-eslint/visitor-keys': 7.18.0
-      debug: 4.4.3
-      globby: 11.1.0
-      is-glob: 4.0.3
-      minimatch: 9.0.9
-      semver: 7.8.5
-      ts-api-utils: 1.4.3(typescript@6.0.3)
-    optionalDependencies:
-      typescript: 6.0.3
-    transitivePeerDependencies:
-      - supports-color
-
-  '@typescript-eslint/utils@5.62.0(eslint@10.6.0(jiti@1.21.7))(typescript@6.0.3)':
-    dependencies:
-      '@eslint-community/eslint-utils': 4.9.1(eslint@10.6.0(jiti@1.21.7))
-      '@types/json-schema': 7.0.15
-      '@types/semver': 7.7.1
-      '@typescript-eslint/scope-manager': 5.62.0
-      '@typescript-eslint/types': 5.62.0
-      '@typescript-eslint/typescript-estree': 5.62.0(typescript@6.0.3)
-      eslint: 10.6.0(jiti@1.21.7)
-      eslint-scope: 5.1.1
-      semver: 7.8.3
-    transitivePeerDependencies:
-      - supports-color
-      - typescript
-
-  '@typescript-eslint/utils@7.18.0(eslint@10.6.0(jiti@1.21.7))(typescript@6.0.3)':
-    dependencies:
-      '@eslint-community/eslint-utils': 4.10.1(eslint@10.6.0(jiti@1.21.7))
-      '@typescript-eslint/scope-manager': 7.18.0
-      '@typescript-eslint/types': 7.18.0
-      '@typescript-eslint/typescript-estree': 7.18.0(typescript@6.0.3)
-      eslint: 10.6.0(jiti@1.21.7)
-    transitivePeerDependencies:
-      - supports-color
-      - typescript
-
-  '@typescript-eslint/visitor-keys@5.62.0':
-    dependencies:
-      '@typescript-eslint/types': 5.62.0
-      eslint-visitor-keys: 3.4.3
-
-  '@typescript-eslint/visitor-keys@7.18.0':
-    dependencies:
-      '@typescript-eslint/types': 7.18.0
-      eslint-visitor-keys: 3.4.3
-
-  '@ungap/structured-clone@1.3.2': {}
-
-  '@upsetjs/venn.js@2.0.0':
-    optionalDependencies:
-      d3-selection: 3.0.0
-      d3-transition: 3.0.1(d3-selection@3.0.0)
-
-  '@webassemblyjs/ast@1.14.1':
-    dependencies:
-      '@webassemblyjs/helper-numbers': 1.13.2
-      '@webassemblyjs/helper-wasm-bytecode': 1.13.2
-
-  '@webassemblyjs/floating-point-hex-parser@1.13.2': {}
-
-  '@webassemblyjs/helper-api-error@1.13.2': {}
-
-  '@webassemblyjs/helper-buffer@1.14.1': {}
-
-  '@webassemblyjs/helper-numbers@1.13.2':
-    dependencies:
-      '@webassemblyjs/floating-point-hex-parser': 1.13.2
-      '@webassemblyjs/helper-api-error': 1.13.2
-      '@xtuc/long': 4.2.2
-
-  '@webassemblyjs/helper-wasm-bytecode@1.13.2': {}
-
-  '@webassemblyjs/helper-wasm-section@1.14.1':
-    dependencies:
-      '@webassemblyjs/ast': 1.14.1
-      '@webassemblyjs/helper-buffer': 1.14.1
-      '@webassemblyjs/helper-wasm-bytecode': 1.13.2
-      '@webassemblyjs/wasm-gen': 1.14.1
-
-  '@webassemblyjs/ieee754@1.13.2':
-    dependencies:
-      '@xtuc/ieee754': 1.2.0
-
-  '@webassemblyjs/leb128@1.13.2':
-    dependencies:
-      '@xtuc/long': 4.2.2
-
-  '@webassemblyjs/utf8@1.13.2': {}
-
-  '@webassemblyjs/wasm-edit@1.14.1':
-    dependencies:
-      '@webassemblyjs/ast': 1.14.1
-      '@webassemblyjs/helper-buffer': 1.14.1
-      '@webassemblyjs/helper-wasm-bytecode': 1.13.2
-      '@webassemblyjs/helper-wasm-section': 1.14.1
-      '@webassemblyjs/wasm-gen': 1.14.1
-      '@webassemblyjs/wasm-opt': 1.14.1
-      '@webassemblyjs/wasm-parser': 1.14.1
-      '@webassemblyjs/wast-printer': 1.14.1
-
-  '@webassemblyjs/wasm-gen@1.14.1':
-    dependencies:
-      '@webassemblyjs/ast': 1.14.1
-      '@webassemblyjs/helper-wasm-bytecode': 1.13.2
-      '@webassemblyjs/ieee754': 1.13.2
-      '@webassemblyjs/leb128': 1.13.2
-      '@webassemblyjs/utf8': 1.13.2
-
-  '@webassemblyjs/wasm-opt@1.14.1':
-    dependencies:
-      '@webassemblyjs/ast': 1.14.1
-      '@webassemblyjs/helper-buffer': 1.14.1
-      '@webassemblyjs/wasm-gen': 1.14.1
-      '@webassemblyjs/wasm-parser': 1.14.1
-
-  '@webassemblyjs/wasm-parser@1.14.1':
-    dependencies:
-      '@webassemblyjs/ast': 1.14.1
-      '@webassemblyjs/helper-api-error': 1.13.2
-      '@webassemblyjs/helper-wasm-bytecode': 1.13.2
-      '@webassemblyjs/ieee754': 1.13.2
-      '@webassemblyjs/leb128': 1.13.2
-      '@webassemblyjs/utf8': 1.13.2
-
-  '@webassemblyjs/wast-printer@1.14.1':
-    dependencies:
-      '@webassemblyjs/ast': 1.14.1
-      '@xtuc/long': 4.2.2
-
-  '@xobotyi/scrollbar-width@1.9.5': {}
-
-  '@xtuc/ieee754@1.2.0': {}
-
-  '@xtuc/long@4.2.2': {}
-
-  accepts@1.3.8:
-    dependencies:
-      mime-types: 2.1.35
-      negotiator: 0.6.3
-
-  acorn-import-phases@1.0.4(acorn@8.16.0):
-    dependencies:
-      acorn: 8.16.0
-
-  acorn-jsx@5.3.2(acorn@8.16.0):
-    dependencies:
-      acorn: 8.16.0
-
-  acorn-jsx@5.3.2(acorn@8.17.0):
-    dependencies:
-      acorn: 8.17.0
-
-  acorn-walk@8.3.5:
-    dependencies:
-      acorn: 8.16.0
-
-  acorn@8.16.0: {}
-
-  acorn@8.17.0: {}
-
-  address@1.2.2: {}
-
-  aggregate-error@3.1.0:
-    dependencies:
-      clean-stack: 2.2.0
-      indent-string: 4.0.0
-
-  ajv-draft-04@1.0.0(ajv@8.20.0):
-    optionalDependencies:
-      ajv: 8.20.0
-
-  ajv-formats@2.1.1(ajv@8.20.0):
-    optionalDependencies:
-      ajv: 8.20.0
-
-  ajv-formats@3.0.1(@redocly/ajv@8.18.1):
-    optionalDependencies:
-      ajv: '@redocly/ajv@8.18.1'
-
-  ajv-keywords@3.5.2(ajv@6.15.0):
-    dependencies:
-      ajv: 6.15.0
-
-  ajv-keywords@5.1.0(ajv@8.20.0):
-    dependencies:
-      ajv: 8.20.0
-      fast-deep-equal: 3.1.3
-
-  ajv@6.15.0:
-    dependencies:
-      fast-deep-equal: 3.1.3
-      fast-json-stable-stringify: 2.1.0
-      json-schema-traverse: 0.4.1
-      uri-js: 4.4.1
-
-  ajv@8.20.0:
-    dependencies:
-      fast-deep-equal: 3.1.3
-      fast-uri: 3.1.2
-      json-schema-traverse: 1.0.0
-      require-from-string: 2.0.2
-
-  algoliasearch-helper@3.29.1(algoliasearch@5.53.0):
-    dependencies:
-      '@algolia/events': 4.0.1
-      algoliasearch: 5.53.0
-
-  algoliasearch@5.53.0:
-    dependencies:
-      '@algolia/abtesting': 1.19.0
-      '@algolia/client-abtesting': 5.53.0
-      '@algolia/client-analytics': 5.53.0
-      '@algolia/client-common': 5.53.0
-      '@algolia/client-insights': 5.53.0
-      '@algolia/client-personalization': 5.53.0
-      '@algolia/client-query-suggestions': 5.53.0
-      '@algolia/client-search': 5.53.0
-      '@algolia/ingestion': 1.53.0
-      '@algolia/monitoring': 1.53.0
-      '@algolia/recommend': 5.53.0
-      '@algolia/requester-browser-xhr': 5.53.0
-      '@algolia/requester-fetch': 5.53.0
-      '@algolia/requester-node-http': 5.53.0
-
-  allof-merge@0.6.8:
-    dependencies:
-      json-crawl: 0.5.3
-
-  ansi-align@3.0.1:
-    dependencies:
-      string-width: 4.2.3
-
-  ansi-html-community@0.0.8: {}
-
-  ansi-regex@5.0.1: {}
-
-  ansi-regex@6.2.2: {}
-
-  ansi-styles@4.3.0:
-    dependencies:
-      color-convert: 2.0.1
-
-  ansi-styles@6.2.3: {}
-
-  ansis@3.17.0: {}
-
-  any-promise@1.3.0: {}
-
-  anymatch@3.1.3:
-    dependencies:
-      normalize-path: 3.0.0
-      picomatch: 2.3.2
-
-  arg@5.0.2: {}
-
-  argparse@1.0.10:
-    dependencies:
-      sprintf-js: 1.0.3
-
-  argparse@2.0.1: {}
-
-  aria-hidden@1.2.6:
-    dependencies:
-      tslib: 2.8.1
-
-  array-flatten@1.1.1: {}
-
-  array-union@2.1.0: {}
-
-  asn1js@3.0.10:
-    dependencies:
-      pvtsutils: 1.3.6
-      pvutils: 1.1.5
-      tslib: 2.8.1
-
-  astring@1.9.0: {}
-
-  async@3.2.6: {}
-
-  autoprefixer@10.5.0(postcss@8.5.15):
-    dependencies:
-      browserslist: 4.28.2
-      caniuse-lite: 1.0.30001797
-      fraction.js: 5.3.4
-      picocolors: 1.1.1
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
-
-  babel-loader@9.2.1(@babel/core@7.29.7)(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)):
-    dependencies:
-      '@babel/core': 7.29.7
-      find-cache-dir: 4.0.0
-      schema-utils: 4.3.3
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
-
-  babel-plugin-dynamic-import-node@2.3.3:
-    dependencies:
-      object.assign: 4.1.7
-
-  babel-plugin-polyfill-corejs2@0.4.17(@babel/core@7.29.7):
-    dependencies:
-      '@babel/compat-data': 7.29.7
-      '@babel/core': 7.29.7
-      '@babel/helper-define-polyfill-provider': 0.6.8(@babel/core@7.29.7)
-      semver: 6.3.1
-    transitivePeerDependencies:
-      - supports-color
-
-  babel-plugin-polyfill-corejs3@0.13.0(@babel/core@7.29.7):
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-define-polyfill-provider': 0.6.8(@babel/core@7.29.7)
-      core-js-compat: 3.49.0
-    transitivePeerDependencies:
-      - supports-color
-
-  babel-plugin-polyfill-corejs3@0.14.2(@babel/core@7.29.7):
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-define-polyfill-provider': 0.6.8(@babel/core@7.29.7)
-      core-js-compat: 3.49.0
-    transitivePeerDependencies:
-      - supports-color
-
-  babel-plugin-polyfill-regenerator@0.6.8(@babel/core@7.29.7):
-    dependencies:
-      '@babel/core': 7.29.7
-      '@babel/helper-define-polyfill-provider': 0.6.8(@babel/core@7.29.7)
-    transitivePeerDependencies:
-      - supports-color
-
-  bail@1.0.5: {}
-
-  bail@2.0.2: {}
-
-  balanced-match@1.0.2: {}
-
-  balanced-match@4.0.4: {}
-
-  base64-js@1.5.1: {}
-
-  baseline-browser-mapping@2.10.35: {}
-
-  batch@0.6.1: {}
-
-  big.js@5.2.2: {}
-
-  binary-extensions@2.3.0: {}
-
-  body-parser@1.20.5:
-    dependencies:
-      bytes: 3.1.2
-      content-type: 1.0.5
-      debug: 2.6.9
-      depd: 2.0.0
-      destroy: 1.2.0
-      http-errors: 2.0.1
-      iconv-lite: 0.4.24
-      on-finished: 2.4.1
-      qs: 6.15.3
-      raw-body: 2.5.3
-      type-is: 1.6.18
-      unpipe: 1.0.0
-    transitivePeerDependencies:
-      - supports-color
-
-  bonjour-service@1.4.0:
-    dependencies:
-      fast-deep-equal: 3.1.3
-      multicast-dns: 7.2.5
-
-  boolbase@1.0.0: {}
-
-  boxen@6.2.1:
-    dependencies:
-      ansi-align: 3.0.1
-      camelcase: 6.3.0
-      chalk: 4.1.2
-      cli-boxes: 3.0.0
-      string-width: 5.1.2
-      type-fest: 2.19.0
-      widest-line: 4.0.1
-      wrap-ansi: 8.1.0
-
-  boxen@7.1.1:
-    dependencies:
-      ansi-align: 3.0.1
-      camelcase: 7.0.1
-      chalk: 5.6.2
-      cli-boxes: 3.0.0
-      string-width: 5.1.2
-      type-fest: 2.19.0
-      widest-line: 4.0.1
-      wrap-ansi: 8.1.0
-
-  brace-expansion@1.1.15:
-    dependencies:
-      balanced-match: 1.0.2
-      concat-map: 0.0.1
-
-  brace-expansion@2.1.1:
-    dependencies:
-      balanced-match: 1.0.2
-
-  brace-expansion@5.0.7:
-    dependencies:
-      balanced-match: 4.0.4
-
-  braces@3.0.3:
-    dependencies:
-      fill-range: 7.1.1
-
-  browserslist@4.28.2:
-    dependencies:
-      baseline-browser-mapping: 2.10.35
-      caniuse-lite: 1.0.30001797
-      electron-to-chromium: 1.5.370
-      node-releases: 2.0.47
-      update-browserslist-db: 1.2.3(browserslist@4.28.2)
-
-  buffer-from@1.1.2: {}
-
-  buffer@6.0.3:
-    dependencies:
-      base64-js: 1.5.1
-      ieee754: 1.2.1
-
-  bundle-name@4.1.0:
-    dependencies:
-      run-applescript: 7.1.0
-
-  bytes@3.0.0: {}
-
-  bytes@3.1.2: {}
-
-  bytestreamjs@2.0.1: {}
-
-  cacheable-lookup@7.0.0: {}
-
-  cacheable-request@10.2.14:
-    dependencies:
-      '@types/http-cache-semantics': 4.2.0
-      get-stream: 6.0.1
-      http-cache-semantics: 4.2.0
-      keyv: 4.5.4
-      mimic-response: 4.0.0
-      normalize-url: 8.1.1
-      responselike: 3.0.0
-
-  call-bind-apply-helpers@1.0.2:
-    dependencies:
-      es-errors: 1.3.0
-      function-bind: 1.1.2
-
-  call-bind@1.0.9:
-    dependencies:
-      call-bind-apply-helpers: 1.0.2
-      es-define-property: 1.0.1
-      get-intrinsic: 1.3.0
-      set-function-length: 1.2.2
-
-  call-bound@1.0.4:
-    dependencies:
-      call-bind-apply-helpers: 1.0.2
-      get-intrinsic: 1.3.0
-
-  call-me-maybe@1.0.2: {}
-
-  callsites@3.1.0: {}
-
-  camel-case@4.1.2:
-    dependencies:
-      pascal-case: 3.1.2
-      tslib: 2.8.1
-
-  camelcase@6.3.0: {}
-
-  camelcase@7.0.1: {}
-
-  caniuse-api@3.0.0:
-    dependencies:
-      browserslist: 4.28.2
-      caniuse-lite: 1.0.30001797
-      lodash.memoize: 4.1.2
-      lodash.uniq: 4.5.0
-
-  caniuse-lite@1.0.30001797: {}
-
-  ccount@1.1.0: {}
-
-  ccount@2.0.1: {}
-
-  chalk@4.1.2:
-    dependencies:
-      ansi-styles: 4.3.0
-      supports-color: 7.2.0
-
-  chalk@5.6.2: {}
-
-  char-regex@1.0.2: {}
-
-  character-entities-html4@2.1.0: {}
-
-  character-entities-legacy@1.1.4: {}
-
-  character-entities-legacy@3.0.0: {}
-
-  character-entities@1.2.4: {}
-
-  character-entities@2.0.2: {}
-
-  character-reference-invalid@1.1.4: {}
-
-  character-reference-invalid@2.0.1: {}
-
-  charset@1.0.1: {}
-
-  cheerio-select@2.1.0:
-    dependencies:
-      boolbase: 1.0.0
-      css-select: 5.2.2
-      css-what: 6.2.2
-      domelementtype: 2.3.0
-      domhandler: 5.0.3
-      domutils: 3.2.2
-
-  cheerio@1.0.0-rc.12:
-    dependencies:
-      cheerio-select: 2.1.0
-      dom-serializer: 2.0.0
-      domhandler: 5.0.3
-      domutils: 3.2.2
-      htmlparser2: 8.0.2
-      parse5: 7.3.0
-      parse5-htmlparser2-tree-adapter: 7.1.0
-
-  chokidar@3.6.0:
-    dependencies:
-      anymatch: 3.1.3
-      braces: 3.0.3
-      glob-parent: 5.1.2
-      is-binary-path: 2.1.0
-      is-glob: 4.0.3
-      normalize-path: 3.0.0
-      readdirp: 3.6.0
-    optionalDependencies:
-      fsevents: 2.3.3
-
-  chokidar@5.0.0:
-    dependencies:
-      readdirp: 5.0.0
-
-  chrome-trace-event@1.0.4: {}
-
-  ci-info@3.9.0: {}
-
-  classnames@2.5.1: {}
-
-  clean-css@5.3.3:
-    dependencies:
-      source-map: 0.6.1
-
-  clean-stack@2.2.0: {}
-
-  cli-boxes@3.0.0: {}
-
-  cli-table3@0.6.5:
-    dependencies:
-      string-width: 4.2.3
-    optionalDependencies:
-      '@colors/colors': 1.5.0
-
-  client-only@0.0.1: {}
-
-  cliui@8.0.1:
-    dependencies:
-      string-width: 4.2.3
-      strip-ansi: 6.0.1
-      wrap-ansi: 7.0.0
-
-  cliui@9.0.1:
-    dependencies:
-      string-width: 7.2.0
-      strip-ansi: 7.2.0
-      wrap-ansi: 9.0.2
-
-  clone-deep@4.0.1:
-    dependencies:
-      is-plain-object: 2.0.4
-      kind-of: 6.0.3
-      shallow-clone: 3.0.1
-
-  clsx@1.2.1: {}
-
-  clsx@2.1.1: {}
-
-  collapse-white-space@2.1.0: {}
-
-  color-convert@2.0.1:
-    dependencies:
-      color-name: 1.1.4
-
-  color-name@1.1.4: {}
-
-  colord@2.9.3: {}
-
-  colorette@1.4.0: {}
-
-  colorette@2.0.20: {}
-
-  combine-promises@1.2.0: {}
-
-  comma-separated-tokens@1.0.8: {}
-
-  comma-separated-tokens@2.0.3: {}
-
-  commander@10.0.1: {}
-
-  commander@2.20.3: {}
-
-  commander@4.1.1: {}
-
-  commander@5.1.0: {}
-
-  commander@7.2.0: {}
-
-  commander@8.3.0: {}
-
-  common-path-prefix@3.0.0: {}
-
-  compressible@2.0.18:
-    dependencies:
-      mime-db: 1.54.0
-
-  compression@1.8.1:
-    dependencies:
-      bytes: 3.1.2
-      compressible: 2.0.18
-      debug: 2.6.9
-      negotiator: 0.6.4
-      on-headers: 1.1.0
-      safe-buffer: 5.2.1
-      vary: 1.1.2
-    transitivePeerDependencies:
-      - supports-color
-
-  compute-gcd@1.2.1:
-    dependencies:
-      validate.io-array: 1.0.6
-      validate.io-function: 1.0.2
-      validate.io-integer-array: 1.0.0
-
-  compute-lcm@1.1.2:
-    dependencies:
-      compute-gcd: 1.2.1
-      validate.io-array: 1.0.6
-      validate.io-function: 1.0.2
-      validate.io-integer-array: 1.0.0
-
-  concat-map@0.0.1: {}
-
-  config-chain@1.1.13:
-    dependencies:
-      ini: 1.3.8
-      proto-list: 1.2.4
-
-  configstore@6.0.0:
-    dependencies:
-      dot-prop: 6.0.1
-      graceful-fs: 4.2.11
-      unique-string: 3.0.0
-      write-file-atomic: 3.0.3
-      xdg-basedir: 5.1.0
-
-  connect-history-api-fallback@2.0.0: {}
-
-  consola@3.4.2: {}
-
-  content-disposition@0.5.2: {}
-
-  content-disposition@0.5.4:
-    dependencies:
-      safe-buffer: 5.2.1
-
-  content-type@1.0.5: {}
-
-  convert-source-map@2.0.0: {}
-
-  cookie-signature@1.0.7: {}
-
-  cookie@0.7.2: {}
-
-  copy-text-to-clipboard@3.2.2: {}
-
-  copy-to-clipboard@3.3.3:
-    dependencies:
-      toggle-selection: 1.0.6
-
-  copy-webpack-plugin@11.0.0(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)):
-    dependencies:
-      fast-glob: 3.3.3
-      glob-parent: 6.0.2
-      globby: 13.2.2
-      normalize-path: 3.0.0
-      schema-utils: 4.3.3
-      serialize-javascript: 6.0.2
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
-
-  core-js-compat@3.49.0:
-    dependencies:
-      browserslist: 4.28.2
-
-  core-js@3.49.0: {}
-
-  core-util-is@1.0.3: {}
-
-  cose-base@1.0.3:
-    dependencies:
-      layout-base: 1.0.2
-
-  cose-base@2.2.0:
-    dependencies:
-      layout-base: 2.0.1
-
-  cosmiconfig@8.3.6(typescript@6.0.3):
-    dependencies:
-      import-fresh: 3.3.1
-      js-yaml: 4.3.1
-      parse-json: 5.2.0
-      path-type: 4.0.0
-    optionalDependencies:
-      typescript: 6.0.3
-
-  cross-spawn@7.0.6:
-    dependencies:
-      path-key: 3.1.1
-      shebang-command: 2.0.0
-      which: 2.0.2
-
-  crypto-js@4.2.0: {}
-
-  crypto-random-string@4.0.0:
-    dependencies:
-      type-fest: 1.4.0
-
-  css-blank-pseudo@7.0.1(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
-      postcss-selector-parser: 7.1.2
-
-  css-declaration-sorter@7.4.0(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
-
-  css-has-pseudo@7.0.3(postcss@8.5.15):
-    dependencies:
-      '@csstools/selector-specificity': 5.0.0(postcss-selector-parser@7.1.2)
-      postcss: 8.5.15
-      postcss-selector-parser: 7.1.2
-      postcss-value-parser: 4.2.0
-
-  css-in-js-utils@3.1.0:
-    dependencies:
-      hyphenate-style-name: 1.1.0
-
-  css-loader@6.11.0(@rspack/core@1.7.11(@swc/helpers@0.5.23))(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)):
-    dependencies:
-      icss-utils: 5.1.0(postcss@8.5.15)
-      postcss: 8.5.15
-      postcss-modules-extract-imports: 3.1.0(postcss@8.5.15)
-      postcss-modules-local-by-default: 4.2.0(postcss@8.5.15)
-      postcss-modules-scope: 3.2.1(postcss@8.5.15)
-      postcss-modules-values: 4.0.0(postcss@8.5.15)
-      postcss-value-parser: 4.2.0
-      semver: 7.8.3
-    optionalDependencies:
-      '@rspack/core': 1.7.11(@swc/helpers@0.5.23)
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
-
-  css-minimizer-webpack-plugin@5.0.1(clean-css@5.3.3)(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)):
-    dependencies:
-      '@jridgewell/trace-mapping': 0.3.31
-      cssnano: 6.1.2(postcss@8.5.15)
-      jest-worker: 29.7.0
-      postcss: 8.5.15
-      schema-utils: 4.3.3
-      serialize-javascript: 6.0.2
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
-    optionalDependencies:
-      clean-css: 5.3.3
-
-  css-prefers-color-scheme@10.0.0(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
-
-  css-select@4.3.0:
-    dependencies:
-      boolbase: 1.0.0
-      css-what: 6.2.2
-      domhandler: 4.3.1
-      domutils: 2.8.0
-      nth-check: 2.1.1
-
-  css-select@5.2.2:
-    dependencies:
-      boolbase: 1.0.0
-      css-what: 6.2.2
-      domhandler: 5.0.3
-      domutils: 3.2.2
-      nth-check: 2.1.1
-
-  css-selector-parser@1.4.1: {}
-
-  css-tree@1.1.3:
-    dependencies:
-      mdn-data: 2.0.14
-      source-map: 0.6.1
-
-  css-tree@2.2.1:
-    dependencies:
-      mdn-data: 2.0.28
-      source-map-js: 1.2.1
-
-  css-tree@2.3.1:
-    dependencies:
-      mdn-data: 2.0.30
-      source-map-js: 1.2.1
-
-  css-what@6.2.2: {}
-
-  cssdb@8.9.0: {}
-
-  cssesc@3.0.0: {}
-
-  cssnano-preset-advanced@6.1.2(postcss@8.5.15):
-    dependencies:
-      autoprefixer: 10.5.0(postcss@8.5.15)
-      browserslist: 4.28.2
-      cssnano-preset-default: 6.1.2(postcss@8.5.15)
-      postcss: 8.5.15
-      postcss-discard-unused: 6.0.5(postcss@8.5.15)
-      postcss-merge-idents: 6.0.3(postcss@8.5.15)
-      postcss-reduce-idents: 6.0.3(postcss@8.5.15)
-      postcss-zindex: 6.0.2(postcss@8.5.15)
-
-  cssnano-preset-default@6.1.2(postcss@8.5.15):
-    dependencies:
-      browserslist: 4.28.2
-      css-declaration-sorter: 7.4.0(postcss@8.5.15)
-      cssnano-utils: 4.0.2(postcss@8.5.15)
-      postcss: 8.5.15
-      postcss-calc: 9.0.1(postcss@8.5.15)
-      postcss-colormin: 6.1.0(postcss@8.5.15)
-      postcss-convert-values: 6.1.0(postcss@8.5.15)
-      postcss-discard-comments: 6.0.2(postcss@8.5.15)
-      postcss-discard-duplicates: 6.0.3(postcss@8.5.15)
-      postcss-discard-empty: 6.0.3(postcss@8.5.15)
-      postcss-discard-overridden: 6.0.2(postcss@8.5.15)
-      postcss-merge-longhand: 6.0.5(postcss@8.5.15)
-      postcss-merge-rules: 6.1.1(postcss@8.5.15)
-      postcss-minify-font-values: 6.1.0(postcss@8.5.15)
-      postcss-minify-gradients: 6.0.3(postcss@8.5.15)
-      postcss-minify-params: 6.1.0(postcss@8.5.15)
-      postcss-minify-selectors: 6.0.4(postcss@8.5.15)
-      postcss-normalize-charset: 6.0.2(postcss@8.5.15)
-      postcss-normalize-display-values: 6.0.2(postcss@8.5.15)
-      postcss-normalize-positions: 6.0.2(postcss@8.5.15)
-      postcss-normalize-repeat-style: 6.0.2(postcss@8.5.15)
-      postcss-normalize-string: 6.0.2(postcss@8.5.15)
-      postcss-normalize-timing-functions: 6.0.2(postcss@8.5.15)
-      postcss-normalize-unicode: 6.1.0(postcss@8.5.15)
-      postcss-normalize-url: 6.0.2(postcss@8.5.15)
-      postcss-normalize-whitespace: 6.0.2(postcss@8.5.15)
-      postcss-ordered-values: 6.0.2(postcss@8.5.15)
-      postcss-reduce-initial: 6.1.0(postcss@8.5.15)
-      postcss-reduce-transforms: 6.0.2(postcss@8.5.15)
-      postcss-svgo: 6.0.3(postcss@8.5.15)
-      postcss-unique-selectors: 6.0.4(postcss@8.5.15)
-
-  cssnano-utils@4.0.2(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
-
-  cssnano@6.1.2(postcss@8.5.15):
-    dependencies:
-      cssnano-preset-default: 6.1.2(postcss@8.5.15)
-      lilconfig: 3.1.3
-      postcss: 8.5.15
-
-  csso@5.0.5:
-    dependencies:
-      css-tree: 2.2.1
-
-  csstype@3.2.3: {}
-
-  cytoscape-cose-bilkent@4.1.0(cytoscape@3.34.0):
-    dependencies:
-      cose-base: 1.0.3
-      cytoscape: 3.34.0
-
-  cytoscape-fcose@2.2.0(cytoscape@3.34.0):
-    dependencies:
-      cose-base: 2.2.0
-      cytoscape: 3.34.0
-
-  cytoscape@3.34.0: {}
-
-  d3-array@2.12.1:
-    dependencies:
-      internmap: 1.0.1
-
-  d3-array@3.2.4:
-    dependencies:
-      internmap: 2.0.3
-
-  d3-axis@3.0.0: {}
-
-  d3-brush@3.0.0:
-    dependencies:
-      d3-dispatch: 3.0.1
-      d3-drag: 3.0.0
-      d3-interpolate: 3.0.1
-      d3-selection: 3.0.0
-      d3-transition: 3.0.1(d3-selection@3.0.0)
-
-  d3-chord@3.0.1:
-    dependencies:
-      d3-path: 3.1.0
-
-  d3-color@3.1.0: {}
-
-  d3-contour@4.0.2:
-    dependencies:
-      d3-array: 3.2.4
-
-  d3-delaunay@6.0.4:
-    dependencies:
-      delaunator: 5.1.0
-
-  d3-dispatch@3.0.1: {}
-
-  d3-drag@3.0.0:
-    dependencies:
-      d3-dispatch: 3.0.1
-      d3-selection: 3.0.0
-
-  d3-dsv@3.0.1:
-    dependencies:
-      commander: 7.2.0
-      iconv-lite: 0.6.3
-      rw: 1.3.3
-
-  d3-ease@3.0.1: {}
-
-  d3-fetch@3.0.1:
-    dependencies:
-      d3-dsv: 3.0.1
-
-  d3-force@3.0.0:
-    dependencies:
-      d3-dispatch: 3.0.1
-      d3-quadtree: 3.0.1
-      d3-timer: 3.0.1
-
-  d3-format@3.1.2: {}
-
-  d3-geo@3.1.1:
-    dependencies:
-      d3-array: 3.2.4
-
-  d3-hierarchy@3.1.2: {}
-
-  d3-interpolate@3.0.1:
-    dependencies:
-      d3-color: 3.1.0
-
-  d3-path@1.0.9: {}
-
-  d3-path@3.1.0: {}
-
-  d3-polygon@3.0.1: {}
-
-  d3-quadtree@3.0.1: {}
-
-  d3-random@3.0.1: {}
-
-  d3-sankey@0.12.3:
-    dependencies:
-      d3-array: 2.12.1
-      d3-shape: 1.3.7
-
-  d3-scale-chromatic@3.1.0:
-    dependencies:
-      d3-color: 3.1.0
-      d3-interpolate: 3.0.1
-
-  d3-scale@4.0.2:
-    dependencies:
-      d3-array: 3.2.4
-      d3-format: 3.1.2
-      d3-interpolate: 3.0.1
-      d3-time: 3.1.0
-      d3-time-format: 4.1.0
-
-  d3-selection@3.0.0: {}
-
-  d3-shape@1.3.7:
-    dependencies:
-      d3-path: 1.0.9
-
-  d3-shape@3.2.0:
-    dependencies:
-      d3-path: 3.1.0
-
-  d3-time-format@4.1.0:
-    dependencies:
-      d3-time: 3.1.0
-
-  d3-time@3.1.0:
-    dependencies:
-      d3-array: 3.2.4
-
-  d3-timer@3.0.1: {}
-
-  d3-transition@3.0.1(d3-selection@3.0.0):
-    dependencies:
-      d3-color: 3.1.0
-      d3-dispatch: 3.0.1
-      d3-ease: 3.0.1
-      d3-interpolate: 3.0.1
-      d3-selection: 3.0.0
-      d3-timer: 3.0.1
-
-  d3-zoom@3.0.0:
-    dependencies:
-      d3-dispatch: 3.0.1
-      d3-drag: 3.0.0
-      d3-interpolate: 3.0.1
-      d3-selection: 3.0.0
-      d3-transition: 3.0.1(d3-selection@3.0.0)
-
-  d3@7.9.0:
-    dependencies:
-      d3-array: 3.2.4
-      d3-axis: 3.0.0
-      d3-brush: 3.0.0
-      d3-chord: 3.0.1
-      d3-color: 3.1.0
-      d3-contour: 4.0.2
-      d3-delaunay: 6.0.4
-      d3-dispatch: 3.0.1
-      d3-drag: 3.0.0
-      d3-dsv: 3.0.1
-      d3-ease: 3.0.1
-      d3-fetch: 3.0.1
-      d3-force: 3.0.0
-      d3-format: 3.1.2
-      d3-geo: 3.1.1
-      d3-hierarchy: 3.1.2
-      d3-interpolate: 3.0.1
-      d3-path: 3.1.0
-      d3-polygon: 3.0.1
-      d3-quadtree: 3.0.1
-      d3-random: 3.0.1
-      d3-scale: 4.0.2
-      d3-scale-chromatic: 3.1.0
-      d3-selection: 3.0.0
-      d3-shape: 3.2.0
-      d3-time: 3.1.0
-      d3-time-format: 4.1.0
-      d3-timer: 3.0.1
-      d3-transition: 3.0.1(d3-selection@3.0.0)
-      d3-zoom: 3.0.0
-
-  dagre-d3-es@7.0.14:
-    dependencies:
-      d3: 7.9.0
-      lodash-es: 4.18.1
-
-  dayjs@1.11.21: {}
-
-  debounce@1.2.1: {}
-
-  debug@2.6.9:
-    dependencies:
-      ms: 2.0.0
-
-  debug@4.4.3:
-    dependencies:
-      ms: 2.1.3
-
-  decode-named-character-reference@1.3.0:
-    dependencies:
-      character-entities: 2.0.2
-
-  decompress-response@6.0.0:
-    dependencies:
-      mimic-response: 3.1.0
-
-  deep-extend@0.6.0: {}
-
-  deep-is@0.1.4: {}
-
-  deepmerge@4.3.1: {}
-
-  default-browser-id@5.0.1: {}
-
-  default-browser@5.5.0:
-    dependencies:
-      bundle-name: 4.1.0
-      default-browser-id: 5.0.1
-
-  defer-to-connect@2.0.1: {}
-
-  define-data-property@1.1.4:
-    dependencies:
-      es-define-property: 1.0.1
-      es-errors: 1.3.0
-      gopd: 1.2.0
-
-  define-lazy-prop@2.0.0: {}
-
-  define-lazy-prop@3.0.0: {}
-
-  define-properties@1.2.1:
-    dependencies:
-      define-data-property: 1.1.4
-      has-property-descriptors: 1.0.2
-      object-keys: 1.1.1
-
-  delaunator@5.1.0:
-    dependencies:
-      robust-predicates: 3.0.3
-
-  depd@1.1.2: {}
-
-  depd@2.0.0: {}
-
-  dequal@2.0.3: {}
-
-  destroy@1.2.0: {}
-
-  detect-libc@2.1.2: {}
-
-  detect-node@2.1.0: {}
-
-  detect-package-manager@3.0.2:
-    dependencies:
-      execa: 5.1.1
-
-  detect-port@1.6.1:
-    dependencies:
-      address: 1.2.2
-      debug: 4.4.3
-    transitivePeerDependencies:
-      - supports-color
-
-  devlop@1.1.0:
-    dependencies:
-      dequal: 2.0.3
-
-  diff@5.2.2: {}
-
-  dir-glob@3.0.1:
-    dependencies:
-      path-type: 4.0.0
-
-  dns-packet@5.6.1:
-    dependencies:
-      '@leichtgewicht/ip-codec': 2.0.5
-
-  docusaurus-markdown-source-plugin@2.2.5(@docusaurus/core@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3))(react-dom@19.2.7(react@19.2.7))(react@19.2.7):
-    dependencies:
-      '@docusaurus/core': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      fs-extra: 11.3.6
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-
-  docusaurus-plugin-llms@0.4.0(@docusaurus/core@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)):
-    dependencies:
-      '@docusaurus/core': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      gray-matter: 4.0.3
-      minimatch: 9.0.9
-      yaml: 2.9.0
-
-  docusaurus-plugin-openapi-docs@5.1.0(@docusaurus/plugin-content-docs@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3))(@docusaurus/utils-validation@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@docusaurus/utils@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@types/json-schema@7.0.15)(react@19.2.7):
-    dependencies:
-      '@apidevtools/json-schema-ref-parser': 15.4.0(@types/json-schema@7.0.15)
-      '@docusaurus/plugin-content-docs': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      '@docusaurus/utils': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@docusaurus/utils-validation': 3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@redocly/openapi-core': 2.36.0
-      allof-merge: 0.6.8
-      chalk: 5.6.2
-      clsx: 2.1.1
-      fs-extra: 11.3.6
-      json-pointer: 0.6.2
-      json5: 2.2.3
-      lodash: 4.18.1
-      mustache: 4.2.0
-      openapi-to-postmanv2: 6.2.0
-      postman-collection: 5.3.0
-      react: 19.2.7
-      slugify: 1.6.9
-      swagger2openapi: 7.0.8
-      xml-formatter: 3.7.0
-    transitivePeerDependencies:
-      - '@types/json-schema'
-      - encoding
-
-  docusaurus-plugin-sass@0.2.6(@docusaurus/core@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(sass@1.101.0)(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)):
-    dependencies:
-      '@docusaurus/core': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      sass: 1.101.0
-      sass-loader: 16.0.8(@rspack/core@1.7.11(@swc/helpers@0.5.23))(sass@1.101.0)(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-    transitivePeerDependencies:
-      - '@rspack/core'
-      - node-sass
-      - sass-embedded
-      - webpack
-
-  docusaurus-plugin-sentry@2.1.0(@docusaurus/core@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3))(react-dom@19.2.7(react@19.2.7))(react@19.2.7):
-    dependencies:
-      '@docusaurus/core': 3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3)
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-
-  docusaurus-theme-openapi-docs@5.1.0(722036656f7e1999e1a6989345bc7722):
-    dependencies:
-      '@docusaurus/theme-common': 3.10.1(@docusaurus/plugin-content-docs@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      '@hookform/error-message': 2.0.1(react-dom@19.2.7(react@19.2.7))(react-hook-form@7.80.0(react@19.2.7))(react@19.2.7)
-      '@reduxjs/toolkit': 2.12.0(react-redux@9.3.0(@types/react@19.2.17)(react@19.2.7)(redux@5.0.1))(react@19.2.7)
-      allof-merge: 0.6.8
-      buffer: 6.0.3
-      clsx: 2.1.1
-      copy-text-to-clipboard: 3.2.2
-      crypto-js: 4.2.0
-      docusaurus-plugin-openapi-docs: 5.1.0(@docusaurus/plugin-content-docs@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3))(@docusaurus/utils-validation@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@docusaurus/utils@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@types/json-schema@7.0.15)(react@19.2.7)
-      docusaurus-plugin-sass: 0.2.6(@docusaurus/core@3.10.1(@docusaurus/faster@3.10.1(@docusaurus/types@3.10.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7))(@swc/helpers@0.5.23)(postcss@8.5.15))(@mdx-js/react@3.1.1(@types/react@19.2.17)(react@19.2.7))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(react-dom@19.2.7(react@19.2.7))(react@19.2.7)(typescript@6.0.3))(@rspack/core@1.7.11(@swc/helpers@0.5.23))(sass@1.101.0)(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      file-saver: 2.0.5
-      lodash: 4.18.1
-      pako: 2.2.0
-      path-browserify: 1.0.1
-      postman-code-generators: 2.1.1
-      postman-collection: 5.3.0
-      prism-react-renderer: 2.4.1(react@19.2.7)
-      process: 0.11.10
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      react-hook-form: 7.80.0(react@19.2.7)
-      react-live: 4.1.8(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      react-magic-dropzone: 1.0.1
-      react-markdown: 10.1.0(@types/react@19.2.17)(react@19.2.7)
-      react-modal: 3.16.3(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      react-redux: 9.3.0(@types/react@19.2.17)(react@19.2.7)(redux@5.0.1)
-      rehype-raw: 7.0.0
-      remark-gfm: 4.0.1
-      sass: 1.101.0
-      sass-loader: 16.0.8(@rspack/core@1.7.11(@swc/helpers@0.5.23))(sass@1.101.0)(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      unist-util-visit: 5.1.0
-      url: 0.11.4
-      xml-formatter: 3.7.0
-    transitivePeerDependencies:
-      - '@rspack/core'
-      - '@types/react'
-      - node-sass
-      - redux
-      - sass-embedded
-      - supports-color
-      - webpack
+  '@img/sharp-libvips-linux-s390x@1.0.4':
+    optional: true
 
-  dom-converter@0.2.0:
-    dependencies:
-      utila: 0.4.0
+  '@img/sharp-libvips-linux-x64@1.0.4':
+    optional: true
 
-  dom-helpers@3.4.0:
-    dependencies:
-      '@babel/runtime': 7.29.7
+  '@img/sharp-libvips-linuxmusl-arm64@1.0.4':
+    optional: true
 
-  dom-helpers@5.2.1:
-    dependencies:
-      '@babel/runtime': 7.29.7
-      csstype: 3.2.3
+  '@img/sharp-libvips-linuxmusl-x64@1.0.4':
+    optional: true
 
-  dom-serializer@1.4.1:
-    dependencies:
-      domelementtype: 2.3.0
-      domhandler: 4.3.1
-      entities: 2.2.0
+  '@img/sharp-linux-arm64@0.33.5':
+    optionalDependencies:
+      '@img/sharp-libvips-linux-arm64': 1.0.4
+    optional: true
 
-  dom-serializer@2.0.0:
-    dependencies:
-      domelementtype: 2.3.0
-      domhandler: 5.0.3
-      entities: 4.5.0
+  '@img/sharp-linux-arm@0.33.5':
+    optionalDependencies:
+      '@img/sharp-libvips-linux-arm': 1.0.5
+    optional: true
 
-  domelementtype@2.3.0: {}
+  '@img/sharp-linux-s390x@0.33.5':
+    optionalDependencies:
+      '@img/sharp-libvips-linux-s390x': 1.0.4
+    optional: true
 
-  domhandler@4.3.1:
-    dependencies:
-      domelementtype: 2.3.0
+  '@img/sharp-linux-x64@0.33.5':
+    optionalDependencies:
+      '@img/sharp-libvips-linux-x64': 1.0.4
+    optional: true
 
-  domhandler@5.0.3:
-    dependencies:
-      domelementtype: 2.3.0
+  '@img/sharp-linuxmusl-arm64@0.33.5':
+    optionalDependencies:
+      '@img/sharp-libvips-linuxmusl-arm64': 1.0.4
+    optional: true
 
-  dompurify@3.4.8:
+  '@img/sharp-linuxmusl-x64@0.33.5':
     optionalDependencies:
-      '@types/trusted-types': 2.0.7
+      '@img/sharp-libvips-linuxmusl-x64': 1.0.4
+    optional: true
 
-  domutils@2.8.0:
+  '@img/sharp-wasm32@0.33.5':
     dependencies:
-      dom-serializer: 1.4.1
-      domelementtype: 2.3.0
-      domhandler: 4.3.1
+      '@emnapi/runtime': 1.11.3
+    optional: true
 
-  domutils@3.2.2:
-    dependencies:
-      dom-serializer: 2.0.0
-      domelementtype: 2.3.0
-      domhandler: 5.0.3
+  '@img/sharp-win32-ia32@0.33.5':
+    optional: true
 
-  dot-case@3.0.4:
-    dependencies:
-      no-case: 3.0.4
-      tslib: 2.8.1
+  '@img/sharp-win32-x64@0.33.5':
+    optional: true
 
-  dot-prop@6.0.1:
-    dependencies:
-      is-obj: 2.0.0
+  '@inquirer/ansi@1.0.2': {}
 
-  dunder-proto@1.0.1:
+  '@inquirer/checkbox@4.3.2(@types/node@26.6.5)':
     dependencies:
-      call-bind-apply-helpers: 1.0.2
-      es-errors: 1.3.0
-      gopd: 1.2.0
-
-  duplexer@0.1.2: {}
-
-  eastasianwidth@0.2.0: {}
-
-  ee-first@1.1.1: {}
-
-  electron-to-chromium@1.5.370: {}
-
-  emoji-regex@10.6.0: {}
-
-  emoji-regex@8.0.0: {}
-
-  emoji-regex@9.2.2: {}
-
-  emojilib@2.4.0: {}
-
-  emojis-list@3.0.0: {}
-
-  emoticon@4.1.0: {}
-
-  encodeurl@2.0.0: {}
+      '@inquirer/ansi': 1.0.2
+      '@inquirer/core': 10.3.2(@types/node@26.6.5)
+      '@inquirer/figures': 1.0.15
+      '@inquirer/type': 3.0.10(@types/node@26.6.5)
+      yoctocolors-cjs: 2.1.3
+    optionalDependencies:
+      '@types/node': 26.6.5
 
-  enhanced-resolve@5.23.0:
+  '@inquirer/confirm@5.1.21(@types/node@26.6.5)':
     dependencies:
-      graceful-fs: 4.2.11
-      tapable: 2.3.3
-
-  entities@2.2.0: {}
-
-  entities@4.5.0: {}
-
-  entities@6.0.1: {}
+      '@inquirer/core': 10.3.2(@types/node@26.6.5)
+      '@inquirer/type': 3.0.10(@types/node@26.6.5)
+    optionalDependencies:
+      '@types/node': 26.6.5
+
+  '@inquirer/core@10.3.2(@types/node@26.6.5)':
+    dependencies:
+      '@inquirer/ansi': 1.0.2
+      '@inquirer/figures': 1.0.15
+      '@inquirer/type': 3.0.10(@types/node@26.6.5)
+      cli-width: 4.1.0
+      mute-stream: 2.0.0
+      signal-exit: 4.1.0
+      wrap-ansi: 6.2.0
+      yoctocolors-cjs: 2.1.3
+    optionalDependencies:
+      '@types/node': 26.6.5
 
-  error-ex@1.3.4:
+  '@inquirer/editor@4.2.23(@types/node@26.6.5)':
     dependencies:
-      is-arrayish: 0.2.1
+      '@inquirer/core': 10.3.2(@types/node@26.6.5)
+      '@inquirer/external-editor': 1.0.3(@types/node@26.6.5)
+      '@inquirer/type': 3.0.10(@types/node@26.6.5)
+    optionalDependencies:
+      '@types/node': 26.6.5
 
-  error-stack-parser@2.1.4:
+  '@inquirer/expand@4.0.23(@types/node@26.6.5)':
     dependencies:
-      stackframe: 1.3.4
-
-  es-define-property@1.0.1: {}
-
-  es-errors@1.3.0: {}
-
-  es-module-lexer@2.1.0: {}
+      '@inquirer/core': 10.3.2(@types/node@26.6.5)
+      '@inquirer/type': 3.0.10(@types/node@26.6.5)
+      yoctocolors-cjs: 2.1.3
+    optionalDependencies:
+      '@types/node': 26.6.5
 
-  es-object-atoms@1.1.2:
+  '@inquirer/external-editor@1.0.3(@types/node@26.6.5)':
     dependencies:
-      es-errors: 1.3.0
-
-  es-toolkit@1.47.0: {}
+      chardet: 2.2.0
+      iconv-lite: 0.7.3
+    optionalDependencies:
+      '@types/node': 26.6.5
 
-  es6-promise@3.3.1: {}
+  '@inquirer/figures@1.0.15': {}
 
-  esast-util-from-estree@2.0.0:
-    dependencies:
-      '@types/estree-jsx': 1.0.5
-      devlop: 1.1.0
-      estree-util-visit: 2.0.0
-      unist-util-position-from-estree: 2.0.0
+  '@inquirer/input@4.3.1(@types/node@26.6.5)':
+    dependencies:
+      '@inquirer/core': 10.3.2(@types/node@26.6.5)
+      '@inquirer/type': 3.0.10(@types/node@26.6.5)
+    optionalDependencies:
+      '@types/node': 26.6.5
 
-  esast-util-from-js@2.0.1:
+  '@inquirer/number@3.0.23(@types/node@26.6.5)':
     dependencies:
-      '@types/estree-jsx': 1.0.5
-      acorn: 8.16.0
-      esast-util-from-estree: 2.0.0
-      vfile-message: 4.0.3
+      '@inquirer/core': 10.3.2(@types/node@26.6.5)
+      '@inquirer/type': 3.0.10(@types/node@26.6.5)
+    optionalDependencies:
+      '@types/node': 26.6.5
 
-  escalade@3.2.0: {}
+  '@inquirer/password@4.0.23(@types/node@26.6.5)':
+    dependencies:
+      '@inquirer/ansi': 1.0.2
+      '@inquirer/core': 10.3.2(@types/node@26.6.5)
+      '@inquirer/type': 3.0.10(@types/node@26.6.5)
+    optionalDependencies:
+      '@types/node': 26.6.5
+
+  '@inquirer/prompts@7.9.0(@types/node@26.6.5)':
+    dependencies:
+      '@inquirer/checkbox': 4.3.2(@types/node@26.6.5)
+      '@inquirer/confirm': 5.1.21(@types/node@26.6.5)
+      '@inquirer/editor': 4.2.23(@types/node@26.6.5)
+      '@inquirer/expand': 4.0.23(@types/node@26.6.5)
+      '@inquirer/input': 4.3.1(@types/node@26.6.5)
+      '@inquirer/number': 3.0.23(@types/node@26.6.5)
+      '@inquirer/password': 4.0.23(@types/node@26.6.5)
+      '@inquirer/rawlist': 4.1.11(@types/node@26.6.5)
+      '@inquirer/search': 3.2.2(@types/node@26.6.5)
+      '@inquirer/select': 4.4.2(@types/node@26.6.5)
+    optionalDependencies:
+      '@types/node': 26.6.5
 
-  escape-goat@4.0.0: {}
+  '@inquirer/rawlist@4.1.11(@types/node@26.6.5)':
+    dependencies:
+      '@inquirer/core': 10.3.2(@types/node@26.6.5)
+      '@inquirer/type': 3.0.10(@types/node@26.6.5)
+      yoctocolors-cjs: 2.1.3
+    optionalDependencies:
+      '@types/node': 26.6.5
 
-  escape-html@1.0.3: {}
+  '@inquirer/search@3.2.2(@types/node@26.6.5)':
+    dependencies:
+      '@inquirer/core': 10.3.2(@types/node@26.6.5)
+      '@inquirer/figures': 1.0.15
+      '@inquirer/type': 3.0.10(@types/node@26.6.5)
+      yoctocolors-cjs: 2.1.3
+    optionalDependencies:
+      '@types/node': 26.6.5
 
-  escape-string-regexp@4.0.0: {}
+  '@inquirer/select@4.4.2(@types/node@26.6.5)':
+    dependencies:
+      '@inquirer/ansi': 1.0.2
+      '@inquirer/core': 10.3.2(@types/node@26.6.5)
+      '@inquirer/figures': 1.0.15
+      '@inquirer/type': 3.0.10(@types/node@26.6.5)
+      yoctocolors-cjs: 2.1.3
+    optionalDependencies:
+      '@types/node': 26.6.5
 
-  escape-string-regexp@5.0.0: {}
+  '@inquirer/type@3.0.10(@types/node@26.6.5)':
+    optionalDependencies:
+      '@types/node': 26.6.5
 
-  eslint-scope@5.1.1:
+  '@isaacs/fs-minipass@4.0.1':
     dependencies:
-      esrecurse: 4.3.0
-      estraverse: 4.3.0
+      minipass: 7.1.3
 
-  eslint-scope@9.1.2:
+  '@jridgewell/gen-mapping@0.3.13':
     dependencies:
-      '@types/esrecurse': 4.3.1
-      '@types/estree': 1.0.9
-      esrecurse: 4.3.0
-      estraverse: 5.3.0
+      '@jridgewell/sourcemap-codec': 1.6.0
+      '@jridgewell/trace-mapping': 0.3.31
 
-  eslint-visitor-keys@3.4.3: {}
+  '@jridgewell/resolve-uri@3.1.2': {}
 
-  eslint-visitor-keys@4.2.1: {}
+  '@jridgewell/sourcemap-codec@1.6.0': {}
 
-  eslint-visitor-keys@5.0.1: {}
+  '@jridgewell/trace-mapping@0.3.31':
+    dependencies:
+      '@jridgewell/resolve-uri': 3.1.2
+      '@jridgewell/sourcemap-codec': 1.6.0
 
-  eslint@10.6.0(jiti@1.21.7):
+  '@jsep-plugin/assignment@1.4.0(jsep@1.6.0)':
     dependencies:
-      '@eslint-community/eslint-utils': 4.9.1(eslint@10.6.0(jiti@1.21.7))
-      '@eslint-community/regexpp': 4.12.2
-      '@eslint/config-array': 0.23.5
-      '@eslint/config-helpers': 0.6.0
-      '@eslint/core': 1.2.1
-      '@eslint/plugin-kit': 0.7.2
-      '@humanfs/node': 0.16.8
-      '@humanwhocodes/module-importer': 1.0.1
-      '@humanwhocodes/retry': 0.4.3
-      '@types/estree': 1.0.9
-      ajv: 6.15.0
-      cross-spawn: 7.0.6
-      debug: 4.4.3
-      escape-string-regexp: 4.0.0
-      eslint-scope: 9.1.2
-      eslint-visitor-keys: 5.0.1
-      espree: 11.2.0
-      esquery: 1.7.0
-      esutils: 2.0.3
-      fast-deep-equal: 3.1.3
-      file-entry-cache: 8.0.0
-      find-up: 5.0.0
-      glob-parent: 6.0.2
-      ignore: 5.3.2
-      imurmurhash: 0.1.4
-      is-glob: 4.0.3
-      json-stable-stringify-without-jsonify: 1.0.1
-      minimatch: 10.2.5
-      natural-compare: 1.4.0
-      optionator: 0.9.4
-    optionalDependencies:
-      jiti: 1.21.7
-    transitivePeerDependencies:
-      - supports-color
+      jsep: 1.6.0
 
-  espree@10.4.0:
+  '@jsep-plugin/regex@1.1.0(jsep@1.6.0)':
     dependencies:
-      acorn: 8.16.0
-      acorn-jsx: 5.3.2(acorn@8.16.0)
-      eslint-visitor-keys: 4.2.1
+      jsep: 1.6.0
 
-  espree@11.2.0:
+  '@jsep-plugin/ternary@1.2.0(jsep@1.6.0)':
     dependencies:
-      acorn: 8.17.0
-      acorn-jsx: 5.3.2(acorn@8.17.0)
-      eslint-visitor-keys: 5.0.1
+      jsep: 1.6.0
 
-  esprima@4.0.1: {}
+  '@json-schema-spec/json-pointer@0.1.2': {}
 
-  esquery@1.7.0:
+  '@json-schema-tools/dereferencer@1.6.3':
     dependencies:
-      estraverse: 5.3.0
+      '@json-schema-tools/reference-resolver': 1.2.6
+      '@json-schema-tools/traverse': 1.11.0
+      fast-safe-stringify: 2.1.1
+    transitivePeerDependencies:
+      - encoding
+
+  '@json-schema-tools/meta-schema@1.8.0': {}
 
-  esrecurse@4.3.0:
+  '@json-schema-tools/reference-resolver@1.2.6':
     dependencies:
-      estraverse: 5.3.0
+      '@json-schema-spec/json-pointer': 0.1.2
+      isomorphic-fetch: 3.0.0
+    transitivePeerDependencies:
+      - encoding
 
-  estraverse@4.3.0: {}
+  '@json-schema-tools/traverse@1.11.0': {}
 
-  estraverse@5.3.0: {}
+  '@leichtgewicht/ip-codec@2.0.5': {}
 
-  estree-util-attach-comments@3.0.0:
+  '@mdx-js/mdx@3.1.1':
     dependencies:
       '@types/estree': 1.0.9
-
-  estree-util-build-jsx@3.0.1:
-    dependencies:
       '@types/estree-jsx': 1.0.5
+      '@types/hast': 3.0.5
+      '@types/mdx': 2.0.14
+      acorn: 8.11.2
+      collapse-white-space: 2.1.0
       devlop: 1.1.0
       estree-util-is-identifier-name: 3.0.0
+      estree-util-scope: 1.0.1
       estree-walker: 3.0.3
+      hast-util-to-jsx-runtime: 2.3.6
+      markdown-extensions: 2.0.0
+      recma-build-jsx: 1.0.0
+      recma-jsx: 1.0.1(acorn@8.11.2)
+      recma-stringify: 1.0.0
+      rehype-recma: 1.0.0
+      remark-mdx: 3.1.1
+      remark-parse: 11.0.0
+      remark-rehype: 11.1.1
+      source-map: 0.7.6
+      unified: 11.0.5
+      unist-util-position-from-estree: 2.0.0
+      unist-util-stringify-position: 4.0.0
+      unist-util-visit: 5.0.0
+      vfile: 6.0.3
+    transitivePeerDependencies:
+      - supports-color
 
-  estree-util-is-identifier-name@3.0.0: {}
-
-  estree-util-scope@1.0.0:
+  '@mdx-js/react@3.1.1(@types/react@19.3.0)(react@19.2.3)':
     dependencies:
-      '@types/estree': 1.0.9
-      devlop: 1.1.0
+      '@types/mdx': 2.0.14
+      '@types/react': 19.3.0
+      react: 19.2.3
+
+  '@mintlify/cli@4.0.1665(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/node@26.6.5)(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(typescript@6.0.3)':
+    dependencies:
+      '@inquirer/prompts': 7.9.0(@types/node@26.6.5)
+      '@mintlify/common': 1.0.1260(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)
+      '@mintlify/link-rot': 3.0.1481(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)
+      '@mintlify/models': 0.0.375
+      '@mintlify/og': 0.0.58(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(typescript@6.0.3)
+      '@mintlify/prebuild': 1.0.1425(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)
+      '@mintlify/previewing': 4.0.1501(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(typescript@6.0.3)
+      '@mintlify/validation': 0.1.923(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)
+      adm-zip: 0.6.0
+      chalk: 5.2.0
+      color: 4.2.3
+      detect-port: 1.5.1
+      fs-extra: 11.2.0
+      ink: 6.3.0(@types/react@19.3.0)(react@19.2.3)
+      inquirer: 12.3.0(@types/node@26.6.5)
+      js-yaml: 4.3.1
+      mdast-util-mdx-jsx: 3.2.0
+      open: 8.4.2
+      openid-client: 6.8.2
+      posthog-node: 5.17.2
+      prosemirror-model: 1.25.4
+      react: 19.2.3
+      remark: 15.0.1
+      remark-frontmatter: 5.0.0
+      remark-gfm: 4.0.1
+      remark-math: 6.0.0
+      remark-mdx: 3.1.1
+      remark-stringify: 11.0.0
+      unified: 11.0.5
+      unist-util-visit: 5.0.0
+      yaml: 2.8.3
+      yargs: 17.7.1
+      zod: 4.3.6
+    optionalDependencies:
+      keytar: 7.9.0
+    transitivePeerDependencies:
+      - '@base-ui/react'
+      - '@types/node'
+      - '@types/react'
+      - bufferutil
+      - debug
+      - encoding
+      - puppeteer
+      - react-devtools-core
+      - react-dom
+      - supports-color
+      - ts-node
+      - typescript
+      - utf-8-validate
 
-  estree-util-to-js@2.0.0:
+  '@mintlify/common@1.0.1260(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)':
     dependencies:
-      '@types/estree-jsx': 1.0.5
-      astring: 1.9.0
-      source-map: 0.7.6
+      '@asyncapi/parser': 3.4.0
+      '@mintlify/mdx': 4.0.7(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)
+      '@mintlify/models': 0.0.375
+      '@mintlify/openapi-parser': 0.0.9
+      '@mintlify/validation': 0.1.923(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)
+      '@sindresorhus/slugify': 2.2.0
+      '@types/mdast': 4.0.4
+      acorn: 8.11.2
+      acorn-jsx: 5.3.2(acorn@8.11.2)
+      estree-util-to-js: 2.0.0
+      estree-walker: 3.0.3
+      front-matter: 4.0.2
+      hast-util-from-html: 2.0.3
+      hast-util-to-estree: 3.1.0
+      hast-util-to-html: 9.0.4
+      ignore: 7.0.5
+      iregexp-check: 0.1.2
+      js-yaml: 4.3.1
+      json-p3: 2.2.2
+      lodash: 4.18.1
+      mdast-util-from-markdown: 2.0.2
+      mdast-util-gfm: 3.0.0
+      mdast-util-mdx: 3.0.0
+      mdast-util-mdx-jsx: 3.1.3
+      micromark-extension-gfm: 3.0.0
+      micromark-extension-mdxjs: 3.0.0
+      openapi-types: 12.1.3
+      postcss: 8.5.23
+      re2js: 2.8.6
+      rehype-katex: 7.0.1
+      rehype-stringify: 10.0.1
+      remark: 15.0.1
+      remark-frontmatter: 5.0.0
+      remark-gfm: 4.0.0
+      remark-math: 6.0.0
+      remark-mdx: 3.1.0
+      remark-parse: 11.0.0
+      remark-rehype: 11.1.1
+      remark-smartypants: 3.0.2
+      remark-stringify: 11.0.0
+      sucrase: 3.34.0
+      tailwindcss-v3: tailwindcss@3.4.17
+      unified: 11.0.5
+      unist-builder: 4.0.0
+      unist-util-map: 4.0.0
+      unist-util-remove: 4.0.0
+      unist-util-remove-position: 5.0.0
+      unist-util-visit: 5.0.0
+      unist-util-visit-parents: 6.0.1
+      valibot: 1.5.0(typescript@6.0.3)
+      vfile: 6.0.3
+      xss: 1.0.15
+    transitivePeerDependencies:
+      - '@base-ui/react'
+      - '@types/react'
+      - debug
+      - encoding
+      - react
+      - react-dom
+      - supports-color
+      - ts-node
+      - typescript
 
-  estree-util-value-to-estree@3.5.0:
+  '@mintlify/link-rot@3.0.1481(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)':
     dependencies:
-      '@types/estree': 1.0.9
+      '@mintlify/common': 1.0.1260(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)
+      '@mintlify/models': 0.0.375
+      '@mintlify/prebuild': 1.0.1425(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)
+      '@mintlify/previewing': 4.0.1501(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(typescript@6.0.3)
+      '@mintlify/scraping': 4.0.1133(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)
+      '@mintlify/validation': 0.1.923(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)
+      fs-extra: 11.1.0
+      remark-smartypants: 3.0.2
+      unist-util-visit: 4.1.2
+    transitivePeerDependencies:
+      - '@base-ui/react'
+      - '@types/react'
+      - bufferutil
+      - debug
+      - encoding
+      - puppeteer
+      - react
+      - react-devtools-core
+      - react-dom
+      - supports-color
+      - ts-node
+      - typescript
+      - utf-8-validate
 
-  estree-util-visit@2.0.0:
+  '@mintlify/mdx@4.0.7(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)':
     dependencies:
-      '@types/estree-jsx': 1.0.5
-      '@types/unist': 3.0.3
+      '@base-ui/react': 1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)
+      '@shikijs/transformers': 3.23.0
+      '@shikijs/twoslash': 3.23.0(typescript@6.0.3)
+      arktype: 2.2.8
+      hast-util-to-string: 3.0.1
+      mdast-util-from-markdown: 2.0.2
+      mdast-util-gfm: 3.1.0
+      mdast-util-mdx-jsx: 3.2.0
+      mdast-util-to-hast: 13.2.1
+      next-mdx-remote-client: 2.1.12(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(unified@11.0.5)
+      react: 19.2.3
+      react-dom: 19.3.1(react@19.2.3)
+      rehype-katex: 7.0.1
+      remark-gfm: 4.0.1
+      remark-math: 6.0.0
+      remark-smartypants: 3.0.2
+      shiki: 3.23.0
+      twoslash: 0.3.9(typescript@6.0.3)
+      unified: 11.0.5
+      unist-util-visit: 5.0.0
+    transitivePeerDependencies:
+      - '@types/react'
+      - supports-color
+      - typescript
 
-  estree-walker@3.0.3:
+  '@mintlify/models@0.0.375':
     dependencies:
-      '@types/estree': 1.0.9
+      axios: 1.18.0
+      openapi-types: 12.1.3
+    transitivePeerDependencies:
+      - debug
+      - supports-color
 
-  esutils@2.0.3: {}
+  '@mintlify/og@0.0.58(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(typescript@6.0.3)':
+    dependencies:
+      '@mintlify/common': 1.0.1260(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)
+      '@mintlify/validation': 0.1.923(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)
+      '@resvg/resvg-wasm': 2.6.2
+      '@shuding/opentype.js': 1.4.0-beta.0
+      image-size: 2.0.2
+      react: 19.2.3
+      satori: 0.33.5
+    transitivePeerDependencies:
+      - '@base-ui/react'
+      - '@types/react'
+      - debug
+      - encoding
+      - react-dom
+      - supports-color
+      - ts-node
+      - typescript
 
-  eta@2.2.0: {}
+  '@mintlify/openapi-parser@0.0.9':
+    dependencies:
+      ajv: 8.20.0
+      ajv-draft-04: 1.0.0(ajv@8.20.0)
+      ajv-formats: 3.0.1(ajv@8.20.0)
+      jsonpointer: 5.0.1
+      leven: 4.1.0
+      yaml: 2.8.3
 
-  etag@1.8.1: {}
+  '@mintlify/package-builder@0.0.48':
+    dependencies:
+      entities: 7.0.1
+      esbuild: 0.25.12
+      js-yaml: 4.3.1
+      semver: 7.7.4
+    optional: true
 
-  eval@0.1.8:
+  '@mintlify/prebuild@1.0.1425(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)':
     dependencies:
-      '@types/node': 25.9.2
-      require-like: 0.1.2
+      '@mintlify/common': 1.0.1260(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)
+      '@mintlify/scraping': 4.0.1133(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)
+      '@mintlify/validation': 0.1.923(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)
+      chalk: 5.3.0
+      favicons: 7.2.0
+      fflate: 0.8.2
+      fs-extra: 11.1.0
+      js-yaml: 4.3.1
+      openapi-types: 12.1.3
+      sharp: 0.33.5
+      sharp-ico: 0.1.5
+      uuid: 11.1.1
+    transitivePeerDependencies:
+      - '@base-ui/react'
+      - '@types/react'
+      - debug
+      - encoding
+      - puppeteer
+      - react
+      - react-dom
+      - supports-color
+      - ts-node
+      - typescript
 
-  eventemitter3@4.0.7: {}
+  '@mintlify/previewing@4.0.1501(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(typescript@6.0.3)':
+    dependencies:
+      '@mintlify/common': 1.0.1260(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)
+      '@mintlify/prebuild': 1.0.1425(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)
+      '@mintlify/validation': 0.1.923(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)
+      adm-zip: 0.6.0
+      better-opn: 3.0.2
+      chalk: 5.2.0
+      chokidar: 3.5.3
+      express: 4.22.0
+      fs-extra: 11.1.0
+      got: 13.0.0
+      ink: 6.3.0(@types/react@19.3.0)(react@19.2.3)
+      ink-spinner: 5.0.0(ink@6.3.0(@types/react@19.3.0)(react@19.2.3))(react@19.2.3)
+      is-online: 10.0.0
+      js-yaml: 4.3.1
+      react: 19.2.3
+      socket.io: 4.8.0
+      tar: 7.5.21
+      yargs: 17.7.1
+    optionalDependencies:
+      '@mintlify/package-builder': 0.0.48
+    transitivePeerDependencies:
+      - '@base-ui/react'
+      - '@types/react'
+      - bufferutil
+      - debug
+      - encoding
+      - puppeteer
+      - react-devtools-core
+      - react-dom
+      - supports-color
+      - ts-node
+      - typescript
+      - utf-8-validate
 
-  events@3.3.0: {}
+  '@mintlify/scraping@4.0.1133(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)':
+    dependencies:
+      '@mintlify/common': 1.0.1260(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)
+      fast-xml-parser: 5.7.3
+      fs-extra: 11.1.1
+      graphql: 16.11.0
+      hast-util-to-mdast: 10.1.0
+      js-yaml: 4.3.1
+      mdast-util-mdx-jsx: 3.1.3
+      neotraverse: 0.6.18
+      rehype-parse: 9.0.1
+      remark-gfm: 4.0.0
+      remark-mdx: 3.0.1
+      remark-parse: 11.0.0
+      remark-stringify: 11.0.0
+      unified: 11.0.5
+      unist-util-visit: 5.0.0
+      yargs: 17.7.1
+      zod: 3.24.0
+    transitivePeerDependencies:
+      - '@base-ui/react'
+      - '@types/react'
+      - debug
+      - encoding
+      - react
+      - react-dom
+      - supports-color
+      - ts-node
+      - typescript
 
-  execa@5.1.1:
+  '@mintlify/validation@0.1.923(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)':
     dependencies:
-      cross-spawn: 7.0.6
-      get-stream: 6.0.1
-      human-signals: 2.1.0
-      is-stream: 2.0.1
-      merge-stream: 2.0.0
-      npm-run-path: 4.0.1
-      onetime: 5.1.2
-      signal-exit: 3.0.7
-      strip-final-newline: 2.0.0
+      '@mintlify/mdx': 4.0.7(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(typescript@6.0.3)
+      '@mintlify/models': 0.0.375
+      fractional-indexing: 3.2.0
+      js-yaml: 4.3.1
+      lcm: 0.0.3
+      lodash: 4.18.1
+      neotraverse: 0.6.18
+      object-hash: 3.0.0
+      openapi-types: 12.1.3
+      uuid: 11.1.1
+      zod: 3.24.0
+      zod-to-json-schema: 3.20.4(zod@3.24.0)
+    transitivePeerDependencies:
+      - '@base-ui/react'
+      - '@types/react'
+      - debug
+      - react
+      - react-dom
+      - supports-color
+      - typescript
 
-  exenv@1.2.2: {}
+  '@nodable/entities@2.2.0': {}
 
-  express@4.22.2:
+  '@nodelib/fs.scandir@2.1.5':
     dependencies:
-      accepts: 1.3.8
-      array-flatten: 1.1.1
-      body-parser: 1.20.5
-      content-disposition: 0.5.4
-      content-type: 1.0.5
-      cookie: 0.7.2
-      cookie-signature: 1.0.7
-      debug: 2.6.9
-      depd: 2.0.0
-      encodeurl: 2.0.0
-      escape-html: 1.0.3
-      etag: 1.8.1
-      finalhandler: 1.3.2
-      fresh: 0.5.2
-      http-errors: 2.0.1
-      merge-descriptors: 1.0.3
-      methods: 1.1.2
-      on-finished: 2.4.1
-      parseurl: 1.3.3
-      path-to-regexp: 0.1.13
-      proxy-addr: 2.0.7
-      qs: 6.15.3
-      range-parser: 1.2.1
-      safe-buffer: 5.2.1
-      send: 0.19.2
-      serve-static: 1.16.3
-      setprototypeof: 1.2.0
-      statuses: 2.0.2
-      type-is: 1.6.18
-      utils-merge: 1.0.1
-      vary: 1.1.2
+      '@nodelib/fs.stat': 2.0.5
+      run-parallel: 1.2.0
+
+  '@nodelib/fs.stat@2.0.5': {}
+
+  '@nodelib/fs.walk@1.2.8':
+    dependencies:
+      '@nodelib/fs.scandir': 2.1.5
+      fastq: 1.20.3
+
+  '@open-rpc/schema-utils-js@2.2.1':
+    dependencies:
+      '@json-schema-tools/dereferencer': 1.6.3
+      '@json-schema-tools/meta-schema': 1.8.0
+      '@json-schema-tools/reference-resolver': 1.2.6
+      '@open-rpc/spec-types': 0.0.2
+      '@open-rpc/specification-extension-spec': 1.0.2
+      ajv: 6.15.0
+      detect-node: 2.1.0
+      fast-safe-stringify: 2.1.1
+      fs-extra: 10.1.0
+      is-url: 1.2.4
+      isomorphic-fetch: 3.0.0
     transitivePeerDependencies:
-      - supports-color
+      - encoding
 
-  extend-shallow@2.0.1:
+  '@open-rpc/spec-types@0.0.2':
     dependencies:
-      is-extendable: 0.1.1
+      '@open-rpc/spec': 1.4.1
 
-  extend@3.0.2: {}
+  '@open-rpc/spec@1.4.1': {}
 
-  fast-deep-equal@3.1.3: {}
+  '@open-rpc/specification-extension-spec@1.0.2': {}
 
-  fast-glob@3.3.3:
+  '@openapi-contrib/openapi-schema-to-json-schema@3.2.0':
     dependencies:
-      '@nodelib/fs.stat': 2.0.5
-      '@nodelib/fs.walk': 1.2.8
-      glob-parent: 5.1.2
-      merge2: 1.4.1
-      micromatch: 4.0.8
+      fast-deep-equal: 3.1.3
 
-  fast-json-stable-stringify@2.1.0: {}
+  '@posthog/core@1.7.1':
+    dependencies:
+      cross-spawn: 7.0.6
 
-  fast-levenshtein@2.0.6: {}
+  '@redocly/cli@2.38.0': {}
 
-  fast-safe-stringify@2.1.1: {}
+  '@resvg/resvg-wasm@2.6.2': {}
 
-  fast-shallow-equal@1.0.0: {}
+  '@scarf/scarf@1.4.0': {}
 
-  fast-uri@3.1.2: {}
+  '@shikijs/core@3.23.0':
+    dependencies:
+      '@shikijs/types': 3.23.0
+      '@shikijs/vscode-textmate': 10.0.2
+      '@types/hast': 3.0.5
+      hast-util-to-html: 9.0.5
 
-  fast-uri@3.1.3: {}
+  '@shikijs/engine-javascript@3.23.0':
+    dependencies:
+      '@shikijs/types': 3.23.0
+      '@shikijs/vscode-textmate': 10.0.2
+      oniguruma-to-es: 4.3.6
 
-  fast-uri@3.1.5: {}
+  '@shikijs/engine-oniguruma@3.23.0':
+    dependencies:
+      '@shikijs/types': 3.23.0
+      '@shikijs/vscode-textmate': 10.0.2
 
-  fastest-stable-stringify@2.0.2: {}
+  '@shikijs/langs@3.23.0':
+    dependencies:
+      '@shikijs/types': 3.23.0
 
-  fastq@1.20.1:
+  '@shikijs/themes@3.23.0':
     dependencies:
-      reusify: 1.1.0
+      '@shikijs/types': 3.23.0
 
-  fault@1.0.4:
+  '@shikijs/transformers@3.23.0':
     dependencies:
-      format: 0.2.2
+      '@shikijs/core': 3.23.0
+      '@shikijs/types': 3.23.0
 
-  fault@2.0.1:
+  '@shikijs/twoslash@3.23.0(typescript@6.0.3)':
     dependencies:
-      format: 0.2.2
+      '@shikijs/core': 3.23.0
+      '@shikijs/types': 3.23.0
+      twoslash: 0.3.9(typescript@6.0.3)
+      typescript: 6.0.3
+    transitivePeerDependencies:
+      - supports-color
 
-  faye-websocket@0.11.4:
+  '@shikijs/types@3.23.0':
     dependencies:
-      websocket-driver: 0.7.5
+      '@shikijs/vscode-textmate': 10.0.2
+      '@types/hast': 3.0.5
 
-  fdir@6.5.0(picomatch@4.0.4):
-    optionalDependencies:
-      picomatch: 4.0.4
+  '@shikijs/vscode-textmate@10.0.2': {}
 
-  feed@4.2.2:
+  '@shuding/opentype.js@1.4.0-beta.0':
     dependencies:
-      xml-js: 1.6.11
+      fflate: 0.7.5
+      string.prototype.codepointat: 0.2.1
+
+  '@sindresorhus/is@5.6.0': {}
 
-  file-entry-cache@8.0.0:
+  '@sindresorhus/slugify@2.2.0':
     dependencies:
-      flat-cache: 4.0.1
+      '@sindresorhus/transliterate': 1.6.0
+      escape-string-regexp: 5.0.0
 
-  file-loader@6.2.0(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)):
+  '@sindresorhus/transliterate@1.6.0':
     dependencies:
-      loader-utils: 2.0.4
-      schema-utils: 3.3.0
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
+      escape-string-regexp: 5.0.0
 
-  file-saver@2.0.5: {}
+  '@socket.io/component-emitter@3.1.2': {}
 
-  file-type@3.9.0: {}
+  '@stellar/prettier-config@1.2.0(prettier@3.9.4)':
+    dependencies:
+      prettier: 3.9.4
 
-  fill-range@7.1.1:
+  '@stoplight/better-ajv-errors@1.0.3(ajv@8.20.0)':
     dependencies:
-      to-regex-range: 5.0.1
+      ajv: 8.20.0
+      jsonpointer: 5.0.1
+      leven: 3.1.0
 
-  finalhandler@1.3.2:
+  '@stoplight/json-ref-readers@1.2.2':
     dependencies:
-      debug: 2.6.9
-      encodeurl: 2.0.0
-      escape-html: 1.0.3
-      on-finished: 2.4.1
-      parseurl: 1.3.3
-      statuses: 2.0.2
-      unpipe: 1.0.0
+      node-fetch: 2.7.0
+      tslib: 1.14.1
     transitivePeerDependencies:
-      - supports-color
+      - encoding
 
-  find-cache-dir@4.0.0:
+  '@stoplight/json-ref-resolver@3.1.6':
     dependencies:
-      common-path-prefix: 3.0.0
-      pkg-dir: 7.0.0
+      '@stoplight/json': 3.21.0
+      '@stoplight/path': 1.3.2
+      '@stoplight/types': 13.20.0
+      '@types/urijs': 1.19.26
+      dependency-graph: 0.11.0
+      fast-memoize: 2.5.2
+      immer: 9.0.21
+      lodash: 4.18.1
+      tslib: 2.8.1
+      urijs: 1.19.11
 
-  find-up@5.0.0:
+  '@stoplight/json@3.21.0':
     dependencies:
-      locate-path: 6.0.0
-      path-exists: 4.0.0
+      '@stoplight/ordered-object-literal': 1.0.5
+      '@stoplight/path': 1.3.2
+      '@stoplight/types': 13.20.0
+      jsonc-parser: 2.2.1
+      lodash: 4.18.1
+      safe-stable-stringify: 1.1.1
 
-  find-up@6.3.0:
-    dependencies:
-      locate-path: 7.2.0
-      path-exists: 5.0.0
+  '@stoplight/ordered-object-literal@1.0.5': {}
+
+  '@stoplight/path@1.3.2': {}
 
-  flat-cache@4.0.1:
+  '@stoplight/spectral-core@1.24.0':
     dependencies:
-      flatted: 3.4.2
-      keyv: 4.5.4
+      '@scarf/scarf': 1.4.0
+      '@stoplight/better-ajv-errors': 1.0.3(ajv@8.20.0)
+      '@stoplight/json': 3.21.0
+      '@stoplight/path': 1.3.2
+      '@stoplight/spectral-parsers': 1.0.5
+      '@stoplight/spectral-ref-resolver': 1.0.5
+      '@stoplight/spectral-runtime': 1.1.6
+      '@stoplight/types': 13.6.0
+      '@types/es-aggregate-error': 1.0.6
+      '@types/json-schema': 7.0.15
+      ajv: 8.20.0
+      ajv-errors: 3.0.0(ajv@8.20.0)
+      ajv-formats: 2.1.1(ajv@8.20.0)
+      es-aggregate-error: 1.0.14
+      expr-eval-fork: 3.0.3
+      jsonpath-plus: 10.4.0
+      lodash: 4.18.1
+      lodash.topath: 4.5.2
+      minimatch: 3.1.5
+      nimma: 0.2.3
+      pony-cause: 1.1.1
+      tslib: 2.8.1
+    transitivePeerDependencies:
+      - encoding
 
-  flat@5.0.2: {}
+  '@stoplight/spectral-formats@1.9.0':
+    dependencies:
+      '@scarf/scarf': 1.4.0
+      '@stoplight/json': 3.21.0
+      '@stoplight/spectral-core': 1.24.0
+      '@types/json-schema': 7.0.15
+      tslib: 2.8.1
+    transitivePeerDependencies:
+      - encoding
 
-  flatted@3.4.2: {}
+  '@stoplight/spectral-functions@1.11.0':
+    dependencies:
+      '@scarf/scarf': 1.4.0
+      '@stoplight/better-ajv-errors': 1.0.3(ajv@8.20.0)
+      '@stoplight/json': 3.21.0
+      '@stoplight/spectral-core': 1.24.0
+      '@stoplight/spectral-formats': 1.9.0
+      '@stoplight/spectral-runtime': 1.1.6
+      ajv: 8.20.0
+      ajv-draft-04: 1.0.0(ajv@8.20.0)
+      ajv-errors: 3.0.0(ajv@8.20.0)
+      ajv-formats: 2.1.1(ajv@8.20.0)
+      lodash: 4.18.1
+      tslib: 2.8.1
+    transitivePeerDependencies:
+      - encoding
 
-  fnv-plus@1.3.1: {}
+  '@stoplight/spectral-parsers@1.0.5':
+    dependencies:
+      '@stoplight/json': 3.21.0
+      '@stoplight/types': 14.1.1
+      '@stoplight/yaml': 4.3.0
+      tslib: 2.8.1
 
-  follow-redirects@1.16.0: {}
+  '@stoplight/spectral-ref-resolver@1.0.5':
+    dependencies:
+      '@stoplight/json-ref-readers': 1.2.2
+      '@stoplight/json-ref-resolver': 3.1.6
+      '@stoplight/spectral-runtime': 1.1.6
+      dependency-graph: 0.11.0
+      tslib: 2.8.1
+    transitivePeerDependencies:
+      - encoding
 
-  foreach@2.0.6: {}
+  '@stoplight/spectral-runtime@1.1.6':
+    dependencies:
+      '@stoplight/json': 3.21.0
+      '@stoplight/path': 1.3.2
+      '@stoplight/types': 13.20.0
+      lodash: 4.18.1
+      node-fetch: 2.7.0
+      tslib: 2.8.1
+    transitivePeerDependencies:
+      - encoding
 
-  form-data-encoder@2.1.4: {}
+  '@stoplight/types@13.20.0':
+    dependencies:
+      '@types/json-schema': 7.0.15
+      utility-types: 3.11.0
 
-  format@0.2.2: {}
+  '@stoplight/types@13.6.0':
+    dependencies:
+      '@types/json-schema': 7.0.15
+      utility-types: 3.11.0
 
-  forwarded@0.2.0: {}
+  '@stoplight/types@14.1.1':
+    dependencies:
+      '@types/json-schema': 7.0.15
+      utility-types: 3.11.0
 
-  fraction.js@5.3.4: {}
+  '@stoplight/yaml-ast-parser@0.0.50': {}
 
-  fresh@0.5.2: {}
+  '@stoplight/yaml@4.3.0':
+    dependencies:
+      '@stoplight/ordered-object-literal': 1.0.5
+      '@stoplight/types': 14.1.1
+      '@stoplight/yaml-ast-parser': 0.0.50
+      tslib: 2.8.1
 
-  fs-extra@10.1.0:
+  '@szmarczak/http-timer@5.0.1':
     dependencies:
-      graceful-fs: 4.2.11
-      jsonfile: 6.2.1
-      universalify: 2.0.1
+      defer-to-connect: 2.0.1
 
-  fs-extra@11.3.6:
+  '@types/cors@2.8.19':
     dependencies:
-      graceful-fs: 4.2.11
-      jsonfile: 6.2.1
-      universalify: 2.0.1
+      '@types/node': 26.6.5
 
-  fs.realpath@1.0.0: {}
+  '@types/debug@4.1.13':
+    dependencies:
+      '@types/ms': 2.1.0
 
-  fsevents@2.3.3:
-    optional: true
+  '@types/es-aggregate-error@1.0.6':
+    dependencies:
+      '@types/node': 26.6.5
 
-  function-bind@1.1.2: {}
+  '@types/estree-jsx@1.0.5':
+    dependencies:
+      '@types/estree': 1.0.9
 
-  gensync@1.0.0-beta.2: {}
+  '@types/estree@1.0.9': {}
 
-  get-caller-file@2.0.5: {}
+  '@types/hast@3.0.5':
+    dependencies:
+      '@types/unist': 3.0.3
 
-  get-east-asian-width@1.6.0: {}
+  '@types/http-cache-semantics@4.2.0': {}
 
-  get-intrinsic@1.3.0:
-    dependencies:
-      call-bind-apply-helpers: 1.0.2
-      es-define-property: 1.0.1
-      es-errors: 1.3.0
-      es-object-atoms: 1.1.2
-      function-bind: 1.1.2
-      get-proto: 1.0.1
-      gopd: 1.2.0
-      has-symbols: 1.1.0
-      hasown: 2.0.4
-      math-intrinsics: 1.1.0
+  '@types/json-schema@7.0.15': {}
 
-  get-own-enumerable-property-symbols@3.0.2: {}
+  '@types/katex@0.16.8': {}
 
-  get-proto@1.0.1:
+  '@types/mdast@4.0.4':
     dependencies:
-      dunder-proto: 1.0.1
-      es-object-atoms: 1.1.2
+      '@types/unist': 3.0.3
 
-  get-stream@6.0.1: {}
+  '@types/mdx@2.0.14': {}
 
-  github-slugger@1.5.0: {}
+  '@types/ms@2.1.0': {}
 
-  glob-parent@5.1.2:
+  '@types/nlcst@2.0.3':
     dependencies:
-      is-glob: 4.0.3
+      '@types/unist': 3.0.3
 
-  glob-parent@6.0.2:
+  '@types/node@26.6.5':
     dependencies:
-      is-glob: 4.0.3
+      undici-types: 8.9.0
 
-  glob-to-regex.js@1.2.0(tslib@2.8.1):
+  '@types/react@19.3.0':
     dependencies:
-      tslib: 2.8.1
+      csstype: 3.2.3
 
-  glob-to-regexp@0.4.1: {}
+  '@types/unist@2.0.11': {}
 
-  glob@13.0.6:
-    dependencies:
-      minimatch: 10.2.5
-      minipass: 7.1.3
-      path-scurry: 2.0.2
+  '@types/unist@3.0.3': {}
 
-  glob@7.2.3:
+  '@types/urijs@1.19.26': {}
+
+  '@types/ws@8.18.2':
     dependencies:
-      fs.realpath: 1.0.0
-      inflight: 1.0.6
-      inherits: 2.0.4
-      minimatch: 3.1.5
-      once: 1.4.0
-      path-is-absolute: 1.0.1
+      '@types/node': 26.6.5
 
-  global-dirs@3.0.1:
+  '@typescript/vfs@1.6.5(typescript@6.0.3)':
     dependencies:
-      ini: 2.0.0
+      debug: 4.4.3
+      typescript: 6.0.3
+    transitivePeerDependencies:
+      - supports-color
 
-  globals@14.0.0: {}
+  '@ungap/structured-clone@1.4.0': {}
 
-  globby@11.1.0:
+  accepts@1.3.8:
     dependencies:
-      array-union: 2.1.0
-      dir-glob: 3.0.1
-      fast-glob: 3.3.3
-      ignore: 5.3.2
-      merge2: 1.4.1
-      slash: 3.0.0
+      mime-types: 2.1.35
+      negotiator: 0.6.3
 
-  globby@13.2.2:
+  acorn-jsx@5.3.2(acorn@8.11.2):
     dependencies:
-      dir-glob: 3.0.1
-      fast-glob: 3.3.3
-      ignore: 5.3.2
-      merge2: 1.4.1
-      slash: 4.0.0
+      acorn: 8.11.2
 
-  gopd@1.2.0: {}
+  acorn@8.11.2: {}
 
-  got@12.6.1:
+  address@1.2.2: {}
+
+  adm-zip@0.6.0: {}
+
+  agent-base@6.0.2:
     dependencies:
-      '@sindresorhus/is': 5.6.0
-      '@szmarczak/http-timer': 5.0.1
-      cacheable-lookup: 7.0.0
-      cacheable-request: 10.2.14
-      decompress-response: 6.0.0
-      form-data-encoder: 2.1.4
-      get-stream: 6.0.1
-      http2-wrapper: 2.2.1
-      lowercase-keys: 3.0.0
-      p-cancelable: 3.0.0
-      responselike: 3.0.0
+      debug: 4.4.3
+    transitivePeerDependencies:
+      - supports-color
+
+  aggregate-error@4.0.1:
+    dependencies:
+      clean-stack: 4.2.0
+      indent-string: 5.0.0
+
+  ajv-draft-04@1.0.0(ajv@8.20.0):
+    optionalDependencies:
+      ajv: 8.20.0
 
-  graceful-fs@4.2.10: {}
+  ajv-errors@3.0.0(ajv@8.20.0):
+    dependencies:
+      ajv: 8.20.0
 
-  graceful-fs@4.2.11: {}
+  ajv-formats@2.1.1(ajv@8.20.0):
+    optionalDependencies:
+      ajv: 8.20.0
 
-  graphemer@1.4.0: {}
+  ajv-formats@3.0.1(ajv@8.20.0):
+    optionalDependencies:
+      ajv: 8.20.0
 
-  graphlib@2.1.8:
+  ajv@6.15.0:
     dependencies:
-      lodash: 4.18.1
+      fast-deep-equal: 3.1.3
+      fast-json-stable-stringify: 2.1.0
+      json-schema-traverse: 0.4.1
+      uri-js: 4.4.1
 
-  gray-matter@4.0.3:
+  ajv@8.20.0:
     dependencies:
-      js-yaml: 3.15.1
-      kind-of: 6.0.3
-      section-matter: 1.0.0
-      strip-bom-string: 1.0.0
+      fast-deep-equal: 3.1.3
+      fast-uri: 3.1.8
+      json-schema-traverse: 1.0.0
+      require-from-string: 2.0.2
 
-  gzip-size@6.0.0:
+  ansi-escapes@4.3.2:
     dependencies:
-      duplexer: 0.1.2
+      type-fest: 0.21.3
 
-  hachure-fill@0.5.2: {}
+  ansi-escapes@7.3.0:
+    dependencies:
+      environment: 1.1.0
 
-  handle-thing@2.0.1: {}
+  ansi-regex@5.0.1: {}
 
-  has-flag@4.0.0: {}
+  ansi-regex@6.2.2: {}
 
-  has-property-descriptors@1.0.2:
+  ansi-styles@4.3.0:
     dependencies:
-      es-define-property: 1.0.1
-
-  has-symbols@1.1.0: {}
+      color-convert: 2.0.1
 
-  has-yarn@3.0.0: {}
+  ansi-styles@6.2.3: {}
 
-  hash-color-material@1.1.3: {}
+  any-promise@1.3.0: {}
 
-  hasown@2.0.4:
+  anymatch@3.1.3:
     dependencies:
-      function-bind: 1.1.2
+      normalize-path: 3.0.0
+      picomatch: 2.3.2
 
-  hast-to-hyperscript@10.0.3:
-    dependencies:
-      '@types/unist': 2.0.11
-      comma-separated-tokens: 2.0.3
-      property-information: 6.5.0
-      space-separated-tokens: 2.0.2
-      style-to-object: 0.4.4
-      web-namespaces: 2.0.1
+  anynum@1.0.1: {}
 
-  hast-util-from-dom@5.0.1:
-    dependencies:
-      '@types/hast': 3.0.4
-      hastscript: 9.0.1
-      web-namespaces: 2.0.1
+  arg@5.0.2: {}
 
-  hast-util-from-html-isomorphic@2.0.0:
+  argparse@1.0.10:
     dependencies:
-      '@types/hast': 3.0.4
-      hast-util-from-dom: 5.0.1
-      hast-util-from-html: 2.0.3
-      unist-util-remove-position: 5.0.0
+      sprintf-js: 1.0.3
 
-  hast-util-from-html@2.0.3:
-    dependencies:
-      '@types/hast': 3.0.4
-      devlop: 1.1.0
-      hast-util-from-parse5: 8.0.3
-      parse5: 7.3.0
-      vfile: 6.0.3
-      vfile-message: 4.0.3
+  argparse@2.0.1: {}
 
-  hast-util-from-parse5@7.1.2:
+  arkregex@0.0.13:
     dependencies:
-      '@types/hast': 2.3.10
-      '@types/unist': 2.0.11
-      hastscript: 7.2.0
-      property-information: 6.5.0
-      vfile: 5.3.7
-      vfile-location: 4.1.0
-      web-namespaces: 2.0.1
+      '@ark/util': 0.56.7
 
-  hast-util-from-parse5@8.0.3:
+  arktype@2.2.8:
     dependencies:
-      '@types/hast': 3.0.4
-      '@types/unist': 3.0.3
-      devlop: 1.1.0
-      hastscript: 9.0.1
-      property-information: 7.2.0
-      vfile: 6.0.3
-      vfile-location: 5.0.3
-      web-namespaces: 2.0.1
+      '@ark/schema': 0.56.7
+      '@ark/util': 0.56.7
+      arkregex: 0.0.13
 
-  hast-util-is-element@3.0.0:
+  array-buffer-byte-length@1.0.2:
     dependencies:
-      '@types/hast': 3.0.4
+      call-bound: 1.0.4
+      is-array-buffer: 3.0.5
 
-  hast-util-parse-selector@2.2.5: {}
+  array-flatten@1.1.1: {}
 
-  hast-util-parse-selector@3.1.1:
-    dependencies:
-      '@types/hast': 2.3.10
+  array-iterate@2.0.1: {}
 
-  hast-util-parse-selector@4.0.0:
+  arraybuffer.prototype.slice@1.0.4:
     dependencies:
-      '@types/hast': 3.0.4
+      array-buffer-byte-length: 1.0.2
+      call-bind: 1.0.9
+      define-properties: 1.2.1
+      es-abstract: 1.24.2
+      es-errors: 1.3.0
+      get-intrinsic: 1.3.0
+      is-array-buffer: 3.0.5
 
-  hast-util-raw@7.0.0:
-    dependencies:
-      '@types/hast': 2.3.10
-      '@types/parse5': 6.0.3
-      '@types/unist': 2.0.11
-      hast-util-from-parse5: 7.1.2
-      hast-util-to-parse5: 7.1.0
-      html-void-elements: 2.0.1
-      parse5: 6.0.1
-      unist-util-position: 4.0.4
-      unist-util-visit: 3.1.0
-      vfile: 4.2.1
-      web-namespaces: 2.0.1
-      zwitch: 2.0.4
+  astring@1.9.0: {}
 
-  hast-util-raw@9.1.0:
-    dependencies:
-      '@types/hast': 3.0.4
-      '@types/unist': 3.0.3
-      '@ungap/structured-clone': 1.3.2
-      hast-util-from-parse5: 8.0.3
-      hast-util-to-parse5: 8.0.1
-      html-void-elements: 3.0.0
-      mdast-util-to-hast: 13.2.1
-      parse5: 7.3.0
-      unist-util-position: 5.0.0
-      unist-util-visit: 5.1.0
-      vfile: 6.0.3
-      web-namespaces: 2.0.1
-      zwitch: 2.0.4
+  async-function@1.0.0: {}
 
-  hast-util-sanitize@4.1.0:
-    dependencies:
-      '@types/hast': 2.3.10
+  asynckit@0.4.0: {}
+
+  auto-bind@5.0.1: {}
 
-  hast-util-to-estree@3.1.3:
+  available-typed-arrays@1.0.7:
     dependencies:
-      '@types/estree': 1.0.9
-      '@types/estree-jsx': 1.0.5
-      '@types/hast': 3.0.4
-      comma-separated-tokens: 2.0.3
-      devlop: 1.1.0
-      estree-util-attach-comments: 3.0.0
-      estree-util-is-identifier-name: 3.0.0
-      hast-util-whitespace: 3.0.0
-      mdast-util-mdx-expression: 2.0.1
-      mdast-util-mdx-jsx: 3.2.0
-      mdast-util-mdxjs-esm: 2.0.1
-      property-information: 7.2.0
-      space-separated-tokens: 2.0.2
-      style-to-js: 1.1.21
-      unist-util-position: 5.0.0
-      zwitch: 2.0.4
-    transitivePeerDependencies:
-      - supports-color
+      possible-typed-array-names: 1.1.0
 
-  hast-util-to-jsx-runtime@2.3.6:
+  avsc@5.7.9: {}
+
+  axios@1.18.0:
     dependencies:
-      '@types/estree': 1.0.9
-      '@types/hast': 3.0.4
-      '@types/unist': 3.0.3
-      comma-separated-tokens: 2.0.3
-      devlop: 1.1.0
-      estree-util-is-identifier-name: 3.0.0
-      hast-util-whitespace: 3.0.0
-      mdast-util-mdx-expression: 2.0.1
-      mdast-util-mdx-jsx: 3.2.0
-      mdast-util-mdxjs-esm: 2.0.1
-      property-information: 7.2.0
-      space-separated-tokens: 2.0.2
-      style-to-js: 1.1.21
-      unist-util-position: 5.0.0
-      vfile-message: 4.0.3
+      follow-redirects: 1.16.1
+      form-data: 4.0.6
+      https-proxy-agent: 5.0.1
+      proxy-from-env: 2.1.0
     transitivePeerDependencies:
+      - debug
       - supports-color
 
-  hast-util-to-parse5@7.1.0:
-    dependencies:
-      '@types/hast': 2.3.10
-      comma-separated-tokens: 2.0.3
-      property-information: 6.5.0
-      space-separated-tokens: 2.0.2
-      web-namespaces: 2.0.1
-      zwitch: 2.0.4
+  bail@2.0.2: {}
 
-  hast-util-to-parse5@8.0.1:
-    dependencies:
-      '@types/hast': 3.0.4
-      comma-separated-tokens: 2.0.3
-      devlop: 1.1.0
-      property-information: 7.2.0
-      space-separated-tokens: 2.0.2
-      web-namespaces: 2.0.1
-      zwitch: 2.0.4
+  balanced-match@1.0.2: {}
 
-  hast-util-to-text@4.0.2:
+  base64-js@0.0.8: {}
+
+  base64-js@1.5.1:
+    optional: true
+
+  base64id@2.0.0: {}
+
+  better-opn@3.0.2:
     dependencies:
-      '@types/hast': 3.0.4
-      '@types/unist': 3.0.3
-      hast-util-is-element: 3.0.0
-      unist-util-find-after: 5.0.0
+      open: 8.4.2
 
-  hast-util-whitespace@2.0.1: {}
+  binary-extensions@2.3.0: {}
 
-  hast-util-whitespace@3.0.0:
+  bl@4.1.0:
     dependencies:
-      '@types/hast': 3.0.4
+      buffer: 5.7.1
+      inherits: 2.0.4
+      readable-stream: 3.6.2
+    optional: true
 
-  hastscript@6.0.0:
+  body-parser@1.20.8:
     dependencies:
-      '@types/hast': 2.3.10
-      comma-separated-tokens: 1.0.8
-      hast-util-parse-selector: 2.2.5
-      property-information: 5.6.0
-      space-separated-tokens: 1.1.5
+      bytes: 3.1.2
+      content-type: 1.0.5
+      debug: 2.6.9
+      depd: 2.0.0
+      destroy: 1.2.0
+      http-errors: 2.0.1
+      iconv-lite: 0.4.24
+      on-finished: 2.4.1
+      qs: 6.16.1
+      raw-body: 2.5.3
+      type-is: 1.6.18
+      unpipe: 1.0.0
+    transitivePeerDependencies:
+      - supports-color
 
-  hastscript@7.2.0:
+  brace-expansion@1.1.21:
     dependencies:
-      '@types/hast': 2.3.10
-      comma-separated-tokens: 2.0.3
-      hast-util-parse-selector: 3.1.1
-      property-information: 6.5.0
-      space-separated-tokens: 2.0.2
+      balanced-match: 1.0.2
+      concat-map: 0.0.1
 
-  hastscript@9.0.1:
+  braces@3.0.3:
     dependencies:
-      '@types/hast': 3.0.4
-      comma-separated-tokens: 2.0.3
-      hast-util-parse-selector: 4.0.0
-      property-information: 7.2.0
-      space-separated-tokens: 2.0.2
+      fill-range: 7.1.1
 
-  he@1.2.0: {}
+  buffer@5.7.1:
+    dependencies:
+      base64-js: 1.5.1
+      ieee754: 1.2.1
+    optional: true
 
-  highlight.js@10.7.3: {}
+  bytes@3.1.2: {}
 
-  highlightjs-vue@1.0.0: {}
+  cacheable-lookup@7.0.0: {}
 
-  history@4.10.1:
+  cacheable-request@10.2.14:
     dependencies:
-      '@babel/runtime': 7.29.7
-      loose-envify: 1.4.0
-      resolve-pathname: 3.0.0
-      tiny-invariant: 1.3.3
-      tiny-warning: 1.0.3
-      value-equal: 1.0.1
+      '@types/http-cache-semantics': 4.2.0
+      get-stream: 6.0.1
+      http-cache-semantics: 4.3.0
+      keyv: 4.5.4
+      mimic-response: 4.0.0
+      normalize-url: 8.1.1
+      responselike: 3.0.0
 
-  hoist-non-react-statics@3.3.2:
+  call-bind-apply-helpers@1.0.2:
     dependencies:
-      react-is: 16.13.1
+      es-errors: 1.3.0
+      function-bind: 1.1.2
 
-  hpack.js@2.1.6:
+  call-bind@1.0.9:
     dependencies:
-      inherits: 2.0.4
-      obuf: 1.1.2
-      readable-stream: 2.3.8
-      wbuf: 1.7.3
-
-  html-escaper@2.0.2: {}
+      call-bind-apply-helpers: 1.0.2
+      es-define-property: 1.0.1
+      get-intrinsic: 1.3.0
+      set-function-length: 1.2.2
 
-  html-minifier-terser@6.1.0:
+  call-bound@1.0.4:
     dependencies:
-      camel-case: 4.1.2
-      clean-css: 5.3.3
-      commander: 8.3.0
-      he: 1.2.0
-      param-case: 3.0.4
-      relateurl: 0.2.7
-      terser: 5.48.0
+      call-bind-apply-helpers: 1.0.2
+      get-intrinsic: 1.3.0
 
-  html-minifier-terser@7.2.0:
-    dependencies:
-      camel-case: 4.1.2
-      clean-css: 5.3.3
-      commander: 10.0.1
-      entities: 4.5.0
-      param-case: 3.0.4
-      relateurl: 0.2.7
-      terser: 5.48.0
+  camelcase-css@2.0.1: {}
 
-  html-tags@3.3.1: {}
+  camelize@1.0.1: {}
 
-  html-url-attributes@3.0.1: {}
+  ccount@2.0.1: {}
 
-  html-void-elements@2.0.1: {}
+  chalk@5.2.0: {}
 
-  html-void-elements@3.0.0: {}
+  chalk@5.3.0: {}
 
-  html-webpack-plugin@5.6.7(@rspack/core@1.7.11(@swc/helpers@0.5.23))(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)):
-    dependencies:
-      '@types/html-minifier-terser': 6.1.0
-      html-minifier-terser: 6.1.0
-      lodash: 4.18.1
-      pretty-error: 4.0.0
-      tapable: 2.3.3
-    optionalDependencies:
-      '@rspack/core': 1.7.11(@swc/helpers@0.5.23)
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
+  chalk@5.6.2: {}
 
-  htmlparser2@6.1.0:
-    dependencies:
-      domelementtype: 2.3.0
-      domhandler: 4.3.1
-      domutils: 2.8.0
-      entities: 2.2.0
+  character-entities-html4@2.1.0: {}
 
-  htmlparser2@8.0.2:
-    dependencies:
-      domelementtype: 2.3.0
-      domhandler: 5.0.3
-      domutils: 3.2.2
-      entities: 4.5.0
+  character-entities-legacy@3.0.0: {}
+
+  character-entities@2.0.2: {}
 
-  http-cache-semantics@4.2.0: {}
+  character-reference-invalid@2.0.1: {}
 
-  http-deceiver@1.2.7: {}
+  chardet@2.2.0: {}
 
-  http-errors@1.8.1:
+  chokidar@3.5.3:
     dependencies:
-      depd: 1.1.2
-      inherits: 2.0.4
-      setprototypeof: 1.2.0
-      statuses: 1.5.0
-      toidentifier: 1.0.1
+      anymatch: 3.1.3
+      braces: 3.0.3
+      glob-parent: 5.1.2
+      is-binary-path: 2.1.0
+      is-glob: 4.0.3
+      normalize-path: 3.0.0
+      readdirp: 3.6.0
+    optionalDependencies:
+      fsevents: 2.3.3
 
-  http-errors@2.0.1:
+  chokidar@3.6.0:
     dependencies:
-      depd: 2.0.0
-      inherits: 2.0.4
-      setprototypeof: 1.2.0
-      statuses: 2.0.2
-      toidentifier: 1.0.1
+      anymatch: 3.1.3
+      braces: 3.0.3
+      glob-parent: 5.1.2
+      is-binary-path: 2.1.0
+      is-glob: 4.0.3
+      normalize-path: 3.0.0
+      readdirp: 3.6.0
+    optionalDependencies:
+      fsevents: 2.3.3
+
+  chownr@1.1.4:
+    optional: true
+
+  chownr@3.0.0: {}
+
+  clean-stack@4.2.0:
+    dependencies:
+      escape-string-regexp: 5.0.0
 
-  http-parser-js@0.5.10: {}
+  cli-boxes@3.0.0: {}
 
-  http-proxy-middleware@2.0.9(@types/express@4.17.25):
+  cli-cursor@4.0.0:
     dependencies:
-      '@types/http-proxy': 1.17.17
-      http-proxy: 1.18.1
-      is-glob: 4.0.3
-      is-plain-obj: 3.0.0
-      micromatch: 4.0.8
-    optionalDependencies:
-      '@types/express': 4.17.25
-    transitivePeerDependencies:
-      - debug
+      restore-cursor: 4.0.0
 
-  http-proxy@1.18.1:
+  cli-spinners@2.9.2: {}
+
+  cli-truncate@4.0.0:
     dependencies:
-      eventemitter3: 4.0.7
-      follow-redirects: 1.16.0
-      requires-port: 1.0.0
-    transitivePeerDependencies:
-      - debug
+      slice-ansi: 5.0.0
+      string-width: 7.2.0
 
-  http-reasons@0.1.0: {}
+  cli-width@4.1.0: {}
 
-  http2-client@1.3.5: {}
+  cliui@8.0.1:
+    dependencies:
+      string-width: 4.2.3
+      strip-ansi: 6.0.1
+      wrap-ansi: 7.0.0
 
-  http2-wrapper@2.2.1:
+  cliui@9.0.1:
     dependencies:
-      quick-lru: 5.1.1
-      resolve-alpn: 1.2.1
+      string-width: 7.2.0
+      strip-ansi: 7.2.0
+      wrap-ansi: 9.0.2
 
-  human-signals@2.1.0: {}
+  code-excerpt@4.0.0:
+    dependencies:
+      convert-to-spaces: 2.0.1
 
-  husky@9.1.7: {}
+  collapse-white-space@2.1.0: {}
 
-  hyperdyperid@1.2.0: {}
+  color-convert@2.0.1:
+    dependencies:
+      color-name: 1.1.4
 
-  hyphenate-style-name@1.1.0: {}
+  color-name@1.1.4: {}
 
-  iconv-lite@0.4.24:
+  color-string@1.9.1:
     dependencies:
-      safer-buffer: 2.1.2
+      color-name: 1.1.4
+      simple-swizzle: 0.2.4
 
-  iconv-lite@0.6.3:
+  color@4.2.3:
     dependencies:
-      safer-buffer: 2.1.2
+      color-convert: 2.0.1
+      color-string: 1.9.1
 
-  icss-utils@5.1.0(postcss@8.5.15):
+  combined-stream@1.0.8:
     dependencies:
-      postcss: 8.5.15
+      delayed-stream: 1.0.0
 
-  ieee754@1.2.1: {}
-
-  ignore@5.3.2: {}
+  comma-separated-tokens@2.0.3: {}
 
-  image-size@2.0.2: {}
+  commander@2.20.3: {}
 
-  immer@11.1.9: {}
+  commander@4.1.1: {}
 
-  immutable@5.1.6: {}
+  commander@8.3.0: {}
 
-  import-fresh@3.3.1:
+  compute-gcd@1.2.1:
     dependencies:
-      parent-module: 1.0.1
-      resolve-from: 4.0.0
-
-  import-lazy@4.0.0: {}
-
-  import-meta-resolve@4.2.0: {}
-
-  imurmurhash@0.1.4: {}
+      validate.io-array: 1.0.6
+      validate.io-function: 1.0.2
+      validate.io-integer-array: 1.0.0
 
-  indent-string@4.0.0: {}
+  compute-lcm@1.1.2:
+    dependencies:
+      compute-gcd: 1.2.1
+      validate.io-array: 1.0.6
+      validate.io-function: 1.0.2
+      validate.io-integer-array: 1.0.0
 
-  infima@0.2.0-alpha.45: {}
+  concat-map@0.0.1: {}
 
-  inflight@1.0.6:
+  content-disposition@0.5.4:
     dependencies:
-      once: 1.4.0
-      wrappy: 1.0.2
+      safe-buffer: 5.2.1
 
-  inherits@2.0.4: {}
+  content-type@1.0.5: {}
 
-  ini@1.3.8: {}
+  convert-to-spaces@2.0.1: {}
 
-  ini@2.0.0: {}
+  cookie-signature@1.0.7: {}
 
-  inline-style-parser@0.1.1: {}
+  cookie@0.7.2: {}
 
-  inline-style-parser@0.2.7: {}
+  cors@2.8.6:
+    dependencies:
+      object-assign: 4.1.1
+      vary: 1.1.2
 
-  inline-style-prefixer@7.0.1:
+  cross-spawn@7.0.6:
     dependencies:
-      css-in-js-utils: 3.1.0
+      path-key: 3.1.1
+      shebang-command: 2.0.0
+      which: 2.0.2
 
-  internmap@1.0.1: {}
+  css-background-parser@0.1.0: {}
 
-  internmap@2.0.3: {}
+  css-box-shadow@1.0.0-3: {}
 
-  interpret@1.4.0: {}
+  css-color-keywords@1.0.0: {}
 
-  invariant@2.2.4:
-    dependencies:
-      loose-envify: 1.4.0
+  css-gradient-parser@0.0.17: {}
 
-  ipaddr.js@1.9.1: {}
+  css-to-react-native@3.2.0:
+    dependencies:
+      camelize: 1.0.1
+      css-color-keywords: 1.0.0
+      postcss-value-parser: 4.2.0
 
-  ipaddr.js@2.4.0: {}
+  cssesc@3.0.0: {}
 
-  is-alphabetical@1.0.4: {}
+  cssfilter@0.0.10: {}
 
-  is-alphabetical@2.0.1: {}
+  csstype@3.2.3: {}
 
-  is-alphanumerical@1.0.4:
+  data-view-buffer@1.0.2:
     dependencies:
-      is-alphabetical: 1.0.4
-      is-decimal: 1.0.4
+      call-bound: 1.0.4
+      es-errors: 1.3.0
+      is-data-view: 1.0.2
 
-  is-alphanumerical@2.0.1:
+  data-view-byte-length@1.0.2:
     dependencies:
-      is-alphabetical: 2.0.1
-      is-decimal: 2.0.1
-
-  is-arrayish@0.2.1: {}
+      call-bound: 1.0.4
+      es-errors: 1.3.0
+      is-data-view: 1.0.2
 
-  is-binary-path@2.1.0:
+  data-view-byte-offset@1.0.1:
     dependencies:
-      binary-extensions: 2.3.0
-
-  is-buffer@2.0.5: {}
+      call-bound: 1.0.4
+      es-errors: 1.3.0
+      is-data-view: 1.0.2
 
-  is-ci@3.0.1:
+  debug@2.6.9:
     dependencies:
-      ci-info: 3.9.0
+      ms: 2.0.0
 
-  is-core-module@2.16.2:
+  debug@4.3.7:
     dependencies:
-      hasown: 2.0.4
-
-  is-decimal@1.0.4: {}
-
-  is-decimal@2.0.1: {}
-
-  is-docker@2.2.1: {}
-
-  is-docker@3.0.0: {}
+      ms: 2.1.3
 
-  is-extendable@0.1.1: {}
+  debug@4.4.3:
+    dependencies:
+      ms: 2.1.3
 
-  is-extglob@2.1.1: {}
+  decode-bmp@0.2.1:
+    dependencies:
+      '@canvas/image-data': 1.1.0
+      to-data-view: 1.1.0
 
-  is-fullwidth-code-point@3.0.0: {}
+  decode-ico@0.4.1:
+    dependencies:
+      '@canvas/image-data': 1.1.0
+      decode-bmp: 0.2.1
+      to-data-view: 1.1.0
 
-  is-glob@4.0.3:
+  decode-named-character-reference@1.3.0:
     dependencies:
-      is-extglob: 2.1.1
+      character-entities: 2.0.2
 
-  is-hexadecimal@1.0.4: {}
+  decompress-response@6.0.0:
+    dependencies:
+      mimic-response: 3.1.0
 
-  is-hexadecimal@2.0.1: {}
+  deep-extend@0.6.0:
+    optional: true
 
-  is-inside-container@1.0.0:
-    dependencies:
-      is-docker: 3.0.0
+  defer-to-connect@2.0.1: {}
 
-  is-installed-globally@0.4.0:
+  define-data-property@1.1.4:
     dependencies:
-      global-dirs: 3.0.1
-      is-path-inside: 3.0.3
+      es-define-property: 1.0.1
+      es-errors: 1.3.0
+      gopd: 1.2.0
 
-  is-network-error@1.3.2: {}
+  define-lazy-prop@2.0.0: {}
 
-  is-npm@6.1.0: {}
+  define-properties@1.2.1:
+    dependencies:
+      define-data-property: 1.1.4
+      has-property-descriptors: 1.0.2
+      object-keys: 1.1.1
 
-  is-number@7.0.0: {}
+  delayed-stream@1.0.0: {}
 
-  is-obj@1.0.1: {}
+  depd@2.0.0: {}
 
-  is-obj@2.0.0: {}
+  dependency-graph@0.11.0: {}
 
-  is-path-inside@3.0.3: {}
+  dequal@2.0.3: {}
 
-  is-plain-obj@2.1.0: {}
+  destroy@1.2.0: {}
 
-  is-plain-obj@3.0.0: {}
+  detect-libc@2.1.2: {}
 
-  is-plain-obj@4.1.0: {}
+  detect-node@2.1.0: {}
 
-  is-plain-object@2.0.4:
+  detect-port@1.5.1:
     dependencies:
-      isobject: 3.0.1
-
-  is-regexp@1.0.0: {}
+      address: 1.2.2
+      debug: 4.4.3
+    transitivePeerDependencies:
+      - supports-color
 
-  is-stream@2.0.1: {}
+  devlop@1.1.0:
+    dependencies:
+      dequal: 2.0.3
 
-  is-typedarray@1.0.0: {}
+  didyoumean@1.2.2: {}
 
-  is-url@1.2.4: {}
+  dlv@1.1.3: {}
 
-  is-wsl@2.2.0:
+  dns-packet@5.6.1:
     dependencies:
-      is-docker: 2.2.1
+      '@leichtgewicht/ip-codec': 2.0.5
 
-  is-wsl@3.1.1:
+  dns-socket@4.2.2:
     dependencies:
-      is-inside-container: 1.0.0
-
-  is-yarn-global@0.4.1: {}
-
-  isarray@0.0.1: {}
+      dns-packet: 5.6.1
 
-  isarray@1.0.0: {}
+  dunder-proto@1.0.1:
+    dependencies:
+      call-bind-apply-helpers: 1.0.2
+      es-errors: 1.3.0
+      gopd: 1.2.0
 
-  isexe@2.0.0: {}
+  ee-first@1.1.1: {}
 
-  isobject@3.0.1: {}
+  emoji-regex-xs@2.0.1: {}
 
-  isomorphic-fetch@3.0.0:
-    dependencies:
-      node-fetch: 2.7.0
-      whatwg-fetch: 3.6.20
-    transitivePeerDependencies:
-      - encoding
+  emoji-regex@10.6.0: {}
 
-  jest-util@29.7.0:
-    dependencies:
-      '@jest/types': 29.6.3
-      '@types/node': 25.9.2
-      chalk: 4.1.2
-      ci-info: 3.9.0
-      graceful-fs: 4.2.11
-      picomatch: 2.3.2
+  emoji-regex@8.0.0: {}
 
-  jest-worker@27.5.1:
-    dependencies:
-      '@types/node': 25.9.2
-      merge-stream: 2.0.0
-      supports-color: 8.1.1
+  encodeurl@2.0.0: {}
 
-  jest-worker@29.7.0:
+  end-of-stream@1.4.5:
     dependencies:
-      '@types/node': 25.9.2
-      jest-util: 29.7.0
-      merge-stream: 2.0.0
-      supports-color: 8.1.1
-
-  jiti@1.21.7: {}
+      once: 1.4.0
+    optional: true
 
-  joi@17.13.3:
-    dependencies:
-      '@hapi/hoek': 9.3.0
-      '@hapi/topo': 5.1.0
-      '@sideway/address': 4.1.5
-      '@sideway/formula': 3.0.1
-      '@sideway/pinpoint': 2.0.0
+  engine.io-parser@5.2.3: {}
 
-  jotai@1.13.1(@babel/core@7.29.7)(@babel/template@7.29.7)(react@19.2.7):
+  engine.io@6.6.11:
     dependencies:
-      react: 19.2.7
-    optionalDependencies:
-      '@babel/core': 7.29.7
-      '@babel/template': 7.29.7
+      '@types/cors': 2.8.19
+      '@types/node': 26.6.5
+      '@types/ws': 8.18.2
+      accepts: 1.3.8
+      cookie: 0.7.2
+      cors: 2.8.6
+      debug: 4.4.3
+      engine.io-parser: 5.2.3
+      ws: 8.21.3
+    transitivePeerDependencies:
+      - bufferutil
+      - supports-color
+      - utf-8-validate
 
-  js-cookie@2.2.1: {}
+  entities@6.0.1: {}
 
-  js-levenshtein@1.1.6: {}
+  entities@7.0.1:
+    optional: true
 
-  js-tokens@4.0.0: {}
+  environment@1.1.0: {}
 
-  js-yaml@3.15.1:
+  es-abstract-get@1.0.0:
     dependencies:
-      argparse: 1.0.10
-      esprima: 4.0.1
+      es-errors: 1.3.0
+      es-object-atoms: 1.1.2
+      is-callable: 1.2.7
+      object-inspect: 1.13.4
 
-  js-yaml@4.1.0:
+  es-abstract@1.24.2:
     dependencies:
-      argparse: 2.0.1
-
-  js-yaml@4.3.1:
+      array-buffer-byte-length: 1.0.2
+      arraybuffer.prototype.slice: 1.0.4
+      available-typed-arrays: 1.0.7
+      call-bind: 1.0.9
+      call-bound: 1.0.4
+      data-view-buffer: 1.0.2
+      data-view-byte-length: 1.0.2
+      data-view-byte-offset: 1.0.1
+      es-define-property: 1.0.1
+      es-errors: 1.3.0
+      es-object-atoms: 1.1.2
+      es-set-tostringtag: 2.1.0
+      es-to-primitive: 1.3.4
+      function.prototype.name: 1.2.0
+      get-intrinsic: 1.3.0
+      get-proto: 1.0.1
+      get-symbol-description: 1.1.0
+      globalthis: 1.0.4
+      gopd: 1.2.0
+      has-property-descriptors: 1.0.2
+      has-proto: 1.2.0
+      has-symbols: 1.1.0
+      hasown: 2.0.4
+      internal-slot: 1.1.0
+      is-array-buffer: 3.0.5
+      is-callable: 1.2.7
+      is-data-view: 1.0.2
+      is-negative-zero: 2.0.3
+      is-regex: 1.2.1
+      is-set: 2.0.3
+      is-shared-array-buffer: 1.0.4
+      is-string: 1.1.1
+      is-typed-array: 1.1.15
+      is-weakref: 1.1.1
+      math-intrinsics: 1.1.0
+      object-inspect: 1.13.4
+      object-keys: 1.1.1
+      object.assign: 4.1.7
+      own-keys: 1.0.2
+      regexp.prototype.flags: 1.5.4
+      safe-array-concat: 1.1.4
+      safe-push-apply: 1.0.0
+      safe-regex-test: 1.1.0
+      set-proto: 1.0.0
+      stop-iteration-iterator: 1.1.0
+      string.prototype.trim: 1.2.11
+      string.prototype.trimend: 1.0.10
+      string.prototype.trimstart: 1.0.8
+      typed-array-buffer: 1.0.3
+      typed-array-byte-length: 1.0.3
+      typed-array-byte-offset: 1.0.5
+      typed-array-length: 1.0.8
+      unbox-primitive: 1.1.0
+      which-typed-array: 1.1.24
+
+  es-aggregate-error@1.0.14:
     dependencies:
-      argparse: 2.0.1
-
-  jsesc@3.1.0: {}
-
-  json-buffer@3.0.1: {}
+      define-data-property: 1.1.4
+      define-properties: 1.2.1
+      es-abstract: 1.24.2
+      es-errors: 1.3.0
+      function-bind: 1.1.2
+      globalthis: 1.0.4
+      has-property-descriptors: 1.0.2
+      set-function-name: 2.0.2
 
-  json-crawl@0.5.3: {}
+  es-define-property@1.0.1: {}
 
-  json-parse-even-better-errors@2.3.1: {}
+  es-errors@1.3.0: {}
 
-  json-pointer@0.6.2:
+  es-object-atoms@1.1.2:
     dependencies:
-      foreach: 2.0.6
+      es-errors: 1.3.0
 
-  json-schema-compare@0.2.2:
+  es-set-tostringtag@2.1.0:
     dependencies:
-      lodash: 4.18.1
+      es-errors: 1.3.0
+      get-intrinsic: 1.3.0
+      has-tostringtag: 1.0.2
+      hasown: 2.0.4
 
-  json-schema-merge-allof@0.8.1:
+  es-to-primitive@1.3.4:
     dependencies:
-      compute-lcm: 1.1.2
-      json-schema-compare: 0.2.2
-      lodash: 4.18.1
+      es-abstract-get: 1.0.0
+      es-define-property: 1.0.1
+      es-errors: 1.3.0
+      is-callable: 1.2.7
+      is-date-object: 1.1.0
+      is-symbol: 1.1.1
+
+  es-toolkit@1.52.0: {}
 
-  json-schema-to-ts@2.7.2:
+  esast-util-from-estree@2.0.0:
     dependencies:
-      '@babel/runtime': 7.29.7
-      '@types/json-schema': 7.0.15
-      ts-algebra: 1.2.2
+      '@types/estree-jsx': 1.0.5
+      devlop: 1.1.0
+      estree-util-visit: 2.0.0
+      unist-util-position-from-estree: 2.0.0
 
-  json-schema-traverse@0.4.1: {}
+  esast-util-from-js@2.0.1:
+    dependencies:
+      '@types/estree-jsx': 1.0.5
+      acorn: 8.11.2
+      esast-util-from-estree: 2.0.0
+      vfile-message: 4.0.3
 
-  json-schema-traverse@1.0.0: {}
+  esbuild@0.25.12:
+    optionalDependencies:
+      '@esbuild/aix-ppc64': 0.25.12
+      '@esbuild/android-arm': 0.25.12
+      '@esbuild/android-arm64': 0.25.12
+      '@esbuild/android-x64': 0.25.12
+      '@esbuild/darwin-arm64': 0.25.12
+      '@esbuild/darwin-x64': 0.25.12
+      '@esbuild/freebsd-arm64': 0.25.12
+      '@esbuild/freebsd-x64': 0.25.12
+      '@esbuild/linux-arm': 0.25.12
+      '@esbuild/linux-arm64': 0.25.12
+      '@esbuild/linux-ia32': 0.25.12
+      '@esbuild/linux-loong64': 0.25.12
+      '@esbuild/linux-mips64el': 0.25.12
+      '@esbuild/linux-ppc64': 0.25.12
+      '@esbuild/linux-riscv64': 0.25.12
+      '@esbuild/linux-s390x': 0.25.12
+      '@esbuild/linux-x64': 0.25.12
+      '@esbuild/netbsd-arm64': 0.25.12
+      '@esbuild/netbsd-x64': 0.25.12
+      '@esbuild/openbsd-arm64': 0.25.12
+      '@esbuild/openbsd-x64': 0.25.12
+      '@esbuild/openharmony-arm64': 0.25.12
+      '@esbuild/sunos-x64': 0.25.12
+      '@esbuild/win32-arm64': 0.25.12
+      '@esbuild/win32-ia32': 0.25.12
+      '@esbuild/win32-x64': 0.25.12
+    optional: true
 
-  json-stable-stringify-without-jsonify@1.0.1: {}
+  escalade@3.2.0: {}
 
-  json5@2.2.3: {}
+  escape-html@1.0.3: {}
 
-  jsonc-parser@2.2.1: {}
+  escape-string-regexp@2.0.0: {}
 
-  jsonfile@6.2.1:
-    dependencies:
-      universalify: 2.0.1
-    optionalDependencies:
-      graceful-fs: 4.2.11
+  escape-string-regexp@5.0.0: {}
 
-  jsonpointer@5.0.1: {}
+  esprima@4.0.1: {}
 
-  katex@0.16.47:
+  estree-util-attach-comments@3.0.0:
     dependencies:
-      commander: 8.3.0
+      '@types/estree': 1.0.9
 
-  keyv@4.5.4:
+  estree-util-build-jsx@3.0.1:
     dependencies:
-      json-buffer: 3.0.1
-
-  khroma@2.1.0: {}
+      '@types/estree-jsx': 1.0.5
+      devlop: 1.1.0
+      estree-util-is-identifier-name: 3.0.0
+      estree-walker: 3.0.3
 
-  kind-of@6.0.3: {}
+  estree-util-is-identifier-name@3.0.0: {}
 
-  kleur@3.0.3: {}
+  estree-util-scope@1.0.1:
+    dependencies:
+      '@types/estree': 1.0.9
+      devlop: 1.1.0
 
-  kleur@4.1.5: {}
+  estree-util-to-js@2.0.0:
+    dependencies:
+      '@types/estree-jsx': 1.0.5
+      astring: 1.9.0
+      source-map: 0.7.6
 
-  latest-version@7.0.0:
+  estree-util-visit@2.0.0:
     dependencies:
-      package-json: 8.1.1
+      '@types/estree-jsx': 1.0.5
+      '@types/unist': 3.0.3
 
-  launch-editor@2.14.1:
+  estree-walker@3.0.3:
     dependencies:
-      picocolors: 1.1.1
-      shell-quote: 1.8.4
+      '@types/estree': 1.0.9
 
-  layout-base@1.0.2: {}
+  etag@1.8.1: {}
 
-  layout-base@2.0.1: {}
+  expand-template@2.0.3:
+    optional: true
 
-  leven@3.1.0: {}
+  expr-eval-fork@3.0.3: {}
 
-  levn@0.4.1:
+  express@4.22.0:
     dependencies:
-      prelude-ls: 1.2.1
-      type-check: 0.4.0
+      accepts: 1.3.8
+      array-flatten: 1.1.1
+      body-parser: 1.20.8
+      content-disposition: 0.5.4
+      content-type: 1.0.5
+      cookie: 0.7.2
+      cookie-signature: 1.0.7
+      debug: 2.6.9
+      depd: 2.0.0
+      encodeurl: 2.0.0
+      escape-html: 1.0.3
+      etag: 1.8.1
+      finalhandler: 1.3.2
+      fresh: 0.5.2
+      http-errors: 2.0.1
+      merge-descriptors: 1.0.3
+      methods: 1.1.2
+      on-finished: 2.4.1
+      parseurl: 1.3.3
+      path-to-regexp: 0.1.13
+      proxy-addr: 2.0.8
+      qs: 6.14.2
+      range-parser: 1.2.1
+      safe-buffer: 5.2.1
+      send: 0.19.2
+      serve-static: 1.16.3
+      setprototypeof: 1.2.0
+      statuses: 2.0.2
+      type-is: 1.6.18
+      utils-merge: 1.0.1
+      vary: 1.1.2
+    transitivePeerDependencies:
+      - supports-color
 
-  lightningcss-android-arm64@1.32.0:
-    optional: true
+  extend@3.0.2: {}
 
-  lightningcss-darwin-arm64@1.32.0:
-    optional: true
+  fast-deep-equal@3.1.3: {}
 
-  lightningcss-darwin-x64@1.32.0:
-    optional: true
+  fast-glob@3.3.3:
+    dependencies:
+      '@nodelib/fs.stat': 2.0.5
+      '@nodelib/fs.walk': 1.2.8
+      glob-parent: 5.1.2
+      merge2: 1.4.1
+      micromatch: 4.0.8
 
-  lightningcss-freebsd-x64@1.32.0:
-    optional: true
+  fast-json-stable-stringify@2.1.0: {}
 
-  lightningcss-linux-arm-gnueabihf@1.32.0:
-    optional: true
+  fast-memoize@2.5.2: {}
 
-  lightningcss-linux-arm64-gnu@1.32.0:
-    optional: true
+  fast-safe-stringify@2.1.1: {}
 
-  lightningcss-linux-arm64-musl@1.32.0:
-    optional: true
+  fast-uri@3.1.8: {}
 
-  lightningcss-linux-x64-gnu@1.32.0:
-    optional: true
+  fast-xml-builder@1.3.1:
+    dependencies:
+      path-expression-matcher: 1.6.2
+      xml-naming: 0.3.0
 
-  lightningcss-linux-x64-musl@1.32.0:
-    optional: true
+  fast-xml-parser@5.7.3:
+    dependencies:
+      '@nodable/entities': 2.2.0
+      fast-xml-builder: 1.3.1
+      path-expression-matcher: 1.6.2
+      strnum: 2.5.1
 
-  lightningcss-win32-arm64-msvc@1.32.0:
-    optional: true
+  fastq@1.20.3:
+    dependencies:
+      reusify: 1.1.0
 
-  lightningcss-win32-x64-msvc@1.32.0:
-    optional: true
+  fault@2.0.1:
+    dependencies:
+      format: 0.2.2
 
-  lightningcss@1.32.0:
+  favicons@7.2.0:
     dependencies:
-      detect-libc: 2.1.2
-    optionalDependencies:
-      lightningcss-android-arm64: 1.32.0
-      lightningcss-darwin-arm64: 1.32.0
-      lightningcss-darwin-x64: 1.32.0
-      lightningcss-freebsd-x64: 1.32.0
-      lightningcss-linux-arm-gnueabihf: 1.32.0
-      lightningcss-linux-arm64-gnu: 1.32.0
-      lightningcss-linux-arm64-musl: 1.32.0
-      lightningcss-linux-x64-gnu: 1.32.0
-      lightningcss-linux-x64-musl: 1.32.0
-      lightningcss-win32-arm64-msvc: 1.32.0
-      lightningcss-win32-x64-msvc: 1.32.0
-
-  lilconfig@3.1.3: {}
+      escape-html: 1.0.3
+      sharp: 0.33.5
+      xml2js: 0.6.2
 
-  lines-and-columns@1.2.4: {}
+  fdir@6.5.0(picomatch@4.0.7):
+    optionalDependencies:
+      picomatch: 4.0.7
 
-  liquid-json@0.3.1: {}
+  fflate@0.7.3: {}
 
-  loader-runner@4.3.2: {}
+  fflate@0.7.5: {}
 
-  loader-utils@2.0.4:
-    dependencies:
-      big.js: 5.2.2
-      emojis-list: 3.0.0
-      json5: 2.2.3
+  fflate@0.8.2: {}
 
-  locate-path@6.0.0:
+  fill-range@7.1.1:
     dependencies:
-      p-locate: 5.0.0
+      to-regex-range: 5.0.1
 
-  locate-path@7.2.0:
+  finalhandler@1.3.2:
     dependencies:
-      p-locate: 6.0.0
+      debug: 2.6.9
+      encodeurl: 2.0.0
+      escape-html: 1.0.3
+      on-finished: 2.4.1
+      parseurl: 1.3.3
+      statuses: 2.0.2
+      unpipe: 1.0.0
+    transitivePeerDependencies:
+      - supports-color
 
-  lodash-es@4.18.1: {}
+  follow-redirects@1.16.1: {}
 
-  lodash.debounce@4.0.8: {}
+  for-each@0.3.5:
+    dependencies:
+      is-callable: 1.2.7
 
-  lodash.get@4.4.2: {}
+  form-data-encoder@2.1.4: {}
 
-  lodash.memoize@4.1.2: {}
+  form-data@4.0.6:
+    dependencies:
+      asynckit: 0.4.0
+      combined-stream: 1.0.8
+      es-set-tostringtag: 2.1.0
+      hasown: 2.0.4
+      mime-types: 2.1.35
 
-  lodash.uniq@4.5.0: {}
+  format@0.2.2: {}
 
-  lodash@4.17.21: {}
+  forwarded@0.2.0: {}
 
-  lodash@4.17.23: {}
+  fractional-indexing@3.2.0: {}
 
-  lodash@4.18.1: {}
+  fresh@0.5.2: {}
 
-  longest-streak@2.0.4: {}
+  front-matter@4.0.2:
+    dependencies:
+      js-yaml: 3.15.2
 
-  longest-streak@3.1.0: {}
+  fs-constants@1.0.0:
+    optional: true
 
-  loose-envify@1.4.0:
+  fs-extra@10.1.0:
     dependencies:
-      js-tokens: 4.0.0
+      graceful-fs: 4.2.11
+      jsonfile: 6.2.1
+      universalify: 2.0.1
 
-  lower-case@2.0.2:
+  fs-extra@11.1.0:
     dependencies:
-      tslib: 2.8.1
-
-  lowercase-keys@3.0.0: {}
+      graceful-fs: 4.2.11
+      jsonfile: 6.2.1
+      universalify: 2.0.1
 
-  lowlight@1.20.0:
+  fs-extra@11.1.1:
     dependencies:
-      fault: 1.0.4
-      highlight.js: 10.7.3
+      graceful-fs: 4.2.11
+      jsonfile: 6.2.1
+      universalify: 2.0.1
 
-  lru-cache@11.5.1: {}
+  fs-extra@11.2.0:
+    dependencies:
+      graceful-fs: 4.2.11
+      jsonfile: 6.2.1
+      universalify: 2.0.1
 
-  lru-cache@5.1.1:
+  fs-extra@11.3.6:
     dependencies:
-      yallist: 3.1.1
+      graceful-fs: 4.2.11
+      jsonfile: 6.2.1
+      universalify: 2.0.1
+
+  fs.realpath@1.0.0: {}
 
-  magic-error@0.0.1: {}
+  fsevents@2.3.3:
+    optional: true
 
-  markdown-extensions@2.0.0: {}
+  function-bind@1.1.2: {}
 
-  markdown-table@2.0.0:
+  function.prototype.name@1.2.0:
     dependencies:
-      repeat-string: 1.6.1
+      call-bind: 1.0.9
+      call-bound: 1.0.4
+      es-define-property: 1.0.1
+      es-errors: 1.3.0
+      functions-have-names: 1.2.3
+      has-property-descriptors: 1.0.2
+      hasown: 2.0.4
+      is-callable: 1.2.7
+      is-document.all: 1.0.0
 
-  markdown-table@3.0.4: {}
+  functions-have-names@1.2.3: {}
 
-  markdown-to-jsx@7.7.17(react@19.2.7):
-    optionalDependencies:
-      react: 19.2.7
+  gcd@0.0.1: {}
 
-  marked@16.4.2: {}
+  generator-function@2.0.1: {}
 
-  math-intrinsics@1.1.0: {}
+  get-caller-file@2.0.5: {}
 
-  mdast-util-definitions@5.1.2:
-    dependencies:
-      '@types/mdast': 3.0.15
-      '@types/unist': 2.0.11
-      unist-util-visit: 4.1.2
+  get-east-asian-width@1.6.0: {}
 
-  mdast-util-directive@3.1.0:
+  get-intrinsic@1.3.0:
     dependencies:
-      '@types/mdast': 4.0.4
-      '@types/unist': 3.0.3
-      ccount: 2.0.1
-      devlop: 1.1.0
-      mdast-util-from-markdown: 2.0.3
-      mdast-util-to-markdown: 2.1.2
-      parse-entities: 4.0.2
-      stringify-entities: 4.0.4
-      unist-util-visit-parents: 6.0.2
-    transitivePeerDependencies:
-      - supports-color
+      call-bind-apply-helpers: 1.0.2
+      es-define-property: 1.0.1
+      es-errors: 1.3.0
+      es-object-atoms: 1.1.2
+      function-bind: 1.1.2
+      get-proto: 1.0.1
+      gopd: 1.2.0
+      has-symbols: 1.1.0
+      hasown: 2.0.4
+      math-intrinsics: 1.1.0
 
-  mdast-util-find-and-replace@1.1.1:
+  get-proto@1.0.1:
     dependencies:
-      escape-string-regexp: 4.0.0
-      unist-util-is: 4.1.0
-      unist-util-visit-parents: 3.1.1
+      dunder-proto: 1.0.1
+      es-object-atoms: 1.1.2
+
+  get-stream@6.0.1: {}
 
-  mdast-util-find-and-replace@3.0.2:
+  get-symbol-description@1.1.0:
     dependencies:
-      '@types/mdast': 4.0.4
-      escape-string-regexp: 5.0.0
-      unist-util-is: 6.0.1
-      unist-util-visit-parents: 6.0.2
+      call-bound: 1.0.4
+      es-errors: 1.3.0
+      get-intrinsic: 1.3.0
+
+  github-from-package@0.0.0:
+    optional: true
 
-  mdast-util-from-markdown@0.8.5:
+  glob-parent@5.1.2:
     dependencies:
-      '@types/mdast': 3.0.15
-      mdast-util-to-string: 2.0.0
-      micromark: 2.11.4
-      parse-entities: 2.0.0
-      unist-util-stringify-position: 2.0.3
-    transitivePeerDependencies:
-      - supports-color
+      is-glob: 4.0.3
 
-  mdast-util-from-markdown@1.3.1:
+  glob-parent@6.0.2:
     dependencies:
-      '@types/mdast': 3.0.15
-      '@types/unist': 2.0.11
-      decode-named-character-reference: 1.3.0
-      mdast-util-to-string: 3.2.0
-      micromark: 3.2.0
-      micromark-util-decode-numeric-character-reference: 1.1.0
-      micromark-util-decode-string: 1.1.0
-      micromark-util-normalize-identifier: 1.1.0
-      micromark-util-symbol: 1.1.0
-      micromark-util-types: 1.1.0
-      unist-util-stringify-position: 3.0.3
-      uvu: 0.5.6
-    transitivePeerDependencies:
-      - supports-color
+      is-glob: 4.0.3
 
-  mdast-util-from-markdown@2.0.3:
+  glob@7.1.6:
     dependencies:
-      '@types/mdast': 4.0.4
-      '@types/unist': 3.0.3
-      decode-named-character-reference: 1.3.0
-      devlop: 1.1.0
-      mdast-util-to-string: 4.0.0
-      micromark: 4.0.2
-      micromark-util-decode-numeric-character-reference: 2.0.2
-      micromark-util-decode-string: 2.0.1
-      micromark-util-normalize-identifier: 2.0.1
-      micromark-util-symbol: 2.0.1
-      micromark-util-types: 2.0.2
-      unist-util-stringify-position: 4.0.0
-    transitivePeerDependencies:
-      - supports-color
+      fs.realpath: 1.0.0
+      inflight: 1.0.6
+      inherits: 2.0.4
+      minimatch: 3.1.5
+      once: 1.4.0
+      path-is-absolute: 1.0.1
 
-  mdast-util-frontmatter@0.2.0:
+  globalthis@1.0.4:
     dependencies:
-      micromark-extension-frontmatter: 0.2.2
+      define-properties: 1.2.1
+      gopd: 1.2.0
 
-  mdast-util-frontmatter@2.0.1:
+  gopd@1.2.0: {}
+
+  got@12.6.1:
     dependencies:
-      '@types/mdast': 4.0.4
-      devlop: 1.1.0
-      escape-string-regexp: 5.0.0
-      mdast-util-from-markdown: 2.0.3
-      mdast-util-to-markdown: 2.1.2
-      micromark-extension-frontmatter: 2.0.0
-    transitivePeerDependencies:
-      - supports-color
+      '@sindresorhus/is': 5.6.0
+      '@szmarczak/http-timer': 5.0.1
+      cacheable-lookup: 7.0.0
+      cacheable-request: 10.2.14
+      decompress-response: 6.0.0
+      form-data-encoder: 2.1.4
+      get-stream: 6.0.1
+      http2-wrapper: 2.2.1
+      lowercase-keys: 3.0.0
+      p-cancelable: 3.0.0
+      responselike: 3.0.0
 
-  mdast-util-gfm-autolink-literal@0.1.3:
+  got@13.0.0:
     dependencies:
-      ccount: 1.1.0
-      mdast-util-find-and-replace: 1.1.1
-      micromark: 2.11.4
-    transitivePeerDependencies:
-      - supports-color
+      '@sindresorhus/is': 5.6.0
+      '@szmarczak/http-timer': 5.0.1
+      cacheable-lookup: 7.0.0
+      cacheable-request: 10.2.14
+      decompress-response: 6.0.0
+      form-data-encoder: 2.1.4
+      get-stream: 6.0.1
+      http2-wrapper: 2.2.1
+      lowercase-keys: 3.0.0
+      p-cancelable: 3.0.0
+      responselike: 3.0.0
 
-  mdast-util-gfm-autolink-literal@2.0.1:
-    dependencies:
-      '@types/mdast': 4.0.4
-      ccount: 2.0.1
-      devlop: 1.1.0
-      mdast-util-find-and-replace: 3.0.2
-      micromark-util-character: 2.1.1
+  graceful-fs@4.2.11: {}
 
-  mdast-util-gfm-footnote@2.1.0:
-    dependencies:
-      '@types/mdast': 4.0.4
-      devlop: 1.1.0
-      mdast-util-from-markdown: 2.0.3
-      mdast-util-to-markdown: 2.1.2
-      micromark-util-normalize-identifier: 2.0.1
-    transitivePeerDependencies:
-      - supports-color
+  graphql@16.11.0: {}
 
-  mdast-util-gfm-strikethrough@0.2.3:
-    dependencies:
-      mdast-util-to-markdown: 0.6.5
+  harfbuzzjs@0.10.0: {}
 
-  mdast-util-gfm-strikethrough@2.0.0:
-    dependencies:
-      '@types/mdast': 4.0.4
-      mdast-util-from-markdown: 2.0.3
-      mdast-util-to-markdown: 2.1.2
-    transitivePeerDependencies:
-      - supports-color
+  has-bigints@1.1.0: {}
 
-  mdast-util-gfm-table@0.1.6:
+  has-property-descriptors@1.0.2:
     dependencies:
-      markdown-table: 2.0.0
-      mdast-util-to-markdown: 0.6.5
+      es-define-property: 1.0.1
 
-  mdast-util-gfm-table@2.0.0:
+  has-proto@1.2.0:
     dependencies:
-      '@types/mdast': 4.0.4
-      devlop: 1.1.0
-      markdown-table: 3.0.4
-      mdast-util-from-markdown: 2.0.3
-      mdast-util-to-markdown: 2.1.2
-    transitivePeerDependencies:
-      - supports-color
+      dunder-proto: 1.0.1
+
+  has-symbols@1.1.0: {}
 
-  mdast-util-gfm-task-list-item@0.1.6:
+  has-tostringtag@1.0.2:
     dependencies:
-      mdast-util-to-markdown: 0.6.5
+      has-symbols: 1.1.0
 
-  mdast-util-gfm-task-list-item@2.0.0:
+  hasown@2.0.4:
     dependencies:
-      '@types/mdast': 4.0.4
-      devlop: 1.1.0
-      mdast-util-from-markdown: 2.0.3
-      mdast-util-to-markdown: 2.1.2
-    transitivePeerDependencies:
-      - supports-color
+      function-bind: 1.1.2
 
-  mdast-util-gfm@0.1.2:
+  hast-util-embedded@3.0.0:
     dependencies:
-      mdast-util-gfm-autolink-literal: 0.1.3
-      mdast-util-gfm-strikethrough: 0.2.3
-      mdast-util-gfm-table: 0.1.6
-      mdast-util-gfm-task-list-item: 0.1.6
-      mdast-util-to-markdown: 0.6.5
-    transitivePeerDependencies:
-      - supports-color
+      '@types/hast': 3.0.5
+      hast-util-is-element: 3.0.0
 
-  mdast-util-gfm@3.1.0:
+  hast-util-from-dom@5.0.1:
     dependencies:
-      mdast-util-from-markdown: 2.0.3
-      mdast-util-gfm-autolink-literal: 2.0.1
-      mdast-util-gfm-footnote: 2.1.0
-      mdast-util-gfm-strikethrough: 2.0.0
-      mdast-util-gfm-table: 2.0.0
-      mdast-util-gfm-task-list-item: 2.0.0
-      mdast-util-to-markdown: 2.1.2
-    transitivePeerDependencies:
-      - supports-color
+      '@types/hast': 3.0.5
+      hastscript: 9.0.1
+      web-namespaces: 2.0.1
 
-  mdast-util-math@3.0.0:
+  hast-util-from-html-isomorphic@2.0.0:
     dependencies:
-      '@types/hast': 3.0.4
-      '@types/mdast': 4.0.4
-      devlop: 1.1.0
-      longest-streak: 3.1.0
-      mdast-util-from-markdown: 2.0.3
-      mdast-util-to-markdown: 2.1.2
+      '@types/hast': 3.0.5
+      hast-util-from-dom: 5.0.1
+      hast-util-from-html: 2.0.3
       unist-util-remove-position: 5.0.0
-    transitivePeerDependencies:
-      - supports-color
 
-  mdast-util-mdx-expression@2.0.1:
+  hast-util-from-html@2.0.3:
     dependencies:
-      '@types/estree-jsx': 1.0.5
-      '@types/hast': 3.0.4
-      '@types/mdast': 4.0.4
+      '@types/hast': 3.0.5
       devlop: 1.1.0
-      mdast-util-from-markdown: 2.0.3
-      mdast-util-to-markdown: 2.1.2
-    transitivePeerDependencies:
-      - supports-color
+      hast-util-from-parse5: 8.0.3
+      parse5: 7.3.0
+      vfile: 6.0.3
+      vfile-message: 4.0.3
 
-  mdast-util-mdx-jsx@3.2.0:
+  hast-util-from-parse5@8.0.3:
     dependencies:
-      '@types/estree-jsx': 1.0.5
-      '@types/hast': 3.0.4
-      '@types/mdast': 4.0.4
+      '@types/hast': 3.0.5
       '@types/unist': 3.0.3
-      ccount: 2.0.1
       devlop: 1.1.0
-      mdast-util-from-markdown: 2.0.3
-      mdast-util-to-markdown: 2.1.2
-      parse-entities: 4.0.2
-      stringify-entities: 4.0.4
-      unist-util-stringify-position: 4.0.0
-      vfile-message: 4.0.3
-    transitivePeerDependencies:
-      - supports-color
+      hastscript: 9.0.1
+      property-information: 7.2.0
+      vfile: 6.0.3
+      vfile-location: 5.0.3
+      web-namespaces: 2.0.1
 
-  mdast-util-mdx@3.0.0:
+  hast-util-has-property@3.0.0:
     dependencies:
-      mdast-util-from-markdown: 2.0.3
-      mdast-util-mdx-expression: 2.0.1
-      mdast-util-mdx-jsx: 3.2.0
-      mdast-util-mdxjs-esm: 2.0.1
-      mdast-util-to-markdown: 2.1.2
-    transitivePeerDependencies:
-      - supports-color
+      '@types/hast': 3.0.5
 
-  mdast-util-mdxjs-esm@2.0.1:
+  hast-util-is-body-ok-link@3.0.1:
     dependencies:
-      '@types/estree-jsx': 1.0.5
-      '@types/hast': 3.0.4
-      '@types/mdast': 4.0.4
-      devlop: 1.1.0
-      mdast-util-from-markdown: 2.0.3
-      mdast-util-to-markdown: 2.1.2
-    transitivePeerDependencies:
-      - supports-color
+      '@types/hast': 3.0.5
 
-  mdast-util-phrasing@4.1.0:
+  hast-util-is-element@3.0.0:
     dependencies:
-      '@types/mdast': 4.0.4
+      '@types/hast': 3.0.5
+
+  hast-util-minify-whitespace@1.0.1:
+    dependencies:
+      '@types/hast': 3.0.5
+      hast-util-embedded: 3.0.0
+      hast-util-is-element: 3.0.0
+      hast-util-whitespace: 3.0.0
       unist-util-is: 6.0.1
 
-  mdast-util-to-hast@11.3.0:
+  hast-util-parse-selector@4.0.0:
     dependencies:
-      '@types/hast': 2.3.10
-      '@types/mdast': 3.0.15
-      '@types/mdurl': 1.0.5
-      mdast-util-definitions: 5.1.2
-      mdurl: 1.0.1
-      unist-builder: 3.0.1
-      unist-util-generated: 2.0.1
-      unist-util-position: 4.0.4
-      unist-util-visit: 4.1.2
+      '@types/hast': 3.0.5
 
-  mdast-util-to-hast@12.3.0:
+  hast-util-phrasing@3.0.1:
     dependencies:
-      '@types/hast': 2.3.10
-      '@types/mdast': 3.0.15
-      mdast-util-definitions: 5.1.2
-      micromark-util-sanitize-uri: 1.2.0
-      trim-lines: 3.0.1
-      unist-util-generated: 2.0.1
-      unist-util-position: 4.0.4
-      unist-util-visit: 4.1.2
+      '@types/hast': 3.0.5
+      hast-util-embedded: 3.0.0
+      hast-util-has-property: 3.0.0
+      hast-util-is-body-ok-link: 3.0.1
+      hast-util-is-element: 3.0.0
 
-  mdast-util-to-hast@13.2.1:
+  hast-util-to-estree@3.1.0:
     dependencies:
-      '@types/hast': 3.0.4
-      '@types/mdast': 4.0.4
-      '@ungap/structured-clone': 1.3.2
+      '@types/estree': 1.0.9
+      '@types/estree-jsx': 1.0.5
+      '@types/hast': 3.0.5
+      comma-separated-tokens: 2.0.3
       devlop: 1.1.0
-      micromark-util-sanitize-uri: 2.0.1
-      trim-lines: 3.0.1
+      estree-util-attach-comments: 3.0.0
+      estree-util-is-identifier-name: 3.0.0
+      hast-util-whitespace: 3.0.0
+      mdast-util-mdx-expression: 2.0.1
+      mdast-util-mdx-jsx: 3.2.0
+      mdast-util-mdxjs-esm: 2.0.1
+      property-information: 6.5.0
+      space-separated-tokens: 2.0.2
+      style-to-object: 0.4.4
       unist-util-position: 5.0.0
-      unist-util-visit: 5.1.0
-      vfile: 6.0.3
-
-  mdast-util-to-markdown@0.6.5:
-    dependencies:
-      '@types/unist': 2.0.11
-      longest-streak: 2.0.4
-      mdast-util-to-string: 2.0.0
-      parse-entities: 2.0.0
-      repeat-string: 1.6.1
-      zwitch: 1.0.5
+      zwitch: 2.0.4
+    transitivePeerDependencies:
+      - supports-color
 
-  mdast-util-to-markdown@2.1.2:
+  hast-util-to-html@9.0.4:
     dependencies:
-      '@types/mdast': 4.0.4
+      '@types/hast': 3.0.5
       '@types/unist': 3.0.3
-      longest-streak: 3.1.0
-      mdast-util-phrasing: 4.1.0
-      mdast-util-to-string: 4.0.0
-      micromark-util-classify-character: 2.0.1
-      micromark-util-decode-string: 2.0.1
-      unist-util-visit: 5.1.0
+      ccount: 2.0.1
+      comma-separated-tokens: 2.0.3
+      hast-util-whitespace: 3.0.0
+      html-void-elements: 3.0.0
+      mdast-util-to-hast: 13.2.1
+      property-information: 6.5.0
+      space-separated-tokens: 2.0.2
+      stringify-entities: 4.0.4
       zwitch: 2.0.4
 
-  mdast-util-to-string@2.0.0: {}
-
-  mdast-util-to-string@3.2.0:
-    dependencies:
-      '@types/mdast': 3.0.15
-
-  mdast-util-to-string@4.0.0:
-    dependencies:
-      '@types/mdast': 4.0.4
-
-  mdn-data@2.0.14: {}
-
-  mdn-data@2.0.28: {}
-
-  mdn-data@2.0.30: {}
-
-  mdurl@1.0.1: {}
-
-  media-typer@0.3.0: {}
-
-  memfs@4.57.6(tslib@2.8.1):
-    dependencies:
-      '@jsonjoy.com/fs-core': 4.57.6(tslib@2.8.1)
-      '@jsonjoy.com/fs-fsa': 4.57.6(tslib@2.8.1)
-      '@jsonjoy.com/fs-node': 4.57.6(tslib@2.8.1)
-      '@jsonjoy.com/fs-node-builtins': 4.57.6(tslib@2.8.1)
-      '@jsonjoy.com/fs-node-to-fsa': 4.57.6(tslib@2.8.1)
-      '@jsonjoy.com/fs-node-utils': 4.57.6(tslib@2.8.1)
-      '@jsonjoy.com/fs-print': 4.57.6(tslib@2.8.1)
-      '@jsonjoy.com/fs-snapshot': 4.57.6(tslib@2.8.1)
-      '@jsonjoy.com/json-pack': 1.21.0(tslib@2.8.1)
-      '@jsonjoy.com/util': 1.9.0(tslib@2.8.1)
-      glob-to-regex.js: 1.2.0(tslib@2.8.1)
-      thingies: 2.6.0(tslib@2.8.1)
-      tree-dump: 1.1.0(tslib@2.8.1)
-      tslib: 2.8.1
-
-  merge-descriptors@1.0.3: {}
-
-  merge-stream@2.0.0: {}
-
-  merge2@1.4.1: {}
-
-  mermaid@11.15.0:
-    dependencies:
-      '@braintree/sanitize-url': 7.1.2
-      '@iconify/utils': 3.1.3
-      '@mermaid-js/parser': 1.1.1
-      '@types/d3': 7.4.3
-      '@upsetjs/venn.js': 2.0.0
-      cytoscape: 3.34.0
-      cytoscape-cose-bilkent: 4.1.0(cytoscape@3.34.0)
-      cytoscape-fcose: 2.2.0(cytoscape@3.34.0)
-      d3: 7.9.0
-      d3-sankey: 0.12.3
-      dagre-d3-es: 7.0.14
-      dayjs: 1.11.21
-      dompurify: 3.4.8
-      es-toolkit: 1.47.0
-      katex: 0.16.47
-      khroma: 2.1.0
-      marked: 16.4.2
-      roughjs: 4.6.6
-      stylis: 4.4.0
-      ts-dedent: 2.2.0
-      uuid: 14.0.1
-
-  methods@1.1.2: {}
-
-  micromark-core-commonmark@1.1.0:
+  hast-util-to-html@9.0.5:
     dependencies:
-      decode-named-character-reference: 1.3.0
-      micromark-factory-destination: 1.1.0
-      micromark-factory-label: 1.1.0
-      micromark-factory-space: 1.1.0
-      micromark-factory-title: 1.1.0
-      micromark-factory-whitespace: 1.1.0
-      micromark-util-character: 1.2.0
-      micromark-util-chunked: 1.1.0
-      micromark-util-classify-character: 1.1.0
-      micromark-util-html-tag-name: 1.2.0
-      micromark-util-normalize-identifier: 1.1.0
-      micromark-util-resolve-all: 1.1.0
-      micromark-util-subtokenize: 1.1.0
-      micromark-util-symbol: 1.1.0
-      micromark-util-types: 1.1.0
-      uvu: 0.5.6
-
-  micromark-core-commonmark@2.0.3:
-    dependencies:
-      decode-named-character-reference: 1.3.0
-      devlop: 1.1.0
-      micromark-factory-destination: 2.0.1
-      micromark-factory-label: 2.0.1
-      micromark-factory-space: 2.0.1
-      micromark-factory-title: 2.0.1
-      micromark-factory-whitespace: 2.0.1
-      micromark-util-character: 2.1.1
-      micromark-util-chunked: 2.0.1
-      micromark-util-classify-character: 2.0.1
-      micromark-util-html-tag-name: 2.0.1
-      micromark-util-normalize-identifier: 2.0.1
-      micromark-util-resolve-all: 2.0.1
-      micromark-util-subtokenize: 2.1.0
-      micromark-util-symbol: 2.0.1
-      micromark-util-types: 2.0.2
+      '@types/hast': 3.0.5
+      '@types/unist': 3.0.3
+      ccount: 2.0.1
+      comma-separated-tokens: 2.0.3
+      hast-util-whitespace: 3.0.0
+      html-void-elements: 3.0.0
+      mdast-util-to-hast: 13.2.1
+      property-information: 7.2.0
+      space-separated-tokens: 2.0.2
+      stringify-entities: 4.0.4
+      zwitch: 2.0.4
 
-  micromark-extension-directive@3.0.2:
+  hast-util-to-jsx-runtime@2.3.6:
     dependencies:
+      '@types/estree': 1.0.9
+      '@types/hast': 3.0.5
+      '@types/unist': 3.0.3
+      comma-separated-tokens: 2.0.3
       devlop: 1.1.0
-      micromark-factory-space: 2.0.1
-      micromark-factory-whitespace: 2.0.1
-      micromark-util-character: 2.1.1
-      micromark-util-symbol: 2.0.1
-      micromark-util-types: 2.0.2
-      parse-entities: 4.0.2
-
-  micromark-extension-frontmatter@0.2.2:
-    dependencies:
-      fault: 1.0.4
-
-  micromark-extension-frontmatter@2.0.0:
-    dependencies:
-      fault: 2.0.1
-      micromark-util-character: 2.1.1
-      micromark-util-symbol: 2.0.1
-      micromark-util-types: 2.0.2
-
-  micromark-extension-gfm-autolink-literal@0.5.7:
-    dependencies:
-      micromark: 2.11.4
+      estree-util-is-identifier-name: 3.0.0
+      hast-util-whitespace: 3.0.0
+      mdast-util-mdx-expression: 2.0.1
+      mdast-util-mdx-jsx: 3.2.0
+      mdast-util-mdxjs-esm: 2.0.1
+      property-information: 7.2.0
+      space-separated-tokens: 2.0.2
+      style-to-js: 1.1.21
+      unist-util-position: 5.0.0
+      vfile-message: 4.0.3
     transitivePeerDependencies:
       - supports-color
 
-  micromark-extension-gfm-autolink-literal@2.1.0:
-    dependencies:
-      micromark-util-character: 2.1.1
-      micromark-util-sanitize-uri: 2.0.1
-      micromark-util-symbol: 2.0.1
-      micromark-util-types: 2.0.2
-
-  micromark-extension-gfm-footnote@2.1.0:
+  hast-util-to-mdast@10.1.0:
     dependencies:
-      devlop: 1.1.0
-      micromark-core-commonmark: 2.0.3
-      micromark-factory-space: 2.0.1
-      micromark-util-character: 2.1.1
-      micromark-util-normalize-identifier: 2.0.1
-      micromark-util-sanitize-uri: 2.0.1
-      micromark-util-symbol: 2.0.1
-      micromark-util-types: 2.0.2
+      '@types/hast': 3.0.5
+      '@types/mdast': 4.0.4
+      '@ungap/structured-clone': 1.4.0
+      hast-util-phrasing: 3.0.1
+      hast-util-to-html: 9.0.5
+      hast-util-to-text: 4.0.2
+      hast-util-whitespace: 3.0.0
+      mdast-util-phrasing: 4.1.0
+      mdast-util-to-hast: 13.2.1
+      mdast-util-to-string: 4.0.0
+      rehype-minify-whitespace: 6.0.2
+      trim-trailing-lines: 2.1.0
+      unist-util-position: 5.0.0
+      unist-util-visit: 5.0.0
 
-  micromark-extension-gfm-strikethrough@0.6.5:
+  hast-util-to-string@3.0.1:
     dependencies:
-      micromark: 2.11.4
-    transitivePeerDependencies:
-      - supports-color
+      '@types/hast': 3.0.5
 
-  micromark-extension-gfm-strikethrough@2.1.0:
+  hast-util-to-text@4.0.2:
     dependencies:
-      devlop: 1.1.0
-      micromark-util-chunked: 2.0.1
-      micromark-util-classify-character: 2.0.1
-      micromark-util-resolve-all: 2.0.1
-      micromark-util-symbol: 2.0.1
-      micromark-util-types: 2.0.2
+      '@types/hast': 3.0.5
+      '@types/unist': 3.0.3
+      hast-util-is-element: 3.0.0
+      unist-util-find-after: 5.0.0
 
-  micromark-extension-gfm-table@0.4.3:
+  hast-util-whitespace@3.0.0:
     dependencies:
-      micromark: 2.11.4
-    transitivePeerDependencies:
-      - supports-color
+      '@types/hast': 3.0.5
 
-  micromark-extension-gfm-table@2.1.1:
+  hastscript@9.0.1:
     dependencies:
-      devlop: 1.1.0
-      micromark-factory-space: 2.0.1
-      micromark-util-character: 2.1.1
-      micromark-util-symbol: 2.0.1
-      micromark-util-types: 2.0.2
+      '@types/hast': 3.0.5
+      comma-separated-tokens: 2.0.3
+      hast-util-parse-selector: 4.0.0
+      property-information: 7.2.0
+      space-separated-tokens: 2.0.2
 
-  micromark-extension-gfm-tagfilter@0.3.0: {}
+  hex-rgb@4.3.0: {}
 
-  micromark-extension-gfm-tagfilter@2.0.0:
-    dependencies:
-      micromark-util-types: 2.0.2
+  html-void-elements@3.0.0: {}
+
+  http-cache-semantics@4.3.0: {}
 
-  micromark-extension-gfm-task-list-item@0.3.3:
+  http-errors@2.0.1:
     dependencies:
-      micromark: 2.11.4
-    transitivePeerDependencies:
-      - supports-color
+      depd: 2.0.0
+      inherits: 2.0.4
+      setprototypeof: 1.2.0
+      statuses: 2.0.2
+      toidentifier: 1.0.1
 
-  micromark-extension-gfm-task-list-item@2.1.0:
+  http2-wrapper@2.2.1:
     dependencies:
-      devlop: 1.1.0
-      micromark-factory-space: 2.0.1
-      micromark-util-character: 2.1.1
-      micromark-util-symbol: 2.0.1
-      micromark-util-types: 2.0.2
+      quick-lru: 5.1.1
+      resolve-alpn: 1.2.1
 
-  micromark-extension-gfm@0.3.3:
+  https-proxy-agent@5.0.1:
     dependencies:
-      micromark: 2.11.4
-      micromark-extension-gfm-autolink-literal: 0.5.7
-      micromark-extension-gfm-strikethrough: 0.6.5
-      micromark-extension-gfm-table: 0.4.3
-      micromark-extension-gfm-tagfilter: 0.3.0
-      micromark-extension-gfm-task-list-item: 0.3.3
+      agent-base: 6.0.2
+      debug: 4.4.3
     transitivePeerDependencies:
       - supports-color
 
-  micromark-extension-gfm@3.0.0:
-    dependencies:
-      micromark-extension-gfm-autolink-literal: 2.1.0
-      micromark-extension-gfm-footnote: 2.1.0
-      micromark-extension-gfm-strikethrough: 2.1.0
-      micromark-extension-gfm-table: 2.1.1
-      micromark-extension-gfm-tagfilter: 2.0.0
-      micromark-extension-gfm-task-list-item: 2.1.0
-      micromark-util-combine-extensions: 2.0.1
-      micromark-util-types: 2.0.2
+  husky@9.1.7: {}
 
-  micromark-extension-math@3.1.0:
-    dependencies:
-      '@types/katex': 0.16.8
-      devlop: 1.1.0
-      katex: 0.16.47
-      micromark-factory-space: 2.0.1
-      micromark-util-character: 2.1.1
-      micromark-util-symbol: 2.0.1
-      micromark-util-types: 2.0.2
+  ico-endec@0.1.6: {}
 
-  micromark-extension-mdx-expression@3.0.1:
+  iconv-lite@0.4.24:
     dependencies:
-      '@types/estree': 1.0.9
-      devlop: 1.1.0
-      micromark-factory-mdx-expression: 2.0.3
-      micromark-factory-space: 2.0.1
-      micromark-util-character: 2.1.1
-      micromark-util-events-to-acorn: 2.0.3
-      micromark-util-symbol: 2.0.1
-      micromark-util-types: 2.0.2
+      safer-buffer: 2.1.2
 
-  micromark-extension-mdx-jsx@3.0.2:
+  iconv-lite@0.7.3:
     dependencies:
-      '@types/estree': 1.0.9
-      devlop: 1.1.0
-      estree-util-is-identifier-name: 3.0.0
-      micromark-factory-mdx-expression: 2.0.3
-      micromark-factory-space: 2.0.1
-      micromark-util-character: 2.1.1
-      micromark-util-events-to-acorn: 2.0.3
-      micromark-util-symbol: 2.0.1
-      micromark-util-types: 2.0.2
-      vfile-message: 4.0.3
+      safer-buffer: 2.1.2
 
-  micromark-extension-mdx-md@2.0.0:
-    dependencies:
-      micromark-util-types: 2.0.2
+  ieee754@1.2.1:
+    optional: true
 
-  micromark-extension-mdxjs-esm@3.0.0:
-    dependencies:
-      '@types/estree': 1.0.9
-      devlop: 1.1.0
-      micromark-core-commonmark: 2.0.3
-      micromark-util-character: 2.1.1
-      micromark-util-events-to-acorn: 2.0.3
-      micromark-util-symbol: 2.0.1
-      micromark-util-types: 2.0.2
-      unist-util-position-from-estree: 2.0.0
-      vfile-message: 4.0.3
+  ignore@7.0.5: {}
 
-  micromark-extension-mdxjs@3.0.0:
-    dependencies:
-      acorn: 8.16.0
-      acorn-jsx: 5.3.2(acorn@8.16.0)
-      micromark-extension-mdx-expression: 3.0.1
-      micromark-extension-mdx-jsx: 3.0.2
-      micromark-extension-mdx-md: 2.0.0
-      micromark-extension-mdxjs-esm: 3.0.0
-      micromark-util-combine-extensions: 2.0.1
-      micromark-util-types: 2.0.2
+  image-size@2.0.2: {}
 
-  micromark-factory-destination@1.1.0:
-    dependencies:
-      micromark-util-character: 1.2.0
-      micromark-util-symbol: 1.1.0
-      micromark-util-types: 1.1.0
+  immer@9.0.21: {}
 
-  micromark-factory-destination@2.0.1:
-    dependencies:
-      micromark-util-character: 2.1.1
-      micromark-util-symbol: 2.0.1
-      micromark-util-types: 2.0.2
+  indent-string@5.0.0: {}
 
-  micromark-factory-label@1.1.0:
+  inflight@1.0.6:
     dependencies:
-      micromark-util-character: 1.2.0
-      micromark-util-symbol: 1.1.0
-      micromark-util-types: 1.1.0
-      uvu: 0.5.6
+      once: 1.4.0
+      wrappy: 1.0.2
 
-  micromark-factory-label@2.0.1:
-    dependencies:
-      devlop: 1.1.0
-      micromark-util-character: 2.1.1
-      micromark-util-symbol: 2.0.1
-      micromark-util-types: 2.0.2
+  inherits@2.0.4: {}
 
-  micromark-factory-mdx-expression@2.0.3:
-    dependencies:
-      '@types/estree': 1.0.9
-      devlop: 1.1.0
-      micromark-factory-space: 2.0.1
-      micromark-util-character: 2.1.1
-      micromark-util-events-to-acorn: 2.0.3
-      micromark-util-symbol: 2.0.1
-      micromark-util-types: 2.0.2
-      unist-util-position-from-estree: 2.0.0
-      vfile-message: 4.0.3
+  ini@1.3.8:
+    optional: true
 
-  micromark-factory-space@1.1.0:
+  ink-spinner@5.0.0(ink@6.3.0(@types/react@19.3.0)(react@19.2.3))(react@19.2.3):
     dependencies:
-      micromark-util-character: 1.2.0
-      micromark-util-types: 1.1.0
+      cli-spinners: 2.9.2
+      ink: 6.3.0(@types/react@19.3.0)(react@19.2.3)
+      react: 19.2.3
 
-  micromark-factory-space@2.0.1:
+  ink@6.3.0(@types/react@19.3.0)(react@19.2.3):
     dependencies:
-      micromark-util-character: 2.1.1
-      micromark-util-types: 2.0.2
+      '@alcalzone/ansi-tokenize': 0.2.5
+      ansi-escapes: 7.3.0
+      ansi-styles: 6.2.3
+      auto-bind: 5.0.1
+      chalk: 5.6.2
+      cli-boxes: 3.0.0
+      cli-cursor: 4.0.0
+      cli-truncate: 4.0.0
+      code-excerpt: 4.0.0
+      es-toolkit: 1.52.0
+      indent-string: 5.0.0
+      is-in-ci: 2.0.0
+      patch-console: 2.0.0
+      react: 19.2.3
+      react-reconciler: 0.32.0(react@19.2.3)
+      signal-exit: 3.0.7
+      slice-ansi: 7.1.2
+      stack-utils: 2.0.6
+      string-width: 7.2.0
+      type-fest: 4.41.0
+      widest-line: 5.0.0
+      wrap-ansi: 9.0.2
+      ws: 8.22.0
+      yoga-layout: 3.2.1
+    optionalDependencies:
+      '@types/react': 19.3.0
+    transitivePeerDependencies:
+      - bufferutil
+      - utf-8-validate
 
-  micromark-factory-title@1.1.0:
-    dependencies:
-      micromark-factory-space: 1.1.0
-      micromark-util-character: 1.2.0
-      micromark-util-symbol: 1.1.0
-      micromark-util-types: 1.1.0
+  inline-style-parser@0.1.1: {}
 
-  micromark-factory-title@2.0.1:
-    dependencies:
-      micromark-factory-space: 2.0.1
-      micromark-util-character: 2.1.1
-      micromark-util-symbol: 2.0.1
-      micromark-util-types: 2.0.2
+  inline-style-parser@0.2.7: {}
 
-  micromark-factory-whitespace@1.1.0:
+  inquirer@12.3.0(@types/node@26.6.5):
     dependencies:
-      micromark-factory-space: 1.1.0
-      micromark-util-character: 1.2.0
-      micromark-util-symbol: 1.1.0
-      micromark-util-types: 1.1.0
+      '@inquirer/core': 10.3.2(@types/node@26.6.5)
+      '@inquirer/prompts': 7.9.0(@types/node@26.6.5)
+      '@inquirer/type': 3.0.10(@types/node@26.6.5)
+      '@types/node': 26.6.5
+      ansi-escapes: 4.3.2
+      mute-stream: 2.0.0
+      run-async: 3.0.0
+      rxjs: 7.8.2
 
-  micromark-factory-whitespace@2.0.1:
+  internal-slot@1.1.0:
     dependencies:
-      micromark-factory-space: 2.0.1
-      micromark-util-character: 2.1.1
-      micromark-util-symbol: 2.0.1
-      micromark-util-types: 2.0.2
+      es-errors: 1.3.0
+      hasown: 2.0.4
+      side-channel: 1.1.1
 
-  micromark-util-character@1.2.0:
-    dependencies:
-      micromark-util-symbol: 1.1.0
-      micromark-util-types: 1.1.0
+  ip-regex@4.3.0: {}
 
-  micromark-util-character@2.1.1:
-    dependencies:
-      micromark-util-symbol: 2.0.1
-      micromark-util-types: 2.0.2
+  ipaddr.js@1.9.1: {}
 
-  micromark-util-chunked@1.1.0:
-    dependencies:
-      micromark-util-symbol: 1.1.0
+  iregexp-check@0.1.2: {}
 
-  micromark-util-chunked@2.0.1:
-    dependencies:
-      micromark-util-symbol: 2.0.1
+  is-alphabetical@2.0.1: {}
 
-  micromark-util-classify-character@1.1.0:
+  is-alphanumerical@2.0.1:
     dependencies:
-      micromark-util-character: 1.2.0
-      micromark-util-symbol: 1.1.0
-      micromark-util-types: 1.1.0
+      is-alphabetical: 2.0.1
+      is-decimal: 2.0.1
 
-  micromark-util-classify-character@2.0.1:
+  is-array-buffer@3.0.5:
     dependencies:
-      micromark-util-character: 2.1.1
-      micromark-util-symbol: 2.0.1
-      micromark-util-types: 2.0.2
+      call-bind: 1.0.9
+      call-bound: 1.0.4
+      get-intrinsic: 1.3.0
 
-  micromark-util-combine-extensions@1.1.0:
-    dependencies:
-      micromark-util-chunked: 1.1.0
-      micromark-util-types: 1.1.0
+  is-arrayish@0.3.4: {}
 
-  micromark-util-combine-extensions@2.0.1:
+  is-async-function@2.1.1:
     dependencies:
-      micromark-util-chunked: 2.0.1
-      micromark-util-types: 2.0.2
+      async-function: 1.0.0
+      call-bound: 1.0.4
+      get-proto: 1.0.1
+      has-tostringtag: 1.0.2
+      safe-regex-test: 1.1.0
 
-  micromark-util-decode-numeric-character-reference@1.1.0:
+  is-bigint@1.1.0:
     dependencies:
-      micromark-util-symbol: 1.1.0
+      has-bigints: 1.1.0
 
-  micromark-util-decode-numeric-character-reference@2.0.2:
+  is-binary-path@2.1.0:
     dependencies:
-      micromark-util-symbol: 2.0.1
+      binary-extensions: 2.3.0
 
-  micromark-util-decode-string@1.1.0:
+  is-boolean-object@1.2.2:
     dependencies:
-      decode-named-character-reference: 1.3.0
-      micromark-util-character: 1.2.0
-      micromark-util-decode-numeric-character-reference: 1.1.0
-      micromark-util-symbol: 1.1.0
+      call-bound: 1.0.4
+      has-tostringtag: 1.0.2
 
-  micromark-util-decode-string@2.0.1:
-    dependencies:
-      decode-named-character-reference: 1.3.0
-      micromark-util-character: 2.1.1
-      micromark-util-decode-numeric-character-reference: 2.0.2
-      micromark-util-symbol: 2.0.1
+  is-callable@1.2.7: {}
 
-  micromark-util-encode@1.1.0: {}
+  is-core-module@2.17.0:
+    dependencies:
+      hasown: 2.0.4
 
-  micromark-util-encode@2.0.1: {}
+  is-data-view@1.0.2:
+    dependencies:
+      call-bound: 1.0.4
+      get-intrinsic: 1.3.0
+      is-typed-array: 1.1.15
 
-  micromark-util-events-to-acorn@2.0.3:
+  is-date-object@1.1.0:
     dependencies:
-      '@types/estree': 1.0.9
-      '@types/unist': 3.0.3
-      devlop: 1.1.0
-      estree-util-visit: 2.0.0
-      micromark-util-symbol: 2.0.1
-      micromark-util-types: 2.0.2
-      vfile-message: 4.0.3
+      call-bound: 1.0.4
+      has-tostringtag: 1.0.2
 
-  micromark-util-html-tag-name@1.2.0: {}
+  is-decimal@2.0.1: {}
 
-  micromark-util-html-tag-name@2.0.1: {}
+  is-docker@2.2.1: {}
 
-  micromark-util-normalize-identifier@1.1.0:
+  is-document.all@1.0.0:
     dependencies:
-      micromark-util-symbol: 1.1.0
+      call-bound: 1.0.4
 
-  micromark-util-normalize-identifier@2.0.1:
-    dependencies:
-      micromark-util-symbol: 2.0.1
+  is-extglob@2.1.1: {}
 
-  micromark-util-resolve-all@1.1.0:
+  is-finalizationregistry@1.1.1:
     dependencies:
-      micromark-util-types: 1.1.0
+      call-bound: 1.0.4
 
-  micromark-util-resolve-all@2.0.1:
-    dependencies:
-      micromark-util-types: 2.0.2
+  is-fullwidth-code-point@3.0.0: {}
 
-  micromark-util-sanitize-uri@1.2.0:
-    dependencies:
-      micromark-util-character: 1.2.0
-      micromark-util-encode: 1.1.0
-      micromark-util-symbol: 1.1.0
+  is-fullwidth-code-point@4.0.0: {}
 
-  micromark-util-sanitize-uri@2.0.1:
+  is-fullwidth-code-point@5.1.0:
     dependencies:
-      micromark-util-character: 2.1.1
-      micromark-util-encode: 2.0.1
-      micromark-util-symbol: 2.0.1
+      get-east-asian-width: 1.6.0
 
-  micromark-util-subtokenize@1.1.0:
+  is-generator-function@1.1.2:
     dependencies:
-      micromark-util-chunked: 1.1.0
-      micromark-util-symbol: 1.1.0
-      micromark-util-types: 1.1.0
-      uvu: 0.5.6
+      call-bound: 1.0.4
+      generator-function: 2.0.1
+      get-proto: 1.0.1
+      has-tostringtag: 1.0.2
+      safe-regex-test: 1.1.0
 
-  micromark-util-subtokenize@2.1.0:
+  is-glob@4.0.3:
     dependencies:
-      devlop: 1.1.0
-      micromark-util-chunked: 2.0.1
-      micromark-util-symbol: 2.0.1
-      micromark-util-types: 2.0.2
+      is-extglob: 2.1.1
 
-  micromark-util-symbol@1.1.0: {}
+  is-hexadecimal@2.0.1: {}
 
-  micromark-util-symbol@2.0.1: {}
+  is-in-ci@2.0.0: {}
 
-  micromark-util-types@1.1.0: {}
+  is-ip@3.1.0:
+    dependencies:
+      ip-regex: 4.3.0
 
-  micromark-util-types@2.0.2: {}
+  is-map@2.0.3: {}
 
-  micromark@2.11.4:
-    dependencies:
-      debug: 4.4.3
-      parse-entities: 2.0.0
-    transitivePeerDependencies:
-      - supports-color
+  is-negative-zero@2.0.3: {}
 
-  micromark@3.2.0:
+  is-number-object@1.1.1:
     dependencies:
-      '@types/debug': 4.1.13
-      debug: 4.4.3
-      decode-named-character-reference: 1.3.0
-      micromark-core-commonmark: 1.1.0
-      micromark-factory-space: 1.1.0
-      micromark-util-character: 1.2.0
-      micromark-util-chunked: 1.1.0
-      micromark-util-combine-extensions: 1.1.0
-      micromark-util-decode-numeric-character-reference: 1.1.0
-      micromark-util-encode: 1.1.0
-      micromark-util-normalize-identifier: 1.1.0
-      micromark-util-resolve-all: 1.1.0
-      micromark-util-sanitize-uri: 1.2.0
-      micromark-util-subtokenize: 1.1.0
-      micromark-util-symbol: 1.1.0
-      micromark-util-types: 1.1.0
-      uvu: 0.5.6
-    transitivePeerDependencies:
-      - supports-color
+      call-bound: 1.0.4
+      has-tostringtag: 1.0.2
 
-  micromark@4.0.2:
-    dependencies:
-      '@types/debug': 4.1.13
-      debug: 4.4.3
-      decode-named-character-reference: 1.3.0
-      devlop: 1.1.0
-      micromark-core-commonmark: 2.0.3
-      micromark-factory-space: 2.0.1
-      micromark-util-character: 2.1.1
-      micromark-util-chunked: 2.0.1
-      micromark-util-combine-extensions: 2.0.1
-      micromark-util-decode-numeric-character-reference: 2.0.2
-      micromark-util-encode: 2.0.1
-      micromark-util-normalize-identifier: 2.0.1
-      micromark-util-resolve-all: 2.0.1
-      micromark-util-sanitize-uri: 2.0.1
-      micromark-util-subtokenize: 2.1.0
-      micromark-util-symbol: 2.0.1
-      micromark-util-types: 2.0.2
-    transitivePeerDependencies:
-      - supports-color
+  is-number@7.0.0: {}
 
-  micromatch@4.0.8:
+  is-online@10.0.0:
     dependencies:
-      braces: 3.0.3
-      picomatch: 2.3.2
+      got: 12.6.1
+      p-any: 4.0.0
+      p-timeout: 5.1.0
+      public-ip: 5.0.0
 
-  mime-db@1.33.0: {}
+  is-plain-obj@4.1.0: {}
 
-  mime-db@1.52.0: {}
+  is-regex@1.2.1:
+    dependencies:
+      call-bound: 1.0.4
+      gopd: 1.2.0
+      has-tostringtag: 1.0.2
+      hasown: 2.0.4
 
-  mime-db@1.54.0: {}
+  is-set@2.0.3: {}
 
-  mime-format@2.0.2:
+  is-shared-array-buffer@1.0.4:
     dependencies:
-      charset: 1.0.1
+      call-bound: 1.0.4
 
-  mime-types@2.1.18:
+  is-string@1.1.1:
     dependencies:
-      mime-db: 1.33.0
+      call-bound: 1.0.4
+      has-tostringtag: 1.0.2
 
-  mime-types@2.1.35:
+  is-symbol@1.1.1:
     dependencies:
-      mime-db: 1.52.0
+      call-bound: 1.0.4
+      has-symbols: 1.1.0
+      safe-regex-test: 1.1.0
 
-  mime-types@3.0.2:
+  is-typed-array@1.1.15:
     dependencies:
-      mime-db: 1.54.0
+      which-typed-array: 1.1.24
 
-  mime@1.6.0: {}
+  is-url@1.2.4: {}
 
-  mime@3.0.0: {}
+  is-weakmap@2.0.2: {}
 
-  mimic-fn@2.1.0: {}
+  is-weakref@1.1.1:
+    dependencies:
+      call-bound: 1.0.4
 
-  mimic-response@3.1.0: {}
+  is-weakset@2.0.4:
+    dependencies:
+      call-bound: 1.0.4
+      get-intrinsic: 1.3.0
 
-  mimic-response@4.0.0: {}
+  is-wsl@2.2.0:
+    dependencies:
+      is-docker: 2.2.1
+
+  isarray@2.0.5: {}
+
+  isexe@2.0.0: {}
 
-  mini-css-extract-plugin@2.10.2(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)):
+  isomorphic-fetch@3.0.0:
     dependencies:
-      schema-utils: 4.3.3
-      tapable: 2.3.3
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
+      node-fetch: 2.7.0
+      whatwg-fetch: 3.6.20
+    transitivePeerDependencies:
+      - encoding
+
+  jiti@1.21.7: {}
+
+  jose@6.2.12: {}
 
-  minimalistic-assert@1.0.1: {}
+  js-tokens@4.0.0: {}
 
-  minimatch@10.2.5:
+  js-yaml@3.15.2:
     dependencies:
-      brace-expansion: 5.0.7
+      argparse: 1.0.10
+      esprima: 4.0.1
 
-  minimatch@3.1.5:
+  js-yaml@4.3.1:
     dependencies:
-      brace-expansion: 1.1.15
+      argparse: 2.0.1
+
+  jsep@1.6.0: {}
+
+  json-buffer@3.0.1: {}
+
+  json-p3@2.2.2: {}
 
-  minimatch@9.0.9:
+  json-schema-compare@0.2.2:
     dependencies:
-      brace-expansion: 2.1.1
+      lodash: 4.18.1
 
-  minimist@1.2.8: {}
+  json-schema-merge-allof@0.8.1:
+    dependencies:
+      compute-lcm: 1.1.2
+      json-schema-compare: 0.2.2
+      lodash: 4.18.1
 
-  minipass@7.1.3: {}
+  json-schema-traverse@0.4.1: {}
 
-  mri@1.2.0: {}
+  json-schema-traverse@1.0.0: {}
 
-  mrmime@2.0.1: {}
+  jsonc-parser@2.2.1: {}
 
-  ms@2.0.0: {}
+  jsonfile@6.2.1:
+    dependencies:
+      universalify: 2.0.1
+    optionalDependencies:
+      graceful-fs: 4.2.11
 
-  ms@2.1.3: {}
+  jsonpath-plus@10.4.0:
+    dependencies:
+      '@jsep-plugin/assignment': 1.4.0(jsep@1.6.0)
+      '@jsep-plugin/regex': 1.1.0(jsep@1.6.0)
+      jsep: 1.6.0
+
+  jsonpointer@5.0.1: {}
 
-  multicast-dns@7.2.5:
+  katex@0.16.47:
     dependencies:
-      dns-packet: 5.6.1
-      thunky: 1.1.0
+      commander: 8.3.0
 
-  mustache@4.2.0: {}
+  keytar@7.9.0:
+    dependencies:
+      node-addon-api: 4.3.0
+      prebuild-install: 7.1.3
+    optional: true
 
-  mz@2.7.0:
+  keyv@4.5.4:
     dependencies:
-      any-promise: 1.3.0
-      object-assign: 4.1.1
-      thenify-all: 1.6.0
+      json-buffer: 3.0.1
 
-  nano-css@5.6.2(react-dom@19.2.7(react@19.2.7))(react@19.2.7):
+  lcm@0.0.3:
     dependencies:
-      '@jridgewell/sourcemap-codec': 1.5.5
-      css-tree: 1.1.3
-      csstype: 3.2.3
-      fastest-stable-stringify: 2.0.2
-      inline-style-prefixer: 7.0.1
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      rtl-css-js: 1.16.1
-      stacktrace-js: 2.0.2
-      stylis: 4.4.0
+      gcd: 0.0.1
+
+  leven@3.1.0: {}
 
-  nano-memoize@1.3.1: {}
+  leven@4.1.0: {}
 
-  nanoid@3.3.12: {}
+  lilconfig@3.1.4: {}
 
-  natural-compare@1.4.0: {}
+  linebreak@1.1.0:
+    dependencies:
+      base64-js: 0.0.8
+      unicode-trie: 2.0.0
 
-  negotiator@0.6.3: {}
+  lines-and-columns@1.2.4: {}
+
+  lodash.topath@4.5.2: {}
+
+  lodash@4.18.1: {}
+
+  longest-streak@3.1.0: {}
+
+  lowercase-keys@3.0.0: {}
+
+  markdown-extensions@2.0.0: {}
 
-  negotiator@0.6.4: {}
+  markdown-table@3.0.4: {}
 
-  neo-async@2.6.2: {}
+  math-intrinsics@1.1.0: {}
 
-  neotraverse@0.6.15: {}
+  mdast-util-find-and-replace@3.0.3:
+    dependencies:
+      '@types/mdast': 4.0.4
+      escape-string-regexp: 5.0.0
+      unist-util-is: 6.0.1
+      unist-util-visit-parents: 6.0.1
 
-  no-case@3.0.4:
+  mdast-util-from-markdown@2.0.2:
     dependencies:
-      lower-case: 2.0.2
-      tslib: 2.8.1
+      '@types/mdast': 4.0.4
+      '@types/unist': 3.0.3
+      decode-named-character-reference: 1.3.0
+      devlop: 1.1.0
+      mdast-util-to-string: 4.0.0
+      micromark: 4.0.3
+      micromark-util-decode-numeric-character-reference: 2.0.2
+      micromark-util-decode-string: 2.0.1
+      micromark-util-normalize-identifier: 2.0.1
+      micromark-util-symbol: 2.0.1
+      micromark-util-types: 2.0.3
+      unist-util-stringify-position: 4.0.0
+    transitivePeerDependencies:
+      - supports-color
 
-  node-addon-api@7.1.1:
-    optional: true
+  mdast-util-from-markdown@2.1.0:
+    dependencies:
+      '@types/mdast': 4.0.4
+      '@types/unist': 3.0.3
+      decode-named-character-reference: 1.3.0
+      devlop: 1.1.0
+      mdast-util-to-string: 4.0.0
+      micromark: 4.0.3
+      micromark-util-decode-numeric-character-reference: 2.0.2
+      micromark-util-decode-string: 2.0.1
+      micromark-util-normalize-identifier: 2.0.1
+      micromark-util-symbol: 2.0.1
+      micromark-util-types: 2.0.3
+      unist-util-stringify-position: 4.0.0
+    transitivePeerDependencies:
+      - supports-color
 
-  node-emoji@2.2.0:
+  mdast-util-frontmatter@2.0.1:
     dependencies:
-      '@sindresorhus/is': 4.6.0
-      char-regex: 1.0.2
-      emojilib: 2.4.0
-      skin-tone: 2.0.0
+      '@types/mdast': 4.0.4
+      devlop: 1.1.0
+      escape-string-regexp: 5.0.0
+      mdast-util-from-markdown: 2.1.0
+      mdast-util-to-markdown: 2.2.0
+      micromark-extension-frontmatter: 2.0.0
+    transitivePeerDependencies:
+      - supports-color
 
-  node-fetch-h2@2.3.0:
+  mdast-util-gfm-autolink-literal@2.0.1:
     dependencies:
-      http2-client: 1.3.5
+      '@types/mdast': 4.0.4
+      ccount: 2.0.1
+      devlop: 1.1.0
+      mdast-util-find-and-replace: 3.0.3
+      micromark-util-character: 2.1.1
 
-  node-fetch@2.7.0:
+  mdast-util-gfm-footnote@2.1.0:
     dependencies:
-      whatwg-url: 5.0.0
+      '@types/mdast': 4.0.4
+      devlop: 1.1.0
+      mdast-util-from-markdown: 2.0.2
+      mdast-util-to-markdown: 2.2.0
+      micromark-util-normalize-identifier: 2.0.1
+    transitivePeerDependencies:
+      - supports-color
 
-  node-readfiles@0.2.0:
+  mdast-util-gfm-strikethrough@2.0.1:
     dependencies:
-      es6-promise: 3.3.1
+      '@types/mdast': 4.0.4
+      mdast-util-from-markdown: 2.0.2
+      mdast-util-to-markdown: 2.2.0
+    transitivePeerDependencies:
+      - supports-color
 
-  node-releases@2.0.47: {}
+  mdast-util-gfm-table@2.0.0:
+    dependencies:
+      '@types/mdast': 4.0.4
+      devlop: 1.1.0
+      markdown-table: 3.0.4
+      mdast-util-from-markdown: 2.0.2
+      mdast-util-to-markdown: 2.2.0
+    transitivePeerDependencies:
+      - supports-color
 
-  normalize-path@3.0.0: {}
+  mdast-util-gfm-task-list-item@2.0.0:
+    dependencies:
+      '@types/mdast': 4.0.4
+      devlop: 1.1.0
+      mdast-util-from-markdown: 2.0.2
+      mdast-util-to-markdown: 2.2.0
+    transitivePeerDependencies:
+      - supports-color
 
-  normalize-url@8.1.1: {}
+  mdast-util-gfm@3.0.0:
+    dependencies:
+      mdast-util-from-markdown: 2.0.2
+      mdast-util-gfm-autolink-literal: 2.0.1
+      mdast-util-gfm-footnote: 2.1.0
+      mdast-util-gfm-strikethrough: 2.0.1
+      mdast-util-gfm-table: 2.0.0
+      mdast-util-gfm-task-list-item: 2.0.0
+      mdast-util-to-markdown: 2.2.0
+    transitivePeerDependencies:
+      - supports-color
 
-  npm-run-path@4.0.1:
+  mdast-util-gfm@3.1.0:
     dependencies:
-      path-key: 3.1.1
+      mdast-util-from-markdown: 2.1.0
+      mdast-util-gfm-autolink-literal: 2.0.1
+      mdast-util-gfm-footnote: 2.1.0
+      mdast-util-gfm-strikethrough: 2.0.1
+      mdast-util-gfm-table: 2.0.0
+      mdast-util-gfm-task-list-item: 2.0.0
+      mdast-util-to-markdown: 2.2.0
+    transitivePeerDependencies:
+      - supports-color
 
-  npm-to-yarn@3.0.1: {}
+  mdast-util-math@3.0.0:
+    dependencies:
+      '@types/hast': 3.0.5
+      '@types/mdast': 4.0.4
+      devlop: 1.1.0
+      longest-streak: 3.1.0
+      mdast-util-from-markdown: 2.1.0
+      mdast-util-to-markdown: 2.2.0
+      unist-util-remove-position: 5.0.0
+    transitivePeerDependencies:
+      - supports-color
 
-  nprogress@0.2.0: {}
+  mdast-util-mdx-expression@2.0.1:
+    dependencies:
+      '@types/estree-jsx': 1.0.5
+      '@types/hast': 3.0.5
+      '@types/mdast': 4.0.4
+      devlop: 1.1.0
+      mdast-util-from-markdown: 2.0.2
+      mdast-util-to-markdown: 2.2.0
+    transitivePeerDependencies:
+      - supports-color
 
-  nth-check@2.1.1:
+  mdast-util-mdx-jsx@3.1.3:
     dependencies:
-      boolbase: 1.0.0
+      '@types/estree-jsx': 1.0.5
+      '@types/hast': 3.0.5
+      '@types/mdast': 4.0.4
+      '@types/unist': 3.0.3
+      ccount: 2.0.1
+      devlop: 1.1.0
+      mdast-util-from-markdown: 2.0.2
+      mdast-util-to-markdown: 2.2.0
+      parse-entities: 4.0.2
+      stringify-entities: 4.0.4
+      unist-util-stringify-position: 4.0.0
+      vfile-message: 4.0.3
+    transitivePeerDependencies:
+      - supports-color
 
-  null-loader@4.0.1(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)):
+  mdast-util-mdx-jsx@3.2.0:
     dependencies:
-      loader-utils: 2.0.4
-      schema-utils: 3.3.0
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
+      '@types/estree-jsx': 1.0.5
+      '@types/hast': 3.0.5
+      '@types/mdast': 4.0.4
+      '@types/unist': 3.0.3
+      ccount: 2.0.1
+      devlop: 1.1.0
+      mdast-util-from-markdown: 2.1.0
+      mdast-util-to-markdown: 2.2.0
+      parse-entities: 4.0.2
+      stringify-entities: 4.0.4
+      unist-util-stringify-position: 4.0.0
+      vfile-message: 4.0.3
+    transitivePeerDependencies:
+      - supports-color
 
-  oas-kit-common@1.0.8:
+  mdast-util-mdx@3.0.0:
     dependencies:
-      fast-safe-stringify: 2.1.1
+      mdast-util-from-markdown: 2.0.2
+      mdast-util-mdx-expression: 2.0.1
+      mdast-util-mdx-jsx: 3.2.0
+      mdast-util-mdxjs-esm: 2.0.1
+      mdast-util-to-markdown: 2.2.0
+    transitivePeerDependencies:
+      - supports-color
 
-  oas-linter@3.2.2:
+  mdast-util-mdxjs-esm@2.0.1:
     dependencies:
-      '@exodus/schemasafe': 1.3.0
-      should: 13.2.3
-      yaml: 1.10.3
+      '@types/estree-jsx': 1.0.5
+      '@types/hast': 3.0.5
+      '@types/mdast': 4.0.4
+      devlop: 1.1.0
+      mdast-util-from-markdown: 2.0.2
+      mdast-util-to-markdown: 2.2.0
+    transitivePeerDependencies:
+      - supports-color
 
-  oas-resolver-browser@2.5.6:
+  mdast-util-phrasing@4.1.0:
     dependencies:
-      node-fetch-h2: 2.3.0
-      oas-kit-common: 1.0.8
-      path-browserify: 1.0.1
-      reftools: 1.1.9
-      yaml: 1.10.2
-      yargs: 17.7.3
+      '@types/mdast': 4.0.4
+      unist-util-is: 6.0.1
 
-  oas-resolver@2.5.6:
+  mdast-util-to-hast@13.2.1:
     dependencies:
-      node-fetch-h2: 2.3.0
-      oas-kit-common: 1.0.8
-      reftools: 1.1.9
-      yaml: 1.10.3
-      yargs: 17.7.3
+      '@types/hast': 3.0.5
+      '@types/mdast': 4.0.4
+      '@ungap/structured-clone': 1.4.0
+      devlop: 1.1.0
+      micromark-util-sanitize-uri: 2.0.1
+      trim-lines: 3.0.1
+      unist-util-position: 5.0.0
+      unist-util-visit: 5.0.0
+      vfile: 6.0.3
 
-  oas-schema-walker@1.1.5: {}
+  mdast-util-to-markdown@2.2.0:
+    dependencies:
+      '@types/mdast': 4.0.4
+      '@types/unist': 3.0.3
+      longest-streak: 3.1.0
+      mdast-util-phrasing: 4.1.0
+      mdast-util-to-string: 4.0.0
+      micromark-util-character: 2.1.1
+      micromark-util-classify-character: 2.0.1
+      micromark-util-decode-string: 2.0.1
+      micromark-util-html-tag-name: 2.0.1
+      unist-util-visit: 5.0.0
+      zwitch: 2.0.4
 
-  oas-validator@5.0.8:
+  mdast-util-to-string@4.0.0:
     dependencies:
-      call-me-maybe: 1.0.2
-      oas-kit-common: 1.0.8
-      oas-linter: 3.2.2
-      oas-resolver: 2.5.6
-      oas-schema-walker: 1.1.5
-      reftools: 1.1.9
-      should: 13.2.3
-      yaml: 1.10.3
+      '@types/mdast': 4.0.4
 
-  object-assign@4.1.1: {}
+  media-typer@0.3.0: {}
 
-  object-hash@3.0.0: {}
+  merge-descriptors@1.0.3: {}
 
-  object-inspect@1.13.4: {}
+  merge2@1.4.1: {}
 
-  object-keys@1.1.1: {}
+  methods@1.1.2: {}
 
-  object.assign@4.1.7:
+  micromark-core-commonmark@2.0.4:
     dependencies:
-      call-bind: 1.0.9
-      call-bound: 1.0.4
-      define-properties: 1.2.1
-      es-object-atoms: 1.1.2
-      has-symbols: 1.1.0
-      object-keys: 1.1.1
-
-  obuf@1.1.2: {}
+      decode-named-character-reference: 1.3.0
+      devlop: 1.1.0
+      micromark-factory-destination: 2.0.1
+      micromark-factory-label: 2.0.1
+      micromark-factory-space: 2.1.0
+      micromark-factory-title: 2.0.1
+      micromark-factory-whitespace: 2.0.1
+      micromark-util-character: 2.1.1
+      micromark-util-chunked: 2.0.1
+      micromark-util-classify-character: 2.0.1
+      micromark-util-edit-map: 1.0.0
+      micromark-util-html-tag-name: 2.0.1
+      micromark-util-normalize-identifier: 2.0.1
+      micromark-util-resolve-all: 2.0.1
+      micromark-util-subtokenize: 2.1.0
+      micromark-util-symbol: 2.0.1
+      micromark-util-types: 2.0.3
 
-  on-finished@2.4.1:
+  micromark-extension-frontmatter@2.0.0:
     dependencies:
-      ee-first: 1.1.1
-
-  on-headers@1.1.0: {}
+      fault: 2.0.1
+      micromark-util-character: 2.1.1
+      micromark-util-symbol: 2.0.1
+      micromark-util-types: 2.0.3
 
-  once@1.4.0:
+  micromark-extension-gfm-autolink-literal@2.1.0:
     dependencies:
-      wrappy: 1.0.2
+      micromark-util-character: 2.1.1
+      micromark-util-sanitize-uri: 2.0.1
+      micromark-util-symbol: 2.0.1
+      micromark-util-types: 2.0.3
 
-  onetime@5.1.2:
+  micromark-extension-gfm-footnote@2.1.0:
     dependencies:
-      mimic-fn: 2.1.0
+      devlop: 1.1.0
+      micromark-core-commonmark: 2.0.4
+      micromark-factory-space: 2.1.0
+      micromark-util-character: 2.1.1
+      micromark-util-normalize-identifier: 2.0.1
+      micromark-util-sanitize-uri: 2.0.1
+      micromark-util-symbol: 2.0.1
+      micromark-util-types: 2.0.3
 
-  open@10.2.0:
+  micromark-extension-gfm-strikethrough@2.1.0:
     dependencies:
-      default-browser: 5.5.0
-      define-lazy-prop: 3.0.0
-      is-inside-container: 1.0.0
-      wsl-utils: 0.1.0
+      devlop: 1.1.0
+      micromark-util-chunked: 2.0.1
+      micromark-util-classify-character: 2.0.1
+      micromark-util-resolve-all: 2.0.1
+      micromark-util-symbol: 2.0.1
+      micromark-util-types: 2.0.3
 
-  open@8.4.2:
+  micromark-extension-gfm-table@2.1.2:
     dependencies:
-      define-lazy-prop: 2.0.0
-      is-docker: 2.2.1
-      is-wsl: 2.2.0
+      devlop: 1.1.0
+      micromark-factory-space: 2.1.0
+      micromark-util-character: 2.1.1
+      micromark-util-symbol: 2.0.1
+      micromark-util-types: 2.0.3
 
-  openapi-to-postmanv2@6.2.0:
+  micromark-extension-gfm-tagfilter@2.0.0:
     dependencies:
-      ajv: 8.20.0
-      ajv-draft-04: 1.0.0(ajv@8.20.0)
-      ajv-formats: 2.1.1(ajv@8.20.0)
-      async: 3.2.6
-      commander: 2.20.3
-      graphlib: 2.1.8
-      js-yaml: 4.1.0
-      json-pointer: 0.6.2
-      json-schema-merge-allof: 0.8.1
-      lodash: 4.17.21
-      neotraverse: 0.6.15
-      oas-resolver-browser: 2.5.6
-      object-hash: 3.0.0
-      openapi-types: 12.1.3
-      path-browserify: 1.0.1
-      postman-collection: 5.3.0
-      swagger2openapi: 7.0.8
-      yaml: 1.10.2
-    transitivePeerDependencies:
-      - encoding
-
-  openapi-types@12.1.3: {}
+      micromark-util-types: 2.0.3
 
-  opener@1.5.2: {}
-
-  optionator@0.9.4:
+  micromark-extension-gfm-task-list-item@2.1.0:
     dependencies:
-      deep-is: 0.1.4
-      fast-levenshtein: 2.0.6
-      levn: 0.4.1
-      prelude-ls: 1.2.1
-      type-check: 0.4.0
-      word-wrap: 1.2.5
-
-  p-cancelable@3.0.0: {}
-
-  p-finally@1.0.0: {}
+      devlop: 1.1.0
+      micromark-factory-space: 2.1.0
+      micromark-util-character: 2.1.1
+      micromark-util-symbol: 2.0.1
+      micromark-util-types: 2.0.3
 
-  p-limit@3.1.0:
+  micromark-extension-gfm@3.0.0:
     dependencies:
-      yocto-queue: 0.1.0
+      micromark-extension-gfm-autolink-literal: 2.1.0
+      micromark-extension-gfm-footnote: 2.1.0
+      micromark-extension-gfm-strikethrough: 2.1.0
+      micromark-extension-gfm-table: 2.1.2
+      micromark-extension-gfm-tagfilter: 2.0.0
+      micromark-extension-gfm-task-list-item: 2.1.0
+      micromark-util-combine-extensions: 2.0.1
+      micromark-util-types: 2.0.3
 
-  p-limit@4.0.0:
+  micromark-extension-math@3.1.0:
     dependencies:
-      yocto-queue: 1.2.2
+      '@types/katex': 0.16.8
+      devlop: 1.1.0
+      katex: 0.16.47
+      micromark-factory-space: 2.1.0
+      micromark-util-character: 2.1.1
+      micromark-util-symbol: 2.0.1
+      micromark-util-types: 2.0.3
 
-  p-locate@5.0.0:
+  micromark-extension-mdx-expression@3.0.1:
     dependencies:
-      p-limit: 3.1.0
+      '@types/estree': 1.0.9
+      devlop: 1.1.0
+      micromark-factory-mdx-expression: 2.0.3
+      micromark-factory-space: 2.1.0
+      micromark-util-character: 2.1.1
+      micromark-util-events-to-acorn: 2.0.3
+      micromark-util-symbol: 2.0.1
+      micromark-util-types: 2.0.3
 
-  p-locate@6.0.0:
+  micromark-extension-mdx-jsx@3.0.2:
     dependencies:
-      p-limit: 4.0.0
+      '@types/estree': 1.0.9
+      devlop: 1.1.0
+      estree-util-is-identifier-name: 3.0.0
+      micromark-factory-mdx-expression: 2.0.3
+      micromark-factory-space: 2.1.0
+      micromark-util-character: 2.1.1
+      micromark-util-events-to-acorn: 2.0.3
+      micromark-util-symbol: 2.0.1
+      micromark-util-types: 2.0.3
+      vfile-message: 4.0.3
 
-  p-map@4.0.0:
+  micromark-extension-mdx-md@2.0.0:
     dependencies:
-      aggregate-error: 3.1.0
+      micromark-util-types: 2.0.3
 
-  p-queue@6.6.2:
+  micromark-extension-mdxjs-esm@3.0.0:
     dependencies:
-      eventemitter3: 4.0.7
-      p-timeout: 3.2.0
+      '@types/estree': 1.0.9
+      devlop: 1.1.0
+      micromark-core-commonmark: 2.0.4
+      micromark-util-character: 2.1.1
+      micromark-util-events-to-acorn: 2.0.3
+      micromark-util-symbol: 2.0.1
+      micromark-util-types: 2.0.3
+      unist-util-position-from-estree: 2.0.0
+      vfile-message: 4.0.3
 
-  p-retry@6.2.1:
+  micromark-extension-mdxjs@3.0.0:
     dependencies:
-      '@types/retry': 0.12.2
-      is-network-error: 1.3.2
-      retry: 0.13.1
+      acorn: 8.11.2
+      acorn-jsx: 5.3.2(acorn@8.11.2)
+      micromark-extension-mdx-expression: 3.0.1
+      micromark-extension-mdx-jsx: 3.0.2
+      micromark-extension-mdx-md: 2.0.0
+      micromark-extension-mdxjs-esm: 3.0.0
+      micromark-util-combine-extensions: 2.0.1
+      micromark-util-types: 2.0.3
 
-  p-timeout@3.2.0:
+  micromark-factory-destination@2.0.1:
     dependencies:
-      p-finally: 1.0.0
+      micromark-util-character: 2.1.1
+      micromark-util-symbol: 2.0.1
+      micromark-util-types: 2.0.3
 
-  package-json@8.1.1:
+  micromark-factory-label@2.0.1:
     dependencies:
-      got: 12.6.1
-      registry-auth-token: 5.1.1
-      registry-url: 6.0.1
-      semver: 7.8.3
-
-  package-manager-detector@1.6.0: {}
-
-  pako@2.2.0: {}
+      devlop: 1.1.0
+      micromark-util-character: 2.1.1
+      micromark-util-symbol: 2.0.1
+      micromark-util-types: 2.0.3
 
-  param-case@3.0.4:
+  micromark-factory-mdx-expression@2.0.3:
     dependencies:
-      dot-case: 3.0.4
-      tslib: 2.8.1
+      '@types/estree': 1.0.9
+      devlop: 1.1.0
+      micromark-factory-space: 2.1.0
+      micromark-util-character: 2.1.1
+      micromark-util-events-to-acorn: 2.0.3
+      micromark-util-symbol: 2.0.1
+      micromark-util-types: 2.0.3
+      unist-util-position-from-estree: 2.0.0
+      vfile-message: 4.0.3
 
-  parent-module@1.0.1:
+  micromark-factory-space@2.1.0:
     dependencies:
-      callsites: 3.1.0
+      micromark-util-character: 2.1.1
+      micromark-util-types: 2.0.3
 
-  parse-entities@2.0.0:
+  micromark-factory-title@2.0.1:
     dependencies:
-      character-entities: 1.2.4
-      character-entities-legacy: 1.1.4
-      character-reference-invalid: 1.1.4
-      is-alphanumerical: 1.0.4
-      is-decimal: 1.0.4
-      is-hexadecimal: 1.0.4
+      micromark-factory-space: 2.1.0
+      micromark-util-character: 2.1.1
+      micromark-util-symbol: 2.0.1
+      micromark-util-types: 2.0.3
 
-  parse-entities@4.0.2:
+  micromark-factory-whitespace@2.0.1:
     dependencies:
-      '@types/unist': 2.0.11
-      character-entities-legacy: 3.0.0
-      character-reference-invalid: 2.0.1
-      decode-named-character-reference: 1.3.0
-      is-alphanumerical: 2.0.1
-      is-decimal: 2.0.1
-      is-hexadecimal: 2.0.1
+      micromark-factory-space: 2.1.0
+      micromark-util-character: 2.1.1
+      micromark-util-symbol: 2.0.1
+      micromark-util-types: 2.0.3
 
-  parse-json@5.2.0:
+  micromark-util-character@2.1.1:
     dependencies:
-      '@babel/code-frame': 7.29.7
-      error-ex: 1.3.4
-      json-parse-even-better-errors: 2.3.1
-      lines-and-columns: 1.2.4
-
-  parse-numeric-range@1.3.0: {}
+      micromark-util-symbol: 2.0.1
+      micromark-util-types: 2.0.3
 
-  parse5-htmlparser2-tree-adapter@7.1.0:
+  micromark-util-chunked@2.0.1:
     dependencies:
-      domhandler: 5.0.3
-      parse5: 7.3.0
-
-  parse5@6.0.1: {}
+      micromark-util-symbol: 2.0.1
 
-  parse5@7.3.0:
+  micromark-util-classify-character@2.0.1:
     dependencies:
-      entities: 6.0.1
-
-  parseurl@1.3.3: {}
+      micromark-util-character: 2.1.1
+      micromark-util-symbol: 2.0.1
+      micromark-util-types: 2.0.3
 
-  pascal-case@3.1.2:
+  micromark-util-combine-extensions@2.0.1:
     dependencies:
-      no-case: 3.0.4
-      tslib: 2.8.1
-
-  path-browserify@1.0.1: {}
-
-  path-data-parser@0.1.0: {}
-
-  path-exists@4.0.0: {}
-
-  path-exists@5.0.0: {}
-
-  path-is-absolute@1.0.1: {}
-
-  path-is-inside@1.0.2: {}
-
-  path-key@3.1.1: {}
-
-  path-parse@1.0.7: {}
+      micromark-util-chunked: 2.0.1
+      micromark-util-types: 2.0.3
 
-  path-scurry@2.0.2:
+  micromark-util-decode-numeric-character-reference@2.0.2:
     dependencies:
-      lru-cache: 11.5.1
-      minipass: 7.1.3
-
-  path-to-regexp@0.1.13: {}
+      micromark-util-symbol: 2.0.1
 
-  path-to-regexp@1.9.0:
+  micromark-util-decode-string@2.0.1:
     dependencies:
-      isarray: 0.0.1
-
-  path-to-regexp@3.3.0: {}
-
-  path-type@4.0.0: {}
+      decode-named-character-reference: 1.3.0
+      micromark-util-character: 2.1.1
+      micromark-util-decode-numeric-character-reference: 2.0.2
+      micromark-util-symbol: 2.0.1
 
-  picocolors@1.1.1: {}
+  micromark-util-edit-map@1.0.0:
+    dependencies:
+      micromark-util-types: 2.0.3
 
-  picomatch@2.3.2: {}
+  micromark-util-encode@2.0.1: {}
 
-  picomatch@4.0.4: {}
+  micromark-util-events-to-acorn@2.0.3:
+    dependencies:
+      '@types/estree': 1.0.9
+      '@types/unist': 3.0.3
+      devlop: 1.1.0
+      estree-util-visit: 2.0.0
+      micromark-util-symbol: 2.0.1
+      micromark-util-types: 2.0.3
+      vfile-message: 4.0.3
 
-  pirates@4.0.7: {}
+  micromark-util-html-tag-name@2.0.1: {}
 
-  pkg-dir@7.0.0:
+  micromark-util-normalize-identifier@2.0.1:
     dependencies:
-      find-up: 6.3.0
+      micromark-util-symbol: 2.0.1
 
-  pkijs@3.4.0:
+  micromark-util-resolve-all@2.0.1:
     dependencies:
-      '@noble/hashes': 1.4.0
-      asn1js: 3.0.10
-      bytestreamjs: 2.0.1
-      pvtsutils: 1.3.6
-      pvutils: 1.1.5
-      tslib: 2.8.1
-
-  pluralize@8.0.0: {}
-
-  points-on-curve@0.2.0: {}
+      micromark-util-types: 2.0.3
 
-  points-on-path@0.2.1:
+  micromark-util-sanitize-uri@2.0.1:
     dependencies:
-      path-data-parser: 0.1.0
-      points-on-curve: 0.2.0
+      micromark-util-character: 2.1.1
+      micromark-util-encode: 2.0.1
+      micromark-util-symbol: 2.0.1
 
-  polished@4.3.1:
+  micromark-util-subtokenize@2.1.0:
     dependencies:
-      '@babel/runtime': 7.29.7
+      devlop: 1.1.0
+      micromark-util-chunked: 2.0.1
+      micromark-util-symbol: 2.0.1
+      micromark-util-types: 2.0.3
 
-  postcss-attribute-case-insensitive@7.0.1(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
-      postcss-selector-parser: 7.1.2
+  micromark-util-symbol@2.0.1: {}
 
-  postcss-calc@9.0.1(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
-      postcss-selector-parser: 6.1.2
-      postcss-value-parser: 4.2.0
+  micromark-util-types@2.0.3: {}
 
-  postcss-clamp@4.1.0(postcss@8.5.15):
+  micromark@4.0.3:
     dependencies:
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+      '@types/debug': 4.1.13
+      debug: 4.4.3
+      decode-named-character-reference: 1.3.0
+      devlop: 1.1.0
+      micromark-core-commonmark: 2.0.4
+      micromark-factory-space: 2.1.0
+      micromark-util-character: 2.1.1
+      micromark-util-chunked: 2.0.1
+      micromark-util-combine-extensions: 2.0.1
+      micromark-util-decode-numeric-character-reference: 2.0.2
+      micromark-util-edit-map: 1.0.0
+      micromark-util-encode: 2.0.1
+      micromark-util-normalize-identifier: 2.0.1
+      micromark-util-resolve-all: 2.0.1
+      micromark-util-sanitize-uri: 2.0.1
+      micromark-util-subtokenize: 2.1.0
+      micromark-util-symbol: 2.0.1
+      micromark-util-types: 2.0.3
+    transitivePeerDependencies:
+      - supports-color
 
-  postcss-color-functional-notation@7.0.12(postcss@8.5.15):
+  micromatch@4.0.8:
     dependencies:
-      '@csstools/css-color-parser': 3.1.0(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      '@csstools/postcss-progressive-custom-properties': 4.2.1(postcss@8.5.15)
-      '@csstools/utilities': 2.0.0(postcss@8.5.15)
-      postcss: 8.5.15
+      braces: 3.0.3
+      picomatch: 2.3.2
 
-  postcss-color-hex-alpha@10.0.0(postcss@8.5.15):
-    dependencies:
-      '@csstools/utilities': 2.0.0(postcss@8.5.15)
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+  mime-db@1.52.0: {}
 
-  postcss-color-rebeccapurple@10.0.0(postcss@8.5.15):
+  mime-types@2.1.35:
     dependencies:
-      '@csstools/utilities': 2.0.0(postcss@8.5.15)
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+      mime-db: 1.52.0
 
-  postcss-colormin@6.1.0(postcss@8.5.15):
-    dependencies:
-      browserslist: 4.28.2
-      caniuse-api: 3.0.0
-      colord: 2.9.3
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+  mime@1.6.0: {}
 
-  postcss-convert-values@6.1.0(postcss@8.5.15):
-    dependencies:
-      browserslist: 4.28.2
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+  mimic-fn@2.1.0: {}
 
-  postcss-custom-media@11.0.6(postcss@8.5.15):
-    dependencies:
-      '@csstools/cascade-layer-name-parser': 2.0.5(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      '@csstools/media-query-list-parser': 4.0.3(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      postcss: 8.5.15
+  mimic-response@3.1.0: {}
 
-  postcss-custom-properties@14.0.6(postcss@8.5.15):
-    dependencies:
-      '@csstools/cascade-layer-name-parser': 2.0.5(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      '@csstools/utilities': 2.0.0(postcss@8.5.15)
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+  mimic-response@4.0.0: {}
 
-  postcss-custom-selectors@8.0.5(postcss@8.5.15):
+  minimatch@3.1.5:
     dependencies:
-      '@csstools/cascade-layer-name-parser': 2.0.5(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      postcss: 8.5.15
-      postcss-selector-parser: 7.1.2
+      brace-expansion: 1.1.21
 
-  postcss-dir-pseudo-class@9.0.1(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
-      postcss-selector-parser: 7.1.2
+  minimist@1.2.8:
+    optional: true
 
-  postcss-discard-comments@6.0.2(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
+  minipass@7.1.3: {}
 
-  postcss-discard-duplicates@6.0.3(postcss@8.5.15):
+  minizlib@3.1.0:
     dependencies:
-      postcss: 8.5.15
+      minipass: 7.1.3
 
-  postcss-discard-empty@6.0.3(postcss@8.5.15):
+  mint@4.2.1062(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/node@26.6.5)(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(typescript@6.0.3):
     dependencies:
-      postcss: 8.5.15
+      '@mintlify/cli': 4.0.1665(@base-ui/react@1.9.0(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3))(@types/node@26.6.5)(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(typescript@6.0.3)
+    transitivePeerDependencies:
+      - '@base-ui/react'
+      - '@types/node'
+      - '@types/react'
+      - bufferutil
+      - debug
+      - encoding
+      - puppeteer
+      - react-devtools-core
+      - react-dom
+      - supports-color
+      - ts-node
+      - typescript
+      - utf-8-validate
 
-  postcss-discard-overridden@6.0.2(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
+  mkdirp-classic@0.5.3:
+    optional: true
 
-  postcss-discard-unused@6.0.5(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
-      postcss-selector-parser: 6.1.2
+  ms@2.0.0: {}
 
-  postcss-double-position-gradients@6.0.4(postcss@8.5.15):
-    dependencies:
-      '@csstools/postcss-progressive-custom-properties': 4.2.1(postcss@8.5.15)
-      '@csstools/utilities': 2.0.0(postcss@8.5.15)
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+  ms@2.1.3: {}
 
-  postcss-focus-visible@10.0.1(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
-      postcss-selector-parser: 7.1.2
+  mute-stream@2.0.0: {}
 
-  postcss-focus-within@9.0.1(postcss@8.5.15):
+  mz@2.7.0:
     dependencies:
-      postcss: 8.5.15
-      postcss-selector-parser: 7.1.2
+      any-promise: 1.3.0
+      object-assign: 4.1.1
+      thenify-all: 1.6.0
 
-  postcss-font-variant@5.0.0(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
+  nanoid@3.3.20: {}
 
-  postcss-gap-properties@6.0.0(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
+  napi-build-utils@2.0.0:
+    optional: true
 
-  postcss-image-set-function@7.0.0(postcss@8.5.15):
-    dependencies:
-      '@csstools/utilities': 2.0.0(postcss@8.5.15)
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+  negotiator@0.6.3: {}
 
-  postcss-lab-function@7.0.12(postcss@8.5.15):
-    dependencies:
-      '@csstools/css-color-parser': 3.1.0(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
-      '@csstools/css-tokenizer': 3.0.4
-      '@csstools/postcss-progressive-custom-properties': 4.2.1(postcss@8.5.15)
-      '@csstools/utilities': 2.0.0(postcss@8.5.15)
-      postcss: 8.5.15
+  neotraverse@0.6.18: {}
 
-  postcss-loader@7.3.4(postcss@8.5.15)(typescript@6.0.3)(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)):
+  next-mdx-remote-client@2.1.12(@types/react@19.3.0)(react-dom@19.3.1(react@19.2.3))(react@19.2.3)(unified@11.0.5):
     dependencies:
-      cosmiconfig: 8.3.6(typescript@6.0.3)
-      jiti: 1.21.7
-      postcss: 8.5.15
-      semver: 7.8.3
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
+      '@babel/code-frame': 7.29.7
+      '@mdx-js/mdx': 3.1.1
+      '@mdx-js/react': 3.1.1(@types/react@19.3.0)(react@19.2.3)
+      '@types/mdx': 2.0.14
+      react: 19.2.3
+      react-dom: 19.3.1(react@19.2.3)
+      remark-mdx-remove-esm: 1.3.3(unified@11.0.5)
+      serialize-error: 13.0.2
+      vfile: 6.0.3
+      vfile-matter: 5.0.1
     transitivePeerDependencies:
-      - typescript
-
-  postcss-logical@8.1.0(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+      - '@types/react'
+      - supports-color
+      - unified
 
-  postcss-merge-idents@6.0.3(postcss@8.5.15):
+  nimma@0.2.3:
     dependencies:
-      cssnano-utils: 4.0.2(postcss@8.5.15)
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+      '@jsep-plugin/regex': 1.1.0(jsep@1.6.0)
+      '@jsep-plugin/ternary': 1.2.0(jsep@1.6.0)
+      astring: 1.9.0
+      jsep: 1.6.0
+    optionalDependencies:
+      jsonpath-plus: 10.4.0
+      lodash.topath: 4.5.2
 
-  postcss-merge-longhand@6.0.5(postcss@8.5.15):
+  nlcst-to-string@4.0.0:
     dependencies:
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
-      stylehacks: 6.1.1(postcss@8.5.15)
+      '@types/nlcst': 2.0.3
 
-  postcss-merge-rules@6.1.1(postcss@8.5.15):
+  node-abi@3.99.0:
     dependencies:
-      browserslist: 4.28.2
-      caniuse-api: 3.0.0
-      cssnano-utils: 4.0.2(postcss@8.5.15)
-      postcss: 8.5.15
-      postcss-selector-parser: 6.1.2
+      semver: 7.8.5
+    optional: true
 
-  postcss-minify-font-values@6.1.0(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+  node-addon-api@4.3.0:
+    optional: true
 
-  postcss-minify-gradients@6.0.3(postcss@8.5.15):
+  node-fetch@2.6.7:
     dependencies:
-      colord: 2.9.3
-      cssnano-utils: 4.0.2(postcss@8.5.15)
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+      whatwg-url: 5.0.0
 
-  postcss-minify-params@6.1.0(postcss@8.5.15):
+  node-fetch@2.7.0:
     dependencies:
-      browserslist: 4.28.2
-      cssnano-utils: 4.0.2(postcss@8.5.15)
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+      whatwg-url: 5.0.0
 
-  postcss-minify-selectors@6.0.4(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
-      postcss-selector-parser: 6.1.2
+  non-error@0.1.0: {}
 
-  postcss-modules-extract-imports@3.1.0(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
+  normalize-path@3.0.0: {}
 
-  postcss-modules-local-by-default@4.2.0(postcss@8.5.15):
-    dependencies:
-      icss-utils: 5.1.0(postcss@8.5.15)
-      postcss: 8.5.15
-      postcss-selector-parser: 7.1.2
-      postcss-value-parser: 4.2.0
+  normalize-url@8.1.1: {}
 
-  postcss-modules-scope@3.2.1(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
-      postcss-selector-parser: 7.1.2
+  oauth4webapi@3.8.8: {}
 
-  postcss-modules-values@4.0.0(postcss@8.5.15):
-    dependencies:
-      icss-utils: 5.1.0(postcss@8.5.15)
-      postcss: 8.5.15
+  object-assign@4.1.1: {}
 
-  postcss-nesting@13.0.2(postcss@8.5.15):
-    dependencies:
-      '@csstools/selector-resolve-nested': 3.1.0(postcss-selector-parser@7.1.2)
-      '@csstools/selector-specificity': 5.0.0(postcss-selector-parser@7.1.2)
-      postcss: 8.5.15
-      postcss-selector-parser: 7.1.2
+  object-hash@3.0.0: {}
 
-  postcss-normalize-charset@6.0.2(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
+  object-inspect@1.13.4: {}
 
-  postcss-normalize-display-values@6.0.2(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+  object-keys@1.1.1: {}
 
-  postcss-normalize-positions@6.0.2(postcss@8.5.15):
+  object.assign@4.1.7:
     dependencies:
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+      call-bind: 1.0.9
+      call-bound: 1.0.4
+      define-properties: 1.2.1
+      es-object-atoms: 1.1.2
+      has-symbols: 1.1.0
+      object-keys: 1.1.1
 
-  postcss-normalize-repeat-style@6.0.2(postcss@8.5.15):
+  on-finished@2.4.1:
     dependencies:
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+      ee-first: 1.1.1
 
-  postcss-normalize-string@6.0.2(postcss@8.5.15):
+  once@1.4.0:
     dependencies:
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+      wrappy: 1.0.2
 
-  postcss-normalize-timing-functions@6.0.2(postcss@8.5.15):
+  onetime@5.1.2:
     dependencies:
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+      mimic-fn: 2.1.0
 
-  postcss-normalize-unicode@6.1.0(postcss@8.5.15):
-    dependencies:
-      browserslist: 4.28.2
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+  oniguruma-parser@0.12.2: {}
 
-  postcss-normalize-url@6.0.2(postcss@8.5.15):
+  oniguruma-to-es@4.3.6:
     dependencies:
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+      oniguruma-parser: 0.12.2
+      regex: 6.1.0
+      regex-recursion: 6.0.2
 
-  postcss-normalize-whitespace@6.0.2(postcss@8.5.15):
+  open@8.4.2:
     dependencies:
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+      define-lazy-prop: 2.0.0
+      is-docker: 2.2.1
+      is-wsl: 2.2.0
 
-  postcss-opacity-percentage@3.0.0(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
+  openapi-types@12.1.3: {}
 
-  postcss-ordered-values@6.0.2(postcss@8.5.15):
+  openid-client@6.8.2:
     dependencies:
-      cssnano-utils: 4.0.2(postcss@8.5.15)
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+      jose: 6.2.12
+      oauth4webapi: 3.8.8
 
-  postcss-overflow-shorthand@6.0.0(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+  orderedmap@2.1.1: {}
 
-  postcss-page-break@3.0.4(postcss@8.5.15):
+  own-keys@1.0.2:
     dependencies:
-      postcss: 8.5.15
+      call-bound: 1.0.4
+      get-intrinsic: 1.3.0
+      object-keys: 1.1.1
+      safe-push-apply: 1.0.0
 
-  postcss-place@10.0.0(postcss@8.5.15):
+  p-any@4.0.0:
     dependencies:
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+      p-cancelable: 3.0.0
+      p-some: 6.0.0
 
-  postcss-preset-env@10.6.1(postcss@8.5.15):
-    dependencies:
-      '@csstools/postcss-alpha-function': 1.0.1(postcss@8.5.15)
-      '@csstools/postcss-cascade-layers': 5.0.2(postcss@8.5.15)
-      '@csstools/postcss-color-function': 4.0.12(postcss@8.5.15)
-      '@csstools/postcss-color-function-display-p3-linear': 1.0.1(postcss@8.5.15)
-      '@csstools/postcss-color-mix-function': 3.0.12(postcss@8.5.15)
-      '@csstools/postcss-color-mix-variadic-function-arguments': 1.0.2(postcss@8.5.15)
-      '@csstools/postcss-content-alt-text': 2.0.8(postcss@8.5.15)
-      '@csstools/postcss-contrast-color-function': 2.0.12(postcss@8.5.15)
-      '@csstools/postcss-exponential-functions': 2.0.9(postcss@8.5.15)
-      '@csstools/postcss-font-format-keywords': 4.0.0(postcss@8.5.15)
-      '@csstools/postcss-gamut-mapping': 2.0.11(postcss@8.5.15)
-      '@csstools/postcss-gradients-interpolation-method': 5.0.12(postcss@8.5.15)
-      '@csstools/postcss-hwb-function': 4.0.12(postcss@8.5.15)
-      '@csstools/postcss-ic-unit': 4.0.4(postcss@8.5.15)
-      '@csstools/postcss-initial': 2.0.1(postcss@8.5.15)
-      '@csstools/postcss-is-pseudo-class': 5.0.3(postcss@8.5.15)
-      '@csstools/postcss-light-dark-function': 2.0.11(postcss@8.5.15)
-      '@csstools/postcss-logical-float-and-clear': 3.0.0(postcss@8.5.15)
-      '@csstools/postcss-logical-overflow': 2.0.0(postcss@8.5.15)
-      '@csstools/postcss-logical-overscroll-behavior': 2.0.0(postcss@8.5.15)
-      '@csstools/postcss-logical-resize': 3.0.0(postcss@8.5.15)
-      '@csstools/postcss-logical-viewport-units': 3.0.4(postcss@8.5.15)
-      '@csstools/postcss-media-minmax': 2.0.9(postcss@8.5.15)
-      '@csstools/postcss-media-queries-aspect-ratio-number-values': 3.0.5(postcss@8.5.15)
-      '@csstools/postcss-nested-calc': 4.0.0(postcss@8.5.15)
-      '@csstools/postcss-normalize-display-values': 4.0.1(postcss@8.5.15)
-      '@csstools/postcss-oklab-function': 4.0.12(postcss@8.5.15)
-      '@csstools/postcss-position-area-property': 1.0.0(postcss@8.5.15)
-      '@csstools/postcss-progressive-custom-properties': 4.2.1(postcss@8.5.15)
-      '@csstools/postcss-property-rule-prelude-list': 1.0.0(postcss@8.5.15)
-      '@csstools/postcss-random-function': 2.0.1(postcss@8.5.15)
-      '@csstools/postcss-relative-color-syntax': 3.0.12(postcss@8.5.15)
-      '@csstools/postcss-scope-pseudo-class': 4.0.1(postcss@8.5.15)
-      '@csstools/postcss-sign-functions': 1.1.4(postcss@8.5.15)
-      '@csstools/postcss-stepped-value-functions': 4.0.9(postcss@8.5.15)
-      '@csstools/postcss-syntax-descriptor-syntax-production': 1.0.1(postcss@8.5.15)
-      '@csstools/postcss-system-ui-font-family': 1.0.0(postcss@8.5.15)
-      '@csstools/postcss-text-decoration-shorthand': 4.0.3(postcss@8.5.15)
-      '@csstools/postcss-trigonometric-functions': 4.0.9(postcss@8.5.15)
-      '@csstools/postcss-unset-value': 4.0.0(postcss@8.5.15)
-      autoprefixer: 10.5.0(postcss@8.5.15)
-      browserslist: 4.28.2
-      css-blank-pseudo: 7.0.1(postcss@8.5.15)
-      css-has-pseudo: 7.0.3(postcss@8.5.15)
-      css-prefers-color-scheme: 10.0.0(postcss@8.5.15)
-      cssdb: 8.9.0
-      postcss: 8.5.15
-      postcss-attribute-case-insensitive: 7.0.1(postcss@8.5.15)
-      postcss-clamp: 4.1.0(postcss@8.5.15)
-      postcss-color-functional-notation: 7.0.12(postcss@8.5.15)
-      postcss-color-hex-alpha: 10.0.0(postcss@8.5.15)
-      postcss-color-rebeccapurple: 10.0.0(postcss@8.5.15)
-      postcss-custom-media: 11.0.6(postcss@8.5.15)
-      postcss-custom-properties: 14.0.6(postcss@8.5.15)
-      postcss-custom-selectors: 8.0.5(postcss@8.5.15)
-      postcss-dir-pseudo-class: 9.0.1(postcss@8.5.15)
-      postcss-double-position-gradients: 6.0.4(postcss@8.5.15)
-      postcss-focus-visible: 10.0.1(postcss@8.5.15)
-      postcss-focus-within: 9.0.1(postcss@8.5.15)
-      postcss-font-variant: 5.0.0(postcss@8.5.15)
-      postcss-gap-properties: 6.0.0(postcss@8.5.15)
-      postcss-image-set-function: 7.0.0(postcss@8.5.15)
-      postcss-lab-function: 7.0.12(postcss@8.5.15)
-      postcss-logical: 8.1.0(postcss@8.5.15)
-      postcss-nesting: 13.0.2(postcss@8.5.15)
-      postcss-opacity-percentage: 3.0.0(postcss@8.5.15)
-      postcss-overflow-shorthand: 6.0.0(postcss@8.5.15)
-      postcss-page-break: 3.0.4(postcss@8.5.15)
-      postcss-place: 10.0.0(postcss@8.5.15)
-      postcss-pseudo-class-any-link: 10.0.1(postcss@8.5.15)
-      postcss-replace-overflow-wrap: 4.0.0(postcss@8.5.15)
-      postcss-selector-not: 8.0.1(postcss@8.5.15)
-
-  postcss-pseudo-class-any-link@10.0.1(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
-      postcss-selector-parser: 7.1.2
-
-  postcss-reduce-idents@6.0.3(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+  p-cancelable@3.0.0: {}
 
-  postcss-reduce-initial@6.1.0(postcss@8.5.15):
+  p-some@6.0.0:
     dependencies:
-      browserslist: 4.28.2
-      caniuse-api: 3.0.0
-      postcss: 8.5.15
+      aggregate-error: 4.0.1
+      p-cancelable: 3.0.0
 
-  postcss-reduce-transforms@6.0.2(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
+  p-timeout@5.1.0: {}
 
-  postcss-replace-overflow-wrap@4.0.0(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
+  pako@0.2.9: {}
 
-  postcss-selector-not@8.0.1(postcss@8.5.15):
+  parse-css-color@0.2.1:
     dependencies:
-      postcss: 8.5.15
-      postcss-selector-parser: 7.1.2
+      color-name: 1.1.4
+      hex-rgb: 4.3.0
 
-  postcss-selector-parser@6.1.2:
+  parse-entities@4.0.2:
     dependencies:
-      cssesc: 3.0.0
-      util-deprecate: 1.0.2
+      '@types/unist': 2.0.11
+      character-entities-legacy: 3.0.0
+      character-reference-invalid: 2.0.1
+      decode-named-character-reference: 1.3.0
+      is-alphanumerical: 2.0.1
+      is-decimal: 2.0.1
+      is-hexadecimal: 2.0.1
 
-  postcss-selector-parser@7.1.2:
+  parse-latin@7.0.0:
     dependencies:
-      cssesc: 3.0.0
-      util-deprecate: 1.0.2
+      '@types/nlcst': 2.0.3
+      '@types/unist': 3.0.3
+      nlcst-to-string: 4.0.0
+      unist-util-modify-children: 4.0.0
+      unist-util-visit-children: 3.0.0
+      vfile: 6.0.3
 
-  postcss-sort-media-queries@5.2.0(postcss@8.5.15):
+  parse5@7.3.0:
     dependencies:
-      postcss: 8.5.15
-      sort-css-media-queries: 2.2.0
+      entities: 6.0.1
 
-  postcss-svgo@6.0.3(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
-      postcss-value-parser: 4.2.0
-      svgo: 3.3.3
+  parseurl@1.3.3: {}
 
-  postcss-unique-selectors@6.0.4(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
-      postcss-selector-parser: 6.1.2
+  patch-console@2.0.0: {}
 
-  postcss-value-parser@4.2.0: {}
+  path-expression-matcher@1.6.2: {}
 
-  postcss-zindex@6.0.2(postcss@8.5.15):
-    dependencies:
-      postcss: 8.5.15
+  path-is-absolute@1.0.1: {}
 
-  postcss@8.5.15:
-    dependencies:
-      nanoid: 3.3.12
-      picocolors: 1.1.1
-      source-map-js: 1.2.1
+  path-key@3.1.1: {}
 
-  postman-code-generators@2.1.1:
-    dependencies:
-      async: 3.2.6
-      detect-package-manager: 3.0.2
-      lodash: 4.18.1
-      postman-collection: 5.3.0
-      shelljs: 0.8.5
+  path-parse@1.0.7: {}
 
-  postman-collection@5.3.0:
-    dependencies:
-      '@faker-js/faker': 5.5.3
-      file-type: 3.9.0
-      http-reasons: 0.1.0
-      iconv-lite: 0.6.3
-      liquid-json: 0.3.1
-      lodash: 4.17.23
-      mime: 3.0.0
-      mime-format: 2.0.2
-      postman-url-encoder: 3.0.8
-      semver: 7.7.1
-      uuid: 8.3.2
+  path-to-regexp@0.1.13: {}
 
-  postman-url-encoder@3.0.8:
-    dependencies:
-      punycode: 2.3.1
+  picocolors@1.1.1: {}
 
-  prelude-ls@1.2.1: {}
+  picomatch@2.3.2: {}
 
-  prettier@3.9.4: {}
+  picomatch@4.0.7: {}
 
-  pretty-error@4.0.0:
-    dependencies:
-      lodash: 4.18.1
-      renderkid: 3.0.0
+  pirates@4.0.7: {}
 
-  pretty-time@1.1.0: {}
+  pony-cause@1.1.1: {}
 
-  prism-react-renderer@1.3.5(react@19.2.7):
+  possible-typed-array-names@1.1.0: {}
+
+  postcss-import@15.1.0(postcss@8.5.23):
     dependencies:
-      react: 19.2.7
+      postcss: 8.5.23
+      postcss-value-parser: 4.2.0
+      read-cache: 1.0.2
+      resolve: 1.22.13
 
-  prism-react-renderer@2.4.1(react@19.2.7):
+  postcss-js@4.1.0(postcss@8.5.23):
     dependencies:
-      '@types/prismjs': 1.26.6
-      clsx: 2.1.1
-      react: 19.2.7
+      camelcase-css: 2.0.1
+      postcss: 8.5.23
 
-  prismjs@1.27.0: {}
+  postcss-load-config@4.0.2(postcss@8.5.23):
+    dependencies:
+      lilconfig: 3.1.4
+      yaml: 2.8.3
+    optionalDependencies:
+      postcss: 8.5.23
 
-  prismjs@1.30.0: {}
+  postcss-nested@6.2.0(postcss@8.5.23):
+    dependencies:
+      postcss: 8.5.23
+      postcss-selector-parser: 6.1.4
 
-  process-nextick-args@2.0.1: {}
+  postcss-selector-parser@6.1.4:
+    dependencies:
+      cssesc: 3.0.0
+      util-deprecate: 1.0.2
 
-  process@0.11.10: {}
+  postcss-value-parser@4.2.0: {}
 
-  prompts@2.4.2:
+  postcss@8.5.23:
     dependencies:
-      kleur: 3.0.3
-      sisteransi: 1.0.5
+      nanoid: 3.3.20
+      picocolors: 1.1.1
+      source-map-js: 1.2.2
 
-  prop-types@15.8.1:
+  posthog-node@5.17.2:
     dependencies:
-      loose-envify: 1.4.0
-      object-assign: 4.1.1
-      react-is: 16.13.1
+      '@posthog/core': 1.7.1
 
-  property-information@5.6.0:
+  prebuild-install@7.1.3:
     dependencies:
-      xtend: 4.0.2
+      detect-libc: 2.1.2
+      expand-template: 2.0.3
+      github-from-package: 0.0.0
+      minimist: 1.2.8
+      mkdirp-classic: 0.5.3
+      napi-build-utils: 2.0.0
+      node-abi: 3.99.0
+      pump: 3.0.4
+      rc: 1.2.8
+      simple-get: 4.0.1
+      tar-fs: 2.1.5
+      tunnel-agent: 0.6.0
+    optional: true
+
+  prettier@3.9.4: {}
 
   property-information@6.5.0: {}
 
   property-information@7.2.0: {}
 
-  proto-list@1.2.4: {}
+  prosemirror-model@1.25.4:
+    dependencies:
+      orderedmap: 2.1.1
 
-  proxy-addr@2.0.7:
+  proxy-addr@2.0.8:
     dependencies:
       forwarded: 0.2.0
       ipaddr.js: 1.9.1
 
-  punycode@1.4.1: {}
+  proxy-from-env@2.1.0: {}
 
-  punycode@2.3.1: {}
-
-  pupa@3.3.0:
+  public-ip@5.0.0:
     dependencies:
-      escape-goat: 4.0.0
+      dns-socket: 4.2.2
+      got: 12.6.1
+      is-ip: 3.1.0
 
-  pvtsutils@1.3.6:
+  pump@3.0.4:
     dependencies:
-      tslib: 2.8.1
+      end-of-stream: 1.4.5
+      once: 1.4.0
+    optional: true
 
-  pvutils@1.1.5: {}
+  punycode@2.3.1: {}
 
-  qs@6.15.2:
+  qs@6.14.2:
     dependencies:
       side-channel: 1.1.1
 
-  qs@6.15.3:
+  qs@6.16.1:
     dependencies:
       es-define-property: 1.0.1
       side-channel: 1.1.1
@@ -16837,12 +7275,6 @@ snapshots:
 
   quick-lru@5.1.1: {}
 
-  randombytes@2.1.0:
-    dependencies:
-      safe-buffer: 5.2.1
-
-  range-parser@1.2.0: {}
-
   range-parser@1.2.1: {}
 
   raw-body@2.5.3:
@@ -16850,299 +7282,53 @@ snapshots:
       bytes: 3.1.2
       http-errors: 2.0.1
       iconv-lite: 0.4.24
-      unpipe: 1.0.0
-
-  rc@1.2.8:
-    dependencies:
-      deep-extend: 0.6.0
-      ini: 1.3.8
-      minimist: 1.2.8
-      strip-json-comments: 2.0.1
-
-  react-aria-components@1.18.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7):
-    dependencies:
-      '@internationalized/date': 3.12.2
-      '@react-types/shared': 3.35.0(react@19.2.7)
-      '@swc/helpers': 0.5.23
-      client-only: 0.0.1
-      react: 19.2.7
-      react-aria: 3.49.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      react-dom: 19.2.7(react@19.2.7)
-      react-stately: 3.47.0(react@19.2.7)
-
-  react-aria-components@1.20.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7):
-    dependencies:
-      '@internationalized/date': 3.12.3
-      '@internationalized/string': 3.2.10
-      '@react-types/shared': 3.36.1(react@19.2.7)
-      '@swc/helpers': 0.5.23
-      client-only: 0.0.1
-      react: 19.2.7
-      react-aria: 3.51.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      react-dom: 19.2.7(react@19.2.7)
-      react-stately: 3.49.0(react@19.2.7)
-
-  react-aria@3.49.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7):
-    dependencies:
-      '@internationalized/date': 3.12.2
-      '@internationalized/number': 3.6.7
-      '@internationalized/string': 3.2.9
-      '@react-types/shared': 3.35.0(react@19.2.7)
-      '@swc/helpers': 0.5.23
-      aria-hidden: 1.2.6
-      clsx: 2.1.1
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      react-stately: 3.47.0(react@19.2.7)
-      use-sync-external-store: 1.6.0(react@19.2.7)
-
-  react-aria@3.51.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7):
-    dependencies:
-      '@internationalized/date': 3.12.3
-      '@internationalized/number': 3.6.7
-      '@internationalized/string': 3.2.10
-      '@react-types/shared': 3.36.1(react@19.2.7)
-      '@swc/helpers': 0.5.23
-      aria-hidden: 1.2.6
-      clsx: 2.1.1
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      react-stately: 3.49.0(react@19.2.7)
-      use-sync-external-store: 1.6.0(react@19.2.7)
-
-  react-dom@19.2.7(react@19.2.7):
-    dependencies:
-      react: 19.2.7
-      scheduler: 0.27.0
-
-  react-fast-compare@3.2.2: {}
-
-  react-hook-form@7.80.0(react@19.2.7):
-    dependencies:
-      react: 19.2.7
-
-  react-is@16.13.1: {}
-
-  react-is@18.3.1: {}
-
-  react-json-view-lite@2.5.0(react@19.2.7):
-    dependencies:
-      react: 19.2.7
-
-  react-lifecycles-compat@3.0.4: {}
-
-  react-live@4.1.8(react-dom@19.2.7(react@19.2.7))(react@19.2.7):
-    dependencies:
-      prism-react-renderer: 2.4.1(react@19.2.7)
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      sucrase: 3.35.1
-      use-editable: 2.3.3(react@19.2.7)
-
-  react-loadable-ssr-addon-v5-slorber@1.0.3(@docusaurus/react-loadable@6.0.0(react@19.2.7))(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)):
-    dependencies:
-      '@babel/runtime': 7.29.7
-      react-loadable: '@docusaurus/react-loadable@6.0.0(react@19.2.7)'
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
-
-  react-magic-dropzone@1.0.1: {}
-
-  react-markdown@10.1.0(@types/react@19.2.17)(react@19.2.7):
-    dependencies:
-      '@types/hast': 3.0.4
-      '@types/mdast': 4.0.4
-      '@types/react': 19.2.17
-      devlop: 1.1.0
-      hast-util-to-jsx-runtime: 2.3.6
-      html-url-attributes: 3.0.1
-      mdast-util-to-hast: 13.2.1
-      react: 19.2.7
-      remark-parse: 11.0.0
-      remark-rehype: 11.1.2
-      unified: 11.0.5
-      unist-util-visit: 5.1.0
-      vfile: 6.0.3
-    transitivePeerDependencies:
-      - supports-color
-
-  react-markdown@8.0.7(@types/react@19.2.17)(react@19.2.7):
-    dependencies:
-      '@types/hast': 2.3.10
-      '@types/prop-types': 15.7.15
-      '@types/react': 19.2.17
-      '@types/unist': 2.0.11
-      comma-separated-tokens: 2.0.3
-      hast-util-whitespace: 2.0.1
-      prop-types: 15.8.1
-      property-information: 6.5.0
-      react: 19.2.7
-      react-is: 18.3.1
-      remark-parse: 10.0.2
-      remark-rehype: 10.1.0
-      space-separated-tokens: 2.0.2
-      style-to-object: 0.4.4
-      unified: 10.1.2
-      unist-util-visit: 4.1.2
-      vfile: 5.3.7
-    transitivePeerDependencies:
-      - supports-color
+      unpipe: 1.0.0
 
-  react-modal@3.16.3(react-dom@19.2.7(react@19.2.7))(react@19.2.7):
+  rc@1.2.8:
     dependencies:
-      exenv: 1.2.2
-      prop-types: 15.8.1
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      react-lifecycles-compat: 3.0.4
-      warning: 4.0.3
+      deep-extend: 0.6.0
+      ini: 1.3.8
+      minimist: 1.2.8
+      strip-json-comments: 2.0.1
+    optional: true
 
-  react-overflow-list@0.5.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7):
-    dependencies:
-      react: 19.2.7
-      react-use: 17.6.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-    transitivePeerDependencies:
-      - react-dom
+  re2js@2.8.6: {}
 
-  react-redux@9.3.0(@types/react@19.2.17)(react@19.2.7)(redux@5.0.1):
+  react-dom@19.3.1(react@19.2.3):
     dependencies:
-      '@types/use-sync-external-store': 0.0.6
-      react: 19.2.7
-      use-sync-external-store: 1.6.0(react@19.2.7)
-    optionalDependencies:
-      '@types/react': 19.2.17
-      redux: 5.0.1
-
-  react-router-config@5.1.1(react-router@5.3.4(react@19.2.7))(react@19.2.7):
-    dependencies:
-      '@babel/runtime': 7.29.7
-      react: 19.2.7
-      react-router: 5.3.4(react@19.2.7)
-
-  react-router-dom@5.3.4(react@19.2.7):
-    dependencies:
-      '@babel/runtime': 7.29.7
-      history: 4.10.1
-      loose-envify: 1.4.0
-      prop-types: 15.8.1
-      react: 19.2.7
-      react-router: 5.3.4(react@19.2.7)
-      tiny-invariant: 1.3.3
-      tiny-warning: 1.0.3
-
-  react-router@5.3.4(react@19.2.7):
-    dependencies:
-      '@babel/runtime': 7.29.7
-      history: 4.10.1
-      hoist-non-react-statics: 3.3.2
-      loose-envify: 1.4.0
-      path-to-regexp: 1.9.0
-      prop-types: 15.8.1
-      react: 19.2.7
-      react-is: 16.13.1
-      tiny-invariant: 1.3.3
-      tiny-warning: 1.0.3
-
-  react-stately@3.47.0(react@19.2.7):
-    dependencies:
-      '@internationalized/date': 3.12.2
-      '@internationalized/number': 3.6.7
-      '@internationalized/string': 3.2.9
-      '@react-types/shared': 3.35.0(react@19.2.7)
-      '@swc/helpers': 0.5.23
-      react: 19.2.7
-      use-sync-external-store: 1.6.0(react@19.2.7)
-
-  react-stately@3.49.0(react@19.2.7):
-    dependencies:
-      '@internationalized/date': 3.12.3
-      '@internationalized/number': 3.6.7
-      '@internationalized/string': 3.2.10
-      '@react-types/shared': 3.36.1(react@19.2.7)
-      '@swc/helpers': 0.5.23
-      react: 19.2.7
-      use-sync-external-store: 1.6.0(react@19.2.7)
-
-  react-syntax-highlighter@15.6.6(react@19.2.7):
-    dependencies:
-      '@babel/runtime': 7.29.7
-      highlight.js: 10.7.3
-      highlightjs-vue: 1.0.0
-      lowlight: 1.20.0
-      prismjs: 1.30.0
-      react: 19.2.7
-      refractor: 3.6.0
-
-  react-transition-group@4.4.5(react-dom@19.2.7(react@19.2.7))(react@19.2.7):
-    dependencies:
-      '@babel/runtime': 7.29.7
-      dom-helpers: 5.2.1
-      loose-envify: 1.4.0
-      prop-types: 15.8.1
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-
-  react-universal-interface@0.6.2(react@19.2.7)(tslib@2.8.1):
-    dependencies:
-      react: 19.2.7
-      tslib: 2.8.1
+      react: 19.2.3
+      scheduler: 0.28.0
 
-  react-use@17.6.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7):
+  react-reconciler@0.32.0(react@19.2.3):
     dependencies:
-      '@types/js-cookie': 2.2.7
-      '@xobotyi/scrollbar-width': 1.9.5
-      copy-to-clipboard: 3.3.3
-      fast-deep-equal: 3.1.3
-      fast-shallow-equal: 1.0.0
-      js-cookie: 2.2.1
-      nano-css: 5.6.2(react-dom@19.2.7(react@19.2.7))(react@19.2.7)
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
-      react-universal-interface: 0.6.2(react@19.2.7)(tslib@2.8.1)
-      resize-observer-polyfill: 1.5.1
-      screenfull: 5.2.0
-      set-harmonic-interval: 1.0.1
-      throttle-debounce: 3.0.1
-      ts-easing: 0.2.0
-      tslib: 2.8.1
+      react: 19.2.3
+      scheduler: 0.26.0
 
-  react@19.2.7: {}
+  react@19.2.3: {}
 
-  readable-stream@2.3.8:
-    dependencies:
-      core-util-is: 1.0.3
-      inherits: 2.0.4
-      isarray: 1.0.0
-      process-nextick-args: 2.0.1
-      safe-buffer: 5.1.2
-      string_decoder: 1.1.1
-      util-deprecate: 1.0.2
+  read-cache@1.0.2: {}
 
   readable-stream@3.6.2:
     dependencies:
       inherits: 2.0.4
       string_decoder: 1.3.0
       util-deprecate: 1.0.2
+    optional: true
 
   readdirp@3.6.0:
     dependencies:
       picomatch: 2.3.2
 
-  readdirp@5.0.0: {}
-
-  rechoir@0.6.2:
-    dependencies:
-      resolve: 1.22.12
-
   recma-build-jsx@1.0.0:
     dependencies:
       '@types/estree': 1.0.9
       estree-util-build-jsx: 3.0.1
       vfile: 6.0.3
 
-  recma-jsx@1.0.1(acorn@8.16.0):
+  recma-jsx@1.0.1(acorn@8.11.2):
     dependencies:
-      acorn: 8.16.0
-      acorn-jsx: 5.3.2(acorn@8.16.0)
+      acorn: 8.11.2
+      acorn-jsx: 5.3.2(acorn@8.11.2)
       estree-util-to-js: 2.0.0
       recma-parse: 1.0.0
       recma-stringify: 1.0.0
@@ -17162,99 +7348,71 @@ snapshots:
       unified: 11.0.5
       vfile: 6.0.3
 
-  redux-thunk@3.1.0(redux@5.0.1):
-    dependencies:
-      redux: 5.0.1
-
-  redux@5.0.1: {}
-
-  reflect-metadata@0.2.2: {}
-
-  refractor@3.6.0:
-    dependencies:
-      hastscript: 6.0.0
-      parse-entities: 2.0.0
-      prismjs: 1.27.0
-
-  reftools@1.1.9: {}
-
-  regenerate-unicode-properties@10.2.2:
+  reflect.getprototypeof@1.0.10:
     dependencies:
-      regenerate: 1.4.2
-
-  regenerate@1.4.2: {}
+      call-bind: 1.0.9
+      define-properties: 1.2.1
+      es-abstract: 1.24.2
+      es-errors: 1.3.0
+      es-object-atoms: 1.1.2
+      get-intrinsic: 1.3.0
+      get-proto: 1.0.1
+      which-builtin-type: 1.2.1
 
-  regexpu-core@6.4.0:
+  regex-recursion@6.0.2:
     dependencies:
-      regenerate: 1.4.2
-      regenerate-unicode-properties: 10.2.2
-      regjsgen: 0.8.0
-      regjsparser: 0.13.1
-      unicode-match-property-ecmascript: 2.0.0
-      unicode-match-property-value-ecmascript: 2.2.1
+      regex-utilities: 2.3.0
 
-  registry-auth-token@5.1.1:
-    dependencies:
-      '@pnpm/npm-conf': 3.0.2
+  regex-utilities@2.3.0: {}
 
-  registry-url@6.0.1:
+  regex@6.1.0:
     dependencies:
-      rc: 1.2.8
-
-  regjsgen@0.8.0: {}
+      regex-utilities: 2.3.0
 
-  regjsparser@0.13.1:
+  regexp.prototype.flags@1.5.4:
     dependencies:
-      jsesc: 3.1.0
+      call-bind: 1.0.9
+      define-properties: 1.2.1
+      es-errors: 1.3.0
+      get-proto: 1.0.1
+      gopd: 1.2.0
+      set-function-name: 2.0.2
 
   rehype-katex@7.0.1:
     dependencies:
-      '@types/hast': 3.0.4
+      '@types/hast': 3.0.5
       '@types/katex': 0.16.8
       hast-util-from-html-isomorphic: 2.0.0
       hast-util-to-text: 4.0.2
       katex: 0.16.47
-      unist-util-visit-parents: 6.0.2
+      unist-util-visit-parents: 6.0.1
       vfile: 6.0.3
 
-  rehype-raw@7.0.0:
+  rehype-minify-whitespace@6.0.2:
     dependencies:
-      '@types/hast': 3.0.4
-      hast-util-raw: 9.1.0
-      vfile: 6.0.3
+      '@types/hast': 3.0.5
+      hast-util-minify-whitespace: 1.0.1
 
-  rehype-recma@1.0.0:
+  rehype-parse@9.0.1:
     dependencies:
-      '@types/estree': 1.0.9
-      '@types/hast': 3.0.4
-      hast-util-to-estree: 3.1.3
-    transitivePeerDependencies:
-      - supports-color
-
-  relateurl@0.2.7: {}
+      '@types/hast': 3.0.5
+      hast-util-from-html: 2.0.3
+      unified: 11.0.5
 
-  remark-directive@3.0.1:
+  rehype-recma@1.0.0:
     dependencies:
-      '@types/mdast': 4.0.4
-      mdast-util-directive: 3.1.0
-      micromark-extension-directive: 3.0.2
-      unified: 11.0.5
+      '@types/estree': 1.0.9
+      '@types/hast': 3.0.5
+      hast-util-to-estree: 3.1.0
     transitivePeerDependencies:
       - supports-color
 
-  remark-emoji@4.0.1:
+  rehype-stringify@10.0.1:
     dependencies:
-      '@types/mdast': 4.0.4
-      emoticon: 4.1.0
-      mdast-util-find-and-replace: 3.0.2
-      node-emoji: 2.2.0
+      '@types/hast': 3.0.5
+      hast-util-to-html: 9.0.4
       unified: 11.0.5
 
-  remark-frontmatter@3.0.0:
-    dependencies:
-      mdast-util-frontmatter: 0.2.0
-      micromark-extension-frontmatter: 0.2.2
-
   remark-frontmatter@5.0.0:
     dependencies:
       '@types/mdast': 4.0.4
@@ -17264,10 +7422,14 @@ snapshots:
     transitivePeerDependencies:
       - supports-color
 
-  remark-gfm@1.0.0:
+  remark-gfm@4.0.0:
     dependencies:
-      mdast-util-gfm: 0.1.2
-      micromark-extension-gfm: 0.3.3
+      '@types/mdast': 4.0.4
+      mdast-util-gfm: 3.0.0
+      micromark-extension-gfm: 3.0.0
+      remark-parse: 11.0.0
+      remark-stringify: 11.0.0
+      unified: 11.0.5
     transitivePeerDependencies:
       - supports-color
 
@@ -17291,93 +7453,84 @@ snapshots:
     transitivePeerDependencies:
       - supports-color
 
-  remark-mdx@3.1.1:
+  remark-mdx-remove-esm@1.3.3(unified@11.0.5):
+    dependencies:
+      '@types/mdast': 4.0.4
+      unified: 11.0.5
+      unist-util-remove: 4.0.0
+
+  remark-mdx@3.0.1:
     dependencies:
       mdast-util-mdx: 3.0.0
       micromark-extension-mdxjs: 3.0.0
     transitivePeerDependencies:
       - supports-color
 
-  remark-parse@10.0.2:
+  remark-mdx@3.1.0:
     dependencies:
-      '@types/mdast': 3.0.15
-      mdast-util-from-markdown: 1.3.1
-      unified: 10.1.2
+      mdast-util-mdx: 3.0.0
+      micromark-extension-mdxjs: 3.0.0
     transitivePeerDependencies:
       - supports-color
 
-  remark-parse@11.0.0:
+  remark-mdx@3.1.1:
     dependencies:
-      '@types/mdast': 4.0.4
-      mdast-util-from-markdown: 2.0.3
-      micromark-util-types: 2.0.2
-      unified: 11.0.5
+      mdast-util-mdx: 3.0.0
+      micromark-extension-mdxjs: 3.0.0
     transitivePeerDependencies:
       - supports-color
 
-  remark-parse@9.0.0:
+  remark-parse@11.0.0:
     dependencies:
-      mdast-util-from-markdown: 0.8.5
+      '@types/mdast': 4.0.4
+      mdast-util-from-markdown: 2.0.2
+      micromark-util-types: 2.0.3
+      unified: 11.0.5
     transitivePeerDependencies:
       - supports-color
 
-  remark-rehype@10.1.0:
+  remark-rehype@11.1.1:
     dependencies:
-      '@types/hast': 2.3.10
-      '@types/mdast': 3.0.15
-      mdast-util-to-hast: 12.3.0
-      unified: 10.1.2
-
-  remark-rehype@11.1.2:
-    dependencies:
-      '@types/hast': 3.0.4
+      '@types/hast': 3.0.5
       '@types/mdast': 4.0.4
       mdast-util-to-hast: 13.2.1
       unified: 11.0.5
       vfile: 6.0.3
 
-  remark-stringify@11.0.0:
+  remark-smartypants@3.0.2:
     dependencies:
-      '@types/mdast': 4.0.4
-      mdast-util-to-markdown: 2.1.2
+      retext: 9.0.0
+      retext-smartypants: 6.2.0
       unified: 11.0.5
+      unist-util-visit: 5.0.0
 
-  remark-stringify@9.0.1:
+  remark-stringify@11.0.0:
     dependencies:
-      mdast-util-to-markdown: 0.6.5
+      '@types/mdast': 4.0.4
+      mdast-util-to-markdown: 2.2.0
+      unified: 11.0.5
 
-  renderkid@3.0.0:
+  remark@15.0.1:
     dependencies:
-      css-select: 4.3.0
-      dom-converter: 0.2.0
-      htmlparser2: 6.1.0
-      lodash: 4.18.1
-      strip-ansi: 6.0.1
-
-  repeat-string@1.6.1: {}
+      '@types/mdast': 4.0.4
+      remark-parse: 11.0.0
+      remark-stringify: 11.0.0
+      unified: 11.0.5
+    transitivePeerDependencies:
+      - supports-color
 
   require-directory@2.1.1: {}
 
   require-from-string@2.0.2: {}
 
-  require-like@0.1.2: {}
-
-  requires-port@1.0.0: {}
-
-  reselect@5.2.0: {}
-
-  resize-observer-polyfill@1.5.1: {}
+  reselect@5.3.0: {}
 
   resolve-alpn@1.2.1: {}
 
-  resolve-from@4.0.0: {}
-
-  resolve-pathname@3.0.0: {}
-
-  resolve@1.22.12:
+  resolve@1.22.13:
     dependencies:
       es-errors: 1.3.0
-      is-core-module: 2.16.2
+      is-core-module: 2.17.0
       path-parse: 1.0.7
       supports-preserve-symlinks-flag: 1.0.0
 
@@ -17385,110 +7538,97 @@ snapshots:
     dependencies:
       lowercase-keys: 3.0.0
 
-  retry@0.13.1: {}
-
-  reusify@1.1.0: {}
-
-  robust-predicates@3.0.3: {}
-
-  roughjs@4.6.6:
+  restore-cursor@4.0.0:
     dependencies:
-      hachure-fill: 0.5.2
-      path-data-parser: 0.1.0
-      points-on-curve: 0.2.0
-      points-on-path: 0.2.1
+      onetime: 5.1.2
+      signal-exit: 3.0.7
 
-  rtl-css-js@1.16.1:
+  retext-latin@4.0.0:
     dependencies:
-      '@babel/runtime': 7.29.7
+      '@types/nlcst': 2.0.3
+      parse-latin: 7.0.0
+      unified: 11.0.5
 
-  rtlcss@4.3.0:
+  retext-smartypants@6.2.0:
     dependencies:
-      escalade: 3.2.0
-      picocolors: 1.1.1
-      postcss: 8.5.15
-      strip-json-comments: 3.1.1
+      '@types/nlcst': 2.0.3
+      nlcst-to-string: 4.0.0
+      unist-util-visit: 5.0.0
 
-  run-applescript@7.1.0: {}
-
-  run-parallel@1.2.0:
+  retext-stringify@4.0.0:
     dependencies:
-      queue-microtask: 1.2.3
-
-  rw@1.3.3: {}
+      '@types/nlcst': 2.0.3
+      nlcst-to-string: 4.0.0
+      unified: 11.0.5
 
-  sade@1.8.1:
+  retext@9.0.0:
     dependencies:
-      mri: 1.2.0
-
-  safe-buffer@5.1.2: {}
-
-  safe-buffer@5.2.1: {}
+      '@types/nlcst': 2.0.3
+      retext-latin: 4.0.0
+      retext-stringify: 4.0.0
+      unified: 11.0.5
 
-  safe-stable-stringify@1.1.1: {}
+  reusify@1.1.0: {}
 
-  safer-buffer@2.1.2: {}
+  run-async@3.0.0: {}
 
-  sass-loader@16.0.8(@rspack/core@1.7.11(@swc/helpers@0.5.23))(sass@1.101.0)(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)):
+  run-parallel@1.2.0:
     dependencies:
-      neo-async: 2.6.2
-    optionalDependencies:
-      '@rspack/core': 1.7.11(@swc/helpers@0.5.23)
-      sass: 1.101.0
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
+      queue-microtask: 1.2.3
 
-  sass@1.101.0:
+  rxjs@7.8.2:
     dependencies:
-      chokidar: 5.0.0
-      immutable: 5.1.6
-      source-map-js: 1.2.1
-    optionalDependencies:
-      '@parcel/watcher': 2.5.6
-
-  sax@1.6.0: {}
+      tslib: 2.8.1
 
-  scheduler@0.27.0: {}
+  safe-array-concat@1.1.4:
+    dependencies:
+      call-bind: 1.0.9
+      call-bound: 1.0.4
+      get-intrinsic: 1.3.0
+      has-symbols: 1.1.0
+      isarray: 2.0.5
 
-  schema-dts@1.1.5: {}
+  safe-buffer@5.2.1: {}
 
-  schema-utils@3.3.0:
+  safe-push-apply@1.0.0:
     dependencies:
-      '@types/json-schema': 7.0.15
-      ajv: 6.15.0
-      ajv-keywords: 3.5.2(ajv@6.15.0)
+      es-errors: 1.3.0
+      isarray: 2.0.5
 
-  schema-utils@4.3.3:
+  safe-regex-test@1.1.0:
     dependencies:
-      '@types/json-schema': 7.0.15
-      ajv: 8.20.0
-      ajv-formats: 2.1.1(ajv@8.20.0)
-      ajv-keywords: 5.1.0(ajv@8.20.0)
-
-  screenfull@5.2.0: {}
-
-  search-insights@2.17.3: {}
+      call-bound: 1.0.4
+      es-errors: 1.3.0
+      is-regex: 1.2.1
 
-  section-matter@1.0.0:
-    dependencies:
-      extend-shallow: 2.0.1
-      kind-of: 6.0.3
+  safe-stable-stringify@1.1.1: {}
 
-  select-hose@2.0.0: {}
+  safer-buffer@2.1.2: {}
 
-  selfsigned@5.5.0:
+  satori@0.33.5:
     dependencies:
-      '@peculiar/x509': 1.14.3
-      pkijs: 3.4.0
+      '@shuding/opentype.js': 1.4.0-beta.0
+      css-background-parser: 0.1.0
+      css-box-shadow: 1.0.0-3
+      css-gradient-parser: 0.0.17
+      css-to-react-native: 3.2.0
+      emoji-regex-xs: 2.0.1
+      escape-html: 1.0.3
+      fflate: 0.7.3
+      harfbuzzjs: 0.10.0
+      linebreak: 1.1.0
+      parse-css-color: 0.2.1
+      postcss-value-parser: 4.2.0
+      yoga-layout: 3.2.1
 
-  semver-diff@4.0.0:
-    dependencies:
-      semver: 7.8.3
+  sax@1.6.1: {}
 
-  semver@6.3.1: {}
+  scheduler@0.26.0: {}
 
-  semver@7.7.1: {}
+  scheduler@0.28.0: {}
 
-  semver@7.8.3: {}
+  semver@7.7.4:
+    optional: true
 
   semver@7.8.5: {}
 
@@ -17510,31 +7650,10 @@ snapshots:
     transitivePeerDependencies:
       - supports-color
 
-  serialize-javascript@6.0.2:
-    dependencies:
-      randombytes: 2.1.0
-
-  serve-handler@6.1.7:
-    dependencies:
-      bytes: 3.0.0
-      content-disposition: 0.5.2
-      mime-types: 2.1.18
-      minimatch: 3.1.5
-      path-is-inside: 1.0.2
-      path-to-regexp: 3.3.0
-      range-parser: 1.2.0
-
-  serve-index@1.9.2:
+  serialize-error@13.0.2:
     dependencies:
-      accepts: 1.3.8
-      batch: 0.6.1
-      debug: 2.6.9
-      escape-html: 1.0.3
-      http-errors: 1.8.1
-      mime-types: 2.1.35
-      parseurl: 1.3.3
-    transitivePeerDependencies:
-      - supports-color
+      non-error: 0.1.0
+      type-fest: 5.10.0
 
   serve-static@1.16.3:
     dependencies:
@@ -17554,55 +7673,69 @@ snapshots:
       gopd: 1.2.0
       has-property-descriptors: 1.0.2
 
-  set-harmonic-interval@1.0.1: {}
-
-  setprototypeof@1.2.0: {}
-
-  shallow-clone@3.0.1:
+  set-function-name@2.0.2:
     dependencies:
-      kind-of: 6.0.3
-
-  shallowequal@1.1.0: {}
+      define-data-property: 1.1.4
+      es-errors: 1.3.0
+      functions-have-names: 1.2.3
+      has-property-descriptors: 1.0.2
 
-  shebang-command@2.0.0:
+  set-proto@1.0.0:
     dependencies:
-      shebang-regex: 3.0.0
-
-  shebang-regex@3.0.0: {}
-
-  shell-quote@1.8.4: {}
+      dunder-proto: 1.0.1
+      es-errors: 1.3.0
+      es-object-atoms: 1.1.2
 
-  shelljs@0.8.5:
-    dependencies:
-      glob: 7.2.3
-      interpret: 1.4.0
-      rechoir: 0.6.2
+  setprototypeof@1.2.0: {}
 
-  should-equal@2.0.0:
+  sharp-ico@0.1.5:
     dependencies:
-      should-type: 1.4.0
+      decode-ico: 0.4.1
+      ico-endec: 0.1.6
+      sharp: 0.33.5
 
-  should-format@3.0.3:
+  sharp@0.33.5:
     dependencies:
-      should-type: 1.4.0
-      should-type-adaptors: 1.1.0
+      color: 4.2.3
+      detect-libc: 2.1.2
+      semver: 7.8.5
+    optionalDependencies:
+      '@img/sharp-darwin-arm64': 0.33.5
+      '@img/sharp-darwin-x64': 0.33.5
+      '@img/sharp-libvips-darwin-arm64': 1.0.4
+      '@img/sharp-libvips-darwin-x64': 1.0.4
+      '@img/sharp-libvips-linux-arm': 1.0.5
+      '@img/sharp-libvips-linux-arm64': 1.0.4
+      '@img/sharp-libvips-linux-s390x': 1.0.4
+      '@img/sharp-libvips-linux-x64': 1.0.4
+      '@img/sharp-libvips-linuxmusl-arm64': 1.0.4
+      '@img/sharp-libvips-linuxmusl-x64': 1.0.4
+      '@img/sharp-linux-arm': 0.33.5
+      '@img/sharp-linux-arm64': 0.33.5
+      '@img/sharp-linux-s390x': 0.33.5
+      '@img/sharp-linux-x64': 0.33.5
+      '@img/sharp-linuxmusl-arm64': 0.33.5
+      '@img/sharp-linuxmusl-x64': 0.33.5
+      '@img/sharp-wasm32': 0.33.5
+      '@img/sharp-win32-ia32': 0.33.5
+      '@img/sharp-win32-x64': 0.33.5
 
-  should-type-adaptors@1.1.0:
+  shebang-command@2.0.0:
     dependencies:
-      should-type: 1.4.0
-      should-util: 1.0.1
-
-  should-type@1.4.0: {}
+      shebang-regex: 3.0.0
 
-  should-util@1.0.1: {}
+  shebang-regex@3.0.0: {}
 
-  should@13.2.3:
+  shiki@3.23.0:
     dependencies:
-      should-equal: 2.0.0
-      should-format: 3.0.3
-      should-type: 1.4.0
-      should-type-adaptors: 1.1.0
-      should-util: 1.0.1
+      '@shikijs/core': 3.23.0
+      '@shikijs/engine-javascript': 3.23.0
+      '@shikijs/engine-oniguruma': 3.23.0
+      '@shikijs/langs': 3.23.0
+      '@shikijs/themes': 3.23.0
+      '@shikijs/types': 3.23.0
+      '@shikijs/vscode-textmate': 10.0.2
+      '@types/hast': 3.0.5
 
   side-channel-list@1.0.1:
     dependencies:
@@ -17634,108 +7767,80 @@ snapshots:
 
   signal-exit@3.0.7: {}
 
-  sirv@2.0.4:
-    dependencies:
-      '@polka/url': 1.0.0-next.29
-      mrmime: 2.0.1
-      totalist: 3.0.1
-
-  sisteransi@1.0.5: {}
+  signal-exit@4.1.0: {}
 
-  sitemap@7.1.3:
-    dependencies:
-      '@types/node': 17.0.45
-      '@types/sax': 1.2.7
-      arg: 5.0.2
-      sax: 1.6.0
+  simple-concat@1.0.1:
+    optional: true
 
-  skin-tone@2.0.0:
+  simple-get@4.0.1:
     dependencies:
-      unicode-emoji-modifier-base: 1.0.0
-
-  slash@3.0.0: {}
-
-  slash@4.0.0: {}
-
-  slugify@1.6.9: {}
+      decompress-response: 6.0.0
+      once: 1.4.0
+      simple-concat: 1.0.1
+    optional: true
 
-  snake-case@3.0.4:
+  simple-swizzle@0.2.4:
     dependencies:
-      dot-case: 3.0.4
-      tslib: 2.8.1
+      is-arrayish: 0.3.4
 
-  sockjs@0.3.24:
+  slice-ansi@5.0.0:
     dependencies:
-      faye-websocket: 0.11.4
-      uuid: 8.3.2
-      websocket-driver: 0.7.5
-
-  sort-css-media-queries@2.2.0: {}
-
-  source-map-js@1.2.1: {}
+      ansi-styles: 6.2.3
+      is-fullwidth-code-point: 4.0.0
 
-  source-map-support@0.5.21:
+  slice-ansi@7.1.2:
     dependencies:
-      buffer-from: 1.1.2
-      source-map: 0.6.1
-
-  source-map@0.5.6: {}
-
-  source-map@0.6.1: {}
-
-  source-map@0.7.6: {}
-
-  space-separated-tokens@1.1.5: {}
-
-  space-separated-tokens@2.0.2: {}
+      ansi-styles: 6.2.3
+      is-fullwidth-code-point: 5.1.0
 
-  spdy-transport@3.0.0:
+  socket.io-adapter@2.5.8:
     dependencies:
       debug: 4.4.3
-      detect-node: 2.1.0
-      hpack.js: 2.1.6
-      obuf: 1.1.2
-      readable-stream: 3.6.2
-      wbuf: 1.7.3
+      ws: 8.21.3
     transitivePeerDependencies:
+      - bufferutil
       - supports-color
+      - utf-8-validate
 
-  spdy@4.0.2:
+  socket.io-parser@4.2.7:
     dependencies:
+      '@socket.io/component-emitter': 3.1.2
       debug: 4.4.3
-      handle-thing: 2.0.1
-      http-deceiver: 1.2.7
-      select-hose: 2.0.0
-      spdy-transport: 3.0.0
     transitivePeerDependencies:
       - supports-color
 
-  sprintf-js@1.0.3: {}
+  socket.io@4.8.0:
+    dependencies:
+      accepts: 1.3.8
+      base64id: 2.0.0
+      cors: 2.8.6
+      debug: 4.3.7
+      engine.io: 6.6.11
+      socket.io-adapter: 2.5.8
+      socket.io-parser: 4.2.7
+    transitivePeerDependencies:
+      - bufferutil
+      - supports-color
+      - utf-8-validate
 
-  srcset@4.0.0: {}
+  source-map-js@1.2.2: {}
 
-  stack-generator@2.0.10:
-    dependencies:
-      stackframe: 1.3.4
+  source-map@0.7.6: {}
 
-  stackframe@1.3.4: {}
+  space-separated-tokens@2.0.2: {}
 
-  stacktrace-gps@3.1.2:
-    dependencies:
-      source-map: 0.5.6
-      stackframe: 1.3.4
+  sprintf-js@1.0.3: {}
 
-  stacktrace-js@2.0.2:
+  stack-utils@2.0.6:
     dependencies:
-      error-stack-parser: 2.1.4
-      stack-generator: 2.0.10
-      stacktrace-gps: 3.1.2
-
-  statuses@1.5.0: {}
+      escape-string-regexp: 2.0.0
 
   statuses@2.0.2: {}
 
-  std-env@3.10.0: {}
+  stop-iteration-iterator@1.1.0:
+    dependencies:
+      es-errors: 1.3.0
+      internal-slot: 1.1.0
 
   string-width@4.2.3:
     dependencies:
@@ -17743,37 +7848,48 @@ snapshots:
       is-fullwidth-code-point: 3.0.0
       strip-ansi: 6.0.1
 
-  string-width@5.1.2:
-    dependencies:
-      eastasianwidth: 0.2.0
-      emoji-regex: 9.2.2
-      strip-ansi: 7.2.0
-
   string-width@7.2.0:
     dependencies:
       emoji-regex: 10.6.0
       get-east-asian-width: 1.6.0
       strip-ansi: 7.2.0
 
-  string_decoder@1.1.1:
+  string.prototype.codepointat@0.2.1: {}
+
+  string.prototype.trim@1.2.11:
+    dependencies:
+      call-bind: 1.0.9
+      call-bound: 1.0.4
+      define-data-property: 1.1.4
+      define-properties: 1.2.1
+      es-abstract: 1.24.2
+      es-object-atoms: 1.1.2
+      has-property-descriptors: 1.0.2
+      safe-regex-test: 1.1.0
+
+  string.prototype.trimend@1.0.10:
+    dependencies:
+      call-bind: 1.0.9
+      call-bound: 1.0.4
+      define-properties: 1.2.1
+      es-object-atoms: 1.1.2
+
+  string.prototype.trimstart@1.0.8:
     dependencies:
-      safe-buffer: 5.1.2
+      call-bind: 1.0.9
+      define-properties: 1.2.1
+      es-object-atoms: 1.1.2
 
   string_decoder@1.3.0:
     dependencies:
       safe-buffer: 5.2.1
+    optional: true
 
   stringify-entities@4.0.4:
     dependencies:
       character-entities-html4: 2.1.0
       character-entities-legacy: 3.0.0
 
-  stringify-object@3.3.0:
-    dependencies:
-      get-own-enumerable-property-symbols: 3.0.2
-      is-obj: 1.0.1
-      is-regexp: 1.0.0
-
   strip-ansi@6.0.1:
     dependencies:
       ansi-regex: 5.0.1
@@ -17782,13 +7898,12 @@ snapshots:
     dependencies:
       ansi-regex: 6.2.2
 
-  strip-bom-string@1.0.0: {}
-
-  strip-final-newline@2.0.0: {}
-
-  strip-json-comments@2.0.1: {}
+  strip-json-comments@2.0.1:
+    optional: true
 
-  strip-json-comments@3.1.1: {}
+  strnum@2.5.1:
+    dependencies:
+      anynum: 1.0.1
 
   style-to-js@1.1.21:
     dependencies:
@@ -17802,13 +7917,15 @@ snapshots:
     dependencies:
       inline-style-parser: 0.2.7
 
-  stylehacks@6.1.1(postcss@8.5.15):
+  sucrase@3.34.0:
     dependencies:
-      browserslist: 4.28.2
-      postcss: 8.5.15
-      postcss-selector-parser: 6.1.2
-
-  stylis@4.4.0: {}
+      '@jridgewell/gen-mapping': 0.3.13
+      commander: 4.1.1
+      glob: 7.1.6
+      lines-and-columns: 1.2.4
+      mz: 2.7.0
+      pirates: 4.0.7
+      ts-interface-checker: 0.1.13
 
   sucrase@3.35.1:
     dependencies:
@@ -17820,96 +7937,61 @@ snapshots:
       tinyglobby: 0.2.17
       ts-interface-checker: 0.1.13
 
-  supports-color@7.2.0:
-    dependencies:
-      has-flag: 4.0.0
-
-  supports-color@8.1.1:
-    dependencies:
-      has-flag: 4.0.0
-
   supports-preserve-symlinks-flag@1.0.0: {}
 
-  svg-parser@2.0.4: {}
+  tagged-tag@1.0.0: {}
 
-  svgo@3.3.3:
+  tailwindcss@3.4.17:
     dependencies:
-      commander: 7.2.0
-      css-select: 5.2.2
-      css-tree: 2.3.1
-      css-what: 6.2.2
-      csso: 5.0.5
+      '@alloc/quick-lru': 5.3.0
+      arg: 5.0.2
+      chokidar: 3.6.0
+      didyoumean: 1.2.2
+      dlv: 1.1.3
+      fast-glob: 3.3.3
+      glob-parent: 6.0.2
+      is-glob: 4.0.3
+      jiti: 1.21.7
+      lilconfig: 3.1.4
+      micromatch: 4.0.8
+      normalize-path: 3.0.0
+      object-hash: 3.0.0
       picocolors: 1.1.1
-      sax: 1.6.0
-
-  swagger2openapi@7.0.8:
-    dependencies:
-      call-me-maybe: 1.0.2
-      node-fetch: 2.7.0
-      node-fetch-h2: 2.3.0
-      node-readfiles: 0.2.0
-      oas-kit-common: 1.0.8
-      oas-resolver: 2.5.6
-      oas-schema-walker: 1.1.5
-      oas-validator: 5.0.8
-      reftools: 1.1.9
-      yaml: 1.10.3
-      yargs: 17.7.3
+      postcss: 8.5.23
+      postcss-import: 15.1.0(postcss@8.5.23)
+      postcss-js: 4.1.0(postcss@8.5.23)
+      postcss-load-config: 4.0.2(postcss@8.5.23)
+      postcss-nested: 6.2.0(postcss@8.5.23)
+      postcss-selector-parser: 6.1.4
+      resolve: 1.22.13
+      sucrase: 3.35.1
     transitivePeerDependencies:
-      - encoding
-
-  swc-loader@0.2.7(@swc/core@1.15.41(@swc/helpers@0.5.23))(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)):
-    dependencies:
-      '@swc/core': 1.15.41(@swc/helpers@0.5.23)
-      '@swc/counter': 0.1.3
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
-
-  tapable@2.3.3: {}
-
-  terser-webpack-plugin@5.6.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(@swc/html@1.15.40)(lightningcss@1.32.0)(postcss@8.5.15)(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)):
-    dependencies:
-      '@jridgewell/trace-mapping': 0.3.31
-      jest-worker: 27.5.1
-      schema-utils: 4.3.3
-      terser: 5.48.0
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
-    optionalDependencies:
-      '@swc/core': 1.15.41(@swc/helpers@0.5.23)
-      '@swc/html': 1.15.40
-      lightningcss: 1.32.0
-      postcss: 8.5.15
+      - ts-node
 
-  terser-webpack-plugin@5.6.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(clean-css@5.3.3)(cssnano@6.1.2(postcss@8.5.15))(html-minifier-terser@7.2.0)(postcss@8.5.15)(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)):
+  tar-fs@2.1.5:
     dependencies:
-      '@jridgewell/trace-mapping': 0.3.31
-      jest-worker: 27.5.1
-      schema-utils: 4.3.3
-      terser: 5.48.0
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
-    optionalDependencies:
-      '@swc/core': 1.15.41(@swc/helpers@0.5.23)
-      clean-css: 5.3.3
-      cssnano: 6.1.2(postcss@8.5.15)
-      html-minifier-terser: 7.2.0
-      postcss: 8.5.15
+      chownr: 1.1.4
+      mkdirp-classic: 0.5.3
+      pump: 3.0.4
+      tar-stream: 2.2.0
+    optional: true
 
-  terser-webpack-plugin@5.6.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)):
+  tar-stream@2.2.0:
     dependencies:
-      '@jridgewell/trace-mapping': 0.3.31
-      jest-worker: 27.5.1
-      schema-utils: 4.3.3
-      terser: 5.48.0
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
-    optionalDependencies:
-      '@swc/core': 1.15.41(@swc/helpers@0.5.23)
-      postcss: 8.5.15
+      bl: 4.1.0
+      end-of-stream: 1.4.5
+      fs-constants: 1.0.0
+      inherits: 2.0.4
+      readable-stream: 3.6.2
+    optional: true
 
-  terser@5.48.0:
+  tar@7.5.21:
     dependencies:
-      '@jridgewell/source-map': 0.3.11
-      acorn: 8.16.0
-      commander: 2.20.3
-      source-map-support: 0.5.21
+      '@isaacs/fs-minipass': 4.0.1
+      chownr: 3.0.0
+      minipass: 7.1.3
+      minizlib: 3.1.0
+      yallist: 5.0.0
 
   thenify-all@1.6.0:
     dependencies:
@@ -17919,119 +8001,110 @@ snapshots:
     dependencies:
       any-promise: 1.3.0
 
-  thingies@2.6.0(tslib@2.8.1):
-    dependencies:
-      tslib: 2.8.1
-
-  throttle-debounce@3.0.1: {}
-
-  thunky@1.1.0: {}
-
-  tiny-invariant@1.3.3: {}
-
-  tiny-warning@1.0.3: {}
-
-  tinyexec@1.2.4: {}
+  tiny-inflate@1.0.3: {}
 
   tinyglobby@0.2.17:
     dependencies:
-      fdir: 6.5.0(picomatch@4.0.4)
-      picomatch: 4.0.4
+      fdir: 6.5.0(picomatch@4.0.7)
+      picomatch: 4.0.7
 
-  tinypool@1.1.1: {}
+  to-data-view@1.1.0: {}
 
   to-regex-range@5.0.1:
     dependencies:
       is-number: 7.0.0
 
-  toggle-selection@1.0.6: {}
-
   toidentifier@1.0.1: {}
 
-  totalist@3.0.1: {}
-
   tr46@0.0.3: {}
 
-  tree-dump@1.1.0(tslib@2.8.1):
-    dependencies:
-      tslib: 2.8.1
-
   trim-lines@3.0.1: {}
 
-  trough@1.0.5: {}
+  trim-trailing-lines@2.1.0: {}
 
   trough@2.2.0: {}
 
-  ts-algebra@1.2.2: {}
-
-  ts-api-utils@1.4.3(typescript@6.0.3):
-    dependencies:
-      typescript: 6.0.3
-
-  ts-dedent@2.2.0: {}
-
-  ts-easing@0.2.0: {}
-
   ts-interface-checker@0.1.13: {}
 
-  ts-keycode-enum@1.0.6: {}
-
   tslib@1.14.1: {}
 
   tslib@2.8.1: {}
 
-  tsutils@3.21.0(typescript@6.0.3):
+  tunnel-agent@0.6.0:
     dependencies:
-      tslib: 1.14.1
-      typescript: 6.0.3
+      safe-buffer: 5.2.1
+    optional: true
 
-  tsyringe@4.10.0:
-    dependencies:
-      tslib: 1.14.1
+  twoslash-protocol@0.3.9: {}
 
-  type-check@0.4.0:
+  twoslash@0.3.9(typescript@6.0.3):
     dependencies:
-      prelude-ls: 1.2.1
+      '@typescript/vfs': 1.6.5(typescript@6.0.3)
+      twoslash-protocol: 0.3.9
+      typescript: 6.0.3
+    transitivePeerDependencies:
+      - supports-color
 
-  type-fest@1.4.0: {}
+  type-fest@0.21.3: {}
 
-  type-fest@2.19.0: {}
+  type-fest@4.41.0: {}
+
+  type-fest@5.10.0:
+    dependencies:
+      tagged-tag: 1.0.0
 
   type-is@1.6.18:
     dependencies:
       media-typer: 0.3.0
       mime-types: 2.1.35
 
-  typedarray-to-buffer@3.1.5:
+  typed-array-buffer@1.0.3:
     dependencies:
-      is-typedarray: 1.0.0
+      call-bound: 1.0.4
+      es-errors: 1.3.0
+      is-typed-array: 1.1.15
 
-  typescript@6.0.3: {}
+  typed-array-byte-length@1.0.3:
+    dependencies:
+      call-bind: 1.0.9
+      for-each: 0.3.5
+      gopd: 1.2.0
+      has-proto: 1.2.0
+      is-typed-array: 1.1.15
 
-  undici-types@7.24.6: {}
+  typed-array-byte-offset@1.0.5:
+    dependencies:
+      available-typed-arrays: 1.0.7
+      call-bind: 1.0.9
+      for-each: 0.3.5
+      gopd: 1.2.0
+      is-typed-array: 1.1.15
+      reflect.getprototypeof: 1.0.10
 
-  unicode-canonical-property-names-ecmascript@2.0.1: {}
+  typed-array-length@1.0.8:
+    dependencies:
+      call-bind: 1.0.9
+      for-each: 0.3.5
+      gopd: 1.2.0
+      is-typed-array: 1.1.15
+      possible-typed-array-names: 1.1.0
+      reflect.getprototypeof: 1.0.10
 
-  unicode-emoji-modifier-base@1.0.0: {}
+  typescript@6.0.3: {}
 
-  unicode-match-property-ecmascript@2.0.0:
+  unbox-primitive@1.1.0:
     dependencies:
-      unicode-canonical-property-names-ecmascript: 2.0.1
-      unicode-property-aliases-ecmascript: 2.2.0
-
-  unicode-match-property-value-ecmascript@2.2.1: {}
+      call-bound: 1.0.4
+      has-bigints: 1.1.0
+      has-symbols: 1.1.0
+      which-boxed-primitive: 1.1.1
 
-  unicode-property-aliases-ecmascript@2.2.0: {}
+  undici-types@8.9.0: {}
 
-  unified@10.1.2:
+  unicode-trie@2.0.0:
     dependencies:
-      '@types/unist': 2.0.11
-      bail: 2.0.2
-      extend: 3.0.2
-      is-buffer: 2.0.5
-      is-plain-obj: 4.1.0
-      trough: 2.2.0
-      vfile: 5.3.7
+      pako: 0.2.9
+      tiny-inflate: 1.0.3
 
   unified@11.0.5:
     dependencies:
@@ -18043,33 +8116,15 @@ snapshots:
       trough: 2.2.0
       vfile: 6.0.3
 
-  unified@9.2.2:
-    dependencies:
-      '@types/unist': 2.0.11
-      bail: 1.0.5
-      extend: 3.0.2
-      is-buffer: 2.0.5
-      is-plain-obj: 2.1.0
-      trough: 1.0.5
-      vfile: 4.2.1
-
-  unique-string@3.0.0:
-    dependencies:
-      crypto-random-string: 4.0.0
-
-  unist-builder@3.0.1:
+  unist-builder@4.0.0:
     dependencies:
-      '@types/unist': 2.0.11
+      '@types/unist': 3.0.3
 
   unist-util-find-after@5.0.0:
     dependencies:
       '@types/unist': 3.0.3
       unist-util-is: 6.0.1
 
-  unist-util-generated@2.0.1: {}
-
-  unist-util-is@4.1.0: {}
-
   unist-util-is@5.2.1:
     dependencies:
       '@types/unist': 2.0.11
@@ -18078,67 +8133,56 @@ snapshots:
     dependencies:
       '@types/unist': 3.0.3
 
-  unist-util-position-from-estree@2.0.0:
+  unist-util-map@4.0.0:
     dependencies:
       '@types/unist': 3.0.3
 
-  unist-util-position@4.0.4:
-    dependencies:
-      '@types/unist': 2.0.11
-
-  unist-util-position@5.0.0:
+  unist-util-modify-children@4.0.0:
     dependencies:
       '@types/unist': 3.0.3
+      array-iterate: 2.0.1
 
-  unist-util-remove-position@5.0.0:
+  unist-util-position-from-estree@2.0.0:
     dependencies:
       '@types/unist': 3.0.3
-      unist-util-visit: 5.1.0
 
-  unist-util-select@4.0.3:
+  unist-util-position@5.0.0:
     dependencies:
-      '@types/unist': 2.0.11
-      css-selector-parser: 1.4.1
-      nth-check: 2.1.1
-      zwitch: 2.0.4
+      '@types/unist': 3.0.3
 
-  unist-util-stringify-position@2.0.3:
+  unist-util-remove-position@5.0.0:
     dependencies:
-      '@types/unist': 2.0.11
+      '@types/unist': 3.0.3
+      unist-util-visit: 5.0.0
 
-  unist-util-stringify-position@3.0.3:
+  unist-util-remove@4.0.0:
     dependencies:
-      '@types/unist': 2.0.11
+      '@types/unist': 3.0.3
+      unist-util-is: 6.0.1
+      unist-util-visit-parents: 6.0.1
 
   unist-util-stringify-position@4.0.0:
     dependencies:
       '@types/unist': 3.0.3
 
-  unist-util-visit-parents@3.1.1:
-    dependencies:
-      '@types/unist': 2.0.11
-      unist-util-is: 4.1.0
-
-  unist-util-visit-parents@4.1.1:
+  unist-util-visit-children@3.0.0:
     dependencies:
-      '@types/unist': 2.0.11
-      unist-util-is: 5.2.1
+      '@types/unist': 3.0.3
 
   unist-util-visit-parents@5.1.3:
     dependencies:
       '@types/unist': 2.0.11
       unist-util-is: 5.2.1
 
-  unist-util-visit-parents@6.0.2:
+  unist-util-visit-parents@6.0.1:
     dependencies:
       '@types/unist': 3.0.3
       unist-util-is: 6.0.1
 
-  unist-util-visit@3.1.0:
+  unist-util-visit-parents@6.0.2:
     dependencies:
-      '@types/unist': 2.0.11
-      unist-util-is: 5.2.1
-      unist-util-visit-parents: 4.1.1
+      '@types/unist': 3.0.3
+      unist-util-is: 6.0.1
 
   unist-util-visit@4.1.2:
     dependencies:
@@ -18146,7 +8190,7 @@ snapshots:
       unist-util-is: 5.2.1
       unist-util-visit-parents: 5.1.3
 
-  unist-util-visit@5.1.0:
+  unist-util-visit@5.0.0:
     dependencies:
       '@types/unist': 3.0.3
       unist-util-is: 6.0.1
@@ -18156,79 +8200,27 @@ snapshots:
 
   unpipe@1.0.0: {}
 
-  update-browserslist-db@1.2.3(browserslist@4.28.2):
-    dependencies:
-      browserslist: 4.28.2
-      escalade: 3.2.0
-      picocolors: 1.1.1
-
-  update-notifier@6.0.2:
-    dependencies:
-      boxen: 7.1.1
-      chalk: 5.6.2
-      configstore: 6.0.0
-      has-yarn: 3.0.0
-      import-lazy: 4.0.0
-      is-ci: 3.0.1
-      is-installed-globally: 0.4.0
-      is-npm: 6.1.0
-      is-yarn-global: 0.4.1
-      latest-version: 7.0.0
-      pupa: 3.3.0
-      semver: 7.8.3
-      semver-diff: 4.0.0
-      xdg-basedir: 5.1.0
-
   uri-js@4.4.1:
     dependencies:
       punycode: 2.3.1
 
-  url-loader@4.1.1(file-loader@6.2.0(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)))(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)):
-    dependencies:
-      loader-utils: 2.0.4
-      mime-types: 2.1.35
-      schema-utils: 3.3.0
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
-    optionalDependencies:
-      file-loader: 6.2.0(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-
-  url@0.11.4:
-    dependencies:
-      punycode: 1.4.1
-      qs: 6.15.3
-
-  use-editable@2.3.3(react@19.2.7):
-    dependencies:
-      react: 19.2.7
-
-  use-resize-observer@9.1.0(react-dom@19.2.7(react@19.2.7))(react@19.2.7):
-    dependencies:
-      '@juggle/resize-observer': 3.4.0
-      react: 19.2.7
-      react-dom: 19.2.7(react@19.2.7)
+  urijs@1.19.11: {}
 
-  use-sync-external-store@1.6.0(react@19.2.7):
+  use-sync-external-store@1.7.0(react@19.2.3):
     dependencies:
-      react: 19.2.7
+      react: 19.2.3
 
   util-deprecate@1.0.2: {}
 
-  utila@0.4.0: {}
-
   utility-types@3.11.0: {}
 
   utils-merge@1.0.1: {}
 
-  uuid@14.0.1: {}
-
-  uuid@8.3.2: {}
+  uuid@11.1.1: {}
 
-  uvu@0.5.6:
-    dependencies:
-      dequal: 2.0.3
-      diff: 5.2.2
-      kleur: 4.1.5
-      sade: 1.8.1
+  valibot@1.5.0(typescript@6.0.3):
+    optionalDependencies:
+      typescript: 6.0.3
 
   validate.io-array@1.0.6: {}
 
@@ -18245,290 +8237,32 @@ snapshots:
 
   validate.io-number@1.0.3: {}
 
-  value-equal@1.0.1: {}
-
   vary@1.1.2: {}
 
-  vfile-location@4.1.0:
-    dependencies:
-      '@types/unist': 2.0.11
-      vfile: 5.3.7
-
   vfile-location@5.0.3:
     dependencies:
       '@types/unist': 3.0.3
       vfile: 6.0.3
 
-  vfile-message@2.0.4:
+  vfile-matter@5.0.1:
     dependencies:
-      '@types/unist': 2.0.11
-      unist-util-stringify-position: 2.0.3
-
-  vfile-message@3.1.4:
-    dependencies:
-      '@types/unist': 2.0.11
-      unist-util-stringify-position: 3.0.3
+      vfile: 6.0.3
+      yaml: 2.8.3
 
   vfile-message@4.0.3:
     dependencies:
       '@types/unist': 3.0.3
       unist-util-stringify-position: 4.0.0
 
-  vfile@4.2.1:
-    dependencies:
-      '@types/unist': 2.0.11
-      is-buffer: 2.0.5
-      unist-util-stringify-position: 2.0.3
-      vfile-message: 2.0.4
-
-  vfile@5.3.7:
-    dependencies:
-      '@types/unist': 2.0.11
-      is-buffer: 2.0.5
-      unist-util-stringify-position: 3.0.3
-      vfile-message: 3.1.4
-
   vfile@6.0.3:
     dependencies:
       '@types/unist': 3.0.3
       vfile-message: 4.0.3
 
-  warning@4.0.3:
-    dependencies:
-      loose-envify: 1.4.0
-
-  watchpack@2.5.1:
-    dependencies:
-      glob-to-regexp: 0.4.1
-      graceful-fs: 4.2.11
-
-  wbuf@1.7.3:
-    dependencies:
-      minimalistic-assert: 1.0.1
-
   web-namespaces@2.0.1: {}
 
   webidl-conversions@3.0.1: {}
 
-  webpack-bundle-analyzer@4.10.2:
-    dependencies:
-      '@discoveryjs/json-ext': 0.5.7
-      acorn: 8.16.0
-      acorn-walk: 8.3.5
-      commander: 7.2.0
-      debounce: 1.2.1
-      escape-string-regexp: 4.0.0
-      gzip-size: 6.0.0
-      html-escaper: 2.0.2
-      opener: 1.5.2
-      picocolors: 1.1.1
-      sirv: 2.0.4
-      ws: 7.5.11
-    transitivePeerDependencies:
-      - bufferutil
-      - utf-8-validate
-
-  webpack-dev-middleware@7.4.5(tslib@2.8.1)(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)):
-    dependencies:
-      colorette: 2.0.20
-      memfs: 4.57.6(tslib@2.8.1)
-      mime-types: 3.0.2
-      on-finished: 2.4.1
-      range-parser: 1.2.1
-      schema-utils: 4.3.3
-    optionalDependencies:
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
-    transitivePeerDependencies:
-      - tslib
-
-  webpack-dev-server@5.2.4(tslib@2.8.1)(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)):
-    dependencies:
-      '@types/bonjour': 3.5.13
-      '@types/connect-history-api-fallback': 1.5.4
-      '@types/express': 4.17.25
-      '@types/express-serve-static-core': 4.19.8
-      '@types/serve-index': 1.9.4
-      '@types/serve-static': 1.15.10
-      '@types/sockjs': 0.3.36
-      '@types/ws': 8.18.1
-      ansi-html-community: 0.0.8
-      bonjour-service: 1.4.0
-      chokidar: 3.6.0
-      colorette: 2.0.20
-      compression: 1.8.1
-      connect-history-api-fallback: 2.0.0
-      express: 4.22.2
-      graceful-fs: 4.2.11
-      http-proxy-middleware: 2.0.9(@types/express@4.17.25)
-      ipaddr.js: 2.4.0
-      launch-editor: 2.14.1
-      open: 10.2.0
-      p-retry: 6.2.1
-      schema-utils: 4.3.3
-      selfsigned: 5.5.0
-      serve-index: 1.9.2
-      sockjs: 0.3.24
-      spdy: 4.0.2
-      webpack-dev-middleware: 7.4.5(tslib@2.8.1)(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      ws: 8.21.0
-    optionalDependencies:
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
-    transitivePeerDependencies:
-      - bufferutil
-      - debug
-      - supports-color
-      - tslib
-      - utf-8-validate
-
-  webpack-merge@5.10.0:
-    dependencies:
-      clone-deep: 4.0.1
-      flat: 5.0.2
-      wildcard: 2.0.1
-
-  webpack-merge@6.0.1:
-    dependencies:
-      clone-deep: 4.0.1
-      flat: 5.0.2
-      wildcard: 2.0.1
-
-  webpack-sources@3.5.0: {}
-
-  webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(@swc/html@1.15.40)(lightningcss@1.32.0)(postcss@8.5.15):
-    dependencies:
-      '@types/estree': 1.0.9
-      '@types/json-schema': 7.0.15
-      '@webassemblyjs/ast': 1.14.1
-      '@webassemblyjs/wasm-edit': 1.14.1
-      '@webassemblyjs/wasm-parser': 1.14.1
-      acorn: 8.16.0
-      acorn-import-phases: 1.0.4(acorn@8.16.0)
-      browserslist: 4.28.2
-      chrome-trace-event: 1.0.4
-      enhanced-resolve: 5.23.0
-      es-module-lexer: 2.1.0
-      eslint-scope: 5.1.1
-      events: 3.3.0
-      glob-to-regexp: 0.4.1
-      graceful-fs: 4.2.11
-      loader-runner: 4.3.2
-      mime-db: 1.54.0
-      neo-async: 2.6.2
-      schema-utils: 4.3.3
-      tapable: 2.3.3
-      terser-webpack-plugin: 5.6.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(@swc/html@1.15.40)(lightningcss@1.32.0)(postcss@8.5.15)(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      watchpack: 2.5.1
-      webpack-sources: 3.5.0
-    transitivePeerDependencies:
-      - '@minify-html/node'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - clean-css
-      - cssnano
-      - csso
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - uglify-js
-
-  webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(clean-css@5.3.3)(cssnano@6.1.2(postcss@8.5.15))(html-minifier-terser@7.2.0)(postcss@8.5.15):
-    dependencies:
-      '@types/estree': 1.0.9
-      '@types/json-schema': 7.0.15
-      '@webassemblyjs/ast': 1.14.1
-      '@webassemblyjs/wasm-edit': 1.14.1
-      '@webassemblyjs/wasm-parser': 1.14.1
-      acorn: 8.16.0
-      acorn-import-phases: 1.0.4(acorn@8.16.0)
-      browserslist: 4.28.2
-      chrome-trace-event: 1.0.4
-      enhanced-resolve: 5.23.0
-      es-module-lexer: 2.1.0
-      eslint-scope: 5.1.1
-      events: 3.3.0
-      glob-to-regexp: 0.4.1
-      graceful-fs: 4.2.11
-      loader-runner: 4.3.2
-      mime-db: 1.54.0
-      neo-async: 2.6.2
-      schema-utils: 4.3.3
-      tapable: 2.3.3
-      terser-webpack-plugin: 5.6.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(clean-css@5.3.3)(cssnano@6.1.2(postcss@8.5.15))(html-minifier-terser@7.2.0)(postcss@8.5.15)(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      watchpack: 2.5.1
-      webpack-sources: 3.5.0
-    transitivePeerDependencies:
-      - '@minify-html/node'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - clean-css
-      - cssnano
-      - csso
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - uglify-js
-
-  webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15):
-    dependencies:
-      '@types/estree': 1.0.9
-      '@types/json-schema': 7.0.15
-      '@webassemblyjs/ast': 1.14.1
-      '@webassemblyjs/wasm-edit': 1.14.1
-      '@webassemblyjs/wasm-parser': 1.14.1
-      acorn: 8.16.0
-      acorn-import-phases: 1.0.4(acorn@8.16.0)
-      browserslist: 4.28.2
-      chrome-trace-event: 1.0.4
-      enhanced-resolve: 5.23.0
-      es-module-lexer: 2.1.0
-      eslint-scope: 5.1.1
-      events: 3.3.0
-      glob-to-regexp: 0.4.1
-      graceful-fs: 4.2.11
-      loader-runner: 4.3.2
-      mime-db: 1.54.0
-      neo-async: 2.6.2
-      schema-utils: 4.3.3
-      tapable: 2.3.3
-      terser-webpack-plugin: 5.6.1(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15))
-      watchpack: 2.5.1
-      webpack-sources: 3.5.0
-    transitivePeerDependencies:
-      - '@minify-html/node'
-      - '@swc/core'
-      - '@swc/css'
-      - '@swc/html'
-      - clean-css
-      - cssnano
-      - csso
-      - esbuild
-      - html-minifier-terser
-      - lightningcss
-      - postcss
-      - uglify-js
-
-  webpackbar@7.0.0(@rspack/core@1.7.11(@swc/helpers@0.5.23))(webpack@5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)):
-    dependencies:
-      ansis: 3.17.0
-      consola: 3.4.2
-      pretty-time: 1.1.0
-      std-env: 3.10.0
-    optionalDependencies:
-      '@rspack/core': 1.7.11(@swc/helpers@0.5.23)
-      webpack: 5.107.2(@swc/core@1.15.41(@swc/helpers@0.5.23))(postcss@8.5.15)
-
-  websocket-driver@0.7.5:
-    dependencies:
-      http-parser-js: 0.5.10
-      safe-buffer: 5.2.1
-      websocket-extensions: 0.1.4
-
-  websocket-extensions@0.1.4: {}
-
   whatwg-fetch@3.6.20: {}
 
   whatwg-url@5.0.0:
@@ -18536,31 +8270,66 @@ snapshots:
       tr46: 0.0.3
       webidl-conversions: 3.0.1
 
-  which@2.0.2:
+  which-boxed-primitive@1.1.1:
     dependencies:
-      isexe: 2.0.0
+      is-bigint: 1.1.0
+      is-boolean-object: 1.2.2
+      is-number-object: 1.1.1
+      is-string: 1.1.1
+      is-symbol: 1.1.1
 
-  widest-line@4.0.1:
+  which-builtin-type@1.2.1:
     dependencies:
-      string-width: 5.1.2
-
-  wildcard@2.0.1: {}
+      call-bound: 1.0.4
+      function.prototype.name: 1.2.0
+      has-tostringtag: 1.0.2
+      is-async-function: 2.1.1
+      is-date-object: 1.1.0
+      is-finalizationregistry: 1.1.1
+      is-generator-function: 1.1.2
+      is-regex: 1.2.1
+      is-weakref: 1.1.1
+      isarray: 2.0.5
+      which-boxed-primitive: 1.1.1
+      which-collection: 1.0.2
+      which-typed-array: 1.1.24
+
+  which-collection@1.0.2:
+    dependencies:
+      is-map: 2.0.3
+      is-set: 2.0.3
+      is-weakmap: 2.0.2
+      is-weakset: 2.0.4
+
+  which-typed-array@1.1.24:
+    dependencies:
+      available-typed-arrays: 1.0.7
+      call-bind: 1.0.9
+      call-bound: 1.0.4
+      for-each: 0.3.5
+      get-proto: 1.0.1
+      gopd: 1.2.0
+      has-tostringtag: 1.0.2
 
-  wolfy87-eventemitter@5.2.9: {}
+  which@2.0.2:
+    dependencies:
+      isexe: 2.0.0
 
-  word-wrap@1.2.5: {}
+  widest-line@5.0.0:
+    dependencies:
+      string-width: 7.2.0
 
-  wrap-ansi@7.0.0:
+  wrap-ansi@6.2.0:
     dependencies:
       ansi-styles: 4.3.0
       string-width: 4.2.3
       strip-ansi: 6.0.1
 
-  wrap-ansi@8.1.0:
+  wrap-ansi@7.0.0:
     dependencies:
-      ansi-styles: 6.2.3
-      string-width: 5.1.2
-      strip-ansi: 7.2.0
+      ansi-styles: 4.3.0
+      string-width: 4.2.3
+      strip-ansi: 6.0.1
 
   wrap-ansi@9.0.2:
     dependencies:
@@ -18570,52 +8339,35 @@ snapshots:
 
   wrappy@1.0.2: {}
 
-  write-file-atomic@3.0.3:
-    dependencies:
-      imurmurhash: 0.1.4
-      is-typedarray: 1.0.0
-      signal-exit: 3.0.7
-      typedarray-to-buffer: 3.1.5
+  ws@8.21.3: {}
 
-  ws@7.5.11: {}
+  ws@8.22.0: {}
 
-  ws@8.21.0: {}
+  xml-naming@0.3.0: {}
 
-  wsl-utils@0.1.0:
+  xml2js@0.6.2:
     dependencies:
-      is-wsl: 3.1.1
-
-  xdg-basedir@5.1.0: {}
+      sax: 1.6.1
+      xmlbuilder: 11.0.1
 
-  xml-formatter@3.7.0:
-    dependencies:
-      xml-parser-xo: 4.1.6
+  xmlbuilder@11.0.1: {}
 
-  xml-js@1.6.11:
+  xss@1.0.15:
     dependencies:
-      sax: 1.6.0
-
-  xml-parser-xo@4.1.6: {}
-
-  xtend@4.0.2: {}
+      commander: 2.20.3
+      cssfilter: 0.0.10
 
   y18n@5.0.8: {}
 
-  yallist@3.1.1: {}
-
-  yaml-ast-parser@0.0.43: {}
-
-  yaml@1.10.2: {}
+  yallist@5.0.0: {}
 
-  yaml@1.10.3: {}
-
-  yaml@2.9.0: {}
+  yaml@2.8.3: {}
 
   yargs-parser@21.1.1: {}
 
   yargs-parser@22.0.0: {}
 
-  yargs@17.7.3:
+  yargs@17.7.1:
     dependencies:
       cliui: 8.0.1
       escalade: 3.2.0
@@ -18634,14 +8386,16 @@ snapshots:
       y18n: 5.0.8
       yargs-parser: 22.0.0
 
-  yocto-queue@0.1.0: {}
+  yoctocolors-cjs@2.1.3: {}
 
-  yocto-queue@1.2.2: {}
+  yoga-layout@3.2.1: {}
 
-  zustand@3.7.2(react@19.2.7):
-    optionalDependencies:
-      react: 19.2.7
+  zod-to-json-schema@3.20.4(zod@3.24.0):
+    dependencies:
+      zod: 3.24.0
+
+  zod@3.24.0: {}
 
-  zwitch@1.0.5: {}
+  zod@4.3.6: {}
 
   zwitch@2.0.4: {}
diff --git a/pnpm-workspace.yaml b/pnpm-workspace.yaml
index 772223c31..0d0dc9831 100644
--- a/pnpm-workspace.yaml
+++ b/pnpm-workspace.yaml
@@ -3,17 +3,12 @@ blockExoticSubdeps: true
 strictDepBuilds: true
 
 allowBuilds:
-  '@parcel/watcher': true
-  '@swc/core': true
-  core-js: true
-  core-js-pure: true
-  postman-code-generators: true
-  protobufjs: true
+  '@scarf/scarf': false   # install telemetry
+  esbuild: true           # needed by mint dev
+  keytar: false           # OS keychain, only for `mint login`
+  sharp: false            # mint dev works without it
 
 trustPolicy: no-downgrade
 trustPolicyExclude:
   - 'detect-port@1.6.1'
   - 'semver@6.3.1'
-
-patchedDependencies:
-  '@stoplight/json-schema-viewer@4.16.4': patches/@stoplight__json-schema-viewer.patch
diff --git a/redirects.json b/redirects.json
new file mode 100644
index 000000000..a0e3716cf
--- /dev/null
+++ b/redirects.json
@@ -0,0 +1,6475 @@
+[
+  {
+    "source": "/assets/audits/2024-01-03%20-%20Veridise%20-%20stellar-core%20v20.0.0%20-%20soroban.pdf",
+    "destination": "/assets/audits/2024-01-03-veridise-stellar-core-v20.0.0-soroban.pdf"
+  },
+  {
+    "source": "/meeting-notes/tags",
+    "destination": "/meetings"
+  },
+  {
+    "source": "/assets/audits/2024-12-20%20-%20OtterSec%20-%20stellar-rpc%20commit%20a60044e.pdf",
+    "destination": "/assets/audits/2024-12-20-ottersec-stellar-rpc-commit-a60044e.pdf"
+  },
+  {
+    "source": "/assets/audits/2025-10-17%20-%20Oak%20-%20stellar-core%20v23.0.0%20-%20protocol%2023%20changes.pdf",
+    "destination": "/assets/audits/2025-10-17-oak-stellar-core-v23.0.0-protocol-23-changes.pdf"
+  },
+  {
+    "source": "/assets/audits/2025-11-13%20-%20Oak%20-%20stellar-core%20v24.0.0%20-%20protocol%2024%20changes.pdf",
+    "destination": "/assets/audits/2025-11-13-oak-stellar-core-v24.0.0-protocol-24-changes.pdf"
+  },
+  {
+    "source": "/assets/audits/2026-02-06%20-%20Runtime%20Verification%20-%20stellar-core%20v25.0.0%20-%20soroban%20environment.pdf",
+    "destination": "/assets/audits/2026-02-06-runtime-verification-stellar-core-v25.0.0-soroban-environment.pdf"
+  },
+  {
+    "source": "/assets/audits/2027-03-07%20-%20Halborn%20-%20bytes-lit%20v0.0.5.pdf",
+    "destination": "/assets/audits/2027-03-07-halborn-bytes-lit-v0.0.5.pdf"
+  },
+  {
+    "source": "/assets/audits/2027-03-07%20-%20Halborn%20-%20crates-git-revision%20v0.0.6.pdf",
+    "destination": "/assets/audits/2027-03-07-halborn-crates-git-revision-v0.0.6.pdf"
+  },
+  {
+    "source": "/assets/audits/2027-03-07%20-%20Halborn%20-%20soroban-poseidon%20v25.0.0.pdf",
+    "destination": "/assets/audits/2027-03-07-halborn-soroban-poseidon-v25.0.0.pdf"
+  },
+  {
+    "source": "/assets/audits/2027-03-07%20-%20Halborn%20-%20soroban-sdk%20v25.1.0.pdf",
+    "destination": "/assets/audits/2027-03-07-halborn-soroban-sdk-v25.1.0.pdf"
+  },
+  {
+    "source": "/assets/audits/2027-03-07%20-%20Halborn%20-%20stellar-strkey%20v0.0.13%20v0.0.16.pdf",
+    "destination": "/assets/audits/2027-03-07-halborn-stellar-strkey-v0.0.13-v0.0.16.pdf"
+  },
+  {
+    "source": "/docs/learn/glossary/accounts",
+    "destination": "/docs/learn/fundamentals/stellar-data-structures/accounts"
+  },
+  {
+    "source": "/docs/glossary/accounts",
+    "destination": "/docs/learn/fundamentals/stellar-data-structures/accounts"
+  },
+  {
+    "source": "/docs/learn/glossary/assets",
+    "destination": "/docs/learn/fundamentals/stellar-data-structures/assets"
+  },
+  {
+    "source": "/docs/glossary/assets",
+    "destination": "/docs/learn/fundamentals/stellar-data-structures/assets"
+  },
+  {
+    "source": "/docs/learn/glossary/channels",
+    "destination": "/docs/build/guides/transactions/channel-accounts"
+  },
+  {
+    "source": "/docs/glossary/channels",
+    "destination": "/docs/build/guides/transactions/channel-accounts"
+  },
+  {
+    "source": "/docs/learn/glossary/claimable-balance",
+    "destination": "/docs/build/guides/transactions/claimable-balances"
+  },
+  {
+    "source": "/docs/glossary/claimable-balance",
+    "destination": "/docs/build/guides/transactions/claimable-balances"
+  },
+  {
+    "source": "/docs/learn/glossary/clawback",
+    "destination": "/docs/build/guides/transactions/clawbacks"
+  },
+  {
+    "source": "/docs/glossary/clawback",
+    "destination": "/docs/build/guides/transactions/clawbacks"
+  },
+  {
+    "source": "/docs/learn/glossary/decentralized-exchange",
+    "destination": "/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools#sdex"
+  },
+  {
+    "source": "/docs/glossary/decentralized-exchange",
+    "destination": "/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools#sdex"
+  },
+  {
+    "source": "/docs/learn/glossary/federation",
+    "destination": "/docs/learn/glossary#federation"
+  },
+  {
+    "source": "/docs/glossary/federation",
+    "destination": "/docs/learn/glossary#federation"
+  },
+  {
+    "source": "/docs/learn/glossary/fee-bumps",
+    "destination": "/docs/build/guides/transactions/fee-bump-transactions"
+  },
+  {
+    "source": "/docs/glossary/fee-bumps",
+    "destination": "/docs/build/guides/transactions/fee-bump-transactions"
+  },
+  {
+    "source": "/docs/learn/glossary/fees",
+    "destination": "/docs/learn/fundamentals/fees-resource-limits-metering"
+  },
+  {
+    "source": "/docs/glossary/fees",
+    "destination": "/docs/learn/fundamentals/fees-resource-limits-metering"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/fees-surge-pricing-fee-strategies",
+    "destination": "/docs/learn/fundamentals/fees-resource-limits-metering"
+  },
+  {
+    "source": "/docs/encyclopedia/fees-surge-pricing-fee-strategies",
+    "destination": "/docs/learn/fundamentals/fees-resource-limits-metering"
+  },
+  {
+    "source": "/docs/learn/glossary/inflation",
+    "destination": "/docs/learn/glossary#inflation"
+  },
+  {
+    "source": "/docs/glossary/inflation",
+    "destination": "/docs/learn/glossary#inflation"
+  },
+  {
+    "source": "/docs/learn/glossary/ledger",
+    "destination": "/docs/learn/fundamentals/stellar-data-structures/ledgers"
+  },
+  {
+    "source": "/docs/glossary/ledger",
+    "destination": "/docs/learn/fundamentals/stellar-data-structures/ledgers"
+  },
+  {
+    "source": "/docs/learn/glossary/liquidity-pools",
+    "destination": "/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools#liquidity-pools"
+  },
+  {
+    "source": "/docs/glossary/liquidity-pools",
+    "destination": "/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools#liquidity-pools"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/liquidity-on-stellar-sdex-and-liquidity-pools/:slug*",
+    "destination": "/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools"
+  },
+  {
+    "source": "/docs/encyclopedia/liquidity-on-stellar-sdex-and-liquidity-pools/:slug*",
+    "destination": "/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools"
+  },
+  {
+    "source": "/docs/learn/glossary/lumen-supply",
+    "destination": "/docs/learn/fundamentals/lumens#lumen-supply-metrics"
+  },
+  {
+    "source": "/docs/glossary/lumen-supply",
+    "destination": "/docs/learn/fundamentals/lumens#lumen-supply-metrics"
+  },
+  {
+    "source": "/docs/learn/glossary/minimum-balance",
+    "destination": "/docs/learn/fundamentals/lumens#minimum-balance"
+  },
+  {
+    "source": "/docs/glossary/minimum-balance",
+    "destination": "/docs/learn/fundamentals/lumens#minimum-balance"
+  },
+  {
+    "source": "/docs/learn/glossary/multisig",
+    "destination": "/docs/learn/fundamentals/transactions/signatures-multisig"
+  },
+  {
+    "source": "/docs/glossary/multisig",
+    "destination": "/docs/learn/fundamentals/transactions/signatures-multisig"
+  },
+  {
+    "source": "/docs/learn/glossary/muxed-accounts",
+    "destination": "/docs/build/guides/transactions/pooled-accounts-muxed-accounts-memos"
+  },
+  {
+    "source": "/docs/glossary/muxed-accounts",
+    "destination": "/docs/build/guides/transactions/pooled-accounts-muxed-accounts-memos"
+  },
+  {
+    "source": "/docs/learn/glossary/network-passphrase",
+    "destination": "/docs/learn/glossary#passphrase"
+  },
+  {
+    "source": "/docs/glossary/network-passphrase",
+    "destination": "/docs/learn/glossary#passphrase"
+  },
+  {
+    "source": "/docs/learn/glossary/operations",
+    "destination": "/docs/learn/fundamentals/transactions/operations-and-transactions#operations"
+  },
+  {
+    "source": "/docs/glossary/operations",
+    "destination": "/docs/learn/fundamentals/transactions/operations-and-transactions#operations"
+  },
+  {
+    "source": "/docs/learn/glossary/scp",
+    "destination": "/docs/learn/fundamentals/stellar-consensus-protocol"
+  },
+  {
+    "source": "/docs/glossary/scp",
+    "destination": "/docs/learn/fundamentals/stellar-consensus-protocol"
+  },
+  {
+    "source": "/docs/learn/glossary/sponsored-reserves",
+    "destination": "/docs/build/guides/transactions/sponsored-reserves"
+  },
+  {
+    "source": "/docs/glossary/sponsored-reserves",
+    "destination": "/docs/build/guides/transactions/sponsored-reserves"
+  },
+  {
+    "source": "/docs/learn/glossary/testnet",
+    "destination": "/docs/networks"
+  },
+  {
+    "source": "/docs/glossary/testnet",
+    "destination": "/docs/networks"
+  },
+  {
+    "source": "/docs/learn/glossary/transactions",
+    "destination": "/docs/learn/fundamentals/transactions/operations-and-transactions"
+  },
+  {
+    "source": "/docs/glossary/transactions",
+    "destination": "/docs/learn/fundamentals/transactions/operations-and-transactions"
+  },
+  {
+    "source": "/docs/glossary/xdr",
+    "destination": "/docs/learn/fundamentals/data-format/xdr"
+  },
+  {
+    "source": "/docs/tools/sdks/library",
+    "destination": "/docs/tools/sdks"
+  },
+  {
+    "source": "/docs/software-and-sdks",
+    "destination": "/docs/tools/sdks"
+  },
+  {
+    "source": "/docs/tools-and-sdks/:slug*",
+    "destination": "/docs/tools/sdks/:slug*"
+  },
+  {
+    "source": "/docs/data/indexers/data-indexers",
+    "destination": "/docs/data/indexers"
+  },
+  {
+    "source": "/docs/tools/developer-tools/data-indexers",
+    "destination": "/docs/data/indexers"
+  },
+  {
+    "source": "/docs/data/indexers/indexer-providers/indexer-providers",
+    "destination": "/docs/data/indexers"
+  },
+  {
+    "source": "/docs/data/indexers/indexer-providers",
+    "destination": "/docs/data/indexers"
+  },
+  {
+    "source": "/docs/start/introduction",
+    "destination": "/docs"
+  },
+  {
+    "source": "/docs/start/list-of-operations",
+    "destination": "/docs/learn/fundamentals/transactions/list-of-operations"
+  },
+  {
+    "source": "/docs/start/stellar-stack",
+    "destination": "/docs/learn/fundamentals/stellar-stack"
+  },
+  {
+    "source": "/docs/tutorials/handling-errors",
+    "destination": "/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging-errors"
+  },
+  {
+    "source": "/docs/tutorials/securing-projects",
+    "destination": "/docs/build/security-docs/securing-web-based-projects"
+  },
+  {
+    "source": "/docs/tutorials/moneygram-access-integration-guide",
+    "destination": "https://developer.moneygram.com/moneygram-developer/docs/integrate-moneygram-ramps"
+  },
+  {
+    "source": "/docs/fundamentals-and-concepts/testnet-and-pubnet",
+    "destination": "/docs/networks"
+  },
+  {
+    "source": "/api",
+    "destination": "/docs/data/apis/horizon"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/custom-account",
+    "destination": "/docs/build/smart-contracts/example-contracts/complex-account"
+  },
+  {
+    "source": "/network/horizon/resources/cb-retrieve-related-operations",
+    "destination": "/docs/data/apis/horizon/api-reference/cb-retrieve-related-operations"
+  },
+  {
+    "source": "/network/horizon/resources/cb-retrieve-related-transactions",
+    "destination": "/docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions"
+  },
+  {
+    "source": "/network/horizon/resources/get-all-offers",
+    "destination": "/docs/data/apis/horizon/api-reference/get-all-offers"
+  },
+  {
+    "source": "/network/horizon/resources/get-all-trades",
+    "destination": "/docs/data/apis/horizon/api-reference/get-all-trades"
+  },
+  {
+    "source": "/network/horizon/resources/get-data-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-data-by-account-id"
+  },
+  {
+    "source": "/network/horizon/resources/get-effects-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-effects-by-account-id"
+  },
+  {
+    "source": "/network/horizon/resources/get-offer-by-offer-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-offer-by-offer-id"
+  },
+  {
+    "source": "/network/horizon/resources/get-offers-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-offers-by-account-id"
+  },
+  {
+    "source": "/network/horizon/resources/get-operations-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-operations-by-account-id"
+  },
+  {
+    "source": "/network/horizon/resources/get-payments-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-payments-by-account-id"
+  },
+  {
+    "source": "/network/horizon/resources/get-trades-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-trades-by-account-id"
+  },
+  {
+    "source": "/network/horizon/resources/get-trades-by-offer-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-trades-by-offer-id"
+  },
+  {
+    "source": "/network/horizon/resources/get-transactions-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-transactions-by-account-id"
+  },
+  {
+    "source": "/network/horizon/resources/list-all-accounts",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-accounts"
+  },
+  {
+    "source": "/network/horizon/resources/list-all-assets",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-assets"
+  },
+  {
+    "source": "/network/horizon/resources/list-all-claimable-balances",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-claimable-balances"
+  },
+  {
+    "source": "/network/horizon/resources/list-all-effects",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-effects"
+  },
+  {
+    "source": "/network/horizon/resources/list-all-ledgers",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-ledgers"
+  },
+  {
+    "source": "/network/horizon/resources/list-all-operations",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-operations"
+  },
+  {
+    "source": "/network/horizon/resources/list-all-payments",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-payments"
+  },
+  {
+    "source": "/network/horizon/resources/list-all-transactions",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-transactions"
+  },
+  {
+    "source": "/network/horizon/resources/list-liquidity-pools",
+    "destination": "/docs/data/apis/horizon/api-reference/list-liquidity-pools"
+  },
+  {
+    "source": "/network/horizon/resources/list-strict-receive-payment-paths",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths"
+  },
+  {
+    "source": "/network/horizon/resources/list-strict-send-payment-paths",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths"
+  },
+  {
+    "source": "/network/horizon/resources/list-trade-aggregations",
+    "destination": "/docs/data/apis/horizon/api-reference/list-trade-aggregations"
+  },
+  {
+    "source": "/network/horizon/resources/retrieve-a-claimable-balance",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance"
+  },
+  {
+    "source": "/network/horizon/resources/retrieve-a-ledger",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledger"
+  },
+  {
+    "source": "/network/horizon/resources/retrieve-a-ledgers-effects",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects"
+  },
+  {
+    "source": "/network/horizon/resources/retrieve-a-ledgers-operations",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations"
+  },
+  {
+    "source": "/network/horizon/resources/retrieve-a-ledgers-payments",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments"
+  },
+  {
+    "source": "/network/horizon/resources/retrieve-a-ledgers-transactions",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions"
+  },
+  {
+    "source": "/network/horizon/resources/retrieve-a-liquidity-pool",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool"
+  },
+  {
+    "source": "/network/horizon/resources/retrieve-a-transaction",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-transaction"
+  },
+  {
+    "source": "/network/horizon/resources/retrieve-a-transactions-effects",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects"
+  },
+  {
+    "source": "/network/horizon/resources/retrieve-a-transactions-operations",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations"
+  },
+  {
+    "source": "/network/horizon/resources/retrieve-a-transactions-payments",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments"
+  },
+  {
+    "source": "/network/horizon/resources/retrieve-an-account",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-account"
+  },
+  {
+    "source": "/network/horizon/resources/retrieve-an-operation",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-operation"
+  },
+  {
+    "source": "/network/horizon/resources/retrieve-an-operations-effects",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-operations-effects"
+  },
+  {
+    "source": "/network/horizon/resources/retrieve-an-order-book",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-order-book"
+  },
+  {
+    "source": "/network/horizon/resources/retrieve-fee-stats",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-fee-stats"
+  },
+  {
+    "source": "/network/horizon/resources/retrieve-related-effects",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-related-effects"
+  },
+  {
+    "source": "/network/horizon/resources/retrieve-related-trades",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-related-trades"
+  },
+  {
+    "source": "/network/horizon/resources/submit-a-transaction",
+    "destination": "/docs/data/apis/horizon/api-reference/submit-a-transaction"
+  },
+  {
+    "source": "/network/horizon/resources/submit-async-transaction",
+    "destination": "/docs/data/apis/horizon/api-reference/submit-async-transaction"
+  },
+  {
+    "source": "/network/resources/cb-retrieve-related-operations",
+    "destination": "/docs/data/apis/horizon/api-reference/cb-retrieve-related-operations"
+  },
+  {
+    "source": "/network/resources/cb-retrieve-related-transactions",
+    "destination": "/docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions"
+  },
+  {
+    "source": "/network/resources/get-all-offers",
+    "destination": "/docs/data/apis/horizon/api-reference/get-all-offers"
+  },
+  {
+    "source": "/network/resources/get-all-trades",
+    "destination": "/docs/data/apis/horizon/api-reference/get-all-trades"
+  },
+  {
+    "source": "/network/resources/get-data-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-data-by-account-id"
+  },
+  {
+    "source": "/network/resources/get-effects-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-effects-by-account-id"
+  },
+  {
+    "source": "/network/resources/get-offer-by-offer-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-offer-by-offer-id"
+  },
+  {
+    "source": "/network/resources/get-offers-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-offers-by-account-id"
+  },
+  {
+    "source": "/network/resources/get-operations-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-operations-by-account-id"
+  },
+  {
+    "source": "/network/resources/get-payments-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-payments-by-account-id"
+  },
+  {
+    "source": "/network/resources/get-trades-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-trades-by-account-id"
+  },
+  {
+    "source": "/network/resources/get-trades-by-offer-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-trades-by-offer-id"
+  },
+  {
+    "source": "/network/resources/get-transactions-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-transactions-by-account-id"
+  },
+  {
+    "source": "/network/resources/list-all-accounts",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-accounts"
+  },
+  {
+    "source": "/network/resources/list-all-assets",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-assets"
+  },
+  {
+    "source": "/network/resources/list-all-claimable-balances",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-claimable-balances"
+  },
+  {
+    "source": "/network/resources/list-all-effects",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-effects"
+  },
+  {
+    "source": "/network/resources/list-all-ledgers",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-ledgers"
+  },
+  {
+    "source": "/network/resources/list-all-operations",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-operations"
+  },
+  {
+    "source": "/network/resources/list-all-payments",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-payments"
+  },
+  {
+    "source": "/network/resources/list-all-transactions",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-transactions"
+  },
+  {
+    "source": "/network/resources/list-liquidity-pools",
+    "destination": "/docs/data/apis/horizon/api-reference/list-liquidity-pools"
+  },
+  {
+    "source": "/network/resources/list-strict-receive-payment-paths",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths"
+  },
+  {
+    "source": "/network/resources/list-strict-send-payment-paths",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths"
+  },
+  {
+    "source": "/network/resources/list-trade-aggregations",
+    "destination": "/docs/data/apis/horizon/api-reference/list-trade-aggregations"
+  },
+  {
+    "source": "/network/resources/retrieve-a-claimable-balance",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance"
+  },
+  {
+    "source": "/network/resources/retrieve-a-ledger",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledger"
+  },
+  {
+    "source": "/network/resources/retrieve-a-ledgers-effects",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects"
+  },
+  {
+    "source": "/network/resources/retrieve-a-ledgers-operations",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations"
+  },
+  {
+    "source": "/network/resources/retrieve-a-ledgers-payments",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments"
+  },
+  {
+    "source": "/network/resources/retrieve-a-ledgers-transactions",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions"
+  },
+  {
+    "source": "/network/resources/retrieve-a-liquidity-pool",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool"
+  },
+  {
+    "source": "/network/resources/retrieve-a-transaction",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-transaction"
+  },
+  {
+    "source": "/network/resources/retrieve-a-transactions-effects",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects"
+  },
+  {
+    "source": "/network/resources/retrieve-a-transactions-operations",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations"
+  },
+  {
+    "source": "/network/resources/retrieve-a-transactions-payments",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments"
+  },
+  {
+    "source": "/network/resources/retrieve-an-account",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-account"
+  },
+  {
+    "source": "/network/resources/retrieve-an-operation",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-operation"
+  },
+  {
+    "source": "/network/resources/retrieve-an-operations-effects",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-operations-effects"
+  },
+  {
+    "source": "/network/resources/retrieve-an-order-book",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-order-book"
+  },
+  {
+    "source": "/network/resources/retrieve-fee-stats",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-fee-stats"
+  },
+  {
+    "source": "/network/resources/retrieve-related-effects",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-related-effects"
+  },
+  {
+    "source": "/network/resources/retrieve-related-trades",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-related-trades"
+  },
+  {
+    "source": "/network/resources/submit-a-transaction",
+    "destination": "/docs/data/apis/horizon/api-reference/submit-a-transaction"
+  },
+  {
+    "source": "/network/resources/submit-async-transaction",
+    "destination": "/docs/data/apis/horizon/api-reference/submit-async-transaction"
+  },
+  {
+    "source": "/api/horizon/resources/cb-retrieve-related-operations",
+    "destination": "/docs/data/apis/horizon/api-reference/cb-retrieve-related-operations"
+  },
+  {
+    "source": "/api/horizon/resources/cb-retrieve-related-transactions",
+    "destination": "/docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions"
+  },
+  {
+    "source": "/api/horizon/resources/get-all-offers",
+    "destination": "/docs/data/apis/horizon/api-reference/get-all-offers"
+  },
+  {
+    "source": "/api/horizon/resources/get-all-trades",
+    "destination": "/docs/data/apis/horizon/api-reference/get-all-trades"
+  },
+  {
+    "source": "/api/horizon/resources/get-data-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-data-by-account-id"
+  },
+  {
+    "source": "/api/horizon/resources/get-effects-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-effects-by-account-id"
+  },
+  {
+    "source": "/api/horizon/resources/get-offer-by-offer-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-offer-by-offer-id"
+  },
+  {
+    "source": "/api/horizon/resources/get-offers-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-offers-by-account-id"
+  },
+  {
+    "source": "/api/horizon/resources/get-operations-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-operations-by-account-id"
+  },
+  {
+    "source": "/api/horizon/resources/get-payments-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-payments-by-account-id"
+  },
+  {
+    "source": "/api/horizon/resources/get-trades-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-trades-by-account-id"
+  },
+  {
+    "source": "/api/horizon/resources/get-trades-by-offer-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-trades-by-offer-id"
+  },
+  {
+    "source": "/api/horizon/resources/get-transactions-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-transactions-by-account-id"
+  },
+  {
+    "source": "/api/horizon/resources/list-all-accounts",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-accounts"
+  },
+  {
+    "source": "/api/horizon/resources/list-all-assets",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-assets"
+  },
+  {
+    "source": "/api/horizon/resources/list-all-claimable-balances",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-claimable-balances"
+  },
+  {
+    "source": "/api/horizon/resources/list-all-effects",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-effects"
+  },
+  {
+    "source": "/api/horizon/resources/list-all-ledgers",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-ledgers"
+  },
+  {
+    "source": "/api/horizon/resources/list-all-operations",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-operations"
+  },
+  {
+    "source": "/api/horizon/resources/list-all-payments",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-payments"
+  },
+  {
+    "source": "/api/horizon/resources/list-all-transactions",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-transactions"
+  },
+  {
+    "source": "/api/horizon/resources/list-liquidity-pools",
+    "destination": "/docs/data/apis/horizon/api-reference/list-liquidity-pools"
+  },
+  {
+    "source": "/api/horizon/resources/list-strict-receive-payment-paths",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths"
+  },
+  {
+    "source": "/api/horizon/resources/list-strict-send-payment-paths",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths"
+  },
+  {
+    "source": "/api/horizon/resources/list-trade-aggregations",
+    "destination": "/docs/data/apis/horizon/api-reference/list-trade-aggregations"
+  },
+  {
+    "source": "/api/horizon/resources/retrieve-a-claimable-balance",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance"
+  },
+  {
+    "source": "/api/horizon/resources/retrieve-a-ledger",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledger"
+  },
+  {
+    "source": "/api/horizon/resources/retrieve-a-ledgers-effects",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects"
+  },
+  {
+    "source": "/api/horizon/resources/retrieve-a-ledgers-operations",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations"
+  },
+  {
+    "source": "/api/horizon/resources/retrieve-a-ledgers-payments",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments"
+  },
+  {
+    "source": "/api/horizon/resources/retrieve-a-ledgers-transactions",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions"
+  },
+  {
+    "source": "/api/horizon/resources/retrieve-a-liquidity-pool",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool"
+  },
+  {
+    "source": "/api/horizon/resources/retrieve-a-transaction",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-transaction"
+  },
+  {
+    "source": "/api/horizon/resources/retrieve-a-transactions-effects",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects"
+  },
+  {
+    "source": "/api/horizon/resources/retrieve-a-transactions-operations",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations"
+  },
+  {
+    "source": "/api/horizon/resources/retrieve-a-transactions-payments",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments"
+  },
+  {
+    "source": "/api/horizon/resources/retrieve-an-account",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-account"
+  },
+  {
+    "source": "/api/horizon/resources/retrieve-an-operation",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-operation"
+  },
+  {
+    "source": "/api/horizon/resources/retrieve-an-operations-effects",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-operations-effects"
+  },
+  {
+    "source": "/api/horizon/resources/retrieve-an-order-book",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-order-book"
+  },
+  {
+    "source": "/api/horizon/resources/retrieve-fee-stats",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-fee-stats"
+  },
+  {
+    "source": "/api/horizon/resources/retrieve-related-effects",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-related-effects"
+  },
+  {
+    "source": "/api/horizon/resources/retrieve-related-trades",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-related-trades"
+  },
+  {
+    "source": "/api/horizon/resources/submit-a-transaction",
+    "destination": "/docs/data/apis/horizon/api-reference/submit-a-transaction"
+  },
+  {
+    "source": "/api/horizon/resources/submit-async-transaction",
+    "destination": "/docs/data/apis/horizon/api-reference/submit-async-transaction"
+  },
+  {
+    "source": "/api/resources/cb-retrieve-related-operations",
+    "destination": "/docs/data/apis/horizon/api-reference/cb-retrieve-related-operations"
+  },
+  {
+    "source": "/api/resources/cb-retrieve-related-transactions",
+    "destination": "/docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions"
+  },
+  {
+    "source": "/api/resources/get-all-offers",
+    "destination": "/docs/data/apis/horizon/api-reference/get-all-offers"
+  },
+  {
+    "source": "/api/resources/get-all-trades",
+    "destination": "/docs/data/apis/horizon/api-reference/get-all-trades"
+  },
+  {
+    "source": "/api/resources/get-data-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-data-by-account-id"
+  },
+  {
+    "source": "/api/resources/get-effects-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-effects-by-account-id"
+  },
+  {
+    "source": "/api/resources/get-offer-by-offer-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-offer-by-offer-id"
+  },
+  {
+    "source": "/api/resources/get-offers-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-offers-by-account-id"
+  },
+  {
+    "source": "/api/resources/get-operations-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-operations-by-account-id"
+  },
+  {
+    "source": "/api/resources/get-payments-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-payments-by-account-id"
+  },
+  {
+    "source": "/api/resources/get-trades-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-trades-by-account-id"
+  },
+  {
+    "source": "/api/resources/get-trades-by-offer-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-trades-by-offer-id"
+  },
+  {
+    "source": "/api/resources/get-transactions-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-transactions-by-account-id"
+  },
+  {
+    "source": "/api/resources/list-all-accounts",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-accounts"
+  },
+  {
+    "source": "/api/resources/list-all-assets",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-assets"
+  },
+  {
+    "source": "/api/resources/list-all-claimable-balances",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-claimable-balances"
+  },
+  {
+    "source": "/api/resources/list-all-effects",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-effects"
+  },
+  {
+    "source": "/api/resources/list-all-ledgers",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-ledgers"
+  },
+  {
+    "source": "/api/resources/list-all-operations",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-operations"
+  },
+  {
+    "source": "/api/resources/list-all-payments",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-payments"
+  },
+  {
+    "source": "/api/resources/list-all-transactions",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-transactions"
+  },
+  {
+    "source": "/api/resources/list-liquidity-pools",
+    "destination": "/docs/data/apis/horizon/api-reference/list-liquidity-pools"
+  },
+  {
+    "source": "/api/resources/list-strict-receive-payment-paths",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths"
+  },
+  {
+    "source": "/api/resources/list-strict-send-payment-paths",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths"
+  },
+  {
+    "source": "/api/resources/list-trade-aggregations",
+    "destination": "/docs/data/apis/horizon/api-reference/list-trade-aggregations"
+  },
+  {
+    "source": "/api/resources/retrieve-a-claimable-balance",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance"
+  },
+  {
+    "source": "/api/resources/retrieve-a-ledger",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledger"
+  },
+  {
+    "source": "/api/resources/retrieve-a-ledgers-effects",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects"
+  },
+  {
+    "source": "/api/resources/retrieve-a-ledgers-operations",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations"
+  },
+  {
+    "source": "/api/resources/retrieve-a-ledgers-payments",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments"
+  },
+  {
+    "source": "/api/resources/retrieve-a-ledgers-transactions",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions"
+  },
+  {
+    "source": "/api/resources/retrieve-a-liquidity-pool",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool"
+  },
+  {
+    "source": "/api/resources/retrieve-a-transaction",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-transaction"
+  },
+  {
+    "source": "/api/resources/retrieve-a-transactions-effects",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects"
+  },
+  {
+    "source": "/api/resources/retrieve-a-transactions-operations",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations"
+  },
+  {
+    "source": "/api/resources/retrieve-a-transactions-payments",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments"
+  },
+  {
+    "source": "/api/resources/retrieve-an-account",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-account"
+  },
+  {
+    "source": "/api/resources/retrieve-an-operation",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-operation"
+  },
+  {
+    "source": "/api/resources/retrieve-an-operations-effects",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-operations-effects"
+  },
+  {
+    "source": "/api/resources/retrieve-an-order-book",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-order-book"
+  },
+  {
+    "source": "/api/resources/retrieve-fee-stats",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-fee-stats"
+  },
+  {
+    "source": "/api/resources/retrieve-related-effects",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-related-effects"
+  },
+  {
+    "source": "/api/resources/retrieve-related-trades",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-related-trades"
+  },
+  {
+    "source": "/api/resources/submit-a-transaction",
+    "destination": "/docs/data/apis/horizon/api-reference/submit-a-transaction"
+  },
+  {
+    "source": "/api/resources/submit-async-transaction",
+    "destination": "/docs/data/apis/horizon/api-reference/submit-async-transaction"
+  },
+  {
+    "source": "/network/horizon/resources/operations/object/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/:slug*"
+  },
+  {
+    "source": "/network/resources/operations/object/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/:slug*"
+  },
+  {
+    "source": "/api/horizon/resources/operations/object/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/:slug*"
+  },
+  {
+    "source": "/api/resources/operations/object/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/:slug*"
+  },
+  {
+    "source": "/network/horizon/resources/:slug*/object",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/:slug*/object"
+  },
+  {
+    "source": "/network/horizon/aggregations/:slug*/object",
+    "destination": "/docs/data/apis/horizon/api-reference/aggregations/:slug*/object"
+  },
+  {
+    "source": "/network/resources/:slug*/object",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/:slug*/object"
+  },
+  {
+    "source": "/network/aggregations/:slug*/object",
+    "destination": "/docs/data/apis/horizon/api-reference/aggregations/:slug*/object"
+  },
+  {
+    "source": "/api/horizon/resources/:slug*/object",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/:slug*/object"
+  },
+  {
+    "source": "/api/horizon/aggregations/:slug*/object",
+    "destination": "/docs/data/apis/horizon/api-reference/aggregations/:slug*/object"
+  },
+  {
+    "source": "/api/resources/:slug*/object",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/:slug*/object"
+  },
+  {
+    "source": "/api/aggregations/:slug*/object",
+    "destination": "/docs/data/apis/horizon/api-reference/aggregations/:slug*/object"
+  },
+  {
+    "source": "/network/horizon/api-reference/aggregations/fee-stats/single/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-fee-stats/:slug*"
+  },
+  {
+    "source": "/network/horizon/aggregations/fee-stats/single/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-fee-stats/:slug*"
+  },
+  {
+    "source": "/network/api-reference/aggregations/fee-stats/single/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-fee-stats/:slug*"
+  },
+  {
+    "source": "/network/aggregations/fee-stats/single/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-fee-stats/:slug*"
+  },
+  {
+    "source": "/api/horizon/api-reference/aggregations/fee-stats/single/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-fee-stats/:slug*"
+  },
+  {
+    "source": "/api/horizon/aggregations/fee-stats/single/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-fee-stats/:slug*"
+  },
+  {
+    "source": "/api/api-reference/aggregations/fee-stats/single/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-fee-stats/:slug*"
+  },
+  {
+    "source": "/api/aggregations/fee-stats/single/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-fee-stats/:slug*"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/aggregations/fee-stats/single/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-fee-stats/:slug*"
+  },
+  {
+    "source": "/docs/data/horizon/aggregations/fee-stats/single/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-fee-stats/:slug*"
+  },
+  {
+    "source": "/docs/data/api-reference/aggregations/fee-stats/single/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-fee-stats/:slug*"
+  },
+  {
+    "source": "/docs/data/aggregations/fee-stats/single/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-fee-stats/:slug*"
+  },
+  {
+    "source": "/network/horizon/api-reference/aggregations/order-books/single/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-order-book/:slug*"
+  },
+  {
+    "source": "/network/horizon/aggregations/order-books/single/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-order-book/:slug*"
+  },
+  {
+    "source": "/network/api-reference/aggregations/order-books/single/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-order-book/:slug*"
+  },
+  {
+    "source": "/network/aggregations/order-books/single/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-order-book/:slug*"
+  },
+  {
+    "source": "/api/horizon/api-reference/aggregations/order-books/single/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-order-book/:slug*"
+  },
+  {
+    "source": "/api/horizon/aggregations/order-books/single/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-order-book/:slug*"
+  },
+  {
+    "source": "/api/api-reference/aggregations/order-books/single/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-order-book/:slug*"
+  },
+  {
+    "source": "/api/aggregations/order-books/single/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-order-book/:slug*"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/aggregations/order-books/single/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-order-book/:slug*"
+  },
+  {
+    "source": "/docs/data/horizon/aggregations/order-books/single/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-order-book/:slug*"
+  },
+  {
+    "source": "/docs/data/api-reference/aggregations/order-books/single/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-order-book/:slug*"
+  },
+  {
+    "source": "/docs/data/aggregations/order-books/single/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-order-book/:slug*"
+  },
+  {
+    "source": "/network/horizon/api-reference/aggregations/paths/strict-receive/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths/:slug*"
+  },
+  {
+    "source": "/network/horizon/aggregations/paths/strict-receive/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths/:slug*"
+  },
+  {
+    "source": "/network/api-reference/aggregations/paths/strict-receive/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths/:slug*"
+  },
+  {
+    "source": "/network/aggregations/paths/strict-receive/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths/:slug*"
+  },
+  {
+    "source": "/api/horizon/api-reference/aggregations/paths/strict-receive/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths/:slug*"
+  },
+  {
+    "source": "/api/horizon/aggregations/paths/strict-receive/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths/:slug*"
+  },
+  {
+    "source": "/api/api-reference/aggregations/paths/strict-receive/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths/:slug*"
+  },
+  {
+    "source": "/api/aggregations/paths/strict-receive/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths/:slug*"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/aggregations/paths/strict-receive/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths/:slug*"
+  },
+  {
+    "source": "/docs/data/horizon/aggregations/paths/strict-receive/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths/:slug*"
+  },
+  {
+    "source": "/docs/data/api-reference/aggregations/paths/strict-receive/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths/:slug*"
+  },
+  {
+    "source": "/docs/data/aggregations/paths/strict-receive/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths/:slug*"
+  },
+  {
+    "source": "/network/horizon/api-reference/aggregations/paths/strict-send/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths/:slug*"
+  },
+  {
+    "source": "/network/horizon/aggregations/paths/strict-send/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths/:slug*"
+  },
+  {
+    "source": "/network/api-reference/aggregations/paths/strict-send/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths/:slug*"
+  },
+  {
+    "source": "/network/aggregations/paths/strict-send/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths/:slug*"
+  },
+  {
+    "source": "/api/horizon/api-reference/aggregations/paths/strict-send/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths/:slug*"
+  },
+  {
+    "source": "/api/horizon/aggregations/paths/strict-send/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths/:slug*"
+  },
+  {
+    "source": "/api/api-reference/aggregations/paths/strict-send/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths/:slug*"
+  },
+  {
+    "source": "/api/aggregations/paths/strict-send/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths/:slug*"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/aggregations/paths/strict-send/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths/:slug*"
+  },
+  {
+    "source": "/docs/data/horizon/aggregations/paths/strict-send/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths/:slug*"
+  },
+  {
+    "source": "/docs/data/api-reference/aggregations/paths/strict-send/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths/:slug*"
+  },
+  {
+    "source": "/docs/data/aggregations/paths/strict-send/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths/:slug*"
+  },
+  {
+    "source": "/network/horizon/api-reference/aggregations/trade-aggregations/list/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-trade-aggregations/:slug*"
+  },
+  {
+    "source": "/network/horizon/aggregations/trade-aggregations/list/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-trade-aggregations/:slug*"
+  },
+  {
+    "source": "/network/api-reference/aggregations/trade-aggregations/list/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-trade-aggregations/:slug*"
+  },
+  {
+    "source": "/network/aggregations/trade-aggregations/list/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-trade-aggregations/:slug*"
+  },
+  {
+    "source": "/api/horizon/api-reference/aggregations/trade-aggregations/list/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-trade-aggregations/:slug*"
+  },
+  {
+    "source": "/api/horizon/aggregations/trade-aggregations/list/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-trade-aggregations/:slug*"
+  },
+  {
+    "source": "/api/api-reference/aggregations/trade-aggregations/list/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-trade-aggregations/:slug*"
+  },
+  {
+    "source": "/api/aggregations/trade-aggregations/list/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-trade-aggregations/:slug*"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/aggregations/trade-aggregations/list/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-trade-aggregations/:slug*"
+  },
+  {
+    "source": "/docs/data/horizon/aggregations/trade-aggregations/list/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-trade-aggregations/:slug*"
+  },
+  {
+    "source": "/docs/data/api-reference/aggregations/trade-aggregations/list/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-trade-aggregations/:slug*"
+  },
+  {
+    "source": "/docs/data/aggregations/trade-aggregations/list/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/list-trade-aggregations/:slug*"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/cb-retrieve-related-operations",
+    "destination": "/docs/data/apis/horizon/api-reference/cb-retrieve-related-operations"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/cb-retrieve-related-transactions",
+    "destination": "/docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/get-all-offers",
+    "destination": "/docs/data/apis/horizon/api-reference/get-all-offers"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/get-all-trades",
+    "destination": "/docs/data/apis/horizon/api-reference/get-all-trades"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/get-data-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-data-by-account-id"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/get-effects-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-effects-by-account-id"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/get-offer-by-offer-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-offer-by-offer-id"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/get-offers-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-offers-by-account-id"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/get-operations-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-operations-by-account-id"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/get-payments-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-payments-by-account-id"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/get-trades-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-trades-by-account-id"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/get-trades-by-offer-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-trades-by-offer-id"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/get-transactions-by-account-id",
+    "destination": "/docs/data/apis/horizon/api-reference/get-transactions-by-account-id"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/list-all-accounts",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-accounts"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/list-all-assets",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-assets"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/list-all-claimable-balances",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-claimable-balances"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/list-all-effects",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-effects"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/list-all-ledgers",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-ledgers"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/list-all-operations",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-operations"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/list-all-payments",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-payments"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/list-all-transactions",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-transactions"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/list-liquidity-pools",
+    "destination": "/docs/data/apis/horizon/api-reference/list-liquidity-pools"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/list-strict-receive-payment-paths",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/list-strict-send-payment-paths",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/list-trade-aggregations",
+    "destination": "/docs/data/apis/horizon/api-reference/list-trade-aggregations"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/retrieve-a-claimable-balance",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/retrieve-a-ledger",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledger"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/retrieve-a-ledgers-effects",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/retrieve-a-ledgers-operations",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/retrieve-a-ledgers-payments",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/retrieve-a-ledgers-transactions",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/retrieve-a-liquidity-pool",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/retrieve-a-transaction",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-transaction"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/retrieve-a-transactions-effects",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/retrieve-a-transactions-operations",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/retrieve-a-transactions-payments",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/retrieve-an-account",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-account"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/retrieve-an-operation",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-operation"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/retrieve-an-operations-effects",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-operations-effects"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/retrieve-an-order-book",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-order-book"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/retrieve-fee-stats",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-fee-stats"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/retrieve-related-effects",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-related-effects"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/retrieve-related-trades",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-related-trades"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/submit-a-transaction",
+    "destination": "/docs/data/apis/horizon/api-reference/submit-a-transaction"
+  },
+  {
+    "source": "/docs/data/horizon/api-reference/resources/submit-async-transaction",
+    "destination": "/docs/data/apis/horizon/api-reference/submit-async-transaction"
+  },
+  {
+    "source": "/network/horizon/resources/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/:slug*"
+  },
+  {
+    "source": "/network/horizon/structure/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/structure/:slug*"
+  },
+  {
+    "source": "/network/horizon/aggregations/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/aggregations/:slug*"
+  },
+  {
+    "source": "/network/horizon/errors/:slug*",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/:slug*"
+  },
+  {
+    "source": "/network/horizon/:slug*",
+    "destination": "/docs/data/apis/horizon/:slug*"
+  },
+  {
+    "source": "/api/horizon/:slug*",
+    "destination": "/docs/data/apis/horizon/:slug*"
+  },
+  {
+    "source": "/network/anchor-platform/resources/:slug*",
+    "destination": "/docs/platforms/anchor-platform/api-reference"
+  },
+  {
+    "source": "/network/anchor-platform/callbacks/:slug*",
+    "destination": "/docs/platforms/anchor-platform/api-reference/callbacks/:slug*"
+  },
+  {
+    "source": "/network/anchor-platform/custody-server/:slug*",
+    "destination": "/docs/platforms/anchor-platform/api-reference"
+  },
+  {
+    "source": "/network/anchor-platform/rpc/:slug*",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/:slug*"
+  },
+  {
+    "source": "/network/stellar-disbursement-platform/resources/:slug*",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/:slug*"
+  },
+  {
+    "source": "/network/anchor-platform",
+    "destination": "/docs/platforms/anchor-platform"
+  },
+  {
+    "source": "/network/anchor-platform/:slug*",
+    "destination": "/docs/platforms/anchor-platform/:slug*"
+  },
+  {
+    "source": "/network/stellar-disbursement-platform",
+    "destination": "/docs/platforms/stellar-disbursement-platform"
+  },
+  {
+    "source": "/network/stellar-disbursement-platform/:slug*",
+    "destination": "/docs/platforms/stellar-disbursement-platform/:slug*"
+  },
+  {
+    "source": "/api/anchor-platform",
+    "destination": "/docs/platforms/anchor-platform"
+  },
+  {
+    "source": "/api/anchor-platform/:slug*",
+    "destination": "/docs/platforms/anchor-platform/:slug*"
+  },
+  {
+    "source": "/api/stellar-disbursement-platform",
+    "destination": "/docs/platforms/stellar-disbursement-platform"
+  },
+  {
+    "source": "/api/stellar-disbursement-platform/:slug*",
+    "destination": "/docs/platforms/stellar-disbursement-platform/:slug*"
+  },
+  {
+    "source": "/network/soroban-rpc/methods/:slug*",
+    "destination": "/docs/data/apis/rpc/api-reference/methods/:slug*"
+  },
+  {
+    "source": "/network/soroban-rpc/json-rpc/:slug*",
+    "destination": "/docs/data/apis/rpc/api-reference/structure/json-rpc"
+  },
+  {
+    "source": "/network/soroban-rpc/pagination/:slug*",
+    "destination": "/docs/data/apis/rpc/api-reference/structure/pagination"
+  },
+  {
+    "source": "/ap_api/:slug*",
+    "destination": "/docs/platforms/anchor-platform/:slug*"
+  },
+  {
+    "source": "/docs/category/anchor-platform",
+    "destination": "/docs/platforms/anchor-platform/admin-guide"
+  },
+  {
+    "source": "/docs/anchoring-assets/",
+    "destination": "/docs/learn/fundamentals/anchors"
+  },
+  {
+    "source": "/docs/anchoring-assets/overview",
+    "destination": "/docs/learn/fundamentals/anchors"
+  },
+  {
+    "source": "/docs/anchoring-assets",
+    "destination": "/docs/learn/fundamentals/anchors"
+  },
+  {
+    "source": "/docs/anchoring-assets/:slug*",
+    "destination": "/docs/learn/fundamentals/anchors"
+  },
+  {
+    "source": "/docs/category/use-the-stellar-disbursement-platform",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide"
+  },
+  {
+    "source": "/docs/stellar-disbursement-platform/:slug*",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/:slug*"
+  },
+  {
+    "source": "/docs/run-api-server",
+    "destination": "/docs/data/apis/horizon/admin-guide/overview"
+  },
+  {
+    "source": "/docs/run-api-server/:slug*",
+    "destination": "/docs/data/apis/horizon/admin-guide/:slug*"
+  },
+  {
+    "source": "/docs/run-platform-server",
+    "destination": "/docs/data/apis/horizon/admin-guide/overview"
+  },
+  {
+    "source": "/docs/run-platform-server/:slug*",
+    "destination": "/docs/data/apis/horizon/admin-guide/:slug*"
+  },
+  {
+    "source": "/docs/run-core-node",
+    "destination": "/docs/validators"
+  },
+  {
+    "source": "/docs/run-core-node/tier-1-orgs",
+    "destination": "/docs/validators/tier-1-orgs"
+  },
+  {
+    "source": "/network/core-node/admin-guide/tier-1-orgs",
+    "destination": "/docs/validators/tier-1-orgs"
+  },
+  {
+    "source": "/docs/run-core-node/:slug*",
+    "destination": "/docs/validators/admin-guide/:slug*"
+  },
+  {
+    "source": "/docs/category/accessing-historical-data",
+    "destination": "/docs/data/analytics/hubble"
+  },
+  {
+    "source": "/docs/category/access-historical-data",
+    "destination": "/docs/data/analytics/hubble"
+  },
+  {
+    "source": "/docs/accessing-data/overview",
+    "destination": "/docs/data/analytics/hubble"
+  },
+  {
+    "source": "/docs/accessing-data/:slug*",
+    "destination": "/docs/data/analytics/hubble/:slug*"
+  },
+  {
+    "source": "/docs/fundamentals-and-concepts/:slug*",
+    "destination": "/docs/learn/fundamentals"
+  },
+  {
+    "source": "/docs/category/encyclopedia",
+    "destination": "/docs/learn/fundamentals"
+  },
+  {
+    "source": "/docs/encyclopedia/:slug*",
+    "destination": "/docs/learn/encyclopedia/:slug*"
+  },
+  {
+    "source": "/docs/glossary/:slug*",
+    "destination": "/docs/learn/glossary/:slug*"
+  },
+  {
+    "source": "/docs/learn",
+    "destination": "/docs/learn/fundamentals"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/retrieve-a-transaction",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-transaction"
+  },
+  {
+    "source": "/platforms/anchor-platform/api-reference/resources/get-transaction",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transaction"
+  },
+  {
+    "source": "/docs/learn/smart-contract-internals/fees-and-metering",
+    "destination": "/docs/learn/fundamentals/fees-resource-limits-metering"
+  },
+  {
+    "source": "/docs/learn/migrate/introduction-to-solidity-and-rust",
+    "destination": "/docs/learn/migrate/evm/introduction-to-solidity-and-rust"
+  },
+  {
+    "source": "/docs/learn/smart-contract-internals/state-expiration",
+    "destination": "/docs/learn/fundamentals/contract-development/storage/state-archival"
+  },
+  {
+    "source": "/platforms/soroban-rpc/methods/:slug*",
+    "destination": "/docs/data/apis/rpc/api-reference/methods/:slug*"
+  },
+  {
+    "source": "/network/soroban-rpc/getEvents",
+    "destination": "/docs/data/apis/rpc/api-reference/methods/getEvents"
+  },
+  {
+    "source": "/docs/smart-contracts/example-contracts/stellar-asset-contract",
+    "destination": "/docs/tokens/stellar-asset-contract"
+  },
+  {
+    "source": "/docs/smart-contracts/faq",
+    "destination": "/docs/build/smart-contracts/overview#soroban-faqs"
+  },
+  {
+    "source": "/docs/learn/smart-contract-internals/faq",
+    "destination": "/docs/build/smart-contracts/overview#soroban-faqs"
+  },
+  {
+    "source": "/docs/learn/smart-contract-internals/high-level-overview/:slug*",
+    "destination": "/docs/learn/fundamentals/contract-development"
+  },
+  {
+    "source": "/docs/smart-contracts/tokens/token-interface.mdx",
+    "destination": "/docs/tokens/token-interface"
+  },
+  {
+    "source": "/network/anchor-platform/anchor",
+    "destination": "/docs/platforms/anchor-platform"
+  },
+  {
+    "source": "/docs/examples/auth",
+    "destination": "/docs/build/smart-contracts/example-contracts/auth"
+  },
+  {
+    "source": "/docs/reference",
+    "destination": "/docs/networks"
+  },
+  {
+    "source": "/docs/reference/futurenet",
+    "destination": "/docs/networks"
+  },
+  {
+    "source": "/docs/reference/:slug*",
+    "destination": "/docs/networks/:slug*"
+  },
+  {
+    "source": "/docs/SDKs/rust-auth",
+    "destination": "/docs/tools/sdks#soroban-rust-sdk"
+  },
+  {
+    "source": "/docs/category/cross-border-payments",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep31"
+  },
+  {
+    "source": "/docs/category/hosted-deposits-and-withdrawals",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep24"
+  },
+  {
+    "source": "/docs/category/programmatic-deposits-and-withdrawals",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep6"
+  },
+  {
+    "source": "/docs/category/stellar-authentication",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep10"
+  },
+  {
+    "source": "/docs/category/web-authentication-for-contracts",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep45"
+  },
+  {
+    "source": "/platforms/anchor-platform/admin-guide/sep1/:slug*",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep1/:slug*"
+  },
+  {
+    "source": "/platforms/anchor-platform/admin-guide/sep6/:slug*",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep6/:slug*"
+  },
+  {
+    "source": "/platforms/anchor-platform/admin-guide/sep10/:slug*",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep10/:slug*"
+  },
+  {
+    "source": "/platforms/anchor-platform/admin-guide/sep24/:slug*",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep24/:slug*"
+  },
+  {
+    "source": "/platforms/anchor-platform/admin-guide/sep31/:slug*",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep31/:slug*"
+  },
+  {
+    "source": "/platforms/anchor-platform/admin-guide/sep45/:slug*",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep45/:slug*"
+  },
+  {
+    "source": "/dapps",
+    "destination": "/docs/learn/interactive"
+  },
+  {
+    "source": "/docs/learn/interactive/dapps",
+    "destination": "/docs/learn/interactive"
+  },
+  {
+    "source": "/docs/learn/networks",
+    "destination": "/docs/networks"
+  },
+  {
+    "source": "/docs/learn/fundamentals/networks",
+    "destination": "/docs/networks"
+  },
+  {
+    "source": "/meeting-notes/2024-01-18",
+    "destination": "/meetings/2024/01/18"
+  },
+  {
+    "source": "/meeting-notes/2024-01-26",
+    "destination": "/meetings/2024/01/26"
+  },
+  {
+    "source": "/meeting-notes/2024-02-01",
+    "destination": "/meetings/2024/02/01"
+  },
+  {
+    "source": "/meeting-notes/2024-02-08",
+    "destination": "/meetings/2024/02/08"
+  },
+  {
+    "source": "/meeting-notes/2024-02-15",
+    "destination": "/meetings/2024/02/15"
+  },
+  {
+    "source": "/meeting-notes/2024-02-22",
+    "destination": "/meetings/2024/02/22"
+  },
+  {
+    "source": "/meeting-notes/2024-02-29",
+    "destination": "/meetings/2024/02/29"
+  },
+  {
+    "source": "/meeting-notes/2024-03-07",
+    "destination": "/meetings/2024/03/07"
+  },
+  {
+    "source": "/meeting-notes/2024-03-14",
+    "destination": "/meetings/2024/03/14"
+  },
+  {
+    "source": "/meeting-notes/2024-03-21",
+    "destination": "/meetings/2024/03/21"
+  },
+  {
+    "source": "/meeting-notes/2024-03-28",
+    "destination": "/meetings/2024/03/28"
+  },
+  {
+    "source": "/meeting-notes/2024-04-04",
+    "destination": "/meetings/2024/04/04"
+  },
+  {
+    "source": "/meeting-notes/2024-04-11",
+    "destination": "/meetings/2024/04/11"
+  },
+  {
+    "source": "/meeting-notes/2024-04-18",
+    "destination": "/meetings/2024/04/18"
+  },
+  {
+    "source": "/meeting-notes/2024-04-25",
+    "destination": "/meetings/2024/04/25"
+  },
+  {
+    "source": "/meeting-notes/2024-05-02",
+    "destination": "/meetings/2024/05/02"
+  },
+  {
+    "source": "/meeting-notes/2024-05-09",
+    "destination": "/meetings/2024/05/09"
+  },
+  {
+    "source": "/meeting-notes/2024-06-13",
+    "destination": "/meetings/2024/06/13"
+  },
+  {
+    "source": "/meeting-notes/2024-06-20",
+    "destination": "/meetings/2024/06/20"
+  },
+  {
+    "source": "/meeting-notes/2024-06-27",
+    "destination": "/meetings/2024/06/27"
+  },
+  {
+    "source": "/meeting-notes/2024-07-11",
+    "destination": "/meetings/2024/07/11"
+  },
+  {
+    "source": "/meeting-notes/2024-07-18",
+    "destination": "/meetings/2024/07/18"
+  },
+  {
+    "source": "/meeting-notes/2024-07-25",
+    "destination": "/meetings/2024/07/25"
+  },
+  {
+    "source": "/meeting-notes/2024-08-01",
+    "destination": "/meetings/2024/08/01"
+  },
+  {
+    "source": "/meeting-notes/2024-08-08",
+    "destination": "/meetings/2024/08/08"
+  },
+  {
+    "source": "/meeting-notes/2024-08-15",
+    "destination": "/meetings/2024/08/15"
+  },
+  {
+    "source": "/meeting-notes/2024-08-22",
+    "destination": "/meetings/2024/08/22"
+  },
+  {
+    "source": "/meeting-notes/2024-08-29",
+    "destination": "/meetings/2024/08/29"
+  },
+  {
+    "source": "/meeting-notes/2024-09-05",
+    "destination": "/meetings/2024/09/05"
+  },
+  {
+    "source": "/meeting-notes/2024-09-12",
+    "destination": "/meetings/2024/09/12"
+  },
+  {
+    "source": "/meeting-notes/2024-09-19",
+    "destination": "/meetings/2024/09/19"
+  },
+  {
+    "source": "/meeting-notes/2024-09-26",
+    "destination": "/meetings/2024/09/26"
+  },
+  {
+    "source": "/meeting-notes/2024-10-24",
+    "destination": "/meetings/2024/10/24"
+  },
+  {
+    "source": "/meeting-notes/2024-11-14",
+    "destination": "/meetings/2024/11/14"
+  },
+  {
+    "source": "/meeting-notes/2024-12-05",
+    "destination": "/meetings/2024/12/05"
+  },
+  {
+    "source": "/meeting-notes/2024-12-12",
+    "destination": "/meetings/2024/12/12"
+  },
+  {
+    "source": "/meeting-notes/2024-12-19",
+    "destination": "/meetings/2024/12/19"
+  },
+  {
+    "source": "/meeting-notes/2025-01-16",
+    "destination": "/meetings/2025/01/16"
+  },
+  {
+    "source": "/meeting-notes/2025-01-23",
+    "destination": "/meetings/2025/01/23"
+  },
+  {
+    "source": "/meeting-notes/2025-01-30",
+    "destination": "/meetings/2025/01/30"
+  },
+  {
+    "source": "/meeting-notes/2025-02-06",
+    "destination": "/meetings/2025/02/06"
+  },
+  {
+    "source": "/meeting-notes/2025-02-13",
+    "destination": "/meetings/2025/02/13"
+  },
+  {
+    "source": "/meeting-notes/2025-02-20",
+    "destination": "/meetings/2025/02/20"
+  },
+  {
+    "source": "/meeting-notes/2025-02-27",
+    "destination": "/meetings/2025/02/27"
+  },
+  {
+    "source": "/meeting-notes/2025-03-06",
+    "destination": "/meetings/2025/03/06"
+  },
+  {
+    "source": "/meeting-notes/2025-03-27",
+    "destination": "/meetings/2025/03/27"
+  },
+  {
+    "source": "/meeting-notes/2025-04-03",
+    "destination": "/meetings/2025/04/03"
+  },
+  {
+    "source": "/meeting-notes/2025-04-10",
+    "destination": "/meetings/2025/04/10"
+  },
+  {
+    "source": "/meeting-notes/2025-04-17",
+    "destination": "/meetings/2025/04/17"
+  },
+  {
+    "source": "/meeting-notes/2025-05-01",
+    "destination": "/meetings/2025/05/01"
+  },
+  {
+    "source": "/meeting-notes/2025-05-22",
+    "destination": "/meetings/2025/05/22"
+  },
+  {
+    "source": "/meeting-notes/2025-07-10",
+    "destination": "/meetings/2025/07/10"
+  },
+  {
+    "source": "/meeting-notes/2025-07-17",
+    "destination": "/meetings/2025/07/17"
+  },
+  {
+    "source": "/meeting-notes/2025-07-24",
+    "destination": "/meetings/2025/07/24"
+  },
+  {
+    "source": "/meeting-notes/2025-08-07",
+    "destination": "/meetings/2025/08/07"
+  },
+  {
+    "source": "/meeting-notes/2025-09-25",
+    "destination": "/meetings/2025/09/25"
+  },
+  {
+    "source": "/meeting-notes/2025-10-02",
+    "destination": "/meetings/2025/10/02"
+  },
+  {
+    "source": "/meeting-notes/2025-10-09",
+    "destination": "/meetings/2025/10/09"
+  },
+  {
+    "source": "/meeting-notes/2025-10-16",
+    "destination": "/meetings/2025/10/16"
+  },
+  {
+    "source": "/meeting-notes/2025-10-23",
+    "destination": "/meetings/2025/10/23"
+  },
+  {
+    "source": "/meeting-notes/2025-10-30",
+    "destination": "/meetings/2025/10/30"
+  },
+  {
+    "source": "/meeting-notes/2025-11-06",
+    "destination": "/meetings/2025/11/06"
+  },
+  {
+    "source": "/meeting-notes/2026-01-22",
+    "destination": "/meetings/2026/01/22"
+  },
+  {
+    "source": "/meeting-notes/2026-01-29",
+    "destination": "/meetings/2026/01/29"
+  },
+  {
+    "source": "/meeting-notes/2026-02-26",
+    "destination": "/meetings/2026/02/26"
+  },
+  {
+    "source": "/meeting-notes/2026-04-16",
+    "destination": "/meetings/2026/04/16"
+  },
+  {
+    "source": "/meeting-notes/2026-04-23",
+    "destination": "/meetings/2026/04/23"
+  },
+  {
+    "source": "/meeting-notes/2026-04-30",
+    "destination": "/meetings/2026/04/30"
+  },
+  {
+    "source": "/meeting-notes/2026-05-07",
+    "destination": "/meetings/2026/05/07"
+  },
+  {
+    "source": "/meeting-notes/2026-05-14",
+    "destination": "/meetings/2026/05/14"
+  },
+  {
+    "source": "/meeting-notes/2026-05-21",
+    "destination": "/meetings/2026/05/21"
+  },
+  {
+    "source": "/meeting-notes/2026-06-11",
+    "destination": "/meetings/2026/06/11"
+  },
+  {
+    "source": "/meeting-notes/2026-06-18",
+    "destination": "/meetings/2026/06/18"
+  },
+  {
+    "source": "/meeting-notes/2026-06-25",
+    "destination": "/meetings/2026/06/25"
+  },
+  {
+    "source": "/meeting-notes/2026-07-02",
+    "destination": "/meetings/2026/07/02"
+  },
+  {
+    "source": "/meeting-notes/2026-07-16",
+    "destination": "/meetings/2026/07/16"
+  },
+  {
+    "source": "/meeting-notes/2026-07-23",
+    "destination": "/meetings/2026/07/23"
+  },
+  {
+    "source": "/meeting-notes/2026-07-30",
+    "destination": "/meetings/2026/07/30"
+  },
+  {
+    "source": "/meeting-notes/2026-08-06",
+    "destination": "/meetings/2026/08/06"
+  },
+  {
+    "source": "/meeting-notes/2026-08-13",
+    "destination": "/meetings/2026/08/13"
+  },
+  {
+    "source": "/meeting-notes/:slug*",
+    "destination": "/meetings/:slug*"
+  },
+  {
+    "source": "/docs/category/build-a-wallet",
+    "destination": "/docs/build/apps/wallet"
+  },
+  {
+    "source": "/docs/category/build-a-wallet-with-the-wallet-sdk",
+    "destination": "/docs/build/apps/wallet"
+  },
+  {
+    "source": "/docs/category/build-a-payment-app-with-the-js-sdk",
+    "destination": "/docs/build/apps/example-application-tutorial"
+  },
+  {
+    "source": "/docs/category/anchor-integration",
+    "destination": "/docs/build/apps/example-application-tutorial/anchor-integration"
+  },
+  {
+    "source": "/docs/category/build-custom-network-ingestion-pipeline",
+    "destination": "/docs/build/apps/ingest-sdk"
+  },
+  {
+    "source": "/docs/learn/smart-contract-internals/authorization/:slug*",
+    "destination": "/docs/learn/fundamentals/contract-development/authorization/:slug*"
+  },
+  {
+    "source": "/docs/learn/smart-contract-internals/types/built-in-types",
+    "destination": "/docs/learn/fundamentals/contract-development/types/built-in-types"
+  },
+  {
+    "source": "/docs/learn/smart-contract-internals/types/custom-types",
+    "destination": "/docs/learn/fundamentals/contract-development/types/custom-types"
+  },
+  {
+    "source": "/docs/learn/smart-contract-internals/types/fully-typed-contracts",
+    "destination": "/docs/learn/fundamentals/contract-development/types/fully-typed-contracts"
+  },
+  {
+    "source": "/docs/learn/smart-contract-internals/contract-lifecycle",
+    "destination": "/docs/learn/fundamentals/contract-development/contract-lifecycle"
+  },
+  {
+    "source": "/docs/learn/smart-contract-internals/rust-dialect",
+    "destination": "/docs/learn/fundamentals/contract-development/rust-dialect"
+  },
+  {
+    "source": "/docs/learn/smart-contract-internals/debugging",
+    "destination": "/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging"
+  },
+  {
+    "source": "/docs/learn/smart-contract-internals/debugging-errors",
+    "destination": "/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging-errors"
+  },
+  {
+    "source": "/docs/learn/smart-contract-internals/environment-concepts",
+    "destination": "/docs/learn/fundamentals/contract-development/environment-concepts"
+  },
+  {
+    "source": "/docs/learn/smart-contract-internals/errors",
+    "destination": "/docs/learn/fundamentals/contract-development/errors-and-debugging/errors"
+  },
+  {
+    "source": "/docs/learn/smart-contract-internals/events",
+    "destination": "/docs/learn/fundamentals/stellar-data-structures/events"
+  },
+  {
+    "source": "/docs/learn/smart-contract-internals/contract-interactions/overview",
+    "destination": "/docs/learn/fundamentals/contract-development/overview"
+  },
+  {
+    "source": "/docs/learn/smart-contract-internals/contract-interactions/cross-contract",
+    "destination": "/docs/learn/fundamentals/contract-development/contract-interactions/cross-contract"
+  },
+  {
+    "source": "/docs/learn/smart-contract-internals/contract-interactions/tests",
+    "destination": "/docs/learn/fundamentals/contract-development/contract-interactions/tests"
+  },
+  {
+    "source": "/docs/learn/smart-contract-internals/contract-interactions/stellar-transaction",
+    "destination": "/docs/learn/fundamentals/contract-development/contract-interactions/stellar-transaction"
+  },
+  {
+    "source": "/docs/learn/smart-contract-internals/contract-interactions/transaction-simulation",
+    "destination": "/docs/learn/fundamentals/contract-development/contract-interactions/transaction-simulation"
+  },
+  {
+    "source": "/docs/learn/smart-contract-internals/persisting-data",
+    "destination": "/docs/learn/fundamentals/contract-development/storage/persisting-data"
+  },
+  {
+    "source": "/docs/learn/smart-contract-internals/state-archival",
+    "destination": "/docs/learn/fundamentals/contract-development/storage/state-archival"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/anchors",
+    "destination": "/docs/learn/fundamentals/anchors"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/channel-accounts",
+    "destination": "/docs/build/guides/transactions/channel-accounts"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/claimable-balances",
+    "destination": "/docs/build/guides/transactions/claimable-balances"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/clawbacks",
+    "destination": "/docs/build/guides/transactions/clawbacks"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/federation",
+    "destination": "/docs/learn/glossary#federation"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/fee-bump-transactions",
+    "destination": "/docs/build/guides/transactions/fee-bump-transactions"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/contract-development/fees-and-metering",
+    "destination": "/docs/learn/fundamentals/fees-resource-limits-metering"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/inflation",
+    "destination": "/docs/learn/glossary#inflation"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/ledger-headers",
+    "destination": "/docs/learn/fundamentals/stellar-data-structures/ledgers#ledger-headers"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/liquidity-on-stellar-sdex-liquidity-pools",
+    "destination": "/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/sdex",
+    "destination": "/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/sdex/liquidity-on-stellar-sdex-liquidity-pools",
+    "destination": "/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/lumen-supply-metrics",
+    "destination": "/docs/learn/fundamentals/lumens#lumen-supply-metrics"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/memos",
+    "destination": "/docs/learn/fundamentals/transactions/operations-and-transactions#memo"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/network-passphrases",
+    "destination": "/docs/learn/glossary#passphrase"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/path-payments",
+    "destination": "/docs/build/guides/transactions/path-payments"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/pooled-accounts-muxed-accounts-memos",
+    "destination": "/docs/build/guides/transactions/pooled-accounts-muxed-accounts-memos"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/securing-web-based-projects",
+    "destination": "/docs/build/security-docs/securing-web-based-projects"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/signatures-multisig",
+    "destination": "/docs/learn/fundamentals/transactions/signatures-multisig"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/sponsored-reserves",
+    "destination": "/docs/build/guides/transactions/sponsored-reserves"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/xdr",
+    "destination": "/docs/learn/fundamentals/data-format/xdr"
+  },
+  {
+    "source": "/network/core-node/:slug*",
+    "destination": "/docs/validators/:slug*"
+  },
+  {
+    "source": "/network/hubble/connecting/:slug*",
+    "destination": "/docs/data/analytics/hubble/analyst-guide/connecting/:slug*"
+  },
+  {
+    "source": "/network/hubble/optimizing-queries/:slug*",
+    "destination": "/docs/data/analytics/hubble/analyst-guide/optimizing-queries/:slug*"
+  },
+  {
+    "source": "/network/hubble/viewing-metadata/:slug*",
+    "destination": "/docs/data/analytics/hubble/analyst-guide/viewing-metadata/:slug*"
+  },
+  {
+    "source": "/network/hubble/:slug*",
+    "destination": "/docs/data/analytics/hubble/:slug*"
+  },
+  {
+    "source": "/network/soroban-rpc/:slug*",
+    "destination": "/docs/data/apis/rpc/:slug*"
+  },
+  {
+    "source": "/docs/category/issue-assets",
+    "destination": "/docs/tokens"
+  },
+  {
+    "source": "/docs/issuing-assets/:slug*",
+    "destination": "/docs/tokens/:slug*"
+  },
+  {
+    "source": "/docs/smart-contracts/tokens/wayfinding/:slug*",
+    "destination": "/docs/tokens/:slug*"
+  },
+  {
+    "source": "/docs/smart-contracts/tokens/:slug*",
+    "destination": "/docs/tokens/:slug*"
+  },
+  {
+    "source": "/docs/category/basic-tutorials",
+    "destination": "/docs/build/guides/basics"
+  },
+  {
+    "source": "/docs/tutorials/:slug*",
+    "destination": "/docs/build/guides/basics/:slug*"
+  },
+  {
+    "source": "/docs/category/build-applications",
+    "destination": "/docs/build/apps"
+  },
+  {
+    "source": "/docs/building-apps/:slug*",
+    "destination": "/docs/build/apps/:slug*"
+  },
+  {
+    "source": "/docs/smart-contracts",
+    "destination": "/docs/build/smart-contracts/overview"
+  },
+  {
+    "source": "/docs/smart-contracts/guides/:slug*",
+    "destination": "/docs/build/guides/:slug*"
+  },
+  {
+    "source": "/docs/smart-contracts/smart-wallets/:slug*",
+    "destination": "/docs/build/guides/contract-accounts/:slug*"
+  },
+  {
+    "source": "/docs/build/apps/smart-wallets/:slug*",
+    "destination": "/docs/build/guides/contract-accounts/:slug*"
+  },
+  {
+    "source": "/docs/smart-contracts/getting-started/create-an-app/:slug*",
+    "destination": "/docs/build/apps/dapp-frontend/:slug*"
+  },
+  {
+    "source": "/docs/smart-contracts/:slug*",
+    "destination": "/docs/build/smart-contracts/:slug*"
+  },
+  {
+    "source": "/docs/build/guides/basics/follow-received-payments/:slug*",
+    "destination": "/docs/build/guides/transactions/send-and-receive-payments/:slug*"
+  },
+  {
+    "source": "/docs/build/guides/transactions/install-wasm-bytecode/:slug*",
+    "destination": "/docs/build/guides/transactions/upload-wasm-bytecode/:slug*"
+  },
+  {
+    "source": "/docs/build/guides/testing/detecting-changes-with-test-snapshots/:slug*",
+    "destination": "/docs/build/guides/testing/differential-tests-with-test-snapshots/:slug*"
+  },
+  {
+    "source": "/docs/build/guides/testing/integration-tests-with-mainnet-data/:slug*",
+    "destination": "/docs/build/guides/testing/fork-testing/:slug*"
+  },
+  {
+    "source": "/docs/data/hubble/admin-guide/:slug*",
+    "destination": "/docs/data/analytics/hubble/developer-guide/:slug*"
+  },
+  {
+    "source": "/docs/data/hubble/analytics-platforms/:slug*",
+    "destination": "/docs/data/analytics/analytics-providers"
+  },
+  {
+    "source": "/docs/data/hubble/:slug*",
+    "destination": "/docs/data/analytics/hubble/:slug*"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/accounts",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/accounts"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/claimable-balances",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/claimable-balances"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/contract-code",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-code"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/contract-data",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-data"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/liquidity-pools",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/liquidity-pools"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/offers",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/offers"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/trustlines",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/trustlines"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/ttl",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/ttl"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/history-assets",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-assets"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/history-contract-events",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-contract-events"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/history-effects",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-effects"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/history-ledgers",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-ledgers"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/history-operations",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-operations"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/history-trades",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-trades"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/history-transactions",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-transactions"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/enriched-history-operations",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations"
+  },
+  {
+    "source": "/docs/data/rpc/:slug*",
+    "destination": "/docs/data/apis/rpc/:slug*"
+  },
+  {
+    "source": "/docs/data/apis/rpc/rpc-providers/:slug*",
+    "destination": "/docs/data/apis/rpc/providers/:slug*"
+  },
+  {
+    "source": "/docs/data/apis/api-providers/:slug*",
+    "destination": "/docs/data/apis/rpc/providers/:slug*"
+  },
+  {
+    "source": "/docs/data/horizon/:slug*",
+    "destination": "/docs/data/apis/horizon/:slug*"
+  },
+  {
+    "source": "/docs/data/migrate-from-horizon-to-rpc/:slug*",
+    "destination": "/docs/data/apis/migrate-from-horizon-to-rpc/:slug*"
+  },
+  {
+    "source": "/docs/data/apis/horizon/horizon-providers/:slug*",
+    "destination": "/docs/data/apis/horizon/providers/:slug*"
+  },
+  {
+    "source": "/docs/data/galexie/:slug*",
+    "destination": "/docs/data/indexers/build-your-own/galexie/:slug*"
+  },
+  {
+    "source": "/docs/data/data-indexers/:slug*",
+    "destination": "/docs/data/indexers/:slug*"
+  },
+  {
+    "source": "/docs/tools/developer-tools/cli/:slug*",
+    "destination": "/docs/tools/cli/:slug*"
+  },
+  {
+    "source": "/docs/tools/developer-tools/lab/:slug*",
+    "destination": "/docs/tools/lab/:slug*"
+  },
+  {
+    "source": "/docs/tools/developer-tools/quickstart/:slug*",
+    "destination": "/docs/tools/quickstart/:slug*"
+  },
+  {
+    "source": "/docs/tools/developer-tools/openzepplin-contracts/:slug*",
+    "destination": "/docs/tools/openzeppelin-contracts"
+  },
+  {
+    "source": "/docs/tools/cli/cookbook/install-deploy/:slug*",
+    "destination": "/docs/tools/cli/cookbook/upload-deploy/:slug*"
+  },
+  {
+    "source": "/docs/tools/cli/cookbook/install-wasm/:slug*",
+    "destination": "/docs/tools/cli/cookbook/upload-wasm/:slug*"
+  },
+  {
+    "source": "/docs/build/guides/cli/install-deploy/:slug*",
+    "destination": "/docs/tools/cli/cookbook/upload-deploy/:slug*"
+  },
+  {
+    "source": "/docs/build/guides/cli/install-wasm/:slug*",
+    "destination": "/docs/tools/cli/cookbook/upload-wasm/:slug*"
+  },
+  {
+    "source": "/docs/build/guides/cli/:slug*",
+    "destination": "/docs/tools/cli/cookbook/:slug*"
+  },
+  {
+    "source": "/docs/build/apps/moneygram-access-integration-guide",
+    "destination": "https://developer.moneygram.com/moneygram-developer/docs/integrate-moneygram-ramps"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/data-format",
+    "destination": "/docs/learn/fundamentals/data-format"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/data-format/xdr",
+    "destination": "/docs/learn/fundamentals/data-format/xdr"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/data-format/xdr-json",
+    "destination": "/docs/learn/fundamentals/data-format/xdr-json"
+  },
+  {
+    "source": "/platforms/stellar-disbursement-platform/admin-guide/anchor-platform-integration-points",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide"
+  },
+  {
+    "source": "/platforms/stellar-disbursement-platform/admin-guide/single-tenant-to-multi-tenant-migration",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide"
+  },
+  {
+    "source": "/platforms/stellar-disbursement-platform/admin-guide/tenant-provisioning",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/advanced-configuration#provisioning-tenants"
+  },
+  {
+    "source": "/platforms/stellar-disbursement-platform/admin-guide/secure-operation-manual",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/security"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/wallets",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/distribution-accounts"
+  },
+  {
+    "source": "/platforms/:slug*",
+    "destination": "/docs/platforms/:slug*"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/errors-and-debugging/:slug*",
+    "destination": "/docs/learn/fundamentals/contract-development/errors-and-debugging/:slug*"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/security/authorization/:slug*",
+    "destination": "/docs/learn/fundamentals/contract-development/authorization/:slug*"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/storage/:slug*",
+    "destination": "/docs/learn/fundamentals/contract-development/storage/:slug*"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/contract-development/:slug*",
+    "destination": "/docs/learn/fundamentals/contract-development/:slug*"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/security/signatures-multisig",
+    "destination": "/docs/learn/fundamentals/transactions/signatures-multisig"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/security/securing-web-based-projects",
+    "destination": "/docs/build/security-docs/securing-web-based-projects"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/security",
+    "destination": "/docs/learn/fundamentals/transactions/signatures-multisig"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/transactions-specialized/channel-accounts",
+    "destination": "/docs/build/guides/transactions/channel-accounts"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/transactions-specialized/claimable-balances",
+    "destination": "/docs/build/guides/transactions/claimable-balances"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/transactions-specialized/clawbacks",
+    "destination": "/docs/build/guides/transactions/clawbacks"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/transactions-specialized/fee-bump-transactions",
+    "destination": "/docs/build/guides/transactions/fee-bump-transactions"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/transactions-specialized/memos",
+    "destination": "/docs/learn/fundamentals/transactions/operations-and-transactions#memo"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/transactions-specialized/path-payments",
+    "destination": "/docs/build/guides/transactions/path-payments"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/transactions-specialized/pooled-accounts-muxed-accounts-memos",
+    "destination": "/docs/build/guides/transactions/pooled-accounts-muxed-accounts-memos"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/transactions-specialized/sponsored-reserves",
+    "destination": "/docs/build/guides/transactions/sponsored-reserves"
+  },
+  {
+    "source": "/docs/learn/encyclopedia/transactions-specialized",
+    "destination": "/docs/build/guides/transactions"
+  },
+  {
+    "source": "/docs/build/guides/basics/create-account",
+    "destination": "/docs/build/guides/transactions/create-account"
+  },
+  {
+    "source": "/docs/build/guides/basics/send-and-receive-payments",
+    "destination": "/docs/build/guides/transactions/send-and-receive-payments"
+  },
+  {
+    "source": "/docs/learn/fundamentals/contract-development/events",
+    "destination": "/docs/learn/fundamentals/stellar-data-structures/events"
+  },
+  {
+    "source": "/docs/learn/encyclopedia",
+    "destination": "/docs/learn/fundamentals"
+  },
+  {
+    "source": "/docs/build/apps/x402/:slug*",
+    "destination": "/docs/build/agentic-payments/x402/:slug*"
+  },
+  {
+    "source": "/docs/tools/developer-tools/building-with-ai/:slug*",
+    "destination": "/docs/build/building-with-ai/:slug*"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/fungible-token",
+    "destination": "/docs/build/smart-contracts/example-contracts/tokens"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/non-fungible-token",
+    "destination": "/docs/build/smart-contracts/example-contracts/tokens"
+  },
+  {
+    "source": "/api/:slug*",
+    "destination": "/docs/data/apis/horizon/:slug*"
+  },
+  {
+    "source": "/docs/build/agentic-payments/index.html",
+    "destination": "/docs/build/agentic-payments/index"
+  },
+  {
+    "source": "/docs/build/agentic-payments/mpp/channel-guide.html",
+    "destination": "/docs/build/agentic-payments/mpp/channel-guide"
+  },
+  {
+    "source": "/docs/build/agentic-payments/mpp/charge-guide.html",
+    "destination": "/docs/build/agentic-payments/mpp/charge-guide"
+  },
+  {
+    "source": "/docs/build/agentic-payments/mpp/index.html",
+    "destination": "/docs/build/agentic-payments/mpp/index"
+  },
+  {
+    "source": "/docs/build/agentic-payments/x402/built-on-stellar.html",
+    "destination": "/docs/build/agentic-payments/x402/built-on-stellar"
+  },
+  {
+    "source": "/docs/build/agentic-payments/x402/index.html",
+    "destination": "/docs/build/agentic-payments/x402/index"
+  },
+  {
+    "source": "/docs/build/agentic-payments/x402/quickstart-guide.html",
+    "destination": "/docs/build/agentic-payments/x402/quickstart-guide"
+  },
+  {
+    "source": "/docs/build/apps/application-design-considerations.html",
+    "destination": "/docs/build/apps/application-design-considerations"
+  },
+  {
+    "source": "/docs/build/apps/dapp-frontend.html",
+    "destination": "/docs/build/apps/dapp-frontend"
+  },
+  {
+    "source": "/docs/build/apps/example-application-tutorial/account-creation.html",
+    "destination": "/docs/build/apps/example-application-tutorial/account-creation"
+  },
+  {
+    "source": "/docs/build/apps/example-application-tutorial/anchor-integration/index.html",
+    "destination": "/docs/build/apps/example-application-tutorial/anchor-integration/index"
+  },
+  {
+    "source": "/docs/build/apps/example-application-tutorial/anchor-integration/sep1.html",
+    "destination": "/docs/build/apps/example-application-tutorial/anchor-integration/sep1"
+  },
+  {
+    "source": "/docs/build/apps/example-application-tutorial/anchor-integration/sep10.html",
+    "destination": "/docs/build/apps/example-application-tutorial/anchor-integration/sep10"
+  },
+  {
+    "source": "/docs/build/apps/example-application-tutorial/anchor-integration/sep24.html",
+    "destination": "/docs/build/apps/example-application-tutorial/anchor-integration/sep24"
+  },
+  {
+    "source": "/docs/build/apps/example-application-tutorial/anchor-integration/sep6.html",
+    "destination": "/docs/build/apps/example-application-tutorial/anchor-integration/sep6"
+  },
+  {
+    "source": "/docs/build/apps/example-application-tutorial/anchor-integration/setup.html",
+    "destination": "/docs/build/apps/example-application-tutorial/anchor-integration/setup"
+  },
+  {
+    "source": "/docs/build/apps/example-application-tutorial/confirmation-modal.html",
+    "destination": "/docs/build/apps/example-application-tutorial/confirmation-modal"
+  },
+  {
+    "source": "/docs/build/apps/example-application-tutorial/contacts-list.html",
+    "destination": "/docs/build/apps/example-application-tutorial/contacts-list"
+  },
+  {
+    "source": "/docs/build/apps/example-application-tutorial/index.html",
+    "destination": "/docs/build/apps/example-application-tutorial/index"
+  },
+  {
+    "source": "/docs/build/apps/example-application-tutorial/manage-trust.html",
+    "destination": "/docs/build/apps/example-application-tutorial/manage-trust"
+  },
+  {
+    "source": "/docs/build/apps/example-application-tutorial/overview.html",
+    "destination": "/docs/build/apps/example-application-tutorial/overview"
+  },
+  {
+    "source": "/docs/build/apps/example-application-tutorial/path-payment.html",
+    "destination": "/docs/build/apps/example-application-tutorial/path-payment"
+  },
+  {
+    "source": "/docs/build/apps/example-application-tutorial/payment.html",
+    "destination": "/docs/build/apps/example-application-tutorial/payment"
+  },
+  {
+    "source": "/docs/build/apps/example-application-tutorial/querying-data.html",
+    "destination": "/docs/build/apps/example-application-tutorial/querying-data"
+  },
+  {
+    "source": "/docs/build/apps/guestbook/bindings.html",
+    "destination": "/docs/build/apps/guestbook/bindings"
+  },
+  {
+    "source": "/docs/build/apps/guestbook/frontend.html",
+    "destination": "/docs/build/apps/guestbook/frontend"
+  },
+  {
+    "source": "/docs/build/apps/guestbook/index.html",
+    "destination": "/docs/build/apps/guestbook/index"
+  },
+  {
+    "source": "/docs/build/apps/guestbook/overview.html",
+    "destination": "/docs/build/apps/guestbook/overview"
+  },
+  {
+    "source": "/docs/build/apps/guestbook/passkeys-prerequisites.html",
+    "destination": "/docs/build/apps/guestbook/passkeys-prerequisites"
+  },
+  {
+    "source": "/docs/build/apps/guestbook/setup-passkeys.html",
+    "destination": "/docs/build/apps/guestbook/setup-passkeys"
+  },
+  {
+    "source": "/docs/build/apps/guestbook/smart-contract.html",
+    "destination": "/docs/build/apps/guestbook/smart-contract"
+  },
+  {
+    "source": "/docs/build/apps/index.html",
+    "destination": "/docs/build/apps/index"
+  },
+  {
+    "source": "/docs/build/apps/ingest-sdk/index.html",
+    "destination": "/docs/build/apps/ingest-sdk/index"
+  },
+  {
+    "source": "/docs/build/apps/ingest-sdk/ingestion-pipeline-code.html",
+    "destination": "/docs/build/apps/ingest-sdk/ingestion-pipeline-code"
+  },
+  {
+    "source": "/docs/build/apps/ingest-sdk/overview.html",
+    "destination": "/docs/build/apps/ingest-sdk/overview"
+  },
+  {
+    "source": "/docs/build/apps/overview.html",
+    "destination": "/docs/build/apps/overview"
+  },
+  {
+    "source": "/docs/build/apps/privacy.html",
+    "destination": "/docs/build/apps/privacy"
+  },
+  {
+    "source": "/docs/build/apps/swift-payment-app.html",
+    "destination": "/docs/build/apps/swift-payment-app"
+  },
+  {
+    "source": "/docs/build/apps/wallet/index.html",
+    "destination": "/docs/build/apps/wallet/index"
+  },
+  {
+    "source": "/docs/build/apps/wallet/intro.html",
+    "destination": "/docs/build/apps/wallet/intro"
+  },
+  {
+    "source": "/docs/build/apps/wallet/overview.html",
+    "destination": "/docs/build/apps/wallet/overview"
+  },
+  {
+    "source": "/docs/build/apps/wallet/sep10.html",
+    "destination": "/docs/build/apps/wallet/sep10"
+  },
+  {
+    "source": "/docs/build/apps/wallet/sep24.html",
+    "destination": "/docs/build/apps/wallet/sep24"
+  },
+  {
+    "source": "/docs/build/apps/wallet/sep30.html",
+    "destination": "/docs/build/apps/wallet/sep30"
+  },
+  {
+    "source": "/docs/build/apps/wallet/sep38.html",
+    "destination": "/docs/build/apps/wallet/sep38"
+  },
+  {
+    "source": "/docs/build/apps/wallet/sep6.html",
+    "destination": "/docs/build/apps/wallet/sep6"
+  },
+  {
+    "source": "/docs/build/apps/wallet/sep7.html",
+    "destination": "/docs/build/apps/wallet/sep7"
+  },
+  {
+    "source": "/docs/build/apps/wallet/stellar.html",
+    "destination": "/docs/build/apps/wallet/stellar"
+  },
+  {
+    "source": "/docs/build/apps/zk.html",
+    "destination": "/docs/build/apps/zk"
+  },
+  {
+    "source": "/docs/build/building-with-ai.html",
+    "destination": "/docs/build/building-with-ai"
+  },
+  {
+    "source": "/docs/build/guides/archival/create-restoration-footprint-js.html",
+    "destination": "/docs/build/guides/archival/create-restoration-footprint-js"
+  },
+  {
+    "source": "/docs/build/guides/archival/extend-persistent-entry-js.html",
+    "destination": "/docs/build/guides/archival/extend-persistent-entry-js"
+  },
+  {
+    "source": "/docs/build/guides/archival/index.html",
+    "destination": "/docs/build/guides/archival/index"
+  },
+  {
+    "source": "/docs/build/guides/archival/restore-contract-js.html",
+    "destination": "/docs/build/guides/archival/restore-contract-js"
+  },
+  {
+    "source": "/docs/build/guides/archival/restore-data-js.html",
+    "destination": "/docs/build/guides/archival/restore-data-js"
+  },
+  {
+    "source": "/docs/build/guides/archival/test-ttl-extension.html",
+    "destination": "/docs/build/guides/archival/test-ttl-extension"
+  },
+  {
+    "source": "/docs/build/guides/auth/check-auth-tutorials.html",
+    "destination": "/docs/build/guides/auth/check-auth-tutorials"
+  },
+  {
+    "source": "/docs/build/guides/auth/contract-authorization.html",
+    "destination": "/docs/build/guides/auth/contract-authorization"
+  },
+  {
+    "source": "/docs/build/guides/auth/index.html",
+    "destination": "/docs/build/guides/auth/index"
+  },
+  {
+    "source": "/docs/build/guides/basics/automate-reset-data.html",
+    "destination": "/docs/build/guides/basics/automate-reset-data"
+  },
+  {
+    "source": "/docs/build/guides/basics/classic-transition.html",
+    "destination": "/docs/build/guides/basics/classic-transition"
+  },
+  {
+    "source": "/docs/build/guides/basics/index.html",
+    "destination": "/docs/build/guides/basics/index"
+  },
+  {
+    "source": "/docs/build/guides/basics/verify-trustlines.html",
+    "destination": "/docs/build/guides/basics/verify-trustlines"
+  },
+  {
+    "source": "/docs/build/guides/contract-accounts/advanced-patterns.html",
+    "destination": "/docs/build/guides/contract-accounts/advanced-patterns"
+  },
+  {
+    "source": "/docs/build/guides/contract-accounts/examples.html",
+    "destination": "/docs/build/guides/contract-accounts/examples"
+  },
+  {
+    "source": "/docs/build/guides/contract-accounts/index.html",
+    "destination": "/docs/build/guides/contract-accounts/index"
+  },
+  {
+    "source": "/docs/build/guides/contract-accounts/smart-wallets.html",
+    "destination": "/docs/build/guides/contract-accounts/smart-wallets"
+  },
+  {
+    "source": "/docs/build/guides/conventions/cross-contract.html",
+    "destination": "/docs/build/guides/conventions/cross-contract"
+  },
+  {
+    "source": "/docs/build/guides/conventions/deploy-contract.html",
+    "destination": "/docs/build/guides/conventions/deploy-contract"
+  },
+  {
+    "source": "/docs/build/guides/conventions/deploy-sac-with-code.html",
+    "destination": "/docs/build/guides/conventions/deploy-sac-with-code"
+  },
+  {
+    "source": "/docs/build/guides/conventions/error-enum.html",
+    "destination": "/docs/build/guides/conventions/error-enum"
+  },
+  {
+    "source": "/docs/build/guides/conventions/extending-wasm-ttl.html",
+    "destination": "/docs/build/guides/conventions/extending-wasm-ttl"
+  },
+  {
+    "source": "/docs/build/guides/conventions/index.html",
+    "destination": "/docs/build/guides/conventions/index"
+  },
+  {
+    "source": "/docs/build/guides/conventions/upgrading-contracts.html",
+    "destination": "/docs/build/guides/conventions/upgrading-contracts"
+  },
+  {
+    "source": "/docs/build/guides/conventions/wasm-metadata.html",
+    "destination": "/docs/build/guides/conventions/wasm-metadata"
+  },
+  {
+    "source": "/docs/build/guides/conventions/workspace.html",
+    "destination": "/docs/build/guides/conventions/workspace"
+  },
+  {
+    "source": "/docs/build/guides/conversions/address-conversions.html",
+    "destination": "/docs/build/guides/conversions/address-conversions"
+  },
+  {
+    "source": "/docs/build/guides/conversions/bytes-conversions.html",
+    "destination": "/docs/build/guides/conversions/bytes-conversions"
+  },
+  {
+    "source": "/docs/build/guides/conversions/index.html",
+    "destination": "/docs/build/guides/conversions/index"
+  },
+  {
+    "source": "/docs/build/guides/conversions/scval-conversions.html",
+    "destination": "/docs/build/guides/conversions/scval-conversions"
+  },
+  {
+    "source": "/docs/build/guides/conversions/string-conversions.html",
+    "destination": "/docs/build/guides/conversions/string-conversions"
+  },
+  {
+    "source": "/docs/build/guides/dapps/frontend-guide.html",
+    "destination": "/docs/build/guides/dapps/frontend-guide"
+  },
+  {
+    "source": "/docs/build/guides/dapps/index.html",
+    "destination": "/docs/build/guides/dapps/index"
+  },
+  {
+    "source": "/docs/build/guides/dapps/initialization.html",
+    "destination": "/docs/build/guides/dapps/initialization"
+  },
+  {
+    "source": "/docs/build/guides/dapps/soroban-contract-init-template.html",
+    "destination": "/docs/build/guides/dapps/soroban-contract-init-template"
+  },
+  {
+    "source": "/docs/build/guides/dapps/state-archival.html",
+    "destination": "/docs/build/guides/dapps/state-archival"
+  },
+  {
+    "source": "/docs/build/guides/dapps/working-with-contract-specs.html",
+    "destination": "/docs/build/guides/dapps/working-with-contract-specs"
+  },
+  {
+    "source": "/docs/build/guides/events/consume.html",
+    "destination": "/docs/build/guides/events/consume"
+  },
+  {
+    "source": "/docs/build/guides/events/index.html",
+    "destination": "/docs/build/guides/events/index"
+  },
+  {
+    "source": "/docs/build/guides/events/ingest.html",
+    "destination": "/docs/build/guides/events/ingest"
+  },
+  {
+    "source": "/docs/build/guides/events/publish.html",
+    "destination": "/docs/build/guides/events/publish"
+  },
+  {
+    "source": "/docs/build/guides/fees/analyzing-smart-contract-cost.html",
+    "destination": "/docs/build/guides/fees/analyzing-smart-contract-cost"
+  },
+  {
+    "source": "/docs/build/guides/fees/index.html",
+    "destination": "/docs/build/guides/fees/index"
+  },
+  {
+    "source": "/docs/build/guides/freighter/connect-testnet.html",
+    "destination": "/docs/build/guides/freighter/connect-testnet"
+  },
+  {
+    "source": "/docs/build/guides/freighter/enable-soroban-tokens.html",
+    "destination": "/docs/build/guides/freighter/enable-soroban-tokens"
+  },
+  {
+    "source": "/docs/build/guides/freighter/index.html",
+    "destination": "/docs/build/guides/freighter/index"
+  },
+  {
+    "source": "/docs/build/guides/freighter/integrate-freighter-react.html",
+    "destination": "/docs/build/guides/freighter/integrate-freighter-react"
+  },
+  {
+    "source": "/docs/build/guides/freighter/prompt-to-sign-tx.html",
+    "destination": "/docs/build/guides/freighter/prompt-to-sign-tx"
+  },
+  {
+    "source": "/docs/build/guides/freighter/send-token-payments.html",
+    "destination": "/docs/build/guides/freighter/send-token-payments"
+  },
+  {
+    "source": "/docs/build/guides/freighter/sign-auth-entries.html",
+    "destination": "/docs/build/guides/freighter/sign-auth-entries"
+  },
+  {
+    "source": "/docs/build/guides/freighter/sign-soroban-xdrs.html",
+    "destination": "/docs/build/guides/freighter/sign-soroban-xdrs"
+  },
+  {
+    "source": "/docs/build/guides/index.html",
+    "destination": "/docs/build/guides/index"
+  },
+  {
+    "source": "/docs/build/guides/rpc/generate-ledger-keys-python.html",
+    "destination": "/docs/build/guides/rpc/generate-ledger-keys-python"
+  },
+  {
+    "source": "/docs/build/guides/rpc/index.html",
+    "destination": "/docs/build/guides/rpc/index"
+  },
+  {
+    "source": "/docs/build/guides/rpc/retrieve-contract-code-js.html",
+    "destination": "/docs/build/guides/rpc/retrieve-contract-code-js"
+  },
+  {
+    "source": "/docs/build/guides/rpc/retrieve-contract-code-python.html",
+    "destination": "/docs/build/guides/rpc/retrieve-contract-code-python"
+  },
+  {
+    "source": "/docs/build/guides/storage/choosing-the-right-storage.html",
+    "destination": "/docs/build/guides/storage/choosing-the-right-storage"
+  },
+  {
+    "source": "/docs/build/guides/storage/index.html",
+    "destination": "/docs/build/guides/storage/index"
+  },
+  {
+    "source": "/docs/build/guides/storage/migrate-contract-storage.html",
+    "destination": "/docs/build/guides/storage/migrate-contract-storage"
+  },
+  {
+    "source": "/docs/build/guides/storage/storage-strategies.html",
+    "destination": "/docs/build/guides/storage/storage-strategies"
+  },
+  {
+    "source": "/docs/build/guides/storage/use-instance.html",
+    "destination": "/docs/build/guides/storage/use-instance"
+  },
+  {
+    "source": "/docs/build/guides/storage/use-persistent.html",
+    "destination": "/docs/build/guides/storage/use-persistent"
+  },
+  {
+    "source": "/docs/build/guides/storage/use-temporary.html",
+    "destination": "/docs/build/guides/storage/use-temporary"
+  },
+  {
+    "source": "/docs/build/guides/testing/code-coverage.html",
+    "destination": "/docs/build/guides/testing/code-coverage"
+  },
+  {
+    "source": "/docs/build/guides/testing/differential-tests.html",
+    "destination": "/docs/build/guides/testing/differential-tests"
+  },
+  {
+    "source": "/docs/build/guides/testing/differential-tests-with-test-snapshots.html",
+    "destination": "/docs/build/guides/testing/differential-tests-with-test-snapshots"
+  },
+  {
+    "source": "/docs/build/guides/testing/fork-testing.html",
+    "destination": "/docs/build/guides/testing/fork-testing"
+  },
+  {
+    "source": "/docs/build/guides/testing/fuzzing.html",
+    "destination": "/docs/build/guides/testing/fuzzing"
+  },
+  {
+    "source": "/docs/build/guides/testing/index.html",
+    "destination": "/docs/build/guides/testing/index"
+  },
+  {
+    "source": "/docs/build/guides/testing/integration-tests.html",
+    "destination": "/docs/build/guides/testing/integration-tests"
+  },
+  {
+    "source": "/docs/build/guides/testing/ledger-snapshot-testing.html",
+    "destination": "/docs/build/guides/testing/ledger-snapshot-testing"
+  },
+  {
+    "source": "/docs/build/guides/testing/mocking.html",
+    "destination": "/docs/build/guides/testing/mocking"
+  },
+  {
+    "source": "/docs/build/guides/testing/mutation-testing.html",
+    "destination": "/docs/build/guides/testing/mutation-testing"
+  },
+  {
+    "source": "/docs/build/guides/testing/test-contract-auth.html",
+    "destination": "/docs/build/guides/testing/test-contract-auth"
+  },
+  {
+    "source": "/docs/build/guides/testing/test-contract-events.html",
+    "destination": "/docs/build/guides/testing/test-contract-events"
+  },
+  {
+    "source": "/docs/build/guides/testing/unit-tests.html",
+    "destination": "/docs/build/guides/testing/unit-tests"
+  },
+  {
+    "source": "/docs/build/guides/tokens/custom-sac-admin.html",
+    "destination": "/docs/build/guides/tokens/custom-sac-admin"
+  },
+  {
+    "source": "/docs/build/guides/tokens/deploying-a-sac.html",
+    "destination": "/docs/build/guides/tokens/deploying-a-sac"
+  },
+  {
+    "source": "/docs/build/guides/tokens/index.html",
+    "destination": "/docs/build/guides/tokens/index"
+  },
+  {
+    "source": "/docs/build/guides/tokens/stellar-asset-contract.html",
+    "destination": "/docs/build/guides/tokens/stellar-asset-contract"
+  },
+  {
+    "source": "/docs/build/guides/transactions/channel-accounts.html",
+    "destination": "/docs/build/guides/transactions/channel-accounts"
+  },
+  {
+    "source": "/docs/build/guides/transactions/claimable-balances.html",
+    "destination": "/docs/build/guides/transactions/claimable-balances"
+  },
+  {
+    "source": "/docs/build/guides/transactions/clawbacks.html",
+    "destination": "/docs/build/guides/transactions/clawbacks"
+  },
+  {
+    "source": "/docs/build/guides/transactions/create-account.html",
+    "destination": "/docs/build/guides/transactions/create-account"
+  },
+  {
+    "source": "/docs/build/guides/transactions/fee-bump-transactions.html",
+    "destination": "/docs/build/guides/transactions/fee-bump-transactions"
+  },
+  {
+    "source": "/docs/build/guides/transactions/index.html",
+    "destination": "/docs/build/guides/transactions/index"
+  },
+  {
+    "source": "/docs/build/guides/transactions/install-deploy-contract-with-code.html",
+    "destination": "/docs/build/guides/transactions/install-deploy-contract-with-code"
+  },
+  {
+    "source": "/docs/build/guides/transactions/invoke-contract-tx-sdk.html",
+    "destination": "/docs/build/guides/transactions/invoke-contract-tx-sdk"
+  },
+  {
+    "source": "/docs/build/guides/transactions/path-payments.html",
+    "destination": "/docs/build/guides/transactions/path-payments"
+  },
+  {
+    "source": "/docs/build/guides/transactions/pooled-accounts-muxed-accounts-memos.html",
+    "destination": "/docs/build/guides/transactions/pooled-accounts-muxed-accounts-memos"
+  },
+  {
+    "source": "/docs/build/guides/transactions/send-and-receive-c-accounts.html",
+    "destination": "/docs/build/guides/transactions/send-and-receive-c-accounts"
+  },
+  {
+    "source": "/docs/build/guides/transactions/send-and-receive-payments.html",
+    "destination": "/docs/build/guides/transactions/send-and-receive-payments"
+  },
+  {
+    "source": "/docs/build/guides/transactions/signing-soroban-invocations.html",
+    "destination": "/docs/build/guides/transactions/signing-soroban-invocations"
+  },
+  {
+    "source": "/docs/build/guides/transactions/simulateTransaction-Deep-Dive.html",
+    "destination": "/docs/build/guides/transactions/simulateTransaction-Deep-Dive"
+  },
+  {
+    "source": "/docs/build/guides/transactions/sponsored-reserves.html",
+    "destination": "/docs/build/guides/transactions/sponsored-reserves"
+  },
+  {
+    "source": "/docs/build/guides/transactions/submit-transaction-wait-js.html",
+    "destination": "/docs/build/guides/transactions/submit-transaction-wait-js"
+  },
+  {
+    "source": "/docs/build/guides/transactions/upload-wasm-bytecode.html",
+    "destination": "/docs/build/guides/transactions/upload-wasm-bytecode"
+  },
+  {
+    "source": "/docs/build/index.html",
+    "destination": "/docs/build/index"
+  },
+  {
+    "source": "/docs/build/security-docs/index.html",
+    "destination": "/docs/build/security-docs/index"
+  },
+  {
+    "source": "/docs/build/security-docs/monitoring/index.html",
+    "destination": "/docs/build/security-docs/monitoring/index"
+  },
+  {
+    "source": "/docs/build/security-docs/monitoring/monitoring-template-builders.html",
+    "destination": "/docs/build/security-docs/monitoring/monitoring-template-builders"
+  },
+  {
+    "source": "/docs/build/security-docs/monitoring/monitoring-template-users.html",
+    "destination": "/docs/build/security-docs/monitoring/monitoring-template-users"
+  },
+  {
+    "source": "/docs/build/security-docs/securing-web-based-projects.html",
+    "destination": "/docs/build/security-docs/securing-web-based-projects"
+  },
+  {
+    "source": "/docs/build/security-docs/threat-modeling/STRIDE-template.html",
+    "destination": "/docs/build/security-docs/threat-modeling/STRIDE-template"
+  },
+  {
+    "source": "/docs/build/security-docs/threat-modeling/index.html",
+    "destination": "/docs/build/security-docs/threat-modeling/index"
+  },
+  {
+    "source": "/docs/build/security-docs/threat-modeling/pizza-restaurant-example.html",
+    "destination": "/docs/build/security-docs/threat-modeling/pizza-restaurant-example"
+  },
+  {
+    "source": "/docs/build/security-docs/threat-modeling/threat-modeling-description.html",
+    "destination": "/docs/build/security-docs/threat-modeling/threat-modeling-description"
+  },
+  {
+    "source": "/docs/build/security-docs/threat-modeling/threat-modeling-how-to.html",
+    "destination": "/docs/build/security-docs/threat-modeling/threat-modeling-how-to"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/alloc.html",
+    "destination": "/docs/build/smart-contracts/example-contracts/alloc"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/atomic-multi-swap.html",
+    "destination": "/docs/build/smart-contracts/example-contracts/atomic-multi-swap"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/atomic-swap.html",
+    "destination": "/docs/build/smart-contracts/example-contracts/atomic-swap"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/auth.html",
+    "destination": "/docs/build/smart-contracts/example-contracts/auth"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/bls-signature.html",
+    "destination": "/docs/build/smart-contracts/example-contracts/bls-signature"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/complex-account.html",
+    "destination": "/docs/build/smart-contracts/example-contracts/complex-account"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/cross-contract-call.html",
+    "destination": "/docs/build/smart-contracts/example-contracts/cross-contract-call"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/custom-types.html",
+    "destination": "/docs/build/smart-contracts/example-contracts/custom-types"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/delegate-auth.html",
+    "destination": "/docs/build/smart-contracts/example-contracts/delegate-auth"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/deployer.html",
+    "destination": "/docs/build/smart-contracts/example-contracts/deployer"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/errors.html",
+    "destination": "/docs/build/smart-contracts/example-contracts/errors"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/events.html",
+    "destination": "/docs/build/smart-contracts/example-contracts/events"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/fuzzing.html",
+    "destination": "/docs/build/smart-contracts/example-contracts/fuzzing"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/index.html",
+    "destination": "/docs/build/smart-contracts/example-contracts/index"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/liquidity-pool.html",
+    "destination": "/docs/build/smart-contracts/example-contracts/liquidity-pool"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/logging.html",
+    "destination": "/docs/build/smart-contracts/example-contracts/logging"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/mint-lock.html",
+    "destination": "/docs/build/smart-contracts/example-contracts/mint-lock"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/simple-account.html",
+    "destination": "/docs/build/smart-contracts/example-contracts/simple-account"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/single-offer-sale.html",
+    "destination": "/docs/build/smart-contracts/example-contracts/single-offer-sale"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/storage.html",
+    "destination": "/docs/build/smart-contracts/example-contracts/storage"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/timelock.html",
+    "destination": "/docs/build/smart-contracts/example-contracts/timelock"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/tokens.html",
+    "destination": "/docs/build/smart-contracts/example-contracts/tokens"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/upgradeable-contract.html",
+    "destination": "/docs/build/smart-contracts/example-contracts/upgradeable-contract"
+  },
+  {
+    "source": "/docs/build/smart-contracts/example-contracts/workspace.html",
+    "destination": "/docs/build/smart-contracts/example-contracts/workspace"
+  },
+  {
+    "source": "/docs/build/smart-contracts/getting-started/deploy-increment-contract.html",
+    "destination": "/docs/build/smart-contracts/getting-started/deploy-increment-contract"
+  },
+  {
+    "source": "/docs/build/smart-contracts/getting-started/deploy-to-testnet.html",
+    "destination": "/docs/build/smart-contracts/getting-started/deploy-to-testnet"
+  },
+  {
+    "source": "/docs/build/smart-contracts/getting-started/hello-world.html",
+    "destination": "/docs/build/smart-contracts/getting-started/hello-world"
+  },
+  {
+    "source": "/docs/build/smart-contracts/getting-started/hello-world-frontend.html",
+    "destination": "/docs/build/smart-contracts/getting-started/hello-world-frontend"
+  },
+  {
+    "source": "/docs/build/smart-contracts/getting-started/index.html",
+    "destination": "/docs/build/smart-contracts/getting-started/index"
+  },
+  {
+    "source": "/docs/build/smart-contracts/getting-started/setup.html",
+    "destination": "/docs/build/smart-contracts/getting-started/setup"
+  },
+  {
+    "source": "/docs/build/smart-contracts/getting-started/storing-data.html",
+    "destination": "/docs/build/smart-contracts/getting-started/storing-data"
+  },
+  {
+    "source": "/docs/build/smart-contracts/index.html",
+    "destination": "/docs/build/smart-contracts/index"
+  },
+  {
+    "source": "/docs/build/smart-contracts/overview.html",
+    "destination": "/docs/build/smart-contracts/overview"
+  },
+  {
+    "source": "/docs/data/analytics/analytics-providers/analytics-providers.html",
+    "destination": "/docs/data/analytics/analytics-providers"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/analyst-guide/connecting.html",
+    "destination": "/docs/data/analytics/hubble/analyst-guide/connecting"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/analyst-guide/creating-visualizations.html",
+    "destination": "/docs/data/analytics/hubble/analyst-guide/creating-visualizations"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/analyst-guide/history-vs-state-tables.html",
+    "destination": "/docs/data/analytics/hubble/analyst-guide/history-vs-state-tables"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/analyst-guide/index.html",
+    "destination": "/docs/data/analytics/hubble/analyst-guide/index"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/analyst-guide/optimizing-queries.html",
+    "destination": "/docs/data/analytics/hubble/analyst-guide/optimizing-queries"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.html",
+    "destination": "/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/analyst-guide/viewing-metadata.html",
+    "destination": "/docs/data/analytics/hubble/analyst-guide/viewing-metadata"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/account-signers.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/account-signers"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/accounts.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/accounts"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/claimable-balances.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/claimable-balances"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/config-settings.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/config-settings"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-code.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-code"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-data.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-data"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/evicted-keys.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/evicted-keys"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-assets.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-assets"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-contract-events.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-contract-events"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-effects.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-effects"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-ledgers.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-ledgers"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-operations.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-operations"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-trades.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-trades"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-transactions.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-transactions"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/index.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/index"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/liquidity-pools.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/liquidity-pools"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/offers.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/offers"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/restored-key.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/restored-key"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/trustlines.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/trustlines"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/ttl.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/ttl"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/account-balances-daily-agg.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/account-balances-daily-agg"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/asset-balances-daily-agg.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/asset-balances-daily-agg"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/daily-fee-stats-agg.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/daily-fee-stats-agg"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/hourly-fee-agg-account.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/hourly-fee-agg-account"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/hourly-soroban-fee-agg-contract.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/hourly-soroban-fee-agg-contract"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/index.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/index"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/ledger-fee-stats-agg.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/ledger-fee-stats-agg"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/soroban-core-metrics.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/soroban-core-metrics"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/trade-agg.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/trade-agg"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/tvl-agg.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/tvl-agg"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/index.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/index"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/account-signers-current.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/account-signers-current"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-current.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-current"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-snapshot.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-snapshot"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/claimable-balances-current.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/claimable-balances-current"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/config-settings-current.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/config-settings-current"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/config-settings-snapshot.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/config-settings-snapshot"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-code-current.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-code-current"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-current.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-current"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-snapshot.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-snapshot"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations-soroban.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations-soroban"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/evicted-keys-snapshot.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/evicted-keys-snapshot"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/index.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/index"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-current.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-current"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-snapshot.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-snapshot"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/offers-current.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/offers-current"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-cex-snapshot.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-cex-snapshot"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-fex-snapshot.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-fex-snapshot"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-sdex-snapshot.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-sdex-snapshot"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/token-transfers-raw.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/token-transfers-raw"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-current.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-current"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-snapshot.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-snapshot"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/ttl-current.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/ttl-current"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-lineage.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-lineage",
+    "permanent": true
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/data-model-diagram.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/data-model-diagram"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/data-catalog/index.html",
+    "destination": "/docs/data/analytics/hubble/data-catalog/index"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/developer-guide/backfill/JS-UDF.html",
+    "destination": "/docs/data/analytics/hubble/developer-guide/backfill/JS-UDF"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/developer-guide/backfill/data-import.html",
+    "destination": "/docs/data/analytics/hubble/developer-guide/backfill/data-import"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/developer-guide/backfill/index.html",
+    "destination": "/docs/data/analytics/hubble/developer-guide/backfill/index"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/developer-guide/connecting-to-bigquery/index.html",
+    "destination": "/docs/data/analytics/hubble/developer-guide/connecting-to-bigquery/index"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/developer-guide/data-curation/architecture.html",
+    "destination": "/docs/data/analytics/hubble/developer-guide/data-curation/architecture"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/developer-guide/data-curation/getting-started.html",
+    "destination": "/docs/data/analytics/hubble/developer-guide/data-curation/getting-started"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/developer-guide/data-curation/index.html",
+    "destination": "/docs/data/analytics/hubble/developer-guide/data-curation/index"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/developer-guide/data-curation/overview.html",
+    "destination": "/docs/data/analytics/hubble/developer-guide/data-curation/overview"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/developer-guide/index.html",
+    "destination": "/docs/data/analytics/hubble/developer-guide/index"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/architecture.html",
+    "destination": "/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/architecture"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/getting-started.html",
+    "destination": "/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/getting-started"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/index.html",
+    "destination": "/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/index"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/overview.html",
+    "destination": "/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/overview"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/developer-guide/source-system-ingestion/architecture.html",
+    "destination": "/docs/data/analytics/hubble/developer-guide/source-system-ingestion/architecture"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/developer-guide/source-system-ingestion/getting-started.html",
+    "destination": "/docs/data/analytics/hubble/developer-guide/source-system-ingestion/getting-started"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/developer-guide/source-system-ingestion/index.html",
+    "destination": "/docs/data/analytics/hubble/developer-guide/source-system-ingestion/index"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/developer-guide/source-system-ingestion/overview.html",
+    "destination": "/docs/data/analytics/hubble/developer-guide/source-system-ingestion/overview"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/developer-guide/visualization/getting-started.html",
+    "destination": "/docs/data/analytics/hubble/developer-guide/visualization/getting-started"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/developer-guide/visualization/index.html",
+    "destination": "/docs/data/analytics/hubble/developer-guide/visualization/index"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/developer-guide/visualization/overview.html",
+    "destination": "/docs/data/analytics/hubble/developer-guide/visualization/overview"
+  },
+  {
+    "source": "/docs/data/analytics/hubble/index.html",
+    "destination": "/docs/data/analytics/hubble/index"
+  },
+  {
+    "source": "/docs/data/analytics/index.html",
+    "destination": "/docs/data/analytics/index"
+  },
+  {
+    "source": "/docs/data/analytics/public-dashboards.html",
+    "destination": "/docs/data/analytics/public-dashboards"
+  },
+  {
+    "source": "/docs/data/apis/horizon/admin-guide/configuring.html",
+    "destination": "/docs/data/apis/horizon/admin-guide/configuring"
+  },
+  {
+    "source": "/docs/data/apis/horizon/admin-guide/index.html",
+    "destination": "/docs/data/apis/horizon/admin-guide/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/admin-guide/ingestion.html",
+    "destination": "/docs/data/apis/horizon/admin-guide/ingestion"
+  },
+  {
+    "source": "/docs/data/apis/horizon/admin-guide/ingestion-filtering.html",
+    "destination": "/docs/data/apis/horizon/admin-guide/ingestion-filtering"
+  },
+  {
+    "source": "/docs/data/apis/horizon/admin-guide/installing.html",
+    "destination": "/docs/data/apis/horizon/admin-guide/installing"
+  },
+  {
+    "source": "/docs/data/apis/horizon/admin-guide/monitoring.html",
+    "destination": "/docs/data/apis/horizon/admin-guide/monitoring"
+  },
+  {
+    "source": "/docs/data/apis/horizon/admin-guide/overview.html",
+    "destination": "/docs/data/apis/horizon/admin-guide/overview"
+  },
+  {
+    "source": "/docs/data/apis/horizon/admin-guide/prerequisites.html",
+    "destination": "/docs/data/apis/horizon/admin-guide/prerequisites"
+  },
+  {
+    "source": "/docs/data/apis/horizon/admin-guide/running.html",
+    "destination": "/docs/data/apis/horizon/admin-guide/running"
+  },
+  {
+    "source": "/docs/data/apis/horizon/admin-guide/scaling.html",
+    "destination": "/docs/data/apis/horizon/admin-guide/scaling"
+  },
+  {
+    "source": "/docs/data/apis/horizon/admin-guide/upgrading.html",
+    "destination": "/docs/data/apis/horizon/admin-guide/upgrading"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/aggregations/fee-stats/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/aggregations/fee-stats/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/aggregations/fee-stats/object.html",
+    "destination": "/docs/data/apis/horizon/api-reference/aggregations/fee-stats/object"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/aggregations/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/aggregations/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/aggregations/order-books/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/aggregations/order-books/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/aggregations/order-books/object.html",
+    "destination": "/docs/data/apis/horizon/api-reference/aggregations/order-books/object"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/aggregations/paths/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/aggregations/paths/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/aggregations/paths/object.html",
+    "destination": "/docs/data/apis/horizon/api-reference/aggregations/paths/object"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/aggregations/trade-aggregations/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/aggregations/trade-aggregations/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/aggregations/trade-aggregations/object.html",
+    "destination": "/docs/data/apis/horizon/api-reference/aggregations/trade-aggregations/object"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/cb-retrieve-related-operations.html",
+    "destination": "/docs/data/apis/horizon/api-reference/cb-retrieve-related-operations"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions.html",
+    "destination": "/docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/error-handling.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/error-handling"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/before-history.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/before-history"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/stale-history.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/stale-history"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/timeout.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/timeout"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-failed.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-failed"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-malformed.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-malformed"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/http-status-codes/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/http-status-codes/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/http-status-codes/standard.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/http-status-codes/standard"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/response.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/response"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/result-codes/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/result-codes/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/account-merge.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/account-merge"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/allow-trust.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/allow-trust"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/bump-sequence.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/bump-sequence"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/change-trust.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/change-trust"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-account.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-account"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-passive-sell-offer.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-passive-sell-offer"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-buy-offer.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-buy-offer"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-data.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-data"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-sell-offer.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-sell-offer"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-receive.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-receive"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-send.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-send"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/payment.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/payment"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/set-options.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/set-options"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/result-codes/operations.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/result-codes/operations"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/errors/result-codes/transactions.html",
+    "destination": "/docs/data/apis/horizon/api-reference/errors/result-codes/transactions"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/get-all-offers.html",
+    "destination": "/docs/data/apis/horizon/api-reference/get-all-offers"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/get-all-trades.html",
+    "destination": "/docs/data/apis/horizon/api-reference/get-all-trades"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/get-data-by-account-id.html",
+    "destination": "/docs/data/apis/horizon/api-reference/get-data-by-account-id"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/get-effects-by-account-id.html",
+    "destination": "/docs/data/apis/horizon/api-reference/get-effects-by-account-id"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/get-offer-by-offer-id.html",
+    "destination": "/docs/data/apis/horizon/api-reference/get-offer-by-offer-id"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/get-offers-by-account-id.html",
+    "destination": "/docs/data/apis/horizon/api-reference/get-offers-by-account-id"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/get-operations-by-account-id.html",
+    "destination": "/docs/data/apis/horizon/api-reference/get-operations-by-account-id"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/get-payments-by-account-id.html",
+    "destination": "/docs/data/apis/horizon/api-reference/get-payments-by-account-id"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/get-trades-by-account-id.html",
+    "destination": "/docs/data/apis/horizon/api-reference/get-trades-by-account-id"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/get-trades-by-offer-id.html",
+    "destination": "/docs/data/apis/horizon/api-reference/get-trades-by-offer-id"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/get-transactions-by-account-id.html",
+    "destination": "/docs/data/apis/horizon/api-reference/get-transactions-by-account-id"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/list-all-accounts.html",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-accounts"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/list-all-assets.html",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-assets"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/list-all-claimable-balances.html",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-claimable-balances"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/list-all-effects.html",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-effects"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/list-all-ledgers.html",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-ledgers"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/list-all-operations.html",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-operations"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/list-all-payments.html",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-payments"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/list-all-transactions.html",
+    "destination": "/docs/data/apis/horizon/api-reference/list-all-transactions"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/list-liquidity-pools.html",
+    "destination": "/docs/data/apis/horizon/api-reference/list-liquidity-pools"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths.html",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths.html",
+    "destination": "/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/list-trade-aggregations.html",
+    "destination": "/docs/data/apis/horizon/api-reference/list-trade-aggregations"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/lp-retrieve-related-operations.html",
+    "destination": "/docs/data/apis/horizon/api-reference/lp-retrieve-related-operations"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/lp-retrieve-related-transactions.html",
+    "destination": "/docs/data/apis/horizon/api-reference/lp-retrieve-related-transactions"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/accounts/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/accounts/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/accounts/object.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/accounts/object"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/assets/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/assets/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/assets/object.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/assets/object"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/claimablebalances/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/claimablebalances/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/claimablebalances/object.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/claimablebalances/object"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/effects/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/effects/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/effects/types.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/effects/types"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/ledgers/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/ledgers/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/ledgers/object.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/ledgers/object"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/liquiditypools/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/liquiditypools/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/offers/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/offers/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/offers/object.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/offers/object"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/operations/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/operations/object/account-merge.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/account-merge"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/operations/object/allow-trust.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/allow-trust"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/operations/object/begin-sponsoring-future-reserves.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/begin-sponsoring-future-reserves"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/operations/object/bump-sequence.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/bump-sequence"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/operations/object/buy-offer.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/buy-offer"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/operations/object/change-trust.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/change-trust"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/operations/object/claim-claimable-balance.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/claim-claimable-balance"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/operations/object/create-account.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/create-account"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/operations/object/create-claimable-balance.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/create-claimable-balance"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/operations/object/end-sponsoring-future-reserves.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/end-sponsoring-future-reserves"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/operations/object/extend-footprint-ttl.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/extend-footprint-ttl"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/operations/object/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/operations/object/invoke-host-function.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/invoke-host-function"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/operations/object/liquidity-pool-deposit.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/liquidity-pool-deposit"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/operations/object/liquidity-pool-withdraw.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/liquidity-pool-withdraw"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/operations/object/manage-data.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/manage-data"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/operations/object/passive-sell-offer.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/passive-sell-offer"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-receive.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-receive"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-send.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-send"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/operations/object/restore-footprint.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/restore-footprint"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/operations/object/revoke-sponsorship.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/revoke-sponsorship"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/operations/object/sell-offer.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/sell-offer"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/operations/object/set-options.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/operations/object/set-options"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/payments/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/payments/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/payments/object.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/payments/object"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/trades/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/trades/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/trades/object.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/trades/object"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/transactions/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/transactions/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/resources/transactions/object.html",
+    "destination": "/docs/data/apis/horizon/api-reference/resources/transactions/object"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance.html",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/retrieve-a-ledger.html",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledger"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects.html",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations.html",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments.html",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions.html",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool.html",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/retrieve-a-transaction.html",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-transaction"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects.html",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations.html",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments.html",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/retrieve-an-account.html",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-account"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/retrieve-an-operation.html",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-operation"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/retrieve-an-operations-effects.html",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-operations-effects"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/retrieve-an-order-book.html",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-an-order-book"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/retrieve-fee-stats.html",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-fee-stats"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/retrieve-related-effects.html",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-related-effects"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/retrieve-related-trades.html",
+    "destination": "/docs/data/apis/horizon/api-reference/retrieve-related-trades"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/structure/consistency.html",
+    "destination": "/docs/data/apis/horizon/api-reference/structure/consistency"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/structure/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/structure/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/structure/pagination/index.html",
+    "destination": "/docs/data/apis/horizon/api-reference/structure/pagination/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/structure/pagination/page-arguments.html",
+    "destination": "/docs/data/apis/horizon/api-reference/structure/pagination/page-arguments"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/structure/rate-limiting.html",
+    "destination": "/docs/data/apis/horizon/api-reference/structure/rate-limiting"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/structure/response-format.html",
+    "destination": "/docs/data/apis/horizon/api-reference/structure/response-format"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/structure/streaming.html",
+    "destination": "/docs/data/apis/horizon/api-reference/structure/streaming"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/structure/xdr.html",
+    "destination": "/docs/data/apis/horizon/api-reference/structure/xdr"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/submit-a-transaction.html",
+    "destination": "/docs/data/apis/horizon/api-reference/submit-a-transaction"
+  },
+  {
+    "source": "/docs/data/apis/horizon/api-reference/submit-async-transaction.html",
+    "destination": "/docs/data/apis/horizon/api-reference/submit-async-transaction"
+  },
+  {
+    "source": "/docs/data/apis/horizon/index.html",
+    "destination": "/docs/data/apis/horizon/index"
+  },
+  {
+    "source": "/docs/data/apis/horizon/providers.html",
+    "destination": "/docs/data/apis/horizon/providers"
+  },
+  {
+    "source": "/docs/data/apis/index.html",
+    "destination": "/docs/data/apis/index"
+  },
+  {
+    "source": "/docs/data/apis/migrate-from-horizon-to-rpc.html",
+    "destination": "/docs/data/apis/migrate-from-horizon-to-rpc"
+  },
+  {
+    "source": "/docs/data/apis/rpc/admin-guide/configuring.html",
+    "destination": "/docs/data/apis/rpc/admin-guide/configuring"
+  },
+  {
+    "source": "/docs/data/apis/rpc/admin-guide/data-lake-integration.html",
+    "destination": "/docs/data/apis/rpc/admin-guide/data-lake-integration"
+  },
+  {
+    "source": "/docs/data/apis/rpc/admin-guide/development.html",
+    "destination": "/docs/data/apis/rpc/admin-guide/development"
+  },
+  {
+    "source": "/docs/data/apis/rpc/admin-guide/index.html",
+    "destination": "/docs/data/apis/rpc/admin-guide/index"
+  },
+  {
+    "source": "/docs/data/apis/rpc/admin-guide/installing.html",
+    "destination": "/docs/data/apis/rpc/admin-guide/installing"
+  },
+  {
+    "source": "/docs/data/apis/rpc/admin-guide/monitoring.html",
+    "destination": "/docs/data/apis/rpc/admin-guide/monitoring"
+  },
+  {
+    "source": "/docs/data/apis/rpc/admin-guide/prerequisites.html",
+    "destination": "/docs/data/apis/rpc/admin-guide/prerequisites"
+  },
+  {
+    "source": "/docs/data/apis/rpc/admin-guide/running.html",
+    "destination": "/docs/data/apis/rpc/admin-guide/running"
+  },
+  {
+    "source": "/docs/data/apis/rpc/api-reference/index.html",
+    "destination": "/docs/data/apis/rpc/api-reference/index"
+  },
+  {
+    "source": "/docs/data/apis/rpc/api-reference/methods/getEvents.html",
+    "destination": "/docs/data/apis/rpc/api-reference/methods/getEvents"
+  },
+  {
+    "source": "/docs/data/apis/rpc/api-reference/methods/getFeeStats.html",
+    "destination": "/docs/data/apis/rpc/api-reference/methods/getFeeStats"
+  },
+  {
+    "source": "/docs/data/apis/rpc/api-reference/methods/getHealth.html",
+    "destination": "/docs/data/apis/rpc/api-reference/methods/getHealth"
+  },
+  {
+    "source": "/docs/data/apis/rpc/api-reference/methods/getLatestLedger.html",
+    "destination": "/docs/data/apis/rpc/api-reference/methods/getLatestLedger"
+  },
+  {
+    "source": "/docs/data/apis/rpc/api-reference/methods/getLedgerEntries.html",
+    "destination": "/docs/data/apis/rpc/api-reference/methods/getLedgerEntries"
+  },
+  {
+    "source": "/docs/data/apis/rpc/api-reference/methods/getLedgers.html",
+    "destination": "/docs/data/apis/rpc/api-reference/methods/getLedgers"
+  },
+  {
+    "source": "/docs/data/apis/rpc/api-reference/methods/getNetwork.html",
+    "destination": "/docs/data/apis/rpc/api-reference/methods/getNetwork"
+  },
+  {
+    "source": "/docs/data/apis/rpc/api-reference/methods/getTransaction.html",
+    "destination": "/docs/data/apis/rpc/api-reference/methods/getTransaction"
+  },
+  {
+    "source": "/docs/data/apis/rpc/api-reference/methods/getTransactions.html",
+    "destination": "/docs/data/apis/rpc/api-reference/methods/getTransactions"
+  },
+  {
+    "source": "/docs/data/apis/rpc/api-reference/methods/getVersionInfo.html",
+    "destination": "/docs/data/apis/rpc/api-reference/methods/getVersionInfo"
+  },
+  {
+    "source": "/docs/data/apis/rpc/api-reference/methods/index.html",
+    "destination": "/docs/data/apis/rpc/api-reference/methods/index"
+  },
+  {
+    "source": "/docs/data/apis/rpc/api-reference/methods/sendTransaction.html",
+    "destination": "/docs/data/apis/rpc/api-reference/methods/sendTransaction"
+  },
+  {
+    "source": "/docs/data/apis/rpc/api-reference/methods/simulateTransaction.html",
+    "destination": "/docs/data/apis/rpc/api-reference/methods/simulateTransaction"
+  },
+  {
+    "source": "/docs/data/apis/rpc/api-reference/structure/data-format.html",
+    "destination": "/docs/data/apis/rpc/api-reference/structure/data-format"
+  },
+  {
+    "source": "/docs/data/apis/rpc/api-reference/structure/index.html",
+    "destination": "/docs/data/apis/rpc/api-reference/structure/index"
+  },
+  {
+    "source": "/docs/data/apis/rpc/api-reference/structure/json-rpc.html",
+    "destination": "/docs/data/apis/rpc/api-reference/structure/json-rpc"
+  },
+  {
+    "source": "/docs/data/apis/rpc/api-reference/structure/pagination.html",
+    "destination": "/docs/data/apis/rpc/api-reference/structure/pagination"
+  },
+  {
+    "source": "/docs/data/apis/rpc/index.html",
+    "destination": "/docs/data/apis/rpc/index"
+  },
+  {
+    "source": "/docs/data/apis/rpc/providers.html",
+    "destination": "/docs/data/apis/rpc/providers"
+  },
+  {
+    "source": "/docs/data/index.html",
+    "destination": "/docs/data/index"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/galexie/admin_guide/configuring.html",
+    "destination": "/docs/data/indexers/build-your-own/galexie/admin_guide/configuring"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/galexie/admin_guide/full-history-exporting.html",
+    "destination": "/docs/data/indexers/build-your-own/galexie/admin_guide/full-history-exporting"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/galexie/admin_guide/index.html",
+    "destination": "/docs/data/indexers/build-your-own/galexie/admin_guide/index"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/galexie/admin_guide/installing.html",
+    "destination": "/docs/data/indexers/build-your-own/galexie/admin_guide/installing"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/galexie/admin_guide/monitoring.html",
+    "destination": "/docs/data/indexers/build-your-own/galexie/admin_guide/monitoring"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/galexie/admin_guide/prerequisites.html",
+    "destination": "/docs/data/indexers/build-your-own/galexie/admin_guide/prerequisites"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/galexie/admin_guide/running.html",
+    "destination": "/docs/data/indexers/build-your-own/galexie/admin_guide/running"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/galexie/admin_guide/setup.html",
+    "destination": "/docs/data/indexers/build-your-own/galexie/admin_guide/setup"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/galexie/examples/gcs-export.html",
+    "destination": "/docs/data/indexers/build-your-own/galexie/examples/gcs-export"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/galexie/examples/index.html",
+    "destination": "/docs/data/indexers/build-your-own/galexie/examples/index"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/galexie/index.html",
+    "destination": "/docs/data/indexers/build-your-own/galexie/index"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/galexie/providers.html",
+    "destination": "/docs/data/indexers/build-your-own/galexie/providers"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/index.html",
+    "destination": "/docs/data/indexers/build-your-own/index"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/architecture.html",
+    "destination": "/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/architecture"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/index.html",
+    "destination": "/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/index"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/bufferedstoragebackend.html",
+    "destination": "/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/bufferedstoragebackend"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/captivecore.html",
+    "destination": "/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/captivecore"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/index.html",
+    "destination": "/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/index"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/rpcledgerbackend.html",
+    "destination": "/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/rpcledgerbackend"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerreaders.html",
+    "destination": "/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerreaders"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/prerequisites.html",
+    "destination": "/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/prerequisites"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/ingest-sdk/examples/changes.html",
+    "destination": "/docs/data/indexers/build-your-own/ingest-sdk/examples/changes"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/ingest-sdk/examples/index.html",
+    "destination": "/docs/data/indexers/build-your-own/ingest-sdk/examples/index"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/ingest-sdk/examples/ledger_entry_statistics.html",
+    "destination": "/docs/data/indexers/build-your-own/ingest-sdk/examples/ledger_entry_statistics"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/ingest-sdk/examples/transaction_statistics.html",
+    "destination": "/docs/data/indexers/build-your-own/ingest-sdk/examples/transaction_statistics"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/ingest-sdk/index.html",
+    "destination": "/docs/data/indexers/build-your-own/ingest-sdk/index"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/processors/index.html",
+    "destination": "/docs/data/indexers/build-your-own/processors/index"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/processors/token-transfer-processor/examples/event_stats.html",
+    "destination": "/docs/data/indexers/build-your-own/processors/token-transfer-processor/examples/event_stats"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/processors/token-transfer-processor/examples/filter_events.html",
+    "destination": "/docs/data/indexers/build-your-own/processors/token-transfer-processor/examples/filter_events"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/processors/token-transfer-processor/examples/index.html",
+    "destination": "/docs/data/indexers/build-your-own/processors/token-transfer-processor/examples/index"
+  },
+  {
+    "source": "/docs/data/indexers/build-your-own/processors/token-transfer-processor/index.html",
+    "destination": "/docs/data/indexers/build-your-own/processors/token-transfer-processor/index"
+  },
+  {
+    "source": "/docs/data/indexers/index.html",
+    "destination": "/docs/data/indexers/index"
+  },
+  {
+    "source": "/docs/data/oracles/index.html",
+    "destination": "/docs/data/oracles/index"
+  },
+  {
+    "source": "/docs/data/oracles/oracle-providers.html",
+    "destination": "/docs/data/oracles/oracle-providers"
+  },
+  {
+    "source": "/docs/learn/fundamentals/anchors.html",
+    "destination": "/docs/learn/fundamentals/anchors"
+  },
+  {
+    "source": "/docs/learn/fundamentals/contract-development/authorization.html",
+    "destination": "/docs/learn/fundamentals/contract-development/authorization"
+  },
+  {
+    "source": "/docs/learn/fundamentals/contract-development/contract-interactions/cross-contract.html",
+    "destination": "/docs/learn/fundamentals/contract-development/contract-interactions/cross-contract"
+  },
+  {
+    "source": "/docs/learn/fundamentals/contract-development/contract-interactions/index.html",
+    "destination": "/docs/learn/fundamentals/contract-development/contract-interactions/index"
+  },
+  {
+    "source": "/docs/learn/fundamentals/contract-development/contract-interactions/overview.html",
+    "destination": "/docs/learn/fundamentals/contract-development/contract-interactions/overview"
+  },
+  {
+    "source": "/docs/learn/fundamentals/contract-development/contract-interactions/stellar-transaction.html",
+    "destination": "/docs/learn/fundamentals/contract-development/contract-interactions/stellar-transaction"
+  },
+  {
+    "source": "/docs/learn/fundamentals/contract-development/contract-interactions/tests.html",
+    "destination": "/docs/learn/fundamentals/contract-development/contract-interactions/tests"
+  },
+  {
+    "source": "/docs/learn/fundamentals/contract-development/contract-interactions/transaction-simulation.html",
+    "destination": "/docs/learn/fundamentals/contract-development/contract-interactions/transaction-simulation"
+  },
+  {
+    "source": "/docs/learn/fundamentals/contract-development/contract-lifecycle.html",
+    "destination": "/docs/learn/fundamentals/contract-development/contract-lifecycle"
+  },
+  {
+    "source": "/docs/learn/fundamentals/contract-development/environment-concepts.html",
+    "destination": "/docs/learn/fundamentals/contract-development/environment-concepts"
+  },
+  {
+    "source": "/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging.html",
+    "destination": "/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging"
+  },
+  {
+    "source": "/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging-errors.html",
+    "destination": "/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging-errors"
+  },
+  {
+    "source": "/docs/learn/fundamentals/contract-development/errors-and-debugging/errors.html",
+    "destination": "/docs/learn/fundamentals/contract-development/errors-and-debugging/errors"
+  },
+  {
+    "source": "/docs/learn/fundamentals/contract-development/errors-and-debugging/index.html",
+    "destination": "/docs/learn/fundamentals/contract-development/errors-and-debugging/index"
+  },
+  {
+    "source": "/docs/learn/fundamentals/contract-development/index.html",
+    "destination": "/docs/learn/fundamentals/contract-development/index"
+  },
+  {
+    "source": "/docs/learn/fundamentals/contract-development/overview.html",
+    "destination": "/docs/learn/fundamentals/contract-development/overview"
+  },
+  {
+    "source": "/docs/learn/fundamentals/contract-development/rust-dialect.html",
+    "destination": "/docs/learn/fundamentals/contract-development/rust-dialect"
+  },
+  {
+    "source": "/docs/learn/fundamentals/contract-development/storage/index.html",
+    "destination": "/docs/learn/fundamentals/contract-development/storage/index"
+  },
+  {
+    "source": "/docs/learn/fundamentals/contract-development/storage/persisting-data.html",
+    "destination": "/docs/learn/fundamentals/contract-development/storage/persisting-data"
+  },
+  {
+    "source": "/docs/learn/fundamentals/contract-development/storage/state-archival.html",
+    "destination": "/docs/learn/fundamentals/contract-development/storage/state-archival"
+  },
+  {
+    "source": "/docs/learn/fundamentals/contract-development/types/built-in-types.html",
+    "destination": "/docs/learn/fundamentals/contract-development/types/built-in-types"
+  },
+  {
+    "source": "/docs/learn/fundamentals/contract-development/types/custom-types.html",
+    "destination": "/docs/learn/fundamentals/contract-development/types/custom-types"
+  },
+  {
+    "source": "/docs/learn/fundamentals/contract-development/types/fully-typed-contracts.html",
+    "destination": "/docs/learn/fundamentals/contract-development/types/fully-typed-contracts"
+  },
+  {
+    "source": "/docs/learn/fundamentals/contract-development/types/index.html",
+    "destination": "/docs/learn/fundamentals/contract-development/types/index"
+  },
+  {
+    "source": "/docs/learn/fundamentals/data-format/index.html",
+    "destination": "/docs/learn/fundamentals/data-format/index"
+  },
+  {
+    "source": "/docs/learn/fundamentals/data-format/xdr.html",
+    "destination": "/docs/learn/fundamentals/data-format/xdr"
+  },
+  {
+    "source": "/docs/learn/fundamentals/data-format/xdr-json.html",
+    "destination": "/docs/learn/fundamentals/data-format/xdr-json"
+  },
+  {
+    "source": "/docs/learn/fundamentals/fees-resource-limits-metering.html",
+    "destination": "/docs/learn/fundamentals/fees-resource-limits-metering"
+  },
+  {
+    "source": "/docs/learn/fundamentals/index.html",
+    "destination": "/docs/learn/fundamentals/index"
+  },
+  {
+    "source": "/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.html",
+    "destination": "/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools"
+  },
+  {
+    "source": "/docs/learn/fundamentals/lumens.html",
+    "destination": "/docs/learn/fundamentals/lumens"
+  },
+  {
+    "source": "/docs/learn/fundamentals/stellar-consensus-protocol.html",
+    "destination": "/docs/learn/fundamentals/stellar-consensus-protocol"
+  },
+  {
+    "source": "/docs/learn/fundamentals/stellar-data-structures/accounts.html",
+    "destination": "/docs/learn/fundamentals/stellar-data-structures/accounts"
+  },
+  {
+    "source": "/docs/learn/fundamentals/stellar-data-structures/assets.html",
+    "destination": "/docs/learn/fundamentals/stellar-data-structures/assets"
+  },
+  {
+    "source": "/docs/learn/fundamentals/stellar-data-structures/contracts.html",
+    "destination": "/docs/learn/fundamentals/stellar-data-structures/contracts"
+  },
+  {
+    "source": "/docs/learn/fundamentals/stellar-data-structures/events.html",
+    "destination": "/docs/learn/fundamentals/stellar-data-structures/events"
+  },
+  {
+    "source": "/docs/learn/fundamentals/stellar-data-structures/index.html",
+    "destination": "/docs/learn/fundamentals/stellar-data-structures/index"
+  },
+  {
+    "source": "/docs/learn/fundamentals/stellar-data-structures/ledgers.html",
+    "destination": "/docs/learn/fundamentals/stellar-data-structures/ledgers"
+  },
+  {
+    "source": "/docs/learn/fundamentals/stellar-ecosystem-proposals.html",
+    "destination": "/docs/learn/fundamentals/stellar-ecosystem-proposals"
+  },
+  {
+    "source": "/docs/learn/fundamentals/stellar-stack.html",
+    "destination": "/docs/learn/fundamentals/stellar-stack"
+  },
+  {
+    "source": "/docs/learn/fundamentals/transactions/index.html",
+    "destination": "/docs/learn/fundamentals/transactions/index"
+  },
+  {
+    "source": "/docs/learn/fundamentals/transactions/list-of-operations.html",
+    "destination": "/docs/learn/fundamentals/transactions/list-of-operations"
+  },
+  {
+    "source": "/docs/learn/fundamentals/transactions/operations-and-transactions.html",
+    "destination": "/docs/learn/fundamentals/transactions/operations-and-transactions"
+  },
+  {
+    "source": "/docs/learn/fundamentals/transactions/signatures-multisig.html",
+    "destination": "/docs/learn/fundamentals/transactions/signatures-multisig"
+  },
+  {
+    "source": "/docs/learn/fundamentals/transactions/transaction-lifecycle.html",
+    "destination": "/docs/learn/fundamentals/transactions/transaction-lifecycle"
+  },
+  {
+    "source": "/docs/learn/glossary.html",
+    "destination": "/docs/learn/glossary"
+  },
+  {
+    "source": "/docs/learn/interactive/dapp-world.html",
+    "destination": "/docs/learn/interactive/dapp-world"
+  },
+  {
+    "source": "/docs/learn/interactive/fca00c.html",
+    "destination": "/docs/learn/interactive/fca00c"
+  },
+  {
+    "source": "/docs/learn/interactive/index.html",
+    "destination": "/docs/learn/interactive/index"
+  },
+  {
+    "source": "/docs/learn/interactive/quest.html",
+    "destination": "/docs/learn/interactive/quest"
+  },
+  {
+    "source": "/docs/learn/migrate/evm/index.html",
+    "destination": "/docs/learn/migrate/evm/index"
+  },
+  {
+    "source": "/docs/learn/migrate/evm/introduction-to-solidity-and-rust.html",
+    "destination": "/docs/learn/migrate/evm/introduction-to-solidity-and-rust"
+  },
+  {
+    "source": "/docs/learn/migrate/evm/smart-contract-deployment.html",
+    "destination": "/docs/learn/migrate/evm/smart-contract-deployment"
+  },
+  {
+    "source": "/docs/learn/migrate/evm/solidity-and-rust-advanced-concepts.html",
+    "destination": "/docs/learn/migrate/evm/solidity-and-rust-advanced-concepts"
+  },
+  {
+    "source": "/docs/learn/migrate/evm/solidity-and-rust-basics.html",
+    "destination": "/docs/learn/migrate/evm/solidity-and-rust-basics"
+  },
+  {
+    "source": "/docs/learn/migrate/evm/solidity-support-via-solang.html",
+    "destination": "/docs/learn/migrate/evm/solidity-support-via-solang"
+  },
+  {
+    "source": "/docs/learn/migrate/index.html",
+    "destination": "/docs/learn/migrate/index"
+  },
+  {
+    "source": "/docs/networks/audits/index.html",
+    "destination": "/docs/networks/audits/index"
+  },
+  {
+    "source": "/docs/networks/audits/soroban-poseidon.html",
+    "destination": "/docs/networks/audits/soroban-poseidon"
+  },
+  {
+    "source": "/docs/networks/audits/soroban-sdk.html",
+    "destination": "/docs/networks/audits/soroban-sdk"
+  },
+  {
+    "source": "/docs/networks/audits/stellar-core.html",
+    "destination": "/docs/networks/audits/stellar-core"
+  },
+  {
+    "source": "/docs/networks/audits/stellar-rpc.html",
+    "destination": "/docs/networks/audits/stellar-rpc"
+  },
+  {
+    "source": "/docs/networks/index.html",
+    "destination": "/docs/networks/index"
+  },
+  {
+    "source": "/docs/networks/resource-limits-fees.html",
+    "destination": "/docs/networks/resource-limits-fees"
+  },
+  {
+    "source": "/docs/networks/software-versions.html",
+    "destination": "/docs/networks/software-versions"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/admin-guide/architecture.html",
+    "destination": "/docs/platforms/anchor-platform/admin-guide/architecture"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/admin-guide/assets-and-client-wallets.html",
+    "destination": "/docs/platforms/anchor-platform/admin-guide/assets-and-client-wallets"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/admin-guide/events/delivery.html",
+    "destination": "/docs/platforms/anchor-platform/admin-guide/events/delivery"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/admin-guide/events/getting-started.html",
+    "destination": "/docs/platforms/anchor-platform/admin-guide/events/getting-started"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/admin-guide/events/index.html",
+    "destination": "/docs/platforms/anchor-platform/admin-guide/events/index"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/admin-guide/events/integration.html",
+    "destination": "/docs/platforms/anchor-platform/admin-guide/events/integration"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/admin-guide/getting-started.html",
+    "destination": "/docs/platforms/anchor-platform/admin-guide/getting-started"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/admin-guide/index.html",
+    "destination": "/docs/platforms/anchor-platform/admin-guide/index"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/callbacks/del-customer.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/callbacks/del-customer"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/callbacks/get-customer.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/callbacks/get-customer"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/callbacks/get-rates.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/callbacks/get-rates"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/callbacks/index.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/callbacks/index"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/callbacks/post-event.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/callbacks/post-event"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/callbacks/put-customer.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/callbacks/put-customer"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/index.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/index"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/index.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/index"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/index.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/index"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_payment.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_payment"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_refund.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_refund"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transaction.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transaction"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transactions.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transactions"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/index.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/index"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_amounts_updated.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_amounts_updated"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_customer_info_updated.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_customer_info_updated"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_interactive_flow_completed.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_interactive_flow_completed"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_available.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_available"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_pending.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_pending"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_received.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_received"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_sent.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_sent"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_received.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_received"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_sent.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_sent"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_pending.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_pending"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_sent.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_sent"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_error.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_error"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_expired.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_expired"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_on_hold.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_on_hold"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_recovery.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_recovery"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_trust_set.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_trust_set"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_offchain_funds.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_offchain_funds"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_onchain_funds.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_onchain_funds"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_trust.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_trust"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/rpc/overview.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/rpc/overview"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transaction.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transaction"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transactions.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transactions"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/api-reference/platform/transactions/index.html",
+    "destination": "/docs/platforms/anchor-platform/api-reference/platform/transactions/index"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/index.html",
+    "destination": "/docs/platforms/anchor-platform/index"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/sep-guide/index.html",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/index"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/sep-guide/sep1/index.html",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep1/index"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/sep-guide/sep10/index.html",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep10/index"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/sep-guide/sep24/configuration.html",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep24/configuration"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/sep-guide/sep24/example.html",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep24/example"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/sep-guide/sep24/faq.html",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep24/faq"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/sep-guide/sep24/getting-started.html",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep24/getting-started"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/sep-guide/sep24/index.html",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep24/index"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/sep-guide/sep24/integration.html",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep24/integration"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/sep-guide/sep24/setting-up-production-server.html",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep24/setting-up-production-server"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/sep-guide/sep31/configuration.html",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep31/configuration"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/sep-guide/sep31/getting-started.html",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep31/getting-started"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/sep-guide/sep31/index.html",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep31/index"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/sep-guide/sep31/integration.html",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep31/integration"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/sep-guide/sep45/index.html",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep45/index"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/sep-guide/sep6/configuration.html",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep6/configuration"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/sep-guide/sep6/getting-started.html",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep6/getting-started"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/sep-guide/sep6/index.html",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep6/index"
+  },
+  {
+    "source": "/docs/platforms/anchor-platform/sep-guide/sep6/integration.html",
+    "destination": "/docs/platforms/anchor-platform/sep-guide/sep6/integration"
+  },
+  {
+    "source": "/docs/platforms/index.html",
+    "destination": "/docs/platforms/index"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/admin-guide/advanced-configuration.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/advanced-configuration"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/admin-guide/cli-manual.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/cli-manual"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/admin-guide/configuring-sdp.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/configuring-sdp"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/admin-guide/deploy-the-sdp.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/deploy-the-sdp"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/admin-guide/design-and-architecture.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/design-and-architecture"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/admin-guide/embedded-wallets.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/embedded-wallets"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/admin-guide/getting-started.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/getting-started"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/admin-guide/index.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/index"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/admin-guide/making-your-wallet-sdp-ready.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/making-your-wallet-sdp-ready"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/admin-guide/monitoring.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/monitoring"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/admin-guide/overview.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/overview"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/admin-guide/security.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/security"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/admin-guide/troubleshooting.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/troubleshooting"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/account-picker.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/account-picker"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/analytics.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/analytics"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/circle-configuration.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/circle-configuration"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/dashboard-home.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/dashboard-home"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/disbursements.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/disbursements"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/distribution-accounts.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/distribution-accounts"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/index.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/index"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/payments.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/payments"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/receivers.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/receivers"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/admin.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/admin"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/api-keys.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/api-keys"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/archive-distribution-wallet.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/archive-distribution-wallet"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/authenticate-mfa.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/authenticate-mfa"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/authentication.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/authentication"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/balances.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/balances"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/bridge-integration.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/bridge-integration"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/create-api-key.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/create-api-key"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/create-asset.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/create-asset"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/create-direct-payment.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/create-direct-payment"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/create-disbursement.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/create-disbursement"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/create-distribution-wallet.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/create-distribution-wallet"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/create-receiver.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/create-receiver"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/create-tenant.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/create-tenant"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/create-user.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/create-user"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/create-wallet.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/create-wallet"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/default-tenant.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/default-tenant"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/delete-api-key.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/delete-api-key"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/delete-asset.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/delete-asset"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/delete-wallet.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/delete-wallet"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/disbursements.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/disbursements"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/distribution-wallets.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/distribution-wallets"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/export-disbursements.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/export-disbursements"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/export-payments-csv.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/export-payments-csv"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/export-receivers-csv.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/export-receivers-csv"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/forgot-password.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/forgot-password"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/get-all-assets.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/get-all-assets"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/get-all-roles.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/get-all-roles"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/get-all-tenants.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/get-all-tenants"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/get-all-users.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/get-all-users"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/get-all-wallets.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/get-all-wallets"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/get-api-key.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/get-api-key"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/get-bridge-integration.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/get-bridge-integration"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-audit.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-audit"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-balance.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-balance"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-capabilities.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-capabilities"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallets-total-balance.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallets-total-balance"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-circle-balances.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-circle-balances"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-info.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-info"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-logo.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-logo"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/get-profile.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/get-profile"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/get-receiver-registration-info.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/get-receiver-registration-info"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/get-sep-24-info.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/get-sep-24-info"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/grant-distribution-wallet-membership.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/grant-distribution-wallet-membership"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/index.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/index"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursements.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursements"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/list-all-payments.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/list-all-payments"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/list-all-receivers.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/list-all-receivers"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/list-api-keys.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/list-api-keys"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallet-memberships.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallet-memberships"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallets.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallets"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/list-receiver-verification-types.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/list-receiver-verification-types"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/list-registration-contact-types.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/list-registration-contact-types"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/log-in.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/log-in"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/organization.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/organization"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/patch-organization-circle.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/patch-organization-circle"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/payments.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/payments"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/profile.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/profile"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/promote-distribution-wallet-to-default.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/promote-distribution-wallet-to-default"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/provide-signed-challenge-transaction.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/provide-signed-challenge-transaction"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/receivers.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/receivers"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/refresh-token.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/refresh-token"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/registration.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/registration"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/request-registration-url.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/request-registration-url"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/reset-password.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/reset-password"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/reset-user-password.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/reset-user-password"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-stellar-info-file.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-stellar-info-file"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/retry-payments.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/retry-payments"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/revoke-distribution-wallet-membership.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/revoke-distribution-wallet-membership"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/send-one-time-passcode.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/send-one-time-passcode"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/start-wallet-registration.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/start-wallet-registration"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/statistics.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/statistics"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/update-a-tenant.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/update-a-tenant"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/update-api-key.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/update-api-key"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/update-bridge-integration.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/update-bridge-integration"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/update-organization-profile.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/update-organization-profile"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/update-payment-status.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/update-payment-status"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet-status.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet-status"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/update-user-activation-status.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/update-user-activation-status"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/update-user-profile.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/update-user-profile"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/update-user-role.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/update-user-role"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/update-wallet.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/update-wallet"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/users.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/users"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/api-reference/verify-receiver-registration.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/api-reference/verify-receiver-registration"
+  },
+  {
+    "source": "/docs/platforms/stellar-disbursement-platform/index.html",
+    "destination": "/docs/platforms/stellar-disbursement-platform/index"
+  },
+  {
+    "source": "/docs/tokens/anatomy-of-an-asset.html",
+    "destination": "/docs/tokens/anatomy-of-an-asset"
+  },
+  {
+    "source": "/docs/tokens/control-asset-access.html",
+    "destination": "/docs/tokens/control-asset-access"
+  },
+  {
+    "source": "/docs/tokens/cross-chain-transfers.html",
+    "destination": "/docs/tokens/cross-chain-transfers"
+  },
+  {
+    "source": "/docs/tokens/how-to-issue-an-asset.html",
+    "destination": "/docs/tokens/how-to-issue-an-asset"
+  },
+  {
+    "source": "/docs/tokens/index.html",
+    "destination": "/docs/tokens/index"
+  },
+  {
+    "source": "/docs/tokens/publishing-asset-info.html",
+    "destination": "/docs/tokens/publishing-asset-info"
+  },
+  {
+    "source": "/docs/tokens/quickstart.html",
+    "destination": "/docs/tokens/quickstart"
+  },
+  {
+    "source": "/docs/tokens/stellar-asset-contract.html",
+    "destination": "/docs/tokens/stellar-asset-contract"
+  },
+  {
+    "source": "/docs/tokens/token-interface.html",
+    "destination": "/docs/tokens/token-interface"
+  },
+  {
+    "source": "/docs/tokens/usdt0-layerzero.html",
+    "destination": "/docs/tokens/usdt0-layerzero"
+  },
+  {
+    "source": "/launch/usdt0.html",
+    "destination": "/launch/usdt0"
+  },
+  {
+    "source": "/docs/tools/cli/cookbook/asset-management.html",
+    "destination": "/docs/tools/cli/cookbook/asset-management"
+  },
+  {
+    "source": "/docs/tools/cli/cookbook/contract-build-meta.html",
+    "destination": "/docs/tools/cli/cookbook/contract-build-meta"
+  },
+  {
+    "source": "/docs/tools/cli/cookbook/contract-invoke-arguments.html",
+    "destination": "/docs/tools/cli/cookbook/contract-invoke-arguments"
+  },
+  {
+    "source": "/docs/tools/cli/cookbook/contract-lifecycle.html",
+    "destination": "/docs/tools/cli/cookbook/contract-lifecycle"
+  },
+  {
+    "source": "/docs/tools/cli/cookbook/deploy-contract.html",
+    "destination": "/docs/tools/cli/cookbook/deploy-contract"
+  },
+  {
+    "source": "/docs/tools/cli/cookbook/deploy-stellar-asset-contract.html",
+    "destination": "/docs/tools/cli/cookbook/deploy-stellar-asset-contract"
+  },
+  {
+    "source": "/docs/tools/cli/cookbook/extend-contract-instance.html",
+    "destination": "/docs/tools/cli/cookbook/extend-contract-instance"
+  },
+  {
+    "source": "/docs/tools/cli/cookbook/extend-contract-storage.html",
+    "destination": "/docs/tools/cli/cookbook/extend-contract-storage"
+  },
+  {
+    "source": "/docs/tools/cli/cookbook/extend-contract-wasm.html",
+    "destination": "/docs/tools/cli/cookbook/extend-contract-wasm"
+  },
+  {
+    "source": "/docs/tools/cli/cookbook/index.html",
+    "destination": "/docs/tools/cli/cookbook/index"
+  },
+  {
+    "source": "/docs/tools/cli/cookbook/payments-and-assets.html",
+    "destination": "/docs/tools/cli/cookbook/payments-and-assets"
+  },
+  {
+    "source": "/docs/tools/cli/cookbook/restore-contract-instance.html",
+    "destination": "/docs/tools/cli/cookbook/restore-contract-instance"
+  },
+  {
+    "source": "/docs/tools/cli/cookbook/restore-contract-storage.html",
+    "destination": "/docs/tools/cli/cookbook/restore-contract-storage"
+  },
+  {
+    "source": "/docs/tools/cli/cookbook/stellar-keys.html",
+    "destination": "/docs/tools/cli/cookbook/stellar-keys"
+  },
+  {
+    "source": "/docs/tools/cli/cookbook/tx-new.html",
+    "destination": "/docs/tools/cli/cookbook/tx-new"
+  },
+  {
+    "source": "/docs/tools/cli/cookbook/tx-new-create-claimable-balance.html",
+    "destination": "/docs/tools/cli/cookbook/tx-new-create-claimable-balance"
+  },
+  {
+    "source": "/docs/tools/cli/cookbook/tx-op-add.html",
+    "destination": "/docs/tools/cli/cookbook/tx-op-add"
+  },
+  {
+    "source": "/docs/tools/cli/cookbook/tx-sign.html",
+    "destination": "/docs/tools/cli/cookbook/tx-sign"
+  },
+  {
+    "source": "/docs/tools/cli/cookbook/upload-deploy.html",
+    "destination": "/docs/tools/cli/cookbook/upload-deploy"
+  },
+  {
+    "source": "/docs/tools/cli/cookbook/upload-wasm.html",
+    "destination": "/docs/tools/cli/cookbook/upload-wasm"
+  },
+  {
+    "source": "/docs/tools/cli/index.html",
+    "destination": "/docs/tools/cli/index"
+  },
+  {
+    "source": "/docs/tools/cli/install-cli.html",
+    "destination": "/docs/tools/cli/install-cli"
+  },
+  {
+    "source": "/docs/tools/cli/plugins.html",
+    "destination": "/docs/tools/cli/plugins"
+  },
+  {
+    "source": "/docs/tools/cli/plugins-list.html",
+    "destination": "/docs/tools/cli/plugins-list"
+  },
+  {
+    "source": "/docs/tools/cli/stellar-cli.html",
+    "destination": "/docs/tools/cli/stellar-cli"
+  },
+  {
+    "source": "/docs/tools/developer-tools/analytics-platforms.html",
+    "destination": "/docs/tools/developer-tools/analytics-platforms"
+  },
+  {
+    "source": "/docs/tools/developer-tools/anchor-tools.html",
+    "destination": "/docs/tools/developer-tools/anchor-tools"
+  },
+  {
+    "source": "/docs/tools/developer-tools/asset-tools.html",
+    "destination": "/docs/tools/developer-tools/asset-tools"
+  },
+  {
+    "source": "/docs/tools/developer-tools/block-explorers.html",
+    "destination": "/docs/tools/developer-tools/block-explorers"
+  },
+  {
+    "source": "/docs/tools/developer-tools/index.html",
+    "destination": "/docs/tools/developer-tools/index"
+  },
+  {
+    "source": "/docs/tools/developer-tools/jupyter-notebooks.html",
+    "destination": "/docs/tools/developer-tools/jupyter-notebooks"
+  },
+  {
+    "source": "/docs/tools/developer-tools/network-insights.html",
+    "destination": "/docs/tools/developer-tools/network-insights"
+  },
+  {
+    "source": "/docs/tools/developer-tools/network-status.html",
+    "destination": "/docs/tools/developer-tools/network-status"
+  },
+  {
+    "source": "/docs/tools/developer-tools/node-operator-tools.html",
+    "destination": "/docs/tools/developer-tools/node-operator-tools"
+  },
+  {
+    "source": "/docs/tools/developer-tools/online-ide.html",
+    "destination": "/docs/tools/developer-tools/online-ide"
+  },
+  {
+    "source": "/docs/tools/developer-tools/security-tools.html",
+    "destination": "/docs/tools/developer-tools/security-tools"
+  },
+  {
+    "source": "/docs/tools/developer-tools/wallets.html",
+    "destination": "/docs/tools/developer-tools/wallets"
+  },
+  {
+    "source": "/docs/tools/index.html",
+    "destination": "/docs/tools/index"
+  },
+  {
+    "source": "/docs/tools/infra-tools/cross-chain.html",
+    "destination": "/docs/tools/infra-tools/cross-chain"
+  },
+  {
+    "source": "/docs/tools/infra-tools/index.html",
+    "destination": "/docs/tools/infra-tools/index"
+  },
+  {
+    "source": "/docs/tools/lab/account.html",
+    "destination": "/docs/tools/lab/account"
+  },
+  {
+    "source": "/docs/tools/lab/api-explorer/horizon-endpoint.html",
+    "destination": "/docs/tools/lab/api-explorer/horizon-endpoint"
+  },
+  {
+    "source": "/docs/tools/lab/api-explorer/index.html",
+    "destination": "/docs/tools/lab/api-explorer/index"
+  },
+  {
+    "source": "/docs/tools/lab/api-explorer/rpc-methods.html",
+    "destination": "/docs/tools/lab/api-explorer/rpc-methods"
+  },
+  {
+    "source": "/docs/tools/lab/index.html",
+    "destination": "/docs/tools/lab/index"
+  },
+  {
+    "source": "/docs/tools/lab/quickstart-with-lab.html",
+    "destination": "/docs/tools/lab/quickstart-with-lab"
+  },
+  {
+    "source": "/docs/tools/lab/saved/index.html",
+    "destination": "/docs/tools/lab/saved/index"
+  },
+  {
+    "source": "/docs/tools/lab/saved/keypairs.html",
+    "destination": "/docs/tools/lab/saved/keypairs"
+  },
+  {
+    "source": "/docs/tools/lab/saved/requests.html",
+    "destination": "/docs/tools/lab/saved/requests"
+  },
+  {
+    "source": "/docs/tools/lab/saved/transactions.html",
+    "destination": "/docs/tools/lab/saved/transactions"
+  },
+  {
+    "source": "/docs/tools/lab/smart-contracts/contract-explorer.html",
+    "destination": "/docs/tools/lab/smart-contracts/contract-explorer"
+  },
+  {
+    "source": "/docs/tools/lab/smart-contracts/index.html",
+    "destination": "/docs/tools/lab/smart-contracts/index"
+  },
+  {
+    "source": "/docs/tools/lab/smart-contracts/smart-contract-list.html",
+    "destination": "/docs/tools/lab/smart-contracts/smart-contract-list"
+  },
+  {
+    "source": "/docs/tools/lab/smart-contracts/upload-deploy-contract.html",
+    "destination": "/docs/tools/lab/smart-contracts/upload-deploy-contract"
+  },
+  {
+    "source": "/docs/tools/lab/transaction-dashboard.html",
+    "destination": "/docs/tools/lab/transaction-dashboard"
+  },
+  {
+    "source": "/docs/tools/lab/transactions.html",
+    "destination": "/docs/tools/lab/transactions"
+  },
+  {
+    "source": "/docs/tools/lab/view-xdr/diff-xdr.html",
+    "destination": "/docs/tools/lab/view-xdr/diff-xdr"
+  },
+  {
+    "source": "/docs/tools/lab/view-xdr/index.html",
+    "destination": "/docs/tools/lab/view-xdr/index"
+  },
+  {
+    "source": "/docs/tools/lab/view-xdr/json-to-xdr.html",
+    "destination": "/docs/tools/lab/view-xdr/json-to-xdr"
+  },
+  {
+    "source": "/docs/tools/lab/view-xdr/xdr-to-json.html",
+    "destination": "/docs/tools/lab/view-xdr/xdr-to-json"
+  },
+  {
+    "source": "/docs/tools/openzeppelin-contracts.html",
+    "destination": "/docs/tools/openzeppelin-contracts"
+  },
+  {
+    "source": "/docs/tools/openzeppelin-relayer.html",
+    "destination": "/docs/tools/openzeppelin-relayer"
+  },
+  {
+    "source": "/docs/tools/quickstart/advanced-usage/container.html",
+    "destination": "/docs/tools/quickstart/advanced-usage/container"
+  },
+  {
+    "source": "/docs/tools/quickstart/advanced-usage/index.html",
+    "destination": "/docs/tools/quickstart/advanced-usage/index"
+  },
+  {
+    "source": "/docs/tools/quickstart/advanced-usage/operation-modes.html",
+    "destination": "/docs/tools/quickstart/advanced-usage/operation-modes"
+  },
+  {
+    "source": "/docs/tools/quickstart/advanced-usage/ports.html",
+    "destination": "/docs/tools/quickstart/advanced-usage/ports"
+  },
+  {
+    "source": "/docs/tools/quickstart/advanced-usage/run-command-examples.html",
+    "destination": "/docs/tools/quickstart/advanced-usage/run-command-examples"
+  },
+  {
+    "source": "/docs/tools/quickstart/advanced-usage/service-options.html",
+    "destination": "/docs/tools/quickstart/advanced-usage/service-options"
+  },
+  {
+    "source": "/docs/tools/quickstart/cloud/digitalocean.html",
+    "destination": "/docs/tools/quickstart/cloud/digitalocean"
+  },
+  {
+    "source": "/docs/tools/quickstart/cloud/fly.io.html",
+    "destination": "/docs/tools/quickstart/cloud/fly.io"
+  },
+  {
+    "source": "/docs/tools/quickstart/cloud/index.html",
+    "destination": "/docs/tools/quickstart/cloud/index"
+  },
+  {
+    "source": "/docs/tools/quickstart/debugging/diagnostic-events.html",
+    "destination": "/docs/tools/quickstart/debugging/diagnostic-events"
+  },
+  {
+    "source": "/docs/tools/quickstart/debugging/index.html",
+    "destination": "/docs/tools/quickstart/debugging/index"
+  },
+  {
+    "source": "/docs/tools/quickstart/debugging/viewing-logs.html",
+    "destination": "/docs/tools/quickstart/debugging/viewing-logs"
+  },
+  {
+    "source": "/docs/tools/quickstart/explorer.html",
+    "destination": "/docs/tools/quickstart/explorer"
+  },
+  {
+    "source": "/docs/tools/quickstart/faucet.html",
+    "destination": "/docs/tools/quickstart/faucet"
+  },
+  {
+    "source": "/docs/tools/quickstart/getting-started/connect-stellar-lab.html",
+    "destination": "/docs/tools/quickstart/getting-started/connect-stellar-lab"
+  },
+  {
+    "source": "/docs/tools/quickstart/getting-started/deploy-smart-contract.html",
+    "destination": "/docs/tools/quickstart/getting-started/deploy-smart-contract"
+  },
+  {
+    "source": "/docs/tools/quickstart/getting-started/index.html",
+    "destination": "/docs/tools/quickstart/getting-started/index"
+  },
+  {
+    "source": "/docs/tools/quickstart/index.html",
+    "destination": "/docs/tools/quickstart/index"
+  },
+  {
+    "source": "/docs/tools/quickstart/network-modes.html",
+    "destination": "/docs/tools/quickstart/network-modes"
+  },
+  {
+    "source": "/docs/tools/ramps/index.html",
+    "destination": "/docs/tools/ramps/index"
+  },
+  {
+    "source": "/docs/tools/ramps/moneygram.html",
+    "destination": "/docs/tools/ramps/moneygram"
+  },
+  {
+    "source": "/docs/tools/scaffold-stellar.html",
+    "destination": "/docs/tools/scaffold-stellar"
+  },
+  {
+    "source": "/docs/tools/sdks/build-your-own.html",
+    "destination": "/docs/tools/sdks/build-your-own"
+  },
+  {
+    "source": "/docs/tools/sdks/client-sdks.html",
+    "destination": "/docs/tools/sdks/client-sdks"
+  },
+  {
+    "source": "/docs/tools/sdks/contract-sdks.html",
+    "destination": "/docs/tools/sdks/contract-sdks"
+  },
+  {
+    "source": "/docs/tools/sdks/index.html",
+    "destination": "/docs/tools/sdks/index"
+  },
+  {
+    "source": "/docs/validators/admin-guide/advanced.html",
+    "destination": "/docs/validators/admin-guide/advanced"
+  },
+  {
+    "source": "/docs/validators/admin-guide/commands.html",
+    "destination": "/docs/validators/admin-guide/commands"
+  },
+  {
+    "source": "/docs/validators/admin-guide/configuring.html",
+    "destination": "/docs/validators/admin-guide/configuring"
+  },
+  {
+    "source": "/docs/validators/admin-guide/environment-preparation.html",
+    "destination": "/docs/validators/admin-guide/environment-preparation"
+  },
+  {
+    "source": "/docs/validators/admin-guide/index.html",
+    "destination": "/docs/validators/admin-guide/index"
+  },
+  {
+    "source": "/docs/validators/admin-guide/installation.html",
+    "destination": "/docs/validators/admin-guide/installation"
+  },
+  {
+    "source": "/docs/validators/admin-guide/logging.html",
+    "destination": "/docs/validators/admin-guide/logging"
+  },
+  {
+    "source": "/docs/validators/admin-guide/maintenance.html",
+    "destination": "/docs/validators/admin-guide/maintenance"
+  },
+  {
+    "source": "/docs/validators/admin-guide/monitoring.html",
+    "destination": "/docs/validators/admin-guide/monitoring"
+  },
+  {
+    "source": "/docs/validators/admin-guide/network-upgrades.html",
+    "destination": "/docs/validators/admin-guide/network-upgrades"
+  },
+  {
+    "source": "/docs/validators/admin-guide/prerequisites.html",
+    "destination": "/docs/validators/admin-guide/prerequisites"
+  },
+  {
+    "source": "/docs/validators/admin-guide/publishing-history-archives.html",
+    "destination": "/docs/validators/admin-guide/publishing-history-archives"
+  },
+  {
+    "source": "/docs/validators/admin-guide/running-node.html",
+    "destination": "/docs/validators/admin-guide/running-node"
+  },
+  {
+    "source": "/docs/validators/admin-guide/soroban-settings.html",
+    "destination": "/docs/validators/admin-guide/soroban-settings"
+  },
+  {
+    "source": "/docs/validators/index.html",
+    "destination": "/docs/validators/index"
+  },
+  {
+    "source": "/docs/validators/tier-1-orgs.html",
+    "destination": "/docs/validators/tier-1-orgs"
+  },
+  {
+    "source": "/index.html",
+    "destination": "/index"
+  },
+  {
+    "source": "/meetings/2024/01/18.html",
+    "destination": "/meetings/2024/01/18"
+  },
+  {
+    "source": "/meetings/2024/01/26.html",
+    "destination": "/meetings/2024/01/26"
+  },
+  {
+    "source": "/meetings/2024/02/01.html",
+    "destination": "/meetings/2024/02/01"
+  },
+  {
+    "source": "/meetings/2024/02/08.html",
+    "destination": "/meetings/2024/02/08"
+  },
+  {
+    "source": "/meetings/2024/02/15.html",
+    "destination": "/meetings/2024/02/15"
+  },
+  {
+    "source": "/meetings/2024/02/22.html",
+    "destination": "/meetings/2024/02/22"
+  },
+  {
+    "source": "/meetings/2024/02/29.html",
+    "destination": "/meetings/2024/02/29"
+  },
+  {
+    "source": "/meetings/2024/03/07.html",
+    "destination": "/meetings/2024/03/07"
+  },
+  {
+    "source": "/meetings/2024/03/14.html",
+    "destination": "/meetings/2024/03/14"
+  },
+  {
+    "source": "/meetings/2024/03/21.html",
+    "destination": "/meetings/2024/03/21"
+  },
+  {
+    "source": "/meetings/2024/03/28.html",
+    "destination": "/meetings/2024/03/28"
+  },
+  {
+    "source": "/meetings/2024/04/04.html",
+    "destination": "/meetings/2024/04/04"
+  },
+  {
+    "source": "/meetings/2024/04/11.html",
+    "destination": "/meetings/2024/04/11"
+  },
+  {
+    "source": "/meetings/2024/04/18.html",
+    "destination": "/meetings/2024/04/18"
+  },
+  {
+    "source": "/meetings/2024/04/25.html",
+    "destination": "/meetings/2024/04/25"
+  },
+  {
+    "source": "/meetings/2024/05/02.html",
+    "destination": "/meetings/2024/05/02"
+  },
+  {
+    "source": "/meetings/2024/05/09.html",
+    "destination": "/meetings/2024/05/09"
+  },
+  {
+    "source": "/meetings/2024/06/13.html",
+    "destination": "/meetings/2024/06/13"
+  },
+  {
+    "source": "/meetings/2024/06/20.html",
+    "destination": "/meetings/2024/06/20"
+  },
+  {
+    "source": "/meetings/2024/06/27.html",
+    "destination": "/meetings/2024/06/27"
+  },
+  {
+    "source": "/meetings/2024/07/11.html",
+    "destination": "/meetings/2024/07/11"
+  },
+  {
+    "source": "/meetings/2024/07/18.html",
+    "destination": "/meetings/2024/07/18"
+  },
+  {
+    "source": "/meetings/2024/07/25.html",
+    "destination": "/meetings/2024/07/25"
+  },
+  {
+    "source": "/meetings/2024/08/01.html",
+    "destination": "/meetings/2024/08/01"
+  },
+  {
+    "source": "/meetings/2024/08/08.html",
+    "destination": "/meetings/2024/08/08"
+  },
+  {
+    "source": "/meetings/2024/08/15.html",
+    "destination": "/meetings/2024/08/15"
+  },
+  {
+    "source": "/meetings/2024/08/22.html",
+    "destination": "/meetings/2024/08/22"
+  },
+  {
+    "source": "/meetings/2024/08/29.html",
+    "destination": "/meetings/2024/08/29"
+  },
+  {
+    "source": "/meetings/2024/09/05.html",
+    "destination": "/meetings/2024/09/05"
+  },
+  {
+    "source": "/meetings/2024/09/12.html",
+    "destination": "/meetings/2024/09/12"
+  },
+  {
+    "source": "/meetings/2024/09/19.html",
+    "destination": "/meetings/2024/09/19"
+  },
+  {
+    "source": "/meetings/2024/09/26.html",
+    "destination": "/meetings/2024/09/26"
+  },
+  {
+    "source": "/meetings/2024/10/24.html",
+    "destination": "/meetings/2024/10/24"
+  },
+  {
+    "source": "/meetings/2024/11/14.html",
+    "destination": "/meetings/2024/11/14"
+  },
+  {
+    "source": "/meetings/2024/12/05.html",
+    "destination": "/meetings/2024/12/05"
+  },
+  {
+    "source": "/meetings/2024/12/12.html",
+    "destination": "/meetings/2024/12/12"
+  },
+  {
+    "source": "/meetings/2024/12/19.html",
+    "destination": "/meetings/2024/12/19"
+  },
+  {
+    "source": "/meetings/2025/01/16.html",
+    "destination": "/meetings/2025/01/16"
+  },
+  {
+    "source": "/meetings/2025/01/23.html",
+    "destination": "/meetings/2025/01/23"
+  },
+  {
+    "source": "/meetings/2025/01/30.html",
+    "destination": "/meetings/2025/01/30"
+  },
+  {
+    "source": "/meetings/2025/02/06.html",
+    "destination": "/meetings/2025/02/06"
+  },
+  {
+    "source": "/meetings/2025/02/13.html",
+    "destination": "/meetings/2025/02/13"
+  },
+  {
+    "source": "/meetings/2025/02/20.html",
+    "destination": "/meetings/2025/02/20"
+  },
+  {
+    "source": "/meetings/2025/02/27.html",
+    "destination": "/meetings/2025/02/27"
+  },
+  {
+    "source": "/meetings/2025/03/06.html",
+    "destination": "/meetings/2025/03/06"
+  },
+  {
+    "source": "/meetings/2025/03/27.html",
+    "destination": "/meetings/2025/03/27"
+  },
+  {
+    "source": "/meetings/2025/04/03.html",
+    "destination": "/meetings/2025/04/03"
+  },
+  {
+    "source": "/meetings/2025/04/10.html",
+    "destination": "/meetings/2025/04/10"
+  },
+  {
+    "source": "/meetings/2025/04/17.html",
+    "destination": "/meetings/2025/04/17"
+  },
+  {
+    "source": "/meetings/2025/05/01.html",
+    "destination": "/meetings/2025/05/01"
+  },
+  {
+    "source": "/meetings/2025/05/22.html",
+    "destination": "/meetings/2025/05/22"
+  },
+  {
+    "source": "/meetings/2025/07/10.html",
+    "destination": "/meetings/2025/07/10"
+  },
+  {
+    "source": "/meetings/2025/07/17.html",
+    "destination": "/meetings/2025/07/17"
+  },
+  {
+    "source": "/meetings/2025/07/24.html",
+    "destination": "/meetings/2025/07/24"
+  },
+  {
+    "source": "/meetings/2025/08/07.html",
+    "destination": "/meetings/2025/08/07"
+  },
+  {
+    "source": "/meetings/2025/09/25.html",
+    "destination": "/meetings/2025/09/25"
+  },
+  {
+    "source": "/meetings/2025/10/02.html",
+    "destination": "/meetings/2025/10/02"
+  },
+  {
+    "source": "/meetings/2025/10/09.html",
+    "destination": "/meetings/2025/10/09"
+  },
+  {
+    "source": "/meetings/2025/10/16.html",
+    "destination": "/meetings/2025/10/16"
+  },
+  {
+    "source": "/meetings/2025/10/23.html",
+    "destination": "/meetings/2025/10/23"
+  },
+  {
+    "source": "/meetings/2025/10/30.html",
+    "destination": "/meetings/2025/10/30"
+  },
+  {
+    "source": "/meetings/2025/11/06.html",
+    "destination": "/meetings/2025/11/06"
+  },
+  {
+    "source": "/meetings/2026/01/22.html",
+    "destination": "/meetings/2026/01/22"
+  },
+  {
+    "source": "/meetings/2026/01/29.html",
+    "destination": "/meetings/2026/01/29"
+  },
+  {
+    "source": "/meetings/2026/02/26.html",
+    "destination": "/meetings/2026/02/26"
+  },
+  {
+    "source": "/meetings/2026/04/16.html",
+    "destination": "/meetings/2026/04/16"
+  },
+  {
+    "source": "/meetings/2026/04/23.html",
+    "destination": "/meetings/2026/04/23"
+  },
+  {
+    "source": "/meetings/2026/04/30.html",
+    "destination": "/meetings/2026/04/30"
+  },
+  {
+    "source": "/meetings/2026/05/07.html",
+    "destination": "/meetings/2026/05/07"
+  },
+  {
+    "source": "/meetings/2026/05/14.html",
+    "destination": "/meetings/2026/05/14"
+  },
+  {
+    "source": "/meetings/2026/05/21.html",
+    "destination": "/meetings/2026/05/21"
+  },
+  {
+    "source": "/meetings/2026/06/11.html",
+    "destination": "/meetings/2026/06/11"
+  },
+  {
+    "source": "/meetings/2026/06/18.html",
+    "destination": "/meetings/2026/06/18"
+  },
+  {
+    "source": "/meetings/2026/06/25.html",
+    "destination": "/meetings/2026/06/25"
+  },
+  {
+    "source": "/meetings/2026/07/02.html",
+    "destination": "/meetings/2026/07/02"
+  },
+  {
+    "source": "/meetings/2026/07/16.html",
+    "destination": "/meetings/2026/07/16"
+  },
+  {
+    "source": "/meetings/2026/07/23.html",
+    "destination": "/meetings/2026/07/23"
+  },
+  {
+    "source": "/meetings/2026/07/30.html",
+    "destination": "/meetings/2026/07/30"
+  },
+  {
+    "source": "/meetings/2026/08/06.html",
+    "destination": "/meetings/2026/08/06"
+  },
+  {
+    "source": "/meetings/2026/08/13.html",
+    "destination": "/meetings/2026/08/13"
+  },
+  {
+    "source": "/meetings/index.html",
+    "destination": "/meetings/index"
+  }
+]
diff --git a/routes.txt b/routes.txt
deleted file mode 100644
index f03d7f79d..000000000
--- a/routes.txt
+++ /dev/null
@@ -1,1001 +0,0 @@
-/
-/404.html
-/docs
-/docs/build
-/docs/build/agentic-payments
-/docs/build/agentic-payments/mpp
-/docs/build/agentic-payments/mpp/channel-guide
-/docs/build/agentic-payments/mpp/charge-guide
-/docs/build/agentic-payments/x402
-/docs/build/agentic-payments/x402/built-on-stellar
-/docs/build/agentic-payments/x402/quickstart-guide
-/docs/build/apps
-/docs/build/apps/application-design-considerations
-/docs/build/apps/dapp-frontend
-/docs/build/apps/example-application-tutorial
-/docs/build/apps/example-application-tutorial/account-creation
-/docs/build/apps/example-application-tutorial/anchor-integration
-/docs/build/apps/example-application-tutorial/anchor-integration/sep1
-/docs/build/apps/example-application-tutorial/anchor-integration/sep10
-/docs/build/apps/example-application-tutorial/anchor-integration/sep24
-/docs/build/apps/example-application-tutorial/anchor-integration/sep6
-/docs/build/apps/example-application-tutorial/anchor-integration/setup
-/docs/build/apps/example-application-tutorial/confirmation-modal
-/docs/build/apps/example-application-tutorial/contacts-list
-/docs/build/apps/example-application-tutorial/manage-trust
-/docs/build/apps/example-application-tutorial/overview
-/docs/build/apps/example-application-tutorial/path-payment
-/docs/build/apps/example-application-tutorial/payment
-/docs/build/apps/example-application-tutorial/querying-data
-/docs/build/apps/guestbook
-/docs/build/apps/guestbook/bindings
-/docs/build/apps/guestbook/frontend
-/docs/build/apps/guestbook/overview
-/docs/build/apps/guestbook/passkeys-prerequisites
-/docs/build/apps/guestbook/setup-passkeys
-/docs/build/apps/guestbook/smart-contract
-/docs/build/apps/ingest-sdk
-/docs/build/apps/ingest-sdk/ingestion-pipeline-code
-/docs/build/apps/ingest-sdk/overview
-/docs/build/apps/overview
-/docs/build/apps/privacy
-/docs/build/apps/swift-payment-app
-/docs/build/apps/wallet
-/docs/build/apps/wallet/intro
-/docs/build/apps/wallet/overview
-/docs/build/apps/wallet/sep10
-/docs/build/apps/wallet/sep24
-/docs/build/apps/wallet/sep30
-/docs/build/apps/wallet/sep38
-/docs/build/apps/wallet/sep6
-/docs/build/apps/wallet/sep7
-/docs/build/apps/wallet/stellar
-/docs/build/apps/zk
-/docs/build/building-with-ai
-/docs/build/guides
-/docs/build/guides/archival
-/docs/build/guides/archival/create-restoration-footprint-js
-/docs/build/guides/archival/extend-persistent-entry-js
-/docs/build/guides/archival/restore-contract-js
-/docs/build/guides/archival/restore-data-js
-/docs/build/guides/archival/test-ttl-extension
-/docs/build/guides/auth
-/docs/build/guides/auth/check-auth-tutorials
-/docs/build/guides/auth/contract-authorization
-/docs/build/guides/basics
-/docs/build/guides/basics/automate-reset-data
-/docs/build/guides/basics/classic-transition
-/docs/build/guides/basics/verify-trustlines
-/docs/build/guides/contract-accounts
-/docs/build/guides/contract-accounts/advanced-patterns
-/docs/build/guides/contract-accounts/examples
-/docs/build/guides/contract-accounts/smart-wallets
-/docs/build/guides/conventions
-/docs/build/guides/conventions/cross-contract
-/docs/build/guides/conventions/deploy-contract
-/docs/build/guides/conventions/deploy-sac-with-code
-/docs/build/guides/conventions/error-enum
-/docs/build/guides/conventions/extending-wasm-ttl
-/docs/build/guides/conventions/upgrading-contracts
-/docs/build/guides/conventions/wasm-metadata
-/docs/build/guides/conventions/workspace
-/docs/build/guides/conversions
-/docs/build/guides/conversions/address-conversions
-/docs/build/guides/conversions/bytes-conversions
-/docs/build/guides/conversions/scval-conversions
-/docs/build/guides/conversions/string-conversions
-/docs/build/guides/dapps
-/docs/build/guides/dapps/frontend-guide
-/docs/build/guides/dapps/initialization
-/docs/build/guides/dapps/soroban-contract-init-template
-/docs/build/guides/dapps/state-archival
-/docs/build/guides/dapps/working-with-contract-specs
-/docs/build/guides/events
-/docs/build/guides/events/consume
-/docs/build/guides/events/ingest
-/docs/build/guides/events/publish
-/docs/build/guides/events/replay-ledger-close-meta
-/docs/build/guides/fees
-/docs/build/guides/fees/analyzing-smart-contract-cost
-/docs/build/guides/freighter
-/docs/build/guides/freighter/connect-testnet
-/docs/build/guides/freighter/enable-soroban-tokens
-/docs/build/guides/freighter/integrate-freighter-react
-/docs/build/guides/freighter/prompt-to-sign-tx
-/docs/build/guides/freighter/send-token-payments
-/docs/build/guides/freighter/sign-auth-entries
-/docs/build/guides/freighter/sign-soroban-xdrs
-/docs/build/guides/rpc
-/docs/build/guides/rpc/generate-ledger-keys-python
-/docs/build/guides/rpc/retrieve-contract-code-js
-/docs/build/guides/rpc/retrieve-contract-code-python
-/docs/build/guides/storage
-/docs/build/guides/storage/choosing-the-right-storage
-/docs/build/guides/storage/migrate-contract-storage
-/docs/build/guides/storage/storage-strategies
-/docs/build/guides/storage/use-instance
-/docs/build/guides/storage/use-persistent
-/docs/build/guides/storage/use-temporary
-/docs/build/guides/testing
-/docs/build/guides/testing/code-coverage
-/docs/build/guides/testing/differential-tests
-/docs/build/guides/testing/differential-tests-with-test-snapshots
-/docs/build/guides/testing/fork-testing
-/docs/build/guides/testing/fuzzing
-/docs/build/guides/testing/integration-tests
-/docs/build/guides/testing/ledger-snapshot-testing
-/docs/build/guides/testing/mocking
-/docs/build/guides/testing/mutation-testing
-/docs/build/guides/testing/test-contract-auth
-/docs/build/guides/testing/test-contract-events
-/docs/build/guides/testing/unit-tests
-/docs/build/guides/tokens
-/docs/build/guides/tokens/custom-sac-admin
-/docs/build/guides/tokens/deploying-a-sac
-/docs/build/guides/tokens/stellar-asset-contract
-/docs/build/guides/transactions
-/docs/build/guides/transactions/channel-accounts
-/docs/build/guides/transactions/claimable-balances
-/docs/build/guides/transactions/clawbacks
-/docs/build/guides/transactions/create-account
-/docs/build/guides/transactions/fee-bump-transactions
-/docs/build/guides/transactions/fee-sponsorship
-/docs/build/guides/transactions/install-deploy-contract-with-code
-/docs/build/guides/transactions/invoke-contract-tx-sdk
-/docs/build/guides/transactions/path-payments
-/docs/build/guides/transactions/pooled-accounts-muxed-accounts-memos
-/docs/build/guides/transactions/send-and-receive-c-accounts
-/docs/build/guides/transactions/send-and-receive-payments
-/docs/build/guides/transactions/signing-soroban-invocations
-/docs/build/guides/transactions/simulateTransaction-Deep-Dive
-/docs/build/guides/transactions/sponsored-reserves
-/docs/build/guides/transactions/submit-transaction-wait-js
-/docs/build/guides/transactions/upload-wasm-bytecode
-/docs/build/security-docs
-/docs/build/security-docs/monitoring
-/docs/build/security-docs/monitoring/monitoring-template-builders
-/docs/build/security-docs/monitoring/monitoring-template-users
-/docs/build/security-docs/securing-web-based-projects
-/docs/build/security-docs/threat-modeling
-/docs/build/security-docs/threat-modeling/STRIDE-template
-/docs/build/security-docs/threat-modeling/pizza-restaurant-example
-/docs/build/security-docs/threat-modeling/threat-modeling-description
-/docs/build/security-docs/threat-modeling/threat-modeling-how-to
-/docs/build/smart-contracts
-/docs/build/smart-contracts/example-contracts
-/docs/build/smart-contracts/example-contracts/alloc
-/docs/build/smart-contracts/example-contracts/atomic-multi-swap
-/docs/build/smart-contracts/example-contracts/atomic-swap
-/docs/build/smart-contracts/example-contracts/auth
-/docs/build/smart-contracts/example-contracts/bls-signature
-/docs/build/smart-contracts/example-contracts/complex-account
-/docs/build/smart-contracts/example-contracts/cross-contract-call
-/docs/build/smart-contracts/example-contracts/custom-types
-/docs/build/smart-contracts/example-contracts/delegate-auth
-/docs/build/smart-contracts/example-contracts/deployer
-/docs/build/smart-contracts/example-contracts/errors
-/docs/build/smart-contracts/example-contracts/events
-/docs/build/smart-contracts/example-contracts/fuzzing
-/docs/build/smart-contracts/example-contracts/liquidity-pool
-/docs/build/smart-contracts/example-contracts/logging
-/docs/build/smart-contracts/example-contracts/mint-lock
-/docs/build/smart-contracts/example-contracts/simple-account
-/docs/build/smart-contracts/example-contracts/single-offer-sale
-/docs/build/smart-contracts/example-contracts/storage
-/docs/build/smart-contracts/example-contracts/timelock
-/docs/build/smart-contracts/example-contracts/tokens
-/docs/build/smart-contracts/example-contracts/upgradeable-contract
-/docs/build/smart-contracts/example-contracts/workspace
-/docs/build/smart-contracts/getting-started
-/docs/build/smart-contracts/getting-started/deploy-increment-contract
-/docs/build/smart-contracts/getting-started/deploy-to-testnet
-/docs/build/smart-contracts/getting-started/hello-world
-/docs/build/smart-contracts/getting-started/hello-world-frontend
-/docs/build/smart-contracts/getting-started/setup
-/docs/build/smart-contracts/getting-started/storing-data
-/docs/build/smart-contracts/overview
-/docs/data
-/docs/data/analytics
-/docs/data/analytics/analytics-providers
-/docs/data/analytics/hubble
-/docs/data/analytics/hubble/analyst-guide
-/docs/data/analytics/hubble/analyst-guide/connecting
-/docs/data/analytics/hubble/analyst-guide/creating-visualizations
-/docs/data/analytics/hubble/analyst-guide/history-vs-state-tables
-/docs/data/analytics/hubble/analyst-guide/optimizing-queries
-/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data
-/docs/data/analytics/hubble/analyst-guide/viewing-metadata
-/docs/data/analytics/hubble/data-catalog
-/docs/data/analytics/hubble/data-catalog/data-dictionary
-/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze
-/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/account-signers
-/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/accounts
-/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/claimable-balances
-/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/config-settings
-/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-code
-/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-data
-/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/evicted-keys
-/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-assets
-/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-contract-events
-/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-effects
-/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-ledgers
-/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-operations
-/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-trades
-/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-transactions
-/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/liquidity-pools
-/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/offers
-/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/restored-key
-/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/trustlines
-/docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/ttl
-/docs/data/analytics/hubble/data-catalog/data-dictionary/gold
-/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/account-balances-daily-agg
-/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/asset-balances-daily-agg
-/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/daily-fee-stats-agg
-/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/hourly-fee-agg-account
-/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/hourly-soroban-fee-agg-contract
-/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/ledger-fee-stats-agg
-/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/soroban-core-metrics
-/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/trade-agg
-/docs/data/analytics/hubble/data-catalog/data-dictionary/gold/tvl-agg
-/docs/data/analytics/hubble/data-catalog/data-dictionary/silver
-/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/account-signers-current
-/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-current
-/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-snapshot
-/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/claimable-balances-current
-/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/config-settings-current
-/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/config-settings-snapshot
-/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-code-current
-/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-current
-/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-snapshot
-/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations
-/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations-soroban
-/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/evicted-keys-snapshot
-/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-current
-/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-snapshot
-/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/offers-current
-/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-cex-snapshot
-/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-fex-snapshot
-/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/reflector-prices-data-sdex-snapshot
-/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/token-transfers-raw
-/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-current
-/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-snapshot
-/docs/data/analytics/hubble/data-catalog/data-dictionary/silver/ttl-current
-/docs/data/analytics/hubble/data-catalog/data-lineage
-/docs/data/analytics/hubble/data-catalog/data-model-diagram
-/docs/data/analytics/hubble/developer-guide
-/docs/data/analytics/hubble/developer-guide/backfill
-/docs/data/analytics/hubble/developer-guide/backfill/JS-UDF
-/docs/data/analytics/hubble/developer-guide/backfill/data-import
-/docs/data/analytics/hubble/developer-guide/connecting-to-bigquery
-/docs/data/analytics/hubble/developer-guide/data-curation
-/docs/data/analytics/hubble/developer-guide/data-curation/architecture
-/docs/data/analytics/hubble/developer-guide/data-curation/getting-started
-/docs/data/analytics/hubble/developer-guide/data-curation/overview
-/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration
-/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/architecture
-/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/getting-started
-/docs/data/analytics/hubble/developer-guide/scheduling-and-orchestration/overview
-/docs/data/analytics/hubble/developer-guide/source-system-ingestion
-/docs/data/analytics/hubble/developer-guide/source-system-ingestion/architecture
-/docs/data/analytics/hubble/developer-guide/source-system-ingestion/getting-started
-/docs/data/analytics/hubble/developer-guide/source-system-ingestion/overview
-/docs/data/analytics/hubble/developer-guide/visualization
-/docs/data/analytics/hubble/developer-guide/visualization/getting-started
-/docs/data/analytics/hubble/developer-guide/visualization/overview
-/docs/data/analytics/public-dashboards
-/docs/data/apis
-/docs/data/apis/horizon
-/docs/data/apis/horizon/admin-guide
-/docs/data/apis/horizon/admin-guide/configuring
-/docs/data/apis/horizon/admin-guide/ingestion
-/docs/data/apis/horizon/admin-guide/ingestion-filtering
-/docs/data/apis/horizon/admin-guide/installing
-/docs/data/apis/horizon/admin-guide/monitoring
-/docs/data/apis/horizon/admin-guide/overview
-/docs/data/apis/horizon/admin-guide/prerequisites
-/docs/data/apis/horizon/admin-guide/running
-/docs/data/apis/horizon/admin-guide/scaling
-/docs/data/apis/horizon/admin-guide/upgrading
-/docs/data/apis/horizon/api-reference
-/docs/data/apis/horizon/api-reference/aggregations
-/docs/data/apis/horizon/api-reference/aggregations/fee-stats
-/docs/data/apis/horizon/api-reference/aggregations/fee-stats/object
-/docs/data/apis/horizon/api-reference/aggregations/order-books
-/docs/data/apis/horizon/api-reference/aggregations/order-books/object
-/docs/data/apis/horizon/api-reference/aggregations/paths
-/docs/data/apis/horizon/api-reference/aggregations/paths/object
-/docs/data/apis/horizon/api-reference/aggregations/trade-aggregations
-/docs/data/apis/horizon/api-reference/aggregations/trade-aggregations/object
-/docs/data/apis/horizon/api-reference/cb-retrieve-related-operations
-/docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions
-/docs/data/apis/horizon/api-reference/errors
-/docs/data/apis/horizon/api-reference/errors/error-handling
-/docs/data/apis/horizon/api-reference/errors/http-status-codes
-/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific
-/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/before-history
-/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/stale-history
-/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/timeout
-/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-failed
-/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-malformed
-/docs/data/apis/horizon/api-reference/errors/http-status-codes/standard
-/docs/data/apis/horizon/api-reference/errors/response
-/docs/data/apis/horizon/api-reference/errors/result-codes
-/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific
-/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/account-merge
-/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/allow-trust
-/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/bump-sequence
-/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/change-trust
-/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-account
-/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-passive-sell-offer
-/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-buy-offer
-/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-data
-/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-sell-offer
-/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-receive
-/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-send
-/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/payment
-/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/set-options
-/docs/data/apis/horizon/api-reference/errors/result-codes/operations
-/docs/data/apis/horizon/api-reference/errors/result-codes/transactions
-/docs/data/apis/horizon/api-reference/get-all-offers
-/docs/data/apis/horizon/api-reference/get-all-trades
-/docs/data/apis/horizon/api-reference/get-data-by-account-id
-/docs/data/apis/horizon/api-reference/get-effects-by-account-id
-/docs/data/apis/horizon/api-reference/get-offer-by-offer-id
-/docs/data/apis/horizon/api-reference/get-offers-by-account-id
-/docs/data/apis/horizon/api-reference/get-operations-by-account-id
-/docs/data/apis/horizon/api-reference/get-payments-by-account-id
-/docs/data/apis/horizon/api-reference/get-trades-by-account-id
-/docs/data/apis/horizon/api-reference/get-trades-by-offer-id
-/docs/data/apis/horizon/api-reference/get-transactions-by-account-id
-/docs/data/apis/horizon/api-reference/list-all-accounts
-/docs/data/apis/horizon/api-reference/list-all-assets
-/docs/data/apis/horizon/api-reference/list-all-claimable-balances
-/docs/data/apis/horizon/api-reference/list-all-effects
-/docs/data/apis/horizon/api-reference/list-all-ledgers
-/docs/data/apis/horizon/api-reference/list-all-operations
-/docs/data/apis/horizon/api-reference/list-all-payments
-/docs/data/apis/horizon/api-reference/list-all-transactions
-/docs/data/apis/horizon/api-reference/list-liquidity-pools
-/docs/data/apis/horizon/api-reference/list-strict-receive-payment-paths
-/docs/data/apis/horizon/api-reference/list-strict-send-payment-paths
-/docs/data/apis/horizon/api-reference/list-trade-aggregations
-/docs/data/apis/horizon/api-reference/lp-retrieve-related-operations
-/docs/data/apis/horizon/api-reference/lp-retrieve-related-transactions
-/docs/data/apis/horizon/api-reference/resources
-/docs/data/apis/horizon/api-reference/resources/accounts
-/docs/data/apis/horizon/api-reference/resources/accounts/object
-/docs/data/apis/horizon/api-reference/resources/assets
-/docs/data/apis/horizon/api-reference/resources/assets/object
-/docs/data/apis/horizon/api-reference/resources/claimablebalances
-/docs/data/apis/horizon/api-reference/resources/claimablebalances/object
-/docs/data/apis/horizon/api-reference/resources/effects
-/docs/data/apis/horizon/api-reference/resources/effects/types
-/docs/data/apis/horizon/api-reference/resources/ledgers
-/docs/data/apis/horizon/api-reference/resources/ledgers/object
-/docs/data/apis/horizon/api-reference/resources/liquiditypools
-/docs/data/apis/horizon/api-reference/resources/offers
-/docs/data/apis/horizon/api-reference/resources/offers/object
-/docs/data/apis/horizon/api-reference/resources/operations
-/docs/data/apis/horizon/api-reference/resources/operations/object
-/docs/data/apis/horizon/api-reference/resources/operations/object/account-merge
-/docs/data/apis/horizon/api-reference/resources/operations/object/allow-trust
-/docs/data/apis/horizon/api-reference/resources/operations/object/begin-sponsoring-future-reserves
-/docs/data/apis/horizon/api-reference/resources/operations/object/bump-sequence
-/docs/data/apis/horizon/api-reference/resources/operations/object/buy-offer
-/docs/data/apis/horizon/api-reference/resources/operations/object/change-trust
-/docs/data/apis/horizon/api-reference/resources/operations/object/claim-claimable-balance
-/docs/data/apis/horizon/api-reference/resources/operations/object/create-account
-/docs/data/apis/horizon/api-reference/resources/operations/object/create-claimable-balance
-/docs/data/apis/horizon/api-reference/resources/operations/object/end-sponsoring-future-reserves
-/docs/data/apis/horizon/api-reference/resources/operations/object/extend-footprint-ttl
-/docs/data/apis/horizon/api-reference/resources/operations/object/invoke-host-function
-/docs/data/apis/horizon/api-reference/resources/operations/object/liquidity-pool-deposit
-/docs/data/apis/horizon/api-reference/resources/operations/object/liquidity-pool-withdraw
-/docs/data/apis/horizon/api-reference/resources/operations/object/manage-data
-/docs/data/apis/horizon/api-reference/resources/operations/object/passive-sell-offer
-/docs/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-receive
-/docs/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-send
-/docs/data/apis/horizon/api-reference/resources/operations/object/restore-footprint
-/docs/data/apis/horizon/api-reference/resources/operations/object/revoke-sponsorship
-/docs/data/apis/horizon/api-reference/resources/operations/object/sell-offer
-/docs/data/apis/horizon/api-reference/resources/operations/object/set-options
-/docs/data/apis/horizon/api-reference/resources/payments
-/docs/data/apis/horizon/api-reference/resources/payments/object
-/docs/data/apis/horizon/api-reference/resources/trades
-/docs/data/apis/horizon/api-reference/resources/trades/object
-/docs/data/apis/horizon/api-reference/resources/transactions
-/docs/data/apis/horizon/api-reference/resources/transactions/object
-/docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance
-/docs/data/apis/horizon/api-reference/retrieve-a-ledger
-/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects
-/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations
-/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments
-/docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions
-/docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool
-/docs/data/apis/horizon/api-reference/retrieve-a-transaction
-/docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects
-/docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations
-/docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments
-/docs/data/apis/horizon/api-reference/retrieve-an-account
-/docs/data/apis/horizon/api-reference/retrieve-an-operation
-/docs/data/apis/horizon/api-reference/retrieve-an-operations-effects
-/docs/data/apis/horizon/api-reference/retrieve-an-order-book
-/docs/data/apis/horizon/api-reference/retrieve-fee-stats
-/docs/data/apis/horizon/api-reference/retrieve-related-effects
-/docs/data/apis/horizon/api-reference/retrieve-related-trades
-/docs/data/apis/horizon/api-reference/structure
-/docs/data/apis/horizon/api-reference/structure/consistency
-/docs/data/apis/horizon/api-reference/structure/pagination
-/docs/data/apis/horizon/api-reference/structure/pagination/page-arguments
-/docs/data/apis/horizon/api-reference/structure/rate-limiting
-/docs/data/apis/horizon/api-reference/structure/response-format
-/docs/data/apis/horizon/api-reference/structure/streaming
-/docs/data/apis/horizon/api-reference/structure/xdr
-/docs/data/apis/horizon/api-reference/submit-a-transaction
-/docs/data/apis/horizon/api-reference/submit-async-transaction
-/docs/data/apis/horizon/providers
-/docs/data/apis/migrate-from-horizon-to-rpc
-/docs/data/apis/rpc
-/docs/data/apis/rpc/admin-guide
-/docs/data/apis/rpc/admin-guide/configuring
-/docs/data/apis/rpc/admin-guide/data-lake-integration
-/docs/data/apis/rpc/admin-guide/development
-/docs/data/apis/rpc/admin-guide/installing
-/docs/data/apis/rpc/admin-guide/monitoring
-/docs/data/apis/rpc/admin-guide/prerequisites
-/docs/data/apis/rpc/admin-guide/running
-/docs/data/apis/rpc/api-reference
-/docs/data/apis/rpc/api-reference/methods
-/docs/data/apis/rpc/api-reference/methods/getEvents
-/docs/data/apis/rpc/api-reference/methods/getFeeStats
-/docs/data/apis/rpc/api-reference/methods/getHealth
-/docs/data/apis/rpc/api-reference/methods/getLatestLedger
-/docs/data/apis/rpc/api-reference/methods/getLedgerEntries
-/docs/data/apis/rpc/api-reference/methods/getLedgers
-/docs/data/apis/rpc/api-reference/methods/getNetwork
-/docs/data/apis/rpc/api-reference/methods/getTransaction
-/docs/data/apis/rpc/api-reference/methods/getTransactions
-/docs/data/apis/rpc/api-reference/methods/getVersionInfo
-/docs/data/apis/rpc/api-reference/methods/queryEvents
-/docs/data/apis/rpc/api-reference/methods/sendTransaction
-/docs/data/apis/rpc/api-reference/methods/simulateTransaction
-/docs/data/apis/rpc/api-reference/structure
-/docs/data/apis/rpc/api-reference/structure/data-format
-/docs/data/apis/rpc/api-reference/structure/json-rpc
-/docs/data/apis/rpc/api-reference/structure/pagination
-/docs/data/apis/rpc/providers
-/docs/data/indexers
-/docs/data/indexers/build-your-own
-/docs/data/indexers/build-your-own/galexie
-/docs/data/indexers/build-your-own/galexie/admin_guide
-/docs/data/indexers/build-your-own/galexie/admin_guide/configuring
-/docs/data/indexers/build-your-own/galexie/admin_guide/full-history-exporting
-/docs/data/indexers/build-your-own/galexie/admin_guide/installing
-/docs/data/indexers/build-your-own/galexie/admin_guide/monitoring
-/docs/data/indexers/build-your-own/galexie/admin_guide/prerequisites
-/docs/data/indexers/build-your-own/galexie/admin_guide/running
-/docs/data/indexers/build-your-own/galexie/admin_guide/setup
-/docs/data/indexers/build-your-own/galexie/data-lake-format
-/docs/data/indexers/build-your-own/galexie/examples
-/docs/data/indexers/build-your-own/galexie/examples/gcs-export
-/docs/data/indexers/build-your-own/galexie/providers
-/docs/data/indexers/build-your-own/ingest-sdk
-/docs/data/indexers/build-your-own/ingest-sdk/developer_guide
-/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/architecture
-/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends
-/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/bufferedstoragebackend
-/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/captivecore
-/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/rpcledgerbackend
-/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerreaders
-/docs/data/indexers/build-your-own/ingest-sdk/developer_guide/prerequisites
-/docs/data/indexers/build-your-own/ingest-sdk/examples
-/docs/data/indexers/build-your-own/ingest-sdk/examples/changes
-/docs/data/indexers/build-your-own/ingest-sdk/examples/ledger_entry_statistics
-/docs/data/indexers/build-your-own/ingest-sdk/examples/transaction_statistics
-/docs/data/indexers/build-your-own/processors
-/docs/data/indexers/build-your-own/processors/token-transfer-processor
-/docs/data/indexers/build-your-own/processors/token-transfer-processor/examples
-/docs/data/indexers/build-your-own/processors/token-transfer-processor/examples/event_stats
-/docs/data/indexers/build-your-own/processors/token-transfer-processor/examples/filter_events
-/docs/data/oracles
-/docs/data/oracles/oracle-providers
-/docs/learn/fundamentals
-/docs/learn/fundamentals/anchors
-/docs/learn/fundamentals/contract-development
-/docs/learn/fundamentals/contract-development/authorization
-/docs/learn/fundamentals/contract-development/contract-interactions
-/docs/learn/fundamentals/contract-development/contract-interactions/cross-contract
-/docs/learn/fundamentals/contract-development/contract-interactions/overview
-/docs/learn/fundamentals/contract-development/contract-interactions/stellar-transaction
-/docs/learn/fundamentals/contract-development/contract-interactions/tests
-/docs/learn/fundamentals/contract-development/contract-interactions/transaction-simulation
-/docs/learn/fundamentals/contract-development/contract-lifecycle
-/docs/learn/fundamentals/contract-development/environment-concepts
-/docs/learn/fundamentals/contract-development/errors-and-debugging
-/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging
-/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging-errors
-/docs/learn/fundamentals/contract-development/errors-and-debugging/errors
-/docs/learn/fundamentals/contract-development/overview
-/docs/learn/fundamentals/contract-development/rust-dialect
-/docs/learn/fundamentals/contract-development/storage
-/docs/learn/fundamentals/contract-development/storage/persisting-data
-/docs/learn/fundamentals/contract-development/storage/state-archival
-/docs/learn/fundamentals/contract-development/types
-/docs/learn/fundamentals/contract-development/types/built-in-types
-/docs/learn/fundamentals/contract-development/types/custom-types
-/docs/learn/fundamentals/contract-development/types/fully-typed-contracts
-/docs/learn/fundamentals/data-format
-/docs/learn/fundamentals/data-format/xdr
-/docs/learn/fundamentals/data-format/xdr-json
-/docs/learn/fundamentals/fees-resource-limits-metering
-/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools
-/docs/learn/fundamentals/lumens
-/docs/learn/fundamentals/stellar-consensus-protocol
-/docs/learn/fundamentals/stellar-data-structures
-/docs/learn/fundamentals/stellar-data-structures/accounts
-/docs/learn/fundamentals/stellar-data-structures/assets
-/docs/learn/fundamentals/stellar-data-structures/contracts
-/docs/learn/fundamentals/stellar-data-structures/events
-/docs/learn/fundamentals/stellar-data-structures/ledgers
-/docs/learn/fundamentals/stellar-ecosystem-proposals
-/docs/learn/fundamentals/stellar-stack
-/docs/learn/fundamentals/transactions
-/docs/learn/fundamentals/transactions/list-of-operations
-/docs/learn/fundamentals/transactions/operations-and-transactions
-/docs/learn/fundamentals/transactions/signatures-multisig
-/docs/learn/fundamentals/transactions/transaction-lifecycle
-/docs/learn/glossary
-/docs/learn/interactive
-/docs/learn/interactive/dapp-world
-/docs/learn/interactive/fca00c
-/docs/learn/interactive/quest
-/docs/learn/migrate
-/docs/learn/migrate/evm
-/docs/learn/migrate/evm/introduction-to-solidity-and-rust
-/docs/learn/migrate/evm/smart-contract-deployment
-/docs/learn/migrate/evm/solidity-and-rust-advanced-concepts
-/docs/learn/migrate/evm/solidity-and-rust-basics
-/docs/learn/migrate/evm/solidity-support-via-solang
-/docs/networks
-/docs/networks/audits
-/docs/networks/audits/soroban-poseidon
-/docs/networks/audits/soroban-sdk
-/docs/networks/audits/stellar-core
-/docs/networks/audits/stellar-rpc
-/docs/networks/resource-limits-fees
-/docs/networks/software-versions
-/docs/platforms
-/docs/platforms/anchor-platform
-/docs/platforms/anchor-platform/admin-guide
-/docs/platforms/anchor-platform/admin-guide/architecture
-/docs/platforms/anchor-platform/admin-guide/assets-and-client-wallets
-/docs/platforms/anchor-platform/admin-guide/events
-/docs/platforms/anchor-platform/admin-guide/events/delivery
-/docs/platforms/anchor-platform/admin-guide/events/getting-started
-/docs/platforms/anchor-platform/admin-guide/events/integration
-/docs/platforms/anchor-platform/admin-guide/getting-started
-/docs/platforms/anchor-platform/api-reference
-/docs/platforms/anchor-platform/api-reference/callbacks
-/docs/platforms/anchor-platform/api-reference/callbacks/del-customer
-/docs/platforms/anchor-platform/api-reference/callbacks/get-customer
-/docs/platforms/anchor-platform/api-reference/callbacks/get-rates
-/docs/platforms/anchor-platform/api-reference/callbacks/post-event
-/docs/platforms/anchor-platform/api-reference/callbacks/put-customer
-/docs/platforms/anchor-platform/api-reference/platform
-/docs/platforms/anchor-platform/api-reference/platform/rpc
-/docs/platforms/anchor-platform/api-reference/platform/rpc/methods
-/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_payment
-/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_refund
-/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transaction
-/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transactions
-/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_amounts_updated
-/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_customer_info_updated
-/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_interactive_flow_completed
-/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_available
-/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_pending
-/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_received
-/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_sent
-/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_received
-/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_sent
-/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_pending
-/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_sent
-/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_error
-/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_expired
-/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_on_hold
-/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_recovery
-/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_trust_set
-/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_offchain_funds
-/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_onchain_funds
-/docs/platforms/anchor-platform/api-reference/platform/rpc/methods/request_trust
-/docs/platforms/anchor-platform/api-reference/platform/rpc/overview
-/docs/platforms/anchor-platform/api-reference/platform/transactions
-/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transaction
-/docs/platforms/anchor-platform/api-reference/platform/transactions/get-transactions
-/docs/platforms/anchor-platform/sep-guide
-/docs/platforms/anchor-platform/sep-guide/sep1
-/docs/platforms/anchor-platform/sep-guide/sep10
-/docs/platforms/anchor-platform/sep-guide/sep24
-/docs/platforms/anchor-platform/sep-guide/sep24/configuration
-/docs/platforms/anchor-platform/sep-guide/sep24/example
-/docs/platforms/anchor-platform/sep-guide/sep24/faq
-/docs/platforms/anchor-platform/sep-guide/sep24/getting-started
-/docs/platforms/anchor-platform/sep-guide/sep24/integration
-/docs/platforms/anchor-platform/sep-guide/sep24/setting-up-production-server
-/docs/platforms/anchor-platform/sep-guide/sep31
-/docs/platforms/anchor-platform/sep-guide/sep31/configuration
-/docs/platforms/anchor-platform/sep-guide/sep31/getting-started
-/docs/platforms/anchor-platform/sep-guide/sep31/integration
-/docs/platforms/anchor-platform/sep-guide/sep45
-/docs/platforms/anchor-platform/sep-guide/sep6
-/docs/platforms/anchor-platform/sep-guide/sep6/configuration
-/docs/platforms/anchor-platform/sep-guide/sep6/getting-started
-/docs/platforms/anchor-platform/sep-guide/sep6/integration
-/docs/platforms/stellar-disbursement-platform
-/docs/platforms/stellar-disbursement-platform/admin-guide
-/docs/platforms/stellar-disbursement-platform/admin-guide/advanced-configuration
-/docs/platforms/stellar-disbursement-platform/admin-guide/cli-manual
-/docs/platforms/stellar-disbursement-platform/admin-guide/configuring-sdp
-/docs/platforms/stellar-disbursement-platform/admin-guide/deploy-the-sdp
-/docs/platforms/stellar-disbursement-platform/admin-guide/design-and-architecture
-/docs/platforms/stellar-disbursement-platform/admin-guide/embedded-wallets
-/docs/platforms/stellar-disbursement-platform/admin-guide/getting-started
-/docs/platforms/stellar-disbursement-platform/admin-guide/making-your-wallet-sdp-ready
-/docs/platforms/stellar-disbursement-platform/admin-guide/monitoring
-/docs/platforms/stellar-disbursement-platform/admin-guide/overview
-/docs/platforms/stellar-disbursement-platform/admin-guide/security
-/docs/platforms/stellar-disbursement-platform/admin-guide/troubleshooting
-/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface
-/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/account-picker
-/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/analytics
-/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/circle-configuration
-/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/dashboard-home
-/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/disbursements
-/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/distribution-accounts
-/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/payments
-/docs/platforms/stellar-disbursement-platform/admin-guide/user-interface/receivers
-/docs/platforms/stellar-disbursement-platform/api-reference
-/docs/platforms/stellar-disbursement-platform/api-reference/admin
-/docs/platforms/stellar-disbursement-platform/api-reference/api-keys
-/docs/platforms/stellar-disbursement-platform/api-reference/archive-distribution-wallet
-/docs/platforms/stellar-disbursement-platform/api-reference/authenticate-mfa
-/docs/platforms/stellar-disbursement-platform/api-reference/authentication
-/docs/platforms/stellar-disbursement-platform/api-reference/balances
-/docs/platforms/stellar-disbursement-platform/api-reference/bridge-integration
-/docs/platforms/stellar-disbursement-platform/api-reference/create-api-key
-/docs/platforms/stellar-disbursement-platform/api-reference/create-asset
-/docs/platforms/stellar-disbursement-platform/api-reference/create-direct-payment
-/docs/platforms/stellar-disbursement-platform/api-reference/create-disbursement
-/docs/platforms/stellar-disbursement-platform/api-reference/create-distribution-wallet
-/docs/platforms/stellar-disbursement-platform/api-reference/create-receiver
-/docs/platforms/stellar-disbursement-platform/api-reference/create-tenant
-/docs/platforms/stellar-disbursement-platform/api-reference/create-user
-/docs/platforms/stellar-disbursement-platform/api-reference/create-wallet
-/docs/platforms/stellar-disbursement-platform/api-reference/default-tenant
-/docs/platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement
-/docs/platforms/stellar-disbursement-platform/api-reference/delete-api-key
-/docs/platforms/stellar-disbursement-platform/api-reference/delete-asset
-/docs/platforms/stellar-disbursement-platform/api-reference/delete-wallet
-/docs/platforms/stellar-disbursement-platform/api-reference/disbursements
-/docs/platforms/stellar-disbursement-platform/api-reference/distribution-wallets
-/docs/platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions
-/docs/platforms/stellar-disbursement-platform/api-reference/export-disbursements
-/docs/platforms/stellar-disbursement-platform/api-reference/export-payments-csv
-/docs/platforms/stellar-disbursement-platform/api-reference/export-receivers-csv
-/docs/platforms/stellar-disbursement-platform/api-reference/forgot-password
-/docs/platforms/stellar-disbursement-platform/api-reference/get-all-assets
-/docs/platforms/stellar-disbursement-platform/api-reference/get-all-roles
-/docs/platforms/stellar-disbursement-platform/api-reference/get-all-tenants
-/docs/platforms/stellar-disbursement-platform/api-reference/get-all-users
-/docs/platforms/stellar-disbursement-platform/api-reference/get-all-wallets
-/docs/platforms/stellar-disbursement-platform/api-reference/get-api-key
-/docs/platforms/stellar-disbursement-platform/api-reference/get-bridge-integration
-/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet
-/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-audit
-/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-balance
-/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallet-capabilities
-/docs/platforms/stellar-disbursement-platform/api-reference/get-distribution-wallets-total-balance
-/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-circle-balances
-/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-info
-/docs/platforms/stellar-disbursement-platform/api-reference/get-organization-logo
-/docs/platforms/stellar-disbursement-platform/api-reference/get-profile
-/docs/platforms/stellar-disbursement-platform/api-reference/get-receiver-registration-info
-/docs/platforms/stellar-disbursement-platform/api-reference/get-sep-24-info
-/docs/platforms/stellar-disbursement-platform/api-reference/grant-distribution-wallet-membership
-/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers
-/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursements
-/docs/platforms/stellar-disbursement-platform/api-reference/list-all-payments
-/docs/platforms/stellar-disbursement-platform/api-reference/list-all-receivers
-/docs/platforms/stellar-disbursement-platform/api-reference/list-api-keys
-/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallet-memberships
-/docs/platforms/stellar-disbursement-platform/api-reference/list-distribution-wallets
-/docs/platforms/stellar-disbursement-platform/api-reference/list-receiver-verification-types
-/docs/platforms/stellar-disbursement-platform/api-reference/list-registration-contact-types
-/docs/platforms/stellar-disbursement-platform/api-reference/log-in
-/docs/platforms/stellar-disbursement-platform/api-reference/organization
-/docs/platforms/stellar-disbursement-platform/api-reference/patch-organization-circle
-/docs/platforms/stellar-disbursement-platform/api-reference/payments
-/docs/platforms/stellar-disbursement-platform/api-reference/profile
-/docs/platforms/stellar-disbursement-platform/api-reference/promote-distribution-wallet-to-default
-/docs/platforms/stellar-disbursement-platform/api-reference/provide-signed-challenge-transaction
-/docs/platforms/stellar-disbursement-platform/api-reference/receivers
-/docs/platforms/stellar-disbursement-platform/api-reference/refresh-token
-/docs/platforms/stellar-disbursement-platform/api-reference/registration
-/docs/platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction
-/docs/platforms/stellar-disbursement-platform/api-reference/request-registration-url
-/docs/platforms/stellar-disbursement-platform/api-reference/reset-password
-/docs/platforms/stellar-disbursement-platform/api-reference/reset-user-password
-/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement
-/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment
-/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver
-/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant
-/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics
-/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics
-/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-stellar-info-file
-/docs/platforms/stellar-disbursement-platform/api-reference/retry-payments
-/docs/platforms/stellar-disbursement-platform/api-reference/revoke-distribution-wallet-membership
-/docs/platforms/stellar-disbursement-platform/api-reference/send-one-time-passcode
-/docs/platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant
-/docs/platforms/stellar-disbursement-platform/api-reference/start-wallet-registration
-/docs/platforms/stellar-disbursement-platform/api-reference/statistics
-/docs/platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status
-/docs/platforms/stellar-disbursement-platform/api-reference/update-a-tenant
-/docs/platforms/stellar-disbursement-platform/api-reference/update-api-key
-/docs/platforms/stellar-disbursement-platform/api-reference/update-bridge-integration
-/docs/platforms/stellar-disbursement-platform/api-reference/update-organization-profile
-/docs/platforms/stellar-disbursement-platform/api-reference/update-payment-status
-/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver
-/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet
-/docs/platforms/stellar-disbursement-platform/api-reference/update-receiver-wallet-status
-/docs/platforms/stellar-disbursement-platform/api-reference/update-user-activation-status
-/docs/platforms/stellar-disbursement-platform/api-reference/update-user-profile
-/docs/platforms/stellar-disbursement-platform/api-reference/update-user-role
-/docs/platforms/stellar-disbursement-platform/api-reference/update-wallet
-/docs/platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions
-/docs/platforms/stellar-disbursement-platform/api-reference/users
-/docs/platforms/stellar-disbursement-platform/api-reference/verify-receiver-registration
-/docs/tokens
-/docs/tokens/anatomy-of-an-asset
-/docs/tokens/control-asset-access
-/docs/tokens/cross-chain-transfers
-/docs/tokens/how-to-issue-an-asset
-/docs/tokens/publishing-asset-info
-/docs/tokens/quickstart
-/docs/tokens/stellar-asset-contract
-/docs/tokens/token-interface
-/docs/tokens/usdt0-layerzero
-/docs/tools
-/docs/tools/cli
-/docs/tools/cli/agent-cli
-/docs/tools/cli/agent-cli/guides/build-and-deploy-contracts
-/docs/tools/cli/agent-cli/guides/build-and-submit-transactions
-/docs/tools/cli/agent-cli/guides/check-balances-and-metadata
-/docs/tools/cli/agent-cli/guides/delegate-spending
-/docs/tools/cli/agent-cli/guides/pay-for-apis-x402
-/docs/tools/cli/agent-cli/guides/send-tokens
-/docs/tools/cli/agent-cli/guides/sign-messages
-/docs/tools/cli/agent-cli/guides/usdt0-on-mainnet
-/docs/tools/cli/agent-cli/quickstart
-/docs/tools/cli/agent-cli/reference/architecture
-/docs/tools/cli/agent-cli/reference/authority-model
-/docs/tools/cli/agent-cli/reference/output-and-errors
-/docs/tools/cli/agent-cli/reference/troubleshooting
-/docs/tools/cli/agent-cli/skills
-/docs/tools/cli/cookbook
-/docs/tools/cli/cookbook/asset-management
-/docs/tools/cli/cookbook/contract-build-meta
-/docs/tools/cli/cookbook/contract-invoke-arguments
-/docs/tools/cli/cookbook/contract-lifecycle
-/docs/tools/cli/cookbook/deploy-contract
-/docs/tools/cli/cookbook/deploy-stellar-asset-contract
-/docs/tools/cli/cookbook/extend-contract-instance
-/docs/tools/cli/cookbook/extend-contract-storage
-/docs/tools/cli/cookbook/extend-contract-wasm
-/docs/tools/cli/cookbook/payments-and-assets
-/docs/tools/cli/cookbook/restore-contract-instance
-/docs/tools/cli/cookbook/restore-contract-storage
-/docs/tools/cli/cookbook/stellar-keys
-/docs/tools/cli/cookbook/tx-new
-/docs/tools/cli/cookbook/tx-new-create-claimable-balance
-/docs/tools/cli/cookbook/tx-op-add
-/docs/tools/cli/cookbook/tx-sign
-/docs/tools/cli/cookbook/upload-deploy
-/docs/tools/cli/cookbook/upload-wasm
-/docs/tools/cli/install-cli
-/docs/tools/cli/plugins
-/docs/tools/cli/plugins-list
-/docs/tools/cli/stellar-cli
-/docs/tools/developer-tools
-/docs/tools/developer-tools/analytics-platforms
-/docs/tools/developer-tools/anchor-tools
-/docs/tools/developer-tools/asset-tools
-/docs/tools/developer-tools/block-explorers
-/docs/tools/developer-tools/jupyter-notebooks
-/docs/tools/developer-tools/network-insights
-/docs/tools/developer-tools/network-status
-/docs/tools/developer-tools/node-operator-tools
-/docs/tools/developer-tools/online-ide
-/docs/tools/developer-tools/security-tools
-/docs/tools/developer-tools/wallets
-/docs/tools/infra-tools
-/docs/tools/infra-tools/cross-chain
-/docs/tools/lab
-/docs/tools/lab/account
-/docs/tools/lab/api-explorer
-/docs/tools/lab/api-explorer/horizon-endpoint
-/docs/tools/lab/api-explorer/rpc-methods
-/docs/tools/lab/quickstart-with-lab
-/docs/tools/lab/saved
-/docs/tools/lab/saved/keypairs
-/docs/tools/lab/saved/requests
-/docs/tools/lab/saved/transactions
-/docs/tools/lab/smart-contracts
-/docs/tools/lab/smart-contracts/contract-explorer
-/docs/tools/lab/smart-contracts/smart-contract-list
-/docs/tools/lab/smart-contracts/upload-deploy-contract
-/docs/tools/lab/transaction-dashboard
-/docs/tools/lab/transactions
-/docs/tools/lab/view-xdr
-/docs/tools/lab/view-xdr/diff-xdr
-/docs/tools/lab/view-xdr/json-to-xdr
-/docs/tools/lab/view-xdr/xdr-to-json
-/docs/tools/openzeppelin-contracts
-/docs/tools/openzeppelin-relayer
-/docs/tools/quickstart
-/docs/tools/quickstart/advanced-usage
-/docs/tools/quickstart/advanced-usage/container
-/docs/tools/quickstart/advanced-usage/operation-modes
-/docs/tools/quickstart/advanced-usage/ports
-/docs/tools/quickstart/advanced-usage/run-command-examples
-/docs/tools/quickstart/advanced-usage/service-options
-/docs/tools/quickstart/cloud
-/docs/tools/quickstart/cloud/digitalocean
-/docs/tools/quickstart/cloud/fly.io
-/docs/tools/quickstart/debugging
-/docs/tools/quickstart/debugging/diagnostic-events
-/docs/tools/quickstart/debugging/viewing-logs
-/docs/tools/quickstart/explorer
-/docs/tools/quickstart/faucet
-/docs/tools/quickstart/getting-started
-/docs/tools/quickstart/getting-started/connect-stellar-lab
-/docs/tools/quickstart/getting-started/deploy-smart-contract
-/docs/tools/quickstart/network-modes
-/docs/tools/ramps
-/docs/tools/ramps/moneygram
-/docs/tools/scaffold-stellar
-/docs/tools/sdks
-/docs/tools/sdks/build-your-own
-/docs/tools/sdks/client-sdks
-/docs/tools/sdks/contract-sdks
-/docs/validators
-/docs/validators/admin-guide
-/docs/validators/admin-guide/advanced
-/docs/validators/admin-guide/commands
-/docs/validators/admin-guide/configuring
-/docs/validators/admin-guide/environment-preparation
-/docs/validators/admin-guide/installation
-/docs/validators/admin-guide/logging
-/docs/validators/admin-guide/maintenance
-/docs/validators/admin-guide/monitoring
-/docs/validators/admin-guide/network-upgrades
-/docs/validators/admin-guide/prerequisites
-/docs/validators/admin-guide/publishing-history-archives
-/docs/validators/admin-guide/running-node
-/docs/validators/admin-guide/soroban-settings
-/docs/validators/tier-1-orgs
-/meetings
-/meetings/2024/01/18
-/meetings/2024/01/26
-/meetings/2024/02/01
-/meetings/2024/02/08
-/meetings/2024/02/15
-/meetings/2024/02/22
-/meetings/2024/02/29
-/meetings/2024/03/07
-/meetings/2024/03/14
-/meetings/2024/03/21
-/meetings/2024/03/28
-/meetings/2024/04/04
-/meetings/2024/04/11
-/meetings/2024/04/18
-/meetings/2024/04/25
-/meetings/2024/05/02
-/meetings/2024/05/09
-/meetings/2024/06/13
-/meetings/2024/06/20
-/meetings/2024/06/27
-/meetings/2024/07/11
-/meetings/2024/07/18
-/meetings/2024/07/25
-/meetings/2024/08/01
-/meetings/2024/08/08
-/meetings/2024/08/15
-/meetings/2024/08/22
-/meetings/2024/08/29
-/meetings/2024/09/05
-/meetings/2024/09/12
-/meetings/2024/09/19
-/meetings/2024/09/26
-/meetings/2024/10/24
-/meetings/2024/11/14
-/meetings/2024/12/05
-/meetings/2024/12/12
-/meetings/2024/12/19
-/meetings/2025/01/16
-/meetings/2025/01/23
-/meetings/2025/01/30
-/meetings/2025/02/06
-/meetings/2025/02/13
-/meetings/2025/02/20
-/meetings/2025/02/27
-/meetings/2025/03/06
-/meetings/2025/03/27
-/meetings/2025/04/03
-/meetings/2025/04/10
-/meetings/2025/04/17
-/meetings/2025/05/01
-/meetings/2025/05/22
-/meetings/2025/07/10
-/meetings/2025/07/17
-/meetings/2025/07/24
-/meetings/2025/08/07
-/meetings/2025/09/25
-/meetings/2025/10/02
-/meetings/2025/10/09
-/meetings/2025/10/16
-/meetings/2025/10/23
-/meetings/2025/10/30
-/meetings/2025/11/06
-/meetings/2026/01/22
-/meetings/2026/01/29
-/meetings/2026/02/26
-/meetings/2026/04/16
-/meetings/2026/04/23
-/meetings/2026/04/30
-/meetings/2026/05/07
-/meetings/2026/05/14
-/meetings/2026/05/21
-/meetings/2026/06/11
-/meetings/2026/06/18
-/meetings/2026/06/25
-/meetings/2026/07/02
-/meetings/2026/07/09
-/meetings/2026/07/16
-/meetings/2026/07/16/protocol
-/meetings/2026/07/23
-/meetings/2026/07/30
-/meetings/2026/08/06
-/meetings/2026/08/13
-/meetings/2026/08/20
-/meetings/2026/08/27
-/meetings/2026/09/03
-/meetings/2026/09/10
-/meetings/2026/09/17
-/meetings/2026/09/17/protocol
-/meetings/2026/09/24
-/meetings/2026/10/01
-/meetings/2026/10/08
-/meetings/archive
-/meetings/authors
-/meetings/authors/carstenjacobsen
-/meetings/authors/carstenjacobsen/page/2
-/meetings/authors/carstenjacobsen/page/3
-/meetings/authors/elliotfriend
-/meetings/authors/kalepail
-/meetings/page/2
-/meetings/page/3
-/meetings/page/4
-/meetings/page/5
-/meetings/page/6
-/meetings/page/7
-/meetings/page/8
-/meetings/tags
-/meetings/tags/developer
-/meetings/tags/developer/page/2
-/meetings/tags/developer/page/3
-/meetings/tags/developer/page/4
-/meetings/tags/developer/page/5
-/meetings/tags/developer/page/6
-/meetings/tags/developer/page/7
-/meetings/tags/protocol
-/meetings/tags/protocol/page/2
-/search
diff --git a/scripts/check-relative-links.sh b/scripts/check-relative-links.sh
deleted file mode 100755
index 568a231b7..000000000
--- a/scripts/check-relative-links.sh
+++ /dev/null
@@ -1,84 +0,0 @@
-#!/usr/bin/env bash
-#
-# Canonical check: internal doc links must be relative (../path/file.mdx), not
-# absolute /docs/... routes. Relative links are validated at build time by
-# Docusaurus' onBrokenMarkdownLinks; absolute route links are not.
-#
-# This is the single source of truth shared by CI (.github/workflows/main.yml)
-# and the local pre-commit hook (.husky/pre-commit) — like `pnpm format:mdx`,
-# there is one definition of the rule, not two driftable copies.
-#
-# It only flags absolute /docs links in NEWLY PROPOSED content: it reads a
-# word-level diff and inspects added tokens only. Editing a typo on a line that
-# already contains an absolute link does not flag that link (the link stays a
-# context token); introducing or editing a /docs link does. Pre-existing debt
-# in untouched lines is never the contributor's problem.
-#
-# CONTRIBUTING.md is excluded: it is not part of the docs build and its /docs
-# link is an intentional, illustrative example.
-#
-# Usage:
-#   scripts/check-relative-links.sh --staged                 # staged changes (pre-commit)
-#   scripts/check-relative-links.sh --range [BASE...HEAD]     # PR range (CI); default origin/main...HEAD
-#
-# Exit 0 = clean, 1 = absolute /docs link(s) introduced.
-
-set -euo pipefail
-
-mode="${1:---range}"
-DOCS_PATHSPEC=('docs/*.md' 'docs/*.mdx')
-
-case "$mode" in
-  --staged)
-    diff_cmd=(git diff --cached --word-diff=porcelain -- "${DOCS_PATHSPEC[@]}")
-    ;;
-  --range)
-    range="${2:-origin/main...HEAD}"
-    diff_cmd=(git diff --word-diff=porcelain "$range" -- "${DOCS_PATHSPEC[@]}")
-    ;;
-  *)
-    echo "usage: $0 [--staged | --range [BASE...HEAD]]" >&2
-    exit 2
-    ;;
-esac
-
-# Walk the word-diff porcelain stream. For each new-file line, remember whether
-# any *added* token on it contains an absolute '](/docs' link; report that line
-# if so. New-file line numbers are tracked from each hunk's @@ header, advancing
-# on every completed line except pure deletions (old-file-only).
-findings=$(
-  "${diff_cmd[@]}" | awk '
-    function reset() { hasrem=0; haskept=0; flag=0 }
-    /^diff --git / { infile=0; reset(); next }
-    /^--- /        { next }
-    /^\+\+\+ /     { path=substr($0,7); sub(/\t.*/,"",path); infile=1; next }
-    /^@@ /         { match($0,/\+[0-9]+/); newno=substr($0,RSTART+1,RLENGTH-1)+0; reset(); next }
-    !infile        { next }
-    /^~/ {
-      is_removal_only = (hasrem && !haskept)
-      if (!is_removal_only) {
-        if (flag && path !~ /CONTRIBUTING\.md$/)
-          print path ":" newno ": absolute /docs link introduced in added content — use a relative ../path/file.mdx link"
-        newno++
-      }
-      reset(); next
-    }
-    {
-      pfx = substr($0,1,1); tok = substr($0,2)
-      if (pfx == "-")      { hasrem = 1 }
-      else if (pfx == "+") { haskept = 1; if (tok ~ /\]\(\/docs/) flag = 1 }
-      else                 { haskept = 1 }   # context token (leading space)
-    }
-  '
-)
-
-if [ -n "$findings" ]; then
-  echo "$findings"
-  echo ""
-  echo "Fix: replace the absolute /docs/... link with a relative link ending in .mdx"
-  echo "(e.g. ../getting-started/setup.mdx). See docs/platforms/anchor-platform/CONTRIBUTING.md."
-  exit 1
-fi
-
-echo "All links check out"
-exit 0
diff --git a/scripts/generate_api_markdown.mjs b/scripts/generate_api_markdown.mjs
deleted file mode 100644
index d30f92e79..000000000
--- a/scripts/generate_api_markdown.mjs
+++ /dev/null
@@ -1,570 +0,0 @@
-// @ts-check
-/**
- * Post-build step for the markdown-source feature (follow-up to PR #2289,
- * issue #2643): generate complete `.md` twins for API reference pages.
- *
- * The docusaurus-markdown-source-plugin builds each page's `.md` twin from the
- * page's static content. That works for prose pages, but API reference pages
- * (generated by docusaurus-plugin-openapi-docs from the bundled OpenAPI specs)
- * render their operation content — parameters, request/response schemas,
- * examples — client-side, so their twins come out near-empty: just the
- * one-line operation description (~39 tokens vs ~14k tokens of rendered HTML).
- *
- * A second pass covers the hand-written api-reference pages (object/schema
- * pages, result codes, resource indexes) whose content sits inside JSX
- * components like `<AttributeTable>`: the plugin drops JSX blocks together
- * with their markdown children, so those twins lose their attribute tables.
- * See patchComponentPages().
- *
- * This script rebuilds the operation twins from the operation data itself. Every
- * `docs/**\/api-reference/**\/*.api.mdx` source file carries the complete,
- * dereferenced operation object (the exact data the page renders) in its
- * `api:` frontmatter field, zlib-compressed and base64-encoded by the openapi
- * plugin. We decode it and emit clean markdown — method + path, auth,
- * parameters, request body, response schemas, and examples — over the
- * near-empty twin at the matching `build/**\/api-reference/**\/<id>.md` path.
- *
- * Like scripts/rewrite_md_links.mjs (which runs after this in `postbuild` and
- * normalizes any intra-doc links), this is output-only: it writes ONLY
- * `build/**\/api-reference/**\/*.md`, never touches HTML or repo sources, and
- * is idempotent (deterministic output; unchanged files are not rewritten).
- */
-
-import { globSync, readFileSync, writeFileSync, existsSync } from 'node:fs';
-import { inflateSync } from 'node:zlib';
-import { dirname, join, relative } from 'node:path';
-
-const DOCS_DIR = 'docs';
-const BUILD_DIR = 'build';
-const MAX_DEPTH = 12; // schema nesting cap; blobs are acyclic but can run deep
-const MAX_EXAMPLE_CHARS = 20000; // skip pathological examples, keep real ones
-
-// ---------------------------------------------------------------------------
-// Frontmatter + operation blob
-// ---------------------------------------------------------------------------
-
-/** Pull the fields we need out of an .api.mdx frontmatter block. */
-function parseFrontmatter(src) {
-  const fm = src.match(/^---\n([\s\S]*?)\n---/);
-  if (!fm) return null;
-  const get = (key) => {
-    const m = fm[1].match(new RegExp(`^${key}: (.+)$`, 'm'));
-    if (!m) return null;
-    let v = m[1].trim();
-    if (v.startsWith('"') && v.endsWith('"')) {
-      v = v.slice(1, -1).replace(/\\"/g, '"');
-    }
-    return v;
-  };
-  return { id: get('id'), title: get('title'), api: get('api') };
-}
-
-/** Decode the `api:` frontmatter value into the operation object. */
-function decodeOperation(apiValue) {
-  if (apiValue.startsWith('{')) return JSON.parse(apiValue); // uncompressed
-  return JSON.parse(inflateSync(Buffer.from(apiValue, 'base64')).toString('utf8'));
-}
-
-// ---------------------------------------------------------------------------
-// Schema rendering — nested bullet tree
-// ---------------------------------------------------------------------------
-
-/** Human-readable type for a schema node, e.g. "array of object", "string (uuid)". */
-function typeLabel(schema) {
-  if (!schema || typeof schema !== 'object') return 'any';
-  if (schema.oneOf) return 'one of';
-  if (schema.anyOf) return 'any of';
-  if (schema.allOf) return 'object';
-  let base = schema.type;
-  if (!base) base = schema.properties ? 'object' : schema.items ? 'array' : 'any';
-  if (base === 'array') return `array of ${typeLabel(schema.items)}`;
-  let label = base;
-  if (schema.format) label += ` (${schema.format})`;
-  if (schema.nullable) label += ', nullable';
-  return label;
-}
-
-/** Collapse a (possibly multi-line, markdown-ish) description onto one line. */
-function inlineText(text) {
-  if (!text) return '';
-  return String(text).replace(/\s*\n\s*/g, ' ').trim();
-}
-
-/** Merge the object members of an allOf into one view; keep the rest as-is. */
-function mergeAllOf(schema) {
-  const merged = { type: 'object', properties: {}, required: [] };
-  const leftovers = [];
-  for (const member of schema.allOf) {
-    if (member && typeof member === 'object' && (member.properties || member.type === 'object')) {
-      Object.assign(merged.properties, member.properties ?? {});
-      merged.required.push(...(member.required ?? []));
-      if (member.description && !merged.description) merged.description = member.description;
-    } else if (member) {
-      leftovers.push(member);
-    }
-  }
-  return { merged, leftovers };
-}
-
-/** One bullet line for a named schema node. */
-function propertyLine(name, schema, required) {
-  const parts = [`\`${name}\``, '—', typeLabel(schema)];
-  if (required) parts.push('(required)');
-  if (schema?.deprecated) parts.push('(deprecated)');
-  const desc = inlineText(
-    schema?.description ?? schema?.allOf?.find((member) => member?.description)?.description,
-  );
-  if (desc) parts.push('—', desc);
-  return parts.join(' ');
-}
-
-const MAX_INLINE_EXAMPLE_CHARS = 300; // property examples are short; skip outliers
-
-/**
- * JSON-encode an example for inline display, or return null when it is too long
- * or carries a character we would have to escape inside a code span. `unsafe`
- * is stricter in table cells, where a pipe or backslash breaks the row.
- */
-function inlineExample(value, unsafe = /`/) {
-  if (value === undefined) return null;
-  const json = JSON.stringify(value);
-  if (json === undefined || json.length > MAX_INLINE_EXAMPLE_CHARS || unsafe.test(json)) {
-    return null;
-  }
-  return json;
-}
-
-/** Trailing detail bullets (enum/default/example/pattern/bounds) for a schema node. */
-function detailLines(schema, pad, lines) {
-  if (schema.enum) {
-    lines.push(`${pad}Possible values: ${schema.enum.map((v) => `\`${v}\``).join(', ')}.`);
-  }
-  if (schema.default !== undefined) {
-    lines.push(`${pad}Default: \`${JSON.stringify(schema.default)}\`.`);
-  }
-  const example = inlineExample(schema.example);
-  if (example) {
-    lines.push(`${pad}Example: \`${example}\`.`);
-  }
-  if (schema.pattern && !schema.pattern.includes('`')) {
-    lines.push(`${pad}Pattern: \`${schema.pattern}\`.`);
-  }
-  bounds('Items', schema.minItems, schema.maxItems, pad, lines);
-  bounds('Length', schema.minLength, schema.maxLength, pad, lines);
-  bounds('Properties', schema.minProperties, schema.maxProperties, pad, lines);
-}
-
-/** "Items: min 1, max 5." — skipped when the schema sets neither bound. */
-function bounds(label, min, max, pad, lines) {
-  const parts = [];
-  if (min !== undefined) parts.push(`min ${min}`);
-  if (max !== undefined) parts.push(`max ${max}`);
-  if (parts.length) lines.push(`${pad}${label}: ${parts.join(', ')}.`);
-}
-
-/**
- * Render a schema's CHILDREN (properties / variants / items) as indented
- * bullets. The node's own line is the caller's responsibility.
- */
-function renderChildren(schema, depth, lines) {
-  if (!schema || typeof schema !== 'object' || depth > MAX_DEPTH) {
-    if (depth > MAX_DEPTH) lines.push(`${'  '.repeat(depth)}- … (nesting truncated)`);
-    return;
-  }
-  const pad = '  '.repeat(depth);
-
-  if (schema.allOf) {
-    const { merged, leftovers } = mergeAllOf(schema);
-    renderChildren(merged, depth, lines);
-    for (const leftover of leftovers) renderChildren(leftover, depth, lines);
-    return;
-  }
-
-  for (const key of ['oneOf', 'anyOf']) {
-    if (schema[key]) {
-      schema[key].forEach((variant, i) => {
-        const name = variant?.title ?? `variant ${i + 1}`;
-        const parts = [
-          `${pad}- ${key === 'oneOf' ? 'One of' : 'Any of'}: **${name}** — ${typeLabel(variant)}`,
-        ];
-        // Untitled variants carry their meaning in the description, so dropping
-        // it leaves "variant 1 — string" and no way to tell the options apart.
-        const desc = inlineText(variant?.description);
-        if (desc) parts.push('—', desc);
-        lines.push(parts.join(' '));
-        renderChildren(variant, depth + 1, lines);
-      });
-      return;
-    }
-  }
-
-  if (schema.type === 'array' || schema.items) {
-    renderChildren(schema.items, depth, lines);
-    return;
-  }
-
-  const required = new Set(schema.required ?? []);
-  for (const [name, child] of Object.entries(schema.properties ?? {})) {
-    lines.push(`${pad}- ${propertyLine(name, child, required.has(name))}`);
-    detailLines(child, `${pad}  `, lines);
-    renderChildren(child, depth + 1, lines);
-  }
-  // `additionalProperties` is a schema or the bare `true` (Horizon's
-  // Problem.extras). typeLabel() answers "any" for the bare form, which has no
-  // children to walk.
-  if (schema.additionalProperties) {
-    lines.push(`${pad}- (additional properties) — ${typeLabel(schema.additionalProperties)}`);
-    if (typeof schema.additionalProperties === 'object') {
-      renderChildren(schema.additionalProperties, depth + 1, lines);
-    }
-  }
-}
-
-/** Render a full schema (top line + children) as markdown lines. */
-function renderSchema(schema, lines) {
-  if (!schema || typeof schema !== 'object') return;
-  const topDesc = inlineText(schema.description);
-  // An object root introduces itself through its property bullets. Anything
-  // else — a leaf, an array, a set of variants — loses its type unless we name
-  // it, because renderChildren only ever emits the children.
-  const isObjectRoot = Boolean(schema.properties || schema.allOf) && !schema.items;
-  if (isObjectRoot) {
-    if (topDesc) lines.push(topDesc);
-  } else {
-    lines.push(`Schema: ${typeLabel(schema)}${topDesc ? ` — ${topDesc}` : ''}`);
-  }
-  detailLines(schema, '', lines);
-  renderChildren(schema, 0, lines);
-}
-
-// ---------------------------------------------------------------------------
-// Sections
-// ---------------------------------------------------------------------------
-
-/** Fenced JSON block, or null when there is nothing to show or it is too big. */
-function fencedJson(value) {
-  const json = JSON.stringify(value, null, 2);
-  if (json === undefined || json.length > MAX_EXAMPLE_CHARS) return null;
-  return ['```json', json, '```'];
-}
-
-/**
- * Push a labelled example. The heading goes in only when the block renders,
- * so an example over MAX_EXAMPLE_CHARS leaves no empty "Example:" behind.
- */
-function pushExample(label, value, lines) {
-  const block = fencedJson(value);
-  if (!block) return;
-  lines.push('', label, '', ...block);
-}
-
-/** Examples attached to a media-type object ({example} or {examples: {..}}). */
-function renderExamples(media, lines) {
-  if (media.example !== undefined) {
-    pushExample('Example:', media.example, lines);
-    return;
-  }
-  const entries = Object.entries(media.examples ?? {});
-  for (const [name, entry] of entries) {
-    pushExample(
-      entries.length > 1 ? `Example (${name}):` : 'Example:',
-      entry?.value !== undefined ? entry.value : entry,
-      lines,
-    );
-  }
-}
-
-function renderParameters(parameters, lines) {
-  const groups = new Map([['path', []], ['query', []], ['header', []], ['cookie', []]]);
-  for (const param of parameters) groups.get(param.in)?.push(param);
-  lines.push('', '## Parameters');
-  for (const [location, params] of groups) {
-    if (!params.length) continue;
-    lines.push('', `### ${location[0].toUpperCase()}${location.slice(1)} parameters`, '');
-    lines.push('| Name | Type | Required | Description |', '| --- | --- | --- | --- |');
-    for (const param of params) {
-      let desc = inlineText(param.description).replace(/\\/g, '\\\\').replace(/\|/g, '\\|');
-      if (param.schema?.enum) {
-        desc += `${desc ? ' ' : ''}Possible values: ${param.schema.enum.map((v) => `\`${v}\``).join(', ')}.`;
-      }
-      if (param.schema?.default !== undefined) {
-        desc += ` Default: \`${JSON.stringify(param.schema.default)}\`.`;
-      }
-      // A parameter carries its example either on itself or on its schema.
-      const example = inlineExample(
-        param.example !== undefined ? param.example : param.schema?.example,
-        /[`|\\]/,
-      );
-      if (example) {
-        desc += `${desc ? ' ' : ''}Example: \`${example}\`.`;
-      }
-      lines.push(`| \`${param.name}\` | ${typeLabel(param.schema)} | ${param.required ? 'yes' : 'no'} | ${desc} |`);
-    }
-  }
-}
-
-function renderRequestBody(op, lines) {
-  const body = op.requestBody;
-  lines.push('', `## Request body${body.required ? ' (required)' : ''}`);
-  const bodyDesc = inlineText(body.description);
-  if (bodyDesc) lines.push('', bodyDesc);
-  for (const [contentType, media] of Object.entries(body.content ?? {})) {
-    lines.push('', `Content type: \`${contentType}\``, '');
-    if (media.schema) renderSchema(media.schema, lines);
-    if (media.example !== undefined || media.examples) {
-      renderExamples(media, lines);
-    } else if (media.schema?.example !== undefined) {
-      pushExample('Example:', media.schema.example, lines);
-    } else if (op.jsonRequestBodyExample != null) {
-      pushExample('Example:', op.jsonRequestBodyExample, lines);
-    }
-  }
-}
-
-function renderResponses(responses, lines) {
-  lines.push('', '## Responses');
-  for (const [status, response] of Object.entries(responses)) {
-    lines.push('', `### ${status}`, '');
-    const desc = inlineText(response.description);
-    if (desc) lines.push(desc, '');
-    const headers = Object.entries(response.headers ?? {});
-    if (headers.length) {
-      lines.push('#### Headers', '', '| Name | Type | Description |', '| --- | --- | --- |');
-      for (const [name, header] of headers) {
-        const headerDesc = inlineText(header.description).replace(/\\/g, '\\\\').replace(/\|/g, '\\|');
-        lines.push(`| \`${name}\` | ${typeLabel(header.schema)} | ${headerDesc} |`);
-      }
-      lines.push('');
-    }
-    for (const [contentType, media] of Object.entries(response.content ?? {})) {
-      lines.push(`Content type: \`${contentType}\``, '');
-      if (media.schema) renderSchema(media.schema, lines);
-      renderExamples(media, lines);
-    }
-  }
-}
-
-/** Render one operation object as a complete markdown page. */
-function renderOperation(op, title) {
-  const lines = [`# ${title}`, '', `\`${(op.method ?? '').toUpperCase()} ${op.path}\``];
-
-  const servers = (op.servers ?? []).filter((server) => server.url);
-  if (servers.length) {
-    lines.push('', ...servers.map(
-      (server) => `- Base URL: \`${server.url}\`${server.description ? ` (${server.description})` : ''}`,
-    ));
-  }
-  if (op.description) lines.push('', op.description.trim());
-  if (op['x-supports-streaming']) {
-    lines.push('', 'This endpoint supports [streaming](https://developers.stellar.org/docs/data/apis/horizon/api-reference/structure/streaming.md) via Server-Sent Events.');
-  }
-  const securityNames = (op.security ?? []).flatMap((requirement) => Object.keys(requirement));
-  if (securityNames.length) {
-    lines.push('', `Authentication: ${securityNames.map((name) => `\`${name}\``).join(' or ')}.`);
-  }
-
-  if (op.parameters?.length) renderParameters(op.parameters, lines);
-  if (op.requestBody) renderRequestBody(op, lines);
-  if (op.responses) renderResponses(op.responses, lines);
-
-  const codeSamples = op['x-codeSamples'] ?? [];
-  if (codeSamples.length) {
-    lines.push('', '## Code samples');
-    for (const sample of codeSamples) {
-      lines.push('', `\`\`\`${(sample.lang ?? '').toLowerCase()}`, sample.source ?? '', '```');
-    }
-  }
-
-  return `${lines.join('\n').replace(/\n{3,}/g, '\n\n').trimEnd()}\n`;
-}
-
-// ---------------------------------------------------------------------------
-// Pass 2: hand-written api-reference pages whose content lives inside JSX
-// components (`<AttributeTable>` and friends). The markdown-source-plugin
-// drops JSX blocks *including their children* when it builds a page's twin,
-// so e.g. the Fee Stats object page's twin loses the entire attribute list
-// even though that list is plain markdown in the source. These pages are
-// hand-written .mdx (not .api.mdx), all under api-reference.
-// ---------------------------------------------------------------------------
-
-/** Components whose children are plain markdown we can pass through. */
-const UNWRAP_COMPONENTS = ['AttributeTable', 'ExampleResponse', 'CodeExample', 'MethodTable'];
-const COMPONENT_OPEN = new RegExp(`^\\s*<(${UNWRAP_COMPONENTS.join('|')})(\\s[^>]*)?>\\s*$`);
-const COMPONENT_CLOSE = new RegExp(`^\\s*</(${UNWRAP_COMPONENTS.join('|')})>\\s*$`);
-
-function prepareBody(src) {
-  return src.replace(/^---\n[\s\S]*?\n---\n/, '');
-}
-
-/**
- * Walk the body line by line, tracking code-fence state so that import-like
- * lines or tag-like lines inside fenced code are never touched.
- *
- * With keepChildren=false this mimics what the plugin emits: import lines and
- * whole component blocks (children included) dropped. That form is used only
- * as a safety check — we overwrite a twin only when we can prove it is the
- * plugin's own output for this source. With keepChildren=true the component
- * tags go away but their markdown children stay: the actual patched twin.
- */
-function transformBody(body, keepChildren) {
-  const out = [];
-  let inFence = false;
-  let depth = 0;
-  for (const line of body.split('\n')) {
-    if (/^\s*(```|~~~)/.test(line)) {
-      inFence = !inFence;
-      if (depth === 0 || keepChildren) out.push(line);
-      continue;
-    }
-    if (!inFence) {
-      if (/^import\s/.test(line)) continue;
-      const open = line.match(COMPONENT_OPEN);
-      if (open) {
-        depth++;
-        if (keepChildren) {
-          const title = (open[2] ?? '').match(/title="([^"]+)"/);
-          if (title) out.push(`**${title[1]}**`, '');
-        }
-        continue;
-      }
-      if (COMPONENT_CLOSE.test(line)) {
-        depth = Math.max(0, depth - 1);
-        continue;
-      }
-    }
-    if (depth === 0 || keepChildren) out.push(line);
-  }
-  return out.join('\n');
-}
-
-/**
- * Whitespace- and link-target-insensitive comparison key. Link targets are
- * masked because scripts/rewrite_md_links.mjs (which runs after this one)
- * rewrites relative targets to absolute URLs in every built .md file.
- */
-function comparisonKey(text) {
-  return text
-    .replace(/\]\([^)]*\)/g, ']()')
-    .replace(/[ \t]+$/gm, '')
-    .replace(/\n{2,}/g, '\n')
-    .trim();
-}
-
-/** docs/<dir>/<name>.mdx -> its built twin path (README.mdx is the dir index). */
-function proseTwinPath(source) {
-  const dir = relative(DOCS_DIR, dirname(source));
-  const base = source.split('/').pop().replace(/\.mdx$/, '');
-  return base === 'README'
-    ? join(BUILD_DIR, DOCS_DIR, `${dir}.md`)
-    : join(BUILD_DIR, DOCS_DIR, dir, `${base}.md`);
-}
-
-function patchComponentPages() {
-  const sources = globSync(`${DOCS_DIR}/**/*.mdx`)
-    .filter((p) => p.includes('/api-reference/') && !p.endsWith('.api.mdx') && !p.includes('/component/'))
-    .sort();
-
-  let written = 0;
-  let unchanged = 0;
-  let skipped = 0;
-  let candidates = 0;
-
-  for (const source of sources) {
-    const src = readFileSync(source, 'utf8');
-    if (!UNWRAP_COMPONENTS.some((name) => src.includes(`<${name}`))) continue;
-    // scripts/rewrite_md_code_examples.mjs runs after this one and regenerates
-    // the twin of every <CodeExample> page from source, unwrapping all four
-    // components. Writing those twins here would only be overwritten, so it
-    // owns them.
-    if (/<CodeExample\b/.test(src)) continue;
-    candidates++;
-
-    const twin = proseTwinPath(source);
-    if (!existsSync(twin)) {
-      console.warn(`[generate-api-markdown] no twin for ${source} — skipping.`);
-      skipped++;
-      continue;
-    }
-
-    const body = prepareBody(src);
-    const existing = readFileSync(twin, 'utf8');
-    const unwrapped = `${transformBody(body, true).replace(/\n{3,}/g, '\n\n').trimEnd()}\n`;
-
-    if (comparisonKey(existing) === comparisonKey(unwrapped)) {
-      unchanged++;
-      continue;
-    }
-    // Only overwrite what we can recognize as the plugin's own (lossy) output.
-    if (comparisonKey(existing) !== comparisonKey(transformBody(body, false))) {
-      console.warn(`[generate-api-markdown] twin for ${source} doesn't match its source — leaving it alone.`);
-      skipped++;
-      continue;
-    }
-    writeFileSync(twin, unwrapped);
-    written++;
-  }
-
-  console.log(
-    `[generate-api-markdown] Patched ${written} component-page twin(s) (${unchanged} already current, ${skipped} skipped) from ${candidates} candidate page(s).`,
-  );
-}
-
-// ---------------------------------------------------------------------------
-// Main
-// ---------------------------------------------------------------------------
-
-function main() {
-  if (!existsSync(BUILD_DIR)) {
-    console.warn(`[generate-api-markdown] "${BUILD_DIR}/" not found — skipping.`);
-    return;
-  }
-
-  const sources = globSync(`${DOCS_DIR}/**/*.api.mdx`)
-    .filter((p) => p.includes('/api-reference/'))
-    .sort();
-
-  let written = 0;
-  let unchanged = 0;
-  let skipped = 0;
-
-  for (const source of sources) {
-    const fm = parseFrontmatter(readFileSync(source, 'utf8'));
-    if (!fm?.id || !fm.api) {
-      console.warn(`[generate-api-markdown] no id/api frontmatter in ${source} — skipping.`);
-      skipped++;
-      continue;
-    }
-
-    // docs/<section>/<name>.api.mdx -> build/docs/<section>/<id>.md
-    const twin = join(BUILD_DIR, DOCS_DIR, relative(DOCS_DIR, dirname(source)), `${fm.id}.md`);
-    if (!existsSync(dirname(twin))) {
-      console.warn(`[generate-api-markdown] no built output dir for ${source} — skipping.`);
-      skipped++;
-      continue;
-    }
-
-    let markdown;
-    try {
-      markdown = renderOperation(decodeOperation(fm.api), fm.title ?? fm.id);
-    } catch (error) {
-      console.warn(`[generate-api-markdown] failed to decode ${source}: ${error.message} — skipping.`);
-      skipped++;
-      continue;
-    }
-
-    if (existsSync(twin) && readFileSync(twin, 'utf8') === markdown) {
-      unchanged++;
-      continue;
-    }
-    writeFileSync(twin, markdown);
-    written++;
-  }
-
-  console.log(
-    `[generate-api-markdown] Wrote ${written} API reference twin(s) (${unchanged} already current, ${skipped} skipped) from ${sources.length} operation source(s).`,
-  );
-
-  patchComponentPages();
-}
-
-main();
diff --git a/scripts/pad-component-tags.mjs b/scripts/pad-component-tags.mjs
new file mode 100644
index 000000000..8051ba773
--- /dev/null
+++ b/scripts/pad-component-tags.mjs
@@ -0,0 +1,60 @@
+#!/usr/bin/env node
+// Keeps block-level MDX components separated by blank lines: after an opening
+// tag, before a closing tag, and around the component itself. Without them,
+// a closing tag right after a list item (or before `---`) is parsed as part of
+// that list item (or as a setext heading), and the MDX build fails.
+//
+// A component tag is a line holding only `<Name ...>` or `</Name>` (Name
+// capitalized, not self-closing). Code fences are left alone.
+//
+// Usage: node scripts/pad-component-tags.mjs [--check] FILE...
+// With --check, prints the files that need padding and exits 1 instead of writing.
+import fs from "node:fs";
+
+const OPEN = /^\s*<([A-Z][\w.]*)(\s[^<>]*)?>\s*$/;
+const CLOSE = /^\s*<\/([A-Z][\w.]*)>\s*$/;
+const FENCE = /^\s*(```|~~~)/;
+
+const isOpen = (line) => OPEN.test(line) && !line.trimEnd().endsWith("/>");
+const isClose = (line) => CLOSE.test(line);
+const isTag = (line) => isOpen(line) || isClose(line);
+
+function pad(text) {
+  const lines = text.split("\n");
+  const out = [];
+  let fence = null;
+  lines.forEach((line, i) => {
+    const m = line.match(FENCE);
+    if (fence) {
+      out.push(line);
+      if (m && m[1] === fence) fence = null;
+      return;
+    }
+    if (m) {
+      fence = m[1];
+      out.push(line);
+      return;
+    }
+    const tag = isTag(line);
+    const prev = out.length ? out[out.length - 1] : "";
+    const next = i + 1 < lines.length ? lines[i + 1] : "";
+    if (tag && prev.trim() !== "" && !isTag(prev)) out.push("");
+    out.push(line);
+    if (tag && next.trim() !== "" && !isTag(next)) out.push("");
+  });
+  return out.join("\n");
+}
+
+const args = process.argv.slice(2);
+const check = args.includes("--check");
+const changed = [];
+for (const file of args.filter((a) => a !== "--check")) {
+  const src = fs.readFileSync(file, "utf8");
+  const padded = pad(src);
+  if (padded !== src) {
+    changed.push(file);
+    if (!check) fs.writeFileSync(file, padded);
+  }
+}
+for (const file of changed) console.log(`${check ? "needs padding" : "padded"}: ${file}`);
+process.exit(check && changed.length ? 1 : 0);
diff --git a/scripts/rewrite_md_admonitions.mjs b/scripts/rewrite_md_admonitions.mjs
deleted file mode 100644
index 7350e6562..000000000
--- a/scripts/rewrite_md_admonitions.mjs
+++ /dev/null
@@ -1,197 +0,0 @@
-// @ts-check
-/**
- * Post-build step for the markdown-source feature (see rewrite_md_links.mjs).
- *
- * The docusaurus-markdown-source-plugin emits a `.md` twin of every docs page
- * but passes Docusaurus admonitions (`:::info[Title]` ... `:::`) through
- * verbatim. That syntax is not standard Markdown, so markdown previews render
- * the `:::` lines literally.
- *
- * This script rewrites admonitions INSIDE the generated `build/**\/*.md` files
- * to GitHub-style alerts (https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#alerts):
- *
- *     :::info[Title]          > [!NOTE]
- *     Body.           --->    > **Title**
- *     :::                     > Body.
- *
- * which render as colored callouts on GitHub and in common markdown viewers,
- * and degrade to plain blockquotes elsewhere. Docusaurus admonition types map
- * to the closest of GitHub's five alert types. A synthesized title gets an
- * empty quote line after it so it doesn't lazily merge into the first body
- * paragraph. GitHub only renders alerts at the top level, so nested
- * admonitions and ones indented inside list items become plain blockquotes
- * with a bold "Type: Title" label instead of a literal "[!TYPE]" marker.
- * Lines inside code fences are left untouched so documented admonition syntax
- * survives.
- *
- * It does NOT touch any source file in the repo and does NOT affect the HTML
- * site — it only post-processes generated build artifacts. It is idempotent:
- * a converted file contains no admonition lines for a re-run to match.
- *
- * Runs automatically via the `postbuild` npm lifecycle hook, so it applies in
- * CI and the production Docker build alike.
- */
-
-import { readdirSync, readFileSync, writeFileSync, existsSync } from 'node:fs';
-import { join } from 'node:path';
-
-const BUILD_DIR = 'build';
-
-// Code-fence delimiter: 3+ backticks or tildes, optionally indented.
-const FENCE_OPEN_RE = /^\s*(`{3,}|~{3,})/;
-// A closing fence is the delimiter alone — no info string after it.
-const FENCE_CLOSE_RE = /^\s*(`{3,}|~{3,})[ \t]*$/;
-// ":::type" or ":::type[Title]" (3+ colons for nesting, optional indentation).
-const OPEN_RE = /^([ \t]*):{3,}([a-zA-Z]+)(?:\[(.*)\])?[ \t]*$/;
-// Bare ":::" closing line (3+ colons, optional indentation).
-const CLOSE_RE = /^[ \t]*:{3,}[ \t]*$/;
-
-// Docusaurus admonition type -> closest GitHub alert type.
-const ALERT_TYPE = {
-  note: 'NOTE',
-  info: 'NOTE',
-  tip: 'TIP',
-  important: 'IMPORTANT',
-  warning: 'WARNING',
-  caution: 'CAUTION',
-  danger: 'CAUTION',
-};
-
-// Emoji stand-ins for the admonition icons, used where GitHub alert syntax
-// doesn't render (nested / list-indented admonitions).
-const TYPE_EMOJI = {
-  note: 'ℹ️',
-  info: 'ℹ️',
-  tip: '💡',
-  important: '❗',
-  warning: '⚠️',
-  caution: '⚠️',
-  danger: '🔥',
-};
-
-/** Convert admonition blocks to GitHub alerts; returns null when unchanged. */
-function convertAdmonitions(content) {
-  let changed = 0;
-  /** Delimiter of the code fence we're inside (e.g. "````"), or null. */
-  let fence = null;
-  /** Separate a synthesized title from the next body line with an empty
-   * quote line, so the two don't lazily merge into one paragraph. */
-  let needBlank = false;
-  /** @type {{ indent: string }[]} */
-  const stack = [];
-  const out = [];
-
-  const prefix = () => (stack[0]?.indent ?? '') + '> '.repeat(stack.length);
-
-  for (const line of content.split('\n')) {
-    if (fence) {
-      // Per CommonMark, only a bare delimiter of the same character and at
-      // least the opening length closes the fence; anything else (an inner
-      // fence of the other character, a shorter run, or a line with an info
-      // string) is fenced content.
-      const close = line.match(FENCE_CLOSE_RE);
-      if (close && close[1][0] === fence[0] && close[1].length >= fence.length) {
-        fence = null;
-      }
-    } else {
-      const open = line.match(FENCE_OPEN_RE);
-      if (open) fence = open[1];
-    }
-
-    if (!fence) {
-      const open = line.match(OPEN_RE);
-      if (open) {
-        const [, indent, type, title] = open;
-        const alert = ALERT_TYPE[type.toLowerCase()] ?? 'NOTE';
-        const topLevel = stack.length === 0 && indent === '';
-        if (needBlank) {
-          out.push(prefix().trimEnd());
-          needBlank = false;
-        }
-        stack.push({ indent });
-        if (topLevel) {
-          out.push(`${prefix()}[!${alert}]`);
-          if (title) {
-            out.push(`${prefix()}**${title}**`);
-            needBlank = true;
-          }
-        } else {
-          // GitHub only renders alerts at the top level; a nested or
-          // list-indented "[!TYPE]" shows up as literal text, so degrade to
-          // a blockquote led by the type's emoji icon and a bold label. The
-          // label keeps the original Docusaurus type name (e.g. "Danger"),
-          // matching the HTML page, since this path isn't limited to
-          // GitHub's alert set.
-          const t = type.toLowerCase();
-          const label = t[0].toUpperCase() + t.slice(1);
-          const emoji = TYPE_EMOJI[t] ?? 'ℹ️';
-          out.push(
-            `${prefix()}${emoji} **${title ? `${label}: ${title}` : label}**`,
-          );
-          needBlank = true;
-        }
-        changed++;
-        continue;
-      }
-      if (stack.length > 0 && CLOSE_RE.test(line)) {
-        stack.pop();
-        needBlank = false;
-        changed++;
-        continue; // drop the closing line entirely
-      }
-    }
-
-    if (stack.length > 0) {
-      // Blockquote the admonition body (fenced lines included — fences are
-      // valid inside blockquotes). Strip the opener's indent so the body
-      // aligns under the quote marker; blank lines become bare ">".
-      const { indent } = stack[stack.length - 1];
-      const rest = line.startsWith(indent)
-        ? line.slice(indent.length)
-        : line.trimStart();
-      if (rest === '') {
-        out.push(prefix().trimEnd());
-      } else {
-        if (needBlank) out.push(prefix().trimEnd());
-        out.push(prefix() + rest);
-      }
-      needBlank = false;
-      continue;
-    }
-
-    out.push(line);
-  }
-
-  return changed > 0 ? out.join('\n') : null;
-}
-
-/** Recursively collect every *.md file under dir. */
-function collectMd(dir) {
-  return readdirSync(dir, { recursive: true })
-    .map((p) => join(dir, String(p)))
-    .filter((p) => p.endsWith('.md'));
-}
-
-function main() {
-  if (!existsSync(BUILD_DIR)) {
-    console.warn(`[rewrite-md-admonitions] "${BUILD_DIR}/" not found — skipping.`);
-    return;
-  }
-
-  const files = collectMd(BUILD_DIR);
-  let touchedFiles = 0;
-
-  for (const file of files) {
-    const out = convertAdmonitions(readFileSync(file, 'utf8'));
-    if (out !== null) {
-      writeFileSync(file, out);
-      touchedFiles++;
-    }
-  }
-
-  console.log(
-    `[rewrite-md-admonitions] Converted admonitions in ${touchedFiles} of ${files.length} generated markdown file(s).`,
-  );
-}
-
-main();
diff --git a/scripts/rewrite_md_code_examples.mjs b/scripts/rewrite_md_code_examples.mjs
deleted file mode 100644
index 53dd4538a..000000000
--- a/scripts/rewrite_md_code_examples.mjs
+++ /dev/null
@@ -1,111 +0,0 @@
-// @ts-check
-/**
- * Post-build step for the markdown-source feature (see rewrite_md_links.mjs).
- *
- * The docusaurus-markdown-source-plugin cleaner removes unknown paired MDX
- * components together with their inner content, so the `.md` twin of any
- * page using <CodeExample> loses its code blocks entirely.
- *
- * This script regenerates the twin of every routed source that uses
- * <CodeExample>: the wrapper tags are unwrapped first — preserving the
- * fenced code, and turning a `title` attribute into a bold label — and the
- * result is passed through the upstream plugin's own cleaner, so everything
- * else is processed identically to the plugin's output. The sibling wrappers
- * (<AttributeTable>, <ExampleResponse>, <MethodTable>) are unwrapped in the
- * same step, because a page that mixes them with <CodeExample> would otherwise
- * lose their content here.
- *
- * The twin-to-source mapping comes from build/.md-source-map.json, written
- * by src/plugins/markdown-source-map during the build (route metadata is
- * only available inside Docusaurus). rewrite_md_titles.mjs deletes the map
- * once it has run.
- *
- * MUST run before the other rewrite_md_* steps — the regenerated twins
- * still need the title, link, and admonition rewrites applied.
- */
-
-import { readFileSync, writeFileSync, existsSync } from 'node:fs';
-import { join, dirname } from 'node:path';
-import { fileURLToPath } from 'node:url';
-import { createRequire } from 'node:module';
-
-const require = createRequire(import.meta.url);
-const {
-  cleanMarkdownForDisplay,
-} = require('docusaurus-markdown-source-plugin/lib/clean-markdown');
-const {
-  transformOutsideCodeFences,
-} = require('docusaurus-markdown-source-plugin/lib/fence-transform');
-
-const SITE_DIR = join(dirname(fileURLToPath(import.meta.url)), '..');
-const BUILD_DIR = join(SITE_DIR, 'build');
-const MAP_PATH = join(BUILD_DIR, '.md-source-map.json');
-
-// A page that uses <CodeExample> may also wrap other content in one of the
-// sibling components. Unwrapping only <CodeExample> would leave those for the
-// cleaner to drop, which would undo the repair scripts/generate_api_markdown.mjs
-// made earlier in `postbuild`, so every wrapper is unwrapped here.
-const UNWRAP_COMPONENTS = ['CodeExample', 'AttributeTable', 'ExampleResponse', 'MethodTable'];
-const UNWRAP_RE = new RegExp(
-  `<(${UNWRAP_COMPONENTS.join('|')})\\b([^>]*)>([\\s\\S]*?)</\\1>`,
-  'g',
-);
-const TITLE_ATTR_RE = /\btitle\s*=\s*["']([^"']*)["']/;
-const MAX_UNWRAP_PASSES = 5; // enough for any nesting these pages actually use
-
-function unwrapComponents(content) {
-  // Unwrap outside code fences only, so documentation ABOUT the components
-  // (a literal <CodeExample> inside a fence) is untouched.
-  return transformOutsideCodeFences(content, (segment) => {
-    // One pass unwraps siblings; nested wrappers need the pass to repeat,
-    // because the outer match swallows the inner tags as body text.
-    for (let pass = 0; pass < MAX_UNWRAP_PASSES; pass++) {
-      const next = segment.replace(UNWRAP_RE, (_match, _name, attrs, inner) => {
-        const title = attrs.match(TITLE_ATTR_RE);
-        const body = inner.replace(/^\s*\n/, '').replace(/\s+$/, '');
-        return title ? `**${title[1]}:**\n\n${body}` : body;
-      });
-      if (next === segment) break;
-      segment = next;
-    }
-    return segment;
-  });
-}
-
-function main() {
-  if (!existsSync(MAP_PATH)) {
-    console.warn(
-      '[rewrite-md-code-examples] build/.md-source-map.json not found — skipping.',
-    );
-    return;
-  }
-
-  const entries = JSON.parse(readFileSync(MAP_PATH, 'utf8'));
-  let touchedFiles = 0;
-
-  for (const { routePath, sourceFilePath, twinRelPath } of entries) {
-    let content;
-    try {
-      content = readFileSync(join(SITE_DIR, sourceFilePath), 'utf8');
-    } catch {
-      continue;
-    }
-    if (!/<CodeExample\b/.test(content)) continue;
-
-    const routeDir = routePath.endsWith('/')
-      ? routePath
-      : routePath.replace(/[^/]+$/, '');
-    writeFileSync(
-      join(BUILD_DIR, twinRelPath),
-      cleanMarkdownForDisplay(unwrapComponents(content), routeDir),
-      'utf8',
-    );
-    touchedFiles++;
-  }
-
-  console.log(
-    `[rewrite-md-code-examples] Regenerated ${touchedFiles} of ${entries.length} generated markdown file(s) with <CodeExample> content preserved.`,
-  );
-}
-
-main();
diff --git a/scripts/rewrite_md_links.mjs b/scripts/rewrite_md_links.mjs
deleted file mode 100644
index ec64f35d7..000000000
--- a/scripts/rewrite_md_links.mjs
+++ /dev/null
@@ -1,188 +0,0 @@
-// @ts-check
-/**
- * Post-build step for the markdown-source feature (PR #2249 / #2289).
- *
- * The docusaurus-markdown-source-plugin emits a `.md` twin of every docs page
- * (e.g. `/docs/learn/fundamentals/stellar-stack.md`) for LLM/agent consumers,
- * but it does NOT rewrite intra-doc links: relative links keep their source
- * `.mdx`/`.md` paths. Requesting those `.mdx` URLs 404s (only the `.md` twin is
- * served), so an agent that follows links falls out of "markdown mode".
- *
- * This script rewrites intra-doc links INSIDE the generated `build/**\/*.md`
- * files to the FULL canonical URL of the served `.md` twin
- * (e.g. `https://developers.stellar.org/docs/networks.md`) — self-contained, so
- * an agent can fetch a linked page directly without resolving relative paths,
- * and consistent with how `static/llms.txt` already references pages. The site
- * origin + baseUrl are read from docusaurus.config.ts (single source of truth).
- *
- * It does NOT touch any source file in the repo and does NOT affect the HTML
- * site — it only post-processes generated build artifacts. (Verified: re-running
- * it leaves every build/**\/*.html byte-identical, and full-URL links are skipped
- * as external on re-runs, so it is idempotent.)
- *
- * Correctness:
- *  - Every candidate link is resolved against the actual generated build tree; a
- *    link is rewritten only when the target `.md` genuinely exists, so we never
- *    point at a missing page. Mapping mirrors the plugin's output naming:
- *      `foo.mdx` -> `foo.md`,  `foo/README.mdx` -> `foo.md`,  `foo/README.md` -> `foo.md`.
- *  - Section-index twins: the plugin collapses `dir/README.mdx` to `dir.md`,
- *    lifting it one directory up, which desyncs links authored relative to
- *    `dir/`. For any twin that has a sibling directory of the same name we pick
- *    the resolution base (the twin's own dir vs. that sibling dir) that resolves
- *    the MOST links to real twins — a per-file vote needing no assumption about
- *    README vs. category-page conventions.
- *
- * Plain non-README `.md` links already resolve and are left untouched. Anchors
- * (`#section`) and queries (`?x=y`) are preserved; external, absolute-root and
- * anchor-only links are skipped.
- *
- * Runs automatically via the `postbuild` npm lifecycle hook (pnpm runs post
- * scripts by default), so it applies in CI and the production Docker build alike.
- */
-
-import {
-  readdirSync,
-  readFileSync,
-  writeFileSync,
-  existsSync,
-  statSync,
-} from 'node:fs';
-import { dirname, join, resolve, relative } from 'node:path';
-
-const BUILD_DIR = 'build';
-const BUILD_ROOT = resolve(BUILD_DIR);
-
-// [text](target) and ![alt](target) — capture the bare target (no spaces/titles).
-const LINK_RE = /(!?\[[^\]]*\]\()([^)\s]+)(\))/g;
-
-/** Read the canonical site origin + baseUrl from docusaurus.config.ts. */
-function readSiteConfig() {
-  const fallback = { origin: 'https://developers.stellar.org', baseUrl: '/' };
-  try {
-    const cfg = readFileSync('docusaurus.config.ts', 'utf8');
-    const url = cfg.match(/\burl:\s*["']([^"']+)["']/)?.[1];
-    const baseUrl = cfg.match(/\bbaseUrl:\s*["']([^"']+)["']/)?.[1] ?? '/';
-    if (!url) return fallback;
-    return { origin: url.replace(/\/+$/, ''), baseUrl };
-  } catch {
-    return fallback;
-  }
-}
-
-const SITE = readSiteConfig();
-
-/** Canonical full URL for a twin file, derived from its path under build/. */
-function twinUrl(twinAbs) {
-  const rel = relative(BUILD_ROOT, twinAbs); // e.g. "docs/networks.md"
-  const base = SITE.baseUrl.endsWith('/') ? SITE.baseUrl : SITE.baseUrl + '/';
-  const path = (base + rel).replace(/\/{2,}/g, '/'); // "/docs/networks.md"
-  return SITE.origin + (path.startsWith('/') ? path : '/' + path);
-}
-
-/**
- * Map an absolute source-link path to its served `.md` twin (absolute), or null
- * if this kind of path isn't something we rewrite.
- */
-function servedTwin(absSourcePath) {
-  if (/(^|\/)README\.mdx?$/i.test(absSourcePath)) {
-    // dir/README.(md|mdx) -> dir.md  (sibling named after the directory)
-    return dirname(absSourcePath) + '.md';
-  }
-  if (absSourcePath.endsWith('.mdx')) {
-    return absSourcePath.slice(0, -'.mdx'.length) + '.md';
-  }
-  return null; // plain non-README .md already resolves; leave it alone
-}
-
-/**
- * Resolve a link target against a base dir to its existing twin file.
- * Returns { suffix, twin } when the target is a rewritable doc link whose twin
- * exists on disk; otherwise null.
- */
-function resolveLink(target, baseDirAbs) {
-  // Skip external, absolute-root, protocol-relative and anchor-only links.
-  if (/^(https?:|mailto:|tel:|\/\/|\/|#)/i.test(target)) return null;
-
-  const m = target.match(/^([^#?]*)([#?].*)?$/);
-  if (!m || !m[1]) return null;
-  const linkPath = m[1];
-  const suffix = m[2] ?? '';
-
-  // Only doc-source links: any .mdx, or a README.md (which the plugin collapses).
-  const isReadme = /(^|\/)README\.mdx?$/i.test(linkPath);
-  if (!linkPath.endsWith('.mdx') && !isReadme) return null;
-
-  const twin = servedTwin(resolve(baseDirAbs, linkPath));
-  if (!twin || !existsSync(twin)) return null;
-  return { suffix, twin };
-}
-
-/** How many of a file's links resolve to real twins under a given base dir. */
-function countResolvable(content, baseDirAbs) {
-  let n = 0;
-  for (const match of content.matchAll(LINK_RE)) {
-    if (resolveLink(match[2], baseDirAbs)) n++;
-  }
-  return n;
-}
-
-function rewriteContent(content, resolveBaseAbs) {
-  let changed = 0;
-  const out = content.replace(LINK_RE, (full, open, target, close) => {
-    const r = resolveLink(target, resolveBaseAbs);
-    if (!r) return full;
-    const next = twinUrl(r.twin) + r.suffix;
-    if (next === target) return full;
-    changed++;
-    return open + next + close;
-  });
-  return { out, changed };
-}
-
-/** Recursively collect every *.md file under dir. */
-function collectMd(dir) {
-  return readdirSync(dir, { recursive: true })
-    .map((p) => join(dir, String(p)))
-    .filter((p) => p.endsWith('.md'));
-}
-
-function main() {
-  if (!existsSync(BUILD_DIR)) {
-    console.warn(`[rewrite-md-links] "${BUILD_DIR}/" not found — skipping.`);
-    return;
-  }
-
-  const files = collectMd(BUILD_DIR);
-  let touchedFiles = 0;
-  let touchedLinks = 0;
-
-  for (const file of files) {
-    const fileDirAbs = resolve(dirname(file)); // where the twin actually lives
-    const content = readFileSync(file, 'utf8');
-
-    // Default: resolve links relative to the twin's own directory.
-    let resolveBaseAbs = fileDirAbs;
-
-    // Section-index twin? (a sibling directory shares this file's basename) Then
-    // its source lived one level deeper; vote on which base resolves more links.
-    const siblingDir = resolve(file.slice(0, -'.md'.length));
-    if (existsSync(siblingDir) && statSync(siblingDir).isDirectory()) {
-      if (countResolvable(content, siblingDir) > countResolvable(content, fileDirAbs)) {
-        resolveBaseAbs = siblingDir;
-      }
-    }
-
-    const { out, changed } = rewriteContent(content, resolveBaseAbs);
-    if (changed > 0) {
-      writeFileSync(file, out);
-      touchedFiles++;
-      touchedLinks += changed;
-    }
-  }
-
-  console.log(
-    `[rewrite-md-links] Rewrote ${touchedLinks} link(s) to ${SITE.origin} across ${touchedFiles} of ${files.length} generated markdown file(s).`,
-  );
-}
-
-main();
diff --git a/scripts/rewrite_md_titles.mjs b/scripts/rewrite_md_titles.mjs
deleted file mode 100644
index eb8103301..000000000
--- a/scripts/rewrite_md_titles.mjs
+++ /dev/null
@@ -1,86 +0,0 @@
-// @ts-check
-/**
- * Post-build step for the markdown-source feature (see rewrite_md_links.mjs).
- *
- * The docusaurus-markdown-source-plugin strips YAML front matter from the
- * generated `.md` twins but never re-injects the page title, so every twin
- * starts abruptly with the first body paragraph while its HTML counterpart
- * shows the title as an H1.
- *
- * This script prepends `# {front matter title}` to each twin, using the
- * twin-to-source map written by src/plugins/markdown-source-map. Pages
- * without a front matter `title`, with `hide_title: true`, or whose body
- * already starts with an H1 are left alone. The map file is deleted
- * afterwards (this is the last step that consumes it) so it is not deployed.
- *
- * MUST run after rewrite_md_code_examples.mjs (which regenerates some twins
- * from source, discarding earlier edits) and before rewrite_md_links.mjs /
- * rewrite_md_admonitions.mjs is fine either way — the injected line is plain
- * markdown that neither step touches.
- */
-
-import {
-  readFileSync,
-  writeFileSync,
-  unlinkSync,
-  existsSync,
-} from 'node:fs';
-import { join, dirname } from 'node:path';
-import { fileURLToPath } from 'node:url';
-
-const SITE_DIR = join(dirname(fileURLToPath(import.meta.url)), '..');
-const BUILD_DIR = join(SITE_DIR, 'build');
-const MAP_PATH = join(BUILD_DIR, '.md-source-map.json');
-
-/** Extract the `title` from a source file's YAML front matter, if any. */
-function frontMatterTitle(source) {
-  const fm = source.match(/^---\r?\n([\s\S]*?)\r?\n---\r?\n/);
-  if (!fm) return null;
-  if (/^hide_title:\s*true\b/m.test(fm[1])) return null;
-  const title = fm[1].match(/^title:[ \t]*(.+?)[ \t]*$/m);
-  if (!title) return null;
-  // Strip surrounding quotes if present.
-  return title[1].replace(/^(["'])(.*)\1$/, '$2');
-}
-
-function main() {
-  if (!existsSync(MAP_PATH)) {
-    console.warn(
-      '[rewrite-md-titles] build/.md-source-map.json not found — skipping.',
-    );
-    return;
-  }
-
-  const entries = JSON.parse(readFileSync(MAP_PATH, 'utf8'));
-  let touchedFiles = 0;
-
-  for (const { sourceFilePath, twinRelPath } of entries) {
-    let source;
-    try {
-      source = readFileSync(join(SITE_DIR, sourceFilePath), 'utf8');
-    } catch {
-      continue;
-    }
-    const title = frontMatterTitle(source);
-    if (!title) continue;
-
-    const twinPath = join(BUILD_DIR, twinRelPath);
-    let twin;
-    try {
-      twin = readFileSync(twinPath, 'utf8');
-    } catch {
-      continue;
-    }
-    if (twin.startsWith('# ')) continue;
-
-    writeFileSync(twinPath, `# ${title}\n\n${twin}`, 'utf8');
-    touchedFiles++;
-  }
-
-  unlinkSync(MAP_PATH);
-  console.log(
-    `[rewrite-md-titles] Injected the page title into ${touchedFiles} of ${entries.length} generated markdown file(s).`,
-  );
-}
-
-main();
diff --git a/sds-components.css b/sds-components.css
new file mode 100644
index 000000000..de0b78fb4
--- /dev/null
+++ b/sds-components.css
@@ -0,0 +1,242 @@
+/* SDS for Mintlify: restyles Mintlify components (callouts, cards, badges, tabs, code blocks, accordions,
+   API fields) to the SDS look. Part of sds-mintlify-kit. Tokens only.
+   Selector stability legend:
+     [documented]  = element selector or data-component-part listed in Mintlify custom-scripts docs
+     [observed]    = data attribute present in the DOM but not documented
+     [tailwind]    = relies on beating a Tailwind utility class; may break on Mintlify updates
+   #body-content is a documented ID and is used to win specificity over utilities. */
+
+/* ---------- Callouts -> SDS Notification (Notification.scss) ---------- */
+/* [documented] .callout, [data-callout-type], [data-component-part="callout-icon"|"callout-content"] */
+#body-content .callout {
+  --sds-n-bg: var(--sds-clr-lilac-01);
+  --sds-n-border: var(--sds-clr-lilac-06);
+  --sds-n-icon: var(--sds-clr-lilac-09);
+  --sds-n-action: var(--sds-clr-lilac-11);
+  background-color: var(--sds-n-bg);
+  border: 1px solid var(--sds-n-border);
+  border-radius: 0.5rem;
+  padding: 0.75rem;
+  gap: 0.75rem;
+  color: var(--sds-clr-gray-11);
+  font-size: 0.875rem;
+  line-height: 1.25rem;
+}
+#body-content .callout[data-callout-type="note"] {
+  --sds-n-bg: var(--sds-clr-gray-01);
+  --sds-n-border: var(--sds-clr-gray-06);
+  --sds-n-icon: var(--sds-clr-gray-09);
+  --sds-n-action: var(--sds-clr-gray-12);
+}
+#body-content .callout[data-callout-type="tip"],
+#body-content .callout[data-callout-type="check"] {
+  --sds-n-bg: var(--sds-clr-green-01);
+  --sds-n-border: var(--sds-clr-green-06);
+  --sds-n-icon: var(--sds-clr-green-09);
+  --sds-n-action: var(--sds-clr-green-11);
+}
+#body-content .callout[data-callout-type="warning"] {
+  --sds-n-bg: var(--sds-clr-amber-01);
+  --sds-n-border: var(--sds-clr-amber-06);
+  --sds-n-icon: var(--sds-clr-amber-09);
+  --sds-n-action: var(--sds-clr-amber-11);
+}
+#body-content .callout[data-callout-type="danger"] {
+  --sds-n-bg: var(--sds-clr-red-01);
+  --sds-n-border: var(--sds-clr-red-06);
+  --sds-n-icon: var(--sds-clr-red-09);
+  --sds-n-action: var(--sds-clr-red-11);
+}
+#body-content .callout [data-component-part="callout-icon"] { margin-top: 0.125rem; width: 1rem; }
+#body-content .callout [data-component-part="callout-icon"] svg { color: var(--sds-n-icon); width: 1rem; height: 1rem; }
+#body-content .callout [data-component-part="callout-content"],
+#body-content .callout [data-component-part="callout-content"] p,
+#body-content .callout [data-component-part="callout-content"] li {
+  color: var(--sds-clr-gray-11);
+  font-size: 0.875rem;
+  line-height: 1.25rem;
+}
+#body-content .callout [data-component-part="callout-content"] strong { color: var(--sds-clr-gray-12); font-weight: var(--sds-fw-medium); }
+#body-content .callout [data-component-part="callout-content"] a {
+  color: var(--sds-n-action);
+  font-weight: var(--sds-fw-medium);
+  text-decoration: none;
+  border-bottom: 0;
+}
+#body-content .callout [data-component-part="callout-content"] a:hover { text-decoration: underline; }
+
+/* ---------- Card -> SDS Card (Card.scss) ---------- */
+/* [documented] .card, card-content-container, card-icon, card-title, card-content.
+   SDS Card is borderless (gray-01 surface); on a gray-01 page it needs the gray-06 hairline that
+   SDS Notification/Badge use, otherwise it disappears. Hover uses !important because Mintlify
+   sets hover:border-primary! [tailwind]. */
+#body-content .card {
+  background-color: var(--sds-clr-gray-01);
+  border: 1px solid var(--sds-clr-gray-06);
+  border-radius: 0.5rem;
+  box-shadow: none;
+  transition: border-color var(--sds-anim-transition-default);
+}
+#body-content .card:hover { border-color: var(--sds-clr-gray-08) !important; }
+#body-content .card [data-component-part="card-content-container"] { padding: 1.5rem; }
+#body-content .card [data-component-part="card-icon"] { width: 1.25rem; height: 1.25rem; }
+#body-content .card [data-component-part="card-icon"] svg {
+  width: 1.25rem; height: 1.25rem;
+  color: var(--sds-clr-gray-12); /* inline SVG icons (icon={<svg/>}) use currentColor */
+}
+#body-content .card [data-component-part="card-icon"] svg[style*="mask-image"] {
+  background-color: var(--sds-clr-gray-12); /* Mintlify's library icons are mask-image boxes colored by background */
+}
+#body-content .card [data-component-part="card-title"] {
+  font-size: 1rem;
+  line-height: 1.5rem;
+  font-weight: var(--sds-fw-medium);
+  color: var(--sds-clr-gray-12);
+  margin-top: 0.75rem;
+}
+#body-content .card [data-component-part="card-content"],
+#body-content .card [data-component-part="card-content"] p {
+  font-size: 0.875rem;
+  line-height: 1.25rem;
+  color: var(--sds-clr-gray-11);
+  margin-top: 0.25rem;
+}
+#body-content .card [data-component-part="card-cta"] { color: var(--sds-clr-lilac-11); font-weight: var(--sds-fw-medium); font-size: 0.875rem; }
+
+/* ---------- Badge -> SDS Badge md (Badge.scss) ---------- */
+/* [observed] span[data-badge][data-color]; Mintlify colors mapped to SDS variants */
+#body-content [data-badge] {
+  --sds-b-text: var(--sds-clr-gray-12);
+  --sds-b-bg: var(--sds-clr-gray-01);
+  --sds-b-border: var(--sds-clr-gray-06);
+  display: inline-flex;
+  align-items: center;
+  gap: 0.125rem;
+  font-family: var(--sds-ff-base);
+  font-size: 0.875rem;
+  line-height: 1.25rem;
+  font-weight: var(--sds-fw-medium);
+  letter-spacing: 0;
+  padding: 0.125rem 0.5rem;
+  border-radius: 6.25rem;
+  border: 1px solid var(--sds-b-border);
+  background-color: var(--sds-b-bg);
+  color: var(--sds-b-text);
+}
+#body-content [data-badge][data-color="blue"],
+#body-content [data-badge][data-color="purple"] {
+  --sds-b-text: var(--sds-clr-lilac-11); --sds-b-bg: var(--sds-clr-lilac-02); --sds-b-border: var(--sds-clr-lilac-06);
+}
+#body-content [data-badge][data-color="green"] {
+  --sds-b-text: var(--sds-clr-green-11); --sds-b-bg: var(--sds-clr-green-02); --sds-b-border: var(--sds-clr-green-06);
+}
+#body-content [data-badge][data-color="red"] {
+  --sds-b-text: var(--sds-clr-red-11); --sds-b-bg: var(--sds-clr-red-02); --sds-b-border: var(--sds-clr-red-06);
+}
+#body-content [data-badge][data-color="yellow"],
+#body-content [data-badge][data-color="orange"],
+#body-content [data-badge][data-color="amber"] {
+  --sds-b-text: var(--sds-clr-amber-11); --sds-b-bg: var(--sds-clr-amber-02); --sds-b-border: var(--sds-clr-amber-06);
+}
+#body-content [data-badge][data-color="gray"],
+#body-content [data-badge][data-color="grey"] {
+  --sds-b-text: var(--sds-clr-gray-11); --sds-b-bg: var(--sds-clr-gray-03); --sds-b-border: var(--sds-clr-gray-06);
+}
+
+/* ---------- Tabs ---------- */
+/* [documented] .tabs, tabs-list, tab-button; [observed] data-active */
+#body-content .tabs [data-component-part="tabs-list"] { border-bottom-color: var(--sds-clr-gray-06); gap: 1.5rem; }
+#body-content .tabs [data-component-part="tab-button"] {
+  font-size: var(--sds-fs-secondary);
+  font-weight: var(--sds-fw-medium);
+  color: var(--sds-clr-gray-11);
+  border-bottom: 2px solid transparent;
+  padding-top: 0.5rem; padding-bottom: 0.625rem;
+}
+#body-content .tabs [data-component-part="tab-button"]:hover { color: var(--sds-clr-gray-12); border-bottom-color: var(--sds-clr-gray-06); }
+#body-content .tabs [data-component-part="tab-button"][data-active="true"] { color: var(--sds-clr-gray-12); border-bottom-color: var(--sds-clr-lilac-09); }
+
+/* ---------- CodeGroup / code blocks ---------- */
+/* [documented] .code-group, code-group-tab-bar, code-block-root; tab buttons are [role=tab] [tailwind] */
+#body-content .code-group {
+  border-radius: 0.5rem;
+  border-color: var(--sds-clr-gray-06);
+  background-color: var(--sds-clr-gray-02);
+}
+#body-content .code-group [role="tab"] { font-family: var(--sds-ff-base); font-size: 0.75rem; font-weight: var(--sds-fw-medium); color: var(--sds-clr-gray-11); }
+#body-content .code-group [role="tab"][data-active],
+#body-content .code-group [role="tab"][aria-selected="true"] { color: var(--sds-clr-gray-12); }
+#body-content .code-group [role="tab"] .bg-primary { background-color: var(--sds-clr-lilac-09); }
+/* One radius for the whole code block. Mintlify rounds the outer frame (.code-block, rounded-2xl = 16px) and the
+   inner fill separately; rounding only the inner fill leaves its corners inset inside the outer outline. */
+#body-content .code-block,
+#body-content .code-group {
+  border-radius: 0.5rem;
+  border-color: var(--sds-clr-gray-06);
+  overflow: hidden;
+}
+#body-content .code-block [data-component-part="code-block-root"],
+#body-content .code-group [data-component-part="code-block-root"] { border-radius: inherit; }
+#body-content .code-group .code-block { border: 0; border-radius: 0; }
+/* Code groups round the inner fill with a layered !important that reads --rounded-xl (14px), so set the variable. */
+#body-content .code-group { --rounded-xl: 0.5rem; }
+/* github-dark ships a blue-gray #24292E, applied by Mintlify as html.dark .code-block-background { ... !important }.
+   Match the SDS dark surface; the extra #body-content specificity wins between two unlayered !important rules. */
+html.dark #body-content .code-block-background { background-color: var(--sds-clr-gray-02) !important; }
+/* The fade behind the copy button reads --fade-color-dark from an inline style (the theme's #24292E).
+   An author !important on the variable beats the inline value, so the fade matches the SDS surface. */
+#body-content [data-fade-overlay] { --fade-color-dark: var(--sds-clr-gray-02) !important; }
+
+/* ---------- Accordion ---------- */
+/* [documented] .accordion, .accordion-group, accordion-button, accordion-title, accordion-caret-right */
+#body-content .accordion,
+#body-content .accordion-group { border-radius: 0.5rem; border-color: var(--sds-clr-gray-06); background-color: var(--sds-clr-gray-01); }
+#body-content .accordion [data-component-part="accordion-button"] { padding: 0.875rem 1rem; }
+#body-content .accordion [data-component-part="accordion-button"]:hover { background-color: var(--sds-clr-gray-02); }
+#body-content .accordion [data-component-part="accordion-title"],
+#body-content .accordion [data-component-part="accordion-title"] strong {
+  color: var(--sds-clr-gray-12);
+  font-size: var(--sds-fs-secondary);
+  font-weight: var(--sds-fw-medium);
+}
+#body-content .accordion [data-component-part="accordion-caret-right"] svg { color: var(--sds-clr-gray-09); }
+
+/* ---------- Expandable ---------- */
+/* [documented] .expandable, expandable-button, expandable-content */
+#body-content details.expandable { border-radius: 0.5rem; border-color: var(--sds-clr-gray-06); }
+#body-content [data-component-part="expandable-button"] { color: var(--sds-clr-gray-11); font-size: var(--sds-fs-secondary); font-weight: var(--sds-fw-medium); }
+#body-content [data-component-part="expandable-button"]:hover { color: var(--sds-clr-gray-12); background-color: var(--sds-clr-gray-02); }
+#body-content [data-component-part="expandable-content"] { border-top-color: var(--sds-clr-gray-04); }
+
+/* ---------- ResponseField / ParamField ---------- */
+/* [observed] .primitive-param-field, field-name, field-meta, field-info-pill, field-required-pill */
+#body-content .primitive-param-field { border-bottom-color: var(--sds-clr-gray-04); }
+#body-content [data-component-part="field-name"] { color: var(--sds-clr-gray-12); font-family: var(--sds-ff-monospace); font-weight: var(--sds-fw-medium); }
+#body-content [data-component-part="field-info-pill"],
+#body-content [data-component-part="field-required-pill"] {
+  font-family: var(--sds-ff-base);
+  font-size: 0.75rem;
+  line-height: 1.125rem;
+  font-weight: var(--sds-fw-medium);
+  padding: 0.125rem 0.375rem;
+  border-radius: 6.25rem;
+  border: 1px solid var(--sds-clr-gray-06);
+  background-color: var(--sds-clr-gray-03);
+  color: var(--sds-clr-gray-11);
+}
+#body-content [data-component-part="field-required-pill"] {
+  border-color: var(--sds-clr-lilac-06);
+  background-color: var(--sds-clr-lilac-02);
+  color: var(--sds-clr-lilac-11);
+}
+
+/* ---------- Code size + callout links (follow-up) ---------- */
+/* Inconsolata runs ~17% narrower than paperMono; 15px keeps line length close to the old 14px. */
+#body-content pre code,
+#body-content pre { font-size: 0.9375rem; }
+/* Mintlify sets [&_a]:text-current! inside a Tailwind cascade layer, and a layered !important beats any
+   unlayered rule. text-fill-color paints the link text without touching color, so it sidesteps that rule. */
+#body-content .callout [data-component-part="callout-content"] a {
+  -webkit-text-fill-color: var(--sds-n-action);
+  text-decoration-color: var(--sds-n-action);
+}
diff --git a/sds-elements.css b/sds-elements.css
new file mode 100644
index 000000000..13bac1d2a
--- /dev/null
+++ b/sds-elements.css
@@ -0,0 +1,135 @@
+/* SDS for Mintlify: element styling (type scale, text colors, links, tables, inline code, monospace font).
+   Part of sds-mintlify-kit, built against @stellar/design-system 4.0.2 and Mintlify theme "sequoia".
+   Tokens only (var(--sds-*) from sds-tokens.css); no raw colors.
+   Selectors: documented Mintlify IDs (#content-area, #page-title, #navbar) plus the `.prose` content
+   wrapper. #navigation-items / #table-of-contents are observed in the DOM but not documented. */
+@import url("https://fonts.googleapis.com/css2?family=Inconsolata:wght@400;500;600;700&display=swap");
+
+/* SDS monospace everywhere. .font-mono covers API reference paths and request samples. */
+code,
+pre,
+kbd,
+.font-mono {
+  font-family: var(--sds-ff-monospace);
+}
+
+/* Page title = SDS Heading sm (2rem/2.5rem), weight medium, gray-12 */
+#content-area #page-title {
+  font-family: var(--sds-ff-heading);
+  font-size: 2rem;
+  line-height: 2.5rem;
+  font-weight: var(--sds-fw-medium);
+  letter-spacing: -0.02em;
+  color: var(--sds-clr-gray-12);
+}
+
+/* Body text: SDS site uses gray-11 base text, 16px, 1.6 line-height */
+#content-area .prose {
+  color: var(--sds-clr-gray-11);
+  font-size: var(--sds-fs-primary);
+  line-height: 1.6;
+}
+#content-area .prose p,
+#content-area .prose li {
+  color: var(--sds-clr-gray-11);
+  line-height: 1.6;
+}
+#content-area .prose strong,
+#content-area .prose b {
+  color: var(--sds-clr-gray-12);
+  font-weight: var(--sds-fw-semi-bold);
+}
+
+/* Heading scale: h2 = Heading xs (1.5rem/2rem), h3 1.25/1.75, h4 1.125/1.625, all weight medium, gray-12 */
+#content-area .prose h2,
+#content-area .prose h3,
+#content-area .prose h4,
+#content-area .prose h5 {
+  font-family: var(--sds-ff-heading);
+  font-weight: var(--sds-fw-medium);
+  color: var(--sds-clr-gray-12);
+  letter-spacing: -0.01em;
+}
+#content-area .prose h2 { font-size: 1.5rem; line-height: 2rem; margin-top: 2.5rem; margin-bottom: 1rem; }
+#content-area .prose h3 { font-size: 1.25rem; line-height: 1.75rem; margin-top: 2rem; margin-bottom: 0.75rem; }
+#content-area .prose h4 { font-size: 1.125rem; line-height: 1.625rem; }
+#content-area .prose h5 { font-size: 1rem; line-height: 1.5rem; font-weight: var(--sds-fw-semi-bold); }
+
+/* Links = SDS Link primary: lilac-11, medium, no underline; hover lilac-12 underline */
+#content-area .prose a:not([class*="card"]):not([data-component-part]):not(.sds *),
+#content-area .prose a.link:not(.sds *) {
+  color: var(--sds-clr-lilac-11);
+  font-weight: var(--sds-fw-medium);
+  text-decoration: none;
+  border-bottom: 0;
+  transition: color var(--sds-anim-transition-default);
+}
+#content-area .prose a:not([class*="card"]):not([data-component-part]):not(.sds *):hover,
+#content-area .prose a.link:not(.sds *):hover {
+  color: var(--sds-clr-lilac-12);
+  text-decoration: underline;
+  text-underline-offset: 0.2em;
+}
+
+/* Inline code = SDS Code: mono, gray-12 on gray-03 with gray-06 border, 0.25rem radius */
+#content-area .prose :not(pre) > code {
+  font-family: var(--sds-ff-monospace);
+  font-size: 0.875em;
+  font-weight: var(--sds-fw-regular);
+  color: var(--sds-clr-gray-12);
+  background-color: var(--sds-clr-gray-03);
+  border: 1px solid var(--sds-clr-gray-06);
+  border-radius: 0.25rem;
+  padding: 0.0625rem 0.25rem;
+}
+
+/* Tables: gray-06 header rule, gray-04 row rules, no vertical borders, 14px */
+#content-area .prose table {
+  font-size: var(--sds-fs-secondary);
+  line-height: 1.25rem;
+  border-collapse: collapse;
+}
+#content-area .prose thead th {
+  color: var(--sds-clr-gray-11);
+  font-weight: var(--sds-fw-medium);
+  font-size: 0.75rem;
+  line-height: 1.125rem;
+  text-transform: uppercase;
+  letter-spacing: 0.02em;
+  border-bottom: 1px solid var(--sds-clr-gray-06);
+  padding: 0.5rem 0.75rem;
+}
+#content-area .prose tbody td {
+  color: var(--sds-clr-gray-12);
+  border-bottom: 1px solid var(--sds-clr-gray-04);
+  padding: 0.625rem 0.75rem;
+  vertical-align: top;
+}
+#content-area .prose tbody tr:last-child td { border-bottom: 0; }
+
+/* Rules and quotes */
+#content-area .prose hr { border-color: var(--sds-clr-gray-04); }
+#content-area .prose blockquote {
+  border-left: 2px solid var(--sds-clr-gray-06);
+  color: var(--sds-clr-gray-11);
+  font-style: normal;
+}
+
+/* Sidebar + TOC as on SDS's docs site: 14px medium, gray-11, active gray-12.
+   IDs observed in the DOM, not in Mintlify's documented list. */
+#navigation-items a,
+#table-of-contents a {
+  font-size: var(--sds-fs-secondary);
+  font-weight: var(--sds-fw-medium);
+  color: var(--sds-clr-gray-11);
+}
+#navigation-items a:hover,
+#table-of-contents a:hover,
+#navigation-items a[aria-current],
+#table-of-contents a[aria-current] {
+  color: var(--sds-clr-gray-12);
+}
+
+/* Inline SDS icon helper for JSX icons in prose */
+.sds-inline-icon { display: inline-flex; vertical-align: -0.15em; width: 1em; height: 1em; color: var(--sds-clr-gray-12); }
+.sds-inline-icon svg { width: 100%; height: 100%; }
diff --git a/sds-icons.css b/sds-icons.css
new file mode 100644
index 000000000..16363f1a2
--- /dev/null
+++ b/sds-icons.css
@@ -0,0 +1,22 @@
+/* Generated from @stellar/design-system@4.0.2 build/assets. Do not edit by hand.
+   Regenerate: cd tools/sds && npm install && npm run build */
+[style*="/file-lines.svg"] { -webkit-mask-image: url("/img/sds-icons/icons-file-04.svg") !important; mask-image: url("/img/sds-icons/icons-file-04.svg") !important; -webkit-mask-size: contain !important; mask-size: contain !important; }
+[style*="/box-archive.svg"] { -webkit-mask-image: url("/img/sds-icons/icons-folder.svg") !important; mask-image: url("/img/sds-icons/icons-folder.svg") !important; -webkit-mask-size: contain !important; mask-size: contain !important; }
+[style*="/house.svg"] { -webkit-mask-image: url("/img/sds-icons/icons-home-05.svg") !important; mask-image: url("/img/sds-icons/icons-home-05.svg") !important; -webkit-mask-size: contain !important; mask-size: contain !important; }
+[style*="/magnifying-glass.svg"] { -webkit-mask-image: url("/img/sds-icons/icons-search-md.svg") !important; mask-image: url("/img/sds-icons/icons-search-md.svg") !important; -webkit-mask-size: contain !important; mask-size: contain !important; }
+[style*="/ellipsis-vertical.svg"] { -webkit-mask-image: url("/img/sds-icons/icons-dots-vertical.svg") !important; mask-image: url("/img/sds-icons/icons-dots-vertical.svg") !important; -webkit-mask-size: contain !important; mask-size: contain !important; }
+[style*="/angle-right.svg"] { -webkit-mask-image: url("/img/sds-icons/icons-chevron-right.svg") !important; mask-image: url("/img/sds-icons/icons-chevron-right.svg") !important; -webkit-mask-size: contain !important; mask-size: contain !important; }
+[style*="/play.svg"] { -webkit-mask-image: url("/img/sds-icons/icons-play.svg") !important; mask-image: url("/img/sds-icons/icons-play.svg") !important; -webkit-mask-size: contain !important; mask-size: contain !important; }
+[style*="/newspaper.svg"] { -webkit-mask-image: url("/img/sds-icons/icons-announcement-01.svg") !important; mask-image: url("/img/sds-icons/icons-announcement-01.svg") !important; -webkit-mask-size: contain !important; mask-size: contain !important; }
+[style*="/cube.svg"] { -webkit-mask-image: url("/img/sds-icons/icons-cube-01.svg") !important; mask-image: url("/img/sds-icons/icons-cube-01.svg") !important; -webkit-mask-size: contain !important; mask-size: contain !important; }
+[style*="/mobile-screen.svg"] { -webkit-mask-image: url("/img/sds-icons/icons-phone-01.svg") !important; mask-image: url("/img/sds-icons/icons-phone-01.svg") !important; -webkit-mask-size: contain !important; mask-size: contain !important; }
+[style*="/bolt.svg"] { -webkit-mask-image: url("/img/sds-icons/icons-zap.svg") !important; mask-image: url("/img/sds-icons/icons-zap.svg") !important; -webkit-mask-size: contain !important; mask-size: contain !important; }
+[style*="/wallet.svg"] { -webkit-mask-image: url("/img/sds-icons/icons-wallet-02.svg") !important; mask-image: url("/img/sds-icons/icons-wallet-02.svg") !important; -webkit-mask-size: contain !important; mask-size: contain !important; }
+[style*="/toolbox.svg"] { -webkit-mask-image: url("/img/sds-icons/icons-tool-02.svg") !important; mask-image: url("/img/sds-icons/icons-tool-02.svg") !important; -webkit-mask-size: contain !important; mask-size: contain !important; }
+[style*="/message.svg"] { -webkit-mask-image: url("/img/sds-icons/icons-message-square-01.svg") !important; mask-image: url("/img/sds-icons/icons-message-square-01.svg") !important; -webkit-mask-size: contain !important; mask-size: contain !important; }
+[style*="/code.svg"] { -webkit-mask-image: url("/img/sds-icons/icons-code-02.svg") !important; mask-image: url("/img/sds-icons/icons-code-02.svg") !important; -webkit-mask-size: contain !important; mask-size: contain !important; }
+[style*="/users.svg"] { -webkit-mask-image: url("/img/sds-icons/icons-users-01.svg") !important; mask-image: url("/img/sds-icons/icons-users-01.svg") !important; -webkit-mask-size: contain !important; mask-size: contain !important; }
+[style*="/discord.svg"] { -webkit-mask-image: url("/img/sds-icons/logos-discord.svg") !important; mask-image: url("/img/sds-icons/logos-discord.svg") !important; -webkit-mask-size: contain !important; mask-size: contain !important; }
+[style*="/x-twitter.svg"] { -webkit-mask-image: url("/img/sds-icons/logos-x-twitter.svg") !important; mask-image: url("/img/sds-icons/logos-x-twitter.svg") !important; -webkit-mask-size: contain !important; mask-size: contain !important; }
+[style*="/youtube.svg"] { -webkit-mask-image: url("/img/sds-icons/logos-youtube.svg") !important; mask-image: url("/img/sds-icons/logos-youtube.svg") !important; -webkit-mask-size: contain !important; mask-size: contain !important; }
+[style*="/linkedin.svg"] { -webkit-mask-image: url("/img/sds-icons/logos-linkedin.svg") !important; mask-image: url("/img/sds-icons/logos-linkedin.svg") !important; -webkit-mask-size: contain !important; mask-size: contain !important; }
diff --git a/sds-preview.mdx b/sds-preview.mdx
new file mode 100644
index 000000000..35a33ad92
--- /dev/null
+++ b/sds-preview.mdx
@@ -0,0 +1,215 @@
+---
+title: "SDS component preview"
+description: "Every component the SDS kit restyles, on one page. Check it in both light and dark themes."
+noindex: true
+---
+
+This page exists to review the SDS styling. It is not in the navigation. Body text should be SDS gray-11 at 16px, links like [this one](/docs/build) should be lilac, and `inline code` should be Inconsolata on a gray chip.
+
+## Headings
+
+### Heading 3
+
+#### Heading 4
+
+##### Heading 5
+
+All headings should be Inter at weight 500.
+
+## Callouts
+
+<Note>
+  A note callout with a [link inside it](/docs/build). Callout links use a workaround, so check that this link is lilac.
+</Note>
+
+<Info>
+  An info callout with `inline code` and a [link](/docs/build).
+</Info>
+
+<Tip>
+  A tip callout.
+</Tip>
+
+<Warning>
+  A warning callout.
+</Warning>
+
+<Check>
+  A check callout.
+</Check>
+
+<Danger>
+  A danger callout.
+</Danger>
+
+## Cards
+
+These icons are all mapped to SDS icons. The last card uses `rocket`, which is not mapped, so it should keep Mintlify's default icon for comparison.
+
+<CardGroup cols={3}>
+  <Card title="House" icon="house" href="/docs/build">
+    Mapped to SDS `home-line`.
+  </Card>
+  <Card title="Bolt" icon="bolt" href="/docs/build">
+    Mapped to SDS `zap`.
+  </Card>
+  <Card title="Wallet" icon="wallet" href="/docs/build">
+    Mapped to SDS `wallet-02`.
+  </Card>
+  <Card title="Code" icon="code" href="/docs/build">
+    Mapped to SDS `code-02`.
+  </Card>
+  <Card title="Cube" icon="cube" href="/docs/build">
+    Mapped to SDS `cube-01`.
+  </Card>
+  <Card title="Rocket (unmapped)" icon="rocket" href="/docs/build">
+    Not in the icon map. Keeps Mintlify's default.
+  </Card>
+</CardGroup>
+
+<Card title="Card without an icon" href="/docs/build">
+  A single full-width card with no icon. Hover to check the border and background change.
+</Card>
+
+## Icons
+
+Every icon the kit maps, drawn with the `<Icon>` component. Each should be an SDS line icon or logo. The last row uses `rocket`, which is not mapped, so it should look different.
+
+| Icon | Mintlify name | SDS file |
+| --- | --- | --- |
+| <Icon icon="file-lines" size={20} /> | `file-lines` | `icons/file-04` |
+| <Icon icon="box-archive" size={20} /> | `box-archive` | `icons/archive` |
+| <Icon icon="house" size={20} /> | `house` | `icons/home-line` |
+| <Icon icon="magnifying-glass" size={20} /> | `magnifying-glass` | `icons/search-md` |
+| <Icon icon="ellipsis-vertical" size={20} /> | `ellipsis-vertical` | `icons/dots-vertical` |
+| <Icon icon="angle-right" size={20} /> | `angle-right` | `icons/chevron-right` |
+| <Icon icon="play" size={20} /> | `play` | `icons/play` |
+| <Icon icon="newspaper" size={20} /> | `newspaper` | `icons/announcement-01` |
+| <Icon icon="cube" size={20} /> | `cube` | `icons/cube-01` |
+| <Icon icon="mobile-screen" size={20} /> | `mobile-screen` | `icons/phone-01` |
+| <Icon icon="bolt" size={20} /> | `bolt` | `icons/zap` |
+| <Icon icon="wallet" size={20} /> | `wallet` | `icons/wallet-02` |
+| <Icon icon="toolbox" size={20} /> | `toolbox` | `icons/tool-02` |
+| <Icon icon="message" size={20} /> | `message` | `icons/message-square-01` |
+| <Icon icon="code" size={20} /> | `code` | `icons/code-02` |
+| <Icon icon="discord" size={20} /> | `discord` | `logos/discord` |
+| <Icon icon="x-twitter" size={20} /> | `x-twitter` | `logos/x-twitter` |
+| <Icon icon="youtube" size={20} /> | `youtube` | `logos/youtube` |
+| <Icon icon="linkedin" size={20} /> | `linkedin` | `logos/linkedin` |
+| <Icon icon="rocket" size={20} /> | `rocket` | Not mapped (Mintlify default) |
+
+Inline in text: <Icon icon="house" /> house, <Icon icon="bolt" /> bolt, <Icon icon="discord" /> discord, <Icon icon="rocket" /> rocket (unmapped).
+
+## Badges
+
+<Badge color="blue">Blue</Badge> <Badge color="green">Green</Badge> <Badge color="yellow">Yellow</Badge> <Badge color="orange">Orange</Badge> <Badge color="red">Red</Badge> <Badge color="purple">Purple</Badge> <Badge color="gray">Gray</Badge>
+
+## Tabs
+
+<Tabs>
+  <Tab title="First tab">
+    Content of the first tab, with a [link](/docs/build).
+  </Tab>
+  <Tab title="Second tab">
+    Content of the second tab.
+
+    ```bash
+    stellar contract build
+    ```
+  </Tab>
+  <Tab title="Third tab">
+    Content of the third tab.
+  </Tab>
+</Tabs>
+
+## Code blocks
+
+A single code block. Code should be Inconsolata at 15px, and the dark theme background should be SDS neutral, not github-dark blue-gray.
+
+```javascript example.js
+import { Horizon, Keypair } from "@stellar/stellar-sdk";
+
+const server = new Horizon.Server("https://horizon-testnet.stellar.org");
+const pair = Keypair.random();
+
+console.log(`Public key: ${pair.publicKey()}`);
+```
+
+A code group with language tabs. The language logos keep Mintlify's style, because SDS has none.
+
+<CodeGroup>
+
+```javascript JavaScript
+const account = await server.loadAccount(pair.publicKey());
+```
+
+```python Python
+account = server.load_account(pair.public_key)
+```
+
+```rust Rust
+let account = client.get_account(&public_key).await?;
+```
+
+</CodeGroup>
+
+## Accordions
+
+<AccordionGroup>
+  <Accordion title="First accordion">
+    Accordion content with a [link](/docs/build) and `inline code`.
+  </Accordion>
+  <Accordion title="Second accordion">
+    More accordion content.
+  </Accordion>
+</AccordionGroup>
+
+<Accordion title="Standalone accordion">
+  An accordion outside a group.
+</Accordion>
+
+## API fields
+
+<ParamField path="account_id" type="string" required>
+  The account's public key. This field is required.
+</ParamField>
+
+<ParamField query="limit" type="integer" default="10">
+  The maximum number of records to return.
+</ParamField>
+
+<ResponseField name="transaction" type="object">
+  The transaction record.
+
+  <Expandable title="properties">
+    <ResponseField name="hash" type="string">
+      The transaction hash.
+    </ResponseField>
+    <ResponseField name="ledger" type="integer">
+      The ledger the transaction was included in.
+    </ResponseField>
+  </Expandable>
+</ResponseField>
+
+## Tables
+
+| Network | Horizon URL | Passphrase |
+| --- | --- | --- |
+| Mainnet | `https://horizon.stellar.org` | Public Global Stellar Network ; September 2015 |
+| Testnet | `https://horizon-testnet.stellar.org` | Test SDF Network ; September 2015 |
+| Futurenet | `https://horizon-futurenet.stellar.org` | Test SDF Future Network ; October 2022 |
+
+## Lists, quotes, and rules
+
+- A **bold** item and an *italic* item
+- An item with a [link](/docs/build)
+  - A nested item
+
+1. First step
+2. Second step
+
+> A blockquote. It should use SDS grays.
+
+---
+
+The line above is a horizontal rule.
diff --git a/sds-tokens.css b/sds-tokens.css
new file mode 100644
index 000000000..3447da9d7
--- /dev/null
+++ b/sds-tokens.css
@@ -0,0 +1,10 @@
+/* Generated from @stellar/design-system@4.0.2 build/styles.min.css. Do not edit by hand.
+   Regenerate: cd tools/sds && npm install && npm run build */
+:root {--sds-version: "4.0.2"
+}
+:root {--sds-fs-primary: 16px;--sds-fs-secondary: 14px;--sds-fw-light: 300;--sds-fw-regular: 400;--sds-fw-medium: 500;--sds-fw-semi-bold: 600;--sds-fw-bold: 700;--sds-ff-heading: "Inter", sans-serif;--sds-ff-base: "Inter", sans-serif;--sds-ff-monospace: "Inconsolata", monospace;--sds-z-index-tooltip: 20;--sds-z-index-modal: 30;--sds-opacity-disabled-button: 0.6;--sds-window-width-min: 360px;--sds-window-width-max: 1296px;--sds-window-height-min: 100vh;--sds-anim-transition-default: cubic-bezier(0.65, 0.05, 0.36, 1) 100ms;--sds-input-color-border-default: var(--sds-clr-gray-06);--sds-input-color-border-default-hover: var(--sds-clr-gray-06);--sds-input-color-border-default-focus: var(--sds-clr-gray-06);--sds-input-color-border-error: var(--sds-clr-red-06);--sds-input-color-border-error-hover: var(--sds-clr-red-06);--sds-input-color-border-error-focus: var(--sds-clr-red-06);--sds-input-color-border-disabled: var(--sds-clr-gray-07);--sds-input-color-border-disabled-hover: var(--sds-clr-gray-07);--sds-input-color-border-disabled-focus: var(--sds-clr-gray-07);--sds-input-color-background-default: var(--sds-clr-gray-01);--sds-input-color-background-error: var(--sds-clr-gray-01);--sds-input-color-background-disabled: var(--sds-clr-gray-03);--sds-input-color-text-default: var(--sds-clr-gray-12);--sds-input-color-text-placeholder: var(--sds-clr-gray-11);--sds-input-color-text-disabled: var(--sds-clr-gray-11);--sds-input-color-icon: var(--sds-clr-gray-11);--sds-input-box-shadow-color-default: var(--sds-clr-gray-04);--sds-input-box-shadow-color-error: var(--sds-clr-red-04)
+}
+:root {--sds-clr-gray-01: #fcfcfc;--sds-clr-gray-02: #f8f8f8;--sds-clr-gray-03: #f3f3f3;--sds-clr-gray-04: #ededed;--sds-clr-gray-05: #e8e8e8;--sds-clr-gray-06: #e2e2e2;--sds-clr-gray-07: #dbdbdb;--sds-clr-gray-08: #c7c7c7;--sds-clr-gray-09: #8f8f8f;--sds-clr-gray-10: #858585;--sds-clr-gray-11: #6f6f6f;--sds-clr-gray-12: #171717;--sds-clr-lilac-01: #fdfcfe;--sds-clr-lilac-02: #fbfaff;--sds-clr-lilac-03: #f5f2ff;--sds-clr-lilac-04: #ede9fe;--sds-clr-lilac-05: #e4defc;--sds-clr-lilac-06: #d7cff9;--sds-clr-lilac-07: #c4b8f3;--sds-clr-lilac-08: #aa99ec;--sds-clr-lilac-09: #6e56cf;--sds-clr-lilac-10: #644fc1;--sds-clr-lilac-11: #5746af;--sds-clr-lilac-12: #20134b;--sds-clr-base-00: #ffffff;--sds-clr-base-01: #000000;--sds-overlay-01: rgba(0, 0, 0, 0.1);--sds-overlay-02: rgba(0, 0, 0, 0.2);--sds-overlay-03: rgba(0, 0, 0, 0.3);--sds-overlay-04: rgba(0, 0, 0, 0.4);--sds-overlay-05: rgba(0, 0, 0, 0.5);--sds-overlay-06: rgba(0, 0, 0, 0.6);--sds-overlay-07: rgba(0, 0, 0, 0.7);--sds-overlay-08: rgba(0, 0, 0, 0.8);--sds-overlay-09: rgba(0, 0, 0, 0.9);--sds-overlay-10: rgba(0, 0, 0, 1);--sds-clr-green-01: #fbfefc;--sds-clr-green-02: #f2fcf5;--sds-clr-green-03: #e9f9ee;--sds-clr-green-04: #ddf3e4;--sds-clr-green-05: #ccebd7;--sds-clr-green-06: #b4dfc4;--sds-clr-green-07: #92ceac;--sds-clr-green-08: #5bb98c;--sds-clr-green-09: #30a46c;--sds-clr-green-10: #299764;--sds-clr-green-11: #18794e;--sds-clr-green-12: #153226;--sds-clr-amber-01: #fefdfb;--sds-clr-amber-02: #fff9ed;--sds-clr-amber-03: #fff4d5;--sds-clr-amber-04: #ffecbc;--sds-clr-amber-05: #ffe3a2;--sds-clr-amber-06: #ffd386;--sds-clr-amber-07: #f3ba63;--sds-clr-amber-08: #ee9d2b;--sds-clr-amber-09: #ffb224;--sds-clr-amber-10: #ffa01c;--sds-clr-amber-11: #ad5700;--sds-clr-amber-12: #4e2009;--sds-clr-red-01: #fffcfc;--sds-clr-red-02: #fff8f8;--sds-clr-red-03: #ffefef;--sds-clr-red-04: #ffe5e5;--sds-clr-red-05: #fdd8d8;--sds-clr-red-06: #f9c6c6;--sds-clr-red-07: #f3aeaf;--sds-clr-red-08: #eb9091;--sds-clr-red-09: #e5484d;--sds-clr-red-10: #dc3d43;--sds-clr-red-11: #cd2b31;--sds-clr-red-12: #381316;--sds-clr-white: #ffffff;--sds-clr-gold-01: #fdfdf9;--sds-clr-gold-02: #fffce8;--sds-clr-gold-03: #fffbd1;--sds-clr-gold-04: #fff8bb;--sds-clr-gold-05: #fef2a4;--sds-clr-gold-06: #f9e68c;--sds-clr-gold-07: #efd36c;--sds-clr-gold-08: #ebbc00;--sds-clr-gold-09: #fdda24;--sds-clr-gold-10: #f7ce00;--sds-clr-gold-11: #946800;--sds-clr-gold-12: #35290f;--sds-clr-navy-01: #fdfdfe;--sds-clr-navy-02: #f8faff;--sds-clr-navy-03: #f0f4ff;--sds-clr-navy-04: #e6edfe;--sds-clr-navy-05: #d9e2fc;--sds-clr-navy-06: #c6d4f9;--sds-clr-navy-07: #aec0f5;--sds-clr-navy-08: #8da4ef;--sds-clr-navy-09: #3e63dd;--sds-clr-navy-10: #3a5ccc;--sds-clr-navy-11: #3451b2;--sds-clr-navy-12: #101d46;--sds-clr-teal-01: #fafdfe;--sds-clr-teal-02: #f2fcfd;--sds-clr-teal-03: #e7f9fb;--sds-clr-teal-04: #d8f3f6;--sds-clr-teal-05: #c4eaef;--sds-clr-teal-06: #aadee6;--sds-clr-teal-07: #84cdda;--sds-clr-teal-08: #3db9cf;--sds-clr-teal-09: #05a2c2;--sds-clr-teal-10: #0894b3;--sds-clr-teal-11: #0c7792;--sds-clr-teal-12: #04313c;--sds-clr-mint-01: #f9fefd;--sds-clr-mint-02: #effefa;--sds-clr-mint-03: #e1fbf4;--sds-clr-mint-04: #d2f7ed;--sds-clr-mint-05: #c0efe3;--sds-clr-mint-06: #a5e4d4;--sds-clr-mint-07: #7dd4c0;--sds-clr-mint-08: #40c4aa;--sds-clr-mint-09: #70e1c8;--sds-clr-mint-10: #69d9c1;--sds-clr-mint-11: #147d6f;--sds-clr-mint-12: #09342e;--sds-clr-lime-01: #fcfdfa;--sds-clr-lime-02: #f7fcf0;--sds-clr-lime-03: #eefadc;--sds-clr-lime-04: #e4f7c7;--sds-clr-lime-05: #d7f2b0;--sds-clr-lime-06: #c9e894;--sds-clr-lime-07: #b1d16a;--sds-clr-lime-08: #94ba2c;--sds-clr-lime-09: #99d52a;--sds-clr-lime-10: #93c926;--sds-clr-lime-11: #5d770d;--sds-clr-lime-12: #263209;--sds-clr-pink-01: #fffcfe;--sds-clr-pink-02: #fff7fc;--sds-clr-pink-03: #feeef8;--sds-clr-pink-04: #fce5f3;--sds-clr-pink-05: #f9d8ec;--sds-clr-pink-06: #f3c6e2;--sds-clr-pink-07: #ecadd4;--sds-clr-pink-08: #e38ec3;--sds-clr-pink-09: #d6409f;--sds-clr-pink-10: #d23197;--sds-clr-pink-11: #cd1d8d;--sds-clr-pink-12: #3b0a2a;--sds-clr-tooltip-background: #ededed;--sds-clr-tooltip-title: #161616;--sds-clr-tooltip-text: #505050;--sds-clr-tooltip-contrast-background: #171717;--sds-clr-tooltip-contrast-title: #fcfcfc;--sds-clr-tooltip-contrast-text: #c7c7c7
+}
+html.dark, html[data-theme="dark"] {--sds-clr-gray-01: #161616;--sds-clr-gray-02: #1c1c1c;--sds-clr-gray-03: #232323;--sds-clr-gray-04: #282828;--sds-clr-gray-05: #2e2e2e;--sds-clr-gray-06: #343434;--sds-clr-gray-07: #3e3e3e;--sds-clr-gray-08: #505050;--sds-clr-gray-09: #707070;--sds-clr-gray-10: #7e7e7e;--sds-clr-gray-11: #a0a0a0;--sds-clr-gray-12: #ededed;--sds-clr-lilac-01: #17151f;--sds-clr-lilac-02: #1c172b;--sds-clr-lilac-03: #251e40;--sds-clr-lilac-04: #2c2250;--sds-clr-lilac-05: #32275f;--sds-clr-lilac-06: #392c72;--sds-clr-lilac-07: #443592;--sds-clr-lilac-08: #5842c3;--sds-clr-lilac-09: #6e56cf;--sds-clr-lilac-10: #7c66dc;--sds-clr-lilac-11: #9e8cfc;--sds-clr-lilac-12: #f1eefe;--sds-clr-base-00: #000000;--sds-clr-base-01: #ffffff;--sds-overlay-01: rgba(255, 255, 255, 0.1);--sds-overlay-02: rgba(255, 255, 255, 0.2);--sds-overlay-03: rgba(255, 255, 255, 0.3);--sds-overlay-04: rgba(255, 255, 255, 0.4);--sds-overlay-05: rgba(255, 255, 255, 0.5);--sds-overlay-06: rgba(255, 255, 255, 0.6);--sds-overlay-07: rgba(255, 255, 255, 0.7);--sds-overlay-08: rgba(255, 255, 255, 0.8);--sds-overlay-09: rgba(255, 255, 255, 0.9);--sds-overlay-10: rgba(255, 255, 255, 1);--sds-clr-green-01: #0d1912;--sds-clr-green-02: #0c1f17;--sds-clr-green-03: #0f291e;--sds-clr-green-04: #113123;--sds-clr-green-05: #133929;--sds-clr-green-06: #164430;--sds-clr-green-07: #1b543a;--sds-clr-green-08: #236e4a;--sds-clr-green-09: #30a46c;--sds-clr-green-10: #3cb179;--sds-clr-green-11: #4cc38a;--sds-clr-green-12: #e5fbeb;--sds-clr-amber-01: #1f1300;--sds-clr-amber-02: #271700;--sds-clr-amber-03: #341c00;--sds-clr-amber-04: #3f2200;--sds-clr-amber-05: #4a2900;--sds-clr-amber-06: #573300;--sds-clr-amber-07: #693f05;--sds-clr-amber-08: #824e00;--sds-clr-amber-09: #ffb224;--sds-clr-amber-10: #ffcb47;--sds-clr-amber-11: #f1a10d;--sds-clr-amber-12: #fef3dd;--sds-clr-red-01: #1f1315;--sds-clr-red-02: #291415;--sds-clr-red-03: #3c181a;--sds-clr-red-04: #481a1d;--sds-clr-red-05: #541b1f;--sds-clr-red-06: #671e22;--sds-clr-red-07: #822025;--sds-clr-red-08: #aa2429;--sds-clr-red-09: #e5484d;--sds-clr-red-10: #f2555a;--sds-clr-red-11: #ff6369;--sds-clr-red-12: #feecee;--sds-clr-white: #ffffff;--sds-clr-gold-01: #1c1500;--sds-clr-gold-02: #221a00;--sds-clr-gold-03: #2c2100;--sds-clr-gold-04: #352800;--sds-clr-gold-05: #3e3000;--sds-clr-gold-06: #493c00;--sds-clr-gold-07: #594a05;--sds-clr-gold-08: #705e00;--sds-clr-gold-09: #fdda24;--sds-clr-gold-10: #ffef5c;--sds-clr-gold-11: #f0c000;--sds-clr-gold-12: #fffad1;--sds-clr-navy-01: #131620;--sds-clr-navy-02: #15192d;--sds-clr-navy-03: #192140;--sds-clr-navy-04: #1c274f;--sds-clr-navy-05: #1f2c5c;--sds-clr-navy-06: #22346e;--sds-clr-navy-07: #273e89;--sds-clr-navy-08: #2f4eb2;--sds-clr-navy-09: #3e63dd;--sds-clr-navy-10: #5373e7;--sds-clr-navy-11: #849dff;--sds-clr-navy-12: #eef1fd;--sds-clr-teal-01: #07191d;--sds-clr-teal-02: #061e24;--sds-clr-teal-03: #072830;--sds-clr-teal-04: #07303b;--sds-clr-teal-05: #073844;--sds-clr-teal-06: #064150;--sds-clr-teal-07: #045063;--sds-clr-teal-08: #00647d;--sds-clr-teal-09: #05a2c2;--sds-clr-teal-10: #00b1cc;--sds-clr-teal-11: #00c2d7;--sds-clr-teal-12: #e1f8fa;--sds-clr-mint-01: #081917;--sds-clr-mint-02: #05201e;--sds-clr-mint-03: #052926;--sds-clr-mint-04: #04312c;--sds-clr-mint-05: #033a34;--sds-clr-mint-06: #01453d;--sds-clr-mint-07: #00564a;--sds-clr-mint-08: #006d5b;--sds-clr-mint-09: #70e1c8;--sds-clr-mint-10: #95f3d9;--sds-clr-mint-11: #25d0ab;--sds-clr-mint-12: #e7fcf7;--sds-clr-lime-01: #141807;--sds-clr-lime-02: #181d08;--sds-clr-lime-03: #1e260d;--sds-clr-lime-04: #252e0f;--sds-clr-lime-05: #2b3711;--sds-clr-lime-06: #344213;--sds-clr-lime-07: #415215;--sds-clr-lime-08: #536716;--sds-clr-lime-09: #99d52a;--sds-clr-lime-10: #c4f042;--sds-clr-lime-11: #87be22;--sds-clr-lime-12: #effbdd;--sds-clr-pink-01: #1f121b;--sds-clr-pink-02: #271421;--sds-clr-pink-03: #3a182f;--sds-clr-pink-04: #451a37;--sds-clr-pink-05: #501b3f;--sds-clr-pink-06: #601d48;--sds-clr-pink-07: #7a1d5a;--sds-clr-pink-08: #a71873;--sds-clr-pink-09: #d6409f;--sds-clr-pink-10: #e34ba9;--sds-clr-pink-11: #f65cb6;--sds-clr-pink-12: #feebf7;--sds-clr-tooltip-background: #171717;--sds-clr-tooltip-title: #fcfcfc;--sds-clr-tooltip-text: #c7c7c7;--sds-clr-tooltip-contrast-background: #ededed;--sds-clr-tooltip-contrast-title: #161616;--sds-clr-tooltip-contrast-text: #505050
+}
diff --git a/docs/platforms/anchor-platform/admin-guide/component/security/api_key.mdx b/snippets/anchor-platform/api_key.mdx
similarity index 89%
rename from docs/platforms/anchor-platform/admin-guide/component/security/api_key.mdx
rename to snippets/anchor-platform/api_key.mdx
index cc5ce4d80..48bae6be6 100644
--- a/docs/platforms/anchor-platform/admin-guide/component/security/api_key.mdx
+++ b/snippets/anchor-platform/api_key.mdx
@@ -1,14 +1,14 @@
 To enable API key authentication, modify your `dev.env` file:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 # dev.env
 PLATFORM_API_AUTH_TYPE=api_key
 # Will be used as API key
 SECRET_PLATFORM_API_AUTH_SECRET="your API key that business server will use"
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Once enabled, all requests must include a valid `X-Api-Key` header, set to the configured API key.
diff --git a/docs/platforms/anchor-platform/admin-guide/component/rpc/error.mdx b/snippets/anchor-platform/error.mdx
similarity index 98%
rename from docs/platforms/anchor-platform/admin-guide/component/rpc/error.mdx
rename to snippets/anchor-platform/error.mdx
index 27746e6f0..7943bed97 100644
--- a/docs/platforms/anchor-platform/admin-guide/component/rpc/error.mdx
+++ b/snippets/anchor-platform/error.mdx
@@ -9,8 +9,8 @@
 
 </div>
 
-:::tip
+<Tip>
 
 We will also reference a `$transaction_id` variable. This is an identification of transaction that is being returned from the Anchor Platform on an withdrawal or deposit start request. You can obtain the transaction ID by connecting the test wallet to your local Anchor Platform instance.
 
-:::
+</Tip>
diff --git a/docs/platforms/anchor-platform/admin-guide/component/security/jwt.mdx b/snippets/anchor-platform/jwt.mdx
similarity index 92%
rename from docs/platforms/anchor-platform/admin-guide/component/security/jwt.mdx
rename to snippets/anchor-platform/jwt.mdx
index e2160a7ce..42bc87929 100644
--- a/docs/platforms/anchor-platform/admin-guide/component/security/jwt.mdx
+++ b/snippets/anchor-platform/jwt.mdx
@@ -1,15 +1,15 @@
 To enable JWT authentication, modify your `dev.env` file:
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 # dev.env
 PLATFORM_API_AUTH_TYPE=jwt
 # Will be used to sign the JWT token
 SECRET_PLATFORM_API_AUTH_SECRET="your secret that business server will use"
 ```
 
-</CodeExample>
+</CodeGroup>
 
 Anchor Platform uses the HMAC SHA-256 (HS256) algorithm to sign JWT tokens. Ensure that `SECRET_PLATFORM_API_AUTH_SECRET` is at least 32 characters long for security.
 
diff --git a/docs/platforms/anchor-platform/admin-guide/component/observer/observer.mdx b/snippets/anchor-platform/observer.mdx
similarity index 89%
rename from docs/platforms/anchor-platform/admin-guide/component/observer/observer.mdx
rename to snippets/anchor-platform/observer.mdx
index 338edf702..7dfa26b0b 100644
--- a/docs/platforms/anchor-platform/admin-guide/component/observer/observer.mdx
+++ b/snippets/anchor-platform/observer.mdx
@@ -1,28 +1,27 @@
-Using the Payment Observer allows you to delegate this step to the Anchor Platform. To enable the Payment Observer, use the `--stellar-observer` flag in the command section of the [compose file](../../getting-started.mdx#configuration).
+Using the Payment Observer allows you to delegate this step to the Anchor Platform. To enable the Payment Observer, use the `--stellar-observer` flag in the command section of the [compose file](/docs/platforms/anchor-platform/admin-guide/getting-started#configuration).
 
 The Payment Observer will track all transactions sent to the distribution account. When the transaction with the expected memo is detected in the network, the status will automatically change to `pending_anchor` and event will be the emitted (if Kafka is used).
 
 In order to update the transaction's statuses, the observer makes corresponding JSON-RPC requests to the platform. It should use the following URL.
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 # dev.env
 PLATFORM_API_BASE_URL=http://platform-server:8085
 ```
 
-</CodeExample>
+</CodeGroup>
 
-:::caution
+<Warning>
 
 The Payment Observer won't validate the amounts. It's your responsibility to verify that the amount sent by the user is correct.
 
-:::
-
-:::info
+</Warning>
+<Info>
 
 If you already have a system that monitors payments, make sure that the logic of the system matches the description below:
 
 First, wait for the transaction to be included in the ledger (using an SDK). This transaction must have the expected memo and destination address (distribution account). Once this transaction has been detected and verified, notify the user that the funds have been received using the [notify_onchain_funds_received](#funds-received-1) JSON-RPC request.
 
-:::
+</Info>
diff --git a/snippets/anchor-platform/request.mdx b/snippets/anchor-platform/request.mdx
new file mode 100644
index 000000000..3395b3b07
--- /dev/null
+++ b/snippets/anchor-platform/request.mdx
@@ -0,0 +1,33 @@
+The Request object must contain the following attributes:
+
+<ParamField body="jsonrpc" type="string">
+
+A String specifying the version of the JSON-RPC protocol. MUST be exactly "2.0"
+
+</ParamField>
+
+<ParamField body="method" type="string">
+
+A String containing the name of the method to be invoked. List of available methods you can see in [JSON-RPC Methods](/docs/platforms/anchor-platform/api-reference/platform/rpc/methods)
+
+</ParamField>
+
+<ParamField body="params" type="object">
+
+A Structured value that holds the parameter values, corresponding to method call, to be used during the invocation of the method
+
+</ParamField>
+
+<ParamField body="id" type="string">
+
+An identifier established by the client. The Server will reply with the same value in the Response object
+
+</ParamField>
+
+<Tip>
+
+It's possible to provide multiple updates in a single JSON-RPC request (by placing multiple JSON-RPC request objects). When an update is done in this way, all updates will be done sequentially.
+
+Most importantly, each JSON-RPC request is not atomic. If one update fails, all previous updates WILL be applied and all subsequent updates WILL be processed and applied as well.
+
+</Tip>
diff --git a/snippets/anchor-platform/response.mdx b/snippets/anchor-platform/response.mdx
new file mode 100644
index 000000000..b1797c058
--- /dev/null
+++ b/snippets/anchor-platform/response.mdx
@@ -0,0 +1,51 @@
+The Response is expressed as a single JSON Object, with the following attributes:
+
+<ResponseField name="jsonrpc" type="string">
+
+A String specifying the version of the JSON-RPC protocol. It's set to "2.0"
+
+</ResponseField>
+
+<ResponseField name="result" type="object">
+
+A Structured value that holds the updated transaction details
+
+</ResponseField>
+
+<ResponseField name="id" type="string">
+
+An identifier sent by the client
+
+</ResponseField>
+
+<ResponseField name="error" type="object">
+
+A Structured value that holds the error details
+
+  <Expandable title="error properties">
+    <ResponseField name="id" type="string">
+
+      Unique id of the transaction for which an error occurred
+
+    </ResponseField>
+
+    <ResponseField name="code" type="number">
+
+      A number that indicates the error type that occurred. Please see a list of [error codes](#error-codes) below
+
+    </ResponseField>
+
+    <ResponseField name="message" type="string">
+
+      A String providing a short description of the error
+
+    </ResponseField>
+
+    <ResponseField name="data" type="string">
+
+      A primitive or structured value that contains additional information about the error
+
+    </ResponseField>
+
+  </Expandable>
+</ResponseField>
diff --git a/docs/platforms/anchor-platform/admin-guide/component/rpc/rpc.mdx b/snippets/anchor-platform/rpc.mdx
similarity index 92%
rename from docs/platforms/anchor-platform/admin-guide/component/rpc/rpc.mdx
rename to snippets/anchor-platform/rpc.mdx
index f00b8ee7f..4d7bf7036 100644
--- a/docs/platforms/anchor-platform/admin-guide/component/rpc/rpc.mdx
+++ b/snippets/anchor-platform/rpc.mdx
@@ -1,8 +1,8 @@
 Before making JSON-RPC requests, let's first create a template for making a request to the Anchor Platform.
 
-<CodeExample>
+<CodeGroup>
 
-```bash
+```bash bash
 # call-json-rpc.sh
 #!/usr/bin/env bash
 
@@ -12,6 +12,6 @@ curl localhost:8085 \
     --data "@$1"
 ```
 
-</CodeExample>
+</CodeGroup>
 
 This small script will make a JSON-RPC request to the Anchor Platform hosted on the default port (8085). JSON transaction data stored in the provided file will be used as body (requests must be an array).
diff --git a/docs/platforms/anchor-platform/admin-guide/component/security/security.mdx b/snippets/anchor-platform/security.mdx
similarity index 91%
rename from docs/platforms/anchor-platform/admin-guide/component/security/security.mdx
rename to snippets/anchor-platform/security.mdx
index 76a3832c3..495da3799 100644
--- a/docs/platforms/anchor-platform/admin-guide/component/security/security.mdx
+++ b/snippets/anchor-platform/security.mdx
@@ -1,11 +1,10 @@
-:::caution
+<Warning>
 
 By default, the Platform API's endpoints such as `GET /transactions` and `GET /transactions/:id` are not protected, and are accessible by anyone who has access to the server, including wallet applications.
 
-:::
-
-:::info
+</Warning>
+<Info>
 
 It's recommended to keep Platform server accessible only from the private network. However, you may want to add additional layer of protection via securing the API.
 
-:::
+</Info>
diff --git a/snippets/storage-diagram.jsx b/snippets/storage-diagram.jsx
new file mode 100644
index 000000000..7f7af8d2b
--- /dev/null
+++ b/snippets/storage-diagram.jsx
@@ -0,0 +1,1869 @@
+// Animated Soroban storage diagrams, ported from the Docusaurus site (src/components/StorageStrategies).
+// Mintlify snippets allow no imports or CSS files: styles ship in a <style> element and hooks are globals.
+export const StorageDiagram = ({ n }) => {
+  const CSS = `
+/* Animated storage diagrams — ported from the Soroban storage field guide.
+   All rules are scoped under .ssd; tier colors: amber=instance, teal=persistent, rose=temporary. */
+
+.ssd {
+  --ssd-page-bg: #ffffff;
+  --accent: #a96a12;
+  --amber: #a96a12;
+  --amber-soft: #f0e2cb;
+  --card-2: #ebf0ee;
+  --danger: #b23a50;
+  --ink: #1c2429;
+  --line: #d8e0dd;
+  --line-strong: #b9c6c2;
+  --muted: #55666a;
+  --rose: #b23a50;
+  --rose-soft: #f2dbdf;
+  --teal: #0e7d6f;
+  --teal-soft: #d2e9e4;
+}
+
+html.dark .ssd,
+[data-theme="dark"] .ssd {
+  --ssd-page-bg: #0e0d0b;
+  --accent: #e3a44b;
+  --amber: #e3a44b;
+  --amber-soft: #3a2f1b;
+  --card-2: #202a2f;
+  --danger: #e4677a;
+  --ink: #e8edeb;
+  --line: #2a363b;
+  --line-strong: #3d4c52;
+  --muted: #93a5a2;
+  --rose: #e4677a;
+  --rose-soft: #3d2027;
+  --teal: #48bfad;
+  --teal-soft: #16352f;
+}
+
+.ssd {
+  position: relative;
+  margin: 1.4em 0 1.6em;
+  padding-top: 6px;
+  overflow-x: auto;
+}
+.ssd svg {
+  display: block;
+  width: 100%;
+  height: auto;
+  min-width: 560px;
+}
+.ssd .caption {
+  font-family: inherit;
+  font-size: 0.78rem;
+  color: var(--muted);
+  text-align: center;
+  margin: 10px 0 2px;
+}
+.ssd .diagram-controls {
+  display: flex;
+  justify-content: flex-end;
+  flex-wrap: wrap;
+  gap: 6px;
+  margin-bottom: 4px;
+}
+#d0 {
+  margin-top: 0.8em;
+}
+#d0 .diagram-controls {
+  margin-bottom: 0;
+}
+.ssd .replay,
+.ssd .restore {
+  border: 1px solid var(--line-strong);
+  background: var(--card-2);
+  color: var(--muted);
+  border-radius: 7px;
+  font-family: inherit;
+  font-size: 0.72rem;
+  font-weight: 650;
+  padding: 4px 10px;
+  cursor: pointer;
+}
+.ssd .replay:hover,
+.ssd .restore:hover {
+  color: var(--ink);
+  border-color: var(--accent);
+}
+.ssd .replay:focus-visible,
+.ssd .restore:focus-visible {
+  outline: 2px solid var(--accent);
+  outline-offset: 2px;
+}
+.ssd .restore[aria-pressed="true"] {
+  color: var(--ink);
+  border-color: var(--teal);
+  background: var(--teal-soft);
+}
+
+/* SVG vocabulary — every diagram is built from these */
+.ssd svg text {
+  font-family: inherit;
+  fill: var(--muted);
+}
+.ssd svg .lbl {
+  font-size: 11px;
+  font-weight: 600;
+}
+.ssd svg .lbl-s {
+  font-size: 9.5px;
+  font-weight: 550;
+}
+.ssd svg .mono {
+  font-family: ui-monospace, SFMono-Regular, Menlo, Consolas, monospace;
+}
+.ssd svg .cell {
+  fill: var(--card-2);
+  stroke: var(--line-strong);
+  stroke-width: 1.2;
+  rx: 5;
+}
+.ssd svg .cell-inst {
+  fill: var(--amber-soft);
+  stroke: var(--amber);
+}
+.ssd svg .cell-pers {
+  fill: var(--teal-soft);
+  stroke: var(--teal);
+}
+.ssd svg .cell-temp {
+  fill: var(--rose-soft);
+  stroke: var(--rose);
+}
+.ssd svg .wire {
+  stroke: var(--line-strong);
+  stroke-width: 1.2;
+  fill: none;
+}
+.ssd svg .dashed {
+  stroke-dasharray: 4 3;
+}
+.ssd svg .ttl-track {
+  fill: var(--line);
+  rx: 2;
+}
+.ssd svg .ttl-fill-pers {
+  fill: var(--teal);
+  rx: 2;
+}
+.ssd svg .ttl-fill-temp {
+  fill: var(--rose);
+  rx: 2;
+}
+.ssd svg .ttl-fill-inst {
+  fill: var(--amber);
+  rx: 2;
+}
+.ssd svg .dot {
+  fill: var(--ink);
+}
+.ssd svg .hatch {
+  stroke: var(--muted);
+  stroke-width: 1;
+}
+
+/* Animations: only run when .diagram has .play */
+.ssd .anim {
+  animation-play-state: paused !important;
+}
+.ssd.play .anim {
+  animation-play-state: running !important;
+}
+@media (prefers-reduced-motion: reduce) {
+  .ssd .anim {
+    animation-duration: 0.001s !important;
+    animation-delay: 0s !important;
+    animation-iteration-count: 1 !important;
+  }
+}
+/* Without JS, .play never lands and several elements' base opacity: 0 would
+   never be revealed. Jump every animation straight to its settled final frame
+   — the informative resting state — instead of freezing on frame 0. */
+@media (scripting: none) {
+  .ssd .anim {
+    animation-play-state: running !important;
+    animation-delay: -999s !important;
+  }
+}
+
+#d0 .anim {
+  animation-fill-mode: forwards;
+}
+#d0 .bar {
+  transform-box: fill-box;
+  transform-origin: left center;
+}
+@keyframes d0-drain {
+  from {
+    transform: scaleX(1);
+  }
+  to {
+    transform: scaleX(0);
+  }
+}
+@keyframes d0-in {
+  from {
+    opacity: 0;
+  }
+  to {
+    opacity: 1;
+  }
+}
+@keyframes d0-out {
+  from {
+    opacity: 1;
+  }
+  to {
+    opacity: 0.12;
+  }
+}
+@keyframes d0-gone {
+  from {
+    opacity: 1;
+  }
+  to {
+    opacity: 0;
+  }
+}
+#d0 .bar {
+  animation: d0-drain 3.2s ease-in-out forwards;
+}
+/* Explicit expiry states: archived entries dim hard and get hatched over;
+   the temporary entry disappears entirely. Outcome boxes appear at expiry. */
+#d0 .d0-entry-inst,
+#d0 .d0-entry-pers {
+  animation: d0-out 0.6s ease-out 3.15s forwards;
+}
+#d0 .d0-entry-temp {
+  animation: d0-gone 0.7s ease-in 3.15s forwards;
+}
+#d0 .d0-hatch {
+  opacity: 0;
+  animation: d0-in 0.6s ease-out 3.3s forwards;
+}
+#d0 .d0-arrow,
+#d0 .d0-arrowhead {
+  fill: none;
+  stroke: var(--line-strong);
+  stroke-width: 1.2;
+}
+#d0 .d0-expiry {
+  paint-order: stroke;
+  stroke: var(--ssd-page-bg);
+  stroke-width: 6px;
+  stroke-linejoin: round;
+}
+#d0 .d0-outcome {
+  opacity: 0;
+  animation: d0-in 0.6s ease-out 3.3s forwards;
+}
+#d0 .d0-result-inst {
+  fill: var(--amber-soft);
+  stroke: var(--amber);
+}
+#d0 .d0-result-pers {
+  fill: var(--teal-soft);
+  stroke: var(--teal);
+}
+#d0 .d0-result-temp {
+  fill: var(--rose-soft);
+  stroke: var(--rose);
+}
+#d0 .d0-result-title {
+  fill: var(--ink);
+  font-size: 10px;
+}
+#d0 .d0-inst-restored,
+#d0 .d0-pers-restored {
+  display: none;
+}
+#d0.restored-instance .d0-inst-archived,
+#d0.restored-persistent .d0-pers-archived {
+  display: none;
+}
+#d0.restored-instance .d0-inst-restored,
+#d0.restored-persistent .d0-pers-restored {
+  display: inline;
+}
+/* Restoring revives the entry: back to full opacity, TTL bar refilled,
+   hatching removed. Temporary has no restore path by design. */
+#d0.restored-instance .d0-entry-inst,
+#d0.restored-persistent .d0-entry-pers {
+  animation: none;
+  opacity: 1;
+}
+#d0.restored-instance .ttl-fill-inst,
+#d0.restored-persistent .ttl-fill-pers {
+  animation: none;
+  transform: scaleX(1);
+}
+#d0.restored-instance .d0-hatch-inst,
+#d0.restored-persistent .d0-hatch-pers {
+  animation: none;
+  opacity: 0;
+}
+
+@keyframes d1-fly {
+  0% {
+    transform: translateX(0);
+    opacity: 0;
+  }
+  12% {
+    opacity: 1;
+  }
+  78% {
+    opacity: 1;
+    transform: translateX(118px);
+  }
+  100% {
+    transform: translateX(118px);
+    opacity: 0;
+  }
+}
+@keyframes d1-glow {
+  0%,
+  100% {
+    stroke: var(--amber);
+    stroke-width: 1.4;
+  }
+  50% {
+    stroke-width: 3;
+  }
+}
+#d1 .inv {
+  opacity: 0;
+  animation: d1-fly 1.6s ease-in-out 3;
+}
+#d1 .inv2 {
+  animation-delay: 0.55s;
+}
+#d1 .inv3 {
+  animation-delay: 1.1s;
+}
+#d1 .box {
+  animation: d1-glow 1.6s ease-in-out 3;
+}
+
+@keyframes d2-grow {
+  0% {
+    transform: scale(1);
+  }
+  70% {
+    transform: scale(1.22);
+  }
+  100% {
+    transform: scale(1.24);
+  }
+}
+@keyframes d2-alarm {
+  0%,
+  100% {
+    stroke: var(--line-strong);
+  }
+  60%,
+  90% {
+    stroke: var(--danger);
+    stroke-width: 2.4;
+  }
+}
+@keyframes d2-in {
+  from {
+    opacity: 0;
+    transform: translateY(6px);
+  }
+  to {
+    opacity: 1;
+    transform: translateY(0);
+  }
+}
+@keyframes d2-dim {
+  to {
+    opacity: 0.45;
+  }
+}
+#d2 .badside {
+  animation: d2-dim 0.8s ease-out 2.6s forwards;
+}
+#d2 .blob {
+  transform-box: fill-box;
+  transform-origin: center;
+  animation:
+    d2-grow 2.4s ease-in forwards,
+    d2-alarm 2.4s ease-in forwards;
+}
+#d2 .warn {
+  opacity: 0;
+  animation: d2-in 0.5s ease-out 2s forwards;
+}
+#d2 .u1 {
+  opacity: 0;
+  animation: d2-in 0.5s ease-out 0.4s forwards;
+}
+#d2 .u2 {
+  opacity: 0;
+  animation: d2-in 0.5s ease-out 0.9s forwards;
+}
+#d2 .u3 {
+  opacity: 0;
+  animation: d2-in 0.5s ease-out 1.4s forwards;
+}
+#d2 .u4 {
+  opacity: 0;
+  animation: d2-in 0.5s ease-out 1.9s forwards;
+}
+
+@keyframes d3-hit {
+  0%,
+  100% {
+    fill: var(--teal-soft);
+    stroke: var(--line-strong);
+  }
+  40%,
+  70% {
+    fill: var(--teal);
+    stroke: var(--teal);
+  }
+}
+@keyframes d3-in {
+  from {
+    opacity: 0;
+  }
+  to {
+    opacity: 1;
+  }
+}
+#d3 .hit {
+  animation: d3-hit 2.6s ease-in-out 0.8s 2;
+}
+#d3 .keylbl {
+  opacity: 0;
+  animation: d3-in 0.6s ease-out 1.2s forwards;
+}
+
+#d4 .bar {
+  transform-box: fill-box;
+  transform-origin: left center;
+}
+@keyframes d4-drain {
+  from {
+    transform: scaleX(1);
+  }
+  to {
+    transform: scaleX(0);
+  }
+}
+@keyframes d4-gone {
+  from {
+    opacity: 1;
+  }
+  to {
+    opacity: 0;
+  }
+}
+@keyframes d4-in {
+  from {
+    opacity: 0;
+  }
+  to {
+    opacity: 1;
+  }
+}
+@keyframes d4-slide {
+  from {
+    transform: translateX(24px);
+    opacity: 0;
+  }
+  to {
+    transform: translateX(0);
+    opacity: 1;
+  }
+}
+#d4 .b1 {
+  animation: d4-drain 2.6s linear forwards;
+}
+#d4 .cell1 {
+  animation: d4-gone 0.6s ease-in 2.6s forwards;
+}
+#d4 .gonelbl {
+  opacity: 0;
+  animation: d4-in 0.5s ease-out 3.1s forwards;
+}
+#d4 .old {
+  animation: d4-gone 0.8s ease-in 1.2s forwards;
+}
+#d4 .new {
+  opacity: 0;
+  animation: d4-slide 0.7s ease-out 1.6s forwards;
+}
+
+#d5 .extend-zone {
+  fill: var(--danger);
+  opacity: 0.14;
+}
+#d5 .threshold {
+  stroke: var(--danger);
+  stroke-width: 1.6;
+  stroke-dasharray: 4 3;
+}
+#d5 .bar {
+  transform-box: fill-box;
+  transform-origin: left center;
+}
+@keyframes d5-drain1 {
+  0% {
+    transform: scaleX(1);
+  }
+  100% {
+    transform: scaleX(0.72);
+  }
+}
+@keyframes d5-drain2 {
+  0% {
+    transform: scaleX(0.72);
+  }
+  100% {
+    transform: scaleX(0.42);
+  }
+}
+@keyframes d5-refill {
+  0% {
+    transform: scaleX(0.42);
+  }
+  100% {
+    transform: scaleX(1);
+  }
+}
+@keyframes d5-bolt {
+  0% {
+    transform: translateY(-16px);
+    opacity: 0;
+  }
+  40% {
+    opacity: 1;
+    transform: translateY(0);
+  }
+  100% {
+    opacity: 0;
+    transform: translateY(0);
+  }
+}
+@keyframes d5-in {
+  from {
+    opacity: 0;
+  }
+  to {
+    opacity: 1;
+  }
+}
+/* One bar, three chained transform animations: the later one wins while it
+   runs or fills, so the bar drains, drains past the threshold, then refills. */
+#d5 .pbar {
+  animation:
+    d5-drain1 1.6s linear forwards,
+    d5-drain2 1.6s linear 2.4s forwards,
+    d5-refill 0.5s ease-out 5.1s forwards;
+}
+#d5 .bolt1 {
+  opacity: 0;
+  animation: d5-bolt 1s ease-out 1.3s;
+}
+#d5 .bolt2 {
+  opacity: 0;
+  animation: d5-bolt 1s ease-out 4.1s;
+}
+#d5 .noop {
+  opacity: 0;
+  animation:
+    d5-in 0.4s ease-out 1.6s forwards,
+    d5-in 0.4s ease-out reverse 2.8s forwards;
+}
+#d5 .bump {
+  opacity: 0;
+  animation: d5-in 0.4s ease-out 5.2s forwards;
+}
+
+@keyframes d6-in {
+  from {
+    opacity: 0;
+    transform: scale(0.6);
+  }
+  to {
+    opacity: 1;
+    transform: scale(1);
+  }
+}
+@keyframes d6-approach {
+  0% {
+    transform: translate(0, 0);
+    opacity: 0;
+  }
+  30% {
+    opacity: 1;
+  }
+  60% {
+    transform: translate(-46px, 0);
+  }
+  78% {
+    transform: translate(-34px, 0);
+  }
+  100% {
+    transform: translate(-38px, 0);
+    opacity: 1;
+  }
+}
+#d6 .slot {
+  transform-box: fill-box;
+  transform-origin: center;
+  opacity: 0;
+}
+#d6 .s1 {
+  animation: d6-in 0.4s ease-out 0.3s forwards;
+}
+#d6 .s2 {
+  animation: d6-in 0.4s ease-out 0.7s forwards;
+}
+#d6 .s3 {
+  animation: d6-in 0.4s ease-out 1.1s forwards;
+}
+#d6 .s4 {
+  animation: d6-in 0.4s ease-out 1.5s forwards;
+}
+#d6 .s5 {
+  animation: d6-in 0.4s ease-out 1.9s forwards;
+}
+#d6 .s6 {
+  animation: d6-in 0.4s ease-out 2.3s forwards;
+}
+#d6 .reject {
+  opacity: 0;
+  animation: d6-approach 1.6s ease-in-out 2.8s forwards;
+}
+#d6 .panic {
+  opacity: 0;
+  /* settle visible so the resting frame still shows why #31 was rejected */
+  animation: d6-stay 0.4s ease-out 4.2s forwards;
+}
+@keyframes d6-stay {
+  from {
+    opacity: 0;
+  }
+  to {
+    opacity: 1;
+  }
+}
+
+@keyframes d7-flash {
+  0%,
+  100% {
+    fill: var(--teal-soft);
+  }
+  45%,
+  65% {
+    fill: color-mix(in srgb, var(--teal) 30%, var(--teal-soft));
+  }
+}
+@keyframes d7-in {
+  from {
+    opacity: 0;
+  }
+  to {
+    opacity: 1;
+  }
+}
+#d7 .wholeblob {
+  animation: d7-flash 2.2s ease-in-out 0.8s 2;
+}
+#d7 .onefield {
+  animation: d7-flash 2.2s ease-in-out 0.8s 2;
+}
+#d7 .u1 {
+  opacity: 0;
+  animation: d7-in 0.5s ease-out 1.6s forwards;
+}
+#d7 .u2 {
+  opacity: 0;
+  animation: d7-in 0.5s ease-out 1.6s forwards;
+}
+
+@keyframes d8-remove {
+  0%,
+  40% {
+    opacity: 1;
+  }
+  60%,
+  100% {
+    opacity: 0;
+  }
+}
+@keyframes d8-move {
+  0%,
+  55% {
+    transform: translateX(0);
+  }
+  85%,
+  100% {
+    transform: translateX(-264px);
+  }
+}
+@keyframes d8-tail {
+  0%,
+  70% {
+    opacity: 1;
+  }
+  95%,
+  100% {
+    opacity: 0.18;
+  }
+}
+@keyframes d8-in {
+  from {
+    opacity: 0;
+  }
+  to {
+    opacity: 1;
+  }
+}
+#d8 .gone {
+  animation: d8-remove 3s ease-in-out forwards;
+}
+#d8 .mover {
+  animation: d8-move 3s ease-in-out forwards;
+}
+#d8 .tail {
+  animation: d8-tail 3s ease-in-out forwards;
+}
+#d8 .note1 {
+  opacity: 0;
+  animation: d8-in 0.5s ease-out 1s forwards;
+}
+#d8 .note2 {
+  opacity: 0;
+  animation: d8-in 0.5s ease-out 1.7s forwards;
+}
+#d8 .note3 {
+  opacity: 0;
+  animation: d8-in 0.5s ease-out 2.2s forwards;
+}
+#d8 .note4 {
+  opacity: 0;
+  animation: d8-in 0.5s ease-out 2.7s forwards;
+}
+
+#d9 .bar {
+  transform-box: fill-box;
+  transform-origin: left center;
+}
+@keyframes d9-rise {
+  from {
+    transform: scaleX(0.3);
+  }
+  to {
+    transform: scaleX(0.85);
+  }
+}
+@keyframes d9-in {
+  from {
+    opacity: 0;
+  }
+  to {
+    opacity: 1;
+  }
+}
+@keyframes d9-arrive {
+  0% {
+    transform: translateY(26px);
+    opacity: 0;
+  }
+  100% {
+    transform: translateY(0);
+    opacity: 1;
+  }
+}
+#d9 .gidx {
+  animation: d9-rise 3.4s linear forwards;
+}
+#d9 .alice {
+  animation: d9-arrive 0.7s ease-out 1.6s both;
+}
+#d9 .delta {
+  opacity: 0;
+  animation: d9-in 0.5s ease-out 2.3s forwards;
+}
+#d9 .dline {
+  opacity: 0;
+  animation: d9-in 0.5s ease-out 2.3s forwards;
+}
+/* Ghost entries settle at partial opacity — visibly "untouched". */
+@keyframes d9-ghost-in {
+  from {
+    opacity: 0;
+  }
+  to {
+    opacity: 0.45;
+  }
+}
+#d9 .ghost {
+  opacity: 0;
+  animation: d9-ghost-in 0.5s ease-out 3s forwards;
+}
+
+/* d10 — checkpoints: entries append left-to-right, then a historical query
+   probes cells by binary search and settles on the last one ≤ the target. */
+@keyframes d10-in {
+  from {
+    opacity: 0;
+    transform: translateY(6px);
+  }
+  to {
+    opacity: 1;
+    transform: translateY(0);
+  }
+}
+@keyframes d10-flash {
+  0%,
+  100% {
+    stroke-width: 1.2;
+  }
+  40%,
+  70% {
+    stroke: var(--ink);
+    stroke-width: 2.6;
+  }
+}
+@keyframes d10-stay {
+  from {
+    opacity: 0;
+  }
+  to {
+    opacity: 1;
+  }
+}
+#d10 .cp1,
+#d10 .cp2,
+#d10 .cp3,
+#d10 .cp4 {
+  transform-box: fill-box;
+  transform-origin: center;
+  opacity: 0;
+}
+#d10 .cp1 {
+  animation: d10-in 0.4s ease-out 0.3s forwards;
+}
+#d10 .cp2 {
+  animation: d10-in 0.4s ease-out 0.7s forwards;
+}
+#d10 .cp3 {
+  animation: d10-in 0.4s ease-out 1.1s forwards;
+}
+#d10 .cp4 {
+  animation: d10-in 0.4s ease-out 1.5s forwards;
+}
+#d10 .cnt {
+  opacity: 0;
+  animation: d10-stay 0.5s ease-out 2s forwards;
+}
+#d10 .q {
+  opacity: 0;
+  animation: d10-stay 0.5s ease-out 2.6s forwards;
+}
+/* Probe order mirrors the code: check the newest checkpoint first,
+   then binary-search down to the last one at or before the target. */
+#d10 .pr3 {
+  animation: d10-flash 0.9s ease-in-out 3.2s;
+}
+#d10 .plbl3 {
+  opacity: 0;
+  animation: d10-stay 0.4s ease-out 3.5s forwards;
+}
+#d10 .pr2 {
+  animation: d10-flash 0.9s ease-in-out 4s;
+}
+#d10 .plbl2 {
+  opacity: 0;
+  animation: d10-stay 0.4s ease-out 4.3s forwards;
+}
+#d10 .winring {
+  opacity: 0;
+  fill: none;
+  stroke: var(--teal);
+  stroke-width: 2.2;
+  animation: d10-stay 0.5s ease-out 4.6s forwards;
+}
+#d10 .ans {
+  opacity: 0;
+  animation: d10-stay 0.5s ease-out 4.8s forwards;
+}
+
+@keyframes d11-fade {
+  from {
+    opacity: 1;
+  }
+  to {
+    opacity: 0.16;
+  }
+}
+@keyframes d11-glow {
+  0% {
+    stroke-width: 1.2;
+  }
+  60% {
+    stroke-width: 3;
+  }
+  100% {
+    stroke-width: 2;
+  }
+}
+@keyframes d11-in {
+  from {
+    opacity: 0;
+  }
+  to {
+    opacity: 1;
+  }
+}
+@keyframes d11-relight {
+  to {
+    opacity: 1;
+  }
+}
+#d11 .leaves {
+  animation: d11-fade 1.8s ease-in 1s forwards;
+}
+#d11 .proof {
+  animation:
+    d11-fade 1.8s ease-in 1s forwards,
+    d11-relight 0.7s ease-out 3.4s forwards;
+}
+#d11 .proof .cell {
+  animation: d11-glow 0.7s ease-out 3.4s forwards;
+}
+#d11 .root {
+  animation: d11-glow 1.4s ease-out 2.4s forwards;
+}
+#d11 .onchain {
+  opacity: 0;
+  animation: d11-in 0.6s ease-out 2.6s forwards;
+}
+#d11 .claimcap {
+  opacity: 0;
+  animation: d11-in 0.6s ease-out 3.6s forwards;
+}
+#d11 .claim {
+  opacity: 0;
+  animation: d11-in 0.6s ease-out 4.3s forwards;
+}
+
+@keyframes d12-spawn {
+  0% {
+    opacity: 0;
+    transform: translateX(-40px) scale(0.7);
+  }
+  100% {
+    opacity: 1;
+    transform: translateX(0) scale(1);
+  }
+}
+@keyframes d12-in {
+  from {
+    opacity: 0;
+  }
+  to {
+    opacity: 1;
+  }
+}
+#d12 .pair {
+  transform-box: fill-box;
+  transform-origin: center;
+  opacity: 0;
+}
+#d12 .w1 {
+  opacity: 0;
+  animation: d12-in 0.4s ease-out 0.4s forwards;
+}
+#d12 .w2 {
+  opacity: 0;
+  animation: d12-in 0.4s ease-out 1.1s forwards;
+}
+#d12 .w3 {
+  opacity: 0;
+  animation: d12-in 0.4s ease-out 1.8s forwards;
+}
+#d12 .pr1 {
+  animation: d12-spawn 0.7s ease-out 0.4s forwards;
+}
+#d12 .pr2 {
+  animation: d12-spawn 0.7s ease-out 1.1s forwards;
+}
+#d12 .pr3 {
+  animation: d12-spawn 0.7s ease-out 1.8s forwards;
+}
+#d12 .reg1 {
+  opacity: 0;
+  animation: d12-in 0.4s ease-out 0.8s forwards;
+}
+#d12 .reg2 {
+  opacity: 0;
+  animation: d12-in 0.4s ease-out 1.5s forwards;
+}
+#d12 .reg3 {
+  opacity: 0;
+  animation: d12-in 0.4s ease-out 2.2s forwards;
+}
+#d12 .iso {
+  opacity: 0;
+  animation: d12-in 0.6s ease-out 2.7s forwards;
+}
+
+/* Color utilities — SVG presentation attributes (fill="var(--x)") lose to any
+   CSS rule above, so accent colors must be classes. Keep these last: they
+   share specificity with .cell/.wire/text rules and win on source order. */
+.ssd svg .fill-ink {
+  fill: var(--ink);
+}
+.ssd svg .fill-amber {
+  fill: var(--amber);
+}
+.ssd svg .fill-teal {
+  fill: var(--teal);
+}
+.ssd svg .fill-rose {
+  fill: var(--rose);
+}
+.ssd svg .fill-danger {
+  fill: var(--danger);
+}
+.ssd svg .fill-none {
+  fill: none;
+}
+.ssd svg .stroke-ink {
+  stroke: var(--ink);
+}
+.ssd svg .stroke-teal {
+  stroke: var(--teal);
+}
+.ssd svg .stroke-danger {
+  stroke: var(--danger);
+}
+`;
+
+const CAPTIONS = {};
+const SVGS = {
+    d0: (<svg viewBox="0 0 660 192" role="img" aria-label="Interactive comparison of storage expiry outcomes and restoration methods. An expired contract instance entry is archived; contract code is a separate entry with its own TTL. An expired persistent key is archived individually. Either can be restored automatically through an invocation restore list or manually with RestoreFootprintOp. An expired temporary entry is deleted permanently.">
+      <text x="105" y="16" textAnchor="middle" className="lbl">
+        instance()
+      </text>
+      <g className="d0-entry d0-entry-inst anim">
+        <rect className="cell cell-inst" x="30" y="26" width="150" height="48"/>
+        <text x="105" y="48" textAnchor="middle" className="lbl-s">
+          contract instance
+        </text>
+        <text x="105" y="65" textAnchor="middle" className="lbl-s mono">
+          Admin, Config…
+        </text>
+      </g>
+      <g className="d0-hatch d0-hatch-inst anim">
+        <line className="hatch" x1="42" y1="72" x2="86" y2="28"/>
+        <line className="hatch" x1="74" y1="72" x2="118" y2="28"/>
+        <line className="hatch" x1="106" y1="72" x2="150" y2="28"/>
+        <line className="hatch" x1="138" y1="72" x2="176" y2="34"/>
+      </g>
+      <rect className="ttl-track" x="30" y="82" width="150" height="6"/>
+      <rect className="ttl-fill-inst bar anim" x="30" y="82" width="150" height="6"/>
+      <line className="d0-arrow" x1="105" y1="94" x2="105" y2="110"/>
+      <path className="d0-arrowhead" d="M101 106 L105 112 L109 106"/>
+      <text x="105" y="104" textAnchor="middle" className="lbl-s d0-expiry">
+        TTL expires
+      </text>
+      <g className="d0-outcome d0-inst-archived anim">
+        <rect className="cell d0-result-inst" x="25" y="119" width="160" height="68"/>
+        <text x="105" y="139" textAnchor="middle" className="lbl d0-result-title">
+          ARCHIVED
+        </text>
+        <text x="105" y="157" textAnchor="middle" className="lbl-s">
+          contract instance entry
+        </text>
+        <text x="105" y="177" textAnchor="middle" className="lbl-s">
+          code has its own TTL
+        </text>
+      </g>
+      <g className="d0-inst-restored">
+        <rect className="cell d0-result-inst" x="25" y="119" width="160" height="68"/>
+        <text x="105" y="141" textAnchor="middle" className="lbl d0-result-title">
+          RESTORED
+        </text>
+        <text x="105" y="161" textAnchor="middle" className="lbl-s">
+          instance entry
+          <tspan x="105" dy="15">
+            + code, if also archived
+          </tspan>
+        </text>
+      </g>
+
+      <text x="330" y="16" textAnchor="middle" className="lbl">
+        persistent()
+      </text>
+      <g className="d0-entry d0-entry-pers anim">
+        <rect className="cell cell-pers" x="255" y="26" width="150" height="48"/>
+        <text x="330" y="48" textAnchor="middle" className="lbl-s mono">
+          Balance(alice)
+        </text>
+        <text x="330" y="65" textAnchor="middle" className="lbl-s mono">
+          → 1_000_000
+        </text>
+      </g>
+      <g className="d0-hatch d0-hatch-pers anim">
+        <line className="hatch" x1="267" y1="72" x2="311" y2="28"/>
+        <line className="hatch" x1="299" y1="72" x2="343" y2="28"/>
+        <line className="hatch" x1="331" y1="72" x2="375" y2="28"/>
+        <line className="hatch" x1="363" y1="72" x2="401" y2="34"/>
+      </g>
+      <rect className="ttl-track" x="255" y="82" width="150" height="6"/>
+      <rect className="ttl-fill-pers bar anim" x="255" y="82" width="150" height="6"/>
+      <line className="d0-arrow" x1="330" y1="94" x2="330" y2="110"/>
+      <path className="d0-arrowhead" d="M326 106 L330 112 L334 106"/>
+      <text x="330" y="104" textAnchor="middle" className="lbl-s d0-expiry">
+        TTL expires
+      </text>
+      <g className="d0-outcome d0-pers-archived anim">
+        <rect className="cell d0-result-pers" x="250" y="119" width="160" height="68"/>
+        <text x="330" y="139" textAnchor="middle" className="lbl d0-result-title">
+          ARCHIVED
+        </text>
+        <text x="330" y="157" textAnchor="middle" className="lbl-s">
+          one persistent entry
+        </text>
+        <text x="330" y="177" textAnchor="middle" className="lbl-s">
+          independent TTL
+        </text>
+      </g>
+      <g className="d0-pers-restored">
+        <rect className="cell d0-result-pers" x="250" y="119" width="160" height="68"/>
+        <text x="330" y="141" textAnchor="middle" className="lbl d0-result-title">
+          RESTORED
+        </text>
+        <text x="330" y="169" textAnchor="middle" className="lbl-s">
+          this exact key only
+        </text>
+      </g>
+
+      <text x="555" y="16" textAnchor="middle" className="lbl">
+        temporary()
+      </text>
+      <g className="d0-entry d0-entry-temp anim">
+        <rect className="cell cell-temp" x="480" y="26" width="150" height="48"/>
+        <text x="555" y="48" textAnchor="middle" className="lbl-s mono">
+          Allowance(a,b)
+        </text>
+        <text x="555" y="65" textAnchor="middle" className="lbl-s mono">
+          → 500
+        </text>
+      </g>
+      <rect className="ttl-track" x="480" y="82" width="150" height="6"/>
+      <rect className="ttl-fill-temp bar anim" x="480" y="82" width="150" height="6"/>
+      <line className="d0-arrow" x1="555" y1="94" x2="555" y2="110"/>
+      <path className="d0-arrowhead" d="M551 106 L555 112 L559 106"/>
+      <text x="555" y="104" textAnchor="middle" className="lbl-s d0-expiry">
+        TTL expires
+      </text>
+      <g className="d0-outcome anim">
+        <rect className="cell d0-result-temp" x="475" y="119" width="160" height="68"/>
+        <text x="555" y="139" textAnchor="middle" className="lbl d0-result-title">
+          DELETED
+        </text>
+        <text x="555" y="157" textAnchor="middle" className="lbl-s">
+          permanent
+        </text>
+        <text x="555" y="177" textAnchor="middle" className="lbl-s">
+          no restore path
+        </text>
+      </g>
+    </svg>),
+    d1: (<svg viewBox="0 0 660 170" role="img" aria-label="Animation: every invocation loads the contract instance entry, so its config needs no separate footprint entry.">
+      <text x="120" y="52" textAnchor="middle" className="lbl">
+        invocations
+      </text>
+      <circle className="inv anim fill-ink" cx="60" cy="86" r="5"/>
+      <circle className="inv inv2 anim fill-ink" cx="60" cy="86" r="5"/>
+      <circle className="inv inv3 anim fill-ink" cx="60" cy="86" r="5"/>
+      <line className="wire" x1="52" y1="86" x2="196" y2="86"/>
+      <rect className="cell cell-inst box anim" x="210" y="30" width="240" height="112" rx="10"/>
+      <text x="330" y="54" textAnchor="middle" className="lbl fill-amber">
+        contract instance — one entry
+      </text>
+      <rect className="cell" x="232" y="66" width="60" height="26" rx="4"/>
+      <text x="262" y="83" textAnchor="middle" className="lbl-s mono">
+        Admin
+      </text>
+      <rect className="cell" x="300" y="66" width="60" height="26" rx="4"/>
+      <text x="330" y="83" textAnchor="middle" className="lbl-s mono">
+        Token0
+      </text>
+      <rect className="cell" x="368" y="66" width="60" height="26" rx="4"/>
+      <text x="398" y="83" textAnchor="middle" className="lbl-s mono">
+        Token1
+      </text>
+      <rect className="cell" x="232" y="100" width="94" height="26" rx="4"/>
+      <text x="279" y="117" textAnchor="middle" className="lbl-s mono">
+        Reserve0
+      </text>
+      <rect className="cell" x="334" y="100" width="94" height="26" rx="4"/>
+      <text x="381" y="117" textAnchor="middle" className="lbl-s mono">
+        Reserve1
+      </text>
+      <text x="330" y="162" textAnchor="middle" className="lbl-s">
+        loaded with each invocation → no separate config footprint entry
+      </text>
+    </svg>),
+    d2: (<svg viewBox="0 0 660 190" role="img" aria-label="Animation: one shared map entry swells toward the 64-kibibyte entry cap, while one-entry-per-user stays small and supports independent access.">
+      <g className="badside anim">
+        <text x="165" y="22" textAnchor="middle" className="lbl">
+          ✗ one shared map
+        </text>
+        <rect className="cell blob anim" x="105" y="42" width="120" height="86" rx="8"/>
+        <text x="165" y="76" textAnchor="middle" className="lbl-s mono">
+          Map&lt;Address,i128&gt;
+        </text>
+        <text x="165" y="94" textAnchor="middle" className="lbl-s">
+          every user, one entry
+        </text>
+      </g>
+      <text x="165" y="166" textAnchor="middle" className="lbl warn anim fill-danger">
+        → 64 KiB cap · rewrites · contention
+      </text>
+
+      <line className="wire dashed" x1="330" y1="30" x2="330" y2="160"/>
+
+      <text x="495" y="22" textAnchor="middle" className="lbl">
+        ✓ one entry per holder
+      </text>
+      <g className="u1 anim">
+        <rect className="cell cell-pers" x="390" y="40" width="210" height="24" rx="4"/>
+        <text x="495" y="56" textAnchor="middle" className="lbl-s mono">
+          Balance(alice) → 120
+        </text>
+      </g>
+      <g className="u2 anim">
+        <rect className="cell cell-pers" x="390" y="70" width="210" height="24" rx="4"/>
+        <text x="495" y="86" textAnchor="middle" className="lbl-s mono">
+          Balance(bob) → 7_500
+        </text>
+      </g>
+      <g className="u3 anim">
+        <rect className="cell cell-pers" x="390" y="100" width="210" height="24" rx="4"/>
+        <text x="495" y="116" textAnchor="middle" className="lbl-s mono">
+          Balance(carol) → 41
+        </text>
+      </g>
+      <g className="u4 anim">
+        <text x="495" y="146" textAnchor="middle" className="lbl-s">
+          …one independently addressed entry per user,
+        </text>
+        <text x="495" y="162" textAnchor="middle" className="lbl-s">
+          transactions touch only the entries they need
+        </text>
+      </g>
+    </svg>),
+    d3: (<svg viewBox="0 0 660 190" role="img" aria-label="Animation: a two-dimensional key like owner and spender maps to exactly one independent ledger entry.">
+      <text x="120" y="40" textAnchor="end" className="lbl">
+        owners ↓
+      </text>
+      <text x="255" y="22" textAnchor="middle" className="lbl">
+        spenders →
+      </text>
+      <g>
+        <rect className="cell" x="140" y="34" width="70" height="34" rx="4"/>
+        <rect className="cell" x="218" y="34" width="70" height="34" rx="4"/>
+        <rect className="cell" x="296" y="34" width="70" height="34" rx="4"/>
+        <rect className="cell" x="140" y="76" width="70" height="34" rx="4"/>
+        <rect className="cell hit anim" x="218" y="76" width="70" height="34" rx="4"/>
+        <rect className="cell" x="296" y="76" width="70" height="34" rx="4"/>
+        <rect className="cell" x="140" y="118" width="70" height="34" rx="4"/>
+        <rect className="cell" x="218" y="118" width="70" height="34" rx="4"/>
+        <rect className="cell" x="296" y="118" width="70" height="34" rx="4"/>
+      </g>
+      <g className="keylbl anim">
+        <line className="wire" x1="366" y1="93" x2="428" y2="93"/>
+        <rect className="cell cell-pers" x="430" y="70" width="196" height="46" rx="6"/>
+        <text x="528" y="89" textAnchor="middle" className="lbl-s mono">
+          Allowance(alice, bob)
+        </text>
+        <text x="528" y="105" textAnchor="middle" className="lbl-s">
+          one independent entry per pair
+        </text>
+      </g>
+      <text x="330" y="180" textAnchor="middle" className="lbl-s">
+        every (owner, spender) combination = its own ledger entry — no nested
+        maps
+      </text>
+    </svg>),
+    d4: (<svg viewBox="0 0 660 200" role="img" aria-label="Animation: a temporary allowance entry is deleted when its TTL runs out, and timestamp-keyed price-history entries are deleted as their derived TTLs expire.">
+      <g className="cell1 anim">
+        <rect className="cell cell-temp" x="40" y="34" width="190" height="52" rx="6"/>
+        <text x="135" y="56" textAnchor="middle" className="lbl-s mono">
+          Allowance(from, spender)
+        </text>
+        <text x="135" y="72" textAnchor="middle" className="lbl-s mono">
+          &#123; amount, live_until_ledger &#125;
+        </text>
+      </g>
+      <rect className="ttl-track" x="40" y="98" width="190" height="6"/>
+      <rect className="ttl-fill-temp bar b1 anim" x="40" y="98" width="190" height="6"/>
+      <text x="40" y="122" className="lbl-s">
+        TTL aligned to the deadline when possible
+      </text>
+      <text x="135" y="70" textAnchor="middle" className="lbl gonelbl anim fill-rose">
+        deleted without a cleanup transaction
+      </text>
+
+      <text x="470" y="26" textAnchor="middle" className="lbl">
+        self-pruning oracle history
+      </text>
+      <g className="old anim">
+        <rect className="cell cell-temp" x="330" y="40" width="56" height="34" rx="4"/>
+        <text x="358" y="61" textAnchor="middle" className="lbl-s mono">
+          t−4
+        </text>
+      </g>
+      <rect className="cell cell-temp" x="394" y="40" width="56" height="34" rx="4"/>
+      <text x="422" y="61" textAnchor="middle" className="lbl-s mono">
+        t−3
+      </text>
+      <rect className="cell cell-temp" x="458" y="40" width="56" height="34" rx="4"/>
+      <text x="486" y="61" textAnchor="middle" className="lbl-s mono">
+        t−2
+      </text>
+      <rect className="cell cell-temp" x="522" y="40" width="56" height="34" rx="4"/>
+      <text x="550" y="61" textAnchor="middle" className="lbl-s mono">
+        t−1
+      </text>
+      <g className="new anim">
+        <rect className="cell cell-temp" x="586" y="40" width="40" height="34" rx="4"/>
+        <text x="606" y="61" textAnchor="middle" className="lbl-s mono">
+          t
+        </text>
+      </g>
+      <text x="470" y="100" textAnchor="middle" className="lbl-s">
+        one entry per price round, keyed by timestamp;
+      </text>
+      <text x="470" y="116" textAnchor="middle" className="lbl-s">
+        TTL derived from retention → old rounds can expire independently
+      </text>
+      <text x="330" y="180" textAnchor="middle" className="lbl-s">
+        temporary entries are deleted on expiry without a cleanup transaction;
+        rent is half the persistent rate
+      </text>
+    </svg>),
+    d5: (<svg viewBox="0 0 660 190" role="img" aria-label="Animation: extend_ttl is a no-op while plenty of TTL remains, and extends the TTL to the bump amount once it drops below the threshold.">
+      <text x="60" y="30" className="lbl">
+        TTL of <tspan className="mono">Balance(alice)</tspan>
+      </text>
+      <rect className="ttl-track" x="60" y="70" width="540" height="14" rx="3"/>
+      <rect className="extend-zone" x="60" y="70" width="324" height="14" rx="3"/>
+      <text x="222" y="110" textAnchor="middle" className="lbl-s fill-danger">
+        in this zone, an extend_ttl() call extends the TTL
+      </text>
+      <rect className="ttl-fill-pers bar pbar anim" x="60" y="70" width="540" height="14" rx="3"/>
+      <line className="threshold" x1="384" y1="58" x2="384" y2="96"/>
+      <text x="384" y="52" textAnchor="middle" className="lbl-s fill-danger">
+        THRESHOLD
+      </text>
+      <text x="60" y="110" className="lbl-s">
+        0
+      </text>
+      <text x="600" y="110" textAnchor="end" className="lbl-s">
+        BUMP
+      </text>
+      <g className="bolt1 anim">
+        <text x="470" y="46" textAnchor="middle" className="lbl fill-ink">
+          extend_ttl()
+        </text>
+      </g>
+      <text x="470" y="132" textAnchor="middle" className="lbl-s noop anim">
+        above threshold → extend_ttl is a no-op
+      </text>
+      <g className="bolt2 anim">
+        <text x="270" y="46" textAnchor="middle" className="lbl fill-ink">
+          extend_ttl()
+        </text>
+      </g>
+      <text x="270" y="132" textAnchor="middle" className="lbl-s bump anim fill-teal">
+        below threshold → extended to BUMP · rent charged with transaction fees
+      </text>
+      <text x="330" y="160" textAnchor="middle" className="lbl-s">
+        if called on every access → at most one extension per 17,280 ledgers
+      </text>
+      <text x="330" y="178" textAnchor="middle" className="lbl-s">
+        not to scale — with THRESHOLD = BUMP − 17,280 ledgers, the no-op zone
+        is only the top ~3% of the bar
+      </text>
+    </svg>),
+    d6: (<svg viewBox="0 0 660 160" role="img" aria-label="Animation: a list inside one entry fills up to the hard cap the contract chose for itself; the next insert is rejected by contract code, not by a network limit.">
+      <rect className="cell cell-pers" x="60" y="40" width="400" height="60" rx="8"/>
+      <text x="260" y="30" textAnchor="middle" className="lbl fill-teal">
+        ResList — ONE entry, hard cap in code
+      </text>
+      <rect className="cell slot s1 anim" x="76" y="54" width="56" height="32" rx="4"/>
+      <text x="104" y="75" textAnchor="middle" className="lbl-s mono">
+        USDC
+      </text>
+      <rect className="cell slot s2 anim" x="140" y="54" width="56" height="32" rx="4"/>
+      <text x="168" y="75" textAnchor="middle" className="lbl-s mono">
+        XLM
+      </text>
+      <rect className="cell slot s3 anim" x="204" y="54" width="56" height="32" rx="4"/>
+      <text x="232" y="75" textAnchor="middle" className="lbl-s mono">
+        EURC
+      </text>
+      <rect className="cell slot s4 anim" x="268" y="54" width="56" height="32" rx="4"/>
+      <text x="296" y="75" textAnchor="middle" className="lbl-s mono">
+        wBTC
+      </text>
+      <rect className="cell slot s5 anim" x="332" y="54" width="56" height="32" rx="4"/>
+      <text x="360" y="75" textAnchor="middle" className="lbl-s mono">
+        wETH
+      </text>
+      <rect className="cell slot s6 anim" x="396" y="54" width="48" height="32" rx="4"/>
+      <text x="420" y="75" textAnchor="middle" className="lbl-s mono">
+        …30
+      </text>
+      <g className="reject anim">
+        <rect className="cell stroke-danger" x="530" y="54" width="56" height="32" rx="4"/>
+        <text x="558" y="75" textAnchor="middle" className="lbl-s mono fill-danger">
+          #31
+        </text>
+      </g>
+      <text x="558" y="114" textAnchor="middle" className="lbl-s panic anim fill-danger">
+        <tspan x="558">rejected: contract&apos;s own cap</tspan>
+        <tspan x="558" dy="14">
+          — not a network limit
+        </tspan>
+      </text>
+      <text x="260" y="130" textAnchor="middle" className="lbl-s">
+        whole list read in 1 footprint entry · iterate in memory
+      </text>
+    </svg>),
+    d7: (<svg viewBox="0 0 660 200" role="img" aria-label="Animation: a packed entry rewrites the whole blob on any update, while split entries update one small piece at a time.">
+      <text x="165" y="24" textAnchor="middle" className="lbl">
+        packed — read/written together
+      </text>
+      <rect className="cell cell-pers wholeblob anim" x="55" y="36" width="220" height="92" rx="8"/>
+      <text x="165" y="58" textAnchor="middle" className="lbl-s mono fill-ink">
+        Positions(user)
+      </text>
+      <text x="165" y="78" textAnchor="middle" className="lbl-s mono fill-ink">
+        liabilities · collateral · supply
+      </text>
+      <text x="165" y="98" textAnchor="middle" className="lbl-s fill-ink">
+        all user positions = 1 read
+      </text>
+      <text x="165" y="150" textAnchor="middle" className="lbl-s u1 anim">
+        any update rewrites the whole blob
+      </text>
+
+      <line className="wire dashed" x1="330" y1="30" x2="330" y2="170"/>
+
+      <text x="495" y="24" textAnchor="middle" className="lbl">
+        split — updated independently
+      </text>
+      <rect className="cell cell-pers onefield anim" x="390" y="36" width="210" height="24" rx="4"/>
+      <text x="495" y="52" textAnchor="middle" className="lbl-s mono fill-ink">
+        ResData(asset) — rates, hot
+      </text>
+      <rect className="cell cell-pers" x="390" y="68" width="210" height="24" rx="4"/>
+      <text x="495" y="84" textAnchor="middle" className="lbl-s mono">
+        ResConfig(asset) — admin, cold
+      </text>
+      <text x="495" y="150" textAnchor="middle" className="lbl-s u2 anim">
+        hot data updates without rewriting cold config
+      </text>
+      <text x="330" y="188" textAnchor="middle" className="lbl-s">
+        heuristic: pack data usually read and written together
+      </text>
+    </svg>),
+    d8: (<svg viewBox="0 0 660 214" role="img" aria-label="Animation: swap-and-pop removal in four steps — read the last item, move it into the removed slot, fix its reverse pointer, remove the tail — all in constant time.">
+      <text x="330" y="22" textAnchor="middle" className="lbl">
+        remove C from &#123;A B C D E&#125; — swap-and-pop, O(1)
+      </text>
+      <text x="93" y="52" textAnchor="middle" className="lbl-s mono">
+        idx 0
+      </text>
+      <text x="225" y="52" textAnchor="middle" className="lbl-s mono">
+        idx 1
+      </text>
+      <text x="357" y="52" textAnchor="middle" className="lbl-s mono">
+        idx 2
+      </text>
+      <text x="489" y="52" textAnchor="middle" className="lbl-s mono">
+        idx 3
+      </text>
+      <text x="621" y="52" textAnchor="middle" className="lbl-s mono">
+        idx 4
+      </text>
+      <rect className="cell cell-pers" x="45" y="62" width="96" height="40" rx="5"/>
+      <text x="93" y="87" textAnchor="middle" className="lbl mono fill-ink">
+        A
+      </text>
+      <rect className="cell cell-pers" x="177" y="62" width="96" height="40" rx="5"/>
+      <text x="225" y="87" textAnchor="middle" className="lbl mono fill-ink">
+        B
+      </text>
+      <g className="gone anim">
+        <rect className="cell cell-pers" x="309" y="62" width="96" height="40" rx="5"/>
+        <text x="357" y="87" textAnchor="middle" className="lbl mono fill-ink">
+          C
+        </text>
+      </g>
+      <rect className="cell cell-pers" x="441" y="62" width="96" height="40" rx="5"/>
+      <text x="489" y="87" textAnchor="middle" className="lbl mono fill-ink">
+        D
+      </text>
+      <g className="mover anim">
+        <rect className="cell cell-pers" x="573" y="62" width="96" height="40" rx="5"/>
+        <text x="621" y="87" textAnchor="middle" className="lbl mono fill-ink">
+          E
+        </text>
+      </g>
+      <rect className="cell tail anim fill-none dashed" x="573" y="62" width="96" height="40" rx="5"/>
+      <text x="264" y="122" className="lbl-s note1 anim">
+        1 · read the last item
+      </text>
+      <text x="264" y="138" className="lbl-s note2 anim">
+        2 · move it into the hole
+      </text>
+      <text x="264" y="154" className="lbl-s note3 anim">
+        3 · fix its reverse pointer
+      </text>
+      <text x="264" y="170" className="lbl-s note4 anim">
+        4 · remove the tail
+      </text>
+      <text x="330" y="200" textAnchor="middle" className="lbl-s">
+        a constant number of entry updates, regardless of set size — order is
+        not preserved
+      </text>
+    </svg>),
+    d9: (<svg viewBox="0 0 660 216" role="img" aria-label="Animation: a global cumulative index rises over time; a user who shows up settles only their own delta into accrued; everyone else's entries are untouched.">
+      <text x="330" y="22" textAnchor="middle" className="lbl">
+        global entry — cumulative rewards-per-share, only ever increases
+      </text>
+      <rect className="cell cell-pers" x="130" y="32" width="400" height="34" rx="6"/>
+      <rect className="ttl-track" x="146" y="45" width="368" height="8"/>
+      <rect className="bar gidx anim ttl-fill-pers" x="146" y="45" width="368" height="8"/>
+      <text x="330" y="86" textAnchor="middle" className="lbl-s mono">
+        index: 1.0842… ↑ (advanced lazily when emissions are updated)
+      </text>
+
+      <g className="alice anim">
+        <rect className="cell cell-pers" x="80" y="118" width="180" height="64" rx="6"/>
+        <text x="170" y="136" textAnchor="middle" className="lbl-s mono">
+          UserEmis(alice)
+        </text>
+        <text x="170" y="152" textAnchor="middle" className="lbl-s mono">
+          index: 0.9310 → 1.0842
+        </text>
+        <text x="170" y="168" textAnchor="middle" className="lbl-s mono">
+          accrued: 12.40 → 27.72
+        </text>
+      </g>
+      <line className="wire dline anim stroke-teal" x1="220" y1="66" x2="185" y2="116"/>
+      <text x="170" y="202" textAnchor="middle" className="lbl-s delta anim fill-teal">
+        accrued += shares × Δindex — settles when alice shows up
+      </text>
+
+      <g className="ghost anim">
+        <rect className="cell dashed" x="330" y="118" width="130" height="64" rx="6"/>
+        <text x="395" y="144" textAnchor="middle" className="lbl-s mono">
+          UserEmis(bob)
+        </text>
+        <text x="395" y="161" textAnchor="middle" className="lbl-s">
+          untouched
+        </text>
+        <rect className="cell dashed" x="474" y="118" width="130" height="64" rx="6"/>
+        <text x="539" y="144" textAnchor="middle" className="lbl-s mono">
+          …× 10,000
+        </text>
+        <text x="539" y="161" textAnchor="middle" className="lbl-s">
+          untouched
+        </text>
+      </g>
+    </svg>),
+    d10: (<svg viewBox="0 0 660 216" role="img" aria-label="Animation: voting-power checkpoints append as one persistent entry per change; a query for a past ledger binary-searches the indexed entries and lands on the last checkpoint at or before it.">
+      <text x="330" y="20" textAnchor="middle" className="lbl">
+        alice&apos;s voting power — one persistent checkpoint entry per change
+      </text>
+      <text x="105" y="44" textAnchor="middle" className="lbl-s mono">
+        idx 0
+      </text>
+      <text x="245" y="44" textAnchor="middle" className="lbl-s mono">
+        idx 1
+      </text>
+      <text x="385" y="44" textAnchor="middle" className="lbl-s mono">
+        idx 2
+      </text>
+      <text x="525" y="44" textAnchor="middle" className="lbl-s mono">
+        idx 3
+      </text>
+      <g className="cp1 anim">
+        <rect className="cell cell-pers" x="45" y="52" width="120" height="44" rx="5"/>
+        <text x="105" y="70" textAnchor="middle" className="lbl-s mono">
+          ledger 100
+        </text>
+        <text x="105" y="86" textAnchor="middle" className="lbl-s mono">
+          votes 40
+        </text>
+      </g>
+      <g className="cp2 anim">
+        <rect className="cell cell-pers" x="185" y="52" width="120" height="44" rx="5"/>
+        <text x="245" y="70" textAnchor="middle" className="lbl-s mono">
+          ledger 250
+        </text>
+        <text x="245" y="86" textAnchor="middle" className="lbl-s mono">
+          votes 90
+        </text>
+      </g>
+      <g className="cp3 anim">
+        <rect className="cell cell-pers pr2 anim" x="325" y="52" width="120" height="44" rx="5"/>
+        <text x="385" y="70" textAnchor="middle" className="lbl-s mono">
+          ledger 400
+        </text>
+        <text x="385" y="86" textAnchor="middle" className="lbl-s mono">
+          votes 75
+        </text>
+      </g>
+      <g className="cp4 anim">
+        <rect className="cell cell-pers pr3 anim" x="465" y="52" width="120" height="44" rx="5"/>
+        <text x="525" y="70" textAnchor="middle" className="lbl-s mono">
+          ledger 620
+        </text>
+        <text x="525" y="86" textAnchor="middle" className="lbl-s mono">
+          votes 130
+        </text>
+      </g>
+      <rect className="winring anim" x="325" y="52" width="120" height="44" rx="5"/>
+      <text x="330" y="122" textAnchor="middle" className="lbl-s cnt anim">
+        NumCheckpoints(alice) → 4 — writes touch only the tail + counter
+      </text>
+      <text x="330" y="148" textAnchor="middle" className="lbl q anim fill-ink">
+        voting power at ledger 500? → binary-search the indexes
+      </text>
+      <text x="525" y="172" textAnchor="middle" className="lbl-s mono plbl3 anim fill-danger">
+        620 &gt; 500 ✗
+      </text>
+      <text x="385" y="172" textAnchor="middle" className="lbl-s mono plbl2 anim fill-teal">
+        400 ≤ 500 ✓
+      </text>
+      <text x="330" y="200" textAnchor="middle" className="lbl-s ans anim">
+        last checkpoint at or before ledger 500 → 75 votes · each probe reads
+        one entry
+      </text>
+    </svg>),
+    d11: (<svg viewBox="0 0 660 232" role="img" aria-label="Animation: a whole airdrop list collapses to a 32-byte Merkle root on-chain; to claim, alice re-submits her record plus proof, the path from her leaf to the root lights back up as the contract re-hashes it, and only a small Claimed(0) flag is written.">
+      <g className="leaves anim">
+        <rect className="cell" x="180" y="140" width="100" height="30" rx="4"/>
+        <text x="230" y="159" textAnchor="middle" className="lbl-s mono">
+          bob, 1200
+        </text>
+        <rect className="cell" x="300" y="140" width="100" height="30" rx="4"/>
+        <text x="350" y="159" textAnchor="middle" className="lbl-s mono">
+          carol, 90
+        </text>
+        <rect className="cell" x="420" y="140" width="100" height="30" rx="4"/>
+        <text x="470" y="159" textAnchor="middle" className="lbl-s mono">
+          …10,000 more
+        </text>
+        <line className="wire" x1="230" y1="140" x2="170" y2="106"/>
+        <line className="wire" x1="350" y1="140" x2="410" y2="106"/>
+        <line className="wire" x1="470" y1="140" x2="410" y2="106"/>
+        <rect className="cell" x="370" y="82" width="80" height="24" rx="4"/>
+        <text x="410" y="98" textAnchor="middle" className="lbl-s mono">
+          h₂₃
+        </text>
+        <line className="wire" x1="410" y1="82" x2="290" y2="52"/>
+      </g>
+      <g className="proof anim">
+        <rect className="cell anim" x="60" y="140" width="100" height="30" rx="4"/>
+        <text x="110" y="159" textAnchor="middle" className="lbl-s mono">
+          alice, 500
+        </text>
+        <line className="wire" x1="110" y1="140" x2="170" y2="106"/>
+        <rect className="cell anim" x="130" y="82" width="80" height="24" rx="4"/>
+        <text x="170" y="98" textAnchor="middle" className="lbl-s mono">
+          h₀₁
+        </text>
+        <line className="wire" x1="170" y1="82" x2="290" y2="52"/>
+      </g>
+      <text x="290" y="196" textAnchor="middle" className="lbl-s">
+        the full list lives off-chain
+      </text>
+      <text x="290" y="214" textAnchor="middle" className="lbl-s claimcap anim">
+        to claim, alice brings her record + proof — the contract re-hashes her
+        path back to the root
+      </text>
+      <rect className="cell root anim stroke-ink" x="230" y="26" width="120" height="28" rx="5"/>
+      <text x="290" y="45" textAnchor="middle" className="lbl-s mono fill-ink">
+        RootHash
+      </text>
+      <text x="222" y="44" textAnchor="end" className="lbl-s onchain anim fill-ink">
+        32-byte root in instance storage →
+      </text>
+      <g className="claim anim">
+        <rect className="cell" x="372" y="26" width="104" height="28" rx="5"/>
+        <text x="424" y="45" textAnchor="middle" className="lbl-s mono">
+          Claimed(0)
+        </text>
+        <text x="488" y="44" className="lbl-s">
+          ← one flag per actual claim
+        </text>
+      </g>
+    </svg>),
+    d12: (<svg viewBox="0 0 660 210" role="img" aria-label="Animation: a factory contract deploys one contract per trading pair and keeps the pair registry plus factory configuration; each deployed contract gets its own storage domain.">
+      <rect className="cell stroke-ink" x="40" y="46" width="150" height="120" rx="10"/>
+      <text x="115" y="72" textAnchor="middle" className="lbl fill-ink">
+        factory
+      </text>
+      <text x="115" y="94" textAnchor="middle" className="lbl-s">
+        registry + factory config
+      </text>
+      <g className="reg1 anim">
+        <text x="115" y="114" textAnchor="middle" className="lbl-s mono">
+          0 → pair XLM/USDC
+        </text>
+      </g>
+      <g className="reg2 anim">
+        <text x="115" y="130" textAnchor="middle" className="lbl-s mono">
+          1 → pair XLM/EURC
+        </text>
+      </g>
+      <g className="reg3 anim">
+        <text x="115" y="146" textAnchor="middle" className="lbl-s mono">
+          2 → pair BTC/USDC
+        </text>
+      </g>
+
+      <line className="wire dashed w1 anim" x1="190" y1="80" x2="268" y2="60"/>
+      <line className="wire dashed w2 anim" x1="190" y1="106" x2="268" y2="106"/>
+      <line className="wire dashed w3 anim" x1="190" y1="132" x2="268" y2="152"/>
+
+      <g className="pair pr1 anim">
+        <rect className="cell cell-inst" x="270" y="36" width="170" height="46" rx="8"/>
+        <text x="355" y="56" textAnchor="middle" className="lbl-s mono">
+          pair XLM/USDC
+        </text>
+        <text x="355" y="72" textAnchor="middle" className="lbl-s">
+          own instance · own TTLs
+        </text>
+      </g>
+      <g className="pair pr2 anim">
+        <rect className="cell cell-inst" x="270" y="88" width="170" height="46" rx="8"/>
+        <text x="355" y="108" textAnchor="middle" className="lbl-s mono">
+          pair XLM/EURC
+        </text>
+        <text x="355" y="124" textAnchor="middle" className="lbl-s">
+          own instance · own TTLs
+        </text>
+      </g>
+      <g className="pair pr3 anim">
+        <rect className="cell cell-inst" x="270" y="140" width="170" height="46" rx="8"/>
+        <text x="355" y="160" textAnchor="middle" className="lbl-s mono">
+          pair BTC/USDC
+        </text>
+        <text x="355" y="176" textAnchor="middle" className="lbl-s">
+          own instance · own TTLs
+        </text>
+      </g>
+      <g className="iso anim">
+        <text x="545" y="100" textAnchor="middle" className="lbl-s fill-teal">
+          independent storage domains:
+        </text>
+        <text x="545" y="118" textAnchor="middle" className="lbl-s fill-teal">
+          pair-local entries do not conflict across pairs
+        </text>
+      </g>
+    </svg>),
+};
+
+  const id = `d${n}`;
+  const caption = CAPTIONS[id];
+  const children = SVGS[id];
+
+  // The first diagram carries the stylesheet so it is present on first paint; the effect covers pages without it.
+  useEffect(() => {
+    if (document.getElementById("ssd-styles")) return;
+    const style = document.createElement("style");
+    style.id = "ssd-styles";
+    style.textContent = CSS;
+    document.head.appendChild(style);
+  }, []);
+
+    const ref = useRef(null);
+    // .play must live in React state: it gates animation-play-state in CSS, and
+    // an imperatively added class would be dropped on the next re-render.
+    const [playing, setPlaying] = useState(false);
+    const [restored, setRestored] = useState({
+        instance: false,
+        persistent: false,
+    });
+    useEffect(() => {
+        const el = ref.current;
+        if (!el) {
+            return undefined;
+        }
+        const io = new IntersectionObserver((entries) => {
+            entries.forEach((entry) => {
+                if (entry.isIntersecting) {
+                    setPlaying(true);
+                    io.unobserve(el);
+                }
+            });
+        }, { threshold: 0.45 });
+        io.observe(el);
+        return () => io.disconnect();
+    }, []);
+    const replay = () => {
+        const el = ref.current;
+        if (!el) {
+            return;
+        }
+        setRestored({ instance: false, persistent: false });
+        setPlaying(true);
+        // Toggling .play only pauses/resumes; to restart from frame 0 the
+        // animations themselves must be torn down and recreated.
+        const anims = el.querySelectorAll(".anim");
+        anims.forEach((a) => {
+            a.style.animation = "none";
+        });
+        void el.offsetWidth;
+        anims.forEach((a) => {
+            a.style.animation = "";
+        });
+    };
+    const className = [
+        "ssd",
+        playing ? "play" : "",
+        restored.instance ? "restored-instance" : "",
+        restored.persistent ? "restored-persistent" : "",
+    ]
+        .filter(Boolean)
+        .join(" ");
+    return (<div className={className} id={id} ref={ref}>
+      {n === 0 ? <style id="ssd-styles-inline">{CSS}</style> : null}
+      <div className="diagram-controls">
+        {id === "d0" ? (<>
+            <button className="restore" type="button" aria-pressed={restored.instance} onClick={() => setRestored((current) => ({ ...current, instance: true }))}>
+              Restore instance
+            </button>
+            <button className="restore" type="button" aria-pressed={restored.persistent} onClick={() => setRestored((current) => ({ ...current, persistent: true }))}>
+              Restore persistent entry
+            </button>
+          </>) : null}
+        <button className="replay" type="button" onClick={replay}>
+          {id === "d0" ? "↻ Replay expiry" : "↻ Replay"}
+        </button>
+      </div>
+      {children}
+      {caption ? <p className="caption">{caption}</p> : null}
+    </div>);
+};
diff --git a/snippets/usdt0-launch.jsx b/snippets/usdt0-launch.jsx
new file mode 100644
index 000000000..953f66d57
--- /dev/null
+++ b/snippets/usdt0-launch.jsx
@@ -0,0 +1,859 @@
+
+export const Usdt0Launch = () => {
+  const CSS = `
+@import url('https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500&family=Inter:wght@400..600&display=swap');
+/* Every rule is scoped under .usdt0 so nothing leaks into the Mintlify chrome.
+   Dark mode follows Mintlify's html.dark class. --usdt0-top is where the sticky
+   section bar parks; 0 because the Mintlify navbar is hidden on this page. */
+.usdt0{
+  --paper:#FFFFFF; --paper-2:#F9F9F9; --paper-3:#F2F2F2;
+  --ink:#0F0F0F; --ink-2:#4A4A4A; --ink-3:#6B6B6B;
+  --rule:#D8D8D8; --rule-2:#E6E6E6;
+  --accent:#FDDA24; --accent-soft:#FDDA2440;
+  --accent-ink:#7A5C00; --on-accent:#0F0F0F;
+  --usdt0-top:0px;
+}
+/* the launch page carries its own header, so the Mintlify navbar is hidden.
+   This stylesheet only exists while the component is mounted, so other pages keep theirs. */
+#navbar{display:none !important}
+html.dark .usdt0{
+  --paper:#0F0F0F; --paper-2:#191919; --paper-3:#080808;
+  --ink:#F5F5F0; --ink-2:#B8B8B0; --ink-3:#8E8E86;
+  --rule:#474747; --rule-2:#333333;
+  --accent:#FDDA24; --accent-soft:#FDDA2422;
+  --accent-ink:#FDDA24; --on-accent:#0F0F0F;
+}
+.usdt0,.usdt0 *{box-sizing:border-box}
+.usdt0{
+  background:var(--paper); color:var(--ink);
+  font-family:"Inter","Helvetica Neue",Arial,sans-serif;
+  font-size:15px; line-height:1.6; -webkit-font-smoothing:antialiased;
+}
+.usdt0 a{color:inherit;text-decoration:none;font-weight:inherit}
+.usdt0 code::before,.usdt0 code::after{content:none}
+.usdt0 .sheet{max-width:1300px;margin:0 auto;padding:22px 24px 64px}
+/* ---------- header ---------- */
+/* sticky, so the section markers stay useful once you have scrolled past them */
+.usdt0 .top{
+  position:sticky;top:var(--usdt0-top);z-index:20;background:var(--paper);
+  display:flex;align-items:center;justify-content:space-between;gap:20px;
+  font-family:"IBM Plex Mono",ui-monospace,monospace;
+  font-size:11px;letter-spacing:.14em;text-transform:uppercase;color:var(--ink-2);
+  border-bottom:1px solid var(--rule);padding:12px 0 10px;
+}
+.usdt0 .secnav{display:flex;gap:5px;align-items:center}
+.usdt0 .top-r{display:flex;align-items:center;gap:18px}
+.usdt0 .toplink{color:var(--ink-2);text-decoration:none;border-bottom:1px solid var(--rule);
+         letter-spacing:inherit;white-space:nowrap}
+.usdt0 .toplink:hover{color:var(--accent-ink);border-bottom-color:var(--accent-ink)}
+.usdt0 .toplink:focus-visible{outline:2px solid var(--accent-ink);outline-offset:3px}
+@media (max-width:560px){ .usdt0 .toplink{display:none} }
+.usdt0 .tick{
+  width:11px;height:11px;border:1px solid var(--ink-2);
+  background:transparent;display:block;
+  transition:background .15s ease,border-color .15s ease;
+}
+.usdt0 .tick:hover{border-color:var(--accent-ink);background:var(--accent-soft)}
+.usdt0 .tick[aria-current="true"]{background:var(--accent);border-color:var(--accent-ink)}
+.usdt0 .tick:focus-visible{outline:2px solid var(--accent-ink);outline-offset:3px}
+/* the tick stays 11px to look at and gets an invisible target around it. The
+   horizontal reach is tied to the gap so neighbours never overlap: 15px wide
+   on a mouse, and on touch the gap opens up so the target clears the 24x24
+   minimum. Vertical reach is free either way. */
+.usdt0 .tick{position:relative}
+.usdt0 .tick::after{content:"";position:absolute;inset:-16px -2px}
+@media (pointer:coarse){
+  .usdt0 .secnav{gap:16px}
+  .usdt0 .tick::after{inset:-16px -8px}
+}
+/* the wider touch gap costs the header its single line at phone widths, so the
+   label tightens to compensate rather than wrapping */
+@media (max-width:430px){ .usdt0 .top{font-size:10px;letter-spacing:.10em} }
+/* anchor jumps must clear the Mintlify navbar and the sticky bar */
+.usdt0 figure[id],.usdt0 section[id]{scroll-margin-top:calc(var(--usdt0-top) + 64px)}
+/* Inter needs display tuning the condensed face did not: more negative
+   tracking, and a little more leading for its taller x-height and longer
+   descenders. The accent is a block so the color change lands on the line
+   break instead of stranding a word at the end of line one. */
+.usdt0 h1{
+  font-family:"Inter","Helvetica Neue",Arial,sans-serif;color:var(--ink);
+  font-weight:600;font-size:clamp(34px,5.4vw,58px);line-height:1.06;
+  letter-spacing:-.03em;margin:26px 0 10px;max-width:24ch;text-wrap:balance;
+}
+.usdt0 h1 em{display:block;font-style:normal;color:var(--accent-ink)}
+.usdt0 .deck{max-width:62ch;color:var(--ink-2);font-size:17px;margin:0 0 8px}
+.usdt0 .deck strong{color:var(--ink);font-weight:500}
+/* ---------- figure chrome ---------- */
+.usdt0 figure{margin:34px 0 0;border:1px solid var(--rule);background:var(--paper-2)}
+.usdt0 .fig-head{
+  display:flex;justify-content:space-between;gap:16px;flex-wrap:wrap;
+  border-bottom:1px solid var(--rule);padding:9px 14px;
+  font-family:"IBM Plex Mono",ui-monospace,monospace;font-size:10.5px;
+  letter-spacing:.13em;text-transform:uppercase;color:var(--ink-2);
+}
+.usdt0 .fig-body{padding:16px 14px;overflow-x:auto}
+.usdt0 .fig-body>svg{min-width:620px}
+.usdt0 figcaption{
+  border-top:1px solid var(--rule);padding:10px 14px;
+  font-size:13.5px;color:var(--ink-2);
+}
+.usdt0 svg{display:block;max-width:100%;height:auto}
+.usdt0 .n-box{fill:var(--paper-2);stroke:currentColor;stroke-width:1}
+.usdt0 .n-box.alt{fill:var(--paper-3)}
+.usdt0 .n-box.hot{stroke:var(--accent-ink);stroke-width:1.6;fill:var(--accent-soft)}
+.usdt0 .n-t{font-family:"Inter","Helvetica Neue",Arial,sans-serif;font-weight:600;font-size:14px;fill:currentColor}
+.usdt0 .n-t.hot{fill:var(--accent-ink)}
+.usdt0 .n-s{font-family:"IBM Plex Mono",monospace;font-size:10px;fill:var(--ink);letter-spacing:.04em}
+.usdt0 .edge{stroke:currentColor;stroke-width:1;fill:none}
+.usdt0 .edge.dash{stroke-dasharray:5 4;stroke:var(--ink-3)}
+/* One 12.5s cycle tells the whole story once: a packet leaves Ethereum, splits
+   at the fork, both halves land together, the far-chain half climbs into the
+   Stellar OFT, and one packet carries on. Every leg runs at the same ~55px/s —
+   each duration is that path's measured length over that rate — so the pacing
+   is uniform even though the legs are different lengths. Boxes light on arrival. */
+.usdt0 .pkt{fill:var(--accent-ink);opacity:0}
+.usdt0 .lit{fill:var(--accent-soft);stroke:var(--accent-ink);stroke-width:1.6;opacity:0}
+.usdt0 .pkt.pTrunk{offset-path:path("M 184 201 H 232");animation:usdt0-pTrunk 12.5s linear infinite}
+@keyframes usdt0-pTrunk{0%,0.00%{offset-distance:0%;opacity:0}0.50%{opacity:1}6.70%{opacity:1}7.20%,100%{offset-distance:100%;opacity:0}}
+.usdt0 .pkt.pUp{offset-path:path("M 232 201 V 110 H 286");animation:usdt0-pUp 12.5s linear infinite}
+@keyframes usdt0-pUp{0%,7.20%{offset-distance:0%;opacity:0}8.66%{opacity:1}26.54%{opacity:1}28.00%,100%{offset-distance:100%;opacity:0}}
+.usdt0 .pkt.pDown{offset-path:path("M 232 201 V 292 H 286");animation:usdt0-pDown 12.5s linear infinite}
+@keyframes usdt0-pDown{0%,7.20%{offset-distance:0%;opacity:0}8.66%{opacity:1}26.54%{opacity:1}28.00%,100%{offset-distance:100%;opacity:0}}
+.usdt0 .pkt.pClimb{offset-path:path("M 384 254 V 168");animation:usdt0-pClimb 12.5s linear infinite}
+@keyframes usdt0-pClimb{0%,32.80%{offset-distance:0%;opacity:0}33.86%{opacity:1}46.94%{opacity:1}48.00%,100%{offset-distance:100%;opacity:0}}
+.usdt0 .pkt.pMint{offset-path:path("M 478 110 H 528 V 201 H 574");animation:usdt0-pMint 12.5s linear infinite}
+@keyframes usdt0-pMint{0%,52.00%{offset-distance:0%;opacity:0}53.90%{opacity:1}77.30%{opacity:1}79.20%,100%{offset-distance:100%;opacity:0}}
+.usdt0 .pkt.pUse1{offset-path:path("M 764 171 H 812");animation:usdt0-pUse 12.5s linear infinite}
+.usdt0 .pkt.pUse2{offset-path:path("M 764 201 H 812");animation:usdt0-pUse 12.5s linear infinite}
+.usdt0 .pkt.pUse3{offset-path:path("M 764 231 H 812");animation:usdt0-pUse 12.5s linear infinite}
+@keyframes usdt0-pUse{0%,82.40%{offset-distance:0%;opacity:0}82.90%{opacity:1}89.10%{opacity:1}89.60%,100%{offset-distance:100%;opacity:0}}
+.usdt0 .lit.lEth{animation:usdt0-lEth 12.5s linear infinite}
+@keyframes usdt0-lEth{0%{opacity:0}0.00%{opacity:0}1.20%{opacity:1}4.40%{opacity:0}100%{opacity:0}}
+.usdt0 .lit.lOft{animation:usdt0-lOft 12.5s linear infinite}
+@keyframes usdt0-lOft{0%{opacity:0}28.00%{opacity:0}29.20%{opacity:1}32.40%{opacity:0}48.00%{opacity:0}49.20%{opacity:1}52.40%{opacity:0}100%{opacity:0}}
+.usdt0 .lit.lChain{animation:usdt0-lChain 12.5s linear infinite}
+@keyframes usdt0-lChain{0%{opacity:0}28.00%{opacity:0}29.20%{opacity:1}32.40%{opacity:0}100%{opacity:0}}
+.usdt0 .lit.lHot{animation:usdt0-lHot 12.5s linear infinite}
+@keyframes usdt0-lHot{0%{opacity:0}79.20%{opacity:0}80.40%{opacity:1}83.60%{opacity:0}100%{opacity:0}}
+.usdt0 .lit.lUse{animation:usdt0-lUse 12.5s linear infinite}
+@keyframes usdt0-lUse{0%{opacity:0}89.60%{opacity:0}90.80%{opacity:1}94.00%{opacity:0}100%{opacity:0}}
+/* ---------- fig 2: the USDT0 folder ---------- */
+/* One folder — USDT0 — with its layers stacked behind its cover, offset
+   down-left so every name stays readable. Percentage geometry, so the stack
+   scales instead of scrolling. */
+.usdt0 .fig-files{padding:0 40px 30px}
+.usdt0 .folder-fig{display:flex;gap:34px;align-items:flex-start;justify-content:center;padding:26px 40px 30px}
+.usdt0 .desc{flex:1 1 0;min-width:0;max-width:620px;display:flex;flex-direction:column;gap:12px}
+.usdt0 .d-eyebrow{
+  font-family:"IBM Plex Mono",monospace;font-size:10px;letter-spacing:.16em;
+  text-transform:uppercase;color:var(--accent-ink);
+}
+.usdt0 .d-head{
+  font-family:"Inter","Helvetica Neue",Arial,sans-serif;font-weight:600;
+  font-size:clamp(24px,2.6vw,36px);line-height:1.1;margin:0;
+  letter-spacing:-.022em;text-wrap:balance;color:var(--ink);
+}
+.usdt0 .d-claim{margin:0;font-size:15.5px;color:var(--ink);max-width:56ch}
+.usdt0 dl{margin:2px 0 0;display:flex;flex-direction:column;gap:12px;
+   border-top:1px solid var(--rule);padding-top:14px}
+.usdt0 dt{
+  font-family:"IBM Plex Mono",monospace;font-size:9.5px;letter-spacing:.14em;
+  text-transform:uppercase;color:var(--ink-2);margin-bottom:3px;font-weight:400;
+}
+.usdt0 dd{margin:0;font-size:14.5px;color:var(--ink-2);max-width:64ch}
+.usdt0 dd code{
+  font-family:"IBM Plex Mono",monospace;font-size:12.5px;
+  background:var(--paper-3);border:1px solid var(--rule-2);padding:.5px 4px;color:var(--ink);
+}
+/* source links: quiet by default, accent on hover — a claim you can check */
+.usdt0 dd a,.usdt0 .id-note a,.usdt0 .dep-note a,.usdt0 .ncopy a,.usdt0 figcaption a{
+  color:inherit;text-decoration:none;
+  border-bottom:1px solid var(--rule);
+}
+.usdt0 dd a:hover,.usdt0 .id-note a:hover,.usdt0 .dep-note a:hover,.usdt0 .ncopy a:hover,
+.usdt0 figcaption a:hover{
+  color:var(--accent-ink);border-bottom-color:var(--accent-ink);
+}
+.usdt0 dd a:focus-visible,.usdt0 .id-note a:focus-visible,
+.usdt0 .dep-note a:focus-visible,.usdt0 .ncopy a:focus-visible,.usdt0 figcaption a:focus-visible{
+  outline:2px solid var(--accent-ink);outline-offset:2px;border-bottom-color:transparent;
+}
+.usdt0 dd a code,.usdt0 .dep-note a code,.usdt0 .ncopy a code{border-bottom:0}
+.usdt0 .sources{
+  margin-top:26px;border-top:1px solid var(--rule);padding-top:10px;
+  display:flex;gap:18px;align-items:baseline;flex-wrap:wrap;
+  font-family:"IBM Plex Mono",monospace;font-size:10.5px;letter-spacing:.13em;
+  text-transform:uppercase;color:var(--ink-3);
+}
+.usdt0 .sources b{font-weight:400;color:var(--ink-3);margin-right:4px}
+.usdt0 .sources a{color:var(--ink-2);text-decoration:none;border-bottom:1px solid var(--rule)}
+.usdt0 .sources a:hover{color:var(--accent-ink);border-bottom-color:var(--accent-ink)}
+.usdt0 .sources a:focus-visible{outline:2px solid var(--accent-ink);outline-offset:3px}
+/* ---- questions: collapsed by default, but the answers stay in the DOM ---- */
+.usdt0 .faq{border-bottom:1px solid var(--rule)}
+.usdt0 .faq:last-child{border-bottom:0}
+
+.usdt0 .faq summary{
+  display:flex;gap:14px;align-items:baseline;list-style:none;cursor:pointer;
+  padding:11px 28px 11px 0;position:relative;
+}
+.usdt0 .faq summary::-webkit-details-marker{display:none}
+.usdt0 .faq summary::after{
+  content:"+";position:absolute;right:8px;top:10px;line-height:1;
+  font-family:"IBM Plex Mono",monospace;font-size:13px;color:var(--ink-3);
+}
+.usdt0 .faq[open] summary::after{content:"\\2212"}
+.usdt0 .faq summary:hover .fq{color:var(--accent-ink)}
+.usdt0 .faq summary:focus-visible{outline:2px solid var(--accent-ink);outline-offset:-2px}
+.usdt0 .fq{font-weight:500}
+.usdt0 .fq code,.usdt0 .fa code{font-size:.92em}
+.usdt0 .fa{padding:0 28px 16px 0;max-width:78ch}
+.usdt0 .fa .ncopy{margin:0}
+@media (max-width:720px){
+  .usdt0 .faq summary{padding-right:26px}
+}
+/* ---- the stack: folders in a folder ---- */
+/* back to front. Each folder's tab sits on the left of its top edge, and the
+   down-left offset keeps every tab uncovered. */
+.usdt0 .stackwrap{flex:0 0 clamp(250px,42%,520px);min-width:0;
+  /* the stack is shorter than the description beside it, so center it
+     rather than let the leftover height pool at the bottom of the panel */
+  align-self:center}
+.usdt0 .stack{position:relative;width:100%;aspect-ratio:var(--ar,1.316);container-type:inline-size}
+.usdt0 .file{
+  position:absolute;width:var(--fw,70.59%);height:var(--fh,61.29%);
+  text-align:left;transition:transform .16s ease;
+}
+.usdt0 .fo{position:absolute;inset:0;width:100%;height:100%;shape-rendering:geometricPrecision}
+/* fill and outline are separate paths: the tab is painted between them, so
+   the silhouette's stroke is drawn last and never gets covered. */
+.usdt0 .fo-body{fill:var(--paper)}
+.usdt0 .fo-tab{fill:none;transition:fill .16s ease}
+.usdt0 .fo-edge{
+  fill:none;stroke:var(--ink-2);stroke-width:1.5;
+  vector-effect:non-scaling-stroke;stroke-linejoin:round;
+  transition:stroke .16s ease,stroke-width .16s ease;
+}
+.usdt0 .fname{
+  position:absolute;left:0;top:0;width:40.97%;height:12.63%;
+  padding:0 5% 0 5.5%;display:flex;align-items:center;
+  font-family:"IBM Plex Mono",monospace;
+  font-size:clamp(6.5px,2.37cqw,11px);letter-spacing:.05em;color:var(--ink-2);
+  white-space:nowrap;overflow:hidden;text-overflow:ellipsis;
+  transition:color .16s ease;
+}
+.usdt0 .file:hover .fo-edge{stroke:var(--accent-ink)}
+.usdt0 .file:hover .fname{color:var(--accent-ink)}
+/* the cover: the folder these sit in */
+.usdt0 .cover .fo-body{fill:var(--paper)}
+.usdt0 .cover .fo-edge{stroke:var(--accent-ink);stroke-width:2}
+.usdt0 .cover .fo-tint{fill:var(--accent);opacity:.10}
+.usdt0 .cover .fname{color:var(--accent-ink)}
+.usdt0 .cover-body{position:absolute;left:5.5%;right:8%;top:24%}
+.usdt0 .cover-name{
+  display:block;font-family:"Inter","Helvetica Neue",Arial,sans-serif;font-weight:600;
+  font-size:clamp(15px,6.1cqw,29px);line-height:1.1;color:var(--accent-ink);
+  letter-spacing:-.01em;
+}
+.usdt0 .cover-sub{
+  display:block;margin-top:7%;font-family:"IBM Plex Mono",monospace;
+  font-size:clamp(7px,2.46cqw,12px);line-height:1.7;color:var(--ink-2);
+}
+/* ---- narrow: stack above, description below ---- */
+@media (max-width:820px){
+  .usdt0 .folder-fig{flex-direction:column;gap:22px;padding:20px 14px 24px}
+  .usdt0 .stackwrap{flex:0 0 auto;width:100%;max-width:380px;align-self:flex-start}
+  .usdt0 .desc{width:100%;max-width:none}
+  .usdt0 .d-claim,.usdt0 dd{max-width:none}
+}
+/* ---- access: the files shown at once, as benefits under the feature ---- */
+.usdt0 .files{
+  border-top:1px solid var(--rule);
+  display:grid; grid-template-columns:repeat(var(--cols,5),minmax(0,1fr));
+}
+.usdt0 .fcol{padding:18px 20px 4px; border-right:1px solid var(--rule);
+  display:flex; flex-direction:column}
+.usdt0 .fcol:last-child{border-right:0}
+.usdt0 .fcol:first-child{padding-left:0}
+.usdt0 .ftag{
+  font-family:"IBM Plex Mono",monospace; font-size:9.5px; letter-spacing:.14em;
+  text-transform:uppercase; color:var(--accent-ink); margin-bottom:7px;
+}
+.usdt0 .fhead{
+  font-family:"Inter","Helvetica Neue",Arial,sans-serif; font-weight:600;
+  font-size:19px; line-height:1.12; letter-spacing:-.01em; color:var(--ink); margin:0 0 9px;
+}
+.usdt0 .fcopy{margin:0 0 14px; font-size:13.5px; line-height:1.5; color:var(--ink-2)}
+@media (max-width:1000px){
+  .usdt0 .files{grid-template-columns:repeat(2,minmax(0,1fr))}
+  .usdt0 .fcol{border-bottom:1px solid var(--rule); padding-left:20px}
+  .usdt0 .fcol:first-child{padding-left:20px}
+  .usdt0 .fcol:nth-child(2n){border-right:0}
+  .usdt0 .fcol:nth-last-child(-n+2){border-bottom:0}
+}
+@media (max-width:620px){
+  .usdt0 .files{grid-template-columns:minmax(0,1fr)}
+  .usdt0 .fcol{border-right:0}
+  .usdt0 .fcol:last-child{border-bottom:0}
+}
+.usdt0 .dep-note b{color:var(--ink);font-weight:500}
+.usdt0 .dep-note{
+  border-top:1px solid var(--rule); padding:12px 20px;
+  font-size:13.5px; line-height:1.55; color:var(--ink-2);
+}
+.usdt0 .dep-note code{
+  font-family:"IBM Plex Mono",monospace;font-size:12.5px;
+  background:var(--paper-3);border:1px solid var(--rule-2);padding:.5px 4px;color:var(--ink);
+}
+.usdt0 .notes-sec{margin:34px 0 0;border:1px solid var(--rule);background:var(--paper-2)}
+.usdt0 .notes-body{padding:20px 20px 22px;display:flex;flex-direction:column;gap:18px}
+.usdt0 .notes{display:grid; grid-template-columns:repeat(2,minmax(0,1fr)); gap:18px 40px}
+.usdt0 .note{display:flex; gap:12px}
+.usdt0 .ntag{
+  flex:0 0 82px; font-family:"IBM Plex Mono",monospace; font-size:9.5px;
+  letter-spacing:.14em; text-transform:uppercase; color:var(--ink-3); padding-top:3px;
+}
+.usdt0 .ncopy{margin:0; font-size:13px; line-height:1.55; color:var(--ink-2)}
+.usdt0 .ncopy b{color:var(--ink);font-weight:500}
+.usdt0 .ncopy code{
+  font-family:"IBM Plex Mono",monospace;font-size:12px;
+  background:var(--paper-3);border:1px solid var(--rule-2);padding:.5px 4px;color:var(--ink);
+}
+@media (max-width:820px){ .usdt0 .notes{grid-template-columns:minmax(0,1fr)} }
+/* below this the two-column note squeezed its copy to about 25 characters a
+   line, so the tag sits above the copy instead of beside it */
+@media (max-width:560px){
+  .usdt0 .note{flex-direction:column; gap:4px}
+  .usdt0 .ntag{flex:0 0 auto; padding-top:0}
+}
+/* ---------- day one ---------- */
+.usdt0 .dayone{margin:34px 0 0;border:1px solid var(--rule);background:var(--paper-2)}
+.usdt0 .d1-body{padding:20px 20px 22px;display:flex;flex-direction:column;gap:20px}
+.usdt0 .d1-lead{margin:0;font-size:15.5px;color:var(--ink);max-width:64ch}
+.usdt0 .venues{display:grid;grid-template-columns:repeat(auto-fit,minmax(220px,1fr));gap:0;
+  border:1px solid var(--rule);background:var(--paper)}
+.usdt0 .venue{padding:15px 16px;border-right:1px solid var(--rule)}
+.usdt0 .venue:last-child{border-right:0}
+@media (max-width:720px){
+  .usdt0 .venue{border-right:0;border-bottom:1px solid var(--rule)}
+  .usdt0 .venue:last-child{border-bottom:0}
+}
+.usdt0 .venue h3{
+  margin:0 0 10px;font-family:"IBM Plex Mono",monospace;font-size:9.5px;line-height:1.6;
+  letter-spacing:.14em;text-transform:uppercase;color:var(--ink-3);font-weight:400;
+}
+.usdt0 .venue ul{margin:0;padding:0;list-style:none;display:flex;flex-wrap:wrap;gap:6px}
+.usdt0 .venue li{
+  margin:0;font-family:"IBM Plex Mono",monospace;font-size:11.5px;color:var(--ink);
+  border:1px solid var(--rule);background:var(--paper-2);padding:4px 8px;
+}
+.usdt0 .venue li::marker{content:none}
+.usdt0 .venue p{margin:10px 0 0;font-size:12.5px;color:var(--ink-2)}
+/* ---------- deploy section ---------- */
+.usdt0 .deploy{margin:34px 0 0;border:1px solid var(--rule);background:var(--paper-2)}
+.usdt0 .dep-head h2,.usdt0 .fig-head h2{font:inherit;letter-spacing:inherit;color:inherit;margin:0}
+.usdt0 .dep-head{
+  display:flex;justify-content:space-between;gap:16px;flex-wrap:wrap;align-items:center;
+  border-bottom:1px solid var(--rule);padding:9px 14px;
+  font-family:"IBM Plex Mono",ui-monospace,monospace;font-size:10.5px;
+  letter-spacing:.13em;text-transform:uppercase;color:var(--ink-2);
+}
+.usdt0 .live{
+  display:inline-flex;align-items:center;gap:6px;
+  color:var(--accent-ink);letter-spacing:.13em;
+}
+.usdt0 .live::before{
+  content:"";width:7px;height:7px;border-radius:50%;background:var(--accent-ink);
+}
+.usdt0 .dep-body{padding:20px 20px 22px;display:flex;flex-direction:column;gap:18px}
+.usdt0 .dep-lead{margin:0;font-size:15.5px;color:var(--ink);max-width:62ch}
+.usdt0 .dep-lead strong{font-weight:500}
+.usdt0 .dep-link{
+  align-self:flex-start;font-family:"IBM Plex Mono",monospace;font-size:11px;
+  letter-spacing:.06em;color:var(--accent-ink);text-decoration:none;
+  border-bottom:1px solid var(--accent-ink);padding-bottom:1px;
+}
+.usdt0 .dep-link:hover{color:var(--ink)}
+.usdt0 .dep-link:focus-visible{outline:2px solid var(--accent-ink);outline-offset:3px}
+.usdt0 .ids{display:flex;flex-direction:column;gap:0;border:1px solid var(--rule);background:var(--paper)}
+.usdt0 .id-row{
+  display:grid;grid-template-columns:minmax(0,240px) minmax(0,1fr);
+  gap:6px 20px;padding:14px 16px;border-bottom:1px solid var(--rule);
+}
+.usdt0 .id-row:last-child{border-bottom:0}
+@media (max-width:720px){.usdt0 .id-row{grid-template-columns:1fr}}
+.usdt0 .id-label{
+  font-family:"IBM Plex Mono",monospace;font-size:9.5px;letter-spacing:.14em;
+  text-transform:uppercase;color:var(--ink-3);
+}
+.usdt0 .id-note{font-size:13px;color:var(--ink-2);margin:4px 0 0;max-width:44ch}
+.usdt0 .id-val{display:flex;align-items:flex-start;gap:10px}
+.usdt0 .id-val code{
+  flex:1 1 auto;min-width:0;
+  font-family:"IBM Plex Mono",monospace;font-size:12.5px;line-height:1.55;
+  color:var(--ink);background:var(--paper-3);border:1px solid var(--rule-2);border-radius:0;
+  padding:6px 8px;overflow-wrap:anywhere;user-select:all;
+}
+.usdt0 .copy{
+  flex:0 0 auto;appearance:none;background:var(--paper-2);border:1px solid var(--rule);
+  color:var(--ink-2);font-family:"IBM Plex Mono",monospace;font-size:9.5px;
+  letter-spacing:.1em;text-transform:uppercase;padding:6px 9px;cursor:pointer;
+}
+.usdt0 .copy:hover{border-color:var(--accent-ink);color:var(--accent-ink)}
+.usdt0 .copy:focus-visible{outline:2px solid var(--accent-ink);outline-offset:2px}
+/* ---------- spec strip ---------- */
+.usdt0 .spec{
+  margin-top:34px;border:1px solid var(--rule);background:var(--paper-2);padding:0;
+  display:grid;grid-template-columns:repeat(auto-fit,minmax(168px,1fr));
+}
+.usdt0 .spec div{padding:12px 14px;border-right:1px solid var(--rule)}
+.usdt0 .spec div:last-child{border-right:0}
+.usdt0 .spec dt{margin-bottom:4px}
+.usdt0 .spec dd{
+  font-family:"IBM Plex Mono",monospace;font-size:14px;color:var(--ink);
+  font-variant-numeric:tabular-nums;
+}
+.usdt0 .spec dd a{color:inherit;text-decoration:none;border-bottom:1px solid var(--rule)}
+.usdt0 .spec dd a:hover{color:var(--accent-ink);border-bottom-color:var(--accent-ink)}
+.usdt0 .foot{
+  margin-top:26px;border-top:1px solid var(--rule);padding-top:10px;
+  font-family:"IBM Plex Mono",monospace;font-size:10.5px;letter-spacing:.13em;
+  text-transform:uppercase;color:var(--ink-3);
+  display:flex;justify-content:space-between;gap:16px;flex-wrap:wrap;
+}
+.usdt0 .xlink{display:inline-flex;align-items:center;color:var(--ink-3)}
+.usdt0 .xlink:hover{color:var(--accent-ink)}
+.usdt0 .xlink:focus-visible{outline:2px solid var(--accent-ink);outline-offset:3px}
+.usdt0 .xlink svg{width:13px;height:13px;display:block}
+@media (prefers-reduced-motion: reduce){
+  .usdt0 .pkt,.usdt0 .lit{animation:none;opacity:0}
+}
+`;
+  const SECTIONS = [
+    ["arrival", "Arrival"], ["access", "Access"], ["dayone", "Day one"], ["deploy", "Deploy"],
+    ["build", "Before you build"], ["faq", "FAQ"],
+  ];
+  const IDS = [
+    ["Classic asset", "The asset code and issuer address. A trustline points at this pair.", "USDT0:GATISXX6BZ6NC7IKQBY37CJD4SOZL3CYZJWXEDG6JVIY4WBS6KXJHN6Q"],
+    ["Token contract (SAC)", "The Stellar Smart Contract (Soroban) interface. Call this from contracts — lending markets, vaults, AMMs.", "CBSJZEIO5C7KC2SF3MKSNXXJSW5G3VTNBX4ATMKUI3B2MR4JKM4R26YF"],
+    ["OFT", "The USDT0-specific OFT contract on Stellar — it burns and mints USDT0 here. Not part of a Stellar-side payment.", "CBOWOLFSDM5PZXNFIVDMP5NZ7U2GSIHED6H6R446QOHF266XINKUMMF6"],
+    ["LayerZero endpoint ID", "Stellar's EID. You need it to address Stellar from another chain's OFT.", "30600"],
+  ];
+  // back to front: [name, left, top]; the cover sits in front at z-index 5
+  const FOLDERS = [
+    ["DISTRIBUTION", "24.99840625597654%", "0%"],
+    ["COLLATERAL", "18.748804691982407%", "8.391684189988943%"],
+    ["TREASURY", "12.49920312798827%", "16.783368379977887%"],
+    ["PAYMENTS", "6.249601563994135%", "25.17505256996683%"],
+  ];
+  const FO_BODY = "M 8 0 H 110 A 8 8 0 0 1 118 8 V 24 H 280 A 8 8 0 0 1 288 32 V 182 A 8 8 0 0 1 280 190 H 8 A 8 8 0 0 1 0 182 V 8 A 8 8 0 0 1 8 0 Z";
+  const FO_TAB = "M 8 0 H 110 A 8 8 0 0 1 118 8 V 25 H 0 V 8 A 8 8 0 0 1 8 0 Z";
+  const topRef = useRef(null);
+  const [active, setActive] = useState(0);
+  const [copyLabels, setCopyLabels] = useState({});
+  // which section is under the sticky bar. Ratio-based spying is biased by
+  // section height, so measure position against a fixed line just below the bar.
+  useEffect(() => {
+    let queued = false;
+    const spy = () => {
+      if (queued) return;
+      queued = true;
+      requestAnimationFrame(() => {
+        queued = false;
+        const bar = topRef.current;
+        const line = (bar ? bar.getBoundingClientRect().bottom : 0) + 32;
+        let idx = 0;
+        SECTIONS.forEach(([id], i) => {
+          const el = document.getElementById(id);
+          if (el && el.getBoundingClientRect().top <= line) idx = i;
+        });
+        // The final section is shorter than the viewport, so the page runs out of
+        // scroll before its top ever reaches the line and it could never go active.
+        // Once the document is scrolled to the end, the last section is the one
+        // being read, whatever the measurement says.
+        const sc = document.scrollingElement || document.documentElement;
+        if (sc.scrollTop + sc.clientHeight >= sc.scrollHeight - 2) idx = SECTIONS.length - 1;
+        setActive(idx);
+      });
+    };
+    window.addEventListener("scroll", spy, { passive: true });
+    window.addEventListener("resize", spy);
+    spy();
+    return () => {
+      window.removeEventListener("scroll", spy);
+      window.removeEventListener("resize", spy);
+    };
+  }, []);
+  const copy = (i) => {
+    const el = document.getElementById(`usdt0-id-${i}`);
+    const done = (msg) => {
+      setCopyLabels((c) => Object.assign({}, c, { [i]: msg }));
+      setTimeout(() => setCopyLabels((c) => Object.assign({}, c, { [i]: undefined })), 1600);
+    };
+    // clipboard access can be blocked in an embedded frame — select it instead
+    const selectIt = () => {
+      const range = document.createRange();
+      range.selectNodeContents(el);
+      const sel = window.getSelection();
+      sel.removeAllRanges();
+      sel.addRange(range);
+      done("Selected");
+    };
+    if (!navigator.clipboard) return selectIt();
+    navigator.clipboard.writeText(el.textContent).then(() => done("Copied"), selectIt);
+  };
+  const folder = (tint) => (
+    <svg className="fo" viewBox="0 0 288 190" preserveAspectRatio="none" aria-hidden="true">
+      <path className="fo-body" d={FO_BODY} />
+      {tint ? <path className="fo-tint" d={FO_BODY} /> : null}
+      <path className="fo-tab" d={FO_TAB} />
+      <path className="fo-edge" d={FO_BODY} />
+    </svg>
+  );
+  return (
+    <div className="usdt0">
+      <style dangerouslySetInnerHTML={{ __html: CSS }} />
+      <div className="sheet">
+        <div className="top" ref={topRef}>
+          <span>USDT0 on Stellar Network</span>
+          <span className="top-r">
+            <a className="toplink" href="/docs/tokens/usdt0-layerzero">Stellar Docs →</a>
+            <nav className="secnav" aria-label="Sections">
+              {SECTIONS.map(([id, label], i) => (
+                <a key={id} className="tick" href={`#${id}`} aria-label={label} title={label} aria-current={active === i ? "true" : undefined} />
+              ))}
+            </nav>
+          </span>
+        </div>
+        <h1>The asset with a unified supply <em>arrives on Stellar</em></h1>
+        <p className="deck">USDT0 is now available on the Stellar network. USDT0 connects Stellar to{" "}
+          <strong>a unified USDT supply</strong>, allowing USDT to move across networks without fragmenting
+          supply. USDT0 is a native Stellar asset that works with your existing stack.</p>
+        <figure id="arrival">
+          <div className="fig-head"><h2>Arrival — how USDT0 gets to Stellar</h2></div>
+          <div className="fig-body">
+            <svg viewBox="0 0 990 420" role="img" aria-label="The USDT0 supply chain. USDT on Ethereum is locked and unlocked with the USDT0 adapter. From there one flow forks: Ethereum mints USDT0 directly on Stellar through Stellar's own OFT contract, and Ethereum also mints USDT0 on every other USDT0 chain, with an OFT on each USDT0-compatible network. Any of those chains can burn its USDT0 so Stellar's OFT mints instead, which never touches Ethereum. Either way the Stellar OFT is the single entry point, and what it mints is USDT0 on Stellar, a native Stellar asset compatible with existing toolkits, which feeds payment rails, treasury balances, and lending markets. A dashed line shows the routes run the other way.">
+              <defs>
+                <marker id="usdt0-ar" viewBox="0 0 10 10" refX="9.4" refY="5" markerWidth="7" markerHeight="7" orient="auto-start-reverse">
+                  <path d="M0 0 L10 5 L0 10 z" fill="currentColor" />
+                </marker>
+                <marker id="usdt0-ar-s" viewBox="0 0 10 10" refX="9.4" refY="5" markerWidth="6.5" markerHeight="6.5" orient="auto-start-reverse">
+                  <path d="M0 0 L10 5 L0 10 z" fill="var(--ink-3)" />
+                </marker>
+              </defs>
+              <path className="edge dash" d="M 620 247 V 392 H 102 V 245" markerEnd="url(#usdt0-ar-s)" />
+              <rect className="n-box" x="20" y="161" width="164" height="80" />
+              <rect className="lit lEth" x="20" y="161" width="164" height="80" />
+              <text className="n-t" x="34" y="188">USDT on Ethereum</text>
+              <text className="n-s" x="34" y="207">Locked / unlocked</text>
+              <text className="n-s" x="34" y="222">with USDT0 adapter</text>
+              <path className="edge" d="M 184 201 H 232" />
+              <path className="edge" d="M 232 201 V 110 H 286" markerEnd="url(#usdt0-ar)" />
+              <path className="edge" d="M 232 201 V 292 H 286" markerEnd="url(#usdt0-ar)" />
+              <rect className="n-box alt" x="304" y="268" width="188" height="76" />
+              <rect className="n-box alt" x="297" y="261" width="188" height="76" />
+              <rect className="n-box" x="290" y="254" width="188" height="76" />
+              <rect className="lit lChain" x="290" y="254" width="188" height="76" />
+              <text className="n-t" x="304" y="282">USDT0 OFTs</text>
+              <text className="n-s" x="304" y="301">Each compatible network</text>
+              <text className="n-s" x="304" y="316">has its own contract</text>
+              <path className="edge" d="M 384 254 V 168" markerEnd="url(#usdt0-ar)" />
+              <rect className="n-box" x="290" y="72" width="188" height="92" />
+              <rect className="lit lOft" x="290" y="72" width="188" height="92" />
+              <text className="n-t" x="304" y="100">Stellar OFT</text>
+              <text className="n-s" x="304" y="119">The contract that</text>
+              <text className="n-s" x="304" y="134">mints and burns</text>
+              <text className="n-s" x="304" y="149">USDT0 on Stellar</text>
+              <path className="edge" d="M 478 110 H 528 V 201 H 574" markerEnd="url(#usdt0-ar)" />
+              <rect className="n-box hot" x="578" y="155" width="186" height="92" />
+              <rect className="lit lHot" x="578" y="155" width="186" height="92" />
+              <text className="n-t hot" x="592" y="182">USDT0 on Stellar</text>
+              <text className="n-s" x="592" y="202">A native Stellar asset</text>
+              <text className="n-s" x="592" y="217">compatible with</text>
+              <text className="n-s" x="592" y="232">existing toolkits</text>
+              <line className="edge" x1="764" y1="171" x2="812" y2="171" markerEnd="url(#usdt0-ar)" />
+              <line className="edge" x1="764" y1="201" x2="812" y2="201" markerEnd="url(#usdt0-ar)" />
+              <line className="edge" x1="764" y1="231" x2="812" y2="231" markerEnd="url(#usdt0-ar)" />
+              <rect className="n-box" x="816" y="157" width="164" height="28" />
+              <rect className="lit lUse" x="816" y="157" width="164" height="28" />
+              <text className="n-s" x="828" y="175">Payment rails</text>
+              <rect className="n-box" x="816" y="187" width="164" height="28" />
+              <rect className="lit lUse" x="816" y="187" width="164" height="28" />
+              <text className="n-s" x="828" y="205">Treasury balances</text>
+              <rect className="n-box" x="816" y="217" width="164" height="28" />
+              <rect className="lit lUse" x="816" y="217" width="164" height="28" />
+              <text className="n-s" x="828" y="235">Lending markets</text>
+              <circle className="pkt pTrunk" r="3.4" /><circle className="pkt pUp" r="3.4" />
+              <circle className="pkt pDown" r="3.4" /><circle className="pkt pClimb" r="3.4" />
+              <circle className="pkt pMint" r="3.4" /><circle className="pkt pUse1" r="3.4" />
+              <circle className="pkt pUse2" r="3.4" /><circle className="pkt pUse3" r="3.4" />
+            </svg>
+          </div>
+          <figcaption>Stellar’s OFT mints the USDT0, whether Ethereum locked the USDT or another chain
+            burned its own. Every chain runs its own OFT; Ethereum alone locks the USDT that backs them all
+            (<a href="https://docs.usdt0.to/technical-documentation/developer" target="_blank" rel="noopener noreferrer">USDT0 developer docs</a>).</figcaption>
+        </figure>
+        <figure id="access">
+          <div className="fig-head"><h2>Access — what USDT0 unlocks</h2></div>
+          <div className="folder-fig">
+            <div className="stackwrap">
+              <div className="stack" role="img" aria-label="A USDT0 folder, its cover in front, holding 4 files: payments, treasury, collateral, distribution." style={{ "--ar": 1.3425316828892888, "--fw": "75.00159374402347%", "--fh": "66.43326324004423%" }}>
+                {FOLDERS.map(([name, left, top], i) => (
+                  <div key={name} className="file" style={{ left, top, zIndex: i + 1 }}>
+                    {folder(false)}
+                    <span className="fname">{name}</span>
+                  </div>
+                ))}
+                <div className="file cover" style={{ left: 0, top: "33.56673675995577%", zIndex: 5 }}>
+                  {folder(true)}
+                  <span className="fname">USDT0</span>
+                  <span className="cover-body">
+                    <span className="cover-name">Access to a new economy</span>
+                    <span className="cover-sub">One asset · one supply</span>
+                  </span>
+                </div>
+              </div>
+            </div>
+            <div className="desc">
+              <span className="d-eyebrow">USDT0</span>
+              <h3 className="d-head">Access to a new economy</h3>
+              <p className="d-claim">The asset that brings access to new corridors, counterparties, and financial use cases on Stellar.</p>
+              <dl>
+                <div><dt>One asset, unified liquidity</dt><dd>USDT0 maintains a unified supply anchored to USDT on Ethereum, so liquidity isn’t fragmented across separate wrapped versions of the asset.</dd></div>
+                <div><dt>Built to move across networks</dt><dd>Operated by <a href="https://everdawn.to/" target="_blank" rel="noopener noreferrer">Everdawn Labs</a>, USDT0 connects Stellar to <a href="https://analytics.usdt0.to/" target="_blank" rel="noopener noreferrer">26+ networks</a> through LayerZero’s OFT standard.</dd></div>
+              </dl>
+            </div>
+          </div>
+          <div className="fig-files">
+            <div className="files" style={{ "--cols": 4 }}>
+              <div className="fcol">
+                <div className="ftag">Payments</div>
+                <h4 className="fhead">Build with an asset already in use</h4>
+                <p className="fcopy">Support cross-border payments, payouts, remittances, and other dollar-denominated flows with USDT0.</p>
+              </div>
+              <div className="fcol">
+                <div className="ftag">Treasury</div>
+                <h4 className="fhead">Power treasury and cash management products</h4>
+                <p className="fcopy">Give businesses and users a dollar-denominated asset for managing working capital.</p>
+              </div>
+              <div className="fcol">
+                <div className="ftag">Collateral</div>
+                <h4 className="fhead">Put USDT0 to work</h4>
+                <p className="fcopy">Give lending markets a dollar-denominated asset to use as collateral or borrow against.</p>
+              </div>
+              <div className="fcol">
+                <div className="ftag">Distribution</div>
+                <h4 className="fhead">One asset, many doors</h4>
+                <p className="fcopy">Every exchange, wallet, and fintech that lists it becomes an entry point to the Stellar network.</p>
+              </div>
+            </div>
+          </div>
+        </figure>
+        <section className="dayone" id="dayone" aria-labelledby="usdt0-d1-h">
+          <div className="dep-head">
+            <h2 id="usdt0-d1-h">Day one — what is already integrated</h2>
+          </div>
+          <div className="d1-body">
+            <p className="d1-lead">You can access USDT0 today across these partners on Stellar.<br />
+              More to come on a rolling basis.</p>
+            <div className="venues">
+              <div className="venue">
+                <h3>Exchanges, DEXs &amp; Lending Protocols</h3>
+                <ul><li>Kraken</li><li>SushiSwap</li><li>BiLira</li><li>Kinetic (K2)</li></ul>
+                <p>Buy, sell, swap, and borrow against USDT0 on Stellar.</p>
+              </div>
+              <div className="venue">
+                <h3>Wallets</h3>
+                <ul><li>Freighter</li><li>Lobstr</li><li>Meru</li><li>Bitget Wallet</li><li>Exodus</li></ul>
+                <p>Hold and send USDT0 on Stellar.</p>
+              </div>
+              <div className="venue">
+                <h3>Custody</h3>
+                <ul><li>Fireblocks</li></ul>
+                <p>Institutional custody and treasury operations for USDT0 on Stellar.</p>
+              </div>
+              <div className="venue">
+                <h3>Fintechs &amp; ramps</h3>
+                <ul><li>Ramp Network</li><li>Kredete</li></ul>
+                <p>Ramp services and fintech products using USDT0 in production, including cross-border payments across Africa.</p>
+              </div>
+            </div>
+            <a className="dep-link" href="https://usdt0.to/transfer" target="_blank" rel="noopener noreferrer">Transfer USDT0 to Stellar →</a>
+          </div>
+          <div className="dep-note">Balances move into and out of Stellar without a custodial bridge or a
+            wrapped representation. Transfer time is set by the chain you send from — a couple of minutes
+            from some networks, hours from others. The cost is that network's gas plus the LayerZero
+            message, <a href="https://docs.usdt0.to/technical-documentation/developer/" target="_blank" rel="noopener noreferrer">quoted per route</a>{" "}
+            before you send. USDT0 itself charges no protocol fee on most routes; where one applies it is
+            0.03%, set per route. Receiving USDT0 needs a trustline on the destination account —
+            see <a href="#build">requirements and limitations</a>.</div>
+        </section>
+        <section className="deploy" id="deploy" aria-labelledby="usdt0-dep-h">
+          <div className="dep-head">
+            <h2 id="usdt0-dep-h">Deploy — adding USDT0 to your environment</h2>
+            <span className="live">Live on Stellar Mainnet</span>
+          </div>
+          <div className="dep-body">
+            <p className="dep-lead">USDT0 is live on Stellar Mainnet. Add it to your wallet or environment. Test your
+              integration by <strong>moving a small amount end to end</strong> before rolling out to your users.</p>
+            <a className="dep-link" target="_blank" rel="noopener noreferrer" href="https://stellar.expert/explorer/public/asset/USDT0-GATISXX6BZ6NC7IKQBY37CJD4SOZL3CYZJWXEDG6JVIY4WBS6KXJHN6Q">View the asset on stellar.expert →</a>
+            <div className="ids">
+              {IDS.map(([label, note, value], i) => (
+                <div key={label} className="id-row">
+                  <div>
+                    <div className="id-label">{label}</div>
+                    <p className="id-note">{note}</p>
+                  </div>
+                  <div className="id-val">
+                    <code id={`usdt0-id-${i}`}>{value}</code>
+                    <button className="copy" type="button" aria-label={`Copy ${label}`} onClick={() => copy(i)}>{copyLabels[i] || "Copy"}</button>
+                  </div>
+                </div>
+              ))}
+            </div>
+            <a className="dep-link" target="_blank" rel="noopener noreferrer" href="https://docs.usdt0.to/technical-documentation/deployments?q=stellar">Contract deployments on docs.usdt0.to →</a>
+          </div>
+          <div className="dep-note"><b><a href="https://stellar.expert/explorer/public/asset/USDT0-GATISXX6BZ6NC7IKQBY37CJD4SOZL3CYZJWXEDG6JVIY4WBS6KXJHN6Q" target="_blank" rel="noopener noreferrer">This asset</a> sets <code>auth_revocable</code> and <code>auth_clawback_enabled</code></b> — the issuer can revoke a trustline or <a href="/docs/build/guides/transactions/clawbacks">clawback a balance</a>. <code>auth_required</code> is not set, so anyone can hold it. 💡 Soroswap maintains an <a href="https://github.com/soroswap/token-list/tree/main/assets" target="_blank" rel="noopener noreferrer">ecosystem token list</a> covering both classic assets and contract tokens (community-maintained rather than an official Stellar registry, and widely used).</div>
+        </section>
+        <section className="notes-sec" id="build" aria-labelledby="usdt0-bd-h">
+          <div className="dep-head"><h2 id="usdt0-bd-h">Before you build — requirements and limitations</h2></div>
+          <div className="notes-body">
+            <p className="dep-lead">What USDT0 on Stellar requires for integration.</p>
+            <div className="notes">
+              <div className="note">
+                <div className="ntag">Trustlines</div>
+                <p className="ncopy"><b>A trustline has to exist before the first payment lands.</b> Sending USDT0 to an account that has no USDT0 trustline fails with <a href="/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/payment"><code>op_no_trust</code></a>. A wallet may create it for you when you swap into USDT0 in-app; a transfer arriving from an exchange or another wallet has no such fallback. If you custody for users, create it during onboarding — <a href="/docs/build/guides/transactions/sponsored-reserves">sponsored reserves</a> can cover the reserve.</p>
+              </div>
+              <div className="note">
+                <div className="ntag">Decimals</div>
+                <p className="ncopy"><b>The OFT reconciles a precision gap for you.</b> USDT0 on Stellar carries <a href="/docs/learn/fundamentals/stellar-data-structures/assets">seven decimals</a>; cross-chain transfers normalize to the OFT’s <a href="https://docs.layerzero.network/v2/concepts/technical-reference/oft-reference" target="_blank" rel="noopener noreferrer">six shared decimals</a>. Send 1.2345678 and 1.234567 moves; the remaining 0.0000008 is floored off as dust and refunded to you before the debit. Nothing to convert by hand — but account for it when you calculate or display an amount.</p>
+              </div>
+              <div className="note">
+                <div className="ntag">Route limits</div>
+                <p className="ncopy"><b>A route can enforce a minimum.</b> Minimum transfer amounts are set per contract, so call <a href="https://docs.usdt0.to/technical-documentation/developer" target="_blank" rel="noopener noreferrer"><code>quote_oft</code></a> for the route you intend to use rather than assuming any amount will go through.</p>
+              </div>
+              <div className="note">
+                <div className="ntag">Backing</div>
+                <p className="ncopy"><b>The backing sits in one contract.</b> USDT0's adapter on Ethereum holds the USDT behind the natively issued supply.</p>
+              </div>
+              <div className="note">
+                <div className="ntag">Yield</div>
+                <p className="ncopy"><b>USDT0 doesn't accrue yield.</b> It earns nothing sitting in a balance — any return has to come from the market you supply it to.</p>
+              </div>
+              <div className="note">
+                <div className="ntag">Listings</div>
+                <p className="ncopy"><b>Each venue decides which networks it supports.</b> One USDT0 doesn't mean every listing offers every route, so check what a partner actually enables before you send users to it.</p>
+              </div>
+            </div>
+          </div>
+        </section>
+        <section className="notes-sec" id="faq" aria-labelledby="usdt0-fq-h">
+          <div className="dep-head"><h2 id="usdt0-fq-h">FAQ</h2></div>
+          <div className="notes-body">
+            <div className="faqs">
+              <details className="faq">
+                <summary><span className="fq">Is USDT0 the same as USDT?</span></summary>
+                <div className="fa"><p className="ncopy">No — it is a separate asset with its own contract, worth the same and backed 1:1 by USDT locked
+                  on Ethereum. The practical difference is deposits: a venue that supports USDT will not necessarily accept
+                  USDT0 on Stellar. Check your destination lists USDT0 on Stellar specifically before you send.</p></div>
+              </details>
+              <details className="faq">
+                <summary><span className="fq">Which USDT0 on Stellar is the real one?</span></summary>
+                <div className="fa"><p className="ncopy">The one issued by <code>GATISXX6BZ6NC7IKQBY37CJD4SOZL3CYZJWXEDG6JVIY4WBS6KXJHN6Q</code> —{" "}
+                  <a href="https://stellar.expert/explorer/public/asset/USDT0-GATISXX6BZ6NC7IKQBY37CJD4SOZL3CYZJWXEDG6JVIY4WBS6KXJHN6Q" target="_blank" rel="noopener noreferrer">check it on Stellar Expert</a>.
+                  Asset codes on Stellar are not unique — anyone can issue an asset called USDT0 — so identity is
+                  the code <b>and</b> the issuer together. Pin that issuer, and confirm the contract you derive from it
+                  matches <code>CBSJZEIO5C7KC2SF3MKSNXXJSW5G3VTNBX4ATMKUI3B2MR4JKM4R26YF</code>.</p></div>
+              </details>
+              <details className="faq">
+                <summary><span className="fq">Why did my USDT0 payment fail with <code>op_no_trust</code>?</span></summary>
+                <div className="fa"><p className="ncopy">The destination account has no USDT0 trustline, and one must exist before the first payment can land.
+                  A wallet often creates it when a user swaps into USDT0 in-app, but a transfer arriving from an exchange or
+                  another wallet has no such fallback. If you custody for users, create it during onboarding —{" "}
+                  <a href="/docs/build/guides/transactions/sponsored-reserves">sponsored reserves</a>
+                  {" "}can cover the reserve.</p></div>
+              </details>
+              <details className="faq">
+                <summary><span className="fq">How long does a transfer to Stellar take?</span></summary>
+                <div className="fa"><p className="ncopy">It depends on the chain you send from, not on Stellar. Stellar finalises in 5–7 seconds; the wait
+                  is the source chain confirming and LayerZero verifying the message. From Polygon it is about a minute.
+                  From Ethereum, Arbitrum, Tron and Solana — the routes carrying most volume — expect roughly
+                  18–21 minutes. A few low-traffic routes take hours. The{" "}
+                  <a href="https://usdt0.to/transfer" target="_blank" rel="noopener noreferrer">transfer UI</a>
+                  {" "}quotes an estimate for your route before you send.</p></div>
+              </details>
+              <details className="faq">
+                <summary><span className="fq">Why is my transfer slower than I expected?</span></summary>
+                <div className="fa"><p className="ncopy">Usually because the figure you saw was a network-wide best case rather than your route. Nothing on the
+                  Stellar side is the bottleneck. If a transfer runs well past the estimate you were quoted, look up the message on{" "}
+                  <a href="https://layerzeroscan.com/analytics/networks" target="_blank" rel="noopener noreferrer">LayerZero Scan</a>,
+                  which indexes Stellar as a destination, to see which step it is sitting at. USDT0 lists{" "}
+                  <a href="https://docs.usdt0.to/resources/contact" target="_blank" rel="noopener noreferrer">support contacts</a>
+                  {" "}for transfers that stall.</p></div>
+              </details>
+              <details className="faq">
+                <summary><span className="fq">What does it cost to bring USDT0 to Stellar?</span></summary>
+                <div className="fa"><p className="ncopy">Three separate things, and two different calls report them. USDT0's own protocol fee is zero on most
+                  routes and 0.03% where one applies:{" "}
+                  <a href="https://docs.usdt0.to/technical-documentation/developer/" target="_blank" rel="noopener noreferrer"><code>quote_oft</code></a>
+                  {" "}shows it as the gap between <code>amount_sent_ld</code> and <code>amount_received_ld</code>, so read it
+                  there rather than trusting a published number. The LayerZero messaging fee is separate and comes back from{" "}
+                  <a href="https://docs.usdt0.to/technical-documentation/developer/" target="_blank" rel="noopener noreferrer"><code>quote_send</code></a>,
+                  paid in XLM when you send from Stellar — this is the part that varies most. And on Stellar, ordinary transactions cost a{" "}
+                  <a href="/docs/learn/fundamentals/fees-resource-limits-metering">minimum of 100 stroops</a>
+                  {" "}per operation, which is unrelated to bridging.</p></div>
+              </details>
+              <details className="faq">
+                <summary><span className="fq">What is the difference between the Open Mesh and the Legacy Mesh?</span></summary>
+                <div className="fa"><p className="ncopy">On the Open Mesh each chain runs its own OFT contract, and moving between them burns on one side and
+                  mints on the other. The{" "}
+                  <a href="https://docs.usdt0.to/overview/the-legacy-mesh" target="_blank" rel="noopener noreferrer">Legacy Mesh</a>
+                  {" "}connects chains where Tether had already deployed native USDT — Ethereum, Tron, TON, Arbitrum, Solana
+                  and Celo — through a shared non-custodial hub on Arbitrum, so those chains keep their existing USDT
+                  contracts rather than migrating.</p></div>
+              </details>
+              <details className="faq">
+                <summary><span className="fq">Why did I receive slightly less than I sent?</span></summary>
+                <div className="fa"><p className="ncopy">Rounding, in the last decimal places only. USDT0 on Stellar carries seven decimals; cross-chain
+                  transfers normalise to the OFT's six shared decimals. Send 1.2345678 and 1.234567 moves — the
+                  remaining 0.0000008 is floored off as dust and refunded to you before the debit.</p></div>
+              </details>
+              <details className="faq">
+                <summary><span className="fq">Who can freeze or clawback USDT0 on Stellar?</span></summary>
+                <div className="fa"><p className="ncopy">The issuer. The asset sets <code>auth_revocable</code> and <code>auth_clawback_enabled</code>, so the
+                  issuer can revoke a trustline or{" "}
+                  <a href="/docs/build/guides/transactions/clawbacks">clawback a balance</a>.
+                  {" "}<code>auth_required</code> is not set, so anyone can hold it without approval.</p></div>
+              </details>
+            </div>
+          </div>
+        </section>
+        <dl className="spec">
+          <div><dt>Asset</dt><dd>USDT0</dd></div>
+          <div><dt>Transfer</dt><dd><a href="https://usdt0.to/transfer" target="_blank" rel="noopener noreferrer">usdt0.to</a></dd></div>
+          <div><dt>Networks</dt><dd><a href="https://analytics.usdt0.to/" target="_blank" rel="noopener noreferrer">26+</a></dd></div>
+          <div><dt>USDT in circulation</dt><dd><a href="https://coinmarketcap.com/currencies/tether/" target="_blank" rel="noopener noreferrer">$180B+</a></dd></div>
+          <div><dt>Stellar settlement</dt><dd><a href="/docs/learn/fundamentals/stellar-stack">5–7s</a></dd></div>
+          <div><dt>Stellar fee</dt><dd><a href="/docs/learn/fundamentals/fees-resource-limits-metering">100 stroops min</a></dd></div>
+          <div><dt>Transfer to Stellar</dt><dd><a href="https://usdt0.to/transfer" target="_blank" rel="noopener noreferrer">~20min typical</a></dd></div>
+        </dl>
+        <div className="sources">
+          <b>Sources</b>
+          <a href="https://docs.usdt0.to/technical-documentation/developer/" target="_blank" rel="noopener noreferrer">USDT0 Docs</a>
+          <a href="https://docs.usdt0.to/technical-documentation/deployments?q=stellar" target="_blank" rel="noopener noreferrer">USDT0 deployments</a>
+          <a href="/docs/tokens/usdt0-layerzero">Stellar Docs</a>
+          <a href="https://lab.stellar.org/smart-contracts/contract-list?$=network$id=mainnet&label=Mainnet&horizonUrl=https:////horizon.stellar.org&rpcUrl=https:////mainnet.sorobanrpc.com&passphrase=Public%20Global%20Stellar%20Network%20/;%20September%202015;&smartContracts$contractList$activeTab=known-assets;;" target="_blank" rel="noopener noreferrer">Stellar Lab</a>
+          <a href="https://docs.layerzero.network/v2/developers/stellar/overview" target="_blank" rel="noopener noreferrer">LayerZero on Stellar</a>
+        </div>
+        <div className="foot">
+          <span>Stellar Development Foundation</span>
+          <a className="xlink" href="https://x.com/BuildOnStellar" target="_blank" rel="noopener noreferrer" aria-label="Build on Stellar on X" title="Build on Stellar on X">
+            <svg viewBox="0 0 24 24" fill="currentColor" aria-hidden="true">
+              <path d="M18.244 2.25h3.308l-7.227 8.26 8.502 11.24H16.17l-5.214-6.817L4.99 21.75H1.68l7.73-8.835L1.254 2.25H8.08l4.713 6.231zm-1.161 17.52h1.833L7.084 4.126H5.117z" />
+            </svg>
+          </a>
+        </div>
+      </div>
+    </div>
+  );
+};
diff --git a/snippets/wallet/dart/configClient.mdx b/snippets/wallet/dart/configClient.mdx
new file mode 100644
index 000000000..6ac7fed7a
--- /dev/null
+++ b/snippets/wallet/dart/configClient.mdx
@@ -0,0 +1,19 @@
+The Flutter Wallet SDK uses the standard Client from the [http package](https://pub.dev/packages/http) for all network requests (excluding Horizon, where the Flutter Stellar SDK's HTTP client is used).
+
+Optionally, you can set your own client from [http package](https://pub.dev/packages/http) to be used across the app.
+
+The client can be globally configured:
+
+```dart
+import 'package:http/http.dart';
+// ...
+
+// init and configure your HTTP client
+// var myClient = ...
+
+// set as default HTTP client
+var appConfig = ApplicationConfiguration(defaultClient: myClient);
+var walletCustomClient = Wallet(StellarConfiguration.testNet, applicationConfiguration: appConfig);
+```
+
+Some [test cases](https://github.com/Soneso/stellar_wallet_flutter_sdk/tree/main/test) of this SDK use for example the `MockClient`.
diff --git a/docs/build/apps/wallet/component/dart/install.mdx b/snippets/wallet/dart/install.mdx
similarity index 100%
rename from docs/build/apps/wallet/component/dart/install.mdx
rename to snippets/wallet/dart/install.mdx
diff --git a/snippets/wallet/header.mdx b/snippets/wallet/header.mdx
new file mode 100644
index 000000000..ac8fe1709
--- /dev/null
+++ b/snippets/wallet/header.mdx
@@ -0,0 +1,22 @@
+import {
+  LanguageButtons,
+  WalletGuideWarn,
+} from "/snippets/wallet/language.jsx";
+
+<LanguageButtons />
+
+<Info>
+
+This guide is available on four different programming languages: Typescript, Kotlin, Flutter (Dart) and Swift. You can change the shown version on each page via the buttons above.
+
+</Info>
+
+<WalletGuideWarn WIPLangs={WIPLangs}>
+<Danger>
+
+**Important**
+
+Documentation for this language is currently work in progress. Some of information may not be applicable for this language, or missing. Code samples may be incomplete.
+
+</Danger>
+</WalletGuideWarn>
diff --git a/snippets/wallet/kt/configClient.mdx b/snippets/wallet/kt/configClient.mdx
new file mode 100644
index 000000000..27040d279
--- /dev/null
+++ b/snippets/wallet/kt/configClient.mdx
@@ -0,0 +1,40 @@
+The Kotlin wallet SDK uses the [ktor client](https://ktor.io/docs/getting-started-ktor-client.html) for all network requests (excluding Horizon, where the Stellar SDK's HTTP client is used). Currently, the okhttp engine is configured to be used with the client. You can read more about how to configure the ktor client [here](https://ktor.io/docs/create-client.html#configure-client).
+
+For example, the client can be globally configured:
+
+```kotlin
+val walletCustomClient =
+  Wallet(
+    StellarConfiguration.Testnet,
+    ApplicationConfiguration(
+      defaultClientConfig = {
+        engine { this.config { this.connectTimeout(Duration.ofSeconds(10)) } }
+        install(HttpRequestRetry) {
+          retryOnServerErrors(maxRetries = 5)
+          exponentialDelay()
+        }
+      }
+    )
+  )
+```
+
+This Kotlin code will set the connect timeout to ten seconds via the [okhttp configuration](https://ktor.io/docs/http-client-engines.html#okhttp) and also installs the [retry plugin](https://ktor.io/docs/client-retry.html). You can also specify client configuration for specific wallet SDK classes.
+
+For example, to change connect timeout when connecting to some anchor server:
+
+```kotlin
+val anchorCustomClient =
+  walletCustomClient.anchor("example.com") {
+    engine { this.config { this.connectTimeout(Duration.ofSeconds(30)) } }
+  }
+```
+
+### Closing Resources
+
+After the wallet class is no longer used, it's necessary to close all clients used by it. While in some applications it may not be required (e.g. the wallet lives for the whole lifetime of the application), in other cases it can be required. If your wallet class is short-lived, it's recommended to close client resources using a close function:
+
+```kotlin
+fun closeWallet() {
+  wallet.close()
+}
+```
diff --git a/docs/build/apps/wallet/component/kt/globalSigner.mdx b/snippets/wallet/kt/globalSigner.mdx
similarity index 100%
rename from docs/build/apps/wallet/component/kt/globalSigner.mdx
rename to snippets/wallet/kt/globalSigner.mdx
diff --git a/docs/build/apps/wallet/component/kt/httpConfig.mdx b/snippets/wallet/kt/httpConfig.mdx
similarity index 100%
rename from docs/build/apps/wallet/component/kt/httpConfig.mdx
rename to snippets/wallet/kt/httpConfig.mdx
diff --git a/docs/build/apps/wallet/component/kt/install.mdx b/snippets/wallet/kt/install.mdx
similarity index 100%
rename from docs/build/apps/wallet/component/kt/install.mdx
rename to snippets/wallet/kt/install.mdx
diff --git a/docs/build/apps/wallet/component/kt/watcher.mdx b/snippets/wallet/kt/watcher.mdx
similarity index 98%
rename from docs/build/apps/wallet/component/kt/watcher.mdx
rename to snippets/wallet/kt/watcher.mdx
index f5af354ee..46e01221b 100644
--- a/docs/build/apps/wallet/component/kt/watcher.mdx
+++ b/snippets/wallet/kt/watcher.mdx
@@ -18,8 +18,8 @@ This code example will consume all events coming from the channel until it's clo
 - `ExceptionHandlerExit`: indicates that the exception handler exited the processing loop. With default retry handler it happens when retries are exhausted.
 - `ChannelClosed`: indicates that the channel is closed and no more events will be emitted. This event will always fire. If `ExceptionHandlerExit` happened, channel will close right after. Otherwise, (under normal circumstances) it will stop when all transactions reach terminal statuses.
 
-:::info
+<Info>
 
 Events are stored in the channel until they are received, and calling the `receive()` method will block the channel until a message is received. You can read more about how channels work in the [channel documentation](https://kotlinlang.org/docs/coroutines-and-channels.html#channels).
 
-:::
+</Info>
diff --git a/snippets/wallet/language.jsx b/snippets/wallet/language.jsx
new file mode 100644
index 000000000..e8e19b214
--- /dev/null
+++ b/snippets/wallet/language.jsx
@@ -0,0 +1,65 @@
+// Port of the Docusaurus wallet guide components (LanguageButtons, LanguageSpecific, WalletGuideWarn).
+// The selected language is kept in the `selected_language` cookie, as in the original, and is also
+// written to Mintlify's `code` preference so code groups open on the matching language tab.
+// Mintlify only keeps exported components from snippet files, so each one is self-contained.
+
+export const LanguageButtons = () => {
+  const [mounted, setMounted] = useState(false);
+  useEffect(() => setMounted(true), []);
+  if (!mounted) return null;
+
+  const labels = { kt: "Kotlin", ts: "TypeScript", dart: "Flutter", swift: "Swift" };
+
+  const setCookie = (lang) => {
+    document.cookie = `selected_language=${lang}; SameSite=Strict; expires=Fri, 31 Dec 9999 23:59:59 GMT; Secure`;
+    try {
+      localStorage.setItem("code", JSON.stringify(labels[lang]));
+    } catch (e) {}
+    window.location.reload();
+  };
+
+  const button = (lang, light, dark, maxHeight) => (
+    <span
+      role="button"
+      tabIndex={0}
+      title={labels[lang]}
+      onClick={() => setCookie(lang)}
+      onKeyDown={(e) => (e.key === "Enter" || e.key === " ") && setCookie(lang)}
+      style={{ cursor: "pointer", display: "inline-flex" }}
+    >
+      <img src={light} alt={labels[lang]} className={dark ? "block dark:hidden" : "block"} style={{ maxHeight, margin: 0 }} />
+      {dark && <img src={dark} alt={labels[lang]} className="hidden dark:block" style={{ maxHeight, margin: 0 }} />}
+    </span>
+  );
+
+  return (
+    <div className="not-prose" style={{ gap: "1rem", display: "flex", alignItems: "center", marginBottom: "1rem" }}>
+      {button("ts", "/img/wallet/ts.png", null, "1.2rem")}
+      {button("kt", "/img/wallet/kt.png", "/img/wallet/kt-dark.png", "1.1rem")}
+      {button("dart", "/img/wallet/flutter.png", "/img/wallet/flutter-dark.png", "1.2rem")}
+      {button("swift", "/img/wallet/swift.png", "/img/wallet/swift-dark.png", "1.2rem")}
+    </div>
+  );
+};
+
+// Renders its children (the warning) only when the selected language is listed in WIPLangs.
+export const WalletGuideWarn = ({ WIPLangs, children }) => {
+  const [lang, setLang] = useState(null);
+
+  useEffect(() => {
+    const name = "selected_language=";
+    const cookie = decodeURIComponent(document.cookie)
+      .split(";")
+      .map((c) => c.trim())
+      .find((c) => c.startsWith(name));
+    setLang(cookie ? cookie.substring(name.length) : "ts");
+  }, []);
+
+  const aliases = { kotlin: "kt", typescript: "ts", flutter: "dart" };
+  const wip = (WIPLangs || []).map((v) => {
+    const l = String(v).toLowerCase();
+    return aliases[l] || l;
+  });
+
+  return lang && wip.includes(lang) ? <>{children}</> : null;
+};
diff --git a/docs/build/apps/wallet/component/swift/globalSigner.mdx b/snippets/wallet/swift/globalSigner.mdx
similarity index 100%
rename from docs/build/apps/wallet/component/swift/globalSigner.mdx
rename to snippets/wallet/swift/globalSigner.mdx
diff --git a/docs/build/apps/wallet/component/swift/install.mdx b/snippets/wallet/swift/install.mdx
similarity index 100%
rename from docs/build/apps/wallet/component/swift/install.mdx
rename to snippets/wallet/swift/install.mdx
diff --git a/docs/build/apps/wallet/component/ts/allowHttpInfo.mdx b/snippets/wallet/ts/allowHttpInfo.mdx
similarity index 94%
rename from docs/build/apps/wallet/component/ts/allowHttpInfo.mdx
rename to snippets/wallet/ts/allowHttpInfo.mdx
index 632ef0bf3..5311b4a77 100644
--- a/docs/build/apps/wallet/component/ts/allowHttpInfo.mdx
+++ b/snippets/wallet/ts/allowHttpInfo.mdx
@@ -1,4 +1,4 @@
-:::info
+<Info>
 
 If the anchor home domain uses http, then you need to set the `allowHttp` flag when creating the anchor:
 
@@ -8,4 +8,4 @@ let anchor = wallet.anchor({ homeDomain: "example.com", allowHttp: true });
 
 This can only be used on Testnet.
 
-:::
+</Info>
diff --git a/snippets/wallet/ts/configClient.mdx b/snippets/wallet/ts/configClient.mdx
new file mode 100644
index 000000000..f9eb3cfad
--- /dev/null
+++ b/snippets/wallet/ts/configClient.mdx
@@ -0,0 +1,16 @@
+The Typescript wallet SDK uses the [axios client](https://axios-http.com/docs/intro) for all network requests. You can read more about how to configure the axios client [here](https://axios-http.com/docs/instance).
+
+For example, we can configure our axios client to be globally configured with a timeout:
+
+```typescript
+const customClient: AxiosInstance = axios.create({
+  timeout: 1000,
+});
+let appConfig = new ApplicationConfiguration(DefaultSigner, customClient);
+let wal = new Wallet({
+  stellarConfiguration: StellarConfiguration.TestNet(),
+  applicationConfiguration: appConfig,
+});
+```
+
+You can find more [configure options here.](https://axios-http.com/docs/req_config)
diff --git a/docs/build/apps/wallet/component/ts/createKeypairInfo.mdx b/snippets/wallet/ts/createKeypairInfo.mdx
similarity index 94%
rename from docs/build/apps/wallet/component/ts/createKeypairInfo.mdx
rename to snippets/wallet/ts/createKeypairInfo.mdx
index cac83adda..cd3970965 100644
--- a/docs/build/apps/wallet/component/ts/createKeypairInfo.mdx
+++ b/snippets/wallet/ts/createKeypairInfo.mdx
@@ -1,4 +1,4 @@
-:::info
+<Info>
 
 If using react-native, `createKeypair` won't work. Instead use the helper method `createKeypairFromRandom` like this:
 
@@ -8,4 +8,4 @@ const rand = Random.randomBytes(32);
 const kp = account.createKeypairFromRandom(Buffer.from(rand));
 ```
 
-:::
+</Info>
diff --git a/docs/build/apps/wallet/component/ts/globalSigner.mdx b/snippets/wallet/ts/globalSigner.mdx
similarity index 100%
rename from docs/build/apps/wallet/component/ts/globalSigner.mdx
rename to snippets/wallet/ts/globalSigner.mdx
diff --git a/docs/build/apps/wallet/component/ts/install.mdx b/snippets/wallet/ts/install.mdx
similarity index 100%
rename from docs/build/apps/wallet/component/ts/install.mdx
rename to snippets/wallet/ts/install.mdx
diff --git a/src/clientModules/apiReferenceMarkdownButton.js b/src/clientModules/apiReferenceMarkdownButton.js
deleted file mode 100644
index 968a91a9a..000000000
--- a/src/clientModules/apiReferenceMarkdownButton.js
+++ /dev/null
@@ -1,74 +0,0 @@
-// Client module for the markdown-source feature (follow-up to PR #2289,
-// issue #2643): show the "Open Markdown" button on API reference pages.
-//
-// docusaurus-markdown-source-plugin injects its actions dropdown into
-// `article .markdown header`, which exists on regular doc pages but not on
-// the operation pages generated by docusaurus-plugin-openapi-docs (they
-// render an `h1.openapi__heading` and no `<header>`), so the button never
-// appears there. This module injects the SAME dropdown component next to
-// that heading, only on operation pages, and only when the plugin hasn't
-// already injected one — regular pages (including prose pages that live
-// under /api-reference/ routes) are left entirely to the plugin.
-
-import React from 'react';
-import { createRoot } from 'react-dom/client';
-import MarkdownActionsDropdown from 'docusaurus-markdown-source-plugin/components/MarkdownActionsDropdown';
-
-let activeObserver = null;
-let activeRoot = null;
-let activeContainer = null;
-
-function cleanup() {
-  if (activeObserver) {
-    activeObserver.disconnect();
-    activeObserver = null;
-  }
-  if (activeRoot) {
-    activeRoot.unmount();
-    activeRoot = null;
-  }
-  if (activeContainer) {
-    activeContainer.remove();
-    activeContainer = null;
-  }
-}
-
-function inject() {
-  // Operation pages only; anything else belongs to the plugin's own injection.
-  const heading = document.querySelector('h1.openapi__heading');
-  if (!heading) return false;
-
-  // Never double up — neither with the plugin's dropdown nor with our own.
-  if (document.querySelector('.markdown-actions-container')) return true;
-
-  const container = document.createElement('div');
-  container.className = 'markdown-actions-container';
-  heading.insertAdjacentElement('afterend', container);
-  activeContainer = container;
-
-  activeRoot = createRoot(container);
-  activeRoot.render(React.createElement(MarkdownActionsDropdown));
-  return true;
-}
-
-export function onRouteDidUpdate({ location }) {
-  cleanup();
-  if (!location.pathname.includes('/api-reference/')) return;
-
-  inject();
-
-  // The operation content hydrates client-side and Docusaurus swaps the DOM
-  // asynchronously on navigation, so keep watching (like the plugin does) and
-  // re-inject if the heading appears late or our container is swapped away.
-  activeObserver = new MutationObserver(() => {
-    if (!document.querySelector('.markdown-actions-container')) {
-      if (activeRoot) {
-        activeRoot.unmount();
-        activeRoot = null;
-      }
-      activeContainer = null;
-      inject();
-    }
-  });
-  activeObserver.observe(document.body, { childList: true, subtree: true });
-}
diff --git a/src/clientModules/webmcp.ts b/src/clientModules/webmcp.ts
deleted file mode 100644
index 556bb07cf..000000000
--- a/src/clientModules/webmcp.ts
+++ /dev/null
@@ -1,184 +0,0 @@
-// Registers a WebMCP `search_docs` tool so in-browser AI agents can search
-// these docs (https://webmachinelearning.github.io/webmcp/). WebMCP is
-// per-page browser tooling — client-side JS, not a network MCP server. The
-// API only exists behind an experimental flag (Chrome EPP / W3C draft), so in
-// every other browser this module must be a silent no-op.
-//
-// Loaded via the top-level `clientModules` option in docusaurus.config.ts.
-
-import siteConfig from '@generated/docusaurus.config';
-
-type AlgoliaCredentials = {
-  appId: string;
-  apiKey: string;
-  indexName: string;
-};
-
-// The same search-only Algolia credentials every DocSearch request already
-// ships to the browser — nothing here is secret.
-const algolia = siteConfig.themeConfig.algolia as
-  | AlgoliaCredentials
-  | undefined;
-
-type AlgoliaHit = {
-  hierarchy?: Record<string, string | null>;
-  url?: string;
-  content?: string | null;
-  _snippetResult?: { content?: { value?: string } };
-};
-
-type ToolContent = { content: Array<{ type: 'text'; text: string }> };
-
-type ModelContextTool = {
-  name: string;
-  description: string;
-  inputSchema: object;
-  annotations?: { readOnlyHint?: boolean };
-  execute: (input: { query?: unknown }) => Promise<ToolContent>;
-};
-
-// The draft spec has moved between navigator.modelContext and
-// document.modelContext, and between registerTool() and provideContext().
-// Chrome's EPP (and the scanners that grade agent-readiness) use
-// navigator.modelContext.registerTool; the current W3C draft says
-// document.modelContext. Probe every surface so the tool registers wherever
-// the running browser put the API.
-type ModelContext = {
-  registerTool?: (tool: ModelContextTool) => unknown;
-  provideContext?: (context: { tools: ModelContextTool[] }) => unknown;
-};
-
-function textResult(text: string): ToolContent {
-  return { content: [{ type: 'text', text }] };
-}
-
-// Strip markup to a fixpoint so overlapping fragments like `<scr<script>ipt>`
-// can't survive a single pass (CodeQL js/incomplete-multi-character-sanitization).
-function stripMarkup(value: string): string {
-  let text = value;
-  let previous;
-  do {
-    previous = text;
-    text = text.replace(/<[^>]*>/g, '');
-  } while (text !== previous);
-  return text;
-}
-
-async function searchDocs(
-  query: string,
-  credentials: AlgoliaCredentials,
-): Promise<string> {
-  // Same contextual facets DocSearch uses on this site: English records from
-  // the docs plugin plus untagged (default) pages, excluding blog-index noise.
-  const language = document.documentElement.lang?.split('-')[0] || 'en';
-  const params = new URLSearchParams({
-    query,
-    hitsPerPage: '8',
-    attributesToRetrieve: JSON.stringify(['hierarchy', 'url', 'content']),
-    attributesToSnippet: JSON.stringify(['content:40']),
-    snippetEllipsisText: '…',
-    highlightPreTag: '',
-    highlightPostTag: '',
-    facetFilters: JSON.stringify([
-      `language:${language}`,
-      ['docusaurus_tag:default', 'docusaurus_tag:docs-default-current'],
-    ]),
-  });
-
-  const response = await fetch(
-    `https://${credentials.appId}-dsn.algolia.net/1/indexes/${encodeURIComponent(credentials.indexName)}/query`,
-    {
-      method: 'POST',
-      headers: {
-        'Content-Type': 'application/json',
-        'X-Algolia-Application-Id': credentials.appId,
-        'X-Algolia-API-Key': credentials.apiKey,
-      },
-      body: JSON.stringify({ params: params.toString() }),
-    },
-  );
-  if (!response.ok) {
-    throw new Error(`Algolia search returned HTTP ${response.status}`);
-  }
-
-  const data = (await response.json()) as { nbHits?: number; hits?: AlgoliaHit[] };
-  const results = (data.hits ?? []).map((hit) => {
-    const hierarchy = hit.hierarchy ?? {};
-    const title =
-      [hierarchy.lvl0, hierarchy.lvl1, hierarchy.lvl2, hierarchy.lvl3]
-        .filter(Boolean)
-        .join(' › ') || hit.url || '';
-    // Snippets come back with highlight markup even with empty highlight
-    // tags on some index configs — strip any leftover tags for plain text.
-    const snippet = stripMarkup(
-      hit._snippetResult?.content?.value ?? hit.content ?? '',
-    );
-    return { title, url: hit.url ?? '', snippet };
-  });
-
-  return JSON.stringify({ query, totalHits: data.nbHits ?? results.length, results });
-}
-
-const searchDocsTool: ModelContextTool = {
-  name: 'search_docs',
-  description:
-    'Search the Stellar developer documentation (developers.stellar.org) and ' +
-    'return matching pages and sections as JSON — title, url, and a ' +
-    'plain-text snippet for each result.',
-  inputSchema: {
-    type: 'object',
-    properties: {
-      query: {
-        type: 'string',
-        description:
-          'Plain-text search query, e.g. "soroban contract deployment".',
-      },
-    },
-    required: ['query'],
-  },
-  annotations: { readOnlyHint: true },
-  async execute(input) {
-    try {
-      const query = typeof input?.query === 'string' ? input.query.trim() : '';
-      if (!query) {
-        return textResult('Error: `query` must be a non-empty string.');
-      }
-      if (!algolia) {
-        return textResult('Error: search is not configured on this page.');
-      }
-      return textResult(await searchDocs(query, algolia));
-    } catch (error) {
-      return textResult(`Error searching docs: ${String(error)}`);
-    }
-  },
-};
-
-if (typeof window !== 'undefined') {
-  const surfaces = [
-    (navigator as Navigator & { modelContext?: ModelContext }).modelContext,
-    (document as Document & { modelContext?: ModelContext }).modelContext,
-  ];
-  // Register once per distinct surface (they alias in a real implementation).
-  const seen = new Set<ModelContext>();
-  for (const modelContext of surfaces) {
-    if (!modelContext || seen.has(modelContext)) {
-      continue;
-    }
-    seen.add(modelContext);
-    try {
-      if (typeof modelContext.registerTool === 'function') {
-        void Promise.resolve(modelContext.registerTool(searchDocsTool)).catch(
-          () => {},
-        );
-      } else if (typeof modelContext.provideContext === 'function') {
-        void Promise.resolve(
-          modelContext.provideContext({ tools: [searchDocsTool] }),
-        ).catch(() => {});
-      }
-    } catch {
-      // Experimental API — registration must never break the page.
-    }
-  }
-}
-
-export {};
diff --git a/src/components/AgentSetup/index.tsx b/src/components/AgentSetup/index.tsx
deleted file mode 100644
index 2dd685b72..000000000
--- a/src/components/AgentSetup/index.tsx
+++ /dev/null
@@ -1,72 +0,0 @@
-import React, { type ReactNode } from 'react';
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-import CodeBlock from '@theme/CodeBlock';
-import Link from '@docusaurus/Link';
-
-import {
-  AGENT_TOOL_GROUP_ID,
-  AGENT_TOOLS,
-  DEFAULT_AGENT_TOOL_ID,
-  type ToolInstructions,
-} from '@site/src/data/agentTools';
-
-/**
- * The Building with AI page's rendering of the shared agent setup content in
- * `src/data/agentTools`. The "For agents" panel renders the same data, so the
- * page and the panel cannot fall out of sync.
- *
- * Both use the `mcp-client` tab group, which means a tool picked in the panel
- * is already selected when the reader lands here.
- */
-
-function Instructions({ instructions }: { instructions: ToolInstructions }): ReactNode {
-  return (
-    <>
-      {instructions.note && <p>{instructions.note}</p>}
-      {instructions.snippets.map((snippet) => (
-        <CodeBlock key={snippet.code} language={snippet.language}>
-          {snippet.code}
-        </CodeBlock>
-      ))}
-      {instructions.links && (
-        <p>
-          {instructions.links.map((link, index) => (
-            <React.Fragment key={link.href}>
-              {index > 0 && ' · '}
-              <Link to={link.href}>{link.label}</Link>
-            </React.Fragment>
-          ))}
-        </p>
-      )}
-    </>
-  );
-}
-
-function AgentToolTabs({
-  render,
-}: {
-  render: (tool: (typeof AGENT_TOOLS)[number]) => ReactNode;
-}): ReactNode {
-  return (
-    <Tabs groupId={AGENT_TOOL_GROUP_ID} defaultValue={DEFAULT_AGENT_TOOL_ID}>
-      {AGENT_TOOLS.map((tool) => (
-        <TabItem key={tool.id} value={tool.id} label={tool.label}>
-          {render(tool)}
-        </TabItem>
-      ))}
-    </Tabs>
-  );
-}
-
-/** Per-client instructions for connecting an agent to the Raven MCP server. */
-export function RavenConnectTabs(): ReactNode {
-  return <AgentToolTabs render={(tool) => <Instructions instructions={tool.raven} />} />;
-}
-
-/** Per-client instructions for installing the Stellar Skills. */
-export function SkillsInstallTabs(): ReactNode {
-  return (
-    <AgentToolTabs render={(tool) => <Instructions instructions={tool.skills.install} />} />
-  );
-}
diff --git a/src/components/AttributeTable/ListItem/index.tsx b/src/components/AttributeTable/ListItem/index.tsx
deleted file mode 100644
index 67eb06bfd..000000000
--- a/src/components/AttributeTable/ListItem/index.tsx
+++ /dev/null
@@ -1,57 +0,0 @@
-import React, { type ReactNode } from "react";
-import Details from "@theme/Details";
-
-import { combineAdjacentStrings, partition } from "@site/src/helpers";
-
-import styles from "./styles.module.scss";
-import Translate from "@docusaurus/Translate";
-
-export function ListItem(props): ReactNode {
-  const children = props.children.props.children.filter((child) => child !== "\n");
-
-  const [name, sublist] = children;
-
-  const [typeElement, descriptionElement] = sublist.props.children.filter((child) => child !== "\n");
-
-  const type =
-  typeElement.props.children === "skip" ? null : typeElement.props.children;
-
-  const [description, collapsedChildren] = partition(
-    React.Children.toArray(descriptionElement.props.children),
-    (child) => child?.type?.name !== "MDXUl" && child?.type?.name !== "ul",
-  );
-
-  const collapsedList = [];
-  collapsedChildren.length > 0 && collapsedChildren[0].props.children
-    .filter((child) => child !== "\n")
-    .map((child, index) => {
-      collapsedList.push(
-        <ListItem key={`collapsedItem-${index}`}>{child}</ListItem>,
-      );
-    });
-
-  return (
-    <li className={styles.ListItem}>
-      <p>
-        <span className={styles.ListItem__name}>{name}</span>
-        <span className={styles.ListItem__type}>{type}</span>
-      </p>
-
-      <p>{description}</p>
-
-      {collapsedList.length > 0 && (
-        <Details summary={
-          <summary>
-            <Translate
-              id="components.AttributeTable.ListItem.ShowChildAttributes"
-              description="For hand-written API schema pages, a message to tell readers they can expand a section to see more sub-items">
-              Show child attributes
-            </Translate>
-          </summary>
-        }>
-          {collapsedList}
-        </Details>
-      )}
-    </li>
-  );
-};
diff --git a/src/components/AttributeTable/ListItem/styles.module.scss b/src/components/AttributeTable/ListItem/styles.module.scss
deleted file mode 100644
index 5615ef3ab..000000000
--- a/src/components/AttributeTable/ListItem/styles.module.scss
+++ /dev/null
@@ -1,31 +0,0 @@
-.ListItem {
-  list-style: none;
-
-  margin: 0 !important;
-  padding: calc(2 * var(--ifm-spacing-vertical)) 0;
-  border-bottom: 1px solid var(--global-border-color);
-
-  &:last-child {
-    border: none;
-  }
-
-  &__name {
-    font-weight: var(--ifm-font-weight-bold);
-  }
-
-  &__type {
-    padding: 0 0.75rem;
-    color: var(--ifm-color-emphasis-600);
-  }
-
-  p {
-    margin: 0 !important;
-  }
-
-  details {
-    --docusaurus-details-decoration-color: var(--ifm-color-emphasis-600);
-    background-color: var(--ifm-background-surface-color);
-    border: 1px solid var(--global-border-color);
-    margin: var(--ifm-spacing-vertical) 0 0 0;
-  }
-}
diff --git a/src/components/AttributeTable/index.tsx b/src/components/AttributeTable/index.tsx
deleted file mode 100644
index b5d507086..000000000
--- a/src/components/AttributeTable/index.tsx
+++ /dev/null
@@ -1,21 +0,0 @@
-import React, { type ReactNode } from "react";
-import { ListItem } from "./ListItem";
-
-import styles from "./styles.module.scss";
-
-export function AttributeTable({ children }): ReactNode {
-  const renderArray = [];
-  children.props.children
-    .filter((child) => child !== "\n")
-    .map((child, index) => {
-      renderArray.push(
-        <ListItem key={`attributeItem-${index}`}>{child}</ListItem>,
-      );
-    });
-
-  return (
-    <div className={styles.AttributeTable}>
-      {renderArray}
-    </div>
-  );
-};
diff --git a/src/components/AttributeTable/styles.module.scss b/src/components/AttributeTable/styles.module.scss
deleted file mode 100644
index 8e642d678..000000000
--- a/src/components/AttributeTable/styles.module.scss
+++ /dev/null
@@ -1,5 +0,0 @@
-.AttributeTable {
-  ul {
-    padding: 0;
-  }
-}
diff --git a/src/components/AudioPlayer.tsx b/src/components/AudioPlayer.tsx
deleted file mode 100644
index 03d52bf8e..000000000
--- a/src/components/AudioPlayer.tsx
+++ /dev/null
@@ -1,39 +0,0 @@
-import React from "react";
-
-type AudioPlayerProps = {
-  src: string;
-};
-
-export default function AudioPlayer({ src }: AudioPlayerProps) {
-  return (
-    <div
-      style={{
-        maxWidth: 640,
-        margin: "20px auto",
-        padding: "12px 14px",
-        borderRadius: 14,
-        background: "var(--ifm-background-surface-color)",
-        border: "2px solid var(--ifm-color-emphasis-300)",
-      }}
-    >
-      <div
-        style={{
-          fontSize: "0.8rem",
-          fontWeight: 600,
-          color: "var(--ifm-color-primary)",
-          marginBottom: 6,
-          display: "flex",
-          alignItems: "center",
-          gap: 6,
-        }}
-      >
-        🎧 Audio Recording
-      </div>
-
-      <audio controls preload="metadata" style={{ width: "100%" }}>
-        <source src={src} type="audio/mpeg" />
-        Your browser does not support the audio element.
-      </audio>
-    </div>
-  );
-}
diff --git a/src/components/CodeExample.tsx b/src/components/CodeExample.tsx
deleted file mode 100644
index ced4b6540..000000000
--- a/src/components/CodeExample.tsx
+++ /dev/null
@@ -1,37 +0,0 @@
-import React, { type ReactNode } from 'react';
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-import CodeBlock from '@theme/CodeBlock';
-import { CODE_LANGS } from "@site/config/constants";
-import Translate from '@docusaurus/Translate';
-
-export function CodeExample({ children }): ReactNode {
-  return (
-    <Tabs groupId="programming-language">
-      {React.Children.map(children, (child, index) => {
-        const codeProps = child.props.children.props;
-        const { className = '' } = codeProps;
-
-        const [, language] = className.split('-');
-
-        return (
-          <TabItem
-            key={language || index}
-            value={language || index}
-            label={CODE_LANGS[language] ||
-              <Translate
-                id='components.CodeExample.NoLanguageTabTitle'
-                description='The tab title for a code example where no programming language was specified'>
-                Example
-              </Translate>
-            }
-          >
-            <CodeBlock language={language} showLineNumbers>
-              {codeProps.children}
-            </CodeBlock>
-          </TabItem>
-        );
-      })}
-    </Tabs>
-  );
-};
diff --git a/src/components/DriveVideo.tsx b/src/components/DriveVideo.tsx
deleted file mode 100644
index 4c36912dc..000000000
--- a/src/components/DriveVideo.tsx
+++ /dev/null
@@ -1,39 +0,0 @@
-import React from "react";
-
-type Props = {
-  ID: string;
-};
-
-export default function DriveVideo({ ID }: Props) {
-  const src = `https://drive.google.com/file/d/${ID}/preview`;
-
-  return (
-    <div
-      style={{
-        position: "relative",
-        width: "100%",
-        maxWidth: 960,
-        margin: "16px auto",
-        aspectRatio: "16 / 9",
-        borderRadius: 16,
-        overflow: "hidden",
-        boxShadow: "0 10px 30px rgba(0,0,0,.18)",
-        background: "rgba(0,0,0,.04)",
-      }}
-    >
-      <iframe
-        src={src}
-        loading="lazy"
-        title="Meeting Playback Video"
-        allow="autoplay; fullscreen"
-        style={{
-          position: "absolute",
-          inset: 0,
-          width: "100%",
-          height: "100%",
-          border: 0,
-        }}
-      />
-    </div>
-  );
-}
diff --git a/src/components/EndpointsTable.tsx b/src/components/EndpointsTable.tsx
deleted file mode 100644
index bec60fbd9..000000000
--- a/src/components/EndpointsTable.tsx
+++ /dev/null
@@ -1,17 +0,0 @@
-import React, { type ReactNode } from "react";
-import { MethodTable } from "./MethodTable";
-import Translate from "@docusaurus/Translate";
-
-const transledEndpoints = (
-  <Translate
-    id='components.EndpointsTable.Endpoints'
-    description="The default title for a table of API endpoints">
-    Endpoints
-  </Translate>
-)
-
-export function EndpointsTable({ children, title = transledEndpoints }): ReactNode {
-  return (
-    <MethodTable title={title}>{children}</MethodTable>
-  );
-};
diff --git a/src/components/ExampleResponse/index.tsx b/src/components/ExampleResponse/index.tsx
deleted file mode 100644
index 72a2b5e30..000000000
--- a/src/components/ExampleResponse/index.tsx
+++ /dev/null
@@ -1,22 +0,0 @@
-import React, { type ReactNode } from "react";
-import clsx from "clsx";
-
-import styles from "./styles.module.scss";
-import Translate from "@docusaurus/Translate";
-
-const translatedExample = (
-  <Translate
-    id='components.ExampleResponse.Example'
-    description="The default title for a table of example API responses">
-    Example
-  </Translate>
-)
-
-export function ExampleResponse({ children, title = translatedExample }): ReactNode {
-  const codeElement = children.props.children;
-
-  return React.cloneElement(codeElement, {
-    title,
-    className: clsx(styles.ExampleResponse, codeElement.props.className),
-  });
-};
diff --git a/src/components/ExampleResponse/styles.module.scss b/src/components/ExampleResponse/styles.module.scss
deleted file mode 100644
index 9ad3da13d..000000000
--- a/src/components/ExampleResponse/styles.module.scss
+++ /dev/null
@@ -1,5 +0,0 @@
-.ExampleResponse {
-  pre {
-    max-height: 30rem;
-  }
-}
diff --git a/src/components/ForAgentsPanel/CopyBlock.tsx b/src/components/ForAgentsPanel/CopyBlock.tsx
deleted file mode 100644
index bd736885d..000000000
--- a/src/components/ForAgentsPanel/CopyBlock.tsx
+++ /dev/null
@@ -1,93 +0,0 @@
-import React, { useEffect, useRef, useState, type ReactNode } from 'react';
-import { translate } from '@docusaurus/Translate';
-
-import styles from './styles.module.scss';
-
-interface Props {
-  code: string;
-}
-
-/**
- * A compact, copyable snippet. Deliberately not `@theme/CodeBlock`: inside a
- * 400px panel we want tight padding, wrapping instead of horizontal scroll,
- * and no syntax highlighting bundle.
- */
-export default function CopyBlock({ code }: Props): ReactNode {
-  const [copied, setCopied] = useState(false);
-  const timeout = useRef<ReturnType<typeof setTimeout>>(undefined);
-
-  useEffect(() => () => clearTimeout(timeout.current), []);
-
-  const copy = async () => {
-    try {
-      await navigator.clipboard.writeText(code);
-    } catch {
-      // Clipboard is unavailable (insecure origin, or permission denied).
-      return;
-    }
-    setCopied(true);
-    clearTimeout(timeout.current);
-    timeout.current = setTimeout(() => setCopied(false), 2000);
-  };
-
-  return (
-    <div className={styles.copyBlock}>
-      <pre className={styles.code}>{code}</pre>
-      <button
-        type="button"
-        className={styles.copyButton}
-        onClick={copy}
-        aria-label={
-          copied
-            ? translate({
-                message: 'Copied',
-                id: 'components.ForAgentsPanel.Copied',
-                description: 'Confirmation shown after copying a command',
-              })
-            : translate({
-                message: 'Copy command',
-                id: 'components.ForAgentsPanel.Copy',
-                description: 'Label for the button that copies a command',
-              })
-        }>
-        {copied ? <CheckIcon /> : <ClipboardIcon />}
-      </button>
-    </div>
-  );
-}
-
-function ClipboardIcon(): ReactNode {
-  return (
-    <svg width="14" height="14" viewBox="0 0 16 16" fill="none" aria-hidden="true">
-      <rect
-        x="5.5"
-        y="5.5"
-        width="8"
-        height="9"
-        rx="1.5"
-        stroke="currentColor"
-        strokeWidth="1.3"
-      />
-      <path
-        d="M10.5 3.5v-.5a1.5 1.5 0 0 0-1.5-1.5H4A1.5 1.5 0 0 0 2.5 3v6A1.5 1.5 0 0 0 4 10.5h.5"
-        stroke="currentColor"
-        strokeWidth="1.3"
-        strokeLinecap="round"
-      />
-    </svg>
-  );
-}
-
-function CheckIcon(): ReactNode {
-  return (
-    <svg width="14" height="14" viewBox="0 0 16 16" fill="none" aria-hidden="true">
-      <path
-        d="M3 8.5 6.2 11.7 13 4.9"
-        stroke="currentColor"
-        strokeWidth="1.6"
-        strokeLinecap="round"
-        strokeLinejoin="round"
-      />
-    </svg>
-  );
-}
diff --git a/src/components/ForAgentsPanel/index.tsx b/src/components/ForAgentsPanel/index.tsx
deleted file mode 100644
index 42dc36b09..000000000
--- a/src/components/ForAgentsPanel/index.tsx
+++ /dev/null
@@ -1,314 +0,0 @@
-import React, { useEffect, useRef, useState, type ReactNode } from 'react';
-import { useLocation } from '@docusaurus/router';
-import Link from '@docusaurus/Link';
-import useBaseUrl from '@docusaurus/useBaseUrl';
-import Translate, { translate } from '@docusaurus/Translate';
-import { useWindowSize } from '@docusaurus/theme-common';
-import clsx from 'clsx';
-
-import SparkleIcon from '@site/static/icons/sparkle.svg';
-import {
-  AGENT_SECTIONS,
-  AGENT_TOOLS,
-  getAgentTool,
-  type SkillsMode,
-  type ToolInstructions,
-} from '@site/src/data/agentTools';
-import useSelectedAgentTool from '@site/src/hooks/useSelectedAgentTool';
-
-import CopyBlock from './CopyBlock';
-import styles from './styles.module.scss';
-
-const FOCUSABLE_SELECTOR = 'a[href], button, [tabindex]';
-
-function focusableItems(container: HTMLElement | null): HTMLElement[] {
-  if (!container) {
-    return [];
-  }
-  return Array.from(container.querySelectorAll<HTMLElement>(FOCUSABLE_SELECTOR)).filter(
-    (element) => element.tabIndex >= 0 && element.offsetParent !== null,
-  );
-}
-
-/**
- * The "For agents" panel: a floating trigger in the bottom right of every page
- * that opens a docked panel of ways to point an AI agent at Stellar.
- *
- * The per-client commands come from `src/data/agentTools`, which the Building
- * with AI page renders too, so the commands cannot disagree between the two.
- */
-export default function ForAgentsPanel(): ReactNode {
-  const { pathname } = useLocation();
-  const llmsTxtUrl = useBaseUrl(AGENT_SECTIONS.llmsTxt.href);
-  const [open, setOpen] = useState(false);
-  const [toolId, selectTool] = useSelectedAgentTool();
-  const [skillsMode, setSkillsMode] = useState<SkillsMode>('install');
-
-  const triggerRef = useRef<HTMLButtonElement>(null);
-  const panelRef = useRef<HTMLDivElement>(null);
-  const restoreFocusOnClose = useRef(false);
-
-  const tool = getAgentTool(toolId);
-
-  // As a full-screen sheet the panel is genuinely modal, so it traps focus and
-  // says so. Docked beside the content on desktop it is not: the page behind it
-  // stays visible and usable, and focus is free to move out into it.
-  const isSheet = useWindowSize() === 'mobile';
-
-  // A docked panel would cover the content of the page the reader navigated to.
-  // Closing here must not restore focus: the reader followed a link, and the
-  // destination page's own focus handling should win.
-  useEffect(() => {
-    restoreFocusOnClose.current = false;
-    setOpen(false);
-  }, [pathname]);
-
-  // Move focus into the panel on open, and while modal, hold it there.
-  useEffect(() => {
-    if (!open) {
-      return undefined;
-    }
-    panelRef.current?.focus();
-
-    const onKeyDown = (event: KeyboardEvent) => {
-      if (event.key === 'Escape') {
-        event.stopPropagation();
-        setOpen(false);
-        return;
-      }
-      if (event.key !== 'Tab' || !isSheet) {
-        return;
-      }
-      const items = focusableItems(panelRef.current);
-      if (items.length === 0) {
-        return;
-      }
-      const first = items[0];
-      const last = items[items.length - 1];
-      const active = document.activeElement;
-      if (!event.shiftKey && active === last) {
-        event.preventDefault();
-        first.focus();
-      } else if (event.shiftKey && (active === first || active === panelRef.current)) {
-        event.preventDefault();
-        last.focus();
-      }
-    };
-
-    document.addEventListener('keydown', onKeyDown);
-    return () => document.removeEventListener('keydown', onKeyDown);
-  }, [open, isSheet]);
-
-  // Hand focus back to the trigger, but only when the reader closed the panel
-  // themselves. See the route-change effect above.
-  useEffect(() => {
-    if (!open && restoreFocusOnClose.current) {
-      restoreFocusOnClose.current = false;
-      triggerRef.current?.focus();
-    }
-  }, [open]);
-
-  const skills = tool.skills[skillsMode];
-
-  return (
-    <>
-      <button
-        type="button"
-        ref={triggerRef}
-        className={clsx(styles.trigger, open && styles.triggerHidden)}
-        aria-expanded={open}
-        aria-controls="for-agents-panel"
-        onClick={() => {
-          restoreFocusOnClose.current = true;
-          setOpen((value) => !value);
-        }}>
-        <SparkleIcon className={styles.triggerIcon} role="presentation" />
-        <Translate
-          id="components.ForAgentsPanel.TriggerLabel"
-          description="Label of the button that opens the AI agent setup panel">
-          For agents
-        </Translate>
-      </button>
-
-      <div
-        id="for-agents-panel"
-        ref={panelRef}
-        role="dialog"
-        aria-modal={isSheet}
-        aria-labelledby="for-agents-panel-title"
-        tabIndex={-1}
-        hidden={!open}
-        className={styles.panel}>
-        <div className={styles.panelHeader}>
-          <span className={styles.panelTitle} id="for-agents-panel-title">
-            <Translate
-              id="components.ForAgentsPanel.Title"
-              description="Accessible name of the AI agent setup panel">
-              Use Stellar with AI
-            </Translate>
-          </span>
-          <button
-            type="button"
-            className={styles.closeButton}
-            onClick={() => setOpen(false)}
-            aria-label={translate({
-              message: 'Close',
-              id: 'components.ForAgentsPanel.Close',
-              description: 'Label for the button that closes the AI agent setup panel',
-            })}>
-            <span aria-hidden="true">×</span>
-          </button>
-        </div>
-
-        <div className={styles.panelBody}>
-          <ToolPicker selected={tool.id} onSelect={selectTool} />
-
-          <section className={styles.section}>
-            <div className={styles.sectionHeader}>
-              <h3 className={styles.sectionTitle}>{AGENT_SECTIONS.raven.title}</h3>
-              <Link className={styles.sectionLink} to={AGENT_SECTIONS.raven.guide.href}>
-                {AGENT_SECTIONS.raven.guide.label} <Arrow />
-              </Link>
-            </div>
-            <p className={styles.sectionDescription}>{AGENT_SECTIONS.raven.description}</p>
-            <Instructions instructions={tool.raven} />
-            <div className={styles.sectionFooterLinks}>
-              {AGENT_SECTIONS.raven.links.map((link) => (
-                <Link key={link.href} className={styles.sectionLink} to={link.href}>
-                  {link.label} <Arrow />
-                </Link>
-              ))}
-            </div>
-          </section>
-
-          <section className={styles.section}>
-            <div className={styles.sectionHeader}>
-              <h3 className={styles.sectionTitle}>{AGENT_SECTIONS.skills.title}</h3>
-              <Link className={styles.sectionLink} to={AGENT_SECTIONS.skills.home.href}>
-                {AGENT_SECTIONS.skills.home.label} <Arrow />
-              </Link>
-            </div>
-            <p className={styles.sectionDescription}>{AGENT_SECTIONS.skills.description}</p>
-            <div className={styles.modeToggle} role="group">
-              {AGENT_SECTIONS.skills.modes.map((mode) => (
-                <button
-                  key={mode.id}
-                  type="button"
-                  className={clsx(styles.pill, skillsMode === mode.id && styles.pillActive)}
-                  aria-pressed={skillsMode === mode.id}
-                  onClick={() => setSkillsMode(mode.id as SkillsMode)}>
-                  {mode.label}
-                </button>
-              ))}
-            </div>
-            <Instructions instructions={skills} />
-          </section>
-
-          <section className={styles.section}>
-            {/* A static file rather than a route, so a plain anchor, not `Link`. */}
-            <a className={styles.sectionLink} href={llmsTxtUrl}>
-              {AGENT_SECTIONS.llmsTxt.title} <Arrow />
-            </a>
-            <p className={styles.sectionDescription}>{AGENT_SECTIONS.llmsTxt.description}</p>
-          </section>
-        </div>
-      </div>
-    </>
-  );
-}
-
-function ToolPicker({
-  selected,
-  onSelect,
-}: {
-  selected: string;
-  onSelect: (id: string) => void;
-}): ReactNode {
-  const groupRef = useRef<HTMLDivElement>(null);
-
-  const onKeyDown = (event: React.KeyboardEvent<HTMLDivElement>) => {
-    const step =
-      event.key === 'ArrowRight' || event.key === 'ArrowDown'
-        ? 1
-        : event.key === 'ArrowLeft' || event.key === 'ArrowUp'
-          ? -1
-          : 0;
-    if (step === 0 && event.key !== 'Home' && event.key !== 'End') {
-      return;
-    }
-    event.preventDefault();
-
-    const current = AGENT_TOOLS.findIndex((tool) => tool.id === selected);
-    let next: number;
-    if (event.key === 'Home') {
-      next = 0;
-    } else if (event.key === 'End') {
-      next = AGENT_TOOLS.length - 1;
-    } else {
-      next = (current + step + AGENT_TOOLS.length) % AGENT_TOOLS.length;
-    }
-
-    onSelect(AGENT_TOOLS[next].id);
-    groupRef.current
-      ?.querySelectorAll<HTMLButtonElement>('button')
-      ?.[next]?.focus();
-  };
-
-  return (
-    <div className={styles.toolPicker}>
-      <span className={styles.toolPickerLabel} id="for-agents-tool-label">
-        <Translate
-          id="components.ForAgentsPanel.YourTool"
-          description="Label above the AI tool picker">
-          Your tool
-        </Translate>
-      </span>
-      <div
-        ref={groupRef}
-        className={styles.pillRow}
-        role="radiogroup"
-        aria-labelledby="for-agents-tool-label"
-        onKeyDown={onKeyDown}>
-        {AGENT_TOOLS.map((tool) => {
-          const isSelected = tool.id === selected;
-          return (
-            <button
-              key={tool.id}
-              type="button"
-              role="radio"
-              aria-checked={isSelected}
-              tabIndex={isSelected ? 0 : -1}
-              className={clsx(styles.pill, isSelected && styles.pillActive)}
-              onClick={() => onSelect(tool.id)}>
-              {tool.label}
-            </button>
-          );
-        })}
-      </div>
-    </div>
-  );
-}
-
-function Instructions({ instructions }: { instructions: ToolInstructions }): ReactNode {
-  return (
-    <>
-      {instructions.note && <p className={styles.note}>{instructions.note}</p>}
-      {instructions.snippets.map((snippet) => (
-        <CopyBlock key={snippet.code} code={snippet.code} />
-      ))}
-      {instructions.links && (
-        <div className={styles.sectionFooterLinks}>
-          {instructions.links.map((link) => (
-            <Link key={link.href} className={styles.sectionLink} to={link.href}>
-              {link.label} <Arrow />
-            </Link>
-          ))}
-        </div>
-      )}
-    </>
-  );
-}
-
-function Arrow(): ReactNode {
-  return <span aria-hidden="true">→</span>;
-}
diff --git a/src/components/ForAgentsPanel/styles.module.scss b/src/components/ForAgentsPanel/styles.module.scss
deleted file mode 100644
index 9d45829ac..000000000
--- a/src/components/ForAgentsPanel/styles.module.scss
+++ /dev/null
@@ -1,274 +0,0 @@
-/**
- * Colors come from Infima's `--ifm-*` variables only, so the panel follows the
- * site's light and dark themes without a second set of hardcoded values.
- */
-
-$panel-width: 400px;
-$edge-gap: 1.5rem;
-
-/* Below Docusaurus' mobile breakpoint the panel becomes a full-screen sheet. */
-$mobile-breakpoint: 996px;
-
-.trigger {
-  position: fixed;
-  right: $edge-gap;
-  bottom: $edge-gap;
-  z-index: calc(var(--ifm-z-index-fixed) - 10);
-
-  display: inline-flex;
-  align-items: center;
-  gap: 0.5rem;
-
-  padding: 0.625rem 1rem;
-  border: 1px solid var(--ifm-color-emphasis-200);
-  border-radius: var(--ifm-global-radius);
-
-  background-color: var(--ifm-background-color);
-  box-shadow: var(--ifm-global-shadow-lw);
-  /* Body text, not link color: this is a button, and it should not read as a link. */
-  color: var(--ifm-font-color-base);
-  font-family: var(--ifm-font-family-base);
-  font-size: 0.9375rem;
-  font-weight: 500;
-  cursor: pointer;
-
-  transition: box-shadow var(--ifm-transition-fast) var(--ifm-transition-timing-default);
-
-  &:hover,
-  &:focus-visible {
-    box-shadow: var(--ifm-global-shadow-md);
-  }
-}
-
-/* The open panel has its own close button, so the trigger steps out of the way. */
-.triggerHidden {
-  display: none;
-}
-
-.triggerIcon {
-  width: 1rem;
-  height: 1rem;
-  flex-shrink: 0;
-
-  /* Inherits the button's text color. */
-}
-
-.panel {
-  position: fixed;
-  top: var(--ifm-navbar-height);
-  right: 0;
-  bottom: 0;
-  z-index: calc(var(--ifm-z-index-fixed) - 10);
-
-  display: flex;
-  flex-direction: column;
-  width: $panel-width;
-
-  border-left: 1px solid var(--ifm-color-emphasis-200);
-  background-color: var(--ifm-background-color);
-  box-shadow: var(--ifm-global-shadow-md);
-
-  &[hidden] {
-    display: none;
-  }
-}
-
-.panelHeader {
-  display: flex;
-  align-items: flex-start;
-  justify-content: space-between;
-  gap: 0.5rem;
-  padding: 1rem 1rem 0;
-}
-
-.panelTitle {
-  color: var(--ifm-color-emphasis-600);
-  font-size: 0.8125rem;
-}
-
-.closeButton {
-  display: flex;
-  align-items: center;
-  justify-content: center;
-
-  width: 1.75rem;
-  height: 1.75rem;
-  padding: 0;
-  border: 1px solid var(--ifm-color-emphasis-200);
-  border-radius: var(--ifm-global-radius);
-
-  background-color: transparent;
-  color: var(--ifm-font-color-base);
-  font-size: 1rem;
-  line-height: 1;
-  cursor: pointer;
-
-  &:hover {
-    background-color: var(--ifm-color-emphasis-100);
-  }
-}
-
-.panelBody {
-  flex: 1;
-  overflow-y: auto;
-  padding: 0.5rem 1rem 1.5rem;
-}
-
-.toolPicker {
-  display: flex;
-  flex-direction: column;
-  gap: 0.5rem;
-  padding-bottom: 1rem;
-}
-
-.toolPickerLabel {
-  font-size: 0.9375rem;
-  font-weight: 500;
-}
-
-.pillRow,
-.modeToggle {
-  display: flex;
-  flex-wrap: wrap;
-  gap: 0.5rem;
-}
-
-.modeToggle {
-  padding-bottom: 0.5rem;
-}
-
-.pill {
-  padding: 0.375rem 0.875rem;
-  border: 1px solid var(--ifm-color-emphasis-300);
-  border-radius: 999px;
-
-  background-color: transparent;
-  color: var(--ifm-font-color-base);
-  font-family: var(--ifm-font-family-base);
-  font-size: 0.875rem;
-  font-weight: 500;
-  cursor: pointer;
-
-  transition: background-color var(--ifm-transition-fast) var(--ifm-transition-timing-default);
-
-  &:hover {
-    background-color: var(--ifm-color-emphasis-100);
-  }
-}
-
-/* Selected state: inverted, so it reads the same in light and dark mode. */
-.pillActive,
-.pillActive:hover {
-  border-color: var(--ifm-font-color-base);
-  background-color: var(--ifm-font-color-base);
-  color: var(--ifm-background-color);
-}
-
-.section {
-  padding: 1rem 0;
-  border-top: 1px solid var(--ifm-color-emphasis-200);
-}
-
-.sectionHeader {
-  display: flex;
-  align-items: baseline;
-  justify-content: space-between;
-  gap: 0.5rem;
-}
-
-.sectionTitle {
-  margin: 0;
-  font-size: 0.9375rem;
-  font-weight: 500;
-}
-
-.sectionLink {
-  font-size: 0.875rem;
-  white-space: nowrap;
-}
-
-.sectionDescription {
-  margin: 0.25rem 0 0.75rem;
-  font-size: 0.875rem;
-}
-
-.note {
-  margin: 0 0 0.5rem;
-  color: var(--ifm-color-emphasis-600);
-  font-size: 0.8125rem;
-}
-
-.sectionFooterLinks {
-  display: flex;
-  flex-wrap: wrap;
-  gap: 1rem;
-  padding-top: 0.75rem;
-}
-
-.copyBlock {
-  display: flex;
-  align-items: flex-start;
-  gap: 0.5rem;
-
-  margin-bottom: 0.5rem;
-  padding: 0.625rem 0.5rem 0.625rem 0.75rem;
-  border-radius: var(--ifm-global-radius);
-
-  background-color: var(--ifm-code-background);
-
-  &:last-child {
-    margin-bottom: 0;
-  }
-}
-
-.code {
-  flex: 1;
-  margin: 0;
-  padding: 0;
-
-  background: transparent;
-  font-family: var(--ifm-font-family-monospace);
-  font-size: 0.75rem;
-  line-height: 1.5;
-
-  /* Wrap rather than scroll: the panel is too narrow for a scrollbar per block. */
-  white-space: pre-wrap;
-  overflow-wrap: anywhere;
-}
-
-.copyButton {
-  display: flex;
-  align-items: center;
-  justify-content: center;
-  flex-shrink: 0;
-
-  width: 1.5rem;
-  height: 1.5rem;
-  padding: 0;
-  border: 1px solid var(--ifm-color-emphasis-200);
-  border-radius: var(--ifm-global-radius);
-
-  background-color: var(--ifm-background-color);
-  color: var(--ifm-font-color-base);
-  cursor: pointer;
-
-  &:hover {
-    background-color: var(--ifm-color-emphasis-100);
-  }
-}
-
-@media (max-width: $mobile-breakpoint) {
-  .trigger {
-    right: 1rem;
-    bottom: 1rem;
-  }
-
-  /* Sit above the navbar so the sheet is not split by it. */
-  .panel {
-    top: 0;
-    z-index: calc(var(--ifm-z-index-fixed) + 10);
-
-    width: 100%;
-    border-left: none;
-  }
-}
diff --git a/src/components/Homepage/DeveloperResources/index.tsx b/src/components/Homepage/DeveloperResources/index.tsx
deleted file mode 100644
index 04e20bc30..000000000
--- a/src/components/Homepage/DeveloperResources/index.tsx
+++ /dev/null
@@ -1,148 +0,0 @@
-import React, { type ReactNode } from 'react'
-import Heading from '@theme/Heading';
-import Link from '@docusaurus/Link';
-import clsx from 'clsx';
-import { exploreLink, partitionBoxes, type NavigatingDocsItem as DeveloperResourcesItem } from '@site/src/components/Homepage/NavigatingTheDocs'
-import Translate, { translate } from '@docusaurus/Translate'
-import styles from './styles.module.css'
-
-const DeveloperResourcesBoxes: DeveloperResourcesItem[] = [
-  {
-    title: translate({
-      message: 'Stellar Developer Discord',
-      id: 'component.Homepage.DeveloperResources.Discord.Title',
-    }),
-    description: (
-      <Translate
-        id='component.Homepage.DeveloperResources.Discord.Description'
-        description='Long description of what kind of developer resource this is.'>
-        Ask questions and engage with other Stellar devs.
-      </Translate>
-    ),
-    link: exploreLink('https://discord.gg/stellardev'),
-  },
-  {
-    title: translate({
-      message: 'Developer Site',
-      id: 'component.Homepage.DeveloperResources.DeveloperSite.Title',
-    }),
-    description: (
-      <Translate
-        id='component.Homepage.DeveloperResources.DeveloperSite.Description'
-        description='Long description of what kind of developer resource this is.'>
-        Get the latest news and insights about building on Stellar.
-      </Translate>
-    ),
-    link: exploreLink('https://stellar.org/developers'),
-  },
-  {
-    title: translate({
-      message: 'Stellar Stack Exchange',
-      id: 'component.Homepage.DeveloperResources.StackExchange.Title',
-    }),
-    description: (
-      <Translate
-        id='component.Homepage.DeveloperResources.StackExchange.Description'
-        description='Long description of what kind of developer resource this is.'>
-        A question and answer site for Stellar developers; if you can’t find what you’re looking for in the docs, try searching the Stack Exchange to see if your question has been addressed. If it hasn't, feel free to ask!
-      </Translate>
-    ),
-    link: exploreLink('https://stellar.stackexchange.com/'),
-  },
-  {
-    title: translate({
-      message: 'Stellar Developers Google Group',
-      id: 'component.Homepage.DeveloperResources.GoogleGroup.Title',
-    }),
-    description: (
-      <Translate
-        id='component.Homepage.DeveloperResources.GoogleGroup.Description'
-        description='Long description of what kind of developer resource this is.'>
-        Discuss Core Advancement Proposals (CAPs) and Stellar Ecosystem Proposals (SEPs), talk about the development of Stellar Core and Horizon, and stay informed about important network upgrades.
-      </Translate>
-    ),
-    link: exploreLink('https://groups.google.com/g/stellar-dev'),
-  },
-]
-
-function DeveloperResourcesFeature({title, description, link}) {
-  return (
-    <div className='col col--6 padding--md'>
-      <div className={clsx(styles.DeveloperResourcesFeature, 'padding--lg')}>
-        <Heading as="h3" className='text--semibold'>{title}</Heading>
-        <p>{description}</p>
-        <Link className='button button--outline button--primary' {...link.props} />
-      </div>
-    </div>
-  )
-}
-
-function DocsContribution() {
-  return (
-    <>
-      <Heading as="h3" className='text--semibold'>
-        <Translate
-          id='component.Homepage.DocsContribution.Heading'>
-          Contribute to the docs and leave feedback
-        </Translate>
-      </Heading>
-      <p>
-        <Translate
-          id='component.Homepage.DocsContribution.Paragraph1'
-          values={{
-            githubRepoLink: (
-              <Link to="https://github.com/stellar/stellar-docs">
-                <Translate
-                  id='component.Homepage.DocsContribution.DocsGithubLink'
-                  description='Label for the link to the Stellar docs repository on Github'>
-                  Stellar Docs GitHub Repo
-                </Translate>
-              </Link>
-            )
-          }}>
-          {'Stellar’s Developer Documentation is open-source, and contributions to the docs are encouraged. You can file an issue or pull request to add new content, suggest revisions to existing content, submit suggestions, report bugs, and more in the {githubRepoLink}.'}
-        </Translate>
-      </p>
-      <p>
-        <Translate
-          id='component.Homepage.DocsContribution.Paragraph2'
-          values={{
-            githubOrgLink: (
-              <Link to="https://github.com/stellar">
-                <Translate
-                  id='component.Homepage.DocsContribution.StellarRepos'
-                  description='Label for the link to the Stellar organization profile on Github'>
-                  Stellar repos
-                </Translate>
-              </Link>
-            )
-          }}>
-          {'Also, feel free to leave any additional feedback by filing issues in the various other {githubOrgLink}.'}
-        </Translate>
-      </p>
-    </>
-  )
-}
-
-export default function DeveloperResources() {
-  const partitionedBoxes = partitionBoxes(DeveloperResourcesBoxes);
-
-  return (
-    <section className='margin-vert--lg'>
-      {partitionedBoxes.map((twoBoxes) => (
-        <div className='row'>
-          {twoBoxes.map((props, idx) => (
-            <DeveloperResourcesFeature key={idx} {...props} />
-          ))}
-        </div>
-      ))}
-      <div className='row'>
-        <div className='col padding--md'>
-          <div className={clsx(styles.DeveloperResourcesFeature, 'padding--lg')}>
-            <DocsContribution />
-          </div>
-        </div>
-      </div>
-    </section>
-  )
-}
diff --git a/src/components/Homepage/DeveloperResources/styles.module.css b/src/components/Homepage/DeveloperResources/styles.module.css
deleted file mode 100644
index 89cabcb2e..000000000
--- a/src/components/Homepage/DeveloperResources/styles.module.css
+++ /dev/null
@@ -1,5 +0,0 @@
-.DeveloperResourcesFeature {
-    border-radius: var(--ifm-global-radius);
-    background-color: var(--ifm-background-surface-color);
-    height: 100%;
-}
diff --git a/src/components/Homepage/NavigatingTheDocs/index.tsx b/src/components/Homepage/NavigatingTheDocs/index.tsx
deleted file mode 100644
index 6d33cdbeb..000000000
--- a/src/components/Homepage/NavigatingTheDocs/index.tsx
+++ /dev/null
@@ -1,160 +0,0 @@
-import React, { type ReactNode } from 'react';
-import Heading from '@theme/Heading';
-import Link from '@docusaurus/Link';
-import Translate, { translate } from '@docusaurus/Translate';
-import clsx from 'clsx';
-import styles from './styles.module.css'
-
-export type NavigatingDocsItem = {
-  title: string;
-  description: ReactNode;
-  link: ReactNode;
-}
-
-export const exploreLink = (target: string) => (
-  <Link to={target}>
-    <Translate
-      id='component.Homepage.ExploreButton.Text'
-      description='The text that will be displayed on the "Explore" buttons'>
-      Explore
-    </Translate>
-  </Link>
-)
-
-export const partitionBoxes = (boxesArray: NavigatingDocsItem[]): NavigatingDocsItem[][] => {
-  return boxesArray.reduce((acc, item, i, arr) => {
-    if (i % 2 === 0) {
-      acc.push(arr.slice(i, i + 2))
-    }
-    return acc
-  }, [])
-}
-
-const NavigatingDocsBoxes: NavigatingDocsItem[] = [
-  {
-    title: translate({
-      message: 'Build',
-      id: 'component.Homepage.NavigatingTheDocs.Build.Title',
-    }),
-    description: (
-      <Translate
-        id='component.Homepage.NavigatingTheDocs.Build.Description'
-        description='Long description of what kind of information this section of the docs.'>
-        Contains tutorials and how-to guides for writing smart contracts, building applications, interacting with the network, and more.
-      </Translate>
-    ),
-    link: exploreLink('/docs/build'),
-  },
-  {
-    title: translate({
-      message: 'Learn',
-      id: 'component.Homepage.NavigatingTheDocs.Learn.Title',
-    }),
-    description: (
-      <Translate
-        id='component.Homepage.NavigatingTheDocs.Learn.Description'
-        description='Long description of what kind of information this section of the docs.'>
-        Find all informational and conceptual content here. Learn about Stellar fundamentals like how accounts and transactions function, dive deeper into the functionality of each operation, discover how fees work, and more.
-      </Translate>
-    ),
-    link: exploreLink('/docs/learn/fundamentals'),
-  },
-  {
-    title: translate({
-      message: 'Tokens',
-      id: 'component.Homepage.NavigatingTheDocs.Tokens.Title',
-    }),
-    description: (
-      <Translate
-        id='component.Homepage.NavigatingTheDocs.Tokens.Description'
-        description='Long description of what kind of information this section of the docs.'>
-        Information on how to issue assets on the Stellar network and create custom smart contract tokens.
-      </Translate>
-    ),
-    link: exploreLink('/docs/tokens'),
-  },
-  {
-    title: translate({
-      message: 'Data',
-      id: 'component.Homepage.NavigatingTheDocs.Data.Title',
-    }),
-    description: (
-      <Translate
-        id='component.Homepage.NavigatingTheDocs.Data.Description'
-        description='Long description of what kind of information this section of the docs.'>
-        Discover various data availability options: RPC, Hubble, Horizon, Galexie, and data indexers.
-      </Translate>
-    ),
-    link: exploreLink('/docs/data'),
-  },
-  {
-    title: translate({
-      message: 'Tools',
-      id: 'component.Homepage.NavigatingTheDocs.Tools.Title',
-    }),
-    description: (
-      <Translate
-        id='component.Homepage.NavigatingTheDocs.Tools.Description'
-        description='Long description of what kind of information this section of the docs.'>
-        Learn about all the available tools for building on, interacting with, or just watching the Stellar network. Also, find information on how to use the Anchor Platform or Stellar Disbursement Platform.
-      </Translate>
-    ),
-    link: exploreLink('/docs/tools'),
-  },
-  {
-    title: translate({
-      message: 'Networks',
-      id: 'component.Homepage.NavigatingTheDocs.Networks.Title',
-    }),
-    description: (
-      <Translate
-        id='component.Homepage.NavigatingTheDocs.Networks.Description'
-        description='Long description of what kind of information this section of the docs.'>
-        Information about deployed networks (Mainnet, Testnet, and Futurenet), current software versions, resource limitations, and fees.
-      </Translate>
-    ),
-    link: exploreLink('/docs/networks'),
-  },
-  {
-    title: translate({
-      message: 'Validators',
-      id: 'component.Homepage.NavigatingTheDocs.Validators.Title',
-    }),
-    description: (
-      <Translate
-        id='component.Homepage.NavigatingTheDocs.Validators.Description'
-        description='Long description of what kind of information this section of the docs.'>
-        Everything you'll need to know if you want to run, operate, and maintain a core validator node on the Stellar network.
-      </Translate>
-    ),
-    link: exploreLink('/docs/validators'),
-  },
-]
-
-function NavigatingDocsFeature({title, description, link}) {
-  return (
-    <div className='col col--6 padding--md'>
-      <div className={clsx(styles.NavigatingDocsFeature, 'padding--lg')}>
-        <Heading as="h3" className='text--semibold'>{title}</Heading>
-        <p>{description}</p>
-        <Link className='button button--outline button--primary' {...link.props} />
-      </div>
-    </div>
-  )
-}
-
-export default function NavigatingTheDocs() {
-  const partitionedBoxes = partitionBoxes(NavigatingDocsBoxes)
-
-  return (
-    <section className='margin-vert--lg'>
-      {partitionedBoxes.map((twoBoxes) => (
-        <div className='row'>
-          {twoBoxes.map((props, idx) => (
-            <NavigatingDocsFeature key={idx} {...props} />
-          ))}
-        </div>
-      ))}
-    </section>
-  )
-}
diff --git a/src/components/Homepage/NavigatingTheDocs/styles.module.css b/src/components/Homepage/NavigatingTheDocs/styles.module.css
deleted file mode 100644
index e1ab9b9ef..000000000
--- a/src/components/Homepage/NavigatingTheDocs/styles.module.css
+++ /dev/null
@@ -1,5 +0,0 @@
-.NavigatingDocsFeature {
-    border-radius: var(--ifm-global-radius);
-    background-color: var(--ifm-background-surface-color);
-    height: 100%;
-}
diff --git a/src/components/Homepage/PathfindingTable/PathfindingRow/index.tsx b/src/components/Homepage/PathfindingTable/PathfindingRow/index.tsx
deleted file mode 100644
index 8e6fab2bb..000000000
--- a/src/components/Homepage/PathfindingTable/PathfindingRow/index.tsx
+++ /dev/null
@@ -1,31 +0,0 @@
-import React from "react";
-import styles from './styles.module.css'
-import clsx from "clsx";
-
-const BADGE_CATEGORIES: Record<string, string> = {
-  Learn: 'warning',
-  Guide: 'primary',
-  Tool: 'success',
-  Example: 'info',
-  Tutorial: 'danger',
-  Data: 'secondary',
-}
-
-export default function PathfindingRow({ row }) {
-  const [linkTd, descTd, badgeTd] = row.props.children
-
-  const description = descTd.props.children
-  const badgeCategory = badgeTd.props.children
-
-  return (
-    <tr>
-      <td className={styles.LinkColumn} {...linkTd.props}></td>
-      <td className={styles.DescColumn}>
-        <div className={clsx(styles.DescColumnInner)}>
-          <span>{description}</span>
-          <span className={clsx('badge', `badge--${BADGE_CATEGORIES[badgeCategory]}`)}>{badgeCategory}</span>
-        </div>
-      </td>
-    </tr>
-  )
-}
diff --git a/src/components/Homepage/PathfindingTable/PathfindingRow/styles.module.css b/src/components/Homepage/PathfindingTable/PathfindingRow/styles.module.css
deleted file mode 100644
index fba997cec..000000000
--- a/src/components/Homepage/PathfindingTable/PathfindingRow/styles.module.css
+++ /dev/null
@@ -1,19 +0,0 @@
-.LinkColumn {
-  width: 25%;
-}
-
-.DescColumn {
-  width: 75%
-}
-
-.DescColumnInner {
-  display: flex;
-  flex-direction: row;
-  justify-content: space-between;
-  align-items: center;
-
-  @media (max-width: 640px) {
-    flex-direction: column;
-    align-items: start;
-  }
-}
diff --git a/src/components/Homepage/PathfindingTable/index.tsx b/src/components/Homepage/PathfindingTable/index.tsx
deleted file mode 100644
index d60783a25..000000000
--- a/src/components/Homepage/PathfindingTable/index.tsx
+++ /dev/null
@@ -1,29 +0,0 @@
-import React from 'react';
-import PathfindingRow from './PathfindingRow';
-import styles from './styles.module.css'
-
-export default function PathfindingTable({ children }) {
-  return (
-    React.Children.map(children, child => {
-      if (child.type === 'table') {
-        const [thead, tbody] = child.props.children
-        const rows = tbody.props.children
-
-        return (
-          <table className={styles.PathfindingTable}>
-            <thead>
-              <tr>
-                <th colSpan={3} {...thead.props.children.props.children[0].props}></th>
-              </tr>
-            </thead>
-            <tbody>
-              {React.Children.map(rows, row => <PathfindingRow row={row} />)}
-            </tbody>
-          </table>
-        )
-      } else {
-        return child
-      }
-    })
-  )
-}
diff --git a/src/components/Homepage/PathfindingTable/styles.module.css b/src/components/Homepage/PathfindingTable/styles.module.css
deleted file mode 100644
index 4e581360c..000000000
--- a/src/components/Homepage/PathfindingTable/styles.module.css
+++ /dev/null
@@ -1,5 +0,0 @@
-.PathfindingTable {
-  border-radius: var(--ifm-global-radius);
-  display: table;
-  width: 100%;
-}
diff --git a/src/components/Homepage/WayfindingBoxes/index.tsx b/src/components/Homepage/WayfindingBoxes/index.tsx
deleted file mode 100644
index 19e51d8b6..000000000
--- a/src/components/Homepage/WayfindingBoxes/index.tsx
+++ /dev/null
@@ -1,141 +0,0 @@
-import React, { type ReactNode } from 'react';
-import clsx from 'clsx';
-import Heading from '@theme/Heading';
-import Link from '@docusaurus/Link';
-import styles from './styles.module.css';
-import Translate, {translate} from '@docusaurus/Translate';
-
-type WayfindingItem = {
-  title: string;
-  description: ReactNode;
-  image: string;
-  link: ReactNode;
-}
-
-export const learnMoreLink = (target: string) => (
-  <Link to={target}>
-    <Translate
-      id='component.Homepage.LearnMoreButton.Text'
-      description='The text that will be displayed on the "Learn More" buttons'>
-      Learn More
-    </Translate>
-  </Link>
-)
-
-const WayfindingWays: WayfindingItem[] = [
-  {
-    title: translate({
-      message: 'Asset Issuers',
-      id: 'components.WayfindingBoxes.AssetIssuers.Title',
-    }),
-    image: require('@site/static/icons/stellar-101.png').default,
-    description: (
-      <Translate
-        id='components.WayfindingBoxes.AssetIssuers.Description'
-        description='Short, punchy description for this "wayfinding box" on the homepage.'>
-        Issue an asset or create a custom smart contract token.
-      </Translate>
-    ),
-    link: learnMoreLink("/docs/tokens/quickstart"),
-  },
-  {
-    title: translate({
-      message: 'Smart Contract Developers',
-      id: 'components.WayfindingBoxes.SmartContractDevelopers.Title'
-    }),
-    image: require('@site/static/icons/contract.png').default,
-    description: (
-      <Translate
-        id='components.WayfindingBoxes.SmartContractDevelopers.Description'
-        description='Short, punchy description for this "wayfinding box" on the homepage.'>
-        Write smart contracts on the Stellar network.
-      </Translate>
-    ),
-    link: learnMoreLink("/docs/build/smart-contracts/getting-started"),
-  },
-  {
-    title: translate({
-      message: 'Ramps (Anchors)',
-      id: 'components.WayfindingBoxes.RampsAnchors.Title'
-    }),
-    image: require('@site/static/icons/issue-assets.png').default,
-    description: (
-      <Translate
-        id='components.WayfindingBoxes.RampsAnchors.Description'
-        description='Short, punchy description for this "wayfinding box" on the homepage.'>
-        Learn about and set up an anchor.
-      </Translate>
-    ),
-    link: learnMoreLink("/docs/learn/fundamentals/anchors"),
-  },
-  {
-    title: translate({
-      message: 'Applications',
-      id: 'components.WayfindingBoxes.Applications.Title',
-    }),
-    image: require('@site/static/icons/build-applications.png').default,
-    description: (
-      <Translate
-        id='components.WayfindingBoxes.Applications.Description'
-        description='Short, punchy description for this "wayfinding box" on the homepage.'>
-        Build a traditional wallet, dapp, or list Stellar assets on an exchange.
-      </Translate>
-    ),
-    link: learnMoreLink("/docs/build/apps/overview"),
-  },
-  {
-    title: translate({
-      message: 'Infrastructure Providers',
-      id: 'components.WayfindingBoxes.InfrastructureProviders.Title',
-    }),
-    image: require('@site/static/icons/dev-tools.png').default,
-    description: (
-      <Translate
-        id='components.WayfindingBoxes.InfrastructureProviders.Description'
-        description='Short, punchy description for this "wayfinding box" on the homepage.'>
-        Set up a Horizon or RPC service.
-      </Translate>
-    ),
-    link: learnMoreLink("/docs/data/apis"),
-  },
-  {
-    title: translate({
-      message: 'Analytics',
-      id: 'components.WayfindingBoxes.Analytics.Title'
-    }),
-    image: require('@site/static/icons/access-data.png').default,
-    description: (
-      <Translate
-        id='components.WayfindingBoxes.Analytics.Description'
-        description='Short, punchy description for this "wayfinding box" on the homepage.'>
-        Use Hubble to perform analysis on Stellar network data.
-      </Translate>
-    ),
-    link: learnMoreLink("/docs/data/analytics"),
-  },
-];
-
-function WayfindingFeature({image, title, description, link}) {
-  return (
-    <div className={clsx('col col--4')}>
-      <div>
-        <Link {...link.props} className={styles.boxIconLink}><img src={image} className={styles.boxIcon} role="img" /></Link>
-      </div>
-      <Heading as="h3" className='text--semibold'>{title}</Heading>
-      <p>{description}</p>
-      <p className="margin-bottom--lg"><Link className="button button--outline button--primary" {...link.props} /></p>
-    </div>
-  );
-}
-
-export default function WayfindingBoxes() {
-  return (
-    <section className='margin-vert--lg'>
-      <div className="row">
-        {WayfindingWays.map((props, idx) => (
-          <WayfindingFeature key={idx} {...props} />
-        ))}
-      </div>
-    </section>
-  );
-}
diff --git a/src/components/Homepage/WayfindingBoxes/styles.module.css b/src/components/Homepage/WayfindingBoxes/styles.module.css
deleted file mode 100644
index e0e49ea4b..000000000
--- a/src/components/Homepage/WayfindingBoxes/styles.module.css
+++ /dev/null
@@ -1,24 +0,0 @@
-.boxes {
-  display: flex;
-  align-items: center;
-  padding: 2rem 0;
-  width: 100%;
-}
-
-.boxIcon {
-  object-fit: cover;
-  max-width: 75%;
-  height: auto;
-  max-height: 75%;
-}
-
-.boxIconLink {
-  display: flex;
-  justify-content: center;
-  align-items: center;
-  border-radius: var(--ifm-global-radius);
-  margin-bottom: var(--ifm-heading-margin-bottom);
-  background-color: var(--ifm-color-secondary);
-  width: 100%;
-  height: 250px;
-}
diff --git a/src/components/LanguageButtons.tsx b/src/components/LanguageButtons.tsx
deleted file mode 100644
index 32117f894..000000000
--- a/src/components/LanguageButtons.tsx
+++ /dev/null
@@ -1,33 +0,0 @@
-import React from "react";
-import BrowserOnly from '@docusaurus/BrowserOnly';
-import {useColorMode} from '@docusaurus/theme-common';
-import Kotlin from '@site/static/img/docusaurus/kt.png';
-import KotlinDark from '@site/static/img/docusaurus/kt-dark.png';
-import Typescript from '@site/static/img/docusaurus/ts.png';
-import Flutter from '@site/static/img/docusaurus/flutter.png';
-import FlutterDark from '@site/static/img/docusaurus/flutter-dark.png';
-import Swift from '@site/static/img/docusaurus/swift.png';
-import SwiftDark from '@site/static/img/docusaurus/swift-dark.png';
-
-export const LanguageButtons = () => {
-    const {colorMode} = useColorMode();
-    const isDark = colorMode === 'dark';
-
-    return (
-        <BrowserOnly>
-            {() =>
-                <div style={{gap: "1rem", display: "flex", marginBottom: "1rem"}}>
-                    <img src={Typescript} onClick={() => setCookie("ts")}  style={{maxHeight: "1.2rem", cursor: "pointer"}}/>
-                    <img src={isDark ? KotlinDark : Kotlin} onClick={() => setCookie("kt")} style={{maxHeight: "1.1rem", cursor: "pointer"}}/>
-                    <img src={isDark ? FlutterDark : Flutter} onClick={() => setCookie("dart")} style={{maxHeight: "1.2rem", cursor: "pointer"}}/>
-                    <img src={isDark ? SwiftDark : Swift} onClick={() => setCookie("swift")} style={{maxHeight: "1.2rem", cursor: "pointer"}}/>
-                </div>
-            }
-        </BrowserOnly>
-    );
-};
-
-const setCookie = (str: String) => {
-    document.cookie = `selected_language=${  str  }; SameSite=Strict; expires=Fri, 31 Dec 9999 23:59:59 GMT; Secure`;
-    window.location.reload();
-};
\ No newline at end of file
diff --git a/src/components/LanguageSpecific.tsx b/src/components/LanguageSpecific.tsx
deleted file mode 100644
index 14d0a27b8..000000000
--- a/src/components/LanguageSpecific.tsx
+++ /dev/null
@@ -1,52 +0,0 @@
-import React from "react";
-import BrowserOnly from '@docusaurus/BrowserOnly';
-
-type LanguageProps = {
-    kt?: JSX.Element;
-    ts?: JSX.Element;
-    flutter?: JSX.Element;
-    swift?: JSX.Element;
-    fallback?: JSX.Element;
-};
-
-export const walletDefaultLang = "ts";
-
-export const LanguageSpecific: React.FC<LanguageProps> = (props) => (
-        <BrowserOnly fallback={props.fallback || getToShow(props, null)}>
-            {() => getToShow(props, getCookie())}
-        </BrowserOnly>
-    );
-
-const getToShow = (props: LanguageProps, cookie: String) => {
-    let toShow = <></>;
-
-    if (cookie == null) {
-        cookie = walletDefaultLang;
-    }
-
-    if (cookie == "kt") {
-        toShow = props.kt || <></>;
-    } else if (cookie == "ts") {
-        toShow = props.ts || <></>;
-    } else if (cookie == "dart") {
-        toShow = props.flutter || <></>;
-    } else if (cookie == "swift") {
-        toShow = props.swift || <></>;
-    }
-
-    return toShow;
-};
-
-export function getCookie() {
-    const name = "selected_language=";
-    const decodedCookie = decodeURIComponent(document.cookie);
-    const ca = decodedCookie.split(';');
-    for (let i = 0; i < ca.length; i++) {
-        const ind = ca[i].indexOf(name);
-        if (ind != -1) {
-            const val = ca[i].indexOf("=");
-            return ca[i].substring(val + 1, ca[i].length);
-        }
-    }
-    return null;
-}
diff --git a/src/components/MethodTable/index.tsx b/src/components/MethodTable/index.tsx
deleted file mode 100644
index d08143c5b..000000000
--- a/src/components/MethodTable/index.tsx
+++ /dev/null
@@ -1,12 +0,0 @@
-import React, { type ReactNode } from "react";
-
-import styles from "./styles.module.scss";
-
-export function MethodTable({ children, title }): ReactNode {
-  return (
-    <div className={styles.MethodTable}>
-      {title && <div className={styles.MethodTable__title}>{title}</div>}
-      {children}
-    </div>
-  );
-}
diff --git a/src/components/MethodTable/styles.module.scss b/src/components/MethodTable/styles.module.scss
deleted file mode 100644
index d39ac1016..000000000
--- a/src/components/MethodTable/styles.module.scss
+++ /dev/null
@@ -1,44 +0,0 @@
-.MethodTable {
-  $border: var(--ifm-table-border-width) solid var(--ifm-table-border-color);
-
-  --ifm-table-stripe-background: transparent;
-
-  border: $border;
-  border-radius: var(--ifm-global-radius);
-  background-color: var(--ifm-background-surface-color);
-  margin-bottom: var(--ifm-spacing-vertical);
-  max-height: 56.25rem;
-  overflow: hidden;
-
-  &__title {
-    padding: var(--ifm-table-cell-padding);
-    font-weight: var(--ifm-font-weight-bold);
-    border-bottom: $border;
-  }
-
-  table {
-    margin: 0;
-
-    &:not(:only-child) {
-      margin: 1rem 0;
-    }
-
-    * {
-      border: none;
-    }
-
-    thead {
-      display: none;
-    }
-
-    td {
-      line-height: 1.5;
-      vertical-align: top;
-      white-space: nowrap;
-
-      &:first-child {
-        font-weight: var(--ifm-font-weight-bold);
-      }
-    }
-  }
-}
diff --git a/src/components/ReaderFeedback/index.tsx b/src/components/ReaderFeedback/index.tsx
deleted file mode 100644
index 47da77d65..000000000
--- a/src/components/ReaderFeedback/index.tsx
+++ /dev/null
@@ -1,57 +0,0 @@
-import React, { useState, type ReactNode } from "react";
-import useIsBrowser from '@docusaurus/useIsBrowser';
-
-import IconThumbsUp from '@site/static/icons/thumbs-up.svg';
-import IconThumbsDown from '@site/static/icons/thumbs-down.svg';
-import Translate, { translate } from "@docusaurus/Translate";
-
-export default function ReaderFeedback(): ReactNode {
-  const [feedbackGiven, setFeedbackGiven] = useState(false);
-
-  const isBrowser = useIsBrowser();
-  if (!isBrowser) {
-    return null;
-  }
-
-  const giveFeedback = () => {
-    setFeedbackGiven(true);
-  };
-
-  return (
-    <div className="readerFeedback">
-      {feedbackGiven ? (
-        <Translate
-          id="components.ReaderFeedback.ThankYou"
-          description="Message to thank a reader for clicking a thumbsup/thumbdown button">
-          Thanks for your feedback!
-        </Translate>
-      ) : (
-        <>
-          <Translate
-            id="components.ReaderFeedback.Prompt"
-            description="A prompt to invite the reader to click a thumbsup/thumbsdown button">
-            Did you find this page helpful?
-          </Translate>
-          <IconThumbsUp
-            className="feedback_thumbsup"
-            title={translate({
-              message: "Like",
-              id: "components.ReaderFeedback.ThumbsUp.Title",
-              description: "The title value for the thumbsup icon"
-            })}
-            onClick={giveFeedback}
-          />
-          <IconThumbsDown
-            className="feedback_thumbsdown"
-            title={translate({
-              message: "Dislike",
-              id: "components.ReaderFeedback.ThumbsDown.Title",
-              description: "The title value for the thumbsdown icon"
-            })}
-            onClick={giveFeedback}
-          />
-        </>
-      )}
-    </div>
-  );
-};
diff --git a/src/components/RedirectPage.tsx b/src/components/RedirectPage.tsx
deleted file mode 100644
index 4b6cd9627..000000000
--- a/src/components/RedirectPage.tsx
+++ /dev/null
@@ -1,11 +0,0 @@
-import React, { useEffect, type ReactNode } from 'react';
-
-export function RedirectPage({ to }: { to: string }): ReactNode {
-  useEffect(() => {
-    window.location.href = to;
-  }, [to]);
-
-  return null;
-}
-
-export default RedirectPage;
diff --git a/src/components/RpcMethod.tsx b/src/components/RpcMethod.tsx
deleted file mode 100644
index 760b7f876..000000000
--- a/src/components/RpcMethod.tsx
+++ /dev/null
@@ -1,11 +0,0 @@
-import Method from "@stellar/open-rpc-docs-react";
-import React from "react";
-import type { MethodObject } from "@open-rpc/meta-schema";
-
-const CodeBlock = require('@theme/CodeBlock').default;
-const Tabs = require('@theme/Tabs').default;
-const TabItem = require('@theme/TabItem').default;
-
-export const RpcMethod = ({ method }: { method: MethodObject}) => {
-    return (<Method method={method} components={{CodeBlock, Tabs, TabItem}} />);
-};
diff --git a/src/components/SepBadge.tsx b/src/components/SepBadge.tsx
deleted file mode 100644
index e5580fad1..000000000
--- a/src/components/SepBadge.tsx
+++ /dev/null
@@ -1,21 +0,0 @@
-import React from "react";
-
-type ProductProps = {
-    tags: string;
-};
-
-export const SepBadge: React.FC<ProductProps> = (props) => {
-    const tags = props.tags.split(",");
-    const seps = tags.filter(w => w.toLowerCase().includes("sep")).sort();
-
-    if (seps.length === 0) {
-        return <></>;
-    }
-
-    return (<div style={{marginBottom: "var(--ifm-spacing-vertical)"}}>
-        {seps.map((sep) => (
-            <span style={{borderRadius: "var(--ifm-global-radius)", marginRight: "var(--ifm-global-spacing"}}
-                  className="badge badge--primary">{sep}</span>
-        ))}
-    </div>);
-};
diff --git a/src/components/StellarCliGitHubVersion.tsx b/src/components/StellarCliGitHubVersion.tsx
deleted file mode 100644
index 94cf7999d..000000000
--- a/src/components/StellarCliGitHubVersion.tsx
+++ /dev/null
@@ -1,9 +0,0 @@
-import React from "react";
-import CodeBlock from "@theme/CodeBlock";
-import { latestVersion } from "@site/src/helpers/stellarCli";
-
-export function StellarCliGitHubVersion() {
-  const command = `uses: stellar/stellar-cli@v${latestVersion}`;
-
-  return <CodeBlock language="yaml">{command}</CodeBlock>;
-}
diff --git a/src/components/StellarCliVersion.tsx b/src/components/StellarCliVersion.tsx
deleted file mode 100644
index fcf396872..000000000
--- a/src/components/StellarCliVersion.tsx
+++ /dev/null
@@ -1,9 +0,0 @@
-import React from "react";
-import CodeBlock from "@theme/CodeBlock";
-import { latestVersion } from "@site/src/helpers/stellarCli";
-
-export function StellarCliVersion() {
-  const command = `cargo install --locked stellar-cli@${latestVersion}`;
-
-  return <CodeBlock language="sh">{command}</CodeBlock>;
-}
diff --git a/src/components/StellarCliWingetVersion.tsx b/src/components/StellarCliWingetVersion.tsx
deleted file mode 100644
index b634f1ffd..000000000
--- a/src/components/StellarCliWingetVersion.tsx
+++ /dev/null
@@ -1,9 +0,0 @@
-import React from "react";
-import CodeBlock from "@theme/CodeBlock";
-import { latestVersion } from "@site/src/helpers/stellarCli";
-
-export function StellarCliWingetVersion() {
-  const command = `winget install --id Stellar.StellarCLI --version ${latestVersion}`;
-
-  return <CodeBlock language="powershell">{command}</CodeBlock>;
-}
diff --git a/src/components/StorageStrategies/AnimatedDiagram.tsx b/src/components/StorageStrategies/AnimatedDiagram.tsx
deleted file mode 100644
index 8781ac007..000000000
--- a/src/components/StorageStrategies/AnimatedDiagram.tsx
+++ /dev/null
@@ -1,109 +0,0 @@
-import React, { useEffect, useRef, useState } from "react";
-import "./diagrams.css";
-
-interface AnimatedDiagramProps {
-  id: string;
-  caption?: string;
-  children: React.ReactNode;
-}
-
-// Card that plays its CSS/SVG animations once it scrolls into view, with a
-// replay button. Animations are gated behind the .play class (see diagrams.css).
-export default function AnimatedDiagram({
-  id,
-  caption,
-  children,
-}: AnimatedDiagramProps) {
-  const ref = useRef<HTMLDivElement>(null);
-  // .play must live in React state: it gates animation-play-state in CSS, and
-  // an imperatively added class would be dropped on the next re-render.
-  const [playing, setPlaying] = useState(false);
-  const [restored, setRestored] = useState({
-    instance: false,
-    persistent: false,
-  });
-
-  useEffect(() => {
-    const el = ref.current;
-    if (!el) {
-      return undefined;
-    }
-    const io = new IntersectionObserver(
-      (entries) => {
-        entries.forEach((entry) => {
-          if (entry.isIntersecting) {
-            setPlaying(true);
-            io.unobserve(el);
-          }
-        });
-      },
-      { threshold: 0.45 },
-    );
-    io.observe(el);
-    return () => io.disconnect();
-  }, []);
-
-  const replay = () => {
-    const el = ref.current;
-    if (!el) {
-      return;
-    }
-    setRestored({ instance: false, persistent: false });
-    setPlaying(true);
-    // Toggling .play only pauses/resumes; to restart from frame 0 the
-    // animations themselves must be torn down and recreated.
-    const anims = el.querySelectorAll<HTMLElement | SVGElement>(".anim");
-    anims.forEach((a) => {
-      a.style.animation = "none";
-    });
-    void (el as HTMLElement).offsetWidth;
-    anims.forEach((a) => {
-      a.style.animation = "";
-    });
-  };
-
-  const className = [
-    "ssd",
-    playing ? "play" : "",
-    restored.instance ? "restored-instance" : "",
-    restored.persistent ? "restored-persistent" : "",
-  ]
-    .filter(Boolean)
-    .join(" ");
-
-  return (
-    <div className={className} id={id} ref={ref}>
-      <div className="diagram-controls">
-        {id === "d0" ? (
-          <>
-            <button
-              className="restore"
-              type="button"
-              aria-pressed={restored.instance}
-              onClick={() =>
-                setRestored((current) => ({ ...current, instance: true }))
-              }
-            >
-              Restore instance
-            </button>
-            <button
-              className="restore"
-              type="button"
-              aria-pressed={restored.persistent}
-              onClick={() =>
-                setRestored((current) => ({ ...current, persistent: true }))
-              }
-            >
-              Restore persistent entry
-            </button>
-          </>
-        ) : null}
-        <button className="replay" type="button" onClick={replay}>
-          {id === "d0" ? "↻ Replay expiry" : "↻ Replay"}
-        </button>
-      </div>
-      {children}
-      {caption ? <p className="caption">{caption}</p> : null}
-    </div>
-  );
-}
diff --git a/src/components/StorageStrategies/diagrams.css b/src/components/StorageStrategies/diagrams.css
deleted file mode 100644
index ea732cfa5..000000000
--- a/src/components/StorageStrategies/diagrams.css
+++ /dev/null
@@ -1,1043 +0,0 @@
-/* Animated storage diagrams — ported from the Soroban storage field guide.
-   All rules are scoped under .ssd; tier colors: amber=instance, teal=persistent, rose=temporary. */
-
-.ssd {
-  --accent: #a96a12;
-  --amber: #a96a12;
-  --amber-soft: #f0e2cb;
-  --card-2: #ebf0ee;
-  --danger: #b23a50;
-  --ink: #1c2429;
-  --line: #d8e0dd;
-  --line-strong: #b9c6c2;
-  --muted: #55666a;
-  --rose: #b23a50;
-  --rose-soft: #f2dbdf;
-  --teal: #0e7d6f;
-  --teal-soft: #d2e9e4;
-}
-
-[data-theme="dark"] .ssd {
-  --accent: #e3a44b;
-  --amber: #e3a44b;
-  --amber-soft: #3a2f1b;
-  --card-2: #202a2f;
-  --danger: #e4677a;
-  --ink: #e8edeb;
-  --line: #2a363b;
-  --line-strong: #3d4c52;
-  --muted: #93a5a2;
-  --rose: #e4677a;
-  --rose-soft: #3d2027;
-  --teal: #48bfad;
-  --teal-soft: #16352f;
-}
-
-.ssd {
-  position: relative;
-  margin: 1.4em 0 1.6em;
-  padding-top: 6px;
-  overflow-x: auto;
-}
-.ssd svg {
-  display: block;
-  width: 100%;
-  height: auto;
-  min-width: 560px;
-}
-.ssd .caption {
-  font-family: var(--ifm-font-family-base);
-  font-size: 0.78rem;
-  color: var(--muted);
-  text-align: center;
-  margin: 10px 0 2px;
-}
-.ssd .diagram-controls {
-  display: flex;
-  justify-content: flex-end;
-  flex-wrap: wrap;
-  gap: 6px;
-  margin-bottom: 4px;
-}
-#d0 {
-  margin-top: 0.8em;
-}
-#d0 .diagram-controls {
-  margin-bottom: 0;
-}
-.ssd .replay,
-.ssd .restore {
-  border: 1px solid var(--line-strong);
-  background: var(--card-2);
-  color: var(--muted);
-  border-radius: 7px;
-  font-family: var(--ifm-font-family-base);
-  font-size: 0.72rem;
-  font-weight: 650;
-  padding: 4px 10px;
-  cursor: pointer;
-}
-.ssd .replay:hover,
-.ssd .restore:hover {
-  color: var(--ink);
-  border-color: var(--accent);
-}
-.ssd .replay:focus-visible,
-.ssd .restore:focus-visible {
-  outline: 2px solid var(--accent);
-  outline-offset: 2px;
-}
-.ssd .restore[aria-pressed="true"] {
-  color: var(--ink);
-  border-color: var(--teal);
-  background: var(--teal-soft);
-}
-
-/* SVG vocabulary — every diagram is built from these */
-.ssd svg text {
-  font-family: var(--ifm-font-family-base);
-  fill: var(--muted);
-}
-.ssd svg .lbl {
-  font-size: 11px;
-  font-weight: 600;
-}
-.ssd svg .lbl-s {
-  font-size: 9.5px;
-  font-weight: 550;
-}
-.ssd svg .mono {
-  font-family: var(--ifm-font-family-monospace);
-}
-.ssd svg .cell {
-  fill: var(--card-2);
-  stroke: var(--line-strong);
-  stroke-width: 1.2;
-  rx: 5;
-}
-.ssd svg .cell-inst {
-  fill: var(--amber-soft);
-  stroke: var(--amber);
-}
-.ssd svg .cell-pers {
-  fill: var(--teal-soft);
-  stroke: var(--teal);
-}
-.ssd svg .cell-temp {
-  fill: var(--rose-soft);
-  stroke: var(--rose);
-}
-.ssd svg .wire {
-  stroke: var(--line-strong);
-  stroke-width: 1.2;
-  fill: none;
-}
-.ssd svg .dashed {
-  stroke-dasharray: 4 3;
-}
-.ssd svg .ttl-track {
-  fill: var(--line);
-  rx: 2;
-}
-.ssd svg .ttl-fill-pers {
-  fill: var(--teal);
-  rx: 2;
-}
-.ssd svg .ttl-fill-temp {
-  fill: var(--rose);
-  rx: 2;
-}
-.ssd svg .ttl-fill-inst {
-  fill: var(--amber);
-  rx: 2;
-}
-.ssd svg .dot {
-  fill: var(--ink);
-}
-.ssd svg .hatch {
-  stroke: var(--muted);
-  stroke-width: 1;
-}
-
-/* Animations: only run when .diagram has .play */
-.ssd .anim {
-  animation-play-state: paused !important;
-}
-.ssd.play .anim {
-  animation-play-state: running !important;
-}
-@media (prefers-reduced-motion: reduce) {
-  .ssd .anim {
-    animation-duration: 0.001s !important;
-    animation-delay: 0s !important;
-    animation-iteration-count: 1 !important;
-  }
-}
-/* Without JS, .play never lands and several elements' base opacity: 0 would
-   never be revealed. Jump every animation straight to its settled final frame
-   — the informative resting state — instead of freezing on frame 0. */
-@media (scripting: none) {
-  .ssd .anim {
-    animation-play-state: running !important;
-    animation-delay: -999s !important;
-  }
-}
-
-#d0 .anim {
-  animation-fill-mode: forwards;
-}
-#d0 .bar {
-  transform-box: fill-box;
-  transform-origin: left center;
-}
-@keyframes d0-drain {
-  from {
-    transform: scaleX(1);
-  }
-  to {
-    transform: scaleX(0);
-  }
-}
-@keyframes d0-in {
-  from {
-    opacity: 0;
-  }
-  to {
-    opacity: 1;
-  }
-}
-@keyframes d0-out {
-  from {
-    opacity: 1;
-  }
-  to {
-    opacity: 0.12;
-  }
-}
-@keyframes d0-gone {
-  from {
-    opacity: 1;
-  }
-  to {
-    opacity: 0;
-  }
-}
-#d0 .bar {
-  animation: d0-drain 3.2s ease-in-out forwards;
-}
-/* Explicit expiry states: archived entries dim hard and get hatched over;
-   the temporary entry disappears entirely. Outcome boxes appear at expiry. */
-#d0 .d0-entry-inst,
-#d0 .d0-entry-pers {
-  animation: d0-out 0.6s ease-out 3.15s forwards;
-}
-#d0 .d0-entry-temp {
-  animation: d0-gone 0.7s ease-in 3.15s forwards;
-}
-#d0 .d0-hatch {
-  opacity: 0;
-  animation: d0-in 0.6s ease-out 3.3s forwards;
-}
-#d0 .d0-arrow,
-#d0 .d0-arrowhead {
-  fill: none;
-  stroke: var(--line-strong);
-  stroke-width: 1.2;
-}
-#d0 .d0-expiry {
-  paint-order: stroke;
-  stroke: var(--ifm-background-color);
-  stroke-width: 6px;
-  stroke-linejoin: round;
-}
-#d0 .d0-outcome {
-  opacity: 0;
-  animation: d0-in 0.6s ease-out 3.3s forwards;
-}
-#d0 .d0-result-inst {
-  fill: var(--amber-soft);
-  stroke: var(--amber);
-}
-#d0 .d0-result-pers {
-  fill: var(--teal-soft);
-  stroke: var(--teal);
-}
-#d0 .d0-result-temp {
-  fill: var(--rose-soft);
-  stroke: var(--rose);
-}
-#d0 .d0-result-title {
-  fill: var(--ink);
-  font-size: 10px;
-}
-#d0 .d0-inst-restored,
-#d0 .d0-pers-restored {
-  display: none;
-}
-#d0.restored-instance .d0-inst-archived,
-#d0.restored-persistent .d0-pers-archived {
-  display: none;
-}
-#d0.restored-instance .d0-inst-restored,
-#d0.restored-persistent .d0-pers-restored {
-  display: inline;
-}
-/* Restoring revives the entry: back to full opacity, TTL bar refilled,
-   hatching removed. Temporary has no restore path by design. */
-#d0.restored-instance .d0-entry-inst,
-#d0.restored-persistent .d0-entry-pers {
-  animation: none;
-  opacity: 1;
-}
-#d0.restored-instance .ttl-fill-inst,
-#d0.restored-persistent .ttl-fill-pers {
-  animation: none;
-  transform: scaleX(1);
-}
-#d0.restored-instance .d0-hatch-inst,
-#d0.restored-persistent .d0-hatch-pers {
-  animation: none;
-  opacity: 0;
-}
-
-@keyframes d1-fly {
-  0% {
-    transform: translateX(0);
-    opacity: 0;
-  }
-  12% {
-    opacity: 1;
-  }
-  78% {
-    opacity: 1;
-    transform: translateX(118px);
-  }
-  100% {
-    transform: translateX(118px);
-    opacity: 0;
-  }
-}
-@keyframes d1-glow {
-  0%,
-  100% {
-    stroke: var(--amber);
-    stroke-width: 1.4;
-  }
-  50% {
-    stroke-width: 3;
-  }
-}
-#d1 .inv {
-  opacity: 0;
-  animation: d1-fly 1.6s ease-in-out 3;
-}
-#d1 .inv2 {
-  animation-delay: 0.55s;
-}
-#d1 .inv3 {
-  animation-delay: 1.1s;
-}
-#d1 .box {
-  animation: d1-glow 1.6s ease-in-out 3;
-}
-
-@keyframes d2-grow {
-  0% {
-    transform: scale(1);
-  }
-  70% {
-    transform: scale(1.22);
-  }
-  100% {
-    transform: scale(1.24);
-  }
-}
-@keyframes d2-alarm {
-  0%,
-  100% {
-    stroke: var(--line-strong);
-  }
-  60%,
-  90% {
-    stroke: var(--danger);
-    stroke-width: 2.4;
-  }
-}
-@keyframes d2-in {
-  from {
-    opacity: 0;
-    transform: translateY(6px);
-  }
-  to {
-    opacity: 1;
-    transform: translateY(0);
-  }
-}
-@keyframes d2-dim {
-  to {
-    opacity: 0.45;
-  }
-}
-#d2 .badside {
-  animation: d2-dim 0.8s ease-out 2.6s forwards;
-}
-#d2 .blob {
-  transform-box: fill-box;
-  transform-origin: center;
-  animation:
-    d2-grow 2.4s ease-in forwards,
-    d2-alarm 2.4s ease-in forwards;
-}
-#d2 .warn {
-  opacity: 0;
-  animation: d2-in 0.5s ease-out 2s forwards;
-}
-#d2 .u1 {
-  opacity: 0;
-  animation: d2-in 0.5s ease-out 0.4s forwards;
-}
-#d2 .u2 {
-  opacity: 0;
-  animation: d2-in 0.5s ease-out 0.9s forwards;
-}
-#d2 .u3 {
-  opacity: 0;
-  animation: d2-in 0.5s ease-out 1.4s forwards;
-}
-#d2 .u4 {
-  opacity: 0;
-  animation: d2-in 0.5s ease-out 1.9s forwards;
-}
-
-@keyframes d3-hit {
-  0%,
-  100% {
-    fill: var(--teal-soft);
-    stroke: var(--line-strong);
-  }
-  40%,
-  70% {
-    fill: var(--teal);
-    stroke: var(--teal);
-  }
-}
-@keyframes d3-in {
-  from {
-    opacity: 0;
-  }
-  to {
-    opacity: 1;
-  }
-}
-#d3 .hit {
-  animation: d3-hit 2.6s ease-in-out 0.8s 2;
-}
-#d3 .keylbl {
-  opacity: 0;
-  animation: d3-in 0.6s ease-out 1.2s forwards;
-}
-
-#d4 .bar {
-  transform-box: fill-box;
-  transform-origin: left center;
-}
-@keyframes d4-drain {
-  from {
-    transform: scaleX(1);
-  }
-  to {
-    transform: scaleX(0);
-  }
-}
-@keyframes d4-gone {
-  from {
-    opacity: 1;
-  }
-  to {
-    opacity: 0;
-  }
-}
-@keyframes d4-in {
-  from {
-    opacity: 0;
-  }
-  to {
-    opacity: 1;
-  }
-}
-@keyframes d4-slide {
-  from {
-    transform: translateX(24px);
-    opacity: 0;
-  }
-  to {
-    transform: translateX(0);
-    opacity: 1;
-  }
-}
-#d4 .b1 {
-  animation: d4-drain 2.6s linear forwards;
-}
-#d4 .cell1 {
-  animation: d4-gone 0.6s ease-in 2.6s forwards;
-}
-#d4 .gonelbl {
-  opacity: 0;
-  animation: d4-in 0.5s ease-out 3.1s forwards;
-}
-#d4 .old {
-  animation: d4-gone 0.8s ease-in 1.2s forwards;
-}
-#d4 .new {
-  opacity: 0;
-  animation: d4-slide 0.7s ease-out 1.6s forwards;
-}
-
-#d5 .extend-zone {
-  fill: var(--danger);
-  opacity: 0.14;
-}
-#d5 .threshold {
-  stroke: var(--danger);
-  stroke-width: 1.6;
-  stroke-dasharray: 4 3;
-}
-#d5 .bar {
-  transform-box: fill-box;
-  transform-origin: left center;
-}
-@keyframes d5-drain1 {
-  0% {
-    transform: scaleX(1);
-  }
-  100% {
-    transform: scaleX(0.72);
-  }
-}
-@keyframes d5-drain2 {
-  0% {
-    transform: scaleX(0.72);
-  }
-  100% {
-    transform: scaleX(0.42);
-  }
-}
-@keyframes d5-refill {
-  0% {
-    transform: scaleX(0.42);
-  }
-  100% {
-    transform: scaleX(1);
-  }
-}
-@keyframes d5-bolt {
-  0% {
-    transform: translateY(-16px);
-    opacity: 0;
-  }
-  40% {
-    opacity: 1;
-    transform: translateY(0);
-  }
-  100% {
-    opacity: 0;
-    transform: translateY(0);
-  }
-}
-@keyframes d5-in {
-  from {
-    opacity: 0;
-  }
-  to {
-    opacity: 1;
-  }
-}
-/* One bar, three chained transform animations: the later one wins while it
-   runs or fills, so the bar drains, drains past the threshold, then refills. */
-#d5 .pbar {
-  animation:
-    d5-drain1 1.6s linear forwards,
-    d5-drain2 1.6s linear 2.4s forwards,
-    d5-refill 0.5s ease-out 5.1s forwards;
-}
-#d5 .bolt1 {
-  opacity: 0;
-  animation: d5-bolt 1s ease-out 1.3s;
-}
-#d5 .bolt2 {
-  opacity: 0;
-  animation: d5-bolt 1s ease-out 4.1s;
-}
-#d5 .noop {
-  opacity: 0;
-  animation:
-    d5-in 0.4s ease-out 1.6s forwards,
-    d5-in 0.4s ease-out reverse 2.8s forwards;
-}
-#d5 .bump {
-  opacity: 0;
-  animation: d5-in 0.4s ease-out 5.2s forwards;
-}
-
-@keyframes d6-in {
-  from {
-    opacity: 0;
-    transform: scale(0.6);
-  }
-  to {
-    opacity: 1;
-    transform: scale(1);
-  }
-}
-@keyframes d6-approach {
-  0% {
-    transform: translate(0, 0);
-    opacity: 0;
-  }
-  30% {
-    opacity: 1;
-  }
-  60% {
-    transform: translate(-46px, 0);
-  }
-  78% {
-    transform: translate(-34px, 0);
-  }
-  100% {
-    transform: translate(-38px, 0);
-    opacity: 1;
-  }
-}
-#d6 .slot {
-  transform-box: fill-box;
-  transform-origin: center;
-  opacity: 0;
-}
-#d6 .s1 {
-  animation: d6-in 0.4s ease-out 0.3s forwards;
-}
-#d6 .s2 {
-  animation: d6-in 0.4s ease-out 0.7s forwards;
-}
-#d6 .s3 {
-  animation: d6-in 0.4s ease-out 1.1s forwards;
-}
-#d6 .s4 {
-  animation: d6-in 0.4s ease-out 1.5s forwards;
-}
-#d6 .s5 {
-  animation: d6-in 0.4s ease-out 1.9s forwards;
-}
-#d6 .s6 {
-  animation: d6-in 0.4s ease-out 2.3s forwards;
-}
-#d6 .reject {
-  opacity: 0;
-  animation: d6-approach 1.6s ease-in-out 2.8s forwards;
-}
-#d6 .panic {
-  opacity: 0;
-  /* settle visible so the resting frame still shows why #31 was rejected */
-  animation: d6-stay 0.4s ease-out 4.2s forwards;
-}
-@keyframes d6-stay {
-  from {
-    opacity: 0;
-  }
-  to {
-    opacity: 1;
-  }
-}
-
-@keyframes d7-flash {
-  0%,
-  100% {
-    fill: var(--teal-soft);
-  }
-  45%,
-  65% {
-    fill: color-mix(in srgb, var(--teal) 30%, var(--teal-soft));
-  }
-}
-@keyframes d7-in {
-  from {
-    opacity: 0;
-  }
-  to {
-    opacity: 1;
-  }
-}
-#d7 .wholeblob {
-  animation: d7-flash 2.2s ease-in-out 0.8s 2;
-}
-#d7 .onefield {
-  animation: d7-flash 2.2s ease-in-out 0.8s 2;
-}
-#d7 .u1 {
-  opacity: 0;
-  animation: d7-in 0.5s ease-out 1.6s forwards;
-}
-#d7 .u2 {
-  opacity: 0;
-  animation: d7-in 0.5s ease-out 1.6s forwards;
-}
-
-@keyframes d8-remove {
-  0%,
-  40% {
-    opacity: 1;
-  }
-  60%,
-  100% {
-    opacity: 0;
-  }
-}
-@keyframes d8-move {
-  0%,
-  55% {
-    transform: translateX(0);
-  }
-  85%,
-  100% {
-    transform: translateX(-264px);
-  }
-}
-@keyframes d8-tail {
-  0%,
-  70% {
-    opacity: 1;
-  }
-  95%,
-  100% {
-    opacity: 0.18;
-  }
-}
-@keyframes d8-in {
-  from {
-    opacity: 0;
-  }
-  to {
-    opacity: 1;
-  }
-}
-#d8 .gone {
-  animation: d8-remove 3s ease-in-out forwards;
-}
-#d8 .mover {
-  animation: d8-move 3s ease-in-out forwards;
-}
-#d8 .tail {
-  animation: d8-tail 3s ease-in-out forwards;
-}
-#d8 .note1 {
-  opacity: 0;
-  animation: d8-in 0.5s ease-out 1s forwards;
-}
-#d8 .note2 {
-  opacity: 0;
-  animation: d8-in 0.5s ease-out 1.7s forwards;
-}
-#d8 .note3 {
-  opacity: 0;
-  animation: d8-in 0.5s ease-out 2.2s forwards;
-}
-#d8 .note4 {
-  opacity: 0;
-  animation: d8-in 0.5s ease-out 2.7s forwards;
-}
-
-#d9 .bar {
-  transform-box: fill-box;
-  transform-origin: left center;
-}
-@keyframes d9-rise {
-  from {
-    transform: scaleX(0.3);
-  }
-  to {
-    transform: scaleX(0.85);
-  }
-}
-@keyframes d9-in {
-  from {
-    opacity: 0;
-  }
-  to {
-    opacity: 1;
-  }
-}
-@keyframes d9-arrive {
-  0% {
-    transform: translateY(26px);
-    opacity: 0;
-  }
-  100% {
-    transform: translateY(0);
-    opacity: 1;
-  }
-}
-#d9 .gidx {
-  animation: d9-rise 3.4s linear forwards;
-}
-#d9 .alice {
-  animation: d9-arrive 0.7s ease-out 1.6s both;
-}
-#d9 .delta {
-  opacity: 0;
-  animation: d9-in 0.5s ease-out 2.3s forwards;
-}
-#d9 .dline {
-  opacity: 0;
-  animation: d9-in 0.5s ease-out 2.3s forwards;
-}
-/* Ghost entries settle at partial opacity — visibly "untouched". */
-@keyframes d9-ghost-in {
-  from {
-    opacity: 0;
-  }
-  to {
-    opacity: 0.45;
-  }
-}
-#d9 .ghost {
-  opacity: 0;
-  animation: d9-ghost-in 0.5s ease-out 3s forwards;
-}
-
-/* d10 — checkpoints: entries append left-to-right, then a historical query
-   probes cells by binary search and settles on the last one ≤ the target. */
-@keyframes d10-in {
-  from {
-    opacity: 0;
-    transform: translateY(6px);
-  }
-  to {
-    opacity: 1;
-    transform: translateY(0);
-  }
-}
-@keyframes d10-flash {
-  0%,
-  100% {
-    stroke-width: 1.2;
-  }
-  40%,
-  70% {
-    stroke: var(--ink);
-    stroke-width: 2.6;
-  }
-}
-@keyframes d10-stay {
-  from {
-    opacity: 0;
-  }
-  to {
-    opacity: 1;
-  }
-}
-#d10 .cp1,
-#d10 .cp2,
-#d10 .cp3,
-#d10 .cp4 {
-  transform-box: fill-box;
-  transform-origin: center;
-  opacity: 0;
-}
-#d10 .cp1 {
-  animation: d10-in 0.4s ease-out 0.3s forwards;
-}
-#d10 .cp2 {
-  animation: d10-in 0.4s ease-out 0.7s forwards;
-}
-#d10 .cp3 {
-  animation: d10-in 0.4s ease-out 1.1s forwards;
-}
-#d10 .cp4 {
-  animation: d10-in 0.4s ease-out 1.5s forwards;
-}
-#d10 .cnt {
-  opacity: 0;
-  animation: d10-stay 0.5s ease-out 2s forwards;
-}
-#d10 .q {
-  opacity: 0;
-  animation: d10-stay 0.5s ease-out 2.6s forwards;
-}
-/* Probe order mirrors the code: check the newest checkpoint first,
-   then binary-search down to the last one at or before the target. */
-#d10 .pr3 {
-  animation: d10-flash 0.9s ease-in-out 3.2s;
-}
-#d10 .plbl3 {
-  opacity: 0;
-  animation: d10-stay 0.4s ease-out 3.5s forwards;
-}
-#d10 .pr2 {
-  animation: d10-flash 0.9s ease-in-out 4s;
-}
-#d10 .plbl2 {
-  opacity: 0;
-  animation: d10-stay 0.4s ease-out 4.3s forwards;
-}
-#d10 .winring {
-  opacity: 0;
-  fill: none;
-  stroke: var(--teal);
-  stroke-width: 2.2;
-  animation: d10-stay 0.5s ease-out 4.6s forwards;
-}
-#d10 .ans {
-  opacity: 0;
-  animation: d10-stay 0.5s ease-out 4.8s forwards;
-}
-
-@keyframes d11-fade {
-  from {
-    opacity: 1;
-  }
-  to {
-    opacity: 0.16;
-  }
-}
-@keyframes d11-glow {
-  0% {
-    stroke-width: 1.2;
-  }
-  60% {
-    stroke-width: 3;
-  }
-  100% {
-    stroke-width: 2;
-  }
-}
-@keyframes d11-in {
-  from {
-    opacity: 0;
-  }
-  to {
-    opacity: 1;
-  }
-}
-@keyframes d11-relight {
-  to {
-    opacity: 1;
-  }
-}
-#d11 .leaves {
-  animation: d11-fade 1.8s ease-in 1s forwards;
-}
-#d11 .proof {
-  animation:
-    d11-fade 1.8s ease-in 1s forwards,
-    d11-relight 0.7s ease-out 3.4s forwards;
-}
-#d11 .proof .cell {
-  animation: d11-glow 0.7s ease-out 3.4s forwards;
-}
-#d11 .root {
-  animation: d11-glow 1.4s ease-out 2.4s forwards;
-}
-#d11 .onchain {
-  opacity: 0;
-  animation: d11-in 0.6s ease-out 2.6s forwards;
-}
-#d11 .claimcap {
-  opacity: 0;
-  animation: d11-in 0.6s ease-out 3.6s forwards;
-}
-#d11 .claim {
-  opacity: 0;
-  animation: d11-in 0.6s ease-out 4.3s forwards;
-}
-
-@keyframes d12-spawn {
-  0% {
-    opacity: 0;
-    transform: translateX(-40px) scale(0.7);
-  }
-  100% {
-    opacity: 1;
-    transform: translateX(0) scale(1);
-  }
-}
-@keyframes d12-in {
-  from {
-    opacity: 0;
-  }
-  to {
-    opacity: 1;
-  }
-}
-#d12 .pair {
-  transform-box: fill-box;
-  transform-origin: center;
-  opacity: 0;
-}
-#d12 .w1 {
-  opacity: 0;
-  animation: d12-in 0.4s ease-out 0.4s forwards;
-}
-#d12 .w2 {
-  opacity: 0;
-  animation: d12-in 0.4s ease-out 1.1s forwards;
-}
-#d12 .w3 {
-  opacity: 0;
-  animation: d12-in 0.4s ease-out 1.8s forwards;
-}
-#d12 .pr1 {
-  animation: d12-spawn 0.7s ease-out 0.4s forwards;
-}
-#d12 .pr2 {
-  animation: d12-spawn 0.7s ease-out 1.1s forwards;
-}
-#d12 .pr3 {
-  animation: d12-spawn 0.7s ease-out 1.8s forwards;
-}
-#d12 .reg1 {
-  opacity: 0;
-  animation: d12-in 0.4s ease-out 0.8s forwards;
-}
-#d12 .reg2 {
-  opacity: 0;
-  animation: d12-in 0.4s ease-out 1.5s forwards;
-}
-#d12 .reg3 {
-  opacity: 0;
-  animation: d12-in 0.4s ease-out 2.2s forwards;
-}
-#d12 .iso {
-  opacity: 0;
-  animation: d12-in 0.6s ease-out 2.7s forwards;
-}
-
-/* Color utilities — SVG presentation attributes (fill="var(--x)") lose to any
-   CSS rule above, so accent colors must be classes. Keep these last: they
-   share specificity with .cell/.wire/text rules and win on source order. */
-.ssd svg .fill-ink {
-  fill: var(--ink);
-}
-.ssd svg .fill-amber {
-  fill: var(--amber);
-}
-.ssd svg .fill-teal {
-  fill: var(--teal);
-}
-.ssd svg .fill-rose {
-  fill: var(--rose);
-}
-.ssd svg .fill-danger {
-  fill: var(--danger);
-}
-.ssd svg .fill-none {
-  fill: none;
-}
-.ssd svg .stroke-ink {
-  stroke: var(--ink);
-}
-.ssd svg .stroke-teal {
-  stroke: var(--teal);
-}
-.ssd svg .stroke-danger {
-  stroke: var(--danger);
-}
diff --git a/src/components/StorageStrategies/diagrams.tsx b/src/components/StorageStrategies/diagrams.tsx
deleted file mode 100644
index e3e8141bc..000000000
--- a/src/components/StorageStrategies/diagrams.tsx
+++ /dev/null
@@ -1,1334 +0,0 @@
-import React from "react";
-import AnimatedDiagram from "./AnimatedDiagram";
-
-const CAPTIONS: Record<string, string> = {};
-
-const SVGS: Record<string, React.ReactNode> = {
-  d0: (
-    <svg
-      viewBox="0 0 660 192"
-      role="img"
-      aria-label="Interactive comparison of storage expiry outcomes and restoration methods. An expired contract instance entry is archived; contract code is a separate entry with its own TTL. An expired persistent key is archived individually. Either can be restored automatically through an invocation restore list or manually with RestoreFootprintOp. An expired temporary entry is deleted permanently."
-    >
-      <text x="105" y="16" textAnchor="middle" className="lbl">
-        instance()
-      </text>
-      <g className="d0-entry d0-entry-inst anim">
-        <rect
-          className="cell cell-inst"
-          x="30"
-          y="26"
-          width="150"
-          height="48"
-        />
-        <text x="105" y="48" textAnchor="middle" className="lbl-s">
-          contract instance
-        </text>
-        <text x="105" y="65" textAnchor="middle" className="lbl-s mono">
-          Admin, Config…
-        </text>
-      </g>
-      <g className="d0-hatch d0-hatch-inst anim">
-        <line className="hatch" x1="42" y1="72" x2="86" y2="28" />
-        <line className="hatch" x1="74" y1="72" x2="118" y2="28" />
-        <line className="hatch" x1="106" y1="72" x2="150" y2="28" />
-        <line className="hatch" x1="138" y1="72" x2="176" y2="34" />
-      </g>
-      <rect className="ttl-track" x="30" y="82" width="150" height="6" />
-      <rect
-        className="ttl-fill-inst bar anim"
-        x="30"
-        y="82"
-        width="150"
-        height="6"
-      />
-      <line className="d0-arrow" x1="105" y1="94" x2="105" y2="110" />
-      <path className="d0-arrowhead" d="M101 106 L105 112 L109 106" />
-      <text x="105" y="104" textAnchor="middle" className="lbl-s d0-expiry">
-        TTL expires
-      </text>
-      <g className="d0-outcome d0-inst-archived anim">
-        <rect
-          className="cell d0-result-inst"
-          x="25"
-          y="119"
-          width="160"
-          height="68"
-        />
-        <text
-          x="105"
-          y="139"
-          textAnchor="middle"
-          className="lbl d0-result-title"
-        >
-          ARCHIVED
-        </text>
-        <text x="105" y="157" textAnchor="middle" className="lbl-s">
-          contract instance entry
-        </text>
-        <text x="105" y="177" textAnchor="middle" className="lbl-s">
-          code has its own TTL
-        </text>
-      </g>
-      <g className="d0-inst-restored">
-        <rect
-          className="cell d0-result-inst"
-          x="25"
-          y="119"
-          width="160"
-          height="68"
-        />
-        <text
-          x="105"
-          y="141"
-          textAnchor="middle"
-          className="lbl d0-result-title"
-        >
-          RESTORED
-        </text>
-        <text x="105" y="161" textAnchor="middle" className="lbl-s">
-          instance entry
-          <tspan x="105" dy="15">
-            + code, if also archived
-          </tspan>
-        </text>
-      </g>
-
-      <text x="330" y="16" textAnchor="middle" className="lbl">
-        persistent()
-      </text>
-      <g className="d0-entry d0-entry-pers anim">
-        <rect
-          className="cell cell-pers"
-          x="255"
-          y="26"
-          width="150"
-          height="48"
-        />
-        <text x="330" y="48" textAnchor="middle" className="lbl-s mono">
-          Balance(alice)
-        </text>
-        <text x="330" y="65" textAnchor="middle" className="lbl-s mono">
-          → 1_000_000
-        </text>
-      </g>
-      <g className="d0-hatch d0-hatch-pers anim">
-        <line className="hatch" x1="267" y1="72" x2="311" y2="28" />
-        <line className="hatch" x1="299" y1="72" x2="343" y2="28" />
-        <line className="hatch" x1="331" y1="72" x2="375" y2="28" />
-        <line className="hatch" x1="363" y1="72" x2="401" y2="34" />
-      </g>
-      <rect className="ttl-track" x="255" y="82" width="150" height="6" />
-      <rect
-        className="ttl-fill-pers bar anim"
-        x="255"
-        y="82"
-        width="150"
-        height="6"
-      />
-      <line className="d0-arrow" x1="330" y1="94" x2="330" y2="110" />
-      <path className="d0-arrowhead" d="M326 106 L330 112 L334 106" />
-      <text x="330" y="104" textAnchor="middle" className="lbl-s d0-expiry">
-        TTL expires
-      </text>
-      <g className="d0-outcome d0-pers-archived anim">
-        <rect
-          className="cell d0-result-pers"
-          x="250"
-          y="119"
-          width="160"
-          height="68"
-        />
-        <text
-          x="330"
-          y="139"
-          textAnchor="middle"
-          className="lbl d0-result-title"
-        >
-          ARCHIVED
-        </text>
-        <text x="330" y="157" textAnchor="middle" className="lbl-s">
-          one persistent entry
-        </text>
-        <text x="330" y="177" textAnchor="middle" className="lbl-s">
-          independent TTL
-        </text>
-      </g>
-      <g className="d0-pers-restored">
-        <rect
-          className="cell d0-result-pers"
-          x="250"
-          y="119"
-          width="160"
-          height="68"
-        />
-        <text
-          x="330"
-          y="141"
-          textAnchor="middle"
-          className="lbl d0-result-title"
-        >
-          RESTORED
-        </text>
-        <text x="330" y="169" textAnchor="middle" className="lbl-s">
-          this exact key only
-        </text>
-      </g>
-
-      <text x="555" y="16" textAnchor="middle" className="lbl">
-        temporary()
-      </text>
-      <g className="d0-entry d0-entry-temp anim">
-        <rect
-          className="cell cell-temp"
-          x="480"
-          y="26"
-          width="150"
-          height="48"
-        />
-        <text x="555" y="48" textAnchor="middle" className="lbl-s mono">
-          Allowance(a,b)
-        </text>
-        <text x="555" y="65" textAnchor="middle" className="lbl-s mono">
-          → 500
-        </text>
-      </g>
-      <rect className="ttl-track" x="480" y="82" width="150" height="6" />
-      <rect
-        className="ttl-fill-temp bar anim"
-        x="480"
-        y="82"
-        width="150"
-        height="6"
-      />
-      <line className="d0-arrow" x1="555" y1="94" x2="555" y2="110" />
-      <path className="d0-arrowhead" d="M551 106 L555 112 L559 106" />
-      <text x="555" y="104" textAnchor="middle" className="lbl-s d0-expiry">
-        TTL expires
-      </text>
-      <g className="d0-outcome anim">
-        <rect
-          className="cell d0-result-temp"
-          x="475"
-          y="119"
-          width="160"
-          height="68"
-        />
-        <text
-          x="555"
-          y="139"
-          textAnchor="middle"
-          className="lbl d0-result-title"
-        >
-          DELETED
-        </text>
-        <text x="555" y="157" textAnchor="middle" className="lbl-s">
-          permanent
-        </text>
-        <text x="555" y="177" textAnchor="middle" className="lbl-s">
-          no restore path
-        </text>
-      </g>
-    </svg>
-  ),
-  d1: (
-    <svg
-      viewBox="0 0 660 170"
-      role="img"
-      aria-label="Animation: every invocation loads the contract instance entry, so its config needs no separate footprint entry."
-    >
-      <text x="120" y="52" textAnchor="middle" className="lbl">
-        invocations
-      </text>
-      <circle className="inv anim fill-ink" cx="60" cy="86" r="5" />
-      <circle className="inv inv2 anim fill-ink" cx="60" cy="86" r="5" />
-      <circle className="inv inv3 anim fill-ink" cx="60" cy="86" r="5" />
-      <line className="wire" x1="52" y1="86" x2="196" y2="86" />
-      <rect
-        className="cell cell-inst box anim"
-        x="210"
-        y="30"
-        width="240"
-        height="112"
-        rx="10"
-      />
-      <text x="330" y="54" textAnchor="middle" className="lbl fill-amber">
-        contract instance — one entry
-      </text>
-      <rect className="cell" x="232" y="66" width="60" height="26" rx="4" />
-      <text x="262" y="83" textAnchor="middle" className="lbl-s mono">
-        Admin
-      </text>
-      <rect className="cell" x="300" y="66" width="60" height="26" rx="4" />
-      <text x="330" y="83" textAnchor="middle" className="lbl-s mono">
-        Token0
-      </text>
-      <rect className="cell" x="368" y="66" width="60" height="26" rx="4" />
-      <text x="398" y="83" textAnchor="middle" className="lbl-s mono">
-        Token1
-      </text>
-      <rect className="cell" x="232" y="100" width="94" height="26" rx="4" />
-      <text x="279" y="117" textAnchor="middle" className="lbl-s mono">
-        Reserve0
-      </text>
-      <rect className="cell" x="334" y="100" width="94" height="26" rx="4" />
-      <text x="381" y="117" textAnchor="middle" className="lbl-s mono">
-        Reserve1
-      </text>
-      <text x="330" y="162" textAnchor="middle" className="lbl-s">
-        loaded with each invocation → no separate config footprint entry
-      </text>
-    </svg>
-  ),
-  d2: (
-    <svg
-      viewBox="0 0 660 190"
-      role="img"
-      aria-label="Animation: one shared map entry swells toward the 64-kibibyte entry cap, while one-entry-per-user stays small and supports independent access."
-    >
-      <g className="badside anim">
-        <text x="165" y="22" textAnchor="middle" className="lbl">
-          ✗ one shared map
-        </text>
-        <rect
-          className="cell blob anim"
-          x="105"
-          y="42"
-          width="120"
-          height="86"
-          rx="8"
-        />
-        <text x="165" y="76" textAnchor="middle" className="lbl-s mono">
-          Map&lt;Address,i128&gt;
-        </text>
-        <text x="165" y="94" textAnchor="middle" className="lbl-s">
-          every user, one entry
-        </text>
-      </g>
-      <text
-        x="165"
-        y="166"
-        textAnchor="middle"
-        className="lbl warn anim fill-danger"
-      >
-        → 64 KiB cap · rewrites · contention
-      </text>
-
-      <line className="wire dashed" x1="330" y1="30" x2="330" y2="160" />
-
-      <text x="495" y="22" textAnchor="middle" className="lbl">
-        ✓ one entry per holder
-      </text>
-      <g className="u1 anim">
-        <rect
-          className="cell cell-pers"
-          x="390"
-          y="40"
-          width="210"
-          height="24"
-          rx="4"
-        />
-        <text x="495" y="56" textAnchor="middle" className="lbl-s mono">
-          Balance(alice) → 120
-        </text>
-      </g>
-      <g className="u2 anim">
-        <rect
-          className="cell cell-pers"
-          x="390"
-          y="70"
-          width="210"
-          height="24"
-          rx="4"
-        />
-        <text x="495" y="86" textAnchor="middle" className="lbl-s mono">
-          Balance(bob) → 7_500
-        </text>
-      </g>
-      <g className="u3 anim">
-        <rect
-          className="cell cell-pers"
-          x="390"
-          y="100"
-          width="210"
-          height="24"
-          rx="4"
-        />
-        <text x="495" y="116" textAnchor="middle" className="lbl-s mono">
-          Balance(carol) → 41
-        </text>
-      </g>
-      <g className="u4 anim">
-        <text x="495" y="146" textAnchor="middle" className="lbl-s">
-          …one independently addressed entry per user,
-        </text>
-        <text x="495" y="162" textAnchor="middle" className="lbl-s">
-          transactions touch only the entries they need
-        </text>
-      </g>
-    </svg>
-  ),
-  d3: (
-    <svg
-      viewBox="0 0 660 190"
-      role="img"
-      aria-label="Animation: a two-dimensional key like owner and spender maps to exactly one independent ledger entry."
-    >
-      <text x="120" y="40" textAnchor="end" className="lbl">
-        owners ↓
-      </text>
-      <text x="255" y="22" textAnchor="middle" className="lbl">
-        spenders →
-      </text>
-      <g>
-        <rect className="cell" x="140" y="34" width="70" height="34" rx="4" />
-        <rect className="cell" x="218" y="34" width="70" height="34" rx="4" />
-        <rect className="cell" x="296" y="34" width="70" height="34" rx="4" />
-        <rect className="cell" x="140" y="76" width="70" height="34" rx="4" />
-        <rect
-          className="cell hit anim"
-          x="218"
-          y="76"
-          width="70"
-          height="34"
-          rx="4"
-        />
-        <rect className="cell" x="296" y="76" width="70" height="34" rx="4" />
-        <rect className="cell" x="140" y="118" width="70" height="34" rx="4" />
-        <rect className="cell" x="218" y="118" width="70" height="34" rx="4" />
-        <rect className="cell" x="296" y="118" width="70" height="34" rx="4" />
-      </g>
-      <g className="keylbl anim">
-        <line className="wire" x1="366" y1="93" x2="428" y2="93" />
-        <rect
-          className="cell cell-pers"
-          x="430"
-          y="70"
-          width="196"
-          height="46"
-          rx="6"
-        />
-        <text x="528" y="89" textAnchor="middle" className="lbl-s mono">
-          Allowance(alice, bob)
-        </text>
-        <text x="528" y="105" textAnchor="middle" className="lbl-s">
-          one independent entry per pair
-        </text>
-      </g>
-      <text x="330" y="180" textAnchor="middle" className="lbl-s">
-        every (owner, spender) combination = its own ledger entry — no nested
-        maps
-      </text>
-    </svg>
-  ),
-  d4: (
-    <svg
-      viewBox="0 0 660 200"
-      role="img"
-      aria-label="Animation: a temporary allowance entry is deleted when its TTL runs out, and timestamp-keyed price-history entries are deleted as their derived TTLs expire."
-    >
-      <g className="cell1 anim">
-        <rect
-          className="cell cell-temp"
-          x="40"
-          y="34"
-          width="190"
-          height="52"
-          rx="6"
-        />
-        <text x="135" y="56" textAnchor="middle" className="lbl-s mono">
-          Allowance(from, spender)
-        </text>
-        <text x="135" y="72" textAnchor="middle" className="lbl-s mono">
-          &#123; amount, live_until_ledger &#125;
-        </text>
-      </g>
-      <rect className="ttl-track" x="40" y="98" width="190" height="6" />
-      <rect
-        className="ttl-fill-temp bar b1 anim"
-        x="40"
-        y="98"
-        width="190"
-        height="6"
-      />
-      <text x="40" y="122" className="lbl-s">
-        TTL aligned to the deadline when possible
-      </text>
-      <text
-        x="135"
-        y="70"
-        textAnchor="middle"
-        className="lbl gonelbl anim fill-rose"
-      >
-        deleted without a cleanup transaction
-      </text>
-
-      <text x="470" y="26" textAnchor="middle" className="lbl">
-        self-pruning oracle history
-      </text>
-      <g className="old anim">
-        <rect
-          className="cell cell-temp"
-          x="330"
-          y="40"
-          width="56"
-          height="34"
-          rx="4"
-        />
-        <text x="358" y="61" textAnchor="middle" className="lbl-s mono">
-          t−4
-        </text>
-      </g>
-      <rect
-        className="cell cell-temp"
-        x="394"
-        y="40"
-        width="56"
-        height="34"
-        rx="4"
-      />
-      <text x="422" y="61" textAnchor="middle" className="lbl-s mono">
-        t−3
-      </text>
-      <rect
-        className="cell cell-temp"
-        x="458"
-        y="40"
-        width="56"
-        height="34"
-        rx="4"
-      />
-      <text x="486" y="61" textAnchor="middle" className="lbl-s mono">
-        t−2
-      </text>
-      <rect
-        className="cell cell-temp"
-        x="522"
-        y="40"
-        width="56"
-        height="34"
-        rx="4"
-      />
-      <text x="550" y="61" textAnchor="middle" className="lbl-s mono">
-        t−1
-      </text>
-      <g className="new anim">
-        <rect
-          className="cell cell-temp"
-          x="586"
-          y="40"
-          width="40"
-          height="34"
-          rx="4"
-        />
-        <text x="606" y="61" textAnchor="middle" className="lbl-s mono">
-          t
-        </text>
-      </g>
-      <text x="470" y="100" textAnchor="middle" className="lbl-s">
-        one entry per price round, keyed by timestamp;
-      </text>
-      <text x="470" y="116" textAnchor="middle" className="lbl-s">
-        TTL derived from retention → old rounds can expire independently
-      </text>
-      <text x="330" y="180" textAnchor="middle" className="lbl-s">
-        temporary entries are deleted on expiry without a cleanup transaction;
-        rent is half the persistent rate
-      </text>
-    </svg>
-  ),
-  d5: (
-    <svg
-      viewBox="0 0 660 190"
-      role="img"
-      aria-label="Animation: extend_ttl is a no-op while plenty of TTL remains, and extends the TTL to the bump amount once it drops below the threshold."
-    >
-      <text x="60" y="30" className="lbl">
-        TTL of <tspan className="mono">Balance(alice)</tspan>
-      </text>
-      <rect
-        className="ttl-track"
-        x="60"
-        y="70"
-        width="540"
-        height="14"
-        rx="3"
-      />
-      <rect
-        className="extend-zone"
-        x="60"
-        y="70"
-        width="324"
-        height="14"
-        rx="3"
-      />
-      <text x="222" y="110" textAnchor="middle" className="lbl-s fill-danger">
-        in this zone, an extend_ttl() call extends the TTL
-      </text>
-      <rect
-        className="ttl-fill-pers bar pbar anim"
-        x="60"
-        y="70"
-        width="540"
-        height="14"
-        rx="3"
-      />
-      <line className="threshold" x1="384" y1="58" x2="384" y2="96" />
-      <text x="384" y="52" textAnchor="middle" className="lbl-s fill-danger">
-        THRESHOLD
-      </text>
-      <text x="60" y="110" className="lbl-s">
-        0
-      </text>
-      <text x="600" y="110" textAnchor="end" className="lbl-s">
-        BUMP
-      </text>
-      <g className="bolt1 anim">
-        <text x="470" y="46" textAnchor="middle" className="lbl fill-ink">
-          extend_ttl()
-        </text>
-      </g>
-      <text x="470" y="132" textAnchor="middle" className="lbl-s noop anim">
-        above threshold → extend_ttl is a no-op
-      </text>
-      <g className="bolt2 anim">
-        <text x="270" y="46" textAnchor="middle" className="lbl fill-ink">
-          extend_ttl()
-        </text>
-      </g>
-      <text
-        x="270"
-        y="132"
-        textAnchor="middle"
-        className="lbl-s bump anim fill-teal"
-      >
-        below threshold → extended to BUMP · rent charged with transaction fees
-      </text>
-      <text x="330" y="160" textAnchor="middle" className="lbl-s">
-        if called on every access → at most one extension per 17,280 ledgers
-      </text>
-      <text x="330" y="178" textAnchor="middle" className="lbl-s">
-        not to scale — with THRESHOLD = BUMP − 17,280 ledgers, the no-op zone
-        is only the top ~3% of the bar
-      </text>
-    </svg>
-  ),
-  d6: (
-    <svg
-      viewBox="0 0 660 160"
-      role="img"
-      aria-label="Animation: a list inside one entry fills up to the hard cap the contract chose for itself; the next insert is rejected by contract code, not by a network limit."
-    >
-      <rect
-        className="cell cell-pers"
-        x="60"
-        y="40"
-        width="400"
-        height="60"
-        rx="8"
-      />
-      <text x="260" y="30" textAnchor="middle" className="lbl fill-teal">
-        ResList — ONE entry, hard cap in code
-      </text>
-      <rect
-        className="cell slot s1 anim"
-        x="76"
-        y="54"
-        width="56"
-        height="32"
-        rx="4"
-      />
-      <text x="104" y="75" textAnchor="middle" className="lbl-s mono">
-        USDC
-      </text>
-      <rect
-        className="cell slot s2 anim"
-        x="140"
-        y="54"
-        width="56"
-        height="32"
-        rx="4"
-      />
-      <text x="168" y="75" textAnchor="middle" className="lbl-s mono">
-        XLM
-      </text>
-      <rect
-        className="cell slot s3 anim"
-        x="204"
-        y="54"
-        width="56"
-        height="32"
-        rx="4"
-      />
-      <text x="232" y="75" textAnchor="middle" className="lbl-s mono">
-        EURC
-      </text>
-      <rect
-        className="cell slot s4 anim"
-        x="268"
-        y="54"
-        width="56"
-        height="32"
-        rx="4"
-      />
-      <text x="296" y="75" textAnchor="middle" className="lbl-s mono">
-        wBTC
-      </text>
-      <rect
-        className="cell slot s5 anim"
-        x="332"
-        y="54"
-        width="56"
-        height="32"
-        rx="4"
-      />
-      <text x="360" y="75" textAnchor="middle" className="lbl-s mono">
-        wETH
-      </text>
-      <rect
-        className="cell slot s6 anim"
-        x="396"
-        y="54"
-        width="48"
-        height="32"
-        rx="4"
-      />
-      <text x="420" y="75" textAnchor="middle" className="lbl-s mono">
-        …30
-      </text>
-      <g className="reject anim">
-        <rect
-          className="cell stroke-danger"
-          x="530"
-          y="54"
-          width="56"
-          height="32"
-          rx="4"
-        />
-        <text
-          x="558"
-          y="75"
-          textAnchor="middle"
-          className="lbl-s mono fill-danger"
-        >
-          #31
-        </text>
-      </g>
-      <text
-        x="558"
-        y="114"
-        textAnchor="middle"
-        className="lbl-s panic anim fill-danger"
-      >
-        <tspan x="558">rejected: contract&apos;s own cap</tspan>
-        <tspan x="558" dy="14">
-          — not a network limit
-        </tspan>
-      </text>
-      <text x="260" y="130" textAnchor="middle" className="lbl-s">
-        whole list read in 1 footprint entry · iterate in memory
-      </text>
-    </svg>
-  ),
-  d7: (
-    <svg
-      viewBox="0 0 660 200"
-      role="img"
-      aria-label="Animation: a packed entry rewrites the whole blob on any update, while split entries update one small piece at a time."
-    >
-      <text x="165" y="24" textAnchor="middle" className="lbl">
-        packed — read/written together
-      </text>
-      <rect
-        className="cell cell-pers wholeblob anim"
-        x="55"
-        y="36"
-        width="220"
-        height="92"
-        rx="8"
-      />
-      <text x="165" y="58" textAnchor="middle" className="lbl-s mono fill-ink">
-        Positions(user)
-      </text>
-      <text x="165" y="78" textAnchor="middle" className="lbl-s mono fill-ink">
-        liabilities · collateral · supply
-      </text>
-      <text x="165" y="98" textAnchor="middle" className="lbl-s fill-ink">
-        all user positions = 1 read
-      </text>
-      <text x="165" y="150" textAnchor="middle" className="lbl-s u1 anim">
-        any update rewrites the whole blob
-      </text>
-
-      <line className="wire dashed" x1="330" y1="30" x2="330" y2="170" />
-
-      <text x="495" y="24" textAnchor="middle" className="lbl">
-        split — updated independently
-      </text>
-      <rect
-        className="cell cell-pers onefield anim"
-        x="390"
-        y="36"
-        width="210"
-        height="24"
-        rx="4"
-      />
-      <text x="495" y="52" textAnchor="middle" className="lbl-s mono fill-ink">
-        ResData(asset) — rates, hot
-      </text>
-      <rect
-        className="cell cell-pers"
-        x="390"
-        y="68"
-        width="210"
-        height="24"
-        rx="4"
-      />
-      <text x="495" y="84" textAnchor="middle" className="lbl-s mono">
-        ResConfig(asset) — admin, cold
-      </text>
-      <text x="495" y="150" textAnchor="middle" className="lbl-s u2 anim">
-        hot data updates without rewriting cold config
-      </text>
-      <text x="330" y="188" textAnchor="middle" className="lbl-s">
-        heuristic: pack data usually read and written together
-      </text>
-    </svg>
-  ),
-  d8: (
-    <svg
-      viewBox="0 0 660 214"
-      role="img"
-      aria-label="Animation: swap-and-pop removal in four steps — read the last item, move it into the removed slot, fix its reverse pointer, remove the tail — all in constant time."
-    >
-      <text x="330" y="22" textAnchor="middle" className="lbl">
-        remove C from &#123;A B C D E&#125; — swap-and-pop, O(1)
-      </text>
-      <text x="93" y="52" textAnchor="middle" className="lbl-s mono">
-        idx 0
-      </text>
-      <text x="225" y="52" textAnchor="middle" className="lbl-s mono">
-        idx 1
-      </text>
-      <text x="357" y="52" textAnchor="middle" className="lbl-s mono">
-        idx 2
-      </text>
-      <text x="489" y="52" textAnchor="middle" className="lbl-s mono">
-        idx 3
-      </text>
-      <text x="621" y="52" textAnchor="middle" className="lbl-s mono">
-        idx 4
-      </text>
-      <rect
-        className="cell cell-pers"
-        x="45"
-        y="62"
-        width="96"
-        height="40"
-        rx="5"
-      />
-      <text x="93" y="87" textAnchor="middle" className="lbl mono fill-ink">
-        A
-      </text>
-      <rect
-        className="cell cell-pers"
-        x="177"
-        y="62"
-        width="96"
-        height="40"
-        rx="5"
-      />
-      <text x="225" y="87" textAnchor="middle" className="lbl mono fill-ink">
-        B
-      </text>
-      <g className="gone anim">
-        <rect
-          className="cell cell-pers"
-          x="309"
-          y="62"
-          width="96"
-          height="40"
-          rx="5"
-        />
-        <text x="357" y="87" textAnchor="middle" className="lbl mono fill-ink">
-          C
-        </text>
-      </g>
-      <rect
-        className="cell cell-pers"
-        x="441"
-        y="62"
-        width="96"
-        height="40"
-        rx="5"
-      />
-      <text x="489" y="87" textAnchor="middle" className="lbl mono fill-ink">
-        D
-      </text>
-      <g className="mover anim">
-        <rect
-          className="cell cell-pers"
-          x="573"
-          y="62"
-          width="96"
-          height="40"
-          rx="5"
-        />
-        <text x="621" y="87" textAnchor="middle" className="lbl mono fill-ink">
-          E
-        </text>
-      </g>
-      <rect
-        className="cell tail anim fill-none dashed"
-        x="573"
-        y="62"
-        width="96"
-        height="40"
-        rx="5"
-      />
-      <text x="264" y="122" className="lbl-s note1 anim">
-        1 · read the last item
-      </text>
-      <text x="264" y="138" className="lbl-s note2 anim">
-        2 · move it into the hole
-      </text>
-      <text x="264" y="154" className="lbl-s note3 anim">
-        3 · fix its reverse pointer
-      </text>
-      <text x="264" y="170" className="lbl-s note4 anim">
-        4 · remove the tail
-      </text>
-      <text x="330" y="200" textAnchor="middle" className="lbl-s">
-        a constant number of entry updates, regardless of set size — order is
-        not preserved
-      </text>
-    </svg>
-  ),
-  d9: (
-    <svg
-      viewBox="0 0 660 216"
-      role="img"
-      aria-label="Animation: a global cumulative index rises over time; a user who shows up settles only their own delta into accrued; everyone else's entries are untouched."
-    >
-      <text x="330" y="22" textAnchor="middle" className="lbl">
-        global entry — cumulative rewards-per-share, only ever increases
-      </text>
-      <rect
-        className="cell cell-pers"
-        x="130"
-        y="32"
-        width="400"
-        height="34"
-        rx="6"
-      />
-      <rect className="ttl-track" x="146" y="45" width="368" height="8" />
-      <rect
-        className="bar gidx anim ttl-fill-pers"
-        x="146"
-        y="45"
-        width="368"
-        height="8"
-      />
-      <text x="330" y="86" textAnchor="middle" className="lbl-s mono">
-        index: 1.0842… ↑ (advanced lazily when emissions are updated)
-      </text>
-
-      <g className="alice anim">
-        <rect
-          className="cell cell-pers"
-          x="80"
-          y="118"
-          width="180"
-          height="64"
-          rx="6"
-        />
-        <text x="170" y="136" textAnchor="middle" className="lbl-s mono">
-          UserEmis(alice)
-        </text>
-        <text x="170" y="152" textAnchor="middle" className="lbl-s mono">
-          index: 0.9310 → 1.0842
-        </text>
-        <text x="170" y="168" textAnchor="middle" className="lbl-s mono">
-          accrued: 12.40 → 27.72
-        </text>
-      </g>
-      <line
-        className="wire dline anim stroke-teal"
-        x1="220"
-        y1="66"
-        x2="185"
-        y2="116"
-      />
-      <text
-        x="170"
-        y="202"
-        textAnchor="middle"
-        className="lbl-s delta anim fill-teal"
-      >
-        accrued += shares × Δindex — settles when alice shows up
-      </text>
-
-      <g className="ghost anim">
-        <rect
-          className="cell dashed"
-          x="330"
-          y="118"
-          width="130"
-          height="64"
-          rx="6"
-        />
-        <text x="395" y="144" textAnchor="middle" className="lbl-s mono">
-          UserEmis(bob)
-        </text>
-        <text x="395" y="161" textAnchor="middle" className="lbl-s">
-          untouched
-        </text>
-        <rect
-          className="cell dashed"
-          x="474"
-          y="118"
-          width="130"
-          height="64"
-          rx="6"
-        />
-        <text x="539" y="144" textAnchor="middle" className="lbl-s mono">
-          …× 10,000
-        </text>
-        <text x="539" y="161" textAnchor="middle" className="lbl-s">
-          untouched
-        </text>
-      </g>
-    </svg>
-  ),
-  d10: (
-    <svg
-      viewBox="0 0 660 216"
-      role="img"
-      aria-label="Animation: voting-power checkpoints append as one persistent entry per change; a query for a past ledger binary-searches the indexed entries and lands on the last checkpoint at or before it."
-    >
-      <text x="330" y="20" textAnchor="middle" className="lbl">
-        alice&apos;s voting power — one persistent checkpoint entry per change
-      </text>
-      <text x="105" y="44" textAnchor="middle" className="lbl-s mono">
-        idx 0
-      </text>
-      <text x="245" y="44" textAnchor="middle" className="lbl-s mono">
-        idx 1
-      </text>
-      <text x="385" y="44" textAnchor="middle" className="lbl-s mono">
-        idx 2
-      </text>
-      <text x="525" y="44" textAnchor="middle" className="lbl-s mono">
-        idx 3
-      </text>
-      <g className="cp1 anim">
-        <rect
-          className="cell cell-pers"
-          x="45"
-          y="52"
-          width="120"
-          height="44"
-          rx="5"
-        />
-        <text x="105" y="70" textAnchor="middle" className="lbl-s mono">
-          ledger 100
-        </text>
-        <text x="105" y="86" textAnchor="middle" className="lbl-s mono">
-          votes 40
-        </text>
-      </g>
-      <g className="cp2 anim">
-        <rect
-          className="cell cell-pers"
-          x="185"
-          y="52"
-          width="120"
-          height="44"
-          rx="5"
-        />
-        <text x="245" y="70" textAnchor="middle" className="lbl-s mono">
-          ledger 250
-        </text>
-        <text x="245" y="86" textAnchor="middle" className="lbl-s mono">
-          votes 90
-        </text>
-      </g>
-      <g className="cp3 anim">
-        <rect
-          className="cell cell-pers pr2 anim"
-          x="325"
-          y="52"
-          width="120"
-          height="44"
-          rx="5"
-        />
-        <text x="385" y="70" textAnchor="middle" className="lbl-s mono">
-          ledger 400
-        </text>
-        <text x="385" y="86" textAnchor="middle" className="lbl-s mono">
-          votes 75
-        </text>
-      </g>
-      <g className="cp4 anim">
-        <rect
-          className="cell cell-pers pr3 anim"
-          x="465"
-          y="52"
-          width="120"
-          height="44"
-          rx="5"
-        />
-        <text x="525" y="70" textAnchor="middle" className="lbl-s mono">
-          ledger 620
-        </text>
-        <text x="525" y="86" textAnchor="middle" className="lbl-s mono">
-          votes 130
-        </text>
-      </g>
-      <rect
-        className="winring anim"
-        x="325"
-        y="52"
-        width="120"
-        height="44"
-        rx="5"
-      />
-      <text x="330" y="122" textAnchor="middle" className="lbl-s cnt anim">
-        NumCheckpoints(alice) → 4 — writes touch only the tail + counter
-      </text>
-      <text x="330" y="148" textAnchor="middle" className="lbl q anim fill-ink">
-        voting power at ledger 500? → binary-search the indexes
-      </text>
-      <text
-        x="525"
-        y="172"
-        textAnchor="middle"
-        className="lbl-s mono plbl3 anim fill-danger"
-      >
-        620 &gt; 500 ✗
-      </text>
-      <text
-        x="385"
-        y="172"
-        textAnchor="middle"
-        className="lbl-s mono plbl2 anim fill-teal"
-      >
-        400 ≤ 500 ✓
-      </text>
-      <text x="330" y="200" textAnchor="middle" className="lbl-s ans anim">
-        last checkpoint at or before ledger 500 → 75 votes · each probe reads
-        one entry
-      </text>
-    </svg>
-  ),
-  d11: (
-    <svg
-      viewBox="0 0 660 232"
-      role="img"
-      aria-label="Animation: a whole airdrop list collapses to a 32-byte Merkle root on-chain; to claim, alice re-submits her record plus proof, the path from her leaf to the root lights back up as the contract re-hashes it, and only a small Claimed(0) flag is written."
-    >
-      <g className="leaves anim">
-        <rect className="cell" x="180" y="140" width="100" height="30" rx="4" />
-        <text x="230" y="159" textAnchor="middle" className="lbl-s mono">
-          bob, 1200
-        </text>
-        <rect className="cell" x="300" y="140" width="100" height="30" rx="4" />
-        <text x="350" y="159" textAnchor="middle" className="lbl-s mono">
-          carol, 90
-        </text>
-        <rect className="cell" x="420" y="140" width="100" height="30" rx="4" />
-        <text x="470" y="159" textAnchor="middle" className="lbl-s mono">
-          …10,000 more
-        </text>
-        <line className="wire" x1="230" y1="140" x2="170" y2="106" />
-        <line className="wire" x1="350" y1="140" x2="410" y2="106" />
-        <line className="wire" x1="470" y1="140" x2="410" y2="106" />
-        <rect className="cell" x="370" y="82" width="80" height="24" rx="4" />
-        <text x="410" y="98" textAnchor="middle" className="lbl-s mono">
-          h₂₃
-        </text>
-        <line className="wire" x1="410" y1="82" x2="290" y2="52" />
-      </g>
-      <g className="proof anim">
-        <rect
-          className="cell anim"
-          x="60"
-          y="140"
-          width="100"
-          height="30"
-          rx="4"
-        />
-        <text x="110" y="159" textAnchor="middle" className="lbl-s mono">
-          alice, 500
-        </text>
-        <line className="wire" x1="110" y1="140" x2="170" y2="106" />
-        <rect
-          className="cell anim"
-          x="130"
-          y="82"
-          width="80"
-          height="24"
-          rx="4"
-        />
-        <text x="170" y="98" textAnchor="middle" className="lbl-s mono">
-          h₀₁
-        </text>
-        <line className="wire" x1="170" y1="82" x2="290" y2="52" />
-      </g>
-      <text x="290" y="196" textAnchor="middle" className="lbl-s">
-        the full list lives off-chain
-      </text>
-      <text x="290" y="214" textAnchor="middle" className="lbl-s claimcap anim">
-        to claim, alice brings her record + proof — the contract re-hashes her
-        path back to the root
-      </text>
-      <rect
-        className="cell root anim stroke-ink"
-        x="230"
-        y="26"
-        width="120"
-        height="28"
-        rx="5"
-      />
-      <text x="290" y="45" textAnchor="middle" className="lbl-s mono fill-ink">
-        RootHash
-      </text>
-      <text
-        x="222"
-        y="44"
-        textAnchor="end"
-        className="lbl-s onchain anim fill-ink"
-      >
-        32-byte root in instance storage →
-      </text>
-      <g className="claim anim">
-        <rect className="cell" x="372" y="26" width="104" height="28" rx="5" />
-        <text x="424" y="45" textAnchor="middle" className="lbl-s mono">
-          Claimed(0)
-        </text>
-        <text x="488" y="44" className="lbl-s">
-          ← one flag per actual claim
-        </text>
-      </g>
-    </svg>
-  ),
-  d12: (
-    <svg
-      viewBox="0 0 660 210"
-      role="img"
-      aria-label="Animation: a factory contract deploys one contract per trading pair and keeps the pair registry plus factory configuration; each deployed contract gets its own storage domain."
-    >
-      <rect
-        className="cell stroke-ink"
-        x="40"
-        y="46"
-        width="150"
-        height="120"
-        rx="10"
-      />
-      <text x="115" y="72" textAnchor="middle" className="lbl fill-ink">
-        factory
-      </text>
-      <text x="115" y="94" textAnchor="middle" className="lbl-s">
-        registry + factory config
-      </text>
-      <g className="reg1 anim">
-        <text x="115" y="114" textAnchor="middle" className="lbl-s mono">
-          0 → pair XLM/USDC
-        </text>
-      </g>
-      <g className="reg2 anim">
-        <text x="115" y="130" textAnchor="middle" className="lbl-s mono">
-          1 → pair XLM/EURC
-        </text>
-      </g>
-      <g className="reg3 anim">
-        <text x="115" y="146" textAnchor="middle" className="lbl-s mono">
-          2 → pair BTC/USDC
-        </text>
-      </g>
-
-      <line className="wire dashed w1 anim" x1="190" y1="80" x2="268" y2="60" />
-      <line
-        className="wire dashed w2 anim"
-        x1="190"
-        y1="106"
-        x2="268"
-        y2="106"
-      />
-      <line
-        className="wire dashed w3 anim"
-        x1="190"
-        y1="132"
-        x2="268"
-        y2="152"
-      />
-
-      <g className="pair pr1 anim">
-        <rect
-          className="cell cell-inst"
-          x="270"
-          y="36"
-          width="170"
-          height="46"
-          rx="8"
-        />
-        <text x="355" y="56" textAnchor="middle" className="lbl-s mono">
-          pair XLM/USDC
-        </text>
-        <text x="355" y="72" textAnchor="middle" className="lbl-s">
-          own instance · own TTLs
-        </text>
-      </g>
-      <g className="pair pr2 anim">
-        <rect
-          className="cell cell-inst"
-          x="270"
-          y="88"
-          width="170"
-          height="46"
-          rx="8"
-        />
-        <text x="355" y="108" textAnchor="middle" className="lbl-s mono">
-          pair XLM/EURC
-        </text>
-        <text x="355" y="124" textAnchor="middle" className="lbl-s">
-          own instance · own TTLs
-        </text>
-      </g>
-      <g className="pair pr3 anim">
-        <rect
-          className="cell cell-inst"
-          x="270"
-          y="140"
-          width="170"
-          height="46"
-          rx="8"
-        />
-        <text x="355" y="160" textAnchor="middle" className="lbl-s mono">
-          pair BTC/USDC
-        </text>
-        <text x="355" y="176" textAnchor="middle" className="lbl-s">
-          own instance · own TTLs
-        </text>
-      </g>
-      <g className="iso anim">
-        <text x="545" y="100" textAnchor="middle" className="lbl-s fill-teal">
-          independent storage domains:
-        </text>
-        <text x="545" y="118" textAnchor="middle" className="lbl-s fill-teal">
-          pair-local entries do not conflict across pairs
-        </text>
-      </g>
-    </svg>
-  ),
-};
-
-export default function StorageDiagram({ n }: { n: number }) {
-  const id = `d${n}`;
-  return (
-    <AnimatedDiagram id={id} caption={CAPTIONS[id]}>
-      {SVGS[id]}
-    </AnimatedDiagram>
-  );
-}
diff --git a/src/components/StorageStrategies/index.ts b/src/components/StorageStrategies/index.ts
deleted file mode 100644
index faa3bdbd0..000000000
--- a/src/components/StorageStrategies/index.ts
+++ /dev/null
@@ -1 +0,0 @@
-export { default } from "./diagrams";
diff --git a/src/components/WalletCodeExample.tsx b/src/components/WalletCodeExample.tsx
deleted file mode 100644
index 22b5c8637..000000000
--- a/src/components/WalletCodeExample.tsx
+++ /dev/null
@@ -1,101 +0,0 @@
-import React from 'react';
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-import CodeBlock from '@theme/CodeBlock';
-import BrowserOnly from '@docusaurus/BrowserOnly';
-import {getCookie, walletDefaultLang} from "./LanguageSpecific";
-import {CODE_LANGS} from "@site/config/constants";
-import Translate from '@docusaurus/Translate';
-
-// TODO: when TS docs are ready set to false
-const ALLOW_EMPTY_DOCS = true;
-// Set to true for local debugging
-const SHOW_ALL = false;
-
-const WALLET_LANGS = ["kt", "ts", "dart", "swift"];
-
-type WalletCodeExampleProps = {
-    children: React.ReactElement;
-};
-
-export const WalletCodeExample: React.FC<WalletCodeExampleProps> = ({children}) => <BrowserOnly fallback={getTabs(children, walletDefaultLang)}>
-        {() => getTabs(children, getCookie())}
-    </BrowserOnly>;
-
-const getTabs = (children: React.ReactElement, targetLanguage: string) => {
-    const defaultVal = CODE_LANGS[targetLanguage];
-
-    const tabs = React.Children.map(children, (child, index) => {
-        const codeProps = child.props.children.props;
-        const {className = ''} = codeProps;
-
-        let [, language] = className.split('-');
-
-        if (language === "flutter") {
-            language = "dart";
-        }
-
-        return (
-            <TabItem
-                key={language || index}
-                value={CODE_LANGS[language] || language || index}
-                label={CODE_LANGS[language] ||
-                    <Translate
-                        id='components.CodeExample.NoLanguageTabTitle'
-                        description='The tab title for a code example where no programming language was specified'>
-                        Example
-                    </Translate>
-                }
-                default={defaultVal === CODE_LANGS[language]}
-            >
-                <CodeBlock language={language} showLineNumbers>
-                    {codeProps.children}
-                </CodeBlock>
-            </TabItem>
-        );
-    });
-
-    for (let i = 0; i < WALLET_LANGS.length; i++) {
-        const language = CODE_LANGS[WALLET_LANGS[i]];
-
-        if (tabs.filter((x) => x.props.value === language).length === 0) {
-            if (ALLOW_EMPTY_DOCS) {
-                tabs.push(<TabItem
-                    key={language}
-                    value={language}
-                    label={language}
-                    default={defaultVal === language}
-                >
-                    <CodeBlock language={language} showLineNumbers>
-                        <Translate
-                            id="components.CodeExample.MissingCodeExample"
-                            description='In the Wallet-SDK code example component, this message will display when the selected programming language has no accompanying example'
-                            values={{language: language}}>
-                            {'// There is no code example for {language} yet'}
-                        </Translate>
-                    </CodeBlock>
-                </TabItem>);
-            } else {
-                throw Error(`Missing ${  language  } documentation`);
-            }
-        }
-    }
-
-   let toShowTabs = tabs;
-
-   if (!SHOW_ALL) {
-       for (let i = 0; i < tabs.length; i++) {
-           const language = CODE_LANGS[targetLanguage];
-           if (tabs[i].props.value === language) {
-                toShowTabs = [tabs[i]];
-           }
-       }
-   }
-
-    const gid = `wallet-lang${  defaultVal}`;
-    // const gid = "p-wallet" + defaultVal + Math.random()
-
-    return (<Tabs groupId={gid}>
-        {toShowTabs}
-    </Tabs>);
-};
diff --git a/src/components/WalletGuideWarn.tsx b/src/components/WalletGuideWarn.tsx
deleted file mode 100644
index 068a1cb45..000000000
--- a/src/components/WalletGuideWarn.tsx
+++ /dev/null
@@ -1,28 +0,0 @@
-import React from "react";
-import Admonition from '@theme/Admonition';
-import {LanguageButtons} from "./LanguageButtons";
-import {LanguageSpecific} from "./LanguageSpecific";
-import {CODE_LANGS} from "@site/config/constants";
-import Translate from "@docusaurus/Translate";
-
-type WalletGuideWarnProps = {
-    WIPLangs?: String[];
-};
-
-export const WalletGuideWarn: React.FC<WalletGuideWarnProps> = (props) => {
-    const langs = (props.WIPLangs || []).map(v => CODE_LANGS[v.toLowerCase()]);
-    const admonition = <Admonition type="danger" title="Important">
-        <Translate
-            id="components.WalletGuideWarn.WorkInProgress"
-            description="For the Wallets SDK, if a given programming language is incomplete, display an admonition warning the user">
-            Documentation for this language is currently work in progress. Some of information may not be applicable for this language, or missing. Code samples may be incomplete.
-        </Translate>
-    </Admonition>;
-
-    const kt = langs.indexOf("Kotlin") != -1 ? admonition : <></>;
-    const ts = langs.indexOf("TypeScript") != -1 ?  admonition: <></>;
-    const flutter = langs.indexOf("Flutter") != -1 ? admonition : <></>;
-    const swift = langs.indexOf("Swift") != -1 ? admonition : <></>;
-
-    return <LanguageSpecific kt={kt} ts={ts} flutter={flutter} swift={swift} fallback={<></>}/>;
-};
diff --git a/src/components/WrapperApiReference.tsx b/src/components/WrapperApiReference.tsx
deleted file mode 100644
index 3eb7e909a..000000000
--- a/src/components/WrapperApiReference.tsx
+++ /dev/null
@@ -1,37 +0,0 @@
-import React, { type ReactNode } from "react";
-import clsx from "clsx";
-
-import { partition } from "@site/src/helpers";
-
-const RIGHT_COLUMN_COMPONENTS_NAME = {
-  CodeExample: "CodeExample",
-  EndpointsTable: "EndpointsTable",
-  ExampleResponse: "ExampleResponse",
-  MethodTable: "MethodTable",
-  table: "table",
-};
-
-export function WrapperApiReference({ children, ...props }): ReactNode {
-  const [rightColumnContent, middleColumnContent] = React.useMemo(
-    () =>
-      partition(
-        React.Children.toArray(children),
-        (child) => RIGHT_COLUMN_COMPONENTS_NAME[child.props.mdxType],
-      ),
-    [children],
-  );
-
-  const hasRightColumn = rightColumnContent.length > 0;
-
-  return (
-    <div className="row">
-      <div className={clsx("col", hasRightColumn && "col--7")} {...props}>
-        {middleColumnContent}
-      </div>
-
-      {hasRightColumn && (
-        <aside className="col col--5">{rightColumnContent}</aside>
-      )}
-    </div>
-  );
-};
diff --git a/src/components/YouTube/index.tsx b/src/components/YouTube/index.tsx
deleted file mode 100644
index e3614621e..000000000
--- a/src/components/YouTube/index.tsx
+++ /dev/null
@@ -1,35 +0,0 @@
-import React, { type ReactNode } from 'react';
-
-export function YouTube({ ID }: { ID: string; }): ReactNode {
-  return (
-    <div
-      className="youtubeEmbed"
-      style={{
-      position: "relative",
-      width: "100%",
-      paddingBottom: "56.25%", // Make 16 x 9
-      height: 0,
-      marginBottom: "23px"
-      }}
-    >
-      <iframe
-        src={`https://www.youtube-nocookie.com/embed/${ID}?rel=0&modestbranding=1`}
-        title="Informational explainer"
-        loading="lazy"
-        allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" // tilt screen
-        allowFullScreen
-        style={{
-          position: "absolute",
-          top: 0,
-          left: 0,
-          width: "100%",
-          height: "100%",
-          border: "0px",
-          borderRadius: "25pt",
-        }}
-      ></iframe>
-    </div>
-  );
-};
-
-export default YouTube;
diff --git a/src/css/custom.scss b/src/css/custom.scss
deleted file mode 100644
index 377d9aab7..000000000
--- a/src/css/custom.scss
+++ /dev/null
@@ -1,301 +0,0 @@
-/**
- * Any CSS included here will be global. The classic template
- * bundles Infima by default. Infima is a CSS framework designed to
- * work well for content-centric websites.
- */
-
-@import url("https://fonts.googleapis.com/css2?family=IBM+Plex+Mono&display=swap");
-@import url("https://rsms.me/inter/inter.css");
-
-/* Override highlighted code line bg so fix issue with contrast */
-:root:not([data-theme="dark"]) {
-  --docusaurus-highlighted-code-line-bg: rgba(255, 255, 0, 0.15);
-}
-
-:root[data-theme="dark"] {
-  --docusaurus-highlighted-code-line-bg: rgba(255, 255, 255, 0.1);
-}
-
-/* You can override the default Infima variables here. */
-:root {
-  /* Background: White */
-  --ifm-background-color: #ffffff;
-  --ifm-background-surface-color: #f6f7f8;
-
-  /* Primary color: Teal */
-  --site-primary-hue-saturation: 185 100%;
-  --ifm-color-primary: #00a7b5;
-  --ifm-color-primary-dark: #0096a3;
-  --ifm-color-primary-darker: #008e9a;
-  --ifm-color-primary-darkest: #00757f;
-  --ifm-color-primary-light: #00b8c7;
-  --ifm-color-primary-lighter: #00c0d0;
-  --ifm-color-primary-lightest: #00d9eb;
-
-  /* Black */
-  --ifm-color-black: #0f0f0f;
-
-  --ifm-spacing-horizontal: 1.5rem;
-  --global-border-color: var(--ifm-color-emphasis-200);
-  --ifm-toc-border-color: var(--global-border-color);
-
-  --ifm-font-family-base: "Inter", sans-serif;
-  --ifm-font-family-monospace: "IBM Plex Mono", monospace;
-  --ifm-code-font-size: 80%;
-  --ifm-heading-font-weight: 400;
-
-  --ifm-table-head-font-weight: 500;
-  --ifm-table-head-background: transparent;
-  --ifm-table-stripe-background: var(--ifm-background-surface-color);
-  --ifm-table-border-color: var(--global-border-color);
-}
-
-/* For readability concerns, you should choose a lighter palette in dark mode. */
-html[data-theme="dark"] {
-  /* Primary color: Teal */
-  --ifm-color-primary: #00a7b5;
-  --ifm-color-primary-dark: #0096a3;
-  --ifm-color-primary-darker: #008e9a;
-  --ifm-color-primary-darkest: #00757f;
-  --ifm-color-primary-light: #00b8c7;
-  --ifm-color-primary-lighter: #00c0d0;
-  --ifm-color-primary-lightest: #00d9eb;
-
-  /* Background: Black */
-  --ifm-color-black: #0f0f0f;
-  --ifm-background-color: var(--ifm-color-black);
-}
-
-.markdown>h4 {
-  --ifm-h4-font-size: 1.25rem;
-
-  margin-bottom: calc(var(--ifm-heading-vertical-rhythm-bottom) * var(--ifm-leading));
-  margin-top: calc(var(--ifm-h4-vertical-rhythm-top) * var(--ifm-leading));
-}
-
-/* Reader Feedback Box */
-
-.readerFeedback {
-  display: flex;
-  flex-direction: row;
-  justify-content: center;
-  align-items: center;
-  gap: 1rem;
-
-  margin-top: 3rem;
-  padding: 1.5rem 2rem;
-  background-color: var(--ifm-menu-color-background-active);
-  font-weight: 700;
-  color: var(--ifm-color-primary);
-
-  svg {
-    height: 1.5rem;
-    width: 1.5rem;
-    transition: color var(--ifm-transition-fast) var(--ifm-transition-timing-default);
-
-    &:hover,
-    &:focus {
-      cursor: pointer;
-    }
-  }
-
-  .feedback_thumbsup {
-    color: var(--ifm-color-success-lightest);
-
-    &:hover,
-    &:focus {
-      color: var(--ifm-color-success-darkest);
-    }
-  }
-
-  .feedback_thumbsdown {
-    color: var(--ifm-color-danger-lightest);
-
-    &:hover,
-    &:focus {
-      color: var(--ifm-color-danger-darkest);
-    }
-  }
-}
-
-/* Announcement Bar(s) */
-
-div[class^="announcementBar_"] {
-  font-size: 18px;
-
-  --site-announcement-bar-stripe-color1: hsl(var(--site-primary-hue-saturation) 85%);
-  --site-announcement-bar-stripe-color2: hsl(var(--site-primary-hue-saturation) 95%);
-
-  background: repeating-linear-gradient(35deg,
-      var(--site-announcement-bar-stripe-color1),
-      var(--site-announcement-bar-stripe-color1) 20px,
-      var(--site-announcement-bar-stripe-color2) 10px,
-      var(--site-announcement-bar-stripe-color2) 40px);
-
-  height: fit-content;
-}
-
-/* Navbar customizations */
-
-.navbar .subtitle {
-  small {
-    text-transform: uppercase;
-    color: #999;
-    padding: 0.25rem 0.5rem;
-    font-size: 0.75rem;
-  }
-
-  hr {
-    width: 93%;
-    height: 4px;
-    margin: 0.4em auto;
-    background-color: var(--ifm-menu-color-background-active);
-  }
-}
-
-.navbar .dropdown>a.active {
-  color: var(--ifm-color-primary);
-}
-
-/* Sidebar HTML item customizations */
-
-.networkMenuHtmlItem small {
-  text-transform: uppercase;
-  color: #999;
-}
-
-/* Customizations to metamask openrpc package styles */
-
-select[data-testid="example-pairing-select"] {
-  padding: 0.75rem;
-  width: 100%;
-  margin-bottom: 1rem;
-  font-size: var(--ifm-font-size-base);
-  border-radius: 5px;
-}
-
-/* Hidden sidebar items */
-
-.sidebar-category-items-hidden ul {
-  display: none !important;
-}
-
-/* Header link icons */
-
-.header-github-link::before {
-  content: '';
-  width: 24px;
-  height: 24px;
-  display: flex;
-  background-color: var(--ifm-navbar-link-color);
-  mask-image: url("data:image/svg+xml,%3Csvg viewBox='0 0 24 24' xmlns='http://www.w3.org/2000/svg'%3E%3Cpath d='M12 .297c-6.63 0-12 5.373-12 12 0 5.303 3.438 9.8 8.205 11.385.6.113.82-.258.82-.577 0-.285-.01-1.04-.015-2.04-3.338.724-4.042-1.61-4.042-1.61C4.422 18.07 3.633 17.7 3.633 17.7c-1.087-.744.084-.729.084-.729 1.205.084 1.838 1.236 1.838 1.236 1.07 1.835 2.809 1.305 3.495.998.108-.776.417-1.305.76-1.605-2.665-.3-5.466-1.332-5.466-5.93 0-1.31.465-2.38 1.235-3.22-.135-.303-.54-1.523.105-3.176 0 0 1.005-.322 3.3 1.23.96-.267 1.98-.399 3-.405 1.02.006 2.04.138 3 .405 2.28-1.552 3.285-1.23 3.285-1.23.645 1.653.24 2.873.12 3.176.765.84 1.23 1.91 1.23 3.22 0 4.61-2.805 5.625-5.475 5.92.42.36.81 1.096.81 2.22 0 1.606-.015 2.896-.015 3.286 0 .315.21.69.825.57C20.565 22.092 24 17.592 24 12.297c0-6.627-5.373-12-12-12'/%3E%3C/svg%3E");
-  transition: background-color var(--ifm-transition-fast)
-    var(--ifm-transition-timing-default);
-}
-
-.goog-te-gadget .goog-te-combo {
-  margin: 0 !important;
-}
-
-.my-google-translate-button::before {
-  content: '';
-  width: 24px;
-  height: 24px;
-  display: flex;
-  background-color: var(--ifm-navbar-link-color);
-  mask-image: url("data:image/svg+xml,%3Csvg viewBox='0 0 24 24' aria-hidden='true' style='vertical-align: text-bottom' xmlns='http://www.w3.org/2000/svg'%3E%3Cpath fill='currentColor' d='M12.87 15.07l-2.54-2.51.03-.03c1.74-1.94 2.98-4.17 3.71-6.53H17V4h-7V2H8v2H1v1.99h11.17C11.5 7.92 10.44 9.75 9 11.35 8.07 10.32 7.3 9.19 6.69 8h-2c.73 1.63 1.73 3.17 2.98 4.56l-5.09 5.02L4 19l5-5 3.11 3.11.76-2.04zM18.5 10h-2L12 22h2l1.12-3h4.75L21 22h2l-4.5-12zm-2.62 7l1.62-4.33L19.12 17h-3.24z'%3E%3C/path%3E%3C/svg%3E");
-  transition: background-color var(--ifm-transition-fast)
-    var(--ifm-transition-timing-default);
-}
-
-/* Hubble data dictionary formatting */
-.scoped-data-dictionary-table table {
-  display: table;
-  width: max-content;
-  max-width: 135%;
-
-  thead {
-    color: var(--ifm-color-primary-darker);
-    background-color: var(--ifm-color-gray-300);
-    font-size: large;
-    text-align: left;
-    text-wrap: nowrap;
-  }
-
-  td {
-    font-size: small;
-  }
-}
-
-/* Indicate additional sections in the drop-down menu */
-
-.dropdown__link.has-nested-items {
-  display: inline-flex;
-  align-items: center;
-}
-
-.dropdown__link.has-nested-items::after {
-  content: '➜';
-  margin-left: 10px; // spacing (use margin instead of padding when using flex)
-  font-size: 1em;
-  line-height: 1;
-  display: inline-block;
-}
-
-.markdown-actions-container {
-  margin-bottom: calc(1.25 * var(--ifm-leading));
-
-  .button {
-    display: inline-flex;
-    align-items: center;
-    line-height: 1;
-
-    svg {
-      flex-shrink: 0;
-    }
-  }
-}
-
-/* Audits tables: stripe by audit group, tighten sub-audit rows */
-.audits-table {
-  tr:nth-child(2n) {
-    background-color: var(--ifm-table-background);
-  }
-
-  tbody:nth-of-type(2n) tr {
-    background-color: var(--ifm-table-stripe-background);
-  }
-
-  tbody td {
-    padding-bottom: 0.15rem;
-  }
-
-  tbody tr:last-child td {
-    padding-bottom: var(--ifm-table-cell-padding);
-  }
-
-  tbody tr:not(:last-child) td {
-    border-bottom: 0;
-  }
-
-  tr.sub {
-    border-top: 0;
-  }
-
-  tr.sub td {
-    border-top: 0;
-    padding-top: 0.15rem;
-  }
-
-  tr.sub td:first-child {
-    position: relative;
-    padding-left: calc(var(--ifm-table-cell-padding) + 1.25rem);
-
-    &::before {
-      content: '↳';
-      position: absolute;
-      left: var(--ifm-table-cell-padding);
-      line-height: inherit;
-    }
-  }
-}
diff --git a/src/data/agentTools.ts b/src/data/agentTools.ts
deleted file mode 100644
index 3fe12a482..000000000
--- a/src/data/agentTools.ts
+++ /dev/null
@@ -1,232 +0,0 @@
-/**
- * Single source of truth for the per-client commands that point an AI agent at
- * Stellar. Section headings and prose are not shared, see `AGENT_SECTIONS`.
- *
- * Consumed by both:
- *  - the "For agents" panel (`src/components/ForAgentsPanel`), and
- *  - the Building with AI page (`docs/build/building-with-ai.mdx`), via
- *    `src/components/AgentSetup`.
- *
- * Keep this file free of JSX so either consumer can render it its own way.
- * Notes are plain text; anything that needs to be clickable goes in `links`.
- */
-
-/**
- * Shared with the `<Tabs>` on the Building with AI page. Docusaurus persists a
- * tab group's choice under `docusaurus.tab.<groupId>`, so the panel reads and
- * writes that same key: pick Codex in the panel and the page's tabs follow.
- */
-export const AGENT_TOOL_GROUP_ID = 'mcp-client';
-
-export const AGENT_TOOL_STORAGE_KEY = `docusaurus.tab.${AGENT_TOOL_GROUP_ID}`;
-
-export interface Snippet {
-  /** Prism language for the docs page; the panel renders snippets unstyled. */
-  language: string;
-  code: string;
-}
-
-export interface ExternalLink {
-  label: string;
-  href: string;
-}
-
-export interface ToolInstructions {
-  /** Short prose above the snippets. Plain text: this has to fit a 400px panel. */
-  note?: string;
-  snippets: Snippet[];
-  links?: ExternalLink[];
-}
-
-export interface AgentTool {
-  /** Also the `<TabItem>` value, so panel and page selections line up. */
-  id: string;
-  label: string;
-  raven: ToolInstructions;
-  skills: {
-    install: ToolInstructions;
-    tryWithoutInstalling: ToolInstructions;
-  };
-}
-
-const RAVEN_MCP_URL = 'https://raven.stellar.buzz/mcp';
-const SKILL_REPO_URL = 'https://github.com/stellar/stellar-dev-skill';
-
-/** Every tool that has no first-party skills CLI installs through `npx skills`. */
-const npxSkillsInstall: ToolInstructions = {
-  note: 'Works with any tool that supports the Agent Skills standard.',
-  snippets: [
-    {
-      language: 'bash',
-      code: `npx skills add ${SKILL_REPO_URL}`,
-    },
-  ],
-};
-
-/**
- * Skills work without installing anything: point the agent at the website and
- * it reads the skills it needs. Same for every tool.
- */
-const browseSkillsInstead: ToolInstructions = {
-  note: 'Tell your agent:',
-  snippets: [
-    {
-      language: 'text',
-      code: 'Read skills.stellar.org before you start building on Stellar.',
-    },
-  ],
-};
-
-export const AGENT_TOOLS: AgentTool[] = [
-  {
-    id: 'claude-code',
-    label: 'Claude Code',
-    raven: {
-      snippets: [
-        {
-          language: 'bash',
-          code: `claude mcp add --transport http stellar-raven "${RAVEN_MCP_URL}"\n# then run /mcp -> Authenticate -> sign in in your browser`,
-        },
-      ],
-    },
-    skills: {
-      install: {
-        note: 'Adds the skill to your tool permanently.',
-        snippets: [
-          { language: 'bash', code: '/plugin marketplace add stellar/stellar-dev-skill' },
-          { language: 'bash', code: '/plugin install stellar-dev@stellar-dev' },
-        ],
-      },
-      tryWithoutInstalling: browseSkillsInstead,
-    },
-  },
-  {
-    id: 'codex',
-    label: 'Codex',
-    raven: {
-      snippets: [
-        {
-          language: 'bash',
-          code: `codex mcp add stellar-raven --url "${RAVEN_MCP_URL}"\ncodex mcp login stellar-raven  # opens your browser`,
-        },
-      ],
-    },
-    skills: {
-      install: {
-        note: 'Codex reads skills from ~/.codex/skills/.',
-        snippets: [
-          {
-            language: 'bash',
-            code: `git clone ${SKILL_REPO_URL} ~/.codex/skills/stellar-dev-skill`,
-          },
-        ],
-      },
-      tryWithoutInstalling: browseSkillsInstead,
-    },
-  },
-  {
-    id: 'vscode',
-    label: 'VS Code',
-    raven: {
-      snippets: [
-        {
-          language: 'bash',
-          code: `code --add-mcp '{"name":"stellar-raven","type":"http","url":"${RAVEN_MCP_URL}"}'`,
-        },
-      ],
-    },
-    skills: {
-      install: npxSkillsInstall,
-      tryWithoutInstalling: browseSkillsInstead,
-    },
-  },
-  {
-    id: 'cursor',
-    label: 'Cursor',
-    raven: {
-      note: 'Add to ~/.cursor/mcp.json (or .cursor/mcp.json per project). Cursor runs the OAuth sign-in on first use.',
-      snippets: [
-        {
-          language: 'json',
-          code: `{\n  "mcpServers": {\n    "stellar-raven": { "url": "${RAVEN_MCP_URL}" }\n  }\n}`,
-        },
-      ],
-    },
-    skills: {
-      install: npxSkillsInstall,
-      tryWithoutInstalling: browseSkillsInstead,
-    },
-  },
-  {
-    id: 'claude-desktop',
-    label: 'Claude desktop',
-    raven: {
-      note: 'Go to Settings -> Connectors -> Add custom connector, paste the endpoint, and approve the browser sign-in.',
-      snippets: [{ language: 'text', code: RAVEN_MCP_URL }],
-    },
-    skills: {
-      install: npxSkillsInstall,
-      tryWithoutInstalling: browseSkillsInstead,
-    },
-  },
-  {
-    id: 'other',
-    label: 'Other clients',
-    raven: {
-      note: 'For clients without native remote or OAuth support, bridge with mcp-remote.',
-      snippets: [
-        {
-          language: 'json',
-          code: `{\n  "mcpServers": {\n    "stellar-raven": {\n      "command": "npx",\n      "args": [\n        "-y",\n        "mcp-remote@latest",\n        "${RAVEN_MCP_URL}",\n        "--transport",\n        "http-only"\n      ]\n    }\n  }\n}`,
-        },
-      ],
-      links: [{ label: 'mcp-remote', href: 'https://github.com/geelen/mcp-remote' }],
-    },
-    skills: {
-      install: npxSkillsInstall,
-      tryWithoutInstalling: browseSkillsInstead,
-    },
-  },
-];
-
-export const DEFAULT_AGENT_TOOL_ID = AGENT_TOOLS[0].id;
-
-export function getAgentTool(id: string | null | undefined): AgentTool {
-  return AGENT_TOOLS.find((tool) => tool.id === id) ?? AGENT_TOOLS[0];
-}
-
-/**
- * Panel chrome: headings, blurbs, and links for the panel's three sections.
- *
- * Unlike `AGENT_TOOLS` above, this is *not* shared with the Building with AI
- * page. That page keeps its own headings because they are `##` anchors that
- * other pages link to, and its prose is longer than a 400px panel can hold.
- * The commands are the part that must never drift, and those are shared.
- */
-export const AGENT_SECTIONS = {
-  raven: {
-    title: 'Raven MCP Server',
-    description: 'Connect your AI agent to Stellar data and tooling.',
-    guide: { label: 'Full guide', href: '/docs/build/building-with-ai' },
-    links: [
-      { label: 'Try in chat', href: 'https://raven.stellar.buzz/playground' },
-      { label: 'View source', href: 'https://github.com/stellar-experimental/stellar-raven' },
-    ] satisfies ExternalLink[],
-  },
-  skills: {
-    title: 'Stellar Skills',
-    description: 'Stellar context for your agent before it writes code.',
-    home: { label: 'skills.stellar.org', href: 'https://skills.stellar.org/' },
-    modes: [
-      { id: 'install', label: 'Install' },
-      { id: 'tryWithoutInstalling', label: 'Try without installing' },
-    ],
-  },
-  llmsTxt: {
-    title: 'llms.txt',
-    href: '/llms.txt',
-    description: 'Machine-readable overview of the Stellar docs.',
-  },
-} as const;
-
-export type SkillsMode = 'install' | 'tryWithoutInstalling';
diff --git a/src/helpers/getPlatform.ts b/src/helpers/getPlatform.ts
deleted file mode 100644
index 4d848adc9..000000000
--- a/src/helpers/getPlatform.ts
+++ /dev/null
@@ -1,7 +0,0 @@
-export function getPlatform() {
-  if (!globalThis.navigator) {
-    return "unix";
-  }
-
-  return navigator.userAgent.match(/Windows/) ? "windows" : "unix";
-}
diff --git a/src/helpers/getShell.ts b/src/helpers/getShell.ts
deleted file mode 100644
index f89e59b7f..000000000
--- a/src/helpers/getShell.ts
+++ /dev/null
@@ -1,7 +0,0 @@
-export function getShell() {
-  if (!globalThis.navigator) {
-    return "bash";
-  }
-
-  return navigator.userAgent.match(/Windows/) ? "powershell" : "bash";
-}
diff --git a/src/helpers/getStellarCliLatestReleaseUrl.ts b/src/helpers/getStellarCliLatestReleaseUrl.ts
deleted file mode 100644
index 7537fedce..000000000
--- a/src/helpers/getStellarCliLatestReleaseUrl.ts
+++ /dev/null
@@ -1,5 +0,0 @@
-import { latestVersion } from "@site/src/helpers/stellarCli";
-
-export function getStellarCliLatestReleaseUrl() {
-  return `https://github.com/stellar/stellar-cli/releases/download/v${latestVersion}/stellar-cli-installer-${latestVersion}-x86_64-pc-windows-msvc.exe`;
-}
diff --git a/src/helpers/index.js b/src/helpers/index.js
deleted file mode 100644
index bddb6d149..000000000
--- a/src/helpers/index.js
+++ /dev/null
@@ -1,20 +0,0 @@
-export const combineAdjacentStrings = (list) =>
-  list.reduce((accum, item) => {
-    const lastIndex = accum.length - 1;
-    if (typeof accum[lastIndex] === "string" && typeof item === "string") {
-       
-      accum[lastIndex] = `${accum[lastIndex]}${item}`;
-    } else {
-      accum.push(item);
-    }
-    return accum;
-  }, []);
-
-export const partition = (items, filter) =>
-  items.reduce(
-    (buckets, item) => {
-      buckets[filter(item) ? 0 : 1].push(item);
-      return buckets;
-    },
-    [[], []],
-  );
diff --git a/src/helpers/stellarCli.ts b/src/helpers/stellarCli.ts
deleted file mode 100644
index 4adad1e36..000000000
--- a/src/helpers/stellarCli.ts
+++ /dev/null
@@ -1,2 +0,0 @@
-// Stub file: the real file is generated in build time by `pnpm stellar-cli:build`.
-export const latestVersion = "0.0.0";
diff --git a/src/hooks/useSelectedAgentTool.ts b/src/hooks/useSelectedAgentTool.ts
deleted file mode 100644
index b78a9030d..000000000
--- a/src/hooks/useSelectedAgentTool.ts
+++ /dev/null
@@ -1,41 +0,0 @@
-import { useCallback, useState } from 'react';
-import { useStorageSlot } from '@docusaurus/theme-common';
-
-import {
-  AGENT_TOOL_STORAGE_KEY,
-  AGENT_TOOLS,
-  DEFAULT_AGENT_TOOL_ID,
-} from '@site/src/data/agentTools';
-
-/**
- * The reader's chosen AI tool, stored under the same key Docusaurus uses for
- * the `mcp-client` tab group. Choosing a tool in the "For agents" panel picks
- * it on the Building with AI page too, and vice versa.
- *
- * This goes through Docusaurus' own storage slot rather than `localStorage`
- * directly, for two reasons: the slot applies the site's storage namespace, and
- * its `set` dispatches a synthetic `storage` event. Writing raw `localStorage`
- * would leave an already-open page's `<Tabs>` on the previous tool until the
- * next navigation, because native storage events only fire in *other* windows.
- */
-export default function useSelectedAgentTool(): [string, (id: string) => void] {
-  const [storedValue, storageSlot] = useStorageSlot(AGENT_TOOL_STORAGE_KEY);
-
-  // Storage can be a no-op (incognito, iframes, strict privacy settings). Local
-  // state keeps the picker working for the current page view when it is.
-  const [fallbackToolId, setFallbackToolId] = useState(DEFAULT_AGENT_TOOL_ID);
-
-  const toolId = AGENT_TOOLS.some((tool) => tool.id === storedValue)
-    ? (storedValue as string)
-    : fallbackToolId;
-
-  const selectTool = useCallback(
-    (id: string) => {
-      setFallbackToolId(id);
-      storageSlot.set(id);
-    },
-    [storageSlot],
-  );
-
-  return [toolId, selectTool];
-}
diff --git a/src/pages/index.mdx b/src/pages/index.mdx
deleted file mode 100644
index 75c772820..000000000
--- a/src/pages/index.mdx
+++ /dev/null
@@ -1,35 +0,0 @@
----
-hide_table_of_contents: true
-title: "Developer Tools, SDKs & Core Resources for Building"
-description: "Build decentralized apps, issue assets, and write smart contracts on Stellar's Layer-1 blockchain. Connect to financial rails and create interoperable projects in one open network"
----
-
-import WayfindingBoxes from "@site/src/components/Homepage/WayfindingBoxes";
-import NavigatingTheDocs from "@site/src/components/Homepage/NavigatingTheDocs";
-import DeveloperResources from "@site/src/components/Homepage/DeveloperResources";
-
-# Welcome to the Stellar Developer Docs
-
-Stellar is a layer-1, open-source, decentralized, peer-to-peer blockchain network that provides a framework for developers to create applications, issue assets, write smart contracts, and connect to existing financial rails. Stellar is designed to enable creators, innovators, and developers to build projects on the network that can interoperate with each other.
-
-The developer docs will teach you how to build applications, issue and use tokens, write smart contracts, set up on- and off-ramps, set up a validator node, and more.
-
-## **Stellar for...**
-
-<WayfindingBoxes />
-
-<hr />
-
-## **Navigating the docs**
-
-What each main section of the developer docs contains.
-
-<NavigatingTheDocs />
-
-## **Developer resources**
-
-Interact with other Stellar developers, keep up with ecosystem standards and protocol upgrades, and learn about upcoming events.
-
-<DeveloperResources />
-
-<hr />
diff --git a/src/plugins/analytics-module/gtag-stub.ts b/src/plugins/analytics-module/gtag-stub.ts
deleted file mode 100644
index 8cf578c81..000000000
--- a/src/plugins/analytics-module/gtag-stub.ts
+++ /dev/null
@@ -1,39 +0,0 @@
-type AnalyticsWindow = Window & {
-  dataLayer?: unknown[];
-  gtag?: (...args: unknown[]) => void;
-  // docusaurus-plugin-sentry loader stub; production-only, queues until SDK loads.
-  Sentry?: { captureMessage?: (message: string, level?: string) => void };
-  __gtagStubInstalled?: boolean; // for manual/E2E verification
-};
-
-if (typeof window !== 'undefined') {
-  const analyticsWindow = window as AnalyticsWindow;
-
-  // plugin-google-gtag calls window.gtag unguarded on every route change. It's a
-  // mutable global; if left non-callable, navigation throws. Install a stub.
-  if (typeof analyticsWindow.gtag !== 'function') {
-    analyticsWindow.dataLayer ??= [];
-
-    analyticsWindow.gtag = function () {
-      (analyticsWindow.dataLayer ??= []).push(arguments);
-    };
-
-    analyticsWindow.__gtagStubInstalled = true;
-
-    // Measure real-world incidence (#2417). Via Sentry, not gtag/dataLayer —
-    // whatever suppressed gtag likely blocks Google too; Sentry is a separate
-    // origin. Deferred + guarded so telemetry never breaks navigation.
-    setTimeout(() => {
-      try {
-        analyticsWindow.Sentry?.captureMessage?.(
-          'gtag-stub: window.gtag not callable at bootstrap',
-          'warning',
-        );
-      } catch {
-        /* no-op */
-      }
-    });
-  }
-}
-
-export {};
diff --git a/src/plugins/analytics-module/index.ts b/src/plugins/analytics-module/index.ts
deleted file mode 100644
index d42a305e1..000000000
--- a/src/plugins/analytics-module/index.ts
+++ /dev/null
@@ -1,29 +0,0 @@
-import path from 'path';
-
-import type { Plugin } from '@docusaurus/types';
-
-export default function analyticsModulePlugin(): Plugin {
-  return {
-    name: 'stellar-docs-analytics-module-plugin',
-
-    getClientModules() {
-      return [path.join(__dirname, 'gtag-stub.ts')];
-    },
-
-    injectHtmlTags() {
-      return {
-        preBodyTags: [
-          {
-            tagName: 'script',
-            innerHTML: `
-              if (typeof window.ga === "function") {
-                window.ga("require", "linker");
-                window.ga("linker:autolink", ["www.stellar.org", "stellar.org"]);
-              }
-            `,
-          },
-        ],
-      };
-    },
-  };
-}
diff --git a/src/plugins/markdown-source-map/index.ts b/src/plugins/markdown-source-map/index.ts
deleted file mode 100644
index 64993392d..000000000
--- a/src/plugins/markdown-source-map/index.ts
+++ /dev/null
@@ -1,64 +0,0 @@
-import fs from 'fs';
-import path from 'path';
-
-import type { LoadContext, Plugin } from '@docusaurus/types';
-
-// Flatten nested Docusaurus route tree into a flat array
-function flattenRoutes(routes: any[]): any[] {
-  return routes.flatMap((route) => [
-    route,
-    ...(route.routes ? flattenRoutes(route.routes) : []),
-  ]);
-}
-
-// Strip baseUrl prefix from a URL path to get build-relative path
-function stripBaseUrl(urlPath: string, baseUrl: string): string {
-  if (baseUrl !== '/' && urlPath.startsWith(baseUrl)) {
-    return urlPath.slice(baseUrl.length);
-  }
-  return urlPath.startsWith('/') ? urlPath.slice(1) : urlPath;
-}
-
-/**
- * Companion to docusaurus-markdown-source-plugin: dumps the mapping from
- * each generated `.md` twin back to its source file, for
- * scripts/rewrite_md_code_examples.mjs (the `postbuild` npm hook) to consume.
- *
- * The regeneration itself cannot live in this plugin: Docusaurus runs all
- * plugins' postBuild hooks concurrently, so there is no way to reliably run
- * after docusaurus-markdown-source-plugin has written the twins. Writing the
- * map is order-independent; the npm `postbuild` hook is guaranteed to run
- * after the whole build.
- *
- * @param context site context, provided by Docusaurus
- * @returns plugin instance that writes the twin-to-source map
- */
-export default function markdownSourceMapPlugin(context: LoadContext): Plugin {
-  return {
-    name: 'stellar-docs-markdown-source-map-plugin',
-
-    async postBuild({ outDir, routes, baseUrl }) {
-      const entries = flattenRoutes(routes)
-        .filter((route) => {
-          const src = route.metadata?.sourceFilePath;
-          return src && (src.endsWith('.md') || src.endsWith('.mdx'));
-        })
-        .map((route) => {
-          const markdownUrl = route.path.endsWith('/')
-            ? route.path + 'index.md'
-            : route.path + '.md';
-          return {
-            routePath: route.path,
-            sourceFilePath: route.metadata.sourceFilePath,
-            twinRelPath: stripBaseUrl(markdownUrl, baseUrl),
-          };
-        });
-
-      const outputPath = path.join(outDir, '.md-source-map.json');
-      fs.writeFileSync(outputPath, JSON.stringify(entries, null, 2));
-      console.log(
-        `[markdown-source-map] Wrote ${entries.length} twin-to-source entries to ${path.relative(context.siteDir, outputPath)}`,
-      );
-    },
-  };
-}
diff --git a/src/plugins/route-export/index.ts b/src/plugins/route-export/index.ts
deleted file mode 100644
index 680a81a37..000000000
--- a/src/plugins/route-export/index.ts
+++ /dev/null
@@ -1,47 +0,0 @@
-import fs from 'fs';
-import path from 'path';
-
-import type { LoadContext, Plugin } from "@docusaurus/types";
-
-export interface PluginOptions {
-  outputDir?: string;
-  outputFilename?: string;
-}
-
-/**
- * Write all route paths to a text file, to be checked in to git. This allows
- * for easier comparison of route changes, and a way to identify if nginx
- * redirects are required.
- *
- * @param context site context, provided by Docusaurus
- * @param options user-defined options
- * @returns plugin instance that will write all routes to a text file
- */
-export default async function routeExportPlugin(
-  context: LoadContext,
-  options?: PluginOptions
-): Promise<Plugin> {
-  return {
-    name: 'stellar-docs-route-export-plugin',
-
-    async postBuild({ routesPaths }) {
-      // Get all routes from Docusaurus
-      const routes = routesPaths.map(route => {
-        // Ensure routes are relative to the site URL
-        return route.startsWith('/') ? route : `/${route}`;
-      });
-
-      // Sort routes for better readability
-      routes.sort();
-
-      // Create content with one URL per line
-      const content = routes.join('\n') + '\n';
-
-      // Write to the repo root directory
-      const outputPath = path.join(options.outputDir || context.siteDir, options.outputFilename || 'routes.txt');
-      fs.writeFileSync(outputPath, content);
-
-      console.log(`✅ Exported ${routes.length} routes to ${outputPath}`);
-    }
-  }
-}
diff --git a/src/sidebar-generator.js b/src/sidebar-generator.js
deleted file mode 100644
index d5484e5f3..000000000
--- a/src/sidebar-generator.js
+++ /dev/null
@@ -1,84 +0,0 @@
-import fs from "fs";
-import path from "path";
-
-module.exports = async ({ defaultSidebarItemsGenerator, ...args }) => {
-  const docs = args.docs.filter(
-    (item) => !/horizon.*\.(api|tag)\.mdx$/.test(item.source)
-  );
-
-  // Get the sidebar items that are generated by default
-  const sidebarItems = await defaultSidebarItemsGenerator({ ...args, docs });
-
-  const apisOverviewCategory = sidebarItems.find(
-    (item) => item.type === "category" && item.label.toLowerCase() === "apis overview",
-  );
-
-  if (apisOverviewCategory) {
-    const horizonCategory = apisOverviewCategory.items.find(
-      (item) => item.type === "category" && item.label.toLowerCase() === "horizon",
-    );
-
-    if (horizonCategory) {
-      const apiReference = horizonCategory.items.find(
-        (item) => item.type === "category" && item.label.toLowerCase() === "api reference",
-      );
-
-      if (apiReference) {
-        const resources = apiReference.items.find(
-          (item) =>
-            item.type === "category" && item.label.toLowerCase() === "resources",
-        );
-        const aggregations = apiReference.items.find(
-          (item) =>
-            item.type === "category" && item.label.toLowerCase() === "aggregations"
-        )
-
-        const sidebarPath = path.join(
-          args.version.contentPath,
-          args.item.dirName,
-          "./apis/horizon/api-reference/sidebar.ts",
-        );
-
-        if (resources && fs.existsSync(sidebarPath)) {
-          const generatedApiSidebar = require(sidebarPath)[0];
-
-          const categories = resources.items.filter(
-            (item) => item.type === "category",
-          );
-
-          categories.forEach((category) => {
-            const generatedCategory = generatedApiSidebar.items.find(
-              (item) => item.type === "category" && item.label === category.label,
-            );
-
-            if (generatedCategory) {
-              category.items = [...category.items, ...generatedCategory.items];
-            }
-          });
-        }
-
-        if (aggregations && fs.existsSync(sidebarPath)) {
-          const generatedApiSidebar = require(sidebarPath)[1];
-
-          const categories = aggregations.items.filter(
-            (item) => item.type === "category",
-          );
-
-          categories.forEach((category) => {
-            const generatedCategory = generatedApiSidebar.items.find(
-              (item) => item.type === "category" && item.label === category.label,
-            );
-
-            if (generatedCategory) {
-              category.items = [...category.items, ...generatedCategory.items];
-            }
-          });
-        }
-
-      }
-    }
-  }
-
-  // return the sidebar items
-  return sidebarItems;
-};
diff --git a/src/template.mustache b/src/template.mustache
deleted file mode 100644
index 338a0e7a8..000000000
--- a/src/template.mustache
+++ /dev/null
@@ -1,45 +0,0 @@
----
-id: {{{id}}}
-title: "{{{title}}}"
-description: "{{{frontMatter.description}}}"
-{{^api}}
-sidebar_label: Introduction
-{{/api}}
-{{#api}}
-sidebar_label: "{{{title}}}"
-{{/api}}
-{{^api}}
-sidebar_position: 0
-{{/api}}
-hide_title: true
-{{#api}}
-hide_table_of_contents: true
-{{/api}}
-{{#json}}
-api: {{{json}}}
-{{/json}}
-{{#api.method}}
-sidebar_class_name: "{{{api.method}}} api-method"
-{{/api.method}}
-{{#infoPath}}
-info_path: {{{infoPath}}}
-{{/infoPath}}
-custom_edit_url: null
-{{#frontMatter.proxy}}
-proxy: {{{frontMatter.proxy}}}
-{{/frontMatter.proxy}}
-{{#frontMatter.hide_send_button}}
-hide_send_button: true
-{{/frontMatter.hide_send_button}}
-{{#frontMatter.show_extensions}}
-show_extensions: true
-{{/frontMatter.show_extensions}}
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-{{#api}}
-<SepBadge tags={'{{{api.x-seps}}}'} />
-{{/api}}
-
-{{{markdown}}}
diff --git a/src/theme/ApiExplorer/index.tsx b/src/theme/ApiExplorer/index.tsx
deleted file mode 100644
index 6124ff207..000000000
--- a/src/theme/ApiExplorer/index.tsx
+++ /dev/null
@@ -1,26 +0,0 @@
-import React, { type ReactNode } from 'react';
-import ApiExplorer from '@theme-original/ApiExplorer';
-import Admonition from "@theme/Admonition";
-import Link from "@docusaurus/Link";
-
-import type ApiExplorerType from '@theme-original/ApiExplorer';
-import type {WrapperProps} from '@docusaurus/types';
-
-type Props = WrapperProps<typeof ApiExplorerType>;
-
-export default function ApiExplorerWrapper(props: Props): ReactNode {
-  return (
-    <>
-      <ApiExplorer {...props} />
-
-      {props?.item?.["x-supports-streaming"] && (
-        <Admonition type="tip" title="Supports Streaming">
-          This endpoint supports streaming. To read more about this, visit the
-          <Link className="padding-horiz--xs" to="/docs/data/apis/horizon/api-reference/structure/streaming">
-            streaming section.
-          </Link>
-        </Admonition>
-      )}
-    </>
-  );
-}
diff --git a/src/theme/DocCardList/index.tsx b/src/theme/DocCardList/index.tsx
deleted file mode 100644
index 1ac1e68bb..000000000
--- a/src/theme/DocCardList/index.tsx
+++ /dev/null
@@ -1,78 +0,0 @@
-import React, {type ReactNode} from 'react';
-import clsx from 'clsx';
-import DocCardList from '@theme-original/DocCardList';
-import type DocCardListType from '@theme/DocCardList';
-import { useCurrentSidebarCategory, useDocById } from '@docusaurus/plugin-content-docs/client';
-import type { PropSidebarItem } from '@docusaurus/plugin-content-docs';
-import type {WrapperProps} from '@docusaurus/types';
-
-type Props = WrapperProps<typeof DocCardListType>;
-
-interface CustomDocCardListProps {
-  items: PropSidebarItem[];
-  className: string;
-}
-
-
-function DocCardListForCurrentSidebarCategory(props: CustomDocCardListProps): ReactNode {
-  const category = useCurrentSidebarCategory()
-
-  const exampleContractsLabels = ['Example Contracts', 'Ejemplos de contratos'];
-  const howToGuidesLabels = ['How-To Guides', 'Guías de Cómo-Hacer'];
-
-  if (exampleContractsLabels.includes(category.label)) {
-    return <ExampleContractsDocCardList items={category.items} className={props.className} />
-  } else if (howToGuidesLabels.includes(category.label)) {
-    return <GuidesDocCardList items={category.items} className={props.className} />
-  }
-  return <DocCardList items={category.items} className={props.className} />
-}
-
-function ExampleContractsDocCardList(props: CustomDocCardListProps): ReactNode {
-  const { items, className } = props;
-  return (
-    <section className={clsx('row', className)}>
-      {items?.filter(item => item.type === 'link').map((item) => {
-        const doc = useDocById(item.docId ?? undefined);
-        item.description = item.description ?? doc?.description;
-        return (
-          <p className='col col--12'>
-            <a href={item.href}><strong>{item.label}</strong></a> - {item.description}
-          </p>
-        );
-      })}
-    </section>
-  );
-}
-
-function GuidesDocCardList(props: CustomDocCardListProps): ReactNode {
-  const {items, className} = props;
-  return (
-    <div className={clsx('row', className)}>
-      {items?.filter(item => item.type === 'category').map((item) => {
-        return (
-          <section className={clsx('col', 'col--6', 'margin-bottom--lg', className)}>
-            <h2>{item.label}</h2>
-            {item.items.filter(item => item.type === 'link').map((item) =>
-              <p className='margin-bottom--sm'><a href={item.href}>{item.label}</a></p>,
-            )}
-          </section>
-        );
-      })}
-    </div>
-  );
-}
-
-export default function DocCardListWrapper(props: Props): ReactNode {
-  const { items, className } = props;
-
-  if (!items) {
-    return <DocCardListForCurrentSidebarCategory {...items} {...className} />
-  }
-
-  return (
-    <>
-      <DocCardList {...props} />
-    </>
-  );
-}
diff --git a/src/theme/DocItem/Footer/index.tsx b/src/theme/DocItem/Footer/index.tsx
deleted file mode 100644
index 6e87a7d5a..000000000
--- a/src/theme/DocItem/Footer/index.tsx
+++ /dev/null
@@ -1,38 +0,0 @@
-import React, {type ReactNode} from 'react';
-import Footer from '@theme-original/DocItem/Footer';
-import type FooterType from '@theme/DocItem/Footer';
-import type {WrapperProps} from '@docusaurus/types';
-
-import Translate from '@docusaurus/Translate';
-import DocCardList from '@theme/DocCardList';
-import { useDoc } from '@docusaurus/plugin-content-docs/client'
-import ReaderFeedback from '@site/src/components/ReaderFeedback';
-import clsx from 'clsx';
-
-type Props = WrapperProps<typeof FooterType>;
-
-export default function FooterWrapper(props: Props): ReactNode {
-  const { metadata } = useDoc();
-
-  const canDisplayDocCardsOnGuide: boolean = (metadata.permalink?.includes('/docs/build/guides')
-    || metadata.permalink?.includes('/docs/tools/cli/cookbook'));
-  const isMainGuidesPage: boolean = metadata.id === 'build/guides/README';
-
-  return (
-    <>
-      {canDisplayDocCardsOnGuide &&
-        <div className={clsx(isMainGuidesPage ? 'margin-top--lg' : 'margin-top--xl')}>
-          {!isMainGuidesPage && <h3>
-            <Translate
-              id='components.HowToGuides.GuidesInCategory'
-              description='The h3 title do display the other related how-to guides'
-            >Guides in this category:</Translate>
-          </h3>}
-          <DocCardList />
-        </div>
-      }
-      <ReaderFeedback pageId={metadata.id} />
-      <Footer {...props} />
-    </>
-  );
-}
diff --git a/src/theme/DocSidebar/index.tsx b/src/theme/DocSidebar/index.tsx
deleted file mode 100644
index 242e42cf0..000000000
--- a/src/theme/DocSidebar/index.tsx
+++ /dev/null
@@ -1,32 +0,0 @@
-import React, { type ReactNode } from 'react';
-import DocSidebar from '@theme-original/DocSidebar';
-import type DocSidebarType from '@theme/DocSidebar';
-import type {WrapperProps} from '@docusaurus/types';
-
-type Props = WrapperProps<typeof DocSidebarType>;
-
-export default function DocSidebarWrapper(props: Props): ReactNode {
-  let newProps;
-
-  // For `/docs/platforms` and `/docs/data` sidebars, remove the parent category from the sidebar.
-  if (
-    props.path.startsWith('/docs/platforms') ||
-    props.path.startsWith('/docs/data')
-  ) {
-    newProps = {
-      ...props,
-    };
-    if (props.sidebar[0].type === 'category') {
-      newProps.sidebar = props.sidebar[0].items;
-    }
-  } else {
-    // For all other sidebars, pass the default props.
-    newProps = props;
-  }
-
-  return (
-    <>
-      <DocSidebar {...newProps} />
-    </>
-  );
-}
diff --git a/src/theme/MDXComponents.ts b/src/theme/MDXComponents.ts
deleted file mode 100644
index 767b9bbb4..000000000
--- a/src/theme/MDXComponents.ts
+++ /dev/null
@@ -1,15 +0,0 @@
-import React from "react";
-import MDXComponents from "@theme-original/MDXComponents";
-
-import { AttributeTable } from '@site/src/components/AttributeTable';
-import { CodeExample } from '@site/src/components/CodeExample';
-import { EndpointsTable } from '@site/src/components/EndpointsTable';
-import { ExampleResponse } from '@site/src/components/ExampleResponse';
-
-export default {
-  ...MDXComponents,
-  AttributeTable,
-  CodeExample,
-  EndpointsTable,
-  ExampleResponse,
-};
diff --git a/src/theme/NotFound/Content/index.tsx b/src/theme/NotFound/Content/index.tsx
deleted file mode 100644
index 1e5f1b849..000000000
--- a/src/theme/NotFound/Content/index.tsx
+++ /dev/null
@@ -1,68 +0,0 @@
-import React, { useEffect, useRef, type ReactNode } from 'react';
-import clsx from 'clsx';
-import Translate from '@docusaurus/Translate';
-import { useHistory } from '@docusaurus/router';
-import type { Props } from '@theme/NotFound/Content';
-import Heading from '@theme/Heading';
-import SearchPage from '@theme/SearchPage';
-import { useSearchQueryString } from '@docusaurus/theme-common';
-
-import styles from './styles.module.scss';
-
-export default function NotFoundContent({className}: Props): ReactNode {
-  const [_, setSearchQuery] = useSearchQueryString()
-
-  const history = useHistory();
-
-  const {
-    current: { pathname, hash },
-  } = useRef({ ...history.location });
-
-  useEffect(() => {
-    const parsedPath = pathname
-      .split("/")
-      .filter((item) => item && item !== "docs" && item !== "es")
-      .map((item) => item.replace(/-/g, " "))
-      .join(" ");
-
-    const parsedHash = hash.substring(1).replace(/-/g, " ");
-
-    const search = [parsedPath, parsedHash].filter((item) => item).join(" ");
-    setSearchQuery(search);
-  }, [pathname, hash]);
-
-  return (
-    <main className={clsx('container margin-vert--xl', className)}>
-      <div className="row">
-        <div className="col col--6 col--offset-3">
-          <Heading as="h1" className="hero__title">
-            <Translate
-              id="theme.NotFound.title"
-              description="The title of the 404 page">
-              Page Not Found
-            </Translate>
-          </Heading>
-          <p>
-            <Translate
-              id="theme.NotFound.p1"
-              description="The first paragraph of the 404 page">
-              We could not find what you were looking for.
-            </Translate>
-          </p>
-          <p>
-            <Translate
-              id="theme.NotFound.p2"
-              description="The 2nd paragraph of the 404 page">
-              Please contact the owner of the site that linked you to the
-              original URL and let them know their link is broken.
-            </Translate>
-          </p>
-        </div>
-      </div>
-
-      <div className={styles.search}>
-        <SearchPage />
-      </div>
-    </main>
-  );
-}
diff --git a/src/theme/NotFound/Content/styles.module.scss b/src/theme/NotFound/Content/styles.module.scss
deleted file mode 100644
index 149e8d32e..000000000
--- a/src/theme/NotFound/Content/styles.module.scss
+++ /dev/null
@@ -1,14 +0,0 @@
-.search {
-  nav {
-    display: none;
-  }
-
-  footer {
-    display: none;
-  }
-
-  :global .container {
-    margin: 5rem 0 !important;
-    padding: 0;
-  }
-}
diff --git a/src/theme/NotFound/index.tsx b/src/theme/NotFound/index.tsx
deleted file mode 100644
index b27bffb18..000000000
--- a/src/theme/NotFound/index.tsx
+++ /dev/null
@@ -1,20 +0,0 @@
-import React, { type ReactNode } from 'react';
-import {translate} from '@docusaurus/Translate';
-import {PageMetadata} from '@docusaurus/theme-common';
-import Layout from '@theme/Layout';
-import NotFoundContent from '@theme/NotFound/Content';
-
-export default function Index(): ReactNode {
-  const title = translate({
-    id: 'theme.NotFound.title',
-    message: 'Page Not Found',
-  });
-  return (
-    <>
-      <PageMetadata title={title} />
-      <Layout>
-        <NotFoundContent />
-      </Layout>
-    </>
-  );
-}
diff --git a/src/theme/Root.tsx b/src/theme/Root.tsx
deleted file mode 100644
index 4109b1ec3..000000000
--- a/src/theme/Root.tsx
+++ /dev/null
@@ -1,28 +0,0 @@
-import React, { type ReactNode } from 'react';
-import Root from '@theme-original/Root';
-
-import ForAgentsPanel from '@site/src/components/ForAgentsPanel';
-
-interface Props {
-  children: ReactNode;
-}
-
-/**
- * `Root` wraps the whole app above the router, so anything rendered here
- * survives client-side navigation. That is what the "For agents" panel needs:
- * one instance for the entire site rather than one per page (#2586).
- *
- * This must WRAP `@theme-original/Root`, not replace it:
- * `docusaurus-markdown-source-plugin` ships its own Root, which injects the
- * "Open Markdown" dropdown and the hash-scroll behavior on docs pages. A
- * user-land Root shadows it outright, which is exactly the regression that
- * removed the button site-wide (#2712).
- */
-export default function RootWrapper({ children }: Props): ReactNode {
-  return (
-    <Root>
-      {children}
-      <ForAgentsPanel />
-    </Root>
-  );
-}
diff --git a/static/.nojekyll b/static/.nojekyll
deleted file mode 100644
index e69de29bb..000000000
diff --git a/static/.well-known/agent-skills/index.json b/static/.well-known/agent-skills/index.json
deleted file mode 100644
index 0f036e078..000000000
--- a/static/.well-known/agent-skills/index.json
+++ /dev/null
@@ -1,54 +0,0 @@
-{
-  "$schema": "https://schemas.agentskills.io/discovery/0.2.0/schema.json",
-  "skills": [
-    {
-      "name": "agentic-payments",
-      "type": "skill-md",
-      "description": "Agentic and machine-to-machine payments on Stellar. Covers x402 (HTTP 402 paid APIs via OZ Channels facilitator, fee-sponsored clients) and MPP (Machine Payments Protocol) in both Charge mode (per-request SAC) and Channel mode (off-chain commits, high-frequency). Defaults to USDC (SEP-41 SAC) on `stellar:testnet`/`stellar:pubnet` (CAIP-2). Use when selling a paid API to AI agents, building an x402 client, or designing a payment-channel architecture for high-frequency agent traffic.",
-      "url": "https://raw.githubusercontent.com/stellar/stellar-dev-skill/v1.2.0/skills/agentic-payments/SKILL.md",
-      "digest": "sha256:b5e2d4def2242b684e3bb75a0945808fd4dbf7beb47a34afb8f17b553ee9accd"
-    },
-    {
-      "name": "assets",
-      "type": "skill-md",
-      "description": "Stellar Assets (classic) + trustlines + Stellar Asset Contract (SAC) bridge to smart contracts. Covers asset issuance, distribution, authorization flags, clawback, regulated assets, trustline management, and the SAC interop layer that exposes classic assets as SEP-41 contract tokens. Use when tokenizing real-world assets, issuing stablecoins, managing trustlines, or bridging classic assets to smart contracts.",
-      "url": "https://raw.githubusercontent.com/stellar/stellar-dev-skill/v1.2.0/skills/assets/SKILL.md",
-      "digest": "sha256:8ea19310a053edc0c2856f41908d7923f004538d31c211d287827c3beeb0c8e4"
-    },
-    {
-      "name": "dapp",
-      "type": "skill-md",
-      "description": "Stellar dApp / frontend development. Covers the JavaScript stellar-sdk (browser + Node.js), Freighter wallet, Stellar Wallets Kit (multi-wallet), Wallet Standard, smart accounts with passkeys, transaction building / signing / submission, smart contract invocation from the client, simulation, and error handling. Use when building a React/Next.js/Node.js app that talks to Stellar — classic operations or smart contracts.",
-      "url": "https://raw.githubusercontent.com/stellar/stellar-dev-skill/v1.2.0/skills/dapp/SKILL.md",
-      "digest": "sha256:1c5c5452595216c6f90bf796f1ed86854900e328931bfc930bc1f85367531c04"
-    },
-    {
-      "name": "data",
-      "type": "skill-md",
-      "description": "Querying Stellar chain data via Stellar RPC (preferred) and Horizon (legacy). Covers RPC JSON-RPC methods, Horizon REST endpoints, streaming, pagination, historical queries, Hubble/Galexie for deep history, and the RPC/Horizon migration story. Use when reading balances, transactions, operations, ledgers, contract events, or building any indexer/analytics workflow.",
-      "url": "https://raw.githubusercontent.com/stellar/stellar-dev-skill/v1.2.0/skills/data/SKILL.md",
-      "digest": "sha256:6c2b2da5cd9d3e1cf527b0278f50d4488359bb2ceea823e934c89f14adeef641"
-    },
-    {
-      "name": "smart-contracts",
-      "type": "archive",
-      "description": "Stellar smart contract development (Rust, soroban-sdk). Entry point with project setup, contract anatomy, and build/deploy workflow, routing to three companion files in this directory — development.md (storage, auth, cross-contract calls, events, errors, upgrades, factories, troubleshooting), testing.md (unit, fuzz, property, fork, mutation, integration), and security.md (vulnerability classes, checklists, tooling, audits). Use when writing, testing, securing, or shipping Stellar smart contracts (formerly branded Soroban).",
-      "url": "https://github.com/stellar/stellar-dev-skill/releases/download/v1.2.0/smart-contracts.tar.gz",
-      "digest": "sha256:d3f997c11e09043be025f2768918cc0d989e463e5fb652798ed1050ffc804b06"
-    },
-    {
-      "name": "standards",
-      "type": "skill-md",
-      "description": "Stellar standards, ecosystem, and reference. Covers SEPs (Stellar Ecosystem Proposals), CAPs (Core Advancement Proposals), and a quick map for picking the right standard for wallets, anchors, payments, deposits/withdrawals, federation, deep links, and KYC. Also bundles ecosystem references (DeFi protocols, dev tools, wallets, infra, community projects) and curated documentation links. Use when you need to know which SEP applies, or want a starting point for ecosystem integrations and official docs.",
-      "url": "https://raw.githubusercontent.com/stellar/stellar-dev-skill/v1.2.0/skills/standards/SKILL.md",
-      "digest": "sha256:7a3dbb58ade371a9b7114ac6aedb2b8ceec00a2032ea3e4382f53016d38a28e1"
-    },
-    {
-      "name": "zk-proofs",
-      "type": "skill-md",
-      "description": "Zero-knowledge proofs and privacy patterns on Stellar. Covers Groth16 verification in smart contracts via BLS12-381 host functions (CAP-0059, available), the BN254 + Poseidon proposals (CAP-0074/0075, status-sensitive), and concrete toolchain walkthroughs for Circom (on-chain verifiable today), Noir, and RISC Zero (attestation pattern until BN254 lands). Use when building privacy-preserving applications, ZK-verifier contracts, or wiring a proving toolchain to Stellar.",
-      "url": "https://raw.githubusercontent.com/stellar/stellar-dev-skill/v1.2.0/skills/zk-proofs/SKILL.md",
-      "digest": "sha256:44e992a294103cf0c0dafe35861c5b8bbc6bc0b99e5b41ee0bf560d40d601e20"
-    }
-  ]
-}
diff --git a/static/.well-known/api-catalog b/static/.well-known/api-catalog
deleted file mode 100644
index 819910286..000000000
--- a/static/.well-known/api-catalog
+++ /dev/null
@@ -1,46 +0,0 @@
-{
-  "linkset": [
-    {
-      "anchor": "https://developers.stellar.org/docs/data/apis/rpc",
-      "service-desc": [
-        {
-          "href": "https://developers.stellar.org/stellar-rpc.openrpc.json",
-          "type": "application/json"
-        }
-      ],
-      "service-doc": [
-        {
-          "href": "https://developers.stellar.org/docs/data/apis/rpc/api-reference",
-          "type": "text/html"
-        }
-      ]
-    },
-    {
-      "anchor": "https://developers.stellar.org/docs/data/apis/horizon",
-      "service-doc": [
-        {
-          "href": "https://developers.stellar.org/docs/data/apis/horizon/api-reference",
-          "type": "text/html"
-        }
-      ]
-    },
-    {
-      "anchor": "https://developers.stellar.org/docs/platforms/anchor-platform",
-      "service-doc": [
-        {
-          "href": "https://developers.stellar.org/docs/platforms/anchor-platform/api-reference",
-          "type": "text/html"
-        }
-      ]
-    },
-    {
-      "anchor": "https://developers.stellar.org/docs/platforms/stellar-disbursement-platform",
-      "service-doc": [
-        {
-          "href": "https://developers.stellar.org/docs/platforms/stellar-disbursement-platform/api-reference",
-          "type": "text/html"
-        }
-      ]
-    }
-  ]
-}
diff --git a/static/assets/SDP/SDP10.png b/static/assets/SDP/SDP10.png
deleted file mode 100644
index f2a0432ee..000000000
Binary files a/static/assets/SDP/SDP10.png and /dev/null differ
diff --git a/static/assets/SDP/SDP11.png b/static/assets/SDP/SDP11.png
deleted file mode 100644
index a3f584bad..000000000
Binary files a/static/assets/SDP/SDP11.png and /dev/null differ
diff --git a/static/assets/SDP/SDP12.png b/static/assets/SDP/SDP12.png
deleted file mode 100644
index 0911d02c8..000000000
Binary files a/static/assets/SDP/SDP12.png and /dev/null differ
diff --git a/static/assets/SDP/SDP13.png b/static/assets/SDP/SDP13.png
deleted file mode 100644
index 515a4df0d..000000000
Binary files a/static/assets/SDP/SDP13.png and /dev/null differ
diff --git a/static/assets/SDP/SDP14.1.png b/static/assets/SDP/SDP14.1.png
deleted file mode 100644
index 8272aa362..000000000
Binary files a/static/assets/SDP/SDP14.1.png and /dev/null differ
diff --git a/static/assets/SDP/SDP14.2.png b/static/assets/SDP/SDP14.2.png
deleted file mode 100644
index 657ebf8cf..000000000
Binary files a/static/assets/SDP/SDP14.2.png and /dev/null differ
diff --git a/static/assets/SDP/SDP15.png b/static/assets/SDP/SDP15.png
deleted file mode 100644
index afa02e169..000000000
Binary files a/static/assets/SDP/SDP15.png and /dev/null differ
diff --git a/static/assets/SDP/SDP16.png b/static/assets/SDP/SDP16.png
deleted file mode 100644
index 2dfae4dac..000000000
Binary files a/static/assets/SDP/SDP16.png and /dev/null differ
diff --git a/static/assets/SDP/SDP17.png b/static/assets/SDP/SDP17.png
deleted file mode 100644
index 131477156..000000000
Binary files a/static/assets/SDP/SDP17.png and /dev/null differ
diff --git a/static/assets/SDP/SDP18.png b/static/assets/SDP/SDP18.png
deleted file mode 100644
index 6fc5b09fc..000000000
Binary files a/static/assets/SDP/SDP18.png and /dev/null differ
diff --git a/static/assets/SDP/SDP2.png b/static/assets/SDP/SDP2.png
deleted file mode 100644
index 2fc1fa20c..000000000
Binary files a/static/assets/SDP/SDP2.png and /dev/null differ
diff --git a/static/assets/SDP/SDP21.png b/static/assets/SDP/SDP21.png
deleted file mode 100644
index ffef5f885..000000000
Binary files a/static/assets/SDP/SDP21.png and /dev/null differ
diff --git a/static/assets/SDP/SDP26.png b/static/assets/SDP/SDP26.png
deleted file mode 100644
index ba88e766b..000000000
Binary files a/static/assets/SDP/SDP26.png and /dev/null differ
diff --git a/static/assets/SDP/SDP27.png b/static/assets/SDP/SDP27.png
deleted file mode 100644
index 86e764c16..000000000
Binary files a/static/assets/SDP/SDP27.png and /dev/null differ
diff --git a/static/assets/SDP/SDP28.png b/static/assets/SDP/SDP28.png
deleted file mode 100644
index 75bec53b9..000000000
Binary files a/static/assets/SDP/SDP28.png and /dev/null differ
diff --git a/static/assets/SDP/SDP29.png b/static/assets/SDP/SDP29.png
deleted file mode 100644
index 6e4eee8b8..000000000
Binary files a/static/assets/SDP/SDP29.png and /dev/null differ
diff --git a/static/assets/SDP/SDP3.png b/static/assets/SDP/SDP3.png
deleted file mode 100644
index 2542ba922..000000000
Binary files a/static/assets/SDP/SDP3.png and /dev/null differ
diff --git a/static/assets/SDP/SDP4.png b/static/assets/SDP/SDP4.png
deleted file mode 100644
index 726210208..000000000
Binary files a/static/assets/SDP/SDP4.png and /dev/null differ
diff --git a/static/assets/SDP/SDP5.png b/static/assets/SDP/SDP5.png
deleted file mode 100644
index 6afdacc0e..000000000
Binary files a/static/assets/SDP/SDP5.png and /dev/null differ
diff --git a/static/assets/SDP/SDP6.png b/static/assets/SDP/SDP6.png
deleted file mode 100644
index 59fe8f0f6..000000000
Binary files a/static/assets/SDP/SDP6.png and /dev/null differ
diff --git a/static/assets/SDP/SDP7.png b/static/assets/SDP/SDP7.png
deleted file mode 100644
index 3ac166213..000000000
Binary files a/static/assets/SDP/SDP7.png and /dev/null differ
diff --git a/static/assets/SDP/SDP8.png b/static/assets/SDP/SDP8.png
deleted file mode 100644
index 81d5a57b4..000000000
Binary files a/static/assets/SDP/SDP8.png and /dev/null differ
diff --git a/static/assets/SDP/SDP9.png b/static/assets/SDP/SDP9.png
deleted file mode 100644
index aa0a18590..000000000
Binary files a/static/assets/SDP/SDP9.png and /dev/null differ
diff --git a/static/assets/ap/SEP24-state-diagram.png b/static/assets/ap/SEP24-state-diagram.png
deleted file mode 100644
index 65d2bb536..000000000
Binary files a/static/assets/ap/SEP24-state-diagram.png and /dev/null differ
diff --git a/static/assets/ap/sequence_diagram_sep24_deposit_job.png b/static/assets/ap/sequence_diagram_sep24_deposit_job.png
deleted file mode 100644
index 30b8059f8..000000000
Binary files a/static/assets/ap/sequence_diagram_sep24_deposit_job.png and /dev/null differ
diff --git a/static/assets/ap/sequence_diagram_sep24_deposit_webhook.png b/static/assets/ap/sequence_diagram_sep24_deposit_webhook.png
deleted file mode 100644
index 630d9173d..000000000
Binary files a/static/assets/ap/sequence_diagram_sep24_deposit_webhook.png and /dev/null differ
diff --git a/static/assets/ap/sequence_diagram_sep24_withdrawal_job.png b/static/assets/ap/sequence_diagram_sep24_withdrawal_job.png
deleted file mode 100644
index a768c5218..000000000
Binary files a/static/assets/ap/sequence_diagram_sep24_withdrawal_job.png and /dev/null differ
diff --git a/static/assets/ap/sequence_diagram_sep24_withdrawal_webhook.png b/static/assets/ap/sequence_diagram_sep24_withdrawal_webhook.png
deleted file mode 100644
index 4005a81d2..000000000
Binary files a/static/assets/ap/sequence_diagram_sep24_withdrawal_webhook.png and /dev/null differ
diff --git a/static/assets/ap/sequence_diagram_sep31_receive_job.png b/static/assets/ap/sequence_diagram_sep31_receive_job.png
deleted file mode 100644
index 3150663fe..000000000
Binary files a/static/assets/ap/sequence_diagram_sep31_receive_job.png and /dev/null differ
diff --git a/static/assets/ap/sequence_diagram_sep31_receive_webhook.png b/static/assets/ap/sequence_diagram_sep31_receive_webhook.png
deleted file mode 100644
index 7a66bbdcc..000000000
Binary files a/static/assets/ap/sequence_diagram_sep31_receive_webhook.png and /dev/null differ
diff --git a/static/assets/dev-tools/openzeppelin-contract-wizard.png b/static/assets/dev-tools/openzeppelin-contract-wizard.png
deleted file mode 100644
index aa513f480..000000000
Binary files a/static/assets/dev-tools/openzeppelin-contract-wizard.png and /dev/null differ
diff --git a/static/assets/diagrams/stellar-stack-diagram.png b/static/assets/diagrams/stellar-stack-diagram.png
deleted file mode 100644
index 23e28661a..000000000
Binary files a/static/assets/diagrams/stellar-stack-diagram.png and /dev/null differ
diff --git a/static/assets/lab/lab-tx-dashboard-profiler-01232026.png b/static/assets/lab/lab-tx-dashboard-profiler-01232026.png
deleted file mode 100644
index d1df375a5..000000000
Binary files a/static/assets/lab/lab-tx-dashboard-profiler-01232026.png and /dev/null differ
diff --git a/static/assets/lab/lab-tx-dashboard-state-change.png b/static/assets/lab/lab-tx-dashboard-state-change.png
deleted file mode 100644
index 31d1600e2..000000000
Binary files a/static/assets/lab/lab-tx-dashboard-state-change.png and /dev/null differ
diff --git a/static/assets/launch/fonts/LICENSE-IBM-Plex.txt b/static/assets/launch/fonts/LICENSE-IBM-Plex.txt
deleted file mode 100644
index c35c4c618..000000000
--- a/static/assets/launch/fonts/LICENSE-IBM-Plex.txt
+++ /dev/null
@@ -1,93 +0,0 @@
-Copyright © 2017 IBM Corp. with Reserved Font Name "Plex"
-
-This Font Software is licensed under the SIL Open Font License, Version 1.1.
-
-This license is copied below, and is also available with a FAQ at: http://scripts.sil.org/OFL
-
-
------------------------------------------------------------
-SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
------------------------------------------------------------
-
-PREAMBLE
-The goals of the Open Font License (OFL) are to stimulate worldwide
-development of collaborative font projects, to support the font creation
-efforts of academic and linguistic communities, and to provide a free and
-open framework in which fonts may be shared and improved in partnership
-with others.
-
-The OFL allows the licensed fonts to be used, studied, modified and
-redistributed freely as long as they are not sold by themselves. The
-fonts, including any derivative works, can be bundled, embedded, 
-redistributed and/or sold with any software provided that any reserved
-names are not used by derivative works. The fonts and derivatives,
-however, cannot be released under any other type of license. The
-requirement for fonts to remain under this license does not apply
-to any document created using the fonts or their derivatives.
-
-DEFINITIONS
-"Font Software" refers to the set of files released by the Copyright
-Holder(s) under this license and clearly marked as such. This may
-include source files, build scripts and documentation.
-
-"Reserved Font Name" refers to any names specified as such after the
-copyright statement(s).
-
-"Original Version" refers to the collection of Font Software components as
-distributed by the Copyright Holder(s).
-
-"Modified Version" refers to any derivative made by adding to, deleting,
-or substituting -- in part or in whole -- any of the components of the
-Original Version, by changing formats or by porting the Font Software to a
-new environment.
-
-"Author" refers to any designer, engineer, programmer, technical
-writer or other person who contributed to the Font Software.
-
-PERMISSION & CONDITIONS
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of the Font Software, to use, study, copy, merge, embed, modify,
-redistribute, and sell modified and unmodified copies of the Font
-Software, subject to the following conditions:
-
-1) Neither the Font Software nor any of its individual components,
-in Original or Modified Versions, may be sold by itself.
-
-2) Original or Modified Versions of the Font Software may be bundled,
-redistributed and/or sold with any software, provided that each copy
-contains the above copyright notice and this license. These can be
-included either as stand-alone text files, human-readable headers or
-in the appropriate machine-readable metadata fields within text or
-binary files as long as those fields can be easily viewed by the user.
-
-3) No Modified Version of the Font Software may use the Reserved Font
-Name(s) unless explicit written permission is granted by the corresponding
-Copyright Holder. This restriction only applies to the primary font name as
-presented to the users.
-
-4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
-Software shall not be used to promote, endorse or advertise any
-Modified Version, except to acknowledge the contribution(s) of the
-Copyright Holder(s) and the Author(s) or with their explicit written
-permission.
-
-5) The Font Software, modified or unmodified, in part or in whole,
-must be distributed entirely under this license, and must not be
-distributed under any other license. The requirement for fonts to
-remain under this license does not apply to any document created
-using the Font Software.
-
-TERMINATION
-This license becomes null and void if any of the above conditions are
-not met.
-
-DISCLAIMER
-THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
-OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
-COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
-INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
-DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
-FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
-OTHER DEALINGS IN THE FONT SOFTWARE.
diff --git a/static/assets/launch/fonts/LICENSE-Inter.txt b/static/assets/launch/fonts/LICENSE-Inter.txt
deleted file mode 100644
index 9b2ca37b3..000000000
--- a/static/assets/launch/fonts/LICENSE-Inter.txt
+++ /dev/null
@@ -1,92 +0,0 @@
-Copyright (c) 2016 The Inter Project Authors (https://github.com/rsms/inter)
-
-This Font Software is licensed under the SIL Open Font License, Version 1.1.
-This license is copied below, and is also available with a FAQ at:
-http://scripts.sil.org/OFL
-
------------------------------------------------------------
-SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
------------------------------------------------------------
-
-PREAMBLE
-The goals of the Open Font License (OFL) are to stimulate worldwide
-development of collaborative font projects, to support the font creation
-efforts of academic and linguistic communities, and to provide a free and
-open framework in which fonts may be shared and improved in partnership
-with others.
-
-The OFL allows the licensed fonts to be used, studied, modified and
-redistributed freely as long as they are not sold by themselves. The
-fonts, including any derivative works, can be bundled, embedded,
-redistributed and/or sold with any software provided that any reserved
-names are not used by derivative works. The fonts and derivatives,
-however, cannot be released under any other type of license. The
-requirement for fonts to remain under this license does not apply
-to any document created using the fonts or their derivatives.
-
-DEFINITIONS
-"Font Software" refers to the set of files released by the Copyright
-Holder(s) under this license and clearly marked as such. This may
-include source files, build scripts and documentation.
-
-"Reserved Font Name" refers to any names specified as such after the
-copyright statement(s).
-
-"Original Version" refers to the collection of Font Software components as
-distributed by the Copyright Holder(s).
-
-"Modified Version" refers to any derivative made by adding to, deleting,
-or substituting -- in part or in whole -- any of the components of the
-Original Version, by changing formats or by porting the Font Software to a
-new environment.
-
-"Author" refers to any designer, engineer, programmer, technical
-writer or other person who contributed to the Font Software.
-
-PERMISSION AND CONDITIONS
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of the Font Software, to use, study, copy, merge, embed, modify,
-redistribute, and sell modified and unmodified copies of the Font
-Software, subject to the following conditions:
-
-1) Neither the Font Software nor any of its individual components,
-in Original or Modified Versions, may be sold by itself.
-
-2) Original or Modified Versions of the Font Software may be bundled,
-redistributed and/or sold with any software, provided that each copy
-contains the above copyright notice and this license. These can be
-included either as stand-alone text files, human-readable headers or
-in the appropriate machine-readable metadata fields within text or
-binary files as long as those fields can be easily viewed by the user.
-
-3) No Modified Version of the Font Software may use the Reserved Font
-Name(s) unless explicit written permission is granted by the corresponding
-Copyright Holder. This restriction only applies to the primary font name as
-presented to the users.
-
-4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
-Software shall not be used to promote, endorse or advertise any
-Modified Version, except to acknowledge the contribution(s) of the
-Copyright Holder(s) and the Author(s) or with their explicit written
-permission.
-
-5) The Font Software, modified or unmodified, in part or in whole,
-must be distributed entirely under this license, and must not be
-distributed under any other license. The requirement for fonts to
-remain under this license does not apply to any document created
-using the Font Software.
-
-TERMINATION
-This license becomes null and void if any of the above conditions are
-not met.
-
-DISCLAIMER
-THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
-OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
-COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
-INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
-DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
-FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
-OTHER DEALINGS IN THE FONT SOFTWARE.
diff --git a/static/assets/launch/fonts/ibm-plex-mono-400-latin-ext.woff2 b/static/assets/launch/fonts/ibm-plex-mono-400-latin-ext.woff2
deleted file mode 100644
index e4f67deb6..000000000
Binary files a/static/assets/launch/fonts/ibm-plex-mono-400-latin-ext.woff2 and /dev/null differ
diff --git a/static/assets/launch/fonts/ibm-plex-mono-400-latin.woff2 b/static/assets/launch/fonts/ibm-plex-mono-400-latin.woff2
deleted file mode 100644
index 52b6c7595..000000000
Binary files a/static/assets/launch/fonts/ibm-plex-mono-400-latin.woff2 and /dev/null differ
diff --git a/static/assets/launch/fonts/ibm-plex-mono-500-latin-ext.woff2 b/static/assets/launch/fonts/ibm-plex-mono-500-latin-ext.woff2
deleted file mode 100644
index 743dae391..000000000
Binary files a/static/assets/launch/fonts/ibm-plex-mono-500-latin-ext.woff2 and /dev/null differ
diff --git a/static/assets/launch/fonts/ibm-plex-mono-500-latin.woff2 b/static/assets/launch/fonts/ibm-plex-mono-500-latin.woff2
deleted file mode 100644
index 3308bce24..000000000
Binary files a/static/assets/launch/fonts/ibm-plex-mono-500-latin.woff2 and /dev/null differ
diff --git a/static/assets/launch/fonts/inter-latin-ext.woff2 b/static/assets/launch/fonts/inter-latin-ext.woff2
deleted file mode 100644
index 57da6f8d4..000000000
Binary files a/static/assets/launch/fonts/inter-latin-ext.woff2 and /dev/null differ
diff --git a/static/assets/launch/fonts/inter-latin.woff2 b/static/assets/launch/fonts/inter-latin.woff2
deleted file mode 100644
index 91dc3e852..000000000
Binary files a/static/assets/launch/fonts/inter-latin.woff2 and /dev/null differ
diff --git a/static/assets/launch/usdt0-og.png b/static/assets/launch/usdt0-og.png
deleted file mode 100644
index c2e5b02e4..000000000
Binary files a/static/assets/launch/usdt0-og.png and /dev/null differ
diff --git a/static/assets/mgi/wallet-mgi-architecture-1.png b/static/assets/mgi/wallet-mgi-architecture-1.png
deleted file mode 100644
index c8d1592fd..000000000
Binary files a/static/assets/mgi/wallet-mgi-architecture-1.png and /dev/null differ
diff --git a/static/assets/mgi/wallet-mgi-architecture-2.png b/static/assets/mgi/wallet-mgi-architecture-2.png
deleted file mode 100644
index 451207b75..000000000
Binary files a/static/assets/mgi/wallet-mgi-architecture-2.png and /dev/null differ
diff --git a/static/definitions/sep6_24_31_status_transition_diagrams.drawio b/static/definitions/sep6_24_31_status_transition_diagrams.drawio
deleted file mode 100644
index 9709c2e64..000000000
--- a/static/definitions/sep6_24_31_status_transition_diagrams.drawio
+++ /dev/null
@@ -1,1517 +0,0 @@
-<mxfile host="app.diagrams.net" agent="Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36" version="28.2.5" pages="5">
-  <diagram name="Sep24 - deposit v.0.4" id="LMAKezt2CjZ62RWBca-x">
-    <mxGraphModel dx="2402" dy="817" grid="1" gridSize="10" guides="1" tooltips="1" connect="1" arrows="1" fold="1" page="1" pageScale="1" pageWidth="850" pageHeight="1100" background="#ffffff" math="0" shadow="0">
-      <root>
-        <mxCell id="0" />
-        <mxCell id="1" parent="0" />
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-1" value="" style="rounded=0;whiteSpace=wrap;html=1;strokeWidth=0;glass=0;strokeColor=#c521c8;fontColor=#c521c8;" parent="1" vertex="1">
-          <mxGeometry x="-190" y="230" width="1180" height="793" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-2" value="" style="group" parent="1" vertex="1" connectable="0">
-          <mxGeometry x="430" y="313" width="508" height="163" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-3" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=#82b366;" parent="6D9sstSB_-0e3DwsuZUU-2" vertex="1">
-          <mxGeometry x="240" y="5" width="50" height="20" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-4" value="shortest e2e status flow" style="text;strokeColor=none;align=center;fillColor=none;html=1;verticalAlign=middle;whiteSpace=wrap;rounded=0;" parent="6D9sstSB_-0e3DwsuZUU-2" vertex="1">
-          <mxGeometry x="290" width="140" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-5" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=#d6b656;" parent="6D9sstSB_-0e3DwsuZUU-2" vertex="1">
-          <mxGeometry x="240" y="30" width="50" height="20" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-6" value="optional status, available for business" style="text;strokeColor=none;align=center;fillColor=none;html=1;verticalAlign=middle;whiteSpace=wrap;rounded=0;" parent="6D9sstSB_-0e3DwsuZUU-2" vertex="1">
-          <mxGeometry x="288" y="25" width="220" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-7" value="(&lt;font style=&quot;border-color: var(--border-color); text-align: left;&quot; color=&quot;#66b2ff&quot;&gt;function&lt;/font&gt;&lt;span style=&quot;text-align: left;&quot;&gt;)&lt;/span&gt;" style="rounded=1;whiteSpace=wrap;html=1;fillColor=none;strokeColor=none;" parent="6D9sstSB_-0e3DwsuZUU-2" vertex="1">
-          <mxGeometry x="240" y="55" width="54" height="20" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-8" value="&lt;font style=&quot;border-color: var(--border-color); text-align: left;&quot;&gt;a side effect that will be triggered by an action&lt;br style=&quot;border-color: var(--border-color);&quot;&gt;&lt;/font&gt;if its Anchor is in custody mode" style="text;strokeColor=none;align=left;fillColor=none;html=1;verticalAlign=middle;whiteSpace=wrap;rounded=0;labelPosition=right;verticalLabelPosition=middle;" parent="6D9sstSB_-0e3DwsuZUU-2" vertex="1">
-          <mxGeometry y="55" width="300" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-9" value="" style="endArrow=open;html=1;rounded=0;endFill=0;strokeColor=#9b1599;strokeWidth=2;" parent="6D9sstSB_-0e3DwsuZUU-2" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="240" y="95" as="sourcePoint" />
-            <mxPoint x="290" y="95" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-10" value="&lt;font style=&quot;border-color: var(--border-color);&quot;&gt;actions available for a business that&lt;br style=&quot;border-color: var(--border-color);&quot;&gt;&lt;/font&gt;doesn&#39;t use custody. Can be used to reflect &lt;br&gt;trustline&amp;nbsp;&lt;span style=&quot;&quot;&gt;state on a destination account&lt;/span&gt;" style="text;strokeColor=none;align=left;fillColor=none;html=1;verticalAlign=middle;whiteSpace=wrap;rounded=0;labelPosition=right;verticalLabelPosition=middle;" parent="6D9sstSB_-0e3DwsuZUU-2" vertex="1">
-          <mxGeometry y="95" width="300" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-11" value="" style="endArrow=open;html=1;rounded=0;endFill=0;strokeColor=#BD7000;strokeWidth=2;fillColor=#f0a30a;" parent="6D9sstSB_-0e3DwsuZUU-2" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="240" y="144" as="sourcePoint" />
-            <mxPoint x="290" y="144" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-12" value="&lt;font style=&quot;border-color: var(--border-color); text-align: left;&quot;&gt;actions&amp;nbsp;available for a business that&lt;br style=&quot;border-color: var(--border-color);&quot;&gt;&lt;/font&gt;uses custody service" style="text;strokeColor=none;align=left;fillColor=none;html=1;verticalAlign=middle;whiteSpace=wrap;rounded=0;labelPosition=right;verticalLabelPosition=middle;" parent="6D9sstSB_-0e3DwsuZUU-2" vertex="1">
-          <mxGeometry y="134" width="300" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-13" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.5;exitDx=0;exitDy=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;endArrow=open;endFill=0;jumpStyle=none;strokeWidth=2;" parent="1" source="6D9sstSB_-0e3DwsuZUU-15" target="6D9sstSB_-0e3DwsuZUU-35" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="341" y="348" as="sourcePoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-14" value="notify_interactive_flow_completed" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="6D9sstSB_-0e3DwsuZUU-13" vertex="1" connectable="0">
-          <mxGeometry x="0.6017" relative="1" as="geometry">
-            <mxPoint y="13" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-15" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;align=left;verticalAlign=top;" parent="1" vertex="1">
-          <mxGeometry x="126" y="313" width="180" height="70" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-16" style="edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.5;exitY=1;exitDx=0;exitDy=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="210" y="573" as="sourcePoint" />
-            <mxPoint x="210" y="695" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-17" value="notify_offchain_funds_received" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="6D9sstSB_-0e3DwsuZUU-16" vertex="1" connectable="0">
-          <mxGeometry x="-0.0219" y="-3" relative="1" as="geometry">
-            <mxPoint x="3" y="-6" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-18" value="(Create custody transaction*)" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];fontColor=#67bbfd;" parent="6D9sstSB_-0e3DwsuZUU-16" vertex="1" connectable="0">
-          <mxGeometry x="0.4595" y="1" relative="1" as="geometry">
-            <mxPoint x="9" y="-22" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-19" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.5;exitDx=0;exitDy=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="6D9sstSB_-0e3DwsuZUU-21" target="6D9sstSB_-0e3DwsuZUU-37" edge="1">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-20" value="&lt;font style=&quot;font-size: 11px;&quot;&gt;notify_offchain_funds_sent&lt;/font&gt;" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="6D9sstSB_-0e3DwsuZUU-19" vertex="1" connectable="0">
-          <mxGeometry x="0.7925" relative="1" as="geometry">
-            <mxPoint as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-21" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="126" y="503" width="180" height="70" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-22" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.007;exitY=0.413;exitDx=0;exitDy=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;strokeWidth=2;endArrow=open;endFill=0;exitPerimeter=0;" parent="1" source="6D9sstSB_-0e3DwsuZUU-31" target="6D9sstSB_-0e3DwsuZUU-52" edge="1">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-23" value="notify_refund_pending" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="6D9sstSB_-0e3DwsuZUU-22" vertex="1" connectable="0">
-          <mxGeometry x="0.7751" y="1" relative="1" as="geometry">
-            <mxPoint x="-1" y="-4" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-24" style="rounded=0;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.139;exitY=0.971;exitDx=0;exitDy=0;exitPerimeter=0;strokeWidth=2;endArrow=open;endFill=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;" parent="1" target="6D9sstSB_-0e3DwsuZUU-65" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="141.99" y="891.02" as="targetPoint" />
-            <mxPoint x="143.01999999999998" y="762.97" as="sourcePoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-25" value="notify_refund_sent" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="6D9sstSB_-0e3DwsuZUU-24" vertex="1" connectable="0">
-          <mxGeometry x="0.2745" y="-2" relative="1" as="geometry">
-            <mxPoint y="10" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-26" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;entryX=0.577;entryY=0.025;entryDx=0;entryDy=0;entryPerimeter=0;fillColor=#f0a30a;strokeColor=#BD7000;strokeWidth=2;endArrow=open;endFill=0;" parent="1" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="307" y="712" as="sourcePoint" />
-            <mxPoint x="766.0100000000002" y="773.0049999999999" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-27" value="do_stellar_payment" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];fontColor=#e0400b;" parent="6D9sstSB_-0e3DwsuZUU-26" vertex="1" connectable="0">
-          <mxGeometry x="-0.389" y="-1" relative="1" as="geometry">
-            <mxPoint x="-80" y="-1" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-28" value="(Do custody payment)" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];fontColor=#67b4fc;" parent="6D9sstSB_-0e3DwsuZUU-26" vertex="1" connectable="0">
-          <mxGeometry x="0.8848" y="-1" relative="1" as="geometry">
-            <mxPoint y="-5" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-29" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.5;exitDx=0;exitDy=0;entryX=0.25;entryY=0;entryDx=0;entryDy=0;fillColor=#e1d5e7;strokeColor=#9c079c;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="6D9sstSB_-0e3DwsuZUU-31" target="6D9sstSB_-0e3DwsuZUU-59" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <Array as="points">
-              <mxPoint x="437" y="732" />
-            </Array>
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-30" value="request_trust" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];fontColor=#b60fcc;" parent="6D9sstSB_-0e3DwsuZUU-29" vertex="1" connectable="0">
-          <mxGeometry x="-0.1111" relative="1" as="geometry">
-            <mxPoint as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-31" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="126" y="695" width="180" height="70" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-32" value="" style="endArrow=open;html=1;rounded=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;strokeWidth=2;endFill=0;" parent="1" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="209.5" y="383" as="sourcePoint" />
-            <mxPoint x="209.5" y="503" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-33" value="request_offchain_funds" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="6D9sstSB_-0e3DwsuZUU-32" connectable="0" vertex="1">
-          <mxGeometry x="-0.495" relative="1" as="geometry">
-            <mxPoint x="7" y="53" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-34" style="edgeStyle=orthogonalEdgeStyle;orthogonalLoop=1;jettySize=auto;html=1;exitX=0;exitY=0.5;exitDx=0;exitDy=0;rounded=1;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="6D9sstSB_-0e3DwsuZUU-35" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="210" y="443" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-35" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="417" y="386" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-36" style="edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;exitX=-0.008;exitY=0.633;exitDx=0;exitDy=0;strokeWidth=2;endArrow=open;endFill=0;exitPerimeter=0;" parent="1" source="6D9sstSB_-0e3DwsuZUU-37" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="210" y="611" as="targetPoint" />
-            <mxPoint x="378" y="611" as="sourcePoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-37" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="418" y="573" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-38" value="SEP24 deposit flow" style="text;html=1;strokeColor=none;fillColor=none;align=center;verticalAlign=middle;whiteSpace=wrap;rounded=0;fontSize=17;fontStyle=1" parent="1" vertex="1">
-          <mxGeometry x="110" y="248" width="250" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-39" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.5;exitY=1;exitDx=0;exitDy=0;entryX=0;entryY=0.25;entryDx=0;entryDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="6D9sstSB_-0e3DwsuZUU-41" target="6D9sstSB_-0e3DwsuZUU-31" edge="1">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-40" value="notify _transaction_recovery" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="6D9sstSB_-0e3DwsuZUU-39" vertex="1" connectable="0">
-          <mxGeometry x="-0.0626" y="-1" relative="1" as="geometry">
-            <mxPoint x="-53" y="-30" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-41" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#f8cecc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="-120" y="594" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-42" value="&lt;font&gt;incomplete&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;verticalAlign=top;align=left;fillColor=#6d8764;fontFamily=Tahoma;strokeColor=none;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="130.5" y="319" width="75" height="26" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-43" value="&lt;font face=&quot;Tahoma&quot;&gt;pending_anchor&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#f0a30a;fontColor=#000000;" parent="1" vertex="1">
-          <mxGeometry x="422" y="391" width="90" height="28" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-44" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.5;exitY=1;exitDx=0;exitDy=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="-54" y="529" as="sourcePoint" />
-            <mxPoint x="-54" y="594" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-45" value="notify_transaction_error&lt;br style=&quot;border-color: var(--border-color);&quot;&gt;notify_transaction_expired" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="6D9sstSB_-0e3DwsuZUU-44" vertex="1" connectable="0">
-          <mxGeometry x="0.1385" y="-3" relative="1" as="geometry">
-            <mxPoint x="2" y="-10" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-46" value="&lt;font style=&quot;&quot; face=&quot;Tahoma&quot;&gt;Any status other than completed or refunded&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#f5f5f5;align=center;verticalAlign=top;fontColor=#333333;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="-124" y="466" width="138" height="63" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-47" value="&lt;font face=&quot;Tahoma&quot;&gt;pending_external&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#f0a30a;fontColor=#000000;" parent="1" vertex="1">
-          <mxGeometry x="424" y="579" width="106" height="34" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-48" value="pending_user_transfer_start" style="rounded=1;whiteSpace=wrap;html=1;verticalAlign=top;align=left;fillColor=#6d8764;fontFamily=Tahoma;strokeColor=none;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="130" y="507" width="157.5" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-49" value="&lt;font face=&quot;Tahoma&quot;&gt;error/expired&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#e51400;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="-112" y="600" width="80" height="25" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-50" value="pending_anchor" style="rounded=1;whiteSpace=wrap;html=1;verticalAlign=top;align=left;fillColor=#6d8764;fontFamily=Tahoma;strokeColor=none;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="130.5" y="700" width="100" height="24" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-51" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.75;exitDx=0;exitDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="141" y="818" as="targetPoint" />
-            <mxPoint x="11" y="818" as="sourcePoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-52" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="-120" y="773" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-53" value="&lt;font face=&quot;Tahoma&quot;&gt;pending_external&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#f0a30a;fontColor=#000000;" parent="1" vertex="1">
-          <mxGeometry x="-112" y="779" width="100" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-54" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0;exitY=0.5;exitDx=0;exitDy=0;strokeWidth=2;endArrow=open;endFill=0;entryX=0.867;entryY=1.014;entryDx=0;entryDy=0;entryPerimeter=0;strokeColor=#c521c8;" parent="1" target="6D9sstSB_-0e3DwsuZUU-31" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="410" y="808" as="sourcePoint" />
-            <mxPoint x="268.02" y="765.03" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-55" value="notify_trust_set" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];fontColor=#c521c8;" parent="6D9sstSB_-0e3DwsuZUU-54" vertex="1" connectable="0">
-          <mxGeometry x="-0.1472" y="2" relative="1" as="geometry">
-            <mxPoint y="-3" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-56" style="edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.5;exitDx=0;exitDy=0;entryX=0;entryY=0.5;entryDx=0;entryDy=0;fillColor=#f0a30a;strokeColor=#BD7000;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="6D9sstSB_-0e3DwsuZUU-59" target="6D9sstSB_-0e3DwsuZUU-63" edge="1">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-57" value="notify_trust_set" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="6D9sstSB_-0e3DwsuZUU-56" vertex="1" connectable="0">
-          <mxGeometry x="-0.0988" relative="1" as="geometry">
-            <mxPoint as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-58" value="(Do custody payment)" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];fontColor=#84c7ff;" parent="6D9sstSB_-0e3DwsuZUU-56" vertex="1" connectable="0">
-          <mxGeometry x="0.6262" y="-3" relative="1" as="geometry">
-            <mxPoint x="-54" y="10" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-59" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="404" y="773" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-60" value="&lt;font face=&quot;Tahoma&quot;&gt;pending_trust&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#f0a30a;fontColor=#000000;" parent="1" vertex="1">
-          <mxGeometry x="410" y="779" width="100" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-61" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.5;exitY=1;exitDx=0;exitDy=0;strokeWidth=2;fillColor=#f0a30a;strokeColor=#BD7000;endArrow=open;endFill=0;" parent="1" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="260" y="847" as="targetPoint" />
-            <Array as="points">
-              <mxPoint x="759" y="848" />
-            </Array>
-            <mxPoint x="759" y="829" as="sourcePoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-62" value="(Update custody payment)" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];fontColor=#7fcffe;" parent="6D9sstSB_-0e3DwsuZUU-61" vertex="1" connectable="0">
-          <mxGeometry x="0.1115" relative="1" as="geometry">
-            <mxPoint as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-63" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="694" y="774" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-64" value="&lt;font face=&quot;Tahoma&quot;&gt;pending_stellar&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#f0a30a;fontColor=#000000;" parent="1" vertex="1">
-          <mxGeometry x="700" y="780" width="100" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-65" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="75.5" y="910" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-66" value="refunded" style="rounded=1;whiteSpace=wrap;html=1;verticalAlign=top;align=left;fillColor=#6d8764;fontFamily=Tahoma;strokeColor=none;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="82" y="915" width="59.5" height="24" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-67" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="230" y="910" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-68" value="completed" style="rounded=1;whiteSpace=wrap;html=1;verticalAlign=top;align=left;fillColor=#6d8764;fontFamily=Tahoma;strokeColor=none;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="235.5" y="915" width="78.5" height="24" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-69" value="" style="endArrow=open;html=1;entryX=0.815;entryY=0.013;entryDx=0;entryDy=0;entryPerimeter=0;strokeWidth=2;fillColor=#f0a30a;strokeColor=#BD7000;endFill=0;rounded=0;" parent="1" target="6D9sstSB_-0e3DwsuZUU-59" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="510" y="713" as="sourcePoint" />
-            <mxPoint x="640" y="613" as="targetPoint" />
-            <Array as="points" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-70" value="(Add custody payment&lt;br&gt;to queue)" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];fontColor=#67c4fd;" parent="6D9sstSB_-0e3DwsuZUU-69" vertex="1" connectable="0">
-          <mxGeometry x="0.0485" relative="1" as="geometry">
-            <mxPoint y="-2" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-71" value="" style="endArrow=open;html=1;rounded=0;strokeColor=#9b1599;strokeWidth=2;endFill=0;" parent="1" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="260" y="765" as="sourcePoint" />
-            <mxPoint x="260" y="850" as="targetPoint" />
-            <Array as="points">
-              <mxPoint x="260" y="813" />
-            </Array>
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-72" value="" style="endArrow=open;html=1;rounded=0;strokeWidth=2;endFill=0;" parent="1" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="260" y="850" as="sourcePoint" />
-            <mxPoint x="260" y="913" as="targetPoint" />
-            <Array as="points">
-              <mxPoint x="260" y="860" />
-            </Array>
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-73" value="notify_onchain_funds_sent" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="6D9sstSB_-0e3DwsuZUU-72" vertex="1" connectable="0">
-          <mxGeometry x="-0.3488" y="-1" relative="1" as="geometry">
-            <mxPoint x="16" y="-4" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-74" value="" style="endArrow=open;html=1;rounded=1;entryX=0.35;entryY=0.986;entryDx=0;entryDy=0;entryPerimeter=0;strokeWidth=2;endFill=0;" parent="1" target="6D9sstSB_-0e3DwsuZUU-31" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="140" y="818" as="sourcePoint" />
-            <mxPoint x="190" y="778" as="targetPoint" />
-            <Array as="points">
-              <mxPoint x="170" y="818" />
-              <mxPoint x="190" y="818" />
-            </Array>
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-75" value="notify_refund_sent" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="6D9sstSB_-0e3DwsuZUU-74" vertex="1" connectable="0">
-          <mxGeometry x="0.3847" relative="1" as="geometry">
-            <mxPoint as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-76" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.25;exitY=1;exitDx=0;exitDy=0;curved=0;strokeWidth=2;" parent="1" source="6D9sstSB_-0e3DwsuZUU-78" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="210" y="693" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-77" value="notify_offchain_funds_received" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="6D9sstSB_-0e3DwsuZUU-76" vertex="1" connectable="0">
-          <mxGeometry x="-0.3274" y="-1" relative="1" as="geometry">
-            <mxPoint as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-78" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="619" y="573" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-79" value="&lt;font face=&quot;Tahoma&quot;&gt;on_hold&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#f0a30a;fontColor=#000000;" parent="1" vertex="1">
-          <mxGeometry x="625" y="579" width="100" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-80" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.25;exitDx=0;exitDy=0;entryX=0.446;entryY=0;entryDx=0;entryDy=0;entryPerimeter=0;curved=0;strokeWidth=2;" parent="1" source="6D9sstSB_-0e3DwsuZUU-21" target="6D9sstSB_-0e3DwsuZUU-78" edge="1">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="6D9sstSB_-0e3DwsuZUU-81" value="&lt;font style=&quot;font-size: 11px;&quot;&gt;notify_transaction_on_hold&lt;/font&gt;" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="6D9sstSB_-0e3DwsuZUU-80" vertex="1" connectable="0">
-          <mxGeometry x="0.1901" y="4" relative="1" as="geometry">
-            <mxPoint y="1" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="kNYIP-7js3pLc9XgrcXy-1" value="" style="endArrow=open;html=1;rounded=1;exitX=0.15;exitY=-0.054;exitDx=0;exitDy=0;exitPerimeter=0;entryX=0.877;entryY=-0.022;entryDx=0;entryDy=0;entryPerimeter=0;jumpStyle=arc;strokeWidth=2;endFill=0;" edge="1" parent="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="150.59000000000023" y="694.9999999999999" as="sourcePoint" />
-            <mxPoint x="266.9100000000002" y="694.1199999999999" as="targetPoint" />
-            <Array as="points">
-              <mxPoint x="150.59" y="657" />
-              <mxPoint x="266.59000000000003" y="657" />
-              <mxPoint x="266.59000000000003" y="675" />
-            </Array>
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="kNYIP-7js3pLc9XgrcXy-2" value="notify_amounts_updated" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" connectable="0" vertex="1" parent="kNYIP-7js3pLc9XgrcXy-1">
-          <mxGeometry x="-0.2381" y="1" relative="1" as="geometry">
-            <mxPoint x="-56" y="17" as="offset" />
-          </mxGeometry>
-        </mxCell>
-      </root>
-    </mxGraphModel>
-  </diagram>
-  <diagram name="Sep24 - withdrawal v.0.4" id="h_MZTiaThZiv6oo3dpg_">
-    <mxGraphModel dx="3982" dy="869" grid="1" gridSize="10" guides="1" tooltips="1" connect="1" arrows="1" fold="1" page="1" pageScale="1" pageWidth="850" pageHeight="1100" math="0" shadow="0">
-      <root>
-        <mxCell id="0" />
-        <mxCell id="1" parent="0" />
-        <mxCell id="19DFnFGgezubew46fDbJ-8" value="" style="rounded=0;whiteSpace=wrap;html=1;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="-2312" y="70" width="1120.5" height="770" as="geometry" />
-        </mxCell>
-        <mxCell id="olQjKZX7w5ClR32a8ufF-7" value="" style="endArrow=open;html=1;rounded=1;exitX=0.5;exitY=1;exitDx=0;exitDy=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;strokeWidth=2;endFill=0;" parent="1" source="1VmnTqBAucP6j0lEsLy9-7" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="-1794" y="429.1199999999999" as="sourcePoint" />
-            <mxPoint x="-1794" y="530" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="8ilRtFF8TZkBPPpWjRlk-1" value="notify_onchain_funds_received" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="olQjKZX7w5ClR32a8ufF-7" connectable="0" vertex="1">
-          <mxGeometry x="-0.1542" y="3" relative="1" as="geometry">
-            <mxPoint x="-2" y="-7" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="olQjKZX7w5ClR32a8ufF-31" value="" style="endArrow=open;html=1;rounded=1;exitX=0.844;exitY=1.017;exitDx=0;exitDy=0;exitPerimeter=0;strokeWidth=2;endFill=0;" parent="1" source="uuhxsLCSQKmmBB7-Bimi-1" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="-1734.1599999999999" y="570.44" as="sourcePoint" />
-            <mxPoint x="-1734" y="745.88" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="olQjKZX7w5ClR32a8ufF-32" value="notify_offchain_funds_sent" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="olQjKZX7w5ClR32a8ufF-31" connectable="0" vertex="1">
-          <mxGeometry x="-0.5215" y="1" relative="1" as="geometry">
-            <mxPoint x="13" y="91" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="olQjKZX7w5ClR32a8ufF-33" value="" style="endArrow=open;html=1;exitX=0.178;exitY=0.983;exitDx=0;exitDy=0;exitPerimeter=0;entryX=0.75;entryY=0;entryDx=0;entryDy=0;strokeWidth=2;rounded=1;endFill=0;" parent="1" source="uuhxsLCSQKmmBB7-Bimi-1" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="-1853.8400000000001" y="571.1199999999999" as="sourcePoint" />
-            <mxPoint x="-1854" y="747.51" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="olQjKZX7w5ClR32a8ufF-34" value="notify_refund_sent" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="olQjKZX7w5ClR32a8ufF-33" connectable="0" vertex="1">
-          <mxGeometry x="-0.5594" relative="1" as="geometry">
-            <mxPoint x="4" y="88" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="olQjKZX7w5ClR32a8ufF-35" value="SEP24 withdrawal flow" style="text;html=1;strokeColor=none;fillColor=none;align=center;verticalAlign=middle;whiteSpace=wrap;rounded=0;fontSize=17;fontStyle=1" parent="1" vertex="1">
-          <mxGeometry x="-1914" y="70" width="240" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="wfEdxK96i-KRs6hGnqwD-1" value="" style="endArrow=open;html=1;rounded=1;exitX=0.15;exitY=-0.054;exitDx=0;exitDy=0;exitPerimeter=0;entryX=0.877;entryY=-0.022;entryDx=0;entryDy=0;entryPerimeter=0;jumpStyle=arc;strokeWidth=2;endFill=0;" parent="1" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="-1849.9999999999998" y="530.9999999999999" as="sourcePoint" />
-            <mxPoint x="-1733.6799999999998" y="530.1199999999999" as="targetPoint" />
-            <Array as="points">
-              <mxPoint x="-1850" y="493" />
-              <mxPoint x="-1734" y="493" />
-              <mxPoint x="-1734" y="511" />
-            </Array>
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="wfEdxK96i-KRs6hGnqwD-2" value="notify_amounts_updated" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="wfEdxK96i-KRs6hGnqwD-1" connectable="0" vertex="1">
-          <mxGeometry x="-0.2381" y="1" relative="1" as="geometry">
-            <mxPoint x="95" y="17" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="lWr0Hpx_SfrrkMofASAg-2" value="" style="endArrow=open;html=1;rounded=1;exitX=1;exitY=0.25;exitDx=0;exitDy=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;strokeWidth=2;endFill=0;" parent="1" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="-1740" y="557" as="sourcePoint" />
-            <mxPoint x="-1359.5" y="616.8800000000001" as="targetPoint" />
-            <Array as="points">
-              <mxPoint x="-1360" y="557" />
-            </Array>
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="lWr0Hpx_SfrrkMofASAg-3" value="notify_offchain_funds_pending" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="lWr0Hpx_SfrrkMofASAg-2" connectable="0" vertex="1">
-          <mxGeometry x="-0.1591" y="-2" relative="1" as="geometry">
-            <mxPoint x="97" y="-8" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="1VmnTqBAucP6j0lEsLy9-1" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="-1764" y="747.51" width="180" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="1VmnTqBAucP6j0lEsLy9-2" value="completed" style="rounded=1;whiteSpace=wrap;html=1;verticalAlign=top;align=left;fillColor=#6d8764;fontFamily=Tahoma;strokeColor=none;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="-1754" y="752.51" width="105" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="1VmnTqBAucP6j0lEsLy9-3" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="-1965" y="748" width="180" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="1VmnTqBAucP6j0lEsLy9-4" value="refunded" style="rounded=1;whiteSpace=wrap;html=1;verticalAlign=top;align=left;fillColor=#6d8764;fontFamily=Tahoma;strokeColor=none;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="-1955" y="752.51" width="105" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="uuhxsLCSQKmmBB7-Bimi-4" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.5;exitY=1;exitDx=0;exitDy=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="1VmnTqBAucP6j0lEsLy9-5" target="1VmnTqBAucP6j0lEsLy9-7" edge="1">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="uuhxsLCSQKmmBB7-Bimi-5" value="request_onchain_funds&lt;br style=&quot;border-color: var(--border-color);&quot;&gt;(&lt;font style=&quot;border-color: var(--border-color);&quot; color=&quot;#0066cc&quot;&gt;Create custody transaction*&lt;br style=&quot;border-color: var(--border-color);&quot;&gt;&lt;/font&gt;&lt;font style=&quot;border-color: var(--border-color);&quot; color=&quot;#0066cc&quot;&gt;Generate custody address and memo*&lt;/font&gt;)" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="uuhxsLCSQKmmBB7-Bimi-4" vertex="1" connectable="0">
-          <mxGeometry x="0.5099" y="1" relative="1" as="geometry">
-            <mxPoint as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="i1Tsm2N9LzVnO38OjRS3-1" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.5;exitDx=0;exitDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="1VmnTqBAucP6j0lEsLy9-5" target="N_XBzseesMyBwSn1S0o6-1" edge="1">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="i1Tsm2N9LzVnO38OjRS3-2" value="notify_interactive_flow_completed" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="i1Tsm2N9LzVnO38OjRS3-1" vertex="1" connectable="0">
-          <mxGeometry x="0.7931" y="-1" relative="1" as="geometry">
-            <mxPoint as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="1VmnTqBAucP6j0lEsLy9-5" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="-1885" y="135" width="180" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="1VmnTqBAucP6j0lEsLy9-6" value="incomplete" style="rounded=1;whiteSpace=wrap;html=1;verticalAlign=top;align=left;fillColor=#6d8764;fontFamily=Tahoma;strokeColor=none;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="-1880" y="145" width="105" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="BCe4yO_wYxQrQEUp4EnU-9" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.5;exitDx=0;exitDy=0;entryX=0;entryY=0.75;entryDx=0;entryDy=0;strokeWidth=2;curved=0;" edge="1" parent="1" source="1VmnTqBAucP6j0lEsLy9-7" target="BCe4yO_wYxQrQEUp4EnU-3">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="1VmnTqBAucP6j0lEsLy9-7" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="-1885" y="379.12" width="180" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="1VmnTqBAucP6j0lEsLy9-8" value="pending_user_transfer_start" style="rounded=1;whiteSpace=wrap;html=1;verticalAlign=top;align=left;fillColor=#6d8764;fontFamily=Tahoma;strokeColor=none;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="-1880" y="384.12" width="160" height="30.88" as="geometry" />
-        </mxCell>
-        <mxCell id="uuhxsLCSQKmmBB7-Bimi-6" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.5;exitY=1;exitDx=0;exitDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="N_XBzseesMyBwSn1S0o6-1" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="-1794" y="260" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="N_XBzseesMyBwSn1S0o6-1" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="-1564" y="220" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="N_XBzseesMyBwSn1S0o6-2" value="&lt;font face=&quot;Tahoma&quot;&gt;pending_anchor&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#f0a30a;fontColor=#000000;" parent="1" vertex="1">
-          <mxGeometry x="-1554" y="230" width="94" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="myNQpcoXiVufHVnh7pvk-1" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="-2259" y="652.88" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="myNQpcoXiVufHVnh7pvk-2" value="&lt;font face=&quot;Tahoma&quot;&gt;pending_stellar&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#f0a30a;fontColor=#000000;" parent="1" vertex="1">
-          <mxGeometry x="-2259" y="660" width="100" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="xSZGYQ3GUr2Xv4BTAuLV-17" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.5;exitY=1;exitDx=0;exitDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="-1562" y="700" as="targetPoint" />
-            <mxPoint x="-1361" y="676.8800000000001" as="sourcePoint" />
-            <Array as="points">
-              <mxPoint x="-1361" y="700" />
-            </Array>
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="1E8NPX2utK_tuPmvM1R9-1" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="-1424" y="616.88" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="1E8NPX2utK_tuPmvM1R9-2" value="&lt;font face=&quot;Tahoma&quot;&gt;pending_external&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#f0a30a;fontColor=#000000;" parent="1" vertex="1">
-          <mxGeometry x="-1416" y="622.88" width="100" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="xSZGYQ3GUr2Xv4BTAuLV-16" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;endArrow=open;endFill=0;strokeWidth=2;" parent="1" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="-1735" y="700" as="targetPoint" />
-            <mxPoint x="-1560" y="677" as="sourcePoint" />
-            <Array as="points">
-              <mxPoint x="-1560" y="677" />
-              <mxPoint x="-1560" y="700" />
-            </Array>
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="T8IIk7023ObEj98OedEK-5" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0;exitY=0.5;exitDx=0;exitDy=0;entryX=1;entryY=0.5;entryDx=0;entryDy=0;curved=0;strokeWidth=2;" edge="1" parent="1" source="xENiUxB1cImVQo_JTPu--1" target="T8IIk7023ObEj98OedEK-3">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="T8IIk7023ObEj98OedEK-8" value="notify_refund_pending" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" vertex="1" connectable="0" parent="T8IIk7023ObEj98OedEK-5">
-          <mxGeometry x="-0.1228" y="-1" relative="1" as="geometry">
-            <mxPoint x="2" y="-36" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="xENiUxB1cImVQo_JTPu--1" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="-1668" y="616.88" width="210" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="xENiUxB1cImVQo_JTPu--2" value="pending_user_transfer_complete" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#f0a30a;fontColor=#000000;" parent="1" vertex="1">
-          <mxGeometry x="-1659" y="622.88" width="190" height="37.12" as="geometry" />
-        </mxCell>
-        <mxCell id="xSZGYQ3GUr2Xv4BTAuLV-3" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.5;exitY=1;exitDx=0;exitDy=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="Jpj7JL_jpf0lYQ3cLoy5-1" target="xSZGYQ3GUr2Xv4BTAuLV-1" edge="1">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="xSZGYQ3GUr2Xv4BTAuLV-4" value="notify_transaction_error&lt;br style=&quot;border-color: var(--border-color);&quot;&gt;notify_transaction_expired" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="xSZGYQ3GUr2Xv4BTAuLV-3" vertex="1" connectable="0">
-          <mxGeometry x="0.0099" y="-1" relative="1" as="geometry">
-            <mxPoint as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="Jpj7JL_jpf0lYQ3cLoy5-1" value="&lt;font style=&quot;&quot; face=&quot;Tahoma&quot;&gt;Any status other than completed or refunded&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#f5f5f5;align=center;verticalAlign=top;fontColor=#333333;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="-2144" y="280" width="130" height="70" as="geometry" />
-        </mxCell>
-        <mxCell id="xSZGYQ3GUr2Xv4BTAuLV-7" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0;exitY=0.5;exitDx=0;exitDy=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="uuhxsLCSQKmmBB7-Bimi-1" target="myNQpcoXiVufHVnh7pvk-1" edge="1">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="xSZGYQ3GUr2Xv4BTAuLV-8" value="do_stellar_refund&lt;br style=&quot;border-color: var(--border-color);&quot;&gt;(&lt;font style=&quot;border-color: var(--border-color);&quot; color=&quot;#0066cc&quot;&gt;Do&amp;nbsp;custody payment&lt;/font&gt;)" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="xSZGYQ3GUr2Xv4BTAuLV-7" vertex="1" connectable="0">
-          <mxGeometry x="0.8113" relative="1" as="geometry">
-            <mxPoint y="-13" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="xSZGYQ3GUr2Xv4BTAuLV-12" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.75;exitDx=0;exitDy=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="uuhxsLCSQKmmBB7-Bimi-1" target="xENiUxB1cImVQo_JTPu--1" edge="1">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="xSZGYQ3GUr2Xv4BTAuLV-13" value="notify_offchain_funds_available" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="xSZGYQ3GUr2Xv4BTAuLV-12" vertex="1" connectable="0">
-          <mxGeometry x="0.7403" relative="1" as="geometry">
-            <mxPoint as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="BCe4yO_wYxQrQEUp4EnU-11" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.25;exitDx=0;exitDy=0;entryX=0;entryY=0.75;entryDx=0;entryDy=0;strokeWidth=2;curved=0;" edge="1" parent="1" source="uuhxsLCSQKmmBB7-Bimi-1" target="BCe4yO_wYxQrQEUp4EnU-3">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="-1570" y="430" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="BCe4yO_wYxQrQEUp4EnU-12" value="notify_transaction_on_hold" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" vertex="1" connectable="0" parent="BCe4yO_wYxQrQEUp4EnU-11">
-          <mxGeometry x="0.0763" y="-2" relative="1" as="geometry">
-            <mxPoint y="-33" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="uuhxsLCSQKmmBB7-Bimi-1" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=#82b366;" parent="1" vertex="1">
-          <mxGeometry x="-1886" y="531" width="180" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="uuhxsLCSQKmmBB7-Bimi-2" value="pending_anchor" style="rounded=1;whiteSpace=wrap;html=1;verticalAlign=top;align=left;fillColor=#6d8764;fontFamily=Tahoma;strokeColor=none;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="-1881" y="536" width="100" height="30.88" as="geometry" />
-        </mxCell>
-        <mxCell id="xSZGYQ3GUr2Xv4BTAuLV-5" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.5;exitY=1;exitDx=0;exitDy=0;entryX=0;entryY=0.25;entryDx=0;entryDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="xSZGYQ3GUr2Xv4BTAuLV-1" target="uuhxsLCSQKmmBB7-Bimi-1" edge="1">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="xSZGYQ3GUr2Xv4BTAuLV-6" value="notify_transaction_recovery" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="xSZGYQ3GUr2Xv4BTAuLV-5" vertex="1" connectable="0">
-          <mxGeometry x="-0.7592" y="-1" relative="1" as="geometry">
-            <mxPoint as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="xSZGYQ3GUr2Xv4BTAuLV-1" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#f8cecc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="-2144" y="439.12" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="xSZGYQ3GUr2Xv4BTAuLV-2" value="&lt;font face=&quot;Tahoma&quot;&gt;error/expired&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#e51400;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="-2136" y="445.12" width="80" height="25" as="geometry" />
-        </mxCell>
-        <mxCell id="19DFnFGgezubew46fDbJ-1" value="" style="group" parent="1" vertex="1" connectable="0">
-          <mxGeometry x="-2358" y="135" width="508" height="163" as="geometry" />
-        </mxCell>
-        <mxCell id="19DFnFGgezubew46fDbJ-2" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;" parent="19DFnFGgezubew46fDbJ-1" vertex="1">
-          <mxGeometry x="74" y="5" width="50" height="20" as="geometry" />
-        </mxCell>
-        <mxCell id="19DFnFGgezubew46fDbJ-3" value="shortest e2e status flow" style="text;strokeColor=none;align=center;fillColor=none;html=1;verticalAlign=middle;whiteSpace=wrap;rounded=0;" parent="19DFnFGgezubew46fDbJ-1" vertex="1">
-          <mxGeometry x="124" width="146" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="19DFnFGgezubew46fDbJ-4" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" parent="19DFnFGgezubew46fDbJ-1" vertex="1">
-          <mxGeometry x="74" y="30" width="50" height="20" as="geometry" />
-        </mxCell>
-        <mxCell id="19DFnFGgezubew46fDbJ-5" value="optional status, available for business" style="text;strokeColor=none;align=center;fillColor=none;html=1;verticalAlign=middle;whiteSpace=wrap;rounded=0;" parent="19DFnFGgezubew46fDbJ-1" vertex="1">
-          <mxGeometry x="122" y="25" width="220" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="19DFnFGgezubew46fDbJ-6" value="(&lt;font style=&quot;border-color: var(--border-color); text-align: left;&quot; color=&quot;#66b2ff&quot;&gt;function&lt;/font&gt;&lt;span style=&quot;text-align: left;&quot;&gt;)&lt;/span&gt;" style="rounded=1;whiteSpace=wrap;html=1;fillColor=none;strokeColor=none;" parent="19DFnFGgezubew46fDbJ-1" vertex="1">
-          <mxGeometry x="74" y="55" width="54" height="20" as="geometry" />
-        </mxCell>
-        <mxCell id="19DFnFGgezubew46fDbJ-7" value="&lt;font style=&quot;border-color: var(--border-color); text-align: left;&quot;&gt;a side effect that will be triggered by an action&lt;/font&gt;" style="text;strokeColor=none;align=left;fillColor=none;html=1;verticalAlign=middle;whiteSpace=wrap;rounded=0;labelPosition=right;verticalLabelPosition=middle;" parent="19DFnFGgezubew46fDbJ-1" vertex="1">
-          <mxGeometry x="-170" y="50" width="300" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="T8IIk7023ObEj98OedEK-1" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.5;exitDx=0;exitDy=0;curved=0;strokeWidth=2;" edge="1" parent="1" source="myNQpcoXiVufHVnh7pvk-1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="-1855" y="683" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="T8IIk7023ObEj98OedEK-2" value="(&lt;font style=&quot;border-color: var(--border-color);&quot; color=&quot;#0066cc&quot;&gt;Update&lt;/font&gt;&lt;font style=&quot;border-color: var(--border-color); color: rgb(0, 153, 227);&quot;&gt;&amp;nbsp;&lt;/font&gt;&lt;font style=&quot;border-color: var(--border-color);&quot; color=&quot;#0066cc&quot;&gt;custody payment&lt;/font&gt;)" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" vertex="1" connectable="0" parent="T8IIk7023ObEj98OedEK-1">
-          <mxGeometry x="-0.5449" y="-3" relative="1" as="geometry">
-            <mxPoint x="11" y="-5" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="T8IIk7023ObEj98OedEK-9" style="edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.75;exitDx=0;exitDy=0;strokeWidth=2;" edge="1" parent="1" source="T8IIk7023ObEj98OedEK-3">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="-1850" y="638" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="T8IIk7023ObEj98OedEK-3" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" vertex="1" parent="1">
-          <mxGeometry x="-2091" y="593.88" width="141" height="59" as="geometry" />
-        </mxCell>
-        <mxCell id="T8IIk7023ObEj98OedEK-4" value="pending_anchor" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#f0a30a;fontColor=#000000;" vertex="1" parent="1">
-          <mxGeometry x="-2082" y="593.88" width="102" height="33" as="geometry" />
-        </mxCell>
-        <mxCell id="BCe4yO_wYxQrQEUp4EnU-5" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.25;exitY=1;exitDx=0;exitDy=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;curved=0;strokeWidth=2;" edge="1" parent="1" source="BCe4yO_wYxQrQEUp4EnU-3" target="xENiUxB1cImVQo_JTPu--1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="-1560" y="610" as="targetPoint" />
-            <Array as="points">
-              <mxPoint x="-1529" y="460" />
-              <mxPoint x="-1530" y="530" />
-              <mxPoint x="-1563" y="530" />
-            </Array>
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="BCe4yO_wYxQrQEUp4EnU-3" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" vertex="1" parent="1">
-          <mxGeometry x="-1560" y="384.68" width="122" height="60.44" as="geometry" />
-        </mxCell>
-        <mxCell id="BCe4yO_wYxQrQEUp4EnU-4" value="&lt;div&gt;&lt;font face=&quot;Tahoma&quot;&gt;on_hold&lt;/font&gt;&lt;/div&gt;" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#f0a30a;fontColor=#000000;" vertex="1" parent="1">
-          <mxGeometry x="-1554" y="391.90000000000003" width="63" height="34.44" as="geometry" />
-        </mxCell>
-      </root>
-    </mxGraphModel>
-  </diagram>
-  <diagram name="Sep31 v0.2" id="I0B1hNTEJ4JI3OO0i4h9">
-    <mxGraphModel dx="2059" dy="1080" grid="1" gridSize="10" guides="1" tooltips="1" connect="1" arrows="1" fold="1" page="1" pageScale="1" pageWidth="850" pageHeight="1100" math="0" shadow="0">
-      <root>
-        <mxCell id="0" />
-        <mxCell id="1" parent="0" />
-        <mxCell id="67SbY_f3dpDVczb7oRwc-1" value="" style="rounded=0;whiteSpace=wrap;html=1;strokeWidth=0;" parent="1" vertex="1">
-          <mxGeometry x="132.5" y="180" width="1200" height="840" as="geometry" />
-        </mxCell>
-        <mxCell id="kk59w1MAhV7eQLREM1ms-1" value="" style="group" parent="1" vertex="1" connectable="0">
-          <mxGeometry y="444.5" width="508" height="163" as="geometry" />
-        </mxCell>
-        <mxCell id="kk59w1MAhV7eQLREM1ms-2" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;" parent="kk59w1MAhV7eQLREM1ms-1" vertex="1">
-          <mxGeometry x="240" y="5" width="50" height="20" as="geometry" />
-        </mxCell>
-        <mxCell id="kk59w1MAhV7eQLREM1ms-3" value="shortest e2e status flow" style="text;strokeColor=none;align=center;fillColor=none;html=1;verticalAlign=middle;whiteSpace=wrap;rounded=0;" parent="kk59w1MAhV7eQLREM1ms-1" vertex="1">
-          <mxGeometry x="290" width="140" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="kk59w1MAhV7eQLREM1ms-4" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" parent="kk59w1MAhV7eQLREM1ms-1" vertex="1">
-          <mxGeometry x="240" y="30" width="50" height="20" as="geometry" />
-        </mxCell>
-        <mxCell id="kk59w1MAhV7eQLREM1ms-5" value="optional status, available for business" style="text;strokeColor=none;align=center;fillColor=none;html=1;verticalAlign=middle;whiteSpace=wrap;rounded=0;" parent="kk59w1MAhV7eQLREM1ms-1" vertex="1">
-          <mxGeometry x="288" y="25" width="220" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="kk59w1MAhV7eQLREM1ms-6" value="(&lt;font style=&quot;border-color: var(--border-color); text-align: left;&quot; color=&quot;#66b2ff&quot;&gt;function&lt;/font&gt;&lt;span style=&quot;text-align: left;&quot;&gt;)&lt;/span&gt;" style="rounded=1;whiteSpace=wrap;html=1;fillColor=none;strokeColor=none;" parent="kk59w1MAhV7eQLREM1ms-1" vertex="1">
-          <mxGeometry x="240" y="55" width="54" height="20" as="geometry" />
-        </mxCell>
-        <mxCell id="kk59w1MAhV7eQLREM1ms-7" value="&lt;font style=&quot;border-color: var(--border-color); text-align: left;&quot;&gt;a side effect that will be triggered by an action&lt;br style=&quot;border-color: var(--border-color);&quot;&gt;&lt;/font&gt;if its Anchor is in custody mode" style="text;strokeColor=none;align=left;fillColor=none;html=1;verticalAlign=middle;whiteSpace=wrap;rounded=0;labelPosition=right;verticalLabelPosition=middle;" parent="kk59w1MAhV7eQLREM1ms-1" vertex="1">
-          <mxGeometry y="55" width="300" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="mxeJzW8ZGcNlbu38qCdp-11" value="" style="endArrow=open;html=1;rounded=1;exitX=0.5;exitY=1;exitDx=0;exitDy=0;entryX=0.467;entryY=0;entryDx=0;entryDy=0;entryPerimeter=0;endFill=0;strokeWidth=2;" parent="1" target="Kf9qd6CPrOdVnlglGHAT-5" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="759.5" y="565" as="sourcePoint" />
-            <mxPoint x="757.98" y="722.01" as="targetPoint" />
-            <Array as="points">
-              <mxPoint x="759" y="680" />
-            </Array>
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="mxeJzW8ZGcNlbu38qCdp-12" value="notify_onchain_funds_received" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="mxeJzW8ZGcNlbu38qCdp-11" connectable="0" vertex="1">
-          <mxGeometry x="-0.55" y="-1" relative="1" as="geometry">
-            <mxPoint x="2" y="1" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="mxeJzW8ZGcNlbu38qCdp-13" value="SEP31 Status Transition Diagram" style="text;html=1;strokeColor=none;fillColor=none;align=center;verticalAlign=middle;whiteSpace=wrap;rounded=0;fontSize=17;fontStyle=1" parent="1" vertex="1">
-          <mxGeometry x="596.25" y="210" width="272.5" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="mxeJzW8ZGcNlbu38qCdp-19" value="&lt;b&gt;Prior to pending_sender status, the receiver business has to communicate &lt;br&gt;with the sender business and provide all necessary data on sep31 transaction creation&amp;nbsp;&lt;/b&gt;" style="text;html=1;align=center;verticalAlign=middle;resizable=0;points=[];autosize=1;strokeColor=none;fillColor=none;" parent="1" vertex="1">
-          <mxGeometry x="472.5" y="250" width="520" height="40" as="geometry" />
-        </mxCell>
-        <mxCell id="mxeJzW8ZGcNlbu38qCdp-20" value="" style="endArrow=open;html=1;rounded=1;strokeWidth=2;endFill=0;entryX=0.75;entryY=0;entryDx=0;entryDy=0;exitX=0.015;exitY=0.417;exitDx=0;exitDy=0;exitPerimeter=0;" parent="1" source="avnREUv3o3WgOM-XI5gU-1" target="Kf9qd6CPrOdVnlglGHAT-5" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="1009" y="680" as="sourcePoint" />
-            <mxPoint x="810" y="710" as="targetPoint" />
-            <Array as="points">
-              <mxPoint x="810" y="680" />
-            </Array>
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="mxeJzW8ZGcNlbu38qCdp-21" value="notify_transaction_recovery" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="mxeJzW8ZGcNlbu38qCdp-20" connectable="0" vertex="1">
-          <mxGeometry x="-0.1381" y="2" relative="1" as="geometry">
-            <mxPoint x="7" y="-2" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="mxeJzW8ZGcNlbu38qCdp-56" value="" style="endArrow=open;html=1;rounded=0;exitX=0.25;exitY=1;exitDx=0;exitDy=0;strokeWidth=2;endFill=0;" parent="1" source="Kf9qd6CPrOdVnlglGHAT-5" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="720" y="738" as="sourcePoint" />
-            <mxPoint x="720" y="920" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="mxeJzW8ZGcNlbu38qCdp-57" value="notify_refund_sent" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];fontSize=11;" parent="mxeJzW8ZGcNlbu38qCdp-56" connectable="0" vertex="1">
-          <mxGeometry x="0.1352" y="-1" relative="1" as="geometry">
-            <mxPoint x="-9" y="6" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="mxeJzW8ZGcNlbu38qCdp-58" value="" style="endArrow=open;html=1;rounded=0;exitX=0.75;exitY=1;exitDx=0;exitDy=0;strokeWidth=2;endFill=0;" parent="1" source="Kf9qd6CPrOdVnlglGHAT-5" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="816.8000000000002" y="767.3358800000001" as="sourcePoint" />
-            <mxPoint x="810" y="920" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="mxeJzW8ZGcNlbu38qCdp-59" value="notify_offchain_funds_sent" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];fontSize=11;" parent="mxeJzW8ZGcNlbu38qCdp-58" connectable="0" vertex="1">
-          <mxGeometry x="-0.0667" relative="1" as="geometry">
-            <mxPoint x="20" y="19" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="3zLw-5_e-Gk6-DkVr-vM-1" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="670" y="496" width="180" height="70" as="geometry" />
-        </mxCell>
-        <mxCell id="3zLw-5_e-Gk6-DkVr-vM-2" value="pending_sender" style="rounded=1;whiteSpace=wrap;html=1;verticalAlign=top;align=left;fillColor=#6d8764;fontFamily=Tahoma;strokeColor=none;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="675" y="505" width="105" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="BmFnIRON6w-JdGfR3euQ-2" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;entryX=0.75;entryY=0;entryDx=0;entryDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="1047.5" y="576" as="sourcePoint" />
-            <mxPoint x="1047.5" y="651" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="BmFnIRON6w-JdGfR3euQ-3" value="notify_transaction_error&lt;br style=&quot;border-color: var(--border-color);&quot;&gt;notify_transaction_expired" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="BmFnIRON6w-JdGfR3euQ-2" vertex="1" connectable="0">
-          <mxGeometry x="-0.04" y="1" relative="1" as="geometry">
-            <mxPoint as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="yReZv6md1lE1Uv3bfNHC-1" value="Any status other than completed or refunded" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#f5f5f5;fontColor=#333333;strokeColor=none;verticalAlign=top;" parent="1" vertex="1">
-          <mxGeometry x="983" y="496" width="130" height="80" as="geometry" />
-        </mxCell>
-        <mxCell id="avnREUv3o3WgOM-XI5gU-1" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#f8cecc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="980" y="655" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="avnREUv3o3WgOM-XI5gU-2" value="&lt;font face=&quot;Tahoma&quot;&gt;error/expired&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#e51400;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="988" y="661" width="80" height="25" as="geometry" />
-        </mxCell>
-        <mxCell id="avnREUv3o3WgOM-XI5gU-6" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="570" y="921" width="180" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="avnREUv3o3WgOM-XI5gU-5" value="refunded" style="rounded=1;whiteSpace=wrap;html=1;verticalAlign=top;align=left;fillColor=#6d8764;fontFamily=Tahoma;strokeColor=none;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="575" y="926" width="105" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="avnREUv3o3WgOM-XI5gU-9" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="780" y="921" width="180" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="avnREUv3o3WgOM-XI5gU-10" value="completed" style="rounded=1;whiteSpace=wrap;html=1;verticalAlign=top;align=left;fillColor=#6d8764;fontFamily=Tahoma;strokeColor=none;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="788" y="927" width="105" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="Kf9qd6CPrOdVnlglGHAT-26" style="edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;exitX=0;exitY=0.5;exitDx=0;exitDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="05dBtIRlAfErdCgNeG_9-1" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="810" y="830" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="05dBtIRlAfErdCgNeG_9-1" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="980" y="800" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="05dBtIRlAfErdCgNeG_9-2" value="&lt;font face=&quot;Tahoma&quot;&gt;pending_external&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#f0a30a;fontColor=#000000;" parent="1" vertex="1">
-          <mxGeometry x="988" y="806" width="100" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="Kf9qd6CPrOdVnlglGHAT-23" style="edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.5;exitDx=0;exitDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="Kf9qd6CPrOdVnlglGHAT-1" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="720" y="830" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="Kf9qd6CPrOdVnlglGHAT-24" value="(&lt;font style=&quot;border-color: var(--border-color);&quot; color=&quot;#0066cc&quot;&gt;Update&lt;/font&gt;&lt;font style=&quot;border-color: var(--border-color); color: rgb(0, 153, 227);&quot;&gt;&amp;nbsp;&lt;/font&gt;&lt;font style=&quot;border-color: var(--border-color);&quot; color=&quot;#0066cc&quot;&gt;custody payment&lt;/font&gt;)" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="Kf9qd6CPrOdVnlglGHAT-23" vertex="1" connectable="0">
-          <mxGeometry x="-0.3295" y="-2" relative="1" as="geometry">
-            <mxPoint x="-6" y="-2" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="Kf9qd6CPrOdVnlglGHAT-1" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="280" y="800" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="Kf9qd6CPrOdVnlglGHAT-2" value="&lt;font face=&quot;Tahoma&quot;&gt;pending_stellar&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#f0a30a;fontColor=#000000;" parent="1" vertex="1">
-          <mxGeometry x="286" y="806" width="100" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="Kf9qd6CPrOdVnlglGHAT-16" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.5;exitY=1;exitDx=0;exitDy=0;entryX=0;entryY=0.25;entryDx=0;entryDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="Kf9qd6CPrOdVnlglGHAT-3" target="Kf9qd6CPrOdVnlglGHAT-5" edge="1">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="Kf9qd6CPrOdVnlglGHAT-17" value="notify_customer_info_updated" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="Kf9qd6CPrOdVnlglGHAT-16" vertex="1" connectable="0">
-          <mxGeometry x="0.009" y="-1" relative="1" as="geometry">
-            <mxPoint x="35" y="1" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="Kf9qd6CPrOdVnlglGHAT-3" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="252" y="607.5" width="200" height="70" as="geometry" />
-        </mxCell>
-        <mxCell id="Kf9qd6CPrOdVnlglGHAT-4" value="pending_customer_info_update" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#f0a30a;fontColor=#000000;" parent="1" vertex="1">
-          <mxGeometry x="258" y="613.5" width="174" height="34" as="geometry" />
-        </mxCell>
-        <mxCell id="Kf9qd6CPrOdVnlglGHAT-12" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0;exitY=0.75;exitDx=0;exitDy=0;entryX=0.554;entryY=-0.033;entryDx=0;entryDy=0;entryPerimeter=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="Kf9qd6CPrOdVnlglGHAT-5" target="Kf9qd6CPrOdVnlglGHAT-1" edge="1">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="Kf9qd6CPrOdVnlglGHAT-13" value="do_stellar_refund&lt;br style=&quot;border-color: var(--border-color);&quot;&gt;(&lt;font style=&quot;border-color: var(--border-color);&quot; color=&quot;#0066cc&quot;&gt;Do&amp;nbsp;custody payment&lt;/font&gt;)" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="Kf9qd6CPrOdVnlglGHAT-12" vertex="1" connectable="0">
-          <mxGeometry x="0.021" y="1" relative="1" as="geometry">
-            <mxPoint x="3" y="4" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="Kf9qd6CPrOdVnlglGHAT-14" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.25;exitY=0;exitDx=0;exitDy=0;entryX=1;entryY=0.5;entryDx=0;entryDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="Kf9qd6CPrOdVnlglGHAT-5" target="Kf9qd6CPrOdVnlglGHAT-3" edge="1">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="Kf9qd6CPrOdVnlglGHAT-15" value="notify_customer_info_updated" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="Kf9qd6CPrOdVnlglGHAT-14" vertex="1" connectable="0">
-          <mxGeometry x="0.4876" y="3" relative="1" as="geometry">
-            <mxPoint x="49" y="-3" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="Kf9qd6CPrOdVnlglGHAT-18" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.5;exitDx=0;exitDy=0;entryX=0.554;entryY=0.017;entryDx=0;entryDy=0;entryPerimeter=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="Kf9qd6CPrOdVnlglGHAT-5" target="05dBtIRlAfErdCgNeG_9-1" edge="1">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="Kf9qd6CPrOdVnlglGHAT-19" value="notify_offchain_funds_pending" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="Kf9qd6CPrOdVnlglGHAT-18" vertex="1" connectable="0">
-          <mxGeometry x="-0.3416" y="-2" relative="1" as="geometry">
-            <mxPoint x="7" y="-2" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="Kf9qd6CPrOdVnlglGHAT-5" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="675" y="720" width="180" height="70" as="geometry" />
-        </mxCell>
-        <mxCell id="Kf9qd6CPrOdVnlglGHAT-6" value="pending_receiver" style="rounded=1;whiteSpace=wrap;html=1;verticalAlign=top;align=left;fillColor=#6d8764;fontFamily=Tahoma;strokeColor=none;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="680" y="729" width="105" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="MjSyEAo8ha0iVIPv7yy3-1" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;" vertex="1" parent="1">
-          <mxGeometry x="670" y="320" width="180" height="70" as="geometry" />
-        </mxCell>
-        <mxCell id="MjSyEAo8ha0iVIPv7yy3-2" value="pending_receiver" style="rounded=1;whiteSpace=wrap;html=1;verticalAlign=top;align=left;fillColor=#6d8764;fontFamily=Tahoma;strokeColor=none;fontColor=#ffffff;" vertex="1" parent="1">
-          <mxGeometry x="675" y="330" width="105" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="MjSyEAo8ha0iVIPv7yy3-3" value="" style="endArrow=open;html=1;rounded=1;exitX=0.5;exitY=1;exitDx=0;exitDy=0;endFill=0;strokeWidth=2;entryX=0.5;entryY=0;entryDx=0;entryDy=0;" edge="1" parent="1" target="3zLw-5_e-Gk6-DkVr-vM-1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="760" y="390" as="sourcePoint" />
-            <mxPoint x="760" y="490" as="targetPoint" />
-            <Array as="points" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="MjSyEAo8ha0iVIPv7yy3-4" value="request_onchain_funds" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" connectable="0" vertex="1" parent="MjSyEAo8ha0iVIPv7yy3-3">
-          <mxGeometry x="-0.55" y="-1" relative="1" as="geometry">
-            <mxPoint x="2" y="1" as="offset" />
-          </mxGeometry>
-        </mxCell>
-      </root>
-    </mxGraphModel>
-  </diagram>
-  <diagram name="Sep-6 - deposit v0.1" id="s9yxVlT1_BEb7k3tPZ03">
-    <mxGraphModel dx="2250" dy="1184" grid="1" gridSize="10" guides="1" tooltips="1" connect="1" arrows="1" fold="1" page="1" pageScale="1" pageWidth="850" pageHeight="1100" math="0" shadow="0">
-      <root>
-        <mxCell id="0" />
-        <mxCell id="1" parent="0" />
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-1" value="" style="rounded=0;whiteSpace=wrap;html=1;strokeWidth=0;glass=0;strokeColor=#c521c8;fontColor=#c521c8;" parent="1" vertex="1">
-          <mxGeometry width="1180" height="793" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-2" value="" style="group" parent="1" vertex="1" connectable="0">
-          <mxGeometry x="620" y="83" width="508" height="163" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-3" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=#82b366;" parent="h22mPx_gXA2pDTQSfuNM-2" vertex="1">
-          <mxGeometry x="240" y="5" width="50" height="20" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-4" value="shortest e2e status flow" style="text;strokeColor=none;align=center;fillColor=none;html=1;verticalAlign=middle;whiteSpace=wrap;rounded=0;" parent="h22mPx_gXA2pDTQSfuNM-2" vertex="1">
-          <mxGeometry x="290" width="140" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-5" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=#d6b656;" parent="h22mPx_gXA2pDTQSfuNM-2" vertex="1">
-          <mxGeometry x="240" y="30" width="50" height="20" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-6" value="optional status, available for business" style="text;strokeColor=none;align=center;fillColor=none;html=1;verticalAlign=middle;whiteSpace=wrap;rounded=0;" parent="h22mPx_gXA2pDTQSfuNM-2" vertex="1">
-          <mxGeometry x="288" y="25" width="220" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-7" value="(&lt;font style=&quot;border-color: var(--border-color); text-align: left;&quot; color=&quot;#66b2ff&quot;&gt;function&lt;/font&gt;&lt;span style=&quot;text-align: left;&quot;&gt;)&lt;/span&gt;" style="rounded=1;whiteSpace=wrap;html=1;fillColor=none;strokeColor=none;" parent="h22mPx_gXA2pDTQSfuNM-2" vertex="1">
-          <mxGeometry x="240" y="55" width="54" height="20" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-8" value="&lt;font style=&quot;border-color: var(--border-color); text-align: left;&quot;&gt;a side effect that will be triggered by an action&lt;br style=&quot;border-color: var(--border-color);&quot;&gt;&lt;/font&gt;if its Anchor is in custody mode" style="text;strokeColor=none;align=left;fillColor=none;html=1;verticalAlign=middle;whiteSpace=wrap;rounded=0;labelPosition=right;verticalLabelPosition=middle;" parent="h22mPx_gXA2pDTQSfuNM-2" vertex="1">
-          <mxGeometry y="55" width="300" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-9" value="" style="endArrow=open;html=1;rounded=0;endFill=0;strokeColor=#9b1599;strokeWidth=2;" parent="h22mPx_gXA2pDTQSfuNM-2" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="240" y="95" as="sourcePoint" />
-            <mxPoint x="290" y="95" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-10" value="&lt;font style=&quot;border-color: var(--border-color);&quot;&gt;actions available for a business that&lt;br style=&quot;border-color: var(--border-color);&quot;&gt;&lt;/font&gt;doesn&#39;t use custody. Can be used to reflect &lt;br&gt;trustline&amp;nbsp;&lt;span style=&quot;&quot;&gt;state on a destination account&lt;/span&gt;" style="text;strokeColor=none;align=left;fillColor=none;html=1;verticalAlign=middle;whiteSpace=wrap;rounded=0;labelPosition=right;verticalLabelPosition=middle;" parent="h22mPx_gXA2pDTQSfuNM-2" vertex="1">
-          <mxGeometry y="95" width="300" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-11" value="" style="endArrow=open;html=1;rounded=0;endFill=0;strokeColor=#BD7000;strokeWidth=2;fillColor=#f0a30a;" parent="h22mPx_gXA2pDTQSfuNM-2" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="240" y="144" as="sourcePoint" />
-            <mxPoint x="290" y="144" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-12" value="&lt;font style=&quot;border-color: var(--border-color); text-align: left;&quot;&gt;actions&amp;nbsp;available for a business that&lt;br style=&quot;border-color: var(--border-color);&quot;&gt;&lt;/font&gt;uses custody service" style="text;strokeColor=none;align=left;fillColor=none;html=1;verticalAlign=middle;whiteSpace=wrap;rounded=0;labelPosition=right;verticalLabelPosition=middle;" parent="h22mPx_gXA2pDTQSfuNM-2" vertex="1">
-          <mxGeometry y="134" width="300" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-13" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.5;exitDx=0;exitDy=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;endArrow=open;endFill=0;jumpStyle=none;strokeWidth=2;" parent="1" source="h22mPx_gXA2pDTQSfuNM-15" target="h22mPx_gXA2pDTQSfuNM-35" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="531" y="118" as="sourcePoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-14" value="notify_customer_info_updated" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="h22mPx_gXA2pDTQSfuNM-13" vertex="1" connectable="0">
-          <mxGeometry x="0.6017" relative="1" as="geometry">
-            <mxPoint y="13" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-15" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;align=left;verticalAlign=top;" parent="1" vertex="1">
-          <mxGeometry x="316" y="83" width="180" height="70" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-16" style="edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.5;exitY=1;exitDx=0;exitDy=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="400" y="343" as="sourcePoint" />
-            <mxPoint x="400" y="465" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-17" value="notify_offchain_funds_received" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="h22mPx_gXA2pDTQSfuNM-16" vertex="1" connectable="0">
-          <mxGeometry x="-0.0219" y="-3" relative="1" as="geometry">
-            <mxPoint x="3" y="-7" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-18" value="(Create custody transaction*)" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];fontColor=#67bbfd;" parent="h22mPx_gXA2pDTQSfuNM-16" vertex="1" connectable="0">
-          <mxGeometry x="0.4595" y="1" relative="1" as="geometry">
-            <mxPoint x="4" y="-22" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-19" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.5;exitDx=0;exitDy=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="h22mPx_gXA2pDTQSfuNM-21" target="h22mPx_gXA2pDTQSfuNM-37" edge="1">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-20" value="notify_offchain_funds_sent" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="h22mPx_gXA2pDTQSfuNM-19" vertex="1" connectable="0">
-          <mxGeometry x="0.7925" relative="1" as="geometry">
-            <mxPoint as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-21" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="316" y="273" width="180" height="70" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-22" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.007;exitY=0.413;exitDx=0;exitDy=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;strokeWidth=2;endArrow=open;endFill=0;exitPerimeter=0;" parent="1" source="h22mPx_gXA2pDTQSfuNM-31" target="h22mPx_gXA2pDTQSfuNM-52" edge="1">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-23" value="notify_refund_pending" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="h22mPx_gXA2pDTQSfuNM-22" vertex="1" connectable="0">
-          <mxGeometry x="0.7751" y="1" relative="1" as="geometry">
-            <mxPoint x="-1" y="-4" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-24" style="rounded=0;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.139;exitY=0.971;exitDx=0;exitDy=0;exitPerimeter=0;strokeWidth=2;endArrow=open;endFill=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;" parent="1" target="h22mPx_gXA2pDTQSfuNM-65" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="331.99" y="661.02" as="targetPoint" />
-            <mxPoint x="333.02" y="532.97" as="sourcePoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-25" value="notify_refund_sent" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="h22mPx_gXA2pDTQSfuNM-24" vertex="1" connectable="0">
-          <mxGeometry x="0.2745" y="-2" relative="1" as="geometry">
-            <mxPoint y="10" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-26" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;entryX=0.577;entryY=0.025;entryDx=0;entryDy=0;entryPerimeter=0;fillColor=#f0a30a;strokeColor=#BD7000;strokeWidth=2;endArrow=open;endFill=0;" parent="1" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="497" y="482" as="sourcePoint" />
-            <mxPoint x="956.0100000000002" y="543.0049999999999" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-27" value="do_stellar_payment" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];fontColor=#e0400b;" parent="h22mPx_gXA2pDTQSfuNM-26" vertex="1" connectable="0">
-          <mxGeometry x="-0.389" y="-1" relative="1" as="geometry">
-            <mxPoint x="-80" y="-1" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-28" value="(Do custody payment)" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];fontColor=#67b4fc;" parent="h22mPx_gXA2pDTQSfuNM-26" vertex="1" connectable="0">
-          <mxGeometry x="0.8848" y="-1" relative="1" as="geometry">
-            <mxPoint y="-5" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-29" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.5;exitDx=0;exitDy=0;entryX=0.25;entryY=0;entryDx=0;entryDy=0;fillColor=#e1d5e7;strokeColor=#9c079c;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="h22mPx_gXA2pDTQSfuNM-31" target="h22mPx_gXA2pDTQSfuNM-59" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <Array as="points">
-              <mxPoint x="627" y="502" />
-            </Array>
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-30" value="request_trust" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];fontColor=#b60fcc;" parent="h22mPx_gXA2pDTQSfuNM-29" vertex="1" connectable="0">
-          <mxGeometry x="-0.1111" relative="1" as="geometry">
-            <mxPoint as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-31" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="316" y="465" width="180" height="70" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-32" value="" style="endArrow=open;html=1;rounded=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;strokeWidth=2;endFill=0;" parent="1" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="399.5" y="153" as="sourcePoint" />
-            <mxPoint x="399.5" y="273" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-33" value="request_offchain_funds" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="h22mPx_gXA2pDTQSfuNM-32" connectable="0" vertex="1">
-          <mxGeometry x="-0.495" relative="1" as="geometry">
-            <mxPoint x="7" y="53" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-34" style="edgeStyle=orthogonalEdgeStyle;orthogonalLoop=1;jettySize=auto;html=1;exitX=0;exitY=0.5;exitDx=0;exitDy=0;rounded=1;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="h22mPx_gXA2pDTQSfuNM-35" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="400" y="213" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-35" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="607" y="156" width="193" height="57" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-36" style="edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;exitX=-0.008;exitY=0.633;exitDx=0;exitDy=0;strokeWidth=2;endArrow=open;endFill=0;exitPerimeter=0;" parent="1" source="h22mPx_gXA2pDTQSfuNM-37" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="400" y="381" as="targetPoint" />
-            <mxPoint x="568" y="381" as="sourcePoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-37" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="608" y="343" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-38" value="SEP6 deposit flow" style="text;html=1;strokeColor=none;fillColor=none;align=center;verticalAlign=middle;whiteSpace=wrap;rounded=0;fontSize=17;fontStyle=1" parent="1" vertex="1">
-          <mxGeometry x="300" y="18" width="250" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-39" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.5;exitY=1;exitDx=0;exitDy=0;entryX=0;entryY=0.25;entryDx=0;entryDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="h22mPx_gXA2pDTQSfuNM-41" target="h22mPx_gXA2pDTQSfuNM-31" edge="1">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-40" value="notify _transaction_recovery" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="h22mPx_gXA2pDTQSfuNM-39" vertex="1" connectable="0">
-          <mxGeometry x="-0.0626" y="-1" relative="1" as="geometry">
-            <mxPoint x="-53" y="-30" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-41" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#f8cecc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="70" y="364" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-42" value="&lt;font&gt;incomplete&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;verticalAlign=top;align=left;fillColor=#6d8764;fontFamily=Tahoma;strokeColor=none;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="320.5" y="89" width="75" height="26" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-43" value="&lt;font face=&quot;Tahoma&quot;&gt;pending_customer_info_update&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#f0a30a;fontColor=#000000;" parent="1" vertex="1">
-          <mxGeometry x="612" y="161" width="178" height="32" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-44" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.5;exitY=1;exitDx=0;exitDy=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="136" y="299" as="sourcePoint" />
-            <mxPoint x="136" y="364" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-45" value="notify_transaction_error&lt;br style=&quot;border-color: var(--border-color);&quot;&gt;notify_transaction_expired" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="h22mPx_gXA2pDTQSfuNM-44" vertex="1" connectable="0">
-          <mxGeometry x="0.1385" y="-3" relative="1" as="geometry">
-            <mxPoint x="2" y="-10" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-46" value="&lt;font style=&quot;&quot; face=&quot;Tahoma&quot;&gt;Any status other than completed or refunded&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#f5f5f5;align=center;verticalAlign=top;fontColor=#333333;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="66" y="236" width="138" height="63" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-47" value="pending_external" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#f0a30a;fontColor=#000000;" parent="1" vertex="1">
-          <mxGeometry x="614" y="349" width="100" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-48" value="pending_user_transfer_start" style="rounded=1;whiteSpace=wrap;html=1;verticalAlign=top;align=left;fillColor=#6d8764;fontFamily=Tahoma;strokeColor=none;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="320" y="277" width="157.5" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-49" value="&lt;font face=&quot;Tahoma&quot;&gt;error/expired&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#e51400;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="78" y="370" width="80" height="25" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-50" value="pending_anchor" style="rounded=1;whiteSpace=wrap;html=1;verticalAlign=top;align=left;fillColor=#6d8764;fontFamily=Tahoma;strokeColor=none;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="320.5" y="470" width="100" height="24" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-51" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.75;exitDx=0;exitDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="331" y="588" as="targetPoint" />
-            <mxPoint x="201" y="588" as="sourcePoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-52" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="70" y="543" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-53" value="&lt;font face=&quot;Tahoma&quot;&gt;pending_external&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#f0a30a;fontColor=#000000;" parent="1" vertex="1">
-          <mxGeometry x="78" y="549" width="100" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-54" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0;exitY=0.5;exitDx=0;exitDy=0;strokeWidth=2;endArrow=open;endFill=0;entryX=0.867;entryY=1.014;entryDx=0;entryDy=0;entryPerimeter=0;strokeColor=#c521c8;" parent="1" target="h22mPx_gXA2pDTQSfuNM-31" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="600" y="578" as="sourcePoint" />
-            <mxPoint x="458.02" y="535.03" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-55" value="notify_trust_set" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];fontColor=#c521c8;" parent="h22mPx_gXA2pDTQSfuNM-54" vertex="1" connectable="0">
-          <mxGeometry x="-0.1472" y="2" relative="1" as="geometry">
-            <mxPoint y="-3" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-56" style="edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.5;exitDx=0;exitDy=0;entryX=0;entryY=0.5;entryDx=0;entryDy=0;fillColor=#f0a30a;strokeColor=#BD7000;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="h22mPx_gXA2pDTQSfuNM-59" target="h22mPx_gXA2pDTQSfuNM-63" edge="1">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-57" value="notify_trust_set" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="h22mPx_gXA2pDTQSfuNM-56" vertex="1" connectable="0">
-          <mxGeometry x="-0.0988" relative="1" as="geometry">
-            <mxPoint as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-58" value="(Do custody payment)" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];fontColor=#84c7ff;" parent="h22mPx_gXA2pDTQSfuNM-56" vertex="1" connectable="0">
-          <mxGeometry x="0.6262" y="-3" relative="1" as="geometry">
-            <mxPoint x="-54" y="10" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-59" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="594" y="543" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-60" value="&lt;font face=&quot;Tahoma&quot;&gt;pending_trust&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#f0a30a;fontColor=#000000;" parent="1" vertex="1">
-          <mxGeometry x="600" y="549" width="100" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-61" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.5;exitY=1;exitDx=0;exitDy=0;strokeWidth=2;fillColor=#f0a30a;strokeColor=#BD7000;endArrow=open;endFill=0;" parent="1" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="450" y="617" as="targetPoint" />
-            <Array as="points">
-              <mxPoint x="949" y="618" />
-            </Array>
-            <mxPoint x="949" y="599" as="sourcePoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-62" value="(Update custody payment)" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];fontColor=#7fcffe;" parent="h22mPx_gXA2pDTQSfuNM-61" vertex="1" connectable="0">
-          <mxGeometry x="0.1115" relative="1" as="geometry">
-            <mxPoint as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-63" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="884" y="544" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-64" value="&lt;font face=&quot;Tahoma&quot;&gt;pending_stellar&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#f0a30a;fontColor=#000000;" parent="1" vertex="1">
-          <mxGeometry x="890" y="550" width="100" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-65" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="265.5" y="680" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-66" value="refunded" style="rounded=1;whiteSpace=wrap;html=1;verticalAlign=top;align=left;fillColor=#6d8764;fontFamily=Tahoma;strokeColor=none;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="272" y="685" width="59.5" height="24" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-67" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="420" y="680" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-68" value="completed" style="rounded=1;whiteSpace=wrap;html=1;verticalAlign=top;align=left;fillColor=#6d8764;fontFamily=Tahoma;strokeColor=none;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="425.5" y="685" width="78.5" height="24" as="geometry" />
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-69" value="" style="endArrow=open;html=1;entryX=0.815;entryY=0.013;entryDx=0;entryDy=0;entryPerimeter=0;strokeWidth=2;fillColor=#f0a30a;strokeColor=#BD7000;endFill=0;rounded=0;" parent="1" target="h22mPx_gXA2pDTQSfuNM-59" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="700" y="483" as="sourcePoint" />
-            <mxPoint x="830" y="383" as="targetPoint" />
-            <Array as="points" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-70" value="(Add custody payment&lt;br&gt;to queue)" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];fontColor=#67c4fd;" parent="h22mPx_gXA2pDTQSfuNM-69" vertex="1" connectable="0">
-          <mxGeometry x="0.0485" relative="1" as="geometry">
-            <mxPoint y="-2" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-71" value="" style="endArrow=open;html=1;rounded=0;strokeColor=#9b1599;strokeWidth=2;endFill=0;" parent="1" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="450" y="535" as="sourcePoint" />
-            <mxPoint x="450" y="620" as="targetPoint" />
-            <Array as="points">
-              <mxPoint x="450" y="583" />
-            </Array>
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-72" value="" style="endArrow=open;html=1;rounded=0;strokeWidth=2;endFill=0;" parent="1" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="450" y="620" as="sourcePoint" />
-            <mxPoint x="450" y="683" as="targetPoint" />
-            <Array as="points">
-              <mxPoint x="450" y="630" />
-            </Array>
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-73" value="notify_onchain_funds_sent" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="h22mPx_gXA2pDTQSfuNM-72" vertex="1" connectable="0">
-          <mxGeometry x="-0.3488" y="-1" relative="1" as="geometry">
-            <mxPoint x="16" y="-4" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-74" value="" style="endArrow=open;html=1;rounded=1;entryX=0.35;entryY=0.986;entryDx=0;entryDy=0;entryPerimeter=0;strokeWidth=2;endFill=0;" parent="1" target="h22mPx_gXA2pDTQSfuNM-31" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="330" y="588" as="sourcePoint" />
-            <mxPoint x="380" y="548" as="targetPoint" />
-            <Array as="points">
-              <mxPoint x="360" y="588" />
-              <mxPoint x="380" y="588" />
-            </Array>
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="h22mPx_gXA2pDTQSfuNM-75" value="notify_refund_sent" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="h22mPx_gXA2pDTQSfuNM-74" vertex="1" connectable="0">
-          <mxGeometry x="0.3847" relative="1" as="geometry">
-            <mxPoint as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="vpoRM2uFi_mH02E-wiQt-1" style="edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0;exitDx=0;exitDy=0;entryX=0.85;entryY=1.035;entryDx=0;entryDy=0;entryPerimeter=0;strokeWidth=2;" parent="1" source="h22mPx_gXA2pDTQSfuNM-31" target="h22mPx_gXA2pDTQSfuNM-35" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <Array as="points">
-              <mxPoint x="771" y="465" />
-            </Array>
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="vpoRM2uFi_mH02E-wiQt-2" value="notify_customer_info_updated" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="vpoRM2uFi_mH02E-wiQt-1" vertex="1" connectable="0">
-          <mxGeometry x="0.8248" y="-1" relative="1" as="geometry">
-            <mxPoint as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="JF5pKwTWw-DiqJtdNlqx-1" value="" style="endArrow=open;html=1;rounded=1;exitX=0.15;exitY=-0.054;exitDx=0;exitDy=0;exitPerimeter=0;entryX=0.877;entryY=-0.022;entryDx=0;entryDy=0;entryPerimeter=0;jumpStyle=arc;strokeWidth=2;endFill=0;" edge="1" parent="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="340.5900000000002" y="465" as="sourcePoint" />
-            <mxPoint x="456.91000000000014" y="464.1199999999999" as="targetPoint" />
-            <Array as="points">
-              <mxPoint x="340.59" y="427" />
-              <mxPoint x="456.59" y="427" />
-              <mxPoint x="456.59" y="445" />
-            </Array>
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="JF5pKwTWw-DiqJtdNlqx-2" value="notify_amounts_updated" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" connectable="0" vertex="1" parent="JF5pKwTWw-DiqJtdNlqx-1">
-          <mxGeometry x="-0.2381" y="1" relative="1" as="geometry">
-            <mxPoint x="-55" y="24" as="offset" />
-          </mxGeometry>
-        </mxCell>
-      </root>
-    </mxGraphModel>
-  </diagram>
-  <diagram name="Sep-6 - withdraw v0.1" id="Wc3wn5-ZP64ZqYri_UEW">
-    <mxGraphModel dx="5943" dy="869" grid="1" gridSize="10" guides="1" tooltips="1" connect="1" arrows="1" fold="1" page="1" pageScale="1" pageWidth="850" pageHeight="1100" math="0" shadow="0">
-      <root>
-        <mxCell id="0" />
-        <mxCell id="1" parent="0" />
-        <mxCell id="oIPxhnnp816XKOSVBjuA-1" value="" style="rounded=0;whiteSpace=wrap;html=1;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="-4204" width="1120.5" height="770" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-2" value="" style="endArrow=open;html=1;rounded=1;exitX=0.5;exitY=1;exitDx=0;exitDy=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;strokeWidth=2;endFill=0;" parent="1" source="oIPxhnnp816XKOSVBjuA-25" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="-3686" y="359.1199999999999" as="sourcePoint" />
-            <mxPoint x="-3686" y="460" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-3" value="notify_onchain_funds_received" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="oIPxhnnp816XKOSVBjuA-2" connectable="0" vertex="1">
-          <mxGeometry x="-0.1542" y="3" relative="1" as="geometry">
-            <mxPoint x="-2" y="-7" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-4" value="" style="endArrow=open;html=1;rounded=1;exitX=0.844;exitY=1.017;exitDx=0;exitDy=0;exitPerimeter=0;strokeWidth=2;endFill=0;" parent="1" source="oIPxhnnp816XKOSVBjuA-47" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="-3626.16" y="500.44000000000005" as="sourcePoint" />
-            <mxPoint x="-3626" y="675.88" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-5" value="notify_offchain_funds_sent" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="oIPxhnnp816XKOSVBjuA-4" connectable="0" vertex="1">
-          <mxGeometry x="-0.5215" y="1" relative="1" as="geometry">
-            <mxPoint x="13" y="91" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-6" value="" style="endArrow=open;html=1;exitX=0.178;exitY=0.983;exitDx=0;exitDy=0;exitPerimeter=0;entryX=0.75;entryY=0;entryDx=0;entryDy=0;strokeWidth=2;rounded=1;endFill=0;" parent="1" source="oIPxhnnp816XKOSVBjuA-47" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="-3745.84" y="501.1199999999999" as="sourcePoint" />
-            <mxPoint x="-3746" y="677.51" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-7" value="notify_refund_sent" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="oIPxhnnp816XKOSVBjuA-6" connectable="0" vertex="1">
-          <mxGeometry x="-0.5594" relative="1" as="geometry">
-            <mxPoint y="95" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-8" value="SEP6 withdrawal flow" style="text;html=1;strokeColor=none;fillColor=none;align=center;verticalAlign=middle;whiteSpace=wrap;rounded=0;fontSize=17;fontStyle=1" parent="1" vertex="1">
-          <mxGeometry x="-3806" width="240" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-9" value="" style="endArrow=open;html=1;rounded=1;entryX=0.5;entryY=1;entryDx=0;entryDy=0;strokeWidth=2;endFill=0;" parent="1" target="oIPxhnnp816XKOSVBjuA-47" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="-3746" y="578" as="sourcePoint" />
-            <mxPoint x="-3686" y="502" as="targetPoint" />
-            <Array as="points">
-              <mxPoint x="-3686" y="578" />
-            </Array>
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-10" value="notify_refund_sent" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="1" connectable="0" vertex="1">
-          <mxGeometry x="-3676.995246557625" y="559.8771268714064" as="geometry">
-            <mxPoint x="-14" y="-6" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-11" value="" style="endArrow=open;html=1;rounded=1;exitX=0.15;exitY=-0.054;exitDx=0;exitDy=0;exitPerimeter=0;entryX=0.877;entryY=-0.022;entryDx=0;entryDy=0;entryPerimeter=0;jumpStyle=arc;strokeWidth=2;endFill=0;" parent="1" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="-3742" y="460.9999999999999" as="sourcePoint" />
-            <mxPoint x="-3625.68" y="460.1199999999999" as="targetPoint" />
-            <Array as="points">
-              <mxPoint x="-3742" y="423" />
-              <mxPoint x="-3626" y="423" />
-              <mxPoint x="-3626" y="441" />
-            </Array>
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-12" value="notify_amounts_updated" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="oIPxhnnp816XKOSVBjuA-11" connectable="0" vertex="1">
-          <mxGeometry x="-0.2381" y="1" relative="1" as="geometry">
-            <mxPoint x="95" y="17" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-13" value="" style="endArrow=open;html=1;rounded=1;exitX=1;exitY=0.25;exitDx=0;exitDy=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;strokeWidth=2;endFill=0;" parent="1" edge="1">
-          <mxGeometry width="50" height="50" relative="1" as="geometry">
-            <mxPoint x="-3632" y="487" as="sourcePoint" />
-            <mxPoint x="-3251.5" y="546.8800000000001" as="targetPoint" />
-            <Array as="points">
-              <mxPoint x="-3252" y="487" />
-            </Array>
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-14" value="notify_offchain_funds_pending" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="oIPxhnnp816XKOSVBjuA-13" connectable="0" vertex="1">
-          <mxGeometry x="-0.1591" y="-2" relative="1" as="geometry">
-            <mxPoint x="64" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-15" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="-3656" y="677.51" width="180" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-16" value="completed" style="rounded=1;whiteSpace=wrap;html=1;verticalAlign=top;align=left;fillColor=#6d8764;fontFamily=Tahoma;strokeColor=none;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="-3646" y="682.51" width="105" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-17" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="-3857" y="678" width="180" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-18" value="refunded" style="rounded=1;whiteSpace=wrap;html=1;verticalAlign=top;align=left;fillColor=#6d8764;fontFamily=Tahoma;strokeColor=none;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="-3847" y="682.51" width="105" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-19" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.5;exitY=1;exitDx=0;exitDy=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="oIPxhnnp816XKOSVBjuA-23" target="oIPxhnnp816XKOSVBjuA-25" edge="1">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-20" value="request_onchain_funds&lt;br style=&quot;border-color: var(--border-color);&quot;&gt;(&lt;font style=&quot;border-color: var(--border-color);&quot; color=&quot;#0066cc&quot;&gt;Create custody transaction*&lt;br style=&quot;border-color: var(--border-color);&quot;&gt;&lt;/font&gt;&lt;font style=&quot;border-color: var(--border-color);&quot; color=&quot;#0066cc&quot;&gt;Generate custody address and memo*&lt;/font&gt;)" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="oIPxhnnp816XKOSVBjuA-19" vertex="1" connectable="0">
-          <mxGeometry x="0.5099" y="1" relative="1" as="geometry">
-            <mxPoint as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-21" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.5;exitDx=0;exitDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="oIPxhnnp816XKOSVBjuA-23" target="oIPxhnnp816XKOSVBjuA-28" edge="1">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-22" value="notify_customer_info_updated" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="oIPxhnnp816XKOSVBjuA-21" vertex="1" connectable="0">
-          <mxGeometry x="0.7931" y="-1" relative="1" as="geometry">
-            <mxPoint as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-23" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="-3777" y="65" width="180" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-24" value="incomplete" style="rounded=1;whiteSpace=wrap;html=1;verticalAlign=top;align=left;fillColor=#6d8764;fontFamily=Tahoma;strokeColor=none;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="-3772" y="75" width="105" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-25" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="-3777" y="309.12" width="180" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-26" value="pending_user_transfer_start" style="rounded=1;whiteSpace=wrap;html=1;verticalAlign=top;align=left;fillColor=#6d8764;fontFamily=Tahoma;strokeColor=none;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="-3772" y="314.12" width="160" height="30.88" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-27" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.5;exitY=1;exitDx=0;exitDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="oIPxhnnp816XKOSVBjuA-28" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="-3686" y="190" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-28" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="-3456" y="150" width="194" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-29" value="&lt;font face=&quot;Tahoma&quot;&gt;pending_customer_info_update&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#f0a30a;fontColor=#000000;" parent="1" vertex="1">
-          <mxGeometry x="-3446" y="160" width="174" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-30" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.5;exitDx=0;exitDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="oIPxhnnp816XKOSVBjuA-32" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="-3746" y="577" as="targetPoint" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-31" value="(&lt;font style=&quot;border-color: var(--border-color);&quot; color=&quot;#0066cc&quot;&gt;Update&lt;/font&gt;&lt;font style=&quot;border-color: var(--border-color); color: rgb(0, 153, 227);&quot;&gt;&amp;nbsp;&lt;/font&gt;&lt;font style=&quot;border-color: var(--border-color);&quot; color=&quot;#0066cc&quot;&gt;custody payment&lt;/font&gt;)" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="oIPxhnnp816XKOSVBjuA-30" vertex="1" connectable="0">
-          <mxGeometry x="-0.0909" y="1" relative="1" as="geometry">
-            <mxPoint as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-32" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="-4036" y="546.88" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-33" value="&lt;font face=&quot;Tahoma&quot;&gt;pending_stellar&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#f0a30a;fontColor=#000000;" parent="1" vertex="1">
-          <mxGeometry x="-4030" y="552.88" width="100" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-34" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.5;exitY=1;exitDx=0;exitDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="-3454" y="630" as="targetPoint" />
-            <mxPoint x="-3253" y="606.8800000000001" as="sourcePoint" />
-            <Array as="points">
-              <mxPoint x="-3253" y="630" />
-            </Array>
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-35" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="-3316" y="546.88" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-36" value="&lt;font face=&quot;Tahoma&quot;&gt;pending_external&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#f0a30a;fontColor=#000000;" parent="1" vertex="1">
-          <mxGeometry x="-3308" y="552.88" width="100" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-37" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;endArrow=open;endFill=0;strokeWidth=2;" parent="1" edge="1">
-          <mxGeometry relative="1" as="geometry">
-            <mxPoint x="-3627" y="630" as="targetPoint" />
-            <mxPoint x="-3452" y="607" as="sourcePoint" />
-            <Array as="points">
-              <mxPoint x="-3452" y="607" />
-              <mxPoint x="-3452" y="630" />
-            </Array>
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-38" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="-3560" y="546.88" width="210" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-39" value="pending_user_transfer_complete" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#f0a30a;fontColor=#000000;" parent="1" vertex="1">
-          <mxGeometry x="-3551" y="552.88" width="190" height="37.12" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-40" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.5;exitY=1;exitDx=0;exitDy=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="oIPxhnnp816XKOSVBjuA-42" target="oIPxhnnp816XKOSVBjuA-51" edge="1">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-41" value="notify_transaction_error&lt;br style=&quot;border-color: var(--border-color);&quot;&gt;notify_transaction_expired" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="oIPxhnnp816XKOSVBjuA-40" vertex="1" connectable="0">
-          <mxGeometry x="0.0099" y="-1" relative="1" as="geometry">
-            <mxPoint as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-42" value="&lt;font style=&quot;&quot; face=&quot;Tahoma&quot;&gt;Any status other than completed or refunded&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#f5f5f5;align=center;verticalAlign=top;fontColor=#333333;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="-4036" y="210" width="130" height="70" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-43" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0;exitY=0.5;exitDx=0;exitDy=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="oIPxhnnp816XKOSVBjuA-47" target="oIPxhnnp816XKOSVBjuA-32" edge="1">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-44" value="do_stellar_refund&lt;br style=&quot;border-color: var(--border-color);&quot;&gt;(&lt;font style=&quot;border-color: var(--border-color);&quot; color=&quot;#0066cc&quot;&gt;Do&amp;nbsp;custody payment&lt;/font&gt;)" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="oIPxhnnp816XKOSVBjuA-43" vertex="1" connectable="0">
-          <mxGeometry x="0.8113" relative="1" as="geometry">
-            <mxPoint y="-13" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-45" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.75;exitDx=0;exitDy=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="oIPxhnnp816XKOSVBjuA-47" target="oIPxhnnp816XKOSVBjuA-38" edge="1">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-46" value="notify_offchain_funds_available" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="oIPxhnnp816XKOSVBjuA-45" vertex="1" connectable="0">
-          <mxGeometry x="0.7403" relative="1" as="geometry">
-            <mxPoint as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="WE7Ez4UL4-nEQ3QiVx3r-1" style="edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;exitX=1;exitY=0.25;exitDx=0;exitDy=0;entryX=0.75;entryY=1;entryDx=0;entryDy=0;strokeWidth=2;" edge="1" parent="1" source="oIPxhnnp816XKOSVBjuA-47" target="oIPxhnnp816XKOSVBjuA-28">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="WE7Ez4UL4-nEQ3QiVx3r-2" value="notify_customer_info_updated" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" vertex="1" connectable="0" parent="WE7Ez4UL4-nEQ3QiVx3r-1">
-          <mxGeometry x="0.4544" y="-1" relative="1" as="geometry">
-            <mxPoint x="1" y="1" as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-47" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=#82b366;" parent="1" vertex="1">
-          <mxGeometry x="-3778" y="461" width="180" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-48" value="pending_anchor" style="rounded=1;whiteSpace=wrap;html=1;verticalAlign=top;align=left;fillColor=#6d8764;fontFamily=Tahoma;strokeColor=none;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="-3773" y="466" width="100" height="30.88" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-49" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;jettySize=auto;html=1;exitX=0.5;exitY=1;exitDx=0;exitDy=0;entryX=0;entryY=0.25;entryDx=0;entryDy=0;strokeWidth=2;endArrow=open;endFill=0;" parent="1" source="oIPxhnnp816XKOSVBjuA-51" target="oIPxhnnp816XKOSVBjuA-47" edge="1">
-          <mxGeometry relative="1" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-50" value="notify_transaction_recovery" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" parent="oIPxhnnp816XKOSVBjuA-49" vertex="1" connectable="0">
-          <mxGeometry x="-0.7592" y="-1" relative="1" as="geometry">
-            <mxPoint as="offset" />
-          </mxGeometry>
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-51" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#f8cecc;strokeColor=none;" parent="1" vertex="1">
-          <mxGeometry x="-4036" y="369.12" width="130" height="60" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-52" value="&lt;font face=&quot;Tahoma&quot;&gt;error/expired&lt;/font&gt;" style="rounded=1;whiteSpace=wrap;html=1;align=left;verticalAlign=top;strokeColor=none;fillColor=#e51400;fontColor=#ffffff;" parent="1" vertex="1">
-          <mxGeometry x="-4028" y="375.12" width="80" height="25" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-53" value="" style="group" parent="1" vertex="1" connectable="0">
-          <mxGeometry x="-4250" y="65" width="508" height="163" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-54" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=none;" parent="oIPxhnnp816XKOSVBjuA-53" vertex="1">
-          <mxGeometry x="74" y="5" width="50" height="20" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-55" value="shortest e2e status flow" style="text;strokeColor=none;align=center;fillColor=none;html=1;verticalAlign=middle;whiteSpace=wrap;rounded=0;" parent="oIPxhnnp816XKOSVBjuA-53" vertex="1">
-          <mxGeometry x="124" width="146" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-56" value="" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=none;" parent="oIPxhnnp816XKOSVBjuA-53" vertex="1">
-          <mxGeometry x="74" y="30" width="50" height="20" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-57" value="optional status, available for business" style="text;strokeColor=none;align=center;fillColor=none;html=1;verticalAlign=middle;whiteSpace=wrap;rounded=0;" parent="oIPxhnnp816XKOSVBjuA-53" vertex="1">
-          <mxGeometry x="122" y="25" width="220" height="30" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-58" value="(&lt;font style=&quot;border-color: var(--border-color); text-align: left;&quot; color=&quot;#66b2ff&quot;&gt;function&lt;/font&gt;&lt;span style=&quot;text-align: left;&quot;&gt;)&lt;/span&gt;" style="rounded=1;whiteSpace=wrap;html=1;fillColor=none;strokeColor=none;" parent="oIPxhnnp816XKOSVBjuA-53" vertex="1">
-          <mxGeometry x="74" y="55" width="54" height="20" as="geometry" />
-        </mxCell>
-        <mxCell id="oIPxhnnp816XKOSVBjuA-59" value="&lt;font style=&quot;border-color: var(--border-color); text-align: left;&quot;&gt;a side effect that will be triggered by an action&lt;/font&gt;" style="text;strokeColor=none;align=left;fillColor=none;html=1;verticalAlign=middle;whiteSpace=wrap;rounded=0;labelPosition=right;verticalLabelPosition=middle;" parent="oIPxhnnp816XKOSVBjuA-53" vertex="1">
-          <mxGeometry x="-142" y="50" width="270" height="30" as="geometry" />
-        </mxCell>
-      </root>
-    </mxGraphModel>
-  </diagram>
-</mxfile>
diff --git a/static/definitions/sequence_diagram_sep24_deposit_job.txt b/static/definitions/sequence_diagram_sep24_deposit_job.txt
deleted file mode 100644
index db8e1418d..000000000
--- a/static/definitions/sequence_diagram_sep24_deposit_job.txt
+++ /dev/null
@@ -1,47 +0,0 @@
-title SEP-24 deposit flow with reconciliation job
-
-participant Client
-participant Bank
-participant Business Server
-participant Platform
-participant Custody Server
-participant DB
-participant Custody Service (Fireblocks)
-participant Stellar
-
-Client->Platform: POST /sep24/transactions/deposit/interactive - \nInitiate SEP24 deposit transaction
-Platform->DB: Create SEP  transaction
-Client<--Platform: SEP transaction ID
-Business Server->Platform: request_offchain_funds RPC request
-Business Server<--Platform: SEP transaction info
-Client->Bank: Send funds
-Business Server->Platform: notify_offchain_funds_received RPC request
-Platform->Custody Server: POST /transactions - Create custody transaction
-Custody Server->DB: Create custody transaction
-Custody Server-->Platform: Void response
-Business Server<--Platform: SEP transaction info
-Business Server->Platform: do_stellar_payment RPC request
-Platform->Custody Server: POST /transactions/{id}/payments - Create transaction payment
-Custody Server->Custody Server: Verify that custody transaction exists
-Custody Server->Custody Service (Fireblocks): POST /v1/transactions - Submit transaction payment
-Custody Service (Fireblocks)->Stellar: Submit transaction
-Custody Server<--Custody Service (Fireblocks): External transaction ID
-Custody Server->DB: Update custody transaction with SUBMITTED status, externalTxId and new updateAt
-Platform<--Custody Server: External transaction ID
-Business Server<--Platform: SEP transaction info
-group Reconciliation Job
-Custody Server->>DB: Get oubound custody transactions for reconciliation \n(SUBMITTED status and non-null externalTxId)
-DB-->Custody Server: Custody transactions
-loop
-Custody Server->Custody Service (Fireblocks): GET /v1/transactions/{id} - Get Fireblocks transaction by id
-Custody Server<--Custody Service (Fireblocks): Fireblocks transaction
-Custody Server->Custody Server: Check whether the status of transaction is observable
-Custody Server->Stellar: Find Stellar transaction and payment by txHash
-Custody Server<--Stellar: Stellar transaction
-Custody Server->DB: Find custody transaction by externalTxId or toAccount and memo
-Custody Server<--DB: Custody transaction
-Custody Server->Custody Server: Validate payment (status, asset type, amount)
-Custody Server->DB: Update custody transaction with COMPLETED status, fromAccount and new updatedAt
-Custody Server->Platform: notify_onchain_funds_sent RPC request
-end
-end
\ No newline at end of file
diff --git a/static/definitions/sequence_diagram_sep24_deposit_webhook.txt b/static/definitions/sequence_diagram_sep24_deposit_webhook.txt
deleted file mode 100644
index 109a6d0a6..000000000
--- a/static/definitions/sequence_diagram_sep24_deposit_webhook.txt
+++ /dev/null
@@ -1,48 +0,0 @@
-title SEP24 deposit flow with webhook
-
-participant Client
-participant Bank
-participant Business Server
-participant Platform
-participant Custody Server
-participant DB
-participant Custody Service (Fireblocks)
-participant Stellar
-
-Client->Platform: POST /sep24/transactions/deposit/interactive - \nInitiate SEP24 deposit transaction
-Platform->DB: Create SEP  transaction
-Client<--Platform: SEP transaction ID
-Business Server->Platform: request_offchain_funds RPC request
-Business Server<--Platform: SEP transaction info
-Client->Bank: Send funds
-Business Server->Platform: notify_offchain_funds_received RPC request
-Platform->Custody Server: POST /transactions - Create custody transaction
-Custody Server->DB: Create custody transaction
-Custody Server-->Platform: Void response
-Platform-->Business Server: SEP transaction info
-Business Server->Platform: do_stellar_payment RPC request
-Platform->Custody Server: POST /transactions/{id}/payments - Create transaction payment
-Custody Server->Custody Server: Verify that custody transaction exists
-Custody Server->Custody Service (Fireblocks): POST /v1/transactions - Submit transaction payment
-Custody Service (Fireblocks)->Stellar: Submit transaction
-Custody Server<--Custody Service (Fireblocks): External transaction ID
-Custody Server->DB: Update custody transaction with SUBMITTED status, externalTxId and new updateAt
-Platform<--Custody Server: External transaction ID
-Business Server<--Platform: SEP transaction info
-Custody Service (Fireblocks)->>Custody Server: POST /webhook - Send SUBMITTED event
-Custody Server->Custody Server: Check whether the event is observable
-Custody Service (Fireblocks)->>Custody Server: POST /webhook - Send QUEUED event
-Custody Server->Custody Server: Check whether the event is observable
-Custody Service (Fireblocks)->>Custody Server: POST /webhook - Send PENDING_SIGNATURE event
-Custody Server->Custody Server: Check whether the event is observable
-Custody Service (Fireblocks)->>Custody Server: POST /webhook - Send BROADCASTING event
-Custody Server->Custody Server: Check whether the event is observable
-Custody Service (Fireblocks)->>Custody Server: POST /webhook - Send CONFIRMING event
-Custody Server->Custody Server: Check whether the event is observable
-Custody Server->Stellar: Find Stellar transaction and payment by txHash
-Custody Server<--Stellar: Stellar transaction
-Custody Server->DB: Find custody transaction by externalTxId
-Custody Server<--DB: Custody transaction
-Custody Server->Custody Server: Validate payment (status, asset type, amount)
-Custody Server->DB: Update custody transaction with COMPLETED status, fromAccount and new updatedAt
-Custody Server->Platform: notify_onchain_funds_sent RPC request
\ No newline at end of file
diff --git a/static/definitions/sequence_diagram_sep24_withdrawal_job.txt b/static/definitions/sequence_diagram_sep24_withdrawal_job.txt
deleted file mode 100644
index 1b07511ee..000000000
--- a/static/definitions/sequence_diagram_sep24_withdrawal_job.txt
+++ /dev/null
@@ -1,44 +0,0 @@
-title SEP-24 withdrawal flow with reconciliation job
-
-participant Client
-participant Bank
-participant Business Server
-participant Platform
-participant Custody Server
-participant DB
-participant Custody Service (Fireblocks)
-participant Stellar
-
-Client->Platform: POST /sep24/transactions/withdrawal/interactive - \nInitiate SEP24 withdrawal transaction
-Platform->DB: Create SEP transaction
-Client<--Platform: SEP transaction ID
-Business Server->Platform: request_onchain_funds RPC request
-Platform->Custody Server: POST /assets/{asset}/addresses - \nGenerate deposit address and memo
-Custody Server -> Custody Service (Fireblocks): POST /v1/vault/accounts/{vaultId}/{asset}/addresses - \nGenerate deposit address and memo
-Custody Server <-- Custody Service (Fireblocks): Deposit address and memo
-Platform<--Custody Server: Deposit address and memo
-Platform->Custody Server: POST /transactions - Create custody transaction
-Custody Server->DB: Create custody transaction
-Custody Server-->Platform: Void response
-Business Server<--Platform: SEP transaction info
-Client->Stellar: Send funds
-group Reconciliation Job
-Custody Server->>DB: Get inbound custody transaction for reconciliation \n(CREATED status and WITHDRAWAL kind)
-Custody Server<--DB: Custody transactions
-Custody Server->Custody Service (Fireblocks): Get Fireblocks transactions by time range
-Custody Service (Fireblocks)-->Custody Server: Fireblocks transactions
-Custody Server->Custody Server: Map custody transactions and Fireblocks transactions
-loop
-Custody Server->Custody Server: Check whether the status of transaction is observable
-Custody Server->Stellar: Find Stellar transaction and payment by txHash
-Custody Server<--Stellar: Stellar transaction
-Custody Server->DB: Find custody transaction by externalTxId or toAccount and memo
-Custody Server<--DB: Custody transaction
-Custody Server->Custody Server: Validate payment (status, asset type, amount)
-Custody Server->DB: Update custody transaction with COMPLETED status, fromAccount, externalTxId and new updatedAt
-Custody Server->Platform: notify_onchain_funds_received RPC request
-end
-end
-Business Server -> Bank: Send funds
-Business Server->Platform: notify_offchain_funds_sent RPC request
-Business Server<--Platform: SEP transaction info
\ No newline at end of file
diff --git a/static/definitions/sequence_diagram_sep24_withdrawal_webhook.txt b/static/definitions/sequence_diagram_sep24_withdrawal_webhook.txt
deleted file mode 100644
index 577707c53..000000000
--- a/static/definitions/sequence_diagram_sep24_withdrawal_webhook.txt
+++ /dev/null
@@ -1,39 +0,0 @@
-title SEP-24 withdrawal flow with webhook
-
-participant Client
-participant Bank
-participant Business Server
-participant Platform
-participant Custody Server
-participant DB
-participant Custody Service (Fireblocks)
-participant Stellar
-
-Client->Platform: POST /sep24/transactions/withdrawal/interactive - \nInitiate SEP24 withdrawal transaction
-Platform->DB: Create SEP transaction
-Client<--Platform: SEP transaction ID
-Business Server->Platform: request_onchain_funds RPC request
-Platform->Custody Server: POST /assets/{asset}/addresses - \nGenerate deposit address and memo
-Custody Server -> Custody Service (Fireblocks): POST /v1/vault/accounts/{vaultId}/{asset}/addresses - \nGenerate deposit address and memo
-Custody Server <-- Custody Service (Fireblocks): Deposit address and memo
-Platform<--Custody Server: Deposit address and memo
-Platform->Custody Server: POST /transactions - Create custody transaction
-Custody Server->DB: Create custody transaction
-Custody Server-->Platform: Void response
-Business Server<--Platform: SEP transaction info
-Client->Stellar: Send funds
-Custody Service (Fireblocks)->>Custody Server: POST /webhook - Send CONFIRMING event
-Custody Server->DB: Find custody transaction by toAccount and memo
-Custody Server<--DB: Custody transaction
-Custody Server->DB: Update custody transaction with externalTxId and new updatedAt
-Custody Server->Custody Server: Check whether the event is observable
-Custody Service (Fireblocks)->>Custody Server: POST /webhook - Send COMPLETED event
-Custody Server->Custody Server: Check whether the event is observable
-Custody Server->Stellar: Find Stellar transaction and payment by txHash
-Custody Server->DB: Find custody transaction by externalTxId or toAccount and memo
-Custody Server->Custody Server: Validate payment (status, asset type, amount)
-Custody Server->DB: Update custody transaction with COMPLETED status, fromAccount, externalTxId and new updatedAt
-Custody Server->Platform: notify_onchain_funds_received RPC request
-Business Server -> Bank: Send funds
-Business Server->Platform: notify_offchain_funds_sent RPC request
-Business Server<--Platform: SEP transaction info
\ No newline at end of file
diff --git a/static/definitions/sequence_diagram_sep31_receive_job.txt b/static/definitions/sequence_diagram_sep31_receive_job.txt
deleted file mode 100644
index d3bc99b24..000000000
--- a/static/definitions/sequence_diagram_sep31_receive_job.txt
+++ /dev/null
@@ -1,43 +0,0 @@
-title SEP-31 receive flow with reconciliation job
-
-participant Client
-participant Bank
-participant Sending Anchor
-participant Business Server
-participant Platform
-participant Custody Server
-participant DB
-participant Custody Service (Fireblocks)
-participant Stellar
-
-Client->Platform: POST /sep31/transactions - \nInitiate SEP31  transaction
-Platform->Custody Server: POST /assets/{asset}/addresses - \nGenerate deposit address and memo
-Custody Server -> Custody Service (Fireblocks): /v1/vault/accounts/{vaultId}/{asset}/addresses - \nGenerate deposit address and memo
-Custody Server <-- Custody Service (Fireblocks): Deposit address and memo
-Platform<--Custody Server: Deposit address and memo
-Platform->DB: Create SEP transaction
-Platform->Custody Server: POST /transactions - Create custody transaction
-Custody Server->DB: Create custody transaction
-Custody Server-->Platform: Void response
-Client<--Platform: SEP transaction ID
-Sending Anchor->Stellar: Send funds
-group Reconciliation Job
-Custody Server->>DB: Get inbound custody transactions for reconciliation \n(CREATED status and RECEIVE kind)
-Custody Server<--DB: Custody transactions
-Custody Server->Custody Service (Fireblocks): Get Fireblocks transactions by time range
-Custody Service (Fireblocks)-->Custody Server: Fireblocks transactions
-Custody Server->Custody Server: Map custody transactions and Fireblocks transactions
-loop
-Custody Server->Custody Server: Check whether the status of transaction is observable
-Custody Server->Stellar: Find Stellar transaction and payment by txHash
-Custody Server<--Stellar: Stellar transaction
-Custody Server->DB: Find custody transaction by externalTxId or toAccount and memo
-Custody Server<--DB: Custody transaction
-Custody Server->Custody Server: Validate payment (status, asset type, amount)
-Custody Server->DB: Update custody transaction with COMPLETED status, fromAccount, externalTxId and new updatedAt
-Custody Server->Platform: notify_onchain_funds_received RPC request
-end
-end
-Business Server -> Bank: Send funds
-Business Server->Platform: notify_offchain_funds_sent RPC request
-Business Server<--Platform: SEP transaction info
\ No newline at end of file
diff --git a/static/definitions/sequence_diagram_sep31_receive_webhook.txt b/static/definitions/sequence_diagram_sep31_receive_webhook.txt
deleted file mode 100644
index 340583e73..000000000
--- a/static/definitions/sequence_diagram_sep31_receive_webhook.txt
+++ /dev/null
@@ -1,40 +0,0 @@
-title SEP-31 receive flow with webhook
-
-participant Client
-participant Bank
-participant Sending Anchor
-participant Business Server
-participant Platform
-participant Custody Server
-participant DB
-participant Custody Service (Fireblocks)
-participant Stellar
-
-Client->Platform: POST /sep31/transactions - \nInitiate SEP31  transaction
-Platform->Custody Server: POST /assets/{asset}/addresses - \nGenerate deposit address and memo
-Custody Server -> Custody Service (Fireblocks): /v1/vault/accounts/{vaultId}/{asset}/addresses - \nGenerate deposit address and memo
-Custody Server <-- Custody Service (Fireblocks): Deposit address and memo
-Platform<--Custody Server: Deposit address and memo
-Platform->DB: Create SEP transaction
-Platform->Custody Server: POST /transactions - Create custody transaction
-Custody Server->DB: Create custody transaction
-Custody Server-->Platform: Void response
-Client<--Platform: SEP transaction ID
-Sending Anchor->Stellar: Send funds
-Custody Service (Fireblocks)->>Custody Server: POST /webhook - Send CONFIRMING event
-Custody Server->DB: Find custody transaction by toAccount and memo
-Custody Server<--DB: Custody transaction
-Custody Server->DB: Update custody transaction with externalTxId and new updatedAt
-Custody Server->Custody Server: Check whether the event is observable
-Custody Service (Fireblocks)->>Custody Server: POST /webhook - Send COMPLETED event
-Custody Server->Custody Server: Check whether the event is observable
-Custody Server->Stellar: Find Stellar transaction and payment by txHash
-Custody Server<--Stellar: Stellar transaction
-Custody Server->DB: Find custody transaction by externalTxId or toAccount and memo
-Custody Server<--DB: Custody transaction
-Custody Server->Custody Server: Validate payment (status, asset type, amount)
-Custody Server->DB: Update custody transaction with COMPLETED status, fromAccount, externalTxId and new updatedAt
-Custody Server->Platform: notify_onchain_funds_received RPC request
-Business Server -> Bank: Send funds
-Business Server->Platform: notify_offchain_funds_sent RPC request
-Business Server<--Platform: SEP transaction info
\ No newline at end of file
diff --git a/static/icons/access-data.png b/static/icons/access-data.png
deleted file mode 100644
index a70eb27b4..000000000
Binary files a/static/icons/access-data.png and /dev/null differ
diff --git a/static/icons/build-applications.png b/static/icons/build-applications.png
deleted file mode 100644
index 3f3d75aae..000000000
Binary files a/static/icons/build-applications.png and /dev/null differ
diff --git a/static/icons/contract.png b/static/icons/contract.png
deleted file mode 100644
index 3d0390bf7..000000000
Binary files a/static/icons/contract.png and /dev/null differ
diff --git a/static/icons/dev-tools.png b/static/icons/dev-tools.png
deleted file mode 100644
index 66fa33df2..000000000
Binary files a/static/icons/dev-tools.png and /dev/null differ
diff --git a/static/icons/issue-assets.png b/static/icons/issue-assets.png
deleted file mode 100644
index c8cea7a5c..000000000
Binary files a/static/icons/issue-assets.png and /dev/null differ
diff --git a/static/icons/sparkle.svg b/static/icons/sparkle.svg
deleted file mode 100644
index 8e908bee4..000000000
--- a/static/icons/sparkle.svg
+++ /dev/null
@@ -1,4 +0,0 @@
-<svg width="16" height="16" viewBox="0 0 16 16" fill="none" xmlns="http://www.w3.org/2000/svg" aria-hidden="true">
-  <path d="M7 2.5Q8 8 13.5 9Q8 10 7 15.5Q6 10 0.5 9Q6 8 7 2.5Z" fill="currentColor"/>
-  <path d="M13 0.5Q13.4 3.1 16 3.5Q13.4 3.9 13 6.5Q12.6 3.9 10 3.5Q12.6 3.1 13 0.5Z" fill="currentColor" opacity="0.75"/>
-</svg>
diff --git a/static/icons/stellar-101.png b/static/icons/stellar-101.png
deleted file mode 100644
index 1fa4aa103..000000000
Binary files a/static/icons/stellar-101.png and /dev/null differ
diff --git a/static/icons/thumbs-down.svg b/static/icons/thumbs-down.svg
deleted file mode 100644
index 3e7bcd6d9..000000000
--- a/static/icons/thumbs-down.svg
+++ /dev/null
@@ -1 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="feather feather-thumbs-down"><path d="M10 15v4a3 3 0 0 0 3 3l4-9V2H5.72a2 2 0 0 0-2 1.7l-1.38 9a2 2 0 0 0 2 2.3zm7-13h2.67A2.31 2.31 0 0 1 22 4v7a2.31 2.31 0 0 1-2.33 2H17"></path></svg>
\ No newline at end of file
diff --git a/static/icons/thumbs-up.svg b/static/icons/thumbs-up.svg
deleted file mode 100644
index 226c44d85..000000000
--- a/static/icons/thumbs-up.svg
+++ /dev/null
@@ -1 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="feather feather-thumbs-up"><path d="M14 9V5a3 3 0 0 0-3-3l-4 9v11h11.28a2 2 0 0 0 2-1.7l1.38-9a2 2 0 0 0-2-2.3zM7 22H4a2 2 0 0 1-2-2v-7a2 2 0 0 1 2-2h3"></path></svg>
\ No newline at end of file
diff --git a/static/img/docusaurus/stellar-logo-dark.svg b/static/img/docusaurus/stellar-logo-dark.svg
deleted file mode 100644
index 9531a23cc..000000000
--- a/static/img/docusaurus/stellar-logo-dark.svg
+++ /dev/null
@@ -1 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 799.93 200" fill="white" stroke="white"><path d="M203 26.16l-28.46 14.5-137.43 70a82.49 82.49 0 0 1-.7-10.69A81.87 81.87 0 0 1 158.2 28.6l16.29-8.3 2.43-1.24A100 100 0 0 0 18.18 100q0 3.82.29 7.61a18.19 18.19 0 0 1-9.88 17.58L0 129.57V150l25.29-12.89 8.19-4.18 8.07-4.11L186.43 55l16.28-8.29 33.65-17.15V9.14zM236.36 50L49.78 145l-16.28 8.31L0 170.38v20.41l33.27-16.95 28.46-14.5 137.57-70.1A83.45 83.45 0 0 1 200 100a81.87 81.87 0 0 1-121.91 71.36l-1 .53-17.66 9A100 100 0 0 0 218.18 100c0-2.57-.1-5.14-.29-7.68a18.2 18.2 0 0 1 9.87-17.58l8.6-4.38zM517.39 64.18c-28.54 0-50.68 21-50.68 54.17 0 30.87 18.25 54.56 51.26 54.56 25.44 0 42.13-14.95 46.79-32.82h-18.25c-4.46 10.29-13 17.28-28.54 17.28-15.34 0-31.65-10.87-32.23-33.39h80.38c2.14-33.2-16.7-59.8-48.73-59.8zm-31.46 44.65c1.56-21 15.92-29.51 31.46-29.51 18.83 0 29.51 14.76 30.09 29.51zM359.26 89.61L343 85.92c-13.25-2.92-23-9.12-23-21.55 0-15.73 19-20.58 29.9-20.58 14 0 30.29 5.63 34.95 21.74h19.23c-5.64-27-28-38.44-53.4-38.44-22.72 0-50.87 11.46-50.87 38.44 0 23.3 19.22 34.18 38.64 38.45l17.55 3.69c17.67 4.08 30.29 9.9 30.29 24.85 0 14-11.84 23.69-32.81 23.69-21.94 0-35.14-10.1-38.83-29.51h-19.46c3.69 28 24.66 46.21 57.86 46.21 28 0 53.59-14.76 53.59-42.14 0-28.34-25.82-36.5-47.38-41.16zM444.58 39.71h-17.67v26.21H410.4V80.1h16.51v64.07c0 21.75 4.66 26.21 24.66 26.21h12.81v-14.75h-8.93c-10.1 0-10.87-2.72-10.87-13.59V80.1h19.8V65.92h-19.8zM794.69 65.34c-13.79.58-24.27 7-29.51 18.83V65.92h-17.29v104.46h17.67v-54.75c0-23.3 8.16-32 24.47-32a63.44 63.44 0 0 1 9.9.78V65.53a52 52 0 0 0-5.24-.19zM730.89 131l.19-24.08c.2-29.71-12.23-43.1-41.55-43.1-20.19 0-40.39 12.62-41.94 35.14h18.25c.78-13 9.13-20.77 23.88-20.77 13.21 0 23.69 6.21 23.69 25.43v2.52c-42.71 4.67-70.67 12-70.67 36.7 0 19.22 16.31 30.1 35.92 30.1 18.64 0 29.32-6 35.72-16.89a114.46 114.46 0 0 0 1.36 14.36h17.86c-2.13-9.93-2.91-21.77-2.71-39.41zm-16.12-4.27c0 24.65-15.72 32.23-32.23 32.23-12.62 0-20.19-6.6-20.19-16.51 0-14.37 20.38-19.22 52.42-22.33zM578.01 29.54h17.67v140.84h-17.67zM613.34 29.54h17.67v140.84h-17.67z"/></svg>
diff --git a/static/img/docusaurus/stellar-logo.svg b/static/img/docusaurus/stellar-logo.svg
deleted file mode 100644
index 5b33add2b..000000000
--- a/static/img/docusaurus/stellar-logo.svg
+++ /dev/null
@@ -1 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 799.93 200"><path d="M203 26.16l-28.46 14.5-137.43 70a82.49 82.49 0 0 1-.7-10.69A81.87 81.87 0 0 1 158.2 28.6l16.29-8.3 2.43-1.24A100 100 0 0 0 18.18 100q0 3.82.29 7.61a18.19 18.19 0 0 1-9.88 17.58L0 129.57V150l25.29-12.89 8.19-4.18 8.07-4.11L186.43 55l16.28-8.29 33.65-17.15V9.14zM236.36 50L49.78 145l-16.28 8.31L0 170.38v20.41l33.27-16.95 28.46-14.5 137.57-70.1A83.45 83.45 0 0 1 200 100a81.87 81.87 0 0 1-121.91 71.36l-1 .53-17.66 9A100 100 0 0 0 218.18 100c0-2.57-.1-5.14-.29-7.68a18.2 18.2 0 0 1 9.87-17.58l8.6-4.38zM517.39 64.18c-28.54 0-50.68 21-50.68 54.17 0 30.87 18.25 54.56 51.26 54.56 25.44 0 42.13-14.95 46.79-32.82h-18.25c-4.46 10.29-13 17.28-28.54 17.28-15.34 0-31.65-10.87-32.23-33.39h80.38c2.14-33.2-16.7-59.8-48.73-59.8zm-31.46 44.65c1.56-21 15.92-29.51 31.46-29.51 18.83 0 29.51 14.76 30.09 29.51zM359.26 89.61L343 85.92c-13.25-2.92-23-9.12-23-21.55 0-15.73 19-20.58 29.9-20.58 14 0 30.29 5.63 34.95 21.74h19.23c-5.64-27-28-38.44-53.4-38.44-22.72 0-50.87 11.46-50.87 38.44 0 23.3 19.22 34.18 38.64 38.45l17.55 3.69c17.67 4.08 30.29 9.9 30.29 24.85 0 14-11.84 23.69-32.81 23.69-21.94 0-35.14-10.1-38.83-29.51h-19.46c3.69 28 24.66 46.21 57.86 46.21 28 0 53.59-14.76 53.59-42.14 0-28.34-25.82-36.5-47.38-41.16zM444.58 39.71h-17.67v26.21H410.4V80.1h16.51v64.07c0 21.75 4.66 26.21 24.66 26.21h12.81v-14.75h-8.93c-10.1 0-10.87-2.72-10.87-13.59V80.1h19.8V65.92h-19.8zM794.69 65.34c-13.79.58-24.27 7-29.51 18.83V65.92h-17.29v104.46h17.67v-54.75c0-23.3 8.16-32 24.47-32a63.44 63.44 0 0 1 9.9.78V65.53a52 52 0 0 0-5.24-.19zM730.89 131l.19-24.08c.2-29.71-12.23-43.1-41.55-43.1-20.19 0-40.39 12.62-41.94 35.14h18.25c.78-13 9.13-20.77 23.88-20.77 13.21 0 23.69 6.21 23.69 25.43v2.52c-42.71 4.67-70.67 12-70.67 36.7 0 19.22 16.31 30.1 35.92 30.1 18.64 0 29.32-6 35.72-16.89a114.46 114.46 0 0 0 1.36 14.36h17.86c-2.13-9.93-2.91-21.77-2.71-39.41zm-16.12-4.27c0 24.65-15.72 32.23-32.23 32.23-12.62 0-20.19-6.6-20.19-16.51 0-14.37 20.38-19.22 52.42-22.33zM578.01 29.54h17.67v140.84h-17.67zM613.34 29.54h17.67v140.84h-17.67z"/></svg>
diff --git a/static/img/github/alert.png b/static/img/github/alert.png
deleted file mode 100644
index 92424c73f..000000000
Binary files a/static/img/github/alert.png and /dev/null differ
diff --git a/static/img/github/code-example.png b/static/img/github/code-example.png
deleted file mode 100644
index d3d767f62..000000000
Binary files a/static/img/github/code-example.png and /dev/null differ
diff --git a/static/img/hubble/hubble_visualization_final.png b/static/img/hubble/hubble_visualization_final.png
deleted file mode 100644
index 146b97e18..000000000
Binary files a/static/img/hubble/hubble_visualization_final.png and /dev/null differ
diff --git a/static/launch/usdt0.html b/static/launch/usdt0.html
deleted file mode 100644
index 55159aaae..000000000
--- a/static/launch/usdt0.html
+++ /dev/null
@@ -1,1089 +0,0 @@
-<!doctype html>
-<html lang="en">
-<head>
-<meta charset="utf-8">
-<meta name="viewport" content="width=device-width, initial-scale=1">
-<title>USDT0 on Stellar</title>
-<script type="application/ld+json">{"@context":"https://schema.org","@type":"FAQPage","url":"https://developers.stellar.org/launch/usdt0","mainEntity":[{"@type":"Question","name":"Is USDT0 the same as USDT?","acceptedAnswer":{"@type":"Answer","text":"No \u2014 it is a separate asset with its own contract, worth the same and backed 1:1 by USDT locked on Ethereum. The practical difference is deposits: a venue that supports USDT will not necessarily accept USDT0 on Stellar. Check your destination lists USDT0 on Stellar specifically before you send."}},{"@type":"Question","name":"Which USDT0 on Stellar is the real one?","acceptedAnswer":{"@type":"Answer","text":"The one issued by GATISXX6BZ6NC7IKQBY37CJD4SOZL3CYZJWXEDG6JVIY4WBS6KXJHN6Q \u2014 check it on Stellar Expert. Asset codes on Stellar are not unique \u2014 anyone can issue an asset called USDT0 \u2014 so identity is the code and the issuer together. Pin that issuer, and confirm the contract you derive from it matches CBSJZEIO5C7KC2SF3MKSNXXJSW5G3VTNBX4ATMKUI3B2MR4JKM4R26YF."}},{"@type":"Question","name":"Why did my USDT0 payment fail with op_no_trust?","acceptedAnswer":{"@type":"Answer","text":"The destination account has no USDT0 trustline, and one must exist before the first payment can land. A wallet often creates it when a user swaps into USDT0 in-app, but a transfer arriving from an exchange or another wallet has no such fallback. If you custody for users, create it during onboarding \u2014 sponsored reserves can cover the reserve."}},{"@type":"Question","name":"How long does a transfer to Stellar take?","acceptedAnswer":{"@type":"Answer","text":"It depends on the chain you send from, not on Stellar. Stellar finalises in 5\u20137 seconds; the wait is the source chain confirming and LayerZero verifying the message. From Polygon it is about a minute. From Ethereum, Arbitrum, Tron and Solana \u2014 the routes carrying most volume \u2014 expect roughly 18\u201321 minutes. A few low-traffic routes take hours. The transfer UI quotes an estimate for your route before you send."}},{"@type":"Question","name":"Why is my transfer slower than I expected?","acceptedAnswer":{"@type":"Answer","text":"Usually because the figure you saw was a network-wide best case rather than your route. Nothing on the Stellar side is the bottleneck. If a transfer runs well past the estimate you were quoted, look up the message on LayerZero Scan, which indexes Stellar as a destination, to see which step it is sitting at. USDT0 lists support contacts for transfers that stall."}},{"@type":"Question","name":"What does it cost to bring USDT0 to Stellar?","acceptedAnswer":{"@type":"Answer","text":"Three separate things, and two different calls report them. USDT0's own protocol fee is zero on most routes and 0.03% where one applies: quote_oft shows it as the gap between amount_sent_ld and amount_received_ld, so read it there rather than trusting a published number. The LayerZero messaging fee is separate and comes back from quote_send, paid in XLM when you send from Stellar \u2014 this is the part that varies most. And on Stellar, ordinary transactions cost a minimum of 100 stroops per operation, which is unrelated to bridging."}},{"@type":"Question","name":"What is the difference between the Open Mesh and the Legacy Mesh?","acceptedAnswer":{"@type":"Answer","text":"On the Open Mesh each chain runs its own OFT contract, and moving between them burns on one side and mints on the other. The Legacy Mesh connects chains where Tether had already deployed native USDT \u2014 Ethereum, Tron, TON, Arbitrum, Solana and Celo \u2014 through a shared non-custodial hub on Arbitrum, so those chains keep their existing USDT contracts rather than migrating."}},{"@type":"Question","name":"Why did I receive slightly less than I sent?","acceptedAnswer":{"@type":"Answer","text":"Rounding, in the last decimal places only. USDT0 on Stellar carries seven decimals; cross-chain transfers normalise to the OFT's six shared decimals. Send 1.2345678 and 1.234567 moves \u2014 the remaining 0.0000008 is floored off as dust and refunded to you before the debit."}},{"@type":"Question","name":"Who can freeze or clawback USDT0 on Stellar?","acceptedAnswer":{"@type":"Answer","text":"The issuer. The asset sets auth_revocable and auth_clawback_enabled, so the issuer can revoke a trustline or clawback a balance. auth_required is not set, so anyone can hold it without approval."}}]}</script>
-<script type="application/ld+json">{"@context":"https://schema.org","@type":"TechArticle","headline":"USDT0 on Stellar","description":"A guide to USDT0 on Stellar: how it arrives, what it unlocks, which partners support it, and how to integrate.","url":"https://developers.stellar.org/launch/usdt0","datePublished":"2026-09-01","inLanguage":"en","about":{"@type":"Thing","name":"USDT0 on Stellar Network"},"publisher":{"@type":"Organization","name":"Stellar Development Foundation","url":"https://stellar.org"}}</script>
-<meta name="description" content="USDT0 is available on the Stellar network. How it arrives, what it unlocks, the contract addresses, and what to check before you build.">
-<meta property="og:type" content="article">
-<meta property="og:title" content="USDT0 on Stellar">
-<meta property="og:description" content="USDT0 is available on the Stellar network. How it arrives, what it unlocks, the contract addresses, and what to check before you build.">
-<meta name="twitter:card" content="summary_large_image">
-<meta property="og:url" content="https://developers.stellar.org/launch/usdt0">
-<link rel="canonical" href="https://developers.stellar.org/launch/usdt0">
-<meta property="og:image" content="https://developers.stellar.org/assets/launch/usdt0-og.png">
-<meta property="og:image:width" content="2400">
-<meta property="og:image:height" content="1260">
-<meta property="og:image:alt" content="USDT0 on Stellar Network">
-<meta name="twitter:image" content="https://developers.stellar.org/assets/launch/usdt0-og.png">
-<!-- the mark the rest of developers.stellar.org already uses, so the tab
-     icon matches every other page on the domain -->
-<link rel="icon" href="/img/docusaurus/favicon-96x96.png">
-<style>
-@font-face{font-family:'IBM Plex Mono';font-style:normal;font-weight:400;font-display:swap;src:url('/assets/launch/fonts/ibm-plex-mono-400-latin-ext.woff2') format('woff2');unicode-range:U+0100-02BA, U+02BD-02C5, U+02C7-02CC, U+02CE-02D7, U+02DD-02FF, U+0304, U+0308, U+0329, U+1D00-1DBF, U+1E00-1E9F, U+1EF2-1EFF, U+2020, U+20A0-20AB, U+20AD-20C0, U+2113, U+2C60-2C7F, U+A720-A7FF}
-@font-face{font-family:'IBM Plex Mono';font-style:normal;font-weight:400;font-display:swap;src:url('/assets/launch/fonts/ibm-plex-mono-400-latin.woff2') format('woff2');unicode-range:U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329, U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD}
-@font-face{font-family:'IBM Plex Mono';font-style:normal;font-weight:500;font-display:swap;src:url('/assets/launch/fonts/ibm-plex-mono-500-latin-ext.woff2') format('woff2');unicode-range:U+0100-02BA, U+02BD-02C5, U+02C7-02CC, U+02CE-02D7, U+02DD-02FF, U+0304, U+0308, U+0329, U+1D00-1DBF, U+1E00-1E9F, U+1EF2-1EFF, U+2020, U+20A0-20AB, U+20AD-20C0, U+2113, U+2C60-2C7F, U+A720-A7FF}
-@font-face{font-family:'IBM Plex Mono';font-style:normal;font-weight:500;font-display:swap;src:url('/assets/launch/fonts/ibm-plex-mono-500-latin.woff2') format('woff2');unicode-range:U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329, U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD}
-@font-face{font-family:'Inter';font-style:normal;font-weight:400 600;font-display:swap;src:url('/assets/launch/fonts/inter-latin-ext.woff2') format('woff2');unicode-range:U+0100-02BA, U+02BD-02C5, U+02C7-02CC, U+02CE-02D7, U+02DD-02FF, U+0304, U+0308, U+0329, U+1D00-1DBF, U+1E00-1E9F, U+1EF2-1EFF, U+2020, U+20A0-20AB, U+20AD-20C0, U+2113, U+2C60-2C7F, U+A720-A7FF}
-@font-face{font-family:'Inter';font-style:normal;font-weight:400 600;font-display:swap;src:url('/assets/launch/fonts/inter-latin.woff2') format('woff2');unicode-range:U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329, U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD}
-</style>
-
-<style>
-:root{
-  --paper:#FFFFFF; --paper-2:#F9F9F9; --paper-3:#F2F2F2;
-  --ink:#0F0F0F; --ink-2:#4A4A4A; --ink-3:#6B6B6B;
-  --rule:#D8D8D8; --rule-2:#E6E6E6;
-  --accent:#FDDA24; --accent-soft:#FDDA2440;
-  --accent-ink:#7A5C00; --on-accent:#0F0F0F;
-}
-@media (prefers-color-scheme: dark){
-  :root:not([data-theme="light"]){
-    --paper:#0F0F0F; --paper-2:#191919; --paper-3:#080808;
-    --ink:#F5F5F0; --ink-2:#B8B8B0; --ink-3:#8E8E86;
-    --rule:#474747; --rule-2:#333333;
-    --accent:#FDDA24; --accent-soft:#FDDA2422;
-    --accent-ink:#FDDA24; --on-accent:#0F0F0F;
-  }
-}
-:root[data-theme="dark"]{
-  --paper:#0F0F0F; --paper-2:#191919; --paper-3:#080808;
-  --ink:#F5F5F0; --ink-2:#B8B8B0; --ink-3:#8E8E86;
-  --rule:#474747; --rule-2:#333333;
-  --accent:#FDDA24; --accent-soft:#FDDA2422;
-  --accent-ink:#FDDA24; --on-accent:#0F0F0F;
-}
-
-*{box-sizing:border-box}
-body{
-  margin:0; background:var(--paper); color:var(--ink);
-  font-family:"Inter","Helvetica Neue",Arial,sans-serif;
-  font-size:15px; line-height:1.6; -webkit-font-smoothing:antialiased;
-}
-.sheet{max-width:1300px;margin:0 auto;padding:22px 24px 64px}
-
-/* ---------- header ---------- */
-/* sticky, so the section markers stay useful once you have scrolled past them */
-.top{
-  position:sticky;top:0;z-index:20;background:var(--paper);
-  display:flex;align-items:center;justify-content:space-between;gap:20px;
-  font-family:"IBM Plex Mono",ui-monospace,monospace;
-  font-size:11px;letter-spacing:.14em;text-transform:uppercase;color:var(--ink-2);
-  border-bottom:1px solid var(--rule);padding:12px 0 10px;
-}
-.secnav{display:flex;gap:5px;align-items:center}
-/* a way back into the docs, sitting with the section markers rather than
-   competing with the page title */
-.top-r{display:flex;align-items:center;gap:18px}
-.toplink{color:var(--ink-2);text-decoration:none;border-bottom:1px solid var(--rule);
-         letter-spacing:inherit;white-space:nowrap}
-.toplink:hover{color:var(--accent-ink);border-bottom-color:var(--accent-ink)}
-.toplink:focus-visible{outline:2px solid var(--accent-ink);outline-offset:3px}
-@media (max-width:560px){ .toplink{display:none} }
-.tick{
-  width:11px;height:11px;border:1px solid var(--ink-2);
-  background:transparent;display:block;
-  transition:background .15s ease,border-color .15s ease;
-}
-.tick:hover{border-color:var(--accent-ink);background:var(--accent-soft)}
-.tick[aria-current="true"]{background:var(--accent);border-color:var(--accent-ink)}
-.tick:focus-visible{outline:2px solid var(--accent-ink);outline-offset:3px}
-/* the tick stays 11px to look at and gets an invisible target around it. The
-   horizontal reach is tied to the gap so neighbours never overlap: 15px wide
-   on a mouse, and on touch the gap opens up so the target clears the 24x24
-   minimum. Vertical reach is free either way. */
-.tick{position:relative}
-.tick::after{content:"";position:absolute;inset:-16px -2px}
-@media (pointer:coarse){
-  .secnav{gap:16px}
-  .tick::after{inset:-16px -8px}
-}
-/* the wider touch gap costs the header its single line at phone widths, so the
-   label tightens to compensate rather than wrapping */
-@media (max-width:430px){ .top{font-size:10px;letter-spacing:.10em} }
-
-/* anchor jumps must clear the sticky bar */
-figure[id],section[id]{scroll-margin-top:64px}
-html{scroll-behavior:smooth}
-@media (prefers-reduced-motion: reduce){html{scroll-behavior:auto}}
-
-/* Inter needs display tuning the condensed face did not: more negative
-   tracking, and a little more leading for its taller x-height and longer
-   descenders. The accent is a block so the color change lands on the line
-   break instead of stranding a word at the end of line one. */
-h1{
-  font-family:"Inter","Helvetica Neue",Arial,sans-serif;
-  font-weight:600;font-size:clamp(34px,5.4vw,58px);line-height:1.06;
-  letter-spacing:-.03em;margin:26px 0 10px;max-width:24ch;text-wrap:balance;
-}
-h1 em{display:block;font-style:normal;color:var(--accent-ink)}
-.deck{max-width:62ch;color:var(--ink-2);font-size:17px;margin:0 0 8px}
-.deck strong{color:var(--ink);font-weight:500}
-
-/* ---------- figure chrome ---------- */
-figure{margin:34px 0 0;border:1px solid var(--rule);background:var(--paper-2)}
-.fig-head{
-  display:flex;justify-content:space-between;gap:16px;flex-wrap:wrap;
-  border-bottom:1px solid var(--rule);padding:9px 14px;
-  font-family:"IBM Plex Mono",ui-monospace,monospace;font-size:10.5px;
-  letter-spacing:.13em;text-transform:uppercase;color:var(--ink-2);
-}
-.fig-body{padding:16px 14px;overflow-x:auto}
-.fig-body>svg{min-width:620px}
-figcaption{
-  border-top:1px solid var(--rule);padding:10px 14px;
-  font-size:13.5px;color:var(--ink-2);
-}
-svg{display:block;max-width:100%;height:auto}
-.n-box{fill:var(--paper-2);stroke:currentColor;stroke-width:1}
-.n-box.alt{fill:var(--paper-3)}
-.n-box.hot{stroke:var(--accent-ink);stroke-width:1.6;fill:var(--accent-soft)}
-.n-t{font-family:"Inter","Helvetica Neue",Arial,sans-serif;font-weight:600;font-size:14px;fill:currentColor}
-.n-t.hot{fill:var(--accent-ink)}
-.n-s{font-family:"IBM Plex Mono",monospace;font-size:10px;fill:var(--ink);letter-spacing:.04em}
-.edge{stroke:currentColor;stroke-width:1;fill:none}
-.edge.dash{stroke-dasharray:5 4;stroke:var(--ink-3)}
-/* One 12.5s cycle tells the whole story once: a packet leaves Ethereum, splits
-   at the fork, both halves land together, the far-chain half climbs into the
-   Stellar OFT, and one packet carries on. Every leg runs at the same ~55px/s —
-   each duration is that path's measured length over that rate — so the pacing
-   is uniform even though the legs are different lengths. Boxes light on arrival. */
-.pkt{fill:var(--accent-ink);opacity:0}
-.lit{fill:var(--accent-soft);stroke:var(--accent-ink);stroke-width:1.6;opacity:0}
-.pkt.pTrunk{offset-path:path("M 184 201 H 232");animation:pTrunk 12.5s linear infinite}
-@keyframes pTrunk{0%,0.00%{offset-distance:0%;opacity:0}0.50%{opacity:1}6.70%{opacity:1}7.20%,100%{offset-distance:100%;opacity:0}}
-.pkt.pUp{offset-path:path("M 232 201 V 110 H 286");animation:pUp 12.5s linear infinite}
-@keyframes pUp{0%,7.20%{offset-distance:0%;opacity:0}8.66%{opacity:1}26.54%{opacity:1}28.00%,100%{offset-distance:100%;opacity:0}}
-.pkt.pDown{offset-path:path("M 232 201 V 292 H 286");animation:pDown 12.5s linear infinite}
-@keyframes pDown{0%,7.20%{offset-distance:0%;opacity:0}8.66%{opacity:1}26.54%{opacity:1}28.00%,100%{offset-distance:100%;opacity:0}}
-.pkt.pClimb{offset-path:path("M 384 254 V 168");animation:pClimb 12.5s linear infinite}
-@keyframes pClimb{0%,32.80%{offset-distance:0%;opacity:0}33.86%{opacity:1}46.94%{opacity:1}48.00%,100%{offset-distance:100%;opacity:0}}
-.pkt.pMint{offset-path:path("M 478 110 H 528 V 201 H 574");animation:pMint 12.5s linear infinite}
-@keyframes pMint{0%,52.00%{offset-distance:0%;opacity:0}53.90%{opacity:1}77.30%{opacity:1}79.20%,100%{offset-distance:100%;opacity:0}}
-.pkt.pUse1{offset-path:path("M 764 171 H 812");animation:pUse1 12.5s linear infinite}
-@keyframes pUse1{0%,82.40%{offset-distance:0%;opacity:0}82.90%{opacity:1}89.10%{opacity:1}89.60%,100%{offset-distance:100%;opacity:0}}
-.pkt.pUse2{offset-path:path("M 764 201 H 812");animation:pUse2 12.5s linear infinite}
-@keyframes pUse2{0%,82.40%{offset-distance:0%;opacity:0}82.90%{opacity:1}89.10%{opacity:1}89.60%,100%{offset-distance:100%;opacity:0}}
-.pkt.pUse3{offset-path:path("M 764 231 H 812");animation:pUse3 12.5s linear infinite}
-@keyframes pUse3{0%,82.40%{offset-distance:0%;opacity:0}82.90%{opacity:1}89.10%{opacity:1}89.60%,100%{offset-distance:100%;opacity:0}}
-.lit.lEth{animation:lEth 12.5s linear infinite}
-@keyframes lEth{0%{opacity:0}0.00%{opacity:0}1.20%{opacity:1}4.40%{opacity:0}100%{opacity:0}}
-.lit.lOft{animation:lOft 12.5s linear infinite}
-@keyframes lOft{0%{opacity:0}28.00%{opacity:0}29.20%{opacity:1}32.40%{opacity:0}48.00%{opacity:0}49.20%{opacity:1}52.40%{opacity:0}100%{opacity:0}}
-.lit.lChain{animation:lChain 12.5s linear infinite}
-@keyframes lChain{0%{opacity:0}28.00%{opacity:0}29.20%{opacity:1}32.40%{opacity:0}100%{opacity:0}}
-.lit.lHot{animation:lHot 12.5s linear infinite}
-@keyframes lHot{0%{opacity:0}79.20%{opacity:0}80.40%{opacity:1}83.60%{opacity:0}100%{opacity:0}}
-.lit.lUse{animation:lUse 12.5s linear infinite}
-@keyframes lUse{0%{opacity:0}89.60%{opacity:0}90.80%{opacity:1}94.00%{opacity:0}100%{opacity:0}}
-@media (prefers-reduced-motion: reduce){.pkt,.lit{animation:none;opacity:0}}
-
-/* ---------- fig 2: the USDT0 folder ---------- */
-/* One folder — USDT0 — with five layers stacked behind its cover, offset
-   down-left so every name stays readable. Clicking a name swaps the title and
-   description on the left. Percentage geometry, so the stack scales instead of
-   scrolling. */
-.fig-files{padding:0 40px 30px}
-.folder-fig{display:flex;gap:34px;align-items:flex-start;justify-content:center;padding:26px 40px 30px}
-
-.desc{flex:1 1 0;min-width:0;max-width:620px;display:flex;flex-direction:column;gap:12px}
-.d-eyebrow{
-  font-family:"IBM Plex Mono",monospace;font-size:10px;letter-spacing:.16em;
-  text-transform:uppercase;color:var(--accent-ink);
-}
-.d-head{
-  font-family:"Inter","Helvetica Neue",Arial,sans-serif;font-weight:600;
-  font-size:clamp(24px,2.6vw,36px);line-height:1.1;margin:0;
-  letter-spacing:-.022em;text-wrap:balance;color:var(--ink);
-}
-.d-claim{margin:0;font-size:15.5px;color:var(--ink);max-width:56ch}
-.d-back{
-  align-self:flex-start;appearance:none;background:none;border:0;padding:4px 0 0;
-  font-family:"IBM Plex Mono",monospace;font-size:10px;letter-spacing:.12em;
-  text-transform:uppercase;color:var(--ink-3);cursor:pointer;
-  border-bottom:1px solid var(--rule);
-}
-.d-back:hover{color:var(--accent-ink);border-bottom-color:var(--accent-ink)}
-.d-back:focus-visible{outline:2px solid var(--accent-ink);outline-offset:3px}
-dl{margin:2px 0 0;display:flex;flex-direction:column;gap:12px;
-   border-top:1px solid var(--rule);padding-top:14px}
-dt{
-  font-family:"IBM Plex Mono",monospace;font-size:9.5px;letter-spacing:.14em;
-  text-transform:uppercase;color:var(--ink-2);margin-bottom:3px;
-}
-dd{margin:0;font-size:14.5px;color:var(--ink-2);max-width:64ch}
-dd code{
-  font-family:"IBM Plex Mono",monospace;font-size:12.5px;
-  background:var(--paper-3);border:1px solid var(--rule-2);padding:.5px 4px;color:var(--ink);
-}
-.caveat{
-  font-size:13px;color:var(--ink-2);border-left:2px solid var(--rule);
-  padding-left:11px;margin:0;
-}
-.caveat b{color:var(--ink);font-weight:500}
-
-/* source links: quiet by default, accent on hover — a claim you can check */
-dd a,.id-note a,.only p a,.spec dd a,.dep-note a,.ncopy a,figcaption a{
-  color:inherit;text-decoration:none;
-  border-bottom:1px solid var(--rule);
-}
-dd a:hover,.id-note a:hover,.only p a:hover,.spec dd a:hover,.dep-note a:hover,.ncopy a:hover,
-figcaption a:hover{
-  color:var(--accent-ink);border-bottom-color:var(--accent-ink);
-}
-dd a:focus-visible,.id-note a:focus-visible,.only p a:focus-visible,.spec dd a:focus-visible,
-.dep-note a:focus-visible,.ncopy a:focus-visible,figcaption a:focus-visible{
-  outline:2px solid var(--accent-ink);outline-offset:2px;border-bottom-color:transparent;
-}
-dd a code,.dep-note a code,.ncopy a code{border-bottom:0}
-.sources{
-  margin-top:26px;border-top:1px solid var(--rule);padding-top:10px;
-  display:flex;gap:18px;align-items:baseline;flex-wrap:wrap;
-  font-family:"IBM Plex Mono",monospace;font-size:10.5px;letter-spacing:.13em;
-  text-transform:uppercase;color:var(--ink-3);
-}
-.sources b{font-weight:400;color:var(--ink-3);margin-right:4px}
-.sources a{color:var(--ink-2);text-decoration:none;border-bottom:1px solid var(--rule)}
-.sources a:hover{color:var(--accent-ink);border-bottom-color:var(--accent-ink)}
-.sources a:focus-visible{outline:2px solid var(--accent-ink);outline-offset:3px}
-/* ---- questions: collapsed by default, but the answers stay in the DOM ---- */
-.faq{border-bottom:1px solid var(--rule)}
-.faq:last-child{border-bottom:0}
-
-.faq summary{
-  display:flex;gap:14px;align-items:baseline;list-style:none;cursor:pointer;
-  padding:11px 28px 11px 0;position:relative;
-}
-.faq summary::-webkit-details-marker{display:none}
-.faq summary::after{
-  content:"+";position:absolute;right:8px;top:10px;line-height:1;
-  font-family:"IBM Plex Mono",monospace;font-size:13px;color:var(--ink-3);
-}
-.faq[open] summary::after{content:"\2212"}
-.faq summary:hover .fq{color:var(--accent-ink)}
-.faq summary:focus-visible{outline:2px solid var(--accent-ink);outline-offset:-2px}
-.fq{font-weight:500}
-.fq code,.fa code{font-size:.92em}
-.fa{padding:0 28px 16px 0;max-width:78ch}
-.fa .ncopy{margin:0}
-@media (max-width:720px){
-  .faq summary{padding-right:26px}
-}
-.foot{margin-top:14px}
-
-/* ---- the stack: folders in a folder ---- */
-/* six slots, back to front. Each folder's tab sits on the left of its top edge,
-   and the down-left offset keeps every tab uncovered. */
-.stackwrap{flex:0 0 clamp(250px,42%,520px);min-width:0;
-  /* the stack is shorter than the description beside it, so center it
-     rather than let the leftover height pool at the bottom of the panel */
-  align-self:center}
-.stack{position:relative;width:100%;aspect-ratio:var(--ar,1.316);container-type:inline-size}
-.file{
-  position:absolute;width:var(--fw,70.59%);height:var(--fh,61.29%);
-  appearance:none;background:none;border:0;padding:0;margin:0;
-  text-align:left;
-  transition:transform .16s ease;
-}
-.fo{position:absolute;inset:0;width:100%;height:100%;shape-rendering:geometricPrecision}
-/* fill and outline are separate paths: the tab is painted between them, so
-   the silhouette's stroke is drawn last and never gets covered. */
-.fo-body{fill:var(--paper)}
-.fo-tab{fill:none;transition:fill .16s ease}
-.fo-edge{
-  fill:none;stroke:var(--ink-2);stroke-width:1.5;
-  vector-effect:non-scaling-stroke;stroke-linejoin:round;
-  transition:stroke .16s ease,stroke-width .16s ease;
-}
-.fname{
-  position:absolute;left:0;top:0;width:40.97%;height:12.63%;
-  padding:0 5% 0 5.5%;display:flex;align-items:center;
-  font-family:"IBM Plex Mono",monospace;
-  font-size:clamp(6.5px,2.37cqw,11px);letter-spacing:.05em;color:var(--ink-2);
-  white-space:nowrap;overflow:hidden;text-overflow:ellipsis;
-  transition:color .16s ease;
-}
-.file:hover .fo-edge{stroke:var(--accent-ink)}
-.file:hover .fname{color:var(--accent-ink)}
-.file:focus-visible{outline:none}
-.file:focus-visible .fo-edge{stroke:var(--accent-ink);stroke-width:2}
-.file:focus-visible .fname{color:var(--accent-ink)}
-.file[aria-selected="true"] .fo-edge{stroke:var(--accent-ink);stroke-width:2}
-.file[aria-selected="true"] .fo-tab{fill:var(--accent)}
-.file[aria-selected="true"] .fname{color:var(--on-accent)}
-.file[aria-selected="true"]:not(.cover){transform:translate(-3%,2.5%)}
-
-/* the cover: the folder these sit in */
-.cover .fo-body{
-  fill:var(--paper);
-}
-.cover .fo-edge{stroke:var(--accent-ink);stroke-width:2}
-.cover .fo-tint{fill:var(--accent);opacity:.10}
-.cover .fname{color:var(--accent-ink)}
-.cover[aria-selected="true"] .fo-tab{fill:var(--accent)}
-.cover[aria-selected="true"] .fname{color:var(--on-accent)}
-.cover-body{position:absolute;left:5.5%;right:8%;top:24%}
-.cover-name{
-  display:block;font-family:"Inter","Helvetica Neue",Arial,sans-serif;font-weight:600;
-  font-size:clamp(15px,6.1cqw,29px);line-height:1.1;color:var(--accent-ink);
-  letter-spacing:-.01em;
-}
-.cover-sub{
-  display:block;margin-top:7%;font-family:"IBM Plex Mono",monospace;
-  font-size:clamp(7px,2.46cqw,12px);line-height:1.7;color:var(--ink-2);
-}
-
-/* ---- narrow: stack above, description below ---- */
-@media (max-width:820px){
-  .folder-fig{flex-direction:column;gap:22px;padding:20px 14px 24px}
-  .stackwrap{flex:0 0 auto;width:100%;max-width:380px;align-self:flex-start}
-  .desc{width:100%;max-width:none}
-  .d-claim,dd{max-width:none}
-}
-
-
-/* ---- access lab: five files shown at once, as benefits under the feature ---- */
-.files{
-  border-top:1px solid var(--rule);
-  display:grid; grid-template-columns:repeat(var(--cols,5),minmax(0,1fr));
-}
-.fcol{padding:18px 20px 4px; border-right:1px solid var(--rule);
-  display:flex; flex-direction:column}
-.fcol:last-child{border-right:0}
-.fcol:first-child{padding-left:0}
-.ftag{
-  font-family:"IBM Plex Mono",monospace; font-size:9.5px; letter-spacing:.14em;
-  text-transform:uppercase; color:var(--accent-ink); margin-bottom:7px;
-}
-.fhead{
-  font-family:"Inter","Helvetica Neue",Arial,sans-serif; font-weight:600;
-  font-size:19px; line-height:1.12; letter-spacing:-.01em; color:var(--ink); margin:0 0 9px;
-}
-.fcopy{margin:0 0 14px; font-size:13.5px; line-height:1.5; color:var(--ink-2)}
-@media (max-width:1000px){
-  .files{grid-template-columns:repeat(2,minmax(0,1fr))}
-  .fcol{border-bottom:1px solid var(--rule); padding-left:20px}
-  .fcol:first-child{padding-left:20px}
-  .fcol:nth-child(2n){border-right:0}
-  .fcol:nth-last-child(-n+2){border-bottom:0}
-}
-@media (max-width:620px){
-  .files{grid-template-columns:minmax(0,1fr)}
-  .fcol{border-right:0}
-  .fcol:last-child{border-bottom:0}
-}
-
-.dep-note b{color:var(--ink);font-weight:500}
-.dep-note{
-  border-top:1px solid var(--rule); padding:12px 20px;
-  font-size:13.5px; line-height:1.55; color:var(--ink-2);
-}
-.notes-sec{margin:34px 0 0;border:1px solid var(--rule);background:var(--paper-2)}
-.notes-body{padding:20px 20px 22px;display:flex;flex-direction:column;gap:18px}
-.notes{display:grid; grid-template-columns:repeat(2,minmax(0,1fr)); gap:18px 40px}
-.note{display:flex; gap:12px}
-.ntag{
-  flex:0 0 82px; font-family:"IBM Plex Mono",monospace; font-size:9.5px;
-  letter-spacing:.14em; text-transform:uppercase; color:var(--ink-3); padding-top:3px;
-}
-.ncopy{margin:0; font-size:13px; line-height:1.55; color:var(--ink-2)}
-.ncopy b{color:var(--ink);font-weight:500}
-@media (max-width:820px){ .notes{grid-template-columns:minmax(0,1fr)} }
-/* below this the two-column note squeezed its copy to about 25 characters a
-   line, so the tag sits above the copy instead of beside it */
-@media (max-width:560px){
-  .note{flex-direction:column; gap:4px}
-  .ntag{flex:0 0 auto; padding-top:0}
-}
-
-/* ---------- day one ---------- */
-.dayone{margin:34px 0 0;border:1px solid var(--rule);background:var(--paper-2)}
-.d1-body{padding:20px 20px 22px;display:flex;flex-direction:column;gap:20px}
-.d1-lead{margin:0;font-size:15.5px;color:var(--ink);max-width:64ch}
-.venues{display:grid;grid-template-columns:repeat(auto-fit,minmax(220px,1fr));gap:0;
-  border:1px solid var(--rule);background:var(--paper)}
-.venue{padding:15px 16px;border-right:1px solid var(--rule)}
-.venue:last-child{border-right:0}
-@media (max-width:720px){
-  .venue{border-right:0;border-bottom:1px solid var(--rule)}
-  .venue:last-child{border-bottom:0}
-}
-.venue h3{
-  margin:0 0 10px;font-family:"IBM Plex Mono",monospace;font-size:9.5px;
-  letter-spacing:.14em;text-transform:uppercase;color:var(--ink-3);font-weight:400;
-}
-.venue ul{margin:0;padding:0;list-style:none;display:flex;flex-wrap:wrap;gap:6px}
-.venue li{
-  font-family:"IBM Plex Mono",monospace;font-size:11.5px;color:var(--ink);
-  border:1px solid var(--rule);background:var(--paper-2);padding:4px 8px;
-}
-.venue p{margin:10px 0 0;font-size:12.5px;color:var(--ink-2)}
-
-
-/* ---------- deploy section ---------- */
-.deploy{margin:34px 0 0;border:1px solid var(--rule);background:var(--paper-2)}
-.dep-head h2,.fig-head h2{font:inherit;letter-spacing:inherit;margin:0}
-.dep-head{
-  display:flex;justify-content:space-between;gap:16px;flex-wrap:wrap;align-items:center;
-  border-bottom:1px solid var(--rule);padding:9px 14px;
-  font-family:"IBM Plex Mono",ui-monospace,monospace;font-size:10.5px;
-  letter-spacing:.13em;text-transform:uppercase;color:var(--ink-2);
-}
-.live{
-  display:inline-flex;align-items:center;gap:6px;
-  color:var(--accent-ink);letter-spacing:.13em;
-}
-.live::before{
-  content:"";width:7px;height:7px;border-radius:50%;background:var(--accent-ink);
-}
-.dep-body{padding:20px 20px 22px;display:flex;flex-direction:column;gap:18px}
-.dep-lead{margin:0;font-size:15.5px;color:var(--ink);max-width:62ch}
-.dep-lead strong{font-weight:500}
-.dep-link{
-  align-self:flex-start;font-family:"IBM Plex Mono",monospace;font-size:11px;
-  letter-spacing:.06em;color:var(--accent-ink);text-decoration:none;
-  border-bottom:1px solid var(--accent-ink);padding-bottom:1px;
-}
-.dep-link:hover{color:var(--ink)}
-.dep-link:focus-visible{outline:2px solid var(--accent-ink);outline-offset:3px}
-
-.ids{display:flex;flex-direction:column;gap:0;border:1px solid var(--rule);background:var(--paper)}
-.id-row{
-  display:grid;grid-template-columns:minmax(0,240px) minmax(0,1fr);
-  gap:6px 20px;padding:14px 16px;border-bottom:1px solid var(--rule);
-}
-.id-row:last-child{border-bottom:0}
-@media (max-width:720px){.id-row{grid-template-columns:1fr}}
-.id-label{
-  font-family:"IBM Plex Mono",monospace;font-size:9.5px;letter-spacing:.14em;
-  text-transform:uppercase;color:var(--ink-3);
-}
-.id-note{font-size:13px;color:var(--ink-2);margin:4px 0 0;max-width:44ch}
-.id-val{display:flex;align-items:flex-start;gap:10px}
-.id-val code{
-  flex:1 1 auto;min-width:0;
-  font-family:"IBM Plex Mono",monospace;font-size:12.5px;line-height:1.55;
-  color:var(--ink);background:var(--paper-3);border:1px solid var(--rule-2);
-  padding:6px 8px;overflow-wrap:anywhere;user-select:all;
-}
-.copy{
-  flex:0 0 auto;appearance:none;background:var(--paper-2);border:1px solid var(--rule);
-  color:var(--ink-2);font-family:"IBM Plex Mono",monospace;font-size:9.5px;
-  letter-spacing:.1em;text-transform:uppercase;padding:6px 9px;cursor:pointer;
-}
-.copy:hover{border-color:var(--accent-ink);color:var(--accent-ink)}
-.copy:focus-visible{outline:2px solid var(--accent-ink);outline-offset:2px}
-
-
-/* ---------- spec strip ---------- */
-.spec{
-  margin-top:34px;border:1px solid var(--rule);background:var(--paper-2);
-  display:grid;grid-template-columns:repeat(auto-fit,minmax(168px,1fr));
-}
-.spec div{padding:12px 14px;border-right:1px solid var(--rule)}
-.spec div:last-child{border-right:0}
-.spec dt{margin-bottom:4px}
-.spec dd{
-  font-family:"IBM Plex Mono",monospace;font-size:14px;color:var(--ink);
-  font-variant-numeric:tabular-nums;
-}
-.foot-r{display:inline-flex;align-items:center;gap:18px;flex-wrap:wrap}
-.themetog{
-  appearance:none;background:none;border:0;padding:0;margin:0;
-  display:inline-flex;align-items:center;gap:6px;cursor:pointer;
-  font-family:inherit;font-size:inherit;letter-spacing:inherit;
-  text-transform:inherit;color:var(--ink-3);
-}
-.themetog:hover{color:var(--accent-ink)}
-.themetog:focus-visible{outline:2px solid var(--accent-ink);outline-offset:3px}
-.themetog svg{width:13px;height:13px;display:block}
-.themetog .sun{display:none}
-:root[data-theme="dark"] .themetog .sun{display:block}
-:root[data-theme="dark"] .themetog .moon{display:none}
-@media (prefers-color-scheme:dark){
-  :root:not([data-theme="light"]) .themetog .sun{display:block}
-  :root:not([data-theme="light"]) .themetog .moon{display:none}
-}
-.foot-icons{display:inline-flex;align-items:center;gap:13px}
-.xlink{
-  display:inline-flex;align-items:center;color:var(--ink-3);
-}
-.xlink:hover{color:var(--accent-ink)}
-.xlink:focus-visible{outline:2px solid var(--accent-ink);outline-offset:3px}
-.xlink svg{width:13px;height:13px;display:block}
-
-.foot{
-  margin-top:26px;border-top:1px solid var(--rule);padding-top:10px;
-  font-family:"IBM Plex Mono",monospace;font-size:10.5px;letter-spacing:.13em;
-  text-transform:uppercase;color:var(--ink-3);
-  display:flex;justify-content:space-between;gap:16px;flex-wrap:wrap;
-}
-
-@media (prefers-reduced-motion: reduce){
-  .pkt,.lit{animation:none;opacity:0}
-  .folder{transition:none}
-  .folder[aria-selected="true"]{transform:none}
-}
-</style>
-<!-- Google Tag Manager: same container the rest of developers.stellar.org loads. Inlined because static/ files skip the Docusaurus build. -->
-<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src='https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);})(window,document,'script','dataLayer','GTM-M2JLH37');</script>
-<script async src="https://www.googletagmanager.com/gtag/js?id=G-ZCT4GYX8KN"></script>
-<script>window.dataLayer=window.dataLayer||[];function gtag(){dataLayer.push(arguments)}
-gtag('js',new Date());gtag('config','G-ZCT4GYX8KN',{anonymize_ip:true});</script>
-</head>
-<body>
-<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M2JLH37"
-  height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
-<div class="sheet">
-
-  <div class="top">
-    <span>USDT0 on Stellar Network</span>
-    <span class="top-r">
-    <a class="toplink" href="https://developers.stellar.org/docs/tokens/usdt0-layerzero">Stellar Docs &rarr;</a>
-    <nav class="secnav" aria-label="Sections">
-      <a class="tick" href="#arrival" aria-label="Arrival" title="Arrival" aria-current="true"></a>
-      <a class="tick" href="#access" aria-label="Access" title="Access"></a>
-      <a class="tick" href="#dayone" aria-label="Day one" title="Day one"></a>
-      <a class="tick" href="#deploy" aria-label="Deploy" title="Deploy"></a>
-      <a class="tick" href="#build" aria-label="Before you build" title="Before you build"></a>
-      <a class="tick" href="#faq" aria-label="FAQ" title="FAQ"></a>
-    </nav>
-    </span>
-  </div>
-
-  <h1>The asset with a unified supply <em>arrives on Stellar</em></h1>
-  <p class="deck">USDT0 is now available on the Stellar network. USDT0 connects Stellar to
-  <strong>a unified USDT supply</strong>, allowing USDT to move across networks without fragmenting
-  supply. USDT0 is a native Stellar asset that works with your existing stack.</p>
-
-  <!-- ============ FIGURE 1 ============ -->
-  <figure id="arrival">
-    <div class="fig-head"><h2>Arrival &mdash; how USDT0 gets to Stellar</h2></div>
-    <div class="fig-body">
-  <svg viewBox="0 0 990 420" role="img" aria-label="The USDT0 supply chain. USDT on Ethereum is locked and unlocked with the USDT0 adapter. From there one flow forks: Ethereum mints USDT0 directly on Stellar through Stellar's own OFT contract, and Ethereum also mints USDT0 on every other USDT0 chain, with an OFT on each USDT0-compatible network. Any of those chains can burn its USDT0 so Stellar's OFT mints instead, which never touches Ethereum. Either way the Stellar OFT is the single entry point, and what it mints is USDT0 on Stellar, a native Stellar asset compatible with existing toolkits, which feeds payment rails, treasury balances, and lending markets. A dashed line shows the routes run the other way.">
-        <defs>
-          <marker id="c-ar" viewBox="0 0 10 10" refX="9.4" refY="5" markerWidth="7" markerHeight="7" orient="auto-start-reverse">
-            <path d="M0 0 L10 5 L0 10 z" fill="currentColor"/>
-          </marker>
-          <marker id="c-ar-s" viewBox="0 0 10 10" refX="9.4" refY="5" markerWidth="6.5" markerHeight="6.5" orient="auto-start-reverse">
-            <path d="M0 0 L10 5 L0 10 z" fill="var(--ink-3)"/>
-          </marker>
-        </defs>
-        <!-- the routes run the other way too; drawn, not argued -->
-        <path class="edge dash" d="M 620 247 V 392 H 102 V 245" marker-end="url(#c-ar-s)"/>
-        <!-- where the backing sits, and the only place USDT is ever locked -->
-        <rect class="n-box" x="20" y="161" width="164" height="80"/>
-        <rect class="lit lEth" x="20" y="161" width="164" height="80"/>
-        <text class="n-t" x="34" y="188">USDT on Ethereum</text>
-        <text class="n-s" x="34" y="207">Locked / unlocked</text>
-        <text class="n-s" x="34" y="222">with USDT0 adapter</text>
-        <!-- one flow out of Ethereum, forking into two mints of equal length so
-             the two packets land on the same frame -->
-        <path class="edge" d="M 184 201 H 232"/>
-        <path class="edge" d="M 232 201 V 110 H 286" marker-end="url(#c-ar)"/>
-        <path class="edge" d="M 232 201 V 292 H 286" marker-end="url(#c-ar)"/>
-        <!-- a set of chains, not a step: two more behind the front one -->
-        <rect class="n-box alt" x="304" y="268" width="188" height="76"/>
-        <rect class="n-box alt" x="297" y="261" width="188" height="76"/>
-        <rect class="n-box" x="290" y="254" width="188" height="76"/>
-        <rect class="lit lChain" x="290" y="254" width="188" height="76"/>
-        <text class="n-t" x="304" y="282">USDT0 OFTs</text>
-        <text class="n-s" x="304" y="301">Each compatible network</text>
-        <text class="n-s" x="304" y="316">has its own contract</text>
-        <!-- chain to chain: never touches Ethereum -->
-        <path class="edge" d="M 384 254 V 168" marker-end="url(#c-ar)"/>
-        <!-- the one Stellar-side entry point, and the contract listed under Deploy -->
-        <rect class="n-box" x="290" y="72" width="188" height="92"/>
-        <rect class="lit lOft" x="290" y="72" width="188" height="92"/>
-        <text class="n-t" x="304" y="100">Stellar OFT</text>
-        <text class="n-s" x="304" y="119">The contract that</text>
-        <text class="n-s" x="304" y="134">mints and burns</text>
-        <text class="n-s" x="304" y="149">USDT0 on Stellar</text>
-        <path class="edge" d="M 478 110 H 528 V 201 H 574" marker-end="url(#c-ar)"/>
-        <rect class="n-box hot" x="578" y="155" width="186" height="92"/>
-        <rect class="lit lHot" x="578" y="155" width="186" height="92"/>
-        <text class="n-t hot" x="592" y="182">USDT0 on Stellar</text>
-        <text class="n-s" x="592" y="202">A native Stellar asset</text>
-        <text class="n-s" x="592" y="217">compatible with</text>
-        <text class="n-s" x="592" y="232">existing toolkits</text>
-        <line class="edge" x1="764" y1="171" x2="812" y2="171" marker-end="url(#c-ar)"/>
-        <line class="edge" x1="764" y1="201" x2="812" y2="201" marker-end="url(#c-ar)"/>
-        <line class="edge" x1="764" y1="231" x2="812" y2="231" marker-end="url(#c-ar)"/>
-        <rect class="n-box" x="816" y="157" width="164" height="28"/>
-        <rect class="lit lUse" x="816" y="157" width="164" height="28"/>
-        <text class="n-s" x="828" y="175">Payment rails</text>
-        <rect class="n-box" x="816" y="187" width="164" height="28"/>
-        <rect class="lit lUse" x="816" y="187" width="164" height="28"/>
-        <text class="n-s" x="828" y="205">Treasury balances</text>
-        <rect class="n-box" x="816" y="217" width="164" height="28"/>
-        <rect class="lit lUse" x="816" y="217" width="164" height="28"/>
-        <text class="n-s" x="828" y="235">Lending markets</text>
-        <circle class="pkt pTrunk" r="3.4"/><circle class="pkt pUp" r="3.4"/>
-        <circle class="pkt pDown" r="3.4"/><circle class="pkt pClimb" r="3.4"/>
-        <circle class="pkt pMint" r="3.4"/><circle class="pkt pUse1" r="3.4"/>
-        <circle class="pkt pUse2" r="3.4"/><circle class="pkt pUse3" r="3.4"/>
-      </svg>
-    </div>
-    <figcaption>Stellar&rsquo;s OFT mints the USDT0, whether Ethereum locked the USDT or another chain
-    burned its own. Every chain runs its own OFT; Ethereum alone locks the USDT that backs them all
-    (<a href="https://docs.usdt0.to/technical-documentation/developer" target="_blank" rel="noopener noreferrer">USDT0
-    developer docs</a>).</figcaption>
-  </figure>
-
-  <!-- ============ FIGURE 2 — the USDT0 folder ============ -->
-  <figure id="access">
-    <div class="fig-head"><h2>Access &mdash; what USDT0 unlocks</h2></div>
-    <div class="folder-fig">
-      <div class="stackwrap">
-        <div class="stack" id="stack" role="img" aria-label="A USDT0 folder, its cover in front, holding 4 files: payments, treasury, collateral, distribution." style="--ar: 1.3425316828892888; --fw: 75.00159374402347%; --fh: 66.43326324004423%;"><div class="file" style="left:24.99840625597654%;top:0%;z-index:1">
-       
-  <svg class="fo" viewBox="0 0 288 190" preserveAspectRatio="none" aria-hidden="true">
-    <path class="fo-body" d="M 8 0 H 110 A 8 8 0 0 1 118 8 V 24 H 280 A 8 8 0 0 1 288 32 V 182 A 8 8 0 0 1 280 190 H 8 A 8 8 0 0 1 0 182 V 8 A 8 8 0 0 1 8 0 Z"></path>
-    <path class="fo-tab" d="M 8 0 H 110 A 8 8 0 0 1 118 8 V 25 H 0 V 8 A 8 8 0 0 1 8 0 Z"></path>
-    <path class="fo-edge" d="M 8 0 H 110 A 8 8 0 0 1 118 8 V 24 H 280 A 8 8 0 0 1 288 32 V 182 A 8 8 0 0 1 280 190 H 8 A 8 8 0 0 1 0 182 V 8 A 8 8 0 0 1 8 0 Z"></path>
-  </svg><span class="fname">DISTRIBUTION</span>
-     </div><div class="file" style="left:18.748804691982407%;top:8.391684189988943%;z-index:2">
-       
-  <svg class="fo" viewBox="0 0 288 190" preserveAspectRatio="none" aria-hidden="true">
-    <path class="fo-body" d="M 8 0 H 110 A 8 8 0 0 1 118 8 V 24 H 280 A 8 8 0 0 1 288 32 V 182 A 8 8 0 0 1 280 190 H 8 A 8 8 0 0 1 0 182 V 8 A 8 8 0 0 1 8 0 Z"></path>
-    <path class="fo-tab" d="M 8 0 H 110 A 8 8 0 0 1 118 8 V 25 H 0 V 8 A 8 8 0 0 1 8 0 Z"></path>
-    <path class="fo-edge" d="M 8 0 H 110 A 8 8 0 0 1 118 8 V 24 H 280 A 8 8 0 0 1 288 32 V 182 A 8 8 0 0 1 280 190 H 8 A 8 8 0 0 1 0 182 V 8 A 8 8 0 0 1 8 0 Z"></path>
-  </svg><span class="fname">COLLATERAL</span>
-     </div><div class="file" style="left:12.49920312798827%;top:16.783368379977887%;z-index:3">
-       
-  <svg class="fo" viewBox="0 0 288 190" preserveAspectRatio="none" aria-hidden="true">
-    <path class="fo-body" d="M 8 0 H 110 A 8 8 0 0 1 118 8 V 24 H 280 A 8 8 0 0 1 288 32 V 182 A 8 8 0 0 1 280 190 H 8 A 8 8 0 0 1 0 182 V 8 A 8 8 0 0 1 8 0 Z"></path>
-    <path class="fo-tab" d="M 8 0 H 110 A 8 8 0 0 1 118 8 V 25 H 0 V 8 A 8 8 0 0 1 8 0 Z"></path>
-    <path class="fo-edge" d="M 8 0 H 110 A 8 8 0 0 1 118 8 V 24 H 280 A 8 8 0 0 1 288 32 V 182 A 8 8 0 0 1 280 190 H 8 A 8 8 0 0 1 0 182 V 8 A 8 8 0 0 1 8 0 Z"></path>
-  </svg><span class="fname">TREASURY</span>
-     </div><div class="file" style="left:6.249601563994135%;top:25.17505256996683%;z-index:4">
-       
-  <svg class="fo" viewBox="0 0 288 190" preserveAspectRatio="none" aria-hidden="true">
-    <path class="fo-body" d="M 8 0 H 110 A 8 8 0 0 1 118 8 V 24 H 280 A 8 8 0 0 1 288 32 V 182 A 8 8 0 0 1 280 190 H 8 A 8 8 0 0 1 0 182 V 8 A 8 8 0 0 1 8 0 Z"></path>
-    <path class="fo-tab" d="M 8 0 H 110 A 8 8 0 0 1 118 8 V 25 H 0 V 8 A 8 8 0 0 1 8 0 Z"></path>
-    <path class="fo-edge" d="M 8 0 H 110 A 8 8 0 0 1 118 8 V 24 H 280 A 8 8 0 0 1 288 32 V 182 A 8 8 0 0 1 280 190 H 8 A 8 8 0 0 1 0 182 V 8 A 8 8 0 0 1 8 0 Z"></path>
-  </svg><span class="fname">PAYMENTS</span>
-     </div><div class="file cover" style="left:0;top:33.56673675995577%;z-index:5">
-     
-  <svg class="fo" viewBox="0 0 288 190" preserveAspectRatio="none" aria-hidden="true">
-    <path class="fo-body" d="M 8 0 H 110 A 8 8 0 0 1 118 8 V 24 H 280 A 8 8 0 0 1 288 32 V 182 A 8 8 0 0 1 280 190 H 8 A 8 8 0 0 1 0 182 V 8 A 8 8 0 0 1 8 0 Z"></path><path class="fo-tint" d="M 8 0 H 110 A 8 8 0 0 1 118 8 V 24 H 280 A 8 8 0 0 1 288 32 V 182 A 8 8 0 0 1 280 190 H 8 A 8 8 0 0 1 0 182 V 8 A 8 8 0 0 1 8 0 Z"></path>
-    <path class="fo-tab" d="M 8 0 H 110 A 8 8 0 0 1 118 8 V 25 H 0 V 8 A 8 8 0 0 1 8 0 Z"></path>
-    <path class="fo-edge" d="M 8 0 H 110 A 8 8 0 0 1 118 8 V 24 H 280 A 8 8 0 0 1 288 32 V 182 A 8 8 0 0 1 280 190 H 8 A 8 8 0 0 1 0 182 V 8 A 8 8 0 0 1 8 0 Z"></path>
-  </svg>
-     <span class="fname">USDT0</span>
-     <span class="cover-body">
-       <span class="cover-name">Access to a new economy</span>
-       <span class="cover-sub">One asset · one supply</span>
-     </span>
-   </div></div>
-      </div>
-      <div class="desc" id="desc"><span class="d-eyebrow">USDT0</span><h3 class="d-head">Access to a new economy</h3><p class="d-claim">The asset that brings access to new corridors, counterparties, and financial use cases on Stellar.</p><dl><div><dt>One asset, unified liquidity</dt><dd>USDT0 maintains a unified supply anchored to USDT on Ethereum, so liquidity isn’t fragmented across separate wrapped versions of the asset.</dd></div><div><dt>Built to move across networks</dt><dd>Operated by <a href="https://everdawn.to/" target="_blank" rel="noopener noreferrer">Everdawn Labs</a>, USDT0 connects Stellar to <a href="https://analytics.usdt0.to/" target="_blank" rel="noopener noreferrer">26+ networks</a> through LayerZero’s OFT standard.</dd></div></dl></div>
-    </div>
-    <div class="fig-files">
-      <div class="files" id="files" style="--cols: 4;">
-  <div class="fcol">
-    <div class="ftag">Payments</div>
-    <h4 class="fhead">Build with an asset already in use</h4>
-    <p class="fcopy">Support cross-border payments, payouts, remittances, and other dollar-denominated flows with USDT0.</p>
-  </div>
-  <div class="fcol">
-    <div class="ftag">Treasury</div>
-    <h4 class="fhead">Power treasury and cash management products</h4>
-    <p class="fcopy">Give businesses and users a dollar-denominated asset for managing working capital.</p>
-  </div>
-  <div class="fcol">
-    <div class="ftag">Collateral</div>
-    <h4 class="fhead">Put USDT0 to work</h4>
-    <p class="fcopy">Give lending markets a dollar-denominated asset to use as collateral or borrow against.</p>
-  </div>
-  <div class="fcol">
-    <div class="ftag">Distribution</div>
-    <h4 class="fhead">One asset, many doors</h4>
-    <p class="fcopy">Every exchange, wallet, and fintech that lists it becomes an entry point to the Stellar network.</p>
-  </div></div>
-    </div>
-  </figure>
-
-  <!-- ============ DAY ONE ============ -->
-  <section class="dayone" id="dayone" aria-labelledby="d1-h">
-    <div class="dep-head">
-      <h2 id="d1-h">Day one &mdash; what is already integrated</h2>
-    </div>
-    <div class="d1-body">
-      <p class="d1-lead">You can access USDT0 today across these partners on Stellar.<br>
-      More to come on a rolling basis.</p>
-
-      <div class="venues">
-        <div class="venue">
-          <h3>Exchanges, DEXs &amp; Lending Protocols</h3>
-          <ul><li>Kraken</li><li>SushiSwap</li><li>BiLira</li><li>Kinetic (K2)</li></ul>
-          <p>Buy, sell, swap, and borrow against USDT0 on Stellar.</p>
-        </div>
-        <div class="venue">
-          <h3>Wallets</h3>
-          <ul><li>Freighter</li><li>Lobstr</li><li>Meru</li><li>Bitget Wallet</li><li>Exodus</li></ul>
-          <p>Hold and send USDT0 on Stellar.</p>
-        </div>
-        <div class="venue">
-          <h3>Custody</h3>
-          <ul><li>Fireblocks</li></ul>
-          <p>Institutional custody and treasury operations for USDT0 on Stellar.</p>
-        </div>
-        <div class="venue">
-          <h3>Fintechs &amp; ramps</h3>
-          <ul><li>Ramp Network</li><li>Kredete</li></ul>
-          <p>Ramp services and fintech products using USDT0 in production, including cross-border payments across Africa.</p>
-        </div>
-      </div>
-
-      <a class="dep-link" href="https://usdt0.to/transfer" target="_blank" rel="noopener noreferrer">
-        Transfer USDT0 to Stellar &rarr;</a>
-
-    </div>
-    <div class="dep-note">Balances move into and out of Stellar without a custodial bridge or a
-    wrapped representation. Transfer time is set by the chain you send from &mdash; a couple of minutes
-    from some networks, hours from others. The cost is that network's gas plus the LayerZero
-    message, <a href='https://docs.usdt0.to/technical-documentation/developer/' target='_blank' rel='noopener noreferrer'>quoted per route</a>
-    before you send. USDT0 itself charges no protocol fee on most routes; where one applies it is
-    0.03%, set per route. Receiving USDT0 needs a trustline on the destination account &mdash;
-    see <a href="#build">requirements and limitations</a>.</div>
-  </section>
-
-  <!-- ============ DEPLOY ============ -->
-  <section class="deploy" id="deploy" aria-labelledby="dep-h">
-    <div class="dep-head">
-      <h2 id="dep-h">Deploy &mdash; adding USDT0 to your environment</h2>
-      <span class="live">Live on Stellar Mainnet</span>
-    </div>
-    <div class="dep-body">
-      <p class="dep-lead">USDT0 is live on Stellar Mainnet. Add it to your wallet or environment. Test your
-      integration by <strong>moving a small amount end to end</strong> before rolling out to your users.</p>
-
-      <a class="dep-link" target="_blank" rel="noopener noreferrer"
-         href="https://stellar.expert/explorer/public/asset/USDT0-GATISXX6BZ6NC7IKQBY37CJD4SOZL3CYZJWXEDG6JVIY4WBS6KXJHN6Q">
-        View the asset on stellar.expert &rarr;</a>
-
-      <div class="ids" id="ids">
-  <div class="id-row">
-    <div>
-      <div class="id-label">Classic asset</div>
-      <p class="id-note">The asset code and issuer address. A trustline points at this pair.</p>
-    </div>
-    <div class="id-val">
-      <code id="id-0">USDT0:GATISXX6BZ6NC7IKQBY37CJD4SOZL3CYZJWXEDG6JVIY4WBS6KXJHN6Q</code>
-      <button class="copy" type="button" data-for="id-0" aria-label="Copy Classic asset">Copy</button>
-    </div>
-  </div>
-  <div class="id-row">
-    <div>
-      <div class="id-label">Token contract (SAC)</div>
-      <p class="id-note">The Stellar Smart Contract (Soroban) interface. Call this from contracts — lending markets, vaults, AMMs.</p>
-    </div>
-    <div class="id-val">
-      <code id="id-1">CBSJZEIO5C7KC2SF3MKSNXXJSW5G3VTNBX4ATMKUI3B2MR4JKM4R26YF</code>
-      <button class="copy" type="button" data-for="id-1" aria-label="Copy Token contract (SAC)">Copy</button>
-    </div>
-  </div>
-  <div class="id-row">
-    <div>
-      <div class="id-label">OFT</div>
-      <p class="id-note">The USDT0-specific OFT contract on Stellar — it burns and mints USDT0 here. Not part of a Stellar-side payment.</p>
-    </div>
-    <div class="id-val">
-      <code id="id-2">CBOWOLFSDM5PZXNFIVDMP5NZ7U2GSIHED6H6R446QOHF266XINKUMMF6</code>
-      <button class="copy" type="button" data-for="id-2" aria-label="Copy OFT">Copy</button>
-    </div>
-  </div>
-  <div class="id-row">
-    <div>
-      <div class="id-label">LayerZero endpoint ID</div>
-      <p class="id-note">Stellar's EID. You need it to address Stellar from another chain's OFT.</p>
-    </div>
-    <div class="id-val">
-      <code id="id-3">30600</code>
-      <button class="copy" type="button" data-for="id-3" aria-label="Copy LayerZero endpoint ID">Copy</button>
-    </div>
-  </div></div>
-
-      <a class="dep-link" target="_blank" rel="noopener noreferrer"
-         href="https://docs.usdt0.to/technical-documentation/deployments?q=stellar">Contract deployments on docs.usdt0.to &rarr;</a>
-
-    </div>
-    <div class="dep-note"><b><a href='https://stellar.expert/explorer/public/asset/USDT0-GATISXX6BZ6NC7IKQBY37CJD4SOZL3CYZJWXEDG6JVIY4WBS6KXJHN6Q' target='_blank' rel='noopener noreferrer'>This asset</a> sets <code>auth_revocable</code> and <code>auth_clawback_enabled</code></b> &mdash; the issuer can revoke a trustline or <a href='/docs/build/guides/transactions/clawbacks'>clawback a balance</a>. <code>auth_required</code> is not set, so anyone can hold it. &#128161; Soroswap maintains an <a href='https://github.com/soroswap/token-list/tree/main/assets' target='_blank' rel='noopener noreferrer'>ecosystem token list</a> covering both classic assets and contract tokens (community-maintained rather than an official Stellar registry, and widely used).</div>
-  </section>
-
-  <section class="notes-sec" id="build" aria-labelledby="bd-h">
-    <div class="dep-head"><h2 id="bd-h">Before you build &mdash; requirements and limitations</h2></div>
-    <div class="notes-body">
-      <p class="dep-lead">What USDT0 on Stellar requires for integration.</p>
-      <div class="notes" id="notes">
-  <div class="note">
-    <div class="ntag">Trustlines</div>
-    <p class="ncopy"><b>A trustline has to exist before the first payment lands.</b> Sending USDT0 to an account that has no USDT0 trustline fails with <a href="/docs/data/apis/horizon/api-reference/errors/result-codes/operation-specific/payment"><code>op_no_trust</code></a>. A wallet may create it for you when you swap into USDT0 in-app; a transfer arriving from an exchange or another wallet has no such fallback. If you custody for users, create it during onboarding — <a href="/docs/build/guides/transactions/sponsored-reserves">sponsored reserves</a> can cover the reserve.</p>
-  </div>
-  <div class="note">
-    <div class="ntag">Decimals</div>
-    <p class="ncopy"><b>The OFT reconciles a precision gap for you.</b> USDT0 on Stellar carries <a href="/docs/learn/fundamentals/stellar-data-structures/assets">seven decimals</a>; cross-chain transfers normalize to the OFT’s <a href="https://docs.layerzero.network/v2/concepts/technical-reference/oft-reference" target="_blank" rel="noopener noreferrer">six shared decimals</a>. Send 1.2345678 and 1.234567 moves; the remaining 0.0000008 is floored off as dust and refunded to you before the debit. Nothing to convert by hand — but account for it when you calculate or display an amount.</p>
-  </div>
-  <div class="note">
-    <div class="ntag">Route limits</div>
-    <p class="ncopy"><b>A route can enforce a minimum.</b> Minimum transfer amounts are set per contract, so call <a href="https://docs.usdt0.to/technical-documentation/developer" target="_blank" rel="noopener noreferrer"><code>quote_oft</code></a> for the route you intend to use rather than assuming any amount will go through.</p>
-  </div>
-  <div class="note">
-    <div class="ntag">Backing</div>
-    <p class="ncopy"><b>The backing sits in one contract.</b> USDT0's adapter on Ethereum holds the USDT behind the natively issued supply.</p>
-  </div>
-  <div class="note">
-    <div class="ntag">Yield</div>
-    <p class="ncopy"><b>USDT0 doesn't accrue yield.</b> It earns nothing sitting in a balance — any return has to come from the market you supply it to.</p>
-  </div>
-  <div class="note">
-    <div class="ntag">Listings</div>
-    <p class="ncopy"><b>Each venue decides which networks it supports.</b> One USDT0 doesn't mean every listing offers every route, so check what a partner actually enables before you send users to it.</p>
-  </div></div>
-    </div>
-  </section>
-
-
-  <section class="notes-sec" id="faq" aria-labelledby="fq-h">
-    <div class="dep-head"><h2 id="fq-h">FAQ</h2></div>
-    <div class="notes-body">
-      <div class="faqs">
-      <details class="faq">
-        <summary><span class="fq">Is USDT0 the same as USDT?</span></summary>
-        <div class="fa"><p class="ncopy">No &mdash; it is a separate asset with its own contract, worth the same and backed 1:1 by USDT locked
- on Ethereum. The practical difference is deposits: a venue that supports USDT will not necessarily accept
- USDT0 on Stellar. Check your destination lists USDT0 on Stellar specifically before you send.</p></div>
-      </details>
-      <details class="faq">
-        <summary><span class="fq">Which USDT0 on Stellar is the real one?</span></summary>
-        <div class="fa"><p class="ncopy">The one issued by <code>GATISXX6BZ6NC7IKQBY37CJD4SOZL3CYZJWXEDG6JVIY4WBS6KXJHN6Q</code> &mdash;
- <a href='https://stellar.expert/explorer/public/asset/USDT0-GATISXX6BZ6NC7IKQBY37CJD4SOZL3CYZJWXEDG6JVIY4WBS6KXJHN6Q' target='_blank' rel='noopener noreferrer'>check it on Stellar Expert</a>.
- Asset codes on Stellar are not unique &mdash; anyone can issue an asset called USDT0 &mdash; so identity is
- the code <b>and</b> the issuer together. Pin that issuer, and confirm the contract you derive from it
- matches <code>CBSJZEIO5C7KC2SF3MKSNXXJSW5G3VTNBX4ATMKUI3B2MR4JKM4R26YF</code>.</p></div>
-      </details>
-      <details class="faq">
-        <summary><span class="fq">Why did my USDT0 payment fail with <code>op_no_trust</code>?</span></summary>
-        <div class="fa"><p class="ncopy">The destination account has no USDT0 trustline, and one must exist before the first payment can land.
- A wallet often creates it when a user swaps into USDT0 in-app, but a transfer arriving from an exchange or
- another wallet has no such fallback. If you custody for users, create it during onboarding &mdash;
- <a href='/docs/build/guides/transactions/sponsored-reserves'>sponsored reserves</a>
- can cover the reserve.</p></div>
-      </details>
-      <details class="faq">
-        <summary><span class="fq">How long does a transfer to Stellar take?</span></summary>
-        <div class="fa"><p class="ncopy">It depends on the chain you send from, not on Stellar. Stellar finalises in 5&ndash;7 seconds; the wait
- is the source chain confirming and LayerZero verifying the message. From Polygon it is about a minute.
- From Ethereum, Arbitrum, Tron and Solana &mdash; the routes carrying most volume &mdash; expect roughly
- 18&ndash;21 minutes. A few low-traffic routes take hours. The
- <a href='https://usdt0.to/transfer' target='_blank' rel='noopener noreferrer'>transfer UI</a>
- quotes an estimate for your route before you send.</p></div>
-      </details>
-      <details class="faq">
-        <summary><span class="fq">Why is my transfer slower than I expected?</span></summary>
-        <div class="fa"><p class="ncopy">Usually because the figure you saw was a network-wide best case rather than your route. Nothing on the
- Stellar side is the bottleneck. If a transfer runs well past the estimate you were quoted, look up the message on
- <a href='https://layerzeroscan.com/analytics/networks' target='_blank' rel='noopener noreferrer'>LayerZero Scan</a>,
- which indexes Stellar as a destination, to see which step it is sitting at. USDT0 lists
- <a href='https://docs.usdt0.to/resources/contact' target='_blank' rel='noopener noreferrer'>support contacts</a>
- for transfers that stall.</p></div>
-      </details>
-      <details class="faq">
-        <summary><span class="fq">What does it cost to bring USDT0 to Stellar?</span></summary>
-        <div class="fa"><p class="ncopy">Three separate things, and two different calls report them. USDT0's own protocol fee is zero on most
- routes and 0.03% where one applies:
- <a href='https://docs.usdt0.to/technical-documentation/developer/' target='_blank' rel='noopener noreferrer'><code>quote_oft</code></a>
- shows it as the gap between <code>amount_sent_ld</code> and <code>amount_received_ld</code>, so read it
- there rather than trusting a published number. The LayerZero messaging fee is separate and comes back from
- <a href='https://docs.usdt0.to/technical-documentation/developer/' target='_blank' rel='noopener noreferrer'><code>quote_send</code></a>,
- paid in XLM when you send from Stellar &mdash; this is the part that varies most. And on Stellar, ordinary transactions cost a
- <a href='/docs/learn/fundamentals/fees-resource-limits-metering'>minimum of 100 stroops</a>
- per operation, which is unrelated to bridging.</p></div>
-      </details>
-      <details class="faq">
-        <summary><span class="fq">What is the difference between the Open Mesh and the Legacy Mesh?</span></summary>
-        <div class="fa"><p class="ncopy">On the Open Mesh each chain runs its own OFT contract, and moving between them burns on one side and
- mints on the other. The
- <a href='https://docs.usdt0.to/overview/the-legacy-mesh' target='_blank' rel='noopener noreferrer'>Legacy Mesh</a>
- connects chains where Tether had already deployed native USDT &mdash; Ethereum, Tron, TON, Arbitrum, Solana
- and Celo &mdash; through a shared non-custodial hub on Arbitrum, so those chains keep their existing USDT
- contracts rather than migrating.</p></div>
-      </details>
-      <details class="faq">
-        <summary><span class="fq">Why did I receive slightly less than I sent?</span></summary>
-        <div class="fa"><p class="ncopy">Rounding, in the last decimal places only. USDT0 on Stellar carries seven decimals; cross-chain
- transfers normalise to the OFT's six shared decimals. Send 1.2345678 and 1.234567 moves &mdash; the
- remaining 0.0000008 is floored off as dust and refunded to you before the debit.</p></div>
-      </details>
-      <details class="faq">
-        <summary><span class="fq">Who can freeze or clawback USDT0 on Stellar?</span></summary>
-        <div class="fa"><p class="ncopy">The issuer. The asset sets <code>auth_revocable</code> and <code>auth_clawback_enabled</code>, so the
- issuer can revoke a trustline or
- <a href='/docs/build/guides/transactions/clawbacks'>clawback a balance</a>.
- <code>auth_required</code> is not set, so anyone can hold it without approval.</p></div>
-      </details>
-      </div>
-    </div>
-  </section>
-
-  <dl class="spec">
-    <div><dt>Asset</dt><dd>USDT0</dd></div>
-    <div><dt>Transfer</dt><dd><a href='https://usdt0.to/transfer' target='_blank' rel='noopener noreferrer'>usdt0.to</a></dd></div>
-    <div><dt>Networks</dt><dd><a href='https://analytics.usdt0.to/' target='_blank' rel='noopener noreferrer'>26+</a></dd></div>
-    <div><dt>USDT in circulation</dt><dd><a href='https://coinmarketcap.com/currencies/tether/' target='_blank' rel='noopener noreferrer'>$180B+</a></dd></div>
-    <div><dt>Stellar settlement</dt><dd><a href='/docs/learn/fundamentals/stellar-stack'>5&ndash;7s</a></dd></div>
-    <div><dt>Stellar fee</dt><dd><a href='/docs/learn/fundamentals/fees-resource-limits-metering'>100 stroops min</a></dd></div>
-    <div><dt>Transfer to Stellar</dt><dd><a href='https://usdt0.to/transfer' target='_blank' rel='noopener noreferrer'>~20min typical</a></dd></div>
-  </dl>
-
-  <div class="sources">
-    <b>Sources</b>
-    <a href="https://docs.usdt0.to/technical-documentation/developer/" target="_blank" rel="noopener noreferrer">USDT0 Docs</a>
-    <a href="https://docs.usdt0.to/technical-documentation/deployments?q=stellar" target="_blank" rel="noopener noreferrer">USDT0 deployments</a>
-    <a href="/docs/tokens/usdt0-layerzero">Stellar Docs</a>
-    <a href="https://lab.stellar.org/smart-contracts/contract-list?$=network$id=mainnet&amp;label=Mainnet&amp;horizonUrl=https:////horizon.stellar.org&amp;rpcUrl=https:////mainnet.sorobanrpc.com&amp;passphrase=Public%20Global%20Stellar%20Network%20/;%20September%202015;&amp;smartContracts$contractList$activeTab=known-assets;;" target="_blank" rel="noopener noreferrer">Stellar Lab</a>
-    <a href="https://docs.layerzero.network/v2/developers/stellar/overview" target="_blank" rel="noopener noreferrer">LayerZero on Stellar</a>
-  </div>
-
-  <div class="foot">
-    <span>Stellar Development Foundation</span>
-    <span class="foot-r">
-      <span class="foot-icons">
-      <button class="themetog" id="themetog" type="button" aria-pressed="false">
-        <svg class="moon" viewBox="0 0 24 24" fill="none" stroke="currentColor"
-             stroke-width="2" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true">
-          <path d="M21 12.8A9 9 0 1 1 11.2 3a7 7 0 0 0 9.8 9.8Z"/>
-        </svg>
-        <svg class="sun" viewBox="0 0 24 24" fill="none" stroke="currentColor"
-             stroke-width="2" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true">
-          <circle cx="12" cy="12" r="4.2"/>
-          <path d="M12 2v2M12 20v2M4.9 4.9l1.4 1.4M17.7 17.7l1.4 1.4M2 12h2M20 12h2M4.9 19.1l1.4-1.4M17.7 6.3l1.4-1.4"/>
-        </svg>
-      </button>
-      <a class="xlink" href="https://x.com/BuildOnStellar" target="_blank"
-         rel="noopener noreferrer" aria-label="Build on Stellar on X"
-         title="Build on Stellar on X">
-        <svg viewBox="0 0 24 24" fill="currentColor" aria-hidden="true">
-          <path d="M18.244 2.25h3.308l-7.227 8.26 8.502 11.24H16.17l-5.214-6.817L4.99 21.75H1.68l7.73-8.835L1.254 2.25H8.08l4.713 6.231zm-1.161 17.52h1.833L7.084 4.126H5.117z"/>
-        </svg>
-      </a>
-      </span>
-    </span>
-  </div>
-</div>
-
-<script>
-// The markup for the folder stack, the benefit columns, the description and
-// the requirement notes is written into the HTML rather than generated here.
-// With scripting off — a plain fetch, a crawler, an agent reading the page —
-// the JS-built version rendered as empty boxes, and that was most of the page.
-// What stays below is behaviour that has nothing to render without: the
-// section markers, the copy buttons and the theme toggle.
-
-// ---------- section markers ----------
-const SECTIONS = [
-  ["arrival","Arrival"], ["access","Access"], ["dayone","Day one"], ["deploy","Deploy"],
-  ["build","Before you build"], ["faq","FAQ"]
-];
-const secTicks = [...document.querySelectorAll('.tick')];
-
-function markSection(i){
-  secTicks.forEach((t,j) => {
-    if (j === i) t.setAttribute('aria-current','true');
-    else t.removeAttribute('aria-current');
-  });
-}
-
-// which section is under the sticky bar. Ratio-based spying is biased by
-// section height, so measure position against a fixed line instead.
-function activeSection(){
-  const line = 96;
-  let idx = 0;
-  SECTIONS.forEach(([id], i) => {
-    const el = document.getElementById(id);
-    if (el && el.getBoundingClientRect().top <= line) idx = i;
-  });
-  // The final section is shorter than the viewport, so the page runs out of
-  // scroll before its top ever reaches the line and it could never go active.
-  // Once the document is scrolled to the end, the last section is the one
-  // being read, whatever the measurement says.
-  const sc = document.scrollingElement || document.documentElement;
-  if (sc.scrollTop + sc.clientHeight >= sc.scrollHeight - 2) idx = SECTIONS.length - 1;
-  return idx;
-}
-let spyQueued = false;
-function spy(){
-  if (spyQueued) return;
-  spyQueued = true;
-  requestAnimationFrame(() => { spyQueued = false; markSection(activeSection()); });
-}
-window.addEventListener('scroll', spy, { passive:true });
-window.addEventListener('resize', spy);
-spy();
-
-// ---------- deploy identifiers ----------
-const ids = document.getElementById('ids');
-
-ids.querySelectorAll('.copy').forEach(btn => {
-  btn.addEventListener('click', async () => {
-    const el = document.getElementById(btn.dataset.for);
-    const done = msg => { btn.textContent = msg; setTimeout(() => btn.textContent = 'Copy', 1600); };
-    try {
-      await navigator.clipboard.writeText(el.textContent);
-      done('Copied');
-    } catch {
-      // clipboard access can be blocked in an embedded frame — select it instead
-      const range = document.createRange();
-      range.selectNodeContents(el);
-      const sel = window.getSelection();
-      sel.removeAllRanges();
-      sel.addRange(range);
-      done('Selected');
-    }
-  });
-});
-
-// ---------- theme toggle ----------
-// No stored choice means follow the OS. Clicking sets an explicit override,
-// which the :root[data-theme] blocks pick up over the media query.
-(function(){
-  const root  = document.documentElement;
-  const KEY   = 'usdt0-atlas-theme';
-  const btn   = document.getElementById('themetog');
-  const mq    = window.matchMedia('(prefers-color-scheme: dark)');
-
-  const store = {
-    get(){ try { return localStorage.getItem(KEY) || localStorage.getItem('theme'); } catch (e) { return null; } },
-    set(v){ try { v ? localStorage.setItem(KEY,v) : localStorage.removeItem(KEY); } catch (e) {} }
-  };
-
-  const showing = () => root.dataset.theme || (mq.matches ? 'dark' : 'light');
-
-  // icon and label are swapped by CSS; only the accessible name needs scripting
-  function paint(){
-    const dark = showing() === 'dark';
-    btn.setAttribute('aria-pressed', String(dark));
-    const name = dark ? 'Switch to light mode' : 'Switch to dark mode';
-    btn.setAttribute('aria-label', name);
-    btn.setAttribute('title', name);
-  }
-
-  const saved = store.get();
-  if (saved === 'dark' || saved === 'light') root.dataset.theme = saved;
-  paint();
-
-  btn.addEventListener('click', () => {
-    const next = showing() === 'dark' ? 'light' : 'dark';
-    root.dataset.theme = next;
-    store.set(next);
-    paint();
-  });
-
-  // with no explicit choice stored, keep following the OS
-  mq.addEventListener('change', () => { if (!root.dataset.theme) paint(); });
-})();
-</script>
-</body>
-</html>
diff --git a/static/llms.txt b/static/llms.txt
deleted file mode 100644
index 5b79e716e..000000000
--- a/static/llms.txt
+++ /dev/null
@@ -1,297 +0,0 @@
-# Stellar Developer Documentation
-Stellar is a layer-1, open-source, decentralized, peer-to-peer blockchain network that provides a framework for developers to create applications, issue assets, write smart contracts, and connect to existing financial rails. Stellar is designed to enable creators, innovators, and developers to build projects on the network that can interoperate with each other.
-
-Each documentation page is available as clean markdown by appending `.md` to the URL
-(e.g. `https://developers.stellar.org/docs/build/smart-contracts/overview.md`).
-Alternatively, send an `Accept: text/markdown` request header to any page URL to receive markdown without modifying the URL.
-
-Full documentation as a single file: https://developers.stellar.org/llms-full.txt
-
-Live MCP server: connect an AI agent to Raven at https://raven.stellar.buzz/mcp
-for these docs plus live ecosystem data, cross-referenced on demand. Open source:
-https://github.com/stellar-experimental/stellar-raven — try it: https://raven.stellar.buzz/playground
-
-
-[Build](https://developers.stellar.org/docs/build.md)
-
-- [Overview](https://developers.stellar.org/docs/build.md)
-
-[Build Smart Contracts](https://developers.stellar.org/docs/build/smart-contracts.md)
-- [Introduction](https://developers.stellar.org/docs/build/smart-contracts/overview.md)
-- [Getting Started](https://developers.stellar.org/docs/build/smart-contracts/getting-started.md)
-- [Example Contracts](https://developers.stellar.org/docs/build/smart-contracts/example-contracts.md)
-
-[Build Applications](https://developers.stellar.org/docs/build/apps.md)
-- [Introduction](https://developers.stellar.org/docs/build/apps/overview.md)
-- [Application Design Considerations](https://developers.stellar.org/docs/build/apps/application-design-considerations.md)
-- [Tutorial: Wallet SDK](https://developers.stellar.org/docs/build/apps/wallet/overview.md)
-- [Tutorial: Payment Application, JavaScript](https://developers.stellar.org/docs/build/apps/example-application-tutorial/overview.md)
-- [Tutorial: Payment Application, Swift](https://developers.stellar.org/docs/build/apps/swift-payment-app.md)
-- [Tutorial: Network Ingestion Pipeline](https://developers.stellar.org/docs/build/apps/ingest-sdk/overview.md)
-- [Tutorial: Passkey Dapp](https://developers.stellar.org/docs/build/apps/guestbook/overview.md)
-- [Tutorial: Dapp Frontend](https://developers.stellar.org/docs/build/apps/dapp-frontend.md)
-
-[How-To Guides](https://developers.stellar.org/docs/build/guides.md)
-- [Contract Authorization](https://developers.stellar.org/docs/build/guides/auth.md)
-- [Contract Conventions](https://developers.stellar.org/docs/build/guides/conventions.md)
-- [Contract Accounts](https://developers.stellar.org/docs/build/guides/contract-accounts.md)
-- [Contract Events](https://developers.stellar.org/docs/build/guides/events.md)
-- [Contract Storage](https://developers.stellar.org/docs/build/guides/storage.md)
-- [Contract Testing](https://developers.stellar.org/docs/build/guides/testing.md)
-- [Dapp Development](https://developers.stellar.org/docs/build/guides/dapps.md)
-- [Fees & Metering](https://developers.stellar.org/docs/build/guides/fees.md)
-- [Freighter Wallet](https://developers.stellar.org/docs/build/guides/freighter.md)
-- [Stellar Basics](https://developers.stellar.org/docs/build/guides/basics.md)
-- [RPC](https://developers.stellar.org/docs/build/guides/rpc.md)
-- [State Archival](https://developers.stellar.org/docs/build/guides/archival.md)
-- [Stellar Asset Contract Tokens](https://developers.stellar.org/docs/build/guides/tokens.md)
-- [Transactions](https://developers.stellar.org/docs/build/guides/transactions.md)
-- [Type Conversions](https://developers.stellar.org/docs/build/guides/conversions.md)
-
-[Security Best Practices](https://developers.stellar.org/docs/build/security-docs.md)
-
-[Learn](https://developers.stellar.org/docs/learn/fundamentals.md)
-
-[Core Concepts](https://developers.stellar.org/docs/learn/fundamentals.md)
-- [Stellar Stack](https://developers.stellar.org/docs/learn/fundamentals/stellar-stack.md)
-- [Lumens (XLM)](https://developers.stellar.org/docs/learn/fundamentals/lumens.md)
-- [Stellar Consensus Protocol (SCP)](https://developers.stellar.org/docs/learn/fundamentals/stellar-consensus-protocol.md)
-- [Data Structures](https://developers.stellar.org/docs/learn/fundamentals/stellar-data-structures.md)
-- [Operations & Transactions](https://developers.stellar.org/docs/learn/fundamentals/transactions.md)
-- [Fees & Metering](https://developers.stellar.org/docs/learn/fundamentals/fees-resource-limits-metering.md)
-- [Stellar Ecosystem Proposals (SEPs)](https://developers.stellar.org/docs/learn/fundamentals/stellar-ecosystem-proposals.md)
-- [Smart Contracts](https://developers.stellar.org/docs/learn/fundamentals/contract-development.md)
-- [Data Format](https://developers.stellar.org/docs/learn/fundamentals/data-format.md)
-- [Ramps (anchors)](https://developers.stellar.org/docs/learn/fundamentals/anchors.md)
-- [SDEX](https://developers.stellar.org/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.md)
-
-[Glossary](https://developers.stellar.org/docs/learn/glossary.md)
-- [Migrate from Another Chain](https://developers.stellar.org/docs/learn/migrate.md)
-- [Interactive Learning](https://developers.stellar.org/docs/learn/interactive.md)
-
-[Tokens](https://developers.stellar.org/docs/tokens.md)
-
-- [Stellar Assets & Contract Tokens](https://developers.stellar.org/docs/tokens.md)
-- [Assets Overview](https://developers.stellar.org/docs/tokens/anatomy-of-an-asset.md)
-- [Quickstart Guide](https://developers.stellar.org/docs/tokens/quickstart.md)
-- [Asset Design Considerations](https://developers.stellar.org/docs/tokens/control-asset-access.md)
-- [Stellar Asset Contract](https://developers.stellar.org/docs/tokens/stellar-asset-contract.md)
-- [Token Interface](https://developers.stellar.org/docs/tokens/token-interface.md)
-- [Tutorial: Issue an Asset](https://developers.stellar.org/docs/tokens/how-to-issue-an-asset.md)
-- [Publish Asset Information](https://developers.stellar.org/docs/tokens/publishing-asset-info.md)
-- [USDT0 Transfers with LayerZero](https://developers.stellar.org/docs/tokens/usdt0-layerzero.md)
-
-[Data](https://developers.stellar.org/docs/data.md)
-
-- [Overview](https://developers.stellar.org/docs/data.md)
-
-[Analytics](https://developers.stellar.org/docs/data/analytics.md)
-- [Hubble](https://developers.stellar.org/docs/data/analytics/hubble.md)
-- [Providers](https://developers.stellar.org/docs/data/analytics/analytics-providers.md)
-
-[API](https://developers.stellar.org/docs/data/apis.md)
-- [RPC](https://developers.stellar.org/docs/data/apis/rpc.md)
-- [RPC Providers](https://developers.stellar.org/docs/data/apis/rpc/providers.md)
-- [Horizon](https://developers.stellar.org/docs/data/apis/horizon.md)
-- [Horizon Providers](https://developers.stellar.org/docs/data/apis/horizon/providers.md)
-- [Migrate Horizon to RPC](https://developers.stellar.org/docs/data/apis/migrate-from-horizon-to-rpc.md)
-
-[Indexers](https://developers.stellar.org/docs/data/indexers.md)
-- [Build Your Own](https://developers.stellar.org/docs/data/indexers/build-your-own.md)
-- [Providers](https://developers.stellar.org/docs/data/indexers.md)
-
-[Oracles](https://developers.stellar.org/docs/data/oracles.md)
-- [Providers](https://developers.stellar.org/docs/data/oracles.md)
-
-[Tools](https://developers.stellar.org/docs/tools.md)
-
-Developer Tools
-- [SDKs](https://developers.stellar.org/docs/tools/sdks.md)
-- [Stellar CLI](https://developers.stellar.org/docs/tools/cli.md)
-- [Lab](https://developers.stellar.org/docs/tools/lab.md)
-- [Quickstart](https://developers.stellar.org/docs/tools/quickstart.md)
-- [OpenZeppelin Relayer](https://developers.stellar.org/docs/tools/openzeppelin-relayer.md)
-- [OpenZeppelin Contracts](https://developers.stellar.org/docs/tools/openzeppelin-contracts.md)
-- [Scaffold Stellar](https://developers.stellar.org/docs/tools/scaffold-stellar.md)
-- [Building with AI](https://developers.stellar.org/docs/build/building-with-ai.md)
-- [More Developer Tools](https://developers.stellar.org/docs/tools/developer-tools.md)
-
-Ramps
-- [MoneyGram Ramps](https://developers.stellar.org/docs/tools/ramps/moneygram.md)
-
-Infra Tools
-- [Cross-Chain](https://developers.stellar.org/docs/tools/infra-tools/cross-chain.md)
-
-SDF Platforms
-- [Anchor Platform](https://developers.stellar.org/docs/platforms/anchor-platform.md)
-- [Stellar Disbursement Platform](https://developers.stellar.org/docs/platforms/stellar-disbursement-platform.md)
-
-[Networks](https://developers.stellar.org/docs/networks.md)
-
-- [Networks Overview](https://developers.stellar.org/docs/networks.md)
-- [Software Versions](https://developers.stellar.org/docs/networks/software-versions.md)
-- [Resource Limits & Fees](https://developers.stellar.org/docs/networks/resource-limits-fees.md)
-
-[Validators](https://developers.stellar.org/docs/validators.md)
-
-- [Validators Introduction](https://developers.stellar.org/docs/validators.md)
-- [Admin Guide](https://developers.stellar.org/docs/validators/admin-guide.md)
-- [Tier 1 Organizations](https://developers.stellar.org/docs/validators/tier-1-orgs.md)
-
-[GitHub](https://github.com/stellar/stellar-docs)
-
-[![](https://developers.stellar.org/assets/images/stellar-101-26081c928aa1f2587e8fa50c8820e4f0.png)](https://developers.stellar.org/docs/tokens/quickstart.md)
-
-### Asset Issuers
-
-Issue an asset or create a custom smart contract token.
-
-[Learn More](https://developers.stellar.org/docs/tokens/quickstart.md)
-
-[![](https://developers.stellar.org/assets/images/contract-4360e7119b2a4ba81b3849ea53901d98.png)](https://developers.stellar.org/docs/build/smart-contracts/getting-started.md)
-
-### Smart Contract Developers
-
-Write smart contracts on the Stellar network.
-
-[Learn More](https://developers.stellar.org/docs/build/smart-contracts/getting-started.md)
-
-[![](https://developers.stellar.org/assets/images/issue-assets-89ec386030248f486d74852861375c43.png)](https://developers.stellar.org/docs/learn/fundamentals/anchors.md)
-
-### Ramps (Anchors)
-
-Learn about and set up an anchor.
-
-[Learn More](https://developers.stellar.org/docs/learn/fundamentals/anchors.md)
-
-[![](https://developers.stellar.org/assets/images/build-applications-41ff5c71635741622bf54098505815da.png)](https://developers.stellar.org/docs/build/apps/overview.md)
-
-### Applications
-
-Build a traditional wallet, dapp, or list Stellar assets on an exchange.
-
-[Learn More](https://developers.stellar.org/docs/build/apps/overview.md)
-
-[![](https://developers.stellar.org/assets/images/dev-tools-80163b11f1e5d7aee9a2d7e24c680762.png)](https://developers.stellar.org/docs/data/apis.md)
-
-### Infrastructure Providers
-
-Set up a Horizon or RPC service.
-
-[Learn More](https://developers.stellar.org/docs/data/apis.md)
-
-[![](https://developers.stellar.org/assets/images/access-data-cd89f8e864d88bc2518f0b4716946071.png)](https://developers.stellar.org/docs/data/analytics.md)
-
-### Analytics
-
-Use Hubble to perform analysis on Stellar network data.
-
-[Learn More](https://developers.stellar.org/docs/data/analytics.md)
-
-
-## **Navigating the docs** [​](https://developers.stellar.org/\#navigating-the-docs "Direct link to navigating-the-docs")
-
-What each main section of the developer docs contains.
-
-### Build
-
-Contains tutorials and how-to guides for writing smart contracts, building applications, interacting with the network, and more.
-
-[Explore](https://developers.stellar.org/docs/build.md)
-
-### Learn
-
-Find all informational and conceptual content here. Learn about Stellar fundamentals like how accounts and transactions function, dive deeper into the functionality of each operation, discover how fees work, and more.
-
-[Explore](https://developers.stellar.org/docs/learn/fundamentals.md)
-
-### Tokens
-
-Information on how to issue assets on the Stellar network and create custom smart contract tokens.
-
-[Explore](https://developers.stellar.org/docs/tokens.md)
-
-### Data
-
-Discover various data availability options: RPC, Hubble, Horizon, Galexie, and data indexers.
-
-[Explore](https://developers.stellar.org/docs/data.md)
-
-### Tools
-
-Learn about all the available tools for building on, interacting with, or just watching the Stellar network. Also, find information on how to use the Anchor Platform or Stellar Disbursement Platform.
-
-[Explore](https://developers.stellar.org/docs/tools.md)
-
-### Networks
-
-Information about deployed networks (Mainnet, Testnet, and Futurenet), current software versions, resource limitations, and fees.
-
-[Explore](https://developers.stellar.org/docs/networks.md)
-
-### Validators
-
-Everything you'll need to know if you want to run, operate, and maintain a core validator node on the Stellar network.
-
-[Explore](https://developers.stellar.org/docs/validators.md)
-
-## **Developer resources** [​](https://developers.stellar.org/\#developer-resources "Direct link to developer-resources")
-
-Interact with other Stellar developers, keep up with ecosystem standards and protocol upgrades, and learn about upcoming events.
-
-### Stellar Developer Discord
-
-Ask questions and engage with other Stellar devs.
-
-[Explore](https://discord.gg/stellardev)
-
-### Developer Site
-
-Get the latest news and insights about building on Stellar.
-
-[Explore](https://stellar.org/developers)
-
-### Stellar Stack Exchange
-
-A question and answer site for Stellar developers; if you can’t find what you’re looking for in the docs, try searching the Stack Exchange to see if your question has been addressed. If it hasn't, feel free to ask!
-
-[Explore](https://stellar.stackexchange.com)
-
-### Stellar Developers Google Group
-
-Discuss Core Advancement Proposals (CAPs) and Stellar Ecosystem Proposals (SEPs), talk about the development of Stellar Core and Horizon, and stay informed about important network upgrades.
-
-[Explore](https://groups.google.com/g/stellar-dev)
-
-
-Resources
-
-- [Developer Blog](https://stellar.org/developers-blog)
-- [Stellar Quest](https://quest.stellar.org)
-- [Soroban Quest](https://fastcheapandoutofcontrol.com/tutorial)
-- [YouTube](https://www.youtube.com/@StellarDevelopmentFoundation)
-- [Twitch](https://m.twitch.tv/stellarorg/home)
-
-Tools
-
-- [Explorer](https://stellar.expert)
-- [Lab](https://lab.stellar.org)
-- [Status](https://status.stellar.org)
-- [Dashboard](https://dashboard.stellar.org)
-- [All Tools](https://developers.stellar.org/docs/tools.md)
-
-Community
-
-- [Contribute to Docs](https://github.com/stellar/stellar-docs?tab=readme-ov-file#contributing)
-- [Developer Discord](https://discord.gg/stellardev)
-- [Developer Meetings](https://developers.stellar.org/meetings)
-- [Developer Google Group](https://groups.google.com/g/stellar-dev)
-- [Stack Exchange](https://stellar.stackexchange.com)
-- [Stellar Community Fund](https://communityfund.stellar.org)
-
-About
-
-- [About SDF](https://stellar.org/foundation)
-- [Careers](https://stellar.org/foundation/careers)
-- [Events](https://stellar.org/events)
-- [Grants & Funding](https://stellar.org/foundation/grants-and-funding)
diff --git a/static/robots.txt b/static/robots.txt
deleted file mode 100644
index 203d37b04..000000000
--- a/static/robots.txt
+++ /dev/null
@@ -1,6 +0,0 @@
-# Algolia-Crawler-Verif: 14A6F6C8BF9C907E
-
-User-agent: *
-Allow: /
-Content-Signal: ai-train=yes, search=yes, ai-input=yes
-Sitemap: https://developers.stellar.org/sitemap.xml
diff --git a/static/stellar-rpc-beta.openrpc.json b/stellar-rpc-beta.openrpc.json
similarity index 100%
rename from static/stellar-rpc-beta.openrpc.json
rename to stellar-rpc-beta.openrpc.json
diff --git a/static/stellar-rpc.openrpc.json b/stellar-rpc.openrpc.json
similarity index 100%
rename from static/stellar-rpc.openrpc.json
rename to stellar-rpc.openrpc.json
diff --git a/style.css b/style.css
new file mode 100644
index 000000000..f27c5b40d
--- /dev/null
+++ b/style.css
@@ -0,0 +1,703 @@
+/* Many rules below target Mintlify's internal markup (ids, data attributes,
+   Tailwind classes), which can change without notice. Re-check the styling
+   after Mintlify releases. */
+
+:root {
+  --stellar-accent: #7d73b2;
+  --stellar-accent-hover: #6c629f;
+  --stellar-accent-contrast: #ffffff;
+  --stellar-accent-soft: rgba(125, 115, 178, 0.12);
+  --stellar-accent-border: rgba(125, 115, 178, 0.24);
+}
+
+html.dark,
+html[data-theme="dark"] {
+  --stellar-accent: #ffda00;
+  --stellar-accent-hover: #ffe34d;
+  --stellar-accent-contrast: #0a0a0a;
+  --stellar-accent-soft: rgba(255, 218, 0, 0.12);
+  --stellar-accent-border: rgba(255, 218, 0, 0.24);
+}
+
+.stellar-hero-base {
+  background:
+    radial-gradient(circle at 16% 52%, rgba(125, 115, 178, 0.18) 0%, rgba(125, 115, 178, 0.08) 24%, rgba(255, 255, 255, 0) 56%),
+    linear-gradient(180deg, #fcfbff 0%, #ffffff 56%, #f6f4ff 100%);
+}
+
+.stellar-hero-base-dark {
+  background:
+    radial-gradient(circle at 16% 52%, rgba(255, 218, 0, 0.12) 0%, rgba(255, 218, 0, 0.06) 24%, rgba(10, 10, 10, 0) 56%),
+    linear-gradient(180deg, #040404 0%, #09090b 56%, #0f172a 100%);
+}
+
+.stellar-hero-wash-light {
+  background: linear-gradient(90deg, rgba(255, 255, 255, 0.92) 0%, rgba(255, 255, 255, 0.74) 34%, rgba(255, 255, 255, 0.24) 68%, rgba(255, 255, 255, 0) 100%);
+}
+
+.stellar-hero-wash-dark {
+  background: linear-gradient(90deg, rgba(2, 6, 23, 0.86) 0%, rgba(2, 6, 23, 0.68) 34%, rgba(2, 6, 23, 0.2) 68%, rgba(2, 6, 23, 0) 100%);
+}
+
+.stellar-accent-button {
+  background-color: var(--stellar-accent);
+  color: var(--stellar-accent-contrast);
+}
+
+.stellar-accent-button:hover {
+  background-color: var(--stellar-accent-hover);
+  color: var(--stellar-accent-contrast);
+}
+
+.stellar-accent-outline-button {
+  border-color: rgba(23, 23, 23, 0.14);
+  background-color: rgba(255, 255, 255, 0.7);
+  color: #171717;
+}
+
+.stellar-accent-outline-button:hover {
+  border-color: var(--stellar-accent);
+  background-color: var(--stellar-accent-soft);
+  color: var(--stellar-accent);
+}
+
+html.dark .stellar-accent-outline-button,
+html[data-theme="dark"] .stellar-accent-outline-button {
+  border-color: rgba(255, 255, 255, 0.2);
+  background-color: rgba(255, 255, 255, 0.05);
+  color: #ffffff;
+}
+
+.stellar-accent-panel {
+  border: 1px solid var(--stellar-accent-border);
+  background: linear-gradient(90deg, rgba(125, 115, 178, 0.16) 0%, #ffffff 52%, rgba(125, 115, 178, 0.06) 100%);
+}
+
+html.dark .stellar-accent-panel,
+html[data-theme="dark"] .stellar-accent-panel {
+  background: linear-gradient(90deg, rgba(255, 218, 0, 0.1) 0%, #0a0a0a 52%, #0f172a 100%);
+}
+
+@media (max-width: 767px) {
+  .stellar-hero-wash-light {
+    background: linear-gradient(180deg, rgba(255, 255, 255, 0.92) 0%, rgba(255, 255, 255, 0.82) 38%, rgba(255, 255, 255, 0.64) 100%);
+  }
+
+  .stellar-hero-wash-dark {
+    background: linear-gradient(180deg, rgba(2, 6, 23, 0.88) 0%, rgba(2, 6, 23, 0.78) 38%, rgba(2, 6, 23, 0.62) 100%);
+  }
+
+  .stellar-accent-panel {
+    background: linear-gradient(180deg, rgba(125, 115, 178, 0.14) 0%, #ffffff 46%, rgba(125, 115, 178, 0.06) 100%);
+  }
+
+  html.dark .stellar-accent-panel,
+  html[data-theme="dark"] .stellar-accent-panel {
+    background: linear-gradient(180deg, rgba(255, 218, 0, 0.1) 0%, #0a0a0a 46%, #0f172a 100%);
+  }
+}
+
+/* Move the sidebar anchors (Blog, Discord, X, YouTube) to the bottom of the sidebar */
+div:has(> ul > li > a.nav-anchor) {
+  display: flex;
+  flex-direction: column;
+}
+ul:has(> li > a.nav-anchor) {
+  order: 99;
+  margin-top: 2rem;
+  padding-top: 1rem;
+  border-top: 1px solid rgba(125, 115, 178, 0.24);
+}
+
+/* Remove the top gap left where the anchors used to be */
+div:has(> ul > li > a.nav-anchor) > div.mt-6 {
+  margin-top: 0;
+}
+#navigation-items > div.pt-6 {
+  padding-top: 0.5rem;
+}
+
+/* Pin the anchors to the bottom of the sidebar */
+#navigation-items [data-component-part="scroll-area-content"] {
+  min-height: 100%;
+  display: flex;
+  flex-direction: column;
+}
+#navigation-items [data-component-part="scroll-area-content"] > div {
+  flex: 1;
+}
+ul:has(> li > a.nav-anchor) {
+  margin-top: auto;
+  padding-top: 1rem;
+}
+
+/* Style Mintlify callouts like the SDS Notification component */
+.callout {
+  --Notification-bg: var(--sds-clr-lilac-01);
+  --Notification-border: var(--sds-clr-lilac-06);
+  --Notification-icon: var(--sds-clr-lilac-09);
+  --Notification-svg: url("/img/sds-icons/icons-info-circle.svg");
+  font-family: var(--sds-ff-base);
+  background-color: var(--Notification-bg) !important;
+  border: 1px solid var(--Notification-border) !important;
+  border-radius: 0.5rem !important;
+  padding: 0.75rem !important;
+  gap: 0.75rem !important;
+  color: var(--sds-clr-gray-11);
+  font-size: 0.875rem;
+  line-height: 1.25rem;
+}
+.callout[data-callout-type="tip"],
+.callout[data-callout-type="check"] {
+  --Notification-bg: var(--sds-clr-green-01);
+  --Notification-border: var(--sds-clr-green-06);
+  --Notification-icon: var(--sds-clr-green-09);
+  --Notification-svg: url("/img/sds-icons/icons-check-circle.svg");
+}
+.callout[data-callout-type="warning"] {
+  --Notification-bg: var(--sds-clr-amber-01);
+  --Notification-border: var(--sds-clr-amber-06);
+  --Notification-icon: var(--sds-clr-amber-09);
+  --Notification-svg: url("/img/sds-icons/icons-alert-triangle.svg");
+}
+.callout[data-callout-type="danger"] {
+  --Notification-bg: var(--sds-clr-red-01);
+  --Notification-border: var(--sds-clr-red-06);
+  --Notification-icon: var(--sds-clr-red-09);
+  --Notification-svg: url("/img/sds-icons/icons-alert-circle.svg");
+}
+[data-component-part="callout-icon"] {
+  width: 1rem !important;
+  margin-top: 0.125rem !important;
+}
+[data-component-part="callout-icon"] svg {
+  display: none;
+}
+[data-component-part="callout-icon"]::before {
+  content: "";
+  display: block;
+  width: 1rem;
+  height: 1rem;
+  background-color: var(--Notification-icon);
+  -webkit-mask: var(--Notification-svg) no-repeat center / contain;
+  mask: var(--Notification-svg) no-repeat center / contain;
+}
+
+/* Replace the "Copy page" button icon with SDS copy-01 */
+#page-context-menu-button svg {
+  display: none;
+}
+#page-context-menu-button > div::before {
+  content: "";
+  display: block;
+  width: 1rem;
+  height: 1rem;
+  flex-shrink: 0;
+  background-color: currentColor;
+  -webkit-mask: url("/img/sds-icons/icons-copy-01.svg") no-repeat center / contain;
+  mask: url("/img/sds-icons/icons-copy-01.svg") no-repeat center / contain;
+}
+
+/* Style the "Copy page" button group like SDS Button (tertiary, md) */
+#page-context-menu > button {
+  height: 2rem !important;
+  padding: 0.375rem 0.625rem !important;
+  font-family: var(--sds-ff-base);
+  font-size: 0.875rem !important;
+  line-height: 1.375rem !important;
+  font-weight: var(--sds-fw-semi-bold) !important;
+  color: var(--sds-clr-gray-12) !important;
+  background-color: var(--sds-clr-gray-01) !important;
+  border: 1px solid var(--sds-clr-gray-06) !important;
+  transition: background-color var(--sds-anim-transition-default),
+              border-color var(--sds-anim-transition-default);
+}
+#page-context-menu > button:hover {
+  background-color: var(--sds-clr-gray-04) !important;
+  border-color: var(--sds-clr-gray-07) !important;
+}
+#page-context-menu-button {
+  border-radius: 0.375rem 0 0 0.375rem !important;
+  border-right: 0 !important;
+}
+#page-context-menu > button:last-child {
+  border-radius: 0 0.375rem 0.375rem 0 !important;
+}
+#page-context-menu-button > div::before {
+  background-color: var(--sds-clr-gray-09);
+}
+
+/* "Copy page" button group — match Figma spec (Varial, node 3436:190880) */
+#page-context-menu > button {
+  height: 2.25rem !important;
+  padding: 0.5rem 0.75rem !important;
+  font-size: 0.875rem !important;
+  line-height: 1.25rem !important;
+  font-weight: 600 !important;
+  color: var(--sds-clr-gray-12) !important;
+  background-color: var(--sds-clr-gray-01) !important;
+  border: 1px solid var(--sds-clr-gray-06) !important;
+}
+#page-context-menu-button {
+  border-radius: 0.5rem 0 0 0.5rem !important;
+  border-right: 0 !important;
+}
+#page-context-menu-button > div {
+  gap: 0.25rem !important;
+}
+#page-context-menu > button:last-child {
+  width: 2.25rem !important;
+  padding: 0 !important;
+  justify-content: center;
+  border-radius: 0 0.5rem 0.5rem 0 !important;
+}
+
+/* Overlap the two buttons by 1px so the shared border reads as a single line */
+#page-context-menu-button {
+  border-right: 1px solid var(--sds-clr-gray-06) !important;
+  margin-right: -1px;
+  position: relative;
+  z-index: 1;
+}
+#page-context-menu > button:last-child {
+  border-left: 1px solid var(--sds-clr-gray-06) !important;
+}
+
+/* Previous / Next links: plain text, no card border or padding */
+#pagination a {
+  border: 0 !important;
+  border-radius: 0 !important;
+  padding: 0 !important;
+}
+
+/* Previous / Next page titles in brand primary (SDS lilac-09) */
+[data-component-part="pagination-title"] {
+  color: var(--sds-clr-lilac-09) !important;
+}
+#pagination a:hover [data-component-part="pagination-title"] {
+  color: var(--sds-clr-lilac-11) !important;
+}
+
+/* Replace the code block copy icon with SDS copy-01 */
+[data-testid="copy-code-button"] svg {
+  display: none;
+}
+[data-testid="copy-code-button"]::before {
+  content: "";
+  display: block;
+  width: 1rem;
+  height: 1rem;
+  background-color: var(--sds-clr-gray-09);
+  -webkit-mask: url("/img/sds-icons/icons-copy-01.svg") no-repeat center / contain;
+  mask: url("/img/sds-icons/icons-copy-01.svg") no-repeat center / contain;
+}
+[data-testid="copy-code-button"]:hover::before {
+  background-color: var(--sds-clr-gray-11);
+}
+
+/* Code block copy button: show SDS check (brand primary) for 2s after copying */
+[data-testid="copy-code-button"]:has(> svg.text-primary)::before {
+  background-color: var(--sds-clr-lilac-09);
+  -webkit-mask-image: url("/img/sds-icons/icons-check.svg");
+  mask-image: url("/img/sds-icons/icons-check.svg");
+}
+
+/* Previous / Next: put the label above the page title */
+#pagination a > div {
+  display: flex;
+  flex-direction: column-reverse;
+  gap: 0.25rem;
+}
+#pagination a > div > * {
+  margin: 0 !important;
+}
+
+/* Push the footer to the bottom of the page when content is short */
+#content-container > div.flex-1 {
+  display: flex;
+  flex-direction: column;
+}
+#content-area {
+  display: flex;
+  flex-direction: column;
+  flex: 1;
+}
+#footer {
+  margin-top: auto;
+  padding-bottom: 2rem !important;
+}
+
+/* Navbar: "For agents" as SDS primary button, "Developer Hub" as SDS tertiary button */
+a[data-component-name="primary-header-button"] {
+  height: 2rem;
+  padding: 0.375rem 0.625rem !important;
+  gap: 0.25rem;
+  font-size: 0.875rem !important;
+  line-height: 1.375rem;
+  font-weight: var(--sds-fw-semi-bold) !important;
+  color: var(--sds-clr-white) !important;
+  background-color: var(--sds-clr-lilac-09) !important;
+  border: 1px solid var(--sds-clr-lilac-09);
+  border-radius: 0.375rem !important;
+  box-shadow: none !important;
+  opacity: 1 !important;
+}
+a[data-component-name="primary-header-button"]:hover {
+  background-color: var(--sds-clr-lilac-11) !important;
+  border-color: var(--sds-clr-lilac-11);
+}
+a[data-component-name="primary-header-button"]::before {
+  content: "\2726";
+  font-size: 0.75rem;
+}
+/* For agents panel (rendered by for-agents.js) */
+#for-agents-panel {
+  position: fixed;
+  top: calc(var(--mintlify-slot-header-height, 6rem) + var(--banner-height, 0px) + 0.5rem);
+  right: 0.75rem;
+  bottom: 0.75rem;
+  width: min(25rem, calc(100vw - 1.5rem));
+  z-index: 60;
+  display: flex;
+  flex-direction: column;
+  font-family: var(--sds-ff-base);
+  color: var(--sds-clr-gray-12);
+  background-color: var(--sds-clr-gray-01);
+  border: 1px solid var(--sds-clr-gray-06);
+  border-radius: 0.5rem;
+  box-shadow: 0 8px 24px rgba(0, 0, 0, 0.12);
+  overflow: hidden;
+}
+#for-agents-panel[hidden] { display: none; }
+.fa-header {
+  display: flex;
+  align-items: center;
+  justify-content: space-between;
+  padding: 0.75rem 1rem;
+  border-bottom: 1px solid var(--sds-clr-gray-06);
+}
+.fa-title {
+  font-size: 0.875rem;
+  line-height: 1.25rem;
+  color: var(--sds-clr-gray-11);
+}
+.fa-close {
+  width: 1.5rem;
+  height: 1.5rem;
+  border: 0;
+  background: var(--sds-clr-gray-09);
+  -webkit-mask: url("/img/sds-icons/icons-x-close.svg") no-repeat center / 1rem;
+  mask: url("/img/sds-icons/icons-x-close.svg") no-repeat center / 1rem;
+  cursor: pointer;
+}
+.fa-close:hover { background: var(--sds-clr-gray-12); }
+.fa-body {
+  overflow-y: auto;
+  padding: 1rem;
+  display: flex;
+  flex-direction: column;
+  gap: 1.25rem;
+}
+.fa-picker-label,
+.fa-section-title {
+  display: block;
+  margin: 0 0 0.5rem;
+  font-size: 0.875rem;
+  line-height: 1.25rem;
+  font-weight: var(--sds-fw-medium);
+  color: var(--sds-clr-gray-12);
+}
+.fa-pills { display: flex; flex-wrap: wrap; gap: 0.5rem; }
+.fa-pill {
+  height: 1.625rem;
+  padding: 0.25rem 0.625rem;
+  font-family: inherit;
+  font-size: 0.75rem;
+  line-height: 1.125rem;
+  font-weight: var(--sds-fw-semi-bold);
+  color: var(--sds-clr-gray-12);
+  background-color: var(--sds-clr-gray-01);
+  border: 1px solid var(--sds-clr-gray-06);
+  border-radius: 9999px;
+  cursor: pointer;
+  transition: background-color var(--sds-anim-transition-default), border-color var(--sds-anim-transition-default);
+}
+.fa-pill:hover { background-color: var(--sds-clr-gray-04); border-color: var(--sds-clr-gray-07); }
+.fa-pill.is-active {
+  color: var(--sds-clr-base-00);
+  background-color: var(--sds-clr-gray-12);
+  border-color: var(--sds-clr-gray-12);
+}
+.fa-section {
+  display: flex;
+  flex-direction: column;
+  gap: 0.5rem;
+  padding-top: 1.25rem;
+  border-top: 1px solid var(--sds-clr-gray-06);
+}
+.fa-section-head { display: flex; align-items: baseline; justify-content: space-between; gap: 0.75rem; }
+.fa-section-head .fa-section-title { margin: 0; }
+.fa-desc, .fa-note {
+  margin: 0;
+  font-size: 0.875rem;
+  line-height: 1.25rem;
+  color: var(--sds-clr-gray-11);
+}
+.fa-note { font-size: 0.75rem; line-height: 1.125rem; }
+.fa-link {
+  font-size: 0.875rem;
+  line-height: 1.25rem;
+  font-weight: var(--sds-fw-medium);
+  color: var(--sds-clr-lilac-11);
+  text-decoration: none;
+  white-space: nowrap;
+}
+.fa-link:hover { text-decoration: underline; }
+.fa-links { display: flex; flex-wrap: wrap; gap: 1rem; margin-top: 0.25rem; }
+.fa-copy {
+  position: relative;
+  border: 1px solid var(--sds-clr-gray-06);
+  border-radius: 0.375rem;
+  background-color: var(--sds-clr-gray-02);
+}
+.fa-code {
+  margin: 0;
+  padding: 0.625rem 2.5rem 0.625rem 0.75rem;
+  font-family: var(--sds-ff-monospace);
+  font-size: 0.8125rem;
+  line-height: 1.25rem;
+  color: var(--sds-clr-gray-12);
+  white-space: pre-wrap;
+  word-break: break-all;
+}
+.fa-copy-btn {
+  position: absolute;
+  top: 0.375rem;
+  right: 0.375rem;
+  width: 1.75rem;
+  height: 1.75rem;
+  border: 0;
+  border-radius: 0.375rem;
+  background: transparent;
+  cursor: pointer;
+}
+.fa-copy-btn:hover { background: var(--sds-clr-gray-04); }
+.fa-copy-btn::before {
+  content: "";
+  display: block;
+  width: 1rem;
+  height: 1rem;
+  margin: auto;
+  background-color: var(--sds-clr-gray-09);
+  -webkit-mask: url("/img/sds-icons/icons-copy-01.svg") no-repeat center / contain;
+  mask: url("/img/sds-icons/icons-copy-01.svg") no-repeat center / contain;
+}
+.fa-copy-btn.is-copied::before {
+  background-color: var(--sds-clr-lilac-09);
+  -webkit-mask-image: url("/img/sds-icons/icons-check.svg");
+  mask-image: url("/img/sds-icons/icons-check.svg");
+}
+
+/* "For agents" navbar button: SDS tertiary instead of primary */
+a[data-component-name="primary-header-button"] {
+  color: var(--sds-clr-gray-12) !important;
+  background-color: var(--sds-clr-gray-01) !important;
+  border-color: var(--sds-clr-gray-06) !important;
+}
+a[data-component-name="primary-header-button"]:hover {
+  background-color: var(--sds-clr-gray-04) !important;
+  border-color: var(--sds-clr-gray-07) !important;
+}
+a[data-component-name="primary-header-button"]::before {
+  color: var(--sds-clr-gray-09);
+}
+
+/* For agents panel: full-height drawer flush to the right edge, like developers.stellar.org */
+#for-agents-panel {
+  top: calc(var(--mintlify-slot-header-height, 6rem) + var(--banner-height, 0px));
+  right: 0;
+  bottom: 0;
+  width: min(26rem, 100vw);
+  border-radius: 0;
+  border-width: 0 0 0 1px;
+  box-shadow: -8px 0 24px rgba(0, 0, 0, 0.06);
+  animation: fa-slide-in 180ms ease-out;
+}
+@keyframes fa-slide-in {
+  from { transform: translateX(100%); }
+  to   { transform: translateX(0); }
+}
+.fa-header { padding: 1rem 1.25rem; }
+.fa-body { padding: 1.25rem; }
+
+/* For agents panel: start right under the top header row, covering the tab bar */
+#for-agents-panel {
+  top: calc(3rem + var(--banner-height, 0px));
+  z-index: 40;
+}
+
+/* For agents panel links: match SDS Link (primary) */
+.fa-link {
+  display: inline-flex;
+  align-items: center;
+  gap: 0.125rem;
+  color: var(--sds-clr-lilac-11);
+  transition: color var(--sds-anim-transition-default);
+}
+.fa-link:hover {
+  color: var(--sds-clr-lilac-12);
+  text-decoration: none;
+}
+.fa-link > span { display: none; }
+.fa-link::after {
+  content: "";
+  display: block;
+  width: 1rem;
+  height: 1rem;
+  background-color: currentColor;
+  -webkit-mask: url("/img/sds-icons/icons-arrow-right.svg") no-repeat center / contain;
+  mask: url("/img/sds-icons/icons-arrow-right.svg") no-repeat center / contain;
+}
+
+/* Code block frame (filename header area): SDS gray-02 instead of Mintlify's tinted gray */
+#body-content .code-block {
+  background-color: var(--sds-clr-gray-02) !important;
+}
+#body-content [data-component-part="code-block-header-filename"] {
+  font-family: var(--sds-ff-base);
+  color: var(--sds-clr-gray-11);
+}
+
+/* Tab bar (Home / Build / Learn...): SDS gray-02 instead of Mintlify's tinted gray */
+#navbar .bg-gray-50 {
+  background-color: var(--sds-clr-gray-02) !important;
+}
+
+/* Active top-level tab: brand primary text to match the underline */
+#navbar .nav-tabs-item[aria-current="location"] {
+  color: var(--sds-clr-lilac-09) !important;
+}
+
+/* Sidebar: active group headers in gray-12, same as active page links */
+#navigation-items [data-active="true"] > div,
+#navigation-items .text-primary {
+  color: var(--sds-clr-gray-12) !important;
+}
+
+/* Sidebar active page link: drop Mintlify's faux-bold text-shadow so weight matches group headers */
+#navigation-items a[aria-current] {
+  text-shadow: none !important;
+}
+
+/* Sidebar group chevrons: SDS chevron-right instead of Mintlify's inline SVG */
+#navigation-items svg.transition-transform {
+  width: 1rem;
+  height: 1rem;
+  margin-right: 0;
+  color: var(--sds-clr-gray-09);
+  background-color: currentColor;
+  -webkit-mask: url("/img/sds-icons/icons-chevron-right.svg") no-repeat center / contain;
+  mask: url("/img/sds-icons/icons-chevron-right.svg") no-repeat center / contain;
+}
+#navigation-items svg.transition-transform > path {
+  display: none;
+}
+
+/* Context menu (Copy page dropdown): external-link arrows as SDS arrow-up-right */
+[role="menu"] [role="menuitem"] .font-medium > svg {
+  width: 0.875rem;
+  height: 0.875rem;
+  color: var(--sds-clr-gray-09);
+  background-color: currentColor;
+  -webkit-mask: url("/img/sds-icons/icons-arrow-up-right.svg") no-repeat center / contain;
+  mask: url("/img/sds-icons/icons-arrow-up-right.svg") no-repeat center / contain;
+}
+[role="menu"] [role="menuitem"] .font-medium > svg > path {
+  display: none;
+}
+
+/* Previous / Next chevrons: SDS chevron-left / chevron-right */
+[data-component-part="pagination-chevron"] {
+  width: 1rem;
+  height: 1rem;
+  color: var(--sds-clr-gray-09);
+  background-color: currentColor;
+  -webkit-mask: url("/img/sds-icons/icons-chevron-right.svg") no-repeat center / contain;
+  mask: url("/img/sds-icons/icons-chevron-right.svg") no-repeat center / contain;
+}
+[data-component-part="pagination-chevron"] > path {
+  display: none;
+}
+.pagination-prev [data-component-part="pagination-chevron"] {
+  -webkit-mask-image: url("/img/sds-icons/icons-chevron-left.svg");
+  mask-image: url("/img/sds-icons/icons-chevron-left.svg");
+  transform: none;
+}
+
+/* Active item in both side menus (sidebar + On this page): brand primary */
+#navigation-items a[aria-current],
+#navigation-items [data-active="true"] > div,
+#navigation-items .text-primary,
+#table-of-contents a[aria-current],
+#table-of-contents .text-primary {
+  color: var(--sds-clr-lilac-09) !important;
+}
+
+/* Active items in side menus: SDS semi-bold */
+#navigation-items a[aria-current],
+#navigation-items [data-active="true"] > button,
+#navigation-items button.text-primary,
+#table-of-contents a[aria-current] {
+  font-weight: var(--sds-fw-semi-bold) !important;
+}
+
+/* Sidebar: remove Mintlify's faux-bold text-shadow from every nav button and link */
+#navigation-items button,
+#navigation-items a {
+  text-shadow: none !important;
+}
+
+/* Purple text everywhere uses SDS lilac-11 (text), not lilac-09 (solid fill) */
+#navbar .nav-tabs-item[aria-current="location"],
+#navigation-items a[aria-current],
+#navigation-items [data-active="true"] > div,
+#navigation-items .text-primary,
+#table-of-contents a[aria-current],
+#table-of-contents .text-primary,
+[data-component-part="pagination-title"] {
+  color: var(--sds-clr-lilac-11) !important;
+}
+
+/* Active top-level tab: gray-12 text and underline */
+#navbar .nav-tabs-item[aria-current="location"] {
+  color: var(--sds-clr-gray-12) !important;
+  text-shadow: none !important;
+  font-weight: var(--sds-fw-semi-bold) !important;
+}
+#navbar .nav-tabs-item[aria-current="location"] > div.bg-primary {
+  background-color: var(--sds-clr-gray-12) !important;
+}
+
+/* Home page has no tab, so Mintlify marks the first tab active: show it as inactive */
+body:has(.stellar-hero-base) #navbar .nav-tabs-item[aria-current="location"] {
+  color: rgb(var(--gray-600)) !important;
+  font-weight: 500 !important;
+}
+body:has(.stellar-hero-base) #navbar .nav-tabs-item[aria-current="location"]:hover {
+  color: rgb(var(--gray-800)) !important;
+}
+html.dark body:has(.stellar-hero-base) #navbar .nav-tabs-item[aria-current="location"] {
+  color: rgb(var(--gray-400)) !important;
+}
+html.dark body:has(.stellar-hero-base) #navbar .nav-tabs-item[aria-current="location"]:hover {
+  color: rgb(var(--gray-300)) !important;
+}
+body:has(.stellar-hero-base) #navbar .nav-tabs-item[aria-current="location"] > div.bg-primary {
+  display: none;
+}
+
+/* Footer: no top divider line */
+#footer {
+  border-top: 0 !important;
+  padding-top: 0 !important;
+}
diff --git a/tools/gen-html-redirects.cjs b/tools/gen-html-redirects.cjs
new file mode 100644
index 000000000..7af0ff30b
--- /dev/null
+++ b/tools/gen-html-redirects.cjs
@@ -0,0 +1,156 @@
+#!/usr/bin/env node
+/*
+ * gen-html-redirects.cjs
+ * ---------------------------------------------------------------------------
+ * Generates a redirect map that strips a trailing `.html` from every page URL
+ * (e.g. /docs/learn/glossary.html -> /docs/learn/glossary), merges it with any
+ * redirects already defined in docs.json, and writes the combined list to a
+ * standalone `redirects.json`. It then rewrites docs.json's `redirects` key to
+ * a single `{ "$ref": "redirects.json" }` so the large list lives outside
+ * docs.json. Mintlify's prebuild resolves the $ref at build time.
+ *
+ * Re-runnable: it reads the current page list from docs.json's navigation each
+ * time, so adding/removing pages + re-running keeps the map in sync. Existing
+ * redirects (by source) always win over generated ones.
+ *
+ * Usage:
+ *   node tools/gen-html-redirects.cjs          # apply (writes redirects.json + docs.json)
+ *   node tools/gen-html-redirects.cjs --dry     # print summary only, write nothing
+ */
+'use strict';
+
+const fs = require('fs');
+const path = require('path');
+
+const ROOT = path.resolve(__dirname, '..');
+const DOCS_JSON = path.join(ROOT, 'docs.json');
+const REDIRECTS_JSON = path.join(ROOT, 'redirects.json');
+const REF_VALUE = 'redirects.json';
+const DRY = process.argv.includes('--dry');
+
+const text = fs.readFileSync(DOCS_JSON, 'utf8');
+const cfg = JSON.parse(text);
+
+// --- 1. Collect page routes: string items of any "pages" array + any "root".
+const routes = new Set();
+(function walk(node) {
+  if (Array.isArray(node)) return node.forEach(walk);
+  if (node && typeof node === 'object') {
+    for (const [k, v] of Object.entries(node)) {
+      if (k === 'pages' && Array.isArray(v)) {
+        for (const item of v) {
+          if (typeof item === 'string') routes.add(item);
+          else walk(item);
+        }
+      } else if (k === 'root' && typeof v === 'string') {
+        routes.add(v);
+      } else {
+        walk(v);
+      }
+    }
+  }
+})(cfg.navigation || cfg);
+
+// --- 2. Preserve existing redirects (resolve a pre-existing $ref if present).
+let existing = [];
+if (Array.isArray(cfg.redirects)) {
+  existing = cfg.redirects;
+} else if (cfg.redirects && typeof cfg.redirects === 'object' && cfg.redirects.$ref) {
+  const refPath = path.join(ROOT, cfg.redirects.$ref);
+  if (fs.existsSync(refPath)) existing = JSON.parse(fs.readFileSync(refPath, 'utf8'));
+}
+
+const existingSources = new Set(existing.map((r) => r.source));
+
+// --- 3. Build .html -> clean-slug redirects, skipping any source already taken.
+const generated = [];
+for (const route of [...routes].sort()) {
+  const clean = '/' + route.replace(/^\/+/, '');
+  const source = clean + '.html';
+  if (existingSources.has(source)) continue;
+  generated.push({ source, destination: clean }); // permanent defaults to true (308)
+}
+
+const combined = [...existing, ...generated];
+
+// Sanity: sources must be unique (Mintlify enforces this).
+const seen = new Set();
+const dupes = [];
+for (const r of combined) {
+  if (seen.has(r.source)) dupes.push(r.source);
+  seen.add(r.source);
+}
+
+console.log(`page routes:        ${routes.size}`);
+console.log(`existing redirects: ${existing.length}`);
+console.log(`generated (.html):  ${generated.length}`);
+console.log(`combined total:     ${combined.length}`);
+console.log(`duplicate sources:  ${dupes.length}${dupes.length ? ' -> ' + dupes.slice(0, 5).join(', ') : ''}`);
+if (dupes.length) {
+  console.error('Refusing to write: duplicate sources would fail validation.');
+  process.exit(1);
+}
+
+if (DRY) {
+  console.log('\n--dry: no files written. Sample generated entries:');
+  generated.slice(0, 5).forEach((r) => console.log('  ', JSON.stringify(r)));
+  process.exit(0);
+}
+
+// --- 4. Write redirects.json.
+fs.writeFileSync(REDIRECTS_JSON, JSON.stringify(combined, null, 2) + '\n');
+
+// --- 5. Surgically replace docs.json's `redirects` value with a $ref, leaving
+// the rest of the file byte-for-byte unchanged.
+const keyIdx = text.lastIndexOf('"redirects"');
+if (keyIdx === -1) {
+  console.error('Could not find "redirects" key in docs.json.');
+  process.exit(1);
+}
+// Find the start of the value after the colon.
+let i = text.indexOf(':', keyIdx) + 1;
+while (/\s/.test(text[i])) i++;
+const open = text[i]; // '[' for an array or '{' for an existing $ref object
+if (open !== '[' && open !== '{') {
+  console.error(`Unexpected redirects value start: ${JSON.stringify(open)}`);
+  process.exit(1);
+}
+const close = open === '[' ? ']' : '}';
+
+// String-aware bracket matcher.
+let depth = 0;
+let end = -1;
+let inStr = false;
+let esc = false;
+for (let j = i; j < text.length; j++) {
+  const c = text[j];
+  if (inStr) {
+    if (esc) esc = false;
+    else if (c === '\\') esc = true;
+    else if (c === '"') inStr = false;
+    continue;
+  }
+  if (c === '"') inStr = true;
+  else if (c === open) depth++;
+  else if (c === close) {
+    depth--;
+    if (depth === 0) { end = j; break; }
+  }
+}
+if (end === -1) {
+  console.error('Could not find end of redirects value.');
+  process.exit(1);
+}
+
+const newText = text.slice(0, i) + `{ "$ref": "${REF_VALUE}" }` + text.slice(end + 1);
+
+// Validate the result parses and the $ref is in place.
+const reparsed = JSON.parse(newText);
+if (!reparsed.redirects || reparsed.redirects.$ref !== REF_VALUE) {
+  console.error('Post-edit validation failed: redirects is not a $ref.');
+  process.exit(1);
+}
+fs.writeFileSync(DOCS_JSON, newText);
+
+console.log(`\nWrote ${REDIRECTS_JSON} (${combined.length} entries).`);
+console.log('Rewrote docs.json "redirects" -> { "$ref": "redirects.json" }.');
diff --git a/tools/sds/build-sds-icons.mjs b/tools/sds/build-sds-icons.mjs
new file mode 100644
index 000000000..8da5aea9a
--- /dev/null
+++ b/tools/sds/build-sds-icons.mjs
@@ -0,0 +1,50 @@
+// Swaps Mintlify's icons for SDS icons without touching pages. Mintlify draws every library icon as a
+// mask-image box whose inline style names the source file, so a CSS rule matching that file name can
+// replace the mask. Copies the mapped SDS SVGs to img/sds-icons/ and writes sds-icons.css at the docs root.
+// Add a row when a page starts using a new icon name; unmapped icons keep Mintlify's default.
+// Language logos on code tabs (Mintlify's devicon set) stay as they are: SDS has no language logos.
+import fs from "node:fs";
+import { createRequire } from "node:module";
+
+// Mintlify icon name (any Font Awesome style folder) -> SDS asset, as "icons/<name>" or "logos/<name>".
+const MAP = {
+  "file-lines": "icons/file-04",
+  "box-archive": "icons/folder",
+  "house": "icons/home-05",
+  "magnifying-glass": "icons/search-md",
+  "ellipsis-vertical": "icons/dots-vertical",
+  "angle-right": "icons/chevron-right",
+  "play": "icons/play",
+  "newspaper": "icons/announcement-01",
+  "cube": "icons/cube-01",
+  "mobile-screen": "icons/phone-01",
+  "bolt": "icons/zap",
+  "wallet": "icons/wallet-02",
+  "toolbox": "icons/tool-02",
+  "message": "icons/message-square-01",
+  "code": "icons/code-02",
+  "users": "icons/users-01",
+  "discord": "logos/discord",
+  "x-twitter": "logos/x-twitter",
+  "youtube": "logos/youtube",
+  "linkedin": "logos/linkedin",
+};
+
+const require = createRequire(import.meta.url);
+const pkgDir = require.resolve("@stellar/design-system/package.json").replace(/package\.json$/, "");
+const { version } = JSON.parse(fs.readFileSync(pkgDir + "package.json", "utf8"));
+const outDir = new URL("../../img/sds-icons/", import.meta.url);
+fs.mkdirSync(outDir, { recursive: true });
+
+const rules = Object.entries(MAP).map(([fa, sds]) => {
+  const file = sds.replace("/", "-") + ".svg";
+  fs.copyFileSync(`${pkgDir}build/assets/${sds}.svg`, new URL(file, outDir));
+  const url = `url("/img/sds-icons/${file}")`;
+  return `[style*="/${fa}.svg"] { -webkit-mask-image: ${url} !important; mask-image: ${url} !important; ` +
+    `-webkit-mask-size: contain !important; mask-size: contain !important; }`;
+});
+
+const header = `/* Generated from @stellar/design-system@${version} build/assets. Do not edit by hand.
+   Regenerate: cd tools/sds && npm install && npm run build */\n`;
+fs.writeFileSync(new URL("../../sds-icons.css", import.meta.url), header + rules.join("\n") + "\n");
+console.log(`sds-icons.css: ${rules.length} icons from @stellar/design-system@${version}`);
diff --git a/tools/sds/build-sds-tokens.mjs b/tools/sds/build-sds-tokens.mjs
new file mode 100644
index 000000000..9d9ac3548
--- /dev/null
+++ b/tools/sds/build-sds-tokens.mjs
@@ -0,0 +1,27 @@
+// Generates sds-tokens.css at the docs root from the pinned @stellar/design-system in package.json.
+// Keeps only --sds-* custom properties. Light and shared tokens go on :root, dark tokens on html.dark.
+import fs from "node:fs";
+import { createRequire } from "node:module";
+import postcss from "postcss";
+
+const require = createRequire(import.meta.url);
+const pkgDir = require.resolve("@stellar/design-system/package.json").replace(/package\.json$/, "");
+const { version } = JSON.parse(fs.readFileSync(pkgDir + "package.json", "utf8"));
+const src = fs.readFileSync(pkgDir + "build/styles.min.css", "utf8");
+
+const out = postcss.root();
+out.append(postcss.rule({ selector: ":root" }).append({ prop: "--sds-version", value: `"${version}"` }));
+postcss.parse(src).walkRules((rule) => {
+  const themeSelectors = rule.selectors.filter((s) => /^(:root|\.sds-theme-(light|dark))$/.test(s));
+  if (themeSelectors.length !== rule.selectors.length) return;
+  const tokens = rule.nodes.filter((n) => n.type === "decl" && n.prop.startsWith("--sds-"));
+  if (!tokens.length) return;
+  const isDark = rule.selectors.length === 1 && rule.selectors[0] === ".sds-theme-dark";
+  const selectors = isDark ? ["html.dark", 'html[data-theme="dark"]'] : [":root"];
+  out.append(postcss.rule({ selectors }).append(tokens.map((t) => t.clone())));
+});
+
+const header = `/* Generated from @stellar/design-system@${version} build/styles.min.css. Do not edit by hand.
+   Regenerate: cd tools/sds && npm install && npm run build */\n`;
+fs.writeFileSync(new URL("../../sds-tokens.css", import.meta.url), header + out.toString() + "\n");
+console.log(`sds-tokens.css written from @stellar/design-system@${version}`);
diff --git a/tools/sds/package-lock.json b/tools/sds/package-lock.json
new file mode 100644
index 000000000..0d34b6bbd
--- /dev/null
+++ b/tools/sds/package-lock.json
@@ -0,0 +1,215 @@
+{
+  "name": "sds-mintlify",
+  "lockfileVersion": 3,
+  "requires": true,
+  "packages": {
+    "": {
+      "name": "sds-mintlify",
+      "devDependencies": {
+        "@stellar/design-system": "4.0.2",
+        "postcss": "8.5.28"
+      }
+    },
+    "node_modules/@floating-ui/core": {
+      "version": "1.8.0",
+      "resolved": "https://registry.npmjs.org/@floating-ui/core/-/core-1.8.0.tgz",
+      "integrity": "sha512-0CIZ5itps/8x7BG8dEIhs53BvCUH2PCoogtakwRTut+Arm58sJooJ0AuZhLw2HJYIR5cMLNPBSS728sPho2khQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "@floating-ui/utils": "^0.2.12"
+      }
+    },
+    "node_modules/@floating-ui/dom": {
+      "version": "1.8.0",
+      "resolved": "https://registry.npmjs.org/@floating-ui/dom/-/dom-1.8.0.tgz",
+      "integrity": "sha512-yXSrzeHZBTZadLOlfyhCkJHNeLJnHRnRInwdZ40L7ZiaAtrBwoYlsDrX3v5zB1Utk7CLfzcOVnVVWoXEky7Ceg==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "@floating-ui/core": "^1.8.0",
+        "@floating-ui/utils": "^0.2.12"
+      }
+    },
+    "node_modules/@floating-ui/utils": {
+      "version": "0.2.12",
+      "resolved": "https://registry.npmjs.org/@floating-ui/utils/-/utils-0.2.12.tgz",
+      "integrity": "sha512-HpCo8tmWzLVad5s2d19EhAz5zqrrQ6s69qd6moPMQvkOuSwDT1YgRfWSVuc4ennqrgv3OHppiOGMQ7oC13yIww==",
+      "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/@stellar/design-system": {
+      "version": "4.0.2",
+      "resolved": "https://registry.npmjs.org/@stellar/design-system/-/design-system-4.0.2.tgz",
+      "integrity": "sha512-GYFrbVp4tjLP4JoW8wuQRdRQAvNZwzCERqwcSIdKkNcTpsqIhs/QpU01ZJbrgyzjIuIRzUBf6qXjIpK9pQL0/w==",
+      "dev": true,
+      "license": "Apache-2.0",
+      "dependencies": {
+        "@floating-ui/dom": "^1.7.4",
+        "bignumber.js": "^9.3.1",
+        "lodash": "^4.17.21",
+        "react-copy-to-clipboard-ts": "^1.3.0",
+        "tslib": "^2.8.1"
+      },
+      "engines": {
+        "node": ">=22.0.0"
+      },
+      "peerDependencies": {
+        "react": ">=18.x",
+        "react-dom": ">=18.x"
+      }
+    },
+    "node_modules/bignumber.js": {
+      "version": "9.3.1",
+      "resolved": "https://registry.npmjs.org/bignumber.js/-/bignumber.js-9.3.1.tgz",
+      "integrity": "sha512-Ko0uX15oIUS7wJ3Rb30Fs6SkVbLmPBAKdlm7q9+ak9bbIeFf0MwuBsQV6z7+X768/cHsfg+WlysDWJcmthjsjQ==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": "*"
+      }
+    },
+    "node_modules/copy-to-clipboard": {
+      "version": "3.3.3",
+      "resolved": "https://registry.npmjs.org/copy-to-clipboard/-/copy-to-clipboard-3.3.3.tgz",
+      "integrity": "sha512-2KV8NhB5JqC3ky0r9PMCAZKbUHSwtEo4CwCs0KXgruG43gX5PMqDEBbVU4OUzw2MuAWUfsuFmWvEKG5QRfSnJA==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "toggle-selection": "^1.0.6"
+      }
+    },
+    "node_modules/lodash": {
+      "version": "4.18.1",
+      "resolved": "https://registry.npmjs.org/lodash/-/lodash-4.18.1.tgz",
+      "integrity": "sha512-dMInicTPVE8d1e5otfwmmjlxkZoUpiVLwyeTdUsi/Caj/gfzzblBcCE5sRHV/AsjuCmxWrte2TNGSYuCeCq+0Q==",
+      "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/nanoid": {
+      "version": "3.3.19",
+      "resolved": "https://registry.npmjs.org/nanoid/-/nanoid-3.3.19.tgz",
+      "integrity": "sha512-Y2tUNy4ouw6tq5oDSKeQYGOyhkUBhNOcGV/02KC+6kd9eDGqdZd++mjMiIDilrBYvjEnCYvVtsuHCuP+okSfug==",
+      "dev": true,
+      "funding": [
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/ai"
+        }
+      ],
+      "license": "MIT",
+      "bin": {
+        "nanoid": "bin/nanoid.cjs"
+      },
+      "engines": {
+        "node": "^10 || ^12 || ^13.7 || ^14 || >=15.0.1"
+      }
+    },
+    "node_modules/picocolors": {
+      "version": "1.1.1",
+      "resolved": "https://registry.npmjs.org/picocolors/-/picocolors-1.1.1.tgz",
+      "integrity": "sha512-xceH2snhtb5M9liqDsmEw56le376mTZkEX/jEb/RxNFyegNul7eNslCXP9FDj/Lcu0X8KEyMceP2ntpaHrDEVA==",
+      "dev": true,
+      "license": "ISC"
+    },
+    "node_modules/postcss": {
+      "version": "8.5.28",
+      "resolved": "https://registry.npmjs.org/postcss/-/postcss-8.5.28.tgz",
+      "integrity": "sha512-RRuzqDtt5Y9h3quz5hWhK+TPnsmVs6WwSU6LkJMeY4HstUEDuYTG8UJSdawMRzmzAtV+KEoG8N3Qg2qLy5vM/A==",
+      "dev": true,
+      "funding": [
+        {
+          "type": "opencollective",
+          "url": "https://opencollective.com/postcss/"
+        },
+        {
+          "type": "tidelift",
+          "url": "https://tidelift.com/funding/github/npm/postcss"
+        },
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/ai"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "nanoid": "^3.3.18",
+        "picocolors": "^1.1.1",
+        "source-map-js": "^1.2.1"
+      },
+      "engines": {
+        "node": "^10 || ^12 || >=14"
+      }
+    },
+    "node_modules/react": {
+      "version": "19.3.0",
+      "resolved": "https://registry.npmjs.org/react/-/react-19.3.0.tgz",
+      "integrity": "sha512-E8LUcbtBWt20bbl2YoHfx4ZDBdxVTfOKtCZn9cDSJ4l6/nuoApcpIBcj47t2wZoVX8g2ZHuMHbiShgCR1T5Sog==",
+      "dev": true,
+      "license": "MIT",
+      "peer": true,
+      "engines": {
+        "node": ">=0.10.0"
+      }
+    },
+    "node_modules/react-copy-to-clipboard-ts": {
+      "version": "1.3.1",
+      "resolved": "https://registry.npmjs.org/react-copy-to-clipboard-ts/-/react-copy-to-clipboard-ts-1.3.1.tgz",
+      "integrity": "sha512-qA4J3vHAdkdrqmaYvFCt5dbATtG8mQPl4Ar8HNrfrPvdaUqAQiwyQSg8fqSw8QYkH5KVUspNyvP6o/7kwZLw8Q==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "copy-to-clipboard": "^3.3.3"
+      },
+      "peerDependencies": {
+        "react": ">=18.0.0"
+      }
+    },
+    "node_modules/react-dom": {
+      "version": "19.3.0",
+      "resolved": "https://registry.npmjs.org/react-dom/-/react-dom-19.3.0.tgz",
+      "integrity": "sha512-JDk8dgif51OjFoDE70+OT9ICyYr+69HlmihNwp1+Nsfbna3t5sIiCa9ZJktDmQ4/1b/rn26hIAR2uYXDMr5r0Q==",
+      "dev": true,
+      "license": "MIT",
+      "peer": true,
+      "dependencies": {
+        "scheduler": "^0.28.0"
+      },
+      "peerDependencies": {
+        "react": "^19.3.0"
+      }
+    },
+    "node_modules/scheduler": {
+      "version": "0.28.0",
+      "resolved": "https://registry.npmjs.org/scheduler/-/scheduler-0.28.0.tgz",
+      "integrity": "sha512-juorfCmIkIw8tT+p5BXSm6PJjQF/ycEYmKyzURCIt/RaZIhL+PulbQ9Yu2z1HdOJDdqDTlxA1+xKBmHXJsczAw==",
+      "dev": true,
+      "license": "MIT",
+      "peer": true
+    },
+    "node_modules/source-map-js": {
+      "version": "1.2.2",
+      "resolved": "https://registry.npmjs.org/source-map-js/-/source-map-js-1.2.2.tgz",
+      "integrity": "sha512-KGj/8Y43x35aZVDtt+J4mK1hoLGHULMYfSkODJNQjNDC3oW1PqPoxMwo0pLUsWM/UEGzON/NxeHywEfNXNP3Vw==",
+      "dev": true,
+      "license": "BSD-3-Clause",
+      "engines": {
+        "node": ">=0.10.0"
+      }
+    },
+    "node_modules/toggle-selection": {
+      "version": "1.0.6",
+      "resolved": "https://registry.npmjs.org/toggle-selection/-/toggle-selection-1.0.6.tgz",
+      "integrity": "sha512-BiZS+C1OS8g/q2RRbJmy59xpyghNBqrr6k5L/uKBGRsTfxmu3ffiRnd8mlGPUVayg8pvfi5urfnu8TU7DVOkLQ==",
+      "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/tslib": {
+      "version": "2.8.1",
+      "resolved": "https://registry.npmjs.org/tslib/-/tslib-2.8.1.tgz",
+      "integrity": "sha512-oJFu94HQb+KVduSUQL7wnpmqnfmLsOA/nAh6b6EH0wCEoK0/mPeXU6c3wKDV83MkOuHPRHtSXKKU99IBazS/2w==",
+      "dev": true,
+      "license": "0BSD"
+    }
+  }
+}
diff --git a/tools/sds/package.json b/tools/sds/package.json
new file mode 100644
index 000000000..8b9432326
--- /dev/null
+++ b/tools/sds/package.json
@@ -0,0 +1,14 @@
+{
+  "name": "sds-mintlify",
+  "private": true,
+  "type": "module",
+  "scripts": {
+    "build": "node build-sds-tokens.mjs && node build-sds-icons.mjs",
+    "build:tokens": "node build-sds-tokens.mjs",
+    "build:icons": "node build-sds-icons.mjs"
+  },
+  "devDependencies": {
+    "@stellar/design-system": "4.0.2",
+    "postcss": "8.5.28"
+  }
+}
diff --git a/tsconfig.json b/tsconfig.json
deleted file mode 100644
index 02bb984f5..000000000
--- a/tsconfig.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
-  "extends": "@docusaurus/tsconfig",
-  "compilerOptions": {
-    "baseUrl": ".",
-    "ignoreDeprecations": "6.0",
-    "strict": true,
-    "types": ["docusaurus-plugin-sass"]
-  },
-  "exclude": [".docusaurus", "build"]
-}